text:
fix count condition

Description
fix the count to distinct image_set_id due group field and see if all devices belongs to same imge-set
Fixes # (issue)
Type of change
What is it?

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run make pre-commit to check fmt/vet/lint/test-no-fdo

@mergifyio rebase

Hmmm this PR was force-pushed at some point :/ I hope it didn't undo anything important.

authors: acosferreira omaciel thom-at-redhat

repo: RedHatInsights/edge-api


text:
THEEDGE-3632: add data validation to show sort option on deviceTable

Description
Add validation around if data is available on device table to show or not the ordering options on table column title.
Fixes # THEEDGE-3632
Type of change
What is it?

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] I run npm run lint:js:fix to check that my code is properly formatted

/retest

@mergifyio rebase

@mergifyio refresh

/retest

source: gharchive/pull-request

authors: acosferreira adeliaferreira de1987

repo: RedHatInsights/edge-frontend

license_type: permissive

license_source: github-api


text:
Setup codecov.io

Description
Setup codecov.io
Type of change

Other

Testing steps
Please describe how the change was tested locally. If, for some reason, the testing was not done or not done fully, please describe what are the testing steps.
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@494270f). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #82   +/-   ##
=========================================
  Coverage          ?   29.89%
=========================================
  Files             ?        6
  Lines             ?      669
  Branches          ?        0
=========================================
  Hits              ?      200
  Misses            ?      459
  Partials          ?       10

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 494270f...0f4e47d. Read the comment docs.

authors: codecov-commenter tisnik


text:
test ci.int: Update README.md

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update
Refactor (refactoring code, removing useless files)
Unit tests (no changes in the code)
Bump-up dependent library (no changes in the code)
Security fix in dependent library (no changes in the code)
Security fix in dependent library (changes made in the code)
Behavioral tests (no changes in the code)
REST API tests
Benchmarks (no changes in the code)
Documentation update
Configuration update

Testing steps
Please describe how the change was tested locally. If, for some reason, the testing was not done or not done fully, please describe what are the testing steps.
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

/retest

Codecov Report
Patch coverage has no change and project coverage change: +2.24 :tada:

Comparison is base (03307a8) 60.50% compared to head (7a83c87) 62.75%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1009      +/-   ##
==========================================
+ Coverage   60.50%   62.75%   +2.24%
==========================================
  Files          23       24       +1
  Lines        3226     3606     +380
==========================================
+ Hits         1952     2263     +311
- Misses       1053     1100      +47
- Partials      221      243      +22

Impacted Files
Coverage Δ

server/endpoints_v2.go
100.00% <0.00%> (ø)

server/upgrade_risks_prediction.go
74.60% <0.00%> (ø)

amsclient/amsclient.go
78.08% <0.00%> (+4.20%)
:arrow_up:

server/server.go
64.25% <0.00%> (+4.97%)
:arrow_up:

server/errors.go
64.10% <0.00%> (+5.12%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

shall we close @matysek ?

authors: codecov-commenter juandspy matysek


text:
Availability check through receptor

Following #8 and extending by availability check with receptor directive (now receptor:ping, waiting for satellite-specific)

sorry @slemrmartin just saw this was still in wip (I look at the labels but looks like that's not set up in this repo)  Was this okay to go in?

hm, it seems I should delete and refork my repo.
It should theoretically work with receptor:ping, but there is probably some issue in receptor controller, so I have to wait with tests

authors: agrare slemrmartin


text:
Plan: add typing

Summary by CodeRabbit

New Features

Enhanced type hints for parameters in the Plan class constructor, improving clarity on expected input types.
Introduced hooks_array attribute to store hook specifications.
Added a new entry to .gitignore for ignoring the .local_dev/ directory.

Bug Fixes

Updated logic for adding hooks to virtual machines to ensure both hooks_array and virtual_machines_list are present before proceeding.

Changes

Modified return types of the __enter__ and deploy methods in the Resource class to Any, broadening expected return values.

Report bugs in Issues
The following are automatically added:

Add reviewers from OWNER file (in the root of the repository) under reviewers section.
Set PR size label.
New issue is created for the PR. (Closed when PR is merged/closed)
Run pre-commit if .pre-commit-config.yaml exists in the repo.

Available user actions:

To mark PR as WIP comment /wip to the PR, To remove it from the PR comment /wip cancel to the PR.
To block merging of PR comment /hold, To un-block merging of PR comment /hold cancel.
To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
verified label removed on each new commit push.
To cherry pick a merged PR comment /cherry-pick <target branch to cherry-pick to> in the PR.

Multiple target branches can be cherry-picked, separated by spaces. (/cherry-pick branch1 branch2)
Cherry-pick will be started when PR is merged

To build and push container image command /build-and-push-container in the PR (tag will be the PR number).

You can add extra args to the Podman build command

Example: /build-and-push-container --build-arg OPENSHIFT_PYTHON_WRAPPER_COMMIT=<commit_hash>

To add a label by comment use /<label name>, to remove, use /<label name> cancel
To assign reviewers based on OWNERS file use /assign-reviewers
To check if PR can be merged use /check-can-merge

Supported /retest check runs

/retest tox: Retest tox
/retest python-module-install: Retest python-module-install
/retest all: Retest all

Supported labels

hold
verified
wip
lgtm

/verified

/verified

repo: RedHatQE/openshift-python-wrapper


text:
Add resource pack-based customization

This PR adds the ability to add custom armor and item bars using a resource pack, an example resource pack is included in the example_resourcepack directory. This would close issue #20 and make it much easier for mod and modpack makers to add their own armors.
Currently this system only supports static armor and item entries, however the previous coded api remains to add dynamic entries that depend on the ItemStack. Ive made this on 1.21 initially but i would be glad to backport these changes if needed.

I could do that, although it would require changing parts of the original APIs code as i would have to include that data in TextureOffset

should I still do it?

yeah, of course. also mojang has split the armor texture recently, so it would be make sense.
so like:
  "render": {
     "full": {
        "texture": "detailab:textures/armor_bar.png",
        "texture_width": 128,
        "texture_height": 128,
        "offset": [27, 9]
     },
     "half" {
        ...
     }
   }

Okay sure, gonna do that

i'll try to keep it as backwards-compatible as possible

yeah, that also would be great

Should I mark the old constructors as deprecated? Since now it takes 4 BarRenderManager.Textures instead of the single texture + offset stuff, i kept the old ones around for backward compatibility

Also im going to test the resource pack functionality now with the changes don't merge yet

No, that doesn't need to be deprecated.
also, please make as draft if it's not done yet :P

Another question: Since you can use multiple textures now, should i make the outline and outline_half fields in the armor json optional and default to the standard outline?

Oh yeah that would be great

I've tested it and it work well, should be ready now

Thanks a lot! I will review and test it myself tomorrow.
if it's works as well, I will merge it and release the new version.

fixed some small things i found while looking over my code

btw i fixed an issue i noticed in the bar rendering code so this PR should fix #55 too

Hii, have you already tested this?

Sorry, I was busy recently 😅
I will test it today

I've planned this release on 1.21.2 release, but there's so many changes with JsonDataLoader class which needs custom codec stuff

authors: RedLime serenyadev

repo: RedLime/DetailArmorBar

license: MIT


text:
Out Of Memory Error On Doc Gen

Describe the bug
When performing build-docs I get a FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
To Reproduce
Steps to reproduce the behavior:
I have placed the OpenAPI Spec here. There are two versions of it. api.yaml is the spec broken up with a bunch of external refs and merged.yaml is the same thing after I ran the redocly merge command on api.yaml

Given this merged.yaml file
Run this command with these arguments... redocly build-docs merged.yaml
See error: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

Expected behavior
I get some docs :D
Logs
redocly build-docs merged.yaml
(node:21925) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
Found undefined and using theme.openapi options
Prerendering docs
<--- Last few GCs --->
[21925:0x130008000]    13582 ms: Scavenge 4045.5 (4124.5) -> 4041.9 (4142.5) MB, 14.46 / 0.00 ms  (average mu = 0.463, current mu = 0.363) allocation failure;
[21925:0x130008000]    15383 ms: Mark-Compact 4055.3 (4142.5) -> 4046.2 (4149.8) MB, 1793.04 / 0.00 ms  (average mu = 0.238, current mu = 0.073) allocation failure; scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0x104fb8080 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
2: 0x10517095c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
3: 0x1053510c8 v8::internal::Heap::stack() [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
4: 0x10534f2d8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
5: 0x1053465c4 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
6: 0x105346e60 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
7: 0x10532ac14 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
8: 0x1056f8d2c v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
9: 0x105a93954 Builtins_CEntry_Return1_ArgvOnStack_NoBuiltinExit [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
10: 0x105a0b648 Builtins_GrowFastSmiOrObjectElements [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
11: 0x10b7aa054
12: 0x10b70e1f4
13: 0x10b7a3478
14: 0x10b5d371c
15: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
16: 0x10b793ce8
17: 0x10b7b1db0
18: 0x10b7ab0e4
19: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
20: 0x10b7b8204
21: 0x10b7b1fe8
22: 0x10b5d376c
23: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
24: 0x10b79dbf0
25: 0x105ab73dc Builtins_ArrayMap [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
26: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
27: 0x10b7b1e80
28: 0x10b5d376c
29: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
30: 0x10b7b22f0
31: 0x10b7ab0e4
32: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
33: 0x10b7b8204
34: 0x10b7b1fe8
35: 0x10b734a48
36: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
37: 0x10b793ce8
38: 0x10b7b1db0
39: 0x10b734a48
40: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
41: 0x10b7b22f0
42: 0x10b734a48
43: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
44: 0x10b70aad8
45: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
46: 0x10b7b8204
47: 0x10b7b1fe8
48: 0x10b734a48
49: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
50: 0x10b793ce8
51: 0x10b7b1db0
52: 0x10b734a48
53: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
54: 0x10b70aad8
55: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
56: 0x10b7a2498
57: 0x105ab6aac Builtins_ArrayMapLoopContinuation [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
58: 0x105ab5e98 Builtins_ArrayMapLoopLazyDeoptContinuation [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
59: 0x105a09a80 Builtins_InterpreterEnterAtNextBytecode [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
60: 0x10b798014
61: 0x10b738904
62: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
63: 0x10b793ce8
64: 0x10b797f3c
65: 0x10b738904
66: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
67: 0x10b72a0b8
68: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
69: 0x10b728ea0
70: 0x105ab73dc Builtins_ArrayMap [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
71: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
72: 0x10b7091bc
73: 0x10b5d376c
74: 0x105a0971c Builtins_InterpreterPushArgsThenFastConstructFunction [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
75: 0x105b6470c Builtins_ConstructHandler [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
76: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
77: 0x105ab73dc Builtins_ArrayMap [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
78: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
79: 0x10b709060
80: 0x10b5d376c
81: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
82: 0x10b709520
83: 0x10b5d376c
84: 0x105a05a48 construct_stub_create_deopt_addr [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
85: 0x10b70aad8
86: 0x105a0971c Builtins_InterpreterPushArgsThenFastConstructFunction [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
87: 0x105b6470c Builtins_ConstructHandler [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
88: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
89: 0x105ab73dc Builtins_ArrayMap [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
90: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
91: 0x10b7091bc
92: 0x10b5d376c
93: 0x105a0971c Builtins_InterpreterPushArgsThenFastConstructFunction [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
94: 0x105b6470c Builtins_ConstructHandler [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
95: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
96: 0x105a0971c Builtins_InterpreterPushArgsThenFastConstructFunction [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
97: 0x105b6470c Builtins_ConstructHandler [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
98: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
99: 0x105ab73dc Builtins_ArrayMap [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
100: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
101: 0x105a0971c Builtins_InterpreterPushArgsThenFastConstructFunction [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
102: 0x105b6470c Builtins_ConstructHandler [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
103: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
104: 0x105a0971c Builtins_InterpreterPushArgsThenFastConstructFunction [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
105: 0x105b6470c Builtins_ConstructHandler [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
106: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
107: 0x105ab73dc Builtins_ArrayMap [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
108: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
109: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
110: 0x105a15b88 Builtins_LoadIC_NoFeedback [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
111: 0x105b58fdc Builtins_GetNamedPropertyHandler [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
112: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
113: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
114: 0x10b6b5bfc
115: 0x10b6a7f34
116: 0x10b6afd78
117: 0x10b694118
118: 0x10b6b5488
119: 0x10b697a84
120: 0x10b6b5b14
121: 0x10b6a7f34
122: 0x10b6afd78
123: 0x10b6baca8
124: 0x10b6baf0c
125: 0x10b6b5414
126: 0x10b6a7f34
127: 0x10b6afd78
128: 0x10b6b00c4
129: 0x10b6afbb8
130: 0x10b6b5530
131: 0x10b6a7f34
132: 0x10b6afd78
133: 0x10b6af014
134: 0x10b6b5a94
135: 0x10b6a7f34
136: 0x10b6afd78
137: 0x10b6b00c4
138: 0x10b6a9af4
139: 0x10b6a829c
140: 0x10b6afd78
141: 0x10b6b5710
142: 0x10b6a7f34
143: 0x10b6afd78
144: 0x10b6baca8
145: 0x10b6baf0c
146: 0x10b6b5414
147: 0x10b6a7f34
148: 0x10b6afd78
149: 0x10b6b00c4
150: 0x10b6a9af4
151: 0x10b6a829c
152: 0x10b6afd78
153: 0x10b6baca8
154: 0x10b6baf0c
155: 0x10b6b5414
156: 0x10b6a7f34
157: 0x10b6afd78
158: 0x10b6b00c4
159: 0x10b6a9af4
160: 0x10b6a829c
161: 0x10b6afd78
162: 0x10b6b5710
163: 0x10b6a7f34
164: 0x10b6afd78
165: 0x10b6baca8
166: 0x10b6baf0c
167: 0x10b6b5414
168: 0x10b6a7f34
169: 0x10b6afd78
170: 0x10b6b00c4
171: 0x10b6a9af4
172: 0x10b6a829c
173: 0x10b6afd78
174: 0x10b6baca8
175: 0x10b6baf0c
176: 0x10b6b5414
177: 0x10b6a7f34
178: 0x10b6afd78
179: 0x10b6b00c4
180: 0x10b6a9af4
181: 0x10b6a829c
182: 0x10b6afd78
183: 0x10b6b00c4
184: 0x10b6afbb8
185: 0x10b6b5530
186: 0x10b6a7f34
187: 0x10b6afd78
188: 0x10b6af014
189: 0x10b6b5a94
190: 0x10b6a7f34
191: 0x10b6afd78
192: 0x10b6b00c4
193: 0x10b6a9af4
194: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
195: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
196: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
197: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
198: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
199: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
200: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
201: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
202: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
203: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
204: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
205: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
206: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
207: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
208: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
209: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
210: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
211: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
212: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
213: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
214: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
215: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
216: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
217: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
218: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
219: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
220: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
221: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
222: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
223: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
224: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
225: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
226: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
227: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
228: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
229: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
230: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
231: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
232: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
233: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
234: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
235: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
236: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
237: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
238: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
239: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
240: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
241: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
242: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
243: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
244: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
245: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
246: 0x105a41e04 Builtins_GeneratorPrototypeNext [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
247: 0x105a08b84 Builtins_InterpreterEntryTrampoline [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
248: 0x105af92d8 Builtins_PromiseFulfillReactionJob [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
249: 0x105a2e654 Builtins_RunMicrotasks [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
250: 0x105a06794 Builtins_JSRunMicrotasksEntry [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
251: 0x1052b2e34 v8::internal::(anonymous namespace)::Invoke(v8::internal::Isolate*, v8::internal::(anonymous namespace)::InvokeParams const&) [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
252: 0x1052b32e4 v8::internal::(anonymous namespace)::InvokeWithTryCatch(v8::internal::Isolate*, v8::internal::(anonymous namespace)::InvokeParams const&) [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
253: 0x1052b3490 v8::internal::Execution::TryRunMicrotasks(v8::internal::Isolate*, v8::internal::MicrotaskQueue*) [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
254: 0x1052db0a0 v8::internal::MicrotaskQueue::RunMicrotasks(v8::internal::Isolate*) [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
255: 0x1052db83c v8::internal::MicrotaskQueue::PerformCheckpoint(v8::Isolate*) [/Users/me/.nvm/versions/node/v21.7.2/bin/node]
[1]    21925 abort      redocly build-docs merged.yaml
OpenAPI description
Not using any custom config file
Redocly Version(s)
1.11.0
Node.js Version(s)
v21.7.2

It looks similar to https://github.com/Redocly/redoc/issues/2474. Transferring to the Redoc repository.

source: gharchive/issue

authors: ryber tatomyr

repo: Redocly/redocly-cli


text:
Escape filename special characters

Paths with " " white spaces or any other special character will generate invalid types at

project\.svelte-kit\types\src\sveltekit-zero-api.d.ts

To fix this:

project\node_modules\sveltekit-zero-api\utils\string.js > invalidCharacters (array)

Add " " white space

Alternative: use npm patch
project\patches\sveltekit-zero-api+0.11.15.patch
diff --git a/node_modules/sveltekit-zero-api/utils/string.js b/node_modules/sveltekit-zero-api/utils/string.js
index 41d8586..d3e61f4 100644
--- a/node_modules/sveltekit-zero-api/utils/string.js
+++ b/node_modules/sveltekit-zero-api/utils/string.js
@@ -1,4 +1,4 @@
-const invalidCharacters = ['[', '/', '\\', ']', '-', ':', '.', '+', '(', ')'];
+const invalidCharacters = ['[', '/', '\\', ']', '-', ':', '.', '+', '(', ')', ' '];
 /** Replaces `[` `/` `\` `]` `-` `:` `.` with `_` */
 export const toValidVariable = (name = '') => name.replaceAll(new RegExp(invalidCharacters.map(m => '\\' + m).join('|'), 'g'), '_');
 /** When importing files: We don't add `.ts` in the import-statement */

Paths with " " white spaces or any other special character will generate invalid types at

project.svelte-kit\types\src\sveltekit-zero-api.d.ts

To fix this:

project\node_modules\sveltekit-zero-api\utils\string.js > invalidCharacters (array)

Add " " white space

Alternative: use npm patch project\patches\sveltekit-zero-api+0.11.15.patch
diff --git a/node_modules/sveltekit-zero-api/utils/string.js b/node_modules/sveltekit-zero-api/utils/string.js
index 41d8586..d3e61f4 100644
--- a/node_modules/sveltekit-zero-api/utils/string.js
+++ b/node_modules/sveltekit-zero-api/utils/string.js
@@ -1,4 +1,4 @@
-const invalidCharacters = ['[', '/', '\\', ']', '-', ':', '.', '+', '(', ')'];
+const invalidCharacters = ['[', '/', '\\', ']', '-', ':', '.', '+', '(', ')', ' '];
 /** Replaces `[` `/` `\` `]` `-` `:` `.` with `_` */
 export const toValidVariable = (name = '') => name.replaceAll(new RegExp(invalidCharacters.map(m => '\\' + m).join('|'), 'g'), '_');
 /** When importing files: We don't add `.ts` in the import-statement */

Thank you! https://github.com/Refzlund/sveltekit-zero-api/commit/e4ca03619c21667dd6e589ecf13b15883e1d6771

authors: Refzlund kauderk

repo: Refzlund/sveltekit-zero-api


text:
When plex dies PlexAutoLanguages is frozen forever.

So I'm getting this error sometimes when Plex connection times out:
2023-08-31 20:43:45,797 [WARNING] The Plex server closed the websocket connection
2023-08-31 20:43:45,838 [ERROR] Unable to process timeline
  File "/app/plex_auto_languages/plex_alert_handler.py", line 66, in _process_alerts
    alert.process(self._plex)
  File "/app/plex_auto_languages/alerts/timeline.py", line 52, in process
    item = plex.fetch_item(self.item_id)
  File "/app/plex_auto_languages/plex_server.py", line 57, in fetch_item
    return self._plex.fetchItem(item_id)
  File "/usr/local/lib/python3.8/site-packages/plexapi/base.py", line 295, in fetchItem
    return self.fetchItems(ekey, cls, **kwargs)[0]
  File "/usr/local/lib/python3.8/site-packages/plexapi/base.py", line 243, in fetchItems
    data = self._server.query(ekey, headers=headers)
  File "/usr/local/lib/python3.8/site-packages/plexapi/server.py", line 756, in query
    raise BadRequest(message)
</html>nter>nginx/1.22.1</center>/center>d>eway;

The only way to fix it is to issue a docker restart container command.

If you use docker you could do a health check on Plex and if there's no response or it responds with exit code 1 autoheal will restart the container.

Just make sure to add "autoheal=true" label to pal container

Just make sure to add "autoheal=true" label to pal container

how to add this in docker compose please ?

If you use docker you could do a health check on Plex and if there's no response or it responds with exit code 1 autoheal will restart the container.

kindly how to add it to docker compose health check , will u please write it in order to copy and paste it to my docker compose file ?

Already an issue for this problem: https://github.com/RemiRigal/Plex-Auto-Languages/issues/56

repo: RemiRigal/Plex-Auto-Languages


text:
Non-flux condition doesn't work

The solution yields nan when non flux condition is put on one of the sides

Found the problem. It comes from the fact that we split u into 4 sub-solutions but don't solve the fourth one.

repo: RemiTheWarrior/Ttrap


text:
Fix "Check for Updates" functionality

I noticed that a release candidate for version 2.0.0 is available, but I was using an alpha version and discovered that the "Check for updates" feature isn't functioning as expected. It should notify users of new versions.

@pmusolino this is intended, because until release, things are change fast. As 2.0.0 is not yet a 'release' version, it is not available from the updater. When 2.0.0 is finally released, it should be available via the updater for all previous versions, including beta and RC (ETA is this week).
Since it's not a real issue, I'll close this now, but thanks for bringing it to my attention!

authors: Renset pmusolino

repo: Renset/macai


text:
Bump magic-string

Closes #183
Care was taken to use versions of Node and NPM as discussed in https://github.com/Rich-Harris/buble/pull/184 for generating minimal changes to package-lock.json.
$ node --version
v10.15.1
$ npm --version
5.8.0

Wow, that's effort. Thanks!

Hooray! Thanks for merging.

authors: adrianheine curran

repo: Rich-Harris/buble


text:
GAS

Is it possible to introduce the gas limit and price of gwei you wanna pay fot the tx?

You can set your own gas parameters by editing the built_tx.

And how can I do It?
Roberto Ortas
El lun, 12 jun 2023, 9:10, Richard A @.***> escribió:

You can set your own gas parameters by editing the built_tx.
—
Reply to this email directly, view it on GitHub
https://github.com/RichardAtCT/1inch_wrapper/issues/16#issuecomment-1586718505,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWSVXJSUD7G2LORQSRJT5DLXK26EVANCNFSM6AAAAAAZCPGGFU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Just edit the dictionary produced by build_tx and change the gas parameters
that you want to change.
On Mon, 12 Jun 2023 at 11:19 AM rob000000 @.***> wrote:

And how can I do It?
Roberto Ortas
El lun, 12 jun 2023, 9:10, Richard A @.***> escribió:

You can set your own gas parameters by editing the built_tx.
—
Reply to this email directly, view it on GitHub
<
https://github.com/RichardAtCT/1inch_wrapper/issues/16#issuecomment-1586718505>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AWSVXJSUD7G2LORQSRJT5DLXK26EVANCNFSM6AAAAAAZCPGGFU>

.
You are receiving this because you authored the thread.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/RichardAtCT/1inch_wrapper/issues/16#issuecomment-1586732311,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHDKB32EURQK7Z3TOGIDOYLXK27HRANCNFSM6AAAAAAZCPGGFU
.
You are receiving this because you commented.Message ID:
@.***>


text:
V12 Compatibility

Hi! Can you please update this to work with V12?

Completed with https://github.com/RichardRobertson/update-your-password/commit/5b486a0131d80347ede6ef73094af156b4764072
Version 2.0.0 available at https://foundryvtt.com/packages/update-your-password

I only did a quick verification that it did show the dialog and update the password so the code hasn't really changed. If you do encounter any errors don't be afraid to reach out.

authors: RichardRobertson cryptiklemur

repo: RichardRobertson/update-your-password

license: ISC


text:
[Bug]程序视频播放页面白屏，并闪退

Bug 描述
在播放视频的时候，即使是同一视频，播放器界面有概率出现白屏现象，但是有声音。再次启动程序有几率解决问题。并有几率闪退（几率很大）
复现步骤

[ 是的] 这个问题是否能在最新版本中复现？（如果你的应用不是最新版，请在 Release 中下载最新版）

重现问题的步骤：

打开应用
进入一个视频
如果白屏

有声音，但是可能闪退（大几率在切换到其他软件的瞬间）

如果没有白屏

播放其他视频之后再次播放上一个视频也可能会白屏，并伴有闪退

环境

应用来源：

[ x ] Github
[ ] 其他来源（请注明来源）

应用版本：2.2111.1.0
系统版本：

[ ] Windows 10 ver.1809 (17763)
[ ] Windows 10 ver.1903 (18362)
[ ] Windows 10 ver.2004 (19041)
[ x ] Windows 11 (22000)
[ ] 内测版本 ({系统版本})

运行设备：

[ x ] 桌面/台式机
[ ] Xbox
[ ] ARM64 设备
[ ] IoT

日志记录
备注

出现了新的问题，在安装完HEVC的解码器之后调整为H.265/HEVC模式之后出现了这个错误：
|System.Exception: 播放失败: DecodingError |  | System.Exception: 请求无效，因为已调用了 Shutdown()。 (Exception from HRESULT: 0xC00D3E85)
2021/11/14 13:46:33.896|Info|
系统信息：10.0.22000.194 | Windows.Desktop | X64
应用信息：2.2111.1.0 | 中文(简体，中国)
只能重启应用来解决

我這邊的情況是刚启动應用時可以完美播放，但是一旦改變視頻的大小（包括調整窗口大小、切換小窗/全窗口/全屏）就會馬上白屏，無論開始還是關閉 HEVC 都會。音頻還會繼續播放。退出視頻再重新播放會變成黑屏。日誌裡沒有報錯。

authors: AkazaRenn hanlongzhifu


text:
Source maps?

I was just poking into devtools but it doesn't seem like sourcemap support is enabled?

Enabled in https://github.com/RickWong/react-isomorphic-starterkit/commit/7cf399c1cfc8b723cfc9c055628511a29474f366#diff-0df7fb3a8ad576181aba79c717230d3dR8

authors: RickWong myndzi

repo: RickWong/react-isomorphic-starterkit


text:
Application references version '13.18.0.0' of 'NSwag.Core' which is lower than the required version '13.19.0.0'.

Hi,
I recently installed the new nswag.consolecore package (v13.19.0).
Running nswag run nswag.json /runtime:Net60 results in an error:
Application references version '13.18.0.0' of 'NSwag.Core' which is lower than the required version '13.19.0.0'.
System.InvalidOperationException: Swagger generation failed with non-zero exit code '4'.
   at NSwag.Commands.Generation.AspNetCore.AspNetCoreToSwaggerCommand.RunAsync(CommandLineProcessor processor, IConsoleHost host) in /_/src/NSwag.Commands/Commands/Generation/AspNetCore/AspNetCoreToOpenApiCommand.cs:line 231
   at NSwag.Commands.NSwagDocumentBase.GenerateSwaggerDocumentAsync() in /_/src/NSwag.Commands/NSwagDocumentBase.cs:line 275
   at NSwag.Commands.NSwagDocument.ExecuteAsync() in /_/src/NSwag.Commands/NSwagDocument.cs:line 81
   at NSwag.Commands.Document.ExecuteDocumentCommand.ExecuteDocumentAsync(IConsoleHost host, String filePath) in /_/src/NSwag.Commands/Commands/Document/ExecuteDocumentCommand.cs:line 85
   at NSwag.Commands.Document.ExecuteDocumentCommand.RunAsync(CommandLineProcessor processor, IConsoleHost host) in /_/src/NSwag.Commands/Commands/Document/ExecuteDocumentCommand.cs:line 32
   at NConsole.CommandLineProcessor.ProcessSingleAsync(String[] args, Object input)
   at NConsole.CommandLineProcessor.ProcessAsync(String[] args, Object input)
   at NSwag.Commands.NSwagCommandProcessor.ProcessAsync(String[] args) in /_/src/NSwag.Commands/NSwagCommandProcessor.cs:line 61

the same. looks like msbuild has strict some dependency here. I still use 13.18.2 to avoid it

Seems to be fixed with version 13.20.0

authors: JanHergenhan vpetrusevici

repo: RicoSuter/NSwag


text:
change how the bubble hides in rg-bubble

Currently the bubble is set to 'opacity:0'; this meant that the bubble will interact with content when not visible. One can, for example, select the text with the mouse with the bubble not visible. Changing to 'display:none' removes the bubble form the DOM until it is activated.

Thanks! Will update dist and publish to npm tonight

authors: gregorypratt rhysallister

repo: RiotGear/rg

license: mit

license_source: bigquery


text:
#761 Fix languages card undefined error

Signed-off-by: Mike Samvelian mike.samvelian@paper.co

The changes in this PR fix issue #761. Repro steps can be found in the issue.
The "value" variable used here can sometimes be undefined causing the page to crash.
Before:

After:

:heavy_check_mark: Checklist

[ ] Added tests for new functionality and regression tests for bug fixes
[x] Added changeset (run yarn changeset in the root)
[x] Screenshots of before and after attached (for UI changes)
[ ] Added or updated documentation (if applicable)

Np!

repo: RoadieHQ/roadie-backstage-plugins


text:
🛑 iot is down

In 5d6cb49, iot (https://iot.sensoro.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: iot is back up in b93836e.

repo: Roarain/upptime


text:
thread safety

Hi,
Have you considered making roaring bitmaps thread safe so they can be read while being updated? With read-write reentrant locks at container level the thread contention would be very low.
I made some tests with external synchronization and the performance penalty is already very low by locking on the whole segment.
Would such contribution be welcomed and if so what would be the best approach? A child implementation synchronizing on protected methods maybe ?

@galderic
Could there be a way to implement this as an optimal API, without penalizing current methods?

Did you mean 'optional' instead of 'optimal'?
On 23 Jul 2015 9:35 pm, "Daniel Lemire" notifications@github.com wrote:

@galderic https://github.com/galderic
Could there be a way to implement this as an optimal API, without
penalizing current methods?
—
Reply to this email directly or view it on GitHub
https://github.com/lemire/RoaringBitmap/issues/35#issuecomment-124278564
.

+1 For making this an optional change. Personally, I would be somewhat adverse to any additional penalties on the current implementation. So if this can be done as an optional ThreadSafe version/API (separate to the current version), that would strongly be my preference.
Also, please correct me if I'm wrong, ( I haven't thought this through completely!), but I'm thinking a thread safe API may need to be explicit (as in ThreadSafeRoaringBitmap ) because it would conflict with the mutable/immutable semantics of memory mapped bitmaps?

@owenkaser  I did. ;-)

@pwebbitrs
I think that ImmutableRoaringBitmap are thread-safe by default, being immutable.
Otherwise, I think it is prudent to avoid adding overhead that everyone must pay when it might benefit only some users. Thus, if it is possible to add new functions calls instead of modifying the existing ones, it might be better.

Nice to see we're all on the same page. In fact @pwebbitrs my approach has been exactly making a ThreadSafeRoaringBitmap extend RoaringBitmap and add support for parallel reads and updates. I only lacked some more visibility on the structural modifications of the highLowContainer array.
I'll try to get my company approval to publish the changes ( it was done during work hours ) so we can continue the discussion. Thanks @lemire @owenkaser  and @pwebbitrs .

@galderic  Looking forward to see your work.

@galderic  Any luck on this front?

@lemire I already have the approval from my company to publish the changes. Current status is that I can check, remove and add bits concurrently by synchronizing in the child class, without much performance penalty. I still have to figure out how to iterate also. I hope I'll be able to commit something near soon.

@galderic  Please consider checking the latest release (0.5.1) as we have added a "runOptimize" function that will improve compression in some cases.

@lemire Ok, no problem. It can be called when holding the write lock for that container. I've committed a first version of ConcurrentBitmap in https://github.com/gpunti/RoaringBitmap/tree/thread-safety.  There's a detailed description of what's been done in the wiki page. I'll be happy to read your opinions.

@gpunti
I am currently traveling but I will review this when I come back.

@gpunti  Sorry for the delay. I think that your approach makes a whole lot of sense.
It would make a great PR.
Two things...

You probably want to sync with the 0.5 release, if you have not done so already.

If not done already, make sure to add some unit tests.

Hi @lemire , yes it's sync with the 0.5 release. There're also unit tests checking that maps perform well under heavy parallelism.
What I'd like to know are the forum's thoughts about how to integrate ConcurrentBitmap with the rest of classes. Should we rewrite and all methods ( serialize, and, or, xor, flip,...)  or just add a method to convert it to a regular RoaringBitmap? Wouldn't three version be a little too much? ( roaring, buffer, concurrent)

@gpunti
It is indeed a software engineering issue.
There are a few distinct strategies...

Add a few methods to existing classes...
Wrap existing classes...
Use inheritance...

You have opted to create an altogether new class which adds a maintenance burden or limits flexibility.
Why did you choose to create a new class?

It's explained in detail in https://github.com/gpunti/RoaringBitmap/wiki.  Extending or using delegation didn't seem a good idea to me because:

(a) Synchronizing highLowContainer externally was very expensive
(b) Inheritance's is a 'is-a' relationship, so a ConcurrentBitmap and a RoaringBitmap should be interoperable with 'and','or','xor', etc...but RoaringBitmap relies on the RoaringArray structure which ConcurrentBitmap doesn't use because of (a). Also the methods are static and cannot be overriden on runtime.

To make the three branches compatible, I think that all operations ( 'and', 'or', 'serialize', ...) should be on different classes (as in FastAggregation) and agnostic on how the containers are stored or retrieved So the highLowContainer could be an interface with only four operations like

contains(short hb) : boolean
addContainer(short hb, Container container) : void
removeContainer(short hb) : void
iterator() : Iterator<Container>

In short, have the same abstraction level in the highLowContainer than we have in ImmutableBitmapDataProvider for the containers.
In this way we could have as many different implementation (mapped, thread-safe, ...) as we desired because all of them would be interoperable and any operator ( 'and', 'or', ...) implementation would make no assumptions on how containers are stored.

Extending or using delegation didn't seem a good idea

Seems reasonable.

In short, have the same abstraction level in the highLowContainer than we have in ImmutableBitmapDataProvider for the containers.

We have this level of abstraction already, at least in the buffer package
https://github.com/lemire/RoaringBitmap/blob/master/src/main/java/org/roaringbitmap/buffer/PointableRoaringArray.java
If you look at the code in ImmutableRoaringBitmap, it does not "know" how highLowContainer is implemented, it just calls it through a PointableRoaringArray interface.
We could generalize this approach throughout the code.

That's true on the or() method but in the and() method it makes use of getKeyAtIndex() and advanceUntil() which relies on it being an array. Both of them also construct a MutableRoaringBitmap by getting its getMappeableRoaringArray() again relying on the result being stored in an array of containers.

@gpunti
Right. I do not think that these methods are specific to an array however. You could get the same effect with
https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ConcurrentSkipListMap.html
Which brings another issue. Because you use a ConcurrentHashMap, you do not iterate through the contained values in order. If you were to use a ConcurrentSkipListMap, you would recover a behaviour closer to the original classes (which iterate through the values in sorted order).
Thoughts?

That's a good example. ConcurrentSkipListMap implements a Map. Internally it might use a list also ( as its name suggests) but you cannot access it by index position, only by key or value as any other map.
Regarding the order of elements, it's an interesting question. In fact it does iterate over the values in sorted order because it sorts the list on every container-switch. That's expensive on the iterate() operation, but faster in the add() remove() operations.  I made the assumption that add() and remove() were more important, but actually might not ( I don't know how roaring bitmaps are used by other projects/companies )
I'm trying to figure out how we could operate with bitmaps (and,or,...) regardless of how they are stored. If I found something interesting I'll commit it in my branch for your consideration.

@gpunti

That's a good example. ConcurrentSkipListMap implements a Map. Internally it might use a list also ( as its name suggests) but you cannot access it by index position, only by key or value as any other map.

Right, one would need something different from the PointableRoaringArray.java, more general. I was not implying that it was usable 'as is'.

That's expensive on the iterate() operation, but faster in the add() remove() operations. I made the assumption that add() and remove() were more important, but actually might not ( I don't know how roaring bitmaps are used by other projects/companies )

Typically, one uses a compressed bitmap for data that is queried far more than it is updated. So having a fast "iterate()" is important, I would think.

@gpunti  i didn't find the ConcurrentBitMap in the latest realease which is (0.6) , what's the plan ?

It's implemented and working in a branch. It's not merged in master as I didn't want to introduce a third type of bitmap ( with its own and,or,xor, etc... operations ). If anyone else is interested in concurrent bitmaps, maybe we could revive the discussion on how to unify them in a single  bitmap type, and a single boolean operations set.

@gpunti Looks like your last commit on the forked branch is broken. You may have forgotten to check in the org.roaringbitmap.concurrent.BitmapInterface file.  Actually ran into a use case where this would have come in handy.

Hi @maxdemarzi you are right. I just committed the missing files.

hi guys,
I'm interested whats the status of this topic? I'm getting similar issue like https://github.com/RoaringBitmap/RoaringBitmap/issues/402, but after few days of checking I was not able to catch the thread-safe issue here. Do you know if there will be ThreadSafeRoaringBitMap released some time?

authors: JasonHuangHuster antal-kajzer-epam galderic gpunti lemire maxdemarzi owenkaser pwebbitrs

repo: RoaringBitmap/RoaringBitmap


text:
Running tests on windows

This relates to a previous discussion about the node environment variable.
I've made some headway on this branch so that windows users can run npm run exec-tests and get all the mocha goodies (moved the environment variable into travis - local environments need to specify the variable themselves).
However, nyc still isn't returning successfully. Running npm run cover on a windows machine still generates errors. I'm investigating further... being able to run all the npm scripts without errors will help other people contribute.
I suspect it's the file glob pattern of the --exclude option for nyc. The nyc README says it uses micromatch for file globbing, but perhaps specifying the excludes in the npm script like that is passing it to the shell to parse the file glob, which may or may not work on windows depending on the shell... I'll have to investigate this later (maybe tomorrow). As I thought the single quotes would pass the path string into nyc (so that it can use micromatch)... I'm not really sure, just guessing.
The error I'm currently running into is this:
$ npm run build
  ... output is good ...
$ npm run cover
  ... scripts, tests, etc ...
npm ERR! sequelize-typescript@0.3.1 cover-v4:
  `npm run prepare-test-v4 && nyc --exclude 'lib/models/v3/**/*.js' --all
    --require source-map-support/register mocha test/specs/`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sequelize-typescript@0.3.1 cover-v4 script.

Installing nyc globally and running the nyc part of the command by itself worked fine. Frustrating!
Next thing I might try is messing with quotes/no quotes/other ways of passing options to nyc.

@snewell92 Thank you for raising this. I will assign this issue to you, if it's OK for you.

repo: RobinBuschmann/sequelize-typescript


text:
Cannot set property 'isInitialized' of undefined

Having an association hasmany and belongsto
My first model ---
import sequelize from "../../../sequalise";
import IndustryTags from "../industry-tags/industry-tags.model";

@Table({
    tableName: Tables.TABLE_INDUSTRY_MASTER,
    timestamps: true
})
export default class IndustryMaster extends Model<IndustryMaster> {

    @PrimaryKey
    @Column
    industry_id: number;

    @Column
    industry_name: string;

    @Column
    industry_description: string;

    @Column
    created_by: number;

    @Column
    updated_by: number;

    @HasMany(() => IndustryTags , 'industry_id')
    industry_tag: IndustryTags[];

}

sequelize.addModels([IndustryMaster]);

second model -----
import sequelize from "../../../sequalise";
import IndustryMaster from "../industry-master/industry-master.model";

@Table({
    tableName: Tables.TABLE_INDUSTRY_TAGS,
    timestamps: true
})
export default class IndustryTags extends Model<IndustryTags> {

    @PrimaryKey
    @Column
    tag_id: number;

    @ForeignKey(() => IndustryMaster)
    @Column
    industry_id: number;

    @BelongsTo(() => IndustryMaster)
    industry_master: IndustryMaster;

    @Column
    tag_title: string;

    @Column
    tag_examples: string;

    @Column
    created_by: number;

    @Column
    updated_by: number;
}

sequelize.addModels([IndustryTags]);

Hey @vipulpatel1994, you can't add models in the same file where you define them. Especially if they depend on each other. The model is undefined because of the circular dependency between IndustryTags and IndustryMaster which isn't solved at the time when addModels is called. Best is to add them in the file where you're setting up your sequelize instance. You can also add them by using globs. Hope this helps!

Facing this issue.
// a.model.ts
import {B} from './b.model.ts';
new B();
// b.model.ts
import {A} from './a.model.ts';
new A();
Can you just give me an example of how to overcome this?

Thanks

I assume it solved your issue (If not, just reopen). So this can be closed then.


text:
Migration from tslint to eslint

Tslint is going to be deprecated. Just migrated the project to eslint and fixed the files based on almost the same configuration as before.

Seems good, will check it out! (I somehow completely missed this).

Based on your MR I've created a branch for this. Check out the eslint branch and let me know what you think. I want to play around with it a bit more to make sure I'm happy with the rules before I merge it.

OK, I'm happy with the rules for now I think. If you have time, check it out, otherwise I'll most likely merge it this weekend.

Hello there,
I tried the eslint branch, currently, eslint fails due to the rule import/extensions.
I suggest adding to .eslintrc.json.rules;
    "import/extensions": 0,

here are the errors without that rule:
$ eslint --ext=jsx,js,tsx,ts src

/Users/mauriziocarboni/development/onetime/webpage-analysis-tool/src/renderer/actions/index.ts
  1:31  error  Missing file extension "ts" for "./counterActions"  import/extensions

/Users/mauriziocarboni/development/onetime/webpage-analysis-tool/src/renderer/app.tsx
  6:25  error  Missing file extension "tsx" for "./components/Application"  import/extensions
  7:19  error  Missing file extension "ts" for "./store"                    import/extensions

/Users/mauriziocarboni/development/onetime/webpage-analysis-tool/src/renderer/components/Application.tsx
  1:21  error  Missing file extension "ts" for "react-hot-loader/root"           import/extensions
  4:30  error  Missing file extension "ts" for "../containers/CounterContainer"  import/extensions

/Users/mauriziocarboni/development/onetime/webpage-analysis-tool/src/renderer/containers/CounterContainer.ts
  4:21  error  Missing file extension "tsx" for "../components/Counter"     import/extensions
  5:27  error  Missing file extension "ts" for "../reducers"                import/extensions
  6:53  error  Missing file extension "ts" for "../actions/counterActions"  import/extensions

/Users/mauriziocarboni/development/onetime/webpage-analysis-tool/src/renderer/reducers/counterReducer.ts
  3:53  error  Missing file extension "ts" for "../actions/counterActions"  import/extensions

/Users/mauriziocarboni/development/onetime/webpage-analysis-tool/src/renderer/reducers/index.ts
  3:46  error  Missing file extension "ts" for "./counterReducer"  import/extensions

/Users/mauriziocarboni/development/onetime/webpage-analysis-tool/src/renderer/store/index.ts
  4:40  error  Missing file extension "ts" for "../reducers"  import/extensions

✖ 11 problems (11 errors, 0 warnings)

error Command failed with exit code 1.

it can also be fixed by being specific about the extensions in the import.

@maury91 you're probably not using the package-lock file in that case since the version in there does not have that problem.
Anyway, I've updated the dependencies and added the config you mentioned so should be fine now! Thanks for trying out the eslint branch! Let me know if you prefer it over the tslint branch so I can make it the default in the future.

@kevinlabx thanks for your comment, you can use the eslint branch for now if you want to use ESLint. I'm just waiting for the ESLint environment to become a bit more stable before switching to it permanently. But don't let yourself be stopped by that, the eslint branch works just fine!

@Robinfr
I am currently using ESLint with TS plugins and I have not run into any issues yet. I will let you know if I run into an issue for using ESLint on our project for TS. 🙂

ESLint is now in master #21
If you want to still use tslint you can use the tslint branch.

authors: Robinfr kevinlabx maury91 psyycker

repo: Robinfr/electron-react-typescript


text:
Add method Instance:ResetPropertyToDefault

Changes

Adds the previously missing documentation for ResetPropertyToDefault.

Checks
By submitting your pull request for review, you agree to the following:

[X] This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
[X] I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
[X] To the best of my knowledge, all proposed changes are accurate.

Ah, are we not allowed to add new elements? Welp.
This method is currently working in the Engine. Minimal documentation is expected, thank you.

repo: Roblox/creator-docs


text:
Tagging

Lets you tag rendered Roact instances with Roact.Tag:
local function Test(props)
    return Roact.createElement("Frame", {
        BackgroundColor3 = props.backgroundColor,
        [Roact.Tag] = "Test"
    })
end

Currently needs lemur changes for unit tests to pass.

@tiffany352 mentioned that it would be useful to assign multiple tags to the same instance.
We could accomplish that with a key like Roact.Event:
Roact.createElement("Frame", {
    [Roact.Tag.Foo] = true,
    [Roact.Tag.Bar] = true,
})

We would choose this over a list of tags because:

Diffing lists quickly is difficult
Creating an extra table per render is heavy
Accepting a string or list makes the API more confusing/complicated to implement

authors: AmaranthineCodices LPGhatguy

repo: Roblox/roact


text:
not able to retrieve the name of the device

have been trying a few libraries and I like a lot yours but I had the issue that I am not able to print the name of my device while with other libraries they do.

BlueteethManager.with(this).scanForPeripherals(DEVICE_SCAN_MILLISECONDS, blueteethDevices -> {
// Scan completed, iterate through received devices and log their name/mac address
for (BlueteethDevice device : blueteethDevices) {
if (!TextUtils.isEmpty(device.getBluetoothDevice().getName())) {
Timber.d("David %s - %s", device.getName(), device.getMacAddress());
}
}
});

Hi @DavidBcn , That's very strange, as I use it all the time to get the device name. It should be noted that a mac address should always be present, but you're correct in checking for existence of a device name (since it's not mandatory).
How about just checking the device name?
https://github.com/RobotPajamas/Blueteeth/blob/master/blueteeth-sample/src/main/java/com/robotpajamas/android/blueteeth/DeviceScanListAdapter.java
    BlueteethDevice device = getItem(position);
    holder.deviceName.setText(device.getName());
    holder.deviceMac.setText(device.getMacAddress());

Closing due to inactivity, and an inability to repro.

authors: DavidBcn sureshjoshi

repo: RobotPajamas/Blueteeth


text:
Scrolling does not work in activities that extends "PreferenceActivity"

From lars.ols...@gmail.com on December 28, 2010 14:36:57
What steps will reproduce the problem? 1. Have an app with a Preference activity with many Preferences
2. ScrollDown, ScrollDownList, searchText, clickOnText all fails to scroll in this activity What is the expected output? What do you see instead? Scrolling should work.  This works in 1.9.0 but not in 2.0.2. What version of the product are you using? On what operating system? 2.0.2 Please provide any additional information below.
Original issue: http://code.google.com/p/robotium/issues/detail?id=51

From renasr...@gmail.com on December 28, 2010 22:04:58
Thanks for this. I am not able to reproduce this problem. Would it be possible for you to send me your application?

From renasr...@gmail.com on January 09, 2011 20:50:51
Not reproducable.
Status: Incomplete

From renasr...@gmail.com on January 09, 2011 20:51:06
Status: Invalid

repo: RobotiumTech/robotium


text:
Update Travis config

Updates Travis config as part of CI maintenance. I was getting a bit tripped up by using PORT as a variable, since that variable is also used in deployment. Do I not need to worry about it since it will be overwritten?
The README will need to be updated, but I'll do that in a separate PR as I want to move this forward before finishing setting up deployment on production (and making these changes in pictor).
I know there is an open dependency PR but I decided not to include that fix here, since the most recent version of Django is still using sqlparse 0.4.1.

Regarding the port - the environment variables you set in Travis CI are available here, so you could just target $DJANGO_PORT. Again, I'll update that in Zodiac.

In the case of $DJANGO_PORT, we have that value as specific to each branch for this application, which would mean we would need to set it in this file for Travis to successfully run on other branches?

In the case of $DJANGO_PORT, we have that value as specific to each branch for this application, which would mean we would need to set it in this file for Travis to successfully run on other branches?

Yes, that's right - I would recommend just making that variable apply to all branches (which would mean deleting the two existing variables and re-adding).

authors: bonniegee helrond

repo: RockefellerArchiveCenter/aquila


text:
"Reload" reloads wrong workspace

Search before asking

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

Operating System

[ ] macOS
[X] Windows
[ ] Linux

Operating System Version
Windows 10
It happens on the web browser too?
No, it just happens on the Desktop app
Rocket.Chat Desktop App Version
3.9.13
Rocket.Chat Server Version
6.6.0
Describe the bug
Under certain circumstances, the functionality "View" -> "Reload" reloads the wrong workspace.
How to Reproduce

Set up at least two workspaces in the desktop app.
Open the first one and click "View" -> "Reload". The workspace will be reloaded.
Open the second workspace and click "View" -> "Reload". The workspace will not be reloaded.
Navigate back to the first one and notice that it is being reloaded.

Describe your Expected behavior
In step 3, I would expect the second workspace to be reloaded.
In step 4, I would expect the first workspace to be reloaded.
Anything else
After reloading the first workspace, I did not find any way to reload the second workspace besides restarting the desktop app.
Are you willing to submit a code contribution?

[ ] Yes, I am willing to submit a Pull Request!

Nice catch! Thank you!

authors: jeanfbrito paulchen


text:
[NEW] Adds drag-and-drop on sidebar

@RocketChat/DesktopApp

Closes #214

this feature introduce the option to drag and drop servers on sidebar, it uses localstorage to save it so when you open the app again it should keep the order

@vcapretz can you post a gif showing the feature?

@rodrigok added on the the first comment!

authors: rodrigok vcapretz


text:
Release v1.0.6?

Any chance of a new release to v1.0.6?

I cut one... but because of the github DNS issue.. Its very possible I'll have to come back and fix the release :grin:

authors: alexbrazier geekgonecrazy

repo: RocketChat/hubot-rocketchat


text:
Unturned hosting server issue 3.20.9.1

i am running into an issue when i try to start up my unturned server (just a LAN one hosted through evolve and such)
yesterday en the 2 days before that i had not a single problem hosting the server but i also forgot to save the game in all those instances yesterday however i did save the server and now i have this error :
ArgumentOutOfRangeException: < 0
Parameter name: count - System.IO.FileStream.Read (System.Byte[] array, Int32 offset, Int32 count)
SDG.Unturned.River.readString ()
SDG.Unturned.GroupManager.load ()
SDG.Unturned.GroupManager.onLevelLoaded (Int32 level)
SDG.Unturned.Level+c__Iterator0.MoveNext ()
UnityEngine.SetupCoroutine.InvokeMoveNext (IEnumerator enumerator, IntPtr returnValueAddress)
i personally do not understand this error and therefore am asking for some help out here.

Doesn't follow issue template.
It is also not a rocketmod issue and has been mentioned https://github.com/RocketMod/Rocket/issues/978 and https://github.com/RocketMod/Rocket/issues/971.
Solution is described there and it is to delete groups.dat.
Requesting again this issue to be closed.

authors: FatalityPig persiafighter

repo: RocketMod/Rocket


text:
Reddit Scope property change

Changed private setter on Scope option to allow setting of property to only the level of access you actually need. No need to only allow a specific amount of access or require users to give up access to private messages to use Reddit auth.

There is no need to change the setter from private. You can still access the list to clear it, e.g.
options.Clear();
options.Add("scope");

I guess I don't understand the purpose of having the setter as private, especially seeing as Slack uses the same List for their "scope" and it's marked as a public setter.
    /// <summary>
    ///     Determines the permissions granted from the application to Slack.
    ///     Options include: identify, read, post, client, and/or admin
    /// </summary>
    public IList<string> Scope { get; set; }

It might just be my personal preference, but I'd rather set all the options for the authentication when I create the options object and not have to clear the Scope property and add what I want back in.
So I guess I have 2 questions
1)What is the purpose of having that setter being private?

Why is the Reddit authentication inconsistent with the Slack authentication in terms of private setters.

No specific purpose. That is how all of them are done - except for perhaps a few like the Slack one which you pointed out. I starter with the providers done by MS initially as a base, as that is why they did it, so that is how it happened.

The Slack one is the one which is inconsistent with the rest.

What does the setter being private prevent you from doing? You can still clear the list of scopes.

Basically WITH the private setting you have to do the following
RedditAuthenticationOptions opts = new RedditAuthenticationOptions
        {
            ClientId = System.Configuration.ConfigurationManager.AppSettings["RedditClientID"],
            ClientSecret =   System.Configuration.ConfigurationManager.AppSettings["RedditClientSecret"]
        };
 opts.Scope.clear();
 opts.Scope.add("identity");
 opts.Scope.add("mysubreddits");

With the setter as public you can do:
RedditAuthenticationOptions opts = new RedditAuthenticationOptions
        {
            Scope = new List<string>{"identity","mysubreddits"},
            ClientId = System.Configuration.ConfigurationManager.AppSettings["RedditClientID"],
            ClientSecret = System.Configuration.ConfigurationManager.AppSettings["RedditClientSecret"]
        };

Which seems much cleaner and makes a little more sense to me as then you aren't forced into setting the options to a variable and messing with the Scope that way and you could potentially skip that and jam it into the app.UseRedditAuthentication() if you really wanted to.

I agree with your argument about the code looking cleaner. It looks cleaner to me as well.
I am however not going to change it, as the private setter is consistent with the way the standard MS implementations work. It is even consistent with the way the next generation providers for ASP.NET 5 is working (https://github.com/aspnet/Security/blob/dev/src/Microsoft.AspNet.Authentication.OAuth/OAuthAuthenticationOptions.cs#L92)
Changing it affectively means going back and change it for every single of the 20+ providers. It also means writing a whole lot of extra code over and above that to do null checking everywhere the Scope property is being accessed.
Give all of that, this is not a change I am going to make.

I hadn't really considered the fact that it would have to do null checking in a lot more places, but you are right, that would give you the ability to pass in a null and that is probably why it is private in the first place, so you can be guaranteed it won't be null.
You might want to change the slack one to be consistent though and avoid that null problem, although I'm not familiar with how the slack auth works so it might be unnecessary.
Thanks for your time!

authors: CrustyJew jerriep

repo: RockstarLabs/OwinOAuthProviders


text:
No way to change the category of a channel

There is currently no way I'm aware of to modify the parent_id property of a channel, which is needed to change its category.

for 1.0 no there is no way of doing this but there is in 2.0 so you could upgrade to 2.0beta on nuget or the the mygetfeed also feel free to join the #dotnet_discord-net channel in https://discord.gg/discord-api

Relevant PR #1016, this feature needs be re-implemented, but I haven't gotten around to it, so it's up for picks at the moment.

switching to the 2.0 beta allowed me to change categories, thanks a lot 💖

authors: Still34 TheNoodleMummy axoila


text:
GetMessagesAsync seems to fail when channel message caching is on

I have this command:

    [Command("prune"), IsModerator]

    public async Task Prune(IUserMessage msg, int amount)
    {
        int messagesDeleted = 0;
        var pruneMessage = await msg.Channel.SendMessageAsync("`_Prune in progress, gimme a moment.._`");
        var lastMessageId = pruneMessage.Id;
        try
        {
            var stop = false;
            while (amount > messagesDeleted)
            {
                var messages = (await msg.Channel.GetMessagesAsync(lastMessageId, Direction.Before, 15)).OfType<IUserMessage>().ToList();
                foreach (IUserMessage message in messages)
                {
                    await message.DeleteAsync();
                    messagesDeleted++;
                    if (messagesDeleted >= amount || messages.Count == 0)
                    {
                        stop = true;
                        break;
                    }
                    lastMessageId = messages.Last().Id;
                }
                if (stop || messages.Count == 0)
                    break;
            }
        }
        catch (Exception ex)
        {
            if (ex.Message != "The server responded with error 404 (NotFound): \"Unknown Message\"")
                await msg.Channel.SendMessageAsync("Something derped while trying to delete messages, you're gonna have to do it manually or try again");
        }
        finally
        {
            await pruneMessage.ModifyAsync(x => x.Content = "_Prune completed, this message will self destruct in 5 seconds_");
            Task.Factory.StartNew(async () =>
            {
                await Task.Delay(5000);
                await pruneMessage.DeleteAsync();
            });
        }
    }

This will work fine until the cache is full after which it will ignore any messageId you toss in the method (I think)

Don't make a Prune using Message.DeleteAsync(), use Channel.DeleteMessagesAsync()
Don't download inside a loop, download all that you're going to delete, then delete, as you're pretty much spamming the API

Thank you for the tips, regardless though that is unrelated to the issue at hand

Fixed in beta2

authors: Nensec RogueException khionu


text:
[Paladin] - adding missing translation items

feast tab

Character Sheet Info Roll20 Internal Use only.


text:
Update translation de.json

Update de.json. New translation with conditions etc.

Hi PhilHoffm,
I'd recommend you apply to become a translator on crowdin.com for the Roll20 project for much easier management of translation key updating.  The keys on crowdin get updated to the site every week at the same time character sheets are merged.  Contact team@roll20.net if you would like to become a translator or have any questions.

authors: PhilHoffm Solarswordsman


text:
'playground activate' under zsh fails with "no such option: rcfile"

Attempting to activate a playground when using the zsh shell gives:
/bin/zsh: no such option: rcfile
ERROR: LoadError: failed process: Process(`/bin/zsh --rcfile /Users/rdeits/locomotion/explorations/point-cloud-signed-distance/pkg/zshrc`, ProcessExited(1)) [1]
 in run at /Applications/Julia-0.4.5.app/Contents/Resources/julia/lib/julia/sys.dylib
 in run_shell at /Users/rdeits/.julia/v0.4/Playground/src/activate.jl:61
 in activate at /Users/rdeits/.julia/v0.4/Playground/src/activate.jl:19
 in main at /Users/rdeits/.julia/v0.4/Playground/src/Playground.jl:74
 in main at /Users/rdeits/.julia/v0.4/Playground/src/Playground.jl:41
 in include at /Applications/Julia-0.4.5.app/Contents/Resources/julia/lib/julia/sys.dylib
 in include_from_node1 at /Applications/Julia-0.4.5.app/Contents/Resources/julia/lib/julia/sys.dylib
 in process_options at /Applications/Julia-0.4.5.app/Contents/Resources/julia/lib/julia/sys.dylib
 in _start at /Applications/Julia-0.4.5.app/Contents/Resources/julia/lib/julia/sys.dylib
while loading /Users/rdeits/.playground/bin/playground, in expression starting on line 10

As far as I can tell, there's no easy way to force zsh to use an arbitrary file instead of its .zshrc file. It is possible to overwrite ZDOTDIR, which is where zsh looks for a file named .zshrc, but that may have other consequences since other files are also expected in that location (from man zsh):
$ZDOTDIR/.zshenv
$ZDOTDIR/.zprofile
$ZDOTDIR/.zshrc
$ZDOTDIR/.zlogin
$ZDOTDIR/.zlogout

Perhaps instead of duplicating and appending to the user's base .zshrc file, it would be better not to duplicate the content of that file, but instead just put the playground-specific lines into a file and invoke the shell as:
zsh -c "source /path/to/playground/file; zsh -i"

That's in fact how this was fixed in commit 7ca1b89 on master, I just haven't gotten around to pulling those fixes back into dev.

Great! I imagine this also makes #40 irrelevant as well?

For now we're just special casing zsh as I'd prefer to explicitly pass the rc file whenever possible, but I may change this later as I don't really like special casing either.

It was kind of ugly, but I've synced the fixes from master into dev. Both of your issues should be resolved now.

Awesome, thanks!

authors: Rory-Finnegan rdeits


text:
Draft 2 MD on custom blocks ??

Hello! , thanks for this awesome plugin.
I've noted that the custom conversion is possible on custom entities but in my case I've a custom block that is not present on the EntityMap

How can I include a custom block  in the draftToMarkdown configuration ?

sorry, I've realized that styleItems was the way to go

repo: Rosey/markdown-draft-js


text:
Add Juan Morais to Contributors list

This is my first ever PR!
It was easier than I thought 😄.

Hi  @timrodz, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

authors: Roshanjossey timrodz

repo: Roshanjossey/first-contributions


text:
MARS-105 Greedy Algorithm

What changes were made:
Implemented Greedy Unlimited + Limited (1 pixel only) algorithm
Added getPath() to Algorithm abstract class, with accompanying implementations in all algorithms I can see in dev
Added getHeight() and getWidth() utility functions to terrainMap
What are the relevant JIRA tickets:
MARS-105, kind of MARS-112, though I will keep the latter open for work with A*
How can these changes be tested(test #?):
Several tests added, see prefix "testGreedy" in AppTest
Comments:
Includes diagonal movement, as discussed in meeting

@sapols
Based on your comments, my plans are to remove the TerminalOutput changes and figure something out for getPath() before findPath() for recursive A*. It looks like most of the concerns are with the implementation of getPath(), but those comments warrant discussion, so I am holding off on those for now.

repo: RossBlassingame/JPL-CUSeniorProjects


text:
Can't build: "ant" can't find org.jdesktop.jxlayer and other packages

Can't build: "ant" can't find org.jdesktop.jxlayer and other packages
See attachment
screenlog.0.txt

You have to specify which is the lib folder:
ant -lib lib


text:
[Doc] Modules Update

This pull request has automatically created by PinpointAutoBot
Items : [spring-rabbit] has been updated

Codecov Report

Merging #40 into master will decrease coverage by 0.07%.
The diff coverage is 40.84%.

@@            Coverage Diff             @@
##           master      #40      +/-   ##
==========================================
- Coverage   40.32%   40.24%   -0.08%
==========================================
  Files        2678     2684       +6
  Lines       80819    80989     +170
  Branches    10806    10859      +53
==========================================
+ Hits        32592    32597       +5
- Misses      45323    45471     +148
- Partials     2904     2921      +17

Impacted Files
Coverage Δ

...t/profiler/util/ApplicationServerTypeResolver.java
0% <ø> (-78.79%)
:arrow_down:

...otstrap/resolver/condition/MainClassCondition.java
83.72% <ø> (-0.73%)
:arrow_down:

...navercorp/pinpoint/plugin/tomcat/TomcatConfig.java
28.88% <ø> (-6.97%)
:arrow_down:

...vercorp/pinpoint/profiler/plugin/PluginConfig.java
85% <ø> (ø)
:arrow_up:

.../resolver/ApplicationServerTypePluginResolver.java
0% <ø> (-47.37%)
:arrow_down:

...m/navercorp/pinpoint/plugin/jboss/JbossConfig.java
51.06% <ø> (+5.96%)
:arrow_up:

...inpoint/plugin/spring/boot/SpringBootDetector.java
0% <0%> (ø)
:arrow_up:

...orp/pinpoint/common/plugin/ServerPluginLoader.java
66.66% <0%> (+10.66%)
:arrow_up:

...m/navercorp/pinpoint/plugin/vertx/VertxPlugin.java
0% <0%> (ø)
:arrow_up:

.../pinpoint/plugin/spring/boot/SpringBootPlugin.java
0% <0%> (ø)
:arrow_up:

... and 69 more

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 e7ea8cf...172f428. Read the comment docs.

authors: RoySRose codecov-io

repo: RoySRose/pinpoint


text:
Compatibility detection between serialized models after version upgrades

Is your feature request related to a problem? Please describe.
Dependabot sent us https://github.com/nextcloud/mail/pull/3610 and I'm a bit hesitant integrating this change because our installations have existing models persisted and it's not obvious for a user of the library whether those have to be discarded or can be reused (class props are still the same in the new version).
For some environments it might be OK to "just" retrain the model before the new code goes into production, but it's not really the case for how we use rubix-ml in Nextcloud Mail. The model is trained in the background, for each user's account. If we discard the model there is a time window where no classification is possible. Some processes rely on this, though, so it would give sub-par UX at best.
Describe the solution you'd like
I think it should be technically feasible to have a version number or similar as property of each model. This number is touched (incremented) every time the data structure changes. Then if php successfully deserialized the class you can compare the restored value with the default of a new class. If there's a mismatch, you throw.
Describe alternatives you've considered
n/a
Additional context
I guess this is somewhat related to https://github.com/RubixML/RubixML/issues/108 and https://github.com/RubixML/RubixML/issues/58

Is "detection" enough to solve your issue @ChristophWurst?

@ChristophWurst @simplechris I like the idea of versioning persistable objects, however, if the serilaized data and class property definitions don't match up PHP will throw an exception upon calling unserialize(). We can catch this exception, however, we cannot read the version property in this case because we don't have an instance of the persistable object yet because it failed to deserialize. Is this going to be a problem?

If php can't even unserialize the string then we are out of luck anyway. I'm more worried about the nifty cases where for example a property was nullable before but in the new version of the code it's always assigned a value. Php will (I think) happily unserialize. The resulting object is semantically faulty. Does that make sense?
I did this quick test in two interactive shells:
Shell 1
php > class A {
php {   private $a;
php {   private $b;
php {
php {   public function __construct() {
php {     $this->a = 3;
php {   }
php { }
php >
php > $a1 = new A();
php > echo serialize($a1);
O:1:"A":2:{s:4:"Aa";i:3;s:4:"Ab";N;}
php > file_put_contents('/tmp/a.ser', serialize($a1));

Shell 2
php > class A {
php {   private $a;
php {   private $b;
php {
php {   public function __construct() {
php {     $this->a = 4;
php {     $this->b = 2;
php {   }
php { }
php > $a1 = new A();
php > echo serialize($a1);
O:1:"A":2:{s:4:"Aa";i:4;s:4:"Ab";i:2;}
php > $a1ser = file_get_contents('/tmp/a.ser');
php > echo $a1ser;
O:1:"A":2:{s:4:"Aa";i:3;s:4:"Ab";N;}
php > $a1orig = unserialize($a1ser);
php > var_dump($a1orig);
php shell code:1:
class A#2 (2) {
  private $a =>
  int(3)
  private $b =>
  NULL
}

As you can see, php happily unserializes the object because no new properties were added. Even worse, I tried with a third shell to see what happens if you add a new property:
php > class A {
php {   private $a;
php {   private $b;
php {   private $c;
php { }
php > $a1ser = file_get_contents('/tmp/a.ser');
php > $a1orig = unserialize($a1ser);
php > var_dump($a1orig);
php shell code:1:
class A#1 (3) {
  private $a =>
  int(3)
  private $b =>
  NULL
  private $c =>
  NULL
}

So php is quite "flexible" and will just set the new properties to null. There was not an exception because of a mismatching property.

@ChristophWurst yup makes sense, thanks for the information. I've had similar results. To me, it seems like the best solution is one implemented in the PHP core no?
As @simplechris mentioend, we are working on revamping the entire persistence subsystem for version 1.0.0. Maybe we can come up with something if we put our heads together.

What if we put a $version property on every Persistable object and compared that to a class constant that we increment everytime the class definition changes? Perhaps this could be done using the new PHP 7.4 __unserialize() magic method. If there is no $version property (it's null as I believe this would be the behavior or unserializing an object without the version property) then we can assume the version is 0.
Any thoughts?

Also, this is sorta related. In this commit https://github.com/RubixML/RubixML/commit/59bafb781dd70e03d16c2771551c75c8ef287fb2 we now catch missing class definitions (missing, not semantically faulty like you say) and throw a more helpful exception in both Native and Igbinary serializers.

@ChristophWurst A prototype solution to this can be found in https://github.com/RubixML/ML/pull/158
The idea is a custom file file format with metadata and automatically tracking class revisions. Your early feedback would be appreciated!

@ChristophWurst A prototype solution to this can be found in https://github.com/RubixML/ML/pull/158
The idea is a custom file file format with metadata and automatically tracking class revisions. Your early feedback would be appreciated!

authors: ChristophWurst andrewdalpino

repo: RubixML/ML


text:
anu 在微信小程序上支持拓展运算符吗

anu 在微信小程序上支持拓展运算符吗
<Component {...props}/>

支持，但是在自定义组件的转译，我们知道props里面有什么东西

所以是需要写成这样?
<Component {...props} onEvent1={handleEvent1} onEvent2={handleEvent2} />

有例子吗？我在官网的文档和注意事项没看到相关的

不要在JSX里面写，其他地方可以

不要在 JSX 里面写是什么意思，就是在 JSX 里不支持，其它地方支持的意思吗

是的

authors: Manweill RubyLouvre kominsan

repo: RubyLouvre/anu


text:
MAAS-2979 | Take latest values of graphite metrics

Fix bug when the oldest values were taken instead of the newest.

Coverage remained the same at 90.956% when pulling f00fe1c6479d6048d224037018f9ee2ae9f10194 on MAAS-2979-info-about-data-series-in-alert into f251b6fb238a354ab38a4dc650f5d27f951a2dbc on develop.

Coverage remained the same at 90.956% when pulling e43ddcc19ac6da34656df6cfc62a2d3013fd1339 on MAAS-2979-info-about-data-series-in-alert into f251b6fb238a354ab38a4dc650f5d27f951a2dbc on develop.

Coverage remained the same at 90.956% when pulling e43ddcc19ac6da34656df6cfc62a2d3013fd1339 on MAAS-2979-info-about-data-series-in-alert into f251b6fb238a354ab38a4dc650f5d27f951a2dbc on develop.

Coverage remained the same at 90.956% when pulling e43ddcc19ac6da34656df6cfc62a2d3013fd1339 on MAAS-2979-info-about-data-series-in-alert into f251b6fb238a354ab38a4dc650f5d27f951a2dbc on develop.

Coverage remained the same at 90.956% when pulling e43ddcc19ac6da34656df6cfc62a2d3013fd1339 on MAAS-2979-info-about-data-series-in-alert into f251b6fb238a354ab38a4dc650f5d27f951a2dbc on develop.

Coverage increased (+0.02%) to 90.976% when pulling ea43ed199fc4aab6d5646d9ade9447578b7c3599 on MAAS-2979-info-about-data-series-in-alert into f251b6fb238a354ab38a4dc650f5d27f951a2dbc on develop.

authors: coveralls tetianakh

repo: RulersOfAsgard/ALAMO-worker


text:
部署成功了，点击登录没反应

你的解决了吗？我的也是

repo: Runner-Go-Team/RunnerGo


text:
nsp check

(+) 2 vulnerabilities found
┌───────────────┬─────────────────────────────────────────────────────────────────┐
│               │ Regular Expression Denial of Service                            │
├───────────────┼─────────────────────────────────────────────────────────────────┤
│ Name          │ minimatch                                                       │
├───────────────┼─────────────────────────────────────────────────────────────────┤
│ Installed     │ 2.0.10                                                          │
├───────────────┼─────────────────────────────────────────────────────────────────┤
│ Vulnerable    │ <=3.0.1                                                         │
├───────────────┼─────────────────────────────────────────────────────────────────┤
│ Patched       │ >=3.0.2                                                         │
├───────────────┼─────────────────────────────────────────────────────────────────┤
│ Path          │ myApp@1.2.0 > appmetrics@1.0.12 > tap@5.7.3 > nyc@… │
├───────────────┼─────────────────────────────────────────────────────────────────┤
│ More Info     │ https://nodesecurity.io/advisories/118                          │
└───────────────┴─────────────────────────────────────────────────────────────────┘
┌───────────────┬─────────────────────────────────────────────────────────────────┐
│               │ Regular Expression Denial of Service                            │
├───────────────┼─────────────────────────────────────────────────────────────────┤
│ Name          │ hawk                                                            │
├───────────────┼─────────────────────────────────────────────────────────────────┤
│ Installed     │ 1.1.1                                                           │
├───────────────┼─────────────────────────────────────────────────────────────────┤
│ Vulnerable    │ < 3.1.3  || >= 4.0.0 <4.1.1                                     │
├───────────────┼─────────────────────────────────────────────────────────────────┤
│ Patched       │ >=3.1.3 < 4.0.0 || >=4.1.1                                      │
├───────────────┼─────────────────────────────────────────────────────────────────┤
│ Path          │ myApp@1.2.0 > appmetrics@1.0.12 > tap@5.7.3 > code… │
├───────────────┼─────────────────────────────────────────────────────────────────┤
│ More Info     │ https://nodesecurity.io/advisories/77                           │
└───────────────┴─────────────────────────────────────────────────────────────────┘```

I guess updating the tap dependency would fix this...

@majgis Can this be closed now that that tap dependancy has been updated ?

I ran nsp check and found no issues.  Thank you!

authors: busybeaver majgis tobespc

repo: RuntimeTools/appmetrics


text:
加上定时开抢的功能会比较好

脚本的源码设计是到选房时间（11:00）需要手动启动，但是现在用脚本的人很多，靠人的手速很难在 11:00 过1秒抢到。
https://github.com/Runtus/dormitory-uestc/blob/9765a3207cd3d927ff912ac3a11d941f267acd80/src/index.ts#L121C1-L121C1
类似 index.ts 中修改成这样，亲测给四个人抢到了，基本挂在后台等结果。
const main = async () => {
  let isBooked = false; // 添加一个标志，表示是否已经抢房成功
  let loopCount = 0; // 添加一个计数器，表示循环的次数
  while(!isBooked){
    loopCount++; // 每次循环，计数器加一
    console.log(`这是第${loopCount}次尝试抢房`); // 在终端打印出循环的次数
    const res = await register()
    if (res.hasRegister) {
      for (let house of config.houses) {
        console.log(`正在抢房 ${house.name} 号`)
        const data = await checkRoom(house.id)
        if (data.isNull) { // 空的，进行选房请求
          console.log('房源为空，开始抢房')
          const promises = data.bed.map(item => (
            got(POST_URL_CHOOSEROOM, {
              method: 'post',
              headers: {
                ...headers,
                Cookie: cookies.find(cookie => cookie.name === item.name).cookie
              },
              form: {
                "bed_id": item.bed_id,
                "choose_bed_auth_counsellor_id": (() => {
                  console.log(item)
                  return item.choose_bed_auth_counsellor_id
                })()
              }
            }).json<{flag: boolean, type: number, data: number, message: string}>()
          ))
          const result = await Promise.all(promises)
          console.log(result)
          if (result.every(item => item.type === 0)) {
            console.log(`恭喜！抢房成功，房号为:${house.name}`)
            isBooked = true;
          } else if (result.every(item => item.type === 1)){
            console.log(`你们貌似抢过房了`)
            isBooked = true;
          } else {
            console.log(`疑似撞车，请登录检查`)
          }
          break;
        } else {
          console.log(`${house.name}房间已有人入驻，开始对下一房间进行抢房操作`)
          continue
        }
      }
      if (!isBooked) {
        console.log('你预定的房间已经没有空位了，请重新进行配置');
      }
    } else {
      console.log('loginID没有注册成功，请重复尝试')
    }
    await new Promise(resolve => setTimeout(resolve, 1000)); // 等待1秒
  }
}

const scheduleStart = () => {
  const targetTime = config.start_time.hour * 60 * 60 + config.start_time.minute * 60 + config.start_time.second; // 11:30:20 in seconds
  console.log(`目标时间: ${config.start_time.hour}:${config.start_time.minute}:${config.start_time.second}`);

  const printIntervalId = setInterval(() => {
    const now = new Date();
    console.log(`现在时间: ${now.getHours()}:${now.getMinutes()}:${now.getSeconds()}`);
  }, 10000); // Print every 30 seconds

  const intervalId = setInterval(() => {
      const now = new Date();
      const currentTime = now.getHours() * 60 * 60 + now.getMinutes() * 60 + now.getSeconds();
      if (currentTime >= targetTime) {
          clearInterval(printIntervalId);
          clearInterval(intervalId);
          console.log(`开始抢房时间: ${now.getHours()}:${now.getMinutes()}:${now.getSeconds()}`);
          main();
      }
  }, 1000);
}

scheduleStart();

Get√，感谢建议，确实这样做会更好，手动触发风险性还是有些高的。

已完成代码和readme的更新。Related Commit
您其实可以直接提一个PR的：）

repo: Runtus/dormitory-uestc


text:
Reparented X11 windows don't receive keyboard events when not hovering over them

An X11 window created using Windows::open_parented() will not receive keyboard input, and as a consequence of that, keyboard input for modifiers, when not hovering over the window. This makes sense as the window is not requesting input focus, but it does mean that weird things happen when you combine this with dragging gestures. When you start a dragging gesture, hold down shift, move your mouse cursor outside of the window, release shift, and then WIndowHandler won't notice shift being released, and every subsequent interaction would behave as if shift was still pressed. You can cry this out with this example using the patched baseview from #115 and Carla:
NOTE: This example has been updated with the patches from #117, so the issue no longer exists on the latest version.
git clone git@github.com:robbert-vdh/nih-plug.git
cd nih-plug
cargo xtask bundle gain_gui --bundle-vst3 && carla-single vst3 target/gain_gui.vst3

Note that this won't happen in Bitwig, as in Bitwig the host's parent window grabs focus itself and then forwards most keyboard events (except for Space and a couple other keys) to the child window.
Also, because modifiers are not sent as part of the mouse move/click events, the modifiers will be ignored when you Shift+click on a plugin GUI directly after opening the window in Bitwig because the click event arrives before the keyboard even (of it doesn't get sent at all, I'd need to check).
The potential ways to fix this would be to always grab keyboard focus, or to add modifiers to mouse move and click events. The last one is the least invasive, and I think this information is part of those events on every platform.

To add to this, I feel like the simplest way around this would be to add grab_focus() and release_focus() methods to WindowHandle, and to also add FocusIn/FocusGrabbed and FocusOut/FocusReleased events that lets the window know if received or lost focus so it can keep track if its focus state.

repo: RustAudio/baseview