lottieconverter: 0.1.1 -> 0.2

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

This version supports GIF transparency, making them more visually satisfying in matrix.
ref: https://github.com/NixOS/nixpkgs/pull/162980

Result of nixpkgs-review pr 182555 run on x86_64-linux 1

1 package built:

lottieconverter

License change is correct, too.


invitation_accepted_at should be nil if the user signs up

I noticed that if there is a pending invite and if the user doesn't go through the link and signs up normally then the invite is marked as accepted. The invite should only be marked as accepted if and only they set the password through the invitation link. Any suggestions for making this so?

You may change line 10 in registrations controller, to clear invitation token. Some tests may need changes.
https://github.com/scambra/devise_invitable/blob/master/app/controllers/devise_invitable/registrations_controller.rb#L10


Improve Kestrel startup example

Fixes #16265
Thanks @Ricardoaraujo00! ⛄ ... We assume a little too much sometimes! Thanks for calling this out, and we look forward to hearing if you run into additional troubles with any of the topics. Please feel free to use the This page feedback button+form at the bottom of any topic. It adds metadata to track the work and automatically pings the author when your docs issue is created.

You're welcome @guardrex

How to expose an aspnet core gRPC service to the outside(executed with "dotnet run" or clicking a published executable).

I can't answer on that one ... I'm not really a gRPC 🐈. I see that you opened https://github.com/aspnet/AspNetCore.Docs/issues/16278, so you should hear back on that question there.
WRT videos ... I'll repeat what I said on https://github.com/aspnet/AspNetCore.Docs/issues/16279 ...

The trouble with videos is that they become dated fairly fast. Then, the entire video has to be replaced because it isn't easy to cut in new or changed content. Text is going to be with us for a long time.

I'm going to lock this one because we don't work from closed issues and PRs ... we don't track that work/discussion very well. It sounds like tho you'll get the answers that you're seeking on the other issues (gRPC and the tutorial for Linux question).


PubSubWorkerThread._run() fails if stream_timeout is used

If you use stream_timeout=1, the PubSubWorkerThread will fail with TimeoutError exception, since the pubsub.get_message() internally uses parse_response(block=False, timeout=0) (since 0 is the default timeout value, and we can't explicitly pass one), which ends using the stream_timeout=1.
I see two ways of solving this:

try-except TimeoutError: pass around pubsub.get_message() at PubSubWorkerThread._run().
give pubsub.get_message(..., timeout=1), so we use the wait_for() path in parse_response().

I tried both and they work. Let me know your preference and I'll submit the patch (or please fix it, should be 1-2 lines of patch :-D)

@barbieri I think the second way may be better~


Specify start and end times when 30 minute steps?

Is it possible to specify start and end dates instead of start and end hours?
For example, if I want it to render slots from 9 am to 10:30, I would have to specify startHours as 9 and endHours as 11 but that would include an extra slot from 10:30 to 11 in day view.
Is there a way to ensure only slots are 9 am - 9:30 am, 9:30 - 10 am and 10 am to 10:30 am?
const Scheduler = ({start,end}) => {
    let end_time = new Date(moment(end).add(30, 'minutes'))
    return (
        <Scheduler
            view="day"
            day={
                {
                    startHour:start.getHours(),
                    endHour: end_time.getHours(),
                    step:30,
                    navigation: false
                }
            }
            disableViewNavigator
            navigation
        />
    )
}

There is no straightforward way for this.
You can -at the moment- override cellRenderer to disabled the extra cell, until I add this feature


DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead

when  import { OAuth2Client } from "google-auth-library"; this warning appears and when removed the import, it disappears
(node:32561) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

OS - MacOs sonoama v.14.5
node -v = 20.14.0
npm -v = 10.8.1
"google-auth-library": "^9.11.0",

This is caused by an upstream dependency; once we release our next major it should work on Node 22 (which has this deprecation message).

temporary solution: add override in package.json
  "overrides": { "whatwg-url": "^14.0.0" },

This warning is still consistent. I am using Node v22.4.0.

I'm useing
NODE_OPTIONS="--no-deprecation"
Please Fix it.


Blocked.

As of 10/26/23 the Cybriagames

website has been detected by the automated blocking system of Securly school blocking.

try to use cybriagames.pages.dev next


Add IDS Description field to Assets

At the time of writing it is not possible to send the description of an asset to another connector.
Therefore, this issue is about introducing a new property key ids:description that is written into the IDS Resource description field.
Dominik Pinsel<EMAIL_ADDRESS>Daimler TSS GmbH, legal info/Impressum

PR #579

Are you suggesting mapping a generic Asset description into the (specific) IDS description? The Asset shouldn't have IDS-specific properties, they need to be mapped.


How to make the web page more responsive #for beginners

To create a responsive website, add the following  tag to all your web pages: Example. . Try it Yourself …

❤


Improve SMTP authentication, Fix user creation bugs and add LDAP cert/key options

This PR has three parts:
Improvements for SMTP authentication:

Default to use SMTPS if port is 465, and allow setting of force SMTPS.
Always use STARTTLS if available
Provide CRAM-MD5 mechanism
Add options for HELO hostname disabling
Add options for providing certificates and keys
Handle application specific password response as a failed user login
instead of as a 500.

Close #16104
Fix creation of new users:

A bug was introduced when allowing users to change usernames which
prevents the creation of external users.
The LoginSource refactor also broke this page.

Add certificate and key options to ldap
Fix #14102
Close #16104
Fix #14102
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Agh I need to update the docs and the command too. Will add those tomorrow.

Codecov Report

Merging #16612 (adfb12a) into main (35735bb) will decrease coverage by 0.00%.
The diff coverage is 9.63%.

@@            Coverage Diff             @@
##             main   #16612      +/-   ##
==========================================
- Coverage   45.35%   45.35%   -0.01%
==========================================
  Files         750      750
  Lines       85100    85148      +48
==========================================
+ Hits        38601    38616      +15
- Misses      40255    40289      +34
+ Partials     6244     6243       -1

Impacted Files
Coverage Δ

cmd/admin_auth_ldap.go
75.36% <0.00%> (-2.25%)
:arrow_down:

services/auth/source/ldap/source.go
80.00% <ø> (-6.67%)
:arrow_down:

services/auth/source/smtp/auth.go
0.00% <0.00%> (ø)

services/auth/source/smtp/source.go
14.28% <0.00%> (ø)

services/auth/source/smtp/source_authenticate.go
0.00% <0.00%> (ø)

services/forms/auth_form.go
100.00% <ø> (ø)

routers/web/admin/auths.go
49.81% <16.66%> (-0.37%)
:arrow_down:

services/auth/source/ldap/source_search.go
44.96% <26.08%> (-1.86%)
:arrow_down:

models/login_source.go
54.30% <0.00%> (-1.99%)
:arrow_down:

... and 8 more

Continue to review full report at Codecov.

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

Imho it would be better to use single pem file for both certificate and key, something like this:
https://gist.github.com/ukautz/cd118e298bbd8f0a88fc#file-cert_load-go-L18

I guess the trouble is we haven't been using that kind of thing before. This PR as it currently stands means that everywhere you have certificates and keys in Gitea you know you need to have them separate.

Oh, had not noticed that. Having them in single file makes things way easier imho but I will not block it either way :)

So the one questionable part of this PR is the option to provide the path to the key/cert combo - this is not restricted to the data path and the path can be anything.
This page is only accessible to the administrator, but perhaps it might be better to make it an option to use a cert/key specifically named for the login_source as in a checked bool option instead.

Why not store certificate/key in database in text/blob field? This would also make it possible later to move it to gitea secrets

Why not store certificate/key in database in text/blob field? This would also make it possible later to move it to gitea secrets

I guess we could encrypt them with the secret key?
My main worry is that it's going to need another huge field that we will have to get out of the db every time someone tries to login and potentially other times too. So it would need to be another table where it could be cached etc.

it should also be noted that this option is only for providing a client certificate - this is not for verifying the host certificate.

Why not store certificate/key in database in text/blob field? This would also make it possible later to move it to gitea secrets

I guess we could encrypt them with the secret key?
My main worry is that it's going to need another huge field that we will have to get out of the db every time someone tries to login and potentially other times too. So it would need to be another table where it could be cached etc.
it should also be noted that this option is only for providing a client certificate - this is not for verifying the host certificate.

Or maybe wait for secrets feature to be added

So you suggest removing this part of the PR?

Use certificate changes have been removed.

@lafriks please review again

Small nit but otherwise looks good


Implement Mango selectors for change feeds

API is modeled after _doc_ids filter for change feeds.
User POSTs to {db}/_changes with filter=_selector.
Document body should have a "selector" field, with
a Mango selector object as value.
For example:
http://.../d1/_changes?filter=_selector
{
  "selector": {"z" : {"$gte" : 1} }
}

In case "selector" is missing or its value is not a
JSON object, a 400 error is returned with a
corresponding error message. For example:
{
    "error": "bad_request",
    "reason": "Selector error: 42, expected an object"
}

In case "selector" object cannot be validated as a
Mango selector, a 400 error is returned with a validation
error as "reason".
Jira: COUCHDB-2988

Nice feature, but I feel quite strange about creating dependency from mango for couch app. Since mango is a cluster thing, shouldn't it be on chttpd side?

@kxepal for the clustered vs. not dependency, it is slightly odd. However the changes code is sadly tied into the main couch repo, there's nothing we can really do to undo that without some pretty awkward contortions just for purity's sake.
Also, in this case, the mango logic being used is purely functional, there's no cluster or anything. Its strictly just a "does this json blob match this other json blob using the mango selector DSL rules" function.
So while I do agree it would be best to have this specific change in a different app, I'd argue that it's more of that all of this particular changes code should be in a different app that understands clustered vs not rather than the hodge podge of things we have now. Until then I wouldn't worry about this too much since it will work for both clustered and single node.

Except for the various tweaks to error messaging, +1 to the feature. Sure did come out a lot simpler than I was expecting.

@davisp Ok, thanks. Indeed decoupling these things would be quite problematic task now without any significant profit.

impressive brevity for such a powerful new feature.

@kxepal @davisp  @rnewson  Updated error message for bad methods to be explicit, fixed get_selector duplicate code, use mango_error:info to format selector error messages.

+1

Good point @rnewson. I'd go with the 400 approach then.

simpler than I thought, +1

That's a great feature! In order to maintain a live list of docs that match a query, I will need changes from docs that used to match the query but no longer do so I can remove them from the list. Is that possible with this feature?

@colinskow there is no easy way to add that I can think of. The query is in the context of the changes request. As long as there are results filtering back from that query, they'll contain documents which match the selector. There is nothing returning from the query which knows which documents matched before (using a previous changes request).

@nickva thank you very much for your response. A "live query" would be a very useful feature for front-end app developers.
I have successfully implemented this, but it requires listening to the entire changes feed. So my solution would not be entirely practical with a noisy database.
Would it be practical to maintain state of the query in a _design, _replication, or _live_query doc so the front end can maintain a live list of docs that match that query without having to listen to other noise?

@colinskow that implies some kind of persistence. The selector passed in a change feed request is active only in the context of the POST request. There could be multiple such concurrent requests. After request is finished, there is no history preserved of previous request.
Or were you thinking about a long / continuous request, and while it is returning data back to the user,  a document which passed the filter and was returned before, was updated to no longer pass the selector. But there is nothing to tell the user about it. So perhaps have something in the change feed saying "this document passed the selector before but no longer does".
That is an interesting case then. If document is deleted we return it with "_deleted":true, is it reasonable to have something like "_selector_failed":true? I am not sure about this. You might want to take this up on the couchdb mailing list. This looks like an API change then and needs a better discussion.


[Jira] ... only shows the first 50 projects, cannot create an issue in project with identifier starting with U

Extension
https://www.raycast.com/raycast/jira
Description
Currently cannot Create Issue on the Jira project I'm on because I cannot access the project in the search list when creating an issue.
Moving to the new Jira extension and authorizing it, I only see the first 50 projects in my Jira account. We work with many clients, so we have many projects inside our Jira account, but the projects with identifiers (for example starting with the letter U) I cannot search for in the Create Issue action, but I can see inside Search Issues with the same project ID.
Steps To Reproduce

Authorize Jira
Attempt to Create Issue
Try searching for the correct project (in this case starting with U)
Cannot find project in the list at all, list is truncated to 50 items

Current Behaviour
Cannot create issue with project identifier starting with U
Expected Behaviour
Should be able to create an issue with any project in my jira account

Thanks for bringing up this issue, I've added it to our backlog and will work on it in the next few weeks.

@thomaslombart I see the hard limit of 100, but for whatever reason, we're getting truncated at 50, honestly this could be the Jira API limiting you too, but the outgoing extension didn't do this, so 🤷 let me know if it needs another look, thanks!

@thomaslombart thanks for handling this quickly, went to try the same thing today and it worked, product is absolutely killer, keep it up


Database link not working

Hello, i was interested into Plasmer but i can't download the pre-built database. Is there any other way to download it?

Hi Andrewab9, thank you for your interest in Plasmer. Our article is currently under review and has not yet been published. As a result, the database resource remains unpublished as well. Would it be possible for you to wait a little longer? I will notify you as soon as everything is ready. Thank you for your patience and understanding.

Hi Andrewab9, we have published the database today. You can try it at https://doi.org/10.5281/zenodo.7030674
or https://drive.google.com/drive/folders/1C1XLqTuPVfwyB7N3b5QAU09Rn-Qq7RdD?usp=sharing
Please notice that the program and database had been updated, you may need to install the latest version 😁


AttributeError: 'module' object has no attribute 'n_entities'

rzai@rzai00:~/prj/DeepMind-Teaching-Machines-to-Read-and-Comprehend$ export DATAPATH=~/prj/DeepMind-Teaching-Machines-to-Read-and-Comprehend/
rzai@rzai00:~/prj/DeepMind-Teaching-Machines-to-Read-and-Comprehend$ python train.py deepmind_deep_lstm
Using gpu device 0: GeForce GTX 1080 (CNMeM is disabled, cuDNN 5005)
No plotting extension available.
Traceback (most recent call last):
File "train.py", line 46, in
ds, train_stream = data.setup_datastream(path, vocab_path, config)
File "/home/rzai/prj/DeepMind-Teaching-Machines-to-Read-and-Comprehend/data.py", line 137, in setup_datastream
ds = QADataset(path, vocab_file, config.n_entities, need_sep_token=config.concat_ctx_and_question)
AttributeError: 'module' object has no attribute 'n_entities'
rzai@rzai00:~/prj/DeepMind-Teaching-Machines-to-Read-and-Comprehend$

this can be fix by
rzai@rzai00:~/prj/DeepMind-Teaching-Machines-to-Read-and-Comprehend$ git diff
diff --git a/config/deepmind_deep_lstm.py b/config/deepmind_deep_lstm.py
index 10b5c9b..8fd05f3 100644
--- a/config/deepmind_deep_lstm.py
+++ b/config/deepmind_deep_lstm.py
@@ -3,7 +3,6 @@ from blocks.initialization import IsotropicGaussian, Constant
from model.deep_lstm import Model

batch_size = 32
sort_batch_count = 20
@@ -12,6 +11,7 @@ shuffle_questions = True
concat_ctx_and_question = True
concat_question_before = True
+n_entities = 550
embed_size = 200
lstm_size = [256, 256]


Fix test_kms_with_rest errors\

fix the upper used in test_kms_with_rest which cause base64 error
fix disable key coding error

Signed-off-by: Long Hanyu<EMAIL_ADDRESS>

Please also fix: https://github.com/intel/ehsm/blob/main/ehsm_kms_service/test/cli/utils.py#L28


mbed support for teensy31 not properly implemented

Teensy support not properly implemented in the software (possible only the interface?)
Take a look at:
tformio/platformio/boards/teensy.json
Here it is indicated that the teensy31 supports the mbed framework.
However, actually using the software gives no such indication.
For example look at:
platformio/platformio/platforms/teensy.py
Here the mbed framework is not included!

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27313401-mbed-support-for-teensy31-not-properly-implemented?utm_campaign=plugin&utm_content=tracker%2F2014790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2014790&utm_medium=issues&utm_source=github).

In board's frameworks field is defined default frameworks. mbed is optional framework for Teensy. See meed-blink example for Teensy 3.1 https://github.com/platformio/platformio/tree/develop/examples/mbed/mbed-blink

Yes, sorry about that. I only noticed the issue tracker after the email.
I looked at the blink example, but I can’t get it to work. I have a feeling it’s not just me doing something wrong.
Do you have skype? I can screen share you.

On 11 Oct 2015, at 07:59, Ivan Kravets<EMAIL_ADDRESS>wrote:
In board's frameworks field is defined default frameworks. mbed is optional framework for Teensy. See meed-blink example for Teensy 3.1 https://github.com/platformio/platformio/tree/develop/examples/mbed/mbed-blink https://github.com/platformio/platformio/tree/develop/examples/mbed/mbed-blink
—
Reply to this email directly or view it on GitHub https://github.com/platformio/platformio/issues/305#issuecomment-147133394.

Here is the immediate error I get upon running the example:

IOError: [Errno 2] No such file or directory: '/Users/heyer/.platformio/packages/framework-  mbed/variant/TEENSY3_1/TEENSY3_1.eix':

Seems the mbed package is not downloaded automatically when using the teensy31 board.

Give me please an output of this command:

ls -la /Users/heyer/.platformio/packages/framework- mbed/variant/TEENSY3_1/

Try to reinstall teensy platform

platformio platforms uninstall teensy
platformio platforms install teensy

Result of first command:

$ ls -la ~/.platformio/packages/framework-mbed/variant/TEENSY3_1/
ls: /Users/heyer/.platformio/packages/framework-mbed/variant/TEENSY3_1/: No such file or directory

I reinstalled the teensy platform using the commands you gave me, but it does not change the result of running the first command.
My version is 2.3.3

Hm... Please  provide me this info:
python -c "import platform; print platform.uname()"

ls -la ~/.platformio/packages/framework-mbed/variant/

Thanks.

Python command:
('Darwin', 'Daniels-MacBook-Pro.local', '15.0.0', 'Darwin Kernel Version 15.0.0: Wed Aug 26 16:57:32 PDT 2015; root:xnu-3247.1.106~1/RELEASE_X86_64', 'x86_64', 'i386')

Upper directory listing (ls -la ~/.platformio/packages/framework-mbed, I removed the "variant" part of the query")
ls: /Users/heyer/.platformio/packages/framework-mbed/: No such file or directory

I haven't really gone into your code, but I have a suspicion that the problem is that the teensy platform is not defined as using the 'mbed' platform. I can see the package is not installed when I install the teensy platform. Perhaps an issue in this file?
https://github.com/platformio/platformio/blob/369d0e1a0040f7f4331cb7607dbaaaa8ab9d6f96/platformio/platforms/teensy.py

Yes, this is bug!!! Thanks! :+1:
Temporary solution, please install some platform which contains framework-mbed:
platformio platforms install nxplpc

It did indeed work.


Multiple ways to mark person as administrator

You can mark a person as a superuser under their user account. There is also an administrator role in the team. I believe we are only using the standard Django superuser flag to decide if we show the edit experiment button etc. We should resolve this and make it more clear.
Note, this is likely related to #24

I think part of implementing #24 will be adding first class "edit experiment" views, at which point we should stop editing anything through the Django admin and move everything over to the tenant permission model


Refactor usage of global device

Closes #531

[x] Introduces a new function get_shared() that returns the globally shared object. This object contains the global adapter, device, std uniform buffer, access to the glyph atlas, and maybe more in the future. The first invocation creates the singleton.
[x] Adds a test to make sure that get_shared() is not called during import.
[x] Refactor code to make use of it. Some rules of thumbs that I used:

The device object is not passed as an argument to a function that is defined in another module.
Within a module avoid sprinkling get_shared() calls by passing the object as an argument (to the module-level private functions).
When the logic is structured in a class (e.g. blender, flusher, renderer), store the device on the object for easy use.

The main pain point (as I experienced it) was that the device is a global object, but was also passed around from one function to another a lot. My intention with this PR is to make its use more obvious, and tracking the device less of a problem, leading (I hope) to clearer code.


"warning: broken physics ahead" -> deep space travel

Large world space coordinates will introduce inaccuracy, courtesy of floating point arithmetic rounding: epsilon.
Floating point errors in deep space caused by large world coordinates and small frame times is affecting movement physics and rendering. Meaning the deeper in space we go, the more "stuff" begins to break.
According to the documentation:
Caution: Box2D works best with world sizes less than 2 kilometers. Use b2World::ShiftOrigin to support larger worlds.
The universe by contrast, is a little bit bigger than 2km....
To solve this we can use a local coordinate system and a large global coordinate system. see: 'Floating Origin' ->  b2World::ShiftOrigin

https://randomascii.wordpress.com/2012/02/13/dont-store-that-in-a-float/
https://www.youtube.com/watch?v=mXTxQko-JH0&t=4m18s


Error of potential length overflow when adding data multiple times in Milvus.

When using Milvus as a database, the maximum length of the textField is calculated and fixed during the first collection creation, like so:
{
    name: this.textField,
    description: "Text field",
    data_type: milvus2_sdk_node_1.DataType.VarChar,
    type_params: {
        max_length: getTextFieldMaxLength(documents).toString(),
    },
}

However, when I add data to the collection again, it's possible to exceed the maximum length set. Is it possible to add a manually set property in the constructor to prioritize setting the maximum value? For example:
{
    name: this.textField,
    description: "Text field",
    data_type: milvus2_sdk_node_1.DataType.VarChar,
    type_params: {
        max_length: this.textFieldMaxLength > 0 ? this.textFieldMaxLength.toString() : getTextFieldMaxLength(documents).toString(),
    },
}

Seems reasonable!

Yes, I'm glad to contribute to the open-source community. I will submit a PR


Terraform provider doesn't check for uniqueness when adding MAC addresses

Prerequisites

[Yes ] Have you tested the operation in the API directly?
[Yes  ] Do you have the latest Terraform provider version?

Describe the bug
The terraform provider does not verify that a mac address [endpoint] already exists when creating a resource.  What I have noticed is that if I declare a resource in terraform to add a mac address [endpoint] that already exists in the endpoint database, the terraform provider says it successfully added it which is false.
Expected behavior
The terraform provider should return the message that I see when I perform the same operation from the API:
"title": "Unable to create the endpoint. Endpoint "00:04:4B:86:40:67" already exists.",
Screenshots

Environment (please complete the following information):

ISE version and patch:    <IP_ADDRESS>8. Patch 3
Terraform version:  Terraform v1.2.7
ISE provider version:   registry.terraform.io/ciscoise/ciscoise v0.6.4-beta
OS version:   MacOS Monterey 12.5

Resource code:
resource "ciscoise_endpoint" "mydevice" {
provider = ciscoise
parameters {
description             = "Terraform managed"
group_id                = "0b5a32b0-ad6a-11e9-b12f-a6a2aaa3119d"
mac                     = "00:04:4B:86:40:67"
name                    = "00:04:4B:86:40:67"
static_group_assignment = "true"
}
}

Hi @netsecprogrammer, could you please export following env variables and please show me whole answer please?
Variables:

TFLOG = "DEBUG"
ISE_DEBUG= "TRUE"

Thanks.

Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.
user48-mac:terraform-ise-staging user$ terraform apply
2022-08-16T18:57:30.340-0600 [INFO]  Terraform version: 1.2.7
2022-08-16T18:57:30.340-0600 [DEBUG] using github.com/hashicorp/go-tfe v1.0.0
2022-08-16T18:57:30.340-0600 [DEBUG] using github.com/hashicorp/hcl/v2 v2.12.0
2022-08-16T18:57:30.340-0600 [DEBUG] using github.com/hashicorp/terraform-config-inspect v0.0.0-20210209133302-4fd17a0faac2
2022-08-16T18:57:30.340-0600 [DEBUG] using github.com/hashicorp/terraform-svchost v0.0.0-20200729002733-f050f53b9734
2022-08-16T18:57:30.340-0600 [DEBUG] using github.com/zclconf/go-cty v1.10.0
2022-08-16T18:57:30.340-0600 [INFO]  Go runtime version: go1.18.1
2022-08-16T18:57:30.340-0600 [INFO]  CLI args: []string{"terraform", "apply"}
2022-08-16T18:57:30.340-0600 [DEBUG] Attempting to open CLI config file: /Users/user/.terraformrc
2022-08-16T18:57:30.340-0600 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.
2022-08-16T18:57:30.340-0600 [DEBUG] ignoring non-existing provider search directory terraform.d/plugins
2022-08-16T18:57:30.340-0600 [DEBUG] ignoring non-existing provider search directory /Users/user/.terraform.d/plugins
2022-08-16T18:57:30.340-0600 [DEBUG] ignoring non-existing provider search directory /Users/user/Library/Application Support/io.terraform/plugins
2022-08-16T18:57:30.340-0600 [DEBUG] ignoring non-existing provider search directory /Library/Application Support/io.terraform/plugins
2022-08-16T18:57:30.340-0600 [INFO]  CLI command args: []string{"apply"}
2022-08-16T18:57:30.343-0600 [DEBUG] New state was assigned lineage "83a939b6-29ca-95b2-96f3-11bf6ee24178"
2022-08-16T18:57:30.446-0600 [DEBUG] checking for provisioner in "."
2022-08-16T18:57:30.447-0600 [DEBUG] checking for provisioner in "/usr/local/bin"
2022-08-16T18:57:30.448-0600 [INFO]  backend/local: starting Apply operation
2022-08-16T18:57:30.451-0600 [DEBUG] created provider logger: level=debug
2022-08-16T18:57:30.451-0600 [INFO]  provider: configuring client automatic mTLS
2022-08-16T18:57:30.470-0600 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta args=[.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta]
2022-08-16T18:57:30.474-0600 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta pid=64138
2022-08-16T18:57:30.474-0600 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta
2022-08-16T18:57:30.485-0600 [INFO]  provider.terraform-provider-ciscoise_v0.6.4-beta: configuring server automatic mTLS: timestamp=2022-08-16T18:57:30.485-0600
2022-08-16T18:57:30.504-0600 [DEBUG] provider: using plugin: version=5
2022-08-16T18:57:30.504-0600 [DEBUG] provider.terraform-provider-ciscoise_v0.6.4-beta: plugin address: network=unix address=/var/folders/hn/vb99_75j3t74v6zsr98plw9s081d33/T/plugin4294144804 timestamp=2022-08-16T18:57:30.504-0600
2022-08-16T18:57:30.595-0600 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2022-08-16T18:57:30.597-0600 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta pid=64138
2022-08-16T18:57:30.597-0600 [DEBUG] provider: plugin exited
2022-08-16T18:57:30.597-0600 [DEBUG] Building and walking validate graph
2022-08-16T18:57:30.598-0600 [DEBUG] ProviderTransformer: "ciscoise_endpoint.mydevice" (*terraform.NodeValidatableResource) needs provider["registry.terraform.io/ciscoise/ciscoise"]
2022-08-16T18:57:30.598-0600 [DEBUG] ReferenceTransformer: "var.IOT_CRUD_DEVICES" references: []
2022-08-16T18:57:30.598-0600 [DEBUG] ReferenceTransformer: "var.allpolicy_set_ids" references: []
2022-08-16T18:57:30.598-0600 [DEBUG] ReferenceTransformer: "provider["registry.terraform.io/ciscoise/ciscoise"]" references: []
2022-08-16T18:57:30.598-0600 [DEBUG] ReferenceTransformer: "ciscoise_endpoint.mydevice" references: []
2022-08-16T18:57:30.598-0600 [DEBUG] ReferenceTransformer: "var.allpolicy_set_names" references: []
2022-08-16T18:57:30.598-0600 [DEBUG] Starting graph walk: walkValidate
2022-08-16T18:57:30.598-0600 [DEBUG] created provider logger: level=debug
2022-08-16T18:57:30.598-0600 [INFO]  provider: configuring client automatic mTLS
2022-08-16T18:57:30.617-0600 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta args=[.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta]
2022-08-16T18:57:30.622-0600 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta pid=64139
2022-08-16T18:57:30.622-0600 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta
2022-08-16T18:57:30.636-0600 [INFO]  provider.terraform-provider-ciscoise_v0.6.4-beta: configuring server automatic mTLS: timestamp=2022-08-16T18:57:30.635-0600
2022-08-16T18:57:30.655-0600 [DEBUG] provider: using plugin: version=5
2022-08-16T18:57:30.655-0600 [DEBUG] provider.terraform-provider-ciscoise_v0.6.4-beta: plugin address: address=/var/folders/hn/vb99_75j3t74v6zsr98plw9s081d33/T/plugin2145390281 network=unix timestamp=2022-08-16T18:57:30.655-0600
2022-08-16T18:57:30.772-0600 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2022-08-16T18:57:30.774-0600 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta pid=64139
2022-08-16T18:57:30.774-0600 [DEBUG] provider: plugin exited
2022-08-16T18:57:30.774-0600 [INFO]  backend/local: apply calling Plan
2022-08-16T18:57:30.774-0600 [DEBUG] Building and walking plan graph for NormalMode
2022-08-16T18:57:30.774-0600 [DEBUG] ProviderTransformer: "ciscoise_endpoint.mydevice (expand)" (*terraform.nodeExpandPlannableResource) needs provider["registry.terraform.io/ciscoise/ciscoise"]
2022-08-16T18:57:30.774-0600 [DEBUG] ReferenceTransformer: "ciscoise_endpoint.mydevice (expand)" references: []
2022-08-16T18:57:30.774-0600 [DEBUG] ReferenceTransformer: "var.allpolicy_set_ids" references: []
2022-08-16T18:57:30.774-0600 [DEBUG] ReferenceTransformer: "var.allpolicy_set_names" references: []
2022-08-16T18:57:30.774-0600 [DEBUG] ReferenceTransformer: "var.IOT_CRUD_DEVICES" references: []
2022-08-16T18:57:30.774-0600 [DEBUG] ReferenceTransformer: "provider["registry.terraform.io/ciscoise/ciscoise"]" references: []
2022-08-16T18:57:30.774-0600 [DEBUG] Starting graph walk: walkPlan
2022-08-16T18:57:30.774-0600 [DEBUG] created provider logger: level=debug
2022-08-16T18:57:30.774-0600 [INFO]  provider: configuring client automatic mTLS
2022-08-16T18:57:30.792-0600 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta args=[.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta]
2022-08-16T18:57:30.796-0600 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta pid=64140
2022-08-16T18:57:30.797-0600 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta
2022-08-16T18:57:30.807-0600 [INFO]  provider.terraform-provider-ciscoise_v0.6.4-beta: configuring server automatic mTLS: timestamp=2022-08-16T18:57:30.807-0600
2022-08-16T18:57:30.833-0600 [DEBUG] provider: using plugin: version=5
2022-08-16T18:57:30.833-0600 [DEBUG] provider.terraform-provider-ciscoise_v0.6.4-beta: plugin address: address=/var/folders/hn/vb99_75j3t74v6zsr98plw9s081d33/T/plugin692679349 network=unix timestamp=2022-08-16T18:57:30.831-0600
2022-08-16T18:57:30.970-0600 [DEBUG] Resource instance state not found for node "ciscoise_endpoint.mydevice", instance ciscoise_endpoint.mydevice
2022-08-16T18:57:30.971-0600 [DEBUG] ReferenceTransformer: "ciscoise_endpoint.mydevice" references: []
2022-08-16T18:57:30.971-0600 [DEBUG] refresh: ciscoise_endpoint.mydevice: no state, so not refreshing
2022-08-16T18:57:30.974-0600 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2022-08-16T18:57:30.976-0600 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta pid=64140
2022-08-16T18:57:30.976-0600 [DEBUG] provider: plugin exited
2022-08-16T18:57:30.976-0600 [DEBUG] building apply graph to check for errors
2022-08-16T18:57:30.976-0600 [DEBUG] Resource state not found for node "ciscoise_endpoint.mydevice", instance ciscoise_endpoint.mydevice
2022-08-16T18:57:30.977-0600 [DEBUG] ProviderTransformer: "ciscoise_endpoint.mydevice" (*terraform.NodeApplyableResourceInstance) needs provider["registry.terraform.io/ciscoise/ciscoise"]
2022-08-16T18:57:30.977-0600 [DEBUG] ProviderTransformer: "ciscoise_endpoint.mydevice (expand)" (*terraform.nodeExpandApplyableResource) needs provider["registry.terraform.io/ciscoise/ciscoise"]
2022-08-16T18:57:30.977-0600 [DEBUG] ReferenceTransformer: "var.allpolicy_set_ids" references: []
2022-08-16T18:57:30.977-0600 [DEBUG] ReferenceTransformer: "var.allpolicy_set_names" references: []
2022-08-16T18:57:30.977-0600 [DEBUG] ReferenceTransformer: "var.IOT_CRUD_DEVICES" references: []
2022-08-16T18:57:30.977-0600 [DEBUG] ReferenceTransformer: "ciscoise_endpoint.mydevice" references: []
2022-08-16T18:57:30.977-0600 [DEBUG] ReferenceTransformer: "provider["registry.terraform.io/ciscoise/ciscoise"]" references: []
2022-08-16T18:57:30.977-0600 [DEBUG] ReferenceTransformer: "ciscoise_endpoint.mydevice (expand)" references: []
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:

create

Terraform will perform the following actions:
ciscoise_endpoint.mydevice will be created

resource "ciscoise_endpoint" "mydevice" {

id           = (known after apply)

item         = (known after apply)

last_updated = (known after apply)

parameters {

description             = "Terraform managed"
group_id                = "0b5a32b0-ad6a-11e9-b12f-a6a2aaa3119d"
mac                     = "00:04:4B:86:40:67"
name                    = "00:04:4B:86:40:67"
static_group_assignment = "true"
}
}

Plan: 1 to add, 0 to change, 0 to destroy.
2022-08-16T18:57:30.977-0600 [DEBUG] command: asking for input: "\nDo you want to perform these actions?"
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
2022-08-16T18:57:32.209-0600 [INFO]  backend/local: apply calling Apply
2022-08-16T18:57:32.209-0600 [DEBUG] Building and walking apply graph for NormalMode plan
2022-08-16T18:57:32.209-0600 [DEBUG] Resource state not found for node "ciscoise_endpoint.mydevice", instance ciscoise_endpoint.mydevice
2022-08-16T18:57:32.209-0600 [DEBUG] ProviderTransformer: "ciscoise_endpoint.mydevice" (*terraform.NodeApplyableResourceInstance) needs provider["registry.terraform.io/ciscoise/ciscoise"]
2022-08-16T18:57:32.209-0600 [DEBUG] ProviderTransformer: "ciscoise_endpoint.mydevice (expand)" (*terraform.nodeExpandApplyableResource) needs provider["registry.terraform.io/ciscoise/ciscoise"]
2022-08-16T18:57:32.209-0600 [DEBUG] ReferenceTransformer: "provider["registry.terraform.io/ciscoise/ciscoise"]" references: []
2022-08-16T18:57:32.209-0600 [DEBUG] ReferenceTransformer: "ciscoise_endpoint.mydevice (expand)" references: []
2022-08-16T18:57:32.209-0600 [DEBUG] ReferenceTransformer: "var.allpolicy_set_names" references: []
2022-08-16T18:57:32.209-0600 [DEBUG] ReferenceTransformer: "var.IOT_CRUD_DEVICES" references: []
2022-08-16T18:57:32.209-0600 [DEBUG] ReferenceTransformer: "var.allpolicy_set_ids" references: []
2022-08-16T18:57:32.209-0600 [DEBUG] ReferenceTransformer: "ciscoise_endpoint.mydevice" references: []
2022-08-16T18:57:32.210-0600 [DEBUG] Starting graph walk: walkApply
2022-08-16T18:57:32.210-0600 [DEBUG] created provider logger: level=debug
2022-08-16T18:57:32.210-0600 [INFO]  provider: configuring client automatic mTLS
2022-08-16T18:57:32.229-0600 [DEBUG] provider: starting plugin: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta args=[.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta]
2022-08-16T18:57:32.232-0600 [DEBUG] provider: plugin started: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta pid=64149
2022-08-16T18:57:32.232-0600 [DEBUG] provider: waiting for RPC address: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta
2022-08-16T18:57:32.244-0600 [INFO]  provider.terraform-provider-ciscoise_v0.6.4-beta: configuring server automatic mTLS: timestamp=2022-08-16T18:57:32.243-0600
2022-08-16T18:57:32.262-0600 [DEBUG] provider: using plugin: version=5
2022-08-16T18:57:32.263-0600 [DEBUG] provider.terraform-provider-ciscoise_v0.6.4-beta: plugin address: address=/var/folders/hn/vb99_75j3t74v6zsr98plw9s081d33/T/plugin4243402755 network=unix timestamp=2022-08-16T18:57:32.262-0600
ciscoise_endpoint.mydevice: Creating...
2022-08-16T18:57:32.397-0600 [INFO]  Starting apply for ciscoise_endpoint.mydevice
2022-08-16T18:57:32.398-0600 [DEBUG] ciscoise_endpoint.mydevice: applying the planned Create change
2022-08-16T18:57:32.398-0600 [INFO]  provider.terraform-provider-ciscoise_v0.6.4-beta: 2022/08/16 18:57:32 [DEBUG] setting computed for "item" from ComputedKeys: timestamp=2022-08-16T18:57:32.398-0600
2022-08-16T18:57:32.398-0600 [INFO]  provider.terraform-provider-ciscoise_v0.6.4-beta: 2022/08/16 18:57:32 [DEBUG] Beginning Endpoint create: timestamp=2022-08-16T18:57:32.398-0600
2022-08-16T18:57:32.398-0600 [INFO]  provider.terraform-provider-ciscoise_v0.6.4-beta: 2022/08/16 18:57:32 [DEBUG] request sent => {"ERSEndPoint":{"name":"00:04:4B:86:40:67","description":"Terraform managed","mac":"00:04:4B:86:40:67","groupId":"0b5a32b0-ad6a-11e9-b12f-a6a2aaa3119d","staticGroupAssignment":true}}: timestamp=2022-08-16T18:57:32.398-0600
2022-08-16T18:57:32.857-0600 [INFO]  provider.terraform-provider-ciscoise_v0.6.4-beta: 2022/08/16 18:57:32 [DEBUG] [RESTY]
GET  /ers/config/endpoint/name/00:04:4B:86:40:67  HTTP/1.1
HOST   : ise:9060
HEADERS:
        Accept: application/json
        Authorization: Basic ZXJzdXNlcjpiMklyNGRnNTNiWElucUVCdW4xYw==
        Content-Type: application/json
        User-Agent: go-resty/2.7.0 (https://github.com/go-resty/resty)
BODY   :
***** NO CONTENT *****
------------------------------------------------------------------------------
~~~ RESPONSE ~~~
STATUS       : 200
PROTO        : HTTP/1.1
RECEIVED AT  : 2022-08-16T18:57:32.857389-06:00
TIME DURATION: 458.487767ms
HEADERS      :
        Cache-Control: no-cache, no-store, must-revalidate
        Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data:;
        Content-Type: application/json;charset=utf-8
        Date: Wed, 17 Aug 2022 00:57:32 GMT
        Expires: Thu, 01 Jan 1970 00:00:00 GMT
        Pragma: no-cache
        Server:
        Set-Cookie: JSESSIONIDSSO=F574829C0F4CE2AFB7C14A5BEB152061; Path=/; Secure; HttpOnly, APPSESSIONID=3D3BB1DB6857E70329E1ECA9006286C1; Path=/ers; Secure; HttpOnly
        Strict-Transport-Security: max-age=31536000; includeSubDomains
        X-Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data:;
        X-Content-Type-Options: nosniff
        X-Frame-Options: SAMEORIGIN
        X-Webkit-Csp: default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data:;
        X-Xss-Protection: 1; mode=block
BODY         :
{
   "ERSEndPoint": {
      "id": "982dc040-3525-11ec-a9bd-92a157dd7b25",
      "name": "00:04:4B:86:40:67",
      "description": "",
      "mac": "00:04:4B:86:40:67",
      "profileId": "1080b360-1f9e-11e2-96ee-0050568e002d",
      "staticProfileAssignment": false,
      "staticProfileAssignmentDefined": true,
      "groupId": "0b5a32b0-ad6a-11e9-b12f-a6a2aaa3119d",
      "staticGroupAssignment": true,
      "staticGroupAssignmentDefined": true,
      "portalUser": "",
      "identityStore": "",
      "identityStoreId": "",
      "customAttributes": {
         "customAttributes": {
            "Owner": ""
         }
      },
      "link": {
         "rel": "self",
         "href": "https://ise:9060/ers/config/endpoint/name/00:04:4B:86:40:67",
         "type": "application/json"
      }
   }
}
==============================================================================: timestamp=2022-08-16T18:57:32.857-0600
2022-08-16T18:57:32.858-0600 [INFO]  provider.terraform-provider-ciscoise_v0.6.4-beta: 2022/08/16 18:57:32 [DEBUG] Beginning Endpoint read for id=[name:=00:04:4B:86:40:67]: timestamp=2022-08-16T18:57:32.857-0600
2022-08-16T18:57:32.858-0600 [INFO]  provider.terraform-provider-ciscoise_v0.6.4-beta: 2022/08/16 18:57:32 [DEBUG] Selecting method. Method 1 [false]: timestamp=2022-08-16T18:57:32.857-0600
2022-08-16T18:57:32.858-0600 [INFO]  provider.terraform-provider-ciscoise_v0.6.4-beta: 2022/08/16 18:57:32 [DEBUG] Selecting method.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .parameters[0].static_profile_assignment: was null, but now cty.StringVal("")
      - .parameters[0].id: was null, but now cty.StringVal("")
      - .parameters[0].portal_user: was null, but now cty.StringVal("")
      - .parameters[0].identity_store_id: was null, but now cty.StringVal("")
      - .parameters[0].profile_id: was null, but now cty.StringVal("")
      - .parameters[0].identity_store: was null, but now cty.StringVal("")
ciscoise_endpoint.mydevice: Creation complete after 1s [id=name:=00:04:4B:86:40:67]
2022-08-16T18:57:33.052-0600 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = transport is closing"
2022-08-16T18:57:33.055-0600 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/ciscoise/ciscoise/0.6.4-beta/darwin_amd64/terraform-provider-ciscoise_v0.6.4-beta pid=64149
2022-08-16T18:57:33.055-0600 [DEBUG] provider: plugin exited

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

Hey @netsecprogrammer, our provider does not fail to create an existing resource since internally, it does not create it again, but when it exists, it searches for it and loads it to handle it as a resource, if you look at the
tfstate file, probably when adding the resource you will have all the data of it accessible.

Hi @fmunozmiranda thank you for the quick reply.  If I understand you correctly, it sounds like the provider is doing a tf import in the instance it encounters a pre-existing mac address.  I did check my tfstate file and as you stated, the resource is in there.
The first issue is I don't know if a mac address is pre-existing ahead of time.  The second issue is that the object that already exists in this case, isn't getting modified when the plan is executed.  It appears that the provider is importing the existing object into the tfstate and the provider believes it pushed down the settings I have in my resource but that second step where the pre-existing resource needs to be modified isn't happening.
I noticed that if I make a second change to my resource (lets say I update the description), the provider will then recognize that there is a modification and will now push all the modifications.  Basically the provider isn't able to do that state import and modify at the same time it appears.

Hey @netsecprogrammer , a new functionality in new provider version (0.6.6-beta) has been added for the provider, this consists of an environment variable or provider that enables or disables the autoimport behavior.
Here I leave the documentation.
https://registry.terraform.io/providers/CiscoISE/ciscoise/latest/docs
Here an example
provider "ciscoise" {
  enable_auto_import = "true"
}
resource "ciscoise_endpoint" "example" {
  provider   = ciscoise
  depends_on = [data.ciscoise_endpoint_group.found]
  parameters {
    name                      = "11:22:33:44:55:66"
    description               = "My Test Endpoint 1"
    mac                       = "11:22:33:44:55:66"
    profile_id                = "67a6ca50-edc9-4236-ada4-225559ed54d6"
    group_id                  = "67a6ca50-edc9-4236-ada4-225559ed54d6"
    static_profile_assignment = "false"
    static_group_assignment   = "false"
    portal_user               = "portalUser"
    identity_store            = "identityStore"
    identity_store_id         = "identityStoreId"
    custom_attributes {
      custom_attributes = {
        Authorization = "Internet"
        Owner         = "wilhelm"
        Department    = "Eng"
        Model         = "1111"
        Manufacturer  = "Cisco"
        iPSK          = "abc123"
        Created       =<PHONE_NUMBER>
        Expired       =<PHONE_NUMBER>
      }
    }
  }
}

NOTE
Variable default is false, so you may only especify if you want to enable it.

Hey @netsecprogrammer  if we don't get answer, this issue will be close due inactivity.

Closing due inactivity.


Saucelabs test runner + cypress, unable to find configuration file when running on Jenkins pipeline

🐛 Bug Report
saucectl run command fails when running on pipeline due to being unable to find the configuration file. The error is
`failed to execute run command error=failed to locate runner configuration in home/seluser/config.yaml' even though the file exists in the repository
To Reproduce
Setup a cypress project and install saucectl along with it
Setup the saucectl config file to run your cypress tests
Setup a pipeline and try to run the saucectl run command in one of the stages
Expected behavior
Saucectl run command executes and runs the cypress tests in the saucelabs environment
Scripts and configuration needed to reproduce this issue (when applicable)
Use the basic saucelabs test runner setup for cypress. Try to run the example test file in a jenkins pipeline
Environment
OS:
Docker version:

@prakrit-baidya can you share how are you setting up your Jenkins stage? In order for saucectl to work properly on CI you need to set one of the testrunner-toolkit images as the agent image.
Take a look at this example provided by @tianfeng92
https://github.com/saucelabs/testrunner-toolkit/blob/master/.jenkins/Jenkinsfile.cypress

Hi @vrunoa thanks for the example. I hadn't set the agent image in the pipeline. I'll try this method and find out if it works for our pipeline :)

Hi @prakrit-baidya ,
You could replace that docker image with your image in pipeline and just cp your test files under /home/seluser/ to see if it works. Hope it can solve your problem :)

@prakrit-baidya hope you got the Jenkins setup working. Im going to close the issue, but feel free to open it again if you're still having issues with the Jenkins setup.

@prakrit-baidya hope you got the Jenkins setup working. Im going to close the issue, but feel free to open it again if you're still having issues with the Jenkins setup.


Tracking Issue: Support for Previously Hand Written Resources

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Support for what are currently SDK defined resources such as kubernetes:apiextensions.k8s.io:CustomResource.
Building on #157
Affected area/feature

I think we can close this as tracked by providers:

https://github.com/pulumi/pulumi-kubernetes/issues/1971
https://github.com/pulumi/pulumi-docker/issues/132

The exception might be that it may be worth implementing a kludge to support Kubernetes CustomResource, as without it there are a good number of things we can't do in YAML.


HDDS-11846. Set the schema version for Recon for fresh install

What changes were proposed in this pull request?
HDDS-11846. Set the schema version for Recon for fresh install
Please describe your PR in detail:

In the current Recon Schema version table, we do not set the version_number value to the table, this causes the version information to default to -1, causing upgrade handler to run even in case of fresh install
In case the version number is not already set for the schema version table - it indicates that this is a fresh install for Ozone.
In case of a fresh install, we need to set the version_number in the table to have a record of the MLV for later upgrade.
This PR adds the insertion of the version to the Schema version table in this scenario

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-11846
How was this patch tested?
Patch was verified using unit tests, and manually tested to ensure the fix works

Hi @devmadhuu @ArafatKhan2198, could you take a look at the PR?

@devabhishekpal thanks for working on the patch, however this will not solve a scenario when a user is on some version say version 1 and once user tries to upgrade our new code containing version framework say version 2, then even though user already has ozone recon and previous tables, ideally even then though our recon upgrade framework is new, all upgrade actions must be run.

So we have to handle 2 scenarios:

Fresh cluster install where Recon is installed fresh.
Upgrade to new cluster version, but framework is getting introduced first in the upgraded version.

No more required, another pull request present


adds examples for querysearch

Adds #1806
I have added some examples in the docstring for query search

Hi ! Thanks for being willing to contribute to aeon.
That's totally due to a lack of communication from me, but this module is being reworked, and I didn't update the issues to reflect that. I've put up PR #2473 to reflect the upcoming changes.
There will be similar things to do as you did here once #2473 is in, so what I can propose to you is that we close this one, and let the examples to be done so you can contribute. Otherwise, I'm sure there is other things that we could use right now, don't hesitate to chat on slack !


Fix peak memory usage not being saved to the logfile

Super simple, just lets us see the peak memory usage from past model runs at the end of the logfile (ran into this today, so just fixing it real quick!)

lgtm 👍


What makes dynamically creating providers unsupported feature?

Is your feature request related to a problem? Please describe.
Let's imagine a twitter post. In the paginated infinite scrolling list, each post may have an avatar, username, image, comment count, repost count, like count. A postItemProvider could handle the name and the counts. But for the avatar and image, they have their own changing state (loading->loaded|failure) and business logics e.g cancelling the image request if the post item is scrolled out of view while the images are loading. So for each post, we need postItemProvider and one or more imageProvider.
Describe the solution you'd like
Should be able to create providers for each post dynamically and dispose them whenever it is appropriate to
Describe alternatives you've considered
Can't figure out alternatives.

For general help request, consider Discord instead. This is for feature requests/bug reports.
But TL;DR, it can easily lead to memory leaks. And it's straight up not really feasible when using the latest syntax


what must the console window  be dark it is impossible to see

What feature do you want to see added?
I was the normal console window of the running and finished job.
We we just looking to make the our multi jenkins look different  but this is too much
Upstream changes
No response

Should be fixed in 0.5.0-rc83.6557e02980de (please reoppen if not).


HBASE-23184 The HeapAllocation in WebUI is not accurate

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
1m 29s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:yellow_heart:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

:green_heart:
mvninstall
6m 40s
master passed

:green_heart:
compile
1m 13s
master passed

:green_heart:
checkstyle
2m  3s
master passed

:green_heart:
shadedjars
7m 45s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
1m 10s
master passed

:blue_heart:
spotbugs
9m 15s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
9m  9s
master passed

_ Patch Compile Tests _

:green_heart:
mvninstall
8m 45s
the patch passed

:green_heart:
compile
2m  5s
the patch passed

:green_heart:
javac
2m  5s
the patch passed

:green_heart:
checkstyle
2m 42s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
shadedjars
8m  6s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
27m 35s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
javadoc
0m 36s
the patch passed

:green_heart:
findbugs
4m 36s
the patch passed

_ Other Tests _

:broken_heart:
unit
271m 42s
hbase-server in the patch failed.

:green_heart:
asflicense
0m 31s
The patch does not generate ASF License warnings.

364m 41s

Reason
Tests

Failed junit tests
hadoop.hbase.regionserver.TestTags

hadoop.hbase.replication.regionserver.TestWALEntryStream

Subsystem
Report/Notes

Docker
Client=19.03.3 Server=19.03.3 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-730/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/730

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 8477055db98e 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-730/out/precommit/personality/provided.sh

git revision
master / 946f1e9e25

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-730/1/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-730/1/testReport/

Max. process+thread count
4272 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-730/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
1m  5s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:yellow_heart:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

:blue_heart:
mvndep
0m 36s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m  8s
master passed

:green_heart:
compile
1m 20s
master passed

:green_heart:
checkstyle
1m 42s
master passed

:green_heart:
shadedjars
4m 33s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
1m  1s
master passed

:blue_heart:
spotbugs
4m  4s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
4m 53s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 15s
Maven dependency ordering for patch

:green_heart:
mvninstall
4m 57s
the patch passed

:green_heart:
compile
1m 21s
the patch passed

:green_heart:
javac
1m 21s
the patch passed

:green_heart:
checkstyle
1m 42s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
shadedjars
4m 40s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
15m 46s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
javadoc
0m 57s
the patch passed

:green_heart:
findbugs
5m  3s
the patch passed

_ Other Tests _

:green_heart:
unit
3m  6s
hbase-common in the patch passed.

:broken_heart:
unit
265m 32s
hbase-server in the patch failed.

:green_heart:
asflicense
1m  6s
The patch does not generate ASF License warnings.

331m 26s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestFromClientSide

Subsystem
Report/Notes

Docker
Client=19.03.3 Server=19.03.3 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-730/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/730

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 048f3e0635c3 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-730/out/precommit/personality/provided.sh

git revision
master / 946f1e9e25

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-730/2/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-730/2/testReport/

Max. process+thread count
5047 (vs. ulimit of 10000)

modules
C: hbase-common hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-730/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.

Rerunning build to see if failure related.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
2m  1s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:yellow_heart:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

:blue_heart:
mvndep
0m 48s
Maven dependency ordering for branch

:green_heart:
mvninstall
7m 19s
master passed

:green_heart:
compile
1m 43s
master passed

:green_heart:
checkstyle
2m 18s
master passed

:green_heart:
shadedjars
5m 58s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
1m 12s
master passed

:blue_heart:
spotbugs
5m 33s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
6m 33s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 15s
Maven dependency ordering for patch

:green_heart:
mvninstall
7m 36s
the patch passed

:green_heart:
compile
1m 54s
the patch passed

:green_heart:
javac
1m 54s
the patch passed

:green_heart:
checkstyle
2m 13s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
shadedjars
6m 13s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
20m 34s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
javadoc
0m 55s
the patch passed

:green_heart:
findbugs
5m 35s
the patch passed

_ Other Tests _

:green_heart:
unit
2m 56s
hbase-common in the patch passed.

:broken_heart:
unit
226m 30s
hbase-server in the patch failed.

:green_heart:
asflicense
0m 46s
The patch does not generate ASF License warnings.

310m 32s

Subsystem
Report/Notes

Docker
Client=19.03.4 Server=19.03.4 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-730/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/730

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux b4593a6debea 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-730/out/precommit/personality/provided.sh

git revision
master / 41bec4b8b1

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-730/3/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-730/3/testReport/

Max. process+thread count
4991 (vs. ulimit of 10000)

modules
C: hbase-common hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-730/3/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.


raise warning if server domain not accessible to host

ie, just debugged issue where:
WP URLs are mydomain.com
but was getting curl errors (not properly surfaced) of unable to access, same with wget mydomain.com from the host.
adding WP site URL (mydomain.com) to /etc/hosts resolves the issue, but need to catch this earlier to save headaches and lengthy debugs...

maybe do a "test crawl" of homepage first and fail quickly.

this may be better handled as "if n first or subsequent crawled files are 4/5xx status, throw an error and stop things"
Failing on a single error on a site with only a small % of inaccessible pages would not be great. capturing errors and reporting on them is more helpful.


Add option to dereference symlinks

Adds the dereference option to flatten symlinks when copying node_modules. This is useful in lerna environments which might symlink a node_module within the same project.
https://github.com/jprichardson/node-fs-extra/blob/HEAD/docs/copy-sync.md

+1 I've been using this with in a serverless monorepo along side serverless-plugin-monorepo. Would be good to see this merged.

Would this make serverless-plugin-monorepo obsolete?

+1 Could we possible have this merged? It's a areal blocker when a monorepo is used.
We use pnpm and have to patch this with patch-package :(

Please merge this. This allows usage of this plugin in a monorepo setup where node_module deps are symlinked.

Bumping, can we possibly get this merged please? 🙏 Solved all of my issues while working in a monorepo (managed with pnpm).

+1 Could we possible have this merged? It's a areal blocker when a monorepo is used.
We use pnpm and have to patch this with patch-package :(

How do you also include subdependencies in a bundle? I noticed this PR to help only with direct deps, but their deps are not being included.

Is this project dead?


S3Adapter returning incorrect url

I was getting incorrect urls for my files stored in S3. I'm using parse-server 2.0.8
I had to modify the following line in  S3Adapter.js
From: return 'https://' + this.bucket + '._s3Client.amazonaws.com' + '/' + this._bucketPrefix + filename;
To: return 'https://' + this._bucket + '.s3.amazonaws.com' + '/' + this._bucketPrefix + filename;

(－‸ლ) Nice catch, fixing in a moment.

not sure if you are aware of this or if it related to this issue, but from my iOS and Android apps and since version 2.1.4, I am getting a URL for my S3 Parse Files that are pointing to my server instead of to S3. Had to revert back to 2.1.3 for the URL to show correctly.

Did you use directAccess = true?

Hi @flovilmart thanks for the reply - no I hadn't. seems like it was a new configuration that I missed. but I added the new config and went back to parse 2.1.4 and still no luck so far; still getting the url to my server

How do you launch parse-server?

I have parse-server as part of another project so I had it installed through npm, added
var S3Adapter = require('parse-server').S3Adapter;
var s3Adapter = new S3Adapter('xxx', 'xxx', "xx", {directAccess: true});

// Specify the connection string for your mongodb database
// and the location to your Parse cloud code
var api = new ParseServer({
  databaseURI: 'xxx',
  cloud: appRoot + '/parse_cloud/main.js', // Provide an absolute path
  appId: 'xxx',
  masterKey: 'xxx',
  clientKey: 'xxx',
  filesAdapter: s3Adapter,
  serverURL: 'http://localhost:1337/parse',
  push: {
    android: {
      senderId: 'xxx',
      apiKey: 'xxx'
    },
    ios: [
      {
        pfx: appRoot + '/apns_cert/apns-dev-key.p12', // Dev PFX or P12
        bundleId: 'xxx',
        production: false // Dev
      },
      {
        pfx: appRoot + '/apns_cert/apns-pro-key.p12', // Prod PFX or P12
        bundleId: 'xxx',
        production: true // Prod
      }
    ]
  }
});

app.use('/parse', api);

to my app.js and then run with node app.js. You think having parse as part of another project can interfere?

We had a problem with the AdapterLoader in 2.1.4, 2.1.5 will be out soon and should resolve that issue


Publishing returns 409 error

When trying to publish an IATI XML file to the registry we get a 409 error back from the registry. In the interface this shows as  'Conflict (e.g. name already exists)’. (On http://aidstream.zimmermanzimmerman.com ).
With debugging I found this is the actual error: ["Publisher name missing. Please select a publisher from the list.”]
Any idea on what might cause this or what I'm doing wrong?
Note: we are not trying to push to the live registry,@stevieflow gave us the staging url for testing; http://iati2.staging.ckanhosted.com/api/ and I set that as the registry.url in the application.ini cfg. This all seems to work well.

Hi @VincentVW et al did the above fix the problem and can this issue be closed now?
Thanks in advance

Hi @iatisupport , Anjesh his comment sounds like the fix (it indeed was using 1.01 of the Registry API) so I'll close it. We never went through to fix this and get Aidstream working on our machine.


Match normalized requirement names

Summary of changes

Requirements might be specified using normalized names as described in PEP 503 but working set would not match them to installed packages that are identified by their canonical name. This is the reason of this issue in liccheck.
Pull Request Checklist

[x] Changes have tests
[x] News fragment added in changelog.d/.
(See documentation for details)

Rebased changes

Nice work @ldaniluk!
I was looking at introducing the same change but I went a different route.
I instead changed the safe_name function call to also change the . to -.
So I was wondering, what is the added benefit of keeping the canonical names in the by_key dict and keeping a separate index for normalised names next to it? Why not update by_key to use normalised names to begin with?

@abravalheri - no rush, take your time, I welcome all the comments
@Jorricks - I did not want to introduce a potentially breaking change since by_key seems to already be a part of interface of this class. I might be mistaken on the topic though - it was my first "real" journey into setuptools.
Initially I considered not adding a translation dictionary and going through all registered distributions in case WorkingSet.find failed to match a canonical name version of a particular distribution.
I have decided against it since current approach with find using a by_key dictionary indicated to me that its focus is on speed and iterating over all by_key entries to convert names to find a match (since normalizing name is one-way function and I cannot just make a canonical name out of normalized one) seemed to be contrarian.

Yes this sounds like a better way to implement it as this makes it completely backwards compatible.
@abravalheri thanks a lot for taking a look at the PR. I understand this might not be at the top of your list @abravalheri, but just be aware, this is quite an annoying issue for many people using the popular pip-tools package.
He also opened the related issue: https://github.com/pypa/setuptools/issues/3157

Hi @Jorricks, sorry for the time it is taking to merge this.
Unfortunately the timing is a bit complicated because some features we were working on since the end of last year were released last week.
In order to make sure we can track down and fix any bugs, I think the best approach here is to give people some extra time to report bugs.
If we mix everything together right now it might make things more difficult for everyone.

Ahh allright, that makes sense. Thanks for the explanation 👍


[BUG] Color hint in shaders causes a shader compilation error

Godot version
v4.1.2.stable.mono.official [399c9dc39]
System information
v4.1.2.stable.mono.official [399c9dc39]
Issue description
I'm unable to use color hints to make an atmosphere shader
Log:
Godot Engine v4.1.2.stable.mono.official (c) 2007-present Juan Linietsky, Ariel Manzur & Godot Contributors.
  modules/gltf/register_types.cpp:73 - Blend file import is enabled in the project settings, but no Blender path is configured in the editor settings. Blend files will not be imported.
--- Debug adapter server started ---
--- GDScript language server started ---
  :3 - Oczekiwana prawidłowa podpowiedź typu po znaku ':'.
  Shader compilation failed.
  res://atmosphere.gdshader:3 - Oczekiwana prawidłowa podpowiedź typu po znaku ':'.
  Shader compilation failed.
--Main Shader--
    1 | shader_type canvas_item;
    2 |
E   3-> uniform vec3 atmosphere_color : hint_color = vec3(0.5, 0.5, 1.0);
    4 | uniform float atmosphere_radius : hint_range(0.001, 2.0) = 1.2;
    5 | uniform float atmosphere_density : hint_range(0.001, 0.1) = 0.05;
    6 |
    7 | void fragment() {
    8 |  vec3 ray_dir = normalize(-frag_coord);
    9 |  float distance = length(ray_dir);
   10 |  float atmosphere_scale = atmosphere_density * distance;
   11 |  COLOR = mix(atmosphere_color, COLOR, exp(-atmosphere_scale));
   12 | }
   13 |
--res://atmosphere.gdshader--
    1 | shader_type canvas_item;
    2 |
E   3-> uniform vec3 atmosphere_color : hint_color = vec3(0.5, 0.5, 1.0);
    4 | uniform float atmosphere_radius : hint_range(0.001, 2.0) = 1.2;
    5 | uniform float atmosphere_density : hint_range(0.001, 0.1) = 0.05;
    6 |
    7 | void fragment() {
    8 |  vec3 ray_dir = normalize(-frag_coord);
    9 |  float distance = length(ray_dir);
   10 |  float atmosphere_scale = atmosphere_density * distance;
   11 |  COLOR = mix(atmosphere_color, COLOR, exp(-atmosphere_scale));
   12 | }
   13 |

Steps to reproduce

Open the attached project in Godot
Use the given shader in a new shader material

Minimal reproduction project
shaderbug.zip

Thanks for the report. hint_color has been renamed to source_color in Godot 4, so closing as this is not a bug. However, there is a PR that would give a more helpful error message in this case: https://github.com/godotengine/godot/pull/82548


Allowed the example window to be ran with a path argument

I thought it'd be neat to provide handling for a path argument, just like usdview.

I like it - however it does now start to hint that the user should run it like that and I wonder if then we're not shooting our own feet by exposing that in this rudimentary manner.
The example window is intended to be the simplest way of showing how one could e.g. implement a window within their own code base. I wonder if this PR would take away from that by introducing more code.
What do you think?

Instead, we might want to instead expose an actual Editor UI within the package (note how the example window is currently outside of usd_qtpy) and maybe allow running that via __main__.py so that one could just do:
python -m usd_qtpy

To run the example editor that combines the widgets into one window in a meaningful way?

Allowing the package to run by itself in the way you suggested seems like the way to go, I think,
that's the way usdview does it too, opens blank by default, but when passing in a filepath, it opens it on startup.
As of now, there is no file loading capability exposed in the interface.
We don't have a menu bar yet with some "file / help / view / window" options available,
so, as a temporary measure, passing in an argument should make things a lot easier instead of relying on
a hardcoded file path. That's solely my motivation for this commit, it doesn't change too much while still opening up
some temporary flexibility for people toying around with the project.
(also, i had to figure out how to make a PR hahaha)

that's the way usdview does it too, opens blank by default, but when passing in a filepath, it opens it on startup.

Note that usdview can't actually open blank - it requires a usd file to open :)

As of now, there is no file loading capability exposed in the interface.
We don't have a menu bar yet with some "file / help / view / window" options available,
so, as a temporary measure, passing in an argument should make things a lot easier instead of relying on
a hardcoded file path. That's solely my motivation for this commit, it doesn't change too much while still opening up
some temporary flexibility for people toying around with the project.

Thanks, good to know that's the first thing you wanted to play with - might be a good first thing to implement for the main window.

Maybe this menu bar should be an optional thing, since I can see usecases where you'd want to use this as a component vs a standalone app. We could mark standalone vs integrated features with an enum or something similar,
or make some keyword arguments afftect what components should be active versus what ones shouldn't be.

Maybe let's first add it - and see where it can go from there. Menu bars can always be hidden in Qt as well and since the individual widgets are still available it would still allow anyone to roll their own using just those components.

(also, i had to figure out how to make a PR hahaha)

Thanks for taking the time to do so; already greatly appreciated.
Your branch is currently sas-dev. Usually it's good practice to name your branches to what you're implementing as a feature. For example: enhancement/launch_example_with_file or alike. Aside of that, good start!

Thanks for taking the time to do so; already greatly appreciated.

No problem!

Your branch is currently sas-dev. Usually it's good practice to name your branches to what you're implementing as a feature. > For example: enhancement/launch_example_with_file or alike. Aside of that, good start!

Will take note for the future!


service_completed_successfully is not a valid option

service_completed_successfully is not a valid option, service_healthy option did not worked

Hi Siddique,
Thank you for the PR. Could you check which versions of Docker and Docker Compose you are using?
DOCKER_BUILDKIT=1 should be the default since Docker version 23 (https://docs.docker.com/build/buildkit/#:~:text=BuildKit is the default builder for users on Docker Desktop%2C and Docker Engine as of version 23.0).
And the condition service_completed_successfully was added in Docker Compose version 1.29.0 (https://github.com/docker/compose/releases/tag/1.29.0).

thanks i have 1.27 let me update that, closing this


WIP: Add RolloutStrategy to addon

Ref: https://github.com/open-cluster-management-io/OCM/issues/114
Signed-off-by: haoqing0110<EMAIL_ADDRESS>

/cc @qiujian16 @zhujian7

https://github.com/open-cluster-management-io/api/pull/208


Update tox requirements

@yasker I updated tox, requirements, and readme to help run validation tests from ones own machine

Thanks @sabiodelhielo !
You need to get rid of the merge commit in the PR though.

LGTM

We may still need this version of gdapi -
git+https://github.com/rancher/gdapi-python.git@31d74507d96c8f053a08bda129cc63f96ca60161

The automation's the pip env uses gdapi-python==0.5.3

@sabiodelhielo I agree with @sangeethah in that we should use the git+https://github.com/rancher/gdapi-python.git@31d74507d96c8f053a08bda129cc63f96ca60161 version of gdapi-python.
Here's the background on that:

That is the latest commit on master of gdapi-python. It has a fix for retrying PUTs when there is a conflict. Cattle can intermittently return 409 conflicts due to just DB race conditions, but in that scenario, cattle hasnt done anything wrong and neither has the test. The only correct thing to do is to retry. So, we made that change to the client.
Normally, we would have just tagged and released this update to the client, but we stopped officially release gdapi-python through the python index (pypi) because it is a pain and the github url approach works just as well. So, the right version to use is the git commit version

Sorry I didnt explain this when you mentioned it the other day @sabiodelhielo. I didn't have full context

@sabiodelhielo
@cjellick just released gdapi-python v0.5.4, can you update the PR to use it instead of the git commit id?

To be clear, I created a release in github, but I did not push it to pypi (we dont really want to go through that hassle). So, you'll still be using the git syntax, but can point at a release instead of an ugliy commit hash now.
https://github.com/rancher/gdapi-python/releases/tag/0.5.4

@cjellick @sabiodelhielo Oops, sorry for the confusion. Yeah, I also meant you can pointed gdapi to the github release 0.5.4 now.

@sabiodelhielo

Can you squash the new commit into the old one?
Can you check if you can use github release v0.5.4 instead of SHASUM for the version?

Let me test with 0.5.4

I think I added everything requested. Do I also need to rebase with master or does the PR handle that on merge?

LGTM.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v3.14 to before v5.4.129",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=83e53a8f120f2f273cf0ad717f5372ab79ac24fe",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d77c9c8537dbc874c8d02b12e7bc5e2a0dcfc04f"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "83e53a8f120f2f273cf0ad717f5372ab79ac24fe",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "d77c9c8537dbc874c8d02b12e7bc5e2a0dcfc04f",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "i2c: robotfuzz-osif: fix control-request directions\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.129 by commit d77c9c8537dbc874c8d02b12e7bc5e2a0dcfc04f, it was introduced in version v3.14 by commit 83e53a8f120f2f273cf0ad717f5372ab79ac24fe. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001121


pre-commit: ensure devtools-protocol version is synced with puppeteer

Enforces e.g. https://github.com/GoogleChromeLabs/chromium-bidi/pull/668

I wonder if we really need a pre-commit hook though. Would it also work to set peerDependencies.devtools-protocol in package.json to a fixed value, instead of '*'?

I don't think we should ensure the same version long-term. Can we change the interfaces in such way so that devtools-protocol is not part of the public chromium-bidi interface?

We use devtools-protocol for type annotations, mainly. @Lightning00Blade, what exactly was breaking on puppeteer's side with the version mismatch?

It's already declared as a peer dependency, see package.json in our repo.

Let's say Puppeteer keep version X, and BiDi Mapper version Y. Due to the first being a Dependency and the latter being a DevDependency, only the Puppeteer one will be installed when running npm install (Mapper has a PeerDependency of '*'). So normal user will never face this issue.
The problem is when trying thing with local version of Puppeteer + local version of Mapper.
Using npm link. Puppeteer's Protocol resolves to X, then you go to Mapper Protocol which tries to resolve node_modules but due to being symlink it does not look at Puppeteer's node_modules folder but it's own.
Then during building phase TypeScripts tries to match the CDP.send commands which are strongly typed, but there are some extra types on Protocol Y that don't exist on Protocol X, thus type become incomparable -> build fails.

@Lightning00Blade how about using the pack -> install workflow for local testing? it is a bit longer but more similar to what happens for the users.

@Lightning00Blade did you have a chance to see if the native npm approach makes sense?

It mostly works. Puppeteer builds even the version are mismatched and changes exits, (used an old and a new version in Mapper to test). The only problem is the Puppeteer's package.json is changed but as long as we don't commit it we are good.

Deleting branch. For reference:
pre-commit hook:

  - repo: local
    hooks:
      - id: puppeteer-devtools-protocol
        name: check devtools-protocol in package.json matches the one used by puppeteer
        files: ^package.json$
        language: system
        entry: .hooks/puppeteer-devtools-protocol.sh

puppeteer-devtools-protocol.sh:

#!/bin/bash
set -euo pipefail

LOCAL="$(npm list devtools-protocol | grep devtools-protocol | cut -d "@" -f2)"
REMOTE="$(npx npm-remote-ls puppeteer@latest | grep devtools-protocol | cut -d "@" -f2)"

if [[ "$LOCAL" != "$REMOTE" ]]; then
    echo "devtools-protocol version ($LOCAL) does not match the one in puppeteer ($REMOTE)"
    exit 1
fi

A small update to this issue -
Just tried it after #691 was merged and it yield TypeScript error with both npm link and npm pack | npm install (...).tgz
../../node_modules/chromium-bidi/lib/cjs/bidiMapper/domains/script/realm.d.ts(32,59): error TS2694: Namespace '"/usr/local/google/home/nvitkov/puppeteer/node_modules/devtools-protocol/types/protocol".Protocol.Runtime' has no exported member 'DeepSerializedValue'.

I will try to create a workaround from Puppeteer side.


Properly specify prerequisites in Makefile

Previously, prerequisites for some targets were implicit in nature, meaning that whether the library targets actually attempted to link with object files compiled with -fPIC depended on the leftover files from previous build and the order in which targets were built.
This could lead to build failures for the libraries, and the standalone utilities may have been able to be linked with object files compiled with position independent code.
Furthermore, a target "all" was added to build all targets, and the phony targets were properly set to "all" and "clean".
This fixes issue #68.

.lo doesn't mean what you think it means.
#57

.lo doesn't mean what you think it means.

This project doesn't use libtool, and libtool itself explicitly states one should not make any assumption about the structure of .lo files.

#57

Didn't see this one before I opened mine. Oh well.


RequestBin has been discontinued

Under the heading "Perform runtime debugging" the RequestBin service is mentioned. But this service is discontinued, now you need to host your own instance of that app. This makes it a hard open to use when wanting to do a detailed debug session. It would be good to provide an alternative way to debug Logic Apps.

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

ID: 5ada40aa-f86c-6951-5147-3c1f069b6af1
Version Independent ID: 432d932d-53a2-e36c-a443-7850416d3a2d
Content: Troubleshoot and diagnose failures - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-diagnosing-failures.md
Service: logic-apps
GitHub Login: @jeffhollan
Microsoft Alias: LADocs; jehollan

@remyblok Thanks for the feedback! We are currently investigating and will update you shortly.

Hi @remyblok - Thanks for reporting this! We have made the necessary changes to this documentation to reference the use of Webhook Tester service instead of RequestBin. The changes will reflect after our next merge, and as such, we will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


[suggestion] Have the query optimizer use indexes fully i.e. covered queries.

Hi,
Continuing from this (albeit hijacked) discussion. (Thanks @taburet für your patience) I'd like to suggest the following.
It would be a simplification for the user and an optimization of the querying system in ODB, if a query that can be returned by an index (covered query), only use the index. In other words, if an index has the fields to cover a projection, then ODB shouldn't fetch any records. It should just return the results directly from the index. This would speed up such queries.
This also simplifies the system for the user, as the user must no longer create special queries against an index to get a faster query result. ODB would do this automatically.
It boils down to a simple rule.

ODB should return any query as fast as it can. :smile:

I am coming from MongoDB and Mongo does this. There are no specific queries on indexes. MongoDB just does its best to be as fast as it can with whatever it has to work with, indexes there or not.
One other interesting feature in MongoDB is index intersecting.
https://docs.mongodb.com/manual/core/index-intersection/
I am just throwing this in as a possible bonus feature. :smile:
Scott

Supported in v3.0-m2.


fix doc hidden and use non-deprecated compare_exchange

Hello
This PR only:

fixes the doc Hidden -> hidden typo.
Replaces compare_and_swap() with non-deprecated compare_exchange()

Thank you!


Conversion .bat files

I have made (with the help of chatGPT) some .bat files to make it easier to convert the models
Convert the initial source model (.safetensors file). Just drop the model on the .bat file
@echo off
REM Check if a file has been dropped
if "%~1"=="" (
    echo Please drag and drop a .safetensors model file onto this .bat file.
    pause
    exit /b
)

REM Extract the file path from the dropped file
set model_path=%~1

REM Use %~dp0 to get the directory of the .bat file (same as convert.py)
set script_path=%~dp0convert.py

REM Run the Python script with the model file
python "%script_path%" --src "%model_path%"

pause

quantize your model to Q4_K_S format (Drop the .GGUF file made from the above script onto this .bat file)
@echo off
REM Check if a file has been dropped
if "%~1"=="" (
    echo Please drag and drop a .GGUF model file onto this .bat file.
    pause
    exit /b
)

REM Extract the file path and name from the dropped file
set model_path=%~1

REM Extract the directory path and filename without extension
for %%f in ("%model_path%") do (
    set model_dir=%%~dpf
    set model_name=%%~nf
)

REM Check if the model name contains '-FP16', '-F16', or '-BF16'
echo %model_name% | findstr /c:"-FP16" /c:"-F16" /c:"-BF16" >nul
if %errorlevel% neq 0 (
    echo The model file must have '-FP16', '-F16', or '-BF16' in the name. Exiting...
    pause
    exit /b
)

REM Remove '-FP16', '-F16', or '-BF16' from the filename
set model_name_no_suffix=%model_name:-FP16=%
set model_name_no_suffix=%model_name_no_suffix:-F16=%
set model_name_no_suffix=%model_name_no_suffix:-BF16=%

REM Set the source and target model paths
set source_model=%model_dir%%model_name%.gguf
set target_model=%model_dir%%model_name_no_suffix%-Q4_K_S.gguf

REM Use %~dp0 to get the directory of the .bat file and construct path to llama-quantize.exe
set script_dir=%~dp0llama.cpp\build\bin\Debug\

REM Run the llama-quantize.exe command
"%script_dir%llama-quantize.exe" "%source_model%" "%target_model%" Q4_K_S

pause

Both files need to be in the \custom_nodes\ComfyUI-GGUF\tools folder
This is a experimental version of the second script that lets you select the quantize format (The formats was recommended by ChatGPT as i don't know what formats is usable)
@echo off
REM Check if a file has been dropped
if "%~1"=="" (
    echo Please drag and drop a .GGUF model file onto this .bat file.
    pause
    exit /b
)

REM Extract the file path and name from the dropped file
set model_path=%~1

REM Extract the directory path and filename without extension
for %%f in ("%model_path%") do (
    set model_dir=%%~dpf
    set model_name=%%~nf
)

REM Check if the model name contains '-FP16', '-F16', or '-BF16'
echo %model_name% | findstr /c:"-FP16" /c:"-F16" /c:"-BF16" >nul
if %errorlevel% neq 0 (
    echo The model file must have '-FP16', '-F16', or '-BF16' in the name. Exiting...
    pause
    exit /b
)

REM Remove '-FP16', '-F16', or '-BF16' from the filename
set model_name_no_suffix=%model_name:-FP16=%
set model_name_no_suffix=%model_name_no_suffix:-F16=%
set model_name_no_suffix=%model_name_no_suffix:-BF16=%

REM Display the list of quantize formats and get user selection
echo Please select a quantize format:
echo 1. Q4_K_S
echo 2. Q5_K_S
echo 3. Q8_K_S
set /p format_choice=Enter the number of your choice (1-3):

REM Map user choice to quantize format
if "%format_choice%"=="1" set quantize_format=Q4_K_S
if "%format_choice%"=="2" set quantize_format=Q5_K_S
if "%format_choice%"=="3" set quantize_format=Q8_K_S

REM Check if the user provided a valid choice
if "%quantize_format%"=="" (
    echo Invalid choice. Exiting...
    pause
    exit /b
)

REM Set the source and target model paths
set source_model=%model_dir%%model_name%.gguf
set target_model=%model_dir%%model_name_no_suffix%-%quantize_format%.gguf

REM Use %~dp0 to get the directory of the .bat file and construct path to llama-quantize.exe
set script_dir=%~dp0llama.cpp\build\bin\Debug\

REM Run the llama-quantize.exe command
"%script_dir%llama-quantize.exe" "%source_model%" "%target_model%" %quantize_format%

pause

I have made a .bat file for installing the llama.cpp/gguf-py and applying the lcpp.patch then it compiles the llama-quantize binary. All .bat files should be in the
ComfyUI-GGUF/tools folder to work
@echo off
REM Clone the repository
git clone https://github.com/ggerganov/llama.cpp
if %ERRORLEVEL% neq 0 (
    echo Git clone failed.
    exit /b %ERRORLEVEL%
)

REM Install the required Python package
pip install llama.cpp/gguf-py
if %ERRORLEVEL% neq 0 (
    echo Pip install failed.
    exit /b %ERRORLEVEL%
)

REM Change to the llama.cpp directory
cd llama.cpp
if not exist llama.cpp (
    echo Directory llama.cpp does not exist.
    exit /b 1
)

REM Checkout the specified tag
git checkout tags/b3600
if %ERRORLEVEL% neq 0 (
    echo Git checkout failed.
    exit /b %ERRORLEVEL%
)

REM Apply the patch
git apply ..\lcpp.patch
if %ERRORLEVEL% neq 0 (
    echo Git apply patch failed.
    exit /b %ERRORLEVEL%
)

REM Create a build directory and navigate into it
mkdir build
cd build

REM Run cmake to configure the build
cmake ..
if %ERRORLEVEL% neq 0 (
    echo CMake configuration failed.
    exit /b %ERRORLEVEL%
)

REM Build with cmake and compile llama-quantize target
cmake --build . --config Debug -j10 --target llama-quantize
if %ERRORLEVEL% neq 0 (
    echo CMake build failed.
    exit /b %ERRORLEVEL%
)

echo Build completed successfully.
pause


Fix the/then typo

Update sentence to start "Then plot your prediction" instead of "The plot your prediction".

Making change in the source document. Thank you!


Port Dimensions fast path + bug fix from upstream

Just some ports from upstream Fabric.
The bugfix mixin isn't strictly necessary, because most people will have FAPI anyway, but I added it in case that two-year-old bug never gets fixed

This PR will be necessary in order to quiltify the Fabric Dimensions API on QFAPI, so yeah, we'll actually need it


[FEATURE] Add documentation on the differences between Schemathesis and Dredd

Is your feature request related to a problem? Please describe.
The differences with Dredd may not be immediately apparent.
Describe the solution you'd like
Add the answer to this question to the FAQ on the documentation site
Nice article, and useful tool :). Just wondered: 1. The user has to… | by Richard Waller | Medium

The biggest difference that I see is that Dredd is using examples and defaults from the schema (I might be wrong but it refuses to run until I add them to the spec under test), Schemathesis generates test cases + uses examples as separate test cases. Also, Schemathesis provides test case shrinking (i.e finding the minimal failing example). I’d say that there are a lot of features that Dredd does that are not in Schemathesis (e.g. API Blueprint support, that powerful hook system, and many more) and probably vice versa. I think we can learn a lot from Dredd, it is an important tool :)

Hi @uta-mori !
Sure thing, I will add this info to the FAQ section today :)

Resolved via https://github.com/schemathesis/schemathesis/commit/8ebe3e5200b0d00e287a1e118c02644739290c09


String / Domain encoding

Encoding for data types "os - octet string", "us - unicode string" and "d - domain" is currently hex-string. According to 309-3 this should be RFC2045 mime-base64.

Is this still relevant? If not please close

Yes, it is. It's more like do we want to change that (and lose compatibility) or keep it as it is (and violate CiA 309-3).

I'd encourage staying as close to the specs as possible.

RFC2045 mime-base64 is implemented in CANopenNode v2.0 and v4.0. See example https://github.com/CANopenNode/CANopenSocket/tree/master/examples/basicDevice