Image upload hook action to kcfinder.

Hello,
I am looking for a way so I can upload a image using kcfinder from the contenttools script.
Since I am no way a hero with javascript I hope somebody could show me how to do it or push me in the right direction.
Best regards,
Wouter.

Hi @concept-core, I'm afraid I'm not familiar with kcfinder at all but with a bit of luck someone here has and can be able to help. You might have more luck posing this question on StackOverflow though.

Hi Anthony.
Let me rephrase since you are better with js then me.
Is there a way I can double click the img icon or change the whole body of the image modal ?
If I can double click the image I should be able to pass trough the url of the image I want to select.
And if I can change the contents of the modal I should be able to place a iframe of some sort there.
If you want you can take a look at kcfinder integration.
That's done in js, maybe it can help you come up with a solution.
Best regards,
Wouter.

Hi Wouter,
If you want to detect a double-click against images one approach would be to do the following:
ContentEdit.Root.get().bind('mount', function(elm) {
    // We're only interested in images
    if (elm.type() != 'Image') { return; }

    // Add an event listener for double clicks
    elm.domElement.addEventListener('dblclick', function(ev) {
        ...call kcfinder...
    });
});

Let me know if that's of any use?

Heej Anthony,
Could we be able to talk on Skype tomorrow?
I still cannot figure it out and I think my explanation goes nowhere.
If you think that is ok may I send you a direct mail.
Best regards,
Wouter.

Sure I'll be around tomorrow afternoon and evening, my skypename is anthonyblackshaw, if you add me we can try and touch base tm.

OK so here's an example of a base integration which I'm hoping you can test for me and that we can improve on once we have it working in it's simplest form:
// So this little bundle of variables is required because I'm using CoffeeScript
// constructs and this code will potentially not have access to these. Longer
// term we can look to bring this into the core library as an integration option
// and rewrite it in CoffeeScript but (despite appearances) this is probably
// easier for the moment as you're not used to CoffeeScript.
var __slice = [].slice,
__indexOf = [].indexOf || function(item) { for (var i = 0, l = this.length; i < l; i++) { if (i in this && this[i] === item) return i; } return -1; },
__hasProp = {}.hasOwnProperty,
__extends = function(child, parent) { for (var key in parent) { if (__hasProp.call(parent, key)) child[key] = parent[key]; } function ctor() { this.constructor = child; } ctor.prototype = parent.prototype; child.prototype = new ctor(); child.__super__ = parent.prototype; return child; },
__bind = function(fn, me){ return function(){ return fn.apply(me, arguments); }; };

// Define out KCFinder image tool
var KCFImageTool = (function(_super) {
    __extends(KCFImageTool, _super);

    function KCFImageTool() {
      return KCFImageTool.__super__.constructor.apply(this, arguments);
    }

    // Register the tool with ContentTools (in this case we overwrite the
    // default image tool).
    ContentTools.ToolShelf.stow(KCFImageTool, 'image');

    // Set the label and icon we'll use
    KCFImageTool.label = 'Image';
    KCFImageTool.icon = 'image';

    KCFImageTool.canApply = function(element, selection) {
        // So long as there's an image defined we can alwasy insert an image
        return true;
    };

    KCFImageTool.apply = function(element, selection, callback) {

        // Configure the KCFinder application
        window.KCFinder = {
            callBack: function(url) {
                // Once the user has selected an image insert it

                // Create the image element
                var image = new ContentEdit.Image({src: url});

                // Insert the image
                var insertAt = KCFImageTool._insertAt(element);
                insertAt[0].parent().attach(image, insertAt[1]);

                // Set the image as having focus
                image.focus();

                // Call the given tool callback
                return callback(true);

                window.KCFinder = null;
            }
        };

        // Open the KCFinder
        window.open(
            '/demo/kcfinder/browse.php?type=files&dir=files/public',
            'kcfinder_textbox',
            'status=0, toolbar=0, location=0, menubar=0, directories=0, ' +
            'resizable=1, scrollbars=0, width=800, height=600'
        );

    };

    return KCFImageTool;

})(ContentTools.Tool);

For other people who want to use KCFinder this is the code anthony came up with.
Here is the code we used to get it working correctly.
// So this little bundle of variables is required because I'm using CoffeeScript
// constructs and this code will potentially not have access to these. Longer
// term we can look to bring this into the core library as an integration option
// and rewrite it in CoffeeScript but (despite appearances) this is probably
// easier for the moment as you're not used to CoffeeScript.
var __slice = [].slice,
__indexOf = [].indexOf || function(item) { for (var i = 0, l = this.length; i < l; i++) { if (i in this && this[i] === item) return i; } return -1; },
__hasProp = {}.hasOwnProperty,
__extends = function(child, parent) { for (var key in parent) { if (__hasProp.call(parent, key)) child[key] = parent[key]; } function ctor() { this.constructor = child; } ctor.prototype = parent.prototype; child.prototype = new ctor(); child.__super__ = parent.prototype; return child; },
__bind = function(fn, me){ return function(){ return fn.apply(me, arguments); }; };

// Define out KCFinder image tool
var KCFImageTool = (function(_super) {
    __extends(KCFImageTool, _super);

    function KCFImageTool() {
      return KCFImageTool.__super__.constructor.apply(this, arguments);
    }

    // Register the tool with ContentTools (in this case we overwrite the
    // default image tool).
    ContentTools.ToolShelf.stow(KCFImageTool, 'image');

    // Set the label and icon we'll use
    KCFImageTool.label = 'Image';
    KCFImageTool.icon = 'image';

    KCFImageTool.canApply = function(element, selection) {
        // So long as there's an image defined we can alwasy insert an image
        return true;
    };

    KCFImageTool.apply = function(element, selection, callback) {

        // Configure the KCFinder application
        window.KCFinder = {
            callBack: function(url) {
                // Once the user has selected an image insert it

                // Create the image element
                var image = new ContentEdit.Image({src: url, width: 400, height: 400, 'data-ce-max-width': 800});

                // Insert the image
                var insertAt = KCFImageTool._insertAt(element);
                insertAt[0].parent().attach(image, insertAt[1]);

                // Set the image as having focus
                image.focus();

                // Call the given tool callback
                return callback(true);

                window.KCFinder = null;
            }
        };

        // Open the KCFinder
        window.open(
            '/path-to-kcfinder/browse.php?type=images&dir=images/public',
            'kcfinder_textbox',
            'status=0, toolbar=0, location=0, menubar=0, directories=0, ' +
            'resizable=1, scrollbars=0, width=800, height=600'
        );

    };

    return KCFImageTool;

})(ContentTools.Tool);


Link to the discussion board.

Description

Replace the signac-support email address and slack link with a link to the signac discussion board.
Checklist:

[x] I am familiar with the Contributing Guidelines.
[x] I agree with the terms of the Contributor Agreement.
[x] The changes introduced by this pull request are covered by existing or newly introduced tests.
[ ] The package documentation and framework documentation in signac-docs are up to date with these changes.
[ ] I have updated the changelog and added any related issue and pull request numbers for future reference.

Review the updated page here: https://signac--225.org.readthedocs.build/projects/dashboard/en/225/support.html

@joaander @cbkerr Hi, is there a policy change around Slack? Are you hoping to retire the Slack workspace?

@joaander @cbkerr Hi, is there a policy change around Slack? Are you hoping to retire the Slack workspace?

No, there is no policy change. I do not have permissions to control the Slack workspace.


Rename the AWS profile

** Which Category is your question related to? **
Generell CLI
** What AWS Services are you utilizing? **
None yet.
** Provide additional details e.g. code snippets **
I ran amplify configure and created a new user. I mispelled the name of the profile (I saw that while running amplify init. How can I rename the profile and point to the renamed profile in the code generated by amplify init?

@janhesters
The amplify-cli does not provide you the functionality to rename a profile, but you can do it manually by directly editing the two files: ~/.aws/credentials and ~/.aws/config

@UnleashedMind Thank you, it worked!


Add ANSI console

We need to add an ANSI implementation of IConsole to properly display colors when running dotnet cake.

maybe create an adapter for the Microsoft.Extensions.Logging ILogger interface, this way we will will be able to use many existing loggers

@Meir017 IConsole is not a logger.
I prefer to keep dependencies to a minimum at the moment until things are stabilizing. Thanks for the suggestion though! 👍

could this not be implemented as an addin or module package ?

@clmcgrath yes this could be an assembly or in your build "app", register the type you want to replace.
   public void Configure(ICakeServices services)
    {
        services.RegisterInstance<IConsole>(new TestConsole());
        services.UseContext<Context>();
        services.UseLifetime<Lifetime>();
        services.UseWorkingDirectory("..");
    }

A simple console "proxy" example could look like this
    public class TestConsole : IConsole
    {

        public TestConsole()
        {
        }

        public ConsoleColor ForegroundColor
        {
            get => Console.ForegroundColor;
            set => Console.ForegroundColor = value;
        }

        public ConsoleColor BackgroundColor
        {
            get => Console.BackgroundColor;
            set => Console.BackgroundColor = value;
        }

        public void Write(string format, params object[] arg)
            => Console.Write(format, arg);

        public void WriteError(string format, params object[] arg)
            => Console.Error.Write(format, arg);

        public void WriteErrorLine(string format, params object[] arg)
            => Console.Error.WriteLine(format, arg);

        public void WriteLine(string format, params object[] arg)
            => Console.WriteLine(format, arg);

        public void ResetColor()
            => Console.ResetColor();
    }

To be able to use raw ansi codes you would need to use something like
Console.OpenStandardOutput();
var con = new StreamWriter(stdout, Encoding.UTF8);
Console.SetOut(con);

Console.WriteLine("\x1b[36mTEST\x1b[0m");

@devlead said...
Cake 0.38.0 added support for ANSI console, but it's internal in Cake.Core so not avail to frosting default console.


About entity name

Nice work, thanks for sharing the code.
By the way, I wonder where can I find the names of all entities in the dataset?
Currently, I can only get the entity indices w/o semantic meanings.
Thanks

Thanks for your interest in our work.  To get semantic meanings of entities, you can

Read entity ids from id2ent.pkl.
Follow this repo to get textual information of entities based on their ids.

Hope it helps.

Thanks for your interest in our work.  To get semantic meanings of entities, you can

Read entity ids from id2ent.pkl.

Follow this repo to get textual information of entities based on their ids.

Hope it helps.

Thx! That's really helpful~


HTML widget should have maxLines option

Need maxLines in HTML widget, and overflow should be ellipsis, also the text color, font size and font weight.

@hemish11 please treat this as high priority as a customer needs it

@kmahmood74 @vusters @snehmehta Hows this EDL looks like:
View:
  styles:
    scrollableView: true
  header:
    title: Home
  body:
    Column:
      children:
        - Html:
            cssStyles: # List of styles similar to CSS
              - style:
                  selector: "#Hello" # or ".Hello" or "div"
                  properties:
                    # All the CSS properties, it will be entered as key value pair just as in CSS
                    color: red
                    borderWidth: 10 # The naming can be of camelCase. Code would convert the camelCase to param-case
              - style:
                  selector: "#tag2"
                  properties:
                    color: blue
                    borderRadius: 10
            styles:
              borderRadius: 20
              borderColor: red
              borderWidth: 2
            text: |
              <div id="hello">
              Until recently, the prevailing view assumed lorem ipsum was born as a nonsense text. “It's not Latin, though it looks like it, and it actually says nothing,” Before & After magazine answered a curious reader, “Its ‘words’ loosely approximate the frequency with which letters occur in English, which is why at a glance it looks pretty real.”

              As Cicero would put it, “Um, not so fast.”

              The placeholder text, beginning with the line “Lorem ipsum dolor sit amet, consectetur adipiscing elit”, looks like Latin because in its youth, centuries ago, it was Latin.

              Richard McClintock, a Latin scholar from Hampden-Sydney College, is credited with discovering the source behind the ubiquitous filler text. In seeing a sample of lorem ipsum, his interest was piqued by consectetur—a genuine, albeit rare, Latin word. Consulting a Latin dictionary led McClintock to a passage from De Finibus Bonorum et Malorum (“On the Extremes of Good and Evil”), a first-century B.C. text from the Roman philosopher Cicero.
              </div>

I thought to include support for both css tags and also for the box wrapper. Also flutter has these tags supported in the styles parameter so will be adding suppport for all of them:

background-color
color
counter-increment
counter-reset
direction
display
font-family
font-feature-settings
font-size
font-style
font-weight
height
letter-spacing
list-style-image
list-style-type
list-style-position
margin
padding
text-align
text-decoration
text-decoration-color
text-decoration-style
text-decoration-thickness
text-shadow
vertical-align
white-space
width
word-spacing
line-height

@hemish11 Reopening this as HTML widget is still missing maxLines, color, fontWeight and overflow

@sharjeelyunus The color property is actually the foreground color, it is per the CSS property, Im actually doing a one-to-one copy of the CSS properties. There was a bug with overflow and I've fixed that one. Also, ensure that all the parameters are being passed as strings.

@hemish11 please add kitchen sink and documentation for this


Dev: Create an empty/sample validation for user to start from

Is your feature request related to a problem? Please describe.
It would be useful to have a command to quickly generate a Lula Validation, with a uuid, provider, domain fields
Describe the solution you'd like

When lula dev gen-validation (or something, possibly including flags for kubernetes domain data / opa and sample rego)
Then validation.yaml is created

Additional context
Just to give users a somewhat shortcut to creating validations, could also be useful for tool-calling AI to create validations
Expected Deliverable
Cmd, Docs

Discussing the opportunity to create a public repository that houses templates across various domain/providers as a way to both accomplish ease-of-start as well as tutorials for users.


Show alert on re-squeak click

Show alert with "Not yet implemented" message.

Related to https://github.com/yzernik/squeaknode/issues/1763

https://github.com/yzernik/squeaknode/pull/1765


KVStore: Track memory usage in Lock CF

What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:

CachePtr is only filled in debug functions when applying prehandled snapshot. We will remove all pre-decode checkings in decoding IO from raft commands.
Make parallel prehandling functinons more readable.
Trace lock CF's memory.

What is changed and how it works?
Check List
Tests

[ ] Unit test
[x] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-all-tests

ComputeServerRunner.multipleQuery

/run-unit-test


gfycat-ripper does not rip URL starting with thumbs.gfycat.com

Ripme version: 1.7.86

Java version: 1.8.0_221

Operating system: Win 10 (10.0.18362.267

Exact URL you were trying to rip when the problem occurred:
As posted on reddit:
https://thumbs.gfycat.com/SilverMixedIberianchiffchaff-size_restricted.gif

Expected Behavior
Expected behavior would be for ripme to download the gif/mp4.
Actual Behavior
It does not download the gif/mp4. There is no mention in the log, not even that it has been skipped.
This is the only sign that something went wrong:

I'd like to contribute to the project. May I be assigned to this issue?

@rtsketo sure


New pk model tests

added tests for 2CXM, 2CUM and Patlak DCE models
made tests with/without artery-capillary delay separate

Please also note changes to the tolerances

Hi @mjt320
thanks for completing this.
Two thoughts:

did we want to add the NLLS fitting for the OGJ contribution next to the LLSQ fitting method?
I would suggest we first merge demo with the develop branch and afterwards merge this one with develop.

did we want to add the NLLS fitting for the OGJ contribution next to the LLSQ fitting method?
Done. Thanks for reminder!
I would suggest we first merge demo with the develop branch and afterwards merge this one with develop.
Okay

Updates on the notebooks based on the new tests for DCE models:

added notebook for 2CUM and 2CXM
split test results for delayed and non-delayed data
separated the NLLS and LLSQ results for the contribution by OGJ_OsloU_Norway


screen settings in the discord app

the settings in discord i did when i got better discord i was just messing around and i enabled something that i cant now un-enable if i uninstall better discord it is still like that and now i cant edit it like i cant go to where i can edit my name or log out i did something in core

ctrl+comma


Add  tags in loop

Hey, there is a way to make this in one loop? (loop over $i18n.locales)

close in-activity


Remove some redundant code

i am not sure about this one, so it needs a proper review.

give v4 is beta, and there is unlikely to be another release of 3, should i change removed in version 4 to be removed in version 5?


"promtool update" is missing

What did you do? We did a dist-upgrade of our Debian machine, which involves migrating to Prometheus 2.0. We are getting obscure error messages that, I think, are about our old rules not being in the new format. According to the latest migration docs, we can run promtool update to convert our rules.
What did you expect to see? promtool update should do what it says it does in the latest documentation.
What did you see instead? Under which circumstances?
$ sudo promtool update rules summed_traffic.rules
promtool: error: expected command but got "update", try --help

Environment

System information: Linux 4.19.0-8-amd64 x86_64

Prometheus version:

prometheus, version 2.7.1+ds (branch: debian/sid, revision: 2.7.1+ds-3+b11)
  build user<EMAIL_ADDRESS>  build date:       20190608-09:54:04
  go version:       go1.11.6

Thanks for the report.
promtool update has been removed as part of https://github.com/prometheus/prometheus/pull/3839. Prometheus 2.5.0 seems to be the last release, which still contained the subcommand -- the 2.6.0 release notes mention the removal.
I agree that the docs are confusing. Apparently it still makes sense to keep a notice regarding rule conversion. I'll open a PR to extend the docs a bit.
In your case, I suggest getting Prometheus 2.5.0 and using promtool from there to convert your rules. I don't think there were any incompatible changes afterwards, so this should work flawlessly. Also, you don't need to install anything.
If Debian did not provide an intermediate version between 1.x and 2.7, then you might want to take this issue up with the maintainers of the Debian package to provide extended update instructions.

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

If Debian did not provide an intermediate version between 1.x and 2.7

Nope, oldstable is on 1.5 and stable is on 2.7.
Looks like Debian users will have to convert their rules manually then, that's a bummer. :/  Would have been good to keep that conversion tool around a bit longer...
Oh well. Thanks for the quick response, anyway!

Looks like Debian users will have to convert their rules manually then, that's a bummer. :/ Would have been good to keep that conversion tool around a bit longer...

You can still download the tar ball and just use the contained promtool binary. No need to install anything, so there is no risk of conflicts with the packaged version.


adding Hungarian algorithm option to type III pKa analysis

@bas-rustenburg has implemented hungarian algorithm for more stringent matching of experimental and predicted pKas.
Currently type III pKa analysis can be done through two types of matching:

closest: predicted pKas are mapped to closest experimental pKa (minimum absolute error).
hungarian: finds the optimum global match between experimental and predicted set of pKas that minimizes linear sum of squared errors of pairwise matches.

@bas-rustenburg Could you check my description of Hungarian algorithm in the README file of the analysis section?
https://github.com/MobleyLab/SAMPL6/blob/pKa_typeIII_analysis3_hungarian/physical_properties/pKa/analysis/analysis_of_typeIII_predictions/README.md


nixos-build-vms: pass --option to nix-build

Motivation for this change
Also simplified the argument parsing to write all currently supported
CLI options into a bash array and pass this to nix-build.
Also documented --option usage in the corresponding manpage.
Things done

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

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

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

Ping @svanderburg as you're the original author. It would be awesome if you could review this :)

@danbst is there anything that keeps us from merging? :)

@Ma27 I waited for some other eyes to look through this. But if you insist...


Online Diagnostics Module

Purpose

Modularize the diagnostics utility.
To-do

Tasks:

[x] move functions to src
[x] allow instantaneous save
[x] add tests
[x] add docs
[x] update Utlilities
[x] wrap into module after testing
[x] update TimeManager with with trigger_callback (for better tracking of callback types) and Monthly()

Note

here we still use ClimaComms 0.3.2, to enable other PRs to go through and avoid dependency problems with ClimaCore (https://buildkite.com/clima/climacoupler-ci/builds/705#_). ClimaComms will be updated to 0.3.4 in #207

Review checklist

[x] I have read and checked the items on the review checklist.

bors r+


[feature]Add COSIGN_REPOSITORY input for the generator_container_slsa3 workflow

Is your feature request related to a problem? Please describe.
Cosign allows publishing attestations and provenance to a repository other than the image repository using the environment variable COSIGN_REPOSITORY.

This will be helpful in scenarios where a single digest/container image is tagged with multiple repositories and would help publish provenance to an external repository to avoid pollution in all image repositories for the same digest.
Reduces migration effort of tags when moving signatures / provenance attestations for multiple images with same digest
Helps to provide a single point of repository to external customers during verification of multiple images of same digest

Describe the solution you'd like
COSIGN_REPOSITORY  must be allowed as an input and set as env variable for cosign command
When set, use this repository to publish provenance instead of image repository.
When unset/empty, publish provenances as per the parsed image repository (default cosign behavior)
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Thanks. I think we'll need to also have an option in the verifier tool https://github.com/slsa-framework/slsa-verifier, correct?

Docs seem to be here: https://docs.sigstore.dev/system_config/registry_support/#specifying-registry
I don't see any info about authentication in the docs.

@saisatishkarra  I think we can add the necessary options here and then add them to the verifier later. I think we just need to make sure we get the implementation right. See our comments on the PR.

Yes, please add the necessary options in the PR you already opened. We can help you for slsa-verifier after that. I think the main question we have on the PR is for authentication to the separate registry.

@laurentsimon I have added the Authentication to a separate provenance registry if specified to the existing PR. Please review and help guide the changes needed for the slsa-verifier (client)

@laurentsimon I am also looking forward to a direction to add an explicit option to the verifier and repo/code details to get started. Can you also clarify if the verifier can work with the COSIGN_REPOSITORY env variable without the explicit CLI option?

Completed in https://github.com/slsa-framework/slsa-github-generator/pull/2962


Aquarius / Let the Sunshine In (The Flesh Failures) [Remastered] by The 5th Dimension unsupported.

Check if issue with swaglyrics or whether song lyrics unavailable on Genius.

stripper -> The-5th-Dimension-Aquarius-/-Let-the-Sunshine-In--[Remastered]

done


fix: reviews on exchange, amm, and liquidamm modules

Description
[x] - Reviews on exchange, amm, and liquidamm modules

closes: #XXXX
Tasks

[ ]

References

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Appropriate labels applied
[ ] Targeted PR against correct branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Necessary changes are cherry-picked in other PR. So, this draft PR is closed.


Update Readme.md

Enhanced Formatting and Structure: The text was reformatted for better readability, with clear sections and headings (e.g., Project Overview, Contribution Guidelines, Installation) to organize information effectively.
Engaging Language and Emojis: The use of engaging language and emojis (e.g., 🔥, 🚀, 💬, 📝) was introduced to make the content more inviting and appealing to potential contributors, encouraging community involvement.

Just adding emojis and changing the text can not be accepted under Hacktoberfest as it will violate the rules


Use https://github.com/magicaljellybeans/mkdocs_schema_reader ?

This is nearly perfect, except for the part where it's not very readable/usable 😅

not bad though

Just a pip3 install mkdocs-schema-reader and adding
plugins:
  - search
  - schema_reader:
      include:
        - "../packwiz-spec/schemas"

to `mkdocs-base.yaml

I've found a better solution, you can see it in #3 - https://github.com/grafana/json-schema-docs/


Problems uploading file with square brackets on name

Hi,
I am having problems uploading file whose names contain square brackets. Is this a real limitation? Any solution for this?
Cheers,
Rafael

I have found out that the problem is when the name of the source file has brackets. So, if I am willing to upload a local file called ./xpto[1].doc, it is possible to upload only if, before doing it, I rename the file to remove the square brackets.
I doesn't work like this:
$ ./onedrive-upload -f "my/path/xpto[1].doc" "./xpto[1].doc"
An error has occurred while uploading './xpto[1].doc' (Code: )

It works like this:
$ cp -a "./xpto[1].doc" "/tmp/xpto"
$ ./onedrive-upload -f "my/path/xpto[1].doc" -r "xpto[1].doc" "/tmp/xpto"
Successfully uploaded '/tmp/xpto'
$ rm "/tmp/xpto"


TextField widget does not show toolbar on web.

Flutter Web:
TextField widget does not show toolbar on web.
No web support?
I need to customize the toolbar for the text editor.
class TestEditableText extends StatefulWidget {
  @override
  _TestEditableTextState createState() => _TestEditableTextState();
}

class _TestEditableTextState extends State<TestEditableText> {
  var _textController = TextEditingController();

  @override
  void dispose() {
    // TODO: implement dispose
    _textController.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Container(
        width: 600,
        height: 200,
        padding: EdgeInsets.all(8.0),
        decoration: BoxDecoration(
            border: Border.all(
          color: Colors.black87,
          width: 1.0,
        )),
        child: TextField(
          // by default the value is true
          enableInteractiveSelection: true,
          showCursor: true,
          selectionControls:
              cupertinoTextSelectionControls,
          toolbarOptions:
              const ToolbarOptions(copy: true, cut: true, selectAll: true),
          controller: _textController,
          focusNode: FocusNode(),
          autofocus: true,
          keyboardType: TextInputType.multiline,
          maxLines: null,
          minLines: null,
          textAlign: TextAlign.start,
          decoration: InputDecoration(
            border: InputBorder.none,
            isDense: true,
          ),
        ));
  }
}

Hi @Patrick386, thanks for filing the issue. Please provide the output of flutter doctor -v.
Also, is this issue with mobile web or an issue with desktop web?

I am developing a flutter web app.
Flutter doctor -v
[✓] Flutter (Channel stable, 2.10.4, on macOS 12.3 21E230 darwin-arm, locale ko-KR)
    • Flutter version 2.10.4 at /Users/patrick386/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision c860cba910 (3 days ago), 2022-03-25 00:23:12 -0500
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/patrick386/Library/Android/sdk
    • Platform android-32, build-tools 32.1.0-rc1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
    • All Android licenses accepted.
                                                                                [✓] Xcode - develop for iOS and macOS (Xcode 13.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.3 21E230 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 99.0.4844.84

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Hi @Patrick386, it looks like this is working as intended. Kindly see https://api.flutter.dev/flutter/widgets/EditableTextState/showToolbar.html


Remove old connector start up syncer

Purpose

Remove the old connector startup synchronization mechanism and synchronize it in a manner suited to the new connector design.

Closing this since this is no longer valid


proposal: go/build: vendor directories are ignored when outside of $GOPATH

What version of Go are you using (go version)?
1.6
What operating system and processor architecture are you using (go env)?
ubuntu 16.04 x86_64
What did you do?
I want to build a go project using gitlab-ci. The project gets clone on the build machine in /build/project, which is not inside the go path. The build fails due to import errors.
I reproduced this manually: moving a project outside the GOPATH leads to ignoring the vendor folder.
What did you expect to see?
go searching for imports in the vendor directory
What did you see instead?
The vendor directory is ignored and go only searches in GOROOT and GOPATH

The go tool is based on GOPATH.  If you don't want to use GOPATH, it's hard to use the go tool.
Note that GOPATH can have multiple entries; see go help gopath.
I'm going to close this; we're not going to be adding support for things like the vendor directory outside of the existing GOPATH support.

Sorry, but this doesn't make sense to me. The vendoring feature is supposed to solve the problem of dependency management. I got all my dependencies except the go standard library as submodules of my project. Why am I forced to put this to a specific location in my filesystems? My GOPATH is set and the go tool searches for modules in there. When a project is located outside the GOPATH/src i would expect the go tool to search the vendor folder first and then the GOPATH for modules.

The design of the "vendor" mechanism is what you should expect: https://golang.org/s/go15vendor
Any deviations from that document should be filed as a bug, but this is not one.
Let's move this to the mailing list. See https://golang.org/wiki/Questions for links.

Honestly I find it odd too. I don't get why the "go way" is so phobic to freely located project directories. This has been one of the big three pains-in-my-ass when working with the language.

Since the linked specification doesn't state anywhere that the GOPATH is required, making the go tool handle this case, for instance with an option to specify the package path of the current working directory, is not going to be bug. My understanding is that this issue is then a feature request, and thus doesn't deserve to be closed because it's not a bug.
In fact, the linked specification states «This proposal allows the Go community to move from builds that require custom GOPATH configuration beforehand to builds that just work», and one concerned by this feature request can interpret this failure as a deviation from this specification, since any build made where no GOPATH exists will require a custom GOPATH as a consequence.

Here's what works for me in GitLab-CI (building the required custom GOPATH to allow the use of vendoring):
build:
    script:
        - mypkg=x/y/z
        - rm -fr workspace
        - mkdir -p workspace/src/$(dirname $mypkg)
        - ln -s $PWD workspace/src/$mypkg
        - GOPATH=$PWD/workspace go build $mypkg/cmd/my-cmd

The design of the "vendor" mechanism is what you should expect: https://golang.org/s/go15vendor
Any deviations from that document should be filed as a bug, but this is not one.

This issue, as specified, is describing a deviation from that document. It simply says that, when compiling code located in "d/", the go command will look for imports in "d/vendor/$path". It makes no mention of GOPATH except in an example.
I'm going to reopen this issue to look at for Go 1.8. I think fixing this bug could be a key part of solving #12488.

While this is useful, it doesn't solve the problem for projects that have local packages (subdirectories) in addition to vendor packages.
If you just fix this (which makes sense), you're solving the GOPATH issue only for projects made of a single package. If they have sub-package, they would still need to use a GOPATH workspace.

@rasky You could put sub-packages inside vendor/lib/ or something similar. That may be considered misuse of vendor/, but it works and has not the problems of typical relative package paths. But it means that the vendor directory now must be committed to source control (at least the lib subfolder and no external tool may clean vendor).

@rasky You can import packages via "./foo/bar", this seems to work fine with packages under the current directory. Not ideal but does the job

If that already works outside of GOPATH, then it's perfectly fine for me, and I agree it does job. Together with the modification described in this issue, it would allow development without GOPATH (assuming a vendor tool that allows you to download/update dependencies directly within vendor/)

Works fine for me, though I cant use it to access libraries inside the vendor folder odly enough (Gives an error saying the github.com/foo/bar should be in the GoPath)

Has there been any update on this?

#12488 is not going to focus in solving this, so this is still a request per se ;-)

fetch:
	glide install
	@for dep in $(shell cd vendor; find * -type d -maxdepth 2 -mindepth 2); do \
	  echo "Linking $$dep into $$GOPATH"; \
	  rm -rf $$GOPATH/src/$$dep; \
		mkdir -p $$GOPATH/src/$${dep%/*}; \
		ln -fs $(shell pwd)/vendor/$$dep $$GOPATH/src/$$dep; \
	done

build: fetch
	ln -fs $(shell pwd) ${GOPATH}/src/gitlab.com/whois/$(shell basename $(shell pwd))
	go build -v

Because I personally have multiple repos in different languages and I just prefer to not install half of them in a GOPATH. Everytime I jump back into go I'm like "Yes I love programming in go! Now create a new project, add a dependency.... Oh god."

vendor is used only for storing source code (the repositories), not the generated binaries (executables and package objects). But these items are created and managed solely by the "go tools " and could IMHO be considered a cache, or rather transient.
So perhaps it wouldn't be out of the question to have the "go tools" default to using a path such as /tmp for the contents of "bin" and "pkg" when it finds that GOPATH is unset. Choosing some arbitrary directory like /tmp/ or ~/.<application> is a common practice for command line applications to stuff their generated files into.

With this, you have options:

vendor/ but no GOPATH - Your project is fully self-contained in its repo using vendoring.
GOPATH but no vendor/ - Your project shares its dependencies with your other projects.
GOPATH and vendor/ - Dependencies you've vendored with your favorite tool are tracked in your repo, but other dependencies are shared with other projects using the GOPATH.

But GOPATH is completely optional, and left as just a "good idea".
You still get an error if you have no GOPATH and no created vendor/ directory.

So perhaps it wouldn't be out of the question to have the "go tools" default to using a path such as /tmp for the contents of "bin" and "pkg" when it finds that GOPATH is unset.

@dragonfax Note that in 1.8 this is already the case (see #17262); GOPATH is $HOME/go by default, and it can be overriden by setting $GOPATH.

@SamWhited That doesn't really solve the problem of this issue. The tools are still going to require your source to be under GOPATH. Even if its choosing a default GOPATH for you. This is about not requiring a GOPATH at all, let alone forcing the source to be under it.

@dragonfax Agreed, @SamWhited it would be ideal to be able to have a go project in any directory of your computer regardless of where the GOPATH is pointing at, which at the moment is not the case as the go tools only recognise the vendor folder if it lies somewhere bellow GOPATH

Sure, sure; I was just pointing out that a default path (where builds can be put) will already exist in 1.8, not suggesting that it somehow solves the problem. Unless the point of using /tmp was to not polute the GOPATH with things built outside the GOPATH, in which case please disregard.

I didn't know about the default path addition. Thanks. With that, I guess I'm just suggesting loosening the requirement for source to be under GOPATH when its not really needed. i.e all deps under vendor/.

I propose to split the GOPATH env into there envs: GOPATH_SRC, GOPATH_PKG and GOPATH_BIN.
This will make building a project outside of GOPATH easier.
We can just call
GOPATH_SRC=$PWD:$GOPATH_SRC go build

in the project folder to build the project.

@golang101, we already have $GOBIN. And ideally we'd get rid of the "pkg" directory entirely (#4719).

The headache one is the src folder.
To add a path in GOPATH, the path must contain a src sub folder.
This is really not convenient.

@golang101, yes, we understand. That's why this proposal and #17271 are about.

#17271 seems to be in limbo as you yourself proposed shelving it to see the impact of $HOME/go (#17262). But I don't see how #17262 addresses the problem brought up by this ticket.

@eikenb, if by "shelving it" you mean taking things slowly and seeing the impact of one change before doing three things at once, yes.

I have no problem with being methodical and taking time to do things. But the proposed timeline would make it about 2 years before considering a fix for this issue, which seemed a bit long to me.

There are many problems with running outside GOPATH. Among others, there's no caching of built object files, so everything is much slower than it should be (go build, go test, and so on). Vendoring is pretty low on the list of problems.
It may be that GOPATH should be reconsidered but if so it should be done as a whole change, not just one piece at a time, like @bradfitz said above. The solution for now is to use GOPATH.
Duplicate of #17271 if anything.

#17271 is a different but similar issue.  That issue is that people should be able to have an auto-configured GOPATH.  The resolution was proposed to auto resolve GOPATH to ./vendor but instead it would be autoresolved to $HOME/go
This issue is that I have a GOPATH configured, but I want to checkout code outside of that path and the ./vendor directory would override packages in the configured GOPATH.

OK, so not a duplicate of #17271 - updated my comment. The rest of my reply still stands.

what about JIri ?
https://fuchsia.googlesource.com/jiri/

I personally think that the GoLang contributors should give developers at least some amount of freedom. Closing an issue that is requested by so many because you think it'll be slower, for people who are already aware of it and are still requesting it because of how painful the alternatives are is not the best way to go. I have projects in monorepo that use golang for some components.
All other languages work fine but working with Go is a pain because of having to link individual modules into the GOPATH. We get that it'll be slow, but we want it anyway. IMHO a language should empower it's users instead of dictating them.
In my humble opinion, vendor directories should not be ignored outside of GOPATH.

FWIW, I've created a shell script for my project that I now use to compile go stuff. It temporarily links stuff into GOPATH, compiles and then unlinks. I get to keep my stuff out of GOPATH and into the repo and don't have to wait for any new features

@steelbrain I agree!
Would you happen to have a gist of that script?

@steelbrain, the discussion of removing the requirement for $GOPATH is mostly happening in #17271. It is on our agenda to figure out in the next few months.
Please watch that issue but keep in mind https://golang.org/wiki/NoMeToo
I'm going to lock this issue so we can focus conversation in one place.


4-char Request Code has conflicts

so we have almost 10000 requests in airtable(!) and we are starting to get overlap with request code. Request code is the last four characters of airtable's unique Id. @mab253  suggested just upping that to last 6 characters. I'm going to look into how this would affect backend, and if we could do this in-place

maybe add in a randomized number before or after? both? just pulling characters from a longer hash is never going to yield unique identifiers


Dmx512 Rs232 support

1. Tell us something about your changes.
Add DMX512/Rs232 support
2. If this changes affect the .conf file. Please provide the changed section
        "device" :
        {
                "name"       : "DefaultHyperionConfig",
                "type"       : "dmx",
                "output"        : "/dev/ttyUSB0",
                "rate"  : 250000,
                "colorOrder" : "grb"
        },

3. Reference an issue (optional)
Note: For further discussions use our forum: forum.hyperion-project.org

Great I have all hardware to test, but My problem os, how to setup dmx address, rgb to fixture capabilities ...

Excellent! I can't test beyond seeing serial data leave my ftdi adaptor.
It's dumb - no led / slot mapping - Hyperion led 0 is sent in slots 1,2 and 3 (r,g,b), Hyperion led 1 in slots 4,5,6 and so on

I have a Mc Crypt LED-spot. This is DMX spec:
DMX channel | Function
1           | Intensity red 0-100% (0-255)
2           | Intensity green 0-100% (0-255)
3           | Intensity blue 0-100% (0-255)
4           | DMX value
            | 0-7     Light off
            | 8-190   Dimmer
            | 191-200 Sound-to-light control
            | 201-247 Flash effect
            | 248-255 Light on

When color to set is the same color as it is currently set, but ligther/darker, then the use of the dimmer is prefered, because it is faster and more smooth instead of setting the rgb channels individually. It is like the white algorithm for rgbw leds.
Most DMX stuff I know has at least 4 channels R-G-B-Specials (of course this is for colored light).
You should add at least a channel gap and a start/end address.
I mean something like start on dmx address 10, then next channel rgb (10,11,12) the gap channel (e.g. 2 -> 13,14) and then start again with rgb (15,16,17) .... until end address is arrived.
Perhaps instead of end address a "fixtureCount" (= how much led spots you have) is better.
setting an off value can be a nice thing to. this should be notated in "channel:value" e.g. 4:0 in my case. in case of "off" all spots (=> fixture count) should set to off. example for 4 spots: send to channel 4,8,12,16 the value 0. (when start address is 1)
In the long run, better fixture config would be the best. (but some kind of complex) hey and then hyperion can go to stage :-)
In future I'm pretty sure we will have music visualization, imagine using that with dmx fixtures for your party. .... endless thoughts whats possible ...

I'll ate the start address and the increment.
The e1.11 DMX512 spec makes no statement about how the 512 bytes are interpreted - they are just 512 "dimmer" channels that may or may not have specific significance.
I think we'll need a big case statement to support various "DMX-light type"

Thx. This schould be enough to drive some fixtures.
For serious dmx support we should read fixture specs from qlc:
https://github.com/mcallegari/qlcplus/blob/master/resources/fixtures/
There is a neat editor to create this files.
In config there should be an array of fixture names that correspond to name of spec. The array idx of fixture correspond to led id.
Ok enough with ideas :-)
Have a nice day

I've added support for yours!
Well, I would have if it didn't segfault

Segfault fixed

I'm guessing this is yours :
http://www.conrad.com/ce/en/product/591490
I'd love to see if my code works in real life !

it basicly works, but timing is not accurate enough and the refresh rate is to low. In general we should put the leddevice in an own thread, so device won't disturb the main thread and vice versa.
With qlc I get it working failry ok. Problem is, that the pc has to generate a timing correct signal and this is mostly not acurate. (same thing with driving ws2812 on raspi with normal gpio)
Making a dmx device with usb rs232 + rs485 converter is known to make problems. Better solution is that a mcu makes the dmx signal and you transfer the light data to the mcu.
I build a adalight2dmx sketch, but currently it is also not working well enough (but not investigated whats the issue)
Nevertheless the device controlled by qlc works much better as our dmx driver. I alredy planed to add more threading to hyperion. I will add for leddevices soon and then we will see how it performs.

thats mine: https://www.conrad.de/de/led-pinspot-dmx-led-pinspot-anzahl-leds-36-x-591241.html

I cheated a bit and used the smoothing to get better output refresh rate. This was ok to maintain a steady clock signal, but sadly not accurate enough to transfer data.

That wa my biggest worry.
the break and make after break is currently done with nanosleep - there could be framing errors here where a picky device ignores the update of the timing is out.
If we move to a separate thread we should look to move the continuous output function to that thread.


Update 'Resource name' fields to meet UX guidelines: Serving Runtimes

Towards RHOAIENG-14746
Description
Updates the create/edit dialog for Model Servers to use the common K8sNameDescriptionField component in order to meet current UX guidelines.
Screen shots
Create

Create editing Resource name

Edit

How Has This Been Tested?

Navigate to a project this model servers and select the Models tab

Select Add model server
Enter the name for the new model server.
View the resource name via the Edit resource name link.
Change the resource name to something invalid (ie. contains a space)
Verify the submit button is disabled
Change the resource name to something valid
Verify the submit button is enabled
Save the profile.
Verify the profile is created with the correct Display name and Resource Name.

Navigate to a project this model servers and select the Models tab

Select the kebab for an existing model server and choose Edit
Update the Name field
Notice the resource name is not editable
Save the model server.
Verify the model server is updated with the correct Display name.

Test Impact
Updated unit tests for new fields
Request review criteria:

[x] The developer has manually tested the changes and verified that the changes work
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)
[x] Included any necessary screenshots or gifs if it was a UI change.
[x] Included tags to the UX team if it was a UI/UX change.

/cc @simrandhaliw

@manosnoam Updated data-testid for the accelerator profile dialog Name field was updated from serving-runtime-name-input to serving-runtime-name

the custom name is not retained and the resource name just matches the model server name.

@jenny-s51 Fixed.

For long server names, the resource name is currently matching the full input, but the guidelines suggest truncating to the first 30 characters.

@jenny-s51 The guidelines say If the resource name has a limit on the number of characters, the limit here is 253 I believe.

For ResourceNameDefinitionTooltip, the tooltip text currently differs a bit from what’s outlined in the guidelines.

@jenny-s51 I have updated the text. See the added screenshot in the PR description


Info cut off

Smaller screen size leads to stats being cut off.

Date navigator isn't shown

see cc2cb01.

iPhone 4s. Do I choose to support this screen size? Reopen and will look into.


bug(CdkVirtualScrollViewport): Using cdkVirtualFor in a template does not find CdkVirtualScrollViewport

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
I want to create a component that does support virtual scrolling but can be turned off.
To do so, I want to use some ng-templates so I do not have to redefine things like headers, item template, etc.
The code for that (minimalistic, without turn on/off virtual scrolling) looks like:
import { Component, Directive, inject, Injector, Input } from '@angular/core';
import { CommonModule } from '@angular/common';
import { bootstrapApplication } from '@angular/platform-browser';
import {
  CdkVirtualScrollViewport,
  ScrollingModule,
} from '@angular/cdk/scrolling';

@Component({
  selector: 'my-test',
  template: `I have a viewport? {{ !!cdkVirtualScrollViewport }}`,
})
export class MyTest {
  cdkVirtualScrollViewport = inject(CdkVirtualScrollViewport);
}

@Directive({
  selector: '[myProvider]',
  exportAs: 'myProvider',
})
export class MyProvider {
  private readonly myInjector = inject(Injector);
  @Input() myProvider!: CdkVirtualScrollViewport;

  get injector(): Injector {
    return Injector.create({
      parent: this.myInjector,
      providers: [
        {
          provide: CdkVirtualScrollViewport,
          useValue: this.myProvider,
        },
      ],
    });
  }
}

@Component({
  selector: 'my-app',
  template: `
    Woop
    <cdk-virtual-scroll-viewport itemSize="50" #scrollViewport style="height: 200px">
      <ng-container *ngTemplateOutlet="gridTemplate; context: { $implicit: virtualFor, scrollViewport: scrollViewport }" />
    </cdk-virtual-scroll-viewport>

    <ng-template #gridTemplate let-template let-scrollViewport="scrollViewport">

Imagine a header here

      <ng-container [myProvider]="scrollViewport" #myProvider="myProvider">
        <ng-container *ngTemplateOutlet="template; injector: myProvider.injector" />
      </ng-container>
    </ng-template>

    <ng-template #virtualFor>
      <my-test />

      <ng-container *cdkVirtualFor="let item of data">
        <ng-container *ngTemplateOutlet="itemTemplate; context: { $implicit: item }" />
      </ng-container>
    </ng-template>

    <ng-template #itemTemplate let-item>

{{ item }}

    </ng-template>
  `,
})
export class AppComponent {
  data = ['hello', 'world'];
}

As you can see, I have

AppComponent: Defines all the templates and the virtual scrolling.
MyProvider: A directive to create a new injector containing the existing CdkVirtualScrollViewport
MyTest: a simple test component to see if injection works as it should

Reproduction
StackBlitz link: https://stackblitz.com/edit/stackblitz-starters-sjp7es?file=src%2Fmain.ts
I've also attached a Zip-File with a working sample, because for whatever reason the StackBlitz does not load the DevServer sometimes, maybe they have a hiccup.
Steps to reproduce:

Either download the example or open the stackblitz link
You will see an error when starting the app, that there is no provider for CdkVirtualScrollViewport
If you comment out the ng-container containing the cdkVirtualFor you will see, that my-test components outputs true, because it has an injector containing a CdkVirtualScrollViewport

Example.zip
Expected Behavior
I would expect it to work and CdkVirtualFor actually sees the CdkVirtualScrollViewport, because it is in the Injector, as my-test component reports.
Actual Behavior
Error pops up with:
[CdkVirtualScrollViewport -> CdkVirtualScrollViewport -> CdkVirtualScrollViewport -> CdkVirtualScrollViewport]:
  NullInjectorError: No provider for CdkVirtualScrollViewport!

Environment
Angular CLI: 16.1.1
Node: 18.16.0
Package Manager: npm 9.5.1
OS: darwin arm64

Angular: 16.1.2
... animations, cdk, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1601.1
@angular-devkit/build-angular   16.1.1
@angular-devkit/core            16.1.1
@angular-devkit/schematics      16.1.1
@angular/cli                    16.1.1
@schematics/angular             16.1.1
rxjs                            7.8.1
typescript                      5.1.3

@ManuelRauber did you find a solution for this problem? still having the same issue

@ManuelRauber did you find a solution for this problem? still having the same issue

Well, I ended up duplicating stuff a bit, unfortunately.

I found good example of how to fix the issue in the template with ng-content here https://github.com/angular/components/issues/15277


Get-DbaSqlBuildReference - gives error if SQL Service is down

Is this:
Just place "x" to indicate selection (e.g. "[x]")

[ ] feature
[x] bug:

Steps to Reproduce
Example:
Get-DbaSqlBuildReference -SqlInstance srv-sql-is-down
Action Results
You cannot call a method on a null-valued expression.
At line:162 char:4
+             $Detected = Resolve-DbaSqlBuild -Build $instance.Version. ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull

You cannot call a method on a null-valued expression.
At line:164 char:4
+             [PSCustomObject]@{
+             ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull

I don't think it's documented .... the parameter is there just to support pipelining..... although we may fix it when a mere string is passed rather than a full blown SMO.


Make the npm package installation idempotent

Installing the 'latest' package triggers a change every time puppet agent runs.  This changes the default to 'present' so it installs the latest at the time of installation, and lets the admin choose to upgrade to subsequent versions at a time of their choosing.
It also fixes the home_dir setting, so a doubled .npm directory isn't created.

@dickp but that means present tag should be present? how the users would be aware of it?

The difference between 'latest' and 'present' is that 'latest' will check for updates every time puppet runs, while 'present' only makes sure the package is installed - and if it isn't it installs the latest at that time, and if it is installs it does nothing.
The problem with 'latest' is that it registers a change every time.

@dickp but that means present tag should be present? how the users would be aware of it?

Instead of
$version = undef,
in the declaration
Variant[Enum['present', 'absent', 'held', 'installed', 'latest'], Pattern[/./]]  $version = 'present',
That way it is explicit as what that field expects and will allow.   And also means the inline if can be removed
so it's just
$npm_ensure = $version

@dickp but that means present tag should be present? how the users would be aware of it?

Instead of $version = undef, in the declaration Variant[Enum['present', 'absent', 'held', 'installed', 'latest'], Pattern[/./]] $version = 'present',
That way it is explicit as what that field expects and will allow. And also means the inline if can be removed so it's just $npm_ensure = $version

btw, the same thing should be done with $ldap_plugin_version, also @param doc should be added for those two variables.


Unsupported OpenType signature

The fonts used to worker loader  work's nicely on dev mode, but when we make quasar build the fonts are not imported.
Getting error Unsupported OpenType signature
DxfViewerWorker.28d49fcb.worker.js:7 Error: Unsupported OpenType signature 404
    at Object.Ha [as parse] (DxfViewerWorker.28d49fcb.worker.js:9:169116)
    at DxfViewerWorker.28d49fcb.worker.js:7:649524
    at Generator.next (<anonymous>)
    at r (DxfViewerWorker.28d49fcb.worker.js:16:21839)
    at o (DxfViewerWorker.28d49fcb.worker.js:16:22042)
(anonymous) @ DxfViewerWorker.28d49fcb.worker.js:7

i don't have any clue in what i'm doing wrong
PS: using quasar.conf.js

After builds the code trying to load fonts from http://localhost:4000/js/fonts/Roboto-LightItalic.2eeb30eb.ttf

Same issue here,
when i run quasar build, the compiler put font in /fonts folder and try to load on /js/fonts, something is wrong when translating url after build. Is it a webpack missing configuration inside a quasar.conf.js?

Probably the build command somehow differs. This example uses vue-cli-service build in its package.json. The result is in this repo: https://github.com/vagran/dxf-viewer-example It has fonts directory on top level.

Some weird things happening with quasar compilations. I fixed the problem by go out of from "import from" to const var like this:
const mainFont = '/fonts/Roboto-LightItalic.ttf'
const aux1Font = '/fonts/NotoSansDisplay-SemiCondensedLightItalic.ttf'
const aux2Font = '/fonts/HanaMinA.ttf'
const aux3Font = '/fonts/NanumGothic-Regular.ttf'

and moving font files from assets/fonts folder to public/fonts.

Should be related to webpack config. See here:
https://chriscourses.com/blog/loading-fonts-webpack
Probably, when building by vue-cli-service these rules already applied by default.
Another way may be specifying file laoder inline: https://webpack.js.org/concepts/loaders/#inline


Parse setting language to DibsLang enum

At the moment the language property in the payment provider doesn't do anything.
This PR parse this to one of the supported languages defined in DibsLang enum.
According to the documentation the default language is Danish if this parameter isn't set, so it think it is fine it just use the default enum value, which is Danish, if it can't parse to string value to a DibsLang value.

Great suggestion 👍


Optional 'No Results Found' behavior

When the query matches no results, the dropdown simply does not appear.
In the case of an application which uses a typeahead for "find or create" behavior, this disables the ability to offer additional selections, e.g. "No results found. Create entry %QUERY?".

+1


Propagate the translated font name to TextContentItem for system fonts.

This allows font data for system fonts to be looked up in PDFObjects. Without this, only text with non-system fonts get a font name that matches the name in PDFObjects (e.g., "g_d0_f1") while text with system fonts get an untranslated name (e.g., "Times").

Please keep in mind that rendering and text-extraction uses different code-paths in PDF documents, as mandated by the specification, hence there's no inherent need for the fonts used in the two modes to match exactly.
Furthermore this patch will cause a lot more font switching in the textLayer thus (potentially) affecting performance, and would also break API-compatibility for something that's existed for (at least) ten years.
All-in-all, I'm sorry to say that this doesn't seem to be a change we want to make here.

Furthermore this patch will cause a lot more font switching in the textLayer thus (potentially) affecting performance,

However, I suppose that the effect of this wouldn't be that severe considering how the caching is currently implemented (essentially using the Font.prototype.fallbackName property): https://github.com/mozilla/pdf.js/blob/eda51d1dcc583120fae8953cb98bf41de6deddf9/src/display/text_layer.js#L130-L135

and would also break API-compatibility for something that's existed for (at least) ten years.

The more problematic part is the API "breakage", since all of this is very old code. @timvandermeij How do you feel about this change?

Hi Jonas, thanks for taking a look at this so quickly, and for the explanations. To provide some additional context, the reason for this change is because it can be useful to look up the original font name, bolding, etc. of extracted text (e.g., for document understanding applications). Right now, this is possible for non-system fonts, but as far as I can tell, it's not feasible to do this for system fonts because of the name mismatch. So even though there's no requirement for the fonts to match between the two modes, I think it would make the API more useful to maintain that correspondence.
Another way to do this would be to store a separate field (e.g., "fontObjectName" or some such) with the TextContentItem (perhaps only when it differs from the fontName, i.e., only for system fonts), and callers can do a lookup via item.fontObjectName || item.fontName. This would make the extraction output a bit larger but maintain backwards compatibility. Thoughts?

To provide some additional context, the reason for this change is because it can be useful to look up the original font name, bolding, etc. of extracted text (e.g., for document understanding applications).

In this case it's pretty clear why a third-party implementation might want to do this; however (in general) please keep in mind additional context usually belongs in the commit message (and not just the PR description/discussion) in order to aid future code archaeology :-)

Another way to do this would be to store a separate field (e.g., "fontObjectName" or some such) with the TextContentItem (perhaps only when it differs from the fontName, i.e., only for system fonts), and callers can do a lookup via item.fontObjectName || item.fontName. This would make the extraction output a bit larger but maintain backwards compatibility. Thoughts?

This sounds like very much like PR #10753, which we really don't want to do because of its overhead.

In this case it's pretty clear why a third-party implementation might want to do this; however (in general) please keep in mind that additional context usually belongs in the commit message (and not just the PR description/discussion) in order to aid future code archaeology :-)

Good to know, I'll definitely keep that in mind for future commits.

This sounds like very much like PR #10753, which we really don't want to do because of its overhead.

That makes sense. If I'm reading correctly, this change would enable the use case that PR #10753, Issue #15651, etc. are interested in, without the memory overhead.
Thanks for the code review as well. I'll wait for Tim to chime in on the general approach - in the meantime, would you prefer that I apply fixes by amending the original commit, or by tacking on another commit and squashing them if and when the PR gets merged?

In terms of the general approach, I'd say that if it's already inconsistent (either in terms of system versus non-systems fonts behaving differently and the useSystemFonts option also adding a difference in behavior) it might actually be better to make it consistent. If we mark this as [api-minor] we at least indicate it's an API change for safety, but I'm not sure if anything would actually break if we do this change or if people even relied on the current behavior if it's inconstent in the first place.

/botio test


It doesn't show video

I forked your code: https://github.com/Soebb/test-flask
And upload a video to the repo as you can see, then i deployed it to doprax.com but the video not appear.
check it: https://whispermase.kfirjgyswf.dopraxrocks.com/
The login password is Soheyb1378

Oh, Sorry. My mistake!
I forgot creating category folder.
Now it works.

Now problem is that the file not upload properly and completely or maybe the problem raise when i want to catch and access to it since the hosted file size is 3kb and incorrect but the correct size is 1mgb.

How are you uploading your videos?
Also are u using docker or manual nginx?

No i don't use.
How i can add nginx manually?

No way to build boehmls/chief-video in a dockerfile ?
I mean using FROM instruction in dockerfile instead of manually do docker build command.


Opencv4.5.0

Hi, I was thinking to use OpenCV 4.5.0 on both pi and jetson, what do you suggest? have you tried it?

Hi, I had to make some adjustments in the Makefile to specify the version of OpenCV.
Now a new error popped when compiling ./compile_darknet.sh
gcc -Iinclude/ -I3rdparty/stb/include -DOPENCV `pkg-config --cflags opencv4` -DGPU -I/usr/local/cuda/include/ -DCUDNN -DCUDNN_HALF -Wall -Wfatal-errors -Wno-unused-result -Wno-unknown-pragmas -fPIC -Ofast -DOPENCV -fopenmp -DGPU -DCUDNN -I/usr/local/cudnn/include -DCUDNN_HALF -fPIC -c ./src/convolutional_layer.c -o obj/convolutional_layer.o
./src/convolutional_layer.c: In function ‘cudnn_convolutional_setup’:
./src/convolutional_layer.c:283:24: error: ‘CUDNN_CONVOLUTION_FWD_PREFER_FASTEST’ undeclared (first use in this function); did you mean ‘CUDNN_CONVOLUTION_BWD_FILTER_ALGO_3’?
     int forward_algo = CUDNN_CONVOLUTION_FWD_PREFER_FASTEST;
                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                        CUDNN_CONVOLUTION_BWD_FILTER_ALGO_3
compilation terminated due to -Wfatal-errors.
Makefile:142: recipe for target 'obj/convolutional_layer.o' failed
make: *** [obj/convolutional_layer.o] Error 1
mv: cannot stat 'libdarknet.so': No such file or directory
Darknet library has been compiled and saved

Hi, yes there is an issue with compiling darknet on Jetson. Can you post the full log so I can take a look? Also, which Jetson and JetPack are you using and what scripts have you run up to this point?

Hi, I am on AGX with Cuda 10.2, after running this darknet I got many errors of compilation due to different reasons like mismatched version of packages (e.g openCV), so I modified the compile_darknet.sh to:
#sudo apt-get update
#mkdir dpd
cd dpd
#git clone http://www.github.com/dataplayer12/darknet.git
cd darknet
make
mv libdarknet.so ../../human_detection/xavier/
cd ../../
#sudo rm -rf dpd
echo "Darknet library has been compiled and saved"

This allowed me to make some changes to files, followed this

Can you do a git checkout xavier before make? I tried to make darknet easy to compile on Jetsons but the darknet codebase keeps changing as do Jetpack versions which frequently break things. So compiling darknet is always a moving target that I as a maintainer must constantly keep up with. I haven't had the time to look at new changes in darknet since this project was published. Your best bet might be to google for something like 'compile darknet on JetPack 4.6' or whatever JetPack you are using. I still dont have the full log from your machine to understand what went wrong.

So first I tested this repo and then this other and they works.
This is the first error that I had at first
g++ -std=c++11 -Iinclude/ -I3rdparty/stb/include -DOPENCV `pkg-config --cflags opencv` -DGPU -I/usr/local/cuda/include/ -DCUDNN -DCUDNN_HALF -Wall -Wfatal-errors -Wno-unused-result -Wno-unknown-pragmas -fPIC -Ofast -DOPENCV -fopenmp -DGPU -DCUDNN -I/usr/local/cudnn/include -DCUDNN_HALF -fPIC -c ./src/image_opencv.cpp -o obj/image_opencv.o
Package opencv was not found in the pkg-config search path.
Perhaps you should add the directory containing `opencv.pc'
to the PKG_CONFIG_PATH environment variable
No package 'opencv' found
./src/image_opencv.cpp:15:10: fatal error: opencv2/core/version.hpp: No such file or directory
 #include <opencv2/core/version.hpp>
          ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:149: recipe for target 'obj/image_opencv.o' failed
make: *** [obj/image_opencv.o] Error 1
mv: cannot stat 'libdarknet.so': No such file or directory
Darknet library has been compiled and saved

Which led me to this and fixed for the most, but then when I run sudo ./compile_darknet.sh this is what I got
chmod +x *.sh
gcc -Iinclude/ -I3rdparty/stb/include -DOPENCV `pkg-config --cflags opencv4` -DGPU -I/usr/local/cuda/include/ -DCUDNN -DCUDNN_HALF -Wall -Wfatal-errors -Wno-unused-result -Wno-unknown-pragmas -fPIC -Ofast -DOPENCV -fopenmp -DGPU -DCUDNN -I/usr/local/cudnn/include -DCUDNN_HALF -fPIC -c ./src/convolutional_layer.c -o obj/convolutional_layer.o
./src/convolutional_layer.c: In function ‘cudnn_convolutional_setup’:
./src/convolutional_layer.c:283:24: error: ‘CUDNN_CONVOLUTION_FWD_PREFER_FASTEST’ undeclared (first use in this function); did you mean ‘CUDNN_CONVOLUTION_BWD_FILTER_ALGO_3’?
     int forward_algo = CUDNN_CONVOLUTION_FWD_PREFER_FASTEST;
                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                        CUDNN_CONVOLUTION_BWD_FILTER_ALGO_3
compilation terminated due to -Wfatal-errors.
Makefile:142: recipe for target 'obj/convolutional_layer.o' failed
make: *** [obj/convolutional_layer.o] Error 1
mv: cannot stat 'libdarknet.so': No such file or directory
Darknet library has been compiled and saved

The ./compile_darknet.sh has a git clone to this path

I suggest updating the script for darknet to which the ./compile_darknet.sh is pointing. I tried with the original repo from AlexeyAB and after some adjustment worked with no problem which definitely needs to update some of the files like Makefile and image_opencv.cpp in order to work with the Xavier and the latest JetPack, OpenCV4, Cuda, the Nccv file location etc.


fix | Trainer Condition

I used the public property of the BattleController, since the getOwner of the pixelEntity doesn't work :(

Hadn't managed to get to this yet. What was the reason for the closure?

It was causing issues with multiplayer, the bt is coming as null :(

Yeah, multiplayer makes it much harder. A lot of the data isn't synced to the client at all, which is why some of the conditions don't work properly.
Appreciate the effort though! If you figure a solution, I'd love to know :)

I was analyzing the classes, and an idea came to me. The rival Pokémon appears right at the trainer's coordinates. I'll try something with that, and if it works, I'll send a PR.


Failed to build kubeflow v1.1.0/v1.2.0 due to kustomization.yaml file not found

/kind bug
What steps did you take and what happened:
I am trying to install kubeflow on minikube single node using official guide, so for first I failed in both v1.1.0 and v1.2.0 so tried with older v0.7.0 which got successfully deployed on my minikube cluster so I tried again to deploy the newer versions. First of all I am not able to connect with CONFIG_URI and the manifest uri present in the CONFIG_URI .yaml file which i faced in v0.7 as well for that I did wget both the yaml file and the repo tar.gz file and changed the uri's manually which worked for me in v0.7.0 so I did same thing for v1.1.0 as well, so now the error that I am getting is pointing me to believe that there is something wrong with .yaml files that setup is trying to lookup into, the error log that I am getting for following uri's are:
CONFIG_URI - "https://raw.githubusercontent.com/kubeflow/manifests/v1.2-branch/kfdef/kfctl_k8s_istio.v1.2.0.yaml"
repo uri - "https://github.com/kubeflow/manifests/archive/v1.2.0.tar.gz"
Log for kfctl build -V -f ${CONFIG_URI} where CONFIG_URI is pointing to local directory where yaml file is downloaded
INFO[0000] No name specified in KfDef.Metadata.Name; defaulting to my-kubeflow_n based on location of config file: /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kfctl_k8s_istio.v1.2.0.yaml.  filename="coordinator/coordinator.go:202"
INFO[0000]

Notice anonymous usage reporting enabled using spartakus
To disable it
If you have already deployed it run the following commands:
cd $(pwd)
kubectl -n ${K8S_NAMESPACE} delete deploy -l app=spartakus
For more info: https://www.kubeflow.org/docs/other-guides/usage-reporting/

filename="coordinator/coordinator.go:120"
INFO[0000] Creating directory /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/.cache  filename="kfconfig/types.go:445"
INFO[0000] Fetching file:/scratch/users/ofsaa/kubeflow/v1.2/v1.2.0.tar.gz to /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/.cache/manifests  filename="kfconfig/types.go:493"
INFO[0000] probing file path: /scratch/users/ofsaa/kubeflow/v1.2/v1.2.0.tar.gz  filename="kfconfig/types.go:543"
INFO[0000] updating localPath to /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/.cache/manifests/manifests-1.2.0  filename="kfconfig/types.go:552"
INFO[0000] Fetch succeeded; LocalPath /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/.cache/manifests/manifests-1.2.0  filename="kfconfig/types.go:561"
INFO[0000] Processing application: namespaces            filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/namespaces/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/namespaces/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: application           filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/application/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/application/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: istio-stack           filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/istio-stack/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/istio-stack/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: cluster-local-gateway  filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cluster-local-gateway/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cluster-local-gateway/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: istio                 filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/istio/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/istio/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: cert-manager-crds     filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cert-manager-crds/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cert-manager-crds/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: cert-manager-kube-system-resources  filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cert-manager-kube-system-resources/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cert-manager-kube-system-resources/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: cert-manager          filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cert-manager/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cert-manager/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: add-anonymous-user-filter  filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/add-anonymous-user-filter/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/add-anonymous-user-filter/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: metacontroller        filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/metacontroller/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/metacontroller/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: bootstrap             filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/bootstrap/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/bootstrap/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: spark-operator        filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/spark-operator/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/spark-operator/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: kubeflow-apps         filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/kubeflow-apps/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/kubeflow-apps/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: knative               filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/knative/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/knative/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: kfserving             filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/kfserving/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/kfserving/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
Error: failed to build kfApp from URI /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kfctl_k8s_istio.v1.2.0.yaml: couldn't generate KfApp:  (kubeflow.error): Code 500 with message: kfApp Generate failed for kustomize: kustomize generate failed Error:  (kubeflow.error): Code 500 with message: couldn't generate kustomization file for component kfserving
Usage:
kfctl build [flags]
Flags:
-f, --file string   Static config file to use. Can be either a local path:
export CONFIG=./kfctl_gcp_iap.yaml
or a URL:
export CONFIG=https://raw.githubusercontent.com/kubeflow/manifests/v1.0-branch/kfdef/kfctl_gcp_iap.v1.0.0.yaml
export CONFIG=https://raw.githubusercontent.com/kubeflow/manifests/v1.0-branch/kfdef/kfctl_istio_dex.v1.0.0.yaml
export CONFIG=https://raw.githubusercontent.com/kubeflow/manifests/v1.0-branch/kfdef/kfctl_aws.v1.0.0.yaml
export CONFIG=https://raw.githubusercontent.com/kubeflow/manifests/v1.0-branch/kfdef/kfctl_k8s_istio.v1.0.0.yaml
kfctl build -V --file=${CONFIG}
-h, --help          help for build
-V, --verbose       verbose output default is false
failed to build kfApp from URI /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kfctl_k8s_istio.v1.2.0.yaml: couldn't generate KfApp:  (kubeflow.error): Code 500 with message: kfApp Generate failed for kustomize: kustomize generate failed Error:  (kubeflow.error): Code 500 with message: couldn't generate kustomization file for component kfserving

Log for 'kfctl apply -V -f ${CONFIG_URI}'
INFO[0000] No name specified in KfDef.Metadata.Name; defaulting to my-kubeflow_n based on location of config file: /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kfctl_k8s_istio.v1.2.0.yaml.  filename="coordinator/coordinator.go:202"
INFO[0000]

Notice anonymous usage reporting enabled using spartakus
To disable it
If you have already deployed it run the following commands:
cd $(pwd)
kubectl -n ${K8S_NAMESPACE} delete deploy -l app=spartakus
For more info: https://www.kubeflow.org/docs/other-guides/usage-reporting/

filename="coordinator/coordinator.go:120"
INFO[0000] Creating directory /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/.cache  filename="kfconfig/types.go:445"
INFO[0000] Fetching file:/scratch/users/ofsaa/kubeflow/v1.2/v1.2.0.tar.gz to /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/.cache/manifests  filename="kfconfig/types.go:493"
INFO[0000] probing file path: /scratch/users/ofsaa/kubeflow/v1.2/v1.2.0.tar.gz  filename="kfconfig/types.go:543"
INFO[0000] updating localPath to /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/.cache/manifests/manifests-1.2.0  filename="kfconfig/types.go:552"
INFO[0000] Fetch succeeded; LocalPath /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/.cache/manifests/manifests-1.2.0  filename="kfconfig/types.go:561"
INFO[0000] Processing application: namespaces            filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/namespaces/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/namespaces/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: application           filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/application/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/application/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: istio-stack           filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/istio-stack/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/istio-stack/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: cluster-local-gateway  filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cluster-local-gateway/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cluster-local-gateway/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: istio                 filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/istio/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/istio/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: cert-manager-crds     filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cert-manager-crds/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cert-manager-crds/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: cert-manager-kube-system-resources  filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cert-manager-kube-system-resources/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cert-manager-kube-system-resources/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: cert-manager          filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cert-manager/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/cert-manager/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: add-anonymous-user-filter  filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/add-anonymous-user-filter/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/add-anonymous-user-filter/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: metacontroller        filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/metacontroller/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/metacontroller/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: bootstrap             filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/bootstrap/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/bootstrap/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: spark-operator        filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/spark-operator/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/spark-operator/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: kubeflow-apps         filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/kubeflow-apps/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/kubeflow-apps/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: knative               filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/knative/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/knative/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
INFO[0000] Processing application: kfserving             filename="kustomize/kustomize.go:408"
WARN[0000] Cannot get kustomization from /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/kfserving/base: error open /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kustomize/kfserving/base/kustomization.yaml: no such file or directory  filename="kustomize/kustomize.go:524"
Error: failed to build kfApp from URI /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kfctl_k8s_istio.v1.2.0.yaml: couldn't generate KfApp:  (kubeflow.error): Code 500 with message: kfApp Generate failed for kustomize: kustomize generate failed Error:  (kubeflow.error): Code 500 with message: couldn't generate kustomization file for component kfserving
Usage:
kfctl apply -f ${CONFIG} [flags]
Flags:
-f, --file string   Static config file to use. Can be either a local path:
export CONFIG=./kfctl_gcp_iap.yaml
or a URL:
export CONFIG=https://raw.githubusercontent.com/kubeflow/manifests/v1.0-branch/kfdef/kfctl_gcp_iap.v1.0.0.yaml
export CONFIG=https://raw.githubusercontent.com/kubeflow/manifests/v1.0-branch/kfdef/kfctl_istio_dex.v1.0.0.yaml
export CONFIG=https://raw.githubusercontent.com/kubeflow/manifests/v1.0-branch/kfdef/kfctl_aws.v1.0.0.yaml
export CONFIG=https://raw.githubusercontent.com/kubeflow/manifests/v1.0-branch/kfdef/kfctl_k8s_istio.v1.0.0.yaml
kfctl apply -V --file=${CONFIG}
-h, --help          help for apply
-V, --verbose       verbose output default is false
failed to build kfApp from URI /scratch/users/ofsaa/kubeflow/v1.2/my-kubeflow_n/kfctl_k8s_istio.v1.2.0.yaml: couldn't generate KfApp:  (kubeflow.error): Code 500 with message: kfApp Generate failed for kustomize: kustomize generate failed Error:  (kubeflow.error): Code 500 with message: couldn't generate kustomization file for component kfserving
What did you expect to happen:
Successfully using kfctl apply to deploy the kubeflow on minikube k8s cluster with working pods and services
Anything else you would like to add:
Tried the same thing with both v1.1.0 and v.1.2.0 and getting the same error of files and directories not present, I was able to deploy v0.7.0 successfully using same approach of manually setting the uri files which is really not a big change from official guide- https://www.kubeflow.org/docs/started/workstation/minikube-linux/
Environment:

Istio Version: Deploying through setup only
Knative Version: Deploying through setup (default)
KFServing Version: Deploying through setup (default)
Kubeflow version: v1.1.0/v1.2.0
Kfdef: k8s_istio
Minikube version: v1.15.1
Kubernetes version: (use kubectl version): server version- 1.14.0 and client version- 1.15.0
(compatible with v1.1)
OS (e.g. from /etc/os-release): Oracle Linux Server 7.6

@chinmay22897 Can you help move this issue to kubeflow/manifests ?

@chinmay22897 Can you help move this issue to kubeflow/manifests ?

Done.


A new label to close an issue if there are 1 month no response after the label marked.

The label could be named close_if_no_feedback or we can reuse need_feedback.
When an issue has a label need_feedback but there is no any comment one month after the label added. then close it automatically.

We need a condition here. Would the following condition work:
Close all issues that have status/needs-feedback AND a month has passed since the last comment from the author AND the last comment is not by the author

Close all issues that have status/needs-feedback AND a month has passed since the last comment from the author AND the last comment is not by the author

How about Close all issues that have status/needs-feedback AND a month has passed since no new comment from anyone after the label created?

I will try to implement it

I created #108 for this


Storing MP3 files in littlefs

Hi,
I've previously worked with littlefs mounted in a NOR Flash and it worked as expected. I'm currently doing some research about replacing an SD Card (used in a prototype) with a memory "chip".
The first candidate was an eMMC (and also using fatfs) but I'm also trying to use something smaller, like a NAND Flash (and use littlefs).
The application stores MP3 files in the SD Card for playback, it would be possible to store those MP3 files in littlefs? I was thinking on writing a "fs converter", reading the files from the SD Card and writing them into littlefs files. They are 14 files from 50KB up to 180KB.
Do you think littlefs is a good tool for the job?

So, the main concern is littlefs's performance issues. littlefs does not handle very large block sizes well, and it doesn't handle a large number of blocks well when full. These both become problems with NAND flash.
That being said, littlefs's performance issues happen to only be when writing to the filesystem. It's actually quite fast when reading, which sounds like it would be the important part for MP3 files?
It may still be problematically slow when moving files from the SD Card to littlefs.

It's hard to know though. I think the best thing to do is measure for your use case and decide if the performance is acceptable or not.
If you don't have hardware you could also use the ram-backed block device + tracing (LFS_YES_TRACE+LFS_RAMBD_YES_TRACE) to measure how many read/erase/programs there are, and compare with the timings in the NAND flash's datasheet.


GROOVY-9985: STC does not report type mismatches in array initializers

This covers the array initializer but not the 'as' coercion

+1


sql with set not work

don't work
strsql := `DECLARE @et DATETIME
				DECLARE @st DATETIME
				set @et=getdate()
				SELECT TOP 20 ip, COUNT(1) AS ordercnt FROM dbo.DMS_OrdersYear a WITH(NOLOCK) WHERE OrderType<=3 AND CreateTime>=DATEADD(hh,-24,GETDATE()) AND CreateTime<GETDATE() GROUP BY ip ORDER BY COUNT(1) desc`
	rows, err := db.Query(strsql)

work:
strsql := `DECLARE @et DATETIME
				DECLARE @st DATETIME
				SELECT TOP 20 ip, COUNT(1) AS ordercnt FROM dbo.DMS_OrdersYear a WITH(NOLOCK) WHERE OrderType<=3 AND CreateTime>=DATEADD(hh,-24,GETDATE()) AND CreateTime<GETDATE() GROUP BY ip ORDER BY COUNT(1) desc`
	rows, err := db.Query(strsql)

digg into the code,if one param in the sql it works,may be some bugs with sendSqlBatch72

Post log and error message if you still have this problem.  Closing it for now.


Can't find the code

Where is it? Did anyone write it? Who is responsible?!

I pasted it below:

Oh awesome! Thank you so much


Floating point underflow with very high coverage

When we have very high coverage data, we run into floating point underflow in the biallelic genotyper. An easy way to fix this is by moving to log likelihoods.

Closed by #134.