Gridfs-stream error on windows.

Getting the following error on a development meteor run.
I'm assuming that its something to do with windows. Obviously using cfs:gridfs
Using these other CFS packages:
'cfs:standard-packages',
<EMAIL_ADDRESS>'cfs:ui',
'cfs:graphicsmagick',
'cfs:ejson-file'

W20150726-23:40:17.248(1)? (STDERR) ReferenceError: require is not defined
W20150726-23:40:17.248(1)? (STDERR)     at app\node_modules\gridfs-stream\node_modules\flushwritable\lib\FlushWritable.js:6:20
W20150726-23:40:17.248(1)? (STDERR)     at app\node_modules\gridfs-stream\node_m
odules\flushwritable\lib\FlushWritable.js:43:3
=> Exited with code: 8

Any ideas? I'm happy to run or do anything required if it can get you more information.

Does this have anything to do with windows not accepting folders with colons?
I think the convention is hyphens instead? Have to check on that..

I don't think so. Nothing in the file path has colons. Its just the package names that do. Thanks for the thoughts :)

Ok figured it out.
I installed the gridfs-stream npm module locally in my application root. This creates the node_modules directory and includes it in the build. Meteor then finds JS code and tries to run it within a meteor environment which causes the above error.
In the next release of meteor the node_modules folder will be excluded from build:
https://github.com/meteor/meteor/pull/4457


fix:restic missing repo desc

Whoops, that was too fast, didn't want to instantly merge here, sorry for that, but then again, I honestly have no good idea how to fix this any better.
I dont have repository set in my restic config and am using repositoryFile in combination with agenix.
nix-topology breaks when not encountering a set repository in the config.
Do you have an idea how to improve this?

Hmm good question, but I don't yet understand exactly how this breaks. I think backups.<name>.repository just defaults to null, so using or "" should be a noop. Is there a chance you still have the exact error on hand?

I recreated it. For now my workaround is setting repository to a descriptive name. Having set repositoryFile at the same time restic just uses this.
Heres the error message:
error:
       … while evaluating the attribute 'value'
         at /nix/store/hfz1qqd0z8amlgn8qwich1dvkmldik36-source/lib/modules.nix:816:9:
          815|     in warnDeprecation opt //
          816|       { value = addErrorContext "while evaluating the option `${showOption loc}':" value;
             |         ^
          817|         inherit (res.defsFinal') highestPrio;

       … while evaluating the option `topology.output':

       … while evaluating the attribute 'mergedValue'
         at /nix/store/hfz1qqd0z8amlgn8qwich1dvkmldik36-source/lib/modules.nix:851:5:
          850|     # Type-check the remaining definitions, and merge them. Or throw if no definitions.
          851|     mergedValue =
             |     ^
          852|       if isDefined then

       … while evaluating the option `topology.renderers.elk.output':

       … while evaluating the option `topology.nodes.haematit.services.remotebackup.info':

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: A definition for option `topology.nodes.<hostname>.services.remotebackup.info' is not of type `strings concatenated with "\n"'. Definition values:
       - In `/nix/store/ghmskbj92iry8723457pkb0p0zbfp2hb-source/topology': null


[bug]: soft lock on crash related to number being not a multiple of 8

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Linux
GPU
cuda
VRAM
No response
What version did you experience this issue on?
rc1
What happened?
Exception in thread invoker_processor:
Traceback (most recent call last):
  File "/usr/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.10/threading.py", line 953, in run
    self._target(*self._args, **self._kwargs)
  File "/home/jsp/InvokeAI3/src/invokeai/app/services/processor.py", line 50, in __process
    self.__invoker.services.graph_execution_manager.get(
  File "/home/jsp/InvokeAI3/src/invokeai/app/services/sqlite.py", line 79, in get
    return self._parse_item(result[0])
  File "/home/jsp/InvokeAI3/src/invokeai/app/services/sqlite.py", line 52, in _parse_item
    return parse_raw_as(item_type, item)
  File "pydantic/tools.py", line 82, in pydantic.tools.parse_raw_as
  File "pydantic/tools.py", line 38, in pydantic.tools.parse_obj_as
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for ParsingModel[GraphExecutionState]
__root__ -> execution_graph -> nodes -> 6c87d68f-031c-4bd5-bdb7-a6cfb84caadf -> NoiseInvocation -> height
  ensure this value is a multiple of 8 (type=value_error.number.not_multiple; multiple_of=8)
[2023-07-19 21:35:00,484]::[InvokeAI]::ERROR --> Image record not found

https://discord.com/channels/1020123559063990373/1131414478949470359
@JPPhoto
Screenshots
No response
Additional context
No response
Contact Details
No response

Odd, the discord link doesn't seem to be working for me and I can't find that stacktrace when searching for it

Here's another issue with same root cause https://github.com/invoke-ai/InvokeAI/issues/3412
The root cause is failed validation during processing, not when the graph is created. I'll test some of these scenarios and see if your pr fixes it.


Error in after(:all) hook doesn't fail rspec

For my tests, I have the following hooks in my spec_helper:
RSpec.configure do |config|

  config.before(:all) do
    setup
  end

  config.after(:all) do
     teardown
  end

end

And the teardown method has some logic for failure:
def teardown
  # if some logic
    raise "Error occurred in after_all hook"
end

Now, when I execute my tests, and the after(:all) hook fails, it prints the error on console output, all specs have passed (which is right), but the overall execution is passed and ends with exit code 0.
I don't understand why we do not fail rspec execution if a after hook failed.
PS: This is also evident in https://www.relishapp.com/rspec/rspec-core/v/2-2/docs/hooks/before-and-after-hooks#failure-in-after(:all)-block
Any help/explanation will be much appreciated.

This is working as designed -- although perhaps we can improve that design.
In general, after hooks are meant for teardown/cleanup, not for assertions or other test lock.  after(:all) even more so -- at the point it runs, the examples in its group have all been reported to the formatter as having passed or failed based on their own status so there's no chance for a failure in an after(:all) hook to affect the pass/fail status of the examples in its group.
We could potentially make after(:all) trigger RSpec to exit with a failing exit status (e.g. 1 instead of 0) but there are a few issues with that:

RSpec doesn't currently have any concept of outside source of failure -- the suite pass/fail status is based on whether or not all specs passed or not.  Having all specs pass but the suite fail due to an after(:all) hook failure is a bit weird.
If teardown/cleanup logic encounters a failure, it's not clear that what you want is a failure, anyway.  For example: if you're after(:all) hook tries to delete a temporary log file, and fails...do you care enough to make it fail your suite?
Given that after(:all) hook failures don't currently cause a suite failure, and that for some users, having the suite fail would be undesirable, making this change now would be a breaking change.  We could make this change in RSpec 4, though.

Thoughts?

Thanks @myronmarston . That's what I thought that this is by design.
My opinion is that it should be consistent. If the before(:all) hook(s) fail the process, so should after(:all). And if any part of the process fails - be it trivial creation / deletion of temp files, it should exit with status 1.
The issue this current behaviour causes is that it makes a build job (say: hudson) pass even when the teardown has failed. And our teardown does a crucial task - reverting application flags to pre-test state.  Hence, we missed to identify a potential problem in our test setup for quite a while, since the tests kept passing and further builds proceeded without a red herring. Rather undesirable :(
Would greatly appreciate if this is updated in RSpec4. Awaiting some more opinions and thoughts.

I think I'm mildly in favour of changing this behaviour in 4, or at least adding in a opt-in mode to enable this. Having errors in your test suite is kind of a smell so it'd be nice to have a strict mode to allow people to enforce not having them..

I think we should make it a config option:
config.evaluate_after_all_blocks_strictly = true/false
config.treate_errors_in_after_all_blocks_as_failures = true/false

or similar. We could add that now, and then decide whether or not to turn it on or not in RSpec 4 later.

I agree that this would be a nice config option to have.


Only sync published releases.

The current code for syncing releases breaks if there are repositories that contain unpublished/ draft releases. This introduces a change to ignore those releases.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Thank you!


RL-update2

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[ ] Testing of all the changes has been performed (for bug fixes / features)
[ ] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[ ] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[ ] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[ ] Verify all checks are passing.
[ ] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[ ] Do NOT submit updates to dependencies unless it fixes an issue.
[ ] Limit your pull request to one application and submit multiple pull requests if necessary.

Pull Request Type
Please check the type of change your PR introduces:

[ ] New App
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

Hey @ivukovicRL, we will take care of these Static tests failures. If your other PR(https://github.com/splunk-soar-connectors/reversinglabs-tiscale/pull/4) is consisting the same changes, then you can close that PR.
Thanks,
Mit

Hi @mjiyani-crest and thanks for the support. RL-update PR is deleted. We have a few questions regarding the PR.
There was an obsolete view tiscale_view.py which we deleted in this PR but it was still there causing errors during the checks (as if it was cached somewhere). So we added it again as an empty file in this commit https://github.com/splunk-soar-connectors/reversinglabs-tiscale/pull/5/commits/a0e11a458d6390e3c9fa1d15f5f631891c7d65b1 so the test could pass. Can you delete it for us?
We also need to update our docs before the merge. Do you have some kind of a template for the docs? Also is the md enough or do we need to generate both html and md for the docs?

Hey @ivukovicRL, thanks for reverting back.

There was an obsolete view tiscale_view.py which we deleted in this PR but it was still there causing errors during the checks (as if it was cached somewhere). So we added it again as an empty file in this commit a0e11a4 so the test could pass. Can you delete it for us?

Once you will finish your changes, we will start working on this PR and take care of it.

We also need to update our docs before the merge. Do you have some kind of template for the docs? Also is the md enough or do we need to generate both HTML and md for the docs?

Yes, you have to create both HTML and md files by keeping the same content in them. You can add all the details which are necessary for the user to take care of while using the app.

Hello @ivukovicRL, Are you done with the changes?
Can we start further activities to release the app?

Hello @ivukovicRL, Are you done with the changes? Can we start further activities to release the app?

Hi @dgopani-crest, thanks for asking. We are almost done. There is is still one more deprecated function in our code, i will let you know when we fix this.
Also we will soon open new PRs on https://github.com/splunk-soar-connectors/reversinglabs-ticloud and https://github.com/splunk-soar-connectors/reversinglabs-a1000

Hi @dgopani-crest, thanks for asking. We are almost done. There is still one more deprecated function in our code, I will let you know when we fix this.

Thanks for the quick response @ivukovicRL. Please let us know once all the changes are updated, we will start further release activities

@dgopani-crest Is there a way to auto-generate a readme out of a config file (for actions outputs)? Also, do you have a preferred tool to convert a markdown to html?

@ivukovicRL, the Documentation mentioned in the screenshot will be auto-generated by your readme.html and .json file and looks like this. The above section of Configuration Variables is generated by readme.html and below that is generated from json file.
readme.md is also a combination of these 2 files, which will help users to know about an app on GitHub repo. For README.md do not worry, we will take care of that and will create it from mentioned 2 files. So you can update all the required data in the readme.html & json file, it will automatically reflect on the Documentation page

@dgopani-crest It should be ok now.

@dgopani-crest It should be ok now.

Thanks @ivukovicRL, we will start further activities and release the app

Hi @ivukovicRL, I am unable to push the changes to branch 'reversinglabs:rl-update2' with below error,

Hi @ebhoir-crest you are added as a collaborator. Please let me know if you have any more issues.

Static test failures are added to expected failures list and MR has been raised for the same. Once the expected failure MR is merged it will resolve the static tests.

Hi @ivukovicRL can you please suggest for the points to be added in unreleased.md for current app changes

Hi @ivukovicRL can you please suggest points for unreleased.md ?

Hi @ivukovicRL, currently we have added below one point for release notes.  we are seeing backward compatibility changes in the action parameters so other than this point do we need to add any other release notes point?

Compatibility changes for Python 3 support

Also, we have made a few best practices changes in the PR. Please have a look into it and let us know in case of any queries.

@dgopani-crest  We agree with the changes.

Static test fails as min_phantom_version will be 5.0.0

Hi @dgopani-crest is there anything else that we need to do before the release?

Hi @dgopani-crest is there anything else that we need to do before the release?

@ivukovicRL, the app is released and available on the splunkbase and my.phantom.us


[QUESTION] How to enable "track_scores" in version 2.x

Dear guys,
We are using Elasticsearch 2.x and ElasticsearchDSL version 2.x too. Based on our needs, we need to enable track_scores in Search request. So I just want to know are there any way to enable this config in version 2.x? Seems it's supported in ElasticsearchDSL version 5.x afak.
Thanks so much

Hi @trandangtri, in 2.x it is not supported. The only way to get it work is to add a support. What has to be done here is to add in getQueryParams the required key and the variable to hold it.
btw 2.x is getting old, is there any reason why you don't upgrade to 5.x of the elasticsearch?

Thanks @saimaz for your quick response.
As an ad-hoc solution, I override ONGR\ElasticsearchDSL\Search as below, and it works as my expectation
namespace AcmeBundle\Service\ONGR\ElasticsearchDSL;

use ONGR\ElasticsearchDSL\Search as OngrSearch;

/**
 * Class Search
 * @package AcmeBundle\Service\ONGR\ElasticsearchDSL
 */
class Search extends OngrSearch
{
    /**
     * @var bool
     */
    private $trackScores;

    /**
     * @param bool $trackScores
     *
     * @return Search
     */
    public function setTrackScores(bool $trackScores): Search
    {
        $this->trackScores = $trackScores;

        return $this;
    }

    /**
     * {@inheritdoc}
     */
    public function toArray()
    {
        $output = parent::toArray();
        if ($this->trackScores) {
                $output['track_scores'] = $this->trackScores;
        }

        return $output;
    }
}

And FYI, the existing system of our client is still using ES 2.4 and they don't have any plan to upgrade to the new one yet.


github.io compatible output filenames

I would like to publish the code documentation of my project vs-deploy on github.io.
As you can see here, this works fine for the index page.
But if you select a module like contracts, GitHub reports an 404 error (maybe because of the _contracts_.html filename with surrounding _ chars?).
Is there a way to fix that issue by defining a custom pattern for the output filenames, e.g.?

You can create a file called .nojekyll in the root of your repository to prevent GitHub from attempting to use Jekyll (which handles names with underscores differently) and instead have it just serve your content as-is. Note that TypeDoc erases all files in the output directory by default, so you may need to use the disable-output-check flag as I do (which means that you will need to manually delete files that are no longer necessary) or add creation of that file to your build scripts.

Thanks a lot! 👍
Works fine! :D

I build the documentation every time a new version is released (but delete the old docs folder before generating new one). Given Github's popularity, it would be great to have an option to add that file to the output. Just a suggestion. :)

If you're publishing with gh-pages remember the --dotfiles parameter, e.g.
gh-pages --dotfiles -d docs


List of properties where exposed variables region do not accurately reflect the available variables

To confirm the accurate variables, you need to console arguments and open the developer console to see the available variables on the property

DataTable>>>Customise columns>>>Background color: There are two variables available, however the region exposed more
Form Settings>>> On Update: Arguments has 14 variables while the region has 10
Form Settings>>> On DataLoaded: Arguments has 12 variables while the region has 10

I will update the card every time I come across variables that don't match the ones declared on the region


Asciidoctor typo error - manual install minishift and nexus

The nexus install manual contains an asciidoctor syntax error

@cmoulliard Thanks fore catching this:)  Fixed in PR #270

PR merged, closing this issue now.


Multiple issues

Hi,
I recently used this for a project and faced several issues/shortcomings of the repository that can be improved. Here are some of the things:

Ability to auto-populate task fields based on labels found in the dataset and removal of the restriction of the task argument to be one of the standard ones

    parser.add_argument('--task', type=str, default=None, required=True, choices=['ace04', 'ace05', 'scierc'])

Having a --no-cuda argument in run_entity as well to allow users to test code on a machine without CUDA without actually interfering with the code. This is already present in run_relations, but has been skipped in this file for some reason.
Lack of --do_predict, which has already been raised in #30
Some optimisations like

    model = EntityModel(args, num_ner_labels=num_ner_labels)

    dev_data = Dataset(args.dev_data)
    dev_samples, dev_ner = convert_dataset_to_samples(dev_data, args.max_span_length, ner_label2id=ner_label2id, context_window=args.context_window)
    dev_batches = batchify(dev_samples, args.eval_batch_size)

    if args.do_train:
        train_data = Dataset(args.train_data)

All of these lines can be put under the if args.do_train as these are relevant only to that section and the other args.do_eval section already loads the model again like so
    if args.do_eval:
        args.bert_model_dir = args.output_dir
        model = EntityModel(args, num_ner_labels=num_ner_labels)

Other small optimisations and some typos

I am thinking of creating an independent issue for each of these and start working on including some of these fixes/features in the near future as I've already made quite a few changes locally for my project. Just wanted to get your thoughts on these issues and if there is something that I am missing.

Hi, thanks for using our code and raising these issues. All the fixes/optimizations look good to me! You may create individual pull requests for them.
One thing to note is that please make sure the modifications are compatible with the current code, because I do think it is easy for people to reproduce the results in the paper. (e.g., you may add an option for --task to enable automatically collecting labels, and still support --task ace05)


Version 2.2.1, Specific test type get methods return list of that spe…

…cific test type instead of list of Test objects

@snorrefjellvang, could you please have a look at this bug fix? Entail ran into issues using the modeltestSDK


[Feature] Setup a cloud mail services provider (AWS SES)

Setup a new AWS account
Setup SES services
Setup frontend / backend to send transactional mail through it
Setup keycloack to send transactional mail through it

Created - to use the smtp server use the following data (request user/password from me directly):
Server Name:
email-smtp.eu-central-1.amazonaws.com
Port:	25, 465 or 587
Use Transport Layer Security (TLS):	Yes
Authentication:	Your SMTP credentials. See below for more information.

Keycloack configured.
Pending AWS acc approval and this card can be closed.

@miraclebg The AWS account should be working fine by now, correct? If so we might close this one

The account is created and the access details are in MartinK and igoychev


dupload; File by file upload status for faster retry

Store file by file upload status with file timestamps in database like sqlite.

It's need to have feautre. Storing state of each file may cause complexity of alternative conditions.
Just retry whole command just like rsync.
Marked as won't fix.


a

1 account address:
3yhAYkinRKfbW9GiBCdKNPDn2mDqr1BGta6QYMaBsF3JSQJRcy
Submit public data attribute(s) First Name: Maco
2 account address:
3pXo4pRSripLiavP6amD1egZ6tUJfdjhFrX8vvMpshbxhrCYWn
Submit public data attribute(s): First Name : Kaco
Last Name: Kuco
Device and os info: Iphone 7 ıos 14.0.1

pending:ID1
account1:missing-TBC
account2:missing-TBC
We cannot fully verify this submission. Please assist us in typing out the account addresses for ID1 in full as text in a comment on this PR. Thank you!
@kbrrgn

rejected:ID4
reason:We cannot fully verify this submission. It looks like you are trying to submit ID4, however, it seems like we cannot find the transaction between your account and Concordium Test Account.

rejected:ID4
reason:We cannot fully verify this submission. It looks like you are trying to submit ID4, however, it seems like we cannot find the transaction between your account and Concordium Test Account.

pending:T1
account:screenshot-TBC
devicedetails:screenshot-TBC
reason:We cannot fully verify this submission. Please assist us in typing out the account addresses for T1 in full as text in a comment on this PR. Thank you!
@kbrrgn

pending:T1
account:screenshot-TBC
devicedetails:screenshot-TBC
reason:We cannot fully verify this submission. Please assist us in typing out the account addresses for T1 in full as text in a comment on this PR. Thank you!
@kbrrgn

confirmed:ID1
address1:3yhAYkinRKfbW9GiBCdKNPDn2mDqr1BGta6QYMaBsF3JSQJRcy
address2:3pXo4pRSripLiavP6amD1egZ6tUJfdjhFrX8vvMpshbxhrCYWn

confirmed:ID1
address1:3yhAYkinRKfbW9GiBCdKNPDn2mDqr1BGta6QYMaBsF3JSQJRcy
address2:3pXo4pRSripLiavP6amD1egZ6tUJfdjhFrX8vvMpshbxhrCYWn

confirmed:ID2
account1:4QEoT3x4Ja5teG28M7NdyNuCdvzuBm3LXiQ3Frhio1vMXRQ9Nt
account2:3yhAYkinRKfbW9GiBCdKNPDn2mDqr1BGta6QYMaBsF3JSQJRcy
PublicDataAttributes:Verified
DeviceMake&Model:Verified

confirmed:ID2
account1:4QEoT3x4Ja5teG28M7NdyNuCdvzuBm3LXiQ3Frhio1vMXRQ9Nt
account2:3yhAYkinRKfbW9GiBCdKNPDn2mDqr1BGta6QYMaBsF3JSQJRcy
PublicDataAttributes:Verified
DeviceMake&Model:Verified

confirmed:B4
address:46LH78HHfiJAMxGuuQJKSUp7grjWbzMNb4mGe2NVMQWmasiHaU
baker:1041

confirmed:B4
address:46LH78HHfiJAMxGuuQJKSUp7grjWbzMNb4mGe2NVMQWmasiHaU
baker:1041

confirmed:T1
account1:3yhAYkinRKfbW9GiBCdKNPDn2mDqr1BGta6QYMaBsF3JSQJRcy
account2:3pXo4pRSripLiavP6amD1egZ6tUJfdjhFrX8vvMpshbxhrCYWn
DeviceMake&Model:Verified

confirmed:T1
account1:3yhAYkinRKfbW9GiBCdKNPDn2mDqr1BGta6QYMaBsF3JSQJRcy
account2:3pXo4pRSripLiavP6amD1egZ6tUJfdjhFrX8vvMpshbxhrCYWn
DeviceMake&Model:Verified

rejected:B5
address:46LH78HHfiJAMxGuuQJKSUp7grjWbzMNb4mGe2NVMQWmasiHaU
reason: no 'update baker account' or 'update baker key' transactions found on-chain

"Form Submitted"  21:14 TSI


Support for OData

please consider OData support for ASP.NET v5 coreclr or provide reference on how to implement odata services in ASP.NET v5

Agreed, please consider OData supprot with ASP.NET 5

+1

+1

+1

+1

+1

+1

+2

+3

Please, add native support to odata

The odata library & framework should target the .NetStandard1.0 this would as understand it allow odata to the be used by CoreCLR AspNetCore and full framework .NET it may also be good to consider at this time including greater extensibility and dependency injection in the framework.

@apiweb what do you mean by native support ?

+3 (3 dev's in our team) :)

See https://github.com/OData/odata.net/issues/568#issuecomment-230068541

+10

+1

This issue is being closed because it has not been updated in 3 months.
We apologize if this causes any inconvenience. We ask that if you are still encountering this issue, please log a new issue with updated information and we will investigate.


How to access Plaid API using Going.Plaid Nuget?

Could anyone please give a simple example with a fully functional method how can I access Plaid API using this Nuget?
eg- I can simply use below method using Plaid.Net nuget to get Link token. Anything similar to this in Going.Plaid?
public async Task CreateLinkTokenRequest()
{
var client = new PlaidClient(clientId, clientSecret, null, Acklann.Plaid.Environment.Sandbox);
var response = await client.CreateLinkToken(new Acklann.Plaid.Management.CreateLinkTokenRequest
{
ClientName = "Example",
ClientId = clientId,
Secret = clientSecret,
CountryCodes = new string[] { "US" },
Products = new string[] { "auth" },
User = new Acklann.Plaid.Management.CreateLinkTokenRequest.UserInfo
{
ClientUserId = Guid.NewGuid().ToString()
}
});
return response;
}
Please help.

@yogirajshakya  - If you download a copy of the code in this repository and open the code under ~/Tests/Plaid.Demo, you can see a working demo.
The most important thing to know is that the code that handles the actual login to Plaid is done in JS in the browser. Specifically, you will want to read this documentation, which describes how the various tokens are used.
General overview:

The app server (C#) will use the CreateLinkToken() api to get a link token.
The client application (JS) will query the app server for the link token and pass it to the Plaid JS code.
On completion of the login UX, the Plaid JS code will query back to your client application code (JS) with a public token.
Your application code (JS) will send this to the app server (C#)
The app server (C#) will call the ItemPublicTokenExchange() api to exchange the public token for an access token.
The app server (C#) will store the access token in a permanent storage (DB, no-sql db, etc.).
The app server (C#) will use the access token for all other API calls.

@viceroypenguin thanks for the quick response. I read the suggested document also. Still, I have one question how to use the Going.Plaid nuget to get the link token, exchange public token for access token ?
If you can provide the actual code that will be very helpful.
eg- What parameters I need to fill inside new block in below code -
**var client = new PlaidClient(
Going.Plaid.Environment.Sandbox,
secret: clientSecret,
clientId: clientId);
        // Retrieving a user's recent transactions.
        var result = await client.LinkTokenGetAsync(
            new()
            {
               .....
               .....
            });**

@viceroypenguin I already have done the above step. But in case of Plaid.demo, I am having below error when i am trying to run it-

I just simply downloaded the nuget and set Plaid.Demo as start up project and ran it.

The errors seems to related to braces in namespace, but I think that shouldn't be the cause. I am missing something.
Please guide.

@yogirajshakya  Sorry, I didn't realize you had replied. While Plaid itself supports .net standard 2.0 and later, and nearly any version of C#, compiling it requires C# 10, which is supported by .net 6.0 or VS 2022.
You should be able to pull out the Plaid.Demo code and compile it independently of the Plaid source, with a nuget reference to the latest version of Plaid.

@viceroypenguin thanks for the reply.  My response is also delayed as there was Holi festival here.
I tried Going.Plaid with .net 6.0 in VS2019 but got same error. I explored further. Still, I am stucked only in to the second step -
https://plaid.com/docs/link/
"Use the link_token to open Link for your user. In the onSuccess callback, Link will provide a temporary public_token."
I am not getting this how, can I redirect to their local UI Link and get a public token from there.

For that, you should review the JS code in index.cshtml. You will need to reference "https://cdn.plaid.com/link/v2/stable/link-initialize.js" in your html first, and then you need to call
let handler = Plaid.create(configs);
handler.open();

using a configs object you create that includes the link_token and various callback methods. The on_success callback will be called with a public_token on success, so this is what you can send back to your web server to move to step 3.

Let me try this. But what is the "configs" here? And I am not sure how it will work. As per the Plaid documentation, one should need to land on "Link", UI of Plaid to login in your bank account, when your bank credentials are successfully verified, only then Plaid will provide you a public token on on_success callback.

Thanks for the help.


Fix a couple Clippy warnings

Fixes some Clippy warnings in the workspace + examples

Oops, they probably appeared after I merged the PRs today

Thanks!


kmeta package: ChildName function produces invalid resource names

Expected Behavior
When I use ChildName to create a truncated resource name, I expect the name produced to be a valid resource name in kubernetes.
Actual Behavior
The function will produce an invalid resource name ending with .
Steps to Reproduce the Problem
I've set up a go playground example with my input that cause the problem: https://go.dev/play/p/HB42UPAWp7h
Additional Info
This came up as an error in the net-contour controller that looks like this:
{"severity":"ERROR","timestamp":"2022-12-08T19:13:48.437648502Z","logger":"net-contour-controller","caller":"controller/controller.go:566","message":"Reconcile error","commit":"041f9e3","knative.dev/controller":"knative.dev.net-contour.pkg.reconciler.contour.Reconciler","knative.dev/kind":"networking.internal.knative.dev.Ingress","knative.dev/traceid":"ec12c38a-f1ac-4581-aae5-2350b60211a2","knative.dev/key":"cody/foo-java","duration":"18.23483ms","error":"HTTPProxy.projectcontour.io \"foo-java-contour-5f549ae3e6f584a5f33d069a0650c0d8foo-java.cody.\" is invalid: metadata.name: Invalid value: \"foo-java-contour-5f549ae3e6f584a5f33d069a0650c0d8foo-java.cody.\": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')","stacktrace":"knative.dev/pkg/controller.(*Impl).handleErr\n\tknative.dev/pkg@v0.0.0-20221011175852-714b7630a836/controller/controller.go:566\nknative.dev/pkg/controller.(*Impl).processNextWorkItem\n\tknative.dev/pkg@v0.0.0-20221011175852-714b7630a836/controller/controller.go:543\nknative.dev/pkg/controller.(*Impl).RunContext.func3\n\tknative.dev/pkg@v0.0.0-20221011175852-714b7630a836/controller/controller.go:491"}

net-contour uses ChildName here: https://github.com/knative-sandbox/net-contour/blob/main/pkg/reconciler/contour/resources/httpproxy.go#L275

related/dupe of https://github.com/knative/pkg/issues/2551


Create health checks for main website

This is unrelated to #33, which was about the uneducated idea of "health checking DNS records", which is not a thing. Here we're talking about adding actual health checks to the website at www.derploid.com, so that we can be notified if/when the site is down. Additional health checks for the other, "redirect" domains might still be good too, so that we know all of those rules are working correctly.

So yeah, after giving this some more thought, this is how it should all work:

Remember that there are:

2 test "redirect" domains: derploidtest.click, www.derploidtest.click
4 prod "redirect" domains: derploid.net, www.derploid.net, derploid.org, www.derploid.org
1 test "main redirect" domain on the main test apex domain: derploidtest.link
1 prod "main redirect" domain on the main prod apex domain: derploid.com
1 test "main" domain: www.derploidtest.link
1 prod "main" domain: www.derploid.com

Define health checks:

One Route53 health check per domain (10 * $0.50 = $5.00 total)
If all health checks validate HTTPS, that's another 10 * $1 = $10. HTTP health checks would fail for (main) redirect domains if HTTPS redirection were not set up in CloudWatch correctly, so I think we can stick with HTTP for them. The main domains have content hosted by GitHub Pages, using certs that we don't control, so we should still do HTTPS checks on them, for 2 * $1 = $2.
Only health checks for the "main" and "main redirect" domains will measure latency, for 4 *$1 = $4. We don't really care if the other redirect domains are slow, but these domains should both be pretty quick (e.g., many people will type derploid.com directly into browsers, not realizing that it redirects to the www subdomain). And the test domains just have the checks so that the test environment stays as similar as possible to prod.
Only the main domains will validate the actual response, for 2 * $1 = $2. After all, if the main domain in test or prod is unhealthy, then all the other (main) redirect domains in that environment will be too (after CloudFront caches expire). We'll verify the HTML <title> of the home page, as this verifies that we didn't get an error page, and that the Jekyll builds worked correctly.

Define metrics/alarms

Each health check reports a HealthCheckStatus metric (among other metrics), so each will need its own separate CloudWatch Metric in CDK, with its own separate CloudWatch Alarm (since each domain could be separately misconfigured).
Only the main domain HealthCheckStatus alarm in each env will have an action: notify an SNS topic with configured emails, for the case when the main domain is unhealthy but the other domains are still good due to caching. This will alert us to act before all domains are unhealthy.
We will then add two composite alarms per environment:

A UnhealthyWebsiteBreakingRedirects alarm with the rule "main domain unhealthy AND any of the (main) redirect domains unhealthy". This will spare us some alarm noise when the main website goes down: later, when the redirect domain caches expire and they start turning unhealthy, we won't get a new alarm for each domain.
A RedirectDomainUnhealthy alarm with rule "main domain healthy AND any of the (main) redirect domains unhealthy". This will cause the same topic to be triggered by the same alarm anytime a (main) redirect domain is unhealthy

Add CloudWatch metrics and alarms for the main (redirect) domain health checks. Main redirect should have slightly higher threshold than main to account for origin requests during cache misses. Neither alarm in each env should have an action.

Define a composite WebsiteLatencyThresholdExceeded alarm with rule "main domain OR main redirect domain unhealthy". This will cause the same topic to be triggered by the same alarm anytime a main (redirect) domain is taking too long.

FWIW, I also considered these alternatives to Route53 HealthChecks:

CloudWatch Synthetic Canaries: these are automated canaries that call the configured endpoint on a regular schedule. They're very similar to Route53 HealthChecks, but able to validate multiple things per request, or even across multiple requests in a workflow (e.g., for automated UI testing). The additional power comes at a price: the first 100 canary runs per month are free, then its $0.0012 per canary run thereafter. Using the Pricing docs example of an endpoint called every 5 minutes, this would come about to another ~$10. We would probably check the "redirect" domains even less frequently, say once per hour or once per day, but across all (sub)domain checks, this could get pricey. Route53 run more often (every 30 sec max) for a lower price ($0.50 per health check per month + $1 per "optional" feature per month).
Defining Lambda Functions to call our endpoints regularly. This would give us the most power, and might even be the cheapest option, but would also require the most complexity and tedium to set up. Each Lambda Function would need to call an endpoint, check the HTTP status code, check the response body, parse it for particular strings, and send metrics to CloudWatch. This would also involve using CDK assets for the Lambda code, which I'm not really ready to learn about just for this use case, and things would get even more complicated to measure latency and other metrics that Route53 health checks already provide out of the box.


issue in Release 1.5 Landscape Mode on orientation changed from minimised state.

Hi Pedrovgs,Fiddl3,
I am facing this wierd issue. For the first time when i  change the device orientation from portrait to landscape, Top view resizes properly and everything works fine.
However when i minimise it once and then changes orientation, The width of Topview reduces to half. Also next time if i change the orientation from maximized portrait mode, it still shows me the half video view.
What modifications changes do i need to do for Release 5 ,because it was working fine in Release 1.2 and post it i updated it directly to R5.

Do you have the screenshot?


Add additional settings info in azure_sql_server for azure defender.

Is your feature request related to a problem? Please describe.
In the current state, we are able to find the Azure Defender setting for required services at the subscription level. However, some compliance requirements need this validation for each resource level.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context

There is no direct api which will provide us the defender setting details, need more investigation on it.


Pangolin mobile but remastered application launchers

Ight, so do not merge, do not, do not. I just wanna put up stuff that isn't done n'd whatever.
The plan is to basically make is so that both pangolin versions, mobile and desktop use the exact same apps. This is for convergence and so we only have to worry about maintaining ONE version of all the apps rather than having to patch other ones to work for mobile.

I'm doing some shid lol


The availability of Azure Monitor logs is not clear

One paragraph says

The following functionality found in the managed gateways is not available in the self-hosted gateways:

Azure Monitor logs

another one

A self-hosted gateway uses connectivity to Azure for:  [...]

Sending request logs and metrics to Azure Monitor, if configured to do so

Please clarify.

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

ID: 20dccd8b-f67a-8728-3bb3-f46a0ffdfd40
Version Independent ID: 3e79e57d-a348-b0d3-cd89-86c76ca70104
Content: Self-hosted gateway overview
Content Source: articles/api-management/self-hosted-gateway-overview.md
Service: api-management
GitHub Login: @dlepow
Microsoft Alias: danlep

Thank you for your feedback! We will review and update as appropriate.

Duplicate of https://github.com/MicrosoftDocs/azure-docs/issues/55956
#reassign: @dlepow


hello ,about the rtsp setup command

I have an extra camera device.
The device has a wifi hotspot.
send the rtsp command.   sendOptionsCommand is OK sendDescribeCommand is OK but sendSetupCommand is FAIL.
however i can use VLC to live feed my camera .
i need your help.

Most probably issue is fixed in this commit in 5.1.2.
Please check it at let me know.


Big integer returned +1.

So I'm doing a query to my database but for some reason, the returned data is higher than the actual data on the mysql server.
Picture

Hi @lluiscab this is a limitation of JavaScript itself: it cannot represent big numbers. You can try it yourself by even trying to console.log a number you typed in manually:
$ node -e 'console.log(147798296306515969)'
147798296306515970

This modules provides a bunch of connection options to help deal with big numbers when you need to, by either allowing you to get the numbers back as strings or as objects from the bignumber.js library.
See the https://github.com/mysqljs/mysql#connection-options for more information :)


Please fix force toggle visible player again

Expected behavior
Shown enemy
Observed/Actual behavior
I was played MLGRush, BedFight, Sumo, PearlFight, Spleef and i can't see enemy
And i got it only one on server other player don't get this
idk why
How to Recreate (if known)
No response
Stack trace
Don't have
Plugin list

Frost version

Agreements

[X] I have searched for and ensured there isn't already an open issue regarding this.

Other
No response

This has been already fixed, the update hasn't been released yet.


add code coverage information

2d0182d0527bd767ef47a151ff540ad5ee1d0367
Looks like the code coverage information made it to sonarcloud (for master branch only at the moment)


External links and mailto: are not working

In my app,
Google.com
<a<EMAIL_ADDRESS>
Above 2 line of code is not working, while clicking links are not responding, any alternate code for that links ??

It is unlikely for the above 2 lines to not work due to framework issues, anyway can you provide some more info? A jsbin or similar would be great,


Multiple controls at same row

[ ] bug

[x] enhancement

[x] question

CakePHP Version: 3.6.

Plugin Version/Branch: dev-4.0.1-alpha.

Any chance to implement multiple controls within same row at forms (similar to https://getbootstrap.com/docs/4.1/components/forms/#form-row) with current version?

This is similar to #70 (old one... ) but with Bootstrap 4. I am currently lacking time to implement new features, but a quick workaround would be to alter the correct template:
// Update the inputContainer template.
$this->Form->setTemplate('inputContainer', '
{{content}}
');

// Open the form-row div manually.
echo '
';

// Output your controls:
echo $this->Form->control(...);
echo $this->Form->control(...);

echo '
';

// Reset the template
$this->Form->setTemplate('inputContainer', '
{{content}}
');


[BUG]: muted not working on Android 12/13 for Samsung and Pixel devices

Version
6.5.0
What platforms are you having the problem on?
Android
System Version
Android 13
On what device are you experiencing the issue?
Real device
Architecture
Old architecture
What happened?
muted video still play audio when loaded on Samsung/Pixel devices with Android 12 or 13; please note that we have attempted to load the same video on other devices like Huawei/Xiaomi/oppo with similar Android version and they work fine in them.
we have applied a workaround with selectedAudioTrack={{type: SelectedTrackType.DISABLED}} configuration, it isn't ideal, but it works for us.
Reproduction Link
No response
Reproduction
Step to reproduce this bug are:

Load a muted video on Samsung/Pixel devices with Android 12 or 13
Notice video still play audio when loaded

https://developer.android.com/reference/kotlin/androidx/media3/common/Player#setVolume(float) currently we don't check if volume control is available ... I think you have a correct workaround.
media3 volume apis are handling volume on player side and it can be disturbing for end user to have 2 parrallel volume management. I can advise to use something like : https://www.npmjs.com/package/react-native-volume-manager to handle volume of the device, not one the player

I don't reproduce the issue with emulator. It would be interesting to test following patch to see if the log is displayed !
diff --git a/android/src/main/java/com/brentvatne/exoplayer/ReactExoplayerView.java b/android/src/main/java/com/brentvatne/exoplayer/ReactExoplayerView.java
index 0714115e..62055c9d 100644
--- a/android/src/main/java/com/brentvatne/exoplayer/ReactExoplayerView.java
+++ b/android/src/main/java/com/brentvatne/exoplayer/ReactExoplayerView.java
@@ -2133,7 +2133,12 @@ public class ReactExoplayerView extends FrameLayout implements
     public void setMutedModifier(boolean muted) {
         this.muted = muted;
         if (player != null) {
-            player.setVolume(muted ? 0.f : audioVolume);
+            Player.Commands cmd = player.getAvailableCommands();
+            if (cmd.contains(Player.COMMAND_SET_VOLUME)) {
+                player.setVolume(muted ? 0.f : audioVolume);
+            } else {
+                DebugLog.e(TAG, "player doesn't support volume management");
+            }
         }
     }


"--acknodelay false" not working

with latest windows client, "--acknodelay false" seems invalid, while "--acknodelay=false" is ok

Merged


drivers: adxl362: fix control flow issue

The return code check and error return on the interrupt register configuration function should be included in the #if defined region.
Fixes #16159.

Added "Fixes #16159" to commit message.


Transition to new server and library code

After settling on a single codebase in #1071, and the release of zipkin-java 1.0, we have some consolidation steps to take. These include at least the following:

Determine how to migrate the zipkin-java code into this repository, whether or not we preserve history from zipkin-java.
Decide what to do with packages (ex. zipkin-java is under the group id io.zipkin.java at the moment)
break out issues to consolidate docker and decomission other repos.

An alternative discussed was to rename this repo and archive it. While simpler mechanics, this was initially thrown out as this repo has a lot of followers. Moreover, it is unclear if you can rename a repo to to archive-X, then have a different repo become X.

so here's an idea. Right now, the only code that's needed and not in zipkin-java is zipkin-ui.
Preparation: move zipkin-ui to zipkin-java and stop development here
Regardless, first step we should take is move zipkin-ui to zipkin-java and stop affecting master here:

Merge pull requests and cut a final release of zipkin-ui here
Migrate zipkin-ui to zipkin-java repo (via git filter-branch  and friends to preserve history)

implies converting the build script to the maven alternative

cut zipkin-ui from the zipkin-java repo

At this point, everything is in sync and we have a couple options to proceed.
Option 1: shuffle repository names
The simplest option would be to rename zipkin to something else (zipkin-scala or zipkin-legacy) and then rename zipkin-java to zipkin.
Pros

no chance to screw up forks (they basically can continue off master and/or be abandoned)
irrelevant issues and old pull requests aren't imported to the new codebase
current issues in zipkin-java are retained

Cons

Not sure if the rename shuffle will work or not. Ex can you rename a github repository to a historical name of another?
Some issues like UI ones, or the new model will need to be recreated
zipkin-java has less stars and watchers.

These would need to be organically regrown

zipkin-java has less collaborators.

Folks who've done historical work in zipkin won't show up in the commit log until they do more work.

Option 2: git-fu
A more drastic approach would be to rewrite master here with the java codebase, then turn off zipkin-java
Pros

zipkin stars, watchers, and collaborator stats remain in place
issues that don't relate to the scala implementation don't need to be recreated.

Basically search is irrelevant

The more I think about it, the less I like option 2. I feel it disrupts both sides with technical gotchas. While I do like the idea of memorializing past contributions and stars, I hope we've made a project that people will star again, and contribute to again. I'll certainly continue to contribute effort to the socializing of zipkin such that stars might be reborn faster.

cc'ing people who've contributed code in the last month to either repo:

zipkin(-scala): @NegatioN @esbie @yurishkuro
zipkin-java: @sveinnfannar @dsyer @abesto @eirslett @michaelsembwever

what about moving scala code to a branch in zipkin repo?  If people have forks which are reasonable up to date, can they just rebase from the scala branch?

How would moving the scala code into a branch help with the problems of
lost stars etc? If anything, it would seem to confuse the fact that it is
not a supported codebase anymore.

I meant as a flavor of option 2, i.e. consolidate both java and scala impls in zipkin repo, in master and scala branches respectively. It may address the first con (with rebase), but not the second.
The second con is a bit questionable, as there may be many things in closed issues that shed light as to why certain things are done one way or another, especially if java impl just copied the original logic. But I hardly ever used search on the old issues/PRs, so I'm not the right person to judge that.

ah ok. Makes more sense now.

The second con is a bit questionable, as there may be many things in
closed issues that shed light as to why certain things are done one way or
another, especially if java impl just copied the original logic. But I
hardly ever used search on the old issues/PRs, so I'm not the right person
to judge that.

I might be a decent person to judge having participated in most issues in
both repos in the last year (as well rewriting the code).
There's well over 1000 issues in the old repo, and quite many pertain to
specifics of finagle, scrooge, sbt, gradle, etc. The code and log in the
zipkin-java repo is far better documented than the old ones, and the pull
request and commit descriptions etc are far more elaborate, too. While
there are some good issues in the old repo, the majority are not going to
ease understanding of the new codebase. If given a choice, I'd stick with
the ones that directly caused the current codebase.

I'm voting for yurish's solution! The variant of 2.

I'm OK with either, especially as either path is towards the end of tasks such as this :p
So to be clear, the git-fu would be something like this..
# after git tag 1.40.2 is pushed and released.. we have a cease-fire on the repo

# First, from zipkin repo, rename master to scala or something
$ git checkout -b scala master
$ git push -u origin scala
$ git branch -d master
$ git push --delete origin master
$ git remote prune origin

# Now, from zipkin-java repo, push master to the zipkin repo
$ git remote add zipkin https://github.com/openzipkin/zipkin.git
$ git push zipkin master

# Next, from the zipkin repo, fix travis credentials and cut a patch release to test it

@gregwhitaker @anuraaga fyi, if we take option 2, you'd need to rebase your forks off a different repo (even though master will end up with the same code as zipkin-java)

mildly revised the option 2 desc to include the master rename

Ps something I didn't mention earlier is a pro in-favor of option 2 is that
the UI issues are retained. Since the code is the same, this is helpful.
Also, I thought of a way to balance the problem of losing zipkin-java's
issues. There are probably less than 10 with lots of comments. Maybe we can
harvest the comments into a doc or something.

We can delete all the code from the zipkin-java and leave only a readme. Then we keep the issues. And we leave it in that state for a couple of months. We make a single "first commit" commit and force push it to the master branch, which will wipe the git history, so that it's not possible to merge or pull/push to it inadvertently.

There are also some open source scripts written to automate github issue moving. It won't replace author/timestamps/metadata, but put that in the issue texts.

Thanks. Will add it to the plan. If I don't hear strongly otherwise, we'll
go with option 2.

here's some related work in docker land, basically renaming the java image to "zipkin" as it doesn't need qualification since it includes collector and query functionality https://github.com/openzipkin/docker-zipkin-java/pull/9

I'm starting this stuff now

Executed the following:
# First, from zipkin repo, rename master to scala
$ git branch -m master scala
$ git push origin scala

# Now, from zipkin-java repo, push master to the zipkin repo
$ git remote add zipkin https://github.com/openzipkin/zipkin.git
$ git push -f zipkin master

verified master looks alright and scala branch is in-tact
https://github.com/openzipkin/zipkin
https://github.com/openzipkin/zipkin/tree/scala

renamed the old bintray repository to zipkin-archived so that we don't accidentally overwrite versions

renamed the bintray repository zipkin-java to zipkin

updated the travis things and links https://github.com/openzipkin/zipkin/commit/2b50556dbb940d39fb6b4ae6dfc04a1c042ad143

moved release tags for 1.0.0 and 1.1.0 and backfilled release notes

@gregwhitaker @anuraaga note! what was zipkin-java is now here. please update your refs accordingly

created a branch on zipkin-java called cutover and force pushed a README that redirects here

done!


AbstractMethodError when using JSON log encoder

Specifically java.lang.AbstractMethodError: net.logstash.logback.encoder.LogstashEncoder.headerBytes()[B. Upgrading "net.logstash.logback" % "logstash-logback-encoder" from 4.8 to 4.11 fixes this issue.

Thanks! Spent 2 days trying to figure out why logback was crashing with this error. Upgrading logstash to 4.11 fixed the problem.


about ERB band

Hello, Mr. Noh
I found that PercepNet used triangular filter in ERB band, and you already caught that point and modified your repo.
(I found this when I read the paper on Personalized PercepNet. In section 2, the author said that they used triangular filters in PercepNet.)
I think that we can get values of ERB subbands from the figure in this post:
https://www.amazon.science/blog/how-amazon-chimes-challenge-winning-noise-cancellation-works
My estimation is :
eband5ms[33] = {2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 23, 26, 29, 33, 37, 41, 46, 52, 58, 64, 71, 81, 91, 103, 117, 133, 154, 177, 206, 241, 283, 336, 400}
In this array, 1 means 50Hz. It can be slightly different from the truth, but it may work properly.
I started from two assumptions to get this array.

I think that each subband is a multiple of 50Hz : You can guess this fact from the implementation of bark scale in RNNoise. He used slightly different version of bark scale so every subband is a multiple of 50Hz and every triangular filter has min/max on borders of subbands.

Every subband is at least 100Hz, to avoid containing just single frequency bin.

Finally, I counted some dots for one hour and got this values. (from 0 to 5000Hz, there are about 280 dots)
I hope that it can help you.
Regards,
Jaeyoung

Hi, Jaeyoung
I've checked the ERB band and your second assumption was not applied before
now I changed it and the result is also similar to yours.
[0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 31, 36, 41, 48, 56, 65, 75, 86, 99, 115, 132, 152, 175, 201, 230, 265, 304, 349, 400]
your second assumption is applied to erbband.h L71~75, had error before now I fixed it.
         //impose mininum 100hz(2 nfft)
          for(int k=0; k<N; k++){
            if(nfftborder[k+1]-nfftborder[k]<2)
              nfftborder[k+1]+=(2-(nfftborder[k+1]-nfftborder[k]));
          }

I'm currently using erb_band->nfftborder instead which is automatically generated by erbband class initializer, In this repo, eband5ms is not used anymore
Thank you for your estimation that makes it easy to find an error and fix it.


cabana: refactor and improve signal view

refactor to use standard TreeView/Model architecture, with many new features and bug fixes:

dark theme:

light theme:

Like the tree structure a lot! Will make it much easier to add multiplexed signals (https://pisnoop.s3.amazonaws.com/snoop_help_dbc.htm, https://github.com/commaai/opendbc/blob/master/vw_golf_mk4.dbc#L1412)

Can we make the fields' height similar to before? I feel like it's a little hard to click around and edit fields now

It uses the system default height. how about keep it as it for now? we can change it later if really need.

Since we can use the keyboard to navigate the tree view and expand stuff, it would be nice if Enter allowed you to edit stuff/toggle check boxes! Doesn't need to be in this PR

Since we can use the keyboard to navigate the tree view and expand stuff, it would be nice if Enter allowed you to edit stuff/toggle check boxes! Doesn't need to be in this PR. Is this PR good to go?

qt use F2 to trigger the editor: https://doc.qt.io/qt-5/qtreeview.html#key-bindings
we can improve the key bindings in another pr.I think this pr is ok to be merged

Just a suggestion, and might be better to do in a different PR. Is it possible to show the latest signal value next to the signal name? Switching back and forth between the logs can be a bit annoying.

it should be easy to show signal value in column 1 by emit mode->dataChange (signal name is col 0).
maybe add a helper function in util.h to reuse it in log model and signal model to read the signal values.
I think about how to make it cleaner

@pd0wm  added in de81678
Kazam_screencast_00066.webm

added a splitter between signal view & binary view:
Kazam_screencast_00067.webm

Since we can use the keyboard to navigate the tree view and expand stuff, it would be nice if Enter allowed you to edit stuff/toggle check boxes! Doesn't need to be in this PR. Is this PR good to go?

@sshane I think this PR is ok for merge after de81678. the new added code is worth it. although it may introduce some new issues, it should be easy to fix.

Looks so much better :)
Would be nice if the position of the divider between the bytes and signal list stayed in place when opening new signals. With CAN-FD you end up constantly making the bytes view larger.


Alarm Enhancements

1.) It would be great to be able to toggle the smart alarm status directly from the watch.
Or/And
Be able to  to specify the days the alarm is active. . .
2.) Can we have the snooze data points added to the log as well?

Can do this now.
Hmm. Good point. I was thinking of charging a small fee per snooze... :-)

Lol. It has been long enough that I don't remember the request. Charging for a snooze would solve the snooze habit, lol.

On May 27, 2015, at 4:08 PM, JamesFowler42<EMAIL_ADDRESS>wrote:

Can do this now.
Hmm. Good point. I was thinking of charging a small fee per snooze... :-)

—
Reply to this email directly or view it on GitHub.


 Could you also update the lib's patch version at the top of the file?

Sorry for the delayed response. I've updated the patch number and fixed up the unit tests as requested.
I can see that tests are still failing to run at the moment, but unless I'm mistaken that issue looks unrelated to the code being changed. Unit and integration tests are passing when run locally, for what it's worth.
Please let me know if you want me to make any further changes or look more closely at those failures!

Excellent, thanks. I'll fix up the unit tests (latest ops, which is 2.0.0+, we're explicitly fetching latest main) only works on Python 3.8+ now, so I'll remove those older Python versions from CI and add newer ones. Not sure what the deal is with integration tests, may be the same issue, but I'll look into it.

The integration test failure is due to flappy test that relies on logs - I've seen this before, we probably need to think a bit harder about that test, but it shouldn't block this PR :)

@jsimpso Can you please allow me to push to your branch/fork? I've got a couple of commits to add to fix the tests. Alternatively apply these two patches yourself:

0001-Only-run-CI-on-Python-3.8-and-3.10-like-ops.patch.txt
0002-Fix-test-that-breaks-when-local-timezone-is-not-UTC.patch.txt

@jnsgruk Could you please update your review? I've opened a separate issue on the integration tests logging issue (not related to this PR): https://github.com/canonical/operator-libs-linux/issues/65


fix: Removed irregular spacing (#1194)

This PR is created fixing the spacing issue introduced while adding the filter to locate columns. As discussed in #1194 I have fixed the issue and the UI now looks like the screenshot below.

Hi @g-kabra,
It looks great to me, but as we released yesterday v4.0.0 there are some conflicts with the PR.
Could you please rebase?
Thanks!

Okay, I'll try rebasing.

Hey @aquemy ! Sorry for the delay, was caught up in some other work.

Codecov Report
Base: 90.32% // Head: 90.33% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (cf62954) compared to base (31d11ba).
Patch coverage: 97.36% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1252      +/-   ##
===========================================
+ Coverage    90.32%   90.33%   +0.01%
===========================================
  Files          185      185
  Lines         5696     5693       -3
===========================================
- Hits          5145     5143       -2
+ Misses         551      550       -1

Flag
Coverage Δ

py3.8-ubuntu-latest-pandas
90.33% <97.36%> (+0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

setup.py
0.00% <0.00%> (ø)

...rc/ydata_profiling/model/expectation_algorithms.py
100.00% <ø> (ø)

.../ydata_profiling/model/pandas/discretize_pandas.py
100.00% <ø> (ø)

...c/ydata_profiling/model/pandas/imbalance_pandas.py
100.00% <ø> (ø)

src/ydata_profiling/model/pandas/utils_pandas.py
93.75% <ø> (ø)

src/ydata_profiling/report/formatters.py
80.00% <ø> (ø)

...a_profiling/report/presentation/core/renderable.py
92.85% <ø> (ø)

...iling/report/presentation/frequency_table_utils.py
94.87% <ø> (ø)

src/ydata_profiling/utils/common.py
52.50% <ø> (ø)

src/ydata_profiling/utils/compat.py
100.00% <ø> (ø)

... and 120 more

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

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


Missing bits from docs

Folllowing comments in gh-32.
The following sections need adding or filling out in docs:

[ ] README
[ ] Frontpage: features and requirements.
[ ] Usage section.
[ ] Dev section in docs
[ ] Overview of core types showing relation between classes.
[ ] Also add an overview of simplecas and explain what its purpose is.
[ ] TreeExpr.children replace dummy docstring.
[ ] ForwardGraph add a good docstring with diagrams.

(Feel free to edit/add to the list)

The main thing we need right now is to fill out the docs main page / project README to explain what the project is and what the plans for it are.

I would like to help on this, can you share some reference materials if possible or guidance to understand the repository.


Add ability to change Custom Editor title

The webview API allows setting a title programmatically, this is also desirable for custom editors that need to use a friendlier name for the resource being edited.
The webview API doesn't cover our use case since it doesn't provide the correct save/close behavior that an editor does.

Can you provide more information about your use case? If you are using virtual files, can you update the file name instead?

Use case:
The editor is part of an extension that allow editing certain files within a webview custom table editor, the files themselves have the same name, but reside in different sub directories. The actual name and path of such a file is irrelevant - the extension determines a "friendly" name for each editor.

We have similar use cases: the custom editor could edit more than one file in the webview, but the title of the custom editor is always the file which is opened by the custom editor. We want to control the lifecycle of the editor, such as undo/redo and save, so the custom editor is a good solution.

If you are using virtual files, can you update the file name instead?

I tried the virtual document, it seems the virtual document can't stay in the unsaved state that we want to keep our editor in to tell the user he has unsaved changes.

We also have another use-case:
The file itself is a json containing the configuration and the custom texteditor will render the configuration view.  The filename will have remain the same so that they layout will remain unchange when vscode is restored.  However, the content of the json file will change with time and the title to provide a "summary" overall of the configuration to the user at a glance.
Thus, the ability to change the title of customTextEditor will be benefical in term of design user-friendly perspective.

@mjbvz ,
https://github.com/microsoft/vscode/issues/160543,
My use case: I am opening custom editors based on cursor position from where we are invoking custom editor creation(invoking from context menu).
A single file can have N number of custom editors but all will have same name as file name. But I want to differentiate these editors with name/title. Custom editors are unique as I will update file URI's query parameter based on cursor position.

Hi folks 👋 — I've had feedback building Triplex for VS Code that it's very easy to lose track of the custom editor as generally both the source code and editor are used in tandem. So when having multiple files / editors open it's very easy to lose them.

Being able to change the title / icon of the custom editor would help reduce this pain point.

I am adding native CPU/memory profiling support to tests for Go. I am implementing this via a read-only custom editor. I want the title to be "{cpu|memory} profile ({test item})", possibly including the time of the capture. Due to filename restrictions (especially on Windows), I would have to make it much less readable to safely include that info in the filename.


feat: update ansible collection

feat: update ansible collection
feat(docker_compose): add role

@CodiumAI-Agent /review

PR Review

 ⏱ Estimated effort to review [1-5]
4, due to the extensive changes across multiple files, including workflows, roles, molecule tests, and configuration files. The PR introduces new functionality, modifies existing workflows, and adds new roles with molecule tests, which requires a thorough review to ensure compatibility and adherence to best practices.

 🧪 Relevant tests
Yes

 🔍 Possible issues

Possible Bug: The removal of the entire .github/workflows/ansible-galaxy.yml might unintentionally remove the capability to deploy to Ansible Galaxy upon tagging. If this functionality is intended to be replaced or moved, it should be clearly documented or implemented in another part of the workflow.

Best Practice: The roles/docker/tasks/main.yml uses a fixed cache validity time for the apt cache. This might not be optimal in all scenarios and could benefit from being configurable.
 🔒 Security concerns
No

 Code feedback:
relevant file.github/workflows/main.yml
suggestion

Consider adding a failure condition or notification for the 'Deploy to Ansible Galaxy' job. This can help in quickly identifying deployment issues. [important]

relevant linedeploy:
relevant fileroles/docker/tasks/main.yml
suggestion

Make the cache_valid_time for apt cache in the Docker role configurable to provide more flexibility. [medium]

relevant linecache_valid_time: 3600 # 1h
relevant fileroles/docker_compose/molecule/docker_compose/converge.yml
suggestion

Add a task to ensure the Docker service is running before deploying Docker Compose projects. This ensures the Docker daemon is available and can prevent deployment failures. [important]

relevant line- name: Deploy Docker App
relevant filepyproject.toml
suggestion

Update the pytest and pytest-ansible dependencies to their latest versions to ensure compatibility with the latest features and fixes. [medium]

relevant linepytest = "^8.1.1"

 ✨ Review tool usage guide:
Overview:
The review tool scans the PR code changes, and generates a PR review. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.
When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:
/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:
[pr_reviewer]
some_config1=...
some_config2=...

  Utilizing extra instructions
The review tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project.
Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize.
Examples for extra instructions:
[pr_reviewer] # /review #
extra_instructions="""
In the 'possible issues' section, emphasize the following:
- Does the code logic cover relevant edge cases?
- Is the code logic clear and easy to understand?
- Is the code logic efficient?
...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

  How to enable\disable automation

When you first install PR-Agent app, the default mode for the review tool is:

pr_commands = ["/review", ...]

meaning the review tool will run automatically on every PR, with the default configuration.
Edit this field to enable/disable the tool, or to change the used configurations

  Auto-labels
The review tool can auto-generate two specific types of labels for a PR:

a possible security issue label, that detects possible security issues (enable_review_labels_security flag)
a Review effort [1-5]: x label, where x is the estimated effort to review the PR (enable_review_labels_effort flag)

  Extra sub-tools
The review tool provides a collection of possible feedbacks about a PR.
It is recommended to review the possible options, and choose the ones relevant for your use case.
Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example:
require_score_review, require_soc2_ticket, require_can_be_split_review, and more.

  Auto-approve PRs
By invoking:
/review auto_approve

The tool will automatically approve the PR, and add a comment with the approval.
To ensure safety, the auto-approval feature is disabled by default. To enable auto-approval, you need to actively set in a pre-defined configuration file the following:
[pr_reviewer]
enable_auto_approval = true

(this specific flag cannot be set with a command line argument, only in the configuration file, committed to the repository)
You can also enable auto-approval only if the PR meets certain requirements, such as that the estimated_review_effort is equal or below a certain threshold, by adjusting the flag:
[pr_reviewer]
maximal_review_effort = 5

  More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs 💎: Generate docstring for new components introduced in the PR.
/generate_labels 💎: Generate labels for the PR based on the PR's contents.
/analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the review usage page for a comprehensive guide on using this tool.


Remove PATCH use

Not working at the moment, the ActivityPub service should be refactored to add immediately collections.

Replaced with #32


[IOTDB-1233] Support SQL of aligned timeseries and schema template

Support SQL of aligned timeseries and schema template.
For more details, please refer to: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=181307906

Coverage increased (+0.1%) to 67.103% when pulling b12b808b537892a3f6407c44c02b68c6072e1841 on liuminghui233:vector_sql into 0eeb0ce4aed2f203825689e0ce5abd1e1122c716 on apache:master.


compile: optimize a+b statically for literal string/list/tuple

Previously, the parser would fold two string literals "a"+"b" into a
fake string literal, to avoid quadratic runtime cost when a long chain
of strings is added (as often happens due to line length limits).
This made the syntax tree unfaithful to the source,
preventing the frontend from being used in a reformatting tool.
This change does the same optimization in the compiler,
and generalizes it to list and tuple expressions too:
"a  b" + "c  d" => "a  bc  d"
[a, b] + [c, d] => [a, b, c, d]
(a, b) + (c, d) => (a, b, c, d)
It also creates the seam for later addition of the "accumulator"
optimization, in which n-ary non-literal additions such as a+b+c are
optimized to:
acc = start(a)
acc.add(b)
acc.add(c)
acc.done()
I evaluated this optimization but it doesn't yet pull its weight
on the kinds of builds I can do so far.

cc: @laurentlb


Update Dockerfile to remove software-properties-common

See https://github.com/Senzing/senzing-api-server/issues/401

Pull requests:

https://github.com/Senzing/init-postgresql/pull/36


isUrl should reject on unicode chars

validator.isURL('http://mixmax.com\u8203') should return false. \u8203 is a unicode zero-width space.

It should technically reject on invalid URL chars, so: !/^[A-Za-z0-9\-\.\_\~\:\/\?\#\[\]\@\!\$\&\\\'\(\)\*\+\,\;\=%]+$/.test(url).
Are you open to a PR?

The URL is valid. See https://en.wikipedia.org/wiki/Internationalized_domain_name
In this case, the URL validator parses com\u8203 as the TLD and checks whether it contains allowed characters (https://github.com/chriso/validator.js/blob/0882fa4694db91d914e05ccf93f8c42d1a4212f7/lib/isFQDN.js#L35-37).
Here's what the TLD looks like when encoded with IDNA:
>>> u'com\u8203'.encode('idna')
'xn--com-ij2i'

So http://mixmax.com\u8203 is a valid URL (http://mixmax.xn--com-ij2i).
Whether or not the TLD exists and the URL resolves is outside the scope of the library.

The URL validator is not completely standards compliant. It currently allows through characters in the range \u00a1-\uffff, however IDNA2008 dropped support for a large chunk of these characters (see https://tools.ietf.org/html/rfc5892#section-0135). Adding them all would significantly increase the size and complexity of the library.


Unable to run

$ swift run CounterExample
error: terminated(1): /usr/bin/xcrun --sdk macosx --show-sdk-platform-path output:
    xcrun: error: unable to lookup item 'PlatformPath' from command line tools installation
    xcrun: error: unable to lookup item 'PlatformPath' in SDK '/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk'

my OS is MacOS
I have installed xcode-select --install and gtk4 via brew install gtk4

What's the output of xcode-select --print-path? This looks like a configuration issue to me.
One option (which may not be necessary if you can get the command line tools working) would be to install Xcode if you have the space/time available to do that.

$ xcode-select --print-path
/Library/Developer/CommandLineTools

I have Xcode installed
I have everything up to date - macOS, App Store apps, and Brew apps
I have almost no configuration on this system, this Mac is like a week old since the factory reset

Thanks a lot, it worked!

I have left a star for your help

Awesome 👍 don’t hesitate to let me know if you face any other issues or find features you need/want added


delivery problem?

Today I have experienced delivery issues, maybe it's just a false alarm, a problem inside the hub, but I've noticed a grid (timeline) overly calm in the last few hours, in 2/3 different channels, maybe someone else might have the same problems (after the upgrade).
In any case, the delivery reports of those posts always give me "no result"...
and redeliver does not work , always "no result".

news:
now I can see  the posts (from yesterday) in my main channel ( network-grid) ;)
..but if I enter in that channel I got again "no result" in delivery report for those posts.
strange behavior.

Doing little experiments:
I've created a post just for some people, and it works fine ;-) .
The problem is when I make a public post. Someone or something blocks the delivery.
I do not use gnusocial protocol, but i have a gnusocial follower , so i deleted the follower, but the problem continues ..
Now I have noticed followers with serious 'certification issues' or similar things in their hubs, maybe I try to get rid of them and see what's happening.
I start to be convinced that some of these are blocking delivery, if so then we all could have serious problems.

Another strange thing:
after the cloning I got one more contact ( in the main channel  I had x contacts and in the clone x+1)..
is<EMAIL_ADDRESS>the +1 connection (rex@manhut has a strange configuration comparing with others hubzilla channels)
So I deleted this contact from my connections in the clone,  and now  I have the same connections.
After the upgrade of the hub the problem continues ( bad delivery report and a giant delay for public posts), just with this channel, and just with public posts ( not public works well ;) ) , and the other channels in the hub  work well too..and also the clone  with  same connections works well (so now  I don't know what's the real cause of the problem in the main :-( ).

Any chance you have the nofed plugin enabled on one site and not the other? Otherwise unless you get lucky and discover something to go on it's very difficult to fix this without logs.

'Any chance you have the nofed plugin enabled on one site and not the other?'
the other channels in that hub ( hub with  problematic channel) work well. (ps: also the channels in the other hub  work well).
Maybe in the main channel the connection<EMAIL_ADDRESS>is still there (this explains why after the cloning he appeared in the list of connections of the clone), but I can not see him, is like a ghost channel, and maybe this causes the delivery problem.(and the bad report).
I've already talked to the admin, but he said he did not see anything strange in the logs. Maybe  he can look again.
Of course the problem is relative, because the clone works well, and I use the clone ;-) , in any case is a new problem, and it would be nice to find out the cause.

the constant continues to be : 'no result'  in delivery report.
I just found that the channel with the problem is in a hub with MariaDB.

Just in case this matters - I discovered my channel was not delivering for several weeks; it turned out to be that the phppath in .htconfig.php was set to a 5.5 version of PHP; and we're now using a lot of 5.6 features in the code. At first this didn't prevent delivery but eventually enough of these changes went in that the delivery daemons started failing.
Execute the version of php in config['system']['phppath'] from the command line with the -v flag and make sure it's running at least 5.6 and preferably 7.0 or greater.

but it affects all the channels in the hub? because the other channels do not have this 'delivery problem', it seems that just ONE channel has this problem in the hub.

I don't know what happened in  the parlementum hub  but it seems that now that channel works well, no more delivery problem (testing today).


generateUsageHint feature

It would be nice if generateUsageHint would be aware of the flags used to generate the environment variables and include them in the generateUsageHint.
Example of current functionality:
$ docker-machine env --swarm swarm-master
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://<IP_ADDRESS>:3376"
export DOCKER_CERT_PATH="/Users/brint/.docker/machine/machines/swarm-master"
export DOCKER_MACHINE_NAME="swarm-master"
# Run this command to configure your shell:
# eval "$(docker-machine env swarm-master)"

The desired outcome would be to have the eval line reflect the command we ran:
# eval "$(docker-machine env --swarm swarm-master)"

This is a "nice to have".

Fixed by https://github.com/docker/machine/pull/2084


[Request for External] Page 490 Acc. Schedule Overview - request protected vars: NewCurrentSchedName + NewCurrentColumnName

Dear ALAppExtensions,
We would like to request the following vars as protected:
    var
        NewCurrentSchedName: Code[10];
        NewCurrentColumnName: Code[10];

Thank you,
SR

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 52844.


string_types not needed anymore in mkdocs 1.1

See https://github.com/mkdocs/mkdocs/blob/1.0.4/mkdocs/utils/init.py
MkDocs 1.1 dropped support for python 2, supporting only 3.5+.
We could remove string_types

Thank you for your PR. In addition, I fixed CI setup. Use pytest directly instead of python setup.py test.

Thanks for the plugin !


how to from address to utxo use rpc?

I try addressindex=1 in VERGE.conf.  but start node.. show : Error reading configuration file: Invalid configuration value addressindex
How to establish address index?

index=1

Did this fix your issue?

my VERGE.conf is:
server=1
txindex=1
index=1
deprecatedrpc=estimatefee
rpcbind=<IP_ADDRESS>
rpcuser=xxxxxx
rpcpassword=xxxxx
when is run   ./verged -datadir=. -daemon  .
show:  Error reading configuration file: Invalid configuration value index
why?

oh sorry it txindex=1 yep you got it. not index

remove index=1

i add  txindex=1 ..buf i can't find getaddressutxos...
on other coin , if my add addressindex=1.. i can see getaddressutxos interface.
why.

@zdyszm Hey there, I did a quick research on bitcoins decision regarding this address tracking stuff. Unfortunately there is no such a functionality nor can you enable it somehow. So you would have to use our “bitcore” software to keep tracking all addresses, which manually scans all blocks and keeps a log of the addresses ever used.
We won’t support this within the core node.


Creating a scm_ike_gateway then attempting to push config for Service Connection results in error

Describe the bug
When attempting to create a scm_ike_gateway via terraform, the resource completes being created, but when I attempt to push the config for the parent service connection, it results in a validation error.
Validation Error:
 network -> ike -> gateway -> entry attribute name is missing
 network -> ike -> gateway is invalid

Expected behavior
I would expect the resource to create successfully, and also not have validation errors when I attempt to push the service connection's config.
Current behavior
Pushing the created ike gateway and service connection results in error.
Possible solution

Steps to reproduce

Create a scm_ike_gateway, scm_ipsec_tunnel, and scm_service_connection via TF
Attempt to push config
Witness validation error

Screenshots

Context
I was able to create a service connection via ui without issue and push the config. Also, when looking at the API response in the UI, my IKE gateway does have a value for name as "@name": "US-DevXX-XXXX",. I believe the values I have provided for the IKE gateway to be valid as they work when I create them through the UI as opposed to the API/TF.
Your Environment

Version used:
Environment name and version (e.g. Chrome 59, node.js 5.4, python 3.7.3):
Operating System and version (desktop or mobile):
Link to your project:

I noticed that there is no Terraform code to reproduce the issue.  Could you guys please share a complete Terraform plan that results in an invalid IKE gateway error when attempting to push the config?  You also said that when you create the IKE gateway via UI it works.  Using the scm_ike_gateway data source to compare the resulting configs for Terraform vs UI would also give me more info.  If the data source output doesn't have any differences between Terraform created vs UI created, enable debug logging on Terraform and check the JSON returned from the API, as there may be fields present in the JSON that are not present in the schema for the scm_ike_gateway data source and resource.

@shinmog the other engineer I am working with indicated that it seems the behavior is caused by a required naming structure with the IKE gateway. They observed changing the name and being able to resolve the issue. Is there some sort of predefined naming structure required for the resource or documentation somewhere that details what structure the name has to follow?
I am not seeing anything specificied in the API https://pan.dev/access/api/prisma-access-config/post-sse-config-v-1-ike-gateways/ other than [0-9a-zA-Z._-]

It certainly sounds like there is some requirements on the naming, but if the provider itself doesn't present those requirements (aka - must match a regex), then that means the OpenAPI file the provider was built from didn't contain that information.
If the OpenAPI spec contains this information, then the provider can help enforce it.
But it sounds like you have a solution at this point..?

We have a workaround for right now in that we have figured out a value that will work by reverse-engineering one from a successful creation via GUI, but this is very fragile and brittle.
It would be nice to have a precise answer for what the undocumented naming requirements needs to be. Is there a resource internally you could get an answer to this?
I understand the OpenAPI spec is missing this information, but just adding details to the docs on this would be quite helpful.

I was unable to reproduce this error.  I was able to create an IKE gateway named tunnel1, associate it to an IPsec tunnel resource, and then create a remote network.  Everything passed the commit validation and deployed without issue.
resource "scm_ike_gateway" "gw1" {
  folder = "Remote Networks"
  name   = "gateway1"
  peer_address = {
    dynamic_address = true
  }
  peer_id = {
    type = "fqdn"
    id = "Terrafoo"
  }

  protocol = {
    version = "ikev2"
    ikev2 = {
      ike_crypto_profile = "PaloAlto-Networks-IKE-Crypto"
      dpd = {
        enable = false
      }
    }
  }
  authentication = {
    pre_shared_key = {
      key = "secret123!"
    }
  }
}

resource "scm_ipsec_tunnel" "tun1" {
    folder = "Remote Networks"
    name = "tunnel1"
    auto_key = {
        ike_gateways = [
            {
                name = scm_ike_gateway.gw1.name
            }
        ]
        ipsec_crypto_profile = "PaloAlto-Networks-IPSec-Crypto"
    }
}

resource "scm_remote_network" "rn1" {
    folder = "Remote Networks"
    name = "Test"
    region = "us-east-1"
    spn_name = "us-east-coral"
    ipsec_tunnel = scm_ipsec_tunnel.tun1.name
}

if you try with the scm_ike_gateway with a name of "ZbuchheitServiceConnectionIkeGw1" does your repro still work? That is the format we used on our name an encountered trouble.


Window decorations broken with GLFW and libdecor

Hyprland Version
 System/Version info
Hyprland, built from branch main at commit 1d2acbe19355c8640d54a4b6cba225c6f4370c85  (config: add absolute monitor workspace selectors (5848)).
Date: Fri May 3 19:38:00 2024
Tag: v0.39.1-138-g1d2acbe1, commits: 4598

flags: (if any)

System Information:
System name: Linux
Node name: 10303B-arch
Release: 6.8.9-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Thu, 02 May 2024 17:49:46 +0000

GPU information:
0c:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c1) (prog-if 00 [VGA controller])

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:

Bug or Regression?
Bug
Description
This happens if libdecor is used for window decorations in a GLFW window:

Window decorations are drawn above of the window
There is a gap between the decorations and the start of the content
The top pixels are repeated by the width of the decorations
Mouse clicks are registered at the wrong position

Does not happen when an X11 session is enforced with XDG_SESSION_TYPE=x11. Other compositors do also work (Mutter).
How to reproduce

Can't share my test application, but this also reproduces the issue: hanatos/vkdt (compile with make, then run ./bin/vkdt)

Details:

Create a GLFW 3.4 window and render something on it (using Vulkan)
Make sure GLFW_WAYLAND_LIBDECOR is hinted as GLFW_WAYLAND_PREFER_LIBDECOR (should be default)
Make sure the Wayland backend is used

Crash reports, logs, images, videos

I have the same issue with my application which is just glfw + vulkan and does not explicitly use or configure libdecor in any way. Not just the window decorations are broken but also mouse coordinates do not line up with the application window anymore. This appears to be a recent regression because until at most a few weeks ago GLFW + hyprland was working without problem.

I'm experiencing the same in a application using glfw and opengl https://github.com/larfingshnew/3d-controller-overlay, a title bar will be drawn in top of the windows and will overlap with every other element on screen as long as the windows is focused, there is also a gap top and bottom, and there will be and small vertical offset between were the mouse pointer is and what is being selected.
This does not happens in sway were the title bar is correctly omitted, and in gnome and kde it will just draw a normal titlebar

can someone bisect this

I could try to bisect later this week

bad commit is ed69502ff6e79a6dad213333b0bc3a15e2247942

@phonetic112 you just beat me to it ;-)
Looking at the debug log it appears like clients with GLFW windows do not end up in the XDGDecoration protocol handler.
For e.g. kitty I see this:
[LOG] Searching for matching rules for kitty (title: )
[LOG] Window rule suppressevent maximize ->  class:.* matched [Window 5adf5c7790d0: title: ""]
[LOG] [hookSystem] New hook event registered: windowUpdateRules
[LOG] Window 5adf5c7790d0 set title to kitty
[LOG] Searching for matching rules for kitty (title: kitty)
[LOG] Window rule suppressevent maximize ->  class:.* matched [Window 5adf5c7790d0: title: "kitty"]
[LOG] [XDGDecoration] setMode: MODE_SERVER_SIDE. Sending MODE_SERVER_SIDE as reply.

So Hyprland is sending MODE_SERVER_SIDE to the client which if I understand the protocol correctly should be the right thing.
For my GLFW window it never gets there, there are not other XDGDecoration messages in the log file at all.
I could try to debug further but since I have zero knowledge of the hyprland code base probably someone else can diagnose the problem much faster than I can figure it out.

I'm quite busy with the wayland core rewrite mr, try debugging the aptly named protocols/xdgdecoration.cpp file I guess

I've debugged this and I'm starting to think this may actually a GLFW problem and not a Hyprland problem.
When starting a 'well-behaved client' like e.g. kitty, chromium or an SDL2 client using SDL_VIDEODRIVER=wayland, the Hyprland XDGDecoration protocol code goes through a zxdg_decoration_manager_v1::get_toplevel_decoration request first, then it receives a zxdg_toplevel_decoration_v1::set_mode request, ignoring whatever the client prefers and instead replying with a zxdg_toplevel_decoration_v1::configure event with zxdg_toplevel_decoration_v1::mode::server_side to tell the client it should not render any decorations.
For GLFW clients, not so much. Hyprland gets a zxdg_decoration_manager_v1::get_toplevel_decoration but it never gets a zxdg_toplevel_decoration_v1::set_mode which means GLFW will default to client-side decorations (and fails to render those properly as well apparently).
Looking at the stack trace at the point where the zxdg_toplevel_decoration_v1::set_mode is received for 'good clients' (this ends up in _CZxdgToplevelDecorationV1SetMode in protocols/xdg-decoration-unstable-v1.cpp), there is no Hyprland code between that point and libwayland, so I don't believe the problem is in Hyprland.
If this makes sense I can file a ticket with GLFW or try to debug it myself, but I could of course be missing something about the Hyprland Wayland protocol handling that could affect the set_mode request getting lost for GLFW clients.

I'd still send the hint. It wouldn't hurt I feel like.

I'm now knee-deep into debugging how GLFW and libdecor interact with the compositor, and I think maybe this is a Hyprland problem after all.
Observations:

GLFW defaults to using libdecor for decorations these days
libdecor uses zxdg_decoration_manager_v1::get_toplevel_decoration do ask the compositor about window decorations
if the compositor replies with zxdg_decoration_manager_v1::mode::server_side it will disable drawing decorations
Running my GFLW app on KWin, the debugger ends up in the libdecor protocol listener for zxdg_decoration_manager_v1, receiving  zxdg_decoration_manager_v1::mode::server_side (the value 2)
Running the exact same app on Hyprland, the listener callback is never hit, so libdecor will decide to draw decorations using the gtk plugin (which is what you see in the screenshot above)

Most likely once you get to 5, there is some mismatch between what Hyprland thinks the size of the client area is vs what libdecor thinks, which leads to these problems. Or something along those lines.
As for why 5 happens, I'm not entirely sure. I see XDGDecorations.cpp is written to respond to xdg_decoration_toplevel_v1::set_mode by emitting a xdg_decoration_toplevel_v1::configure event, and this works as expected for clients that do the set_mode request (cf. kitty, chromium, etc). But it seems set_mode is mostly intended for requesting a change in decorations, and clients are not actually required to call it, they can also get the decoration mode when doing get_toplevel_decoration.
I cannot figure out how to fix this though, because I don't understand the mechanisms by which the Hyprland protocol handlers are supposed to communicate with the client. It's probably trivial to fix this if all that is needed is to make sure Hyprland sends 'zxdg_decoration_manager_v1::mode::server_side when a client is requesting zxdg_decoration_manager_v1::get_toplevel_decoration.

Ok I was able to fix this with a one-liner and created PR #6308
The fix is to send the xdg_decoration_toplevel_v1::configure event when the CXDGDecoration event is created in response to a xdg_decoration_toplevel_v1::get_toplevel_decoration request.
I just threw the event emit into the CXDGDecoration constructur which is probably not the right place to do it, but at least it demonstrates how this can be fixed.