kakoune: rework plugin support

Motivation for this change
The previous implementation of plugin-support for the kakoune derivation
was based on generating, at build time, a plugins.kak file that would
source all .kak files in the list of plugins, and wrap the kak binary
in a script that would add some command-line arguments so that this
file gets loaded on start-up. The main problem with this approach
is that the plugins' code get executed after the user's configuration
file is loaded, so effectively one cannot automatically activate/configure
these plugins.
The idiomatic way of loading plugins is ensuring they end up installed
somwhere under share/kak/autoload. Because plugins are already being
packaged to have their code in share/kak/autoload/plugins/<name-of-plugin>,
we can obtain a kakoune-with-plugins derivation simply by doing a
symlinkJoin of kakoune and all the requested plugins.
For this to work, we need to fix two issues:

By default, kakoune makes share/kak/autoload a symbolic link to
share/kak/rc, which contains all builtin definitions. We need
to patch this to put the symlink under share/kak/autoload/rc, so that
the join works.

kakoune actually expects the autoload directory to be in
../share/kak/autoload relative to the location of the kak binary
(and this can't currently be overriden, say, with environment
variables), so we can't rely on a symlink for the kak binary and
need to copy it instead.

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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)~
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] 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)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@jcpetruzza FWIW, I have been using Kakoune on macOS installed with this patch for weeks now, it fixed a problem I had with the previous setup and seems to be working great. What is needed to get this merged?

Also, I'm not sure what's going on, but the :doc command no longer autocompletes help pages, even though it does manage to find them.  I'm not sure why.

Oh, it got merged.  Huh, well nevermind.

Thanks for the feedback, @eraserhd!
I'm not sure what is the convention for naming packages in nixpkgs, tbh. My understanding was that the -unwrapped packages made sense when there were other versions of the same packages based on wrapping the binary with a shell script to select certain options. That way, the -unwrapped would serve as an entrypoint for that. Since with this change kak would no longer be based on a wrapper script, I though keeping the convention could be misleading. For what is worth, the convention of package and package-with-plugins is used elsewhere in nixpkgs too, e.g. with gimp.
The point about backwards compatibility is a very good one. If we were to go with kakoune/kakoune-with-plugins, we could perhaps makekakoune-unwrapped an alias to kakoune and mark it as deprecated.

@jcpetruzza I assume most people are currently using kakoune, rather than kakoune-unwrapped, so this alias won't help them.  I merged this PR locally, and I needed to change quite a few things.  See here: https://github.com/eraserhd/dotfiles/commit/a9e8c5d6f7324e3f07de9f70d306262ab3a5b270
I get the naming thing, and that's really unfortunate.
<rant/>Names are the principle method of abstraction in functional programming, and they should tell the caller their contract and hide the implementation details if possible....   hrmmm... <rant/>
Ok, how about kakoune-without-plugins and kakoune, with a deprecated alias kakoune-unwrapped for kakoune-without-plugins and a deprecated function wrapper wrapKakoune?
(Also, this PR now has conflicts from the recent release.)

@jcpetruzza Hey, this would be nice to get merged...  what do you think of the package renaming?  Also, there's now a merge conflict to resolve.

Yes, it'd be good to get this merged; it's been on my TODO list for a while, sorry! I'll be afk for the next two weeks, happy to look into it after that!
Notice that https://github.com/nix-community/home-manager/pull/1356 recently added support for kakoune plugins (so this now works via home-manager) but it requires kakaoune-unwrapped to work, so removing it will require some coordination.
I still think we should deprecate it, and use kakoune for plain kak, it's the most obvious name. Using kakoune-with-plugins makes it more easy to discover. We can probably make it so that kakoune.plugins [...] also works, to make all backwards compatible.

@eraserhd, I've updated the PR. Notable changes:

I tried to preserved backwards compatibility, so kakoune-unwrapped is still there, and kakoune can be overriden with either { plugins = [ foo ]; } or { configure = { plugins = [ foo ]; }; } as before.
No longer uses the hack of copying the binary, but now relies on KAKOUNE_RUNTIME (thanks for that, btw! :slightly_smiling_face:)
I "fixed" the issue with :doc not working with plugins you found. It seems kak doesn't like the doc files to be symlinks. It looks like a bug to me, but worked it around for now by copying the content of the files.

Let me know what you think?
@joefiorini If you are able to try the new version on macOS again, that'd be great!

Code looks good to me.  I'm currently bisecting Darwin breakages this morning, so I haven't tested yet.  Will post back when that's resolved.

Took me a while, but it is working nicely for me!

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/269


Remove the last reference to bugbug by removing the regressor script.…

… Fix #774
As the regressor information is now displayed directly on Phabricator, we can
remove regressor script and the bugbug dependency.

@marco-c @La0 @calixteman I have removed the regressor reference in the runauto_nag_daily.sh bash script. I think I have catched all the references to the old regressor script but maybe you know where it could be referenced in addition to the runauto_nag_daily.sh bash script.

@calixteman after removing it, you could also bring back the VM to a lower amount of RAM.

Coverage increased (+0.5%) to 26.115% when pulling 4d1f9da6d714d184ff3e8707ccda72223533a9e6 on Lothiraldan:remove-bugbug into 7859c8b692892fd07be234365567cfbaa925d3b4 on mozilla:master.


RHEL/CentOS: update VOLUME to match Documentation instructions

The Documentation for mssql in Docker uses the /var/opt/mssql mount point
while the Dockerfile is using the /var/opt/mssql/data mount point.
If the user specifies a persistent volume for the documented mount point,
the data may not be persisted due to Docker mounting the data dir separately
to non-persistent storage.

Closing due to age.


Breaking Change Disscussion: .NET 4.5 Support

Currently ExtendedXmlSerializer supports .NET Framework 4.5.
This is not ideal as it essentially forces two builds for every release: .NET 4.5 and everything else.
I wanted to start a discussion around this if anyone is still using .NET 4.5 and if this is used in any capacity with ExtendedXmlSerializer.
The idea is that we could bump the ExtendedXmlSerializer package to 2.2.x and make ExtendedXmlSerializer a strictly .NET Standard 2.0 library, which would support 4.6.1 as a minimum baseline.
If you absolutely require 4.5, you would have to force your dependency to the last version of ExtendedXmlSerializer 2.1.x (and pray you don't run into any bugs).
I am open to discussion around this and welcome any comments.  Speak now or forever hold your peace. 😆

Looks like 4.5.1 and below is unsupported, so this is really about any projects that use 4.5.2 and 4.6:
https://github.com/Microsoft/dotnet/blob/master/releases/README.md

I'm going to send some information next week. It is not so easy because of the issue in Full dotnet.

Yeah?  I guess I would have to see it.  I was able to remove it without any problems, all tests pass here:
https://github.com/Mike-EEE/ExtendedXmlSerializer/tree/dotnet461
It's basically removing the net45 from the ExtendedXmlSerializer
https://github.com/Mike-EEE/ExtendedXmlSerializer/blob/dotnet461/src/ExtendedXmlSerializer/ExtendedXmlSerializer.csproj#L8
and replacing net45 with net461 in ExtendedXmlSerializer.Tests:
https://github.com/Mike-EEE/ExtendedXmlSerializer/blob/dotnet461/test/ExtendedXmlSerializer.Tests/ExtendedXmlSerializer.Tests.csproj#L5

https://weblog.west-wind.com/posts/2019/Feb/19/Using-NET-Standard-with-Full-Framework-NET

https://github.com/dotnet/standard/issues/514

OK, so it seems like additional DLLs in the output folder is the primary inconvenience for .NET Framework 4.7.1 and below.
So, a hassle with extra assemblies, but still works.  I understand how that can be annoying to someone who is being mindful of disk space and utilized overhead.
That stated, as time goes on, the greater the chance a 4.7.1 and lower SLN incorporating a .NET Standard project only increases, leading to the inevitable (and annoying) inconvenience.
Personally, I do not find that annoying and am only glad that it works. 😁  Of course, I am using .NET Core these days and have given up .NET Framework for some time now.
Along those lines, my thought on this is that the .NET Framework is being phased out in favor of the new NEW (😆) .NET 5.  With that in mind, we should keep this issue open with high (pinned) visibility and then revisit in one year.
That should give plenty of time for a sample of those who use .NET Framework 4.7.1 and lower to respond to this issue.
At which point we can analyze the current IDE and .NET landscape to determine if it's a "big deal" or not to go .NET Standard 2.0-only.
Sound good?

Disk space is not the biggest problem. Let's imagine that someone has a program in full .net framework with an installer. After installing ExtendedXmlSerializer, the installer will have additional MB more. Quest what he will do? He will uninstall ExtendedXmlSerializer and he solves the problem in a different way.

Yeah?  I would still classify that as a disk space problem.  The more time that passes, the more common this will be, so those who use 4.5-4.6.1 will encounter this more and more (with other packages not ExtendedXmlSerializer), and eventually will migrate to 4.6.2 (especially if they are on 4.6.1!) to reduce the number of redundant dependencies on disk.
Is my hunch. 😁
I still say we wait a year to see if anyone who is using 4.5-4.6.1 to contribute to this discussion.
We currently have 64 GitHub repos that use EXS... is there a way to see which framework they are using?  That would be a good sample set to start analyzing.

It is not only a local disk space problem. Programs are built on some CI server so, they are saved on a shared disk. These installers are sent over the network, so there is also a network issue. The next problem is the time of sending.
Some people want to have also a clean bin directory. After installing .Net Standard in .Net Framework library you will get https://weblog.west-wind.com/images/2019/Using-.NET-Standard-with-Full-Framework-.NET/AssemblyHell.png
(picture from https://weblog.west-wind.com/posts/2019/Feb/19/Using-NET-Standard-with-Full-Framework-NET)
I think that we can remove .Net 4.5 but we should publish .Net 4.6(.x) version also.

Some people want to have also a clean bin directory

I understand that.  I am one of them. 😁  Or at least, I understand the unnecessary .dlls.  That image was my takeaway from that blog article when you shared it earlier, too.  It's quite striking!

I think that we can remove .Net 4.5 but we should publish .Net 4.6(.x) version also.

Technically this is the right thing to do as net45 is officially no longer supported by MSFT.  However, this leaves us in the same spot as we are now of having to support two versions of ExtendedXmlSerializer when ideally we should only have one in netstandard2.0.
Here's the table, actually:
https://dotnet.microsoft.com/download/dotnet-framework
Seems that 4.5.2 is the earliest that is supported.
We could bump from net45 to net452, which would protect 4.5.2-4.6.1 from AssemblyHell.png. 😆
However, I would still like to move to netstandard2.0 only at some point which would reduce the complexity of our project.
Let's keep this issue open for a year and find out.  I would love to know how many users are on 4.5.2-4.6.1.

Thinking about this more, let's table this discussion until we see how .NET 5 and the new tooling fares out.  Maybe they might find a way to get around the dll include hell for .NET Framework which makes this a non-issue.
One can hope. 😆

.NET Framework 4.5.2, 4.6, 4.6.1 will reach End of Support on April 26, 2022, so end is near.
Your dependency Sprache will drop 4.5, too with their version 3.0.

Dang, a better memory than I @MagicAndre1981!  So essentially we become a .NETStandard-only library at this time, I would take it.  I'm OK with this as it would greatly simplify our test suite.  Still feels a little wrong chopping it all away, though.
I guess technically that's a non-issue.  Conceivably, we would bump the major version (4.0.0), so those who still need to use .NET Framework can still use the 3.x found on nuget.
In any case, please do feel free to open a new issue around that time and we can take it from there. 👍


Update Interface to use shadcn-svelte

Whenever time permits (prof downtime/after work etc):
Update the interface globally to utilize shadcn-svelte wherever possible, especially on the user input fields on every page and the config.
Rethink some theming decisions and general layout.
This opens up migrating the queries frontend into Hare even more so than the queries svelte migration, as queries is using shadcn-svelte.

TODO: some guides modernization, adjust conflicting css, comb through the user agents for whats unnecessary
Post: check which tools should be added or removed from resources if it actually gets used
Bring queries into hare


Redeploy: extra variables passed to sub shell

Due to how Redeploy invokes the cluster.yml using a sub shell, there is currently no way to pass variables to the cluster.yml , so for example it could differentiate between a standard run and a redeployment run.
So my suggestion is to have an extra dictionary variable passed (redeploy_extra_vars) on all redeployment methods to the sub shell invoking cluster.yml
Example

redeploy.yml playbook:

- name: Redeploy
  hosts: localhost
  connection: local
  tasks:
    - name: Run redeploy
      include_role:
        name: clusterverse/redeploy
      vars:
        mainclusteryml: "cluster.yml"
        predeleterole: "persistence-cassandra/redeploy"
        redeploy_extra_vars:
          cassandra_redeploy: True

roles/clusterverse/redeploy/_scheme_addnewvm_rmdisk_rollback/tasks/redeploy_by_hosttype_by_host.yml:
https://github.com/sky-uk/clusterverse/blob/master/redeploy/_scheme_addnewvm_rmdisk_rollback/tasks/redeploy_by_hosttype_by_host.yml#L3

- name: "Run {{mainclusteryml}} to add {{cluster_host_redeploying.hostname}} to cluster"
  shell: "{{ (argv | join(' ')) | regex_replace('redeploy.yml', mainclusteryml) }} -e '{'redeploy_extra_vars': {{redeploy_extra_vars|default({})|to_json}}}' -e cluster_suffix={{cluster_suffix}} -e '{'cluster_hosts_target': [{{cluster_host_redeploying | to_json}}]}'"
  register: r__mainclusteryml
  no_log: True
  ignore_errors: yes

roles/clusterverse/redeploy/_scheme_rmvm_keepdisk_rollback/tasks/by_hosttype_by_host.yml:
https://github.com/sky-uk/clusterverse/blob/master/redeploy/_scheme_rmvm_keepdisk_rollback/tasks/by_hosttype_by_host.yml#L26

- name: "by_hosttype_by_host | Run {{mainclusteryml}} to add {{host_to_redeploy.hostname}} to cluster"
  shell: "{{ (argv | join(' ')) | regex_replace('redeploy.yml', mainclusteryml) }} -e '{'redeploy_extra_vars': {{redeploy_extra_vars|default({})|to_json}}}' -e cluster_suffix={{cluster_suffix}} -e '{'cluster_hosts_target': [{{host_to_redeploy | to_json}}]}'"
  register: r__mainclusteryml
  no_log: True
  ignore_errors: yes

roles/clusterverse/redeploy/_scheme_rmvm_rmdisk_only/tasks/by_hosttype_by_host.yml
https://github.com/sky-uk/clusterverse/blob/master/redeploy/_scheme_rmvm_rmdisk_only/tasks/by_hosttype_by_host.yml#L18

- name: "Run {{mainclusteryml}} to fix cluster"
  shell: "{{ (argv | join(' ')) | regex_replace('redeploy.yml', mainclusteryml) -e '{'redeploy_extra_vars': {{redeploy_extra_vars|default({})|to_json}}}'}}"
  register: r__mainclusteryml
  no_log: True
  ignore_errors: yes

The arguments from the root shell are passed to the cluster.yml sub-shell.  You should be able to do e.g.:

ansible-playbook redeploy.yml -e buildenv=sandbox -e clusterid=test -e cloud_type=gcp -e region=europe-west1 -e canary=none -e cassandra_redeploy=True

Thanks. I understand it could be passed via the command line, but my ask is to not having to do this, and pass arguments via the playbook (redeploy.yml) instead. Passing via command line requires that the arguments are known at the time of the execution.
Because it is a sub-shell, it would be very useful to allow multiple arguments to be passed - otherwise the only way is the command line.

closed by https://github.com/sky-uk/clusterverse/pull/104


Not able to use SSL certificate and keystore with Jersey

Refer to https://github.com/intuit/karate/issues/71 - this works fine with Apache.
Apache honors the system settings but Jersey does not seem to.

closing, realized this actually works as expected


[Feature]: Add the black linter workflow

[x] Would you like to take up this task?
[x] Are you from GSSoC'23?

✨
Feature request

Is your feature request related to a problem?
As a project with multiple users contributing to it, it is essential to maintain a proper linting style to ensure better code readability by users. An excellent way to do this is by automatic linting checks using the prettier linter in GitHub actions.

Describe the solution you'd like
Add the black linter workflow to ensure proper and uniform linting of the codebase

Thank you for expressing your interest in contributing to our project and participating in Gssoc'23. We value your enthusiasm and eagerness to contribute.
However, at this time, we would like to keep the issue template, readme, and other non-core project areas unchanged. These aspects have been carefully crafted and aligned with our project's guidelines and requirements.
That being said, we are delighted to have you contribute to the core functionality of our project. There are several key areas that require attention and enhancement. We believe your skills and expertise would be a valuable addition in these areas. If you are interested, we can provide you with more detailed information about the specific features and functionality that need improvement.
We appreciate your understanding regarding our decision to maintain the existing documentation and non-core aspects of the project. We genuinely look forward to collaborating with you on the core functionality, where your contributions can make a significant impact.
Please let us know if you are still interested, and we will provide you with further guidance and support to get you started.

Thank you for expressing your interest in contributing to our project and participating in Gssoc'23. We value your enthusiasm and eagerness to contribute.
However, at this time, we would like to keep the issue template, readme, and other non-core project areas unchanged. These aspects have been carefully crafted and aligned with our project's guidelines and requirements.
That being said, we are delighted to have you contribute to the core functionality of our project. There are several key areas that require attention and enhancement. We believe your skills and expertise would be a valuable addition in these areas. If you are interested, we can provide you with more detailed information about the specific features and functionality that need improvement.
We appreciate your understanding regarding our decision to maintain the existing documentation and non-core aspects of the project. We genuinely look forward to collaborating with you on the core functionality, where your contributions can make a significant impact.
Please let us know if you are still interested, and we will provide you with further guidance and support to get you started.

I am very much interested and would love to get guidance and support from you. Please do let me know more about where I can contribute.


Create Post “dva-c01-studying-iam-part-2”

Automatically generated by Netlify CMS

👷 Deploy Preview for dazzling-dieffenbachia-448a02 processing.

Name
Link

🔨 Latest commit
74484ce9519f6f20e4f023ad4b76f4b919e6499d

🔍 Latest deploy log
https://app.netlify.com/sites/dazzling-dieffenbachia-448a02/deploys/62cc85231e1251000825af68


Move rule type engine code to more descriptive files

Summary
Instead of having everything under the rule_type.go file in the engine,
this moves the validation and engine to their own files respectively.
This is in hopes to make the codebase a little easier to follow.
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[x] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 47.701%. remained the same
when pulling 80baee8a52dec32540be901ce30c9f6acdf5c408 on rt-move
into 112288805d47111b652fd8eaee1f3f0e80fa6914 on main.


in debug  "hkubeapi.start_algorithm" and "start_stored_subpipeline" with "resultAsRaw=True" does not return results

HKube micro-service
code api
Describe the bug
when debugging Pthon algorithm  "hkubeapi.start_algorithm" and "start_stored_subpipeline" with "resultAsRaw=True" does not return results (if building  the algorithm it works properly  )
code example

import time
def start(args, hkubeapi):
    input=args['input'][0]
    if input and input["action"] == "start_alg":
        ret = hkubeapi.start_algorithm(input["name"], input["input"], resultAsRaw=True, blocking=True) #input["resultAsRaw"]
        time.sleep(2)
        print(ret)
        return ret

    if input and input["action"] == "start_stored_subpipeline":
        ret = hkubeapi.start_stored_subpipeline(input["name"], input["input"],  blocking=True)
        time.sleep(2)
        print(ret)
        return ret
    time.sleep(1)
    return "did not get response"

to start algorithm use
{
    "action":"start_alg",
    "name":"yellow-alg",
    "input":[7]

    }

to start sub pipeline use
{
    "action":"start_stored_subpipeline",
    "name":"simple",
    "input":{"inp":7}
    }

on  "systemVersion": "v1.3.46",
"fullSystemVersion": "v1.3.46-1593064528107",
"versions": [
connected to ws://test.hkube.io/hkube/debug/tamir?storage=v2&encoding=bson
got message from worker: initialize
sending message to worker: initialized
got message from worker: start
sending message to worker: started
start_algorithm called with yellow-alg
sending message to worker: startAlgorithmExecution
got message from worker: algorithmExecutionDone
Traceback (most recent call last):
File "src/gevent/greenlet.py", line 854, in gevent._gevent_cgreenlet.Greenlet.run
File "/home/tamirre/envs/python36/lib/python3.6/site-packages/hkube_python_wrapper/wrapper/wc.py", line 49, in algorithmExecutionDone
self.events.on_algorithmExecutionDone(data)
File "/home/tamirre/envs/python36/lib/python3.6/site-packages/events/events.py", line 95, in call
f(*a, **kw)
File "/home/tamirre/envs/python36/lib/python3.6/site-packages/hkube_python_wrapper/codeApi/hkube_api.py", line 25, in algorithmExecutionDone
result = self._dataAdapter.tryGetDataFromPeerOrStorage(response)
File "/home/tamirre/envs/python36/lib/python3.6/site-packages/hkube_python_wrapper/wrapper/data_adapter.py", line 124, in tryGetDataFromPeerOrStorage
dataPath = options.get('path')
AttributeError: 'int' object has no attribute 'get'
2020-06-25T13:57:01Z <Greenlet at 0x7f87d87a0548: <bound method WebsocketClient.algorithmExecutionDone of <hkube_python_wrapper.wrapper.wc.WebsocketClient object at 0x7f87f1d27978>>({'execId': '1', 'response': 1})> failed with AttributeError

tested on  "systemVersion": "v1.3.58",
"fullSystemVersion": "v1.3.58-1593434450223",
hkube-python-wrapper 2.0.4


Recurrent Highway Networks - some remarks

Hi LeavesBreathe,
Thank you for making these tensorflow implementations of new papers public. I really appreciate it.
There are just two remarks I would like to make.
First, the original setup of Recurrent Highway Networks uses the input only in the first of the stacked highway layers. If I am not mistaken, the current implementation uses the input in all stacked highway layers. This is, of course, in the end a design choice.
Second, it is probably best to test Recurrent Highway Networks on large language modeling datasets. From the experiments we ran, it seemed that the network overfits very easily on the PTB dataset. A smart regularization scheme will be necessary otherwise only qualitative results (as reported on PTB in the paper) will be achieved. Hence training on large datasets is more suitable to do the network justice. Even then the network overfit without regularization on the Hutter Wikipedia dataset.
Thanks again for the good work.
Best wishes,
Julian

Hey @julian121266,
Thanks for addressing these two issues. Firstly, I reviewed the paper, and it does seem that they opt to just use the inputs on the first layer, I have added an option on the mulint version of the recurrent highway to turn on and off using the input on subsequent layers. This also applies to the gating function as well.
Harder datasets are probably more preferable. I think at this point though, users can simply supply their own dataset that they want to use? I feel that having a larger dataset will make the repo itself very large. I'm going to close this issue as I think both points are addressed but feel free to reopen it or start a new issue.


[Exposure Request] codeunit 64 "Sales-Get Shipment" - CalcInvoiceDiscount

Please make function CalcInvoiceDiscount externally available:
procedure CalcInvoiceDiscount(var SalesLine: Record "Sales Line")
var
    SalesReceivablesSetup: Record "Sales & Receivables Setup";
    SalesCalcDiscount: Codeunit "Sales-Calc. Discount";
begin
    SalesReceivablesSetup.Get();
    if SalesReceivablesSetup."Calc. Inv. Discount" then begin
        SalesCalcDiscount.CalculateInvoiceDiscountOnLine(SalesLine);
        OnAfterCalcInvoiceDiscount(SalesLine);
    end;
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 45938.


lib: posix: nanosleep

This change adds support for nanosleep(2) documented at
https://pubs.opengroup.org/onlinepubs/9699919799/functions/nanosleep.html
Note: Does not achieve any greater resolution than that provided by k_busy_wait(us) but at least makes the API available.
I've not researched it much in Zephyr, but I would say there is still some work to be done for a generic clock API - one that allows querying resolutions, supports multiple system clocks, etc, primarily to support POSIX time APIs.
A nanosleep system call would also require high-res timer support (See #6498)
Fixes #25554

I have a feeling there is a conflict with CONFIG_BOARD_NATIVE_POSIX
CONFIG_BOARD_NATIVE_POSIX_64BIT

I have a feeling there is a conflict with CONFIG_BOARD_NATIVE_POSIX
CONFIG_BOARD_NATIVE_POSIX_64BIT

I'm not sure what exactly you mean (that native_posix and native_posix_64 boards conflict between each other?), but otherwise it's a known problem that Zephyr POSIX subsys conflicts with native_posix board. It should be understanding why - it's too layery a pie, where Zephyr POSIX subsys sits on top of native Zephyr core, and naive_posix boards tries to implement that in terms of the underlying full-POSIX system. Something doesn't match regularly. Many a POSIX tests/samples simply blacklist native_posix.

I have a feeling there is a conflict with CONFIG_BOARD_NATIVE_POSIX
CONFIG_BOARD_NATIVE_POSIX_64BIT

I'm not sure what exactly you mean (that native_posix and native_posix_64 boards conflict between each other?), but otherwise it's a known problem that Zephyr POSIX subsys conflicts with native_posix board. It should be understanding why - it's too layery a pie, where Zephyr POSIX subsys sits on top

That's what I meant. Sorry, was on mobile when I commented previously.

Should be good to go now
$ ./scripts/sanitycheck --enable-slow --inline-logs -j8 --testcase-root tests/posix/common
Renaming output directory to /home/cfriedt/workspace/zephyrproject/zephyr/sanity-out.24
INFO    - JOBS: 8
INFO    - Selecting default platforms per test case
INFO    - Building initial testcase list...
INFO    - 26 test configurations selected, 972 configurations discarded due to filters.
INFO    - Adding tasks to the queue...
INFO    - Total complete:   26/  26  100%  skipped:    0, failed:    0
INFO    - 26 of 26 tests passed (100.00%), 0 failed, 0 skipped with 0 warnings in 179.42 seconds
INFO    - In total 4 test cases were executed on 13 out of total 250 platforms (5.20%)
INFO    - 20 tests executed on platforms, 6 tests were only built.

Btw, the variance in latency (in CI / qemu) is pretty drastic between architectures. E.g. on qemu_cortex_r5, it was 500us, on xtensa it was 86 us, and on qemu_cortex_m3 it was 25us.
Sample size of 1, not statistically representative, of course.

@cfriedt, Thanks for the patch. I would personally recommend this merged for 2.3, but per the release freeze rules, 2 reviews are required at this time. I've added @carlescufi who both could review and merged (but definitely busy with a lot of other stuff now, as the release manager for this version), but feel free ping other folks who you know can help with review.

@cfriedt, Thanks for the patch. I would personally recommend this merged for 2.3, but per the release freeze rules, 2 reviews are required at this time. I've added @carlescufi who both could review and merged (but definitely busy with a lot of other stuff now, as the release manager for this version), but feel free ping other folks who you know can help with review.

It would be awesome if nanosleep could actually get relatively close to the exact time (if there is hardware to support it). The high-res timer stuff is pretty important though, and I think it deserves a great deal of care. No rush on that one. The nice thing about it though is that the interface is there, and it's not moving, so just redoing the implementation later will have no unwanted side-effects.

@carlescufi  - rebased off of using <stdint.h> integer types. Should be good to go as long as the build works.

Was green before. Looks like there is some misra change that breaks things atm

some misra change

New swear word in software engineering? ;-)

starting test - test_timeout_lifo_thread

    Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/lifo/lifo_usage/src/main.c:329: test_timeout_lifo_thread: packet != NULL is false

FAIL - test_timeout_lifo_thread

I got such a failure in one of my recent PR. Looks like nondeterministic failure du jour.
@cfriedt: Please keep rebasing this, until sweet spot is found.


Error - events.js:187 - Unhandled 'error' event

sgp -f fe6df99ec3e030c73e20cc620144c020b76d55b4 -o ./output
events.js:187
throw er; // Unhandled 'error' event
^
Error: spawn git ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:264:19)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
at onErrorNT (internal/child_process.js:456:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: 'ENOENT',
code: 'ENOENT',
syscall: 'spawn git',
path: 'git',
spawnargs: [
'diff',
'--name-status',
'fe6df99ec3e030c73e20cc620144c020b76d55b4',
'HEAD'
]
}

It appears to me that spg cannot launch git.  Not sure what info you might need from me to debug this!

The repo should be specified.
Else the default value will be taken (./repo)

I’m not following your response well.  How would I specify the repo?  I’m running the command from the root directory of the git repo ( and my project).

You want to provide the --repo parameter or shorter version : -r  to the cli.
In your case as you are in the repo when executing the command line, you just need to provide "-r ." parameter


[BUG] normal import use case is considered as unused (only on master branch).

/lab.py:
from pathlib import Path

EXAMPLE = Path(__file__).parent

python3 -m unimport lab.py -d

--- lab.py

+++

@@ -1,3 +1,2 @@

-from pathlib import Path

 EXAMPLE = Path(__file__).parent

Note: this bug doesn't affect the current version, only the master one!

This is the line that caused the issue, I would appreciate it if you want to work on this issue, If you don't want it, I will.

I'm gonna try as soon as I have time for that, and please don't forget to not release until we fix this!

@hakancelik96 I'm sorry to say that, but unfortunately, I've no time for that, so I'm gonna unassign myself.
I apologize for the delay and withdrawal.

I'm afraid to disrupt the workflow.

Okey no problem


fixing tests for dart sass

@Athorcis Thanks for your super work! I merged it, and will going to open a PR with the final branch in the original sass-extract repo!


Avoid backgrounding by default when doing runhouse start.

With the addition of nohup if screen is not available, we were
backgrounding by default when running runhouse start. Now we should only do
it if runhouse start --nohup was passed.

Current dependencies on/for this PR:

main

PR #386   👈

This stack of pull requests is managed by Graphite.

if you run runhouse start locally, on main, right now, it uses nohup.
We want to avoid backgrounding when running runhouse start. This PR just makes it optional to background.


Crash on legal (but non-standard) getter code

  val testGetter: Boolean; get() {
    return "OK" == "foo"
  }

The formatter crashes on this code with the error:
error: expected token: ';'; generated get instead
Removing the ; and putting the get() on the following line fixes the exception.

I'm thinking we should remove the semicolon from the formatted code, so this becomes
val testGetter: Boolean
   get() {
     return "OK" == "foo"
   }

(or whatever ktfmt outputs for a getter without a semicolon preceding it).
@bethcutler  @strulovich  thoughts?

Stumbled into this example in the wild, in case it's useful as a repro:
https://github.com/JetBrains/kotlin/blob/723ef8f1fba8664f3948f545f5d7091047d0920c/compiler/frontend/src/org/jetbrains/kotlin/types/expressions/PatternMatchingTypingVisitor.kt#L103

Honestly, for things this small, I feel like that one could get one-liner'ed.
val testGetter: Boolean get() { return "OK" == "foo" }

This connects back to the "lambda formatting" issues I see elsewhere here. But generally I do small things like this in one line.

@cgruber, I agree that in the case of a really simple getter this may look better.
If you'd like to send a PR we can make sure it looks reasonable on our existing code and take it. (I assume we will only allow this 1-line if only a get or set exists, and not both)

On v0.47 this no longer crashes and formats to
  val testGetter: Boolean; get() {
    return "OK" == "foo"
  }


docs: FileClient.uploadFile supports stream

Fixes: #232
FileClient.uploadFile() has already supported Stream because the method uses form-data in Node.js environment.

@chick-p form-data is only used in Node.js environment, so Stream support is only in Node.js. It would be nice to add a note for the limitation👍

@koba04 Thank you for your review. I added a note for the limitation.


Add requirement on service_offering_ref to throw 422 instead of 404

This should fix the 422/404 on the create_portfolio_itemcall.

@miq-bot add_reviewer mkanoor
@miq-bot add_reviewer syncrou


Running conda-pytorch from a secondary drive causes a linking issue

On the qgpu machines, I keep my pytorch repo checkouts in the /work directory, which is on a larger secondary hard drive. This causes an issue when conda-pytorch tries to (presumably) create hard links from pytorch nightly files in /tmp to the pytorch repo directory. Since it's not possible to create hard links between two different drives, it fails.
When I run conda-pytorch dev inside my pytorch checkout in /work/kurtamohler/development/pytorch-cuda, I get this error:
INFO:conda-pytorch:Checking out nightly PyTorch took 6.901 [s]
INFO:conda-pytorch:Moving nightly files into repo
Linking /tmp/tmp37q8i1vy/lib/python3.8/site-packages/torch/_C.cpython-38-x86_64-linux-gnu.so -> /work/kurtamohler/development/pytorch-conda/torch/_C.cpython-38-x86_64-linux-gnu.so
Traceback (most recent call last):
  File "/home/kurtamohler/miniconda3/bin/conda-pytorch", line 11, in <module>
    load_entry_point('conda-pytorch==0.0.0', 'console_scripts', 'conda-pytorch')()
  File "/home/kurtamohler/miniconda3/lib/python3.7/site-packages/conda_pytorch-0.0.0-py3.7.egg/conda_pytorch/main.py", line 25, in main
  File "/home/kurtamohler/miniconda3/lib/python3.7/site-packages/conda_pytorch-0.0.0-py3.7.egg/conda_pytorch/main.py", line 17, in dev
  File "/home/kurtamohler/miniconda3/lib/python3.7/site-packages/conda_pytorch-0.0.0-py3.7.egg/conda_pytorch/develop.py", line 208, in install
  File "/home/kurtamohler/miniconda3/lib/python3.7/site-packages/conda_pytorch-0.0.0-py3.7.egg/conda_pytorch/tools.py", line 27, in wrapper
  File "/home/kurtamohler/miniconda3/lib/python3.7/site-packages/conda_pytorch-0.0.0-py3.7.egg/conda_pytorch/develop.py", line 198, in move_nightly_files
  File "/home/kurtamohler/miniconda3/lib/python3.7/site-packages/conda_pytorch-0.0.0-py3.7.egg/conda_pytorch/develop.py", line 184, in _link_files
  File "/home/kurtamohler/miniconda3/lib/python3.7/site-packages/conda_pytorch-0.0.0-py3.7.egg/conda_pytorch/develop.py", line 174, in _move_single
OSError: [Errno 18] Invalid cross-device link: '/tmp/tmp37q8i1vy/lib/python3.8/site-packages/torch/_C.cpython-38-x86_64-linux-gnu.so' -> '/work/kurtamohler/development/pytorch-conda/torch/_C.cpython-38-x86_64-linux-gnu.so'

Would there be anything issue with checking out the nightly pytorch directly into the repo, avoiding /tmp?

Ah I see that on Windows, these files are being copied rather than linked. I'll make a PR to check if the target dir is on a different drive, and copy the files if so.

If this ends up being a real issue, I can move the temp directory to the current PyTorch repo dir.  And that should fix it.  Also I just fixed an issue with relative paths not copying correctly


Mov kyma env cleanup job

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.4 out of 5 committers have signed the CLA.:white_check_mark: szwedm:white_check_mark: ukff:white_check_mark: MarekMichali:white_check_mark: piotrmiskiewicz:x: kyma-btp-manager-botYou have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.4 out of 5 committers have signed the CLA.:white_check_mark: piotrmiskiewicz:white_check_mark: ukff:white_check_mark: szwedm:white_check_mark: MarekMichali:x: kyma-btp-manager-botYou have signed the CLA already but the status is still pending? Let us recheck it.

/test all

/test pre-kyma-environment-broker pull-keb-deprovision-retrigger-job-build pull-keb-runtime-reconciler-job-build pull-keb-trial-cleanup-job-build

CLA already completed in kyma-project/control-plane


Overflow error

https://github.com/nnaisense/evotorch/blame/9d31d59cfcace0c99de59bf59bfbc7ceb55ae11f/src/evotorch/algorithms/cmaes.py#L365
This line results in an overflow error for me. The floor results to zero, thus division by zero.
shouldn't this line be:
int(np.floor(1 / (10 * d * (self.c_1.cpu() + self.c_mu.cpu()))))

Hi @sstroobants !
Thank you for your very useful feedback, and sorry for my very late reaction!
Hopefully this fixes the issue: https://github.com/nnaisense/evotorch/pull/86


[stable/prometheus-operator] Version 4.0.0 is broken

I created a fresh kuberentes cluster 1.14.0-alpha3.
Then installed helm and run setup for prometheus operator
helm install --namespace monitoring stable/prometheus-operator --name prometheus-operator

I got next exception:
Error: validation failed: [unable to recognize "": no matches for kind "Alertmanager" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"]

tiller logs:
[tiller] 2019/02/25 15:02:49 preparing install for prometheus-operator
[storage] 2019/02/25 15:02:49 getting release history for "prometheus-operator"
[tiller] 2019/02/25 15:02:49 rendering prometheus-operator chart using values
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/alertmanager/podDisruptionBudget.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/prometheus-operator/cleanup-crds.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/exporters/kube-etcd/endpoints.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/exporters/kube-scheduler/endpoints.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/prometheus/additionalAlertmanagerConfigs.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/charts/grafana/templates/dashboards-json-configmap.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/charts/prometheus-node-exporter/templates/endpoints.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/prometheus/additionalScrapeConfigs.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/exporters/kube-controller-manager/endpoints.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/prometheus/podDisruptionBudget.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/grafana/configmap-dashboards.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/alertmanager/ingress.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/charts/grafana/templates/ingress.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/prometheus/servicemonitors.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/charts/grafana/templates/pvc.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/prometheus/ingress.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/exporters/kube-dns/servicemonitor.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/prometheus/additionalAlertRelabelConfigs.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/prometheus/additionalPrometheusRules.yaml" is empty. Skipping.
2019/02/25 15:02:49 info: manifest "prometheus-operator/templates/exporters/kube-dns/service.yaml" is empty. Skipping.
[tiller] 2019/02/25 15:02:49 performing install for prometheus-operator
[tiller] 2019/02/25 15:02:49 executing 4 crd-install hooks for prometheus-operator
[tiller] 2019/02/25 15:02:49 deleting crd-install hook alertmanagers.monitoring.coreos.com for release prometheus-operator due to "before-hook-creation" policy
[kube] 2019/02/25 15:02:49 Starting delete for "alertmanagers.monitoring.coreos.com" CustomResourceDefinition
[kube] 2019/02/25 15:02:49 customresourcedefinitions.apiextensions.k8s.io "alertmanagers.monitoring.coreos.com" not found
[kube] 2019/02/25 15:02:49 building resources from manifest
[kube] 2019/02/25 15:02:49 creating 1 resource(s)
[tiller] 2019/02/25 15:02:49 deleting crd-install hook prometheuses.monitoring.coreos.com for release prometheus-operator due to "before-hook-creation" policy
[kube] 2019/02/25 15:02:49 Starting delete for "prometheuses.monitoring.coreos.com" CustomResourceDefinition
[kube] 2019/02/25 15:02:49 customresourcedefinitions.apiextensions.k8s.io "prometheuses.monitoring.coreos.com" not found
[kube] 2019/02/25 15:02:49 building resources from manifest
[kube] 2019/02/25 15:02:49 creating 1 resource(s)
[tiller] 2019/02/25 15:02:49 deleting crd-install hook prometheusrules.monitoring.coreos.com for release prometheus-operator due to "before-hook-creation" policy
[kube] 2019/02/25 15:02:49 Starting delete for "prometheusrules.monitoring.coreos.com" CustomResourceDefinition
[kube] 2019/02/25 15:02:49 customresourcedefinitions.apiextensions.k8s.io "prometheusrules.monitoring.coreos.com" not found
[kube] 2019/02/25 15:02:49 building resources from manifest
[kube] 2019/02/25 15:02:49 creating 1 resource(s)
[tiller] 2019/02/25 15:02:49 deleting crd-install hook servicemonitors.monitoring.coreos.com for release prometheus-operator due to "before-hook-creation" policy
[kube] 2019/02/25 15:02:49 Starting delete for "servicemonitors.monitoring.coreos.com" CustomResourceDefinition
[kube] 2019/02/25 15:02:49 customresourcedefinitions.apiextensions.k8s.io "servicemonitors.monitoring.coreos.com" not found
[kube] 2019/02/25 15:02:49 building resources from manifest
[kube] 2019/02/25 15:02:50 creating 1 resource(s)
[tiller] 2019/02/25 15:02:50 hooks complete for crd-install prometheus-operator
[tiller] 2019/02/25 15:02:50 failed install perform step: validation failed: [unable to recognize "": no matches for kind "Alertmanager" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"]

Yesterday it was worked well, but I assume a new version was released.
 $ helm version
Client: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}

This is an old issue and one caused by Helm itself, rather than this chart
https://github.com/helm/charts/issues/9241
There is a link to a work-around from that issue also as well as a PR for Helm to try addressing it in a later version

@vsliouniaev interesting that if I install chart from local filesystem it works. And as I mentioned I install prometheus-operator to fresh cluster for one week, and it starts happen only today. Anyway thanks for the #9241, will try to do this.

1- helm ls --all
2- //purge all packages based on the name that you have found via "helm ls --all"
helm delete --purge existing-saola
helm delete --purge fair-saola
helm delete --purge guiding-tortoise
3- helm install --name prometheus stable/prometheus --namespace=monitoring


Version increase to 1.0.5.  Testing new onVisibilityChange prop.

I've added a visibility callback (needed for anlaytics on one of our projects) to Lazyloadview and updated the README.md appropriately.  I'm hoping you merge this back in – I'd love to benefit from the main repo's changes.
I'm also curious about how, exactly, rendering is deferred since I'm seeing messages come through on invisible components if I console during a render, but that's a conversation for another pull request :)
Thank you!

FYI - this is working in production on an app about to go out globally.  Very seamless.  Please pull if you can!

Updated to fix naming collisions and adding scrollablemixin capabilities to the listview component.

Thanks for this PR
:+1:


I wish /docs/ knew how awesome it was for asking me what else I wished about it!

I wish /docs/ knew how awesome it was for asking me what else I wished about it!

Haha, thank you! Glad you like the feature. :)


[stdlib] Partially ungyb Integers

The new file straucture is similar to that of floating point types,
where protocols live in one file, and concrete types – in another.

@stephentyrone 's idea.

@swift-ci Please test

@swift-ci please test compiler performance

@swift-ci Please benchmark

!!! Couldn't read commit file !!!

Build comment file:
Build failed before running benchmark.

Build failed
Swift Test OS X Platform
Git Sha - f04cd628aac26de3c337bb259a1550a0094a6dd0

@swift-ci Please test macOS platform

Build failed
Swift Test OS X Platform
Git Sha - f04cd628aac26de3c337bb259a1550a0094a6dd0

@swift-ci Please smoke test Linux platform

@swift-ci Please smoke test Linux platform

@swift-ci Please smoke test Linux platform

@swift-ci Please smoke test macOS platform

@swift-ci Please smoke test macOS platform

@swift-ci Please benchmark

@swift-ci Please test compiler performance

!!! Couldn't read commit file !!!

Build comment file:
Performance: -Onone

TEST
OLD
NEW
DELTA
SPEEDUP

Improvement

CharIndexing_tweet_unicodeScalars
767940
690931
-10.0%
1.11x

How to read the data
The tables contain differences in performance which are larger than 8% and differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false alarms. Unexpected regressions which are marked with '(?)' are probably noise. If you see regressions which you cannot explain you can try to run the benchmarks again. If regressions still show up, please consult with the performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB

@swift-ci Please test macOS platform


Webp support

Would it be possible to add webp image format support for this?
This would mean lower download sizes for people using the API compared to png and jpg.

Hi @xXBuilderBXx
JPEG and PNG are only provided as a fallback for older environments. For newer environments, SVG should be used. For this reason there is no support for webp, because webp has no advantage over SVG. Feel free to correct me if I missed something.

SVG is nice for your own website stuff but still a lot of online services don't really support SVG uploading and/or viewing things like chat platforms such as Discord and social media websites like Twitter.
Having support for webp would allow support for both those cases while also keeping the download size smaller.

Good arguments. I will look into an implementation.


refactor: Create 'operator' folder (move docs)

This commit is part of a larger set of commits with the goal of restructuring the repository.
Signed-off-by: Romain Arnaud<EMAIL_ADDRESS>

@bnallapeta

I believe kcp-registration.md and operations.md are now moved to Architect folder. Should be deleted from here.

The diff tells me that the file are move from the architect folder. My understanding is that it is OK.

Git url ...

Addressed by your edit.

@Roming22 Ack. Merging the PR.


Linked to multiple cheat sheets (Git, VSCode, HTML, JS)

Linked to multiple cheat sheets (Git, VSCode, HTML, JS)

Thank you @tomaslau


Port forwarding boot2docker 1.2.0

Hello,
I got an issue when I try to ping my nginx container from my computer.
What I do for my test :
Go in the docker-vm :
`{ ~ }  » boot2docker ssh                                                                      ~ 1
boot2docker: 1.2.0
             3.16.1-config-file : e75396e - Fri Aug 22 06:45:30 UTC 2014
docker@boot2docker:~$ docker -v
Docker version 1.2.0, build fa7b24f
docker@boot2docker:~$ docker run -Pd nginx
5a2d49cd85c1a4426c4421e796fb872ef0b4fe0efad4ff2b2c39464f333f6dad
docker@boot2docker:~$ docker ps
CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS                                           NAMES
5a2d49cd85c1        nginx:latest        "nginx -g 'daemon of   3 seconds ago       Up 3 seconds        <IP_ADDRESS>:49157->443/tcp, <IP_ADDRESS>:49158->80/tcp   focused_fermi

docker@boot2docker:~$ curl -I localhost:49158
HTTP/1.1 200 OK
Server: nginx/1.7.5

docker@boot2docker:~$ exit

So it's working in the VM, but when I go out :
{ ~ }  » boot2docker ip                                                                         ~
The VM's Host only interface IP address is: <IP_ADDRESS>
{ ~ }  » curl -v <IP_ADDRESS>:49158                                                       ~ 130
* STATE: INIT => CONNECT handle 0x8001f458; line 1026 (connection #-5000)
* Rebuilt URL to: <IP_ADDRESS>:49158/
* Hostname was NOT found in DNS cache
*   Trying <IP_ADDRESS>...
* STATE: CONNECT => WAITCONNECT handle 0x8001f458; line 1073 (connection #0)

No response...
After this first test, I add a rule for the VM and I restart it :

But still the same result..
{ ~ }  » curl -v <IP_ADDRESS>:49158                                                           ~
* STATE: INIT => CONNECT handle 0x8001f458; line 1026 (connection #-5000)
* Rebuilt URL to: <IP_ADDRESS>:49158/
* Hostname was NOT found in DNS cache
*   Trying <IP_ADDRESS>...
* STATE: CONNECT => WAITCONNECT handle 0x8001f458; line 1073 (connection #0)

What did I wrong?
Thanks in advance for your help

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).


Feature/support python3.12

Feature: Support python 3.12

Update CI testing for python 3.12
Update setup.py for python 3.12 (note added package dependency setuptools; refer to pep 632 )

Closing this and opening a new PR against master branch.


nqfrom-angle tries to store resulting quaternion in the axis argument

I'm not sure what it should do instead. I suppose it's a nonsense OP since the first arg isn't a quat.


registry.list_models() returns un empty list

Description
Tensor2Tensor library can't find any of its predefined models! I wanted to use the Transformer but finally, I found that it contains absolutely no single model, because registry.list_models() returned an empty list.
Environment information
OS: Manjaro Linux 64-bit with kernel 4.19.81 and KDE Plasma 5.17.2

$ pip freeze | grep tensor
mesh-tensorflow==0.1.4
tensor2tensor==1.14.1
tensorboard==1.15.0
tensorflow==1.15.0
tensorflow-datasets==1.3.0
tensorflow-estimator==1.15.1
tensorflow-gan==2.0.0
tensorflow-hub==0.7.0
tensorflow-metadata==0.15.0
tensorflow-probability==0.7.0

$ python -V
Python 3.7.4

For bugs: reproduction and error logs
>>> from tensor2tensor.utils import registry
>>> registry.list_models()
[]

Steps to reproduce:
Import the registry module then list_models():
>>> from tensor2tensor.utils import registry
>>> registry.list_models()
[]

Nevermind, solved it simply by adding a stupid from tensor2tensor import models!


Pass function to create option in connectOrCreate that is only executed when create is actually executed

Problem
when I try to collect data from an api, I get only a list of id's of deeper objects.
currently I have to request every time the detail api endpoint for every object
{
  connectOrCreate: await Promise.all(
    organization.membership.map(
      async (
        id,
      ) => {
        const membership = await oparl.getData(id);
        return {
          where: {
            id: membership.id,
          },
          create: membership,
        };
      },
    ),
  ),
}

Suggested solution
when I can pass a function to the create option, it is possible to request the detail endpoint only if necessary.
{
  connectOrCreate: await Promise.all(
    organization.membership.map(
      async (
        id,
      ) => ({
          where: {
            id: membership.id,
          },
          create: await oparl.getData(id),
      }),
    ),
  ),
}

@ManAnRuck did you mean create: oparl.getData(id)? I think the way it is now, it would be the same as the problem example.
I'm not fully sure I understand the problem. Can you try explaining the problem in more detail? Thanks!

oparl.getData(id) is a function which calls a rest API and get more data.
connectOrCreate.where connects the id property if it exists.
connectOrCreate.create takes an object and when the where id doesn't exists, it creates a new entry
if I am right, currently it's only possible to pass only an object to the create property.
this means I first have to get the details from api for both cases. (the entry exists and not)
when it is possible to pass an async function to create, then I can save network traffic if the entry already exists.

Does a solution for this exist yet?


On install of 0.59 from 56.2 or 57.2, computer went to blue "Restarting" screen without asking. It closed several other programs without save.

Microsoft PowerToys version
0.59.0
Running as admin

[ ] Yes

Area(s) with issue?
Installer
Steps to reproduce
Popup showed up asking if I wanted to update the version I started the update and went back to working.
PowerToysReport_2022-06-07-11-36-17.zip
✔ Expected Behavior
I expect if a program needs the computer to restart, that it will ask.
❌ Actual Behavior
A sudden reboot was triggered without warning.
Other Software
No response

This should've been fixed in 0.57.0.
https://github.com/microsoft/PowerToys/commit/aba4e462a86d22c2486accc38a83c1e754c8855c
The logs you've sent are from 0.56.1, where this was still an issue.
Could you please send the logs from the machine that was on 0.57.2 and showed this behavior? Thank you. /needinfo

PowerToysReport_2022-06-07-12-10-36.zip
Logs sent before were auto generated after the update and restart. I've generated a new set here. I'm not certain now what previous version was - I had just glossed over that when the update notification popped up. Best recollection is 0.56.2 or 0.57.2.
I would assume then it was 0.56.2 and the issues is fixed since then. I will close ticket.

Based on the logs it does seem to be an upgrade from 0.56.1 to 0.59.0, but I had the same experience upgrading from 0.57.2. It seems the inclusion of the VC++ Redistributable is at fault here.
I've included the specific log where a reboot is required by vcredist, and while this installer does not initiate a reboot, the bootstrapper itself does after completion. As I did a silent install the computer rebooted without any notification.
Is it possible to also suppress a required reboot by vcredist?
Please let me know if you require any additional information!
powertoys-bootstrapper-msi-0.59.0_20220608105411.log

@NickSPH if you're doing a silent install that's what the bootstrapper will do unless you specify the /norestart flag for the bootstrapper like we do when updating: https://github.com/microsoft/PowerToys/commit/aba4e462a86d22c2486accc38a83c1e754c8855c
Unfortunately the default for the Wix bootstrapper is to restart automatically when doing a silent install unless you specify that flag as well.
Hope this helps.


pull in fix from argocd-operator

Add permissions to manage machineconfig resource #275

What type of PR is this?
/kind bug
What does this PR do / why we need it:
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #?
How to test changes / Special notes to the reviewer:
See https://github.com/argoproj-labs/argocd-operator/pull/275 for how to test.

/test unit

/retest

/retest

/retest

/retest

/refest

/retest

/retest

/retest

/retest

/retest

/retest


getByTag() Error

If a player isn't in a clan, the .getByTag() gives an error. In your code you are calling data.clan.tag, so it isn't resolving when the data.clan is undefiend.
https://github.com/VerZsuT/coc-game-api/blob/main/src/api/players/index.ts

A fast way to fix this is by changing line 16 in the linked file above to
clan: clanHelpers.createClanExtObject(token, data.clan && data.clan.tag || "", data.clan),


Share interpolation and minimize redundant calculations

🚀 Feature Proposal
In this case, I want to animate the 3 properties in a style object (position, transform and zIndex) for an <animated.div>. Given these properties share the same interpolation logics, I'd like to do something like this:
const SomeComponent = () => {
    const { scroll1, scroll2, transition } = useContext(SomeContext);
    const shared = interpolate([scroll1, scroll2, transition], (a, b, c) => {
        // Do some calculations based on 3 input values
        // and output final a single numeric value.
    });
    const style = {
        // Unset property when y <= 0, so that the browser won't promote it to render layer.
        transform: shared.interpolate(y => y > 0 ? `transform(0, ${y}px, 0)` : undefined),
        position: shared.interpolate(y => y > 0 ? 'relative' : undefined),
        zIndex: shared.interpolate(y => y > 0 ? 3 : undefined)
    };
    return (
        <animated.div style={style}>
            {someChildren}
        </animated.div>
    );
};

Although, there's the shared interpolator object, instead of calculate 1x time on each frame, the calculations are actually done 3x times (1x for each of the 3 props: position, transform and zIndex).
Motivation
Performance, simplify codes and minimize redundant calculations.
Example
Maybe something like the code example above, or even better:
const SomeComponent = () => {
    const { scroll1, scroll2, transition } = useContext(SomeContext);
    const shared = interpolate([scroll1, scroll2, transition], (a, b, c) => {
        // Do some calculations based on 3 input values
        // and output final a single numeric value.
    });
    // Unset property when y <= 0, so that the browser won't promote it to render layer.
    const style = shared.interpolate(y => y > 0 ? {
        transform: `transform(0, ${y}px, 0)`,
        position: 'relative',
        zIndex: 3
    }: undefined);
    return (
        <animated.div style={style}>
            {someChildren}
        </animated.div>
    );
};

Fixed in #808, which will be merged into v9 eventually.


MPQ Browser's additional features

In the New Matrix Eater, similar to Magos's editor, there is an MPQ Browser. This is a step forwards in replacing and assimilating the functionality of the Magos model editor and the MdlVis model editor, which is a long term goal for the Matrix Eater.
However, the MPQ Browser in the Matrix Eater always loads all MPQs at the same time. It lacks a "Load MPQ" feature, lacks "Copy Path to Clipboard", and lacks "Use as Texture". These features should be added.

With Retera Model Studio v0.03, the "Load MPQ" feature was basically solved because you can do that in the Data Sources panel in Preferences. "Copy Path to Clipboard" has been around for several months, and I just locally added "Use as Texture" which should become available soon.
So I am closing this issue as solved.


Let tests pass on Windows

LF/CRLF was wreaking havoc. Use gulp-eol to force all output to LF, and fix path separators in error output as needed.

I would think that the output already uses \n because it's defined in the host (https://github.com/ivogabe/gulp-typescript/blob/34248bc890b4ecba45e4e4e19fbbca7e8cda7324/lib/host.ts#L60). That would not cover isolatedModules, which uses the file based compiler instead of the project based compiler (in compiler.ts). Could you take a look at it? An option newLine exists in TypeScript, that might fix this for isolatedModules. I think it's better to fix this inside gulp-typescript than in the tests, as other users might benefit from this as well

Setting the newLine option for FileCompiler did the trick :thumbsup:

Thanks!


Add option for using handed-off segments only for query with lucene filter

Instead of exception, we can just ignore realtime / peons.

druid.query.useHandedOffSegmentsOnlyForLuceneIndex

Done


Architecture documentation

Basic architecture overview in markdown files in the source tree.
Fixes #111

Can one of the admins verify this patch?


Ruler handles display incorrectly in Chrome

This wasn't actually a Chrome vs Firefox issue. It only worked when the window size was exactly what my default window size is in Firefox.

This wasn't actually a Chrome vs Firefox issue. It only worked when the window size was exactly what my default window size is in Firefox.


SONAR-22353 Define the HorizontalPodAutoscaler for the app deployment

Small question, should we add the link to the official doc afterward ?

Yup, we discussed this, we are gonna update the doc when ready.


Merge changes from fundrx/echochamber

Separate out the doc changes (rebase once PR #7 is merged).


Client Allocation Request for: Chengdu 23mofang Biotechnology Co., Ltd.

Client Allocation Questions
Core Information

Name: Chengdu 23mofang Biotechnology Co., Ltd.
Website / Social Media: https://www.23mofang.com/
Region: North America
DataCap Requested: 30TiB
Addresses to be Notarized: f1paantyyxvw562mpaqe45dnjhxe6pypectod7rya
Notary Requested: ann-shin

Hi, nice to meet you. Thanks for your request. Can you kindly add more information here.
1.Are you representing for yourself or your company？
2.If you are representing for your company, Please give the following informations, duration of etablishment, number of employees, business scope, users volume, number of social media followers, data size to be stored, products or projects, and so on. If you are representing for yourself , please introduce yourself,such as number of social media followers, filecoin activities partipation with links, data size to be stored. Provide links to social media/news mentions.
3.The history working on IPFS / Filecoin, e.g. notable contributions to the community, type of engagement shown over time, etc.
Type, size, and source of the data you will be store on Filecoin,e.g. public data or private data, etc. Is there any sensitive or illegal content?
4.How do you intend to store the data on Filecoin, e.g. redundancy, location/miner preferences, etc
5.Have you already apply for DataCap to another notary, and whether it is accepted or rejected. Is there any reliable DataCap left?
6.Would you like to post real transactions on Github?

Hi, thanks for your reply. Please see our information below.
1.Are you representing for yourself or your company？
I'm representing our company, Chengdu 23mofang Biotechnology Co., Ltd.
2.If you are representing for your company, Please give the following informations, duration of establishment, number of employees, business scope, users volume, number of social media followers, data size to be stored, products or projects, and so on. If you are representing for yourself , please introduce yourself,such as number of social media followers, filecoin activities partipation with links, data size to be stored. Provide links to social media/news mentions.
Chengdu 23mofang Biotechnology Co., Ltd. was established in March 2015 with nearly 200 employees. We provide genetic testing services for Chinese people and carrying out life data analysis business. Relying on the Internet + genetic testing, our company builds a big database of life. We take the "digitizing life to benefit everyone" as our mission to build a trustworthy technology enterprise. The name, 23mofang (Mofang means Rubik's Cube in English ), derives from the fact that humans have 23 pairs of chromosomes, and "mofang" expresses polymorphism in genes. We now have about one million users and our data is more than 20PiB.
According to the "Analysis of China's Genetic Testing Industry 2018" released by Analysys（a third-party data institution in China）, 23mofang ranked first in the consumer-level genetic testing industry. At the same time, 23mofang was listed in the "50 Most Innovative Enterprises in China" released by Forbes China, and was evaluated by Forbes China as "gene testing innovator".
23mofang has accumulated 6 rounds of financing from investors including SoftBank China, Hanwang Technology, Jingwei China, and CD Capital, etc. It is the enterprise with the largest financing scale in the domestic consumption-level genetic testing industry.
We have a self-established gene testing center, which has been certified by the former National Health and Family Planning Commission and conforms to the standards of medical clinical testing institute. 23mofang also cooperates with the Ministry of Education's Key Laboratory of Modern Anthropology of Fudan University, Medical Genetics Center of the First Affiliated Hospital of Army Military Medical University, Kunming Institute of Zoology . Cas and other institutions to carry out scientific research.
Wechat official account: 23魔方（more than one million followers）
3.The history working on IPFS / Filecoin, e.g. notable contributions to the community, type of engagement shown over time, etc.
Type, size, and source of the data you will be store on Filecoin,e.g. public data or private data, etc. Is there any sensitive or illegal content?
We don't have any notable contributions to the community yet.  We want to store about 30TiB at this time for a small scale test and all these data are from genetic test samples, analysis results and genetic source data. They are all private data and can not be public with no sensitive/illegal content.
4.How do you intend to store the data on Filecoin, e.g. redundancy, location/miner preferences, etc
We want to store data in China with 3 copies. We prefer those miners with active working, high ranking, low cost.
5.Have you already apply for DataCap to another notary, and whether it is accepted or rejected. Is there any reliable DataCap left?
Yes, we have apply to another one notary before this application but its processing is slow.
6.Would you like to post real transactions on Github?
Yes, of course.

Your organization is not in North America。
According to our allocation strategy(https://github.com/filecoin-project/notary-governance/issues/27)，please wait for further notice after  7 days.

OK, @XnMatrixSV if more information is required after 7 days, please tell us at any time.
Besides, we'd like to say that 23 Mofang ranks first in the consumer genetic testing industry and is committed to building the largest life database in China. By collecting saliva samples, users can perform ancestry analysis, genetic risk, genetic traits, genetic variation carrying, nutritional needs, drug response, sports health, skin management and other hundreds of genetic tests. These real data, including genetic test samples, analysis results and genetic source data, constitute a huge gene database.
In short, through genetic testing, 23 Mofang helps people better understand themselves and targeted disease prevention, which is conducive to improving the human health index. At the same time,  the huge testing and analysis data of 23 Mofang has also greatly promoted the development of medical research and genetic science research.


What's the user name and password for the demo?

http://serenity.is/demo/     the user name and password for the demo?
http://serenedemo.azurewebsites.net/      the user name and password for the demo?

Hi @ghd258
Username   "Admin"
Password  "Serenity"
for Both the links which are mentioned on the login page.
Regards,
Srinivas

Please make sure to look through the old issues before posting questions. This has been asked a number of times plus the placeholders for Login page do state the default name and password on them.


Vulnerability roundup 93: sharutils-4.15.2: 1 advisory [7.8]

search, files

[ ] CVE-2018-1000097 CVSSv3=7.8 (nixos-20.03)

Scanned versions: nixos-20.03: 0d0660fde3b.

20.03 is Frozen and EOL.
As such, issue is closed.


Add WebGL support to web-sys

This is a tracking issue for adding support for the WebGL API to the web-sys crate.
General info on WebGL: https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API
How to add support for new Web APIs to web-sys: https://rustwasm.github.io/wasm-bindgen/web-sys/supporting-more-web-apis.html
Interfaces
Here is a list of interfaces we need to support:

[ ] WebGLRenderingContext
[ ] WebGLActiveInfo
[ ] WebGLBuffer
[ ] WebGLContextEvent
[ ] WebGLFramebuffer
[ ] WebGLProgram
[ ] WebGLRenderbuffer
[ ] WebGLShader
[ ] WebGLShaderPrecisionFormat
[ ] WebGLTexture
[ ] WebGLUniformLocation
[ ] ANGLE_instanced_arrays
[ ] EXT_blend_minmax
[ ] EXT_color_buffer_float
[ ] EXT_color_buffer_half_float
[ ] EXT_disjoint_timer_query
[ ] EXT_frag_depth
[ ] EXT_sRGB
[ ] EXT_shader_texture_lod
[ ] EXT_texture_filter_anisotropic
[ ] OES_element_index_uint
[ ] OES_standard_derivatives
[ ] OES_texture_float
[ ] OES_texture_float_linear
[ ] OES_texture_half_float
[ ] OES_texture_half_float_linear
[ ] OES_vertex_array_object
[ ] WEBGL_color_buffer_float
[ ] WEBGL_compressed_texture_astc
[ ] WEBGL_compressed_texture_atc
[ ] WEBGL_compressed_texture_etc
[ ] WEBGL_compressed_texture_etc1
[ ] WEBGL_compressed_texture_pvrtc
[ ] WEBGL_compressed_texture_s3tc
[ ] WEBGL_compressed_texture_s3tc_srgb
[ ] WEBGL_debug_renderer_info
[ ] WEBGL_debug_shaders
[ ] WEBGL_depth_texture
[ ] WEBGL_draw_buffers
[ ] WEBGL_lose_context

Example

[ ] Add an example to examples/ that shows off working with WebGL

@fitzgen if it's a helpful resource at all I've been working on a wasm-bindgen + WebGL visualizer for meshes / rigs that I'm exporting from Blender
https://github.com/chinedufn/blender-exporter/tree/master/mesh-visualizer
https://github.com/chinedufn/blender-exporter#running-the-mesh-visualizer-locally
Would also be happy to work on a more stripped down example if no one else is already on that.
Do we already have an idea for an example in mind?

I've been working on a wasm-bindgen + WebGL visualizer for meshes / rigs that I'm exporting from Blender

Neat!

Do we already have an idea for an example in mind?

I don't. I'm hoping for something that is pretty self contained, since examples shouldn't require a lot of unrelated context. Maybe a mandelbrot or julia set visualization? Even just drawing a triangle could work.

Gotcha!
I think the goal would be to demonstrate the following in the simplest way possible (open to other goals!):

Passing data to the GPU
Linking a shader program
A request animation frame render loop

A triangle would sure be simple and it would hit on 1 and 2, but not 3.
So one step up from that that would also hit on 3 might be rendering a cube with lighting (just so that you can tell that it's a cube).
?

We could also just make the triangle spin. Lighting requires a little bit more context and background knowledge, I think.

I've got my own WebGL-based project that would benefit greatly from having proper WebGL bindings instead of the ad-hoc stuff I've cobbled together. I could probably contribute a few tests to get things started.

Great idea on just making a triangle spin. Perfect! I'll try to make some time for this this weekend but not 100% certain yet.
One question:
Is it possible to depend on the web-sys crate in an example right now? Would be great to make separate PRs as I go to add the bits of the API that I need instead of hard coding the externs
Sorry if that's a silly question.. still learning!

@chinedufn Although web-sys is not published to crates.io yet, you can use a relative dependency in examples/webgl/Cargo.toml:
[dependencies]
web-sys = { path = "../../crates/web-sys" }

Note that we may be putting the cart ahead of the horse by working on an example before we've enabled bindings for the WebGL interfaces, however :)

Note that we may be putting the cart ahead of the horse by working on an example before we've enabled bindings for the WebGL interfaces, however :)

Yeah; I'm concerned about that as well. From the bit of testing I just did, it looks like getting the full bindings supported may be non-trivial; these bindings are an order of magnitude larger than the currently enabled ones, and not everything is showing up in the docs, so it seems likely that we'll have to add some features to the webidl crate.

Yep, that's expected. The plan is to drive forward the wasm-bindgen-webidl crate based on what we actually need to generate bindings for these APIs.

I've got an extremely minimal test in my branch; it basically just creates a WebGLRenderingContext and passes it to a function that does nothing with it. It seems like getting code generation working for the constants and the WebGLContext.clear* functions would be a reasonable starting point. I'm not familiar enough with the WebIDL stuff yet to know where to start, but I'll poke around and see if I can figure something out.

@blm768 just a note: rather than modifying .webidl files, we should be extending support in the webidl frontend crate.
In general, we are happy to make small incremental progress, enabling .webidl files if they don't break the crate, even if we aren't generating bindings for all the things described therein yet.

Ah so my thinking was to just hard code the APIs and replace them with web-sys as we had then but cool waiting works just fine too!!

rather than modifying .webidl files, we should be extending support in the webidl frontend crate.

That makes sense. My modifications were just a quick hack to keep errors in the generated bindings from terminating the test, but now that I've got a better handle on what's going on, I'll look into implementing support for [NoInterfaceObject] before I put these changes into a PR.

I think we are ready for a WebGL example if anyone was waiting for web-sys to mature a little more before trying to create an example.

I've got a slightly larger project that I think I could pare down into a working demo.

This has now been done, thanks @blm768!


Viessman Vitobloc 200

initial commit

pending status test comment (please ignore)

Tanya don't look just yet

Need help with the new modbus connection, resolution part and checking for data types in different groups


feature: Improve WezTerm themes

Did you check the docs?

[X] I have read all the tokyonight.nvim docs

Is your feature request related to a problem? Please describe.
WezTerm themes supports not fancy tabs
Looks like this

In case of tokyonight it's not themed

Describe the solution you'd like
This is Catppuccin implementation for the reference:
https://github.com/catppuccin/wezterm/blob/main/dist/catppuccin-frappe.toml
Describe alternatives you've considered
I stick with Catppuccin for now
Additional context
Thanks for mentioning WezTerm in Twitter.
I like it so far. Especially after enabling CTRL-hjkl to navigate between term and neovim splits using https://github.com/numToStr/Navigator.nvim

I actually have some updates of the wezterm theme locally. Will push the changes soon.

Added some styles, but the colorscheme colors only work for the retro tab bar, not the fancy one (see https://github.com/wez/wezterm/issues/2615)

Thanks a lot for the update.


Freebsd unix socket support

This pull req ensures it is actually possible to connect() to unix sockets on FreeBSD without having to add a dummy char to the path. The same applies for bind().

Completed in #263 and #264. Thanks!


init-CTDirect

[x] Generic initialisation  as function of time
[x] Default initialisation, actually 1.1 for the control and the state
[ ] Initialisation of the co-state variable ?

The only change is when explicitely passing an init to solve().

old syntax was to pass a single vector containing all constant values

x_init = [1.0, 0.1]
u_init = [0.5]
v_init = [2]
solve(..., init=[x_init, u_init, v_init], ...)

new syntax passes an OptimalControlInit

x_init = [1.0, 0.1]
u_init = [0.5]
v_init = [2]
solve(..., OptimalControlInit(x_init, u_init, v_init), ...)

in addition to constant intialization we can now have a warm start

sol1 = solve(...)
sol2 = solve(..., init=OptimalControlInit(sol1), ...)

As per our discussion I'll improve the 'constant init' Constructor a bit by making all arguments optional (v_init is optional already) and merge the () constructor with it.
Release will follow.

Put aside multipliers initialization for now due to the questionable benefits observed with Bocop2.


DV_GlueJobV3_Added

@madhu-k-sr2 Terraform plan evaluation detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform - please contact #ask-modernisation-platform for assistance

@madhu-k-sr2 Terraform plan evaluation detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform - please contact #ask-modernisation-platform for assistance

@madhu-k-sr2 Terraform plan evaluation detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform - please contact #ask-modernisation-platform for assistance


Support in SM Globalnet for dual-stack clusters

Partially fixes: https://github.com/submariner-io/submariner/issues/1739
Signed-off-by: Sridhar Gaddam<EMAIL_ADDRESS>

Sample output from a KIND dual-stack setup:
[sgaddam@localhost submariner]$ subctl show all
Cluster "cluster1"
 ✓ Detecting broker(s)
NAMESPACE               NAME                COMPONENTS     GLOBALNET   GLOBALNET CIDR   DEFAULT GLOBALNET SIZE   DEFAULT DOMAINS
submariner-k8s-broker   submariner-broker   connectivity   yes         <IP_ADDRESS>/8      65536

 ✓ Showing Connections
GATEWAY            CLUSTER    REMOTE IP    NAT   CABLE DRIVER   SUBNETS          STATUS      RTT avg.
cluster2-worker2   cluster2   <IP_ADDRESS>   no    libreswan      <IP_ADDRESS>/24   connected   483.251µs

 ✓ Showing Endpoints
CLUSTER    ENDPOINT IP   PUBLIC IP         CABLE DRIVER   TYPE
cluster1   <IP_ADDRESS>    <IP_ADDRESS>   libreswan      local
cluster2   <IP_ADDRESS>    <IP_ADDRESS>   libreswan      remote

 ✓ Showing Gateways
NODE              HA STATUS   SUMMARY
cluster1-worker   active      All connections (1) are established

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  kindnet
        Service CIDRs:   [<IP_ADDRESS>/16,fd00:1234::/112]
        Cluster CIDRs:   [<IP_ADDRESS>/16,fd00:200::/48]
        Global CIDR:     <IP_ADDRESS>/24

 ✓ Showing versions
COMPONENT               REPOSITORY           VERSION
submariner-gateway      localhost:5000       local
submariner-routeagent   localhost:5000       local
submariner-globalnet    localhost:5000       local
submariner-operator     quay.io/submariner   devel

All e2e Globalnet tests are passing with this PR.
[dataplane] Gateway status reporting when a gateway node is configured should correctly report its status and connection information
github.com/submariner-io/submariner@v0.15.0-m3/test/e2e/dataplane/gateway_status.go:38
  STEP: Creating namespace objects with basename "dataplane-gateway-status" @ 03/02/23 12:57:46.782
  STEP: Generated namespace "e2e-tests-dataplane-gateway-status-qkqkx" in cluster "cluster1" to execute the tests in @ 03/02/23 12:57:46.785
  STEP: Creating namespace "e2e-tests-dataplane-gateway-status-qkqkx" in cluster "cluster2" @ 03/02/23 12:57:46.785
  STEP: Ensuring that only one gateway reports as active on "cluster1" @ 03/02/23 12:57:46.79
  STEP: Ensuring that gateway "cluster1-worker" reports connection information for cluster "cluster2" @ 03/02/23 12:57:46.797
  STEP: Deleting namespace "e2e-tests-dataplane-gateway-status-qkqkx" on cluster "cluster1" @ 03/02/23 12:57:46.801
  STEP: Deleting namespace "e2e-tests-dataplane-gateway-status-qkqkx" on cluster "cluster2" @ 03/02/23 12:57:46.805
• [0.027 seconds]
------------------------------
SSSSSSSS
------------------------------
[SynchronizedAfterSuite]
github.com/submariner-io/shipyard@v0.15.0-m3/test/e2e/e2e.go:53
[SynchronizedAfterSuite] PASSED [0.000 seconds]
------------------------------

Ran 13 of 44 Specs in 279.970 seconds
SUCCESS! -- 13 Passed | 0 Failed | 0 Pending | 31 Skipped

When creating a service with ipFamilyPolicy configured as PreferDualStack, Globalnet controller internally creates an SingleStack service and the same can be accessed from remote clusters without any issues.
[sgaddam@localhost submariner]$ kubectl get svc nginx -oyaml
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: "2023-03-02T16:19:50Z"
  labels:
    app: nginx
  name: nginx
  namespace: default
  resourceVersion: "124224"
  uid: 712239f9-2afe-4be3-9d6a-11873131c3e5
spec:
  clusterIP: <IP_ADDRESS>
  clusterIPs:
  - <IP_ADDRESS>
  - fd00:1234::a31f
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  - IPv6
  ipFamilyPolicy: PreferDualStack
  ports:
  - port: 8080
    protocol: TCP
    targetPort: 8080
  selector:
    app: nginx
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

[sgaddam@localhost submariner]$ kubectl get svc
NAME                                          TYPE        CLUSTER-IP       EXTERNAL-IP     PORT(S)    AGE
kubernetes                                    ClusterIP   <IP_ADDRESS>       <none>          443/TCP    23h
nginx                                         ClusterIP   <IP_ADDRESS>     <none>          8080/TCP   133m
submariner-lpq6zr4tl4o5qvrv2t7o3l3gawkagast   ClusterIP   <IP_ADDRESS>   <IP_ADDRESS>   8080/TCP   131m

[sgaddam@localhost submariner]$ kubectl get svc submariner-lpq6zr4tl4o5qvrv2t7o3l3gawkagast -oyaml
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: "2023-03-02T16:22:32Z"
  finalizers:
  - submariner.io/globalnet-internal-service
  labels:
    submariner.io/exportedServiceRef: nginx
  name: submariner-lpq6zr4tl4o5qvrv2t7o3l3gawkagast
  namespace: default
  resourceVersion: "124324"
  uid: 5de2d2de-a7e3-46bf-8d73-84ff77d8e653
spec:
  clusterIP: <IP_ADDRESS>
  clusterIPs:
  - <IP_ADDRESS>
  externalIPs:
  - <IP_ADDRESS>
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - port: 8080
    protocol: TCP
    targetPort: 8080
  selector:
    app: nginx
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

Submariner Lighthouse e2e test results:
subctl verify --only service-discovery --context cluster2 --tocontext cluster1 --verbose
...
...
------------------------------
[SynchronizedAfterSuite]
github.com/submariner-io/shipyard@v0.15.0-m3/test/e2e/e2e.go:53
[SynchronizedAfterSuite] PASSED [0.000 seconds]
------------------------------

Ran 13 of 44 Specs in 474.488 seconds
SUCCESS! -- 13 Passed | 0 Failed | 0 Pending | 31 Skipped

I verified the Lighthouse use-cases in a non-Globalnet deployment as well and see that they are working fine. Basically, Lighthouse, while creating the ServiceImport object uses the service.spec.clusterIP which points to the IPv4 address even when the service has both IPv4 and IPv6 addresses. Because of this, even in a dual-stack cluster, the Lighthouse use-cases continue to work normally.
[sgaddam@localhost submariner]$ kubectl get svc nginx -oyaml
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: "2023-03-03T09:47:49Z"
  labels:
    app: nginx
  name: nginx
  namespace: default
  resourceVersion: "11439"
  uid: 521fc913-0d7c-4062-ac2a-ed67542f427c
spec:
  clusterIP: <IP_ADDRESS>
  clusterIPs:
  - <IP_ADDRESS>
  - fd00:1234::1493
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  - IPv6
  ipFamilyPolicy: PreferDualStack
  ports:
  - port: 8080
    protocol: TCP
    targetPort: 8080
  selector:
    app: nginx
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}
[sgaddam@localhost submariner]$

[sgaddam@localhost submariner]$ kubectl get serviceimport -n submariner-operator nginx-default-cluster1 -oyaml
apiVersion: multicluster.x-k8s.io/v1alpha1
kind: ServiceImport
metadata:
  creationTimestamp: "2023-03-03T09:51:40Z"
  generation: 1
  labels:
    lighthouse.submariner.io/sourceNamespace: default
    multicluster.kubernetes.io/service-name: nginx
    multicluster.kubernetes.io/source-cluster: cluster1
  name: nginx-default-cluster1
  namespace: submariner-operator
  resourceVersion: "11566"
  uid: 50cc15a7-c838-40ac-a940-6ab261f758e5
spec:
  ips:
  - <IP_ADDRESS>
  ports:
  - port: 8080
    protocol: TCP
  sessionAffinityConfig: {}
  type: ClusterSetIP

[sgaddam@localhost submariner]$ subctl show all
Cluster "cluster1"
 ✓ Detecting broker(s)
NAMESPACE               NAME                COMPONENTS                        GLOBALNET   GLOBALNET CIDR   DEFAULT GLOBALNET SIZE   DEFAULT DOMAINS
submariner-k8s-broker   submariner-broker   service-discovery, connectivity   no          <IP_ADDRESS>/8      65536

 ✓ Showing Connections
GATEWAY           CLUSTER    REMOTE IP    NAT   CABLE DRIVER   SUBNETS                        STATUS      RTT avg.
cluster2-worker   cluster2   <IP_ADDRESS>   no    libreswan      <IP_ADDRESS>/16, <IP_ADDRESS>/16   connected   512.992µs

 ✓ Showing Endpoints
CLUSTER    ENDPOINT IP   PUBLIC IP         CABLE DRIVER   TYPE
cluster1   <IP_ADDRESS>    <IP_ADDRESS>   libreswan      local
cluster2   <IP_ADDRESS>    <IP_ADDRESS>   libreswan      remote

 ✓ Showing Gateways
NODE              HA STATUS   SUMMARY
cluster1-worker   active      All connections (1) are established

 ✓ Showing Network details
    Discovered network details via Submariner:
        Network plugin:  kindnet
        Service CIDRs:   [<IP_ADDRESS>/16,fd00:1234::/112]
        Cluster CIDRs:   [<IP_ADDRESS>/16,fd00:200::/48]

 ✓ Showing versions
COMPONENT                       REPOSITORY           VERSION
submariner-gateway              quay.io/submariner   devel
submariner-routeagent           quay.io/submariner   devel
submariner-operator             quay.io/submariner   devel
submariner-lighthouse-agent     quay.io/submariner   devel
submariner-lighthouse-coredns   quay.io/submariner   devel


How to get Project Hash if service is not yet deployed?

Sorry for asking question here.
I have cloudbuild.yaml file which builds an image and deploys it on Cloud Run, how do you figure out CLOUD_RUN_PROJECT_HASH if service is not yet deployed?

Sadly you can't. The only way to do this is to make runsd also capture ingress traffic, and look at the host header but I decided not to implement this as it won't work well for apps that hardcore port 8080.

I am in the exact same boat as @madbbb :(

Nothing we can do in this repo.
If you wanna automate deployment of runsd, you can deploy an unused placeholder service to that project and parse the project's hash for now.
We might add deterministic URLs to Cloud Run at some point later.

Deploy an example service (Cloud Run offers an example image for you in the Cloud Console) and copy the hash from there, and delete the service.

For anyone like me that doesn't know the project hash is project-wide: It is project wide! So just deploy any service once, copy the hash and delete the service again. You can use the same hash for all services. 👍

@ahmetb this fresh comment of @steinroe about hash was really helpful, and it occurred to me: why not generate this hash when somebody enables Cloud Run Admin API for the GCP project?

@ahmetb this fresh comment of @steinroe about hash was really helpful, and it occurred to me: why not generate this hash when somebody enables Cloud Run Admin API for the GCP project?

why not generate this hash when somebody enables Cloud Run Admin API for the GCP project?

FWIW I locked this conversation because this repository is not the place to make Cloud Run feature requests.