Add full example for beginers

Warning included for using for also publishing as it runs on both pull requests and pushes. Wasn't sure what was the best way to express that they need to not just use it verbatim if they are also going to be publishing using the same workflow

Added where to put the file for beginners

This is definitely nice for beginners, but I think it makes it worse for people who are already comfortable with GitHub Actions because it's more verbose. GitHub Actions usually tend to start by showing the smallest code to run them, then expand into an end-to-end example. For example, consider: https://github.com/actions/setup-python
It's also a bit dangerous because it presents an example workflow that is configured to break on breaking changes, and then runs it on every PR. Many people's workloads are not aligned with this approach, and the example will break for them and be quite frustrating.
I think the basic idea here is sound, and just requires another half hour or hour of polishing work:

looking at how other GitHub Actions in the ecosystem are documented
writing a basic workflow that does cargo publish and perhaps is triggered on pushed version number tags
placing that workflow in a new section such that the explanation feels natural and neither overly verbose nor too brisk

Ok makes sense, I only push to main when I'm going to release hence that's why it works for me. I haven't found a simple workflow that does cargo publish yet that I can use as an example. I will have to look into triggering on version number tags as well. I also agree about putting it in a new section (I was on the fence about the placement). However, it don't think it's just an hour of work left because of the amount I need to go search for and test. I propose to close this PR for now and reopen once I understand github actions a bit more and have a good example to pattern on. Let me know what you think.

Sounds good to me 👍
On Fri, Nov 10, 2023, 3:05 AM One @.***> wrote:

Ok makes sense, I only push to main when I'm going to release hence that's
why it works for me. I haven't found a simple workflow that does cargo
publish yet that I can use as an example. I will have to look into
triggering on version number tags as well. I also agree about putting it in
a new section (I was on the fence about the placement). However, it don't
think it's just an hour of work left because of the amount I need to go
search for and test. I propose to close this PR for now and reopen once I
understand github actions a bit more and have a good example to pattern on.
Let me know what you think.
—
Reply to this email directly, view it on GitHub
https://github.com/obi1kenobi/cargo-semver-checks-action/pull/59#issuecomment-1805266912,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR5MSV6BA2Z6MJC4ZMOHG3YDXN5ZAVCNFSM6AAAAAA7FI6EGGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBVGI3DMOJRGI
.
You are receiving this because you commented.Message ID:
@.***>

Ok cool will reopen after I get a better understanding of publishing crates from actions


Change type dialog should accept colons in type signatures

From the types view you can create a type name containing colons. The change type popup (hitting Y on a function) will not accept any type names with ':' in them.
This especially becomes problematic when PDB's apply type names containing colons, because it prevents any modification from the UI of the type name.
Possibly related to #788?

Hmm I just tried this and it worked just fine. Could it be that you were trying to change a c++ operator overload? like foo::operator< in this case its actually the < that is the problem

It is very possible I have screwed something up.
Created a new struct:

Tried to add it to a function as a type, it fails:

Change the struct type name to X__Y, it works:

I don't think it's just colons either -- applying a PDB to a toy Windwos binary I compiled gave me the signature int64_t  j_sub_140010190(class C* arg1), and in this case 'class' is invalid if I make any edits:
Hitting 'Y' shows it as fine:

Add and remove whitespace though and it starts to error, without any change in content:


How to add Attachment to Test Steps?

I would like to add attachments to some of the steps of my Test Cases like I can do in the Web Interface.
This is how I want my step to look like:

... and when you run it, that would look like this:

However, I have not been able to find where this information is stored.
This is the JSON data for the WorkItem of my Test Case

{
id: 224,
rev: 2,
fields: {
    System.AreaPath: "GM_sandbox\GM-Toto",
    System.TeamProject: "GM_sandbox",
    System.IterationPath: "GM_sandbox",
    System.WorkItemType: "Test Case",
    System.State: "Design",
    System.Reason: "New",
    System.AssignedTo: "Jeff",
    System.CreatedDate: "2019-01-03T01:43:09.743Z",
    System.CreatedBy: "Jeff",
    System.ChangedDate: "2019-01-03T02:12:07.15Z",
    System.ChangedBy: "Jeff",
    System.Title: "Titi",
    Microsoft.VSTS.Common.StateChangeDate: "2019-01-03T01:43:09.743Z",
    Microsoft.VSTS.Common.ActivatedDate: "2019-01-03T01:43:09.743Z",
    Microsoft.VSTS.Common.ActivatedBy: "Jeff",
    Microsoft.VSTS.Common.Priority: 2,
    Microsoft.VSTS.TCM.AutomationStatus: "Not Automated",
    Microsoft.VSTS.TCM.Steps: "<steps id="0" last="2"><step id="2" type="ValidateStep"><parameterizedString isformatted="true">

Click on the rainbow button

</parameterizedString><parameterizedString isformatted="true">
Screen becomes Blue (see picture)
</parameterizedString><description/></step></steps>"
},
_links: {
    self: {
        href: "https://my_server.com:8443/tfs/PRODUCT/23d89bd4-8547-4be3-aa73-13a30866f176/_apis/wit/workItems/224"
    },
    workItemUpdates: {
        href: "https://my_server.com:8443/tfs/PRODUCT/_apis/wit/workItems/224/updates"
    },
    workItemRevisions: {
        href: "https://my_server.com:8443/tfs/PRODUCT/_apis/wit/workItems/224/revisions"
    },
    workItemHistory: {
        href: "https://my_server.com:8443/tfs/PRODUCT/_apis/wit/workItems/224/history"
    },
    html: {
        href: "https://my_server.com:8443/tfs/PRODUCTi.aspx?pcguid=4107d6a2-eaaa-40b9-9a8d-f8fdbb31d4b7&id=224"
    },
    workItemType: {
        href: "https://my_server.com:8443/tfs/PRODUCT/23d89bd4-8547-4be3-aa73-13a30866f176/_apis/wit/workItemTypes/Test%20Case"
    },
    fields: {
        href: "https://my_server.com:8443/tfs/PRODUCT/23d89bd4-8547-4be3-aa73-13a30866f176/_apis/wit/fields"
    }
},
url: "https://my_server.com:8443/tfs/PRODUCT/23d89bd4-8547-4be3-aa73-13a30866f176/_apis/wit/workItems/224"
}

Any idea on where this information is stored?
And, if possible, could anyone tell me how to add an attachment from a file and link it to the test step?
Thanks a lot

Seleha from the TCM team has provided us with this helpful information:

This will be a two step process

The first step is to add an attachment to the test case work item.
This can be done using this API - https://docs.microsoft.com/en-us/rest/api/azure/devops/wit/attachments/create?view=azure-devops-rest-5.0
To attach the uploaded attachment to the test step, you can use this API sample - https://docs.microsoft.com/en-us/rest/api/azure/devops/wit/work items/update?view=azure-devops-rest-5.0#add_an_attachment with comment as [TestStep=] and URL as obtained from the previous API.
If however you are open to using C# or JS clients, this step is simplified. The samples can be found here - https://blogs.msdn.microsoft.com/devops/2016/11/02/how-to-use-test-step-using-rest-client-helper/

Regards
Saleha

In the python code the methods for step 1 and 2 can be found here:

WorkItemTrackingClient create_attachment
WorkItemTrackingClient update_work_item

I hope this helps,
Ted

The example method seems to be working for me, except I get the error JsonPatchOperation is not defined. Is there a library or extension I need to use for it?


IllegalArgumentException calling updateFirst

When calling the updateFirst method that takes a query and an entity (~line 865 in DatastoreImpl), I (always?) receive an IllegalArgumentException if the entity in question is versioned.  The exception I get is:
java.lang.IllegalArgumentException: Invalid BSON field name $inc
	at org.bson.AbstractBsonWriter.writeName(AbstractBsonWriter.java:516)
	at com.mongodb.DBObjectCodec.encode(DBObjectCodec.java:129)
	at com.mongodb.DBObjectCodec.encode(DBObjectCodec.java:61)
	...
	at com.mongodb.Mongo.execute(Mongo.java:845)
	at com.mongodb.Mongo$2.execute(Mongo.java:828)
	at com.mongodb.DBCollection.executeWriteOperation(DBCollection.java:342)
	at com.mongodb.DBCollection.update(DBCollection.java:567)
	at org.mongodb.morphia.DatastoreImpl.update(DatastoreImpl.java:1552)
	at org.mongodb.morphia.DatastoreImpl.update(DatastoreImpl.java:1507)
	at org.mongodb.morphia.DatastoreImpl.updateFirst(DatastoreImpl.java:869)

This appears to be because the org.mongodb.morphia.DatastoreImpl#update(org.mongodb.morphia.query.Query<T>, com.mongodb.DBObject, org.mongodb.morphia.UpdateOptions, boolean) method assumes that the input is an update operations document and not a replacement.

My concern about #1101 is that it changes the intent of the operation. By putting everything in a $set, it doesn't actually do a replace on the update.  Because the incoming DB object may not have all fields (since null ones might be absent, say), it will leave fields that aren't in the DBObject in place, only setting new ones.  I think that would make it (for instance) impossible to set a field to null using updateFirst.

I did some testing prior to this.  It only ever updated the field listed in the update object.  Any existing fields in the document that weren't in the update document were unchanged.

My understanding is that when I call updateFirst() with an entity, it should issue an update as if I had done: db.Versioned.update({foo: "bar"}, {foo: "bar", baz: "qux"}), not db.Versioned.update({foo: "bar"}, {$set: {foo: "bar", baz: "qux"}}), because the intent and the results of the two operations is different.  If I'd wanted "$set", I would have used one of the updateFirst operations that takes an UpdateOperations instance.
Because $set only updates fields that are included, fields won't get nulled, even though I intend them to.  If you change the test to:
    @Test
    public void testEntityUpdateWithoutUpdateOps() {
        final Datastore datastore = getDs();

        Versioned original = new Versioned();
        original.setName("Value 1");
        original.setCount(42);
        getDs().save(original);

        Versioned found = datastore.find(Versioned.class).field("name").equal("Value 1").get();
        assertEquals("Value 1", found.getName());
        assertEquals(1L, found.getVersion().longValue());

        Versioned update = new Versioned();
        update.setName("Value 2");
        update.setCount(9);

        datastore.updateFirst(
            datastore.find(Versioned.class).field("name").equal("Value 1"),
            update,
            true
        );

        Versioned found2 = datastore.find(Versioned.class).field("name").equal("Value 2").get();
        assertNotNull(found2);
        assertEquals(2L, found2.getVersion().longValue());
        assertEquals(9, found2.getCount().intValue());

        try {
            getDs().save(original);
            fail("Should get a ConcurrentModificationException");
        } catch (ConcurrentModificationException ignored) {
        }

        Versioned update2 = new Versioned();
        update2.setName("Value 3");

        assertFalse(getMorphia().getMapper().toDBObject(update2).containsField("count"));

        datastore.updateFirst(
            datastore.find(Versioned.class).field("name").equal("Value 2"),
            update2,
            false
        );

        Versioned found3 = datastore.find(Versioned.class).field("name").equal("Value 3").get();
        assertNotNull(found3);
        assertEquals(3L, found3.getVersion().longValue());
        assertNull(found3.getCount());
    }

You will see that the field doesn't get nulled in the DB.
I see your concern with the initial pull request not updating the version; I'm not sure how to reconcile the two.  Maybe the updateFirst that accepts the entity should add a version check to the query, just as the save() calls do?  But I'm concerned that changing it to a $set produces the unintended consequence of leaving values in the DB that I didn't expect to be there.

hrm.  you're right.  i apparently fat fingered my initial test...  I'm not convinced we can reconcile updateFirst and versioning, then.  At least not atomically.  One option is to query first to get that "first" document, then run the update with the ID and version info from that document.  Not entirely atomic but i'm not sure it matters functionally speaking.

Yeah.  I'm not sure what the solution is.  I'd hate to loose atomicity; that's part of why we use the call.  We could do a "best attempt" at setting the version like in my PR, but it does leave the possibility that you would re-use the version or overwrite an object that had been previously updated.  Maybe it's just not possible and an updateFirst with a full entity shouldn't include versioning like that?  That is, in my PR, the "isReplace" option would just turn off the version incrementing.
(A side note, I was wondering if there should be a way to turn the update-verison-change off via QueryOptions).

Another option might be to do what I have in that PR but add $unset for every other field in the entity.  A little brute force but would clear out the other values.

So long as it had the intended effect, I think that would work for me.

We kicked around this option among others and found no palatable solution.  This particular approach would leave any unmapped fields in the document which is not functionally equivalent.  Other solutions involve rolling back the version number or having to manually set it which violates the morphia-managed aspect of that field.  As such for now, we're opting to merely throw an UnsupportedOperationException when updateFirst() is called with a versioned entity.  There doesn't appear to be a reasonable resolution of these two features so for now, we'll just disallow it.


[biomed nl] multi entity fulfill

NL changes for fulfilling multiple entities
frontend changes in: https://github.com/datacommonsorg/website/pull/4070

thanks for the review!


Property cannot be accessed on possibly undefined value when access to object's key of map

When I access to object's key of map, the error that is Property cannot be accessed on possibly undefined value has occurred, even checked the map has key.
example code.
https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVBjOA7AzgFzAFsAuMAWQEMAHAHgICcBLbAcwBowBvAawFMAnmUYtWAXwB8YALxhsfJFWoAKANqowYdZs0BySrvYadXMPyFhdAN0owArnwCCusGOMBdI5u07dAI0NjTVNzMmtbBwAhFzdNT1R3AEoAbnQmKDBlIgA6AAtKXGV9XUTE7mMsPEIbGABGYXxmNhlibNY+fCKDROzzVLdMHAIwGoBmBqbWFpz8wuKygH5W9s753sEwMN1UoA
Do you have any solutions to resolve this errors?

Flow doesn't count Map#has() as an actual predicate. Here's the workaround:
const a = m.get('a')
if (a) {
  const val1: string = a.key;
}

I see. Thanks!
But val1's scope is in the if block by your code.
And here's not smart.
const a = m.get('a')
let val1: string = '';
if (a) {
  val1 = a.key;
}

This is a tough one...

You can use a ternary:
const a = m.get(‘a’)
const val1 = a ? a.key : ‘’

Surely!! Thanks ;)


Create liv-coll.txt

https://www.liv-coll.ac.uk
https://www.liv-coll.ac.uk/courses/computing-bsc-top-up-degree/

@daledavies Pull request merged. Thank you!


Add OpenWhisk support

(brought over from old repo)

Add new "cloud functions" plugin to list of pre-installs

Added, but not currently used nor referenced.  Future create enhancements will likely use this plugin.


0 4 5 eliminate sys exits in client py

Hi Anton,
I am using pygnmi as modul in an python umbrella testing suite ....
I run in some issues with Cisco(most likely a Cisco issue), resulting in grpc exceptions, resulting in sys.exits in the client.py.
As I cannot cover sys.exits in the python umbrella testing suite, can we please change the sys.exits in client.py to raise Exceptions ...
Greetings from Berlin
Stefan

Hey @slieberth ,
Thanks a lot for the modification, they looks good. I noticed you created a new class for the non-blocking interator. May I ask you to create some example how that works so that we can update our documentation, please?
Thanks,
Anton


FIX: SUPPORT NON-COMMUTATIVE OPERATION

fix bug of supporting non-commutative operation through algorithm selecting.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


parent tag not working for params in state

http://plnkr.co/U8rrmORZiS7xyLBM5wtp
In my plnkr, the "home",  "element" and "detail" are parallel states, and I build parent-child relationship use parent tag. The requirement is the URL shouldn't show any id, so I send the id by params: {idElement: null}.
But the parent tag seems not work in this case. When I go to detail, I lose params in parent state.

ui-sref style dynamic links seem to be broken currently, not sure if there is anything in the works to fix them...
I came up with a workaround where I default state params using the $stateParams service.
I forked your plunker to demonstrate the fix:
http://plnkr.co/edit/8yQlDN8suimQAn0DWmuF?p=preview

@mateatslc  Not working on page refresh.


Day238

Resolves #489 .

Pull Request Test Coverage Report for Build 909

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 916:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls

Pull Request Test Coverage Report for Build 918

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 916:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


is phantomjs downoader supported？

is there any demo scripts of crawing ajax site with "javascript:click_to_next_page()"

sorry, for now you have to parse javascript by hand


Run Prettier in CI

This PR:

Adds Prettier to lint script so it's enforced in CI
Commits prettified files
Bumps Prettier to latest

https://github.com/neondatabase/neonctl/blob/dc891c365b118d0b02d9f8de5c64801196859792/package.json#L95-L100
yeah it's already there, maybe I can extend it to more extensions, is that what you meant?


Promise v3

Resolves: #143

I see that the failing checks on PHP 7.1 are caused by PHPStan requiring PHP 7.2. It's coming up on four years since PHP 7.1 EOL, maybe it's time to drop it?

I see that the failing checks on PHP 7.1 are caused by PHPStan requiring PHP 7.2. It's coming up on four years since PHP 7.1 EOL, maybe it's time to drop it?

In short yes, the bigger question is more do we want v3 in the 0.5 range or take it into 0.6, drop up to 8.1, and a whole bunch of changes? Having the same question in https://github.com/WyriHaximus/reactphp-throw-unhandled-rejected-promises mainly putting it at 7.1 for this package, but if we would raise it I would put 1.0.0 out with 7.1 and 1.1.0 right after with lets say 8.1

it will be great to finish this. bunny is only package in my project which is holding me back with old promise package :/

it will be great to finish this. bunny is only package in my project which is holding me back with old promise package :/

While I agree, it is complicated. V3 handles unhandled rejections differently and I want to make sure that is taken care of well before merging and releasing this.

Any idea as to when this could be finished, please?

Closed via #147, wasn't about to get this to work in 0.5, so went v3 only for 0.6 instead. Essentially #147 is the result of starting to do some internal updates 😅 .


[ca] Propagate issuer info from TLS certificates to SecurityConfig

The issuer info will allow us to determine if a TLS certificate needs rotation (because it is signed by the wrong issuer during a root rotation - if it is signed by a cert with the same subject + public key as our desired signing cert, it doesn't need to rotate its certificates).
This information will be generated from:

RootCA.IssueAndSaveNewCertificates
RootCA.RequestAndSaveNewCertificates
Loading TLS certs from disk.

As part of this change, I've also updated SecurityConfig to accept this info plus the TLS certificate in order to update credentials, as opposed to accepting a new ClientTLSCreds object and ServerTLSCreds object.
This means that creation of the mutable TLS credentials can be centralized to just within SecurityConfig, and that the issuer information is accessible from a SecurityConfig and can be updated on every TLS certificate update.
These are cherry-picked from #2077.

^ Not sure what's with codecov, but https://codecov.io/github/docker/swarmkit shows master at around 54.2%, not 57.67%.

LGTM


Regen operator/placement proto and update the code accordingly

Description
Regen operator/placement proto and update the code accordingly

Next PR: regen runtime proto.

Issue reference
#1464
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test


feat(ContentBlockHeadlines): add ContentBlockHeadlines pattern

Related Ticket(s)
#3007
Description
Adds new ContentBlockHeadlines pattern
Changelog
New

ContentBlockHeadlines pattern
ContentBlockHeadlines styles, story, and documentation

@kennylam 3 small changes:

The end of section horizontal rule should span the full 12 columns not just the 8 columns like the in section rules above

Top of section padding on Medium breakpoint should be 32px. Is currently showing 64px:

On small breakpoint the spacing at the top of each item should remain 16px (same as all other breakpoints). It is currently increasing to 24px:


Description y Screenshots translate to spanish

The screenshots use the files: editor and svg, that I don't know where to find them.

Thank you for the PR. I'll add them to the MAS when I release CotEditor 4.6.0 this autumn. Please let me keep open this PR until then for my reminder.

The screenshots use the files: editor and svg, that I don't know where to find them.

Don't worry, I'll make them.


Cassandra metadata extractor connector move to a separate repository?

Should this connector be part of the core repository?
As I investigate #1087, this connector is revealing a dependency on the datastax driver, which itself places an upper-bound on the reactive elements that would otherwise be included for a migration to WebClient (from RestTemplate).  The datastax driver places an upper bound on org.reactivestreams::reactive-streams at version 1.0.2, while the latter releases of io.projectreactor::reactor-core (3.3.x and now 3.4.x) depend on version 1.0.3 -- and the Spring release we're using (5.3.x) depends on version 3.4.x of reactor-core, placing a dependency on version 1.0.3 of reactive-streams...
I vaguely recall discussing that such a connector may better be placed in its own repository (like other connectors) -- was that captured already somewhere, or should we do that through this issue?  (Or am I mis-remembering such a discussion?)

Here's the build issue:
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-versions) @ cassandra-metadata-extractor-connector ---
[WARNING] Rule 5: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps failed with message:
Failed while enforcing RequireUpperBoundDeps. The error(s) are [
Require upper bound dependencies error for org.reactivestreams:reactive-streams:1.0.2 paths to dependency are:
+-org.odpi.egeria:cassandra-metadata-extractor-connector:2.5-SNAPSHOT
  +-com.datastax.oss:java-driver-core:4.9.0
    +-org.reactivestreams:reactive-streams:1.0.2
and
+-org.odpi.egeria:cassandra-metadata-extractor-connector:2.5-SNAPSHOT
  +-org.odpi.egeria:data-platform-client:2.5-SNAPSHOT
    +-org.odpi.egeria:ffdc-services:2.5-SNAPSHOT
      +-org.odpi.egeria:spring-rest-client-connector:2.5-SNAPSHOT
        +-io.projectreactor:reactor-core:3.4.0
          +-org.reactivestreams:reactive-streams:1.0.3

It's interesting that this appears to result in only a warning - I would have expected it to be worse.
I think that we definitely need to do more to decouple such build dependencies, whether or not we choose to move connectors (or other elements of ecosystem) to other repositories. My current understanding is that we are moving them to other repositories.

Agreed - these are two distinct issues. Firstly ensuring the code can be decoupled at runtime so we remove these hard dependencies, and avoid bringing unnecessary code into the runtime (as well as allow third party code such as connectors to be added), as well as making the development/test/distributino/focus process earlier by moving to a seperate repo.
Cassandra is something I would move to an external repo - though which one....  perhaps worth a team discussion on the focus group call?  Also note we need to get the dynamic loading sorted first
We should also bear in mind that although we would no longer get an error if moved to a seperate repo, the issue still exists as there could be multiple versions of the library in the classpath -- this is why within egeria we do that enforcement. Without any other changes I am unsure which version would be picked up.
Shading(ie renaming classes) is the traditional way to avoid this, but we probably need to look at this in more depth. I believe we have a slot at the next monthly meeting to discuss this?
Graham - I think we fail on warnings in this step, as per your expectation

Also to add, we have a gradle build in parallel where the dependency resolution is slightly different -- gradle's default behaviour is better (it always aims for the latest, compatible versions) though we currently have less additional checks.
Aso worth adding that even within a repo we can override the repo-wide policy from the top level pom,  so moving to a new repo isn't a prereq (despite the fact I think it's sensible in this case.. for other reasons).. but the check makes us stop and think about what we really want, and what the behaviour should be.

Who owns this connector now? @mstrelchuk  ?

It appears as if the cassandra metadata extractor is no longer in the source tree.
However there are still a few remaining references to cleanup
All are minor/low impact...

a redundant entry remains in the top level pom.xml for the dependencyManagement, which should be removed
THIRD_PARTY.md contains the license info
We could remove the commented content in DataStoreConnectorsArchiveBuilder.java for clarity, along with the related build.gradle script in open-connector-archives

I notice we still have a reference to disabling the metrics for spring+cassandra, which I think could go, unless it's needed when janusgraph is configured to use cassandra in the graph repo. To be checked?


Redirect Loop

Hi,
following problem:
My htaccess generates a redirect-loop.
On my local system there is no problem, but on a web-server (1und.de) i get the redirect loop.
I have the typical structure:
public-directory with .htaccess and index.php.
index.php includes the silex-application (../src/app.php)
This is my .htaccess:
<IfModule mod_rewrite.c>
    Options -MultiViews

    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [QSA,L]
</IfModule>

I have to define the RewriteBase, otherwise it will not work.
Can anyone help?

what is the redirect loop you are getting?
Have you checked the web server to make sure there isn't any other configurations that could be affecting your site?

I've been running silex on apache and nginx and have never experienced a redirect loop.

In my case, if i do this:
src/controller.php
$app->mount("/v1/tests", new Test/TestProviderController());

then call src/Test/TestProviderController,
$controllers = $app['controllers_factory'];
$controllers->get("/", "Bundle\\Test\\TestController::get");

and call src/Test/TestController.php
class TestController
{
    public function get(Request $request, Application $app)
    {
        return new JsonResponse(['test' => 'OK']);
    }
}

and make a curl request:
$ curl -v http://host:port/tests

I receive this response:
<!DOCTYPE html>

        <meta charset="UTF-8" />
        <meta http-equiv="refresh" content="1;url=/tests/" />

        <title>Redirecting to /tests/</title>

        Redirecting to /tests/.

but with extra bar at the end of url and request again:
$ curl -v http://host:port/tests/

I receive correct response:
*   Trying <IP_ADDRESS>...
* Connected to php-docker.local (<IP_ADDRESS>) port 8080 (#0)
> GET /v1/stocks/ HTTP/1.1
> Host: php-docker.local:8080
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx/1.11.1
< Content-Type: application/json
< Transfer-Encoding: chunked
< Connection: keep-alive
< X-Powered-By: PHP/7.0.8
< Cache-Control: no-cache
< Date: Sat, 16 Jul 2016 19:15:30 GMT
<

Is this on request the root of domain only? Maybe the RewriteBase / is in the way, since Silex might redirect to a path not having a trailing '/' when you've mounted a service/controller on it,

Closing as there is no feedback.


who is this

https://github.com/Abu2rkyi
Why are they in my account

Thanks for creating this issue. We think this issue is unactionable or unrelated to the goals of this project. Please follow our issue reporting guidelines.
Happy Coding!


header_to_metadata: support coping metadata to header

For the 2nd point in https://github.com/envoyproxy/envoy/issues/7771
@lizan @kyessenov @rgs1 @zuercher @mattklein123 @htuch
Before working on the actual code change, I would like to get agreements on the API for this. PTAL and let me know what do you think, thank you.

Option 1
The commit adds a new standalone metadata_to_header filter

Pros

Cleaner, we don't need to deprecate any thing in the header_to_metadata filter.

Cons

Duplicate the current filter API and implementation.

Option 2
The commit incrementally change the header_to_metadata API by deprecating the old fields.

Pros

Reuse the current filter API and implementation
More powerful as we can support the case for header-to-header and metadata-to-metadata, but not sure if this will be useful.

Cons

Need to deprecate the current header_to_metadata API.

Other options
Please let me know if you have suggestions for other options, thank you.

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description:
Risk Level: Low
Testing: N/A (will add after API approved)
Docs Changes: N/A (will add after API approved)
Release Notes: N/A (will add after API approved)
[Optional Fixes #Issue]
[Optional Deprecated:]

Thanks for this contribution. I have a few thoughts:

How come we are still using dynamic metadata? It was my understanding that the typed filter state was the direction we want to take filter state sharing. It seems a solution to what you want to do that takes us towards that is preferable.

However you structure the filters, the API can share messages, we do't need to repeat the value encoding fields etc.

I think it's reasonable to structure as two distinct filters, these are complementary.

@htuch, regarding 1: for a dynamic script support, untyped metadata is beneficial. Think about how we would obtain a shared filter value from a Lua script. It would be hard to do that without having to write a filter-specific accessor for the filter state. If a filter object could provide a generic traversal method, that would make it usable, but right now it appears to be a an opaque C++ type without any interface.

How come we are still using dynamic metadata? It was my understanding that the typed filter state was the direction we want to take filter state sharing. It seems a solution to what you want to do that takes us towards that is preferable.

I don't think we had consensus with moving toward C++ typed filter state, instead we documented clearly which are known dynamic metadata from in-tree filter. The flexibility of dynamic metadata is inevitable for filters like RBAC and ext_authz.

@htuch @lizan Could we mandate the use of protobuf messages as filter objects? There is a generic reflection-based accessor for protobuf objects. Struct has a very annoying issue with inability to represent ints as ints.

@htuch
Regarding 1: In addition to Lizan and Kuat's comments, the other thing is I'm following the current convention in the header-to-metadata filter, it seems more natural to have the counterpart as metadata-to-header instead of filter_state-to-header.
Regarding 2: We could share some of the common APIs but I'm not sure if it worth the extra work for sharing only some simple messages and enums. It requires change in both Envoy and control plane.
Regarding 3: I'm slightly leaning to option 2 (incrementally change the current filter) as it seems cleaner and more flexible. But I'm okay with either way. @lizan @rgs1 @zuercher @mattklein123 @kyessenov Any thoughts on this? I really appreciate if we can get this decided soon so I can update the PR with the actual code change, thank you.

@htuch @lizan Could we mandate the use of protobuf messages as filter objects? There is a generic reflection-based accessor for protobuf objects. Struct has a very annoying issue with inability to represent ints as ints.

Do we now have a generic enough reflection-based accessor for protobuf? IIRC when we had the discussion last time, the one in OSS isn't enough to handle repeated fields etc.

I don't recall this discussion in the past, but I've run into some reflection limitations before. There is a dirty-but-working hack in CEL around accessing maps.

Yeah, so let's continue the filter state discussion in https://github.com/envoyproxy/envoy/issues/4929. For this PR, let's unblock as it's the inverse of an existing filter that is already relying on dynamic metadata anyway.
I'd still advocate sharing common messages between filters. You should not have to make any breaking changes, just reference the existing messages.

Quick update: based on the feedback, I will go with Option 1 and update the PR soon. Thanks!


Chrome Browser  Uncaught TypeError: undefined is not a function

I'm getting (intermediate value)(...) is not a function in Chrome myself. Either way doesn't seem to work…


feat: configurable keyboard shortcuts

includes large refactor of event system

TODOs:
Fix failing tests - note github actions failing too
Decide on an action parameter (e.g down(5))
Decide if actions should be an array
Deduplicate keycommand and keybind modules
Broaden implementation of Scrollable
Allow merging of default and non-default config.

Before merging - fix issue with modal / dominant keybinds - not activating, and hack to activate resulted in loss of list keybinds.


Prepare GMock support for Noetic.

This follows Cartographer installing libgmock-dev.
Signed-off-by: Wolfgang Hess<EMAIL_ADDRESS>

FYI @MichaelGrupp

This is for #1494. It does:

Install libgmock-dev to use for GMock.
Saving GMOCK_LIBRARIES before it gets overwritten.
Explicitly add GMock and the GTest main to each test. Not strictly necessary right now, but good for a potential future where we do not have to rely on Cartographer's approach to find GTest and GMock anymore.

Thanks


oPack bulk check and update

Be able to bulk check the versions of all installed opacks and update them.

There is an old 'opack update -all' option that bulks checks and updates in one go.


refactor(table): make it easier to translate the empty state labels

Summary

fixes to the props to the empty state labels

:tada: This PR is included in version 1.31.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.31.3 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


Fix docs about default name for route handlers in HandlerIndex

PR Checklist

[x] Have you followed the guidelines in CONTRIBUTING.md?
[ ] Have you got 100% test coverage on new code?
[x] Have you updated the prose documentation?
[ ] Have you updated the reference documentation?

This PR updates docs about default name for route handlers.
Also noticed that test for default handler name is a bit inconsistent trying to use handler.name first. I highly doubt that there will be some changes affecting name property but anyway lets keep tests straightforward

@all-contributors add @jtraub docs


Error with ADFSLoginAction function

I am getting the a stale element reference when I try to use the ADFSLoginAction with the code that is currently present (it is commented out in the code). Everything seems to work (the initial login page loads, code enters the username, waits for page to reload to redirected login page, enters the password and then clicks submit) but it gets a stale element reference error
public void ADFSLoginAction(LoginRedirectEventArgs args)
{
var d = args.Driver;
d.FindElement(By.Id("passwordInput")).SendKeys(args.Password.ToUnsecureString());
d.ClickWhenAvailable(By.Id("submitButton"), new TimeSpan(0, 0, 2));
d.WaitForPageToLoad();
}
I tried changing how I submit with a different line of code but it also failed with the same error
d.FindElement(By.Id("passwordInput")).SendKeys(Keys.Enter);
it ended up working if I put in the submit()
d.FindElement(By.Id("passwordInput")).Submit();
Test Name:	TestOpenActiveContact
Test FullName:	Microsoft.Dynamics365.UIAutomation.Sample.OpenContact.TestOpenActiveContact
Test Source:	C:\Code\EasyRepro-master\EasyRepro-master\Microsoft.Dynamics365.UIAutomation.Sample\OpenContact.cs : line 21
Test Outcome:	Failed
Test Duration:	0:00:55.4222568
Result StackTrace:
at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary2 parameters)    at OpenQA.Selenium.Remote.RemoteWebElement.get_Location()    at Microsoft.Dynamics365.UIAutomation.Browser.InteractiveBrowser.EventDriver_ElementValueChanged(Object sender, WebElementEventArgs e) in C:\Code\EasyRepro-master\EasyRepro-master\Microsoft.Dynamics365.UIAutomation.Browser\InteractiveBrowser.cs:line 490    at OpenQA.Selenium.Support.Events.EventFiringWebDriver.OnElementValueChanged(WebElementEventArgs e)    at OpenQA.Selenium.Support.Events.EventFiringWebDriver.EventFiringWebElement.SendKeys(String text)    at Microsoft.Dynamics365.UIAutomation.Sample.OpenContact.ADFSLoginAction(LoginRedirectEventArgs args) in C:\Code\EasyRepro-master\EasyRepro-master\Microsoft.Dynamics365.UIAutomation.Sample\OpenContact.cs:line 58    at Microsoft.Dynamics365.UIAutomation.Api.LoginPage.Login(IWebDriver driver, Uri uri, SecureString username, SecureString password, Action1 redirectAction) in C:\Code\EasyRepro-master\EasyRepro-master\Microsoft.Dynamics365.UIAutomation.Api\Pages\LoginPage.cs:line 126
at Microsoft.Dynamics365.UIAutomation.Browser.DelegateBrowserCommand5.ExecuteCommand(IWebDriver driver, Object[] params) in C:\Code\EasyRepro-master\EasyRepro-master\Microsoft.Dynamics365.UIAutomation.Browser\DelegateBrowserCommand.cs:line 134    at Microsoft.Dynamics365.UIAutomation.Browser.BrowserCommand1.Execute[T1,T2,T3,T4,T5,T6,T7,T8,T9](IWebDriver driver, T1 p1, T2 p2, T3 p3, T4 p4, T5 p5, T6 p6, T7 p7, T8 p8, T9 p9) in C:\Code\EasyRepro-master\EasyRepro-master\Microsoft.Dynamics365.UIAutomation.Browser\BrowserCommand.cs:line 167
at Microsoft.Dynamics365.UIAutomation.Browser.BrowserCommand1.Execute[T1,T2,T3,T4](IWebDriver driver, T1 p1, T2 p2, T3 p3, T4 p4) in C:\Code\EasyRepro-master\EasyRepro-master\Microsoft.Dynamics365.UIAutomation.Browser\BrowserCommand.cs:line 60    at Microsoft.Dynamics365.UIAutomation.Browser.BrowserPage.Execute[TResult,T1,T2,T3,T4](String commandName, Func6 delegate, T1 p1, T2 p2, T3 p3, T4 p4) in C:\Code\EasyRepro-master\EasyRepro-master\Microsoft.Dynamics365.UIAutomation.Browser\BrowserPage.cs:line 102
at Microsoft.Dynamics365.UIAutomation.Api.LoginPage.Login(Uri uri, SecureString username, SecureString password, Action`1 redirectAction) in C:\Code\EasyRepro-master\EasyRepro-master\Microsoft.Dynamics365.UIAutomation.Api\Pages\LoginPage.cs:line 84
at Microsoft.Dynamics365.UIAutomation.Sample.OpenContact.TestOpenActiveContact() in C:\Code\EasyRepro-master\EasyRepro-master\Microsoft.Dynamics365.UIAutomation.Sample\OpenContact.cs:line 25
Result Message:
Test method Microsoft.Dynamics365.UIAutomation.Sample.OpenContact.TestOpenActiveContact threw exception:
OpenQA.Selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
(Session info: chrome=61.0.3163.100)
(Driver info: chromedriver=2.31.488763 (092de99f48a300323ecf8c2a4e2e7cab51de5ba8),platform=Windows NT 10.0.15063 x86_64)

Yea we see that quite a bit in our API's. Our wait extension methods are setup to ignore those exceptions types but it looks like we're not handling that in the Click extension methods.   I'll add that to our tasks.
Thanks for the feedback.

This issue is fixed in the latest release.  Please test with the latest build and let us know if you run into any issues.
Thanks


Is there a Region report ?

And if so, Can it be downloaded by the regionadmin ?

No, not yet.
Add a job to create 1 reports with all game per region.


fix(parser): Fix function name.

As per our conversation in PR https://github.com/livingdocsIO/editable.js/pull/222.

:tada: This PR is included in version 2.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


AMD Support

AMD and RequireJS are becoming a very popular way to manage JavaScript libraries. It would be great to see this library have AMD support.

Thank you for your suggestion. Sounds fine. I will add the AMD support soon.

colo suppurts AMD. Thanks for your suggestion.


starwaster has taken over ProceduralParts

there's a new 1.2.9 release for KSP 1.2.2

Looks good to me. Merging with thanks!


Question: Clickable links in the chat

Hi,
Could you please advise if it’s possible to make links returned by an LLM clickable? The LLM can return them in any format, such as , markdown, or any specific format that is needed. As for now none of them works.
Thank you.

They are clickable by default since they're rendered in markdown.
https://github.com/user-attachments/assets/061b5ef2-ad93-458f-ad0e-393573e28b84

Hi,
Sorry for the delay in responding. I realized that it didn't work because LLM was returning a URL with the space symbol, that's why it wasn't rendered. So, there are no generic issues here indeed, thank you.
However, I've got a new pretty specific problem :). Local links like this one [test.txt](file:///c:/temp/test.txt) don't work. They point to the localhost instead.


fix mpii .yaml bug

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: DouYishun sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Simple Java Mail Wishlist -- email.setReturnReceiptRequested

I recently became acquainted with SimpleJavaMail.    Thank you very much for making it, and sharing it with us!
On your website, you asked for suggestions for how it could be improved.  I have a few "wishlist" items for it.  I'll put them in separate tickets so you can evaluate and track them individually.

Please consider adding a method to set Return Receipt Requested information:
email.setReturnReceiptRequested(MsgFromAddress) // or other address

if (bReturnReceiptRequested) {
   msg.setHeader("Disposition-Notification-To", getMsgFrom());
}

Yes, we could set it with a custom header, but it would be nice if we didn't have to program it ourselves -- especially so people don't need to learn the intricacies of mail headers.

Agreed.
What about a custom notification reply (https://stackoverflow.com/questions/25600405/how-to-create-a-return-receipt-email-javamail)? I haven't looked into this before though.

I believe we're talking about the same thing here.  It's just a simple addition:
email.addHeader("Disposition-Notification-To", msgFromAddress;

What I get from that stackoverflow answer is that you can have a custom return-body embedded.

Create a MultipartReport object, populate it with a DispositionNotification object, the text to display to the user, and optionally the original message. Use the Message.setContent method to set the MultipartReport as the content of the new message that you send back as the read receipt notification.

I'm not sure I've ever encountered such a custom return-email. Perhaps for a follow-up feature lateron. For now we can focus on just the notification address.

I think you're right.  I don't think I've ever encountered it, either...
And I agree.  I think I'd save it for another day, and see if someone requests it.  I think spending quality time with your little one(s) would probably be a better use of your time!
Thank you again.

Release in 4.4.0. Please verify.


Do not refresh the page with the list of Wi-Fi if the list has not actually been changed, to prevent the page from scrolling

QA passed


v1.0 checklist

[ ] https://github.com/swoosh/swoosh/pull/830/files#diff-e3dca7da1dc26f78c6942e408e806dd74956ef02fe0d75ff3ce1ddd3d319f52aR27

Unsure how this will work but I created https://github.com/wojtekmach/req/issues/263 to track that.

I am not sure either! But will comment over there, thanks. Some defaults
are very nice to have always, for other it depends on the use case!
Le mar. 14 nov. 2023 à 20:35, Wojtek Mach @.***> a
écrit :

Unsure how this will work but I created #263
https://github.com/wojtekmach/req/issues/263 to track that.
—
Reply to this email directly, view it on GitHub
https://github.com/wojtekmach/req/issues/269#issuecomment-1811066222,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAACPHMMOY6BSXEN6H47AWLYEPBZRAVCNFSM6AAAAAA7I4NREOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJRGA3DMMRSGI
.
You are receiving this because you commented.Message ID:
@.***>


PZ typings

It's rather a question. Are PZ typings generated by some tool, or you've written them mannualy?

I wrote a tool that comprehensively compiles the typings in this project. It's actually the bulk of the project's time spent being developed.


Better reporting when result object fails

This PR is inspired by the following situation:
from qiskit import *
simulator = Aer.get_backend('qasm_simulator')
qc = QuantumCircuit(3)
qc.h(range(3))
# qc.measure_all()   <- There is no measure
result = execute(qc, backend=simulator).result()
counts = result.get_counts(qc)

The error raised is the following:
Traceback (most recent call last):
  File "./[redacted].py", line 7, in <module>
    counts = result.get_counts(qc)
  File "/[redacted]/qiskit-terra/qiskit/result/result.py", line 257, in get_counts
    raise QiskitError('No counts for experiment "{0}"'.format(key))
qiskit.exceptions.QiskitError: 'No counts for experiment "     ┌───┐\nq_0: ┤ H ├\n     ├───┤\nq_1: ┤ H ├\n     ├───┤\nq_2: ┤ H ├\n     └───┘"'

The error includes the text representation of the circuit, badly formated.
This PR prints the repr representation of the object:
Traceback (most recent call last):
  File "[redacted].py", line 7, in <module>
    counts = result.get_counts(qc)
  File "/[redacted]/qiskit-terra/qiskit/result/result.py", line 256, in get_counts
    raise QiskitError('No counts for experiment "{0}"'.format(repr(key)))
qiskit.exceptions.QiskitError: 'No counts for experiment "<qiskit.circuit.quantumcircuit.QuantumCircuit object at 0x118185890>"'

Additionally, this PR adds some fixes here and there. And it adds some tests.

The user might call get_counts  with an integer or with an object. I thought was better to raise error with a reference to that very same parameter.
I would be in to have a __repr__ with the name of the circuit for QuantumCircuit.


orbitDB functionality is not working

While trying to run
it throws an arguments to path.join should be a string
and the line where the actual execution stops is
95:      const controller = await Database.createInstance(this.ipfsNode);
in the connect.vue file

Actually node is not working....  I have not check yet... After checking , will try to fix


Misleading Documentation for isDeviceSupported() Method of the "local_auth" Flutter plugin

Issue:
The current documentation for the isDeviceSupported() method in the "local_auth" Flutter plugin does not accurately represent its main functionality. The documentation states, "Returns true if the device is capable of checking biometrics or is able to fail over to device credentials," which can be misleading.
Proposed Action:

Update the documentation to accurately describe the primary functionality of the isDeviceSupported() method, emphasizing its purpose in checking if a device has a user-configured system lock.

Consider renaming the method to better reflect its functionality, perhaps to something like isDeviceLockConfigured().

This adjustment will enhance the clarity and user-friendliness of the plugin's documentation, preventing potential confusion among developers.
Please feel free to correct me if I misunderstood the intended functionality of the isDeviceSupported(). Your insights are valuable in ensuring accurate and helpful documentation for the "local_auth" Flutter plugin.
Thank you for your attention to this matter.

Hi @vivekjivani, how is the documentation misleading?

hi @danagbemava-nc, Thanks for Responding, I realized it is not misleading but I didn't get it in the first shot, my request is to change the description of the method to a simpler sentence or add a more descriptive description.
Thanks.

Hi @vivekjivani, what would you propose it be updated to?

I already Proposed in Posiabble Actions in the Issue description,
Also, I wanted you to know that the documentation for flutter_webview is poor, you guys need someone who can manage the plugin documents well so people like me don't have to struggle for two days just because documentation is missing proper explanation and examples

Thanks for update.

Also, I wanted you to know that the documentation for flutter_webview is poor, you guys need someone who can manage the plugin documents well so people like me don't have to struggle for two days just because documentation is missing proper explanation and examples

Kindly file issues that describe how the documentation is not clear so that it can be improved.
Thank you

I realized it is not misleading but I didn't get it in the first shot, my request is to change the description of the method to a simpler sentence or add a more descriptive description.

It's still not clear to me what is being requested here; the proposed changes would make it longer, not simpler, and the current description is accurate as far as I'm aware (and it sounds like you agree that's the case).
Absent a specific actionable suggestion, closing.


notifications

any kind of notification that upload went well would be great.

To see if the upload is successful i usually toggle the sidebar and look at the status bar.

@erroid There is a status bar at the bottom of the remote ftp tree view. However notifications for when there are errors would be good, which I plan to get round to at some point.


Improve BitArray's constructors

Adds a block-accepting overload, similar to other containers: BitArray.new(7, &.even?) # => BitArray[1010101]
Allows non-Int32 size arguments, also similar to other containers. The size is converted within the constructor. The added Int restriction is not a breaking change because size was previously used to initialize an Int32 instance variable directly.
Raises if the size argument is negative, instead of silently returning an empty BitArray for sizes within -31..-1.

I avoided BitArray.[] because it could be interpreted in two ways, a variadic literal-like constructor (which requires changes to #inspect's format), and an integer-to-bits constructor (similar to the from_int spec helper method).

I'm not sure if the yielding overload is that useful, but it's probably good to have it for consistency.


chore: remove reference to defunct disutils-sig

The mailing list was shut down at the end of 2021.
Remove the reference from the Help page and translations.
Refs<EMAIL_ADDRESS>Signed-off-by: Mike Fiedler<EMAIL_ADDRESS>

cc @akuchling as mailing list maintainer who shut it down

Thanks!


DOC: Example for signal.cmplx_sort

Reference to: #7168

Note that the documentation should agree with the latest numpy release.
Not that whitespace matters that much, but there's an automatic check
that needs to pass, and it may not be smart enough to ignore the
whitespace here.

After updating numpy I fixed whitespaces to match current version.
AFAIK all checks passed even in previous version of this PR and hopefully they will pass in this as well.

Thanks @ziejcow


Remove pyarrow_hotfix import from __init__.py

Description

Remove pyarrow_hotfix import

Closes #1691
By Submitting this PR I confirm:

I am familiar with the Contributing Guidelines.
When the PR is ready for review, new or existing tests cover these changes.
When the PR is ready for review, the documentation is up to date with these changes.

/merge


Modules -- a more complete implementation.

Adding {Module|Parameter}{List|Dict}

I've only looked through on my phone but it all looks good. I'll mark as approved - if you'd like me to do a line by line review I could do that tomorrow or next week

I've only looked through on my phone but it all looks good. I'll mark as approved - if you'd like me to do a line by line review I could do that tomorrow or next week

No need. It's pretty straight-forward.

@NiklasGustafsson I went through the text and it is wonderful.
The only thing I had trouble with is in the first example,
public TestModule1(Tensor tensor, bool withGrad)

... where the tensor parameter is never used so I spent some time figuring out what it is doing there.
I assume it is a static parameter which becomes useful in a Sequential definition, but in this particular case it's just a distraction to the reader since it is unused. Maybe it would be a better idea to explain the tensor-as-a-module-parameter concept separately and omit it in the first example.

@pkese -- thanks for pointing that out. That argument should not be there at all. I'll remove it.


Not working for me anymore.

It isn't working for me anymore. I have several keywords in and all of a sudden they all popped back up on my YouTube page.

Do you know if you have the new layout of YouTube?
I'm currently working on a new version that fixes problems of the extension with the new layout.

I do have the new layout. I was using a different content blocker and when they moved to the new layout that one stopped working. There was the option to use the old layout and I did but they took that option away from me and I moved to your blocker. It worked with the new layout for about a month and then stopped.

I'm trying to fix this problem as we speak so I hope to fix it soon!

OK thank you.

I've pushed the new version that fixes the problems with the new layout to github. Will upload the update to the chrome extensionstore now. I'd love to hear if everything is working after this update on your end!

@Real-Rodville are there any features from your old extension that you would love to see in my version?

The one I miss from the other one was the ability to right click and add videos or channels to the block list.
Now if you want a wish list I would live to be able to filter out videos that are not in English. I am getting them in Arabic, Thai, Portuguese, and Tagalog. I am not even sure why but it would be nice to not have those.

I've added rightclick on selection of text support and support for blocking of channels. Don't have the right click on channel/video to block the channel function yet as that is a bit harder than I thought. Filtering non english video's is not something I can easily support.

Thank you.


python: spacy: wheel>=0.32.0,<0.33.0 -> wheel>=0.32.0

Motivation for this change
python37Packages.spacy depends on 0.32.0,<0.33.0, but wheel has recently been updated to 0.33.4. This change removes the <0.33.0 restriction to allow compatibility with future versions.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I force pushed an update after somehow accidentally deleting a char between testing and committing - only noticed this evening during a rebuild while looking at another package. i hope this is OK.

@jonringer Thanks for the feedback. Should I amend the commit message and simply edit the PR title? Or would it be more appropriate to close and create a new PR to correct this?

Amend.

Sorry, i thought i replied to this. Yes, you should just amend an existing PR.
Plenty of people force push changes, so that the commit history looks nice on master. :)

Thanks for the feedback guys! :)


v0.1.11 - NA remover bug fix

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/12256
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.11 -m "<description of version>" 6f8206c595ec7596b7e0ce9310e164481be5fb34
git push origin v0.1.11


Segmentation fault on Macmini7,1

I'm experiencing segfaults on Macmini7,1, which looks like the same issue as #4, running on
$ lsb_release -a
LSB Version:	n/a
Distributor ID:	ManjaroLinux
Description:	Manjaro Linux
Release:	24.0.3
Codename:	Wynsdey

Here's the relevant output:
$ macfand -n
Loading profile for model: macmini7,1
dbug: opening profile /usr/local/macfand/machines//macmini7,1.conf
Found 60 sensors:
	 1: TA0P - ???
	 2: TA0V - ???
	 3: TA0p - Ambient 2
	 4: TA1P - ???
	 5: TA1p - Ambient 1
	 6: TA2P - ???
	 7: TA2p - Ambient 3
	 8: TC0C - ???
	 9: TC0E - ???
	10: TC0F - ???
	11: TC0G - ???
	12: TC0J - ???
	13: TC0P - ???
	14: TC0c - CPU Core 1 PECI
	15: TC0p - CPU Proximity
	16: TC1C - ???
	17: TC1c - CPU Core 2 PECI
	18: TCGC - ???
	19: TCGc - Intel GPU
	20: TCPG - ???
	21: TCSC - ???
	22: TCSc - CPU System Agent Core PECI
	23: TCTD - ???
	24: TCXC - CPU Core
	25: TCXc - ???
	26: TCXr - CPU PECI DTS
	27: TH0A - ???
	28: TH0B - ???
	29: TH0C - ???
	30: TH0F - ???
	31: TH0O - ???
	32: TH0P - ???
	33: TH0R - ???
	34: TH0a - ???
	35: TH0b - ???
	36: TH0c - ???
	37: TH1A - ???
	38: TH1B - ???
	39: TH1C - ???
	40: TH1F - ???
	41: TH1O - ???
	42: TH1P - ???
	43: TH1R - ???
	44: TH1a - ???
	45: TH1b - ???
	46: TH1c - ???
	47: TM0P - ???
	48: TM0V - ???
	49: TM0p - Memory Proximity
	50: TPCD - ???
	51: TPCd - PCH Die Digital
	52: TS0V - ???
	53: TW0P - ???
	54: TW0p - Wi-Fi Proximity
	55: Te0T - ???
	56: Te0t - Thunderbolt Diode
	57: Tm0P - ???
	58: Tm0p - Logic Board
	59: Tp0C - PSU Analog
	60: Ts0G - ???
zsh: segmentation fault (core dumped)  macfand -n

And strace:
$ strace !!
strace macfand -n
execve("/usr/local/bin/macfand", ["macfand", "-n"], 0x7fff6210aeb8 /* 66 vars */) = 0
brk(NULL)                               = 0x5e8300fd7000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=134767, ...}) = 0
mmap(NULL, 134767, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7b6339ef0000
close(3)                                = 0
openat(AT_FDCWD, "/usr/lib/libconfig.so.11", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=55088, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7b6339eee000
mmap(NULL, 57360, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7b6339edf000
mmap(0x7b6339ee3000, 24576, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x4000) = 0x7b6339ee3000
mmap(0x7b6339ee9000, 12288, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xa000) = 0x7b6339ee9000
mmap(0x7b6339eec000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xc000) = 0x7b6339eec000
close(3)                                = 0
openat(AT_FDCWD, "/usr/lib/libm.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\0\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=960856, ...}) = 0
mmap(NULL, 958792, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7b6339df4000
mmap(0x7b6339e02000, 524288, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe000) = 0x7b6339e02000
mmap(0x7b6339e82000, 372736, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x8e000) = 0x7b6339e82000
mmap(0x7b6339edd000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe9000) = 0x7b6339edd000
close(3)                                = 0
openat(AT_FDCWD, "/usr/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`^\2\0\0\0\0\0"..., 832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0<EMAIL_ADDRESS>784, 64) = 784
fstat(3, {st_mode=S_IFREG|0755, st_size=1989944, ...}) = 0
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0<EMAIL_ADDRESS>784, 64) = 784
mmap(NULL, 2014064, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7b6339c08000
mmap(0x7b6339c2c000, 1490944, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x24000) = 0x7b6339c2c000
mmap(0x7b6339d98000, 319488, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x190000) = 0x7b6339d98000
mmap(0x7b6339de6000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1dd000) = 0x7b6339de6000
mmap(0x7b6339dec000, 31600, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7b6339dec000
close(3)                                = 0
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7b6339c05000
arch_prctl(ARCH_SET_FS, 0x7b6339c05740) = 0
set_tid_address(0x7b6339c05a10)         = 3437
set_robust_list(0x7b6339c05a20, 24)     = 0
rseq(0x7b6339c06060, 0x20, 0, 0x53053053) = 0
mprotect(0x7b6339de6000, 16384, PROT_READ) = 0
mprotect(0x7b6339edd000, 4096, PROT_READ) = 0
mprotect(0x7b6339eec000, 4096, PROT_READ) = 0
mprotect(0x5e82cd257000, 4096, PROT_READ) = 0
mprotect(0x7b6339f49000, 8192, PROT_READ) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0
munmap(0x7b6339ef0000, 134767)          = 0
getrandom("\x82\x84\x8e\xea\x7b\x2a\xfb\xa6", 8, GRND_NONBLOCK) = 8
brk(NULL)                               = 0x5e8300fd7000
brk(0x5e8300ff8000)                     = 0x5e8300ff8000
rt_sigaction(SIGCHLD, {sa_handler=SIG_IGN, sa_mask=[CHLD], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7b6339c44ae0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTSTP, {sa_handler=SIG_IGN, sa_mask=[TSTP], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7b6339c44ae0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTTOU, {sa_handler=SIG_IGN, sa_mask=[TTOU], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7b6339c44ae0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTTIN, {sa_handler=SIG_IGN, sa_mask=[TTIN], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7b6339c44ae0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGINT, {sa_handler=0x5e82cd2549b1, sa_mask=[INT], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7b6339c44ae0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGHUP, {sa_handler=0x5e82cd2549b1, sa_mask=[HUP], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7b6339c44ae0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
rt_sigaction(SIGTERM, {sa_handler=0x5e82cd2549b1, sa_mask=[TERM], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7b6339c44ae0}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
openat(AT_FDCWD, "/etc/macfand.conf", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=1349, ...}) = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=1349, ...}) = 0
read(3, "# macfand - Fan Control daemon f"..., 8192) = 1349
read(3, "", 4096)                       = 0
read(3, "", 8192)                       = 0
close(3)                                = 0
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0x1), ...}) = 0
write(1, "Loading profile for model: macmi"..., 38Loading profile for model: macmini7,1
) = 38
write(1, "dbug: opening profile /usr/local"..., 67dbug: opening profile /usr/local/macfand/machines//macmini7,1.conf
) = 67
openat(AT_FDCWD, "/usr/local/macfand/machines//macmini7,1.conf", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2563, ...}) = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=2563, ...}) = 0
read(3, "# macmini7,1.conf\n#\n# Machine Na"..., 8192) = 2563
read(3, "", 4096)                       = 0
read(3, "", 8192)                       = 0
close(3)                                = 0
mmap(NULL, 151552, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7b6339be0000
mmap(NULL, 208896, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7b6339bad000
openat(AT_FDCWD, "/sys/class/hwmon", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
brk(0x5e830101a000)                     = 0x5e830101a000
getdents64(3, 0x5e8300ff1dd0 /* 5 entries */, 32768) = 144
openat(AT_FDCWD, "/sys/class/hwmon/hwmon2/device/name", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/sys/class/hwmon/hwmon0/device/name", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/sys/class/hwmon/hwmon1/device/name", O_RDONLY) = 4
read(4, "applesmc", 8)                  = 8
close(4)                                = 0
readlink("/sys", 0x7ffec19ff200, 1023)  = -1 EINVAL (Invalid argument)
readlink("/sys/class", 0x7ffec19ff200, 1023) = -1 EINVAL (Invalid argument)
readlink("/sys/class/hwmon", 0x7ffec19ff200, 1023) = -1 EINVAL (Invalid argument)
readlink("/sys/class/hwmon/hwmon1", "../../devices/platform/applesmc."..., 1023) = 48
readlink("/sys/devices", 0x7ffec19ff200, 1023) = -1 EINVAL (Invalid argument)
readlink("/sys/devices/platform", 0x7ffec19ff200, 1023) = -1 EINVAL (Invalid argument)
readlink("/sys/devices/platform/applesmc.768", 0x7ffec19ff200, 1023) = -1 EINVAL (Invalid argument)
readlink("/sys/devices/platform/applesmc.768/hwmon", 0x7ffec19ff200, 1023) = -1 EINVAL (Invalid argument)
readlink("/sys/devices/platform/applesmc.768/hwmon/hwmon1", 0x7ffec19ff200, 1023) = -1 EINVAL (Invalid argument)
readlink("/sys/devices/platform/applesmc.768/hwmon/hwmon1/device", "../../../applesmc.768", 1023) = 21
readlink("/sys/devices/platform/applesmc.768", 0x7ffec19ff200, 1023) = -1 EINVAL (Invalid argument)
getdents64(3, 0x5e8300ff1dd0 /* 0 entries */, 32768) = 0
brk(0x5e8301012000)                     = 0x5e8301012000
close(3)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0
getdents64(3, 0x5e8300ff1dd0 /* 143 entries */, 32768) = 4600
getdents64(3, 0x5e8300ff1dd0 /* 0 entries */, 32768) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp1_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp2_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp3_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp4_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp5_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp6_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp7_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp8_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp9_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp10_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp11_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp12_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp13_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp14_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp15_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp16_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp17_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp18_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp19_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp20_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp21_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp22_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp23_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp24_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp25_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp26_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp27_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp28_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp29_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp30_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp31_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp32_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp33_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp34_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp35_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp36_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp37_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp38_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp39_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp40_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp41_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp42_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp43_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp44_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp45_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp46_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp47_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp48_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp49_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp50_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp51_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp52_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp53_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp54_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp55_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp56_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp57_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp58_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp59_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp60_input", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0
newfstatat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp61_input", 0x7ffec19fef40, 0) = -1 ENOENT (No such file or directory)
write(1, "Found 60 sensors:\n", 18Found 60 sensors:
)     = 18
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp1_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TA0P\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp2_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TA0V\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp3_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TA0p\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp4_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TA1P\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp5_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TA1p\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp6_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TA2P\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp7_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TA2p\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp8_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TC0C\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp9_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TC0E\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp10_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TC0F\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp11_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TC0G\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp12_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TC0J\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp13_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TC0P\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp14_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TC0c\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp15_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TC0p\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp16_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TC1C\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp17_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TC1c\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp18_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TCGC\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp19_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TCGc\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp20_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TCPG\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp21_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TCSC\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp22_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TCSc\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp23_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TCTD\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp24_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TCXC\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp25_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TCXc\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp26_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TCXr\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp27_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH0A\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp28_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH0B\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp29_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH0C\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp30_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH0F\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp31_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH0O\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp32_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH0P\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp33_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH0R\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp34_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH0a\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp35_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH0b\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp36_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH0c\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp37_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH1A\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp38_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH1B\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp39_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH1C\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp40_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH1F\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp41_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH1O\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp42_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH1P\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp43_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH1R\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp44_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH1a\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp45_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH1b\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp46_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TH1c\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp47_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TM0P\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp48_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TM0V\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp49_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TM0p\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp50_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TPCD\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp51_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TPCd\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp52_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TS0V\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp53_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TW0P\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp54_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "TW0p\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp55_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "Te0T\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp56_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "Te0t\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp57_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "Tm0P\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp58_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "Tm0p\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp59_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "Tp0C\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/sys/devices/platform/applesmc.768/temp60_label", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0
read(4, "Ts0G\n", 4096)                 = 5
read(4, "", 4096)                       = 0
close(4)                                = 0
write(1, "\t 1: TA0P - ???\n", 16	 1: TA0P - ???
)      = 16
write(1, "\t 2: TA0V - ???\n", 16	 2: TA0V - ???
)      = 16
write(1, "\t 3: TA0p - Ambient 2\n", 22	 3: TA0p - Ambient 2
) = 22
write(1, "\t 4: TA1P - ???\n", 16	 4: TA1P - ???
)      = 16
write(1, "\t 5: TA1p - Ambient 1\n", 22	 5: TA1p - Ambient 1
) = 22
write(1, "\t 6: TA2P - ???\n", 16	 6: TA2P - ???
)      = 16
write(1, "\t 7: TA2p - Ambient 3\n", 22	 7: TA2p - Ambient 3
) = 22
write(1, "\t 8: TC0C - ???\n", 16	 8: TC0C - ???
)      = 16
write(1, "\t 9: TC0E - ???\n", 16	 9: TC0E - ???
)      = 16
write(1, "\t10: TC0F - ???\n", 16	10: TC0F - ???
)      = 16
write(1, "\t11: TC0G - ???\n", 16	11: TC0G - ???
)      = 16
write(1, "\t12: TC0J - ???\n", 16	12: TC0J - ???
)      = 16
write(1, "\t13: TC0P - ???\n", 16	13: TC0P - ???
)      = 16
write(1, "\t14: TC0c - CPU Core 1 PECI\n", 28	14: TC0c - CPU Core 1 PECI
) = 28
write(1, "\t15: TC0p - CPU Proximity\n", 26	15: TC0p - CPU Proximity
) = 26
write(1, "\t16: TC1C - ???\n", 16	16: TC1C - ???
)      = 16
write(1, "\t17: TC1c - CPU Core 2 PECI\n", 28	17: TC1c - CPU Core 2 PECI
) = 28
write(1, "\t18: TCGC - ???\n", 16	18: TCGC - ???
)      = 16
write(1, "\t19: TCGc - Intel GPU\n", 22	19: TCGc - Intel GPU
) = 22
write(1, "\t20: TCPG - ???\n", 16	20: TCPG - ???
)      = 16
write(1, "\t21: TCSC - ???\n", 16	21: TCSC - ???
)      = 16
write(1, "\t22: TCSc - CPU System Agent Cor"..., 39	22: TCSc - CPU System Agent Core PECI
) = 39
write(1, "\t23: TCTD - ???\n", 16	23: TCTD - ???
)      = 16
write(1, "\t24: TCXC - CPU Core\n", 21	24: TCXC - CPU Core
) = 21
write(1, "\t25: TCXc - ???\n", 16	25: TCXc - ???
)      = 16
write(1, "\t26: TCXr - CPU PECI DTS\n", 25	26: TCXr - CPU PECI DTS
) = 25
write(1, "\t27: TH0A - ???\n", 16	27: TH0A - ???
)      = 16
write(1, "\t28: TH0B - ???\n", 16	28: TH0B - ???
)      = 16
write(1, "\t29: TH0C - ???\n", 16	29: TH0C - ???
)      = 16
write(1, "\t30: TH0F - ???\n", 16	30: TH0F - ???
)      = 16
write(1, "\t31: TH0O - ???\n", 16	31: TH0O - ???
)      = 16
write(1, "\t32: TH0P - ???\n", 16	32: TH0P - ???
)      = 16
write(1, "\t33: TH0R - ???\n", 16	33: TH0R - ???
)      = 16
write(1, "\t34: TH0a - ???\n", 16	34: TH0a - ???
)      = 16
write(1, "\t35: TH0b - ???\n", 16	35: TH0b - ???
)      = 16
write(1, "\t36: TH0c - ???\n", 16	36: TH0c - ???
)      = 16
write(1, "\t37: TH1A - ???\n", 16	37: TH1A - ???
)      = 16
write(1, "\t38: TH1B - ???\n", 16	38: TH1B - ???
)      = 16
write(1, "\t39: TH1C - ???\n", 16	39: TH1C - ???
)      = 16
write(1, "\t40: TH1F - ???\n", 16	40: TH1F - ???
)      = 16
write(1, "\t41: TH1O - ???\n", 16	41: TH1O - ???
)      = 16
write(1, "\t42: TH1P - ???\n", 16	42: TH1P - ???
)      = 16
write(1, "\t43: TH1R - ???\n", 16	43: TH1R - ???
)      = 16
write(1, "\t44: TH1a - ???\n", 16	44: TH1a - ???
)      = 16
write(1, "\t45: TH1b - ???\n", 16	45: TH1b - ???
)      = 16
write(1, "\t46: TH1c - ???\n", 16	46: TH1c - ???
)      = 16
write(1, "\t47: TM0P - ???\n", 16	47: TM0P - ???
)      = 16
write(1, "\t48: TM0V - ???\n", 16	48: TM0V - ???
)      = 16
write(1, "\t49: TM0p - Memory Proximity\n", 29	49: TM0p - Memory Proximity
) = 29
write(1, "\t50: TPCD - ???\n", 16	50: TPCD - ???
)      = 16
write(1, "\t51: TPCd - PCH Die Digital\n", 28	51: TPCd - PCH Die Digital
) = 28
write(1, "\t52: TS0V - ???\n", 16	52: TS0V - ???
)      = 16
write(1, "\t53: TW0P - ???\n", 16	53: TW0P - ???
)      = 16
write(1, "\t54: TW0p - Wi-Fi Proximity\n", 28	54: TW0p - Wi-Fi Proximity
) = 28
write(1, "\t55: Te0T - ???\n", 16	55: Te0T - ???
)      = 16
write(1, "\t56: Te0t - Thunderbolt Diode\n", 30	56: Te0t - Thunderbolt Diode
) = 30
write(1, "\t57: Tm0P - ???\n", 16	57: Tm0P - ???
)      = 16
write(1, "\t58: Tm0p - Logic Board\n", 24	58: Tm0p - Logic Board
) = 24
write(1, "\t59: Tp0C - PSU Analog\n", 23	59: Tp0C - PSU Analog
) = 23
write(1, "\t60: Ts0G - ???\n", 16	60: Ts0G - ???
)      = 16
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x1} ---
+++ killed by SIGSEGV (core dumped) +++
zsh: segmentation fault (core dumped)  strace macfand -n

Any updates? Experiencing same issue with Macmini 7,1.


Normalize doc indentation

We used to trim every doc line. This is a problem for code blocks where
the indentation is relevant (e.g. in the amp-list sample). We now
normalize docs based on the indentation of the comment tags, e.g. for:
__<--
__  text
__text
__-->
all whitespaces marked by '_' will be removed resulting in
"
text
text
"
Fixes #68

@kul3r4 PTAL


Traefik 2.10 affected by CVE-2024-45410 9.8 critical vulnerability

Kamal V1 defaults to traefik 2.10 which has a critical security vulnerability https://www.cve.org/CVERecord?id=CVE-2024-45410.
First published 2024-09-19.
2.11.9 addresses this issue.
Defaulting to 2.11 should fix this.

Fixed in Kamal 1.9.1


Planner: continue in PV mode when planner finishes

From Slack: we should think about splitting the planner target soc from the actual target, i.e. treat planner more as a minimum value.
/cc @naltatis

I get the idea, but I think we are introducing a lot of complexity where. We'll have to visualize this extra SoC limit in addition to the existing ones (min soc, target soc, vehicle limit). In addition it's not obvious to the user which soc is the limit. As an example: I use target time before longer trips. In these scenarios I want the vehicle reach a higher soc (100%) than my usual limit (80%). But you could also make the case the other way around where it's more of a minimum value as you described.
I'm not sure if it's wise to open this topic right now. I see that we have work to do here especially when we are thinking about departure schedules / recurring targets. see #5492

For the visualization you could simply insert 2 bars/slider instead of currently only one bar/slider. The first bar sets the minSOC and the second the target SOC.

I think the real point here is that we should treat the planner soc as a minsoc with timestamp rather than as a targetsoc.

As a naive user who didn't read the doc, the described behavior was actually my expectation for min+PV mode. Eventually this is also my use case, preserve a minimum SoC for daily trips and in case of PV surplus charge to max.

It is unlcear what this issue should achieve. Planner uses target soc. Once target is achieved, PV mode would stop charging as well. We might revisit this behaviour once we address https://github.com/evcc-io/evcc/issues/5492.