Egeria monthly workshop documentation

In order to have better documentation of what we have discussed during the workshop, it would be really helpful for us to keep them in the git repo and use as reference on any decisions that we have made.
This issue will be referenced for the PRs of adding Egeria Workshop documentation in the developer-resources module.

In order to have better documentation of what we have discussed during the workshop, it would be really helpful for us to keep them in the git repo and use as reference on any decisions that we have made.

I wasn't on for that part of the discussion, but just wanted to be sure this doesn't supersede creating more granular issues for individual topics that were agreed and need to have some work done to address them (whether fixes, changes, new functionality, etc)?  I wouldn't want to try to track all changes against some large piece of documentation, or it won't be very clear what progress we're making / still remains to be made, and collaborating on further sub-decisions against each granular item won't really be possible...

Hi @cmgrote you are right it does not mean we are going to replace any particular issues or any topics we have discussed. It is just used for adding general workshop notes as not everyone of us is involved in every topic during the workshop. So the purpose is just to track what we have discussed during the workshop and some results or questions from it so we can have a memory on it.
Maybe it is not a practical approach to create an issue for adding the notes of workshop. What do you think?

Maybe it is not a practical approach to create an issue for adding the notes of workshop. What do you think?

I think it's great to have the notes of each workshop, no debate there -- but indeed, I'm not sure what the added value of an issue is to ensure that those notes are entered.  They should be easy enough to find just based on the folder structure of the repository when they're committed (?)
As long as we're still planning to create separate (granular) issues for each topic that needs some action, then that gives us the fine-grained traceability and progress monitor-ability(?)

Maybe it is not a practical approach to create an issue for adding the notes of workshop. What do you think?

I think it's great to have the notes of each workshop, no debate there -- but indeed, I'm not sure what the added value of an issue is to ensure that those notes are entered. They should be easy enough to find just based on the folder structure of the repository when they're committed (?)
As long as we're still planning to create separate (granular) issues for each topic that needs some action, then that gives us the fine-grained traceability and progress monitor-ability(?)

Yes I agree with you. It would be wise to keep the issue on lower granular level so it can be clear and resolvable for anyone. In this case I will close this issue and still add the notes. Thanks!


Support pyarrow 14.0.0

Support pyarrow 14.0.0.
Fix #6377 and fix #6374 (root cause).
This fix is analog to a previous one:

#6175

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


[BUG] Parse Block Raising Errors

Describe the bug
Can you make the parse block return empty instead of throwing an error.
Example:
Block:Parse
MODE:Json
if the site return a non json response, the parse block break and throw an error

I honestly don't see any reasons for this to be implemented, once you can just handle the possible error. Ruri gave an example in this answer in another issue: https://github.com/openbullet/OpenBullet2/issues/12#issuecomment-793870899

I can see why this would be preferred by non-programmers though.
We have to make a decision fast because if I do it, it will break configs that rely on catching the exception from the parse block, so it's better to do it as soon as possible instead of waiting to minimize the impact.

I can see why this would be preferred by non-programmers though.
We have to make a decision fast because if I do it, it will break configs that rely on catching the exception from the parse block, so it's better to do it as soon as possible instead of waiting to minimize the impact.

I don't see why any configs would rely on catching the exception from the parse block, since the error handler is there because in some cases the error will happen. But if you want to implement this, its up to you, I personally see no reason to do this since you can easily use the TRY CATCH. That way new members/people not used to programming can also learn a bit more about programming and how to treat errors xD.

Maybe we could set it to null instead of a blank string / empty list so we can differentiate between something that couldn't be parsed and something that could be parsed but was simply empty.
This will avoid the try/catch syntax in the config and still let people check if anything was parsed through a keycheck right after the parse block, which adds less noise to the code.
Let me know what you guys think!


[PRO]: MentionBridge example not working on latest versions

Describe the bug
It seems like after typing a Mention and selecting one (which causes it to be inserted), the backspace key stops working until you use a directional arrow. Once you use a directional arrow, backspace starts working again.  Doing some debugging, it seems like taking any action on the editor at all causes this to hapeen.
This bug does not reproduce on version 0.5.8, but after upgrading to 0.5.12 and 0.5.13 (and rebuilding the editor), it happens consistently.
To Reproduce
Steps to reproduce the behavior:

Open the MentionBridge paid example.
Change of 10play/10tap-editor to 0.5.13.
Run yarn editor:build
Open in simulator (iOS), type an @ and then select a mention.
Try to press the backspace key.

Expected behavior
Backspace key should keep working.

We're looking into this - seems to be some dependency issue caused by https://github.com/10play/10Tap-Editor/commit/26000271ccf4f0b95c359672015895f8dca21d5f

Should be fixed on 0.5.15

Thank you, it's working great now!


event-stream missing in dependency

In the package.json the event-stream package is missing as dependency

run  npm i --save-dev event-stram , then it worked.

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

3. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

Winners: @lxedge, @Zawaf, @ElijahLaMoon, @lluma, @peyzor, @Rofromthetrap, @xfo-0, @istvancsabakis, @Olegt0rr, @MatthieuBarraque

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.

Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @


Prettify without leaving out the comments.

LS
Thanks for all effort invested into this power tool. The Transcrypt Python to JavaScript compiler uses the Google Closure Compiler, both to minify code and to convert es6 to es5.
We'd like to be able to use it also as a code prettyfier. So what would be needed then is the possibility to have it output for es5 or es6 WITHOUT STRIPPING COMMENTS, but just prettifying it.
Kind regards
Jacques de Hooge
<EMAIL_ADDRESS>

You can use the option --preserve_type_annotations to keep the type-related comments. Currently, we don't have a way to preserve all comments.

Ok, I understand that.
I'll leave this as a feature request, but I can fully understand there are other priorities.
KR
J

Another possibility to look at is clang-format, which is a tool specifically for formatting code and has a JavaScript mode:
http://clang.llvm.org/docs/ClangFormat.html

@blickly
Thanks for the advice!


Need a standalone script to sign the artifacts

Is your feature request related to a problem? Please describe
Signing the artifacts is a manual process. We need to automate the signing process for the artifacts.
Describe the solution you'd like
Write a bash script to sign the artifacts for release.
Describe alternatives you've considered
No response
Additional context
No response

Part of #778 and #757


chore(deps): upgrade jenkins-x/jx3-versions to version 1.1.16

from: https://github.com/jenkins-x/lighthouse.git

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
4fe9508864933f929b9f52929d088d222dcdcdb7
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
4fe9508864933f929b9f52929d088d222dcdcdb7
link
/test gsm

vault
4fe9508864933f929b9f52929d088d222dcdcdb7
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
4fe9508864933f929b9f52929d088d222dcdcdb7
link
/test gsm

vault
4fe9508864933f929b9f52929d088d222dcdcdb7
link
/test vault

kube
4fe9508864933f929b9f52929d088d222dcdcdb7
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
4fe9508864933f929b9f52929d088d222dcdcdb7
link
/test gsm

vault
4fe9508864933f929b9f52929d088d222dcdcdb7
link
/test vault

kube
4fe9508864933f929b9f52929d088d222dcdcdb7
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Mac support

Thanks for your contribution.
Unfortunately the decpp change conflicts with what I already comitted earlier.
Could you please sync with your local fork and create a new PR only adding the mac library?


Swift 2.3 or Swift 3 Support

Hi,
Thanks for your great tool. It would be great if it could support Swift 2.3 or Swift 3 ?
Cheers,

This is currently being working on. You should hopefully see it shortly :)

Could you re-open this issue until it's fix? Almost submitted a new one.. I guess we can consider it's not fix until done, correct?

Agreed -- I'm not sure why I closed this ;)
Please feel free to contribute 👍

Trying (at least for 2.3) but having some issue doing a clean PR on InkKit.. Can't set base PR branch to a tag!? (see: https://github.com/shaps80/InkKit/pull/5)

I understand.  Not that i will never both to formally support 2.3 since no further Xcode versions will support it.
Shaps
Sent from my iPhone

On 8 Nov 2016, at 13:37, Hugues Bernet-Rollande<EMAIL_ADDRESS>wrote:
Trying (at least for 2.3) but having some issue doing a clean PR on InkKit.. Can't set base PR branch to a tag!? (see: shaps80/InkKit#5)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

@shaps80 yep I know XCode 8.2 is last Swift 2.3 support :( I thought Obj-C was dead :P. I love all my Obj-C pods right now :). I think having Swift 2.3 supporting branches (but not keep up to date) is nice. Will try my best.

@shaps80 ask and you shall receive... https://github.com/shaps80/Peek/pull/16. Except issue with not being able to point to the correct branch on the PR (as there is not branch for the base branch on which I did my changes, ...).. Hope it's clear.

Hi, is there any Swift 3 support planned? I really like this tool and would love to use it in my Swift 3 projects too.

Absolutely. However my wife and I just had a baby a few days ago so I couldn't say how long it'll be before I find the time.
You're more than welcome to submit a PR ;-)
Shaps
Sent from my iPhone

On 14 Dec 2016, at 21:33, anneWe<EMAIL_ADDRESS>wrote:
Hi, is there any Swift 3 support planned? I really like this tool and would love to use it in my Swift 3 projects too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

pod 'Peek', '2.3'
Thanks to @huguesbr for his help getting this out -- sorry for the delays.

@anneWe @huguesbr @mackoj Just letting you all know...
Swift 4 will be officially supported this week!
Thank you for supporting the project.


Allow setting tag message with $EDITOR.

Both Git and Mercurial have the option to write an annotated tag in the
$EDITOR. Expose this when --tag-message is passed with no argument.

This changes it to always tag with a message and I'd like to keep the option not to tag with a message.

This changes it to always tag with a message and I'd like to keep the option not to tag with a message.

I don't think this commit changes that behavior -- message is only None if --tag-message is passed with no arguments. If I understand it correctly, in your branch the only way to have no tag is by passing --tag-message '' and I believe I've preserved that behavior since that test (test_unannotated_tag) still passes.

I was slightly surprised there was no test for 'without message' so I'm going to verify. Otherwise I think this is looking like a nice addition to my patch.

Thanks for the review. At first I was thinking this should be merged into your branch/PR but now I'm thinking I should submit it as a separate PR to upstream. It doesn't change much of your work and given that #58 has been under review for over a year it would be a shame to start the review process over. Thoughts?

I was thinking of further reviewing your comments and then keep it as a separate commit. That should make reviewing simple enough. I don't think the size of #58 matters that much, there's simply a lack of time at all.

Cool.

My apologies for never getting around to it. I'm going to close this now but please open a PR against https://github.com/c4urself/bump2version which is a fork and released on pypi.


(MODULES-6699) Add spec tests

This PR adds spec tests to cover the psrepository type, then increases the validation blocks in the psrepository type to handle basic validation for params and properties.
It also updates the .gitignore to ignore the common files generated in Puppet module development.

Hi @hbuckle, I was hoping you could review this for me. This is part of our work to get this module to the approved status.


[FLOC-3119] Cache inspected image data in memory

Fixes FLOC-3119

Thanks, back to you for some improvements.

Thanks.  Back to you.

This is the wrong requirements file, I think.

Oops, good catch! Absent-minded Monday morning (AMMM) syndrome.

image is a unicode ID in the callable here though, as things stand atm.

Ah.  Okay.  Probably better to use the Field.for_types constructor, then, and just tell Eliot that the value is unicode rather than supplying repr as a serializer.

Thanks!  Just a few more points, marked with inline comments.  Please address those and merge when buildbot is green.


Supporting Helix editor

Is your feature request related to a problem? Please describe.
I have been using the nightfox theme for neovim and I find it very neat.
However, recently, I started playing with the new text editor, Helix (https://github.com/helix-editor/helix), which is inspired by Neovim and Kakoune editors. I wonder if it is possible to make the nightfox theme compatible with it?
Describe the solution you'd like
It would be nice to have the nightfox theme work with the helix editor.
Thank you

This is similar to #68, with asking for vscode. Anyone is welcome to port nightfox and I can link it in the readme.

I want to try porting it because as of today I'm also playing around with Helix. @EdenEast should I create a PR where I put the files in the extra directory or should I create a new repo?

I am not sure how helix does colorschemes/plugins. If using the extra's directory would work then sure you can make a PR. If it would require a new repo, when it is ready you can open a PR and we can add it to the readme.

I have created a new Repo to avoid cluttering this issue section with helix issues. At the moment only carbonfox is ported because it's my main theme. There are plans to port the others too. PR's are welcome.


23.05 & 23.11 Issues with Qt applications (dark theme and emoji rendering)

Describe the bug
Since I migrated from 22.11 to 23.05 (and now to 23.11 where all the issues still persist) I got some bugs that I see every day. I was lazy about reporting it earlier, and hoped it would be fixed in 23.11 by some Qt libs update for example. But now in 23.11 it’s still there as in 23.05.

keepassxc (Qt-based app) starts using dark or light color scheme with approximately 50%/50% chance (it’s supposed to be dark by the config):
qt = {
  enable = true;
  platformTheme = "gnome";
  style = "adwaita-dark";
};

I can’t figure out a pattern, to me it seems random. I can’t say whether it would be a light or dark theme when I run the app, can’t tell what it depends on. I can just run and close it in a loop and it would randomly be one or another. The log is always empty, I don’t see any errors or warnings.
In 22.05 it was working just fine. Always the dark theme, as configured in my NixOS config.

The second issue is in nheko (QML app) with emojis. They are not rendered in the message typing field, and in the quick search (by Ctrl+K). But everywhere else it’s rendered just fine (rooms list, chat, etc.). In 22.05 emojis were rendered properly everywhere. When I migrated to 23.05 the Nheko version did not change, so I can tell for sure it’s not an internal regression in Nheko.

Steps To Reproduce
Steps to reproduce the behavior:

Configure Qt theme to be dark like this:
qt = {
  enable = true;
  platformTheme = "gnome";
  style = "adwaita-dark";
};

Run and close keepassxc in a loop multiple times

Observe that it rendered with either light or dark theme randomly picking one or another

In Nheko try to type an emoji (using : sign or copy-paste it from somewhere)

Observe it’s either square box (unknown char) or a plain text (non-colored) sign

Expected behavior

keepassxc to always start with a dark theme.
Emojies in Nheko to be rendered both in the message typing field and quick search window

Screenshots
KeePassXC:

Nheko:

Additional context
  qt = {
    enable = true;
    platformTheme = "gnome";
    style = "adwaita-dark";
  };

Notify maintainers

KeePassXC @jonafato @BlankParticle
Nheko @Ekleog @fpletz

Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.3, NixOS, 23.11 (Tapir), 23.11.1115.5de0b32be6e8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos, nixos-unstable"`
 - channels(wenzel): `"nixpkgs-test"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I can add an example of another Qt application that has Emoji rendering issues — psi-plus. This I see in the roster (contact list):

First of all, I can confirm @unclechu's keepassxc behavior.
Additionally, it seems like I'm facing a extende "dark-theme" issues on some KDE apps under GNOME with the same settings. The general theming in qt apps seems like a bit of a mess to me...
Can anyone approve the broken theming on the following apps following my settings?
Additional context
My system configuration: dotfiles.nix
Settings for Qt integration (nixos/gnome.nix:l.118):
BackgroundNormal=#2E2E2E
  ## Leftover KDE Support
  qt = {
    enable = true;
    platformTheme = "gnome"; # leverages qgnomeplatform package; redundant due to gnome.core-os-services
    style = "adwaita-dark";
  };

~/.config/kdeglobals:
[Colors:View]
BackgroundNormal=#2E2E2E

[General]
TerminalApplication=gnome-terminal

[KDE]
ShowDeleteCommand=false

Screenshots
libsForQt5.gwenview:

libsForQt5.konsole:

libsForQt5.okular:

libsForQt5.kate:

libsForQt5.kate (without the BackgroundNormal=#2E2E2E value in ~/.config/kdeglobals):

kwrite:

Properly themed apps

dolphin
krita
qtikz

On my system, just tried out a few ones


Update verify-egress command

With the merge of https://github.com/openshift/osd-network-verifier/pull/122, the interface for running an egress test has changed. This PR updates the verify-egress command to use the latest interface, as well as expose new options available for the test.

/lgtm

/lgtm
tested locally all working well

/hold cancel

/lgtm
/approve
Great work!


Clean up dependencies and ordering, fix syntax for future parser

For instance, syntax like:
notify    => File[$homebrew_directories]
is not valid and doesn't do anything useful in future parser.  This uses ordering operators to ensure all of the directories are managed prior to running the installer.
It also manages the brew user.

Thanks for the help!


Add brew install deno to README

We should also update the manual https://deno.land/manual.html#binaryinstall

If someone updates the manual, please also recommend scoop install deno on Windows.


Can't refuel beds

To quote a comment on the Steam Workshop page: "So currently i can build a ergonimic and advanced nano beds which cannot be refueled for some reason. vanilla beds work fine. the ergonomic and advanced beds are from vanilla furniture expanded".
I have the same problem. It seems as if I cant refuel those beds.

I have the same problem


Darkside skin and colors

Read more here: https://github.com/ZeroBug-ZB/tvjs-xp/tree/main/src/extensions/darkside
Please note that using:
<trading-vue :data="dc" :extensions="ext" skin="darkside"/>
cause following crash:
client.js?06a0:96 TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))     at shaders_createForOfIteratorHelper (trading-vue.js?0042:13465)     at VueComponent.init_shaders (trading-vue.js?0042:13481)     at VueComponent.mounted (trading-vue.js?0042:13575)     at invokeWithErrorHandling (vue.runtime.esm.js?2b0e:1854)     at callHook (vue.runtime.esm.js?2b0e:4219)     at Object.insert (vue.runtime.esm.js?2b0e:3139)     at invokeInsertHook (vue.runtime.esm.js?2b0e:6346)     at VueComponent.patch [as __patch__] (vue.runtime.esm.js?2b0e:6565)     at VueComponent.Vue._update (vue.runtime.esm.js?2b0e:3948)     at VueComponent.updateComponent (vue.runtime.esm.js?2b0e:4060)
After some debugging, it seems a problem related to the automatic builded "tvjs-xp.js" and not related to the extension/skin itself.

Thanks for the contribution. I was thinking about an extension with several color themes, w/o doubt will add your pack.

Thanks for the contribution. I was thinking about an extension with several color themes, w/o doubt will add your pack.


[Bug] [dolphinscheduler woker]  datax use mysql to hive not work

Search before asking

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

What happened
datax use mysql to hive not work

What you expected to happen
i found  this will be  Translated into

but data x  not support  rdbms hive writer
and  From both hive and spark, it's not nearly as good as Hdfswirter.
How to reproduce
so  Have you tested the feasibility of this feature
Anything else
No response
Version
3.1.x
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

The same to me ,when use datax to sync mysql data to apache hive!


Create uk-UA.json

Initial translation

Does this translation exist in transifex?
If so, please just translate it there. We pull all the translations from transifex every release, and replace any files in the repo with them.

Okay, thanks for a reply

I saw your join request on Transifex and approved it. Thank you for helping with translations.

My pleasure!


about_us

about_us page

@mohdshahzil Please disable the linting for using single quotes and double quotes as it is having problems with next lint

@mohdshahzil Please disable the linting for using single quotes and double quotes as it is having problems with next lint

will look onto it


parameterHints text blurs on scroll when editor zoom level is non-default

VSCode Version: Code 1.8.1 (ee428b0eead68bf0fb99ab5fdc4439be227b6281, 2016-12-19T14:49:23.350Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

PowerShell
ms-vscode
0.7.2

Steps to Reproduce:

Zoom out from default/reset zoom level (Ctrl + -)
In a .psm1 PowerShell file, type a command, begin typing an argument with a hyphen (eg: Write-host -)
The suggestion box will show, scroll down any amount and observe the text is no longer sharp but is now blurry

#5154


Saving current progress

As my algorithm is going to last quite long I am wondering if there is any possibility to save my current progress (Population, BestChromosome, etc.)? Then having it saved, recreate an algorithm and run from this point, instead of starting with fresh Algorithm.

We've already talked about something similar to what you want in this issue  https://github.com/giacomelli/GeneticSharp/issues/9

Closed due to inactivity. Feel free to reopen it if needed.


Fix Formatting

Made "Maintains the backlog" an H3, as it appears it should have been all along. Removed an errant comma and turned an "an" into "a".

Ping on this pull request, since I don't have write access to this repo.


Work up person and organization data files

Person and organization names show up as creator or contributor contacts in DataCite records. They will all have at least a name, which is generally in the form "last, first initial" for people. I made a design decision to put givenName and familyName together into a more readable label, so these are the labels for people we end up with in content metadata and in the authors taxonomy (I still also need to work through other contributors and decide what to do on classification).
The operational modality I'm developing is to leave the taxonomy structure simple with lists of labels but then back this up with data files as JSON in the /data/ folder of the site that can be called up to pull in additional details. Those details are most appropriate on what becomes the logical landing page for the term, specifically the list.html files in the layout folder for each taxonomy. I initially proved the basic method by calling up ORCID values for named authors and adding a link to ORCID for the person.
For this task, I just need to ensure that I write every person and organization label used in building content to separate data files (e.g., people.json and organizations.json). Available properties will vary, but I will start with simply including whatever is onboard the items in a given batch of DataCite documents being processed. For people or organizations including a resolvable identifier like an ORCID, I will group records on these. Grouping will put content together from multiple instances, which may or may not be the same (names can vary across time for one reason or another). For name-only contacts, I have no real choice but to group on their labels and hope for the best unless I want to consult a logical source for disambiguation within a particular context.

For the initial cut at this, I created a single JSON data cache called contacts.json with all creator and contributor entities from the given dataset. Items are indexed on their label (name attribute from Datacite metadata). The relevant layouts (now in the PaperMod fork theme) such as author fetch the additional properties for a person and display them on the list page using a partial called contact.html.
I need to do some further work in this area to run any initial disambiguation based on identifiers (so far, I've not encountered cases where the same name/label exists in a dataset with one having an identifier and the other not). It might also be nice to turn named entities into links, but I need to figure out Hugo's complete logic in taking taxonomy term strings and turning those into logical web page names (e.g., "Balhara, Himanshu" becomes "balhara-himanshu" which seems straightforward, but I've found corner cases I don't understand yet).


Set node version to 23.1

FRONTEND PULL REQUEST
Related Issue
Our frontend build job was initially passing following the Node 23 upgrade. Recently, the same job began to fail.
@mehansen found that version 23.2.x of NodeJS released on November 11, 2024 is breaking our frontend builds
Changes Proposed

Specify the minor version of NodeJs to avoid this regression

Additional Information
Previous comment

⚠ I didn't change the image in our frontend Dockerfile because it looks like that image uses node 23.1.0. Let me know if you prefer I choose a different image though 🤔

Updated to a Docker image with node 23.1.0 set
See other reported issues:

https://github.com/nodejs/node/issues/55826
https://github.com/webpack/webpack/issues/18963

Internal convo here
Testing

All checks (maybe minus Trivy 😅 -- unrelated to this) should pass
deployed on dev6

Screenshots / Demos

N/A

do we know how often the Docker images are updated and how that impacts us? I assume someone would update it to use 23.2 soon enough. if that happens will our frontend start failing to build?
tagging @shanice-skylight in case she has more insight

During pairing @mehansen found this image that sets it to node 23.1 so I'll update with this one for now!

smoke tested in dev6. checks pass, so looks good to me


Add shlink extension

Description
Manage your shlink addresses.
You can create, edit and delete short URLs, get a QR-Code and tracking pixel for each one of them, and much more!
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi, @pernielsentikaer !
Sorry for so long answer.

thunderforestApiKey/thunderforestType is not used in the code but is set in the preferences

This preferences using there:
  const { thunderforestApiKey, thunderforestType } = getPreferenceValues<ExtensionPreferences>();

  const mapLink =
    item.visitLocation && !item.visitLocation?.isEmpty
      ? `https://tile.thunderforest.com/static/${thunderforestType}/` +
        `${item.visitLocation.longitude},${item.visitLocation.latitude},14/300x125@2x.png?` +
        `apikey=${thunderforestApiKey}`
      : "";

Could you record a screencast of the flow since I don't have shlink 🙂

Sorry, but I can't record a screencast, but if you need, I can give you docker-compose.yml for test or create a new domain for you.


Set testID on default tabs

Hi, I'm trying to set a testID on the default tab bar touchables, but I can't seem to find the way. I'm writing e2e tests with Detox and I'm trying to trigger a click on each tab icon. Is this possible at all? Should I instead build a customer tab bar?

Version
Tell us which versions you are using:

react-native-router-flux v4.2.0
react v16.9.0
react-native v0.61.5

I think custom tab bar should be used

@aksonov can you provide example of how to toggle drawer, and switch between tab bar using detox?

+1


DiscreteDP Performance

DiscreteDP performance might be bad in the Julia version.
For example, this Python code runs 220 times faster (local 2x2.66GHZ, 4 GB machine) than this Julia code. (The task is described here).
Could someone please replicated this performance issue?

Profiling the "solve"-function suggests nothing unusual:

BUT: line 319 and 380 in ddp.jl have:
 vals = ddp.R + ddp.beta * ddp.Q * v
but really should be:
 vals = ddp.R + ddp.beta * (ddp.Q * v).
Runtime drops by a factor of 6 and memory allocations drop from 500 MB to 2 MB of this single line!

Great sleuthing! This makes perfect sense!
Do you mind putting that change in a pull request?

I did not know what that means 30 minutes ago, but I hope I did the right thing!

A new performance test with the altered matrix multiplication yielded:
constructor 0.773396 seconds (2.02 k allocations: 466.133 MB, 2.01% gc time)
solve 1.922052 seconds (616 allocations: 108.402 MB, 1.30% gc time)
While Python has:
constructor CPU times: user 103 ms, sys: 8.35 ms, total: 112 ms
solve CPU times: user 56.5 ms, sys: 2.05 ms, total: 58.5 ms
So the issue remains open.

Further profiling points to linear algebra to be the most expensive type of operation, for both PFI:
and VFI:

@oyamad I saw you are working on a number of memory/performance issues concerning ddp.jl. May I suggest to make Q sparse throughout ddp.jl?
I played around with the evaluate_policy-function (ddp.jl:451) and having Q sparse (see the task above) leads to a ridiculously high performance gain (factor 22000) and I guess it will outweigh other disadvantages of sparse matrices.
Having Q sparse in the bellman_operator!-function (ddp.jl:318) yields a performance boost of factor 25.

You will probably want to be careful about making Q sparse without first having some kind of check as to whether a sparse matrix is appropriate. I won't claim to know much about sparse matrices but I imagine this is easy enough to check.
There are many economic applications (eg., markov has two states, employment and unemployment or recession and boom, and Q is transition between these, as eg. Imrohoroglu (1989), or the 4x4 Q matrix on labour efficiency units used by Castañeda, Díaz-Gímenez & Río-Rull (2003) to match the US lorenz curves for income and wealth inequality) where Q will not be a sparse matrix.
Equally, for many examples Q is probably going to be the Tauschen method of discretizing an AR(1) and these will be sparse (or close enough) so there are lots of examples where the speed boost @MaximilianJHuber is describing might be gained.

Ok, that is true. The user must decide.
I gave it a try and altered line 51 in ddp from: Q::Array{T,NQ} to Q::AbscractArray{T,NQ} (I know that is quick and dirty, because composite types should have concrete types a fields!)
and line 87 from new(R, full(Q), beta, _a_indices, a_indptr) to new(R, Q, beta, _a_indices, a_indptr)
Then the constructor allocates for grid_size=500 only 12 MB instead of 480 MB with a runtime improvement by factor 20 and solve allocates 43 MB instead of 108 MB with a runtime improvement by factor 17.
Are there expert opinions on sparse matrices? Or is the first order of business to redesign ddp.jl in order to gain performance?

I guess that once we decide on the internal data structure (visit #124 to join the discussion), it should be straightforward to implement methods that preserve the sparsity of the input matrix.


Problem in High Water Mark option in ZMQ communication

I have a problem in High Water Mark option in ZMQ communication:
According to the ZeroMQ documentation, a pub socket is supposed to drop messages once the number of queued messages reaches the high-water mark.
This doesn't seem to work in the following example (and yes I do set the hwm before bind/connect):
import time
import pickle
from threading import Thread
import zmq

ctx = zmq.Context()

def pub_thread():
    pub = ctx.socket(zmq.PUB)
    pub.set_hwm(2)
    pub.bind('tcp://*:5555')

    i = 0
    while True:
        # Send message every 100ms
        time.sleep(0.1)
        pub.send_string("test", zmq.SNDMORE)
        pub.send_pyobj(i)
        i += 1

def sub_thread():
    sub = ctx.socket(zmq.SUB)
    sub.subscribe("test")
    sub.connect('tcp://localhost:5555')
    while True:
        # Receive messages only every second
        time.sleep(1)
        msg = sub.recv_multipart()
        print("Sub: %d" % pickle.loads(msg[1]))

t_pub = Thread(target=pub_thread)
t_sub = Thread(target=sub_thread)
t_pub.start()
t_sub.start()

while True:
    pass

I'm sending messages on pub 10 times faster than reading them on the sub socket, hwm is set to 2. I would expect to only receive about every 10th message. Instead, I see the following output:
Sub: 0
Sub: 1
Sub: 2
Sub: 3
Sub: 4
Sub: 5
Sub: 6
Sub: 7
Sub: 8
Sub: 9
Sub: 10
Sub: 11
Sub: 12
Sub: 13
Sub: 14
...

So I see all messages arriving, thus they are held in some queue until I read them. Same holds true when adding a hwm=2 on the sub socket as well before connect.
What am I doing wrong or am I misunderstanding hwm?
I use pyzmq version 17.1.2

Also I tried with the following code, but result was the same:
import time
import pickle
import zmq
from threading import Thread

ctx = zmq.Context()

def pub_thread():
    pub = ctx.socket(zmq.PUB)
    pub.setsockopt(zmq.SNDHWM, 2)  # This line was changed.
    pub.bind('tcp://*:5555')

    i = 0
    while True:
        time.sleep(0.1)
        pub.send_string("test", zmq.SNDMORE)
        pub.send_pyobj(i)
        i += 1

def sub_thread():
    sub = ctx.socket(zmq.SUB)
    sub.setsockopt(zmq.SUBSCRIBER, b'')
    sub.setsockopt(zmq.RCVHWM, 2)  # This line added.
    # sub.setsockopt(zmq.CONFLATE, 1)  # Last msg only (another option).
    sub.connect('tcp://localhost:5555')
    while True:
        time.sleep(1)
        msg = sub.recv_multipart()
        print("Sub: %d" % pickle.loads(msg[1]))

t_pub = Thread(target=pub_thread)
t_pub.start()
sub_thread()  # Start with main thread.

These posts (POST1, POST2, POST3) are relevant to this issue in the Stack Overflow.

Thanks in advance,

Messages are held in operating system's network buffers. I have found HWMs to be not that useful because of that. Here is modified code where subscriber misses messages:
import time
import pickle
import zmq
from threading import Thread
import os

ctx = zmq.Context()

def pub_thread():
    pub = ctx.socket(zmq.PUB)
    pub.setsockopt(zmq.SNDHWM, 2)
    pub.setsockopt(zmq.SNDBUF, 2*1024) # see: http://api.zeromq.org/4-2:zmq-setsockopt
    pub.bind('tcp://*:5555')
    i = 0
    while True:
        time.sleep(0.001)
        pub.send_string(str(i), zmq.SNDMORE)
        pub.send(os.urandom(1024))
        i += 1

def sub_thread():
    sub = ctx.socket(zmq.SUB)
    sub.setsockopt(zmq.SUBSCRIBE, b'')
    sub.setsockopt(zmq.RCVHWM, 2)
    sub.setsockopt(zmq.RCVBUF, 2*1024)
    sub.connect('tcp://localhost:5555')
    while True:
        time.sleep(0.1)
        msg, _ = sub.recv_multipart()
        print("Received:", msg.decode())

t_pub = Thread(target=pub_thread)
t_pub.start()
sub_thread()

Output looks something like this:
Received: 0
Received: 1
Received: 2
Received: 3
Received: 4
Received: 5
Received: 6
Received: 47
Received: 48
Received: 64
Received: 65
Received: 84
Received: 85
Received: 159
Received: 160
Received: 270

Messages are missed because all queues/buffers are full and publisher starts to drop messages (see documentation for ZMQ_PUB: http://api.zeromq.org/4-2:zmq-socket).

At first glance set_hwm method is broken for modern 0mq.
It is effectively
        if major >= 3:
            raised = None
            try:
                self.sndhwm = value
            except Exception as e:
                raised = e
            try:
                self.rcvhwm = value
            except Exception as e:
                raised = e

            if raised:
                raise raised

sndhwm is not used in any other way.
Am I missing something?

Closing some old issues, especially those about libzmq socket behavior not specific to pyzmq. If you still have issues or questions, always feel free to open against libzmq, or other pyzmq-specific questions here.


Warn when using old Ruby version

Apparently Ruby 1.9.x doesn't support File.write which caused react-native init foo to fail for me. Ideally a warning should be given to help the user into the right direction.

The ruby dependency will be gone soonish. #440


On Map zoom or rotation marker icon disappears

Issue Type
[-] Bug
Description and/or steps/code to reproduce the problem
After drawing marker with icon drawable , icon vanishes on rotate or on zooming :
code for drawing marker
         private fun drawMarker(marker: TTMarker): Marker {
        val osmMarker = Marker(this)
        osmMarker.position = getGeoPoint(marker.location)
        osmMarker.setAnchor(Marker.ANCHOR_CENTER, Marker.ANCHOR_BOTTOM)
        osmMarker.title = marker.label

        if (marker.showLabelAsDrawable() && marker.label != null && marker.label.trim { it <= ' ' }.isNotEmpty()) {
            osmMarker.setTextIcon(marker.label)
        } else if (marker.iconUrl != null) {
            try {
                val bmp = createBitmapFromUrl(marker.iconUrl)
                osmMarker.icon = BitmapDrawable(resources, bmp)
            } catch (e: Exception) { // TODO: 6/1/19 Remove this when you are sure the marker url is pinging
            }
        } else if (marker.color != null) {
            osmMarker.icon = getMarkerIcon(marker.color)
        } else if (marker.size != null && marker.size > 0) {
            val bmp = MapUtilities.getBitmapFromVectorDrawable(context, marker.resId, MapUtilities.dpToPx(context, marker.size), marker.color)
            osmMarker.icon = BitmapDrawable(resources, bmp)
        } else {
            osmMarker.icon = ContextCompat.getDrawable(context, marker.resId)
        }
        osmMarker.setOnMarkerClickListener(this)
        osmMarker.setOnMarkerDragListener(this)
        overlays.add(osmMarker)
       invalidate()
        return osmMarker
    }

PFA url of video
https://drive.google.com/file/d/1RK0O1cLR6Vk7xtCfTlcsUN-rAa31_X_d/view?usp=sharing
Version of osmdroid the issue relates to:
6.1.5

That shouldn't be the case with the latest osmdroid code (you say you're testing with 6.1.5).

yes I m testing with version 6.1.5

That's my point: now it's 6.1.6 ou 6.1.7.

Any luck with a higher version?
I don't speak kotlin but it looks like for some reason you don't use the standard way to draw Markers. My suggestions: just add a Marker to the MapView overlays, et voilà.
Or perhaps there's something I've missed.

Updating to 6.1.6 seems to be working..still testing for different scenarios


Question on passing a string to query

Hey there,
I'd like to point query to my manifest file and then use Fingerprint::js on my my JS file. Unfortunately, that doesn't seem to work. The generated src attribute contains the path, but without the filename of my JS like assets/js/ instead of assets/js/main-somehash.js.
In my config.php, I'm doing this:
    'bnomei.fingerprint.query' => kirby()->root('assets') . '/manifest.json',

Inside Fingerprint.php, line 76, when dumping $this->option('query'), I'm getting the path to my kirby folder /assets/manifest.json instead of what I passed (see above).
??
// Edit:
My manifest.json looks like this:
{
  "main.css": "main-8660347533.css",
  "main.js": "main-3883a30b2d.js",
  "main.min.css": "main-8f550e0370.min.css",
  "main.min.js": "main-83e06e8ea7.min.js"
}

Yep, inside the hash() function, $query equals /path/to/vendor/getkirby/assets/manifest.json, but I passed my own assets folder (see above)?!

This seems to be a general issue, so I asked the forum:
https://forum.getkirby.com/t/problem-with-kirby-being-passed-to-config-option/22754


Neoverse V1 build error with "arch=arm64-v8.2-a-sve"

Output of 'strings libarm_compute.so | grep arm_compute_version':
arm_compute_version=v22.02 Git hash=8f587de9214dbc3aee4ff4eeb2ede66747769b19
Platform: aws c7g
Operating System: ubuntu 18.04.6 LTS

Problem description:
I can build successfully with 'arch=arm64-v8.2-a'; but got error with "arch=arm64-v8.2-a-sve" like below, what's the problem?
cc1plus: error: invalid feature modifier in ‘-march=armv8.2-a+sve+fp16+dotprod’

Hi @taosun1
Your toolchain does not support sve.
Can you please share the output of the following command aarch64-linux-gnu-g++ --version ?
Hope this helps.

@morgolock thanks, I finally built successfully inside this container https://hub.docker.com/r/armswdev/tensorflow-arm-neoverse. I guess we can close this issue. Earlier my host complier version is:
aarch64-linux-gnu-g++ (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


feature: Remove the usage of workspace hierarchy in KS

In general not all Space providers support space hierarchy. KS is using space hierarchy just for better organization. It was decided that the Space framework will not support hierarchy and therefore we need to remove this from KS. This is mainly a documentation/user instructions change.

Implemented by https://github.com/kubestellar/kubestellar/pull/1015


Add support for up to Django 3.1 & Python 3.9

Add support to Django 2.2 through Django 3.1 as well as Python 3.8 and 3.9 according to the list of supported versions.
Feature or Bugfix

Feature

Purpose
The postgresql_psycopg2 module is removed in Django 3.0 which prevents this library to be used with Django > 2.2. This change should fix it.
Issues
Might want to drop Python 2.x and Django 1.x as mentioned in #50

I'll review here after PR #71 is resolved. Thanks for your contribution!

This was also fixed in #72, my apologies that I hadn't seen this PR before.

This was also fixed in #72, my apologies that I hadn't seen this PR before.

Now I've released 2.0.0. Thanks for your contribution!
https://pypi.org/project/django-redshift-backend/2.0.0/

Now I've released 2.0.0. Thanks for your contribution!
https://pypi.org/project/django-redshift-backend/2.0.0/


Add ptr method for Slice

PR is simple, but it has a lot of style fixes.
This is the last synchronization from the Mir library because the basic API become stable.
ndslice will be removed from Mir when LDC get DMD front-end 2.072.

This is the last synchronization from the Mir library because the basic API become stable.

I might throw in isSlice later today ;-)
As always, this change comes from Mir - so I already reviewed or proposed the changes, hence LGTM!

This is the last synchronization from the Mir library because the basic API become stable.
I might throw in isSlice later today ;-)

This can be added directly to Phobos. However I don't think that we need this alias right now in Phobos

LGTM too

Auto-merge toggled on


FIX: Shapely dependence failing

https://github.com/ansys/pyedb/blame/870ab6031b5c1b7c6b54bdfd0aff29da077969aa/src/pyedb/common/nets.py#L5 imports shapely but this dependency is listed as a test-only dependency in pyproject.toml, leading to a failure if the tests dependency group is not installed.
closing #925

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.60%. Comparing base (870ab60) to head (7ee6392).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #927   +/-   ##
=======================================
  Coverage   82.60%   82.60%
=======================================
  Files         160      160
  Lines       21055    21055
=======================================
  Hits        17392    17392
  Misses       3663     3663


DRILL-6624: Fix loss of the table row type when the same schema name …

…was specified as single path and as a complex path in the same query

@vdiravka, could you please take a look?


fix(raw): Avoid buffer overrun for flip direction cases

If you are looping i over range [0,width), and want index to go the other direction, you need index = width - 1 - i, not index = width - i.
Identified by Sonar static analysis.

@Shootfast I would love your opinion on this.

LGTM!


processor.Close is blocked by SourceManager.Close

What did you do?
Rolling upgrade TiDB and TiCDC cluster.
Changefeed lag is increasing and TiCDC OOM due to processor.Close is blocked between
https://github.com/pingcap/tiflow/blob/40ba4175a57a45d5facabe1e8f876368ca3a9b59/cdc/processor/processor.go#L958-L971
Because there is a log "Processor try to close source manager" but no "Processor closed source manager successfully" or "Failed to close source manager".
It also causes OOM on agent receiving message.
What did you expect to see?
Lag is steady and no OOM.
What did you see instead?
Changefeed lag is increasing and TiCDC OOM.
Versions of the cluster
TiCDC version (execute cdc version):
40ba4175a57a45d5facabe1e8f876368ca3a9b59

/severity critical

Could you please provide cdc logs @AkiraXie


Do not load url templatetag in templates

We had this warning:

RemovedInDjango19Warning: Loading the url tag from the future
library is deprecated and will be removed in Django 1.9. Use the
default url tag instead.

Hi @wo0dyn !
As the url tag is part of the built-in templatetags (django/template/defaulttags.py), there should be nothing to import.
Rendering this template would raise an error like 'url' is not a registered library.
You can simply get rid of the load url.

Oh s…! Thank you very much @hsmett. I will amend the PR.

You may add some tests? :p

You may add some tests? :p

Spotted. 👍  I thought it was too simple to write a test… My mistake. 😉

Is it still OK for you guys? @hsmett @Natim

Yes it is good to me, also it is generally a bad idea to squash commit because it removes all the work of collaboration that we have been doing. Your work, then @hsmett reviews and then my reviews doesn't appear if you squash the commit. While it was a process that lasted 17 hours, we don't have any track of it anymore.

it is generally a bad idea to squash commits because it removes all the work of collaboration that we have been doing

Oops, sorry about that. 😕
FYI, here is a small set of commits from my reflog prior rebasing:

17bf316 commit (amend): fixup! Do not load url templatetag in templates
71fe4ac commit: fixup! Do not load url templatetag in templates
56c7ebf commit: fixup! Do not load url templatetag in templates
80792e2 commit: fixup! Do not load url templatetag in templates

It isn't a big deal I think.

More about that has been written by @benoitbryon back in the days

Thanks for the blog posts. Will read that later.


Update publications.php

What I really wanted to do was to have this generate a URL that reported the field $properties["name"], so that it is easier for a search engine to pick up on. For this purpose, it would be better for the name to contain hyphens instead of underscores...
Also, on the home page, the feed reporting the latest publications should list them in chronological order, instead of upload date.
Thank you!
M.

Using the name field is a bit complicated as it may contain lots of non-url-friendly letters, and there's no unique restriction on it, two publications can share the same name. Maybe we should change the way the admin page works so that the administrator manages the url name manually instead?

Ok, whatever works, I'm in your hands. :)

By the way, for some reason Google cannot see the meta verification tag... Shall I send you the html file to upload, so I can verify fraudacademy too?


Intermittent: single_player_single_device_end_to_end_workflow, writes_do_not_block_reads

I've seen this happen occasionally when running tests locally.
test single_player_single_device_end_to_end_workflow has been running for over 60 seconds
test writes_do_not_block_reads has been running for over 60 seconds

Caused when running multiple tests in rust/noosphere/tests/integration.rs from the failing cases each first call to sphere_channel().mutable().save(None), ultimately calling sphere_context.db_mut().flush(). The initial tokio::join in SphereDb<S>::flush never completes in either test (intermittently).

Due to sled's [flush_async()](https://docs.rs/sled/latest/sled/struct.Tree.html#method.flush_async) causing deadlocks. This was fixed in January 2021, but there hasn't been a release since. Using the main branch of sled, I'm unable to repro the failures over a reasonable amount of iterations.


API: Changes to content documents are often reverted after saving

The API sometimes / often backdates changes to the previous version of the content document.
This is probably happening when changes to posts/tags are causing an update to the content documents (replicating fields from the post / tag to the content documents), and arriving out of sequence at the client.

@ivanslabbert I want to take this one, but how can i reproduce this ?

#217 should be fixed by this, but I need to test if this issue is solved


#361 - custom pause container image support

Issue #, if available:
fixes #361
Description of changes:
Support passing in custom pause container.

@mogren thanks, any idea when a new ami would be baked with this in?


Migrate to CircleCI

This library should be migrated to CircleCI

CircleCI is already integrate for this project, right?

looks like yes.


LicenseFinder fails build of "aruba" on jRuby

Hey @kdykeman,
we get build failures on Travis' jRuby due to a dependency of LicenseFinder. I'm still investigating to give you some more details.
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
current directory:
/home/travis/.rvm/gems/jruby-<IP_ADDRESS>/gems/yajl-ruby-1.3.0/ext/yajl
/home/travis/.rvm/rubies/jruby-<IP_ADDRESS>/bin/jruby -r
./siteconf20170724-6662-1vmnrij.rb extconf.rb
creating Makefile

In Gemfile:
  license_finder was resolved to 3.0.1, which depends on
    yajl-ruby

@maxmeyer we just released version 3.0.2 of LicenseFinder today which should remove the yajl-ruby dependency. It also has numerous fixes for other issues in 3.0.1. Give the new version a shot and re-open this issue if you're still having the same problem.

@kdykeman Great! I just started the build. This will take a while. Thanks!


Add just one more theme

I have plans to implement just one more theme based on some popular color scheme. I need your help. Please give me your suggestions and vote for existing ones :wink:
Expected Behavior

This theme will use colors of the winning color scheme :heart:

Boxy Cyanide
Original: https://github.com/lefoy/cyanide-theme
Requested by @babygau in #24

Oh, it has to be solarized. Personally I use the Monokai scheme (and the boxy monokai theme is by far the best) and sometimes the solarized scheme.  The themes available for solarized are not particularly good.
http://ethanschoonover.com/solarized

Maybe Facebook theme :)
https://github.com/mbixby/facebook-color-scheme

The voting is closed. I'll add Solarized Dark & Light themes in the 4.0.0. I have no plans to add more themes in the near future. That's why you are free to fork :wink:

Closed by<PHONE_NUMBER>ce4350bb633514ccff44f42d8fedfa and ed123b7c93142ab80e12bbe0abae1a2301cd6628.


Module not found on AWS node 14x

First of all, Merry Christmas for you
Possible install-time or require-time problem
I have researched besides only the documentation, several other posts and tried installing with many different commands.
The runtime is node 14x at AWS lambda.
The error message says it cant find that module, but I went in the sharp dir in node_modules and it is there.
tried with the following commands:
npm install --arch=x64 --platform=linux --target=14x sharp
npm install --arch=x64 --platform=linux sharp
SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install --arch=x64 --platform=linux --libc=glibc sharp
"Error: ",
        "Something went wrong installing the \"sharp\" module",
        "",
        "Cannot find module '../build/Release/sharp-linux-x64.node'"

[x] I have read the documentation relating to installation.
[x] I have ensured that the architecture and platform of Node.js used for npm install is the same as the architecture and platform of Node.js used at runtime.

Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.
If you are using another package which depends on a version of sharp that is not the latest, please open an issue against that package instead.
Is this a problem with filesystem permissions?
NO
If you are using npm v6 or earlier and installing as a root or sudo user, have you tried with the npm install --unsafe-perm flag?
Not applicable
If you are using npm v7 or later, does the user running npm install own the directory it is run in?
Yes
If you are using the ignore-scripts feature of npm, have you tried with the npm install --ignore-scripts=false flag?
Yes
What is the complete output of running npm install --verbose --foreground-scripts sharp in an empty directory?

npm verb cli [
npm verb cli   '/home/lschulzes/.nvm/versions/node/v16.13.0/bin/node',
npm verb cli   '/home/lschulzes/.nvm/versions/node/v16.13.0/bin/npm',
npm verb cli   'install',
npm verb cli   '--verbose',
npm verb cli   '--foreground-scripts',
npm verb cli   'sharp'
npm verb cli ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm timing npm:load:whichnode Completed in 0ms
npm timing config:load:defaults Completed in 1ms
npm timing config:load:file:/home/lschulzes/.nvm/versions/node/v16.13.0/lib/node_modules/npm/npmrc Completed in 2ms
npm timing config:load:builtin Completed in 2ms
npm timing config:load:cli Completed in 1ms
npm timing config:load:env Completed in 1ms
npm timing config:load:project Completed in 0ms
npm timing config:load:file:/home/lschulzes/.npmrc Completed in 1ms
npm timing config:load:user Completed in 1ms
npm timing config:load:file:/home/lschulzes/.nvm/versions/node/v16.13.0/etc/npmrc Completed in 1ms
npm timing config:load:global Completed in 1ms
npm timing config:load:validate Completed in 0ms
npm timing config:load:credentials Completed in 0ms
npm timing config:load:setEnvs Completed in 1ms
npm timing config:load Completed in 8ms
npm timing npm:load:configload Completed in 8ms
npm timing npm:load:setTitle Completed in 0ms
npm timing npm:load:setupLog Completed in 0ms
npm timing config:load:flatten Completed in 2ms
npm timing npm:load:cleanupLog Completed in 2ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load:projectScope Completed in 0ms
npm timing npm:load Completed in 15ms
npm timing arborist:ctor Completed in 0ms
npm timing idealTree:init Completed in 7ms
npm timing idealTree:userRequests Completed in 2ms
npm http fetch GET 200 https://registry.npmjs.org/sharp 11ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/color 16ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/tunnel-agent 15ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/detect-libc 18ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/node-addon-api 17ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/simple-get 17ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/prebuild-install 18ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/tar-fs 18ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/semver 20ms (cache hit)
npm timing idealTree:#root Completed in 42ms
npm http fetch GET 200 https://registry.npmjs.org/color-string 27ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/minimist 26ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/github-from-package 27ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/pump 26ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/color-convert 29ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/expand-template 28ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/decompress-response 27ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/napi-build-utils 28ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/once 27ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/chownr 26ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/mkdirp-classic 29ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/lru-cache 29ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/node-abi 31ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/simple-concat 30ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/safe-buffer 28ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/rc 32ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/tar-stream 30ms (cache hit)
npm timing idealTree:node_modules/sharp Completed in 49ms
npm http fetch GET 200 https://registry.npmjs.org/color-name 3ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/simple-swizzle 3ms (cache hit)
npm timing idealTree:node_modules/color Completed in 6ms
npm timing idealTree:node_modules/color-convert Completed in 1ms
npm timing idealTree:node_modules/color-name Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/is-arrayish 4ms (cache hit)
npm timing idealTree:node_modules/color-string Completed in 5ms
npm timing idealTree:node_modules/detect-libc Completed in 0ms
npm timing idealTree:node_modules/node-addon-api Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/ini 6ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/end-of-stream 7ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/strip-json-comments 6ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/deep-extend 7ms (cache hit)
npm timing idealTree:node_modules/prebuild-install Completed in 14ms
npm timing idealTree:node_modules/expand-template Completed in 0ms
npm timing idealTree:node_modules/github-from-package Completed in 0ms
npm timing idealTree:node_modules/minimist Completed in 0ms
npm timing idealTree:node_modules/mkdirp-classic Completed in 0ms
npm timing idealTree:node_modules/napi-build-utils Completed in 0ms
npm timing idealTree:node_modules/node-abi Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/wrappy 3ms (cache hit)
npm timing idealTree:node_modules/pump Completed in 6ms
npm timing idealTree:node_modules/end-of-stream Completed in 0ms
npm timing idealTree:node_modules/once Completed in 0ms
npm timing idealTree:node_modules/rc Completed in 2ms
npm timing idealTree:node_modules/deep-extend Completed in 0ms
npm timing idealTree:node_modules/ini Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/yallist 2ms (cache hit)
npm timing idealTree:node_modules/semver Completed in 4ms
npm timing idealTree:node_modules/lru-cache Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/mimic-response 3ms (cache hit)
npm timing idealTree:node_modules/simple-get Completed in 4ms
npm timing idealTree:node_modules/decompress-response Completed in 1ms
npm timing idealTree:node_modules/mimic-response Completed in 0ms
npm timing idealTree:node_modules/simple-concat Completed in 0ms
npm timing idealTree:node_modules/simple-swizzle Completed in 1ms
npm timing idealTree:node_modules/is-arrayish Completed in 0ms
npm timing idealTree:node_modules/strip-json-comments Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/bl 8ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/fs-constants 9ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/inherits 9ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/readable-stream 8ms (cache hit)
npm timing idealTree:node_modules/tar-fs Completed in 14ms
npm timing idealTree:node_modules/chownr Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/string_decoder 4ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/util-deprecate 4ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/buffer 6ms (cache hit)
npm timing idealTree:node_modules/tar-stream Completed in 10ms
npm http fetch GET 200 https://registry.npmjs.org/base64-js 4ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/ieee754 4ms (cache hit)
npm timing idealTree:node_modules/bl Completed in 6ms
npm timing idealTree:node_modules/buffer Completed in 1ms
npm timing idealTree:node_modules/base64-js Completed in 0ms
npm timing idealTree:node_modules/fs-constants Completed in 0ms
npm timing idealTree:node_modules/ieee754 Completed in 0ms
npm timing idealTree:node_modules/inherits Completed in 0ms
npm timing idealTree:node_modules/readable-stream Completed in 1ms
npm timing idealTree:node_modules/string_decoder Completed in 1ms
npm timing idealTree:node_modules/safe-buffer Completed in 0ms
npm timing idealTree:node_modules/tunnel-agent Completed in 0ms
npm timing idealTree:node_modules/util-deprecate Completed in 0ms
npm timing idealTree:node_modules/wrappy Completed in 0ms
npm timing idealTree:node_modules/yallist Completed in 0ms
npm timing idealTree:buildDeps Completed in 174ms
npm timing idealTree:fixDepFlags Completed in 1ms
npm timing idealTree Completed in 185ms
npm timing reify:loadTrees Completed in 185ms
npm timing reify:diffTrees Completed in 1ms
npm timing reify:retireShallow Completed in 0ms
npm timing reify:createSparse Completed in 5ms
npm timing reify:loadBundles Completed in 0ms
npm timing reifyNode:node_modules/chownr Completed in 95ms
npm timing reifyNode:node_modules/strip-json-comments Completed in 94ms
npm timing reifyNode:node_modules/ini Completed in 95ms
npm timing reifyNode:node_modules/once Completed in 95ms
npm timing reifyNode:node_modules/wrappy Completed in 95ms
npm timing reifyNode:node_modules/end-of-stream Completed in 95ms
npm timing reifyNode:node_modules/simple-swizzle Completed in 96ms
npm timing reifyNode:node_modules/color-name Completed in 96ms
npm timing reifyNode:node_modules/color-string Completed in 96ms
npm timing reifyNode:node_modules/mkdirp-classic Completed in 96ms
npm timing reifyNode:node_modules/ieee754 Completed in 98ms
npm timing reifyNode:node_modules/inherits Completed in 98ms
npm timing reifyNode:node_modules/fs-constants Completed in 98ms
npm timing reifyNode:node_modules/mimic-response Completed in 98ms
npm timing reifyNode:node_modules/decompress-response Completed in 98ms
npm timing reifyNode:node_modules/lru-cache Completed in 98ms
npm timing reifyNode:node_modules/tunnel-agent Completed in 99ms
npm timing reifyNode:node_modules/util-deprecate Completed in 102ms
npm timing reifyNode:node_modules/string_decoder Completed in 102ms
npm timing reifyNode:node_modules/base64-js Completed in 102ms
npm timing reifyNode:node_modules/yallist Completed in 102ms
npm timing reifyNode:node_modules/expand-template Completed in 102ms
npm timing reifyNode:node_modules/simple-concat Completed in 103ms
npm timing reifyNode:node_modules/deep-extend Completed in 103ms
npm timing reifyNode:node_modules/pump Completed in 103ms
npm timing reifyNode:node_modules/napi-build-utils Completed in 103ms
npm timing reifyNode:node_modules/color Completed in 103ms
npm timing reifyNode:node_modules/safe-buffer Completed in 106ms
npm timing reifyNode:node_modules/is-arrayish Completed in 105ms
npm timing reifyNode:node_modules/color-convert Completed in 105ms
npm timing reifyNode:node_modules/detect-libc Completed in 105ms
npm timing reifyNode:node_modules/tar-stream Completed in 108ms
npm timing reifyNode:node_modules/simple-get Completed in 107ms
npm timing reifyNode:node_modules/buffer Completed in 109ms
npm timing reifyNode:node_modules/rc Completed in 109ms
npm timing reifyNode:node_modules/bl Completed in 111ms
npm timing reifyNode:node_modules/github-from-package Completed in 110ms
npm timing reifyNode:node_modules/prebuild-install Completed in 109ms
npm timing reifyNode:node_modules/node-abi Completed in 112ms
npm timing reifyNode:node_modules/minimist Completed in 116ms
npm timing reifyNode:node_modules/readable-stream Completed in 120ms
npm timing reifyNode:node_modules/node-addon-api Completed in 120ms
npm timing reifyNode:node_modules/tar-fs Completed in 120ms
npm timing reifyNode:node_modules/semver Completed in 122ms
npm timing reifyNode:node_modules/sharp Completed in 123ms
npm timing reify:unpack Completed in 127ms
npm timing reify:unretire Completed in 0ms
npm timing build:queue Completed in 2ms
npm timing build:link:node_modules/prebuild-install Completed in 2ms
npm timing build:link:node_modules/semver Completed in 1ms
npm timing build:link:node_modules/rc Completed in 1ms
npm timing build:link Completed in 2ms
npm info run<EMAIL_ADDRESS>install node_modules/sharp (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)

<EMAIL_ADDRESS>install
(node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)

sharp: Using cached /home/lschulzes/.npm/_libvips/libvips-8.13.3-linux-x64.tar.br
npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 394ms
npm timing auditReport:getReport Completed in 395ms
npm timing auditReport:init Completed in 0ms
npm timing reify:audit Completed in 396ms
sharp: Integrity check passed for linux-x64reify:audit Completed in 396ms
prebuild-install info begin Prebuild-install version 7.1.1pleted in 396ms
prebuild-install info looking for local prebuild @ prebuilds/sharp-v0.31.3-napi-v7-linux-x64.tar.gz
prebuild-install info looking for cached prebuild @ /home/lschulzes/.npm/_prebuilds/3edfda-sharp-v0.31.3-napi-v7-linux-x64.tar.gz
prebuild-install info found cached prebuild
prebuild-install info unpacking @ /home/lschulzes/.npm/_prebuilds/3edfda-sharp-v0.31.3-napi-v7-linux-x64.tar.gz
prebuild-install info unpack resolved to /home/lschulzes/node_modules/sharp/build/Release/sharp-linux-x64.node
prebuild-install info install Successfully installed prebuilt binary!
npm info run<EMAIL_ADDRESS>install { code: 0, signal: null }
npm timing build:run:install:node_modules/sharp Completed in 635ms
npm timing build:run:install Completed in 636ms
npm timing build:deps Completed in 640ms
npm timing build Completed in 640ms
npm timing reify:build Completed in 640ms
npm timing reify:trash Completed in 0ms
npm timing reify:save Completed in 9ms
npm timing reify Completed in 981ms
added 45 packages, and audited 46 packages in 1s
10 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
npm timing command:install Completed in 985ms
npm verb exit 0
npm timing npm Completed in 1146ms
npm info ok

What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
System:
OS: Linux 5.15 Arch Linux
CPU: (6) x64 Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz
Memory: 17.36 GB / 31.27 GB
Container: Yes
Shell: 5.9 - /usr/bin/zsh
Binaries:
Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
Yarn: 1.22.19 - ~/.local/bin/yarn
npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm

The installation looks OK to me. Are you using any kind of code bundler (e.g. webpack, esbuild) that might be breaking/changing import/require paths?

Yes, I am using esbuld on the serverless.yml file with the following script:
  esbuild:
    packagerOptions:
      scripts:
        - rm -rf node_modules/sharp
        - npm install --arch=x64 --platform=linux sharp

Does your configuration also include the following?
  esbuild:
    external:
      - sharp

Please see https://sharp.pixelplumbing.com/install#esbuild

It worked, I didnt see, that, thank you!

aws lambda need layers FOLDER NAME ( nodejs ) than zip it upload on lambda layers . if your folder name not nodejs its not running on aws lambda layers .


Implement a leaderboard

Create a leaderboard UI and controller.
Leaderboard should include (#) Position in leaderboard, (Username) as @Username, (Score) in format 9,999,999.
Leaderboard should sort by score.
Use sql or printwriter for storing/retrieving data.

No leaderboard needed


Handle on('disconnect') event

What is the new or updated feature that you are suggesting?
MetaMask documents a disconnect event: https://docs.metamask.io/wallet/reference/provider-api/#disconnect
which seemingly happens only in case of network connectivity issues.
I don't have a specific reproducible case in mind, but maybe the MetaMaskProvider could subscribe to that event and update the state accordingly.
Why should this feature be included?
Handle disconnection error properly

Thanks for this other issue @serejke!
It looks interesting indeed! I think a new field rpcProviderConnected in the state may be interesting to add in order to track the health of the underlying RCP provider
I'm currently in holidays but I'll take a look in the coming weeks :)

Hey!
Sorry for the late news, I did not take the time to work on this!
Unfortunately I am no longer maintaining this package so I'll close this issue. I linked the alternatives in the README.
Thanks again for this issue! Have a great day!


Error upgrading to 0.11.0

I attempted to migrate my sqlite database to 0.11 and am having some problems. The first was needing to use the caravel db stamp f162a1dea4c4 work around. I then performed a caravel db upgrade
The last bits of the upgrade log show a few warnings:
INFO  [alembic.runtime.migration] Context impl SQLiteImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
INFO  [alembic.runtime.migration] Running upgrade f162a1dea4c4 -> ad82a75afd82, Update models to support storing the queries.
/usr/lib/python3.5/site-packages/alembic/util/messaging.py:69: UserWarning: Skipping unsupported ALTER for creation of implicit constraint
  warnings.warn(msg)
INFO  [alembic.runtime.migration] Running upgrade ad82a75afd82 -> 3c3ffe173e4f, add_sql_string_to_table
INFO  [alembic.runtime.migration] Running upgrade 3c3ffe173e4f -> 41f6a59a61f2, database options for sql lab
INFO  [alembic.runtime.migration] Running upgrade 41f6a59a61f2 -> 4500485bde7d, allow_run_sync_async
INFO  [alembic.runtime.migration] Running upgrade 4500485bde7d -> 65903709c321, allow_dml
INFO  [alembic.runtime.migration] Running upgrade 41f6a59a61f2 -> 33d996bcc382
INFO  [alembic.runtime.migration] Running upgrade 33d996bcc382, 65903709c321 -> b347b202819b, empty message
INFO  [alembic.runtime.migration] Running upgrade b347b202819b -> 5e4a03ef0bf0, Add access_request table to manage requests to access datastores.
INFO  [alembic.runtime.migration] Running upgrade 5e4a03ef0bf0 -> eca4694defa7, sqllab_setting_defaults
INFO  [alembic.runtime.migration] Running upgrade eca4694defa7 -> ab3d66c4246e, add_cache_timeout_to_druid_cluster
INFO  [alembic.runtime.migration] Running upgrade eca4694defa7 -> 3b626e2a6783, Sync DB with the models.py.
WARNI [root] No such constraint: 'slices_ibfk_1'
WARNI [root] Constraint must have a name
WARNI [root] No such index: 'table_name'
INFO  [alembic.runtime.migration] Running upgrade 3b626e2a6783, ab3d66c4246e -> ef8843b41dac, empty message

I am able to get onto my caravel instance and see a list of dashboard. However if I look at any tables or slices, I see the following error
(sqlite3.OperationalError) no such column: sql_metrics.d3format [SQL: 'SELECT
sql_metrics.created_on AS sql_metrics_created_on, sql_metrics.changed_on AS
sql_metrics_changed_on, sql_metrics.id AS sql_metrics_id, sql_metrics.metric_name AS
sql_metrics_metric_name, sql_metrics.verbose_name AS sql_metrics_verbose_name,
sql_metrics.metric_type AS sql_metrics_metric_type, sql_metrics.table_id AS
sql_metrics_table_id, sql_metrics.expression AS sql_metrics_expression, sql_metrics.description
AS sql_metrics_description, sql_metrics.is_restricted AS sql_metrics_is_restricted,
sql_metrics.d3format AS sql_metrics_d3format, sql_metrics.changed_by_fk AS
sql_metrics_changed_by_fk, sql_metrics.created_by_fk AS sql_metrics_created_by_fk \n
FROM sql_metrics \nWHERE ? = sql_metrics.table_id'] [parameters: (19,)]

Any thoughts on what I might do to properly migrate from 0.10.0 to 0.11.0? Please let me know if I can provide any additional information and I will happily do so.

Ran into this problem myself... albeit a slightly different flavour and am running MariaDB.
Not sure how easy it is to query/update SQLite3 but doing this might help:
https://github.com/amancevice/caravel/issues/14

@kingo55 Thank you for the pointer. I've tried that but am still having a similar issue. First for others, sqlite3 does not support alter removing columns, so I had to create a new table, copy the data over, remove the old table, then move the new table back by doing the following:
CREATE TABLE "table_columns_new" (
created_on DATETIME NOT NULL,
changed_on DATETIME NOT NULL,
id INTEGER NOT NULL,
table_id INTEGER,
column_name VARCHAR(255),
is_dttm BOOLEAN,
is_active BOOLEAN,
type VARCHAR(32),
groupby BOOLEAN,
count_distinct BOOLEAN,
sum BOOLEAN,
max BOOLEAN,
min BOOLEAN,
filterable BOOLEAN,
description TEXT,
created_by_fk INTEGER,
changed_by_fk INTEGER,
expression TEXT,
verbose_name VARCHAR(1024),
PRIMARY KEY (id),
CHECK (is_dttm IN (0, 1)),
CHECK (is_active IN (0, 1)),
CHECK (groupby IN (0, 1)),
CHECK (count_distinct IN (0, 1)),
CHECK (sum IN (0, 1)),
CHECK (max IN (0, 1)),
CHECK (min IN (0, 1)),
CHECK (filterable IN (0, 1)),
FOREIGN KEY(created_by_fk) REFERENCES ab_user (id),
FOREIGN KEY(changed_by_fk) REFERENCES ab_user (id),
FOREIGN KEY(table_id) REFERENCES tables (id)
);

insert into table_columns_new select created_on, changed_on, id, table_id, column_name, is_dttm, is_active, type, groupby, count_distinct, sum, max, min, filterable, description, created_by_fk, changed_by_fk, expression, verbose_name from table_columns;

drop table table_columns;

alter table table_columns_new rename to table_columns;

I then did a caravel db upgrade and a caravel init
The init gives me the following error:
2016-10-11 14:57:05,082:INFO:root:Creating database reference
2016-10-11 14:57:05,087:INFO:root:sqlite:////home/caravel/db/caravel.db
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_context
    context)
  File "/usr/lib/python3.5/site-packages/sqlalchemy/engine/default.py", line 450, in do_execute
    cursor.execute(statement, parameters)
sqlite3.OperationalError: no such column: sql_metrics.d3format

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/bin/caravel", line 155, in <module>
    manager.run()
  File "/usr/lib/python3.5/site-packages/flask_script/__init__.py", line 412, in run
    result = self.handle(sys.argv[0], sys.argv[1:])
  File "/usr/lib/python3.5/site-packages/flask_script/__init__.py", line 383, in handle
    res = handle(*args, **config)
  File "/usr/lib/python3.5/site-packages/flask_script/commands.py", line 216, in __call__
    return self.run(*args, **kwargs)
  File "/usr/bin/caravel", line 64, in init
    utils.init(caravel)
  File "/usr/lib/python3.5/site-packages/caravel/utils.py", line 295, in init
    init_metrics_perm(caravel)
  File "/usr/lib/python3.5/site-packages/caravel/utils.py", line 312, in init_metrics_perm
    metrics += list(db.session.query(model).all())
  File "/usr/lib/python3.5/site-packages/sqlalchemy/orm/query.py", line 2613, in all
    return list(self)
  File "/usr/lib/python3.5/site-packages/sqlalchemy/orm/query.py", line 2761, in __iter__
    return self._execute_and_instances(context)
  File "/usr/lib/python3.5/site-packages/sqlalchemy/orm/query.py", line 2776, in _execute_and_instances
    result = conn.execute(querycontext.statement, self._params)
  File "/usr/lib/python3.5/site-packages/sqlalchemy/engine/base.py", line 914, in execute
    return meth(self, multiparams, params)
  File "/usr/lib/python3.5/site-packages/sqlalchemy/sql/elements.py", line 323, in _execute_on_connection
    return connection._execute_clauseelement(self, multiparams, params)
  File "/usr/lib/python3.5/site-packages/sqlalchemy/engine/base.py", line 1010, in _execute_clauseelement
    compiled_sql, distilled_params
  File "/usr/lib/python3.5/site-packages/sqlalchemy/engine/base.py", line 1146, in _execute_context
    context)
  File "/usr/lib/python3.5/site-packages/sqlalchemy/engine/base.py", line 1341, in _handle_dbapi_exception
    exc_info
  File "/usr/lib/python3.5/site-packages/sqlalchemy/util/compat.py", line 202, in raise_from_cause
    reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File "/usr/lib/python3.5/site-packages/sqlalchemy/util/compat.py", line 185, in reraise
    raise value.with_traceback(tb)
  File "/usr/lib/python3.5/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_context
    context)
  File "/usr/lib/python3.5/site-packages/sqlalchemy/engine/default.py", line 450, in do_execute
    cursor.execute(statement, parameters)
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such column: sql_metrics.d3format [SQL: 'SELECT sql_metrics.created_on AS sql_metrics_created_on, sql_metrics.changed_on AS sql_metrics_changed_on, sql_metrics.id AS sql_metrics_id, sql_metrics.metric_name AS sql_metrics_metric_name, sql_metrics.verbose_name AS sql_metrics_verbose_name, sql_metrics.metric_type AS sql_metrics_metric_type, sql_metrics.table_id AS sql_metrics_table_id, sql_metrics.expression AS sql_metrics_expression, sql_metrics.description AS sql_metrics_description, sql_metrics.is_restricted AS sql_metrics_is_restricted, sql_metrics.d3format AS sql_metrics_d3format, sql_metrics.changed_by_fk AS sql_metrics_changed_by_fk, sql_metrics.created_by_fk AS sql_metrics_created_by_fk \nFROM sql_metrics']

In app if I try to look at a table I get the following error (as part of a stack trace):
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_context
    context)
  File "/usr/lib/python3.5/site-packages/sqlalchemy/engine/default.py", line 450, in do_execute
    cursor.execute(statement, parameters)
sqlite3.OperationalError: no such column: table_columns.python_date_format

[Not included stack trace, available upon request]

sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such column:
table_columns.python_date_format [SQL: 'SELECT table_columns.created_on AS
table_columns_created_on, table_columns.changed_on AS table_columns_changed_on,
table_columns.id AS table_columns_id, table_columns.table_id AS table_columns_table_id,
table_columns.column_name AS table_columns_column_name, table_columns.verbose_name AS
table_columns_verbose_name, table_columns.is_dttm AS table_columns_is_dttm,
table_columns.is_active AS table_columns_is_active, table_columns.type AS table_columns_type,
table_columns.groupby AS table_columns_groupby, table_columns.count_distinct AS
table_columns_count_distinct, table_columns.sum AS table_columns_sum, table_columns.max AS
table_columns_max, table_columns.min AS table_columns_min, table_columns.filterable AS
table_columns_filterable, table_columns.expression AS table_columns_expression,
table_columns.description AS table_columns_description, table_columns.python_date_format AS
table_columns_python_date_format, table_columns.database_expression AS
table_columns_database_expression, table_columns.changed_by_fk AS
table_columns_changed_by_fk, table_columns.created_by_fk AS table_columns_created_by_fk
\nFROM table_columns']

If I look at any dashboard I see the following where any slice should be:
(sqlite3.OperationalError) no such column: sql_metrics.d3format [SQL: 'SELECT
sql_metrics.created_on AS sql_metrics_created_on, sql_metrics.changed_on AS
sql_metrics_changed_on, sql_metrics.id AS sql_metrics_id, sql_metrics.metric_name AS
sql_metrics_metric_name, sql_metrics.verbose_name AS sql_metrics_verbose_name,
sql_metrics.metric_type AS sql_metrics_metric_type, sql_metrics.table_id AS
sql_metrics_table_id, sql_metrics.expression AS sql_metrics_expression, sql_metrics.description
AS sql_metrics_description, sql_metrics.is_restricted AS sql_metrics_is_restricted,
sql_metrics.d3format AS sql_metrics_d3format, sql_metrics.changed_by_fk AS
sql_metrics_changed_by_fk, sql_metrics.created_by_fk AS sql_metrics_created_by_fk \nFROM
sql_metrics \nWHERE ? = sql_metrics.table_id'] [parameters: (19,)]

update: By going through the above process, but omitting the caravel db stamp f162a1dea4c4 I get much further. Everything seems ok, except that all of tables are saying that the tables don't exist in the database. Looking into that now.

It looks like the issue is that I have to set the Datetime Format on my temporal columns again as otherwise no records show up.
I'll mark this closed now.

@jwthomp what was the rational for stamping f162a1dea4c4? Looks like this resulted in skipping needed migrations.

btw I wouldn't worry about the warning, it's coming from a db migration script

@mistercrunch My recollection is that when I was first trying to fix this I was seeing the alter error in https://github.com/airbnb/caravel/issues/817 so I tried that fix.
I'm guessing I misread the error.


Service worker installation failed

Hi @farrukhsheikh248, this is the expected behavior when a request for a precache asset fails with a 404. In this case the service worker installation should also fail.

Hey @jeffposnick
I've migrated from v3 to v4, using the workbox-window(CDN) and workbox-webpack-plugin,
I have the same issue as above, the service worker installation is failing for some reason. Could you please help me know how to fix this.

Any Update ?


Logger

Tests should pass once we merge https://github.com/alantech/anycloud/pull/32

@aguillenv you'll need to update the Cargo.lock to the latest anycloud once the other PR is landed before any of these tests can pass: https://github.com/alantech/alan/pull/459/checks?check_run_id=2185186570


fix: replace v-tooltip with vue-tippy popover

fix mew-tooltip UI bugs
replace v-tooltip with vue-tippy

https://user-images.githubusercontent.com/9893774/173556468-2627fc87-deec-4554-a4f1-cb2cafc57fab.mp4
https://user-images.githubusercontent.com/9893774/173556621-0ebc1374-7038-4a61-a28f-22eadf61c1e5.mp4

it looks fine on storybook. Can you make sure it’s not one of the styles on v6 causing this? Thanks!

it looks fine on storybook. Can you make sure it’s not one of the styles on v6 causing this? Thanks!


Update Upgrade docs to list breaking changes for 0.14.x

Summary
The changelog for Kong 0.14.x mentions breaking changes to the /consumers endpoint as a result of moving to the new DAO, as part of #3437
The specific breaking changes are not listed in the CHANGELOG or the UPGRADE document.
Steps To Fix
Please update the documentation to include the specific breaking changes.

i am taking this issue

Check this PR please,
I added the missing breaking changes as mentioned earlier
https://github.com/Kong/kong/pull/5365#issue-355966730

Closed by #5365

BTW - nice to see you, @ukiahsmith :)!


Android users

Android chrome isn't helping when we try and access it the user experience isn't pleasant please help

There is an app that might be better for you: https://play.google.com/store/apps/details?id=dularion.streama
But we still might look at this.

I know of the app thanks anyway

I tested the app and exactly this happed on android but in browser works well,

Just to be clear, are you saying that the issue in the screenshot is also happening on the android app and not just the phones browser?

Correct, I face the issue in screenshot on the app for Android.

The issue described originally is referring to the regular site, viewed in a browser, as can be seen by the address bar. For me the images display properly, @junnotpiper . What kind of content is this? manually added? or via tmdb?

the play button for the video and I couldn't see it (I got to know because of my knowledge on the desktop site)  is so small  and it's not mobile friendly