Embedded player is flickering inside its iframe

Describe the bug (required)
When embedding a stream being served by livepeer's platform in a webpage using the iframe, it is producing unwanted flickering.
See this video for evidence: https://youtu.be/8xBsQN5o6Mo
This issue is resolve if a user clicks "full screen" in which case it fills the frame it's embedded in, and stops flickering.
Expected behavior (required)
When the player is loaded up as part of a webpage, that it remains in the same place, and doesn't flicker.
To Reproduce (required)
Go to e.g. ethberlin.com/livestream
Device (required):

Device: Thinkpad
OS: Ubuntu 18.04.1
Browser: Chromium
Version: 68.0.3440.106 (Official Build) (64-bit)

Screenshots (optional)
https://youtu.be/8xBsQN5o6Mo

Hi @chrishobcroft! You can just add scrolling="no" to the iframe element. scrolling is actually a deprecated attribute, and is no longer officially supported by HTML5, but still works in all major browsers. A more elegant and up-to-date solution would be to use CSS: iframe { overflow: hidden; }

@chrishobcroft does that solve the issue? If so we can close this issue.

@chrishobcroft has this problem been solved by the suggestion? If so I would like to close this issue.

Yes please close it
On Fri, Sep 21, 2018 at 9:38 PM Randy Burrell<EMAIL_ADDRESS>wrote:

@chrishobcroft https://github.com/chrishobcroft has this problem been
solved by the suggestion? If so I would like to close this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/livepeer/livepeerjs/issues/202#issuecomment-423649211,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACHDK3B39Kr0rfGE6nx9XxCCBh5cZFINks5udUAhgaJpZM4WRyzj
.

--
Chris Hobcroft
Creative Director
Livepeer http://livepeer.org/
+4915163846782
<EMAIL_ADDRESS>@chrishobcroft http://www.twitter.com/chrishobcroft

Ok great.

Hey @Randy1Burrell, I don't think it's in Brave, but in Gitcoin. I will do what I can to remove it.

Yes, removing from Gitcoin


Whitelist HTML tags

Summary
I would like to whitelist some HTML tags so they can be rendered in the Viewer.
Version
2.2.0
Additional context
The main idea is to have a simple way to render a YouTube video. If I paste a YouTube link in the WYSIWYG editor, I will then transform it as an iframe using PHP. After that, when using the Viewer, I would like my iframe to be rendered.
Is there a way for doing this ? Or maybe it is a wrong way to do it... thanks for your help !

@Fl0ux I think the customHTMLSanitizer option will allow you to use the tags you need. By default, the Editor is sanitizing unnecessary tags, but using this option will not sanitize. So you can use tags like iframe that you need. Below is a usage example. (Note: Example of creating a viewer using the Editor's factory function)
import Editor from '@toast-ui/editor';

const editor = Editor.factory({
  el: document.querySelector('#editor'),
  height: '500px',
  viewer: true,
  initialValue: '<iframe></iframe>',
  customHTMLSanitizer: html => html
});

However, it should be noted that if you use this option, you have to handle the tags with the XSS vulnerability, and tags like `iframe`` may disappear when you switch to WYSIWYG mode in the Editor.

Thanks, it is working ! I added DOMPurify to avoid XSS problems.


Feature/oap/annotation

Use annotation to instead of the definition file.

BTW, CI fails.

Coverage decreased (-0.3%) to 22.621% when pulling 5c8c5d58e8d0a7ba93949742c443b752eae42283 on peng-yongsheng:feature/oap/annotation into 9ac0f0779372782c169686f0084ce0395e7c0862 on apache:6.0.


Add k8s events to task phase updates

Read then delete this section
- Make sure to use a concise title for the pull-request.
- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version
will be bumped. More details
TL;DR
Please replace this text with a description of what this PR accomplishes.
Type

[ ] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
3825
Follow-up issue
NA
OR
https://github.com/flyteorg/flyte/issues/

ohh please do not do this :( - This will kill etcD and KubeAPI

Is this just watching kube events? If so, we should increased the throughput on kubeclient. Do not write kube events. That impacts kubeapi drastically

@kumare3

Is this just watching kube events? If so, we should increased the throughput on kubeclient. Do not write kube events. That impacts kubeapi drastically

Correct, this just watches k8s events. It uses a separate clientset vs the KubeClient in flyteplugins in order to create a filtered informer.


How does it compare against LunaticMuch plugin?

Hi there
how does this plugin compare against https://github.com/LunaticMuch/docusaurus-terminology besides being inactive for months as well 😭.
(And being a fork of the  originally developed one  by Thanasis Katsadas<EMAIL_ADDRESS>and the Greek Government. The original work is still available on GRNet Gitlab.?)

Might be better answered by LunaticMuch, my read is that that project is the one that's diverged from this one? I've xposted to his project, see https://github.com/LunaticMuch/docusaurus-terminology/issues/30

I'm not sure about the repo of LunaticMuch and how it compares. Originally, we developed the docusaurus-terminology repo on Gitlab and then we redesigned it and integrated in our tooling. At some point, we did release the current open-source repository on Github, because there was some demand from people to join our Gitlab instance.

ok, wondering if he might one of them want to have access to gitlab. His Repo was shortly created after yours:

api.github.com/repos/LunaticMuch/docusaurus-terminology
"created_at": "2022-10-04T20:16:23Z",

api.github.com/repos/grnet/docusaurus-terminology
"created_at": "2022-09-05T13:06:37Z",

He might supoport here, if you change focus.
There are some changes,fixes, which could help you as well:

Release v1.4.0 · LunaticMuch/docusaurus-terminology
Fixed issue with glossary command. by T-Sana · Pull Request #28 · LunaticMuch/docusaurus-terminology


Loaders can't be specified inline

For example, the following won't work:
{
  "icons": [
    "src": "file-loader!./image.png",
    "sizes": "256x256",
    "type": "image/png"
  ]
}

In the meantime, you can work around this by ensuring all loaders are specified in webpack.config.js

Actually, this wasn't a real issue. It turns out that I was specifying the loader inline with file?... instead of file-loader?..., which was the cause of the issue.


Import support level for C

https://user-images.githubusercontent.com/57088952/111072753-e86a7e00-8516-11eb-9cdd-b25d2dee07a7.mp4
Originally posted by @denstiny in https://github.com/michaelb/sniprun/issues/45#issuecomment-798919844
This behavior would be practical !

Barring the fact that quite strangely, there is no error message, having import support level for C should not be harder that copypasting C++ interpreter code, so why not do it?

I think it should be no problem

I'm still a bit concerned that you don't have error messages like this when the code fail to compile

I think it should be no problem

I'll look into that shortly

I think it should be no problem

I'll look into that shortly

我仍然有点担心，当代码无法编译时，您没有像这样的错误消息（带有适当的错误ofc）

In addition I have not received any error

What can I do for you？

In fact, when running a little bit complicated code without any output

Similar to the c language to implement the already very difficult, so don't lose heart

This particular code is invalid (i guess, you should initialize s and malloc it some memory) , so Sniprun try do diusplay an error - and that doesn't work for you, which is what 'ill try to debug)

Sniprun relies on nvim_err_write ( a neovim function) to display an error.
Could you try to run
:call nvim_err_write("line1\nline2\n")

This particular code is invalid (i guess, you should initialize s and malloc it some memory) , so Sniprun try do display an error - and that doesn't work for you, which is what I'll try to debug)

Sniprun依靠nvim_err_write（neovim函数）来显示错误。
你能跑吗
:call nvim_err_write("line1\nline2\n")
（来自neovim）？

I can't run him

The code itself is (again) invalid, so I wonder what you have run this time.
I guess you've run :call nvim_err_write("4\n7\n") , and in this case it makes sense, but that also means nvim_err_write works..... but not when run from sniprun

该代码本身（再次）无效，所以我想知道您这次运行了什么。
我猜你已经运行了:call nvim_err_write("4\n7\n") ，在这种情况下这很有意义，但这也意味着nvim_err_write可以工作...但是从sniprun运行时则不行

Well, I run Sniprun error code won't give me any mistake, I'm sorry, I ability is limited, can only help you so much, can reply to me if there is any need, I should go to bed

no worries, you can get in touch anytime. Though, this is a side project and i'm also working on other things, idk if i'll be able to debug your (pretty but) particular neovim

no worries, you can get in touch anytime. Though, this is a side project and i'm also working on other things, idk if i'll be able to debug your (pretty but) particular neovim

I didn't understand your last sentence. Debug my neovim? What do you mean?

It looks like Sniprun does not display correctly (if at all) on your config, whereas it works on mine and a friend's.
If we want to understand why, we'll have to take some time to search for the cause and solution

It looks like Sniprun does not display errors correctly (if at all) on your config, whereas it works on mine and a friend's.
If we want to understand why, we'll have to take some time to search for the cause and solution

Do you want to install my configuration to try to find the problem?

Sure, if you have any dotfiles that would be great, and I'd also like to check your neovim version.
I won't do it right away though, you've mentionned you wanted to go to sleep and you should take care of yourself, open-source is great but also a rabbithole

You are so thoughtful, I think the installation is very simple at least, But I did not do English documents, if you can, try to translate Chinese into English, encounter installation problems at any time to reply to me, I try to help you.
地址        https://github.com/denstiny/nvim-nanny

no worries, you can get in touch anytime. Though, this is a side project and i'm also working on other things, idk if i'll be able to debug your (pretty but) particular neovim

Is it possible that I'm using a preview version of neovim?

A recent version should not create problems (whereas an older one....), and i'm on nightly 0.5 myself

I successfully reproduced and I've worked through some kind of workaround, though the exact cause of the issue remains a mystery.
You should set a new config variable, let g:SnipRun_inline_messages=1, that , while it breaks multi-line support that wasn't there for you in the first place, does now display, more or less nicely, output & errors.
To try that before it gets a release, you can set your plugin manager on the dev branch, and run the post-install script bash ./install.sh 1

I successfully reproduced and I've worked through some kind of workaround, though the exact cause of the issue remains a mystery.
You should set a new config variable, let g:SnipRun_inline_messages=1, that , while it breaks multi-line support that wasn't there for you in the first place, does now display, more or less nicely, output & errors.
To try that before it gets a release, you can set your plugin manager on the dev branch, and run the post-install script bash ./install.sh 1
You are great, but unfortunately I can't run it because of the network.

trust you know what you're doing, just don't forget to run ./install.sh, or alternatively, cargo build --release
This code.     cargo build --release

I'll try setting'g: SnipRun _ inline _ messages'

I am sorry that I did not receive an error message, I think it is not important, because this error is caused by the programmer, and not your plugin
I set up the let g: SnipRun_inline_messages = 1
I think I should be running bash. / install. Sh 1
But I can't run him, not because of my network

if bash ./install.sh 1 try to download something, it's because you don't have the Rust toolchain installed.
I've tested with your config, didn't work before, and now works with g:SnipRun_inline_messages=1, so the working code is already written!
However I didn't have the time to make a new release with an updated (pre-compiled) binary, and I'm working right now

ok,Thank you very much

I've tried, and it works with your config.
Though ,it's not as pretty as on mine because of some colorscheme shenanigans, still very usable.
Be sure to update to v0.4.9, no need to get the dev branch or give '1' as arg to the install script.

我已经尝试过了，它可以与您的配置一起使用。
虽然，由于某些颜色设计的恶作剧，它不如我的漂亮，但仍然非常有用。
确保更新至v0.4.9，无需获取dev分支或将'1'作为arg赋予安装脚本。

You really are a very, head of the author

No worries, I'll close this issue if you don't have any new problems :-)

This doesn't appear to work for me btw -
test case:
#include <stdio.h>
int ret(int i){
	return i;
}

int main(void) {
    int res = ret(2);
    printf("hello %i", res);
    return 0;
}

exe '! gcc ' . expand("%") . ' -o ' . expand("%")[:-3] .'.o && ' . expand("%")[:-3] . '.o'
hello world 2

Hovering on the printf line:
:<,>SnipRun
Compile-time error: use of undeclared identifier 'res'
    printf("hello %i", res);
Press ENTER or type command to continue

that's expected behavior.
While your one-liner run the entire file (and depends on its semantic correctness), at Import support level, sniprun only has knowledge about the code you selected.
In this case, :'<,'>SnipRun has no knowledge about 'res', let alone 'ret'.
However running sniprun on a visual selection containing
int a = 3;
printf("hello %i \n", a);

will work (that's Bloc-level support)
I know that's a bit of a shame because verbose languages such as C often have many dependencies on non-contiguous parts of code, however getting these 'dependencies' is a very complicated task (though not impossible), because I want that to work even if some parts of the code are still incomplete/ incorrect

I see - thank you! Ah yeah okay I should've RTFM a bit more closely. What's your workflow for interactive running of multi-function/more complicated in  Import supported languages?

For now, that's only possible with interpreters that have REPL capabilities, and then one can sniprun separately a function, then a print(function_call()), jupyter-notebook-style.
Unfortunately, only Python, Bash, R, Julia(wip) and Lua have such capabilitiesfor now. It's not unfeasible to give this 'REPL' capability to compiled languages, but that's not in the plans right now.
Feel free to open a feature request ofc :-)

I see! so when e.g. working in C or C++ you mostly use this for working with imported functions and less with functions that are defined in the same file?
And for C++ (and possibly others) - there are REPLs in form of jupyter kernels right? e.g. (cling)[https://github.com/jupyter-xeus/xeus-cling/tree/1d091cafb031073fb9ce78027d6c1ca81de0c243]


[Storage] Fix #21781 az storage blob upload/download: Progress fix

Related command

Description

Fix #21781 progress fail to update properly.
Testing Guide

az storage blob upload --file {file_path} -c {container_name} -n {blob_name} --account-name {account_name} --max-connection 5
az storage blob download --file {file_path} -c {container_name} -n {blob_name} --account-name {account_name} --max-connection 5
History Notes

[Storage] Fix #21781 az storage blob upload/download: Progress fix

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Storage


add semantic -version

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@devel dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix coap docs & action nodes screenshot

 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.


Unexpected number of items

CsystemArc can't read config of Netorareta Mama also something wrong with cgs extracting and hooking the game, it doesn't reference any of the proxies
Arc00.zip

Fixed in version 1.1.

Close as fixed

Could you also check this game. I think the game is encrypted so the tool gave me Found invalid data while decoding. when I extracted the config and vntextpatch can't get the tex
Tsumahaha.zip
t


Compilation with Clang fails, va_printf undeclared

Trying to compile the following example:
#include <thrust/device_vector.h>

int main(void)
{
    thrust::device_vector<float> A(1);
    return 0;
}

with Clang 8 or Clang 10 yields the following error:
/usr/local/cuda-10.0/include/thrust/system/cuda/detail/core/agent_launcher.h:557:11: error: use of undeclared identifier 'va_printf'

/usr/local/cuda-10.0/include/thrust/system/cuda/detail/cub/device/dispatch/../../util_debug.cuh:134:42: note: expanded from macro '_CubLog'
            #define _CubLog(format, ...) va_printf("[block (%d,%d,%d), thread (%d,%d,%d)]: " format, __VA_ARGS__);

...

Compiling with nvcc works.
Checking the code after pre-processing shows that the va_printf() function indeed lives under thrust::cuda_cub::cub while in agent_launcher.h it is called from within thrust::cuda_cub::core.

The va_printf compiler error is reproducible on Clang++ 9.0 with CUDA 10.0 and thrust 1.9.3 when compiling our software ESPResSo. Applying the solution by @j-petit removed the compiler error in ESPResSo, with all GPU tests passing:
--- thrust/system/cuda/config.h	2020-04-09 17:41:08.164278955 +0200
+++ thrust/system/cuda/config.h	2020-04-09 17:42:30.793338972 +0200
@@ -77,6 +77,8 @@
 #define THRUST_CUB_NS_PREFIX namespace thrust {   namespace cuda_cub {
 #define THRUST_CUB_NS_POSTFIX }  }

+#include <thrust/system/cuda/detail/cub/util_debug.cuh>
+using namespace thrust::cuda_cub::cub;

 #ifndef END_NS_THRUST
 #define END_NS_THRUST }

The underlying issue comes from an old fix in the CUB dependency (thrust/cub:cub/util_debug.cuh#L134-L141) that was introduced for Clang 4.0.0 (72fefca8). It's probably not relevant anymore for recent Clang versions. In fact, replacing va_printf by printf also removes the compiler error in ESPResSo:
--- cub/util_debug.cuh	2020-04-09 17:21:16.707835166 +0200
+++ cub/util_debug.cuh	2020-04-09 17:24:09.225871996 +0200
@@ -129,9 +129,9 @@
         #endif
             }
         #ifndef __CUDA_ARCH__
-            #define _CubLog(format, ...) va_printf(format,__VA_ARGS__);
+            #define _CubLog(format, ...) printf(format,__VA_ARGS__);
         #else
-            #define _CubLog(format, ...) va_printf("[block (%d,%d,%d), thread (%d,%d,%d)]: " format, __VA_ARGS__);
+            #define _CubLog(format, ...) printf("[block (%d,%d,%d), thread (%d,%d,%d)]: " format, __VA_ARGS__);
         #endif
     #endif
 #endif

I'm not really familiar with the thrust code, so take these two quick fixes with a grain of salt. The issue seems to have been fixed in thrust 1.9.5 because the compiler error is not reproducible with Clang++ 9.0 with CUDA 10.0 and thrust 1.9.5.

This was fixed with thrust/cub@a568ffa1fe061c20689934f119afd09beae820fd.


Fix broken imports for ListEvents

Backend checklist

[x] Formatted my code by running autoflake -r -i --remove-all-unused-imports src && isort . && black . in app/backend
[ ] Added tests for any new code or added a regression test if fixing a bug
[ ] All tests pass
[ ] Run the backend locally and it works
[ ] Added migrations if there are any database changes, rebased onto develop if necessary for linear migration history

If it's still not working IDK. Maybe @aapeliv can help you, I believe he wrote it.
Also make sure to update the front end where the API is actually called

I'm confused, is the query working or not?

Haven't had time to look again to see if it's something funky in my DB, but last time I checked it wasn't working :(


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 194 ms

Resolved: ClamAV performance has improved in 05207d8 after 5 minutes.


[Production check] Slack Garbage collector

What's the status here?

friendly bump what's the status here @lasryaric ?

Lost track of that in the Olympus backlog.
We never discussed it again really. I suppose the idea was to the same thing as the Gdrive production check, but it's been opened for a very long time and we never felt the need for it again, so I suggest we close this for now.


Typesetting for gaussian elimination

Description
I want to typeset Gaussian elimination. The process is often notated using augmented matrices. As far as I can see, they are currently not supported by typst. In addition, I would like to add descriptions next to the lines of the matrix to indicate which operations are performed on them. I also don't see any way to do this currently. The best I could do so far is to draw lines, numbers, and text using a grid, but this method is only an approximation of what I want to achieve and does not support brackets around the matrix.
Use Case
Gaussian elimination

Augmented matrices were already requested in #948 and there's also a workaround. Regarding your second request, I'm not sure what exactly you want, could you add an image with an example?

Thank you for the link to the other issue, I didn't find it before because github's search wasn't matching it for "augmented".
For the desciptions of the operations, I imagine something like this:

This seems like a job for a future package, not the base typst language.
Your picture should be achievable already today by using for instance place, move or box with outset.

Thanks, I will try to figure it out with these functions.

Thanks, I will try to figure it out with these functions.

Have you figured out how to write descriptions of operations?

Support for augmented matrices was added! See #1679


Warning about ES2017+ target does not show when using Webpack plugin

🐞 Bug report
Component
@ngtools/webpack (AngularCompilerPlugin)
Is this a regression?
No
Description
https://github.com/angular/angular-cli/pull/13643 added a warning message when the TS compiler is configured to emit ES2017 or higher, due to https://github.com/angular/angular-cli/issues/13477.  This warning is not displayed when the project is built via Webpack using AngularCompilerPlugin.  I asked on https://github.com/angular/angular/issues/31730 and it sounds like we need a separate ticket to track this since the linked PR and issue are both auto-closed.  It doesn't look like there's a path forward on the Zone issue so this is going to keep biting people for a good while, I think.
🔬 Minimal Reproduction
Pick any project you have lying around that uses AngularCompilerPlugin, change compilerOptions.target in the tsconfig.json to ES2017, and build.  If you were building it with the CLI you'd see Warning: Zone.js does not support native async/await in ES2017 on the console, but not with the plugin.
🌍 Your Environment
@ngtools-webpack 10.1.2, but I don't see any relevant changes in the recent 11+ builds.

@alan-agius4 is "freq1" really appropriate?  The plugin has 1.5M weekly downloads on NPM, and while I'm sure that ES2015 is the most popular emit target by a wide margin, in late 2020 we have broad browser support for the full ES2017 feature set, including async/await.
I started my project with a lower emit years ago, but at some point I raised it to ES2018 (I do have the luxury of running in a known environment) and it seemed to "just work", so I left it that way.  It wasn't until I spent 2+ days tracking down a mysterious inability to test some async code that I found the linked Zone issue.  If it happened to me, it's happening to a nontrivial percentage of your users, and even 1% of 1.5M users is hardly "only a handful, who observe it rarely".

Hi @thw0rted,
Most of the package downloads comes from @angular/cli users. Approximately 8% of the users use @ngtools/webpack without Angular CLI. That 8% goes down even more when taking into account users that target only ES2017+.
That said, I do have a PR in flight for this https://github.com/angular/angular-cli/pull/19228

Sorry, Alan, I was going by the NPM page -- I didn't realize those numbers reflected usage other than via Webpack.  (Or, I guess, the CLI uses Webpack under the hood?)  Anyway, it looks like this was a quick fix, which is great news.  Thanks!

No worries @thw0rted, yes the CLI does use Webpack under the hood.


Add server API

#264  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @teobaranga and the rest of your teammates on  Graphite


addDevServerHandler not working as expected

Environment

Operating System: Windows_NT
Node Version:     v20.10.0
Nuxt Version:     3.9.1
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, app, css, i18n, dayjs, routeRules, modules, runtimeConfig
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-jcbsci?file=modules%2Fhello%2Findex.ts
Describe the bug
addDevServerHandler handler in the documentation accepts a string, but ts is throwing "Type 'string' is not assignable to type 'EventHandler<EventHandlerRequest, any>'."
When running the project a warning is thrown:  WARN  [h3] Implicit event handler conversion is deprecated. Use eventHandler() or fromNodeMiddleware() to define event handlers.
Route: /_handler
Handler: /home/projects/github-jcbsci/modules/hello/runtime/uptime.get
The addServerHandler works fine.
Additional context
No response
Logs
No response

The type of handler within addDevServerHandler is an EventHandler. The documentation need a fix

Can I ask why addDevServerHandler has a different implementation than addServerHandler?

That's because addDevServerHandler() is only a semantic helper to add a dev handler in nitro.
The type is constrained to nitro types and nitro.options.devServerHandlers is an array of objects with route and handler. With handler being the EventHandler you're using in nitro endpoints


Add Pxem, MOONBlock, Painter Programming, JSX, AnalF*ck, 秀丸マクロ, Kinx,G-BASIC, Blawn, LibreOffice Basic and XBasic / Update TSharp, Whitespace, Malbolge, Kitanai and MarioLANG

Adding a language

[x] The code displays "Hello World"
[x] I have updated the readme to include the new language
[x] I have incremented the language count in the readme
[x] I have no association with the language
[x] There are no copyright issues with this code
[x] The language has not been added prior to this pull request

Add:
Pxem *
https://web.archive.org/web/20120605223423/http://cfs.maxn.jp/neta/pxem.php
https://ja.wikipedia.org/wiki/Pxem
MOONBlock
https://moonblock.jp/index.html#
Painter Programming **
https://square1001.github.io/painter-programming/index.html
JSX
http://jsx.github.io/
AnalF*ck
https://github.com/makenowjust/AnalF_ck
秀丸マクロ
https://hide.maruo.co.jp/software/hidemaru.html
Kinx
https://github.com/Kray-G/kinx
G-BASIC
https://ja.wikipedia.org/wiki/ぴゅう太
Blawn
https://github.com/Naotonosato/Blawn
https://github.com/kmizu/Blawn/tree/develop
Libreoffice Basic
https://help.libreoffice.org/6.1/en-US/text/sbasic/shared/01000000.html
XBasic
https://xbasic.org/
Update:
TSharp (ext)
https://github.com/Tsharp-lang/Tsharp/
Whitespace (code)
https://en.wikipedia.org/wiki/Whitespace_(programming_language)
Malbolge (ext,code)/reported at #1322
https://en.wikipedia.org/wiki/Malbolge
Fixes #1322
Kitanai (ext)
https://github.com/Sygmei/Kitanai
MarioLANG(name,ext)
https://github.com/tomsmeding/MarioLANG
*Real source file of Pxem is zipped because source code must be written in file name.
**Draw "HELLO WORLD" in upper case

The MOONBlock code isn't quite right

The MOONBlock code isn't quite right

it correct.worked on my side

this title decreases readability

The MOONBlock code isn't quite right

it correct.worked on my side

The text isn't capitalised

this title decreases readability

It's a tradeoff between being readable and looking nice

Can MOONBlock be exported as a project file instead of being screenshotted?

There's source button,but cannot import from it.

There's source button,but cannot import from it.

What does it do?

it shows json based on code.but it just shows only.cannot import

Could you send a link to the editor?

already wrote in first comment
https://moonblock.jp/index.html#

Alright then, just crop the borders of the image in to be proportional


Extract create agreements

Follow up on #2279: RuboCop ABC size failure.
RuboCop failure on the main branch caused by the transition of current_user from an instance variable to a method call.
Offenses:

app/controllers/profiles_controller.rb:21:3: C: Metrics/AbcSize: Assignment Branch Condition size for create is too high. [<6, 72, 13> 73.41/72]
  def create ...
  ^^^^^^^^^^

380 files inspected, 1 offense detected

To resolve this, the create_agreements method was extracted.
Note: CNDS2024 does not uses these agreements.

Closing this PR as it's addressed in PR #2299.


Image files are not present in the manifest and not all images are revisioned

Hey, i'm trying to use this plugin, but i fail to make it work the way i need it to:
first, i need all the files form my /images/ dir to be revisioned, even the files I don't require in my js or css. (can this even be done?) and then i'm having this strange bug that the image files are not present in the manifest.json even though they were copied, revisioned and successfully linked.
This is the project with the testcase, just run "npm run webpack" if you want to help me and take a look at it. Thank you very much!
https://github.com/antpaw/webpack-test-project/tree/plugin

Hi, you don't have webpack included in your package.json so I'm not sure what version you're running.
Can you also try using "webpack": "^1.9.10" and seeing if that changes anything?

sorry, i pushed the fix, it didnt help, exactly the same outcome

Have you tried minimizing it down to just this plugin with your assets, and then add in your other plugins 1 by 1?

okay i have emptied dependencies, file structures, configs in this brach to have the most simplest use case https://github.com/antpaw/webpack-test-project/tree/simple-plugin
and I still have the same two problems

Perfect, thanks. I will look into it over the weekend.

I did glance it quickly and while I haven't tested this yet, why are you going back 2 directories here:
https://github.com/antpaw/webpack-test-project/blob/simple-plugin/webpack.config.js#L22
Also, here's a working example to look at:
https://github.com/nickjj/demo-for-chattanooga-python-user-group

Without the 2 "backs" it crashes because modules cant be found.
the example you gave works, I'm not sure what i'm doing differently, maybe I'm using too many absolute paths.
another thing: Can you explain when the directory move and revision of rootAssetPath happens? does it happen before anything else in webpack happens?

I am having this same issue myself. It seems the problem stems from the if block here https://github.com/nickjj/manifest-revision-webpack-plugin/blob/master/index.js#L60 where it ignores chunked assets. I have a few hundred images in my assets directory that get used statically, but a few of them are imported in my javascript, and none of those imported images make it to the manifest.json, which I still need because they are sometimes accessed in my static html. Maybe we could do with a config option to include certain files even if they appear in chunks?

Is there ever a situation where you'd have a ton of those white listed files? It seems like it would be really tedious if you had to add dozens or hundreds of them to a list.

Well the main issue is that 90% of our site is served statically from flask via jinja templates. Almost all of our images are used there, but we want to be able to use webpack and flask-webpack for the 10% that we use react for. I was able to work around it by just never pulling images in through js imports, but obviously that's not ideal as a long-term solution.

Yeah I'm just concerned about a bigger project where you may have all of your images imported in JS. That would mean you'd need to white list all of them, and keeping a manual manifest of all of your assets seems lame.
I wonder if there's a way to do this in a way that's automated.

I had a similar issue and created a PR that fixed it in my case.
Here is the constructor I'm using:
new ManifestRevisionPlugin(
  path.resolve(PATHS.build, 'manifest.json'),
  {
    rootAssetPath: PATHS.rootAssetPath,
    ignorePaths: [],
    extensionsRegex: /\.(jpe?g|png|gif|svg)$/i,
  }
),

@antpaw @auskast
Could you try out the branch where I have the change and report if it works for you?
To try it out you can use this in your package.json (but don't use this in production!)
"manifest-revision-webpack-plugin": "git://github.com/stoikerty/manifest-revision-webpack-plugin.git#feature/additional-regex-option",

Definitely interested to see if it works for them, if so that looks like a clean fix.

nope it doesnt work, same problem, you can checkout yourself by installing the git i have included in the intial post

Yes it solved one problem!!! but the images that are not included or required in the code will not appear in the manifest, which is a far less of a problem, but i still need to find a solution for this. I have updated my example git repo as well.

Nice to hear that it works for you @antpaw!
IIRC images that are not included can't be detected since they are never being traversed. I think that might be out of scope for this plugin. I'm not sure how useful it would be to have a hashed image in your build folder if it's never being used in your code.
What you could do however is simply have a file that references all the images you need. If I add require('../images/asofoa/aof/imgres.jpg'); to your foo.js for instance, the image will appear where you would expect and be referenced in the manifest file.

Thanks for the report.

I need this because I'm building a isomorphic javascript app that also renders on node. So not every image will be present in required frontend js. But i still need one manifest for all my images. However this is no longer an issue for this plugin. Thank you. Will this fix be merged?

@antpaw I merged it yesterday and pushed v0.3 to npm with that fix.
Going to close this for now.


tidy and fix magefile

@michaelneale what do you think?

Looks good. Didn’t think of the mobile requirement, nice one.

@michaelneale I apologize, I was impatient and merged this into the ssi-sdk project.


Exclude Directory

Looked up exclude or exclude-directory in the documentation as I would like to exclude one directory from being deployed. It is a directory we do like to keep in version control on Github but would like to exclude from deployment. Is there such a parameter? How would we add it to our Laravel recipe?

What is the purpose of that directory?
Is it an option to create a separate repository for it perhaps?

Deployer uses git to clone the repo, so I think it will always clone the whole repository.
An option might be to clone the repo, and create a custom task in Deployer which will delete a specific directory?

@GlennM , yeah, will have to think about this. Perhaps post addition a removal. Sounds like the only option really. Thanks for the feedback!

@jasperf I don't have any experience with it, but it seems that when you use the rsync recipe you can exclude files/dirs.

Laravel Deployer based on PHP Deployer does allow you to exclude directories. See https://github.com/lorisleiva/laravel-deployer/blob/master/docs/strategy-upload.md where they mention
// config/deploy.php

'options' => [
    'upload_options' => [
        'options' => [
            '--exclude=.git',
            '--exclude=/vendor', // unless `upload_vendors` is set to `true`
            '--exclude=node_modules',
        ],
    ],
],

as an example. Going to look into this.

Read https://deployer.org/recipes/rsync.html and they mention this example (only added required recipe).
// deploy.php

require 'recipe/rsync.php';

set('rsync',[
    'exclude'      => [
        '.git',
        'deploy.php',
    ],
    'exclude-file' => false,
    'include'      => [],
    'include-file' => false,
    'filter'       => [],
    'filter-file'  => false,
    'filter-perdir'=> false,
    'flags'        => 'rz', // Recursive, with compress
    'options'      => ['delete'],
    'timeout'      => 60,
]);

We will test this.

Do wonder how we would fit that rsync part here
<?php

namespace Deployer;

require 'recipe/laravel.php';
require 'vendor/deployer/recipes/cachetool.php';

// Configuration
set('repository', 'git@github.com:user/domain-v3.git');
set('default_stage', 'production');
set('git_tty', true); // [Optional] Allocate tty for git on first deployment
set('ssh_type', 'native');
set('cachetool', '/var/run/php/php7.3-fpm.sock');
set('keep_releases', 10);

// Make sure uploads & published , tls, logs aren't overwritten by deploying
set('shared_dirs', [
    'public/uploads',
    'public/published',
    'storage/logs',
    'storage/tls',
    'storage/app/public',
]);
set('shared_files', [
    '.env',
    '.transip_private_key',
]);
set('writable_dirs', [
    'public/uploads',
    'public/published',
    'storage/framework/cache/data',
    'storage/logs',
    'storage/tls',
    'storage/app/public',
]);

// SMART CUSTOM DEPLOY COMMANDS
task('db:migrate', function () {
    run('cd {{release_path}} && php artisan migrate');
});
task('horizon:terminate', function () {
    run('cd {{release_path}} && php artisan horizon:terminate');
});

task('queue:restart', function() {
    run('cd {{release_path}} && php artisan queue:restart');
});

task('reload:php-fpm', function () {
run('sudo /etc/init.d/php7.3-fpm restart'); // Using SysV Init scripts
});

// Hosts
// dep deploy production
// dep deploy staging

   host('staging')
   ->hostname('staging.domain.com')
   ->user('forge')
   ->forwardAgent()
   ->stage('staging')
   ->set('deploy_path', '/home/forge/staging.domain.com');

   host('production')
   ->hostname('my.domain.com')
   ->user('forge')
   ->forwardAgent()
   ->stage('production')
   ->set('deploy_path', '/home/forge/domain.com');

// Run database migrations
after('deploy:symlink', 'db:migrate');

// Restart job
after('db:migrate', 'queue:restart');

// Clear OPCache
after('queue:restart', 'cachetool:clear:opcache');
after('cachetool:clear:opcache', 'horizon:terminate');

after('deploy', 'reload:php-fpm');
after('rollback', 'reload:php-fpm');

Any pointers?

As shown at https://github.com/deployphp/deployer/issues/2044 I probably need the following, but still tweaking:
<?php

namespace Deployer;

require 'recipe/laravel.php';
require 'vendor/deployer/recipes/ rsync.php'
require 'vendor/deployer/recipes/cachetool.php';

// Configuration
set('rsync', [
    'exclude' => ['.git', 'docs'],
    'flags' => 'rzcE', // Recursive, with compress, check based on checksum rather than time/size, preserve Executable flag
    'timeout' => '600',
]);
set('rsync_src', __DIR__);
set('rsync_dest','{{release_path}}');
set('cachetool', '/var/run/php/php7.3-fpm.sock');
set('keep_releases', 10);

// Make sure uploads & published , tls, logs aren't overwritten by deploying
set('shared_dirs', [
    'public/uploads',
    'public/published',
    'storage/logs',
    'storage/tls',
    'storage/app/public',
]);
set('shared_files', [
    '.env',
    '.some_private_key',
]);
set('writable_dirs', [
    'public/uploads',
    'public/published',
    'storage/framework/cache/data',
    'storage/logs',
    'storage/tls',
    'storage/app/public',
]);

//  CUSTOM DEPLOY COMMANDS
task('db:migrate', function () {
    run('cd {{release_path}} && php artisan migrate');
});
task('horizon:terminate', function () {
    run('cd {{release_path}} && php artisan horizon:terminate');
});

task('queue:restart', function() {
    run('cd {{release_path}} && php artisan queue:restart');
});

task('reload:php-fpm', function () {
run('sudo /etc/init.d/php7.3-fpm restart'); // Using SysV Init scripts
});

// Hosts
// dep deploy production
// dep deploy staging

   host('staging')
   ->hostname('staging.domain.com')
   ->user('forge')
   ->forwardAgent()
   ->stage('staging')
   ->set('deploy_path', '/home/forge/staging.domain.com');

   host('production')
   ->hostname('my.domain.com')
   ->user('forge')
   ->forwardAgent()
   ->stage('production')
   ->set('deploy_path', '/home/forge/domain.com');

// Run database migrations
after('deploy:symlink', 'db:migrate');

// Restart job
after('db:migrate', 'queue:restart');

// Clear OPCache
after('queue:restart', 'cachetool:clear:opcache');
after('cachetool:clear:opcache', 'horizon:terminate');

after('deploy', 'reload:php-fpm');
after('rollback', 'reload:php-fpm');

I am cleaning up on issues. Fill free to reopen if needed.
Also, we have a new section available: discussions.

What's the current way to do this since Laravel Deployer is no longer developed? I would like to be able to exclude a directory from being copied over while sticking to the git clone, but will settle just for knowing the necessary YAML syntax to delete a folder.


How is the zsh_completion supposed to be used?

Does it have to be copied manually to $(brew --prefix)/completions/zsh e.g. /usr/local/Homebrew/completions/zsh? I was thinking it would be automatic once I executed brew tap homebrew-services.

It needs to be manually symlinked for now but there's an open PR to work on this https://github.com/Homebrew/brew/pull/1708

Thanks @MikeMcQuaid!


Add stoty to the developer list

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 28s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 23s
master passed

+1 :green_heart:
compile
5m 12s
master passed

+1 :green_heart:
spotless
0m 46s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

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

+1 :green_heart:
compile
5m 13s
the patch passed

+1 :green_heart:
javac
5m 13s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
hadoopcheck
5m 33s
Patch does not cause any errors with Hadoop 3.3.6.

+1 :green_heart:
spotless
0m 43s
patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 12s
The patch does not generate ASF License warnings.

31m 28s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5790/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac hadoopcheck spotless xml compile

uname
Linux 9586d60e175e 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 90639d75a5

Default Java
Eclipse Adoptium-11.0.17+8

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

modules
C: . U: .

 U: .

 U: .

 U: .

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

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.


Is it compatible with gorm ?

This library is what the gorm sqlite driver uses. https://github.com/go-gorm/sqlite/blob/master/sqlite.go#L8

@rittneje  the one gorm uses doesn't have encryption. tis why am asking.

You didn't mention anything about encryption in your original question. No, this library does not currently support encryption.
Also, I think you may be confused. This library is the one gorm is using.

@rittneje  thanks for clarifying ^^.


API V2 discontinued -  Changes to migrate to V3

Translator Text API V2 is going to be discontinued, I have done the migration to V3.
This Pull Request fixes #30

Hi,
Have you had time to review the changes I submitted?
Thanks!

Hi,
Could be possible to accept those changes so the Translator Text API can continue working?
Thank you!


Greenkeeper/cz conventional changelog 3.1.0

:tada: This PR is included in version 1.0.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


bump syn, quote and proc-macro2 to version 1.0

Just a simple version bump for the dependencies, and a few line fixes where the api changed. This currently does not get rid of the old versions in the Cargo.lock due to num-derive's newest version not having upgraded to the 1.0 releases yet. From what I've seen that will be fixed once https://github.com/rust-num/num-derive/pull/29 lands there.

Nice, thanks! The num-derive situation may have been resolved by the time I release the next version anyway, so that's fine. I'm hoping for a new release of num-traits with some no-std improvements.

bord r+

bors r+


[NVIDIA] Weird display issues

Regression?
Yes
System Info and Version
 System/Version info
Hyprland, built from branch  at commit 2cfc6722fdbc93fd0c5987eeac0d4b96cd0128a7  ().
Date: 2024-08-06
Tag: , commits: 2cfc6722fdbc93fd0c5987eeac0d4b96cd0128a7

flags: (if any)

System Information:
System name: Linux
Node name: silenos
Release: 6.6.44
Version: #1-NixOS SMP PREEMPT_DYNAMIC Sat Aug  3 06:54:42 UTC 2024

GPU information:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev a1) (prog-if 00 [VGA controller])
NVRM version: NVIDIA UNIX x86_64 Kernel Module  555.42.02  Mon May 13 17:24:29 UTC 2024

os-release: ANSI_COLOR="1;34"
BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
BUILD_ID="24.05.20240805.883180e"
DOCUMENTATION_URL="https://nixos.org/learn.html"
HOME_URL="https://nixos.org/"
ID=nixos
IMAGE_ID=""
IMAGE_VERSION=""
LOGO="nix-snowflake"
NAME=NixOS
PRETTY_NAME="NixOS 24.05 (Uakari)"
SUPPORT_END="2024-12-31"
SUPPORT_URL="https://nixos.org/community.html"
VERSION="24.05 (Uakari)"
VERSION_CODENAME=uakari
VERSION_ID="24.05"

plugins:
  hy3 by outfoxxed ver 0.1

======Config-Start======

Config File: /home/usr/.config/hypr/hyprland.conf: Read Succeeded
exec-once = /nix/store/8piinp0n24cl145qndjdfzja8x9s5x0k-dbus-1.14.10/bin/dbus-update-activation-environment --systemd DISPLAY HYPRLAND_INSTANCE_SIGNATURE WAYLAND_DISPLAY XDG_CURRENT_DESKTOP && systemctl --user stop hyprland-session.target && systemctl --user start hyprland-session.target
plugin=/nix/store/9f1x75xrr67dhkkld546i2crn364p4yw-hy3-hl0.41.2/lib/libhy3.so
$mod=SUPER
animations {
  bezier=myBezier, 0.05, 0.9, 0.1, 1.05
  animation=windows, 1, 5, myBezier
  animation=windowsOut, 1, 5, default, popin 80%
  animation=border, 1, 5, default
  animation=borderangle, 1, 8, default
  animation=fade, 1, 7, default
  animation=workspaces, 1, 6, default
  animation=specialWorkspace, 1, 3, default, slidevert
}

cursor {
  no_hardware_cursors=false
}

debug {
  disable_logs=false
}

decoration {
  blur {
    enabled=true
    passes=1
    size=5
    vibrancy=0.169600
  }
  rounding=5
}

general {
  layout=hy3
}

input {
  kb_layout=de
}
bind=$mod SHIFT, Left, hy3:movewindow, l
bind=$mod SHIFT, Right, hy3:movewindow, r
bind=$mod SHIFT, Up, hy3:movewindow, u
bind=$mod SHIFT, Down, hy3:movewindow, d
bind=$mod, Left, hy3:movefocus, l
bind=$mod, Right, hy3:movefocus, r
bind=$mod, Up, hy3:movefocus, u
bind=$mod, Down, hy3:movefocus, d
bind=$mod, X, hy3:makegroup, h
bind=$mod SHIFT, X, hy3:makegroup, v
bind=$mod, escape, exec, ags --toggle-window powermenu
bind=$mod, F, exec, chromium
bind=, Print, exec, grimblast copy area
bind=$mod, M, exit
bind=$mod, T, exec, foot
bind=$mod, Q, killactive
bind=ALT, space, exec, ags --toggle-window launcher
bind=$mod SHIFT, S, exec, grim -g "$(slurp)"  - | tee >(wl-copy) >(swappy -f -)
bind=SUPER_SHIFT, C, exec, cliphist list | wofi --show=dmenu | cliphist decode | wl-copy
bind=$mod, 1, workspace, 1
bind=$mod SHIFT, 1, movetoworkspace, 1
bind=$mod, 2, workspace, 2
bind=$mod SHIFT, 2, movetoworkspace, 2
bind=$mod, 3, workspace, 3
bind=$mod SHIFT, 3, movetoworkspace, 3
bind=$mod, 4, workspace, 4
bind=$mod SHIFT, 4, movetoworkspace, 4
bind=$mod, 5, workspace, 5
bind=$mod SHIFT, 5, movetoworkspace, 5
bind=$mod, 6, workspace, 6
bind=$mod SHIFT, 6, movetoworkspace, 6
bind=$mod, 7, workspace, 7
bind=$mod SHIFT, 7, movetoworkspace, 7
bind=$mod, 8, workspace, 8
bind=$mod SHIFT, 8, movetoworkspace, 8
bind=$mod, 9, workspace, 9
bind=$mod SHIFT, 9, movetoworkspace, 9
bind=$mod, 0, workspace, 10
bind=$mod SHIFT, 0, movetoworkspace, 10
bind=, F1, togglespecialworkspace, E
bindi=, code:122, exec, pamixer -d 5
bindi=, code:123, exec, pamixer -i 5
bindi=, code:173, exec, playerctl previous
bindi=, code:171, exec, playerctl next
bindi=, code:172, exec, playerctl play-pause
bindm=$mod, mouse:274, movewindow
bindm=$mod, mouse:272, resizewindow
env=XDG_CACHE_DIR,/home/usr/.cache/
env=XDG_CONFIG_HOME,/home/usr/.config/
env=ELECTRON_OZONE_PLATFORM_HINT,auto
env=NIXOS_OZONE_WL,1
exec-once=hyprpaper
exec-once=wl-paste --type text --watch cliphist store
exec-once=wl-paste --type image --watch cliphist store
exec-once=ags
monitor=Unknown-1, disable
windowrule=fullscreen, title:(HELLDIVERS™ 2)
windowrule=fullscreen, title:(Titanfall 2)
windowrulev2=workspace special:E silent, class:(vesktop)

======Config-End========

Description
After the Explicit sync fix MR Ive started to experience some weird issues with seemingly random apps.
For example when launching Alacritty, the window is stuck on before the shell gets launched. According to debug output by alacritty it receives keyboard and mouse events, however It appears that the shell is never launched, and alacritty also doesnt respond to the kill dispatcher.
These wierd occurences arent limited to Alacritty however. OBS also has issues with resizing the window, and also refuses to respond to the kill dispatcher.
And MPV freezes on the first frame and doesnt play the video.
Upon bisecting the MR I found that 158bbaaf88764e2a1e19ca1e3a11af541374432e first introduces this behaviour.
How to reproduce

Build Hyprland from 158bbaaf88764e2a1e19ca1e3a11af541374432e
( when using nix flakes with

hyprland.url = "git+https://github.com/hyprwm/Hyprland/?submodules=1&ref=explicit-sync&rev=158bbaaf88764e2a1e19ca1e3a11af541374432e";

)
2. Try to start Alacritty
3. Profit
Crash reports, logs, images, videos
Im using the 555 drivers
hypr_bad_4.txt
https://github.com/user-attachments/assets/c77f27e7-435a-443d-a92f-d677dab1c0f3
Couldn't give any feedback before the mr merge because i was at work

alacritty launching fine for me. nvidia-open-beta-dkms 560.31.02, hyprland-git 0.41.2.r169.b0a70f63-1

Weirdly enough the attatched video wont work, but here is one frame ( with alacritty in the middle and 2 foot instances to the sides)

And here is OBS:

the commit you bisected doesn't make sense as a regressor

Im aware

Try updating to b0a70f63e3865eaa77f0b78a04b230aa583bc95c, it works for me and seems like it fixed at least 3 other issues recently.

try updating the driver or disabling explicit sync as well

explicit sync doesnt seem to change anything (unless Im doing it wrong) :
https://github.com/user-attachments/assets/81368ae2-0a03-448b-a370-321b3c4326c3

Updating the driver works!
(WHY???????)

Updating the driver (to 560.28.03) works! (WHY???????)

Maybe some egl-wayland shenanigans, did u try egl-wayland from source?
U can close this issue now

Maybe some egl-wayland shenanigans, did u try egl-wayland from source?

No, I didn't.

U can close this issue now
Alr


Run testing on every pr

Description
We need too add check of the project tests on every pr to the main branch
Screenshots
No response
Additional information
No response

PR proposed

implementation tested and running
https://playwright.dev/docs/ci-intro#on-pushpull_request
however:
tests need to be refactored the BASE_URL is hard coded and thus fails to run in github action workflow


Update Meson Network

What kind of PR is this?
Select only one to speed up review/approval; i.e., don't lump an addition and a removal into a single PR.

[x] Adding something new to awesome-ipfs
[ ] Editing something already listed on awesome-ipfs
[ ] Removing something from awesome-ipfs
[ ] Something else (if so, please explain in the "Additional details" section below)

Pre-submit checklist
Please confirm ALL of the following before submitting your PR.

[x] This PR includes only one addition, removal, or edit.
[x] I edited the /data directory instead of the README.md.
[x] I reviewed the content policy and the and the IPFS Community Code of Conduct to ensure my submission meets the requirements.
[x] I have followed the CONTRIBUTING.md guidelines.

Additional details
Is there anything else we should know about this PR?

For new additions: What is your project's current size/reach?

For new additions: What is your project's potential size/reach?

For new additions: How critical is IPFS to your project?

[x] Essential
[ ] Somewhat critical
[ ] Useful, but not critical

For new additions: What core goal(s) does your project address?

[ ] Big-data solutions
[ ] Freedom from corporate/government interference
[ ] Data integrity
[x] Dev tools or other ways to enable developers
[ ] Disaster resilience/recovery
[x] File storage/retrieval
[x] File streaming
[ ] Permanent archiving
[ ] Self-sovereign identity
[ ] Platforms that utilize consensus, reputation, or incentivization
[ ] Other (please list)

Is anything about IPFS blocking your project?

Can you please share more information on how Meson uses IPFS?


Support object mapping of query result rows

Nobody wants to work with a Query and Cursor. Add support for mapping rows to objects. This should support both table-based and custom view-based objects.

how about something like this -
@Mapper
public interface Mapper {
    @Column.Mapper(0) long getId(Cursor c);
    @Column.Mapper(1) String getText(Cursor c);
    @Column.Mapper(2) Date getWhen(Cursor c);
}

one good thing about this is it works even for joins (since it's just a numeric position) - the unfortunate piece is that working with column numbers is problematic.
unfortunately, the alternative of this is also not great and is problematic due to the bug about not being able to use table.column in getColumnIndexOrThrow:
@Mapper
public interface Mapper {
    @Column.Mapper("notes._id") long getId(Cursor c);
    @Column.Mapper("notes.text") String getText(Cursor c);
    @Column.Mapper("todos.whence") Date getWhen(Cursor c);
}

thoughts?

In my opinion, It would be best if we could come up with a solution where the model can define the table structure, builders and mappings (preferably most of the boiler plating done by an annotation processor).  As a user(developer), I don't want to have to define a ton of interfaces, builders, abstract classes just to get some models out of the database.  This is one of my concerns I have as I watch this library mature through its infancy.

I agree with Kevin that we want to reduce boilerplate as much as possible, #16 is actually a great start on that. One thing we have to keep in mind is that we need something that works for every type of SELECT, things like SELECT count(*), SELCT table1.column, table2.column FROM table1 JOIN table2, SELECT *, SELECT table1.column AS alias, which are all pretty common occurrences.

Would it be possible to add an optional parameter like the following to the create method and call it later in the Query.run method?
'''java
/** Convert the query Cursor to the user model */
public interface CursorModel{
T convertToModel(Cursor c);
}
'''
This would not reduce the boilerplate but just move the cursor mapping out of the observable flow/subscribe methods implementation.

@ahmedre that's just perfect, now we need to generate those Mappers from SQL strings, and look for type hints: initial creation script + all the migrations or assist the IDE plugin by hand
the second option is at least achieveable

@ahmedre and what's the bug with getColumnIndexOrThrow?

@adelnizamutdinov getColumnIndexOrThrow doesn't work with table.column, only with column - see http://androidxref.com/5.1.0_r1/xref/frameworks/base/core/java/android/database/AbstractCursor.java line 275 for details.

A few months ago I put together https://github.com/madebyatomicrobot/vinyl to start to address some accumulated internal project pains with Cursors and mapping rows into objects.  Not sure if something like that is what you would like to see in SQLBrite.

There is also sqlbrite dao

Our solution to this is https://github.com/square/sqldelight and efforts around object mapping will be focused there.


Seed shown in message is incorrect for n > 1

It seems to show the seed from the last image rather than the first one, so if you copy/paste the command the seeds increase.
EG if n = 5, and the seed = 0, then the message in the channel on completion will say that the seed was 4

Thanks for finding this, fixed here: https://github.com/parlance-zz/g-diffuser-bot/commit/bf93bfe351d94eb89d3551dea1e0d8d11930479b


use "import" or "require("survey-react-bootstrap") not work!

Is there any chance you add  this?
this is error #
node_modules/survey-react-bootstrap/dist/survey.react.bootstrap.js:4519
}(React.Component));
THANKS

Hi, I do not mind to support it. Could you please point me a direction?

@andrewtelnov duplicate of https://github.com/andrewtelnov/surveyjs/issues/75

@cyberiuscorp @cpruijsen
Guys, I have updated https://github.com/andrewtelnov/surveyjs/issues/75.
There is a version that should works fine now. It uses webpack. Could you check it out?
Thank you,
Andrew


I can confirm 1.0.1 fixes all issues I was having in #1


Spring Boot: Remove tech preview note from runtime details section

tech preview note not applicable for Spring Boot guide

fixed in #754


Array manipulation access

Adds look up and assignment for arrays. Need to decide if when translating from python to js if arr[x] = 1 should be translated to arr[x] = 1 or let arr[x] = 1 .

let arr[x] = 1 would be pretty confusing, how hard would it be to remove that behavior?

It's just a simple if statement, I just added it


[Feature Request] Challenge mode

A mode where you can generate a seed for the RNG and share it as a URL. Everyone who plays this seed will get the exact same tiles so their scores relative to each other are more a result of skill than luck (maybe). Coupled with your plan to enable sharing of scores, this could add another dimension to the game?

This way users wouldn’t have to choose a game mode up front, which would keep the game simpler.

Great point! I saw that you're using Math.random() in useBoard.ts and I'm aware that js doesn't allow you to seed that function but there is a package that allows seedable RNG https://www.npmjs.com/package/seedrandom

I actually didn't know that Math.random() can't be seeded, so thanks for that link.
It would also require changing the way new tiles are generated. Right now they're just generated on demand, where they're needed. For a challenge mode, new tiles should probably be generated at the start of the game or at least in the same position. Maybe the random generator could be seeded with the column number and the amount of tiles that have been generated so far in that column.

I think the seedrandom package allows you to save and restore it's state, though I don't know if that would fit into a URL


GM: match ECM standstill check

Useful for avoiding faults both for OP long and without. As well as allowing engagement where the ECM allows it (sometimes up to 0.5 m/s, but as far as ECM and camera are concerned, we're at a standstill).
Also matches panda standstill now.

[ ] Should check to make sure this isn't noisy at all on ASCM cars

This doesn't seem right. The camera's standstill check is 0.311 kph, but the ECM's is above 0.2 m/s


Bump Dart SDK to 1.18.0-dev.4.4.

Some native extensions (and Dartium) fixes mainly but it’s (fingers crossed) a release candidate so we should make sure nothing breaks for Flutter.


Fix Lapis Lazuli Belt generation

Lapis Lazuli gaussian belt generator fixed/rewritten. Added corresponding gui sliders to configure generation.
Left old method for gaussian curve in in case it's needed somewhere else.

Squash commits. To do so type git rebase -i HEAD~6 and type squash to every commit except first.

Also no need to squash commits, I can do it myself when merging.

Any progress @Shad0wlife ?
Also now that there is unlimited height for lapis, there should also be min height limit for consistency.

Had a lot to do at work yesterday and the WE was full of birthday parties, but I'll go look into it again now.
I guess I can use your height range slider you use for the unfiorm ores then, right?

Yes, you should use that.

Unit testing something like this comes down to computing a few values by hand or using a more simplified version of your math functions and then comparing the output. I. e. you have a complex 3d noise function, then you may be able to test it using well chosen values from a simpler 2d noise function.
You may also test for function properties like monotonicity  and so on.

Closing as a newer and cleaner PR was issued.


THUDM/CogVideoX-5b-I2V is producing jibberish output

System Info / 系統信息
diffusers               0.32.0.dev0
torch                   2.5.1+cu121
torchvision             0.20.1+cu121
python 3.11
Information / 问题信息

[X] The official example scripts / 官方的示例脚本
[ ] My own modified scripts / 我自己修改的脚本和任务

Reproduction / 复现过程
python inference/cli_demo.py --prompt "A young girl with sun-kissed hair and sparkling blue eyes stands in a lush, sunlit garden, her face radiant with a genuine smile that lights up her entire being. She wears a soft, floral dress that complements the vibrant blooms around her. As she tilts her head slightly, the sunlight catches the gentle curve of her smile, highlighting her joyful expression. Her hands are gently clasped in front of her, adding to the serene and happy atmosphere. The background is a tapestry of colorful flowers and greenery, enhancing the warmth and beauty of her smile." --model_path THUDM/CogVideoX-5b-I2V --generate_type "i2v" --num_frames 48 --image_or_video_path image.png --width 720 --height 480
https://github.com/user-attachments/assets/c7cd2013-41dd-4c95-9d94-ded741308e21
Expected behavior / 期待表现
I tried the same image here and output was fine
https://huggingface.co/spaces/THUDM/CogVideoX-5B-Space

num_frames must be 81 or 161. If the documentation. I see it mentioned in the docs here: https://huggingface.co/docs/diffusers/main/en/api/pipelines/cogvideox.
Looks like the table rendering is broken, so will fix that in a follow-up PR

@a-r-r-o-w
I am using --model_path THUDM/CogVideoX-5b-I2V, I think it supports less than 49 frames.
THUDM/CogVideoX1.5-5b-I2V supports 81 frames.
Is my understanding wrong?

Oh really sorry, I misread the model id. 49 frames is indeed correct here, but I see that you have 48 frames specified in the command. The I2V model is very sensitive to this and that's probably why you're seeing this tile patterns

So what do you suggest. Please if you can guide on how to do inference using v1 i2v.

Try running inference with height=480, width=720 and num_frames=49. I don't get any artifacts running the pure Diffusers example. I will take a look at the file in question soon as well to see if there are any bugs

@a-r-r-o-w
Is there any idea why the I2V model is too sensitive to num_frames?
And wouldn't this issue happen in 5B-I2V-v1.5?


Move autocomplete JS and CSS to top-level layout.html

Should we make the class something like .autocomplete_path so we could add autocomplete for other things later (like .autocomplete_job_id or something)?

Can you also add this class to custom_network_snapshot on "classificationModel#new" and "genericModel#new" and to all the fields at "genericDataset#new"?
I was going to create a pull request to do this, but I would be stepping on your work here too much. I'll just let you do it.

Hi Luke, thanks for the comments, I will propose another patch.

Looks great, thanks!


SPIKE: Investigate bringing on Community NextJS Storefront project

There is a community-created project that integrates NextJS with OC. Let's do some investigation into:

What the quality of the project
Is the creator interesting in this becoming an "official" project
What would be need to make it replace example storefront

Could you share the link of this project ? I didn't find it on github.
FYI, I found an "old" code to integrate OC with Vue Storefront, didn't try it https://github.com/pondigitalsolutions/rc-storefront-api

@triomen https://github.com/tedraykov/airfit-storefront

Closing this as we have decided to move forward with building our own NextJS Storefront implementation


Update shoot-rsyslog-relp jobs to<EMAIL_ADDRESS>

/kind enhancement
What this PR does / why we need it:
Related PR on shoot-rsyslog-relp side - ref https://github.com/gardener/gardener-extension-shoot-rsyslog-relp/pull/73
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

/lgtm
/approve


Add messageFilter config

Fixes https://github.com/AtomLinter/linter-ui-default/issues/26

@Arcanemagus Do we really have to do this? Can't we just disable the panel and rely on bubble if we want to get messages for current line? I will have to kill a lot of optimizations to do this

Personally the tooltip is fine since it actually shows all messages now instead of the first one.
I think my only requirement for not having this would be the messages being properly sorted in the list so you can find all the relevant messages for a line by scrolling through that if needed.

Now that we show all of messages in bubble, I don't think we need this


Restructure into monorepo

What is the difference between test-packages and test-projects?
This appears to keep the actual test still in dummy in the addon. Future restructure to to extract that to a test-app as well?

What is the difference between test-packages and test-projects?

technically none.
Since we introduce packages folder (which is widely used for monorepos) makes sense just to rename "projects" in to "packages" for consistency

This appears to keep the actual test still in dummy in the addon. Future restructure to to extract that to a test-app as well?
Correct! Kept PR focused as extracting dummy app into test app would take another ~100 files changes

I may have misread the PR, so many files changed. It looked like the end result would have both, didnt notice it was just a rename, wouldnt have ask. will look some more

The scripts like link.sh used to share the node_modules amoung all the projects. With the workspaces assuming the scripts are no longer needed. Nice

It seems this file https://github.com/miragejs/ember-cli-mirage/pull/2395/files#diff-f79b9ecbffd42f337bfa51417cd40e5a274ce039d5042b27cc64cebf1558a1a0 was a .gitkeep renamed to ci.yml but thinking this file and directory should not be here. Could be misreading PR again

Is there suppose to be an empty file at `packages/ember-cli-mirage/.github/workflows/ci.yml?

it was already removed, thanks for noticing!


random_password as auth_token rotation causes destroy and create because of transit_encryption handling != nuill

Found a bug? Maybe our Slack Community can help.

Describe the Bug
If one tries to set a new dynamic auth_token the way this module is written it will cause a destroy and create of the redis cache. The upstream aws provider added this support here.
The way transit_encryption_enabled is handled causes a destroy create when the auth_token is changed with a random_password as a source. Any dynamic input for auth_token causes this, a string literal will not replicate this issue. Because a string literal will be known at plan time. The work around with random_password has to be in state for us to get good modify only behavior.
Because the conditional var.transit_encryption_enabled || var.auth_token != null when auth_token is rotated but not yet known, terraform assumes the worst and I believe this causes the destroy create. (Credits to apparentlymart in the hangops slack. Thread here)
Expected Behavior
Using random_password to generate an auth_token and rotating it, I expected the redis cache to be modified not, destroy/created again. This is more disruptive than it has to be.
Steps to Reproduce
See this gist as a reference.

Apply random_password.password, aws_elasticache_replication_group.default and module.redis.
At the same time uncomment the code for random_password.password2 and use it in both redis blocks. (you'll see the resource works fine where the module destroy creates.)

the key to the above is in the same plan/apply phase we have to be adding a dynamic auth_token value which isn't fully known at plan time.

You'll see the redis cache get destroyed and recreated

The work around with the code as it is written is:

Apply random_password.password, aws_elasticache_replication_group.default and module.redis.
Plan and apply just random_password.password2 but do not reference it in the redis blocks.
Once password2 is known in state, use it as the auth_token in both redis blocks
this will only modify the cache instead of destroy create because the auth_token will be fully known since it's in the state.

Screenshots
If applicable, add screenshots or logs to help explain your problem.
Environment (please complete the following information):
OSX
terraform 1.3.1
aws provider 4.63.0
random provider 3.5.1
Anything that will help us triage the bug will help. Here are some ideas:

OS: [e.g. Linux, OSX, WSL, etc]
Version [e.g. 10.15]

Additional Context
Add any other context about the problem here.

Anyone truly working on fixing this?


Investigate popping noise on noisetorch

Using NoiseTorch creates a weird popping/crunchy sound that doesn't exist when using the mic raw.

moved to private task list


Need bigger switch/checkbox/radio buttons

Hi,
Currently you can change input sizes with .input-sm/.input-lg, but there is no equivalent for switch/checkbox/radio buttons.
These elements should be able to be resized.
Nice job by the way and thanks for the framework.

Seems legit.
But in case of checkboxes and radio buttons this would mean (correct me if I'm wrong), that they have to be overwritten to

even be resizable
match the look of the other form-controls

I'd say
.form-checkbox .form-icon.input-lg {
  height: 2.4rem;
  width: 2.4rem;
}
.form-checkbox input:checked + .form-icon.input-lg::after {
  height: 1.4rem;
  left: 46%;
  top: 38%;
  width: .8rem;
}

should be enough for the checkbox.
I don't understand the second point, they already have the same look and feel.

Could you post a test case e.g. CodePen?
Yeah, you're right. I withdraw my statement on the second point.

Actually I moved the logic to .checkform to fix the label positioning issue http://codepen.io/bybb/pen/aZZqrB

I forked your code and added a small version + radio buttons.
Positioning is not good, yet. But I will fix it and also append small and large switches.
Maybe we should also tweak the font-size.
http://codepen.io/tomlutzenberger/pen/zBBWdw?editors=1100

https://jsfiddle.net/Randore/6sw05zdL/
This roughly done but I think you should change the border-radius to 50% that will give perfect circle instead of using em (correct me, if I'm wrong)

@picturepan2 Was this issue closed because of inactivity or because there's now a way to make checkboxes / switches bigger? I can't seem to find a way to make them bigger using .input-lg or .label-lg.

@leroydev I closed it because I am not adding larger version of checkbox and switch.


Collection.gather requires identical names for values of type Item and Stream

While using something like Collection.gather(Task, sources, fetchedTasks$, 'uid') , I have to make sure fetchedTasks$ has objects where the property item is actually named item$. No idea why. This requires me to use a transformer like this:
function crazyHack(subCols: Stream<SubForCollection[]>): Stream<any> {
  return subCols.map( scs => scs.map(sc => {
    return {
      // For some reason, Collection wants submission to
      // be named submission$
      submission$: sc.submission,
      submission_id: sc.submission_id
    };
  }))

I then call e.g., Collection.gather(Task, sources, crazyHack(fetchedTasks$), 'uid').
This happened during an automatic refactor of naming submission to the more appropriate submission$ and took me hours to find, so I would advocate removing this dependence if possible.

gather uses the keys from snapshot object as keys for sources: https://github.com/cyclejs/collection/blob/master/src/collection.js#L201. I don't think it should append dollar sign automatically, but maybe it could accept a transformKey: (String) => String function as an argument

That sounds reasonable to me!


feat: Add support for generating json schemas using schemars

Adds support for generating JsonSchema for types by applying derive(JsonSchema) macro.
https://docs.rs/schemars/latest/schemars/
Hopefully the PR speaks for itself. I would like to preface that I am fairly new to the Rust language and package ecosystem, so let me know if there is anything that could be improved.
Cheers,
Jan

Thank you for PR.


Add unit tests for EligibilityBedrooms React component

Issue

Addresses #219

Description
This change adds two tests for the EligibilityBedrooms React component: one to check that it renders successfully and the other to check that an error message shows up at the appropriate time.
Type of change

[X] Adds a test

How Can This Be Tested/Reviewed?
cd sites/public && yarn test:unit-tests
Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have reviewed the changes in a desktop view
[ ] I have reviewed the changes in a mobile view
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have assigned reviewers
[ ] I have updated the changelog to include a description of my changes

There are some warnings in the test output:
    console.error
      Warning: An update to EligibilityBedrooms inside a test was not wrapped in act(...).

      When testing, code that causes React state updates should be wrapped into act(...):

      act(() => {
        /* fire events that update state */
      });
      /* assert on the output */

      This ensures that you're testing the behavior the user would see in the browser. Learn more at https://fb.me/react-wrap-tests-with-act
          in EligibilityBedrooms

Resolved this (by adding the act wrapping), and that caused other warnings to be converted to errors, but I fixed those also (by mocking useRouter) and now this just succeeds without errors/warnings :)


[Improvement] add REST catalog backend for Iceberg catalog

What would you like to be improved?
Iceberg catalog supports hive,jdbc catalog backend in WEB,  we need to support rest catalog backend too, it only supports uri properties.
How should we improve?
No response

Hi, I'd like to contribute by working on this issue if it's available. Please let me know if I can take it on.

hi @TungYuChiang Thank you for your interest this issue, I assigned to you, thanks.

Hi, I'd like to work on this issue . Could you assign it to me? Thanks

hi @liuchunhao I assign to you.

Hi, I'd like to work on this issue . Could you assign it to me? Thanks


Update matmul-advisor readme

Added instructions for how to run in batch mode on DevCloud.
Existing Sample Changes
Description
Added instructions for how to run in batch mode on DevCloud.
Fixes Issue#
External Dependencies
List any external dependencies created as a result of this change.
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Implement fixes for ONSAM Jiras
[ x] Documentation

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ x] Command Line
[ ] oneapi-cli
[ ] Visual Studio
[ ] Eclipse IDE
[ ] VSCode
[ ] When compiling the compliler flag "-Wall -Wformat-security -Werror=format-security" was used

@Kevinpoleary please review the changes and approve the PR if there are no further changes needed.


Emulate difference between destroy and destroy! in default ActiveRecord

In ActiveRecord, destroy! raises ActiveRecord::RecordNotDestroyed if before_destroy aborts, whereas destroy just returns false. ActsAsParanoid should do the same.

@mvz thank you for bringing this up, any plan on this? cheers

No, there's no work in progress on this. Pull requests welcome, of course.

@mvz PR filed https://github.com/ActsAsParanoid/acts_as_paranoid/pull/240, please help to review, cheers

Fixed in #240


Multiple camunda-spring-boot apps can connect to a single database

For this to work, we must register the deployment (PA) and configure the job executor accordingly so the jobExecutorDeploymentAware flag is working correctly.

Duplicate of #25


Difference between the paper and the code

Hi, Steven Walton
Thank you for sharing your amazing work!
If feasible, I would like to ask a question.
In the paper I found that "ViT, by default, uses a dropout for the MLP heads only with a probability of 0.1, and no attention dropout.Conversely, we do not use MLP dropout and only use attention dropout (p = 0.1)." However, in utils/transformers.py I found:
src_temp = self.activation(self.linear1(src))
src2 = self.linear2(self.dropout1(src_temp))
src = src + self.drop_path(self.dropout2(src2))

I wonder whether my understanding is wrong. I’d really appreciate it if you can let me know.

Hey Haelles,
If you look at src/cct:231 you'll see that we hard code CCT (and CVT) to have a dropout of 0. Though ViTLite line 161 has a dropout of 0.1.
The lines that you are looking at (src/transformers.py:62) are called by all the models. They all use the same Transformer Encoder structure. But CCT and CVT will not apply dropout and you can safely ignore that for those models, unless you want to do some hyper parameter testing yourself.
I can see the ambiguity in how we wrote it. We'll make sure this is more clear in the next version of the paper. Thank you!

Hey Haelles,
If you look at src/cct:231 you'll see that we hard code CCT (and CVT) to have a dropout of 0. Though ViTLite line 161 has a dropout of 0.1.
The lines that you are looking at (src/transformers.py:62) are called by all the models. They all use the same Transformer Encoder structure. But CCT and CVT will not apply dropout and you can safely ignore that for those models, unless you want to do some hyper parameter testing yourself.
I can see the ambiguity in how we wrote it. We'll make sure this is more clear in the next version of the paper. Thank you!

Thank you for your reply.
If I may ask again, I added print(self.dropout1) at src/transformers.py:62 and got Dropout(p=0.1, inplace=False). I think there is something wrong here src/cct.py:109, the value of parameter "dropout" should be "dropout" rather than "dropout_rate". The value of "dropout_rate" is 0.1 here.
Really appreciate your help!

Hello @Haelles
Thank you for bringing this to our attention. We noticed there was a small key mismatch in this version, and we just fixed it in the latest commit (619f4bee334c132b444438e893df2cb7180a082d).

Thanks for your response!


[feature request] send GPS location

It would be great if ChatSecure would be able to send the current phone location (from GPS) via a Google maps url and/or a small maps image with the location.

yes, it would! we are working on this for a future release. you can share a location from Google Maps into ChatSecure currently.


How solve tooltip error

http://<IP_ADDRESS>/rastreadorgps/rastreame/
I need how solve tooltip error
Tnks

@johnfelipe your link seems down...


How to make the task hidesecret ?

I am getting this error:
Task 'hideSecret' not found in project ':app'.
Please help.
C:\Users\abhiv\AndroidStudioProjects\Testing\app>gradle hideSecret -Pkey=loveabhishek [-PkeyName=first] [-Ppackage=com.example.testing] --info
Initialized native services in: C:\Users\abhiv\.gradle\native
The client will now receive all logging from the daemon (pid: 26056). The daemon log file: C:\Users\abhiv\.gradle\daemon\6.5.1\daemon-26056.out.log
Starting 7th build in daemon [uptime: 4 mins 27.496 secs, performance: 98%]
Using 16 worker leases.
Starting Build
Settings evaluated using settings file 'C:\Users\abhiv\AndroidStudioProjects\Testing\settings.gradle'.
Projects loaded. Root project using build file 'C:\Users\abhiv\AndroidStudioProjects\Testing\build.gradle'.
Included projects: [root project 'Testing', project ':app']

> Configure project :
Evaluating root project 'Testing' using build file 'C:\Users\abhiv\AndroidStudioProjects\Testing\build.gradle'.
Unzip jar to C:\Users\abhiv\AndroidStudioProjects\Testing\build/hidden-secrets-tmp

> Configure project :app
Evaluating project ':app' using build file 'C:\Users\abhiv\AndroidStudioProjects\Testing\app\build.gradle'.
Creating configuration androidTestUtil
All projects evaluated.
Analytics other plugin to proto: Unknown plugin type com.klaxit.hiddensecrets.HiddenSecretsPlugin expected enum COM_KLAXIT_HIDDENSECRETS_HIDDENSECRETSPLUGIN

FAILURE: Build failed with an exception.

* What went wrong:
Task 'hideSecret' not found in project ':app'.

* Try:
Run gradle tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s

Hello @kuabhish how did you integrate the plugin in your project, can you share your gradle file please ? Did you sync your project after ? Do you see logs about fetching the plugin ?

Hey @ben-j69  yes i have tried to inteegrate best to my knowledge.  I have attached both build.gradle files. (app level and root level)
Yes i synced the project. Yeah the logs appeared i think.
plugins {
    id 'com.android.application'
}
apply plugin: 'kotlin-android'

android {
    compileSdkVersion 30
    buildToolsVersion "30.0.2"

    defaultConfig {
        applicationId "com.example.testing"
        minSdkVersion 16
        targetSdkVersion 30
        versionCode 1
        versionName "1.0"

        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    // Enable NDK build
    externalNativeBuild {
        cmake {
//            version "3.9.1"
            path "src/main/resources/cpp/CMakeLists.txt"
        }
    }
}

dependencies {

    implementation 'androidx.appcompat:appcompat:1.1.0'
    implementation 'com.google.android.material:material:1.1.0'
    implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
    testImplementation 'junit:junit:4.+'
    androidTestImplementation 'androidx.test.ext:junit:1.1.1'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0'

    implementation 'com.github.bumptech.glide:glide:4.11.0'
    annotationProcessor 'com.github.bumptech.glide:compiler:4.11.0'

    implementation platform('com.google.firebase:firebase-bom:26.1.0')
    implementation 'com.google.firebase:firebase-analytics'
    implementation 'com.google.firebase:firebase-dynamic-links'
    implementation 'com.google.firebase:firebase-messaging'
    implementation "androidx.core:core-ktx:1.3.2"
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}
repositories {
    mavenCentral()
}

// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
    ext.kotlin_version = '1.4.20'
    repositories {
        google()
        jcenter()
        maven {
            url "https://plugins.gradle.org/m2/"
        }
    }
    dependencies {
        classpath "com.android.tools.build:gradle:4.1.1"
        classpath "com.klaxit.hiddensecrets:HiddenSecretsPlugin:0.1.0"
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        google()
        jcenter()
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

apply plugin: 'com.klaxit.hiddensecrets'

Thanks, in the README.md it is indicated that you must add the plugin in your app level gradle file, not in the top level one. Please follow the README step by step to use the plugin. That might fix your issue ;)

Hey @ben-j69
Now I am seeing new error.
C:\Users\abhiv\AndroidStudioProjects\dummy>gradle hideSecret -Pkey=ilovemylife [-Ppackage=com.example.dummy] --info
Initialized native services in: C:\Users\abhiv\.gradle\native
Found daemon DaemonInfo{pid=2760, address=[a915fb1f-4c43-48cb-b260-6fa1c69a3233 port:63557, addresses:[/<IP_ADDRESS>]], state=Idle, lastBusy=1606660822766, context=DefaultDaemonContext[uid=99d43b77-9ff7-492d-a3fb-4c6c6a4cad86,javaHome=C:\Program Files\Java\jre1.8.0_271,daemonRegistryDir=C:\Users\abhiv\.gradle\daemon,pid=2760,idleTimeout=10800000,priority=NORMAL,daemonOpts=-XX:MaxMetaspaceSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xms256m,-Xmx512m,-Dfile.encoding=windows-1252,-Duser.country=US,-Duser.language=en,-Duser.variant]} however its context does not match the desired criteria.
At least one daemon option is different.
Wanted: DefaultDaemonContext[uid=null,javaHome=C:\Program Files\Java\jre1.8.0_271,daemonRegistryDir=C:\Users\abhiv\.gradle\daemon,pid=13852,idleTimeout=null,priority=NORMAL,daemonOpts=-Xmx2048m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]
Actual: DefaultDaemonContext[uid=99d43b77-9ff7-492d-a3fb-4c6c6a4cad86,javaHome=C:\Program Files\Java\jre1.8.0_271,daemonRegistryDir=C:\Users\abhiv\.gradle\daemon,pid=2760,idleTimeout=10800000,priority=NORMAL,daemonOpts=-XX:MaxMetaspaceSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xms256m,-Xmx512m,-Dfile.encoding=windows-1252,-Duser.country=US,-Duser.language=en,-Duser.variant]

  Looking for a different daemon...
Found daemon DaemonInfo{pid=2288, address=[00b13798-c963-4a5c-b10d-71281a7ce389 port:65229, addresses:[/<IP_ADDRESS>]], state=Idle, lastBusy=1606661101331, context=DefaultDaemonContext[uid=4d2f88f4-aade-4fa4-b7df-925eb9883766,javaHome=C:\Program Files\Java\jre1.8.0_271,daemonRegistryDir=C:\Users\abhiv\.gradle\daemon,pid=2288,idleTimeout=10800000,priority=NORMAL,daemonOpts=-Xmx2048m,-Dfile.encoding=windows-1252,-Duser.country=US,-Duser.language=en,-Duser.variant]} however its context does not match the desired criteria.
At least one daemon option is different.
Wanted: DefaultDaemonContext[uid=null,javaHome=C:\Program Files\Java\jre1.8.0_271,daemonRegistryDir=C:\Users\abhiv\.gradle\daemon,pid=13852,idleTimeout=null,priority=NORMAL,daemonOpts=-Xmx2048m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]
Actual: DefaultDaemonContext[uid=4d2f88f4-aade-4fa4-b7df-925eb9883766,javaHome=C:\Program Files\Java\jre1.8.0_271,daemonRegistryDir=C:\Users\abhiv\.gradle\daemon,pid=2288,idleTimeout=10800000,priority=NORMAL,daemonOpts=-Xmx2048m,-Dfile.encoding=windows-1252,-Duser.country=US,-Duser.language=en,-Duser.variant]

  Looking for a different daemon...
The client will now receive all logging from the daemon (pid: 9364). The daemon log file: C:\Users\abhiv\.gradle\daemon\6.5.1\daemon-9364.out.log
Starting 9th build in daemon [uptime: 14 mins 16.951 secs, performance: 96%]
Using 16 worker leases.
Starting Build
Settings evaluated using settings file 'C:\Users\abhiv\AndroidStudioProjects\dummy\settings.gradle'.
Projects loaded. Root project using build file 'C:\Users\abhiv\AndroidStudioProjects\dummy\build.gradle'.
Included projects: [root project 'dummy', project ':app']

> Configure project :
Evaluating root project 'dummy' using build file 'C:\Users\abhiv\AndroidStudioProjects\dummy\build.gradle'.
Invalidating in-memory cache of C:\Users\abhiv\.gradle\caches\journal-1\file-access.bin

> Configure project :app
Evaluating project ':app' using build file 'C:\Users\abhiv\AndroidStudioProjects\dummy\app\build.gradle'.
Compiling build file 'C:\Users\abhiv\AndroidStudioProjects\dummy\app\build.gradle' using SubsetScriptTransformer.
Compiling build file 'C:\Users\abhiv\AndroidStudioProjects\dummy\app\build.gradle' using BuildScriptTransformer.
Invalidating in-memory cache of C:\Users\abhiv\AndroidStudioProjects\dummy\.gradle\buildOutputCleanup\outputFiles.bin
Creating configuration androidTestUtil
Unzip jar to C:\Users\abhiv\AndroidStudioProjects\dummy\app\build/hidden-secrets-tmp
android.ndkVersion from module build.gradle is [not set]
android.ndkPath from module build.gradle is not set
ndk.dir in local.properties is not set
Not considering ANDROID_NDK_HOME because support was removed after deprecation period.
sdkFolder is C:\Users\abhiv\AppData\Local\Android\Sdk
Because no explicit NDK was requested, the default version [21.1.6352462] for this Android Gradle Plugin will be used
All projects evaluated.
Analytics other plugin to proto: Unknown plugin type com.klaxit.hiddensecrets.HiddenSecretsPlugin expected enum COM_KLAXIT_HIDDENSECRETS_HIDDENSECRETSPLUGIN

FAILURE: Build failed with an exception.

* What went wrong:
Task '[-Ppackage=com.example.dummy]' not found in root project 'dummy'.

* Try:
Run gradle tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s

If you want to see my gradle files I will also attach them ..:
apply plugin: 'com.android.application'
apply plugin: 'com.klaxit.hiddensecrets'

android {
    compileSdkVersion 28
    buildToolsVersion "28.0.3"

    defaultConfig {
        applicationId "com.example.dummy"
        minSdkVersion 16
        targetSdkVersion 28
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    externalNativeBuild {
        cmake {
            path "src/main/cpp/CMakeLists.txt"
        }
    }
}

dependencies {
    implementation 'androidx.appcompat:appcompat:1.2.0'
    implementation 'com.google.android.material:material:1.2.1'
    implementation 'androidx.constraintlayout:constraintlayout:2.0.4'
    testImplementation 'junit:junit:4.+'
    androidTestImplementation 'androidx.test.ext:junit:1.1.2'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.3.0'
}

repositories {
    mavenCentral()
}

// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
    ext.kotlin_version = '1.4.20'
    repositories {
        google()
        jcenter()
        maven {
            url "https://plugins.gradle.org/m2/"
        }
    }
    dependencies {
        classpath "com.android.tools.build:gradle:4.1.1"
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
        classpath "com.klaxit.hiddensecrets:HiddenSecretsPlugin:0.1.0"

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        google()
        jcenter()
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

Also I got this while building the project with the gradle files pasted above.
> Configure project :app
Unzip jar to C:\Users\abhiv\AndroidStudioProjects\dummy\app\build/hidden-secrets-tmp

> Task :prepareKotlinBuildScriptModel UP-TO-DATE
Gradle project cmake.path is C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp\CMakeLists.txt but that file doesn't exist
Gradle project cmake.path is C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp\CMakeLists.txt but that file doesn't exist
Gradle project cmake.path is C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp\CMakeLists.txt but that file doesn't exist
Gradle project cmake.path is C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp\CMakeLists.txt but that file doesn't exist
Gradle project cmake.path is C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp\CMakeLists.txt but that file doesn't exist
Gradle project cmake.path is C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp\CMakeLists.txt but that file doesn't exist
Gradle project cmake.path is C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp\CMakeLists.txt but that file doesn't exist
Gradle project cmake.path is C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp\CMakeLists.txt but that file doesn't exist
C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp\CMakeLists.txt : C/C++ debug|x86 : Not a directory: C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp
C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp\CMakeLists.txt : C/C++ debug|x86 : Failed to activate protocol version: "sourceDirectory" is not a directory.
C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp\CMakeLists.txt : C/C++ debug|x86 : Waiting for type "handshake".
executing external native build for cmake C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\cpp\CMakeLists.txt

BUILD SUCCESSFUL in 983ms

Dot not use [ and ] they means the parameter is optional in the documentation. So if your app has the package com.example.dummy the command line to hide a secret should look like
gradle hideSecret -Pkey=ilovemylife -Ppackage=com.example.dummy
To check that the plugin is well integrated in your app you can run a simple command :
gradle obfuscate -Pkey=ilovemylife  should succeed and display an obfuscated key as hexadecimal array.

Awesome bro .. that worked ..
I saw this output :
### KEY NAME ###
TNWDPJXI

### SECRET ###
ilovemylife

### PACKAGE NAME ###
com.example.dummy

### OBFUSCATED SECRET ###
{ 0xf, 0x5a, 0xb, 0x10, 0x51, 0x55, 0x41, 0x5c, 0xc, 0x54, 0x5d }
You can now get your secret key by calling : Secrets().getTNWDPJXI(packageName)

But another error I see now:
C:\Users\abhiv\AndroidStudioProjects\dummy\app\src\main\java\com\example\dummy\MainActivity.java:13: error: cannot find symbol
        String key = new Secrets().getTNWDPJXI(getPackageName());
                         ^
  symbol:   class Secrets
  location: class MainActivity

where my code is
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);
        String key = new Secrets().getTNWDPJXI(getPackageName());
        System.out.println(key);

obfuscate is only a command to display keys it does nothing in your project.
To copy kotlin, c++ and really hide a key you need to use the command hideSecret Then you should find a Secrets.kt file in your project that you can import anywhere.

I tried both commands -
gradle obfuscate -Pkey=ilovemylife
and after this
gradle hideSecret -Pkey=ilovemylife -Ppackage=com.example.dummy
i got this output
### KEY NAME ###
TNWDPJXI

### SECRET ###
ilovemylife

### PACKAGE NAME ###
com.example.dummy

### OBFUSCATED SECRET ###
{ 0xf, 0x5a, 0xb, 0x10, 0x51, 0x55, 0x41, 0x5c, 0xc, 0x54, 0x5d }
You can now get your secret key by calling : Secrets().getTNWDPJXI(packageName)

and I found Secrets.kt in my project in the same directory as MainActivity.
I imported and it didn't show any error there here:
        String key = new Secrets().getTNWDPJXI(getPackageName());
        System.out.println(key);

But while building or running the app it shows error.

It looks like the plugin work well if Secrets.kt and the C++ code is n your app. If your app does not compile it is not because of the plugin. You should check again your imports, Android Studio would not let you compile with errors like this.

Hey @ben-j69
Thanks for all the help. It is solved.

@kuabhish Can you please explain how you solved this issue? I have the same error.

It looks like the plugin work well if Secrets.kt and the C++ code is n your app 👍 .
If your app does not compile it is not because of the plugin. You should check again your imports, Android Studio would not let you compile with errors like this.

Getting same error

Hey @ben-j69
Thanks for all the help. It is solved.

how to resolved this error

Hey @ben-j69
Thanks for all the help. It is solved.

Please help me to resolve this issue