text:
Use iproute2 instead of ifconfig

@xlii-chl said : The package net-tools and the included ifconfig seems to be slowly abandoned in favor of iproute2.
It should be great to stick to the most commonly used packages.

Quick note before going to sleep :)
ip route get 198.51.100.1 | sed -n 's/.* src \([^[:space:]]*\) .*/\1/p'
ip route get 2001:DB8::1 | sed -n 's/.* src \([^[:space:]]*\) .*/\1/p'

Also available in JSON :
ip -json route get 198.51.100.1
# [{...,"prefsrc":"192.168.0.12",...}]

The 198.51.100.0/24 (RFC5737 TEST-NET-2) and 2001:db8::/32 (RFC3849) are reserved addresses so it should be safe to use them as is.

What do you think about this ChatGPT version ?
ip addr show | awk '/inet /{print $2}' | cut -d'/' -f1 | grep -v '127.0.0.1'

Well, if it works on your side, that's good but on mine, it outputs the dockers' adresses:
# ip addr show | awk '/inet /{print $2}' | cut -d'/' -f1 | grep -v '127.0.0.1'
192.168.1.12
172.16.238.1
172.18.0.1
172.17.0.1
# ip route get 198.51.100.1 | sed -n 's/.* src \([^[:space:]]*\) .*/\1/p'
192.168.1.12

On another computer with some virtualization, the VM network address is before the "main" one:
$ ip addr show | awk '/inet /{print $2}' | cut -d'/' -f1 | grep -v '127.0.0.1'
10.0.5.1
192.168.0.27
$ ip route get 198.51.100.1 | sed -n 's/.* src \([^[:space:]]*\) .*/\1/p'
192.168.0.27

(note: you can replace 198.51.100.1 by 1.1.1.1 or 8.8.8.8 if you feel it makes more sense.)

Seems to work...

authors: weeger xlii-chl

repo: wexample/wex


text:
Implement maxWidth for Marker InfoWindow

If there is much text in the content of the InfoWindow, currently it takes up full width of the available map screen and just does not look good.
I have added a new option called "width" to the styles dictionary. With this it is possible to set the width of the InfoWindow by specifying either a numeric value (pixel), or a percentage (0.0-1.0) or 50%.

Looks good to me. We'll wait until someone or masashi had find time to develop it for android.

@Hirbod, I actually made the commit for both platforms. Could someone review and test my pull request, and if all is good, push it into the master branch? It already works for me as expected. Thanks!

Your right, sorry for that. Did not look close enough. I'm fine with that but the final decision has to be made by Masashi. He is very busy these days, please be patient.

@masashiGMS @wf9a5m75 I'd like to merge this. Ok?

Dear @trancee would you please be so kind and provide a short documentation? I would like to add it to the wiki and finally merge this one here

@Hirbod, thanks for finally merging this pull request. It has been quite some time.
Generally, I have tried to apply the same logic as in the original Google Maps implementation, with one slight difference. Besides the option maxWidth for defining the maximum width of the InfoWindow, there is a new option width to define the initial width of the InfoWindow. This can be percentage (%) or just a numeric value from 0.0 to 1.0 for percentile representation, or the numeric width in pixels.
I hope that helps.

@trancee thanks, could you please provide some examples what is possible for the documentation. I have limited time currently.

@Hirbod yes, sure. That is an example how I am using it in my project:
map.addMarker (
	{
		"position": position,

		"title": "This is the title.",
		"snippet": "And the description of this marker.",

		"styles": {
			"maxWidth": "80%"
		},

		// allows all users to drag the marker.
		"draggable": false
	}, ...

@trancee just merged your code, but I get:
...platforms/ios/Nachbarschaft/Plugins/plugin.google.maps/GoogleMapsViewController.m:385:27: error:
      no visible @interface for 'NSString' declares the selector 'isNumeric:'
                } else if ([widthString isNumeric:widthString]) {
                            ~~~~~~~~~~~ ^~~~~~~~~
...platforms/ios/Nachbarschaft/Plugins/plugin.google.maps/GoogleMapsViewController.m:408:27: error:
      no visible @interface for 'NSString' declares the selector 'isNumeric:'
                } else if ([widthString isNumeric:widthString]) {

I'll change your code.
        NSNumberFormatter *nf = [[NSNumberFormatter alloc] init]; // new
        BOOL isNumeric = [nf numberFromString:widthString] != nil; // new
...
...
...
		//} else if ([widthString isNumeric:widthString]) {
		} else if (isNumeric) {

Strange, I did not get those errors. But thanks for fixing them!

source: gharchive/pull-request

authors: Hirbod trancee

license_type: permissive

license_source: bigquery


text:
Parcial por LIGA

Olá,
Uma boa funcionalidade seria a Parcial/Pontos por Liga, exemplo:
Digita a liga XYZ, busca os times da liga tendo como filtros de pontuação da Rodada, Mês, Ano, Turno.
Enquanto a rodada não finalizar trás as parciais, quando fechar trás o valor final.
Ano passado tinha feito isso com ajuda da API, porém esse ano já não consegui acessar mais nada.
Se tiverem interesse posso ajudar nessa funcionalidade, apenas precisaria de ajuda com a API AUTH pois fiz uns testes nela e não esta retornando nada.
array(3) {   ["id"]=>   string(13) "Authenticated"   ["userMessage"]=>   string(32) "UsuÃ¡rio autenticado com sucesso"   ["glbId"]=>   string(255) "1333d9fc9d06178edd1dfe01f37372a346c466256487051667a536c5730592d59704a436e4f3244315a70414e616d4b4347674f624c625271727a4e384c79363443576379726d35727a375f68357a685150714249754c336a6c37484c4c7876564736384342673d3d3a303a7566776d766d6d72647077626c6b736e77666571" } 404 page not found

mas essa resposta diz que você esta autenticado.

Sim, porém mesmo autenticado nenhuma API restrita tá funcionando, retorna
404.
Em 12 de mai de 2017 8:14 PM, "Jhonata Menezes" notifications@github.com
escreveu:

mas essa resposta diz que você esta autenticado.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wgenial/cartrolandofc/issues/61#issuecomment-301205997,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGpurlCT9l5iDUKDEs0MmMa7SQ8bgIRHks5r5Oe4gaJpZM4NZ1jM
.

e como voce esta passando o glbId?

No próprio arquivo auth API.php tem dois exemplos da API passando string no
$_GET  para formar a URL e logo após o comando exec()
Em 13 de mai de 2017 10:29 AM, "Jhonata Menezes" notifications@github.com
escreveu:

e como voce esta passando o glbId?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wgenial/cartrolandofc/issues/61#issuecomment-301248437,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGpurgTPaZZj-LrGV8vZ1qRfG_--0DLYks5r5bAwgaJpZM4NZ1jM
.

voce copiou o arquivo config.php.dist para config.php ? o dist é apenas para distribuição

Sim, por isso estou conseguindo logar... No config só vai login e senha...
Você já usou essa API e funcionou ?
Em 13 de mai de 2017 10:35 AM, "Jhonata Menezes" notifications@github.com
escreveu:

voce copiou o arquivo config.php.dist
https://github.com/wgenial/cartrolandofc/blob/master/config.php.dist
para config.php ? o dist é apenas para distribuição
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wgenial/cartrolandofc/issues/61#issuecomment-301248788,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGpuriOPHIjPLZYkqUkRbEVK0MN7bRRpks5r5bGagaJpZM4NZ1jM
.

ta certo, viajei agora desculpa. Acabei de testar e passou, verifica se o header X-GLB-Token esta sendo enviado, se executar com curl você pode passar o parâmetro -v que ele mostra os headers de requisição e resposta

// estatisticas e scouts dos atletas
else if ($_GET["api"] === "atleta-pontuacao") {
  $url = "https://api.cartolafc.globo.com/auth/mercado/atleta/".

$_GET["atleta_id"] ."/pontuacao";
}
$json = exec("curl -X GET ". $url ." -H 'x-glb-token: ".

$_SESSION['glbId'] ."'");
echo $json;
}
2017-05-13 10:41 GMT-03:00 Jhonata Menezes notifications@github.com:

ta certo, viajei agora desculpa. Acabei de testar e passou, verifica se o
header X-GLB-Token esta sendo enviado, se executar com curl você pode
passar o parâmetro -v que ele mostra os headers de requisição e resposta
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wgenial/cartrolandofc/issues/61#issuecomment-301249091,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGpursRI6XwE0S2_PIKHyg_oyT6QggE_ks5r5bL2gaJpZM4NZ1jM
.

--
Douglas Pootz
Gerente de Projetos
Tel: (61)    3037-9199
Cel: (61) 9.9681-5217
Skype: douglas.pootz
douglas@grupocevicom.com.br
www.grupocevicom.com.br http://www.grupocevicom.com.br/

coloca "curl -v -X" assim voce ve a requisição, testa com o postman tbm para ver o que ocorre

array(3) {
["id"]=>
string(13) "Authenticated"
["userMessage"]=>
string(32) "UsuÃ¡rio autenticado com sucesso"
["glbId"]=>
string(255) "1466d969ceee6e701b53fc773dd807f44335a65734e6d6a7839637a47574679337a314a3345672d68666c675a475233427a4a77762d397549526446793364357236483257695f314b67574f5a4671734d37657a355745425a6346325a394731684e39594d67673d3d3a303a7566776d766d6d72647077626c6b736e77666571"
}
404 page not found
Mesma coisa, será alguma configuração no servidor? de CURL?
2017-05-13 11:00 GMT-03:00 Jhonata Menezes notifications@github.com:

coloca "curl -v -X" assim voce ve a requisição, testa com o postman
https://chrome.google.com/webstore/detail/postman/fhbjgbiflinjbdggehcddcbncdddomop
tbm para ver o que ocorre
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wgenial/cartrolandofc/issues/61#issuecomment-301250220,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGpurk3EgLj6_0k2AwWvb3YPX6ztkK5Vks5r5beBgaJpZM4NZ1jM
.

--
Douglas Pootz
Gerente de Projetos
Tel: (61)    3037-9199
Cel: (61) 9.9681-5217
Skype: douglas.pootz
douglas@grupocevicom.com.br
www.grupocevicom.com.br http://www.grupocevicom.com.br/

Pessoal, vocês não acham melhor tratar sobre esse assunto no gitter https://gitter.im/cartrolandofc/dev pois isso não é uma issue e assim fica distorcido o objetivo. Valeu

Desculpe Giovani, irei por lá agora... na verdade o foco seria a melhoria
que coloquei la em cima!
2017-05-13 11:08 GMT-03:00 Giovani Generali notifications@github.com:

Pessoal, vocês não acham melhor tratar sobre esse assunto no gitter
https://gitter.im/cartrolandofc/dev pois isso não é uma issue e assim
fica distorcido o objetivo. Valeu
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wgenial/cartrolandofc/issues/61#issuecomment-301250636,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGpurk6Mu1heL4y313HT0QdhriWa0n1Fks5r5blJgaJpZM4NZ1jM
.

--
Douglas Pootz
Gerente de Projetos
Tel: (61)    3037-9199
Cel: (61) 9.9681-5217
Skype: douglas.pootz
douglas@grupocevicom.com.br
www.grupocevicom.com.br http://www.grupocevicom.com.br/

@spydoug vou manter o label melhoria mas as dúvidas de autenticação e afim, melhor no gitter. Valeu

@spydoug se quiser contribuir com essa melhoria basta fazer um fork do projeto e enviar um pull request.

minha sugestão é que essa implementação seja feita no https://github.com/wgenial/cartrolandofc/blob/master/load-api-auth.php  pois assim fica fácil de consumir isso via json.
sobre sua dúvida na autenticação foi resolvida lá no gitter, valeu!

source: gharchive/issue

authors: giovanigenerali jhonata-menezes spydoug

repo: wgenial/cartrolandofc

license: mit


text:
[问题反馈]WIN缩放时关闭按钮不隐藏

如图所示

为什么要隐藏

为什么要隐藏

我在使用的时候发现，在WIN的窗口的宽度接近图片的原始宽度时，还有Andriod的竖屏模式时，关闭按钮会隐藏（如图所示），似乎是为了防止图标遮挡图片做的自动处理。但是在WIN的窗口的宽度大于图片的原始宽度，还有Andriod的横屏模式，图片放大至宽度附近时，却并不会为了防遮挡而隐藏。
（点击呼出的抽屉菜单左上角已经有返回关闭按钮，不如。。。）

这个是由窗口宽度决定的，目的是提高大屏设备尤其是PC端的交互体验，在移动端可以通过手势直接退出阅读器，而在大屏设备和PC端就有些麻烦，因此加上了这个关闭按钮

这个是由窗口宽度决定的，目的是提高大屏设备尤其是PC端的交互体验，在移动端可以通过手势直接退出阅读器，而在大屏设备和PC端就有些麻烦，因此加上了这个关闭按钮

这个是由窗口宽度决定的，目的是提高大屏设备尤其是PC端的交互体验，在移动端可以通过手势直接退出阅读器，而在大屏设备和PC端就有些麻烦，因此加上了这个关闭按钮

pc端的话，或许可以监听键盘，比如说监听esc/backspace退出。移动端横屏状态也可以接收手势，也可以不用这个悬浮按钮。

设置中有关闭选项，不需要的话关闭就好，PC端目前有监听鼠标侧键执行路由返回

From: 纸控 @.>
Sent: Monday, September 11, 2023 3:11:02 PM
To: wgh136/PicaComic @.>
Cc: wgh136 @.>; Comment @.>
Subject: Re: [wgh136/PicaComic] [问题反馈]WIN缩放时关闭按钮不隐藏 (Issue #163)
这个是由窗口宽度决定的，目的是提高大屏设备尤其是PC端的交互体验，在移动端可以通过手势直接退出阅读器，而在大屏设备和PC端就有些麻烦，因此加上了这个关闭按钮
pc端的话，或许可以监听键盘，比如说监听esc/backspace退出。移动端横屏状态也可以接收手势，也可以不用这个悬浮按钮。
―
Reply to this email directly, view it on GitHubhttps://github.com/wgh136/PicaComic/issues/163#issuecomment-1713296379, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQEI6J45IMO3SFROABOT7H3XZ22QNANCNFSM6AAAAAA4SIGEG4.
You are receiving this because you commented.Message ID: @.***>

设置中有关闭选项，不需要的话关闭就好，PC端目前有监听鼠标侧键执行路由返回
…
________________________________ From: 纸控 @.> Sent: Monday, September 11, 2023 3:11:02 PM To: wgh136/PicaComic @.> Cc: wgh136 @.>; Comment @.> Subject: Re: [wgh136/PicaComic] [问题反馈]WIN缩放时关闭按钮不隐藏 (Issue #163) 这个是由窗口宽度决定的，目的是提高大屏设备尤其是PC端的交互体验，在移动端可以通过手势直接退出阅读器，而在大屏设备和PC端就有些麻烦，因此加上了这个关闭按钮 pc端的话，或许可以监听键盘，比如说监听esc/backspace退出。移动端横屏状态也可以接收手势，也可以不用这个悬浮按钮。 ― Reply to this email directly, view it on GitHub<#163 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQEI6J45IMO3SFROABOT7H3XZ22QNANCNFSM6AAAAAA4SIGEG4. You are receiving this because you commented.Message ID: @.***>

不是软件有BUG而是我有BUG

license: MIT

license_source: github-api


text:
Pembenahan Struktur MVC & Lainnya

Perubahan utama:

Menambahkan model-model.
Mengganti penggunaan controller home dan user menjadi guest dan admin.
Memisahkan view guest dan admin ke dalam direktori berbeda.
Memisahkan bagian view header, navbar dan footer menjadi layout terpisah yang disimpan pada direktori layout.

Perubahan lainnya:

Penggantian database.
Meningkatkan fitur pelayanan dengan metode refresh loop.
Perubahan kecil lainnya yang tidak dapat di-track.

wah akeh tenan cok sek kudu di resolve

authors: mkthulu wgnalvian


text:
ユーザー管理追加

概要
■ recoil
https://recoiljs.org/docs/introduction/getting-started
recoilで実装してみる

https://zenn.dev/ria/articles/2427d0e998c557cdbb96

repo: wheatandcat/memoir


text:
Response validation

Is there an ability to validate a response schema?
@Post()
@ApiOperation({ description: 'Create something })
@ApiResponse({ status: HttpStatus.OK, description: 'Success response', type: CreateSomethingResponseDto })
async create(
  @Body() body: CreateSomethingDto,
): Promise<Something> {
  return this.somethingService.create(body)
}

And CreateSomethingResponseDto:
  import { JoiSchema, JoiSchemaOptions } from 'nestjs-joi'

  @JoiSchemaOptions({stripUnknown: true})
export class CreateSomethingResponseDto {
  @JoiSchema(integerRequired)
  @ApiProperty({ example: 1, description: 'Tenant id', nullable: true })
  id: number | null
}

Not at the moment, but it's an interesting idea. @ApiResponse() is part of the Swagger package - meaning it would only work with that package - and does not offer any hooks that could be used for this, as far as I know. Simply put, the concept of Pipes in NestJS is made specifically for input data, so it's easy to do something like this for input data, as opposed to output data.
As for response validation, probably the most straightforward way to implement it would be to use interceptors (https://docs.nestjs.com/interceptors), but we have no way of knowing the type class of the response, so it would have to be specified manually, perhaps with a decorator. Also, this would not work if a route uses the @Res() decorator.
I'll keep this in mind and think about it a bit. If you know of a way to get the response type for the route from the ExecutionContext or similar, let me know, though I think this will be difficults, since a lot of the time the actual type will have to be unpacked from a Promise<> or similar, so the decorator would probably be the easiest way...

After some investigation, I found how to get type passed to ApiResponse.
It is just a quick test, so it is not ideal. Here is a short example of how to get it:
test.dto.ts
export class TestDto{
  superString: string
}

response.interceptor.ts
import { tap } from 'rxjs/operators';
import {Reflector} from "@nestjs/core";
import {DECORATORS} from "@nestjs/swagger/dist/constants";

@Injectable()
export class ResponseInterceptor implements NestInterceptor {
  constructor(private reflector: Reflector) {}

  intercept(context: ExecutionContext, next: CallHandler): Observable<any> {
    return next
      .handle()
      .pipe(
        tap(() => {
          const swaggerData = this.reflector.get<string[]>(DECORATORS.API_RESPONSE, context.getHandler());
          console.log(swaggerData['200'].type)
        }),
      );
  }
}

in main.ts
app.useGlobalInterceptors(new ResponseInterceptor(new Reflector()));

in some.controller.ts
@Get()
  @ApiResponse({status: 200, type: TestDto})
  getHello(): string {
    return 'Hello world';
  }

and console output:
[class TestDto]

I didn't investigate the next steps for applying validation.
Is it helpful information?

Thanks for investigating!
Your example relies on an internal constant of the @nestjs/swagger module (the @nestjs/swagger/dist/constants import), which could technically change at any time, so I don't think it's safe to use.
Like I said above, this would also introduce a hard dependency on the @nestjs/swagger module, which otherwise has no connection to the purpose of this module.
Should this be implemented, I believe the best route would be a custom decorator on the route to explicitly specify the return type, and then only routes with that decorator would have their response validated.
I'm not sure this has broad use, though. Unlike the input, the output has fairly strong validation already given that we're using TypeScript, provided you are using types consistently.
Can you give an example of your use case that would benefit from such strong response validation when compared to stringent use of TypeScript types?

Closing as stale. @redwert feel free to reopen if you have any additions.

authors: redwert whefter

repo: whefter/nestjs-joi


text:
make location linkable

use https://chronomaps.net/geo/ as a location-helper

Currently linking to the mapbox location helper.

authors: akariv mushon

repo: whiletrue-industries/Chronomaps


text:
Something wrong when using whiteout

Hi,everyone.I'm new to whiteout.As the picture shows,how can I resolve this problem?Another question,when logging,I need to input the backup code or upload the PGP key file,can I skip this step?I mean is there a method that I only input the email address and password then I can login successfully?
Thanks.

do you know which imap server you are on? #394 should fix this

authors: b-deng felixhammerl


text:
Error on launch and no output

I get the following error dialog when I run "Coq: Start".

Error loading syntax file "Packages/Sublime-Coq/Coq Toplevel.sublime-syntax": Unable to read Packages/Sublime-Coq/Coq Toplevel.sublime-syntax

After dismissing it, the *COQTOP* pane opens but there is no output. I also tried creating a user settings file containing
{
	"coqtop_path": "/usr/local/bin/coqtop"
}

but it has no effect. How can I debug this?

Reproduced, looking into it.

authors: vassilmladenov whitequark

repo: whitequark/Sublime-Coq


text:
"JSON Pointer points to missing location" after upgrade to v3.0.0

Hello,
I think I am experiencing issues caused by this change in v3.0.0 removed options.relativeBase.
I am using CLI interface
json-refs resolve index.yaml -y --filter relative > output.yaml
where index.yaml contains references to other yaml files in the subdictionaries.
I receive a lot of messages "JSON Pointer points to missing location" caused by the fact that the yaml files in the subdictionaries contain links to #/definitions/
But those are the links that I don't want to resolve.
In version 2.1.6 it worked flawlessly.
Thank you
Martin

Any chance the unresolved references in the relative files are local references but they are not contained in the containing document?  If so, this was an accidental feature removed from v3.0.0: https://github.com/whitlockjc/json-refs/issues/100

Long story short, if you have #/definitions/Person defined in root.json and you reference it as #/definitions/Person from child.json, that use to work prior to v3.0.0 but it was an accidental feature.  Removing it made json-refs spec-compliant as mentioned in the referenced issues from https://github.com/whitlockjc/json-refs/issues/100

Hello Jeremy,
you are probably right about the root cause of my issue. I'll try to fix it as it's mentioned in #100 .
Thank you very much for your support
Martin

Any time.

repo: whitlockjc/json-refs


text:
chore: release master

:robot: I have created a release beep boop
@allaround/all-components: 1.8.11
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/input bumped from ^2.8.7 to ^2.8.8
@allaround/container bumped from ^1.7.0 to ^1.7.1
@allaround/sidebar bumped from ^1.0.5 to ^1.0.6
@allaround/navbar bumped from ^1.0.6 to ^1.0.7
@allaround/hooks bumped from ^1.0.7 to ^1.0.8
@allaround/textarea bumped from ^1.0.6 to ^1.0.7
@allaround/tags bumped from ^1.0.7 to ^1.0.8
@allaround/dropdown bumped from ^1.0.7 to ^1.0.8
@allaround/select bumped from ^1.0.7 to ^1.0.8
@allaround/upload bumped from ^1.0.7 to ^1.0.8
@allaround/scheduler bumped from ^1.0.7 to ^1.0.8
@allaround/video bumped from ^1.0.8 to ^1.0.9
@allaround/image bumped from ^1.0.7 to ^1.0.8
@allaround/checkbox bumped from ^1.0.7 to ^1.0.8
@allaround/tooltip bumped from ^1.0.7 to ^1.0.8
@allaround/switch bumped from ^1.0.4 to ^1.0.5
@allaround/progress-bar bumped from ^1.0.4 to ^1.0.5
@allaround/notification bumped from ^1.0.6 to ^1.0.7
@allaround/placeholder bumped from ^1.0.4 to ^1.0.5

@allaround/checkbox: 1.0.8
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/container bumped from ^1.7.0 to ^1.7.1
@allaround/tooltip bumped from ^1.0.7 to ^1.0.8
@allaround/input bumped from ^2.8.7 to ^2.8.8

container: 1.7.1
1.7.1 (2023-08-25)
Bug Fixes

make event props partial (#93) (be0eae5)

@allaround/dropdown: 1.0.8
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/container bumped from ^1.7.0 to ^1.7.1
@allaround/tooltip bumped from ^1.0.7 to ^1.0.8

@allaround/hooks: 1.0.8
Dependencies

The following workspace dependencies were updated

devDependencies

@allaround/container bumped from ^1.7.0 to ^1.7.1
@allaround/notification bumped from ^1.0.6 to ^1.0.7

@allaround/image: 1.0.8
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/upload bumped from ^1.0.7 to ^1.0.8
@allaround/tooltip bumped from ^1.0.7 to ^1.0.8
@allaround/container bumped from ^1.7.0 to ^1.7.1

@allaround/input: 2.8.8
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/hooks bumped from ^1.0.7 to ^1.0.8
@allaround/container bumped from ^1.7.0 to ^1.7.1
@allaround/tooltip bumped from ^1.0.7 to ^1.0.8

@allaround/navbar: 1.0.7
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/container bumped from ^1.7.0 to ^1.7.1

@allaround/notification: 1.0.7
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/container bumped from ^1.7.0 to ^1.7.1

@allaround/placeholder: 1.0.5
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/container bumped from ^1.7.0 to ^1.7.1

@allaround/progress-bar: 1.0.5
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/container bumped from ^1.7.0 to ^1.7.1

@allaround/scheduler: 1.0.8
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/hooks bumped from ^1.0.7 to ^1.0.8
@allaround/select bumped from ^1.0.7 to ^1.0.8
@allaround/container bumped from ^1.7.0 to ^1.7.1

@allaround/select: 1.0.8
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/container bumped from ^1.7.0 to ^1.7.1
@allaround/hooks bumped from ^1.0.7 to ^1.0.8

@allaround/sidebar: 1.0.6
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/container bumped from ^1.7.0 to ^1.7.1

@allaround/switch: 1.0.5
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/container bumped from ^1.7.0 to ^1.7.1

@allaround/tags: 1.0.8
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/hooks bumped from ^1.0.7 to ^1.0.8
@allaround/input bumped from ^2.8.7 to ^2.8.8
@allaround/textarea bumped from ^1.0.6 to ^1.0.7

@allaround/textarea: 1.0.7
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/container bumped from ^1.7.0 to ^1.7.1

@allaround/tooltip: 1.0.8
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/hooks bumped from ^1.0.7 to ^1.0.8

@allaround/upload: 1.0.8
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/hooks bumped from ^1.0.7 to ^1.0.8
@allaround/input bumped from ^2.8.7 to ^2.8.8
@allaround/container bumped from ^1.7.0 to ^1.7.1

@allaround/video: 1.0.9
Dependencies

The following workspace dependencies were updated

dependencies

@allaround/progress-bar bumped from ^1.0.4 to ^1.0.5
@allaround/hooks bumped from ^1.0.7 to ^1.0.8
@allaround/container bumped from ^1.7.0 to ^1.7.1
@allaround/tooltip bumped from ^1.0.7 to ^1.0.8
@allaround/upload bumped from ^1.0.7 to ^1.0.8

allaround-components: 2.10.1
2.10.1 (2023-08-25)
Bug Fixes

make event props partial (#93) (be0eae5)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/allaround-components-v2.10.1 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/all-components-v1.8.11 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/input-v2.8.8 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/container-v1.7.1 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/sidebar-v1.0.6 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/navbar-v1.0.7 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/hooks-v1.0.8 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/textarea-v1.0.7 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/tags-v1.0.8 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/dropdown-v1.0.8 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/select-v1.0.8 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/upload-v1.0.8 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/scheduler-v1.0.8 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/video-v1.0.9 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/image-v1.0.8 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/checkbox-v1.0.8 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/tooltip-v1.0.8 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/switch-v1.0.5 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/progress-bar-v1.0.5 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/notification-v1.0.7 :sunflower:

:robot: Release is at https://github.com/wholesome-ghoul/allaround-components/releases/tag/placeholder-v1.0.5 :sunflower:

repo: wholesome-ghoul/allaround-components


text:
🛑 Übersicht 🇫🇷 (fr) is down

In ef2e4d9, Übersicht 🇫🇷 (fr) (https://holiday-lescala.com/fr/maisons/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Übersicht 🇫🇷 (fr) is back up in fcacf8b after 12 minutes.

repo: whytspace/upptime-holiday-lescala


text:
Issues as of 2019-08-06

God Mode & No Cooldowns no longer work past the first stage - Fixed
ESP Seems to cause severe lag past the first stage.

Project discontinued


text:
Customize shortcut keys?

amazing tool!
Will the next version allow users to define shortcuts?
Either UI or config files are good ways.
thanks again.

I agree, on my keyboard, I have one windows key on the left side. It would be nice to be able to use Alt which I have access to with both hands.

@dalianzhu @PhilipNelson5
Sure I can make it customizable, I also have to clean up some of the switching, occasionally it can glitch. Should be releasing a new version within a few days here.

I'll probably go with a configuration file, what do you guys think about something like this:
{
  "toggle-groups": [
    {  // create toggle groups. These allows you to group a bunch of virtual desktops.
      // When you press the toggle key it will cycle through the desktops.
	"shortcut": "win+^",
	"desktops": [1, 2, 3]
    }
  ],
  "jump-to-1": "win+1", // custom shortcut to jump to desktop 1
  "jump-to-2": "win+2", // etc.
  "jump-to-3": "win+3",
  "jump-to-4": "win+4",
  "jump-to-5": "win+5",
  "jump-to-6": "win+6",
  "jump-to-7": "win+7",
  "jump-to-8": "win+8",
  "jump-to-9": "win+9",
  "jump-to-10": "win+0"
}

I like the toggle-groups idea.
Another idea inspired by VSCode keybindings. It's more verbose but maybe allows for greater flexibility.
{
  // create toggle groups. These allows you to group a bunch of virtual desktops.
  // When you press the toggle key it will cycle through the desktops.
  "toggle-groups": [
    {
      "key": "win+^",
      "desktops": [ 1, 2, 3 ]
    }
  ],
  "keybindings": [
    {
      "key": "win+1",
      "command": "jump-to-1"
    },
    {
      "key": "ctrl+2",
      "command": "jump-to-2"
    },
    {
      "key": "alt+3",
      "command": "jump-to-3"
    }
  ]
}

Funnily enough I came to the same conclusion and then just pulled up your comment, definitely the better way to do it and makes the code a bit easier too. I'm just about finished implementing it should have a release for you soon. Thanks for the feedback.

@PhilipNelson5 @dalianzhu
I just published a new release that supports configuration files. I updated the readme to explain how to write a configuration file.
Let me know if you have any issues. If it works for ya'll then I'll go ahead and close the issue.

looks good to me

Thanks!

authors: PhilipNelson5 dalianzhu widavies

repo: widavies/WinJump

license: Unlicense


text:
Independent lights for camera operator and speaker

It should be possible to have a light for the operator (which also shows error and connection states) and a light for the speaker (without the status lights)

Documentation is still missing.

12d66e7fd2ee46eb580ab1bf705c0c8bde6a6991

repo: wifi-tally/wifi-tally


text:
Verifying diamonds with hardhat etherscan-verify results in error

When using etherscan-verify to verify a Diamond contract, the following error gets thrown for the facet
Error: types/values length mismatch (count={"types":2,"values":1}, value={"types":[{"components":[{"internalType":"address","name":"facetAddress","type":"address"},{"internalType":"enum IDiamondCut.FacetCutAction","name":"action","type":"uint8"},{"internalType":"bytes4[]","name":"functionSelectors","type":"bytes4[]"}],"internalType":"struct IDiamondCut.FacetCut[]","name":"_diamondCut","type":"tuple[]"},{"components":[{"internalType":"address","name":"owner","type":"address"}],"internalType":"struct Diamond.DiamondArgs","name":"_args","type":"tuple"}],"values":["0xB812f503607Ee2259E9607Cb5E5836B550ac6492"]}, code=INVALID_ARGUMENT, version=abi/5.4.1)     at Logger.makeError (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat-deploy/node_modules/@ethersproject/logger/src.ts/index.ts:225:28)     at Logger.throwError (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat-deploy/node_modules/@ethersproject/logger/src.ts/index.ts:237:20)     at AbiCoder.encode (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat-deploy/node_modules/@ethersproject/abi/src.ts/abi-coder.ts:102:20)     at submit (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat-deploy/src/etherscan.ts:308:12)     at processTicksAndRejections (internal/process/task_queues.js:97:5)     at async Object.submitSources (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat-deploy/src/etherscan.ts:425:5)     at async SimpleTaskDefinition.action (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat-deploy/src/index.ts:774:5)     at async Environment._runTaskDefinition (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat/src/internal/core/runtime-environment.ts:217:14)     at async Environment.run (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat/src/internal/core/runtime-environment.ts:129:14)     at async main (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat/src/internal/cli/cli.ts:197:5) {   reason: 'types/values length mismatch',   code: 'INVALID_ARGUMENT',   count: { types: 2, values: 1 },   value: {     types: [ [Object], [Object] ],     values: [ '0xB812f503607Ee2259E9607Cb5E5836B550ac6492' ]   } }

If you have a repo, that would help
But at least put the command you use and give the full console output
Thanks

You can find the repo I'm trying to verify here (https://github.com/oncyberio/factory/tree/verification/packages/contracts), I've taken out the deployment script for the first contract as I'm only trying to verify the second.
I run hardhat etherscan-verify --network rinkeby
`

hardhat etherscan-verify --network rinkeby

verifying CyberDestinationUtilityFactoryFacet (0x0d84BF4A82DC7771c09c37BAcF5B7DD6a37d50Ae) ...
waiting for result...
Failed to verify contract CyberDestinationUtilityFactoryFacet: NOTOK, Fail - Unable to verify
{
"apikey": "XXXXXX",
"module": "contract",
"action": "verifysourcecode",
"contractaddress": "0x0d84BF4A82DC7771c09c37BAcF5B7DD6a37d50Ae",
"sourceCode": "...",
"codeformat": "solidity-standard-json-input",
"contractname": "contracts/DestinationUtility/CyberDestinationUtilityFactoryFacet.sol:CyberDestinationUtilityFactoryFacet",
"compilerversion": "v0.8.7+commit.e28d00a7",
"licenseType": 3
}
Etherscan sometime fails to verify when only metadata sources are given. See https://github.com/ethereum/solidity/issues/9573. You can add the option --solc-input to try with full solc-input sources. This will include all contract source in the etherscan result, even the one not relevant to the contract being verified
already verified: Diamantaire (0xB812f503607Ee2259E9607Cb5E5836B550ac6492), skipping.
verifying DiamondCyberDestinationUtilityFactory (0xd068bcf331ABA7B2aB91779C179C1288205887Df) ...
An unexpected error occurred:
Error: types/values length mismatch (count={"types":2,"values":1}, value={"types":[{"components":[{"internalType":"address","name":"facetAddress","type":"address"},{"internalType":"enum IDiamondCut.FacetCutAction","name":"action","type":"uint8"},{"internalType":"bytes4[]","name":"functionSelectors","type":"bytes4[]"}],"internalType":"struct IDiamondCut.FacetCut[]","name":"_diamondCut","type":"tuple[]"},{"components":[{"internalType":"address","name":"owner","type":"address"}],"internalType":"struct Diamond.DiamondArgs","name":"_args","type":"tuple"}],"values":["0xB812f503607Ee2259E9607Cb5E5836B550ac6492"]}, code=INVALID_ARGUMENT, version=abi/5.4.1)
at Logger.makeError (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat-deploy/node_modules/@ethersproject/logger/src.ts/index.ts:225:28)
at Logger.throwError (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat-deploy/node_modules/@ethersproject/logger/src.ts/index.ts:237:20)
at AbiCoder.encode (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat-deploy/node_modules/@ethersproject/abi/src.ts/abi-coder.ts:102:20)
at submit (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat-deploy/src/etherscan.ts:308:12)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async Object.submitSources (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat-deploy/src/etherscan.ts:425:5)
at async SimpleTaskDefinition.action (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat-deploy/src/index.ts:774:5)
at async Environment._runTaskDefinition (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat/src/internal/core/runtime-environment.ts:217:14)
at async Environment.run (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat/src/internal/core/runtime-environment.ts:129:14)
at async main (/Users/rayan/Documents/Cyber/Tech/factory/packages/contracts/node_modules/hardhat/src/internal/cli/cli.ts:197:5) {
reason: 'types/values length mismatch',
code: 'INVALID_ARGUMENT',
count: { types: 2, values: 1 },
value: {
types: [ [Object], [Object] ],
values: [ '0xB812f503607Ee2259E9607Cb5E5836B550ac6492' ]
}
}
`

SO there seems to be 2 different issues
CyberDestinationUtilityFactoryFacet is failing to verify. this could be due to an etherscan bug.
As for the error thrown it is due to the number of arguments in the deployment file not matching the number of arguments the constructor expect.
see https://github.com/oncyberio/factory/blob/65b0ba1be56bc079f61d911b5f78b494143f2cb3/packages/contracts/deployments/rinkeby/DiamondCyberDestinationFactory.json#L5-L43
it expect 2 argument but only 2 was saved here : https://github.com/oncyberio/factory/blob/65b0ba1be56bc079f61d911b5f78b494143f2cb3/packages/contracts/deployments/rinkeby/DiamondCyberDestinationFactory.json#L887

should be fixed in newer version. for existing deployment you can replace the args field with the following:
"args": [
    [
        {
            "facetAddress": "0x35d80a53f7be635f75152221d4d71cd4dcb07e5c",
            "action": 0,
            "functionSelectors": [
                "0x1f931c1c"
            ]
        },
        {
            "facetAddress": "0xc1bbdf9f8c0b6ae0b4d35e9a778080b691a72a3e",
            "action": 0,
            "functionSelectors": [
                "0xadfca15e",
                "0x7a0ed627",
                "0xcdffacc6",
                "0x52ef6b2c",
                "0x01ffc9a7"
            ]
        },
        {
            "facetAddress": "0xcfEe10af6C7A91863c2bbDbCCA3bCB5064A447BE",
            "action": 0,
            "functionSelectors": [
                "0xf2fde38b",
                "0x8da5cb5b"
            ]
        }
    ],
    {
        "owner": "<the original owner>"
    }
],

authors: rayanoncyber wighawag

repo: wighawag/hardhat-deploy


text:
apply 'waitConfirmations' to all transactions

Make sure to respect defined 'waitConfirmations' for :

"deterministic deployment" (CREATE2)
"execute"
"rawTX"

Closes #510

Thanks!

authors: fullkomnun wighawag


text:
Add Bengali language assets

Tests fail for strange reasons that is beyond my knowledge
Bug: https://phabricator.wikimedia.org/T162620

Also, needs https://github.com/travis-ci/apt-package-whitelist/pull/4107/files to be merged first

We might need to disable that test.  It could be that the package is not available in our test vms.  See had to do the same for hindi and tamil.  See https://github.com/wiki-ai/revscoring/blob/master/.travis.yml#L51

Done

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b9c402f). Click here to learn what that means.
The diff coverage is 2.5%.

@@            Coverage Diff            @@
##             master     #309   +/-   ##
=========================================
  Coverage          ?   84.95%
=========================================
  Files             ?      231
  Lines             ?     7385
  Branches          ?        0
=========================================
  Hits              ?     6274
  Misses            ?     1111
  Partials          ?        0

Impacted Files
Coverage Δ

revscoring/languages/tests/test_bengali.py
0% <0%> (ø)

revscoring/languages/bengali.py
0% <0%> (ø)

revscoring/languages/tests/util.py
100% <100%> (ø)

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 b9c402f...8390084. Read the comment docs.

Needs an update to requirements.txt for deltas 0.4.6

authors: Ladsgroup codecov-io halfak

repo: wiki-ai/revscoring


text:
[WFCORE-3991] Test coverage for read-config-as-features(nested=false)

https://issues.jboss.org/browse/WFCORE-3991

@LittleJohnII WFCORE-3991 has been resolved as we already merge the feature. Could you open additional WFCORE issues for additional testing please?

Sure, I updated the description.

Hold on a second, I'll rename the commit as well...

I force pushed another fix - this is also relevant to the previous test coverage. The domain tests sometime didn't wait for all the servers to start and the tests could fail with server boot in process. Thanks to Alexey for letting me know.
Cc. @aloubyansky

authors: LittleJohnII jmesnil

repo: wildfly/wildfly-core


text:
Move some javax.* to jakarta.*

This includes a temporary commit to add the jakarta.json module to full. This module lives in core which for testing purposes should wait for this to be merged, then reverted once merged into core and core is released. This also pertains to the jakarta.inject dependency as well.
This includes the following as to not cause conflicts with having these separate commits:

https://issues.jboss.org/browse/WFLY-12499
https://issues.jboss.org/browse/WFLY-12501
https://issues.jboss.org/browse/WFLY-12502

Dependency Tree Analyzer Output:
New Dependencies:

jakarta.inject:jakarta.inject-api:jar:1.0:compile
jakarta.json.bind:jakarta.json.bind-api:jar:1.0.2:compile
jakarta.json:jakarta.json-api:jar:1.1.6:compile
org.glassfish:jakarta.json:jar:1.1.6:compile

Removed Dependencies:

javax.inject:javax.inject:jar:1:compile
javax.json.bind:javax.json.bind-api:jar:1.0:compile

CC @wildfly/prod

@bstansberry Okay no problem. I'll revert that part. I saw that EL created a new module and I should have just asked rather than assuming :)

@jamezp what is the EL change you are referring to?

Ah I see. It's just the implementation module that changes from org.glassfish.javax.el to org.glassfish.jakarta.el. Do we want the implementation modules renamed?

The branch for the revert is: https://github.com/wildfly/wildfly/compare/master...jamezp:WFLY-12501-WFLY-12502-revert?expand=1
A PR can be opened for this once https://github.com/wildfly/wildfly-core/pull/3947 is done and a core upgrade is merged.

@jamezp Can you add a commit adding the no-longer wanted GAs to the maven-enforcer-plugin ban-bad-dependencies execution in the root pom?
That will result in a failure if any of our deps are pulling that in without us having added an exclude in dependencyManagement.
I don't think that needs to be part of the commits we plan to revert as banning the deps in full is valid even though the versions we want will come in via core.
What's here LGTM. I think the org.glassfish.jakarta is ok. Not my favorite but I don't have a good argument and we've already done it for el.

authors: bstansberry jamezp wildfly-ci

repo: wildfly/wildfly


text:
[WFLY-15747] / [WFLY-13889] Remove PicketBox dependency from iiop-openjdk.

https://issues.redhat.com/browse/WFLY-15747
Supersedes https://github.com/wildfly/wildfly/pull/14948

Hi @tadamski this follow up on https://github.com/wildfly/wildfly/pull/14948 as I needed to submit as a new PR if you could please review the last commit I have applied the changes you requested.
I have also left it that if somehow the values for legacy security are set we report an error and fail, I want to avoid ignoring legacy security and accidentally leaving something unsecured.

Looks like it now has some related CI failures to follow up.


text:
[WFLY-16984] Refactoring Batch Subsystem to use new MSC value API

https://issues.redhat.com/browse/WFLY-16984

Some service classes are changed to implement MSC 2 Service API, while some others don't. Can you detail what prevents the use of the new Service in those classes? https://issues.redhat.com/browse/WFLY-16930 (Batch subsystem should maintain its own cache of services) could be issue for BatchConfigurationService, and JobOperatorService.

Sure @chengfang , the difference between using org.jboss.msc.Service and org.jboss.msc.service.Service are the following:
Services implementing new API org.jboss.msc.service will throw UnsupportedOperationException when calling the following deprecated methods:

ServiceController.getValue()
ServiceController.awaitValue()
ServiceController.awaitValue(long,TimeUnit)
ServiceController.getService()

By implementing deprected org.jboss.msc.service.Service interface aforementioned deprecated methods backward compatibility is maintained.
I didn't refactor these services because my main purpose for this PR was fixing just dependencies declaration.

These ServiceController methods were deprecated because they are exposing MSC runtime internals to API users.

Thanks @ropalka

authors: bstansberry chengfang ropalka


text:
Not working with pnpm

pnpm rebuild --reporter=ndjson

  let mainPath = Array(attempts).join("../");
  try {
    const content = fs.readFileSync(path.join(__dirname, mainPath, 'package.json'), 'utf-8');
    const packageJson = JSON.parse(content);
    const opts = packageJson.iohook || {};
    if (!opts.targets) {
      opts.targets = []
    }
    if (!opts.platforms) opts.platforms = [process.platform];
    if (!opts.arches) opts.arches = [process.arch];
    return opts
  } catch (e) {
    return optionsFromPackage(attempts + 1);
  }

Expected Behavior
Should find package.json config properly.
Current Behavior
{"time":1607995718300,"hostname":"VMBP2019.fritz.box","pid":54464,"level":"debug","name":"pnpm:lifecycle","depPath":"/iohook/0.7.2","line":"Can't resolve main package.json file","stage":"install","stdio":"stdout","wd":"/Users/Vaughan/dev-mono/thirtyfive/node_modules/.pnpm/iohook@0.7.2/node_modules/iohook"}

Possible Solution
For mainPath use require.main.
Steps to Reproduce (for bugs)
pnpm rebuild --reporter=ndjson

Workaround
Use env vars:
const options = optionsFromPackage();
if (process.env.npm_config_targets) {
  options.targets = options.targets.concat(process.env.npm_config_targets.split(','));
}
options.targets = options.targets.map(targetStr => targetStr.split('-'));
if (process.env.npm_config_targets === 'all') {
  options.targets = supportedTargets.map(arr => [arr[0], arr[2]]);
  options.platforms = ['win32', 'darwin', 'linux'];
  options.arches = ['x64', 'ia32']
}
if (process.env.npm_config_platforms) {
  options.platforms = options.platforms.concat(process.env.npm_config_platforms.split(','));
}
if (process.env.npm_config_arches) {
  options.arches = options.arches.concat(process.env.npm_config_arches.split(','));
}

Add to .npmrc:
# For iohook
targets=electron-85

Closing as irrelevant, as in not something I think anyone is interested in addressing. If anyone is interested please feel free to reopen and PR.

It would be better to say "closed due to inactivity".

It would be better to say "closed due to inactivity".

@vjpr True :sweat_smile:  Though the inactivity isn't odd. It's a niche issue so I didn't think anyone would be interested, didn't mean that it's not important :smile:
While I have you here, are there issues with the workaround you posted?
If this workaround is an ok way to do it with pnpm then I'll include it in docs, if it requires a fix and it's something we can feasibly knock down in a couple of hours then I can add it to todo list.

repo: wilix-team/iohook


text:
Request for Detailed Implementation of Machine Learning Algorithms as Described in Figure 2 of the Main Paper

Dear William
I hope this message finds you well. I am reaching out to express a difficulty I encountered while navigating through the API documentation linked in your repository. Upon review, I was able to find detailed documentation on generating trajectories from dynamical systems. However, I was unable to locate the specifics regarding the implementation of the machine learning algorithms, particularly those pertaining to RNN and LSTM.
The main paper's Figure 2 references the implementation of various machine learning methods, and I am particularly interested in the transformer architecture discussed. Your paper notes that "Transformers can capture long-term dependencies and complex patterns in time series data by using positional encoding and multihead attention, leading to their widespread use for diverse problems such as machine translation, text summarization, and question answering [63]".
Could you kindly provide or point me to the detailed implementation of these machine learning algorithms, especially the transformer model? The code snippets, examples, or documentation that illustrate the transformer's application specifically on you dynamical systems would be incredibly beneficial.
I appreciate the work you've put into this project and look forward to exploring the machine learning aspects further.
Thank you for your time and assistance.

Hi, it is in the benchmarks directory:
https://github.com/williamgilpin/dysts/tree/master/benchmarks
I used the Transformer implementation found in the darts python library

authors: munozdjp williamgilpin

repo: williamgilpin/dysts


text:
Example nat-tcp-v4 port_map bug

Hi,
Just want to report a bug in https://github.com/williamofockham/NetBricks/blob/809cde67a630d3ada387caedac72d2740f38cab0/examples/nat-tcp-v4/src/main.rs#L115-L121.
It is a little bit tricky: PORT_MAP.read().unwrap() should be dropped; otherwise, you cannot have mutuable PORT_MAP.write().unwrap() later.
I have fixed it here:
https://github.com/YangZhou1997/NetBricks/blob/48c53e2154198423e29dcd0b89003444c959c0c9/examples/nat-tcp-v4/src/main.rs#L119-L133
Best,
Yang

👍 will do. Good catch.

handled a littler cleaner even in https://github.com/williamofockham/NetBricks/pull/104.

repo: williamofockham/NetBricks

license: ISC


text:
Use the proper error message with caused exceptions

Type of changes

[x] Bug fix
[ ] New feature
[ ] Documentation / docstrings
[x] Tests
[ ] Other

Checklist

[x] I've run the latest black with default args on new code.
[x] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[x] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review.

Description
When an exception is raised using "from", the chained exception goes into
cause, which results in a different message using Python's native traceback
handler. This patch properly replicates that error message.

Thanks!

authors: nneonneo willmcgugan

repo: willmcgugan/rich


text:
Add ability to restrict http referrer

This adds the ability to whitelist the HTTP Referer header, to prevent evil people from hotlinking your images and stealing valuable resources!
Works in unit tests and in my simple in-browser testing. No breaking behaviour is introducted.

I signed it!

rebased onto master and merged as 9213c93c9496f8c6525b6786d8b18ba9f09db00c.  Sorry it took so long to get around to looking at this, but thanks for contributing it... looks good! :+1:

No problem, glad to contribute :smile:

repo: willnorris/imageproxy


text:
TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/73590

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/106711


text:
[BUG] Crash when user attempts to log in with non-public email address

When the user attempts to log in through Github with an email address that is not public, a crash is observed.

@oconn I'm still seeing an error when I attempt to log in with a non-public email address. Moving back to Ready.

Blocked for testing until I can log in again on QA.

Success! Moving to Closed.

repo: willowtreeapps/wombats-api


text:
🛑 willpxxr.com is down

In a7e71f3, willpxxr.com (https://willpxxr.com) was down:

HTTP code: 999
Response time: 315 ms

Resolved: willpxxr.com is back up in 2a144b6 after 9 hours, 47 minutes.


text:
Noise_threshold fixed in logmmse.py

Fixed issues with the argument 'noise_threshold'. The parameter 'eta' in logmmse.py should change according to the passed noise_threshold.

👍

authors: alessandroragano wilsonchingg

repo: wilsonchingg/logmmse


text:
LICENSE

Hi!
What is the LICENSE of this work? Can you add the LICENSE file please?
Thanks.

Thanks for mentioning this! I've added it in :)

authors: mancvso wilsonowilson

repo: wilsonowilson/Flutter-Pomodoro


text:
error.handling.log-levels property is not being overridden

I would like to override the default values of the log-levels to
error:
  handling:
    log-levels:
      4xx: WARN
      500: ERROR

but still the exception is being logged as ERROR
2023-02-02T22:55:43.450+04:00 ERROR 9014 --- [           main] i.g.w.e.LoggingService                   : checkEmail.email: Invalid email address

I tried debugging the LoggingService and the logLevels props is empty

I have also tried adding @EnableConfigurationProperties(ErrorHandlingProperties::class) but still not working
Spring Boot v3.0.1
Java 19
Error Handling Spring Boot Starter v4.1.0

Can you try using a properties file instead of yaml to see if that is the issue?

Fixed the problem. It turned out my properties file is not being picked up propertly.

authors: tddiaz wimdeblauwe


text:
shortcuts configuration does not take effect

What I expected
Both bn and btn can take effect
export default {
  shortcuts: {
    bn: 'rounded border border-gray-300 text-gray-600 px-4 py-2 m-2 inline-block hover:shadow',
    btn: 'rounded border border-gray-300 text-gray-600 px-4 py-2 m-2 inline-block hover:shadow',
  }
}

The fact is
Only btn works. bn doesn't work
Here is my demo
https://github.com/Nokic233/windi-vite
you just need
cd windi && npm i
npm run dev

Node 12.13.0

repo: windicss/windicss


text:
Docker版でフォントが豆腐でレンダされている

https://twitter.com/masatoi0/status/1753361084927586699

利用するフォントをxmlファイル側で選択できるようにする
フリーフォントをDockerイメージに同梱する
デフォルトのフォントを同梱フォントにする

の手順でなんとかなるのではないか

解消したとのこと

repo: windymelt/zmm


text:
Explain a little more about formats

In the README, link to the logform project, and tell readers to look there to learn more about logging formats.

Good copy writing @mmorearty. Thank you for your contribution!

authors: indexzero mmorearty

repo: winstonjs/winston


text:
Fix deprecation warning in Node 7

See winstonjs/winston#992

Duplicate of https://github.com/winstonjs/winston/pull/949


text:
Some more Onkyo fixes:

Fix error when closing connections
Handle 'N/A' audio/video information
Schedule an update when AVR changes state

This is the same as this PR

Once again thanks alot for the work  you put in this!
I tested the graceful shutdown and this seems to work well, I don't see an error anymore when restarting Home-Assistant.
However, I'm not totally convinced about the way we update the A/V information yet.
As you already stated, the AVR does not push the A/V information when it changes, so we have to implement some form of polling to query new info. However, I think it is not the best option to query A/V information when the AVR pushes fl-display-information to HASS. The fl-display-information is pushed whenever something on the display changes, but the A/V information does not change every time the display changes. What I think would be better, is to query new A/V information when either the listening mode or the source changes, since we know that the A/V information will change when one of those things change, right?

@klaashoekstra94 triggering after fl-display-information can indeed lead to false positives, but there's no harm in them, and looking through my log, it doesn't look like there are too many of them.
Source or listening mode changes are not enough - the A/V information can change without the source changing, for example, a Bluray player's output (and thus the AVR's input) can change depending on the media. Even the same disc usually has several different soundtracks.

@OnFreund Okay, I agree with you that source and listening mode might not be enough. However, using fl-display-information still feels very illogical since I think the two don't really have to do anything with each other, right?
Maybe it would be better then to just use a timer and poll for A/V information at a defined time interval?

A timer might make sense, but that sort of brings us back to the previous polling version...
The reason I feel comfortable with fl-display-information, is that any change to A/V info necessitates an update to the display, meaning fl-display-information will be triggered. Of course, other changes (such as volume) will also trigger it, but I can live with this level of false positives, especially given there's no adverse affect.

When I play music through the built-in Spotify, the name of the song will not fit on the display, so it will behave as a marquee element, resulting in up to 6 display updates per second. I think polling for the A/V information 6 times per second will put an unnecessary load on the network.
But anyways, we can think of something for that, maybe query once per second at maximum or so. If you could have a look at the review I made, we can merge this PR and then look at how to change things further!

My implementation doesn't query more than once per 10 seconds (if there's already a scheduled update it cancels it).

repo: winterscar/core


text:
Make E2 object-oriented (User defined classes)

[Suggestion] Make E2 object-oriented again
Its not a secret that currently the majority of people who program in E2 are those who have had lots of experience with it, and since they are more likely to program more complex programs, fir many it would've been much easier if e2 supported OOP practises.
I know some people went as far as to use tables as a workaround to make their code 'sort-of-object-oriented'

o'really. sure, you aren't the first nor the last one suggesting this.
cough i think i know what is going to happen here:
"just keep using tables."
/thegrb93-post-link-to-starfall
/closed

E2 already has objects. If you're suggestion user defined objects then I guess that would be neat, but there's not really anyone willing to work on it.

It's on my mental task list that E2 should support user-defined types.
This won't exactly be "object-oriented programming" in the sense that people often mean it - i.e. with inheritance and runtime polymorphism. At first it will likely look like simple record types:
type person = { Name: string, Age: number } # example syntax, do not bikeshed here
function person:obituary(): string { # E2 already has method syntax, which would play nicely with record types!
    return "Here lies " + Person.Name + ", who lived to the age of " + Person.Age
}
print(person("AbigailBuccaneer", 969):obituary())

Then the next thing I want to do is add union types:
type status = success | failure { Reason: string } # again, example syntax
function foo(): status {
    return failure("You didn't bar the baz!")
}
function bar() {
    switch (foo()) {(
        case success -> print("Hooray!")
        case failure(Reason) -> print("Uh oh: " + Reason)
    }
}

Then this could go in a couple of different directions: static parametric polymorphism, Haskell-like typeclasses, and more.

So basically you are going to add javascript objects

No, I'm going to add Haskell objects :smile:

It's on my mental task list that E2 should support user-defined types.
This won't exactly be "object-oriented programming" in the sense that people often mean it - i.e. with inheritance and runtime polymorphism. At first it will likely look like simple record types:
type person = { Name: string, Age: number } # example syntax, do not bikeshed here
function person:obituary(): string { # E2 already has method syntax, which would play nicely with record types!
    return "Here lies " + Person.Name + ", who lived to the age of " + Person.Age
}
print(person("Methuselah", 969):obituary())

Then the next thing I want to do is add union types:
type status = success | failure { Reason: string } # again, example syntax
function foo(): status {
    return failure("You didn't bar the baz!")
}
function bar() {
    switch (foo()) {
        case success -> print("Hooray!")
        case failure(Reason) -> print("Uh oh: " + Reason)
    }
}

Then this could go in a couple of different directions: static parametric polymorphism, Haskell-like typeclasses, and more. Of course, this will only happen if I have the time and motivation. If anybody wants to pay me to work full time on Wiremod then this'll happen faster! 😉

@name POO_Exemple

function string table:getPersonName(){ return This["Name", string] }
function number table:getPersonAge(){ return This["Age", number] }

function table person(Name_:string, Age_:number){

    return table(
        "Name"  =   Name_,
        "Age"   =   Age_
    )

}

function string table:obituary(){

    return "Here lies " + This:getPersonName() + ", who lived to the age of " + This:getPersonAge():toString()

}

print(person("Methuselah", 969):obituary())

Hello
I'm not sure if someone already though of this, but maybe something easy to implement without too much thinking, would be to allow aliases of default types, kind of like C's typedef.
For example @typedef table person
Then instead of the actual
function string table:getPersonName(){ return This["Name", string] }

that is prone to functions names collisions, you would be able to do
function string person:getName(){ return This["Name", string] }

authors: AbigailBuccaneer CaptainPRICE Divran TAbdiukov guillaume-dorczynski kstzl thegrb93

repo: wiremod/wire


text:
Fixed size for permission notice on extension menu

The label displaying "You are not a superadmin..." is now multiline and will not be cut off.

Fixed that stuff, you might want to publish some code of conduct or if there is one make it more visible.

here

Oh, I guess thats my fault then. Thanks.

That's the old guide. the new one is on google docs somewhere. I thought someone transferred that already

Here it is:
https://docs.google.com/document/d/1pnBMWcs7K5I0fzLIcbOkn0PUMfVy8S8k8uAZoYBAD3k/edit?pref=2&pli=1
We weren't quite done with that yet.
I went and accepted a couple of changes I proposed since no one bothered to discuss them.
Now it should be readable and can act as replacement for that wiki article.

I knew about the one on google docs but I had lost the link.

Thanks TomyLobo.
I guess my code is fine now?

I hope you're not asking me.
I know jack shit about derma (is that even derma?)
Someone else needs to take a look at this.

What he changed was derma yes.
And looking at what you changed, you didn't really need to change the way the superadmin check was handled, it was a useless change.
And according to the wiki AddControl is deprecated. You should just use the DForm functions, which is what AddControl calls internally.
So changed the AddControl to something like this
local label = panel:Help "You are not a superadmin - you cannot change these settings, only view them."
label:SetColor(Color(153, 51, 0, 255))

@bigdogmat Please don't omit parentheses around function arguments.

@TomyLobo Literals weren't outlined in the code style doc, my mistake.

Changed to DForm function and squashed commits.

Does panel:Help look visually any different from Label(..., panel)?

panel:Help automatically multilines if needed, the text with Label gets cut off with dots.

authors: AbigailBuccaneer GuurgleOS TomyLobo bigdogmat


text:
Update os-lib to 0.10.0

About this PR
📦 Updates com.lihaoyi:os-lib from 0.8.1 to 0.10.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.lihaoyi", artifactId = "os-lib" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.lihaoyi", artifactId = "os-lib" }
}]

labels: library-update, early-semver-major, semver-spec-minor, commit-count:1

Superseded by #173.

repo: wiringbits/my-photo-timeline


text:
Usage example

Can you include a simple example of uploading a video to Wistia from a linux machine?
Something that anyone can copy/change/paste to have their files shot to wistia using this tool.
Thanks in advance...

Found this http://wistia.github.io/demobin/magicbox/

Hey Zohar, glad you found that. The wistia-uploader gem is a bit out of date and we usually recommend people just use curl (http://wistia.com/doc/upload-api#examples). But if it is working for you, that's great!

+1 Thanks!

authors: bschwartz zohar

repo: wistia/wistia-api


text:
[v3 checks] Update instances of class:list

📚 Subject area/topic

class:list directive AND 2. scoped style hashes are lowercase!

📋 Page(s) affected (or suggested, for new content)
https://docs.astro.build/en/reference/directives-reference/#classlist
https://docs.astro.build/en/core-concepts/astro-components/#the-component-template
https://docs.astro.build/en/guides/styling/
📋 General description or bullet points (if proposing new content)
@natemoo-re needs to check docs for any examples that are now counter to the class:list changes for v3.0:

https://deploy-preview-4166--astro-docs-2.netlify.app/en/guides/upgrade-to/v3/#removed-classlist-features
https://deploy-preview-4166--astro-docs-2.netlify.app/en/guides/upgrade-to/v3/#removed-passing-classlist-as-a-prop

Including updating some uppercase scoped style hashes e.g. class="astro-KOI4QYR5"
The above listed should be the only three pages that are possibly affected.
🖥 Reproduction in StackBlitz (if reporting incorrect content or code samples)
none

Not sure why this wasn't closed automatically, but closed by #4322 :partying_face:

repo: withastro/docs


text:
Remove Netlify edge functions adapter

Description (required)
Remove netlify edge functions adapter
Astro 3.0 removed this adapter https://github.com/withastro/adapters/blob/main/packages/netlify/CHANGELOG.md#major-changes

Related issues & labels (optional)

Closes #
Suggested label:

Thank you for noticing this @julienp ! We actually merged a PR today that updates advice for this, since you can still use Netlify edge functions, just with the other adapter, and by adding middleware. There were a few things on this page that had to change, but we believe that it's all correct now! Thank you again for noticing, and I'll close this PR since it no longer matches the current page, but if you spot anything else, please open a new PR!  :raised_hands:


text:
i18n(fr): Update nav.ts

Description (required)
Update nav.ts file because of missing and malformed translation key.
Related issues & labels (optional)

Suggested label: i18n

I participate to the Hacktoberfest!

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
nav.ts
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Hi @pioupia! I was checking for any other inconsistencies in the menu... What do you think about updating reference/adapter-reference as well? All other translations start with API while this one ends with API, which is a bit strange. What do you think of API de l'Adaptateur or API des Adaptateurs?

Hi @pioupia! I was checking for any other inconsistencies in the menu... What do you think about updating reference/adapter-reference as well? All other translations start with API while this one ends with API, which is a bit strange (well, there is also reference/container-reference but the page is not translated so it is perhaps less annoying). What do you think of API de l'Adaptateur or API des Adaptateurs?

Yeah, this is a good idea. On the adapter-reference, I think that the title is pretty bad "Adaptateur l'API de Astro". Maybe "Adaptateur de l'API d'Astro" is better.
Anyway, for this topic, I'm going to update the order even if it's not important, it will help us keep consistency between languages and design.
Also, I'll rename "Adaptateur API" in "API de l'Adaptateur" as you suggested above, and "Conteneur API" in "API de Conteneur".


text:
Improve <Tabs> component keyboard interactions

What kind of changes does this PR include?

Changes to Starlight code

Description

Closes #233

As discussed in #233, this pull request stops intercepting the down arrow key in the <Tabs> component to follow the ARIA Authoring Practices Guide for the Tabs pattern:

If the tab list is horizontal, it does not listen for Down Arrow or Up Arrow so those keys can provide their normal browser scrolling functions even when focus is inside the tab list.

Altho, this is not the entire story as the guide also states that when the tabpanel does not contain any focusable elements or the first element with content is not focusable, the tabpanel should set tabindex="0" to include it in the tab sequence of the page. The current implementation is always setting a tabindex of -1 through the rehype tabs processor.
This PR also introduces a change to follow this behavior. For example, with the following <Tabs> component:
<Tabs>
<TabItem label="tab 1">

basic text

</TabItem>
</Tabs>

Tabbing through the page will first focus the tab list and then the tab panel (which does not contain any focusable element).

Altho, with the following code:
<Tabs>
<TabItem label="tab 1">

<input type="text" placeholder="email" />

</TabItem>
</Tabs>

Tabbing from the tab list will focus the input element immediately.

Finally, this PR adds support for the Home and End keys to navigate to the first and last tab respectively.
Accessibility-wise, I tested the changes with VoiceOver on macOS and the behavior seems to be correct and match the one from the ARIA Authoring Practices Guide and the React Aria implementation altho I do not have a machine with Windows to test with NVDA or JAWS.
Notes:

The rules to detect if a tabpanel contains a focusable element are borrowed from React Aria which follows this pattern as described in their documentation.
The rules are CSS selectors and used through the hast-util-select package. They could all be converted to JS conditions (e.g. node.tagName === 'input' && node.attributes.type !== 'hidden' && // etc.) but I think the CSS selectors are way more readable in this case. Any thoughts?
The changeset I added is fairly generic, should it contain a list of all the exact changes instead?

Thanks @HiDeoo, this looks great!
All the patterns seem to work in NVDA, the only issue is that with this change, using the shortcut to read the next line (↓) doesn't work, since we aren't capturing the down arrow and moving it to the tab panel.
I did some research, and most tabbed interface implementations don't do this as well, I know this is a recommendation from the Inclusive Components book but it might as well be an oversight for not considering the need to scroll the page.
Letting Chris know that this tradeoff is worth taking, considering the down arrow works again the moment the user focus (Tab) inside the tab panel.

All the patterns seem to work in NVDA

Thanks for taking the time to check this out, really appreciate it.

I did some research, and most tabbed interface implementations don't do this as well

Yeah, this is pretty much the conclusion I came to as well, although I guess it does not 100% mean that it's the right thing to do considering it is such a complex topic with lots of considerations.

authors: HiDeoo Yan-Thomas

repo: withastro/starlight


text:
No lens appear until we leave and reenter into the thumb.

fix : When large full image is lately loaded (into a pop-up), no lens will appear until we leave and reenter into the thumbnail.
Due to isReady === false when we pass into zoomOn function and display = 'block' is never set until mouseLeave and mouseEnter again.

Thank you for the pull request. Unfortunately I'll be traveling for next few weeks and won't have a chance to look into testing, merging and releasing this for a bit. Looks like a legit bugfix from a glance though!

No problem, take your time to check that there is no side effects.
We have a plan B to use my fork until it is fixed.
I think it's typically due to our use of the module into a pop-up.

Super late coming back to this, but I've had a chance to try this out now and this fix is not working for me. It probably solves your problem, but setting 'display = block' when images are loaded means the zoom will look enabled even if the mouse isn't over the image. Or if the image hasn't been clicked in the click-mode. So this issue will need a different approach, feel free to either update the PR or I'll try looking into a solution myself at a later point.

authors: mowgliLab wittlock

repo: wittlock/ngx-image-zoom