Runtime element changing/cloning

I believe it's possible to implement feature like cloneElement in react. It could be really useful.
Example from react:
https://stackoverflow.com/a/50441271/8086153

Is there a suggestion?
I haven't really come up with a way that this feature makes sense. I do not see how it's possible. On one side there is already an element.cloneNode that is shipped in the browser. On the other side there is nothing to clone. Solid has no actual components. Cloning it would be like cloning a function and its closures with no way to interface with it.
There was discussion about this in #126 (most specifically this comment here: https://github.com/ryansolid/solid/issues/126#issuecomment-597810845). And a couple other places. I honestly have no idea how doing this could be possible.
Now it is possible I'm missing something but as I'm right now I have no ideas.

Yeah it is suggestion.
I think problem is not to clone, but to dynamically change existed nodes
Maybe it could be done at dom-expressions level?

for example, I need to change ref in Parent component
function Child(){
    return
 console.log('hello, world!')}/>
}
function Parent({children}){
    let childRef;
    const child = children[0];
    child.ref = (ref)=> childRef = ref;
    return
 Hello, {children}

}

My suggestion would be to create hook that should return new mutated children:
function Child(){
    return
 console.log('hello, world!')}/>
}
function Parent({children}){
    let childRef;
    childrenMounted((children)=>{
        children[0].ref = (ref) => childRef = ref;
    })
    return
 Hello, {children}

}

I'm not sure about this, could it be possible at least on transpile level?

Actually I do not know how refs are working it solid. Do they create at transpile time as links to nodes?

props.children in Solid is a constructor, not a bunch of VDOM nodes.
I mean this far for an actual static DOM node you can:
function Parent(props) {
  const { children } = props; // its static resolve it children === div
  // do whatever you want with children, then
  return
 Hello, {children}

}

However now insertion looks like:
<Parent>{state.condition && <Child/>}</Parent>

We no longer can static resolve. props.children changes. All we can do is intercept it. You would think something like:
function Parent(props) {
  const children = () => {
    const c = props.children;
    // do whatever with children;
    return c;
  }
  return
 Hello, {children()}

}

However, that isn't the end of the story. Since if you actually look at what that generates props.children returns a function:
https://solid-template-explorer.netlify.app/#DwBQhgTgpgdgLgPgN4Gc5jlAdAYwPYwAmAlnMQQAQBkVFwAwgBbEA2hA9AgL7DvjTwEQA
In fact, depending on how convoluted, you can have functions of functions of arrays of functions of functions etc.. This is what I call the reactive onioning. It is possible to unwind this backwards (I do with Context https://github.com/ryansolid/solid/blob/master/packages/solid/src/reactive/signal.ts#L747) and perhaps that is the method we need. I did a bit of this in solid-transition-group but that is a restrictive case since I know single DOM children. https://github.com/ryansolid/solid-transition-group/blob/master/src/Transition.ts#L28
Inserting in the DOM automatically handles all this resolution but probably too late. So I think you are looking for:
function Parent(props) {
  const children = () => {
    const c = resolveChildren(props.children);
    // do whatever with children;
    return c;
  }
  return
 Hello, {children()}

}

Refs work like this:
https://solid-template-explorer.netlify.app/#DwPgUABBwCYJYDcICcCmAzAvAbwM4HsBbVAFwAs4A7AcwF8IB6cKWRFDHAClQBsBKCJhAQCxclWqCIvekzDAmQA
They just do assignment or call functions at create time.

Now I get it.
In my case working example is
const children = createMemo(() => props.children);
***
  return (
    <For each={data()}>
      {(el, i) => {
        const child = children()(el, i);
        child.addEventListener('click', () => {
          onElementClick(i());
        });
        addRef(child);
        return child;
      }}
    </For>
  );

i think it should be further investigated by possible perfomance and ethic issues

Yeah.. I mean this is the last resort. Almost necessary to do certain types of DOM manipulation like animation co-ordination. I mostly try to suggests patterns where we inject on create to allow declarative syntax. Like in this case passing the click handler to the child template through the callback function... like:
<MyListWrapper>{
  ({ item, onClick }) =>
{item.title}

}</MyListWrapper>

The benefit here is it goes back to declarative where the compiler controls it. The trickiest thing about what you posted is it will never work on the Server.. which is fine for isomorphic we can just write different code path, say things aren't supported etc.. Like I'm not worried about Transition Groups working on the server. But if moved to declarative code structures we get this for free. Refs and Events won't fire and Effects won't run in the server.
Of course these patterns put onus on the end-user. Another way to do this is to pass up and pass down...
<MyListWrapper clickHandlerRef={getHandler}>{
  (item) =>
{item.title}

}</MyListWrapper>

This works less intrusive in cases where you don't already have a callback function...
Hmm... let's think out of the box. Could we create a Component for this? Problem is its internals would be the same as what we are doing here so no different than a helper function. It would need to be an intrinsic compiled element for this to work. Challenge is this would still have to be client only since reopening strings is off the table.
Not sure if anyone has other ideas. How do non-React libraries handle these things?

Just was shown this. Felt relevant here: https://kentcdodds.com/blog/how-to-give-rendering-control-to-users-with-prop-getters

I've manage to generalize a children helper which will give you a memo with the fully resolved children. I'm not doing any transforms like always an array or anything at this point. So wouldn't mind thoughts there. But I think that is the best we can do here. Can't clone so stuff like prop/getters and the other discussed methods are the only recourse, but atleast you can get the DOM elements and actually interact with them via an easy helper. This adds support for like putting <For> inside <Switch> etc.. it's in beta now but will be 0.24.0 when it is released.

I've manage to generalize a children helper which will give you a memo with the fully resolved children. I'm not doing any transforms like always an array or anything at this point. So wouldn't mind thoughts there. But I think that is the best we can do here. Can't clone so stuff like prop/getters and the other discussed methods are the only recourse, but atleast you can get the DOM elements and actually interact with them via an easy helper. This adds support for like putting <For> inside <Switch> etc.. it's in beta now but will be 0.24.0 when it is released.

Ok I've released it. You use it like:
const getChildren = children(() => props.children)

createEffect(() => {
   const children = getChildren();
   // do something
})

It creates a simple memo but what it does is fully resolve all the dynamic parts in between. So if the end dropped in a static list or use <For> to create those nodes it is all the same. It's the improved version of what you were doing. With this I think we've done all we can here.

@ryansolid Reading this discussion, I assume that something similar to Slot would be impossible to replicate in Solid? (I'm working on porting parts of Radix to Solid)

That's a weird example swapping the anchor in the button so I don't quite get the use case. But I mean reactivity can do anything. Just you have to recognize there is no virtual model in between. So when we update things those are real DOM nodes. But something like Slot doesn't really require anything that special.
https://playground.solidjs.com/?hash=-2011641040&version=1.3.3

That's really neat! Is spread documented anywhere?
As for the use case for this, usually, the prop as is used when you want to render your own component, similar to <Dynamic />, however, it comes with a bunch of TypeScript issues, so Radix came up with the idea for this Slot.

No that was the thing I've been hesitant documenting some of these just to keep things open for change in the future as the compiler APIs tend to be a bit less stable and it's fine because the runtime and compiler update in lockstep. To be fair this one hasn't really changed interface wise for years.
Biggest challenge with that approach is SSR. Spreading after the fact doesn't really work. It's just a string. Mind you maybe something special purpose. There is a question of if there is a more generalizable too potential here for this too like Dynamic. It's always challenging because this operation is platform specific so sort of vying into making it for all, but something that enhanced an existing element does seem useful. Could be worth looking into. Not going to lie Dynamic is probably the buggiest component to get right for SSR and this would be probably even more so. But better me take that on than anyone else.

Hmmm. Isn't there a way to somehow do the spreading at the compile step right now? Otherwise, do you recommend sticking with Dynamic?

Spreading can't really be done at compile time ever. We don't' know what is going to be passed in from a parent. Dynamic is doing the same thing. Spread is always a runtime de-opt in every framework. Requires pulling in code we wouldn't otherwise need. But what can you do?
More so with these after-the-fact approaches we've already created and serialized the thing. In the case of browser we have real DOM nodes.. in the case of the server it's just a string. In theory, might be able to find the end of the opening tag and insert some more strings.

My question is when we write {children()} the Component gets printed in the page by Solid so why can't we write something like: {children(addedProps)}


move to @ariatype namespace

Hi, maintainer of ariatype here. The project was previously under the @dddstack namespace; however, now will be under @ariatype going forward.
@dddstack namespace packages will be deprecated and any future updates will be on the @ariatype namespace packages. All types and imports will remain the same, feel free to look at the documentation.
Very cool project!

Thanks for building @dddstack and @ariatype.


added a "unsubscribe from all" method and a test to back it up.

This is an attempt at fixing #25.

@ffMathy - the 0.5.0 release now has a reset method that will clear all ko.postbox subscriptions. I had to add some more comprehensive tracking of subscriptions to capture all subscriptions created directly (ko.postbox.subscribe) vs. the observable extensions. The postboxSubs object only exists on individual subscribables (observables, observableArrays, computeds). Thanks for your PR!


Updated code comment, fixed typo

This approach it --> This approach is

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Codecov Report

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

@@            Coverage Diff             @@
##           master    #4763      +/-   ##
==========================================
- Coverage   53.73%   49.83%    -3.9%
==========================================
  Files       10328     6207    -4121
  Lines      217144   174146   -42998
==========================================
- Hits       116686    86791   -29895
+ Misses     100458    87355   -13103

Impacted Files
Coverage Δ

...ure-servicebus/azure/servicebus/receive_handler.py
21.33% <ø> (ø)
:arrow_up:

...afactory/azure/mgmt/datafactory/models/__init__.py
50.67% <0%> (-49.33%)
:arrow_down:

...ights/azure/applicationinsights/models/__init__.py
51% <0%> (-49%)
:arrow_down:

...e/cognitiveservices/vision/face/models/__init__.py
51.08% <0%> (-48.92%)
:arrow_down:

...services/language/textanalytics/models/__init__.py
51.16% <0%> (-48.84%)
:arrow_down:

...iveservices/search/entitysearch/models/__init__.py
51.25% <0%> (-48.75%)
:arrow_down:

azure-eventgrid/azure/eventgrid/models/__init__.py
51.25% <0%> (-48.75%)
:arrow_down:

...ration/azure/mgmt/datamigration/models/__init__.py
51.27% <0%> (-48.73%)
:arrow_down:

...ure/mgmt/recoveryservicesbackup/models/__init__.py
51.46% <0%> (-48.54%)
:arrow_down:

...ce/azure/mgmt/containerinstance/models/__init__.py
51.8% <0%> (-48.2%)
:arrow_down:

... and 4207 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 095af34...27f7066. Read the comment docs.

please ignore


Unable to find image 'openmmlab/lmdeploy:latest' locally

Install following the readme process, facing the upfront problem.
I am deploying llama2-chat-7b

Did you login docker hub?
It is supposed to download openmmlab/lmdeploy:latest automatically if this image can't be found locally.


Update haskell.nix and HLS

[x] Bump haskell.nix
[x] Try bumping Haskell Language Server to <IP_ADDRESS>

Comments

Build got stuck locally; trying in CI
Seems to build fine, but HLS doesn't seem updated (when I tried changing manually, it was reverted by the automatic nix regeneration)

Issue Number

Closing for now

This is what I got when trying to run nix-shell locally:
trace: ERROR: cabal configure failed with:
Warning: The package list for 'hackage.haskell.org-at-2021-10-05T000000Z' is
18954 days old.
Run 'cabal update' to get the latest list of available packages.
Warning: Requested index-state 2021-10-05T00:00:00Z is newer than
'hackage.haskell.org-at-2021-10-05T000000Z'! Falling back to older state
(2021-10-04T22:59:49Z).
Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: haskell-language-server-<IP_ADDRESS> (user goal)
[__1] trying: haskell-language-server:+eval
[__2] next goal: hls-eval-plugin (dependency of haskell-language-server +eval)
[__2] rejecting: hls-eval-plugin-<IP_ADDRESS>, hls-eval-plugin-<IP_ADDRESS>,
hls-eval-plugin-<IP_ADDRESS>, hls-eval-plugin-<IP_ADDRESS>, hls-eval-plugin-<IP_ADDRESS>,
hls-eval-plugin-<IP_ADDRESS>, hls-eval-plugin-<IP_ADDRESS>, hls-eval-plugin-<IP_ADDRESS>,
hls-eval-plugin-<IP_ADDRESS>, hls-eval-plugin-<IP_ADDRESS>, hls-eval-plugin-<IP_ADDRESS>
(conflict: haskell-language-server +eval => hls-eval-plugin^>=<IP_ADDRESS>)
[__2] fail (backjumping, conflict set: haskell-language-server,
hls-eval-plugin, haskell-language-server:eval)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: haskell-language-server,
haskell-language-server:eval, hls-eval-plugin

Let's try again with latest Hackage and index-state.

bors r+


dynamic route name

This PR is related to the Issue #27
I need to localize the route names displayed in breadcrumbs. I have a language switcher on the page which changes site locale without page reloading and breadcrumbs should dynamically change together with the rest of the page. The idea is to generate a name by a custom function when required.
I changed usage of JSON.parse(JSON.stringify(_route)) to Object.assign because JSON serialization/deserialization removes all the functions from an object making it impossible to pass a name generation function in route props.
Now a route definition may look as follows:
<Router history={browserHistory}>
        <Route
          name="Home"
          getDisplayName={() => l20nMessage('homeTitle', 'Home')}
          id="APP"
          path={routes.APP.path}
          component={Layout}
        >
          <Route
            id="PORTAL"
            name="Portal"
            getDisplayName={() => l20nMessage('portalTitle', 'Portal')}
            path={routes.PORTAL.path}
            component={PortalPage}
          />
...

Looks cool!
One question about dynamic route name: How would you make the dynamic route name use data resolved in the route component? For instance:
<Route path="/users/:userId" component={User} />

Currently, the breadcrumb will display a static name or the :userId parameter. What would be great would be to display instead the firstName and lastName of the user which is available in the component.


Is there any way to overwrite on_error event?

What I wanted to do is
I can see ws client having on_error but it just logs the error would be helpful if we can get access to it
        try:
            auth = PasswordAuth(reddit_username=self.username,
                                reddit_password=self.password)
            self.bot = ChatBot(authentication=auth, store_session=False)
        except Exception as e:
            logger.error(f"{Fore.RED}Failed to log in {e} for {a['username']}{Fore.RESET}")
            return

        @self.bot.event.on_error
        def on_error(_):
            print("Some error occured", _)

        @self.bot.event.on_ready
        def on_ready(_):
            logger.info(f"{Fore.GREEN}{self.bot.get_own_name()} ready!{Fore.RESET}")

        self.bot.run_4ever(auto_reconnect=True)

EDIT: same goes for on_close

which on_error do you mean? the errors from the websocket or reddit?


Tweak requirements

sckitbeam and databroker are now in pypi, no need for git installs
metadatastore and filestore are deprecated and should not be installed
should not be installing sip explicitly
should not be installing attrs directly (databroker dependency)

Need git+...ModestImage as well I think

There are some changes in https://github.com/yugangzhang/chxanalys/blob/master/requirements.txt, which was updated first. I don't like the fact this main NSLS-II-CHX repo is forked from Yugang's one.

We should ask github to fix that...

I just pinged github support to fix the 'upstream' ness.

if there was an alternative to deleting/recreating that would be great!

Looks good, eiger-io dependency will be updated separately.


Branch 2.4

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

Hi, @un-knower . Could you close this?

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Remote paths

:white_check_mark: Build TheIdServer 1.0.0-user-ole0034 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/7d069637eb by @aguacongas)

:white_check_mark: Build TheIdServer 1.0.0-user-ole0035 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/1e2e24aa75 by @aguacongas)

:white_check_mark: Build TheIdServer 1.0.0 -user-ole0051 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/c608999637 by @aguacongas)


Cant create a project

when i try to create a project i cant type its name and when i go back from beardlib menu or beardlib editor menu i cant click anywhere

works fine for me
You'll have to provide extra info like screenshot, blt log in the issue report.

i cant type in here

after backing out i cant click anywhere

You didn't give me all that I need

what do you need

2019_08_15_log.txt

Odd no idea what's going on

well fuck

thanks tho

is there way to create a project without going there

Remove all mods and see if that works

tried it didnt work

with or without the mods same

Gonna close for now, not sure what is the issue as much.


Figure out why Docker compose is failing in CI

With so many integration tests, we're hitting this failure very very frequently now:
Error response from daemon: driver failed programming external connectivity on endpoint ftl-db-1 (77de40e71a5a9b79309209ca12abdb5f67ca1faefcab7fce30ceaa2891f560e0): Error starting userland proxy: listen tcp4 <IP_ADDRESS>:54320: bind: address already in use

It doesn't seem to be an issue with FTL itself, but it would be great to fix it because it's really annoying.

Examples
https://github.com/TBD54566975/ftl/actions/runs/9460605277/job/26059731611#step:5:564
https://github.com/TBD54566975/ftl/actions/runs/9457427212/job/26051227590#step:5:585
https://github.com/TBD54566975/ftl/actions/runs/9457388106/job/26051102482#step:5:597
https://github.com/TBD54566975/ftl/actions/runs/9444996323/job/26011687680#step:5:573
Seen on "Integration Test" matrix and "Test Go"

@gak volunteered as tribute

The postgres port is always triggering the error.
The port is not used immediately beforehand.

tcp6       0      0 <IP_ADDRESS>:54320        <IP_ADDRESS>:443        ESTABLISHED 592/provisioner

Processes are randomly choosing high ports as the source port, randomly hitting 54320. Just need to choose a lower port under that range.


Update UI colours

Update UI colours, so that they match a new OCF palette https://coolors.co/ffd053-ffac5f-e4e4e4-14120e-48b0df-63bcaf-70c2b6

This is a duplication of an earlier issue


'whisper' is not recognized as an internal or external command, operable program or batch file.

Installed the package according to readme.md and tried to run command, but the following error occurred:
PS D:\python\transcriber> transcribe-anything https://www.youtube.com/watch?v=dQw4w9WgXcQ
'whisper' is not recognized as an internal or external command,
operable program or batch file.
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "D:\Program Files (x86)\python\3115\Scripts\transcribe-anything.exe\__main__.py", line 7, in <module>
  File "D:\Program Files (x86)\python\3115\Lib\site-packages\transcribe_anything\_cmd.py", line 154, in main
    args = parse_arguments()
           ^^^^^^^^^^^^^^^^^
  File "D:\Program Files (x86)\python\3115\Lib\site-packages\transcribe_anything\_cmd.py", line 60, in parse_arguments
    whisper_options = get_whisper_options()
                      ^^^^^^^^^^^^^^^^^^^^^
  File "D:\Program Files (x86)\python\3115\Lib\site-packages\transcribe_anything\_cmd.py", line 52, in get_whisper_options
    whisper_options = parse_whisper_options()
                      ^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\Program Files (x86)\python\3115\Lib\site-packages\transcribe_anything\parse_whisper_options.py", line 28, in parse_whisper_options
    stdout = subprocess.check_output(
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\Program Files (x86)\python\3115\Lib\subprocess.py", line 466, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\Program Files (x86)\python\3115\Lib\subprocess.py", line 571, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'whisper --help' returned non-zero exit status 1.

Same here.
Event pip install whisper does not solve the situation.

Same here

I see that people are using powershell, does this also fail when launching from cmd.exe?

I see that people are using powershell, does this also fail when launching from cmd.exe?

Yes, I tried to run the command in admin cmd and the same prompt appeared as well.

In cmd I ran into the same problem:
C:\Users\Aaron\Downloads\>sudo py -3.10 -m pip install transcribe-anything
WARNING: Ignoring invalid distribution -overage (c:\python310\lib\site-packages)
WARNING: Ignoring invalid distribution -ip (c:\python310\lib\site-packages)
WARNING: Ignoring invalid distribution -overage (c:\python310\lib\site-packages)
WARNING: Ignoring invalid distribution -ip (c:\python310\lib\site-packages)
Collecting transcribe-anything
  Using cached transcribe_anything-2.7.38-py2.py3-none-any.whl (33 kB)
Requirement already satisfied: isolated-environment~=2.0.0 in c:\python310\lib\site-packages (from transcribe-anything) (2.0.0)
Requirement already satisfied: FileLock in c:\python310\lib\site-packages (from transcribe-anything) (3.15.4)
Requirement already satisfied: yt-dlp>=2023.3.4 in c:\python310\lib\site-packages (from transcribe-anything) (2024.8.6)
Requirement already satisfied: webvtt-py==0.4.6 in c:\python310\lib\site-packages (from transcribe-anything) (0.4.6)
Requirement already satisfied: disklru>=1.0.7 in c:\python310\lib\site-packages (from transcribe-anything) (1.0.7)
Requirement already satisfied: appdirs==1.4.4 in c:\python310\lib\site-packages (from transcribe-anything) (1.4.4)
Requirement already satisfied: static-ffmpeg>=2.7 in c:\python310\lib\site-packages (from transcribe-anything) (2.7)
Requirement already satisfied: docopt in c:\python310\lib\site-packages (from webvtt-py==0.4.6->transcribe-anything) (0.6.2)
Requirement already satisfied: setuptools in c:\python310\lib\site-packages (from isolated-environment~=2.0.0->transcribe-anything) (65.5.0)
Requirement already satisfied: semver in c:\python310\lib\site-packages (from isolated-environment~=2.0.0->transcribe-anything) (3.0.2)
Requirement already satisfied: wheel in c:\python310\lib\site-packages (from isolated-environment~=2.0.0->transcribe-anything) (0.44.0)
Requirement already satisfied: requests in c:\python310\lib\site-packages (from static-ffmpeg>=2.7->transcribe-anything) (2.32.3)
Requirement already satisfied: brotli in c:\python310\lib\site-packages (from yt-dlp>=2023.3.4->transcribe-anything) (1.1.0)
Requirement already satisfied: websockets>=12.0 in c:\python310\lib\site-packages (from yt-dlp>=2023.3.4->transcribe-anything) (12.0)
Requirement already satisfied: urllib3<3,>=1.26.17 in c:\python310\lib\site-packages (from yt-dlp>=2023.3.4->transcribe-anything) (2.2.2)
Requirement already satisfied: certifi in c:\python310\lib\site-packages (from yt-dlp>=2023.3.4->transcribe-anything) (2024.7.4)
Requirement already satisfied: pycryptodomex in c:\python310\lib\site-packages (from yt-dlp>=2023.3.4->transcribe-anything) (3.20.0)
Requirement already satisfied: mutagen in c:\python310\lib\site-packages (from yt-dlp>=2023.3.4->transcribe-anything) (1.47.0)
Requirement already satisfied: idna<4,>=2.5 in c:\python310\lib\site-packages (from requests->static-ffmpeg>=2.7->transcribe-anything) (3.7)
Requirement already satisfied: charset-normalizer<4,>=2 in c:\python310\lib\site-packages (from requests->static-ffmpeg>=2.7->transcribe-anything) (3.3.2)
WARNING: Ignoring invalid distribution -overage (c:\python310\lib\site-packages)
WARNING: Ignoring invalid distribution -ip (c:\python310\lib\site-packages)
Installing collected packages: transcribe-anything
WARNING: Ignoring invalid distribution -overage (c:\python310\lib\site-packages)
WARNING: Ignoring invalid distribution -ip (c:\python310\lib\site-packages)
Successfully installed transcribe-anything-2.7.38
WARNING: Ignoring invalid distribution -overage (c:\python310\lib\site-packages)
WARNING: Ignoring invalid distribution -ip (c:\python310\lib\site-packages)
WARNING: Ignoring invalid distribution -overage (c:\python310\lib\site-packages)
WARNING: Ignoring invalid distribution -ip (c:\python310\lib\site-packages)
WARNING: There was an error checking the latest version of pip.

C:\Users\Aaron\Downloads>sudo transcribe-anything --help
Der Befehl "whisper" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
Traceback (most recent call last):
  File "C:\Python310\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Python310\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "C:\Python310\Scripts\transcribe-anything.EXE\__main__.py", line 7, in <module>
  File "C:\Python310\lib\site-packages\transcribe_anything\_cmd.py", line 154, in main
    args = parse_arguments()
  File "C:\Python310\lib\site-packages\transcribe_anything\_cmd.py", line 60, in parse_arguments
    whisper_options = get_whisper_options()
  File "C:\Python310\lib\site-packages\transcribe_anything\_cmd.py", line 46, in get_whisper_options
    whisper_options = parse_whisper_options()
  File "C:\Python310\lib\site-packages\transcribe_anything\parse_whisper_options.py", line 28, in parse_whisper_options
    stdout = subprocess.check_output(
  File "C:\Python310\lib\subprocess.py", line 421, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "C:\Python310\lib\subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'whisper --help' returned non-zero exit status 1.

managed to install openai-whisper. Still doesn't recognize it :/
C:\Users\Aaron\Downloads>sudo transcribe-anything --help
Der Befehl "whisper" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
Traceback (most recent call last):
  File "C:\Python310\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Python310\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "C:\Python310\Scripts\transcribe-anything.EXE\__main__.py", line 7, in <module>
  File "C:\Python310\lib\site-packages\transcribe_anything\_cmd.py", line 154, in main
    args = parse_arguments()
  File "C:\Python310\lib\site-packages\transcribe_anything\_cmd.py", line 60, in parse_arguments
    whisper_options = get_whisper_options()
  File "C:\Python310\lib\site-packages\transcribe_anything\_cmd.py", line 46, in get_whisper_options
    whisper_options = parse_whisper_options()
  File "C:\Python310\lib\site-packages\transcribe_anything\parse_whisper_options.py", line 28, in parse_whisper_options
    stdout = subprocess.check_output(
  File "C:\Python310\lib\subprocess.py", line 421, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "C:\Python310\lib\subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'whisper --help' returned non-zero exit status 1.

C:\Users\Aaron\Downloads>whisper
usage: whisper [-h] [--model MODEL] [--model_dir MODEL_DIR] [--device DEVICE] [--output_dir OUTPUT_DIR]
               [--output_format {txt,vtt,srt,tsv,json,all}] [--verbose VERBOSE] [--task {transcribe,translate}]
               [--language {af,am,ar,as,az,ba,be,bg,bn,bo,br,bs,ca,cs,cy,da,de,el,en,es,et,eu,fa,fi,fo,fr,gl,gu,ha,haw,he,hi,hr,ht,hu,hy,id,is,it,ja,jw,ka,kk,km,kn,ko,la,lb,ln,lo,lt,lv,mg,mi,mk,ml,mn,mr,ms,mt,my,ne,nl,nn,no,oc,pa,pl,ps,pt,ro,ru,sa,sd,si,sk,sl,sn,so,sq,sr,su,sv,sw,ta,te,tg,th,tk,tl,tr,tt,uk,ur,uz,vi,yi,yo,yue,zh,Afrikaans,Albanian,Amharic,Arabic,Armenian,Assamese,Azerbaijani,Bashkir,Basque,Belarusian,Bengali,Bosnian,Breton,Bulgarian,Burmese,Cantonese,Castilian,Catalan,Chinese,Croatian,Czech,Danish,Dutch,English,Estonian,Faroese,Finnish,Flemish,French,Galician,Georgian,German,Greek,Gujarati,Haitian,Haitian Creole,Hausa,Hawaiian,Hebrew,Hindi,Hungarian,Icelandic,Indonesian,Italian,Japanese,Javanese,Kannada,Kazakh,Khmer,Korean,Lao,Latin,Latvian,Letzeburgesch,Lingala,Lithuanian,Luxembourgish,Macedonian,Malagasy,Malay,Malayalam,Maltese,Mandarin,Maori,Marathi,Moldavian,Moldovan,Mongolian,Myanmar,Nepali,Norwegian,Nynorsk,Occitan,Panjabi,Pashto,Persian,Polish,Portuguese,Punjabi,Pushto,Romanian,Russian,Sanskrit,Serbian,Shona,Sindhi,Sinhala,Sinhalese,Slovak,Slovenian,Somali,Spanish,Sundanese,Swahili,Swedish,Tagalog,Tajik,Tamil,Tatar,Telugu,Thai,Tibetan,Turkish,Turkmen,Ukrainian,Urdu,Uzbek,Valencian,Vietnamese,Welsh,Yiddish,Yoruba}]
               [--temperature TEMPERATURE] [--best_of BEST_OF] [--beam_size BEAM_SIZE] [--patience PATIENCE]
               [--length_penalty LENGTH_PENALTY] [--suppress_tokens SUPPRESS_TOKENS] [--initial_prompt INITIAL_PROMPT]
               [--condition_on_previous_text CONDITION_ON_PREVIOUS_TEXT] [--fp16 FP16]
               [--temperature_increment_on_fallback TEMPERATURE_INCREMENT_ON_FALLBACK]
               [--compression_ratio_threshold COMPRESSION_RATIO_THRESHOLD] [--logprob_threshold LOGPROB_THRESHOLD]
               [--no_speech_threshold NO_SPEECH_THRESHOLD] [--word_timestamps WORD_TIMESTAMPS]
               [--prepend_punctuations PREPEND_PUNCTUATIONS] [--append_punctuations APPEND_PUNCTUATIONS]
               [--highlight_words HIGHLIGHT_WORDS] [--max_line_width MAX_LINE_WIDTH] [--max_line_count MAX_LINE_COUNT]
               [--max_words_per_line MAX_WORDS_PER_LINE] [--threads THREADS]
               audio [audio ...]
whisper: error: the following arguments are required: audio


Breakout of UI into napari-recorder

As mentioned in #38, we will likely have to breakout a smaller repo napari-recorder that contains at minimum the napari_entry_point.py file which instantiates a napari plugin.  This is due to Napari requiring that the repo distribution name conforms to PEP8 for being a recognizable napari plugin.
The idea for this would be to potentially have all of what lives under recOrder/plugin be migrated to a new repo that has recOrder as a dependency.  recOrder could also have the napari-recorder listed as a dependency as well, so a user could just install recOrder in order to have full access to the plugin.
The issue comes with development -- its quite difficult to do efficient development simultaneously on two different repos, so this separation will likely occur once the repo has stabilized.

Not necessary anymore with npe2 napari plugin engine


Move JaegerFeature from jaeger-dropwizard to jaeger-jaxrs2

JaegerFeature implements javax.ws.rs.core.Feature and does not require any dropwizard specific classes.

Closing in favor of #182


Data available in iControl REST is missing from Telemetry Streaming.

Is your feature request related to a problem? Please describe.
I'm migrating an application that is using iControl REST API calls to Telemetry Streaming.   Not all the data that we are gathering via iControl is available from TS.  So far, I've identified these bits of data that we collect from iControl that I can't find in TS:

From /mgmt/tm/cm/device, we collect the edition attribute
From /mgmt/tm/net/self, we collect the name, floating, address and vlan attributes
From /mgmt/tm/ltm/virtual, we collect the sourceAddressTranslation.type attribute

Describe the solution you'd like
I'd like to see these attributes available from TS.  (My guess is that there is a lot of information available in iControl that is not in TS, but that is only a guess.  If I'm right, is there a plan to get all the missing bits in TS?)
Describe alternatives you've considered
I have to make iControl REST API calls to collect the bits I can't get from TS.
Additional context
Add any other context or screenshots about the feature request here.

F5 BIG-IP Telemetry Streaming is entering a phase of ongoing maintenance and support. A product in maintenance mode continues to receive support and ensures its stability with regular critical fixes and security updates. This maintenance approach helps maintain the longevity and reliability of the product for the long term. Enhancement requests for this product will be evaluated on an individual basis, taking into consideration their overall impact and alignment with our business objectives. Only those with a strong case for improvement will be considered for implementation. There is no plan to deprecate this product. If you have a business case for this, please let me know and I will let you know how to contact us. Thank you


cargo miri setup failing on custom target

I am attempting to use Miri in a bare metal project using my custom target. When I run cargo miri setup --target MY_TARGET, it prepares a sysroot for the target, but fails with:
error[E0464]: multiple candidates for `rmeta` dependency `core` found
 --> /home/binds/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/rustc-std-workspace-core/lib.rs:4:9
  |
4 | pub use core::*;
  |         ^^^^
  |
  = note: candidate #1: /tmp/.tmpSCntaC/target/x86_64-prestige/release/deps/libcore-5484c1dfc1494680.rmeta
  = note: candidate #2: /tmp/.tmpSCntaC/target/x86_64-prestige/release/deps/libcore-fe8fccd3bdf8e7b3.rmeta

For more information about this error, try `rustc --explain E0464`.
error: could not compile `rustc-std-workspace-core` due to previous error
fatal error: failed to build sysroot: sysroot build failed

I am at a loss for what could be causing this. Even if I cargo clean, the same error occurs. I will put anything I believe relevant to help solve this:
rustc -vV:
rustc 1.69.0-nightly (e972bc808 2023-01-29)
binary: rustc
commit-hash: e972bc8083d5228536dfd42913c8778b6bb04c8e
commit-date: 2023-01-29
host: x86_64-unknown-linux-gnu
release: 1.69.0-nightly
LLVM version: 15.0.7

My custom target:
{
    "llvm-target": "x86_64-unknown-none",
    "data-layout": "e-m:e-i64:64-f80:128-n8:16:32:64-S128",
    "arch": "x86_64",
    "target-endian": "little",
    "target-pointer-width": "64",
    "target-c-int-width": "32",
    "os": "none",
    "executables": true,
    "linker-flavor": "ld.lld",
    "linker": "rust-lld",
    "panic-strategy": "abort",
    "disable-redzone": true,
    "features": "-mmx,-sse,+soft-float",
    "code-model": "kernel",
    "pre-link-args": {
        "ld.lld": [
            "--gc-sections",
            "-T.cargo/linker.ld"
        ]
    }
}

It seems like JSON targets began to be supported as of #2744, so I don't think its an issue with Miri's support for it.
.cargo/config.toml:
[unstable]
build-std = ["core", "compiler_builtins", "alloc"]
build-std-features = ["compiler-builtins-mem"]

rust-toolchain.toml:
[toolchain]
channel = "nightly"
components = ["rust-src", "rustfmt", "clippy", "miri"]

The error looks similar to https://github.com/rust-lang/miri/issues/2705... Does 'cargo miri setup' without --target work?

The error looks similar to https://github.com/rust-lang/miri/issues/2705... Does 'cargo miri setup' without --target work?

No, it does not

So, exact duplicate of https://github.com/rust-lang/miri/issues/2705?
In that case please post over there with your OS details, and the output of cargo miri setup -v. I am at a complete loss about what might be causing this but maybe there's a pattern...


Created self-contained React mockup of FAQ

The mockup uses Bootstrap styling and functionality with the ability to programmatically create new FAQ entries using React props. Unlike the current FAQs on Appalachian websites, multiple question dropdowns can be opened simultaneously, hopefully boosting user experience.

I'm going to keep the wip (work in progress) branch open for future development.


Let's actually hire someone

Nice! Once this is up you should consider posting in the georust discord.

Nice! Once this is up you should consider posting in the georust discord.

Yep, it's finally happening -- Robin pulled some administrative magic. 100% going to advertise to georust!

I'll interpret approval as mergeable!


OpTestPNOR: Run this test on Host as well.

As we can easily upgrade the pflash tool using upstream skiboot on
host instead of petitboot, lets make it this test run on host as well.
So we can catch pflash bugs early, instead of waiting for petitboot
pflash to bump through op-build.
Signed-off-by: Pridhiviraj Paidipeddi<EMAIL_ADDRESS>

Merged to master as of 8a6531d5fb5cf4cd564b6fc1b0c712ca48902ae3


Accidentally dora command is unresponsive and stuck

Describe the bug
Accidentally dora command is unresponsive and stuck
To Reproduce
Steps to reproduce the behavior:

Few cases，when executing command dora up , dora start dataflow.yaml,  dora stop, dora destroy

Environments (please complete the following information):

System info: Linux jia 5.15.0-69-generic #76~20.04.1-Ubuntu SMP Mon Mar 20 15:54:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Dora version：0.2.2

Could you give us more details on how to reproduce this issue?

I think I can reproduce the issue with:
dora up
dora destroy
dora up # <--- This hangs

I think it is due the coordinator waiting for something which makes it unable to respond to other request.

Hmm, I tried it multiple times but I couldn't reproduce the issue on the main branch. Which dora version are you using @haixuanTao ?

Yep, I think, I will investigate on my end

Thanks!

reproduce the problem again, the steps are as shown above.
The premise is that dora start has an exception, as shown below:

@phil-opp

the service 'dora daemon' hung up.

I think it's probably linked to the operator yolov5 not accessing github, stucking the initialisation function. But it's going to be very hard for Philipp to reproduce.

Having retested this issue, this is the stack trace:
(base) ~/D/C/dora ❯❯❯ RUST_LOG=trace dora destroy                                           (base) fix-coordinator-loop ✭
  2023-04-25T08:21:11.484181Z TRACE dora_coordinator::control: Control connection closed
    at binaries/coordinator/src/control.rs:90

  2023-04-25T08:21:11.484197Z TRACE dora_coordinator: Handling event Control(IncomingRequest { request: Destroy, reply_sender: Sender { inner: Some(Inner { state: State { is_complete: false, is_closed: false, is_rx_task_set: true, is_tx_task_set: false } }) } })
    at binaries/coordinator/src/lib.rs:142

  2023-04-25T08:21:11.484227Z  INFO dora_coordinator: Received destroy command
    at binaries/coordinator/src/lib.rs:403

  2023-04-25T08:21:11.484359Z  INFO dora_daemon: received destroy command -> exiting
    at binaries/daemon/src/lib.rs:331
    in dora_daemon::run_inner with self.machine_id:

Send destroy command to dora-coordinator
  2023-04-25T08:21:11.484604Z TRACE dora_coordinator::control: Control connection closed
    at binaries/coordinator/src/control.rs:90

It seems to be due to this: Control connection closed which happens because there is an ErrorKind::UnexpectedEof
Looking at running process the dora daemon has exited.
This is probably linked to an error on sending a confirmation of the dora daemon to the coordinator to have been successfully destroyed.

It seems to be due to this TRACE: Control connection closed which happens because there is an ErrorKind::UnexpectedEof

This is expected, as the CLI closes it's control connection to the coordinator when it exits.

The premise is that dora start has an exception, as shown below:

This seems to be the real issue here. The python operator seems to require GLIBCXX_3.4.29 (required by matplotlib), but it is not found. This error brings down the whole runtime node. I'm not sure why the daemon does not detect this error, but my guess is that it is stuck waiting for the node to finish initialization (for the synchronized start introduced in #236).
So I think there are two things that we need to look into:

Why is the mentioned GLIBCXX version required, but not found?
Why doesn't the dora daemon detect the operator/node initialization error?

I opened #271 to track this issue: Why doesn't the dora daemon detect the operator/node initialization error?

Does this issue still happen on the latest version (i.e. with #271 merged)?

Does this issue still happen on the latest version (i.e. with #271 merged)?

The situation described above has not happened again, but there is still a situation where dora stop cannot stop dataflow. This problem occurs because an exception occurs inside an operator that dataflow depends on, as shown below:
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$ dora list
Running dataflows:
- [YOLOv8] 4aba7bb7-7966-4839-921d-72c575f7ea33
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$ dora stop
> Choose dataflow to stop: [YOLOv8] 4aba7bb7-7966-4839-921d-72c575f7ea33
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$ dora list
Running dataflows:
- [YOLOv8] 4aba7bb7-7966-4839-921d-72c575f7ea33
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$ dora -V
dora-cli 0.2.3
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$

vi webcam_yolov8.yaml
nodes:
  - id: webcam
    operator:
      python: ../../operators/webcam_op.py
      inputs:
        tick: dora/timer/millis/100
      outputs:
        - image
    env:
      DEVICE_INDEX: 2

  - id: yolov8
    operator:
      outputs:
        - bbox
      inputs:
        image: webcam/image
      python: ../../operators/yolov8_op.py
    env:
      PYTORCH_DEVICE: "cuda"
#      YOLOV8_PATH: $DORA_DEP_HOME/dependencies/YOLOv8/
#      YOLOV8_WEIGHT_PATH: $DORA_DEP_HOME/dependencies/YOLOv8/weights/yolov8n.pt

  - id: plot
    operator:
      python: ../../operators/plot.py
      inputs:
        image: webcam/image
        obstacles_bbox: yolov8/bbox

(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$ RUST_LOG=true dora start graphs/tutorials/webcam_yolov8.yaml --attach --hot-reload --name YOLOv8
4aba7bb7-7966-4839-921d-72c575f7ea33
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$

Does this issue still happen on the latest version (i.e. with #271 merged)?

v0.2.3 problem still exists, dora-cli unresponsive.
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$ dora destroy
  2023-06-27T09:32:54.865121Z  WARN dora_daemon::node_communication: failed to send event to daemon

Location:
    /home/runner/work/dora/dora/binaries/daemon/src/node_communication/mod.rs:490:26
    at binaries/daemon/src/node_communication/mod.rs:253

  2023-06-27T09:32:54.865152Z  WARN dora_daemon::node_communication: failed to receive reply from daemon

Location:
    /home/runner/work/dora/dora/binaries/daemon/src/node_communication/mod.rs:494:30
    at binaries/daemon/src/node_communication/mod.rs:253

Send destroy command to dora-coordinator
(dora3.7) jarvis@jia:~/coding/pyhome/github.com/dora-rs/dora-drives$ dora list

To Reproduce
Steps to reproduce the behavior:

Dora start daemon: dora up
Start a new dataflow: dora start graphs/tutorials/webcam_yolov5.yaml --attachml --attach

Screenshots or Video

Environments (please complete the following information):

System info: ubuntu 20.04 LTS
Dora version: v0.2.3


create mixer CRDs by invoking mixs crd all

fixes #2565

@jmuk any status here?  is this PR still needed?

Why was this PR closed? I'd be nice if the CRDs were created automatically so that things don't get missed/out of date. Ideally #8003 gets fixed and doesn't happen again in any future releases.


Fixed slide over lapping on zoom

Summary
Based on Issue closes Positions element #7
Fixes  #7
Test Plan

Checklist

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you written closes #XXXX in your comment to auto-close the issue that your PR addresses?
[x] Does your submission pass tests?
[ ] Have you linted your code locally prior to submission?

can we have a deploy? :D that fix is what I need on a project of mine :D

Hey @persocon, glad to hear you're using the library :)
I'll get a release out this week once #11 is merged

@skozer it's amazing :D and it worked the release haha just updated on my website, it looks beautiful now 💘


BFE UI label alignment with BF vocab terms

As mentioned on a listserv post, we're requesting that the BFE UI labels be either more closely aligned with or replaced with the actual bf: vocab to promote understanding of and familiarity with the vocab.  While some of the examples below are clearly more confusing than others, when we stop to look these things up in the vocab and can’t readily find a match or the definition seems out of whack, we lose focus and momentum.
These comments are based on work with the BFE demo New Monograph forms and the comparisons are made to the list view of the vocab – I’ve gone through the Work and Instance sections of New Monograph for examples, but not the Holdings.
UI Label/bf vocab term
Variant title type/bf:titleType
Variant title data/bf:titleVariationDate
Other Authority Information/bf:referenceAuthority
Authority information/bf:hasAuthority
Creator role/bf:creator (actually, I’d prefer bf term to change here as the label is more descriptive)
Contributor role/bf:contributor (again, the label is more descriptive than the bf term)
Work content category/bf:contentCategory (I think this is the correct pairing per the BFE output, but the label for contentCategory in the vocab list view is Content type)
Local identifier/bf:local (again, the label is more descriptive than the bf term)
Part title enumeration/bf:partNumber (the vocab shows the label for this term as Part Number)
Other attribute of title/bf:titleAttribute (the vocab shows the label for this term as Other title attribute)
Edition Statement/bf:edition
Media type/bf:mediaCategory
Carrier/bf:carrierCategory (but the vocab shows the label as Carrier type)
Page nos./bf:extent
‘Has derivative’ is a UI label in the Instance form, but the definition of bf:hasDerivative is “Work has a modification for which it is the source” – so is this an Instance property?
‘Is Derivative of’ is a UI label in the Instance form but the definition of bf:derivativeOf (bf:isDerativeOf is no longer valid) is “Work is a modification of a source work”, so is this an Instance property?  Should this actually be bf:derivedFrom in the Instance form?
Author, Editor, and Publication have no corresponding vocab terms, and while we obviously understand what the expected data is about, it’s not clear up front how that data is resolving in BF, e.g., as a BF Authority for author.  Most people will not have the same depth of familiarity with the BF model that you and I have, so while it may seem patently clear to us that Author data resolves to a BF Authority, it may not be as clear to others (at least at the start).

We've done a lot of work to create RDA-based profiles, which use RDA instructions as labels. If there's some interest I'll bring back the 'Kitchen-sink' view but in the pilot we didn't find that to be very useful.


fix: correct misspelled 'surName' field

Didn't find any uses where it was bound to views.

:+1:

:-1: pending hunting down how this is generated for reals.  Guest session and session are just example feeds; in production that's a live JSON feed out of uPortal, where that spelling error might or might not be a real thing.

Coverage remained the same at 34.738% when pulling 20c1b82845d8870a3c06f8f65a43597703fd1b11 on nblair:surname into dc5af3b90dcd85961ef06d7f0ba6e13019d78771 on UW-Madison-DoIT:master.

surName isn't in the data model presented by /portal/web/session.json
{
person: {
lastName: "Blair",
userName: "npblair",
sessionKey: redacted,
serverName: redacted,
firstName: "Nicholas",
displayName: "Nicholas Blair",
version: "<IP_ADDRESS>"
}
}

It looks like I should change it to 'lastName' instead of 'surName'.

Force pushed an amended commit so that it's lastName.

:+1: for fixing typo, but I was hoping sirName was for heraldic titles or something :disappointed:

Weird build failure:
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":">=0.10.40"} (current: {"node":"0.10.36","npm":"1.4.28"})
|><EMAIL_ADDRESS>install /home/travis/build/UW-Madison-DoIT/uw-frame/node_modules/phantomjs-prebuilt
> node install.js
-JS at /usr/local/phantomjs/bin/phantomjs ...verifying
-JS detected, but wrong version 1.9.8 @ /usr/local/phantomjs/bin/phantomjs.
Downloading https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-2.1.1-linux-x86_64.tar.bz2
Saving to /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
Receiving...
-Error requesting archive.
Status: 403
Request options: {
  "uri": "https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-2.1.1-linux-x86_64.tar.bz2",
  "encoding": null,
  "followRedirect": true,
  "headers": {
    "User-Agent": "npm/1.4.28 node/v0.10.36 linux x64"
  },
  "strictSSL": true
}

Any way to tell travis to try again?

Yes, you can tell Travis to try again. Doing.

Coverage remained the same at 34.738% when pulling a902beaf5abca295944f425edd3060d57d90b91c on nblair:surname into dc5af3b90dcd85961ef06d7f0ba6e13019d78771 on UW-Madison-DoIT:master.

:+1:


remove check fixes #213

Q
A

Fixed Tickets
#213

License
MIT

A new inspection was created.

The inspection completed: No new issues


Added helpful links section to README file

Added a helpful links section to the README file.

Looks good to me as well. Thanks, @jdraiv!


Fix #152 build failure, uneeded coma

Could you fix the typo in the commit message? 😄
I guess "Fix #152 unneeded comma" should be fine.

@xalopp done

@xalopp accepted the PR, thanks for your contribution.


Check if converted file already exists

I have question about possible enhancement.
Would it be possible to check if destination file (.jpg) already exists before conversion?
For clarification, I would like to run a scheduled task on all folders and converting all .heic files that were not already converted.
Thank you

I've introduced --ignore-existing parameter. Check the README for examples


[enhancement] allow further configuration of the output columns

I use lfs to monitor the free space on my hard disks. IMHO there is information that this command shows that for most users is not necessary and only takes up space.
$ lfs
┌───┬─────┬──────────────┬────┬────┬────┬─────────┬────┬────┬────────────┐
│ id│ dev │  filesystem  │disk│type│used│  use%   │free│size│mount point │
├───┼─────┼──────────────┼────┼────┼────┼─────────┼────┼────┼────────────┤
│140│8:1  │/dev/sda1     │HDD │xfs │7.6T│42% ██▏  │ 10T│18T │/multimedia │
│145│8:17 │/dev/sdb1     │HDD │xfs │5.4T│33% █▋   │ 11T│16T │/multimedia2│
│ 62│259:2│/dev/nvme0n1p2│SSD │f2fs│384G│19% █    │1.6T│2.0T│/           │
│ 87│259:1│/dev/nvme0n1p1│SSD │vfat│59M │22% █▏   │209M│268M│/boot       │
└───┴─────┴──────────────┴────┴────┴────┴─────────┴────┴────┴────────────┘

I would like to be able to obtain something like this output:
┌──────────────┬────┬─────────┬────┬────┬────────────┐
│ filesystem   │used│  use%   │free│size│mount point │
├──────────────┼────┼─────────┼────┼────┼────────────┤
│/dev/sda1     │7.6T│42% ██▏  │ 10T│18T │/multimedia │
│/dev/sdb1     │5.4T│33% █▋   │ 11T│16T │/multimedia2│
│/dev/nvme0n1p2│384G│19% █    │1.6T│2.0T│/           │
│/dev/nvme0n1p1│59M │22% █▏   │209M│268M│/boot       │
└──────────────┴────┴─────────┴────┴────┴────────────┘

Including being able to change the order of the columns.

I can do that. This would probably be with a verbose launch argument like --columns fs,used,use-percent,free,size,mount-point but I imagine all people interested would only do that with an alias

what about adding --compact to accomplish this? It should only print the bare minimum to list drives and volumes as used in the example by @simonbcn

@daniejstriata Problem is there can be very different opinions about what's the useful compact set. I might allow a few standard sets. Right now I'm thinking about using the syntax I defined for rhit fields selection, allowing an explicit set, or additions or removals to a standard one: https://dystroy.org/rhit/usage-fields/

@Canop That sounds good.

And I'll have to build a documentation site because the README will start to be too hard to read. Suggestions for what to include on the site, or other needed parameters are welcome (chat is good for that).

@simonbcn @daniejstriata I've started a GH discussion on this topic: https://github.com/Canop/lfs/discussions/29

Done in lfs 2. See doc: https://dystroy.org/lfs/table/

Thank you very much, I just tried it and the only thing is that the filesystem is not aligned to the left:
$ lfs
┌──────────────┬────┬────┬────┬─────────┬────┬────┬────────────┐
│  filesystem  │disk│type│used│  use%   │free│size│mount point │
├──────────────┼────┼────┼────┼─────────┼────┼────┼────────────┤
│  /dev/sda1   │HDD │xfs │6.8T│38% █▉   │ 11T│ 18T│/multimedia │
│  /dev/sdb1   │HDD │xfs │9.0T│56% ██▊  │7.0T│ 16T│/multimedia2│
│/dev/nvme0n1p2│SSD │f2fs│364G│18% ▉    │1.6T│2.0T│/           │
│/dev/nvme0n1p1│SSD │vfat│ 89M│33% █▋   │180M│268M│/boot       │
└──────────────┴────┴────┴────┴─────────┴────┴────┴────────────┘

Damn... Didn't notice this...
I'll release a new version ^^

Done. version 2.0.1.


Live app is not working

SyntaxError: Unexpected token < in JSON at position 0

Hi, do you have any more details? Seems to be working for me: https://www.graphqlhub.com/playground?query=%23 Welcome to GraphQLHub! Type your GraphQL query here%2C or
%23 explore the "Docs" to the right

{
  hn2 {
    nodeFromHnId(id%3A"clayallsopp"%2C isUserId%3Atrue) {
      id
      ... on HackerNewsV2User {
        submitted(first%3A 5) {
          pageInfo {
            hasNextPage
            endCursor
          }
          edges {
            cursor
            node {
              id
              ... on HackerNewsV2Story {
								score
                url
              }
              ... on HackerNewsV2Comment {
                text
              }
            }
          }
        }
      }
    }
  }
}

It seems to be a graphiql error.
Try press "prettify query" and then run your query.

Hm, still working - can you paste the link to the query that's failing for you?

I just try your query but showing me this

@clayallsopp

I also try "prettify query" but still the same problem. @nodkz

@ratulcse27 can you erase the "null" in the Query Variables section and try again?

I tried it but still the same problem @clayallsopp


app.py: indexing pngs when nlp selected

Describe your problem
With cookiecutter options:

task_type: nlp
index_type: files

It creates app.py with line 26 being
f.index_files('data/**/*.png', batch_size=64, read_mode='rb', size=num_docs)

Since we're dealing with NLP, should the extension be changed to txt or csv?
Why do you think it's happening?
Misconfigured variable in cookiecutter?
Environment
Downloaded latest cookiecutter-jina

@yuanbit I just tested again today and this bug still exists. Could you look into it pls?

@yuanbit I just tested again today and this bug still exists. Could you look into it pls?

In app.py:
    with f:
        f.index_files('data/**/*.png', batch_size=8, read_mode='rb', size=num_docs)

In app.py:
    with f:
        f.index_files('data/**/*.png', batch_size=8, read_mode='rb', size=num_docs)

@alexcg1 I think this is happening because for nlp you are only supposed to select strings and the extension doesn't matter because f.index_lines(filepath=data_path, batch_size=16, read_mode='r', size=num_docs) in line 32 only needs the file path. I think the only requirements to use cookiecutter for an nlp task is that each document in the data needs to be separated by lines.

@alexcg1 I think this is happening because for nlp you are only supposed to select strings and the extension doesn't matter because f.index_lines(filepath=data_path, batch_size=16, read_mode='r', size=num_docs) in line 32 only needs the file path. I think the only requirements to use cookiecutter for an nlp task is that each document in the data needs to be separated by lines.


On front-end currency symbol display only for Indian Rupee and USD. If code is selected other than these two in currency then code displays before price.

Framework Version: 0.1.3

Framework Version: 0.1.4
Not Fixed

This was deliberately left as we don't have currency symbols to apply for the other currencies.
Yet a fix will be provided for it shortly.

you have saved wrong currency code


Restore Missing Yeoman Generator Jest Test

Jira
http://vjira2:8080/browse/BDS-1966?filter=-1
Summary
Restores our missing component-generator.js file accidentally removed recently
How to test
Confirm tests pass / run as expected

@sghoweri I compared this to the version that is in @adamszalapski's PR #1647 and found one discrepancy. It is adding the -- to this line:
    shell.exec('yarn run cc -- -N Test -D "Test Description" -T');

I'm guessing this is intentional? Or else, it was added later and should be there?
Otherwise, looks good to me.

Right now in yarn we don't need to add -- to pass parameters to next command.


HBASE-26383 HBCK incorrectly reports inconsistencies for recently split regions following a master failover

A regression was introduced by HBASE-25847 which changed regionInfo#isParentSplit to regionState#isSplit. The region state after restart is CLOSED instead of SPLIT. We need to check both regionState and regionInfo for split status.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 11s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
5m 21s
master passed

+1 :green_heart:
compile
1m 21s
master passed

+1 :green_heart:
shadedjars
9m  4s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m  3s
the patch passed

+1 :green_heart:
compile
1m 20s
the patch passed

+1 :green_heart:
javac
1m 20s
the patch passed

+1 :green_heart:
shadedjars
9m  2s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 42s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
207m  2s
hbase-server in the patch passed.

242m 54s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3775/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3775

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b8bebe173496 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 9e73ea878d

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3775/1/testReport/

Max. process+thread count
3451 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3775/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

Sorry I missed your comment @saintstack .

Was wondering why the change over in HBASE-25847 in the first place @apurtell (If you remember...).

I do not remember. Given the related changes, without that additional change the new log lines were contrary to expectation. It looked like a bug, per my comments on the issue.

@saintstack I am going to release a 2.4.8 with this merged PR included. If you'd like some additional work done here or a revert of the original change rather than this addition, just say.

Thanks for the PR @apurtell . I think this change will do away with the confusing split parent reporting as inconsistent (after a Master restart). That'll help. Can work on the bigger issue of new Master not faithfully reproducing old Master's in-memory state in another PR/JIRA. Thanks (I kicked Benoit and Boris for comment...)


Fix minor filter menu bugs

Fixes minor bugs that occurred when user filtered products - like non-removable filters or one that caused fast-checked checkboxes to not switching their state excluding last one.

Codecov Report

Merging #1279 into update-demo will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           update-demo    #1279   +/-   ##
============================================
  Coverage        69.65%   69.65%
============================================
  Files              117      117
  Lines             6094     6094
  Branches           776      776
============================================
  Hits              4245     4245
- Misses            1689     1690    +1
+ Partials           160      159    -1

Impacted Files
Coverage Δ

saleor/graphql/api.py
81.92% <0%> (ø)
: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 0188a5a...f961522. Read the comment docs.


Fix/376 blog posts should not appear in activity feeds

based on https://github.com/near/neardevhub-widgets/pull/369
fixes #376

Preview


Conditional groupings unsound - parens mismatch

Resulting in error: Extra closing ')' at the end of expression.

Here's the culprit:
https://github.com/firebase/protobuf-rules-gen/blob/master/firebase_rules_generator/generator.cc#L287


Enhance/group feature

Description
Design a way to improve the group Task submission.
Use case: When submitting the group task, only one person needs to submit, however after the submission other students can still overwrite this with the incorrect file.
We need to write up a design document that outlines how we can mitigate this either by selecting in the task which students can submit, or adding a password that the unit chair allocates to certain students. Or possibly some other idea !
Documentation

This has prettier errors.


Clicking "Change board" causes a download to happen

Repro:

pair a device via webusb (e.g. meowbit)
click "change hardware" and select meowbit
this causes a download to automatically happen and it shouldn't.

Seems to be fixed, choose hardware doesn't cause automatic download


Add a network card to a VM and connect it to a network

knife vsphere vm network add VMNAME NETWORKNAME

Hound sure is fussy about blank spaces. I think it took longer to make hound happy than to actually write the code...

How are you supposed to add the documentation (author etc) to the top of the file without this error:
Missing frozen string literal comment.

We already have knife vsphere network set to change the VLAN associated with a particular NIC. What would you think about renaming this one to be knife vsphere network add rather than using the word nic, just for consistency?
Also, please add a section to the README for this, thanks.

Thanks mate! Just getting up here, will be looking at it within the next few hours.

Thanks for sticking with it. This works awesome and will make a lot of people happy. I'll merge this and cut a release after checking out your other PR.

No problem, its been a fun few days learning ruby, I hope to contribute more in the future...


Daily Email Notifications for Favorites

WHAT DOES THIS PR DO?

Daily Email Notifications for Favorites

WHAT ISSUES ARE RELATED TO THIS PR?

Jira cards

GitHub issues

Closes #

HOW DO I TEST OUT THIS PR?
WHICH ENDPOINTS SHOULD BE READY FOR TESTING?:
IS THERE ANY JENKINS CONSOLE LINK FOR CODE COVERAGE AND BUILD INFO?
ARE THERE ANY RELATED PRs?

Hi @BenjaminSsempala ,thanks for this. Do you mind sharing more details about the problem this PR is solving. Why are we creating daily email notifications?

@Baalmart This is inline with the OKRs for Mobile, The 1st Key result, Under the corresponding activities
https://docs.google.com/document/d/1xL13ibn4KegFCcjv0Ghvi4gV8rfLL467r6p-cJ3uX8E/edit#heading=h.qb3f0zpuw0a9

Hi @BenjaminSsempala ,thanks for this. Do you mind sharing more details about the problem this PR is solving. Why are we creating daily email notifications?

@Baalmart This is inline with the OKRs for Mobile, The 1st Key result, Under the corresponding activities https://docs.google.com/document/d/1xL13ibn4KegFCcjv0Ghvi4gV8rfLL467r6p-cJ3uX8E/edit#heading=h.qb3f0zpuw0a9
Although I've been corrected that the frequency is weekly, not daily

thanks for the clarifications @BenjaminSsempala


etcdserver: keep a min number of entries in memory

Do not aggressively compact the raft log entries. After a snapshot,
etcd server can compact the raft log upto snapshot index. etcd server
compacts to an index smaller index to keep some entries in memory.
The leader can still read out the in memory entries to send to a slightly
slow follower. If all the entries are compacted, the leader will send the
whole snapshot or read entries from disk if possible.

@xiang90 I did a little testing here and it seems we only compact the raft log once based on the log messages. I started a 3 node cluster with the snapshot-count=100
22:30:34 etcd3 | 2015/02/28 22:30:34 raft: 924e2e83e93f2560 received msgApp rejection(lastindex: 4) from a8266ecf031671f3 for index 7
22:30:34 etcd3 | 2015/02/28 22:30:34 raft: 924e2e83e93f2560 decreased progress of a8266ecf031671f3 to [next = 5, match = 4, wait = 0]
22:30:34 etcd3 | 2015/02/28 22:30:34 raft: 924e2e83e93f2560 received msgApp rejection(lastindex: 4) from 6e3bd23ae5f1eae0 for index 7
22:30:34 etcd3 | 2015/02/28 22:30:34 raft: 924e2e83e93f2560 decreased progress of 6e3bd23ae5f1eae0 to [next = 5, match = 4, wait = 0]
22:30:34 etcd3 | 2015/02/28 22:30:34 etcdserver: published {Name:infra3 ClientURLs:[http://localhost:4003]} to cluster e9c7614f68f35fb2
22:30:34 etcd2 | 2015/02/28 22:30:34 etcdserver: published {Name:infra2 ClientURLs:[http://localhost:4002]} to cluster e9c7614f68f35fb2
22:30:34 etcd1 | 2015/02/28 22:30:34 etcdserver: published {Name:infra1 ClientURLs:[http://localhost:4001]} to cluster e9c7614f68f35fb2
22:30:46 etcd3 | 2015/02/28 22:30:46 etcdserver: start to snapshot (applied: 101, lastsnap: 0)
22:30:46 etcd3 | 2015/02/28 22:30:46 etcdserver: saved snapshot at index 101
22:30:46 etcd3 | 2015/02/28 22:30:46 etcdserver: compacted raft log at 1
22:30:46 etcd1 | 2015/02/28 22:30:46 etcdserver: start to snapshot (applied: 101, lastsnap: 0)
22:30:46 etcd2 | 2015/02/28 22:30:46 etcdserver: start to snapshot (applied: 101, lastsnap: 0)
22:30:46 etcd1 | 2015/02/28 22:30:46 etcdserver: saved snapshot at index 101
22:30:46 etcd1 | 2015/02/28 22:30:46 etcdserver: compacted raft log at 1
22:30:46 etcd2 | 2015/02/28 22:30:46 etcdserver: saved snapshot at index 101
22:30:46 etcd2 | 2015/02/28 22:30:46 etcdserver: compacted raft log at 1
22:30:54 etcd3 | 2015/02/28 22:30:54 etcdserver: start to snapshot (applied: 202, lastsnap: 101)
22:30:54 etcd3 | 2015/02/28 22:30:54 etcdserver: saved snapshot at index 202
22:30:54 etcd2 | 2015/02/28 22:30:54 etcdserver: start to snapshot (applied: 203, lastsnap: 101)
22:30:54 etcd1 | 2015/02/28 22:30:54 etcdserver: start to snapshot (applied: 203, lastsnap: 101)
22:30:54 etcd2 | 2015/02/28 22:30:54 etcdserver: saved snapshot at index 203
22:30:54 etcd1 | 2015/02/28 22:30:54 etcdserver: saved snapshot at index 203
22:31:03 etcd3 | 2015/02/28 22:31:03 etcdserver: start to snapshot (applied: 303, lastsnap: 202)
22:31:03 etcd3 | 2015/02/28 22:31:03 etcdserver: saved snapshot at index 303
22:31:03 etcd2 | 2015/02/28 22:31:03 etcdserver: start to snapshot (applied: 305, lastsnap: 203)
22:31:03 etcd1 | 2015/02/28 22:31:03 etcdserver: start to snapshot (applied: 305, lastsnap: 203)
22:31:03 etcd2 | 2015/02/28 22:31:03 etcdserver: saved snapshot at index 305
22:31:03 etcd1 | 2015/02/28 22:31:03 etcdserver: saved snapshot at index 305
22:31:11 etcd3 | 2015/02/28 22:31:11 etcdserver: start to snapshot (applied: 404, lastsnap: 303)
22:31:11 etcd3 | 2015/02/28 22:31:11 etcdserver: saved snapshot at index 404
22:31:11 etcd1 | 2015/02/28 22:31:11 etcdserver: start to snapshot (applied: 407, lastsnap: 305)
22:31:11 etcd2 | 2015/02/28 22:31:11 etcdserver: start to snapshot (applied: 407, lastsnap: 305)
22:31:11 etcd1 | 2015/02/28 22:31:11 etcdserver: saved snapshot at index 407
22:31:11 etcd2 | 2015/02/28 22:31:11 etcdserver: saved snapshot at index 407
22:31:20 etcd3 | 2015/02/28 22:31:20 etcdserver: start to snapshot (applied: 505, lastsnap: 404)
22:31:20 etcd3 | 2015/02/28 22:31:20 etcdserver: saved snapshot at index 505
22:31:20 etcd2 | 2015/02/28 22:31:20 etcdserver: start to snapshot (applied: 509, lastsnap: 407)
22:31:20 etcd1 | 2015/02/28 22:31:20 etcdserver: start to snapshot (applied: 509, lastsnap: 407)
22:31:20 etcd2 | 2015/02/28 22:31:20 etcdserver: saved snapshot at index 509
22:31:20 etcd1 | 2015/02/28 22:31:20 etcdserver: saved snapshot at index 509
22:31:28 etcd3 | 2015/02/28 22:31:28 etcdserver: start to snapshot (applied: 606, lastsnap: 505)
22:31:28 etcd3 | 2015/02/28 22:31:28 etcdserver: saved snapshot at index 606
22:31:28 etcd2 | 2015/02/28 22:31:28 etcdserver: start to snapshot (applied: 611, lastsnap: 509)
22:31:28 etcd1 | 2015/02/28 22:31:28 etcdserver: start to snapshot (applied: 611, lastsnap: 509)
22:31:28 etcd1 | 2015/02/28 22:31:28 etcdserver: saved snapshot at index 611
22:31:28 etcd2 | 2015/02/28 22:31:28 etcdserver: saved snapshot at index 611
22:31:32 etcd2 | 2015/02/28 22:31:32 filePurge: successfully removed file infra2.etcd/member/snap/0000000000000002-0000000000000065.snap
22:31:32 etcd3 | 2015/02/28 22:31:32 filePurge: successfully removed file infra3.etcd/member/snap/0000000000000002-0000000000000065.snap
22:31:32 etcd1 | 2015/02/28 22:31:32 filePurge: successfully removed file infra1.etcd/member/snap/0000000000000002-0000000000000065.snap
22:31:36 etcd3 | 2015/02/28 22:31:36 etcdserver: start to snapshot (applied: 707, lastsnap: 606)
22:31:36 etcd3 | 2015/02/28 22:31:36 etcdserver: saved snapshot at index 707
22:31:37 etcd2 | 2015/02/28 22:31:37 etcdserver: start to snapshot (applied: 713, lastsnap: 611)
22:31:37 etcd1 | 2015/02/28 22:31:37 etcdserver: start to snapshot (applied: 713, lastsnap: 611)
22:31:37 etcd1 | 2015/02/28 22:31:37 etcdserver: saved snapshot at index 713
22:31:37 etcd2 | 2015/02/28 22:31:37 etcdserver: saved snapshot at index 713
22:31:45 etcd3 | 2015/02/28 22:31:45 etcdserver: start to snapshot (applied: 808, lastsnap: 707)
22:31:45 etcd3 | 2015/02/28 22:31:45 etcdserver: saved snapshot at index 808
22:31:45 etcd1 | 2015/02/28 22:31:45 etcdserver: start to snapshot (applied: 815, lastsnap: 713)
22:31:45 etcd2 | 2015/02/28 22:31:45 etcdserver: start to snapshot (applied: 815, lastsnap: 713)
22:31:45 etcd2 | 2015/02/28 22:31:45 etcdserver: saved snapshot at index 815
22:31:45 etcd1 | 2015/02/28 22:31:45 etcdserver: saved snapshot at index 815
22:31:53 etcd3 | 2015/02/28 22:31:53 etcdserver: start to snapshot (applied: 909, lastsnap: 808)
22:31:53 etcd3 | 2015/02/28 22:31:53 etcdserver: saved snapshot at index 909
22:31:54 etcd1 | 2015/02/28 22:31:54 etcdserver: start to snapshot (applied: 917, lastsnap: 815)
22:31:54 etcd2 | 2015/02/28 22:31:54 etcdserver: start to snapshot (applied: 917, lastsnap: 815)
22:31:54 etcd2 | 2015/02/28 22:31:54 etcdserver: saved snapshot at index 917
22:31:54 etcd1 | 2015/02/28 22:31:54 etcdserver: saved snapshot at index 917
22:32:02 etcd3 | 2015/02/28 22:32:02 etcdserver: start to snapshot (applied: 1010, lastsnap: 909)
22:32:02 etcd3 | 2015/02/28 22:32:02 etcdserver: saved snapshot at index 1010
22:32:02 etcd2 | 2015/02/28 22:32:02 filePurge: successfully removed file infra2.etcd/member/snap/0000000000000002-00000000000000cb.snap
22:32:02 etcd2 | 2015/02/28 22:32:02 filePurge: successfully removed file infra2.etcd/member/snap/0000000000000002-0000000000000131.snap
22:32:02 etcd2 | 2015/02/28 22:32:02 filePurge: successfully removed file infra2.etcd/member/snap/0000000000000002-0000000000000197.snap
22:32:02 etcd3 | 2015/02/28 22:32:02 filePurge: successfully removed file infra3.etcd/member/snap/0000000000000002-00000000000000ca.snap
22:32:02 etcd3 | 2015/02/28 22:32:02 filePurge: successfully removed file infra3.etcd/member/snap/0000000000000002-000000000000012f.snap
22:32:02 etcd3 | 2015/02/28 22:32:02 filePurge: successfully removed file infra3.etcd/member/snap/0000000000000002-0000000000000194.snap
22:32:02 etcd3 | 2015/02/28 22:32:02 filePurge: successfully removed file infra3.etcd/member/snap/0000000000000002-00000000000001f9.snap
22:32:02 etcd1 | 2015/02/28 22:32:02 filePurge: successfully removed file infra1.etcd/member/snap/0000000000000002-00000000000000cb.snap
22:32:02 etcd1 | 2015/02/28 22:32:02 filePurge: successfully removed file infra1.etcd/member/snap/0000000000000002-0000000000000131.snap
22:32:02 etcd1 | 2015/02/28 22:32:02 filePurge: successfully removed file infra1.etcd/member/snap/0000000000000002-0000000000000197.snap
22:32:02 etcd2 | 2015/02/28 22:32:02 etcdserver: start to snapshot (applied: 1019, lastsnap: 917)
22:32:02 etcd1 | 2015/02/28 22:32:02 etcdserver: start to snapshot (applied: 1019, lastsnap: 917)
22:32:02 etcd2 | 2015/02/28 22:32:02 etcdserver: saved snapshot at index 1019
22:32:02 etcd1 | 2015/02/28 22:32:02 etcdserver: saved snapshot at index 1019
22:32:10 etcd3 | 2015/02/28 22:32:10 etcdserver: start to snapshot (applied: 1111, lastsnap: 1010)
22:32:10 etcd3 | 2015/02/28 22:32:10 etcdserver: saved snapshot at index 1111
22:32:11 etcd2 | 2015/02/28 22:32:11 etcdserver: start to snapshot (applied: 1121, lastsnap: 1019)
22:32:11 etcd1 | 2015/02/28 22:32:11 etcdserver: start to snapshot (applied: 1121, lastsnap: 1019)
22:32:11 etcd1 | 2015/02/28 22:32:11 etcdserver: saved snapshot at index 1121
22:32:11 etcd2 | 2015/02/28 22:32:11 etcdserver: saved snapshot at index 1121
22:32:18 etcd3 | 2015/02/28 22:32:18 etcdserver: start to snapshot (applied: 1212, lastsnap: 1111)
22:32:18 etcd3 | 2015/02/28 22:32:18 etcdserver: saved snapshot at index 1212
22:32:19 etcd1 | 2015/02/28 22:32:19 etcdserver: start to snapshot (applied: 1223, lastsnap: 1121)
22:32:19 etcd2 | 2015/02/28 22:32:19 etcdserver: start to snapshot (applied: 1223, lastsnap: 1121)
22:32:19 etcd1 | 2015/02/28 22:32:19 etcdserver: saved snapshot at index 1223
22:32:19 etcd2 | 2015/02/28 22:32:19 etcdserver: saved snapshot at index 1223
22:32:27 etcd3 | 2015/02/28 22:32:27 etcdserver: start to snapshot (applied: 1313, lastsnap: 1212)
22:32:27 etcd3 | 2015/02/28 22:32:27 etcdserver: saved snapshot at index 1313
22:32:28 etcd1 | 2015/02/28 22:32:28 etcdserver: start to snapshot (applied: 1325, lastsnap: 1223)
22:32:28 etcd2 | 2015/02/28 22:32:28 etcdserver: start to snapshot (applied: 1325, lastsnap: 1223)
22:32:28 etcd2 | 2015/02/28 22:32:28 etcdserver: saved snapshot at index 1325
22:32:28 etcd1 | 2015/02/28 22:32:28 etcdserver: saved snapshot at index 1325
22:32:32 etcd2 | 2015/02/28 22:32:32 filePurge: successfully removed file infra2.etcd/member/snap/0000000000000002-00000000000001fd.snap
22:32:32 etcd2 | 2015/02/28 22:32:32 filePurge: successfully removed file infra2.etcd/member/snap/0000000000000002-0000000000000263.snap
22:32:32 etcd2 | 2015/02/28 22:32:32 filePurge: successfully removed file infra2.etcd/member/snap/0000000000000002-00000000000002c9.snap
22:32:32 etcd2 | 2015/02/28 22:32:32 filePurge: successfully removed file infra2.etcd/member/snap/0000000000000002-000000000000032f.snap
22:32:32 etcd3 | 2015/02/28 22:32:32 filePurge: successfully removed file infra3.etcd/member/snap/0000000000000002-000000000000025e.snap
22:32:32 etcd3 | 2015/02/28 22:32:32 filePurge: successfully removed file infra3.etcd/member/snap/0000000000000002-00000000000002c3.snap
22:32:32 etcd3 | 2015/02/28 22:32:32 filePurge: successfully removed file infra3.etcd/member/snap/0000000000000002-0000000000000328.snap
22:32:32 etcd1 | 2015/02/28 22:32:32 filePurge: successfully removed file infra1.etcd/member/snap/0000000000000002-00000000000001fd.snap
22:32:32 etcd1 | 2015/02/28 22:32:32 filePurge: successfully removed file infra1.etcd/member/snap/0000000000000002-0000000000000263.snap
22:32:32 etcd1 | 2015/02/28 22:32:32 filePurge: successfully removed file infra1.etcd/member/snap/0000000000000002-00000000000002c9.snap
22:32:32 etcd1 | 2015/02/28 22:32:32 filePurge: successfully removed file infra1.etcd/member/snap/0000000000000002-000000000000032f.snap
22:32:35 etcd3 | 2015/02/28 22:32:35 etcdserver: start to snapshot (applied: 1414, lastsnap: 1313)
22:32:35 etcd3 | 2015/02/28 22:32:35 etcdserver: saved snapshot at index 1414
22:32:36 etcd1 | 2015/02/28 22:32:36 etcdserver: start to snapshot (applied: 1427, lastsnap: 1325)
22:32:36 etcd2 | 2015/02/28 22:32:36 etcdserver: start to snapshot (applied: 1427, lastsnap: 1325)
22:32:36 etcd2 | 2015/02/28 22:32:36 etcdserver: saved snapshot at index 1427
22:32:36 etcd1 | 2015/02/28 22:32:36 etcdserver: saved snapshot at index 1427

@kelseyhightower That is expected. We keep at least 5000 in memory entries.

After testing this with a single node and 3 node cluster everything seems to be working as we expect.
LGTM.

lgtm

Since we plan to keep 5000 log entries around we need to document this fact, and ideally make this setting tunable.

@kelseyhightower This is an implementation details for now. We need to understand the exact impact of this before making it tunable.

@kelseyhightower I am going to merge this as it is. I will follow up with a memory usage summary of etcd section in tune.md.


Add tests

Tests should be added to the project to ensure each PR does not introduce breaking changes.
I am currently working on this in the add-tests branch and will open a PR when they are ready.

This is proving harder than expected, as the synchronous methods don't implement web sessions.
Is it worth maintaining these synchronous methods? I believe it's easy enough to run it asynchronously when implementing this module, but I'd like to get some input. If we remove the synchronous methods, we'd also be able to remove the requests module dependency as well.
I do not believe Home Assistant utilizes the synchronous methods at all, so nothing would break in terms of that.
@funkybunch @AritroSaha10 Thoughts?

I agree that the synchronous functions aren't completely useful considering the simplicity of the async methods. In addition, I doubt that they are used much, if it all, since most repos that are reported to use the library are just forks of HA core. Maybe we can keep a legacy fork in case if anyone is interested in using them?

I agree that the synchronous functions aren't completely useful considering the simplicity of the async methods. In addition, I doubt that they are used much, if it all, since most repos that are reported to use the library are just forks of HA core. Maybe we can keep a legacy fork in case if anyone is interested in using them?

There's also quite a few ways to call synchronous functions from asynchronous functions, but in my small amount of testing, I wasn't able to get it working. This would streamline things having the synchronous and asynchronous functions call essentially the exact same code.

I've begun work on this issue in #9. So far I've set up a number of basic unit tests with a typical pytest structure, which could be a good starting point for further tests to be added down the road.


feat: Add M3 TopTabBar style

PR Type
What kind of change does this PR introduce?

Feature

Our current Material TopTabBar was not following the Material guidelines very well. There should be several styles for Tabs, as you see here (https://material.io/components/tabs/android#theming-tabs):

(There's a third style mentioned on that page but we will ignore it for now.)
There is the notion of a default TabBar in Material (see: https://material.io/components/tabs#interactive-demo) with a transparent background and Primary color highlighting:

There are also "colored" Material Tabs (see: https://material.io/components/tabs#states) with a background of Primary color and OnPrimaryColor highlighting:

This PR introduces both those styles for both Material Design 2 and 3:
Uno Material Colored TopTabBar:

Uno Material TopTabBar:

@kazo0 with the latest web static app version, is this normal that M2 is displaying M3 styles ?

Also, notice the check icon border (not sure if it's a wasm issue)

In a way, this is a breaking change no ? as MateriaTopTabBarStyle was replaced by MaterialColoredTopTabBarStyle in terms of styling visually. Should the commit reflect the info?

 Also, notice the check icon border (not sure if it's a wasm issue)

Happening also for the colored top tab bar

"Show top tab bar sample" buttons seems cut for M3 for WASM

Also noticed the button is on top of the MaterialTopTabBarStyle but the nested sample show the MaterialColoredTopTabBarStyle (maybe confusing ?)

Hmm maybe there is some sort of antialiasing issue for the border renderer like there was for Android: https://github.com/unoplatform/uno/pull/8357. I don't think this would be fixable within Themes.
Yeah I'll try and better organize this page with the nested samples, maybe a nested sample for each style? One for the default and one for Colored.

"Show top tab bar sample" buttons seems cut for M3 for WASM

Also noticed the button is on top of the MaterialTopTabBarStyle but the nested sample show the MaterialColoredTopTabBarStyle (maybe confusing ?)

Hmm maybe there is some sort of antialiasing issue for the border renderer like there was for Android: unoplatform/uno#8357. I don't think this would be fixable within Themes.
Yeah I'll try and better organize this page with the nested samples, maybe a nested sample for each style? One for the default and one for Colored.

I understand and yes maybe a nested sample for each style could do it I think.


removed inline function

if one includes the header and does not link with coding.cc gets unresolved error. not the case when you just include extern functions and do not use them, more over this function does not seem to save so much being inlined.

Nagging Reviewer @andrehentz: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 17 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @andrehentz: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 48 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @andrehentz: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 63 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @andrehentz: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 78 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @andrehentz: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 93 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @andrehentz: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 123 days with no activity and the awaiting review label has been applied.

Sorry I completely missed this one. Are you still interested in proceeding?

Thanks for you contribution and your understanding!

Changes are already in the master branch , closing this


TFRS - 2023 Exclusion report bug in prod

Describe the Bug
In TFRS prod, exclusion report #2719 was submitted by a BCeID user. On the IDIR side, the exclusion agreement shows that nothing has been input in to any cells and that the drop-down options and free text cells are available to the IDIR user to select.
Expected Behaviour
The expected behaviour for an exclusion report is that the rows in the 'Exclusion agreements' tab of the report show entries made by the BCeID user as viewable only. There should be no option for the IDIR user to change the data in the report.
Actual Behaviour
Exclusion report #2719 is a 2023 that is showing no data in any of the rows, and is allowing for an IDIR user to input data.

Implications
The implications are: 1) An IDIR user with the analyst role can not see any data that was input to the row(s) of the report.
2) An IDIR user with the analyst role can choose input's for this organizations report (although it has not been tested if they save as this is in production).
Steps To Reproduce
Steps to reproduce the behaviour:
User/Role: IDIR

Go to Exclusion Report #2719
Click on 'Exclusion agreements' tab
See error

Notes

BCeID user said that the report had been sitting in a draft state for awhile.
As an IDIR user, once you attempt to put any data in the report, if you navigate away from the page and then back, the option to input anything is removed and the view only table is displayed (with no information still).
This is the first exclusion report the supplier has submitted for 2023.

I have completed the investigation into the database for this exclusion report. The initial draft record was never saved with any attached exclusion agreement rows so it seems that the user had an issue when saving their data. I tried creating a supplemental version of the existing report and was able to input and save new rows. I would recommend this to the client to try, and then see if they have any followup issues.

Thank you, @AlexZorkin. I will advise the policy analyst to contact this supplier and make that suggestion. Appreciate the quick turn around.


Cannot persist number to string dicts in windows, can persist string to numbers dict just fine

Hi,
I am a noob in Julia, so I might be making some big wrong assumption or error.
The corresponding code for Dict{Int64,String} works just fine. (Julia 0.4 on Windows 8)
julia> x = {1=>"alp",2=>"blp"}
WARNING: deprecated syntax "{a=>b, ...}".
Use "Dict{Any,Any}(a=>b, ...)" instead.
Dict{Any,Any} with 2 entries:
2 => "blp"
1 => "alp"
julia> using HDF5,JLD
julia> save("maxmax",x)
ERROR: MethodError: bytestring has no method matching bytestring(::Int64)
in anonymous at C:\Users\sony.julia\v0.4\HDF5\src\JLD.jl:1036
in jldopen at C:\Users\sony.julia\v0.4\HDF5\src\JLD.jl:233
in save at C:\Users\sony.julia\v0.4\HDF5\src\JLD.jl:1033

You want to use save("maxmax", "x", x). When you pass only a dict, the keys of the dict are taken as the names of the variables. That's not your intention here, so you need to give a name for the variable in the HDF5 file.

Thanks a tonne. This works :) .

Actually, if you think it's under-documented, please edit the docs to make them better! (You can do that straight from your web browser, see https://github.com/JuliaLang/julia/blob/master/CONTRIBUTING.md#improving-documentation

Sure, will do. Thanks again.

I think I was too hasty to close this; at a minimum we could improve the error message.


Error when compiled with pyinstaller

I'm getting this error when trying to use your package after being compiled into an exe by pyinstaller.
Here is my code
rpc = DiscordRPC.RPC.Set_ID('Example')
button = DiscordRPC.button(button_one_label='Server Invite', button_one_url="https://discord.gg/batch", button_two_label='Website', button_two_url='https://sped.lol')
rpc.set_activity(state='test', details='test', large_image='WORKING_LARGE_IMAGE_KEY', large_text='test', buttons=button, timestamp=rpc.timestamp())
rpc.run()

It works perfectly fine as just a py file but when compiled it breaks

Why are you using PyInstaller? I've never tried to compile it, so I don't recommend compiling it.

Why are you using PyInstaller? I've never tried to compile it, so I don't recommend compiling it.

I already fixed this was awhile ago

Why are you using PyInstaller? I've never tried to compile it, so I don't recommend compiling it.

I already fixed this was awhile ago

Good. That's why I closed this, inactive.


How is workload_sqls obtained in main.py

Hello,
I am trying to understand about the workload_sqls that is being fed into main.py. Could you explain to me how these SQLs are being derived?
Is the information being extracted from the pg_stat_statements view?

Yes, you can obtain workload_sqls from pg_stat_statements by removing queries over the 'postgres' database (https://github.com/TsinghuaDatabaseGroup/DB-GPT/blob/main/utils/database.py#L330).
However, as mentioned in README, pg_stat_statements does not support time-period-based filtering and the obtained queries may not be within the anomaly period. A better choice is to (1) directly extract queries from the anomaly trigging scripts (for test only) or (2) utilize advanced tools in commercial databases (e.g., AWR report in Oracle).
Queries can be most critical for finding useful root causes. Thus, if you have any better strategies to extract representative historical queries during a time period (as we know, logging all the queries can be unaffordable). Please let us know -:)

Thank you for your detailed response, it was very informative.
Firstly, I appreciate your clear explanation on how to obtain workload_sqls from pg_stat_statements. Your advice on filtering queries on the 'postgres' database was particularly useful.
I also noted your suggestion regarding the issue with time-based filtering. I do not fully understand yet the strategy for extracting representative historical queries over a specific period.
Therefore, I would like to further explore this matter.
Thank you very much.


F#-style type providers

Problem

When querying a database from Ruby, I would like to write SQL or GraphQL directly in my code (rather than use an ORM, for example). While this is great because it lets me use the full power of the database, it can result in runtime errors due to misformatted queries, missing references, etc.
Further, the result of a successful query is typically T.untyped, and requires runtime deserialization and checks to go from the raw response to typed data structures.
Proposed solution

It would be great if Sorbet could provide static typechecking when writing the query as well as types for the result of the query. Assuming we have access to a static database schema when writing the code and running it, we could automatically check query strings and show errors when the query does not typecheck (for example, the table name is misspelled, or a join operation is being performed on incompatible columns). We could also infer the types of the result, since we know the exact fields or aggregations being returned.
This has been implemented in F# via type providers.
A good example is the SQL provider here: https://github.com/rspeele/Rezoom.SQL. The README includes a GIF of the desired behavior.
More examples are listed here: https://docs.microsoft.com/en-us/dotnet/fsharp/tutorials/type-providers/#commonly-used-type-providers.
A similar request was raised for TypeScript: https://github.com/microsoft/TypeScript/issues/3136.
I know very little about type systems, so can't comment on whether this is the right approach or not. However, the desired behavior would definitely improve my productivity quite a bit!

Thanks for the idea. F#'s type providers are pretty cool.
The way we suggest implementing something similar is using code generation to create RBI files with more specific types.


claude2 500错误

访问时候得到如下错误：

测试的py脚本如下
#!/usr/bin/env python3
# -*- encoding: utf-8 -*-
#@time : 2023/08/19 13:23:48

import openai

openai.api_key = ""
openai.api_base = "http://<IP_ADDRESS>:8787/v1"

while True:
    text = input("请输入问题：")
    response = openai.ChatCompletion.create(
        model='gpt-4',
        messages=[
            {'role': 'user', 'content': text},
        ],
        stream=True,
        allow_fallback=True
    )

    for chunk in response:
        print(chunk.choices[0].delta.get("content", ""), end="", flush=True)
    print("\n")

提示的错误信息如下：
Unknown error {"error":{"code":"500","details":"Get \"https://claude.ai/api/organizations\": read tcp <IP_ADDRESS>:64215-\u003e<IP_ADDRESS>:7890: wsarecv: An existing connection was forcibly closed by the remote host.","message":"Unknown error","param":null,"type":"internal_server_error"}} 500 {'error': {'code': '500', 'details': 'Get "https://claude.ai/api/organizations": read tcp <IP_ADDRESS>:64215-><IP_ADDRESS>:7890: wsarecv: An existing connection was forcibly closed by the remote host.', 'message': 'Unknown error', 'param': None, 'type': 'internal_server_error'}} {'Access-Control-Allow-Headers': '*', 'Access-Control-Allow-Methods': '*', 'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json; charset=utf-8', 'Date': 'Tue, 19 Sep 2023 12:13:39 GMT', 'Content-Length': '273'}

使用新版本试一下，docker已同步更新了

Fixed with the latest version.
Curious is there any difference between GPT-3.5 and GPT-4 with this Claude to GPT?

Fixed with the latest version. Curious is there any difference between GPT-3.5 and GPT-4 with this Claude to GPT?

There is no difference, because in the end, the Claude interface is called and the Claude model is used

Fixed with the latest version. Curious is there any difference between GPT-3.5 and GPT-4 with this Claude to GPT?

There is no difference, because in the end, the Claude interface is called and the Claude model is used

Thank-you


Docs need to be updated

https://developers.google.com/maps/documentation/javascript/error-messages#sensor-not-required according to this the sensor=false is not required anymore.
Thanks

@pradyumna2905 Thanks for pointing out the latest change. This has been addressed.


Ignore auto_repeat for non-pandora tracks.

Add check to see if a Pandora track is being played before triggering the auto_set_repeat logic.
This is necessary as the the callback appears to be registered against Mopidy's global pykka.ThreadingActor, and the about_to_finish_callback is called for every type of track played.

Pushed https://github.com/rectalogic/mopidy-pandora/commit/ff8444e009cf6f6a1df99553a509c737d79f092b and https://github.com/rectalogic/mopidy-pandora/commit/a41a76b7e4cdf4a8cbc533550963921839dcd998 which retrieves information on the currently playing track directly from the Mopidy actor, which seems to be the only way to get updated track information for tracks that are provided by other backends.


Modify giganto-client function/enum

Add receive Ok/Err function (for giganto/reconverge/hog usage)
Add Hash trait to RecordType enum (for piglet usage)

Codecov Report
Base: 77.72% // Head: 77.53% // Decreases project coverage by -0.19% :warning:

Coverage data is based on head (2f28552) compared to base (70f8c03).
Patch coverage: 0.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #262      +/-   ##
==========================================
- Coverage   77.72%   77.53%   -0.19%
==========================================
  Files          27       27
  Lines        3744     3753       +9
==========================================
  Hits         2910     2910
- Misses        834      843       +9

Impacted Files
Coverage Δ

giganto-client/src/frame.rs
100.00% <ø> (ø)

giganto-client/src/ingest.rs
100.00% <ø> (ø)

giganto-client/src/publish.rs
71.66% <0.00%> (-1.84%)
:arrow_down:

src/publish.rs
70.31% <0.00%> (-1.35%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.