text:
chore: release v4.1.0

🤖 New release

kiddo: 4.0.0 -> 4.1.0

Changelog

[4.1.0] - 2024-02-17
Chore

Remove unused import
Update actions/cache action to v4
Update codecov/codecov-action action to v4
Update baptiste0928/cargo-install action to v3

Ci

Fix issue with CI lint steps

Deps

Relax strictness of some deps to reduce renovate noise

♻ Refactor

Remove need for gated import

✨ Features

Make tracing an optional dependency gated by tracing feature flag
Iterate over trees
Make rand and rayon optional

🐛 Bug Fixes

Stdsimd removed from unstable, fix:fixup simd removal
Add missing global_allocate feature definition and sort feature defs alphabetically
Update benches to require test_utils feature. update clippy and test steps to include new test_utils feature
Claytonwramsey bug, Fixes:#138

🧪 Testing

Fix iter doctests and remove unused var
Add hacky workaround to enable tests to run without having to specify --features=test_utils

This PR was generated with release-plz.

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

Comparison is base (281287d) 95.32% compared to head (84c93c7) 95.31%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #147      +/-   ##
==========================================
- Coverage   95.32%   95.31%   -0.02%
==========================================
  Files          52       52
  Lines        7573     7573
  Branches     7573     7573
==========================================
- Hits         7219     7218       -1
- Misses        333      334       +1
  Partials       21       21

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter sdd

repo: sdd/kiddo


text:
Fixes #37 - Expireless tokens

Tried to just comment out the key refresh token parts, just for in case we need to reimplement them.
I tested the authorization grant, checked the database to see that no refresh token is being generated.
Besides that, the methodology used to make refresh tokens expireless was to set its duration for 100 years. I did this also for the access tokens.
Related isssue #37

Reimplemented all the refreshToken parts.
Had some trouble revoking a refresh token, but it was solved eventually.

source: gharchive/pull-request

repo: sdec-brasil/dashboard

license: MIT

license_type: permissive

license_source: github-api


text:
GRIP 7.1.1

Add series

[x] Access to electricity, urban (% of urban population) - Canada
[x] Access to electricity, rural (% of rural population) - CanadaAccess to electricity, urban (% of urban population) - Canada

Implemented!

FR

[ ] def: Cet indicateur mesure la proportion de la population ayant accès à l'électricité.

Les pays classés « à haut revenu » selon la classification des pays de la Banque mondiale (80 pays) au cours de l'exercice 2020 étaient supposés avoir complètement fait la transition vers une énergie domestique propre et sont donc signalés comme ayant un accès >95 % aux technologies propres.
comment: Les pays classés « à haut revenu » selon les groupes de pays et de prêt de la Banque mondiale sont censés atteindre l'accès universel dès la première année où le pays a rejoint la catégorie.
computation: Les données étaient disponibles pour rapporter pour cet indicateur comme spécifié dans les métadonnées. Veuillez vous référer aux sources pour obtenir des informations supplémentaires sur les métadonnées ou la source.

source: gharchive/issue

authors: Zelheim catherinemichaud


text:
Feature: 能不能做成系统级别的环境管理

感谢你查看我想法，谢谢
每当我在开发的时候，我一个电脑可能需要切换很多环境（Java 、sdk、pip、其他系统上的环境变量），可以想象成工作生活都分开
比如：app多开、系统切换这样

It is possible to make SDKMAN work at the system level by explicitly setting the SDKMAN_DIR environment variable to some common folder like /usr/local/sdkman. You will need to ensure that the folder has appropriate read/write acces for both your users and that their bash profiles point to the common directory. Please refer to our website installation page for details.

repo: sdkman/sdkman-cli


text:
Add support for macOS arm64

Address #830 by adding "DarwinARM64". No Java candidates will be returned since they are not yet added.

Will be addressed in #846


text:
UI freezes if multiselectcombobox is not visible when a piece of UI is loaded

I am working with the Mahapps UI api to show a custom dialog that contains an SDL multiselectcombobox.  If the combobox is visible on dialog arrange/layout then the dialog will load & present without any issues; however if the combobox's visibility is collapsed then it will lock up the UI indefinitely.  For the time being, my solution is to simply only use this control in containers that will always be visible on presentation, but it would be great if the visibility issues could be addressed.
Cheers!
-Lucy

Alright i have a fix prepared to address this issue.  It was related to 3 infinite loops buried in the control code: ItemsCoerceValueCallback, ItemsPropertyChangedCallback, SuggestionProviderPropertyChangedCallback.
These 3 methods should not be recursively calling themselves on app loaded, because if the visibility of the control is collapsed(Template not applied) then it will be a guaranteed infinite loop.  The fix is to remove these 3 dispatcher calls, and instead make 1 dispatcher call within OnApplyTemplate.  After making this change there are also a couple null checks that need to be added, but they were really needed regardless.

Hi @lucyainsworth, you are right on the money; please check out the latest release 1.0.18 that resolves a threading issue. Can you confirm again with the latest release?

authors: Impertatore lucyainsworth

repo: sdl/Multiselect-ComboBox


text:
conduit-iconv-0.1.1.0 missing hsiconv.h

conduit-iconv fails to build:
Configuring conduit-iconv-0.1.1.0...
cabal: Missing dependency on a foreign library:
* Missing (or bad) header file: hsiconv.h

I think you need to add hsiconv.h to your .cabal file.

https://github.com/fpco/stackage/pull/1016#issuecomment-161547653
I think this is a problem wherever this is tried to be built. Seems no iconv.h is available there. Can you confirm? What platform is this built on?

There is no .h file in the tarball.  I think it should be in c-sources.

Ah, that makes sense. Thanks!

Can you update here when you make a new release? :)

Done already, there's 0.1.1.1 on hackage now

Thank you!

authors: juhp sdroege

repo: sdroege/conduit-iconv


text:
FEATURE REQUEST: Allow libraries other than “Movies”

First - thanks for this.  The idea is spot on and there a lot of potential here.
After a bit of struggling to get this working, I discovered the app is hard coded to expect a single library called “movies”.  My temporary workaround was to use docker to map the app/plex folder to a local directory where I downloaded and modified classes.py.
Any chance to allow the user to use their own library names?  And ideally support more than 1 library?

Hi @JesseWebDotCom thanks for taking the time to submit this feature request. Yes you are right that it is currently hardcoded to use "Movies", which was just my setup at the time that I created this. You are now the second to mention the use of different library names (the first being in #7, so I'll see if I can make this higher priority.
If I roll a PR with a different docker image are you be happy to test it out for me?

Happy to test - just let me know.  Thanks.  I also haven’t gotten the app to actually delete files but I’ll log that issue if it persists in the next test version.

Thanks @JesseWebDotCom.
Please test the docker image selexin/plex-library-cleaner:issue-8 and use the new environment var LIBRARY_NAMES to pass in your library names. You can pass in multiple names by separating them with the ; character.
For example:
docker run \
	-e PLEX_BASE_URL="http://192.169.1.100:32400" \
	-e PLEX_TOKEN="somerandomstring" \
	-e LIBRARY_NAMES="Movies 1;Movies 2" \
	-p 5000:80 \
	selexin/plex-library-cleaner:issue-8

I'm intrigued by your mention of not being able to delete files, but yes at this point it's hard to tell if it is or is not related.

Successfully picked up my 2 libraries
Fails if I had quotes around the names  in my docker compose (maybe you can just ignore single or double quotes)

    environment:
      - LIBRARY_NAMES="Adult Movies;Kid Videos"

Separately:

Suggestion: add a table header with the library name to be able to tell which files belong to which library (without having to look at the path)
FYI - Got the delete working (maybe you can highlight in your README.md); You need to check Settings | Library | Allow media deletion

FWIW, here’s my docker compose if you wanted to add it to your README.md:
version: '3'

services:

  plex-library-cleaner-issue8:
    image: selexin/plex-library-cleaner:issue-8
    container_name: plex-library-cleaner-issue8
    hostname: plex-library-cleaner-issue8
    ports:
      - "5000:80"
    environment:
      - BYPASS_SSL_VERIFY=1
      - PLEX_TOKEN=1234567890
      - PLEX_BASE_URL=http://192.168.1.12:32400
      - LIBRARY_NAMES=Adult Movies;Kid Videos
    restart: unless-stopped

Thanks heaps for testing that and all the additional info!
I've updated the readme with all your info, and have also added the library title to the Movie header:

It's all merged to master and official builds are now available on DockerHub. You can update your container to selexin/plex-library-cleaner:latest or selexin/plex-library-cleaner:1.1.0. (Make sure to docker pull selexin/plex-library-cleaner:latest again to update it).
Thanks again!


text:
[功能]：私骰模式实现的一种思路

在提问之前...

[X] 我填写了简短且清晰明确的标题，以便开发者在翻阅 issue 列表时能快速确定大致问题。而不是“一个建议”、“卡住了”等
[X] 我基本确定这是一个新功能/建议，而不是遇到了 bug（不确定的话请附上日志）

说说你遇到的问题？
同 #791
对该issue做一个细化
有什么好的想法？
1、与白名单联动，可以尝试在私骰模式，由master通过 .ban trust 指令给予trust用户，无trust用户的好友申请自动忽略/拒绝，同时，检测到无trust用户强制拉群，自动退出该群并发送相关信息（类似黑名单操作）
2、如果上述方案存在实现困难，则是否可以存在中间件可以实现通过调用海豹的黑白名单进行退群和好友申请相关处理？
其他内容
No response

直接评论在 #791 下吧，同一个需求不要提两个 issue。

authors: JustAnotherID kenichiLyon

repo: sealdice/sealdice-core


text:
docs: sealer is not supported by root users

Signed-off-by: Xinwei Xiong 3293172751nss@gmail.com<!--  Thanks for submitting a pull request! Here are some tips for you:

Please make sure you have read and understood the contributing guidelines: https://github.com/alibaba/blob/master/CONTRIBUTING.md
Please make sure the PR has a corresponding issue.
-->

Describe what this PR does / why we need it
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

pls fix lint


text:
http://api.sealtalk.im/user/zj3AqojRy

在源码中，request headers 哪里设置了cookies?

cookie是自动带上的，不需要手工处理，只需要让server和web同处于一个父域下即可。
你可以在sealtalk在线体验里抓包看看 http://web.sealtalk.im/

嗯，是的，谢了

authors: shuise slowsay

repo: sealtalk/sealtalk-web

license: mit

license_source: bigquery


text:
Support generic devices, e.g., locks that don't have a locked property, etc.

We would need to disable a few elements, e.g., the lock toggle and lock status.
Can we fix this in version 4, but also backport the fix to https://github.com/seamapi/react/tree/2.20.x ?
Need to update isLockDevice. If there is no locked property, then check for existence of at least one of the lock or access code capability flags.

Patches some edge cases in v2 that need to be ported to v4: https://github.com/seamapi/react/compare/v2.20.0...2.20.x

repo: seamapi/react


text:
Gotcha postgres: unique_index_on_selector? does not work as expected

Current behavior
The standard way of defining a unique index for table integrity in rails is to call add_index(..., unique: true).  This calls CREATE UNIQUE INDEX in postgres to define the unique constraint.
Gotcha!
upsert is using information_schema.constraint_column_usage to determine if a table has a unique constraint which is different than a unique index in postgres.  Considering the method name suggests you're checking for unique index, maybe we should change the name?
Related documentation
https://www.postgresql.org/message-id/49E798A3.2020805%40fmed.uba.ar
And the reply
https://www.postgresql.org/message-id/3622.1239912596%40sss.pgh.pa.us
Fix
Quick fix
you need to define a constraint in postgres like so:
ALTER TABLE $1
ADD CONSTRAINT $2 UNIQUE
    USING INDEX $2

where $1 is the table name and $2 is the name of the unique index
but warning: if you are using rails and the :ruby schema_format for your schema dump, the constraint will not be captured.  You will need to change your format to :sql
Fix the gem
Use a combination of pg_class, pg_index, and pg_attribute to look for unique indexes.
related SO post

I’ll change the name, as we want to look for a unique constraint (a unique
index does not necessarily work) in order for INSERT ... ON CONFLICT ...
work.
On Sat, Aug 18, 2018 at 9:55 PM Kevin Coleman notifications@github.com
wrote:

Current behavior
The standard way of defining a unique index for table integrity in rails
https://apidock.com/rails/ActiveRecord/ConnectionAdapters/SchemaStatements/add_index
is to call add_index(..., unique: true). This calls CREATE UNIQUE INDEX
in postgres to define the unique constraint.
Gotcha!
upsert is using information_schema.constraint_column_usage to determine
if a table has a unique constraint which is different than a unique
index in postgres. Considering the method name suggests your checking for
unique index, maybe we should change the name?
Related documentation
https://www.postgresql.org/message-id/49E798A3.2020805%40fmed.uba.ar
And the reply
https://www.postgresql.org/message-id/3622.1239912596%40sss.pgh.pa.us
Fix Quick fix
you need to define a constraint in postgres like so:
ALTER TABLE $1
ADD CONSTRAINT $2 UNIQUE
USING INDEX $2
where $1 is the table name and $2 is the name of the unique index
Fix the gem
Use a combination of pg_class, pg_index, and pg_attribute to look for
unique indexes.
related SO post
https://stackoverflow.com/questions/2204058/list-columns-with-indexes-in-postgresql
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/seamusabshere/upsert/issues/111, or mute the thread
https://github.com/notifications/unsubscribe-auth/AACNf2gloDaFRBLOV-gXIJB1r56q_nOxks5uSO-ngaJpZM4WC1Bk
.

@pnomolos
If you're just changing the name, this will make your gem difficult to use with rails b/c the alter table would not be reflected in your schema.rb file which most rails projects use to define the schema.

Why does the unique index not work?

Because Postgres requires a unique constraint, not a unique index, in order
to use that syntax. Took me a couple days of banging my head against the
wall to sort that one out.
On Sat, Aug 18, 2018 at 10:04 PM Kevin Coleman notifications@github.com
wrote:

Why does the unique index not work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/seamusabshere/upsert/issues/111#issuecomment-414103801,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACNf6UKUdtqtD-YRGtZWeX0T6RmzcIuks5uSPHqgaJpZM4WC1Bk
.

I can add a note that you need to ensure you’re using a constraint in order
for the gem to use the native functionality instead of the generated
function.
On Sat, Aug 18, 2018 at 10:06 PM Philip Schalm pnomolos@gmail.com wrote:

Because Postgres requires a unique constraint, not a unique index, in
order to use that syntax. Took me a couple days of banging my head against
the wall to sort that one out.
On Sat, Aug 18, 2018 at 10:04 PM Kevin Coleman notifications@github.com
wrote:

Why does the unique index not work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/seamusabshere/upsert/issues/111#issuecomment-414103801,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACNf6UKUdtqtD-YRGtZWeX0T6RmzcIuks5uSPHqgaJpZM4WC1Bk
.

that is so lame.  Yes, please add a note.  I spent 3 hours poking at this gem trying to figure out why inserting 60k rows took 30 minutes on my dev machine.
The only other thing that was slow was the batch not batching the network calls.

What’s your setup?  It’s very curious that it’s taking that long - even on my 2011 MBP it’s faster than that.  If every call is over the network, though, that would make sense.

I misread the csv file. When I opened it up in "Apple Numbers", ignored the warning of "there are 1,400,000 rows, but we are only going to show 65k".
On my 2016 MBP with pg running locally and 16GB ram, 1.4m records with use_pg_native? as true takes 26 minutes, which is more understandable.
===
I made a PR to add a warning if use_pg_native? is false
https://github.com/seamusabshere/upsert/pull/112

Closed via #112

authors: KevinColemanInc pnomolos

repo: seamusabshere/upsert


text:
TypeError: Object of type StringMatch is not JSON serializable

Changes in yara-python 4.3.0 cause the error "TypeError: Object of type StringMatch is not JSON serializable" to occour when the yaramail attempts CLI attempts te generate results in JSON format.
See: https://github.com/VirusTotal/yara-python/issues/230https://github.com/VirusTotal/yara-python/issues/230

Fixed in yaramail 3.1.10 by pinning yara-python to 4.2.3

yaramail 3.2.0 supports yara-mail 4.3.0

repo: seanthegeek/yaramail


text:
读隔离和写隔离是如何体现出分布式事务的

写隔离举的例子：
两个全局事务Tx1和Tx2，它们使用的本地锁是互斥的吗？Tx1和Tx2两个事务如果是对同一个数据库表进行操作，就没必要使用分布式事务了，直接依赖数据库的隔离特性就可以做到，所以这个地方有点不明白

tx1写了数据A tx2去读数据A，这俩一定是在同一时间去做的吗？你把时间概念加进去，tx1可能早就提交了，但是在全局事务下是属于未提交

加上时间确实是好理解了，谢了


text:
🎉 4.0.15

ℹ About this release

Version: 4.0.15
Type: patch
Last Release: 4.0.14 (10/25/2023, 5:58:20 PM) [?]
Commits to merge: 10 [?]

📦 Dependencies

Update semantic-release from ^22.0.5 to ^22.0.7

📦 Development Dependencies

Update @sebbo2002/semantic-release-docker from ^4.0.1 to ^4.0.2
Update eslint from ^8.51.0 to ^8.53.0

:tada: This PR is included in version 4.0.15 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
File-system change to edited file is not recognised

I noticed the following:

Save file in OLS.
Edit file with Notepad++, save.
Alt-Tab back to OLS. Save again. No complaints, save simply executed.
Alt-Tab to Notepad++. Notepad++ complains that the content of the file changed and asks if it should be reloaded.

I think OLS should guard file integrity in the same way as NP++ does (ask for reload if no edits, ask for new save location/overwrite if there are).

Hi, is anyone working on this? Or can I start working on this? @sebbrudzinski

authors: Amitbhave LordFarin

repo: sebbrudzinski/Open-LaTeX-Studio


text:
Add mixin for focus state

Add utility mixin that can be reused by components that need to have a focus and active state

:tada: This issue has been resolved in version @sebgroup/green-angular@1.0.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This issue has been resolved in version @sebgroup/chlorophyll@1.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This issue has been resolved in version @sebgroup/green-charts@1.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This issue has been resolved in version @sebgroup/green-react@1.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This issue has been resolved in version @sebgroup/green-react-charts@1.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag) :package::rocket:
GitHub release :package::rocket:

authors: hjalmers sebopensource

repo: sebgroup/green


text:
非平衡求交，报ConnectionError问题

Issue Type
Bug
Source
binary
Secretflow Version
使用docker方式按latest方式安装的secretflow
OS Platform and Distribution
CentOS 7
Python version
3.10.13   docker方式安装
Bazel version
No response
GCC/Compiler version
No response
What happend and What you expected to happen.
[ root@localhost ~]# python alice_offline.py
Since the GPL-licensed package unidecode is not installed, using Python's unicodedata package which yields worse result
s.
2024-09-13 02:04:56,845 INFO worker.py:1540 -- Connecting to existing Ray cluster at address: 10.2.11.72:3255...
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/ray/_private/worker.py", line 1680, in init
_global_node = ray._private.node.Node(
File "/usr/local/lib/python3.10/site-packages/ray/_private/node.py", line 153, in init
self. init gcs client( )
File "/usr/local/lib/python3.10/site-packages/ray/_private/node.py", line 730, in _init_gcs_client
raise RuntimeError(
RuntimeError: Failed to connect to GCS.
During handling of the above exception,another exception occurred:
Traceback (most recent call last):
File "/root/alice_offline.py", line 87, in <module>
app.run(main)
File "/usr/local/lib/python3.10/site-packages/absl/app .py",line 308, in run
run main(main,args)
Fiie "/usr/local/Lib/python3.10/site-packages/absl/app .py",line 254, in _run_main
sys.exit(main(argv))
File "/root/alice offline.py", line 42,in main
sf.init(address='10.2.11 .72:3255'，cluster_config=cluster_config,log_to_driver=True,omp_num_threads=multiprocess.cpu_c
ount())
File "/usr/local/ib/python3.10/site-packages/sec ret flow/device/driver.py", line 557, in init
ray.init(
File "/usr/local/lib/python3.10/site-packages/ray/_private/client_mode_hook .py", line 103, in wrapper
return func(*args,**kwargs)
File "/usr/local/lib/python3.10/site-packages/ray/_private/worker.py",line 1696, in init
raise ConnectionError
ConnectionError

Reproduction code to reproduce the issue.
使用下方的代码做非平衡求交，对应的data10w和data500w csv数据，已放到root/input目录下，以及secret_key.bin也放到了root目录下。
使用docker创建容器时，使用了host主机模式，同时把脚本中涉及的四个端口也与主机端口映射。

使用非平衡求交的脚本代码如下：
import os
import sys
import time
import logging
import multiprocess
from absl import app
import spu
import secretflow as sf
#import random
# init log
logging.basicConfig(stream=sys.stdout, level=logging.DEBUG)
cluster_config ={
    'parties': {
        'alice': {
            'address': '10.2.11.72:3255',       #ray proxy端口不可冲突
            'listen_addr': '0.0.0.0:3255'           #本地
        },
        'bob': {
            'address': '10.2.11.76:3256',       #ray proxy端口不可冲突
            'listen_addr': '0.0.0.0:3256'           #本地
        },
    },
    'self_party': 'alice'
}
# SPU settings
cluster_def = {
    'nodes': [
        {'party': 'alice', 'address': '10.2.11.72:12946', 'listen_address': '0.0.0.0:12946'},
        {'party': 'bob',   'address': '10.2.11.76:12947', 'listen_address': '0.0.0.0:12947'},
    ],
    'runtime_config': {
        'protocol': spu.spu_pb2.SEMI2K,
        'field': spu.spu_pb2.FM128,
    },
}
link_desc = {
    'recv_timeout_ms': 3600000,
}
def main(_):
    # sf init
    sf.shutdown()
    sf.init(address='10.2.11.72:3255', cluster_config=cluster_config, log_to_driver=True,omp_num_threads=multiprocess.cpu_count())
    # init log
    logging.basicConfig(stream=sys.stdout, level=logging.DEBUG)
    alice = sf.PYU('alice')
    bob = sf.PYU('bob')
    offline_input_path = {
        alice: '/root/input/data10.csv', # alice作为小数据一方
        bob: '/root/input/data500.csv', # bob作为大数据一方
    }
    select_keys = {
        alice: ['x1'],
        bob: ['x1'],
    }
    offline_output_path = {
        alice: "/root/output/unbalanced_10w_out.csv",
        bob: "/root/output/unbalanced_500w_out.csv",
    }
    offline_preprocess_path = "/root/preprocess/offline_psi.csv"
    secret_key = "000102030405060708090a0b0c0d0e0ff0e0d0c0b0a090807060504030201000"
    secret_key_path = "/root/secret_key.bin"
    spu = sf.SPU(cluster_def, link_desc)
    # offline离线阶段
    print("=====offline phase====")
    start = time.time()
    with open(secret_key_path, 'wb') as f:
            f.write(bytes.fromhex(secret_key))
    reports = spu.psi_csv(
        key=select_keys,# 用于求交的列
        input_path=offline_input_path,# 用于求交的CSV文件，配置绝对路径
        output_path=offline_output_path,# 输出的CSV文件，配置绝对路径
        receiver='alice',  # 求交结果接收方if `broadcast_result=False`, only receiver can get output file.
        protocol='ECDH_OPRF_UB_PSI_2PC_OFFLINE',   # PSI求交协议，psi protocol，这里是离线阶段
        precheck_input=False,  # 是否在求交之前，检查列 will cost ext time if set True
        sort=False,  # 求交结果是否排序 cost ext time if set True
        broadcast_result=False,  # 是否给各方广播求交结果，will cost ext time if set True
        bucket_size=10000000,# PSI中指定哈希桶大小
        curve_type="CURVE_FOURQ",# ocdh的加密曲线
        preprocess_path=offline_preprocess_path,#在非平衡求交协议中，预处理文件路径
        ecdh_secret_key_path=secret_key_path,# ecdh_opf秘密密钥文件路径
    )
    #print(f"psi reports: {reports}")
    logging.info(f"offline psi reports: {reports}")
    logging.info(f"cost time: {time.time() - start}")
    sf.shutdown()
if __name__ == '__main__':
    app.run(main)

@wjwJack 请注意
你的ray proxy端口和sf.init的端口重复了，也就是3255被ray proxy和sf.init同时使用。
可以看到代码已经备注ray proxy端口不可冲突

@wjwJack 请注意 你的ray proxy端口和sf.init的端口重复了，也就是3255被ray proxy和sf.init同时使用。 可以看到代码已经备注ray proxy端口不可冲突

把sf.init用的端口换了3257，再次执行脚本，还是同样的错

看起来是Ray没有启动，先把Ray启动起来，注意端口号不要重复
ray start --head --node-ip-address="10.2.11.72" --port="3155" --resources='{"alice": 16}' --include-dashboard=False --disable-usage-stats
ray start --head --node-ip-address="10.2.11.76" --port="3155" --resources='{"bob": 16}' --include-dashboard=False --disable-usage-stats

看起来是Ray没有启动，先把Ray启动起来，注意端口号不要重复 ray start --head --node-ip-address="10.2.11.72" --port="3155" --resources='{"alice": 16}' --include-dashboard=False --disable-usage-stats ray start --head --node-ip-address="10.2.11.76" --port="3155" --resources='{"bob": 16}' --include-dashboard=False --disable-usage-stats

好的，谢谢

authors: Chrisdehe wjwJack

repo: secretflow/secretflow


text:
Resolve and ResolveEnv

This PR contains the following new functionality to the client:

Resolve fetches the values of a secret from SecretHub, when the ref parameter has the format secrethub://<path>
ResolveEnv takes a map of environment variables and replaces the values of those which store references of secrets in SecretHub (secrethub://<path>) with the value of the respective secret.

Do you need Resolve(ref) to be public? If not, we could keep it private for now, so that we can delete the function later and move the functionality to the Read function, without any breaking changes.

Do you need Resolve(ref) to be public? If not, we could keep it private for now, so that we can delete the function later and move the functionality to the Read function, without any breaking changes.

It is needed in the XGO Project, so we want it to be exported.
I think the best course of action would be to implement this in the XGO project and move it to the Go client once we decide on how we want to make it public.

I do think that secrethub run with the environments may be something very useful, both for developer and for docker containers.
As for reducing duplicates. if we implement the functionality in the SDK, then in CLI we only need to make the call and print the putput, which simplifies it.
Accepting references as paths can be easily adjusted if we implement it in the SDK. if we want it with a flag, we call the Resolve function only then, otherwise it can be always called, since the path will remain untouched if it is not a reference.
In my opinion, the necessary adjustment to bring this new feature are small. Now it is up to you to what extent you want to accept this and how should the user make use of this. In either case, the adjustments are small.

@Marton6 I like that cut :+1: It's relatively little code, so it shouldn't be too much work to implement it in the XGO project I assume?
It will enable us to quickly proceed with the .NET SDKs and pick it up for the GO SKD / CLI commands later.
While I do agree, @edif2008 , that it's probably going to be just a couple of slight modifications to the code, I think to make sure it's consistent across all places will require some dedicated attention and time. For example, I expect a discussion about to what extend we allow the secrethub:// syntax to be used on other types of paths: secrets, directories, probably yes. But do we also allow it for "repo paths" or even workspaces/namespaces/org-names/usernames ? That's a discussion we can postpone for now and focus on the .NET SDK first.

Closed because this feature is not a priority and requires a significant amount of planning to be implemented. This feature will be discussed and implemented in the future.

repo: secrethub/secrethub-go


text:
Abstract class vs Interface distinction and their implementation in C#

Topic Suggestion
Proposal Submission
Proposed title of article
[Languages] Abstract class vs Interface distinction and their implementation in C#
Proposed article introduction
Unnecessary details can be hidden using Abstraction in C#. There will be less emphasis on how things work and more on what they do. It's a popular choice for large, intricate implementations. This is accomplished through the use of abstract classes and interfaces in C#. We can create the functionality required by a derived class in an abstract class. Functionality or functionalities can be defined, but the interface cannot be implemented. As the name suggests, this is a subclass derived from an interface.
Key takeaways
By the end of this article the learner will be able to understand:

What are abstract classes and interface in C#
The distinguishing feature or factors between an abstract class and interface in C#
How to work with the abstract class as well as an interface in C#
The advantages and disadvantages while working with abstract classes as well as an interface in C#

Article quality
This article will be more of differentiating between abstract classes and interface in C#. I aim at using a well and elaborate approach and in an in-depth manner while working with these concepts. The article will be more interesting and I will provide relevant examples and with an easy simple but understandable language more friendly to beginners. I will also provide detailed head-to-head comparisons with key differences between these concepts.
References
N/A

Hi @gracy20
Thank you for your response and we thank you for submitting your topic. After some careful consideration it struck us that this topic may be a bit over saturated throughout other blog sites and official documentations as previously mentioned on your topic form by our content moderator.
We typically refrain from publishing content that is covered widely on the net or other blogs. As we're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
We believe this is the best way for students to build a great portfolio (for potential employers) is by building what does not exist and what can provide the most value.
You are more than welcome to pursue another more in depth topic


text:
[LANGUAGES] Manipulating Excel(Spreadsheet) data and files in Android

Topic Suggestion
[ANDROID || LANGUAGES] Manipulating Excel(Spreadsheet) data and files in Android
Writing sample(s):
My samples are found here
Proposal Submission
Proposed title of the article
Manipulating Excel(Spreadsheet) files in Android
Proposed article introduction
Maybe you are trying to preprocess data for some custom on-device model or you want to create your own spreadsheet app, you have to know how to first manipulate the spreadsheets. In his article, we will look at loading a spreadsheet file, opening it, and then performing common statistical functions in it.
Key takeaways
The user will learn about:

Accessing spreadsheets in Android.
Using Kotlin to implement this.
Performing common statistical functions such as mode, median, variance, standard deviation, etc.
Additionally, how Retrofit may be handy in getting a hosted spreadsheet.

Article quality
It will be simple to follow and guide the user on getting the files from the local and shared storage. We will also perform the statistical functions, something other blogs haven't shown.

We might also look at saving changes done to a spreadsheet. I'm still doing my research on this.

References
I used this to get insights. It talks about reading one from Google Sheets.

good topic @vinstex - approved. One important note: please be sure to put your article through a thorough grammar/readability editing review prior to submitting for final approval. This will help increase the likelihood of your article getting published and you receiving a payout :)

authors: LinusMuema vinstex


text:
Some Matroska and OGG files fail to play.

I'm playing these files using the latest Lavalink. Stacktrace indicates it's a Lavaplayer issue.
Both of these files are a little loud.
Sample Matroska file
Sample OGG file
Matroska stacktrace
OGG stacktrace

OGG: currently multi-stream (video+audio for example) OGG files are not supported, only plain audio. It would require a bit different handling of OGG format than I have now.
MKV: will look into it, I may have limited the codec metadata size to too low so there are valid ones it rejects.

Any updates on this, sed?

authors: Giggitybyte sedmelluq

repo: sedmelluq/lavaplayer


text:
vue3中使用graphPlug的问题

在vue3+ts项目中使用到了graphPlug插槽，按照示例上写#graph-plug但是ts报类型错误，
，
直接写#graphPlug又完全不生效，插槽中的内容完全不会渲染出来

这是因为声明文件写的有问题，但不影响使用。使用graph-plug没有问题，只不过你这可能设置的ts校验太严格了，禁用掉这个错误或者暂时手工修改一下声明文件都可以解决这个问题：

下个版本会更新声明文件的错误。就这两天会发布出来，relation-graph@2.1.18

authors: ListeningRift seeksdream

repo: seeksdream/relation-graph


text:
Add Google Analytics

``

done


text:
Installation fails on Apple Silicon (M1)

Diagrams rules.
I love diagrams, long since replaced using dot native.
recently I upgraded to an M1 mac, and unfortunately diagrams doesn't seem to work on M1.
npm install -g diagrams
fails due to an electron dependency.
Electron will only work with 11.0 or above on m1 - so I checked out this diagrams repository and replaced the dependency, and install npm install . but then it says it installs fine, yet does not / diagrams doesn't work.
I'm not a node developer and the chance of me figuring this out and contributing a solution is very low.
I write in case anyone else has successfully gotten diagrams to install on M1.

i am also facing similar issue

electron@3.1.13 postinstall /usr/local/lib/node_modules/diagrams/node_modules/electron
node install.js

internal/modules/cjs/loader.js:905
throw err;
^
Error: Cannot find module '/usr/local/lib/node_modules/diagrams/node_modules/electron/install.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12)
at internal/main/run_main_module.js:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/diagrams/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! electron@3.1.13 postinstall: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the electron@3.1.13 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-03-30T11_14_18_578Z-debug.log

authors: cs-akash-jarad nanodust

repo: seflless/diagrams


text:
Replace substitute package

The current substitute package isn't published on npm.
We can either get someone to publish it, or we can just replace its functionality. I think the latter will be simpler.

..or we can just replace its functionality.

Seeing there's about 10 lines of code involved and the code hasn't changed for 5 years, I would also be tempted to copy-paste those lines into this project 🤷♂

authors: XhmikosR phillipj

repo: segmentio/metalsmith-permalinks


text:
Gifs > Screenshots

A single gif is worth three screenshots 😃

Absolutely. Done.
Thanks :)

authors: moyheen segunfamisa

repo: segunfamisa/bottom-navigation-demo


text:
Loading multiple inventories

I am trying to load both a TF2 and a CS:GO inventory, but once it's loaded it seems to unload itself.
My loadInventory code(s):
steamTrade.loadInventory(440, 2, function(inv) {
	myTF2Keys = inv.filter(function(item) {
		return item.name === 'Mann Co. Supply Crate Key';
	});
	myMetal = inv.filter(function(item) {
		return item.name === 'Refined Metal';
	});
});
steamTrade.loadInventory(730, 2, function(inv) {
	myCSGOKeys = inv.filter(function(item) {
		return item.type === 'Base Grade Key';
	});
});
bot.sendMessage(steamID, 'I currently have ' + myTF2Keys.length + ' TF2 keys, ' + myCSGOKeys.length + ' CS:GO keys, and ' + myMetal.length + ' refined metal.');

When the message is sent at the end, they all show 0, even though I threw a console log after the myMetal = inv.filter function and the myCSGOKeys = inv.filter function, and they both said 3.

I found a workaround for this issue. I defined 3 variables, all with the value of the length of its array. For example, myMetalNumber is equal to myMetal.length.

Currently mobile, but it seems that you use the asynchronous loadInventory call twice, to then send the chat message before being sure the loadInventory calls are actually done.

As @jabbink has already pointed out, the loadInventory functions are async therefore this won't work. You should probably read some articles about asynchronous programming before creating another "it somehow works" solution. :+1:

authors: dragonbanshee jabbink scholtzm

repo: seishun/node-steam


text:
Changes Reserved Iterable name to IterableType

Library breaks in 7.1 due to Iterable being reserved name.

LGTM

authors: JasonGFitzpatrick MarkVaughn

repo: sellerlabs/nucleus


text:
Support Travis Enterprise

See https://github.com/semantic-release/semantic-release/issues/540
I'd be happy to provide a PR for this 🙂

BTW, have you tried emailing Travis about getting access to an enterprise instance for testing? I haven't mailed them before, but I'm hopeful they'd be positive towards helping with an integration for semantic-release.
https://docs.travis-ci.com/user/enterprise/#Trials-and-Licensing

Anyways, I can test on Travis Enterprise as we use it at work. Ay ideas on where to start? I have no idea from where the call which fails even comes from.
(and I don't think I can remotely debug either, so it'll be push and see what happnes...)

The problem is actually in semantic-release/travis-deploy-once which use https://github.com/pwmckenna/node-travis-ci.
Unfortunately pwmckenna/node-travis-ci doesn't support Travis Enterprise. See lib/travis-http.js#L5.
In condition-travis we need to:

Add a new config option travisUrl that can be configured via a plugin option or an environment variable. See githubUrl  in https://github.com/semantic-release/github for an example.
Pass this url to https://github.com/semantic-release/travis-deploy-once

Then semantic-release/travis-deploy-once will have to make API calls with this url. There is multiple approach to achieve (by order of preference):

Open a PR with https://github.com/pwmckenna/node-travis-ci to support an additional travisUrl parameter (that should be fairly easy to do, so I strongly favor this options)
Replace pwmckenna/node-travis-ci by another lib that supports Travis Enterprise
Implement all the API calls in semantic-release/travis-deploy-once with an http library like https://github.com/sindresorhus/got

We would gladly accept PRs on all that!
For now you can also set the environment variable BUILD_LEADER_ID to select on which job number semantic-release should run. By doing so the call to semantic-release/travis-deploy-once will be skipped and no API call will be made. See an example here (The build stage part is not required).

👍 It seems a PR would be welcomed to solve pwmckenna/node-travis-ci#21 :)

PR sent. Not sure if it'll be released right away, though: https://github.com/pwmckenna/node-travis-ci/pull/19#issuecomment-346230739

BUILD_LEADER_ID seems ignored - all 3 of my builds (node 8, 6, and 9) try to run semantic-release, and they all fail with the api error towards travis

That's quite surprising....The Node 6 job should exit right away due to https://github.com/semantic-release/semantic-release/blob/caribou/bin/semantic-release.js#L9
What value did you set for BUILD_LEADER_ID ?

Not if Travis allow to export variables like that. Can you set it in your travis.yml like that:
env:
  - BUILD_LEADER_ID=1

Oh sorry, I lied. Node 6 is not ran!
Relevant part of my .travis.yml:
language: node_js
node_js:
- 8
- 6
- 9
before_install:
- export NPM_TOKEN=""
script:
- yarn commitlint --from="$TRAVIS_BRANCH" --to="$TRAVIS_COMMIT"
- yarn commitlint --from=$TRAVIS_COMMIT
- yarn test
after_success: yarn semantic-release --debug
cache:
  yarn: true
branches:
  only:
  - master
env:
  global:
  - GITHUB_URL=https://github.schibsted.io
  - GITHUB_PREFIX=/api/v3
  - NPM_USERNAME=$ARTIFACTORY_USER
  - NPM_PASSWORD=$ARTIFACTORY_NPM_SECRET
  - NPM_EMAIL=$ARTIFACTORY_USER
  - BUILD_LEADER_ID=1
  - secure: some token

From what I can see in the code, the auth request to travis is always sent: https://github.com/semantic-release/travis-deploy-once/blob/ad21dc45a20f9029d3f14758e9ca7d58d4bc2eae/lib/travis-deploy-once.js#L31

Looking at the code more in detail the workaround will not work... The API is called no matter what...Sorry for the confusion.

I looked into sending a PR, but because of waitForOtherJobs there's no way to avoid the API calls

Yes, we test if there is other jobs and if they are completed, even with Build stages enabled.

Ok. Will give pwmckenna/node-travis-ci#22 a couple of days then, before I start thinking about replacing it in semantic-release/travis-deploy-once 🙂

If we had to to re-implment the calls with an http library it would be great to do so with the API v3. As v2 is deprecated.

authors: SimenB pvdlg

repo: semantic-release/condition-travis


text:
Update schemas in graphql prototype

Four actions are required:

[x] Delete superfluous schemas
[x] Add schema's to run the examples in the documentation
[x] Add schema options to arguments of the script
[x] Document how to use the prototype with arguments for different schemas in dev docs

@bobvanluijt and/or @moretea, is there a reason to keep all the test schema's in the prototype? If not I will throw them out.
According to @JeroenStravers1 I can delete them since he's using a different source for testschemas.

If @JeroenStravers1 doesn't need them you can remove them. Please note that you could even go as far as using these in the prototype.
So you would have;

Test schema
Bigger schema for readability.

PS:
Please also check with Dominique if he isn't using them.

Closing as prototype has been deprecated.

authors: bobvanluijt etiennedi laura-ham

repo: semi-technologies/weaviate


text:
ci: fix clippy

2 fixes for the clippy checks:

Fail on warnings
--all-targets, which somehow unearthed a lot of warnings

Then I fixed all the warnings in several passes.

Rebased onto latest main


text:
Make middleware functions run in right order;

Middleware should run in order in which they were registered. So now middleware functions wrapping in reverse order to do so.

Codecov Report

Merging #9 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master       #9   +/-   ##
=======================================
  Coverage   54.19%   54.19%
=======================================
  Files           4        4
  Lines         286      286
=======================================
  Hits          155      155
  Misses        105      105
  Partials       26       26

Impacted Files
Coverage Δ

server.go
72.59% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-io dizzyfool

repo: semrush/zenrpc


text:
feat: add all domain management tools for SolanaAgentKit

Added AllDomains Features to Agent API:
Domain Resolution
Added agent.resolveAllDomains(domain) to resolve a domain's public key.
Lookup Owner
Added agent.getOwnedAllDomains(owner) to retrieve all domains owned by a specific owner.
Get Domains on TLD
Added agent.getOwnedDomainsForTLD(owner, tld) to fetch all domains owned under a specific TLD.
Get All Active TLDs
Added agent.getAllDomainsTLDs() to list all currently active TLDs.
Get All Registered Domains
Added agent.getAllRegisteredAllDomains() to fetch all registered domains across all TLDs.
Get User Main Domain
Added agent.getMainAllDomainsDomain(owner) to retrieve a user's favorite or main domain..
This pull request was created for https://app.gib.work/bounties/57ed99db-7c9b-4239-ab05-5be02971f586 in an attempt to solve a bounty #15 . Payment for the bounty is immediately sent to the contributor after merge.

hey - can you pls follow this guide to also include the langchain tool class
https://docs.solanaagentkit.xyz/v0/guides/add_your_own_tool#2-implement-the-tool-class

Added new tools to langchain tool class

hey @thearyanag just want to check if everything's good!

Maybe @arihantbansal could help out?

authors: ancienthumans thearyanag

repo: sendaifun/solana-agent-kit


text:
Update getting-started-with-automation.md

Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @Whatthefoxsays,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX

authors: Whatthefoxsays thinkingserious

repo: sendgrid/docs


text:
How to get sender id

Issue Summary
I am registering sender using below API
$sg->client->senders()->post($request_body);
Its response me 400"  statusCode":protected]=> int(400) ["body":protected]=> string(105) "{"errors":[{"message":"You already have a sender identity with the same nickname.","field":"nickname"}]}
Now I want that user sender id
I used the below API but getting an empty response.
https://api.sendgrid.com/v3/senders
I know I have senders but still getting an empty responses.
Technical details:

sendgrid-php version: V3
php version: 7

Have you addressed this issue you see?
You already have a sender identity with the same nickname
Also, have you tried doing the api call without using the helper library?

how can I get the sender id from SendGrid if the sender already registers?

Hello @hiteshSonagra,
I believe this API call might be what you need.
With best regards,
Elmer

repo: sendgrid/sendgrid-php


text:
Course Meta Data

date created
date modified
name
descp
version
more?

https://stackoverflow.com/questions/30739931/store-metadata-in-csv-file

A work-around here is to display the filename, which could include name, date created, version.

That's a great idea. Thanks!

authors: charkour kvlinden

repo: senior-knights/course-schedulizer


text:
fixed unarchive

combined two steps

👍

authors: jaredledvina ttic-admin

repo: sensu/sensu-ansible


text:
문제 추가! Quiz Request: (문제 입력 Enter your quiz title)

이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description

언어가 선택되지 않았고, 문제가 지정되지 않았으며, 풀이도 없습니다. 해당 이슈를 기각합니다.

s

ㄴ

s

ㄴ

네

ㅍ

이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description

이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description

이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description

이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description

이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description이 템플릿은 한국어와 영어로 쓰여 있습니다.
This template is both written Korean and English.
(꼭, 이슈 하나당 하나의 문제만 적어주세요! Please write only one question per issue!)
문제의 언어 Quiz Language (Programming Language)
문제 Question (OX로 문제를 풀수있어야 합니다 Yes/No quiz)
여기에 문제를 입력해 주세요. (~에서는 ~해서 ~한다.) Enter question here
답 Answer

[ ] O
[ ] X

풀이 Answer Explanation
( 자세하게 해줘요! Write it detailed! )
사진 (선택) Image (Optional)
사진 설명 Image Description

도배가 확인되어 이슈를 잠궜습니다.
만약 문제를 추가하고 싶다면 새 이슈를 생성하여 주시기 바랍니다.

authors: Javselver LLOOOOTT comjun04

repo: seoaapp/SeoaBot


text:
Ambiguous attribution

Hello,
Could you please state in the project description and ReadMe that this project is not affiliated with Notational Velocity?
With the current description, some people may mistakenly believe that this is an official component or sub-project of Notational Velocity.
Thank you in advance for your help and understanding.
Regards,
Zachary Schneirov

Hi Zachary, I will rewrite the readme tonight. I am really sorry to make
you pinged.
On Mon, May 22, 2017 at 10:59 Zachary Schneirov notifications@github.com
wrote:

Hello,
Could you please state in the project description and ReadMe that this
project is not affiliated with Notational Velocity?
With the current description, some people may mistakenly believe that this
is an official component or sub-project of Notational Velocity.
Thank you in advance for your help and understanding.
Regards,
Zachary Schneirov
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/seongjaelee/nvatom/issues/73, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA54TQFEkLzD9Wy38NYLRzSHPdhsXYJ5ks5r8czmgaJpZM4NisAn
.

authors: scrod seongjaelee

repo: seongjaelee/nvatom


text:
[Feature]: Add --set-on flag

Describe the feature you want to add
Add a --set-on flag to set the timer until a specific time.
mytimer --hour=15 --minute=30 --set-on

This will run timer until 15:30 from now
Describe your proposed solution
No response
Describe alternatives you've considered, if relevant
No response
Additional context
No response

@sadrasabouri Are you interested in addressing this issue?

@sadrasabouri Are you interested in addressing this issue?

Yes I am. I will self-assign it to myself. Will talk about the timeline for adding this feature in our weekly.

authors: sadrasabouri sepandhaghighi

repo: sepandhaghighi/mytimer


text:
🛑 GAMS - gams.dh.uni-passau.de is down

In f0acab8, GAMS - gams.dh.uni-passau.de (https://gams.dh.uni-passau.de/) was down:

HTTP code: 404
Response time: 416 ms

Resolved: GAMS - gams.dh.uni-passau.de is back up in 5a699d4.

repo: sepastian/status


text:
I would like the Create DataChannel functionality.

I would like to create and connect a DataChannel from the ESP32.

The esp32 example in libpeer already supports this feature

Thank you.
This example supports peer_connection_ondatachannel though,
I want peer_connection_create_datachannel, not peer_connection_ondatachannel.

Hi @gtk2k I am implementing this. Hopefully available tomorrow!

@Sean-Der
Thank you !!

@Sean-Der Thank you for your time.I will test it.

authors: GOROman Sean-Der gtk2k sepfy

repo: sepfy/libpeer


text:
Attempting free on address which was not malloc()-ed

Executing the following code:
// Open file database and setup a context c
rliteCommand(c, "SET a b");
rliteCommand(c, "DEL a"); // << removing this DEL and it works
rliteCommand(c, "SET a b");

Crashes with ASAN output:
=================================================================
==18629==ERROR: AddressSanitizer: attempting free on address which was not malloc()-ed: 0x60200000e090 in thread T0
    #0 0x4c9860 in __interceptor_cfree.localalias.0 (/home/mannol/Documents/Programming/Closenger/Debug-Desktop/Closenger+0x4c9860)
    #1 0x751894 in rl_btree_node_destroy /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/page_btree.c:125
    #2 0x729e8c in rl_write /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/rlite_internal.c:807
    #3 0x759c78 in rl_long_set /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/page_long.c:37
    #4 0x72a0e1 in rl_delete /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/rlite_internal.c:859
    #5 0x753026 in rl_btree_add_element /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/page_btree.c:432
    #6 0x70dd6f in rl_key_set /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/page_key.c:75
    #7 0x7205b7 in rl_set /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/type_string.c:50
    #8 0x7022ba in setGenericCommand /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/hirlite.c:2491
    #9 0x702620 in setCommand /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/hirlite.c:2534
    #10 0x6fa5d5 in rliteAppendCommandClient /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/hirlite.c:1086
    #11 0x6fa78e in rlitevAppendCommand /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/hirlite.c:1119
    #12 0x6fa961 in rlitevCommand /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/hirlite.c:1150
    #13 0x6faa3d in rliteCommand /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/hirlite.c:1159
    #14 0x4fda3d in main /home/mannol/Documents/Programming/Closenger/Debug-Desktop/../main.cpp:69:5

0x60200000e090 is located 0 bytes inside of 54032-byte region [0x60200000e090,0x60200001b3a0)
==18629==AddressSanitizer CHECK failed: /build/llvm-toolchain-3.8-RMgQsv/llvm-toolchain-3.8-3.8.1/projects/compiler-rt/lib/asan/asan_allocator.cc:667 "((res.trace)) != (0)" (0x0, 0x0)
    #0 0x4d2f4d in __asan::AsanCheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/home/mannol/Documents/Programming/Closenger/Debug-Desktop/Closenger+0x4d2f4d)
    #1 0x4d98e3 in __sanitizer::CheckFailed(char const*, int, char const*, unsigned long long, unsigned long long) (/home/mannol/Documents/Programming/Closenger/Debug-Desktop/Closenger+0x4d98e3)
    #2 0x42c3ac in __asan::AsanChunkView::GetAllocStack() (/home/mannol/Documents/Programming/Closenger/Debug-Desktop/Closenger+0x42c3ac)
    #3 0x4cdbb0 in __asan::DescribeHeapAddress(unsigned long, unsigned long) (/home/mannol/Documents/Programming/Closenger/Debug-Desktop/Closenger+0x4cdbb0)
    #4 0x4d0c31 in __asan::ReportFreeNotMalloced(unsigned long, __sanitizer::BufferedStackTrace*) (/home/mannol/Documents/Programming/Closenger/Debug-Desktop/Closenger+0x4d0c31)
    #5 0x42f1a5 in __asan::asan_free(void*, __sanitizer::BufferedStackTrace*, __asan::AllocType) (/home/mannol/Documents/Programming/Closenger/Debug-Desktop/Closenger+0x42f1a5)
    #6 0x4c983c in __interceptor_cfree.localalias.0 (/home/mannol/Documents/Programming/Closenger/Debug-Desktop/Closenger+0x4c983c)
    #7 0x751894 in rl_btree_node_destroy /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/page_btree.c:125
    #8 0x729e8c in rl_write /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/rlite_internal.c:807
    #9 0x759c78 in rl_long_set /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/page_long.c:37
    #10 0x72a0e1 in rl_delete /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/rlite_internal.c:859
    #11 0x753026 in rl_btree_add_element /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/page_btree.c:432
    #12 0x70dd6f in rl_key_set /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/page_key.c:75
    #13 0x7205b7 in rl_set /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/type_string.c:50
    #14 0x7022ba in setGenericCommand /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/hirlite.c:2491
    #15 0x702620 in setCommand /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/hirlite.c:2534
    #16 0x6fa5d5 in rliteAppendCommandClient /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/hirlite.c:1086
    #17 0x6fa78e in rlitevAppendCommand /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/hirlite.c:1119
    #18 0x6fa961 in rlitevCommand /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/hirlite.c:1150
    #19 0x6faa3d in rliteCommand /home/mannol/Documents/Programming/Closenger/rlite/Debug-Desktop/../src/hirlite.c:1159
    #20 0x4fda3d in main /home/mannol/Documents/Programming/Closenger/Debug-Desktop/../main.cpp:69:5

It works on :memory: database...

Fixed in 4688a34ef9bb919b0f25ad30e590ce4285db907a. Thanks for the report.

Fix confirmed; thank you!


text:
CLOUD-850 updated blueprints

@akanto

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1324/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1325/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1328/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1329/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1330/

authors: doktoric jenkins-sequenceiq

repo: sequenceiq/cloudbreak


text:
[WIP] Bundle it with Rocket-Chip

Bump chisel to use 3.6.0-RC2

old version wont work for rocket chip
3.6.0 wont compile for mill
firrtl is bumped to 1.6.0-RC2, accordingly

Introduce rocket chip related submodules

rocket-chip, hardfloat, cde, inclusive-cache

Add a config and glue file for connecting them together
Add emulator building script

Known issue:
Caused by: chisel3.package$ChiselException: Connection between left (VectorPLCT.x$1: Wire[TLBundle]) and source (VectorWrapper.memoryPorts[0]: IO[TLBundle]) failed @.d.bits.e
cho: Right Record missing field (echo).

New connector requirement from new chisel.
Cannot prove that freechips.rocketchip.tilelink.TLBundle =:= tilelink.TLBundle

There are also some issues with emulator, possibly with the nix toolchain.
In file included from <built-in>:1:
In file included from vector/out/tests/rocket/verilator/elf.dest/CMakeFiles/emulator.dir/VTestHarness.dir/VTestHarness.h:11:
In file included from /nix/store/qdk6dv5ynaj0sqdm6rmq6xgr8k5j1svz-verilator-5.006/share/verilator/include/verilated.h:51:
In file included from /nix/store/aafdki1nf49k5vxq6gx2yabiybk2bjmw-gcc-12.2.0/include/c++/12.2.0/memory:78:
In file included from /nix/store/aafdki1nf49k5vxq6gx2yabiybk2bjmw-gcc-12.2.0/include/c++/12.2.0/bits/shared_ptr_atomic.h:33:
In file included from /nix/store/aafdki1nf49k5vxq6gx2yabiybk2bjmw-gcc-12.2.0/include/c++/12.2.0/bits/atomic_base.h:41:
/nix/store/aafdki1nf49k5vxq6gx2yabiybk2bjmw-gcc-12.2.0/include/c++/12.2.0/bits/atomic_wait.h:108:22: error: use of undeclared identifier 'SYS_futex'; did you mean '_S_mutex'?
        auto __e = syscall (SYS_futex, static_cast<const void*>(__addr),
                            ^

We can get an emulator now.
FAILED: CMakeFiles/emulator.dir/CMakeFiles/emulator.dir/VTestHarness.dir/VTestHarness_Lane__DepSet_hdc0b5c3a__2.cpp.o
g++ -DVM_COVERAGE=0 -DVM_SC=0 -DVM_TRACE=1 -DVM_TRACE_FST=0 -DVM_TRACE_VCD=1 -I/run/user/2015/T/vector/dependencies/rocket-chip/src/main/resources/csrc -I/run/user/2015/T/vector/out/tests/rocket/elaborate/elaborate.dest -I/run/user/2015/T/v
ector/out/tests/rocket/verilator/elf.dest/CMakeFiles/emulator.dir/VTestHarness.dir -I/nix/store/qdk6dv5ynaj0sqdm6rmq6xgr8k5j1svz-verilator-5.006/share/verilator/include -I/nix/store/qdk6dv5ynaj0sqdm6rmq6xgr8k5j1svz-verilator-5.006/share/ver
ilator/include/vltstd -isystem /nix/store/c3vb81kdwgj86kp9ff6iz466p0fawdzv-libspike-1.1.0/include/riscv -isystem /nix/store/c3vb81kdwgj86kp9ff6iz466p0fawdzv-libspike-1.1.0/include/fesvr -isystem /nix/store/c3vb81kdwgj86kp9ff6iz466p0fawdzv-l
ibspike-1.1.0/include/softfloat -DVERILATOR -DTEST_HARNESS=VTestHarness -include VTestHarness.h -include verilator.h -include freechips.rocketchip.system.VectorLongConfig.plusArgs -O3 -DNDEBUG -std=gnu++20 -MD -MT CMakeFiles/emulator.dir/CM
akeFiles/emulator.dir/VTestHarness.dir/VTestHarness_Lane__DepSet_hdc0b5c3a__2.cpp.o -MF CMakeFiles/emulator.dir/CMakeFiles/emulator.dir/VTestHarness.dir/VTestHarness_Lane__DepSet_hdc0b5c3a__2.cpp.o.d -o CMakeFiles/emulator.dir/CMakeFiles/em
ulator.dir/VTestHarness.dir/VTestHarness_Lane__DepSet_hdc0b5c3a__2.cpp.o -c /run/user/2015/T/vector/out/tests/rocket/verilator/elf.dest/CMakeFiles/emulator.dir/VTestHarness.dir/VTestHarness_Lane__DepSet_hdc0b5c3a__2.cpp
In file included from /nix/store/aafdki1nf49k5vxq6gx2yabiybk2bjmw-gcc-12.2.0/include/c++/12.2.0/bits/atomic_base.h:41,
                 from /nix/store/aafdki1nf49k5vxq6gx2yabiybk2bjmw-gcc-12.2.0/include/c++/12.2.0/bits/shared_ptr_atomic.h:33,
                 from /nix/store/aafdki1nf49k5vxq6gx2yabiybk2bjmw-gcc-12.2.0/include/c++/12.2.0/memory:78,
                 from /nix/store/qdk6dv5ynaj0sqdm6rmq6xgr8k5j1svz-verilator-5.006/share/verilator/include/verilated.h:51,
                 from /run/user/2015/T/vector/out/tests/rocket/verilator/elf.dest/CMakeFiles/emulator.dir/VTestHarness.dir/VTestHarness.h:11,
                 from <command-line>:
/nix/store/aafdki1nf49k5vxq6gx2yabiybk2bjmw-gcc-12.2.0/include/c++/12.2.0/bits/atomic_wait.h: In function 'void std::__detail::__platform_wait(const _Tp*, __platform_wait_t)':
/nix/store/aafdki1nf49k5vxq6gx2yabiybk2bjmw-gcc-12.2.0/include/c++/12.2.0/bits/atomic_wait.h:108:29: error: 'SYS_futex' was not declared in this scope
  108 |         auto __e = syscall (SYS_futex, static_cast<const void*>(__addr),
      |                             ^~~~~~~~~

The build.sc now references two spike, as libspike wont work (using -isystem).

Already did it a long time ago.

authors: ZenithalHourlyRate sequencer

repo: sequencer/vector