text:
bpf: add libbpf 8.0 support

[x] Baseline support for libxdp 1.2.5 and libbpf 0.8.0
[x] Update readme to show how to build and install libxdp 1.2.5 and libbpf 0.8.0
[x] Update implementation to use USE_LIBXDP and USE_LIBBPF_8 directly

Hey folks
I'm not sure why the smoke test fails... when trying to use the USE_* flags directly for the XDP build
I've tried to replicate the failure on fresh ubuntu 22.04 container and haven't been able to. The build seems to pass.
Would appreciate any insight you may have as to why we see the error below if we don't use the flags from cne_common.h
FAILED: lib/core/xskdev/4934eeb@@cne_xskdev@sha/xskdev.c.o
cc -Ilib/core/xskdev/4934eeb@@cne_xskdev@sha -Ilib/core/xskdev -I../lib/core/xskdev -Ilib/include -I../lib/include -Ilib/core/osal -I../lib/core/osal -Ilib/core/log -I../lib/core/log -I. -I../ -Ilib/core/cne -I../lib/core/cne -Ilib/common/uds -I../lib/common/uds -Ilib/core/mmap -I../lib/core/mmap -Ilib/core/mempool -I../lib/core/mempool -Ilib/core/pktmbuf -I../lib/core/pktmbuf -I/usr/include/libnl3 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -Werror -O3 -g -Wno-pedantic -Wcast-qual -Wdeprecated -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -include cne_build_config.h -march=native -DCC_AVX2_SUPPORT -fPIC -MD -MQ 'lib/core/xskdev/4934eeb@@cne_xskdev@sha/xskdev.c.o' -MF 'lib/core/xskdev/4934eeb@@cne_xskdev@sha/xskdev.c.o.d' -o 'lib/core/xskdev/4934eeb@@cne_xskdev@sha/xskdev.c.o' -c ../lib/core/xskdev/xskdev.c
In file included from ../lib/core/xskdev/xskdev.c:28:
../lib/core/xskdev/xskdev.h:21:10: fatal error: xdp/xsk.h: No such file or directory
   21 | #include <xdp/xsk.h>
      |          ^~~~~~~~~~~
compilation terminated.

Is it because we have not installed libxdp on the test VMs or machines?

Is it because we have not installed libxdp on the test VMs or machines?

I don't think so... unless my logic in the meson file is not correct... it sets the USE_XDP flag to false then tries to find a suitable version of libxdp... if it's not found then that flag should remain false? I mean we even look for the header xdp/xsk.h :(
let me dig into it a little more

Is it because we have not installed libxdp on the test VMs or machines?

I don't think so... unless my logic in the meson file is not correct... it sets the USE_XDP flag to false then tries to find a suitable version of libxdp... if it's not found then that flag should remain false? I mean we even look for the header xdp/xsk.h :(
let me dig into it a little more

I managed to reproduce it... it looks like cne_conf.set10() wasn't being picked up properly? using cne_conf.set() seems to have fixed the issue

@KeithWiles I do have a stupid question... should I not need to define a xdp_dep in the dependency sets in the examples?
everything seems to compile and run as expected - but I'm just a little surprised as I didn't include xdp_dep in the dependency list for cndpfwd for example

The -lxdp should be enough as it is added to all link lines. The depend for libbpf and xdp_dep should not we used other then to find the libs. If we have it other places then it is not doing any harm I believe.

authors: KeithWiles maryamtahhan

repo: CloudNativeDataPlane/cndp


text:
Added my data

I have added my data into your codebase . plzz merge my code

Good job @Arpaninformationtech
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.
Note that this repo is excluded from Hacktoberfest but this PR is still eligible for ClueLess Swags.

Star this repository. ⭐

SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.

https://www.clueless.tech/profile/admin/100986138 @Rajdip019

source: gharchive/pull-request

repo: Clueless-Community/first-contribution

license: MIT

license_type: permissive

license_source: github-api


text:
BUG: test folder was deleted for different scrapers

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
It seems that in the previously merged PR #374, the test folder has been deleted. I would like to contribute to restore the test folder.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC 23 contributor
[X] I want to work on this issue

Hey @Mihan786Chistie | I deleted the test folder because it was not appropriate, if you are willing the add test files, go ahead and add them for the GitHub class.
Note

Covert test of each module of GitHub class in one defined class only.
For example - Add all the Users class and their methods in a single test class names UserTest.

Do let me know if you have any further doubts :))

@nikhil25803 will the userTest file be inside the GitHub folder?

No @Mihan786Chistie | In the scrape-up folder, add a folder names test. In that create a file name GitHubTest.py and add your test script there.

No @Mihan786Chistie | In the scrape-up folder, add a folder names test. In that create a file name GitHubTest.py and add your test script there.

Ohhh ok thanks

source: gharchive/issue

repo: Clueless-Community/scrape-up


text:
Refactor: Use a User-Agent constant for HTTP requests

Description
By introducing a constant USER_AGENT for the User-Agent string, this commit improves code readability and reusability. The Academia class's init method now utilizes the constant, making it easier to manage and update the User-Agent across the class. This change enhances the clarity of the codebase and simplifies the process of maintaining the User-Agent header in future updates.
Checklist

Before submitting this pull request, kindly verify that the ensuing checkpoints have been reached.

[x] Have you adhered to the repository's defined coding convention rules?

I certify that I have carried out the relevant checks and provided the requisite screenshot for validation by submitting this pull request.
I appreciate your contribution.

@nikhil25803 could you please check this out?

The PR you raised doesn't make much difference.
From the next time, please start working on a project only after you get assigned to it.


text:
Create a feature card with image

One need to make this component using HTML and Tailwind CSS. I would suggest to use Tailwind Playgrounds to make things faster and quicker.
Here is a reference to the component.

After building the component please raise a PR with a screenshot of the component and add the component in Feature Card/feature-card-image.html.
If you need to use any icon please use it from Hero Icons
Good luck.

Yess @hritikbhattacharya

@Rajdip019 I have submitted the PR regarding this issue

repo: Clueless-Community/web-ui-kit


text:
[FLOC-2150] Wait for delete to complete before returning from destroy_volume.

flocker.node.agents.functional.test_ebs
EBSBlockDeviceAPIInterfaceTests
test_attach_destroyed_volume ...                                       [OK]

Ran 1 tests in 6.590s

It would be nice to have a test that directly demonstrates the expected behavior change (though green builder on thing that has been red forever does demonstrate that indirectly). However, once https://clusterhq.atlassian.net/browse/FLOC-2165 is done I expect the "deleted volumes aren't listed" test will actually cover this change, so I think that's OK.
So: address minor design improvement above, then merge if functional builder is green.

It would be nice to have a test that directly demonstrates the expected behavior change

test_attach_destroyed_volume consistently failed locally without the fix.
With the fix, it passed.

authors: itamarst myechuri

repo: ClusterHQ/flocker


text:
Set socket options correctly to re-use address/port

Running the broker throws up an error :
thread 'main' panicked at src/main.rs:595:68:
called Result::unwrap() on an Err value: Os { code: 48, kind: AddrInUse, message: "Address already in use" }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
running on localhost for unicast and multicast causes this error.
Quick fix: change port number used by unicast and multicast addresses when creating a socket.

It seems that this can be fixed by building each socket using socket2 and setting nonblocking, reuse address and reuse port for each, then transforming into a tokio UdpSocket (using from_std) before binding. Doing this allows the broker to use port 5683 on unicast and multicast.

The fix also works with just reuse port
https://stackoverflow.com/questions/14388706/how-do-so-reuseaddr-and-so-reuseport-differ/14388707#14388707
Basically in multicast, reuseaddr should work but for it isnt working quite as intended here.

authors: Kavan-M bsilverajan

repo: CoAPConnect/coap-pubsub-rust


text:
[Campinas] Dextra - Desenvolvedor iOS

Empresa
Desde 1995 no mercado de tecnologia, enxergamos a inovação como chave para nosso diferencial no mercado.
A Dextra é especialista no desenvolvimento de software sob medida para negócios digitais. Usamos processos de inovação, tecnologia e conhecimento do negócio para a criação de produtos digitais que colocam nossos clientes em um novo patamar de mercado.
Este ano fomos eleitos a 5ª MELHOR empresa brasileira de TI para se trabalhar no ranking do Great Place to Work de Tecnologia da Informação e em quarto lugar do ranking da América Latina!
Descrição da vaga
Se você é ávido por tecnologias de ponta e gosta de novos desafios...Aqui é o seu lugar!
Na Dextra os desenvolvedores são responsáveis pela expertise e conhecimento das tecnologias e propõem as melhores soluções técnicas durante todo o processo de desenvolvimento garantindo o sucesso da entrega para o cliente.
Posição
Desenvolvedor iOS Pleno / Sênior
Tipo de contratação
Contratação CLT para atuação de 40h semanais, com horário flexível e possibilidade de home office
Requisitos
O que você precisa saber para ocupar esta vaga?
Programar.. Mas com paixão!  Ser fera no desenvolvimento de aplicativos na plataforma iOS usando Objective-C e principalmente Swift; Desenvolver novas funcionalidades para os produtos digitais de nossos clientes  e ter conhecimento em desenvolvimento de telas para iOS (Storyboard, Auto Layout, componentes nativos, Views, criação de componentes customizados)
Benefícios
Além dos benefícios tradicionais possuímos: Horário flexível; Casual Day everyday; Sala PS3/ Espaço Relax; Planos de Carreira; Treinamentos internos; Mentoria e muito mais.
Como aplicar
Envie seu cv para recrutamento@dextra-sw.com ou se aplique em nosso site
Contato
Tamires Gomes - tamires.gomes@dextra-sw.com

Essa possiblidade de Home Office seria 100% remoto(outra cidade) ?

A possibilidade de home office é par time  ;)

Olá, vocês já pensaram em fazer outsourcing? Sai o mesmo preço de um funcionário, mas você tem uma equipe à disposição e com um contrato de prestação de serviços.

Como assim? Seria part-time home office + part-time e o restante presencial ou se for fazer home office, o trabalho fica só part-time?

Na Dextra valorizamos muito a interação entre equipe e a presença de todos os membros no dia a dia da empresa. Essa vaga é para contratação CLT com atuação de 40 horas semanais para atuação em nossa base em Campinas, contudo, caso haja interesse, trabalhamos com horários flexíveis e possibilidade de atuar em home office em alguns dias da semana. Espero ter sido mais clara ;) Abs

Ah, obrigado. Minha dúvida era mais essa. Se havia possibilidade de remoto. Obrigado
Sent from my iPhone

On 19 Apr 2017, at 12:55, tamiresmgomes notifications@github.com wrote:
Na Dextra valorizamos muito a interação entre equipe e a presença de todos os membros no dia a dia da empresa. Essa vaga é para contratação CLT com atuação de 40 horas semanais para atuação em nossa base em Campinas, contudo, caso haja interesse, trabalhamos com horários flexíveis e possibilidade de atuar em home office em alguns dias da semana. Espero ter sido mais clara ;) Abs
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

repo: CocoaHeadsBrasil/vagas


text:
超星平台一个页面多视频时，只会自动播放第一个，望更新！

错误描述
如图，在超星平台上，当一个学习页面中包括多个视频时，插件能够检测到所有视频，但是只能自动播放第一个，其它的视频需要手动点击开始挂机。

错误版本
Chrome 64.0
插件：超星慕课的小工具，版本：2.1.17

已经准备更新

新版本已经发布在商城,麻烦确认一下有没有解决

收到，非常感谢。
    1、一个页面多视频播放的问题已经解决。
    2、但是看见另一位提出issue：挂机需要手动进行操作，一个视频挂完，刷新页面到下一节，视频不会自动播放，小概率抽风。
        看他之前也提过这个问题，它的是fireFox，我的是Chrome，也出现这个问题：
        当跳转到下一个页面后，新视频会进入挂机过程，但是视频本身处于黑屏，需要手动点击一下页面，视频才会真正的播放。目前不确定是由于我自身网络问题，还是其它原因。
    再次感谢大佬！

Best wishes,
                                      Yours,
                             Tian yongsheng
South-Central University For Nationalities
Wuhan, Hubei 430074, P.R.CHINA

------------------ 原始邮件 ------------------
发件人: "CodFrm"<notifications@github.com>;
发送时间: 2020年3月27日(星期五) 上午9:12
收件人: "CodFrm/cxmooc-tools"<cxmooc-tools@noreply.github.com>;
抄送: "田永胜"<tiansheng.33@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [CodFrm/cxmooc-tools] 超星平台一个页面多视频时，只会自动播放第一个，望更新！ (#126)
新版本已经发布在商城,麻烦确认一下有没有解决
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

authors: CodFrm StudentWH

repo: CodFrm/cxmooc-tools


text:
increase k 3-->5

low k causes forks.
intent is that k > (2*delay)+1

Closing due to duplicated work in https://github.com/CodaProtocol/coda/pull/3166 (also, we want a k greater than 5 specifically for the staking network release).

repo: CodaProtocol/coda


text:
Identifier 'AppExport' has already been declared

I am using Remix Vite and have followed all the instructions,  but I get the following error when running remix vite:dev
[vite] Error when evaluating SSR module /app/root.tsx:
|- SyntaxError: Identifier 'AppExport' has already been declared
    at new AsyncFunction (<anonymous>)
    at instantiateModule (file:///xxx)

10:24:24 AM [vite] Error when evaluating SSR module virtual:remix/server-build: failed to import "/app/root.tsx"
|- SyntaxError: Identifier 'AppExport' has already been declared
    at new AsyncFunction (<anonymous>)
    at instantiateModule (file:///xxx)

10:24:24 AM [vite] Internal server error: Identifier 'AppExport' has already been declared
      at new AsyncFunction (<anonymous>)
      at instantiateModule (file:///xxx)

These are the changes I made in root.tsx
import rdtStylesheet from "remix-development-tools/index.css";
export const links: LinksFunction = () => [

  ...(process.env.NODE_ENV === "development" ? [{ rel: "stylesheet", href: rdtStylesheet }] : []),
]

function App() {
//
}

let AppExport = App;

if(process.env.NODE_ENV === 'development') {
  const { withDevTools } = await import("remix-development-tools");
  AppExport = withDevTools(AppExport);
}

export default AppExport;

Fixed it, for Vite nothing else but the plugin in the vite.config needs to be added.

repo: Code-Forge-Net/Remix-Dev-Tools


text:
Various stats

@lailahr
This makes stuff like this available in jekyll:
site.data.gazettes.stats.count
site.data.gazettes.stats.earliest_year
site.data.gazettes.stats.latest_year

In addition, site.data.gazettes.stats.years[2015] is the number of gazettes in that year, which could be a fun mini-vis somewhere.

license: mit

license_source: bigquery


text:
Fix Wazimap favicon

@longhotsummer
I find it weird that the previous code didn't work as I thought it would. Anyway.

👍

authors: longhotsummer xybrnet


text:
Wheel: Multiple Value Change on One Swipe

I see your commit https://github.com/MudBlazor/MudBlazor/commit/046c46bc6995213d2d6bb230b8766b734fa45d6e so I think you already know that rotating wheels on a smartphone is a very slow experience.
I hope to use MudDateWheelPicker when a swipe will create a little acceleration...

It was a limitation due to MudSwipeArea component. With the latest Mud version we merged a PR that added sensitivity to swipe area, so we can also improve swipe behavior on wheels.

@mckaragoz despite the Sensitivity parameter the behaviour is like before: one swipe change only one unit at a time.

Ah yes, i know we also should add multiple changes per x sensitivity, but i think it needs some more work. Maybe need to change more codes into core library first.

A nice feature would be 3D effect like https://demo.mobiscroll.com/fullscreen/datetime/mobile-desktop-usage

@GioviQ  I think now we support multiple value change. I already changed the core library to support this feature.
https://user-images.githubusercontent.com/78308169/231787999-e82ef011-584b-4a83-99c2-516d23bf5d44.mp4
Note: It does not really work on real time (ontouchmove) but at least changed multiple value ontouchend.

authors: GioviQ mckaragoz


text:
提示"授权页已存在，不能再次拉起"

Describe the bug
拉取项目（1.1.5版本）运行到安卓手机上，点击第一个“开始全屏登录按钮”进入登录页面后，不要点击登录按钮，而是关闭当前页面（返回手势），再次点击“开始全屏登录按钮”时，无法再次唤起登录页面。
日志：
I/ConnectivityManager(29875): getMobileDataEnabled()- subId=1 retVal=true
I/OneKeyLoginPublic(29875): checkEnvAvailable：{"carrierFailedResultData":"","code":"600002","msg":"授权页已存在，不能再次拉起","requestCode":0,"requestId":"30ab96c5-4742-472e-b7ab-885e751bea8d","vendorName":"cu_xw"}
I/OneKeyLoginPublic(29875): checkEnvAvailable：{"carrierFailedResultData":"","code":"600024","msg":"终端支持认证","requestCode":0,"requestId":"33478e53-e92b-41f9-bf40-f0a4333a889d","vendorName":"cu_xw"}
I/flutter (29875): ----------------> {msg: 唤起授权⻚失败！建议切换到其他登录⽅式, code: 600002, data: null} <----------------
I/flutter (29875): ----------------> {msg: 终端环境检查⽀持认证, code: 600024, data: null} <----------------

Flutter (Channel stable, 3.13.8, on Microsoft Windows [版本 10.0.19042.630], locale zh-CN)
    • Flutter version 3.13.8 on channel stable at D:\flutter\flutter
    • Upstream repository https://github.com/flutter/flutter/
    • FLUTTER_GIT_URL = https://github.com/flutter/flutter/
    • Framework revision 6c4930c4ac (2 weeks ago), 2023-10-18 10:57:55 -0500
    • Engine revision 767d8c75e8
    • Dart version 3.1.4
    • DevTools version 2.25.0
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

Connected device (4 available)
    • WLZ AL10 (mobile) • FMLDU19C13016286 • android-arm64  • Android 12 (API 31)

弹窗的圆角是不是没起作用，有点突兀了

ios平台使用弹窗登录，没有勾选同意协议时，点击“切换到其他方式”按钮时会吐司提示“请先阅读用户协议”。点击“一键登录”按钮时反无提示。预期应该是点击“一键登录”按钮时提示“请先阅读用户协议”，点击“切换到其他方式”按钮无需同意协议。

调用 AliAuth.quitPage(); 先强制关闭就可以

今天运行报错了
[ +541 ms] Initialized native services in: C:\Users\lrj\.gradle\native [   +1 ms] Initialized jansi services in: C:\Users\lrj\.gradle\native [ +313 ms] Removing 0 daemon stop events from registry [        ] Previous Daemon (18840) stopped at Fri Nov 10 14:05:56 CST 2023 stop command received [        ] Starting a Gradle Daemon, 10 busy and 1 stopped Daemons could not be reused, use --status for details [  +94 ms] Starting process 'Gradle build daemon'. Working directory: C:\Users\lrj\.gradle\daemon\7.5 Command: D:\Program Files\Android\android-studio2  2023  3.1\jbr\bin\java.exe --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED --add-opens java.base/java.nio.charset=ALL-UNNAMED --add-opens java.base/java.net=ALL-UNNAMED --add-opens java.base/java.util.concurrent.atomic=ALL-UNNAMED -Xmx1536M -Dfile.encoding=GBK -Duser.country=CN -Duser.language=zh -Duser.variant -cp C:\Users\lrj\.gradle\wrapper\dists\gradle-7.5-all\8ocs8mtabk52vmng7wysmmfns\gradle-7.5\lib\gradle-launcher-7.5.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 7.5 [   +1 ms] Successfully started process 'Gradle build daemon' [+1207 ms] An attempt to start the daemon took 1.199 secs. [  +94 ms] The client will now receive all logging from the daemon (pid: 22344). The daemon log file: C:\Users\lrj\.gradle\daemon\7.5\daemon-22344.out.log [        ] Starting build in new daemon [memory: 1.5 GiB] [  +97 ms] Using 6 worker leases. [ +406 ms] Watching the file system is configured to be enabled if available [  +93 ms] Now considering [F:\test\flutter_ali_auth-master2\flutter_ali_auth-master\example\android] as hierarchies to watch [        ] File system watching is active [ +599 ms] Starting Build [ +299 ms] Settings evaluated using settings file 'F:\test\flutter_ali_auth-master2\flutter_ali_auth-master\example\android\settings.gradle'. [ +109 ms] Projects loaded. Root project using build file 'F:\test\flutter_ali_auth-master2\flutter_ali_auth-master\example\android\build.gradle'. [        ] Included projects: [root project 'android', project ':ali_auth', project ':app'] [+1990 ms] > Configure project : [        ] Evaluating root project 'android' using build file 'F:\test\flutter_ali_auth-master2\flutter_ali_auth-master\example\android\build.gradle'. [+1996 ms] > Configure project :app [        ] Evaluating project ':app' using build file 'F:\test\flutter_ali_auth-master2\flutter_ali_auth-master\example\android\app\build.gradle'. [        ] Using Kotlin Gradle Plugin gradle71 variant [        ] Caching disabled for Kotlin DSL script compilation (Project/ScriptPlugin/stage1) because: [        ]   Build cache is disabled [        ] Skipping Kotlin DSL script compilation (Project/ScriptPlugin/stage1) as it is up-to-date. [        ] Parsed shrinker version: 3.3.83 [ +508 ms] > Configure project :ali_auth [        ] Evaluating project ':ali_auth' using build file 'F:\test\flutter_ali_auth-master2\flutter_ali_auth-master\android\build.gradle'. [        ] Compiling build file 'F:\test\flutter_ali_auth-master2\flutter_ali_auth-master\android\build.gradle' using SubsetScriptTransformer. [        ] Compiling build file 'F:\test\flutter_ali_auth-master2\flutter_ali_auth-master\android\build.gradle' using BuildScriptTransformer. [        ] Could not execute [class org.jetbrains.kotlin.gradle.plugin.statistics.KotlinBuildStatHandler.buildFinished] [        ] FAILURE: Build completed with 2 failures. [   +1 ms] 1: Task failed with an exception. [        ] ----------- [        ] * Where: [        ] Build file 'F:\test\flutter_ali_auth-master2\flutter_ali_auth-master\android\build.gradle' line: 40 [        ] * What went wrong: [        ] A problem occurred evaluating project ':ali_auth'. [        ] > Could not find method android() for arguments [build_82xe29y13ws6ykchb222d21t$_run_closure2@1329eff3] on project ':ali_auth' of type org.gradle.api.Project. [        ] * Try: [        ] > Run with --debug option to get more log output. [        ] > Run with --scan to get full insights. [        ] * Exception is: [        ] org.gradle.api.GradleScriptException: A problem occurred evaluating project ':ali_auth'. [        ]      at org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93) [        ]      at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.lambda$apply$0(DefaultScriptPluginFactory.java:133) [        ]      at org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:79) [        ]      at org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:136) [        ]      at org.gradle.configuration.BuildOperationScriptPlugin$1.run(BuildOperationScriptPlugin.java:65) [        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29) [        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26) [        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66) [        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59) [        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157) [        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59) [        ]      at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47) [        ]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:68) [        ]      at org.gradle.configuration.BuildOperationScriptPlugin.lambda$apply$0(BuildOperationScriptPlugin.java:62) [        ]      at org.gradle.configuration.internal.DefaultUserCodeApplicationContext.apply(DefaultUserCodeApplicationContext.java:44) [        ]      at org.gradle.configuration.BuildOperationScriptPlugin.apply(BuildOperationScriptPlugin.java:62)

圆角是需要结合背景使用，安卓要考虑主题


text:
🛑 The Polder Group is down

In f811535, The Polder Group (https://thepoldergroup.com) was down:

HTTP code: 521
Response time: 171 ms

Resolved: The Polder Group is back up in ef1c0b0 after 15 minutes.

repo: CodeIntel-Development/uptime


text:
Feature/categoria

Hola Henry,
En este pull request, he realizado las siguientes tareas:

Implementé la funcionalidad de agregar una nueva categoría.
Refactoricé el método save en la interfaz ICRUD para lanzar la excepción DataAlreadyExistsException cuando se intenta guardar una entidad que ya existe.
Actualicé la documentación relacionada con la nueva funcionalidad.
Añadí pruebas unitarias para asegurar el correcto funcionamiento de las nuevas funcionalidades.

Por favor, revisen los cambios y proporcionen sus comentarios y sugerencias. Estoy abierto a cualquier mejora o ajuste necesario.
¡Gracias!

Excelente trabajo con este pull request. He revisado los cambios y todo se ve muy bien. Los cambios implementados en la funcionalidad de agregar una nueva categoría y la redefinición del método save cumplen con nuestras expectativas y requisitos.
El código está bien estructurado, fácil de leer y sigue nuestras convenciones de codificación. También se han incluido pruebas unitarias adecuadas para garantizar la calidad del código.
Aprobado y listo para fusionar. ¡Gracias por tu contribución y esfuerzo en este desarrollo!

repo: CodeMentoring/ebook-api


text:
fix(GridForm): cancel + submit button

Overview

Fixes cancel button alignment in GridForm + add cancel button alignment to Storybook

PR Checklist

[x] Related to JIRA ticket: [web-2295]
[x] I have run this code to verify it works
[x] This PR includes unit tests for the code change
[x] This PR includes testing instructions tests for the code change
[x] The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories

Testing Instructions
Vist GridForm / Submit Button Position + Gridform / Cancel button sections in Storybook + observe how they are fixed
PR Links and Envs

Repository
PR Link
PR Env

Monolith
Monolith PR
Monolith Env

Portal
Portal Link
Portal Env

Another Repo
Another Link
Another Env

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.291-alpha.ec3a6e.0@codecademy/gamut-labs@35.7.1-alpha.ec3a6e.0@codecademy/gamut@52.1.1-alpha.ec3a6e.0@codecademy/monaco@0.7.10-alpha.ec3a6e.0@codecademy/styleguide@63.6.1-alpha.ec3a6e.0

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.293-alpha.8b70bf.0@codecademy/gamut-labs@35.8.0-alpha.8b70bf.0@codecademy/gamut@52.2.0-alpha.8b70bf.0@codecademy/monaco@0.7.12-alpha.8b70bf.0@codecademy/styleguide@63.7.0-alpha.8b70bf.0

🚀 Styleguide deploy preview ready!https://6412368611290d11cb3468ae--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.294-alpha.8bf9ce.0@codecademy/gamut-labs@35.8.1-alpha.8bf9ce.0@codecademy/gamut@52.2.1-alpha.8bf9ce.0@codecademy/monaco@0.7.13-alpha.8bf9ce.0@codecademy/styleguide@63.7.1-alpha.8bf9ce.0

🚀 Styleguide deploy preview ready!https://641367d86211813457beff63--gamut-preview.netlify.appDeploy Logs

authors: codecademydev dreamwasp

repo: Codecademy/gamut


text:
刷新状态补充

你的新功能建议是否牵扯到某个常见的问题？
刷新状态缺少了刷新完成的状态 导致自定义刷新头的时候缺了完成状态而不能满足需求
你希望达到的效果
增加刷新完成状态,即MJRefreshStateRefreshing之后变成MJRefreshStateDone(刷新完成)
你能考虑到的可选实现方案
描述一下你认为要实现这个功能，有哪些可行的一些实现方案？
在底层的实现中 刷新状态之后变为刷新完成状态,再次下拉的时候才变成待刷新状态

请使用 endRefreshingCompletionBlock

authors: puhahalx wolfcon

repo: CoderMJLee/MJRefresh


text:
"Block user" feature is never used as intended and is not well designed

So, if I've learnt my CW history lessons properly, the current block user feature was added because of #623 and #787.
Currently these things happen if a user (A) has blocked another user (B):

A cannot see B's comment, they're masked and will say: This comment can not be viewed.
B cannot see A's profile
B cannot leave comments on A's profile (at least on the front-end)
B cannot edit A's kata
...

The problem: it was added due to one user causing one flame war in the past, and this has never happened again in the future. At least for the whole year I'm on CW, I've never seen any actual occurrences of any flame war happening, so it's solving a "problem" that doesn't exist in the first place.
(Note that even things like #1198 and #1210 had happened just once before, and it was resolved by admin action, not block user.)
However, what I have seen multiple times is newbies blocking users telling they're wrong, and kata authors blocking users to stop these users posting issues on their katas (I'm looking at you, @SteffenVogel79). The latter is not normal usage of this feature. It's an abuse.
Also, block users feature should not hinder normal site usage. CW does not belong to any user, so there's no reasons being blocked by a user makes me unable to perform certain site-related actions. This is not Twitter or Facebook, we don't have user-specific timelines, just public katas that everyone can see and comment on.

Proposal:

Either remove all restrictions on those B cannot do this to A and just leave the first one apart...
Or just remove this feature, it doesn't solve anything practically and track record proves that it's causing hindrances instead. It wasn't even added with much thought in the first place. And in fact, most actually abusive things, like spams, are resolved by admin action anyway.

Voile, you are creating issues only because you think a kata have to be in your way of thinking.
Your postings are annoying and I don't like your revenge bad votings.
That is the reason, I blocked you! I do not want to discuss or read from you! So, the blocking feature is the best and most worthy feature on codewars.
Have a nice time on codewars, but please without disturbing and annoying me.

Though he is right about one thing: shit posting authors that can block power users so that they cannot post issues on their wrongly done katas IS a REAL PROBLEM.

@SteffenVogel79 What you're saying is completely wrong and off the basis of facts.
For the record, you blocked me when I posted issues at your "Construct a Car" katas:
https://www.codewars.com/kata/constructing-a-car-number-2-driving
https://www.codewars.com/kata/constructing-a-car-number-3-on-board-computer
The thing is, just like most of the OO katas on CW, these katas have serious lack of specs:

2: See the comments: did you see that at least 3 people are asking about what some of the tests are about? I was posting an issue about 2 of the things that I encountered as I'm attempting the kata, and I haven't even gone through the whole thing by that point. There are even more hidden mines.
3: It's basically 2 but lots, lots more of these mines. The consumption by distance metric are the worst: only in actual tests, zero feedback, zero information as to how the tests are set up, and in fact even the calculation of it is vague. Basically the tests are shit.
Also, lots, lots, lots of tests are in the actual tests only and they test behaviours which is not stated anywhere. If we have to comtemplate

I mean, seriously, both you and @g964 needs to get your heads straight and admit the fact that your kata can be unclear/have issues and you have to work with the users to resolve them, not just f**king block/shoot down the reporters and pretend they don't exist. Has anyone felt good about how g964 handled the inquiries in his kata comments? Pretty much none. In fact it's so annoying it's been vented out on various occasions; we just don't speak out in the kata comments.
And I have to say, you're even worse than him. Shooting down issues by abusing a site feature? This is bad and you should feel bad. You're not even trying to be cooperative to your kata users (there were lots of questions in your katas about the specs and you answered none).
(Shots fired because, seriously, lots of people have been thinking along the same line. I think someone has to speak out, and it's gonna be me today.)

:)

Bumping the issue. This "feature" is abused more than used for valid reasons. Considering the fact, that CW is "calm" and more-or-less friendly in the whole, there's virtually no reason why users would need to block other users. On the other hand, oversensitive kata-creators (let's be fair, they are the only ones doing this) like to block users whose views (especially on kata issues) they do not share. And this is a far more serious problem than a possibility that once in a few years some troll will start spamming messages and targetting users (this also doesn't help with the targetted downvoting bullshit).

Is this going to be fixed? Because apparently SteffenVogel is just blocking everyone who raises a issue on his katas. This is literally the worst abuse of this "feature" (if it's even a "feature" in the first place).

Another problem is that it may fix the issue if user A is exclussively targetting user B, but it changes nothing if troll is spamming everywhere. Obviously, all of the active users won't just go and block him, and even if they did, the endless flow of "this message is not shown to you"'s would still appear on the dashboard.

I've been avoiding this issue because I don't really know how to "fix" and I didn't know what to say. I've already spent more time than I wanted to so here's my initial thoughts.

@Voileexperiments

At least for the whole year I'm on CW, I've never seen any actual occurrences of any flame war happening, so it's solving a "problem" that doesn't exist in the first place.

I see you arguing with other users (mostly new users) about best practices very often. I understand the frustration, but I'd appreciate if you toned down. They're usually just lacking knowledge and/or experience and simply need more time to gain that. Words from some random person won't be enough anyways.
Also, sometimes you sound too harsh. Again, I understand the frustration of seeing similar issues happening over and over, but usually those are different users.
I personally don't mind the directness since I believe you have good intentions, but many will misunderstand you. They will react defensively and the communication will be highly inefficient. So I'd appreciate if you can pause and think about how others will feel before posting your comments.

@SteffenVogel79
Can you help me understand the problem from your point of view? You seem to have blocked many users. Can you elaborate on how they annoyed you?
I know @Voileexperiments sometimes sounds too harsh, but issues opened for the kata mentioned above seems fine. If there was other issues that triggered blocking him, please let me know so I have a better understanding.

Constructing a car #2 - Driving: 2279 code submissions and completed 49 times.
Constructing a car #3 - On-Board Computer: 471 submissions and completed 8 times.

Doesn't this show many are struggling to understand the requirements? Or they had to submit in order to find the hidden requirements? Do you think descriptions can be improved?
It's your kata, but it's for the Codewars community to solve and to learn from. So I'd like you to at least consider whenever someone opens issues rather than forcing them to stop by blocking. They're usually trying to help improving it or having problems understanding it.
If you disagree with them, explaining the reasons behind your decision will be much more constructive. This can also prevent someone else from raising the same issue again.
Like I wrote above, I only looked at the mentioned kata. So let me know if I've misunderstood the problem.

So, the blocking feature is the best and most worthy feature on codewars.

This is very depressing :(

I have never blocked anyone but I think this should be kept if used wisely. "Respect and courtesy" must be CW's motto.

I have never blocked anyone but I think this should be kept if used wisely. "Respect and courtesy" must be CW's motto.

@kazk I do not consider my tone "too harsh" for the situation in which I choose my tone; I choose my tone that I feel reflects what the other side deserves, which includes the tone of the original message and the other side's reputation. Being respected is a privilege that is earned by being, well, respectable; it is never an universal right in the first place. Yes, I do admit sometimes I get salty like everyone does, but I do adjust afterwards.
What is not mentioned here is that most of the times I'm very strongly worded because the other side starts the discussion with a condescending tone, especially prevalent with "I can't pass the test" inquiries-as-issues and UUN (Unreadable, Unmaintainable, Not for production) arguments: what do you expect to do then? Newbies buy into these arguments; and sometimes the entire discussion thread is wrong. If you don't debunk them, you lose by forfeiting the argument. If you're not strongly worded enough, you lose because you look like a wimp. I know people don't like to listen to strong worded sentences because it hurts their (sometimes blistering) ego, but I choose to do it anyways because while every choice lead to losing, it is at least the best for my mental health. I hope you can understand my situation.
(Also, humbleness goes to both sides too: if one is inexperience, they should've been sure to be extra humble and not make very strong claims because they're more likely to be incorrect. This is like, I dunno, human interaction 101? If someone's bold enough to make outrageous claims about wrong stuff despite the lack of abilities and doesn't back up at all, I feel I have all the rights to retaliate.)

I am very strongly worded about this issue because it is, to be honest, very appalling. It takes effort and time to actually pinpoint and write the issues; after all I can just solve the kata in the quickest way, do nothing about the obvious problems and let everyone after me suffer from the same thing. But then all the beta katas will be approved with tons of issues, and in the end kata quality becomes abyssmal, CW quality is dragged down as a result and everybody loses.
I know nobody wants to have issues in their katas, especially the bogus ones. I understand that. But blocking users to prevent them from posting issues because the author believes that their issues are "not a issue" is not just ridiculous, but completely disrespectful of any author-user interactions. The author might as well live in an ivory tower where they believe that their works are "perfect", and anyone who dares to point out otherwise would be banished. Now that's the real WTF right there.
(In addition, for almost all the katas with issues I can just edit them and change everything to make them make sense again, which would've saved all the troubles and avoided any needs to deal with potentially hostile kata authors. I choose not to because I still respect the will of the kata author. It's their katas, and they get to decide what the requirement is. By committing the act to outright blocking users who post issues, the kata author is basically saying they do not want to be respected. So why should I?)
Oh, by the way, yes, those two katas still have issues with completely unspecified requirements and wrong requirements.

Also, let's point out more problems with how the current "block" function is implemented:

As mentioned above, it is supposed to be a restriction on user interaction but it's interfering with site functions. Site function related restrictions should've been handled by admins (like a certain no one that has manipulated the beta system by somewhat). If I can censor people I don't like by using the block function like this, it's abuse.
It is not just visible, it's wide in the open: I can easily see a kata author has blocked me from the comment section of their katas. In fact it's even worse: #1357 is not patched so anyone can instantly see all users that have blocked them.

I recommend reading this as to how to design these user interaction related features that prevents abuse.

@Voileexperiments
You're assuming that they can recognize their lack of ability.
They think they know what they're talking about because that's all they know. If they only know one way of doing something, they won't be able to think about trade-offs.
UNN comments are often reactions to seeing something different from what they value and not being able to accept it. They're in denial. They have the right to express that and they should be able to have civil discussions. It's part of a learning process and there's no need to put them down.
"I can't pass the test" is someone being desperate and not knowing what to do. We should tell them to label their comment as questions instead and help them.

Newbies buy into these arguments; and sometimes the entire discussion thread is wrong. If you don't debunk them, you lose by forfeiting the argument. If you're not strongly worded enough, you lose because you look like a wimp.

I honestly don't understand this.
Do you argue with little kids and yell at them for not knowing better?
I mean, they might be wrong, but that's not really their fault. They just need to learn.

It takes effort and time to actually pinpoint and write the issues; after all I can just solve the kata in the quickest way, do nothing about the obvious problems and let everyone after me suffer from the same thing.
I choose not to because I still respect the will of the kata author. It's their katas, and they get to decide what the requirement is.

I know you have good intentions.
You clearly care about Codewars and have done a lot for the community.
Unfortunately, many users don't think so because they've misunderstood you and they're intimidated by you. A new user might see your comment on the dashboard and assume you're abusive user putting others down.
You might not care what others think of you, but I think that's sad and that's why I mentioned it in the first comment.

I agree blocking shouldn't be used this way, but I also understand some authors want to do it their way.
For the next version of Codewars, I was thinking of having a few separate pool of kata:

Official Kata Listing

Require certain quality to be listed here
Authors agree to adhere to Codewars standards and are not allowed to personalize the content

Personal Kata Listing

Authors are free to do whatever they like and it'll be under their namespace

Beginners Kata Listing

Kata for really basic stuff to learn languages

Also, let's point out more problems with how the current "block" function is implemented:

I agree it's not implemented well. Thanks for the link, it was a great read.

@SteffenVogel79 probably muted this issue.
I just checked if any other author does this and he is the only one that blocked multiple active power users. Maybe we can keep it as is for now.

PSA: I've just been blocked by JohanWiltink too. He's probably fed up with my issues on his kata.
Relying on users to use the block user feature responsibly when we all know it can slience users you don't like on your katas is just not gonna work. Are we still gonna repeat the same history again?

Strange. I did not block Johan, and he did not block me.
Bot we blocked YOU both! Maybe the problem is you!

What do you mean? Why don't you list out the 1000 users you've blocked? ;-)
You're the biggest prick on CW living on the highest ivory tower, and every power user knows it. I'm surprised you have the audacity to still comment on this issue.

It must be so hard for you, that there are users, who don't want to read your stupid comments... And they can block you... sorry, it must be very hard.
There are many power users, with whom I have discussed hard and we are still ok with each other.
But freaks like you.... no thanks.
Bye, voile. The blocking-feature ist the best feature here ever!

What? Nobody is trying to win him over.
I think you're getting the point wrong: he has been doing this for years and has basically refused any kind of communication (just look at this issue). If anything most PUs do not want to deal with him at all.
This issue is opened to advocate kazk to remove most of the (unnecessary and poorly designed) power associated with block feature to dethrone him from the ivory tower he's on right now.

Well then don't deal with him... ignoring each other seems to be the simpler way here, it doesn't look like there is any chance of reconciliation, so maybe mutually ignoring each other works better rather than try to change the whole website because of one single particular dispute between two users. But that's just my $0.02.

Yes, I have read through the issues, although I am not such an active or great user, and I'm nowhere near as experienced with coding as you, I do find the progression of this website interesting. I do not mean/did not mean to attack you personally or something, but I just think that this issue is completely pointless and just wanted to voice my opinion about that. I hope that's fine with you.
If someone blocks too many people needlessly, it will become their own problem too, you know, one day they will have nobody to interact with. Also, I don't think that calling people vulgarities will help your cause nonetheless, it's kind of hard to take it seriously at that point.
I don't think that a community site with no block feature will work, sometimes people just don't get on, and there needs to be a way for such people to stop the other one from interacting with them.

The thing is that when a user blocks everyone, there's no one left to raise issues on their katas, so there're lots of permanently unfixable katas around.

The thing is that when a user blocks everyone, there's no one left to raise issues on their katas, so there're lots of permanently unfixable katas around.

Maybe a (reasonable) limit on the number of users that you can block would help. But not removing the feature altogether...

Neithor Johan nor me blocks everyone! Only freaks like Voile are blocked!
The number of users blocked by me is not so high as Voile said.
He is really my important blocking!

Maybe a (reasonable) limit on the number of users that you can block would help. But not removing the feature altogether...

Why? Katas do not belong to authors. They belong to the site. By submitting your kata to CW you already forfeit your right to the original content you've written: they become CW material. This is how every site featuring user-created content works.
So no, blocking users causing a disruption in site function does not make sense, because that would imply the kata author is "special", in which they are not. Kata author do not, and should not have the privilege to block users to access to a kata's specific features.
Also, there is still the issue that block user feature is prone to abuse, and has been abused (by multiple users even). Are you going to address it? If not then this issue is not for you.

Maybe a (reasonable) limit on the number of users that you can block would help. But not removing the feature altogether...

Why? Katas do not belong to authors. They belong to the site. By submitting your kata to CW you already forfeit your right to the original content you've written: they become CW material. This is how every site featuring user-created content works.
So no, blocking users causing a disruption in site function does not make sense, because that would imply the kata author is "special", in which they are not. Kata author do not, and should not have the privilege to block users to access to a kata's specific features.
Also, there is still the issue that block user feature is prone to abuse, and has been abused (by multiple users even). Are you going to address it? If not then this issue is not for you.

If not then this issue is not for you.

Thankfully it is not up to you to decide what is for who :)
I see you are often berating other users (sometimes with vulgarities). If we go by standards of how other sites work, you'd be long excluded by now.
If you have not considered the fact that people do not want to be berated by others, then you probably should. It's the main issue that you are having (and causing to yourself).

In any case, are you contributing to the discussion? Or are you just trying to invalidate my personality?
Looks like both you and SteffenVogel is doing the latter. I thought you would be better than this ;-)

Yes, I am, I'm giving you a neutral point of view. It's not about invalidating your personality, it's about the fact that you are berating other users and then posting (pointless) issues that they are blocking you as a response.

Your "neutral" point of view is funny, because in a neutral point of view I do not enter the equation, nor SteffenVogel.
A neutral point of view is this:

Blocking users currently disrupts normal site functions
Kata do not belong to kata authors, so kata author should not be able to rig their katas in whatever means

Hence I already mentioned my suggested course of action above:

Block user do not need to be removed, but it should be revised
It should definitely not block users from interacting with katas, because katas do not belong to kata authors. If there are abuse (which there isn't btw), they should be resolved by admins, not some dumb block functions
However blocking users should hide their comments. That's why blocking are supposed to be in the first place

And when will you learn to not talk about individual users? You're really "neutral" there, you know ;-) Maybe you should take your effort to post on #1646 instead.

And when will you learn to not talk about individual users?
(I'm looking at you, @SteffenVogel79)

Your opening comment is literally about picking out an individual user :)

Block user do not need to be removed, but it should be revised

Agreed, the site does not seem to have big issues in general, perhaps a limit to how many users can be permanently blocked could work, and perhaps there could also be a feature to block someone temporarily.

It should definitely not block users from interacting with katas, because katas do not belong to kata authors

Do not agree, people should be able to have complete peace of mind from abusive users.

And when will you learn to not talk about individual users?
(I'm looking at you, @SteffenVogel79)

Your opening comment is literally about picking out an individual user :)

Block user do not need to be removed, but it should be revised

Agreed, the site does not seem to have big issues in general, perhaps a limit to how many users can be permanently blocked could work, and perhaps there could also be a feature to block someone temporarily.

It should definitely not block users from interacting with katas, because katas do not belong to kata authors

Do not agree, people should be able to have complete peace of mind from abusive users.

@SteffenVogel79 did you read my comment? Can you reply to that instead of calling names?

I agree it needs improvement, but this is low priority because I already have too many problems to fix and this doesn't seem too bad:

Number of kata authors that blocked at least one active power user: 15

14 of them blocked one or two

12 of them blocked one
2 of them blocked two

8 of them authored 3 or less kata

Number of kata authors that blocked at least one active user: 18

17 of them blocked one or two

14 of them blocked one
3 of them blocked two

9 of them authored 3 or less kata

As far as I can tell, @Voileexperiments (blocked by many) and @SteffenVogel79 (blocked many) are outliers.
I can't look up those blocks temporarily so I don't know about that.

The main issue is that there isn't a separation between

general feedback, commentary
raising issues

It is reasonable for a user to be able to prevent the first, completely unreasonable for the second.
If they are not uncoupled then a solution for users who do the second would be they lose the right to do the first. However what is happening in some cases is that one user feels another one is raising issues which are not actually issues and they are blocking them to prevent that. That is a more complicated issue because someone has to judge if the issues are valid to settle the conflict.

@kazk Well, #1357 is not fixed yet, so...
I'm not sure if even my case is "too many" compared to what SteffenVogel is doing. There are users with 2 honor, there are many inactive users that haven't even posted comments, and after all there are just... 3 active users? At least compare that to what PUs have been mentioning the in gitter chat over the year about being blocked by him, that's certainly much lower in numbers.
Also, I should point out that @plasticbottle have also blocked me. I think I understand now why he insists on talking about me instead of the issue.  (It's also why disclosure of interest is a good thing!) For some reasons the blockers have been acting are low-quality trolls in this issue instead of, say, contributing to the issue.

I do agree about

If they are not uncoupled then a solution for users who do the second would be they lose the right to do the first.

though. But then this is again material for #1646, and I think we need more of kazk's feedback.

Also, I should point out that @plasticbottle have also blocked me. I think I understand now why he insists on talking about me instead of the issue

I did that as a preventative measure, since I do not want to spend much time arguing with users that like to do that all the time. All I can say is reiterate what has already been said in #805:

If a blocked user feels like they can't express themselves because they were blocked - maybe they should reconsider their actions that got them blocked in the first place.

I think they'd expect that the blocked user can't contact them anymore anyhow.

CW is not Facebook, and the discourse is not owned by anyone ;-) I don't care if the block function make you unable to see my comments (after all, everyone is free to ignore other's comments), but if I cannot comment on some of the entire discourse because I was blocked by an user, then I consider it a breach of my rights as I have the right to comment on every discourse, unless I had done something that forbids me to comment on the entire site. This has happened before, in fact twice (#1198, #1210) ;-)
The same goes to katas. Kata does not belong to kata author, so they do not have the right to arbitrarily deny an user's functionality on their katas. By tomorrow you might as well claim that by blocking me I'm not able to solve any of your katas.
In fact I think only two person here would think so ;-)

All I can say is reiterate what has already been said in #805

And in the same thread jhoffner also said "I was reluctant to add it in the first place". When you quote someone, please quote it in full and not just cherry-pick the part that flavours you ;-)
Everyone knows that why and how the block feature was implemented (see this issue's OP), and how much of a rush it was. Blocking users also blocks the entire discourse is not part of #623, and 2 of the 3 proponents there have blocked me anyway (yes, I figured out dinglemouse blocked me recently too. JohanWiltink has lifted the block though).
So what I'm saying here is: essentially jhoffner just listened to 3 particular outlier users and hastily (in 2 days) implemented a feature due to a conflict between one of them and another user; in which this feature is being abused by also the same outlier users. There were no feedback asked from any other users. In this ground I cannot claim at all that this function is well-designed at all, or is implemented in the benefit of most CW users. No, not at all.
(Also it's good to know that SteffenVogel has already behaved like that back in #623 was made. Really eye-opening!)

Also, let's get this straight: I perfectly know you don't like how I talk. But I don't care :trollface: Keep telling me this is not doing anything, so you might as well do other things instead.

Hence the title of this issue, and my strong request that it should be removed before it is certain that most users actually want this function.

Good. I respect your opinion and your view. I am here to say the opposite however. People should be able to have complete peace of mind from users that they find abusive/obnoxious. As much as you have a right to express your opinions, everyone has the right to feel comfortable on the website too.
So what do you really want to achieve? Troll everyone on this website until everyone else but you gets frustrated and leaves? :)

(see this issue's OP)

There you pretty much picked out a user and made a salty thread that you can't harrass him anymore. Why don't you try instead, to find out why he blocked you, and try to say sorry/apologize and reconcile, instead of calling him out publicly on a forum, and trying to force the site admins to lift the block?

I perfectly know you don't like how I talk.

If you are such a leading figure in being blocked, then apparently I'm not alone. Perhaps community advices shouldn't be taken from you...

But I don't care :trollface:

This response entirely reflects your overall attitude.

The fact, that Voile called me a prick is the best sign, that it is the best decision to block him!

I am here to say the opposite however. People should be able to have complete peace of mind from users that they find abusive/obnoxious.

And CW should be ensuring that kata authors are fulfilling their responsibility and doing their jobs properly, which SteffenVogel has done none of them. He's just abusing this feature so he can continue not fulfilling any responsibilities as a kata author and shoot down every single issue in his kata.
If it is just used to slience particular user, I don't mind (like I don't complain about how KenKamau blocks people temporarily). But if it is used to circumvent the kata process, this is an abuse.
And CW > people, so your opinion is invalid.
If you want to argue, don't argue about me. You're still spending an entire thread commenting about me. I thought you should've learnt that already ;-)

And CW > people, so your opinion is invalid.

Umm... what? There is no CW without a userbase. If it becomes possible to keep trolling a person and the person has zero tools to stop that as per your suggestion, it means the only thing a user can do is basically delete his account and leave the website and thereby letting the troll win. And that is not cool :(
The current system seems reasonable. People can block each other, instead of going down on big flame-wars. Additionally, the current system forces people to act respectfully to each other, since there is now a real deterrent from trolling authors.

If you want to argue, don't argue about me.

I do not really care about you, but I did not like how a user in OP and ever since OP has been getting picked on. And the abusive language got me to put my $0.02 into this thread.

And CW should be ensuring that kata authors are fulfilling their responsibility

I saw a pretty good idea from the site admin in another thread for the future, I'll link it for you:
https://github.com/Codewars/codewars.com/issues/1626#issuecomment-438400435
Perhaps we simply need to be patient ;)

Last week I solved an issue, that was correct.
But I close issues like "Your description is not in the way I like" or "My code does not work. Your tests must be wrong!"
And I blocked Blind4Basic. This was really a fault and I unblocked him. Sorry, Blind4Basic, if you read this.
But again and again, it shows, that it is the best feature to block freaks like Voile! Really!

I kinda agree with @SteffenVogel79. Sometimes there are users that need to be blocked, I for one have not blocked anyone since I failed to see anything wrong with anyone (highest in my list is @FArekkusu and I don't hate him enough to bother blocking). But if some users want some peace of mind, they should be allowed to block a user. @Voileexperiments on pointing out issues : just give it a down-vote and rank it, and post in gitter channel that there is an issue on this Kata and let someone else post it (neither of them have blocked Blind4Basics, ZED and a ton of others).

So after one particular user threw a fit on a hastily authored "Kata" and this repo, he proceeded to block me on Codewars solely based on a (perhaps out-of-place, I'll have to admit) comment I left on the Codewars Gitter channel on his last reply to #1866 . As this particular case once again demonstrates, the block feature is commonly abused by irresponsible Kata authors who don't give a s*** about the Codewars community in order to push their s***ty Kata out of Beta.
@kazk @jhoffner Can we just agree to remove this "block" function once and for all? As @Voileexperiments stressed multiple times before:

It was hastily added to Codewars based on just one particular incident of some egotistic maniac (who I won't name here to protect his identity from those who do not already know him) causing shenanigans in the Discourse section of multiple CW Kata who requested this feature himself to prevent others from refuting his absurd actions
It has brought nothing but harm to the site. If a particular Codewarrior is found to exhibit disruptive behavior on Codewars by leaving inappropriate comments or otherwise then an admin can always step in and ban the user from continued engagement of Codewars' services. Instead, Codewars has opted to provide a "Block" button which gives the perfect excuse for snowflakes unable to handle comments from respected Codewarriors pointing out actual issues on their Kata to "ignore the elephant in the room", so to speak, by blocking them and continue on with their destructive actions
It doesn't actually work! As #1840 has demonstrated, experienced Codewarriors can easily work around the "block" by fiddling with various endpoints creating issues that the Kata author can neither view nor resolve

I'm going to have to pipe in and comment that the biggest issue with the "Block" feature is it does not understand the problem that it is trying to solve... and in the history of the Internet has never done anything but escalate the scenario.
I've gotten into a few heated interactions with people back when I was still checking stuff out on Codewars (I've since then decided to take a break for a bit, to see if that has me more level headed when I return)... but even when talking about how the to solve me getting into these interactions, I'd have not suggested this.
Essentially, there are a number of issues from Dunning-Kruger Effect, Tribalism, Confirmation Bias and a result in blocking just making stuff worse.
IIRC, I mentioned that such a feature would only make matters worse prior to me taking a little self-imposed vacation last year.
That being said, the closest thing I can give to a solution is "have moderators/staff be trained in psychology sufficiently"--which is a fucking shitty solution that is just awful.

Since then there are apparently at least several cases where new users, after publishing the first beta kata and being pointed out their beta kata do not constitute acceptable quality, begin blocking power users that are pointing the above out:
https://www.codewars.com/kata/student-grades-what-grade-did-the-student-achieve
https://www.codewars.com/kata/is-fred-a-good-golfer-or-not
...how are the new users knowing this feature? Is there are group of people in behind who are actively trying to sabotage the beta process and undermine the power users or something? Because otherwise it's difficult to explain how new users magically know this feature undocumented on anywhere else besides here. This is honestly ridiculous and we're now resorting to dirty tactics, apparently?


text:
Feature Request: Simple list, single choice list, multi choice list support

@shardul89
The android counter part has the above features.
Any plans on adding it to iOS?

@shiv19 Its good that you took time and analyzed the difference between iOS and Android version of this library.
The thing is in native Android alert dialog simple list, single choice list and multi-choice list support is already there. So to make a transition easier for the developers who are using native alert dialog and wanted to move to CFAlertDialog, we have added this feature only into the android library. They will get all the native features + additional new features which our library provides when they transition.
Currently, we don't have any plan to port that feature into iOS library. But in upcoming months we have some plans which will solve this problem on the scale. For now, the user can make their own custom view and attach it to header or footer view to get this feature working.

@shardul89 thank for clearing that up for me. :smile:
I'm writing a nativescript plugin which wraps CFAlertDialog,
I have finished making Android part, next up I'll be making iOS part. ( https://github.com/shiv19/nativescript-cfalert-dialog )
In nativescript we generally try to do our best to provide same feature on both platforms, which is why this was my concern.

repo: Codigami/CFAlertViewController


text:
ubuntu server 16.04 x86_64 build失败,该如何解决?

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14
building frontend...

coding-web-ide@1.0.0 build /home/hook/WebIDE/frontend
cross-env NODE_ENV=production ./node_modules/webpack/bin/webpack.js --progress --colors

/usr/bin/env: "node": 没有那个文件或目录
npm ERR! Linux 4.4.0-31-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "build"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! coding-web-ide@1.0.0 build: cross-env NODE_ENV=production ./node_modules/webpack/bin/webpack.js --progress --colors
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the coding-web-ide@1.0.0 build script 'cross-env NODE_ENV=production ./node_modules/webpack/bin/webpack.js --progress --colors'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the coding-web-ide package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cross-env NODE_ENV=production ./node_modules/webpack/bin/webpack.js --progress --colors
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs coding-web-ide
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls coding-web-ide
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/hook/WebIDE/frontend/npm-debug.log

root@ubuntu:/home/hook/WebIDE# cat /home/hook/WebIDE/npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'bugs', 'coding-web-ide' ]
2 info using npm@3.5.2
3 info using node@v4.2.6
4 silly fetchPackageMetaData coding-web-ide
5 silly fetchNamedPackageData coding-web-ide
6 silly mapToRegistry name coding-web-ide
7 silly mapToRegistry using default registry
8 silly mapToRegistry registry https://registry.npmjs.org/
9 silly mapToRegistry uri https://registry.npmjs.org/coding-web-ide
10 verbose request uri https://registry.npmjs.org/coding-web-ide
11 verbose request no auth needed
12 info attempt registry request try #1 at 上午11:44:48
13 verbose request id 27b6fda3a5fbaae7
14 http request GET https://registry.npmjs.org/coding-web-ide
15 http 404 https://registry.npmjs.org/coding-web-ide
16 verbose headers { 'content-type': 'application/json',
16 verbose headers   'cache-control': 'max-age=0',
16 verbose headers   'content-length': '2',
16 verbose headers   'accept-ranges': 'bytes',
16 verbose headers   date: 'Wed, 21 Sep 2016 03:47:17 GMT',
16 verbose headers   via: '1.1 varnish',
16 verbose headers   age: '0',
16 verbose headers   connection: 'keep-alive',
16 verbose headers   'x-served-by': 'cache-sin6922-SIN',
16 verbose headers   'x-cache': 'MISS',
16 verbose headers   'x-cache-hits': '0',
16 verbose headers   'x-timer': 'S1474429637.177396,VS0,VE269',
16 verbose headers   vary: 'Accept-Encoding' }
17 silly get cb [ 404,
17 silly get   { 'content-type': 'application/json',
17 silly get     'cache-control': 'max-age=0',
17 silly get     'content-length': '2',
17 silly get     'accept-ranges': 'bytes',
17 silly get     date: 'Wed, 21 Sep 2016 03:47:17 GMT',
17 silly get     via: '1.1 varnish',
17 silly get     age: '0',
17 silly get     connection: 'keep-alive',
17 silly get     'x-served-by': 'cache-sin6922-SIN',
17 silly get     'x-cache': 'MISS',
17 silly get     'x-cache-hits': '0',
17 silly get     'x-timer': 'S1474429637.177396,VS0,VE269',
17 silly get     vary: 'Accept-Encoding' } ]
18 silly fetchPackageMetaData Error: Registry returned 404 for GET on https://registry.npmjs.org/coding-web-ide
18 silly fetchPackageMetaData     at makeError (/usr/share/npm/node_modules/npm-registry-client/lib/request.js:264:12)
18 silly fetchPackageMetaData     at CachingRegistryClient. (/usr/share/npm/node_modules/npm-registry-client/lib/request.js:242:14)
18 silly fetchPackageMetaData     at Request._callback (/usr/share/npm/node_modules/npm-registry-client/lib/request.js:172:14)
18 silly fetchPackageMetaData     at Request.self.callback (/usr/share/npm/node_modules/request/request.js:198:22)
18 silly fetchPackageMetaData     at emitTwo (events.js:87:13)
18 silly fetchPackageMetaData     at Request.emit (events.js:172:7)
18 silly fetchPackageMetaData     at Request. (/usr/share/npm/node_modules/request/request.js:1082:10)
18 silly fetchPackageMetaData     at emitOne (events.js:82:20)
18 silly fetchPackageMetaData     at Request.emit (events.js:169:7)
18 silly fetchPackageMetaData     at IncomingMessage. (/usr/share/npm/node_modules/request/request.js:1009:12)
18 silly fetchPackageMetaData  error for coding-web-ide { [Error: Registry returned 404 for GET on https://registry.npmjs.org/coding-web-ide] pkgid: 'coding-web-ide', statusCode: 404, code: 'E404' }
19 verbose stack Error: Registry returned 404 for GET on https://registry.npmjs.org/coding-web-ide
19 verbose stack     at makeError (/usr/share/npm/node_modules/npm-registry-client/lib/request.js:264:12)
19 verbose stack     at CachingRegistryClient. (/usr/share/npm/node_modules/npm-registry-client/lib/request.js:242:14)
19 verbose stack     at Request._callback (/usr/share/npm/node_modules/npm-registry-client/lib/request.js:172:14)
19 verbose stack     at Request.self.callback (/usr/share/npm/node_modules/request/request.js:198:22)
19 verbose stack     at emitTwo (events.js:87:13)
19 verbose stack     at Request.emit (events.js:172:7)
19 verbose stack     at Request. (/usr/share/npm/node_modules/request/request.js:1082:10)
19 verbose stack     at emitOne (events.js:82:20)
19 verbose stack     at Request.emit (events.js:169:7)
19 verbose stack     at IncomingMessage. (/usr/share/npm/node_modules/request/request.js:1009:12)
20 verbose statusCode 404
21 verbose pkgid coding-web-ide
22 verbose cwd /home/hook/WebIDE
23 error Linux 4.4.0-31-generic
24 error argv "/usr/bin/nodejs" "/usr/bin/npm" "bugs" "coding-web-ide"
25 error node v4.2.6
26 error npm  v3.5.2
27 error code E404
28 error 404 Registry returned 404 for GET on https://registry.npmjs.org/coding-web-ide
29 error 404
30 error 404 'coding-web-ide' is not in the npm registry.
31 error 404 You should bug the author to publish it (or use the name yourself!)
32 error 404 Note that you can also install from a
33 error 404 tarball, folder, http url, or git url.
34 verbose exit [ 1, true ]

确认两件事：

服务器上命令行运行 /usr/bin/env node 看看 node 是不是能开
到 frontend 的 package.json 把 "scripts.build" 字段改为：
NODE_ENV=production ./node_modules/webpack/bin/webpack.js --progress --colors

做完麻烦给我个反馈

node能开,pkgjson等会反馈

ok,成功运行,我去试试看docker能不能构建

啊咧..又出怪事了
2016-09-21 22:50:34.449  WARN 812 --- [ost-startStop-2] o.a.c.loader.WebappClassLoaderBase       : Failed to check for ThreadLocal references for web application [ROOT]
java.lang.UnsupportedOperationException: null
at com.zaxxer.hikari.util.FastList.iterator(FastList.java:209)
at org.apache.catalina.loader.WebappClassLoaderBase.loadedByThisOrChild(WebappClassLoaderBase.java:1986)
at org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks(WebappClassLoaderBase.java:1890)
at org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalsForLeaks(WebappClassLoaderBase.java:1844)
at org.apache.catalina.loader.WebappClassLoaderBase.clearReferences(WebappClassLoaderBase.java:1514)
at org.apache.catalina.loader.WebappClassLoaderBase.stop(WebappClassLoaderBase.java:1460)
at org.apache.catalina.loader.WebappLoader.stopInternal(WebappLoader.java:447)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:229)
at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5436)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:229)
at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1419)
at org.apache.catalina.core.ContainerBase$StopChild.call(ContainerBase.java:1408)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2016-09-21 22:50:34.467  WARN 812 --- [           main] o.s.boot.SpringApplication               : Error handling failed (Error creating bean with name 'eventExchange' defined in file [/root/WebIDE/backend/target/classes/net/coding/ide/web/message/EventExchange.class]: BeanPostProcessor before instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration': Initialization of bean failed; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'org.springframework.context.annotation.ConfigurationClassPostProcessor.importRegistry' is defined)
2016-09-21 22:50:34.525 ERROR 812 --- [           main] o.s.boot.SpringApplication               : Application startup failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaAutoConfiguration.class]: Invocation of init method failed; nested exception is com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Exception during pool initialization: HikariPool-0 - Connection is not available, request timed out after 30007ms.
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1578)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1076)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:851)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:541)
at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:759)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:369)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:313)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1185)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1174)
at net.coding.ide.Application.main(Application.java:31)
Caused by: com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Exception during pool initialization: HikariPool-0 - Connection is not available, request timed out after 30007ms.
at com.zaxxer.hikari.pool.HikariPool.initializeConnections(HikariPool.java:526)
at com.zaxxer.hikari.pool.HikariPool.(HikariPool.java:136)
at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:94)
at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:139)
at org.hibernate.engine.jdbc.internal.JdbcServicesImpl$ConnectionProviderJdbcConnectionAccess.obtainConnection(JdbcServicesImpl.java:279)
at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:124)
at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234)
at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206)
at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1887)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1845)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:857)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850)
at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:425)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:849)
at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider.createContainerEntityManagerFactory(SpringHibernateJpaPersistenceProvider.java:60)
at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:338)
at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory(AbstractEntityManagerFactoryBean.java:373)
at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:362)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1637)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
... 16 common frames omitted
Caused by: java.sql.SQLTransientConnectionException: HikariPool-0 - Connection is not available, request timed out after 30007ms.
at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:195)
at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:147)
at com.zaxxer.hikari.pool.HikariPool.initializeConnections(HikariPool.java:510)
... 36 common frames omitted
Caused by: java.sql.SQLException: path to '/root/.coding-ide-home/ide.db': '/root/.coding-ide-home' does not exist
at org.sqlite.core.CoreConnection.open(CoreConnection.java:192)
at org.sqlite.core.CoreConnection.(CoreConnection.java:76)
at org.sqlite.jdbc3.JDBC3Connection.(JDBC3Connection.java:24)
at org.sqlite.jdbc4.JDBC4Connection.(JDBC4Connection.java:23)
at org.sqlite.SQLiteConnection.(SQLiteConnection.java:45)
at org.sqlite.JDBC.createConnection(JDBC.java:114)
at org.sqlite.JDBC.connect(JDBC.java:88)
at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:95)
at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:314)
at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:171)
at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:436)
at com.zaxxer.hikari.pool.HikariPool.access$500(HikariPool.java:65)
at com.zaxxer.hikari.pool.HikariPool$PoolEntryCreator.call(HikariPool.java:567)
at com.zaxxer.hikari.pool.HikariPool$PoolEntryCreator.call(HikariPool.java:560)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:18 min
[INFO] Finished at: 2016-09-21T22:50:34+00:00
[INFO] Final Memory: 47M/247M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:1.4.0.RELEASE:run (default-cli) on project backend: Could not exec java: Application finished with non-zero exit code: 1 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

还是不行,最后的日志:

coding-web-ide@1.0.0 build /opt/coding/WebIDE/frontend
cross-env NODE_ENV=production ./node_modules/webpack/bin/webpack.js --progress --colors

Hash: 544aceb991a45c89d681
Version: webpack 1.13.2
Time: 23916ms
Asset       Size  Chunks             Chunk Names
main.js    3.34 MB       0  [emitted]  main
1.1.js     6.9 MB       1  [emitted]
index.html  753 bytes          [emitted]
favicon.ico    4.29 kB          [emitted]
[0] multi main 40 bytes {0} [built]
+ 906 hidden modules
Child html-webpack-plugin for "index.html":
+ 3 hidden modules
packing frontend....
[ERROR] Could not create local repository at /home/coding/.m2/repository -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/LocalRepositoryNotAccessibleException
npm install...
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14
building frontend...

coding-web-ide@1.0.0 build /opt/coding/WebIDE/frontend
cross-env NODE_ENV=production ./node_modules/webpack/bin/webpack.js --progress --colors

Hash: 544aceb991a45c89d681
Version: webpack 1.13.2
Time: 16169ms
Asset       Size  Chunks             Chunk Names
main.js    3.34 MB       0  [emitted]  main
1.1.js     6.9 MB       1  [emitted]
index.html  753 bytes          [emitted]
favicon.ico    4.29 kB          [emitted]
[0] multi main 40 bytes {0} [built]
+ 906 hidden modules
Child html-webpack-plugin for "index.html":
+ 3 hidden modules
packing frontend....
[root@localhost WebIDE]# ./ide.sh docker logs
CRITICAL - webide is not running.

希望尽早提供官方镜像, 唉...折腾三天了, 还是没见着

官方镜像已经上传到 docker hub，请参考 readme

repo: Coding/WebIDE


text:
Unpack filad

Unpack filad

Pubg mobile liite not unpack

Pubg mobile liite not unpack

Help

Please help

Please solve problems

Hello sir

Solov problem

repo: CodingGay/BlackDex


text:
محمد

محمد  هاك

محمد

فك التشفير

https://github.com/CodingGay/BlackDex/issues/128#issuecomment-2056948515


text:
Added Coding Challenge 76 10PRINT Processing #267

Made Processing version of 10PRINT.
it is taking 0.5 as probability , not 0.9  as stated in Pull request #320

Thanks for this! Did you mean to have the Lorenz attractor README In this pull request as well? Sorry to be slow about these.

Sorry ,finally I fixed a small problem in my Fork. Now putting pull request of  Coding Challenge 76 10PRINT Processing  and README of CC_12_LorenzAttractor.  Actually I am new on GIT-HUB . And thanks a lot
for your GITHUB for Poets Youtube Videos. It really helped me a lot , and made me to connected here.

Thank you!

Thanks for accepting....

authors: AryanGitHub shiffman

repo: CodingTrain/Rainbow-Code


text:
New images

Here are some new images.  I have added some color gradients to some of the ones that originally had black backgrounds to add a little bit of color, but keep original aesthetic.  Also  increased strokeWeight on some of them.

This is incredible!


text:
Added contribution

This is an object oriented implementation of fractal trees that creates random forests

Great idea and implementation ❤

repo: CodingTrain/website


text:
Update token_handler.py

Type
enhancement, bug_fix

Description

Added a try-except block in _get_system_user_tokens to handle potential exceptions by returning -1. This enhancement improves the robustness of the token handling mechanism by gracefully handling errors instead of raising exceptions to the caller.
Fixed the missing newline at the end of the file to adhere to Python file formatting standards.

Changes walkthrough
Relevant filesError handling

token_handler.pyEnhance Error Handling and Fix Newline in token_handler.py

pr_agent/algo/token_handler.py
Added error handling in _get_system_user_tokens method to return -1 on exception.  Ensured newline at the end of the file.

+10/-7

✨ PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

/describe

repo: Codium-ai/pr-agent


text:
Add Incremental Review /review -i

Use /review -i to review only new commits that hasn't been reviewed since the last pr-agent review, instead of full review to the entire PR (from the first commit).
How is works:
The pr-agent will search last review published by the PR-Agent and review all the subsequent commits that hasn't been reviewed yet ( * commits where commit_date > last_review_date)

@hussam789 /review -i

@hussam789 /review -i

Preparing review...

@hussam789 /review -i

Preparing review...

Incremental PR Review

⏮ Review for commits since previous PR-Agent review: Starting from commit https://api.github.com/repos/Codium-ai/pr-agent/pulls/94/commits/5f36f0d75332f7be956cb79fdf620a6f5dd1bf04

PR Analysis

🎯 Main theme: Adding incremental review functionality to the PR-Agent
📌 Type of PR: Enhancement
🧪 Relevant tests added: No
✨ Focused PR: Yes, the PR is focused as it introduces a new feature of incremental review. The title and description clearly explain the purpose of the PR and the changes in the code are aligned with this purpose.
🔒 Security concerns: No, the PR does not introduce any apparent security issues. The changes are primarily related to the logic of the PR review process and do not involve any sensitive data handling or operations that could be exploited for malicious purposes.

PR Feedback

💡 General PR suggestions: The PR is well-structured and the code changes are logically organized. However, it would be beneficial to include tests for the new functionality to ensure it works as expected and does not introduce regressions. Additionally, it would be helpful to update the documentation to explain how to use the new incremental review feature.

How to use

Tag me in a comment '@hussam789' and add one of the following commands:
/review - Request a review of the latest update to the PR.
/describe - Modify the PR title and description based on the contents of the PR.
/improve - Suggest improvements to the code in the PR. These will be provided as pull request comments, ready to commit.
/ask  - Pose a question about the PR.

@hussam789 /ask do I have enough documentation

@hussam789 /ask do i have enough documentation

@hussam789 /review

@hussam789 /review -i

Preparing review...

@CodiumAI-Agent /improve

Preparing review...


text:
Some strings cannot be translated

FilePrompt.java#L16, L34, L51 and L63

JarFileTree.java#L35, L58, L64 and L67

AccessPanel.java#L24-L27 and L45

DefinitionBox.java#L63 and L96

MemberTable.java#L29, VariableTable.java#L37 and ClassDisplayPanel.java#L224

Yeah, I've missed a few things here and there...

Last few commits have fixed all of these. I've attempted to use existing translations to fill in the new values. If I messed them up do correct me.

authors: Col-E andylizi

repo: Col-E/Recaf


text:
設置字體

您好。對您製作的主題很感興趣。感謝您的辛勤勞動。
在主題的設置中。字體似乎只有默認。雅黑等不多的選擇。麻煩問下有可能使用自己選擇的字體嗎。
非常感謝。
祝好。

关于定制的话，我是特别想满足任何一个人的。
如果有这类需求的话，我会尽量满足。

[ ] 在_config.yml配置字体

患病一周没有使用电脑，如对你带来不便，抱歉

我發完帖子後也生病了。剛剛康復。
目前在 _config.yml 中只能配置您給定的幾種字體吧。似乎暫時無法支持本地的 ttf otf 等字體文件。個人覺得似乎能分別設置一個 CJK 字體。一個西文字體和一個等寬字體。會是比較便捷的。否則如果能支持公認比較優秀的思源黑體。那麼在不同平臺上都會有比較理想的效果。
感謝您的回覆。我給一些人看了您製作的主題。設計方面收到的大多數是好評。不過功能方面似乎比起較爲流行的 NexT 還有一定差距。
最後。因爲我對前端和 UI 設計都是外行。所以有一個可能是亂說的看法。僅供參考。搜索功能的 alpha 值似乎可以調整一下。現在透明度有點太高。這樣搜索結果和背景有點重合在一起。就看不太清搜索結果了。效果如下。

谢谢
暂时就是想按照您说的，可以配置自定义字体名字达到效果。至于分别设置字体，这个我倒是要看看怎么做比较好。
至于跟NEXT比较，那就真的抬举我了，人家那个项目已经做成社区了（逃
好评倒是没有那么夸张，毕竟我们做着玩，然后有人“哇！喜欢！”。这个时候我才知道，我得为nlvi的粉丝负责了！
至于UI，我也没受过什么专业学习，是个建议都会接受。不过针对透明度，我倒是制作的时候来来回回对比了很多版，就目前的效果来说是比较漂亮的。如果还是有阅读问题的话，调整！

老哥，关于自定义字体的事，我找了一个比较不妥的方式。暂时先这样。以后想到好的方法我会告诉你的。
现在在主题的source中，style目录下，有一个_custom.styl，这个文件优先级算是比较高的，你可以把你喜欢的字体按西文到中文的顺序填到custom-fonts-style后，怎么填我已经在文件给了例子。
然后_config.yml还是设置字体那里，改成Custom即可
本地字体的话，你可以直接就在_custom.styl写你的配置，如果不清楚的话，具体我会更新wiki。
本来想在_config.yml一条龙解决，看来还是不行呢（笑

您好。感謝您的辛勤勞動。
您默認的樣例 ''_custom.styl'' 中包括了三個字體。第一個苹方。第二個是冬青黑。第三個是 Roboto。這三個字體分別對應了怎樣的設置呢。如果按照您這個文件這樣設置。最後的 CJK 字體到底是蘋方還是冬青黑呢。

$fonts-style = hexo-config("fonts-style")
$font-article-YaHei = 'Microsoft YaHei', "微软雅黑", sans-serif
$font-article-Hel = 'Helvetica', 'Hiragino Sans GB', 'Roboto', 'Noto SansCJK', 'Heiti TC', 'Heiti SC', sans-serif
$font-article-Simsun = 'Times New Roman', 'Simsun', 'STSong', '华文宋体', sans-serif
在您的這個配置文件中。不同的字體配置是一個長度不等的序列。所以我有點困惑這些字體分別對應了什麼設置。

_custom.styl是我随便写的，立刻能想到的三个就直接写上了，给你带来困扰真是不好意思…
如果你自己填写，按照其他字符 -> 西文 -> CJK -> serif来填写。
最后这个serif有两个答案，一个是sans-serif，另一个是serif，填这个的原因是：在浏览器都找不到你前面填写的那些字体的时候，采用浏览器默认字体来显示，sans-serif是默认无衬线字体，serif是衬线字体，请务必记得添加。
至于下面那个疑问…我解释起来就费劲了…如果您确实喜欢思源体的话，我下个更新会给你提供一个版本，你看这样行不行

为什么说西文放前面，是因为浏览器找字体的流程就是：该字符在该字体找不到时，跳到下一字体查找。
所以一般西文字体，是不会有中文字体的。故放前面。如果你把类似于苹方字体放前面，那么苹方字体的范围是西文CJK都有，那么就会直接把全部字体交给苹方处理。但是非apple设备是不会有苹方字体的，故所有字体的适配跳到下一字体也就是可能但不限于Helvetica字体，当然这也是我设定的

啊。多謝解釋。我自己搞定了。我可能是 latex 用多了。總覺的應該有特別詳細的一套 setXXXfont。尤其是對於等寬體有一些執着的選擇傾向。現在這樣我只要默認用思源黑或者思源明就行了。雖然達不到完全理想的強迫症效果。但設置起來倒是簡單了。

authors: ColMugX ShadowQuark

repo: ColMugX/hexo-theme-Nlvi


text:
capture groups are in wrong order

For the rather complex regex "^((?:[+-]\\d{6}|\\d{4}))(?:-(\\d{2})-(\\d{2})|(\\d{2})(\\d{2}))(?:(?:T|\\s+)(\\d{2})(?::(\\d{2})(?::(\\d{2})(?:[.,](\\d{1,9}))?)?|(\\d{2})(?:(\\d{2})(?:[.,](\\d{1,9}))?)?)?)?(?:([zZ])|(?:([+-])([01][0-9]|2[0-3])(?::?([0-5][0-9])(?::?([0-5][0-9])(?:[.,](\\d{1,9}))?)?)?)?)(?:\\[((?:(?:\\.\\.[-A-Za-z._]{1,12}|\\.[-A-Za-z_][-A-Za-z._]{0,12}|_[-A-Za-z._]{0,13}|[a-zA-Z](?:[A-Za-z._][-A-Za-z._]{0,12})?|[a-zA-Z]-(?:[-._][-A-Za-z._]{0,11})?|[a-zA-Z]-[a-zA-Z](?:[-._][-A-Za-z._]{0,10})?|[a-zA-Z]-[a-zA-Z][a-zA-Z](?:[A-Za-z._][-A-Za-z._]{0,9})?|[a-zA-Z]-[a-zA-Z][a-zA-Z]-(?:[-._][-A-Za-z._]{0,8})?|[a-zA-Z]-[a-zA-Z][a-zA-Z]-[a-zA-Z](?:[-._][-A-Za-z._]{0,7})?|[a-zA-Z]-[a-zA-Z][a-zA-Z]-[a-zA-Z][a-zA-Z](?:[-._][-A-Za-z._]{0,6})?)(?:\\/(?:\\.[-A-Za-z_]|\\.\\.[-A-Za-z._]{1,12}|\\.[-A-Za-z_][-A-Za-z._]{0,12}|[A-Za-z_][-A-Za-z._]{0,13}))*|Etc\\/GMT[-+]\\d{1,2}|(?:[+\\u2212-][0-2][0-9](?::?[0-5][0-9](?::?[0-5][0-9](?:[.,]\\d{1,9})?)?)?)))\\])?(?:\\[u-ca-((?:[A-Za-z0-9]{3,8}(?:-[A-Za-z0-9]{3,8})*))\\])?$", the JS implementation when matching the string 19761118 yields the following result:
'[
  "19761118",
  "1976",
  null,
  null,
  "11",
  "18",
  null,
  null,
  null,
  null,
  null,
  null,
  null,
  null,
  null,
  null,
  null,
  null,
  null,
  null,
  null
]'

The AS implementation yields the following:
  "matches": [
    "19761118",
    "1976",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "",
    "11",
    "18"
  ]

i.e. groups 4 & 5 are now at the end

Another exmaple,
Regex - ^(\\d{2})(?::(\\d{2})(?::(\\d{2})(?:[.,](\\d{1,9}))?)?|(\\d{2})(?:(\\d{2})(?:[.,](\\d{1,9}))?)?)?(?:(?:([zZ])|(?:([+\u2212-])([01][0-9]|2[0-3])(?::?([0-5][0-9])(?::?([0-5][0-9])(?:[.,](\\d{1,9}))?)?)?)?)(?:\\[((?:(?:\\.[-A-Za-z_]|\\.\\.[-A-Za-z._]{1,12}|\\.[-A-Za-z_][-A-Za-z._]{0,12}|[A-Za-z_][-A-Za-z._]{0,13})(?:\\/(?:\\.[-A-Za-z_]|\\.\\.[-A-Za-z._]{1,12}|\\.[-A-Za-z_][-A-Za-z._]{0,12}|[A-Za-z_][-A-Za-z._]{0,13}))*|Etc\\/GMT[-+]\\d{1,2}|(?:[+\\u2212-][0-2][0-9](?::?[0-5][0-9](?::?[0-5][0-9](?:[.,]\\d{1,9})?)?)?)))\\])?)?(?:\\[u-ca=((?:[A-Za-z0-9]{3,8}(?:-[A-Za-z0-9]{3,8})*))\\])?$
JS Result :-
  [
      "152343.121212121",
      "15",
      "23",
      "43",
      "121212121"
      null,
      null,
      null,
      null,
      null,
      null,
      null,
      null,
      null,
      null,
      null
    ]

AS Result ;-
  [
      "152343.121212121",
      "15",
      "",
      "",
      "",
      "",
      "",
      "",
      "",
      "",
      "",
      "",
      "",
      "23",
      "43",
      "121212121"
    ]

Group 2,3,4 are now at the end.

Thanks @ashutoshvarma I'll investigate this issue shortly.
I'm still super pleased that this regex engine can handle such complex expressions! 😀

@ColinEberhardt  Many thanks for bringing complete regex support to AS ecosystem!
Here is another example, (while porting test cases for PlainTime I am finding many such cases )
It looks like extension of OP example,
Regex (Same as OP post, the PlainDateTIme one) - "^((?:[+-]\\d{6}|\\d{4}))(?:-(\\d{2})-(\\d{2})|(\\d{2})(\\d{2}))(?:(?:T|\\s+)(\\d{2})(?::(\\d{2})(?::(\\d{2})(?:[.,](\\d{1,9}))?)?|(\\d{2})(?:(\\d{2})(?:[.,](\\d{1,9}))?)?)?)?(?:([zZ])|(?:([+-])([01][0-9]|2[0-3])(?::?([0-5][0-9])(?::?([0-5][0-9])(?:[.,](\\d{1,9}))?)?)?)?)(?:\\[((?:(?:\\.\\.[-A-Za-z._]{1,12}|\\.[-A-Za-z_][-A-Za-z._]{0,12}|_[-A-Za-z._]{0,13}|[a-zA-Z](?:[A-Za-z._][-A-Za-z._]{0,12})?|[a-zA-Z]-(?:[-._][-A-Za-z._]{0,11})?|[a-zA-Z]-[a-zA-Z](?:[-._][-A-Za-z._]{0,10})?|[a-zA-Z]-[a-zA-Z][a-zA-Z](?:[A-Za-z._][-A-Za-z._]{0,9})?|[a-zA-Z]-[a-zA-Z][a-zA-Z]-(?:[-._][-A-Za-z._]{0,8})?|[a-zA-Z]-[a-zA-Z][a-zA-Z]-[a-zA-Z](?:[-._][-A-Za-z._]{0,7})?|[a-zA-Z]-[a-zA-Z][a-zA-Z]-[a-zA-Z][a-zA-Z](?:[-._][-A-Za-z._]{0,6})?)(?:\\/(?:\\.[-A-Za-z_]|\\.\\.[-A-Za-z._]{1,12}|\\.[-A-Za-z_][-A-Za-z._]{0,12}|[A-Za-z_][-A-Za-z._]{0,13}))*|Etc\\/GMT[-+]\\d{1,2}|(?:[+\\u2212-][0-2][0-9](?::?[0-5][0-9](?::?[0-5][0-9](?:[.,]\\d{1,9})?)?)?)))\\])?(?:\\[u-ca-((?:[A-Za-z0-9]{3,8}(?:-[A-Za-z0-9]{3,8})*))\\])?$"
JS -
[
    "+0019761118T152330.1+0000",
    "+001976",
    null,
    null,
    "11",
    "18",
    "15",
    null,
    null,
    null,
    "23",
    "30",
    "1",
    null,
    "+",
    "00",
    "00",
    null,
    null,
    null,
    null
]

AS-
[
    "+0019761118T152330.1+0000",
    "+001976",
    "",
    "",
    "15",
    "",
    "",
    "",
    "",
    "",
    "",
    "+",
    "00",
    "00",
    "",
    "",
    "23",
    "30",
    "1",
    "11",
    "18"
]

authors: ColinEberhardt ashutoshvarma

repo: ColinEberhardt/assemblyscript-regex