text:
add retry for dict:incr in case of post event failed

Hi, I have the following problem when using Kong:

According to the function logic of updating the target of a service, in a node, the specific balance: targets: upstream_id will be expelled in on_upstream_event, which will execute invalidate_local (" balance: targets: upstream_id ") for all workers, and this function will call mlcache: delete (key) which deletes L2 and L1 caches. And the latter on_upstream_event -> get_upstream_by_id -> cache.get  show that If there is a value in L1, it will be returned directly. Otherwise, look for L2. If there is no value in L2, L3 will be called and  execute set shm_ set_ lru_。

Specifically, I have encountered a number of workers' inconsistency in the  balance: targets: upstream_id  cache. That is, some workers' L1 still caches old data, and at least one worker can read new data (combined with the implementation of lua-resty-mlcache: delete, this indicates that delete_shm is successful, but the problem may be caused by other workers' inability to remove the old data of L1 layer).
The following is the function call logic:
[kong] cache:invalidate(service_key,cluster) ---> [kong] self:invalidate_ local(key) ---> [lua-resty-mlcache] self.mlcache:delete(key) ---> [lua-resty-worker-event] post(channel_name, channel, data) ---> [lua-resty-worker-event] post_ event(source, event, data, unique) ---> [lua-resty-worker-event] dict:incr && dict:add
I think there may be problems in the following parts:
In lua-resty-worker-event's post_event function, dict: add has a retry mechanism(shm_retries), but dict: incr lacks a retry. If incr fails, it returns directly and interrupts post_event function.
In my problem, this will cause the invalidate event to not be inserted into the shm, so other workers cannot consume it, and other workers cannot remove the L1 layer data.
Refer to the implementation of dict: incr. When this function is called, a lock will be obtained. However, when there is high concurrency, other requests are also occupying the lock, resulting the dict:incr failure, thus interrupting post_event function and causes the invalidate event cannot be inserted into the shm, so that other workers cannot consume it.
implementation of dict: incr in lua-nginx-module

Since this function is designed as post event in shm, should we try to ensure the success rate of post? So I think we should also give dict:incr a few retries to avoid this to some extent like this:
https://github.com/Kong/lua-resty-worker-events/blob/master/lib/resty/worker/events.lua#L157
before:
_dict:add(KEY_LAST_ID, 0)
event_id, err = _dict:incr(KEY_LAST_ID, 1)
if err then return event_id, err end

after:
  _dict:add(KEY_LAST_ID, 0)
  retries = 0
  while not event_id and retries < 5 do
    event_id, err = _dict:incr(KEY_LAST_ID, 1)
    if err then
      return event_id, err
    elseif retries >= 5 then
      log(WARN, "worker-events: could not incr events-last-id to shm after ", retries,
              " tries. Payload size: ", #json, " bytes, ",
              "source: '", tostring(source), "', event: '", tostring(event))
    end
    retries = retries + 1
  end

Current status is that we're letting go of this library, in favour of event communications over unix sockets.

Current status is that we're letting go of this library, in favour of event communications over unix sockets.
@Tieske  Thank you for your reply. I looked at the implementation of the new library, and also did not provide the retry of event insertion (post_event && queue.put) to ensure successful insertion as much as possible. Do you want to leave the retry of failed event insertion to the method caller? In this case, should the relevant implementation of Kong also be adjusted?

I haven't been involved with the new lib. Maybe @chronolaw has ideas?

https://github.com/Kong/lua-resty-worker-events/blob/master/lib/resty/worker/events.lua#L291

Is this error in the log file?
@zjlooojoe
@Tieske

In lua-resty-events, we will report error if event publishing fails, then you can try to post it again.

If no out-of-memory error is reported, the retry code does not resolve it, it may be caused by another issue

Retrying makes sense to me, but I think the code is flawed. The goal is to retry both the dict:add and dict:incr operations if they fail. Both are done in a tight loop.

dict:add will on each retry expel a number of entries (30 iirc) from the LRU, until there is enough room to fit it in. So during the loop changes are made to improve the probability of success.
dict:incr will not change anything on a try. So I think the tight loop is bound to keep failing.

So can we add an exponential back-off to the dict:incr operation? that should improve the retry-success. (probably need to take care of yielding and non-yielding phases)

authors: Tieske chronolaw fairyqb zjlooojoe

repo: Kong/lua-resty-worker-events


text:
[12] feat(*) fix stream ffi function issues

Add @james-callahan's patches to fix stream ffi function issues.

See also: https://github.com/Kong/openresty-patches/pull/5

source: gharchive/pull-request

repo: Kong/openresty-patches

license_type: permissive

license_source: github-api


text:
Handle case unstake when active stake = 0

User report that the unstake button is not disabled even after unstaking everything

Expect:

If "Withdraw action" available -> Show button Withdraw on details screen (Move unstake action on "... button)
User click on "Unstake"

"Active stake" > 0 => Show unstake screen
"Active stake" = 0 and "Withdraw action is available" => Move unstake action on "... button" and disable button Unstake
"Active stake" = 0 and "Withdraw action not available" => Show popup with content:

Header: Unstaking not available
Message: You don't have any staked funds left to unstake. Check withdrawal status (how long left until the unstaking period ends) by scrolling down in the Details screen. Keep in mind that you need to withdraw manually.
Button: Check withdraw status

Click button -> Back to details screen (automatically open see more and scroll to bottom)

Version test: Mobile - v1.1.15 - Build: 261
Device test: IP 8 Plus (15.5)
Validation passed
https://konistudio-my.sharepoint.com/:v:/g/personal/nhungphung_koni_studio/EVCcBWSb_N1JulKrGhmAK6oBCS4XJprwzhT7lleHTCzfEA?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJPbmVEcml2ZUZvckJ1c2luZXNzIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXciLCJyZWZlcnJhbFZpZXciOiJNeUZpbGVzTGlua0NvcHkifX0&e=OFbJCS

source: gharchive/issue

repo: Koniverse/SubWallet-Mobile


text:
update api-schemas

[x] list of top/bottom cards  for decks where is revealed for player
[x] status of game - is_active: bool #97
[x] game/preset/faction merge with game/preset priority with query and use different option for priority (my, you, rand)
[x] game/next with query turn,phase as bool

faction = cia, kgb
priority = true, false, random

@chemeshuggah changes:

now game decks contains only pile (this not list of Card objects, this is list of cards names) and deck_len. pile_len field is removed

added PlayerGroupOrObjectivreCard schema. Here is:
        "example": {
            "is_in_deck": True,
            "is_in_play": False,
            "is_active": True,
            "position": 0,
            "name": "Master Spy",
            }

is_active mark - can player use group or objective card. Position mark position of card in deck, if it known by player

added field mission_card to game cards schema - in this field we observe mission objective card, defined in any turn

repo: KonstantinKlepikov/cold-war-boardgame

license: MIT


text:
Rationalisering af historikflag

For fire info punkt har vi p.t. flagene -K/--koord og -o/--obs til at håndtere udvalg af hhv. koordinater og observationer. Desuden foreligger en patch (#246) som, uden tilhørende flag, markerer om en punktinformation er historisk ("slukket") eller gældende.
@kbevers foreslår i kommentarsporet til #246 at indføre et mere overordnet tilvalg -H/--historik der kan styre alle aspekter af historikvisningen. Jeg tilføjer for egen regning: Valg af historikvisning for koordinater, (observationer), geometrier, punktinformationer.
Dertil hører også naturligt valg af om der skal vises tidsstempler (fra/til, bare fra, eller slet ingen) for historiksporet. Det vil næppe være praktisk at læsse al denne funktionalitet over på et enkelt, stakkels -H-flag, men det vil givetvis være værdifuldt at opbygge en lille gruppe af flag, der kan forbedre og strukturere historikvisningen.
Det er imidlertid en grundidé, der skal have tid til at modne - så mit forslag er at være åbne for merging af yderligere historikfunktionalitet, og så, efterhånden som behov og use-cases bliver tydeligere, diskutere -H og hendes potentielle søskende herunder.

Ville det mon fungere hvis historik var en alt-eller-intet ting, så -H giver historik både for koordinater og attributter, -K vælger hvilke typer koordinater der skal uddkrives, -O hvilke typer observationer - og måske et -L til at inkludere lukkede observationer?

Det tror jeg sagtens kan fungere.
Hvis det ændres skal dokumentationen (især workshopdelen) konsekvensrettes. Der er en del skærmbilleder som kommer til at være forældede.

@kbevers skriver ovre på #442 om fire info punkt med historik:

Nå ja. Den funktionalitet er jeg ikke sikker på er så nyttig som oprindeligt tiltænkt

Jeg har ikke skarp nok hukommelse til at forholde mig til hvad der oprindeligt var tiltænkt, men jeg bruger den funktionalitet noget nær dagligt for at kunne lave A/B-tests dels ved ilægning af nye data, dels på kryds og tværs af test/prod (fordi for længst udførte ændringer i test står tydeligt frem i forhold til prod).
Funktionaliteten ville være mere anvendelig hvis der var tale om et tilvalg (præcis som dette issue jo handler om) frem for standardhandlingen: Jeg har nok kun brug for -H cirka hver femte gang jeg taster fire info punkt (hvilket så i øvrigt nok sker ca. 25 gange om dagen)

Jeg har ikke skarp nok hukommelse til at forholde mig til hvad der oprindeligt var tiltænkt,

Det var vist meget specifikt noget med at kunne følge udviklingen i ATTR:bemærkning og evt. også ATTR:beskrivelse. Efter nu at have set det temmelig mange gange er jeg overbevist om at det ikke tilføjer speciel værdi i standardvisningen.

Det var vist meget specifikt noget med at kunne følge udviklingen i ATTR:bemærkning og evt. også ATTR:beskrivelse. Efter nu at have set det temmelig mange gange er jeg overbevist om at det ikke tilføjer speciel værdi i standardvisningen.

Lige præcis de to attributter er temmeligt ligegyldige i de fleste af mine sammenhænge: De fylder ganske rigtigt usigeligt meget hver gang der er rettet et komma, mellemrum eller noget endnu mindre (og netop derfor væsentligt at historik er et tilvalg, frem for en standard). Men for provokerede opdateringer (og bare generel nysgerrighed) er det ret anvendeligt til bevarelse af overblikket. Jeg ville nødig undvære det.

Jeg ville nødig undvære det.

Jeg skal lige sikre at jeg forstår dig ret. Du vil nødig undvære historikvisningen som standard? Eller er det generelt hvis man slet ikke kan se historikken? Sidstnævnte havde jeg ingen intention om at ændre ved.

Nej, jeg vil helst have historikvisning som tilvalg, for det er kun cirka hver femte gang jeg skal bruge den, og formodentlig meget sjældnere for alle andre. Men det medfører at punkt.punktinformationer også skal indeholde de historiske informationer - det var der diskussionen startede.

authors: busstoptaktik kbevers

repo: Kortforsyningen/FIRE


text:
Create ksl.json

initial descriptor for the Kotlin Simulation Library, https://github.com/rossetti/KSL

Thanks for accepting the merge.  I have one question and please forgive me for its stupidity. I tested my descriptor file locally. For example, %use ksl@file[/pathToTheFile/ksl.json].  It works fine. When I try to do %use ksl in my kotlin notebook I get Failed to process '%use ksl' command. Unknown library 'ksl@default'.  So, I wonder if there is a problem with my descriptor or some other issue that a newbie doesn't know about.

repo: Kotlin/kotlin-jupyter-libraries


text:
🛑 Annette is down

In 1ba67fd, Annette (https://annette-lartey.de/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Annette is back up in 3ce2042 after 44 minutes.

repo: KrisKodira/uptime-monitor


text:
🛑 Sebastian VmW is down

In 33cd850, Sebastian VmW (https://verkaufenmitwerten.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sebastian VmW is back up in 3f4c945 after 5 minutes.


text:
merge package template from arlac77/npm-package-template

package.json

chore(engines): update node@>=8.11 from template

.travis.yml

chore(travis): remove node versions 8.10
chore(travis): add node versions 8.11

:tada: This PR is included in version 3.3.18 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: Kronos-Integration/kronos-service-koa

license_source: bigquery


text:
Create Post “scascc”

Automatically generated by Netlify CMS

👷 Deploy Preview for gleeful-crisp-945073 processing.

Name
Link

🔨 Latest commit
a15f038a3d40935e7569b9cf7b5b0f1927a4d744

🔍 Latest deploy log
https://app.netlify.com/sites/gleeful-crisp-945073/deploys/63c245d89bb33d000959eb08

repo: KrzysPi/one-click-hugo-cms


text:
Consolidate env variable names

Currently env variables are used to configure limitador-server. We should consolidate these in some sort of prefix/namespace. LIMITADOR_ maybe? So that e.g. the currently LIMITS_FILE would become LIMITADOR_LIMITS_FILE.
We should also modify the logger to use the same prefix (currently RUST_LOG and RUST_LOG_STYLE)

Config the logger
diff --git a/limitador-server/src/main.rs b/limitador-server/src/main.rs
index 280cdf4..110cf02 100644
--- a/limitador-server/src/main.rs
+++ b/limitador-server/src/main.rs
@@ -5,6 +5,7 @@ extern crate log;

 use crate::envoy_rls::server::run_envoy_rls_server;
 use crate::http_api::server::run_http_server;
+use env_logger::Env;
 use limitador::errors::LimitadorError;
 use limitador::limit::Limit;
 use limitador::storage::infinispan::{Consistency, InfinispanStorageBuilder};
@@ -239,7 +240,13 @@ impl Limiter {

 #[actix_rt::main]
 async fn main() -> Result<(), Box<dyn std::error::Error>> {
-    env_logger::init();
+    if let Err(e) = env_logger::try_init_from_env(
+        Env::new()
+            .filter("LIMITADOR_LOG")
+            .write_style("LIMITADOR_LOG_STYLE"),
+    ) {
+        eprintln!("Couldn't initializer logger: {}", e);
+    }

     let rate_limiter: Arc<Limiter> = match Limiter::new().await {
         Ok(limiter) => Arc::new(limiter),

Might be "overruled" by #83 if we go for command line args… Or should we keep the logging configuration thru env vars maybe?

I think with the work done as part of CLI #92 We can leave this as is (so things remain backwards compatible, yet the new CLI based approached is favored)

repo: Kuadrant/limitador


text:
PicHoro的版本
1.9.9
系统信息
魅族16s，安卓10
问题重现 | Bug reproduce
打开软件就是白屏，无法进入
相关日志 | Logs
No response

参考 #29  试一下，估计是有权限没有给的问题

解决了，得手动给安装未知应用权限

解决了，得手动给安装未知应用权限

好的  现在安装未知应用的权限是在手动更新的时候才会主动获取，而不是第一次启动的时候，估计是这个原因。
后面我把这个的权限请求移动到第一次启动APP的时候应该就可以不用手动设置了。

authors: Kuingsmile sucooer

repo: Kuingsmile/PicHoro


text:
Tensorflow CUDA GPU support

Can i ask you to compile tensorflow aarch64 with CUDA 10.2 and Python 3.8 support ? I've installed your version, but it seems like it doesn't use GPU for calculations:

tf.config.list_physical_devices('GPU')
[]

I'm using NVIDIA's Jetson Nano device.
I'm trying to build it in a cross compile environment. But i spend almost month and tons of tries to, but still have no result.

Hi! The binaries provided here (both I compiled and Linaro's builds) are built on CPUs only.
To make use of Nvidia GPUs on an ARM board, I'm afraid that you'll have to compile it natively on your SBC.
Could you provide some errors printed while compiling?

authors: KumaTea gmernov


text:
Binary Search Tree  || Java

Is your feature request related to a problem? Please describe.
Binary Search Hasnt been done in java
Describe the solution you'd like
Will code it clear with a proper documented solution
Describe alternatives you've considered
A clear and concise description of the solution will done in other languages
Additional context
Other documentation will be added in the time of pr merge

Assigned!
@Abhinavkar : Java

Refer #92

authors: Abhinavkar Kumar-laxmi

repo: Kumar-laxmi/Algorithms


text:
spf: reintroduce CheckHostParams

r? @wez

lgtm, thanks!

authors: djc wez

repo: KumoCorp/kumomta


text:
Title: Creation of an editing software using Numpy

Is your proposal related to a problem? Please describe.
Yes with normal webcam or camera we can detect different kind of images  like Hsv , negative , gray scale ,detect face and rest all blurred, adding filters etc.

Most of people dont know that we can take thermal images using webcam or camera of laptop with numpy which gives same level of input as a thermal image-capturing device

We can capture live video in thermal, negative, grey etc

The highlight of this project is teaching usage of Python in image creation, manipulation etc

This project will teach how Python can be used to manipulate images and take different forms of images which have quality equivalent to devices used for detecting specific types of images

Add any other context or screenshots about the proposal request here.
No response

Sir in this issue i will create algorithm and core functionalities can u please label3 or 2 sir as it will be helpful for me ,I will be making it from scratch

@Kushal997-das Sir because of some exam issues I was not active project is ready if you open it I will push the code sir

@litesh1123 Submit it ASAP

Ok sir Thank you sir

@Kushal997-das Sir projects is done shall I add this folder to desktop application ?


text:
chore: secret generator add more test cases

What type of PR is this?

What this PR does / why we need it:
secret generator add more test cases
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., design docs, usage docs, etc.:

Pull Request Test Coverage Report for Build 7446928699

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 77.104%

Totals

Change from base Build 7444621980:
0.1%

Covered Lines:
8658

Relevant Lines:
11229

💛  - Coveralls

authors: adohe coveralls

repo: KusionStack/kusion


text:
New time command not working?

23:28:42 NadekoModule | Culture info is en-US
23:28:42 CommandHandler | Command Executed after 0/0/0/0.11s
        User: xnaas#7485 [83983966608068608]
        Server: Action Sack [141249302260350977]
        Channel: spam [226086096675667969]
        Message: -h !time
23:28:47 NadekoModule | Culture info is en-US
23:28:47 CommandHandler | Command Errored after 0/0/0/0.266s
        User: xnaas#7485 [83983966608068608]
        Server: Action Sack [141249302260350977]
        Channel: spam [226086096675667969]
        Message: !time Austin
        Error: Index was outside the bounds of the array.
23:28:59 NadekoModule | Culture info is en-US
23:28:59 CommandHandler | Command Errored after 0/0/0.016/0.25s
        User: xnaas#7485 [83983966608068608]
        Server: Action Sack [141249302260350977]
        Channel: spam [226086096675667969]
        Message: !time Austin, US
        Error: Index was outside the bounds of the array.
23:29:05 NadekoModule | Culture info is en-US
23:29:05 CommandHandler | Command Errored after 0/0/0/0.234s
        User: xnaas#7485 [83983966608068608]
        Server: Action Sack [141249302260350977]
        Channel: spam [226086096675667969]
        Message: !time London, UK
        Error: Index was outside the bounds of the array.

Perhaps I'm missing a requirement (API key?) for the command?

"Pretty" screenshot form for the bored? ¯\_(ツ)_/¯

(I assume your module is ! for that instead of the normal ~)
But yea, see the #announcements channel on Discord. You need to enable the Geocoding and TimeZone API if you haven't already on Google. No new key, works with the one already setup for self-hosters. :-)

Thanks @shikhir-arora, that would explain it then. Haven't been in the Discord server for many many months. 😛

Also yes @shikhir-arora, ~ is the worst fucking prefix ever.

authors: shikhir-arora xnaas

repo: Kwoth/NadekoBot

license: mit


text:
Automated Price Reserve Setup Fail

I met this kind of error when try to configuring Automated Price Reserve.

Command:

node liquidityReserveDeployer.js --config-path ropsten.json --gas-price-gwei 30 --rpc-url https://ropsten.infura.io --print-private-key true --network-address "0x3f9a8e219ab1ad42f96b22c294e564b2b48fe636"

Error details:

Error: Error: [number-to-bn] while converting number undefined to BN.js instance, error: invalid number value. Value must be an integer, hex string, BN or BigNumber instance. Note, decimals are not supported. Given value: "undefined"
    at Object.toBN (/Users/admin/Desktop/kyber-smart-contracts/node_modules/web3-utils/src/utils.js:64:15)
    at /Users/admin/Desktop/kyber-smart-contracts/web3deployment/liquidityReserveDeployer.js:159:46
    at Array.forEach (<anonymous>)
    at parseInput (/Users/admin/Desktop/kyber-smart-contracts/web3deployment/liquidityReserveDeployer.js:148:28)
    at Object.<anonymous> (/Users/admin/Desktop/kyber-smart-contracts/web3deployment/liquidityReserveDeployer.js:303:3)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
    at startup (internal/bootstrap/node.js:282:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)

I invested a bit of my time and recognized that in the guide you told that The most important properties are symbol, name, decimals, and address. The rest can be ignored. So you can specify your token details, filling in these fields. and indeed, you ignored them in ETH config.
"ETH": {
      "name": "Ethereum",
      "decimals": 18,
      "address": "0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee"
    }

However, when I come to liquidityReserveDeployer.js I saw,
const dict = {
        minimalRecordResolution : web3.utils.toBN(val["minimalRecordResolution"]),
        maxPerBlockImbalance : web3.utils.toBN(val["maxPerBlockImbalance"]),
        maxTotalImbalance : web3.utils.toBN(val["maxTotalImbalance"])
      };

So, obviously val["minimalRecordResolution" might be undefined in ETH and then led to the error.
What do you think? Please let me know If I missed something. In case I was right, please edit either your guide or your code to make them fit each others. Thanks for reading.

I got around by
const dict = {
      minimalRecordResolution: web3.utils.toBN(val["minimalRecordResolution"] ? val["minimalRecordResolution"] : 0),
      maxPerBlockImbalance: web3.utils.toBN(val["maxPerBlockImbalance"] ? val["maxPerBlockImbalance"] : 0),
      maxTotalImbalance: web3.utils.toBN(val["maxTotalImbalance"] ? val["maxTotalImbalance"] : 0)
    };

But it brought me to another error
deploying conversion rates
TypeError: Cannot read property 'bytecode' of undefined
    at deployContract (/Users/admin/Desktop/kyber-smart-contracts/web3deployment/liquidityReserveDeployer.js:82:53)
    at main (/Users/admin/Desktop/kyber-smart-contracts/web3deployment/liquidityReserveDeployer.js:222:61)
    at process._tickCallback (internal/process/next_tick.js:68:7) Promise {
  <rejected> TypeError: Cannot read property 'bytecode' of undefined
      at deployContract (/Users/admin/Desktop/kyber-smart-contracts/web3deployment/liquidityReserveDeployer.js:82:53)
      at main (/Users/admin/Desktop/kyber-smart-contracts/web3deployment/liquidityReserveDeployer.js:222:61)
      at process._tickCallback (internal/process/next_tick.js:68:7) }

This is my ropsten.json

can u try again now.
we fixed some conflicting web3 packages issue.
On Fri, Feb 15, 2019 at 6:35 AM Tu Phan notifications@github.com wrote:

I got around by
const dict = {
minimalRecordResolution: web3.utils.toBN(val["minimalRecordResolution"] ? val["minimalRecordResolution"] : 0),
maxPerBlockImbalance: web3.utils.toBN(val["maxPerBlockImbalance"] ? val["maxPerBlockImbalance"] : 0),
maxTotalImbalance: web3.utils.toBN(val["maxTotalImbalance"] ? val["maxTotalImbalance"] : 0)
};
But it brought me to another error
deploying conversion rates
TypeError: Cannot read property 'bytecode' of undefined
at deployContract (/Users/admin/Desktop/kyber-smart-contracts/web3deployment/liquidityReserveDeployer.js:82:53)
at main (/Users/admin/Desktop/kyber-smart-contracts/web3deployment/liquidityReserveDeployer.js:222:61)
at process._tickCallback (internal/process/next_tick.js:68:7) Promise {
 TypeError: Cannot read property 'bytecode' of undefined
at deployContract (/Users/admin/Desktop/kyber-smart-contracts/web3deployment/liquidityReserveDeployer.js:82:53)
at main (/Users/admin/Desktop/kyber-smart-contracts/web3deployment/liquidityReserveDeployer.js:222:61)
at process._tickCallback (internal/process/next_tick.js:68:7) }
This is my ropsten.json
https://trello-attachments.s3.amazonaws.com/5bdfb1ca38c3d5366cdfe564/5c474199f09703442f67093a/205ba18595b930704958293df9a50651/ropsten.json
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/KyberNetwork/smart-contracts/issues/388#issuecomment-463903632,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJt5hY_zfmyKr90ClcPh1uCBtz4zaSx9ks5vNjksgaJpZM4a86Ax
.

thanks @ilanDoron , I got around by ayobuenavista's patch.

authors: ilanDoron tphanson

repo: KyberNetwork/smart-contracts


text:
BUG: Boats in Boats appear & disappear as you interact with the game

iPhone model: 13 mini
iOS version: 17.6.1
App version: 1.2.1
When playing Boats, the rendering of the boats on the game grid and in the bottom "available boats" area tend to disappear & reappear as you play. I've noticed this primarily with the size-1 boat indicators while playing on "6x6 size 3 easy" difficulty. Everything still seems to function and the game can still be won, but the constant appearance & disappearance is very distracting.
This is probably an upstream issue, but I haven't built/played the x-sheep puzzles so I can't say for sure.
Here's an example of this type of behavior that I've been able to reliably reproduce:

Tap once to place a boat in the middle of an empty 3x3 area of the grid
Starting with the left-center of the 3x3 grid, working counter-clockwise, and ending at the upper-left, mark the 8 border cells around that boat as water by tapping them twice in a row (first tap turns it "on", second tap makes it water).
Result: The center boat disappears completely after you turn the last tile from "boat" to "water".
While in this broken state, use Menu > Restart. One of the size-1 "available boats" indicators at the bottom of the screen disappears completely.

As noted, there are other scenarios where the "available boats" indicators disappear, typically with the size-1 boat. Based on the steps above, I think it's mainly scenarios where you are marking the border around a size-1 boat as water by tapping twice (instead of long-pressing).

Thanks for the report. Confirmed I can reproduce - thanks for the detailed steos!
I suspect this is due in part to upstream code, but could also be a side effect of how I'm rendering the puzzles in the app (I'll spare you the gory details). I'll review a bit more and take a look at the upstream code.

Great news, I'm glad that you were able to get these resolved -- will definitely make the experience a lot smoother.

These changes (and all the other issues) are live in testflight, if you'd like to help test out: https://testflight.apple.com/join/WTgP9Te4
No pressure! I'll test and if I find no issues get it released to the app store in the next few days.

Issue fixed in 1.3 and released to app store. Closing as complete!

I've been using 1.3 since launch, and so far Boats seems to be rendering a lot more smoothly/consistently. I haven't seen any instances of this or any other visual glitches (same with Clusters / #13 ). Nice work, thanks!

authors: KyleDSwarner themowski

repo: KyleDSwarner/puzzles-reloaded


text:
Suggestion: If initial search is disabled, don't trigger a search until search is selected

Hi!
I like the new ability to disable the initial search, but I noticed that when I change the search criteria, it starts automatically searching.
It would be nice to have the ability to have no searching happen until search is selected. That way, if I want to choose 2+ different search criteria, I'm not doing extra searches before I'm "ready".
See my amazing photo-editing skills below:

Yeah I somewhat agree, but hopefully once you click search, you can make adjustments after, and it will auto search still, that way you don't have to click search 20 times for each adjustment.

Yeah I somewhat agree, but hopefully once you click search, you can make adjustments after, and it will auto search still, that way you don't have to click search 20 times for each adjustment.

Query Behavior (Run initial search off)
(A) Current:

Initial search doesn't start until a criteria is adjusted or Search is selected

(B) Your version (Maybe it should be the default behavior):

Initial search doesn't start until Search is selected.

After that, auto-search for each adjustment.

(C) My version (It's more clicks, but potentially less searches performed):

Searches only performed once Search is selected.

I think my preferred behavior in order of preference would be: C, B, A - But I think popular opinion would probably be for option B.

Hi, thanks for creating an issue. B is definitely my intended behavior of this feature. Unfortunately I've only tested it using the setting Debounce Time on infinite which results in behavior C. Will be addressed with the next version.

0.6.27 (2020-05-08)

fixed search triggered after changing filter if initial search is off (#682)

authors: EhhNahNoMouse Kyusung4698 conetopia


text:
Le téléchargement ne fonctionne pas sur firefox mobile

Erreur retournée au téléchargement dans firefox mobile: "Firefox ne peut pas télécharger ce type de fichier"
Alors que ça fonctionne bien sur Firefox sur un ordinateur.
Le problème a déjà été brièvement reporté dans le commentaire suivant:
Originally posted by @guillemcanal in https://github.com/LAB-MI/deplacement-covid-19/issues/2#issuecomment-610300920

Mozilla travaille sur le correctif:
https://github.com/mozilla-mobile/fenix/issues/9735
https://github.com/mozilla-mobile/android-components/issues/1159

Je viens de tester: ça fonctionne bien sur Firefox Release. Seule la version "Nightly" qui est une réécriture complète du logiciel a le souci.

merci pour ces précisions.
le problème est donc du côté de cette version nocturne du navigateur.

Bonjour, le problème étant identifié sur cette version du navigateur, nous fermons cet issue. Merci.

authors: bbinet infosteph julienw philippeBron sylvestre


text:
[bug] PC Client, no games on first launch

When launching the client and logging in for the first time, this is the screen:

It took a bit of messing with it to get the games to appear.
https://github.com/LANCommander/LANCommander/assets/5581855/73c9d706-ada4-4577-b3b2-07b54117089d

Fixed in 0.8.5

authors: miketweaver pathartl

repo: LANCommander/LANCommander


text:
训练较大的数据集

您好，请问如果想在该模型上训练类似HMER100K的数据集，需要调整什么超参数吗

您好，请问如果想在该模型上训练类似HMER100K的数据集，需要调整什么超参数吗

你好，在HME100K上可以将weight_decay调小一些，除了backbone之外的dropout可以设置为false，因为在大数据集上不容易过拟合。

好的，非常感激您的建议


text:
Correct Chinese corpus error

Using correct Chinese content from Wiki

Thank you for your concern. But this workload cannot be merged yet, if you finish cleaning up all the corpus, then we will merge it to the master branch.

@qiyuan-chen 你们开源的意图让我不解，你们并不是想通过让多数人参与进来一点点渐进式的完善和提高语料质量吗？想一次性把这么多数量的语料清理完再让你们合并？

authors: lindeer qiyuan-chen


text:
Use python2 to run

For example:
/usr/bin/env python2

I will try to add python3 support

#6 added


text:
Allows literal in InputLookupQA.

closes #1049

LGTM to me too.  Do we need to be concerned with RDF generation?

@peetucket I verified that RDF generation works correctly (as well as loading).

authors: justinlittman peetucket


text:
Aligns tabs for InputLookup.

closes #2575
Why was this change made?
It was a mess.
How was this change tested?
Locally.
Which documentation and/or configurations were updated?
NA


text:
New test case : Verify Enable-Disable SRIOV.

Azure now supports Enable/Disable Accelerated networking for existing VMs. This means, we do not need to delete and recreate the VMs to alter SRIOV status.

Execution on local machine is verified.
Jenkins execution is in progress...  (job-cloudtest-auto/5572)

Execution is verified.
09/06/2018 21:07:51 : [INFO ] ~~~~~~~~~~~~~~~TEST END : VERIFY-ENABLE-DISABLE-SRIOV-ON-EXISTING-VM~~~~~~~~~~
09/06/2018 21:07:51 : [INFO ] CURRENT - PASS    - 1
09/06/2018 21:07:51 : [INFO ] CURRENT - FAIL    - 0
09/06/2018 21:07:51 : [INFO ] CURRENT - ABORTED - 0
09/06/2018 21:07:51 : [INFO ] Checking background cleanup jobs..
09/06/2018 21:07:51 : [INFO ] Removed 0 context files.
09/06/2018 21:07:51 : [INFO ] Cycle Finished.. TC-44786
09/06/2018 21:07:51 : [INFO ]
Test Results Summary
ICA test run on 09/06/2018 20:28:55
ARM Image under test Canonical : UbuntuServer : 16.04-LTS : latest
Total Executed TestCases        1 (       1 Pass,        0 Fail,        0 Abort)
Total Execution Time(dd:hh:mm) 0:0:38
XML file: TestConfiguration

VERIFY-ENABLE-DISABLE-SRIOV-ON-EXISTING-VM Execution Time: 38.9 minutes
	VERIFY-ENABLE-DISABLE-SRIOV-ON-EXISTING-VM : PASS
		  EnableSRIOV : Test Iteration - 1 : PASS
		  DisableSRIOV : Test Iteration - 1 : PASS
		  EnableSRIOV : Test Iteration - 2 : PASS
		  DisableSRIOV : Test Iteration - 2 : PASS
		  EnableSRIOV : Test Iteration - 3 : PASS
		  DisableSRIOV : Test Iteration - 3 : PASS
		  EnableSRIOV : Test Iteration - 4 : PASS
		  DisableSRIOV : Test Iteration - 4 : PASS
		  EnableSRIOV : Test Iteration - 5 : PASS
		  DisableSRIOV : Test Iteration - 5 : PASS

Logs can be found at .\TestResults\2018-06-09-20-28-49-4095

09/06/2018 21:07:51 : [INFO ] Creating 'Azure-44786-buildlogs.zip' from '.\TestResults\2018-06-09-20-28-49-4095'
09/06/2018 21:07:51 : [INFO ] C:\LISAv2\PLBR44786\Azure-44786-buildlogs.zip created successfully.
09/06/2018 21:07:51 : [INFO ] Copied : .\report\report_TC-44786.xml --> .\report\report_TC-44786-junit.xml
09/06/2018 21:07:51 : [INFO ] Analysing results..
09/06/2018 21:07:51 : [INFO ] PASS  : 1
09/06/2018 21:07:52 : [INFO ] FAIL  : 0
09/06/2018 21:07:52 : [INFO ] ABORT : 0
Copying all files back to original working directory: C:\Jenkins-Slaves\azure-slave-2-executor-7\workspace\job-azuretest\job-cloudtest-auto.
Cleaning up C:\LISAv2\PLBR44786
Setting workspace back to original location: C:\Jenkins-Slaves\azure-slave-2-executor-7\workspace\job-azuretest\job-cloudtest-auto
09/06/2018 21:07:54 : [INFO ] LISAv2 exits with code: 0

Please follow up each open comment.

@juhlee-microsoft , @lizzha  comments are addressed.

authors: iamshital juhlee-microsoft


text:
Feature/nselliott/path class

Summary

This PR is a small code cleanup
It does the following:

Modifies some of the operations on path strings in IOManager to use axom::Path rather than conduit string utilities
Does not change the API
Addresses issue #754

Approved pending you fix your style problem.

repo: LLNL/axom


text:
Submodule conflicts

I attempted to use Serac as a submodule in CMake and ran into some small problems.

LGTM

LGTM

repo: LLNL/serac


text:
Adds serac subdirectory

#282

LGTM

Codecov Report

Merging #307 (abb5047) into develop (b0527b3) will decrease coverage by 5.07%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #307      +/-   ##
===========================================
- Coverage    90.33%   85.25%   -5.08%
===========================================
  Files           45       42       -3
  Lines         1604     1533      -71
===========================================
- Hits          1449     1307     -142
- Misses         155      226      +71

Impacted Files
Coverage Δ

src/serac/coefficients/coefficient_extensions.cpp
80.30% <ø> (ø)

src/serac/coefficients/coefficient_extensions.hpp
100.00% <ø> (ø)

src/serac/infrastructure/accelerator.cpp
28.57% <ø> (ø)

src/serac/infrastructure/cli.cpp
41.66% <ø> (ø)

src/serac/infrastructure/initialize.cpp
33.33% <ø> (ø)

src/serac/infrastructure/input.cpp
89.09% <ø> (ø)

src/serac/infrastructure/input.hpp
100.00% <ø> (ø)

src/serac/infrastructure/logger.cpp
4.87% <ø> (ø)

src/serac/infrastructure/profiling.cpp
25.00% <ø> (ø)

src/serac/infrastructure/terminator.cpp
0.00% <ø> (ø)

... and 38 more

Continue to review full report at Codecov.

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

LGTM

Thanks for this PR, Chris-- it's going to save me a lot of headaches when working in the smith repo!

authors: codecov-io samuelpmishLLNL white238


text:
[Bug] Read/write conflict when using local disk KV loading

Describe the bug
When the LMCache tries to retrieve the KV cache while the same KV cache is being stored on the local disk, the serving engine will generate wrong responses.
To Reproduce
Steps to reproduce the behavior:

Start the serving engine with the local disk backend
Send a request with a long context
Quickly send another request with the same long context before all the KV in step 2 has been written to disk

The problem may also be reproduced using offline inference

This is expected to be fixed by #94

repo: LMCache/LMCache


text:
INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS error (Windows Desktop)

Using my own lnd remote node.  Zap iOS wallet works perfectly.
Zap Desktop however all payments fail with error INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS (identical payments work on Zap iOS).
Windows 10.  Zap 0.7.2-beta
Happy to drop into slack to discuss / post any further info here.

I'm getting this error as well for the same version (0.7.2) but on Linux. Any more information on why this is happening or a possible work around?

repo: LN-Zap/zap-desktop


text:
Fix that we had redundant lnd rpc.proto files

Only one of these files was being used, and they were going out of step
relative to one another.
Also updated the def from:
https://github.com/lightningnetwork/lnd/blob/master/lnrpc/rpc.proto

@Empact this needs to be updated to apply cleanly to master due to a number of recent changes around how we manage the lnd client configuration.

Solved with #406. Thanks @mrfelton!

authors: Empact mrfelton


text:
Simnet Development Documentation

As new developers come and help us out, we should put up a nice Zap iOS + simnet guide, as it's likely the best developer environment

where do we want to put this? simnet repo? tutorial repo?
am i the one who has to do it? 😅

opened a PR with an example workflow on the simnet repo https://github.com/LN-Zap/simnet/pull/2

authors: JimmyMow ottosuess

repo: LN-Zap/zap-iOS


text:
Please add the source

Source name
The world of novels
Source link
https://realmnovel.com/
Language
العربية
Other details

Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

Fix the problem, open the comment and add the source.

repo: LNReader/lnreader-plugins


text:
Progress bar - better proportions

Since the tts buttons has been replaced by the bubble version, it's now possible.
Proportions taken based on Stable 1.1.19 except vertical (shorter than stable, longer than current beta)
If you want to make vertical like stable the height values is around 55vh
Current:

Modified (commit):

Im not OCD, but isnt 95.5 a not pretty number, the left and right space is 4.5/2=2.25 (2 number after decimal point)

95 is fine too. I just reproduced the proportions from stable.

authors: Palloxin nyagami

repo: LNReader/lnreader


text:
Single mass option for neutrinos

In discussion with @c-d-leonard: In issue #572, it was pointed out it would be convenient to have a "single mass" option for neutrinos, where instead of splitting a single number into a hierarchy or equal masses always, you could pass a single number and mean masses = (M, 0, 0). Obviously this is covered by the list option but there was a desire to have this simple option available as a named option as well.

We can add this to the API post-v2 without breaking things. Going to remove from v2 milestone.

Closed by PR #730

authors: beckermr c-d-leonard elisachisari

repo: LSSTDESC/CCL


text:
Eq. for EulerianPT calculator

This implements comparison between PT calculators beyond id.
The tracers seem to me to be complicated enough that the only practical and safe comparison is via id equality.

OK, done (although it seems a bit silly, since this is effectively a slower way of just checking ids atm)


text:
Generalizing Cl tracers

Closes #511
This will generalize the current treatment of tracers as described in #627
Tasks to accomplish:

[x] Generalize current 2D power spectra to arbitrary functions of k and a. These could be factorizable, and can be extrapolated in redshift in a different way than power spectra.
[x] Implement generic tracer structure in C. Main ingredients are: transfer function (a 2D function as above), radial kernel (a 1D spline), ell-prefactor (a discrete set of choices), Bessel derivative order (discrete set of choices).
[x] Make it possible to combine tracers at the C level.
[x] Hook the generalized tracers with the Limber integrator.
[x] Make the new structure visible from python.
[x] Make some specific tracer constructors for useful cases in python. At least they should cover the current set of tracers: NumberCounts (linear bias, RSDs, magnification), WeakLensing (with IAs), CMBLensing.

Some work still needs to be done:

[ ] Make sure that previous benchmarks pass (they do at the C level, so should do in python too)
[ ] Make new unit tests that validate the fully general tracers
[ ] Document everything!

So not fully ready for review, but ready for eyeballing if anyone is interested.

Pull Request Test Coverage Report for Build 3404

117 of 135 (86.67%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-1.07%) to 88.06%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pyccl/pk2d.py
0
4
0.0%

pyccl/tracers.py
104
118
88.14%

Files with Coverage Reduction
New Missed Lines
%

pyccl/core.py
1
95.96%

Totals

Change from base Build 3364:
-1.07%

Covered Lines:
649

Relevant Lines:
737

💛  - Coveralls

Alright, this is now ready for review. Tagging all relevant people @elisachisari @beckermr @jablazek @elikrause @slosar @jeremyneveu @jecampagne . It'd be ideal if at least a subset of you can have a look at this.
To facilitate the review, here's a summary of the changes:

Generalized tracers fully implemented as described in section 4.9 of the CCL note and in #627 .
The C implementation is coded up in src/ccl_tracers.c and include/ccl_tracers.h.
The C implementation is pure infrastructure. This means that there's no explicit functionality to compute number counts / weak lensing / CMB lensing tracers in C, only the infrastructure for the generalized ones. The convenience functions for the specific tracers now live in python.
Tracers and power spectra are linked in src/ccl_cls.c, which has also seen significant modifications.
I've had to disengage angpow entirely, so currently we don't have non-Limber functionality. This is temporary only until @jeremyneveu @jecampagne can provide the interface. I would propose that this happen in a different PR after this one gets merged. When writing the angpow interface, I believe the contents of section 4.9 in the note and the C docstrings should be sufficiently informative, and I'm more than happy to help here.
The python implementation lives in pyccl/tracers.py and pyccl/ccl_tracers.i. You can see the new constructors for NumberCountsTracers etc. in there, and how they all inherit from a general Tracer class that is now accessible to users.
The only change to the python API is that I've deprecated the red fraction argument for intrinsic alignments, as discussed in #639 .
I've adapted all existing benchmark checks and they all pass.
I've created unit tests for the generalized tracers in benchmarks/test_tracers.py. Since now we can pass whatever P(k) and transfer functions we want, these tests are based on matching power-law versions of these to their corresponding analytic expectation.

Alright, I think that's it!

OK, to try and entice people to review this, I've created a notebook that describes the functionality of the generalized tracers: https://github.com/LSSTDESC/CCL/blob/generalized_tracers/examples/GeneralizedTracers.ipynb

Sorry for the delay. I will be looking tomorrow.

will look next week. totally swamped this week - sorry for the delay.

Again, terribly sorry, but cannot look before after collab meeting by when others will be able to do it. (but if not happy to look)

This is great, @beckermr , thanks a lot! I'll address these ASAP.
Something very strange is happening where the linux tests are passing but all the C_ell tests are failing on OSX. If I look at the pytest error messages, it's failing when comparing the benchmark C_ells with the calculated ones, but this is not a matter of floating-point precision, both arrays are different by several orders of magnitude (which, again, doesn't happen on linux...).
I don't have easy access to a mac, but I wonder if you have any intuition why this might be happening.

I'll checkout the tests. you might try rebuilding without the cache on circle ci too.

I just ran the tests on my machine (macOS 10.14.5, via python setup.py test) and didn't encounter any issues.

Thanks a lot @tilmantroester
I'm really puzzled then about what's happening...

Yes thank you @tilmantroester! IDK how we can fix this if we cannot reproduce this locally. Let me dig into the CI env since I think I was the last person to touch it.

I can reproduce the failure locally on my Mac.

@elisachisari @sjoudaki : now the tests won't pass because of this silly error (remember, we're calling growth_factor now when implementing IAs because of the new parametrization):
CCLError: Error 1040: ccl_background.c: ccl_cosmology_compute_growth(): Support for the growth rate in cosmologies with massive neutrinos is not yet implemented.

Are you happy with me transforming this error into a warning in the code or even removing the error altogether? Otherwise we need to change our tests to avoid IAs for cosmologies with neutrinos.

And I'd like to again voice my discontent with this parametrization (even though I know it's the standard, and it's pointless to fight against it :-( )

Also, unless we fix this in the code, rather than the tests, it will come back to bite us in the bottom when we ever want to use CCL to do any analysis with neutrinos

Chatting with @damonge it seems the growth function includes massive neutrinos, just not the scale dependence. As we currently don't account for scale-dependence in the IA equation anyway, David's suggestion seems fine, i.e. for the error message to be turned into a warning.

I'm happy with the suggestion for the error to be turned into a warning. I am also open to discussing reverting to the old normalization if others find this preferable, in which case we should document this in the open issue regarding IA amplitude #280.

Sorry @elisachisari , I was just nagging above. I think it makes sense to keep whatever convention is the most common one (i.e. what you've implemented).
About the growth issue, I would rather fix that in a different PR. For now what I've done is avoid IAs in the tests when neutrinos are present, and all tests are passing now.

OK, now everything is passing (including coveralls), and Elisa has addressed the magic numbers issue.
We haven't received comments from other interested parties (@jablazek ?), but I have discussed this in detail with them during the collaboration meeting. So @beckermr , do you think we're ready to merge?

LGTM on merging. We need to make issues about any remaining tasks. I think this is just the growth function error?

https://github.com/LSSTDESC/CCL/issues/648

Thanks!

Hi all. Sorry - have continued traveling this week, and just looking at this now (post merge). In general, looks great. On the issue of IA normalization, I think CCL just should at least allow the standard convention to be used (even if it is annoying). With the new generalized tracer structure, where would be best to put in a different z-dependence? Should that go in specifying the IA amplitude itself (an array of A(z) values) or in the generalized transfer functions?

Hey @jablazek . No worries. @elisachisari has implemented the standard IA normalization in the custom IA tracer, so I think we're good on that front.

authors: beckermr coveralls damonge elisachisari jablazek sjoudaki slosar tilmantroester


text:
Refactor methods

informer\Informer::iterateOptionInfo()
ArrayDeserializer::deserializeSection()
ArrayDeserializer::getOptionName()
base\Section::addOptionInternal()
configurationEntities\base\Section::initType()
ArrayDeserializer::deserializeOptions()

B за методы приемлемо, пожалуй.

repo: LTD-Beget/sphinx-configurator


text:
Don't publish dependency scopes in BOM

As discussed, this PR takes care of removing dependency scopes from the BOM. It turns out that this was already fixed in Gradle 6.2, thus I only had to remove one line in the workaround for native artifacts.

Thanks!

authors: Spasi TheMrMilchmann


text:
Update README Environment and Software.Setup section

In order to run through your setup instructions properly, i had to install virtualenv
Adding a Requirements section that includes

pip install virtualenv
pip install jupyterlab

would be clearer to first time users starting up cyphercat.

created PR here: https://github.com/Lab41/cyphercat/pull/85


text:
Add basic auth.

All operations are currently full public. Need to restrict operations to those with basic authorization. For now, restrict all operations, then follow up with white-listing certain public operations.

Added in #14.

repo: LabAdvComp/indexd


text:
Issue 43420: Swap jTidy --> jSoup

Rationale
jTidy appears abandoned and doesn't support common HTML5 tag elements
Issue #43420: Replace jTidy with jSoup...or similar
Related Pull Requests

https://github.com/LabKey/server/pull/95

Changes

Swapped jSoup library in place of jTidy
TODOs

Additional code clean up
Expand unit tests
Use experimental flag/deprecation scheme?

Updated draft PR to get fresh test results: https://github.com/LabKey/platform/pull/4542

authors: labkey-ians labkey-jeckels

repo: LabKey/platform


text:
Control Module Script Fails if Clusters are Modified From Default After Sample Project Creation

This is because the original sample project will add a True to the 'Get Data Definition' VI and 'Get Index Definition'. These have to be changed manually if data is added to a method that was originally blank (or made blank when it originally had data).
A solution could be to see if these are set to False, but the clusters were changed to something other than ‘fmwk_placeholder’. The script could then also modify the data and index definitions appropriately.

The actual script is in tag editor core, will recreate the issue there

Control Module Script Fails if Clusters are Modified From Default After Sample Project Creation #252
https://github.com/LabVIEW-DCAF/TagEditorCore/issues/252

authors: Beazurt becega

repo: LabVIEW-DCAF/DCAFSampleProjects


text:
XML parsing issue with Entity Reference

Summary
There is an issue on function: https://github.com/LadybirdBrowser/ladybird/blob/c04297129323904f15c743eb83a3ff934769b14d/Userland/Libraries/LibXML/Parser/Parser.cpp#L754
I was able to figure out it is related to the parsing of Entity Reference. There may be an issue in there. Additionally, there is an Entity Reference grammar rule that seem not be implemented, namely [69] here https://www.w3.org/TR/2006/REC-xml11-20060816/#NT-Reference:
PEReference | ::= | '%' Name ';'
It's similar to the EntityRef one, so maybe easy to implement.
Maybe that's the cause of the issue.
Side note, just wondering, is it worth to develop our own XML parsing lib? Maybe it's better to use an existing, well-mantained FOSS one?
Operating system
Linux
Steps to reproduce

Go to https://yewtu.be/watch?v=5OYawYN9ZCs (or any Invidious video page really)
There seem to be an issue when parsing XML related to DASH. See here:

636.040 WebContent(5257): Unhandled JavaScript exception: [TypeError] Cannot access property "setVolume" on undefined object
636.050 WebContent(5257):     at set
    at https://yewtu.be/videojs/video.js/video.js?v=d8b893e:26371:21
    at <unknown>
    at https://yewtu.be/videojs/video.js/video.js?v=d8b893e:4412:20
    at <unknown>
    at https://yewtu.be/videojs/video.js/video.js?v=d8b893e:4411:29
    at https://yewtu.be/videojs/video.js/video.js?v=d8b893e:5078:11
    at <unknown>

:1: parser error : EntityRef: expecting ';'
ndwidth="130429" codecs="mp4a.40.2"><BaseURL>/videoplayback?expire=1730611585&ei
                                                                               ^
:1: parser error : EntityRef: expecting ';'
4a.40.2"><BaseURL>/videoplayback?expire=1730611585&ei=IbUmZ-HvFaaG6dsPuabvmAs&ip
                                                                               ^
:1: parser error : EntityRef: expecting ';'
mZ-HvFaaG6dsPuabvmAs&ip=2603%3Ac020%3A8002%3Aaa00%3A2711%3A7e46%3Aba4f%3Ac4a7&id
                                                                               ^
:1: parser error : EntityRef: expecting ';'
2711%3A7e46%3Aba4f%3Ac4a7&id=o-ACsSloeXB0SKqSw1-sxjdPdph5NzLAvhjxSxHfRjsjc0&itag
                                                                               ^
:1: parser error : EntityRef: expecting ';'
%3Aba4f%3Ac4a7&id=o-ACsSloeXB0SKqSw1-sxjdPdph5NzLAvhjxSxHfRjsjc0&itag=140&source
                                                                               ^
:1: parser error : EntityRef: expecting ';'

...
[dash @ 0x563d6ef169c0] Unable to parse '' - missing root node

Expected behavior
The thing should parse correctly and without error
Actual behavior
Parsing error
URL for a reduced test case
Not vailable
HTML/SVG/etc. source for a reduced test case
Couldn't extract a minimal case but the Invidious site still provide plenty

Log output and (if possible) backtrace
See above

Screenshots or screen recordings
No response
Build flags or config settings
No response
Contribute a patch?

[ ] I’ll contribute a patch for this myself.

+1 to adopting a mature OSS library for XML parsing

repo: LadybirdBrowser/ladybird


text:
Browser Devlopment key ?

@Laimiux
hi , m new to development and my need to embed some YouTube videos in my application, i read your library and i think it's a great idea. but the init function asks for a browser_development_key , what's that about ? how do we get that ?

Go to https://console.developers.google.com/ and create a project. In that project, enable Youtube Data API. Then, go to "APIs & Auth -> Credentials",  create new api key, select browser key and in the form you can leave the http refferers empty.

Got it Sir !
Cheers,
Vinit
On Oct 24, 2015 5:08 PM, "Laimonas Turauskas" notifications@github.com
wrote:

Go to https://console.developers.google.com/ and create a project. In
that project, enable Youtube Data API. Then, go to "APIs & Auth ->
Credentials", create new api key, select browser key and in the form you
can leave the http refferers empty.
—
Reply to this email directly or view it on GitHub
https://github.com/Laimiux/android-youtube-listview/issues/1#issuecomment-150793949
.

Hi! I can not get the browser Okay. In https://console.developers.google.com/ everything changed. He is now in the mail come? Help me please.

repo: Laimiux/android-youtube-listview


text:
Greg Shaughn - Unit 1 Sprint 4

still need to complete 2, 3, 4, stretch goals. finished step 1.

Good job encoding your dataframe, I like how you split the issues into their own columns and encoded your dataframe to integers. You're going about it the right way, keep practicing.
As for the kde plot, it's failing because one of your columns, or more, still have strings. I saw specifically the party column. One way to get around this would be to create a new dataframe that only has the issues, or make a boolean filter that only plots columns that are numeric.

You were on fire today! Looks like you really got the material under your belt and I love how you captured the relationship at the end with a violin plot. Really great work!

Good job encoding your dataframe, I like how you split the issues into their own columns and encoded your dataframe to integers. You're going about it the right way, keep practicing.
As for the kde plot, it's failing because one of your columns, or more, still have strings. I saw specifically the party column. One way to get around this would be to create a new dataframe that only has the issues, or make a boolean filter that only plots columns that are numeric.

Thanks for the advice!

Good work casting the features to float, one thing you can try to save yourself some time is playing around with pandas apply function, pandas.to_numeric, and astype.
https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.to_numeric.html
https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.astype.html
df = df.apply(pd.to_numeric, errors='coerce')
df = df.astype('float64')
Other than that you did a great job utilizing the stats libraries, making visuals for the feature relationships, and interpreting the results. Great work!

authors: edwardauron grommitt


text:
Sprint Challenge 1 - Evan Carlstrom

Contains all work prior to stretch goals.

One update after pull request was made to edit a value in index.css.


text:
Is there any documentation on how to install it?

As title, would like to install but no clues how to start.

It's a Kafka Connect Transform, so if you build the JAR, and place it on the connect CLASSPATH, (or plugin.path with Confluent 4.0), it should be available

I am using the connector "io.confluent.connect.elasticsearch.ElasticsearchSinkConnector" and would like to exclude certain fields to be sinked to a topic. Is this plugin allows to do a this filtering. If so, and provided I installed it in my classpath, is the curl command looks like something below?
curl -X "POST" "http://<my_ip>:28083/connectors/" \      -H "Content-Type: application/json" \      -d $'{   "name": "es_sink_abc",   "config": {     "topics": "abc",     "tasks.max": 2,     "connector.class": "io.confluent.connect.elasticsearch.ElasticsearchSinkConnector",     "key.converter": "org.apache.kafka.connect.storage.StringConverter",     "key.ignore": "true",     "schema.ignore": "true",     "value.converter": "org.apache.kafka.connect.json.JsonConverter",     "value.converter.schemas.enable": false,     "type.name": "kafka-connect",     "topic.index.map": "'abc:abc",     "connection.url": "http://elasticsearch:9200",     "connect.transforms.sql.value": "SELECT a, b as fieldSugar FROM abc"   }

That's how you would use it.
you can always check our connector for ES  https://lenses.stream/connectors/sink/elastic5.html
it has that capability you want as part of the configuration and you don't need the SMT.
I am going to close the issues, since it is not an issue and @cricket007 has responded to how you would use this.

authors: cricket007 kccheung stheppi

repo: Landoop/kafka-connect-kcql-smt


text:
Add chart to docker-chatbot example

Preview here:
https://github.com/LangStream/langstream/tree/example-chart/examples/applications/docker-chatbot#application-flow-chart

great stuff

authors: cbornet eolivelli

repo: LangStream/langstream


text:
Api 404

When opening the tool page in nova receiving the following error:
https://www.larabug.com/exception/YlK2xVCoMtdZcBj
Weird thing is, the error does get send to larabug.
So the config must be correct
Is the API down?

Can confirm! Same issue here!

Is this tool deprecated? If so, please close the repo

No, certainly not. Tool is in full development and working beautifully. If there's any error with this package for Nova, we'd accept any PR to fix/resolve this issue.
https://github.com/LaraBug/larabug-app
https://github.com/LaraBug/LaraBug

Would like to reopen this issue, since the issue is still there.
Do you have an idea to what the issue is? Would like to solve this, making a pr wouldn't be a problem

Still same server error, from larabug.
see: https://www.larabug.com/exception/0GWqvTvvZMR9WSf
Any clue?

I don't know what the issue is, if I would a fix would be easy to implement myself.
I haven't got the time to dive into that as of now. I'd recommend cloning it in your nova installation and try to see what the issue is.

Still same server error, from larabug.
see: https://www.larabug.com/exception/0GWqvTvvZMR9WSf
Any clue?

same as mine after installing this nova tool

authors: Cannonb4ll ao-jhelmich lloricode mamedia-edv

repo: LaraBug/nova-larabug-tool


text:
This is the Arabic translation for the Base and Crud

I Like your Project very much so I have translated the Base and Crud Lang files to the Arabic Language .
If you like you can merge them.
<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Backpack\Base Language Lines
    |--------------------------------------------------------------------------
    */

    'registration_closed'    => 'التسجيل مغلق.',
    'first_page_you_see'     => 'الصفحة الأولى التي تشاهدها بعد تسجيل الدخول',
    'login_status'           => 'حالة تسجيل الدخول',
    'logged_in'              => 'لقد سجلت الدخول!',
    'toggle_navigation'      => 'Toggle navigation',
    'administration'         => 'الادارة',
    'user'                   => 'المستخدم',
    'logout'                 => 'خروج',
    'login'                  => 'تسجيل الدخول',
    'register'               => 'تسجيل',
    'name'                   => 'الأسم',
    'email_address'          => 'عنوان البريد الألكتروني',
    'password'               => 'كلمة السر',
    'old_password'           => 'كلمة السر القديمة',
    'new_password'           => 'كلمة السر الجديدة',
    'confirm_password'       => 'تأكيد كلمة السر',
    'remember_me'            => 'تذكرني',
    'forgot_your_password'   => 'هل نسيت كلمة السر ؟',
    'reset_password'         => 'إعادة تعيين كلمة المرور',
    'send_reset_link'        => 'إرسال رابط إعادة تعيين كلمة المرور',
    'click_here_to_reset'    => 'اضغط هنا لإعادة تعيين كلمة المرور الخاصة بك',
    'change_password'        => 'تغيير كلمة السر',
    'unauthorized'           => 'غير مصرح',
    'dashboard'              => 'الصفحة الرئيسية',
    'handcrafted_by'         => 'Handcrafted by',
    'powered_by'             => 'Powered by',
    'my_account'             => 'حسابي',
    'update_account_info'    => 'تحديث معلومات الحساب',
    'save'                   => 'حفظ',
    'cancel'                 => 'إلغاء',
    'error'                  => 'خطأ',
    'success'                => 'نجاح',
    'old_password_incorrect' => 'كلمة السر القديمة غير صحيحة.',
    'password_dont_match'    => 'كلمة المرور غير مطابقة.',
    'password_empty'         => 'تأكد من ملء كل من حقول كلمة المرور.',
    'password_updated'       => 'تم تحديث كلمة السر.',
    'account_updated'        => 'تم تحديث الحساب بنجاح.',
    'unknown_error'          => 'حدث خطأ غير معروف. حاول مرة اخرى.',
    'error_saving'           => 'حدث خطأ أثناء الحفظ. حاول مرة اخرى.',
];

<?php

 return [
    "infoFiltered" => "(filtered from _MAX_ total entries)",
    "thousands" => ",",
    "admin" => "المشرف",
    "browse_uploads" => "تصفح التحميلات",
    "table_cant_add" => "لا يمكن إضافة :entity جديد",
    "clear" => "نظف",
    "save_action_changed_notification" => "تم تغيير السلوك الافتراضي بعد الحفظ.",
    "edit_translations" => "تعديل الترجمة",
    "internal_link_placeholder" => "Internal slug. Ex: 'admin/page' (no quotes) for ':url'",
    "table_max_reached" => "أقصى عدد :max تم الوصول إليه",
    "zeroRecords" => "لم يتم العثور على سجلات متطابقة",
    "infoEmpty" => "Showing 0 to 0 of 0 entries",
    "info" => "Showing _START_ to _END_ of _TOTAL_ entries",
    "details_row" => "هذا هو صف التفاصيل. عدل كما تريد.",
    "reorder_text" => "استخدام السحب والإفلات لإعادة الترتيب.",
    "reorder_success_message" => "تم حفظ ترتيبك.",
    "reorder_error_message" => "لم يتم حفظ ترتيبك.",
    "lengthMenu" => "_MENU_ records per page",
    "created_this" => "أنشئت هذه",
    "page_link_placeholder" => "http://example.com/your-desired-page",
    "actions" => "أفعال",
    "remove_filters" => "إزالة الفلاتر",
    "add_a_new" => "إضافة جديد",
    "reorder" => "إعادة ترتيب",
    "cancel" => "إلغاء",
    "choose_file" => "اختر ملف",
    "restore_this_value" => "استعادة هذه القيمة",
    "add" => "اضافة",
    "unauthorized_access" => "الدخول غير مصرح به - ليس لديك الأذونات اللازمة للاطلاع على هذه الصفحة.",
    "filters" => "الفلاتر",
    "to" => "الى",
    "reorder_success_title" => "انتهى",
    "search" => "بحث:",
    "toggle_filters" => "تبديل الفلاتر",
    "undo" => "تراجع",
    "edit" => "تعديل",
    "update_success" => "تم تعديل العنصر بنجاح.",
    "delete_confirmation_title" => "تم حذف العنصر",
    "delete_confirmation_message" => "تم حذف العنصر بنجاح.",
    "insert_success" => "تمت إضافة العنصر بنجاح.",
    "revision_restored" => "تمت استعادة المراجعة بنجاح",
    "loadingRecords" => "جار التحميل...",
    "infoPostFix" => "جميع السجلات",
    "details_row_loading_error" => "حدث خطأ أثناء تحميل التفاصيل. الرجاء اعادة المحاولة.",
    "delete_confirmation_not_message" => "حدث خطأ. ربما لم يتم حذف العنصر.",
    "guest_user" => "حساب زائر",
    "save" => "حفظ",
    "save_action_save_and_edit" => "حفظ هذا العنصر وتعديله",
    "save_action_save_and_back" => "حفظ و رجوع",
    "save_action_save_and_new" => "حفظ وعنصر جديد",
    "reorder_error_title" => "خطأ",
    "page_link" => "رابط الصفحة",
    "external_link" => "رابط خارجي",
    "internal_link" => "رابط داخلي",
    "preview" => "عرض",
    "back_to_all" => "عودة",
    "changed_the" => "غيرت",
    "in_the_database" => "في قاعدة البيانات",
    "list" => "قائمة",
    "all" => "كل",
    "no" => "لا",
    "emptyTable" => "لا تتوفر بيانات في الجدول",
    "no_revisions" => "لا توجد مراجعات",
    "language" => "لغة",
    "delete_confirmation_not_title" => "لم يتم الحذف",
    "delete_confirmation_not_deleted_title" => "لم يتم الحذف",
    "delete_confirmation_not_deleted_message" => "لم يحدث شيء. البند الخاص بك هو آمن.",
    "file_manager" => "مدير الملفات",
    "revisions" => "مراجعات",
    "delete" => "مسح",
    "processing" => "معالجة...",
    "from" => "من",
    "yes" => "نعم",
    "delete_confirm" => "هل أنت متأكد أنك تريد حذف هذا العنصر؟",
    "please_fix" => "يرجى تصحيح الأخطاء التالية:",
    "aria" => [
        "sortAscending" => ": تفعيل لفرز العمود تصاعدي",
        "sortDescending" => ": تفعيل لفرز العمود تنازلي"
    ],
    "paginate" => [
        "first" => "الأول",
        "last" => "الاخير",
        "next" => "التالى",
        "previous" => "السابق"
    ],
    "export" => [
        "copy" => "نسخ",
        "excel" => "Excel",
        "csv" => "CSV",
        "pdf" => "PDF",
        "print" => "طباعة",
        "column_visibility" => "رؤية العمود"
    ]
];

Thank you very much it was useful

hey thanks for this i can confirm it but you need to open pull request for each package translate,
also you have some improvements to do for example
كلمة مرور
you wrote it with two formats
كلمة السر
it should be the same concept for all phrases
so improve it and i'm sure it will be accepted ( don't forget to open pull requests for each package )

Totally agree with @iMokhles .
@allam2002 , wouldn't you like to create a PR with this, so that your contribution is registered on Github?

how to install ?

Merged a while back. Thank you @allam2002 !

authors: AlaaAo OdaiTu allam2002 iMokhles tabacitu

repo: Laravel-Backpack/CRUD


text:
Show getting started widget on dashboard (on localhost)

WHY
Addresses https://github.com/Laravel-Backpack/ideas/issues/170
BEFORE - What was wrong? What was happening before this PR?
After you installed Backpack for the first time, you were greeted by a blank dashboard, that did nothing to guide you on your next steps:

AFTER - What is happening after this PR?
On localhost, we show a different widget instead of the plain one, that instructs devs on the 3 important steps that would introduce them to Backpack:

HOW
How did you achieve that, in technical terms?
Added a view widget instead of the current one, when needed.
Is it a breaking change?
Yes and no... I mean... it's non-breaking, because it's only visual and only on localhost. But it's also breaking, because it's visual and it'll happen to existing projects that haven't customized their dashboard... To get rid of this, devs have to go to their config file and set it to false...
Is this ready?
I don't know... Let's call it an advanced first draft. I think it goes a long way towards introducing people to Backpack but... it's not as good as it could be... then again, it could take us a few weeks to polish this and create videos for it. So until then... this first draft is better than nothing...

Then if you click the last link here, new text will appear, to make some customizations:

And the other two accordion items are pretty basic:

And

What I don't know right now is if... I didn't go a bit overboard with explaining how to do password/unique validation, and using Model Events... Not sure if this qualifies as crash course (good) or too much, too soon (bad).
I'll sleep on it. Eager to hear what others think too.

Hey @tabacitu
I like the idea, I think it describes very well what should be the baby-steps to start interacting with Backpack.
I am with you on the "maybe a little too much" for the UsersController.
1- creating the controller ? ✅
2- Validation ? ✔ | ❌ (If anything, I think we should ONLY instruct developers to use the FormRequests. It addds alot of functionality not directly available in fields like the $stopOnFirstFailure, to where should user be redirected, preparing the validation etc. And it's the default Laravel way! All of this topics ofcourse are out of scope for this get started).
3- Password management? ❌ It's too many concepts and not directly related with Backpack in a "getting started".
I get why you pick the User model, it's already there ... But it's quite a complicated one to deal because of all the business logic it involves.
I would suggest we create something to add into users, like Address (hasOne) or Pets (hasMany). It would need one aditional step (create the migration), but we would show Backpack relationships (feature flag of this software).
We could then tell developers: now that you have this new Address for Users, it would be TOP if you could add the address directly when creating a new User, rigth ? We got you covered, there are two ways to proceed here:
a) we already did some of the hard work for you on the user management side, if you want to have user management in your Backpack application plus Roles and Permissions go ahead now and install backpack permission manager package.
b) If you simply want to have user management (without roles and permissions) follow me on how to create the User crud Controller:
....

I would tell everything as you did but would omit the password management part, make a note that it's required to properly work and point to permission manager crud controller where we already do that and keep that "simple" here.

Now lets add our Address relation into user controller
If you followed:
a) tell them to create a new controller, explain them how to override a backpack package controller to customize stuff etc. (probably point to a FAQ we should have online with exactly this question).
b) head to user controller and add in setupCreateOperation() add CRUD::field('address.street') and in ListOperation CRUD::column('address.street').
Very important lessons teached here and keeping a similar approach as you did.
Let me know what you think, if we can refine this idea.
Cheers

I get why you pick the User model, it's already there ... But it's quite a complicated one to deal because of all the business logic it involves.

I know... that's the downside of it...

I would suggest we create something to add into users, like Address (hasOne) or Pets (hasMany). It would need one aditional step (create the migration), but we would show Backpack relationships (feature flag of this software).

Creating a migration is a BIG extra step... that's not actually Backpack-specific. That's what annoys me. But you're right, Users don't show relationship fields... which IS in fact a big selling point... Damn...

Let me know what you think, if we can refine this idea.

Ok so I've decided. I don't like creating an Addresses CRUD. Because 99% of all projects won't need Address. So they have no reason to create it - just for learning, then they delete it... I wouldn't do that myself. And I expect it will deter people from actually following the steps. They'll think "Address... I don't need address... shut up".
That's what I liked creating a CRUD for User. In addition to the fact that the Model is already there, developers will probably keep the Users CRUD afterwards. And it's easier to convince people to follow our steps... if they were going to build that CRUD anyway. If it'll be useful to them, since 90% of all projects don't actually need roles and permissions - a Users CRUD is enough.

Now lets add our Address relation into user controller
If you followed:
a) tell them to create a new controller, explain them how to override a backpack package controller to customize stuff etc. (probably point to a FAQ we should have online with exactly this question).
b) head to user controller and add in setupCreateOperation() add CRUD::field('address.street') and in ListOperation CRUD::column('address.street').

No way, Jose. That's less useful to learn and it doesn't concern the main package (CRUD). It concerns an addon. The first things we should teach are the first things they should know - how to generate stuff, how to use Operations, how to use fields/columns. Everything else is "advanced", not "basic".

No, I'm convinced. We stay with Users - it's not perfect, but it's the best compromise. We've already hidden the complex stuff, and we can do a video for those later, to replace all the fluff.
PROs:

model is already there (fewer complex instructions)
devs are more likely to try it
it's actually useful (devs can keep it)

CONs:

doesn't show relationship fields;
to make it work well, it needs quite a bit of editing for the Create and Update operations;

I think the PROs heavily outweigh the CONs.

My question for you here Pedro was less about the tutorial. And more about the implementation. About when we show this widget - basically always on localhost, unless the dev has changed the config. This is OK for new projects in my opinion... but has implications for old projects - they'll start seeing this too... Just on locahost, but... it'll be a bad surprise, right? Then again, the widget itself shows how to hide it soo... maybe it isn't that bad? What do you think @pxpm ?

Let's just see if there is something more we can do here. As it is I am a little scary to approve this 🙃
We can try to make it work, but how we are implementing this, we are bound to break people applications in certain conditions.
I see the following scenarios:

new install ✅
old install without changes in dashboard ✅ (if they didn't change nothing in dashboard, probably they just removed the dashboard url and/or are not using the backpack dashboard page)
old install and changed backpack::base.welcome and/or backpack::base.use_sidebar ❌ ❌ ❌ ❌

What makes me a little relieved is the fact that we show this only on local, but I think we can do a little bit more to mitigate the failed scenario I referenced earlier.
Can we check if backpack::base.welcome and backpack::base.use_sidebar matches the backpack default texts ?

if dashboard is published they will not get this update ✔
if it's not published and the base.welcome message is still the default one, I think they are not using the Backpack provided dashboard, as the default message have no relevance/meaning for a non developer user. So the previous check for the messages would mitigate our concerns.

I think with these 2 checks we are reducing by 99% the chance of showing the widget in unwanted scenarios.
What do you think ? Is it overkill with no benefits ?
I would be more confident to say merge it, if we have some contention like that in place.
Let me know!
Cheers

Seems like we have the same reservations here Pedro. I'm also not 100% comfortable with merging this - exactly because of the scenario we leave out, that you mentioned. But I also think what you proposed is overkill so... yeah... merged it!

authors: pxpm tabacitu


text:
Вернуть апостроф, не поломав оформление

Вернуть в сообщение бота апостроф, убранный в PR #81, не поломав оформление.

Fixed in #83

repo: LaravelRUS/GitterBot


text:
Wording for allow/denylist

In response to https://nerdica.net/display/a85d7459-1663-a121-dbd1-41e364669631

Closed by https://github.com/Lartsch/FediAct/commit/6634889224fd55353dadcacf6784cedd959baf82

repo: Lartsch/FediAct


text:
Entrega documento Vision

Buenas,
No se si esto se notifica aquí, pero la fecha de entrega del documento de la definición de la visión está desactualizada (será la del año pasado), y creo recordar que es para mañana jueves. Aunque nos deja agregar la entrega, me gustaría comprobar que la fecha de entrega es mañana.
Un saludo

Admitida.
Sí, se notifica por aquí.

Verifica que esté arreglado.

Todo correcto

repo: LatacitaTeaching/IngenieriaRequisitos


text:
[Feature Request] Option to change directory for WinKeyServer/MacKeyServer

I noticed when I used the pkg module to package my node project into an exe, it would throw an error saying it could not find the WinKeyServer. I ended up having to change the path in WinKeyServer.js to get it to work. An option to change the path to the WinKeyServer would be nice to avoid this issue.

I vaguely remember this to already be the case...? After #20

It is. I did not know this existed. Thanks!
For anyone who needs the code:
new GlobalKeyboardListener({
    windows: {
        serverPath: "path/to/WinKeyServer.exe"
    }
});

authors: MrDiamondDog sancarn

repo: LaunchMenu/node-global-key-listener


text:
Events section

Don't ask, just merge 👍

I figured what is wrong. Will update this tonight after work.

I love how this PR started with don't ask anything, then bringing something up to approve to merge to revert the merge lol. What even happened here since my last comment

I love how this PR started with don't ask anything, then bringing something up to approve to merge to revert the merge lol. What even happened here since my last comment

Man, I did not see Keebs' review, merged and wanted then decided to revert but then I was like meh it won't hurt to leave it so I closed PR and then it got reverted again. TLDR; due diligence lacking.

All gooood homies! If anything its just a small thing to laugh together about😝
Take your time with fixing the issues and feel free to just make another PR when you're done Juan

authors: aidantrabs juancwu sshakibbb

repo: LaurierCS/Website


text:
README.md: unterminated code block

The README.md contains an unterminated code block

Fixed on master (v0.1.0).

repo: LaxarJS/ax-developer-tools-widget


text:
Adapt to breaking LaxarJS changes

Replace usage of fn.debounce with lodash.debounce
fn was completely removed from LaxarJS/laxar. This change was never applied here. Instead lodash.debounce should be used.
Explicitly use jQuery were needed
In LaxarJS 1.x jQuery was implicitly loaded to replace jqLite where possible. Since this is no longer the case, jQuery has to be used explicitly where necessary.

Fixed on master (v3.0.0).

repo: LaxarJS/laxar-show-hide-widget


text:
new plugin "leaflet-geoserver-request"

This is the plugin for various kind of GeoServer requests on leaflet map. For now, it has only four requests, i.e. wms, wfs, legend, wmsImage.

But... this looks like (another) WMS/WFS client, not something specific for GeoServer :-/

Well, I tested the requests with the Geoserver URL. The URL patterns for the request are set for GeoServer. I am not sure it will work for more than GeoServer. For now, it has four types of requests for fetch the GeoServer data,

WMS
WFS
legend
wmsImage

I tested the code by putting the baseLayerUrl as GeoServer base URL (eg. http://localhost:8080/geoserver/wms).

authors: IvanSanchez iamtekson

repo: Leaflet/Leaflet


text:
Fix incorrect VK_RETURN define (from 0x0C to 0x0D)

VK_RETURN is 0x0D as defined here:
https://docs.microsoft.com/en-us/windows/desktop/inputdev/virtual-key-codes
0x0C is VK_CLEAR.

Good catch!

authors: Leandros pmttavara

repo: Leandros/WindowsHModular

license: unlicense


text:
CallPlanner

Added CallPlanner action to RL_Bridge_Approach.

Closing in favor of #1670

authors: NishanthJKumar matrixbalto


text:
add Helium derivation path to application's access permissions

This PR gives the Solana Ledger App access to the Helium bip32 derivation path. This will allow the Helium Foundation to develop a migration tool to from the Helium bip32 derivation path to a standard Solana derivation path.
More details available here: https://docs.google.com/document/d/1AXalBlO03mMCtn8Bv8ngpr6_sE1V-6JX6DpET2dExRg/edit?usp=sharing
cc: @ChewingGlass

Hello @lthiery
Now that Helium has it's own app, can we drop this PR ?
App seems is here:
https://github.com/LedgerHQ/app-helium

Yes, thanks for pointing this out.

authors: fbeutin-ledger lthiery

repo: LedgerHQ/app-solana


text:
error on windows

windows 10
ledger nano s on ssh/pgp agent
trezor app -> right click -> show key
[24.03.2018 20:50:43] INFO: Java version: 1.8.0_131-b11 (64-bit)
[24.03.2018 20:50:43] INFO: Java home: C:\Program Files\Java\jre1.8.0_131
[24.03.2018 20:50:43] INFO: Trezor SSH Agent 1.0.3 started successfully
[24.03.2018 20:50:43] INFO: Existing settings file loaded: C:\Users\Frank\Trezor_Agent.properties
[24.03.2018 20:50:43] INFO: Trezor Service Started
[24.03.2018 20:50:43] INFO: Received USB event: SHOW_DEVICE_DETACHED
[24.03.2018 20:50:47] INFO: Request for operation: SSH2_AGENT_GET_IDENTITIES
[24.03.2018 20:50:47] WARNING: Trezor not ready.

I believe this is expected. The Trezor SSH Agent for Windows does not support the Ledger Nano S. This  may be more appropriate to report at https://github.com/martin-lizner/trezor-ssh-agent.

authors: chozian eightsixeight

repo: LedgerHQ/blue-app-ssh-agent


text:
questions about the input_height and input_width

last time,I use my data with the size of 15441284,and I resized it with 178218 as the  celeba dataset,but the result is not good.The generated picture is not clear,so I want to ask how to choose the size of data

When you train the GAN with your own data, hyperparameter tuning is needed.
(because GAN is very sensitive to dataset and hyperparameters)

Thanks,that is to say,I don't need to resize my dataset,but when I set the input_height and width with a big size,it dosen't work.Another question is that the picture would lost some information after crop in the training test ,if I want the GAN learn the whole picture ,do I need crop?

Sorry,I wonder the hyperparameter, does it contains the learning rate,beta1 and other? Thanks for you if you could explain more detail,and I am feel confused about what aspects should I adjust to suit my dataset

authors: LeeDoYup lzzlxxlsz

repo: LeeDoYup/AnoGAN


text:
🛑 Retamin2 is down

In 89addea, Retamin2 (https://app2.wisereport.co.kr/Home/ServerCheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Retamin2 is back up in 3d3cd18.


text:
🛑 MobileETFGlobal3 is down

In 281e053, MobileETFGlobal3 (https://mglobaletf3.wisereport.co.kr/Home/ServerCheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MobileETFGlobal3 is back up in 7c15ce7.


text:
🛑 MobileETFGlobal3 is down

In 0af72fd, MobileETFGlobal3 (https://mglobaletf3.wisereport.co.kr/Home/ServerCheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MobileETFGlobal3 is back up in 0a3ecfd.


text:
🛑 MobileCompanyGlobal2 is down

In 434cf40, MobileCompanyGlobal2 (https://mglobal2.wisereport.co.kr/Home/ServerCheck) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MobileCompanyGlobal2 is back up in d065b2d.


text:
App names containing "."

Just added this to a project based on Django-cookiecutter which uses a hierarchical app structure.
So the app names are 'foo.bar', etc.
This seems to break the visualisation for some reason I have not yet determiened. Not in a great position to debug the issue at present, will update with more details once I have a chance.

Hey @techdragon why did you close this, happy to take a look at this if need be.

Oh wait... I just saw it was left open for a year. My bad :(

Looks like this is still true on master?

NVM, looks like you can make it work by dropping the prefix/ matching whatever the app_name is on the model.

authors: LegoStormtroopr tclancy techdragon


text:
?activatemodule Tickets doesn't work

Bugreport:
Bug reported by Fabiooo
Is it a bugreport for the website or for the bot?: bot
What is the title of your bugreport?: ?activatemodule Tickets doesn't work
How can you reproduce the bug? (Explain in steps): ?deactivatemodule Tickets and then activate it
Which result would normally have to be?: It should be activated
What happens if you do the action now?: i't will not activate
ReportID: 76
┆Attachments: http://prntscr.com/l8cc6f

➤ LenoxBot commented:
?deactivatemodule also doesn't work with Tickets
Fabiooo

➤ LenoxBot commented:
fixed - pls approve
Dadi

➤ LenoxBot commented:
Approve:
has been fixed
Monkeyyy11

➤ LenoxBot commented:
Approve:
could be reproduced
Dadi

➤ LenoxBot commented:
Approve:
fixes
Wandi

repo: LenoxBot/LenoxBot


text:
custom-bootbackup.sh

The script doesn't work correctly. Probably some logic errors.
May be also related to the rsync statement I use.

Additional Flags:

-q

I am not certain that this actually is the problem.
It might also be related to the PARTUUID again

This is solved

repo: LeoMeinel/mdadm-encrypted-btrfs


text:
can't able to install types from npm

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@types%2Fanimated-number-react - Not found
npm ERR! 404
npm ERR! 404  '@types/animated-number-react@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

Hi @jeetrabadiya this package doesn't have types

@Leocardoso94 so how we can use in react-typescript?

@Leocardoso94 No problem... I have created custom d.ts file for this packages. Maybe it will help to those people who want to use this package in react-typescript.

@Leocardoso94  can you please add types for this package? I really want to use this in typescript.

@magic990619 I have a solution for types issue. Please refer this comment it will work for typescript.


text:
Tutorial 0. Introduction

Tutorial 0. Introduction
Would you like to participate in the writing of this tutorial?
Or do you have a question about this tutorial?
Let us know here!
Description
The objective of this introductory tutorial is to explain the general principles of cross-decomposition algorithms, their possible applications and practical considerations. It should introduce and refer to the other tutorials.
This tutorial should also give an overview of the different cross-decomposition algorithms that exist, including CCA, PLS regression, PLS canonical, PLS-PM (for more than 2-blocks of variables), etc.
Useful references

Cross-decomposition in scikit-learn: scikit-learn documentation for the cross-decomposition module (CCA, PLS regression, PLS canonical). Note that the documentation should be updated soon (see current pull request, corresponding branch).
PLS-PM: "PLS Path Modeling with R" Gaston Sanchez
PLS-PM in Python
PLS methods for neuroimaging: Krishnan, Anjali, et al. "Partial Least Squares (PLS) methods for neuroimaging: a tutorial and review." Neuroimage 56.2 (2011): 455-475.
CCA for neuroscientists: Wang, Hao-Ting, et al. "Finding the needle in a high-dimensional haystack: Canonical correlation analysis for neuroscientists." NeuroImage (2020)

We will work on this tutorial with @IsabellaBreukelaar!

Just created a pull request for some text I added to this tutorial, everyone feel free to improve on this as this is a my first go at interpreting these methods.

authors: IsabellaBreukelaar LeonieBorne

repo: LeonieBorne/plstuto


text:
Example on how to use the upload_name function?

Hi there, thanks for all the hardwork on this package.
I'm just reading through the docs but struggling with how to properly use the upload_name function. Would you be able to share a very brief example within the S3.upload call?
Thanks!

Also very interested in this

authors: andregoldstein johnmore


text:
[报错] 本地部署访问链接时返回报错

Error: Could not find expected browser (chrome) locally. Run npm install to download the correct Chromium revision (961656).
at ChromeLauncher.launch (D:\mirai\WS\WebStack-Screenshot\node_modules\puppeteer\lib\cjs\puppeteer\node\Launcher.js:101:23)
at async Server.module.exports (D:\mirai\WS\WebStack-Screenshot\src\main.js:30:15)
{"msg":"Screenshot failed"}

执行了npm install了吗？
因该是没有成功安装chromium


text:
Quickstart

Build the browser distribution
npm install --g browserify
git clone https://github.com/Level/level-browserify.git
cd level-browserify
npm install .
browserify browser.js --standalone level > level-browserify.js

Include level-browserify.js using a script tag in your html page
<script type="text/javascript" src="level-browserify.js"></script>

Run the following code in your app
var database = level('./test_database');
database.put('key', 'value', function(error) {
	database.get('key', function(error, value) {
		console.log('value:', value)
	});
});

I'm not sure what the actionable item is here. If you feel like the readme doesn't provide enough information, feel free to reopen, or to send a pull request! :)

authors: simplygreatwork vweevers

repo: Level/level-browserify


text:
fix: BrnIconButton fontSize 标记废弃

优化建议：#349

那可能，还要考虑下。

repo: LianjiaTech/bruno


text:
Notebook export bug (from upstream autopep8)

We're affected by this issue in autopep8 when exporting a notebook:
https://github.com/hhatto/autopep8/issues/689
specifically in:
  File "D:\...\envs\lt_release012\Lib\site-packages\libertem\web\notebook_generator\template.py", line 36, in code_formatter
    return autopep8.fix_code(code)
           ^^^^^^^^^^^^^^^^^^^^^^^

From activity on the issue it looks like it will soon be handled ?
#1476

Seems like a solution is to pin pycodestyle to 2.10.0.

Seems like a temporary solution is to pin pycodestyle to 2.10.0

Yeah, probably <2.11 is the correct pin, to not be overly strict

I'll take care of this one - theoretically the notebook tests should also reproduce the issue, I'll see if that is the case

repo: LiberTEM/LiberTEM


text:
Improve clustering analysis

Closes #596

Reduce memory footprint and improve speed by using a connectivity matrix
Use faster ApplyMasksUDF to generate a feature vector
Don't use delta and binary vector, instead use normalized float values

[x] Update screenshots and documentation
[x] Review tests
[x] Correct PR in changelog
[x] Update notebook with new file and feature vector method

Contributor Checklist:

[x] I have added myself to the creators.json file
[x] I have added a changelog entry for my contribution
[x] I have added/updated documentation for all user-facing changes
[x] I have added/updated test cases

Looks good, merged! :+1:


text:
Add Keystone 54 Battery Clips Package

Part: https://www.digikey.ch/product-detail/de/keystone-electronics/54/36-54-ND/2254090
Mechanical drawings: http://www.keyelco.com/product-pdf.cfm?p=826
Datasheet for battery contacts: http://keyelco.com/userAssets/file/M65p11.pdf
So far I have only created the package variant for the unprotected 18650 cell. I'd like some initial feedback (@ubruhin), if everything is OK I'll add other variants (e.g. protected 18650 which is a bit longer, and the other supported cells).
One thing which I'm a bit unsure about is whether we should use round holes (like in the datasheet) or oblong shapes that match the pads. The latter would be easier to solder while the former would be easier to manufacture (a simple drill, no milling).
I'm also unsure about the category. I put it in "Connectors" but that's not really fitting. Maybe we should have a category "Battery Clips" below connectors?

I'd like some initial feedback

Looks good IMHO :+1: Just some small thoughts:

I would swap the pads "-2" and "-3" (since the two holders are identical, the pads should be numbered identically). Of course that has no functional impact, it's just more intuitive IMHO :)
The documentation layer should also contain the outer dimension of the holders, not only of the battery.
Maybe use a slightly thicker line for the battery outline? For such a large part the 0.2mm look very thin :)
Adding a polygon on the courtyard layer would be nice to indicate the space on the PCB which is occupied by the holders and the battery. That's useful to avoid placing other parts too close to the battery/holders.

I would love to see points 1. and 2. implemented - 3. and 4. are nice to have, I would also approve if those aren't implemented (yet).

One thing which I'm a bit unsure about is whether we should use round holes (like in the datasheet) or oblong shapes that match the pads.

Since LibrePCB does not yet support oblong pads (WIP in https://github.com/LibrePCB/LibrePCB/pull/423), this question is easy to answer :grin:

I'm also unsure about the category. I put it in "Connectors" but that's not really fitting. Maybe we should have a category "Battery Clips" below connectors?

See also https://github.com/LibrePCB-Libraries/LibrePCB_Base.lplib/issues/31#issuecomment-506973238. Maybe add it to "Manufacturer-Specific -> Keystone", with the option to also add a "Battery Clips" category some time in future?

@ubruhin should be ready for review now.

authors: dbrgn ubruhin


text:
Adding component and package categories for my previous PRs

These are needed for some of the parts in my other PRs. Please review/merge before:

https://github.com/LibrePCB-Libraries/Cree.lplib/pull/1

https://github.com/LibrePCB-Libraries/Diodes_Incorporated.lplib/pull/7

https://github.com/LibrePCB-Libraries/LibrePCB_Base.lplib/pull/71

https://github.com/LibrePCB-Libraries/LibrePCB_Base.lplib/pull/72

https://github.com/LibrePCB-Libraries/LibrePCB_Base.lplib/pull/73

https://github.com/LibrePCB-Libraries/LibrePCB_Base.lplib/pull/74

https://github.com/LibrePCB-Libraries/LibrePCB_Base.lplib/pull/75

https://github.com/LibrePCB-Libraries/LibrePCB_Base.lplib/pull/76

https://github.com/LibrePCB-Libraries/LibrePCB_Base.lplib/pull/77

https://github.com/LibrePCB-Libraries/LibrePCB_Base.lplib/pull/78

https://github.com/LibrePCB-Libraries/LibrePCB_ICs.lplib/pull/23

https://github.com/LibrePCB-Libraries/LibrePCB_ICs.lplib/pull/24

https://github.com/LibrePCB-Libraries/LibrePCB_ICs.lplib/pull/25

https://github.com/LibrePCB-Libraries/LibrePCB_ICs.lplib/pull/26

https://github.com/LibrePCB-Libraries/LibrePCB_ICs.lplib/pull/27

To be honest, I even think we don't need most of these categories:

Component Category "Magnetic Field Sensors" -> this looks OK to me :+1:
Component Category "Potentiometers" -> I'd simply add potentiometers to the "Resistors" category. When selecting the "Resistors" category, the user will then see the potentiometer components next to the fixed value resistor components, which makes sense to me.
Package Category "Potentiometers" -> There are no standardized potentiometer packages, thus I'd say it's (currently) not worth to add a package category for it. Use "Miscellaneous" and/or "Manufacturer-Specific" instead.
Package Category "THT LED" -> Rename to "Through-Hole LED", then I think it's OK :+1:
Package Category "Sensors, Transducers" -> This does not really describe a package category, but component category. Sensors can have almost any package, there is no typical kind of package for sensors. So this category should not be added.
Package Category "Switches" --> Duplicate of "Switch" which was already added in #32.
Package Category "Magnetic Field Sensors" -> Same as for "Sensors, Transducers", magnetic field sensors is not really a package description.

I'm sorry about the wasted effort, but I really want to keep categories clean. We can add more specific categories at any time once some categories get crowded too much by lots of components or packages. But once a category is added, we should really not remove it anymore, even if we realize some day that the category was actually not needed (removing categories might break users library elements!).

authors: sixtyfive ubruhin


text:
[FRONTEND] Bad album alignment on mobile view

On the album page, album lists seems to not respect the margins/alignments.

Using latest docker image on frontend and whole stack.

I would say I get similar behaviour of WEB UI on my smartphone but only some. I looks to be link to text size when it exeeds one line.... (I would say text size is too large... but it's linked to my eyesight ;-) )
Moreover, when I open "things" with portait mode I get 2 columns, if I go to landscape mode, I get 3 colomns and if I switch back to portrait mode I still get 3 columns.

Fixed, will be available in next release :)

authors: derneuere hardwareadictos loulou91

repo: LibrePhotos/librephotos


text:
Lido app/marcus/offset

LIDO-1913

Previous PR was working of a bad Master branch commit that was reverted. Thus I had to migrate my code onto the current master

repo: Lido-App/fast-formula-parser