Feature request: smarter primitive for container_types

I've been noticing that grad() can be quite memory intensive, due to the tape.
As a workaround, I've been making some of my subroutines @primitive, and assigning their derivatives thru defgrad. This way, the gradient for the subroutine gets computed "off" the tape.
However, there is a problem if the primitive subroutine takes a container argument, e.g. if I call subroutine(a_dict), where subroutine is primitive and a_dict is a dict containing Node entries. Then not isinstance(a_dict, Node),  and so subroutine acts as if it is not primitive at all: it will not call self.gradmaker(), and continue to pass Node objects into self.fun(), thus continuing to add to the tape.
My solution is to convert a_dict into a DictNode, so that subroutine truly acts as a primitive. More specifically:
make_dict = primitive(lambda keys, *vals: dict(zip(keys, vals)))
make_dict.gradmaker = lambda argnum, ans, args, kwargs: lambda g: g[args[0][argnum-1]]

a_dict = make_dict(a_dict.keys(), *a_dict.values())
ret = subroutine(a_dict)

Then a_dict is a DictNode and none of its entries are Node, so subroutine(a_dict) won't add its internal computations to the tape. (Note make_dict doesn't work if a_dict recursively contains more dicts).
It would be nice if primitive.__call__() did this automatically (i.e., not just check if the arguments are Node, but if they are container types with Node inside). Then, primitives with container_type arguments would be really primitive.

Hmm, I just realized I could make my primitive subroutine have signature
@primitive
def subroutine(keys, *vals):
    a_dict = dict(zip(keys, vals))
    ...

instead of
@primitive
def subroutine(a_dict):
    ...

which would also solve this issue.
It might still be neat to have primitive work with container_type arguments but maybe it would be too much work/code bloat. I'll leave it to you to decide whether to close this issue.

I agree with your diagnosis: in general, there are cases where we'd need to recursively descend into data structures to look for any nodes in them. I've run into some corner cases along these lines, especially when making tuples of nodes and when defining my own primitives; to ensure that they get wrapped into a TupleNode, I call make_tuple, which I put in autograd.util. I think your make_dict is similar, and we should probably add that to autograd.util too. (We've also seen similar nested data structure challenges come up when primitive arguments are bundled into kwargs in such a way that autograd doesn't unbox nodes before passing them to the wrapped function, like with some of the scipy wrappers.)
However, recursively descending into data structures would make the boxing/unboxing logic a lot more complicated (not just the implementation but even the decision of what cases to handle) and also slower for the common case. As long as these issues remain rare corner cases, requiring the power users to call make_tuple or make_dict seems pretty reasonable, at least until we find a better solution.
Dougal's been cleaning up the core logic a bit in a branch. It may be the changes that he's made will help this container type logic. For the time being, I'm going to add make_dict to autograd.util and close this issue.

For posterity, this commit is where we added make_tuple.

On second thought, I'm not going to add make_dict yet; let's see how the new core logic might treat things differently.

Sounds reasonable -- doing all the extra checking could certainly slow down a lot of common cases. I think requiring power users to call make_tuple or make_dict to move computations off the tape is pretty reasonable.
Maybe this functionality for moving certain computations off the tape, could become an official part of the API/documentation/functionality, with some unit tests? In practice it can be hard to tell whether a computation is happening on or off the tape, so my worry is that future changes to autograd may affect the code behavior in a way that is hard to diagnose.
Anyways, thanks for the response, I was worried my initial rambling post would be impossible to understand :)

We read you loud and clear; we've just gotten busy with thesis defenses and job hunts.
I think "moving computations off the tape" means defining your own primitives and, in so doing, being able to discard some values that aren't needed on the reverse pass. Defining your own primitives is in the documentation (to the extent that anything here is documented), but there are some more things we could write down and some API adjustments we could make. In particular, sometimes your primitive does need to cache some results for the reverse pass gradfun to use, and the API should support that. I hacked something like that into the API as primitive_with_aux and used it for a project where I wrote some primitives and gradients in cython, but that implementation isn't a good one because it breaks higher-order differentiation. Now that we understand this issue better we're hoping that an updated core design will handle these cases.


add 219-colorization

This notebook demostrates colorization with OpenVINO. We use the colorizatioin siggraph from Open Model Zoo. Given a black and white image, the colorization model can turn it into a plausible color version of the image.

@adrianboguszewski please help run the workflow again, thanks.

This PR is a duplication of #525


[0.1] Hotfix -  Customer purchase history

Fixed #712
Add active pagination state to purchase order and users table
Maintain active tab state when page reloaded

Hi, @Aslam97 thanks for this.
I've taken a look and the issue that you face on #712 is still happening for me when using this branch.
It was fine once I closed the error, but on first load of "Purchase History" it would happen.

Hi, @Aslam97 thanks for this.
I've taken a look and the issue that you face on #712 is still happening for me when using this branch.
It was fine once I closed the error, but on first load of "Purchase History" it would happen.

Strange, it worked for me straight away 🤔


Use a standard license which GitHub can read

Hi there!
Thank-you for the amazing plugin!
You already have a LICENSE file here:
https://github.com/jpcima/spectacle/blob/master/LICENSE
However because it is not a standard template, GitHub cannot display the license. It also requires all users to read the LICENSE end-to-end to understand what type of license it is.
Would you be able to use a standard template to make it easier to understand and search for?
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository
Thanks!

Hello, the file changed according to template, does it look correct now?

Yes it works! Now when you view the file GitHub shows enriched information:
https://github.com/jpcima/spectacle/blob/master/LICENSE
This also means the license is available via Search and API:
https://api.github.com/repos/jpcima/spectacle
Thank-you for the quick turnaround!


modules/mono/mono_gd/gd_mono_utils.cpp:371 - System.ArgumentException: Illegal characters in path.

I am having precisely this issue, which the original person has closed since they cannot replicate it.
I am receiving the same errors as described in the console every time Godot is opened.
https://github.com/godotengine/godot/issues/39432

Duplicate of #39432. (Please be more patient when requesting issues to be reopened.)

Apologies, and thanks.


Cannot read property 'removeEventListener' of undefined when using resize in nuxt and navigating away

Version
<EMAIL_ADDRESS><EMAIL_ADDRESS>OS
Windows 10, Chrome 90.0.4430.212
Reproduction Link
I am experiencing this error in development, and it also affects the live demo at https://vue-final-modal.org/examples/liveDemo
Steps to reproduce

Make sure resize is true
Open & close modal
Open console
Navigate to another page using the links in the sidebar
You see this error

I think this has something to do with how Nuxt page navigations work, perhaps the modal element no longer exists after navigation? Strangely this only happens when resize is true.
What is Expected?
There are no errors.
What is actually happening?
You see an error (above)

Also, thank you so much for this component. It is very useful for my website.

Hi @jeffalo,
Thank you for reporting this issue. I will fix it in the next few days.

Fixed and Released in<EMAIL_ADDRESS>

Thank you so much. That was very fast!!


Extend latitude/longitude to have (locale?) bounding areas

Hi, the built in latitude/longitude generators are an amazing idea but they're not too useful for me right now as they spill out worldwide.
Two ways I'd like to see this extended (I'm happy to have a go at writing the code if you can indicate if this is preferred + if so, which way):

Allow latitude() and longitude() to have a min and a max fed into it,
Allow each locale to define bounding areas these functions should use.  Most countries don't fit into a nice square, so this is obviously more complicated to implement (array of points to bound within?)

Ah, I've just noticed that a few of the locales do have latitude() and longitude() defined.  I'll submit a PR for my locale (en_AU) but it's going to be a little janky due to (2), so feedback still appreciated.

Latitude and longitude should not be extended, see #387


Tags support

This is a key notion of article management.

[x] displaying
[x] filtering

[x] from filters menu
[x] from article listing

[ ] article modification

[x] for a single article
[ ] in bulk

[ ] global label management

[ ] creation
[ ] modification
[ ] deletion
[ ] merge

also, create tags is missing (or I do not find it) :P

That's right, I have added it in the list.


Exception caught by gesture

The following assertion was thrown while handling a gesture:
type 'int' is not a subtype of type 'String' of 'other'

ListTile(
 title: Text(S.of(context).share, textAlign: TextAlign.center),
 onTap: () {
   Navigator.of(context).pop();
   final RenderBox box = context.findRenderObject();
   Share.share(product.name,
       sharePositionOrigin:
       box.localToGlobal(Offset.zero) &
       box.size);
 }
);

Hi @bhallaramdhatarwal
can you please provide your flutter run --verbose?
Also, to better address the issue, would be helpful
if you could post a self contained app code to reproduce it.
I tried to run your code

this way
import 'package:flutter/material.dart';
import 'package:share/share.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: MyHome(),
    );
  }
}

class MyHome extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return ListView(
      children: <Widget>[
        Card(
          child: ListTile(
              title: Text('name', textAlign: TextAlign.center),
              onTap: () {
                Navigator.pop(context);
                final RenderBox box = context.findRenderObject();
                Share.share('name',
                    sharePositionOrigin:
                    box.localToGlobal(Offset.zero) &
                    box.size);
              }
          ),
        ),
      ],
    );
  }
}

But I don't know what are yours product.name and S.of(context).share
Is problem there?
Thank you

@VladyslavBondarenko
product.name just a string type parameter, and S.of(context).share is just local string values is share nothing else

@bhallaramdhatarwal
Can you modify my code sample in such way to reproduce the exception?
Thank you

@VladyslavBondarenko No, not really but I solve using same code and clean flutter and clean system cache
Thank you


Fix new clippy warnings coming up in CI

thanks for taking care of new linter errors from the latest rust release.


Explicit Logic - Communication-item API Doc Updates

User Story - Business Need
User Story(ies)
As a business line
I want my recipient to expressly opt in to receive my notifications
So that I'm only notifying those who ask to be notified
As a VA Notify engineer/QA
I want to understand the capabilities and limitations of the API
So that I can manage communication items via the API
Additional Info and Resources

https://github.com/department-of-veterans-affairs/notification-api/tree/master/documents/openapi
Related tickets: #1253, #1252, #1227

[ ] Talk to QA when picking up ticket, they may collaborate on this work with you to create a standard example

Engineering Checklist
Required

[ ] Update existing communication-item GET {{notification-api-url}}/communication-item

[ ] Must include new optional, boolean field "default_send_indicator"
[ ] Should include all response options, 201, 400, 401, 403, 404, 500 with example values for each

[ ] Add new communication-item routes with applicable assets for each

[ ] Read - GET {{notification-api-url}}/communication-item by id
[ ] Update - PATCH {{notification-api-url}}/communication-item/{{communication-item-id}}
[ ] Create - POST {{notification-api-url}}/communication-item
[ ] Delete - DEL {{notification-api-url}}/communication-item/{{communication-item-id}}

Acceptance Criteria
Required
API Documentation
Within the documentation I can understand how to:

Create a new communication item
Update an existing communication item
Delete an existing communication item
Read a list of existing communication items
Read a single existing communication item

Per endpoint:

Any applicable parameters are documented
Request body examples are present
Required fields are indicated
Response codes are documented for 201, 400, 401, 403, 404, 500 with example values for each

Endpoint AC details are below for reference
Create a new communication-item
POST {{notification-api-url}}/communication-item
"id" is an auto-generated UUID when the object is inserted into the DB
payload:
"name": string, required, minLen 1, not nullable, cannot be a duplicate
"va_profile_item_id": integer, required, min 1, not nullable, cannot be a duplicate
"default_send_indicator": bool, default value true, not nullable, optional
201 response is the object, with all 4 properties visible
{
"id": "df6457be-97c4-4ce3-9413-ebcb68a2dc56",
"name": "Board of Veterans' Appeals hearing reminder",
"va_profile_item_id": 1
"default_send_indicator": true
}
Swagger contains 201, 400, 401, 403, 404, 500 responses
Update an existing communication-item by ID
POST {{notification-api-url}}/communication-item/{{communication-item-id}}
properties that can be updated:
"name": string, minLength 1, not nullable, cannot be a duplicate
"va_profile_item_id": integer, min 1, not nullable, cannot be a duplicate
"default_send_indicator": bool, not nullable
200 response is either in the form of nested data object or just the updated object, with all 4 fields visible (see Create response)
Swagger contains 200, 400, 401, 403, 404, 500 responses
Read ALL communication-item
GET {{notification-api-url}}/communication-item/
200 response is nested list with top-level property "data" as a list
each object in the 200 response has all four properties (see Create response)
Swagger contains 200, 401. 403, 404, 500 (see GET /service/{service_id}/api-keys for examples)
Read BY ID communication-item
GET {{notification-api-url}}/communication-item/{{communication-item-id}}
200 response is the object containing all four properties (see Create response)
Swagger contains 200, 401. 403, 404, 500 (see GET /service/{service_id}/api-keys/{{api_key_id}} for examples)
Delete BY ID communication-item
DEL {{notification-api-url}}/communication-item/{{communication-item-id}}
object is removed from DB
202 response is an OK
Swagger contains 202, 401. 403, 404, 500 response (see POST /service/{service_id}/api-keys/{{api_key_id}} for examples)
GET ALL and GET by ID no longer return this object
QA Considerations
For QA to populate. Leave blank if QA is not applicable on this ticket.
Potential Dependencies
Leave blank if n/a
This may be handled before the endpoints and postman are created/fully functional
Out of Scope
Leave blank if n/a

Hey team! Please add your planning poker estimate with Zenhub @EvanParish @jakehova @justaskdavidb2 @k-macmillan @kalbfled @ldraney

Useful:
https://editor-next.swagger.io/
https://spec.openapis.org/oas/latest.html

Merged to master, reviewed document in SwaggerEditor and it looks as expected. Closing ticket.


More user and contact data?

Hey thanks for creating the repo!
I have been through the API and am not sure if I can accomplish a couple things with the limited api.  Wondering if you have any thoughts on what is possible @phmiller
Is it possible to get an availability status for each of the agents?  Currently neither listUsers, nor describeUser appears to have any of that data, and the Metric Data only appears to have aggregate data?  I'd like to host a dashboard with the current status of each of my agents, kind of thought this would be easy with the api?
Second was getting more data about the contact.  I am recording calls, but need an api to know what the URL of the recording is for a given contact.  Have you seen that data flowing around anywhere in the api?
Thanks again for your time!

Thanks @anthonywebb. The API was pretty limited when I first published this. Since then I've moved on to other systems, so I have not been keeping up. So, unfortunately, I can't be of too much help here.


Refactor e2e nodepool tests

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/retest-required

/check-required-labels

/retest-required

/area hypershift-operator

/approve

/retest-required


Which files need to be hosted?

Hi @SchwarzwaldFalke ,
We are cdnjs team, we want to host your project on cdnjs.
But I'm not sure which files in this repo need to be added, could you please help up find out the main files?
Thank you.
https://github.com/cdnjs/cdnjs/issues/8042

I think that I can answer as I'm the author of the cdnjs hosting request :)
Only two files are needed:

/src/css/ngGallery.css
/src/js/ngGallery.js


Updated README.md to improve clarity

Updated wording on throughout document to improve readability.
Made some formatting and changed wording to improve consistency

Thank you!


Not working)

I got one ID through chrome, another one through Tor. Opera without VPN gave a third identifier, Mozilla also showed another. This nonsense does not work and also does not run on NodeJs))

Opera vpn and no vpn different IDs

I got one ID through chrome, another one through Tor. Opera without VPN gave a third identifier, Mozilla also showed another. This nonsense does not work and also does not run on NodeJs))

Fingerprinting is done exactly as expected, but not cross-browser.
Please read the docs!


Inconsistant InfluxDB data types.

In an ongoing effort to clean up all the bugs with the influxDB history component we still have some outstanding bugs that I would like to discus before writing up a solution.
Known Issues

Home Assistant does not have strict data types for each entity state and attribute. The state of a sensor can be string, int, float, or bool. This causes errors with InfluxDB because the first measurement sent determines the data type for each column from then on. So if the first one was an int, then every update after has to also be an int. If the next time it updates it's a string it will error causing nothing to go to influxDB.  This is what is happening at the moment for most updates causing very little to actually get to influxdb.

Home Assistant currently uses the unit_of_measurement attribute if it exists as the measurement name otherwise it uses the entity name as the measurement. This allows some common measurements like temperature to be grouped into the same series, but the majority of entities go to their own time series. This is only useful if you want to look at each individual entity. InfluxDB does not allow merging of different measurements. This should be done by putting them all  under the same measurement name but use tags to query the ones we want out.

Strings currently get sent to influxdb as field columns. Influxdb uses tags and fields. Tags are indexed and used for identifying metrics in a series. Fields are the actual metric data. While influxDB allows strings to be sent to fields it is not very common and has very little use since you can't query by field. If you could it would be super slow because it has no index.

Existing Attempts

#4632: This was a great first step to fixing so many entities going to their own unique series. This solves the 2nd known issue for the most part.

I would argue that this should not be an optional configuration.

#4642: This prevents any unsupported data type from going to influxDB and converts all numeric values to float.

This has greatly reduced the number of errors but it's still not perfect.

Proposed Solution

Prevent any string or boolean from being sent to a field column.

Only numeric values should be sent to a field column.

Update all measurements to be sent to 2 different series.

Series (Measurements)

gauges: This will only include numeric value changes to the state and attributes.
counters: This will happen for every change no matter what the data type. All tags will be the same but the only field will be a boolean or some other value to indicate a change occurred

This would line up influxDB in a similar way that the recorder component currently puts all states in a single table.

Impact On Existing Implementation

All existing measurements will be discontinued requiring any existing users to update their queries for the new layout.

This will likely not be a problem as it's so broken already that very few people likely use it.

For every update a maximum of two measurements will be sent to InfluxDB.

Influx allows multiple measurements per request so it will not increase the number of requests. It will only increase the payload size slightly.

I have opened this issue to get feedback and ideas from other people that are using the influxdb component before I code it and open a PR.

So is this what is causing my history timelines to be drawn with bad or no coloring and taking forever to load and causing database locked errors in my logs?

This is a metrics component. Not the recorder used to show the logbook and graphs.

Here is my proposed changes http://hastebin.com/ovonizujuq.diff
This adds two measurements hass.event and hass.state
hass.event
Every state change, homeassistant_start and homeassassitent_stop gets this.

Tags: domain, entity_id, event_type, and event_origin
Fields: count

hass.state
Only state changes that have a state or attribute that is numeric.

Tags: domain, entity_id
Fields: all states or attributes that are numeric

Can we also add the other attributes and states which are not numeric as tags ?

I thought about doing something like this but tags are used for the purpose of querying the metrics and are indexed.
Because we don't know which attribute values are informative data and which are state data it's hard to know what should be there and what shouldn't. Also if we put attributes in tags then every metric will have nulled tags and traditionally nulls in an indexed column can have a negative impact on performance.
Once thing I did think of doing was adding a 3rd measurement for the strings. But the usefulness of strings for metric data is limited and for the majority of uses will just be a lot of junk building up in their database.


feat(message-parser): Parser options

Proposed changes (including videos or screenshots)

Add some grammar rules activated by options, like colors and katex.

Issue(s)

Further comments

The tokens and tests seem OK... @ggazzo do you want to check also?

just wondering how much this changes adds terms of sizing and if brings any performance issue

just wondering how much this changes adds terms of sizing and if brings any performance issue

Before:
56K    packages/message-parser/dist/messageParser.production.js

After:
76K    packages/message-parser/dist/messageParser.production.js

@ggazzo and @tassoevan
I made a benchmark between this grammar and develop branch grammar.
The markdown file used has all type blocks/elements and more than 2k lines of markdown text.
Here it is the results:

Considering that includes more functionalities I think that it is expected an increase of Avg. Time to parse a file.


docs: fix broken links

Signed-off-by: Jintao Zhang<EMAIL_ADDRESS>
What type of PR is this?

/kind documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

/lgtm

/approved

/ok-to-test

/approve


Support the KHR_texture_transform GLTF extension

What problem does this solve or what need does it fill?
In Blender, the default way of making sure a texture tiles n times is to add a UV Map and a Mapping node, like this;

The above example tiles the texture exactly 5 times.
This transforms the UV. The Blender GLTF exporter supports this by writing it to the KHR_texture_transform extension. So, setting the nodes up as follows, we get a nicely tiled GLTF:

I have a simple greyboxing grid texture applied to a cube in this case. Viewing it through a GLTF viewer, I get this:

As you can see, the text in the grid is repeated 5 times per face. Opening this up in Bevy however... (ignore the poor lighting)

Oh no! Bevy does not support GLTF extensions yet, so it just stretches the texture instead of tiling it!
What solution would you like?
Ideally, Bevy should apply the transforms to the UV automatically when encountering this extension. As the Khronos group link specifies, most implementations ignore the rotation value, so I think it's fine if we do too. Most important are the offset for texture atlases and scale for tiling.
What alternative(s) have you considered?
Leave it to the user. https://github.com/bevyengine/bevy/pull/11138 allows us to read the extension manually, so a user could write a custom shader or a shader extension for this.
Additional context

Related issue: https://github.com/bevyengine/bevy/issues/399
Fixes: https://github.com/bevyengine/bevy/issues/6335
Implements a part of https://github.com/bevyengine/bevy/issues/5178 and https://github.com/bevyengine/bevy/issues/11350

I'd be ready to implement this myself if anyone gave me some pointers on how/where to change the UVs :)

It looks like the PR has been abandoned by the author: adopt it by forking the work and submitting a new PR, then ping the original reviewers for a re-review :)

@alice-i-cecile, alright, I'll try to get it done later, quick enough for 0.13 💪


Firmware update is temporarily unavailable

The problem
Can someone shed some light on why the firmware update utility was hidden? It happened in a direct commit rather than a PR, so there's no information explaining the change. Is that best practice?
Is this related to the voltage regulator failure in some way?
Context: I needed to upgrade the EZSP protocol version in order to use Zigbee2MQTT (which I think has a required minimum version of 13; the ZBT-1 I received was on 9). This required updating the device firmware. The only user-friendly and well-documented way to do that is the web firmware update tool. I had to edit the html in Chrome Inspect to essentially reverse that commit, and was able to update firmware that way and get z2m working. Not a great user experience.
Alternatively, I would suggest documenting detailed instructions on how to safely update the firmware with command line or other tools.
Link to the page
https://connectzbt1.home-assistant.io/firmware-update/

Bump to prevent closure of the Issue per the bot.

In case anyone else is having trouble with this, here's a small static site with the firmware management component: https://zbt1.notaphish.fyi/
I successfully used it to change a new ZBT-1 dongle to the Thread firmware.

The voltage regulator problem is indeed why the web flasher is currently disabled. We found that a few people broke their ZBT-1s after plugging them into a desktop computer to use the web flasher. It took some time to identify the root cause but for the time being the web flasher will remain disabled.
The good news is that we're going to be adding ZBT-1 firmware updates directly to Home Assistant Core, which will replace the web flasher entirely.
You can always update the firmware by using the flasher addon. Or directly use the universal-silabs-flasher tool that both of these wrap.

Worth noting that it is back up now, albeit with a confusing warning about how only ZBT-1 sticks made after Oct '24 are supported for flashing.
I'm just not sure why though, because I thought it was said that the newer 'Connect ZBT-1' branded products weren't supposed to have used any different modules to the older models that just had the 'SkyConnect' name on its own, Could Nabu Casa's HASS Devs elaborate by pushing an explanation/reason of why alongside that warning box?

Worth noting that it is back up now, albeit with a confusing warning about how only ZBT-1 sticks made after Oct '24 are supported for flashing.
Sorry to ping you @puddly but I'm just not really sure why this is the case though, because I thought it was said that the newer 'Connect ZBT-1' branded products weren't supposed to have used any different modules to the older models that just had the 'SkyConnect' name on its own, Could Nabu Casa's HASS Devs elaborate by pushing an explanation/reason of why alongside that warning box?

(not affiliated with Home Assistant or Nabu Casa, don't take this as official)
I believe this is covered in the blog post:

Though Home Assistant SkyConnect is identical to the ZBT-1 under the hood, it is not affected. The design is not what’s at fault, but instead, a defective voltage regulator that was used in this specific production run that is causing the issue.

https://www.home-assistant.io/blog/2024/10/02/connect-zbt1-issue-and-replacement/

Also, I think it's safe to close this issue now that the official docs have the updater available again! ❤


Check mark for secondary subtitles is too big on Safari

(How to get away with murder, S03E08)
It happens only on Safari. Can you check @WingCH ?
I made this issue in this repository because WingCH/NflxMultiSubs doesn't support issues.

This is fixed in v2.2.8. The Safari version is still on v2.2.6 it seems. @WingCH will have to update it.

I made this issue in this repository

That's fine 👍

i will update it tonight!

2.2.8 version has been release in mac app store, Thank you for your interest!
https://apps.apple.com/hk/app/nflxmultisubs/id1594059167?mt=12

👍


HARP-5631 Fixing missing tiles during tilting / rotating view

Signed-off-by: Jonathan Stichbury<EMAIL_ADDRESS>

@heremaps-bot retest this please


How to use AAD groups for AuthZ

What are the options to use AAD groups in OCP for authorization.
OCP  Syncing LDAP groups would need AD DS I assume. https://docs.openshift.com/container-platform/4.7/authentication/ldap-syncing.html
Any suggestion:

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

ID: b0bd7bfa-9c1c-c19c-0e80-fbcaf1fe048b
Version Independent ID: 129d0b46-35e3-6c01-7c33-9d9bf8ea7ca8
Content: Azure Red Hat OpenShift running OpenShift 4  - Configure Azure Active Directory authentication using the command line
Content Source: articles/openshift/configure-azure-ad-cli.md
Service: azure-redhat-openshift
GitHub Login: @sabbour
Microsoft Alias: asabbour

@TiloGit Thank you for your query . We will have this reviewed and update the thread.

any update?

see here as well: https://github.com/Azure/ARO-RP/issues/457 ;

@TiloGit Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused. I'd recommend posting your question in https://azure.microsoft.com/en-us/support/community/ since it's not directly related to the documentation. We'll follow up there. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Package does not play well with ccache and ninja

Here's the full error message
[2/58] cd /Users/yagiz/Developer/url-parser/benchmarks/competitors/servo-url &...parser/build/./cargo/build --profile=release -- -Cdefault-linker-libraries=yes
   Compiling tinyvec_macros v0.1.1
   Compiling libc v0.2.139
   Compiling percent-encoding v2.2.0
   Compiling unicode-bidi v0.3.10
   Compiling tinyvec v1.6.0
   Compiling form_urlencoded v1.1.0
error: linking with `/opt/homebrew/bin/ccache` failed: exit status: 1
  |
  = note: "/opt/homebrew/bin/ccache" "-arch" "arm64" "/var/folders/zh/k9s2ynfn5mzblpbzc2n76hmc0000gn/T/rustccSX7Y4/symbols.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.0.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.1.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.10.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.11.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.12.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.13.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.14.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.15.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.2.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.3.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.4.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.5.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.6.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.7.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.8.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.build_script_build.a1a91adf-cgu.9.rcgu.o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3.2t7ubitt1g6czhst.rcgu.o" "-L" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/deps" "-L" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libstd-f6811f31090e0239.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libpanic_unwind-585aa2ea4819ce90.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libobject-1b4ea1dc4a3823f8.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libmemchr-f653b27121920f5c.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libaddr2line-ef1f6d7964edf865.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libgimli-8d0a95997d48da47.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/librustc_demangle-68d9470ea5ba2fa3.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libstd_detect-d4ed7f63db7e9953.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libhashbrown-d2ad324cf0492211.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libminiz_oxide-a00c8eba7ff52d83.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libadler-92e25d254b309fb5.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/librustc_std_workspace_alloc-9cf27ed549592a86.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libunwind-ebee0ebd9a510319.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libcfg_if-718033b8fe200c22.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/liblibc-5ec3532fb120beec.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/liballoc-80ef5ce8d4cd7e19.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/librustc_std_workspace_core-b5600cb14c277fae.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libcore-760870d297bc6b81.rlib" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib/libcompiler_builtins-931e7dc6a4f959e6.rlib" "-lSystem" "-lresolv" "-lc" "-lm" "-liconv" "-L" "/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/aarch64-apple-darwin/lib" "-o" "/Users/yagiz/Developer/url-parser/build/./cargo/build/release/build/libc-1c6f01aa30c937e3/build_script_build-1c6f01aa30c937e3" "-Wl,-dead_strip" "-nodefaultlibs"
  = note: ccache: invalid option -- a

error: could not compile `libc` due to previous error
warning: build failed, waiting for other jobs to finish...
[43/58] Generating ada.cpp, ada.h, demo.cpp, README.md
SCRIPTPATH=/Users/yagiz/Developer/url-parser/singleheader PROJECTPATH=/Users/yagiz/Developer/url-parser
We are about to amalgamate all ada files into one source file.
See https://www.sqlite.org/amalgamation.html and https://en.wikipedia.org/wiki/Single_Compilation_Unit for rationale.
timestamp is 2023-03-03 16:09:51 -0500
Creating /Users/yagiz/Developer/url-parser/build/singleheader/ada.h

Creating /Users/yagiz/Developer/url-parser/build/singleheader/ada.cpp
Done with all files generation.
Files have been written to directory: /Users/yagiz/Developer/url-parser/build/singleheader/
Done with all files generation.
[44/58] Linking CXX executable tools/adaparse
FAILED: benchmarks/CMakeFiles/_cargo-build_servo-url /Users/yagiz/Developer/url-parser/build/benchmarks/CMakeFiles/_cargo-build_servo-url
cd /Users/yagiz/Developer/url-parser/benchmarks/competitors/servo-url && /opt/homebrew/Cellar/cmake/3.25.2/bin/cmake -E env CARGO_TARGET_AARCH64_APPLE_DARWIN_LINKER=/opt/homebrew/bin/ccache CC_aarch64-apple-darwin=/opt/homebrew/bin/ccache CXX_aarch64-apple-darwin=/opt/homebrew/bin/ccache SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.1.sdk CORROSION_BUILD_DIR=/Users/yagiz/Developer/url-parser/build/benchmarks CARGO_BUILD_RUSTC=/Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/bin/rustc /Users/yagiz/.rustup/toolchains/stable-aarch64-apple-darwin/bin/cargo rustc --lib --target=aarch64-apple-darwin --package servo-url --manifest-path /Users/yagiz/Developer/url-parser/benchmarks/competitors/servo-url/Cargo.toml --target-dir /Users/yagiz/Developer/url-parser/build/./cargo/build --profile=release -- -Cdefault-linker-libraries=yes
[46/58] Building CXX object singleheader/CMakeFiles/demo.dir/demo.cpp.o
ninja: build stopped: subcommand failed.

error: linking with `/opt/homebrew/bin/ccache` failed: exit status: 1

From the error I'm guessing you set CMAKE_C_COMPILER or CMAKE_CXX_COMPILER to ccache. Don't do that - ccache is not the compiler.
Use CMAKE_<LANG>_COMPILER_LAUNCHER instead.

error: linking with `/opt/homebrew/bin/ccache` failed: exit status: 1

From the error I'm guessing you set CMAKE_C_COMPILER or CMAKE_CXX_COMPILER to ccache. Don't do that - ccache is not the compiler. Use CMAKE_<LANG>_COMPILER_LAUNCHER instead.

I was already using CMAKE_CXX_COMPILER_LAUNCHER but it didn't work. Building without Ninja fixes the issue unexpectedly.

Sorry, but I can't reproduce your issue. For me, using ccache works (tested on macOS 13), and I don't see why it shouldn't. Corrosion sets the Rust linker to CMAKE_CXX_COMPILER (Or the C compiler for C code), so as long as you don't mess with that variable (or use corrosion_set_linker), your Rust linker should not point to ccache`.

Building without Ninja fixes the issue unexpectedly.

Are you sure this isn't just a coincidence, because switching generators forces you to do a full reconfigure?
In any cases, for further investigation, I would need an example project which allows me to reproduce the issue.

In any cases, for further investigation, I would need an example project which allows me to reproduce the issue.

@jschwe Commenting out the highlighted code on Ada (which is corrosion_import_crate) fixes the issue for me, but I'm looking for a solution where I don't have to:
https://github.com/ada-url/ada/blob/main/benchmarks/CMakeLists.txt#L188

Or if you want easy integration and forget the details: Ccache.cmake

@OlivierLDff with our without ccache.cmake the following command fails on Ada
cmake -DADA_BENCHMARKS=ON -G Ninja -B build && cmake --build build

I found the fix, if somebody can tell me the disadvantage of it, I'd appreciate. Using NO_LINKER_OVERRIDE fixes it.
corrosion_import_crate(MANIFEST_PATH "competitors/servo-url/Cargo.toml" NO_LINKER_OVERRIDE PROFILE release)

Corrosion by default sets the Linker to CMAKE_CXX_COMPILER (or the C compiler for C projects) to fix two issues:

Linking C++ code requires linking the (correct) C++ standard library, which happens automatically if you use the compiler as the linker driver (same as what CMake would do).
The default linker rust selects is just broken for some targets when cross-compiling. This notably includes basically all -linux targets, where the linker selected by rustc is cc which always results in linking failures, because the linker is linking for the host target.

If those two scenarios don't apply to you (which they don't otherwise your build would have broken with linker errors), then setting NO_LINKER_OVERRIDE is fine.
I'd still like to point out that corrosion is setting the linker to either CMAKE_C_COMPILER or CMAKE_CXX_COMPILER, so if your linker suddenly points to ccache, that indicates you set the compiler to ccache somewhere (which you shouldn't, it may negatively affect also other CMake code that checks the COMPILER_ID or similar).

with our without ccache.cmake the following command fails on Ada

cmake -DADA_BENCHMARKS=ON -G Ninja -B build && cmake --build build

I cloned your project at commit c10cac90e0d3536018f0579712d42419b106d4c4, and I can't reproduce the issue.
ccache works fine. Maybe on your local machine you have some environment variable that sets CC to ccache or similar?


Compile error at Linux since version 9.0.1 : error: use of undeclared identifier 'gettid' (irondash_engine_context/linux/irondash_engine_context_plugin.cc:30:20:)

Is there an existing issue for this?

[X] I have searched the existing issues

Flutter Quill version
9.0.1
Other Flutter Quill packages versions
No response
Steps to reproduce
1.Compile : Click Debug button or use command flutter run -d linux、flutter build linux
Expected results
Compile success
Actual results
Compile failed
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Hello there, on behalf the Flutter Quill Team I would like to thank you for opening your first issue. Your inputs and insights are valuable in shaping a stable and reliable version for all our users. Thank you for being part of the open-source community!

Before every release, we test building the app on all platforms, you can take a look at this
It build successfully for Linux, it might something wrong in your local configurations or something on our side.

Before every release, we test building the app on all platforms, you can take a look at this
It build successfully for Linux, it might something wrong in your local configurations or something on our side.
in either case we need more info to be fix the issue

Thank you for your response, in my machine the lib libstdc++ is too old.

Before every release, we test building the app on all platforms, you can take a look at this
It build successfully for Linux, it might something wrong in your local configurations or something on our side.
in either case we need more info to be fix the issue

Thank you for your response, in my machine the lib libstdc++ is too old.

So were you able to fix it?

Before every release, we test building the app on all platforms, you can take a look at this
It build successfully for Linux, it might something wrong in your local configurations or something on our side.
in either case we need more info to be fix the issue

Thank you for your response, in my machine the lib libstdc++ is too old.

So were you able to fix it?

Havn't solve till now. The distribution my company used is Deepin which support up to stdlibc++-8-dev. I have tried to switch to ubuntu sources, but many of the system's dependencies rely on the lower version, so it failed. Any suggestions?

@ellet0  I contacted the author of the super_native_extensions library, which has been fixed in version 0.8.1, and quill will also be able to fix it after using the new version. I will use the local path dependency for the time being, and expect your new version.

@ellet0  I contacted the author of the super_native_extensions library, which has been fixed in version 0.8.1, and quill will also be able to fix it after using the new version. I will use the local path dependency for the time being, and expect your new version.

Thanks!

@ellet0 I contacted the author of the super_native_extensions library, which has been fixed in version 0.8.1, and quill will also be able to fix it after using the new version. I will use the local path dependency for the time being, and expect your new version.

Done, you can try 9.1.1

Let me know if the issue didn't got fixed

Let me know if the issue didn't got fixed

Yeah. LGTM since 9.1.1


Add pod backoff failure policy

Fixes #49
TL;DR;
The proposal is to set the backoff failure policy to a lower number (2m) to reduce the total number of failed pods.
Description
Profile jobs are using the default backoff failure policy (aka: 6m) which can create a lot of pods because the back-off count is reset when a Job's Pod is deleted or successful without any other Pods for the Job failing around that time.

The back-off limit is set by default to 6. Failed Pods associated with the Job are recreated by the Job controller with an exponential back-off delay (10s, 20s, 40s ...) capped at six minutes.

looks good, merging


Symbol search hangs VSCode

VSCode Version: 1.13.1
OS Version: Arch Linux, Kernel: 4.11.6-3

I am using VSCode on a huge PHP project. I am using felixfbecker/vscode-php-intellisense to index the codebase. Autocomplete, jump to definition, ... all work.
When I want to use symbol search panel interface freezes and CPU usage goes through the roof. Interface stays completely unresponsive for minutes. I confirmed that it is VSCode process that is doing this.
Any thoughts?
I already reported this in felixfbecker/vscode-php-intellisense#130 and they sent me here.

Try this https://marketplace.visualstudio.com/items?itemName=bmewburn.vscode-intelephense-client

@bmewburn Well, this refers to a generic issue with vscode, because it fetches the list in the main thread. I think you shouldn't promote your own product, this is a bug report with vscode.

@jens1o I'm just contributing to the discussion. @slashrsm might try the extension above and find the exact same problem. In which case it has helped confirm it as a vscode issue.

I tried Intelephense and it seems to be working well (symbol search + everything else).

Thanks!

I just tried intelephpense. Two differences:

Symbol search only starts after entering text, in php-intellisense the search starts immediately
Number of symbols returned. intelliphpense queries only the symbol name, php-intellisesnse only returns symbols that have the query string somewhere in their fully qulified name.

Overall, less symbols are returned to vscode which sesms to mask the problem.
Maybe the way symbols are searched in php-intellisesnse needs to be considered. I will have a look at some other IDEs to see what is the expected behavior here.

This is correct. The intelephense response is also limited to 100 items. I'm unsure how vscode handles the items. Perhaps the LSP workspace/symbol response needs an additional isIncomplete flag too? Microsoft/language-server-protocol#267

When this happens, can you check which process is using high CPU? I want to know whether it's the extensionhost process or the vscode renderer process. Try running this: ps -eo pcpu,user,pid,command | grep Code | grep "^\s*[1-9]" to get the Code procs with high CPU.
@kieferrm does your crazy extension cover language servers returning many symbols?

The command above returns
37.3 slashrsm  8288 /opt/visual-studio-code/code --type=renderer --js-flags=--nolazy --no-sandbox --primordial-pipe-token=9696A54299E3A25F67A93EB57322ED26 --lang=sl --node-integration=true --background-color=#1e1e1e --disable-blink-features=Auxclick --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553 --disable-accelerated-video-decode --service-request-channel-token=9696A54299E3A25F67A93EB57322ED26 --renderer-client-id=13 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd
 7.2 slashrsm  8309 /opt/visual-studio-code/code /opt/visual-studio-code/resources/app/out/bootstrap --type=extensionHost
 2.3 slashrsm  8310 /opt/visual-studio-code/code /opt/visual-studio-code/resources/app/out/bootstrap --type=watcherService

I've noticed this same issue with a c++ project. I also noticed that if you slow down the rate of typing into the dialog then you can usually avoid the hang and the results are not horribly slow. appears that once you trigger some threshold of queued/interrupted searches then it just hangs everything.

@kieferrm You have an extension that just sends lots of traffic, right? Does it cover a language server returning lots of symbols?

@roblourens no it doesn't (yet).

Is this still an issue?
I think this isn't a PHP issue but a symbol search issue, @mjbvz or someone else?

@bpasero didn't you just add cancellation of getWorkspaceSymbols?

I tested on 1.27.1 in a C++ project that had been consistently reproducing this, even several weeks ago. So far I can't get the issue anymore.

@mjbvz yes, when the typed input changes or when quick open closes, the token will get cancelled

@slashrsm is this still reproducible with our latest insider builds?


ziomon/ziomon_fcpconf: Compilation errors

Hi, when I try to run ziomon/ziomon_fcpconf I get following errors:
Global symbol "$map_dev" requires explicit package name (did you forget to declare "my $map_dev"?) at ziomon/ziomon_fcpconf line 61. Global symbol "$map_dev" requires explicit package name (did you forget to declare "my $map_dev"?) at ziomon/ziomon_fcpconf line 65. Unmatched right curly bracket at ziomon/ziomon_fcpconf line 67, at end of line syntax error at ziomon/ziomon_fcpconf line 67, near "}" Execution of ziomon/ziomon_fcpconf aborted due to compilation errors.
Probably some cycle was disappeared from line 60.

Your are right. During the GPL->MIT conversion process from 1.39.0 to 2.0.0 obviously one line has been lost.
The following patch fixes the problem:
diff --git a/ziomon/ziomon_fcpconf b/ziomon/ziomon_fcpconf
index 7643540..c51690e 100644
--- a/ziomon/ziomon_fcpconf
+++ b/ziomon/ziomon_fcpconf
@@ -58,6 +58,7 @@ sub store_mapper_devices
        my $src_dir = shift();
        my @entries = grep { ! /^\./ } dir_content($src_dir);

+       foreach my $map_dev (@entries) {
                my $tf = catfile($src_dir, "$map_dev");
                my $mm = `stat -L -c%t:%T $tf`;
                chomp($mm);


consider adding --head option?

As the supplement to --tail, this might be used when user only care about the first nth elements in the result.
Although, I can use | head -n | fzf to archieve the same goal, but a bit of verbose, any thought?

It isn't that verbose.
| head -n | fzf
| fzf --head=n

fzf follows the Unix philosophy and tries not to implement features that can be outsourced to other programs.
--tail is a different story. ... | tail -n | fzf isn't identical to ... | fzf --tail=n. With --tail, fzf can show the last entries at the moment before the stream is complete.
https://junegunn.github.io/fzf/tips/browsing-log-streams/


Base vocab

Added base vocab to attribute resolution based on spec issue 85.
Awaiting spec issue 87 to fix automated tests - PR #50 .

@simonoakesepimorphics
PRs have been merged into the specification repository
we've cut a 0.2 release
https://github.com/opengeospatial/netcdf-ld/releases/tag/v0.2
and the overnight build of the doc should run tonight
this should give stable links to the tests
please continue to report any issues (we've no qualms about a v0.3 to fix errors)

@marqh Tests are passing now.

@marqh Please can you approve this as soon as is convenient because the spec tests feature depends on it.


What is the purpose of the "-loop" suffix at the end of some character animations?

What is your question?
Certain character animations in the base engine have a -loop suffix at the end of them..
For example theres an idle animation and theres an idle-loop animation...
Whats the purpose of this suffix?

its for animations after idle or any animation ended,
when it ended, it switch to the loop animation

Interesting...
Thanks :D


pull request for e2e test at 01/24/2017 17:15:06

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Applying indent attribute throws container.containsOffset(position.offset) fail assertion

Is there an existing issue for this?

[X] I have searched the existing issues

Flutter Quill version
10.6.5
Steps to reproduce

Insert a header at the beginning of the document (write whatever you want).
Create a new line.
Below the new line you created in the previous step, write some text.
Apply the indent attribute to this last line (any that is not the first one) and you will see how this happens.

Expected results
Apply indent to any line without exception calls.
Actual results
When apply indent to any line that is not the first one, text_line throws an exception by the container is not registering the current offset position.
Additional Context
It seems that when we try to indent a line text_line throws the typical exception "container.containsOffset(position.offset)" which seems to tell us that the node we are selecting is not at the offset that the position is telling the editor.
But, I was wrong, I thought that the Offset was reloaded, instead of keeping the values it had before applying the indentation attribute.
Explanation
it seems that there is a problem with the childAtPosition function of RenderEditableContainerBox which compares in a while if the target we currently have corresponds to the node found through the queryChild method. But, is this not right? Yes, but it seems that there is an error at the level of equals and hashcode (this last one is still a theory that I am testing).
This would be the function in question:
RenderEditableBox childAtPosition(TextPosition position) {
  assert(firstChild != null);
  final targetNode = container.queryChild(position.offset, false).node;

  var targetChild = firstChild;
  while (targetChild != null) {
    /// The issue is here with the equality
    if (targetChild.container == targetNode) {
       break;
    }
    final newChild = childAfter(targetChild);
    if (newChild == null) {
       // At start of document fails to find the position
       // here is where the issue start
       targetChild = childAtOffset(const Offset(0, 0));
       break;
    }
    targetChild = newChild;
  }

  if (targetChild == null) {
     throw 'targetChild should not be null';
  }
  return targetChild;
}

What happens with this?
Let's take an example, let's assume that the editor has a text such that (I'll use markdown syntax to not complicate the example using Deltas):
# First header

any content

Supposing that we are right at the beginning of the third line (i.e. where "any content" starts), the caret should be with a TextPosition with an offset of 13. Having this value now, if we apply indent to the third line, the error will now occur. Why? Obviously the position was not updated neither in QuillController's updateSelection nor much less from our raw_editor_state_text_input_client_mixin since the latter is the one that maintained this last value.
Since we mentioned our text_input_client we have to mention that when we apply the indent, it goes and calls _updateComposingRectIfNeeded which our editor calls getLocalRectForCaret to get the current Rect of the caret. Why do I mention getLocalRectForCaret? This is because when it is called, then at the same time, in order to have which node is selected it calls childAtPosition. Do you see the problem? Every time we update the position of the caret, the node is searched, at this point there is no problem.
But, it seems that when we apply indent, something changes inside the editor, which is not able to determine if the node we obtained is really the one found through the targetChild of the code sample I showed before. It's strange, isn't it? Even though queryChild DOES find the node, when the loop is executed and we compare the RenderEditableBox container, it is not able to know if it is really equal or not. This only happens if indent is applied. With any other attribute it doesn't seem to be happening (although I've noticed that link sometimes suffers from this problem as well).
Concluding with this, it seems that since it is not able to properly compare the node obtained (which is the one we are actually selecting) with the node that childAtPosition returns, then it throws an error. This is mostly because since it is not able to obtain any new value that satisfies the condition, then it takes the first node it finds from the document and returns it, which causes this problem, since it is clear that it is more than likely that the first node is not or does not contain the offset in which we are.
I have a theory that the RenderEditableBox isn't updated fast enough so that when the editor gets it, it can compare the new value to the old one.
Having said that, it looks like we'll have to figure out if this is just an equality issue or something like one part being updated way before the other.
https://github.com/user-attachments/assets/f00d5df8-f035-4469-ac38-cfb9a665d991

@singerdmx @EchoEllet
What I'm going to say is subject to change, because I'm going to test if this could be an update bug. However, should we add a new way to identify our nodes? That is, add something like an identifier or something that allows us to go directly to them without having to compare nodes that may have changed between them but are basically the same.
This is just an example of how we could do it (not equally, because the Delta structure we have is the Quill js standard and will stay that way) as BlockNote does in its node structure.

However, I'm not 100% sure about this as it would bring greater complexity as it is quite certain that we will have to change many parts of the code due to this new way of identifying the nodes.
Most likely we will have to review the code and see that everything is correct and that it is just a mistake that was accidentally implemented while other errors were being fixed.

Update: i added id property (it's auto generated when the node is created) and it solves the issue with the indent (because searching by id makes more easy compare). But comes with issues because if we split a line, then now the nodes takes a new id and throws error.

Update: I managed to notice that we don't need to add a complicated structure with ids (I managed to fix the problem where splitting a line into two parts anyway). It seems that the QuillRawEditor is directly updating itself before the RenderEditableContainerBox which makes it not notice the changes and this error occurs.

By now, i switching between versions to watch which version does not throw this error.

Finally! I get where the issue start. #2239 fix the composing range rect but, also add the discussed issue.

If the change is not documented or clear, then I would suggest reveting the change and asking them for more details. New changes should be possible to understand from other developers' perspectives.

It seems the issue comes from giving the selection of the QuillController to the composingRange var. Removing that part of code makes the code run without issues.


Request Feature If not Exist

Thanks in advance for all time and effort you put in this awesome config .
Can you provide simple shortcut for toggling light and dark mode please

Hello @mbaneshi 👋
What do you mean?

I mean how can we toggle between light and dark mode?

Well I'm not sure how that would work.
Tmux doesn't have such a feature and I'm not sure how it would compose with the various terminal emulator apps. Do they have dark vs light mode?

It should be implemented for example for iterm ,I think defining one function that can change color schema , and bind that to a key would be a solution . am I right ?


Compilation errors with 0.4.0-rc

Hello, i've found out that once i add thaw in a project (i used an actix starter from leptos), i get an errors on compile.
Code that gets an error :
#[server(AuthCheck, "/api")]
pub async fn auth_check_session() -> Result<(), ServerFnError> {
    use actix_identity::Identity;
    use leptos_actix::*;

    let info: Option<Identity> = extract().await.unwrap_or_default();
    dbg!(info.is_some());
    Err(ServerFnError::ServerError("User is not connected".into()))
}

And an error i get is :
error[E0432]: unresolved import `leptos_actix`
 --> src/db/user/auth.rs:6:9
  |
6 |     use leptos_actix::*;
  |         ^^^^^^^^^^^^ use of undeclared crate or module `leptos_actix`
  |

Using thaw 0.4.0-rc with features : csr, hydrate, ssr and defined it as :
csr = [..., "thaw/csr"]
ssr = [..., "thaw/ssr"]
hydrate = [..., "thaw/hydrate"]
P.S Also getting error if try to apply SSRMountStyleProvider in main.rs aswell

Can I see your Cargo.toml file?

Sure :
[package]
name = "secret"
version = "0.1.0"
edition = "2021"

[lib]
crate-type = ["cdylib", "rlib"]

[dependencies]
actix-files = { version = "0.6", optional = true }
actix-web = { version = "4", optional = true, features = ["macros"] }
actix-session = { version = "0.10.1", features = [
  "cookie-session",
], optional = true }
actix-identity = { version = "0.8.0", optional = true }
console_error_panic_hook = "0.1"
http = { version = "1.0.0", optional = true }
leptos = { version = "0.7", features = ["nightly"] }
leptos_meta = { version = "0.7" }
leptos_actix = { version = "0.7", optional = true }
leptos_router = { version = "0.7", features = ["nightly"] }
reactive_stores = "0.1"
wasm-bindgen = "=0.2.99"
thaw = { version = "0.4.0-rc", default-features = false, features = [
  "nightly",
  "ssr",
  "hydrate",
  "csr",
] }
surrealdb = { version = "2", optional = true }
icondata_core = "0.1.0"
icondata_ai = "0.0.10"
leptos_i18n = { version = "0.5.0-rc1" }
serde = { version = "*", features = ["derive"] }
serde_json = "1"
thiserror = "2.0.6"
cfg-if = "1"

[features]
csr = ["leptos/csr", "thaw/csr"]
hydrate = ["leptos/hydrate", "thaw/hydrate", "leptos_i18n/hydrate"]
ssr = [
  "dep:actix-files",
  "dep:actix-web",
  "dep:leptos_actix",
  "dep:actix-session",
  "dep:actix-identity",
  "dep:surrealdb",
  "leptos/ssr",
  "leptos_meta/ssr",
  "leptos_router/ssr",
  "thaw/ssr",
  "leptos_i18n/actix",
]

# Defines a size-optimized profile for the WASM bundle in release mode
[profile.wasm-release]
inherits = "release"
opt-level = 'z'
lto = true
codegen-units = 1
panic = "abort"

[package.metadata.leptos]
# The name used by wasm-bindgen/cargo-leptos for the JS/WASM bundle. Defaults to the crate name
output-name = "secret"
# The site root folder is where cargo-leptos generate all output. WARNING: all content of this folder will be erased on a rebuild. Use it in your server setup.
site-root = "target/site"
# The site-root relative folder where all compiled output (JS, WASM and CSS) is written
# Defaults to pkg
site-pkg-dir = "pkg"
# [Optional] The source CSS file. If it ends with .sass or .scss then it will be compiled by dart-sass into CSS. The CSS is optimized by Lightning CSS before being written to <site-root>/<site-pkg>/app.css
style-file = "style/main.scss"
# Assets source dir. All files found here will be copied and synchronized to site-root.
# The assets-dir cannot have a sub directory with the same name/path as site-pkg-dir.
#
# Optional. Env: LEPTOS_ASSETS_DIR.
assets-dir = "assets"
# Tailwind integration
tailwind-input-file = "style/tailwind.css"
# The IP and port (ex: <IP_ADDRESS>:3000) where the server serves the content. Use it in your server setup.
site-addr = "<IP_ADDRESS>:3005"
# The port to use for automatic reload monitoring
reload-port = 3001
# [Optional] Command to use when running end2end tests. It will run in the end2end dir.
#   [Windows] for non-WSL use "npx.cmd playwright test"
#   This binary name can be checked in Powershell with Get-Command npx
end2end-cmd = "npx playwright test"
end2end-dir = "end2end"
#  The browserlist query used for optimizing the CSS.
browserquery = "defaults"
# The environment Leptos will run in, usually either "DEV" or "PROD"
env = "DEV"
# The features to use when compiling the bin target
#
# Optional. Can be over-ridden with the command line parameter --bin-features
bin-features = ["ssr"]

# If the --no-default-features flag should be used when compiling the bin target
#
# Optional. Defaults to false.
bin-default-features = false

# The features to use when compiling the lib target
#
# Optional. Can be over-ridden with the command line parameter --lib-features
lib-features = ["hydrate"]

# If the --no-default-features flag should be used when compiling the lib target
#
# Optional. Defaults to false.
lib-default-features = false

# The profile to use for the lib target when compiling for release
#
# Optional. Defaults to "release".
lib-profile-release = "wasm-release"

[package.metadata.leptos-i18n]
default = "en"
locales = ["en", "fr"]
namespaces = ["layout"]

Delete as follows, and then try again:
wasm-bindgen = "=0.2.99"
thaw = {
  version = "0.4.0-rc",
- default-features = false,
  features = [
  "nightly",
-  "ssr",
-  "hydrate",
-  "csr",
] }
surrealdb = { version = "2", optional = true }


Date with high timezone and low hour regression test

Hi everybody,
since 4.1.0 we have a regression on date validation.
I wrote a test to recreate it, but I wasn't able to fix the validation in the code.
Can you please have a look?
Thanks!

Thanks.
This is cc #431 / #418.

This is fixed in v4.2.


Joblib Format

Is there any way to save "model.pkl" as "model.joblib" in model versioning.
catalog.yml
example_model:
  type: kedro_mlflow.io.artifacts.MlflowArtifactDataSet
  data_set:
    type: kedro_mlflow.io.models.MlflowModelSaverDataSet
    flavor: mlflow.sklearn
    filepath: data/06_models/sklearn_model

Hi,
basically kedro-mlflow can do anything mlflow can, but I do not add extra features to logging.
Looking at [mlflow.sklearn flavor documentation]
(https://www.mlflow.org/docs/latest/python_api/mlflow.sklearn.html#mlflow.sklearn.log_model), we can see that there is a serialization_format argument :

serialization_format – The format in which to serialize the model. This should be one of the formats listed in mlflow.sklearn.SUPPORTED_SERIALIZATION_FORMATS. The Cloudpickle format, mlflow.sklearn.SERIALIZATION_FORMAT_CLOUDPICKLE, provides better cross-system compatibility by identifying and packaging code dependencies with the serialized model.

Let's look at available formats:
from mlflow.sklearn import SUPPORTED_SERIALIZATION_FORMATS
print(SUPPORTED_SERIALIZATION_FORMATS) # ['pickle', 'cloudpickle']

joblib is unfortunately not supported currently. If you want to make it available, you should open an issue directly in mlflow repo.
Example with kedro-mlflow
If you want to change the serialisation format, add these lines in your catalog:
example_model:
  type: kedro_mlflow.io.artifacts.MlflowArtifactDataSet
  data_set:
    type: kedro_mlflow.io.models.MlflowModelSaverDataSet
    flavor: mlflow.sklearn
    filepath: data/06_models/sklearn_model
    save_args:
        serialization_format: pickle  # put joblib here when it will be available in mlflow

Thank you @Galileo-Galilei

Hey @Galileo-Galilei thanks for quick responses.
Interestingly below code serves our purpose of saving model as joblib, let me know if you see any loop hole.
example_model:
  type: kedro_mlflow.io.artifacts.MlflowArtifactDataSet
  data_set:
    type: pickle.PickleDataSet
    backend: joblib
    filepath: data/06_models/sklearn_model/model.joblib

Hi @tpanthera, as you explain this will work and save the artifacts properly. You can retrieve it later manually.
However, I think it is better to use MlflowModelSaverDataset when you can because you automatically benefit from all the mlflow addons. Indeed when you log a "model" in the mlflow sense, it does not only store the artifact (i.e. the .pkl or the .joblib file) but also some metadata (a MLModel configuration file, a conda_env.yml file...). thanks to these metadata, mlflow enable to automatically benefit from:

the model registry to register different versions of the same model (with different "stage" in the lifecycle and a promotion process through the UI) which is very useful for production purpose
serving / batching (mlflow has a command to automatically serve a model as an API and to deploy it to different target platforms)
input control: if the model schema is specified, mlflow will perform data validation of any inputs you pass to your model and raise an error if column names or types are mismatching with the training data

I do personnally like to not rebuild everything on my own and use mlflow built-in capabilities, but if you just want to track the model and you do not plan to use the model registry or the serving functionalities, your solution is totally fine.


[sw, dif_plic] Reset the PLIC peripheral on initialisation

Resetting a peripheral on initialisation ensures that there is no implicit configuration, for example, from boot_rom after jump to flash.

PLIC_ID_TO_INDEX(kDifPlicIrqIdLast) -> kDifPlicIrqIdLast, because in the case of calculating the register count, we don't deal with bit indexes, but rather the count of IDs. Because the IDs start from 1, kDifPlicIrqIdLast correspond to the total count of the IDs.

In the latest push:

Addressed all of the review comments.

I'll leave the review of this PR to the software team, @gkelly or @mcy can you have a look?

This looks good to me, @lenary had some comments so I'll hold off on merging until he's had another chance to look.

In the latest push:

Have addressed all of the outstanding review comments.

I expect to discover the buggs if any - when I am updating the PLIC mock tests.

In the latest push:

Have deleted the plic_reset in-function TODO. The TODO is now reflected in the function description.


NLP++ type checking

@dehilsterlexis
NLP++ is loosely typed.
When a concept is expected but a string is supplied (eg to a function call), things go bad, often silently.
NLP++ should have built-ins like
isCon
isStr
isNum
isPunct

isPn (for parse tree node)


Change MAX_EFFECTIVE_BALANCE will cause prysm or lighthouse failed to sync with lodestar

Describe the bug
I tried to run a new testnet, with MAX_EFFECTIVE_BALANCE = 320 ETH.
I run the testnet with 1 EC: geth, 3 consensus nodes: 2 - lodestar nodes + 1 lodestar validator, 1 prysm node, 1 lighthouse node.
Lodestar can create new block and successfully past the merge. But both prysm and lighthouse failed to sync with loadestar.
Same thing happen when I start another testnet: 1 lighthouse node + 1 lighthouse validator, 1 prysm node, 1 lodestar node.
Pysm can sync with ligthouse, by lodestar was not.
Error log from Prysm:
[2024-04-02 14:57:55]  WARN initial-sync: Block processing failure error=failed to validate consensus state transition function: could not execute state transition: could not process block: could not process block header: proposer index: 59 is different than calculated: 90 firstSlot=6 firstUnprocessed=6 lastSlot=6 root=0x965564714926063dad38b88ec0309a8fdc1148ca3708bf87e0a0efaa9c3dc111

Error log from lighthouse:
Apr 02 07:57:49.703 DEBG Missed snapshot cache                   block_delay: None, parent_root: 0x630339bc76ca60d3bc43829776777cef9823754f41ae0aa432fde04d13ba344d, parent_slot: 0, slot: 6, service: beacon
Apr 02 07:57:49.703 DEBG Invalid block received                  outcome: IncorrectBlockProposer { block: 59, local_shuffling: 90 }, msg: peer sent invalid block
Apr 02 07:57:49.703 DEBG Batch processing failed                 service: sync, error: Peer sent invalid block. Reason: IncorrectBlockProposer { block: 59, local_shuffling: 90 }, imported_blocks: 0, last_block_slot: 28, chain:<PHONE_NUMBER>743628209, first_block_slot: 0, batch_epoch: 0
Apr 02 07:57:49.704 DEBG Batch processing result                 client: Lodestar: version: v1.16.0, batch_epoch: 0, start_slot: 0, end_slot: 31, downloaded: 0, processed: 0, processed_no_penalty: 27, state: Processing(16Uiu2HAmSdjN4jTXvkGbYxbaL2ko8PezhsZAMVQR5nW8Hgiit7VC), batch_ty: blocks, result: NonFaultyFailure, chain:<PHONE_NUMBER>743628209, service: sync

I don't know if this is lodestar's bug or tech debt.
Expected behavior
Both prysm and lighthouse can sync with lodestar when start new testnet with MAX_EFFECTIVE_BALANCE = 320 ETH.
Steps to reproduce

Set MAX_EFFECTIVE_BALANCE = 320 ETH
Start lodestar node + lodestar validator.
Run prysm and lighthouse with same config and connect to lodestar.

Additional context
No response
Operating system
macOS
Lodestar version or commit hash
v1.16.0

closing as stale


Is there a way to change the underline color?

Not an issue. Just use the tintColor property as done in the Demo project.


Translate the text on the 404 page

For some reason none of the text here was translated before. Fixed!

Gonna merge this once the tests pass.


Parallelization changes sometimes throw FlurlHttpException stating the collection was modified

After merging #10 we got an exception this morning while tag processing. This didn't happen while testing, I'll look into it.
Flurl.Http.FlurlHttpException: Call failed. Collection was modified; enumeration operation may not execute. GET https://hcr.io/api/repositories/***/***/tags ---> System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
   at System.ThrowHelper.ThrowInvalidOperationException_InvalidOperation_EnumFailedVersion()
   at System.Collections.Generic.Dictionary`2.ValueCollection.Enumerator.MoveNext()
   at Flurl.Http.FlurlRequest.WriteRequestCookies(HttpRequestMessage request)
   at Flurl.Http.FlurlRequest.<SendAsync>d__19.MoveNext()
   --- End of inner exception stack trace ---
   at Flurl.Http.FlurlRequest.<HandleExceptionAsync>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Flurl.Http.FlurlRequest.<SendAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Flurl.Http.FlurlRequest.<SendAsync>d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Flurl.Http.HttpResponseMessageExtensions.<ReceiveJson>d__0`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Harbor.Tagd.API.HarborClient.<GetTags>d__13.MoveNext() in /home/jenkins/workspace/tagd-deployment_master-JF7YPWJZTOOXFXCSSMKKW3M2EI6YOS6ORV23RH3WIKLWAALDS2CA/tagd/src/Harbor.Tagd/API/HarborClient.cs:line 75
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Harbor.Tagd.TagEngine.<ProcessRepository>d__12.MoveNext() in /home/jenkins/workspace/tagd-deployment_master-JF7YPWJZTOOXFXCSSMKKW3M2EI6YOS6ORV23RH3WIKLWAALDS2CA/tagd/src/Harbor.Tagd/TagEngine.cs:line 147
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Harbor.Tagd.TagEngine.<ProcessProject>d__11.MoveNext() in /home/jenkins/workspace/tagd-deployment_master-JF7YPWJZTOOXFXCSSMKKW3M2EI6YOS6ORV23RH3WIKLWAALDS2CA/tagd/src/Harbor.Tagd/TagEngine.cs:line 139
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Harbor.Tagd.TagEngine.<Process>d__9.MoveNext() in /home/jenkins/workspace/tagd-deployment_master-JF7YPWJZTOOXFXCSSMKKW3M2EI6YOS6ORV23RH3WIKLWAALDS2CA/tagd/src/Harbor.Tagd/TagEngine.cs:line 80

Well shit: tmenier/Flurl#318. We may be able to work around it. More digging required!

This breaks even if I explicitly create a single client and enable cookies before sending any requests. I think the best thing to do here is to revert #10 and deal with the slowdowns until this becomes a part of Harbor Proper (goharbor/harbor#5420). I don't really want to rewrite the API stack between then for some small performance increases.

I know this is old but there's a much better cookie experience coming in Flurl 3.0 if you're still interested:
https://github.com/tmenier/Flurl/issues/506


[release/1.7] Revert errdefs package

Switching to the errdefs package in 1.7 is a breaking change since the new errdefs package was no stabilized. We can consider moving to the errdefs package once it is marked as 1.0 after the containerd 2.0 release.
As part of the changes in errdefs, we made sure that even if we don't have exact type compatibility, we can rely on interface compability. This will ensure that any version of the errdefs package or any similar errdefs package which uses the same interfaces will have error matches. Switching this in 1.7 was premature and unnecessary considering we can get compatibility with the interface checks. This has now been reverted and the error definitions synchronized with errdefs to ensure the interfaces are included.
This is currently causing some 1.7 builds to break after version resolution and is a blocker for 2.0 since it prevents us from moving up the errdefs package due to a circular dependency. This dependency could also be solved by bumping 1.7 to errdefs 0.2.0, but that is introducing another breaking change to 1.7 for a non-1.0 package.

Ugh; this will be a painful one. Wasn't the errdefs package specifically MEANT so that errors between v2 and v1 could be handled? At least this will be a painful one with moby <--> buildkit <--> containerd

Wasn't the errdefs package specifically MEANT so that errors between v2 and v1 could be handled? At least this will be a painful one with moby <--> buildkit <--> containerd

Yes, but errdefs 0.1.0 didn't solve that and can makes the situation more difficult since the package isn't 1.0 and not stable. Also buildkit and moby haven't adopted the errdefs package for their definitions and errdefs.Is functions will still work with this change. The interface approach is more reliable for now and what we already do for compatibility with Moby errors. This change still ensures errors will be handled between v1 and v2.

Yeah, mostly concerned that code consumed from BuildKit will match different errors than Moby code if only one will update, and updating only the containerd dependency likely means that none of the cerrdefs.Is(...) will match anything
git describe --tags --match="v[0-9]*" HEAD
v0.16.0

git grep '"github.com/containerd/errdefs"' | wc -l
      97

git describe --tags --match="v[0-9]*" HEAD
v27.3.0
git grep '"github.com/containerd/errdefs"' | wc -l
     126
git grep 'cerrdefs.Is' | wc -l
      90

BuildKit is doing its own thing with error handling and not directly handling errors from containerd yet, so that is not a concern yet. There is definitely still ongoing work in both BuildKit and Moby to get the error handling unified, but we shouldn't even try to rely on strict type matching until we have a 1.0 of errdefs, we should use interface matching via Is functions for now when needed.


[FLINK-33008] Refactor to use KubernetesClient from JOSDK Context

What is the purpose of the change
Refactor code to use KubernetesClient from JOSDK Context
Brief change log
KubernetesClient is passed from josdkContext to flinkResourceContext. The rest of the code get client from either context.
Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changes to the CustomResourceDescriptors: (no)
Core observer or reconciler logic that is regularly executed: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Thanks Gyula for the review, have addressed the comment in latest commit


Fix dependency conflicts azure-messaging-eventhubs-checkpointstore-blob SDK

Please fix the dependency conflicts as mentioned below

You can find the latest report at https://azuresdkartifacts.blob.core.windows.net/azure-sdk-for-java/staging/dependency_conflictlist.html which may change once azure-core releases.

This was fixed as part of the August release.


Nested Page Object length errors out

I get an error whenever I call any function that calls length on my nested page object. The page object works just fine other than being unable to call length (I can call eq(10) on the page object, grab a field and interact with that nested page object)
> this.fields.length
jquery.js:1541 Uncaught Error: Syntax error, unrecognized expression: [data-test-beta-transaction-panel] scope(scope) {
      return this.extend({ scope });
    }
    at Function.Sizzle.error (jquery.js:1541)
    at Sizzle.tokenize (jquery.js:2193)
    at Function.Sizzle [as find] (jquery.js:815)
    at jQuery.fn.init.find (jquery.js:2873)
    at new jQuery.fn.init (jquery.js:2988)
    at jQuery (jquery.js:139)
    at AcceptanceNativeEventsExecutionContext.$ (native-events-context.js:54)
    at AcceptanceNativeEventsExecutionContext.find (native-events-context.js:91)
    at executionContext.run.context (count.js:91)
    at AcceptanceNativeEventsExecutionContext.run (native-events-context.js:19)

for my collection that looks like:
fields: collection(TransactionFieldPageObject.scope('[data-test-beta-transaction-value-editor]')),

turned out to be an issue of other dependencies causing my main app to use 0.4.6 despite me specifying in package.json that I needed 0.4.8 🤷♂  looks like everything is fine once I manage to upgrade


leetcode problem  2560. House Robber IV

Hey @Saikat2407 , I would like to contribute to this problem, do assign it to me.

@Saikat2407  done, please check.


Cannot load custom adapters

I'm trying to run the logstash adapter but it doesnt' works.
In master is already added in the custom/modules.go.
We can see that the adapters loaded are: udp tls raw syslog tcp

Hey, we're using the logstash adapter as well.
Did you add _ "github.com/looplab/logspout-logstash" to the modules.go file?
Otherwise this works as well:

go get logspout repo
go get logspout-logstash repo
copy logspout-logstash files into adapters/logstash
add to modules.go: _ "github.com/gliderlabs/logspout/adapters/logstash"
in our docker-compose: - ROUTE_URIS=logstash://logstash:5000 (where logstash is a linked service)


Vulnerability assessment findings are not shown in Log Analytic workspace

Hello,
I have enabled Continous export in ASC and installed a Qualys extension into VM. Vulnerabilities generated under the "Vulnerabilities in your virtual machines should be remediated" recommendation, but these vulnerabilities are not shown in Log Analytics.
I should see vulnerabilities in Log Analytics according to the new ASC update https://docs.microsoft.com/en-us/azure/security-center/release-notes#vulnerability-assessment-findings-are-now-available-in-continuous-export

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

ID: e15ac4e7-7e04-980d-27e1-cf5837763cf3
Version Independent ID: 69f74d6d-c0ee-18cd-9457-f2dbb7771f31
Content: Release notes for Azure Security Center
Content Source: articles/security-center/release-notes.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@serxansherif
Thanks for your feedback! We will investigate and update as appropriate.

@serxansherif
Thank you for your post!
The documentation you linked states, "Use continuous export to stream your alerts and recommendations in real time to Azure Event Hubs, Log Analytics workspaces, or Azure Monitor". Which sounds like you're able to choose one of the three features to stream your alerts to.

If you'd like to use continuous export to stream your alerts to a Log Analytics workspace, you can do so by following this link:
Continuous export to a Log Analytics workspace
After enabling this feature, if you're still running into issues, can you please email me with the below information so I can enable a one-time free support request for you, so our support engineers can take a close look into this and help resolve this issue.
Email<EMAIL_ADDRESS>Subject: ATTN - James Tran
Body:
Azure Subscription ID
Link to this GitHub issue
If you have any other questions, please let me know.
Thank you for your time and patience throughout this issue.

@serxansherif
I just wanted to check in and see if you required additional assistance or if you were able to resolve this issue? Since I haven't heard from you in a while, I'll go ahead and close out this issue at the end of the day pending a response from your end.
If you require additional assistance, please feel free to tag me or send me an email using the information above and I'd be more than happy to continue working with you.
If you have any other questions, please let me know.
Thank you for your time and patience throughout this issue.


BD не устанавливается

When installed, bd freezes in half of the installation. Already tried different versions, but nothing helped. In the latest bd version, the slider did not move at all during installation.

That means your internet is preventing the installer from downloading the resources it needs.


LLVM supported versions

I thought it might be worth an issue to discuss the supported versions of LLVM.
This issue comes from the discussion in this https://github.com/crystal-lang/crystal/pull/8538.
Why?
Support for older versions creates more maintenance in code, and we can miss out on taking advantage of new features in LLVM.
Why Not?
Not supporting older versions can make support of deployments and platforms harder.
Currently
LLDB support is being added and is using features that are outside our LLVM support window (3.x)
Proposal 1
Crystal could maintain a soft 3-year window LLVM support.
After some digging around on the llvm site, it seems like they have rough support of 3 years for their toolchain.
http://llvm.org/docs/DeveloperPolicy.html#updating-toolchain-requirements
Note: This is not LLVM supported versions, just their toolchain.
Proposal 2
We could follow the Ubuntu LTS LLVM package.
This is a widely deployed target and would make deployment easier.
This was in the above PR https://github.com/crystal-lang/crystal/pull/8538#issuecomment-580423607.
Proposal 3
We could update LLVM whenever we have a feature or blocker that would benefit the project.
This is more like Rust, which is discussed here, which updates more based on need.  This would enable us to be more liberal in implementing features like LLDB.

The availability of recent packages for LLVM ain't much of a problem, except for old linux distributions, such as Raspbian Stretch or Centos 6 (EOL 2020-11-30).
Distribution provided packages:

Ubuntu 16.04: LLVM 6 (xenial-updates);
Ubuntu 18.04: LLVM 9 (bionic-updates);
Debian Jessie (oldoldstable): LLVM 6;
Debian Stretch (oldstable): LLVM 7;
Debian Buster (stable): LLVM 8 (buster-backports);
Raspbian Stretch: LLVM 4;
Raspbian Buster: LLVM 8;
Centos 6 : LLVM 3.6;
Centos 7 : LLVM 7.

The LLVM APT repository has updated packages for i386 and amd64:

Ubuntu 14.04 (EOL): up to LLVM 8 ;
Ubuntu 16.04, 18.04: up to LLVM 11 ;
Debian Jessie: up to LLVM 8.
Debian Stretch, Buster: up to LLVM 11.

I don't think sticking to a fixed rule such as "we support the last N releases of LLVM" is a good idea. It's IMO better to see which versions are widely available, and which LLVM versions are providing what we need, and the cost of maintaining support for older releases. The LLVM C API isn't breaking that much anymore, and most of our C++ extensions is now available in the official C API since LLVM 7 (DIBuilder, Atomics).

From the availability of packages, there are zero reasons to still support LLVM 3.x.

Keeping anything below LLVM 6 feels useless. Only Centos 6 would be affected and it's nearing EOL. Sadly, Raspbian jessie/stretch are lagging behind Debian, but Buster has LLVM 8, and older releases can try the Debian armhf packages (I did that once).

LLVM 7 introduces an official C API for most of what our C++ extension provides (DIBuilder, Atomics).

IMO: I see little reason to support anything below LLVM 7.

@ysbaddaden so shall we do the clean up then?
The only drawback is here that we also expose llvm module in our standard library so if someone will need 3.x support in their code they will be out of luck.

Currently, the build process stresses only uses the two latest LLVM versions. Usually darwin build are bumped before linux to ensure homebrew releases will work with updated llvm formula.
There are no strick guarantees on what LLVM versions are supported other than that. Even if there is code around that.
An overdue in the CI is to stress different explicit versions of binaries dependencies like LLVM and others (libz, libyaml, openssl, etc). Without something like that at some extent there is no hard guarantee.
Regarding a lower bound, I would not limit it by features like debug support. And newer llvm consume more resources while compiling crystal code. So that might be something to have in mind.

@bcardiff When I compile crystal on my computer it takes about 1.2 GB so it is still possible to compile on Raspberry Pi 4 2GB and up. Then that code can be used on on all other RPi's.

We should provide support for what the distros can compile with. There's no sense at all in only supporting LLVM versions that are too new for debian and missing out on getting an official package.
Centos is, however, a lost cause.

CentOS/RHEL 7 has a newer LLVM (8 I think?) in the software collections,
and 8 has a newer one as part of the app streams.
On Wed, Feb 5, 2020, 6:59 PM Stephanie Hobbs<EMAIL_ADDRESS>wrote:

We should provide support for what the distros can compile with. There's
no sense at all in only supporting LLVM versions that are too new for
debian and missing out on getting an official package.
Centos is, however, a lost cause.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/crystal-lang/crystal/issues/8725?email_source=notifications&email_token=AAM4YSJ3EKQVWPRBLQOYEKTRBNOGZA5CNFSM4KN4GVMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK5RIZA#issuecomment-582685796,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM4YSM5LDCICQ3HWPEFWYTRBNOGZANCNFSM4KN4GVMA
.

I have a question. Why Crystal doesn't bundle own LLVM toolchain with possibilities to disable/remove, but built-in, and use system LLVM toolchain by own choice? My understating is, Crystal still needs LLVM for compilation Crystal programs.
I have a problem with Installation from Homebrew on Mac when with recent version of Crystal is huge large LLVM 10 and it breaks compilation of some gems and Ruby compilation through ruby-build. That's maybe a problem on my settings (I use all in default state).
TruffleRuby contains own built-in LLVM Toolchain based on llvm 9 in the recent version (https://github.com/oracle/truffleruby/releases). It has ~170 MB after decompression. Compressed build of TruffleRuby 20.0.0 for Mac has only 110 MB. TruffleRuby bypasses paths while a gem compilation and don't use anything system outside its own toolchain.
I guess built-in LLVM toolchain would solve problems any given distribution does or doesn't support LLVM X.X

@deepj I think that's more of a homebrew problem, you might be able to fix it by installing multiple versions of LLVM.
Bundling our own LLVM toolchain would be a lot of work, if we wanted to do more than static linking (which wouldn't help macos anyway since it doesn't support it). If it becomes a larger problem I think we'll explore it, but I'll always err on the side of doing the normal thing: using the system libraries.

@RX14 What I know Sulong team patches their LLVM toolchain minimally. They uses regular LLVM releases and just apply these patches into that.
https://github.com/oracle/graal/tree/master/sulong/patches
https://github.com/oracle/graal/blob/master/sulong/docs/TOOLCHAIN.md#graalvm-deployment
In TruffleRuby there are some issues with static linking rather then with dynamic linking currently. So I guess that would not be a problem.

@deepj the targz and pkg packages for darwin in github releases have a built-in llvm 6.0.1. As long as you compile crystal programs, but not the compiler, it should be enough.
brew formula requires linking against llvm formula.
Eventually we will build another llvm package to bump from 6.0.1 to whatever recent release of llvm is present at that time.

CentOS 6 is supported until 2020-11-30 .
I suggest at this date, or even sooner (as people wish), to drop support anything below LLVM7, as @ysbaddaden said, and bump the CI accordingly (and the brew package too apparently).

Debian 7 Jessie support ends in June 30, 2020
Debian 8 Stretch has LLVM 7
Ubuntu 16.04 has LLVM8 with the in updates repositories
CentOS 7 has LLVM 7

I suppose, supporting the most recent LLVM versions available on the oldest supported CentOS, Debian, Ubuntu at the minimum is the policy? (if yes, can it be written somewhere?)

As @rdp mentioned in #11403, the oldest LLVM versions are actually not supported anymore. Since nobody reported that yet, I think it's safe to drop them.
llvm_ext fails to build with LLVM 3.8, probably since #9562 (can't find llvm/Support/CodeGenCWrappers.h).
Linking the compiler with LLVM 6.0.1 fails with a lot of undefined references. I didn't dig into it.
LLVM 7.0.0 still works.
https://github.com/crystal-lang/crystal/pull/11343 adds a CI job to test with the latest LLVM release (13.0.0). We should add a similar one for the oldest one. We could consider adding test for all supported versions, but that would definitely only need to run for maintenance release workflows.

If there is a CI matrix for the different supported LLVM versions it would also be a good chance to run the rests in spec/llvm-ir.

Thank you!
On Thursday, January 19, 2023, Johannes Müller @.***>
wrote:

Closed #8725 as completed via #12906.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.<
https://ci3.googleusercontent.com/proxy/-P9T2UC73kDQNBN1mqy-OlduJ8UK8n7j0OieiZ1Kb3rh7OS9sNz_4S3b2SBwzdoHoyS2nAMLg27P9bITWGUyGOS7SgPz0A1w9lt2PF_1tUhegTcXSD-qLah9O3yG0AUKCnQlL2St_gImNh7G_l4j9KlBJwVnaOvGnLohefFu3RtIm66qKt0HBaVdGFoDQUgdNgchcyHONf1gQFAkgSiC2sB8QENrFD5cXDRUuIA1W1Iaoyh-qexbXNmsB99iTEAxSYT957M=s0-d-e1-ft#https://github.com/notifications/beacon/AAADBUFRDUP5FM3QXD67GJLWTEU6NA5CNFSM4KN4GVMKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGPAAAAAAPPMS65G.gif>Message
ID: @.***>