text:
[Bug]: Error with composite emojis

OS

[X] Windows
[ ] macOS
[ ] Linux

PSVersionTable
Name                           Value
----                           -----
PSVersion                      7.4.5
PSEdition                      Core
GitCommitId                    7.4.5
OS                             Microsoft Windows 10.0.26100
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

What happened?
I am using this emoji I grabbed from the Windows emoji picker: 🧑🏻💻
But it looks like this is a combination of  🧑🏻💻 Because that is what I see when I run PowerShellRun.

Does your terminal render 🧑🏻💻 correctly? I remember Windows Terminal could not render some emojis.

Interesting. It renders in some terminals but not all. But even in the console where I can paste the emoji, PowerShell Run still is problematic.

You can see 3 or 4 spaces after the pasted emoji. That is stil not rendering it correctly. Even if I can fix the issue that is splitting it into 2 emojis, it will still break the layout.
I can only say for now please avoid using those emojis. There is a section about the limitations. I'll add some more explanations there.

I recall now the known limitation. And I've accepted rendering problems. I often have to insert a space into the name to align things. I think some emojis simply have a little more white space than others.

It turned out Windows Terminal was able to render the emoji correctly and the issue was caused by PowerShellRun. I'm working on this.

The issue has been fixed. From the next release, you can use more emojis without breaking the rendering.

authors: jdhitsolutions mdgrs-mei

repo: mdgrs-mei/PowerShellRun


text:
[REQ] Simultanious Post Processing

This is an extra request that could serve as alternative to the thread option, as multi threaded ffmpeg is slower then running 3-4 instances on 1 core.
Could u make it run the processing on background ?
So sab thinks post processing is done and starts with the next one, while after the processing is done the script still pings couchpotato/nzbdrone/sickbeard so they get moved automatically.
The point of this is when you are downloading with 20MB/s + the post processing queue gets huge and this could greatly speed up the efficiency.
The script would have to queue up to 4 ( or changable  number ) conversions, but once 4 are already running make it wait.
So < 4, Post process on background else wait ...
Well I can imagine this might be hard to implement or not something u want to add, in that case would it be possible to get a custom script for some kind of donation?

I've been thinking on this myself. I actually I'd prefer not to do this, but rather have the script pass a 0 if the conversion was completed correctly. Logs would be good. There are many concurrency programs that can spawn jobs to run this script. If I have time I will try an write up something.

This isn't so much an issue with my script as it is a limitation of the way
SAB handles its processing. There's nothing stopping you from creating
multiple simultaneous instances of the script using, for example, manual.py.
Check here for possible solutions:
https://www.sabnzbd.org/viewtopic.php?f=2&t=4365
On Tue, Jan 6, 2015 at 2:59 AM, cod3fr3ak notifications@github.com wrote:

I've been thinking on this myself. I actually I'd prefer not to do this,
but rather have the script pass a 0 if the conversion was completed
correctly. Logs would be good. There are many concurrency programs that can
spawn jobs to run this script. If I have time I will try an write up
something.
—
Reply to this email directly or view it on GitHub
https://github.com/mdhiggins/sickbeard_mp4_automator/issues/116#issuecomment-68836497
.

source: gharchive/issue

authors: Mirabis cod3fr3ak mdhiggins

license: MIT

license_type: permissive

license_source: github-api


text:
unclear instructions: https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Source_Code/Mercurial/Bundles

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details

It reads

"To use the below command in Windows, export the \path\to\hg and invoke the command from command prompt."

in the article, where it's unclear to users how they "export the \path\to\hg" and how they "invoke" the command. Please add a better understandable instruction.

Thanks for your issue. This doc set isn't maintained and will be archived soon. Closing this issue.
You might want to checkout new docs at https://firefox-source-docs.mozilla.org/

repo: mdn/sprints


text:
Adding to glossary

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[x] New documentation
[ ] Correction or update

Details

Hello. I would like to add a few entries to the Glossary. I was working on MDN from November for my university module, editing and translating some documents. My deadline for submission is December 5th and I would like to add at least one entry to glossary. If you will allow me to do this and give me the permission either today or tomorrow, can I add such definitions as "Agile" and "Bootstrap" to the glossary? If you will still grant me the permission, but on the 3rd of December, please allow me to add only "Agile". No later permission is required.
I also tried to open the admin contact form for this question, but I couldn't setup Outlook from uni computers, so I hope it is alright that I am writing here about this.
Thank you.

Sorry, emailed admins directly.


text:
Fix https proxy

Fix https proxy

WFM and LGTM

source: gharchive/pull-request

authors: austek rlichszteld-mdsol

repo: mdsol/mauth-java-client

license: mit

license_source: bigquery


text:
atualização Planejamento Fases em Visão Geral do Projeto

No último feedback o professor informou que deveríamos fazer algumas modificações nessa parte, principalmente no que tange o RAD, portanto, as iterações.
Atividades:

[x] Inserir texto de introdução para iniciar essa parte tentando levar em considerações a forma como o RAD divide as atividades (contextualizar)
[x] Adaptar o que está dividido em formato de sprints para o formato de Iterações
[x] Retirar coisas que são relativas a disciplina de fato (feedback dado em sala de aula pelo professor)
[x] Alterar datas (por exemplo: data do fim do projeto conforme comentado pelo professor em sala de aula..)
[x] Verificar o KANBAM e inserir lá as atividades que você acredita estarem faltando (pode adicionar mais iterações caso seja necessário)
[x] Fazer as alterações na tabela atual para que ela de certa forma siga o padrão do kanbam (artefatos precisam conversar entre si)

OBS1 : Para atualizar essa parte das US é preciso que a #18 esteja pronta, mas e quando você for fazer não tiver o número das issues certinhas ainda aqui no pages, mas tenta só manter o número das US que não alteraram e das novas só colocar uns números pra quantidade total que estiver faltando
OBS2: Link do KANBAM -> https://miro.com/app/board/uXjVNOv3H60=/

Feito!

authors: CarolCoCe suzaneduarte


text:
Rest of bug and bad behavior in release 3.0 of medInria

[ ] CRASHING BUG, when you open an image via the command line like "--view toto.nii.gz", on Windows and Linux not on OSX.
[ ] Into tab with multiple views, when you close some view you can have a bad behavior of resizing for keeped views.

split into #413 and #414

repo: medInria/medInria-public


text:
when is the new release due?

Hi,
It seems the last release of this package was 8 months ago? Is there a planned date for new release as it seems there has been few fixed in past 8 months?
Thanks!

https://github.com/media-kit/media-kit/pull/845 but you can use github version
dependency_overrides:
  media_kit:
    git:
      url: https://github.com/media-kit/media-kit
      path: media_kit
  media_kit_video:
    git:
      url: https://github.com/media-kit/media-kit
      path: media_kit_video
  media_kit_libs_video:
    git:
      url: https://github.com/media-kit/media-kit
      path: libs/universal/media_kit_libs_video

@abdelaziz-mahdy How are things going with the support of the package itself? As far as I understand, @alexmercerind is a bit busy with something else, since there have been no commits from him lately.
I find this package to be cutting edge in this area for flutter, would like to know what its status is for maintainers.

Well I don't understand the internals the same as other maintainers, so I mostly do bug fixes on flutter and dart issues that I am able to understand, and answer issues that I know the fix for
I don't know the situation for the other maintainers sadly , for the release once the mentioned pr merged we may release the version in it,
Note currently most of the problems crashes on windows due to some changes from windows itself, and Linux is from flutter 3.22
I don't see any critical problem other than those but I sadly don't have the knowledge to fix them

@abdelaziz-mahdy Ok, thanks for your work.
@alexmercerind @birros If you have any information please let us know.

@alexmercerind
Sorry to bother you, but is it possible to release a new version of media_kit? The version currently published on pub.dev is outdated. In fact, it can't even be built correctly with the latest version of the MSVC toolchain (#892). This is preventing many users from using the media_kit library. media_kit is currently the best multimedia library for Flutter, and we all hope this excellent library can continue to thrive.

authors: Predidit StarProxima abdelaziz-mahdy dkliss

repo: media-kit/media-kit


text:
Detect when seek has been called by user interaction

This is the same goal as this PR but for the seek event.
Added one new property to MediaElementPlayer (with docs):
seekUserInteraction: Returns whether the last seek call was initiated from user interaction

Thanks for the pull request. Making a new version soon.

I merged this pr into master, by creating a branch and fixing the conflict there: https://github.com/mediaelement/mediaelement/commit/439efbfbb887bfa8bef1883ccc1c4ef4ad0d55a2

authors: TronchDeYack dpxgit

repo: mediaelement/mediaelement


text:
Adding a default template label

ECOPROJECT-1759
ATM The UI is looking for SNR Template with the default remediation strategy completely hard coded (i.e hard coded for ResourceDeletion).
In order to make the UI more robust and prevent unnecessary changes in the UI when the default Strategy is changed, we'd put a label on the Template with the default strategy instead.

/lgtm

authors: clobrano mshitrit


text:
Build fails on Android with GoCoderSDK 1.5.0 build 609

I'm trying to build an Android app but I'm getting some errors.
Following the post install instructions I downloaded the GoCoderSDK 1.5 here.
When I try to run the app I'm geting the following errors:
> Task :react-native-wowza-gocoder:compileReleaseJavaWithJavac FAILED
/mnt/projects/trywowza/node_modules/react-native-wowza-gocoder/android/src/main/java/com/rngocoder/AutoFocusListener.java:9: error: cannot find symbol
import com.wowza.gocoder.sdk.api.devices.WZCamera;
                                        ^
  symbol:   class WZCamera
  location: package com.wowza.gocoder.sdk.api.devices
/mnt/projects/trywowza/node_modules/react-native-wowza-gocoder/android/src/main/java/com/rngocoder/AutoFocusListener.java:10: error: cannot find symbol
import com.wowza.gocoder.sdk.api.devices.WZCameraView;
                                        ^
  symbol:   class WZCameraView
  location: package com.wowza.gocoder.sdk.api.devices
/mnt/projects/trywowza/node_modules/react-native-wowza-gocoder/android/src/main/java/com/rngocoder/AutoFocusListener.java:11: error: cannot find symbol
import com.wowza.gocoder.sdk.api.geometry.WZSize;
                                         ^

Checking the release notes I found this change (link):

Changed the prefix of all WZ classes to WOWZ to be consistent with the naming convention in Wowza GoCoder SDK for iOS. This is a breaking change. You must update your code.

In the Readme.md there is a note:

... we require RN 0.42+ and GoCoderSDK 1.5.+ for this to work!

So, I think this package is not compatible with GoCoderSDK 1.5.+ as said in the Readme.
Is there any plan to support the newest versions of the SDK?

Is there any update on this?

I am also having same issue.

Guys, sorry for the late response. We haven't updated this package in quite some time. We currently don't have the resources to make any updates in the near future either. Any one of you is welcome to open a pull request that fixes these issues and brings this package up to speed to work with the latest version Wowza GoCoder SDK.
Thanks!

I'm actually working on this in a forked repo, but if I get it, I'll submit it here too.

I've fixed this in my forked repo. Do install from my fork for the latest SDK support.

Do install from my fork for the latest SDK support.

Correction on

I'm trying to build an Android app but I'm getting some errors. Following the post install instructions I downloaded the GoCoderSDK 1.5 here.
When I try to run the app I'm geting the following errors:
> Task :react-native-wowza-gocoder:compileReleaseJavaWithJavac FAILED
/mnt/projects/trywowza/node_modules/react-native-wowza-gocoder/android/src/main/java/com/rngocoder/AutoFocusListener.java:9: error: cannot find symbol
import com.wowza.gocoder.sdk.api.devices.WZCamera;
                                        ^
  symbol:   class WZCamera
  location: package com.wowza.gocoder.sdk.api.devices
/mnt/projects/trywowza/node_modules/react-native-wowza-gocoder/android/src/main/java/com/rngocoder/AutoFocusListener.java:10: error: cannot find symbol
import com.wowza.gocoder.sdk.api.devices.WZCameraView;
                                        ^
  symbol:   class WZCameraView
  location: package com.wowza.gocoder.sdk.api.devices
/mnt/projects/trywowza/node_modules/react-native-wowza-gocoder/android/src/main/java/com/rngocoder/AutoFocusListener.java:11: error: cannot find symbol
import com.wowza.gocoder.sdk.api.geometry.WZSize;
                                         ^

Checking the release notes I found this change (link):

Changed the prefix of all WZ classes to WOWZ to be consistent with the naming convention in Wowza GoCoder SDK for iOS. This is a breaking change. You must update your code.

In the Readme.md there is a note:

... we require RN 0.42+ and GoCoderSDK 1.5.+ for this to work!

So, I think this package is not compatible with GoCoderSDK 1.5.+ as said in the Readme.
Is there any plan to support the newest versions of the SDK?

Actually, not all places were replaced by WOWZ, they rapleced every method but the broadcast services state while overridden is still WZ...

authors: 2chaines Ayanjit Tracklous ademirmochi pranay-medlmobile victor0402


text:
Add negation location to negex outputs

It would probably be a good idea to show not just which entities where negated, but what was the trigger for the negation. This should not be too much of a problem since the matcher returns the position and all that is needed is to persist that.

Great point. There is a way to get this by looking at an entity's modifiers, although it's not based on specific attributes. Does the snippet below get you the info you're looking for?
doc = nlp("There is no evidence of pneumonia.")
for ent in doc.ents:
    print(ent, ent._.is_negated)
    for modifier in ent._.modifiers:
        print(modifier, modifier.category)

Great point. There is a way to get this by looking at an entity's modifiers, although it's not based on specific attributes. Does the snippet below get you the info you're looking for?
doc = nlp("There is no evidence of pneumonia.")
for ent in doc.ents:
    print(ent, ent._.is_negated)
    for modifier in ent._.modifiers:
        print(modifier, modifier.category)

Yeah, I realized I was looking at the old version of medspacy with the original negex instead of the context. Thanks!

Yeah, I realized I was looking at the old version of medspacy with the original negex instead of the context. Thanks!

repo: medspacy/medspacy


text:
insertTao not found

windeditor 中调用了一个叫 insertTao 的插件，但是并不存在。
customPlugins.push('insertTao');

好的，抽时间看看～

@kinosang 已经修复～

authors: kinosang medz

repo: medz/phpwind


text:
NDK ERROR

CMake Error at G:/Android/sdk/cmake/3.10.2.4988404/share/cmake-3.10/Modules/ExternalProject.cmake:2474 (message):
No download info given for 'boringssl_proj' and its source directory:

I didn't use git to download...

any one can answer this issue?

repo: meetecho/janus-mobile-sdk


text:
Rename UNeXt2

Rename the 'Unet22d' architecture to 'UNeXt2'.

@Soorya19Pradeep just FYI we are changing names for what used to be 2.2D Unet

Thanks for the update @edyoshikun !

authors: Soorya19Pradeep edyoshikun ziw-liu

repo: mehta-lab/VisCy


text:
Upgrade to jest v24-26 and babel to version 7

Because or Jest version is v23 we have vulnerabilities caused by yargs-parser.
We tried to fix it by using the resolutions, this introduced more problems. Also, resolutions are patches and not a solution.
linked issue: https://github.com/facebook/jest/issues/7424
This vulnerability has been fixed in jest v24>
Jest version 24 uses Babel 7:
https://jestjs.io/blog/2019/01/25/jest-24-refreshing-polished-typescript-friendly#typescript-support
But we use a previous version that is not compatible with jest v24.
To fix this problem properly we should consider upgrading jest to v24 or higher and babel to version 7.

Also related to #123 I think.

authors: bidoubiwa curquiza


text:
{ kind: Builder, source: RelativeUrlWithoutBase }

Great utility! We're getting the error { kind: Builder, source: RelativeUrlWithoutBase } when running:
cargo run --release -- --url 'https://ms-abc.nyc.meilisearch.io' --index abc --primary-key mykey --token xyz --files ./dataset/jsonfile.json --batch-size 90MB
Can you confirm this supports local JSON files as follow?
[
{ "a": "b" }, { "a": "c" }
]

Hey @sabatale 👋
Yes, it does support this kind of local files. However, the issue you encounter seems more related to the URL you are using even if it seems valid to me. Was it this one that you used when you tested the CLI tool? Because using an URL like this one ms-abc.nyc.meilisearch.io (no https://) can result in the error you got.

Hi! I am having the same issue here. The command I entered looks like:
meilisearch-importer --url 'https://search.pwn.guide' --index docs --api-key 'MyAPIKey123' --files docs.json
Help would be appreciated!

authors: Kerollmops pwnllc sabatale

repo: meilisearch/meilisearch-importer


text:
event for placeholder images position change ?

Hi,
How to handle placeholder images position changes ?
Example: i have 3 images in the placeholder, then i drag & drop image 1 after image 2, how can i intercept this event  so i can push the new images order to my server ?
ty

Hi, evitik:
You can get these info through property - uploadInfo. Actually the light DOM's input will also put these data into its value.

I was speaking of an event, so i added a new "custum" event on my side "msc-image-uploader-move"

authors: eviltik meistudioli

repo: meistudioli/msc-image-uploader


text:
[Android/Vulkan] Unable to use CopyTexture with cubemaps

This code crashes when running on Android/Vulkan:
var cubemap = factory.CreateTexture(TextureDescription.Texture2D(
        texSize, texSize, 1, 1, PixelFormat.R8_G8_B8_A8_UNorm, TextureUsage.Cubemap));
var sampled = factory.CreateTexture(TextureDescription.Texture2D(
        texSize, texSize, 1, 1, PixelFormat.B8_G8_R8_A8_UNorm, TextureUsage.Sampled));

var cl = factory.CreateCommandList();
cl.Begin();
cl.CopyTexture(sampled, 0, 0, 0, 0, 0, cubemap, 0, 0, 0, 0, 0, texSize, texSize, 1, 1);
cl.End();

device.SubmitCommands(cl);
device.WaitForIdle();

Only tested it on a Xiaomi Redmi 4X (Android 7.1).
You can find a small repro project here.

Hm, very odd. I have the same phone, so I'll give it a shot on mine sometime soon.

You're passing 0 for the depth parameter. Instead, that should be 1. I didn't actually test this on my Android yet, but running your code on my desktop I do get a validation error. Using 1 for the depth avoids the validation error. Can you give that a try and see if it fixes the issue?

In the meantime, I will add some validation to CommandList.CopyTexture that ensures you specify a region that is valid.

Right, it should be 1. Still getting the exact same crash though.

I did a bit of investigating. It crashes in Release mode for me, but not otherwise. It doesn't seem to matter what kind of Texture or what the format is. I tried RGBA8_UNorm, and non-cubemap, and it still failed. Since it works in Debug mode, I wonder if there's some optimization that's corrupting something? I'll give try to give this a closer look tomorrow.

Hmm, on my device it crahses in Debug mode as well.

The format was supposed to be RGBA8_UNorm in both cases, but well, not that it matters. Also you're right, it doesn't even have to be a cubemap. Getting the same crash with 2 Sampled textures, both in Debug and Release modes.

Updated the issue and the repro project since the problem isn't specific to cubemaps.

This is where it crashes.

Another update: it only crashes when using the 32-bit runtime. Here's how to make sure it's used instead of the ARM64 one:

Uncheck Android Options -> Use Shared Runtime in the project settings
In the Advanced settings, uncheck every architecture except armeabi-v7a.

Since calling conventions are on my mind lately, one guess is that there's something wrong there. The Vulkan docs aren't very up-front with this info, but there are clues in some header files regarding platform-specific calling conventions. I'm not sure if this could affect us. The Vulkan bindings currently use StdCall everywhere (and it's non-trivial to do platform-specific calling conventions).

Weird, I can use the debugger just fine. Here's the debug output I'm getting. I don't think there's much useful information in there except that it's a segfault.
Meanwhile, I tried running this on Mono x86 on Windows -- no crash.

Hm, are you able to step through the code and get output from Debug.WriteLine, for example? Those aren't working for me, which is very frustrating. They only work if I use arm64-v8a.

Yes, the experience is exactly the same as when debugging an ARM64 app.

Now that I've enabled debug layers, this is the message I'm getting:
Source AccessMask 0 [None] must have required access bit 16384 [VK_ACCESS_HOST_WRITE_BIT]  when layout is VK_IMAGE_LAYOUT_PREINITIALIZED, unless the app has previously added a barrier for this transition.

Alright, I've built it from source. Only getting this message now.
" [ VUID-VkImageSubresourceLayers-aspectMask-requiredbitmask ] Object: VK_NULL_HANDLE (Type = 0) | vkCmdCopyImage: value of pRegions[0].srcSubresource.aspectMask must not be 0. The spec valid usage text states 'aspectMask must not be 0' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-VkImageSubresourceLayers-aspectMask-requiredbitmask)"

Yeah, I'm not sure how that could be 0. On the other hand, it's really valuable information that there is a validation error on the exact function call that is crashing. Perhaps there is something going wrong in the struct layout or struct marshalling somehow?

I'm getting a slightly different error when using PInvoke instead of calli:
" [ VUID-vkCmdCopyImage-pRegions-parameter ] Object: VK_NULL_HANDLE (Type = 0) | vkCmdCopyImage: required parameter pRegions specified as NULL. The spec valid usage text states 'pRegions must be a valid pointer to an array of regionCount valid VkImageCopy structures' (https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-vkCmdCopyImage-pRegions-parameter)"
[DllImport("libvulkan.so")]
public static extern void vkCmdCopyImage(VkCommandBuffer commandBuffer, VkImage srcImage, VkImageLayout srcImageLayout, VkImage dstImage, VkImageLayout dstImageLayout, uint regionCount, VkImageCopy* pRegions);

Tried several calling conventions - the error is the same (yet it's different when using calli).

I don't think switching everything to PInvoke should make a difference. It seems like, for whatever reason, the pointer parameter is getting mangled or passed incorrectly somehow. Both error messages seem to point to that (the first message seems to indicate a valid pointer, but invalid data).

This is the code generated by Mono's AOT compiler in release mode:
LDR     R1, [R0] ; vkCmdCopyImage
LDR     R0, [R11,#commandBuffer]
LDR     R2, [R11,#srcImage_lo]
LDR     R3, [R11,#srcImage_hi]
LDR     R12, [R11,#srcImageLayout]
STR     R12, [SP]
LDR     R12, [R11,#dstImage_lo]
STR     R12, [SP,#4]
LDR     R12, [R11,#dstImage_hi]
STR     R12, [SP,#8]
LDR     R12, [R11,#dstImageLayout]
STR     R12, [SP,#0xC]
LDR     R12, [R11,#regionCount]
STR     R12, [SP,#0x10]
LDR     R12, [R11,#pRegions]
STR     R12, [SP,#0x14]
BLX     R1

Essentially, this is what the registers and the stack look like when vkCmdCopyImage is called:
R0: commandBuffer
R1: points to the function
R2: srcImage (low word)
R3: srcImage (high word)

[SP + 0] srcImageLayout
[SP + 4] dstImage (low word)
[SP + 8] dstImage (high word)
[SP + C] dstImageLayout
[SP + 10] regionCount
[SP + 14] pRegions

And here's the equivalent (except working) code generated by clang:
LDR.W       LR, [LR] ; vkCmdCopyImage
LDR         R2, [SP,#0x700+commandBuffer]
LDR         R3, [SP,#0x700+srcImage+4]
LDR.W       R12, [SP,#0x700+srcImage]
LDR.W       R4, [SP,#0x700+dstImage]
LDR.W       R5, [SP,#0x700+dstImage+4]
MOV         R6, SP
LDR.W       R8, [SP,#0x700+var_634]
STR.W       R8, [R6,#0x18] ; pRegions
STR         R0, [R6,#0x14] ; regionCount
MOVS        R0, #7
STR         R0, [R6,#0x10] ; dstImageLayout
STR         R5, [R6,#0xC] ; dstImage (low word)
STR         R4, [R6,#8] ; dstImage (high word)
MOVS        R0, #6
STR         R0, [R6] ; srcImageLayout
MOV         R0, R2
MOV         R2, R12
BLX         LR

So the arguments are passed like this:
R0: commandBuffer
R1: unused?
R2: srcImage (low word)
R3: srcImage (high word)

[SP + 0] srcImageLayout
[SP + 8] dstImage (low word)
[SP + C] dstImage (high word)
[SP + 10] dstImageLayout
[SP + 14] regionCount
[SP + 18] pRegions

Notice where pRegions is stored. The location is different, and that's because here we have a 4 byte gap between srcImageLayout and dstImage. I don't have an explanation for this. Could be some sort of convention that Mono doesn't respect, I don't know. But the fact of the matter is, the implementation expects to find pRegions at [SP + 18], not [SP + 14].
I've already tried changing the function signature so that the arguments would end up at the corrent locations, and it worked. You can do that by adding an extra 4 byte parameter after srcImageLayout. Removing the extra parameter makes it crash again. I think this will only work in release mode, though.

@SomeAnon42 That is excellent information. Thanks for helping out with the debugging. Unless there's some other way for us to influence how the parameters are handled that we haven't already tried, then it seems to be a mono codegen bug.

I'd really like to see what RyuJIT generates on ARM32. But, unfortunately, I don't have any ARM devices that can run desktop Windows or Linux.

Hmm... .NET Native gives me this error:
Error: NUTC300D:Internal Compiler Error: Type 'Vulkan.VkComputePipelineCreateInfo[]' is not valid for use outside of the managed environment, but is passed to native code while compiling method 'static Vulkan.VkResult Vulkan.VulkanNative.vkCreateComputePipelines(Vulkan.VkDevice, Vulkan.VkPipelineCache, System.UInt32, Vulkan.VkComputePipelineCreateInfo[], Vulkan.VkAllocationCallbacks&, Vulkan.VkPipeline&)'

It looks to me like the issue is that the uint64 dstImage argument is not being aligned to an 8 byte boundary? I took a look at the ARM calling conventions and this seems to be required.

I'd appreciate it if you could file things like this upstream in future - I only found it by chance 🙂

Does the crash happen only when using the AOT compiler ?

Where is the code which calls using calli ?

It's generated as part of this rewriting step: https://github.com/mellinoe/vk/blob/master/src/vk.rewrite/Program.cs. Some marshalling is also done in there, but not for this overload, since it shouldn't be necessary.

the calli needs to use the correct (pinvoke) calling convention.

We talked about all of this above -- using different calling conventions doesn't make a difference. Also, there are dozens of other Vulkan functions that are being called successfully which are all declared with the same calling convention.

Does the crash happen only when using the AOT compiler ?

I can't recall that -- @SomeAnon42 Do you remember? I can't test this again until later tonight.

Does the crash happen only when using the AOT compiler ?

No, it happens when using the JIT compiler as well. I simply used the AOT compiler to get the disassembly, because that seemed like the easiest way to me.

@vargaz I think we hit a different case. You are assuming the parameter is MONO_TYPE_I8, right?
But since the type is VkImageCopy* pRegions, we go this path:
https://github.com/vargaz/mono/blob/b0f20fcd028811c24e2e6b82e623972cb6d94431/mono/mini/mini-arm.c#L1410-L1415 or
https://github.com/vargaz/mono/blob/master/mono/mini/mini-arm.c#L1435-L1440
and therefore simple = TRUE
https://github.com/vargaz/mono/blob/b0f20fcd028811c24e2e6b82e623972cb6d94431/mono/mini/mini-arm.c#L1069-L1075
where we don't respect eabi_supported/i8_aligned.
does that sound plausible?

authors: SomeAnon42 lewurm mellinoe mhutch vargaz

repo: mellinoe/veldrid


text:
Support a Python-based Plugin Architecture

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3038
Originally created by @aaronsteers on 2021-11-02 21:22:40

Currently all Python-specific plugin handlers live in our main Meltano repo and is installed in a single go.
To make a leaner install, we could (for instance) refactor "Singer EL", "dbt Transform", and "Airflow Orchestrator" into separate repositories.
For each type of plugin we want to support, we'd have to create an interface layer and decide which hooks/notifications/invocations are needed by the respective type of plugin.
Note: The refactoring effort for the Singer EL would likely be very large. It might make more sense to use orchestrators (Dagster or Airflow) first.
How is this different?
Today, if we want to support Dagster in the same way we support Airflow, we have three levers we can control:

CLI-based 'command' definitions. This is basically just aliasing existing CLI commands from the tool. Not capable of deep integrations.
Files-based plugins. This is the least robust: we download some pre-configured files into the repo.
Python code-based approach. This is the only "deep" integration option we have today. This gives a lot of power to wrap the tool's capabilities, but it also requires expanding the code base of Meltano core repo.

This proposal would give an alternate path to the third option, enabling us to write an external plugin definition in python, and import it into the project without having it defined tightly as part of that repo.

View 8 previous comments from the original issue on GitLab

repo: meltano/meltano


text:
Docs - requirements links broken

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/494
Originally created by @derek-knox on 2019-03-18 20:59:01

Simple links fixing.

View 2 previous comments from the original issue on GitLab


text:
Update Config params when using Local Ollama models

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

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (does not change functionality, e.g. code style improvements, linting)
[ ] Documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Please delete options that are not relevant.

[ ] Unit Test
[ ] Test Script (please provide)

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have checked my code and corrected any misspellings

Maintainer Checklist

[ ] closes #xxxx (Replace xxxx with the GitHub issue number)
[ ] Made sure Checks passed

Hey @SamuelDevdas Thanks for the contribution. Changes LGTM.

authors: Dev-Khant SamuelDevdas


text:
restart: remove unused restart_mmap_set function

restart_mmap_set function in restart.h is not used but has not been removed.

thanks!

Out in 1.5.20

repo: memcached/memcached


text:
nvgCreateImageMem() creates black square, no errors

I am using the LWJGL bindings for NanoVG.
While I am using the Java bindings for NanoVG, the issue I am having is related directly to the library itself.
I want to create a NanoVG image from a ByteBuffer, in order to draw it on the screen using the nvgCreateImageMem method. This is because I want to load the image asynchronously, something which cannot be achieved using nvgCreateImage. The picture, a PNG, is read into a ByteBuffer, flipped, then given to NanoVG. However, when I use it to fill a rectangle on the screen, it just appears as solid black.
The signature in the bindings I am using for nvgCreateImageMem is:
int nvgCreateImageMem(long ctx, int imageFlags, ByteBuffer data)

Here is the contents of the ByteBuffer:
-119 80 78 71 13 10 26 10 0 0 0 13 73 72 68 82 0 0 0 48 0 0 0 48 8 4 0 0 0 -3 11 49 12 0 0 0 -56 73 68 65 84 88 -61 -19 -106 75 10 -61 48 12 5 5 57 100 126 -89 75 106 66 15 105 -104 46 10 37 -115 67 44 -39 -54 -94 -59 111 109 -49 -128 -80 31 18 105 105 105 -7 -37 -48 17 -24 -43 -89 103 86 58 27 -2 9 68 -99 -126 -103 8 108 6 5 -127 119 34 -125 18 15 -16 -48 11 -122 -49 -91 -116 98 -121 -113 -6 -111 -86 21 -59 -8 68 49 -70 -29 69 68 24 -81 20 -43 -8 107 -123 11 62 81 76 -18 120 17 17 -90 -93 -62 21 -97 42 -36 -15 -119 -62 31 127 24 -53 29 -8 68 -31 -113 -65 93 112 -13 -120 -66 94 78 -44 55 109 9 -66 -41 55 109 17 -34 86 -26 69 120 93 -45 86 -31 -13 77 91 -115 119 81 -28 59 -25 -68 105 -35 -16 -25 77 -21 -118 -81 80 -80 -22 -1 -21 78 -79 88 22 -81 -51 -68 120 5 -21 110 103 91 29 23 19 -66 -91 -91 -27 -57 -14 2 97 52 95 56 -6 -23 5 -103 0 0 0 0 73 69 78 68 -82 66 96 -126

Here is the actual image.
When I write the ByteBuffer out to a file, and then load it using nvgCreateImage, the picture is displayed correctly.
As the title says, no error or warning is printed to the console.
I think that one of two things could be happening; the first being far less likely than the second:

There is actually a bug in nvgCreateImageMem()
nvgCreateImageMem() wants the image data to be in a certain format that my ByteBuffer is not in. If this is the case, what format should it be in? The required format is perhaps something that could be clearer in the documentation.

nvgCreateImageMem() expects same data format as nvgCreateImage(). They both return 0 in case creating the image failed.
I dont know what ByteBuffer does. What is the actual code you use to get stuff from ByteBuffer and pass it to NanoVG? What does flipping the buffer mean?

Thank you for your fast response. I will try to answer your questions and follow up on your points:

They both return 0 in case creating the image failed.

nvgCreateImageMem() does not return 0. Instead, it returns 3.

I dont know what ByteBuffer does.

Here is an explanation of ByteBuffer and what its used for:
"The easiest way to think of ByteBuffer is as a wrapper over a native C pointer, plus the array length (the buffer.capacity()). LWJGL maps C primitive types to the corresponding class in java.nio. Arrays of pointers are mapped to the org.lwjgl.PointerBuffer class. Pointers to structs are mapped to the corresponding struct class. Pointers to struct arrays are mapped to the corresponding .Buffer class. PointerBuffer and the struct Buffer classes have an API very similar to java.nio buffers."

What is the actual code you use to get stuff from ByteBuffer and pass it to NanoVG?

The data is read from a file into the ByteBuffer like so:
try (SeekableByteChannel byteChannel = Files.newByteChannel(path)) {
            buffer = createByteBuffer((int) byteChannel.size() + 1);
            while (byteChannel.read(buffer) != -1);
}
buffer.flip()

I am using this method of reading the file to load font files for NanoVG; and it works perfectly.
The binding take the ByteBuffer as an argument, and then runs the following:
nvgCreateImageMem(ctx, imageFlags, memAddress(buffer), buffer.remaining());

memAddress() is part of MemoryUtil.
Here is the screenshot of the black square. If I use nvgCreateImage() instead, the icon renders correctly, as you can see here.

I have discovered the cause of the problem:
You cannot create images on a separate thread, they must be created on the main thread
If you try to create images on a separate thread from the active context thread, you will get a full black or full white image, and no error will occur.

To people seeing this in the future:
Make sure you fully understand the discrepancy between nvgCreateImageMem() and nvgCreateImageRGBA(). Under the hood, nvgCreateImage() loads an image using stb, and then creates the image using the latter of these two methods. This is something that surprised me when trying to solve the issue I was having above. If you use the wrong method, you will probably get funny (i.e. undesirable) results.

authors: memononen otoomey

repo: memononen/nanovg

license: Zlib


text:
(WIP) struct Rav1dData{,Props}: Replace Rav1dRefs with CArcs

There are still 3 remaining failing tests that I've been trying to debug for a while but not having much success (I left my current debugging code in).  I'll split up the PR more carefully once I get it working.

The bug has been fixed and the PR has been split into:

#655
#656
#657
#658


text:
purpose

just curious, but is there an additional benefit in using this tool, from dev perspective, as opposed to just using netcat/socat?
$ printf "%s\n"   "HTTP/1.0 200 OK"  "" \
    | docker run -i --rm --name test -p 8080:80 alpine:3.10 nc -lp 80 &
$ echo '{ "key": "value" }' | curl -D- -d@- localhost:8080
HTTP/1.0 200 OK

POST / HTTP/1.1
Host: localhost:8080
User-Agent: curl/7.54.0
Accept: */*
Content-Length: 18
Content-Type: application/x-www-form-urlencoded

{ "key": "value" }
$

It'll depend on what you're using it for.  Not every test setup will have access to nc, like mobile devices or emulators.  If you do have those tools then this is just a convenience with some pretty printing/formatting.  I use it for HTTPS/Certificate testing too.
In some cases like closed applications, I want to issue the request and inspect it afterwards (via docker logs rather than the response)

Not every test setup will have access to nc, like mobile devices or emulators.

I know absolutely nothing about iot, mobile, et al, so take the following as mostly ignorance: first, I was using an alpine container, purposefully here, to ensure access to netcat or preferred tooling, because my assumption was that the repo docker-http-https-echo, considered docker as a given dep. Second, is nodejs, as a dependency, more or less available on non-standard platforms, than netcat, socat, /dev/tcp, telnet, yada?
What I am driving at here, is, is did you use nodejs because you like nodejs or because the tool fit your given requirements and in a way that gives an advantage over older, better established and generally more available utilities?
That sounds more rhetorical and aggressive than intended, and tbh, I, along with everyone else gives outsized preference to the tools they like: I use shell when I shouldn't and end up with 800 line horrors that no one can read. In this case, i am honestly just curious.
Cheers

The platform tooling and availability isn't a consideration, it's simply that this image forms part of my test suite, so I go docker-compose up -d and everything is ready for me to run my test harnesses.  For others it will serve other troubleshooting/testing purposes and I can't speak for them. This has no advantage over other utilities, it's merely a convenience function; if something else works for you please continue using it.
Regarding the choice of NodeJS your question is then better directed at the origin - this repo is a fork of a fork, it's not original.   I've adopted it to add additional information in the output, the docker logs, support custom TLS certificates, and share it on Docker Hub.

authors: callowaylc mendhak

repo: mendhak/docker-http-https-echo


text:
Compatibility with Xmonad

I know you mentioned that you only tested on Ubuntu, but if you're interested in making it compatible with arch, the only problem right now is that the menu executes the commands when hovering over the entry, not when clicking.
I am on the newest kernel (5.17.5) and python 3.10, im using xmonad, as window manager, and xmonbar with trayer
EDIT: kernel version and window manager information

At last I was able to get tray icons working.  I had to install https://extensions.gnome.org/extension/615/appindicator-support/ and also https://flathub.org/apps/details/org.gnome.Extensions and then turn on the Extensions.
However, the behaviour you mentioned, I didn't see that.  The system only reboots when I click on a menu item.

Now I don't really understand xmonad and xmobar, but I installed them using sudo pacman -S xmonad xmobar and then I logged out, chose xmonad from the login screen, but when I login, the screen is just blank.  I have no idea what is happening here.

I apologize for the disrespectful amount of time I haven't come back here.
so xmonad is a tiling window manager that relies on a user-created config file.
What you experienced was

I apologize for responding late to this topic.
You would install the package from the AUR using some AUR-Helper like yay.
Xmonad is a tiling window manager that relies on a user-edited config file. What you experienced was the default behaviour, pressing Alt + Shift + Enter will bring up a terminal.
I have some new Information about the behaviour I'm experiencing.

I have tested it in GNOME, and i can confirm that the issue is not with Arch itself, but the windowmanager xmonad. (I changed the Issue name accordingly)
In the provided picture you can see that the reboot picker interprets the actual bootable Entrys as folders, but the only folder should be the Advanced Options.
There is a Critical error you can see in the Terminal Emulator, i have no clue what it means as I have no clue of GDK-Programming or UI programms in general, maybe that can help you.

@errare-humanum-est1 while testing on Ubuntu 24.04 I was able to reproduce the "activate on mouse hover" issue. I do have a workaround for it here. At some point this should make its way to the next release.
https://github.com/mendhak/grub-reboot-picker/pull/7/files#diff-ec1a1686f710546e40a3ab11f7684e7c7720a631feab4204bed44d194e121868R136-R145

OK so a new version 0.0.9 is published and that activate-on-hover problem should go away, at least the specific one I found should go away.

repo: mendhak/grub-reboot-picker


text:
Clarify Java options configuration

This setting is discussed in #232 / #234 but isn't very well documented.
This clarifies the expected format used to configure Java options.

Oh hey, this is done much better by #260

repo: mendix/cf-mendix-buildpack


text:
[NC] Add PIW Switch documentation and update core checkbox documentation

The core Checkbox widget will soon have a new render mode checkbox (because currently it renders as a Switch depsite its name). Update the styling documentation to clarify this and add new styling properties.
Document core checkbox render mode
A new pluggable Switch widget will be added to the marketplace. Add styling documentation for this widget.

@ConnorLand the code for this is merged into AppDev, meaning it will be released in 9.8.0 Studio Pro.
How can we manage this to avoid needing to remember this open PR? Can we apply a label 9.8.0 or something so that once 9.8.0 is released, this gets merged?

@ConnorLand the code for this is merged into AppDev, meaning it will be released in 9.8.0 Studio Pro.
How can we manage this to avoid needing to remember this open PR? Can we apply a label 9.8.0 or something so that once 9.8.0 is released, this gets merged?

Label added.

authors: ConnorLand jordanch

repo: mendix/docs


text:
Rewards

Plugin that replicates lifepoints.io

3d dice rolls using http://a.teall.info/dice/ and randomness from random.org?

repo: mentality-tools/tasklist


text:
Add additional query args

Hi - I know this is unsolicited so please just close if you don't want it. I wanted to not get notifications about dependabot so I've added an additional field to the view -

I don't know Swift and this is my first time fiddling, so if its wrong I wont be offended if you close.

Hi! This is great! I was tired of dependabot PRs as well, but I thought it's only me 😆 - it's a good solution 👍
I will probably rename the Menu tab to General and move this setting there - hope you don't mind)
Thank you!

Hi! This is great! I was tired of dependabot PRs as well, but I thought it's only me 😆 - it's a good solution 👍 I will probably rename the Menu tab to General and move this setting there - hope you don't mind)
Thank you!

Thats great thanks - do what you want with it, I just wanted to contribute back since I was tweaking it to my requirements.
Its a great app btw!

authors: owenrumney streetturtle

repo: menubar-apps/PullBar


text:
[Fix] Header fixes

[Fix] Header fixes
Cambios:

Cambio de iconos del badge
Cambio del status bar en el Header Component
Formateo de los amounts en el título del Header Component
Fix de loadings en la pantalla de payment result: El loading se muestra hasta que termina el api call de instrucciones.

Codecov Report

:exclamation: No coverage uploaded for pull request base (feature/congrats-templating@b55523d). Click here to learn what that means.
The diff coverage is 30.37%.

@@                      Coverage Diff                       @@
##             feature/congrats-templating     #730   +/-   ##
==============================================================
  Coverage                               ?   29.48%
==============================================================
  Files                                  ?      279
  Lines                                  ?    19066
  Branches                               ?     1694
==============================================================
  Hits                                   ?     5622
  Misses                                 ?    12828
  Partials                               ?      616

Impacted Files
Coverage Δ

...dopago/paymentresult/props/PaymentResultProps.java
63.63% <ø> (ø)

...rcadopago/paymentresult/PaymentResultActivity.java
0% <ø> (ø)

...dopago/paymentresult/renderers/HeaderRenderer.java
0% <0%> (ø)

...opago/paymentresult/PaymentResultPropsMutator.java
0% <0%> (ø)

.../com/mercadopago/util/SuperscriptSpanAdjuster.java
0% <0%> (ø)

...paymentresult/renderers/PaymentResultRenderer.java
0% <0%> (ø)

...cadopago/paymentresult/renderers/IconRenderer.java
0% <0%> (ø)

...ymentresult/components/PaymentResultContainer.java
73.83% <100%> (ø)

...m/mercadopago/paymentresult/props/HeaderProps.java
59.57% <50%> (ø)

...cadopago/paymentresult/PaymentResultPresenter.java
37.89% <55.55%> (ø)

... and 3 more

Continue to review full report at Codecov.

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

authors: codecov-io valeserber

repo: mercadopago/px-android


text:
why does not .gitignore file of gaurun contain _vendor?

mattn/gom creates the _vendor directory by default. But the .gitignore file of gaurun contains .vendor.
Why does not .gitignore file of gaurun contain _vendor?

mattn/gom allows changing vendor-path by GOM_VENDOR_NAME.
Usually I use the config below. Because I don't like that external packages are always visible.
export GOM_VENDOR_NAME=.vendor

But it is possible to ignore .vendor with ~/.gitignore instead of gaurun/.gitignore. As you mentioned, gaurun/.gitignore should contain _vendor instead of .vendor in general. (Patches welcome!)

I make the patch #5.
Please merge.

authors: catatsuy cubicdaiya

repo: mercari/gaurun


text:
Can we make a flag to make it support parsing PDX file even validation fail?

We discussed in a previous question about parsing PDX files when validation fails. The validation failure is caused by the keyword "assert", for example,
def parse_int(value: str) -> int:     try:         return int(value)     except ValueError:         v = float(value)         assert v.is_integer()         return int(v)
In this scenario, if the input string is "0.05", the entire process fails. However, we would like to continue parsing the rest of the validated PDX file without letting one type of issue block the entire process. Editing the PDX file is a costly process, and we would prefer not to modify it.
Is it possible to introduce a flag that allows us to control the behavior of the library, enabling it to parse the entire PDX file even if validation fails in a testing environment? For instance, we can toggle the flag to false during testing, allowing the parsing of the PDX file. However, in the production environment, we can set the flag to true to ensure parsing fails if validation fails. The production environment should prioritize safety considerations.

the problem with this in general is that removing the asserts outright will lead to a lot of mypy complaints. In your particular case, I would advise to locally remove the incriminating assert in parse_int(), if you're really sure that throwing away all decimal digits is correct...
also, it could be that parse_int() was used somewhere where floating point values are allowed. In this case, please open a PR fixing that. (this is the case if all *.odx-d files that are contained within the PDX validate against the XSD schema file from the ODX specification package.)

since #168 has been merged, there now is a non-strict mode which might help here. Let's close the issue for now. If it turns out that the non-strict mode does not help, feel free to re-open it...

repo: mercedes-benz/odxtools


text:
HAP-NodeJS Warning

Hi,
I'm getting this warning in HB logs:
[4/29/2020, 17:23:03] [webostv] webOS - init - initializing devices
[4/29/2020, 17:23:03] [webostv] webOS - init - initializing device with name: Old Room TV
HAP-NodeJS WARNING: The accessory 'Old Room TV' is getting published with the characteristic 'Name' (of the AccessoryInformation service) not having a value set. This might prevent the accessory from being added to the Home App or leading to the accessory being unresponsive!
[4/29/2020, 17:23:03] [webostv] webOS - init - initializing device with name: New Room TV
HAP-NodeJS WARNING: The accessory 'New Room TV' is getting published with the characteristic 'Name' (of the AccessoryInformation service) not having a value set. This might prevent the accessory from being added to the Home App or leading to the accessory being unresponsive!

Maybe this can fix #223.

This is strange, i do not get the warning on my machine. What version of HAP-NodeJS do you have installed?

@agneevX same issue here

[4/29/2020, 8:32:07 PM] [webostv] webOS - init - initializing device with name: LG Television
HAP-NodeJS WARNING: The accessory 'LG Television' is getting published with the characteristic 'Name' (of the AccessoryInformation service) not having a value set. This might prevent the accessory from being added to the Home App or leading to the accessory being unresponsive!

Can you please post your HAP-NodeJS version?

Sorry I am not sure how to find it out?

How about your homebridge version?

How about your homebridge version?

Its 1.0.3.

How about your homebridge version?

1.0.3 too

This is strange, i do not get the warning on my machine. What version of HAP-NodeJS do you have installed?

Are you using Config UI X? v4.17.1 is the version I'm using where these logs are visible.

Ok, i just updated to the latest versions and also got the warning. Will check it out.

Fixed with my latest commit.
@agneevX can you please check if that also fixes your other issue? You would need to manually replace the index.js. I want to make sure if this is just a cosmetic warning or really can cause other issues before i release a new version.

Fixed with my latest commit.

confirmed latest commit on index.js has fixed it for me

You would need to manually replace the index.js.

Where is this located again?

This issue is not resolved as the warnings are still shown https://github.com/merdok/homebridge-webos-tv/issues/226#issuecomment-625155990.

I did not yet release a new version with that fix since for now it just looks like a harmless warning.
If you think that this could fix your issue then you need to manually replace the index.js and let me know, then i will release a new update with the fix included.

Same warning comes up with me.
Homebridge Version: 1.1.0
Node.js Version | v14.2.0
Npm Version | v6.14.4
homebridge-webos-tv v1.7.1

authors: Salvora agneevX coalfield merdok

repo: merdok/homebridge-webos-tv


text:
doc: fix flux case problem

Signed-off-by: Underwood-M dongfanghuifan@gmail.com
Summary
doc: fix flux case problem

Hi @Underwood-M, thanks for pointing this out! Your attention to detail is extraordinary:)
I also did some research, it seems "Flux" should be uppercase.
I'm not so sure about "FluxCD" or "Flux CD" (with or without the space). According to Google, it seems to be "Flux CD" (see attached screenshot), but I didn't find it elsewhere. What do you think?

repo: merico-dev/stream


text:
Controlling 4 lights

how can i control many lights using mqtt light.ino file, ive tried many ways of modifying the  code but it didnt work... please help me to fix..

Hi @PavanSN,
Someone asked me the same question a few months ago. Just look at this [issue]/https://github.com/mertenats/Open-Home-Automation/issues/1), a example is provided.
Sam

authors: PavanSN mertenats

repo: mertenats/Open-Home-Automation


text:
README for Vault auth path configuration

This PR adds a README file with a description of Vault auth path configuration. It is added temporally until an appropriate documentation will be created.

@ronenkat Thanks for the review comments. I made changes based on them.

@revit13 we still need the README right? Do you want to rebase and merge? Sorry I missed the progress on this one

@revit13 please clarify what is the status of this PR.

@revit13 please advise

@revit13 reopen if needed

repo: mesh-for-data/mesh-for-data


text:
Propogate changes to nginx-sm

Description
This PR fixes #
Propagation changes made from this
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@Rohith-Raju If you haven’t built antacid these changes before submitting for others to spend their time reviewing… It would seem that you have, yet again, not done your homework but are asking others to do it for you.
Perhaps I’m misunderstanding the situation, but given the number of times that we have run into the situation I don’t believe that the benefit of the doubt is appropriate. Just like it’s not appropriate to knowingly turn in an incomplete assignment with the expectation that others carry it to completion.

@leecalcote truly sorry, won't happen again. Thought this was a plug-and-play kinda thing, but it is not. I should've known better.I'l l compile and make changes accordingly.

I hear that and if there is any type of issue to learn on, this is a great type to do so with. My ask is that you be upfront with me maintainers, set appropriate expectations and both do your homework and document your studies as proof of diligence.

@leecalcote, Yes, I'll redo the entire changes

@Rohith-Raju there are only very small changes required after this PR, I can make them and keep your commits so you get the credit for your work. On to the next one for you :smile:

@gr455 sounds good, I'm more than happy to make changes if you point them out :smile:

@gr455 sounds good, I'm more than happy to make changes if you point them out so that I'd know where I went wrong. smile

Oh, @MUzairS15 has pointed out the problems. Very small changes though, I did them. No problem. Thanks for doing the major part :smile:

authors: Rohith-Raju gr455 leecalcote

repo: meshery/meshery-nginx-sm


text:
OSM will be achived

Current Situation
There is an open proposal to archive OSM repo at this time.
https://github.com/cncf/toc/pull/1044
Desired Situation
Decide if we're going to keep this repo meshery-osm alive for maintenance or archive this repo as well.

[Optional] Alternatives
A brief description of any alternative solutions or features you've considered.
[Optional] Additional context
Add any other context or screenshots about the chore or task here.
Contributor Resources
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

📝 Meshery Adapters Spreadsheet
See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

We're in need of removing the meshery-osm adapter from the default deployment profile.

authors: acald-creator leecalcote

repo: meshery/meshery-osm


text:
Utilize Liquid templates for feature sections on the homepage

Current Behavior
Currently, the feature sections on the homepage of meshery.io are hardcoded in HTML, which makes it challenging to update or maintain them efficiently.
Desired Behavior
To enhance flexibility and ease of maintenance, it is recommended to transition to Liquid templates for rendering the feature sections dynamically on the homepage. The features sections should be moved in the includes directory and are used as liquid templates.
Screenshots / Mockups

Contributor Guides and Resources

🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🖥 Contributing to Meshery Website
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Ravindra Pandey wants to contribute, shall we assign?

Please assign this issue to me @samyakshah3008 @thisiskaransgit

Please go ahead!

hey @RavindraP04
let's discuss about your progress on the websites call.
Please add this as an agenda item in the meeting minutes, if you would :)
https://docs.google.com/document/d/1XczAHXVe2FIWPqiF57ospJ43zw5cZQ7ui8mn39v5EvA/edit#heading=h.lohhtewfwima

@thisiskaransgit @Ghat0tkach Can you please review the PR


text:
Gem: Updated ruby version to 2.7.5

Signed-off-by: Nikhil-Ladha nikhilladha1999@gmail.com
Description
The latest version of ruby-3.* is not yet available in rvm, so updating it to the next latest available version.
Other gems are taken care of by dependabot. Therefore, no need for manual updates.
Signed commits

[X] Yes, I signed my commits.

build is failing because of the mismatch of ruby versions. @Nikhil-Ladha it's working fine for you locally yes?

Works fine for me locally.
Trying to understand the issue in the case of netlify,

These netlify failures are occurring on other PRs, too.

So, even after changing the version to 2.7.0 the build is failing :/

Ok, found the issue.
Comments are not allowed in a JSON file, and the wasm.json file was having one which led to the failure in parsing.

apparently, the build was failing from 26th Feb 👀

Phew! 😌

Huh, I dont remember me doing that 😅.

Thank you @Nikhil-Ladha , merge at -will

Huh, I dont remember me doing that sweat_smile.

Now let's not blame the old man anymore. We should understand the pain and move ahead 😆

authors: Nikhil-Ladha leecalcote warunicorn19


text:
[Docs] Typo issue in meshery Rest API

Current State
Word "specific" repeat.

Desired State
"Handle GET request for getting meshmodel components of a specific model."

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

I would like to work on this issue. Can you please walk me through the process

@senali-d Shouldn't it be specific model rather than just specific

@UsmanDev09 Yeah it should be. Thank you

Raised PR - https://github.com/meshery/meshery/pull/7628

This has been merged https://github.com/meshery/meshery/pull/7628

done by #7628

authors: UsmanDev09 senali-d shivamganwani suhasamaresh vishalvivekm

repo: meshery/meshery


text:
[Docs] Add description and link to each Meshery schema

Current State
The Designs, Models, Components, Relationships, and other resources are schema-backed constructs in Meshery.
Desired State
Each should have a consistent blurb that points to their schema in https://github.com/meshery/schemas
Example:
-https://docs.meshery.io/concepts/connections should have a description of and link to its schema https://github.com/meshery/schemas/tree/master/openapi/schemas

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

I would like to take this. Please assign this to me.

@LakshyaSatpal you have been assigned the issue.

Thank you, @LakshyaSatpal, @goldfishdolphin.


text:
feat: Add asdf mage targets

Adds asdf targets to mage to control runtime versions. These targets are a necessary intermediate step to migrate tasks not compatible with mage.
Targets( with asdf namespace):
› mage
Targets:
  asdf:install    installs all plugins and versions specified in local and global .tool-versions file
  asdf:upgrade    upgrades all plugins and versions specified in local .tool-versions file

Install:
› mage asdf:install
act 0.2.30 is already installed
age 1.1.0-rc.1 is already installed
...
sops 3.7.3 is already installed
yq 4.25.3 is already installed

Upgrade:
› mage asdf:upgrade
plugin awscli is already up to date with version 2.8.12
...
upgrading age from 1 to 1.1.0-rc.1
age 1.1.0-rc.1 is already installed
....
plugin pre-commit is frozen, with version 2.19.0, skipping upgrade

Install custom plugin from mage target:
func SomeTask(ctx context.Context) error {
	err := asdf.InstallPlugins("golang", "helm", "kubernetes-cli")
	if err != nil {
		return err
	}

	// Do something ...

	return nil
}

@aweris Shall we have unit tests for that targets? Wdyt?

it's in the roadmap but I didn't have time to investigate. I hope we'll add some tests following weeks

repo: mesosphere/daggers


text:
Marathon 0.13 compatible with Mesos 0.26.0?

Mesos 0.26.0 was recently released, any idea if it is compatible with Marathon 0.13.0?
Based on the upgrade instructions it seems like it probably should, though it mentions some "compile time adjustments" might be required.

I've tested mesos 0.26.0 with marathon 0.13.0, everything seems to be fine.

I can also validate that mesos-0.26.0-0.2.145.centos701406.x86_64 & marathon-0.13.0-1.0.440.el7.x86_64 work wonderfully together. Make sure you have upto date patches, else you will see SASL auth issues.

@mindscratch unfortunately, we're not seeing that, see: https://github.com/mesosphere/marathon/issues/2870
They changed something related to tasks IPs with Docker containers.

@scalp42 Marathon v0.13.0 doesn't use the IP address in NetworkInfo for health checks, so it should still be compatible with Mesos 0.26.0.

repo: mesosphere/marathon


text:
don't accept empty string or / as app id

Currently, the marathon API allows to create apps with "id": "". Not only do I think that doesn't make sense, it also caused issues with mesos: It will create tasks with an empty name which are not removed from mesos when deleting the app.

Ugh just realised that check is not exhaustive enough, things like " " will probably cause issues too. Are there validation rules for this I can reuse already?

This requires more validation. For example, sending "id":"/" has the same problems as the empty string before. Am i correct in assuming that the "root" path can never be suitable as an app id?

Zombie tasks in Mesos, which are not removed by marathon when DELETEin the rooth path:

@c089 Yes, the root is a group where all top level tasks live, so it may not be used as an app id.

So this should fix it for now. I'm not familiar enough with the codebase to make up my mind, but I feel it might be a good idea to change the AppDefinition class itself to use a custom type instead of PathId.

@c089 Could you please add the constraint that an app id can not be / in the Reads and add a test for this case? Also please squash this into a single commit, thanks!

I'd love to but right now I fail at understanding this :/
How would I add an "and not equal to"?

It should be enough to append .filter(_.isRoot)

thanks! squashed and rebased onto master

:100: Thanks!


text:
Documentation for persistent volumes

Note: screen shots to come

Thanks, @sascala, please see my comments. It's still not completely clear (because not implemented)

how the housekeeping will work/how and when volumes are destroyed
whether absolute and/or nested containerPaths will be allowed.

I'd go for merging this after you have addressed my comments and polishing the text as soon as we have more information. Are you ok with this?

@meichstedt Thanks for your careful comments. As for merging: if the page won't appear on the live site before the persistent volume functionality actually exists for users, then please do if everything looks good to you. Otherwise, I'd wait on that so as not to promise functionality that doesn't exist yet.

Thanks again, @meichstedt. I fixed the typo and made the change you suggested.

Thanks, @sascala!
                                                       /\  /\
                                                      /  ''  \
                                                     / .o\  ..\
                                                    /.'  |\ | '.
              __                                    '    |_\|
              \ \___     .__                             |_|<o>
            .--""___\..--"/                              |_| |
        .__.|-"""..... ' /                          _____|_|_|\__
________\_______________/______________________..-'::::::::::::::::-..___
                                                 '''""""""""""""""'''
               ~       ~           ~        ~                  ~
       ~                     ~                   ~       ~
  ~                 ~                  ~                         ~

authors: meichstedt sascala


text:
feat(#major); friend-tech; add friend-tech subgraph

Description

Added friend-tech subgraph using non-standard schema.
Added configs for networks: base

Links

base: https://okgraph.xyz/?q=dhruv-chauhan%2Ffriend-tech-base (review changes on pending deployment)

New Subgraph Checklist

[x] Researched protocol / contracts
[x] Modeled off this template using the latest versions
[x] Updated title
[x] Added subgraph(s) to deployment.json
[x] Used standard subgraph libraries (if necessary/available)
[x] General aggregate metrics can be similar to known sources like the protocol or defi llama (The detailed QA will be done by a protocol specialist)
[x] Assigned the proper reviewers. If you are unsure, ask in our discord!
[x] Followed docs, especially WALKTHROUGH.md

https://thegraph.com/hosted-service/subgraph/messari/friend-tech-base

authors: dhruv-chauhan melotik

repo: messari/subgraphs


text:
Provided signature does not match calculated signature.

Hi,
I followed all the required steps, but I always got the error Processing of callback payload failed: Signature verification failed. Provided signature does not match calculated signature.

Hi,
please make sure that your configured App Secret matches the App Secret of your FB app (which is linked to your FB page).

Am 26.02.2017 um 19:55 schrieb Aboullaite Mohammed notifications@github.com:
Hi,
I followed all the required steps, but I always got the error Processing of callback payload failed: Signature verification failed. Provided signature does not match calculated signature.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

My bad. Thank you :)

authors: aboullaite maxgrabenhorst


text:
Audio not playing in Safari

I created a website using the minimal template you provided. The website works perfectly when used on Google chrome. But for some reason the avatar doesn't speak on Safari or on iPhone in any browser. I debugged the code the tts api key is retrieved from the proxy properly, the text is also going into head.SpeakText function. Console logs no errors. I checked if its apple that has some kind of restrictions, turns out they do have an autoplay limitation, but I specifically went to my safari settings and clicked on the option where all sites are now allowed to autoplay. But still I am facing that issue. Is there anything else that I can try ?

I am so embarrassed but I had my iphone's physical switch for silent on this whole time, spent like 5 hours trying out stuff and getting mad at Apple.

Btw, I have created my own portfolio using this, you can check it out at https://akshatrastogi.in
If you do like it, I'd love to get my website featured in your readme section.

No problem, these kinds of things happen to me all the time... 😀
I tried your app, and I really like the idea of having a personal portfolio where you can ask questions and explore topics that interest you the most. I'm happy to include it in my use case examples sometime later this week.

I just added your app to the use case examples. - I'll close this issue, but feel free to reply if you’d like to adjust the wording or suggest any other changes. Thank you for using the TalkingHead class!


text:
Clang Warning on macOS

🐛 Bug Report

clang: warning: argument unused during compilation: '-fuse-ld=gold' [-Wunused-command-line-argument]
View Full logs
7_Build.txt
Also here are the full CI logs on my own fork

Solved

repo: metacall/core


text:
User Experience Updates

Description
This PR:

Adds a $help functionality to check all available functions and commands on the MetaCall Kernel.
Refactors the $shutdown functionality to close the REPL subprocess.

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] This change requires a documentation update
[ ] Documentation update

Hello @HarshCasper! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file metacall_jupyter/kernel.py:

Line 267:80: E501 line too long (85 > 79 characters)
Line 268:80: E501 line too long (80 > 79 characters)
Line 269:80: E501 line too long (95 > 79 characters)
Line 270:80: E501 line too long (93 > 79 characters)
Line 271:80: E501 line too long (98 > 79 characters)
Line 272:80: E501 line too long (99 > 79 characters)
Line 273:80: E501 line too long (98 > 79 characters)
Line 274:80: E501 line too long (86 > 79 characters)
Line 275:80: E501 line too long (98 > 79 characters)
Line 277:80: E501 line too long (87 > 79 characters)

Hello @HarshCasper! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file metacall_jupyter/kernel.py:

Line 267:80: E501 line too long (85 > 79 characters)
Line 268:80: E501 line too long (81 > 79 characters)
Line 269:80: E501 line too long (95 > 79 characters)
Line 270:80: E501 line too long (93 > 79 characters)
Line 271:80: E501 line too long (98 > 79 characters)
Line 272:80: E501 line too long (99 > 79 characters)
Line 273:80: E501 line too long (98 > 79 characters)
Line 274:80: E501 line too long (86 > 79 characters)
Line 275:80: E501 line too long (98 > 79 characters)
Line 277:80: E501 line too long (87 > 79 characters)

repo: metacall/jupyter-kernel


text:
load ansible config not Ansible 2.4 compliant

Issue Type

Bug report

Molecule and Ansible details
ansible --version

2.4

molecule --version

master

Molecule installation method: source
Ansible installation method: pip

Actual Behaviour (Bug report only)
Unit tests fail with Ansible 2.4.
___________________________________________________________________ test_ansible_config_options_property_when_enabled ___________________________________________________________________

monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x1070ae4e0>, ansible_config = '/Users/jodewey/git/molecule_2/test/unit/provisioner/../../resources/ansible.cfg'
ansible_instance = <molecule.provisioner.ansible.Ansible object at 0x106bbaeb8>

    def test_ansible_config_options_property_when_enabled(
            monkeypatch, ansible_config, ansible_instance):
        monkeypatch.setenv('MOLECULE_INCLUDE_ANSIBLE_CFG', '1')
        monkeypatch.setenv('ANSIBLE_CONFIG', ansible_config)
        x = {
            'default': {
                'foo': 'bar',
            }
        }

>       assert x == ansible_instance.ansible_config_options

/Users/jodewey/git/molecule_2/test/unit/provisioner/test_ansible.py:119:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/Users/jodewey/git/molecule_2/molecule/provisioner/ansible.py:259: in ansible_config_options
    c, p = self._load_ansible_config_file()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <molecule.provisioner.ansible.Ansible object at 0x106bbaeb8>

    def _load_ansible_config_file(self):
>       return ansible.constants.load_config_file()
E       AttributeError: module 'ansible.constants' has no attribute 'load_config_file'

/Users/jodewey/git/molecule_2/molecule/provisioner/ansible.py:710: AttributeError
_______________________________________________________ test_ansible_config_options_property_when_enabled_but_missing_ansible_cfg _______________________________________________________

monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x106fa30f0>, ansible_instance = <molecule.provisioner.ansible.Ansible object at 0x106f9d278>

    def test_ansible_config_options_property_when_enabled_but_missing_ansible_cfg(
            monkeypatch, ansible_instance):
        monkeypatch.setenv('MOLECULE_INCLUDE_ANSIBLE_CFG', '1')

>       assert {} == ansible_instance.ansible_config_options

/Users/jodewey/git/molecule_2/test/unit/provisioner/test_ansible.py:126:

/Users/jodewey/git/molecule_2/molecule/provisioner/ansible.py:259: in ansible_config_options
    c, p = self._load_ansible_config_file()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <molecule.provisioner.ansible.Ansible object at 0x106f9d278>

    def _load_ansible_config_file(self):
>       return ansible.constants.load_config_file()
E       AttributeError: module 'ansible.constants' has no attribute 'load_config_file'

/Users/jodewey/git/molecule_2/molecule/provisioner/ansible.py:710: AttributeError
______________________________________________________________________________ test_ansible_config_to_dict ______________________________________________________________________________

monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x106fe6b38>, ansible_config = '/Users/jodewey/git/molecule_2/test/unit/provisioner/../../resources/ansible.cfg'
ansible_instance = <molecule.provisioner.ansible.Ansible object at 0x106fdb828>

    def test_ansible_config_to_dict(monkeypatch, ansible_config, ansible_instance):
        monkeypatch.setenv('ANSIBLE_CONFIG', ansible_config)
>       c, p = ansible_instance._load_ansible_config_file()

/Users/jodewey/git/molecule_2/test/unit/provisioner/test_ansible.py:871:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <molecule.provisioner.ansible.Ansible object at 0x106fdb828>

    def _load_ansible_config_file(self):
>       return ansible.constants.load_config_file()
E       AttributeError: module 'ansible.constants' has no attribute 'load_config_file'

/Users/jodewey/git/molecule_2/molecule/provisioner/ansible.py:710: AttributeError
_____________________________________________________________________________ test_load_ansible_config_file _____________________________________________________________________________

monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0x1067e9f98>, ansible_config = '/Users/jodewey/git/molecule_2/test/unit/provisioner/../../resources/ansible.cfg'
ansible_instance = <molecule.provisioner.ansible.Ansible object at 0x106bebf28>

    def test_load_ansible_config_file(monkeypatch, ansible_config,
                                      ansible_instance):
        monkeypatch.setenv('ANSIBLE_CONFIG', ansible_config)
>       c, p = ansible_instance._load_ansible_config_file()

/Users/jodewey/git/molecule_2/test/unit/provisioner/test_ansible.py:884:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <molecule.provisioner.ansible.Ansible object at 0x106bebf28>

    def _load_ansible_config_file(self):
>       return ansible.constants.load_config_file()
E       AttributeError: module 'ansible.constants' has no attribute 'load_config_file'

/Users/jodewey/git/molecule_2/molecule/provisioner/ansible.py:710: AttributeError
========================================================================= 4 failed, 503 passed in 20.52 seconds =========================================================================
ERROR: InvocationError: '/Users/jodewey/git/molecule_2/.tox/py36-ansible24-unit/bin/py.test -vv --cov-report=term-missing --cov=/Users/jodewey/git/molecule_2/molecule/ --no-cov-on-fail'

/cc @kharkevich

Hi,
I see that "load_config_file" was removed in following commit: https://github.com/ansible/ansible/commit/74842adc07edb248f9b544389ce4093b9149f195#diff-b77962b6b54a830ec373de0602918318
@retr0h do we need to provide backward compatibility or I can create patch with Ansible support > 2.4 only?

@retr0h do we need to provide backward compatibility or I can create patch with Ansible support > 2.4 only?

We should provide backward compatibility.

I opened an issue about ansible 2.4 compliance before seeing that you already have this one. I've already close it, but you may find useful information in it.

Hello
I updated both ansible and molecule with pip, ended up with ansible 2.4 and molecule 2.1, wich broke my test due to molecule generated inventory including &id001, $id001, ...
I thought I'ld just paste my error log, so people might end up here googling.
[WARNING]:  * Failed to parse /opt/ansible-playbooks/roles/rgarrigue.python/mo
lecule/default/.molecule/ansible_inventory.yml with ini plugin: /opt/ansible-pl
aybooks/roles/rgarrigue.python/molecule/default/.molecule/ansible_inventory.yml
:6: Expected key=value host variable assignment, got: &id001

[WARNING]: Unable to parse /opt/ansible-playbooks/roles/rgarrigue.python/molec
ule/default/.molecule/ansible_inventory.yml as an inventory source

[WARNING]: No inventory was parsed, only implicit localhost is available

I'm actually tempted reverting this work all together, which was implemented in #921.  I don't think many people actually use it, and was on the fence about it since the beginning.
Importing data from an outisde ansible.cfg seems like a recipe for weird bugs, when molecule.yml allows the config to be customized.

yes, @retr0h you can revert it. looks like that general 'ansible.cfg' for providing pass to libraries and so on use I only.

@kharkevich how long before you would have a fix?  Just curious.

@retr0h I have a fix and I test it internally. So, I'll hope that i fix it today.

@kharkevich I am likely going to put the breaks on this feature.  We can discuss further.  However, the feature mostly goes against the way we want to modify Molecule's ansible.cfg.  Especially b/c it can introduce weird bugs from an external ansible.cfg.  Since Molecule supports configuring it's own ansible.cfg from molecule.yml, I'm going to ask that we continue to use that method.'
Closing this particular bug since the functionality was reverted in #977.

@retr0h Ok, let's get back to discus in #956, because one case of using external ansible.cfg - using dynamic inventory

authors: alexppg kharkevich retr0h rgarrigue

repo: metacloud/molecule


text:
user-friendliness

Delivery of all parameters which can be changed like cutt-offs (e-Value, score, ...) and keywords as an Input for the Pipeline.
Default values if no parameter is set.

For this issue we first have to decide how and where we can define the parameters.
I suggest to use a YAML file that can be configured by the user.

Since we are using the nextflow configuration file, there is no need to use a YAML files.
In my opinion is the last step in order to close this issue, a short getting started section in the readme.

authors: pbelmann wpaetzold

repo: metagenomics/bioPipeline


text:
add: activate .venv

HT @pugio
Before running a command:

check if in an active venv, if yes run command as-is
check if there's a .venv nearby, activate it appropriately

Order of shells to support:

bash
fsh
powershell
cmd

Confirmed that adding a source .venv/bin/activate line before works.

repo: metaist/ds


text:
🌱 Add dependabot configuration

Add dependabot configuration

/test-ubuntu-integration-main
/test-centos-e2e-integration-main

/test-centos-e2e-integration-main

/test-centos-e2e-integration-main

/test-ubuntu-integration-main
/test-centos-e2e-integration-main

/test-ubuntu-integration-main
/test-centos-e2e-integration-main

/retest

/retest

/test-centos-e2e-integration-main

/test-centos-e2e-integration-main

/test-centos-e2e-integration-main

/test-centos-integration-main

/keep-test-centos-e2e-integration-main

/test-centos-e2e-integration-main

/keep-test-centos-e2e-integration-main

authors: kashifest lentzi90 mboukhalfa


text:
:bug: Fix broken images

Image paths were relative and this caused the website to look for the images in the wrong url. I changed the image paths it fixed the issue. Fixes #367

/approve

/lgtm

/cc @lentzi90

authors: Rozzii peppi-lotta tuminoid


text:
Fix error on range containing a single IP

Running MetalLB's e2e tests with the Operator returns an error:
admission webhook "addresspoolvalidationwebhook.metallb.io" denied the request:
Failed to parse addresses for test-addresspool1:
invalid CIDR "172.18.0.6-172.18.0.6" in pool test-addresspool1:
invalid IP range "172.18.0.6-172.18.0.6":
start IP "172.18.0.6" is after the end IP "172.18.0.6"

This was fixed by https://github.com/metallb/metallb/pull/1011
and should be here too.
Signed-off-by: Ori Braunshtein obraunsh@redhat.com

LGTM

authors: fedepaol oribon

repo: metallb/metallb-operator


text:
Do not enforce ban on "see" references to normative main clauses

In ISO, "see" is not meant to be used for references to normative bibliographic entries (ISO/IEC DIR 2 15.5.3), or cross-references normative annexes (ISO/IEC DIR 2 20.2). However there is no good evidence that this ban applies to normative clauses in the main section of the standard (which is all of them), and ISO/IEC DIR 2 uses "see" for references to main clauses all the time.
On the other hand, https://www.iso.org/ISO-house-style.html#iso-hs-s-text-r-s-informative states:

Unless there is a clear requirement (“shall”) or imperative language in the text, all document content is informative by default.

Right now, Metanorma assumes by default that document section content is normative, and it complains if "see" is used to cross reference any clause in the main section of the document. A rule saying "do not use see to reference normative clauses in the main part of the document is not explicit in ISO/IEC DIR 2 now; only annexes and external references are spoken about.
https://www.iso.org/ISO-house-style.html#iso-hs-s-text-r-r-ref_within says that "see is used for informative cross-references, but it implies that main section text can indeed be informative:

When referring to a specific element of the document, use only the element identifier (number or letter):
“…in accordance with Clause 7”
“…as shown in Figure 4”
“…the limits specified in Table 12”
“…the method described in Annex B”
“…calculated using Formula (5)”
“…fulfilling list items a) to d) in 8.4.5”
It is permitted to refer to an element informatively without making it part of the sentence:
“…the prepared sample (Figure 6)”
“…using the syntax (see Annex C)”

We know that Terms & Definitions are officially meant to be normative. But "See 3.4.1" for terms is used all the time, and that indicates that ISO does NOT follow the rule about normative references to a main clause.
We have the following alternatives:

Main clauses by default remain normative, complain about using "see" to reference them
Main clauses by default become informative, complain about using "see" to reference them if they are explicitly made normative (but "see 3.4.1" would still be an error, and I would need to change code to make terms and definitions normative explicitly)
Suppress the complaint about "see" to reference normative main clauses, since ISO does not seem to be following that rule itself.

The latter is my recommendation.

@ronaldtse for your decision
@manuelfuenmayor as discussed

@ronaldtse Reminder: this needs your decision.

What's the context here? What exactly is the problem?

Suppress the complaint about "see" to reference normative main clauses, since ISO does not seem to be following that rule itself. Not clear that the rule was ever intended to apply to main content anyway.

As you have pointed out, the "see" issue only happens to bib entries and annexes. ISO DIR 2 does not apply this check in the references to main content.
Let's get rid of this check for main content.

authors: opoudjis ronaldtse

repo: metanorma/metanorma-iso


text:
Exclude chem_mods and neutral losses from decoy selection

Changed decoy sampling so that chemical modifications and neutral losses won't be sampled from the list of possible decoy adducts.

@Bisho2122 I asked this not for myself, but for someone who will be involved in this project after us ;)


text:
specify start hour & minute

reduce instantaneous load by allowing start times specified to the minute

also allow for a 0 hour duration

repo: metatooth/herbert


text:
Improved Scroll UI usability

Is your feature request related to a problem? Please describe.
페이지 마다 스크롤 영역이 일관성이 없음

Describe the solution you'd like
[개선방안. 정책]

내용이 영역을 넘어갈때 스크롤이 생김
NOTE. 프랩의 데이터플로우 화면과 같은 외부 라이브러리를 사용할 때 특히 유의해 주세요.

화면의 메인 콘텐츠가 박스형인 경우, 화면 크기에 따라 박스 height 가변. 이때, 하단 마진 유지.
NOTE. 박스형 디자인은 데이터 그리드나 컬럼리스트와 같이 표시할 내용이 매우 많아질 수 있는 경우 사용합니다.
NOTE. 단, 박스 하단에 다른 입력 콤포넌트가 있을 경우, 박스의 Height를 min.사이즈가 있고 박스 내용에 따라 가변되도록함 (예.생성 마지막 단계 팝업)

헤더 영역이 사라졌을 때 혼선이 생길 수 있는 경우, 헤더 영역 유지.
NOTE. 테이블의 헤더. 타이틀 영역 등

참고페이지
https://tde.sktelecom.com/pms/browse/METATRON-1417
https://tde.sktelecom.com/pms/browse/METATRON-1226

@eltriny 제 기억으로는 다른 이슈로 인한 개선이 진행되는 화면부터 순차적으로 진행하기로 했던 것 같은데, 잊혀지고 있는 것 같습니다 ^^; 이건은 어떻게 처리하는게 효율적일까요?

@kyungtaak 네, 그렇게 하는게 좋을 것 같습니다. 페이지가 많아서 이슈 만들고, 각 화면 담당자 분들이 수고해 주셔야 할것 같네요

@eltriny 연관된 4개의 이슈를 확인해주시고요. 금번 Iteration 개발에 얼마만큼 포함이 될수 있을런지 확인 부탁드립니다.

authors: AnnieHwang kyungtaak minjung-cho

repo: metatron-app/metatron-discovery


text:
fn-fix_mdm_metadata_edit_error

Description

fix edit name and description not working if type is stagedb or database
Related Issue :

METATRON-3022
How Has This Been Tested?

1.Management-> Explore data -> Metadata
2. click list item
3. check edit name and description is working whatever metadata data type is
Need additional checks?
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.

Additional Context

run build
deploy to 6

run build
deploy to 2

@thinkcsww
The height and width of the textarea do not match the right button.

@ufocsw
2. what text should be displayed when there is no description value ? No description?
I check planning book but there is no guide.

@thinkcsww
If description is undefined, the same message as for empty value is displayed.
"No Description"

@ufoscw
Sorry, i misunderstood
Modified

run build
deploy to 2

@thinkcsww
Please check Korean resource bundle

@minhyun2
Modified

authors: kyungtaak minhyun2 thinkcsww ufoscw