Update Docker image tags in Maven files (pom.xml)

Is there an existing issue for this?

[X] I have searched the existing issues

Feature description
It would be great if it was possible to have image tags in Maven pom.xml files be updated by Dependabot. The use case we have, and that I imagine is not too uncommon in general, is for Jib.
Right now Maven is the most important use case for us but going forward I wonder if there is some thinking around some kind of broader support for file types and formats since image references tend to show up in lots of different kinds of files, e.g. Gradle build files, ko configuration, Skaffold configuration, Makefiles, etc?
Maybe this is already supported but I just can't find any documentation describing what file formats the Dependabot Docker support understands. And I guess this is another problem, it would be great if there was more documentation on exactly what kind of updates, in what file types Dependabot can perform.

Interesting, I didn't realize they could be tagged there.
The docker ecosystem currently will inspect any file matching:
https://github.com/dependabot/dependabot-core/blob/7353a1e4083f840c5be916d0e33d64557f8b722e/docker/lib/dependabot/docker/file_fetcher.rb#L12
As well as kubernetes files:
https://github.com/dependabot/dependabot-core/blob/7353a1e4083f840c5be916d0e33d64557f8b722e/docker/lib/dependabot/docker/file_fetcher.rb#L73
And helm charts:
https://github.com/dependabot/dependabot-core/blob/7353a1e4083f840c5be916d0e33d64557f8b722e/docker/lib/dependabot/docker/file_fetcher.rb#L81
We do receive requests to bump image references in a few other places, and before we do that we'll probably need to add an additional config that allows a user to specify a sub-type of an ecosystem so we know what to actually parse...
Related:

https://github.com/dependabot/dependabot-core/issues/390
https://github.com/dependabot/dependabot-core/issues/5541
https://github.com/dependabot/dependabot-core/issues/5819

Thank you for the response! Would it be feasible to start by documenting what files the docker ecosystem will inspect somewhere? Not sure what the the best place is.

We do receive requests to bump image references in a few other places, and before we do that we'll probably need to add an additional config that allows a user to specify a sub-type of an ecosystem so we know what to actually parse...

Is there an issue for this or is it something we should create?


Using artifact.associate with artifacttype=PipelineArtifact

Hi, I'm attempting to use the ##vso[artifact.associate ... command to forward artifacts from an older pipeline run into a newer one, without downloading and republishing the artifacts.
I've had some success with getting this to work when using artifacts produced by ##vso[artifact.upload ..., where the artifact has a type of Container and a resource.data property which looks like "#/23441549/Shared" (found using the Artifacts - List API).
Unfortunately, we're currently using the PublishPipelineArtifact task to publish artifacts, which produces artifacts with a type of PipelineArtifact. I've done a bit of digging and it looks like this has some level of support from the associate command. Running the following command produces an error that indicates that the server is trying to do something meaningful:
$artifactName = $artifact.name
$data = $artifact.resource.data
$rootId = $artifact.resource.properties.RootId

# Fails with '##[error]The artifact resource does not have a property with key: ProofNodes'
# Failed with an error mentioning RootId before I added the RootId part
Write-Host "##vso[artifact.associate artifacttype=PipelineArtifact;artifactname=$artifactName;RootId=$rootId]$data"

I guess I'm wondering if PipelineArtifacts are supported but not documented, or just not supported at all. If it's the latter, then it might be worth calling this out explicitly (it seems to be indicated elsewhere that PipelineArtifacts are the recommended approach now so it's a bit confusing that they aren't supported in this scenario). If it's the former, then it would be good to know what I'm missing in my example!
Additionally, the examples mention the required type property. I believe that this should be artifacttype, and also that the property isn't  actually required (I was originally seeing errors about failing to infer the type property, which seems to indicate that there's some support for this not being provided).

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

ID: 16bf0bbb-8b63-6384-aa33-b5b1e2b8cfe3
Version Independent ID: f4da8dbd-a02f-bbdf-2cf2-60e081339237
Content: Logging commands - Azure Pipelines
Content Source: docs/pipelines/scripts/logging-commands.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-scripts
GitHub Login: @juliakm
Microsoft Alias: jukullam

@TomGathercole -- Tom, thank you for your thorough feedback.  Please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@juliakm -- Julia, please look into this issue.

@jorfde


Make PBXFileReference return an optional full path

The filesystem path to a PBXReference may not always exist in the fullFilePaths
dictionary, for example when the user incorrectly edits (or merges) their Xcode project file.
I would like to catch this error in R.swift, but can't because this dictionary lookup in Xcode.swift is already a fatal error.

Little bit of background; We crashed into this forced unwrap in a project we worked on. It was an incorrectly merged file, but R.swift now exited with some sort of segfault complaining about a "mac architecture thing". Very confusing.
I don't feel Xcode.swift should support all kind of corrupt Xcodeproj files, but by making this an optional R.swift could indeed catch nil values here and warn the user about them.

As you may have noticed in the source code; This isn't the only !, there's a lot of them!
In practice, I've never seen Xcode.swift crash on any of them. Except for when the xcodeproj is corrupt, like you have here.
In general, I think it's a bad idea to "hide" errors like this.
By making fullPath optional, the user who has a non-corrupt xcodeproj now has to deal with an extra case that will never occur.
A different approach would be to have the XCProjectFile initializer do a bunch of checks to see if the xcodeproj is internally consistent.
It would be really nice if it would throw ProjectFileError.InternalInconsistency with something like:
- BuildFile (46880B8819C43A87006E1F66) references missing fileRef 3EACC98E19EE6D4300EB3C5E
- FileReference `AppDelegate.cpp` (288765A40DF7441C002DB57D) is not used in any BuildFile.

Perhaps a merge conflict?

I agree with @tomlokhorst. After some IRL discussion I think a constructor that validates the project and throws clear errors is better than just making this an optional.
@mbernson do you have the time and would you like to take this up and PR that? Would be awesome if you have the time to pick this up.  But I can't give any guarantees for when it will be done.

I've created an issue for this: https://github.com/tomlokhorst/Xcode.swift/issues/13


Is changing the "make square" shortcut a good idea?

I read in some sub thread that the squareing-shortcut was changed from s to q. There was also a reason why, that I don't recall.
I just wanted to double check, that this change is really the best idea.
Pro:

I believe there was an argument that it is more like josm now?
I believe there was a conflict with another shortcut?
?

Con:

my muscle memory has to be re-trained :-)
all the HOTOSM tutorials in most of the campaigns need to be updated, they all explain somethink like

Please square your buildings ('S' key in the iD web editor) and keep them unattached from roads, landuse and other buildings unless they are physically attached.
(Source)

?

Yes, #5999 is what you're looking for.
We know it's a big change for a lot of people used to hitting S, but it allows us to both straighten or square lines too, which is a big benefit.

@bhousel thanks. I didn't get at first, that the s-key is still there but only to straighten lines now. It all makes sense now :).
Do you have an easy way to contact someone relevant at the HOTOSM crew so they update their help texts after the release?
We could also create an issue at https://github.com/hotosm/tasking-manager/issues/ to let them know now and post that in their slack as a FYI.

Do you have an easy way to contact someone relevant at the HOTOSM crew so they update their help texts after the release?
We could also create an issue at https://github.com/hotosm/tasking-manager/issues/ to let them know now and post that in their slack as a FYI.

You can if you want.  I quit their stuff last year.

(Actually it should be called a rectangle tool, not square tool.)

(Actually it should be called a rectangle tool, not square tool.)

@jidanni All the operations have verb names. "To square" means to make corresponding lines parallel and to make corners 90 degrees. "To rectangle" doesn't mean anything. But that has nothing to do with this issue.


Cannot read properties of null (reading '__helper')

Describe the bug
I have a users entity that references several entities, so what I try to do is to use the fields property of the query to limit which fields to show from the nested properties, but then when I try to limit the properties of the owner field of the projectmembers entity from the project entity then I get the error Cannot read properties of null (reading '__helper').
My project is open source, and you can see who is causing the error here:
https://github.com/kent-0/api/blob/main/src/modules/auth/services/account.service.ts#L126-L174
If you need to run the project, there is an (https://github.com/kent-0/api/blob/main/.env.example) file that you just need to rename to .env and set its values.
Stack trace
[Nest] 18624  - 09/10/2023, 5:27:20 PM   ERROR [ExceptionsHandler] Cannot read properties of null (reading '__helper')
TypeError: Cannot read properties of null (reading '__helper')
    at helper (/home/sawa/personal/backend/api/node_modules/.pnpm/@mikro-orm+core@5.8.0_@mikro-orm+migrations@5.8.0_@mikro-orm+postgresql@5.8.0_@mikro-orm+seeder@5.8.0/node_modules/@mikro-orm/core/entity/wrap.js:21:19)
    at /home/sawa/personal/backend/api/node_modules/.pnpm/@mikro-orm+core@5.8.0_@mikro-orm+migrations@5.8.0_@mikro-orm+postgresql@5.8.0_@mikro-orm+seeder@5.8.0/node_modules/@mikro-orm/core/entity/EntityFactory.js:103:48
    at Array.forEach (<anonymous>)
    at EntityFactory.mergeData (/home/sawa/personal/backend/api/node_modules/.pnpm/@mikro-orm+core@5.8.0_@mikro-orm+migrations@5.8.0_@mikro-orm+postgresql@5.8.0_@mikro-orm+seeder@5.8.0/node_modules/@mikro-orm/core/entity/EntityFactory.js:100:28)
    at EntityFactory.create (/home/sawa/personal/backend/api/node_modules/.pnpm/@mikro-orm+core@5.8.0_@mikro-orm+migrations@5.8.0_@mikro-orm+postgresql@5.8.0_@mikro-orm+seeder@5.8.0/node_modules/@mikro-orm/core/entity/EntityFactory.js:42:18)
    at SqlEntityManager.findOne (/home/sawa/personal/backend/api/node_modules/.pnpm/@mikro-orm+core@5.8.0_@mikro-orm+migrations@5.8.0_@mikro-orm+postgresql@5.8.0_@mikro-orm+seeder@5.8.0/node_modules/@mikro-orm/core/EntityManager.js:372:35)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at AuthAccountService.me (/home/sawa/personal/backend/api/src/modules/auth/services/account.service.ts:128:18)
    at target (/home/sawa/personal/backend/api/node_modules/.pnpm/@nestjs+core@10.2.4_@nestjs+common@10.2.4_@nestjs+platform-express@10.2.4_reflect-metadata@0.1.13_rxjs@7.8.1/node_modules/@nestjs/core/helpers/external-context-creator.js:74:28)
    at Object.accountMe (/home/sawa/personal/backend/api/node_modules/.pnpm/@nestjs+core@10.2.4_@nestjs+common@10.2.4_@nestjs+platform-express@10.2.4_reflect-metadata@0.1.13_rxjs@7.8.1/node_modules/@nestjs/core/helpers/external-proxy.js:9:24)

To Reproduce
Steps to reproduce the behavior:
const user = await this.usersRespository.findOne(
      {
        id: userId,
      },
      {
        fields: [
          'biography',
          'createdAt',
          'first_name',
          'last_name',
          'username',
          'id',
          'projects.project.description',
          'projects.project.end_date',
          'projects.project.id',
          'projects.project.name',
          'projects.project.owner.id',
          'projects.project.owner.username',
          'projects.project.owner.first_name',
          'projects.project.owner.last_name',
          'projects.project.start_date',
          'projects.roles.id',
          'projects.roles.name',
          'projects.roles.permissions',
          'email.value',
          'email.is_confirmed',
        ],
        populate: [
          'email',
          'projects',
          'projects.project',
          'projects.project.roles',
          'projects.project.owner',
        ],
      },
    );

Expected behavior
Result of the relationship of the property owner of the entity project members of the entity project resolved correctly with the fields that were set to view.
Additional context
I am using mikro-orm with nestjs and I am using postgres as database.
Versions

Dependency
Version

node
v20.6.0

typescript
5.2.2

mikro-orm
5.8.0

your-driver
postgres

Can you please provide minimal reproduction? So a script, no additional dependencies, no web servers, no GQL...

Hello @B4nan!
I tried to replicate the problem without using graphql but I could not replicate the problem using the nestjs controllers, only using graphql.

Problem solved. The problem came from this query:
	const tokenSession = await this.tokensRepository.findOne({
      revoked: false,
      token_type: TokenType.AUTH,
      token_value: token,
      user: payload.sub,
	});

That it was being used in an authentication guard: https://github.com/kent-0/api/blob/main/src/modules/auth/strategy/jwt.strategy.ts?rgh-link-date=2023-09-11T18%3A12%3A13Z#L96-L122
Then changing it to:
    const tokenSession = await this.em.fork().findOne(AuthTokensEntity, {
      revoked: false,
      token_type: TokenType.AUTH,
      token_value: token,
      user: payload.sub,
    });

It has worked correctly now.

So it's about contexts, you apparently have something loaded to the context that affects the following query and hydration.
Btw I see you have forceEntityConstructor enabled, may I ask why? I've started to see this flag way too often, and up until now, everyone just misunderstood what it does. I don't see any place in your app that would require it, do you understand that the entities are created with the same class prototype regardless of it? It only controls whether your managed entity (so loaded from he database) fires the constructor or not, there are no other differences (e.g. both ways will support instanceof checks, will have the class methods, etc).

Looks more to me like a code issue rather than an orm issue. Since its solved , i think it can be closed


How to resolve registred types (without constructor)?

Prerequisites

[ ] I have written a descriptive issue title
[ ] I have verified that I am running the latest version of Nancy
[ ] I have verified if the problem exist in both DEBUG and RELEASE mode
[ ] I have searched open and closed issues to ensure it has not already been reported

Description

Steps to Reproduce

System Configuration

Nancy version:
Nancy host

[ ] Nancy.Hosting.Aspnet
[x] Nancy.Hosting.Self
[x] Nancy.Owin ()
[ ] Other:

Other Nancy packages and versions: v1.4.4
Environment (Operating system, version and so on):
.NET Framework version: 4.6.1
Additional information:

Nancy.TinyIoc.TinyIoCResolutionException throwing, when I resolve SyncService as following:
var service = TinyIoCContainer.Current.Resolve<SyncService>();
How can I get instance of registred types from TinyIoCContainer?

@sjahongir What is the stack trace of the exception? Why are you accessing the container like that? It's a big anti-pattern and not something we really support. It would help if you explained why you need to do this, in order for us to provide a good answer

@thecodejunkie, I want to get instance of type in anywhere.

Yeah and that's the problem right there.. WHY do you need this. It sounds like there's an inherit design flaw if you need to do that.

tl;dr
If you want to use TinyIoCContainer.Current when you need to override the GetApplicationContainer and return your own instance (in this case TinyIoCContainer.Current).
⚠ You are probably doing something wrong if you need direct access to the container, from you code, especially if you need it "anywhere"

Thank you for your answer!


fix: router to correct work with first / route and others

This PR fix the problem associated with the route / and rest routes.
In order to reproduce the problem, you can use the code below, which will cause the router /body to stop being called without this fix.
const connect = require('connect');

const app = connect();

app.use('/', (req, res, next) => {
    const { headers, method, body } = req;

    res.writeHead(200, { 'Content-Type': 'application/json' });
    res.end(JSON.stringify({ headers, method, body }, null, 2));

    next();
});

app.use('/body', (req, res, next) => {
    const { body } = req;

    res.writeHead(200, { 'Content-Type': 'application/json' });
    res.end(JSON.stringify({ body }, null, 2));

    next();
});

Closing due to no response.


Code coverage ignores project with keyword "DataCollector" in their name

There is a hidden behavior not mentioned anywhere. If your project is named anywhere as DataCollector the code coverage wont pick it up.
It should be noted here as a troubleshot step that if your project has the word/setence "DataCollector" in it. It won't work.
Examples of project names that wont be picked up:

DataCollectorUnitTests
Fabrikam.DataCollector
Fabrikam.DataCollector.UnitTests

The above info should be added to the docs

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

ID: c4d41fc7-bc52-8fe3-6b25-c1b2c3f89eb1
Version Independent ID: 9d141754-5f8f-d330-0974-75cbcf45a011
Content: Troubleshooting Code Coverage - Visual Studio (Windows)
Content Source: docs/test/troubleshooting-code-coverage.md
Product: visual-studio-windows
Technology: vs-ide-test
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@pavelhorak Pavel, is it OK to document this behavior? I assume this is some kind of reserved name.

Fix should be live by the end of the day.


Scenario to restart kubelet

Node scenarios ( https://github.com/krkn-chaos/krkn/blob/main/docs/node_scenarios.md ) should support kubelet restart scenario with number of iterations as a parameter.

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

PR for this was added here: https://github.com/krkn-chaos/krkn/pull/688


ContactDetail.contactDetailType, ContactDetail.contactDetailCategory - combine terms

See meeting notes: 2nd March 23
Original defs: https://github.com/tdwg/cd/issues/331, https://github.com/tdwg/cd/issues/330
Current master defs: https://github.com/tdwg/cd/blob/review/standard/terms/ltc_standard_terms_draft.csv#L43
These two are a bit too similar/hard to distinguish and that is 🙅♀🙅♀🙅♀. We want to keep contactDetailCategory and widen it a bit to incorporate some of the functionality from contactDetailType. The resulting property will be primarily used to state the mechanism of contact, rather than the purpose of the communiqué, although it does have a little wiggle room to distinguish between different types of the same communication medium, e.g., mobile phone vs. home phone.

[x] Update contactDetailCategory's examples to include some of the work phone/home phone/mobile phone type scenarios
[x] Remove contactDetailType from termlist/skos mapping docs/wherever else it may appear

Closed by #473


Search all files

A very low priority request but thought this would be cool
The ability to use the full Obsidian search function through better command palette would be cool.
It becomes like a floating/popup search function, rather than being stuck in the small sidebar space.

I like this. It likely is a significant amount of work to add this in, but I think worth it. Don't expect it in the near term at all, but I will start working on it 😄

Haha very true, it's a bit ambitious! Awesome to hear you're considering it

Something maybe that could fit in? https://github.com/scambier/obsidian-omnisearch


Remove *ReadyCount from telemetry status

This removes "autoscalingReadyCount" and "ceilometerReadyCount" as discussed in https://github.com/openstack-k8s-operators/telemetry-operator/pull/256#discussion_r1434162340
Telemetry is able to deploy only one of each resource, therefore the count can only be either 0 or 1. In this case the Ready contitions with values True or False give us the same information.

/lgtm

/retest


Documentation suggestions.

Going through your documentation, I think it would be helpful to be more explicit in the requirements for the input data format. In particular:

Mentioning image registration requirements. Is the star at the center of the image (what about for even-sized arrays) for all images?
The format of the angles vector. Also, whether this is CCW or CW rotation, and whether it is in degrees or radians.

For the SDI feature, I understand it is still under development but here are some suggestions:

Typically, this is done in IFS images where multiple wavelengths are acquired at the same time. I'd suggest leading with the nf dimension rather than the nlam dimension
How is the scales argument defined? I think there is a 1/x degeneracy without knowing its definition (or an example computing this term from the wavelength).

Thanks for the comments- I remember when I was first learning these things I had to grok source code, so I love the suggestion to clarify the data structures in the docs.
For the SDI, so far I've been using the same model that VIP uses, which permutes the dims with the spectral axis first. I've made sure to include a note in the docs discussing the potential discrepancy and made a note about how to form the scales from the wavelengths.
Again, thanks for the in-depth comments- everything starts to look better the more eyes look at it!


Blob Trigger - Event Hub Capture - Avro Issue Error: truncated bufferat RecordType.Type.fromBuffer

I am using Azure EventHubs archive to store my event hubs data to an azure blob storage. Eventhubs archive stores the data in avro format. I've written an Azure function in NodeJS that listens to the blob trigger event (fired whenever data is sent to Eventhubs and written to the blob storage in avro format).
As soon as the trigger is fired, I want to decode the data sent in avro format (which is a binary buffer) and retrieve the payload
Error received: Error: truncated bufferat RecordType.Type.fromBuffer
index.js file:
`const avro = require('avsc');
module.exports = async function (context, myBlob) {
context.log("JavaScript blob trigger function processed blob \n Blob:", context.bindingData.blobTrigger, "\n Blob Size:", myBlob.length, "Bytes");
context.log(typeof myBlob);//returns object
//get Schema dynamically instead of statically defined below:
const schema = avro.Type.forSchema({
type : "record",
name : "EventData",
namespace : "Microsoft.ServiceBus.Messaging",
fields : [ {
name : "SequenceNumber",
type : "long"
}, {
name : "Offset",
type : "string"
}, {
name : "EnqueuedTimeUtc",
type : "string"
}, {
name : "SystemProperties",
type : {
type : "map",
values : [ "long", "double", "string", "bytes" ]
}
}, {
name : "Properties",
type : {
type : "map",
values : [ "long", "double", "string", "bytes", "null" ]
}
}, {
name : "Body",
type : [ "null", "bytes" ]
} ]
});
if(myBlob.length){
    context.log("JavaScript blob trigger function processed blob \n Name:", context.bindingData.name, "\n Blob Size:", myBlob.length, "Bytes");
    context.log(schema.fromBuffer(myBlob)); // myBlob contains the binary avro buffer data

}
context.done();

};`

FYI @alrod . Transferring this to the Node repo

@zhamadagithub Are you still experiencing this issue? If yes, can you please provide more information about the app and function, including the function.json contents? And if there's an example avro file that doesn't contain private info, can you also share that please?


merge from arlac77/npm-package-template

package.json

fix(engines): add >=12.15.0 remove >=12.14.1 (engines.node)

.travis.yml

chore(travis): (jobs.include)
chore(travis): add 12.15.0 remove 12.14.1 (jobs.include.node_js)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[auto-form] Editing many-to-one relationships

For many-to-one properties auto form should add a single-selection field. A ComboBox seems like the most useful default field to use as it supports lazy-loading. The field should render a useful string representation of each entity and should be filterable by it. Ideally the field automatically knows how to load related entities based on the model and without manual configuration.

I'm encountering a similar issue with a Many-to-One relationship. I've set up a ComboBox to showcase the child objects , but upon clicking the submit button, nothing seems to occur. There's no visible activity even in the network logs. Is there a workaround available for addressing this problem?

Adding a combo box for a many to one property should look something like this:
@Entity
public class Employee {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;
    @ManyToOne
    private Department department;
    ...
}

@Entity
public class Department {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;
    private String name;
    @OneToMany(mappedBy = "department", fetch = FetchType.LAZY)
    @JsonIgnore
    private List<Employee> employees;
    ...
}

@AnonymousAllowed
@Endpoint
public class EmployeeService extends CrudRepositoryService<Employee, Long, EmployeeRepository>{
}

const [employee, setEmployee] = useState<Employee>();
const [departments, setDepartments] = useState<Department[]>([]);

useEffect(() => {
    EmployeeService.get(1).then(setEmployee);
    DepartmentService.list().then(setDepartments); // Some other service that gets all department entities
}, []);

<AutoForm
    service={EmployeeService}
    model={EmployeeModel}
    item={employee}
    fieldOptions={{
        department: {
            renderer({field}) {
                return <ComboBox {...field} items={departments} itemIdPath="id" itemValuePath="id"
                                 itemLabelPath="name"/>;
            }
        }
    }}/>


Investigate using Confluent Cloud API to obtain Consumer Group's current_offset data

This would enable Kommitted to work with Confluent Cloud. Unfortunately the API don't seem to return the timestamp of when the value current_offset was read, and so we will have to work on the assumption it's the wall clock value.
The "Emitter -> Register" design choice still works pretty well here: it will require to introduce a new Emitter that loops over the list of currently known Consumer Groups. That list can be obtained via the consumer_groups module, and then multiple reads will have to be arranged via API.
Potentially, to save requests, the listKafkaConsumerLags API could be used.
API doc:

getKafkaConsumerLag
listKafkaConsumerLags

API path:
/kafka/v3/clusters/{cluster_id}/consumer-groups/{consumer_group_id}/lags/{topic_name}/partitions/{partition_id}

Request example:
curl --request GET \
  --url https://pkc-00000.region.provider.confluent.cloud/kafka/v3/clusters/cluster-1/consumer-groups/consumer-group-1/lags/topic-1/partitions/0 \
  --header 'Authorization: Basic REPLACE_BASIC_AUTH'

Response example:
{
  "kind": "KafkaConsumerLag",
  "metadata": {
    "self": "https://pkc-00000.region.provider.confluent.cloud/kafka/v3/clusters/cluster-1/consumer-groups/consumer-group-1/lags/topic-1/partitions/1",
    "resource_name": "crn:///kafka=cluster-1/consumer-group=consumer-group-1/lag=topic-1/partition=1"
  },
  "cluster_id": "cluster-1",
  "consumer_group_id": "consumer-group-1",
  "topic_name": "topic-1",
  "partition_id": 1,
  "consumer_id": "consumer-1",
  "instance_id": "consumer-instance-1",
  "client_id": "client-1",
  "current_offset": 1,
  "log_end_offset": 101,
  "lag": 100
}

First few notes

module consumer_groups must have it's own ConsumerGroupsRegister and return that on ::init() instead of the ConsumerGroups channel receiver
This new Register has to be configurable: how long after a consumer group stops being reported by the Kafka API, we keep it around in the data (eg application has a total failure, we don't want the CG Lag info to entirely disappear immediately)
Lag Register should use the new register as source of truth for the set of known groups, instead of relying on the data it contains
An entire "emit handling branch" in the Lag Register can be removed: no more need to populate it's internal structure, if the new Register is the source of truth

These changes are valid and doable even before we start consuming Confluent API.
Once the changes above are done, a new emitter, alternative to the KonsumerOffsetsDataEmitter can be created: this would also consume the new ConsumerGroupsRegister, and loop over the list of groups. It will:

list groups
for each group, query the Confluent Cloud API
Create and emit objects OffsetCommit

This emitter would "slotted" in as alternative to KonsumerOffsetsDataEmitter, based on command line arguments.


[New Feature]: automated report generation and command line interface for generating reports

Checked for duplicates
No - I haven't checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
It's frustrating to wait on operators to click through a slow and cumbersome interface to generate reports.  I'd like the ability to generate them via the command-line, which would allow a single script call to generate everything needed for a given time period (and could also be automated with a chron job).
Describe the feature request
Command-line interface to generate reports - anything that can be generated with the Reporting UI.  Automatically generating them with PCM code is optional - I'm OK with operator-controlled & CM'd scripts to do that as well.

For Production time summary report:
http:///bach-api/reports/ProductionTimeSummaryReport?startDateTime=2024-06-05T00:00:00&endDateTime=2024-06-05T23:59:59&reportType=sdp&mime=application/zip
For production time detailed report:
curl -kL "http:///bach-api/reports/ProductionTimeDetailedReport?startDateTime=2024-06-01T00:00:00&endDateTime=2024-06-30T23:59:59&reportType=sdp&mime=text/csv" >
For retrieval time summary report:
curl -kL "http:///bach-api/reports/RetrievalTimeSummaryReport?startDateTime=2024-06-01T00:00:00&endDateTime=2024-06-30T23:59:59&reportType=sdp&mime=application/zip" >
For retrieval time detailed report:
curl -kL "http:///bach-api/reports/RetrievalTimeDetailedReport?startDateTime=2024-06-01T00:00:00&endDateTime=2024-06-30T23:59:59&reportType=sdp&mime=text/csv" >


"Delete unattached classic VM disks stored in the storage account" does not seem to be a requirement for storage account migration any more.

"Delete unattached classic VM disks stored in the storage account" does not seem to be a requirement for storage account migration any more.
I was able to migrate a classic storage account with unattached classic disk present in it.
steps to reproduce the issue :
Created a storage account 'classicstormig'.
added an OS vhd and created a classic 'Disk' from it.
created a Classic VM classicstormig using the same storage account.
Performed VM MIgration :-
$vnetName = "Group classicstormig classicstormig"
Move-AzureVirtualNetwork -Validate -VirtualNetworkName $vnetName -Debug
Move-AzureVirtualNetwork -Prepare -VirtualNetworkName $vnetName -Debug
Move-AzureVirtualNetwork -Commit -VirtualNetworkName $vnetName -Debug
Performed Storage account migration
$storageAccountName = "classicstormig"
Move-AzureStorageAccount -Validate -StorageAccountName $storageAccountName -debug
Move-AzureStorageAccount -Prepare -StorageAccountName $storageAccountName -debug
Move-AzureStorageAccount -Commit -StorageAccountName $storageAccountName -debug
It worked successfully without any issues. The unattached classic disk stayed as a vhd in ARM.

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

ID: 972e651f-7ac9-fd9c-092b-5fb7334f0721
Version Independent ID: f56b5a76-a64d-7f0f-3bf1-307dec38de8e
Content: Migrate to Resource Manager with PowerShell
Content Source: articles/virtual-machines/windows/migration-classic-resource-manager-ps.md
Service: virtual-machines-windows
GitHub Login: @singhkays
Microsoft Alias: kasing

@nayakshweta, Thank you for your efforts on enhancing the documentation. I will repro and post the results here.

@nayakshweta, I am able to reproduce the same scenario. You don't need to delete the unattached classic VM disks stored in the storage account to migrate from ASM to ARM. I guess the Powershell commands are optional. I will assign this issue to the author, where he can clarify and make changes to the documentation accordingly.

Correct, this is an optional step. The platform removes the disks and migrates the blobs underneath

We are currently closing out long standing backlog in order to better determine which issues are still valid and which have been addressed. If you are still seeing a specific problem with this document please open a new issue so we can properly assign the feedback to the correct author and get it addressed ASAP.
#please-close


ImportError: cannot import name 'enable_fused_na' from 'natten'

Hello, I'm trying to inference with your pretrained model. But I encounter ImportError: cannot import name 'enable_fused_na' from 'natten' error. I tried to change torch & natten versions but the same error occurs again and again.

python main.py type=inference

Traceback (most recent call last):
  File "/home/justin/workspace/StyleNAT/main.py", line 11, in <module>
    from models.generator import Generator
  File "/home/justin/workspace/StyleNAT/models/generator.py", line 22, in <module>
    from models.stylenat import HydraNeighborhoodAttention, MHSARPB, NeighborhoodAttentionSplitHead
  File "/home/justin/workspace/StyleNAT/models/stylenat.py", line 14, in <module>
    from natten import (
ImportError: cannot import name 'enable_fused_na' from 'natten' (/home/justin/anaconda3/envs/stylenat/lib/python3.10/site-packages/natten/__init__.py)

Also the following is my pip freeze output.

antlr4-python3-runtime==4.9.3
certifi==2024.2.2
charset-normalizer==3.3.2
click==8.1.7
cmake==3.29.3
contourpy==1.2.1
cycler==0.12.1
dill==0.3.8
docker-pycreds==0.4.0
einops==0.8.0
filelock==3.13.1
fonttools==4.52.4
fsspec==2024.2.0
ftfy==6.2.0
gitdb==4.0.11
GitPython==3.1.43
huggingface-hub==0.23.2
hydra-core==1.3.2
idna==3.7
imageio-ffmpeg==0.4.9
Jinja2==3.1.3
joblib==1.4.2
kiwisolver==1.4.5
lmdb==1.4.1
markdown-it-py==3.0.0
MarkupSafe==2.1.5
matplotlib==3.9.0
mdurl==0.1.2
mpmath==1.3.0
natten==0.17.1+torch220cu121
networkx==3.2.1
ninja==<IP_ADDRESS>
numpy==1.26.4
nvidia-cublas-cu12==<IP_ADDRESS>
nvidia-cuda-cupti-cu12==12.1.105
nvidia-cuda-nvrtc-cu12==12.1.105
nvidia-cuda-runtime-cu12==12.1.105
nvidia-cudnn-cu12==<IP_ADDRESS>
nvidia-cufft-cu12==<IP_ADDRESS>
nvidia-curand-cu12==<IP_ADDRESS>
nvidia-cusolver-cu12==<IP_ADDRESS>
nvidia-cusparse-cu12==<IP_ADDRESS>
nvidia-nccl-cu12==2.19.3
nvidia-nvjitlink-cu12==12.1.105
nvidia-nvtx-cu12==12.1.105
omegaconf==2.3.0
packaging==24.0
pillow==10.3.0
platformdirs==4.2.2
protobuf==4.25.3
psutil==5.9.8
Pygments==2.18.0
pyparsing==3.1.2
python-dateutil==2.9.0.post0
PyYAML==6.0.1
requests==2.31.0
rich==13.7.1
safetensors==0.4.3
scikit-learn==1.5.0
scipy==1.13.1
sentry-sdk==2.3.1
setproctitle==1.3.3
six==1.16.0
smmap==5.0.1
sympy==1.12
threadpoolctl==3.5.0
timm==1.0.3
torch==2.2.2+cu121
torchaudio==2.2.2+cu121
torchvision==0.17.2+cu121
tqdm==4.66.4
triton==2.2.0
typing_extensions==4.11.0
urllib3==2.2.1
wandb==0.17.0
wcwidth==0.2.13

The problematic code is as follows:

And I verified there are no such enable_fused_na() and so on.

Thanks for your great project, I hope I could hear from you.
Best,
Junyeong Ahn

Thank you for raising this issue; that's my fault, I changed the API name in 0.17.
Although now that I'm looking more closely, it looks like StyleNAT doesn't use FNA, even though the flags are being set.
I'll push a temporary fix to unblock you right now and will wait for @stevenwalton to chime in.
StyleNAT should be able to use FNA for inference, but training gets complicated because FNA doesn't implement the backward pass for RPB.

I close this issue since at least the error is fixed although there are some others remaining.

@alihassanijr thanks for handling this so quickly.
I think FNA was still in alpha when we did this so it wasn't fully implemented or maybe there was miscommunication between us. We can fully switch to FNA. We can sync outside this chat.
@justin4ai, thanks for your interest in StyleNAT. We're always interested to see what people do with it, and don't hesitate to reach out if you're running into issues. Some of the param choices can be tricky. If you're doing face-swapping (as your profile suggests) the attention maps will be helpful for debugging and finding artifacts.

@stevenwalton Thanks for your suggestion! I really love your works. Actually I'm trying to replace mere attention module with your HydraNAT module in absorbing diffusion sampler for facial image generation! And this StyleNAT helps me a lot as both a reference for my trial and itself. I'd like to share my work if it finishes! Thank you so much anyways :)

Great to hear! You'll need a bit more complex kerneling for things other than faces. Though this will play a bit differently in diffusion, but it should work fine.


spec/iasm.dd: Add definition for Opcode

The full set of supported opcodes is probably an implementation detail, so we should at least include definitions for the syntax used to lex them.

The full list is actually here:
https://dlang.org/spec/iasm.html#supported_opcodes
But, I don't think it would make sense to restrict this list to whatever DMD supports.


Fix the yaml indentation for the docs.yml workflow

Gotta love yaml.

Motivation
The docs publishing workflow got re-enabled recently but the yaml in the file got mangled.
Solution

Fix the indentation at the bottom of the workflow yaml to make it parse correctly again.
Review
Not urgent.

Sorry about that, i copy & pasted the code instead of using revert(https://github.com/ZcashFoundation/zebra/issues/1784#issuecomment-782318471) so the last line of the docs was broken and was not able to see it. Thanks for the fix @dconnolly

Sorry about that, i copy & pasted the code instead of using revert(https://github.com/ZcashFoundation/zebra/issues/1784#issuecomment-782318471) so the last line of the docs was broken and was not able to see it. Thanks for the fix @dconnolly

No worries, yaml's funky 🤭

Sorry about that, i copy & pasted the code instead of using revert(#1784 (comment)) so the last line of the docs was broken and was not able to see it. Thanks for the fix @dconnolly

I didn't realise there was a revert button until last week when I had to revert a bunch of PRs.
Just letting you know so it's easier for you next time.


[FR]: Automatically add the "created" key with the file.ctime and add the "updated" key with the file.mtime

Issue validation

[X] I checked the issue to prevent duplicate

Is your feature related to a problem ?
When using cloud services to automatically deploy Quartz, the created time of notes will become the deployment time. Usually, it is necessary to manually add a field to frontmatter to mark the created time of notes (advanced, some blogs can also display article updated time by adding a field). Can the file's inherent properties be utilized to automatically create fields and add the file's creation and modification times when there are no relevant fields?
What solution do you want to see ?
The function may be simliar to https://github.com/Enveloppe/obsidian-enveloppe/issues/242.
Describe the alternative you've considered
No response
OS
Windows
Anything else?
No response
Plugin version
7.3.0
Obsidian version & debug log
Obsidian v1.6.7

Out of the scope.


Fix images in Wiki repo not showing in Gitea Wiki (#4690)

wikiRaw method in routers calls WikiNameToFilename which unconditionally adds ".md" to the path.
As a result, findEntryForFile will fail finding the corresponding git blob.
I added WikiNameToFilenameRaw to the model used in wikiRaw which omits any additions to the filename.
Signed-off-by: Matthias Wientapper<EMAIL_ADDRESS>

Please fmt and commit.

Codecov Report

Merging #5013 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #5013      +/-   ##
==========================================
+ Coverage    37.4%   37.41%   +<.01%
==========================================
  Files         306      306
  Lines       45374    45377       +3
==========================================
+ Hits        16973    16976       +3
- Misses      25947    25949       +2
+ Partials     2454     2452       -2

Impacted Files
Coverage Δ

routers/repo/wiki.go
44.96% <0%> (ø)
:arrow_up:

models/wiki.go
61.22% <0%> (-1.28%)
:arrow_down:

models/repo_indexer.go
52.11% <0%> (+1.27%)
:arrow_up:

Continue to review full report at Codecov.

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

Tests will be better.

Gentle bump. 😃
Can I do anything to make this simple PR acceptable?

@mattzzw as I mentioned before could you add some tests that will let review easier.

I think this has been fixed by #5814


[App Request] Invidious

App Information

Name: Invidious
Short Description: open source alternative front-end to YouTube.
Official Website: https://invidious.io/
GitHub Repository: https://github.com/iv-org/invidious
Docker Image: https://quay.io/repository/invidious/invidious

Why do you want this app?
It is an unparalleled alternative to Youtube's front end and one that respects your privacy. Setup process is a breeze, however since CasaOS does not support importing multiple services via docker-compose, transferring it to CasaOS is a bit more complex. Adding it to the app store would be a welcome addition.
Additional information?

The Invidious docker image is only available on Quay because, unlike Docker Hub, Quay is Free and Open Source Software.

Ample documentation available at https://docs.invidious.io/installation/

Update?

+1

+1

I have been trying to install Invidious manually to no success. Not on Cacaos at least, I managed to get it running locally, with the same script, but when I import it into Cacaos I just get a blank settings screen, so apparently it wasn't in the mood.
And even when I got a window that worked, I get a 502 error for a bad gateway, when trying to launch. It might be because of the Quay image? There is a docker image, but it is not official, and I got the same results.
As stated in the documentation, I first had to pull the Invidious repo, but I have got quite used to ssh into Cacaos to get what I want.
I did have to change the port, already had something running on 3000.
Cacaos also doest know how to parse the nested environment from the Invidious docker compose file.
      INVIDIOUS_CONFIG: |         db:           dbname: invidious           user: kemal           password: kemal           host: invidious-db           port: 5432
This just becomes one variable, with everything else inside it. I flattened it to:
      INVIDIOUS_DB_DBNAME: invidious       INVIDIOUS_DB_USER: kemal        INVIDIOUS_DB_PASSWORD: kemal       INVIDIOUS_DB_HOST: invidious-db       INVIDIOUS_DB_PORT: 5432       INVIDIOUS_CHECK_TABLES: true       INVIDIOUS_HMAC_KEY: "Cahnge me to a random 20 char password"
I don't know any more, this was a rather frustrating afternoon, so I leave you with my docker fill, and I will return when this is an item in the store, or somebody else manages to get it up and running.
`version: "3"
services:
invidious:
image: quay.io/invidious/invidious:latest
restart: unless-stopped
ports:
- "3115:3000"
environment:
INVIDIOUS_DB_DBNAME: invidious
INVIDIOUS_DB_USER: kemal
INVIDIOUS_DB_PASSWORD: kemal
INVIDIOUS_DB_HOST: invidious-db
INVIDIOUS_DB_PORT: 5432
INVIDIOUS_CHECK_TABLES: true
INVIDIOUS_HMAC_KEY: poo3eThah3euraepiegh
healthcheck:
test: wget -nv --tries=1 --spider http://<IP_ADDRESS>:3115/api/v1/trending || exit 1
interval: 30s
timeout: 5s
retries: 2
logging:
options:
max-size: "1G"
max-file: "4"
depends_on:
- invidious-db
invidious-db:
image: docker.io/library/postgres:14
restart: unless-stopped
volumes:
- postgresdata:/var/lib/postgresql/data
- ./DATA/AppData/invidious/config/sql:/config/sql
- ./DATA/AppData/invidious/docker/init-invidious-db.sh:/docker-entrypoint-initdb.d/init-invidious-db.sh
environment:
POSTGRES_DB: invidious
POSTGRES_USER: kemal
POSTGRES_PASSWORD: kemal
healthcheck:
test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB"]
volumes:
postgresdata:`

+1

+1


Amir/azure auth/dont require refresh token

This PR fixes https://github.com/microsoft/azuredatastudio/issues/11434

I'm going to be doing a bunch of manual testing on this to validate the base features still work

Coverage increased (+0.1%) to 37.651% when pulling 5ec03269f3e6c3ee5fe21a35cd2e46f5d2ba8943 on amir/azureAuth/dontRequireRefreshToken into 047c51921b8b09bfd81bd6e73cd31d025cf90c15 on main.

Going to do a full refactor of the azure auth since it wasn't initially designed with refresh tokens changing in mind


Add TorchScript version

Hi, I just did something that can export PyTorch model to TorchScript version

Add modified MODNet that satisfies TorchScript version
Modify MobileNetV2 (Due to torch.jit doesn't support lambda expression)
Upload an exported TorchScript model using official pretrain model (See README.md for detail)

Hi, thanks for your contributions! I will test the code and merge it next week. Then I will give you a feedback.

Thanks a lot !

Hi, I have tried to merge you branch. However, it seems that the code will affect some other demos. Therefore, I reversed it.
Could you start a new pull requests to the branch develop?
In this way, I can process it before merge it to master. Thanks.

No problem.


Buffer with buftype=prompt lost the prompt icon after running dd

Steps to reproduce

Open a new buffer
run set buftype=prompt
go into insert mode
type something
dd
prompt icon is gone.
back to insert, prompt icon is back

Expected behaviour
I think the prompt icon should always be visible.
Version of Vim
8.2.3489
Environment
OS: macOS 12.1 (the latest)
terminal: kitty
$TERM: xterm-kitty
shell: zsh 5.8
Logs and stack traces
No response

With "prompt icon" you mean the "%" at the start of the line?
If you delete the line then there is no line to put "%" in front of.
Thus I would say this is expected.

Okay, make sense. Thank you very much. Closing this.


Imaginary friend antag

I'm closing this one because reading it now it's kinda similar to split personality.


Thrimbletrimmer Fixes 2021 Roundup #3

This is a quicker round fixing a couple things of varying intensity:

The range endpoints updating when the video load time changes turned out to be massively broken (further described in the relevant commit message). This makes it (and the interaction between ranges and reloading the video in general) work properly.
Validation on title/description for a video now also applies on page load.
Since a workflow for time conversion was mentioned during editor training, I added a time conversion tool to the restreamer page. It's not part of the header times like in the old Thrimbletrimmer because I found that to be fairly annoying when quickly entering times, but there is now a tool that does it.

It also already defaults to "time ago" so I'm not sure what you'd be converting for that?
My primary use case is picking up swaths of time that happened at some point during the run, for which entering times and then remembering that I didn't switch it to bustime first and then having to go back and enter the times a second time is lightly frustrating. (This happens occasionally.) I suppose I could fix that with some light UI rearrangement on the time entry.


Dashboard is unavailable

Hello... I have two new miners and from the start they cannot open dashboard... I tried many browsers also check firewall and all other things and the problem cannot resolve... Panther support is very lazy, Im still waiting for help.... I also tried to acces via putty but also without success because password admin doesnt work..... Before 1 weeks I also have the same problem with panther x2 mineer and that one of their tech fix it with anydesk and putty acces... any option to fix this problem on my new miners ?

@hajlender89 please submit your ticket in https://panther.global/ and keep it online, the technical support will help you to fix it.


Viewport setting seems odd when pixel ratio is not 1

I was trying to use window.viewport to simplify my calculations in terms of having the window centered at 0,0 in model space. I modified the code in examples/model/model.py, changing line 14
    window.viewport = (0, 0, *window.get_framebuffer_size())

to
    w, h = window.get_framebuffer_size()
    window.viewport = (-w/2, -h/2, *window.get_framebuffer_size())

and found that the cube moved twice as far on the screen as I had expected. (For ease of visualization, I also changed lines 33 and 39 trans = Mat4.from_translation(Vec3(-1.75, 0, 0)) to trans = Mat4.from_translation(Vec3(0 0, 0)) to center the cube in world space at 0,0,0.)
If I instead used
    window.viewport = (-w/4, -h/4, *window.get_framebuffer_size())

then the world is centered as expected. I believe this is because on my MacOS machine,get_pixel_ratio() returns 2.0. (The requested window size is 720x480, but get_framebuffer_size() of course returns 1440 x 960.)
It seems like the OpenGL viewport should not care about the pixel_ratio, so I don't understand why this is occurring. I suspect this is more a misunderstanding on my part, but perhaps it is a bug in perspective_projection or look_at???
thanks!

The purpose of viewport is only to define what area of the screen we render to.
This makes sure you render to the entire screen even if you have hidpi window
window.viewport = (0, 0, *window.get_framebuffer_size())

The coordinate system of the window is decided by the projection. (window.projection). The configured projection is projected into the viewport meaning the viewport acts as a "screen". The smaller viewport you have the smaller the content will be.

Please correct me if I'm wrong, but I believe the viewport defines the coordinates in render space that get mapped to window space. So by setting window.viewport = (-w/2, -h/2, w, h), the bottom left pixel will map to (-w/2, -h/2) after all of the transformations are applied.
(I also just verified that I can place objects throughout the window with the viewport set as described here.)

More confusion - I see that in Linux, with the same code, I find that window.viewport = (0, 0, w, h) produces the behavior I want (pixel_ratio = 1.0).

Einarf is correct here.
The viewport in OpenGL, is usually used to determine which part of the visible screen you want to render into. In your case, you're stretching it off of the bottom left size of the screen. Generally speaking, you want the viewport to cover the viewable screen, and leave it like that. You might set the viewport temporarily smaller to renderer in a mini-map, or rear-view mirror in a car, etc., but generally speaking you shouldn't touch it.
Instead as Einarf suggested, use the Window.projection matrix to control the projection. If you only wish to translate the "camera", use the Window.view matrix. In the default shaders, both are multiplied together (MVP, or Model-View-Projection as it's called).
See the examples/model/fpscamera.py example of how this works to move around a scene.

Hi Ben/Einarf,
Yeah - the model.py code uses the Mat4.look_at() function to define a camera centered in the world. Maybe to summarize the issue - it seems like it doesn't actually center the view on MacOS with pixel_ratio=2. Screen shots attached freezing the first frame running the example code.
thanks
Caleb

Ah, I see the issue. The Window.viewport setter was updated to automatically handle pixel aspect ratio.
You can use the on_resize(width, height) values as-is, and no longer need to pass in get_framebuffer_size(). I updated the examples in Github to reflect that.
For reference (Window class):
    @viewport.setter
    def viewport(self, values: tuple[int, int, int, int]) -> None:
        self._viewport = values
        pr = self.get_pixel_ratio()
        x, y, w, h = values
        pyglet.gl.glViewport(int(x * pr), int(y * pr), int(w * pr), int(h * pr))

Awesome. Now things look right. Sorry about the confusion and I appreciate your time!!!

No worries, it was a valid bug in the examples.


feature add restore new property 'reserve_dynamic_partition_enable'

Proposed changes
Issue Number: close #xxx
Problem summary
add restore new property 'reserve_dynamic_partition_enable', which means you can
get a table with dynamic_partition_enable property which has the same value
as before the backup. before this commit, you always get a table with property
'dynamic_partition_enable=false' when restore.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes

Has unit tests been added:

[ ] No Need

Has document been added or modified:

[ ] Yes

Does it need to update dependencies:

[ ] No

Are there any changes that cannot be rolled back:

[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Can you create an issue for this feature where you can describe it more detail?


Add bubble sort

@NyorJa : It would be great if you can add the description along with the issue number.
Feel free to use our contribution guidelines (https://github.com/fnplus/interview-techdev-guide/blob/master/CONTRIBUTING.md) for reference

Thanks for contributing!


Fix for connection glitch

Fix for https://github.com/MindFreeze/ha-sankey-chart/issues/18

Play around and you will see, that without the fixes, the bugs are there and with no bugs are there. I played around with a lot of cases. Please show only one situation, where the fix is not working.
Better to have

instead of

in the min1 case.
And regarding startYOffset. Without that, the connections are not drawn

with, they are drwan absolutely correctly.

Really don't see, why you want to have tis cases

If there is a fix.


Do we have to show the repository dropdown for only one repo

Create a new PR. Notice there are 4 drop-downs.
I believe this makes the view much more complicated than having just 2 drop-downs as GitHub does

Do we show the repository drop-down because there can be multiple repositories in the Workspace?
Does it make sense that we do not show the repository dropdown for Workspaces that have only one repository? I believe this is the majority and would quite simplify the flow. What do you think?

Thanks for the explanation.

Duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/4403


chore(dart pubspec.yaml): consistent baseline

Make all pubspec.yaml files consistent with the stagehand web-angular default.
Fixes #1642.

I'm taking a look now...

LGTM
@thso LGTY?

Merging now...


pod update failing

Dear Team,
I was using 1.0.2 version of SwiftForms and when I updated the pod, it is giving me a lot of errors

Please help, should I update or roll back to 1.0.2?
Thanks a lot.

Yo should use new API, or either downgrade to any version prior to 1.5


Adding some Spanish banks and Halifax from UK

This is what I have for now. Added, among others, BBVA, Banco Santander, CaixaBank, Banco Sabadell, and ING.
I'll continue adding more banks as a get more bank accounts to extract the needed info. I'll also work on the new Exceptions as discussed in #19.
I would need this merged and released to use the new banks data in my project. Unless there is an easy way to use a tarball version from my own repo. I used to do so via dependency_links but it looks like pbr doesn't play well with that snapshot-like option. What I have done is to tag my update as 2020.01.1 in my repo and setup my dependency_links to point to my repo's tarball (https://github.com/osroca/schwifty/tarball/2020.01.1#egg=schwifty-2020.01.1). This caused the following error when installing my project:
  File "/private/var/folders/z_/ll7j31r11p37z687bk0w7bs80000gn/T/easy_install-id3gs88l/osroca-schwifty-2a88b09/.eggs/pbr-5.4.4-py3.7.egg/pbr/hooks/metadata.py", line 26, in hook
    self.config['name'], self.config.get('version', None))
  File "/private/var/folders/z_/ll7j31r11p37z687bk0w7bs80000gn/T/easy_install-id3gs88l/osroca-schwifty-2a88b09/.eggs/pbr-5.4.4-py3.7.egg/pbr/packaging.py", line 876, in get_version
    name=package_name))
Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. It's also possible that there is a mismatch between the package name in setup.cfg and the argument given to pbr.version.VersionInfo. Project name schwifty was given, but was not able to be found.
error: Setup script exited with error in setup command: Error parsing /private/var/folders/z_/ll7j31r11p37z687bk0w7bs80000gn/T/easy_install-id3gs88l/osroca-schwifty-2a88b09/setup.cfg: Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. It's also possible that there is a mismatch between the package name in setup.cfg and the argument given to pbr.version.VersionInfo. Project name schwifty was given, but was not able to be found.

It's a bit embarrassing, but I'm not familiar enough to pbr.

It's good that were starting to get some non-german banks into schwifty! I think however that I have to add a mechanism first to deal with different kind of data sources. What I mean is that the current bank-registry.json is a generated file, but now there is manually curated data that should not be overwritten by the generator script. I can work on a solution for that tomorrow.
Regarding your installation problem. Are you trying to install your local version of the library inside a virtual environment? You can always do pip install -e . (or even without the -e option) from the repository root to install the package into your current environment. If you want to create a distributable package you can do pip wheel --no-deps . (or python setup.py bdist_wheel) and you'll get a wheel that you can install elsewhere.


Change User Guide website in help window

Codecov Report

Merging #188 (6a9d04a) into master (e7706f8) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #188   +/-   ##
=========================================
  Coverage     41.84%   41.84%
  Complexity      481      481
=========================================
  Files           152      152
  Lines          2521     2521
  Branches        294      294
=========================================
  Hits           1055     1055
  Misses         1409     1409
  Partials         57       57

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/seedu/address/ui/HelpWindow.java
0.00% <ø> (ø)
0.00 <0.00> (ø)

Continue to review full report at Codecov.

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


Accessibility issue with admonition

Some of the admonitions have too low contrast rate (<4) which creates accessibility issues. Please inspect the demo page to have a look.

Maybe you can make appropriate changes to the colors?


L5.2: User table does not allow extra fields, L5.2 core dumps when adding/updating

Laravel Version: 5.2.45
PHP Version: PHP 5.5.9-1ubuntu4.20
Database Driver & Version: mysql  Ver 14.14 Distrib 5.5.53

Description:
L5.2: User table does not allow extra fields, L5.2 core dumps when adding/updating;
I'm working on a webbased program where I need to have a login routine using a simple setup using like the following; admin, superuser, sales
for this i've added two additional columns to the Users table labelled: is_admin (int), role (varchar(20))
when trying to add or update a user now Laravel/PHP crashes and gives an core-dump message in the Apache log file. The 'mass fill' option already has all required fields. No luck getting this working.
Another approach i've tried is following a simple setup of two tables Users (in its original form) and a 'hasOne' table for Roles (with again a minimal setup being) - id, user_id, role, is_admin.
Also now when trying to User::create (new user) or update like below snip-it - no luck again (core-dump)
public function update(AUser $user)
{
    $dbUser = $this->byId( new UserId($user->user_id()) );

    $dbRole = Role::find($user->user_id());
    $dbRole->fill([
        'user_id' => $user->user_id(),
        'role' => $user->role(),
        'is_admin' => $user->is_admin()
    ]);

    $dbUser->fill([
        'name' => $user->name(),
        'password' => bcrypt($user->password()),
        'email' => $user->email()
    ]);
    $dbUser->save();
}

Steps To Reproduce:

Add some fields to the User table
Try to use your 'own' User::create or User::update procedure (instead of the in-build version)

Segmentation faults are often caused by endless recursive calls. You could try and pinpoint the location/pattern with xdebug's xdebug.max_nesting_level.

To continue what Simon said, segmentation faults are very rarely caused by Laravel itself.
Try running it with a different version of PHP or through console(php artisan tinker).
As for nesting level, I think PHP would throw an error saying something like Maximum nesting level of 100 exceeded, I never got a segfault from that. Try disabling xDebug if you have it enabled in your php.ini and check again.

Please upgrade to Laravel 5.3, your version of Laravel is not supported anymore.
Closing this, feel free to ping me in case you could regenerate the issue on a 5.3 instance, I also suggest that you post your question on the forums, we try to keep this repo for bug reporting only.


no-jira - lot of things

wip still fixing up this draft.

added tests for prod issue
removed thread.sleep
modified readme
cleanup tags


Increase the E2E Full timeout to 45min

The Lighthouse jobs are timing out with the current 30min limit. This
increases the timeout to match that used in Submariner.
Signed-off-by: Stephen Kitt<EMAIL_ADDRESS>

Related: https://github.com/submariner-io/lighthouse/pull/736

We’re hitting the timeouts on the 0.12 branch as well (see https://github.com/submariner-io/submariner-operator/actions/runs/2262447911/attempts/1), this should be backported.

We should probably do https://github.com/submariner-io/enhancements/issues/45 instead of this


When clicking sort in an empty column in Workspace, all records disappear

In my genome group, if I click the column header for which no records have information, all the rows in the table disappear.

I still see this behavior. In my genome group, when I sort by disease, all rows disappear.

The problem was that disease field was multi-value, and solr doesn't allow sorting on multi value fields. Dustin has disabled sorting on disease.


Feature/dropped messages report

generate a dropped_messages report for each executable

here are a few initial results for reference:
dropped_msg_reports.zip

The dropped messages numbers look kind of weird (like: expected=51.321, received=42, dropped=9.231)

@christophebedard so for all the callback events the way I am calculating expected is by looking at the Timer callbacks and getting their periods (e.g. 100ms), then getting the run_time by looking at the first timestamp and last timestamp in the series and subtracting them.  with that time and period in seconds you can divide time / period to get expected. for the majority of the nodes they should be the same as whatever the publishing rate is set to for the first 5 sensor_nodes (e.g. 100ms period) and with the experiment running for 5 seconds that gets us to ~50 callbacks per node for most of them with a bit of time either early or late depending on the last timestamp in the trace.

start time of Nth callback at the end - start time of Nth callback at the beginning

the latency graphs are all specific for the FrontLidarDriver and ObjectCollisionEstimator callbacks and are only latency measurements for that specific pipeline.

also i think its pretty neat to see the latency increase during the course of the experiment for the singlethreaded executor. this should be what we expect I think and is a neat effect that goes away when using the multithreaded executor.

@elfenpiff @ralph-lange would love your input here as well on if this is a logical way of calculating latency. seems sort of "hacky" but also sort of ok to me?

with that time and period in seconds you can divide time / period to get expected

it's not a big deal, but just to make the expected number look less "weird" at a glance, could we round it down? Because if the timer period is 100 ms and the runtime is 199 ms, theoretically, that last 99 ms doesn't matter, right?

I guess it works if it's a 1-to-1 pipeline and if there are no dropped messages, so it's pretty fragile

Also I actually drop the last lidar time stamps if the columns don't match up since if there were dropped samples we couldn't get latency measurements anyways. And since the pipeline is 1-1 the time stamps that are left should line up (I think?)

that correctly takes care of the messages that are left in the pipeline, but yeah even if the pipeline is theoretically 1-to-1, you don't know if it actually is: the timestamps might not line up if there are actual dropped messages in between. Example:

message
	timestamp at node 1
	timestamp at node 2
	timestamp at node 3

message 1
	0 s
	1 s
	2 s

message 2
	1 s
	(dropped, never gets here)
	(never gets here)

message 3
	2 s
	3 s
	4 s

The first latency is 2-0=0, which is good, but then you'd have 4-1=3 instead of 4-2=2 because the 2nd message at the beginning of the pipeline would line up with the 3rd message at the end of the pipeline. All subsequent messages would be misaligned (which would result in +1 second to all latencies), and even if you do drop rows from the timestamps at node 1, dropping rows either at the top or the bottom wouldn't help. You'd need to drop the rows corresponding to the dropped messages, somewhere in the middle, but you don't know which rows those are.
I overexplained, but that's what I mean, and yeah we don't currently have the necessary information to do it properly. In any case, this is probably good enough.

converting to draft because I didnt get to finish it today, but I think I've fixed our fragile way of counting dropped messages. We might also be able to use the same logic to figure out a way to count latency as well....but that might be a stretch in the timeframe we have.

@budrus @christophebedard @elfenpiff I've added the behavior jitter plot to the report.  going to add some documentation, review the other reports to make sure everything is still working then we should be good to merge.
latency_and_dropped_messages_summary_report.zip


Set Firefox browser.download preferences

Setting these preferences makes Firefox handle downloads in the same way that Chrome does by default. This means any tests that download a file which are failing in Firefox will work now without needing any other updates. I tested this in a local debug container and download tests are passing.
@rmdaggett @rtabor @rleibovitz89

LGTM


Update device-discovery-faq.md

@roshahno Please implement the suggested changes. Thanks

@mjcaparas Please merge this PR. Thanks


Add GAR paper

Added a new paper on automated paper review using LLM agents.

Thanks for adding this!


OAuth open URL in default browser, set success message and throw desc…

[oauth] Open authorization URL in default browser
[oauth] Allow optionally passing success message to display on browser return page
[oauth] Throw specific errors on failure states

My initial thought is I should have made this an object rather than just a function, having to break the API just to support a custom response message is a shame.

My initial thought is I should have made this an object rather than just a function, having to break the API just to support a custom response message is a shame.

Is it worth working this up a bit more so that there are overloads instead without too much copy paste? I don't mind doing the leg work on that. It would mean you can keep the existing API and we can add a method to pass the message

I think that sounds good.

@stevenleadbeater friendly nudge - would you address the comment you and @kingosticks discussed above?

There was another issue recently where they needed to do something different for android. I can't remember or find it now. My point is we could do with way to pass more options without breaking API (builder pattern maybe?).

Another option besides builder pattern that allows flexible parameters adjustment, is an <method>_with_options alternative method (like here https://github.com/librespot-org/librespot/blob/dev/core/src/spclient.rs#L435). It's a bit simpler and straight forward in comparison to the builder pattern.

Another option besides builder pattern that allows flexible parameters adjustment, is an <method>_with_options alternative method (like here https://github.com/librespot-org/librespot/blob/dev/core/src/spclient.rs#L435). It's a bit simpler and straight forward in comparison to the builder pattern.

But if you add a new arg to that, isn't that still a breaking ApI change?

If the struct with the args doesn't have Default implemented yes, otherwise you could use a struct initialization with ..Default::default() for the remaining args you don't want to use.
But even then people could initialize it directly and that would result in breaking changes... So yeah not fault proof but a very simple alternative and an easy solution to not break existing apis, but going forward not so good.
Just had the "best" case in mind.

Happy with the idea that people who program defensively against breaking changes are catered for. Sounds good, easy is good.


Minor tweaks

When creating a new PR, please do the following and delete this template text:

Reference the issue number if there is one:
Fixes #Issue_Number

The "Fixes #nnn" syntax in the PR description causes
GitHub to automatically close the issue when this PR is merged.

@alfredmyers Nice catch! Thank you for taking the time to fix it.


New API or changes?

With latest update of firmware and app and library getting error -
Has the API changed or does the new firmware from Hitachi require some different mechanism to connect?
python3 example.py
Traceback (most recent call last):
File "/Users/nsankar/Projects/LibJciHitachi/example.py", line 11, in
api.login()
File "/Users/nsankar/Projects/LibJciHitachi/JciHitachi/api.py", line 384, in login
self._peripherals = Peripheral.from_device_names(
File "/Users/nsankar/Projects/LibJciHitachi/JciHitachi/api.py", line 95, in from_device_names
assert device_names is None or len(device_names) == len(peripherals),
AssertionError: Some of device_names are not available from the API.
more example.py
from JciHitachi.api import JciHitachiAPI
Fill out your Jci Hitachi email address, password, and device name.
Login
api = JciHitachiAPI(EMAIL, PASSWORD, DEVICENAME)
api.login()
Check device status
device_status = api.get_status()
print(device_status[DEVICENAME].status)

Exactly, the new firmware is using a new API. I would probably release a new version in the next few days that fits with the new API. BTW you should not paste your credentials here, please remove it as soon as possible. Tks.

Would you mind inviting me to the home group again so that I can test out your device.

 For some reason after this firmware update the connection to the device has been flaky even from the official app. The device is reported as disconnected most of the time. Not sure if there is any issue on hitachi side
Thanks!
—————
Naren Sankar
On Jan 13, 2022, 1:25 AM +0800, Li-Huai (Allan) Lin @.***>, wrote:

Would you mind inviting me to the home group again so that I can test out your device.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

It seemed that the firmware update this time also unbound all built in sub-services of the Hitachi app such as Google home and home group linking, so now I'm not in the home group (I saw I was kicked from the group yesterday).

Closing as the new version was released.


t_dyes only works with tubs, not with t_dye_vat

If u change the type of any ítem to t_dye_vat, u Will be not able to dye it with dyes, the only thing u can dye with dyes are tubs.
gms can dye any t_dye_vat item, players can´t
https://youtu.be/QsbLHCVPs4Y
https://youtu.be/6zIrs_Y6yW4

https://youtu.be/QsbLHCVPs4Y

This is because you haven't set OF_DyeType flag in sphere.ini to OptionFlags;
Here is the information in sphere ini;
// OF_DyeType					00008000 // Allow use i_dye on all items with t_dye_vat typedef instead only on i_dye_tub itemdef
You just need to add 08000 to OptionFlags to active it.

right

If this solve your issue, please close the topic, so developers knows there is no issue left to check.


When typing a message to someone including an isolated @ fails

https://www.bsd-unix.net/seitz/screenshots/2015-05-18_14-07-25.png

fixed here:
https://github.com/rawdigits/wee-slack/commit/32b784d7ef362b7866e174a578fc27010c06bddb#diff-67e177ac444a14d6bcd7be6306ab4a20R473


typings: createInstance should return constructor function

Hi, I believe the typescript signature of createInstance should be:
export function createInstance<T>(defaultProps?: AsyncProps<T>): new() => Async<T>

I have tested this locally, and I'm happy to create a pull request if needed.

Yes, that looks good. Better than what we have now at least. Unfortunately it doesn't work with the helper components:

Please create a PR. Would be great if you can fix the static members as well. I've struggled with typing these in the past and I'm still not comfortable with creating types for that kind of thing.

It's not about the "unknown" by the way, if I provide a promiseFn that resolves to a string it's still the same error (just with Async<string>).

@harbeedev Will you create a pull request? Let's ignore the subcomponents for now, hopefully somebody will come up with a fix for that.

Fixed in v7.0.4


cage crashes with -r rotate the output 90 degrees clockwise

cage version 0.1.5
there is no option -r ?? - not cool folks!
However, here is my solution for anyone who relies on changing the orientation of the screen:
services.cage = {
enable = true;
user = "kassa";
program = "${pkgs.writeScriptBin "start-cage-app" ''
#!/usr/bin/env bash
wlr-randr --output HDMI-A-1 --transform 90 # Adjust command as needed
exec ${(pkgs.chromium).outPath}/bin/chromium
''}/bin/start-cage-app";
};

Indeed -r option has been removed from Cage as wlr output management protocol is now supported and allows more configurations e.g. you may apply two different transform for two outputs. So, you have to use a tool which know how to deal with this wlroots protocol such as kanshi or wlr-randr.
Apart from that, do you really observe a crash using -r option? Cage should just return an expected error for an unknown argument.

Hi - thanks for replying. Well, it seemed to me like a crash using it as a
service in a NixOS configuration - no output where provided to any
logging (e.g. journalctl) - I only found the "unexpected option" message
after installing Cage and running it manually.
However - I can't find any alternative other than using wlr-randr. How can
one use wlr output management as an option for Cage?
Am Mo., 11. März 2024 um 14:29 Uhr schrieb Jonathan GUILLOT <
@.***>:

Indeed -r option has been removed from Cage as wlr output management
https://wayland.app/protocols/wlr-output-management-unstable-v1
protocol is now supported and allows more configurations e.g. you may apply
two different transform for two outputs. So, you have to use a tool which
know how to deal with this wlroots protocol such as kanshi or wlr-randr.
Apart from that, do you really observe a crash using -r option? Cage
should just return an expected error for an unknown argument.
—
Reply to this email directly, view it on GitHub
https://github.com/cage-kiosk/cage/issues/321#issuecomment-1988446492,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIEL557HR4TZKEXNZMQAEXLYXWWVNAVCNFSM6AAAAABEOD5NJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBYGQ2DMNBZGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Ralph Eichelberger, Ing.
6645 Vorderhornbach 122
Mobil: +43 677 620 321 85

However - I can't find any alternative other than using wlr-randr.

wlr-randr is an easy way to go for your purpose. Keep it like this.

no output where provided to any logging

I don't know how NixOS work but when using -r option, Cage exits with error 1 and print some details in standard output.

OK - works for me. However, I need to get rid of the title bar of my
application - it should just run in fullscreen without any title bar and
buttons - what can I do to accomplish that?
Am Mo., 11. März 2024 um 15:20 Uhr schrieb Jonathan GUILLOT <
@.***>:

However - I can't find any alternative other than using wlr-randr.
wlr-randr is an easy way to go for your purpose. Keep it like this.
no output where provided to any logging
I don't know how NixOS work but when using -r option, Cage exits with
error 1 and print some details in standard output.
—
Reply to this email directly, view it on GitHub
https://github.com/cage-kiosk/cage/issues/321#issuecomment-1988556953,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIEL55ZTWMQVPWIHXAC3IPDYXW4S3AVCNFSM6AAAAABEOD5NJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBYGU2TMOJVGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Ralph Eichelberger, Ing.
6645 Vorderhornbach 122
Mobil: +43 677 620 321 85

The -d flag requests clients to not draw decorations.

Or your application may have a fullscreen option which can be passed as argument on the command line.


MFA should not be required parameter

When running:
$ perun create-stack my-stack-name path/to/template --region us-east-1 --profile some-profile

I got:
 INFO: Configuration file from the following location will be used: /Users/myuser/.config/perun/main.yaml
ERROR: There is no mfa_serial for the profile some-profile-long-term

If you don't specify --mfa the check for mfa_serial should be probably omitted. It is up to users if they are going to use mfa or not.
Additionally if something is throwing an error I would expect the whole command to fail, but in this case the stack was created.

Additionally if something is throwing an error I would expect the whole command to fail, but in this case the stack was created.

THIS. :wink:

Do we want to force the user to type '--mfa' always when they use MFA Authentication?

closed by https://github.com/Appliscale/perun/pull/101


Fixed JSDoc error in RND.shuffle param

This PR (delete as applicable)

Updates the Documentation

Describe the changes below:
The JSDoc was generating it as an array of arrays as opposed to a one dimensional array.

👍


laravel 4 form multiple model binding

i've been try to binding one model with relationship, can i binding that forms for multiple relationships model ?
sorry for bad english. thanks

Haven't tried this myself but I will try and look into it soon!


Add health check mechanism for integrations which can be used to check if integration is up and running or not

The problem faced currently?
Mission control starts integrations but doesn't check if it really started. Because of this all the user may get an error when he clicks to Open integration console button.
How can we solve it?
Add a health field in the config which can be used to check if the integration is up and running or not. Mission control can poll this periodically till a status code 200 is received signifying that the integration has started successfully. We can also include another status code (eg. 500) which signifies the integration could not be initialised and isn't functional anymore.

If you want this feature to be implemented, give it a thumbs up reaction, so that we can determine which features are important to you.
👍

Done. Coming in v0.19.3


cartopy feature download

🚀 Pull Request
Description
This PR fixes the broken ABF fileformat documentation URL link.
Closes #4302

Consult Iris pull request check list

Looks like the Natural Earth server is having issues again 😞

Well... this PR took an unexpected diversion :rofl:

@bjlittle maybe update the title?  I’m not sure I’m qualified to review this anymore.

This is actually a pretty handy little general utility, and whatsmore, as with cartopy it won't be bundled with iris when it is packaged.

I know that populating the cartopy cache is a pain-point for many users, particularly when pre-caching for offline usage, or when attempting to develop behind a firewall with no internet access e.g., on a secure HPC, so this may somewhat help ease the burden i.e., you can use the utility to download a cartopy cache, then lift and shift it to your installation, or be confident that you have all the resource you need before working offline.

I confused here: if the script isn't bundled with Iris, how do the users take advantage of it?

@rcomer I've followed the same pattern as cartopy, as a starter i.e., cartopy/tools/feature_download.py is not bundled within cartopy as a package. So really, it's a development tool.
If we're serious about packaging this with iris, then we could easily make an entry-point for it, then it would indeed be accessible to users via the command line on install.
I didn't want to do that work up front, only for people to object... I rather discuss it, have agreement, then do it.

So since we're on topic... what would you prefer?

@bjlittle my opinion is to punt that question to a new Issue: the scope on this PR has ~creeped~ swerved far enough, and fixing the CI should be the first priority!

@bjlittle my opinion is to punt that question to a new Issue: the scope on this PR has creeped swerved far enough, and fixing the CI should be the first priority!

That's way better than what I was about to write. PR's that solve multiple problems are an anti-pattern, and as @rcomer eludes, this isn't exactly a small add-on.

Totally happy to follow this up with a GH discussion :+1:
Anyone fancy reviewing and merging?
I'm keen to unblock CI

Note that https://github.com/SciTools/cartopy/pull/1602 renames tools/feature_download.py to be tools/cartopy_feature_download.py and also makes it a pucker command line script (finally) :partying_face:
That PR was merged in May 2021 and didn't make the cut for the April release of cartopy 0.19.0.post1... but it will be available in the next release of cartopy, as will https://github.com/SciTools/cartopy/pull/1833

@rcomer @trexfeathers
I'm good with this as it is.  I reviewed the code and its CLI and I think it works OK.
I do also agree that including this as an installed script is another step, and we don't want to get into that yet

assuming that is what everyone else meant by "punt that question to a new Issue" / "PR's that solve multiple problems"

Going to merge unless someone objects...

Once this PR is merge, I'll make an associated issue to discuss follow-up work.
This is all in a state of flux, and we may insist on a minimum pin for cartopy within iris moving forwards to make our lives easier :thinking: ... but that's for later to decide

Oh look 👀 https://github.com/conda-forge/cartopy-feedstock/pull/116

That's only a fix to 0.19.0.post1, and not older versions of cartopy

@bjlittle but it would get our CI moving?

@jamesp ... and finally, this is good to go :crossed_fingers:


[SPARK-17546] [DEPLOY] start-* scripts should use hostname -f

What changes were proposed in this pull request?
Call hostname -f to get fully qualified host name
How was this patch tested?
Jenkins tests of course, but also verified output of command on OS X and Linux

Test build #65532 has started for PR 15129 at commit 5a8fb58.

Test build #65532 has finished for PR 15129 at commit 5a8fb58.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65532/
Test PASSed.

Merged build finished. Test PASSed.

LGTM.

Merged to master/2.0


Rarity generation

Is there a way to only pull one rare or super rare image from a random layer when compiling a rare or super rare image?

@EvilShaggz you mean that for a rare or super rare you would only get one part of the actual rare content and everything else remains the 'original'?
Currently this doesn't work. You can add images of your originals into the rare/super rare folder which allows this permutation to occur, but doesn't give you a guarantee that exactly one rare element will be added (or any for that matter).
But something that can certainly be introduced with appropriate code adjustments.

I was thinking some sort of function like
Adding an element id number 1-7 as i have 7 layers
Const raritylayer (raritylayer=(Get rarity)If rarity = rare,super rare get randnum (elementrange) else exit
But i assume this will meant modifying how the image is built also
Ps I literally started looking at code yesterday so please for give lack of knowledge


Support for React v15

React v15 has been released, and currently this library has compatibility issues with it. Since react-addons-pure-render-mixin is an external dependency and version constrained to ^0.14.0, which has a peer-dependency of<EMAIL_ADDRESS>Since the mixin is fairly simple, I'd suggest either removing it from externals in webpack so it gets bundled with the release (like lodash.throttle currently is), or add it as a peer-dependency instead so the responsibility to install a compatible version falls on the user, as with react and react-dom (why is react-dom a peer dependency btw?)
I can submit a pull request, just want to check your thoughts first.

Hi @simon-lifelike thanks for the issue.
I have just made some changes which are up in PR https://github.com/mderrick/react-html5video/pull/25. I've been long thinking about removing this pure-render-mixin and now you have given me good reason to do so. I don't think I needed it at all really so instead I have just made sure all the video controls have a shouldComponentUpdate method as it is these that would find themselves being rendered extremely often.
I've also gone and removed the dependency on react-dom which was just simply a mistake as it needn't be there at all. Let me know if this PR solves your issue.

Fixed in release https://github.com/mderrick/react-html5video/tree/1.2.7


Failed on the first time with a simple example

Just running a docker node and run a simple example here https://polkadot.js.org/docs/api/start/create
const { ApiPromise, WsProvider } = require('@polkadot/api');

const wsProvider = new WsProvider('ws://<IP_ADDRESS>:9944');

(async () => {
  const api = await ApiPromise.create({ provider: wsProvider });

  // Do something
  console.log(api.genesisHash.toHex());
})();

Got tons of strange errors :(
2021-05-27 15:08:27        REGISTRY: Unable to resolve type ChainId, it will fail on construction
2021-05-27 15:08:27        REGISTRY: Unable to resolve type DepositNonce, it will fail on construction
2021-05-27 15:08:27        REGISTRY: Unable to resolve type ResourceId, it will fail on construction
2021-05-27 15:08:27        API/INIT: Error: FATAL: Unable to initialize the API: createType(ChainId):: Cannot construct unknown type ChainId

That is a customized node. Which means types have been added on the Rust side. There is no type reflection capabilities in the metadata yet.
So this is not a simple example, but rather one where the node has been customized. Please see the devotions on injecting additional types (that does not exist on Substrate master) into your JS API so it knows how to handle it.
You will need to inject it each of the unknown types such as ChainId….

Ok, so if I have a local edgeware node like this https://github.com/hicommonwealth/edgeware-contracts-tutorials/blob/master/4/setting-up-a-local-node.md
How can I make this code snippet work? Or it simply doesn't support.

Edgeware publishes their own type definitions on NPM that is to be used with the API to inject the types for that type of node - https://github.com/hicommonwealth/edgeware-node-types


hs-boot exception

I see an error with hs-boot again unfortunately, but it seems on ghci's end. if the .hs file (where a corresponding hs-boot, without errors, exists) contains error(s), i see the following output from ghci:

Failed, modules loaded: Language.Haskell.Brittany.Backend (dist/build/Language/Haskell/Brittany/Backend.o), Language.Haskell.Brittany.BackendUtils (dist/build/Language/Haskell/Brittany/BackendUtils.o), Language.Haskell.Brittany.Config (dist/build/Language/Haskell/Brittany/Config.o), Language.Haskell.Brittany.Config.Types (dist/build/Language/Haskell/Brittany/Config/Types.o), Language.Haskell.Brittany.ExactPrintUtils (dist/build/Language/Haskell/Brittany/ExactPrintUtils.o), Language.Haskell.Brittany.LayouterBasics (dist/build/Language/Haskell/Brittany/LayouterBasics.o), Language.Haskell.Brittany.Layouters.Decl (dist/build/Language/Haskell/Brittany/Layouters/Decl.o), *** Exception: expectJust showModule
CallStack (from HasCallStack):
error, called at compiler/utils/Maybes.hs:48:27 in ghc:Maybes

And consequently reloading does not work, because modules (especially INTERNAL_GHCID) are not reloaded, which then makes ghcid hang. This all happens deterministically.
ghc-8.0.2
Now this seems mostly like a ghc bug, so my question: have you seen this/reported it already; and can you think of a workaround?

I haven't seen it, and it does seem like a pretty bad GHCi bug. I suggest you report it upstream at the GHC trac (and post the link here) - they may have a workaround. Note that GHCi seems pretty buggy in general, and I often find regressions between versions - although usually not as obvious and clear cut as above.

https://ghc.haskell.org/trac/ghc/ticket/13591#ticket

The fix i wrote has made it into GHC-8.2.1, and i can confirm that ghcid now works as desired for hs-boot.


feat(files): use mocha 6's way of resolving files

Use mocha 6's implementation to resolving files.
This adds support for exclude, spec, files as well as positional arguments.
Fixes #1428
Note: #1511 should be merged first

This is now ready for review.
@simondel I'm using https://github.com/mochajs/mocha/blob/master/lib/cli/run-helpers.js#L132 This is a yet undocumented API. Do you think we should work around this?


How I can find tab of some extension?

Type: Feature Request
Hello,
I've been working with VS Code for a long time, I really like this program and it's its free distribution that makes it first on my list! Thank you so much for your work and this product!
Regarding the problem: I installed the "Todo Tree" extension, it added a tab to the sidebar, and after several years I lost that tab and cannot recover it.
Perhaps somewhere there are instructions on how to return the extension tabs, but reinstalling the extension did not help me.
Suggestion: It would be great to have a search for all extension tabs in the sidebar context menu or in main menu.
Best regards, @AndreyChursin
VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:14:24.611Z)
OS version: Darwin x64 22.6.0
Modes:

@sandy081 no

May be you would have moved it. Try resetting the locations - F1 > View: Reset View Locations.

Maybe, but it will reset all my view preferences.
This issue mostly "Feature Request"...

You can also find the view from the command pallette and pin it or move it.
F1 > Open View... > Name of the view


only run macOS job on merge

They are slow in being picked up by github runner and should be very similar to the ubuntu one.

kinda sucks we have to duplicate the job definition, but lets take it for now; we can always improve that later.

Yep, I first tried with adding some conditions and not duplicating the jobs, but it still created the job so we still got the delay in runner pickup.


[BUG]require("auto-session").get_session_files() does not return sessions with names ending in 'x'.

Describe the bug
I attempted to save /examples/llvm-project/libcxx as a session, and indeed, it generated a %home%user%examples%llvm-project%libcxx.vim file under /.local/share/nvim/sessions/.
However, when I tried to use require("auto-session").get_root_dir() to retrieve the sessions, I found that it was not listed.
To Reproduce
Steps to reproduce the behavior:

Navigate into a directory ending with 'x'
Save session
Invoke require("auto-session").get_root_dir()

Expected behavior
require("auto-session").get_root_dir() returns the correct result.
Baseline (please complete the following information):

vim.o.sessionoptions="blank,buffers,curdir,folds,help,tabpages,winsize,winpos,terminal,localoptions"
OS: WSL2 under Windows 11 23H2 22631.3593, ArchWSL
Neovim version: v0.9.5
URL to your current config:

Additional context
I reviewed the source code, and it seems the issue is caused by string.find(item, "x.vim$").
function AutoSession.get_session_files()
  local files = {}
  local sessions_dir = AutoSession.get_root_dir()

  if not vim.fn.isdirectory(sessions_dir) then
    return files
  end

  local entries = vim.fn.readdir(sessions_dir, function(item)
    return vim.fn.isdirectory(item) == 0 and not string.find(item, "x.vim$")
  end)

  return vim.tbl_map(function(entry)
    return { display_name = AutoSession.format_file_name(entry), path = entry }
  end, entries)
end

While I'm not entirely certain about the role of the x.vim file, it seems there might be a more effective approach to implement this functionality.

Here's some context for the x.vim functionality.
https://github.com/rmagatti/auto-session/issues/74

Here's some context for the x.vim functionality. #74

This appears to require designing an algorithm to check if each file ending with .x.vim is an extra data file for a particular session file.
However, this approach does not resolve the situation where both session A and session Ax exist simultaneously.
Do you have any better ideas?

What about:

For each file in the sessions dir that matches *x.vim

check and see if there's a *.vim

if there isn't, assume it's a session file
if there is, check the x.vim file to see if the first line contains 'SessionLoad'?

or maybe more simply just check any *x.vim file to see if the first line contains 'SessionLoad'?
there's risk that that breaks if the implementation of mks changes but that risk exists in both cases (albeit it would have less impact in the first solution)

@cameronr that sounds like it could work well! That risk is acceptable as we're relying on Neovim's internal functionality 👍


[COD-571] fix: refactored API calls to make them tolerate network failures and retry

https://snyksec.atlassian.net/browse/COD-571

[ ] Ready for review
[ ] Linked to Jira ticket

What does this PR do?
Where should the reviewer start?
How should this be manually tested?
Any background context you want to provide?
Screenshots
Additional questions

tests are adjusted and added a test for network failure

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


MAV_CMD_DO_SET_SERVO using dronekit

I have to use MAV_CMD_DO_SET_SERVO mavlink command in dronekit python for controlling a fixed wing UAV.  Is there any syntax available.  I tried channeloverride and its working. since i want to put my own autopilot in a companion computer and many advised not to use channeloverride i want to use MAV_CMD_DO_SET_SERVO.

If you're going to use DK-Python then you'll have to use the channel override - I'm pretty sure we don't provide any other mechanism for direct servo control.
Not sure what you mean by  "i want to put my own autopilot in a companion computer". That is something you should discuss in the gitter channel - depending on what you want to do this probably not a good use case for DroneKit.


Fix/source tweaks tweaks

Couple of changes here required for supporting sources in the docs site (https://github.com/fishtown-analytics/dbt-docs/pull/13). These changes are all intended to  include source tables in catalog generation.

@beckjake can you revisit this last commit (fix_tests) when you get a second? I'm not sure it's super controversial, but wanted to check before merging.
The problem I hit was that we assumed a single catalog entry would map to a single node in the manifest. As it turns out, we're using sources to point to seeds, so the entry for the seed table would actually be represented by both a seed and a source.
I think this all shakes out to be fine, and it's only a problem if two different catalog entries map to the same node. We're still accounting for that case, but still, let me know if you think there's some better way of handling this.

lgtm! 👍


(maint) Bumping inifile dependency from > 2.0.0 to > 3.0.0

Pull Request (PR) description
Bump dependency of the puppetlabs/inifile module to handle the newer versions without the PMT tool throwing dependency issues
This Pull Request (PR) fixes the following issues:
Fixes #172
Task list:

[x] Bump dependency in metadata.json file. ( .fixtures.yml is pointed to the lastest master branch so no bumping needed in here )

The build failure will happen until #169 is fixed.


How do you get cartesian coordinates?

I'm trying to use this library, but I need to deal with cartesian coordinates (particularly of Beziers).
How do I get cartesian coordinates in this library?

TinySpline uses cartesian coordinates by default. You can find the points in tsBSpline#ctrlp. Given a Bezier curve in 2D, the points are arranged as follows: [x0, y0, x1, y1, x2, y2, ..., xn, yn]. Given a Bezier curve in 3D, the points are arranged as: [x0, y0, z0, x1, y1, z1, x2, y2, z2, ..., xn, yn, zn]. The C++ wrapper provides the method TsBSpline#ctrlp, which simply returns the field mentioned above.