text:
Unnecessary /* fake(empty) types */ for nested imports; here: missing tRPC types

The @trpc/client package imports successfully, but the loaded types lack some information that is loaded from a subfolder of @trpc/server. These types missing lead to lack of type inference, killing the main benefit from the whole package, see the code below. This bug might affect other libraries relying on similar imports for their exported types.
You can use the below code to reproduce this, following the type definition of trpc.getCount.query in the client file, where the count variable incorrectly gets inferred as any.
@trpc/client is importing types from @trpc/server as well as @trpc/server/shared here.
While the former get resolved correctly to 'https://esm.sh/v102/@trpc/server@10.8.1/dist/index.d.ts', the latter resolves to https://esm.sh/v102/@trpc/server@10.8.1/shared/dist/index.d.ts, with shared and dist in the incorrect order. As they are not found, the modules are replaced as /* fake(empty) types */.
Reproduction steps
// server.ts
import { initTRPC } from "https://esm.sh/@trpc/server@10.8.1";
import { z } from "https://esm.sh/zod@3.20.2";

const t = initTRPC.create();

let count = 0;

const appRouter = t.router({
  getCount: t.procedure.input(() => {}).query(() => {
    return { count };
  }),
  increment: t.procedure.input(z.object({ amount: z.number().optional() }))
    .mutation((req) => {
      count += req.input.amount ?? 1;
    }),
});

export type AppRouter = typeof appRouter;

// client.ts
import {
  createTRPCProxyClient,
  httpBatchLink,
} from "https://esm.sh/@trpc/client@10.8.1";
import type { AppRouter } from "./server.ts";

export const trpc = createTRPCProxyClient<AppRouter>({
  links: [httpBatchLink({ url: "/api/trpc" })],
});

const res = await trpc.getCount.query();
export const count = res.count; // ⛔ this has type any, but should have type number

v104 removes the fake types, just returns 404 instead. Can you pls try again? thanks

Thanks for the update. Like you said, the types are still missing because imports from directories inside modules are resolved incorrectly.

@trpc/client imports types from @trpc/server/shared
The import is resolved to'https://esm.sh/v104/@trpc/server@10.8.1/shared/dist/index.d.ts'; but should be'https://esm.sh/v104/@trpc/server@10.8.1/dist/shared/index.d.ts';
The nested folder should be appended after, not before the /dist
missing types kill the benefits of the whole package
This bug might break packages, that import code from other packages this way

the wrong dts path may have been cached, i will release v105 soon

Just checking in again. With v120 & the latest tRPC version, the types inferred correctly. Thank you!

authors: ccssmnn ije


text:
CSS font color inconsistency

I've noticed that the list items gets rendered in a different font color than the paragraph (e.g. this post
Any suggestion on how to fix it?

You can apply the p styles to the list items too if you want them to match by changing this line to p, li or add another style for the li to just match the color from that block if desired

Thanks! Fixed. In the future, if I wanted to render the "callout" block in  Notion, what would I need to change? Right now a callout block does not get rendered at all.

Here's an example of what's needed to add support for rendering the callout block relevant code and example of it being rendered can be viewed on this post: https://notion-blog.now.sh/blog/my-second-post

Thanks @ijjk !
Unfortunately I get an error when I try to deploy:

Failed to compile.
02:08:21 PM
./src/pages/blog/[slug].tsx
02:08:21 PM
SyntaxError: /zeit/1c2a91a8/src/pages/blog/[slug].tsx: Unexpected token (245:10)
02:08:21 PM
243 |               break
02:08:21 PM
244 |           }
02:08:21 PM
245 |           case 'callout': {
02:08:21 PM
|           ^
02:08:21 PM
246 |               toRender.push(
02:08:21 PM
247 |
02:08:21 PM
248 |                   {value.format?.page_icon && (
02:08:21 PM
Build error occurred
02:08:21 PM
Error: > Build failed because of webpack errors
02:08:21 PM
at build (/zeit/1c2a91a8/node_modules/next/dist/build/index.js:12:900)
02:08:21 PM
error Command failed with exit code 1.
02:08:21 PM
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
02:08:21 PM
Error: Exited with 1
02:08:21 PM
at ChildProcess. (/zeit/2b7c515595ce4419/.build-utils/node_modules/@now/build-utils/dist/index.js:31347:24)
02:08:21 PM
at ChildProcess.emit (events.js:223:5)
02:08:21 PM
at ChildProcess.EventEmitter.emit (domain.js:475:20)
02:08:21 PM
at maybeClose (internal/child_process.js:1021:16)
02:08:21 PM
at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)`

I thought I was missing a { but my slug file looks exactly like yours.

@UberVero it looks like the extra { I added on the case above the callout didn't get added in that commit. I added another bracket on this line. It was just for preference, you could remove the closing bracket on this line if you'd prefer. Sorry for the un-necessary change 😅

source: gharchive/issue

authors: UberVero ijjk

repo: ijjk/notion-blog

license: MIT

license_type: permissive

license_source: github-api


text:
Allow plugins to be registered before Vue is mounted

This PR allows for conditionally auto-mounting the Vue component, allowing for any Vue plugins to be registered before mounting.
No breaking changes, this is fully backwards compatible. Default behaviour is still to auto-mount the component.
Also updated the React component flow for consistency (also no breaking changes, fully backwards compatible)
Changelog:

Adds an options argument to the mingleVue createComponent function, allowing to pass autoMount: false
Also added an options argument to the mingleReact createComponent function, for consistency.
Add return values to the mingleVue createComponent function, allowing for "manual" mounting.
Also added return values to the mingleReact createComponent function, for consistency.

Fixes https://github.com/ijpatricio/mingle/issues/17
Supersedes https://github.com/ijpatricio/mingle/pull/14

Hello @pepijnolivier
Thank you for this.
PS: I'll try to bring docs to this repo.

source: gharchive/pull-request

authors: ijpatricio pepijnolivier

repo: ijpatricio/mingle


text:
🛑 Uptime VF Bot is down

In 5bfa3c1, Uptime VF Bot (https://uptime-discord-bot.nexter32.repl.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Uptime VF Bot is back up in 0f01db4.


text:
what does volatile=True for?

Dear author:
I found your code very helpful. However, I have problems trying to read the following code:
https://github.com/ikostrikov/pytorch-trpo/blob/eb26e29ed75b7c7b46b0c717331cc7488ab16b8d/main.py#L111
I wonder the usage of volatile flag. I want to when u  set volatile to True/False.

I just doesn't compute gradients when one of the inputs is volatile.
But in the new versions of PyTorch it's deprecated.

repo: ikostrikov/pytorch-trpo


text:
[WIP] List alternatives in the README

crowbar is really cool, but there are some other really cool projects that solve similar problems. Arguably, rust-aws-lambda, despite its worse name, solves the problem better by merit of coming into existence after lambda added go support.
At the very least it seems like a good idea to let users know of the alternatives.
If you'd rather me word it differently or create a crowbar-biased comparison, I'd be happy to.

I'm marking this "WIP" for the moment since it seems more data is needed to figure out the best way to word this. I'll do a bit more digging and then take another swing at drafting an alternatives section.

@euank ping

@softprops Since you commented on the previous revision, does this now look like something you'd want to see merged?

I reached out to the rust lambda folks who have now started actually measuring things ;)  and removed its previous claims. I feel better I about this now.
Building crowbar crates is a solved problem for me now. What's left is implementation details that leak through that itself may have a remedy on the way https://github.com/ilianaw/rust-crowbar/pull/46

authors: euank ilianaw softprops

repo: ilianaw/rust-crowbar


text:
Doesn't seem to work / Or I might be doing something wrong

I installed this extension, loaded up a file "test.asp" with the code below.  There is no syntax highlighting at all.
Did I setup something wrong?
Thanks
Joe

<%
' PETERs ATTEMPT TO FIND OUT WHAT THE HELL THE PROBLEM IS, YET AGAIN, WITH THE CMS SYSTEM.
If Len(Request("file")) > 0 Then
Set ConnFile = Server.CreateObject("ADODB.Connection")
ConnFile.Open Session("ConnectString_Tables")
Set RSFile = CreateObject("ADODB.Recordset")

sql = "SELECT * FROM table_files WHERE id = '" & Request("file") & "' "

Session("SQL") = sql
RSFile.Open sql, ConnFile, 1, 2

if request("mode") = "delete" then

    If NOT(RSFile.EOF) Then
		response.write "deleting..."
        sql = " DELETE FROM TableViews WHERE File_Id = '" & Request("file") & "'; "
        sql = sql & " DELETE FROM table_files WHERE id = '" & Request("file") & "' "
        Session("SQL") = sql
        ConnFile.Execute sql
    Else
		response.write "Cannot find a record to delete..."
    End If

else
	'download the file ---THIS BRANCH MUST BE THE FIRST THING TO RUN...dont put the headers above this!
	'response.contenttype = RSFile("coding") this method doenst work with this component
	if right(lcase(RSFile("file_name")),3) = "tif" or right(lcase(RSFile("file_name")),4) = "tiff" then
		Response.ContentType = "image/tiff"
	elseif right(lcase(RSFile("file_name")),3) = "pdf" then Response.ContentType = "application/pdf"
	else
		 Response.ContentType = "application/x-msdownload"
	end if
	Response.AddHeader "Content-Disposition", "attachment; filename=" & RSFile("file_name")
	Response.BinaryWrite RSFile("FILE_data")
	response.end
end if 'delete/download

Set RSFile = Nothing
ConnFile.Close
Set ConnFile = Nothing

Response.End

End If
%>

This is strange. I think there is an issue ASP.tmLanguage syntax definition. Unfortunately I took this file from another open source project. Please let me know if you will find better language definition file, and I will update the extension.

Unfortunately I don't know much language files.  Thanks for looking into it.

Take a look to https://github.com/ilich/vscode-classic-asp/issues/4. It may help you.

Thank you, that helped.My next question would be why doesn't it open as an ASP file to begin with?  All my file extensions are .asp
Is that a different setting somewhere?
ThanksJoe
Date: Sun, 15 May 2016 23:26:23 -0700
From: notifications@github.com
To: vscode-classic-asp@noreply.github.com
CC: sherwoodwebdesigns@outlook.com; author@noreply.github.com
Subject: Re: [ilich/vscode-classic-asp] Doesn't seem to work / Or I might be doing something wrong (#3)
Take a look to #4. It may help you.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

Finally found a file association setting and added asp files to that, now they highlight automatically when loaded.
Joe

repo: ilich/vscode-classic-asp

license: mit

license_source: bigquery


text:
是否能支持更多的源

支持一下作者，最近更新好频繁啊。
我之前是用豆瓣FM的，也很喜欢它的模式，现在是用QQ音乐，因为版权多，没办法。
不知道Petal能否支持更多的源，API接口能不能做成可配置的。
很喜欢Petal这个界面，希望能经常用~

emmm, 支持更多的源基本是不可能了。。因为这里面的所有逻辑都是围绕着豆瓣FM的API写的，隔离不出来了。
做这个的初衷就是豆瓣FM没有PC客户端，其他的音乐基本都有客户端，所以就分着用吧 :joy:。

好的，理解~
另一个问题就是昨天clone了项目下来想跑一下没跑起来，发现里面一个依赖模块 upath 只有1.04，只支持node 版本4到9之间，最好yarn upgrade一下。

有得package目前还没有升级依赖，所以upath会版本错误，yarn --ignore-engines 可以解决这个问题。

有的package目前还没有升级依赖，所以upath会报版本错误，yarn --ignore-engines 可以解决这个问题。

repo: ilime/Petal


text:
fix error link in issue template config.yml

update https://github.com/illa-family/discussions to https://github.com/orgs/illa-family/discussions
📝 Description
Add a brief description.
💣 Is this a breaking change (Yes/No):

[x] Yes
[ ] No

🚧 How to migrate?
Don't need.
📝 Additional Information
fix issue template error

Thanks for your PR. But it seems like the link is incorrect. Could you please change the link to https://github.com/illa-family/illa-builder/discussions.

authors: AruSeito SAMZONG

repo: illa-family/illa-builder


text:
[AI Agent idea] SPAM Detector

Description
This AI Agent will take a piece of text content and then determine whether it is SPAM or HAM.

/assign @Rutam21

repo: illacloud/illa-builder


text:
2.2.2 release doesn't update dist version

Correct if I'm missing something!

Thank you, I just released 2.3.0 with proper dist version!

authors: ilyashubin joshdavenport

repo: ilyashubin/scrollbooster


text:
🛑 Profil Dosen STIS is down

In a3a7291, Profil Dosen STIS (https://stis.ac.id/dosen) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Profil Dosen STIS is back up in c52723f.

repo: im-perativa/stis-uptime


text:
Allow users to specify their ImageJ distribution

@ctrueden says (in #14):

I'd much rather create a napari-trackmate plugin or so instead of trying to shoehorn that functionality into this plugin.

That is fair, and I think I agree. But I do think you should be able to, with napari-imagej and no other napari plugins installed, initialize your ImageJ2 with whatever init string you want (including a locally wrapped ImageJ2 installation if desired). That way, people can invoke Fiji plugins with the search bar, for example—they just won't magically gain additional data structure conversions beyond those fundamentally supported. But for the vast majority of such plugins, they won't need anything extra.

Hmm, how do we add this functionality without it becoming an annoyance? If I just want stock ImageJ would I want to click through a startup screen every time I want to start the plugin? I'd prefer that this was some setting you could specify.
Maybe we could have an "napari-imagej-startup" plugin that allows you to modify where your imagej comes from? :laughing:

how do we add this functionality without it becoming an annoyance?

napari needs an options dialog, a la ImageJ2 OptionsPlugins. Then plugins could register typed options displayed in a dialog with components by magicgui.
And until then: next to the search bar we could add a little ⚙ button for bringing up the plugin's options.

@tlambert03 do you have an opinion on this?

this is in the works.  see https://github.com/napari/npe2/blob/main/npe2/manifest/contributions/_configuration.py ... which allows exactly this... it just hasn't been exposed in the contributions points yet

authors: ctrueden gselzer tlambert03

repo: imagej/napari-imagej


text:
"decompress" Package have high severity vulnerabilities

there is high severity vulnerability package "decompress" please use another one because it effect users security.
Package: decompress
Dependency of : imagemin-jpegtran
Path : imagemin-jpegtran > jpegtran-bin > bin-wrapper > download >
decompress

This seems to be solved by bumping packages, thank you for your report.
dc6b9bd855d04fe9bc05e3c568e50341fabaa88a
https://github.com/imagemin/jpegtran-bin/commit/49f230ffbf6160955e3e11150995bafd0135e31f

repo: imagemin/imagemin-jpegtran


text:
svlangserver for monaco-editor

I'm working on a React application that utilizes the react-monaco-editor component for Verilog language editing. I'm currently investigating language server options for Verilog support within the editor.
In that context, I'd like to inquire about the compatibility of svlangserver with react-monaco-editor.
Any insights on this or alternative Verilog language server solutions that might integrate well with react-monaco-editor would be much appreciated.
Thanks a lot!!

Unfortunately I have no familiarity with react-monaco-editor.

authors: kkanhere mohithsathyanarayanan

repo: imc-trading/svlangserver


text:
chore: add tracking header to imgix API requests

This PR adds the x-imgix-plugin header to requests made to the imgix management API, made possible by the imgix-management-js library.

Current dependencies on/for this PR:

main

PR #326   (this PR)

This comment was auto-generated by Graphite.

Verified this is working in both the product and page designer parts of the app

repo: imgix/sf-commerce-cloud


text:
Input should be fixed, clicking on it doesn't toggle the checkbox it is referring to

Aktuellen Wert auf dem Schieberegler anzeigen :
Input should be fixed, clicking on it doesn't toggle the checkbox it is referring to on slider question page

Merged in #136

repo: imi-ms/MoPat


text:
Add New Internship Part View

Should create a new internship part for the student in the specified semester.
View:

Result:

Improvements:

Refactor so that components can be re-used in EditInternship
Add localization


text:
feat: add support for @fastify/sensible errors

Add support for internalServerError exposed by the plugin.
When you throw that error your custom message is used in the response.
Closes #2

Can you resolve conflicts?

authors: dnlup simonecorsi

repo: immobiliare/fastify-sentry


text:
Does it support wss (SSL)?

Sorry, couldn't find it anywhere else, does this package supports usage of SSL and do I have to setup it?

You can try to add SSL parameters into server section of config file, Such as ssl_cert_file, ssl_key_file, ssl_method..
Config example: yii2-swoole-websocket/example/websocket/config/params.php
Docs: https://wiki.swoole.com/#/server/setting?id=ssl_cert_file
More easy way to get SSL support for your project is use Nginx proxy. You can add SSL support with Nginx and make it support websocket proxy


text:
Limit access to archived content like with drafts

Context
https://github.com/impactoss/impactoss-server/issues/409
We want archived content to only be visible to authenticated users with
the admin, manager, or contributor roles.
Changes
This commit limits access to archived content in the same way that we
currently do for draft content.
It also updates our controller tests to account for the new restriction,
making them more robust in the process.
Considerations
Along the way, I found it helpful to change the RSpec setting that
limits the maximum formatted output length for any given test failure.
The default value was quite low, and RSpec truncated away a lot of
vital information when using the match_array matcher. I've included
that change in this commit.

Along the way, I found it helpful to change the RSpec setting that
limits the maximum formatted output length for any given test failure.
The default value was quite low, and RSpec truncated away a lot of
vital information when using the match_array matcher. I've included
that change in this commit.

Awesome!

authors: lukearndt tmfrnz

repo: impactoss/impactoss-server


text:
Новый антагонист: Паучья королева

Добавляет нового антагониста.
Подробней - https://discord.com/channels/1040938900039929917/1235651299329179689/1235651299329179689
Добавляется новый антагонист — королева пауков. Вероятность её появления в вентиляции составляет 0,005.
Измерения КД будут производиться в секундах.
Характеристики королевы:

ХП — 300;
урон:
колющий — 25;
ядовитый — 5;
структурный — 15.

Способности королевы:

создание прочной стены из паутины (КД — 10);
создание синего кристалла для освещения (КД — 30);
создание королевской паутины, которая замедляет сильнее обычной (КД — 6);
создание накладной паутины, которая исчезает через некоторое время, но замедляет сильнее (КД — ваниль);
выпуск трёх паучат, которые нападают на ближайшего врага (КД — 40);
возможность стрелять ядом;
введение усыпляющего реагента в жертву (пассивная способность);
4 способности, связанные с яйцами (подробности ниже) (КД — разное).

Способности яиц:
Королева создаёт яйца, которые через некоторое время вылупляются в различных пауков.

Яйцо охранника:

КД — 200 секунд;
вылупление — 55 секунд.

Яйцо охотника:

КД — 300 секунд;
вылупление — 80 секунд.

Яйцо стрелка:

КД — 380 секунд;
вылупление — 80 секунд.

Яйцо призрака:

КД — 350 секунд;
вылупление — 80 секунд.

Характеристики пауков:

Паук-охранник (трутень):

ХП — 85;
урон:
колющий — 5;
структурный — 10.

Способности:

создание стены из паутины (КД — 8);
создание синего кристалла для освещения (КД — 30);
создание паутины (КД — 5);
создание накладной паутины, которая исчезает через некоторое время, но замедляет сильнее (КД — ваниль).

Паук-охотник (защитник):

ХП — 110;
урон:
колющий — 15;
структурный — 15.

Способности:

создание накладной паутины, которая исчезает через время, но замедляет сильнее (КД — ваниль);
создание самой слабой паутины (замедляет хуже всех).

Паук-призрак (разведчик, защитник):

ХП — 100;
урон:
ядовитый — 4;
структурный — 10.

Способности:

невидимость как у картонной коробки ЯО (пассивная способность);
введение усыпляющего реагента в жертву (пассивная способность);
создание самой слабой паутины (замедляет хуже всех) (КД — 10);
может стрелять ядом.

Паук-стрелок (дальнобойный защитник):

ХП — 80;
урон:
ядовитый — 5;
колющий — 2;
структурный — 5.

Способности:

может стрелять ядом (лучше всех);
введение усыпляющего реагента в жертву (пассивная способность);
создание клоунской паутины (КД — 25).

Пауки лечатся пассивно, достаточно хорошо.
Благодарим 3vlad31 за перевод, fufunuru за помощь со спрайтами и lugzag за подсказки по созданию прототипа.

зачем эти пустые строки внизу?

Не плох 👍

https://github.com/imperial-space/space-station14-public/pull/261 Новый


text:
Редспейс Репульсоры

О чём PR
В аплинк к агентам и ядерным оперативникам добавлены 2 новых предмета:

Редспейс Репульсор агентов: Наносит Heat: 12.5 Blunt: 12.5. (Изначально хотел чтобы вместо хита был электрический, но от него практически ни у кого нету статов) Используется в слоте перчаток, волокна которые обнаруживает детектив через сканнер показываются как обычные изолирующие. Скорость удара: 0.8. Отталкивает на чуть больше чем 7 тайлов.
Редспейс Репульсор нюкеров: Точно такой же, только есть отличие, он отталкивает на 6.2 тайла примерно. Только с более большой скоростью.
Стоимость: 10 ТК у агентов, 15 у нюкеров. (Есть возможность обсуждения этого предмета у нюкеров.)

Почему / Баланс
Агентам и нюкерам никогда не помешают новое вооружение. Что касается их характеристик, всё вполне сбалансировано. Почему? Он наносит 25 урона, на 5 меньше, чем лазерный меч, а меч стоит 8 ТК, а репульсоры 10. Отбрасывание не является таким уж сильным аспектом в этих репульсорах. Например, если откинуть человека на смазку, он не упадёт, а просто пролетит дальше. Такая же ситуация и с мылом. Весь смысл отбрасывания в том, что ты просто кидаешь человека, он не станится, ВООБЩЕ НИКАК. Он просто летит без возможности двигаться; если он врежется в какое-либо препятствие, то невозможность двигаться исчезнет. То есть это не стан, а просто отбрасывание. Они подходят либо в узком коридоре, куда нужно загнать жертву, либо чтобы оттолкнуть её далеко в коридор. Не такая уж и имба.
Media
https://github.com/user-attachments/assets/1baf2740-570f-4c86-90a1-8e816e5baa5d
https://github.com/user-attachments/assets/fe4de539-54b3-46a8-99f7-71cfb6bbda40

А вообще, насчёт баланса цены в 10 ТК у агентов: Это не самостоятельное оружие, оно скорее как вспомогательное, его отталкивание не позволит нормально убить цель не в узком коридоре, если бы оно стоило 12 ТК то его бы никто не покупал за такую цену.

его забанили пермой , но он не сдавался.....

И вообще это не финальный вариант, как только я более менее пойму как работает C# я сделаю ему работу от ТК; как перчатка гориллы в артефактах, только там от ядер аномалий.

И вообще это не финальный вариант, как только я более менее пойму как работает C# я сделаю ему работу от ТК; как перчатка гориллы в артефактах, только там от ядер аномалий.

А если нюкер наденет перчатки-репульсоры и начнет бить энергомечем кого-то , то урон от перчаток и отталкивание сработают?

И вообще это не финальный вариант, как только я более менее пойму как работает C# я сделаю ему работу от ТК; как перчатка гориллы в артефактах, только там от ядер аномалий.

А если нюкер наденет перчатки-репульсоры и начнет бить энергомечем кого-то , то урон от перчаток и отталкивание сработают?

То просто будет бить энерго-меч.

И вообще это не финальный вариант, как только я более менее пойму как работает C# я сделаю ему работу от ТК; как перчатка гориллы в артефактах, только там от ядер аномалий.

А если нюкер наденет перчатки-репульсоры и начнет бить энергомечем кого-то , то урон от перчаток и отталкивание сработают?

То просто будет бить энергомеч.

его забанили пермой , но он не сдавался.....

Рано сдаваться...

Скоро исправлю некоторые моменты, ПОКА НЕ МЕРДЖИТЬ.

Я ещё там основное описание на английском укоротил (Которое вы не увидите)

Привет чюваки.

Походу Миртону не зашел мой прототип(((

Миртон возможно в отпуске. По крайне мере мне так кажется

Походу Миртону не зашел мой прототип(((

Тоже сидишь и каждый час обновляешь страницу, чтобы посмотреть не приняли ли ПР? Уэээ, когда уже(

Походу Миртону не зашел мой прототип(((

Тоже сидишь и каждый час обновляешь страницу, чтобы посмотреть не приняли ли ПР? Уэээ, когда уже(

Да не, мне уведомления на почту приходят если кто-то написал коммент/замерджил или другое.

Севен, прими в друзьях ДСа. Мы с тобой уже вместе почти 3 недели висим. Почти как родные теперь

Севен, прими в друзьях ДСа. Мы с тобой уже вместе почти 3 недели висим. Почти как родные теперь

Ты точно мне отправил запрос? А то я чет не вижу.

Севен, прими в друзьях ДСа. Мы с тобой уже вместе почти 3 недели висим. Почти как родные теперь

Ты точно мне отправил запрос? А то я чет не вижу.

Уэээ... Я скопировал твой ник тут и в ДСе вставил и отправил запрос. Похоже у тебя другой ник в ДСе. Увы

Уэээ... Я скопировал твой ник тут и в ДСе вставил и отправил запрос. Похоже у тебя другой ник в ДСе. Увы

seven221 его юзнейм в ДСе


text:
Rule Proposal: exports-last

I would like to propose a new rule which enforces that all export statements are at the end of the file.
Why?
I really like to keep all my exports at the end of the file so I can quickly scan what a file exports.

Sounds good to me.
With commonjs, I have the same preference. I don't necessarily have it for ES6 modules at the moment, but this makes sense to me to have this rule.
@k15a Would you be interested in working on this? :)

I am interested but I tried working on another issue 2 times and failed hard so it's not a guarantee for success :laughing:

Sounds like a reasonable style guide rule to me. 👍

Good afternoon! The question is: can I cancel the rule (put it in ignor) for classes that are exported at the beginning of the file export default class SomeClass, followed by defaultProps and PropTypes?

Good afternoon! The question is: can I cancel the rule (put it in ignor) for classes that are exported at the beginning of the file export default class SomeClass, followed by defaultProps and PropTypes?

This would be reasonable for storybook csf files, since templating would require exports to be mixed within the file
It's not a big deal to disable the rule on every stories file but would be nice to be able to handle it in the eslint config

@RodrigoNovais you can use overrides to disable them on every story file at once, in the config.

Didn't know that's possible, thank you @ljharb

authors: RodrigoNovais benmosher jfmengels k15a ljharb sevor005

repo: import-js/eslint-plugin-import


text:
Filtering by production spec causes Cadence badges to not be seen

Summary
The "pending production digital lines" query looks at an order, takes the designs, takes the line items, and returns a row for every combination of the two, disregarding what's actually selected on the production specification.
After a support ticket with Shopworks, they gave us access to query the production specification, and I merged #67 to accurately reflect that.
I then promptly received a ticket from production saying that they couldn't see any badges.
I've reverted #67 in #71 for now.
Why?
The Impress badges have a single line item, with production applied

SELECT OrderDes.id_Design          AS design_id,
       LinesOE.cn_LineQuantity_Req AS quantity,
       LinesOE.OrderInstructions   AS instructions
FROM Orders
         JOIN OrdDesLoc ON Orders.ID_Order = OrdDesLoc.ID_Order
         JOIN OrderDes ON OrderDes.ID_OrderDesign = OrdDesLoc.id_OrderDesign
         JOIN LinesCompletion ON OrdDesLoc.ID_OrderDesLoc = LinesCompletion.id_OrderDesLoc
         JOIN LinesOE ON LinesCompletion.id_LineOE = LinesOE.ID_LineOE
WHERE Orders.sts_Produced IN (0, 0.5)
  AND Orders.id_OrderType = 63
  AND LinesOE.OrderInstructions IS NOT NULL
UNION
SELECT OrderDes.id_Design          AS design_id,
       LinesOE.cn_LineQuantity_Req AS quantity,
       LinesOE.OrderInstructions   AS instructions
FROM LinesOE
         JOIN LinesCompletion ON LinesOE.ID_LineOE = LinesCompletion.id_LineOE -- never matches, because the design is not on the parent
         JOIN OrderDes ON LinesCompletion.id_OrderDesign = OrderDes.ID_OrderDesign
WHERE LinesOE.ID_LineOE IN (SELECT DISTINCT LinesOE.id_LineOE_AssbParent -- parent grabbed here
                            FROM LinesOE
                            WHERE LinesOE.ID_LineOE IN (SELECT LinesCompletion.id_LineOE
                                                        FROM LinesCompletion
                                                        WHERE LinesCompletion.id_order IN (SELECT Orders.ID_Order
                                                                                FROM Orders
                                                                                WHERE Orders.sts_Produced IN (0, 0.5)
                                                                                AND Orders.id_OrderType = 63)
                                                          AND LinesCompletion.sts_ApplyLocation = 1)
                              AND LinesOE.id_LineOE_AssbParent <> 0);

repo: impressdesigns/charlie


text:
Refactor App Architecture

Would you be willing to let me refactor your apps architecture?
I would:

reduce the size of widgets (some are 1000 lines long)

remove state from views (turn all views stateless) and place presentation state in view models (using Provider package)

I can open a draft PR with some ideas I have and you can let me know if you like them.

@kwe92 Sure, it would be great, I know my code sucks. DM me on X, if you wanna discuss these changes.

@imrofayel was the app meant to be ran in the browser on any device?

@kwe92 it's a desktop app primarily for Windows.

It is a great app, refactoring could be step-by-step
Like:

Adding code formatting like lefthook, so on push, it will fail if the code is not formatted
features folders and clean architecture
application(blocs) - data(services/providers) - domain(repositories) - presentation(pages/ui)
data > get data, domain > prepare the data,  application > handle data logic in states relevant to UI > presentation
and so on

@amrgetment Thank you for these suggestions. I wanna refactor this app since long but kinda busy in studies and job. But I'm willing to support any contribution. If you wanna collaborate on it, let me know. 🕊

authors: amrgetment imrofayel kwe92

repo: imrofayel/Ozan


text:
Resolve hostnames asynchronously

Resolves #6
Thanks for the tool, I love it!
So, in addition of resolving the hostnames in a thread pool I went for making it asynchronous. It should be more performant as we will not block the threads waiting for the response from the dns servers. Let me know if you like the approach.
I have doubts about some changes I made, I will leave some comments.

This looks great! I'll go over it in the next few days.

Hey, just a heads-up, I'm waiting for this issue to be solved. Tokio 0.2.0 was released two days ago and broke a bit the ecosystem, dependent crates are catching up.

Thanks for the update!

It seems that the issue I mentioned can't be fixed until next week because some dependency is blocking it. For the moment I've done as the author suggests and I'm using the branch that will be merged when the issue is solved.
We should either not merge this PR until the issue is solved or change the version in Cargo.toml as soon as a new one is available (remember that you can't cargo publish with a git dependency).
I think I've dealt with all the suggestions, let me know what you think!

Hey, just squashed and rebased on top of the new changes in master to solve the conflicts

You are extremely fast :D Still merging

The changes look great. I especially liked the naming (eg. dns_client), your solution with the cache method and the Lookup trait. Good stuff.
I also took it out for a spin and it works really fast!
About the trust-dns-resolver issue: I have managed in the past to publish to cargo with a git dependency. All it required was to add the version as well as the url to Cargo.toml (though that was a dev dependency, so I wonder if it will also work here pondering eomji). I wouldn't want to do that if it can be avoided though (because github is a mutable medium).
Let's give it a week until we merge and if it's not over by then, we'll think up another solution for it. Sounds okay?
Meanwhile I'm going to hold off on releasing the other changes in master.

Sounds good to me!

A new version of trust-dns was released :tada:

authors: ebroto imsnif

repo: imsnif/what


text:
WIP: block ip ping data

example not-runnable code for discussion

addressed in https://github.com/imup-io/client/pull/44

authors: phanyzewski stevenaldinger

repo: imup-io/client


text:
vite打包部署后引用编辑器出现 st.join is not a function

Describe the issue
本地正常
但打包部署后会出现

Procedure version
node版本 16.20.2
Reproduction link
No response

方便的话，提供一下还原问题的可运行代码，和你的部署方式

只要引入就会报错
/*
 * @Description:打包配置
 * @Author: cyd @.***
 * @Date: 2023-06-26 16:41:56
 * @LastEditTime: 2023-11-28 14:10:40
 /
import { defineConfig } from 'vite';
import vue from @./plugin-vue';
import commonjs from @./plugin-commonjs';
import requireTransform from 'vite-plugin-require-transform';
import path from 'path';
import viteCompression from 'vite-plugin-compression';
import legacy from @.**/plugin-legacy';
import { createSvgIconsPlugin } from 'vite-plugin-svg-icons';
// https://vitejs.dev/config/
export default defineConfig({
  // root: resolve('./'), //  入口index.html，注意入口js应该与index.html 同一目录下（只能写到目录，不能写到具体文件）
  base: './',
  // publicDir: resolve('static'), //静态资源文件夹
  plugins: [
    commonjs() as any,
    legacy({
      targets: ['defaults', 'not IE 11']
    }),
    vue(),
    createSvgIconsPlugin({
      iconDirs: [path.resolve(process.cwd(), 'src/assets/svg')],
      symbolId: '[name]'
    }),
    requireTransform({
      fileRegex: /.js$|.vue$|.png$|.ts$|.jpg$/
    }), //配置require
    viteCompression({
      verbose: true,
      disable: false,
      threshold: 10240,
      algorithm: 'gzip',
      ext: '.gz'
    })
  ],
  css: {
    preprocessorOptions: {
      scss: {
        additionalData: @.*** "./src/assets/theme/theme.scss";' // 加载全局样式，使用scss特性
      }
    }
  },
  resolve: {
    alias: {
      // 这里就是需要配置resolve里的别名
      '@': path.join(__dirname, './src') // path记得引入
      // 'vue': 'vue/dist/vue.esm-bundler.js' // 定义vue的别名，如果使用其他的插件，可能会用到别名
    }
  },
  optimizeDeps: {
    include: ['@/../lib/vform/designer.umd.js'] //此处路径必须跟main.js中import路径完全一致！
  },
  build: {
    commonjsOptions: {
      include: /node_modules|lib/ //这里记得把lib目录加进来，否则生产打包会报错！！
    },
    outDir: 'JcCloudWeb',
    cssCodeSplit: true,
    rollupOptions: {
      input: 'index.html',
      output: {
        // 静态资源打包做处理
        chunkFileNames: 'static/js/[name]-[hash].js',
        entryFileNames: 'static/js/[name]-[hash].js',
        assetFileNames: 'static/[ext]/[name]-[hash].[ext]',
        manualChunks(id) {
          if (id.includes('node_modules')) {
            return id.toString().split('node_modules/')[1].split('/')[0].toString();
          }
        }
      }
    },
    minify: 'terser',
    terserOptions: {
      // 清除console和debugger
      compress: {
        drop_console: true,
        drop_debugger: true
      }
    }
  },
  server: {
    port: 8086,
    host: '0.0.0.0',
    headers: {
      'Access-Control-Allow-Origin': '*'
    },
    proxy: {
      '/dev-api': {
        target: 'http://localhost:5008',
        changeOrigin: true,
        rewrite: p => p.replace(/^/dev-api/, '')
      }
    }
  }
});
打包后部署到服务器使用nginx代理
我打算先用cdn方式，感谢帮忙
陈毅东
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "imzbf/md-editor-v3"                                                                                @.>;
发送时间: 2024年2月1日(星期四) 凌晨0:34
@.>;
@.@.>;
主题: Re: [imzbf/md-editor-v3] vite打包部署后引用编辑器出现 st.join is not a function (Issue #447)
方便的话，提供一下还原问题的可运行代码，和你的部署方式
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

只要引入就会报错 /*  * @description:打包配置  * @author: cyd @.***  * @Date: 2023-06-26 16:41:56  * @LastEditTime: 2023-11-28 14:10:40  / import { defineConfig } from 'vite'; import vue from @./plugin-vue'; import commonjs from @./plugin-commonjs'; import requireTransform from 'vite-plugin-require-transform'; import path from 'path'; import viteCompression from 'vite-plugin-compression'; import legacy from @./plugin-legacy'; import { createSvgIconsPlugin } from 'vite-plugin-svg-icons'; // https://vitejs.dev/config/ export default defineConfig({   // root: resolve('./'), //  入口index.html，注意入口js应该与index.html 同一目录下（只能写到目录，不能写到具体文件）   base: './',   // publicDir: resolve('static'), //静态资源文件夹   plugins: [     commonjs() as any,     legacy({       targets: ['defaults', 'not IE 11']     }),     vue(),     createSvgIconsPlugin({       iconDirs: [path.resolve(process.cwd(), 'src/assets/svg')],       symbolId: '[name]'     }),     requireTransform({       fileRegex: /.js$|.vue$|.png$|.ts$|.jpg$/     }), //配置require     viteCompression({       verbose: true,       disable: false,       threshold: 10240,       algorithm: 'gzip',       ext: '.gz'     })   ],   css: {     preprocessorOptions: {       scss: {         additionalData: @.* "./src/assets/theme/theme.scss";' // 加载全局样式，使用scss特性       }     }   },   resolve: {     alias: {       // 这里就是需要配置resolve里的别名       '@': path.join(__dirname, './src') // path记得引入       // 'vue': 'vue/dist/vue.esm-bundler.js' // 定义vue的别名，如果使用其他的插件，可能会用到别名     }   },   optimizeDeps: {     include: ['@/../lib/vform/designer.umd.js'] //此处路径必须跟main.js中import路径完全一致！   },   build: {     commonjsOptions: {       include: /node_modules|lib/ //这里记得把lib目录加进来，否则生产打包会报错！！     },     outDir: 'JcCloudWeb',     cssCodeSplit: true,     rollupOptions: {       input: 'index.html',       output: {         // 静态资源打包做处理         chunkFileNames: 'static/js/[name]-[hash].js',         entryFileNames: 'static/js/[name]-[hash].js',         assetFileNames: 'static/[ext]/[name]-[hash].[ext]',         manualChunks(id) {           if (id.includes('node_modules')) {             return id.toString().split('node_modules/')[1].split('/')[0].toString();           }         }       }     },     minify: 'terser',     terserOptions: {       // 清除console和debugger       compress: {         drop_console: true,         drop_debugger: true       }     }   },   server: {     port: 8086,     host: '0.0.0.0',     headers: {       'Access-Control-Allow-Origin': ''     },     proxy: {       '/dev-api': {         target: 'http://localhost:5008',         changeOrigin: true,         rewrite: p => p.replace(/^/dev-api/, '')       }     }   } }); 打包后部署到服务器使用nginx代理 我打算先用cdn方式，感谢帮忙 陈毅东 @.**
…
------------------ 原始邮件 ------------------ 发件人: "imzbf/md-editor-v3" @.>; 发送时间: 2024年2月1日(星期四) 凌晨0:34 @.>; @.@.>; 主题: Re: [imzbf/md-editor-v3] vite打包部署后引用编辑器出现 st.join is not a function (Issue #447) 方便的话，提供一下还原问题的可运行代码，和你的部署方式 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

👌，问题还原不了，这多半和你构建项目的环境有关系

找到问题了
跟require插件冲突
陈毅东
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "imzbf/md-editor-v3"                                                                                @.>;
发送时间: 2024年2月1日(星期四) 中午1:35
@.>;
@.@.>;
主题: Re: [imzbf/md-editor-v3] vite打包部署后引用编辑器出现 st.join is not a function (Issue #447)
只要引入就会报错 /*  * @description:打包配置  * @author: cyd @.***  * @Date: 2023-06-26 16:41:56  * @LastEditTime: 2023-11-28 14:10:40  / import { defineConfig } from 'vite'; import vue from @./plugin-vue'; import commonjs from @./plugin-commonjs'; import requireTransform from 'vite-plugin-require-transform'; import path from 'path'; import viteCompression from 'vite-plugin-compression'; import legacy from @./plugin-legacy'; import { createSvgIconsPlugin } from 'vite-plugin-svg-icons'; // https://vitejs.dev/config/ export default defineConfig({   // root: resolve('./'), //  入口index.html，注意入口js应该与index.html 同一目录下（只能写到目录，不能写到具体文件）   base: './',   // publicDir: resolve('static'), //静态资源文件夹   plugins: [     commonjs() as any,     legacy({       targets: ['defaults', 'not IE 11']     }),     vue(),     createSvgIconsPlugin({       iconDirs: [path.resolve(process.cwd(), 'src/assets/svg')],       symbolId: '[name]'     }),     requireTransform({       fileRegex: /.js$|.vue$|.png$|.ts$|.jpg$/     }), //配置require     viteCompression({       verbose: true,       disable: false,       threshold: 10240,       algorithm: 'gzip',       ext: '.gz'     })   ],   css: {     preprocessorOptions: {       scss: {         additionalData: @.* "./src/assets/theme/theme.scss";' // 加载全局样式，使用scss特性       }     }   },   resolve: {     alias: {       // 这里就是需要配置resolve里的别名       '@': path.join(__dirname, './src') // path记得引入       // 'vue': 'vue/dist/vue.esm-bundler.js' // 定义vue的别名，如果使用其他的插件，可能会用到别名     }   },   optimizeDeps: {     include: ['@/../lib/vform/designer.umd.js'] //此处路径必须跟main.js中import路径完全一致！   },   build: {     commonjsOptions: {       include: /node_modules|lib/ //这里记得把lib目录加进来，否则生产打包会报错！！     },     outDir: 'JcCloudWeb',     cssCodeSplit: true,     rollupOptions: {       input: 'index.html',       output: {         // 静态资源打包做处理         chunkFileNames: 'static/js/[name]-[hash].js',         entryFileNames: 'static/js/[name]-[hash].js',         assetFileNames: 'static/[ext]/[name]-[hash].[ext]',         manualChunks(id) {           if (id.includes('node_modules')) {             return id.toString().split('node_modules/')[1].split('/')[0].toString();           }         }       }     },     minify: 'terser',     terserOptions: {       // 清除console和debugger       compress: {         drop_console: true,         drop_debugger: true       }     }   },   server: {     port: 8086,     host: '0.0.0.0',     headers: {       'Access-Control-Allow-Origin': ''     },     proxy: {       '/dev-api': {         target: 'http://localhost:5008',         changeOrigin: true,         rewrite: p => p.replace(/^/dev-api/, '')       }     }   } }); 打包后部署到服务器使用nginx代理 我打算先用cdn方式，感谢帮忙 陈毅东 @.**
…
------------------ 原始邮件 ------------------ 发件人: "imzbf/md-editor-v3" @.>; 发送时间: 2024年2月1日(星期四) 凌晨0:34 @.>; @.@.>; 主题: Re: [imzbf/md-editor-v3] vite打包部署后引用编辑器出现 st.join is not a function (Issue #447) 方便的话，提供一下还原问题的可运行代码，和你的部署方式 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
👌，问题还原不了，这多半和你构建项目的环境有关系
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

vite-plugin-require-transform这个是吗

对
陈毅东
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "imzbf/md-editor-v3"                                                                                @.>;
发送时间: 2024年2月1日(星期四) 下午2:15
@.>;
@.@.>;
主题: Re: [imzbf/md-editor-v3] vite打包部署后引用编辑器出现 st.join is not a function (Issue #447)
vite-plugin-require-transform这个是吗
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

authors: CDCDA imzbf


text:
Tab is ignored on first line

If a put a text with tab on first line(like a code) this tab is ignored on editor , the bug can be reproduced here
<script>
$('#myEditor').markdownEditor({
  // Options
});
</script>
<div id="myEditor">
	System.out.println();
</div>

Happen with space too

@inacho Any chance of merge it?

The spaces issue is fixed in the latest release (v1.3.0) you can test it here:
http://jsfiddle.net/t476p7wp/2/

authors: inacho mageddo

repo: inacho/bootstrap-markdown-editor


text:
Hidden coordinates aren't showing when the observer trusts you in API v2

Describe the bug
When you view an obscured observation by someone who trusts you with their hidden coordinates, the hidden coordinates are not being shown.
To Reproduce
Steps to reproduce the behavior:

In API v1, Visit an obscured observation by a user that trusts you with their hidden coordinates
You should see a stemmed marker on the map on the true coordinates; when you click details you should see a "Why You Can See the Coordinates" section explaining that the observer trusts you
Append ?test=apiv2 to the URL and load again
Now the marker has no stem, is on the obscured coordinates, and you're not seeing the "Why You Can See the Coordinates" section under Details

Expected behavior
User-to-user trust like this should continue to work in API v2
Additional context
I feel like this was working at some point...

I actually did the Rails side of this in df6572008f60845b8ef5972a92a9afbde6f67829, but apparently I neglected to update the API.

repo: inaturalist/inaturalist


text:
Show either catches or catch per km waterway

I was going through the project proposal and noticed that this is also one of the requirements for the dashboard. I would show this as number of catches per km waterway for each km²

Hi @EmmaCartuyvels1:
If I understand correctly, that would be a different map that shows 1x1km cells over Belgium. For each cell, we would show the number of catches divided by the length of waterways, is that correct?
Please note that I'll need source some GIS data (shapefile) for those waterways, preferably in Open Data. I found the following shapefiles https://www.atlas-belgique.be/index.php/en/resources/map-data/ from KUL/Belpo/ULiège. Do you think the "waterway" file is good for our use?

Needed:

Have waterway line layer
Calculate number of km waterway per km2: x
Calculate number of occurrences per km2: y
Provide y/x in map with km2 grid

Hi @EmmaCartuyvels1, I've started some work with the "waterways" file from atlas-belgique.be so I can already make progress! Here is a screenshot showing its content, as far as I understand it only contains navigable bodies of water, which might not been enough for MICA:

Can you have a look and confirm if we need to find another source of data or not?

Hi Nicolas, we will need to work with a layer that includes all waterways and water bodies so this won't be enough

@EmmaCartuyvels1: I've experimented with the data found at http://hydro.iis.u-tokyo.ac.jp/~yamadai/OSM_water/index.html and I think it might actually be used to assign a "water coverage score" to each 1km square:

(the water data is representend by highlighted "pixels", the red grid is the 1km fishnet and the background is standard openstreetmap for reference)
We could count the number/surface of pixels in each red square, and we'd have a decent approximation of how much inland water occupies it, n?o

@peterdesmet: if you have some time :sweat_smile: , don't hesitate to give your input on that (those last two comments might be enough to grasp the situation)

I've asked for some more details on the Dutch way of calculating this, since I do think they work with the length of the waterways. I'll update once I hear back from them.

@peterdesmet:
Thanks for the feedback. Answers below:

OSM water layers is indeed a raster data source. Each pixel covers roughly 90 meter on 55, so if my calculation is correct we can fit around 200 pixels in each of the 1 km square. By simply counting pixels, we could therefore calculate an 'inland water coverage score' between 0 and 200 for each square. Each pixel also provides a value (1: ocean, 2: lake, 3: major river, 4 canal, 5: small stream), so we could maybe improve our score calculation by adding some ponderation (1 pixel marked as major river would count for more than a pixel marked for a small stream).
For your second question, I was indeed confusing in my use of the grid/square/fishnet terminology, but itś pretty simple: the fishnet is the grid, and it contains 1km squares over our region of interest.

About the data source, I think we have 3 possible routes now:

use the raster date from "OSM water layers", as described above
wait for the Dutch team's answer to see if their calculation method is applicable here and better than our other approaches
Apparently the OSM water layers also exist in vector format. That could give us even better results (precise surface percentage of inland water for each square), but it might be a bit more complex to manipulate than the raster version.

On my side, I think I'll focus more on the development side of the feature (make the dashboard able to show the squares and their score), and go back to the data question later, when things get a bit clearer.

Hi Nico,
This was the answer from Dolf:
We only look at the bank length to be processed:
For ponds and lakes, the perimeter is taken.
For watercourses up to 6 meters wide, the single bank length is included (such a watercourse can be worked from one side. For watercourses that are wider than 6 meters, both banks are included.

Thanks Emma!
Can you provide me  data to calculate this? I'd need:

data in a GIS format (shapefile, geopackages, ...)
covering Belgium, Germany and Netherlands
that includes all water courses and include width information
and also includes lakes/ponds

If you can find that it would be immensely helpful. In case we cannot find this data (I am especially unsure about the river width data), I can try a different approach such as what was discussed above. Another approach would be doing it "the Dutch way" but treating all rivers the same (irrespective of their width).

Update: first implementation visible on https://mica-uat.inbo.be/

Hi @EmmaCartuyvels1 : do you still have remarks and things to change for this feature? Otherwise I was thinking of closing the issue so get a better view of what is still left to do. Thanks!

authors: EmmaCartuyvels1 niconoe peterdesmet

repo: inbo/mica-dashboard


text:
Dwc mapping

add dwc mapping in repo

PS code ziet er goed uit ;-) maar ik zou graag eens naar de data kijken kwestie van eens na te gaan of het klopt!

https://github.com/inbo/sk-analyse/blob/Dwc_mapping/darwincore/processed/occurrence.csv @SanderDevisscher

Ik hoop volgende week de tijd te vinden om ernaar te kunnen kijken ;-)

@DimEvil er zijn bljkbaar een aantal bijvangsten verdwenen uit de occurrence ("darwincore/processed/occurrence.csv") dataframe.
> sum(is.na(occurrence$individualCount))
[1] 14504
> sum(is.na(gbif_stierkikker_bijvangsten$individualCount))
[1] 14668

enig idee hoe dit komt ?  Het komt allesinds al niet doordat er stierkikker NA's in zitten want dan zou je er meer verwachten in de occurrences. Ik heb ook al getest of er soorten ontbreken in de occurrence df die wel voorkomen in de bijvangsten en ook dit is niet het geval.
PS de stierkikkers zitten er op het eerste zicht wel goed in:
> sum(gbif_stierkikker_vangsten$individualCount, na.rm = TRUE) == sum(occurrence$individualCount, na.rm = TRUE)
[1] TRUE

found it, er zitten "NA" soorten in de bijvangsten => alles is ok dus

authors: DimEvil SanderDevisscher

repo: inbo/sk-analyse


text:
styleguide R code has no referral to tidyverse style guide

While reading into issue #116 on the INBO R styleguide, and myself rather using the tidyverse style guide, I wonder why we don't just refer to the latter and redirect people there (and if needed, propose enhancements there). It seems to me that we want to adhere to it anyway. Maybe I overlook things ;-)
Currently, there is no referral to the tidyverse style guide at all, which is the main point of this issue.

I agree, good point!

The Tidyverse style guide is good and community maintained, so pointing to that one (with maybe some specific INBO clarifications) would be less maintenance for us. @ThierryO is there much in our style guide that differs from the Tidyverse style guide? If so, are there good reasons for them?

Ok to refer to it as an additional guideline.  As it is rather long, I think it would be nice to keep a short list of the most important rules/guidelines in our tutorial (to not force everyone to read the whole guideline).  And of course the items that are specific for INBO.
From memory: adding INBO as copyrighter is something that is unique to our guideline.  ;-)  And also the fact that it is allowed to use different styles for parameter names and function names.

While working on PR #117, I'm wondering: is the guideline not growing too long for one page?  If I am not mistaken, it was first written for package development (some years ago), and only after a comment I noticed it is now used more general.  Because all different subjects are mixed, it becomes a bit confusing and difficult to pick the right things.
Would it be a good idea to split this page in 3 different pages?

one page on coding style that is useful for all users (Scope, Syntax and sections R script and RMarkdown under File Structure?)
one page on subjects specific to package development (Documentation and File Structure / R Package?)
one page on recommended packages

After discussion yesterday: current suggestion is to refer to the checklist package for this, instead of maintaining a separate styleguide.
Further, if a vignette in checklist is/becomes available on this topic, this tutorial page can be dropped after handling #262.

authors: ElsLommelen florisvdh peterdesmet

repo: inbo/tutorials


text:
Image page d’accueil trop lourde / retirer le lazy loading sur l'image

Implémenter la technique qui suit : charger une version pixelisée de l’image dans un premier temps, qui sera remplacée par l’image animée lorsqu’elle sera chargée à son tour. Permettra de faire d’une pierre deux coups : accélérer le chargement de la page, supprimer le layout shift induit par le chargement de l’image.

À première vue : l'image semble être inline (et donc être chargée en même temps que le reste du dom) et attend le chargement et l'initialisation du script AnimatedIllustration.chunk.js. Peut être juste changer pour que l'image s'affiche (en statique) avant le chargement du script ?

Au final le poids de l'image en soi n'est pas le problème mais plutôt la manière dont elle était chargée, en lazy loading, et donc avec un délai, ce qui faisait se décaler le contenu de la page vers le bas, ce qui est pénalisé sur le plan du SEO.

authors: bjlaa florianpanchout lbranaa

repo: incubateur-ademe/nosgestesclimat-site


text:
Ingest API (Part 3)

Created by: @pepe-zamarripa Aug 02 2022 at 14:39 CET
Last updated: Aug 02 2022 at 14:41 CET
ClickUp ID: IK-3706
Given
The GO SDK Ingest API
When
Customer wants to ingest data
Then
A python SDK ingest API should be available.
Please update the wiki when feature complete: https://www.notion.so/indykite/SDK-feature-comparison-8d8333a604fc4327b0a9c14ad02f42e8
The GO interface can be found here: https://buf.build/indykite/indykiteapis.
Use the following command to generate the required proto bufs: https://github.com/indykite/jarvis-sdk-python/blob/master/gen_proto.sh
echo "Generating protobufs ..."
buf generate buf.build/indykite/indykiteapis
buf generate buf.build/envoyproxy/protoc-gen-validate
echo "Rewriting the imports..."
packages=("indykite" "validate")
for package in  $ {packages[@]}; do
       find jarvis_sdk/indykite/. -name '*.py' -exec sed -i -e "s/from  $ {package}/from jarvis_sdk. $ {package}/g" {} ;
done
echo "Done"

Commented by: @pepe-zamarripa Aug 02 2022 at 14:41 CET
@martasd when you come back from vacations, we need to update the title and the content of the ticket, so we can differentiate the scope during each sprint. cc @bayegan

Closing - duplicate of https://github.com/indykite/jarvis-sdk-python/issues/73

Hi @pepe-zamarripa. Why did you reopen this issue?

Hi @martasd! I re-opened the issue because its status is blocked.

authors: adelefelicia bayegan martasd pepe-zamarripa

repo: indykite/jarvis-sdk-python


text:
[Bug]: chatting with OpenAI model  appear issue

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
infiniflow/ragflow
Commit ID
#flaskwrongrag0004
Other environment information
No response
Actual behavior
chatting appear error with gpt

Expected behavior
No response
Steps to reproduce
set model of openai gpt,embedding knowledge is  ok ,but appear error when i was chatting with gpt3 or gpt4

Additional information
No response

hi @Rama-19  This is because the default embedding model was not added to the relevant data table, but this does not affect usage.

repo: infiniflow/ragflow


text:
[Bug]: file Parsing failed

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
main
Commit ID
2afe7a7
Other environment information
当前仓库的名称是：ragflow
当前目录的Git版本号是: 2afe7a7
操作系统: Ubuntu 22.04 (内核版本: 6.5.0-27-generic)
CPU类型：x86_64
内存容量：
Docker版本：26.0.1,
Python版本：Python未安装

Actual behavior

can't parse any file.
removed all docker volume, not working.
Expected behavior
No response
Steps to reproduce
1. Normal deployment.
2. Create a knowledge base.
3. Upload any document.

Additional information
No response

Upgrade to latest dev version of the docker image. Problem solved.


text:
[14.0] ISPN-14256 CLI should work with piped input

https://issues.redhat.com/browse/ISPN-14256

Is https://ci.infinispan.org/job/Infinispan/job/PR-10428/1/testReport/junit/org.infinispan.server.cli/CliIT/testCliBatchError/ related? I think I missed this on main as well.

Moved these two commits into the https://github.com/infinispan/infinispan/pull/10474 PR

authors: tristantarrant wburns

repo: infinispan/infinispan


text:
[14.0.x] ISPN-14008 indexing annotations, query updates

backports #10785
https://issues.redhat.com/browse/ISPN-14008

LGTM. Merged. Thank you!


text:
[9.3.x] ISPN-10029 Invalidation locking is not clustered

Backport of #6887

@danberindei @tristantarrant CI is failing because there is no JDK 10 anymore. ERROR: No tool named JDK 10 found. Do we just build 9.3.x for JDK8? Or Upgrade to 11.

I'll do it the easy way: create a "JDK 10" on Jenkins which points to 11 :)

It's building now

Thanks Tristan!

@tristantarrant just don't let this hack bite you in the ass at some point in the future!

I think the build looks good @tristantarrant

@alanfx well, JDK 10 is EOL anyway :)

Merged, thanks

True enough, @tristantarrant!

authors: alanfx danberindei ryanemerson tristantarrant


text:
ISPN-11889 Remove deprecated parser attributes

~~https://issues.redhat.com/browse/ISPN-11889~~

Updated to remove test XML configurations for versions 7.0-8.5.

After the Zulip discussion, I reverted the attribute removals and I only changed the parser to reject some replication queue attributes that were silently ignored.

LGTM, just restarting the CI build as the last one was interrupted.

Thanks @danberindei

authors: danberindei ryanemerson


text:
_get_unicode with force=True breaks with unicode characters on Python 2.7

On Python 2.7, the _get_unicode function on line_protocol.py breaks if the passed text contains an Unicode code point with a UnicodeEncodeError if force is True.
For example:
Python 2.7.6 (default, Mar 22 2014, 22:59:56)
Type "copyright", "credits" or "license" for more information.

In [1]: from influxdb import line_protocol

In [2]: line_protocol._get_unicode(u'ç')
Out[2]: u'\xe7'

In [3]: line_protocol._get_unicode(u'ç', force=True)
---------------------------------------------------------------------------
UnicodeEncodeError                        Traceback (most recent call last)
<ipython-input-3-fb06071b454e> in <module>()
----> 1 line_protocol._get_unicode(u'ç', force=True)

/<virtualenv>/local/lib/python2.7/site-packages/influxdb/line_protocol.pyc in _get_unicode(data, force)
     75         return ''
     76     elif force:
---> 77         return str(data)
     78     else:
     79         return data

I worked around it by substituting return str(data) with return unicode(data). I can't really say what is the full impact of this change, but this seemed to work so far.
This problem shows up when I try to generate a line when one of its tags has a string with Unicode characters:
  File "<virtualenv>/local/lib/python2.7/site-packages/influxdb/client.py", line 373, in write_points
    tags=tags)
  File "<virtualenv>/local/lib/python2.7/site-packages/influxdb/client.py", line 418, in _write_points
    expected_response_code=204
  File "<virtualenv>/local/lib/python2.7/site-packages/influxdb/client.py", line 258, in write
    data=make_lines(data, precision).encode('utf-8'),
  File "<virtualenv>/local/lib/python2.7/site-packages/influxdb/line_protocol.py", line 108, in make_lines
    value = _escape_tag(tags[tag_key])
  File "<virtualenv>/local/lib/python2.7/site-packages/influxdb/line_protocol.py", line 40, in _escape_tag
    tag = _get_unicode(tag, force=True)
  File "<virtualenv>/local/lib/python2.7/site-packages/influxdb/line_protocol.py", line 77, in _get_unicode
    return str(data)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 9: ordinal not in range(128)

+1

#296

Closed in #296

authors: ArthurPBressan aviau pengyao

repo: influxdata/influxdb-python


text:
Precision option in SeriesHelper options

Unable to set precision when using

SeriesHelper Class

Please help me here, also when I send timestamp in seconds it gets converted to nanoseconds since epoch and getting a date near epoch. If you can help on setting this in Influxdb as default as well it will be helpful
https://stackoverflow.com/questions/46294051/influx-db-precision-setting-at-db-level

#502  I am doing a pull request to solve this issue

Referencing Stackoverflow question for future reference
https://stackoverflow.com/questions/46294051/influx-db-precision-setting-at-db-level

This is closed in #502 and #719


text:
fix(package): make rpm verify pass after installation

This change sets the ownership of directories on package generation with fpm instead that in post-install to make rmp -V pass.
For more details, see: influxdata/EAR#716
Briefly describe your proposed changes:

[ ] CHANGELOG.md updated with a link to the PR (not the Issue)
[ ] Rebased/mergeable
[ ] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)
[ ] Sign CLA (if not already signed)

I think this would need backport.

@affo I don't know enough about this to review it. @mark-rushakoff might have a better insight.

@mark-rushakoff I added the chmod lines and moved user creation to pre-install phase.
I did because of an issue with rpm-attr and non-existing user at installation time (see https://github.com/influxdata/EAR/issues/716#issuecomment-487758645).

authors: affo e-dard

repo: influxdata/influxdb


text:
Add NodeID to execution options

Overview
This pull request changes the ExecutionOptions and SelectOptions to allow a NodeID for specifying an exact node to query against. HTTP support is also added with a node_id field.
/cc @jwilder
TODO

[x] Rebased/mergable
[x] Tests pass
[x] CHANGELOG.md updated

Looks fine to me, but @jwilder should take a look at it too. I would say that I think this is leaking a bit too much of the clustering code into the open source version and we should consider how to make the handler more extensible.

@jsternberg I agree it's leaky but I wasn't sure of a better way to do it. The ShardInfo includes an owner id so I didn't think it was too far off.

👍

authors: benbjohnson jsternberg jwilder


text:
cancel recordings in progress?

Is it possible to stop a batch recording in progress? I looked through the main.go code and it doesn't look like it's an option via the command line/undocumented API.
It would be nice to be able to issue a "cancel recording" command. Sometimes my batch recordings take a really long time and I decide to terminate the recording and start a new, modified one. Instead of just having kapacitor continue to query influx until the recording is finished -- thus wasting valuable computing resources in the meantime -- I'd like to kill the current recording in progress before I start a new, modified one.

@gargooza ATM it is not possible, but Kapacitor does maintain state about which recordings are in progress so it is feasible that this could be added.

authors: gargooza nathanielc

repo: influxdata/kapacitor


text:
Create Top Level Chart

Create a tick chart that includes each member of the stack. Making that configurable will be the challenge.

related/duplicates #10

authors: ivankudibal jackzampolin

repo: influxdata/tick-charts


text:
Double quotes included in tag value :(

Wrote this script. The double quotes in the string "test" are included in the tag value when written to the database.
require 'influxdb'

database = 'mydb'

influxdb = InfluxDB::Client.new database, host: "localhost"

	data = {
		series: 'blueberries',
		tags: {
			station_id: "test"
		},
		values: {
			value: 5
		},
		timestamp: Time.now.to_i
	}

influxdb.write_points([data])

> select * from blueberries where station_id ='test'
> select * from blueberries where station_id ='"test"'
name: blueberries
tags: station_id="test"
time			value
----			-----
2015-07-24T23:36:37Z	5

Love, Regan

Fixed by #98.

authors: rkuchan toddboom

repo: influxdb/influxdb-ruby


text:
Data Race in TSDB

WARNING: DATA RACE
Write by goroutine 1564:
  runtime.mapassign1()
      /usr/local/Cellar/go/1.5.1/libexec/src/runtime/hashmap.go:411 +0x0
  github.com/influxdb/influxdb/tsdb.(*Shard).createFieldsAndMeasurements()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/tsdb/shard.go:378 +0x6df
  github.com/influxdb/influxdb/tsdb.(*Shard).WritePoints()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/tsdb/shard.go:230 +0x640
  github.com/influxdb/influxdb/tsdb.(*Store).WriteToShard()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/tsdb/store.go:398 +0x1e6
  github.com/influxdb/influxdb/cluster.(*Service).processWriteShardRequest()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/cluster/service.go:214 +0x861
  github.com/influxdb/influxdb/cluster.(*Service).handleConn()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/cluster/service.go:162 +0x5a3
  github.com/influxdb/influxdb/cluster.(*Service).serve.func1()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/cluster/service.go:112 +0x7b

Previous read by goroutine 1286:
  runtime.mapiterinit()
      /usr/local/Cellar/go/1.5.1/libexec/src/runtime/hashmap.go:559 +0x0
  github.com/influxdb/influxdb/tsdb.(*Measurement).FieldNames()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/tsdb/meta.go:1491 +0x106
  github.com/influxdb/influxdb/tsdb.(*DatabaseIndex).ExpandWildcards()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/tsdb/meta.go:350 +0x2f5
  github.com/influxdb/influxdb/tsdb.(*DatabaseIndex).RewriteSelectStatement()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/tsdb/meta.go:309 +0x14a
  github.com/influxdb/influxdb/tsdb.(*RawMapper).Open()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/tsdb/raw.go:809 +0xd6
  github.com/influxdb/influxdb/tsdb.(*RawExecutor).execute()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/tsdb/raw.go:69 +0x141

Goroutine 1564 (running) created at:
  github.com/influxdb/influxdb/cluster.(*Service).serve()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/cluster/service.go:113 +0x454

Goroutine 1286 (running) created at:
  github.com/influxdb/influxdb/tsdb.(*RawExecutor).Execute()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/tsdb/raw.go:59 +0x74
  github.com/influxdb/influxdb/tsdb.(*QueryExecutor).executeStatement()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/tsdb/query_executor.go:707 +0x104
  github.com/influxdb/influxdb/tsdb.(*QueryExecutor).ExecuteQuery.func1()
      /Users/corylanou/go/src/github.com/influxdb/influxdb/tsdb/query_executor.go:173 +0xbde

This line ... https://github.com/influxdb/influxdb/blob/master/tsdb/shard.go#L378
Should be calling https://github.com/influxdb/influxdb/blob/master/tsdb/meta.go#L1480

authors: corylanou dgnorton

repo: influxdb/influxdb


text:
Move VersionCommand back to influxd

Overview
This commit moves the command in cmd/influxd/version into the cmd/influxd package so that the version and commit can be injected via -ldflags.

:+1:

authors: benbjohnson toddboom


text:
Control whether each query should be logged

Fixes issue #4138

:+1:

authors: jwilder otoolep


text:
Rezolvarile mele

Probleme rezolvate:

[x] Caesar
[x] ICAO
[x] Unic
[x] Cursor
[x] Fill shape
[x] Paranteze
[x] Tree
[ ] Syncronize

Istoricul pull request-ului tău conține elemenete ce nu sunt relevante.
Propunerea mea ar fi să unești următoarele commit-uri:

https://github.com/alexandrucoman/labs/pull/158/commits/ec7295befd3863c0739e5092f84bb0b82e48813a

https://github.com/alexandrucoman/labs/pull/158/commits/7496ac93cbe3f950a7de5011d206cda483b4c610

https://github.com/alexandrucoman/labs/pull/158/commits/71b0cb6a206c86a7c82c43150443c97a9c8bf304

https://github.com/alexandrucoman/labs/pull/158/commits/6804125a320bb1b26f4649bd602888a4ef6e120a

https://github.com/alexandrucoman/labs/pull/158/commits/ee97d9e017f3d9d793aae401857c3711c2ff0ad5

https://github.com/alexandrucoman/labs/pull/158/commits/d71542e9accc54f3124ab4fcc29e49056f9eb571

https://github.com/alexandrucoman/labs/pull/158/commits/9f8f1d5461bcb15955dd1e265cfe4af313d984f1

https://github.com/alexandrucoman/labs/pull/158/commits/ad846e0091fd3508dd6626dab27c28c3835b4e7e

Pull request-ul tău conține și 5 commit-uri ce nu sunt ale tale.
După ce rezolvi și această problemă pull request-ul este gata pentru merge.

authors: MonicaMaria alexandrucoman

repo: info-uaic/labs


text:
How to generate the mobilenet.mlmodel file?

Thank you for this awesome project!
When I compile the project, I got this error:
coremlc: Error: unable to read document: /Users/qyvideo/work/deep_learning/SwiftOpenPose/SwiftOpenPose/Resources/mobilenet.mlmodel
detail: validator error: unable to open file for read
and how to generate this file? Is it in this section:
OpenPose Keras Mobilenet-Model
Result: However it did not work.

Thank you for trying.
You need to create a model converted from Caffe-Model to MLModel with reference to the next section.
https://github.com/infocom-tpo/SwiftOpenPose#the-following-is-how-to-execute-this-project
Apart from that, I can try out a model trained with the high speed mobilenet layer that we will release today.
https://s3-ap-northeast-1.amazonaws.com/swiftopenpose/MobileOpenPose.mlmodel
thank.

Cool!

repo: infocom-tpo/SwiftOpenPose


text:
Refactor tx raw commands

Closes: #2315, closes: #2376
Description
This PR refactors the tx raw commands in order to be synchronised with the ADR 010. The following modifications are applied:

Remove the raw subcommand from all the tx raw commands
Remove the four duplicate commands:

tx raw update-client, which is the same as update client
tx raw upgrade-client, which is the same as upgrade client
tx raw upgrade-clients, which is the same as upgrade clients
tx raw create-client, which is the same as create client

Replace all flag prefixes --src- and --dst- with more appropriate prefixes
Add unit tests for all tx raw commands

PR author checklist:

[x] Added changelog entry, using unclog.
[x] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[x] Linked to GitHub issue.
[x] Updated code comments and documentation (e.g., guide/).

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

I know this is merged but I am not sure about some of these changes.
I find it confusing, especially for handshake Tx-es, where we now use a-chain and b-chain but then in the help strings to make things clear we still use source and destination. For packets seems a bit better but again we use source and destination in the help to explain things.
The general idea for tx (raw) commands is that, regardless of the type of action (relay packet, client or handshake message), you instruct the relayer to send one or more messages to a (destination) chain by retrieving state values and proofs from another (source) chain. So I find using src/ dst more clear here. Or chain/ counterparty.
a-chain and b-chain work fine in the create connection/ channel where you just want to say "create a connection/channel" between chains a and b. And it results in sending Tx-es to both a and b.
I also find it confusing the sender/ receiver in tx upgrade-chain. We use host/ reference in the high level upgrade. We should use the same here.
Nit: there is stil tx raw packet-recv in the ADR.

Is it a reasonable compromise if we make the explicit relation between a-chain being a destination always (wherever applicable) and b-chain being the source? I think this might be the case already.

Is it a reasonable compromise if we make the explicit relation between a-chain being a destination always (wherever applicable) and b-chain being the source? I think this might be the case already, we would just document it as such throughout help and guide.

Not sure what you mean by "make an explicit relation". And btw, a-chain is the source/ counterparty chain (i just looked at all tx CLIs, at least we are consistent).
IMO we should fix this and not use a-chain and b-chain in the tx(raw) and fix the upgrade params names also.

I propose we use chain/ counterparty instead of b-chain/ a-chain. Except the chain upgrade where we can use host-chain/ reference-chain (with the note that the reference-chain is the chain to be upgraded)

I propose we use chain/ counterparty instead of b-chain/ a-chain
Just to be clear, are you proposing we remove all a-chain/b-chain language entirely from the CLI?

Just to be clear, are you proposing we remove all a-chain/b-chain language entirely from the CLI?

Only from the tx CLIs (old tx raw-s)

As I see the process for the commands syntaxe, it usually has two steps:

One issue/PR to create/update an ADR which generates a discussion up to some mutual agreement
One issue/PR to update the commands in order to match the ADR

So I think this should be discussed in the issue regarding updating ADR 010 https://github.com/informalsystems/ibc-rs/issues/2383 or in a new issue. This would avoid having a mismatch between ADR 010 and the commands, as well as making it easier to track the discussion which lead to the chosen syntaxe.
What do you think ?

I opened #2410 to capture @ancazamfir's request 🙂

repo: informalsystems/ibc-rs


text:
docs: Apply suggestions from #1212 code review

Follows from #1212.

[x] Referenced an issue explaining the need for the change
[x] Updated all relevant documentation in docs
[ ] Updated all code comments where relevant
[ ] Wrote tests
[ ] Added entry in .changelog/

Codecov Report

Merging #1215 (cc20ca9) into main (e830f85) will decrease coverage by 0.0%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            main   #1215     +/-   ##
=======================================
- Coverage   63.9%   63.9%   -0.1%
=======================================
  Files        253     253
  Lines      21636   21636
=======================================
- Hits       13844   13838      -6
- Misses      7792    7798      +6

Impacted Files
Coverage Δ

proto/src/serializers/bytes.rs
51.6% <ø> (ø)

testgen/src/vote.rs
84.0% <0.0%> (-1.7%)
:arrow_down:

testgen/src/header.rs
82.9% <0.0%> (-1.2%)
:arrow_down:

testgen/src/validator.rs
86.7% <0.0%> (-0.8%)
:arrow_down:

light-client-verifier/src/types.rs
38.1% <0.0%> (-0.6%)
:arrow_down:

tendermint/src/node.rs
63.9% <0.0%> (ø)

config/src/config.rs
54.9% <0.0%> (+0.1%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: codecov-commenter thanethomson

repo: informalsystems/tendermint-rs


text:
Add Visible Columns Annotation

Add visible columns annotation to schemas that has been used for test cases, to avoid usage of heuristics.

I talked to @RFSH about this PR today, he said it's okay to merge once updating it with master. It only changes test schemas for a change to ermrestJS. This PR is being merged first because it's compatible with ermrestJS both before and after that PR is merged.

authors: RFSH jrchudy

repo: informatics-isi-edu/chaise


text:
Updates stf-run-ci setup playbook to use cert-manager in stable-v1

For newer OCP versions (OCP >= 4.12), cert-manager should be consumed from the stable-v1 channel. This differs from previous versions of OCP, in which we were consuming cert-manager from the tech-preview channel.
The way of installing both operators is different (the tech-preview requires a specific namespace and operator group, whereas the stable-v1 version does not).
This change adds a conditional block checking the versions of OCP in which we are running this playbook and executing the installation steps that correspond which each version.

Ran smoke tests on an environment with cert-manager from stable-v1 installed in the way that it is being installed in this patch set to verify sanity of the deployment, it is passing.
Some validation of the creation of the subscription should be added, is https://github.com/infrawatch/service-telemetry-operator/blob/master/build/validate_deployment.sh a good place for this? cc @csibbitt @leifmadsen @elfiesmelfie

Ran smoke tests on an environment with cert-manager from stable-v1 installed in the way that it is being installed in this patch set to verify sanity of the deployment, it is passing.

:+1:

Some validation of the creation of the subscription should be added, is https://github.com/infrawatch/service-telemetry-operator/blob/master/build/validate_deployment.sh a good place for this? cc @csibbitt @leifmadsen @elfiesmelfie

I think if the cert-manager doesn't work, then validate_deployment.sh will fail while waiting for the QDR to deploy.

test

There was some side discussion that we may want to pin testing to the tech-preview channel in all cases where it's available, since that's what we'd expect people to be using if they installed following the docs. If that's the case then we might want to keep this structure and just adjust the versions?

Considering we will stick to tech-preview for STF up to 1.5.2 we should

Drop this change, since we still have cert-manager from tech-preview channel available in OCP 4.12
Revert https://github.com/infrawatch/service-telemetry-operator/pull/424

For OCP 4.13 we will add dependency resolution and customers are no longer expected to pre-install cert-manager. We will need to reflect those changes in our CI. For that case, the steps followed will look like

Create namespace
Create operatorgroup
Create subscription to STO
Verify all dependencies are installed (SGO, cert-manager, AMQ Interconnect, OBO)

Related PR https://github.com/infrawatch/service-telemetry-operator/pull/444
Will close this PR once we agreed on the approach

authors: csibbitt vkmc

repo: infrawatch/service-telemetry-operator


text:
Windows: Service intermittently stops

We've had 3 occurrences over the last 6 months where the service stops by itself, there are currently no logs to indicate what the cause is other than in the system event log:
The monitoring-agent service terminated unexpectedly. It has done this 3 time(s).

Release https://github.com/infraweavers/monitoring-agent/releases/tag/0.1.792 adds extra stderr logging to investigate this

Just occurred, output.log.stdout is empty, normal output.log contains as the last thing:
ma 2022/08/05 09:45:18 WARNING : Request Timed Out. Timeout: '10s'; Command: 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe'; Arguments: []string{"-command", "-"}

The https://github.com/infraweavers/monitoring-agent/blob/master/main.go#L107 log isn't logged; so whatever process termination is occurring, isn't "just main ending".

Just occurred on Debian 9 as well when the box was under significant IO pressure. I'm pretty sure this is the same problem as a few of the instances where we have seen this occur are when disks have failed in RAID arrays etc causing IO stalls.
$:/var/log/monitoring-agent$ cat monitoring-agent.log.stdout
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x4d2db9]

goroutine 2691924 [running]:
os.(*Process).signal(0x0, {0x8d18a0, 0xb16600})
        /opt/hostedtoolcache/go/1.17.12/x64/src/os/exec_unix.go:64 +0x39
os.(*Process).Signal(...)
        /opt/hostedtoolcache/go/1.17.12/x64/src/os/exec.go:138
os.(*Process).kill(...)
        /opt/hostedtoolcache/go/1.17.12/x64/src/os/exec_posix.go:68
os.(*Process).Kill(...)
        /opt/hostedtoolcache/go/1.17.12/x64/src/os/exec.go:123
monitoringagent/internal/web.runScriptWithStdIn.func1()
        /home/runner/work/monitoring-agent/monitoring-agent/go/src/monitoring-agent/internal/web/helpers.go:163 +0x5f
created by time.goFunc
        /opt/hostedtoolcache/go/1.17.12/x64/src/time/sleep.go:180 +0x31

Fixed in: https://github.com/infraweavers/monitoring-agent/pull/22

Fixed in release 0.1.800

repo: infraweavers/monitoring-agent


text:
Folder level permission check in Ranger

changes bucket path naming to hdfs style with fqn (starting with / etc.)
Adds option to check full s3 path in Ranger

Codecov Report

Merging #22 into master will decrease coverage by 0.47%.
The diff coverage is 76.47%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
- Coverage   86.16%   85.68%   -0.48%
==========================================
  Files          29       29
  Lines         571      580       +9
  Branches       51       56       +5
==========================================
+ Hits          492      497       +5
- Misses         79       83       +4

Impacted Files
Coverage Δ

...k/proxy/provider/AuthorizationProviderRanger.scala
100% <100%> (ø)
:arrow_up:

...la/com/ing/wbaa/airlock/proxy/data/S3Request.scala
100% <100%> (ø)
:arrow_up:

.../airlock/proxy/api/directive/ProxyDirectives.scala
86.79% <42.85%> (-6.83%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: arempter codecov-io

repo: ing-bank/airlock


text:
Updating worker environment does not work in 1.3.4 and greater

I have a worker environment which I cannot update with versions 1.3.4, 1.3.5, and 1.4.0. The specific issue is that the plugin fails to find the environment. The environment is present and the status is Green.
I tried in version 1.3.3 and I am able to update.

oops. can you send me in private your pom so I could look into it?
Sent from my Windows Phone
-----Original Message-----
From: "David Venable" notifications@github.com
Sent: 2/28/2015 5:07 PM
To: "ingenieux/beanstalker" beanstalker@noreply.github.com
Subject: [beanstalker] Updating worker environment does not work in 1.3.4 andgreater (#58)
I have a worker environment which I cannot update with versions 1.3.4, 1.3.5, and 1.4.0. The specific issue is that the plugin fails to find the environment. The environment is present and the status is Green.
I tried in version 1.3.3 and I am able to update.
—
Reply to this email directly or view it on GitHub.

Our POM is fairly complicated because it uses a parent-child hierarchy. I'll see if I can break down the properties for you.
One important thing to note - running the beanstalk:wait-for-environment Maven goal succeeds just fine in version 1.3.5. There must be something different in how the two wait commands are setup.

mvn help:effective-pom
--
-- Aldrin Leal, aldrin@leal.eng.br
Master your EC2-fu! Get the latest ekaterminal public beta
http://www.ingenieux.com.br/products/ekaterminal/
On Sat, Feb 28, 2015 at 8:19 PM, David Venable notifications@github.com
wrote:

Our POM is fairly complicated because it uses a parent-child hierarchy.
I'll see if I can break down the properties for you.
One important thing to note - running the beanstalk:wait-for-environment
Maven goal succeeds just fine in version 1.3.5. There must be something
different in how the two wait commands are setup.
—
Reply to this email directly or view it on GitHub
https://github.com/ingenieux/beanstalker/issues/58#issuecomment-76562488
.

Hello @aldrinleal, I sent you an email at the email address listed in your Git commits for this project.

hello @aldrinleal, I have the same issue and not sure if I put a proper configuration in POM. Could you, please, refer to working example or some docs describing configuration for the Worker tier.
thanks in advance!

mkalinin has also submitted a PR: https://github.com/ingenieux/beanstalker/pull/68 which should address this issue. Is there any chance of it being merged in the next few days/weeks?

@dlvenable, can you see if the current snapshot (with the @mkalinin patch) appears to solve your problem?
@scatat, please way, things are a bit slower here :)

@mkalinin, there was an archetype example in the service webapp, but I think you saw it.
@dlvenable, I created an example at github.com/aldrinleal/example-awseb-worker.
First, I deployed it with mvn -Pawseb deploy
It had an issue, which was good. Fixed it, then ran the same command again but with wait-for-environment:
$ mvn -Pawseb clean deploy beanstalk:wait-for-environment
...
[INFO] Artifact Uploaded
[INFO] SUCCESS
[INFO] null
[INFO]
[INFO] --- beanstalk-maven-plugin:1.4.1-SNAPSHOT:create-application-version (deploy) @ example-worker-app ---
[INFO] SUCCESS
[INFO] {
[INFO]   "applicationName" : "example-worker-app",
[INFO]   "description" : "Update from beanstalk-maven-plugin",
[INFO]   "versionLabel" : "20150918015711",
[INFO]   "sourceBundle" : {
[INFO]     "s3Bucket" : "elasticbeanstalk-us-east-1-235368163414",
[INFO]     "s3Key" : "apps/example-worker-app/example-worker-app-20150918015711.zip"
[INFO]   },
[INFO]   "dateCreated" : 1442541562432,
[INFO]   "dateUpdated" : 1442541562432
[INFO] }
[INFO]
[INFO] --- beanstalk-maven-plugin:1.4.1-SNAPSHOT:put-environment (deploy) @ example-worker-app ---
[INFO] ... with environmentName matching re '\Qexample-worker-app\E'
[INFO] ... with status *NOT* set to 'Terminated'
[INFO] Calling update-environment, and using versionLabel: 20150918015711
[INFO] SUCCESS
[INFO] {
[INFO]   "environmentName" : "example-worker-app",
[INFO]   "environmentId" : "e-9ssmpvubdf",
[INFO]   "applicationName" : "example-worker-app",
[INFO]   "versionLabel" : "20150918015711",
[INFO]   "solutionStackName" : "64bit Amazon Linux 2015.03 v2.0.0 running Docker 1.6.2",
[INFO]   "description" : "example-worker-app",
[INFO]   "dateCreated" : 1442539729398,
[INFO]   "dateUpdated" : 1442541563466,
[INFO]   "status" : "Updating",
[INFO]   "health" : "Grey",
[INFO]   "tier" : {
[INFO]     "name" : "Worker",
[INFO]     "type" : "SQS/HTTP",
[INFO]     "version" : "1.0"
[INFO]   }
[INFO] }
[INFO]
[INFO] --- beanstalk-maven-plugin:1.4.1-SNAPSHOT:wait-for-environment (default-cli) @ example-worker-app ---
[INFO] Environment Lookup
[INFO] ... with environmentName matching re '\Qexample-worker-app\E'
[INFO] ... with status   set to 'Ready'
[INFO] ... with health equal to 'Green'
[INFO] SUCCESS
[INFO] {
[INFO]   "environmentName" : "example-worker-app",
[INFO]   "environmentId" : "e-9ssmpvubdf",
[INFO]   "applicationName" : "example-worker-app",
[INFO]   "versionLabel" : "20150918015711",
[INFO]   "solutionStackName" : "64bit Amazon Linux 2015.03 v2.0.0 running Docker 1.6.2",
[INFO]   "description" : "example-worker-app",
[INFO]   "dateCreated" : 1442539729398,
[INFO]   "dateUpdated" : 1442541701508,
[INFO]   "status" : "Ready",
[INFO]   "health" : "Green",
[INFO]   "tier" : {
[INFO]     "name" : "Worker",
[INFO]     "type" : "SQS/HTTP",
[INFO]     "version" : "1.0"
[INFO]   }
[INFO] }
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:49 min
[INFO] Finished at: 2015-09-17T23:02:00-03:00
[INFO] Final Memory: 33M/126M
[INFO] ------------------------------------------------------------------------

...and it worked. I suggest you start by reviewing beanstalk.environmentRef values and paste the lookup prefix (the lines like the ones below) so we can validate it together:
[INFO] Environment Lookup
[INFO] ... with environmentId equal to 'e-9ssmpvubdf'
[INFO] ... with status   set to 'Ready'
[INFO] ... with health equal to 'Green'

Thank you

@aldrinleal, it appears that the latest source code does not find the existing environment. The environment does exist and is in the Green state.
[INFO] ... with environmentName matching re '\Qweb-worker-TEST\E'
[INFO] ... with status *NOT* set to 'Terminated'
[INFO] Environment Lookup
[INFO] ... with environmentName matching re '\Qweb-worker-TEST\E'
[INFO] ... with status *NOT* set to 'Updating'
[WARNING] FAILURE
org.apache.maven.plugin.MojoExecutionException: Timed out
	at br.com.ingenieux.mojo.beanstalk.cmd.env.waitfor.WaitForEnvironmentCommand.executeInternal(WaitForEnvironmentCommand.java:271)
	at br.com.ingenieux.mojo.beanstalk.cmd.env.waitfor.WaitForEnvironmentCommand.executeInternal(WaitForEnvironmentCommand.java:46)
	at br.com.ingenieux.mojo.beanstalk.cmd.BaseCommand.execute(BaseCommand.java:73)
	at br.com.ingenieux.mojo.beanstalk.AbstractNeedsEnvironmentMojo.waitForNotUpdating(AbstractNeedsEnvironmentMojo.java:490)
	at br.com.ingenieux.mojo.beanstalk.env.UpdateEnvironmentMojo.executeInternal(UpdateEnvironmentMojo.java:211)
	at br.com.ingenieux.mojo.aws.AbstractAWSMojo.execute(AbstractAWSMojo.java:386)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:140)

$ mvn beanstalk:describe-environments. Can you paste its output?

[INFO] --- beanstalk-maven-plugin:1.4.1-SNAPSHOT:describe-environments (default-cli) @ web-worker ---
[INFO] SUCCESS
[INFO] {
[INFO]   "environments" : [ {
[INFO]     "environmentName" : "web-worker-TEST",
[INFO]     "environmentId" : "e-spqiyyjjey",
[INFO]     "applicationName" : "testing-web-worker",
[INFO]     "versionLabel" : "Web Worker 1.0.11",
[INFO]     "solutionStackName" : "64bit Amazon Linux 2014.09 v1.2.0 running Tomcat 7 Java 7",
[INFO]     "description" : "Web Worker",
[INFO]     "dateCreated" : 1443620644771,
[INFO]     "dateUpdated" : 1443623797400,
[INFO]     "status" : "Ready",
[INFO]     "abortableOperationInProgress" : false,
[INFO]     "health" : "Red",
[INFO]     "tier" : {
[INFO]       "name" : "Worker",
[INFO]       "type" : "SQS/HTTP",
[INFO]       "version" : "1.0"
[INFO]     }
[INFO]     }
[INFO]   } ]
[INFO] }

The health is Red now because I made some changes. But, it was Green when I ran the first update-environment command.

I just re-tried update-environment, while the state was Red and it worked.
[INFO] ... with environmentName matching re '\Qweb-worker-TEST\E'
[INFO] ... with status *NOT* set to 'Terminated'
[INFO] Environment Lookup
[INFO] ... with environmentName matching re '\Qweb-worker-TEST\E'
[INFO] ... with status *NOT* set to 'Updating'
[INFO] Calling update-environment, and using versionLabel: this Web Worker 1.0.13
[INFO] SUCCESS
[INFO] {
[INFO]   "environmentName" : "web-worker-TEST",
[INFO]   "environmentId" : "e-spqiyyjjey",
[INFO]   "applicationName" : "testing-web-worker",
[INFO]   "versionLabel" : "Web Worker 1.0.13",
[INFO]   "solutionStackName" : "64bit Amazon Linux 2014.09 v1.2.0 running Tomcat 7 Java 7",
[INFO]   "description" : "Web Worker",
[INFO]   "dateCreated" : 1443620644771,
[INFO]   "dateUpdated" : 1443629580842,
[INFO]   "status" : "Updating",
[INFO]   "abortableOperationInProgress" : true,
[INFO]   "health" : "Grey",
[INFO]   "tier" : {
[INFO]     "name" : "Worker",
[INFO]     "type" : "SQS/HTTP",
[INFO]     "version" : "1.0"
[INFO]   }
[INFO] }
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

this is closed, but doesn't indicate the solution.

@bpappin, can you show your maven output and beanstalk.* settings please?
Thank you

authors: aldrinleal bpappin dlvenable mkalinin scatat

repo: ingenieux/beanstalker


text:
Sequence diagram overlap when print

i try to using sequence diagram but the printed page is overlap
it's expected or not ?

I can't see the image

Next version will fix this problem. Thanks!

Inkdrop v3.4.0 is out.
Please update the app and update plugins by ipm update.

authors: craftzdog zainul

repo: inkdropapp/inkdrop-export-print


text:
Update gcm3

Update to new GCM using Play Services 7.5.
Fix #36 #34 #33 #32

I will take a look at this. Adding also @destil to this PR.

Back to you, @peterbartos .

Isn't the google-services.json file with configuration required? Even if it's not, I think it's a nice way how to configure Google APIs. Nothing in resources (config.xml), just one json in the app. And I imagine that the app will need multiple Google APIs, then the app needs just one json for all APIs (login, Drive, GCM, ...) and it will just work.

+1 on the json configuration files. To keep backwards compatibility we can check if easygcm_sender_id string and only use it in that case. Otherwise the json file will be used. The developers will be instructed by the README to put apply plugin: 'com.google.gms.google-services into their build.gradle files.

I am OK with this.
The AsyncTask can be converted to an wakeful IntentService in a separate pull request.
@destil do you see any more issues here? Thanks.

Thank you destil for the good review. Good idea with adding the string only as a value without using the plugin. Update soon...

Code-review +2, Looks good to me

Okay, this is ready to merge @peterbartos .

authors: DanielNovak destil peterbartos

repo: inloop/easygcm


text:
Bump setuptools from 67.3.1 to 67.3.2 (#5574)

Pull request opened by the merge tool on behalf of #5574

Merged in 968892ecd6b02f15cf69cb66b05cba5e2b1557a1

repo: inmanta/inmanta-core


text:
Fix bug in notify_compile_request_committed method (#5962)

Pull request opened by the merge tool on behalf of #5962

Merged into branches iso6 in 1ded98b2f04c24ff2d95098702364b8120a9b672


text:
updating the test functions :

updating test_calibration_output, as the artifact correction is now the first correction to be applied in l1a to l1b processing, changing the output order for L1_calibrate.
adding test for artifact correction in the test_calibration_output function
removing test for flatfield correction

Also I couldn't get the photometer test working, but it seems to be an issue on the testdata folder that is not updated on box rather than in the test file

Also I couldn't get the photometer test working, but it seems to be an issue on the testdata folder that is not updated on box rather than in the test file

Ok I will have a look at this and fix it (before we merge this thing in)

OK, I will try to see if I can get the flatfield working today.


text:
feat:admin #34 admin_공통 ui components 개발

개요
#34 admin_공통 ui components 개발
작업 사항

[x]  메뉴 버튼(회원관리, 게시물 관리 등)
[x]  기본 버튼(회원생성, 엑셀 익스포트)
[x]  리스트 전체 컴포넌트
[x]  리스트 개별 컴포넌트

변경점
목적
스크린샷 (optional)

ListCard.tsx 에서 props.userInfo 가 반복되는데 const { name, id, auth, group, createdAt, lastLogin } = props.userInfo 로 구조분해해주는게 어떨까요??
아마 아시는데 안하신 다른 이유가 있겠지만요!
Menu.tsx 에서 < li >의 key값이 menuLists.map 에는 없고 subMenuLists.map에는 넣어주신 이유가 궁금합니당

제가 타입스크립트로 작업을 안해봐서 구조분해로 넣으려면 props타입 지정을 따로 해줘야 되나? 의문이 들었는데 일단 시간이 없어서 그냥 props로 받았습니다!
Menulist key는 제가 놓친거구요 (왠지..콘솔에 빨간게 가득하더라니....) 수정해야할 거 같아요!

repo: innovationacademy-kr/slabs-munetic