Implement ensure => $version for pacemaker and corosync package

Instead of just installing the corosync and pacemaker version in the present version, sometimes you need to install a specific version and/or not install by it puppet at all.

This adds interface complexity that I'm not especially fond of.
How would you feel about
class { '::corosync':
  packages => {
    'corosync' => { 'ensure' => 'latest' },
    'pacemaker' => true,
    'this-will-throw-errors' => 'boo'
  },
  # more parameters...
}

The parameter becomes more unwieldy, but we save on the number of parameters that share repetitive documentation. (My grasp on module best practices is somewhat tenuous, I might add.)

This needs a squash. I'm okay with the current implementation, though I am grooving on what @ffrank is saying. I think if we think we're ever going to go beyond those two packages, we should do @ffrank's idea. If we're pretty sure we're gonna keep it to just pacemaker and corosync then I think this implementation is ok.

Agree, three extra parameters are just acceptable.

Well, currently I don't longer have any interest in setting the version either. Thanks for Feedback.

If it's all right for you @stefanandres I will keep this open. It is a valuable feature and I'd like to see it upstream.

Sure, I can also rebase it. Will probably do that when I have free 5 minutes for that. :-)

Okay, it's rebased now.

Neat!
As it stand, this is a breaking change. Should we make it so that the old API is still supported, and throw errors when things are mixed nonsensically? I'd be fine with also deprecating the packages parameter.
Finally, tests for all these changes will be needed. Do you think that you could add those? We do this ourselves if necessary.

Taking over from Stefan since he's a tad busy right now. I added deprecation warnings as suggested and will add spec tests next (multiple commits to keep track of things for now; we'll squash them again once everything's ready and tested).

Alright, all done. I omitted tests for the packages getting installed now, since none existed before our patch. I hope that's ok.

Thanks so much @jgrassler. Looks very good, just left two inline notes.

Alright, I fixed the missing else branches and added tests for all combinations of the new package parameters. Should be ready for merge now.

It is! Thank you both for the contribution!


Dynamic imports

Do they work?
Maybe I don't want Firebase imported until they actually click the button.
let firebase = null;
function SigninButton() {
  return (
    <button
      onClick={async () => {
        if (!firebase) {
          firebase = await import("../firebase");
        }
        firebase.signInWithPopup();
      }}
    >
      Log in
    </button>
  );
}

Do we want our own React.lazy that code splits and server renders?
import { lazy } from "@remix-run/react";

let HugeModal = lazy(
  () => import("../HugeModal"),
  () => <LoadingSkeleton />
);

<HugeModal/>

Sometimes its perf reason (loading when its needed), sometimes its just a must.
I struggle to implement Leaflet maps in Remix now, I definitely need something like next's dynamic() or react lazy, otherwise its hacking. Some libraries are unsafely trying to access DOM...

Sometimes its perf reason (loading when its needed), sometimes its just a must.
I struggle to implement Leaflet maps in Remix now, I definitely need something like next's dynamic() or react lazy, otherwise its hacking. Some libraries are unsafely trying to access DOM...

You can currently do Client Only dynamic component imports with the following pattern:
import { Suspense, lazy, useEffect, useState } from "react";
import type { ReactNode } from "react";

let LazyImported = lazy(() => import("./lazy-comp"));

export function ClientOnly({ children }: { children: ReactNode }) {
  let [mounted, setMounted] = useState(false);
  useEffect(() => {
    setMounted(true);
  }, []);
  return mounted ? <>{children}</> : null;
}

export default RouteComponent() {
  return (

YAY!

    <ClientOnly>
      <Suspense fallback="">
        <LazyImported />
      </Suspense>
    </ClientOnly>
  );
}

Thanks @jacob-ebey , it work indeed, but its a hacky way. I assume it will be gone when React 18 and SSR suspense is shipped.
What is worth to mention IMO is

Add this to the documentation. There are plenty of examples how to do it in Next and Remix is sort of more high level Next alternative. I think problems with SSR/hydration is one of the biggest challenges for devs
Dynamic imports require TS to set a valid module flag in tsconfig. For me it works with es2022 but I can't be sure if I'm not breaking Remix internal builds right now

Regarding initial issue by Ryan, my opinion is to use native React way (lazy and suspense) without re-exporting it, but ensure internal build system is configured well to support it

Dynamic imports require TS to set a valid module flag in tsconfig

Dynamic imports seem to work just fine with "module": "es6" in tsconfig even though TS complains about the availability.
Older browsers probably break entirely but that's to be expected with ES6.
Would be nice if there was some sort of official guidance on the subject. I was able to implement a lazy loading admin overlay, but I'm a bit afraid for it's longevity.

tsconfig isn't really used and there's nothing you configure there that will break how remix complies your code currently. Don't worry about changing it, especially when it's to include a config for language settings you are trying to use such as dynamic import. Anything you can do today such as putting suspense behind a client only won't break in the future as react is only adding the ability for the server to use this, not removing anything. Don't worry about "longevity" in terms of things braking around the pattern I've outlined above.
As for a "dynamic" component, React.lazy will essentially become this when 18 drops, but I'm skeptical about implementing it today as every version of it will be a combo of the compiler turning async imports into sync imports for the server, and "hacks" for the client around delaying hydration until these chunks have loaded to avoid hydration issues. This means we'd have to expose some sort of "waitTillDynamicHasLoaded()" you have to call in your entry.client, or hide this away very hacky under the hood. I don't think this is worth it currently.

Thanks for the clarification! I can get rid of // @ts-expect-error comments by just switching the module flag. I had gotten a bit of misinformation from somewhere, thinking things would break in the future.


Gooey-fied script that has a dependency on another script with an @Gooey annotation causes infinite setup-screen workflow

[X] OS - Fedora 29 x86_64
[X] Python Version - Python 3.7.3 (From miniconda)
[X] Gooey Version - 1.0.2
[X] When Gooey-fied script imports a value from another script that also has an @Gooey annotation anywhere in that script, the GUI in the first script will endlessly loop back to the setup page when "next" is pressed, and never run.

[X] Expected Behavior: When python MainScript.py is run, it will take the user-input "ResourceNumber", and print the corresponding value from the list imported from "ResourceScript".
[X] Actual Behavior: The Gooey setup screen for MainScript.py's argument displays. When a value is entered and "next" is pressed, the window switches to the "running" screen, but then another setup screen for MainScript.py appears. If you enter an argument and hit "next", it changes to an additional "running" screen, and another setup screen appears. I think you can do this endlessly.

[X] A minimal code example:

#MainScript.py
import argparse
from gooey import Gooey
from ResourceScript import ConstantArray

def get_resource(num):
    return ConstantArray[num]

@Gooey
def main():
    parser = argparse.ArgumentParser()
    parser.add_argument("ResourceNumber")
    args = parser.parse_args()

    print(get_resource(int(args.ResourceNumber)))

if __name__=="__main__":
    main()

#ResourceScript.py
import argparse
from gooey import Gooey

ConstantArray = [
        'foo',
        'bar',
        'baz',
        'gat'
]

# Doesn't matter what this does, as long as there's another Gooey-annotated function
@Gooey
def main():
    parser = arparse.ArgumentParser()
    parser.add_argument("echo")
    args = parser.parse_args()

    print(parser.echo)
    for c in ConstantArray:
        print(c)

if __name__=="__main__":
    main()

Save the two files MainScript.py and ResourceScript.py in the same directory, then run python MainScript.py. You will see the behavior described above. My real-world encounter with this was a little different, but this seems to reproduce it. I haven't dug into Gooey's code at all, although I imagine it has something to do with how the annotation is handled.

Neat.
The root of the problem is due to an interaction (a) the eager evaluation or decorators, and (b) the fact that Gooey and Argparse read from the global mutable state that is sys.argv.
More background than is probably wanted, but when Gooey invokes your program, here's the flow:

python begins parsing MainScript.py
hops into ResourceScript.py while resolving imports
Gooey decorator gets evaluated
The internal IGNORE_GOOEY flag is popped out of sys.argv so that it doesn't show up in your code
parser returns to MainScript.py
main's Gooey decorator gets evaluated
It finds no IGNORE_GOOEY flag (removed in step 4), and thus thinks it needs to show the UI again

Thus you get an endless stream of initial Gooey configuration screens.
This could potentially be worked around in Gooey, but, the lame answer is that hesitant to do so as, this is pretty niche (first time it has come up) and it would require some (more) crufty global state tracking to work around the already global modification of sys.argv (forced upon us by Argparse!).
The good news:
You're not outta luck, though! ^_^
An easy fix to your specific problem would be to just "manually" decorate your non-main functions after the if __name__ == '__main__' guards. This prevents them from being eagerly evaluated and the problem goes away!
Here's an example:
main.py
import argparse
from gooey import Gooey
from examples.issue458.resource import ConstantArray

def get_resource(num):
    return ConstantArray[num]

@Gooey
def main():
    parser = argparse.ArgumentParser()
    parser.add_argument("ResourceNumber")
    args = parser.parse_args()

    print(get_resource(int(args.ResourceNumber)))

if __name__ == "__main__":
    main()

resource.py
import argparse
from gooey import Gooey

ConstantArray = [
        'foo',
        'bar',
        'baz',
        'gat'
]

def fooobar():
    parser = argparse.ArgumentParser()
    parser.add_argument("echo", help="sup fam")
    args = parser.parse_args()

    print(args)

if __name__ == "__main__":
    Gooey(fooobar)()   # <-- manually applying the decorator

This lets you run main without endless Gooey instances and still run other things in your project directly as well.


 Also, refactored
it to only calculate length of the Enum (n) once in the function.

Coverage remained the same at 100.0% when pulling 216fc9913721f912e6b98fd9186d6a054771b179 on feat/median into 0417edef7edf182971da743ff3923159804a7830 on master.


Request to update mull browser icon

About this discussion
The mull browser icon has changed request to update the icon in lawnicons.

Done. Thanks!


Add X41 team to the setec ACL

Additional Description:
X41 team is working on fixing OSS-Fuzz bugs and need access to the setec repo for PRs that may be a security vulnerability.
Risk Level: Low
Testing: N/A
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A
Signed-off-by: Yan Avlasov<EMAIL_ADDRESS>

/retest

Just curious about that could we have a list to see the OSS-Fuzz bug?


TS enhancement for BIG-IP as pull consumer for 3rd party integrations

We are looking at collecting basic Stats from the BIG-IP related to the VIP and Pool as we see on the BIG-IP.

From the TS output see the following I see only bitsIn and bitsOut (no Packets, Connections, or Request information)
[
   {
      "virtualServers":{
         "/Dynamic/DemoApp1/serviceMain":{
            "clientside.bitsIn":8867392,
            "clientside.bitsOut":18203840,
            "clientside.curConns":0,
            "destination":"<IP_ADDRESS>:80",
            "mr.msgIn":0,
            "mr.msgOut":0,
            "mr.reqIn":0,
            "mr.reqOut":0,
            "mr.respIn":0,
            "mr.respOut":0,
            "availabilityState":"available",
            "enabledState":"enabled",
            "status.statusReason":"The virtual server is available",
            "name":"/Dynamic/DemoApp1/serviceMain",
            "ipProtocol":"tcp",
            "mask":"<IP_ADDRESS>",
            "pool":"/Dynamic/DemoApp1/web_pool",
            "profiles":{
               "/Common/f5-tcp-progressive":{
                  "name":"/Common/f5-tcp-progressive"
               },
               "/Common/http":{
                  "name":"/Common/http"
               }
            }
         }
      },
      "pools":{
         "/Dynamic/DemoApp1/web_pool":{
            "activeMemberCnt":18,
            "curPriogrp":0,
            "highestPriogrp":0,
            "lowestPriogrp":0,
            "mr.msgIn":0,
            "mr.msgOut":0,
            "mr.reqIn":0,
            "mr.reqOut":0,
            "mr.respIn":0,
            "mr.respOut":0,
            "serverside.bitsIn":7705920,
            "serverside.bitsOut":15016032,
            "serverside.curConns":0,
            "availabilityState":"available",
            "enabledState":"enabled",
            "status.statusReason":"The pool is available",
            "name":"/Dynamic/DemoApp1/web_pool",
            "members":{
               "/Dynamic/<IP_ADDRESS>:80":{
                  "addr":"<IP_ADDRESS>",
                  "monitorStatus":"up",
                  "mr.msgIn":0,
                  "mr.msgOut":0,
                  "mr.reqIn":0,
                  "mr.reqOut":0,
                  "mr.respIn":0,
                  "mr.respOut":0,
                  "port":80,
                  "serverside.bitsIn":419520,
                  "serverside.bitsOut":817568,
                  "serverside.curConns":0,
                  "availabilityState":"available",
                  "enabledState":"enabled",
                  "status.statusReason":"Pool member is available"
               },
             }
         }
      }
   }
]

Can information related to Packets, Connections, and Request information be added. The information available by default when BIG-IP is a pull consumer is very limited.

Created AUTOTOOL-2056 to track this in the backlog.

This has been resolved as part of the 1.17.0 release.

This has been resolved as part of the 1.17.0 release.


Fix meta.tests system

This will be easier reviewed commit-by-commit, I tried to add in useful commit messages.
I think this should handle the concerns raised at https://github.com/NixOS/nixpkgs/pull/44439 and https://github.com/NixOS/nixpkgs/issues/50230.
For those who want to read only the commit messages, here they are:
tests: refactor to carry the package set as an argument
This way, the package set will be possible to pass without re-importing
all the time
tests: split into a separate all-tests.nix file
This will make the list much easier to re-use, eg. for nixosTests
The drawback is that this approaches makes the
nix-build release.nix -A tests.opensmtpd.x86_64-linux

command about twice as slow (3s to 6s): it now has to evaluate nixpkgs
once for each architecture, instead of just having the hardcoded list of
tests that allowed to say “ok just evaluate for x86_64-linux”.
On the other hand, complete evaluation of release.nix should be much
faster because we no longer import nixpkgs for each test: testing with
the following command went from 30s to 18s, and that's just for a few
tests.
time nix-instantiate --eval --strict nixos/release.nix -A tests.nat

I initially wanted to test on the whole release.nix, but there are too
many broken tests and it takes too long to eval them all, especially
compared to the fact that the current implementation breaks some setup.
Given developers can just nix-build nixos/tests/my-test.nix, it sounds
like an overall win.
tests: disable some broken tests and/or restrict to x86_64
meta.tests: drop meta.needsVMSupport
Its job is already handled by requiredSystemFeatures
meta.tests: rename into passthru.tests
Nix currently rejects derivations in meta values. This works around
that limitation by using passthru instead.
Closes #50230
nixosTests: use the newly-extracted all-tests.nix

@timokau The meta -> passthru is not that urgent: currently the meta.tests lines are commented-out. Also, this is fixing the issues @Ericson2314 mentioned, and I don't think we'd have merged the initial PR if we had known them?
Then I must say I'm currently basically thinking “well, this already 3 months, can wait 1 more”, though I'm aware this will merge-conflict as soon as someone adds a test.
Anyway, I can split the “drop meta.needsVMSupport” and “rename to passthru.tests” commits in a separate PR if you'd rather, I was just thinking it'd be better to have nothing than a broken setup, in part because it encourages people to actually review it instead of thinking something along the lines of “well, it works good enough, there are more pressing PRs” :)
BTW let's check whether it actually works with ofborg.
@GrahamcOfBorg build opensmtpd.tests

Success on x86_64-linux (full log)
Attempted: opensmtpd.tests
Partial log (click to expand)
client: running command: sync
client: exit status 0
test script finished in 41.94s
cleaning up
killing smtp1 (pid 597)
killing smtp2 (pid 609)
killing client (pid 621)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/k46cncv2yvkk1r1lifwkjs9pyxv7qj3h-vm-test-run-opensmtpd

Success on aarch64-linux (full log)
Attempted: opensmtpd.tests
Partial log (click to expand)
smtp1: running command: sync
smtp1: exit status 0
test script finished in 111.09s
cleaning up
killing client (pid 631)
killing smtp2 (pid 643)
killing smtp1 (pid 657)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/drz0xhw9pw7hyb7qqqxz2appcpdnlyqk-vm-test-run-opensmtpd

Then I must say I'm currently basically thinking “well, this already 3 months, can wait 1 more”, though I'm aware this will merge-conflict as soon as someone adds a test.

Sure, whatever way you think works best. I know it can be very frustrating when you spend time improving something and then it goes stale forever. Bonus stress points if there are issues after merge. That happens and is hard to avoid without better tooling. I appreciate your efforts to improve the testing infrastructure :)

I understand the impatience, and can't see how anyone wouldn't think this is at least a step in the right direction, so I'll merge.

\o/ Thank you! :D

env -i nix-build -I . --option restrict-eval true ./nixos/release.nix -A tests.openssh
error: access to path '/nix/store/x29rrys4gmskxpzngwibnmriigycnb79-nixpkgs' is forbidden in restricted mode
(use '--show-trace' to show detailed location information)

This currently stops ofborg from testing tests, and I would hazard a guess it will also fail on Hydra.

A first attempt at figuring out this is at https://github.com/NixOS/nixpkgs/pull/50186#issuecomment-438272329

@samueldr https://github.com/NixOS/nixpkgs/pull/50342 should solve this issue.

nixops breakage documented here: #50419


need a working simp_le fork

The acme protocol changed and simp_le is bust,
https://github.com/zenhack/simp_le/ looks ok

Thanks!

No problem :)
btw, i noticed that the role has disappeared from ansible galaxy, would it be possible to add it back?
Or do you think the role (and simp_le) should be completely depreciated? (In which case I'll find something else and write a migration guide).

I added it back (had some weird issues with ansible-galaxy not wanting to register the repo a few months ago, it's fixed now).
I still use this role on a server with no systemd so I would not consider it totally deprecated, I edited the README to reflect this.


{RBAC} Fix bug in az role assignment list --all --assignee "***" --include-groups: list should include the group if --include-groups specified.

Description

az role assignment list --all --assignee "***" --include-groups does not include the group that the assignee user is a member of. This is a regression issue in CLI.
Root cause: The role assignment list filtered the result based on the assignee object id which will exclude the group.
How to fix: do not filter the assignee object id if the "scope" is not specified since the list query already includes the filter for assignee object id.
Testing Guide

az role assignment list --all --assignee "***" --include-groups should list the group which the user is member of.
History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

add to S171

Please kindly link the PR to the related issue in the title (for it to appear in history) and the description (for the issue to be linked).

You may rebase on dev to rectify the history.


Multiple live selects get updated to same value

If you have two live selects in the same form, selecting a value for one updates both.
The form is set up as follows:
  <.form for={:unit_converter_form} let={f} phx-change="change" phx-submit="submit" class="w-1/2">
    <div class="flex gap-2 items-center">
      <%= LiveSelect.live_select(f, :unit_from, add_placeholder("Units From", @live_select_opts)) %>
      <%= LiveSelect.live_select(f, :unit_to, add_placeholder("Units To", @live_select_opts)) %>
    </div>
    <%= submit("Submit", class: "btn btn-primary") %>
  </.form>

It appears to be due to the js handleEvents firing for both instances. On my local copy I made a couple of changes to resolve this. I don't know if I am misunderstanding how to use multiple instances, but if these changes make sense, I'm happy to package them into a PR.
I patched the mounted in live_select.js to look like this:
    mounted() {
      this.handleEvent("reset", ({ id: id }) => {
        if (this.el.id == id) { // Note check on matching DOM id
          this.setSearchInputValue("")
          this.setHiddenInputValue("")
        }
      })
      this.handleEvent("selected", ({ selected: [label, selected], id: id }) => {
        if (this.el.id == id) {
          this.setSearchInputValue(label);
          this.setHiddenInputValue(selected)
        }
      })
      this.attachDomEventHandlers()
    },

and the functions that invoke the events in component.ex to look like this:
  defp select(socket, selected_position) do
    {label, selected} = Enum.at(socket.assigns.options, selected_position)
    id = socket.assigns.id # Pass in DOM id

    socket
    |> assign(
      options: [],
      current_focus: -1,
      search_term: label,
      selected: selected
    )
    |> push_event("selected", %{selected: [label, selected], id: id})
  end

  defp reset_input(socket) do
    id = socket.assigns.id

    socket
    |> assign(options: [], selected: nil, search_term: "")
    |> push_event("reset", %{id: id})
  end

@mindok thank you so much! Excellent catch.
I thought that https://hexdocs.pm/phoenix_live_view/Phoenix.LiveView.html#push_event/3 would route the event to the right component, but that was a wrong assumption. The docs are pretty clear that this is not the case.
I followed your suggestions and now it's working. Let me know if it works for you too.
closed by: ec34db79754d7423824f435210e75779e618eb82

Looks great thanks!


Add keywords support to Texture

Group says:

we would only need one keyword group
we could add the optional content-type attribute for kwd elements to group keywords
Users would prefer keyword sections in the user interface
We would need one additional keyword group per translated language

Spec proposal:
<kwd-group>
  <kwd content-type="author-keyword">optogenetics</kwd>
  <kwd content-type="author-keyword">two-photon</kwd>
  <kwd content-type="author-keyword">calcium imaging</kwd>
  <kwd content-type="research-organism">Mouse</kwd>
</kwd-group>

This model is equivalent to typed tags. We keep everything in a flat structure but allow the keyword to be member of a group. Using this model we can make Texture configurable to support journal- and  subject-specific keywords.

First version done, including category property and multiple languages.


Collapse stops working

I've noticed this when having 1 child item, spam tapping the parent eventually results in having multiple mPendingUpdates and then it stops reacting to expand taps. In onItemRangeRemoved it then returns false for return mPendingUpdates.size() == 1;. I substituted BigNerdRanch's expandable recycler view because it is deprecated and suffered the same fate, instead crashed though. But now I realise the same thing in here.
I'm using com.thoughtbot:expandablerecyclerview:1.3 with a very vanilla implementation, similar to the sample, even just setting title in bind, was doing a bit more but reverted to just that to make sure I'm not causing any undesired effects.

Issue seems to be not calling notifyDataSetChanged() from runOnUiThread when changes were made.


Add new functionality and fix bugs

here is example of my usage of this cookbook (part of role file):
"vim_config" => {
  "force_update" => true,
  "plugin_manager" => "pathogen",
  "bundles" => {
    "git" => [
      "git://github.com/tpope/vim-endwise.git"
    ]
  },
  "config_file_mode" => "template_from_attrs",
  "vimrc" => {
    "config" => {
      "system_wide" => [
        "syntax on",
        "set number"
      ],
      "user_specific" => {
        "root" => [
          'set statusline=%<%f%h%m%r%=format=%{&fileformat}\ file=%{&fileencoding}\ enc=%{&encoding}\ %b\ 0x%B\ %l,%c%V\ %P'
        ]
      }
    }
  }
}

Later I'll try to read config from data_bags and merge it with attributes from roles.

Finally got around to it.
Renamed the config option to simply "attributes" instead of "config_from_attrs", other than that it works as expected.
I was unable to fix the issue with creating config files for users that are created during the same run, and I don't think it's the responsibility of this cookbook to implement that.
If you can't wait for the second chef run, you need to manually notify the config creation on the user creation, but I'm not sure how do it since it's not an LWRP, sorry.


please add an example for multiple cards

Added multiple cards example inside Column, if you need any changes let me know

Closing this issue feel free to open it again if you have any questions


Dynamic icons in f7-nav-right problem

If I use dynamic icons in navbar there is a problem:

In 0.9.4 it works fine:

What is "dynamic" icon

Something like that:
<f7-nav-right>
   <f7-link v-if="currentTabShown === 1" @click="toggleFontSize" class="toggle-fontsize">Аа</f7-link>
   <f7-link v-if="currentTabShown === 2" icon-material="search" popup-open="#search"></f7-link>
</f7-nav-right>

I've made repo with example: https://github.com/NikitaKA/f7testapp/tree/navbar

It seems that this is not framework7-vue problem, but framework7.
I found a workaround:
this.$f7.navbar.size(navbarEl)

Call it every time after f7-nav-right size changed.


Support passing falafel option (for ecmaVersion 6)

There is no way to pass falafel options. It would be nice if there is a way to do this.
I tried to add {falafelOptions: {ecmaVersion:6}} when calling makeRequireTransform, but somehow it doesn't work. The second time falafel is called, falafelOptions disappears. It may be a bug of browserify-transform-tools.

falafelOptions disappearing issue seems my browserify mistake. I'll post again when I can confirm.


DreamOS

This is a simple example of a DreamOS which has several limitation:

[ ] it handles only HTTP/1.1 but the support of H2 will be easy
[ ] it does not support upgrade connection to websocket (it's a bit too divergent from what I did in paf)
[ ] it includes cohttp for letsencrypt (but I prepared something to completely delete cohttp from it here: mmaker/ocaml-letsencrypt#26)
[ ] paf is not released yet but close to be
[ ] complete the interface of dream.mirage to be like dream (without static)
[ ] make a static middleware which take a (module Mirage_kv.S) implementation
[ ] *.eml is not handled but we can I think with ocamlbuild (or waiting MirageOS 4)

The current example is deployed here - with gcloud (with a non-productive certificate!): https://dream.egar.im/
I will have less and less time in the coming weeks but it's a nice start for DreamOS 🎉 ! If someone would like to participate (mostly to copy/paste the H2 handler), it will be really appreciate.

Looks nice! The overall structuer of the PR seems quite reasonable. I will give it a detailed look over the next few days and leave comments.

@dinosaure For most of this PR, I'm ready to merge and have you "take over" src/mirage and Mirage examples, so you can do what is necessary for the port :) The code looks mostly self-contained. I can raise various questions, but I don't think blocking the PR is necessary.
The current issue is: if I run dune build -p dream in this branch, I get
File "src/vendor/dune", line 8, characters 36-41:
8 |   (libraries faraday bigstringaf ke mimic)))
                                        ^^^^^
Error: Library "mimic" not found.
Hint: try:
  dune external-lib-deps --missing -p dream @install
File "src/vendor/dune", line 22, characters 46-58:
22 |   (libraries dream.paf tls-mirage mirage-time mirage-stack dream.paf.alpn)))
                                                   ^^^^^^^^^^^^
Error: Library "mirage-stack" not found.
Hint: try:
  dune external-lib-deps --missing -p dream @install
File "src/vendor/dune", line 29, characters 49-59:
29 |   (libraries ipaddr domain-name dream.paf httpaf cohttp-lwt)))
                                                      ^^^^^^^^^^
Error: Library "cohttp-lwt" not found.
Hint: try:
  dune external-lib-deps --missing -p dream @install
File "src/vendor/dune", line 38, characters 4-15:
38 |     letsencrypt)))
         ^^^^^^^^^^^
Error: Library "letsencrypt" not found.
Hint: try:
  dune external-lib-deps --missing -p dream @install

So some Mirage packages have "infected" the basic build.

Let me know if you want commentary on the details of the Mirage version of the API, etc. I am currently assuming we will just discuss those in future work.

So some Mirage packages have "infected" the basic build.

Yes, I currently wants to delete cohttp as an "insidious" dependency from letsencrypt. I did not upgrade the Dream's OPAM file and it's why the build fail. My goal is to:

release letsencrypt without cohttp
release paf with the new version of letsencrypt (and split paf.cohttp to paf-cohttp)
upgrade the Dream's OPAM file with all of that

AFAIK paf is currently only for the Mirage version of Dream. If that's correct, then dream shouldn't depend on it. Do you intend to use package name dream for the Mirage version?

AFAIK paf is currently only for the Mirage version of Dream. If that's correct, then dream shouldn't depend on it. Do you intend to use package name dream for the Mirage version?

Currently, the MirageOS support exists via dream.mirage. So this PR brings new dependencies needed for dream.mirage from the OPAM point-of-view. I need to do some tries to see if a split still work or not - I remember some issues when I tried to make a new dream-mirage.opam package (mainly about access of internal stuffs).

I remember some issues when I tried to make a new dream-mirage.opam package (mainly about access of internal stuffs).

What were the issues? I just tried creating dream-mirage.opam and moving dream.mirage to dream-mirage. The issues I got were unchanged from not having the split (src/vendor/dune appears to depend on paf, etc.)
Could you push your nearest attempt into this PR? If you can separate the vendoring, I can probably take care of all the internal references issues.

I will do a try soon, currently we are are able to delete cohttp from the dependency graph with the new release of letsencrypt.

I just created dream-mirage package and it's fine :+1:. Then, I currently updated the whole stack to use letsencrypt.0.3.0 and delete by this way the CoHTTP dependency and the unikernel become smaller: from 8.6Mo to 7.9Mo 🎉 . The h2 supports still is needed but, as I said, it should be easy to implement it.

Based on this error in CI:
File "src/mirage/dune", line 2, characters 14-26:
2 |  (public_name dream-mirage)
                  ^^^^^^^^^^^^
Error: The current scope doesn't define package "dream-mirage".
The only packages for which you can declare elements to be installed in this
directory are:
- dream (because of dream.opam)

You may need to add dream-mirage.opam or the like. You may already have seen that :)


Simplified and optimized django.utils.functional.lazy().

Thanks for picking up and merging these !


[BUG] PWA create react app is throwing 400 Bad Request for site ID other than RefArch

Summary
When installing pwa react app using site ID other than RefArch, 400 Bad Request is received
Steps To Reproduce

Create new react app and give your own site id
npm start
app starts on local host
In terminal you receive below error
[Error]: 400 Bad Request
at eval (webpack-internal:///./node_modules/commerce-sdk-isomorphic/lib/index.esm.js:19:227975)
at di (webpack-internal:///./node_modules/commerce-sdk-isomorphic/lib/index.esm.js:19:21359)
at Generator.eval [as _invoke] (webpack-internal:///./node_modules/commerce-sdk-isomorphic/lib/index.esm.js:19:21109)
at Generator.Ii.forEach.e. [as next] (webpack-internal:///./node_modules/commerce-sdk-isomorphic/lib/index.esm.js:19:21733)
at Kn (webpack-internal:///./node_modules/commerce-sdk-isomorphic/lib/index.esm.js:19:19318)
at o (webpack-internal:///./node_modules/commerce-sdk-isomorphic/lib/index.esm.js:19:19522)
at processTicksAndRejections (node:internal/process/task_queues:95:5) {
response: Response {
size: 0,
timeout: 0,
[Symbol(Body internals)]: { body: [PassThrough], disturbed: false, error: null },
[Symbol(Response internals)]: {
url: 'http://localhost:3000/mobify/proxy/api/shopper/auth/v1/organizations/f_ecom_zzcu_183/oauth2/token',
status: 400,
statusText: 'Bad Request',
headers: [Headers],
counter: 0
}
}
}

Expected result
App should run without 400 errors
Actual result
Soon after launching the app in localhost above response is received in terminal
System Information (as applicable)
Browser: Chrome
Node version: 18.18.0
pwa-kit version: 3
Desktop OS: MacOS
Mobile Device Info:
Additional information

Hi @athik88,
Has the app configs in both sites.js and default.js been updated to include and point to the new site? Does zzcu_183 have the MegaStar site available?

Hi @athik88
I responded to you in our slack thread and will summarize here for visibility.
The issue you are seeing is triggered when the newly created site is missing a few pieces of configuration in BM.
To fix, you will want to assign a catalog to the site, assign a locale to the site (so that it isn't just default and so that the locale matches what is in your PWA kit config), and rebuild search indexes.
I will go ahead and close this thread here.


Remove MI Debugger from Help -> About

MI Debugger does not need to show up in Help -> About, this is only for
top level "brands".
@davkean

I think you also want to delete: https://github.com/microsoft/MIEngine/blob/main/src/MIDebugPackage/Resources/Package.ico.


Edits by atlas admin failing on Safari

A an atlas admin user has reported that when saving their edits the atlas is popping up the "Submission must be approved" message. Edits are not being applied nor are they showing up in the submission queue.
OS X Yosemite Version 10.10.5 and Safari version 10.0 (106<IP_ADDRESS>.10)
Older 2.2.8 snapshot from August 9ish

I am not able to reproduce this problem. I do not have the exact same components as you:

Safari 10.0 (116<IP_ADDRESS>.10)
nunaliit2-2.2.8-SNAPSHOT (2016-10-25)

Is it possible to provide me with the logs?

I am not able to reproduce it using
Safari Version 10.0.1 (116<IP_ADDRESS>.7) on the same site as the original bug reporter after upgrading it to an Oct 24, 2016 build of 2.2.8. So I'm not sure where the problem lay, but it seems to be OK now.


Plen 223/index fix [PLEN-223]

The pipeline only added the most recent helm chart into the index yaml file beforehand because the relevant command was outside of the for loop. With this modification the index yaml gets appended every time a new release is created and before it is removed from the folder, that is why the relevant command had to be placed inside the for loop.

@adamma-da Can you add a description regarding what are the changes and why are the changes required?
Also, probably the PR title could use a bit of touching up, remove the prefix and add a short title that is relevant to the changes being done.

@nicu-da good point there, your comments have been implemented

The other change has to do with the new tagging convention - we would like to remove 0.1.0 releases and add the 0.0.7 releases that came from the auto sync mechanism placed in our internal repo


'WiFiEventStationModeDisconnected' does not name a type

Hi Mdhiggins,
Thanks a lot for making this program.
I get the follow error.
'WiFiEventStationModeDisconnected' does not name a type.
I used Arduino 1.8.0 and also  Arduino 1.8.5.
I din't find answer to fix this problem.

Do you have the latest version of WiFiManager installed?
Sent from my iPhone

On Dec 5, 2017, at 15:23, lampenschakelen<EMAIL_ADDRESS>wrote:
Hi Mdhiggins,
Thanks a lot for making this program.
I get the follow error.
'WiFiEventStationModeDisconnected' does not name a type.
I used Arduino 1.8.0 and also Arduino 1.8.5.
I din't find answer to fix this problem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Actually make sure you’re using the ESP8266 Arduino Core 2.4.0. That might fix it
Sent from my iPhone

On Dec 5, 2017, at 15:23, lampenschakelen<EMAIL_ADDRESS>wrote:
Hi Mdhiggins,
Thanks a lot for making this program.
I get the follow error.
'WiFiEventStationModeDisconnected' does not name a type.
I used Arduino 1.8.0 and also Arduino 1.8.5.
I din't find answer to fix this problem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Seems to work on 2.3.0 actually

Hi Thanks a lot for you fast response.
WifiManager by Tzapu versie 0.12.0 Installed.
I fix the problem with the following instructions below.
Installing with Boards Manager
Starting with 1.6.4, Arduino allows installation of third-party platform packages using Boards Manager. We have packages available for Windows, Mac OS, and Linux (32 and 64 bit).
Install the current upstream Arduino IDE at the 1.8 level or later. The current version is at the Arduino website.
Start Arduino and open Preferences window.
Enter http://arduino.esp8266.com/stable/package_esp8266com_index.json into Additional Board Manager URLs field. You can add multiple URLs, separating them with commas.
Open Boards Manager from Tools > Board menu and install esp8266 platform (and don't forget to select your ESP8266 board from Tools > Board menu after installation).
After that i search for esp8266
Find the esp8266 by esp8266 community click update.


Require login

Currently the app comes up even when the user is not logged in. Now that the backend requires auth, this is confusing, as the user can't do anything with the app because all requests to the backend fail. We should check if the user is logged in, and make them log in if they aren't.

In the future, will we want this to be able to run in "standalone"/"local" mode?

I could see it being useful to allow the Scenario Editor + Analyst to run together without Auth

Basically IF Auth0 credentials are provided, require it. If not, go cray

Yeah probably not a bad idea. Can we make it a config param?
On Thu, Mar 31, 2016 at 4:40 PM, Trevor Gerhardt<EMAIL_ADDRESS>wrote:

I could see it being useful to allow the Scenario Editor + Analyst to run
together without Auth
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/conveyal/scenario-editor/issues/37#issuecomment-204116838

--
Matthew Wigginton Conway [WIG-in-tun CON-way]
Transportation Analytics/Open Source
Washington, DC

cool cool
On Thu, Mar 31, 2016 at 4:40 PM, Trevor Gerhardt<EMAIL_ADDRESS>wrote:

Basically IF Auth0 credentials are provided, require it. If not, go cray
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/conveyal/scenario-editor/issues/37#issuecomment-204116988

--
Matthew Wigginton Conway [WIG-in-tun CON-way]
Transportation Analytics/Open Source
Washington, DC


Ruby: explicitly require 'grpc/grpc' when loading C core, to avoid circular import warning

I think this will fix #4130.

src/ruby/lib/grpc/core/time_consts.rb modified 2016 but copyright only extends to 2015
src/ruby/lib/grpc/errors.rb modified 2016 but copyright only extends to 2015

Sorry :)

Fixed

Ping


im not completely sure why but it seems like changing things about spawners inside of the code causes the game to crash

but im also not completely sure about that either since it might just be spawning spawner nodes from a sub-scene might be the reason but i have tested with it inside and outside a subscene and it still crashes before godot can print any errors or anything like that. below is an unlisted video on my channel of this problem occuring.
video

update: attaching a node of the same type as the planned target as a temporary starting target seems to do the trick in fixing it but it crashes even when there are 0 homing or general target node things if its not assigned so im not closing the issue


installer: Don't run graphical installer ISOs as root

Motivation for this change
This is currently causing issues with some tools like Dolphin (the KDE
file manager) that refuses to run as root.
It's also very rare for graphical install media to be running as root nowadays, all other distros I know of run their installation processes as unprivileged users.
We can instead allow passwordless sudo with similar effect.
On the TTY you are still root, it's just the graphical session user that has changed.
I also took the opportunity to deduplicate some configuration that was the same across KDE/GNOME live ISOs.
Things done

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

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

[x] 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 nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Thanks for going off of my idea. :heart:

Great work!
I think the user should be less complex, like just 'live' without -.

@davidak Thanks for your feedback. I agree.

This should be in a merge-ready state. I just rebased it on master.
Unless someone is opposed I'll merge in a few days.
CC @dezgeg @xeji @grahamc @edolstra

Not in favor of this. It just seems to make the installation process needlessly complicated. I mean, installing an OS is an inherently privileged operation, so what security is gained by not running as root?

@edolstra Imo this is not at all about security.
It's about tools like dolphin refusing to run as root and
Currently our live media comes without a working file manager.

@edolstra Also it is substantiated that running graphical programs as root is insecure.
Here's as statement from a Gnome dev that supports this.

@worldofpeace That's cargo cult security. If a user account can sudo to root without a password, then that user account is pretty much equivalent to root in security terms.

Other than the file manager not being usable as root, which real other reasons are there for the installer environment to run in that double-faced manner? I will continue with arguments against, but I am open to arguments for.
1. Dolphin is fixed

https://phabricator.kde.org/D12795

https://phabricator.kde.org/R318:40453cb627a39f1ff92373f865426f0bcdc83419

https://phabricator.kde.org/D12732

https://phabricator.kde.org/R318:621cd24acfec8cbed19e9aa6ff8650cd6f38f809

This was taken from a freshly built graphical iso at the current tip of channels/nixos-18.09. We don't need this for 18.09.
2. Makes documentation harder to write
This is because anything related to manipulations using the installer image now has to account for the possibility of having the user not be root. The existing instructions and the existing user knowledge all assume this is always done under the root user account.
This will also cause issues when troubleshooting (discourse, IRC) where it will become plausible an issue a user has is caused by being in the graphical interface instead of being in a VT logged-in as root.
3. Wayland
I lied, this is not an argument against, but more of an open-ended question: when is it realistic to see Wayland on the installer image? I'm not up to speed with the state of Wayland, it may be more likely than I think!

I'm thinking this should be delayed, because we may need to figure out a better alternative than having the installer image sometimes be root, sometimes not be. It may be better (imho) to figure out a way so that all installer images behave the same way.
Since Wayland isn't (probably) for the next release, and definitely not this one, let's work on a proactive better integrated solution instead of a reactive (to dolphin) solution.

@samueldr I completely share your concerns. I also noticed the change in behaviour of dolphing and was deliberately holding this off for after 18.09.
Now that my immediate reason for this change is no longer valid I think it's a good idea to close this and rethink how we can get a wayland session installer up and running for a future release.


Add drone configuration

Signed-off-by: Mohamed Eldafrawi<EMAIL_ADDRESS>

https://drone-pr.longhorn.io/longhorn/backing-image-manager/1/1/3

https://drone-pr.longhorn.io/longhorn/backing-image-manager/1/1/3


Cannot change orientation after play video

I've followed your instructions on how to use your video player, it was a good video player. But what's wrong here is after i played your video, my apps does not want to change the orientation. When I rotate my tab into landscape, the apps still in portrait mode. Or maybe am I missing something? Thank you.

You can manual config these two params, that can control fullscreen origentation and quit fullscreen origentation

@RhezaSALT, the problem is that you need to set the Activity to let the player manage the orientation changes (this step should probably be added to the setup instructions).
In your AndroidManifest file, add the android:configChanges line like so:
<activity android:name=".activities.MyActivity" android:configChanges="orientation|keyboardHidden|screenLayout|screenSize"/>
Best of luck!


Change of libcxx linkage

https://github.com/conda-forge/cctools-and-ld64-feedstock/pull/70 changed the linkage of libcxx which is now linked dynamically by default.
This has been observed for mamba with https://github.com/mamba-org/mamba/pull/3434 (see those logs).

If it's "just" the default, then prioritizing the shared library is actually in the interest of conda-forge's general preference for shared libraries. In that case micromamba should still be able to specify that it wants to link to libc++.a specifically?
If static linkage is not possible anymore then that would obviously be a bigger problem

Most packages should be completely fine with shared linkage, as we ship libcxx basically in every environment. Cases like micromamba (everything statically linked) are very rare to my knowledge, so I doubt a conda-forge-wide announce is useful. But I don't mind in principle... 🤷♂

OK let's close it then.

https://github.com/conda-forge/cctools-and-ld64-feedstock/pull/70 changed the linkage of libcxx which is now linked dynamically by default.

Why do you think #70 is the culprit?

The build logs on micromamba passed with the previous build but do not with the new one, here is the environment change in between the two:
@@ -424,10 +425,10 @@ List of packages in environment: "/Users/runner/micromamba/envs/mambabuild"
   bzip2                      1.0.8         h99b78c6_7          conda-forge
   c-ares                     1.33.1        hd74edd7_0          conda-forge
   ca-certificates            2024.8.30     hf0a4a13_0          conda-forge
-  cctools                    986           h4c9edd9_3          conda-forge
-  cctools_osx-arm64          986           hf2da8af_3          conda-forge
+  cctools                    1009.2        h4c9edd9_0          conda-forge
+  cctools_osx-arm64          1009.2        hfaac078_0          conda-forge
   certifi                    2024.8.30     pyhd8ed1ab_0        conda-forge
-  cffi                       1.17.0        py312h0fad829_1     conda-forge
+  cffi                       1.17.1        py312h0fad829_0     conda-forge
   chardet                    5.2.0         py312h81bd7bf_2     conda-forge
   charset-normalizer         3.3.2         pyhd8ed1ab_0        conda-forge
   click                      8.1.7         unix_pyh707e725_0   conda-forge
@@ -457,14 +458,14 @@ List of packages in environment: "/Users/runner/micromamba/envs/mambabuild"
   jsonschema                 4.23.0        pyhd8ed1ab_0        conda-forge
   jsonschema-specifications  2023.12.1     pyhd8ed1ab_0        conda-forge
   krb5                       1.21.3        h237132a_0          conda-forge
-  ld64                       711           h4c6efb1_3          conda-forge
-  ld64_osx-arm64             711           h5ecc89c_3          conda-forge
+  ld64                       907           h4c6efb1_0          conda-forge
+  ld64_osx-arm64             907           hdd277f2_0          conda-forge
   libarchive                 3.7.4         h83d404f_0          conda-forge
   libcurl                    8.9.1         hfd8ffcc_0          conda-forge
   libcxx                     18.1.8        h3ed4263_7          conda-forge
   libedit                    3.1.20191231  hc8eb9b7_2          conda-forge
   libev                      4.33          h93a5062_2          conda-forge
-  libexpat                   2.6.2         hebf3989_0          conda-forge
+  libexpat                   2.6.3         hf9b8971_0          conda-forge
   libffi                     3.4.2         h3422bc3_5          conda-forge
   libiconv                   1.17          h0d3ecfb_2          conda-forge
   liblief                    0.14.1        h3f3aa29_1          conda-forge
@@ -477,13 +478,15 @@ List of packages in environment: "/Users/runner/micromamba/envs/mambabuild"
   libssh2                    1.11.0        h7a5bd25_0          conda-forge
   libxml2                    2.12.7        h01dff8b_4          conda-forge
   libzlib                    1.3.1         hfb2fe0b_1          conda-forge
+  llvm-tools                 18.1.8        h5090b49_2          conda-forge
+  llvm-tools-18              18.1.8        h5090b49_2          conda-forge

I would need to see the full compiler and linker commands to help with debugging.

I am not using a machine on macOS so I cannot really tell the different command. I recommend that you can browse those logs. Note that this was fixed for micromamba with https://github.com/mamba-org/mamba/pull/3436.

-static-libstdc++ was a deprecated option and I guess they removed it.


please add new query by city

I want to get random user by city, like https://randomuser.me/api/?nat=us&city=palmdale
please add this query selection
thanks

Adding a city parameter would have no affect on the data that is generated. Data fields such as zip/state are all generated randomly randomly regardless of city.


Flow refine a union type between arguments and return value of a function

Proposal
I'm trying to figure out a way to represent basically a single disjoint union type that is split between function arguments and the return value. I don't think this is currently possible in flow, but it would be really useful.
Use case
This could be useful in a lot of situations, but one specific example would be typing an API client. You have a single function, something like client.request and depending on the path and method of the request, the data returned will be a different shape.
Here's a code example of this. The interesting thing is, you can represent this using a disjoint union if you expose a callback API, but I don't think there's a way to represent it where the function returns the result.
type User = {id: number, name: string}
type Post = {id: number, content: string}
type APIRoute = {| +path: "/users", +method: "GET", +callback: (results: User[]) => void |} |
                {| +path: "/posts", +method: "GET", +callback: (results: Post[]) => void |};

// Callback version works as expected
function apiClientCb(params: APIRoute): void {
  // access api, call params.callback(results)
}
apiClientCb({path: "/users", method: "GET", callback: (results) => {
  console.log("Fetched users", results.map(r => r.name)); // Works
  console.log("Fetched posts", results.map(r => r.content));  // Error, as expected
}});

// Returning a value instead doesn't work
function apiClient(params) {
  const p = new Promise(resolve => (
    apiClientCb({...params, callback: (results) => resolve(results)})
  ));
  return p;
}
apiClient({path: "/users", method: "GET"}).then(results => console.log("Fetched users", results.map(u => u.name)));

TryFlow link
I'm not even sure if the syntax exists to type the non-callback version. In the above code when trying to infer the type flow gives an error "Could not decide which case to select. Since case 1 [1] may work but if it doesn't case 2 [2] looks promising too."
A similar issue is: https://github.com/facebook/flow/issues/5675 but it is expressed a little bit differently and it hasn't gotten any responses.

You can define an intersection of function types to declare that a function can be called with multiple signatures. For instance, the type
type ApiClient =
  & {| +path: "/users", +method: "GET" |} => Promise<User[]>
  & {| +path: "/posts", +method: "GET" |} => Promise<Post[]>;

would capture a function that can be called both with path: "/users" to produce a Promise<User[]>, and with path: "/posts" to produce a Promise<Post[]>.
That it's an intersection rather than a union makes sense if you consider that T & U is a type that has to satisfy both T and U, whereas T | U is one that has to satisfy one of them.
I'm not sure you can type the non-callback version in a way so that you can implement it as just a call to the callback version though--not sure how the types interact together with the spread of params.
See flow.org/try.


Allow schema_extra to be a classmethod

Change Summary
Allow schema_extra to be a classmethod.

Related issue number
Resolves #1305

Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[ ] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

I find it far easier to remove the check altogether, than tinker with method inspection on class object. Not sure what is the best way to make mypy happy though.
@samuelcolvin wdyt?

So, I've added a test for instance methods, but I'm not sure how useful it is.
Lint is failing due to obsolete pyflakes version (fixed in master, but not yet released on pypi). How should we proceed?

spent ages trying to improve on this, but nothing seems to work.
Let's go with this.


refactor janitor

Features: #662   swan proxy 重构和增强
API： https://github.com/bbklab/swan/blob/refactor-janitor/src/janitor/docs/api.md

Codecov Report

Merging #661 into master will increase coverage by 0.02%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #661      +/-   ##
==========================================
+ Coverage    18.1%   18.13%   +0.02%
==========================================
  Files          28       28
  Lines        1640     1632       -8
==========================================
- Hits          297      296       -1
+ Misses       1301     1296       -5
+ Partials       42       40       -2

有个问题，如何更新upstream中一个app的权重或者域名

r.POST("/upstreams", s.addUpstream)
r.DELETE("/upstreams", s.delUpstream)

期望提供PATCH方法。

Codecov Report

Merging #661 into master will decrease coverage by 0.13%.
The diff coverage is 18.18%.

@@            Coverage Diff             @@
##           master     #661      +/-   ##
==========================================
- Coverage    18.1%   17.97%   -0.14%
==========================================
  Files          28       28
  Lines        1640     1647       +7
==========================================
- Hits          297      296       -1
- Misses       1301     1307       +6
- Partials       42       44       +2

用统一的PUT方法 增加或更新 upstream 和 backend


[Bug][hdom, rstream] error is silently ignored

Hi!
I don't actually know which combination of hdom, rstream and generators causes this issue but in this particular case if I have some error it is not shown and it vanishes into the void causing troubleshooting and debugging quite difficult.
I'll try to investigate on it but maybe someone has a smart enlightenment.
import { stream, sync } from<EMAIL_ADDRESS>import { updateDOM } from<EMAIL_ADDRESS>import { map, scan, count, range } from<EMAIL_ADDRESS>
function getColor(n: number, clicks: number) {
  if (n === 3) {
    throw new Error('dudee')
  }
  return n === clicks - 1 ? 'red' : 'black'
}

const app = ({ clicks }: any) => [
  'div',
  [
    'a',
    {
      href: '#',
      onclick: () => clickStream.next(0),
    },
    `${clicks} clicks`,
  ],
  ...[...range(clicks)].map(n => {
    console.log(n, clicks - 1)
    return ['p', { style: { color: getColor(n, clicks) } }, n]
  }),
]

const clickStream = stream().transform(scan(count(-1)))
clickStream.next(0)

sync<any, any>({
  src: {
    clicks: clickStream,
  },
}).transform(map(app), updateDOM({ root: document.body }))

Ciao, @nkint - am back from the mountains... will look into this tomorrow, but 2 things:

currently there's no explicit error handling (yet!) for transform()ers (transducers) - this will be added as part of the ongoing updates on the feature/rstream-opts branch
you can enable error logging like this:

import { ConsoleLogger, LogLevel } from<EMAIL_ADDRESS>import { setLogger } from<EMAIL_ADDRESS>
// set package specific logger instance
setLogger(new ConsoleLogger("rstream", LogLevel.WARN));

Be aware that not all errors will be caught & logged via this mechanism, but it should work for the above use case...
In general, each ISubscriber' can provide an error hook, but transducers added via transform() are handled differently, and as mentioned, currently still lack user controllable error handling/hooks...

@nkint Just to add to this, here's how you can add/override an error handler for a transform() subscription (based on your example)
const main = sync<any, any>({
    src: {
        clicks: clickStream
    }
});
const sub = main.transform(map(app), updateDOM({ root: document.body }));
sub.error = (e) => alert(e.message);

The other thing worth noting here is that iff a custom error handler is provided, the subscription will NOT automatically go into the ERROR state and can receive future values. Only if the default error handler is called, the sub switches to that state and silently ignores further inputs... This behavior still needs to be documented. But the underlying reasoning for this is that you could do something like:
import { fromIterable, stream, sync } from<EMAIL_ADDRESS>import { map, range, sideEffect } from<EMAIL_ADDRESS>import { updateDOM } from<EMAIL_ADDRESS>
const app = ({ main, errors }: any) => [
    "div",
    ["h1", main],
    errors && ["div.red", "error: ", errors]
];

const main = fromIterable(range(5), 1000);

const errors = stream<string | null>();
errors.next(null);

const mainXform = main.transform(
    sideEffect((x: number) => {
        if (x > 2) throw new Error(String(x));
    }),
    map((x: number) => x * 10)
);
mainXform.error = (e: Error) => errors.next(e.message);

sync<any, any>({ src: { main, errors } }).transform(map(app), updateDOM());


FormsPlot does not contain a definition for 'Plot'

i am tring the example below and getting the error in the topic of this
double[] dataX = new double[] { 1, 2, 3, 4, 5 };
double[] dataY = new double[] { 1, 4, 9, 16, 25 };
formsPlot1.Plot.AddScatter(dataX, dataY);

Hi @kayleejacob1,
Ensure you are using the latest (beta / pre-release) version of ScottPlot. When searching packages with NuGet, ensure the "pre-release" checkmark is checked to let you see the latest versions (currently ScottPlot 4.1).
Let me know if this doesn't do the trick!


[Internal] Query: Fixes LINQ Test Organization

Pull Request Template
Description
This PR reorganizes the LINQ test files into a folder called Linq for easier test discovery
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[] New feature (non-breaking change which adds functionality)
[] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[] This change requires a documentation update

Closing issues
To automatically close an issue: closes #IssueNumber

{

Should the namespace be also updated for the file move?

Refers to: Microsoft.Azure.Cosmos/tests/Microsoft.Azure.Cosmos.EmulatorTests/Linq/LinqAggregateFunctionsBaselineTests.cs:7 in 8889c9c. [](commit_id = 8889c9ceb211e38cff5d43d763b874d10e323109, deletion_comment = False)

{

Should the namespace be also updated for the file move?
Refers to: Microsoft.Azure.Cosmos/tests/Microsoft.Azure.Cosmos.EmulatorTests/Linq/LinqAggregateFunctionsBaselineTests.cs:7 in 8889c9c. [](commit_id = 8889c9c, deletion_comment = False)

The files are all under different namespace originally, so I haven't changed them in case there was a weird namespace dependency. I will look at that in the future


Allow users to choose lhs sampling criteria

Codecov Report

Merging #217 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #217   +/-   ##
=======================================
  Coverage   77.36%   77.36%
=======================================
  Files          97       97
  Lines        4603     4603
=======================================
  Hits         3561     3561
  Misses       1042     1042

Impacted Files
Coverage Δ

GPyOpt/experiment_design/latin_design.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Please don't "steal" the .html extension

Hi, thanks for contributing your plugin.
I just spent 15 minutes figuring out why suddenly HTML formatting was broken (wrong amount of indent spaces, no automatic white lines, etc.) in PhpStorm. As it turned out, installing the svelte plugin had "stolen" the .html extension. Under Settings > Editor > File Types, the .html extension had been moved to 'Svelte Html Components'. That means that the formatting settings under Settings > Editor > Code Style > HTML no longer applied to HTML documents (PhpStorm was using the settings for 'Other File Types' instead).
AFAIC this should not be the default behavior, as it is unexpected and hard to debug.

Also breaks syntax highlighting for HTML Django Templates in PyCharm 2018.1.1

Thanks for the plugin but I had the same issue. Since I installed it the "open in browser" feature in Webstorm stopped working. Hope it will be fixed. In the meantime I had to disable the plugin.


Warship tooltip is completely incorrect

Pretty sure this has never been the case for Warships and is just a leftover tooltip from when I started Kul'tiras and didn't finish it.

What is it supposed to say?

@HerrDave Just something similar to Battleship I guess. The wrong part is "Each Warship built is a different flagship with slightly different attributes." The ship doesn't do that.

@SebastianTanoni Who would own this ticket if not you? Didn't you implement Kul'tiras?

I'm not sure I removed my assignment


Confirm Python 3 support

As you can see in the Python 2.7 Countdown clock, Python 2.7 will retire in a year. It is imperative that Python 3 support therefore be confirmed. Would this code cleanly work with Python 3?

OK, we will do it later. Thanks


[DOC] improvements on local linting/precommit setup developer documentation

Update: content has been added, but the lists are formatted badly due to typos in the code. Would be appreciated if someone could fix this!

From #3086, by @jelc53, in reference to https://github.com/alan-turing-institute/sktime/pull/3089 and the current developer doc on local linting and precommit setup:

Great to hear! Appreciate you helping me through it. Re feedback on https://github.com/alan-turing-institute/sktime/pull/3089, the pre-commit setup made life much easier for me so I think that’ll be helpful for others too. Only question for me is whether you also make clear that another option is to configure the ide to flag black and flake8 conventions for those who don’t want to use pre-commit. Not sure. Might be one of those things where more info is more confusing than helpful.

@jelc53, not sure I understand - what is that other option you are referring to, i.e., "configure the ide to flag black and flake8 conventions"?
I added an entire section called "Integrating with your local developer IDE" in #3089, so do you think this is not detailed enough, or is there a different option?
Here: https://www.sktime.org/en/latest/developer_guide/coding_standards.html#integrating-with-your-local-developer-ide
(you need to go to latest documentation to see the one on current main, the stable will always show the state at the last release)
Pull requests to improve the docs are also always appreciated!
The file in question is developer_guide/coding_standards.rst

Yep I was defintely looking at an older version. The section on integrating with local developer ide is exactly what I was thinking.

Excellent! If you have anything to add, PR are appreciated. Closing for now, since it looks like the requirements are met.

actually, the bullet points in various lists are going over lines and are badly formatted, with lines starting in the middle of other lines. Would be great if someone could fix this before the next release 😄
(good first issue since it just requires adding spaces in the above-mentioned file)

I will take this up.

Do I have to look in developer_guide/coding_standards.rst?

Thanks, @C-mmon!

Do I have to look in developer_guide/coding_standards.rst?

Yes, correct!

created a pull request

Just wondering if this issue has been resolved?  If so can we close the issue?

Yes I think so!

yes, here: https://github.com/sktime/sktime/pull/3111


Not able to run locally

functions-framework : The term 'functions-framework' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

functions-framework --target=get_topics

  + CategoryInfo          : ObjectNotFound: (functions-framework:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

I have tried uninstalling and installing functions-framework
I'm using windows11 and using vscode

Hi @salmanpary, this sounds like it might be an issue with your machine's PATH variable. From my understanding Python usually adds to it so pip packages are available, but in some cases may not. I think this guide should help you: https://stackoverflow.com/a/36160069
I'm closing for now, but feel free to re-open if you have additional questions!


WALinuxAgent: address issues in systemd unit configuration

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[ ] The toolchain has been rebuilt successfully (or no changes were made to it)
[ ] The toolchain/worker package manifests are up-to-date
[ ] Any updated packages successfully build (or no packages were changed)
[ ] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[ ] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[ ] All package sources are available
[ ] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[ ] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[ ] All source files have up-to-date hashes in the *.signatures.json files
[ ] sudo make go-tidy-all and sudo make go-test-coverage pass
[ ] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary

What does the PR accomplish, why was it needed?
Change Log

Add preset file to explicitly enable waagent.service
Fix waagent.service to point to /usr/sbin/waagent

Does this affect the toolchain?

NO
Test Methodology

Pipelines running

i'd recommend putting the preset into azurelinux-release, probably into the 90-default.preset file


Aligned inline comments don't work right with {:style :respect-nl}

In some situations, when inline comments are aligned, they don't work right when {:style :respect-nl} is used:
(def e439a "(;a\nlist\n:b\n:c ;def\n   ;aligned-inline\nd)")
czprint e439a {:parse-string? true})
(;a
 list :b
      :c ;def
         ;aligned-inline
        d)

(czprint e439a {:parse-string? true :style :respect-nl})
(;a
 list
  :b
  :c ;def
                 ;aligned-inline
    d)

It should look like this:
(czprint e439a {:parse-string? true :style :respect-nl})
(;a
 list
  :b
  :c ;def
     ;aligned-inline
    d)

Well, it should look like that except the "d" is also in the wrong place, but that is a separate issue.

Fixed in 1.0.0


body limit exceeded error

I'm submitting a query to Qlever containing a large VALUES block. It responds with a server error, and this message is printed to the Qlever log:
 ERROR: body limit exceeded: body limit exceeded

Is this limit configurable?

@balhoff Please try #1089

Thank you @hannahbast! I'll be giving it a try soon.

@hannahbast I'm testing this now, and running into a new error:
Merging of more than one non-empty local vocabularies is currently not supported, please contact the developers

Could this be related to using multiple VALUES blocks in my query?


Fix ROF off by one error

Fixes #12725

You've changed the behavior of the plugin, and the test tests the behavior of the plugin, and so the test is failing. It is possible the test is incorrect and testing the wrong behavior, in which case the test would need to be updated. Offhand I do not know if either the test is right or your change is right.

I have updated the test so that it should be correct, but it is still failing.

#15288 at least explains why the change is being made and has a correct test

I feel like the comments in my code explain why the change is being made. The way they fixed the test is unsatisfactory, as it does not emulate the actual behaviour of the client, so I opted to do the test this way. If #15288 does this better, then we should merge that instead.

The test is expecting the value 140, but 141 is returned. Because your change of adding + 1 to MAX_RING_OF_FORGING_CHARGES. Though I don't think this is the right solution. A conditional to subtracting in the first place I think is more suitable such as skipping if RING_OF_FORGING_USED_TEXT is after RING_OF_FORGING_BREAK_TEXT.

I don't know why 141 is returned, if you look at the modified test, the ring is used after it is broken, same as in the client, so it should return 140.
I made this change to imitate the way necklaces of binding are coded, so if we make this change to rings of forging, we should make the same change to necklaces of binding


Group Configuration Formatting & Crashes

Hyprland Version
Hyprland, built from branch main at commit 99ca26d4eb84e0071264713902e5b287fcab392e dirty (hooksystem: fix missed log include). Tag: v0.32.3-84-g99ca26d4  flags: (if any) debug
Bug or Regression?
Bug
Description
Configuration Formatting Issues
When writing in the variables for group properties, it does not take the normal json formatting.
group {
    groupbar{
        gradients=false
    }
}

Instead, variables must be specified inline group:groupbar:gradients=false.
Configuration Crashes
When making modifications to any of the color configurations (not tested with other options) Hyprland will crash on save. I was using NeoVim to make the modifications and had an active group in the workspace I was editing from.
How to reproduce
Group windows and make configuration modifications. It should crash when you save the settings or throw an error if you attempt to format in json.
Crash reports, logs, images, videos
hyprlandCrashReport4275.txt
hyprlandCrashReport3595.txt
hyprlandCrashReport526.txt

No crash when making modifications without a group active.

When writing in the variables for group properties, it does not take the normal json formatting.

your syntax is invalid, I will refer you to the wiki: https://wiki.hyprland.org/Configuring/Configuring-Hyprland/

That works, but I'm still getting crashes when modifying properties. It looks like they're isolated to having titles rendered. If I turn off title rendering the crashes don't occur when modifying other properties.

check with e2f18f8c7f95e4094acb94c5a06dc6d75d7fc9c1

No crashes! Gradients don't update dynamically, but I'm assuming that's intended.

Let me clarify, removing/adding the gradient doesn't update dynamically. The color will update dynamically without issue.

toggle another group, open a window in a group, or something to reload them

I'll consider this solved then


Sonarcloud with code coverage

This is used to get code coverage for our sonarcloud integration on PR's and when code is pushed to main.
The complication comes with using the sonarcloud token from forked repos. I have tested using two github accounts and forking my fork.
This works by saving the test report from the PR Tests workflow as an artifact and also the pr number. Then when the PR Tests workflow completes successfully a workflow will begin for sonarcloud witch gets information about the forked repo, and fetches the code for the scan. The code coverage is downloaded from the artifact, updated and then upload to sonarcloud.
Another workflow runs the tests on merge to main, runs the scan and uploads results. I thought about doing this as one workflow but decided separate workflows was actually much simpler.
I changed the workflow Tests to an action and adjusted the other workflows that used it. When calling from the push to main workflow it was having trouble as a workflow.
Requires disabling Automatic Analysis in the sonarcloud admin console. You can't use automatic and manage it from CI at the same time. Also won't exist until the workflows have been merged to main.
Main branch:

PR (Failing):
The required coverage can be adjusted in sonarcloud console.

PR (Passing):

Hmm. Might have messed something up with that Tests / Test Python 3.9 Expected — Waiting for status to be reported

We'll need to update the Required checks to switch to the updated test flow/action.  If we do that before we merge this PR, it will have to be done right before the merge, as the change will impact the required checks on all outstanding PRs, and they will need to be updated so they run and pass the new test flow/action.

A few questions, and a suggestion.
Is it necessary to run the sonar scan on the PR and on the merge? Just wondering what the difference is and whether running the scan on merge would be redundant since it's already been run on the PR.

I think it's necessary to get the code coverage on main and not just the PR. Also, I think sonarcloud is already doing a scan on both currently, when using automatic analysis. I can have a look and see if I can find any information on this.

I may be able to use the same code coverage artifact to avoid needing to run the tests on merge to main. I will look at doing that.
For the extra scan on merge to main I don't think anything needs to be changed. This is the same behaviour as automatic analysis after reading the sonarcloud documentation.

I may be able to use the same code coverage artifact to avoid needing to run the tests on merge to main. I will look at doing that.
For the extra scan on merge to main I don't think anything needs to be changed. This is the same behaviour as automatic analysis after reading the sonarcloud documentation.

Sounds good.  Let me know when your ready for final review.

@WadeBarnes So, I tried to use the previous test coverage artifact but have been having a hard time locating it from this workflow. It's a lot different than the other workflow which has the workflow run id. I thought I could use the pr commit, but haven't been able to make it work.
It would be nice to not run the tests twice for the same code, but I also don't want to mess around with this for a long time. So, I think this should be ready and maybe I'll be able to figure it out for a later PR.

Branch protection checks have been updated to account for the changes made to the workflows in this PR.  This will impact ALL existing PRs, which will have to be updated to run the updated workflows in order to pass the branch protection checks.
cc @jamshale, @swcurran, @dbluhm

Failure here was my fault.  I forgot to turn off automatic analysis.  It's off now.

Job was rerun successfully.


chore: release-please initial configuration PT-1672

Description :sparkles:
Issues :bug:
Closes :no_good_woman:
PT-1672:
Related :handshake:
Testing :alembic:
Automated tests :gear:
Manual testing :construction_worker_man:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

kultus-admin-ui branch is deployed to platta: https://kultus-admin-ui-pr300.dev.hel.ninja :rocket::rocket::rocket:


Schema with a transform results in an invalid intersection

Given a schema like:
const workflowSchema = z.object({
      sequence: z.number(),
      state: z.nativeEnum(WorkflowState),
      in_bundle: z.boolean(),
      timestamp: z.string().transform(value => DateTime.fromISO(value)),  // Luxon Datetime
})

which is intersected with another schema to parse an object, e.g.:
const apiSchema = z.intersection(featureSchema, workflowSchema)

This is not built via extends because featureSchema is defined to be used directly from files as well as via the API.
Since upgrading Zod (from 3.2 to 3.18) this results in an invalid intersection. From the debugger I've shown that timestamp fails in mergeValues.
My workaround is to transform after merge, e.g.
const apiSchema = z.intersection(featureSchema, workflowSchemaNoTransform)
    .transform(value => ({ ...value, timestamp: DateTime.fromISO(value) }))

I don't know if there's a "fix" here. I get why it's failing. It would be good to get a more useful error message, rather than having to poke around in the debugger to realise why it fails.

Can you share a minimal reproduction?

I do get invalid_intersection_types, but I don't get the key that's causing the failure. It's worth noting that apiSchema was then packed into a z.array to receive a list of objects from the API. I'll see if I can reproduce it in a minimal case.

Okay here's a minimal case.
It would be nice if the ZodError had a path that pointed you to the broken field.
import * as z from "zod";
import { DateTime } from "luxon";

const featureSchema = z.object({
  type: z.literal("Feature"),
  timestamp: z.string()
});

const workflowSchema = z.object({
  timestamp: z.string().transform((value) => DateTime.fromISO(value))
});

const mergedSchema = z.intersection(featureSchema, workflowSchema);

console.log(
  mergedSchema.parse({
    type: "Feature",
    timestamp: DateTime.now().toISO()
  })
);

// Fails with
// ZodError: [
//  {
//    "code": "invalid_intersection_types",
//    "path": [],
//    "message": "Intersection results could not be merged"
//  }
// ]

Sandbox

Bump. Ran into this in our code recently; worked around it by dropping the shared fields and using .extend for good measure. The error was the same as in the example; no information as to why mergeValues failed --- which makes sense since mergeValues just returns { valid: false } when it fails and it's only ZodIntersection._parse that adds the issue to the context :thinking:


nolightmap stuff, fix #118

@gimhael is it ready for merge?
bug reporter @maek confirmed it works
I confirm it works and fixes the issues without noticing any regression

LGTM

code looks OK, it works, change fixes the issue, it does not introduce regressions, and the commits look to be shaped for a merge, so let's merge! :dancer:


Add dist serialization to Category model

Adds JSON and TXT serialization to the Category model for dist generation, including methods for both individual values and collections.

Adds descendants and descendants_and_self methods
Localizes full_name method
TXT padding is calculated based on longest GID, which is implemented simply by iterating through the collection. This only took a few milliseconds on my machine, so is fine for now.

Merge activity

Nov 27, 2:30 PM EST: A user merged this pull request with Graphite.


audio volume level lowered.

What is the purpose of your issue?

[x ] Bug
[ ] Feature Request
[ ] Question
[ ] Other

Description

one of my downloaded track has its volume decreased. confirmed the yt link has normal volume via --dry-run
Log

I think it is related to the video from youtube.

post the exact link so that we can try it ourselves

I recently experienced the same issue, it's legit, No idea what could be causing it

I recently experienced the same issue, it's legit, No idea what could be causing it

I think it depends on the video?

am not sure but I'll try to redownload it to confirm

FFMPeg has the ability to normalize audio. There are also specialized packages that can do this i.e. FFMPEG Normalize.
Perhaps this could be added as a feature.
See: https://superuser.com/questions/323119/how-can-i-normalize-audio-using-ffmpeg

Audio is normalized using the EUB R128 algorithm by default in v3. So, already implemented.


useIntersectionObserver return previous entry as well

It seems like it'd be generally useful to have the previous entry (or list of prev entries) returned from the hook. That way client code could compare timings, e.g.
const [ entry, prevEntry ] = useIntersectionObserver(ref, {})
const timeOnScreen = prevEntry ?? entry.time - prevEntry.time

or all previous entries like:
const { entry, previousEntries } = useIntersectionObserver(ref, {})
// ... do fancy comparisons

Hi, thanks for the feedback!
I've pushed a PR that should fix it,  feel free to give a code review on it.
See #464

Amazing, thanks @juliencrn. I'll check it out!

Hey @juliencrn, I might have missed it but I don't see a way to get the previous entry with the new code.


fix(kendo): update peer dependencies

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
this makes any available version of kendo ui compatible for the library
What is the current behavior? (You can also link to an open issue here)
https://github.com/ngx-formly/ngx-formly/issues/3571
What is the new behavior (if this is a feature change)?
any version of kendo above the minimum will be accepted
Please check if the PR fulfills these requirements
The commit messages follow our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
A unit test has been written for this change.
Running npm run build produced a successful build. (Unit testing can be done by running npm test;)
My code has been linted. (npm run lint to do this. npm run build will fail if there are files not linted.)
Please provide a screenshot of this feature before and after your code changes, if applicable.

@aueelis this is the new one

Thank you @luizfbicalho!

You're welcome @aitboudad
when Will be a new version?

when Will be a new version?

done in v6.1.2


Update ThemeSettingsView.swift

Added "QueryTextField"
Replaced "TextField" with "QueryTextField"

Description

Related Issues

#ISSUE_NUMBER

Checklist

[ ] I read and understood the contributing guide as well as the code of conduct
[ ] The issues this PR addresses are related to each other
[ ] My changes generate no new warnings
[ ] My code builds and runs on my machine
[ ] My changes are all related to the related issue above
[ ] I documented my code

Screenshots

@CrashdebugDevelopment could you please add a screenshot?


CookieJar refactoring v2

#6864 was bad because CookieJar did too many things, having too many responsibilities.
Here's the (backward compatible) approach of this pull request:

response cookies are handled by the new ResponseCookieJar
we don't need a RequestCookieJar: it's already there in Symfony (see $request->cookies)
CookieJar now is a simpler class that can be used for simple operations that involve both request and response cookies

For backward compatibility (we have to consider existing code that uses $app->make('cookies') or the CookieJar class with DI), I kept these methods (but I deprecated them) that work with response cookies:

set ⇒ use ResponseCookieJar::addCookie
add ⇒ use ResponseCookieJar::addCookieObject
clear ⇒ use ResponseCookieJar::clear
getCookies ⇒ use ResponseCookieJar::getCookies

I should have fixed the issues.


Added the class keyword

Added the class keyword in the Visual Basic syntax file.

Codecov Report

Merging #5132 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5132      +/-   ##
==========================================
- Coverage   81.99%   81.97%   -0.02%
==========================================
  Files         134      134
  Lines      147133   147133
==========================================
- Hits       120644   120619      -25
- Misses      26489    26514      +25

Impacted Files
Coverage Δ

src/ui.c
69.06% <0%> (-1.26%)
:arrow_down:

src/gui_gtk_x11.c
58.35% <0%> (-0.25%)
:arrow_down:

src/gui.c
64.27% <0%> (-0.16%)
:arrow_down:

src/drawline.c
85.07% <0%> (-0.14%)
:arrow_down:

src/os_unix.c
63.41% <0%> (-0.09%)
:arrow_down:

src/mouse.c
74.97% <0%> (-0.09%)
:arrow_down:

src/terminal.c
81.7% <0%> (-0.04%)
:arrow_down:

src/window.c
88.22% <0%> (-0.04%)
:arrow_down:

src/message.c
79.43% <0%> (ø)
:arrow_up:

src/channel.c
84.25% <0%> (+0.07%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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

Please contact the maintainer, Tim Chase, see the file header.

Sorry but the mail of the maintainer doesn't work.

Sorry but the mail of the maintainer doesn't work.

Try: Tim Chase<EMAIL_ADDRESS>Or:  Tim Chase<EMAIL_ADDRESS>--
I think that you'll agree that engineers are very effective in their social
interactions.  It's the "normal" people who are nuts.
(Scott Adams - The Dilbert principle)
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Moved the navbar to the right

Description

Checklist:

[x] I've made sure that tests are updated accordingly (especially if adding or updating a template option)
[x] I've updated the documentation or confirm that my change doesn't require any updates

Rationale

Just moved the navbar to the right.

Wait lemme create a pull request again


Block Backfaces

A neat feature would be block backfaces. Would add to the 3D effect, as opposed to the UI disappearing when looking at it from behind.
I could see it being an optional attribute that is enabled via the constructor and set API. If enabled, the block would create a second frame like object and rotate it to be opposite of the main frame, to act as a simple backface. No need to mirror the content of the main frame, rather just be a solid or transparent color.
This can be done outside of the library, but I figured I'd see what thoughts are on supporting this idea.
Cheers,
Joe

Sort of an idea of what it could look like.
https://user-images.githubusercontent.com/83366171/121239422-d589f000-c85e-11eb-871c-6433c9b3d173.mp4


Error on bower install clappr

bower install clappr failed.
bower lodash.result#^3.1.2   ENOTFOUND Package lodash.result not found
Thanks

not sure but maybe refs to https://github.com/webpack/webpack/issues/332

bower lodash.result#^3.1.2   ENOTFOUND Package lodash.result not found
bower lodash.once#^3.0.1     ENOTFOUND Package lodash.once not found
bower lodash.find#^3.2.1     ENOTFOUND Package lodash.find not found
bower lodash.uniq#^3.2.2     ENOTFOUND Package lodash.uniq not found

duplicated


spatialization

spatialization 1: no spatialization

using an 'out' or 'outs' modules.
spatialization 2: auditing the cables
raycast instersecting with a cable
maybe handheld mic/probe
spatialization 3: vr.source~ strategycurrently in development i.e. speaker in msvr
spatialization 4: submix bubble

handled. see vr.source~/vr.context~ in mischmasch.maxpat


Merge profiler module into runtime

This is a part of #7620. Soft link profiler symbols in CUDART SoftLink. Depends on #7929.
This PR also removes cupy.cuda.profiler.initialize() function, which was removed in CUDA 12 and marked deprecated since CuPy v12 (#7332). Code search yields no use-case for this function.

Superseded by #7954


deps: gateway API bumped to v1.0.0

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #96
Does this PR introduce a user-facing change?:

Gateway API has been bumped to v1.0.0.

/cc @LiorLieberman

/cc @dpasiukevich

/lgtm

/lgtm
/approve


Upgrade lodash from ^4.17.11

Per https://github.com/lodash/lodash/issues/4348, an upgrade is required to address a recent security vulnerability CVE-2019-10744
https://github.com/benmosher/eslint-plugin-import/blob/master/package.json#L90 -- dependency currently out of date.

This CVS is a false positive for most, and semver already causes the update to happen, so nothing needs to be done here.


Error, failed to detect gcc version of backend compiler 'gcc'.

Please check whether the bug was already reported or fixed.
Hello, i have an problem to compile with nuitka.
I am using the command:
python -m nuitka --windows-icon-from-ico=ico.ico --onefile --windows-company-name=Zuna --windows-product-version=1.0 --plugin-enable=tk-inter main.py
Im getting the error: FATAL: Error, failed to detect gcc version of backend compiler 'gcc'.
libwinpthread-1.dll wasnt found.
Any Solutions or help please?
Nuitka version, full Python version, flavor, OS, etc. as output by this
1.1.2
Commercial: None
Python: 3.10.7 (tags/v3.10.7:6cc6b13, Sep 5 2022, 14:08:36) [MSC v.1933 64 bit (AMD64)]
Flavor: Unknown
Executable: C:\Users\jamu\AppData\Local\Programs\Python\Python310\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 10
How did you install Nuitka and Python
normal pip / standart interpreter
pip install nuitka
The specific PyPI names and versions
2captcha-python | 1.1.2 | 1.1.2
Eel | 0.14.0 | 0.14.0
Faker | 15.0.0 | 15.0.0
Flask | 1.1.4 | 2.2.2
Jinja2 | 2.11.3 | 3.1.2
Js2Py | 0.71 | 0.71
MarkupSafe | 2.1.1 | 2.1.1
MouseInfo | 0.1.3 | 0.1.3
Nuitka | 1.1.2 | 1.1.3
Pillow | 9.2.0 | 9.2.0
PyAutoGUI | 0.9.53 | 0.9.53
PyGetWindow | 0.0.9 | 0.0.9
PyMsgBox | 1.0.9 | 1.0.9
PyPrind | 2.11.3 | 2.11.3
PyRect | 0.2.0 | 0.2.0
PyScreeze | 0.1.28 | 0.1.28
PySocks | 1.7.1 | 1.7.1
PyYAML | 6.0 | 6.0
Pygments | 2.13.0 | 2.13.0
SpeechRecognition | 3.8.1 | 3.8.1
Telethon | 1.25.2 | 1.25.2
VaLID | 1.0.8 | 1.0.8
Werkzeug | 1.0.1 | 2.2.2
actions | 1.0.3 | 1.0.3
aiohttp | 3.8.1 | 3.8.3
aiosignal | 1.2.0 | 1.2.0
altgraph | 0.17.3 | 0.17.3
anyio | 3.6.1 | 3.6.1
appdirs | 1.4.4 | 1.4.4
astunparse | 1.6.3 | 1.6.3
async-generator | 1.10 |
async-timeout | 4.0.2 | 4.0.2
attrs | 22.1.0 | 22.1.0
auto-py-to-exe | 2.23.1 | 2.23.1
b | 1.0.0 | 1.0.0
barrier | 0.2.2 | 0.2.2
bcolors | 1.0.4 | 1.0.4
beautifulsoup4 | 4.11.1 | 4.11.1
bottle | 0.12.23 | 0.12.23
bottle-websocket | 0.2.9 | 0.2.9
bs4 | 0.0.1 | 0.0.1
bunch | 1.0.1 | 1.0.1
buttons | 0.1.9 | 0.1.9
certifi | 2022.6.15 | 2022.9.24
cffi | 1.15.1 | 1.15.1
charset-normalizer | 2.1.1 | 2.1.1
click | 7.1.2 | 8.1.3
codeclose | 1.0 |
colorama | 0.4.4 | 0.4.5
commonmark | 0.9.1 | 0.9.1
configobj | 5.0.6 | 5.0.6
configure | 0.5 | 0.5
contourpy | 1.0.5 | 1.0.5
cryptography | 38.0.1 | 38.0.1
cssselect | 1.1.0 | 1.1.0
curlify | 2.2.1 | 2.2.1
cursor | 1.3.5 | 1.3.5
cycler | 0.11.0 | 0.11.0
decorator | 5.1.1 | 5.1.1
discord.py | 2.0.1 | 2.0.1
distlib | 0.3.6 | 0.3.6
docopt | 0.6.2 | 0.6.2
driver | 0.1.0 | 0.1.0
fake-headers | 1.0.2 | 1.0.2
fake-useragent | 0.1.11 | 0.1.11
filelock | 3.8.0 | 3.8.0
flask-oidc | 1.4.0 | 1.4.0
fonttools | 4.37.4 | 4.37.4
frozenlist | 1.3.1 | 1.3.1
future | 0.18.2 | 0.18.2
gevent | 21.12.0 | 22.8.0
gevent-websocket | 0.10.1 | 0.10.1
greenlet | 1.1.3 | 1.1.3.post0
gunicorn | 19.10.0 | 20.1.0
h11 | 0.12.0 | 0.14.0
html5lib | 1.1 | 1.1
httmock | 1.4.0 | 1.4.0
http-request-randomizer | 1.3.2 | 1.3.2
httpcore | 0.13.7 | 0.15.0
httplib2 | 0.20.4 | 0.20.4
httpx | 0.19.0 | 0.23.0
idna | 3.3 | 3.4
importlib-metadata | 5.0.0 | 5.0.0
iso-639 | 0.4.5 | 0.4.5
iso8601 | 1.0.2 | 1.1.0
isodate | 0.6.1 | 0.6.1
itsdangerous | 1.1.0 | 2.1.2
joblib | 1.2.0 | 1.2.0
kiwisolver | 1.4.4 | 1.4.4
licensing | 0.37 | 0.37
lxml | 4.9.1 | 4.9.1
matplotlib | 3.6.0 | 3.6.1
multidict | 6.0.2 | 6.0.2
names | 0.3.0 | 0.3.0
numpy | 1.23.3 | 1.23.3
oauth2client | 4.1.3 | 4.1.3
ordered-set | 4.1.0 | 4.1.0
orq | 0.0.1 | 0.0.1
outcome | 1.2.0 | 1.2.0
packaging | 21.3 | 21.3
pandas | 1.5.0 | 1.5.0
parse | 1.19.0 | 1.19.0
pefile | 2022.5.30 | 2022.5.30
pip | 22.2.2 | 22.2.2
pipenv | 2022.9.21 | 2022.10.10
pipwin | 0.5.2 | 0.5.2
platformdirs | 2.5.2 | 2.5.2
playwright | 1.26.1 | 1.27.0
poetry-version | 0.1.5 | 0.2.0
psutil | 5.9.2 | 5.9.2
pyAesCrypt | 6.0.0 | 6.0.0
pyOpenSSL | 22.0.0 | 22.1.0
pySmartDL | 1.3.4 | 1.3.4
pyaes | 1.6.1 | 1.6.1
pyarmor | 7.7.0 | 7.7.0
pyasn1 | 0.4.8 | 0.4.8
pyasn1-modules | 0.2.8 | 0.2.8
pycountry | 22.3.5 | 22.3.5
pycparser | 2.21 | 2.21
pycryptodome | 3.15.0 | 3.15.0
pycryptodomex | 3.15.0 | 3.15.0
pyee | 8.1.0 | 9.0.4
pyfiglet | 0.8.post1 | 0.8.post1
pygame | 2.1.2 | 2.1.2
pyinstaller | 5.4.1 | 5.5
pyinstaller-hooks-contrib | 2022.10 | 2022.10
pyjsparser | 2.7.1 | 2.7.1
pyparsing | 3.0.9 | 3.0.9
pyperclip | 1.8.2 | 1.8.2
pyppeteer | 1.0.2 | 1.0.2
pyquery | 1.4.3 | 1.4.3
pystyle | 2.0 | 2.0
python-dateutil | 2.8.2 | 2.8.2
python-dotenv | 0.21.0 | 0.21.0
pytweening | 1.0.4 | 1.0.4
pytz | 2022.2.1 | 2022.4
pytz-deprecation-shim | 0.1.0.post0 | 0.1.0.post0
pywin32 | 304 | 304
pywin32-ctypes | 0.2.0 | 0.2.0
requests | 2.28.1 | 2.28.1
requests-html | 0.10.0 | 0.10.0
rfc3986 | 1.5.0 | 2.0.0
rich | 12.6.0 | 12.6.0
rsa | 4.9 | 4.9
scikit-learn | 1.1.2 | 1.1.2
scipy | 1.9.1 | 1.9.2
selenium | 4.4.3 | 4.5.0
self | 2020.12.3 | 2020.12.3
setuptools | 63.2.0 | 65.4.1
six | 1.16.0 | 1.16.0
sklearn | 0.0 | 0.0
sniffio | 1.3.0 | 1.3.0
sortedcontainers | 2.4.0 | 2.4.0
soupsieve | 2.3.2.post1 | 2.3.2.post1
streamlink | 5.0.1 | 5.0.1
sudo | 1.0.0 | 1.0.0
termcolor | 2.0.1 | 2.0.1
threadpoolctl | 3.1.0 | 3.1.0
tomlkit | 0.5.11 | 0.11.5
tqdm | 4.64.1 | 4.64.1
trio | 0.21.0 | 0.22.0
trio-websocket | 0.9.2 | 0.9.2
twitchAPI | <IP_ADDRESS> | <IP_ADDRESS>
twitchio | 2.4.0 | 2.4.0
typing-extensions | 4.3.0 | 4.4.0
tzdata | 2022.2 | 2022.4
tzlocal | 4.2 | 4.2
ui | 0.1.4 | 0.1.4
undetected-chromedriver | 3.1.5.post4 | 3.1.5.post4
urllib3 | 1.26.12 | 1.26.12
user-agent | 0.1.10 | 0.1.10
useragent | 0.1.1 | 0.1.1
virtualenv | 20.16.5 | 20.16.5
virtualenv-clone | 0.5.7 | 0.5.7
w3lib | 2.0.1 | 2.0.1
webdriver-manager | 3.8.3 | 3.8.3
webencodings | 0.5.1 | 0.5.1
websocket-client | 1.4.1 | 1.4.1
websockets | 10.1 | 10.3
wheel | 0.37.1 | 0.37.1
whichcraft | 0.6.1 | 0.6.1
wsproto | 1.2.0 | 1.2.0
yarl | 1.8.1 | 1.8.1
zipp | 3.8.1 | 3.9.0
zope.event | 4.5.0 | 4.5.0
zope.interface | 5.4.0 | 5.5.0
zstandard | 0.18.0 | 0.18.0

That is very strange. You must have a broken gcc somewhere in PATH environment. If you open a CMD.exe and type where gcc what do it say?

That is very strange. You must have a broken gcc somewhere in PATH environment. If you open a CMD.exe and type where gcc what do it say?

It says:
INFORMATION: No files could be found with the specified
patterns are found.

Can you execute it with --show-scons, then there should be a line coming from this code:
        scons_details_logger.info(
            "Error, error exit from '%s' (%d) gave %r." % (command, exit_code, stderr)
        )

I should be able to conclude from there. Thanks in advance.

Closing for lack of feedback.

Closing for lack of feedback.
It says:
INFORMATION: No files could be found with the specified
patterns are found.

again

Can you execute it with --show-scons, then there should be a line coming from this code:
        scons_details_logger.info(
            "Error, error exit from '%s' (%d) gave %r." % (command, exit_code, stderr)
        )

I should be able to conclude from there. Thanks in advance.

It says:
INFORMATION: No files could be found with the specified
patterns are found.
again.

I wanted the extra trace that I mentioned. I wasn't saying it will magically fix the error.

And how should i magically get the trace when it is not showing with the command?

Hard to tell, my best bet is that you have a CC or CXX environment variable set, that fails to work then. I am afraid you are too smart in being selecting in reporting the trace output. Had I seen it, even without the line, I would know a lot more.