🐛 Bug Report: [Tech insights plugin] the expired facts won't be cleared if the source entity is deleted

📜 Description
The tech insights plugin fact retriever supports setting TTLs for the facts, and the expired records should be cleaned up automatically.
All of the fact retrievers we enabled have lifecycle set to { timeToLive: { weeks: 2 } }. However, when I check the facts table, we see many records are clearly out of the 2 weeks range and not being cleared.
👍 Expected behavior
All the expired records in the facts table should be cleared.
👎 Actual Behavior with Screenshots
Many expired records are still in the database, and all of them are from entities that are removed from the catalog.
👟 Reproduction steps
=> select count(*) from tech_insights.facts where timestamp< now() - INTERVAL '14 DAY';
 count
--------
 237381
(1 row)

📃 Provide the context for the Bug.
The expired items cleanup happens in the insertFacts:
https://github.com/backstage/backstage/blob/7b47138d9a655625f17dbb372796a07a18bf1c23/plugins/tech-insights-backend/src/service/persistence/TechInsightsDatabase.ts#L120-L126
deleteExpiredFactsByDate and deleteExpiredFactsByNumber are the two methods that handle the actual deletion of the records, and both of them accept factRows, which are the latest facts from fact retrievers. The factRows restrain the scope of the deletion to only the currently present entities. In other words, if an entity was present and then deleted, all the fact items related to that entity will be left in the database forever.
For deleteExpiredFactsByDate, we can tweak the SQL query to make it delete all the expired records that match the fact retriever id. It would roughly be equivalent to the following statement:
delete from facts where id="entityMetadataFactRetriever" and timestamp < now() - INTERVAL '14 DAY'

We can delete in batch (say 5000 records at a time) so it won't choke the database.
However, it's a bit more complicated for deleteExpiredFactsByNumber. Since it means "delete all but N latest facts for each id/entity pair", it has to be aware what's the entity it's acting on. We could:

Join the table in catalog. But it breaks the assumption that all the plugins should be isolated.
Query the catalog backend endpoint to check if the entity is still available, but I'm not sure if it will incur too much load on the backend.

🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

You can indeed not join with the catalog table. If you do need to make an existence check, you can use the new /entities/by-refs endpoint which, which can batch fetch any number of things by ref, returning nulls where there was no match. That can be combined with fields limiting to e.g. only get some placeholder like the kind to keep the response size down.
But would it have to have the existence check? Haven't checked the code, but sounds like it could group by ref no matter what, and leaving the actual "final" termination of things to the other janitor function to deal with.

But would it have to have the existence check? Haven't checked the code, but sounds like it could group by ref no matter what, and leaving the actual "final" termination of things to the other janitor function to deal with.

It's not needed for deleteExpiredFactsByDate coz the timestamp is the only thing we care about.
On second thought, we might not need to have the existence check for deleteExpiredFactsByNumber either, but we need to leverage the scheduled task cadence.
For example, if we have a fact retriever registered like below:
createFactRetrieverRegistration({
  cadence: '0 */6 * * *', // Run every 6 hours - https://crontab.guru/#0_*/6_*_*_*
  factRetriever: entityOwnershipFactRetriever,
  lifecycle: { maxItems: 7 },
}),

So the task runs every 6 hours, and we will keep the last 7 items. If the entity still exists, every run should generate an item. Therefore, if the first (id, entity) pair timestamp is earlier than 7 runs (which is 6*7=42 hours), but the total count of that (id, entity) pair is less than 7, then it means the entity disappears in between. That logic is a bit convoluted but I think it should be doable.
It would be great if you and others can shed some light on this too!

The PR linked will fix this for time based queries (as a side effect, the purpose of the PR wasn't initially to fix this). The maxItems variant is still unaddressed.

For maxItems variant I believe a separate janitor job is probably the best approach. The implementation from the linked PR will eventually stale out timed facts but will leave n amount maxItems facts behind because the queries don't know which entities' facts should have 0 records and which entities' facts should have n records.
The janitor task can query the entites endpoint from catalog and find a difference between facts table references and those entities and then run the existing queries to rectify the DB. Note that for a large amount of entities the where-clause of the query will slow down query execution a lot (which is fixed in the linked PR) so I wouldn't add this as part of a scheduled task to ingest facts. Fact ingestion will happen at a more frequent cadence than deletion of stale data is necessary as well.

I thought it was an option to also delete ANY data for ANY reason that's older than N days (whether the entity exists or not). But I'm honestly not up to speed on this one.

Yup, there are two options to automatically clean the DB:

time based
amount of records based

#1 will now (after linked PR) remove all records when they stale out.
#2 will keep n records for each entity regardless if the entity is still present in the catalog or not

Thanks for the fix @Xantier!
I have a question about the fix. After your PR the deletion query is this:
https://github.com/backstage/backstage/blob/3adb716e587608b9d5d0ceea2e20b708e2f8a065/plugins/tech-insights-backend/src/service/persistence/TechInsightsDatabase.ts?rgh-link-date=2023-01-16T09%3A35%3A04Z#L206-L212
May I ask what's the purpose for the whereIn here?
   .and.whereIn('entity', db =>
     db.distinct('entity').where({ id: factRetrieverId }),
   )

For maxItems variant I believe a separate janitor job is probably the best approach.

I agree with this too. Especially after your PR, it seems not necessary to be tied to the fact retriever's cadence anymore. Perhaps we should turn both of cleanup methods to a separate janitor task. @Xantier @freben WDYT?

Thanks @namco1992. That's correct, for the timed queries we don't case about the entity so the whereIn is not needed. I'll create a subsequent PR to take that away.

@Xantier does this resolve this overall issue, or just a separate finding?

bump

Thanks Evan,
Will you provide a pull request for so we can get this merged in? There are at least two ways you can approach this:

Use the now added eventing functionality to inform when an entity is deleted and do the needed actions based on that
Add a scheduled job to remove facts for entities that are not present in the system anymore


Supporting \underline in Text Mode

As a user I would expect \text{\underline{hi}} to work. Currently this works as expected in Math mode.
Actual Results: Error is thrown, and text is not rendered with an underline.
Not sure if this is considered a bug, or just not yet implemented, but tagging as a bug for now.

Agreed! I confirmed that this works in LaTeX. Fixed in #1159.


Properly export types and modules

Change-type: major
Signed-off-by: Carol Schulze<EMAIL_ADDRESS>

@balena-ci I self-certify!


assertion error on tf.random.normal() and tf.keras.layers.conv2D()

System information

Have I written custom code (as opposed to using a stock example script
provided in TensorFlow): NO
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 64 bit
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue
happens on a mobile device: NO
TensorFlow installed from (source or binary): Source
TensorFlow version (use command below): 2.1.0
Python version: 3.7.4
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: 10.1
GPU model and memory: NVIDIA GeForce MX 250, 2GB
Exact command to reproduce:
** Following is the code I took from the official documentation here after getting the exact here at tf.keras.layers.Conv2D traceback.

input_shape = (4, 28, 28, 3)
x = tf.random.normal(input_shape)
y = tf.keras.layers.Conv2D(2, 3, activation='relu', input_shape=input_shape[1:])(x)
print(y.shape)

AssertionError                            Traceback (most recent call last)
 in
----> 1 tf.random.normal((2, 2))
C:\ProgramData\Anaconda3\lib\site-packages\tensorflow_core\python\ops\random_ops.py in random_normal(shape, mean, stddev, dtype, seed, name)
67   """
68   with ops.name_scope(name, "random_normal", [shape, mean, stddev]) as name:
---> 69     shape_tensor = tensor_util.shape_tensor(shape)
70     mean_tensor = ops.convert_to_tensor(mean, dtype=dtype, name="mean")
71     stddev_tensor = ops.convert_to_tensor(stddev, dtype=dtype, name="stddev")
C:\ProgramData\Anaconda3\lib\site-packages\tensorflow_core\python\framework\tensor_util.py in shape_tensor(shape)
992       # not convertible to Tensors becasue of mixed content.
993       shape = tuple(map(tensor_shape.dimension_value, shape))
--> 994   return ops.convert_to_tensor(shape, dtype=dtype, name="shape")
995
996
C:\ProgramData\Anaconda3\lib\site-packages\tensorflow_core\python\framework\ops.py in convert_to_tensor(value, dtype, name, as_ref, preferred_dtype, dtype_hint, ctx, accepted_result_types)
1312
1313     if ret is None:
-> 1314       ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
1315
1316     if ret is NotImplemented:
C:\ProgramData\Anaconda3\lib\site-packages\tensorflow_core\python\framework\constant_op.py in _constant_tensor_conversion_function(v, dtype, name, as_ref)
315                                          as_ref=False):
316   _ = as_ref
--> 317   return constant(v, dtype=dtype, name=name)
318
319
C:\ProgramData\Anaconda3\lib\site-packages\tensorflow_core\python\framework\constant_op.py in constant(value, dtype, shape, name)
256   """
257   return _constant_impl(value, dtype, shape, name, verify_shape=False,
--> 258                         allow_broadcast=True)
259
260
C:\ProgramData\Anaconda3\lib\site-packages\tensorflow_core\python\framework\constant_op.py in _constant_impl(value, dtype, shape, name, verify_shape, allow_broadcast)
264   ctx = context.context()
265   if ctx.executing_eagerly():
--> 266     t = convert_to_eager_tensor(value, ctx, dtype)
267     if shape is None:
268       return t
C:\ProgramData\Anaconda3\lib\site-packages\tensorflow_core\python\framework\constant_op.py in convert_to_eager_tensor(value, ctx, dtype)
93     except AttributeError:
94       dtype = dtypes.as_dtype(dtype).as_datatype_enum
---> 95   ctx.ensure_initialized()
96   return ops.EagerTensor(value, ctx.device_name, dtype)
97
C:\ProgramData\Anaconda3\lib\site-packages\tensorflow_core\python\eager\context.py in ensure_initialized(self)
491       if self._initialized:
492         return
--> 493       assert self._context_devices is None
494       opts = pywrap_tensorflow.TFE_NewContextOptions()
495       try:
AssertionError:

Can you test with tensorflow 2.2.0 or 2.3.0?

@Mrutyunjay01,
The code snippet you have provided is different from the one in the screenshot. Could you please provide the complete code you are running.
Also, I was able to run the code without any issues. Please find the gist of it here.
As suggested by @bhack, please upgrade to TF v2.3 and check if you are facing the same error in a virtual environment. Thanks!

@amahendrakar Yeah, When Conv2D didn't work, I tried running that simple one. But it showed exactly the same error.  However, using tf.compat.v1.disable_eager_execution() surprisingly suppressed the error. But, again I encountered

the same here, Here I am attaching the snippet.

If you have noticed, the error is at 493 line of last block, having this line
assert self._context_devices is None.
Yeah, in google colab, it works fine. But what's the problem in my system? And how did it get suppress while using tf.disable_eager_execution(), but again gave error in the same environment?

What Is this? Are you changing the code example again?
Could you share a single very very minimal but runnable code and tell us  what kind of error you got?
Thanks

Closing the issue as uninstalling and re-installing the updated version solved the issue.

@Mrutyunjay01,
The code snippet you have provided is different from the one in the screenshot. Could you please provide the complete code you are running.
Also, I was able to run the code without any issues. Please find the gist of it here.
As suggested by @bhack, please upgrade to TF v2.3 and check if you are facing the same error in a virtual environment. Thanks!

I am not getting any error now, but Kindly review the 493rd line of my snippet or comment. The code is

self._context_devices is None.
And it has no assertion statement. If you could clarify the cause once, thank you.


Add redirect error boundary

Fixed the merge conflicts here:
https://github.com/storybookjs/module-mocking-demo/pull/10


Need help with initial set up

Hello,
I followed set up instructions and set up twitter notifications,
but after running scan.py I see the following output and no twitts are coming.
I even tried to set up  NOTIFY_RANKING = 10 to make sure there would be no problem to find a pokemons
Obviously, I missed something, Please help me to set up everything correctly.
Thanks
terminal output:
. .
X .
[W2: BENCHING]
Monocle running for 0:04:51.756482
Known spawns: 1, unknown: 1, more: 0
4 workers, 6 threads, 4 coroutines
DB queue: 0, sightings cache: 0, mystery cache: 0
Seen per worker: min 0, max 0, med 0
Visits per worker: min 0, max 0, med 0
Visit delay: min 0.0, max 0.0, med 0.0
Speed: min 0.0, max 15.5, med 0.0
Extra accounts: 0, CAPTCHAs needed: 1
Pokemon found count (10s interval):
0 0 0 0 0 0 0 0 0 0
Visits: 0, per second: 0.00
Skipped: 0, unnecessary: 0
Workers without sightings so far:
0, 1, 2, 3

Your workers have not found any Pokémon yet. Since you just got it running I would let it run for at least 2 hours so that it can find spawn points. I usually let mine run at least 8 hours before even trying to get notifications
Workers without sightings so far:
0, 1, 2, 3

@stunnaspinz
Thank you very much for your help, I will wait.
Thanks


Mermaid markdown does not support links/actor menus

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams
What part(s) of the article would you like to see updated?
Explicitly explain which functionality of Mermaid is and isn't supported
Additional information
This mermaid doc should have links, but it doesn't
sequenceDiagram
    autonumber
    A ->> B: Hello
    links A: {"google": "https://google.com", "github", "https://github.com"}

Working example: https://mermaid-js.github.io/mermaid-live-editor/edit#pako:eNpdj7sOwjAMRX8l8lzonqFSEUjsDCxe0sRtI_KA1BlQ1X-nJWXBm4-P7OsZdDQEEiZ6ZQqazlYNSXkMYi2VOYbsO0qlb8WhacRJiis5F8U9JmfKxNnwmEQrxYwwxDg4QpACYWR-TrKuCzvq6BGqlQ-Wx9z9OV9WnAUDVOApeWXNGm_eziDwSH7fbKhX2TEChmVV89MopouxHBPIXrmJKtjy395Bg-SU6SftL-7W8gEFqFaT

@aiven-amartin
Thanks so much for opening an issue! I'll triage this for the team to review :eyes:

google.com

google.gg


getAll not working in version 1.1.1

Hi guys,
I can't seem to get the 'getAll' method to work no matter what OIDs I try. However if I query them with getSubtree it works. Can someone please inform me of what I am missing.
Doesn't work:
var snmp = require('snmp-native');
var session = new snmp.Session({ host: 'localhost', port: 161, community: 'public' });
var oids = [[1,3,6,1,2,1,1,1],[1,3,6,1,2,1,1,3]];
session.getAll({ oids: oids }, function (error, varbinds) {
    if (error) {
        console.log(error);
    } else {
        varbinds.forEach(function(vb) {
            console.log(vb.oid + " " + vb.value + " " + vb.type);
        });
    }
});

Using getSubtree works:
var snmp = require('snmp-native');
var session = new snmp.Session({ host: 'localhost', port: 161, community: 'public' });
var oids = [[1,3,6,1,2,1,1,1],[1,3,6,1,2,1,1,3]];
session.getSubtree({ oid: oids[0] }, function (error, varbinds) {
    if (error) {
        console.log(error);
    } else {
        varbinds.forEach(function(vb) {
            console.log(vb.oid + " " + vb.value + " " + vb.type);
        });
    }
});

Thanks.

I have answered my own question already. I needed to add a 0 to the end of my OIDs.
var oids = [[1,3,6,1,2,1,1,1,0],[1,3,6,1,2,1,1,3,0]];


EntryGenerator DefaultValues (5): Support for Enum/Bit Flags

Implement default value support for enum / bit flags.
This includes the following:

Flags defined as Set

The user would have to write the following:
@RegisterProperty
@EnumFlag(MyFlag.ONE, MyFlag.TWO)
lateinit var flags: Set<MyFlag> //fail if not lateinit as default values are passed in annotation

Implementation hints:

Files that need to be changed: PropertyDefaultValueProvider and PropertyHintTypeMapper
Provide proper error messages (with Expcetions for now. MessageCollector will be implemented later)
Default values need to be wrapped in a Variant
A value type hint needs to be supplied at registration time
returned bit flag from godot must be converted back to Set<Enum>
Hint string and default value generated from values in @EnumFlag annotation
Registration should look like:

property("nameOfProperty", TestingClass::propertyReference, STRING /*This is the püroperty type*/, Variant("defaultValue") /*This is the default value*/, true /**visible in editor/, DISABLED /*RPCMode*/, GODOT_PROPERTY_HINT_GLOBAL_DIR /*hint type*/, "" /*hint string*/)

@RegisterProperty
@EnumFlag(MyFlag.ONE, MyFlag.TWO)
lateinit var flags: Set<MyFlag> //fail if not lateinit as default values are passed in annotation


[Bug]: crash when pressing E

Bug Description
https://pastebin.com/pP99SY9k
How to Reproduce?
No response
Expected Behavior
No response
Version
2.3.3
Mod Loader Version
1.20.1     47.2.30
Mod Loader
Forge
Logs or additional context
No response
Code of Conduct

[X] I have searched the issue tracker and confirmed that the issue has not been reported
[X] I have checked the FAQ (if one is present) and my issue is not listed
[X] I have verified that I am using the latest version of the mod
[X] I have verified that I have installed all the required dependencies for the mod
[X] I have verified that I do not have Optifine installed. We will close issues if we detect Optifine is in your pack. We cannot fix Optifine issues. Please do not report issues with Optifine present.

HUHU Deutsche Kartoffel-bock zu MODDEN?

I responded to this issue in the discord, this issue is caused by Minecraft Transit Railway, a mod that causes a number of issues with other mods. Blockstates are never meant to be defined as null, hence this is an issue on their side.

when did MTR dev team fix it!!!
i must use MTR to make subways in  my city building!


Captcha notification appears repeatedly after logging in

Describe the bug
After last update HA continuusly request captcha authentication every some minutes
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
After first time captcha inserted no more requested
Screenshots
If applicable, add screenshots to help explain your problem.
System details

Home-assistant (version):
Hassio (Yes/No): (Please note you may have to restart hassio 2-3 times to load the latest version of alexapy after an update. This looks like a HA bug).
alexa_media  (version from const.py or HA startup):
alexapy (version from pip show alexapy or HA startup):

Logs
Please provide logs. We'll be most likely asking for them anyway.
Additional context
Add any other context about the problem here.

Had same problem in earlier update of HA. Did you update Alexa Addon to latest version?

Yes

Please fill out the template and provide a log.

I had the same issue with Home Assistant 0.112.3 and Alexa Media Player v2.9.2.  It prompted for Captcha repeatedly until reverting to Alexa Media Player v2.9.1.
I was able to resolve the issue two different ways:

Reverting Alexa Media Player v2.9.1 and staying with Home Assistant 0.112.3
Keeping Alexa Media Player v2.9.2 and updating to Home Assistant 0.112.4.

I have the same issue with Alexa Media Player v2.9.2 and Home Assistant 0.112.4. Can pass the Captcha, as it keeps repeating the process

Still experience this.. my issue is really, the Notification does not give you the Captcha.. but my Workaround is to uninstall and reinstall.  When you enter in your credentials you get a Captcha..   It recognizes my many Echo Dots.. but the downside is that all those Reminder, Alarm, Timer Sensors  pop up again.   Since this has been occurring too often... I am looking for a means of NOT having to Disable (Gear followed by toggling off Enable and Update ) 3 sensors per Echo x 5 Echos.

Please note this report is for a captcha that pops up after successfully logging in. If you can't log in at all, you're not in the right thread.

I am having the same issues and I have logs. I have scrubbed away some IDs.
2020-07-16 21:15:10 INFO (MainThread) [custom_components.alexa_media]
-------------------------------------------------------------------
alexa_media
Version: 2.10.0
This is a custom component
If you have any issues with this you need to open an issue here:
https://github.com/custom-components/alexa_media_player/issues
-------------------------------------------------------------------

2020-07-16 21:15:10 INFO (MainThread) [custom_components.alexa_media] Loaded alexapy==1.12.0
2020-07-16 21:15:10 DEBUG (MainThread) [alexapy.alexalogin] No valid cookies for log in; using credentials
2020-07-16 21:15:20 DEBUG (MainThread) [alexapy.alexalogin] GET: redirected from
https://alexa.amazon.com
2020-07-16 21:15:20 DEBUG (MainThread) [alexapy.alexalogin] GET:
https://www.amazon.com/ap/signin?showRmrMe=1&openid.return_to=https://alexa.amazon.com/&openid.identity=http://specs.openid.net/auth/2.0/identifier_select&openid.assoc_handle=amzn_dp_project_dee&openid.mode=checkid_setup&openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select&openid.ns=http://specs.openid.net/auth/2.0& returned 200:OK with response <CIMultiDictProxy('Server': 'Server', 'Content-Type': 'text/html;charset=UTF-8', 'X-XSS-Protection': '1', 'X-Content-Type-Options': 'nosniff', 'x-ua-compatible': 'IE=edge', 'Pragma': 'No-cache', 'Cache-Control': 'max-age=0, no-cache, no-store, must-revalidate', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'Strict-Transport-Security': 'max-age=47474747; includeSubDomains; preload', 'Vary': 'Content-Type,Cookie,Referer,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent', 'x-amz-rid': 'xxx', 'p3p': 'policyref="http://www.amazon.com/w3c/p3p.xml",CP="CAO DSP LAW CUR ADM IVAo IVDo CONo OTPo OUR DELi PUBi OTRi BUS PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA HEA PRE LOC GOV OTC "', 'X-Frame-Options': 'SAMEORIGIN', 'Content-Encoding': 'gzip', 'Date': 'Thu, 16 Jul 2020 11:15:19 GMT', 'Content-Length': '23939', 'Connection': 'keep-alive', 'Set-Cookie': 'ap-fid=""; Domain=.amazon.com; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/ap/; Secure', 'Set-Cookie': 'session-id=137-1522117-0788223; Domain=.amazon.com; Expires=Fri, 16-Jul-2021 11:15:18 GMT; Path=/; Secure', 'Set-Cookie': 'session-id-time=2225618118l; Domain=.amazon.com; Expires=Fri, 16-Jul-2021 11:15:18 GMT; Path=/; Secure')>
2020-07-16 21:15:20 DEBUG (MainThread) [alexapy.alexalogin] Processing https://www.amazon.com/ap/signin?showRmrMe=1&openid.return_to=https://alexa.amazon.com/&openid.identity=http://specs.openid.net/auth/2.0/identifier_select&openid.assoc_handle=amzn_dp_project_dee&openid.mode=checkid_setup&openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select&openid.ns=http://specs.openid.net/auth/2.0&
2020-07-16 21:15:20 DEBUG (MainThread) [alexapy.alexalogin] Found standard login page
2020-07-16 21:15:20 DEBUG (MainThread) [alexapy.alexalogin] Found post url to https://www.amazon.com/ap/signin/137-1522117-0788223
2020-07-16 21:15:20 DEBUG (MainThread) [alexapy.alexalogin] Preparing post to https://www.amazon.com/ap/signin/137-1522117-0788223 with input data: {}
2020-07-16 21:15:21 DEBUG (MainThread) [alexapy.alexalogin] POST:
https://www.amazon.com/ap/signin/137-1522117-0788223 returned 200:OK with response <CIMultiDictProxy('Server': 'Server', 'Content-Type': 'text/html;charset=UTF-8', 'X-XSS-Protection': '1', 'X-Content-Type-Options': 'nosniff', 'x-ua-compatible': 'IE=edge', 'Pragma': 'No-cache', 'Cache-Control': 'max-age=0, no-cache, no-store, must-revalidate', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'Strict-Transport-Security': 'max-age=47474747; includeSubDomains; preload', 'Vary': 'Content-Type,Cookie,Referer,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent', 'x-amz-rid': 'xxxxx', 'p3p': 'policyref="http://www.amazon.com/w3c/p3p.xml",CP="CAO DSP LAW CUR ADM IVAo IVDo CONo OTPo OUR DELi PUBi OTRi BUS PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA HEA PRE LOC GOV OTC "', 'X-Frame-Options': 'SAMEORIGIN', 'Content-Encoding': 'gzip', 'Date': 'Thu, 16 Jul 2020 11:15:21 GMT', 'Content-Length': '26006', 'Connection': 'keep-alive', 'Set-Cookie': 'ap-fid=""; Domain=.amazon.com; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/ap/; Secure', 'Set-Cookie': 'session-id=137-1522117-0788223; Domain=.amazon.com; Expires=Fri, 16-Jul-2021 11:15:21 GMT; Path=/; Secure', 'Set-Cookie': 'session-id-time=2225618121l; Domain=.amazon.com; Expires=Fri, 16-Jul-2021 11:15:21 GMT; Path=/; Secure', 'Set-Cookie': 'ubid-main=131-8080594-3374564; Domain=.amazon.com; Expires=Fri, 16-Jul-2021 11:15:21 GMT; Path=/; Secure')>
2020-07-16 21:15:22 DEBUG (MainThread) [alexapy.alexalogin] Processing https://www.amazon.com/ap/signin/137-1522117-0788223
2020-07-16 21:15:22 DEBUG (MainThread) [alexapy.alexalogin] Error message: Important Message!
            To better protect your account, please re-enter your password and then enter the characters as they are shown in the image below.

2020-07-16 21:15:22 DEBUG (MainThread) [alexapy.alexalogin] Captcha requested
2020-07-16 21:15:22 DEBUG (MainThread) [alexapy.alexalogin] Found post url to https://www.amazon.com/ap/signin
2020-07-16 21:15:22 DEBUG (MainThread) [custom_components.alexa_media.configurator] Testing login status: {'error_message': 'Important Message!\n            To better protect your account, please re-enter your password and then enter the characters as they are shown in the image below.\n          ', 'captcha_required': True, 'captcha_image_url': 'https://opfcaptcha-prod.s3.amazonaws.com/4cc777b057d044b48158246fdf87997a.jpg?AWSAccessKeyId=xxxx&Expires=1594898421&Signature=xxxxx'}
2020-07-16 21:15:22 DEBUG (MainThread) [custom_components.alexa_media.configurator] Creating configurator to request captcha
2020-07-16 21:15:41 DEBUG (MainThread) [custom_components.alexa_media.configurator] Configurator closed for Status: {'error_message': 'Important Message!\n            To better protect your account, please re-enter your password and then enter the characters as they are shown in the image below.\n          ', 'captcha_required': True, 'captcha_image_url': 'https://opfcaptcha-prod.s3.amazonaws.com/4cc777b057d044b48158246fdf87997a.jpg?AWSAccessKeyId=xxxxx&Expires=1594898421&Signature=xxxxx'}
Callback_data: {'captcha': 'xabvwc'}
2020-07-16 21:15:41 DEBUG (MainThread) [alexapy.alexalogin] No valid cookies for log in; using credentials
2020-07-16 21:15:41 DEBUG (MainThread) [alexapy.alexalogin] Loaded last request to https://www.amazon.com/ap/signin/137-1522117-0788223
2020-07-16 21:15:41 DEBUG (MainThread) [alexapy.alexalogin] Processing https://www.amazon.com/ap/signin/137-1522117-0788223
2020-07-16 21:15:42 DEBUG (MainThread) [alexapy.alexalogin] Error message: Important Message!
            To better protect your account, please re-enter your password and then enter the characters as they are shown in the image below.

2020-07-16 21:15:42 DEBUG (MainThread) [alexapy.alexalogin] Captcha requested
2020-07-16 21:15:42 DEBUG (MainThread) [alexapy.alexalogin] Found post url to https://www.amazon.com/ap/signin
2020-07-16 21:15:42 DEBUG (MainThread) [alexapy.alexalogin] Preparing post to https://www.amazon.com/ap/signin with input data: {'captcha': 'xabvwc'}
2020-07-16 21:15:43 DEBUG (MainThread) [alexapy.alexalogin] POST:
https://www.amazon.com/ap/signin returned 200:OK with response <CIMultiDictProxy('Server': 'Server', 'Content-Type': 'text/html;charset=UTF-8', 'X-XSS-Protection': '1', 'X-Content-Type-Options': 'nosniff', 'x-ua-compatible': 'IE=edge', 'Pragma': 'No-cache', 'Cache-Control': 'max-age=0, no-cache, no-store, must-revalidate', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'Strict-Transport-Security': 'max-age=47474747; includeSubDomains; preload', 'Vary': 'Content-Type,Cookie,Referer,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent', 'x-amz-rid': 'VSQH02FQE03CH7WKJJJG', 'p3p': 'policyref="http://www.amazon.com/w3c/p3p.xml",CP="CAO DSP LAW CUR ADM IVAo IVDo CONo OTPo OUR DELi PUBi OTRi BUS PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA HEA PRE LOC GOV OTC "', 'X-Frame-Options': 'SAMEORIGIN', 'Content-Encoding': 'gzip', 'Date': 'Thu, 16 Jul 2020 11:15:43 GMT', 'Content-Length': '26025', 'Connection': 'keep-alive', 'Set-Cookie': 'ap-fid=""; Domain=.amazon.com; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/ap/; Secure', 'Set-Cookie': 'session-id=137-1522117-0788223; Domain=.amazon.com; Expires=Fri, 16-Jul-2021 11:15:43 GMT; Path=/; Secure', 'Set-Cookie': 'session-id-time=2225618143l; Domain=.amazon.com; Expires=Fri, 16-Jul-2021 11:15:43 GMT; Path=/; Secure', 'Set-Cookie': 'ubid-main=131-8080594-3374564; Domain=.amazon.com; Expires=Fri, 16-Jul-2021 11:15:43 GMT; Path=/; Secure', 'Set-Cookie': 'session-token=xxxx; Domain=.amazon.com; Expires=Fri, 16-Jul-2021 11:15:43 GMT; Path=/; Secure')>
2020-07-16 21:15:43 DEBUG (MainThread) [alexapy.alexalogin] Processing https://www.amazon.com/ap/signin
2020-07-16 21:15:44 DEBUG (MainThread) [alexapy.alexalogin] Error message: There was a problem
            Enter the characters as they are given in the challenge.

2020-07-16 21:15:44 DEBUG (MainThread) [alexapy.alexalogin] Captcha requested
2020-07-16 21:15:44 DEBUG (MainThread) [alexapy.alexalogin] Found post url to https://www.amazon.com/ap/signin
2020-07-16 21:15:44 DEBUG (MainThread) [custom_components.alexa_media.configurator] Testing login status: {'error_message': 'There was a problem\n            Enter the characters as they are given in the challenge.\n          ', 'captcha_required': True, 'captcha_image_url': 'https://opfcaptcha-prod.s3.amazonaws.com/f488346a9a1b4471a0c817176cf156c9.jpg?AWSAccessKeyId=xxxxx&Expires=1594898443&Signature=xxxxx'}
2020-07-16 21:15:44 DEBUG (MainThread) [custom_components.alexa_media.configurator] Creating configurator to request captcha
2020-07-16 21:16:25 DEBUG (MainThread) [custom_components.alexa_media.configurator] Configurator closed for Status: {'error_message': 'There was a problem\n            Enter the characters as they are given in the challenge.\n          ', 'captcha_required': True, 'captcha_image_url': 'https://opfcaptcha-prod.s3.amazonaws.com/f488346a9a1b4471a0c817176cf156c9.jpg?AWSAccessKeyId=xxxxx&Expires=1594898443&Signature=xxxxx'}
Callback_data: {'captcha': '53e8fa'}
2020-07-16 21:16:25 DEBUG (MainThread) [alexapy.alexalogin] No valid cookies for log in; using credentials
2020-07-16 21:16:25 DEBUG (MainThread) [alexapy.alexalogin] Loaded last request to https://www.amazon.com/ap/signin
2020-07-16 21:16:25 DEBUG (MainThread) [alexapy.alexalogin] Processing https://www.amazon.com/ap/signin
2020-07-16 21:16:25 DEBUG (MainThread) [alexapy.alexalogin] Error message: There was a problem
            Enter the characters as they are given in the challenge.

2020-07-16 21:16:25 DEBUG (MainThread) [alexapy.alexalogin] Captcha requested
2020-07-16 21:16:25 DEBUG (MainThread) [alexapy.alexalogin] Found post url to https://www.amazon.com/ap/signin
2020-07-16 21:16:25 DEBUG (MainThread) [alexapy.alexalogin] Preparing post to https://www.amazon.com/ap/signin with input data: {'captcha': '53e8fa'}
2020-07-16 21:16:26 DEBUG (MainThread) [alexapy.alexalogin] POST: redirected from
https://www.amazon.com/ap/signin
2020-07-16 21:16:26 DEBUG (MainThread) [alexapy.alexalogin] GET: redirected from
https://www.amazon.com/ap/challenge?ie=UTF8&arb=a24e1d9f-f81f-475a-9582-f8900b791f2a
2020-07-16 21:16:26 DEBUG (MainThread) [alexapy.alexalogin] GET:
https://www.amazon.com/ap/cvf/approval?arb=50c8479b-bccb-4382-ae81-a9b7298ff830&openid.assoc_handle=amzn_dp_project_dee&pageId=amzn_dp_project_dee&openid.return_to=https://www.amazon.com/ap/signin?ie%3DUTF8%26clientContext%3D131-8080594-3374564%26arb%3Dd2083ba1-8aab-4ba5-9bfe-c31a78f8ff92%26showRmrMe%3D1%26use_global_authentication%3Dfalse%26openid.return_to%3Dhttps%253A%252F%252Falexa.amazon.com%252F%26openid.identity%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.assoc_handle%3Damzn_dp_project_dee%26openid.mode%3Dcheckid_setup%26use_audio_captcha%3Dfalse%26pageId%3Damzn_dp_project_dee%26openid.claimed_id%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.ns%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0 returned 200:OK with response <CIMultiDictProxy('Content-Type': 'text/html;charset=UTF-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Server': 'Server', 'Date': 'Thu, 16 Jul 2020 11:16:26 GMT', 'Set-Cookie': 'ubid-main=131-8080594-3374564; Domain=.amazon.com; Expires=Fri, 16-Jul-2021 11:16:26 GMT; Path=/; Secure', 'Pragma': 'no-cache', 'Expires': 'Thu, 01 Jan 1970 00:00:00 GMT', 'Cache-Control': 'no-cache', 'Cache-Control': 'no-store', 'Content-Language': 'en-US', 'Content-Encoding': 'gzip', 'Vary': 'accept-encoding,Content-Type,Cookie,Referer,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent', 'Strict-Transport-Security': 'max-age=47474747; includeSubDomains; preload', 'x-amz-rid': 'JR70CKS4SA04MY2K4SBX', 'X-Frame-Options': 'SAMEORIGIN', 'X-Cache': 'Miss from cloudfront', 'Via': '1.1 4507fe7df8410726135c5afe328b2149.cloudfront.net (CloudFront)', 'X-Amz-Cf-Pop': 'SYD1-C2', 'X-Amz-Cf-Id': 'lbvqLt_BVm6YeMBRGu8likyEv9WJ5ZNZU5gyoofGLo0vRLKPtPYnwQ==')>
2020-07-16 21:16:27 DEBUG (MainThread) [alexapy.alexalogin] Processing https://www.amazon.com/ap/cvf/approval?arb=50c8479b-bccb-4382-ae81-a9b7298ff830&openid.assoc_handle=amzn_dp_project_dee&pageId=amzn_dp_project_dee&openid.return_to=https://www.amazon.com/ap/signin?ie%3DUTF8%26clientContext%3D131-8080594-3374564%26arb%3Dd2083ba1-8aab-4ba5-9bfe-c31a78f8ff92%26showRmrMe%3D1%26use_global_authentication%3Dfalse%26openid.return_to%3Dhttps%253A%252F%252Falexa.amazon.com%252F%26openid.identity%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.assoc_handle%3Damzn_dp_project_dee%26openid.mode%3Dcheckid_setup%26use_audio_captcha%3Dfalse%26pageId%3Damzn_dp_project_dee%26openid.claimed_id%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.ns%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0
2020-07-16 21:16:27 DEBUG (MainThread) [alexapy.alexalogin] Javascript Authentication page detected: Authentication required. Please respond to the notification sent to:

Email address
         xxxx
Application
         xxxx

2020-07-16 21:16:27 DEBUG (MainThread) [alexapy.alexalogin] Found url for openid.return_to https://www.amazon.com/ap/signin?ie=UTF8&clientContext=131-8080594-3374564&arb=d2083ba1-8aab-4ba5-9bfe-c31a78f8ff92&showRmrMe=1&use_global_authentication=false&openid.return_to=https%3A%2F%2Falexa.amazon.com%2F&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=amzn_dp_project_dee&openid.mode=checkid_setup&use_audio_captcha=false&pageId=amzn_dp_project_dee&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0
2020-07-16 21:16:27 DEBUG (MainThread) [custom_components.alexa_media.configurator] Testing login status: {'force_get': True, 'message': 'Authentication required. Please respond to the notification sent to:\nEmail address<EMAIL_ADDRESS>AmazonShopping, samsung SM-G950F\n'}
2020-07-16 21:16:27 DEBUG (MainThread) [custom_components.alexa_media.configurator] Creating configurator to wait for user action
2020-07-16 21:17:06 DEBUG (MainThread) [custom_components.alexa_media.configurator] Configurator closed for Status: {'force_get': True, 'message': 'Authentication required. Please respond to the notification sent to:\nEmail address<EMAIL_ADDRESS>AmazonShopping, samsung SM-G950F\n'}
Callback_data: {'captcha': '53e8fa'}
2020-07-16 21:17:06 DEBUG (MainThread) [alexapy.alexalogin] No valid cookies for log in; using credentials
2020-07-16 21:17:06 DEBUG (MainThread) [alexapy.alexalogin] Loaded last request to https://www.amazon.com/ap/cvf/approval?arb=50c8479b-bccb-4382-ae81-a9b7298ff830&openid.assoc_handle=amzn_dp_project_dee&pageId=amzn_dp_project_dee&openid.return_to=https://www.amazon.com/ap/signin?ie%3DUTF8%26clientContext%3D131-8080594-3374564%26arb%3Dd2083ba1-8aab-4ba5-9bfe-c31a78f8ff92%26showRmrMe%3D1%26use_global_authentication%3Dfalse%26openid.return_to%3Dhttps%253A%252F%252Falexa.amazon.com%252F%26openid.identity%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.assoc_handle%3Damzn_dp_project_dee%26openid.mode%3Dcheckid_setup%26use_audio_captcha%3Dfalse%26pageId%3Damzn_dp_project_dee%26openid.claimed_id%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.ns%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0
2020-07-16 21:17:06 DEBUG (MainThread) [alexapy.alexalogin] Processing https://www.amazon.com/ap/cvf/approval?arb=50c8479b-bccb-4382-ae81-a9b7298ff830&openid.assoc_handle=amzn_dp_project_dee&pageId=amzn_dp_project_dee&openid.return_to=https://www.amazon.com/ap/signin?ie%3DUTF8%26clientContext%3D131-8080594-3374564%26arb%3Dd2083ba1-8aab-4ba5-9bfe-c31a78f8ff92%26showRmrMe%3D1%26use_global_authentication%3Dfalse%26openid.return_to%3Dhttps%253A%252F%252Falexa.amazon.com%252F%26openid.identity%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.assoc_handle%3Damzn_dp_project_dee%26openid.mode%3Dcheckid_setup%26use_audio_captcha%3Dfalse%26pageId%3Damzn_dp_project_dee%26openid.claimed_id%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.ns%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0
2020-07-16 21:17:06 DEBUG (MainThread) [alexapy.alexalogin] Javascript Authentication page detected: Authentication required. Please respond to the notification sent to:

Email address
          xxxx
Application
          xxxx

2020-07-16 21:17:06 DEBUG (MainThread) [alexapy.alexalogin] Found url for openid.return_to https://www.amazon.com/ap/signin?ie=UTF8&clientContext=xxxx&arb=xxxx&showRmrMe=1&use_global_authentication=false&openid.return_to=https%3A%2F%2Falexa.amazon.com%2F&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=amzn_dp_project_dee&openid.mode=checkid_setup&use_audio_captcha=false&pageId=amzn_dp_project_dee&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0
2020-07-16 21:17:06 DEBUG (MainThread) [custom_components.alexa_media.configurator] Testing login status: {'force_get': True, 'message': 'Authentication required. Please respond to the notification sent to:\nEmail address xxxxx\n xxxxx\n'}
2020-07-16 21:17:06 DEBUG (MainThread) [custom_components.alexa_media.configurator] Creating configurator to wait for user action
2020-07-16 21:17:12 DEBUG (MainThread) [custom_components.alexa_media.configurator] Configurator closed for Status: {'force_get': True, 'message': 'Authentication required. Please respond to the notification sent to:\nEmail address xxxxx\n xxxxx\n'}
Callback_data: {'captcha': '53e8fa'}
2020-07-16 21:17:12 DEBUG (MainThread) [alexapy.alexalogin] No valid cookies for log in; using credentials
2020-07-16 21:17:12 DEBUG (MainThread) [alexapy.alexalogin] Loaded last request to https://www.amazon.com/ap/cvf/approval?arb=50c8479b-bccb-4382-ae81-a9b7298ff830&openid.assoc_handle=amzn_dp_project_dee&pageId=amzn_dp_project_dee&openid.return_to=https://www.amazon.com/ap/signin?ie%3DUTF8%26clientContext%26showRmrMe%3D1%26use_global_authentication%3Dfalse%26openid.return_to%3Dhttps%253A%252F%252Falexa.amazon.com%252F%26openid.identity%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.assoc_handle%3Damzn_dp_project_dee%26openid.mode%3Dcheckid_setup%26use_audio_captcha%3Dfalse%26pageId%3Damzn_dp_project_dee%26openid.claimed_id%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.ns%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0
2020-07-16 21:17:12 DEBUG (MainThread) [alexapy.alexalogin] Processing https://www.amazon.com/ap/cvf/approval?arb=50c8479b-bccb-4382-ae81-a9b7298ff830&openid.assoc_handle=amzn_dp_project_dee&pageId=amzn_dp_project_dee&openid.return_to=https://www.amazon.com/ap/signin?ie%3DUTF8%26clientContext%3D131-8080594-3374564%26arb%3Dd2083ba1-8aab-4ba5-9bfe-c31a78f8ff92%26showRmrMe%3D1%26use_global_authentication%3Dfalse%26openid.return_to%3Dhttps%253A%252F%252Falexa.amazon.com%252F%26openid.identity%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.assoc_handle%3Damzn_dp_project_dee%26openid.mode%3Dcheckid_setup%26use_audio_captcha%3Dfalse%26pageId%3Damzn_dp_project_dee%26openid.claimed_id%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.ns%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0
2020-07-16 21:17:12 DEBUG (MainThread) [alexapy.alexalogin] Javascript Authentication page detected: Authentication required. Please respond to the notification sent to:

Email address
          xxxx
Application
          xxxx

2020-07-16 21:17:12 DEBUG (MainThread) [alexapy.alexalogin] Found url for openid.return_to https://www.amazon.com/ap/signin?ie=UTF8&clientContext=131-8080594-3374564&arb=d2083ba1-8aab-4ba5-9bfe-c31a78f8ff92&showRmrMe=1&use_global_authentication=false&openid.return_to=https%3A%2F%2Falexa.amazon.com%2F&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=amzn_dp_project_dee&openid.mode=checkid_setup&use_audio_captcha=false&pageId=amzn_dp_project_dee&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0
2020-07-16 21:17:12 DEBUG (MainThread) [custom_components.alexa_media.configurator] Testing login status: {'force_get': True, 'message': 'Authentication required. Please respond to the notification sent to:\nEmail address xxxxx\n xxxxx\n'}
2020-07-16 21:17:12 DEBUG (MainThread) [custom_components.alexa_media.configurator] Creating configurator to wait for user action
2020-07-16 21:18:39 DEBUG (MainThread) [custom_components.alexa_media.configurator] Configurator closed for Status: {'force_get': True, 'message': 'Authentication required. Please respond to the notification sent to:\nEmail address xxxxx\n xxxxx\n'}
Callback_data: {'captcha': '53e8fa'}
2020-07-16 21:18:39 DEBUG (MainThread) [alexapy.alexalogin] No valid cookies for log in; using credentials
2020-07-16 21:18:39 DEBUG (MainThread) [alexapy.alexalogin] Loaded last request to https://www.amazon.com/ap/cvf/approval?arb=50c8479b-bccb-4382-ae81-a9b7298ff830&openid.assoc_handle=amzn_dp_project_dee&pageId=amzn_dp_project_dee&openid.return_to=https://www.amazon.com/ap/signin?ie%3DUTF8%26clientContext%3D131-8080594-3374564%26arb%3Dd2083ba1-8aab-4ba5-9bfe-c31a78f8ff92%26showRmrMe%3D1%26use_global_authentication%3Dfalse%26openid.return_to%3Dhttps%253A%252F%252Falexa.amazon.com%252F%26openid.identity%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.assoc_handle%3Damzn_dp_project_dee%26openid.mode%3Dcheckid_setup%26use_audio_captcha%3Dfalse%26pageId%3Damzn_dp_project_dee%26openid.claimed_id%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.ns%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0
2020-07-16 21:18:39 DEBUG (MainThread) [alexapy.alexalogin] Processing https://www.amazon.com/ap/cvf/approval?arb=50c8479b-bccb-4382-ae81-a9b7298ff830&openid.assoc_handle=amzn_dp_project_dee&pageId=amzn_dp_project_dee&openid.return_to=https://www.amazon.com/ap/signin?ie%3DUTF8%26clientContext%3D131-8080594-3374564%26arb%3Dd2083ba1-8aab-4ba5-9bfe-c31a78f8ff92%26showRmrMe%3D1%26use_global_authentication%3Dfalse%26openid.return_to%3Dhttps%253A%252F%252Falexa.amazon.com%252F%26openid.identity%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.assoc_handle%3Damzn_dp_project_dee%26openid.mode%3Dcheckid_setup%26use_audio_captcha%3Dfalse%26pageId%3Damzn_dp_project_dee%26openid.claimed_id%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0%252Fidentifier_select%26openid.ns%3Dhttp%253A%252F%252Fspecs.openid.net%252Fauth%252F2.0
2020-07-16 21:18:39 DEBUG (MainThread) [alexapy.alexalogin] Javascript Authentication page detected: Authentication required. Please respond to the notification sent to:

Email address
          xxxx
Application
          xxxx

2020-07-16 21:18:39 DEBUG (MainThread) [alexapy.alexalogin] Found url for openid.return_to https://www.amazon.com/ap/signin?ie=UTF8&clientContext=131-8080594-3374564&arb=d2083ba1-8aab-4ba5-9bfe-c31a78f8ff92&showRmrMe=1&use_global_authentication=false&openid.return_to=https%3A%2F%2Falexa.amazon.com%2F&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=amzn_dp_project_dee&openid.mode=checkid_setup&use_audio_captcha=false&pageId=amzn_dp_project_dee&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0
2020-07-16 21:18:39 DEBUG (MainThread) [custom_components.alexa_media.configurator] Testing login status: {'force_get': True, 'message': 'Authentication required. Please respond to the notification sent to:\nEmail address xxxxx\nxxxxx'}
2020-07-16 21:18:39 DEBUG (MainThread) [custom_components.alexa_media.configurator] Creating configurator to wait for user action

Just would like to mention that I was having problems when logging in with the captcha in a loop. While I was having these problems, I receive another query to authorize another alexa account from another completely different computer and amazon account. When try to authorize that machine, it works on first try... I check possible differences and noticed I have Two Factor Authorization (2FA) activated in the amazon account that worked.
So I enter my amazon account in which I was not being able to autorize, and activate (at amazon.es) the 2FA process. After that went to hassio to authorize and check again the notification (after reboot of course) and CONFIGURE button, etc. New window with different text appears mentioning the 2FA process. I enter first the captcha and second the 6 digit number sent to my phone. I passed the process this time without problems.
It doesn't solve the problem of course... but could be a way to circumvent it.

@emansih @user514  Thanks, but please use the right issue #807; it's off topic in this thread.  We're stuck because we don't have testers to resolve it. As noted in that thread, 2FA was always a workaround.

I have this issue as well, haven’t seen any related logs though. But I’ve had to sign in like 4 times today so far.

Same here with latest version of Hass and Alexa media player. Seems like every few hours will need to sign in...

Absent some logs showing it's a component issue, this looks like an Amazon issue. You can try increasing the scan_interval to try to avoid hitting the Amazon servers too much but there may be nothing we can do.

Closing this until you're ready to proceed. Thanks.


Optimise TokenMap to only hold either a typed or parsed AST token

Description
This PR optimizes the TokenMap structure by modifying the Token type to store either a parsed or typed AST token, but not both simultaneously. Parsed tokens are now only accessible if a typed token does not exist. Previously, both parsed and typed variants were stored which was inefficient in terms of memory usage.
Key changes:

Replaced separate parsed and typed fields in Token with a single ast_node field using an enum TokenAstNode
Added helper methods as_parsed() and as_typed() to safely access the token variants
Updated all token creation and access code throughout the codebase to use the new structure
Refactored the attributes handling code to properly check both parsed and typed variants

Works towards the memory optimization goals in #6226.
Checklist

[x] I have linked to any relevant issues.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have updated the documentation where relevant (API docs, the reference, and the Sway book).

[ ] If my change requires substantial documentation changes, I have requested support from the DevRel team

[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
[x] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[x] I have requested a review from the relevant team or maintainers.

While reading this a question popped in my head, I wonder what is the average number of tokens at a given time in the token map.
If this is sufficiently high, maybe using unions instead of enums in appropriate places will help reduce the memory usage even more at the cost of some code quality (we will need to track the variant ourselves in the code explicitly). I think the enum variant is 8 byte per Token. So the total number of tokens allocated should be very large to see meaningful gains from this change >100k. Also it is possible that rust compiler already optimizes this and compresses some of the variant effects. So the actual effect of the enum might not be directly 8 bytes.

That's an interesting point, thanks for raising it. I just did a few quick tests to see how big the token map gets on various projects.
sway repo counter example: 354
FUSD protocol-manager-contract: 1378
FUSD libraries project: 2876
Looks like we are sub 10,000 tokens even for the largest sway projects I have for stress testing, so we should be fine for now. Thanks for the suggestion though :)


Switch to jinja2

Use Jinja2 as template engine for our project to benefit from a more matured syntax.

Not necessary, we don't have a huge benefit anymore. Closing.


listener: add integration test for in-place update listener filters order

Signed-off-by: He Jie Xu<EMAIL_ADDRESS>Commit Message: listener: add integration test for in-place update listener filters order
Additional Description:
Risk Level: low
Testing: integration test
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a
Part of Fixes #20100

cc @lambdai


networkx version potential incompatibilty

In the output-analysis branch, we are beginning to use networkx functions. However, v2 is not compatible with v1.11. Should the version be specified in a requirements.txt file?

Yes, I agree that we should specify compatible package versions for all external packages we depend on.  For networkx, I propose we have our code be compatible with the latest version (2.5.x).
The oi2 branch adds a conda environment file environment.yml instead of a requirements.txt file and specifies networkx=2.5.  It then runs the pytest tests in that environment.  Would that address this issue?


BUG: HistoryResponse types switched

HistoryResponse comes through to Swift as:
public var account: AnyCodable
public var history: [String]

which should be reversed to
public var account: String
public var history: [AnyCodable]

@samdowd can you confirm if this and #346 are fixed for you?

@beeman yes, these are fixed now


separate app from library?

at the moment both taggle library and taggle (demo) app are mixed. However, with increasing demo specific attributes (datasets #135, header #134) and dependencies we should think of separating both.
like: http://github.com/Caleydo/lineupjs and http://github.com/Caleydo/lineup

done. see taggle-daily.caleydoapp.org and https://github.com/Caleydo/lineupjs/tree/develop.


all: increased toolchain binary sizes

Compared to 1.23, binary sizes of most toolchain binaries have increased :
linux | amd64 |   |   |   |   |
-- | -- | -- | -- | -- | -- | --
Files | Go1.23 (B) | Tip (B) | % (+/-) |   | Go1.23 (M) | Tip (M)
go | 13387863 | 19362295 | +45 |   | 12.76 | 18.46
gofmt | 2850696 | 4108237 | +44 |   | 2.71 | 3.91
addr2line | 2814484 | 4547767 | +62 |   | 2.68 | 4.3
asm | 4106917 | 6335065 | +54 |   | 3.91 | 6.04
buildid | 2271515 | 3656700 | +61 |   | 2.16 | 3.48
cgo | 4032102 | 6009954 | +49 |   | 3.84 | 5.73
compile | 19798633 | 28201144 | +42 |   | 18.88 | 26.89
covdata | 2949306 | 4191031 | +42 |   | 2.81 | 3.99
cover | 4567071 | 6723952 | +47 |   | 4.35 | 6.41
dist | 2984094 | 4261242 | +43 |   | 2.84 | 4.06
distpack | 2397807 | 3743405 | +56 |   | 2.28 | 3.56
doc | 3392398 | 4821225 | +42 |   | 3.23 | 4.59
fix | 2861911 | 4154515 | +45 |   | 2.72 | 3.96
link | 5678421 | 8691638 | +53 |   | 5.41 | 8.28
nm | 2776817 | 4490895 | +62 |   | 2.64 | 4.28
objdump | 3826204 | 6053727 | +58 |   | 3.64 | 5.77
pack | 2030214 | 2982774 | +47 |   | 1.93 | 2.84
pprof | 12382808 | 18451654 | +49 |   | 11.80 | 17.59
preprofile | 2127222 | 3140546 | +48 |   | 2.02 | 2.99
test2json | 2295467 | 3392933 | +48 |   | 2.18 | 3.23
trace | 12606079 | 17061695 | +35 |   | 12.02 | 16.27
vet | 7194248 | 10024784 | +39 |   | 6.86 | 9.56

Related Issues

all: increased toolchain binary sizes #68109 (closed)
all: understand binary size changes vs 1.14 #38694
all: binary size regression #67588 (closed)

Related Code Changes

cmd/compile,link: use "go.." for compiler genereated types
cmd/compile: first cut at exporting position info

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Those seem fairly large. I preemptively marked this as a release blocker, but maybe OK after RC1. Thoughts?

CC @golang/compiler

Is this something about toolchain binaries in particular? I checked a few binaries in our private codebase (all in the 30-60 MB range) and they only get a bit larger between 1.23 and tip (<2%).

There isn't much more code.
objdump -d on arm64 says there are only 3% more instructions in cmd/go on tip than 1.23.

Looks like dwarf, 1.23.2 binaries have their dwarf stripped, tip binaries do not.
I thought we stripped toolchain binaries. Maybe only for release?

Yeah, we strip toolchain binaries for releases https://cs.opensource.google/go/go/+/master:src/cmd/dist/build.go;l=1393

These numbers look much better after using distpack (the proper flags). I will update the numbers and remove the release blocker label.

Locally I see the following for gofmt:
% objdump -h /Users/taking/sdk/go1.23.1/bin/gofmt

/Users/taking/sdk/go1.23.1/bin/gofmt:   file format mach-o arm64

Sections:
Idx Name            Size     VMA              Type
  0 __text          001209c4<PHONE_NUMBER>001000 TEXT
  1 __symbol_stub1  0000030c<PHONE_NUMBER>1219e0 TEXT
  2 __rodata        00038fee<PHONE_NUMBER>121d00 DATA
  3 __rodata        0003e800<PHONE_NUMBER>15c000 DATA
  4 __typelink      00000c34<PHONE_NUMBER>19a800 DATA
  5 __itablink      00000548<PHONE_NUMBER>19b440 DATA
  6 __gosymtab      00000000<PHONE_NUMBER>19b988 DATA
  7 __gopclntab     000bff10<PHONE_NUMBER>19b9a0 DATA
  8 __go_buildinfo  00000220<PHONE_NUMBER>25c000 DATA
  9 __nl_symbol_ptr 00000210<PHONE_NUMBER>25c220 DATA
 10 __noptrdata     0000b360<PHONE_NUMBER>25c440 DATA
 11 __data          00006c30<PHONE_NUMBER>2677a0 DATA
 12 __bss           00026760<PHONE_NUMBER>26e3e0 BSS
 13 __noptrbss      000035a0<PHONE_NUMBER>294b40 BSS
% objdump -h /Users/taking/sdk/gotip/bin/gofmt

/Users/taking/sdk/gotip/bin/gofmt:      file format mach-o arm64

Sections:
Idx Name             Size     VMA              Type
  0 __text           0011fd44<PHONE_NUMBER>001000 TEXT
  1 __symbol_stub1   00000318<PHONE_NUMBER>120d60 TEXT
  2 __rodata         0003ac60<PHONE_NUMBER>121080 DATA
  3 __rodata         00042d40<PHONE_NUMBER>15c000 DATA
  4 __typelink       00000cdc<PHONE_NUMBER>19ed40 DATA
  5 __itablink       00000550<PHONE_NUMBER>19fa20 DATA
  6 __gosymtab       00000000<PHONE_NUMBER>19ff70 DATA
  7 __gopclntab      000c6ca0<PHONE_NUMBER>19ff80 DATA
  8 __go_buildinfo   00000100<PHONE_NUMBER>268000 DATA
  9 __go_fipsinfo    00000078<PHONE_NUMBER>268100 DATA
 10 __nl_symbol_ptr  00000218<PHONE_NUMBER>268178 DATA
 11 __noptrdata      0000ab82<PHONE_NUMBER>2683a0 DATA
 12 __data           00006db2<PHONE_NUMBER>272f40 DATA
 13 __bss            00026890<PHONE_NUMBER>279d00 BSS
 14 __noptrbss       00003580<PHONE_NUMBER>2a05a0 BSS
 15 __zdebug_abbrev  0000014a<PHONE_NUMBER>2a4000 DATA, DEBUG
 16 __zdebug_line    00036890<PHONE_NUMBER>2a414a DATA, DEBUG
 17 __zdebug_frame   0000ba53<PHONE_NUMBER>2da9da DATA, DEBUG
 18 __debug_gdb_scri 00000034<PHONE_NUMBER>2e642d DATA, DEBUG
 19 __zdebug_info    0006f772<PHONE_NUMBER>2e6461 DATA, DEBUG
 20 __zdebug_loc     0003ff6c<PHONE_NUMBER>355bd3 DATA, DEBUG
 21 __zdebug_ranges  000130f5<PHONE_NUMBER>395b3f DATA, DEBUG

The difference in the binary sizes is 1128962 (locally).  The extra sections in the gotip copy of gofmt that are not in 1.23.1 copy add up to 1068084 bytes (95%).

The release binaries look much better in terms of the size increase (built with make.bash -distpack):
linux | amd64 |   |   |   |   |
-- | -- | -- | -- | -- | -- | --
files | Go1.23 (bytes) | Tip (bytes) | % (+/-) |   | MB | MB
go | 13387863 | 14271934 | 7 |   | 12.76766109 | 13.6107769
gofmt | 2850696 | 2922116 | 3 |   | 2.718635559 | 2.786746979
addr2line | 2814484 | 3365550 | 20 |   | 2.684101105 | 3.209638596
asm | 4106917 | 4675184 | 14 |   | 3.916661263 | 4.458602905
buildid | 2271515 | 2591643 | 14 |   | 2.166285515 | 2.471583366
cgo | 4032102 | 4365513 | 8 |   | 3.845312119 | 4.163277626
compile | 19798633 | 20899679 | 6 |   | 18.88144779 | 19.93148708
covdata | 2949306 | 2999246 | 2 |   | 2.812677383 | 2.860303879
cover | 4567071 | 4947863 | 8 |   | 4.355498314 | 4.718649864
dist | 2984094 | 3051249 | 2 |   | 2.845853806 | 2.909897804
distpack | 2397807 | 2663964 | 11 |   | 2.286726952 | 2.540554047
doc | 3392398 | 3453200 | 2 |   | 3.235242844 | 3.293228149
fix | 2861911 | 2959114 | 3 |   | 2.729331017 | 2.822031021
link | 5678421 | 6242053 | 10 |   | 5.415364265 | 5.952885628
nm | 2776817 | 3332582 | 20 |   | 2.648179054 | 3.178197861
objdump | 3826204 | 4621606 | 21 |   | 3.648952484 | 4.407506943
pack | 2030214 | 2092973 | 3 |   | 1.936162949 | 1.996014595
pprof | 12382808 | 13910725 | 12 |   | 11.80916595 | 13.26630116
preprofile | 2127222 | 2208161 | 4 |   | 2.028676987 | 2.105866432
test2json | 2295467 | 2393740 | 4 |   | 2.189127922 | 2.282848358
trace | 12606079 | 13407966 | 6 |   | 12.02209377 | 12.78683281
vet | 7194248 | 7469567 | 4 |   | 6.860969543 | 7.123534203

Thanks @cagedmantis .
objdump's increase is somewhat reasonable, as we added more disassembler support (e.g. s390x disassembler). pprof supports disassembling, so it is probably also reasonable.
The disassembler symbols (golang.org/x/arch stuff) also show up in nm and addr2line, causing them to increase as well. In theory I don't think they need disassembler symbols, so this is unfortunate. I'll see if we can remove those symbols from nm and addr2line.

fwiw, I've found that  evcc Linux binary slightly shrinks from 1.23 to tip: 91485682 vs 90495826 bytes.

After nm, addr2line, objdump, and pprof, the next ones are asm and buildid.
One part that they depend on now but not in Go 1.23 is crypto FIPS stuff, as they perform various crypto hash operations. In 1.23 most of the hash operations use notsha256, which is deleted in CL 610599 and switched to real sha256, which now depends on FIPS things. We get some binary size back if we revert back to notsha256. Not completely, though.
Another place for at least cmd/asm is that they now contain a number of different instantiations of slices.Sort routines. The old code was using sort.Sort or sort.Slice, which is not generic. I guess this increase is okay...

I did another run with GOOS=linux GOARCH=amd64 make.bash -distpack
                    go1.23.3           tip           delta      %delta
          go	  13397287	  14280843	    883556	6.60
       gofmt	   2855408	   2922116	     66708	2.34
   addr2line	   2819123	   2627110	   -192013	-6.81
         asm	   4115652	   4675046	    559394	13.59
     buildid	   2280250	   2591505	    311255	13.65
         cgo	   4040817	   4365375	    324558	8.03
     compile	  19803234	  20934109	   1130875	5.71
     covdata	   2953945	   2999246	     45301	1.53
       cover	   4575841	   4943679	    367838	8.04
         doc	   3401113	   3453200	     52087	1.53
         fix	   2866530	   2959114	     92584	3.23
        link	   5683028	   6246132	    563104	9.91
          nm	   2781456	   2608126	   -173330	-6.23
     objdump	   3830843	   4621684	    790841	20.64
        pack	   2030757	   2092973	     62216	3.06
       pprof	  12387591	  13915107	   1527516	12.33
  preprofile	   2127765	   2208161	     80396	3.78
   test2json	   2300013	   2393740	     93727	4.08
       trace	  12610862	  13412106	    801244	6.35
         vet	   7194840	   7469230	    274390	3.81
----------------------------------------------------------------------
       total	 114056355	 121718602	   7662247	6.72

The changes we inspected are all more or less expected (supporting more features, reasonable refactoring, etc.). I don't think we need to do anything more on this at the moment. Thanks.


Update kazoo version to make it compatible with Python 3.7

This also bumps the SolrClient version to 0.3.0.

can we please merge and release the new version? Need this for one of our task.
@nickvasilyev


[Query] Which dependency type is this using?

Description
I've been migrating projects from Microsoft.Azure.ServiceBus to Azure.Messaging.ServiceBus and upgrading some other projects already using Azure.Messaging.Servicebus. My telemetry is showing different dependency types for the same dependency name. I'll focus on ServiceBusSender.Send.
Some of them have the type being Azure Service Bus. Others have the type as servicebus.
What package or version is specifying the type as Azure Service Bus? I know Azure.Messaging.ServiceBus has the type as a constant defined here: https://github.com/Azure/azure-sdk-for-net/blob/62f2223e46c33825628443d11b8267de4e72a1c6/sdk/servicebus/Azure.Messaging.ServiceBus/src/Diagnostics/DiagnosticProperty.cs#:~:text=public const string ServiceBusServiceContext %3D "servicebus"%3B

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Can you provide a little more detail, such as a screenshot of the issue you are seeing? Also, what is the version of the Application Insights SDK that you are using?
When testing, I always see Azure Service Bus for ServiceBusSender.Send.

There was an update in 2.21.0 that fixed an issue with dependency tracking for Service Bus. Can you make sure you are using that version and try?

Can you tell me which Type I'm suppose to be looking for? Azure Service Bus or servicebus?

Can you tell me which Type I'm suppose to be looking for? Azure Service Bus or servicebus?

I would expect the dependency type to be Azure Service Bus if you are using the latest App Insights SDK version 2.21.0.


Update CHANGELOG for v0.5.0

A release of v0.5.0 somehow happend in parallel :slightly_smiling_face:

The release was for cortextool so it isn't affected by this binary.


Adding Domains.Google.com as an option for DNS-01

I am self hosting and my domain name provider is not listed in your options for DNS-01 domains.google.com.
I believe it is possible to be implemented now.
based on this pr for acme.
https://github.com/acmesh-official/acme.sh/pull/4546
Also this documentation
https://developers.google.com/domains/acme-dns/reference/rest
I'm willing to contribute to help get the feature out. I just don't know where it would need to be implemented in the code.
/kind feature

Hi, thanks for opening the issue.
I had a brief look at the docs to understand whether the ACME Google Domains acts as a compliant ACME server. It is not clear to me from the docs, although I did not read it very thoroughly.
If it does act like an ACME server you should already be able to use it with the ACME issuer.
If it does not, the solution would be to write an external DNS webhook for cert-manager  https://github.com/cert-manager/webhook-example.
We no longer add support for additional DNS providers in-tree for maintainability reasons

That makes  sense with maintainability aspect. I will try acme issuer.  If it works. Would I be able to update the documentation to help other know how to implement it?

Added a webhook for google domains here:
https://github.com/dmahmalat/cert-manager-webhook-google-domains


Update to Electron 2.0.x

https://github.com/Microsoft/vscode/issues/45542

try electron v3.0.0-beta.1 ?

@NateLing https://github.com/Microsoft/vscode/issues/52629


Use raw byte arrays in most cases instead of base58-encoding

In the process of getting to 100% code coverage, I was getting annoyed at how long it was taking the test suite to run - between 1 and 2 minutes.
A look at the profiler showed that we were spending a ton of time Base58-encoding binary data.
I like Base58 for usability reasons:

It's more compact than hexadecimal encoding
Unlike Base64 strings, a Base58 string contains only alphanumeric characters, so it can be selected with a double-click

But it turns out string encoding is expensive, and Base58 in particular starts to get really slow with data larger than 256 bytes.[^1]
Our internal data format doesn't need to match the human-facing format. We can use raw byte arrays internally, and only encode them when a user will see them.
This PR removes the Base58 encoding for all encrypted data. It also replaces JSON serialization/deserialization in Connection messages with msgpackr. As a result of these changes, all 400+ tests across the auth, crdx, and crypto packages now run on my creaky laptop in under 20 seconds.
We're still using Base58 for small things like invitation seeds and cryptographic keys. There might be further gains still possible by leaving those as byte arrays internally, and just encoding them when we need to show them to humans.
[^1]:
https://digitalbazaar.github.io/base58-spec/

Current dependencies on/for this PR:

main

PR #85

PR #86

PR #87   👈

This stack of pull requests is managed by Graphite.


Possible to reduce Deployment target to 8.0?

Good evening,
I would like to add this repo through pod "PromiseKit/Alamofire" onto a project with a deployment target of 8.0, however the project's minimum deployment target is 9.0 (https://github.com/mxcl/PromiseKit/blob/master/PromiseKit.podspec#L39). I had to copy the files to my project. Is there any reasoning for not having the deployment target same as the PromiseKit? If not, would it be possible to reduce the deployment target 8.0 (https://github.com/mxcl/PromiseKit/blob/master/PromiseKit.podspec#L24)?
Thank you,
Bruno

I'm guessing there was a reason, but we should test it and see what happens. I do not have time to test it right now, perhaps you can?

Looks like we can.
Though notably, I had to rebuild Alamofire from Carthage as its deployment target was 9.0 with my old checkout, so presumably Alamofire 4.x was previously 9.0 also.
Will submit.

Hey, sorry I only caught up with your answers now.
I am using your source actively on a project and so, far there has been no issues from with any apple device with 8.0.
Thank you for taking a look into the issue


Error setting up new project as README.md

Environment

Elixir version (elixir -v): Elixir 1.16.3 (compiled with Erlang/OTP 26)
Phoenix version (mix deps): 1.7.14
Phoenix LiveView version (mix deps):
Beacon version (mix deps):
Operating system: fedora 40
Browsers on which you attempted to reproduce this bug (the more the merrier):

Actual behavior
I did
mix archive.install hex phx_new && mix archive.install hex igniter_new

and then
mix igniter.new my_app --install beacon,beacon_live_admin --with phx.new --beacon.site my_site
* creating my_app/lib/my_app/application.ex
* creating my_app/lib/my_app.ex
* creating my_app/lib/my_app_web/controllers/error_json.ex
* creating my_app/lib/my_app_web/endpoint.ex
* creating my_app/lib/my_app_web/router.ex
* creating my_app/lib/my_app_web/telemetry.ex
* creating my_app/lib/my_app_web.ex
* creating my_app/mix.exs
* creating my_app/README.md
* creating my_app/.formatter.exs
* creating my_app/.gitignore
* creating my_app/test/support/conn_case.ex
* creating my_app/test/test_helper.exs
* creating my_app/test/my_app_web/controllers/error_json_test.exs
* creating my_app/lib/my_app/repo.ex
* creating my_app/priv/repo/migrations/.formatter.exs
* creating my_app/priv/repo/seeds.exs
* creating my_app/test/support/data_case.ex
* creating my_app/lib/my_app_web/controllers/error_html.ex
* creating my_app/test/my_app_web/controllers/error_html_test.exs
* creating my_app/lib/my_app_web/components/core_components.ex
* creating my_app/lib/my_app_web/controllers/page_controller.ex
* creating my_app/lib/my_app_web/controllers/page_html.ex
* creating my_app/lib/my_app_web/controllers/page_html/home.html.heex
* creating my_app/test/my_app_web/controllers/page_controller_test.exs
* creating my_app/lib/my_app_web/components/layouts/root.html.heex
* creating my_app/lib/my_app_web/components/layouts/app.html.heex
* creating my_app/lib/my_app_web/components/layouts.ex
* creating my_app/priv/static/images/logo.svg
* creating my_app/lib/my_app/mailer.ex
* creating my_app/lib/my_app_web/gettext.ex
* creating my_app/priv/gettext/en/LC_MESSAGES/errors.po
* creating my_app/priv/gettext/errors.pot
* creating my_app/priv/static/robots.txt
* creating my_app/priv/static/favicon.ico
* creating my_app/assets/js/app.js
* creating my_app/assets/vendor/topbar.js
* creating my_app/assets/css/app.css
* creating my_app/assets/tailwind.config.js

Fetch and install dependencies? [Yn]
* running mix deps.get
* running mix assets.setup
* running mix deps.compile

We are almost there! The following steps are missing:

    $ cd my_app

Then configure your database in config/dev.exs and run:

    $ mix ecto.create

Start your Phoenix app with:

    $ mix phx.server

You can also run your app inside IEx (Interactive Elixir) as:

    $ iex -S mix phx.server

     warning: Macro.Env.define_alias/4 is undefined or private
     │
 178 │       case Macro.Env.define_alias(env, meta, arg, [trace: false] ++ opts) do
     │                      ~
     │
     └─ lib/spitfire/env.ex:178:22: Spitfire.Env.expand/3
     └─ lib/spitfire/env.ex:481:28: Spitfire.Env.alias_defmodule/3

     warning: Macro.Env.define_import/4 is undefined or private
     │
 209 │            {:ok, env} <- Macro.Env.define_import(env, meta, arg, [trace: false] ++ opts) do
     │                                    ~
     │
     └─ lib/spitfire/env.ex:209:36: Spitfire.Env.expand/3

     warning: Macro.Env.define_require/4 is undefined or private
     │
 193 │       case Macro.Env.define_require(env, meta, arg, [trace: false] ++ opts) do
     │                      ~
     │
     └─ lib/spitfire/env.ex:193:22: Spitfire.Env.expand/3

     warning: Macro.Env.expand_alias/4 is undefined or private
     │
 137 │     case Macro.Env.expand_alias(env, meta, list, trace: false) do
     │                    ~
     │
     └─ lib/spitfire/env.ex:137:20: Spitfire.Env.expand/3

     warning: Macro.Env.expand_import/5 is undefined or private
     │
 308 │     case Macro.Env.expand_import(env, meta, fun, arity,
     │                    ~
     │
     └─ lib/spitfire/env.ex:308:20: Spitfire.Env.expand/3

     warning: Macro.Env.expand_require/6 is undefined or private
     │
 274 │       case Macro.Env.expand_require(env, meta, module, fun, arity,
     │                      ~
     │
     └─ lib/spitfire/env.ex:274:22: Spitfire.Env.expand/3

== Compilation error in file lib/swoosh/adapters/xml/helpers.ex ==
** (ArgumentError) lib file xmerl/include/xmerl.hrl could not be found
    (elixir 1.16.3) lib/record/extractor.ex:41: Record.Extractor.from_lib_file/1
    (elixir 1.16.3) lib/record/extractor.ex:18: Record.Extractor.from_or_from_lib_file/1
    (elixir 1.16.3) lib/record/extractor.ex:5: Record.Extractor.extract/2
    lib/swoosh/adapters/xml/helpers.ex:5: (module)
could not compile dependency :swoosh, "mix compile" failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile swoosh --force", update it with "mix deps.update swoosh" or clean it with "mix deps.clean swoosh"
==> swoosh
Compiling 51 files (.ex)

== Compilation error in file lib/swoosh/adapters/xml/helpers.ex ==
** (ArgumentError) lib file xmerl/include/xmerl.hrl could not be found
    (elixir 1.16.3) lib/record/extractor.ex:41: Record.Extractor.from_lib_file/1
    (elixir 1.16.3) lib/record/extractor.ex:18: Record.Extractor.from_or_from_lib_file/1
    (elixir 1.16.3) lib/record/extractor.ex:5: Record.Extractor.extract/2
    lib/swoosh/adapters/xml/helpers.ex:5: (module)
could not compile dependency :swoosh, "mix compile" failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile swoosh --force", update it with "mix deps.update swoosh" or clean it with "mix deps.clean swoosh"

Expected behavior
Compile
Additional considerations
I am a newbie in the elixir world. Assume i make a silly mistake.

Hi @Talleyrand-34 that bug is related to swoosh compilation (a Phoenix dependency). I found these 2 issues very similar to your problem: https://github.com/swoosh/swoosh/issues?q=xmerl.hrl
You're on OTP 26 which is supported but if you installed it with a system package, then you might need to install https://packages.fedoraproject.org/pkgs/erlang/erlang-xmerl/ as well


How to open SCIAMACHY L1 .N1 using matlab ?

Hello, Thanks to your help last time, I was able to open the .N1 file of GOMOS.

But via coda I can't open SCIAMACHY's .N1 file, what should I do?

This product (L1 V8) should be supported. Did you install the SCIAMACHY codadef? https://github.com/stcorp/codadef-envisat-sciamachy/releases/tag/ENVISAT_SCIAMACHY-20180102

thank you !!!!
At 2024-10-22 04:13:36, "Sander Niemeijer" @.***> wrote:
This product (L1 V8) should be supported. Did you install the SCIAMACHY codadef? https://github.com/stcorp/codadef-envisat-sciamachy/releases/tag/ENVISAT_SCIAMACHY-20180102
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Can't migrate data from Fedora 3.7.1 to Fedora 5.1.0

As stated in the README, the tool should allow a data migration from a Fedora 3 to a Fedora 5 repository. However, I can't get this to work and am less and less sure about which CLIs are even appropriate for populating an F5 repository - or if this functionality is even still supported.
I have a 3.7.1. Fedora repo and wanted to test a migration of some data from it to a Fedora 5.1.0 repo (which is up and running). I tried both input variants, i.e. pointing directly to the fedora3 objectStore/datastreamStore or using exported FOXML files (testing with both archive and migration context). However, as far as I can see, the migration tool only ever exports data into a specified directory (--target-dir), in the OCFL format (which, if I understand correctly, is only relevant for Fedora 6?). In the command line options, there is never any specification of a target repository into into which to populate the migrating data. The config file conf/fedora3.xml seems to have some relevant options for this (e.g. fedora4Url), but editing it doesn't change the outcome.
I'm a little bit lost as to how to proceed. Do I just need to move the resulting output to an appropriate place in the Fedora 5 home? Or have I missed some other option/config somewhere? Apologies if this not really appropriate for an issue (as I might just do/understand something wrong here).

I did some more testing and managed to get it to work with a Fedora 6 build and I assume the process is very similar for a Fedora 5 repo. Thus, not a bug per se, just maybe a lack of documentation (or understanding on my side).
For posterity, if anyone else stumbles on this: I set up a new Fedora 6 repo from scratch, with the folders created by the migration tool already in place in $FEDORA_HOME/data (plus, of course, the environment variable properly set before setting up the repo) and the ocfl folder renamed to ocfl-root.


[v2.10] Add support for Docker 27.3.0 and 27.3.1

Add support for docker v27.3.0 & v27.3.1.
https://docs.docker.com/engine/release-notes/27/#273

Tested Docker v27.3.0 and v27.3.1 install script on rancher v2.10-head.
Docker install script worked correctly and cluster provisions successfully on following OSes.

Ubuntu 22.04 & 24.04
RHEL, Rocky and OL (9.4 and 8.10)


posh-git prompt with detached head adds to $global:error.Count

I notice that $global:error.Count constantly increases when just pressing the return key in a git versioned directory with detached head:
 ☠ Pfeiffer.Stefan@NB24  ~\…\…\…\oh-my-posh   (46908d8...) ●  $global:error.Count
53
 ☠ Pfeiffer.Stefan@NB24  ~\…\…\…\oh-my-posh   (46908d8...) ●  $global:error.Count
55
 ☠ Pfeiffer.Stefan@NB24  ~\…\…\…\oh-my-posh   (46908d8...) ●  $global:error.Count
57
 ☠ Pfeiffer.Stefan@NB24  ~\…\…\…\oh-my-posh   (46908d8...) ● 

This triggers an perpetual display of the FailedCommand-Character (skull in my case). I could not reproduce that in other git versioned directories, so i assume it has to do with the detached head. Not sure if that is an posh-git-issue...

I like the skull. I really do.  But it's a posh-git error.
git : fatal: no tag exactly matches '1aeab566491847616c8318584fc4ee5713ed0800'
At C:\Users\Jan\Documents\WindowsPowerShell\Modules\posh-git\GitUtils.ps1:57 char:39
+ ...            default { git describe --tags --exact-match HEAD 2>$null }
+                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (fatal: no tag e...c4ee5713ed0800':String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

This means we either create an issue over there (or a PR with a fix :-))

Thanks for analyzing that. My skills are too limited to submit a PR. Even submitting a proper issue is hard, i do not know to even get the error message you quoted on the screen.

You can get the errors thrown in PowerShell by looking at the $error object. It's what I use to determine whether or not the last command failed ($lastexitcode is unreliable). I'm looking for a way to adjust those git commands in a way where they no longer throw an error but rather the commit hash. But that might break other stuff, so I have to dig a bit deeper 😎

I looked at the code at bit more and I can't seem to find a solution for this. It will iterate over a few options and return the first one that does not return NULL. The problem is that the first one git symbolic-ref HEAD 2>$null returns NULL due to being detached. It will then do a describe to see if we checked out a tag and not find one (3 options are available) and add that error to $error. This is what we are seeing.

I fixed it and created a PR over at posh-git.
If you want to fix it locally, check the changes in that PR ;-)

Thanks for not only fixing bugs in other projects but also educating me about Powershell along the way. :+1: I think the issue can be closed over here?

I'd leave it open for people to find in case they notice the same issue. It won't be resolved until the PR is accepted at posh-git, which will not be anytime soon looking at their response times 😎.
And you are welcome!

PR closed at posh-git.


Possible to put a CLEAR button on the popup window?

Love the popup window! VERY helpful when you're getting a lot of audible ACT calls at once.
Just wanted to ask whether it was possible to have a CLEAR button on the popup window also.

Added in version 1.2


[master] avoid crowded more writable for auto grow

What problem are we solving?
https://github.com/seaweedfs/seaweedfs/issues/6121

unexpected behavior crowded more writable
How are we solving the problem?
removed auto grow in this case added logging of deletion from crowded
How is the PR tested?
Checks

[ ] I have added unit tests if possible.
[ ] I will add related wiki document changes and link to this PR after merging.

"unexpected behavior crowded more writable" I do not understand this sentence without going through the issue. Could you please explain this better?

"unexpected behavior crowded more writable" I do not understand this sentence without going through the issue. Could you please explain this better?

the crowded map in some cases did not allocate volume id, which led to the fact that the number of volumes in the map grew infinitely until the restart of the master and led to an incorrect calculation of the difference between vratibles and led to an writable growth of volumes.
I'm still not sure that the problem has been solved, since it was not reproduced on the dev cluster. Today I'll do a PR and turn the growth logic back on and roll it out to production.

"unexpected behavior crowded more writable" I do not understand this sentence without going through the issue. Could you please explain this better?

https://github.com/seaweedfs/seaweedfs/pull/6267


Routers load twice when management port is different from server port

Describe the bug
Routers load twice when management port is different from server port
Sample
https://github.com/kdlan/spring-cloud-gateway-test
Start this demo, it will print logs as follow
2020-09-04 11:56:25.727  INFO 98826 --- [           main] com.example.demo.DemoApplication         : No active profile set, falling back to default profiles: default
2020-09-04 11:56:26.371  INFO 98826 --- [           main] o.s.cloud.context.scope.GenericScope     : BeanFactory id=fa863064-1a99-3431-89bb-859627dc9c36
2020-09-04 11:56:26.959 DEBUG 98826 --- [           main] o.s.c.gateway.config.GatewayProperties   : Routes supplied from Gateway Properties: [RouteDefinition{id='default', predicates=[PredicateDefinition{name='Host', args={_genkey_0=**}}], filters=[FilterDefinition{name='PreserveHostHeader', args={}}], uri=http://<IP_ADDRESS>:8081/, order=0, metadata={}}]
2020-09-04 11:56:27.250  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [After]
2020-09-04 11:56:27.250  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [Before]
2020-09-04 11:56:27.250  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [Between]
2020-09-04 11:56:27.250  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [Cookie]
2020-09-04 11:56:27.250  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [Header]
2020-09-04 11:56:27.250  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [Host]
2020-09-04 11:56:27.250  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [Method]
2020-09-04 11:56:27.250  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [Path]
2020-09-04 11:56:27.250  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [Query]
2020-09-04 11:56:27.250  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [ReadBodyPredicateFactory]
2020-09-04 11:56:27.251  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [RemoteAddr]
2020-09-04 11:56:27.251  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [Weight]
2020-09-04 11:56:27.251  INFO 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : Loaded RoutePredicateFactory [CloudFoundryRouteService]
2020-09-04 11:56:27.644  INFO 98826 --- [           main] o.s.b.web.embedded.netty.NettyWebServer  : Netty started on port(s): 8080
2020-09-04 11:56:27.726  INFO 98826 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 16 endpoint(s) beneath base path '/actuator'
2020-09-04 11:56:27.773  INFO 98826 --- [           main] o.s.b.web.embedded.netty.NettyWebServer  : Netty started on port(s): 18091
2020-09-04 11:56:27.791 DEBUG 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : RouteDefinition default applying {_genkey_0=**} to Host
2020-09-04 11:56:27.811 DEBUG 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : RouteDefinition default applying filter {} to PreserveHostHeader
2020-09-04 11:56:27.813 DEBUG 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : RouteDefinition matched: default
2020-09-04 11:56:27.826 DEBUG 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : RouteDefinition default applying {_genkey_0=**} to Host
2020-09-04 11:56:27.827 DEBUG 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : RouteDefinition default applying filter {} to PreserveHostHeader
2020-09-04 11:56:27.827 DEBUG 98826 --- [           main] o.s.c.g.r.RouteDefinitionRouteLocator    : RouteDefinition matched: default
2020-09-04 11:56:27.830  INFO 98826 --- [           main] com.example.demo.DemoApplication         : Started DemoApplication in 2.928 seconds (JVM running for 3.44)

The PreserveHostHeader filter has been load twice. Change management port to server port, the log only print once
This seems with different port, the ApplicationContext published 2 ContextRefreshedEvent, that makes RouteRefreshListener reset twice

I wonder if this is similar to #477 but for the FilteringWebHandler rather than the handler mapping.

It's actually RouteRefreshListener


Importing seals.testing.envs errors when mujoco_py isn't installed

This makes imitation testing break on a pip install -e .[dev,test] install (not on our CircleCI instance, which comes with MuJoCo).
This isn't a high-priority thing for me, but just wanted to document this problem having run into it.
During handling of the above exception, another exception occurred:
tests/test_envs.py:5: in <module>
    from seals.testing import envs as seals_test
env/lib/python3.7/site-packages/seals/testing/envs.py:21: in <module>
    from gym.envs.mujoco import mujoco_env
env/lib/python3.7/site-packages/gym/envs/mujoco/__init__.py:1: in <module>
    from gym.envs.mujoco.mujoco_env import MujocoEnv
env/lib/python3.7/site-packages/gym/envs/mujoco/mujoco_env.py:14: in <module>
    raise error.DependencyNotInstalled("{}. (HINT: you need to install mujoco_py, and also perform the setup instructions here: https://github.com/openai/mujoco-py/.)".format(e))
E   gym.error.DependencyNotInstalled: No module named 'mujoco_py'. (HINT: you need to install mujoco_py, and also perform the setup instructions here: https://github.com/openai/mujoco-py/.)

+1, this also makes it annoying to run the imitation tests, since IIRC mujoco_py cannot coexist with dm_control (they both require different versions of MuJoCo).

+1, this also makes it annoying to run the imitation tests, since IIRC mujoco_py cannot coexist with dm_control (they both require different versions of MuJoCo).

I did this in the py3.6 branch a while back, but never PR'd due to weird CI errors: https://github.com/HumanCompatibleAI/seals/commit/5169358c71ee63010a0864ffbca8a89bacced6b7

Submitted a PR for this issue #49.


Piping & HT discovery

Figure out what needs to be done to split piping & ht app in two. Consult with Atle for details

Piping workspace (with pipetest as main object)
HT workspace (with heat tracing cable as main object)

https://miro.com/app/board/uXjVMZPHKgo=/
The decision is to split the existing JCA Piping and Heat trace into two separate application. We will need to include Atle in refinement.

Discovery
When the time is right - come up with a high-level estimate (days) - add it to Estimates on the Issue in the Project.

Can't do anymore before i get SQL-view

Meeting with 07.06 with Atle, Magnus and Are.
Key highlights:

Data coming from MIPS to JC wil come through Pcs for OGP (and other projects). This is a new column that has been added to pcs this week, and is planned to soon be available in FAM
Split Piptest and HT so that we avoid duplicates, due to many to many relationship between PT and HT. This will result in two views.
Agree that I will look more into this, and will revert back with questions and follow up

Replaced by

equinor/lighthouse#303
equinor/lighthouse#312


⚠ PrivateHD has degraded performance

In edf0774, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 3504 ms

Resolved: PrivateHD performance has improved in 07286de.


Fix personal blocklist filtering issue

fix case where brandsRefinements is undefined (amazon.fr problem)
fix personal blocklist toggle issue where brands that should be shown are hidden

@chris-mosley i think that i've found the bug that was causing problems when the personal blocklist was enabled! this pr should fix the issue (tested on chrome and firefox), but if you're still seeing the problem please let me know. i've also addressed the following bug that seemed to frequently occur on amazon.fr:


Allow to pass ReplyTo Topic

I think If someone wants to use nats authentication with request reply the reply topic needs to configureable.
@mtmk would it be possible to check the change / suggest a different implementation.
Thanks in advance

looks reasonable to me but could you explain the use case a little? is this to do with permissions on the server? I might be missing something.

NewInbox() generates a completely random Inbox for every request-reply
It has the format:
{InboxPrefix}.{Random ID for this Client}.{Random ID for this Request}

So every time Request or RequestMany is called, it generates a new ID.  That way the response will only go to the requester.
To tighten the permissions on inboxes, so that other clients can't see each other's inboxes, use a unique permission-constrained Inbox Prefix.

That is the Request subject.
For the requesting side:
A connection making a Request to those subjects can already do that.  Then the response will come on the replyTo subject, which will be dynamically generated based off the InboxPrefix
For the serving side
Consider using NATS.Client.Services for serving these endpoints

I will close this PR with the inbox prefix user can configure authentication.
Only limitation is that this has to be shared across connection.


How to test relations between tags

I was trying to test that every input tag has its correspondent label tag. How can I do this in a DOM-less environment?

My initial thought would be we could make such an assertion after the component has rendered using a componentDidMount callback. This is the approach I took for implementing logging of DOM element references.


Fix search filters appearing in the dropdown

📝 Description
When filter.items is empty for some filters like 'Node' as maybe all vms are stopped, the filters appears in the dropdown.
🎥 Demo
Before

After

@upalatucci Hi Ugo :)
Quick question, by the after screenshot it also seems there's no ip address but it still shows in the dropdown, why are we still showing the IP address option?
I also thought in general we don't make option disappear but we disable it, is that possible to disable instead of removing?

hei @avivtur here in the dropdown we should have only searchable filters. We added recently IP Address so that the user can type the IP and search vms by subnetwork and singular ips. Node is a filter that should be in the 'Filters' section and not in the dropdown


Yosys assertion when converting SyncFIFO

SyncFIFO cant be used with recent yosys anymore.
Probably related to https://github.com/YosysHQ/yosys/commit/c7076495f197732725456992c9a02aed9966139a ?
repro:
from nmigen import *
from nmigen.back import verilog
from nmigen.lib.fifo import SyncFIFO
verilog.convert(SyncFIFO(width=8, depth=8))

results in:
nmigen._toolchain.yosys.YosysError: ERROR: Assert `!port.transparent' failed in kernel/mem.cc:293.

Please report this against Yosys,

from the yosys issue:

By the way, there is no such thing as a "transparent" asynchronous read port, and it never behaved differently from a plain one. It just so happens that a check function meant to trigger on invalid memory configs was added, and caught this.

It seems like we should reflect this in the nMigen Memory / FIFO?

Fixed on the yosys side, sorry for the mess (this issue will only affect yosys master compiled within the last 9 days). $memrd cells without a clock are now once again accepted regardless of the (effectively meaningless) value of the TRANSPARENT parameter. $memrd_v2 will follow more strict rules when it lands, but then it's very likely to have per-port-pair transparency masks instead.

We should also set TRANSPARENT to whatever Yosys expects for such ports. That code was written a very long time ago and IIRC it predates any documentation on $memrd cells, which I wrote using the code as reference. So it's not unexpected that the nMigen side of this is kinda wrong.

Verilog frontend uses 0, hence my expectation in the check.  However, I don't see a point of changing this — I explicitely don't want to break compatibility with old RTLIL inputs and $memrd should now be accepted according to the old rules.  And when we migrate to $memrd_v2 for the the new features, we'll get to deal with transparency masks instead.

Alright.

closing this as it is fixed upstream :)


How can I make a model with input size 640x384 from 640x640, the original Yolov7 training?

Environment (Hardware)

Hardware: Device, CPU, GPU, etc.
Software: OS, Compiler, etc.
(Please include version information)
GPU : Cuda 11
OS : Windows 11

Project Name
pj_tensorrt_det_yolov7
Issue Details
I have a question about your model...
After training yolov7 with default input size 640x640, how can I change the input size from 640x640 to 640x384?
Is there your owned way to do this?
Thanks ~
How to Reproduce
Steps to reproduce the behavior. Please include your cmake command.
Error Log
error log

Additional Information
Add any other context about the problem here.

I just downloaded and used the models here. https://github.com/PINTO0309/PINTO_model_zoo/tree/main/307_YOLOv7

Hello, IWATAKE
Thank you for your reply.
It is very helpful for your code and work to me.
Really appreciate your work.
NTS
2022년 10월 30일 (일) 오후 12:48, iwatake @.***>님이 작성:

I just downloaded and used the models here.
https://github.com/PINTO0309/PINTO_model_zoo/tree/main/307_YOLOv7
—
Reply to this email directly, view it on GitHub
https://github.com/iwatake2222/play_with_tensorrt/issues/31#issuecomment-1296092006,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A34QQUE2RWQVIDQIKXAB753WFXVZ5ANCNFSM6AAAAAARSAHTLA
.
You are receiving this because you authored the thread.Message ID:
@.***>


simplify maccs

I simplified the MACCS code by putting everything in one file, instead of spreading some of the logic to the main file. couldn't really tell what was going on without a lot of effort so now I think this is clearer of the logic involved. and now we are just storing the bit instead of storing the number of matches and then comparing at end. just think it's clearer of what each entry is now. 😄

Codecov Report

Merging #46 (e2f34a8) into main (2be850a) will increase coverage by 0.00%.
The diff coverage is 90.00%.

@@           Coverage Diff           @@
##             main      #46   +/-   ##
=======================================
  Coverage   99.51%   99.52%
=======================================
  Files          10       10
  Lines         208      210    +2
=======================================
+ Hits          207      209    +2
  Misses          1        1

Impacted Files
Coverage Δ

src/MolecularGraphKernels.jl
66.66% <50.00%> (-16.67%)
:arrow_down:

src/maccs.jl
100.00% <100.00%> (ø)

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