add skill to determine the relationship in family tree with reasoning

The skill enables determining the relationship in a family tree or blood relations with necessary reasoning
If your PR is related to a contribution to the taxonomy, please, fill
out the following questionnaire. If not, replace this whole text and the
following questionnaire with whatever information is applicable to your PR.
Describe the contribution to the taxonomy

The skill enables determining the relationship in a family tree or blood relations with necessary reasoning

Input given at the prompt

   ...

Response that was received

  ...

Response that is now received instead

  ...

Contribution checklist

[ ] Contribution was tested with lab generate
[ ] No errors or warnings were produced by lab generate
[ ] All commits are signed off (DCO)
[ ] The qna.yaml file was linted and prettified (yaml-validator can do both)

Thank you for your contribution to InstructLab! Unfortunately, once a Github repo is made public, all open PRs are automatically closed since they link against a private repo. We have detected that your PR might have been one of the ones affected by this change. If you are still interested in contributing your improvement, please fill out the following short form by no later than May 3rd, and we will get back to you with the additional steps necessary once we have had time to assess the PRs of those still interested:
https://forms.gle/V7SrPPMZDo6iGDYu8


Add *_i32 and *i64 for fixed sized chrono types

Useful if you only want an int, since the default is a long long.

Looks good.


Age Out Old Registry Content

We migrated forward all existing images since the beginning of hosting Kubernetes images, from gcr.io/google-containers to k8s.gcr.io to registry.k8s.io
We should consider establishing an intended retention policy for images hosted by registry.k8s.io, and communicating that early.
Not retaining all images indefinitely could help the container-image-promoter avoid dealing with an indefinitely growing set of images to synchronize and sign and may also have minor hosting cost benefits.
Even if we set a very lengthy period, we should probably consider not hosting content indefinitely.

Jeefy lizard brain policy idea:
Non-Prod images: Age out after 9 months
Prod images: Age out after release-EOL + 1y (so if 1.27 aged out Jan 2024, it would get culled Jan 2025)

I am broadly in support of this. I don't think its a reasonable ask for the project to host all releases for all time.
Do we have any data on which versions are being pulled?
I know there are 3rd party reports available (e.g. datadog report) that show 1.21 is still the most common version deployed right now, I would want to make sure we take that into account.
Right now I'm leaning towards EOL-6 (2 years) or EOL-9 (3 years), but would want some data before making any decision.

/sig testing
/kind cleanup

Some additional points:

We have a lot of images that are not related to Kubernetes releases, but may have their own release timelines. I think we should maybe just set an N year policy, where N is relatively generous but still gives us room to stop perma-hosting.

The mechanism to remove images needs some thinking ...

The source of truth on what images are available is in the k8s.io repo, and is https://github.com/kubernetes-sigs/promo-tools copying to the backing registries (so to be clear no changes will happen in this repo, it's a multi-repo problem and I figured visibility might be best here, but we need to forward this to more people).
We might have to cull them from the image promoter manifests somehow, and then start to permit auto-pruning things that are in production storage but not in the manifests. Automating the policy to drop things from the source manifests sounds tricky, but I'm not sure there's a more reasonable approach. The implementation details need input from promo-tools maintainers and will probably at least somewhat drive the viable policy. cc @puerco @kubernetes/release-engineering

EDIT: Even without data I think we should remove the google-containers images...oof

Yeah. That also just hasn't happened due to lack of policy. We did the flip to k8s.gcr.io July 24th 2020. https://github.com/kubernetes/release/issues/270#issuecomment-681175843

/sig testing

While I'm sure sig-testing is happy to support this effort, I'd suggest that the policy is a combination of k8s-infra (what is k8s-infra willing to fund resources for generally) and release (particularly around the promo tools support for this and kubernetes release timeframe).
/sig k8s-infra
/sig release
/remove-sig testing

/committee steering
as this has budget / cncf related items

Technical aside: when we serve layer redirects, we then get an option to serve a Warning header alongside the redirect.

One additional complication for people to consider: We more commonly host our own base images at this point, building old commits from source will become more challenging (but not necessarily impossible*) if we age out those images.

non-reproducible builds may be an issue, e.g. the "debian-base" image.

Posted this on the linked issue, but maybe it's better here:
The cost reduction would primarily be because we would break people, and encourage them to upgrade (?)
I think other OSS projects follow a similar strategy, e.g. the "normal" debian APT repos don't work with old releases, but there is a public archive.
I don't know the actual strategy for when debian distros move to the archive. For kubernetes, if we support 4 versions (?), we probably want to keep at least 5 versions "live" so that people aren't forced to upgrade all their EOL clusters at once, but we probably want to keep no more than 8 versions "live" so that people are nudged to upgrade. So I come up with a range of 5-8 releases if we wanted to split off old releases, and I can imagine a case for any of those values.

For kubernetes, if we support 4 versions (?), we probably want to keep at least 5 versions "live" so that people aren't forced to upgrade all their EOL clusters at once, but we probably want to keep no more than 8 versions "live" so that people are nudged to upgrade.

This is bringing up a very good point. We have to keep in mind that you can't skip Kubernetes versions when upgrading, otherwise you'll go against the skew policy and eventually break the cluster. Let's say that we remove images for up until 1.22, but someone is using 1.20. They don't have a way to upgrade their cluster to a newer version because they have to start with upgrading to 1.21 which wouldn't exist any longer. This is a very problematic scenario because the only way is more-or-less to start from scratch and that's unacceptable for many.
We need to be a bit generous here. I agree with @justinsb that we should target 5-8 release. I'd probably go closer to 8.

These are good points.
I think we should probably be implementing policy in terms of time though, both to be more managable to implement and because we have many images that are not part of Kubernetes releases.
If we consider the lifespan of releases but put it in terms of time we could say e.g. "3 years after publication" which would be 5-8 releases (since releases are every 1/3 year and supported for one year).

I think we should set a more aggressive timeline going forward, say starting with 1.27 we'll host artifacts for 1 year after things after they hit end of support.  I'm not sure how we best handle older things, but things like 1.21 are still being heavily used. If we said "5" releases, that would still fall into that window pretty soon.
If we have to chose between the health of the project overall (CI infra, etc) and impacting people with those older versions, I think we have to unfortunately chose the health of the project :(  Can we provide some extraordinary mechanisms for people to pull maybe tarballs of older stuff and some instructions on how to put those into a registry, like some sort of cold storage for folks?

💯 to say starting with 1.27 we'll host artifacts for 1 year after things after they hit end of support.

Can we provide some extraordinary mechanisms for people to pull maybe tarballs of older stuff and some instructions on how to put those into a registry, like some sort of cold storage for folks?

What if we keep the latest patch release for each minor? For example, 1 year after reaching the EOL date, we keep images for the latest patch release, but delete all other images. Eventually, we can remove the latest patch release, let's say, 3-4 years after the EOL date. That will reduce storage and (hopefully) bandwidth costs, but at the same time, it shouldn't break any clusters or workflows.

The source code will remain https://github.com/kubernetes/kubernetes/releases , is not that people can do make release

Technical capabilities aside, the ideal set would be, IMHO:

Everything for the last 4 releases
Just the final patch release for the 4 releases before that, just to enable upgrading

If we had the ability, I expect that there are probably lots of other images we could purge for older releases from subprojects, etc, which could be removed much more aggresively.

Thanks all for all the input and suggestions!

The source code will remain https://github.com/kubernetes/kubernetes/releases , is not that people that needs can not do make release ;)

That's not sufficient, because the base images cannot just be re-built from source typically, and the source code references base images. Those base images are a snapshot of various packages at a point in time.
We also run binary builds in containers sometimes (see kubernetes/kubernetes), where the build-environment image is also an important point-in-time snapshot for reproducing a source build.

We've been discussing this further in various forums, and on further review I think the cost angle is going to be near totally irrelevant once we have traffic off k8s.gcr.io onto registry.k8s.io.
Storage costs are not large enough to matter. Image storage de-dupes pretty well, it's compressed, in real numbers we're actually looking at less than 2 TB currently even after ~8 years. 2 TB costs like $50/mo to store in GCS standard tier for exxample.
Bandwidth costs matter, deeply, ... but only for content people actually use, and they're going to be a lot more manageable on registry.k8s.io (e.g. >50% of requests to k8s.gcr.io came from AWS, and we're now serving content out of AWS ... no egress).
For the tooling "needs to iterate all of this" angle, I've been working on a new tool that needs to scan all the images over the past few days, and it's actually quite doable to optimize this even as images grow. AR provides a cheap API to list all digests in a repo. I think we can teach the promoter tools to avoid repeatedly fetching content-addressable data we've already processed.

I think disappearing base images in particular is going to cause more harm than benefit ...
We're also really ramping up having users migrate, so I think we are missing the window on "lets get a policy in place before people use it", and it we've forced users to adapt to a new registry twice in the past few years, so I think we can just introduce a policy later if we wind up needing it.
@mrbobbytables outreach to subprojects and other CNCF projects to migrate, and other pending cost optimization efforts are probably a better use of time at the moment.

There are other issues tracking things like potentially sunsetting k8s.gcr.io, they're tracked in the general k8s-infra repo at https://github.com/kubernetes/k8s.io


doc: add note to twister documentation

It could be helpfull to have a note about running single testsuite,
and adding more runners to the note, that are supported in hardware map

I added changes in the same commit, if everything is fine, let's merge it.

I added changes in the same commit, if everything is fine, let's merge it.

Sure :) But I'd like @nashif to comment (he's the assignee anyway so will have to approve) on my comment regarding the fact that it sound wrong to me to only document -s option out of the blue, and not other useful options like -T, etc.
IMO it should be either we invite people to run the --help command to learn about all the options and don't duplicate that information in the documentation page, or we have information in the doc page that's effectively documenting all the available/useful options and not just a random one.

it sound wrong to me to only document -s option out of the blue, and not other useful options like -T, etc.

@kartben
that is not the case, many options are being documenting across this file. If some enhancements or overhaul needed, this would be a different PR.

DNM until revisted by @kartben

That being said, if Twister maintainer is happy, I'm happy :-D so please just go ahead remove the DNM tag if you feel like this can be addressed later.

@nashif Ping on the above


Fix typo in k-lib.mdx

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Fixing a small typo on quick help docs

When calling insert(_:at:) the returned index may be different than the requested index in case selected is false rather than true
Checklist

[X] I've read the Contribution Guidelines
[X] My contributions are licensed under the Swift license.
[ ] I've followed the coding style of the rest of the project. (No changes on code were made, only on the documentation)
[ ] I've added tests covering all new code paths my change adds to the project (if appropriate).
[ ] I've added benchmarks covering new functionality (if appropriate).
[X] I've verified that my change does not break any existing tests or introduce unexplained benchmark regressions.
[X] I've updated the documentation if necessary.

@swift-ci test


Upgrading nodejs to 12.22.1

Description
Upgrading nodejs to 12.22.1
Motivation and Context
Outdated versions might have security issues
Checklist:

[x] My pull request is properly named
[x] The changes respect the code style of the project ($ npm run lint)
[x] I tested/previewed my changes locally

@kytwb - I have also updated the appveyor.yml file to use this node version for testing purposes. FYI.

@vraravam thanks!


Bump mysql-server to version 8.0.36

This is an automatically generated Pull Request from the Cryogenics CI Bot.
I have detected a new version of mysql-8 and automatically bumped
this package to benefit from the latest changes.
If this does not look right, please reach out to the #mapbu-cryogenics team.

will be recreated to test ci


Add Contracts

closes #69

[ ] Add ulox script tests of contracts

Coverage decreased (-0.2%) to 92.87% when pulling 00afa2667f65f34fa98dd5aa0dcf3ccbf7b1ce24 on contracts into 143ea0b13d10a2184525c9b4ea95ec8a913a9ee7 on main.


[Suggestion]: Database in TxAdmin

It would be really useful if you could traverse the database within TxAdmin.
I'm happy to contribute if I can

ofcourse you can contribute! thats why its on github :)

which database? you mean the txadmin whitelist, bans and etc?


Can not edit issue description after creation

Gitea version (or commit ref): 1.3.0
Git version: 2.7.4
Operating system: Ubuntu 16.04 LTS
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:

Description
After an issue has been created, the issue description can not be edited ― regardless of whether there are texts in it or the description is empty. Clicking on the edit icon on the right opens the 'Write' box, and it can be written in. But after editing, neither the 'Save' nor the 'Cancel' button works. The 'Preview' button does not work either.
If page reload is attempted, no warning is displayed about unsaved changes. And if reloaded, the page returns to the 'view issue details' state.
Issue title can be edited, however. And issue can be assigned a label, a milestone, or an assignee. Only the description box does not work.
Screenshots

Could you reproduce that behaviour at try.gitea.io, since your version is no longer supported?

issue can't be reproduced at try.gitea.io.

@JonasFranzDEV
Do you reconmmend upgrading to the latest version (currently v1.4.2)?

@shortmotiv yes

Can confirm the bug is present on latest stable 1.4.3.
However, we figured out that this depends on your permission level. Admins can edit their issue comments while regular users are affected by this bug.

Can confirm the bug is present on latest stable 1.4.3.

This issue should be tagged as bug.

Ok, I looked a bit further:

it's possible to edit the comment via the API, the problem only occurs when using the web ui
I'm only affected when I'm not added as a collaborator

It appears that the error occurs when hitting the edit button.
In the released v1.5.0 I get a different error:
index.js?v=35c36e89ef751b74c7aa3b07d7e0f6b6:609 Uncaught ReferenceError: emojiTribute is not defined
    at HTMLAnchorElement.<anonymous> (index.js?v=35c36e89ef751b74c7aa3b07d7e0f6b6:609)
    at HTMLAnchorElement.dispatch (jquery.min.js:4)
    at HTMLAnchorElement.r.handle (jquery.min.js:4)
(anonymous) @ index.js?v=35c36e89ef751b74c7aa3b07d7e0f6b6:609
dispatch @ jquery.min.js:4
r.handle @ jquery.min.js:4

This is NOT a bug in v1.4.2

I have the "issuesTribute is not defined" error as well, when editing a comment on an issue, on gitea 1.6.0. I haven't customized anything. I don't think I even have a "custom" folder. I also had the same behavior on v1.4.2, though I haven't checked the javascript console output on that version.

Can you reproduce the bug at https://try.gitea.io: Gitea Version: fdec258

[x] Yes (https://try.gitea.io/gfPlay/orgRepo/issues/2#issuecomment-8810)
[ ] No
[ ] Not relevant

Description
same as @neuoy , and I test it for collaborator with admin, write, and read permission
the admin and write permission are fine.
the issue happened when read permission.
the collaborator can delete the comment but cannot edit the text.
this situation doesn't make sense.

I can confirm this is a bug, when a read permission user create an issue, then edit the issue will reproduce it.

@shortmotiv @coolaj86 @neuoy @gfwing please confirm #5516 fix your problem.

Sorry late, I just confirm my situation with

[ok] v1.6.0 + pr-5516
[ok] fdec258 + pr-5516
[ok] 0bd802e (I found it already merge to master after I test)

thank you.

Can confirm that it is fixed on current master release of Gitea Download section.


Not farming any plots on this harvester. Check your configuration.

i have this error in log on windows:
harvester spare.harvester.harvester: WARNING  Not farming any plots on this harvester. Check your configuration.
what i need to do?

please be sure to import your Chia plotting key to be able to farm on existing Chia plots

how?


IOpipe core as peer dep

Since this is a plugin and "should not" specify iopipe as a dependency, it should be moved to a peer dependency.
https://nodejs.org/en/blog/npm/peer-dependencies/

Yay! With @iopipe/iopipe available this makes more sense.


Curate initial phenology dataset

Get plant flowering dates across sites from phenology measurements dataset DP1.10055.001.

Initial curated phenology measurements dataset, across all sites and all dates, is in #12. This includes the script for curating the data, the resulting dataset, and an updated readme.
@dlebauer I don't know if you want to look this over?

looks great, thanks!

looks great, thanks!


Splitting parser_visitor.py

Follows this method:
https://stackoverflow.com/questions/47561840/python-how-can-i-separate-functions-of-class-into-multiple-files
One issue is that this requires adding an import statement in __init__.py every time a new function is added. This is because of a limitation in python, import * only allowed at module level.

Code was rewritten using multiple Inheritance.


Create virtual-machine-scale-sets-faq.yml

Added the below points at line number 478 to 482
Once the extension is updated to the scale set using below PowerShell/CLI cmd, upgrade the instances to update the username/password to VM instances.
Note:
-If Auto upgrade policy set for manual, user has to manually select the instance to perform an "upgrade" operation on individual VM instances.
-If auto upgrade set to Auto, it will automatically upgrade.

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


Brand

Find a name and get a domain

I like Bugle, but bugle.io is taken :(

Had another thought - maybe we can do octo-something? Dunno what the something is get though.


Expose liftReducer and/or liftState

Hey. I'm trying out the library and the first issue I've encountered is that some actions produce effects and others don't, which means my reducer returns inconsistent structures. I'd like to be able to normalize that for testing.
I see you've solved this problem internally with liftReducer / liftState. It'd be great to have access to those in my application/tests.
For my own sanity, I could see myself normalizing them upfront like this:
import { Effects, loop, liftReducer: liftReducerToLooper } from 'redux-loop';
// ...
export const reducer = liftReducerToLooper(createReducer({
  [FOO_ACTION]: (state, action) => {
    return {...state, foo: 'bar' };
  },
  [EFFECTING_ACTION]: (state, action) => {
     return loop(state, Effects.promise(someFn));
  },
}, initialState));

What do you think? I know there's always a tension between minimal surface area and convenience.

Actually, upon second glance, it looks like I actually want something more like compose(liftState, myReducer) since liftReducer changes the input as well as the output.

Sure, we can expose liftState. Do you want to submit a PR?

Included in v2.0.0!

thanks @lukewestby! sorry I didn't get around to a PR.


Issue with build cache

          Also found a similar problem with the build cache, if you want, I can create a separate ticket for this:

          1. Run `./gradlew clean`
          2. Run `./gradlew :feature:debugComposeCompilerCheck --build-cache`
          3. Run `./gradlew clean`
          4. Run `./gradlew :feature:debugComposeCompilerCheck --build-cache`

          Check will fail with `compose_reports not exists` error

Originally posted by @matejdro in https://github.com/j-roskopf/ComposeGuard/issues/41#issuecomment-2292851419

With the recent fixes from other reported issues, this issue is no longer occurring and is working as expected

Thanks for looking into it!
As mentioned on the commit comment, I think --rerun-tasks workaround is way overkill as it will forcefully invalidate whole project, completely negating the up to date checks and build cache. For example:

Start with a clean build folder (but with all outputs ready in config cache)
Run :feature:debugComposeCompilerCheck
Compile output for everything is loaded from build cache
Final debugComposeCompilerCheck runs
It detects that compose_reports is missing
It forces rerun of everything
Whole point of build cache is negated

A better workaround would probably be adding compose_reports folder as an output to the kotlin compile task, but as mentioned in the other task, this comes with a risk of kotlin tasks invalidating each other, so each compile task should have a different output folder.

Can you elaborate a bit more on each compile task having a different output folder? I'm following in theory, but not understanding how that translates to code. adding compose_reports folder as an output to the kotlin compile task makes sense to me, but each compile task having a different output folder doesn't. we are referring to another kotlin compile task like ksp right?

I published a 2.2.4-alpha with the kotlin task having the output directory of the check task added. I understand the risk of the other compile tasks like ksp being invalidated, but that seems like a fair tradeoff for the time being

Seems to be working. Thanks!


ec2 limit filters on account

while we do trusted advisor reported limits, with the service-limit filter on the account, there are a few that are specific to the ec2 describe account attributes method that we should expose as well for pro-active notification.

actually it does look like trusted advisor server-limit checks have this info but its seems dependent on support level.

i think we just need customization here on the extant service limit to handle the way instance limits get reported (per instance type counts, but reported against limit of all instances).


cmd/link: regression in big text fix for external linking on ppc64le

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version devel +04d7135 Fri Nov 4 14:09:52 2016 +0000 linux/ppc64le
What operating system and processor architecture are you using (go env)?
Ubuntu 16.04 ppc64le
What did you do?
Testing with Go 1.8, attempted to build and test hyperkube from Kubernetes on ppc64le with golang master.
What did you expect to see?
Successful build and run.
What did you see instead?
Successful build but execution failure:
unexpected fault address 0xed840
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x1 addr=0xed840 pc=0xed840]
goroutine 1 [running, locked to thread]:
runtime.throw(0x12d81cdf, 0x5)
/usr/local/go/src/runtime/panic.go:596 +0x7c fp=0xc420703eb8 sp=0xc420703e88
runtime.sigpanic()
/usr/local/go/src/runtime/signal_unix.go:276 +0x24c fp=0xc420703f18 sp=0xc420703eb8
main.init()
/root/kubernetes/_output/local/go/src/k8s.io/kubernetes/cmd/hyperkube/server.go:76 +0x70 fp=0xc420703f58 sp=0xc420703f38
runtime.main()
/usr/local/go/src/runtime/proc.go:173 +0x1b0 fp=0xc420703fc0 sp=0xc420703f58
runtime.goexit()
/usr/local/go/src/runtime/asm_ppc64x.s:1271 +0x4 fp=0xc420703fc0 sp=0xc420703fc0
goroutine 17 [syscall, locked to thread]:
runtime.goexit()
/usr/local/go/src/runtime/asm_ppc64x.s:1271 +0x4
goroutine 5 [chan receive]:
k8s.io/kubernetes/vendor/github.com/golang/glog.(*loggingT).flushDaemon(0x1601d740)
/root/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/golang/glog/glog.go:879 +0x64
created by k8s.io/kubernetes/vendor/github.com/golang/glog.init.1
/root/kubernetes/_output/local/go/src/k8s.io/kubernetes/vendor/github.com/golang/glog/glog.go:410 +0x1fc
[root@localhost kubernetes]#
I found this error was introduced in commit c7e8556.  I have a simple fix for it.

This is related to #15823 and #16665.  For ppc64 & ppc64le, trampolines are used to solve the too-far branch problem only for internal linking.  For external linking, the solution for ppc64le is to split the text sections and allow the external linker to handle the long calls.  External linking doesn't work for ppc64.


Error when adding a member to a hierarchy

When I click Add in Level Collection Editor, I get the following error:
"Constructor on type 'TabularEditor.TOMWrapper.Level' not found."

Thanks for reporting this. Could you try to add a level by dragging a column into the hierarchy instead? Alternatively, there should be an option for adding a column as a level in a hierarchy, if you right-click on the column.

Thanks, both these options works.
But now I can't remove a column from a hierarchy. It seems the only way is
throgh the Level Collection Editor?
And when i remove a column there, and click OK, I get the following error,
and then all columns are removed from the dialog window.
[image: Billede indsat i tekst 1]
2017-07-13 10:06 GMT+02:00 Daniel Otykier<EMAIL_ADDRESS>
Thanks for reporting this. Could you try to add a level by dragging a
column into the hierarchy instead? Alternatively, there should be an option
for adding a column as a level in a hierarchy, if you right-click on the
column.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/otykier/TabularEditor/issues/78#issuecomment-315003824,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AcvuhdU1fz5xOov08APfNZTMBXEFwpEVks5sNc_ygaJpZM4OWoGM
.

You should be able to remove a level from a hierarchy by simply deleting it in the tree. That is, select the level you want to remove and hit DEL or right-click and choose delete.
I think I enabled the Level Collection editor by mistake in the latest build. In previous builds, it wasn't available at all, but you could still get by using the tree. I'm not sure what benefits the collection editor has over directly adding/removing levels in the tree, so I might remove it again instead of fixing the current issues.

I don't get a right-click menu on a level in a hiearchy, and nothing
happens, when pressing DEL.
2017-07-13 11:07 GMT+02:00 Daniel Otykier<EMAIL_ADDRESS>
You should be able to remove a level from a hierarchy by simply deleting
it in the tree. That is, select the level you want to remove and hit DEL or
right-click and choose delete.
I think I enabled the Level Collection editor by mistake in the latest
build. In previous builds, it wasn't available at all, but you could still
get by using the tree. I'm not sure what benefits the collection editor has
over directly adding/removing levels in the tree, so I might remove it
again instead of fixing the current issues.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/otykier/TabularEditor/issues/78#issuecomment-315019082,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AcvuhdzSDF_qdFwvl0qk9rrwMv7XKRk0ks5sNd5IgaJpZM4OWoGM
.

That's also a bug in the latest release. Will provide a fix ASAP. In the meantime, you can use the following script to delete a level:
`Selected.Level.Delete();’
Run the script while the level you wish to delete is selected in the tree.

Issue fixed in release 2.5.
Feel free to reopen the issue if you're still having problems.


Updating to 2020.3 EAP downgrades poetry plugin

Describe the bug
After updating to 2020.3 EAP version 0.5 of the plugin disappears from the marketplace.
Interestingly enough, it appears that all features of 0.5 work. The package manger UI is filled correctly as is the virtualenv integration.
To Reproduce
Steps to reproduce the behavior:

Install plugin on 2020.2
Make version 0.5.0 a required plugin
Upgrade to 2020.3 EAP
See error "version 0.5 is required but 0.1.2 is installed"

Expected behavior
The correct version should be available
Screenshots

Environments (please complete the following information):

IDE: IntelliJ IIntelliJ IDEA 2020.3 EAP (Ultimate Edition), Build #IU-203.3645.34, built on September 21, 2020
OS: running in WSL (ArchLinux) on Windows 10
Poetry Version 1.0.10
Plugin version 0.5?

@thuringia
Thank you for creating this issue.
I have applied a fixed version to JetBrains Market.
They will approve the request in two business days.
I will post the information here when It's published.

@thuringia
version 0.5.1 is approved by JetBrains.
You can use the plugin on PyCharm 2020.3 EAP.


Installed @trivago/prettier-plugin-sort-imports; customized Prettier rules

Current dependencies on/for this PR:

main

PR #177   👈

PR #178

This comment was auto-generated by Graphite.


fix: I cannot expect a string with a dollar sign in it

Description
I cannot expect that a string with a dollar sign is visible or not.
Steps To Reproduce

Open a shell
Install the CLI via flutter pub global activate fluttium_cli (on Windows 11 if that matters)
Go to your flutter project in my case autologin/example (even not sure if that matters)
Run fluttium new flow foo
Use this three steps:- pressOn: "Enter sample data"
- expectVisible: "Some-Username"
- expectNotVisible: "Example-P@§$w0rd!"

Execute the flow/test via fluttium test .\foo.yaml

Expected Behavior
A passed test. Actual I get a compile error.
Screenshots
Temp/fluttium_b62c6914/lib/fluttium_test_runner.dart:24:60: Error: Undefined name 'w0rd'.
    UserFlowStep.fromJson({"expectNotVisible":"Example-P@§$w0rd!"}),
                                                           ^^^^
Failed to compile application.

Additional Context
It is cool that you can click on icons when they have a tooltip.

My current workaround is to use this \\u0024 as a replacement for the $. Very ugly but it works.

Is it possible because the text is converted to Regex? According to the docs, the string can also be regex and '$' is used in regex https://fluttium.dev/docs/actions/built-in/expectations

The compile error shows that the dollar sign is interpreted for embedding an variable.


#60: implement a serial semi unsorted search

also removed parallelunsorted search. It remains in git history if we want to fix it later
NOTE
I have not tested this with a dataset where there are both http and https results, so it would be good if reviewer could validate that this actually sort across http and https results or supply warc file(s) where this occurs

no more snake_case 🐍


support seletced multiple rows to export

My English is very poor, so I make a gif picture to show this feature:
http://oayueu6v6.bkt.clouddn.com/flask-admin-select-export-iloveimg-compressed.gif

Thanks for this!
I tried it out locally, but I don't think it's a great idea in general: At the moment, the behaviour we're looking for is that the user filter / search until they have only the records that they are interested in, and then they can export the list. I'm not sure there's a strong use-case for selecting only specific rows for export.


Adding cli options for Dask customization

[ ] I have added the tests to cover my changes.
[x] I have updated the documentation and CHANGELOG accordingly.
[x] I have read the CONTRIBUTING document.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.6 out of 7 committers have signed the CLA.:white_check_mark: venkatBala:white_check_mark: Emmanuel289:white_check_mark: Prasy12:white_check_mark: ruihao-li:white_check_mark: wjcunningham7:white_check_mark: cjao:x: CovalentOpsBotCovalentOpsBot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Hey @venkatBala @Emmanuel289 Any reason why the files in the webapp folders have been modified? I see a lot of front-end related files modified which might not be required.

Any reason why the files in the webapp folders have been modified? I see a lot of front-end related files modified which might not be required.

@Prasy12 I am not sure how those changes got included in this PR (this has been open for quite some time). I have updated this PR by syncing the webapp files to match the one in develop, so I think that should take care of that

@scottwn I've addressed your comments... this should be good to go

Resolves #616


Categorize table based on its type

Is your feature request related to a problem? Please describe.
In JDBC, TABLE_TYPE can be used to categorize tables. Typical types are "TABLE", "VIEW", "SYSTEM TABLE", "GLOBAL TEMPORARY", "LOCAL TEMPORARY", "ALIAS", "SYNONYM". I see DBeaver supports the first two, but can we support more? For example, in ClickHouse, there are also dictionaries and "remote" tables.
Database client like SQL Squirrels supports custom table types:

Describe the solution you'd like
Allow to customize table categorizes - could be somewhere in advanced configuration. Tables and views should be enough for most databases.
Describe alternatives you've considered
N/A
Additional context
N/A

Thank you for the future request!


Load legacy file formats to Spark SQL Dataframes

Spark SQL supports loading Parquet data into Dataframes natively. It'd be reasonable to add matching support for SAM/BAM, VCF, etc.

Punting to 0.21.0.

Closing in favor of #1018.


⚠ ClamAV has degraded performance

In fe9d1e0, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 428 ms

Resolved: ClamAV performance has improved in 0342937.


Swift 2.0

Would love to use this in my new Swift 2.0 application (:
But there are some bugs :/

Done
please use pod 'TisprCardStack', '~> 0.2.0beta1' to install version with swift 2.0


refactor twitter api with es6 syntax and async/await

Twit library natively supports promise. It is better to use the new syntax es6. This eliminates the need for callback.

Thank you :)

Related: https://github.com/sahat/hackathon-starter/issues/720


Renamed ExonCollection, use Locatable instead of SimpleInterval, and add two methods

@lbergelson this minor refactoring is needed for AllelicCapSeg in hellbender-protected.  @vruano if you disapprove of anything, let me know.

@davidbenjamin My review is complete.  Lots of tiny documentation issues.  I'd refactor that unit test with a data provider as well.

Back to you, @lbergelson

@lbergelson I did the stuff we talked about.  Now it's prettier.

@davidbenjamin Looks good!  :+1:  to merge when you're squashed and ready.

Let me know when you've merged and I'll release a new version.

I'm just going to superstitiously wait for travis before squash/merge.

@lbergelson Merged.


Disable analytics with localStorage item

Use localStorage to disable analytics instead of blocking URLs.
Based on the way it was done in the IQE test suite.
https://issues.redhat.com/browse/IQE-1594
https://github.com/RedHatInsights/insights-chrome/pull/1963

Changed it to use the more "correct" way.

I suggested the change, in order to remove the hundreds of line of actions in the trace generated by the route controller we have been using so far.
Since chrome - the consoledot app - has an official way for disabling the marketing files responsible for all the disruptive popups, we are trying to use that. This is the same approach the previous test framework used.

+1 on removing unused code by the way!

Created a Jira in RHCLOUD project for a proper way to disable any disruptive pendo pop-ups. https://issues.redhat.com/browse/RHCLOUD-24418 Without this implemented, we should not proceed with this PR. Some workaround could be implemented to detect and close such pop-ups.


Create token types for if, else-if, else and while

This will make it much easier to write lint-rules and will help with writing custom code-gen stages.

Thanks! This will also make the integration of halting-problem easier either in code-gen or parser.


update base64 md5 hex env_logger rand

Update base64 to 0.11.x, md5 to 0.7.x, hex to 0.4.x, env_logger to 0.7, rand to 0.7.x

It looks like the AppVeyor build hit the 1 hour limit

Hey @paolobarbolini thanks for the PR! Perhaps you can push another commit, like a merge in from master, to force another build. If that build fails again for the same reason, we can decide on how to proceed then.

It did it again.

Appveyor has been timing out often lately, it's probably time to band aid that until we land https://github.com/rusoto/rusoto/issues/1553 or something else.
If that's the only potential issue with this PR I think it's good to go! 👍

https://github.com/rusoto/rusoto/issues/1425 is related and is probably the short term change to make.

Integration test pass, looks good, thank you!


Analytics support

Hello. Thanks for this nice theme!
I have not found an easy way to load a custom script. My current workaround is to extend the default templates, but that's not really intuitive
I'm currently using Plausible if that matters, but I think a generic solution would be better
What do you think?

I think it is a good idea. I could have an empty template file to be included in which case your template file could override it and it's contents would get included in the head
We could also just use a config value in config.toml such as this:
head_extra = ''
Let me know what you think, or if you had any other ideas.

The config.toml option is probably the simplest

done: https://github.com/Jieiku/abridge/commit/dfa40127ea0471488a04fa6cf67c749d429dde46

That was fast, than you


Fix code block markup display in README

Coverage remained the same at 60.829% when pulling c94d1f9c7d9f1ea5c25736369b470144b57140b0 on DanielJohnBenton:patch-2 into 6a29449f72a8ab26a2434b2f929e42a1db75eaaa on DistrictDataLabs:master.

Thanks for providing the fix - we had it updated in the develop branch but haven't merged due to compatibility issues!


Add gettext dependency required for l10n.

r+

Coverage remained the same at 92.56% when pulling 25ed2209db96b33fee92d061518f497dae81270d on johngian:gettext-dockerfile into 865bc313e1a5b2a9bf00342c7b05b8cf9251c5ef on mozilla:master.


Change ' ShouldDelete*'  methods to invoke 'Func' only once.

Before this change 'ShouldDelete*' would call passed 'Func' once for every selection. With this change, it calls 'Func' only once for multiple selections.
Issue discussed :
https://github.com/Blazor-Diagrams/Blazor.Diagrams/issues/164

Please review this once you get time.

Hello. sorry for the late reply.
I'm just still thinking to see whether this approach is the best one, I have 2 worries right now:

Is this efficient? Creating 3 arrays (looping 3 times in your case too) might be too much
What if the user asks to delete 2 nodes, but you can only delete 1 of them. In your case, if you return false you wouldn't delete anything, is that the desired behavior?

What do you think?

I have made changes for the same. Removed multiple for loops . Please let me know can we do this way?

Is this solution will work for you?

Hi It will be great if you suggest something on this..

Hi sorry, I'm still thinking whether this is the best solution that we can do.

Please give your thoughts. So will make changes as required.


OAS 3.0 support?

Does this support OAS 3.0?

Hi! ... any plans for this?

@subeeshcbabu hi, are you still with us ?


Use ComposerFinder's useAutoloading method

Closes #659
This implementation is much simpler: now that we use kcs/class-finder and that it has autoloading enabled by default, the only thing left to do is provide an option to disable it if you need the "legacy" behaviour for whatever reason.
I've tested the new autoloading flow in our project and it's behaving exactly as expected.

@oprypkhantc Can't you just set your own customized Finder instance on the SchemaFactory, instead of us modifying it to support this edge case?
$finder = (new ComposerFinder)->useAutoloading(false);
$schemaFactory->setFinder($finder);

@oojacoboo This PR is mostly for backwards compatibility. Let me explain:
Up until now, graphqlite used include_once to load classes - both before the migration to kcs/class-finder and after. The most recent version of kcs/class-finder at the moment is 0.4.0, which still uses include_once by default, effectively meaning useAutoloading(false).
Now the author of the library pushed a commit to master changing the default to use autoloading instead, meaning once we upgrade to 0.5.0, the behaviour will change for all users of graphqlite. It also makes some tests in graphqlite fail.
With this PR, I've upgraded to dev-master (0.5.0 as soon as the release is out) and added an autoloading opt-out option for those who need to use the legacy include_once behaviour for whatever reason. I can remove this option of course and I'll gladly do so :)
We'll still need this PR to fix the tests and add a kcs/class-finder ^0.5.0 constraint though :)

@oprypkhantc yep - got it.
I think we remove this option in GraphQLite and update documentation on how to disable using something like the example code I provided above.

@oojacoboo Done :) Added a small section in the docs about autoloading. Also I'm not sure why docs generation fails on CI - it builds locally no problem 👀

Merged.


MINOR: [Docs][Python] Remove note about pyarrow.dataset being experimental

Rationale for this change
In practice pyarrow.dataset is quite stable and we have not been treating it as experimental. So after several years of existence, high time to remove the (misleading) "experimental" label

Better late than never! LGTM 👍


Add a server-tracked Delayed re-delivery method, rather than client-side re-consume logic

Is your feature request related to a problem? Please describe.
Scenarios
When the consumer gets a message, it selects one of its workers to process. It needs to do the following work.

It needs to tell Pulsar to redeliver the message after a timeout.
If the worker finishes the work within the timeout. It tell Pulsar to Ack the message and do not redeliver the message.
If the worker fails the work within the timeout, It tells Pulsar to redeliver the message immediately.

First Attempt
We use Pulsar AckTimeout feature. However, It does not meet our requirement because if the consumer crashes, the unacked messages will be redelivered immediately. What we expect is that the messagesNAckedWithDelayedDuration only be redelivered after the delayed time even if the consumer crashes.
Second Attempt
We use Pulsar ReCosume logic, but still cannot meet our requirement because every time we ReCosume a message, it actually generate a new message, when the worker finishes/fails the original message, it has no info about the new message.
We could do some workaround here, e.g. when the consumer dispatches the original message, it first ReConsume it, generating a new Message, then dispatches the new message to the worker. I have done some performance test on it, which is really poor.
Describe the solution you'd like
Solution
Just like DelayedPublish, Pulsar could offer DelayedNAck. When the message is DelayedNAcked, it won't be available until the delayed duration. But it could be Acked, NAcked.

I think you can take a look at PIP-58 and it already released at 2.6.0.

Hi @codelipenghui , thanks for your reply. I have tried ReconsumeLater feature, but it does not meet our requirements, like I said in my original post,

Second Attempt
We use Pulsar ReCosume logic, but still cannot meet our requirement because every time we ReCosume a message, it actually generate a new message, when the worker finishes/fails the original message, it has no info about the new message.
We could do some workaround here, e.g. when the consumer dispatches the original message, it first ReConsume it, generating a new Message, then dispatches the new message to the worker. I have done some performance test on it, which is really poor.

Closed as stale. Please create a new issue if it's still relevant to the maintained versions.


Add a lint GitHub action that runs on a pull request and pushes to the main branch

Describe the feature you would like to see added
Adding a lint GitHub action that runs on a pull request and pushes to the main branch could help ensure the quality and consistency of your code.
Is your feature request related to a problem?
No response
Describe the solution you'd like
My work: https://github.com/OmerFI/monorepo/commit/90f883e5a3a742ddc4fdfce97497cdfa2588a6c4
Describe alternatives you have considered
No response
Additional context
No response

@OmerFI Thank you so much for starting this discussion. I'd like all of us in the same page when we are introducing a crucial infra like this.
So can we first talk about this here:

what steps we are going to introduce to the pipeline?
links to some sort of documentation for each step.
Also why we are introducing each step, what problem does it solve?


Carousel: fix z-index bug

Inactive carousel items' z-index are all 0
this result some items may incorrectly covering the previous active item during the transition.
In the example below the third item e.g. translateX(255) sometimes covering the first item e.g. translateX(-255) during the transition when the second item is active.
https://jsfiddle.net/po0utg8n/1/

Thanks for contributing. This is actually fixed in #6394


How can I make this component to start resizing upwards after resizing downwards to a certain height on screen?

Hi, please i'd like to make this textarea to resize downwards up to a certain point, and then start resizing upwards, so that the cursor never gets hidden from the viewport. Any idea how I can do this. I want the cursor to be a like about 100px from the bottom of the viewport and never go below.
My textarea starts with the following height. Resulting from a minRows of 5.

thanks in advance.

You could try manipulating maxRows - nothing will be added to the core of this component to support this, so if you want to use then you will have to just use what's already available.


Test ImuTracker

Adds unit tests for ImuTracker to cover filtering of the gravity
vector and tracking angular velocity.

Done with the corrections, PTAL.

@wally-the-cartographer merge

Merge requested by authorized user gaschler. Merge queue now has a length of 1.


[question] Structure of parent/child relationship

This is a general architecture when using Reflux to store collections of data. In Backbone, one has Collection and Model which makes structuring listing/detail views relatively straightforward.
I'm searching for good way to accomplish the same in reflux. I'm wondering if there is a standard idiom for this that others are using. Specifically I'm interested in how this works along side a router like react-router.
I can think of a few ways to do it:

Have a ProductsStore and then a ProductStore that fetches a given project via API/WebSockets/whatever.
Add a method to ProductsStore to return a single product.
Something else I'm not thinking of...

Maybe some can shed light on how you architect a parent/child relationship with Reflux?

this post might help you (as it helped me) structure your stores.
Basically, you should not duplicate data informations, and use one "singleton" data store (for each type of data you have) and several "selection/idList" store, even for one entity, which listen to the data store (in case the entity is deleted or else).
Also I tends to think my selectStore as per features, for example I have a feature "paginated list of object" and a feature "details of one object" ; therefore, I will have one dataStore which will store all my objects data, one selectStore which will hold the ids currently displayed in the list (+ the current page, ...) & one "detailsStore" which will hold the id of the object displayed on my details page (+ eventual other states of this page).
As per the way to populate components with the actual data, I use a dataStore.getAll() & a dataStore.getOne(id) methods when I receive the id (or ids) from the selectStores.
Since the selectStore is not allowed to hold a not existing id (since it listen to dataStore), it works well. But i'm sure the process could use some improvements.

Thanks @Cethy, this is helpful. I'll play around with that example code and find a way to integrate the concepts into my project.

Also I tends to think my selectStore as per features, for example I have a feature "paginated list of object" and a feature "details of one object" ; therefore, I will have one dataStore which will store all my objects data, one selectStore which will hold the ids currently displayed in the list (+ the current page, ...) & one "detailsStore" which will hold the id of the object displayed on my details page (+ eventual other states of this page).

Why make a store to keep id, when that id should be in URL either it's REST or non REST?

@ivan-kleshnin id in URL is an "app design" choice IMHO.
When I say "page", it's a wide term for an actual page, a panel, a popup or whatever you choose to display the details.
Also, I failed to mention that I don't use component state in stand-alone (always linked to a store), in order to get my app back exactly how I left it. This way, even a hide/show panel in the "details page" must be tracked in a store. And it's not the role of the listStore.
Does it answer your question ?

@Cethy thanks, it's clear answer and agree with your point.

Like this discussion. Anyone care to post a really simple hello world example with a list/detail view of a collection of objects?
Also, when directly viewing a detail page, does the page set the current ID in the detailStore and then calls a function on the listStore to actually fetch the item from the API? How does the detailStore know when to update? Is it getting info about the item from the listStore? How does it know when the details change for the item?
Dana Woodman • danawoodman.com
On Tue, Jan 27, 2015 at 4:45 AM, Ivan Kleshnin<EMAIL_ADDRESS>wrote:

@Cethy thanks, it's clear answer and agree with your point.
Reply to this email directly or view it on GitHub:
https://github.com/spoike/refluxjs/issues/198#issuecomment-71642271

I'll try to spawn a simple app using this architecture, as it's kinda obscure and I would love to have feedback from more senior (reflux) devs.

How does the detailStore know when to update? Is it getting info about the item from the listStore? How does it know when the details change for the item?

To be sure we're talking about the same thing, when you say listStore, you mean dataStore, right ?
In this case, as I said in my first comment, your detailsStore should listen to dataStore, and trigger a new state (with basically the same info, we don't care) to force the detailsComponent to update the data it displays via dataStore.getOne(id).
You could set detailsComponentto listen directly to dataStorebut it might disrupt some actions detailsStore could do before triggering the updated data.

Also, when directly viewing a detail page, does the page set the current ID in the detailStore and then calls a function on the listStore to actually fetch the item from the API?

I didn't think about that, since my apps are always "one-page apps" and there is some kind of initialization going on behind the scene loading the dataStore.
IMHO, if you just display a detailsPage and don't want to ask the API for the all collection, you should initialize an empty dataStore and add a failsafe in the dataStore.getOne(id) method which will ask the API if its collection is not initialized.

In order to clean up the issue tracker I have to close down all questions. Please use proper communications channels for questions about reflux, such as:

StackOverflow with the refluxjs tag
#reflux channel on Reactiflux Slack group. Sign up here for an account.


Buttons not using styles font for alignment of text

Noticed that buttons don't align text properly when using non default styles.
potential fix :diff
noticed when i had a singularly large button with center alignment and font size 64

I've noticed that 'comp:setAlign("center")' throws it off as well, but sometimes using 'component.align = "center"' or just calling center in 'gooi.newButton({align = "center"})' agruments works. Sometimes... Not always

The issue about the buttons not  fitting the text is now fixed in version 0.0.2, I was unable to reproduce the second issue about the text alignment, I small snippet reproducing the issue may help me.
I had to make some decisions about how the buttons react to changes in the font size, take a look at this example (and run it if you have a change):
require "gooi"

function love.load()
	gr = love.graphics
	kb = love.keyboard
	mo = love.mouse

	bigFont = gr.newFont(18)

	btn1 = gooi.newButton("gooi.alert()"):onRelease(function()
		gooi.alert("alert!");
	end)

	btn2 = gooi.newButton("gooi.confirm()"):onRelease(function()
		gooi.confirm("Choose", function()
			gooi.alert("You clicked yes! :)");
		end, function()
			gooi.confirm("Are you sure? :(", function()
				gooi.alert("I'M CRYIIIIING")
			end, function()
				gooi.alert("Good, I have a chance :)")
			end)
		end)
	end)

	btn3 = gooi.newButton("button 3")

	joyGame = gooi.newJoy()
	btnShoot = gooi.newButton("Shoot")
	lblLife = gooi.newLabel("Life:")
	lblLife.w = 60
	barLife = gooi.newBar(0.9)

	gridPanel = gooi.newPanel(320, 140, 450, 100, "grid 3x3"):add(btn1, btn2):add(btn3, "3,2")
	gamePanel = gooi.newPanel(320, 260, 350, 250, "game")
	gamePanel:add(joyGame, "b-l")
	gamePanel:add(btnShoot, "b-r")
	gamePanel:add(lblLife, "t-l")
	gamePanel:add(barLife, "t-l")

	comps = {
		gooi.newLabel("this is a label", 10, 10):setOpaque(true),
		gooi.newButton("Tooltip button", 10, 60, 300, 20):setTooltip("this is a tooltip"),
		gooi.newSlider(.75, 10, 110),
		gooi.newCheck("this is a check box", 10, 160),
		gooi.newRadio("this is a radio", "rg1", 10, 210),
		gooi.newText("this is a text box", 10, 260),
		gooi.newBar(.7, 10, 310),
		gooi.newSpinner(0, 200000, 150, 10, 360),
		gooi.newJoy(10, 410),
		gooi.newKnob(.9, 320, 10),
		gridPanel,
		btn1,
		btn2,
		btn3,
		gooi.newButton("Change style", 320, 520):onRelease(function()
			for i = 1, #comps do
				comps[i]:setStyle({
					font = bigFont,
					bgColor = "#FF8800AA"
				})
			end
		end):bg("#00FF0088"),
		joyGame,
		btnShoot,
		lblLife,
		barLife,
	}

	-- This enables tooltips and make dialogs smaller:
	gooi.desktopMode()
end
function love.update(dt)
	gooi.update(dt)
end
function love.draw()
	gr.rectangle("line", gridPanel.x, gridPanel.y, gridPanel.w, gridPanel.h)
	gr.rectangle("line", gamePanel.x, gamePanel.y, gamePanel.w, gamePanel.h)

	gooi.draw()
	gr.print("FPS: "..love.timer.getFPS())
end

function love.mousereleased(x, y, button) gooi.released() end
function love.mousepressed(x, y, button)  gooi.pressed() end

function love.textinput(text)
	gooi.textinput(text)
end
function love.keypressed(key)
	gooi.keypressed(key)
	if key == "escape" then
		quit()
	end
end

function quit()
	love.event.quit()
end

Before pressing "Change style":

After:

Note:

Components inside a panel don't change their proportions
Free components with no text attribute (Joysticks, Progress bars, etc.) keep their bounds too
Only free elements with a text component react to font size changes


TypeError: object of type 'NoneType' has no len()

Hello,
I tend to run into this error at "spacy_lookup_init_.py" line 60,
doc.ents = list(doc.ents) + [entity]
Looks like line 58 and line 60 is incorrectly indented. It should be inside of "if entity:"
Please check if this is the case. I can get around the error by indenting the two lines.
Thanks,
Agnes

This should be solved in the latest release. Thanks!


No mention of struct serialization?

Type of issue
Missing information
Description
Since struct serialization wasn't always supported, it would be nice to officially state that it now is, e.g. in the Serialization behavior section.
Page URL
https://learn.microsoft.com/en-us/dotnet/standard/serialization/system-text-json/how-to
Content source URL
https://github.com/dotnet/docs/blob/main/docs/standard/serialization/system-text-json/how-to.md
Document Version Independent Id
002f9f2a-48d1-0671-a079-b99b9f6bab58
Article author
@gewarren
Metadata

ID: 588ae32f-3429-143f-824c-5ab2d046d24a
Service: dotnet-fundamentals

Related Issues

Adding an (tiny) example with a struct could also be worth considering.

@eiriktsarpalis Can you weigh in?

We have a supported collection types article already but not a general "supported types". Perhaps it makes sense to generalize it and include explicit mention of all supported kinds, roughly:
Serializing as JSON objects
The following types serialize as JSON objects unless they implement IEnumerable<T>

Classes
Structs
Interfaces
Records and struct records

Serializing as JSON arrays
(insert existing content about collection types)
Unupported types

System.Type and System.Reflection.MemberInfo
ReadOnlySpan<T> , Span<T> and ref structs in general
Delegate types
IntPtr and UIntPtr.


Opening a video in the viewer crashes the app

Describe the bug
When I tap the thumbnail of a video file to open it in the viewer, the app crashes.
This happened with all video files I tried. Viewing images works as expected. Reinstalling the app didn't fixed the issue.
Screenshots
https://github.com/deckerst/aves/assets/41990490/1330ffb1-c54c-4608-8193-b4648386052c
System information and logs:
Package: deckers.thibault.aves.libre
Installer: dev.imranr.obtainium
Aves version: 1.9.0-libre, build 10102
Flutter: stable 3.13.0
Android version: 13, API 33 (GrapheneOS)
Android build: TQ3A.230805.001.2023080800
Device: Google Pixel 7a
Geocoder: not available
Mobile services: not available
System locales: en_US
Storage volumes: /storage/emulated/0/
Storage grants:
Error reporting: false
aves-logs-20230821_222848.txt

Thanks for the report.
For this release I switched to a different video engine (media_kit using mpv using ffmpeg). I'd be curious to know whether the test app of that video package works on your device. Would you know how to build and run the test app in https://github.com/media-kit/media-kit/ ? Otherwise I'll try and package it for you, but maybe later.

Here they are:

media_kit_test_arm64-v8a-release_20230821_2330.apk
media_kit_test_debug_20230821_2330.apk

Please let me know if you can play videos with these packages.

I have almost no experience with building Android apps, so the package would be better for me, but if this is a problem, I can try to build it myself.
Nevertheless, I'll be happy to help!
On August 21, 2023 11:00:14 PM GMT+02:00, Thibault Deckers @.***> wrote:

Thanks for the report.
For this release I switched to a different video engine (media_kit using mpv using ffmpeg). I'd be curious to know whether the test app of that video package works on your device. Would you know how to build and run the test app in https://github.com/media-kit/media-kit/ ? Otherwise I'll try and package it for you, but maybe later.
--
Reply to this email directly or view it on GitHub:
https://github.com/deckerst/aves/issues/722#issuecomment-1687036040
You are receiving this because you authored the thread.
Message ID: @.***>

Thank you. Yes, I can play all the videos from the app and some mine as well (the ones that caused Aves to crash).

Do you mind trying the play version of Aves v1.9.0 (also in the GitHub release), enabling anonymous error reporting and making it crash a couple of times? Of course, if it doesn't crash with that flavour I'm interested too ^^
By the way, do you use some special settings with your GrapheneOS, like hardened malloc?

(Probably) the same results as @Zumux on my device.
Tried the play version with anonymous error reporting enabled, and the app still crashes.
Enabling "Exploit protection compatibility mode - Improve compatibility with misbehaving apps by using Android's standard address space size and memory allocator" (this is an app-specific setting) fixes the issue on the both play and libre versions; disabling the setting causes the app to crash again.

Thanks, I'll take a look at the reports. But this hardened malloc thing is esoteric to me. Last time there was a problem with it, it was because of the bundled shaders. This time i don't know, and the only way for me to hold since this issue is to ask you to try various builds that i will need to prepare.
@Zumux just to be sure, you use Graphene OS too?

I get that, I have no idea if there is any convenient way to debug this. Nevertheless, I'll be happy to help you test those builds.

First batch of APK to try:

aves-arm64-v8a-libre-release_flutter3.13.0_ijk-control_ff-meta_20230822_1900.apk
aves-arm64-v8a-libre-release_flutter3.13.0_ijk-control_ijk-meta_20230822_1900.apk
aves-arm64-v8a-libre-release_flutter3.13.0_mpv-control_ijk-meta_20230822_1900.apk

All these are based on Aves 1.9.0, libre flavour, but with different libraries for video playback and video metadata analysis. Please let me know if any of these work for you.

The plot thickens... So media_kit (used in 3. and the regular release) is problematic, but you reported earlier that the test app of media_kit works fine. I need to find out what differs.

The same results as @Zumux on my device.

And enabling the Exploit protection compatibility mode fixes the issue again.

Thanks for the precision. I expect this as the hardened malloc setting is obviously one piece of this crash puzzle. The other is related to media_kit, but I don't know how yet.

I have experienced this issue as well. This issue was not apparent in the previous versions. Ia there any fis to this?

@Zumux I tried doing that, every single time I try installing it would would say that the application is on my device despite having uninstalled it on all my profiles. Do you have any way this can be circumvented?

Hi, I am also on grapheneos and experience same bug since the last 2 releases.
Thank you again for this great tool and good job

A couple of APKs as a baseline for later experiments:

media_kit_test_arm64-v8a-profile_20230902_1900_same_dep
aves-arm64-v8a-libre-profile_issue722_20230902_2030

The 2 use the same underlying video library package versions.
In the media_kit_test app, please try the first tab, then the button at the bottom to load a local video.
In the Aves app, there will only be 2 buttons, to load a local video in 2 different ways.
Please let me know whether media_kit_test still works without crash, and whether both ways to load in Aves make the app crash.

Google wants me to sign in and request access to download the media_kit_test app... is this intentional?
Downloading the Aves app doesn't require this.

As for the Aves app, I have the same results as @matchboxbananasynergy on my device.

Google wants me to sign in and request access to download the media_kit_test app... is this intentional?

No, my mistake. Should be fixed now. You can retry that link.

What is interesting is that enabling exploit protection compatibility mode and thus disabling hardened_malloc for that app doesn't change anything. SAF URI still crashes, cache copy doesn't.

Haha, it makes no sense >.<
Thanks for the feedback. I'll double check but on my device the SAF URI was working fine.

Thanks. Loading and playing a local video file in the  media_kit_test app still works without crashing.

I don't have a physical device with Android 13, but I've just tried on an emulator and it worked fine with the SAF URI. I used an x84_64 build to match the emulator architecture, not the arm64-v8a provided here for you, but it shouldn't matter if it was related to bad permission/API/logic. So the plot thickens.

Since this particular issue with SAF URI isn't fixed with exploit protection compatibility mode, it might be a separate issue and not related to the issue being raised here.

Right. I'll add some log export button to the build so we can hopefully see what's going on.

@matchboxbananasynergy could you please give this one a try, playing a video via SAF with and without exploit protection compatibility mode?
aves-arm64-v8a-libre-profile_issue722_20230903_1900
And if you get a crash, please relaunch the app, save the logs, and attach them here.

Thanks for the logs. Once again I see that things are not the same on the Android 13 emulator and on GrapheneOS. Here it's the kind of media URI that are returned by the picker.
Anyway, I can't possibly know what will or won't work on your custom devices, so here goes another try:
aves-arm64-v8a-libre-profile_issue722_20230904_2030
Please enable the exploit protection compatibility mode and try to load a video. If it crashes, please save the logs. If it doesn't crash, you can try again with the compatibility mode disabled.

It crashed with compatibility mode on
https://paste.hackliberty.org/?9593ab1a03bad375#AYBS4igHL2xySSVngcXfrCtG89BG9j7qNJeUnVgA2fRb

Can you try to open a content:// URI inside media_kit_test?
You can copy content:// URI from "Info" of a video in Aves.

@alexmercerind I downloaded 1.17 from your repo. Playing a video works without compatibility mode on. However, giving it a content uri in the "Video URI" field just load indefinitely

Hi @Welteam!
Thanks for trying out.
There's a possibility that you accidentally added a white-space while copying after the URI (I will recommend pressing a backspace for confirmation in the text-field).

(EPCM means Exploit protection compatibility mode; P&V means Photos & videos)
For some reason, my results are different in one case: Even with EPCM on and with P&V permission, the app crashes when I try to open a video file via URI.
Complete results:

EPCM off, without P&V permission:

file picker: OK
URI: loads indefinitely

EPCM off, with P&V permission:

file picker: OK
URI: crashes

EPCM on, without P&V permission:

file picker: OK
URI: loads indefinitely

EPCM on, with P&V permission:

file picker: OK
URI: crashes

I also made sure that that invisible character is removed.
I downloaded the media_kit_test app from the URL in the comment https://github.com/deckerst/aves/issues/722#issuecomment-1703940807 (I'm not sure which version is that)

I confirm, when using the app from the link @Zumux provided (version 1.1.7), opening a video via URI with EPCM and P&V permission enabled plays the video without the app crashing.

Thanks everybody for the feedback.
The media_kit_test build I provided in the comment above was built in the following way:

split APK (in this thread I just linked the APK for arm64-v8a)
profile mode (by opposition to a release build)
the following media_kit subpackage versions:

media_kit: 1.1.7
media_kit_libs_android_video: 1.3.3
media_kit_native_event_loop: 1.0.7
media_kit_video: 1.1.8

For me it's important that it was built that way so I could compare with the builds of Aves I provide to investigate the bug. The libre flavour of Aves is also released via split APKs.
The official media_kit_test v1.1.7 seems to use the same subpackage versions, so maybe the fact that it is a fat APK built in release mode makes the difference.

@sykoram
It is clear that normal playback through file-picker (file:// URI) is working fine.
I'm curious about these two cases:

The content:// URI plays/crashes if:

READ_MEDIA_IMAGES & READ_MEDIA_VIDEO are provided.
EPCM is disabled.

The content:// URI should playes/crashes if:

READ_MEDIA_IMAGES & READ_MEDIA_VIDEO are provided.
EPCM is enabled.

In your comment #1 you state that there is crash in both cases. In your comment #2 you state that there is no crash in both cases. I need a bit clarity about this (probably my English isn't good).
This is the part of my code, where I convert content:// URI to a file-descriptor. Is there something wrong here?
These logs from @Welteam show the debug log "media_kit: result = %d" at L147 (refer to code above). It means everything is correct till that point (at least; so there's that). Whenever JNI code crashes, Android logcat shows ART/Dalvik getting angry & giving information about shared library that caused it. I don't see it here.

Turns out I did copy a space causing the infinite loading. Without it, I get a crash with/without EPCM on deckerst's media_kit_test and a crash only with EPCM on the official media_kit_test
GrapheneOS also has a "Native debugging" setting which can crash app when disabled and the app does some weird stuff. I thought this may be the cause of the crash in deckerst's version but I still get the crash with it enabled

@alexmercerind the reason why the results are different is because he tested two builds of the app. The results I describe in point 1 match his results

Variants of the media_kit_test app (split/fat APK, profile/release):

media-kit-test_arm64-v8a-profile_deckerst_20230910_2330
media-kit-test_arm64-v8a-release_deckerst_20230910_2330
media-kit-test_profile_deckerst_20230910_2330
media-kit-test_release_deckerst_20230910_2330

Interested to know which of these builds, if any, can open a local media content:// URI without crashing, with the compatibility mode enabled.

For some reason the profile builds I was providing were not appropriate, which messed my initial investigation. But now it's clear that there is an issue for GrapheneOS users who open a SAF URI with media_ kit, even with the official media_kit_test app. It's not specific to Aves usage.
@alexmercerind do you want me to create an issue on your repo regarding this? I don't have the appropriate testing environment myself, but you can see there are many nice folks here willing to help debugging this.

@alexmercerind if providing an emulator build of GOS can help, I can look into doing that

As you can see from the discussion above, fixing this issue is not up to me but to the maintainer of media_kit. Feel free to file an issue and make your case there that this is important.

@deckerst i will open an issue in the mediakit repo if someone hasn't already done it. Before that I would like to confirm with you what we found in this thread.

there was an issue with the "profile_deckerst" apks causing a crash
this issue is not present in "release_deckerst" apks and is irrelevant to both mediakit and aves
mediakit, aves and the "release_deckerst" test apks crash (only) when used with hardened_malloc
the issue is present in the code path "opening a video from SAF URI" (and only when opening a video this way?)

Is there any relevant information you think I should put in the issue?

All correct, as i understand it. The maintainer of that repo is aware of the issue (he also reacted to the comments above) so he already knows the context.

I have this issue as well, but today it only seems to affect the libre app version on GrapheneOS. The standard app, from F-Droid, plays videos just fine.

May someone please try the version of media_kit_test from this branch:

Download (scroll down & locate "media_kit_test_android-arm64-v8a"):

https://github.com/media-kit/media-kit/actions/runs/6524527786

Allow photos & videos permissions from settings.
Open content:// URI.
Crash ???

Also, does opening a video from system file explorer in mpv-android work on GrapheneOS?
https://github.com/mpv-android/mpv-android/releases/tag/2023-08-27

Doesn't for me, no. I get an "Oops!" error within the app itself, and then it crashes.
Oct 15, 2023, 9:43 a.m. by @.***:

Also, does opening a video from system file explorer in mpv-android work on GrapheneOS?
https://github.com/mpv-android/mpv-android/releases/tag/2023-08-27
—
Reply to this email directly, > view it on GitHub https://github.com/deckerst/aves/issues/722#issuecomment-1763428342> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/AX3YBNKNTKNOM5PVHQRBZ3TX7QABHAVCNFSM6AAAAAA3Y5TW7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRTGQZDQMZUGI> .
You are receiving this because you commented.> Message ID: > <deckerst/aves/issues/722/1763428342> @> github> .> com>

Not sure how that would look like.

May someone please try the version of media_kit_test from this branch:

Download (scroll down & locate "media_kit_test_android-arm64-v8a"):

https://github.com/media-kit/media-kit/actions/runs/6524527786

Allow photos & videos permissions from settings.

Open content:// URI.

Crash ???

NOTE: DO NOT FORGET TO REMOVE THAT TRAILING WHITESPACE.

Yes, it crashes.
But with Exploit protection compatibility mode enabled, the video plays successfully.

Also, does opening a video from system file explorer in mpv-android work on GrapheneOS?
https://github.com/mpv-android/mpv-android/releases/tag/2023-08-27

I'm not sure what do you mean by system file explorer.
There are 3 options in the app:

Open document tree, where you select a folder (not file!) to use and you can than display all images and play videos from this folder (the files are listed in the app, not in the system file picker). This all works even without Exploit protection compatibility mode enabled.

Open URL, where you paste an URL to a file. This works (videos play) even without Exploit protection compatibility mode enabled! (The media_kit app crashes in this scenario.)

File picker (legacy), where you can browse the internal storage (in the app, not in the system file picker -- like in the first option). This works fine just like the first option.

But I don't think there is a option to use the system file picker to pick just one file.

Hi @sykoram,
Thanks a lot for testing out & detailed response. I will try to locate something else.

But I don't think there is a option to use the system file picker to pick just one file.

I was referring to some "Open with" option like this:

Regardless, your existing reply is helpful.
Thanks!

@sykoram
Just so that I don't waste my time in this direction:

Open URL, where you paste an URL to a file. This works (videos play) even without Exploit protection compatibility mode enabled!

You entered a content:// URI right?

@alexmercerind No, MPV Android doesn't crash when opening a file from the system file explorer

I think I figured it out:
Scroll down & locate "media_kit_test_android-arm64-v8a":

https://github.com/media-kit/media-kit/actions/runs/6526549498

I hope content:// URI works in this build.
Thanks!

A confirmation from someone will still be helpful because I'm not 100% sure. I'll publish an update afterwards.
Yeah, hardened_malloc has really helped here.

Yes, I confirm that opening a video via URI (with Pictures&Videos permission) works even without Exploit protection compatibility mode enabled!
Good job figuring it out!

I have published a new version of package:media_kit with the fix. Thanks a lot everyone for your valuable time, reports, tests & feedback. We've solved an issue that could cause issue for many people.
Thanks again!

cc: @deckerst

Congratulations, @alexmercerind!
Just to be sure there's no remaining issue with Aves itself, could someone give this build a try?
aves-arm64-v8a-libre-release_20231016_2330.apk

Nice. Thanks again to everyone who helped debug this. Open-source :heart:

@deckerst thank you!
Does that mean we can update the application on the play store and it would work?

@Striker789 yes, the new play store version no longer crashes

Published on Accrescent now, other channels soon™.


Show Menu When Right Clicking On Transaction - Option causing crashing of YNAB

Name of Defective Feature
Show Menu When Right Clicking On Transaction
System Settings (Required)
ToolKit Version:  1.1.0
Operating System (Mac/Windows/Etc): Windows
Browser (Chrome/Firefox/Safari): Chrome
Browser Version: Version 60.0.3112.113 (Official Build) (32-bit)
Other Extensions: LassPass, ieTab, Evernote,
Export of Toolkit Settings (Bottom Left of Settings Page)
[{"key":"AccountsDisplayDensity","value":"1"},{"key":"AccountsEmphasizedOutflows","value":false},{"key":"AccountsStripedRows","value":true},{"key":"AdditionalColumns","value":true},{"key":"AdjustableColumnWidths","value":true},{"key":"AutoCloseReconcile","value":false},{"key":"ChangeEnterBehavior","value":true},{"key":"CheckNumbers","value":false},{"key":"ColourBlindMode","value":false},{"key":"CustomFlagNames","value":true},{"key":"DisplayTargetGoalAmount","value":"0"},{"key":"GoalWarningColor","value":false},{"key":"HideAgeOfMoney","value":false},{"key":"HideReferralBanner","value":false},{"key":"PrintingImprovements","value":true},{"key":"RemovePositiveHighlight","value":false},{"key":"RowHeight","value":"0"},{"key":"RunningBalance","value":true},{"key":"ShowCategoryBalance","value":true},{"key":"SquareNegativeMode","value":false},{"key":"StealingFromFuture","value":true},{"key":"TargetBalanceWarning","value":true},{"key":"accountsClearSelection","value":true},{"key":"activityTransactionLink","value":true},{"key":"betterScrollbars","value":"1"},{"key":"budgetBalanceToZero","value":true},{"key":"budgetProgressBars","value":"0"},{"key":"budgetQuickSwitch","value":true},{"key":"budgetRowsHeight","value":"1"},{"key":"calendarFirstDay","value":"0"},{"key":"categoryActivityPopupWidth","value":"2"},{"key":"checkCreditBalances","value":true},{"key":"collapseExpandBudgetGroups","value":true},{"key":"collapseSideMenu","value":true},{"key":"compactIncomeVsExpense","value":true},{"key":"currentMonthIndicator","value":true},{"key":"daysOfBuffering","value":true},{"key":"daysOfBufferingHistoryLookup","value":"0"},{"key":"editButtonPosition","value":"2"},{"key":"enableRetroCalculator","value":true},{"key":"enlargeCategoriesDropdown","value":true},{"key":"goalIndicator","value":false},{"key":"googleFontsSelector","value":"0"},{"key":"hideAccountBalancesType","value":"0"},{"key":"hideHelp","value":true},{"key":"highlightNegativesNegative","value":true},{"key":"importNotification","value":"2"},{"key":"incomeFromLastMonth","value":"1"},{"key":"l10n","value":"0"},{"key":"largerClickableIcons","value":true},{"key":"monthlyNotesPopupWidth","value":"2"},{"key":"navDisplayDensity","value":"2"},{"key":"pacing","value":"0"},{"key":"popupCalculator","value":true},{"key":"privacyMode","value":"2"},{"key":"reconciledTextColor","value":"0"},{"key":"removeZeroCategories","value":true},{"key":"reports","value":true},{"key":"resizeInspector","value":true},{"key":"rightClickToEdit","value":false},{"key":"seamlessBudgetHeader","value":true},{"key":"showIntercom","value":true},{"key":"spareChange","value":false},{"key":"splitKeyboardShortcut","value":true},{"key":"splitTransactionAutoAdjust","value":true},{"key":"swapClearedFlagged","value":false},{"key":"toBeBudgetedWarning","value":true},{"key":"toggleSplits","value":true},{"key":"toggleTransactionFilters","value":"0"},{"key":"warnOnQuickBudget","value":false}]

Steps to Reproduce the Behavior
Please write down the steps necessary to reproduce the behavior you're seeing. Please be as thorough as possible.

 Turn on option "Show Menu When Right Clicking on Transaction"
 Refresh YNAB
 receive error message saying that YNAB needs to refresh.

Expected Behavior
What did you expect would happen after completing the steps?
Not receiving error message
Actual Behavior
What actually happened after you completed the steps.
Received error message.

YNAB released an update which broke many features this looks to be one of them. I'm going to tag issues #892 so that we have reference to this issue and close this one. If you still experience the issue after our next release, please reopen.

Thanks for the update.
BTW - I'm very impressed the the YNAB toolkit.  This is the first issue I
have ran across.  It was quite a shock!  :)
Please keep up the good work.  I wish I could help with the project.
-Steven Loosle
On Fri, Sep 8, 2017 at 1:42 PM, Josh Madewell<EMAIL_ADDRESS>wrote:

YNAB released an update which broke many features this looks to be one of
them. I'm going to tag issues #892
https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/892 so that
we have reference to this issue and close this one. If you still experience
the issue after our next release, please reopen.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/906#issuecomment-328196241,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIsuAwJbceMYusEDQdvC7Uz13SPfTvrAks5sgZi5gaJpZM4PRc_Q
.


IATU, IASP error handling

I agree. Many other classes (e.g. IATU or IASP to just name some) have to be reworked then too, right? The same question arises also for the following suggestions.
_Originally posted by @CASAG-MariusRaht in https://github.com/render_node/MDI0OlB1bGxSZXF1ZXN0UmV2aWV3Q29tbWVudDMzNjM1NzYzNg==/comments/review_comment

duplicate #2982


Task Card Title Display Enhancement

Closes : #565
Description:
This pull request addresses the issue of task card titles not being displayed correctly when the title is long and wrapping to multiple lines. The proposed changes aim to improve the task card title display by ensuring that long titles are shown in a single line with an ellipsis (...) to indicate that the title has been truncated.
Changes Made:

Updated the CSS styles for task card titles to enforce a single line display.
Added the text-overflow: ellipsis property to truncate long titles with an ellipsis when they exceed the available width.

After Changes
https://github.com/Real-Dev-Squad/website-status/assets/70854507/e51cac31-de91-489a-95e9-28db10d09209

As discussed please add tooltip for the ellipsis.

As discussed please add tooltip for the ellipsis.

Currently we don't have a design for tooltip so i can't add it.

In that case can you create a ticket for adding tooltip and mention there that design is awaited. and add that ticket link here.

As discussed please add tooltip for the ellipsis.

Currently we don't have a design for tooltip so i can't add it.

In that case can you create a ticket for adding tooltip and mention there that design is awaited. and add that ticket link here.

Issue ticket for add tooltip - https://github.com/Real-Dev-Squad/website-status/issues/570


⚠ Bofrost.de has degraded performance

In 19530a1, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1399 ms

Resolved: Bofrost.de performance has improved in a6759c0 after 13 minutes.


Find authoritative documentation for retryable error codes

last comment in https://github.com/googleapis/google-cloud-cpp/pull/8736

Punt for now.

Realistically no time to work on this. Closing.


Updated Provisioning.Extensibility sample using the new ExtensibilityHandler interface

Q
A

Bug fix?
no

New feature?
no

New sample?
updated

Related issues?

What's in this Pull Request?
This PR contains an update in the Provisioning.Extensibility sample, to use the new ExtensibilityHandler interface instead of the "deprecated" ProvisioningHandler. Also, the project has been updated to use the new SharePointPnPCoreOnline nuget package.

thx Luis, good update on the sample so that we have up to date reference for the community.


Traslate frontend page title and meta elements.

Sorry, I forgot those translations. 😅

By the way, I don't know what the abbr FC means. So I can't translate this word. 😂


Sidebar scroll position

Is this a bug report?
yes

Have you read the Contributing Guidelines on issues?
Yes
Environment
all versions
Expected Behavior

This is probabaly more of a feature request but could be also considered an UX bug.
I will explain on the RN docs.
So when the sidebar is quite long and I scroll to some item, for example AccessibilityInfo (in the API section) and if I click on it the AccessibilityInfo doc is loaded and the sidebar scrolls all the way up. if I would like to check some other doc from the API section I would have to scroll again. I would expect it to keep the sidebar scroll position as is.

@knowbody
Mind to give more information/describe it more clearly ? Seems to me this is quite normal given that user loads a new html page when choosing a doc.

If we convert Docusaurus into an server-side rendered SPA in v2, this problem would go away.

Maybe it looks like SPA now because there is no trailing .html 😂

The weird thing is that, Reason docs has the behavior that @knowbody wants. Try clicking on "Syntax Cheatsheet" from https://reasonml.github.io/docs/en/quickstart-javascript

@yangshun
Seems like a javascript hack for me
https://github.com/MoOx/pjax

Pjax is a standalone JavaScript module that uses AJAX (XmlHttpRequest) and pushState() to deliver a fast browsing experience.

It allows you to completely transform the user experience of standard websites (server-side generated or static ones) to make them feel like they are browsing an app, especially for users with low bandwidth connection.

No more full page reloads. No more multiple HTTP requests.
https://github.com/reasonml/reasonml.github.io/blob/source/website/static/js/pjax-api.min.js

Ah that's the trick. What an awesome trick. We can consider adding that to
core!
On Tue, Jul 3, 2018, 12:05 PM Endilie Yacop Sucipto <
<EMAIL_ADDRESS>wrote:

@yangshun https://github.com/yangshun
Seems like a javascript hack for me
https://github.com/MoOx/pjax
Pjax is a standalone JavaScript module that uses AJAX (XmlHttpRequest) and
pushState() to deliver a fast browsing experience.
It allows you to completely transform the user experience of standard
websites (server-side generated or static ones) to make them feel like they
are browsing an app, especially for users with low bandwidth connection.
No more full page reloads. No more multiple HTTP requests.
https://github.com/reasonml/reasonml.github.io/blob/source/website/static/js/pjax-api.min.js
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/Docusaurus/issues/823#issuecomment-402262182,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQRHaif3y0syRxcd8o8Uakds09P5ovtks5uC8COgaJpZM4U_InG
.

It would be awesome!
On Tue, 3 Jul 2018 at 21:20, Endilie Yacop Sucipto<EMAIL_ADDRESS>wrote:

Oops reasonml is actually using the 2nd generation pjax
https://github.com/falsandtru/pjax-api
Not really sure on the difference but i guess this pjax thing is quite
cool.
Yeah I agree on adding it 😃
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/Docusaurus/issues/823#issuecomment-402265884,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADoDp_XLm4l-InrZMKgeFCGkhh1RYS-hks5uC8QBgaJpZM4U_InG
.

This would be a wonderful feature.

@prithvi16 it's yours!
I've added an "issue-claimed" label so that others will know not to start work on the issue. If you change your mind about the issue, no worries! Just let me know so that I can remove the label and free it up for someone else to claim.
I'll check in with you periodically so that we can keep the task updated with the progress.

@yangshun  Thanks!
So how do you want me to do this? Should I use Pjax hack used by https://github.com/reasonml/reasonml.github.io/blob/source/website/static/js/pjax-api.min.js
Or something else?

Yes ReasonML's way looks good. If you can think of even better ways that would be appreciated.

Here's my proposal :
Store scroll location in local storage when user scrolls
and retrieve it on page reload.

Store scroll location in local storage when user scrolls and retrieve it on page reload.

What if someone opens multiple pages of Docusaurus in the same browser? It's not uncommon to right click -> open in new tab when browsing documentation.

Yes. :smile: . I will think of something else.
Do you have anything in mind?

Should I go ahead with adding Pjax to Docusaurus @yangshun ?

Here's something of a hack I put together to address this on my own docusaurus site.
I load the following code in a script, using the scripts parameter in siteConfig.js.
document.addEventListener('DOMContentLoaded', () => {
  // Find the active nav item in the sidebar
  const item = document.getElementsByClassName('navListItemActive')[0];
  if (!item) { return; }
  const bounding = item.getBoundingClientRect();
  if (
    bounding.top >= 0 &&
    bounding.bottom <= (window.innerHeight || document.documentElement.clientHeight)
  ) {
    // Already visible.  Do nothing.
  } else {
    // Not visible.  Scroll sidebar.
    item.scrollIntoView({block: 'center', inline: 'nearest'});
    document.body.scrollTop = document.documentElement.scrollTop = 0;
  }
});

This code checks to see if

is an active nav item in the sidebar?
if so is it scrolled outside the viewport?
if so scroll the nav item into view and then scroll the document to the top (to avoid having other content not scrolled to the top.)

I'm posting it here in case this approach is useful to others, or if there's interest in integrating this as an option into the docusaurus core (until serverside SPA lands).  I don't believe it will work in all browsers due to lack of support for scrollIntoView in all browsers, and I haven't done any cross browser testing yet outside of chrome.

@samg Thank you for your tip! 🎉 I am using it here: https://github.com/reactioncommerce/reaction-docs/pull/686, scrolling through over 130+ docs or so. Great to learn about https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoView

@prithvi16 Sorry for the late response. I think making pjax an opt-in feature would be really cool! Not sure how much work it involves but if it can be easily turned off/on we're keen to have it. Otherwise, the hack/tip by @samg works ok as well.

Okay. Thank you for the response. Will submit a PR by the end of the week.
On Sun, Oct 14, 2018 at 1:24 AM Yangshun Tay<EMAIL_ADDRESS>wrote:

@prithvi16 https://github.com/prithvi16 Sorry for the late response. I
think making pjax an opt-in feature would be really cool! Not sure how much
work it involves but if it can be easily turned off/on we're keen to have
it. Otherwise, the hack/tip by @samg https://github.com/samg works ok
as well.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/Docusaurus/issues/823#issuecomment-429570504,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKXRyQtyuyh8vEq2p85LuO5qMj751blVks5ukkUAgaJpZM4U_InG
.

--

Prithviraj Sukale

Closing due to stale. Please use the suggested workaround on 1.x. It will come by default on next major version. See https://docusaurus-2.netlify.com for WIP


Update EmailEditor.Page.al

I want to include an alternative email editor and need to call the ShowCloseOptionsMenu function from my PageExt to do this. Can you therefore set the function to "protected"?
Thanks a lot

Will ship with 23.1.

Thank you :)

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

Availability update: We will publish a fix for this issue in the next update for release 23.
Build ID to track: 12931.