When running ros install arrival , I get an error related to log4cl

Hello,
When running ros install arrival , I get an error related to log4cl

To load "arrival":
  Load 1 ASDF system:
    arrival
; Loading "arrival"
..[1/3] System 'arrival' found. Loading the system..
;
; caught ERROR:
;   READ error during COMPILE-FILE:
;
;     Lock on package SB-C violated when interning LAMBDA-PARENT while in package
;     LOG4CL-IMPL.
;   See also:
;     The SBCL Manual, Node "Package Locks"
;
;     (in form starting at line: 99, column: 0, position: 3779)
Aborted during step [1/3].
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD tid=80526 "main thread" RUNNING
                                                          {10044A0113}>:
  COMPILE-FILE-ERROR while
  compiling #<CL-SOURCE-FILE "log4cl" "src" "naming-sbcl">

Any idea where this comes from ?
Thanks

Please note that this repository is not maintained anymore. Maintenance of this library is performed in the https://github.com/sharplispers/log4cl fork.
I don't know what arrival is or how ros loads it but I suspect that the problem stems from the fact that log4cl uses internal interfaces of SBCL which changed in recent SBCL versions. The two solutions I can think of are

Use an older SBCL version
Use the master version of log4cl (from the https://github.com/sharplispers/log4cl fork)

Hope this helps.


WIP: integrating_other_schedulers

(for not messing with existing code yet)

@tholop it's not finished but you are welcome to review.


udp.Listener and udp.Conn should implement net.Listener and net.Conn

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
udp.Listener and udp.Conn should implement net.Listener and net.Conn
For udp.Conn several methods are missing like LocalAddr, RemoteAddr, SetDeadline, SetReadDeadline and SetWriteDeadline (see net.Conn). This could be fixed by proxying to the underlying net.UDPConn:
func (c *Conn) LocalAddr() net.Addr {
	return c.listener.Addr()
}

func (c *Conn) RemoteAddr() net.Addr {
	return c.rAddr
}

func (c *Conn) SetDeadline(t time.Time) error {
	return c.listener.pConn.SetDeadline(t)
}

func (c *Conn) SetReadDeadline(t time.Time) error {
	return c.listener.pConn.SetReadDeadline(t)
}

func (c *Conn) SetWriteDeadline(t time.Time) error {
	return c.listener.pConn.SetWriteDeadline(t)
}

The udp.Listener then needs to implement func (l *Listener) Accept() (net.Conn, error) {, returning a net.Conn instead of udp.Conn, as it is implemented currently (see net.Listener).
This way, the server.UDPEntryPoint can work on a net.Listener instead of a udp.Listener (see here).
As udp.Listener also implements func (l *Listener) Shutdown(graceTimeout time.Duration) error, this can be extended to stoppableListener interface, analogously to stoppableServer in the tcp package.
type stoppableListener interface {
	Accept() (net.Conn, error)
	Addr() net.Addr
	Shutdown(graceTimeout time.Duration) error
	Close() error
}

What did you see instead?
They do not implement net.Listener and net.Conn.
What version of Traefik are you using?
v.2.10.7
What is your environment & configuration?
Does not apply
If applicable, please paste the log output in DEBUG level
No response

Hi,
Thank you for your interest in the project.
While I understand the topic I'm uncertain about its necessity. Could you please provide further clarification?

We are looking into extending traefik to be connected to a SCION network. For this we need to incorporate a custom listener and this is way easier, if udp.Listener and udp.Conn implement the net.Listener and net.Con.
In general, for the sake of making traefik extendable, I'd propose to implement standart net interfaces.

Ok, I understand your need.
Feel free to open a PR for this, we would gladly accept it.
Nevertheless, I must warn you that, presently, the Traefik code isn't officially designed for extension.
This implies that in the future, there's a possibility of breaking signatures or interfaces without adhering to semver conventions.


fix: use hashchange event instead of popstate for IE/Edge compatibility

We do not even need to listen on all history change. We currently use popstate (checked for Accordion, Magellan, Reveal and Tabs) only for window.location.hash, and could rely on hashchange instead without any problems. No need for a polyfill.

See: https://github.com/zurb/foundation-sites/pull/11006#issuecomment-370193395
Events:

popstate: Edge 14+.
hashchange: IE 8+.

Updated components:

Accordion
Magellan
Reveal
Tabs

Previous PR: https://github.com/zurb/foundation-sites/pull/11006 (@DanielRuf)
Closes https://github.com/zurb/foundation-sites/issues/10771 (@hubert-ried)

@DanielRuf Yes this is the reason of this PR. We currently only need to listen on hash changes.


Introduce upload source and rukpakctl run

This PR introduces an upload source and a rukpakctl run command that makes use of the new upload source.
Closes https://github.com/operator-framework/rukpak/issues/472
The local source is a great way to help us get up and running quickly with a mechanism that enables direct usage bundle contents to a kubernetes cluster without requiring those bundles to be pushed to a git remote or an image registry. However, the local source's use of configmaps could only get us so far. Configmap size is restricted by etcd configuration (typically 2MB), so the local source could only support bundles up to 2MB in size. Some improvements for the local source are discussed in #464.
The upload source does not place this restriction on bundle size because it does not rely on etcd for storage of local bundle content.
An upload source enables bundle developers or other clients to directly upload bundle tar.gz files to inject them into bundles.
This introduces a upload manager service that:

accepts uploads for bundles with the upload source type
serves those bundles to provisioners that request them
garbage collects its local storage when bundle uploads are no longer needed

This also introduces client tooling necessary to actually exercise this functionality in a user-friendly way. It:

Adds rukpakctl run to create a BD with an upload source bundle, get the name of the generated bundle, and then upload the bundle contents to the upload manager, which then makes that bundle content available to the bundle provisioners.
Adds a simple library for running a port-forward to a specific service in the cluster (in this case, we use it to connect to the upload manager from outside the cluster)
A BundleUploader type that is essentially a small API for actually doing the upload. This is used in rukpakctl run and also in the e2e tests.

Hmm.... I wonder if the inclusion of the binary: {} struct in the Bundle API is causing go-spew (and thus the hashing for name generation) to change the output. I ran the e2e twice and I'm pretty sure this PR's code produced the same (incorrect, according to the tests) hash suffix for the generated bundle.

About the client tool, can it create the bundle instead of the bundle instance embedding a bundle? So it doesn't need to wait for the bundle name is determined. we can have another command to create the bundle instance that specify the bundle.

To actually run the bundle, we have to create a bundle instance that embeds the binary-type bundle. So at least in that case, I don't think we have any choice but to:

Create the BI
Wait for the bundle to exist
Upload the tar.gz for that bundle name

@joelanford Thanks!  I didn't realize that the bundleinstance has to embed the bundle.  I thought it could still reference a bundle.

LGTM.  The design refers to the configmap source.  Are we going to use the binary source instead of the comfigmap source there?

The design refers to the configmap source. Are we going to use the binary source instead of the comfigmap source there?

That's a great question. We probably need to re-open that design to discuss the best way to accomplish what it proposes while avoiding the concerns raised in #464.
I think using the binary source is definitely an option. But that is slightly more complex because the thing creating the ResolveSet bundle would have to perform the same upload function that rukpakctl uses.

Do we need to update the core webhook to also accommodate this new source type?

Is there anything I'm missing about what we'd need to check? The bundle spec can't change (and there wouldn't be anything really worth changing since binary isn't configurable)
And the upload manager http server forbids re-uploads of already unpacked binary bundles, so I think that covers the immutability from that perspective.

Adding godocs for some of the exported utility packages that were added.
Will do. They're all under the internal tree so I somewhat glossed over that, but I agree nonetheless. docs > no docs regardless of what/where.

Is there anything I'm missing about what we'd need to check? The bundle spec can't change (and there wouldn't be anything really worth changing since binary isn't configurable)

This is my bad: I forgot the core webhook just ensures Bundle spec immutability, and we moved the union type validation logic as oneOf CRD schema validations. I was talking about the latter when making that comment.

One additional thought I had -- do we ensure that the kube client proxy to the service tears down gracefully after ending the upload? I have seen issues with kubectl port-forward where it would close the stream but the localhost port would still be in use. This would prevent the command from being idempotent.

do we ensure that the kube client proxy to the service tears down gracefully after ending the upload?

If I understand your question, I think the answer is yes. We start a goroutine in the error group whose sole purpose is to wait for the context to be canceled and then close the stop channel.
https://github.com/joelanford/rukpak/blob/01f7e6f85dec68610bf9d0aa390fb991d9c28418/internal/rukpakctl/portforward.go#L104-L108
Then at the very end of that function we call eg.Wait() to block returning from Start() until all error group routines have completed.

CRD schema documentation that this service can be used to handle arbitrarily sized bundles to avoid the etcd size limitation?

I didn't call this out specifically in the "upload" source struct GoDoc because the "image" and "git" sources also support arbitrarily sized bundles. Maybe we should instead call out the local source's limitations?

Yeah, that sounds reasonable to me. That can be done as a follow-up anyways from my perspective.


Fixed ImageDomainValidator for GitHub URLs

by adding the missing /actions/ segment into the URL regex
GithubBadgeUrlRegEx.
Addresses https://github.com/NuGet/NuGetGallery/issues/8645

@lyndaidaii I modified the expression accordingly.

@nils-a, thank you for great contribution. awesome work, all look good to me.


Refactor and remove excessive calls of NOTIFICATION_THEME_CHANGED

Fixes (partially, see https://github.com/godotengine/godot/pull/62846) https://github.com/godotengine/godot/issues/50743
Fixes https://github.com/godotengine/godot/issues/62844
Fixes https://github.com/godotengine/godot/issues/61765
See the updated NOTIFICATION_THEME_CHANGED documentation for when it should be called.
After this is merged, https://github.com/godotengine/godot/pull/62846 can be merged, and https://github.com/godotengine/godot/issues/50743 can be closed.

Can you please rebase this now that https://github.com/godotengine/godot/pull/63318 is merged?

Remembered to update the documentation as well

Marking as a draft temporarily, I want to tweak the documentation a bit and double check this is the best way to do things before this is reviewed/merged

Rebased after https://github.com/godotengine/godot/pull/63595, and a few small improvements made. I'm thinking this is good enough for now, more refactoring and improvements can be done in future PRs.

Marking as draft again, hopefully for the last time :)
I made some changes last night that I want to test a little more thoroughly and document a little better.

Ready for review :P

@YuriSizov changes made :)

Also needs a rebase, then should be good to go

██████╗░███████╗██████╗░░█████╗░░██████╗███████╗██████╗░
██╔══██╗██╔════╝██╔══██╗██╔══██╗██╔════╝██╔════╝██╔══██╗
██████╔╝█████╗░░██████╦╝███████║╚█████╗░█████╗░░██║░░██║
██╔══██╗██╔══╝░░██╔══██╗██╔══██║░╚═══██╗██╔══╝░░██║░░██║
██║░░██║███████╗██████╦╝██║░░██║██████╔╝███████╗██████╔╝
╚═╝░░╚═╝╚══════╝╚═════╝░╚═╝░░╚═╝╚═════╝░╚══════╝╚═════╝░

... and now a check is failing 🙃

Poke-poke. Would be great to merge this soon!

Poke-poke. Would be great to merge this soon!

Sorry 😅
I'll try and get this fixed today. I'd love to spend more time contributing to Godot, I've just been really busy with work and other projects I'm working on 😃

Thanks!


Any proposed solutions?

I'd be interested in know/help as a lot of the articles from my site https://vuejsdevelopers.com have been stolen by these sites as well.

I started banning morioh on FB Python group where they posted a lot. A final solution would be their hosting provider action if he cares about it in any way.

I've got a FB group too but they're continually creating fake profiles to post


Late bindable index signatures on classes vs override and noImplicitOverride

🔎 Search Terms
override ambient type declaration class dts noImplicitOverride late bindable index signatures
🕗 Version & Regression Information

This changed in commit or PR: https://github.com/microsoft/TypeScript/pull/59860

⏯ Playground Link
https://www.typescriptlang.org/play/?noImplicitOverride=true&ts=5.8.0-dev.20241128#code/PTAEAEDsHsEkFsAOAbAlgY1QFwPIDcBTAJyNQBMCAuULIgVwIChH1pIBnLUdgT3mt7wARtGSgAvKADKfEcgAUASgDczdMgCG7dqABCWggEZQAb0ahQAbUEBdJaYC+jJy03bQAEWKpCZYwQAPLAJIMh19diNTc1BoQhJyAitbexMnF3UtcIMAJmiLaz47RUdnNTcdL1JfPMDg0OzIvLMClJK0stcsvQMAZlKu9yqfAjJ+upCwnsj+ltj40gpkotT0oA
💻 Code
// @noImplicitOverride: true

const sym: symbol = Symbol();

class Base1 {
  [sym]() {}
}

class Derived1 extends Base1 {
  override [sym]() {}
}

class Base2 {
  [sym]() {}
}

class Derived2 extends Base2 {
  [sym]() {}
}

class Base3 {}

class Derived3 extends Base3 {
  override [sym]() {}
}

🙁 Actual behavior
No errors are raised
🙂 Expected behavior
I'd expect either:

errors on override with dynamic names
errors raised on override members without override under noImplicitOverride

Additional information about the issue
I implemented the first suggestion here https://github.com/microsoft/TypeScript/commit/f33497877dd6b723e4d9169a431c58083556dae9 but since I don't know if this is the desired behavior I didn't open a PR with this change yet, cc @weswigham

Yeah, @Andarist I'm just gonna go ahead and say we can issue errors on override on dynamic-named class members. It's not a regression, since we haven't issued errors on them before (we just also didn't check them before), but we probably should, since it likely indicates that you don't realize you're not actually overriding a specific member. We also just straight up don't allow override on actually declared index signatures, so allowing it on implicit ones would be wonky. Feel free to open a PR with your commit.


contours, hierarchy = cv2.findContours(mask, 1, 2) ValueError: too many values to unpack (expected 2)

am trying to test this example and i got this error
Traceback (most recent call last):
File "ex_particle_filter_object_tracking_video.py", line 70, in
if(my_mask_analyser.returnNumberOfContours(frame_mask) > 0):
File "/usr/local/lib/python3.6/dist-packages/deepgaze/mask_analysis.py", line 36, in returnNumberOfContours
contours, hierarchy = cv2.findContours(mask, 1, 2)
ValueError: too many values to unpack (expected 2)
please how can i resolve this error

Hi @SolomonAvion please report the version of python, OpenCV, and deepgaze that you are using.
This is most likely a compatibility problem.
If you have a recent version of OpenCV it is possible that it is not compatible with deepgaze 1.0 and you have to install deepgaze 2.0  as reported in the README.

thanks, i have resolved it by adding a third value in front of the other two also solved the problem for me
like this
_,contours, hierarchy = cv2.findContours(mask, 1, 2)


Finalize the project

Code Refinement:

Review your code for any potential improvements or optimizations.
Ensure that the code follows best practices and coding standards.

DoD:
Finalizing and Building The Image

commit:
https://github.com/youssef456/RTOS_Embedded_Linux/commit/290c9ac0fecfe038dd561256e0339d397bb525c8


docs(readme): added instructions for enabling DM functionality

Followed the instructions, and I was unable to DM the bot. Found out that I needed to enable this.

Thanks!


nix-serve: Make test reusable and expose linked nix in passthru

Description of changes
This makes the nix-serve test available in a way that allows an overlay to affect the test.
For instance, we may use this in Nix's own CI as an example of a package that uses the Perl bindings.
Example:
  # pkgs has an overlay applied to it to set `nix`
  checks.${system}.nix-serve =
    assert pkgs.nixosTests.nix-serve.config.nodes.machine.services.nix-serve.package.nix == self.packages.${system}.nix;
    pkgs.nixosTests.nix-serve;

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks!


Dynamic Structured Tool returndirect return Invalid Tool Input

Hello,
I have a Dynamic Structured Tool, which output I want to return directly, but sometimes my Agent runs into an Error, while filling the Tool Input. I get a Invalid Tool Input exception, but I don´t want to return this Toolexception directly. I need handle this parsing error while occuring, preferably the agent should fix himself by passing the exception back to him and trying again. How can i achieve this behaivor?

I don´t see where I can edit the _call function.


How to set up Locales

Hi, I can't find a way to use the calendar in spanish, set the locales. Thanks!

@brunoravizzinidev there is no way to handle locales in this component, in 5 days we will be able to update the component, and let us update you here.

@brunoravizzinidev released 3.2.0 with language support.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-25-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3483

Questions ?
Please refer to the Backport tool documentation


Plugin settings and SDK config path storing

Description
An option should be available to specify the file location to place the generated config.
This PR adds the initial base for our plugin settings.
A few notes on the Settings API.

We must declare a class that extends Configurable (AeroGearMobileConfigurable) which returns our settings component and reacts to saving/resetting/isModified events.
Storage is managed by AeroGearMobileConfiguration which implements PersistentStateComponent and the storage annotation. Any properties on AeroGearMobileConfiguration will be saved (serialized to xml) on IDE exit in a file called AeroGearMobileConfiguration.xml. Reloaded again on IDE startup.

Additional Notes
JIRA Ticket - https://issues.jboss.org/browse/AEROGEAR-1919

@maleck13 Yes this just covers the storing of the setting. This piece of work was ready and standalone so I decided to get it reviewed.

Am I right in assuming this doesn't actually get the config yet?

But thats good question how config should be loaded. We need to have project structure and some .xml file which should be loaded first and configuration persisted.
But other question is when we create project from scratch with wizzard from where config.xml should be loaded or generated dummy one?


Disabled environment still checks for DSN

Raven 2.XX.0 configured not to capture errors: DSN not set keeps showing in development event thought the environment is disabled using config.environments = %w[production]
I would expect the config.environments to be the source of truth on enabled/disabled environments, and this should be checked before the DSN.
Is this the intended behaviour?

quite true.
It still reports below at development env
Raven 2.11.0 configured not to capture errors: DSN not set

Though my config
Raven.configure do |config|
  config.environments = %w(staging production)
  config.sanitize_fields = Rails.application.config.filter_parameters.map(&:to_s)
end

I'm finding this as well. It looks like this has come up before (#607, #793) and the best workaround so far is to set the logger to /dev/null

I explained once why this is clearly buggy behaviour but I didn't get any answer so far.

Yeah also followed up on surprisingly-was-closed #793 - agree with comments here - workarounds like logger to dev/null are IMHO hacks which although they might work, shouldn't be needed.

For anyone running into this, here is a workaround:
raven_environments = %w[staging production]

Raven.configure do |config|
  config.silence_ready = !raven_environments.include?(Rails.env)
  config.environments = raven_environments
end

Nonetheless, I agree that ignoring unspecified environments should be the default behavior.

Thanks for reporting, this issue should be fixed by https://github.com/getsentry/raven-ruby/pull/1000


Cannot determine amount of signers for TX Building from Utxos

While Building a Tx from UTxOs There's no way to provide the correct amount of signers to provide to balanceTx method.
Suggestion: Utxo SelectionStrategy should provide the number of different (unique) addresses used in Tx and provide it to signTx method automatically using the current functional methodology.

Additional utxos selected during balanceTx don't get added to the TxBuilderContext's utxos list. Need to verify


Support for """ comments before a query

Thank you for this plugin!
I am wondering if there can be support for "documentation comments" as per https://dgraph.io/docs/graphql/schema/documentation/#schema-documentation-processed--by-generated-api
When I use them, they build OK and insert the comments into the generated class's JavaDoc, but the parsing describes and error and subsequent syntax highling fails:
When inserting a """ comment before a query, such as:
"""
    My doc comment
"""
query ...

I get the following error message at end of the last """: directive, enum, input, interface, scalar, schema, type or union expected, got 'query'. There is no syntax highlighting after this error in the GraphQL file.
Normal comments with # work fine but they don't get inserted into the generated class's JavaDoc.
Operation system: Windows 10
IDE name and version: Android Studio Dolphin | 2021.3.1
Plugin version: 3.3.0

Hi @TheNavigateur! Documentation strings for operations are not supported in GraphQL.
https://spec.graphql.org/October2021/#sec-Descriptions
https://spec.graphql.org/October2021/#sec-Language.Operations
For example, if you try to reformat that snippet with the GraphQL plugin for Prettier, you'll get the following exception:
"""
    Comment
"""
query {
    node {
        id
    }
}

Syntax Error: Unexpected Name "query". (4:1)
  2 |     Comment
  3 | """
> 4 | query {
    | ^
  5 |     node {
  6 |         id
  7 |     }
SyntaxError: Syntax Error: Unexpected Name "query". (4:1)
  2 |     Comment
  3 | """
> 4 | query {
    | ^
  5 |     node {
  6 |         id
  7 |     }


Rename EIP150 to Tangerine Whistle.  Fixes #221

What was wrong?
The Tangerine Whistle hardfork was called EIP150 in the code.
How was it fixed?
Refactoring.
Cute Animal Picture

Thanks @NicolaiSoeborg


Fixed volume stats

Description

This fixes a bug where the volume statistics for the physical size is incorrect

Fixes: #3416
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Screenshots (if appropriate):
How Has This Been Tested?

This was tested by verifying that the vmdk file size in vcenter corresponds to the physical volume size in the ui of the management server. Please note that vcenter displays kilobytes where
Cloudstack management server displays kibibytes on linux.

@Spaceman1984 is this meant to go in 4.14, 4.13.1 or else?
@blueorangutan package

@andrijapanicsb a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@Spaceman1984 is this meant to go in 4.14, 4.13.1 or else?
@blueorangutan package

Looks like 4.13.1

@Spaceman1984 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@Spaceman1984 pls don't quote the reply with the blue monkey, it triggers re-build or whatever command was there for "him"...
I've killed both jobs, running a new one again
@blueorangutan package

@Spaceman1984 pls don't quote the reply with the blue monkey, it triggers re-build or whatever command was there for "him"...
I've killed both jobs, running a new one again
Ok

@blueorangutan package

@andrijapanicsb a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-558

@blueorangutan test

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-738)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 28260 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3798-t738-kvm-centos7.zip
Smoke tests completed. 77 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

There is an issue here, this fix doesn't take into account when the volume has a different name than root, and it also doesn't work for volumes that are not attached to a vm. A rework is in progress


Use 'vulkan-spirv' as the compiler target for consistency

This is a spin-off of #5837.

Are there other vulkan-* configurations?

Not right now. We are only using vulkan-spirv. (There is metal-spirv but it does not fall into this regex.)


Release script does not work for Windows containers

Repro steps

Install Docker, set up Windows containers
Follow deployment instructions, run release.cmd

Expected behavior
Code gets published to Docker hub
Actual behavior
docker: Error response from daemon: failed to create endpoint test on network nat: Windows does not support host IP addresses in NAT settings.
Running build failed.
Error:
System.Exception: Docker run failed
   at FSI_0005.Build.clo@290-21.Invoke(Unit _arg7) in <my project location>\build.fsx:line 298
   at Fake.TargetHelper.runSingleTarget(TargetTemplate`1 target) in D:\code\fake\src\app\FakeLib\TargetHelper.fs:line 626

Known workarounds
Switch to Linux containers.
Related info
I am running this on Windows 10 x64.
Ideas
I do not know if it is expected behavior. If it is, then it is worth mentioning in docs.

not supported - not fault of SAFE stack

I wrote a comment into the docs. thanks


Add http client and insecure tls tests for registry client

<!--  Thanks for sending a pull request!  Here are some tips for you:
1. Make sure to read the Contributing Guide before submitting your PR: https://github.com/helm/helm/blob/main/CONTRIBUTING.md

Needed a big refactor of https://github.com/helm/helm/pull/9564 after OCI moved away from experimental.  Want to give @chenwng credit for most of the implementation details.

**What this PR does / why we need it**:

Adds features to the registry client to allow:

* HTTP OCI registries
* custom CAs
* key/cert authentication

Will enable features being added to the CLI when ready

**Special notes for your reviewer**:

**If applicable**:
- [ ] this PR contains documentation
- [ ] this PR contains unit tests
- [ ] this PR has been tested for backwards compatibility

@runyontr thanks for the contribution. There is a collaborative effort ongoing right now with this similar feature that is living on the oci-transport-refinement branch. The latest PR to that branch is https://github.com/helm/helm/pull/11599

@sabre1041 Let me know how would be best to collaborate.  Happy close to close mine and get the work into your branch if you want.  I'd like to get the http client work in to unblock some work on fluxcd/source-controller, and don't see that specific capability in your branch.

TLS is already enabled in this branch (see test cases in client_tls_test.go.

Tracking that TLS was already implemented and working. I believe this adds the following:

Plain HTTP client
Plain HTTP Client tests
Custom CA TLS Client tests
InsecureSkipVerifyTLS Client Tests

Happy new year @runyontr. Made some comments in cmd. I also wanted to review pkg but it seems not ready yet.


Build Test: Windows MinGW/Cygwin

Build process fails on MinGW due to missing pthread.h. I need to investigate this issue further.

Windows build requires wrapped pthread calls, possibly using macro to separate Linux/Win code, where Windows should refer to WINAPI solution. CMake should generate working VS project. MinGW is questionable now.

pthread.h is just Unix(POSIX) only, needs to use Win32 Threads, only CYGWIN could build probably, but not sure.


Correction for raw affiliation Ecole normale supérieure de Fontenay-Saint-Cloud

Correction needed for raw affiliation Ecole normale supérieure de Fontenay-Saint-Cloud
raw_affiliation_name: Ecole normale supérieure de Fontenay-Saint-Cloud
new_rors: 01m0z6m03
previous_rors: 01dp7jr64
works_examples: W2953328944;W3162704705
contact: 57b3bfc0e14d28a6905c97fdd578e5e4:ee8499687d2e47026b789bd4deaa @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Update issue template

The issue template currently asks about Version and OS under Specifications. This could be updated to something like:
## Specifications
- Browser (vendor/version):

Resolved in PR


[SPARK-46722][CONNECT] Add a test regarding to backward compatibility check for StreamingQueryListener in Spark Connect (Scala/PySpark)

What changes were proposed in this pull request?
This PR proposes to add a functionality to perform backward compatibility check for StreamingQueryListener in Spark Connect (both Scala and PySpark), specifically implementing onQueryIdle or not.
Why are the changes needed?
We missed to add backward compatibility test when introducing onQueryIdle, and it led to an issue in PySpark (https://issues.apache.org/jira/browse/SPARK-45631). We added the compatibility test in PySpark but didn't add it in Spark Connect.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Modified UTs.
Was this patch authored or co-authored using generative AI tooling?
No.

cc. @zsxwing @viirya @anishshri-db @HyukjinKwon Please take a look. Thanks!


SLIM-850 Updates default security keys to RSA encrypted versions

This pull request makes the build fail.

This pull request makes the build fail.

All is well.


Batched tile APIs: promote to beta, access mesh export service

Various applications have copy-pasted code to implement computeSpatialTilesetBaseUrl using the mesh export service.
Provide an obtainTilesetUrlFromMeshExportService function in the package they can use instead, to avoid proliferation of outdated/buggy copies. Caller can supply access token and url prefix.
Promote all alpha APIs to beta.

If I understood it correctly

Right, e.g.:
initializeFrontendTiles({
  computeSpatialTilesetBaseUrl: async (iModel) => {
    return obtainTilesetUrlFromMeshExportService({
      iModel,
      urlPrefix: process.env.IMJS_URL_PREFIX,
      accessToken: getAccessTokenFromSomewhere(),
  },
});

Only iModel is required.
I amended the docs to say you can omit computeSpatialTilesetBaseUrl but failed to actually make it optional and provide a default, fixing that now.

Merging master pulled in this new test that fails to compile. @kabentley?
--[ FAILURE: core-full-stack-tests ]-------------------------[ 7.52 seconds ]--

src/backend/AzuriteTest.ts(43,11): error TS2322: Type '{ application: string; description: string; format: string; blockSize: string; }' is not assignable to type 'Metadata'.
  Object literal may only specify known properties, and 'application' does not exist in type 'Metadata'.

@Mergifyio backport release/4.0.x


feat(mssql): add MS SQL Server driver [WIP]

Closes #771

@B4nan Would love to see more work done on this

@B4nan Would love to see more work done on this

Well, then do the work on this :] For me this have very low priority. I did gave it a try and rebased to latest v5 but it did not really help, there are more blockers than just the schema generator, and for me there are too much unknowns as I never used mssql.

You asked... I've delivered.
https://github.com/mikro-orm/mikro-orm/pull/3023

Codecov Report

Merging #1375 (a64fea6) into master (60ec052) will decrease coverage by 0.48%.
The diff coverage is 79.65%.

@@             Coverage Diff             @@
##            master    #1375      +/-   ##
===========================================
- Coverage   100.00%   99.51%   -0.49%
===========================================
  Files          193      204      +11
  Lines        11904    12185     +281
  Branches      2748     2802      +54
===========================================
+ Hits         11904    12126     +222
- Misses           0       45      +45
- Partials         0       14      +14

Impacted Files
Coverage Δ

packages/knex/src/AbstractSqlConnection.ts
100.00% <ø> (ø)

packages/mssql/src/types/UnicodeStringType.ts
13.79% <13.79%> (ø)

packages/mssql/src/types/TimeStampType.ts
29.03% <29.03%> (ø)

packages/mssql/src/MsSqlSchemaHelper.ts
46.66% <46.66%> (ø)

packages/mssql/src/MsSqlPlatform.ts
97.50% <97.50%> (ø)

packages/mssql/src/MsSqlQueryBuilder.ts
97.61% <97.61%> (ø)

packages/mssql/src/MsSqlDriver.ts
97.72% <97.72%> (ø)

packages/mssql/src/MsSqlConnection.ts
97.82% <97.82%> (ø)

packages/core/src/EntityManager.ts
100.00% <100.00%> (ø)

...ges/core/src/events/TransactionEventBroadcaster.ts
100.00% <100.00%> (ø)

... and 11 more

Continue to review full report at Codecov.

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

The clearDatabase calls are taking a lot of time (>500ms). Its pretty much all from the truncate.sql script. Will try the other suggestions from https://stackoverflow.com/questions/253849/cannot-truncate-table-because-it-is-being-referenced-by-a-foreign-key-constraint

All the mapped types you added seems to be not needed, I guess that was for some initial implementation, right? Will remove them, all the tests are passing just fine without them. If they are needed, we need a test case that shows why we need them.
Will try to get the schema generator working, for now with disabled FKs, given we can't even define all of them in the mssql-schema.sql file.

@B4nan

All the mapped types you added seems to be not needed, I guess that was for some initial implementation, right?
They are absolutely needed!

MSSql uses N-types (Unicode types) which is different from regular strings (Non-unicode types). If you have no ability to apply Unicode types then languages like Chinese will fail. This is incredibly important.

They are absolutely needed!

I guess you are missing my point. Those types should be applied to all strings/dates, right? We dont need them if things work out of box the same way for all strings/dates.
If you think they are still needed (with my latest changes), please provide test case that proves it. I already removed them, everything is passing just fine. I dont want to bend indernals via custom types - that is an extension for users, internally we can find more performant ways to do things.

Yes, I will add some tests that will cause the default assumption of Unicode to fail.
You either need to have a Unicode type or a NonUnicode type as MSSQL commonly uses both.

@UTGuy I guess I got confused by what the unicode strings mean. Initially I thought the other "regular" strings will support only ASCII, but thats probably not true? I mean you can put things like the czech characters there or not? e.g. ěščřžýáíéůú? Those (and similar chars used e.g. in Slovakia, France, etc) are in my eyes something to support out of box with the default string mapping. If its just about chinese and special chars or even emoji, we don't need that and having the opt in type implementation sounds good to me.

@B4nan is this still work in progress and or other plans to support mssql in the near future?


Raw content displayed in a default sized window

The same should depend on the content with the same mechanism as source-pane when opening as raw content
number of lines +2

could be replaced by issue https://github.com/solid/solidos/issues/97


Added feature to overwrite JS/CSS of Bundles in app/Resources (like Twig-Templates overwrite mechanism)

added feature to allow the overwrite of  bundle's JS/CSS-Files directly (by Filename) or for whole directories (/css/*)
added feature (addLoadPath) for configuring SASS' loadPath to look for files (partials) which are included by @import: you can tell /usr/bin/sass where to look for these partials by config.
wrote unit-tests for that
did something with the mode of most directories and files. Hopefullly I fixed it correctly. If not: Please tell me, the correct mode. I will reset it then.

Updated pull request and changed files as suggested.

This is a big patch. Do I understand correctly that you want to be able to replace partials called from inside a third party SASS file?

Hi Kris,
yes. That is right. We have exactly that use case in our environment.
The use case is:
A central design department creates partials and sass-css-files for a
white-label-page and in several local design-departments the
"designers" should be enabled to just modify these partials on the
first layer if needed.
The patch to the filter is placed in the bundle because I didn't want
to have a dependency from the bundle to ascetic for now, because we
are currently using my fork in production and would like to switch if
it is in the release.
Christophe already suggested to bring it to assetic which would be really easy.
If you tell me were I can document the feature, I won't hesitate to
start documentation.
Regards.
Mike
2011/11/22 Kris Wallsmith
<EMAIL_ADDRESS>
This is a big patch. Do I understand correctly that you want to be able to replace partials called from inside a third party SASS file?

Reply to this email directly or view it on GitHub:
https://github.com/symfony/AsseticBundle/pull/40#issuecomment-2835275

Something new about this feature ? :-)
Thanks.


Do not add libs/ to .gitignore

As libs/ was removed in 663c75d we do not need to gitignore libs/
anymore.
See also #3593

Indeed.


Fix the WI docs to include annotating the KSA

The step of annotating the KSA was missing from the documentation for setting up Porch with Workload Identity.

Yes, I did test it and it worked. Alas 16 hours later #3390

Looked a bit more into this. Which command are you running? The porch/scripts/create-deployment-blueprint.sh scripts should add the annotation to the SA, and it is used by the push-and-deploy make target.  Do you have a project configured in your gcloud (i.e. gcloud config get-value project returns something)?

I just followed the documentation. I didn't use a script or a make target.
https://kpt.dev/guides/porch-installation?id=workload-identity
That section is, seemingly erroneously, under "Running a Custom Build of Porch", which I am not doing. I probably should have moved it out of that section. It really belongs in the section on registering repos (so does the OCI part). But I didn't want to undertake reorganizing all the docs, I just wanted to push a quick fix out.

I see that this section is perhaps intended to be in there with the make push-and-install - but I don't see using WI and building a custom porch as related. Maybe we do need to re-org the docs rather than just add this line.

Yeah, we need to restructure the docs a bit. But lets merge this now.


Create EquipmentBinaryPackage

For New Contributors
How to contribute
Description

Intended Design

Location

Related Issues

Requirements

Additional information

Definition of Done

[ ] Class level comments exist for all new classes.
[ ] XUnit tests exist for every method that does not require the game to be ran.

Duplicate of #326


chore: remove webpack configurations from demo apps

The nativescript-dev-webpack plugin should add them automatically. That
way we won't have to update them manually with every new version of the
plugin.

test

Maybe add them to .gitignore so we do not commit them in the future by accident?

test


Generate HandlerConfig.gen.go via tools/codegen/cmd/bootstrap

Release note:

release-note-none

This change is

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-presubmit.sh
21e76f8c6117cef72be1b7a5de3379e354fd2c06
link
/test mixer-presubmit

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. I understand the commands that are listed here.

/approve

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-presubmit.sh
2d1101943bb82a6a252bd37d85401cbcf75a807e
link
/test mixer-presubmit

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. I understand the commands that are listed here.

@guptasu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-e2e-smoketest.sh
a54b60a83adf3c4f89e39d042fe075c0149755aa
link
/test mixer-e2e-smoketest

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. I understand the commands that are listed here.

doing it different way.


RFC: Composable Modifiers

I've been thinking of ways to make modifiers better. I wrote up some notes on how I think this can be done and would love some discussion (especially if @plusvic thinks this is a terrible idea or not =b). My notes are at https://gist.github.com/wxsBSD/44aa8b8133e3ea96e738b66ec1c600f2 and if this sounds like something reasonable I'm willing to put in the effort to get it working.

The design looks nice, and would certainly use that idea from the very beginning if I had envisioned that modifiers could get more complex over time.  However, I'm worried about two issues:

Backward compatibility. There are literally hundred of thousands YARA rules out there, and a large percentage of them use string modifiers. Rewriting all those rules manually is not an option, for a change like this we would be forced to provide additional tooling for automating the rewrite. From time to time we can afford to introduce some backward incompatible change, like adding a new keyword. The introduction of the "base64" keyword for example broke only a handful of rules in VirusTotal Intelligence, that can be assumed because you can fixed by hand in a few minutes. But the breakage in this case would be a lot larger.

Added complexity vs added value. This feature would be certainly helpful if the plan is adding even more modifiers in the future. But right now I'm leaning towards the opposite: being extremely cautious about adding new modifiers. That's why I haven't decided anything yet about the "rol" modifier, I'm putting it on quarantine (a popular word these days) until I have a clear strategy.  So far, my impression is that the "rol" modifier is a very niche feature. I had doubts about the "base64" modifier too, but I must admit that I've seen a bunch of rules where people use base64-encoded strings and that helped to change my mind. Also, this kind of modifiers that take one string and produce a single string are a nice-to-have but not strictly necessary, as you can always do the operation by yourself and use the resulting string.

PD: I just saw this other PR https://github.com/VirusTotal/yara/pull/1248 and it becomes clear to me that we either implement this proposal and add more modifiers, or stop adding modifiers. For the time being I prefer the latter.

Backward compatibility

This is a big concern for me too. I think finding a way to maintain existing behavior is a hard requirement. I have ideas on how I can do this but I haven't fully thought them through yet. I'm going to think about how I might do this in a backwards compatible way, and if I can't then I'll drop the idea.

Added complexity vs added value

I too question the value of some of these modifiers (rol and add specifically). I think we should continue to be cautious about adding them for now, but if we can get composable modifiers working we can require that they be used only in a composable way (if multiple modifiers exist).

I think that having clearer string modifiers is useful.
To compose the strings without breaking backwards compatibility,


Filtering by Enum as a numeric values

Hi
I am working on API with OData V3.
I want to make a query with a enum value .. the normal thing that I know that the enum is a numeric values .. so if I want to use it in a filter I have to send it like that
$filter=PatientDetectingState eq 1
but this filter throws an error:

"The query specified in the URI is not valid. A binary operator with incompatible types was detected. Found operand types 'Edm.String' and 'Edm.Int32' for operator kind 'Equal'

But if the filter was like this:
$filter=PatientDetectingState eq '1'
it works fine.
Ten enum field type is a Edm.String in metadata .. why ?!!

Now I need to make my filter in Simple.OData.Client like that
obj.Filter(it=> it.PatientDetectingState == PatientDetectingStates.Closed)
.FindEntriesAsync()

I tried to this  but I don't understand 'revise your service metadata' means
I tried
config.EnableEnumPrefixFree(true); in WebApiConfig.cs but didn't work
I tried this  but didn't work either
How can I do it ?
I am working on

Microsoft.AspNet.WebApi.OData 5.2.3
Simple.OData.Client 5.6.2
Microsoft.Data.OData 5.8.4

Looks like the problem is caused by PatientDetectingState property definition. It is assigned to Edm.String, not the actual enum type.
If you check OData TripPin sample, you will see that for Person entity type has "Gender" property assigned to a proper enum type:
Property Name="Gender" Type="Microsoft.OData.Service.Sample.TrippinInMemory.Models.PersonGender" Nullable="false"
As long as it is set to a string, you can't use it as enum in your queries.

Looks like the problem is caused by PatientDetectingState property definition. It is assigned to Edm.String, not the actual enum type.
If you check OData TripPin sample, you will see that for Person entity type has "Gender" property assigned to a proper enum type:
Property Name="Gender" Type="Microsoft.OData.Service.Sample.TrippinInMemory.Models.PersonGender" Nullable="false"
As long as it is set to a string, you can't use it as enum in your queries.

Yes I think this is the problem. But I don't know how to change it and assign it to it's type.

This has to be done on a server side. Simple.OData.Client only deals with client-side request generation.

Thanks @object. I have the same question as @AmirImam. How do you assign to a proper enum type on the server side?
For example, I have the following:
public enum Status {     One,     Two,     Three }
public class Entity {     public Status Status { get; set; } }
ODataModelBuilder builder = new ODataConventionModelBuilder();
builder.EntitySet<Entity>("entities");
IEdmModel model = builder.GetEdmModel();

You can check official OData samples: https://github.com/OData/ODataSamples
For example, TripPin sample implements OData enums.

Thanks @object. Looks like that's for OData V4. I have V4 working I'm looking for pointers for OData V3.


Spanner: We may not be retrying requests when WithSessionExpiryChecking() fails with UNAVAILABLE

We got a customer issue reported where they are using the SpannerDataReader and they see an error in their logs:
Exception details: google.Cloud.Spanner.Data.SpannerException: The service is currently unavailable. This is a most likely a transient condition.

---> Grpc.Core.RpcException: Status(StatusCode="Unavailable", Detail="GOAWAY received", DebugException="Grpc.Core.Internal.CoreErrorDetailException:

There doesn't seem to be any impact on the workload from this error other than it taking a long time when this happens. Looking at the code, an UNAVAILABLE error is caught and retried. But that's only if hasNext is computed and _safeToRetry is set.
I don't think it's getting this far based on the below stack trace because I see WithExpirationChecking().

My question is will the RPC be retried elsewhere even if the UNAVAILBLE error is not caught in this loop?
CC @olavloite

Maybe we need to implement similar logic to that of Node.js that @olavloite worked on a few months ago.

I'll try to take a look today.

No, if the RPC isn't retried there, I don't think there's anywhere else it would be retried. I don't think anything else would have enough information to retry it sensibly. Note that retrying streaming RPCs is inherently somewhat different to retrying regular ones.
I don't think this has anything to do with WithSessionExpiryChecking though - the only impact of that method should be to mark the session expired if the exception is "Session not found" (which it isn't in this case). All exceptions are just passed through, so it shouldn't affect retry at all.
This exception propagating suggests that either:

We received more than 512 partial result sets since the last resume token (so we no longer have a valid resume token) and then an error occurred
Two RPCs failed in a row

The first of these is complicated to go through - I'd need to look much more closely at the code. It seems much more likely that we've received two RPC failures in a row, despite backing off for as long as the first RPC said we ought to.
The part about hasNext is a red herring, I believe - _safeToRetry starts off as true. So even if the very first request fails, we'll still retry - but if that second request fails as well, that won't be retried.

Thanks @jskeet, that makes sense. I missed the fact that _safeToRetry is true to begin with.
I think you're right that it's way more likely that they received two failures in a row.
I will mark this as closed since there's no action we can take. I might reopen it if more information comes up.

@olavloite did some investigations and he was able to reproduce the issue with two consecutive UNAVAILABLE errors being returned.
From his experience no other Spanner client libraries has this restriction. His recommendation was to remove _maxConsecutiveErrors and retry until the total timeout is reached.
@jskeet, is there a reason that the C# client chose this path? Do you see any problems with changing this logic?
This issue is still impacting the customer.

@skuruppu: I suspect when I implemented SqlResultStream, I was either taking my cue from the Java code at the time (which may well have changed since then) or from the .NET code at the time (which we were fixing, basically).
I think if we retry until the total timeout is reached, we should probably add some sort of minimum sleep time in there. At the moment, if the failure doesn't indicate how long to wait for, we don't wait at all - which could lead to us basically hammering a failed node (or whatever) as hard as we could. The "max consecutive errors" prevents that, so if we remove that protection we should add something else in.

Ah ok, so I was thinking we'll implement it with exp backoff so that should address your concern.
@olavloite would you be able to take this on?

Ah figured it out!


Added setting for Proxy using.

This setting allows to set a Proxy string for the bot to use.
This way, on creating the bot I can add it like:
b, err := tb.NewBot(tb.Settings{
	Token:  "myt0k3n",
        ...
	Proxy:  "http://proxyhost:port",
})

And behind, it will create a client with a transport using the proxy as client.Post(). If Proxy were not defined, usual http.Post() would be used.
Similar implementation could be used for Bot.sendFiles(). But I haven't had time to try and test an example of those, so it's pending.

Hi.
Does it really need? Default transport supports HTTP_PROXY env var from the box.
https://golang.org/pkg/net/http/#RoundTripper

@tucnak This can be closed.

Oh yeah, definitely. Cheers mate. @MarAvFe closing this in favour of #132


Use the floating bazel version on CI.

Ideally I would like to run both the latest version of bazel and the oldest "supported" version of bazel.


Project edit page - data users

Implement the code to allow a user to add many read-write data users and many read-only data users. The value entered for a "data user" will be their netid.
This should be a comma separated list for the moment.
Acceptance Criteria:

[ ] There are two text boxes that allow the user to enter a comma separated list

Hey team! Please add your planning poker estimate with Zenhub @bess @jrgriffiniii @kelynch


Set custom size in px

Hi. qrcode generated with 50x50 px size. It's so small!
I want set custom size, for example 200x200 px

v0.0.3 released.
Qrcode::make('QR Code', 'url')
    ->indexSize(100)
    ->detailSize(500)


Readme incomplete

Thank you for your excellent work. In the Readme, you should probably specify in the example:
$client = new RestClient\Client('https://raw.githubusercontent.com/romanpitak');
instead of:
$client = new Client('https://raw.githubusercontent.com/romanpitak');
If you use composer to pull out and install dependencies, the simple new Client() call won't work. Thanks

I did consider that when I wrote it, but to keep the example small I chose to omit insignificant details such as the vendor/autoload.php inclusion and the namespace definition.
Thank you very much for the suggestion though and thanks for caring about the open source software.


"could not obtain update details"

What model of system are you using?

[ ] Old 3DS
[x ] Old 3DS XL
[ ] 2DS (non-XL)
[ ] New 3DS
[ ] New 3DS XL
[ ] New 2DS XL

What is your current Luma3DS version?
If you are running an hourly version of Luma3DS, please manually update to a stable version as I will no longer deal with people who are using hourlies.

[ ] Luma3DS v7.1 + boot9strap v1.0/v1.1
[ ] Luma3DS v8.0 + boot9strap v1.2+
[ ] Luma3DS v8.1 + boot9strap v1.2+
[ ] Luma3DS v8.1.1 + boot9strap v1.2+
[ ] Luma3DS v9.0 + boot9strap v1.2+
[ ] Luma3DS v9.1 + boot9strap v1.2+
[x ] Luma3DS v10.0+ + boot9strap v1.2+

What version of Luma Updater are you using?

[ ] v2.0
[ ] v2.1
[ ] v2.1.1
[ ] v2.1.2
[ ] v2.2
[ ] v2.3
[ ] v2.4
[x ] v2.5

How are you running Luma Updater?

[x ] .cia
[ ] .3dsx + HBL/Rosalina

What problems are you experiencing?
"could not obtain update details"
Steps to reproduce

connect to wifi
open luma updater
can't dind update data

I believe it's because this page is no longer there:
http://astronautlevel2.github.io/

Shall we all uninstall it then @KunoichiZ ?

@halpz No, wait for me to release a new version.


Update nf-winbase-pulseevent.md

@justanotheranonymoususer : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks for the contribution. I've merged your changes and they should be live soon.


LINE

paper
LINE: Large-scale Information Network Embedding
problem: node embedding

given a graph
task: embed each node in the graph to a vector

solution

used 1st and 2nd order proximity of nodes with unclear origin
not neural network models

evaluation: node classification
given: a graph
task: feed each node embedding produced by LINE to another model to predict the node label
data sets

social network: http://socialnetworks.mpi-sws.org/
DBLP citation network: https://aminer.org/citation

code: LINE
https://github.com/tangjianpku/LINE

The model description in the paper and the code are both very unclear. Discontinue studying this approach.


Working reverse-proxy-for-free-basics-docker MVP for inclusao.etica.ai

Quick links:

Site: Inclusão Digital - Etica.AI (destiny in Portuguese)

https://inclusao.etica.ai/

Issue: Proxy reverso para melhorar compatibilidade de sites com o Free Basics / internet.org (destiny in Portuguese)

https://github.com/fititnt/cplp-aiops/issues/62

Issue: Processo de inclusão no Free Basics / internet.org (acesso gratuito) (destiny in Portuguese)

https://github.com/fititnt/inclusao-digital/issues/1 (early access, ask via email rocha(at)ieee.org)

Free Basics Technical Guidelines

https://developers.facebook.com/docs/internet-org/platform-technical-guidelines/

This repository started at https://github.com/fititnt/cplp-aiops/issues/62, and the main discussion/documentation about the inclusion about submittion on the https://inclusao.etica.ai as part of the Free Basics / Internet.org is here https://github.com/fititnt/inclusao-digital/issues/1 (early access, ask via email rocha(at)ieee.org)
The template used on inclusao.etica.ai is the GitHub default. But even if we care about do not use big images or download, the default uses JavaScript for create anchors (https://github.com/bryanbraun/anchorjs).
So, this issue is not just about make this reverse proxy work, but also about at least one project be accepted. And this can take some time.
We doing this (creating a reverse proxy in Docker) hoping that it could be reused in future for other projects, and make easier to force adaptation to the Free Basics Technical guidelines, that, in short, require absence of:

JavaScript
iframes
Video and large images
Flash and Java applets

CNAME 0.inclusao.etica.ai aguia-pescadora-charlie.etica.ai (TTL 15min)

The step by step by step is on the file tsuru-deployment.sh. Maybe for this project (assuming that the Free Basics team can take weeks to review) I will leave some more time doing other things and just make the bare minimum to make it work.


Proposal: Ballerina Constraint Package

Summary
Ballerina Constraint package will provide features to validate the values that have been assigned to Ballerina types. This proposal is to introduce the new package that supports for the validation.
Goals
Introduce a new standard library package which has APIs to validate the values that have been assigned to Ballerina types.
Motivation
Right now, the values assigned to Ballerina types cannot be validated further. As an example, according to the definition of int type in Ballerina specification:
The int type consists of integers between -9,223,372,036,854,775,808 and 9,223,372,036,854,775,807 (i.e. signed integers than can fit into 64 bits using a two's complement representation).

It cannot be further constrained as the user wishes. As an example, the age of the Person cannot be validated for a positive integer. Likewise, there is no way to constraint the values assigned to Ballerina types as of now. With this proposed package, that can be done with the use of an annotation which is binded to the type.
Also, this support is available in the other language specification such as XML Schema Part 2, JSON schema validation, OpenAPI specification and JSR 303.
Description
The XML Schema Part 2, JSON schema validation, OpenAPI specification and JSR 303 considered as references for designing this package. The highlighted validation rules/keywords are used for the proposed design for Ballerina.
Constraints of XML Schema

type
validation rule

string
length, minLength, maxLength, pattern, enumeration, whiteSpace

boolean
pattern, whiteSpace

float, double
pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

decimal
totalDigits, fractionDigits, pattern, whiteSpace, enumeration, maxInclusive, maxExclusive, minInclusive, minExclusive

duration, dateTime, time, date, gYearMonth, gYear, gMonthDay, gDay, gMonth
pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

hexBinary, base64Binary, anyURI, QName, NOTATION
length, minLength, maxLength, pattern, enumeration, whiteSpace

Example:
<simpleType name='password-string'>
 <restriction base='string'>
   <minLength value='8'/>
   <maxLength value='12'/>
 </restriction>
</simpleType>

References:

https://www.w3.org/TR/xmlschema-2/#defn-validation-rules

Constraints of OpenAPI Specification

type
validation keyword
values for format keyword

integer
minimum, maximum, exclusiveMinimum, exclusiveMaximum, multipleOf
int32, int64

number
-ditto-
float, double

string
minLength, maxLength, pattern
byte, binary, date, date-time, password

array
minItems, maxItems, uniqueItems
-

object
minProperties, maxProperties
-

boolean
-
-

Example:
components:
  schema:
    type: string
    minLength: 8
    maxLength: 12
    format: password

References:

https://swagger.io/specification/
https://swagger.io/docs/specification/data-models/data-types/

Constraints of JSON Schema

type
validation keyword
values for format keyword

integer
minimum, maximum, exclusiveMinimum, exclusiveMaximum, multipleOf
-

number
-ditto-
-

string
minLength, maxLength, pattern
date, date-time, time, duration, email, idn-email, hostname, idn-hostname, ipv4, ipv6, uri, uri-reference, iri, iri-reference, uuid, uri-template, json-pointer, relative-json-pointer, regex

array
minItems, maxItems, uniqueItems, maxContains, minContains
-

object
minProperties, maxProperties, required, dependentRequired
-

boolean
-
-

Example:
{
   "type": "string",
   "minLength": 8,
   "maxLength": 12,
   "pattern": "^(?=.*[A-Za-z])(?=.*\\d)[A-Za-z\\d]{8,12}$"
}

References:

https://json-schema.org/draft/2020-12/json-schema-validation.html#general
https://json-schema.org/draft/2020-12/json-schema-validation.html#format
https://json-schema.org/understanding-json-schema/index.html

Constraints of Java
NOTE: A whitespace have been added between @ symbol and the constraint name, in order to remove tagging GitHub users and organizations.
@ Null
@ NotNull
@ AssertTrue
@ AssertFalse
@ Min
@ Max
@ DecimalMin
@ DecimalMax
@ Negative
@ NegativeOrZero
@ Positive
@ PositiveOrZero
@ Size
@ Digits
@ Past
@ PastOrPresent
@ Future
@ FutureOrPresent
@ Pattern
@ NotEmpty
@ NotBlank
@ Email
public class User {
    private String name;

    @Min(value = 18, message = "Age should not be less than 18")
    private int age;

    @Email(message = "Email should be valid")
    private String email;

    // standard setters and getters
}

References:

https://beanvalidation.org/1.0/spec/
https://beanvalidation.org/2.0/spec/
https://docs.oracle.com/javaee/7/tutorial/bean-validation001.htm
https://www.baeldung.com/javax-validation

Proposed Constraints for Ballerina
The following constraints are proposed for Ballerina.

Constraint name
Applies to type
Constraint value type
Semantics (v is value being constrained, c is constraint value)

minValue
Any ordered type T
T
v > c

maxValue
-ditto-
-ditto-
v < c

minValueExclusive
-ditto-
-ditto-
v >= c

maxValueExclusive
-ditto-
-ditto-
v <= c

multipleOf
-ditto-
-ditto-
v % c = 0

length
string, xml, table, list, map
int
v.length() == c

minLength
-ditto-
-ditto-
v.length() >= c

maxLength
-ditto-
-ditto-
v.length() <= c

minContains
anydata[], map<anydata>
int
v[k] >= c

maxContains
-ditto-
-ditto-
v[k] <= c

uniqueMembers
-ditto-
boolean
v[k] != v[k+1]

pattern
string
regexp ~or predefined formats~
v matches c (need to decide whether match is anchored or not)

schemaValid
xml
SchemaValid record [^1]
v must be valid according to an XSD schema as described by the SchemaValid record c

fractionDigits
decimal
int
v must have not more than c fraction digits

oneOf
mapping
string[][]
protobuf oneof semantics; [["a", "b"], ["c", "d"]] allowed when a, b, c, d are optional fields; must have exactly one of a and b, and exactly one of c and d

dependentRequired
mapping
map<string[]>
if field k is present, then all fields in v[k] must be present

[^1]: SchemaValid record definition
ballerina     type SchemaValid record {|        // top-level can contain pi,comment, whitespace before/after element        boolean document = true;        // "{ns}localName" (works with xmlns declaration)        string elementName;        map<string> schemaLocation?;        string noNamespaceSchemaLocation?;     |};
~NOTE: We identified the format constraint is also used in XML schema and JSON schema, for the string type validations. But, it is quite similar to the pattern constraint defined for the string type. Hence, the constraint value type of pattern constraint is extended to regexp or predefined formats. Predefined formats have a regexp assigned internally.~
~Predefined formats: date, date-time, time, email, ipv4, ipv6, uri~
Proposed APIs
Annotation
The Ballerina constraints are attached to the type, parameter, return or record field attachment points with the use of an annotation.
public const annotation Constraint constrain on type, parameter, return, record field;

type Constraint record {|
   float minValue?;
   float maxValue?;
   float minValueExclusive?;
   float maxValueExclusive?;
   // ... all the finalized constraints should go here
|};

Function
The package has the public function that the developer is expected to call with the parameter that needs to be validated. Returns () if the validation is successful, or else an error if the validation is unsuccessful or if there is an issue with the constraint value.
public function validate(anydata v) returns error? {
   // ...
}

Examples
import ballerina/constraint;
import ballerina/io;

type Person record {|
    string name;
    @constrain {
        minValue: 18
    }
    int age;
    @constrain {
        pattern: "^[\\w-\\.]+@([\\w-]+\\.)+[\\w-]{2,4}$"
    }
    string email;
|};

public function main() returns error? {
    Person person = {name: "Chanaka", email<EMAIL_ADDRESS>
    _ = check constraint:validate(person);
    string s = string `Name: "${person.name}", Email: "${person.email}".`;
    io:println(s);
}

Questions

Ordered type in Ballerina is defined as follows.
public type OrderedType ()|boolean|int|float|decimal|string|OrderedType[];

Are (), boolean and string considered as ordered types?

Constraints defined in the Constraints record is valid only for some types. Validity of constraints for a particular type have to be validated separately. How can it be done?
Ex: pattern constraint is valid only for string type. How can it be validated not use against int type?

Related issue: https://github.com/ballerina-platform/ballerina-standard-library/issues/2788

Ordered type is defined here: https://ballerina.io/spec/lang/2022R1/#ordering. It cannot be described by a Ballerina type definition. OrderedType is an approximation: any Ballerina ordered type will be an OrderedType.

uniqueItems only makes sense when member type is subtype of anydata, i.e. applicable only to subtype of map<anydata> or anydata[]: Items is not the right word: Ballerina terminology is members.

I don't understand what minContains and maxContains mean.
Is there a real use case for multipleOf?
This syntax is wrong:
@constrain {
        minValue = 18
    }

Needs a colon not an equals.

Constraints defined in the Constraints record is valid only for some types. Validity of constraints for a particular type have to be validated separately. How can it be done?

You might be able to handle some cases with a constraint on the annotation record type.
An annotation is a qualified name. So you can have a constrain module that provides different annotations for different basic types e.g. @constrain:String for strings, @constrain:Map for maps etc. each of these will define a separate associated record type.
But in general the constraint checker code will need to do some checking. It won't all be done declaratively by the annotation mechanism.

Hence, the constraint value type of pattern constraint is extended to regexp or predefined formats. Predefined formats have a regexp assigned internally.

This is a terrible idea.  They are totally different things.

This is wrong pattern = "^[\w-\.]+@([\w-]+\.)+[\w-]{2,4}$": you would need to use \\w not \w.

uniqueItems only makes sense when member type is subtype of anydata, i.e. applicable only to subtype of map<anydata> or anydata[]: Items is not the right word: Ballerina terminology is members.

Updated the proposal for the applicable types with the correct terminology.

I don't understand what minContains and maxContains mean.

These 2 constraints were added with the idea of validating the minimum and the maximum value that an any ordered type array or map can have.

Is there a real use case for multipleOf?

type Polygon record {|
    string name;
    @constrain {
         multipleOf: 180
    }
    int sumOfInteriorAngles;
|};

This syntax is wrong:
@constrain {
        minValue = 18
    }

Needs a colon not an equals.

Updated the proposal.

This is wrong pattern = "^[\w-\.]+@([\w-]+\.)+[\w-]{2,4}$": you would need to use \\w not \w.

Updated the proposal.

Constraints defined in the Constraints record is valid only for some types. Validity of constraints for a particular type have to be validated separately. How can it be done?

You might be able to handle some cases with a constraint on the annotation record type.
An annotation is a qualified name. So you can have a constrain module that provides different annotations for different basic types e.g. @constrain:String for strings, @constrain:Map for maps etc. each of these will define a separate associated record type.
But in general the constraint checker code will need to do some checking. It won't all be done declaratively by the annotation mechanism.

This is much better than the proposed method IMO. As explained, we can have different annotations for different basic types where each of these will define a separate associated record type.
public const annotation StringConstraints String on type, parameter, return, record field;
public const annotation IntConstraints Int on type, parameter, return, record field;
...

type StringConstraints record {|
   int length?;
   int minLength?;
   int maxLength?;
   string pattern?;
   // ... all the finalized constraints for string type should go here
|};

type IntConstraints record {|
   float minValue?;
   float maxValue?;
   float minValueExclusive?;
   float maxValueExclusive?;
   // ... all the finalized constraints for int type should go here
|};

@jclark Since package name is ballerina/constraint, shouldn't the annotation-tag be like @constraint:String/@constraint:Map instead of @constrain:String/`@constrain:Map?
If so, the example would be as follows:
import ballerina/constraint;
import ballerina/io;

type Person record {|
    string name;
    @constraint:Int {
        minValue: 18
    }
    int age;
    @constraint:String {
        pattern: "^[\\w-\\.]+@([\\w-]+\\.)+[\\w-]{2,4}$"
    }
    string email;
|};

public function main() returns error? {
    Person person = {name: "Chanaka", email<EMAIL_ADDRESS>
    _ = check constraint:validate(person);
    string s = string `Name: "${person.name}", Email: "${person.email}".`;
    io:println(s);
}

@sameerajayasoma do let us know if you have any feedback.

We had a meeting today with @jclark to discuss about the proposal and decided followings:

different annotations for different basic types where each of these will define a separate associated record type
public const annotation StringConstraints String on type, parameter, return, record field;
public const annotation IntConstraints Int on type, parameter, return, record field;

agreed to have the package named as ballerina/constraint

decided to work on phases as follows:
Phase 1
constraints

(min|max)Value(Exclusive)?
(min|max)?Length

records

constraint:Int
constraint:Float
constraint:Number (values are decimal)
constraint:String

length constraints

constrain:Array

length constraints

Phase 2

Structural constraints that constrain the use of constraints@constrain:Map {
   atMostOneOf: [["minValue", "minValueExclusive"]]
}
type Float record {|
    float minValue;
    float minValueExclusive;
|};

Phase 3

pattern: depends on regexp

applies to constraint:String

Updated the proposal according to these.

I thought we were going to have e.g. constraint:Int and constraint:String.  Numbers require some subtlety to deal with the case where a value might allow a union:

constraint:Int is a constraint that applies when the value is an int; the annotation record declares the min/maxValue fields as type int
constraint:Float is a constraint that applies when the value is an float; the annotation record declares the min/maxValue fields as type float
constraint:Number is a constraint that applies when the value is int|float|decimal; the annotation declares the min/maxValues fields as type decimal; the semantics are that the value when converted to decimal is within the specified limits

decimal is special because it includes the range of the other numeric types, and it represents floating point decimal values exactly.
multipleOf makes sense for only int and decimal.

Yes. That is true. I meant to express the same but sorry for not explaining it properly. Thanks for the clarification. Updated my last comment to be less ambiguous.

@jclark The proposed API works successfully with the record field annotation attachment point, but there is an issue with retrieving the annotations form the type annotation attachment point.
Case 1: record field annotation attachment point
import ballerina/constraint;
import ballerina/log;

type Foo record {
    @constraint:String {
        length: 6
    }
    string value;
};

public function main() {
    Foo foo = {value: "s3cr3t"};
    error? validation = constraint:validate(foo);
    if validation is error {
        log:printError("Failed to validate details", validation);
    }
    // business logic
}

Case 2: type annotation attachment point.
import ballerina/constraint;
import ballerina/log;

@constraint:Int { minValue: 0 }
type PositiveInt int;

public function main() {
    PositiveInt age = 18;
    error? validation = constraint:validate(age);
    if validation is error {
        log:printError("Failed to validate age", validation);
    }
    // business logic
}

In case-2, there is no way to get the annotations attached to the PositiveInt type in the runtime. Because, in runtime, the value (which is 18) is passed to the validate function and the type is resolved with inherent type (which is int in this case). Therefore, we might have to come up a different API to solve this.

I agree the API isn't right.
Does it really make sense to get the constraints from the value being validated? I don't think so. I think you should pass in the typedesc to be used for validation as a parameter, something like:
function validate(anydata value, typedesc<anydata> t = <>) returns t|error;

e.g.
Foo foo = {value: "s3cr3t"};
Foo validFoo = check constraint:validate(foo);

Thanks @jclark. This API is better and solve the problem we have. Also, it works successfully with the both cases mentioned above.

I would not return the validated value  cg

I understand why we had to design the validate method to return the value it validates.
But I would use the following signature for the validation method. I know that we don't have the syntax to specify some typedesc values.
function validate(anydata value, typedesc<anydata> t) returns error?;

e.g.,
@constraint:Int { minValue: 0 }
type PositiveInt int;

public function main() returns error?{
    PositiveInt age = 18;
    check constraint:validate(age, PositiveInt);
    // ...
}

Regarding the regexp match for string types, we would go with the name pattern for the constraint since the same name is used in the references mentioned in the proposal.
Sample :
string:RegExp regExp = re `([0-9]{10})|(\+[0-9]{11})`;

@constraint:String {pattern: regExp}
type PhoneNumber string;

type User record {|
    string name;
    @constraint:String {pattern: re `male|female`}
    string gender?;
    int age;
    @constraint:String {pattern: re `([0-9]{9}[v|V]|[0-9]{12})`}
    string nic;
|};

type UserAdvanced record {|
    *User;
    PhoneNumber contactNumber;
    @constraint:String {pattern: re `([a-zA-Z0-9._%\-]+@[a-zA-Z0-9.\-]+\.[a-zA-Z]{2,6})*`}
    string email;
|};


Make Local Variable Storage (TODO)

https://github.com/Wopslang/Wops/blob/863e926ad0a8d2b944b28b1337b427287bc8ab26/src/runtime/AST.h#L239-L239

THIS IS TODO ISSUE.

Issue resolved: bac8d09


Enhancement: Some new feature ideas for the Video test menu on ATK

Sorry for another post :), I am sure you are busy with tons of other things but just some suggestions....

Interlaced checkerboard

Overscan test screen showing boundary edges/corners for various screen sizes

Some sort of up/down & left/right scrolling test for ghosting/refresh
e.g. Pinball Fantasies where the screen blurs badly going up and down if using an old slow refreshing LCD screen.
Same game, top text/score scrolling e.g. looks a lot clearer on certain CRT's than others depending on long or short phosors.
[perhaps a speed adjustable scrolling checkerboard?]

PAL/NTSC software switch [feasable?]

More than happy to test & help in any way I can!

What would you want for the overscan test card? The existing test card is not overscan but does accurately show the usual Amiga NTSC/PAL boundaries using a white bounding box. Anything outside the box would be overscan.

from the monitors actual resolution, these are the maximal for a demo/game I have come across;
PAL		#720x288
PALi		#720x576
NTSC	#720x240
NTSCi	#720x480
I was thinking perhaps a single pixel bounding box at the given dimension, maybe with a few inside rectangles, less 8 pixels each time (720x , 712x, 704x ) , with some label text of axis size ? This would also be good for screen centring.
So as an example I have found the 'Monster' demo pic  from the 'Rebels-Infestation44' demo disk [attached] the current best test overscan screen.
Demos_Monster_DMS.zip
I have attached 3 demo's which contain it, as they display it in different positions onscreen, and it is also different position on the same demo A500 to A1200
[Need Skick/relokick on A1200 with mixed luck as to if they work at all, emulated A1200 they are ok.]
If you try all three you should be able to see the actual extents the picture should be displayed at!
As a game in overscan I think the 'largest' is 'The Settlers' and perhaps the intro in 'Agony'.
Maybe also some ideas from this (the second pic down with explanations) ?
https://en.wikipedia.org/wiki/Indian-head_test_pattern

Like I say, the existing "RGB gradients and PAL/NTSC extents" is good for screen sizing and centering. If you put the PAL box as large and centered as you can, the overscan should take care of itself.
There are a lot of weird overscan sizes I found on Amiga titles. I settled on a sensible average as about 16px each left and right, and 12px each top and bottom. But if this is centered like so, then the normal PAL bounding box is also centered, and you minimise risk of seeing the overscan boundary by making that box as large as possible... And you can already do that, right?

Ok here's a build for you with the 50/60Hz switch on the main menu.
https://github.com/keirf/Amiga-Stuff/suites/3277780324/artifacts/76393468

I tried the interlaced checkerboard, but on an LCD monitor of course it looks a right mess. Even weirder, my Dell LCD monitor now has an interlace/checker shimmer on all input sources! I have no idea why... Since it flickers it can't be persistence. A testcard that may freak out LCD monitors is not great :)

For now I've done a new release with all the new features and fixes so far.
Some scroll tests in future would make sense.

50/60 toggle works perfectly on my 1200 and 500, [could it be possibly be a global button that works on all screens? sorry to keep asking for things, it is great as it is if not!]
I am trying to draw an overlay to existing gradients screen for a few suggestions , I tried writing it and it just sounded a lot more complicated than it is.
Yes I get interlace shimmer residual effect if the screen is static for long on one LCD monitor, powering it off for a few minutes seems to reset it otherwise it can persist for a long time. PAL Interlace looks wrong on most LCD's as the field invert is set wrong in their firmware (NTSC interlace should look correct if so, although will still flicker)

I may revisit the interlace screen. I need to really bring in a CRT and test on that. I did enough to kind of prove it can work and it's not too hard. Is it actually that useful? I don't know. Maybe it's tuneable but untuned via OSSC it looks like sh*t!
Global 50/60Hz switch? Probably not unless I hide it away on another key perhaps, but then it wouldn't be clickable on every screen.
Yes a drawing of the new improved gradient screen might make sense!

lcd and crt interlace should look the same if field invert is right on the lcd, clear but flickering. Simplest test I have found thus far is MasterBlaster load menu screen as interlaced and lots of small text. (Amiga monitor crt with long phosphor persist should have almost no flickering). Yes useful, to me at least,  both gradient and checkerboard in Interlace PAL and Interlace NTSC would be perrfect! cheers!

hopefully this will make sense!
First two pics are current PAL and NTSC with a wide screen res [using emulator here but pretty sure was same on real hardware, been a while since I was fiddling with it]. Centring seems askew as the horizontal white bar lengths are different.
In the NTSC the bottom surround bar is missing too.

Perhaps this is a solution, without having to change much?
I have played around with various ideas and this may be the simplest ?
It should be pretty easy to see at a glance how centered in H and V plane and to what amount of overscan the screen has?

It is normal that the "non overscan" display is right of centre: https://eab.abime.net/showthread.php?t=85490
But yet that is what you'd want to centre on whatever real display you are viewing on: the vast majority of games (and Workbench) use these viewport settings.
The bottom surround bar is the PAL surround for normal PAL viewport. The NTSC viewport (even in full overscan) does not include all the scanlines required to view the bottom of the PAL surround bar.

just wondering if it was possible to get your interlace test version to try please? (presume nothing further in the works on it?)
thanks very much.


Application freezes

Trying to use the application on Windows 10. The first time it uploaded a handful of files and then froze. The second time it froze straight away upon clicking Upload. Not usable.

I'm unable to reproduce this issue.


Faster copy

this change will accerate the aten::copy by about 5%.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.16 out of 17 committers have signed the CLA.:white_check_mark: wiryls:white_check_mark: jfxu-st:white_check_mark: zhaoguochun1995:white_check_mark: caikun-pjlab:white_check_mark: POI-WX:white_check_mark: Bonbon-Tang:white_check_mark: lljbash:white_check_mark: NeosZhang:white_check_mark: tangzhiyi11:white_check_mark: Reinerzhou:white_check_mark: CoolKbh:white_check_mark: Wrench-Git:white_check_mark: fandaoyi:white_check_mark: hellozmz:white_check_mark: lwj-st:white_check_mark: zyf654321:x: SHshenhaoYou have signed the CLA already but the status is still pending? Let us recheck it.


conftest: 0.21.0 -> 0.22.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/open-policy-agent/conftest/releases.
meta.description for conftest is: "Write tests against structured configuration data"
meta.homepage for conftest is: "https://github.com/open-policy-agent/conftest"
meta.changelog for conftest is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.22.0 with grep in /nix/store/6nzcjc7va81wf2kjn3hz7vr5xyrd3x1m-conftest-0.22.0

directory tree listing: https://gist.github.com/d67359d8da59c6b5fbb5b9504e5d4782

du listing: https://gist.github.com/062af0502d1715ffcf740bb4f754f020

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
conftest

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6nzcjc7va81wf2kjn3hz7vr5xyrd3x1m-conftest-0.22.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A conftest https://github.com/r-ryantm/nixpkgs/archive/ac49fb46e20b829c4ea49a5f76ce0aaa1e4814c7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6nzcjc7va81wf2kjn3hz7vr5xyrd3x1m-conftest-0.22.0
ls -la /nix/store/6nzcjc7va81wf2kjn3hz7vr5xyrd3x1m-conftest-0.22.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

conftest

Maintainer pings
cc @yurrriq @kalbasit for testing.

Result of nixpkgs-review pr 103856 1

1 package failed to build:

conftest

Result of nixpkgs-review pr 103856 1

1 package built:

conftest

lgtm. to whomever picks this up, could you please merge #99557 too? :smiley:


master

Hey @king350023 this PR seems like a mistake. Let us know what you were looking to do. Thanks!

在鬆弛中查看