Attributes Text field length limited for adding values

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues
[x] Investigated source code

Expected Behaviour

As a user, I should be able to add more than 1000 values to a attribute in a class
Current Behaviour
I am only able to add approximately 224 values which ranges to 4091 characters with white spaces.  In my use case, an attribute needs more than 1000 values to be declared.

Possible Solution

Increasing the attribute values length would be helpful.
Steps to Reproduce (for bugs)

1.Create a class label in either a new project/task
2.Add an attributes label and add a value to generate a raw format.
3.In raw format, for the values field try adding more than 225 values with a combine length of more than 4091 characters
4.There should be pop on the left shown as below:

Context

I am trying to upload an annotated image dataset car Make, Model and colour. The Model attributes consists of highest values length. This is to the fact that every Make has a variation of Models
Your Environment

Git hash commit 75d2826a3d35324f3cc1f867fd8d1b8821ef1bce
Docker version  19.03.12
Ubuntu 18.04.4 LTS bionic

Next steps
You may join our Gitter channel for community support.

Need to fix the limitation. What is the reasonable limitation from your point of view? How did you use CVAT? Probably we can try to find an alternative way to solve the issue.

One of my attributes consists of car models, there are quite a few variations in models. I think max length for attributes is limited to 4096. This could be the limitation in my view.

actually i have the same issue with the same problem. I need to put up to 10k radio button in one attribute and so it gives the same error. how can i solve this issue if possible??

Any updates on this?

Hi @nmanovic @bsekachev
I would like to take up this issue. Could you assign this to me?

I am trying to reproduce the issue and observed that I cannot enter more than 128 characters in the values.

Hi all,
Is there any update on this issue? I'm interested in its progress and would be happy to help if needed.
Thanks,
Benjamin


Support configuration of back-off policy in RetryLoadBalancerInterceptor

RetryLoadBalancerInterceptor is internally using RetryTemplate that is created for each intercepted request but there seems to be no way how to configure back-off policy. As a result requests are retried immediately which is not very fortunate.

Similar issue in Spring Cloud Netflix https://github.com/spring-cloud/spring-cloud-netflix/issues/2195

I suppose that https://github.com/spring-cloud/spring-cloud-commons/pull/270 implements this feature request.

Yup!


Zt control

Main change is move to more general reorientation framework.

Codecov Report

Merging #26 (1397b26) into master (d3ea5e0) will decrease coverage by 6.82%.
The diff coverage is 53.96%.

@@            Coverage Diff             @@
##           master      #26      +/-   ##
==========================================
- Coverage   55.86%   49.03%   -6.83%
==========================================
  Files           7       15       +8
  Lines         145      363     +218
==========================================
+ Hits           81      178      +97
- Misses         64      185     +121

Impacted Files
Coverage Δ

src/contract.jl
0.00% <0.00%> (ø)

src/cycle.jl
0.00% <0.00%> (ø)

src/order.jl
0.00% <0.00%> (ø)

src/passes.jl
4.16% <4.16%> (ø)

src/invert.jl
25.00% <25.00%> (-58.34%)
:arrow_down:

src/param.jl
33.33% <33.33%> (-26.67%)
:arrow_down:

src/places.jl
33.33% <33.33%> (ø)

src/cfg.jl
51.85% <51.85%> (ø)

src/primitives.jl
57.14% <57.14%> (+19.64%)
:arrow_up:

src/reorient.jl
76.35% <76.35%> (ø)

... and 12 more

Continue to review full report at Codecov.

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


The plugin is too large, what is the optimization method? Can it be integrated on demand?

插件体积过于庞大，有何优化手段？能否按需集成

Can you see which files are too large for your environment? Is it files included in previous commits on this repo?

Can you see which files are too large for your environment? Is it files included in previous commits on this repo?

that what i thought, i saw before that these framework files were uploaded to previous commits from a long time ago.
@littleGnAl the repo is, i believe, over 300mb because of these mistakenly uploaded frameworks. would expect it shouldn't be more than 10mb.
could you look at stripping the large files out? i'm happy to do it if you're not able to right now, all people with clones will need to pull a forced update though, to avoid re-pushing the files

@maxxfrazer This is not that issue.

Please check https://github.com/AgoraIO-Extensions/Agora-Flutter-SDK/issues/1214


ContextMenu is invisible

From @tkvtkv on April 18, 2017 11:51
I created a ContextMenu (vaadin-context-menu-0.7.4).
 ContextMenu contextMenu = new ContextMenu(this, false);
        contextMenu.setAsContextMenuOf(butTest);

        contextMenu.addContextMenuOpenListener(new ContextMenu.ContextMenuOpenListener() {
            public void onContextMenuOpen(ContextMenu.ContextMenuOpenListener.ContextMenuOpenEvent event) {
                Notification.show("Context menu on "
                        + event.getSourceComponent().getCaption());
            }
        });

        MenuItem basic = contextMenu.addItem("Basic Item", new ContextMenu.Command() {
            public void menuSelected(com.vaadin.addon.contextmenu.MenuItem selectedItem) {
                //main.addWindow(getAboutDialog());
                labAction.setValue("ContextMenu item 'Basic Item' selected " );
            }
        });

        MenuItem second = contextMenu.addItem("Second Item", new Menu.Command() {
            public void menuSelected(com.vaadin.addon.contextmenu.MenuItem menuItem) {
                labAction.setValue("ContextMenu item 'Second Item' selected " );
            }
        });

When I right mouse click on butTest I see a notification "Context menu on ..." only. But the Context menu is invisible.

What I missed?
Please help me to understand what need to do to show a context menu.
Copied from original issue: vaadin/vaadin-core-elements#102

It happens exactly to me. Just after use 'fetch' option in <vaadin.widgetset.mode> (yesterday all was working). No matter if right now I recompile widget, still it does not appear. Now will try to delete all existing related .jar files & try to recompile.

Right now, using 'cdn' option and recompiling all, it works again. NOTE: had not deleted existing
.m2/repository/com/vaadin/vaadin-context-menu/2.0.0/vaadin-context-menu-2.0.0.jar, just changed from fetch to cdn + maven clean + maven install.

I recompiled it and now all works OK.
Thanks.

Again happens, without no changes, just usual recompilation... It fires open event, but no menu is shown.

The issue is not related to ContextMenu, you definitely have troubles with widgetset compilation or browser widgetset caching.
For more details, please refer to https://vaadin.com/docs/v8/framework/addons/addons-maven.html#addons.maven
I close the issue as not a bug.


Implement versioning ontology per issue 979

Fixes #979.

Putting into draft state - forgot to check documentation for necessary updates.

This can't be finalized until #983 is complete, since the versioning and ops files can't be downloaded so the checks fail.

Keeping in draft state until:

Issue #989 has been merged.
bundle.yaml runs versioning validation queries.

The queries should be put into a sub-module, but can do that later.

@sa-bpelakh @uscholdm Do you think it's necessary to state the version and dependencies in the ancillary ontologies as well as gistCore? It looks like a bit of overkill, and these ontologies are always versioned with gist and would likely not have dependencies different from gist's. On the other hand, for absolute correctness I suppose they are needed.

I'm just curious really - but in reference to 'absolute correctness' around dependencies, dependency ranges, and the like, did you folks look into PLOW? (As indeed, I think 'absolute correctness' is definitely a most worthy goal, as dependency issues have a very nasty habit of getting convoluted/unwieldy/nightmarish pretty quickly once out in the 'real-world'.)

Moved to 12.2.0

@sa-bpelakh: @uscholdm has raised the point that you should make sure this implementation doesn't clash with the new units and magnitudes model (shouldn't, because there is no dependency on gist, but worth checking).

This can't be finalized until #983 is complete, since the versioning and ops files can't be downloaded so the checks fail.

@rjyounes This now works.

Keeping in draft state until:

Issue Issue 372 text datatype properties #989 has been merged.

@rjyounes This has now been merged.


$convert-data Endpoint uses POST method to convert the HL7 to FHIR JSON

$convert-data Endpoint uses POST method to convert the HL7 to FHIR JSON
The document uses PUT method, which returns 404 response, instead it should use POST method.
Error when trying with PUT :
{
"resourceType": "OperationOutcome",
"id": "3566497594d7cd45a924b1106cf5a9aa",
"issue": [
{
"severity": "error",
"code": "not-found",
"diagnostics": "The requested route was not found."
}
]
}
Using POST, we get the converted JSON response.

@SherrySahni : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#please-close

Hi Ranvijay,
Can we add one liner to describe what should the request method (POST)be ?


Water stops being rendered when resizing the window

What you were trying to do
Resize Terasology's window to verify the rendering engine performs correctly
What actually happened
The water stops being rendered, leaving a big ugly hole in the ground.
How to reproduce

Either start Terasology in window mode or toggle the Fullscreen OFF before loading a game
Create/Load up a game and find a lake/sea
Resize the window by dragging one of its border - the water disappears

I suspect this also occurs when trying to take screenshots at resolutions that are different from the current window/display resolution.
Log details and game version
This problem was introduced in commit 0378926c (really ba84900) - my bad.

The plot thickens.
Simply going to the Video Settings menu and changing a setting such as Fog or Water Reflections trigger the water to show up again. Interestingly, after this operation the water stays visible even if the window is resized.
Very peculiar.

Peculiar indeed! I can confirm the issue, although "Film Grain" and "Cloud Shadows" didn't restore the water, "Fog" did though. And then yep, no further breaking on resize. Fun with states :-)

Possible addendum or very similar/related issue: the window resizing (now?) also seems to cut out block rendering in the areas the window resized to. Sample screenie (also showing the missing water again):

Going to the graphic settings and tweaking stuff fixed the water as noted above. Amusingly the fixed water then does display in the newly resized margin.
http://i.imgur.com/rvFle1u.png
Unsure if that is a separate fix is closely tied to this enough to count as the same issue. Your call @emanuele3d :-)

Closing as fixed by #2844!
At least the resizing stuff is dealt with. Not totally sure if that's the same as "weird things can happen when applying video settings changes" but I think that was improved too recently.

@Cervator There are still some oddities surrounding the video setting (like having Parallax mapping + extra lighting causes weird black edges) but that's mostly coz of shaders, everything else should be fine now. That too will be fixed very soon :D


challenge wont pass despite the correct coding

Challenge Name

https://www.freecodecamp.com/challenges/change-the-color-of-text#?solution=<h2 style%3D"color%3Ablue">CatPhotoApp<%2Fh2>
<p>Kitty ipsum dolor sit amet%2C shed everywhere shed everywhere stretching attack your ankles chase the red dot%2C hairball run catnip eat the grass sniff.<%2Fp>

Issue Description

The challenge asked to change style of h2 element by changing color to blue. I did that and when i press run test, the test just wont pass. find the attached image.
 Add a screenshot of your issue -->
![capture](https://cloud.githubusercontent.com/assets/16494206/14761175/f4e0568a-0971-11e6-80c4-6f2cca7e85fd.JPG)

resolved


react-tiptap: FloatingComposer onComposerSubmit prop not working

Describe the bug
Passing onComposerSubmit as prop to the FloatingComposer element of the @lexical/react-tiptap package does nothing.
Proposed fix
Looks like the prop isn't used at all in the source file of the FloatingComposer.
Looking at the implementation in @lexical/react-lexical, I suggest adding  props.onComposerSubmit?.(comment, event); to the handleComposerSubmit function:
  const handleComposerSubmit = useCallback(
    (comment: ComposerSubmitComment, event: FormEvent<HTMLFormElement>) => {
      const { body } = comment;
      if (!editor) {
        return;
      }
      props.onComposerSubmit?.(comment, event);
      if (event.defaultPrevented) return //straight from @lexical/react-lexical
      event.preventDefault();

      const thread = createThread({
        body,
      });
      editor.commands.addComment(thread.id);
    },
    [editor, createThread]
  );

Thanks for the report. We definitely need to abstract out the stuff that's duplicated between Lexical/TipTap so we don't keep getting diverging functionality. For now, I'll go ahead and update the component, which is also missing attachements/metadata support and we'll make a plan for anchored threads, floating composer, and floating threads to be core components in the react-ui package.


gitconfig

#2 mentions it but the linked commit did not add support for ~/.gitconfig. As per the antidot/rules.yaml, it should simply be moved to ${XDG_CONFIG_HOME}/git/config. See also git-config:

For writing options: write to global ~/.gitconfig file rather than the repository .git/config, write to $XDG_CONFIG_HOME/git/config file if this file exists and the ~/.gitconfig file doesn’t.
For reading options: read only from global ~/.gitconfig and from $XDG_CONFIG_HOME/git/config rather than from all available files.

So, yes, simply moving it should suffice.

~/.gitconfig should have been added with 6bdc0881, and it's in the file for git: https://github.com/b3nj5m1n/xdg-ninja/blob/4ee47996cb48f51a2a52d64bc5cb0e8967522e59/programs/git.json#L5-L7.
Are you not seeing it in the output when running xdg-ninja?

My bad. There is output, it was just so short compared to the others that I did not see it. In general, I find the formatting rather chaotic. Maybe an empty line before each new tool would help or by indenting the instructions or by first giving a oneline hint what is supported and what not and only then the full instructions for each tool. Also, why are the colors different? Some tools are yellow some red and the red ones are supported, it seems. Personally, I would have expected them to be green. The yellow ones are unsupported it seems, I would have expected them to be red. Maybe use yellow for some not well-supported like those requiring the export of an environment variable.


Add migrate packages command

bors r+

Codecov Report

Merging #22 into master will decrease coverage by 0.22%.
The diff coverage is 4.09%.

@@            Coverage Diff            @@
##           master     #22      +/-   ##
=========================================
- Coverage    1.69%   1.47%   -0.23%
=========================================
  Files          21      22       +1
  Lines        2413    2576     +163
  Branches     1162    1275     +113
=========================================
- Hits           41      38       -3
- Misses       2317    2479     +162
- Partials       55      59       +4

Impacted Files
Coverage Δ

src/commands/init.rs
0.00% <0.00%> (-6.14%)
:arrow_down:

src/commands/migrate_packages.rs
0.00% <0.00%> (ø)

src/fs.rs
6.94% <0.00%> (-0.41%)
:arrow_down:

src/lib.rs
0.69% <0.00%> (-0.05%)
:arrow_down:

src/project.rs
8.46% <21.87%> (+1.49%)
:arrow_up:

Continue to review full report at Codecov.

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


IFileService doesn't support binary data

The contract for resolving a file is to return IContent with value: string (or the string-stream equivalent). That API prevents us from doing a few things, such as previewing images from remote sources (see https://github.com/Microsoft/vscode/issues/34773) and things like drag and drop of files between different file systems, esp between the file-support and others.
An easy way to corrupt your data is:

have a workspace folder from disk and one from ftp
have an image file in the workspace folder from disk
dnd that onto a folder in the ftp workspace
🐛 the image is now garbage...

IMO the better API would be to just talk about bytes or chunks of bytes and turn things into a string later, e.g in the text file service. That would allow to pump data from one provider onto another provider, it would also allow to build data-uris for remote images.

As discussed - We should have methods that return streams (readable, writable) which return bytes or strings depending on the presence of a encoding. Maybe no encoding guessing in those methods?

This also prevents copying data from a 'remote' file onto the local disk

via https://github.com/Microsoft/vscode/commit/deab785846dae90cf7a72b8aaaec35945be8303c
The remaining task to make file read/write use the new service is tracked via https://github.com/Microsoft/vscode/issues/34840


[#100210316] Add invite user audit type

https://www.pivotaltracker.com/story/show/100210316
All invitations need to be audited:

Who sent the invite
When it was sent
To whom
By which supplier

:+1:


Phoenix 1.7 compatibility

Hi,
i've migrated my existing boruta backed app to phoenix 1.7 and wanted to share the diffs so that you can either pull them back into your generators or we can document them here for others to use. It is simply going through your docs step by ste. the only thing i added is a phx.gen.json step so we have a API to test against.
Here is the diff: https://github.com/norbu09/boruta_auth_phx_1_7/commit/ddc24cf6ec750f63e08b975dd53d064a3f745377
cheers
Lenz

Phoenix 1.7 was released a year ago - so can we move on to phoenix 1.7?
If the auth lib itself wokrs with phoenix 1.7 without changes - then we can just upgrade generator without breaking existing apps using it as lib.


Search by references types

Is there any way to Find document using referenced type?
Example which return empty list:
var searchDb = db.Query<Order>()     .Include(x => x.Customer)     .Include(x => x.Products)     .Where(x => x.Customer.Age > 18)     .ToList();
Example which return proper list:
var searchLocally = db.Query<Order>()     .Include(x => x.Customer)     .Include(x => x.Products)     .ToList()     .Where(x => x.Customer.Age > 18);

Hi @stravinci, it's not possible because Includes runs only on results (after apply filter). There is no join like sql. And than works in your second example because it´s a simple Linq-To-Object filter and occurs after you deserialize all documents

Hi! With the objective of organizing our issues, we are closing old unsolved issues. Please check the latest version of LiteDB and open a new issue if your problem/question/suggestion still applies. Thanks!


2.1.5 relate:fill command removes all relationships (I only have oneToMany)

Hello,
We have a fairly simple setup in our project.  Everything works great on version 2.1.4, after upgrading to the latest version, whenever we run the relate:fill command, it simply removes all the relationships.  The only thing we are doing is vanilla oneToMany relationships.  For now I've downgraded to 2.1.4 as that version continues to work great.  On 2.1.5 there is no other indication of issue.  The relate:list command runs and lists all the commands correctly.

On 2.1.5 when I run the command it appears to work great in the terminal, but the result is all the relationships are gone

Would you be able to setup an example repository that exhibits this behavior? That would help to track this down

Would you be able to setup an example repository that exhibits this behavior? That would help to track this down

I went ahead and made a VERY simple repository that exhibits the same behavior.  The relationship gets cleared from 1 side.
INSTRUCTIONS:

checkout: https://github.com/vicam-consulting/relations-test
composer install
go and look at the control panel and test the relationship between categories and products, you'll see that everything is working great (when you attach one, it will be attached on the other side etc)
now run php please relate:fill, and take a look at git and notice that all of the products have been removed from the category.  In other words the "automatic inverse" relationship is all cleared out.

Thank you very much for this! I'll take a look this week and let you know what I find out

A fix for this is available in 2.1.6


Add chat_with_documents example

Please check @sfc-gh-jcarroll

Hey @shashankdeshpande this is awesome!!! Thank you for the contribution!!
I hope you don't mind, I took the liberty to clean up a couple things on the PR.
One significant change - the current StreamlitCallbackHandler doesn't work as well as I'd like (yet!) with Retrieval Chains. I had a quick prototype version that shows more interesting results, so I swapped that one in. Take a look and let me know what you think. If you want to improve it any further, feel free.
Once you confirm it looks good (please leave a comment so I see it) I'll go ahead and get this merged 🚀

@sfc-gh-jcarroll Thanks for the feedback! The prototype version for Retrieval Chains is awesome. I think we're good to merge this PR now.


Flatten values array

If the intent is to flatten the values array this [].concat(values) is not doing it for me. Turns out this [].concat.apply([], values) does.
For example: http://jsfiddle.net/BloodyKnuckles/d7k7d0Lk/

Hi! The intent is not to flatten the values. The call is to turn something like a non-array argument (a string for an example) into a one element array. If an array is provided, it will stay as-is.
I hope that explains why we wont be accepting this PR. If you feel like the documentation in the readme can be improved, a PR with documentation change is always welcome!

I can dig it.
Is it okay to do both: convert string values to array elements, AND flatten nested arrays?
[].concat.apply([], [].concat(values))
For example: http://jsfiddle.net/BloodyKnuckles/d7k7d0Lk/1/
Or is there a reason NOT to flatten the values array provided to connection.query?

Well, you should be able to see how much just flattening breaks everything by running the tests. For example, the query field IN (?) is transformed into field IN (1,2,3) when given the argument [[1,2,3]]. After your flattening, that would no longer function.
This should be all documented in https://github.com/felixge/node-mysql#escaping-query-values . Let me know if there is a way to make the documentation more clear!

Basically, no, we will not accept flattening arrays. I was only mentioning the string because you said "If the intent is to flatten the values array this [].concat(values) is not doing it for me.". It is absolutely not our intent to flatten the arguments. You will need to do that yourself if that is your desire. Flattening breaks existing features we provide.

I get it (after reading the instructions). I don't need a "?" for every value. Nice!


Support WalletConnect in gateway

:clipboard: closed #397
Overview
Describe what your Pull Request is about in a few sentences.
Support WalletConnect in gateway
Changes
Describe your changes and implementation choices. More details make PRs easier to review.

The new supported wallet is added to wallet.service.js
Fix a crash issue on earn page on Boba Mainnet

Testing
Describe how to test your new feature/bug fix and if possible, a step by step guide on how to demo this.

On setting up with fresh meta mask failing with error on switch to avax on wrong network modal.

@Boyuan-Chen can you please help me with some to test out the wallet connect on test network!

Codecov Report
Patch and project coverage have no change.

Comparison is base (ac4b902) 48.51% compared to head (f0c0fd9) 48.51%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #625   +/-   ##
========================================
  Coverage    48.51%   48.51%
========================================
  Files          132      132
  Lines         5551     5551
  Branches      1123     1123
========================================
  Hits          2693     2693
  Misses        2858     2858

Flag
Coverage Δ

coverage
48.51% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

@Boyuan-Chen can you please help me ? how we can test out the wallet connect on test network!

I use onekey mac desktop app to test it.

@Boyuan-Chen can you please help me ? how we can test out the wallet connect on test network!

I use onekey mac desktop app to test it. The gnosis safe doesn't support the feature of switching the network.

Okay, so any idea like how do we educate user correctly as we don't have control on switching network there?

@Boyuan-Chen can you please help me ? how we can test out the wallet connect on test network!

I use onekey mac desktop app to test it. The gnosis safe doesn't support the feature of switching the network.

Okay, so any idea like how do we educate user correctly as we don't have control on switching network there?

If they pick wallet connect, they should know what they are doing. It's more complicated than MetaMask.
In onekey wallet, the walletconnect supports the network switch and everything works fine. The Gnosis is different, because it only supports Ethereum L1 and there is no Gnosis on Boba L2 (Offical Gnosis) so that switching network from L1 to L2 is impossible.


Using the LCD requires sudo

Using the LCD requires sudo ..
Debian stretch on LEGO MINDSTORMS EV3!
Last login: Mon Jan  4 01:58:49 2021 from fe80::99:40ae:6557:e588%wlx08beac054001
robot@ev3dev:~$ java -jar LcdTest.jar
[main] INFO ev3dev.actuators.LCDStretch - Instancing LCD for Stretch
[sudo] password for robot:
[main] INFO ev3dev.actuators.lego.motors.BaseRegulatedMotor - Configuring motor connected on Port: B
[main] INFO ev3dev.actuators.lego.motors.BaseRegulatedMotor - Configuring motor connected on Port: C

@JakubVanek - is there something intrinsic to the way the code works that it needs root access?

@JakubVanek - is there something intrinsic to the way the code works that it needs root access?

Yes and no. Running Java from console like this requires us to stop the brick menu via sudo systemctl stop brickman ("stolen display mode"). This is because we don't support switching to separate display manually. However, if one runs brickrun -- java -jar LcdTest.jar, then display access is granted to the Java process by brickrun ("owned display mode"). In that mode sudo shouldn't be necessary. Similar thing happens when java programs are launched viafrom brickman (possible via shell scripts, was built into https://github.com/ev3dev-lang-java/gradle-plugin)

Yes and no. Running Java from console like this requires us to stop the brick menu via sudo systemctl stop brickman ("stolen display mode"). This is because we don't support switching to separate display manually. However, if one runs brickrun -- java -jar LcdTest.jar, then display access is granted to the Java process by brickrun ("owned display mode"). In that mode sudo shouldn't be necessary. Similar thing happens when java programs are launched viafrom brickman (possible via shell scripts, was built into https://github.com/ev3dev-lang-java/gradle-plugin)

That sounds like what I was hoping for. I'll explore tonight. Thanks!

That sounds like what I was hoping for. I'll explore tonight. Thanks!

brickman seems to do the trick - next I'll get the flashing to stop.
Any downside to using it?

brickman seems to do the trick - next I'll get the flashing to stop.
Any downside to using it?

There is a peculiarity that has to be kept in mind. As specified in brickrun docs, unless -r/--redirect arguments are passed, then stdin/stdout of the program will be routed to the brick display/keyboard, not to the SSH console (SSH=redirected). However, stderr will always go to the SSH console. You can also see text from stdout on the display only when graphical mode is disabled, this stops being the case when a GraphicsLCD is constructed (switchToGraphicsMode()/switchToTextMode()).

There is a peculiarity that has to be kept in mind. As specified in brickrun docs, unless -r/--redirect arguments are passed, then stdin/stdout of the program will be routed to the brick display/keyboard, not to the SSH console (SSH=redirected). However, stderr will always go to the SSH console. You can also see text from stdout on the display only when graphical mode is disabled, this stops being the case when a GraphicsLCD is constructed (switchToGraphicsMode()/switchToTextMode()).


launching ball upwards with setVelocity does not have expected height

I was following around with trying to predict trajectories. Right now I'm isolating just the vertical component using the basic formula
vy = - sqrt(2 * g * h)

where vy is the vertical component of the initial velocity, g is gravity, and h is the height to travel. I currently have frictionAir on the ball set to 0.
I have a basic setup where the ball is on the ground. A mouse button press will setVelocity on the ball, using the calculated vy.
What results is the ball going way higher than expected. Either my understanding of the correct way of using gravity is incorrect or I'm doing something else wrong.
The isolated code (full code will also be included at the end) for just setting the velocity is:
    Events.on(mouseConstraint, "mousedown", function(event) {
        // Calculate vy based on vy = - sqrt(2 * g * h)
        let g = world.gravity.y // Note gravity is positive since y increases downwards
        let h = ball.position.y // In theory, this should be the distance of the ball to the top of the screen
        let vy = - Math.sqrt(2 * g * h)

        console.log("vy = " + vy)
        console.log("Projected height = " + h)
        launchY = ball.position.y
        Body.setVelocity(ball, {x: 0, y: vy})
        upwards = true
    })

Clearly it seems trying to use world.gravity.y is the naive approach. It appears I'm missing some conversion or perhaps my math is off.
I've tried multiplying in the world.gravity.scale but in that case, the ball doesn't even launch.
    // module aliases
    let Engine = Matter.Engine,
        Render = Matter.Render,
        World = Matter.World,
        Body = Matter.Body,
        Composite = Matter.Composite,
        Constraint = Matter.Constraint,
        MouseConstraint = Matter.MouseConstraint,
        Mouse = Matter.Mouse,
        Runner = Matter.Runner,
        Events = Matter.Events,
        Vector = Matter.Vector,
        Bodies = Matter.Bodies;

    // create an engine
    let engine = Engine.create();
    let world = engine.world;

    // create a renderer
    let render = Render.create({
        element: document.body,
        engine: engine,
        options: {
            height: 1000
        }
    });

    // Build ground
    const ballRadius = 60
    let ground = Bodies.rectangle(render.bounds.max.x / 2.0, render.bounds.max.y, render.bounds.max.x, 60, { restitution: 1, isStatic: true } );
    let ball = Bodies.circle(render.bounds.max.x / 2.0, render.bounds.max.y - ballRadius * 2, ballRadius, { restitution: 1, friction: 0, frictionAir: 0, frictionStatic: 0, restitution: 0.5 })

    // Add bodies
    World.add(world, ground)
    World.add(world, ball)

    // Add mouse
    mouse = Mouse.create(render.canvas),
        mouseConstraint = MouseConstraint.create(engine, {
            mouse: mouse,
            constraint: {
                stiffness: 0.98,
                render: {
                    visible: false
                }
            }
        });

    // Ignore mouseConstraint for now
    mouseConstraint.collisionFilter.mask = 0
    World.add(world, mouseConstraint);

    let upwards = false
    let launchY = 0

    // On mousedown, add velocity to the ball
    Events.on(mouseConstraint, "mousedown", function(event) {
        // Calculate vy based on vy = - sqrt(2 * g * h)
        let g = world.gravity.y // Note gravity is positive since y increases downwards
        let h = ball.position.y // In theory, this should be the distance of the ball to the top of the screen
        let vy = - Math.sqrt(2 * g * h)

        console.log("vy = " + vy)
        console.log("Projected height = " + h)
        launchY = ball.position.y
        Body.setVelocity(ball, {x: 0, y: vy})
        upwards = true
    })

    let useEngineRun = false

    if (useEngineRun) {
        // START - Code based on default Engine.run
        Engine.run(engine);

        // run the renderer
        Render.run(render);
        // END - Code based on default Engine.run
    } else {
        // START - Code based on using runner
        let runner =  Runner.create()
        Render.run(render);

        requestAnimationFrame(loop)
        function loop() {
            //console.log("Ball y " + ball.position.y)
            if (upwards && ball.velocity.y >= 0) {
                console.log("Distance traveled " + (launchY - ball.position.y))
                upwards = false
            }
            Engine.update(engine)
            requestAnimationFrame(loop)
        }
        // END - Code based on using runner
    }

I've been doing some more investigation around this. Much like in this issue #603, I found I need roughly the same corrective values as that author. In that issue, he cites about how the value is derived to cancel out the delta time squared.
I was looking for a way to come up with deriving that number based on known information since it seems we should have a way to get a good estimate of what the engine would do (there actually doesn't see to be a great way to do it).
This code generates roughly the correct vy. The resulting value does need to be scaled by 1.01 (roughly) to reach the desired height. This value will be referenced again below.
  let g = world.gravity.y // Note gravity is positive since y increases downwards
  let correction = 1000 * (1/60) * (1/60)
  let h = ball.getPosition().y * correction // In theory, this should be the distance of the ball to the top of the screen
  let vy = - Math.sqrt(2 * g * h)

I should also note, that in my test, I added box2d support. I have a setup where I have side by side balls, where one ball is based on matter and the other is based on box2d.
The balls start from the top of the screen and drop to verify gravity is working the same. Using a box2d scale of 100, I can see the fall of the ball is pretty much identical. Until the hit of the ground ... here things deviate slightly. I have found a restitution of 1 with matter is approximately equal to a restitution of 0.49498995 in box2d.
Moreover, I have found when using iforce2d's formula (link below) to calculate the vertical velocity opposed to the formula I was using, the box2d results are pretty much as expected (I print out the actual height reached for each ball and compare it to the desired height). Here's some sample output to the console as an example:
Box2d Projected height = 6.092009544372559, actual distance<PHONE_NUMBER>372559
Matter Distance traveled<PHONE_NUMBER>94045
Box2D Distance traveled<PHONE_NUMBER>540039

This is his formula (this is based on Box2D, hence b2Gravity).
function calculateVerticalVelocityForHeight(height) {
    if (height <= 0) {
        return 0.0
    }
    var t = 1 / 60.0
    var stepG = t * t * b2Gravity.y
    var a = 0.5 / stepG
    var b = 0.5
    var c = height
    var qSol1 = (-b - Math.sqrt(Math.abs(b * b - 4 * a * c))) / (2 * a)
    var qSol2 = (-b + Math.sqrt(Math.abs(b * b - 4 * a * c))) / (2 * a)
    var v = qSol1
    if (v < 0) {
        v = qSol2
    }
    return v * 60.0
}

I have not managed to make figure out how to create a version of calculateVerticalVelocityForHeight which will generate the correct velocity for matter.js.
Here is an example of a run. Box2d is on the right.

Both engines use Verlet integration, so I would expect roughly the same results.
But I think one thing based on reviewing #179, #240, #584, and #603 is that there seems to be a need for a better explanation of converting coordinates as well as how to derive more accurate values like in this case.
Right now, matter.js is operating on a 1:1 for pixels. box2D is a scale of 100. box2D, at least from this case, seems more predictable/derivable and was actually quite easy to get expected results.
I'd love to better understand how correction in my code above is derived (the "why"), where the correction really needs to be applied (and "why"),  as well as how to properly calculate the proper velocity. It just seems like there are some "magic numbers" that are needed to make it work, which I think is some of the basis of those issues I've cited.
As another note, when I used the
vy = sqrt(2 * g * h)

Method for deriving the initial velocity is applied to both matter and box2d, the results are nearly identical. I of course still have to use the correction value in the case of matter.
Based on https://www.iforce2d.net/b2dtut/projected-trajectory, I sort of get why you need to calculate based on time steps versus seconds. I need to go through the math a bit more, but it does make sense. Using his version, it was roughly 1.01 scaled up from when using the physics formula.
Another curious thing I noticed from my quick look at Verlet integration and how it works is your formulas seem to be slightly different. Note I didn't go through the math entirely. I'm sure you have your reasons. I'm just wondering is this also is a source for the weirdness.
Hope this isn't taken the wrong way. I think the engine is quite nice and you've done a great job. Just noticing some pain points in usage which seem valuable not just to me, but to others as well.

Any updates on this? Also struggling with impulse / force required to reach certain height.


Option: password

I was a bit confused by this, default auth is with our HA credentials, but this would over-ride that?

Password option has been removed


Fixes 2276 - Added prerequisites section

PR Summary
Fixes #2276 - Added prerequisites section.
PR Checklist

[x] Descriptive Title: This PR's title is a synopsis of the changes it proposes.
[x] Summary: This PR's summary describes the scope and intent of the change.
[x] Contributor's Guide: I have read the contributors guide.
[x] Style: This PR adheres to the style guide.

Learn Build status updates of commit 798638e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

includes/azps-prerequisites-no-header.md
:warning:Warning
View (azps-9.0.0)
Details

docs-conceptual/azps-9.0.0/create-azure-service-principal-azureps.md
:white_check_mark:Succeeded
View (azps-9.0.0)

includes/azps-prerequisites-h2.md
:white_check_mark:Succeeded
View (azps-9.0.0)

includes/azps-prerequisites-h3.md
:white_check_mark:Succeeded

includes/azps-prerequisites-no-header.md

Line 15, Column 9: [Warning: file-not-found - See documentation] Invalid file link: '../articles/cloud-shell/overview.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit adfdec6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-9.0.0/create-azure-service-principal-azureps.md
:white_check_mark:Succeeded
View (azps-9.0.0)

includes/azps-prerequisites-h2.md
:white_check_mark:Succeeded
View (azps-9.0.0)

includes/azps-prerequisites-h3.md
:white_check_mark:Succeeded

includes/azps-prerequisites-no-header.md
:white_check_mark:Succeeded
View (azps-9.0.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


publish more types

I'm using your library from typescript, I've installed it via npm and by default I can use quite a few definitions. But a lot of the inputs and outputs are not declared in index.d.ts - so for example const out: TI.MACDOutput = this.macd.getResult(); doesn't work because node_modules/technicalindicators/declarations/index.d.ts has no exported member MACDOutput
It would be nice if they were declared so we could simply use them if we're using typescript.

@gemmell I'll add the missing types in the next release

@gammell Would you mind contributing this. Thanks


Upgrade StencilJS to v4

Six Webcomponents version
3.2.1
Steps to reproduce
We are currently using version 3 of stencil
What is expected?
We should migrate to stencil v4
What is actually happening?
We are currently using version 3 of stencil
System Info
No response
Any additional comments?
No response

This has been implemented in #72


[Feature]: Add the pr-title-checker.yml and it's json for keeping tracks of PR.

Describe the feature you'd like to request
This will :
/Improved Code Organization: Consistent PR titles will enhance code organization and searchability.
/Streamlined Workflow: Integration with CodeQL and a dedicated workflow will promote efficiency and automation.
/Reduced Manual Effort: Automated checks will minimize the need for manual title review, freeing up time for development tasks.
Describe the solution you'd like
Help to future contributors
Describe alternatives you've considered
No response
Additional context
No response

Assign me @LegendSumeet under iwoc

Your SWOC CONTRIBUTOR

Your SWOC CONTRIBUTOR

I am IWOC contributor, please dd that tag along with difficulty level thanks.

@LegendSumeet tags?

Your SWOC CONTRIBUTOR

I am IWOC contributor, please dd that tag along with difficulty level thanks.

@LegendSumeet please follow the guidelines, I informed before too.


Aria2-NG error

After pulling the latest p3terx/ariang:latest image, when accessing Aria2-NG this error will show:
Internal Server Error
Couldn't list directory: No such file or directory

Before this everything was fine, I was using an image from Sep-2020. Any idea what is wrong?

Never mind about this - recreated the container from scratch and it worked fine


Merge BucketPolicyMembership into BucketPolicy?

What happened?

It seems like BucketPolicy and BucketPolicyMembership actually both manipulate the same underlying API object, per https://cloud.google.com/storage/docs/json_api/v1/buckets/setIamPolicy. This doesn't seem idiomatic - I would expect there to be a single BucketPolicy type that could be updated to add and remove members.
How can we reproduce it?

What environment did it happen in?
Crossplane version:

@turkenh I forget whether this was discussed when you implemented https://github.com/crossplane/provider-gcp/pull/291. Was there a reason to split this into two different managed resources?

TL;DR: It was because BucketPolicy resource could remove google managed policies breaking basic access to the bucket from console or cli.

@negz I don't remember any public discussion that I could refer to. However, I remember the reason why I ended up doing so. My primary use case for the resources introduced with #291 was to provision required infrastructure to run a production-grade Vault on GKE with proper configuration.
After creating a bucket and a service account for Vault storage, I need to add two members to the policy of the bucket which corresponds to the following commands:
gsutil iam ch \
  ${SERVICE_ACCOUNT}@${PROJECT_ID}.iam.gserviceaccount.com:objectAdmin \
  gs://${GCS_BUCKET_NAME}

gsutil iam ch \
  ${SERVICE_ACCOUNT}@${PROJECT_ID}.iam.gserviceaccount.com:legacyBucketReader \
  gs://${GCS_BUCKET_NAME}

My first attempt was to achieve this with a single BucketPolicy object, however, when I created a managed resource with the above two members, I could no longer access the bucket from the GKE web console since it overrides some existing google managed policies which was allowing me to do so. I believe, it was the same as in this stackoverflow post. Later I noticed that, terraform also has separate resources for policy and member and followed the same approach.

Yeah, I started using BucketPolicyMember in earnest last night after raising this issue and I can see why we've modelled it this way. I feel a little uncomfortable about potentially having N managed resources all managing the state of one API endpoint, but it does lead to a much better UX. 😬


License?

Hi,
There is currently no license attached to this project. Can you please add one. Otherwise we cannot use this wonderful project.
See: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#5-license-grant-to-other-users
Thanks,
Tom

Done!  Thanks for the link.


remove references to uproxy-obfuscators

Gah, I keep missing these.

This change is

:thumbsup:


Utf16 strings serde

Coverage increased (+0.004%) to 98.663% when pulling e65b279925b9998e106b6f0fa204e3ce1b6a3735 on utf16-strings-serde into 80c6d223a21d3d1deea7193452828922804e8841 on master.


Output path malformed when path contains 'server' in it

https://github.com/module-federation/nextjs-mf/blob/1ca2c86a51167cc792d33342968a411dad879275/packages/nextjs-mf/src/internal.ts#L214
I have a compiler output path like /my-app/packages/server/.next/server because I use next-mf in a monorepo with inside a package called server.
The getOutputPath method returns a wrong path now, because it searches for the word 'server' from the start of the path string.
Instead, it should use findLastIndex.

Ohh good one. I'll adjust

@adroste like this?
https://github.com/module-federation/universe/pull/555

Exactly. Looks good.

releasing


Fix race condition

Condition variables are used incorrectly in this code.
If signalInitialized() is called before waiting for it, it will not be registered and the thread unnecessarily waits for 100 seconds.
In addition, if the timeout expires we probably want to report this as an error but the thread instead continues to run.
Using a CountDownLatch instead of Condition and ReentrantLock fixes both problems.

YouTrack issue: https://youtrack.jetbrains.com/issue/MPS-35992/MPSHeadlessPlatformStarter-race-condition-causes-unnecessary-wait

Was merged into the code base


maybe fix zarya bubble position?

Im not sure if it works really maybe cause of different screen resolution but it should work fine for most people? but what this does is just fix the inworld text of zarya back to it. (mine used to fit in there normally so I'm also just guessing this applies to others.)

I moved the text down because ever since 2 patches ago, the icon appears on top of the inworld text and it's very hard to see.
In other words, it's intended that the cooldown text is not directly on the ability icons.


Ordinal Inscription In Correct Format, But Does Not Get Indexed - Sample Mainnet Tx Included Here

I've followed the commit/reveal procedure and created a taproot spend (for the reveal) which appears to be in the correct envelope format.
https://blockchair.com/bitcoin/transaction/67e9f1e04ce08fd9b9cc1a6cf593f898a0c1466a860770a164c7d36383f6b1d9
The second array entry in the txinwitness is:
2059bceae3a1058584801da29238e0f574ceb9703fc2915bb1ac6bd140e180ab58ac0063036f72645118746578742f706c61696e3b636861727365743d7574662d38000c68656c6c6f776f726c647a3968

Decoded to ascii is:
 Y¼êã¡¢8àõtÎ¹p?Â[±¬kÑ@á«X¬cordQtext/plain;charset=utf-8helloworldz9h

And the ASM script of the locking (scriptPubKey) is:
59bceae3a1058584801da29238e0f574ceb9703fc2915bb1ac6bd140e180ab58 OP_CHECKSIG OP_0 OP_IF 6f7264 OP_1 746578742f706c61696e3b636861727365743d7574662d38 OP_0 68656c6c6f776f726c647a39 OP_ENDIF

Broken down for visualization is:
// Pubkeycheck
59bceae3a1058584801da29238e0f574ceb9703fc2915bb1ac6bd140e180ab58 OP_CHECKSIG

// ordinals OP_0 OP_IF envelope begins
OP_0 OP_IF
    // "ord" pushbytes
    6f7264

    // OP_1 for the content-type of "text/plain;charset=utf-8"
    OP_1 746578742f706c61696e3b636861727365743d7574662d38

    // OP_0 for the body of "helloworldz9"
    OP_0 68656c6c6f776f726c647a39
OP_ENDIF

As far as I can see, I've matched the ordinals protocol exactly, if you pull up an existing inscription which is indexed correctly on ordinals.com (such as: 7050456cabbc4499820b2a5a06774262e8039fecdba5b31439f635e2a8eafa0ei0) then you will see that it is showing up correctly, but not in the example tx that I've created above.
Can someone help spot what is hopefully an obvious error?  I've looked through the ord indexer code as well and don't see why there would be a problem, the unlocking script is in the required format as far as I can tell byte for byte.

The solution will require a design decision be made (by @casey), but for now the simplest solution is going to be to swap your OP_1 (0x51) for 0x0101.
Detailed explanation for the team:
The current envelope deviates from what is presented in the docs. This appears to be due to confusion around OP_1. Specifically, while OP_0 is 0x00, OP_1 is actually 0x51.
This portion can easily be resolved by updating the documentation to reflect 0x01 instead of OP_1 (0x51).
There is additional confusion as currently inscriptions use 0x0101XX (where XX is length in bytes) between the PROTOCOL_ID and the content_type. The above statement resolves why the first 0x01 exists, but, I believe the second should be OP_PUSHDATA1 (0x4C), but it is mistakenly using 0x01 (Load one byte).
These two combined could adversely impact the ability of third-parties to implement Inscriptions (which I believe is desirable). As such, I am seeking clarification if this was intentional and if so an explicit authorization to update the definition presented in the documentation I linked above.
It is also possible that I have misread the relevant code so I will also include links to the information I used when coming to these conclusions:
https://github.com/casey/ord/blob/master/docs/src/inscriptions.md - Documentation for Inscription Envelope
https://en.bitcoin.it/wiki/Script - Quick reference for OP_X to bytes
https://github.com/casey/ord/blob/a4ee361d27265032d69bd668560a6fbbd8996de4/src/inscription.rs#L63 - Relevant code that builds the envelope

Additionally, assuming I am not wrong, the simple solution of updating the 0x01 to be 0x51 would happen here https://github.com/casey/ord/blob/a4ee361d27265032d69bd668560a6fbbd8996de4/src/inscription.rs#L17
However, I believe that doing so would be significantly more work/testing than just updating documentation to effect the envelope that was taken to production.

This is a related PR: https://github.com/casey/ord/pull/1769


Improve UI and UX of side-content components

Improve UI and UX of side-content components
Summary: Fixes a few bugs with the side-content components, including addressing #920.
Changelog

Fix odd spacing in long code blocks rendered in Autograder cells

Override text justify applied to the side-content-text container and force the cells to break words that exceed the cell width

Fix the scrollbar for horizontally overflowing side-content from scrolling the tab list out of view

The horizontal scrollbar now renders at the level of the side-content-text container instead of the side-content-tabs container

Fix missing right-padding between scrollbar and vertically overflowing side-content (#920)

The vertical scrollbar now renders at the same DOM level as that of the REPL, respecting the internal padding of bp3's Card component used in the SideContent component

Fix the failed resize of the horizontal divider separating the side-content and REPL on initial load when the side-content vertically overflowed the right-parent container

Last updated 15 Sept 2019, 08:00PM

Pull Request Test Coverage Report for Build 3514

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 36.99%

Totals

Change from base Build 3506:
0.0%

Covered Lines:
2690

Relevant Lines:
6512

💛  - Coveralls


Updates for 0.6 release

0.6 will incorporate the lifecycle stuff @natefaubion kindly worked on along with a few other things.

Ok, got a few things to update in the README still, and maybe a few other changes to go in if we sort Affable out (slamdata/purescript-aff#49), but I'm done messing around with it now.
Changes involved:
Build stuff:

Use pulp rather than gulp to build everywhere
Include a package.json in each of the example projects so the virtual-dom dependency is present for each, if someone tries to run one without using the npm run example-blah approach.
Did some horrible things to make the travis build "fast" (now it's just really slow, not excruciatingly slow)

Breaking changes:

Dropped the old Render, Eval synonyms, since the s -> ComponentHTML f / Natural f (ComponentDSL s f g) are less opaque and have basically been unused within Halogen since ComponentHTML/DSL were introduced
All the component construction functions use a record now, partially to help with the comprehensibility of the component type signature now the old synonyms are gone, but also there's no parentComponent' now. Instead the expected record for a parent component has a peek :: Maybe .... It's probably 50/50 as to whether a parent component uses peek or not, so it didn't seem bad to do that rather than having two version of parentComponent.
@natefaubion's componentSpec/parentComponentSpec have been renamed to lifecycleComponent / lifecycleParentComponent
initializer and finalizer properties have gone, in favour of ref which fires in the same situations the old properties did, but with a Maybe to distinguish between the element appearing and disappearing.
runUI now requires an element rather than providing one that can be attached later. This avoids some issues with ref/initializer firing before the element is actually in the DOM.
The stuff in Halogen.Util has been reworked to make it more useful with the new runUI.

I think that covers it. I'm not sure who should review this really... it's probably more a case of discussing the breaking change choices I made, as the code changes are mostly trivial, so any feedback is welcome @natefaubion / @jdegoes / @jonsterling etc.

If we are doing breaking changes, how do we feel about changing InstalledState to ParentState to match the other synonyms (ParentQuery, ParentHTML, etc)?

@garyb I know in IRC you mentioned getting rid of f in ParentState. I think the only thing you could do is use memo :: M.Map p (Tree f' Unit) rather than memo :: M.Map p (Tree (ParentQuery f f' p) p). If we do the map fusion on trees or thunk the html on the tree, this is mostly a no op. You'd only pay for it if virtual-dom absolutely had to rerender the memoed tree (which would only be the case if you were moving around a component without using keys).

 It's a bit tiresome but easy to remember.

That's true, yeah. I'm fine with leaving it that way too.
I made the ParentState change by the way. Do you think it makes sense to call the s -> ParentState ... function parentState too? Previously was installedState.
Just waiting on an update to aff-coroutines now, then I can remove the local FunctorAff stuff in favour of Affable.

Yeah, I think parentState is the logical choice.

FYI I've got a branch off of this with a massive performance improvement for render. When do you want to do a release of 0.6? I still need to do some testing, so it's probably best to do it in a follow up.

I'm going to finish the README updates and release it tomorrow. Looking forward to the followup :)

Bug in the lifecycle example: the Main.purs file does not define a Main module so it doesn't build correctly.

Right now, the unhook for ref has the same issue as the old finalizers. Is this expected (ie, you should not use it to do guaranteed cleanup)?

Bug in the lifecycle example

Thanks, I'll fix that.

Is this expected (ie, you should not use it to do guaranteed cleanup)?

Yep, I'll make that clear in the docs.

Ok, I've updated the docs now too. I've separated out a lot of stuff into a separate GUIDE.md file now rather than having the massive doc as the README.
@natefaubion could you do a quick scan of the README if you get a minute please? Mainly to check that I've characterised the behaviour of refs and lifecycle handlers accurately, but I've also made a bunch of other changes where things had fallen out of date so hopefully everything should be good now.

Looks good to me. I noticed a small typo: you mention eventSource' when it should be eventSource_.

Good catch, thanks!


Main Menu

Design the Main Menu and the Camera Transition

Resolved with the following commit: https://github.com/BraisGlezArias/TheHeroNeverDies/commit/7d824a27ce7406a7db7e8cab019527dccd08a640


Allow users to select between senders when requesting submissions

Problem statement
The submissions page (/submissions) currently tries to request all submissions for a given Organization and defaults to the default Sender.  However, Organizations should be able to specify if they want to request submission data from all Senders for the Organization or for an individual Sender.
What you need to know
The Platform team will:

Fix the API to pass back an empty array if there are no Senders
~Fix the API to only include submissions from the requested Organization or Sender (not default if not specified)~ - complete

See the related Slack thread for more information.
Acceptance criteria
As an Organization with one or more Senders:

[ ] I can select a specific Sender when requesting submission data on /submissions

[ ] I only see the submission data for the selected Sender

[ ] I can select all Organization-wide Senders (by selecting the Organization) when requesting submission data on /submissions

[ ] I see the submission data for all Senders in the Organization

[ ] The active sender service is selected by default

@stephenkao This will require some UI work as well to allow the user to select a specific sender, correct?
If so, I want to ensure Design gets to have input either on this ticket or a separate one.

@brandonnava What is engagement's view/desire from a user perspective on the need for a Sender Organization to be able to see not only all submissions from all senders in their organization, but also the ability to see JUST the submissions from a selected sender in the organization?

Blocked: Awaiting response from engagement.


Bug Fix Running CI Integration Test

Fix the bug, so it is possible to run Liv Doc on a CI.

There was a problem that CI run did not fetch extra project data.
The bug was caused by limited scope of the GitHub token. There is a need to add a LIV_DOC_ACCESS_TOKEN into the GH secrets, that are stored in the repository (the repo, from which we run the LIV DOC Action).
Currently workflow solution can be seen here: https://github.com/absa-group/living-doc-example-project/actions/runs/10699120043/workflow.

I approved the latest changes. The bug solution still needs to be talked about.

Release Notes Bug fix for correct CI run. Integration CI test successful.

use bullet points for release notes lines, please


Publish screenshots / video of integration creation using CLI

create a blog that includes screenshots and video showing actual creation of a new integration using the CLI

Outdated, can re-create in appropriate place when/if this gets prioritized


Adding kvh_geo_fog_3d to documentation index for distro

Requesting merge of MITRE kvh_geo_fog_3d set of packages to rosdistro for kinetic.

The travis-ci is failing when trying to find package.xml for each of the packages within this repository. I'm not sure why this is happening, as the package.xml are present.

@tfoote @sloretz Yes, you're right. My mistake. I'll modify the pull request to remove the -release repo until I get it moved over from our internal environment.


quick fix to request_feature.yml

Yeah, I missed that one 😅

1 vs 150+ , I am surprised it was just this tbh. Found it while trying to merge yours to mine lol


GSE123904 - RegenerativeLineagesLungMetastasis

Project short name:
RegenerativeLineagesLungMetastasis
Primary Wrangler:
Ida
Secondary Wrangler:
Arsenios

Associated files

Google Drive: folder

Published study links

Paper: Regenerative lineages and immune-mediated pruning in lung cancer metastasis

Accessioned data: superseries GSE123904

GSE123903 mouse host, humans scRNA-seq
GSE123902 human scRNA-seq

Ingest

Key Events

[x] Convert published metadata to HCA spreadsheet
[x] Manually curate dataset to meet HCA metadata standard
[x] Collect any matrix and cell-type annotation files
[ ] Are the analysis files suitable for CellxGene? If something is missing get in touch with the authors to request it
[x] Upload sheet to validate metadata
[x] Transfer raw files to ingest to validate data files
[x] Check linking using ingest graph validator
[ ] Ask the Secondary Wrangler for an end-to-end review of the project. Ask the Expertise Wrangler to review specific tabs if needed
[ ] Submit dataset to Production
[ ] Complete the Export SOP
[ ] Convert project data to SCEA format following the SCEA conversion SOP if appropriate

Mouse host data
Mice are employed as xenograft metastasis model. Mice are injected with H2087-LCCs (lung cell cancer) then:

metastasis are collected from 6 mice, cultured with antibiotic to select human cells over host cells

We isolated lung cancer cells from two BLI-negative kidneys that showed no signs of metastasis, yet contained DTCs. We also isolated cancer cells from one case of incipient lung metastasis and from three individual lung macrometastases that evolved spontaneously.
Cells were uniformly isolated through antibiotic selection for one passage in culture and then subjected to scRNA-seq. This selection step, which was essential because DTCs are extremely rare, likely has some effect on gene expression and is a limitation of our model.

6 mice are treated to depleate NK cells, to increase metastasis potential. Metastasis are collected

H2087-LCCs were intracardially injected  into the arterial circulation of athymic mice. Thirty days later, we administrated anti-GM1 antibody to trigger NK cell depletion which facilitates the robust outbreak of macrometastases as evidenced by BLI signal.

when reviewing please pay attention to the ontology terms and the inDrop library preparation (it would be good to review the entry in the cheat sheet)

Hello, Ida! Here are my comments.
Secondary review
Project

[ ] Lung atlas is now available in hca_bionetwork.name module in the latest update here.
[ ] Emails can be added for the two corresponding authors.

Dissociation protocol

[ ] In the best practice document, it is mentioned: No dissociation protocol for blood and other fluids, since the cells are already separated. Here, since we don't have separate RBC suspension (would be considered an enrichment protocol), I would suggest to skip the red_blood_cells_lysis protocol. It is however, worth discussion whenever we have more time.

Analysis file

[ ] missed formula at tab Analysis file, cell H37

TO BE UPDATED soon with comments on lib_prep & files

thank you for reviewing!
from my prerspective the point of red_blood_cells_lysis as a dissociation protocol is to highlight that red blood cells have been excluded from the lung cell suspension. Since the methods say "Red blood cells were lysed in red blood cell lysis solution (once or twice depending on red blood cell content)" it felt like a meaningful thing to record
Library preparation --> I'm going to put 19 as cell barcode length for now, but I'm not sure what's the best way to represent split barcodes like this one. Is it more important to get the total barcode length or the nucleotide lenght in the read, also accounting for the gap?
Thanks for spotting the formula! I've checked the submission and it looks like the formula didn't make it to ingest, which is surprising
If we get a weird validation issue it might be related this!

After discussing the dataset with the wrangler I've changed red_blood_cells_lysis into an enrichment protocol and updated the cell barcode length for inDrop to 41, to include the spacer length

additional cellxgene info in this thread


gtk4 support?

I know gBar depends on gtk+-3.0 for building, but does that means it's incompatible with gtk4? (I'd rather not have multiple sets of gtk* deps)
(I'm new to gtk stuff, apologies)

gtk3 is not compatible with gtk4, as there are many breaking changes on the C API side. And since these changes aren't small things either, gtk4 would require some major rewrites. So unfortunately gBar will depend on gtk3 for the time being.


flutter pub run build_runner build failed in CI

Details
When i run this command flutter pub run build_runner build locally, it works just fine, generates *.g.dart* files. But when i run in Gitlab CI, doesn't work. It throws an error

Logs

$ flutter pub run build_runner build
Failed to set file modification time, path = './pubspec.lock' (OS Error: Operation not permitted, errno = 1)
---- Log transcript ----
FINE: Pub 2.3.0-dev.0.5.flutter-a1668566e5
ERR : Failed to set file modification time, path = './pubspec.lock' (OS Error: Operation not permitted, errno = 1)
FINE: Exception type: FileSystemException
FINE: dart:io                                 _File.setLastModifiedSync
    | package:pub/src/io.dart 802:39          touch
    | package:pub/src/entrypoint.dart 404:9   Entrypoint.assertUpToDate
    | package:pub/src/entrypoint.dart 108:5   Entrypoint.packageGraph
    | package:pub/src/command/run.dart 70:25  RunCommand.run
    | ===== asynchronous gap ===========================
    | dart:async                              _AsyncAwaitCompleter.completeError
    | package:pub/src/command/run.dart        RunCommand.run
---- End log transcript ----
pub failed (66)

flutter docter -v
[✓] Flutter (Channel stable, v1.5.4-hotfix.2, on Linux, locale en_US.UTF-8)
    • Flutter version 1.5.4-hotfix.2 at /home/precious/Flutter
    • Framework revision 7a4c33425d (7 weeks ago), 2019-04-29 11:05:24 -0700
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /home/precious/Android/Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /home/precious/Android/Studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b16-5323222)
    • All Android licenses accepted.

[✓] Android Studio (version 3.4)
    • Android Studio at /home/precious/Android/Studio
    • Flutter plugin version 35.3.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b16-5323222)

[✓] VS Code (version 1.35.0)
    • VS Code at /usr/share/code
    • Flutter extension version 3.1.0

[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.

Gitlab CI .gitlab-ci.yml
image: cirrusci/flutter
stages:
  - build

build:apk:
  stage: build
  script:
    # - flutter pub get
    # - flutter pub run build_runner build --delete-conflicting-outputs
    - flutter packages get
    - flutter pub run build_runner build
    - flutter build apk
  artifacts:
    paths:
      - build/app/outputs/apk/release
    expire_in: 5 days

Failed to set file modification time, path = './pubspec.lock' (OS Error: Operation not permitted, errno = 1)
This means that your CI environment is lacking permissions to write files, something that build runner will need to do. This is not an issue with Flutter

@codekeyz were you able to resolve this? I ran into the same issue. Adding the gitlab-runner to group root and making sure the user is allowed to touch the pubspec.lock makes me wonder if this is really a problem of permissions.

Yes,,, not a fix actually; I refactored my CI config to this https://gist.github.com/codekeyz/75c8b5a1e771ea667d49da26611a8dfb. Do share with me if you have any fix for using the CI config with the Flutter Docker Image..

Same problem with the cirrusci/flutter image :/

Run the flutter command directly works for me:
sudo /home/cirrus/sdks/flutter/bin/flutter packages pub run build_runner build

If someone had this problem using GitLab CI and cirrusci/flutter, it is possible to use:
sudo chown -R cirrus:cirrus .

Before all commands to reset the code project permissions to the current user (which is cirrus for that image). This fixes the Failed to set file modification time, path = './pubspec.lock' (OS Error: Operation not permitted, errno = 1) error.


Add more explicit procedure on how to create gh-pages and docs repositories

Description of the feature
Following email exchange with @pkrull-ansys, we should try and improve the docs for creating the gh-pages branch on a certain repository and creating a dedicated docs repository.
We should also include information on how to set up the custom domain (if not available).
Steps for implementing the feature

Useful links and references

Thanks for opening this, @RobPasMue.

The resultant format of the issue is related with the issue templates https://github.com/pyansys/.github/issues/12. Linking this for demonstrating that issue.

I'll address this today 👍🏽

Great, let me know if you need any help!


How to use mysql as database

I want to use MySQL instead of Mongodb. How can we do this. I want to use MySQL in my project.

Sorry i didn't see this for some reason. I am working on the ability to make this easier to add configurations for other databases or styling libraries. I'm guessing you problem don't have interesting in using mysql with this anymore so im gonna close the issue just because of how long it's been. But feel free to open up another one if you are still really interested in doing this and i'll spend some time with you on it if you'd like.


Ability to move Screen Ruler utility toolbar

Description of the new feature / enhancement
Ability to move Screen Ruler utility toolbar.
Scenario when this would be used?
It won't cover the parts it shouldn't
For example, the toolbar covers the MS Edge tabs:

Supporting information
No response

/dup #23800


Update README with more info and images.

Update the README file with images to show how the card looks and give more info about the card.

Readme updated with v0.3.0 and v0.4.0 to be more instructive and has a few images that show the card.


Add some missing dev packages

They were needed for me, so maybe somebody else needs them too?

Thank you!


Desired improvements to the VM

Description
The Tevm vm currently takes a minimal set of options and has a [minimal set of actions(https://github.com/evmts/tevm-monorepo/tree/main/vm/vm/src/actions). This issue contains many sub issues that are needed to improve the VM functionality:
Improvements

[x] #763
[x] #764
[x] #765
[ ] #766
[x] #767
[x] #768

Closing in favor of prune history ticket as a solo ticket


Never_in_taxon Fungi restriction for GO:0001968 'fibronectin binding' and GO:0043236 'laminin binding'

Hello,
There were 3 annotations from out site that were affected by this new restriction. In the first paper that I went to check out (PMID:17714474) it was stating in the introduction:
"During their evolution, fungal pathogens
have acquired the ability to exploit cell surface matrix
components as ligands for attachment (Rostand & Esko,
1997). The extracellular matrix of the alveolar basal lamina
is a complex mixture of molecules, including fibronectin,
laminin, and collagens. Although the matrix is not available
for binding in normal cells, the components can be exposed
after tissue damage resulting from either inflammatory
process or lytic activity by toxins of the microorganism (Patti
et al., 1994)."
And they conclude:
"All the data indicate that TPI present on the surface
of P.  brasiliensis is able to interact with host extracellular
matrix proteins. This fungal cell-wall characterized protein
could be crucial for the initial fungal adherence and inva-
sion, thus promoting the fungal infection."
Are we sure that what the authors describe never happen in nature?
Thanks,
Penelope

@ukemi @thomaspd Would it be useful to have this under some kind of 'hijacked function' - ie this does not bind endogenous fibronectin/laminin.
Pascale

@thomaspd should comment, but to me it doesn't seem so. I think the fungal protein that binds the fibronectin has evolved to do this. The def of hijacked molecular function is:
A function that was not selected for in the evolution of an organism, but arises from co-option by another organism, e.g. a human protein used as a virus receptor.

@pgarmiri Can you use 'host cell extracellular matrix binding'? And if you need to specify which protein is bound, use 'has input'?
Thanks, Pascale

Hi @pgaudet,
In theory that would have been fine but in the particular paper they used commercial proteins (they don't specify the origin) in vitro, so  I wasn't sure that was enough to annotate to 'host cell extracellular matrix binding'. There were evidence for annotation to 'adhesion of symbiont to host cell' though. Do you think from those two different experiments the annotation you suggested could be supported?
Thanks,
Penelope

@ValWood I will remove the taxon constraints on the binding terms.
I can change
GO:0001968 	fibronectin binding 	Never in Taxon NCBITaxon:4751 	Fungi
GO:0043236 	laminin binding 	Never in Taxon  NCBITaxon:4751
to Never in pombe and cerevisiae
Thanks, Pascale


Capture full window screenshot

Description of the new feature / enhancement
If I have a windows that has scroll bars I expected to have a full capture of its contents.
Scenario when this would be used?
Every windows that has the scroll bar. But I think that the most useful, is Edge's web pages captures.
Supporting information
No response

/dup #3338


fix: don't encode with router.resolve

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

History: vuejs/vue-router#3350 > #8325 > #8421
Resolves #8429

Since<EMAIL_ADDRESS>makes it mandatory to use encodeURI when using RouterLink, NuxtLink and  router.push, we introduced a fix by automatically encoding URIs. But seems it makes regression when a query param (and probably path param) is encoded and not being properly decoded.
Current change fixes new regression but makes it mondatory to use encodeURI with $router.push ($nuxt.$router.push(encodeURI('/тест'))
Alternatives

Find a way to solve both regressions
Pin vue-router to 2.14.8

Reproduction
A:

https://codesandbox.io/s/objective-bassi-5oxri?file=/pages/index.vue
https://5oxri.sse.codesandbox.io/?t=coffee%2Cfood

B:

yarn nuxt dev test/fixtures/encoding
http://localhost:3000/ö/query?q=food,coffef

Another issue is that browser (at least chrome) changes /query?q=food%2Ccoffee to /query?q=food,coffee which makes a mismatch node issue

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Note: we see this issue when a browser visits the encoded URL (via typing, for instance), without any router push.

Codecov Report

Merging #8430 (657b68f) into dev (f4ed683) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #8430   +/-   ##
=======================================
  Coverage   68.07%   68.07%
=======================================
  Files          91       91
  Lines        3912     3912
  Branches     1069     1069
=======================================
  Hits         2663     2663
  Misses       1012     1012
  Partials      237      237

Flag
Coverage Δ

unittests
68.07% <ø> (ø)

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

Continue to review full report at Codecov.

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


Less awkward parent path example

This way shows a parent path doesn't go all the way to the root, just up one level.

Thanks @timdorr :dancer:


Hard-coded gcc

On recent FreeBSD distros, there is no gcc binary.  If you install the gcc package, you have binaries like gcc48 and g++48.  Or there's the other clang project, which is similar.
I ran across this project when compiling pump.io, which depends on it.  What I do to make pump.io is...
env CC=cc CXX=c++ MAKE=gmake npm install

And that works for most of the project dependencies, except not with libusdt.  With libusdt, I get the below error message.
gmake: Entering directory '/usr/home/d/src/pump.io/node_modules/bunyan/node_modules/dtrace-provider/build'
  ACTION binding_gyp_libusdt_target_build_libusdt .
Using node: /usr/local/bin/node
Building libusdt for i386
gmake[1]: Entering directory '/usr/home/d/src/pump.io/node_modules/bunyan/node_modules/dtrace-provider/libusdt'
rm -f *.gch
rm -f *.o
rm -f libusdt.a
rm -f test_usdt
rm -f test_usdt32
rm -f test_usdt64
gcc -O2 -Wno-error=unknown-pragmas -I/usr/src/sys/cddl/compat/opensolaris -I/usr/src/sys/cddl/contrib/opensolaris/uts/common -m32   -c -o usdt.o usdt.c
gmake[1]: gcc: Command not found
: recipe for target 'usdt.o' failed
gmake[1]: *** [usdt.o] Error 127
gmake[1]: Leaving directory '/usr/home/d/src/pump.io/node_modules/bunyan/node_modules/dtrace-provider/libusdt'

That's the short version, which I think is sufficient.  Greater detail can be found at https://dperkins.org/arc/2014-11-12.pump on freebsd.html.
I can work around the problem by making a symlink from gcc to gcc48, but that's not elegant.  It would be better if the environment variable CC worked.

I have the same problem on Solaris. It is an error in Makefile. The following line in Makefile inserts space between old path and newly added component:
PATH +=:/usr/perl5/5.10.0/bin:/usr/perl5/5.12/bin

So the PATH is then blablabla :/usr/perl5/... and make is unable to find gcc then. If I rewrite the line above as follows it works fine:
export PATH := $(PATH):/usr/perl5/5.10.0/bin:/usr/perl5/5.12/bin

However this maybe works only with GNU make. In any case it fixes the problem for me.

@jkryl that's definitely a bug, but it's not this particular issue, which is that we need to use "CC := ..." not "CC = "


Vendor Temporary helper crate for widgets

Add's Alice's helper crate for creating widgets.
Fixes #70.

Looks like you need to fix some imports in the doc tests :)


Servo Motor(s)

Create servo motor Assembly (at least one, made parametric)
Parameters should include:

Mounting points:

locations
hole diameters
flange fillet radius

Motion range (30 <= range < 360)
shaft diameter
shaft key type (and parameters)
attachment
(more?)

I'm not sure the best way to represent this, but some indication of where the data/power socket is.
Eg:  http://www.trossenrobotics.com/dynamixel-mx-28-robot-actuator.aspx
The cables are often quite difficult to plug in when the servo is mounted and it would be nice to have a cad representation of how accessible the plugs are.

That's a good point @blooop.
This would definitely be a good future improvement.
The target servo just has wires hanging out, but the servo's Assembly should have a sense of electrical connectivity. Which may eventually lead to calculated cable lengths.
As for the servo you linked, the connector would probably come from an import of KiCad.
I'll keep all this in mind while designing it 👍

Not sure if this helps, but CadQuery community member @easyw has created a workbench for integration of electronics and mechanical systems in 3D. I'm not sure if it defines electrical connector interfaces though.
I think that we'll probably want interfaces and constraints defined in CadQuery code somehow, but I always like to take a look at existing open source work when talking about things like this.

@jmwright

I always like to take a look at existing open source work when talking about things like this

That sounds like a good habit to get in to :smile:
I wouldn't want this library to dive too deeply into the electrical side of things, especially because it already seems to be done so well. (@easyw, that quad-copter looks amazing!)
(I've added #19 to track that aspect)
For something like a servo, the Assembly instance could contain a list of connections.
But I think this should be user code; an adaptation of cqparts... for example:
# library code
class Assembly:
    pass

# User Code
class ElectronicAssembly(Assembly):
    wires = []

class MyServoMotor(ElectronicAssembly):
    wires = ['GND', '+5V', 'SERVO_SIGNAL']

That's quite crude, but it's just illustrating my point.
I'd like to build that into an example, but initially make it just that; an example usage.

Oh... major point I've neglected to mention in all this...
This ServoMotor assembly is a functional example of the cqparts library.
It's a case-study I'll be implementing, mainly to show that everything works, and to demonstrate how to use it.
This will not be the root of all future servo-motors to use as an implementation base.

Removed from initial release project...
I'd still like to do this, but I need to release this before I go mad.

once dc motors are settled I will hit this.


[SMALLFIX] Test improvements

We've had a series of flaky tests in our build lately. This PR aims to make it easier to determine the root cause of these flakes.

Make logs more useful for debugging. Previously all tests would dump their logs into the same file, making it difficult to find the relevant logs from Jenkins test failures. This PR changes the behavior so that we reset the logs after each test, and save the logs for failed tests under a classname-mathodname.log file. Note that this change doesn't play well with running multiple test suites concurrently.
Remove tests that were creating unreadable files. Those files have been building up on jenkins because we can't clean them up.
Minor improvements to AlluxioTestDirectory and MultiProcessCluster

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17994/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18000/
Test PASSed.

@calvinjia Comments addressed, PTAL

@aaudiber Thanks, had a follow up question about the exception message logging.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18028/Build result: FAILURE[...truncated 3706 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/pom.xml to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/common/target/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar to org.alluxio/alluxio-core-common/1.7.0-SNAPSHOT/alluxio-core-common-1.7.0-SNAPSHOT-tests.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/pom.xml to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/worker/target/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-worker/1.7.0-SNAPSHOT/alluxio-core-server-worker-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/pom.xml to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/logserver/target/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-logserver/1.7.0-SNAPSHOT/alluxio-logserver-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/client/pom.xml to org.alluxio/alluxio-core-client/1.7.0-SNAPSHOT/alluxio-core-client-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/target/alluxio-examples-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-examples/1.7.0-SNAPSHOT/alluxio-examples-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/pom.xml to org.alluxio/alluxio-core/1.7.0-SNAPSHOT/alluxio-core-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/pom.xml to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/proxy/target/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-proxy/1.7.0-SNAPSHOT/alluxio-core-server-proxy-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/pom.xml to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/shell/target/alluxio-shell-1.7.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-shell/1.7.0-SNAPSHOT/alluxio-shell-1.7.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/tests/pom.xml to org.alluxio/alluxio-tests/1.7.0-SNAPSHOT/alluxio-tests-1.7.0-SNAPSHOT.pomchannel stoppedArchiving artifacts
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18031/
Test PASSed.


driverless fails with "ERROR: ippfind (PID ...) stopped with status 1!" possibly false alarm?

I use cups-filters 1.28.8 with CUPS 2.3.3op2 on openSUSE Leap 15.2 x86_64.
In /var/log/cups/error_log I noticed that after lpinfo -v the following appears (excerpt)
D [08/Jun/2021:08:57:35 +0200] [cups-deviced] Started backend /usr/lib/cups/backend/driverless (PID 6729)
D [08/Jun/2021:08:57:35 +0200] [CGI] Started ippfind (PID 6746)
E [08/Jun/2021:08:57:35 +0200] [CGI] ippfind (PID 6746) stopped with status 1!
E [08/Jun/2021:08:57:35 +0200] [cups-deviced] PID 6729 (driverless) stopped with status 1!

Running driverlesss directly as root results
# /usr/bin/driverless --debug
DEBUG: Started ippfind (PID 7668)
ERROR: ippfind (PID 7668) stopped with status 1!

but calling plain ippfind directly as root works and results
# /usr/bin/ippfind
ipp://linux-h9wr.local:631/printers/fr
ipp://linux-h9wr.local:631/printers/ps
ipp://linux-h9wr.local:631/printers/testq

fr ps and testq are some local queues for some (other) tests.
Unfortunately the driverless debug mode doesn't tell anything more
why ippfind failed so I guessed it fails because driverless calls ippfind
in a special way which fails so I tried some more debugging via
# /usr/bin/driverless --debug & sleep 0.2 ; ps -o pid,user,args -C ippfind | cat -n ; sleep 3
[1] 7820
DEBUG: Started ippfind (PID 7822)
     1    PID USER     COMMAND
     2   7822 root     ippfind -T 0 _ipps._tcp _ipp._tcp ! --txt printer-type --and ( --txt-pdl image/pwg-raster --or --txt-pdl application/PCLm --or --txt-pdl image/urf --or --txt-pdl application/pdf ) -x echo -en {service_scheme}?{service_name}?{service_domain}?  ;
ERROR: ippfind (PID 7822) stopped with status 1!
[1]+  Exit 1                  /usr/bin/driverless --debug

which shows how driverless calls ippfind
but of course that cannot show how ippfind fails
so I tried to run such an ippfind command directly
("man ippfind" doesn't tell anything about 'verbose' or 'debug')
# ippfind -T 0 _ipps._tcp _ipp._tcp --not --txt printer-type --and \( --txt-pdl image/pwg-raster --or --txt-pdl application/PCLm --or --txt-pdl image/urf --or --txt-pdl application/pdf \) -x echo -en '{service_scheme} {service_name} {service_domain}' \;
# echo $?
1

so I got exit code 1 from ippfind which seems to be not an actual error exit
because "man ippfind" reads
EXIT STATUS
ippfind returns 0 if the result for all processed expressions is true,
1 if the result of any processed expression is false,
2 if browsing or any query or resolution failed,
3 if an undefined option or invalid expression was specified, and
4 if it ran out  of  memory.

and I think when an expression result is false it basically means "not found"
but that is not an error of ippfind so perhaps in the end all is well
and the message
ERROR: ippfind (PID ...) stopped with status 1!

is only misleading false alarm and
when driverless runs ippfind its exit code 1 should be ignored
or considered as some special kind of "not found" success
in list_printers in utils/driverless.c ?

Hi Johannes,
please check my email on printing-architecture mailing list - Solomon got into the same situation and IMO it is an expected behavior, if the queues you found by ippfind are remote cups queues and my assumption about driverless are correct.
I wrote the email to get a verification from Till.

ERROR: ippfind (PID ...) stopped with status 1!

is only misleading false alarm and
when driverless runs ippfind its exit code 1 should be ignored
or considered as some special kind of "not found" success
in list_printers in utils/driverless.c ?

If you propose to remove this error message and just return '1' as an exit code, then I agree. If ippfind finds nothing, driverless shouldn't state it as an error.

Hello Zdenek
I think you mean
https://lists.linuxfoundation.org/pipermail/printing-architecture/2021/004047.html
I think this is something different.
My issue here is that I think when ippfind exits with exit code 1
it seems to be not an actual error (as far as I understand "man ippfind")
so ippfindexit code 1 should not be treated as an error so that
in particular driverless should not be stopped with status 1.
I think when ippfind exits with exit code 1 it behaves like
# echo foo | grep bar

# echo $?
1

where the caller of grep must decide if its exit code 1 means
an error for the caller or if "not found" is an expected successful outcome.

Aha, I'm sorry - I thought one of the part of the problem is that driverless returns nothing but ippfind finds queues.
Ad the actual problem - IMO the return value from ippfind should propagate into driverless - meaning ippfind returns 1 -> driverless returns 1.

https://bugzilla.redhat.com/show_bug.cgi?id=1954469#c2
reads (excerpt)
Dropping the '!' seems to make things work for me.  Not sure why it's there.

so I tried the above ippfind command without the --not
(and a bit different echo for better readability here):
# ippfind -T 0 _ipps._tcp _ipp._tcp --txt printer-type --and \( --txt-pdl image/pwg-raster --or --txt-pdl application/PCLm --or --txt-pdl image/urf --or --txt-pdl application/pdf \) -x echo '{service_scheme} {service_name} {service_domain}' \; ; echo $?
=ipps fr @ linux-h9wr local
=ipp fr @ linux-h9wr local
=ipps ps @ linux-h9wr local
=ipp ps @ linux-h9wr local
0

I guess the --not or ! is there to intentionally exclude such found IPP printers
from what driverless autodetects.

https://lists.linuxfoundation.org/pipermail/printing-architecture/2021/004048.html
explains it all
Thank you @tillkamppeter !

Fixed in commit 78b6b2c9 on master. Thanks for the bug report.
Now driverless exits with 0 if no suitable printer got found, according to CUPS standards.

@tillkamppeter just implementation question - can we do this just by assigning 0 after the getting exit status from ippfind, if the ippfind returns 1?
It will be only two lines change.

@zdohnal, I switched to your method now, as mine also interfered with some other error condition. Thank you very much.

Interesting to see that what looks on first glance like a
quick and dirty hack if (exit_status == 1) exit_status = 0;
is actually the simplest and most straightforward solution in this case.
@zdohnal @tillkamppeter thank you both for the proper fix!


refine CLI output when running incremental backups

kopia-assisted incrementals and incremental backups both change the number of files that are persisted to kopia. This can sometimes produce misleading output on the CLI with how we track file completions. For example, a backup using kopia-assisted incrementals will say that it only backed up two files if nothing else changed (the two files backed up are the metadata files Corso requires for delta token-based incrementals). Despite that, all items were actually checked and are preserved.
Similarly, delta token-based incrementals lead to lots of Action: Backup performed on 0 of 0 objects (0.00B) within 1 directories. Downloaded from Inbox in the debug log output since no items in the M365 folder were changed

closing as this seems to have been split into other issues


CI fails to tag releases

Problem
The CI job to tag releases fails with an error:
Run<EMAIL_ADDRESS>New version is 2.5.0.
New tag after applying prefix is 2.5.0.
Changelog is ## [2.5.0](https://github.com/matrix-org/matrix-rich-text-editor/compare/2.4.1...2.5.0) (2023-08-11)

.
Error: Not Found

Possible solution

Possibly related to https://github.com/mathieudutour/github-tag-action/issues/165
Replace the secrets.PAT variable with a token that has the right permissions.

If the default secrets.GITHUB_TOKEN is in permissive mode (i.e. has read/write) permissions then we may remove the config to use this.
If the default secrets.GITHUB_TOKEN is in restricted mode, then replace secrets.PAT with a new token with the correct permissions (repository write permissions).

cc @langleyd who I believe has access to manage Github secrets

Fixed in https://github.com/matrix-org/matrix-rich-text-editor/pull/779/commits/e1f16579284aca3857198056e8c55778f33c965d


Palworld save corruption after guild collectively catch/sell/butcher/drop/etc 7000 pals

Is your feature request related to a problem? Please describe.
Some Palworld server saves are being corrupted or the servers will constantly crash on start.
The current workaround is run fix_save.py using the code from this repo thanks to user HyperBCS
The instructions were posted on reddit

Simply drag Level.sav into fix_world.cmd or run the python script fix_save.py with the filename as the argument. If no --output argument was given, the file will be saved into a folder named "fixed". This script is largely untested so please make a backup and report any bugs.

Describe the solution you'd like
I propose automating this to run on container start as a current workaround until palworld resolves the bug. As this is largely untested it should be optional and save backups should be automatically inferred or warning in documentation that when enabling it is highly recommend to also automate backups as it may corrupt the save.
Describe alternatives you've considered
No alternatives currently known.
Additional context
No additional context

This was supposedly fixed in Palworld patch <IP_ADDRESS>
"・Implemented the first fix for an issue where the game would always crash and save data would be corrupted when the guild's total number of pals captured reached around 7000.
*The game no longer crashes even if the total number of captured objects exceeds 7000."

You are right, it was just fixed with the most recent patch that came out today. The save fix is only needed for servers that have had the issue happen to them as the patch will not repair already corrupted saves. Thank you PocketPair!