Segfault on Windows 2.0.18 release for certain fonts/sizes

Over at pygame we got an issue report after updating to SDL_ttf 2.0.18 that rendering a font that previously worked segfaulted their program. It only seems to segfault at certain sizes.
I wanted to be sure this was a problem at the C level, and not an unrelated regression by pygame, so I put together a small test script.
#include "SDL.h"
#include "SDL_ttf.h"
#include <stdio.h>

int main(int argc, char *argv[])
{
    SDL_SetMainReady();
    SDL_Init(SDL_INIT_VIDEO);

    SDL_Window *window = NULL;
    SDL_Surface *screen = NULL;

    window = SDL_CreateWindow("Example", SDL_WINDOWPOS_UNDEFINED, SDL_WINDOWPOS_UNDEFINED, 500, 150, SDL_WINDOW_SHOWN);

    screen = SDL_GetWindowSurface(window);
    SDL_FillRect(screen, NULL, SDL_MapRGBA(screen->format, 0, 0, 120, 255));

    printf("running on patch level %i\n", SDL_TTF_PATCHLEVEL);

    TTF_Init();

    // font size 70 = segfault, 20 = fine
    TTF_Font* f = TTF_OpenFont("PlayfairDisplay-Regular.ttf", 20);
    printf("error=%s\n", SDL_GetError());

    SDL_Color white;
    white.r = 255;
    white.g = 255;
    white.b = 255;
    white.a = 255;

    //SDL_Surface *text = TTF_RenderText_Blended(f, "Hello world", white);
    SDL_Surface *text = TTF_RenderUTF8_Blended(f, "Hello world", white);
    printf("text=%p\n", text);
    printf("error=%s\n", SDL_GetError());

    SDL_BlitSurface(text, NULL, screen, NULL);
    printf("error=%s\n", SDL_GetError());

    SDL_UpdateWindowSurface(window);
    printf("error=%s\n", SDL_GetError());

    // Keep the main loop until the window is closed (SDL_QUIT event)
    int exit = 0;
    SDL_Event eventData;
    while (!exit)
    {
        while (SDL_PollEvent(&eventData))
        {
            switch (eventData.type)
            {
            case SDL_QUIT:
                exit = 1;
                break;
            }
        }
    }

    SDL_Quit();

    return 0;
}

Both pygame and my test script are compiled with Visual Studio, and use the 64 bit dev VS SDL_ttf 2.0.18 release. I tried to replicate this bug on my Mac, but I was unable to.
Running this in the VS debugger yields:
Unhandled exception at 0x00007FFDE6C723F6 (ntdll.dll) in SDL_c_test.exe: 0xC0000028: An invalid or unaligned stack was encountered during an unwind operation.
^ This pops up over the call to TTF_RenderUTF8_Blended
Call stack:

This hits the playfair family, at least regular and semibold (those are the ones I tested).
PlayfairDisplay-Regular.zip
I also tested this through pygame with all the system fonts pygame could detect, and got failures on the fonts
algerian, castellar, gigi, imprintshadow, blackadderitc, edwardianscriptitc, kunstlerscript
maturascriptcapitals, oldenglishtext, msoutlook, parchment, vivaldi, vladimirscript

I can't reproduce it on linux. also using some fuzzy test doesn't fail.

Can you add some debug flag to have more info ?
Printf the Surface width, height, pitch ?
Eventually replace "SDL_Surface *text = TTF_RenderUTF8_Blended(f, "Hello world", white);" by a dummy blank surface to make sure that SDL_ttf is really involved.

Sorry for the late response @1bsyl

Can you add some debug flag to have more info ?

I'm not sure how. I'm building the c code in debug mode, and running it in a debugger. I probably need an SDL_ttf with debug symbols, I'm just using the stock development DLL prebuilt. I've had difficulties before when I've attempted to build SDL_ttf from source in Visual Studio.

Printf the Surface width, height, pitch ?

The surface doesn't get created, it crashes somewhere in the render. Or perhaps something goes wrong in the TTF_OpenFont only at certain sizes, that is encountered when the program goes to render text.

Eventually replace "SDL_Surface *text = TTF_RenderUTF8_Blended(f, "Hello world", white);" by a dummy blank surface to make sure that SDL_ttf is really involved.

I did that, and the code worked.

I tried on window with my VisualC project and it runs fine. (this is visual studio 2017)
Build for x86 and also x64 for UWP
I use the latest dev source of SDL_ttf. and latest SDL dev source
Maybe put SDL_Log() instead of printf() because traces didin't appear

I use the latest dev source of SDL_ttf. and latest SDL dev source

Try using the SDL_ttf 2.0.18 VC development DLL. It's also specific to the font and size.

I tried you test case. eg font + size. So this should get reproduce.
Maybe  your SDL dll (not dll) isn't recent enough. I am not much familiar wit window. I suggest to try to rebuild SDL_ttf

I'll try.
I checked, my test case uses SDL 2.0.22.

Ok.
Really double check the dll sdl2 beacause this could silently fails if it
doesnt handle aligned memory
Le jeu. 19 mai 2022, 07:42, Charlie Hayden @.***> a
écrit :

I'll try.
I checked, my test case uses SDL 2.0.22.
—
Reply to this email directly, view it on GitHub
https://github.com/libsdl-org/SDL_ttf/issues/201#issuecomment-1131232349,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGH4KEKPCVVXPBOJ5VFWA3VKXIDVANCNFSM5VHP2LIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@1bsyl Yes!
With the SDL_ttf 2.0.19 DLL I built, the segfault goes away!
It is slightly different, because I built the DLL for x86 by mistake, and my previous tests were in x64, but that shouldn't matter (hopefully).
Do you SDL peeps want to do another SDL_ttf release soon? :smile:

I get the same "unaligned stack" exception described above when calling TTF_RenderUTF8_Blended. x64 debug and release builds crash. x86 builds seem to work as expected.
Using Visual Studio 2022, SDL2_ttf-devel-2.0.18-VC.zip, C++17;

@RageRocker I just tried it on my homemade SDL_ttf 2.0.19 DLL, x64, and it seems to be working.
Try slotting this guy in: (It's an x64 release build)
SDL2_ttf.zip

Okay, I found the ft_longjmp call that's problematic at font size 70. It's in ftgrays.c, line 616.

The official SDL_ttf DLL is built with mingw64, and it looks like there's an issue with setjmp/longjmp on 64-bit architecture:
https://stackoverflow.com/questions/53709069/setjmp-longjmp-in-x86-64-w64-mingw32

And a workaround:
https://web.archive.org/web/20170110124635/http://www.agardner.me/golang/windows/cgo/64-bit/setjmp/longjmp/2016/02/29/go-windows-setjmp-x86.html

The official SDL_ttf DLL is built with mingw64

Even the MSVC release? (That's the one I was using, specifically SDL2_ttf-devel-2.0.18-VC

Yep, it's just the official SDL_ttf DLL with Visual Studio import libraries.

The good news is, I can reproduce this, so I can see if the workaround is viable.

Should this be a patch to freetype when compiled in Mingw?

I built with a newer mingw64 compiler, and it looks like this may have been fixed.
Can you try this DLL?
https://www.libsdl.org/tmp/SDL2_ttf.zip

Yes, that works!
To get it building I used the .lib file I had around from my build of SDL_ttf. (If that matters, which it probably doesn't)

Great, thanks!

I'll leave this issue open for verification with the final 2.20.0 release candidate build.
Thanks!

I've verified this against the SDL_ttf 2.19.2 MSVC development prebuilt.

Great, thanks!


Passwords are saved as plaintext

When "remember password" is checked, the password is saved in plaintext (64-bit encoded) with no encryption in dep.dat

Yeah, I'm not really sure how to handle that. Do you have any recommendations?

@willsherwood Wow, I did not know that the encoding was just 64-bit encoding. This could simplify the encoding/decoding.


[BUG]: Set Default Item for Nav Control

Describe the bug
Cannot select a default item for a Nav control.
To Reproduce
Steps to reproduce the behavior:

Add Nav control to screen
Create variable to use for SelectedKey property (ex. ctxSelKey)
Set Nav control SelectedKey property to variable, ctxSelKey
Set variable, ctxSelKey, to default key value

Expected behavior
With SelectedKey variable set to a default key, when Nav is shown the Item with the Key value = to the SelectedKey value will be selected.
If this is not how this is supposed to work, please provide an example showing how to set the default selection in a Nav control.
Screenshots
N/A
Additional context
I tried creating an InputEvent for SetFocus, SetFocusOnRowSetSelection and SetSelection. The documentation only shows that the Nav Control supports the SetFocus InputEvent. None of these worked.

I was able to figure out the issue. The problem with the Nav control is the ItemKey must be Text. It cannot be numeric. I would still classify this as a bug because keys are usually numeric for performance reasons.
Is this working by design?


test: repair the custom_derivative test

The test imports the C library for the math library.  Add a case for
Windows.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @marcrasi @dan-zheng @ematejska

@swift-ci please smoke test


How to output the loss after/during training?

During the training, relevant progress, loss, and val metrics information will be output on the console and fit() will returns a tuple (Model, History) object after training,  History contains loss information.


Make compatible with cvxpy 1.3

I made cvxpygen compatible with cvxpy 1.3 in the most straightforward way I could. I think the generate_code function could be organized a bit more cleanly by breaking it into multiple functions, but that's a topic for a different PR.
Fixes #10

I also had a bit of trouble running tests locally.

I had to play around with installation a lot to get things working on ubuntu CI. In the end the main thing was switching from conda install to pip install. It's possible that some changes, such as removing version bounds for pybind11 and cmake, were not necessary.

Thanks @PTNobel !


styling: Changes font

Changes font to Robot light
and integrates it locally
closes https://github.com/inveniosoftware/invenio-app-rdm/issues/236

@jrcastro2 Can I ask you to check if your PR possibly closes this one: inveniosoftware/invenio-theme#171


Find/Add thumbnail images

Find images, then crop and add them to the imgs folder. I'll do this Tues night.

This appears to be done, we have a large list of images to choose from for the components.


Bug: Fix Zora contract call

What changed? Why?
Fix Zora contract call.

Changing value: parseEther('0.000777') to value: parseEther('0.000111')
Separating mintContractAddress with collectionAddress

Notes to reviewers
How has it been tested?

Can you make sure CI pass, please.

@cpcramer can you help @fakepixels get the CI passing.

Closing this, as this work was covered by @abcrane123


Dominant Piranha problem of contest 1433/Q.C on codeforces

Aim

A problem that requires greedy method and constructive algo to be solved

Details

I have solved the code in C++ and it will add value to the project

Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python

no need for competitive programming questions only ds algo questions @Saup21


Way to find convert agent position to maze coverage

Hi,
For the maze environments, I'm interested in converting an agent's (x, y)-position into what cell of the maze they are located so I can easily compute the percentage of the maze the agent has explored.
In the code, I saw that each maze environment has its own representation i.e.:
U_MAZE = \
        "#####\\"+\
        "#GOO#\\"+\
        "###O#\\"+\
        "#OOO#\\"+\
        "#####"

but what I haven't been able to find are the centers of each of the open positions and their corresponding height and width (for both the point maze and ant maze).
Thanks!

sorry, I double posted the issue

sorry, I double posted the issue


CentOS reboots when trying full screen with Ctrl+Alt+Enter

Environment:
~]$ cat /etc/centos-release
CentOS Linux release 7.7.1908 (Core)
~]$ xfreerdp /version
This is FreeRDP version 2.0.0-rc4 (n/a)
Command to launch:
~]$ xfreerdp /u:User /v:win-machine9 /gd:networks '/p:Password'
The new window is launching properly. When I try to get a full screen of the window using Ctrl+Alt+Enter then the user in the system gets logged off and redirected to the CentOS login page as a new boot. All running applications were killed.

I´d check the local key bindings of your WM. Sounds a lot like there is a mapping for what you see.

No feedback, closing.

oops, sorry, wrong issue ^^


Prevent predictable tokens in certain setups

Predictable random number generators could result in session takeover, since the auth cookies could be guessed.
mcrypt_create_iv will fall-back to insecure RNG if there's no /dev/urandom available.
(It would actually be better if this function would crash instead of falling back...)

This is a good improvement, thanks!


https://www.instagram.com/radar_sari_00/?hl=tr

We have written the needed data into your clipboard because it was too large to send. Please paste.

Duplicate of #


[AST] Fix comment merging

toRawComment takes a range of line/block ordinary/doc comments and
converts them into a RawComment that should represent the doc comment
for the attached decl.
Fix a bunch of unhandled cases:

A prior comment with whitespace in between would cause the first
line of the next comment to be missed
Multiple block comments would all merge rather than picking the last
A gyb comment would attach the prior comment, regardless of
whitespace inbetween

Resolves rdar://82414210

@swift-ci please test

Note that there's some functionality change here - block comments are no longer merged. This makes sense to me, but let me know if you disagree.

Build failed
Swift Test Linux Platform
Git Sha - 789d7e6bbf453fd6b227daab47ccd900d6783224

Build failed
Swift Test OS X Platform
Git Sha - 789d7e6bbf453fd6b227daab47ccd900d6783224

(Could clean up SR-6605 that I, er, abandoned)

(Could clean up SR-6605 that I, er, abandoned)

Oh thanks! It does indeed fix SR-6605 :). I'll also add a comment in there (I checked the source compatibility suite for instances of comments with a newline between + mixing block and line).

@swift-ci please test

I had a look at the source compatibility suite and there's no case where we'd want to merge blocks (mixed or otherwise) or comments with a newline in-between. Not merging is marginally better since it does fix a few cases, so I've gone ahead and modified the tests to reflect that.
So note that the behaviour is now:

Merge consecutive /// comments together
Only keep the last consecutive block of /// or the single /** */ comment (ie. do not merge block comments)

This is a little different to the Clang side, which does keep consecutive comments (including mixed), hence only the offset/length change in test/SourceKit/InterfaceGen/gen_clang_module.swift.response  - the full comment is still printed, but we only keep the last one.
There's no instance of multiple block doc comments in a row or mixed block/line, so I could be convinced to keep that if anyone thinks it's worth it. Not supporting that case makes the code slightly simpler and easier to understand though.
@rintaro @johnfairh

Build failed
Swift Test Linux Platform
Git Sha - aa8968168c0cffd20a40cb5ba44fb4640e191240

Build failed
Swift Test OS X Platform
Git Sha - aa8968168c0cffd20a40cb5ba44fb4640e191240


How can we exclude or include other Enterprise app registrations

We have a application which pulls data out of Exchange and SharePoint.
In this application we want to see that information. If we enforce CA with e.g. MFA on EXO and SP, this info is not displayed.
How can we exclude or include our Enterprise app registration for the "Late-bound" enforcement?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7834fc25-6e4d-1a00-e9d3-949928ccb94b
Version Independent ID: 23e71a83-28ea-da6f-0e3e-cda56a320358
Content: What are service dependencies in Azure Active Directory Conditional Access?
Content Source: articles/active-directory/conditional-access/service-dependencies.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@Laho19
Thanks for your feedback! We will investigate and update as appropriate.

@Laho19 Apologies for the delay on this one. Here is the udpate -
Late-bound enforcement occurs when the application requests a token from Azure AD in order to access the downstream service (e.g. SPO and EXO), for example when it requests an access token to invoke the Microsoft Graph API endpoints for SPO and EXO. If the application is using the MSAL library this is handled automatically as explained here, the MSAL library will request a token to Azure AD and the response is going to contain information that MSAL will use to prompt the user to login again and request MFA if necessary.  Also, the application can have the user consent upfront for accessing different resources (e.g. SPO and EXO) so that the user logins only once, the process is described here. If the application is not using MSAL then this flow needs to be handled manually based on the token request responses from Azure AD.

@Laho19 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


pod 'Realm', '~> 0.102.1'

I mentioned a few years ago that I was stuck on v0.102.1: https://github.com/realm/realm-cocoa/issues/3879
I have now finally got a computer fast enough to run Xcode 7.3. (Previously max was 7.2 due to macOS Yosemite support being dropped).
Is it easy for me to upgrade to the latest version of REALM (or a later version) with minimal code changes given I need to deploy  and get app approval within the next few days.

@stel @bdash @JadenGeller

Please don't ping random people on GitHub issues. It is rude.
If I understand correctly, you're asking if it'll be easy to update from a pre-1.0 version of Realm using Xcode 7.x to a current version of Realm that requires Xcode 8.3 or greater. It's certainly doable, but as the version number implies there have been a number of API changes in that time period. You can learn about these API changes by reading over our release notes. It's impossible to know whether they'll affect you, and how much work adapting to them will take. The only way to find out would be to update and see what problems you run into.

Thank you for response. I appreciate that.
But please don't pretend that the social conventions have been unambiguously established yet in terms of GitHub etiquette. You were not ransom because you responded to my prior issue which I linked to above.


[AVM Module Issue]: New parameter for virtual-network-link

Check for previous/existing GitHub issues

[x] I have checked for previous/existing GitHub issues

Issue Type?
Feature Request
Module Name
avm/res/network/private-dns-zone
(Optional) Module Version
0.6.0
Description
Hello everyone
I don't know if you are already adding preview features. We have the problem with Private DNS zones, which can be solved with the new feature: resolutionPolicy
More info:
https://learn.microsoft.com/en-us/azure/dns/private-dns-fallback
I hope you find time to implement it soon.
(Optional) Correlation Id
No response

@alphasteff - Apologies for the delay, a fix is in PR now.


Atemori-deck-tool

merge compilation from origen sorce to cloned sorce

requesting merge from old code base to updated code base


Please add Null Safety.

Can you add Null Safety please and thank you!

News about this, @rohansohonee? It would be amazing. :D

Hi
You check this PR #6 and implement the changes as described in my comment. "NOTE: I have not tested this."
I am not maintaining this project at the moment. I will update the README file and refer to another package which already provides equalizer functionality and is available for iOS platform.
See https://github.com/ryanheise/just_audio/issues/147


Request to provide a clear documentation for CA rotation for those who want to do it

This is a Bug Report

Problem: There is no documentation for CA rotation, kubernetes does not supports it through kubeadm and it is also not documented anywhere.
Issue link: https://github.com/kubernetes/kubeadm/issues/2027
Proposed Solution:
I tried and successfully rotated the CA manually, there are some issues with kubelet which I am working but otherwise I was able to rotate the CA.
Steps recorded in https://github.com/kubernetes/kubeadm/issues/2027. If this is not the right way, I would say help me and other people who would want to do it.
For example, my organization has a mandate to rotate CA every year and if this is documented somewhere, it would be a big help for people me and everybody using kubernetes.
Page to Update:
https://kubernetes.io/docs/tasks/tls/certificate-rotation/

Kubernetes Version: v1.16.x and v1.15.3
Additional Information:
The documentation should be a separate page references in https://kubernetes.io/docs/tasks/tls/certificate-rotation/ somewhere, so that people can actually make use of it.
This issue https://github.com/kubernetes/website/issues/18169 has some information but it is not very much related to CA rotation.

/sig auth

@abhiTamrakar as pointed out earlier, it would be best to notify SIG Auth on their slack channel or zoom meeting about this ticket.

@neolit123 Yes sure, will do that.

Is this also /sig cluster-lifecycle?

Is this also /sig cluster-lifecycle?

ideally the documentation for CA rotation should be deployer agnostic (e.g. not being a guide for kubeadm).

I was thinking about cluster lifecycle in general per https://github.com/kubernetes/community/blob/master/sig-cluster-lifecycle/charter.md#sig-cluster-lifecycle-charter rather than specifically about kubeadm.

@sftim It should be a part of cluster lifecycle as certificates would anyways be a part of it, irrespective of the individual segregation of entities.

I was thinking about cluster lifecycle in general per https://github.com/kubernetes/community/blob/master/sig-cluster-lifecycle/charter.md#sig-cluster-lifecycle-charter rather than specifically about kubeadm.

it's certainly not in the SIG Cluster Lifecycle charter to own this space or to document it.
so it's up to SIG Auth to drive this and CL can give feedback.
/sig cluster-lifecycle

I'd like make a PR documenting how to do this.

preventing it from rotting, since the PR is WIP
/remove-lifecycle stale

/assign @abhiTamrakar

the document merged
https://github.com/kubernetes/website/pull/19351
https://github.com/kubernetes/website/pull/21651
/close


Integrate Hero Version: Disable usage of hardlinks, but allow enabling via settings

Changelog Description
Integrate Hero Version: Disable usage of hardlinks, but allow enabling via settings
Additional info
There are 'known issues' with hardlinks on Windows where Windows disallows deleting any of the links if ANY of the files are in use. As such, when e.g. hero version and latest v010 publish are hardlinked, a machine actively has v010 in use (e.g. on renderfarm) and we try to delete an swap the hero version with a v011 hardlink when publishing a new version then Windows disallows the removal of the hero version's files - even if actually that particular file isn't in use.

Historically there have been issues with hardlinks when publishing looks. More details scattered across:

https://github.com/ynput/OpenPype/pull/2986
https://github.com/ynput/OpenPype/issues/879
https://github.com/ynput/OpenPype/issues/2970
https://github.com/ynput/OpenPype/issues/5342
https://github.com/ynput/OpenPype/issues/925#issuecomment-1011961476
https://github.com/ynput/OpenPype/issues/3805#issuecomment-1240717042

And yes, hardlinks have bitten our asses before as you can see.
Testing notes:

Integrating hero version should not use hardlinks by default
Setting to enable hardlink usage should work.

On Windows you should be able to 'detect' hardlinks using fsutil hardlink:
fsutil hardlink list MyFileName.txt

just to show different ways of finding the hardlinks on Windows
fsutil hardlink list <fileName>

using Linux subsystem on Windows
 find . -links +1

Not sure how to approach this PR and its testing... could you elaborate more on exact testing steps pls?
I was trying to render animation on DL and also publish animation products while rendering and never happened to me that hero version integration failed (tested outside of this PR). So Im not sure how I should prove this PR fixes something.
So more elaborate test steps might help me a lot...thx

Not sure how to approach this PR and its testing... could you elaborate more on exact testing steps pls?
I was trying to render animation on DL and also publish animation products while rendering and never happened to me that hero version integration failed (tested outside of this PR). So Im not sure how I should prove this PR fixes something.
So more elaborate test steps might help me a lot...thx

The bug the client is facing may be hard to reproduce - I think the best test for you here, outside of their production enviromment, is to ensure the setting does what it is intended to do and that is "choose" between writing hero versions as hardlinks or regular copies.
So I suppose, with the setting on and off do a few hero publishes, all should work fine.
Then each time check whether the files are hardlinks or not - using e.g. the techniques @m-u-r-p-h-y showed in the screenshots (for which a windows variant is also in the testing notes). Those will have to be done through command line most likely since I don't know a way on windows to detect whether a file is hardlink or not without command line.

...it seems that the Use Hardlinks knob does not have any effect atm

@LiborBatek your  test screenshot with the forcing copy versus hardlink seems to be for Look publishing from Maya - which is unrelated to this PR. The only thing this PR changes is the Integration of Hero Versions
Then, the logic currently will always report it's copying the file instead of reporting it's hardlinking - which may be confusing since you then can't really check the log but must check the files on disk itself to confirm whether it hardlinked or not. I've changed that with https://github.com/ynput/ayon-core/pull/678/commits/0ab3653f360e530402d17bc1c78fbeea4f2cd9fd
It should now debug log "Hardlinking file {source} to {destination}" if hardlink is enabled for Integrate Hero Versions and will debug log "Copying file {source} to {destination}". If for whatever reason the hardlink failed and it falls back to copying the file it will now debug log that as well.

Test run on my side. Setting enabled:
// pyblish.IntegrateHeroVersion : Hardlinking file "C:\projects\ayontest\asset\char_hero\publish\pointcache\pointcacheMain\v022\ynts_char_hero_pointcacheMain_v022.abc" to "C:/projects/ayontest/asset/char_hero/publish/pointcache/pointcacheMain/hero/ynts_char_hero_modeling_hero.abc"

Setting disabled:
// pyblish.IntegrateHeroVersion : Copying file "C:\projects\ayontest\asset\char_hero\publish\pointcache\pointcacheMain\v023\ynts_char_hero_pointcacheMain_v023.abc" to "C:/projects/ayontest/asset/char_hero/publish/pointcache/pointcacheMain/hero/ynts_char_hero_modeling_hero.abc"

should not the hardlinking be more generic setting (the storage either supports it or not)
having this option scattered across different families and DCCs does not sound right to me.
The solution should not be part of this PR just thinking aloud . . .

should not the hardlinking be more generic setting (the storage either supports it or not)
having this option scattered across different families and DCCs does not sound right to me. The solution should not be part of this PR just thinking aloud . . .

I understand your point. But at the same time I don't see an issue with a studio wanting looks to NOT be hardlinked, but hero versions they want. Which is a customization option you would lose then. These are now two options - that's not too bad. If this was scattered all over for 10s of options.
It could be worth a separate issue if you think it's very problematic in design currently.


interface.h/cpp: add QWebEnginePage implementation

This adds implementation for QWebEnginePage methods.
For more information about new methods, see ROADMAP.org.

Looks good to me!  Could you test this, at least in C?

Could you test this, at least in C?

Sure! I will test it in C right away.

Adding to that, is webEnginePageRunJavaScript() done on your local branch? If so, please push it to be in line with ROADMAP :)

Adding to that, is webEnginePageRunJavaScript() done on your local branch?

webEnginePageRunJavaScript() had already been implemented in cl-webengine, just not marked as done in the ROADMAP file.

Could you test this, at least in C?

I successfully tested the functions in C++ and some functions in C. However, it is impossible to create a C test for all of them now because the following functions:

webEnginePageTriggerAction()
webEnginePageAction()
webEnginePageHistory()
webEnginePageSetUrlRequestInterceptor()

require the implementation of additional classes, namely, QAction, QWebEngnineUrlRequestInterceptor, QWebEngineHistory for testing. I see two solutions to this situation. The first one is to merge only tested functions now and add others after implementing mentioned classes. The second is to merge both tested and untested functions and then start working on implementing the classes.
What do you think about it? Do these ideas make sense?

Adding to that, is webEnginePageRunJavaScript() done on your local branch?

webEnginePageRunJavaScript() had already been implemented in cl-webengine, just not marked as done in the ROADMAP file.

Oh, sorry for that, I forgot we've got it :sweat_smile:

Could you test this, at least in C?

I successfully tested the functions in C++ and some functions in C. However, it is impossible to create a C test for all of them now because the following functions:
* webEnginePageTriggerAction()

* webEnginePageAction()

* webEnginePageHistory()

* webEnginePageSetUrlRequestInterceptor()

require the implementation of additional classes, namely, QAction, QWebEngnineUrlRequestInterceptor, QWebEngineHistory for testing. I see two solutions to this situation. The first one is to merge only tested functions now and add others after implementing mentioned classes. The second is to merge both tested and untested functions and then start working on implementing the classes.

Let's merge this and get to QWebEngineHistory and QAction afterwards.

Thanks a lot!


Bump-up Ruff to version 0.4.10

Description
Bump-up Ruff to version 0.4.10
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[x] Bump-up library or tool used for development (does not change the final image)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (main@5b1ea99). Learn more about missing BASE report.
Report is 29 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1126   +/-   ##
=======================================
  Coverage        ?   95.44%
=======================================
  Files           ?       56
  Lines           ?     2371
  Branches        ?        0
=======================================
  Hits            ?     2263
  Misses          ?      108
  Partials        ?        0

/lgtm

/approve


Make collection display metadata mutable, add update-collection CLI command

Work towards #117

Closing in favour of #130


docs: ADR to expose all SCSS variables that MFEs use as CSS variables [BB-6307]

Description
Adds an ADR for a plan to expose all Bootstrap variables used by Paragon and MFEs as CSS variables.
Deploy Preview
NA
Merge Checklist

[x] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[ ] Does your change adhere to the documented style conventions?
[x] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[x] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[x] Were your changes tested in the example app?
[x] Is there adequate test coverage for your changes?
[x] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @xitij2000!  Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

I've created a starting implementation draft PR for this.

@xitij2000 Even though your pull request wasn’t merged, please take a moment  to answer a two question survey so we can improve your experience in the future.


Since today no metrics

Since today there are no metrics in HA, i noticed that there is a captcha on apsystemsema server in browser, this is a change from yesterday.
Log HA:
Logger: homeassistant.helpers.entity
Source: custom_components/apsystems/sensor.py:241
Integration: apsystems (documentation)
First occurred: 07:32:28 (100 occurrences)
Last logged: 09:07:34
Update for sensor.apsystems_energy_day fails
Update for sensor.apsystems_energy_latest fails
Update for sensor.apsystems_power_max_day fails
Update for sensor.apsystems_power_latest fails
Update for sensor.apsystems_date fails

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 487, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 691, in async_device_update
raise exc
File "/config/custom_components/apsystems/sensor.py", line 146, in async_update
ap_data = await self._fetcher.data()
File "/config/custom_components/apsystems/sensor.py", line 252, in data
await self.run()
File "/config/custom_components/apsystems/sensor.py", line 241, in run
self.cache = result_data.json()
File "/usr/local/lib/python3.9/site-packages/requests/models.py", line 910, in json
return complexjson.loads(self.text, **kwargs)
File "/usr/local/lib/python3.9/site-packages/simplejson/init.py", line 525, in loads
return _default_decoder.decode(s)
File "/usr/local/lib/python3.9/site-packages/simplejson/decoder.py", line 370, in decode
obj, end = self.raw_decode(s)
File "/usr/local/lib/python3.9/site-packages/simplejson/decoder.py", line 400, in raw_decode
return self.scan_once(s, idx=_w(s, idx).end())
simplejson.errors.JSONDecodeError: Expecting value: line 5 column 1 (char 4)

Same here I can not see any sensor

Looking into it and seems to be a fault at their end... but looking on into it....
We are so sorry, EMA has encountered an error.click [OK] to email us and we will deal with it within 48 hours. Please re-login
your system.

Where to press OK? yesterday it seems to work
apsystems: Error on device update!

well the short answer is, that this is now dead... i can't login without a code and i can't get the code from the image in any easy way.... i will mail them and ask if there is any other way to login and get that info from their site, so that home assistant still can get the data... but else i can't see another way at current....

well the short answer is, that this is now dead... i can't login without a code and i can't get the code from the image in any easy way.... i will mail them and ask if there is any other way to login and get that info from their site, so that home assistant still can get the data... but else i can't see another way at current....

I’m sorry to hear that. This was such a great component. Let’s hope apsystems shows some interest and tries to help us.

well i have found a new way to login, now i just need to get it to work... i'm not a python coder, so i have to learn the python ways todo it... but working on it...

thanks skelgaard for invest, i am familar with shell script but not python and try to follow your work an try to understand

i have gotten it work now, just need homeassistant to play along :) still working on it

i have data on my graph again... i will make the changes to the config and make sure all that working and expect a new release later today that works again

version 1.0.5 has ben pushed with a fix for this.. please say if it works for you too...

Hi, 1.0.5 failed:
Logger: homeassistant.config
Source: config.py:454
First occurred: 14:09:17 (1 occurrences)
Last logged: 14:09:17
Invalid config for [sensor.apsystems]: [username] is an invalid option for [sensor.apsystems]. Check: sensor.apsystems->username. (See /config/configuration.yaml, line 67). Please check the docs at https://github.com/skelgaard/homeassistant-apsystems/blob/master/README.md

disable your config in your yaml file, restart, enable config in yaml with authid ,restart working

if still have problems, i'm on the home assistant discord for help :)

Yeah!
Have not noticed to change the config params, now it works!
Thanks a lot, where ist the "spent a coffee" button?

its comming :)

"Not working at current" from the main page is outdated.

and, today, the captcha on apsystemsema.com is gone

removed :)

i have seen its gone, but i'm guessing that it will return at some point... so i'm not going to change it back to use username/password... but i may make it an option that can be selected to use that or the authid at some point.

yes, i guess they test and check the acceptance, authid would the save way if they dont change that


Fix Travis post-browserify

Heya @jhilde @pauledwardmitchell! FYI for devs on the project -- we added Browserify-rails to let us do import and export on our cool ES6 JS. Things will break for you when you pull down these changes but then running npm install should fix everything. The first time you try to start a rails server locally it will be reaaaaally slow as Browserify builds up a cache.

👍

Groovy. Thanks @alexsoble


Remove nsenter hack for kubelet

There is a hack for kubelet where it uses nsenter to use the host's mount point. It seems we don't need it anymore.

FYI: https://github.com/kubernetes/kubernetes/issues/4869#issuecomment-237472754
This seems to be the current state of kubelet in docker without nsenter.

I think kubelet wrapper has been cleaned up in coreos since that comment - https://github.com/coreos/coreos-overlay/blob/master/app-admin/kubelet-wrapper/files/kubelet-wrapper
rkt has support for DNS configuration and kubelet-wrapper is riding on top of it - https://coreos.com/rkt/docs/latest/networking/dns.html

In general do we want to sur rkt for k8s components as default ? #784
Rkt is wrapper around systemd-nspawn and also works to well to manage kubelet
I feel confortable to use it a primary container-engine for kubelet/etcd
what do you think?

I'm not opposed to it

Funny story; our team already put together the patches to optionally run etcd and kublet under rkt and were talking about upstreaming those today. :smile:

@cheuschober that's just great. Looking forward for a PR! :)

Hey guys
Is this going to be optional or mandatory?
I know the CRI work will enable multiple container engines...But I would
request to not move away from Docker in the short term. Docker has
security,hipaa certification programs that would be important for us.
http://www.cloudera.com/about-cloudera/press-center/press-releases/2016-12-19-cloudera-and-docker-partner-to-vastly-improve-the-security-of-data.html
On Dec 20, 2016 20:24, "Chad Heuschober"<EMAIL_ADDRESS>wrote:

Funny story; our team already put together the patches to optionally run
etcd and kublet under rkt and were talking about upstreaming those today.
😄
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/kargo/issues/776#issuecomment-268263039,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEsU-tt2tXyL26SYOHuIeKb_PogAiPSks5rJ-wugaJpZM4LQjxa
.

Also, this bug is not tied to rkt. Docker imho removes the need for nsenter
(except for already running containers)
On Dec 20, 2016 9:55 PM, "Sandeep"<EMAIL_ADDRESS>wrote:

Hey guys
Is this going to be optional or mandatory?
I know the CRI work will enable multiple container engines...But I would
request to not move away from Docker in the short term. Docker has
security,hipaa certification programs that would be important for us.
http://www.cloudera.com/about-cloudera/press-center/press-
releases/2016-12-19-cloudera-and-docker-partner-to-vastly-
improve-the-security-of-data.html
On Dec 20, 2016 20:24, "Chad Heuschober"<EMAIL_ADDRESS>wrote:

Funny story; our team already put together the patches to optionally run
etcd and kublet under rkt and were talking about upstreaming those today.
😄
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/kargo/issues/776#issuecomment-268263039,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEsU-tt2tXyL26SYOHuIeKb_PogAiPSks5rJ-wugaJpZM4LQjxa
.

I believe that should be a opt-in inventory var, false by default (i.e. docker for all). Later we could push that to true and add another one for k8s workloads as well.

@sandys the Idea here is not to switch the containe-engine/cri to rkt,.
but to run the the super privileged containers with rkt (aka kubelet)

Hi Antoine
It doesn't matter - certification can't be for one container versus
another. It has to be for the full deployment.
May I request that the rkt switch be discussed in a separate bug and issue
? It has far greater implications than just eliminating nsenter for DNA
resolutions.
I strongly believe that kargo should not switch but enable the CRI
mechanism to allow end users to choose their own runtime.
On Dec 20, 2016 10:18 PM, "Antoine Legrand"<EMAIL_ADDRESS>wrote:

@sandys https://github.com/sandys the Idea here is not to switch the
containe-engine/cri to rkt,.
but to run the the super privileged containers with rkt (aka kubelet)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/kargo/issues/776#issuecomment-268294228,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEsU-2uPCEmndhXPf9KL5lHC4HnReoGks5rKAbVgaJpZM4LQjxa
.

#784 adds in flags to specify the type of deployment ( docker vs rkt ) and defaults to docker.

I do agree it's probably worthwhile taking the discussion to https://github.com/kubernetes-incubator/kargo/pull/784

@sandys CRI is a good option for k8s workloads only, not for the etcd and kubelet containers, unless self-hosted, right? Also I'm skeptic regarding to the ops impact, specifically on RPC failure modes that it brings in.

@bogdan - you may be right .. although the general thought is that CRI is
meant to be a drop in replacemnt.
But I agree with your concern nevertheless - but then I would also say that
moving to rkt is a hasty decision and should NOT be part of this bug. The
feature sets for rkt and docker are on par atleast for this nsenter vs
resolv.conf issue. Both of them mount in the same way and both have the
same issues with running containers not updating.
On Wed, Dec 21, 2016 at 4:15 PM, Bogdan Dobrelya<EMAIL_ADDRESS>wrote:

@sandys https://github.com/sandys CRI is a good option for k8s
workloads only, not for the etcd and kubelet containers, unless
self-hosted, right? Also I'm skeptic regarding to the ops impact,
specifically on RPC
http://blog.kubernetes.io/2016/12/container-runtime-interface-cri-in-kubernetes.html
failure modes that it brings in.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/kargo/issues/776#issuecomment-268492434,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEsU_KgokWdCHydfgyghctt6-JR8GzRks5rKQNEgaJpZM4LQjxa
.


[Python] Tracecontext OTel propagator config generates an additional X-Ray span

I am using v1.3.0 of the Python layer and configured the lambda to use tracecontext propagation, but I can see the lambda reporting an additional extra span that seems to be related to X-Ray, which shouldn't be there.
Notable additional config:
    OTEL_PROPAGATORS: "tracecontext"
    OTEL_TRACES_SAMPLER: "Always_On"

Lambda tracing is turned off (PassThrough).
Code:
def consumer(event, lambda_context):

    context = extract(event['headers'])

    # Create top level transaction representing the lambda work
    with tracer.start_as_current_span("consumer-function-top-level", context=context, kind=SpanKind.SERVER):

        # Some other internal work performed by the lambda
        with tracer.start_as_current_span("consumer-function-some-internal-work", kind=SpanKind.INTERNAL):

            time.sleep(1)

        time.sleep(0.5)

    return {'statusCode': 200}

This should produce 2 spans: top-level consumer-function-top-level and nested consumer-function-some-internal-work. Instead, I am seeing 3 spans created in CloudWatch log with Span 2 065c07aa6cc4916d that shouldn't be there:

2021-07-24T04:36:51.316Z	INFO	loggingexporter/logging_exporter.go:41	TracesExporter	{     "#spans": 3 }
--
2021-07-24T04:36:51.316Z	DEBUG	loggingexporter/logging_exporter.go:51	ResourceSpans #0
Resource labels:
-> telemetry.sdk.language: STRING(python)
-> telemetry.sdk.name: STRING(opentelemetry)
-> telemetry.sdk.version: STRING(1.3.0)
-> cloud.region: STRING(ap-southeast-2)
-> cloud.provider: STRING(aws)
-> faas.name: STRING(aws-python-api-worker-project-dev-consumer)
-> faas.version: STRING($LATEST)
-> service.name: STRING(aws-python-api-worker-project-dev-consumer)
InstrumentationLibrarySpans #0
InstrumentationLibrary handler

Span #0
Trace ID       : ac4d7110c6d22e985b5db28e8ecca769
Parent ID      : 3c374013084a679c
ID             : 522890b38766e922
Name           : consumer-function-some-internal-work
Kind           : SPAN_KIND_INTERNAL
Start time     : 2021-07-24 04:36:49.813522476 +0000 UTC
End time       : 2021-07-24 04:36:50.814894967 +0000 UTC
Status code    : STATUS_CODE_UNSET
Status message :

Span #1
Trace ID       : ac4d7110c6d22e985b5db28e8ecca769
Parent ID      : e24504245b7cff0e
ID             : 3c374013084a679c
Name           : consumer-function-top-level
Kind           : SPAN_KIND_SERVER
Start time     : 2021-07-24 04:36:48.812135568 +0000 UTC
End time       : 2021-07-24 04:36:51.315562096 +0000 UTC
Status code    : STATUS_CODE_UNSET
Status message :

Span #2 <==== EXTRA SPAN!!!
Trace ID       : ac4d7110c6d22e985b5db28e8ecca769
Parent ID      : ad1bb604de1da312
ID             : 065c07aa6cc4916d
Name           : handler.consumer
Kind           : SPAN_KIND_SERVER
Start time     : 2021-07-24 04:36:48.811673087 +0000 UTC
End time       : 2021-07-24 04:36:51.315622948 +0000 UTC
Status code    : STATUS_CODE_UNSET
Status message :
Attributes:
-> faas.execution: STRING(e759abdb-6119-4f91-afe0-716a71276825)
-> faas.id: STRING(arn:aws:lambda:ap-southeast-2:401722391821:function:aws-python-api-worker-project-dev-consumer)
-> faas.name: STRING(aws-python-api-worker-project-dev-consumer)
-> faas.version: STRING($LATEST)

Hey @michaelhyatt! Thanks for providing logs and steps to reproduce.
I don't think that extra span has anything to do with X-Ray, but if you think it does can you let me know?
I also think that what you are seeing is the expected behavior, if you are following the public AWS OTel docs on Getting Started with Lambda for Python.
This is because the docs include this step:

Add the environment variable AWS_LAMBDA_EXEC_WRAPPER and set to /opt/otel-instrument.

This environment variable is used to run the /opt/otel-instrument script before your def consumer(event, lambda_context) function. That script in opentelemetry-instrument will in turn call a wrapper otel-instrument Python script which will automatically instrument Lambda by creating a trace.
Given the faas namespace in the attributes of Span#2, and its timestamp which both starts and ends  before/after Spans#0 and Spans#1 I suspect that this is the span created by the otel_wrapper.py file to encompass them as the overarching parent span.
I was able to see only your 2 spans (I used the SDK exporter not the Collector exporter though) by not setting the AWS_LAMBDA_EXEC_WRAPPER environment variable and configuring the opentelmetry package on Lambda on my own without the help of the otel-instrument script. From what I understand, that script is meant to initialize much of opentelmetry for you automatically and give you a top "Lambda" span (Span#2) from which any subsequent spans will follow so you can see where they descend from on the Service Map. But if you have another use case, the layer is still useful because it provides all the opentelemetry package code for you to be able to configure it how you want 🙂
I hope that provides a solution for you, please let me know if I can answer anything else!

Hi @NathanielRN, thanks for looking into it.
I can see that the span is indeed created by the otel_wrapper.py file. It automatically assumes X-Ray trace context propagation here and I can see that the generated span (no 2 in my log) has parent.id taken from the X-Ray trace ID header.
In my case, I am using a different trace context propagation method. Instead of X-Ray, I am relying on W3C traceparent header, hence is the setting OTEL_PROPAGATORS: "tracecontext". The problem is this code is hardwired to propagate the X-Ray trace ID instead of the one I am sending in the traceparent HTTP header.
In my previous example you can see the mismatch between the parent.ids of the spans:

Span1.parent.id is injected from traceparent header (not shown there).
Span0.parent.id is Span1.ID <= this is done by my instrumentation.
Span2.parent.id is pointing to some other external span.id that is presumably coming from some X-Ray external trace.

So, to summarise, I am perfectly happy with the auto-instrumentation of my lambda code, as long as the trace context is propagated properly respecting the OTEL_PROPAGATORS setting instead of being hard-wired to AWS X-Ray.

@michaelhyatt sure thing! I spoke with my colleague @garrettwegan and I hope I can give you an answer 🙂
Thanks for pointing me to that code! You're absolutely right that there is an assumption that the _X_AMZN_TRACE_ID environment variable contains the context. (Instead of looking at HTTP headers).
I should point out that the code you linked to is in an upstream OpenTelemetry repository and not in this downstream aws-otel-lambda repository (although this repo does use that code from the upstream). The code you see there was contributed as part of our team's initial release to get OpenTelemetry working with Python (and other SDKs) and the initial scope included making sure it worked with AWS X-Ray, which is why you see that it is hard-coded.
Some OTel Lambda implementations in other languages have already evolved to allow for a wider amount of user use-cases like yours. For example, the upstream OTel Lambda JavaScript now gives users the option to disables AWS X-Ray Propagation and use custom code to extract the context out of the Lambda event. Then you can use that custom context form the Lambda event instead of having it look for an X-Ray context from the _X_AMZN_TRACE_ID env variable by default.
For your issue, my suggestion would be to open an issue upstream to update the OTel Python instrumentation to have an option similar to JavaScript. The repo is still in early stages of development so it is taking help to make all the languages better!
As another note, you said this:

instead of the one I am sending in the traceparent HTTP header.

I think you may run into problems here. I have not verified this myself, but from what I understand, the design of Lambda is that it will never have HTTP headers because Lambda cannot be directly invoked by an HTTP request. HTTP headers are replaced by _X_AMZN_TRACE_ID for X-Ray (as a special case) or by "Lambda Events" (in any other case). So you must get your context from a Lambda Event if you have a custom context you want to use. (i.e. you would invoke your Lambda function and insert the HTTP headers into the event that is to be received at the Lambda side).
The ideal future would be one where upstream supports both the X-Ray method of using _X_AMZN_TRACE_ID and the poweruser method way like yourself that uses Lambda Events and an "eventContextExtractor" (like OTel JS) to get the context.
Please let me know if that explains the issue! Unfortunately it's just a limitation of where the project is for now 😞

Thanks, @NathanielRN and @garrettwegan. I created this issue in the upstream opentelemetry-lambda repo.
I wanted to clarify the trace context propagation with Lambdas.

Lambda function receives HTTP headers through event["headers"] and using OTel tracecontext extract/inject with the right context propagator setting should take care of using the right getter and setter to extract the parent trace context. A very similar setup can work with SQS message headers and any other protocol supporting metadata attached to the event. So, AWS X-Ray context propagation shouldn't be the only way to propagate trace context between services.
I had a similar issue with JS lambdas, but now it has been fixed with v0.23 of JS layer and tracecontext propagation appears to work as expected.
I really like all the initialisation that is done within otel-instrument and would like to continue to rely on it without having to initialise OTel myself. And relying on auto instrumentation would be super helpful instead of creating the spans myself, however, I really want the spans to be linked to the external context rather than AWS X-Ray.

Hope it makes sense, happy to move the discussion into the other upstream issue.

Thanks for creating that issue! I appreciate it! 😄
I'll do my best to answer your questions:
Regarding 1, I don't think you can count on headers being in event["headers"]. It seems like you can configure that for API Gateway but it's not defined? It would help to continue this thread on my PR to fix the problem if you know otherwise!
Regarding 2, I'm glad you got a solution! However I looked at the issue you posted and I'm not sure what fix was done to address that? But it's probably best to continue the conversation there if you have any additional questions.
Regarding 3, I think we may encounter difficulties again as pointed out in the thread on my PR but hopefully we do find  a solution upstream that works!


VIM crashes on starup with VDebug installed

VIM 7.4.629
VDegug 1.5.1
Python 2.7.12
Redhat Enterprise Linux 6.9
Hi,
I am new to VIM, was excited by the VDebug plugin.
When I try to start VIM with VDegug installed, VIM crashes with the following error messages:

Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault (core dumped

Any clues?
Thanks much either way
My Vdebug installation directory at /home/itsme/.vim

prompt> ls -1
bootstrap.sh
build.sh*
CHANGELOG
doc/
features/
Gemfile
Gemfile.lock
LICENCE
plugin/
Rakefile
README.md
requirements.txt
rubylib/
spec/
syntax/
tests/
Vagrantfile
vdebugtests.py
VERSION

VIM Version Information:

prompt> vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Dec 12 2016 09:49:04)
Included patches: 1-207, 209-629
Modified by<EMAIL_ADDRESS>Compiled by<EMAIL_ADDRESS>Huge version without GUI.  Features included (+) or not (-):
+acl             +farsi           +mouse_netterm   +syntax
+arabic          +file_in_path    +mouse_sgr       +tag_binary
+autocmd         +find_in_path    -mouse_sysmouse  +tag_old_static
-balloon_eval    +float           +mouse_urxvt     -tag_any_white
-browse          +folding         +mouse_xterm     -tcl
++builtin_terms  -footer          +multi_byte      +terminfo
+byte_offset     +fork()          +multi_lang      +termresponse
+cindent         +gettext         -mzscheme        +textobjects
-clientserver    -hangul_input    +netbeans_intg   +title
-clipboard       +iconv           +path_extra      -toolbar
+cmdline_compl   +insert_expand   +perl            +user_commands
+cmdline_hist    +jumplist        +persistent_undo +vertsplit
+cmdline_info    +keymap          +postscript      +virtualedit
+comments        +langmap         +printer         +visual
+conceal         +libcall         +profile         +visualextra
+cryptv          +linebreak       +python/dyn      +viminfo
+cscope          +lispindent      -python3         +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con      -lua             +rightleft       +windows
+diff            +menu            -ruby            +writebackup
+digraphs        +mksession       +scrollbind      -X11
-dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     -xim
+emacs_tags      -mouseshape      -sniff           -xsmp
+eval            +mouse_dec       +startuptime     -xterm_clipboard
+ex_extra        +mouse_gpm       +statusline      -xterm_save
+extra_search    -mouse_jsbterm   -sun_workshop    -xpm
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/etc"
 f-b for $VIMRUNTIME: "/usr/share/vim/vim74"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -O2 -g -pipe -Wall -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc   -Wl,-E -Wl,-rpath,/usr/lib64/perl5/CORE   -L/usr/local/lib -Wl,--as-needed -o vim        -lm -lnsl  -lselinux  -ltinfo -lacl -lattr -lgpm   -Wl,-E -Wl,-rpath,/usr/lib64/perl5/CORE  -fstack-protector  -L/usr/lib64/perl5/CORE -lperl -lresolv -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc
prompt>

@tinker123456 It crashes immediatly on startup? Could you try with 1.5.2 and confirm the issue is still present?

Yes, the issue is exactly the same with 1.5.2

I found this with h: python-dynamic

The 'pythondll' or 'pythonthreedll' option can be used to specify the Python shared library file instead of DYNAMIC_PYTHON_DLL or DYNAMIC_PYTHON3_DLL file what were specified at compile time. The version of the shared library must match the Python 2.x or Python 3 version Vim was compiled with.

@tinker123456 thanks.That might need some further investigation. All the packages are official ones? So I could probably reproduce it with centos?

@tinker123456 hmm for the dynamic python, could you do strings /usr/bin/vim | grep python and paste the output?

I found this in my vim --version output from above:
Huge version without GUI.  Features included (+) or not (-):
+python/dyn
-python3
My version of python is Python 2.7.12
I have no idea how to find out what version Python my VIM was compiled with or the shared library the h: blurb mentions.

@tinker123456 but all the packages you use are from the official repo's? So I basically could reproduce this on CentOS?

The system I described above isn't mine, it is my box at work, at a Big Org, that had some ghost prepared in Big tech department.  In other words, I don't know and it wouldn't be easy to find out.

If I check the version output of vim in my centos container it begins like this
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug  2 2017 00:45:54)
Included patches: 1-160
Modified by<EMAIL_ADDRESS>Compiled by<EMAIL_ADDRESS>
Note the last lines, they indicate that it was compiled for the official package I guess.


Mobile support

The javascript seens not to be working in my iPhone 5s(iOS 8.3, Safari & Chrome)
I have no idea to fix it. Please help, thanks!!

The demo site works just fine on my iPhone 5. Can you be more specific? Can you connect with the Safari debugger and see a console error?

The demo site works just fine on my iPhone, too!! Sorry!!
I'll check mine deployment later, Thanks!!

@kako0507 I have a problem like you, how did you solve it?


Revamp events and refactor/reformat code

All event traits are removed and base events classes used instead (thereby avoid declaring public properties in traits for classes)
Added unavailable comyii\user\events\admin\CreateEvent
Revamped clients and included ClientTrait and base Client class
Renamed client classes to end with Auth for consistency
Revamped PHP Documentation and edited various classes
Various code formatting updates

@derekisbusy ... FYI... I am incorporating updates to the repo via this issue.

Okay, I just pushed what I have for now. Also I moved the clients to comyii\user\authclient\clients to match that of the yii\authclient\clients structure.


[bugfix]move access policy into keyvault resource

Purpose
Keyvault secrets created in other modules only depend on var.kv_id implicitly. If we separate the access policy to a separate resource (even within same module),  kv secrets can be created before the access policy is created. By moving the access policy into the keyvault resource block, the var.kv_id in other modules will handle the dependency and will be created after both keyvault and access policy are created.
Does this introduce a breaking change?

[x] Yes
[ ] No

Author pre-publish checklist:

[ ] Added test to prove my fix is effective or new feature works
[x] No PII in logs
[ ] Made corresponding changes to the documentation

ah sorry, I remembered that we cannot use access_policy block with the access policy resource together( we still have the access policy resource in ADF, let me fix it and update this PR later

ah sorry, I remembered that we cannot use access_policy block with the access policy resource together( we still have the access policy resource in ADF, let me fix it and update this PR later

fixed


Research ExitWithErrorCode returns in Spawn.go

Line 22 in spawn.go
	if err != nil {
		return err
	}

should be revisited to confirm that this should be wrapped in ExitWithErrorCode like the rest of the returns back to the command launch.

I have confirmed that this should not be wrapped in an ExitWithErrorCode. This would mask errors such as vaulted.ErrIncorrectPassword, causing them to no longer be translated into the correct exit codes (see main.go:66).


[BUG] Spring Data Cosmos Query doesn't apply Sort parameter correctly when using non-space-character whitespace

Describe the bug
When creating a Spring Data repository to use Cosmos, if creating a query with the @Query parameter but using newlines between statements instead of just spaces, which has a Sort parameter to allow for the caller to dynamically set the sort order, the constructed query is incorrect causing a Cosmos error.
Exception or Stack Trace
2023-12-07T11:38:30.564-05:00 DEBUG 14364 --- [project] [ctor-http-nio-8] c.a.c.implementation.SqlQuerySpecLogger  : select *
from collection
where collection.field = @val
 ORDER BY collection
where.otherfield ASC

com.azure.spring.data.cosmos.exception.CosmosAccessException: Failed to find items
	at com.azure.spring.data.cosmos.exception.CosmosExceptionUtils.exceptionHandler(CosmosExceptionUtils.java:38) ~[azure-spring-data-cosmos-5.7.0.jar:5.7.0]
	Suppressed: [CIRCULAR REFERENCE: com.azure.cosmos.CosmosException: {"innerErrorMessage":"{\"code\":\"BadRequest\",\"message\":\"One of the input values is invalid.\\r\\nActivityId: 1b6f9e4c-706c-45b2-8b77-f59ae22dce1b, Windows/10.0.17763 cosmos-netstandard-sdk/3.18.0\"}, StatusCode: BadRequest","cosmosDiagnostics":{"userAgent":"azsdk-java-cosmos/4.52.0 Windows11/10.0 JRE/17.0.9 az-sd-cos/<EMAIL_ADDRESS>
To Reproduce
Steps to reproduce the behavior:

Attempt to call the query with a sort specified

Code Snippet
Example of code that doesn't work:
@Query("""
select *
from collection
where collection.field = @val
""")
Flux<Entity> findByField(final String val, final Sort sort);

But rearranging so that the "where" is on the same line as the "from" does work:
@Query("""
select *
from collection where
collection.field = @val
""")
Flux<Entity> findByField(final String val, final Sort sort);

Expected behavior
Any sort of whitespace should be treated the same, so it shouldn't break if using a newline after the collection name instead of a space.
Setup (please complete the following information):

OS: Windows 11 Enterprise 22H2 build 22621.2792
IDE: IntelliJ IDEA 2022.1.4 Ultimate
Library/Libraries: com.azure.spring:spring-cloud-azure-starter-data-cosmos:5.7.0
Java version: 17.0.9
Frameworks: Spring Boot 3.2.0

Additional context
I think the bug is here:
https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/spring/azure-spring-data-cosmos/src/main/java/com/azure/spring/data/cosmos/core/generator/NativeQueryGenerator.java#L51
Where it uses a regular expression accepting any sort of whitespace after the collection name, but then does an indexOf(" ") which assumes that the whitespace after the collection name is an actual space character.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[X] Bug Description Added
[X] Repro Steps Added
[X] Setup information Added

@kushagraThapar could you please help route this?

@trande4884 can you please take a look at this, thanks!

@petercooperjr-spls I am able to reproduce your issue, and I actually have problems with both of the examples you have above with new lines. I will work on a solution for this bug shortly!

It's possible I did something slightly different in my attempt to anonymize my actual collection and field names. In any event, I do have a workaround of just having more of the query on the same line, so this isn't particularly urgent. It's just one of those annoying things that should probably get fixed.
Thank you very much!


[CT-1188] [Feature] Support Migration from Transient to Permanent Table Configurations

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt-snowflake functionality, rather than a Big Idea better suited to a discussion

Describe the feature
Changing transient=true on a table that was built with transient=false has no effect, particularly for "long lived tables" like snapshots, this is a problem.
Describe alternatives you've considered
https://stackoverflow.com/questions/73469697/snowflake-transient-to-permanent-table
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response

Added context from Slack thread: rather than needing to switch this partway through a table's existence, the right answer here might be better defaults!

Makes sense to me that snapshots would want to be permanent tables (support undrop + time-travel for >1 day).
We could also consider

updating the docs here to recommend setting transient: false for all snapshots
(code change) setting transient = false for snapshots by default

+1 for better defaults by making the code change to set transient = false for snapshots by default -- feels like we could easily make that change whether or not we take up supporting migration from transient to permanent.

updating the docs here to recommend setting transient: false for all snapshots
(code change) setting transient = false for snapshots by default

Capture these in a new issue: https://github.com/dbt-labs/dbt-snowflake/issues/332


add healthz deep subpathes for all controllers

Issue #, if available:
Description of changes:
We want to add deep health check probes into individual controllers.
The current healthz ping is simple and basically just checking if the VPC RC manager goroutine (main routine) is not failing. Reported customers’ cases told us the main check may not be sufficient in some cases. What we want

if one goroutine blocks resources, the healthz need to restart the entire controller
the healthz probes should cover all sub controllers
the heatlhz probe should have its own timeout instead of rely on kubelet timeout
the health status monitored by kubelet should be aggregated (one failure should fails all)
simple ping or complicate probing real data should depend on how critical and vulnerable the targeted controller may be.

Tests have been done
[+]health-annotation-validating-webhook ok
[+]health-branch-provider ok
[+]health-cm-controller ok
[+]health-custom-pod-controller ok
[+]health-deploy-controller ok
[+]health-interface-cleaner ok
[+]health-introspect-controller ok
[+]health-ipv4-provider ok
[+]health-node-controller ok
[+]health-node-manager ok
[+]health-node-validating-webhook ok
[+]health-pod-controller ok
[+]health-pod-mutating-webhook ok
[+]health-resource-manager ok
[+]health-root-manager-ping ok
healthz check passed

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Seems controller-gen has some flakiness. I will take some look at this tool as working on #199


CI: update setup

use opencollective instead of ubuntu user

@znarf Seems this also needs to be done in the frontend.

@eloyekunle it was done and merged at the same time: https://github.com/opencollective/opencollective-frontend/pull/1808

I'm getting a CI error here: https://circleci.com/gh/opencollective/opencollective-frontend/21574

@eloyekunle It's because the matching API branch was not updated. We should deleted it instead.

Oh okay, will do that. Thanks.


WFS Crash Fix

WFS Crash Fix
The map was crashing whenever DataBC sent an empty feature array. I added a couple try/catch statements that fix this.
I should also add that there is a Pesticide query mostly baked. It has no effect on either backend or frontend yet.

/rebase


[New Feature]Does W8A8 currently support mixed precision inference?

Currently SQ encounters accuracy and diff rate issues
Is there any good solution?
Does TRT_LLM currently support mixed precision? FP16 is used in the Linear layer with high quantization sensitivity, and INT8 is used in others.
Thank you~

@Tracin Do you have some suggestions?
Thanks~

No, we don't support mixed-precision at current stage.


Calls tensor.untyped_storage instead of tesnor.storage

Fix https://github.com/Stonesjtu/pytorch_memlab/issues/58

LGTM overall.
Can you update the README for using UntypedStorage class here:
https://github.com/Stonesjtu/pytorch_memlab/blob/212e59568e72e4ea6275b38031f4f766bf3d70d0/README.md?plain=1#L207


sarima added in Codebase

#131 Fixes Issue🛠
Description👨💻
Sarima implementation added in the Code Base.

Type of change📄

[x] New feature (non-breaking change which adds functionality)

Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added demonstration in the form of GIF/video file
[x] I am an Open Source Contributor

Screenshots/GIF📷

Pls provide the screenshots of accuracy metrics and plot @ayushrathore111


In-snakefile style conda env and schema

I use snakemake mostly for automating jobs on remote infrastructure. I pretty routinely find myself writing small (1-2 rule) workflows. At the moment, I have to spread the logic for these workflows across three distinct locations: a conda env file, a schema file defining the config, and a snakefile defining the rules.
I find this to be a bit annoying for small jobs, and it seems to be a pain point for some of my fellow bioinformaticians who are clinging to local hardware. It also doesn't seem necessary. It seems like we could pretty easily support embedding conda environments and schema in the Snakefile itself. The syntax might look something like....
from snakemake.utils import validate

schema = {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "description": "configuration for workflow",
    "required": ["basename", "reads"],
    "properties": {
        "basename": {
            "type": "string",
            "description": "basename for output files"
        },
        "reads": {
            "type": "array",
            "items": {"type": "string"},
            "description": "a set of reads to process"
        },
        "threads": {
            "type": "integer",
            "description": "number of cores to use",
            "default": 16
        }
    }
}

validate(config, schema)

env = {
    'name': 'myworkflow',
    'channels': ['conda-forge', 'bioconda', 'defaults'],
    'dependencies': [
        'rust',
        'git',
        'pip',
        'plotly',
        'seaborn',
        'pandas',
        'scipy',
        { 'pip': ['git+https://gitlab.com/salk-tm/kmer_smudge_rs.git'] }
    ]
}

rule smudge_rs:
    input:
        config["reads"]
    output:
        config["basename"] + ".counts",
        config["basename"] + ".hist"
    params:
        base = config["basename"],
    conda:
        env
    threads:
        config["threads"]
    shell:
        """
        # my simple script
        touch {output}
        """

I could probably put together a pull request to get these two features, but I wanted to get input from others before plunging in. Implementing these features is not necessarily good from a design perspective.
The main pro I see is that simple workflows can have all their logic located in a single place, speeding up development, and speeding up learning. It is a lot easier for novices to read a single file than to read three and understand how they are linked.
The main con I see is that users may be tempted to use this style in places where it isn't appropriate, with more complicated workflows, that would benefit from having environments and schema separated out from the main rule graph logic.
What do you all think. Is this style something that snakemake should support?

I think this could be useful, particularly because often in my case many rules require only a single package (which comes with its own dependencies of course). It would make more sense to me to specify only the package rather than create several almost identical looking yaml files with only the name of the dependency being different. So if this were implemented I could create a dict with the defaults (such as the channels) which are constant between envs, and for each one only add the name and dependency.


[SPARK-37545][SQL] V2 CreateTableAsSelect command should qualify location

What changes were proposed in this pull request?

Currently, v2 CTAS command doesn't qualify the location:
spark.sql("CREATE TABLE testcat.t USING foo LOCATION '/tmp/foo' AS SELECT id FROM source")
spark.sql("DESCRIBE EXTENDED testcat.t").filter("col_name = 'Location'").show

+--------+-------------+-------+
|col_name|    data_type|comment|
+--------+-------------+-------+
|Location|/tmp/foo     |       |
+--------+-------------+-------+

, whereas v1 command qualifies the location as file:/tmp/foo which is the correct behavior since the default filesystem can change for different sessions.
Why are the changes needed?

This PR proposes to store the qualified location in order to prevent the issue where default filesystem changes for different sessions.
Does this PR introduce any user-facing change?

Yes, now, v2 CTAS command will store qualified location:
+--------+-------------+-------+
|col_name|    data_type|comment|
+--------+-------------+-------+
|Location|file:/tmp/foo|       |
+--------+-------------+-------+

How was this patch tested?

Added new test

Test build #145920 has started for PR 34806 at commit e3c2624.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50396/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50396/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50396/

Test build #145920 has finished for PR 34806 at commit e3c2624.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145920/

Test build #145922 has started for PR 34806 at commit fb771b7.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50398/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/50398/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/50398/

Test build #145922 has finished for PR 34806 at commit fb771b7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145922/

I didn't qualify path in ReplaceTableAsSelect. I will submit a PR shortly to fix it.

Merged to master. Thanks! @imback82
cc @cloud-fan

late LGTM


Fix comment typo probeContainerReadiness

I'm covered by Red Hat's CLA.

LGTM, thanks @sdodson! Will merge on green.


Update AvailablePlugins.md

👍

Thanks @snatchev, closed in favor of https://github.com/fastlane/fastlane/pull/5260/ (there is a rake task to automatically generate the file 👍)


Add GIGACHAD Diffusion Pruned

Please add GIGACHAD Diffusion Pruned

please upload here https://huggingface.co

please upload here https://huggingface.co

https://huggingface.co/SpiteAnon/gigachad-diffusion

Hmm... Your colab notebook just loads the model. Ok I'll make a PR.


No video output but sound works fine

Hello, first of all, amazing project!!!
I've tried to test Super Mario Bros in a real SNES (SNS-CPU-RGB-01) using a flashcard and, while the game actually has sound output just as one would expect, theres absolutely no video output, just a black screen.
Thanks,
Soniccd123
PS: I've made some tests after reading the NESdev post about the emulator sugesting that this behavior is reproducible in HIGAN and that could be some PPU initialization problem. To test it, i've used a normal SNES cart to initialize the PPU, removed this cart with the console running, inserted my flashcard and pressed reset on the console. With this the screen came to life, i hope this helps to find a fix.

I implemented your change to v1.1


Need to add authentication to MQTT

Hey folks, was lookin at this to see what's needed but there's no description.
Looked a bit at options. There's bus authentication itself which should be used:
https://mosquitto.org/documentation/authentication-methods/
Then using that bus, being authenticated to it, components might use something like JWT-rs265 tokens and certificates to sign them to authenticate to eachother via the bus.  If implemented correctly (maybe my explanation is a bit poor), that should ensure only components with the right certificates (signed by the soarca-implementor themselves) can speak to eachother over an common authenticated channel.
Does that sound about right or do you have different views on how it should work?
Regards,
~Sebbie

@r0c300 I think this is something we have to consider. JWT-rs265 tokens auth are currently not part of the Fin Protocol, however, this might be a good suggestion for SOARCA v1.2.


feat(rust): entity refactor

Roll back cloud_node_tcp_address copy
Lower ctx viz in LocalEntity
Remove send and receive from LocalEntity
Remove local entity secure_channel_address
Remove forwarding from LocalEntity
Remove RemoteEntity. Its only current use was a small forwarding example. Not fully baked, I don't think.
LocalEntity randomize address for new context.
Entity no longer starts a worker.
LocalEntity  renamed to Entity.
Example variables named local have been renamed to alice and bob as appropriate.
Example secure channel name changed to bob_secure_channel_listener

@SanjoDeundiak FYI this is my first set of changes today


when can gateway 2.0X be ready?

when can gateway 2.0X be ready?

https://github.com/spring-cloud/spring-cloud-release/milestones?direction=asc&sort=due_date&state=open


Update following BBC site changes

The players are no longer detected correctly.

Oh, I already pushed those changes. Going a bit crazy. :-(


Aesthetic

CSS dark mode changes, HTML changes (spelling fixes), also replaces certain images for better dark mode cohesion.

Had to delete some files to merge it. The culprits were the db.sqlite3 file, most likely from a conflicting account made. The other problem was with a template, appointments.html. I got rid of the file for now, but I am going to push it to prod and see if I can change the file in prod by just replacing it.


GUI Scripts

Read and run available scripts.

Feature added. GUI reads parameters from available scripts for looping.


Add statistics visualiser.

Add canvas based graph to the test page and build process.
This addresses issue  #98

@joeyparrish I have added buffer length to the visualisation. Shall I include it in this PR or open another?

Sorry for the delay.  I was busy on other projects for a bit, and I'm getting caught up now.
Buffer length in this PR is fine with me.  Thanks so much for taking this on.

A legend might also be nice.  It is very hard to figure out what these lines are at first glance without referring to the source code.

@joeyparrish I have updated the PR with your suggestions.

Can one of the admins verify this patch?

Closing, please see comments in #98.


Error on Influxdb web data connector

Since February 5, the influxdb web data connector no longer work. Did you have more information about this issue ?
I use Tableau desktop 2019.2 and the error is "SyntaxError: Invalid character: '`' file: https://tagyoureit.github.io/InfluxDB_WDC/InfluxDB_WDC.js line: 68"
Regards

You will need to bring this issue to the developer of the WDC: https://github.com/tagyoureit/InfluxDB_WDC/issues/new/choose


Fork eosio.contracts

eosio.contracts have some known bugs, which have local fixes here. But contracts from eos repository is deprecated. After adding eosio.contracts as submodule, the build of GolosChain/golos-smart becomes tricky.
Required to fix GolosChain/golos-smart#42

Done: https://github.com/GolosChain/golos.contracts


Initial application skeleton in electron

Create an initial skeleton of the application.

Merging the basic code skeleton into main branch.


Closing this issue.


License?

Fantastic! Thanks for making and sharing this! What’s the license for it?

Added license.
Thank you for reminding me :)

Yay, MIT my favorite!


Run distribtests on Python source packages in CI infrastructure

Following https://github.com/grpc/grpc/pull/15028 which fixes https://github.com/grpc/grpc/issues/14762, source package test script is split and is supposed to be run under a different, new set of docker images, that include python-dev package. Currently they are not being run.

Fixed by https://github.com/grpc/grpc/pull/15202


v4.2.0 crashes on pre-lollipop android devices

Description of the problem:
The readme has instructions for using the latest version on older API levels https://github.com/journeyapps/zxing-android-embedded#older-sdk-versions, but when used, the app crashes on devices running on API < 21.
The reason for the crash is the use of AudioAttributes introduced in this PR https://github.com/journeyapps/zxing-android-embedded/pull/587. AudioAttributes was added in API level 21.
Related Issue: https://github.com/journeyapps/zxing-android-embedded/issues/643
We should probably update the README and explicitly mention that the latest version isn't compatible with API < 21 devices.
Which library version are you using? E.g. 4.2.0.
Which phone/tablet are you using, and which Android version does it run? (e.g. Samsung Galaxy S5,
Android 5.0)  Android 4.4.2 and 4.4.4
In the case of an error do you have a stack trace or adb logs?
Fatal Exception: java.lang.NoClassDefFoundError: android.media.AudioAttributes$Builder
       at com.google.zxing.client.android.BeepManager.playBeepSound(BeepManager.java:97)
       at com.google.zxing.client.android.BeepManager.playBeepSoundAndVibrate(BeepManager.java:84)
       at com.journeyapps.barcodescanner.CaptureManager$1.barcodeResult(CaptureManager.java:80)
       at com.journeyapps.barcodescanner.DecoratedBarcodeView$WrappedCallback.barcodeResult(DecoratedBarcodeView.java:50)
       at com.journeyapps.barcodescanner.BarcodeView$1.handleMessage(BarcodeView.java:52)
       at android.os.Handler.dispatchMessage(Handler.java:98)
       at android.os.Looper.loop(Looper.java:136)
       at android.app.ActivityThread.main(ActivityThread.java:5584)
       at java.lang.reflect.Method.invokeNative(Method.java)
       at java.lang.reflect.Method.invoke(Method.java:515)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1268)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1084)
       at dalvik.system.NativeStart.main(NativeStart.java)

FYI @rkistner @ANewGalaxy


[SMALLFIX] Make hadoop-client dependency provided by default for client runtime jar

To fix the incompatibility issue when using client jar compiled with hadoop 2.7.3 (default hadoop-2.7 profile), while the hadoop deployment is 2.7.2

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15426/
Test PASSed.

@apc999 Were you able to run Flink with hadoop in provided scope?

@calvinjia I was able to run basic sanity check. I didn't have flink installation, shall I verify flink for this PR? Just FYI, the flink profile is not effectively defined for client runtime jars.


The index value offset should be the vertex count of all previous mesh

https://github.com/SaschaWillems/Vulkan/blob/cd8274c2942cc18fc4734edd7e045a6a7a000b36/base/VulkanModel.hpp#L298
The index value offset should be the vertex count of all previous mesh because you've append vertices of all meshes into the one single buffer:
indexBuffer.push_back(vertexCount - paiMesh->mNumVertices + Face.mIndices[0]);
indexBuffer.push_back(vertexCount - paiMesh->mNumVertices + Face.mIndices[1]);
indexBuffer.push_back(vertexCount - paiMesh->mNumVertices + Face.mIndices[2]);
BTW, you use this buffer like this
vkCmdBindVertexBuffers(drawCmdBuffers[i], VERTEX_BUFFER_BIND_ID, 1, &models.floor.vertices.buffer, offsets);
vkCmdBindIndexBuffer(drawCmdBuffers[i], models.floor.indices.buffer, 0, VK_INDEX_TYPE_UINT32);
vkCmdDrawIndexed(drawCmdBuffers[i], models.floor.indexCount, 1, 0, 0, 0);

Can you add some detail? Does this cause a bug in a certain example?


Is this plugin ready for 6.6?

Hi
Can we use this plugin also on 6.6?
Thanks!

We have released the version 3.0.0 for Shopware 6.6 support: https://github.com/AREA-NET-GmbH-Shopware-Agentur/plugin-default-product-layout/releases/tag/3.0.0


(rbx-binary) Rojo6 Unknown binary chunk name SSTR

rojo5 serve works but rojo6 serve crashes with this error:

The error message here is not actually about the unknown chunk name, it's the InvalidTypeError note a little lower.
In any case, we've fixed this in rbx-dom and Rojo 7. It required a number of breaking changes, which is why we can't make Rojo 6's binary support better without a lot of work.
I recommend sticking to XML (rbxlx and rbxmx) for Rojo 6, and upgrading to binary when Rojo 7 reaches stable.


Inline nested tags support

Hi @zealot128, I've had a go at adding support for nested pug syntax (I.e.: div A #[a(href="/link") link] can go here.) as it's one of a few things I've noticed needs sorting whilst using the parser and I saw the TODO at the top of grammar.js. I appreciate this looks like a big pull request, but all I've really done is:

[x] Update grammar.js
[x] Update test/example.pug
[x] Add tests in: test/corpus/inline-nested.txt

Aside from that most of the files were generated on tree-sitter generate. I've noticed however that these files also exist in other treesitter parser repositories that are marked as "complete", so I've committed them and updated the .gitignore to match some of these other "complete" parsers.
From what I can see it seems to be working fine. The tests pass and I can see the highlighting working in the example file locally. Let me know if I've missed anything here or done anything wrong, it's my first attempt at a treesitter parser and I have had a few other minor issues whilst using this one that I intend to fix once I know you're happy with what's been done so far.

Thanks for the work. I enabled tests for your PR.
Can you have a look into the failing tests, if there are something that's expected?

Yeah sure. I believe these were failing before I started working on the grammar but I'll have a look into them soon.


Remove patch_method_to_DataFrame and use piping for functions in computation.operations

See https://github.com/uw-echospace/EchoPro/pull/164#pullrequestreview-1843066471 -- to keep code easily traceable seems better to just use .pipe and not a specialized decorator for these operations.
This is low priority since all functions are working fine now. We can do this after v0.4.2 is released.

Just to provide additional context so I can reference this later to discern the logic/rationale for why I implemented these functions using a sort of monkey patch rather than just using the native pandas.DataFrame.pipe method.
There is certainly overlap between patch_method_to_DataFrame decorator and the associated functions (that will be renamed in via #164, but like discretize_variable) and the flexibility/extension of pandas.DataFrame that .pipe provides. My brain definitely prefers moving through pipes with chained method, e.g. object.function(*args), rather than as independent functions/mutations, e.g. function(object, *args). As you've pointed out, .pipe accomplishes the same task (it's almost as if pipe was intentionally designed that way or something...). So the (kind of) monkey patch feature in patch_method_to_DataFrame is (almost) entirely an aesthetic choice such that the difference for how discretize_variable is written out would be:
# the current (sort of) monkey patched pandas.DataFrame extension approach
specimen_grouped = (
    specimen_df_copy
    .assign( arbitrary_value = 1 )
    .discretize_variable( bin_values = length_intervals , bin_variable = 'length' )
    .assign( group = lambda x: np.where( x['sex'] == int(1) , 'male' , 'female' ) )
    .pipe( lambda df: pd.concat( [ df.loc[ df[ 'sex' ] != 3 ] , df.assign( group = 'all' ) ] ) )
    .assign( station = 2 )
)

# the 'let's not be beholden to Brandyn's mostly trivial and idiosyncratic code aesthetic preferences" approach
specimen_grouped = (
    specimen_df_copy
    .assign( arbitrary_value = 1 )
    .pipe( lambda df: discretize_variable( df , bin_values = length_intervals , bin_variable = 'length' ) )
    .assign( group = lambda x: np.where( x['sex'] == int(1) , 'male' , 'female' ) )
    .pipe( lambda df: pd.concat( [ df.loc[ df[ 'sex' ] != 3 ] , df.assign( group = 'all' ) ] ) )
    .assign( station = 2 )
)


Use org/maplibre/mlt instead of com/mlt

If my understanding is correct (per Slack discussion), com in our Java code is the same as example.com - i.e. commercial domain.  Since we are a non-profit, we should probably use org, and clearly indicate the origin - i.e. use org/maplibre/mlt structure in java code

👍 seems like a good change to batch with other changes which might cause conflicts (like the Java formatting PR)


cc: CUBIC - rfc8312bis fast convergence

Update based on https://github.com/NTAP/rfc8312bis/pull/35

remove w_last_max
update the logic of fast convergence
fix the bug where fast convergence is not applied

Rebased on master.


GPB issue

as input I have: GBP15.25
{ _input: 'GBP15.25', _value:<PHONE_NUMBER>0 }
15250000000
Why Value is<PHONE_NUMBER>0?
Shouldn't be 15.25?

No it is not obligated to do so.
Check this out:
http://numeraljs.com/
If you want to see this feature in the next releases you should label this issue enhancement.


Can´t connect or discover Alpha Mini Robot

When I run test_connect.py, I can't discover or connect to the robot:
C:\Users\Sistemas\AppData\Local\Programs\Python\Python312\python.exe C:\Users\Sistemas\PycharmProjects\mini_demo\test\test_connect.py
start scanning...
Address not available when adding <IP_ADDRESS> to multicast group, it is expected to happen on some systems
Address not available when adding <IP_ADDRESS> to multicast group, it is expected to happen on some systems
Address not available when adding <IP_ADDRESS> to multicast group, it is expected to happen on some systems
Address not available when adding <IP_ADDRESS> to multicast group, it is expected to happen on some systems
scan device timeout
stop scan finished.
test_get_device_by_name result:None
Process finished with exit code 0

I change this and put the serial number of my alpha mini:
result: WiFiDevice = await MiniSdk.get_device_by_name("XXXXX", 10)
Also change the type of robot (I'm trying EDU, DEDU and MINI):
MiniSdk.set_robot_type(MiniSdk.RobotType.MINI)
I still can't connect to the robot. :(

Well, I solved this in two ways, the first time I restarted my computer, in my case I use Windows 10, after restarting I managed to connect to the robot.
The second time it was necessary to restart the robot, after restarting it I was able to connect to it.
I don't know if it is related to zeroconf as mentioned in another issue.

100% same problem, however still not solved with the restart of PC/robot :(

Hi @shiiiiikiiiii Is your WiFi behind a firewall? Or something else that could block connections.
Try connecting to 2.4 Ghz or 3.5 Ghz

Check disabled Firewall, also disable and enable wifi device.
https://docs.ubtrobot.com/alphamini/python-sdk-en/qa.html

Check disabled Firewall, also disable and enable wifi device.
https://docs.ubtrobot.com/alphamini/python-sdk-en/qa.html

Thank you so much for your kind advices!!
I'm trying to control the robot by running Java code on its Android system now. I'll check if this will work when using the Wifi solution next time :)

@shiiiiikiiiii Have you managed to change the language of the robot?

@shiiiiikiiiii Have you managed to change the language of the robot?

Some functions are well guided in the doc, like calling the speech service: http://docs.ubtrobot.com/alphamini/#/en-us/speechservice/Development-guide-of-speech-service-for-Alpha-Mini
However, most of the functions are explained weirdly and not completely, only interface definition are listed: see everything in http://docs.ubtrobot.com/alphamini/#/en-us/SDK-INTERFACE-DOCUMENT


linux emoji and adding 'noto color emoji' to the font stack

With Ubuntu 18.04 and Fedora 28 brings full color emoji support to Linux.  By adding "Noto Color Emoji" the end of the bootstrap font stack should improve linux support.
Firefox uses some internal emoji font for rendering, but it isn't what the system uses (meaning, if you cut-n-paste emoji from firefox into terminal, it will look differently).  Chrome  seems to use "Noto Color Emoji" automatically.
Attached is screen shot on firefox before and after adding "Noto Color Emoji" with various defaults.  It's "better" but not perfect since some of the default fonts contain B/W emoji.  That can only be fixed by more complicated @font-face and unicode-range hacks and don't recommend it.

This was generated from https://codepen.io/client9/pen/qoJoZW and some other  https://www.client9.com/css-color-emoji-stack/
thoughts?  Maybe not a big enough problem to justify the change.
Regards,
n

Feel free to make a PR and link to this.


Added Logging support using fern

Fixes #408

So it looks like the approach we'll have to take here is to keep fern behind a feature flag, and not expose it on fuchsia. For fuchsia, we will declare our own versions of these macros that just print to stderr.

@cmyr You may have a look. I don't know how to handle it for Fuschia yet. You said something about cfg flags.

Awesome, will need to give this a spin but it looks good.
It looks like Fuchsia won't be a problem; because fern is only used in the main binary, which fuchsia doesn't use, there's no dependency issue. In the fuchsia binary we can pick use the fuchsia system logger, which will be a nice improvement there as well, so this looks like a clean win.

Done.

Thanks @betterclever, this was long overdue. 😄


Publish 8.4-20230920064108+0000

Publish 8.4-20230920064108+0000

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.


Elements without closing tags not appearing in the soup

None of the self closing tag elements appear in the soup. I saw a post on SO saying that using 'lxml' as my parser would fix it, but that's not working. I get the error message saying no parser was specified so it's defaulting to lxml on my system, but I still don't see any span, a or meta tags.

lxml is the best parser to use. Try mechanicalsoup.Browser(soup_config=dict(features='lxml'))
You'll need to install it from PyPI http://lxml.de/installation.html
See also https://www.crummy.com/software/BeautifulSoup/bs4/doc/#differences-between-parsers


Checking CW vs. CCW Polygons

I have a project that requires polygons start at a particular location on the object and also be in CCW (counter clockwise) order.  Functionality is already built in to LS to view the start point, but requires the polygon is selected.  As for winding order, I don't think there is quick way to check this in the current version (1.9.0) of LS.
One possible solution might be to add the ability to set a different stroke width for the first polygon edge.  Also, adding a toggle to show (or not show) the start point and first edge without having to actually select a polygon, would allow users to verify polygons much faster, especially when checking images with many polygons.  The image below is a good example for this use case.
The first point must always start on the nose, and the winding order must be CCW order... Check.

I don't have a workaround for checking the polygon start point other than just clicking each polygon one by one. As for the winding order, I can get the labels via API GET request, fix any problems, and then PATCH, but this is starting to affect negatively the flow of our downstream labeling pipeline.

Thanks @WillieMaddox, I've taken this to our product and engineering team for review.