Feature request: export whole folder into dokuwiki with internal links preserved

Great Plugin
Great plugin, was wating for this since ages
Current Issue

When currently export .md to any format, internal links [[Link]] doesn't work

Dokuwiki

Exporting whole folder as .txt files with dokuwiki formatting, one can upload it to dokuwiki server, hence internal links would be preserved

Benefits

One can directly publish his/her work on dokuwiki server

Hi, thanks for the suggestions!
I've just published 0.2.4 which has a couple of the features you've requested.

Exporting internal links: there is a setting called Internal link processing which you can try adjusting. If that doesn't work, you can change the Export files from HTML or markdown? setting, which will leave wikilinks alone but will stop formatting from other plugins from working
DokuWiki: I've added this as an export destination, but for now there isn't a batch export feature (relates to #10, #41). This will come soonish

Let me know if you have any issues,
Oliver

Just to clarify: you can get the latest version by updating your plugins inside Obsidian, you don't need to worry about the releases page I linked


sun visibility issue for unloaded vessels

It seem that in some cases sun visibility for unloaded vessels is not correct. Reports of the UB have surfaced from time to time, in various forms. It doesn't seem related to analytical sun visibility evaluation at higher timewarp speeds. Also worth nothing it is reportedly not happening for loaded vessels.
See description here and useful files there.

Check if this can be reproduced, after the fix for #71

This was probably caused by the fact that, as soon as a flag was present in the savegame, the cache stopped recomputing, leading to sun visibility being not updated. Only after a KSP reboot the cache would update correctly, for a single time, then the issue repeated.
Hence the randomness in the reports and their circumstances.
Related to #75, fixed here.


Limit the number of records returned for a task in the UI

once we have https://github.com/influxdata/influxdb/issues/13575
the UI should add the limit parameter when requesting the runs of a task. this should be 20 until we have more options for paging.

No pagination. Just last 20 results.

this was fixed in the api so we don't need to update the UI right now.


Leaked semaphore object in MONAI integration tests

Description
In https://github.com/Project-MONAI/MONAI/pull/2274 we are observing:
/opt/conda/lib/python3.8/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 33 leaked semaphore objects to clean up at shutdown

https://github.com/Project-MONAI/MONAI/runs/2728004520?check_suite_focus=true#step:7:2534
Steps to Reproduce
MONAI integration tests in https://github.com/Project-MONAI/MONAI/pull/2274
Expected behavior
No warnings.
Actual behavior
Pesky warnings.
Versions
Observed with itk-5.2.0.post3.
Additional Information
We thought https://github.com/InsightSoftwareConsortium/ITK/commit/cfdb5023a82fc61f3825231b257ca47f4d9d4d8a should avoid this, but there may be another code path, etc.
CC @wyli @aylward @hjmjohnson @dzenanz

Thanks for tracking this @thewtex.
Not sure if this could be treated as a fix for this issue, but I'm able to avoid the warning by using
torch.multiprocessing.get_context("spawn")  instead of
torch.multiprocessing.set_start_method("spawn")
(please see https://github.com/Project-MONAI/MONAI/pull/2615/commits/ac7944e1a296cef39b71106fc204abd771b8a825).

@wyli Can you check whether PR #2649 helps this semaphore leak?

@wyli Can you check whether PR #2649 helps this semaphore leak?

Happy to test if there are compiled binaries for Ubuntu or Macos... Otherwise I don't currently set up the build environment for the c++ core, I may try to build and get back to you later

now able to reproduce the issue with itk-5.2.0.post3 + torch (it's not a monai issue)
import multiprocessing

try:
    multiprocessing.set_start_method("spawn")
except RuntimeError:
    pass

from itk import Image
import torch

if __name__ == "__main__":
    for d in torch.utils.data.DataLoader([torch.tensor(i) for i in range(10)], num_workers=4):
        pass

With #2649 now in master, there is no semaphore leak, even when un-commenting the commented code:
#import multiprocessing
#
#try:
#    multiprocessing.set_start_method("fork")
#except RuntimeError:
#    pass
#
from itk import Image
import torch

if __name__ == "__main__":
    for d in torch.utils.data.DataLoader([torch.tensor(i) for i in range(10)], num_workers=4):
        pass

With "spawn" method, the leak is still present.
My setup:
Linux corista 5.4.0-77-generic #86-Ubuntu SMP Thu Jun 17 02:35:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

MONAI version: 0.6.0rc2+2.g3254ac39
Numpy version: 1.20.3
Pytorch version: 1.9.0+cu102
MONAI flags: HAS_EXT = False, USE_COMPILED = False
MONAI rev id: 3254ac39c57cdd6df1bc21b36c03cb9171dbcfb2

Optional dependencies:
Pytorch Ignite version: NOT INSTALLED or UNKNOWN VERSION.
Nibabel version: NOT INSTALLED or UNKNOWN VERSION.
scikit-image version: NOT INSTALLED or UNKNOWN VERSION.
Pillow version: NOT INSTALLED or UNKNOWN VERSION.
Tensorboard version: 2.5.0
gdown version: NOT INSTALLED or UNKNOWN VERSION.
TorchVision version: NOT INSTALLED or UNKNOWN VERSION.
ITK version: 5.3.0
tqdm version: NOT INSTALLED or UNKNOWN VERSION.
lmdb version: NOT INSTALLED or UNKNOWN VERSION.
psutil version: 5.8.0
pandas version: 1.2.5
einops version: NOT INSTALLED or UNKNOWN VERSION.

but I'm able to avoid the warning by using
torch.multiprocessing.get_context("spawn") instead of
torch.multiprocessing.set_start_method("spawn")
(please see Project-MONAI/MONAI@ac7944e,

@wyli great work here.
Indeed, the CPython documentation on multiprocessing start methods states,

set_start_method() should not be used more than once in the program.

And their example puts the set_start_method call under the condition if __name__ == '__main__'::
import multiprocessing as mp

[...]

if __name__ == '__main__':
    mp.set_start_method('spawn')

Debugging:
import multiprocessing

try:
    multiprocessing.set_start_method("spawn")
except RuntimeError:
    pass

from itk import Image
import torch

if __name__ == "__main__":
    for d in torch.utils.data.DataLoader([torch.tensor(i) for i in range(10)], num_workers=4):
        pass

I found that set_start_method gets called multiple times, and this causes the leak.
This works:
import multiprocessing

from itk import Image
import torch

print(__name__)

if __name__ == '__main__':
    try:
        multiprocessing.set_start_method("spawn")
    except RuntimeError:
        pass

    for d in torch.utils.data.DataLoader([torch.tensor(i) for i in range(10)], num_workers=4):
        pass

In the spawned process, __name__ is __mp_main__.
MONAI is working, we have a good handle on the cause, so closing. Thanks, everyone who helped with this tricky issue!


Fix y-title for function names

Close #47. I didn't try on many plots myself but it looks like it passes the CI. Sorry for all for the git changes, I don't know why it's like this, the changes are just a few lines at the beginning of plot2.default().
@grantmcdermott I'm still struggling with the tests suite of this package (esp. because I'm currently on Windows) so it's probably better if you can take over this PR to generate snapshots.
New behavior:
set.seed(42)
plot(rnorm(1))

library(plot2)
set.seed(42)
plot2(rnorm(1))

Sorry for all for the git changes, I don't know why it's like this, the changes are just a few lines at the beginning of plot2.default().

Is it perhaps this? Or maybe something to do with your lintr?
Regardless, I'll take a look shortly. Thanks @etiennebacher!

Is it perhaps this?

Thanks, I think it worked for future commits but I can't cancel for this PR

No worries


Publish a new nuget for xamarin.android.google.billingclient

The latest nuget is 7 month old, new versions where introduced on master 14 days ago.
Are there plans to release a new nuget for xamarin.android.google.billingclient?

It is live!!! :)


[Mhlo] BatchNorm & Concat

This PR serves the following purposes:

supports the lowering of ONNXBatchNormalizationInferenceModeOp and ONNXConcatOp from ONNX-MLIR to MHLO.
adds tests for the two operations.
The corresponding RFC is here: https://github.com/onnx/onnx-mlir/issues/1514

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@jenkins-droid test this please

Can one of the admins verify this patch?

@jenkins-droid test this please

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@chenchongsong merged with the latest before starting to make a run, hope  its ok with you.

Jenkins Linux amd64 Build #6671 [push] [Mhlo] BatchNorm & Conca... started at 03:42

Jenkins Linux ppc64le Build #5783 [push] [Mhlo] BatchNorm & Conca... started at 04:45

Jenkins Linux amd64 Build #6671 [push] [Mhlo] BatchNorm & Conca... passed after 1 hr 59 min


Option parsing error when adding coveragePathIgnorePatterns to package.json

🐛 Bug Report
I get This TypeError: pattern.replace is not a function error when adding the coveragePathIgnorePatterns to my package.json
To Reproduce
Steps to reproduce the behavior:

clone this https://github.com/TheRealSyler/Jest-bug-test
then npm i && npm run test
you should get this error

TypeError: pattern.replace is not a function
    at /home/syler/Documents/GitHub/Jest-bug-test/node_modules/jest-config/build/normalize.js:370:15
    at Array.map (<anonymous>)
    at normalizeUnmockedModulePathPatterns (/home/syler/Documents/GitHub/Jest-bug-test/node_modules/jest-config/build/normalize.js:368:16)
    at /home/syler/Documents/GitHub/Jest-bug-test/node_modules/jest-config/build/normalize.js:773:17
    at Array.reduce (<anonymous>)
    at normalize (/home/syler/Documents/GitHub/Jest-bug-test/node_modules/jest-config/build/normalize.js:618:14)
    at readConfig (/home/syler/Documents/GitHub/Jest-bug-test/node_modules/jest-config/build/index.js:163:46)
    at readConfigs (/home/syler/Documents/GitHub/Jest-bug-test/node_modules/jest-config/build/index.js:373:26)
    at /home/syler/Documents/GitHub/Jest-bug-test/node_modules/@jest/core/build/cli/index.js:155:58
    at Generator.next (<anonymous>)

if you insert console.log(pattern) at jest-confing/normalize.js:370, you will get a different error but also an array.
pattern.replace is not a function because pattern is an array and not a string.
so the bug is caused by jest-confing/normalize.js:358 getting an array but expecting a string.
the line numbers are from the compiled jest-config package.
Expected behavior
Parse the option properly.
envinfo
npx: installed 1 in 0.783s

  System:
    OS: Linux 5.3 Pop!_OS 19.10
    CPU: (6) x64 Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz
  Binaries:
    Node: 12.13.1 - /usr/local/bin/node
    Yarn: 1.21.1 - /usr/bin/yarn
    npm: 6.12.1 - /usr/local/bin/npm
  npmPackages:
    jest: ^24.9.0 => 24.9.0

nvm my config was wrong, always check when your copy pasting.


Hide things for archives

Relies on and augments #4790. Logical changes:

Default to assuming it's an archive
If it's an archive, hide the search div, the normal archive drop-down (because we have the butterbar one), the "Edit this page" link, and the ratings widget.
If it's not an archive, show the above things.

The reason we default to it being an archive is that it's less visually flickery to hide elements by default and then show them, than to show them and then hide them. I tested both ways. I think this is pretty clean.
Of course it breaks if JS is disabled, but so does the whole site.
To test what happens if it's an archive, set isArchive = true in line 296 of js/docs.js and do jekyll serve.

@johndmulhausen PTAL, I changed it to visibility.

Oops I did not mean to actually click that. 🙈 let me know if I should revert.


Support multipart content (file uploads)

I don't think it makes sense to send the data as multipart - I worked it out and it all works but I think there is more benefit to keeping the data as json. Can create a controller in your web api project if you need to handle file uploads.


Change frontend color scheme via configuration.yaml

This is 100% a wishlist item, so don't feel bad about saying no :).
I was wondering if it might be possible to have a configuration setting for the frontend color scheme?  I don't dislike the current color scheme, but I do dislike that when I'm in a dark room (aka, I just woke up and the sun isn't up yet) that the HA screen has so much white.  Doubly so since we already have a sun tracker, so if we could expose the color scheme into the configuration file it'd, in theory, be pretty simple to write some automation to handle color.

This issue comes up from time to time in the chat too. It is not going to be implemented.
Adding colors will add a lot of extra development effort on every extra feature that is being developed for the frontend, because now it has to look good in whatever combination the user can pick. That's just not worth the cost.

Just chiming in to agree that the white and light blue at night is very jarring. I hope this gets looked at eventually.

balloob,
That's a fair sentiment, what if we just limited it to a single "Night Time" mode?

Sorry to dredge up a closed issue, but a night time mode would be very handy. Full themeability probably isn't worth the effort I agree, but I'd like to have HA on an old tablet in my living room as a sort of central information panel and the white/blue interface (while quite pretty) is way too bright in the dark. I imagine I'm not the only one wanting to do this.
I'd suggest something like the colorscheme Grafana uses, but anything on a black or otherwise dark background works for me.

@balloob Can you at least agree that a single night/dark mode would be very useful? We can't be the only ones who are using this on our tablets at night to check the status of things or in a dark room when watching a movie.

I agree with this request, I open HA on my iphone when we're going to sleep to see if everything has run and a darker theme would be nicer to view then

Op 25 feb. 2016 om 13:58 heeft David Thomas<EMAIL_ADDRESS>het volgende geschreven:
@balloob Can you at least agree that a single night/dark mode would be very useful? We can't be the only ones who are using this on our tablets at night to check the status of things or in a dark room when watching a movie.
—
Reply to this email directly or view it on GitHub.

I completely agree. A simple night-mode esque theme would be great. Based on a user-set schedule in configuration.yaml or with a button on the front-end. Loving HA so far. Keep up the good work.

One more vote for a simple night mode using a darker color scheme.

At least night mode (white on black) would be very helpfull!!


minor improvement: after loading a mod, the tool should automatically go to the enemies screen/change visually in some way

it took me a bit to realize that my mod was actually loaded and i could go to the other tabs

Fixed. Thanks!


Move to api

Summary
This should fix some issues with running the jupyter notebook on the singlequdits
Details and comments

connect to API
use the rlx, rlz etc.

This should now also properly implement the communication through https


Remove Typescript build info during cleanup

fix #267
After manually removing .tsbuildinfo files, I could build again the project.
This PR adds the *.tsbuildinfo to the list of files to clean when doing a yarn clean

Great! Thank you, Adrien!


Immutability

Closes #581
This is still a wip, but I need your feedback to finish it. Don't mind the code style & PHPStan, I'll fix it later.
A couple of notes on the implementation:

Cloneable is a tiny temporary workaround to allow cloning readonly objects. Once PHP 8.3 is out, it can be refactored to regular clone + $this->prop = $prop combination
I wanted to avoid creation of ResolverInterface instances on each resolve to avoid mutations, so instead went with passing the object $source parameter
ResolverInterface::executionSource is the replacement for ResolverInterface::getObject() - it allows getting the object that the field/method is called on. This is used by #[Security('this.someMethod()')] and for prefetching data #[Field(prefetchMethod: 'someMethodOnThis')]
Getters on QueryFieldDescriptor and InputFieldDescriptor are gone since properties are now readonly

And a lot of questions @oojacoboo:

Currently prefetch is tied into graphqlite, such that it's impossible to implement such a feature in userland: there a hard dependency on it in QueryField. What do you think of extracting it into a separate attribute and a parameter middleware? Something like #[Prefetch('methodName', ['arg1'])] + PrefetchParameterMiddleware? That would simplify the QueryField further and allow implementation of similar features in userland, without graphqlite having to implement them. I know you're against adding more attributes, but this seems logical. Existing prefetechMethod and prefetechArgs parameters of #[Field] can be deprecated and removed later on.

Although ResolverInterface::executionSource works, I think it's worthwhile thinking on how to improve that. There are multiple problems currently:

checks for null in resolvers, because of the __invoke(object|null $source) signature forced by ServiceResolver, which doesn't need a source. All other resolvers do need one and have ugly runtime checks
->setCallable() on QueryFieldDescriptor which duplicates the logic of some of the existing resolvers
most importantly, input constructor parameters are not passed through middlewares, partly due to issues with resolvers. This single-handedly stops me from using constructor parameters

What do you think of refactoring them too in the scope of 7.x? I have a few ideas on mind.

QueryFieldDescriptor and InputFieldDescriptor are both bloated with logic of selecting the $originalResolver, being passed 6 properties $callable, $targetMethodOnSource, $targetPropertyOnSource, $magicProperty, $refMethod and $refProperty solely for that purpose. Instead of doing so we can just accept the $originalResolver as a constructor parameter and make respective properties of resolvers public readonly, so that in the rare cases it's needed they can just do $descriptor->originalResolver->methodName

I've only added readonly in places where I refactored things, but it's probably worthy adding everywhere, also dropping the getters. Maybe as part of a different PR. Thoughts?

Can't we just make prefetchMethod accept a callable as well?  What's the benefit of an additional annotation here?
These seem like reasonable improvements.  Let's do a separate PR on them though.
I like it
I think locking down the public API is a good idea, or else we could find ourselves dealing with more BC break issues down the road.

Of note, on the documentation, we only need to update the current src.  The versioned docs shouldn't be edited since they represent the defined version, which is already locked in functionality.  They only need to be updated for mistakes, not changes to the API.

Also, when it comes to defining the public API, I realize there are 2 camps.  With the addition of readonly props and typing, we have far greater control over how properties are managed and therefore the accessibility of the property can be used for defining the API, instead of getters/setters.
I realize this may be where we're headed in PHP land, and it may take some time before that's a standard, if ever.  The issue I take with this is that is splits your API into methods and properties and it's not always clear which you should be looking for, especially when using something like autocomplete.  Sometimes you may need a getter to massage the output from a property, making it private, and other times you may not, relying on that property being public.  This leaves the dev wondering and it's a bit chaotic IMO.
In short, I'm not sold on the trend of moving to public properties for defining the API.  It's neat, clean, less code - yes.  But, it can also be confusing.  Further, most of GraphQLite already uses getters/setters, so a move away from this only bifurcates the public API further.

It sounds like you're trying to reverse the order of processing for prefetching. Instead of defining how a prefetch is handled for a given field, on that field, you're wanting to add a middleware that will prefetch for all fields based on some logic?

Not really, the order and all of the behaviour will stay exactly the same. I'm just not satisfied with the implementation of it. Currently QueryField checks whether a prefetch is needed and if so, changes the resolver to return a deferred result. I want to remove any references to prefetch inside of QueryField and extract them into middlewares. For prefetch, I was thinking of a PrefetchParameterMiddleware:
public function mapParameter(ReflectionParameter $parameter, DocBlock $docBlock, Type|null $paramTagType, ParameterAnnotations $parameterAnnotations, ParameterHandlerInterface $parameterMapper): ParameterInterface
    {
        $prefetchAttribute = $parameterAnnotations->getAnnotationByType(Prefetch::class);

        if (!$prefetchAttribute) {
            return $parameterMapper->mapParameter($parameter, $docBlock, $paramTagType, $parameterAnnotations);
        }

        return new PrefetchDataParameter($prefetchAttribute->method, $prefetchAttribute->args);
    }

and a PrefetchDataParameter:
public function resolve(object|null $source, array $args, mixed $context, ResolveInfo $info, QueryField $field = null): mixed
    {
        $prefetchBuffer = $context->getPrefetchBuffer($field);
        $prefetchBuffer->register($source, $args); // <--- this is what `QueryField` is currently responsible for

        // QueryField also defers the resolver for prefetch-annotated fields, which could be done on parameter level
        return new Deferred(function () {
            if (! $prefetchBuffer->hasResult($args)) {
                $prefetchResult = $this->computePrefetch($source, $args, $context, $info, $field, $prefetchBuffer);

                $prefetchBuffer->storeResult($prefetchResult, $args);
            }

            return $prefetchResult ?? $prefetchBuffer->getResult($args);
        });
    }

That would allow future features that require deferring the parameter resolution possible. And not only in the graphqlite itself, but in userland code too.

On the APIs, public and internal, I think we should stick with getters for defining the API. Going immutable will obviously eliminate setters. We don't need getters for every property internally either. That can be something that's selectively chosen when defining the API.

Got it. I'll revert the getters then on this PR, then submit two more PRs: one for resolvers, the other for readonly throughout graphqlite.

@oprypkhantc not opposed to a #[Prefetch] attribute.  I do think the separation of concerns here has a good deal of benefit - I like it.  In general, I do want to see a limited set of attributes on this lib.  I think it's easy to get carried away with adding new functionality through another attribute.  However, I think this one is clear with intent and is deserved.  I like the design on this.  Let's target this on a different PR.

Also while working on #[Prefetch] I found an interesting detail: for some bizarre reason, prefetch method is not called statically but rather on the first (random) source instance. This doesn't make sense at all and could lead to problems (like someone accidentally using one of $this-> properties/methods in the prefetch method).
I believe the more logical solution is to call the method statically when only a method name is specified. Not only will this avoid problems for the users, it'll also simplify the code for graphqlite.
Obviously when a full callable is specified we can just resolve the class from the container instead of calling the method statically. Wdyt?

Regarding #[Prefetch], is removing #[Field(prefetchMethod: 'some')] support an OK breaking change or should we first deprecate it?

Are there any issues or limitations in keeping it deprecated?  It'd be ideal to deprecate before removal.

Are there any issues or limitations in keeping it deprecated? It'd be ideal to deprecate before removal.

No I don't think so; I'll add deprecations then. Also is there a point in supporting the annotation version of #[Prefetch]? That wouldn't be difficult either, but I suppose it won't be too long till annotations support is deprecated.

Annotation support is already deprecated.  No need to add an annotation.
https://graphqlite.thecodingmachine.io/docs/doctrine-annotations-attributes

@oprypkhantc We still need to get that deprecation added.  Is there anything else remaining on this?

@oojacoboo Are you talking about Prefetch-related deprecations? If so, this is included in a different in a different PR, where I refactored Prefetch: https://github.com/thecodingmachine/graphqlite/pull/588/files#diff-44cccfa8f1939494e34146f50de7ef43e88de7e1789ddc53ec4dd4a813bed6c8R67

@oojacoboo Hey. Any chance to review this and after this - the prefetch refactor? There are some other issues I'd like to tackle, but first I want these to get merged.

@oprypkhantc this looks great :)
My apologies for the delay in reviewing this.  I'll get the others reviewed as well and look forward to any additional PRs.
Before merging this one, can you confirm that we have adequate test coverage for prefetch and the PrefetchBuffer?

Should we reorganize tests a bit? Separate fixtures, unit tests and integration tests and add #[Covers] wherever possible? That'd allow actually using phpunit coverage for coverage reliably.

That'd certainly be nice.  It'd give us a little more confidence with these merges.  Everything else looks good though.  I'll go ahead and merge and we can monitor this on master for a bit before tagging a release.

Thanks! It'd also be awesome to include prefetch and resolvers refactor in that release as well.

Yes - agreed.


Adds reachedEnd(action) {}, improves optional handing

Also applies guard instead of if let, and adheres to code
conventions

Fixes #384


Provide 'originate' api

We need the contract origination feature. Do you plan to provide it?

found it! sorry.


RFC 2: partial lockfiles

As proposed by @bollwyvl https://github.com/pyodide/pyodide-lock/issues/4#issuecomment-1608118850
The way the in-flight jupyterlite PR works is by:

generating partial lockfiles

these wouldn't be sufficient to run anything

layering them, by name, on top of the as-loaded runtime with whatever index is hosted with it

this could be hoisted/normalized in pyodide's initializer with e.g. extraLockUrls: []

this could be non-destructive, which might be better, and potentially support "punch-out" by setting a name to a null (ick!)

The concrete things this solves there:

auto-install-on-import
replacing packages in the pyodide stdlib

IPython has an optional dependency on jedi/parso (but still downloads them)

we haven't been able to make jedi work well enough in jupyterlite to use, so would rather replace it with dummy shims to save a couple megabytes on the wire

per-PR docs builds of packages that are in the pyodide stdlib and really just want one different

Thanks for the proposal @bollwyvl ! From JupyterLite side I can see why one could be tempted to do something like this, minimally interacting with upstream pyodide-lock.json and having something that works reasonably fast.
On one side I agree that no one wants to create yet another package manager, on the other I'm concerned that while such a solution should be easy to start with, it might be difficult to maintain or debug over time. Generating a lock file for packages is fairly standard task, and there existing tools we could re-use. While with this approach is fairly new packaging concept and so any issues would be ours. Unless you are aware of any packaging project that does similar things?

With #7 done, to be able to move further to something usable outside pyodide-build, would probably be to have a public API that can generate a single PackageSpec from an at-rest .whl, not yet on PyPI, already in a pyodide-lock.json, or otherwise uncharacterized.
Some thoughts on API design:

only accept Path
expose as...

pyodide_lock.spec_from_wheel as a standalone function
pyodide_lock.PackageSpec.from_wheel as a class method
both, with the implementation in a separate file from the spec itself

Out of scope:

downloading .whl would incur a lot more complexity
generating full pyodide-lock.json
CLI

I've got a working, but potentially out-of-date, strawman but I'm not precious about it... if there's another one in pyodide-build, that's fine, too.
The strawman implementation uses pkginfo (MIT, 30k .whl, no deps). This could be an extra dependency, lazily imported inside the implementation, as it would not be required to validate... but then pydantic is at least 150kb, so maybe who's counting (and [extras] are... kinda broken).

Added the above as a draft on #18... probably won't have any more time to respond this weekend, but had this kinda working in #17 before descoping, so figured I'd push it up so it could be discussed later.


Fix redirect on android artifacts for "window-core" module.

Fixes https://youtrack.jetbrains.com/issue/CMP-5959
Release Notes
Fixes - Multiple Platforms

(prerelease fix) Fix redirect on android artifacts for "window-core" module.

Can you write a workaround for application projects (exclude dependency on Android, and include the right one)?
Otherwise users have to wait for the next version to use it in multiplatform.

Workaround https://youtrack.jetbrains.com/issue/CMP-5959/Invalid-redirect-in-window-core#focus=Comments-27-10365630.0-0


[POC] Alter the existing enodebd state machine to handle on-the-fly config changes properly

POC implemented and initially tested on FreedomFi AGW.
Code works but in an E2E scenario and a proper PR might require changes.
Those further modifications and PR will be handled in a separate task.


Update local dev instructions in CONTRIBUTING.md

Update local dev instructions in CONTRIBUTING.md to reflect changes from the last few months.
@mistercrunch @michellethomas @graceguo-supercat

Codecov Report

Merging #6513 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #6513   +/-   ##
======================================
  Coverage    73.5%   73.5%
======================================
  Files          72      72
  Lines       10001   10001
======================================
  Hits         7351    7351
  Misses       2650    2650

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 56aa7ac...e371e44. Read the comment docs.


Fix memcached selector and labels

updating from quay.io/openstack-k8s-operators/infra-operator:dcc7dc061f30e78180a3635f0730b00409f910f1c19f93049f20aac860158ddb to quay.io/openstack-k8s-operators/infra-operator:6e7cb7a577393bff299ea199ad89845e868a41aee44f5ac5b0490b573a01c523
triggers an error because in https://github.com/openstack-k8s-operators/infra-operator/commit/8e55a15bddcc869f5463c76077bb449d2858a4f6 we erroneously deleted the "app" label and lib-common is not able to recreate the statefulset (nor we probably should) :
2024-11-20T01:41:04Z	ERROR	Reconciler error	{"controller": "memcached", "controllerGroup": "memcached.openstack.org", "controllerKind": "Memcached", "Memcached": {"name":"memcached","namespace":"openstack"}, "namespace": "openstack", "name": "memcached", "reconcileID": "0155da36-541b-481d-aca3-255e24a491a2", "error": "StatefulSet.apps "memcached" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"cr":"memcached", "memcached/name":"memcached", "memcached/namespace":"openstack", "memcached/uid":"6bddcfc1-63d4-424f-8b8d-91b7dcdf0e9c", "owner":"infra-operator", "service":"memcached"}: selector does not match template labels"}
with this patch we re-add the missing "app" label so that the existing resource can be reconciled.

/cherry-pick 18.0-fr1

recheck

@lmiccini: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name 	Commit 	Details 	Required 	Rerun command
ci/prow/infra-operator-build-deploy-kuttl 	72a3070 link 	unknown 	/test infra-operator-build-deploy-kuttl
Full PR test history. Your PR dashboard.

error: build error: Failed to push image: trying to reuse blob sha256:3d252ab42824f0f833f0fcf3c660065bd878cb4de12b9c69b6a1758287e338e8 at destination: pinging container registry quay.rdoproject.org: Get "https://quay.rdoproject.org/v2/": dial tcp <IP_ADDRESS>:443: i/o timeout

/test infra-operator-build-deploy-kuttl

/test infra-operator-build-deploy-kuttl


Custom Domains - booked by project creator but unavailable for collaborator

Preflight checklist

[X] I could not find a solution in the existing issues, docs, nor discussions.
[X] I agree to follow this project's Code of Conduct.
[X] I have read and am following this repository's Contribution Guidelines.
[X] This issue affects my Ory Cloud project.
[X] I have joined the Ory Community Slack.
[X] I am signed up to the Ory Security Patch Newsletter.

Describe the bug
A colleague of mine created a (paid) Ory cloud project and activated custom domains. When he visits https://console.ory.sh/projects/<PROJECT_ID>/custom-domains he can see the domain, when I visit the very same URL it says

Your plan does not have access to the Custom Domains feature.
Consider upgrading to a paid plan.

Reproducing the bug
See description
Relevant log output
No response
Relevant configuration
No response
Version
Ory cloud
On which operating system are you observing this issue?
No response
In which environment are you deploying?
No response
Additional Context
No response

Hi @aeneasr, thanks. At the moment, the information presented is just misleading. It would be OK to see that I'm not able to edit it but to see the information whatsoever.

We have identified the issue and have an item on the backlog, however the fix is not trivial at the moment and it might take a bit for it to be resolved.


proposal: cmd/go: add go work use -r -maxdepth

I propose that we add a new optional -maxdepth <uint> flag to go work use -r moddirs. It limits the level of directories to descend into for each moddirs, like how the -maxdepth in the Unix find command works.

what are the practical/real world cases is which this is useful?

most go modules are defined at the root directory of repos, and most people have go projects cloned onto their local filesystem either in one directory (flat layout) or in a hierarchy of sub-directories with a known/limited depth. So a -maxdepth flag can be used to limit the search scope in these cases and prevent bogus or unwanted go.mod files from becoming accidentally included in the work space (e.g. issue #51959) at which point users would then have to prune those out, which is cumbersome.

Depth seems like a poor proxy for the actual issues, a multi module repository can easily have modules at different depths, while a checked out dependency in the same workspace (eg, x/tools from the other issue) may have "unwanted" go.mods at the same depths.
I don't see this as a generally useful mechanism for excluding unwanted module declarations.

-maxdepth is only useful for cases where the desirable depth of directory for where to find go modules to be included in the work space is known. I suspect this is the common case.
Even for cases where a directory level contains both desirable go modules and undesirable ones, limiting the search scope with a max depth would result in fewer (or equal) undesirable ones that need to be pruned out than that of allowing the search scope to be unbound.

CC @bcmills @matloob

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

Because -r is not the default, another option is to use other file walking tools to prepare a list of directories passed to go work use. It seems like -r does not need all the bells and whistles.

Because -r is not the default, another option is to use other file walking tools to prepare a list of directories passed to go work use. It seems like -r does not need all the bells and whistles.

Yeah, I'm okay with that.

This proposal has been declined as retracted.
— rsc for the proposal review group


Sync this repo with RuboCop GOV.UK

https://github.com/alphagov/rubocop-govuk/issues/73
This removes all custom config and fixes the resulting
linting issues. Please see the commits for more details.

Bump 😸

Testing on Integration (creating a doc with an image and then removing it) works fine.


It dozent work in windows 11

I troed it in qindows 11 and it dozent work the colour, blur, etx feature does work but the felt alinged start button and center app icons dozent works so please update it for windows 11

Yeah has some odd errors for me in Windows 11 - most if it worked but I was unable to open the Windows 11 Display Settings windows (one you change your resolution, etc). After uninstalling this the window would open normally

I want the start button in left and apps in center i like apps in centre but start button in centre is a bit annoying so it would be great if u managed to slide the start button to the left in center taskbar mode

Yeah, that's what I'd like too

To be able to focus on major/current bugs I had to close all issues. The issues section has gotten very messy to a point that I couldn't follow it anymore. Most issues are duplicates, very old or are already fixed/solved. Feel free to reopen this issue if you still have this issue on the latest version of TaskbarX to get my attention. All feature requests have been put in a list here: 💡| Feature requests #870
I hope you understand ❤


41 character bug

Type of issue
[ x ] Bug
[ ] Question (e.g. about handling/usage)
[ ] Request for new feature/improvement
Expected Behavior
The QR code generated by 41 characters shall can be recognized.

Current Behavior
The QR code generated by 41 characters cannot be recognized.

Possible Solution (optional)

Steps to Reproduce (for bugs)

QRCoder.QRCodeData code_data = code_generator.CreateQrCode("some string", QRCoder.QRCodeGenerator.ECCLevel.H, true, true, QRCoder.QRCodeGenerator.EciMode.Utf8);

Note the length of "some string" should be 41, the content can be any ASCII characters, and the 4th parameter is set as true.

Use the code_data to generate a bitmap.

QRCoder.QRCode code = new QRCoder.QRCode(code_data);
Bitmap bmp = code.GetGraphic(3, Color.Black, Color.White, true);

Show the bmp on screen, use other application to scan the code.
The QR code of bmp cannot be recognized.

Your Environment
Windows with .NetFramework v4.6

I can reproduce in 32 string length:
            QRCodeGenerator qrGenerator = new QRCodeGenerator(); QRCodeData qrCodeData = qrGenerator.CreateQrCode("https://www.gallery.kz/p/20309pi", QRCodeGenerator.ECCLevel.Q, true, false, QRCodeGenerator.EciMode.Utf8); QRCode qrCode = new QRCode(qrCodeData); using (Bitmap image = qrCode.GetGraphic(pixelsPerModule, Color.Black, Color.White, true))

If you change string with the same length the qrcode will be nonrecognizable too.

Hi @morrowind ,
I could re-produce the error. It happened if someone used ECI-mode and entered a payload which maxed out a specific QR code version. Unfortunately the additional headers for ECI mode weren't taken into size calculation.
The error was fixed in: https://github.com/codebude/QRCoder/commit/012dee3edb5be2508f35ebc6a3d1d9311dc2c256
And thus will be publicly available with the next Nuget package update.


[11.x] Let logger with replace_placeholders to be tap-able via env

Added tap options to driver with replace_placeholders=true so the options can be configurable from env. The env should then provide list of class-string.
This is added to make it easier to customize processor & line formatter without importing log config.

I am closing this pull request because it lacks sufficient explanation, tests, or both. It is difficult for us to merge pull requests without these things because the change may introduce breaking changes to the framework.
Feel free to re-submit your change with a thorough explanation of the feature and tests - integration tests are preferred over unit tests. Please include it's benefit to end users; the reasons it does not break any existing features; how it makes building web applications easier, etc.
Thanks!


Dynamic require in dependencies breaking apps with version 0.49.0

Is this a bug report?
Yes

Have you read the Contributing Guidelines?
Yes
Environment
Environment:
OS:  macOS Sierra 10.12.5
Node:  7.10.0
Yarn:  0.24.5
npm:  4.2.0
Watchman:  4.7.0
Xcode:  Xcode 8.3.3 Build version 8E3004b
Android Studio:  2.3 AI-162.4069837
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0
react-native: 0.49.0 => 0.49.0

Steps to Reproduce

prerequisite: Have a react-native app with version 0.49.0

Install and use a package with dynamic imports statements such as moment.js
Run the app
Witness red screen of death notifying of TransformError

Expected Behavior

I expected the project to build and run as it did for the RN version I was using before (0.48.4).
Actual Behavior

I got an error saying that a require() must have a string literal argument. Even though the responsible for this error was located in the source code of a dependency (Moment.js)
require('./locale/' + name);

Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

https://github.com/moment/moment/pull/4187

@nihgwu Thank you for pointing this out to me. I thought I had checked moment's github for this error but somehow missed it


Disable color picker and only select from predefined colors

Is your feature request related to a problem? Please describe.
I want content editors to stick to the predefined colors so they don't pick colors on the picker that mess up the aesthetic of the page/content.
Describe the solution you'd like
An option to disable the color picker(and input fields) so only the predefined colors are displayed and selectable.
Describe alternatives you've considered
...
Additional context
...

@nwazuo funny I came to post the exact same feature request. I have this project and I'm asked to have some color fields completely opened, and some others restricted to a color palette. I can replace the restricted field by a string field with hex options. But it does not give a color preview (only a name) and most importantly the data structure is not the same. One is a full color object and the other is just an hex string. That would force me to change my frontend. This is not ideal, especially if the clients change their mind along the way.
Anyway I had the the same requirement. If somebody has a work around, even if it's a bit hacky, I'd be interested.

@mig-hub Creating a fork and looking into the code to figure a way to hide it would be the way to go.
I remember inspecting CSS classes to try and write some custom CSS to hide the color picker but that didn't quite work out as the DOM structure and class names didn't lend itself to writing a selector that could target the color picker accurately.

I need exact the same thing. Any progress on it?

https://github.com/cositehq/sanity-plugin-simpler-color-input


Fix putWhen

This should fix #369.

Thanks for the patch, most appreciated! Let's continue all the discussions in #369.

Agreed in #369 that this isn't the way it was intended.


feat: lazy loading added to pages

Related Issue
Closes: #853
Changes made 👷🏻♂

Imported all the pages using react lazy
Added react suspense to the routes
Improved the loading spinner css to be shown at the center of the page

@tamalCodes I have made some changes. Now the navbar will appear while loading.

@tamalCodes I have made some changes. Now the navbar will appear while loading.

That is really cool addition, however, I would like something else. It is not about having a navbar, it is more about having a skeleton or a pre-defined structure that lets the user know that okay, the contents are loading in.
With looks like this, it will make the UX much better than having a simple spinner. The goal is to make our project much more UX-friendly and impressive !

Updates 🚧
Hi there, because of some personal and professional reasons we had to change our code structure, and UI. The changes are visible in this pull request, and will be merged as soon as they are done. Until then we need to halt all the progress (merging PRs).
There might be a few conflicts in this PR, we will work on those too.
We are also moving to a new domain : https://milanhub.org
Sorry for the inconveniences caused.
Team Milan.


Insert a BigQuery table only when the last modified timestamp is after a given timestamp

Describe the feature
The idea is probably very close to dbt_utils.insert_by_period_materialization, but I would like to decide to insert a BigQuery table. Because, a BigQuery table doesn't potentially any timestamp field. And even running queries just to get the information about the latest value is potentially costly.
And consider if a project has a hundred of models and it takes a long time to execute dbt run. moreover, it is accidentally killed or failed in the middle of the process. So, we have to rerun dbt run again, however we want to resume the process as much as possible in order to reduce cost and elapsed time. It would be nice to skip models whose last updated is within a specified period.
For instance, if we want to insert a table whose last updated timestamp is only more than 24 hours, a possible config is like below.
{{
  config(
    materialized="insert_by_last_modified",
    period="24 hours",
    enabled=(target.type == 'bigquery')
  )
}}

...

Describe alternatives you've considered
No idea.
Additional context
NA
Who will this benefit?
I think the feature is probably very useful for many BigQuery users.
Are you interested in contributing this feature?
Yes, I am interested in implementing it. But, I am not sure what is the best approach, since I am still very new to dbt. I need

Hi @yu-iskw, take a look at incremental models. In particular, the BigQuery-specific insert_overwrite strategy sounds like it might be what you're after.
Have you joined our community? If not, you should! By asking a question like this one in Slack, community members would help you uncover the larger problem and talk through the available approaches. (I notice you opened https://github.com/fishtown-analytics/dbt/issues/2667 as well, which someone in Slack could have quickly answered.) Of course, StackOverflow is still best for debugging specific errors.
There is one specific point you made that I want to call out:

however we want to resume the process as much as possible in order to reduce cost and elapsed time. It would be nice to skip models whose last updated is within a specified period.

This is a great idea! We have some thinking about a future approach here that would let you point to a previous build, and run only models that failed or skipped in that build. That's not here yet, but it's not far off.
In the meantime, if you materialize your biggest models incrementally, there's little pain felt by running them twice in quick succession, since the max timestamp that feeds into {% is_incremental() %} logic jumps ahead on the first go-round.
Otherwise, I do think it would be valuable to add BigQuery support for the insert_by_period materialization. There's an open issue for that (and more) in the dbt-utils repo, which is where that code is defined: https://github.com/fishtown-analytics/dbt-utils/issues/192

@jtcohen6 Thank you replying to my suggestion. I joined the community and I just start taking advantage of it like Show meta on the web UI like tags - Water Cooler - dbt Discourse.
I am not familiar with incremental materialization. I will give it a try. Even if I figure out missing piece against what I want to do, I will let you know.


CosmosDb bindings

I wonder if it should be possible to create a function with a cosmosDBbinding with Static web apps at the moment?
I get this error message when I try add a cosmosDB binding to a function:

Error in processing api build artifacts: the file 'products-post/function.json' does not specify a valid function with only HTTP triggers and bindings. Please ensure the JSON contains a single httpTrigger input trigger and a single http output binding.

My function.json looks like this:
{   "bindings": [     {       "authLevel": "anonymous",       "type": "httpTrigger",       "direction": "in",       "name": "req",       "methods": ["post"],       "route": "products"     },     {       "type": "http",       "direction": "out",       "name": "res"     },     {       "type": "cosmosDB",       "name": "inputDocumentIn",       "databaseName": "mydb",       "collectionName": "mycol",       "connectionStringSetting": "CosmosDBConnectionString",       "direction": "in",       "sqlQuery": "SELECT * from c"     }   ] }

Thanks for opening this issue. You can open this issue in https://github.com/azure/static-web-apps as it likely relates to your SWA experience.


MELD Speakers Mapping

What is the mapping for the speaker indices in the features file?

Thanks for your interest in our work.
The mapping for the speaker indices is
The examples for using DialogueCRN with RoBERTa features (i.e., IEMOCAP and MELD) are available now. You can see README.md in this repo for details.
If you have any other questions, please feel free to ask me.

We found that there is no fixed speaker mapping in the processed MELD features, and different sessions usually have different mappings.
In this work, our method only utilizes the sequence information of speakers, without strictly distinguishing which speaker each utterance belongs to.
If you need this speaker information, I suggest you retrain the features from raw data. Another alternative is to directly align the textual utterance in the features files with the original data (with full speaker information).

What is the mapping for the speaker indices in the features file?

Thanks for your interest in our work.
We found that there is no fixed speaker mapping in the processed MELD features, and different sessions usually have different mappings.
In this work, our method only utilizes the sequence information of speakers, without strictly distinguishing which speaker each utterance belongs to.
If you need this speaker information, I suggest you retrain the features with fixed speaker mapping from raw data. Another alternative is to directly align the textual utterance in the features file with the original data (with full speaker information).


Fixed usage of ToolChoice parameter with OpenAI

Fix passing ToolChoice parameter to ChatRequest
PR Checklist

[x] Read the Contributing documentation.
[x] Read the Code of conduct documentation.
[x] Name your Pull Request title clearly, concisely, and prefixed with the name of the primarily affected package you changed according to Good commit messages (such as memory: add interfaces for X, Y or util: add whizzbang helpers).
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. Fixes #123).
[x] Describes the source of new concepts.
[x] References existing implementations as appropriate.
[x] Contains test coverage for new functions.
[x] Passes all golangci-lint checks.

Tackled in https://github.com/tmc/langchaingo/pull/829


A_Fistful_of_Darkness_V1.4 - Update and minor changes

Changes / Comments

Name change of The Law Special Ability (keeping up with bookV1.4)
Better readability for resisting via updated background picture
Fixed image preloading (from dropbox to github)
Fixed text for rolling Riders

Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[X] Does the pull request title have the sheet name(s)? Include each sheet name.
[X] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.

Hello,
when I click on the link "Character Sheet Info" I get a "not authorized"
error message. And yes, I'm logged in.
Is there something to do on my side?
thanks in advance for the helping hand.
-Stefan
Am So., 18. Apr. 2021 um 11:28 Uhr schrieb roll20deploy <
@.***>:

Character Sheet Info
https://app.roll20.net/managesheets/A Fistful of Darkness/roll20-character-sheets Roll20
Internal Use only.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Roll20/roll20-character-sheets/pull/8740#issuecomment-821961433,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJT4RHDFAWF2LW54FOLOVRDTJKQ4DANCNFSM43EAW7PQ
.


cmd/go: type inference fails for unused type in generic type alias

Go version
go version devel go1.24-669d87a Thu Dec 19 19:19:59 2024 -0800 darwin/arm64
Output of go env in your module/workspace:
AR='ar'
CC='clang'
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_ENABLED='1'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
CXX='clang++'
GCCGO='gccgo'
GO111MODULE=''
GOARCH='arm64'
GOARM64='v8.0'
GOAUTH='netrc'
GOBIN=''
GOCACHE='/Users/dmitry/Library/Caches/go-build'
GODEBUG=''
GOENV='/Users/dmitry/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFIPS140='off'
GOFLAGS=''
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/59/2slgfdl91td3z8w75b7zh6kw0000gn/T/go-build2195658086=/tmp/go-build -gno-record-gcc-switches -fno-common'
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMOD='/Users/dmitry/alias_example/go.mod'
GOMODCACHE='/Users/dmitry/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/dmitry/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/dmitry/sdk/gotip'
GOSUMDB='sum.golang.org'
GOTELEMETRY='on'
GOTELEMETRYDIR='/Users/dmitry/Library/Application Support/go/telemetry'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/Users/dmitry/sdk/gotip/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='devel go1.24-669d87a Thu Dec 19 19:19:59 2024 -0800'
GOWORK=''
PKG_CONFIG='pkg-config'

What did you do?
$ > cat main.go
package main

type A[V any] = struct{}

func Foo[V any](_ A[V]) {}

func main() {
	Foo(A[int]{})
}

$ > gotip version
go version devel go1.24-669d87a Thu Dec 19 19:19:59 2024 -0800 darwin/arm64

$ > gotip run main.go
# command-line-arguments
./main.go:8:5: in call to Foo, cannot infer V (declared at ./main.go:5:10)

What did you see happen?
Compilation failure.
What did you expect to see?
Successful compilation, even tho type A[V any] = struct{} doesn't make much sense.
Notes:

Original thread on reddit.

Related Issues

cmd/compile: "type does not match inferred type" even though it compiles when the inferred type is explicitly provided as type argument #53389 (closed)
spec: type inference doesn't work for struct literals #50482 (closed)
cmd/compile: type arguments for generic aliases are not checked against type parameter constraints #69576 (closed)
go/types, types2: go generic assert compile escape #52228 (closed)
cmd/compile: error using generics: "incompatible type: cannot use n (variable of type MyType[T]) as T value" #48543 (closed)
cmd/compile: specific type for generic struct type in recevier #62030 (closed)
cmd/compile: infer generic type based on the function return type #54791 (closed)
cmd/compile: internal compiler error: assertion failed #54028 (closed)
spec: function type inference ignores type parameter constraints #50272 (closed)
cmd/compile: Bad error message on missing type constraint #55961 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

@griesemer @timothy-king

CC @griesemer


web page not safe !

hei...  @kgretzky
I have read the evilginx 2.1 installation instructions from breakdev.org ..I am sure that everything has been done properly....I'm running evilginx 2 .1 in developer mode .but when I enter my site it says it's not safe.
I think there is a certificate error..now I'm sending you a screenshot of the actions I have made to you..

I have made no adjustments other than these images...do I have a settings file where I can type the location of the folder where the certificates are stored ?? it probably does not recognize the location of the certificate folder ?? What do you think @kgretzky  ??

Evilginx will generate a new root CA certificate when it runs for the first time. You can find the CA certificate at $HOME/.evilginx/ca.crt or %USERPROFILE%.evilginx\ca.crt. Import this certificate into your certificate storage as a trusted root CA and your browsers will trust every certificate, generated by Evilginx.

That part of the blog post was crucial.

@kgretzky i know it... look at the sixth picture ... ca certifica in /root/.evilginx/crt/ca.crt
but it is not working.. Do I need to move the ca.crt certificate file to another folder?? @kgretzky


Error following tutorial

Following the tutorial on the quick start guide, step 5 generates the following error:
cd /workspaces/isaac_ros-dev && \
  colcon build --symlink-install && \  #<< problematic command
  source install/setup.bash

Error:
--- stderr: isaac_ros_apriltag
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/colcon_core/executor/__init__.py", line 91, in __call__
    rc = await self.task(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/colcon_core/task/__init__.py", line 93, in __call__
    return await task_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/colcon_ros/task/ament_cmake/build.py", line 59, in build
    rc = await extension.build(
  File "/usr/lib/python3/dist-packages/colcon_cmake/task/cmake/build.py", line 87, in build
    rc = await self._reconfigure(args, env)
  File "/usr/lib/python3/dist-packages/colcon_cmake/task/cmake/build.py", line 133, in _reconfigure
    buildfile = get_buildfile(cmake_cache)
  File "/usr/lib/python3/dist-packages/colcon_cmake/task/cmake/__init__.py", line 112, in get_buildfile
    if 'Ninja' in generator:
TypeError: argument of type 'NoneType' is not iterable
---
Failed   <<< isaac_ros_apriltag [0.02s, exited with code 1]
Aborted  <<< isaac_ros_image_pipeline [0.02s]

Summary: 25 packages finished [3.06s]
  1 package failed: isaac_ros_apriltag
  1 package aborted: isaac_ros_image_pipeline
  1 package had stderr output: isaac_ros_apriltag
argument of type 'NoneType' is not iterable

This looks like it might be an error in the colcon tool itself. Are you successfully able to build this workspace if you remove isaac_ros_apriltag and only build the other packages?
I found this issue in colcon-cmake with a merged PR that might address the problem you're seeing.

Removing isaac_ros_apriltag results in :
Starting >>> isaac_ros_image_pipeline
[4.221s] ERROR:colcon.colcon_cmake.task.cmake.build:Failed to parse previous --cmake-args from '/workspaces/isaac_ros-dev/build/isaac_ros_image_pipeline/cmake_args.last': unexpected EOF while parsing (<unknown>, line 0)
Finished <<< isaac_ros_image_pipeline [1.42s]

Summary: 26 packages finished [5.27s]

Patching the colcon-cmake locally as per the issue you referenced, did result in a successful build at that stage of the quick start guide. (Happy to close the issue)
Q: Are you aware how often is the colcon-cmake package updated/released? Feels to me that it hasn't been thought as critical from April - does the standard build process go through the repo?

I'm not sure at what cadence the colcon-cmake package is released; the release schedule on that GitHub repository shows the most recent release in August 2022. We use the prebuilt Isaac ROS Docker container for most of our development workflows, which has lots of the dependencies baked into the image.
As for the test failure you've reported, could you please send the log file for that test? You can find it under isaac_ros-dev/log/latest_test (assuming that this was the most recent test run).


Set intent to danger if numberField fails min/max validation

I am not sure about this change.  Seems like we want a more general story around validation and display of validation state in hoist controls.  This seems pretty specific and somewhat arbitrary.
How does this differ from just entering a non-number?  Would love to discuss more.

Just wanted to add some notes here, I feel like HoistField should have a validation method and each component extending HoistField should have it's own implementation of the validator.

Gil -- yes, something like that is what I was thinking.    Please feel free to start sketch out a design in this ticket, if you have any ideas?   Maybe a list of the template methods, what they return, how an app would use them to modify validation, and how a control writer would use them to display validation?
Note:  I do not want to start coding this without a plan.  This is a tricky thing to make useful to application -- very easy to build something that is unusable....

Closing this in favor of https://github.com/exhi/hoist-react/issues/317


Add Windows 11 23H2 support

Please add Windows 11 23H2 support
https://www.microsoft.com/en-us/download/details.aspx?id=105667

please mark this closed

yes it was overlooked, I'm already on the case, thanks!

@msfreaks Please close this issue.

Tested and confirmed wonderful @JonathanPitre !


Missing do_objectID in ColorAsset/GradientAsset schemas

Looks like ColorAsset/GradientAsset schemas are missing do_objectID properties however they're generated for file format 121

👍


Enforce formatting with alejandra

Yes, I was thinking the same thing and was just reading the alejandra readme yesterday for this reason. I will add this to my todo for Ngipkgs.


Fix bug in index of loop in LVT_MaxTimeMod.F90

The do loop is indexed by "k", but the new variable "kk" is used within the loop.  The corresponding file LVT_MinTimeMod.F90 correctly has this do loop indexed by "kk".
This bug was introduced by pull request #542 .

Thanks for catching this @dmocko. The test case ran fine for me; did an error occur on your end?
Regardless, I'll go ahead and merge.

No, I did not encounter an error.  Have not run LVT today.  I just noticed the difference when updating my code.

Gotcha. Good eye.


[R] release <IP_ADDRESS>

Could you please also kindly add CMakeLists.txt as a new line to R-package/.Rbuildignore? In this way we don't have CMakeLists.txt in the built package.

@hetong007 Done.


refactor(@angular-devkit/build-angular): remove postcss-import

We use css-loader which already handles resolving of @import rules.
https://github.com/webpack-contrib/css-loader#import

Umm.. This causes imported content not to be prefixed
/* normal-comment */
/*! important-comment */
-    section { -ms-flex: 1; flex: 1 }
+    section { flex: 1 }
/* normal-comment */
/*! important-comment */
    div { -ms-flex: 1; flex: 1 }
/*# sourceMappingURL=styles.css.map*/


Lost swiftpp.xcodeproj in that last commit??

 Run 'cmake -G Xcode' to generate the Xcode project.
I'm in the middle of major changes (as time permit). Performance improvement but also Linux support, so an Xcode project wasn't up to the task anymore. Also, llvm/clang build system is cmake based so it's easier to track changes in those.

Ok, thanks. That wasn't immediately obvious. I'll call that closed but do please update the readme.


Add sample test cases for Passwordless functionality

1-Verify that the user can login using a passwordless authentication method.
2-Verify that the user is not required to enter a password during the authentication process.
3-Verify that the system sends an email or SMS message to the user with a verification code or link to complete the authentication process.
4-Verify that the verification code or link is valid for a limited time only.
5-Verify that the user can request a new verification code or link if the old one has expired or been invalidated.
6-Verify that the verification code or link is unique and cannot be used more than once.
7-Verify that the system displays an appropriate error message if the user enters an incorrect verification code or link.
8-Verify that the system blocks access to the user's account if too many incorrect verification attempts are made.
9-Verify that the user can update their email or phone number used for passwordless authentication.
10-Verify that the user can disable or enable the passwordless authentication method at any time

Hi, I would like to take this issue.


Merge 'origin/develop' into main

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

v1.4.0
GitHub release

Your semantic-release bot :package::rocket:


cos window multiple feature map (training)

Hi,
I noticed that while training, the CNN output (before DCF) is not mult with cos window (or hann) in contradiction to tracking pipeline that mult the CNN output.
Why?

Because the hanning window will 'tell' DCFNet where is the target. (will make the DCFNet think the object with high RGB is target.)
I want to train the network with hard cases.
@he010103  it is easy now. ^.^  I try to use pytorch recently (autograd).


Make TopBar Public By Default

In reference to #583.

@codydaig I've tested this, and it works as expected.
However, I'm having an issue with the isPublic field of the Menu. I'm not quite sure what the point of this field is; Is it necessary since we have the isPublic field on individual Menu Items & Sub Items? Especially, since this change (rightfully) has moved the isPublic inheritance from the Menu, to the Items.
It doesn't make sense that I would need to set topbar isPublic: true in order to have just one Menu Item (in this case Articles) render for Guests. I'd rather explicitly define what Menu Items are public.
We'd have to modify the shouldRender() member of the Menu service to accommodate what I'm proposing.
Anyone else have any input on this? @rhutchison @trainerbill

@mleanos The way I went about this implementation is that all menu items have a default isPublic value of false. However SubMenuItems inherit their parent's isPublic status still.

It doesn't make sense that I would need to set topbar isPublic: true in order to have just one Menu Item (in this case Articles) render for Guests. I'd rather explicitly define what Menu Items are public.

That is what this PR fixes. It makes the topBar public by default.

However, I'm having an issue with the isPublic field of the Menu. I'm not quite sure what the point of this field is; Is it necessary since we have the isPublic field on individual Menu Items & Sub Items? Especially, since this change (rightfully) has moved the isPublic inheritance from the Menu, to the Items.

If i'm understanding your proposal correctly: Having the isPublic option on the menu bar allows people to create navigation bars that you must be logged in for it to show at all. However, that option can be left out and it defaults to true.
https://github.com/codydaig/mean/blob/feature/issue583/modules/core/client/services/menus.client.service.js#L63

@codydaig I realize that the isPublic field was intended to be used to distinguish the behavior of multiple Menu's from each other; providing configurable rendering.
What I'm trying to wrap my head around is the purpose of the isPublic field. If we're setting the roles & isPublic fields on the Menu Items & Sub Items, these settings should determine the rendering of the Menu. With this PR, the isPublic field for the Menu solely acts as an overriding setting. This is where the logic breaks down for me.
This line seems to be useless https://github.com/meanjs/mean/blob/master/modules/core/client/services/menus.client.service.js#L27 as it only serves as an override; when the settings on the Menu items should determine this.
If I don't set any of my Menu Items' roles or isPublic fields, the default is set to none & false respectively. Now, if I set the topbar Menu isPublic: false, the topbar still displays. However, it doesn't render any of the Menu items. This clearly, IMHO, demonstrates the uselessness of the isPublic field. Now, if we're considering having a separate Menu, say sidebar that we want hidden to Guests, then this should be accomplished with a different field. How it stands now, the isPublic field is being used incorrectly to serve two purposes.
My proposed change would look something like this...
// A private function for rendering decision
    var shouldRender = function (user) {
      var render = false;

      if (user) {
        if (!!~this.roles.indexOf('*')) {
          render = true;
        } else {
          for (var userRoleIndex in user.roles) {
            for (var roleIndex in this.roles) {
              if (this.roles[roleIndex] === user.roles[userRoleIndex]) {
                render = true;
              }
            }
          }
        }
      } else {

        if (this.items) {
          this.items.forEach(function (menuItem) {
            if (menuItem.items) {
              menuItem.items.forEach(function (subMenuItem) {
                if (subMenuItem.isPublic) render = true;
              });
            }
            else {
              if (menuItem.isPublic) render = true;
            }
          });
        } else {
          if (this.isPublic) render = true;
        }
      }

      return render;
    };

If the user isn't authenticated, then we should check if there are any Menu items that do allow public viewing.

@mleanos @codydaig @lirantal I think isPublic property should be removed, and we should only rely on the roles declaration.  We can have a 'guest' role which covers unauthenticated users.

Sounds Good. I've got a proposed solution coming soon. Thanks for the feedback! :-D

@rhutchison @mleanos I know the build will probably fail because I haven't modified the tests yet. But, I wanted to get your opinions on this strategy of removing the isPublic.
It removes the isPublic option and relies on the roles to determine if it should render or not. '*' means it will render for everyone, including users that are not logged in. And since every user gets created with the 'user' role, then you just have to add the 'user' to the list of allowed roles to make it so only people who are logged in can view it.
I'm open to suggestions, this was just the fix that came into mind first.

@codydaig I know we've talked quite a bit about this on Gitter yesterday... Just wanna get this out to the rest of the team.
From my perspective, the Menu defaultRoles shouldn't be *public"; it should be locked down to [user, admin]. If I want to have a Menu item or sub items public, I would go in and make that change. It seems less prone to error that way.
My other consideration would be the use of the shouldRender() method on the Menu. It's needed for the Menu Items & Sub Items, but not a Menu (topbar in this case). For me the Menu is a completely different type of entity than the Items & Sub Items, but they are being treated the same.
However, removing the render check, on the Menu, in the header client view might be too big of a change right now? At least before we get a decent consensus from the community.
@lirantal @rhutchison @cdriscol @danaronoff @igorauad @lirantal @AlexisTM

@mleanos I removed the tests that check for isPublic since I removed that option and solely rely on the roles option. It's ready for review! :-D

@codydaig I think this looks good, and I've tested it. Everything works as expected...
I made some modifications that address the issues we've talked about. Can you review this, and see if it's in line with those concerns? If this doesn't look good enough, and we're not ready to make these changes, then I say this PR is good to go.
https://github.com/mleanos/mean/tree/issue583

@codydaig This looks good. I've tested. Thank you for working with me on this. I think this is the right way to implement these changes.
LGTM. From my perspective, this is ready to be merged.
@rhutchison @lirantal any feedback?

Good then

I think there are some issues after this merge.
I could see, Sign Up & Sign In both are displaying 'Display Name' of user after logging in.
In Chat Option, even the empty messages r getting posted & 'Email' has become little blur or not readable.

@ANUPJHA I don't think this is an issue with the merge, or anything else related to the code. I've seen the issue with the Display Name showing up in place of the User's avatar. Is this what your experiencing? If so, it's most likely caused by the User's profileImageURL set to a file that it can't find. This happens when I switch between databases and/or the profile image uploads directory getting overwritten. Check that.
As far as those other issues, I can't reproduce. Can you check additional factors that might be causing issues on your end? For instance, your application by not be loading properly due to missing dependencies.

@ANUPJHA If your still having issues, go ahead and open a issue. Since this was merged in, the discussion is bound to get lost.


Getting 'Could not create SSL/TLS secure channel' error when trying to run this sample application

Hello:
I am trying to use this tutorial  (https://docs.microsoft.com/en-us/power-bi/developer/embed-sample-for-customers ) to test the Apps Own Data application that is provided as part of this tutorial. I have tried both options to run/test this application:
a) Using the Embedding Setup Tool and then trying to run the code in Visual Studio
b) Followed the steps to complete the manual setup process (AD setup, Power BI API setup and granting of permissions etc) and then downloading of the sample application from GitHub and then updating web.config manually to run/test the application.
When I try to run the application (using either of the both above methods) then I am getting this error message below:
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
I do get the popup window in IE where it asks to select 'Embed Report'. 'Embed Dashboard' or 'Embed Tile' option but once I select/click on the 'Embed Report' button then I get the above 'SSL/TLS secure channel' related exception.
Few things I would like to ask:

I am using a Power BI Pro trial license when testing this application. My published sample report on Power BI website was published using the trial license as well so could this error be related to any possible limitations associated with a trial Power BI Pro license?
I am using A1 pricing tier for the dedicated Power BI Embedded capacity that I have created via my Azure portal access. Does this error has anything to do with the A1 pricing tier?

I would appreciate if someone from your team can help me figure out how to resolve this so I may complete the testing of the Apps Own Data application. Thank you!

Thanks for your comment, @naushadsiddiqui. This looks like a support request rather than documentation feedback. You might find a solution in the Power BI Community, found at https://community.powerbi.com. If not, you can get support by going to https://support.powerbi.com.
However, I can answer your 2 questions above.

As long as your using a Pro Licences (regardless if it is a trial or not) you should be fine.
The error is not related to the SKU you are using

Also, see if these articles might help:
https://community.powerbi.com/t5/Desktop/The-request-was-aborted-Could-not-create-SSL-TLS-secure-channel/td-p/122743
https://stackoverflow.com/questions/37324743/azure-api-the-request-was-aborted-could-not-create-ssl-tls-secure-channel-http
Thank you.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Update screenshot in getting started tutorial

Pertinent section of the Wagtail docs

Section
Details

The screenshot, as seen attached is a bit misleading. To create a blog post as a child of the index page, the add child page selected should be the one attached to the Blog Index page as opposed to the home page as shown int the screenshot.
A pull request for this will be submitted shortly.

Thanks for the report @Julietadeboye! This has already been handled by @activus-d in #9303, and the fix will be visible in the next version of the docs.

Alright, thanks @gasman


vaccine trade name

"I noticed that the subject page for vaccine Menveo does not show the trade name, although it is present on the vaccine ontology page and at the EBI page.  Wonder what this is about??"
http://hipc-dashboard.org/#vaccine/vo-0001246/vaccine
http://www.ontobee.org/ontology/VO?iri=http://purl.obolibrary.org/obo/VO_0001246
https://www.ebi.ac.uk/ols/ontologies/vo/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FVO_0001246
(from Ken's email)

The latest version of the source data at http://purl.obolibrary.org/obo/vo.owl (redirected to https://raw.githubusercontent.com/vaccineontology/VO/master/src/VO_merged.owl) of date July 18, 2020, version 1.1.102, is used. There are more than one way of presenting trade names in the source data. The earlier extracting code does not cover those including VO-0001246.

Tested in production, works as expected.  Note that not all vaccines have a proper name or a trade name, they are left blank in the GUI in that case.


cmd/compile: a[1.0 << s] should be accepted

Per the fix for #14844, https://play.golang.org/p/fWbHLgkJ7Z should now be accepted by the compiler.

Ping Robert.
I assume this is a release-blocker, given the spec update?

Will look into this tomorrow. It's not spec compliant anymore but I don't think it's a release blocker - after all there's a trivial work around (just write a[1 << s] instead). Leaving as is for now in case there's an easy fix.

I had started working on this at some ungodly hours of Saturday morning but I couldn't  get a proper cast/conversion to int in https://github.com/golang/go/blob/992ce90f662467f04dd93b3bb565bb0414f82999/src/cmd/compile/internal/gc/const.go#L262
so I'll defer to you @griesemer :)


DTIAtlasFiberAnalyzer and Compressing VTKs

Hi,
Is it possible for the tool to compress the output vtk files by default?
Thank you!
Rachel

has been resolved a while ago


Investigate how to implement socket.io with Flask

might need extra configuration for nginx
https://flask-socketio.readthedocs.io/en/latest/deployment.html#using-nginx-as-a-websocket-reverse-proxy

https://turbo-flask.readthedocs.io/en/latest/quickstart.html#how-to-add-to-your-project
Package to update HTML using server side events
Can send to select clients
Need to find way to integrate with socket io


Beamer Bridge Minimal Website

Description
When announcing Beamer we want to also have a website for the project.
Acceptance Criteria
Minimal static website.

Sorry, that we did not push any status updates. A repository beamer-bridge/www.beamerbridge.com has been created. The domain is registered and working (currently only shows under construction). The content of the website has been finished and the responsiveness has been heavily optimized. It will need a final look by @olympe-silve but I'm optimistic we are good to go.


convert Yips wiki pages to sphinx docs

@kadler,
I have the draft done for the conversion for issue #19 .

@kadler How can I get a account to login the Jekins?

I've added you

@kadler It seems make -j4 caused the failure. RUNSQLSTM started before CRTSRVPGM and could not get the lock which resulted in

SQL7909  10       1  Position 1 IPLUG4K was created, changed, or dropped, but object not modified.

10 level severity errors found in source

I tried on my 7.4 box with make -j4. I could get SQL7909  but it didn't fail my make right after the sql errors. Do you have any ideas? Can we don't use the parallel make?

Aha! The xmlstoredp.sqlinst will result in the generic sqlinst rule running, but it has no dependency on xmlstoredp.srvpgm. Unfortunately, I don't think that we can create another rule that defines the prereq for the srvpgm and have make keep using the generic rule (from what I can tell, make will ignore the generic rule in that case :frowning_face:). Since we only have one SQL script, we could update the existing generic rule to require a matching srvpgm, eg.
-%.sqlinst: src/%.sql
+%.sqlinst: src/%.sql %.srvpgm
 	system -q "RUNSQLSTM SRCSTMF('$<')" && touch $@

@kadler The dependency you suggested looks working. But now I got this error:
> bash-4.4$ make -j4 build-procedure
> (system -q 'CHKOBJ XMLSERVICE *LIB' || system -q 'CRTLIB XMLSERVICE') && touch XMLSERVICE.lib
> system "CRTSQLRPGI OBJ(XMLSERVICE/xmlstoredp) SRCSTMF('src/xmlstoredp.sqlrpgle') OBJTYPE(*MODULE) REPLACE(*YES) RPGPPOPT(*LVL2) COMPILEOPT('INCDIR(''src/'') TGTCCSID(37)')" > xmlstoredp.log 2> xmlstoredp.msg && rm xmlstoredp.log xmlstoredp.msg || touch xmlstoredp.failed
> system "CRTRPGMOD MODULE(XMLSERVICE/plugconf) SRCSTMF('src/plugconf.rpgle') DBGVIEW(*ALL) REPLACE(*YES) TGTCCSID(37)" > plugconf.log 2> plugconf.msg && rm plugconf.log plugconf.msg || touch plugconf.failed
> system "CRTRPGMOD MODULE(XMLSERVICE/plugbug) SRCSTMF('src/plugbug.rpgle') DBGVIEW(*ALL) REPLACE(*YES) TGTCCSID(37)" > plugbug.log 2> plugbug.msg && rm plugbug.log plugbug.msg || touch plugbug.failed
> test ! -e plugconf.msg || cat plugconf.msg
> system "CRTRPGMOD MODULE(XMLSERVICE/plugipc) SRCSTMF('src/plugipc.rpgle') DBGVIEW(*ALL) REPLACE(*YES) TGTCCSID(37)" > plugipc.log 2> plugipc.msg && rm plugipc.log plugipc.msg || touch plugipc.failed
> RNS9313: Library XMLSERVICE cannot be found.
> RNS9309: Compilation failed. Module PLUGCONF not created in library XMLSERVICE.

Looks like %.lib was not done and then the other dependencies started executing.  build-main, build-cgi... all have this problem on my box today. Does system crtlib command run in a child process and cause make not wait?

Looks like all the build rules need to have a dependency on the library just like this one: https://github.com/IBM/xmlservice/blob/master/Makefile.in#L117

I tried adding dependency of creating library ahead, but it didn't work. I saw CRTLIB was ran ahead, but the following CRTMOD just failed with no library found. So I guessed make didn't wait for CRLIB done.
Not like svrpgm and sqlint dependency worked.

The .lib dependency seems not working. I tried your Makefile.in also got this:
bash-4.4$ make -j4 build-cgi
(system -q 'CHKOBJ XMLSERVICE *LIB' || system -q 'CRTLIB XMLSERVICE') && touch XMLSERVICE.lib
system "CRTRPGMOD MODULE(XMLSERVICE/xmlcgi) SRCSTMF('src/xmlcgi.rpgle') DBGVIEW(*ALL) REPLACE(*YES) TGTCCSID(37)" > xmlcgi.log 2> xmlcgi.msg && rm xmlcgi.log xmlcgi.msg || touch xmlcgi.failed
system "CRTRPGMOD MODULE(XMLSERVICE/plugconf) SRCSTMF('src/plugconf.rpgle') DBGVIEW(*ALL) REPLACE(*YES) TGTCCSID(37)" > plugconf.log 2> plugconf.msg && rm plugconf.log plugconf.msg || touch plugconf.failed
system "CRTRPGMOD MODULE(XMLSERVICE/plugbug) SRCSTMF('src/plugbug.rpgle') DBGVIEW(*ALL) REPLACE(*YES) TGTCCSID(37)" > plugbug.log 2> plugbug.msg && rm plugbug.log plugbug.msg || touch plugbug.failed
test ! -e xmlcgi.msg || cat xmlcgi.msg
test ! -e plugconf.msg || cat plugconf.msg
RNS9313: Library XMLSERVICE cannot be found.
RNS9309: Compilation failed. Module XMLCGI not created in library XMLSERVICE.
test ! -e xmlcgi.log || ./parse.sh xmlcgi.log
RNS9313: Library XMLSERVICE cannot be found.


[Feat] Add a class selection for action buttons inside dialogs

Use the search function to see if this feature has already been suggested.

[X] I have searched for duplicate issues.

Description of new feature
It would be nice if we would change the class of the action button inside a dialog.
The default class of the button is statically set to "Flat", which looks bad for my application because I want to achieve a "Visual-Studio-Like" theme which has a white primary color and a dark accent together with the flat background style.
This leads to the button being completely white with the "Flat" class
For reference my dialog looks like this:

Package Version
6.0.0-rc

Hi guys,
A little bit off-topic but I saw this about a white-black theme.
As I like the shadcn library, I tried to add some trick to make a special shadcn theme for SukiUI.

Maybe I will do some specific shadcn style files to add for a theme like that.

I pushed the changes in the last commit.
To test the "shadcn mode", just call "Shadcn.Configure" in the Application class (it is commented in SukiUI Demo) :

It's a little mess with styles addition/changes for some controls but let's say it's an experiment for high contrast needs, and has zero influence on SukiUI if Shadcn is not called of course.


fix: show sn in drops listing

Thank you for your contribution to the Koda - Generative Art Marketplace.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix

Context
Fix #9971
Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

Screenshot 📸

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

set price
after set price

@preschian love how you show UI changes, doesn't take a lot of vertical space , will start doing the same , I hope you don't mind :d

pay 20 usd

😍 Perfect, I’ve sent the payout
💵 $20 @ 8.28 USD/DOT ~ 2.415 $DOT
🧗 1xjvRADwdJcnmUCLWerEHR4iGCT5EBTm4D4fzLLg4LcAC9p
🔗 0xc1511a7fe265a814c7d6ed77ecc965640007eb3ea38669276c792ce8dbec2994
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


[Feature] support pass data from Terraform cloud resource to helm component

Is your feature request related to a problem? Please describe.
Below is my application that the RDS component will generate a secret name db-conn, it has a  DB_PUBLIC_HOST key with the valueI want to pass to helm component.
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: webapp
spec:
  components:
    - name: sample-db
      type: alibaba-rds
      properties:
        instance_name: sample-db
        account_name: oamtest
        password: U34rfwefwefffaked
        writeConnectionSecretToRef:
          name: db-conn
    - name: app
      type: helm
      properties:
        repoType: "helm"
        url: "xxx"
        chart: "app"
        version: "1.0.0"
        values:
          datasource:
            host: # how th get the secret key-value ("DB_PUBLIC_HOST") from rds db-conn?

Describe the solution you'd like
Add a velaql into component definition.
apiVersion: core.oam.dev/v1beta1
kind: ComponentDefinition
metadata:
  annotations:
    definition.oam.dev/description: Describes long-running, scalable, containerized services that have a stable network endpoint to receive external network traffic from customers.
  name: webservice
  namespace: {{ include "systemDefinitionNamespace" . }}
spec:
  schematic:
    cue:
      template: |
        ...
  status:
    velaql: |-
         import "velaql/op"
         mysecret: op.Read&{
               kind: "Secret"
               metadata: name : "db-conn"
         }
        myhost: op.DecodeBase64 &{
            decodeValue: mysecret.value.DB_PUBLIC_HOST
        }
        status: myhost.value
    customStatus: |-
      ...

The status of velaql should be passed into the context.velaql.
Then users can use output/input of component like:
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: webapp
spec:
  components:
    - name: sample-db
      type: alibaba-rds
      properties:
        instance_name: sample-db
        account_name: oamtest
        password: U34rfwefwefffaked
        writeConnectionSecretToRef:
          name: db-conn
     outputs:
        # the output is the mysql service address
        - name: myhost
          valueFrom: context.velaql
    - name: app
      type: helm
      inputs:
        # set the host to mysql service address
        - from: myhost
          parameterKey: properties.values.datasource.host
      properties:
        repoType: "helm"
        url: "xxx"
        chart: "app"
        version: "1.0.0"

Describe alternatives you've considered

Additional context

This is a simple proposal, we could combine with configuration management requirements
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: webapp
spec:
  variables:
     static:
         db_user: xxx
         db_database: xxx
         db_password: xxx
     discover:
        secret:
            name: xxx
            namespace: xxx
        nacos:
            url: xxx
            dataId: xxx
            group: xxx
  components:
    - name: sample-db
      type: alibaba-rds
      outputs:
        # the output is the mysql service address, endpoints are default provide and do not need to custom the definition.
        - name: myhost
          valueFrom: context.status.endpoints[0]
      properties:
        account_name: context.variables.db_user
    - name: app
      type: helm
      dependsOn: ["sample-db"]
      inputs:
        - from: myhost
          parameterKey: properties.values.datasource.host
      properties:
        repoType: "helm"
        url: "xxx"
        chart: "app"
        version: "1.0.0"
        values:
          datasource:
            user: context.variables.db_user

Final target
passing data from a cloud resource components to other components
Background

We are using deploy workflow step to manage all resource dispatching. At least we hope to use it in all scenairos. For now we are using both apply-component and deploy.

Name
deploy
apply-component

multicluster
✅

override/replication
✅

input/output

✅

deploy step's behavior of dispatch cloud-resource is not defined.

Design
Deploy Input/Output
Enable deploy step to pass data between the components it dispatches. In one deploy step, for combinations like Cluster/Resource, controller will guarantee that all inputs has been filled before dispatching it.
Example: "c1/configmap" will wait until "c1/svc" is dispatched and IO key endpoint is filled.
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: deploy-input-output
spec:
  components:
    - type: raw
      name: svc
      properties:
        apiVersion: v1
        kind: Service
        metadata:
          name: svc
        spec:
          selector:
            key: value
      outputs:
        - valueFrom: status.endpoint
          name: endpoint
    - type: raw
      name: configmap
      properties:
        apiVersion: v1
        kind: ConfigMap
        metadata:
          name: cm
      inputs:
        - from: endpoint
          parameterKey: data.key
  policies:
    - type: topology
      name: topo
      properties:
        clusters: ["c1", "c2"]
  workflow:
    step:
      - type: deploy
        name: deploy
        properties:
          policies: ["topo"]

Deploy behavior of cloud resource
TL;DR
Keep Configuration CR in control plane. Dispatch generated secret to managed clusters.
details
A quick review about how deploy is executed.
read selected policies -> topology -> override -> replicate -> applyComponents

Configuration-based components will be normally processed before applyComponents. In applyComponents, deploy step will

redirect configuration to local cluster.
dispatching generated secret which contains some connection info to specific cluster.

As a result, we will got one cloud resource and several secret in different clusters.
Note: in the first phase when combining deploy and cloud resource , we can disable override and replication policy for simplicity.
How to combine deploying cloud resource and input/output

dispatch secrets to managed cluster
set output to secret's name in Configuration status with key secretName
set input to use secretName and webservice component in managed cluster can read corresponding secret.

Since we have supported deploy step with data passing in https://github.com/kubevela/kubevela/pull/5161
What's the block on this issue now? @chivalryq

Here's some illustration of what we are meeting and the possible ways to solve this problem.
Possible solutions
Solutions can be divided into two kinds:

Pass Secret: The secret that contains connection info is created at managed cluster. Workload use the Secret name and key in Secret. This is solved.
Pass Value: The secret is not created in managed cluster. The required connection info is directly written in workload spec (e.g. env). This is the issue mainly cares. Unfortunately there's more problems in this way.

Problems

As displayed in mind map above, the main problem to pass Data is read ing data from either Configuration or Secret it created. Here is an image that tells relationship between Application, Configuration and Secret, which helps to understand 2.1 and 2.2.1

Demo of Passing Secret
Here's a demo about passing secret from cloud resource component to other worload. In this demo application will first create a database and then create two workloads in different clusters. The both workloads will use the same DB.
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: multi-cluster-app-with-db
spec:
  components:
    - name: db
      type: alibaba-rds
      properties:
        instance_name: favorite-links
        database_name: links
        account_name: oamtest
        password: U34rfwefwefffaked
        writeConnectionSecretToRef:
          name: db-conn
    - name: favorite-links
      type: webservice
      properties:
        image: oamdev/nodejs-mysql-links:v0.0.1
        port: 4000
      traits:
        - type: service-binding
          properties:
            envMappings:
              DATABASE_HOST:
                secret: db-conn
                key: DB_PUBLIC_HOST
              DATABASE_NAME:
                secret: db-conn
                key: DATABASE_NAME
              DATABASE_USER:
                secret: db-conn
                key: DB_USER
              DATABASE_PASSWORD:
                secret: db-conn
                key: DB_PASSWORD
  policies:
    - name: worker
      type: topology
      properties:
        clusters:
          - cluster-worker
    - name: all-cluster
      type: topology
      properties:
        clusters:
          - cluster-worker
          - local
    - name: links-comp
      type: override
      properties:
        selector:
          - favorite-links
  workflow:
    steps:
      - name: create-rds
        type: apply-component
        properties:
          component: db
      - name: read-secret
        type: read-object
        properties:
          apiVersion: v1
          kind: Secret
          name: db-conn
        outputs:
          - name: db-host
            valueFrom: |
              import "encoding/base64"
              base64.Decode(null, output.value.data.DB_PUBLIC_HOST)
          - name: db-user
            valueFrom: |
              import "encoding/base64"
              base64.Decode(null, output.value.data.DB_USER)
          - name: db-password
            valueFrom: |
              import "encoding/base64"
              base64.Decode(null, output.value.data.DB_PASSWORD)
          - name: db-name
            valueFrom: |
              import "encoding/base64"
              base64.Decode(null, output.value.data.DATABASE_NAME)
      - name: export-secret
        type: export-data
        properties:
          name: db-conn
          namespace: default
          kind: Secret
          topology: worker
        inputs:
          - from: db-host
            parameterKey: data.DB_PUBLIC_HOST
          - from: db-user
            parameterKey: data.DB_USER
          - from: db-password
            parameterKey: data.DB_PASSWORD
          - from: db-name
            parameterKey: data.DATABASE_NAME

      - name: deploy-web
        type: deploy
        properties:
          policies: [ "all-cluster", "links-comp" ]

Discuss About Passing Value
Let's see what we have solved:

Local
Sub-Cluster

Pass Secret
✅
✅

Pass Value
✅

To fill the last grid of table, we have to solve either 2.1 or 2.2.

To solve 2.1 we need to refactor the Configuration rendering logic and unify it to CUE.
To solve 2.2, 2.2.3 is an easier way and need less effort.

I'm going to close this issue as most of the cases have been supported, we'll raise new issues if we found use cases that not meet. https://github.com/kubevela/kubevela/pull/5489


examples/ernie-completion-examples: make this example a separate module

Right now it's in the main module, the only example of this kind.
Align it with the other examples.
This is a two step change, and this is step 1; step 2 will be updating
this example's go.mod to rely on a newer version of langchaingo that
no longer provides this package.
This change has to comment out the example's contents for the lint
to pass -- the issue is that both the main module and this new module
provide the package.
PR Checklist

[x] Name your Pull Request title clearly, concisely, and prefixed with the name of the primarily affected package you changed according to Good commit messages (such as memory: add interfaces for X, Y or util: add whizzbang helpers).
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. Fixes #123).
[x] Describes the source of new concepts.
[x] References existing implementations as appropriate.
[x] Contains test coverage for new functions.
[x] Passes all golangci-lint checks.

Thanks, these should all definitely be separate modules, missed this.

Thanks for the quick turnaround; stay tuned for part 2 :)


Release/1.10

macOS Cookbook - Release 1.10
Changelog

#66 Resolve build failure using correct InSpec syntax
#77 Resolve issue when adding users to groups
#78 Revamped InSpec profile
#79 Install Command Line Tools as part of Xcode setup
#80 Execute block in Xcode resource times out
#81 Allow node attributes for Apple ID credentials

Building failing intermittently due to issues with keep_awake on 10.13.3. Maybe related to the box itself or a race condition in the recipe. All other tests passing, so we're ready to merge.