text:
Elbow Injuries Formatting Challenges

@andyglittle what are you thinking for reformatting this card? It is so heavy on the table.
I the past I've turned the table header into list items to flatten it out:
|         | header 1 | header 2 | header 3 |
|-----|----------|----------|----------|
| one | value       | value       | value      |
| two | value       | value       | value      |

## One
- header 1: value
- header 2: value
- header 3: value

## Two
- header 1: value
- header 2: value
- header 3: value

I'm not sure that strategy works for this card.

@michellealiem suggested maybe breaking this card up into smaller cards. As she points out, so much dense information isn't really "in a few words".
Might make sense to break it up.

I broke up the knee injuries card, and then made one main card to link to the other cards.
Check out this pull request to see how I did it:
#131

Starting to break up the elbow card now. In term of the images, what are
you using to crop the images from the current PDF Card to the github?
Andy
On Tue, Mar 28, 2017 at 3:11 PM, Jeremy Voros notifications@github.com
wrote:

I broke up the knee injuries card, and then made one main card to link to
the other cards.
Check out this pull request to see how I did it:
#131 https://github.com/aliemteam/aliemcards/pull/131
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aliemteam/aliemcards/issues/123#issuecomment-289874250,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYVVuQQHD0Seeoc_tsu3BaJwPJiZ1i6cks5rqVt-gaJpZM4MmG6U
.

I'm just using the screenshot tool on Mac to create an image.
There is probably something similar on Windows.
What are you using?
On Tue, Mar 28, 2017 at 20:23 andyglittle notifications@github.com wrote:

Starting to break up the elbow card now. In term of the images, what are
you using to crop the images from the current PDF Card to the github?
Andy
On Tue, Mar 28, 2017 at 3:11 PM, Jeremy Voros notifications@github.com
wrote:

I broke up the knee injuries card, and then made one main card to link to
the other cards.
Check out this pull request to see how I did it:
#131 https://github.com/aliemteam/aliemcards/pull/131
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/aliemteam/aliemcards/issues/123#issuecomment-289874250
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AYVVuQQHD0Seeoc_tsu3BaJwPJiZ1i6cks5rqVt-gaJpZM4MmG6U
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aliemteam/aliemcards/issues/123#issuecomment-289962519,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACVxJrWDEkvy4JMpKW-6kdTAAe_miOErks5rqcCjgaJpZM4MmG6U
.

Mac, I'll give that a try
On Tue, Mar 28, 2017 at 11:01 PM, Jeremy Voros notifications@github.com
wrote:

I'm just using the screenshot tool on Mac to create an image.
There is probably something similar on Windows.
What are you using?
On Tue, Mar 28, 2017 at 20:23 andyglittle notifications@github.com
wrote:

Starting to break up the elbow card now. In term of the images, what are
you using to crop the images from the current PDF Card to the github?
Andy
On Tue, Mar 28, 2017 at 3:11 PM, Jeremy Voros notifications@github.com
wrote:

I broke up the knee injuries card, and then made one main card to link
to
the other cards.
Check out this pull request to see how I did it:
#131 https://github.com/aliemteam/aliemcards/pull/131
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/aliemteam/aliemcards/issues/123#
issuecomment-289874250
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AYVVuQQHD0Seeoc_
tsu3BaJwPJiZ1i6cks5rqVt-gaJpZM4MmG6U
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/aliemteam/aliemcards/issues/123#
issuecomment-289962519>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACVxJrWDEkvy4JMpKW-
6kdTAAe_miOErks5rqcCjgaJpZM4MmG6U>

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aliemteam/aliemcards/issues/123#issuecomment-289967809,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYVVuVIlD_g9kM_6M5SHWgogqtIK7o_fks5rqcmWgaJpZM4MmG6U
.

Shift + Command + 4 will get you a crop box you can use to get just the
parts you want.
On Tue, Mar 28, 2017 at 21:15 andyglittle notifications@github.com wrote:

Mac, I'll give that a try
On Tue, Mar 28, 2017 at 11:01 PM, Jeremy Voros notifications@github.com
wrote:

I'm just using the screenshot tool on Mac to create an image.
There is probably something similar on Windows.
What are you using?
On Tue, Mar 28, 2017 at 20:23 andyglittle notifications@github.com
wrote:

Starting to break up the elbow card now. In term of the images, what
are
you using to crop the images from the current PDF Card to the github?
Andy
On Tue, Mar 28, 2017 at 3:11 PM, Jeremy Voros <
notifications@github.com>
wrote:

I broke up the knee injuries card, and then made one main card to
link
to
the other cards.
Check out this pull request to see how I did it:
#131 https://github.com/aliemteam/aliemcards/pull/131
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/aliemteam/aliemcards/issues/123#
issuecomment-289874250
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AYVVuQQHD0Seeoc_
tsu3BaJwPJiZ1i6cks5rqVt-gaJpZM4MmG6U
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/aliemteam/aliemcards/issues/123#
issuecomment-289962519>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACVxJrWDEkvy4JMpKW-
6kdTAAe_miOErks5rqcCjgaJpZM4MmG6U>

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/aliemteam/aliemcards/issues/123#issuecomment-289967809
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AYVVuVIlD_g9kM_6M5SHWgogqtIK7o_fks5rqcmWgaJpZM4MmG6U
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aliemteam/aliemcards/issues/123#issuecomment-289969761,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACVxJkQPumj5_J5w37va786bhaMyw6ruks5rqcy3gaJpZM4MmG6U
.

probably a stupid question, How to I get these into the github doc?
On Tue, Mar 28, 2017 at 11:17 PM, Jeremy Voros notifications@github.com
wrote:

Shift + Command + 4 will get you a crop box you can use to get just the
parts you want.
On Tue, Mar 28, 2017 at 21:15 andyglittle notifications@github.com
wrote:

Mac, I'll give that a try
On Tue, Mar 28, 2017 at 11:01 PM, Jeremy Voros <notifications@github.com
wrote:

I'm just using the screenshot tool on Mac to create an image.
There is probably something similar on Windows.
What are you using?
On Tue, Mar 28, 2017 at 20:23 andyglittle notifications@github.com
wrote:

Starting to break up the elbow card now. In term of the images, what
are
you using to crop the images from the current PDF Card to the github?
Andy
On Tue, Mar 28, 2017 at 3:11 PM, Jeremy Voros <
notifications@github.com>
wrote:

I broke up the knee injuries card, and then made one main card to
link
to
the other cards.
Check out this pull request to see how I did it:
#131 https://github.com/aliemteam/aliemcards/pull/131
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/aliemteam/aliemcards/issues/123#
issuecomment-289874250
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AYVVuQQHD0Seeoc_
tsu3BaJwPJiZ1i6cks5rqVt-gaJpZM4MmG6U
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/aliemteam/aliemcards/issues/123#
issuecomment-289962519>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/ACVxJrWDEkvy4JMpKW-
6kdTAAe_miOErks5rqcCjgaJpZM4MmG6U>

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/aliemteam/aliemcards/issues/123#
issuecomment-289967809
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AYVVuVIlD_g9kM_
6M5SHWgogqtIK7o_fks5rqcmWgaJpZM4MmG6U
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/aliemteam/aliemcards/issues/123#
issuecomment-289969761>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACVxJkQPumj5_
J5w37va786bhaMyw6ruks5rqcy3gaJpZM4MmG6U>

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aliemteam/aliemcards/issues/123#issuecomment-289970089,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYVVuUP7193mm6yt8mZt74uwyHEglvJYks5rqc1PgaJpZM4MmG6U
.

just tried it and I think I figured out. Let me know
On Tue, Mar 28, 2017 at 11:26 PM, Andy Little andyglittle@gmail.com wrote:

probably a stupid question, How to I get these into the github doc?
On Tue, Mar 28, 2017 at 11:17 PM, Jeremy Voros notifications@github.com
wrote:

Shift + Command + 4 will get you a crop box you can use to get just the
parts you want.
On Tue, Mar 28, 2017 at 21:15 andyglittle notifications@github.com
wrote:

Mac, I'll give that a try
On Tue, Mar 28, 2017 at 11:01 PM, Jeremy Voros <
notifications@github.com>
wrote:

I'm just using the screenshot tool on Mac to create an image.
There is probably something similar on Windows.
What are you using?
On Tue, Mar 28, 2017 at 20:23 andyglittle notifications@github.com
wrote:

Starting to break up the elbow card now. In term of the images, what
are
you using to crop the images from the current PDF Card to the
github?
Andy
On Tue, Mar 28, 2017 at 3:11 PM, Jeremy Voros <
notifications@github.com>
wrote:

I broke up the knee injuries card, and then made one main card to
link
to
the other cards.
Check out this pull request to see how I did it:
#131 https://github.com/aliemteam/aliemcards/pull/131
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/aliemteam/aliemcards/issues/123#
issuecomment-289874250
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AYVVuQQHD0Seeoc_
tsu3BaJwPJiZ1i6cks5rqVt-gaJpZM4MmG6U
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/aliemteam/aliemcards/issues/123#
issuecomment-289962519>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ACVxJrWDEkvy4JMpKW-
6kdTAAe_miOErks5rqcCjgaJpZM4MmG6U>

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/aliemteam/aliemcards/issues/123#issuecomm
ent-289967809
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AYVVuVIlD_
g9kM_6M5SHWgogqtIK7o_fks5rqcmWgaJpZM4MmG6U
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/aliemteam/aliemcards/issues/123#issuecom
ment-289969761>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ACVxJkQPumj5_J5w37va786bhaMyw6ruks5rqcy3gaJpZM4MmG6U>

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aliemteam/aliemcards/issues/123#issuecomment-289970089,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYVVuUP7193mm6yt8mZt74uwyHEglvJYks5rqc1PgaJpZM4MmG6U
.

authors: andyglittle jvoros

repo: aliemteam/aliemcards


text:
recast() should cache sorted data

recast() requires a sort, however currently the sort is executed every time the table is iterated over, which is unnecessary. Rather recast() should perform the sort only once then re-use the cached sort result.

Btw should be a good opportunity to fix #297 also, and ensure only a single pass is made through the data (#35).

source: gharchive/issue

repo: alimanfoo/petl

license: mit

license_type: permissive

license_source: bigquery


text:
是否能提供下rest 协议的zipkin支持？

是否能提供下rest 协议的zipkin支持？

@lifesinger  tracer层面已经支持了我记得，有文档么。

@glmapper tracer层面已经支持了我记得，有文档么。

issue & pr : https://github.com/alipay/sofa-tracer/pull/131
document : https://www.sofastack.tech/sofa-tracer/docs/ReportToZipkin

感谢 @glmapper
请 @xiaohanfeidao  根据文档使用，如果有问题可以在tracer的issue中进行沟通。谢谢～

感谢 你们！

我直接通过sofarpc的 rest（不是spring mvc）调用另外一个应用的sofarpc的rest zipkin没有调用轨迹啊？是什么版本开始支持rest协议的，bolt支持，rest也支持吗？

我直接通过sofarpc的 rest（不是spring mvc）调用另外一个应用的sofarpc的rest zipkin没有调用轨迹啊？是什么版本开始支持rest协议的，bolt支持，rest也支持吗？

SOFATracer 将 span 数据上报至 zipkin 目前就是通过 rest 协议上报的，从 2.3.0 版本开始支持。对于SOFARpc 来说，不管你使用的是 bolt 协议还是 rest 协议，对于TRACER上报数据是没有影响的。
PS:
1、先看下你是否有部署 zipkin 的服务端
2、参考 https://www.sofastack.tech/sofa-tracer/docs/ReportToZipkin 看下是否正确使用了 zipkin 上报

不是通过rest协议上报Zipkin，是需要支持sofa rest的链路追踪，bolt协议是可以显示的，
demo地址：https://github.com/xiaohanfeidao/cloudware-sofa
我用的是nacos 0.6.0版本
初衷是全部使用resteasy + netty这种方式的微服务架构，入口从 sofa rest调用开始，
现在测试的结果是不支持的，不知道是我代码有问题 还是本身就是不支持？

authors: glmapper leizhiyuan xiaohanfeidao

repo: alipay/sofa-rpc

license_source: github-api


text:
fix some misspell and warning code

Motivation:
Fix some misspell and waring code
Modification:
Describe the idea and modifications you've done.

fix misspell
remove 'public' from interface method

Result:
No issue.

Codecov Report

Merging #254 into master will increase coverage by <.01%.
The diff coverage is 20%.

@@             Coverage Diff              @@
##             master     #254      +/-   ##
============================================
+ Coverage      71.3%   71.31%   +<.01%
- Complexity      960      961       +1
============================================
  Files           342      342
  Lines         14301    14299       -2
  Branches       2300     2300
============================================
  Hits          10197    10197
+ Misses         2909     2908       -1
+ Partials       1195     1194       -1

Impacted Files
Coverage Δ
Complexity Δ

...ay/sofa/rpc/client/AllConnectConnectionHolder.java
63.33% <ø> (ø)
0 <0> (ø)
:arrow_down:

...lipay/sofa/rpc/client/ElasticConnectionHolder.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ipay/sofa/rpc/client/SingleGroupAddressHolder.java
98.21% <100%> (ø)
0 <0> (ø)
:arrow_down:

...alipay/sofa/rpc/registry/zk/ZookeeperRegistry.java
62.1% <0%> (-0.79%)
0% <0%> (ø)

.../alipay/sofa/rpc/registry/local/LocalRegistry.java
66.26% <0%> (+0.6%)
29% <0%> (+1%)
:arrow_up:

...ava/com/alipay/sofa/rpc/config/RegistryConfig.java
90.19% <0%> (+0.98%)
0% <0%> (ø)
:arrow_down:

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 036054b...30fe9ca. Read the comment docs.

source: gharchive/pull-request

authors: codecov-io dbl-x


text:
Read from stdin

I would be great if the script supported piping.
Example:
echo "test" | qrcode-terminal-py
Possible implementation:
if not options.data:
    options.data = sys.stdin.readline()[:-1]

Supported! Thanks for your suggestion :)

repo: alishtory/qrcode-terminal


text:
bug in showInfoWindow

in line 1175 ther is 'else if' statement that checks if customMarkers exists:
else if (
//additionally check if that marker is a custom marker
typeof mapController.map.customMarkers
&& typeof mapController.map.customMarkers[marker] != "undefined") {
marker = mapController.map.customMarkers[marker];
}
'typeof mapController.map.customMarkers' should also check if it is '!= "undefined"'
otherwise it always returns true.
kind regards,
Pavle Ozretic

Fixed

authors: PavleO allenhwkim

repo: allenhwkim/angularjs-google-maps


text:
Setup CI coverage for tzif library and tzdata package

Is your feature request related to a problem? Please describe.
The current CI uses whatever environment python has setup, and instead we want an environment that simulates no local zoneinfo using tzdata package.
Describe the solution you'd like
We may want to run in a mode that acts like zoneinfo is not available, and ensures that tzdata package is installed. I think we first check zoneinfo files before checking tzdata, so this may be able to be done with a fixture with different patches for each test mode.
Describe alternatives you've considered
Alternatives could include running separate images for testing at a lower level (e.g. the os image handles this). Windows may be the other interesting test case to consider as the target of tzdata, which probably wouldn't run in CI.

This package now always installs tzdata and prefers that first, before looking at system timezone information rather than assuming anything based on the install state of the system.

repo: allenporter/ical


text:
Broken README link

Hey, this "here" link:

Is broken and leads to a 404 page:

ngl it took me a while to understand this is a print screen. The link is working for me, can you check again?

@dolby360  Everything works now. I will close the issue thank you

repo: allero-io/allero


text:
Create AnyTxEnvelope

Component
network
Describe the feature you would like
#584 follow-up
Create a new struct AnyTxEnvelope replacing alloy_consensus::TxEnvelope here:
https://github.com/alloy-rs/alloy/blob/d68a6b787b2904061f0ae7fcc02ece8513e3c500/crates/network/src/any/mod.rs#L62
Additional context
No response

I've started to work on this, but I struggle to impl Encodable2718<AnyTxType> and Decodable2718<AnyTxType> for AnyTxEnvelope.
I created AnyTxEnvelope like this:
#[derive(Clone, Debug, PartialEq, Eq)]
#[cfg_attr(feature = "serde", derive(serde::Serialize, serde::Deserialize))]
pub struct AnyTxEnvelope<T> {
    /// The signed transaction
    #[cfg_attr(feature = "serde", serde(flatten))]
    pub inner: Signed<T>,
    /// The transaction type.
    #[cfg_attr(feature = "serde", serde(with = "alloy_serde::num::u8_hex"))]
    pub r#type: u8,
}

It's used in AnyNetwork like that:
type TxEnvelope = alloy_consensus::AnyTxEnvelope<WithOtherFields<alloy_rpc_types::eth::transaction::Transaction>>;

But actually I'm not sure it's correct. wdyt?

Closing as this issue has been created as a follow up to #584, that won't be merged.

repo: alloy-rs/alloy


text:
Overhaul multi-threading approach: execute events in parallel

This pull request constitutes my Google Summer of Code 2018 project: Improve multi-threading support for CERN’s Allpix-Squared project using dependency graphs.
This branch (mt-overhaul) overhauls the multi-threading approach of the framework to simulate events in parallel instead of parallelizing the execution of modules that are explicitly thread-safe. A detailed account of the changes to the multi-threading approach is available below. Benchmarks between the old and new approach, along with another branch of interest, are also available below.
Configurations used for benchmarking can be found here.
Contrary to the title of the project, this new approach does not utilize dependency graphs; building one with a simulation's events would take up too much memory (e.g. a simulation with million events) and would also clash with the general design of the framework. However, this project does improve the multi-threading support for Allpix² in regards to increased performance and improved resource utilization.
The GitLab CI tests passes successfully for this branch and are available here.
Multi-threading is still considered an experimental feature in Allpix². Until all file writer modules have been confirmed to be working correctly, and until the performance of Allpix² properly scales when using more than eight workers, it will remain experimental.
When the above has been confirmed, it is likely that this branch is merged into the framework for a new major release, Allpix-Squared v2.0.
The multi-threading performance for Allpix² has via this project been almost completely optimized for worker/core counts up to 8. Or in the case of removing the ROOT inheritance from the base Allpix² object, for all worker/core counts up to 32. The main target of Allpix² are systems with four CPU cores. Removal of ROOT inheritence is done with this commit.

Multi-threading approach
Allpix² now supports experimental multi-threading by running events in parallel. For the number of events configured, an Event instance is constructed and submitted to the thread pool. As soon as an event is pushed to the thread pool a free worker will pick it up and execute it; when done it will pick up the next event. When all events have been executed Allpix² begins terminating.
Module thread safety
An event is constructed with a shared list of the loaded modules. Inside an event, and thus for each worker, these modules are run sequentially, modifying the Event instance given to them. In the context of an event, the only module function used is the Module::run(Event*)-method. To enable thread safety, this function has been made constant; the run()-method may not access or modify member fields of the module unless the module author has explicitly allowed this. If a module's run()-function does access a member field (which is then accessed by multiple workers) it must be appropriately protected with a mutex and should for performance reasons only be used to record module statistics.
Readers and writers
Modules that read from and write to files are not subject to the rule presented in the previous section.
Between two simulations using the same configuration, if the simulated events are to be written to file, the two simulations must produce the same output file. To achieve this, a module author will appropriately mark their module as a reader or writer via inheritance. During run-time, Allpix² checks whether the module is a reader, writer or neither; if it does access files, it will be run in order of increasing event number. E.g. a reader/writer of event 4 will be run before the same module(s) of event 5. If it isn't a specific event's turn to run this module, the thread will block and wait for its turn. While blocking, the thread does no work. A reader and a writer may run in parallel, because they do not access the same files.
Seed distribution
To enable two matching simulations to produce the same output, the seed distribution must also match.
Each Event instance now owns a random engine that can be accessed and modified in whatever manner a running module wishes. For a stable seed distribution, Allpix² holds a top-level random engine that seeds every event's engine in a sequential manner in order of increasing event number. This ensures that two matching simulations produce the same output, even when the number of workers do not match.
Messages
Modules communicate with each other via messages. Considering that events are independent of each other, messages from a module to another must be local to the event. Subscription to specific messages are done in the modules' constructors and is thus global, but this read-only delegate information is now shared with all event-local messengers. These are then responsible for dispatching and fetching messages in the event. Upon the termination of an event, all messages local to that event are deleted.
Geant4 and ROOT
Unfortunately, because of the dependencies on Geant4 and ROOT and their incorporation into event execution, Allpix² cannot simply spawn n workers and expect a new run-time of one nth of the original single-threaded run-time.
Geant4 is responsible for building the simulation geometry and depositing charges in the detectors.
When working in a multi-threaded context, Geant4 expects to handle the parallel work internally;
this clashes with the design of Allpix². Because of this, all modules that runs Geant4 code may not run on spawned threads, lest the program will segfault. In Allpix², all instanced Events are thus initialized by the master thread by running these modules before submission to the thread pool. To prevent workers from being idle, a buffer of initialized events is maintained by the module manager.
ROOT, specifically the TObject and TRef classes, are used by all objects in Allpix² to relate to other objects. These classes, because of legacy reasons, do not scale well to a high number of running threads. For this reason, it is not currently recommended to use more than 8 workers during simulation as this will greatly impact performance negatively.
Removing the inheritance on ROOT for the Allpix² base object greatly increases performance, as can be seen in the benchmarks below.
Benchmarks
Below are benchmarks between the old multi-threading approach, the new multi-threading approach, the new approach without ROOT inheritance ("no root"), and the optimal run-time for an increasing number of workers/cores. The optimal plots' first point are the same as the old approach's; subsequent points are calculated by dividing the single-threaded run-time with the current number of workers/cores.

The server on which these branches where benchmarked on had 48 cores at its disposal, hence a maximum of 47 workers — the remaining core is used by the master thread.
The reason for the greater deviation of the "no root" plot from the optimal plot past 32 workers in the benchmarks above is presently unknown.
Future improvements
Investigate if ROOT penalty can be minimized
A thread was created on the ROOT forums regarding the scaling issues we had with ROOT. After a minimal example was created, mimmicking the event construction and execution in Allpix² (while not doing any real work), a performance patch was written and merged into the master branch. Unfortunately, running some benchmarks with this patch eventually crashes Allpix² via segmentation fault. Finding the cause and amending the minimal example to reproduce it should allow us to properly benchmark with a stable patch.
Remove ROOT inheritance
As can be seen in the benchmarks above, removing the inheritance on ROOT for the base Allpix² object allows us to reach an almost optimal run-time performance; effectively future proofing the framework for systems with a high number of CPU cores. The final TObjects can then be constructed just before they are written to file.
Investigate and fix buffer implementation
The module manager maintains a buffer of initialized events (where Geant4 modules have been run on the main thread) which are submitted to the thread pool in order as to not let any workers be idle. This is done by checking the size of the thread pool's internal queue of events every 50ms. To maintain acceptable memory usage throughout the execution of a simulation, the buffer should never exceed number of workers x 4 events. Asserting this predicate after each submission to the thread pool however leads to crashes. A stricter check allows us to satisfy this predicate, but at the cost of having some idle threads. What's odd is that increasing the buffer size does not fix the issue.
Resolving this issue should allow the framework to have much better memory usage throughout any simulation, especially those where millions of events are simulated.
Make Geant4 modules able to run on spawned threads
A thread was created on the Geant4 mailing list regarding our problems of running Geant4 code on spawned threads. According to replies, it may be possible to make Geant4 work as we want it to. If Geant4 modules can then run on spawned threads, it would allow us to get rid of the buffer the module manager maintains, improving the framework's memory usage and containing the full run of an event in its run()-method. It would also allow us to get rid of the master thread that currently only initializes events.
Buffer file writes
At present, when an event reaches the execution of a writer module, its execution will block until all previous events have been written to file. This leaves threads idle if previous events happen to take longer to simulate. If these writes are instead buffered (by buffering the execution of the writer modules for that specific event) threads should never end up idle, and should increase framework performance somewhat. This is at the cost of keeping more events in memory. A later event would then check if any events have been buffered, and if that's the case, write any previous events before writing self to file, removing them from the buffer.

Superseded by merge request https://gitlab.cern.ch/allpix-squared/allpix-squared/merge_requests/227

authors: Tmplt simonspa

repo: allpix-squared/allpix-squared

license: MIT


text:
CSS under LESS

Hi,
When i use grunt with the gruntfile you have created, i have some CSS files that are created under the less files.
My architecture :
├── less/
|   ├── AdminLTE.less
|    |    └── AdminLTE.css
How can i fix it ?

Ok i fixed it, PHPStorm automatically added a watcher on less files...


text:
Typescript support

How can I stop “Property 'AdminLTE' does not exist on type 'JQueryStatic'.” syntax errors when using Typescript?
Thanks!

Hello @yoyo837
In the new AdminLTE 2.4, we have rewritten all of our JS code. Your best bet to make this  work is to upgrade to v2.4 by following this guide: https://adminlte.io/docs/2.4/upgrade-guide
Please open a new issue if the problem persists in v2.4
We greatly appreciate your contribution. Thanks!


text:
Match Prefixes not being delimited by a space character

I see the code is checking for a space character following defined prefix in the object's name. I'd say it's more versatile if it wouldn't do that. Do you have any specific reason why is it like that?
If it wouldn't check I could still explicitly tell I need to search for prefix being delimited by a space by specifying it.
Current behavior:
--prefix Win
"Win_policy1" - won't match
"Win policy1" - will match
Suggested behavior:
--prefix Win
"Win_policy1" - will match
"Win policy1" - will match
--prefix "Win "
"Win_policy1" - won't match
"Win policy1" - will match

No specific reason really :) I will push a change to beta soon where it uses regex instead so it will work as you describe it above, also it will be case insensitive

try it out in the beta: pip install IntuneCD==2.0.4b1

authors: almenscorner jangrundmann

repo: almenscorner/IntuneCD


text:
Remove model specific constructors

This PR removes the model specific constructors from the Builder type. Instead one generic new constructor can now be used for all controller types. This shouldn't make the API harder to use and has other advantages, like reducing the amount of code required to implement a model. And this method also works for externally implemented Models, which aren't able to add a new constructors to Builder.

LGTM, thank you, but could you please add an entry to the migration guide? This feels like it should be mentioned there for the next major version.

OK, done. Perhaps we should open an issue to remember to update the migration guide before the release. There are already other changes that should be mentioned in the guide, like the removed re-exports.

repo: almindor/mipidsi


text:
[FEATURE] Запоминание настроек фильтрации в блоттере во вкладке Заявки при выходе из терминала.

Опишите проблему, которую решает ваша фича
При выходе из терминала не запоминается настройка фильтрации блоттера во вкладке Заявки (отложена, отменена, исполнена, активна). Приходится кажды раз заново настраивать.
Опишите предлагаемое вами решение
При выходе из терминала запоминаться настройки фильтрации вкладки Заявки.
Опишите альтернативные решения, о которых вы думали
No response
Дополнительная информация
No response
Правила

[X] Я согласен следовать правилам

Фильтрация это временная настройка. Она должна сбрасываться. Теперь представь, что у человека его сортировка или фильтрация сохранились, он перезашел, уже забыл про фильтрацию и он в растерянности, куда делить его позиции. То что там иконочка подсвечена он может и не заметить. Я против честно говоря.

клиенты просят вообще оставить толкьо активные по умолчанию, но тут я не согласен с ними. А вот активному трейдеру приходится кажды раз утром донастраивать терминал - это плохо. Я проверил алор-трейд, он запоминает настройку фильтрации в окне заявок, и никакой растерянности это не вызывало у клиентов на протяжении 23 лет.

Ты, пожалуйста, АТ в пример не приводи. На ком-то другом может и сработает, но я хорошо знаю этот терминал это одна сплошная растерянность. Ты то с ним всю жизнь с момента его рождения он конечно не вызывает растерянности, но вот для других это совершенно не так.
По задаче в целом, думаю можно сделать как опциональную настройку, выключенную по умолчанию.

authors: MorozovDen PilgrimViis

repo: alor-broker/Astras-Trading-UI


text:
Call the supplied source function when the query is empty

This fixes the bug report in this issue comment.

Solution
The solution to this bug is to call the source function when the query becomes empty and then let the source function decide whether to show no results (closing the menu) or to show some results

Explanation of the bug
This fixes a bug for using async source functions, below is the steps to show the original bug:

Create accessible-autocomplete instance with an async source function
Type a character and then delete the character really quickly

A live demo of this can be found at https://output.jsbin.com/werupanune
You can view the code for the demo at https://jsbin.com/werupanune/edit?html,js,output
Accessible-autocomplete would only call the supplied source function when the user has enter a value into the text-input and not when the user has deleted all values from the text-input. Below is the part of the code which implements that logic:
https://github.com/alphagov/accessible-autocomplete/blob/935f0d43aea1c606e6b38985e3fe7049ddbe98be/src/autocomplete.js#L226-L241
Because of logic to only call when there is text entered and not when the text has been deleted, there is a race-condition between the async source function and accessible-autocompletes own code to close the menu when the query is empty. Accessible-autocomplete will close the menu immediately, but the async source function, once it gets it's results, will call the callback to populate the menu with the results from the previous input/query the user had entered.
Below is a video showing the bug:
https://user-images.githubusercontent.com/1569131/119124363-7a679900-ba28-11eb-8028-ecf7ce89d7d3.mov

@JakeChampion Really appreciate your work, however at the moment we don't have capacity to deal with issues and pull requests on this repo unfortunately:
https://github.com/alphagov/accessible-autocomplete/issues/430
Possibly in time we will be able to, and in the meantime I'm sure your work can help people looking for a fix.

I think our team came across this same bug recently.

Hi @romaricpascal @colinrotherham @joelanman,
We've noticed there's been more activity on this repo in the last few months and wonder if it might be possible for this PR to be revisited?
(Financial-Times maintains a fork of this repo purely to include this bugfix.)

authors: JakeChampion andygout edwardhorsford joelanman

repo: alphagov/accessible-autocomplete


text:
Conservative upgrade of origin gem (fix inconsistent Gemfile.lock)

I ran the following command:
bundle update origin --conservative

My motivation for doing this was that I was seeing the following error when trying to upgrade unrelated gems:
Bundler could not find compatible versions for gem "origin":
In snapshot (Gemfile.lock):
origin (= 2.1.1)

In Gemfile:
mongoid (~> 5.0) was resolved to 5.2.1, which depends on
  origin (~> 2.3)

This seems to suggest that the origin gem was locked at a version which was incompatible with the locked version of the mongoid gem. I'm guessing that the Gemfile.lock was edited by hand and left in an inconsistent state, so although bundle install worked OK, bundle update did not. This commit should fix that problem.

@chrislo: Thanks for reviewing!

repo: alphagov/asset-manager


text:
Update 'View Opportunities' page to include missing 'and'

For this story on Pivotal.
This PR updates the view opportunities page to use a new filter (see this PR) which will convert a list of strings to a properly formatted string. It joins all elements with a ', ' except for the last which it joins with ' and '.
If a list has only one element, it just returns that element as a lower case string without any commas or 'and'.
If the list has no elements it will just return an empty string. This should never occur in this use case, but the functionality has been added in case it is needed for another application in the future.
All strings are converted to lowercase.
See the screenshot below.

👍
(Although looking at it in context now, I'm not sure about smartjoin name. Since it's used without an argument it's not really obvious that it's using commas and 'and'. But that's something we can revisit later.)

authors: Wynndow allait


text:
WIP: G7 upload signed agreements

Allow G-Cloud 7 signed framework agreements to be uploaded by suppliers.

Depends on

[x] Sign off from Ralph
[x] https://github.com/alphagov/digitalmarketplace-utils/pull/201
[ ] https://github.com/alphagov/digitalmarketplace-supplier-frontend/pull/318

Yes, good point about the utils bump. That means that this PR now depends on https://github.com/alphagov/digitalmarketplace-supplier-frontend/pull/322 because of version 12.0.0 of utils.

:+1:

authors: TheDoubleK robyoung


text:
Bugfix to mail threshold, not signature count

PT: https://www.pivotaltracker.com/story/show/98080170

repo: alphagov/e-petitions


text:
Bump trello-poster-action from 1.0.1 to 1.1.0

Bumps trello-poster-action from 1.0.1 to 1.1.0.

Commits

Closing in favour of Dependabot PR #833.

repo: alphagov/forms-admin


text:
Markdown: soft line breaks not being rendered correctly

http://spec.commonmark.org/0.27/#soft-line-breaks
I used ExternalDoc.fetch to embed some markdown from GitHub. This markdown contained newlines within paragraphs. These newlines were rendered as <br> tags. The spec says they should have been rendered as newlines in the HTML or space characters. This breaks formatting.
I don't know if this issue is specific to ExternalDoc.fetch or whether it's for markdown within this project, too.

No one has commented on this issue for 2 years and the versions involved have changed since it was raised so I'm closing this ticket. Please feel free to reopen if the issue is still present. Or just to say "Hello"

authors: deanwilson tuzz

repo: alphagov/govuk-developer-docs


text:
link-buttons do not focus like regular buttons do in firefox

What
In Firefox, by default very few items can be focused - but buttons can.
However, our link buttons can't. This means if you have two items styled like buttons, one a button and one a link button, only one can be focused.
Can be seen in this video tabbing through the new cookie banner:

Why
We have two things that look like buttons, but focus behaves differently in them. This feels wrong. We shim link buttons with js and role=button to help make them behave like buttons - but this appears to be a case where it's not enough.
Anything else
I note Firefox's default behaviour is pretty useless - but since it's default it would be good if our link buttons could behave like the thing they look like.
If others don't see this issue - check you haven't enabled firefox's option to make all tabable things tabable.

We're going to do a quick investigation to see if [tabIndex=0] might give us a more consistent behaviour.
If it doesn't or this isn't something we want to do, we'll close this and reference it as a note in the backlog entry for buttons.

OK I tried in Safari and Firefox, and [tabindex=0] does not seem to make things tabbable when these settings are enabled.

I have raised a bug for this on Firefox's bug tracker for them to consider: https://github.com/alphagov/reported-bugs/issues/43

Thanks for raising, Ed this is good to know.

Nice, thanks @nickcolley!

authors: edwardhorsford nickcolley

repo: alphagov/govuk-frontend


text:
Link underlines sit too low in Firefox

As originally raised by @dashouse on GOV.UK Template, link underlines looks like they're sitting below the text (almost as if they are using text-underline-position: under; (which they aren't). This is affecting GOV.UK Frontend as well:

Dave identified that this started happening in Firefox 39, and from doing some digging it looks like Firefox 39 was the release that enabled support for WOFF2, and this seems to be related – commenting out the woff2 file from the font-face declaration 'fixes' it. We think this is something to do with the way that the text decoration is aligned with the 'baseline' (which we know is 'high' in the current cut of our font-face) in woff2 fonts.
However, it looks like updating to use the new cut of the font, with the normalised baseline, will fix this, so we might not need to do anything except prioritising the work to move to the new font:

Looks like this will be addressed with the font change in 3.0 as we expected.
Before

After

I wonder if we should list this as a fix in the changelog? / cc @aliuk2012


text:
Can't modify some settings for plugins (like $govuk-suppressed-warnings)

Description of the issue
a user should be able to customise sass settings for their plugins by creating and adding settings to app/assets/sass/settings.scss in their prototype, which is imported before the the plugin styles
hmrc-frontend uses some sass functions that generate sass deprecation warnings when it's installed in a prototype, and I tried to suppress these within a prototype by setting $govuk-suppressed-warnings in app/assets/sass/settings.scss, however it doesn't work, because the sass file generated by the prototype kit to import plugin styles defines (not as a default, and not appending to existing list if it's set) $govuk-suppressed-warnings
Steps to reproduce the issue
you can try running this example of the issue
Actual vs expected behaviour
would expect to be able to define $govuk-suppressed-warnings in app/assets/sass/settings.scss and have it apply to plugins
it's not possible for plugins to set a default value for $govuk-suppressed-warnings either, because the setting written into _plugins.scss will take precedence - and if they overwrite it, then plugins loaded further in the list will lose the value that's set in _plugins.scss "legacy-color-param"
Environment (where applicable)
all

Operating system: n/a
Browser: n/a
Browser version: n/a
GOV.UK Prototype Kit version: 13.16.2

@oscarduignan I am having the same issue.  I wondered if you have resolved this?

another workaround for the sass is to add an override:
https://github.com/joelanman/govuk-prototype-kit-prototype/blob/main/package.json#L12-L14

authors: joelanman oscarduignan pb-control-dwp

repo: alphagov/govuk-prototype-kit


text:
Tom Byers has left GOV.UK

https://trello.com/c/oiS9MunH/153-tom-byers-left-govuk

🎺

repo: alphagov/govuk-puppet


text:
Fix gemspec comment

The comment that applied to the inclusion of the webmock gem had become
decoupled.  I've re-attached them and changed the wording of the comment
so that it's hopefully clearer that they belong together.

I didn't think it was @injms!


text:
Change default sort order

This PR changes the default sort order to be descending.  This means that when viewing metrics they are shown from highest values to lowest by default.
This is however problematic as the initially selected 'order by' is for the name (of the dept or service). We want to view the names in alphabetical order by default, unalphabetical is just weird.  If we default to ascending here then it will be carried across to the metrics when the user changes a different field to order by. This would enforce ordering by ascending value, which isn't what we want.
Having checked that sort by name is required (via a detour in 74a6a76
which removed the option) , we now treat name as with all the metrics, but reverse it at the last second before use in the presenter.

I've reworked it a little to make sure we only reverse at most once, and hopefully it's a little clearer.

repo: alphagov/gsd-view-data


text:
use sed to avoid pipefail in harbor-resource

head will stop reading from it's stdin once it has happily done
it's job, leaving the stdin stream with unread data.
when used in a chain of processes piped together, leaving unread bytes
on the stream will cause a pipefail error to be raised in the recving
process.
This is all by design. Although the behaviour is somewhat surprizing.
The harbor resource sets -o pipefail to abort on any process that
returns a pipefail status (141). This helps us catch errors that occur
in chains of processes, without them being swallowed by the sending
process.
To parse the harbor project-name out of the full image uri, we were
spliting the uri into url segments, then using:
echo $URI_SEGMENTS | head -n2 | tail -n1
to grab the 2nd line of the file (the name).
You can simulate something similar by observing the 141 exit code by doing:
seq 90000 | cat | head -n2; echo ${PIPESTATUS[@]}

I believe this is the culprit for the mysterious failures of the
resource we have seen.
Since the $URI_SEGMENTS string was so short, it is likely that this
almost always fit into the write buffer of the sending process (echo)
and so is instantly consumed in total by head... however sometimes
(totally up to the OS, hardware pressure, phase of the moon) the entire
string might not be sent/or read in one go... this would give head and
oportunity to stop reading more bytes, and ultimatly cause a pipefail
141 status.
To workaround this issue, I have switched to using sed to grab the 2nd
line of the URI_SEGMENTS and avoid the potential for pipefail.

@Krenair we are so far past that point :smile:  ... but yeah we probably should rewrite some of this in a "propper" language

repo: alphagov/gsp


text:
Revert "Bump pino-pretty from 5.1.3 to 6.0.0"

Reverts alphagov/paas-admin#1780

no need to revert this one it seems

repo: alphagov/paas-admin


text:
Bump Prometheus data volumes

We're close to running out of disk on 2/3 proms. We have run out
entirely of disk on prom-1. The disk usage appears to be accelerating
even though the rate of metric ingestion seems largely unchanged. We're
going to bump the disk size for the time being.

5⃣0⃣


text:
Replace references to master with main

Part of https://github.com/alphagov/design-system-team-internal/issues/423
What
Replace references to master with main.
Why

One task steps a user through creating a new Github repo. All new Github repos have a main branch instead of a master branch, so we need to update that command
An introduction to using the terminal gives an example of pushing to a master branch. Update this example to use a main branch. The branch name shouldn't matter as it's just an example.
Update the Travis config to replace master with main. The Travis config will also be manually updated in the UI to specify main as the new default branch before this PR is merged.

The update to the Travis config and the terminal branch example look fine to me.
I'm a bit unsure about the steps in task 5; my understanding is that the git command line client is still using master as the default branch name, so for most people who have not used git before running git init and then committing changes locally will create a commit to the master branch. Then I think what will happen when git push -u origin main for recent versions of git is that the user will get an error message error: src refspec main does not match any, because they don't have a local branch called main. I've followed the instructions locally using an new Ubuntu LTS installation in Docker, and I think the same thing will happen on macOS.
I did notice that when creating a repo in GitHub, it now recommends an extra step to rename your local master branch to main:

…or create a new repository on the command line
echo "# test-new-empty" >> README.md
git init
git add README.md
git commit -m "first commit"
git branch -M main
git remote add origin git@github.com:lfdebrux/test-new-empty.git
git push -u origin main

…or push an existing repository from the command line
git remote add origin git@github.com:lfdebrux/test-new-empty.git
git branch -M main
git push -u origin main

Maybe this training document should have a git branch -M main step as well?

Thanks @lfdebrux , really good spot! I think it makes sense to add a git branch -M main, I'll try and draft something for that now.

authors: lfdebrux vanitabarrett

repo: alphagov/prototype-kit-training


text:
[Don't merge, FC] Differentiate between Israeli travel documents

We've had letters of complaint from customers that the Visa Checker tool is not
clear for holders of Israeli travel documents in lieu of passports. Israeli
passport holders are non-visa nationals, so in general only require entry
clearance if they are coming here for longer than 6 months. Israeli-issued
travel documents are issued to non-Israeli citizens (like Palestinians) and
the holders are visa nationals so require a visa to come to the UK for any
reason.
Add an Israel-specific question that collects information about the user's
travel document type and show the corresponding outcome.

Looks good to me. Presumably the tests have failed because the changes in the final 'fixup' commit need the regression test artefacts to be regenerated again?

Thanks for reviewing.
I haven't updated the checksums because content designers are not sure how best to describe the provisional passport. I'll update this PR once we hear back from the department :)

@chrisroos I've added two more commits to this PR, would you mind checking them as well?

Update: apparently there were two people fact-checking this and one of them thinks a correction is needed, so please hold off reviewing for now

We've now received confirmation that this change can go live. I'm going to double check it and get it merged.

authors: chrisroos tadast

repo: alphagov/smart-answers


text:
Marriage abroad: Support two questions/outcomes per path for Japan

This PR needs to be merged after #3114
Trello card
Description
The goal of this PR is to convert the flow for Japan to use the outcome per path strategy and also add support for two questions flow.
Factcheck
Preview link
GOVUK
Expected changes

Enable two question flow for Japan
Replace 18 with 2 outcome for Japan

Before

After

thanks @cbaines for reviewing

Closing this PR to recreate another PR to get the preview link on the GOVUK account


text:
Preview Govspeak button for document new and edit views

This sends an AJAX request and renders the Govspeak body text on the page.
We decided to use a Govspeak controller because serving this ajax call is something that is not specific to documents.
We've had to update jenkins to run using Xvfb, so that Capybara can run functional tests that rely on Javascript. More details here.
trello card

Looks good. A couple of minor questions. 👍

👍

authors: Seraphiana tuzz

repo: alphagov/specialist-publisher-rebuild


text:
Say goodbye to Issy

From http://humanstxt.org/ -

humans.txt is an initiative for knowing the people behind a website.
It's a TXT file that contains information about the different people who
have contributed to building the website.

The internet is for humans...
We are always saying that, but the only file we generate is one full
of additional information for the searchbots: robots.txt. Then why not
doing one for ourselves?

My proposal here is to:

Update www.gov.uk/humans.txt with a short message saying goodbye and
thank you
Leave it up for about a day
Revert this PR to set it back to the old version

I think this is a nice thing to do, and well within the intended purpose of
the humans.txt file - it's not going to affect any users of GOV.UK who
aren't looking for humans.
Thanks Issy - we'll miss you!
Screenshot from firefox, against static running locally:

😍😍😍😍😍

👏 this is so nice to see. Well done Issy, you've been amazing!

authors: boffbowsh issyl0 richardTowers

repo: alphagov/static


text:
API documentation issues

What should change
After following the guide to generate API documentation from an OpenAPI spec, we've found that Array/List responses are rendered incorrectly - they appear as empty objects.
For example, see: https://ministryofjustice.github.io/hmpps-probation-integration-services/tech-docs/projects/create-and-vary-a-licence-and-delius/api-reference.html#probation-case-crn-addresses

The response should appear as a a list of objects as they do in Swagger, for example: https://create-and-vary-a-licence-and-delius-dev.hmpps.service.justice.gov.uk/swagger-ui/index.html#/probation-case-resource/findAddresses

On our API docs, we found the generated docs inadequate and essentially re-implemented the entire thing to suit our use-case.
There's fairly substantial parts of the OpenAPI spec that aren't covered by the gem's built-in implementation, such as like as polymorphic types (which we've used extensively in our API).
For anyone interested, we created a new module which we load in through config.rb. We then have a bunch of helpers that we use throughout the various templates:

Config
Extension
Helpers
Schema template
Endpoint template

This is by no means a complete implementation so your mileage may vary. It should still be a useful starting point for anyone wanting to improve their generated docs!

authors: marcus-bcl ntsim

repo: alphagov/tech-docs-gem


text:
Fix initial page position when linking to anchor

The call to handleScrollEvent was previously causing the browser to jump back up to the start of the document. This seems to be because:

handleScrollEvent is called before the browser has scrolled the user to the target heading
tocItemForFirstElementInView therefore returns the first heading on the page
the current history state is therefore updated with the hash of the first heading on the page
this appears to be enough to cause the browser to scroll back to the top of the document

We need slightly different behaviour when loading the page for the first time - if there is an anchor specified, we should use the hash and offset for that entry rather than trying to find the first element in view. We’ll fall back to the first element if there is no hash, or the hash does not link to somewhere in the ToC.

Needs a rebase, but LGTM

repo: alphagov/tech-docs-template


text:
Some tried to select multiple radio buttons when specifying notification channel

Impact: Users were unsure which contact channel would be best so far into the future and wanted to select multiple channels to be sure.
Evidence: Users were observed clicking radio buttons for multiple contact channels and providing details for each, explaining that this would be their preference, given their uncertainty over

repo: alphagov/verify-local-patterns


text:
Fresh Installation Error

Acknowledge the following

[x] I carefully read and followed the Getting Started guide.
[x] I read through FAQ and searched through the past issues, none of which addressed my issue.
[x] The issue I am raising is a potential bug in al-folio and not just a usage question.  [For usage questions, please post in the Discussions instead of raising an issue.]

Describe the bug
I got the following error message when I tried bundle exec jekyll serve --lsi locally as well as on GitHub pages build
Incremental build: disabled. Enable with --incremental
      Generating...
"Fetching external posts from medium.com:"
                    ------------------------------------------------
      Jekyll 4.3.2   Please append `--trace` to the `serve` command
                     for any additional information or backtrace.
                    ------------------------------------------------
/usr/local/lib/ruby/gems/3.1.0/gems/feedjira-3.2.2/lib/feedjira.rb:63:in `parse': No valid parser for XML. (Feedjira::NoParserAvailable)

System (please complete the following information):

OS: [MacOS 12.3.1 (Intel)]
Jekyll version [4.3.2]
Ruby version [3.1.2]

Additional context
Add any other context about the problem here.

I might be wrong here, but maybe feedjira have a lib dependecy that is not currently satisfied in the system (maybe libxml2 idk).

I am trying to find what dependency might be unfulfilled. I have installed the dependencies listed in the feedjira website though. What's surprising for me is how it doesn't even run successfully inside GitHub since I would assume it should only throw errors, if any, when trying to run it locally.

Update: I disabled imagemagick and now Pages deployment works fine. However, even on fresh installation, the issue persists on my local machine.

That would be the obvious work around. However, since I did not modify the source code (except the repository name), it should have built without any issue. By the way, I am working via docker now and its working fine.

@majauhar agreed. But without having the same system I can't help that much. Also, apparently this is not a common error, I couldn't find any recent issues on this matter.

I am on linux with manjaro and i have the same error

Have you tested docker? You should be fine with all OSes with docker.

Have you tested docker? You should be fine with all OSes with docker.

@pourmand1376
If it works well with docker

If it works? It means that it is not working? Or the If in your answer was a typo?

If it works? It means that it is not working? Or the If in your answer was a typo?
@george-gca

yes it works well  with Docker.

Okay, good. If that resolves your problem, please close this issue.

same issue here with Mac Sonoma

repo: alshedivat/al-folio


text:
Status of project

Hello,
The repository hasn't got any commit for 7 months now, is there still someone maintaining it?
Thanks a lot.

I would also like to know if anyone is working on this?  If so, where can I suggest exchanges to be added?  If not, what can be done to get this project rolling again?
Thanks in advance.

We love this library -- can someone take over write access or approve prs?

I'd be happy to give write access to volunteers.  Sadly I don't have time to maintain this library anymore.

In the meantime I checked other projects and found out that CCXT (library on which CCXWS is working above) is merging for free their pro version (including websockets handling, etc) within few months (check by yourself here: https://ccxt.pro/)
So I don't think CCXWS is relevant anymore

That's great news about CCXT.PRO merging with CCXT (free version) - it will be welcome by all users of CCXT, and I think we should keep our eye on that merge process, but until that happens I'm still using CCXWS, therefore, it's still valuable to me.
The plan (and/or timeframe) to merge could change or some other issue might arise, so I believe we should continue attempting to update CCXWS until that merge is complete and we're able to successfully adopt it and use it.
I wonder if there is a video on how all the CCXWS pieces fit and work together?

authors: Mateotey backnight bmancini55 drsavant-pub

repo: altangent/ccxws


text:
Support for klines in all exchanges

First of all thank you for the amazing integration across various exchanges.
I looked through the code and see subscribeTicker, subscribeTrade etc but dont find klines anywhere. Do you have any plans of integrating klines from each exchange?
Thannks

Yes, just need to find some bandwidth to work on it.
Always happy to accept a pull requests to add it to any exchange as well.

Interesting, in that case, I ll try adding klines to each exchange one by one and then run some tests, will update you if everything goes well/bad :)

I just pushed a branch with a few additions to the base clients to scaffold candle subscriptions:
https://github.com/altangent/ccxws/tree/candles
I can merge this into master once a few details have been worked out and it should be pretty straight forward to implement individual exchanges after this code has been merged.
The biggest issue is that there is no pattern for passing data to subscriptions. Candles subs will require the time period as an argument. Ideally the library would be flexible enough to allow multiple subscriptions to the same market with different time periods.  A generic example:
let market1 = { id: 'BTCUSDT', base: 'BTC', quote: 'USDT };
let market2 = { id: 'LTCBTC' base: 'LTC', quote: 'BTC' };

client.subscribeCandles(market1, '1m');
client.subscribeCandles(market1, '1d');
client.subscribeCandles(market2, '1d');

The above is a departure from existing patterns and would be a nice addition to the library.
Alternatively, as with orderbooks, candle subscriptions could be managed at a client level setting and the additional data would be automatically sent with the subscriptions.  For example:
let client = ccxws.binance();
client.candleInterval = '1m';
client.subscribeCandles(market);

Thoughts?

I will have to go through your code in detail and try to understand what you are trying to do. i have an implementation on my end of connecting various exchanges but it is very different conceptually than what you have implemented
The way I do it is at the heart of everything there is a monitor
The monitor simply takes previous symbols and compares them to current symbols
Each exchange extending the monitor uses a restApi and a wsApi
The restApi is responsible for methods that update the state of the monitor such as symbols
The wsApi is responsible for subscribing/unsubscribing to tickers trades candles and orderbooks based on the state of the symbols maintained by the monitor
The monitor fires a change event when the symbols change.
This change event is used to unsubscribe resubscribe etc
The wsApi of each exchange also has access to the restApi component of that exchange through a shared interface
Lol your method is radically different from mine. I will through it in absolute detail.
So far I see a bunch of client-spec files and it seems each exchange extends these spec files. Some rough explanation of the inner workings if mentioned in the documentation or anywhere else for the matter would be super appreciated

Ah sounds like an interesting approach. This code  is very much emergent as additional exchanges were implemented. The architecture started with a nice idea and definitely has some rough edges now. There is information on the architecture in the contributing guide that may be helpful.
Side note is that I have plans to refactor the integration tests into a single test fixture runner.  Once that is done it will ensure all clients have equal and thorough coverage. That should make future refactoring much easier.

The more I think about this, the more it makes sense to use a single configuration setting for the client to control candle resolution.
The most common use case is subscribing to a single candle resolution for a market (such as providing data to a chart).  Being able to subscribe to multiple resolutions for a market is a "nice to have" not a hard requirement.
Limiting to a single resolution is also a more universal implementation.  It prevents issues with clients such as Poloniex and Gemini that use a single event "room" per market that send updates for all types of data. For these types of clients, subscribes to multiple resolutions of candles at a time would necessitate multiple socket connections.  Essentially, we can't guarantee that a single socket allows multiple resolution subscription.
Lastly, this retains the same pattern as orderbooks where resolution data is attached on a per client basis.
The net result is that if a user wanted to subscribe to multiple candle periods at a time the user would be required to create multiple clients.
let client1 = new ccxws.binance();
client1.candleResolution = '1d';
client1.subscribeCandles(market);

let client2 = new ccxws.binance();
client2.candleResolution = '1m';
client2.subscribeCandles(market);

I

Why not just build candles out of trades? Put them in a bucket and periodically free the bucket while emitting an event?

Hi,
What is the status on this branch? do you have a roadmap for the merge?
Thanks!

Finishing up the baseline code and hoping to have it merged this week.

Initial implementation has been merged and includes Binance and Kraken. Still need to add support for Bibox, BitMEX, Cex, Coinex, Gate, HitBTC, Huobi, OKEx, ZB but that's going to be a work in progress.

Great work! I started playing with it and it works as expected.
I would add an optional "quote/symbol" field in the returned data, as it would remove the need to open an "exchange.on()" for every markets (leading to a MaxListenerExceededWarning)

Oh, nevermind, I just saw that it is automatically returned also!
This seems to be a wonderful new feature! Thanks again!

Amazing repo, thank you for your hard work, are you planning to add support for klines on more exchanges, currently I can see it works with 3 of them?

Yep, it's a work in progress.  Haven't had much time to work on it in the last month but hoping to get back into it over the next few weeks. I'll continue to update this issue as work is performed.

sorry to ask but i was wondering, its been a while since any changes were made to the kline section, are you working on it secretly or something, past few releases i havent seen anything on klines :) would be great to see something, keep up the awesome work

Not much progress unfortunately. I'm trying to free up a bit of time every week to work on this library. Finishing the klines is the next thing I want to chip away at.

authors: bmancini55 lejacobroy mypirateapp nightwolfz slidenerd


text:
Vim Solarized Looks Horrible in Terminal.app in Lion

Even though I use the Solarized theme in Terminal, Solarized isn't working in the normal mode. Terminal.app identifies itself properly as xterm-256color and tput colors reports 256, as does t_Co.   g:solarized_termcolors reports 16.
I have to use the 256 degraded mode.
if colors_name == 'solarized'
  if has('gui_macvim')
    set transparency=0
  endif

  if !has('gui_running') && $TERM_PROGRAM == 'Apple_Terminal'
    let g:solarized_termcolors = &t_Co
    let g:solarized_termtrans = 1
    colorscheme solarized
  endif

  call togglebg#map("<F2>")
endif

@vguerci I had the same issue today and actually ended up tweaking the terminal colors by hand, mostly just making them darker. The result isn't perfect, but it's certainly better than what it does by default

Don't know how much this will help, but I have a MacPro that I installed Terminal colors from https://github.com/altercation/solarized/pull/83 on, and it worked fine.  On my Macbook Air, the same colors give me the ugly grey background in vim.
Both are running 10.7.2, and have identical .vimrc & .zshrcs.  I'm really struggling to spot what the difference is...

Though, I have not tested #83, I have also fixed the colours in both Terminal and iTerm. I shall open my own pull request.
However, fixing the terminal colours is not enough. You also have to add logic to your .vimrc for Solarized to work properly.
" Color Scheme ----------------------------------------------------------- {{{

" Set the color scheme.
try
    set background=dark
    colorscheme solarized
catch /E185:/
    colorscheme default
endtry

" }}}

" Solarized -------------------------------------------------------------- {{{

 if exists('colors_name') && colors_name == 'solarized'
    " Text is unreadable with background transparency.
    if has('gui_macvim')
        set transparency=0
    endif

    " Highlighted text is unreadable in Terminal.app because it
    " does not support setting of the cursor foreground color.
    if !has('gui_running') && $TERM_PROGRAM == 'Apple_Terminal'
        let g:solarized_termcolors = &t_Co
        let g:solarized_termtrans = 1
        colorscheme solarized
    endif

    call togglebg#map("<F2>")
endif

" }}}

Unreadable Highlight in Terminal.app

Readable Highlight in Terminal.app

Unfortunately, all colours are altered, and it looks worse, but it is usable.

Another option to retain the original colours and make visual selection readable is to set the colour in vimrc.
" Solarized -------------------------------------------------------------- {{{

if exists('g:colors_name') && g:colors_name == 'solarized'
    " Text is unreadable with background transparency.
    if has('gui_macvim')
        set transparency=0
    endif

    " Highlighted text is unreadable in Terminal.app because it
    " does not support setting of the cursor foreground color.
    if !has('gui_running') && $TERM_PROGRAM == 'Apple_Terminal'
        if &background == 'dark'
            hi Visual term=reverse cterm=reverse ctermfg=10 ctermbg=7
        endif
    endif
    call togglebg#map("<F2>")
endif

" }}}

However, if you toggle the background, it will revert back to the unreadable visual selection colour. So, the toggle background code also has to be patched.
" Solarized -------------------------------------------------------------- {{{

if exists('g:colors_name') && g:colors_name == 'solarized'
    " Text is unreadable with background transparency.
    if has('gui_macvim')
        set transparency=0
    endif

    " Highlighted text is unreadable in Terminal.app because it
    " does not support setting of the cursor foreground color.
    if !has('gui_running') && $TERM_PROGRAM == 'Apple_Terminal'
         if &background == 'dark'
            hi Visual term=reverse cterm=reverse ctermfg=10 ctermbg=7
        endif

        function! PatchedTogBG()
            let &background = ( &background == "dark"? "light" : "dark" )
            if exists("g:colors_name")
                exe "colorscheme " . g:colors_name
                if g:colors_name == "solarized" && &background == 'dark'
                    hi Visual term=reverse cterm=reverse ctermfg=10 ctermbg=7
                endif
            endif
        endfunction
        command! ToggleBG :call PatchedTogBG()
        silent! nnoremap <F2> :ToggleBG<CR>
        silent! inoremap <F2> :ToggleBG<CR>
        silent! vnoremap <F2> :ToggleBG<CR>
    endif
    call togglebg#map("<F2>")
endif

" }}}

setting  following properties in .vimrc worked for me for mac terminal,
let g:solarized_termcolors= 16
let g:solarized_termtrans = 16

let g:solarized_bold = 1
let g:solarized_underline = 1
let g:solarized_italic = 1
let g:solarized_contrast = "high"
let g:solarized_visibility= "high"

My dotfiles -> https://github.com/prayagupd/dotfiles-mac/blob/master/.vimrc#L12

Not sure whether I'm doing this correctly but prayagupd's solution worked for me! I've spent a lot of time in macvim but I was missing my tmux bindings. Now my Vim looks pretty again! Thans a lot!

let g:solarized_termtrans = 1 resolved it for me; the background becomes the same as whatever terminal you are using.

authors: Rainymood ashah03 darthdeus jdelStrother prayagupd sorin-ionescu

repo: altercation/solarized


text:
🛑 roothouse-1 is down

In befcbf8, roothouse-1 (https://rhstatus-proxy.alterine0101.id/?deviceId=roothouse-1) was down:

HTTP code: 404
Response time: 584 ms

Resolved: roothouse-1 is back up in 0e27d56.


text:
🛑 roothouse-1 is down

In d6fca03, roothouse-1 (https://rhstatus-proxy.alterine0101.id/?deviceId=roothouse-1) was down:

HTTP code: 404
Response time: 258 ms

Resolved: roothouse-1 is back up in d91be72.


text:
Feature request: Support for the FictionBook format?

Specs description at: https://wiki.mobileread.com/wiki/FB2

Partially discussed in https://github.com/altescy/bookshelf/issues/2#issuecomment-706177299

authors: ligurio marek-lach

repo: altescy/bookshelf


text:
CDN Link Generator shows wrong libnode links for linux release branch.

Description of the problem
The CDN Link Generator shows libnode.so.102 for the release branch but currently libnode.so.83 is the latest libnode version for release branch.
Reproduction steps

Go https://docs.altv.mp/articles/cdn_links.html
Select release as branch and x64_linux as OS.
Check js-module checkbox.
Click Generate Links button.
The given libnode CDN link is this: https://cdn.altv.mp/js-module/release/x64_linux/modules/js-module/libnode.so.102

Expected behaviour
The given CDN link should be this instead: https://cdn.altv.mp/js-module/release/x64_linux/modules/js-module/libnode.so.83
Additional context
No response
Operating system

Version

Thats because dev already is changed to 102, not sure if i will add a branch check just for this, cuz we update node maybe once a year or something, so its not really worth

Thats because dev already is changed to 102, not sure if i will add a branch check just for this, cuz we update node maybe once a year or something, so its not really worth

If you run wget/curl https://cdn.altv.mp/js-module/release/x64_linux/modules/js-module/libnode.so.102 you will get 404 HTTP response because libnode.so.102 is not available in release branch. The peoples who are not aware of this bug are failing to get appropriate URL. As you said this might be fixed by itself when both dev and release branches have same libnode version but up to you.

repo: altmp/altv-docs


text:
weapon event cant work

Description of the problem
alt.on('playerWeaponChange', (oldWeapon, newWeapon) =>{
console.log('playerWeaponChange');
});
alt.on('playerWeaponShoot', (weapon, totalAmmo, ammoInClip) =>{
console.log(weapon, totalAmmo, ammoInClip);
});
when switch weapon or shoot, console have no output
Reproduction steps
see Description
Expected behaviour
see Description
Additional context
No response
Operating system
Windows 11
Version
release/12.10
Scope
server, client
Reproduction tested

[X] I confirm that I have made sure that this issue is also present on the newest dev version

In Version section you wrote release, but these features are only available in dev branch, see upcoming release on the docs:
https://docs.altv.mp/articles/changelogs/upcoming.html

In Version section you wrote release, but these features are only available in dev branch, see upcoming release on the docs:
https://docs.altv.mp/articles/changelogs/upcoming.html
also in the api docs it has "dev" only icon
https://docs.altv.mp/js/api/alt-client.IClientEvent.html#_altmp_altv_types_alt_client_IClientEvent_playerWeaponShoot

authors: PassWordE xxshady

repo: altmp/altv-js-module


text:
🛑 Angkor is down

In b407e35, Angkor (https://angkor-fougeres.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Angkor is back up in c01c38d.

repo: alxuy/upptime


text:
🛑 stamp.itove.com is down

In 1cffa9a, stamp.itove.com (https://stamp.itove.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: stamp.itove.com is back up in 21cd120 after 12 minutes.

repo: alzee/up


text:
APU's DMC channel

Hi,
I added the complete APU implementation with DMC to your project. Hope it's useful.

Hi,
It's very cool that you decided to do this! I hope you don't mind, but I would rather not merge this in because part of the point of my emulator was not to look at or use other people's emulator code. At some point, I might try to implement the DMC channel myself.
Just curious, how did you stumble upon my emulator, and what made you decide to do this? I'm genuinely interested as I haven't really advertised that I wrote this.
Thanks!

Sure, I figured out your objective after reading the README. Sorry, didn't know it before creating this pull request.
I'm having a pet project to add streaming feature to a NES emulator, so that I can play with friends over internet. The existing projects have netplay feature but it isn't suitable for my purpose. So I searched through github and found your project, which is really good and has MIT license, hence I like it, haha.

No need to apologize, I'm honored that you decided to use my emulator :)
Let me know how the streaming feature goes!

authors: amaiorano kakashidinho

repo: amaiorano/nes-emu


text:
[GSSOC'23] T-shirt Competiton

Is your feature request related to a problem? Please describe.
Actually I want to introduce a  t-shirt competion where there users will like or dislike the t-shirt the majority points will be getting badges on it . Can u please assgin me this issue under GSSOC'23
Describe the solution you'd like
this implementation will increase the creative spirit of the individuals
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct

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

i am raising this issue because the login and sign up is already created


text:
Add an SPI controller for reading

 Issue by HarryHo90sHK
Monday Dec 23, 2019 at 08:38 GMT
Originally opened as https://github.com/m-labs/nmigen-stdio/pull/2

On this pull request, I propose an SPI flash controller module exclusively for reading data or registers out of a flash device. Currently, it has:

_SPIFlashReaderBase: a base class from which can be inherited to create a new controller module, such as one that reads the ID of the flash device by issuing the opcode 0x9F (or 0x9E)
SPIFlashSlowReader: a module for normal reads from the device, meaning no dummy cycles of waiting is needed right after sending the address bytes to the device, while the read frequency is often capped.
SPIFlashFastReader: a module for "fast reads", meaning a faster frequency than normal reads while a number of dummy cycles of waiting is needed right after sending the address bytes.

Note that only the SlowReader but not the FastReader has been successfully tested on the ECP5 evaluation board.
In order to use the clock signal clk as the SPI clock for this module design, ECP5 requires the user NOT to request for SPI clock that corresponds to the on-chip oscillator (MCLK) but to instantiate a USRMCLK Instance. Therefore, to use this module and bulid the configuration bitstream on nextpnr without errors (see this comment), the user must avoid requesting for the normal clock pin from Ball U3 by some means. One way is to use my proposed modification of nmigen-boards.
I look forward to seeing further comments, thanks.

HarryHo90sHK included the following code: https://github.com/m-labs/nmigen-stdio/pull/2/commits

The PR is outdated and the author is no longer working on it.

authors: nmigen-issue-migration whitequark

repo: amaranth-lang/amaranth-stdio


text:
problem in nested 3.1.1 engines

I have a full 3.1.1 engine called Base2Cms. In the engine is a model named "Organization".
I have another engine that uses the Base2Cms engine that needs to extend the Organization model. The extension of the model looks like this:
require_dependency "#{Base2Cms::Engine.root}/app/models/organization"
class Organization < ActiveRecord::Base
has_one  :consumer_organization, :dependent => :destroy
has_many :meetings
has_many :subscriptions, :as => :parent_object, :dependent => :destroy
has_one  :supplier_organization, :dependent => :destroy
has_many :supplier_qualifications, :dependent => :destroy
accepts_nested_attributes_for :consumer_organization
accepts_nested_attributes_for :supplier_organization
end
Using the console to test with using "Organization.limit(10).page(1)", in the Base2Cms engine, works just fine. In the next engine, it generates the error:
undefined local variable or method `page' for #ActiveRecord::Relation:0x000001199c0260
Things like "Organization.first.subscriptions" works just fine in the second engine, so the model extension is working nicely. Just kaminari gets messed  up somehow.
Any ideas?  I've tried "require 'kaminari'" and other methods all over the place with the same results.
Kaminari version is 0.12.4

Let me firstly see if it still happens on master.
Can you please try bundling this?
gem 'kaminari', :git => 'git://github.com/amatsuda/kaminari'

Sorry...we already switched back to will_paginate....

authors: amatsuda fmorton

repo: amatsuda/kaminari


text:
Tai/input handler improvements

Not necessarily for this version
Implements https://github.com/amazingalek/owml/projects/1#card-41552452

Just tested with TAIcheat. Seems to work without any problem

repo: amazingalek/owml


text:
Update config.yml

i am learning it i am so sorry

i will not do this aggain i am sorry

repo: amazingandyyy/mern


text:
Language Supported

I added the attribute "languageCode" in the contact flow "VM-Greeting.json" with "ja-JP". But it does not work. However, when i use either "zh-CN or ko-KR". Both are ok. I suspect the transcribe service source-code got issue. Would you check the code is compatible with the language, ja-JP??  thanks

This is fixed with v1.1.0.

authors: khastation mfsuen


text:
Unique list generators

Finally got tired of project-specific non-polymorphic versions of this function and wrote it properly.
(Like all polymorphic solutions to "generate a list of n distinct values" these are partial, and should naturally only be used in tests.)

:+1: on comment wibble fix.

authors: erikd-ambiata olorin


text:
Java code generator uses the type annotations on the AST

This is part of the refactoring to be done to make the C codegen easier to write.

yep, this is definitely worth it. thanks for convincing me to do it properly :seedling:

authors: amosr jystic

repo: ambiata/icicle


text:
🛑 Wikipedia is down

In 35ffcea, Wikipedia (https://en.wikipedia.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wikipedia is back up in 97260bc.

repo: ameelan/adkbank-Upptime


text:
解决Intellij idea Java JDK多重选择提示问题

问题描述
objc[52336]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/bin/java (0x10942a4c0) and /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/libinstrument.dylib (0x1095a54e0). One of the two will be used. Which one is undefined.

配置Intellij Idea
1、打开idea.properties文件
help->edit custom properties
idea.no.launcher=true

2、在文件中添加一行
3、重启 idea 问题解决

我的idea还是有这个问题，jdk1.8.0112，idea2018

idea.properties 文件在哪……

help->edit custom properties 没有认真看噢 @FrankFang

authors: FrankFang ameizi beamaster

repo: ameizi/DevArticles


text:
big_core - create mif file using script as part of FPGA build

Use this script:
https://github.com/amichai-bd/rvc_asap/blob/main/apps/hex2mif.py
Make sure that the both i_mem & D_mem have offset 0x0000 on the generated MIF

@danielk532 Please make this your top priority - this will alow us to demonstrate DE10-lite FPGA.
The CR Write & Reads should be able to communicate with the Switch, button, LED & 7SEG without enable the VGA.


text:
DASH to HLS live

solution to restream live DASH stream to live HLS ?

See this example.

authors: aminyazdanpanah dromicron


text:
TypeError in /clan/popz-war-clan-y822upj

Error in ClashLeaders
TypeError in /clan/popz-war-clan-y822upj
Cannot read property 'value' of undefined
View on Bugsnag
Stacktrace
webpack:///js/components/ClanTable.vue?bf65:1 -

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
TypeError in /clan/popz-war-clan-y822upj

license: ISC


text:
Create file using file data

Hi,
How can i save the file in the external storage folder from URL?
createFile(data.uri,filename,mimetype).
Thank you.

First write the file to app cache folder with RNFetchBlob then use the copyFile function to move it to the folder you need.

repo: ammarahm-ed/react-native-scoped-storage


text:
Extend fetch validator script to local json files

User story

As a developer
I want / need the fetch validator script extended
So that I can extract data from a local json file

Acceptance criteria

Data from json files from industry partner can be extracted with the fetch validator script (json file can be found here: https://faubox.rrze.uni-erlangen.de/getlink/fi715pnEj7PPdtv2zsxgbF4x/)
Data stored in prometheus

Definition of done (DoD)

local json file can be analyzed

Feature DoD

Feature has been fully implemented
All acceptance criteria were met
All tests are passing
No known errors
Documentation updated
Bill of materials updated

Sprint Release DoD

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Peer code review passed
Developers agreed to release
Documentation updated
Bill of materials updated

For better application, a separate script is provided "convert_json_to_prometheus.py".

authors: A-Sandrini codeDavidLopez


text:
Make VSCode start an R session on startup

In the Dev Container, have it create an R session

Unfortunately, it's not currently possible to automatically start and attach to a new R terminal within a dev container due to limitations in the Visual Studio Code API.

repo: amphora/PatentSafeR


text:
chore(deps-dev): update PHP-CS-Fixer to ^3.x

This updates to PHP-CS-Fixer 3.x, and applies style fixes from the updated version.
Note: It looks like this strips the \ prefix for global namespaced functions. This can be configured with the native_function_invocation rule, however this is classed as risky so I wasn't sure whether to include it. 👍🏻 Let me know.

Thanks for the PR! This should really be done in https://github.com/amphp/php-cs-fixer-config/issues/6 instead and then use that package here. We've enabled risky rules, yes.

There's a v2 branch for https://github.com/amphp/php-cs-fixer-config/tree/v2 now based on php-cs-fixer v3.

@kelunik, I've updated this to use the v2.x branch 👍🏻

@owenvoke Thanks! :raised_hands:

authors: kelunik owenvoke

repo: amphp/parallel-functions


text:
Amplitude Cookies lifetime are not GDPR compliant

Amplitude default cookie configuration doesn't respect GDPR, as it states cookies tracking users should live no longer than 13 months (according to French CNIL) and 12 months according to GDPR itself (https://gdpr.eu/cookies/#:~:text=All persistent cookies have an,you do not take action.), while those created by the JS SDK live for 10 years by default.
I strongly suggest you change the default lifetime of cookies created by Amplitude SDKs to match this requirement (12 months). Here is a screenshot of cookies created by Amplitude JS SDK at https://nrn-v2-mst-aptd-at-lcz-sty-c1-amplitude-g.vercel.app/fr

This single violation of the GDPR makes Amplitude non GDPR compliant (according to my attorney).
Also, I haven't found any way of changing that behavior through configuration of the JS SDK at https://developers.amplitude.com/docs/javascript-sdk-reference, and I suggest such option gets added for people who'd have even stricter rules regarding cookies (or to gracefully handle any future change in the GDPR itself, regarding this particular matter).

@kelvin-lu Thanks for prioritizing this. Any idea when it might be done? Rough ETA? Q3/Q4 2020?

@Vadorequest we'll likely start with a fix this week /next week to change the default value to be gdpr compliant, and then look into optioning later on!

@Vadorequest I started looking over this (briefly) and I noticed that there's a cookieExpiration option that can be passed in to configure the # of days the cookie lives for - have you found this to work?
We're still planning on addressing the default value but wanted to bring this as a possible workaround for the time being!

Thanks for the hint, I hadn't noticed this option, is it documented? It
could indeed be a workaround. I'll have a look at it later on!
On Fri, Sep 11, 2020, 19:32 Kelvin Lu notifications@github.com wrote:

@Vadorequest https://github.com/Vadorequest I started looking over this
(briefly) and I noticed that there's a cookieExpiration option that can
be passed in to configure the # of days the cookie lives for - have you
found this to work?
We're still planning on addressing the default value but wanted to bring
this as a possible workaround for the time being!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/amplitude/Amplitude-JavaScript/issues/275#issuecomment-691222751,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5BRYW5YDTMT3HLYONPASTSFJNKVANCNFSM4PCVMWIQ
.

Only very lightly - and not with good documenting practices; apologies! We're in the process of updating our documentation to be more helpful and we'll keep this in mind! :)

I can confirm cookieExpiration: 365 does work! 😄
I believe this solves the original issue, since it allows us to control how much time a cookie can live, and make ourselves compliant with GDPR-related stuff.

This will be addressed in the next deployment - setting the cookie lifetime to 365 by default.

authors: Vadorequest kelvin-lu

repo: amplitude/Amplitude-JavaScript


text:
TypeError: Cannot assign to read only property 'writeQueueSize' of object '#'

Hi, I used this node on node-red and it raised excpetions like below.
22 Oct 16:38:42 - [red] Uncaught Exception:
22 Oct 16:38:42 - TypeError: Cannot assign to read only property 'writeQueueSize' of object '#'
at _clone (D:\work\source\Nodejs\node-red\node_modules\clone\clone.js:162:16)
at _clone (D:\work\source\Nodejs\node-red\node_modules\clone\clone.js:162:18)
at _clone (D:\work\source\Nodejs\node-red\node_modules\clone\clone.js:162:18)
at _clone (D:\work\source\Nodejs\node-red\node_modules\clone\clone.js:162:18)
at _clone (D:\work\source\Nodejs\node-red\node_modules\clone\clone.js:162:18)
at _clone (D:\work\source\Nodejs\node-red\node_modules\clone\clone.js:162:18)
at _clone (D:\work\source\Nodejs\node-red\node_modules\clone\clone.js:162:18)
at clone (D:\work\source\Nodejs\node-red\node_modules\clone\clone.js:202:10)
at Object.cloneMessage (D:\work\source\Nodejs\node-red\node_modules@node-red\util\lib\util.js:90:13)
at amqpReceiverNode.Node.send (D:\work\source\Nodejs\node-red\node_modules@node-red\runtime\lib\nodes\Node.js:409:61)
at Receiver. (D:\work\source\Nodejs\node-red\node_modules\node-red-contrib-rhea\rhea\rhea.js:262:26)
at Receiver.emit (events.js:198:13)
at Receiver.link.dispatch (D:\work\source\Nodejs\node-red\node_modules\node-red-contrib-rhea\node_modules\rhea\lib\link.js:59:37)
at Incoming.on_transfer (D:\work\source\Nodejs\node-red\node_modules\node-red-contrib-rhea\node_modules\rhea\lib\session.js:357:22)
at Session.on_transfer (D:\work\source\Nodejs\node-red\node_modules\node-red-contrib-rhea\node_modules\rhea\lib\session.js:728:19)
at Connection.(anonymous function) [as on_transfer] (D:\work\source\Nodejs\node-red\node_modules\node-red-contrib-rhea\node_modules\rhea\lib\connection.js:689:30)
I also opened an issue about it.
Now I changed the the code and now it works. Hope this code helps others.  Thanks.

Were you by any chance connecting the source node to two different nodes?
Ref: https://github.com/guidone/node-red-contrib-chatbot-discord/issues/4

I connected to both AMQP node and MQTT node. Messages from AMQP node were transformed and transferred to MQTT node. I think it is a common use case.

repo: amqp/node-red-contrib-rhea


text:
Objects through Ajax

Hello,
how can I get suggestions as objects through Ajax ?
I have a lot of repeated items in the suggestions list.
This is the modified suggestions.php file
<?php
$suggestions 	= [['tag'=>'India','value'=>34], ['tag'=>'Pakistan','value'=>12], ['tag'=>'Nepal','value'=>43], ['tag'=>'UAE','value'=>11], ['tag'=>'Iran','value'=>21], ['tag'=>'Bangladesh','value'=>22],['tag'=>'Italy','value'=>23], ['tag'=>'Australia','value'=>134]];

$data 			= [];

foreach($suggestions as $suggestion)
{
	if(strpos(strtolower($suggestion['tag']), strtolower($_GET['term'])) !== false)	{
		$data[] = $suggestion;
	}
}

header('Content-Type: application/json');
echo json_encode(['suggestions' => $data]);

Sorry for the late response and thanks for letting me know the issue. I have fixed it and published the latest version. Please check and confirm.

It works fine, thank you !
For initialization I set the value attribute to IDs
<input type="text" class="form-control" name="toAjax" value="India,Pakistan"/>
and populate suggestions
$('input[name="toAjax"]').amsifySuggestags({
           suggestions: [
		{tag: 'India', value: 34},
		{tag: 'Pakistan', value: 12},
           ],
	   suggestionsAction : {
		url : 'jquery-plugins/suggestags/examples/suggestions.php'
	   }
});

Is that right ?

No, input should have actual values separated by comma not tag names.
<input type="text" class="form-control" name="toAjax" value="34,12"/>

This works with objets, but not with objets through Ajax.
I tried, but this way the field contains the numbers.

Since, you are setting default value and using ajax, not only you need to set the actual value in html input.
<input type="text" class="form-control" name="toAjax" value="34,12"/>

It's all clear now.
Thank you very much for your great work and for your time.


text:
Running liquor-tree

I cloned the repository and was trying to run it following the README.md instructions but it didn't work.
I also noticed that out of the 23 dependencies 20 were outdated with 17 of those were by outdated by a major version or more. There were a lot of deprecated warnings and vulnerabilities including high danger. And @vue/test-utils should be updated from 1.0.0-beta.25 to 1.0.0-beta.30 it includes major breaking changes on the way asynchronous code works. And I'm having trouble testing components that involve liquor-tree.
It also warned me that the package.json didn't contain a licence field.
I was gonna add a role="treeitem" to the node template.
With a cleanly cloned project not building before changing anything then I'm not inclined to actually contribute to it, I'm not gonna do a pull request with a broken build.

Hi! Check the new version (0.2.69)

It's still not working, after cloning and doing npm install when I run npm run dev this is the output:
rollup v0.66.6
bundles src/main.js → dist\liquor-tree.esm.js...
[!] Error: 'default' is not exported by node_modules\vue-runtime-helpers\dist\normalize-component.js
https://rollupjs.org/guide/en#error-name-is-not-exported-by-module-
src\components\TreeRoot.vue (80:9)
78:
79:   export default {
80:     name: 'Tree',
             ^
81:     components: {
82:       TreeNode,
Error: 'default' is not exported by node_modules\vue-runtime-helpers\dist\normalize-component.js
...

When I run npm run build this is the output:
src/main.js → dist/liquor-tree.esm.js...
(!) Error when using sourcemap for reporting an error: Can't resolve original location of error.
src\components\TreeRoot.vue: (23:9)
[!] Error: 'default' is not exported by node_modules\vue-runtime-helpers\dist\normalize-component.js
https://rollupjs.org/guide/en#error-name-is-not-exported-by-module-
src\components\TreeRoot.vue (23:9)
21:             v-if="node && node.visible()"
22:
23:             :key="node.id"
             ^
24:             :node="node"
25:             :options="opts"
Error: 'default' is not exported by node_modules\vue-runtime-helpers\dist\normalize-component.js

Could you also had role="treeitem" to the TreeNodes? just like the Tree already has the role="tree".

Fixed. Problem was with "rollup-plugin-vue" package

Yeah rollup-plugin-vue breaks stuff. Maybe move away from rollup and just do the package using vue-cli-service.
With this I'm closing this issue, I've opened a PR with a few commits, please check them.

authors: I-Vargas amsik

repo: amsik/liquor-tree


text:
Adding a preloader

Is your feature request related to a problem ? Please describe. ✍
Enhancement
Your website is very beautiful .It will become more beautiful if while loading ,a preloader will be there. I can add the preloader to the website so that looks better.Can you assign this task to me?
Describe briefly how you would implement this enhancement.
Some steps to implement this enhancement-
1. Step 1- add a preloader
2. Step 2- give some styling to it
3. Step 3 -ADD required comments for better understanding of the code.

Additional context or screenshots
Additional context
Are you contributing for a program?
GSSoC2023
Code of Conduct

[X] I have read and agree to the Contributing Guidelines of this project.

That's a cool! have good preload with keep in mind that what is amupedia. Book preloader for eg.

I cannot find index.html in the folders. Can you please guide me about this.

we have _document.js

not getting any update
create new issue if you want to work on that


text:
remove calls to commit_particles in bridge.py

See #670 - commit_particles calls shouldn't happen here, the state model will take care of this.

If merged, this would close #670

yes, I agree!

the original commit doesn't mention any reason for adding the commit_particles, it was probably because the state model was a bit flaky at the time..

authors: ipelupessy rieder

repo: amusecode/amuse


text:
Doesnt work with cache-disabled: false

sdk-version: 30
build-tools-version: 30.0.3
ndk-version:
cmake-version:
cache-disabled: false

Full steps
name: Android CI
on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

jobs:
  build:
    runs-on: [ ubuntu-latest ]
    - name: Setup JDK
      uses: actions/setup-java@v3.12.0
      with:
        distribution: 'temurin'
        java-version: '17'
#        cache: 'gradle'

    - name: Setup Android SDK
      uses: amyu/setup-android@v2
      with:
        # default: false
        # Whether to use the cache
        cache-disabled: false

        # default: '30'
        # sdk version
        # see https://developer.android.com/studio/releases/platforms
        # It will always be installed.
        sdk-version: '30'

        # default: '30.0.3'
        # build tools version
        # see https://developer.android.com/studio/releases/build-tools
        # It will always be installed.
        build-tools-version: '30.0.3'

        # default: ''
        # cmake version
        # see https://developer.android.com/studio/projects/install-ndk
        # Installed when the version is specified
        # cmake-version: '3.10.2.4988404'

        # default: ''
        # cmake version
        # see https://developer.android.com/studio/projects/install-ndk
        # Installed when the version is specified
        # ndk-version: '23.1.7779620'

        # default: true
        # Whether to generate or not the job summary
        # generate-job-summary: false

Result:
https://i.imgur.com/DCJJNR0.png
But if set cache-disabled: true , then it works fine:
https://i.imgur.com/VDRisEs.png

:eyes:

Sorry for the late reply.
Is this problem still happening?
I cannot reproduce it on my end.
See below
https://github.com/amyu/setup-android/actions/runs/5992134798

@spamnick
Sorry for the late reply.
Is this problem still happening?
I cannot reproduce it on my end.
See below
https://github.com/amyu/setup-android/actions/runs/5992134798

Looking at your steps example, aren't you using GithubHostedRunner?
This Action is provided for SelfHostedRunner.
Please reopen if the problem is still not resolved

authors: amyu spamnick

repo: amyu/setup-android