Should not be an error: No files matching the pattern "entry.js" were found.

Due to rule:
{
    rules: {
        'import/no-unused-modules': [
            'error',
            {
                ignoreExports: ['index.js', 'entry.js', 'main.js'],
                missingExports: true,
                unusedExports: true
            }
        ]
    }
}

I get the error:
> eslint . --ext .js

Oops! Something went wrong! :(

ESLint: 6.8.0.

No files matching the pattern "entry.js" were found.
Please check for typing mistakes in the pattern.

If I dont have an "entry.js" file, it should just ignore it and move on.
However, I get the error even if I have an "entry.js" file :(

Where does the config live exactly, and where does entry.js live exactly?

the config lives in the root folder and entry.js lives in the source folder

ok, so the path to entry.js from the config (and also from where you run the eslint command) is src/entry.js, not entry.js - what if you put that in your config?

Yes, it works now. But I was hoping that it'd just ignore if it can't find the file. Because I want the config to be shared among different projects that not always will follow the same file name and path structure.

In that case each project needs to define it themselves, which is all the more reason not to try to put that in the shared config. I don't think silently ignoring things is a good approach.

@ljharb, it's however pretty standard practice to have configurations silently ignore files that do not exist: .gitignore, .eslintignore, etc. And that's not just among *ignore files: include/exclude fields of tsconfig.json, files field of package.json, to name just a few.
In our projects, some have a webpack.config.ts we need this rule to ignore and some don't, some projects have a top-level index.ts and others have index.tsx where all things available outside the boundaries of each projects live (not the best example because index.ts{,x} is a valid pattern here).
Another example is our configuration has an entry for **/*.d.ts, which will break the linter when a project does not have any declaration files, but would work ok as long as there is a single file in the entire repo.
It does seem counter-intuitive to me, and the opposite of what most tools out there accustomed us to. Would you be open to reconsider your position on this? :)

@astorije you're right about the common practice, for sure - altho that's probably caused more bugs than most, which is why eslint $x now errors out if you pass it an $x that results in no matched files - and i think eslint's example is a good one to follow for an eslint plugin. (this is even where the actual source of the error comes from, i believe)
I think it's reasonable in this case, however, that as long as at least one file is found in ignoreExports, an individual glob not matching should not error.

I agree with you that my-tool my-file.js should fail if my-file.js does not exist because you're explicitly passing an argument to a command, but that's a different use case IMO. Ignore lists do not usually cause a tool to fail if there is not at least one file from the ignore list that actually exists.
Until this behavior changes, we will not be able to use this rule organization-wide unfortunately, and I wouldn't be surprised if other teams that have shared configurations encountered the same issue.
I understand we can extend shared configurations per-repositories, but it makes it harder to ensure good practices organization-wide.

I'd be happy to accept a PR that implemented the semantics I described. Would that address your use case? It seems like it would address the OP's as well.

I don't believe so. Given the following configuration:
ignoreExports:
  - webpack.config.ts

The shared configuration would fail on projects that have no webpack.config.ts files. Is that correct?

Hmm, understood. I suppose it makes sense to avoid the error in cases like this.

The --no-error-on-unmatched-pattern flag was added in v6.8.0 of ESLint.
https://eslint.org/docs/user-guide/command-line-interface#no-error-on-unmatched-pattern

Even better - if we can detect when that flag is passed, then we’d be able to follow it.


Adding OPERATING VOLTAGE Helper and use it for IPShutterContact

HMIP-SWDO-I has voltage attribute.

Since the other PR has been merged, this one now has a conflict. But before continuing work on this: what exactly is the benefit of adding the operating voltage? Isn't this value rather constant? And what type of automation would you trigger with this? Even though it's a valid parameter for some devices, adding ones that are not useful would just bloat this library.


[Feature Request] Toggle marks

I've been loving the tabline addition. It's really speeding up my harpoon interaction.
I'd love the ability to toggle marks. i.e. quick add/remove a mark.
Imagining something like the below existing within the docs;
Toggling Marks
you can toggle marks against a file;
:lua require("harpoon.mark").toggle_file()

--

P.S. Marry me Prime 💜

Can we also have the icon when toggle marks?

I toggle current buffer with "M" and it is already builtin
local mark = require('harpoon.mark')
local i = mark.get_current_index()
mark.toggle_file(i)

For indication if current file is "harpooned", I wrote custom winbar from scratch

Feel free to take a look on my config in kkpagaev/nvim.conf, code for winbar is located in lua/markbar/winbar in case you interested


Future Request: Do not delete

Starting temporary download folder cleanup!
Deleting directory 'C:\Users...\AppData\Local\Temp\TL_2d5c0dec-ae4f-4967-8d5b-93056dfde405'... done!

Here's what I'd like to see as an enhancement. Do not delete directory if my internet connection is failed for a moment. It has happened to me three times today. And say, I got to the 73% downloaded but deleting directory after a failed connection... It's hard to take :(
I can make it work after a disconnection. I can find where it stopped from the downloaded stream(time stamp etc.) and then again I would start downloading it from where it stopped. If it wouldn't delete all files, that'd be great.
I'd like to see an option which is "Do not delete directory if connection lost". That's it.
Thanks for the great application ^^

Twitch does not allow to reconnect to a server with the same token as soon as the download failed. TL already retries failed parts 3 times over the same connection before deciding to end the download with an error.
What do you want to do with all these VOD chunks? The temporary download folder is nothing the user should get involved in. It is only the source material that ffmpeg uses to merge the single video file again. I don't understand how you want to go on from a failed state. What do you want to do with the downloaded files?

I want to keep them and continue download from the disconnected point. So I would not lose all the progression. I can work with ffmpeg, so that'd a nice little addition, I thought.

If you work with ffmpeg on your own, why do you need TL then? My goal with TL is to make things easy for the users that do not know anything about video processing and downloading VODs via APIs. Users want to click on stuff and TL should download what they clicked on. That's the spirit.
Keeping the downloaded chunks and processing them is "advanced stuff" that TL tries to hide from the user. I don't like the idea of opening up TL to be some kind of "support-tool" for ffmpeg users.
There's Issue #46 that will make TL more error-proof in the future. I am not a fan of adding workaround features to software that only 3 of 100000 people actually take advantage of. I hope you understand this.

I get your philosophy. Sorry for me being one sided on the subject. Because of the disconnections, I have learned to use ffmpeg recently. Thanks for the explanation.

No problem, it's definitely valid to bring this up here. But you must see that overreacting to specific problems of a single user (sorry that you are one of these persons) is not the best solution in order to make software better. I made this mistake a lot of times in the past... and I have learned from it 😄


More advanced string creation functions

I have a sort of odd use case for ferret where I'm using it to interop with some C++ code in order to generate FFI bindings. A part of this requires generating source code in a different language and having the ability to apply templates would be helpful. Having format or even str would be useful for this case.
I went ahead and hacked up a replacement for str that relies on the std::string class, but would be nice to have str and format in core. Happy to send a PR with my str, though not sure it handles all cases and, as I said, it requires std::string.
Thanks for ferret, it's kind of weird but I like it as a hacky way to get at C++. :)

Hi,
Currently string support is problematic. Most embedded targets lacks std::string, plain C strings are also problematic due to them using continuous memory, good for performance bad for memory fragmentation. My current plan is to keep rudimentary string support as is, since currently A Ferret string is just a sequence of numbers Ferret's sequence functions allows basic string operations on them and they are platform independent. And implement proper str functions as platform dependent modules still in core but they are opted in i.e require ferret.string that uses a  std::string or ferret.arduino.string that uses String.

The simple string type Ferret supports is just fine. My gripe is there's no way for me to create a new string in Ferret from runtime values without dipping into C++.
Imagine there's a Person struct with std::string name and int age members. As a simple example, I'd like to be able to represent a struct instance as a Ferret string like this:
(defn Person->string     [p]   (str "name: " (get-name-member p) "age: " (get-age-member p))
It's completely possible I've missed the Ferret way to do this. But if not, the runtime generation of Ferret strings could be provided without changing how Ferret strings are represented. Right?

I've modified new-string from a macro to a function so instead of,
(str "first name: " (get-first-name p) " last name: " (get-last-name p)

you can write new-string, it will concat all arguments and return a string,
(new-string "first name: " (get-first-name p) " last name: " (get-last-name p))

This also fixes the issue of once you use a lazy-sequence function on a string, it is no longer a string but a lazy-sequence this will convert it to a string. Does this fix works for your use case?

Thanks! I didn’t get a chance to look at the code or try it today, but sounds like it’ll work.


feat: add some APIs from propsys.dll

Description

Related Issue
Fixes #889
Type of Change

[x] ✨ feat -- New feature (non-breaking change which adds functionality)
[ ] 🛠 fix -- Bug fix (non-breaking change which fixes an issue)
[ ] ❌ ! -- Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 refactor -- Code refactor
[ ] ✅ ci -- Build configuration change
[ ] 📝 docs -- Documentation
[ ] 🧪 test -- Test
[ ] 🗑 chore -- Chore

Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 61.73%. Comparing base (aecd0ea) to head (bf47337).

Files with missing lines
Patch %
Lines

packages/win32/lib/src/inline.dart
0.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #904      +/-   ##
==========================================
- Coverage   61.85%   61.73%   -0.12%
==========================================
  Files          33       33
  Lines        1059     1061       +2
==========================================
  Hits          655      655
- Misses        404      406       +2

Flag
Coverage Δ

win32
59.33% <0.00%> (-0.31%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines
Coverage Δ

packages/win32/lib/src/inline.dart
0.00% <0.00%> (ø)


Ability to set background opacity

At present I am able to set "backgroundImageOpacity" but  I need ability to set background opacity with the default color of the command prompt (i.e. Black) without making it appear gray!

Is this different from #5145?

Is this different from #5145?

Yes it is different from #5145 because I want to have a background opacity like in the picture below. This background opacity means that with the default background color of the terminal (like black in cmd) we can see the apps or desktop below the terminal with an opacity.

Note that you can already get a form of window transparency with the useAcrylic and acrylicOpacity parameters (see the Schema Documentation for more details). But if you don't like the acrylic blurred effect, then the feature you're probably asking for is #603.

Looks like a duplicate of that ticket. Subscribing in that one and giving it a thumbs up. I see it's on "Terminal Backlog" ... sounds ominous ;)

Yep, this is a /dupe of #603 -- we're not prioritizing it for version 1.0, but we absolutely think it's valuable and want to nail it at some point.
I just marked it Help-Wanted--it's a small token, and doesn't mean too much because we're all community-driven--which should tell people that we'd welcome contributions :smile:
When we initially specified acrylic, we wanted to expand it to some sort of "material gallery" -- glass, diffuse perspex, acrylic, all sorts of fun things. This would be on the glassier side of material.


mouse problems

Karabiner elements makes my bluetooth mouse go haywire. The cursor movement becomes jerky and it's unusable.

This happens to me too with version 11.1.8.
My keyboard is a "ThinkPad Compact Bluetooth Keyboard with TrackPoint". Vendor ID 6127 and product ID 24648.


Update README.md

reference: "on our staging server" ...  is there a permission needed?  xcode simulator opens and closes.
The type of this PR is: TYPE

This PR resolves [CX-]
Description

PR Checklist (tick all before merging)

[ ] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added an app state migration, or my changes do not require one. (What are migrations?)
[ ] I have added a CHANGELOG.yml entry or my changes do not require one.

not sure if there is a better way to ask this question;
do I need permission from "our staging server" to run the oss application?
attempting to run this locally and it crashes;
libc++abi.dylib: terminating with uncaught exception of type NSException
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[0]'
terminating with uncaught exception of type NSException
CoreSimulator 732.18.6 - Device: iPhone 12 Pro Max (04950C3A-3C45-4388-B87D-3659204E8E4C) - Runtime: iOS 14.3 (18C61) - DeviceType: iPhone 12 Pro Max

running master
havent tried 6.3.0-release yet but will do that next.
using Xcode 12.3 for development, and I did note that the documentation says:
"require using Xcode 12 for development, with the latest version (12.2.0)"
not sure if this is part of the problem.
thanks in advance!

not sure if there is a better way to ask this question;
do I need permission from "our staging server" to run the oss application?
attempting to run this locally and it crashes;
libc++abi.dylib: terminating with uncaught exception of type NSException
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[0]'
terminating with uncaught exception of type NSException
CoreSimulator 732.18.6 - Device: iPhone 12 Pro Max (04950C3A-3C45-4388-B87D-3659204E8E4C) - Runtime: iOS 14.3 (18C61) - DeviceType: iPhone 12 Pro Max

running master
havent tried 6.3.0-release yet but will do that next.
using Xcode 12.3 for development, and I did note that the documentation says:
"require using Xcode 12 for development, with the latest version (12.2.0)"
not sure if this is part of the problem.
thanks in advance!

Hi @llwp 👋

do I need permission from "our staging server" to run the oss application?

No, you shouldn't need any explicit permission.

attempting to run this locally and it crashes;

Can you verify that a .env.shared file is present within the root eigen directory? I wonder if the attempt to insert nil object from objects[0] error might be triggered if that file is not present.
You can create that file from the example by running make oss or ./scripts/setup-env-for-oss.

Hi @llwp 👋

do I need permission from "our staging server" to run the oss application?

No, you shouldn't need any explicit permission.

attempting to run this locally and it crashes;

Can you verify that a .env.shared file is present within the root eigen directory? I wonder if the attempt to insert nil object from objects[0] error might be triggered if that file is not present.
You can create that file from the example by running make oss or ./scripts/setup-env-for-oss.

yes, .env.shared it is present and in the root eigen directory.
(it actually had to be, with a mapbox key for the build to happen - good theory!)
... other thoughts?
THANK YOU

yes, .env.shared it is present and in the root eigen directory.
(it actually had to be, with a mapbox key for the build to happen - good theory!)
... other thoughts?
THANK YOU

... other thoughts?

My next thought would be echo, our feature flagging utility. Can you try running the ./scripts/update-echo script?
If that doesn't work, I might try running the ./scripts/flip-table script to attempt to reset things. I had to comment out L7-12 to skip the gradle step.

... other thoughts?

My next thought would be echo, our feature flagging utility. Can you try running the ./scripts/update-echo script?
If that doesn't work, I might try running the ./scripts/flip-table script to attempt to reset things. I had to comment out L7-12 to skip the gradle step.

ok... update-echo did not seem to alter anything
trying flip-table now

ok... update-echo did not seem to alter anything
trying flip-table now

flip-table seemed to get stuck on the android build - much to your point about the conditional and lines 7-12.
I commented them out as well and it clears Pods, node modules, packages etc etc etc...
Completed the build and running locally.
The iPhone simulator using XCode still does the same thing; that is ... it "launches" the app and rotated through some images (EchoNew.json). Ends in a crash and that nil error.
Hmm.

flip-table seemed to get stuck on the android build - much to your point about the conditional and lines 7-12.
I commented them out as well and it clears Pods, node modules, packages etc etc etc...
Completed the build and running locally.
The iPhone simulator using XCode still does the same thing; that is ... it "launches" the app and rotated through some images (EchoNew.json). Ends in a crash and that nil error.
Hmm.

I'll go ahead and close this.
We have https://artsyproduct.atlassian.net/browse/CX-531 to make some changes so that OSS contributors can run the app more easily.
If you have any specific issues or are still trying to run this, please re-open this and we will figure it out. Thanks!


Sanitize messages

Some messages contain new lines (\n) which break the Slack markdown.
Check for \n in the notification messages and replace it with \n> to avoid breaking the quote block.

Upon inspection of the affected messages, it's due to \r characters:
(1717941633, '09-Jun-2024 09:00:33', 'Beam to NuMI, BNb.\r \r No SY beam during interlocks work.')
(1717945120, '09-Jun-2024 09:58:40', 'Beam to NuMI, BNB.\r No SY beam during interlocks work.')

Adding > clashes a bit with the customizable slack message. It would work in the default, is it would avoid breaking the quote but it might add quotes in other cases...
For now, I will sanitize by completely removing any \r or \n in the incoming message strings.


High-value plugin ideas

This is a meta-issue to collect ideas for plugins that we want to see sooner rather than later, once we have some plugin infrastructure in place. (Thanks @tlambert03! :grinning:) I'm writing this in preparation for RGSoC, as plugins would make a great development project for students.

[ ] Ilastik-like interactive segmentation
[ ] Segmentation editor: merge labels, split labels with e.g. watershed, label painting
[ ] Manual registration picking correspondence points
[ ] Manual registration with parameter tuning (e.g. translation and rotation along all axes, plus optional view of a scoring metric)
[ ] Deep learning viewer a-la tensorboard
[ ] Deep learning model views (e.g. visualisation of the weights of all the layers of a model)
[ ] Regionprops viewer (polished version of @VolkerH's viewer)
[ ] Matplotlib integration (putting interactive plots in dockable widgets)
[ ] UI for interactive watershed seed selection as demonstrated with code in the blog post
[ ] Skeleton viewer + analyzer (integrated with skan)
[ ] 3D point picking and line tracing
[ ] viewing 3D+t tracks, + editing?
[ ] Register translation using skimage.

I'm rather keen to work on the regionprops viewer once a plugin infrastructure is in place. I did not follow all the issues/discussions on this during my absence in January, will read up on the pluggy discussions. Possibly @jni can bring me up to speed with this.

this is awesome and really fun about @jni!  For those reading up on this and thinking about how to implement some of these items, i think the key things to identify are:

where exactly in the napari codebase a hook function needs to be added.
what is the signature (both arguments and types) of that function that will be passed to the plugin (i.e. what hookspec would we be adding)
what considerations will there be when actually calling the hooks, collecting the results, and dealing with exceptions.

On PyPi I have grabbed the following names

napari-classification
napari-denoising
napari-detection
napari-io
napari-registration
napari-segmentation
napari-tracking

My idea for those plugins, would be to try and turn them into their own little plugin ecosystems - i.e. napari-segmentation would provide some convenience functionality that all segmentation plugins might want to use and provide hooks for specific segmentation algorithms that are more specific than the hooks provided by napari. I'm not wedded to this strategy, but thought it might be an approach of interest  further down the line. I see this approach as complementary to people who want to make a full on specific segmentation plugin themselves, and is something that might come much later for us, after some initial plugins get made from the list @jni mentions above.

[ ] add a reader plugin for the "surface" layer that uses https://github.com/nschloe/meshio - see https://github.com/vispy/vispy/issues/1817

Once there is a plugin infrastructure is in place, there are a few of us who would like to contribute to a registration plugin for napari (cc @FedeClaudi). We're particularly interested in registration of 2D sections to a 3D volume, which would likely involve a lot of manual tweaking (and napari seems perfect for).

One vote for DeepLabCut for multi-keypoints tracking of animals, cells, etc:
www.deeplabcut.org

We still need to write up developer-focused plugin documentation, but I'd just like to add a little background info here for any developers thinking ahead:
For now at least (since https://github.com/napari/napari/pull/908), what it means to "plug in" to napari is to write a function (called a "hook implementation") that will get called at some specific place (a "hook") inside of the napari codebase.  This means that for each new "type" of plugin that we want to offer support for, we need to do two things:

Determine the exact function signature that a plugin developer will need to implement: i.e. exactly what arguments will the hook function accept, what are the argument types, and what type of object will the hook return.  These signatures are called "hook specifications" and as they are added, you will find them in napari.plugins.hook_specifications.

for an example hook specification see napari_get_reader

Determine the exact line(s) in the napari codebase where that hook function will be called, and what exactly napari is supposed to do with the return value.

for example, with napari_get_reader, see this (work-in-progress) hook

If you are a developer who is particularly excited to extend napari functionality, we welcome you to familiarize yourself with the hook/hook_specification/hook_implementation pattern, and think about where in the napari codebase the hook might go.  As you come up with ideas, please open new issues or PRs to propose additional places where napari might offer hooks!

@jni can you expand on why these plugins should be "sooner than later"? because they are foundational and every bioimage analyst will want to use them? because they are a "flagship" that demonstrate how napari differentiates from competing image visualization+analysis tools? I'm curious how you are thinking about this and you would approach prioritization.

Regarding plugins in general, if they add new functionality they will typically bring new dependencies. I believe the napari developers are trying to keep unnecessary dependencies at a minimum (at least that is my impression from interactions with @jni). However, I assume that the plugins have to live in the same python environment as the viewer. I expect some of the highly desirable plugins to come with dependencies such as tensorflow (or tensorflow-gpu), pandas etc.
As the plugins probably can't live in separate python environments, are there any ideas on how to address this? I fear the dependency hell trying to create an environment in which napari and multiple plugins from different groups have to coexist. Not trivial to manage for intermediate python users and almost impossible for end-users.
To some degree, this is the problem that Cellprofiler faces with their plugins as well. There are some high-value plugins (segmentation using unet) but they don't work with the standard binary distribution of Cellprofiler. One has to create an environment in which both Cellprofiler and the plugin run.
Feel free to separate this thought from the thread where plugin ideas are collected - maybe it should have gone elsewehere, I just don't want to create to many new issues.

Super good point 👆.  Dependency hell will a very real issue with multiple plugins with heavy dependencies. Thanks @VolkerH. Possible that conda could help slightly here, but some users will likely still run into unsolveable dependencies between plugins (and the plugins would also need to have conda installs of course)

Just thought of imjoy. The plugin architecture there is based on plugins running in their own process and exchanging data with the main program via rpcs. That has some limitations when it comes to tight integration with the viewer (I'm thinking e.g.  of. GUI elements ot direct access to GPU functionality via vispy) but avoids the depedency hell.

just thinking out loud... if we did eventually want to go that direction (RPCs and messages) we could, it would just require moving away from pluggy and rolling our own plugin registration system (since pluggy is pretty much built on the assumption that you can import the plugin module at registration time).  That's might not be that big of a job though, and we can definitely take what we learn from the pluggy hooks/spec/implementation pattern when doing so... (if it comes to that).

Feel free to separate this thought from the thread where plugin ideas are collected - maybe it should have gone elsewehere, I just don't want to create too many new issues.

I just pulled of the discussion from @VolkerH and @tlambert03 on plugin dependency management into its own issue #1001 and it would be great if we could keep discussion on that there as I do see it as separate from ideas on new plugins.
@VolkerH really never worry about creating too many issues, it's actually much easier for me to keep track of more issues that are smaller / more granular and tightly focused as I can then close them when the discussion is done. In the event that you do create a new issue for a something that already had an issue it's also easier to close the duplicate issue and put that comment into the existing issue rather then pull out a discussion like the one above into something new. But really no worries either way, we're just glad you're surfacing such important points for discussion!!

Do I understand correctly that "plugins" for napari is first and foremost an architecture decision? And that when #376 or some variant is implemented, some fundamental plugins (e.g. i/o) will likely be bundled with the application?

@neuromusic bundling is its own discussion also. =)

@neuromusic re "high value" and "sooner", these are applications/workflows that I and others have already received requests for in the context of napari.

@VolkerH suggested via email that another good idea would be a plugin similar to AnnotatorJ, for semi-automatic image annotations.
AnnotatorJ: an ImageJ plugin to ease hand-annotation of cellular compartments
https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>8362v1.full.pdf

Someone at NEUBIAS asked for a Napari implementation of Stephan Saalfeld's Interactive Moving Least Squares ImageJ plugin to facilitate manual registration of cross-modal imaging data.
https://imagej.net/Interactive_Moving_Least_Squares

Also, @carsen-stringer's cellpose
https://twitter.com/computingnature/status/1224477812763119617

How about adding a pythonized CLIJ as plugin for generic image processing? We could call it clEsperanto 😉

Along with segmentation, I think it'd be great if there was a plugin for binary thresholding. That way, if I have a grayscale image, I don't need to do viewer.add_image(skimage.whatever.import(grayscale_img)) for each algorithm I want to try; instead, I can just click a few buttons and see the outputs of all the algorithms.


Welcome Page, About Dialog, Additional Open VSX Plugins

What it does

This adds a welcome page and an about dialog that explain the purpose of the blueprint application and provides useful links for the user (documentation, how to report bugs, ..)
Adds additional open vsx plugins in order to achieve good support for JavaScript, Typescript, and Java, and additional useful tools like markdown.
This increases the version to 1.9.1 so that we may test updating existing 1.9.0 application

Closes #5
Closes #9
Closes #10

How to test
Build application and review getting started page and about dialog.
Open a workspace and test language support
Review checklist

[x] as an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

as a reviewer, I agree to behave in accordance with the review guidelines

@vince would you have a look at the branding aspect of this PR?

@vince would you have a look at the branding aspect of this PR?

I have some general comments about the pull-request:

Thank you for your feedback, all good and valid points!

the about dialog is not responsive and does not display properly for smaller viewports.
the styling of the custom getting-started can be improved (especially when verifying responsiveness).
we should think of updating the applicationName for the application:

this will be used for example in the window title.
we will no longer need to hardcode theia blueprint but can rather read the applicationName once.

I opened an issue for these points: #27
In addition there is already a ticket to update the application name property: #25

we can store user level configurations under the custom name (user home - ~/.theia-blueprint) rather than the upstream default ~/.theia.

I added this to the existing tickets to update all config files: #25
To me it seems none of this is a blocker and we can go ahead with the PR?

I have some general comments about the pull-request:

Thank you for your feedback, all good and valid points!

the about dialog is not responsive and does not display properly for smaller viewports.
the styling of the custom getting-started can be improved (especially when verifying responsiveness).
we should think of updating the applicationName for the application:

this will be used for example in the window title.
we will no longer need to hardcode theia blueprint but can rather read the applicationName once.

I opened an issue for these points: #27
In addition there is already a ticket to update the application name property: #25

we can store user level configurations under the custom name (user home - ~/.theia-blueprint) rather than the upstream default ~/.theia.

I added this to the existing tickets to update all config files: #25
To me it seems none of this is a blocker and we can go ahead with the PR?

To me it seems none of this is a blocker and we can go ahead with the PR?

Absolutely. I'll have a quick look at the latest version and approve ASAP.
@vince-fugnitto everything good for you?

To me it seems none of this is a blocker and we can go ahead with the PR?

Absolutely. I'll have a quick look at the latest version and approve ASAP.
@vince-fugnitto everything good for you?

@vince-fugnitto everything good for you?

Everything looks fine as an initial update to about and getting-started for me :+1:

@vince-fugnitto everything good for you?

Everything looks fine as an initial update to about and getting-started for me :+1:

@vince-fugnitto then can you please approve?

@vince-fugnitto then can you please approve?

This is almost ready. I do not see that the comment about adding the node-debug extensions had been resolved. I'm also ok with opening an issue or adding this item to an existing issue, as you see fit

This is included by now, see line 127, 128 (https://github.com/eclipse-theia/theia-example/pull/24/files#diff-60e7eeb6bc8be48e5693ebc9be980d76bb7973ab861bf167c666b519d437f501)
The build is also green now  (Linux build is a bit brittle and the windows node sometimes loses connection :-()

This is almost ready. I do not see that the comment about adding the node-debug extensions had been resolved. I'm also ok with opening an issue or adding this item to an existing issue, as you see fit

This is included by now, see line 127, 128 (https://github.com/eclipse-theia/theia-example/pull/24/files#diff-60e7eeb6bc8be48e5693ebc9be980d76bb7973ab861bf167c666b519d437f501)
The build is also green now  (Linux build is a bit brittle and the windows node sometimes loses connection :-()

Thanks for reviewing and merging!

Thanks for reviewing and merging!

Thank you. @thegecko Could you please restart the master build?
Unfortunately the last build failed with a 403 when fetching from github: https://ci.eclipse.org/theia/job/theia-example/job/master/

Thank you. @thegecko Could you please restart the master build?
Unfortunately the last build failed with a 403 when fetching from github: https://ci.eclipse.org/theia/job/theia-example/job/master/


Next

Been rewriting most of the internals for a while. This is the result (wip).

[x] integrate hypercore so it's not just in memory
[x] migrate tests
[x] deletes
[x] diff api
[x] iterators/read-streams api
[x] changes api

@noffle i'm merging this now so I can start working on master again. I'm sure I broke some of your stuff, just let me know and I'll get it fixed :)


Store.createFragment pushes records into the store but not Store.push

Whenever store.createFragment gets called a record is pushed into the ember-data store. This doesn't happen in version 0.3.3 but I wasn't sure if this was a new behavior. Calling store.push seems to behave differently because it doesn't push any fragments into the store.
We think this may be causing an issue when combined with the stained-by-children mixin since newly saved fragments in child records are being destroyed on rollback but aren't destroyed on rollback when the data is originally loaded from the server.
Twiddle demonstrating the issue

Whenever store.createFragment gets called a record is pushed into the ember-data store. This doesn't happen in version 0.3.3 but I wasn't sure if this was a new behavior

Fragments should never be pushed into the store, so this is definitely a bug on that level :persevere:

whoops hit the wrong button sorry. Meant to say I thought the fragments appearing in the store might be a bug but wasn't sure with the 1.13 changes.

I looked into this a few weeks ago, but realized I never posted my findings. In short, it would be exceedingly difficult to prevent ED from creating live records for model fragments with the internalModel changes. I think I'd rather address concrete side effects of this behavior, e.g. the destroy on rollback issue you mentioned. Do you think you could create a failing test that demonstrates the issue?

It's probably not an actual issue with model-fragments. We're using a modified version of the stained-by-children addon to mark embedded saved records as clean and the problem we were running into was newly saved fragments in embedded objects being were being removed from the store after a rollback.
The solution we came up with was calling adapterDidCommit on every embedded child's fragments when a parent object gets saved. We also needed to fork this repo and tweak adapterDidCommit on model-fragment.js. I'm probably going to replace the fork with re-opening the class in our app.
Our use case is weird enough that I don't think its fair to expect a fix but it would be really nice to have a function to call to make fragments clean. I could put together a PR if you think it would be acceptable.

Were fragments getting removed from the store on save, or were they only getting removed when rolling back the parent record? Or does stained-by-children do a rollback as part of marking the embedded records as clean? Also, I'm unsure what the negative effects of a fragment getting removed from the store actually are; do they also get changed to the deleted state?
I'm hesitant to provide official support for marking a fragment as clean. There's a number of good reasons that ED doesn't do it, and until it does (if ever), I'd like to avoid it too.  But again, if there's an underlying issue we can address, then let's do it.

Sorry for the poor explanation of whats going on. Heres a repository showing what I'm talking about. The basic problem is that if you save a parent object with embedded records then rollback one of the embedded records any of the fragments inside that child are deleted even though they were persisted to the server. You can replicate it in the example app by clicking the add button, saving the parent record, the clicking rollback on the child. This probably isn't an issue you need to worry about so you can probably just close this issue. Thanks for the awesome addon!


react-native-template-typescript-tv fails with "Could not locate Gemfile"

Description
When running...
react-native init TestApp --template=react-native-template-typescript-tv
it errors out with Could not locate Gemfile
Version
9.2.1
Output of npx react-native info
npx react-native info
errors with
error: unknown command 'info'
(Did you mean init?)
Steps to reproduce
Run the following when you already have the cocoapods gem installed.
react-native init TestApp --template=react-native-template-typescript-tv
Snack, code example, screenshot, or link to a repository
No response

Thanks for the bug report, I will take a look.

Tracking this in https://github.com/react-native-tvos/react-native-template-typescript-tv/issues/5


[Improvement] Update chat message on reroll

Try to update the existing chat message when using reroll instead of creating a new one.

Made in 11.2.0


upgrade husky to v1

close #1906 greenkeeper's PR which didn't update the changes.
https://github.com/typicode/husky/blob/master/CHANGELOG.md#notable-changes
Config

Move hooks config from scripts field to husky field

This looks good, but I'm a bit hesitant to merge it because this newer version of husky drops support for Node.js 4, and the 0.14.0 version of Bookshelf is still aiming to maintain support for that version. However this is only a devDependency so it may not be such a big deal in terms of compatibility.

I guess that there are not so many contributors still using node v4 to develop bookshelf, so It's not a big deal to merge this.

Yeah, I agree, let's go with bleeding edge for devDependencies.


remove sdk.Context param in PoolI interface function

Background

I think PoolI interface functions should not take in a sdk.Context param because those functions don't need to access or change the state. Accessing or changing the state is done via gamm keeper's methods.
I've checked all the PoolI interface function implementations, none of them actually uses the sdk.Context passed in.

Suggested Change
We remove sdk.Context param from all the PoolI interface function

If so, should "get" functions like GetSwapFee or GetExitFee which has nothing to do with state mutations takes in sdk.Context

We explicitly need this for GetSwapFee, I don't see a reason why GetTotalShares would need to depend on state, except if a pool decided to store it in state rather than it struct. (We could add ctx there for simplicity)


Playlist is not shown when adding a song from an Album

I tried to create a new playlist by adding a song from an Album. The playlist was not shown in the Playlists tab.
However, when I add another song from Titles or Authors tab, the Playlist is shown.

Tested with the latest SNAPSHOT and found this to be working as expected.


Vue Router 404 error on page reload

Refreshing or revisiting a url on the github pages causes a 404 error, due to the way Vue Router works. There is a simple workaround described here.
It looks like an easy fix, and I'll make the changes as soon as I get a chance, but if anyone else has time before I do then go ahead!

ok - fixed. The fix depends on doing a cp index.html 404.html in dist before deploying, so if we automate deployment this should be including in the deploy.sh script.


Allow UART baudrate to be configured

In FireSim, we want the nominal PeripheryBus frequency to be 3.2 GHz. But this makes printing through the UART really slow, since the baud rate is hard-coded to 115200. This commit makes the baud rate configurable.

This only affects the initial baud rate out of reset.  This is adjustable at runtime by writing to the divisor register, so perhaps the parameter should be called initBaudRate.

Okay, I fixed it.

Is there anything blocking this PR? (aside from I guess rebasing it on top of the latest changes)?

@mwachs5: Would you or another SiFive maintainer mind taking another look at this PR?  This would let FireSim, which uses a non-standard baud rate, work with upstream bbl and OpenSBI without needing to hardcode constants in the software or hack the device tree.  Thanks!


[Feature] Improve catalog lock for paimon

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
Currently paimon only support hive lock for hive catalog, it should support unified lock for filesystem catalog
Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

Great！I want this feature, too.

+1 for this.

+1 thanks @FangYongs for driving!

Hi, after reviewing https://github.com/apache/paimon/pull/3076
I feel more description should be provided here, otherwise it may lead to incorrect design by contributors.

What is the overall options API? Do option keys require a lock prefix?
How does FileSystemCatalog build Lock? How should JdbcLock handle without a jdbc lock context? Do we need to make some modifications to JDBCLock and HiveLock?

I suggest having a clear design before considering reducing subtasks. What do you think? @FangYongs

Thanks @JingsongLi , and I completely agree with your opinion! I will create a PIP for this feature and start a discussion thread later.

@FangYongs @JingsongLi

I think that the parameters for LockContext to be open to the public should only be 'option', so there is no need to reference the connection implementation between jdbc and hive in the Filesystem Catalog, which is the future ClientPool

2.I think the parameters required for lock should be distinguished by adding a prefix of "lock." This will not cause any inconvenience to users. However, metastores like jdbc and hive, which come with their own Lock implementation, need to be compatible and do not require redeclaration of lock specific configuration parameters

The core issue is the issue of connection. If we need to create a new connection every time and close it after use, it is inevitable to have too many connections, and it may not be possible to seize them during busy times. Therefore, it is recommended to use cache to cache and set the eviction time

If possible, I can refactor according to the above description first.

+1 for this


Crash/segmentation fault during Chromium Mac bot execution

Crashes on Chromium Mac bot, at different places in build script:
https://build.chromium.org/p/client.flutter/builders/Mac/builds/6158, during "flutter build ios stocks"
===== CRASH =====
version=2.0.0-dev.61.0.flutter-c95617b19c (Wed Jun 6 13:24:42 2018 +0000) on "macos_x64"
si_signo=Segmentation fault: 11(11), si_code=0, si_addr=0x0
Dumping native stack trace for thread 2813

https://build.chromium.org/p/client.flutter/builders/Mac/builds/6159, during "run test.dart for tests shard"
===== CRASH =====
version=2.0.0-dev.61.0.flutter-c95617b19c (Wed Jun 6 13:24:42 2018 +0000) on "macos_x64"
si_signo=Segmentation fault: 11(11), si_code=0, si_addr=0x0
Dumping native stack trace for thread 1303

The ensuing build was green. All three attempted to build the same version of Flutter.

@mkustermann Are these Dart VM crashes?

Thanks for the bug, @mravn-google .
Yes, it appears that these are Dart VM crashes.
Looking at the second log:
⏩ RUNNING: cd packages/flutter; ../../bin/flutter test

00:00 +0: loading /b/build/slave/Mac/build/flutter/packages/flutter/test/animation/animation_controller_test.dart

00:53 +233: test/commands/create_test.dart: create project
00:54 +233: test/commands/create_test.dart: create project

===== CRASH =====
version=2.0.0-dev.61.0.flutter-c95617b19c (Wed Jun 6 13:24:42 2018 +0000) on "macos_x64"
si_signo=Segmentation fault: 11(11), si_code=0, si_addr=0x0
Dumping native stack trace for thread 1303

the final "All tests passed" message is not printed, so this appears, at first sight, to be a crash in the Dart VM running the tests.
The last

engine -> flutter roll 211b67708ff348a8a37fe2724fd0baf1c10a323a included
dart -> engine roll flutter/engine@f79fab1c97a2af91543984bcd656cb60b7ceb2db
which is dart-lang/sdk@4b2d60cb18e418c5cb92cf22d2d959d8b70142a3.

Since there is probably no coredump we'll need to reproduce this. I'll see if it reproduces on my linux machine, but it might be a mac-only problem.
/cc @mraleph @a-siva

Since there is too little information to diagnose this issue and it was around 2 months ago, I'll close this issue. If we see this again, we should file a new bug.


Update notification in case transaction time out

Describe the bug
Update notification in case transaction time out
To reproduce the behavior
Steps:

Perform a transaction
After approving the transaction, disconnect the internet
After 2 minutes, when the transaction change to "Failed", re-connect the internet
Observe the notification of the browser displayed

Actual:

Show incorrect status
Transaction is undefined

Expect:

If have extrinsic hash -> Show "Transaction status", Extrinsics hash
If not have extrinsic hash -> Show "Transaction status", Transaction type and Network of the transaction"

Version test: https://file.cdmteck.com/s/4oimk9zDJ8R5Aai/download?path=%2F&files=./upgrade-ui-pr-1487-build-1.0.7-1-2023-06-01T09-55-12UTC.zip
Validation passed.


Update circe-core, circe-generic, ... to 0.14.0

Updates

io.circe:circe-core
io.circe:circe-generic
io.circe:circe-parser

from 0.13.0 to 0.14.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.circe" } ]

labels: library-update, semver-minor

Superseded by #309.


has the file storage location changed?

I installed mattermost this way back in august or september. I recently updated to 4.3.1, and am wondering if the static file paths changed somehow. I had to re-upload my profile image, and while it sitll remembers the names of several custom emoji, and I can confirm their images are stored at /mattermost/data/emoji (and the corresponding host directory form my volume mapping in the docker-compose.yml file), the images are not visible when using those emojis. Also, when i add a new custom emoji that seems to work, it is not added to the above location(s)

Hey @hcientist,
In v4.2.0 and later, uploaded file attachments are now grouped by day and stored in /data/<date-of-upload-as-YYYYMMDD>/teams/...  of your file storage system.
For other important notices, see https://docs.mattermost.com/administration/important-upgrade-notes.html

@hcientist Is your problem solved ?


Change Urect::width & Urect::height to be const

Objective
The two functions
Urect::height,
Urect::width
are currently not const.
Since the methods are very unlikely to change (ever) and are useful to be const for some games, they should be.

Also just saw that #7557 is related

If only we had constant float arithmetic :( One day, maybe.

If only we had constant float arithmetic :( One day, maybe.

So true. I feel like so many crates would benefit greatly. :(
Sadly, it seems like the progress on const float arithmetics is stalled


FFQ Answer selectable

Description
Grid view of selectable buttons with 2 columns
On what platform have you tested the change?

[ ] Android - Emulator
[ ] Android - Physical device
[x] iOS - Emulator
[ ] iOS - Physical device

Screenshots

Checklist

[ ] I have updated mockServer
[ ] I've added analytics as relevent
[x] I have run npm test
[ ] I have run npm run test:i18n

@abubuwe Made commits for requested changes


ECDH context for SMTP server

Fixes #878
Switching to EC Diffie Hellman key exchange in SMTP with SSL for compliance.

Merge this, please!

As per https://github.com/postalhq/postal/issues/857#issuecomment-586310259
This particular callback is apparently removed from more recent OpenSSL versions so presumably there is a more up to date way of reaching the desired setup.


IndexError: Invalid key is out of bounds for size 0 despite having a populated dataset

Describe the bug
I am encountering an IndexError when trying to access data from a DataLoader which wraps around a dataset I've loaded using the datasets library. The error suggests that the dataset size is 0, but when I check the length and print the dataset, it's clear that it has 1166 entries.
Steps to reproduce the bug

Load a dataset with 1166 entries.
Create a DataLoader using this dataset.
Try iterating over the DataLoader.

code:
def get_train_dataloader(self) -> DataLoader:
        if self.train_dataset is None:
            raise ValueError("Trainer: training requires a train_dataset.")

        train_dataset = self.train_dataset
        data_collator = self.data_collator
        print(len(train_dataset))
        print(train_dataset)
        if is_datasets_available() and isinstance(train_dataset, datasets.Dataset):
            train_dataset = self._remove_unused_columns(train_dataset, description="training")
        else:
            data_collator = self._get_collator_with_removed_columns(data_collator, description="training")
        train_sampler = self._get_train_sampler()
        dl = DataLoader(
            train_dataset,
            batch_size=self._train_batch_size,
            sampler=train_sampler,
            collate_fn=data_collator,
            drop_last=self.args.dataloader_drop_last,
            num_workers=self.args.dataloader_num_workers,
            pin_memory=self.args.dataloader_pin_memory,
            worker_init_fn=seed_worker,
        )
        print(dl)
        print(len(dl))
        for i in dl:
            print(i)
            break
        return dl

output :
1166
Dataset({
    features: ['input_ids', 'special_tokens_mask'],
    num_rows: 1166
})
<torch.utils.data.dataloader.DataLoader object ...>
146

Error:
Traceback (most recent call last):
  File "/home/dl/zym/llamaJP/TestUseContinuePretrainLlama.py", line 266, in <module>
    train()
  File "/home/dl/zym/llamaJP/TestUseContinuePretrainLlama.py", line 260, in train
    trainer.train()
  File "/root/miniconda3/envs/LLM/lib/python3.10/site-packages/transformers/trainer.py", line 1506, in train
    return inner_training_loop(
  File "/root/miniconda3/envs/LLM/lib/python3.10/site-packages/transformers/trainer.py", line 1520, in _inner_training_loop
    train_dataloader = self.get_train_dataloader()
  File "/home/dl/zym/llamaJP/TestUseContinuePretrainLlama.py", line 80, in get_train_dataloader
    for i in dl:
  File "/root/miniconda3/envs/LLM/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 630, in __next__
    data = self._next_data()
  File "/root/miniconda3/envs/LLM/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 674, in _next_data
    data = self._dataset_fetcher.fetch(index)  # may raise StopIteration
  File "/root/miniconda3/envs/LLM/lib/python3.10/site-packages/torch/utils/data/_utils/fetch.py", line 49, in fetch
    data = self.dataset.__getitems__(possibly_batched_index)
  File "/root/miniconda3/envs/LLM/lib/python3.10/site-packages/datasets/arrow_dataset.py", line 2807, in __getitems__
    batch = self.__getitem__(keys)
  File "/root/miniconda3/envs/LLM/lib/python3.10/site-packages/datasets/arrow_dataset.py", line 2803, in __getitem__
    return self._getitem(key)
  File "/root/miniconda3/envs/LLM/lib/python3.10/site-packages/datasets/arrow_dataset.py", line 2787, in _getitem
    pa_subtable = query_table(self._data, key, indices=self._indices if self._indices is not None else None)
  File "/root/miniconda3/envs/LLM/lib/python3.10/site-packages/datasets/formatting/formatting.py", line 583, in query_table
    _check_valid_index_key(key, size)
  File "/root/miniconda3/envs/LLM/lib/python3.10/site-packages/datasets/formatting/formatting.py", line 536, in _check_valid_index_key
    _check_valid_index_key(int(max(key)), size=size)
  File "/root/miniconda3/envs/LLM/lib/python3.10/site-packages/datasets/formatting/formatting.py", line 526, in _check_valid_index_key
    raise IndexError(f"Invalid key: {key} is out of bounds for size {size}")
IndexError: Invalid key: 1116 is out of bounds for size 0

Expected behavior
I expect to be able to iterate over the DataLoader without encountering an IndexError since the dataset is populated.
Environment info

datasets library version: [2.14.5]
Platform: [Linux]
Python version: 3.10
Other libraries involved: HuggingFace Transformers

It looks to be the same issue as the one reported in https://discuss.huggingface.co/t/indexerror-invalid-key-16-is-out-of-bounds-for-size-0.
Can you check the length of train_dataset before the train_sampler = self._get_train_sampler() (and after _remove_unused_columns) line?


[Feature] Simple search functionality

The backend PR for this PR: https://github.com/benawad/vscode-stories/pull/42

Do you want to do '%' + searchInput + '%' or do you only want exact matches? Also maybe use ilike so it's case insensitive.

We can also sanatize query param searchInput, as currently its been directly passed to the native SQL query. What do you think @benawad ?

I believe TypeORM escapes $1 for you

Yeah that's there, so it will be done already. Also are we deleting stories after 24 hours or storing it forever

I was thinking if we were deleting stories after 24 hours then we don't need pagination as there will be atmost 10 stories available so we can return the stories for that user immediately

Do you want to do '%' + searchInput + '%' or do you only want exact matches? Also maybe use ilike so it's case insensitive.

My b, didn't think about case insensitivity. Yeah, imo we should also allow "similar" and not only case sensitive exact matches.

I was thinking if we were deleting stories after 24 hours then we don't need pagination as there will be atmost 10 stories available so we can return the stories for that user immediately

Yh, we would save memory and computation time - also, having an auto deletion with an interval of 1 day seems to be pretty reasonable for stories.

for now I'm keeping all the stories until I wipe the db, but that's a separate concern

for now I'm keeping all the stories until I wipe the db, but that's a separate concern

Yes I just asked to be sure as in code logic like this was not there


Nuke: Adding still image family workflow

Adding Still image nuke write rendering workflow from creator via publisher to loader.
Testing notes

start Openpype with settings and make sure you are not having any project overides on Anatomy imageio and nuke loadImage
select any node in your testing workfile and go to OpenPype Menu / Create / Create Write Still Image. Notice the name of subset will be created regarding actual frame on timeline
Publish first with local setting in render knob and then with already rendered frame.
Test Validator for rendered frames if you set already rendered frame and it was not rendered yet, it should be alarming your
Check published subset in loader and load it into scene.
in Manager set to lower version then it is actually loaded into your workfile.
all should be working as expected ;)

Task linked: PYPE-1844 nuke still image family

Task linked: PYPE-1844 nuke still image family

@mkolar did you follow the testing steps? Settings need to me treated as it is in Anatomy. Look if you see there the still write node definition in Nuke nodes ImageIO.

@mkolar did you follow the testing steps? Settings need to me treated as it is in Anatomy. Look if you see there the still write node definition in Nuke nodes ImageIO.

Thanks that was exactly it. I wiped my studio default, but project stayed. With that it works exactly as intended. I just think that the ultimate publish shouldn't have the new family, but stick to image, so we don't fragment it as much.

The same error as mentioned above

The same error as mentioned above

did you try this? https://github.com/pypeclub/OpenPype/pull/2064#issuecomment-930347375


Missing CLEVA file

CLEVA depends on a file at the following URL, but the URL returns a 404 Not Found error:
http://<IP_ADDRESS>/data/v1/dialogue_generation.zip

@Jianqiao-Zhao is there an updated URL for the dialogue_generation.zip file?

Hi @yifanmai , the file was accidentally deleted on our file server. I am working on it to fix this problem as soon as possible. Sorry for the inconvenience!

Hi @yifanmai , I have fixed this problem. Please try again to see if it persists. Thank you very much!

Looks good, thanks!


Expand Fireblocks remote signing to cover more operations and users

Problem description
Current support for Fireblocks in Guaridan is limited to signing messages going into Hedera topics (see docs). This is too restrictive, many use-cases require keys used in other (if possible all) operations to be custodied in Fireblocks.
Requirements
Expand the set of Guaridan operations in which Fireblocks API is used for signing transactions (using raw signing) remotely. See this repo for examples on how to implement this.
Definition of done

Fireblocks raw (remote) signing is used in all Guardian operations to the extent possible.
Documentation is updated accordingly

Acceptance criteria
To the extent possible, Guardian keys are in custody of Fireblocks with transactions signed remotely.

I would like to extend a bit the issue opened here by Andrey. We have a particular business case that could ease a lot the guardian implementation with Fireblocks signing service and facilitate the use of guardian based software by non tech users.
We (Allcot) would like to use fireblocks as an external signing service between Straatos and MGS.
Business needs:

We need two different configurations for the system account (straatos account) and our user accounts.
We need a centralized account registered in FireBlocks that can manage multiple VaultID for each user

First option (Guardian does everything with our admin keys)
Allcot configures a system account, the same way we configure IPFS, MongDB, etc. via .env file (or WebUI/or manual configuration in case of MGS)

Every time a new user is created, instead of creating an Hedera account, it creates a new Fireblocks vault
for each vaultID, Guardian creates an HBAR account

here the Hedera keys are generated

each user should be assigned the new vaultID

this implies that it needs to READ the account ID via Fireblocks API

every operation signed by a Guardian user should be signed by the Hedera keys inside their assigned vaultID
deletion of FB vaultIDs, accounts, etc should not be implemented by Guardian (yet)
configuration of FB credentials should be possible via APIs and .env files
we need a mock/testnet Fireblocks service for testing purposes
Guardian should always use the fake FB service for Hedera Testnet and the real FB service for Mainnet

This makes the vauldID a random number inside MongoDB

This is in case Guardian uses real FB for test:

Guardian should consider the testnet is reset every 3 months (so accountIDs are not valid anymore and must be recreated)

the best way to deal with this is to recycle the same userID and create a new the accountID under the same VaultID
backup/fallback: ignore the old ValutID, create a new one, assign the new one to the old userID. This have a list of unused VaulID on Allcot’s Fireblocks user.

Second option

pre configure Fireblocks ourselves
then Guardian links information by requesting FB keys

Co created by Giuseppe and me


Mouse event stuck on MouseJustReleased

Hello,
I noticed an issue that happens quite frequently in my app when an Interactable entity keeps receiving the MouseJustReleased event even when the mouse is at rest.
Sorry i dont have an easy repro... Though I managed to repro it in the events example, by adding more "planes" next to another, and clicking frantically on a plane then another then back etc..
Eventually you'll see the MouseJustReleased start pouring non stop, even if you take your hand off the mouse.
This seems to happen when you click on a plane then move the mouse out of the plane quickly, because it stops pourring events when you bring the cursor back on top of the stuck plane (if that makes sense)
I hope that's enought information, i'll try to find time to investigate this, might be an issue in the event system or in bevy's mouse input.
Here is the code i use to repro, in example/event.rs just replace the plane spawning by:

//plane
.spawn(PbrBundle {
mesh: meshes.add(Mesh::from(shape::Plane { size: 4.9 })),
transform: Transform::from_translation(Vec3::new(-5.0, 0.0, -5.0)),
material: materials.add(Color::rgb(1.0, 1.0, 1.0).into()),
..Default::default()
})
.with(PickableMesh::default())
.with(InteractableMesh::default())
//plane
.spawn(PbrBundle {
mesh: meshes.add(Mesh::from(shape::Plane { size: 4.9 })),
transform: Transform::from_translation(Vec3::new(0.0, 0.0, 0.0)),
material: materials.add(Color::rgb(1.0, 1.0, 1.0).into()),
..Default::default()
})
.with(PickableMesh::default())
.with(InteractableMesh::default())
//plane
.spawn(PbrBundle {
mesh: meshes.add(Mesh::from(shape::Plane { size: 4.9 })),
transform: Transform::from_translation(Vec3::new(0.0, 0.0, -5.0)),
material: materials.add(Color::rgb(1.0, 1.0, 1.0).into()),
..Default::default()
})
.with(PickableMesh::default())
.with(InteractableMesh::default())
//plane
.spawn(PbrBundle {
mesh: meshes.add(Mesh::from(shape::Plane { size: 4.9 })),
transform: Transform::from_translation(Vec3::new(-5.0, 0.0, 0.0)),
material: materials.add(Color::rgb(1.0, 1.0, 1.0).into()),
..Default::default()
})
.with(PickableMesh::default())
.with(InteractableMesh::default())

Then quickly click on 1 plane, then another, then another... etc
Hope that helps!

looks like the issue is in interactable.rs.
if the interactable is not hovered anymore, the event is never reset.
Maybe we just need to reset it to None if it's not hovered.

dirty fix (seems to work fine)

pub fn generate_click_events(
// Resources
mouse_inputs: Res<Input>,
// Queries
mut interactable_query: Query<(&mut InteractableMesh, &PickableMesh)>,
) {
for (mut interactable, pickable) in interactable_query.iter_mut() {
for group in &pickable.groups {
let hover = match interactable.hover(&group) {
Ok(false) => false,
Err(_) => false,
_ => true,
};
let new_event = interactable
.watched_mouse_inputs
.iter()
.map(|button| {
(
*button,
if !hover {
MouseDownEvents::None
} else if mouse_inputs.just_released(*button) {
MouseDownEvents::MouseJustReleased
} else if mouse_inputs.just_pressed(*button) {
MouseDownEvents::MouseJustPressed
} else {
MouseDownEvents::None
},
)
})
.collect();
interactable.mouse_down_events.insert(*group, new_event);
}
}
}

on a side note would it be possible to send events only when the state changes?

Thanks for the example and fix, I'll take a closer look soon.

on a side note would it be possible to send events only when the state changes?

That is how it should behave in practice, are you seeing extra events somewhere?

As a follow up to the "only send events when the state changes", you can use this to only run on a state change.
https://github.com/aevyrie/bevy_mod_picking/blob/a554350d771e2c71078993ac4b3d6ad3accb180c/examples/events.rs#L63-L66
PR #79 should address this issue in interactable.rs I used a slightly condensed version of the solution you provided. Thanks!

Thanks, it works fine :-)
Regarding events, i was thinking of an event queue so we dont need to check
every entity, but I guess it's not very ECS style.
On Thu, Dec 17, 2020 at 7:02 AM Aevyrie<EMAIL_ADDRESS>wrote:

As a follow up to the "only send events when the state changes", you can
use this to only run on a state change.
https://github.com/aevyrie/bevy_mod_picking/blob/a554350d771e2c71078993ac4b3d6ad3accb180c/examples/events.rs#L63-L66
PR #79 https://github.com/aevyrie/bevy_mod_picking/pull/79 should
address this issue in interactable.rs I used a slightly condensed version
of the solution you provided. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aevyrie/bevy_mod_picking/issues/66#issuecomment-747227856,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACF5UVTOZNNZTPRTQZADHTLSVGNGJANCNFSM4UAWYT7A
.

but I guess it's not very ECS style.

I'm right there with you, I'm not sure what the "best" way to do this is. I was just thinking the other day that it might make more sense to use the Bevy event system. ¯_(ツ)_/¯


Daedalus install fails with CPPDriver.hs error

When I run the install command as follows:
cabal install exe:daedalus --installdir=/Users/miked/bin --overwrite-policy=always

I get the following error:
Building executable 'daedalus' for daedalus-<IP_ADDRESS>..
[1 of 3] Compiling CPPDriver        ( exe/CPPDriver.hs, dist/build/daedalus/daedalus-tmp/CPPDriver.o )

exe/CPPDriver.hs:8:18: error:
    • Exception when trying to run compile-time code:
        exe/driver-template: getDirectoryContents:openDirStream: does not exist (No such file or directory)
      Code: embedDir "exe/driver-template"
    • In the untyped splice: $(embedDir "exe/driver-template")
  |
8 | template_files = $(embedDir "exe/driver-template")
  |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cabal: Failed to build exe:daedalus from daedalus-<IP_ADDRESS>. See the build log
above for details.

Temporary fix: edit the file CPPDriver.hs as follows:
< template_files = $(embedDir "exe/driver-template")
---
> template_files = []

Fixed


feat: [M3-7563] – Add proper support for OBJ Access Key events

Description 📝
Add support for obj_access_key_create, obj_access_key_delete, and obj_access_key_update events so that they are properly formatted in the Events dropdown and Events landing page.
Changes  🔄

Add OBJ Access Key events to eventMessageGenerator.ts

Preview 📷

Screenshot

How to test 🧪
Verification steps

Create, edit, and delete an OBJ Access Key
Observe: OBJ Access Key events should be properly formatted as shown in the screenshot in the Preview section

As an Author I have considered 🤔

[X] 👀 Doing a self review
[X] ❔ Our contribution guidelines
[X] 🤏 Splitting feature into small PRs
[X] ➕ Adding a changeset
[X] 🧪 Providing/Improving test coverage
[X] 🔐 Removing all sensitive information from the code and PR description
[X] 🚩 Using a feature flag to protect the release
[X] 👣 Providing comprehensive reproduction steps
[X] 📑 Providing or updating our documentation
[X] 🕛 Scheduling a pair reviewing session
[X] 📱 Providing mobile support
[X] ♿  Providing accessibility support

@dwiley-akamai Thank you for formatting the Access Key Events. Is this change part of the OBJ Multi-cluster feature?

Sure thing! I noticed it as an issue while looking into OMC-related stuff so I included the ticket in the epic to make sure we get it addressed (none of this is contingent on the feature flag or unreleased API changes though).


feat: get images (DO NOT MERGE - check kubeflow-ci PR first)

Repository specific list of images.
Used by CVE scanning workflows and can be used to collect images URL for airgapped setup.
Summary of changes:

Added script that retrieves image managed by charm(s).

Closing. New PR file.


Portable version for v19

Hello.
Sorry for possible incorrect placement of the issue.
I have SteamDeck and would like to launch ALVR on it. Portable v18+ worked just fine.
v19 doesn't has portable version, and simple linux version is not being worked correctly (stuck on launching).
Client on Quest2 doesn't connect to the older server (Client v19, Server v18+), so this is the main issue.

The latest version of ALVR that works on Linux seems to be the nightly from November 20th https://github.com/alvr-org/ALVR-nightly/releases/tag/v20.0.0-dev01%2Bnightly.2022.11.20 i could not get the v19 release to work.
Make sure you uninstall Steamvr completely before you go through the ALVR install instructions again.
Im on Pop! OS 22.04 (Ubuntu)


Bind action creators when dispatchToActions is an object

This adds another thing that is possible to do in react-redux; pass an object to dispatchToActions and have them automatically bound to dispatch. This allows you to create action creators as separate functions, and have them automatically be dispatched instead of wrapping them in a dispatch call yourself.
Below is an example component after this change:
import { createPost } from 'module/action-creators';

const mapDispatchToActions = {
  createPost
};

// compared to
/*
const mapDispatchToActions = (dispatch) => {
  createPost: () => dispatch(createPost())
});
*/

export default connect(undefined, mapDispatchToActions)(Ember.Component.extend({
  layout: hbs`
  <button onclick={{action "createPost"}}>Create post</button>
  `
}));

I've found myself using this exclusively in React, and I personally think it's nice to get rid of some boilerplate — of which there is already quite a bit when using Redux.

@dbashford could you carve out a little time to look this over in the next 5/7 days? Would love someone more familiar than me looking at this. I know it has been missing from the connect api since the very start so I want to be sure we solve it as you would expect

@jkarsrud great work! This truly looks dead simple :)

@jkarsrud the only request I have is to see you qire up one full flow acceptance test that shows the dispatch part in action (hitting a reducer to update some value / proving it will re render)
You mind adding a simple component like the up/down that just alters the number reducer we already use in other end-to-end test cases?

I'll take a look. May not be until next week.

And by next week I meant the week after next week. Finally digging into this now. Will let you know. =)

👍
Looks good!

One little snag which bears mentioning and might trip someone up, but not sure it is a ember-redux problem.
Here's a cut down version of one of our dispatchToActions.
const dispatchToActions = (dispatch) => ({
  toggleRequest: () => dispatch(VisualActions.toggleRequest()),
});

toggleRequest being activated via a click in the template: click=(action "toggleRequest")
Theoretically this turns into something like this:
const dispatchToActions = { toggleRequest };

However, the toggleRequest accepts a parameter that allows for explicitly setting the request flag. In some cases we may have something like...
const dispatchToActions = (dispatch) => ({
  requestOn: () => dispatch(VisualActions.toggleRequest(true)),
});

The problem with const dispatchToActions = { toggleRequest }; is that toggleRequest will now get passed the jQuery.Event from the click.
jQuery.Events probably ought not be handed to an action creator. If a dev on our team PRed something to the codebase where an e was being inspected in an action creator, the PR would get lit up. If the jQuery.Event must be inspected, I'd expect that to be handled in the component and for the result of that, some POJO or primitive, to be this.send into the action creator.
Not sure what we could/should even do in this case?

That is a snag for sure, but the problem is the same for React apps using react-redux, where you would need to wrap the action creator in a function that handles the event and calls the action creator.
So in Ember, you could make a new action that specifically handles the click event, and calls the bound action:
handleToggleClick(e) {
  this.get('toggleRequest')(true);
}

It's perhaps something that's worth mentioning in docs when showing this shorthand?
On another note, I have some spare cycles for doing OSS this week, so hopefully I'll be able to write a component and proper tests for this to prove it actually works :)

Yep, alluded to the workaround with the action in the middle. And yeah, I'd recommend a mention in the docs. Lots of people will come here from Ember proper not having React+Redux experience, so it is worth being as clear with them as possible. "In this case a jQuery.Event is being sent into your Action Creator and you may not intend for that to be the outcome."
Given in most cases (like above) bindActionCreators is allowing me to replace a long one-liner with a short one-liner, when I have to write something like the below to use the short(er)hand, I'm just going to pass and provide the function rather than the object.
handleToggleClick(e) {
  this.get('toggleRequest')(true);
}

@jkarsrud appreciate any spare cycles here :)
@dbashford thanks for the feedback! totally legit to learn more about this (as I've not used action creators myself with ember/or react)

@jkarsrud added the full e2e acceptance test over in a new PR
https://github.com/ember-redux/ember-redux/pull/107
Keeping you both in the loop here - I wanted to think about this jQuery event issue as I ran into it myself and I'd like a little more time to hack around on react-redux to see that in action.

Closing this in favour of #107.


Help indicate a node activity for maintenance

Would it be possible to help indicate that a node was stopped by an operator for maintenance for example? This would help when multiple users are using shipyard and prevent a node being restarted accidentally, maybe this could be indicated by a different colour or a text field or a "maintenance" status option ?
Thanks,
Damien

We use Swarm nodes and there is currently no way to bring down a node.  Perhaps we could use an agent for this type of functionality?  I'm closing this one specifically but if you would like something else please feel free to open a new issue.  Thanks!


Update .travis.yml

Remove pip log before caching to avoid it affecting the cache.
Add --branch argument to coverage run as the coveralls module
reports coverage to Coveralls.io now.
Test against latest nightly rather than a fixed Python 3 version so
that it doesn't have to be manually changed in future.

What does the new branch notation mean?
I assume Branches [[0, 1]] missed. for this file generally means the if statement is always True, so the else branch is not covered?
So for this file, what does Branches [[0, 100]] missed. mean, specifically the 100, as opposed to 1 in the smaller file?

Sometimes it seems to show the line of the next step in the branch that has been missed, like your latter case. Sometimes it's not so clear, like you first case. Coveralls.io doesn't seem to display the branch output from coverage.py in the clearest manner. 😞

Ah, in your first case, the branch that is missed would result in the program going from line 6 to the end of the file and that seems to be reported as a 1.

ah yes, I guess that make sense :p


🐞 [Bug]: Error when getting the consumption for a newly created twin

What happened?
when trying to get the consumption of a twin that doesn't have any contracts. it returns an error
https://gridproxy.dev.grid.tf/twins/8989/consumption
which network/s did you face the problem on?
Dev
Twin ID/s
8989
Version
0.15.15-dev
Node ID/s
No response
Farm ID/s
No response
Contract ID/s
No response
Relevant log output
"error": "sql: Scan error on column index 0, name \"sum\": converting NULL to uint64 is unsupported"

Verification

Created a new account with a twin ID 9670
Tried https://gridproxy.dev.grid.tf/twins/9670/consumption

Got no errors


[WIP] Implement overlapped operations for files

This PR contains a clangformat pass, plus an implementation of overlapped operations for files

@hardening why a separate clang-format run and not just format your changes with git clang-format -f before commit?

@akallabeth to treat other files that are marked as modified when running make clangformat


[fullScreen.js] Deutsch Translation

Adding deutsch translation for fullScreen.js

Thanks @SupLiCatinG and @SIMULATAN for the translations,
Can you make the changes requested in this pull request, or are you opening another?

I applied changes to new pull request.


copy current mouse coords to over handler event

This overwrites the pageX and pageX properties of the mouse event passed
to the over handler with the coordinates obtained from the most recent
tracked mousemove. This is usually more useful than the possibly-stale
coordinates of the pointer at "mouseenter" time.
Thisi change may break compatibility with any handler that expects the
original coordinates, though these are still available on the
event.originalEvent.
Closes briancherne/jquery-hoverIntent#11.

Note that this doesn't update the coordinates sent in the mouseout event that is passed to the out handler.


Update topics template to include NSMI v2 for each Topic_Name for Alaska

Update topics template to include NSMI v2 for each Topic_Name for Alaska

@grawdon and @breeglej Is this for tagging content later? (based on the latest decision)


Python37 64-bits and STM32WB55 :STLink error (9): Get IDCODE error

Hi all,
I have got problem during debug nucleo with STM32WB55 chip. In console after run command I got error:
PS C:\Users\pawel> C:\Users\pawel\AppData\Local\Programs\Python\Python37\Scripts\pyocd.exe gdbserver
0001639:INFO:board:Target type is stm32wb55rgvx
0002270:CRITICAL:__main__:STLink error (9): Get IDCODE error
Traceback (most recent call last):
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\__main__.py", line 343, in run
    self._COMMANDS[self._args.cmd](self)
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\__main__.py", line 571, in do_gdbserver
    with session:
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\core\session.py", line 287, in __enter__
    self.open()
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\core\session.py", line 367, in open
    self._board.init()
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\board\board.py", line 83, in init
    self.target.init()
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\core\coresight_target.py", line 164, in init
    seq.invoke()
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\utility\sequencer.py", line 208, in invoke
    resultSequence = call()
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\coresight\dap.py", line 85, in init
    self.link.connect()
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\probe\stlink_probe.py", line 118, in connect
    self._link.enter_debug(STLink.Protocol.SWD)
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\probe\stlink\stlink.py", line 256, in enter_debug
    self._check_status(response)
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\probe\stlink\stlink.py", line 294, in _check_status
    raise exceptions.ProbeError(error_message)
pyocd.core.exceptions.ProbeError: STLink error (9): Get IDCODE error

PS C:\Users\pawel> C:\Users\pawel\AppData\Local\Programs\Python\Python37\Scripts\pyocd-gdbserver.exe
0000379:WARNING:gdb_server:pyocd-gdbserver is deprecated; please use the new combined pyocd tool.
Waiting for a debug probe to be connected...
0015925:INFO:board:Target type is stm32wb55rgvx
0016545:ERROR:gdb_server:uncaught exception: STLink error (9): Get IDCODE error
Traceback (most recent call last):
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\tools\gdb_server.py", line 287, in run
    with session:
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\core\session.py", line 287, in __enter__
    self.open()
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\core\session.py", line 367, in open
    self._board.init()
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\board\board.py", line 83, in init
    self.target.init()
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\core\coresight_target.py", line 164, in init
    seq.invoke()
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\utility\sequencer.py", line 208, in invoke
    resultSequence = call()
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\coresight\dap.py", line 85, in init
    self.link.connect()
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\probe\stlink_probe.py", line 118, in connect
    self._link.enter_debug(STLink.Protocol.SWD)
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\probe\stlink\stlink.py", line 256, in enter_debug
    self._check_status(response)
  File "c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages\pyocd\probe\stlink\stlink.py", line 294, in _check_status
    raise exceptions.ProbeError(error_message)
pyocd.core.exceptions.ProbeError: STLink error (9): Get IDCODE error

I used STLink in nucleo, I upgraded it to the newest version of firmware:

Similar error occurred at Visual Studio Code when I start debug mbed program:

Version of dependencies:
PS C:\Users\pawel> pip3 install -U pyocd
Requirement already up-to-date: pyocd in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (0.23.0)
Requirement already satisfied, skipping upgrade: pyelftools in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from pyocd) (0.25)
Requirement already satisfied, skipping upgrade: pyusb<2.0,>=1.0.0b2 in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from pyocd) (1.0.2)
Requirement already satisfied, skipping upgrade: intelhex<3.0,>=2.0 in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from pyocd) (2.2.1)
Requirement already satisfied, skipping upgrade: colorama in c:\users\pawel\appdata\roaming\python\python37\site-packages (from pyocd) (0.4.1)
Requirement already satisfied, skipping upgrade: prettytable in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from pyocd) (0.7.2)
Requirement already satisfied, skipping upgrade: pyyaml<6.0,>=5.1 in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from pyocd) (5.1.2)
Requirement already satisfied, skipping upgrade: pywinusb>=0.4.0; platform_system == "Windows" in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from pyocd) (0.4.2)
Requirement already satisfied, skipping upgrade: six<2.0,>=1.0 in c:\users\pawel\appdata\roaming\python\python37\site-packages (from pyocd) (1.12.0)
Requirement already satisfied, skipping upgrade: intervaltree<4.0,>=3.0.2 in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from pyocd) (3.0.2)
Requirement already satisfied, skipping upgrade: cmsis-pack-manager>=0.2.7 in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from pyocd) (0.2.9)
Requirement already satisfied, skipping upgrade: sortedcontainers<3.0,>=2.0 in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from intervaltree<4.0,>=3.0.2->pyocd) (2.1.0)
Requirement already satisfied, skipping upgrade: appdirs>=1.4 in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from cmsis-pack-manager>=0.2.7->pyocd) (1.4.3)
Requirement already satisfied, skipping upgrade: milksnake>=0.1.2 in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from cmsis-pack-manager>=0.2.7->pyocd) (0.1.5)
Requirement already satisfied, skipping upgrade: cffi>=1.6.0 in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from milksnake>=0.1.2->cmsis-pack-manager>=0.2.7->pyocd) (1.13.2)
Requirement already satisfied, skipping upgrade: pycparser in c:\users\pawel\appdata\local\programs\python\python37\lib\site-packages (from cffi>=1.6.0->milksnake>=0.1.2->cmsis-pack-manager>=0.2.7->pyocd) (2.19)
You are using pip version 19.0.3, however version 19.3.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.

Someone have any idea what is wrong?

cc @schstm @jeromecoutant
Sorry for the slow reply. Usually a failure to read IDCODE means the target device is not powered on or is in a deep sleep mode. Please make sure you are using a debug build of your application that does not put the device to sleep.

Please try setting the connect_mode option to under-reset. This will connect to the target while the hardware reset is held asserted. You can set this option by adding -Oconnect_mode=under-reset to the command line, or put it in a config file. Of course, you cannot use this option is you want to attach to the running system.
I also recommend that you use the combined pyocd tool instead of the (deprecated) pyocd-gdbserver. The basic functionality isn't any different, but pyocd-gdbserver will be dropped in version 1.0.
(Thanks to @schstm for this suggestion!)


Request trove classifier for Hypothesis

Request to add a new Trove classifier, Framework :: Hypothesis for the Hypothesis testing ecosystem.
Why do you want to add this classifier?
There are already tens of packages on PyPI that extend Hypothesis, by providing custom strategies or integrating with another framework (here's a curated subset).  I estimate that there are 30-60 packages already on PyPI that could use this new classifier.
This classifier request is prompted by HypothesisWorks/hypothesis#1661, which observes - in my experience correctly - that it is increasingly difficult to distinguish packages that extend Hypothesis from those that simply use Hypothesis with keyword or dependency searches.  A new trove classifier Framework :: Hypothesis, like Framework :: Pytest, would make it much easier to search for Hypothesis extensions and integrations.

I've added this classifier.

Thanks @di - much appreciated!


Small text update

updating text as @rleigh-dundee said in https://github.com/openmicroscopy/ome-documentation/pull/1305

Reads ambiguously to me. "the web framework is no longer shipped with Django" means that Django no longer provides the web framework, when I think this means to say that "the OMERO web framework no longer bundles a copy of Django", which is the opposite way around.

cc: @jburel

Reads better to me

@ximenesuk see now

This all looks good in the commits. It's probably worth double checking on staging before merging.

Staging is fine thanks, merging.


Give team membership info

Hi @benbalter! This is super cool. Got it all setup for Jekyll now.
It'd be cool for users to see some (cached?) membership info, whether it's the team listed or just a count, like:

Join 11 other Jekyllers on the Build team

It could foster a sense of community, like you're not the only one?

Queueing this up as an open source Friday project for tomorrow.


[Feature][Rest-API] Add token authentication when calling API

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
Add token authentication when calling API
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

cc

Hi @Xuzhengz How do the ST server verify the token is right or not, base on what's information?
Is there need a api to generate the token first, if yes, same question how and base on what's information? Do we need import other components?


Add support for forward-tls-upstream in unbound subscriber

Closes #10

Sorry for the very late review!
This won't fly as is because it forces the unbound option which may not exist in some setups.
What we need is a generic setting like
unbound_forwardzone_options="forward-tls-upstream: yes"
Can you change your PR to support something like that please?

This has been resolved in a more generic way in e521eeddb61a556f7be6cb724642a965aee027df


[Flow] Add a pass to fold away values of tensor type with zero extents

Fixes https://github.com/openxla/iree/issues/14077
Forked from https://github.com/openxla/iree/pull/14269

The patch that Mahesh submitted for review had some testing errors. Fixed that up in this one.


[SPARK-3910] Remove pyspark/mllib/ from sys.path in tests to fix relative import issue

This patch addresses an issue where PySpark's MLlib unit tests might fail on certain environments due to circular import issues.  The root issue is that PySpark has a module named random, which shares its name as the built-in Python random.  This isn't a problem for consumers of Spark, though: numpy also has a numpy.random module, so it's perfectly fine to have qualified module names that have components that match Python built-ins.  In normal operation, the top-level pyspark directory is added to sys.path so that PySpark's random module can only be imported via pyspark.mllib.random.  However, our unit tests end up invoking ./bin/pyspark python/pyspark/mllib/clustering.py, which causes the first entry of sys.path to be the directory containing clustering.py (python/pyspark/mllib, in that case); as a result, PySpark's random module shadows the built-in Python module.  This causes numpy and other dependencies to end up importing PySpark's random, which leads to circular import errors that cause tests to fail.
To fix this, we need to prevent our tests from adding the script's directory to sys.path.  There was already some code to do this in linalg.py, so this patch just copies that code to all of the other MLlib tests.

TL;DR relative imports are a frustrating Python language feature :(

QA tests have started for   PR 3940 at commit ad38522.

This patch merges cleanly.

Also, to be clear, I think this is only relevant for backports prior to Spark 1.2, which is why I've opened this against branch-1.1.
/cc @davies, I think this should be a safe patch because it only touches test code and because we don't use relative imports in our own code.

QA tests have finished for   PR 3940 at commit ad38522.

This patch fails unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25177/
Test FAILed.

Ah, I see why this failed: the sys.path hacking has to be done at the top of the file, not at the bottom.

Would the hack we used in branch-1.2 and master work?
https://github.com/apache/spark/blob/master/python/pyspark/mllib/__init__.py

@mengxr I think so, it's better to back port that into 1.1

@davies @mengxr I agree with you; let's go ahead and backport the master and branch-1.2 change, since I don't think it breaks compatibility from a user-POV and will make it easier to backport future fixes.


Swiper multirow order of slides

I want to put 3 slidesPerView and 3 slidesPerColumn in this order:
first Slide             second slide
1|2|3                  10|11|12
4|5|6  -------->  13|14|15
7|8|9
but only can organize like this:
perColumn:
1|4|7               10|13||16
2|5|8   ------->11|14|17
3|6|9                12|15|
perRow:
1|2|3        4|5|6
7|8|9---->10|11|12
how i can fix this?

I sent a pull request that solve this issue.
#2008

Having the same problem using the latest version (4.0.5).
Does exists a fix?


Simple cleanups of the S3/HTTP backend code

Includes:

Adding copyright notices to each source file.
Use XRootD's logging framework and corresponding configuration.
Re-arrange/cleanup headers
Fix all compilation warnings identified by Mac OS X's compiler.

@jhiemstrawisc - do you know what's up with the linter here?
I mean, it does reasonable suggestions ... just its suggestions are so wide-ranging that one would lose sight of what the real changes are.  I'd suggest that we merge this (and #22 if ready) and then do a codebase-wide reformat.
(I do like the suggested reformatting changes, it's just the original stylings are quite different)

RE the linter, I think I started to add a few CI/CD pieces to this repo awhile ago, but hit a time crunch elsewhere that prevented me from getting it all in working order. I like your plan of merging #21 and #22 and then doing a repo-wide refactor.

@bbockelm It looks like our operating systems disagree about the underlying type of off_t. I see you changed various statements from %zu to %lld, and this breaks things for me on Linux:
/workspaces/xrootd-s3-dev/xrootd-s3-http/src/S3Commands.cc: In member function ‘virtual bool AmazonS3Upload::SendRequest(const string&, off_t, size_t)’:
/workspaces/xrootd-s3-dev/xrootd-s3-http/src/S3Commands.cc:400:20: error: format ‘%lld’ expects argument of type ‘long long int’, but argument 3 has type ‘off_t’ {aka ‘long int’} [-Werror=format=]
   formatstr(range, "bytes=%lld-%lld", offset, offset + size - 1);

Do you want me to take this over and worry about portability, or is that something you want to handle? I'm no multi-platform C++ guru, but I'm happy to give things a shot.

@jhiemstrawisc - can you take it over?
For this particular item: I think you can simply cast the offset to a long long int (and then use %llu in the format specifier) to avoid potential issues as that's going to always be the larger of the two and not risk truncation issues.
Note that on 32-bit systems (which are near-impossible to find these days...), it's possible off_t is 32-bit if it is a long (as many 32-bit environments used a 32-bit long) unless a certain flag was set when compiling.  This was a big headache about 20 years ago as it required a transition to use files greater than ~2GB.


NoCode un-used function.

I'm create a lot of functions inside my code but there're not support.
NoCode it's a great repository. But how I do if I don't wanna think about my code and it will be success by themself ?

no thinking will do it.


Opening GIVE at a specific position via a link

Hi! I want to create a link to direct users to a specific position in GIVE. I was wondering if GIVE has such  a function. I know one method like constructing a URL and share it to others.

If you use GIVE HUG to create your HTML code, you may use the "Default coordinates" field to specify the genomic position. You may look up gene name if the reference supports.
If you create the HTML code from scratch, you may use attribute coordinates='["chrX:XXXXX-XXXXX"]' (Single window) or coordinates='["chrX:XXXXX-XXXXX", "chrY:YYYYY-YYYYY"]' (Dual window). Please note the use of quotation marks (we recommend using single quotes outside and double quotes inside).

This function has been added in commit https://github.com/Zhong-Lab-UCSD/Genomic-Interactive-Visualization-Engine/commit/ffe886b47b78206388549306132e8f4ffdf8826f. Will work on documentation in the next major update.


Upload any type of file in Memos

Describe the solution you'd like
At present, only picture-type files can be uploaded. I hope it can support uploading any type of files, and then display them in Memos in the form of links or cards.
Type of feature
User Interface (UI)
Additional context
No response

What file types are you finding are not uploading, uploading non images is supported

Sorry, I may have used an older version of the docker image and didn't upgrade in time. It's OK at the moment. Bother