DotnetTool package type cannot be installed by Guardian

When attempting to install the package via Nuget, we get the following error:
Warning: Failed to install from source https://pkgs.dev.azure.com/secdevtools/_packaging/SecDevTools/nuget/v3/index.json with exception NuGet.Packaging.Core.PackagingException: Package 'Microsoft.Sbom.DotNetTool 0.2.5' has a package type 'DotnetTool' that is not supported by project 'C:\Repos\actions-runner_work_msdo\packages\nuget'.
Can another package be produced that either leaves the package type unset, or specifies it as 'Dependency'? More details here: https://learn.microsoft.com/en-us/nuget/create-packages/set-package-type?tabs=dotnet

@chrisnielsen-MS this sounds like an error on your project. Does your project type support dotnet tools? If not, you may be better off using the nuget package instead. I am closing this ticket, if you have any questions please reopen.

@aasim the other nuget package (Microsoft.Sbom.Tool) is framework-dependent and so is also unsuitable for use in Guardian. We need a package that is self-contained but also is not of type 'DotnetTool'.


.github/PULL_REQUEST_TEMPLATE.md: init

Initialises a pull request template that can be used by Github, due to https://github.com/NixOS/nixos-hardware/pull/488#issuecomment-1292908274

Thanks!

bors merge


Migration generates tables in wrong order

When generating the first migration the create table statements can not run, because they are in the wrong order.
Example:
CREATE TABLE device_location (
	id serial PRIMARY KEY,
	since timestamptz,
	device_id bigint REFERENCES devices(id),
	customer_id bigint REFERENCES customers(id)
);

CREATE TABLE devices (
	id serial PRIMARY KEY,
	serial text
);

Table devices must be created first. As a fix I can just edit the generated file.
Another (maybe separate) issue is that circular dependencies between tables do not work. That could be solved by first creating the tables and then adding the columns separately.

Thanks for reporting this!
I'd swear the order thing was fixed long ago, but I'll take a look at it with the example you provided. Will also take a look at the circular dependency thing while I'm at it.

Can you post the code for these two models? Maybe the problem is in the way the relationships are declared. Thanks.

That's my complete model.
//go:generate kallax gen

type Controller struct {
	kallax.Model `table:"controllers"`
	ID           int64   `pk:"autoincr"`
	Device       *Device `fk:"device_id,inverse"`
	Serial       string
}

type Device struct {
	kallax.Model `table:"devices"`
	ID           int64 `pk:"autoincr"`
	Serial string
	Type   string
}

type DeviceLocation struct {
	kallax.Model `table:"device_location"`
	ID           int64 `pk:"autoincr"`
	Since        time.Time
	Device       Device   `fk:"device_id,inverse"`
	Customer     Customer `fk:"customer_id,inverse"`
}

type Data struct {
	kallax.Model `table:"data"`
	ID           int64      `pk:"autoincr"`
	Device       Device     `fk:"device_id,inverse"`
	Controller   Controller `fk:"controller_id,inverse"`
	Data         map[string]interface{}
}

type Customer struct {
	kallax.Model `table:"customers"`
	ID           int64 `pk:"autoincr"`
	Name         string
	CustomerNr   string
}

Generating the following migration:
BEGIN;

CREATE TABLE data (
	id serial PRIMARY KEY,
	device_id bigint REFERENCES devices(id),
	controller_id bigint REFERENCES controllers(id),
	data jsonb
);

CREATE TABLE controllers (
	id serial PRIMARY KEY,
	device_id bigint REFERENCES devices(id),
	serial text
);

CREATE TABLE device_location (
	id serial PRIMARY KEY,
	since timestamptz,
	device_id bigint REFERENCES devices(id),
	customer_id bigint REFERENCES customers(id)
);

CREATE TABLE devices (
	id serial PRIMARY KEY,
	serial text,
	type text
);

CREATE TABLE customers (
	id serial PRIMARY KEY,
	name text,
	customer_nr text
);

CREATE TABLE users (
	id uuid PRIMARY KEY,
	username text,
	email text,
	password text
);

COMMIT;

Yep, the model is correct. So there's a bug in there. We'll take a look as soon as we can.


Upgrade salsa

The only code change is that Salsa now requires the Db to implement Clone to create "lightweight" snapshots.

it looks like the fuzz build failed on this PR's CI run... should we make that a required check so that automerge fails if the check fails?


"Settings" page displayed not in specified language in url

I specified the language code "zh-cn" in url of "Settings" page as below:
http://<IP_ADDRESS>:9991/zh-cn/#settings
but it still shows a English UI.
While I enter the page from the setting menu, it has no such problem.

Hmm, interesting; I see the translation tags in the handlebars templates, but I don't see some of the strings like "Your organization's name" in the translations.json files generated by manage.py makemessages.  Any ideas @umairwaheed?

Checking it

@timabbott it seems that "Your organization's name" was missed, it is not marked for translation.

so it seems the problem is that the translations are loaded asynchronously while we don't wait for them to load completely.

@umairwaheed can you explain a bit more what you mean?  Would it make sense to move the translations to being loaded more synchronously, or are there other reasonable solutions?

@timabbott we need to make sure that before we render any templates all the translation resources are loaded. It seems that i18next doesn't support synchronous loading of resources so we will have to figure out an asynchronous solution.

The fix for this was merged just now; thanks @Jianchun1 for reporting and @umairwaheed for fixing!

NP!


Add VMI creation timestamp metric

What this PR does / why we need it:
Add kubevirt_vmi_creation_timestamp_seconds to the exposed metrics.
In this PR, a refactor has been made since currently, vm, vmi and vmim collectors have many duplicated code
and follow the same logic.
Hence, the logic is wrapped in a interface, and a generic struct
is introduced to prevent code duplication.
Also, vmi metrics now are auto-generated.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

Add VMI creation timestamp metric

/cc @iholder101 @sradco

/cc @rthallisey

@machadovilaca Hi, Please have a look.

/hold
I want to put a hold on this because: A timestamp is no unit which prometheus understands. Please read https://prometheus.io/docs/concepts/metric_types/ for the context. No metric type fits which means no reasonable prometheus operatons can be done, or at least only with a lot of extra care. I think we already moved away too much from best practices in PRs like https://github.com/kubevirt/kubevirt/pull/5343. They already make us harder to understand and use.

Hi @rmohr, @fossedihelm ,@rthallisey , Im not sure if there is still a confusion here, so I'll add a clarification just to make sure we are aligned.
timestamp is not the unit. seconds is the unit.
We must have the timestamp, since the metric value should is the epoch timestamp of the VMI creation date and this is the Prometheus convention.
The timestamp implementation allows us to check the VMI age, even if it  has been more than the time of Prometheus retention time(For example, the retention is 2 weeks and the VMI was created 3 weeks ago).
It should be seconds since this is Prometheus units guidelines.
By using the (time()  - the metric) you will get the time that passed since the VMI was created in seconds.

@machadovilaca Can you please have a look?

@sradco could you outline why Prometheus us the right place to store this info? Without more context it does not look like this is monitoring-relevant information.

FYI: this isn't the first time this issue had been brought up. It was already discussed here https://github.com/kubevirt/kubevirt/pull/7918#issuecomment-1196409004 (which eventually led me to write this design proposal: https://github.com/kubevirt/community/pull/189).

It normally does not make sense to safe timestamps or passing seconds. You would for a.g. unhealthy tracking just have a metric which flips from 0 to 1. And an alert could just check for how long it is unhealthy based on the time series record. If we really merged such a metric already we have to remove it imo.

It normally does not make sense to safe timestamps or passing seconds. You would for instance for unhealthy tracking just have a metric which flips from 0 to 1. And an alert could just check for how long it is unhealthy based on the time series record. If we really merged such a metric already we have to remove it imo. Point in time and duration is an inherent property of the time series. Further everything which goes beyond the retention period of the top level metrics storage (e.g. Thanos, prom on prom, ...) is out of scope of the monitoring part.

@rmohr Hi. So IIUC you are suggesting to implement the unhealthy calculation internally, and export the binary indication to that via a metric, also to implement the alert based on how long this binary metric is true. Is that correct?
And if we need the save metrics for long-term periods, for example to have an ability to monitor an unhealthy state for 6 consecutive months , we should not abuse Prometheus for that (by saving timestamps on each sample)?

@rmohr Hi. So IIUC you are suggesting to implement the unhealthy calculation internally, and export the binary indication to that via a metric, also to implement the alert based on how long this binary metric is true. Is that correct?

Hm, the unhealthy metrics was just an example. What I mostly meant, is collecting metrics like is done here for phases on VMIs: https://github.com/kubevirt/kubevirt/blob/main/pkg/monitoring/perfscale/vmi-phase-transitions.go.
I also sense there a huge overlap and I would ask to re-evaluate the exposure of some of the VM metrics.
Having something like an unhealthy metric may sound tempting, but it is not clear what unhealthy means. Like if a VM is not ready for 2 hours, what does  that mean? Maybe there is maintenance on the webserver going on, inside that VM and it is supposed to not get service traffic.

And if we need the save metrics for long-term periods, for example to have an ability to monitor an unhealthy state for 6 consecutive months , we should not abuse Prometheus for that (by saving timestamps on each sample)?

Yes, that is definitely not a prometheus task. You can read that out of VMs and VMIs.

@rmohr Hi. So IIUC you are suggesting to implement the unhealthy calculation internally, and export the binary indication to that via a metric, also to implement the alert based on how long this binary metric is true. Is that correct?

Hm, the unhealthy metrics was just an example. What I mostly meant, is collecting metrics like is done here for phases on VMIs: https://github.com/kubevirt/kubevirt/blob/main/pkg/monitoring/perfscale/vmi-phase-transitions.go.
I also sense there a huge overlap and I would ask to re-evaluate the exposure of some of the VM metrics.

I agree that we some overlap with the kubevirt_vmi_phase_count metric, but you can see here Pod Lifecycle that the Phases and Conditions are not the same. The conditions on the VMI level is important for us.
The kubevirt_vmi_phase_count metric doesn't cover all the VMs and VMIs , it is aggregated and we can't get all the information that we need from it.
The last_transition metrics provides us a broader use.
We use it to alert on the specific VM/VMI, report uptime for the specific VM, downtime and unplanned downtime, it can be used to identify VMs that are not used and to identify a bigger issue if we see that more than X VMs are in an "unhealthy" state for  a specific time period.

Having something like an unhealthy metric may sound tempting, but it is not clear what unhealthy means. Like if a VM is not ready for 2 hours, what does that mean? Maybe there is maintenance on the webserver going on, inside that VM and it is supposed to not get service traffic.

The metrics are not called unhealthy, but the alerts that are based on them are determining if its unhealthy based on the time it is in that condition. These are highly important metrics for sysadmins for doing actions like cleanup.

And if we need the save metrics for long-term periods, for example to have an ability to monitor an unhealthy state for 6 consecutive months , we should not abuse Prometheus for that (by saving timestamps on each sample)?

I disagree that this is not a correct way of doing it as there are Prometheus metrics that are of type timestamp_seconds that are exactly doing the same. There is the time() function that allows use to calculate the number of seconds that passed since the the last transition time and graph it (time()-metric_timestamp_seconds).

Yes, that is definitely not a prometheus task. You can read that out of VMs and VMIs.

What do you mean? How will you be able to do calculations and create reports by reading it out of the VMs and VMIs?
And specifically about this PR, I think that we need an age metric for a VM not VMI.

Yes, that is definitely not a prometheus task. You can read that out of VMs and VMIs.

What do you mean? How will you be able to do calculations and create reports by reading it out of the VMs and VMIs?
And specifically about this PR, I think that we need an age metric for a VM not VMI.

You can fetch the VM object directly and investigate it. Prometheus is a monitoring tool for health, not for creating another nice-dashboard api for what was happening in the last 6 months in the cluster. You can still expose this information for prometheus, exactly as you chose here, but I don't see this as something which should go into kubevirt core.
We can discuss about an additional vm_created metric, but it should not be a timestamp. It should be easy summable values without special knowledge to answer questions like "did an unusual amount of VMs get created?", "do the VMIs go to created but an unusual big amount, compared to max capacity stays in pending"?
A question like "did this VM already exist 5 months ago" is not something which monitoring should be concerned with. It has no cluster-health value.

The last_transition metrics provides us a broader use.
We use it to show this information for the specific VM/VMI so that the sysadmin can inspect if there are unhealthy VMIs, report uptime for the specific VM, downtime and unplanned downtime, it can be used to identify VMs that are not used and to identify a bigger issue if we see that more than X VMs are in an "unhealthy" state for a specific time period.

I am not sure how a cluster admin should know what unhealthy means. Like again, if a VM is not ready, that does not mean that it is not healthy. Again like above, we can discuss about generic metrics which indicate readiness, but a timestamp is definitely the last resort and not necessary in this context.
I also want to point out that an "unhealthy" alert as part of kubevirt core, based on what you describe, would probably not fit into kubevirt core. We can not say here what unhealthy or healthy is.

@sradco I would suggest that you come up with a design doc, mentioning all the points which you perceive as friction points which are blocking you reaching your goals. From there we can see if  we can find solutions. Otherwise we will probably continue having this discussion again, and my intention is not to block you from reaching your goals.

@rmohr  A design doc for what? The age metric or are you referring to the last transition metrics?

@rmohr A design doc for what? The age metric or are you referring to the last transition metrics?

A design doc on what your goals are, like despite being not really about general health monitoring in the sense to  detect potentially neet-to-investigate-abnormities you want info like:

did this VM exist 2 months ago already over prometheus metrics
why you having the info that a vm became ready 3 months ago is more important than streight forward timeseries operations (yes I know  you can do all kind of tricks with queries) to find if an overall abnormal behaviour is happening.

And why you want to create admin alerts in kubevirt for user-centric workload questions like:

a user deploys a VM with apache and has a readiness probe defined. The user decides to stop apache to take it out of service traffic, which makes the ready condition go to false. Why should an admin get an alert?

Like I only see a fraction of your overall goals in the PRs (just the code), not the final vision. Whatever your final vision is, there may be better ways to achieve it. If there is consensus on that, we can see in the  design goals on how you can achieve certain goals best without friction like in this PR.

Yes, that is definitely not a prometheus task. You can read that out of VMs and VMIs.

What do you mean? How will you be able to do calculations and create reports by reading it out of the VMs and VMIs?
And specifically about this PR, I think that we need an age metric for a VM not VMI.

You can fetch the VM object directly and investigate it. Prometheus is a monitoring tool for health, not for creating another nice-dashboard api for what was happening in the last 6 months in the cluster. You can still expose this information for prometheus, exactly as you chose here, but I don't see this as something which should go into kubevirt core.

There is no way to do this one by one. Its a sysadmin nightmare. Prometheus is exactly the tool to help them see the overall VM and VMIs conditions so that they can split and dice their data and do actions based on them.
Doing this is in an aggregated way will not allow them to address the individual VMs and VMIs.
You have metrics for individual pods, containers, node and more. Way do you believe you don't need this for individual VMs and VMIs?

We can discuss about an additional vm_created metric, but it should not be a timestamp. It should be easy summable values without special knowledge to answer questions like "did an unusual amount of VMs get created?", "do the VMIs go to created but an unusual big amount, compared to max capacity stays in pending"?

These are not the questions that the last_transition metrics are trying to answer. They answer  questions like:
"How long is the VM/VMI in this condition?"

If a VMI is in pending for a month this means its consuming resources and should consider to deleted it.
If its running for a month but CPU and memory statistics are almost static and very low this might also indicate a stale VM.

As for the age metric, I think we should not add an age metrics for a VMI.
I asked to get this story closed.

A question like "did this VM already exist 5 months ago" is not something which monitoring should be concerned with. It has no cluster-health value.

The last_transition metrics provides us a broader use.
We use it to show this information for the specific VM/VMI so that the sysadmin can inspect if there are unhealthy VMIs, report uptime for the specific VM, downtime and unplanned downtime, it can be used to identify VMs that are not used and to identify a bigger issue if we see that more than X VMs are in an "unhealthy" state for a specific time period.

I am not sure how a cluster admin should know what unhealthy means. Like again, if a VM is not ready, that does not mean that it is not healthy. Again like above, we can discuss about generic metrics which indicate readiness, but a timestamp is definitely the last resort and not necessary in this context.
I also want to point out that an "unhealthy" alert as part of kubevirt core, based on what you describe, would probably not fit into kubevirt core. We can not say here what unhealthy or healthy is.
For kubevirt core, the alerts should be correct for at least 95% of users I would say, better 100%. Otherwise we ship meaningless alerts which people can't get rid of easily.

We don't plan to add an alerts based on these metrics. This is important information that the user can analyse his cluster with. Like he does with the performance metrics (CPU, Memory, Disk) where not all of the metrics there are used for alerts. But they can create their own logic to identify issues in their system using them. They can also route messages with alertmanager based on stopped VMs to the namespace owners to delete old VMs just as an example.
When talking about VMs in OCP we should still consider that some of our users are using the Virtual machines in a more traditional way and they do care about the resources consumption and about doing cleanups and

There is no way to do this one by one. Its a sysadmin nightmare. Prometheus is exactly the tool to help them see the overall VM and VMIs conditions so that they can split and dice their data and do actions based on them.
Doing this is in an aggregated way will not allow them to address the individual VMs and VMIs.
You have metrics for individual pods, containers, node and more. Way do you believe you don't need this for individual VMs and VMIs?

What I am suggesting still allows addressing individual VMs. Just better integrated in prometheus. However what  you are suggesting makes it hard to get overall overviews (again with hacks a lot is possible) and only allows the individual case which makes it much less useful and potentially not even something which can be included in core kubevirt.
Most of the metrics you want sound fine from the overall intention, but how and where you want them is not necessarily ok on this lower level.
I can only ask again that you file a design doc and that we can sort out there on how to proceed. Like what you describe here sounds like a mixture of long-term metrics storage and monitoring. Prometheus is no long-term metric store, but tools on top of it (or instead of it), like thanos provide this.
I hope that we can sort out these differences and show you paths forward for your need in a design doc.
Let me know if it is still not clear where the tension is coming from.

Closing since this metric does not add value.
Thanks


test-branch/execute-job/quoted-authorization/b1893a3d-2ecf-4365-ba73-74d3dbc38629

PR for testing e03c42ec94e67f0ad92212120d4253fc914cf760

/canonical/self-hosted-runners/run-workflows e03c42ec94e67f0ad92212120d4253fc914cf760


Added LevelDB compaction after replicated log truncation.

LevelDB compaction algorithm doesn't seem to work well with out key usage pattern because the background compaction is not triggered [1]. Because of that the replicated log storage grows over time until it consumes all disk space on the partition. As a workaround we can manually invoke leveldb::DB::CompactRange() every time a truncation action is persisted and some stored keys are removed. This workaround can be turned off by setting the MESOS_LOG_AUTO_COMPACT=0 environment variable.
[1] https://github.com/google/leveldb/issues/603

Fixed commit message. @bmahler

I believe this was actually sent out for review but not landed, there should be 2 related commits: https://issues.apache.org/jira/browse/MESOS-184
Can you look through the feedback on them here:
https://reviews.apache.org/r/68089/
https://reviews.apache.org/r/68090/

Updated commit message and environment variables.


Added ActorReference creation from the ActorBase class informations

Description

Handled the case where you want to create an ActorReference inside the actor implementation from informations found in the Actor base class.
Added missing test for ActoreReference.Get method.
Handled: // TODO check for ActorBase  in the code of ActorReference class.

Example:
public interface ITestActor: IActor
{
  Task TestMethod();
}

public class TestActor: Actor, ITestActor
{
  public TestActor(ActorHost host)
    : base(host)
  {
  }

  public Task TestMethod()
  {
    // Currently an ArgumentOutOfRangeException is thrown when a call to ActorReference.Get(this) is executed
    //  because the Actor parameter cannot be cast to the IActorProxy interface.
    // The only way to create an ActorReference from the Actor implementation is as follows
    var referenceOldWay = new ActorReference { ActorId = this.Id, ActorType = this.Host.ActorTypeInfo.ActorTypeName };

    // In this case the ActorReference must be created based on the informations
    //  contained in the Actor base class with the .Get method already present in the object
    // This approach unifies the methodology already used to create an ActorReference from an IActorProxy
    var referenceNewWay = ActorReference.Get(this);
  }
}

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

[x] Code compiles correctly
[x] Created/updated tests
[ ] Extended the documentation

@philliphoff Another transient error seems to have appeared in actions.
Is there a command that can be given to re-execute actions?
Like \assign to assign issues
Recorded error in integration-test / run integration tests (6.0) (pull_request)
Error: Dapr.E2E.Test.GrpcProxyTests.TestGrpcProxyStreamingBroadcast: Grpc.Core.RpcException : Status(StatusCode="Unavailable", Detail="connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:37149: connect: connection refused"")

@philliphoff Done

@philliphoff can be included in v1.14 milestone?


Add sync of files from knative/community

Changes
Sync files from knative/community, starting with (generated) OWNERS_ALIASES. Attempt
to only apply this to knative (and knative-sandbox, if we choose to use
OWNERS_ALIASES there).
This is an alternate attempt to CODEOWNERS to automate group management, particularly for release leads.
Not sure how to test this...
/kind enhancement
/hold
Need https://github.com/knative/community/pull/532 submitted first.

/assign @n3wscott

/hold cancel

/hold

Want to fix the actions sync before I add more madness...

/hold cancel


Adding the ability to not preserve the keys when reversing a collection

This comes up quite a bit. Just call ->reverse()->values().


add: appwrapper pending status and condition check for scale-up

Issue link
Closes: https://issues.redhat.com/browse/RHOAIENG-861
What changes have been made
This pr contains an update to ensure the AW is in a pending state, with a condition of Insufficient resources before scaling up the specified resources for the appwrapper. This ensure resource usage efficiency for the cluster.
Verification steps
Steps I have followed to ensure the functionality. On a cluster with 2 m6i.2xlarge worker nodes.
I provisioned an appwrapper which required more resources than available on the cluster.
    - custompodresources:
      - limits:
          cpu: 10
          memory: 40G
          nvidia.com/gpu: 0
        replicas: 2
        requests:
          cpu: 10
          memory: 40G
          nvidia.com/gpu: 0
      - limits:
          cpu: 10
          memory: 40G
          nvidia.com/gpu: 1
        replicas:
        requests:
          cpu: 10
          memory: 40G
          nvidia.com/gpu: 1

This ensured the aw would reach pending state with the condition on Insufficient resources, inducing a scale up of the specified resources, as can be seen here:

I also provisioned an appwrapper with required resources within the clusters available
    - custompodresources:
      - limits:
          cpu: 2
          memory: 8G
          nvidia.com/gpu: 0
        replicas: 1
        requests:
          cpu: 2
          memory: 8G
          nvidia.com/gpu: 0
      - limits:
          cpu: 2
          memory: 8G
          nvidia.com/gpu: 1
        replicas: 2
        requests:
          cpu: 2
          memory: 8G
          nvidia.com/gpu: 1

With this the appwrapper was dispatched without the need for scaling up. As can be seen in the following:

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] Testing is not required for this change

Hey @asm582
I just pushed some changes there regarding the conditions message :)

Thanks @VanillaSpoon for the quick turnaround, Can you please add some screenshots of manual tests performed on this PR please?

Hi @asm582
I have added screenshots and an explanation of the scale-up testing to the pr description :)

Thanks @VanillaSpoon
LGTM


Exception TypeError when running a script more than once

Hi,
I have an error message when i run a script more than once.
Here the script, as simple as it could be:
# -*- coding: utf-8 -*-
import sys
import os
import matplotlib.pyplot as plt
import pyzdde.zdde as pyz

ln = pyz.createLink()
print(ln.zGetVersion()) # example
ln.close()

And here what is printed in a freshly started iPython console. Two runs are shown:
Python 2.7.11 |Anaconda 4.0.0 (64-bit)| (default, Feb 16 2016, 09:58:36) [MSC v.1500 64 bit (AMD64)]
Type "copyright", "credits" or "license" for more information.

IPython 4.1.2 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.
%guiref   -> A brief reference about the graphical user interface.

runfile('C:/Users/xxxx/Desktop/Temp/PyzDDE_tests/test_00.py', wdir='C:/Users/xxxx/Desktop/Temp/PyzDDE_tests')
160608

runfile('C:/Users/xxxx/Desktop/Temp/PyzDDE_tests/test_00.py', wdir='C:/Users/xxxx/Desktop/Temp/PyzDDE_tests')
160608
Exception TypeError: "'NoneType' object is not callable" in <bound method PyZDDE.__del__ of PyZDDE(appName='', appNum=1, connection=False, macroPath=None)> ignored

As you can see, I am using Anaconda, Python 2.7, Spyder.
Interestingly this does not happen the first time that I run the code.
I have tried to follow the recommendations in earlier posts ( #40)  but it does not seem to have an effect.
I would appreciate any suggestions.
All the best,
andres

I'm not sure what's going on.
Please try running the script in a "dedicated Python console" in spyder [Preferences >> Run >>  Console >> Execute in a new dedicated Python console] and see if you can still reproduce the error.
Please do let me know.
Thank you,
Best regards,
Indranil.

Hi Indranil, sorry for the delay.
In a dedicated console this error does not appear. Also, the first time i run it in a non-dedicated console, it does not appear, only from the second time on. that may be the reason why it does not appear on a dedicated console.
Best & thanks.
Andrés


Assembly is not Signed

Would it be possible to get the assembly signed?

Hi @JohanKustner,
When you say "signed", I assume you mean strong-named? Sorry, but strong-signing for OSS projects is a major PITA, and I'm not willing to take that burden...
If you really need strong-naming, I suggest you use Assembly Strong-Naming Toolkit, which can sign unsigned assemblies in NuGet packages.


∫eˢsin(10s) is not exact

SymbolicNumericIntegration can integrate ∫eˢsin(s) exactly:
julia> using Symbolics, SymbolicNumericIntegration

julia> @variables s
1-element Vector{Num}:
 s

julia> integrate(exp(s) * sin(s))
((1//2)*exp(s)*sin(s) - (1//2)*cos(s)*exp(s), 0, 0)

but for some reason it switches to floating-point approximations if sin(s) is changed to sin(10*s):
julia> integrate(exp(s) * sin(10s))
(0.009900990099009925exp(s)*sin(10s) - 0.09900990099009901exp(s)*cos(10s), 0, 6.878113617473781e-16)

even though the exact integral has rational coefficients:

Similar problem with:
integrate(1//4*exp(-10t)*sin(t), t)[1]

leading to:

which also can be made exact if rational numbers are taken advantage of.
Summing terms with rational numbers may easily lead to numerator and denominator larger than what can be handled by Int64, but I don't think that will be common in integrals.

SymbolicNumericIntegration ver 1.2 now supports symbolic integration in many cases. It returns
julia> integrate(1//4*exp(-10t)*sin(t), t; symbolic=true, detailed=false)
(-1//404)*cos(t)*exp(-10t) - (5//202)*sin(t)*exp(-10t)
Symbolic coverage is partial and may still fall back to numerical calculation if necessary.


styling issue with table

Hi!, thank you for your awesome library. I faced the issue on MS Word 2017 on Windows OS
I checked on MS Word for Mac, it looks fine. but when I tried to open by MS Word 2017 on Windows, there is spacing after 8pt, it makes the table cell doesn't middle align.

I exported the files from http://evidenceprime.github.io/html-docx-js/test/sample.html
Thank you so much.

Try to add { line-height: 8pt;} to your tr tag.

Hello ! Did you ever find a solution to this issue ?

Hello ! Did you ever find a solution to this issue ?

Hi, I couldn't find a solution to this issue. :(

Someone found a workaround in an other issue. You can wrap your cell content in a marginless
 tag to remove the spaces.
Something like :

Hello !

HOW WE CAN ADD FONT FAMILY TIMES NEW ROMAN IN TABLE STRUCTURE


Badges for "dev" package are not reporting the correct version

Describe the bug
As per the title.
How to reproduce it
Look at the README.md :point_down:

Expected behaviour
Badges should report the latest version on the master branch according to the following format:
x.y.z-N+hash
Where:

x.y.z the latest released version
N is the number of commit since the latest released version
hash is the ID of the latest commit on the master (first 7 digits)

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Hey @leogr, has this been fixed? I see the badges render as expected right now.

Hey @jasondellaluce
IIRC, it's partially fixed. It might not work under some circumstances. Basically, we pick the last version by relying on the S3 bucket ordering which may not reflect the version order.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale
I confirm a similar issue is still present. Basically, it seems to me filenames are ordered lexicographically.
So falco-0.30.0-19+f7893fb-x86_64.deb will come after than falco-0.30.0-177+f86423d-x86_64.deb that's not ok for our use case (you can check out the full order list here).

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

/remove-lifecycle rotten
cc @FedeDP

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

/remove-lifecycle stale

@leogr: Closing this issue.

In response to this:

In the end, the best option was to remove them from the README.
We will work on a better way to document how to use dev packages.
/milestone 0.36.0
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Add gentx-619d4079cd291c56dd0da4a5aa9546e2b6f54779.json

Add gentx-619d4079cd291c56dd0da4a5aa9546e2b6f54779.json

Thanks for the submission, but Github accounts have to be at least a year old to participate: https://github.com/public-awesome/stakebird-testnets#submit-genesis-transaction. This is to prevent Sybil attacks and ensure a fair and decentralized launch.


Database migration when deploying

Set up a system for automatic database migration, both schema and data.

Resolved by 4d09657f05494493478c6f93719e3b6c83632c15


Rollout improved example converter

Rolls out improved TF example converter.

This one has quite a few new examples but has also lost some.

jq '.|select(.ConversionResults.java.FailureSeverity==2)|.ConversionResults.typescript.FailureInfo' cov/byExample.json  | sort | uniq                                                                                ~/bugs/ci-mgmt-889/pulumi-github
""
"Duplicate resource \"github_actions_environment_secret\" configuration: A github_actions_environment_secret resource named \"example_secret\" was already declared at /e0.tf:1,1-62. Resource names must be unique per type in each module."
"Duplicate resource \"github_actions_organization_secret\" configuration: A github_actions_organization_secret resource named \"example_secret\" was already declared at /e27.tf:1,1-63. Resource names must be unique per type in each module."
"Duplicate resource \"github_actions_secret\" configuration: A github_actions_secret resource named \"example_secret\" was already declared at /e116.tf:5,1-50. Resource names must be unique per type in each module."
"Duplicate resource \"github_codespaces_organization_secret\" configuration: A github_codespaces_organization_secret resource named \"example_secret\" was already declared at /e82.tf:1,1-66. Resource names must be unique per type in each module."
"Duplicate resource \"github_codespaces_secret\" configuration: A github_codespaces_secret resource named \"example_secret\" was already declared at /e58.tf:5,1-53. Resource names must be unique per type in each module."
"Duplicate resource \"github_codespaces_user_secret\" configuration: A github_codespaces_user_secret resource named \"example_secret\" was already declared at /e131.tf:5,1-58. Resource names must be unique per type in each module."
"Duplicate resource \"github_dependabot_organization_secret\" configuration: A github_dependabot_organization_secret resource named \"example_secret\" was already declared at /e53.tf:1,1-66. Resource names must be unique per type in each module."
"Duplicate resource \"github_dependabot_secret\" configuration: A github_dependabot_secret resource named \"example_secret\" was already declared at /e130.tf:5,1-53. Resource names must be unique per type in each module."
"Invalid multi-line string: Quoted strings may not be split over multiple lines. To produce a multi-line string, either use the \\n escape to represent a newline character or use the \"heredoc\" multi-line template syntax.; Missing newline after argument: An argument definition must end with a newline."
"Invalid multi-line string: Quoted strings may not be split over multiple lines. To produce a multi-line string, either use the \\n escape to represent a newline character or use the \"heredoc\" multi-line template syntax.; Unterminated template string: No closing marker was found for the string."
"pcl.BindProgram failed: example.pp:0,14-35: unknown function 'github:index:labels'; unknown function 'github:index:labels'"


Tutorial has problems connecting with existing IAM IDP

Environment information
On cloudshell:

npm notice
npm notice New major version of npm available! 9.8.1 -> 10.8.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.1
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! could not determine executable to run

npm ERR!   Node 21 has reached end-of-life on 2024-06-01 and is not supported.       !!
!!  Please upgrade to a supported node version as soon as possible.           !!
!!                                                                            !!
!!  This software is currently running on node v21.7.1.                       !!
!!
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables
steve@Steves-MBP-8 amplifytest %

Description
Following the Amplify Gen2 tutorial.
I come to this page https://docs.amplify.aws/react/start/account-setup/
and do not understand how to proceed.
IAM Identity center was set up some time ago on the organisation root account and is connected to MS Entra as the identity provider.
Next, we are going to automate a number of steps that simulate the operations of setting up a user in the IAM Identity Center console. To get started open CloudShell, located in the console footer.
(Does this refer to the cloud shell in the application account or the org root account? Can this disrupt other users?)
response=$(aws sso-admin list-instances)
ssoId=$(echo $response | jq '.Instances[0].IdentityStoreId' -r)
ssoArn=$(echo $response | jq '.Instances[0].InstanceArn' -r)
email_json=$(jq -n --arg email "$user_email" '{"Type":"Work","Value":$email}')
response=$(aws identitystore create-user --identity-store-id $ssoId --user-name amplify-admin --display-name 'Amplify Admin' --name Formatted=string,FamilyName=Admin,GivenName=Amplify --emails "$email_json")
userId=$(echo $response | jq '.UserId' -r)
response=$(aws sso-admin create-permission-set --name amplify-policy --instance-arn=$ssoArn --session-duration PT12H)
permissionSetArn=$(echo $response | jq '.PermissionSet.PermissionSetArn' -r)
aws sso-admin attach-managed-policy-to-permission-set --instance-arn $ssoArn --permission-set-arn $permissionSetArn --managed-policy-arn arn:aws:iam::aws:policy/service-role/AmplifyBackendDeployFullAccess
accountId=$(aws sts get-caller-identity | jq '.Account' -r)
aws sso-admin create-account-assignment --instance-arn $ssoArn --target-id $accountId --target-type AWS_ACCOUNT --permission-set-arn $permissionSetArn --principal-type USER --principal-id $userId
Hit enter

Hey @stevegroom :wave: if your organization is already onboarded to IAM Identity Center then you do not need to run this script. It is intended to bootstrap IAM Identity Center with opinionated defaults for working with Amplify apps.
In your case, you can create a permission set named AmplifyAccess with the AmplifyBackendDeployFullAccess managed policy, and layer an AWS profile on top of your existing IAM Identity Center/SSO profile
[profile josef]
sso_session = josef
sso_account_id = xxxxxx
sso_role_name = AdministratorAccess
region = us-east-1

[profile josef-amplify]
source_profile = josef
sso_role_name = AmplifyAccess

[sso-session josef]
sso_start_url = https://d-xxxx.awsapps.com/start
sso_region = us-east-1
sso_registration_scopes = sso:account:access

Closing the issue due to inactivity. Do reach out to us if you are still experiencing this issue.


Update README.md

NPM should be installed already when you installed node.

On debian npm (1.4.21) must be installed separately: https://packages.debian.org/stretch/amd64/nodejs/filelist - but then again, that node version is very old (4.8.2).
Personally, I use n and n-install but a lot of people are using nvm.

Yeah I'll add some instructions about installing with nvm or n.

There are instructions for installing node using the package manager, on debian and ubuntu, available at https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions using the NodeSource distributions repository.

The timing of this thread has been WONDERFUL. A QUICK intro is I've apparently had my Github account since approximate 2009, but I am just now actually using it for almost the very first time. Am an absolute newbie learning on the fly here so my apologies in advance for beginner "oopsies" :smile:
A couple hopefully appropriate observations: #1 https://github.com/creationix/nvm#install-script worked perfect on Debian Buster. nvm then tried to (manually at my prompting) download node twice.
It failed both times most likely because dialup kept cutting off. nvm (understandably) started over at 0% download of the archive file. I was hoping to find flags documented that would circumvent that but so far am having hard time finding documentation that I can comprehend. Why I bother seeking a flag similar to wget's "-c" is that failed instances of that nature are about repeat wear and tear on the volunteer host servers and not just end user time spent.
#2 Nvm found more current than I did manually. Most current I could find was node-v6.11.2.tar.gz. Nvm chose the seemingly appropriate node-v8.3.0-linux-x64.tar.xz so I let it do what it thought should be done.
NOW after multiple nvm fails, I'm back at node-6.x k/t @paul90 pointing out node.js download page. I'd already been on that page, but this time the instructions made sense. I am working on the a-sumption that curl/apt-get's chosen version is correct for Beaker. PS Is my first successful curl. :smile:
Why I'm even writing is because you are considering potential readme notes. One "possible show stopper" glitch I encountered is that somewhere about 2 days ago I "apt-get install nodejs" directly. That was because "apt-get search node.js" was available via my one-liner Buster sources.list repository choice. That decision was not an informed one but was made because node.js popped up several times in online npm/nvm/node tips.
The notable "glitch" I encountered is that the curl/"apt-get install" route suggested via the @paul90 recommendation... reinstalled node.js after I had JUST installed it. ? :smile: Seems safe to think it was maybe about host repositories catching up to speed with the product's creators.
EXCEPT THAT: A further glitch (bug?) that has now been corrected is that npm did NOT exist when I installed node.js directly via Debian Buster (with no curl first). Some more research turned up "yum" with some possible potential, but that's as close as I could get.
The bottom line (for now): That "curl/apt-get install" reinstallation route JUST finished... and now the apparently important npm is available!! Thank you!! I have no idea what step comes next because it's been so long in between attempts, but I'm off to try anyway. :smile:

Paul Frazee
Great work and i'd like contributing with a package to Arch linux
I built a packages using the Arch Linux and yaourt, it's to don't have building from source if you aren't developer and install it on arch linux more easy:
You can view how to install on:
https://goo.gl/yaSXp7
If you want more information, please visit:
https://aur.archlinux.org/packages/beakerbrowser/

Cool, thanks @flaketill.


Performance Improvements, Parsing failover fixes

Huge performance gains
Redirect parsing and failure behavior to property accessors instead of constructor that could fail on DI resolution

Please review and lets make it happen together.

How to update this PR with the added changes?


[SP] Translate error

Description
Bad: Cheques
Good: Chequeos
Corrected: Activar chequeos del estado de salud...
Better alternative: Activar comprobaciones del estado de salud...
Gitea Version
1.21.4
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots

Git Version
No response
Operating System
No response
How are you running Gitea?
Self Hosted
Database
PostgreSQL

Gitea is using crowdin for the localization.
https://github.com/go-gitea/gitea?tab=readme-ov-file#translating
So we will not maintain other languages except English here.
You can access and contribute https://crowdin.com/project/gitea in crowdin.

Gitea is using crowdin for the localization. https://github.com/go-gitea/gitea?tab=readme-ov-file#translating
So we will not maintain other languages except English here. You can access and contribute https://crowdin.com/project/gitea in crowdin.

Cool, done
https://crowdin.com/editor/gitea/68/enus-es?view=comfortable&filter=basic&value=0#q=cheque


Implement "useExecutor" feature for new dispatching logic

This is one the features pending after the implementation of the new dispatching logic started on #2038.
When launching a new execution, an Azkaban admin can choose the executor for it by specifying a useExecutor parameter in the request.
New executions are inserted into execution_flows table in the database. A newly added column to this table, "use_executor", will hold the executor id passed as a parameter in the request.
Active executors will poll executions with (use_executor == null or use_executor == pollingExecutorId)
Inactive executors will only poll executions with their ids  (use_executor == pollingExecutorId)

please resolve conflicts.

Pull Request Test Coverage Report for Build 4369

15 of 18 (83.33%)  changed or added relevant lines in 3 files are covered.
12 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.06%) to 36.893%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

azkaban-common/src/main/java/azkaban/executor/ExecutionFlowDao.java
15
16
93.75%

azkaban-common/src/main/java/azkaban/executor/JdbcExecutorLoader.java
0
1
0.0%

azkaban-exec-server/src/main/java/azkaban/execapp/FlowRunnerManager.java
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/jmx/JmxJobMBeanManager.java
1
72.73%

azkaban-common/src/main/java/azkaban/jobExecutor/AbstractJob.java
2
31.03%

azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
4
76.23%

azkaban-common/src/main/java/azkaban/jobExecutor/AbstractProcessJob.java
5
60.71%

Totals

Change from base Build 4366:
0.06%

Covered Lines:
10945

Relevant Lines:
29667

💛  - Coveralls

@ypadron-in, questions about this:

Inactive executors will only poll executions with their ids (use_executor == pollingExecutorId)

So are inactive executors still polling & dispatching executions from the queue after they have been inactivated?
Is it even allowed to submit new executions (ie. add to the queue) with use_executor == someInactiveExecutorId, after the executor has been inactivated?

@ypadron-in, questions about this:

Inactive executors will only poll executions with their ids (use_executor == pollingExecutorId)

So are inactive executors still polling & dispatching executions from the queue after they have been inactivated?
Is it even allowed to submit new executions (ie. add to the queue) with use_executor == someInactiveExecutorId, after the executor has been inactivated?

@juhoautio Yes to both questions.
Our use case in this scenario of inactive executor polling and running executions is that following deployment of binaries we run test executions before activating the executor so that production flows are not affected if there is something wrong with the binaries. If tests pass then we activate the executor.
Also useExecutor parameter will only be honored if set by an Azkaban admin, we assume is going to be used wisely.


Add display override for hiding content when printing

When printing users often need to print the content without the surrounding site furniture (eg menus, breadcrumbs, back links and footers).
Introduce a helper so that a class can be used to hide any given element from the print view:
govuk-!-print-display-none

This is explicit and preferable to listing all the selectors for things that shouldn't be printed. These lists grow unwieldy over time. (An example of one of these lists)
(We've been using this pattern on Apply for teacher training and Becoming a teacher: Design History)

@fofr what do you think about components such as the footer having sensible print styles: https://github.com/alphagov/govuk-frontend/issues/573 ? Do you think you'd want full control over that with a helper instead of them being baked in?

@nickcolley I think we need both.
Components should have good print styles out of the box. But sometimes it's not clear if a component should be printed or not – for instance a breadcrumb may sometimes be useful to print as it shows the hierarchy or context of some content, whereas at other times it's simply a navigational aid and can be hidden.
In our case we are printing an application and all its completed fields. Which means hiding a lot from the print view so that it's clean and appears similar to a completed paper form.

We're happy to accept this, would you mind adding a feature CHANGELOG entry that introduces the new class? You can look at other feature CHANGELOG entries for examples.
I can do this on your behalf if you'd prefer that.

I've added a changelog entry. Happy for you to amend if it's not quite right.

What's happening with this PR now?

@fofr sorry I think I got us confused and left this in an unresolved place.
I'll work with the team to get consensus and reply to you, thanks for your patience.

@fofr sorry for the delay, we decided that in order to keep consistency with the existing govuk-grid-column-one-third-from-desktop class that we want to name this new override govuk-!-display-none-print. If you want we can do this on your behalf, let us know :)

@nickcolley PR updated.


Support for named tokens for format string

What is the appetite for supporting named tokens in a new method, to be called like this:
en:{
    welcome:"welcome |firstName|, your status is |Status|."
  }
  ...
  var tokens = { firstName: "John", status: "Accepted" };
  strings.formatStringWithTokens(strings.welcome, tokens);

The benefit of this is that when the strings are handed over to localization teams they have more context of the value in those fields and less room for error.

@joshsalverda the PR is merged, so I think this should be closed.


Song plays everywhere

Hello! The songs for me play anywhere, even when speakers are loaded or not. I don't think this is intended since you have coded it to be linked to 3 speakers, so it would make sense that the songs play until a certain distance, like vanilla jukeboxes.
The mod's version is SpeakerMod-1.18.1-<IP_ADDRESS>.jar and I'm using Forge 40.1.0 for Minecraft 1.18.2
Thank you in advance

I will give this a look.

Sorry for the lack of updates.  Best friend diagnosed with Cancer and someone stole my catalytic converter.   I'll give this a look tomorrow.

No problem, I'm sorry for you about those things and thank you for updating me here even in those circumstances. I appreciate your passion for modding, although if there is IRL stuff happening please tend to them as you need to and want to, as it is very important.


512x512 training  configuration

I want to know the specific configuration of 512x512 size training, --num_bucket_per_side should be 512, 512?

The num_bucket_per_side for nuImages is 512x512, while 256x256 for COCO-Stuff. Check the generation configs in our pre-trained checkpoints for reference here.
Other configurations are maintained similarly to the 256x256 experiments. The only thing to change is to linearly scale the learning rate with respect to the batch size.


Issues 198 and 201

Cleans up ascending lock file bug and adds relative path handling to Ctx.LoadProject.  Adds numerous unit tests to same.  Supercedes PR #200

No problem on all of the above.  Will tweak now.

?  Why would test.Testgo go down?

Oh - I see Testgo was just renamed to Helper.

@sdboyer do you want this squashed, or is 5 commits ok?

LGTM! thanks again!


Remove wasmlink, wasmlink-cli, and test-modules.

This PR removes wasmlink, wasmlink-cli, and test-modules from the
wit-bindgen repo.
wasmlink is based on an outdated module linking proposal and predates any of
the work on the component model. As such, it never really graduated beyond a
useful demo of how multiple core WebAssembly modules might exchange interface
types.
Now that the work on the component model is progressing, the underlying
wasm-tools no longer support the module linking proposal; therefore, wasmlink
is becoming a maintenance burden.
As the author of wasmlink, I think the time has come to remove it from the
tree. Any parties that need a copy of wasmlink for whatever reason may fork
it prior to this commit being merged.

Pinging @saulecabrera for your thoughts on this too.


chore(Dependencies) : update tapir-akka-http-server, tapir-core, ... from 0.17.20 to 0.19.1

Updates

com.softwaremill.sttp.tapir:tapir-akka-http-server
com.softwaremill.sttp.tapir:tapir-core
com.softwaremill.sttp.tapir:tapir-json-circe
com.softwaremill.sttp.tapir:tapir-openapi-circe-yaml
com.softwaremill.sttp.tapir:tapir-openapi-docs
com.softwaremill.sttp.tapir:tapir-sttp-client

from 0.17.20 to 0.19.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.tapir" } ]

labels: library-update, early-semver-major, semver-spec-minor

Superseded by #369.


Hey i need help with this problem in kali linux

Umm so i was using Kali linux today and I wanted to download HiddenEye but i get this problem here is a screneshot - http://prntscr.com/q0xuqi
Any way on how i can fix that and i am new to kali linux stuff

@Feelingloved ,
This is not Build/Installation or Bug/Performance issue. This repo is to report issue related to Tensorflow/core.Please raise the issue in right repo.Thanks!


fix: version range handling in update_pkg function

keep user's library version if higher than hard-defined version
#11693

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

let me add another test


Allow using unix sockets for safe usage on multi-user machines

On multi-user dev machines (such as is our case), it seems there's no way to prevent one user from sending commands to another user's instance, as it's using a standard TCP port on the machine.
Also, it means the users must agree on which port each of them uses, which might be tedious.
It seems that a solution to both issues would be to allow using unix sockets, which are basically sockets but path-based, supporting file permissions. It seems that using a local file in the user's home directory would naturally propagate that directory's permissions, and avoid conflicts.

The reason I've originally written it with TCP sockets is that UNIX sockets don't work on windows and I wanted to make it portable.
If someone wants unix sockets and submits a PR that will allow a unix socket in the listen and connect config options without breaking windows and users who are using tcp sockets and/or are using default config I'd be happy to accept that. We could even make unix sockets the default config on *nix systems.


update out-of-resource.md

change "thresholds" to "threshold"

This change is

update branch already

update branch again


Style of the toolbar button isn't right

such as the picture above, the button style is not like the sample.

the height doesnt equal the width.

The version has solved this issue, sorrry for late response.


Is there a way to ignore certain tags?

Is there a white to whitelist / blacklist certain tags? For example, if I only want to parse bold and italic tags and ignore the rest.

There's no way to cherry pick syntax elements you want to parse, but you might be able to achieve this with a lang extension.


Update cats-helper to 1.5.2

Updates com.evolutiongaming:cats-helper from 1.5.1 to 1.5.2.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.evolutiongaming", artifactId = "cats-helper" } ]

labels: library-update, semver-patch

Pull Request Test Coverage Report for Build 131

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

Files with Coverage Reduction
New Missed Lines
%

scassandra/src/main/scala/com/evolutiongaming/scassandra/CreateClusterJ.scala
1
50.0%

scassandra/src/main/scala/com/evolutiongaming/scassandra/PoolingConfig.scala
2
88.24%

scassandra/src/main/scala/com/evolutiongaming/scassandra/SocketConfig.scala
3
53.85%

Totals

Change from base Build 130:
0.0%

Covered Lines:
345

Relevant Lines:
461

💛  - Coveralls


MongoError

Check out this issue for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!
For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

[ ] You've met the prerequisites.

[ ] You're running the latest version of Parse Server.

[ ] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup
parse-server version 2.2.6
Steps to reproduce
When I modify databaseUri to a cluster "mongo://....." ,I come up the error of "MongoError: Authentication failed" ,but the same connection string can work in the old version of parse server (2.1.3).
I change the connection string to a singe node mlab ,I can pass the indentify and get the instalations data. I doubt that there are some issue in the mongo libs.
Logs/Trace
error: Uncaught internal server error. { [MongoError: Authentication failed.]
name: 'MongoError',
message: 'Authentication failed.',
ok: 0,
code: 18,
errmsg: 'Authentication failed.' } MongoError: Authentication failed.
at Function.MongoError.create (/Users/gongchen/Desktop/PinssibleWork/pinParse/worldcity.parse/libs/parse-server/node_modules/mongodb-core/lib/error.js:31:11)
at commandCallback (/Users/gongchen/Desktop/PinssibleWork/pinParse/worldcity.parse/libs/parse-server/node_modules/mongodb-core/lib/topologies/server.js:1154:66)
at Callbacks.emit (/Users/gongchen/Desktop/PinssibleWork/pinParse/worldcity.parse/libs/parse-server/node_modules/mongodb-core/lib/topologies/server.js:119:3)
at null.messageHandler (/Users/gongchen/Desktop/PinssibleWork/pinParse/worldcity.parse/libs/parse-server/node_modules/mongodb-core/lib/topologies/server.js:295:23)
at Socket. (/Users/gongchen/Desktop/PinssibleWork/pinParse/worldcity.parse/libs/parse-server/node_modules/mongodb-core/lib/connection/connection.js:285:22)
at emitOne (events.js:90:13)
at Socket.emit (events.js:182:7)
at readableAddChunk (_stream_readable.js:153:18)
at Socket.Readable.push (_stream_readable.js:111:10)
at TCP.onread (net.js:529:20)

I found the reason .
  The url format makes the connenction string authentication failed

I ran into this as well and the solution above fixed it. For me it was due to a / character and uppercase letters in my password. Manually encoding the slash worked without modifying any code. See here: https://github.com/ParsePlatform/parse-server/pull/986#issuecomment-210135135


Updated TestStore DSL

This PR introduces a newer, flatter way of asserting with the test store. Instead of calling store.assert(...) with a series of steps, one can now invoke store.send and store.received directly, improving how/where XCTest failures are surfaced.

Very minor (and I almost managed to comment on this before it was merged), but there are a number of usages of self.scheduler that could be simplified to scheduler. I could create a PR for that, assuming there wasn't a reason for keeping them that way.

@nmccann We may be in the minority here, but we prefer to always be explicit about self even where it can be implicit. We think it makes it clearer when a value is a property vs. a local variable or constant, especially when reading outside of Xcode, like in PRs. We'd take submissions to add self. if we've missed it anywhere, though 😁

Fair enough - I'll gladly admit that it does help readability in PRs. Even if you're in the minority - it's your project and you raise some compelling points, so I'm happy to defer to your preferences :) I've long ago realized there is no "correct" choice in regards to such things - internal consistency within a project is the more important thing.


Memory can be leaked by createTensorFromOrtValue

The createTensorFromOrtValue function is used internally when DynamicAdvancedSession.Run(...) automatically allocates output tensors (and in any other place where an OrtValue may need to be converted to a go type).  This function uses the GetTensorMutableData(...) function from the C API to get an unsafe.Pointer to the actual tensor data.  Currently, the data pointed to by this pointer is never freed, even after calling Destroy() on the tensor returned by createTensorFromOrtValue.
Handling this is not necessarily straightforward.  Unfortunately, simply creating a new Tensor directly with the OrtValue in createTensorFromOrtValue is not going to work, because a user may call that tensor's GetData() function to obtain a slice.  If the user maintains a reference to this slice after calling Tensor.Destroy(), the data pointed to by the slice will become invalid.  The obvious solution is to have createTensorFromOrtValue create a copy of the data, but this is overhead that may be nice to avoid.
In summary, here are two possible fixes:

Have createTensorFromOrtValue always copy the tensor data and return an entirely new Tensor backed by go-managed memory. This will solve the memory leak and behave as before, but make DynamicAdvancedSession.Run(...) a bit slower, especially for large tensors.  Destroy the original OrtValue before returning to clean up the original data.
In createTensorFromOrtValue, use the input OrtValue directly as the .ortValue field in the returned Tensor.  Therefore, when the returned tensor is Destroy()ed, the underlying data will be cleaned up as expected.  However, in this case a copy would need to be made (and cached) when GetData() is called.  We could also potentially add a GetUnsafeData() function that would return the original data slice, that would become invalid after destroying the tensor.  This would allow avoiding the copy in new code, but I don't know if I like having the potential for mistakes here.

Out of these two options, I am strongly leaning towards option 1 for several reasons:

Tensor.GetData() does not return an error, so making it have side effects could potentially introduce the need for panics.
I don't think many users are heavily using the auto-allocation feature of DynamicAdvancedSession.Run(...) since this memory leak hasn't been reported yet.
If users were heavily using the existing DynamicAdvancedSession.Run(...) in this way, the performance gains from fixing the memory leak may make up for the performance loss due to the copy, especially in longer-running applications.
If the copy causes a performance regression, users still can avoid it simply by reusing tensors on subsequent calls to Run(...), rather than having onnxruntime reallocate them every time.

Should be fixed by commit 75416c0bb68399ba


[snakecase sniff] Unclear error msg when using static property

Just ran into an unclear error message.
$classes = array_udiff( $classes, Prefix_PHP_Classes::$PHP_classes, 'strcasecmp' );

Throws a Variable "PHP_classes" is not in valid snake_case format while I would expect it to say Property "PHP_classes" is not in valid snake_case format
Also wondering if there is a way for me to whitelist this as an exception ?
Related #549
[Edited: quoted wrong line from source code originally, now corrected]

Also wondering if there is a way for me to whitelist this as an exception ?

Answered my own question by sending in PR #557 ;-)


applies_to_file_regex tag doesn't work propertly

Describe the bug
The following regex in applies_to_file_regex doesn't work properly:
^(?!\/.configuration$)\/.+\/.configuration$

The regex search .configuration files in folders or subfolders but not in the root, using the following rule:
 {
    "name": "DES",
    "id": "DES1",
    "description": "This is a description",
    "applies_to_file_regex": [
      "^(?!\\/.configuration$)\\/.+\\/.configuration$"
    ],
    "tags": [
      "Configuration"
    ],
    "severity": "critical",
    "patterns": [
      {
        "pattern": "^",
        "type": "regex",
        "scopes": [
          "all"
        ],
        "modifiers": [],
        "confidence": "high"
      }
    ]
  }

Inspector detects the root file:

I tested the regex using an online regex tester and seems to be ok:

To Reproduce

Create rule and folder with .configuration file
Run inspector with analyze with HTML output

Expected behavior
The root file won't be detected by Inspector using the regex expression.
Operating Environment (please complete the following information):

Application Inspector Version: 1.9.22
OS:  MacOS 14.5 using docker image mcr.microsoft.com/dotnet/sdk:8.0

Hi @ganchix, Sorry you're having trouble but I'm unable to reproduce this.

Hi @gfs
To reproduce use the following command
appinspector analyze -s /project -r /rules
In the folder project add the following structure:

project/.configuration
project/testDir/.configuration

In the rules folder, add the rule.
The output should be 1 match, but it is 2.
The difference is that the whole project folder is analyzed using the two structures.
Thank you!

Hi @ganchix,
Sorry, I'm still unable to reproduce this, here's what I tried.
I tried with the command you recommend above but it results in 0 matches due to missing the -u argument for scanning unknown file types. When debugging custom rules I find it's also useful to include -i to exclude the default rules, and -S to force single threaded behavior to isolate if the issue is related to a threading bug - though that does not appear to be the case here.

Once adding -u I got the results I sent the screenshot of in my previous reply - as expected by the regex the file at /.configuration is ignored but the file at /testDir/.configuration is not.
Based on the regex you provided, a file at /project/.configuration should not be skipped, because it is not at the root of the filesystem (also as seen in the regex screenshot from your report). The file regex is performed against the full file path, not the relative path from the scan folder (unless the scan folder is specified as a relative path, more on this below*).

If I modify your regular expression to include the full path to the .configuration file in the project root as you indicated you're attempting in your second message it still seems to be working fine to me. Something like this:

Here are two runs, first using your original regex, and second using a regex which excludes the .configuration file in the project folder root. Before each run in the screenshot, I cat out the contents of the rule being used. You can see with your provided regex run it finds two matches from the two .configuration files, but with my modification it only finds one match:

I'm using the same file structure you mention in your follow-up message:

If you want to ignore files located at /some/path/to/project/.configuration without using the full absolute path you could try something like ^(?!(/.+)?/project/.configuration$)/.+/.configuration$. Note that /.configuration in the absolute file root still isn't matched because of the /.+/ in the second part of the regex, Its up to you if that's your intention for the regex.

I also see the same behavior if the rules are loaded from a folder containing the rule json rather than the explicit path to the rules.

Please let me know if that helps or if you still believe there is an issue I'm missing here.

I do believe I've identified one issue here, if you specify the scan path as a relative path, the paths used to check the file regex will be relative paths (that include that initial provided directory) rather than absolute paths. Though that issue doesn't seem to result in the behavior you've seen with your regex, since the paths will then also be missing a leading /, resulting in no matches in your case.


ci: update agreements action (allow dependabot)

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

v1.9.1
GitHub release

Your semantic-release bot :package::rocket:


Mifare Classic 1K: Authentication Error after Multiple Writes

Hi @pokusew,
Something weird is happening when attempting multiple writes. I have the following simple script that (1) Authenticates Blocks 4-7, Reads Blocks 4-7 and then Writes to Blocks 4-7.
It seems that the cards become unusable after attempting multiple write operations as they refuse to Authenticate. I have also tried this using promises.
I really like this package due to its quality, straightforward installation across platforms and Electron support.
Any suggestions or advice from your side?
https://gist.github.com/therealri/96adfa625d8bb3b2929a956ec1919cda
1:53:04 AM info ACS ACR122 0  device attached
1:53:05 AM info ACS ACR122 0  card detected
card:
  type: TAG_ISO_14443_3
  uid:  4e62e3f5
1:53:05 AM error ACS ACR122 0  error when authenticating data
card:
  type: TAG_ISO_14443_3
  uid:  4e62e3f5
err:
  name: AuthenticationError
  code: operation_failed

Hi @therealri,
Just to clarify:
Does the script fail always or does it work just for the first time (meaning that it allows you to write data just once)?
Thanks for your answer.

Hey @pokusew,
So it works just the first time but thereafter the card becomes unusable.
So yes, it allows me to write data just once using the Exact Script in the Gist and thereafter it's not possible use the card again.
Thanks!

And does it work when you restart the script (CTRL-C and run again)?

@therealri I have got the idea, from where the problem comes. ❗❗❗
Please answer my previous question and we can go further.

@therealri I think that the problem is here:
I am looking into the technical documentation of Mifare Classic 1K.
Section 8.6 is about Memory organization.

... memory is organized in 16 sectors of 4 blocks. One block
contains 16 bytes.

When accessing these blocks with this library, blocks are numbered as follows:

sector 0:

block 0 – manufacturer data (read only)
block 1 – data block
block 2 – data block
block 3 – sector trailer

sector 1:

block 4 – data block
block 5 – data block
block 6 – data block
block 7 – sector trailer

sector 2:

block 8 – data block
block 9 – data block
block 10 – data block
block 11 – sector trailer

and so on

That's important, it's that the last block in each sector is "sector trailer" (Section 8.6.3), which contains access conditions for the other 3 data blocks.
So block 7, which you are trying to write to in your code, is not for data. After you write to it, it changes access conditions (including key) and you cannot authenticate your card then.
I don't have any Mifare Classic card to test it, but according to documentation it is quite clear.
Could you please update your code (remove interaction with block 7, see updated gist here) and test if it works?
Hope it helps and looking forward to your answer.

Hi @therealri,
I have just noticed another problem in you gist, on line 100, 104, 108, 112 you forgot to add the third, blockSize, argument 16 (4, 16, 16). It probably causes unneeded read operations.
Just to be sure, you probably do know it, 16bit integer takes just 2 bytes, not 16 bytes (1 bytes = 8 bits). So before writing only 2-byte 16-bit integer into 16-byte unsafely-allocated Buffer, add data.fill(0), more info here.
I fixed all these things in my fork here. Take a look!
Also let me know, if everything works for you as expected.
Hope it helps.

Hey @pokusew,
Thanks so much and sorry for not getting back to you sooner, I have been travelling.
I also needed to get some extra Mifare Classic 1K Stock.
I have read through your comments and see where I went wrong on the configuration. I appreciate the updated code and all your help and time!
I have tested and it works perfectly, I have a clear understanding of the Mifare Classic 1K Data Layout now :)
Thanks so much!

it is not working with angular 6 and it throwing error while importing like "nfc is not a constructor".
import {NFC} from 'nfc-pcsc' throwing error
ERROR in ./node_modules/bindings/bindings.js
Module not found: Error: Can't resolve 'fs' in 'C:\Users\Admin\Desktop\electronapp\node_modules\bindings'
ERROR in ./node_modules/bindings/bindings.js
Module not found: Error: Can't resolve 'path' in 'C:\Users\Admin\Desktop\electronapp\node_modules\bindings'
reason i found fs module will not work with angular 6. by inbuilt nfc containing fs .
because of these reason i accessed  nfc from html and i declared in angular 6 component declare var NFC: any;
because of above i am getting nfc is not a constructor

@therealri I have been having troubles trying to read some data from my Mifare Class 1k card. Do you think you could spare some time and help out?

Hi @fabioloreggian, what troubles do you have? I am happy to help. 🙂


(pkg/openapi3) Support schema in openapi3 format

Codecov Report

Merging #136 into master will decrease coverage by 1.14%.
The diff coverage is 59.80%.

@@            Coverage Diff             @@
##           master     #136      +/-   ##
==========================================
- Coverage   82.14%   81.00%   -1.15%
==========================================
  Files         125      131       +6
  Lines        5483     5664     +181
==========================================
+ Hits         4504     4588      +84
- Misses        664      754      +90
- Partials      315      322       +7

Impacted Files
Coverage Δ

pkg/providers/openapi3/schema.go
49.20% <49.20%> (ø)

pkg/providers/openapi3/resolver.go
76.92% <76.92%> (ø)

pkg/broker/logger/logger.go
88.63% <0.00%> (-4.23%)
:arrow_down:

pkg/codec/xml/xml.go
53.84% <0.00%> (ø)

pkg/codec/json/json.go
37.93% <0.00%> (ø)

pkg/codec/proto/message.go
63.22% <0.00%> (ø)

pkg/codec/www-form-urlencoded/form.go
82.25% <0.00%> (ø)

pkg/codec/www-form-urlencoded/errors.go
100.00% <0.00%> (ø)

pkg/specs/property_errors.go
0.00% <0.00%> (ø)

... and 5 more

Codecov Report

Merging #136 into master will decrease coverage by 0.53%.
The diff coverage is 65.73%.


Up-to-date screenshots

https://courses.ics.hawaii.edu/ics314s24/morea/final-project/experience-final-project-m1.html


County selection box cuts off longer text

Is it possible to have the box a minimum character width? This should be the length of the longest entry.
We could lose some width from the Volume and Page fields if necessary, I think?

No different on Test3 or Beta.
However now a slidy bar underneath, so allocating to a future version

REady for testing in test3


values not exists if the sheet is empty.

Coverage remained the same at 100.0% when pulling 70e8233340c285285d6eec1e9dd3de4d2b19e6cb on lanfon72:patch-1 into fd855a857e8e222aa27ad1fa15a2885fb7a900ee on xflr6:master.


Loading DLL fails in packaged UWP

Description
Using Win2d in a packaged UWP app fails when attempt to load the native DLL.
Steps To Reproduce

Create an UWP app with packaging project
Add <PackageReference Include="Win2D.uwp" Version="1.28.0" /> to .csproj
Add new Microsoft.Graphics.Canvas.UI.Xaml.CanvasControl();
COMException (CLASSNOTREG) is thrown

Microsoft.Graphics.Canvas.dll cannot be loaded in DllModule.TryCreate. LoadLibraryEx returns ERROR_MOD_NOT_FOUND for all probed paths.
Expected Behavior
The DLL should load, and the control should be created.
Version Info
CsWinRT 2.1.6
.NET 9.0.100-rc.2.24474.11
Windows SDK 26100
Additional Context
Without a separate packaging project, the DLL loads.

This is probably MSIX/WAP issue, not CsWinRT.

The issue is that for some reasons the wapproj doesn't automatically pickup SDKReferences from the csproj, you can add these props to your .wapproj as temporary workaround until we fix the issue
<SDKReference Include="Microsoft.VCLibs, Version=14.0" />
<SDKReference Condition="'$(Configuration)' == 'Debug'" Include="Microsoft.UniversalCRT.Debug, Version=$(TargetPlatformVersion)" />

That helped. Thanks a lot.


Handling birthday - timezone issues

Hi, I have an issue with the timezones and I can't find the solution.
When the user picks his/her birthday's date the angular-moment-picker is automatically converting the date to UTC format. This is not too lucky since when I'm sending the picked date to the backend the UTC date will be sent so I don't know what was the local timezone of the client.
For example, if I'm in GMT and select my birthday: 1980-01-21 the backend will get 1980-01-20 as a date, and the wrong birthday will be stored (01-20 instead 01-21).
When the users want to see other user's birthday a wrong date appears when a user is in different timezone from GMT, only those users are getting the correct value (01-21) who are in the same timezone like me (GMT), users with a browser in UTC will get the wrong 01-20 birthday date.
I have no idea how to handle this on the backend side ( I don't want to convert back and forth the picked date object on the client side that would be a bit ugly).
Can I somehow avoid converting the picked value to UTC automatically? Or any other suggestions how should I handle this?

The trick is to manually convert the moment object to UTC while not changing the display time:
var m = moment();
var keepLocalTime = true;

m.utc(keepLocalTime);

Now the value sent back to the back-end will still be in UTC (the default), but on the correct date.
For the issue of displaying values sent by the server, you might need to use m.local(keepLocalTime).


x/tools/gopls: improve documentation

Our current documentation is not very user-friendly and rarely updated.
We should add more information about workflows, features, example configurations, etc.
We should also try to autogenerate as much as possible (https://github.com/golang/go/issues/33544).

Will the code actions be documented in this issue
as well, or should I file a separate one?
Also, I think I'll be able to contribute some docs
regarding Neovim's (currently nightly-only) native LSP support
in the next few days. Whom should I set
as a reviewer?

I think we can include an overview of code actions as part of this documentation effort.
You can feel free to add me as a reviewer, but you can also not assign a reviewer and one will get added automatically.

This issue is probably too general to be useful for tracking purposes. We have made a number of documentation improvements recently, and we are currently working on more. Will close this as a result. If anyone has concerns about our existing documentation, please file a new issue.

This issue is probably too general to be useful for tracking purposes. We have made a number of documentation improvements recently, and we are currently working on more. Will close this as a result. If anyone has concerns about our existing documentation, please file a new issue.


gitnr search view reacts to both Press and Release events

In fn handle_key_events (here), the event.kind is not checked with keyboard input.
I think this event is created when pressing and releasing a key, so every key is reacted to twice. Trying to select using enter selects and then unselects, or using arrow keys moves 2 items at a time.
This is on Windows, but looking at the crossterm docs, the event kind needs to be opted-in for unix systems so it might not happen for you.

Hey, thanks for the heads-up and providing the relevant docs.
Didn't notice that at all. Thankfully, I think the fix was quite simple (https://github.com/reemus-dev/gitnr/commit/7dffa5b63f5b1812711eee4302c0e493ba0f903a). I also enabled event.kind for Unix systems as well, so things are consistent across platforms.
The new release v0.1.1 has that fix.
Let me know if it works fine, I don't use Windows and as such can't test it out easily.

Hey, thanks for reacting so quickly. The new version actually doesn't work now hah. Screenshot below:

I think you might need to gate the push and pop of KeyboardEnhancementFlags, maybe behind cfg(not(windows)), I'm not sure on the syntax. But the rest of the commit looks correct. This is probably because, as the crossterm docs say, it's always enabled for Windows and the enhancement flags don't exist.

My bad mate...lol. Thanks for showing the error and pointing me in the right direction.
Managed to fix that issue and tested it in my Windows VM. Also managed to fix a few other issues too.
Release v0.1.3 is available now.
I've also set up the GH action to publish the crate, so it's available on crates.io now. I've also configured it to work with cargo-binstall as well. Check out the README for more info on the new install methods.


Random crash on long batch.

Steps to reproduce

Do any batch (long ones, more than 6-8hours long)
Nothing special I loaded an .igl then the program close itself up while downloading.
I provided .igl that cause crash, but basically, every "long run" download made the program crash.

Context
Nothing fancy, the applications was running and not minimized. No big app running like games or others, just it downloading. (I used NetLimiter to reduce it's speed, but it append with or without it)
Screenshots
There is nothing, the application was running on desktop (not even minimized) and it suddently crash.

Provide the crash dump that was linked by the Crash Reporter tool.
This one ? https://i.imgur.com/pCdAbjs.jpg

System information

OS: Windows 10 (Up to date)
Grabber version: [e.g. 6.0.3] Lastest and Nightly.

Additional context
This append like every night during batch. Provider as no revelance, i got crash on e621 and Gelbooru too. It didn't not noticed anything like memory leak's, the applications was under a gigabyte of ram every times I looked at my task manager. I included filtered process monitor log too. But I didn't see anything revelant, the crash apear to be random. The only "constant" is that it appens over long (very big) batches. (I included two of the crashing igl files, the smallest is the lastest, i basically re-save them when a part is completed and re-launch the application to "avoid" crashes.)
Grabber log+igl+ini and procmon log too.zip
If u need procmon : https://docs.microsoft.com/fr-fr/sysinternals/downloads/procmon#download

Seems to have disapear since 6.0.6.


Clarify inital setup steps for running RN Tester app

Summary:
There were a few missing details in the RN Tester steps that I had to infer or hunt down elsewhere. Making them explicit so future folks will have an easier time.

Changelog:
N/A

Test Plan:
Check new clickable links and look for typos.

Closing as per review comments


fix: remove upper limit for required terraform version

/run pipeline

:tada: This PR is included in version 1.1.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Requests should send a default user-agent

Requests made with okhttp 2.x do not set a proper user-agent. I would expect to see a default user agent. Maybe similar to the one used by picasso:
Dalvik/1.6.0 (Linux; U; Android 4.4.4; Nexus 5 Build/KTU84P)

Requests made with okhttp 2.x do not set a proper user-agent. I would expect to see a default user agent. Maybe similar to the one used by picasso:
Dalvik/1.6.0 (Linux; U; Android 4.4.4; Nexus 5 Build/KTU84P)

I want to know  why that dalvik user agent is coming ?
Is anybody can help regarding this?


New version: charmbracelet.sequin 0.1.0

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Automated with GoReleaser
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-11-18 12:16:53.276 [FAIL] Installer failed security check. Url: https://github.com/charmbracelet/sequin/releases/download/v0.1.0/sequin_0.1.0_Windows_x86_64.zip Result: 0x80004005
2024-11-18 12:10:07.032 [FAIL] Installer failed security check. Url: https://github.com/charmbracelet/sequin/releases/download/v0.1.0/sequin_0.1.0_Windows_i386.zip Result: 0x80004005

Automated error analysis suggests -1978335187 may mean Installer failed security check. Another script should retry this every 18 hours.
Automated error analysis suggests 80004005 may mean Resource missing
(Automated response - build 897.)

@wingetbot run

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-11-19 14:03:07.751 [FAIL] Installer failed security check. Url: https://github.com/charmbracelet/sequin/releases/download/v0.1.0/sequin_0.1.0_Windows_x86_64.zip Result: 0x80004005
2024-11-19 14:04:53.696 [FAIL] Installer failed security check. Url: https://github.com/charmbracelet/sequin/releases/download/v0.1.0/sequin_0.1.0_Windows_i386.zip Result: 0x80004005

Automated error analysis suggests -1978335187 may mean Installer failed security check. Another script should retry this every 18 hours.
Automated error analysis suggests 80004005 may mean Resource missing
(Automated response - build 898.)

@wingetbot run

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-11-20 09:13:41.872 [FAIL] Installer failed security check. Url: https://github.com/charmbracelet/sequin/releases/download/v0.1.0/sequin_0.1.0_Windows_x86_64.zip Result: 0x80004005

Automated error analysis suggests -1978335187 may mean Installer failed security check. Another script should retry this every 18 hours.
Automated error analysis suggests 80004005 may mean Resource missing
(Automated response - build 899.)

@wingetbot run

Automatic Validation ended with:

No errors to post.

(Automated response - build 899.)

Manual Validation ended with:

2024-11-25 17:38:15.881 [FAIL] Installer failed security check. Url: https://github.com/charmbracelet/sequin/releases/download/v0.1.0/sequin_0.1.0_Windows_x86_64.zip Result: 0x80004005

(Automated response - build 899.)

Manual Validation ended with:

2024-11-25 18:06:47.786 [FAIL] Installer failed security check. Url: https://github.com/charmbracelet/sequin/releases/download/v0.1.0/sequin_0.1.0_Windows_x86_64.zip Result: 0x80004005

(Automated response - build 899.)


feat: Add slack notification support for reports

[x] Add slack user and channel inputs to create.
[x] Fix slack notification. (https://github.com/rilldata/rill/pull/6005)
[x] Add slack user and channel to metadata.
[x] Add slack user and channel inputs to edit.
[x] Get feedback on design, the form is too long. Perhaps we can use the new multi entry input used in user invite? (Switched to MultiInput along with using superforms)

Done.
A generic Report sent is better IMO. If one of them fails to send we should get an error and show that instead.


Support for nested entities in QueryByIdAsync

Hi there,
I recently wanted to call QueryByIdAsync to grab opportunity details, although I also wanted a couple of Account level details, too.
I know I could have written the SOQL query myself and passed it directly into QueryAsync but I thought it was cleaner (from the consumer's perspective) to allow nesting entities.
See the ForceQueryBuilderTests for a super simple example.
Not sure if this is something you would be interested in? I thought it only polite to submit the PR either way =)

I greatly appreciate this pull request but, at this time, I don't think I'm going to merge. I'll continue to noodle on it though. Perhaps it would make a great sample!


pub get --offline for observatory build fails on debian package builder

Starting with commits
https://github.com/dart-lang/sdk/commit/b1197eb7141762fe42d7c738fa3395f3dc8c2b9d
and
https://github.com/dart-lang/sdk/commit/cf24b24f6dcf7031525d3e6ea55622b6c484cb46 (status files only)
the build of the Debian package for Dart has failed.  The pub get --offline command in building the observatory gives the error: "Incompatible dependencies on barback":
This error cannot be seen in the logs, you need to run the dpgk build step by hand to see it.
I am trying to fix it by deleting the entire checkout.
FAILED: gen/observatory_copy/runtime/observatory/packages.stamp
python ../../tools/observatory_tool.py --sdk=True --dart-executable /tmp/dart-1.25.0-edge.3b2625ccdec4a6850956ad01ee661dda8e0eff83/dart/out/ReleaseX64/dart_bootstrap --silent=True --stamp /tmp/dart-1.25.0-edge.3b2625ccdec4a6850956ad01ee661dda8e0eff83/dart/out/ReleaseX64/gen/observatory_copy/runtime/observatory/packages.stamp --directory /tmp/dart-1.25.0-edge.3b2625ccdec4a6850956ad01ee661dda8e0eff83/dart/out/ReleaseX64/gen/observatory_copy/runtime/observatory/ --command get
Command failed: /tmp/dart-1.25.0-edge.3b2625ccdec4a6850956ad01ee661dda8e0eff83/dart/out/ReleaseX64/dart_bootstrap /tmp/dart-1.25.0-edge.3b2625ccdec4a6850956ad01ee661dda8e0eff83/dart/third_party/pkg/pub/bin/pub.dart get --offline
output: Resolving dependencies...
Incompatible dependencies on barback:

observatory depends on it from source path
pub itself depends on it from source hosted

ERROR: Observatory failed to build. What should you do?

Revert to a working revision of the Dart VM
Contact zra@, rmacnak@, dart-vm-team@
File a bug: https://github.com/dart-lang/sdk/issues/new

ninja: build stopped: subcommand failed.
BUILD FAILED

The problem seems to have fixed itself, when I clobbered some directories.