text:
Bug: Default keymaps doesn't work with newer version of skim

RTFM Checklist

[X] I have searched exisiting issues / discussions
[X] I have read the Wiki including the Advanced section
[X] I have read man fzf / I am well versed in shell fzf

Operating system
Mac
Shell
zsh
Neovim version (nvim --version)
v0.10.2
Fzf version (fzf --version)
sk 0.12.0
Output of :lua print(os.getenv('FZF_DEFAULT_OPTS'))
--layout=reverse --border
Is the problem reproducible with mini.sh?

[x] My issue is reproducible with mini.sh
[x] My issue IS NOT reproducible with mini.sh
[ ] I have not tested with mini.sh (not relevant, requires LSP, Windows, etc)

Fzf-lua configuration
require('fzf-lua').setup({
      fzf_bin  = 'sk',
})

Describe the bug / steps to reproduce
With newer version of sk (0.12.0), I am getting two issues

Invalid tiebreak option

[Fzf-lua] fzf error 2: error: invalid value 'index' for '--tiebreak <TIEBREAK>'

As as work around I added below, I guess default index option needs to be changed
fzf_opts = {
   ["--tiebreak"] = "score",
},

<ctrl-g> mapping doesn't work, popup just disappears. Infact, I tried custom actions as well, they don't seem to work as well.

files = {
  actions   = {
     ["ctrl-i"] = { actions.toggle_ignore },
     ["ctrl-g"] = { actions.toggle_hidden },
  }
}

Skim has recently moved to its own org and restated development in high pace, there’s a new version almost every day, v12.0 added the reload action which I plan to add support for (seamless refresh of the actions).
I’ll give it some more time for the development blitz to settle down and make the necessary adjustments.

That sounds fair, thanks 👍🏼

I did some testing, all the issues mentioned here are upstream bugs.

Invalid tiebreak option

Already solved in https://github.com/skim-rs/skim/pull/609 (works with v0.13).

 mapping doesn't work, popup just disappears. Infact, I tried custom actions as well, they don't seem to work as well.

Newly introduced issue, still bugged with 0.13, opened an issue upstream:  https://github.com/skim-rs/skim/issues/622

@ibhagwan thanks for following this up. I agree with what you said earlier, to wait till initial development spike cools off

Both issues fixed upstream on HEAD, closing.

repo: ibhagwan/fzf-lua


text:
fadeOnAsynchronouslyDisplay label还是会闪动

_titleLabel.displaysAsynchronously = YES;
_titleLabel.ignoreCommonProperties = YES;
_titleLabel.fadeOnAsynchronouslyDisplay = NO;
_titleLabel.fadeOnHighlight = NO;
页面刷新时，label还是会闪动一下。

不闪，但是显示可能会有延迟：
clearContentsBeforeAsynchronouslyDisplay = YES

您好，作者，在下拉刷新时，或者reloaddata时，这样设置，yylabel会闪烁一下。能帮我指点下不…我也看了你写的范例，按照那样设置，确实会闪烁。

怎样才能解决刷新不闪，显示延迟问题，二者只能取一吗

source: gharchive/issue

authors: githubzxq ibireme ljw215 woodjobber

repo: ibireme/YYKit

license: mit

license_type: permissive

license_source: bigquery


text:
When I set an attribute to its default value explicitly, I rather would not see a warning

Is your feature request related to a problem? Please describe.
See the following picture.

I want to be sure that property createFolders of my DirectoryListener is false. I do not want to depend on the default value, because I fear it may change in a new version of the Frank!Framework. Because I set this attribute on purpose, I do not want to see a warning that I set an attribute equal to its default value.
Describe the solution you'd like
I would like not to have a warning when I set an attribute to its default value.
Describe alternatives you've considered
We may introduce a tag or attribute to suppress warnings, like the Java programming language has syntax to suppress warnings.
Additional context
I came up with this issue when working on the Frank!Manual. I was using the Frank!Runner to start the Frank!Framework. The issue applies to Frank!Framework version 7.6-20200420.180231.

Verified. I documented property warnings.suppress.defaultvalue in the Frank!Manual.

repo: ibissource/iaf


text:
Bug fix revert

Want to merge the change to MAIN

Allow to merge

source: gharchive/pull-request

license_source: github-api


text:
ModuleNotFoundError: No module named 'confluent_kafka'

How can i fix the issue?
When i run python3 app.py , I got the error:
ModuleNotFoundError: No module named 'confluent_kafka'

This indicates you have not installed the confluent_kafka library in your python3 environment.
You may need to adapt the instructions a bit for your environment and instead run pip3 install -r requirements.txt to install the dependencies.

It works.
Thank you

repo: ibm-messaging/event-streams-samples


text:
IOS9 support

There are 2 issues which breaks JS interaction in vue app when using scroll-spy on mobile device with IOS9
I managed to trace these issues down to IOS 9 and this package. IOS10+ is not affected.
Related to: https://github.com/webpack/webpack/issues/3928

try v2.3.1

Issue still persists using v.2.3.1

The solution posted in https://github.com/ibufu/vue2-scrollspy/issues/27#issuecomment-440257925 might solve this as well.

@Anima-t3d thanks

license: MIT


text:
🛑 Icarephone is down

In 3a15834, Icarephone (https://www.icarephone.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Icarephone is back up in 6b400d7.

repo: icarephone/upptime


text:
🛑 Git is down

In 5410be0, Git (https://git.icarephone.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Git is back up in 472cc38.


text:
🛑 Secret Site is down

In 8f2a71b, Secret Site ($SECRET_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Secret Site is back up in 526c05a.


text:
🛑 Git is down

In 6c4d431, Git (https://git.icarephone.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Git is back up in ed714b1.


text:
🛑 Secret Site is down

In 17c08af, Secret Site ($SECRET_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Secret Site is back up in dac7564.


text:
Improve formatting of wrapped and aligned statements.

These changes build on the previous changes for improving the parsing support.

Align multiline module and function parameters.
Wrap long module and function call parameter lists at a parameter.
Fix customizer highlighting for numbers.
Prevent customizer comments from being wrapped.
Update the test result files.
Update gradle build settings.
Specify ActionUpdateThread type to remove deprecation warning.
Check for a null value from the virtual file system.

Changes were merged into the master branch.

repo: icaven/idea-openscad


text:
npm 包中 import 语句不加 .js 后缀编译不报错

比如 @ice/runtime：
// 错误写法
import xxx from './utils/react-router-dom';
// 正确写法
import xxx from './utils/react-router-dom.js';

使用了错误写法后 watch 不会报错，但在项目里构建时就会报错，期望是组件编译时报错。

需要在 tsconfig.json 中开启 compilerOptions.moduleResolution = 'node12'，并且保证 typescript 的版本是 next (估计是未来发的 4.7.x 的版本)

按标准写法增加 .js 后缀，由包编译工具决定是否需要自动补全

authors: ClarkXia imsobear luhc228

repo: ice-lab/ice-next


text:
[WIP] Build Beta Pack

发布 packages ，更新包的版本号及其依赖的其他 packages 的版本号
extensions 更新 dependencies 中 packages 的版本号

Codecov Report

Merging #70 into release/0.1.0 will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release/0.1.0      #70   +/-   ##
==============================================
  Coverage          78.88%   78.88%
==============================================
  Files                 26       26
  Lines                966      966
  Branches             198      198
==============================================
  Hits                 762      762
  Misses               200      200
  Partials               4        4

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 fc5b35f...2d8b9a9. Read the comment docs.

authors: alvinhui codecov-commenter

repo: ice-lab/iceworks


text:
Deprecated packages & other warnings in package.json

Running yarn/npm install in the git checkout produces the following warnings:
warning jade@1.11.0: Jade has been renamed to pug, please install the latest version of pug instead of jade
warning mocha > jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
warning jade > transformers@2.1.0: Deprecated, use jstransformer
warning mocha > glob > minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
warning mocha > to-iso-string@0.0.2: to-iso-string has been deprecated, use @segment/to-iso-string instead.
warning gitbook-cli > npm > lodash.isarray@4.0.0: This package is deprecated. Use Array.isArray.
warning gitbook-cli > npm > node-gyp > minimatch@1.0.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
warning coveralls > request > node-uuid@1.4.7: use uuid module instead
warning gitbook-cli > npm > request > tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130

I don't have this message when I do npm install on the project or when I do npm install vue-form-generator on another project.
@dflock is this still an issue ? If yes, can you give more context for these warning ?

It's come if you run yarn instead of npm install.

#124 dc08fbf185fe13bb9a4cefe4bddb7bc8e0d064b8 4b2e1f73ee36c2c7a4d59e2c005118fdd3272e07

authors: dflock icebob lionel-bijaoui

repo: icebob/vue-form-generator


text:
profile page with device availability

Just not sure about the string filter pipe, since it was filtering wiki pages so I created another one with almost the same code.

Oh, and please rebase :)

I've fixed the git history.

authors: alasmaleki chaoran-chen

repo: icebreaker-science/frontend


text:
add source but not work

add https://ftp.sotirov-bg.net/pub/contrib/slackware/packages/slackware64-15.0/ slackpack to sources.list
run un-get update, I can see /tmp/un-get/filelist-slackpack file content is ok
run un-get search ncdu, return Found no packages matching your search 'ncdu'.

Thank you for the report, will look into this ASAP and report back.

@hcwhan I've now took a closer look at this, this is actually caused because the FILELIST.TXT doesn't follow the Slackware default (date and time is formatted wrong).
I will look into it if I can account for this in un-get

@ich777 ok

Please update the plugin to v0.18 or 2022.10.27 respectively to fix the issue with this repository.
If you have any further issues please feel free to re-open this issue again or open up a new issue.

2022.10.27 is ok, tks very much


text:
an idea for region-based memory management

https://github.com/ichiban/prolog/issues/304

This approach requires every term to be a reference to heap (TermPool) but we want chars to be direct values.

repo: ichiban/prolog


text:
Two small issues

Thank you for this amazing project. So much to learn from.
a) BashTube/src/rest/http/http_orchestrator.sh needs to be chmod +x
b) Getting this error when trying to upload a video using Firefox...
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://127.0.0.1:8080/upload. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 201.

Hi, I'm really happy to hear that!
Now, for the issues:

A "Setting up" section has been added to the README, as the project is simple enough that a installation script is not necessary.
I could not repro your issue on the latest Firefox build, but have added the CORS header described by your issue. If the problem persists, let me know, or feel free to submit a PR.

Not so fast :-)
It seems I can now upload a small mp4, it's just that without any feedback I accidentally uploaded some more copies. However, when trying to refresh the page, I get the attached similar error.
Another docu point is that it took me quite a few attempts to figure out which script to run, and that it's necessary to cd into src/app first before running a bash main.sh.

Hi again! :)

As you pointed out, I added a new part to the "Setting up" section for running the actual app.
Also added a global preflight requests handler that should theoretically handle your error case, although considering how complex/varied browser behavior is, it may very well not be a end-all solution - after all, this is really just a simple Bash app.

Getting further along but getting the below. I was also missing the "bc" command, so maybe a setup script might be a good idea to check that all binary dependencies exist, and a chmod along the way.
[05/10/24 22:10:27][DEBUG][HTTP]: GET / HTTP/1.1 200
[05/10/24 22:10:27][DEBUG][HTTP]: GET /static/bashtube_logo.png/ HTTP/1.1 200
[05/10/24 22:10:27][DEBUG][HTTP]: GET /storage/user_icon.jpg/ HTTP/1.1 200
[05/10/24 22:11:23][DEBUG][HTTP]: POST /upload/ HTTP/1.1 201
[05/10/24 22:11:39][DEBUG][HTTP]: POST /videos/ HTTP/1.1 400
[05/10/24 22:11:52][DEBUG][HTTP]: GET / HTTP/1.1 200
[05/10/24 22:11:52][DEBUG][HTTP]: GET /static/bashtube_logo.png/ HTTP/1.1 200
[05/10/24 22:11:52][DEBUG][HTTP]: GET /storage/0/ HTTP/1.1 404
[05/10/24 22:11:52][DEBUG][HTTP]: GET /storage/user_icon.jpg/ HTTP/1.1 200
[05/10/24 22:11:52][DEBUG][HTTP]: GET /storage/video_upload_1ca7b7e9-06d5-4487-9d6b-6c39dffac767.mp4/ HTTP/1.1 200
Error: in prepare, no such column: user_icon.jpg
  SELECT * FROM videos WHERE id = user_icon.jpg;
                    error here ---^
[05/10/24 22:12:08][DEBUG][HTTP]: GET /videos/user_icon.jpg/ HTTP/1.1 404

The bc command is most definitely a sub-requirement to the 3 major dependencies that I will be adding to the README (thanks for pointing that out).
From the error log it seems you are trying to access /videos/user_icon.jpg/ which is correctly returning 404 - the error doesn't interrupt the flow of the app. Is something related to that the problem? You may want to clear your database if some entries are malformatted (which may be possible if your first attempts at uploading videos were only partial).

authors: icitry markc

repo: icitry/BashTube


text:
[bug] next event not loading after an empty event

https://news.icpc.global/gallery/?album=2017&event=New+RCD+Workshop
I guess here even if I scroll down I don't see any further events, even though they exist

@lperovskaya should be fixed now, please close once confirmed.
http://icpc.io/gallery/?album=2017&event=RCD+Symposium

works now
https://news.icpc.global/galleryNAC/?album=RC+2021-2022&event=Photo+Tour

authors: azat-ismagilov lperovskaya

repo: icpc/gallery


text:
21 ss log

Added functionality to write the solar log information onto two CSV files,  using cronjobs, MPPT_LOG_Hr takes care of writing to the hourly log, MPPT_LOG_HD, takes care of the 12hr log. The ReadMe has also been updated to include a setup for these, as well as a setup for the cronjob that takes care of the 1am reboot. Closes issue 21

This PR has been replaced by PR #43 correct?  If yes, I will close it unless anyone would like to keep it open.

authors: EliasMartinezJ icr-ctl

repo: icr-ctl/dencam


text:
🛑 Icrop Website is down

In f21de63, Icrop Website (https://icrop.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Icrop Website is back up in 724f595.

repo: icroptec/uptime-monitor


text:
In ZipOutputStream.PutNextEntry, account for AES overhead when calculating compressed entry size

Found when looking at #454:
The code at:
https://github.com/icsharpcode/SharpZipLib/blob/f36ca373206340a25b1d3bb226acc7b679128a7c/src/ICSharpCode.SharpZipLib/Zip/ZipOutputStream.cs#L330
for writing entries when the header information is known tries to take account of the crypto header overhead, but only does so for ZipCrypto encrypted entries - it uses the wrong values for AES entries.
Also, the code for building the Zip64 extra data at:
https://github.com/icsharpcode/SharpZipLib/blob/f36ca373206340a25b1d3bb226acc7b679128a7c/src/ICSharpCode.SharpZipLib/Zip/ZipOutputStream.cs#L375
doesn't take account of that overhead at all, which seems to also produce incorrect archives.
The
// TODO: Refactor header writing.  Its done in several places.

becomes a bit more true with the simple change, as it duplicates a bit more logic that could perhaps do with being shared.
PR adds a set of test cases for different encryption/compression methds, with and without zip64, but only for 0 byte entries - something with populated entries whose size and crc are known upfront might be useful seperately.
I certify that I own, and have sufficient rights to contribute, all source code and related material intended to be compiled or integrated with the source code for the SharpZipLib open source product (the "Contribution"). My Contribution is licensed under the MIT License.

Updated to move some of the duplicated overhead size calculation logic to an 'EncryptionOverheadSize' property on ZipEntry, and also changed ZipEntry.LocalHeaderRequiresZip64 to use that instead of always using the ZipCrypto constant.

A small observation about the length calculation logic ZipOutputStream.CloseEntry that I noticed when looking at this:
When calculating the compressed size of the entry, it does
if (curEntry.IsCrypted)
{
	if (curEntry.AESKeySize > 0)
	{
		curEntry.CompressedSize += curEntry.AESOverheadSize;
	}
	else
	{
		curEntry.CompressedSize += ZipConstants.CryptoHeaderSize;
	}
}

but then after that it does
if (curEntry.LocalHeaderRequiresZip64)

and inside LocalHeaderRequiresZip64, it does
if ((versionToExtract == 0) && IsCrypted)
{
    trueCompressedSize += ZipConstants.CryptoHeaderSize;
}

So it looks like it counts the crypto overhead twice.
Not sure if there's any scope for an edge case there where that makes it use the wrong values if those few exctra bytes push it over the non-64 length limit?

ok, too much copy/pasting, will have a look over the weekend.

updated

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

Complexity decreasing per file
==============================
+ src/ICSharpCode.SharpZipLib/Zip/ZipOutputStream.cs  -1

Clones removed
==============
+ src/ICSharpCode.SharpZipLib/Zip/ZipOutputStream.cs  -1

See the complete overview on Codacy

authors: Numpsy piksel

repo: icsharpcode/SharpZipLib


text:
Create a getDefaultTerm() function for termData

Currently, the expression termData[defaultTerm] is used to access the default term, which is not the most concise.
Create a function getDefaultTerm() in termData which returns that expression, and make sure all usages of the expression are replaced with this function call. Optionally, also make sure defaultTerm is no longer accessible from outside of termData.

I'll claim this one.

authors: ecxyzzy felixweiguangwu

repo: icssc/AntAlmanac


text:
CREO2URDF – MVP-3

We will focus exporting the entire ergocub

MVP3 reached 🎸

https://github.com/icub-tech-iit/creo2urdf/pull/39#issuecomment-1643652447


text:
Stranky so spatnou vazbou (MHSR / Ness)

Je spätná väzba povinná pre každú službu , t.j. kde ju pre službu nemáme, tak ju
musíme doplniť ?

Áno, je.


text:
fix numpy issue with dtype

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
close #85
What are the significant changes in functionality due to this change request?

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual.
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Regression tests have to complete successfully.
[ ] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test.
[ ] 6. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.

@joshua-cogliati-inl Here is the pull request to fix the issue with the bumpy 1.24.


text:
🛑 SocialGenius.net Store is down

In 1f74407, SocialGenius.net Store (https://store.socialgenius.net) was down:

HTTP code: 526
Response time: 265 ms

Resolved: SocialGenius.net Store is back up in 74cf442.

repo: idammi/status


text:
method does not override or implement a method from a supertype

node_modules/react-native-barcodescanner/android/src/main/java/com/eguma/barcodescanner/BarcodeScannerPackage.java:20: error: method does not override or implement a method from a supertype
@Override

I am also having same issue

I am also having the same issue. Any help on this please !!

authors: Anujmoglix gitpayal srivatsav


text:
关于界面的一点提议

首先表示非常感谢，完美解决了一群南大人的痛点（
然后。。。稍微有一点点提议

菜单按钮的话做成三条杠大概也许可能用的比较多（好像在左边的比较多？）
可以试试直接一次导入之前所有课表
弹出窗口的字距和阴影没准可以适配一下material design 比如下面那个

（比如阴影由近及远和英文字母间距）

最后再次感谢

啊还有一点 可能查成绩需求也蛮大的 可以考虑加一个

CourseActivity用的是popupview，OP想要的是dialog

authors: Dothion doowzs

repo: idealclover/NJU-Class-Shedule-Android


text:
Stop using functions ToISOFormat/GetISODateTime

Consider GetStringFromDateTime

closed via commit 614266f78b7b5b64ff73a69fcdcdb0f0ebfa86f3

repo: ideaportriga/siebel-nexus-bridge


text:
Improve Error reporting to firebase

@pmigueld or @danicaerediano can we add the react-native plugin as well to get more details? https://rnfirebase.io/crashlytics/usage
@rjmangubat23 can we move the google-services.json file to a secret in the build?

@pmigueld @danicaerediano @rjmangubat23 what's the status of this?

@kneckinator not sure on the react-native plugin but on move the google-services.json file to a secret in the build, this has already been done via this PR https://github.com/idpass/inji/pull/105 with the help of @typelogic.

@jeremi should we still chase down the RN plugin for Firebase?

I am moving this to 0.4.0

authors: jeremi kneckinator rjmangubat23

repo: idpass/inji


text:
Problems with markdown-style strong text

A few experiments:

**p a**: fails (Uncaught TypeError: children.map is not a function)
**f a**: succeeds
**pa**: succeeds
**a**: rendered as bulleted list with string content *a**
Test **p a**: fails (Uncaught TypeError: children.map is not a function)
Test **f a**: succeeds
Test **pa**: succeeds
Test **a**: suceeds (note starting the line with not * lets it know it's not a list)

In particular, the problem with the letter p is a bit surprising. I haven't tried all letters exhaustively yet. 😄

This should be fixed in v1.3.1 via https://github.com/idyll-lang/idyll-compiler/commit/0e62942db7e398f0949f4cc1f7dda494c5247dff

authors: mathisonian rreusser

repo: idyll-lang/idyll-compiler


text:
Transaction expiration

Hi,
I'm using this repository for Tron transaction. I found that expiration time for each transaction is set to 60 seconds in Java source codes. How can I increase expiration time using tron-api-python?
If it's not possible in python, how can I solve it anyway?
output :
[{'code': 'TRANSACTION_EXPIRATION_ERROR', 'message': 'transaction expired'}]

I did what has been explained in below link:
[(https://github.com/tronprotocol/java-tron/issues/2883)]

repo: iexbase/tron-api-python


text:
"InternalServerError: is at commit  but expected commit <N - 1>" when uploading cover image

Getting this error when trying to upload a cover image to a post.
InternalServerError: is at 9222de0514c40164f1fc209ba563eb326b1c6826 but expected 18990c738b7fddfacc3e1c0042d242a97837f3ca

I think the problem might be caused my Ghost trying to upload two images at the same time (original + optimized), leading to some sort of mismatch in the Git hash.

This issue may be related to #18.

Possible solution: try to fetch the latest commit before attempting to create a new file.

Closing because #18 already exists.

Closed by #34.

repo: ifvictr/ghost-storage-github


text:
Unaligned memory access causing hard fault

I'm working with the wifi_station sample and a PSOC6 board to connect to the Golioth platform but have encountered a hard fault.
uart:~$ WLAN MAC Address : 74:7A:90:D4:5F:04
WLAN Firmware    : wl0: Jul 18 2021 19:15:39 version 7.45.98.120 (56df937 CY) FWID 01-69db62cf
WLAN CLM         : API: 12.2 Data: 9.10.39 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2021-07-18 19:03:20
WHD VERSION      : v2.2.0-dirty : v2.2.0 : GCC 10.3 : 2021-12-14 13:57:54 +0000
*** Booting Zephyr OS build 5fb80e74f153  ***

--------------------------------------------------------------------------------------------------
  #                  SSID                  RSSI   Channel       MAC Address              Security
----------------------------------------------------------------------------------------------------

[00:00:00.638,000] <wrn> net_sock_tls: No entropy device on the system, TLS communication is insecure!
[00:00:00.638,000] <inf> golioth_system: Initializing
[00:00:00.665,000] <err> os: ***** USAGE FAULT *****
[00:00:00.665,000] <err> os:   Unaligned memory access
[00:00:00.665,000] <err> os: r0/a1:  0x08033ce7  r1/a2:  0x000000ff  r2/a3:  0xffffffff
[00:00:00.665,000] <err> os: r3/a4:  0x08033ced r12/ip:  0x10015f15 r14/lr:  0x1001971d
[00:00:00.665,000] <err> os:  xpsr:  0x61000000
[00:00:00.665,000] <err> os: Faulting instruction address (r15/pc): 0x10019722
[00:00:00.666,000] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[00:00:00.666,000] <err> os: Current thread: 0x8003f48 (main)
[00:00:00.765,000] <err> os: Halting system

To Reproduce
Steps to reproduce the behavior:

Add Golioth module to west.yml under projects
    - name: golioth
    path: modules/lib/golioth
    revision: 3086987ed8b4e80dd16312a418dcd1972ef00f5f
    url: https://github.com/golioth/zephyr-sdk.git
    - name: qcbor
    revision: 17b5607b8c49b835d22dec3effa97b25c89267b3
    url: https://github.com/golioth/QCBOR.git
    path: modules/lib/qcbor

west update

Add to the bottom of prj.con in wifi_station sample
    CONFIG_GOLIOTH=y
    CONFIG_GOLIOTH_SYSTEM_CLIENT=y

Build and flash:
west build -b cy8cproto_062_4343w samples/boards/infineon/wifi_station
west flash

Unaligned memory access fault happens when scanning for WiFi networks

Expected behavior
A list of wifi APs should be displayed
Troubleshooting
I asked Marcin on our firmware team about it and he thinks he's found some clue to the cause:
.noinit."WEST_TOPDIR/zephyr/drivers/wifi/infineon_wifi/cyw43xxx_wifi_drv.c".1
                0x000000000802794f     0x4b00 zephyr/drivers/wifi/libdrivers__wifi.a(cyw43xxx_wifi_drv.c.obj)

This is the memory pool that they allocate from. You can notice that it is starting from 0x000000000802794f, which is not aligned to 4 bytes (0xf at the end of address, means 15, which does not divide by 4). Then after allocation they try to reference uint32_t variables. This obviously results in Unaligned memory access that you are seeing.
The net_buf pool defined in:

NET_BUF_POOL_DEFINE(cyw43xxx_pool, 12, 1600, 0, NULL);

is not guaranteed to be 4 bytes aligned, but they seem to assume so.

@szczys, thanks for the report. Can you let me know what commit you are using as a base?
Thanks,
Ian

Hi Ian, sorry I didn't include this before:
zephyr/samples/boards/infineon/wifi_station $ git rev-parse HEAD
5fb80e74f15336fb256bea81f9e4802558de0188

hi @szczys, we fixed this in https://github.com/ifyall/zephyr/commit/d8ef5443f1a02b1f7e20eb07e6cdb298d453ebda
also i push PR to Zephyr to fix NET_BUF_POOL_DEFINE https://github.com/zephyrproject-rtos/zephyr/pull/48713
in future update i will revert NET_BUF_POOL_DEFINE (remove NET_BUF_POOL_FIXED_DEFINE_ALIGN  ) in cyw43xxx driver once pull/48713 is merge.

authors: ifyall npal-cy szczys

repo: ifyall/zephyr


text:
🛑 Comparador Prestamos is down

In bb7447b, Comparador Prestamos (https://www.acierto.com/prestamos/comparador/) was down:

HTTP code: 500
Response time: 10258 ms

Resolved: Comparador Prestamos is back up in 356cc0c.

repo: igaataciertocom/upptime


text:
2 ➡ 3 (part 1)

Broken off #268 because that is having to many failures

Ignoring actions now because #269 is not being forward-ported yet.

repo: ignitionrobotics/ign-gazebo


text:
How to download data for a year

How to download data for a year

I'm not the repository owner, but I have a shellscript like this, which can be modified easily (you should probably parallelize it for performance if you're going to download the entire year):
#!/usr/bin/env bash

set -o errexit
set -o nounset

cd "$(dirname "$0")"

DATE_FORMAT="+%Y-%m-%d"

START_DATE=2011-02-13
END_DATE="$(date --date='1 day ago' "$DATE_FORMAT")"

curr_date=$(date --date="$START_DATE" "$DATE_FORMAT")
while [[ "$curr_date" < "$END_DATE" ]]; do
    for hour in $(seq 0 23); do
        gh_date="$curr_date-$hour"

        target_file=$gh_date.json.gz

        echo -n "$gh_date: "
        if ! [[ -f "$target_file" ]]; then
          echo "Downloading."

          tmpfile="$(mktemp -p tmp)"
          curl -# --fail \
            "http://data.gharchive.org/$target_file" \
            --output "$tmpfile" \
            && rc=$? || rc=$?
          if [[ $rc -eq 0 ]]; then
            mv "$tmpfile" "$target_file"
	 else
            echo "Failed!"
          fi
        else
          echo "Exists, skipped."
        fi

 done

    curr_date=$(date --date="$curr_date + 1 days" "$DATE_FORMAT")
done

thanks!

authors: JeffreyBool utdemir


text:
no effect after changing resources/genomes.json

Hi,
Sorry for the naive question. I really want to get this work but have not been successful after try many times.
I was able to set up igv-webapp.
By running
npm start I can get it running. However I have two issues:

except hg19 (the default?), everything else will give error:

I cannot change any of the genome list (or the track lists):
I modified my resources/genomes.json to by deleting all other genomes:

but the genome drop down menu will not change.
similarly i modified resources/tracks/trackRegistry.json, and will not have effects.
Thank you very much,
Shuoguo

@jrobinso , I still have issue, but thought I published at wrong repo...tried to follow a resolved issues but still having trouble:
https://github.com/igvteam/igv-webapp/issues/103
thanks for the quick response.

Are you restarting your server (http-server) after editing the json?

If you are running from the dist directory you need to rebuild after making any changes with

npm run build

From the root directory.   Then restart.

yes. i re-run npm run build npm start every time.
feel like i should just update resource/genome.json and resource/tracks/trackRegsitry.json, followed by  npm run build and  npm start
I see the genome drop down menu changed, but not the tracks drop down menu. will test a bit more

You can just edit the files in dist/resources, instead of resources, and avoid the build step.  I just updated the readme to reflect that.

Does this looked good?
$ vi igvwebConfig.js

$ vi dist/resources/genomes.json

$ vi dist/resources/tracks/trackRegistry.json

Thanks,

I think those paths should be relative to the webpage referencing them, correct?  In that case you should not have "dist/" in them.   What are you seeing in the javascript console, or network tab?

authors: iiiir jrobinso

repo: igvteam/igv-webapp


text:
Create an Python interface

Simply create a Python interface similar to the C# interface.

Looks like pybind11 is a more controlled way of doing the interface. Compared to SWIG.

I have done a pybind11 python interface in the DBC library as a pybind11 test run. A python interface for the MDF library will can now be done fast.
So far, nobody have required a Python interface for the MDF library, why I put this enhancement into low priority. If anyone needs an interface, please let me know.

Hello,
Could you please guide me to the folder where to find this Python pybind11 interface? Is it possible to load the MDF4Reader.dll/MDF4Writer.dll as COM objects?
Thanks for the help.

The python interface is done if anyone wants it. It should be strait forward but it's still some (2-3) weeks work with the pybind11 interface. I did a training mission  on the DBC library as it is smaller than the MDF library. Do you want me to do the Python interface ?
There is no COM interface for the MDF library but there is a .NET assembly available (mdflibrary.dll). It is build by using the Visual Studio IDE (vcproj/sln). This interface is rarely used and manually maintained. The other libraries use CMAKE. In theory, it is possible to create a COM interface but it's a lot of work to support this type of legacy interface. Excel do still use VB script (COM). Please let me know if a COM interface is a requirement.

Hello,
If it’s not too much trouble and if it’s already developed, I would appreciate a Python interface.
I don’t require a COM interface. I’m curious about the location of mdflibrary.dll. If I can load this library in Python using the .dll file, it might be sufficient for me to start building something. If not, C# might be a more convenient choice. Thank you.

OK, I will finalize the Python interface by using pybind11. There is an older 2.1 release in GitHub. The executable is an installation kit that includes the .NET assembly. According to Google it should work to load an assembly into Python but this might be in the twilight zone.

authors: CarlesAB ihedvall

repo: ihedvall/mdflib


text:
请问微信通知支持pushplus吗？

https://www.pushplus.plus/
微信推送接口链接 =
这里应该怎么填写

http://www.pushplus.plus/send/{你的token}
例如：http://www.pushplus.plus/send/eb5a13c985c2435b91f264a3745c7dd9

repo: ihmily/DouyinLiveRecorder


text:
Login false

Pls help.I can not log in

All i can say here is to double check the password.

Did you replace the accounts.py file in scripts with the one in resources?

Did you replace the accounts.py file in scripts with the one in resources?

i did it
password is oke
sorry my english bad

I don't know what is wrong then. If you replaced the accounts.py file in /scripts with the one in /resources, then all I can tell you is to manually log in and then start the bot.

I change is here and it work^^
thanks for care

authors: iholston thuypoi

repo: iholston/lol-bot


text:
cleanup of Westeros tutorials

Description of this PR
This PR cleans up the Westeros suite of tutorials, in particular:

remove legacy elements of summer school presentation, use more generic header and summary instead
replace unit % by - where the values are absolute (0.05, not 5%)
consistency of section headers
miscellaneous rewriting

The PR also updates the reference to the MESSAGEix South Africa publication in the user guidelines.

Hey @danielhuppmann. Content looks good. I have an open question on the python2/3 stuff.

@thanks Gidden, implemented first suggested, commented on why not to worry about second suggestion. Should be good to go once the unit tests pass.

looks great, thanks @danielhuppmann

authors: danielhuppmann gidden


text:
📄 Add CODE_OF_CONDUCT.md file

📄 Add CODE_OF_CONDUCT.md file
Add a CODE_OF_CONDUCT.md file to the root of the project.

Hello, could you assign this issue to me ?

Hello @PrerakMathur20 .
I would like to work on this issue. Could you please assign it to me.

@Nincompup Assigned to you!
@KanishkDadhich Since the Issues are FCFS, I can't assign you this one. Feel free to look around for more issues you're comfortable with.

authors: KanishkDadhich Nincompup PrerakMathur20

repo: iiitl/geet-hub-editor


text:
Added  gcd, insertion sort, linear search and sieve of Eratosthenes [Haskell]

By submitting this pull request I confirm I've read and complied with the below declarations.

[X] I have read the Contribution guidelines and I am confident that my PR reflects them.
[X] I have followed the coding guidelines for this project.
[X] My code follows the skeleton code structure.
[X] This pull request has a descriptive title. For example, Added {Algorithm/DS name} [{Language}], not Update README.md or Added new code.
[X] This pull request will be closed if I fail to update it even once in a continuous timespan of 7 days.

@tgdn Hello thanks for contributing here, but please first read the CONTRIBUTIING.md to know how to contribute to this repo.
Please read and follow those guidelines :smiley:

@tgdn Thanks for the PR. Excited to see new contributors. 😀
Btw, as you can see, Haskell is not a supported language for this repository right now. But we are considering this at our Gitter channel. We will let you know what we come up with.

@tgdn: The code looks good. We are waiting for a bear for Haskell in #223. We'll be able to merge this only after that.
In the meantime, I recommend you to open issues for each of the algorithms, break this into 4 PRs and update the respective README file.

@tgdn: Please make the requested changes. This PR will be closed upon 7 days of inactivity.

@tgdn: Please take a look at Travis failure.

@aviaryan sir this may be closed due to inactivity.

@tgdn Since this PR is not assigned to any issue, please open this PR when you are willing to work on it later.

authors: Monal5031 aviaryan singhpratyush tgdn

repo: iiitv/algos


text:
上传一直出错，且上传速度很慢 可否支持多线程上传

V3.5.4(旧版也出错)，错误如下：
[1] 秒传失败, 开始上传文件...
[1] ↑ 1.20GB/17.76GB 5.61MB/s in 3m29.039s ............panic: runtime error: invalid memory address or nilpointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x82fa25]
goroutine 55 [running]:
github.com/iikira/BaiduPCS-Go/internal/pcsfunctions/pcsupload.(*PCSUpload).TmpFile.func1.1(0xc4203a85a0, 0xc4203e8550, 0x4f, 0xc4200f9cc0, 0xc42000c388, 0xc420373290, 0xc42002af00, 0xc42000c380)
/Users/apple/go/src/github.com/iikira/BaiduPCS-Go/internal/pcsfunctions/pcsupload/upload.go:57 +0xe5
created by github.com/iikira/BaiduPCS-Go/internal/pcsfunctions/pcsupload.(*PCSUpload).TmpFile.func1
/Users/apple/go/src/github.com/iikira/BaiduPCS-Go/internal/pcsfunctions/pcsupload/upload.go:52 +0x1db

因为经常用到上传的功能，恳请解决一下

上传还是在网页里面最快，几M每秒，这个倒不是痛点需求，百度自己做的上传就是最快速度了

@effzmt 但是上传一直出错没办法用，baidupcs分片多线程上传开多线程可以到100MB/s，但是作者不维护了
需求可能不太一样 因为我只用上传功能

额。。只用上传的话，倒不如用百度自己的客户端了，基本没限速的

repo: iikira/BaiduPCS-Go


text:
Existing secret "notion-token" will be used

Hello there,
I tried to deploy one time. But I probably entered the wrong token and id. I delete project and try again.
But this time I can't change my token and index-id on vercel

Does anyone have a same issue?

Hi, to change theses values you currently need to use the Vercel CLI or the new environment variables support.
You should be able to update them with vercel secrets rm notion-token and vercel secrets rm blog-index-id and then go through the import flow again or add them with the CLI with vercel secrets add notion-token "YOUR_TOKEN" and vercel secrets add blog-index-id "YOUR_PAGE_ID"

authors: furkanacikgoz ijjk

repo: ijjk/notion-blog


text:
github issue template

It should contain links how to create a min repo on stackblitz / codesandbox.

You might use something like this: https://stackblitz.com/edit/github-ytvy85-gv1rtf?file=src%2Ftest.spec.ts
It is simply a copy of your examples stackblitz, but with most files deleted. I just kept style & setup related files.

Hi there,
Thanks for your help, my plan was the same with the difference to do it in the example repo as a separate branch:

master - as it is
base - only setup without tests

Hi,
Yeah, ofc, this would allow keeping versions in sync & use CI pipelines (I guess you have some), so this is way better.
Ideally, IMO even more files should be hidden/removed from the files tree, to keep the strict minimum.

v13.4.0 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.

authors: GerkinDev satanTime


text:
[CI] Xcode 7 beta 6 has come in Travis

http://blog.travis-ci.com/2015-08-27-xcode-70-beta-for-oss/

:ship:

repo: ikesyo/Himotoki


text:
android 14 上的拖拽异常：阴影视觉残留

描述：android 14 设备，在拖拽返回时，处于返回栈中的内容不可见，同时正在侧滑返回的页面边界呈现 拖拽 的阴影 残留现象。

修复：通过修改 demo 中 SwipeBackActivityHelper#onActivityCreate() 的设置背景逻辑来修复这一问题。

修改之前：

    public void onActivityCreate() {
        mActivity.getWindow().setBackgroundDrawable(new ColorDrawable(Color.TRANSPARENT));
        mActivity.getWindow().getDecorView().setBackgroundDrawable(null); // 问题在这里
        mSwipeBackLayout = (SwipeBackLayout) LayoutInflater.from(mActivity).inflate(
                me.imid.swipebacklayout.lib.R.layout.swipeback_layout, null);
    }

修改之后：

   public void onActivityCreate() {
        Drawable drawable = new ColorDrawable(Color.TRANSPARENT);
        mActivity.getWindow().setBackgroundDrawable(drawable);
        mActivity.getWindow().getDecorView().setBackgroundDrawable(drawable);
        mSwipeBackLayout = (SwipeBackLayout) LayoutInflater.from(mActivity).inflate(
                me.imid.swipebacklayout.lib.R.layout.swipeback_layout, null);
   }

如果修改之后无效，还需要检查 styles.xml 中的设置

<item name="android:windowIsTranslucent">true</item>

希望对碰到相同问题的人有帮助！

有用

我这边jcenter加载不到库，请教您是怎么加载的

你可以选择以下方式：

源码依赖，直接 copy 到项目；
导入 library 作为 module 依赖

怎么搞成一个lib呢，我没有做过类似的东西,就是把项目编译成一个jar包嘛

我拿进来一直在报错，我再试试看，第一次搞android实在是不好意思打扰到您了

先把 项目 clone 到本地；
再按照图中方式导入，导入框中的 Source directory 就是 clone 到本地 的 这个项目 的 library 本地路径

好的好的，我试试看

我拿进来一直在报错，我再试试看，第一次搞android实在是不好意思打扰到您了

如果你是做新项目，建议你不要用这个库了，我是在解决 之前的项目中碰到的问题。现在 android 系统有 自己的 拖拽 返回功能，没必要用这个了

好的，我去搜搜看，谢谢您

好的，我去搜搜看，谢谢您

你不用搜啊，系统自带的 拖拽返回 功能，在屏幕 左边 和 右边 都可以 用 手势 触发，你啥都不用做，android 手机用户 都知道的。

我这个是定制的设备，系统还是android8.0，就很多功能都没有，要自己写

有用，点个赞


text:
Adding several serial functions and unit tests for all print and println functions

Added mocking for:

Serial::read,
Serial::available,
Serial::write
A new helper class stringCapture which simplifies getting all data from Serial functions, or other functions for that matter. This helps when testing code with arbitrary number of calls to Serial functions, but where the "sent" string is known (ie, you know how the protocol should look, but don't care how it is created).

Unit tests are added for almost all functionality, and also updated to cover all print/println functions.

Good work!
My comment is only one for a position where we should have stringCapture.
It seems a helper function for arduino-mock's unittest, so it should be locate in /test?

Hi Ikeyasu!
Thanks! I really appreciate the project fyi, I've been looking for a good mocking system of the arduino platform for a long time as it is fairly hard to test on the platform itself :).
Anyways, back to topic, the stringCapture class is supposed to be used by external users. I'm currently using it in a private project to verify functions which calls Serial::write arbitrary number of times and where I don't want to rely on the internal implementation of the function, but the outcoming stream format is really important. In this testcase, I encode it using the arduino functions, then I decode it using the PC side decoder within the unit test/mock framework.

Thank you for your reply.
I would like to improve Arduino testing framework. (You know the current Arduino testing is very poor..)

I'm currently using it in a private project to verify functions which calls Serial::write arbitrary number of times and where I don't want to rely on the internal implementation of the function

You mean you are using it as a library for your Arduino project?
If so, please consider to separate the class to another header file.
I understood that It is necessary but I would like to keep a structure of 'serial.h' as same as Arduino's library.

Fair enough. I've moved the functions into a file called serialHelper.cc/h and serialHelper_unittest.cc. Makefiles have been updated. Is this better?

LGTM. It was merged manually.
Thanks a lot.

Thank you :)

authors: frznlogic ikeyasu

repo: ikeyasu/arduino-mock

license: isc


text:
DotRecast creating a lot of RcSpan objects for a relatively small scene.

I'm in the memory profiler today checking in on my program and was surprised by the number of objects that DotRecast is creating and keeping live for what might be considered a relatively small scene -

Here you'll notice we have 500k live instances of RcSpan -

Is there any change we can make to DotRecast or our usage to reduce the object count footprint here? Maybe a different internal representation or perhaps a posteri pruning? Or perhaps there's a reference from the mesh construction process I can let go of? I currently keep a reference to RcBuilderResult so I can draw the above debug lines. Should I not hold on to that? If so, would there be a better way to draw debug info for the nav mesh than using RcBuilderResult? If not, can I prune RcBuilderResult somehow?
Since we're dealing with realtime games, we'd like to keep the GC sweep phase as cheap as possible.
Lastly, here's the related issue I filed locally -
https://github.com/bryanedds/Nu/issues/774
Thank you for your greatly helpful project - it has already saved us tremendous amounts of time and effort!

Hello,
We're currently working on the issues you mentioned.
The problem seems to stem from RcBuilderResult referencing many objects. We're currently working on optimizing RcSpan.
Once the issue is resolved, we will mention it.

Thank you kindly!

@bryanedds
50ea674 - used option keepInterResults to save memory
Inspired by the recastnavigation source code, I added the keepInterResults option. You will be able to see that it significantly reduces memory usage.

I don't think this change set helps us because none of the changes touch our actual use path. Here's how we use DotRecast currently -
https://github.com/bryanedds/Nu/blob/70edd89adab2e2befab54ceba4cfb370354c2453/Nu/Nu/World/WorldScreen.fs#L453-L467
We use the public RcBuilderResult Build(IInputGeomProvider geom, RcBuilderConfig bcfg) method to generate our nav data, which in turn calls public RcBuilderResult Build(RcContext ctx, int tileX, int tileZ, IInputGeomProvider geom, RcConfig cfg, RcHeightfield solid). As far as I can see, neither of those code paths are hit any of the code you changed.
Am I missing something?

Thank you, this should work better!

authors: bryanedds ikpil

repo: ikpil/DotRecast

license: Zlib


text:
ObjectEncoder and ObjectDecoder

java nettyserver used ObjectEncoder and ObjectDecoder
The client is developed using .net
how  impl in DotNetty support to send and receive objects.

The ObjectEncoder/ObjectDecoder in Netty has been deprecated. Therefore, it will not be implemented.

authors: ikpil vincentZ-Z

repo: ikpil/UniNetty


text:
[WIP] client/x11: file clipping support

Teach XFreeRDP to transfer files via cliprdr.

[ ] Implement local-to-remote transfers

[x] Preparatory work

[x] Negotiating streaming support
[x] Registering local formats
[x] Data conversions
[x] Common utilities for FILEDESCRIPTOR processing

[x] Basic format and backend support

[x] Support for text/uri-list

[x] Parsing
[x] Directory expansion
[x] Serializing into FILEDESCRIPTOR

[x] Support for POSIX files

[x] Querying sizes
[x] Querying contents

[x] Client integration (xfreerdp)

[x] Dynamic format registration
[x] Clipboard callbacks

[x] Extract backend interface from local file code
[x] Optimize POSIX backend

[x] Cache open fds
[x] Avoid needless seeking

[ ] Cleanup round

[x] Formatting
[x] Refactoring
[x] Debug logging
[ ] Commit cleanup

[x] Diffs
[ ] Ordering
[ ] Comments

[ ] Conditional compilation

[ ] Testing & bugfix

[ ] Write an acceptance check list
[ ] Evaluate quality
[ ] Fix found issues

:checkered_flag: PR should be ready for review at this point
[ ] Implement and test asynchronous GIO backend (x-special/gnome-copied-files)
:question: Support for KIO (application/x-kde-cutselection)

:grey_question: Implement remote-to-local transfers
:grey_question: Implement intersession (raw) transfers
:grey_question: File locking

File clipping tests
Positive

[ ] File names

[ ] ASCII file names
[ ] Unicode file names
[ ] Special file names

[ ] Whitespace
[ ] Line breaks
[ ] Percent characters
[ ] Prefixed with dots

[ ] File types

[ ] Nested directories
[ ] Symbolic links

[ ] File sizes

[ ] Empty files
[ ] Empty directories
[ ] Large files (< 2 GB)
[ ] Over 9000 files in a directory

Negative

[ ] Invalid file names

[ ] Windows special characters
[ ] Windows reserved names
[ ] Invalid UTF-8 in file names

[ ] UTF-16
[ ] Invalid UTF-8
[ ] Non-UTF-8

[ ] Overlong file name

[ ] Overlong single name
[ ] Overlong full name

[ ] Invalid file sizes

[ ] Files over 2 GB
[ ] Files over 4 GB

[ ] System error handling

[ ] Unreadable file
[ ] Unreadable directory
[ ] Broken symlink

[ ] Crash testing

[ ] Symbolic link loop
[ ] Removal of files during transfer
[ ] Clipboard update during transfer

repo: ilammy/FreeRDP


text:
Most of the selected settings are not saved

What I did:
I selected "Save all" data in the settings, rebooted Automatic1111 and tried exporting the changes.
As it turns out, only the following settings are saved:
{
"state-img2img_checkpoint": "",
"state-img2img_#script_list": "None",
"state-img2img_sampling": "DPM++ 3M SDE",
"state-img2img_seed": "-1",
"state-img2img_styles": "",
"state-img2img_scheduler": "Karras",
"state-tab": "img2img",
"state-img2img_prompt": "masterpiece, best quality, highres, lora:more_details:0.5 lora:SDXLrender_v2.0:1,"
}
The plugin does NOT save other changed settings and fields.
That is, they are not saved:

Negative prompt
Checkpoint
most img2img settings
Controlnet
Tile Diffusion
Previously selected tabs are not selected (for example, Batch in img2img does not open on its own).

As a result, at the moment (with the latest updates for Automatic1111 (08 May 2024)) this plugin does NOT work almost completely.

Hi, @Shyryp ! Did you hit 'Apply settings' button before reloading the UI?

He's right, I'm afraid it's not working at all now.

I have made some fixes for the new Gradio. Unfortunately, the core code is constantly changing, and I cant keep up with updating the extension. Please check your browser console if something isnt working and share any errors you see.

authors: EmoryAhlberg Shyryp ilian6806


text:
How to add transparency to empty page

I have a custom css file going on, but for some reason the main page (empty state) editor content is not getting a transparency. What would be the css class for it?

My css file:
.scroll-decoration {
  box-shadow: none !important;
}

.minimap, .editor-scrollable>.decorationsOverviewRuler {
  opacity: 0.6;
}

.editor-container {
  background: transparent !important;
}

.monaco-workbench .part.sidebar
.search-view .search-widget .input-box, .search-view .search-widget .input-box .monaco-inputbox,
.monaco-workbench .part.editor>.content>.one-editor-silo>.container>.title .tabs-container>.tab,
.monaco-editor-background,
.monaco-workbench .part>.content,
.monaco-workbench .editor>.content>.one-editor-silo.editor-one,
.monaco-workbench .part.editor>.content>.one-editor-silo>.container>.title,
.monaco-workbench .part>.title,
.monaco-workbench,
.monaco-workbench .part,
body {
  background: rgba(1, 22, 39, 0.038) !important;
}

.editor-group-container>.tabs {
  background-color: transparent !important;
}

.editor-group-container>.tabs .tab {
  background-color: transparent !important;
}

.editor-group-container>.tabs .tab.active, .editor-group-container>.tabs .monaco-breadcrumbs {
  background-color: rgba(1, 22, 39, 0.3) !important;
}

.monaco-list.settings-toc-tree .monaco-list-row.focused {
  outline-color: rgb(0, 43, 54, 0.6) !important;
}

.monaco-list.settings-toc-tree .monaco-list-row.selected,
.monaco-list.settings-toc-tree .monaco-list-row.focused,
.monaco-list .monaco-list-row.selected,
.monaco-list.settings-toc-tree:not(.drop-target) .monaco-list-row:hover:not(.selected):not(.focused) {
  background-color: rgba(72, 85, 127, 0.487) !important;
  color: #ffffff !important;
}

.monaco-list.settings-editor-tree .monaco-list-row {
  background-color: transparent !important;
  outline-color: transparent !important;
}

.monaco-inputbox {
  background-color: rgba(41, 41, 41,0.2) !important;
}

.monaco-editor .selected-text {
  background-color: rgba(0, 90, 111, 0.6) !important;
}

.monaco-editor .focused .selected-text {
  background-color: rgba(0, 90, 111, 0.3) !important;
}

.monaco-editor .view-overlays .current-line {
  border-color: rgba(7, 54, 66,0.2) !important;
}

.extension-editor,
.monaco-workbench .part.editor>.content>.one-editor-silo>.container>.title .tabs-container>.tab.active,
.preferences-editor>.preferences-header,
.preferences-editor>.preferences-editors-container.side-by-side-preferences-editor .preferences-header-container,
.monaco-editor, .monaco-editor .inputarea.ime-input,
.monaco-list .monaco-list-rows {
  background: transparent !important;
}

.monaco-workbench .part.sidebar {
  background-color: rgba(0, 33, 43, 0.3) !important;
}

.notification-toast {
  padding: 4px 6px !important;
  border: 1px solid #c6c6c6 !important;
  border-radius: 3px !important;
  box-shadow: none !important;
  background-color: rgba(1, 22, 39, 0.8) !important;
}

.notifications-list-container,
.notifications-list-container .monaco-list-row {
  background: transparent !important;
}

.monaco-button {
  border-radius: 3px !important;
}

.quick-input-widget {
  background-color: rgba(1, 22, 39, 0.9) !important;
  padding: 4px 6px !important;
  border-radius: 3px !important;
  top: 50% !important;
  transform: translate(0%, -50%) !important;
  box-shadow: none !important;
  border: 1px solid #c6c6c6 !important;
}

.editor-group-container>.tabs .tab {
  border: none !important;
}

.terminal-outer-container,
.xterm-viewport,
.xterm-rows {
  background-color: transparent !important;
}

.monaco-workbench.fullscreen {
  background-color: #002b36 !important;
}

.monaco-editor .margin {
  background: rgba(1, 22, 39, 0.038) !important;
}

.notebookOverlay.notebook-editor,
.cell-statusbar-container,
.margin-view-overlays,
.monaco-list-row:hover:not(.selected):not(.focused) {
  background-color: transparent !important;
}

.monaco-workbench .pane-header {
  background-color: rgba(1, 22, 39, 0.3) !important;
}

I don’t provide support for custom themes, apologies. You could try using the Developer Console in VSCode through the Command Palette to play with VSCode’s styles in real-time. Also, consider checking the existing theme for Dark+ and its alternative version that only styles the sidebar, the difference between those themes has the classes that you need to style.

authors: gonzastoll illixion

repo: illixion/vscode-vibrancy-continued


text:
std::complex multiply in kernel produces wrong result

Running complex.cxx, which does multiply on std::complex array elements in a kernel, with hipSYCL on AMD RX 570, results in garbage results:
$ make -f Makefile.hipsycl
$ ./build-hipsycl/complex gpu
[GPU  ] Device 67df {AMD}
0: (0,0) * (0,0) = (5.51054e+84,3.92651e-261)
1: (1,-1) * (1,1) = (4.88846e-20,8.07758e-276)
2: (2,-2) * (2,2) = (5.51054e+84,3.92651e-261)
3: (3,-3) * (3,3) = (4.88844e-20,8.07758e-276)
4: (4,-4) * (4,4) = (5.51054e+84,3.92651e-261)
5: (5,-5) * (5,5) = (4.88846e-20,8.07758e-276)
6: (6,-6) * (6,6) = (5.51054e+84,3.92651e-261)
7: (7,-7) * (7,7) = (4.88846e-20,8.07758e-276)
8: (8,-8) * (8,8) = (5.51054e+84,3.92651e-261)
9: (9,-9) * (9,9) = (4.88846e-20,8.07758e-276)
10: (10,-10) * (10,10) = (5.51054e+84,3.92651e-261)
11: (11,-11) * (11,11) = (4.88846e-20,8.07758e-276)
12: (12,-12) * (12,12) = (5.51054e+84,3.92651e-261)
13: (13,-13) * (13,13) = (4.88846e-20,8.07758e-276)
14: (14,-14) * (14,14) = (5.51054e+84,3.92651e-261)
15: (15,-15) * (15,15) = (4.88846e-20,8.07758e-276)

Addition on the other hand produces the correct result. I built b4d2e1185a86f6fc6ce58828bd9856d120eeb9b7 from source, against ROCm 3.8.0 on Ubuntu 18.04.
Aside: my other simple examples, including a usm test, are working using the ROCm backend. I have not yet been able to get CUDA or CPU backends to work on my test machine.

Well, officially SYCL doesn't support std::complex inside kernel code (or any other std:: stuff really, with only a few exceptions). In general, std:: code might work, or might not work inside kernels with hipSYCL.
The reason why we cannot really make guarantees about such code is because it depends on the implementation of the standard library. There are restrictions inside SYCL kernels that any kernel code must obey. STL code might violate these restrictions. For example, a simple assert() may be enough to cause problems because assert() might call std::terminate() which is unavailable on device. Or code might make other assumptions that are only true on the host.
gfx80x support in ROCm is shaky in general, independently of hipSYCL. There have been numerous reports of people having encountered compiler bugs with that hardware generation. hipSYCL doesn't touch code generation at all (it mainly does an additional AST pass to make sure that everything required by a kernel is treated as HIP/CUDA __host__ __device__), so whatever happens usually happens because of the clang HIP compiler..
I don't see how we could fix this - likely it's either caused by the STL implementation or a bug in clang HIP or the amdgpu LLVM backend (potentially for gfx80x generation specifically). You could try a different clang version.
If feasible I would also recommend using a custom complex implementation which would also be in line with the SYCL specification. With that said, I think there should at least be a sycl::complex in the specification for users who need complex numbers.

+1 for a sycl::complex in the specification, I've been pushing for something like that: https://github.com/intel/llvm/issues/2061. std::complex works with Intel's implementation with the -device-math-lib=fp32,fp64 option and ComputeCPP with -ffast-math, but using sycl namespace is probably a cleaner way to standardize this.
I see what you mean regarding HIP support - it seems to work on some machines and not others depending on the C library implementation. My gtensor HIP backend happens to be working with complex numbers on my test machines, but I guess I just got lucky. For CUDA, using thrust::complex works well, std::complex not so much. Which is fine because thrust::complex is included with all recent cuda distributions and with type aliasing I can bring it in to whatever namespace is convenient (gtensor does this with gt::complex).

What I could offer you if you are interested in sycl::complex is that we add that class in hipSYCL. In general it's always a good idea for standardization if you can point to an implementation that has already successfully prototyped a feature and it might be an incentive for other implementations to follow.
Of course the fastest way to add this would be if you create a PR, otherwise I can work on it at some undetermined point in the future when I have time for it ;)

I guess NVIDIA had solved this with their C++ core library.
Perhaps their implementation can be used here? @brycelelbach

Oh Ronan :). You do love asking me questions I cannot answer.
std::complex, the class template, is the easy part -  at least functionally. The challenging part is associated math library functions. Fortunately CUDA has an excellent math library team.

For CUDA, using thrust::complex works well, std::complex not so much.

Stay tuned. Everything is std::, including complex, is coming to an NVIDIA GPU near you soon. And I do mean everything.

My guess would be that the problem here is a miscompile, NOT an issue with std::complex. Multiply is fairly "boring". The common standard libraries (including libc++, which my team uses) do typically implement multiply with some intrinsics, but I see no reason why this code or code like it would not work. The fact that the code compiled means that the relevant builtins exist, or at least the compiler is aware of them. It's possible they are defined wrong. Try turning off device code optimizations and see if it repros.

Ouch! :-(

I believe that is the extent to which I can provide assistance in this regard, given my current employer and line of work.

Thanks for the hints at least, my dear coopetitor! :-)
Since most of the code is open-source, we can probably layer or retarget a lot of things by playing with (inline) namespaces and so on. No need to reimplement things just for the sake of reimplementing things...

For CUDA, using thrust::complex works well, std::complex not so much.

Stay tuned. Everything is std::, including complex, is coming to an NVIDIA GPU near you soon. And I do mean everything.

You said "everything"... My secret plan is to accelerate all the FPGA bitstream generation by x1000 by using GPU. This is "just" C++ using the STL, right? :-)

I've just had a look at the LLVM IR that comes out, and I can see nothing that would be a problem on device.
The code also runs fine and produces correct results for me with current hipSYCL and clang 10 on my Radeon VII (with ROCm 3.8) as well as GTX 1080 (with CUDA 11.0). I agree that it is probably a miscompile - likely a bug in the amdgpu LLVM backend for that particular chip.

What I could offer you if you are interested in sycl::complex is that we add that class in hipSYCL. In general it's always a good idea for standardization if you can point to an implementation that has already successfully prototyped a feature and it might be an incentive for other implementations to follow.
Of course the fastest way to add this would be if you create a PR, otherwise I can work on it at some undetermined point in the future when I have time for it ;)

This is a great idea thank you! I am interested to try implementing it, although not sure how soon I will have time (will see who gets to it first I guess? Will let you know before starting work so we don't duplicate effort). I think just implementing conj /norm/plus/minus/multiply/divide is almost trivial, like @brycelelbach said it's all the math functions that get complicated. We could start simple and expand. For the Fusion code I am working on porting to different GPUs, we are actually only using the basic operations - I think that covers a non-trivial number of use cases.

My complex.cxx example works on Ubuntu 20.04 with same version of hipSYCL and ROCm, same GPU RX 570 (gfx 803) (in a different chroot). It appears to be an issue with Ubuntu 18.04 and ROCm 3.8 packages, perhaps with gcc7 version of std lib.
I'm going to go ahead an close the issue, and create a new feature request re sycl:complex prototype. In my experience std::complex support is inconsistent and fragile in SYCL implementations, which is a real problem for the application I am working on.

authors: bd4 brycelelbach illuhad keryell

repo: illuhad/hipSYCL


text:
Linker error on clang 11+ for unnamed kernel lambdas and function object kernels

In clang 11 and newer, the way that clang generates kernel invocation stubs on CUDA and HIP was changed. This now causes code using unnamed kernel lambdas to fail with a linker error. clang 10 works fine.
The following code (which follows the same principles as hipSYCL internals) reproduces the issue:
#include <SYCL/sycl.hpp>

template<class kernel_name, class F>
__sycl_kernel void invoker(F f){
    f();
}

int main(){
  std::function<void()> bound_invoker = [](){
    invoker<class _unnamed_kernel>([=](){});
  };
  bound_invoker();
}

It seems to be related to the fact that we wrap the kernel launch in a function object - without the function object it works fine. Also named kernels work fine, so it seems that clang's default name mangling that we rely on doesn't do the right thing here.

It seems function objects as kernels are also affected, i.e. all cases where we don't explicitly rename the kernel.

It seems that starting with clang 11, we also need to rerun codegen during the host pass - if this is the entire problem in that case it should be easy to fix since we already do the same for the device pass.


text:
Enforce cxx standards in build

This should be the correct version of that fix. Passed both docker build tests. I've also removed the now extraneous --std=c++14 build flag from the ROCm build and used the opportunity to multithread the build in both that dockerfile and the one for CUDA
Thanks @psalz for giving me a reason to revisit every single build at work now that you've shown me CMAKE_CXX_EXTENSIONS =P

Awesome, thank you! Could you please also put implement the changes you did to the Dockerfiles in the singularity definition files (also in install). They do exactly the same as the Dockerfiles, so we should try to keep them in sync.

Sure thing. Have already shit everything down for the night, but will do it tomorrow morning, should be easy

Having a go at this right now and it's not liking a class from hipcpu... wonder if that got bumped while we weren't looking?
[ 38%] Building CXX object src/libhipSYCL/CMakeFiles/hipSYCL_cpu.dir/application.cpp.o
cd /home/rocm-user/hipSYCL/build/src/libhipSYCL && /home/rocm-user/hipSYCL/bin/syclcc   -DHIPSYCL_DEBUG_LEVEL=1 -DhipSYCL_cpu_EXPORTS -I/home/rocm-user/hipSYCL/include -I/home/rocm-user/hipSYCL/contrib/hipCPU/include  -O3 -DNDEBUG -fPIC   --hipsycl-platform=cpu --hipsycl-bootstrap -std=c++14 -o CMakeFiles/hipSYCL_cpu.dir/application.cpp.o -c /home/rocm-user/hipSYCL/src/libhipSYCL/application.cpp
In file included from /home/rocm-user/hipSYCL/contrib/hipCPU/include/hipCPU/hip/hip_runtime.h:62:0,
                 from /home/rocm-user/hipSYCL/bin/../include/CL/sycl/detail/../backend/backend.hpp:45,
                 from /home/rocm-user/hipSYCL/bin/../include/CL/sycl/detail/task_graph.hpp:32,
                 from /home/rocm-user/hipSYCL/bin/../include/CL/sycl/detail/runtime.hpp:35,
                 from /home/rocm-user/hipSYCL/bin/../include/CL/sycl/detail/application.hpp:33,
                 from /home/rocm-user/hipSYCL/src/libhipSYCL/application.cpp:28:
/home/rocm-user/hipSYCL/contrib/hipCPU/include/hipCPU/hip/detail/runtime.hpp:271:25: error: enclosing class of constexpr non-static member function 'std::size_t hipcpu::device::get_max_shared_memory() const' is not a literal type
   constexpr std::size_t get_max_shared_memory() const
                         ^
/home/rocm-user/hipSYCL/contrib/hipCPU/include/hipCPU/hip/detail/runtime.hpp:184:7: note: 'hipcpu::device' is not literal because:
 class device
       ^
/home/rocm-user/hipSYCL/contrib/hipCPU/include/hipCPU/hip/detail/runtime.hpp:184:7: note:   'hipcpu::device' has a non-trivial destructor

Double posting as I'm doing stuff now:
Going through his (@misos1) steps and how he bumped into this it would appear that syclcc is the culprit, in a way. It's reading the correct clang when it's set through CC and CXX but it doesn't get forwarded straight through CMake's variables... The reason It's only being picked up here could be because the standard CC in Bionic is good enough whereas the one in Xenial is (predictably) not.
I'll push a minor tweak that introduces the multithreaded build and all, but I'll leave the environment variables for the time being. Still don't like them so I'll see if I can figure out a way to do this part semi-smartly

Great, thanks for investigating!

authors: VileLasagna illuhad


text:
Change highlight for stylusExplicitVariable to Identifier

Stylus variables highlighted as NonText now. NonText highlight rule is for non printable chars like line breaks or tabs, it usually has low contrast and it is not easily readable. I've changed it to Identifier to make it easy to read.
Before:

After:

Accepted.
I just used this NonText highlight rule because I wanted stylus variables to differ from classes and ids. I actually haven't thought about this issue because NonText is pretty readable and looks very nice in the color scheme that I currently use. And this is, probably, not the case for the vast majority of vim users.
Thank you.

authors: igorgladkoborodov iloginow

repo: iloginow/vim-stylus


text:
I do not Install Goodwork Project Management Tool on Ubuntu 20.04

I do not install Goodwork Project Management Tool on Ubuntu 20.04
I don't know the following settings.
ｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰ
APP_ENV=local
APP_KEY=
APP_DEBUG=true
APP_LOG_LEVEL=debug
APP_URL=http://goodwork.techviewleo.com # Use correct DNS domain name
APP_PORT=80
APP_NAME=Goodwork
APP_PROTOCOL=http
APP_LOCALE=en
DB_CONNECTION=mysql
DB_HOST=db
DB_PORT=3306
DB_DATABASE=goodwork
DB_USERNAME=root
DB_PASSWORD=StrongDBPassw0rd
DB_ROOT_PASSWORD=StrongrootDBPassw0rd
BROADCAST_DRIVER=pusher
CACHE_DRIVER=file
SESSION_DRIVER=file
QUEUE_DRIVER=redis
REDIS_HOST=redis
REDIS_PASSWORD=null
REDIS_PORT=6379
REDIS_CLIENT=predis
MAIL_MAILER=smtp
MAIL_DRIVER=smtp
MAIL_HOST=mailtrap.io
MAIL_PORT=2525
MAIL_USERNAME=null
MAIL_PASSWORD=null
MAIL_ENCRYPTION=null
MAIL_FROM_ADDRESS=
MAIL_FROM_NAME=
PUSHER_APP_ID=23123123
PUSHER_APP_KEY=SASHDASDASD
PUSHER_APP_SECRET=AUSDASDSDSSDW
PUSHER_APP_CLUSTER=
MIX_PUSHER_APP_KEY="${PUSHER_APP_KEY}"
MIX_PUSHER_APP_CLUSTER="${PUSHER_APP_CLUSTER}"
COMPANY_NAME=
TELESCOPE_ENABLED=false
NOTIFICATION_CHANNELS="broadcast,mail,database"
CLIENT_ID=
CLIENT_SECRET=
ｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰ
Could you please tell me this setting?

the project is currently pause, so don't use it until a stable release
On Tue, Apr 13, 2021 at 8:09 AM yukimaharu @.***> wrote:

I do not install Goodwork Project Management Tool on Ubuntu 20.04
I don't know the following settings.
ｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰ
APP_ENV=local
APP_KEY=
APP_DEBUG=true
APP_LOG_LEVEL=debug
APP_URL=http://goodwork.techviewleo.com # Use correct DNS domain name
APP_PORT=80
APP_NAME=Goodwork
APP_PROTOCOL=http
APP_LOCALE=en
DB_CONNECTION=mysql
DB_HOST=db
DB_PORT=3306
DB_DATABASE=goodwork
DB_USERNAME=root
DB_PASSWORD=StrongDBPassw0rd
DB_ROOT_PASSWORD=StrongrootDBPassw0rd
BROADCAST_DRIVER=pusher
CACHE_DRIVER=file
SESSION_DRIVER=file
QUEUE_DRIVER=redis
REDIS_HOST=redis
REDIS_PASSWORD=null
REDIS_PORT=6379
REDIS_CLIENT=predis
MAIL_MAILER=smtp
MAIL_DRIVER=smtp
MAIL_HOST=mailtrap.io
MAIL_PORT=2525
MAIL_USERNAME=null
MAIL_PASSWORD=null
MAIL_ENCRYPTION=null
MAIL_FROM_ADDRESS=
MAIL_FROM_NAME=
PUSHER_APP_ID=23123123
PUSHER_APP_KEY=SASHDASDASD
PUSHER_APP_SECRET=AUSDASDSDSSDW
PUSHER_APP_CLUSTER=
MIX_PUSHER_APP_KEY="${PUSHER_APP_KEY}"
MIX_PUSHER_APP_CLUSTER="${PUSHER_APP_CLUSTER}"
COMPANY_NAME=
TELESCOPE_ENABLED=false
NOTIFICATION_CHANNELS="broadcast,mail,database"
mobile login
CLIENT_ID=
CLIENT_SECRET=
ｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰ
Could you please tell me this setting?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/iluminar/goodwork/issues/1340, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACH7DG6ASRHJORG7MVT4MULTIORWRANCNFSM422MUYTQ
.

Thank you for your reply.
I'm looking forward to the release.

the project is currently pause, so don't use it until a stable release
…
On Tue, Apr 13, 2021 at 8:09 AM yukimaharu @.***> wrote: I do not install Goodwork Project Management Tool on Ubuntu 20.04 I don't know the following settings. ｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰ APP_ENV=local APP_KEY= APP_DEBUG=true APP_LOG_LEVEL=debug APP_URL=http://goodwork.techviewleo.com # Use correct DNS domain name APP_PORT=80 APP_NAME=Goodwork APP_PROTOCOL=http APP_LOCALE=en DB_CONNECTION=mysql DB_HOST=db DB_PORT=3306 DB_DATABASE=goodwork DB_USERNAME=root DB_PASSWORD=StrongDBPassw0rd DB_ROOT_PASSWORD=StrongrootDBPassw0rd BROADCAST_DRIVER=pusher CACHE_DRIVER=file SESSION_DRIVER=file QUEUE_DRIVER=redis REDIS_HOST=redis REDIS_PASSWORD=null REDIS_PORT=6379 REDIS_CLIENT=predis MAIL_MAILER=smtp MAIL_DRIVER=smtp MAIL_HOST=mailtrap.io MAIL_PORT=2525 MAIL_USERNAME=null MAIL_PASSWORD=null MAIL_ENCRYPTION=null MAIL_FROM_ADDRESS= MAIL_FROM_NAME= PUSHER_APP_ID=23123123 PUSHER_APP_KEY=SASHDASDASD PUSHER_APP_SECRET=AUSDASDSDSSDW PUSHER_APP_CLUSTER= MIX_PUSHER_APP_KEY="${PUSHER_APP_KEY}" MIX_PUSHER_APP_CLUSTER="${PUSHER_APP_CLUSTER}" COMPANY_NAME= TELESCOPE_ENABLED=false NOTIFICATION_CHANNELS="broadcast,mail,database" mobile login CLIENT_ID= CLIENT_SECRET= ｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰｰ Could you please tell me this setting? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1340>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACH7DG6ASRHJORG7MVT4MULTIORWRANCNFSM422MUYTQ .

Thank you for your reply.
I'm looking forward to the release.

authors: Hasnayeen yukimaharu

repo: iluminar/goodwork


text:
Update Farsi (Persian) translate

Make sure you've reviewed the checklist. (DO NOT REMOVE)
🚨Please review the guidelines for contributing to this repository.

[x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
[x] Make sure you are making a pull request against the dev branch. Also you should start your branch off dev branch.
[x] Check you have included issue number in your pr (e.g #23).
[x] Check you have added tests that prove your fix is effective or that your feature works.
[x] Check your code additions will fail neither code linting checks nor unit test.
[x] Check you added any notable changes to the CHANGELOG.md file.

Description
Please describe your pull request.
💔Thank you!

previous pr has already been merged, this is not necessary

@Hasnayeen I see you update en lang files today and updated them in fa files.
What is the problem?

the same pr has already been merged, https://github.com/iluminar/goodwork/pull/669
this is duplicate, please do not open duplicate pr

Check the changed files. I didn`t open duplicate PR.

I've checked both pr and both have same changes, compare yourself (677 and 669) if you're trying to complete hacktoberfest challenge use this repo please https://github.com/Dhroov7/Hacktoberfest2019 and send pr to that.

I think my last changes not committed. I work on hacktoberfest but I don`t like to complete that without effect on the FOSS. If you think my PR is duplicate, close that.

authors: Hasnayeen aznadesign


text:
🛑 Web STIS is down

In bde26fb, Web STIS (https://stis.ac.id) was down:

HTTP code: 503
Response time: 1331 ms

Resolved: Web STIS is back up in e3a79e1 after 7 hours, 14 minutes.

repo: im-perativa/stis-uptime


text:
Simplified File transfer

Added '*' as a wildcard for any files containing 'mv win-sudo/su', which is basically all the files you wanted to move.

Good catch!

authors: DemonixCraft imachug

repo: imachug/win-sudo


text:
portrait capture image orientation not showing correct.

Hello,i found one issue.In my App i am not allowing device to change orientation. problem is captured image orientation showing .right not .up even if capture image in portrait(up). not just it in all  orientation it showing .right orientation. plz help

I have the same issue. All images is taken from front camera is right orientation

Few things to keep in mind:

The front camera is mounted on the device with the left edge of the phone considered as "up" and the camera is fixed obviously, so even if you disallow orientation changes in your app, it doesn't make portrait orientation "up" for the camera; portrait orientation is always mapped to "right" for the camera.
That being said, camera itself actually doesn't know about orientation either, i.e. the camera knows that portrait maps to right but it doesn't know whether the device is in portrait orientation or not. It is the job of the capture code to tell the capture connection the correct orientation. So if you have not set shouldRespondToOrientationChanges to false on your CameraManager instance, the code in _orientationChanged() is setting the camera orientation every time your phone rotates.
So with that said, there're two issues:
If you explicitly set shouldRespondToOrientationChanges to false, the orientation will be set once on initialization and never changes. If you launch the CameraManager from a portrait orientation, all images will be right afterwards; while if you launch the CameraManager from a horizontal orientation, all images will be up/down afterwards.
The default value of shouldRespondToOrientationChanges is true, so if you don't explicitly set it to false, the images you get from the front camera should have the correct orientation, i.e. "right" for portrait orientation. However, there is a bug in CameraManager that every time you switch between front and back cameras, the orientation is reset to "right" until the phone is rotated again. With this bug, you may actually get "right" images for when you're holding the phone horizontally. If that bug is blocking you, you'll have to compare the image orientation with the current device orientation to see determine whether you're hitting the bug or not, and act accordingly.
One final thing: the logic in _currentVideoOrientation() actually treats portraitUpsideDown as portrait. Not sure why it does that, but just something to keep in mind.

repo: imaginary-cloud/CameraManager


text:
No public image found. It looks like you may be using a private image - please add a credential or check the image URL for mistakes.

Image banned by Render?

https://hub.docker.com/r/imdingtalk/registry-mirror/tags

Image banned by Render?

https://hub.docker.com/r/imdingtalk/registry-mirror/tags

Maybe it has been banned. Try version 1.3, or pull the image and try another public repository.

repo: imdingtalk/registry-mirror


text:
Removing imgui-gfx-renderer?

Would it make sense to remove the renderer which uses the deprecated gfx crate?

https://github.com/gfx-rs/gfx#the-gfx-crate
This repository was originally home to the gfx crate, which is now deprecated. You can find the latest versions of the code for that crate in the pre-ll branch of this repository.

and the last release of gfx (0.18.2) was close to a year ago and is presumably the final release
The reason it might be worth removing is it is maybe (at least it was to me) a little confusing as the gfx repo is still active, but it is now being used for the gfx-hal package. So I initially assumed the  imgui-gfx-renderer was as-valid a thing to use for a new project as glium. To add further confusion, the gllium repo says it is "no longer actively developed by its original author" (which on first glance reads like the project is dead, but it's actually just maintained by different people - edit: made issue about clarifying this with glium project here)
I can see the value in having more than one example integration codebase - which is probably where #243 comes in I guess!

i am pretty in favor of this. It's useful to have the rendering backends in some form for CI to identify any reversions, but it'd be nicer instead if we could figure out how to check out imgui-wgpu and use that as a test bench too.

@thomcc opinions?

In favor of it, but not really in favor of having glium (which is very lightly maintained and not commonly used) be the only example impl here. I think long term we probably want:

A glow renderer instead of the glium renderer.
A wgpu renderer instead of the gfx renderer, although for this I suspect the community does a better job than we would (or than I would anyway), so it requires more thought / coordination.

That said, that stuff doesn't need to block removal of the gfx one.

I do not believe there is a currently publicly available glow implementation. My own imgui bindings are using glow however, and are closely based on the dear imgui opengl bindings. I doubt the https://github.com/Yatekii/imgui-wgpu-rs would be interested in being consumed by us, but maybe they are? I can reach out

@Hperigo has recently started working on https://github.com/Hperigo/imgui-glow-renderer
Played around with it today and seems quite promising (only been going for a few weeks but pretty much worked as expected - missing some obvious things like changing cursors, and things mentioned in the README like custom texture support - but certainly not from being pretty usable)

In favor of it, but not really in favor of having glium (which is very lightly maintained and not commonly used) be the only example impl here.

but it'd be nicer instead if we could figure out how to check out imgui-wgpu and use that as a test bench too

I agree this is a good thing to retain. I wonder if it's just a case of the examples having imgui-whatever-renderer = "1" as a dependency, along with
[patch.crates-io]
imgui = { path = "../imgui/" }

so the CI builds will pull in the latest published release of the renderer, and build against the to-be-tested imgui-rs
Assuming that actually works, then the imgui-rs repo could still have imgui-examples, imgui-glow-example, imgui-wgpu-examples, but the actual integraiton code could live elsewhere and be separately versioned (which seems like a good thing I think?)

Hello!
I am planning on doing the following now that imgui-glow-renderer has been stabilized:

remove the gfx_renderer from this repository, place it in a separate repository under this org, and kill it there.
glium, despite supposedly not being maintained, is chugging along just fine. I'd be in favor of keeping it around, even though glow is my personal preference.
finally, add an sdl2 crate to mirror the winit crate.

It has been removed (well, it is now enjoying a quiet retirement here)

authors: dbr sanbox-irl thomcc

repo: imgui-rs/imgui-rs


text:
High CPU usage on release profile

Describe the bug
High CPU usage on release profile. From < 3% in debug to > 30% in release
To Reproduce
cargo run --example hello_world --release
Please describe your environment

Latest git commit so a78fb454973a2546bde42f6d236448fe6d36ab64
Windows 10 with latest stable msvc toolchain (1.51.0)

Other information
It seems that the culprit is debug_assertion = false so for now I have to enable it in release mode which is not that great but it works.
Same bug in my project when using backend from example directory.

The culprit is here https://github.com/glium/glium/blob/master/src/context/mod.rs#L813-L819 so not directly imgui-rs.
With DebugCallbackBehavior::DebugMessageOnError-> no problem.
With DebugCallbackBehavior::Ignore -> high cpu usage.

Weird, I think you should file the bug with glium then, since that sounds like a bug on their end.

authors: KarlitosVII thomcc


text:
ERR_REQUIRE_ESM error

after installing ""eslint-import-resolver-typescript": "^3.6.1",
there is the Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/tmf/WebstormProjects/back-v3/node_modules/string-width/index.js from /Users/tmf/WebstormProjects/back-v3/node_modules/wrap-ansi/index.js not supported. Instead change the require of /Users/tmf/WebstormProjects/back-v3/node_modules/string-width/index.js in /Users/tmf/WebstormProjects/back-v3/node_modules/wrap-ansi/index.js to a dynamic import() which is available in all CommonJS modules. error while starting application
tsconfig: {   "compilerOptions": {     "module": "commonjs",     "declaration": true,     "removeComments": true,     "emitDecoratorMetadata": true,     "experimentalDecorators": true,     "allowSyntheticDefaultImports": true,     "target": "ES2021",     "sourceMap": true,     "outDir": "./dist",     "baseUrl": "./",     "incremental": true,     "skipLibCheck": true,     "paths": {       "@interfaces": ["src/interfaces"],       "@interfaces/*": ["src/interfaces/*"],     }   },   "include": ["src/**/*"] }
package json:
{   "name": "v3",   "version": "1.0.0",   "description": "",   "license": "MIT",   "scripts": {     "prebuild": "rimraf dist",     "build": "nest build",     "format": "prettier --write \"src/**/*.ts\" \"test/**/*.ts\"",     "start": "cross-env nest start",     "lint": "eslint --ext .js,.ts .",     "lint:fix": "eslint \"{src,apps,libs,test}/**/*.ts\" --fix",     "test": "jest",     "test:watch": "jest --watch",     "test:cov": "jest --coverage",     "test:debug": "node --inspect-brk -r tsconfig-paths/register -r ts-node/register node_modules/.bin/jest --runInBand",     "test:e2e": "echo 'No e2e tests implemented yet.'"   },   "dependencies": {     "@nestjs/common": "10.2.6",     "@nestjs/core": "10.2.6",     "@nestjs/platform-express": "10.2.6",     "@nestjs/swagger": "7.1.13",     "@nestjs/typeorm": "10.0.0",     "class-transformer": "0.5.1",     "class-validator": "0.14.0",     "cross-env": "7.0.3",     "mongodb": "4.16.0",     "reflect-metadata": "0.1.13",     "rimraf": "5.0.5",     "rxjs": "7.8.1",     "typeorm": "0.3.6"   },   "devDependencies": {     "@nestjs/cli": "10.1.18",     "@nestjs/schematics": "10.0.2",     "@nestjs/testing": "10.2.6",     "@types/express": "4.17.18",     "@types/node": "20.8.7",     "@types/supertest": "2.0.15",     "@typescript-eslint/eslint-plugin": "5.62.0",     "@typescript-eslint/parser": "5.62.0",     "eslint": "8.42.0",     "eslint-config-prettier": "9.0.0",     "eslint-import-resolver-typescript": "^3.6.1",     "eslint-plugin-import": "2.29.0",     "eslint-plugin-prettier": "5.0.0",     "eslint-plugin-unused-imports": "^2.0.0",     "husky": "4.2.5",     "lint-staged": "10.2.11",     "prettier": "3.0.3",     "supertest": "6.3.3",     "ts-jest": "29.1.1",     "ts-loader": "9.4.4",     "ts-node": "10.9.1",     "tsconfig-paths": "4.2.0",     "typescript": "5.2.2"   },   "lint-staged": {     "*.ts": [       "eslint --fix",       "git add"     ]   },   "husky": {     "hooks": {       "pre-commit": "lint-staged"     }   } }
node 20.9.0
what can be wrong ?

No reproduction, no way to guess or debug.

No reproduction, no way to guess or debug.

The tsconfig and package json attached, need to run with this config to reproduce

Please provide an online runnable reproduction instead of just codes.

It seems not related to this resolver at all.

authors: JounQin plyasheshnikovt

license: ISC


text:
store: Querying with regex label matchers return invalid metrics in version 0.3.0

Thanos, Prometheus and Golang version used

Thanos: all components 0.3.0
Prometheus: 2.7.1

What happened
After upgrading all components from 0.2.1 to 0.3.0, some dashboards using queries with regex label matchers started showing incorrect metrics. Querying thanos store v0.2.1 from thanos query v0.3.0 works as expected. Toggling deduplication, partial response, and all downsampling options return the same incorrect results. Some query examples:

container_memory_usage_bytes{name=~"thanos-compact} returns metrics for all containers, whereas container_memory_usage_bytes{name="thanos-compact} returns metrics for only thanos-compact. In this case, the invalid results are only for a 6h window, all results outside of this window are correct. The blocks in this 6h window were uploaded with thanos 0.2.1 components.
up{job=~"thanos"} returns thanos metrics correctly, however up{invalidLabelName=~"thanos"} behaves as if the query was for only up. In this case, the query returns incorrect results for all time.

What you expected to happen
Queries return metrics that correctly match the regex in the query, just as prometheus and thanos-store v0.2.1 do.
How to reproduce it (as minimally and precisely as possible):
Should be covered by the description above, but happy to provide any information required.
Full logs to relevant components
thanos-store
level=info ts=2019-02-11T09:16:17.930002237Z caller=flags.go:75 msg="gossip is disabled"
level=info ts=2019-02-11T09:16:17.930311959Z caller=factory.go:39 msg="loading bucket configuration"
level=info ts=2019-02-11T09:16:42.611885128Z caller=main.go:256 msg="disabled TLS, key and cert must be set to enable"
level=info ts=2019-02-11T09:16:42.6122304Z caller=store.go:197 msg="starting store node"
level=info ts=2019-02-11T09:16:42.612546496Z caller=main.go:308 msg="Listening for metrics" address=0.0.0.0:19193
level=info ts=2019-02-11T09:16:42.612433471Z caller=store.go:166 msg="Listening for StoreAPI gRPC" address=0.0.0.0:19092

thanos-query
level=info ts=2019-02-11T09:30:25.069246106Z caller=flags.go:75 msg="gossip is disabled"
level=info ts=2019-02-11T09:30:25.088541595Z caller=main.go:256 component=query msg="disabled TLS, key and cert must be set to enable"
level=info ts=2019-02-11T09:30:25.088775851Z caller=query.go:468 msg="starting query node"
level=info ts=2019-02-11T09:30:25.092463697Z caller=query.go:437 msg="Listening for query and metrics" address=0.0.0.0:19192
level=info ts=2019-02-11T09:30:25.094654745Z caller=query.go:460 component=query msg="Listening for StoreAPI gRPC" address=0.0.0.0:10901
level=info ts=2019-02-11T09:30:30.096756862Z caller=storeset.go:250 component=storeset msg="adding new store to query storeset" address=172.18.0.4:19092
level=info ts=2019-02-11T09:30:30.096901412Z caller=storeset.go:250 component=storeset msg="adding new store to query storeset" address=172.18.0.3:19090

Anything else we need to know

Hm.. I think it is actually quite related to this:
https://github.com/improbable-eng/thanos/issues/834
https://github.com/improbable-eng/thanos/issues/829
This all is related to this PR: https://github.com/improbable-eng/thanos/pull/753 where we change the postings and matchers. Looking more into that, but I am on holidays, so have limited time.

In mean time try deploying thanos-store in 0.2.1.

Thanos store 0.2.1 seems to be working fine for now, enjoy your holidays!

We fixed the matchers here: https://github.com/improbable-eng/thanos/pull/839
Also we added extended test cases, but I don't think we can repro your case. Can you try master image for thanos-store?

Looks like the second scenario from the issue has been fixed! Unfortunately the first has not.
If it'd help I can provide access to the GCS bucket? DM: @BenClapp

I think just more info in what is wrong is fine for now.
So this doesn't not work?

up{job=~"thanos"} returns thanos metrics correctly, however up{invalidLabelName=~"thanos"} behaves as if the query was for only up. In this case, the query returns incorrect results for all time.

What Prometheus itself is doing? It is doing as you expect? And what you expect? Because for "invalid label" ~= the flow is that it gives all, because we filtered out what we could - nothing because label does not exist. (:

Sure :) So with the build from master, this is what I see.

Query for up{invalidLabelName=~"foo"} returns all results, like querying up
Query for up{job=~"invalidLabelValue"} returns all results, like querying up or up{job=~".+"}

In both cases Prometheus returns no results, as I would expect.
I may be mistaken, but shouldn't the logic be to use the label selectors to select series, rather than to filter away series which don't match?

To update on this scenario from the original post

container_memory_usage_bytes{name=~"thanos-compact} returns metrics for all containers, whereas container_memory_usage_bytes{name="thanos-compact} returns metrics for only thanos-compact. In this case, the invalid results are only for a 6h window, all results outside of this window are correct. The blocks in this 6h window were uploaded with thanos 0.2.1 components.

Blocks that have a successful regex match return results as I would expect, that is only series for {name=thanos-compact}. Blocks that do not have any series that match, return all series for this metric name instead.

Confirming the issue.
Another thing to note is that it works fine from thanos-query UI, for example
go_goroutines{instance=~"thanos-query"}
returns single value.
But grafana doing:
GET api/datasources/proxy/1/api/v1/query_range?query=go_goroutines%7Binstance%3D~%22thanos-query%22%7D&start=1550571840&end=1550582670&step=30

to the same thanos-query and get 174 results.

Blocks that do not have any series that match, return all series for this metric name instead.

Ok I think this is a key issue here (: let me again double check between our and tsdb matching in this detail.

Found & fixed: https://github.com/improbable-eng/thanos/pull/862
PTAL and thanks all for details input on what's broken (: Silly bug in edge case ): I wish there were more unit tests for TSDB we could get test cases from. Now our test cases are much more extended then for TSDB itself - hopefully it covers now all we need.

#862 fixed and confirmed by @benclapp :+1: closing.

Thank you, confirming the fix in master-2019-02-21-0c730c1

authors: benclapp bwplotka domgreen sepich

repo: improbable-eng/thanos


text:
Improve dev setup

Added scripts to improve dev setup steps.

This will close #13

@cglotr Thank you for the contribution!

authors: cglotr imranariffin

repo: imranariffin/aiotaskq


text:
作者你好 md预览性能 优点低 渲染太慢了 有办法改进吗

https://react.vuevuex.com/posts/details/61  用作者的md-editor-rt 可以刷新网页看渲染 卡了几秒才出来
版本 "md-editor-rt": "^2.1.0",
react 使用 ：
import MdEditor from 'md-editor-rt';
import 'md-editor-rt/lib/style.css';
<MdEditor previewTheme="vuepress" codeTheme="atom" modelValue={'markdown内容'} previewOnly showCodeRowNumber />
https://vuevuex.com/postsDetail/61： 这个是用的v-md-editor （vue的 他这个预览 渲染的时候就能快）

把延迟渲染设置为0试试
MdEditor.config({
  editorConfig: {
    renderDelay: 0
  }
});

谢谢作者 厉害！

已解决 问题

repo: imzbf/md-editor-rt


text:
Allow to search just photos

https://github.com/inaturalist/inaturalist/issues/1829 shows there is interest in being able to search photos on iNaturalist.
For a new user like me, there seems to be no search for photos at all at first. If I search a species in the main search bar I get something like https://www.inaturalist.org/search?q=Amaryllis-paradisicola and the top bar does not help, instead I have to click a link "view observations" next to a name, which leads to https://www.inaturalist.org/observations?taxon_id=579700
Once I'm on that page, nothing is shown at all unless I allow loading scripts from maps.google.com, which I don't want to do for a variety of reasons and is unexpected as I never asked for a map. Once I allow loading the map, a list of photos somewhat appears in the right corner. It would be nice to be able to get just that.
A workaround would be to provide a search API or some feed for external search engines to provide the service, for instance Creative Commons search as suggested by Dario.

I'm not really sure what you're asking for here, so I'm going to close this. You can search observations in the header by entering "Amaryllis paradisicola" and clicking the "View observations" link. You can also do so at https://www.inaturalist.org/observations. You can view all photos of a taxon from the taxon detail page (e.g. https://www.inaturalist.org/taxa/579700-Amaryllis-paradisicola) by clicking "View More" under the photo. If you're hitting bugs b/c you block scripts from Google, that's a different, larger issue concerning our dependency on Google. I'm not sure we'll ever make it possible to use the site without Google (certainly looking into it for users in China), but right now, there's no way around that.
FWIW, you might find GBIF's search tools a bit more satisfying, e.g. https://www.gbif.org/occurrence/gallery?media_type=StillImage&taxon_key=7346102. You can also filter that to only include iNat contributions to GBIF.
For future feature requests, please go through the Forum so we can talk things through and the rest of the community can provide input. We'd prefer to reserve github issues for things where product-level discussions and decisions have already happened.

authors: kueda nemobis

repo: inaturalist/inaturalist


text:
Journal search

I frequently want to search for posts in the official iNat blog, so IMO we just need a simple, database-based search for posts in a journal, like the dbsearch scope for guides.

Closed in #3549


text:
Issue-144: Add unique page titles.

[X] This pull request has been linted by running npm run lint without errors
[X] This pull request has been tested by running npm run dev and reviewing affected routes
[X] This pull request has been built by running npm run generate without errors
[X] This isn't a duplicate of an existing pull request

Description
To resolve https://github.com/inclusive-design/wecount.inclusivedesign.ca/issues/144.
Add unique titles for each page.
Steps to test

Visit each page;
Make sure they all have unique titles in the format of "{title} | We Count".

Comments addressed and ready for another look.


text:
Renommer les templates iframe en formulaire

Cf https://github.com/incubateur-ademe/quefairedemesobjets/pull/875/files#r1773128655
Les templates du formulaire sont préfixés de iframe ce qui est troublant car tant la carte que le formulaire sont embarqués dans une iframe
qfdmo/_addresses_partials/filters/iframe_advanced_filters.html

fait

repo: incubateur-ademe/quefairedemesobjets


text:
make sure all the mixins are imported in mixins.sass

I'm not sure why the sprites one wasn't there before.
I realised that I missed this when I add the svg mixins before.
If the sprites one wasn't in there for a reason please tell me and I'll take it out again.
Also not sure if this requires an update to the changelog?
@incuna/frontend

If the sprites one wasn't in there for a reason please tell me and I'll take it out again.

So a project doesn't have to have a sprites folder setup just to compile the Sass. Perhaps Compass has changed in the meantime, but it would either error or warn or just get upset if there weren't any folders and/or images to work on.
Our seed projects that use this have it commented out, so including it in a project is trivial.
Perhaps now is the time to add a comment explaining the above? Yay docs!

Also not sure if this requires an update to the changelog?

All updates should go in the changelog, unless they're trivial repo settings. Maybe readme changes shouldn't, but I think it's safer/easier to put all updates in the changelog.

@henrahmagix so leave it in and comment or take it out and comment?

"leave it in and comment" I think would be best :+1:

@henrahmagix how's the comment, if you want more description let me know (also let me know the description because this is the extent of my understanding)

@hippogriffic Have you tested with it imported in a project that has no sprites folders or images? What is output?

@henrahmagix better? Also I did not test I don't know how, but is that necessary now?

but is that necessary now?

Yes, definitely necessary =)

I did not test I don't know how

cd thisfolder
bower link
make a new folder somewhere else and cd to it
bower link incuna-sass -> it goes in bower_components/incuna-sass
touch test.sass or make that file with your own method
import everything in that file like @import incuna-sass/thing
run compass compile --force --sass-dir . --import-path bower_components/incuna-sass
see if it errors

A more detailed test.sass will call all the functions, @include all the mixins, and @extend all the extensions. @hippogriffic Please paste the contents of your test.sass into #44: we could use it for the test suite.

Alternatively, you could bower link incuna-sass in a current project and see if that project errors.

@henrahmagix tests are passing for these changes - see #44 for more details
@incuna/frontend please review

authors: henrahmagix hippogriffic

repo: incuna/incuna-sass


text:
is there a version can upload files?

your work is awesome!!
is there a version can upload files?

Not of http-server. You can search GitHub for sth like "http server upload". I also made one a while ago, but it's not really polished.

Thanks bro

authors: JaosnHsieh derhuerst

repo: indexzero/http-server