gcc-arm-embedded: 6-2017-q2-update -> 7-2018-q2-update

Motivation for this change
gcc-arm-embedded was not updated since mid-2017, this update brings the package to the latest possible version
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

I would suggest the inclusion of this change into 18-09 as well.

nox-review pr 47542 on NixOS
...
gdb_main.c: In function 'gdb_main_loop':
gdb_main.c:157:16: error: this statement may fall through [-Werror=implicit-fallthrough=]
    single_step = true;
                ^
gdb_main.c:159:3: note: here
   case 'c': /* 'c [addr]': Continue [at addr] */
   ^~~~
gdb_main.c:167:16: error: this statement may fall through [-Werror=implicit-fallthrough=]
    single_step = false;
                ^
gdb_main.c:169:3: note: here
   case '?': { /* '?': Request reason for target halt */
   ^~~~
%% bus_spi.c
cc1: all warnings being treated as errors
make: *** [Makefile:71: gdb_main.o] Error 1
%% piniobox.c
...
builder for '/nix/store/cc4pdza1zrk0izxbnqcgrjb19yl8zi0f-blackmagic-1.6.1.drv' failed with exit code 2
error: build of '/nix/store/5pzgcm2wma2lviibja7km4w3szciw13v-inav-2.0.0-rc2.drv', '/nix/store/cc4pdza1zrk0izxbnqcgrjb19yl8zi0f-blackmagic-1.6.1.drv', '/nix/store/xmir01cxxamlpqslgp4p9cgfg643q9c7-betaflight-3.4.0-rc4.drv', '/nix/store/y4m4a0s68bqzwlwl5w55h13jhrqidkgf-axoloti-1.0.12-1.drv', '/nix/store/y6g3l860w20spam79a8hgnny1mxdpb1y-opentx-2.2.1.drv' failed

Third option is to set dependencies of mentioned packages to "gcc-arm-embedded-6" instead of "gcc-arm-embedded"

sounds good to me

Provide feedback to the other packages so they are aware of the issue and can fix it. People seem to welcome this.

@prusnak Sound good to me.  Thanks for updating blackmagic.

Thanks!

@Mic92 Thanks for the merge. What is the correct process to get this into 18.09 release?

I don't think we should backport gcc-arm-embedded = gcc-arm-embedded-7; since it is already late.
It should be ok to backport it as a new package. In that case open a new pull request targeting release-18.09 branch.

Use git cherry-pick -x for backporting and then git commit --amend to remove the gcc-arm-embedded = gcc-arm-embedded-7;


"W" not in this function

https://github.com/Parskatt/DeDoDe/blob/457193690c387b65e17a2035fcfc66cfa0515e08/DeDoDe/datasets/megadepth.py#L174C1-L175C55

What is W?

What is W?

Aha, should be W_A / W_B respectively.

Aha, should be W_A, W_B respectively. Must have copied wrongly from somewhere.

thx, this issue is resolved. 😃


Tick version, rerendered if needed

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


feat(icons): updates play; adds pause icons

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Question about Evaluator thread safety

I'm trying to parallelize multiplying ciphertexts. From previous posts, my understanding is that Evaluator should be thread-safe (so I should be able to use evaluator.multiply in threads). However I'm getting segmentation faults when I try to do so. The relevant code I'm running is:
#pragma omp parallel for
for (int j = 0; j < mult_size;j=j+2){
    if ((j+1) < mult_size){
        seal::Ciphertext mult_el;
        this->evaluator_->multiply(multi_list[j], multi_list[j+1], mult_el);
        this->evaluator_->relinearize_inplace(mult_el, relin_keys);
        inter_list.push_back(mult_el);
    } else {
        inter_list.push_back(multi_list[j]);
    }
}

This causes a segmentation fault. I'm also under the impression that I do not need to worry about MemPools for each thread (I think I saw an earlier post that said that it's now handled internally?).
My code does work when I indicate that either multiply or relinearize_inplace is OpenMP critical (only one thread should run the function at a time).
#pragma omp parallel for
for (int j = 0; j < mult_size;j=j+2){
    if ((j+1) < mult_size){
        seal::Ciphertext mult_el;
        #pragma omp critical(multiply)
        {
            this->evaluator_->multiply(multi_list[j], multi_list[j+1], mult_el);
        }
        this->evaluator_->relinearize_inplace(mult_el, relin_keys);
        inter_list.push_back(mult_el);
    } else {
        inter_list.push_back(multi_list[j]);
    }
}

However I'm confused as to a) why I need to specify this in the first place if Evaluator is thread safe, and b) why doing so for either multiply or relinearize_inplace works (why do either one work and not just one specific one). Ideally I'd like to not need the critical indicator at all given that it slows everything down. Am I doing something wrong or is what I'm trying to do not possible? Thanks in advance for any help!

What type is inter_list? Is inter_list.push_back(...) thread-safe?

Ah, it is not. I guess I assumed it was an Evaluator issue since addressing it "fixed" the problem, but I should know that debugging concurrency issues are never that straightforward. Thanks for pointing that out!

Ah, it is not. I guess I assumed it was an Evaluator issue since addressing it "fixed" the problem, but I should know that debugging concurrency issues are never that straightforward. Thanks for pointing that out!

why not just comment out inter_list.push_back() and then try it again and see whether segment fault pop out.

Oh, I should have mentioned in my last post that I did that and it resolved the issue. I've since made inter_list.push_back() thread safe and everything works as it should.


Bug: When a DLL exports functions by ordinal, the PE module's "number_of_exports" is incorrect

I have a sample DLL (SHA256: 6494f7a6fa5b9d73a7521b823e00c592e83bd4b926e04d4875845e056b17f59c) which exports 5 functions by ordinal:
Copyright (C) Microsoft Corporation.  All rights reserved.

Dump of file 498a331fd5d0161e8583cd1237f00980
File Type: DLL

  Section contains the following exports for khlp760w.dll

    00000000 characteristics
    476699CE time date stamp Mon Dec 17 16:46:22 2007
        0.00 version
           1 ordinal base
           5 number of functions
           0 number of names

    ordinal hint RVA      name

          1      0000254E [NONAME]
          2      00002519 [NONAME]
          3      0000253E [NONAME]
          4      00002562 [NONAME]
          5      0000257D [NONAME]

However, YARA PE module's dump reports 2 exports only (YARA 3.7.1):
pe
	number_of_signatures = 0
	signatures
	number_of_resources = 1
	resources
		[0]
			offset = 45144
			length = 916
			type = 16
			id = 1
			language = 0
			type_string = UNDEFINED
			name_string = UNDEFINED
			language_string = UNDEFINED
	resource_version
		minor = 0
		major = 4
	resource_timestamp = 0
	number_of_exports = 2
	number_of_imports = 5

I’ll take a look at this today.

Thanks for bringing this up! This looks like a parser differential. I can't get a copy of dumpbin right now to compare exact output, but between your output and the fact that IDA also recognizes 5 exports by ordinal I think we need to fix this. I'll investigate more deeply, but this is certainly a interesting issue in the parser.

I don't have an answer just yet, since the specification is confusing on this. I'll keep digging, but for now here are my notes...
Here's what the exports directory entry looks like for 6494f7a6fa5b9d73a7521b823e00c592e83bd4b926e04d4875845e056b17f59c:
(lldb) p/x *exports
(_IMAGE_EXPORT_DIRECTORY) $0 = {
  Characteristics = 0x00000000
  TimeDateStamp = 0x476699ce
  MajorVersion = 0x0000
  MinorVersion = 0x0000
  Name = 0x0000b39c
  Base = 0x00000001
  NumberOfFunctions = 0x00000005
  NumberOfNames = 0x00000000
  AddressOfFunctions = 0x0000b388
  AddressOfNames = 0x0000b39c
  AddressOfNameOrdinals = 0x0000b39c
}
(lldb)

The Name, AddressOfNames and AddressOfNameOrdinals RVAs all point to khlp760w.dll. When we walk the number of functions and attempt to get a name or ordinal for each one we end up with completely bogus offsets into the file, because we are using the contents of the Name field as an RVA, which it clearly is not. Because of this we end up skipping all the export information and end up with UNDEFINED (as you mention in #840).
In the past I've seen 0bad5ff96477fa009db357c42977ebf91c967d9b1df5d2b2c8f8f942a364960d which has an interesting export directory entry. I'm doing my best to make sure we don't regress when parsing that one, since it is another one I've looked at in the past when dealing with the export parsing code.
I'm still trying to work out the best way to go about this so our parser more closely matches IDA, GNU objdump and MSFT bindump, but I'm still a bit away from having something that works.

Let me clear some things up about this whole export directory issue because specification for export directory is indeed confusing.
How export directory works
Export directory points to 3 arrays with RVAs stored in AddressOfFunctions, AddressOfNames and AddressOfNameOrdinals. Let's call them Functions, Names and NameOrdinals. Some facts about these arrays:

Length of array Functions is equal to NumberOfFunctions.
Arrays Names and NameOrdinals should have the same length that is equal to NumberOfNames.
Arrays Names and NameOrdinals can generally be shorter than array Functions in which case some functions do not have a name and are exported purely by ordinal. They can even be empty if all functions are exported by ordinals.
Ordinal of each exported function is just its index in Functions array.
Association of name and function address is done in NameOrdinals array. Each element in NameOrdinals is index into Functions array (so just ordinal). Position of the element in NameOrdinals indicates the position of name in Names array with the name of the function. I tried to create small ASCII art which depicts it all:

 Functions             NameOrdinals           Names
############          ##############      ##############
#  Addr 0  # <------- #     0      # ---> #   Name 1   #
############          ##############      ##############
#  Addr 1  #   +----- #     2      # ---> #   Name 2   #
############   |      ##############      ##############
#  Addr 2  # <-+  +-- #     4      # ---> #   Name 3   #
############      |   ##############      ##############
#  Addr 3  #      |
############      |
#  Addr 4  # <----+
############

From what I understand, YARA now assumes that the length of all three arrays is the same and each exported function also has a name but that's not right at all.
I already have working patch that parses the export directory the right way but I still need to test it against multiple cases of export directories. I'll post it as soon as I am done with testing.

@Wesley: yeah parsing an export directory could be a complete mess. Here's a code that I use:
{
    HANDLE hFile;
    HANDLE hMap = NULL;
    LPBYTE pbMap = NULL;

    hFile = CreateFile(szFileName, FILE_READ_DATA, FILE_SHARE_READ, NULL, OPEN_EXISTING, 0, NULL);
    if(hFile != NULL)
    {
        NtCreateSection(&hMap, SECTION_ALL_ACCESS, NULL, NULL, PAGE_READONLY, SEC_IMAGE, hFile);
        if(hMap != NULL)
        {
            pbMap = (LPBYTE)MapViewOfFile(hMap, FILE_MAP_READ, 0, 0, 0);
            CloseHandle(hMap);
        }

        CloseHandle(hFile);
    }

    return pbMap;
}

int _tmain(void)
{
    LPBYTE pbImageBase;
    LPBYTE pbImageEnd;

    if(__argc < 2 || __targv[1] == NULL)
    {
        printf("No parameters given. Syntax: Test.exe DllName\n");
        return 3;
    }

    // Map the file as image.
    pbImageBase = MapFileAsImage(__targv[1]);
    if(pbImageBase != NULL)
    {
        PIMAGE_EXPORT_DIRECTORY pExportDir;
        PIMAGE_NT_HEADERS64 pNtHdrs64;
        PIMAGE_NT_HEADERS32 pNtHdrs32;
        PIMAGE_DOS_HEADER pDosHdr = (PIMAGE_DOS_HEADER)pbImageBase;
        ULONG SizeOfImage = 0;
        ULONG ExportEnd = 0;
        ULONG ExportVA = 0;

        pNtHdrs64 = (PIMAGE_NT_HEADERS64)(pbImageBase + pDosHdr->e_lfanew);
        if(pNtHdrs64->FileHeader.Machine == IMAGE_FILE_MACHINE_AMD64 || pNtHdrs64->FileHeader.Machine == IMAGE_FILE_MACHINE_IA64)
        {
            if(pNtHdrs64->OptionalHeader.NumberOfRvaAndSizes >= IMAGE_DIRECTORY_ENTRY_EXPORT)
            {
                SizeOfImage = pNtHdrs64->OptionalHeader.SizeOfImage;
                ExportVA = pNtHdrs64->OptionalHeader.DataDirectory[IMAGE_DIRECTORY_ENTRY_EXPORT].VirtualAddress;
                ExportEnd = ExportVA + pNtHdrs64->OptionalHeader.DataDirectory[IMAGE_DIRECTORY_ENTRY_EXPORT].Size;
            }
        }

        pNtHdrs32 = (PIMAGE_NT_HEADERS32)(pbImageBase + pDosHdr->e_lfanew);
        if(pNtHdrs32->FileHeader.Machine == IMAGE_FILE_MACHINE_I386)
        {
            if(pNtHdrs32->OptionalHeader.NumberOfRvaAndSizes >= IMAGE_DIRECTORY_ENTRY_EXPORT)
            {
                SizeOfImage = pNtHdrs32->OptionalHeader.SizeOfImage;
                ExportVA = pNtHdrs32->OptionalHeader.DataDirectory[IMAGE_DIRECTORY_ENTRY_EXPORT].VirtualAddress;
                ExportEnd = ExportVA + pNtHdrs32->OptionalHeader.DataDirectory[IMAGE_DIRECTORY_ENTRY_EXPORT].Size;
            }
        }

        // Set the size of image
        pbImageEnd = pbImageBase + SizeOfImage;

        // Check whether the image export directory is valid
        if(0 < ExportVA && ExportVA < SizeOfImage)
        {
            // Get the export directory range
            pExportDir = (PIMAGE_EXPORT_DIRECTORY)(pbImageBase + ExportVA);
            if(pExportDir->AddressOfNameOrdinals && pExportDir->AddressOfNames)
            {
                PUSHORT AddressOfNameOrdinals = (PUSHORT)(pbImageBase + pExportDir->AddressOfNameOrdinals);
                PULONG AddressOfNamesIndexed;
                PULONG AddressOfFunctions = (PULONG)(pbImageBase + pExportDir->AddressOfFunctions);
                PULONG AddressOfNames = (PULONG)(pbImageBase + pExportDir->AddressOfNames);
                ULONG NumberOfFunctions = pExportDir->NumberOfFunctions;

                // Allocate indexed array of names to translate ordinal -> function name
                AddressOfNamesIndexed = new ULONG[NumberOfFunctions];
                if(AddressOfNamesIndexed != NULL)
                {
                    // Convert the AddressOfNameOrdinals to AddressOfNameIndexed
                    memset(AddressOfNamesIndexed, 0, NumberOfFunctions * sizeof(ULONG));
                    for(ULONG i = 0; i < pExportDir->NumberOfNames; i++)
                    {
                        USHORT NameOrdinal = AddressOfNameOrdinals[i];

                        // Make sure that the index doesn't go out of bounds.
                        if(NameOrdinal < pExportDir->NumberOfFunctions)
                            AddressOfNamesIndexed[NameOrdinal] = AddressOfNames[i];
                    }

                    // Dump all exports
                    for(ULONG i = 0; i < NumberOfFunctions; i++)
                    {
                        LPCSTR szForwardedExport = NULL;
                        LPCSTR szExportName = "";
                        LPCSTR szFormat = " %4u  %4u  %08p  %s\n";
                        ULONG_PTR NameAddr = AddressOfNamesIndexed[i] ? AddressOfNamesIndexed[i] : 0;
                        ULONG_PTR ProcAddr = AddressOfFunctions[i] ? AddressOfFunctions[i] : 0;

                        // Get the export name
                        if(NameAddr != 0)
                            szExportName = (LPCSTR)(pbImageBase + NameAddr);

                        // Forwarded export: If the function address is within the export directory
                        if(ExportVA <= ProcAddr && ProcAddr < ExportEnd)
                        {
                            szForwardedExport = (LPCSTR)(pbImageBase + ProcAddr);
                            szFormat = " %4u  %4u  %08p  %s --> %s\n";
                        }

                        // Show the export
                        printf(szFormat, pExportDir->Base + i, i, ProcAddr, szExportName, szForwardedExport);
                    }

                    // Free the array
                    delete [] AddressOfNamesIndexed;
                }
            }
        }
        else
        {
            printf("Export directory outside the image\n");
        }

        UnmapViewOfFile(pbImageBase);
    }
}


All types are inferred as string

Type inference error for request and response: I tried to build an OpenAPI using this library in combination with hono.js and Next.js. However, after defining the schema, I discovered that when calling the API from the Next.js client, type errors occur. All request parameters and response types have become string types, including date and number types.
response type error
export const postSchema = z
    .object({
        id: z.string(),
        title: z.string(),
        thumb: z.string(),
        summary: z.string().nullable().optional(),
        keywords: z.string().nullable().optional(),
        description: z.string().nullable().optional(),
        slug: z.string().nullable().optional(),
        body: z.string(),
        createdAt: z.coerce.date(),
        updatedAt: z.coerce.date(),
    })
    .strict();
app .openapi(
            createRoute({
                tags: ['文章操作'],
                method: 'get',
                path: '/:item',
                request: {
                    params: z.object({
                        item: z.string(),
                    }),
                },
                responses: {
                    200: {
                        content: {
                            'application/json': {
                                schema: postSchema,
                            },
                        },
                        description: '文章查询结果',
                    },
                },
            }),
            async (c) => {
                try {
                    const { item } = c.req.param();
                    const result = await queryPostItem(item);
                    return c.json(result) as any;
                } catch (error) {
                    return c.json({ error }, 500);
                }
            },
        )

 const result = await apiClient.api.posts[':item'].$get({ param: { item: params.item } });
    if (!result.ok) return notFound();
    const post = await result.json();
// ...

                                <AiOutlineCalendar />

                            <time className="tw-ellips">
                                {!isNil(post.updatedAt)
                                    ? formatChineseTime(post.updatedAt)
                                    : formatChineseTime(post.createdAt)}
                            </time>

request type error
export const postPaginateQuerySchema = z.object({
    page: z.coerce.number().optional().openapi({ type: 'number' }),
    limit: z.coerce.number().optional().openapi({ type: 'number' }),
    orderBy: z.enum(['asc', 'desc']).optional(),
});
export const postPaginateResultSchema = z.object({
    items: z.array(postSchema),
    meta: z.object({
        itemCount: z.coerce.number(),
        totalItems: z.coerce.number(),
        perPage: z.coerce.number(),
        totalPages: z.coerce.number(),
        currentPage: z.coerce.number(),
    }),
});
export type PostPaginate = z.infer<typeof postPaginateResultSchema>;

 const res = await apiClient.api.posts.$get({
        query: { page, limit },
    });
    const { items, meta } = (await res.json()) as any as PostPaginate;

    if (meta.totalPages && meta.totalPages > 0 && page > meta.totalPages) {
        return redirect('/');
    }
// ...

@pincman this is not an issue with our library in terms of your integration.

The date. z.date() does validate dates. However in terms of "specification" (Open API) there is no date representation - there is only a string with some specific formatting but it still a string.
The second screenshot with page and limit is probably correct - I think the documentation would say that it is a number. However in general over HTTP requests the query parameters are all strings. So I imagine what you are seeing is caused by the Next.JS (or something else on your stack) type system and it has nothing to do with our library.

I am going to close this issue but if you happen to notice that is wrongly generated feel free to open up a new issue or reopen this one. Good luck!

I'm encountering the same issue. @pincman how did you go about resolving response values that are dates/numbers being converted to strings?


Can you share some failure cases?

Hi!
Thank you very much for your work. It's awesome! I was wondering if you could share more failure cases besides the few one shared in the paper?
Thanks,
Tianyang

BTW, here is a little typo :).

Hi @Leolty, absolutely! We have all trajectories recorded. Let me clean them and upload them by the end of this week. And thanks for catching the typo, we will update in the next version :)

Hey @Leolty, check out the resources we just uploaded


UI/UX design for required fields

Requirements
As a Guardian user, I want to be told which fields are required within forms.
Pre-requisite
Schema definition language includes provision for defining required items #118
DOD

Mock-up of the UI is created and reviewed by the stakeholder

Acceptance Criteria

When a user is using a schema containing required items it is represented in the UI in the Form
Users are unable to submit a form if/when the required fields are empty, on an attempt to do so the omissions are clearly indicated.

Adding 8 Story Points and Assigning to Mendel

The Control is not something that we can get from any Framework, it is custom. It will take some time. We can't afford this time or Framework as per @mendelenvisionblockchain


[SPARK-47394][SQL] Support TIMESTAMP WITH TIME ZONE for H2Dialect

What changes were proposed in this pull request?

Following the guidelines of SPARK-47375, this PR supports TIMESTAMP WITH TIME ZONE for H2Dialect and maps it to TimestampType regardless of the option preferTimestampNTZ
https://www.h2database.com/html/datatypes.html#timestamp_with_time_zone_type
Why are the changes needed?

H2Dialect improvement, we currently don't have a default mapping for java.sql.Types.TIME_WITH_TIMEZONE, TIMESTAMP_WITH_TIMEZONE
Does this PR introduce any user-facing change?

no
How was this patch tested?

new tests
Was this patch authored or co-authored using generative AI tooling?
no

Thank you @dongjoon-hyun


xxx =

We LOVE to help with any issues or bugs you have!
Questions: If you have questions about how to use Realm, ask on
StackOverflow.
We monitor the realm tag.
Feature Request: Just fill in the first two sections below.
Bugs: To help you as fast as possible with an issue please describe your issue
and the steps you have taken to reproduce it in as many details as possible.
Thanks for helping us help you! :-)
Please remove this line and all above before submitting.

Goals
What do you want to achieve?
Expected Results
What did you expected to happen?
Actual Results
What did happened instead?
e.g. the stack trace of a crash
Steps to Reproduce
What are steps we can follow to reproduce this issue?
Code Sample
Provide a code sample or test case that highlights the issue.
If relevant, include your model definitions.
For larger code samples, links to external gists/repositories are preferred.
Alternatively share confidentially via mail to<EMAIL_ADDRESS>Full Xcode projects that we can compile ourselves are ideal!
Version of Realm and Tooling
In the CONTRIBUTING guidelines, you will find a script,
which will help determining these versions.
Realm version: ?
Xcode version: ?
iOS/OSX version: ?
Dependency manager + version: ?

Hey @BackWorld! Your issue doesn't contain any info. Please update it with the template we provide and we will try to help you.

If you're seeing xxx = <Maximum depth exceeded> in a description of a Realm type (RLMObject/RLMArray/etc), that's just because Realm caps logging an object graph depth at 5 levels deep: https://github.com/realm/realm-cocoa/blob/v2.0.3/Realm/RLMCollection.mm#L180-L218
This is done to prevent infinite loops when logging a circular object graph, among other reasons. It's nothing to be concerned about.


Fixed the way ENV variable for iterations are read

ITERATIONS is not always a number, so doing a parseInt.
P.S: I am trying to create a runtime benchmark for CSS-in-JS, aka trying to record Chrome timeline metrics like paint, layouts, styling, etc for each of the cases and hence wanted the page to be really big to show differences.

:)


Use shutil.which() to get compiler path

Remove the __get_first_compiler_in_path() function that used which(1) / where program to get the compiler path, with built-in shutil.which().  This fixes pygccxml on systems where which(1) is no longer present (it is not a standard POSIX tool, and Linux distributions are working towards making it optional).

Thanks!


Unable to run bmlingam-coeff

I have installed bmlingam which works great finding causality .
However I am facing the following issue while running bmlingam-coeff.
Traceback (most recent call last):
File "/home/administrator/anaconda2/bin/bmlingam-coeff", line 11, in <module>
from bmlingam.commands.bmlingam_coeff import estimate_coeff_posterior, \
ImportError: cannot import name estimate_coeff_posterior

Can you please help what must have gone wrong

Hi @abhishekscript Thanks for your report. I fixed a bug on your problem and pushed to develop branch. Could you try this?


Inheritance Key Health Check

For IK health check, a HC message is sent to all comma user has - notification, sms and email. The message says “This is a Health Check notification for your Inheritance Key. Please click below to complete the process”. May be more text.
Once the user has clicked on any one of the message, the HC for IK is complete

Health Check Breakdown:

IKS instance available at the backend can be checked instantaneously. This is manageable w/ the current UX for health check.
IKS email health check requires user action(as per the issue description) and a follow up request from the app to check the status once the user has acknowledged the CTA. @ASN-BitHyve This might require UX update and instructions on the know more modal.

Dependency https://github.com/bithyve/bitcoin-keeper/issues/4679
Moving to 33.


How to write tests if you use Provider for passing props

Hi. I start using Provider and encounter that writing test is tricky. I use enzyme mount function for my tests. My first intent was next:

const profile = new Profile_Store({ id: 1, name: 'Tod' });
wrap = mount(
         <Provider profile ={profile}>
            <Person age={'30'} />
         </Provider>
      );

and component

@observer(['profile']) class Person extends Component {
   render() {
      return(
         <div className="person">
            { this.props.profile.name }
         </div>
      )
   }
}

export default Person;

but dealing that way produce 2 problems:

Enzyme .context() function doesn't work cuz it try to get state of Provider instead of Person
Error: MobX observer: Store 'profile' is not available! Make sure it is provided by some Provider

@optimatex in your test you should be able to pass profile directly, @observaber will pick that up as well: mount(<Person profile={profile} age={'30'} />)

Closed for inactivity, answer has been provided in the docs

oh, i did write answer in docs. Maybe it didn't show u my post
optimatex added a line comment 14 days ago
Thank for ur response. I did like u suggest and met another error:
TypeError: Attempted to wrap undefined property handleLike as function
in this sinon function:
handleLike_spy = sinon.spy(Person.prototype, 'handleLike');
this error appears only if i use @observer(['profile']) . If i remove (['profile']) - no more error.
i also did console.log(Person.prototype) :
// Prototype
Constructor{
constructor: function (props, context, updater) { ... },
__reactAutoBindMap: Object{getDOMNode: function () { ... }},
getDOMNode: function () { ... }, render: function (){ ... },
mixins: null,
statics: null,
propTypes: null,
contextTypes: null,
childContextTypes: null,
getDefaultProps: null,
etInitialState: null,
getChildContext: null,
componentWillMount: null,
componentDidMount: null,
componentWillReceiveProps: null,
shouldComponentUpdate: null,
componentWillUpdate: null,
componentDidUpdate: null,
componentWillUnmount: null,
updateComponent: null
}
and in case when i remove (['main_store']) the output is next:
Bar{
componentWillMount: function (){ ... },
componentWillUnmount: function (){ ... },
componentDidMount: function (){ ... },
componentDidUpdate: function (){ ... },
shouldComponentUpdate: function (e,t){ ... }
}
do u have any idea what can cause this transformation which lead to unrealizable wrapping function with sinon?

@optimatex is Person the component? note that when using inject or observer([stores]), a component get's actually wrapped around your component, so this might lead to a mismatch if you try to access component functions / props from outside. The wrapped (your original) component should be available as .wrappedInstance / .wrappedComponent. E.g: Person.wrappedComponent.prototype.handleLike

@mweststrate thank u for ur answer. I'll try

So what about the case when the component under test is using child components that also use inject?
In my test, I tried to pass child stores from the parent, assuming they are going to be inherited but that didn't work, throwing the error in the title of this issue.
For example
const wrapper = renderer.create(<Videos videos={videosStore} routing={{}} thread={mockThreadStore} classes={{}}/>)
expect(wrapper.toJSON()).toMatchSnapshot()

Here, videos store is used by the Videos component. routing and thread are being used by a child.

Does your Videos pass these stores on to its children? Note that Videos
itself does not become magically an provider by just passing it some stores
:) So if nested children need injection, just wrap your component under
test with a Provider
Op wo 28 mrt. 2018 om 08:01 schreef Mohammed Hamdy<EMAIL_ADDRESS>
:

So what about the case when the component under test is using child
components that also use inject?
In my test, I tried to pass child stores from the parent, assuming they
are going to be inherited but that didn't work, throwing the error in the
title of this issue.
For example
const wrapper = renderer.create()
expect(wrapper.toJSON()).toMatchSnapshot()
Here, videos store is used by the Videos component. routing and thread
are being used by a child.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/112#issuecomment-376771259,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABvGhMfosD5CfRUz9G0dqkJjIHydRfrlks5tiycdgaJpZM4Jv4oy
.

thank you for the fast response @mweststrate ! I thought that won't work given the OP comment but it worked for me. Thank you!


Disable automatic type acquisition with command line option, replace npm view with request to npm registry

--disableAutomaticTypingAcquisition command line option can be used to turn off automatic type acquisition.
Fixes #11553
// cc @dbaeumer, @mhegazy

thanks!


Research: Github planning and roadmap options

As a developer
I want to use planning and roadmap views
So I can take proper actions during sprint planning or grooming sessions
Acceptance criteria: Wiki page with workflow when managing stories from planning and roadmap views


fix: deprecate CDP for Firefox

This PR adds a deprecation warning if Chrome DevTools Protocol (CDP) is used for Firefox. Instead CDP, use WebDriver BiDi:
import puppeteer from 'puppeteer';

const browser = await puppeteer.launch({
  product: 'firefox',
  protocol: 'webDriverBiDi',
});
const page = await browser.newPage();
...
await browser.close();

@Lightning00Blade code to action?

@Lightning00Blade code to action?
Typo I wanted to say call to action as there is no issue way for a person to say this is not working file and issue or something else

@whimboo PTAL I think on our end we are ready to mark CDP support for Firefox as deprecated

@whimboo PTAL I think on our end we are ready to mark CDP support for Firefox as deprecated

I thought that we wanted to do that after the announcement that Puppeteer fully supports Firefox via WebDriver BiDi. For me it feels a bit too early.

@whimboo we are only 13 tests away  from feature-parity with CDP and 147 new tests are passing so I think it is fine to nudge users to try WebDriver BiDi and switch over.


Update the go get to k8s.io/sample-controller

Referring to the issue: https://github.com/kubernetes/sample-controller/issues/20#issuecomment-398716033
Sorry, we do not accept changes directly against this repository. Please see
CONTRIBUTING.md for information on where and how to contribute instead.

@rkamudhan Please create a PR for this against the main kubernetes/kubernetes repo: https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/sample-controller. This repo is a copy of the code from the main repo.
/close


Adds className prop to ComponentWrapperFooter

💬 Description
Not a lot else to say really!

 Fix styling for editable component field hover handles

 Fix styling for editable component field hover handles


Please explain what --run-id is

The --run-id parameter is required on all these commands, but nowhere do you explain what one is or give an example that shows what one would look like.
Please add those details.

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

ID: 4e1f25b5-397e-03b6-7d7f-75570d8649e5
Version Independent ID: 962e2f0c-ce31-7de7-8222-17ceeac1dc98
Content: az pipelines runs artifact
Content Source: latest/docs-ref-autogen/ext/azure-devops/pipelines/runs/artifact.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@RickKra
You will be able to better map these commands and inputs to UI if you have the preview feature enabled as below -

If above feature is NOT enabled on your account, you can think of --run-id as --build-id

az pipelines commands like list, show, create, delete help you manage the pipeline definitions.
az pipelines runs commands help you manage pipeline runs for those definitions.
e.g. az pipelines list

az pipelines runs list

Hence --run-id is the pipeline runs identifier which might be listed in your url as --build-id https://dev.azure.com/MyOrganization/MyProject/_build/results?buildId=984&view=results
Please let me know if this helps.
We will try to fix the documentation for this in command help.

@geverghe Please suggest how we can improve the help text to fix the issue.

@RickKra - Would the following update work?

"ID of the run that the artifact is associated to. For example, --run-id 1"

@atbagga your 1st comment where you explain that run-id and build-id (or release-id as well?) are equivalent and show where to find those values is what I was after.
@geverghe no that update wouldn't work, because it's a fabricated value. I wanted to understand what it is and where I'd find the values that I'd want to use with those commands.

@RickKra
Addressing feedback on "what it is"
Isn't "--run - ID of the run that the artifact is associated to." adequate for understanding what it is? Which part requires more clarity or is confusing? Would mentioning "ID of the pipeline run that the artifact is associated to."
Addressing feedback on "where I'd find the values to use with those commands"
Further, for all ID related parameters, the paradigm followed is that the list command gives the ID which is to be used in the show command. Therefore, az pipelines runs show would require the ID which is fetched from az pipelines runs list. This is a consistent paradigm followed in Azure CLI. To clarify, are you facing a challenge in this paradigm or only for this specific command? This helps us evaluate if the change required is widespread or limited to just this command.
In case you want to continue the conversation offline, you can reach me at geverghe at microsoft dot com.

@RickKra Resolving the issue since it is a learning curve for using some of the commands and new terminology with the pipelines revamp. For any concerns/feedback please reach out to George as per his comment above and we will be happy to help.


Consume 0.20.0 version of operator framework api

This pull request updates the operator-framework api dependency to 0.20.0.
As part of that consumption, this updates the operator-sdk bundle validate command to consume the new hierarchy of optional validators, given the deprecation of the optional operatorhub validator. See https://github.com/operator-framework/api/pull/304 for more info.

@everettraven looks like the linter is failing because of https://staticcheck.dev/docs/checks/#SA1019 against the old validator. That's valid, because the old validator is deprecated, but do you know if there's a way to allow it anyway? Or is it expected that we remove anything that is deprecated immediately? This will be a backwards incompatible update if we just remove the validator.


Add hmac-secret (demo) support

We have use cases (e.g. https://github.com/ola-ct/Qt-SESAM) where people want to get HMAC(device-secret, provided nonce). The idea is that we can use hmac-secret for this.
Implement this here, so we can refer people to it.

Certainly possible: https://gist.github.com/nickray/78f6d91562a43980ffd8989e31557fcf
Maybe not too useful since you can't make backups, so websites would need to accept multiple passwords really.

https://github.com/solokeys/solo-python#challenge-response


Twitter won't load any tweets or profiles when script is running

I have the script installed in tampermonkey. When visiting twitter, I see an error that says "Something went wrong. Try reloading." where tweets/profiles should be (reloading did not fix this). After disabling the script in tampermonkey and reloading twitter, everything appears normal. Re-enabling the script and reloading twitter again causes the error to re-appear.

In tampermonkey settings, change "Config mode" to advance, then go to the "Security" and change "Modify existing content security policy (CSP) headers" to Yes ,then go to bottom of page, in "Experimental" , change "Add Tampermonkey to the HTML's CSP" to Yes

Having same issue, neither of above fixes seem to work on firefox

Hi all,
This could be a problem about Content-Security-Policy (CSP) and was discussed before in #19.
For Chrome users, it should just work.
For Firefox users with Tampermonkey installed, try setting:

Modify existing content security policy (CSP) headers: yes
Add Tampermonkey to the HTML's CSP: yes

For Firefox users with Violentmonkey installed, the upstream issue is tracked here:
https://github.com/violentmonkey/violentmonkey/issues/1001

Thanks. I tried this and unfortunately it didn't work. I then tried changing "Modify existing content security policy (CSP) headers" from "Yes" to "Remove entirely (possibly unsecure" just to see if it would make a difference, and that worked. I then changed it back because I don't know enough to judge if "possibly unsecure" is a problem for me, but this seems to be a possible solution.

@Jars1415  Thanks. That did the trick!


Access to Mozilla legal counsel

Will the rust foundation continue to have access to mozilla legal counsel, or what will replace it?

No, the Foundation will retain its own counsel, separate from Mozilla’s, as it will be an independent legal entity.


Kubernetes cannot be started and the local dokcer does not work.

Describe the bug
Enable Kubernetes cluster
INFO[2023-12-31T01:09:09.590675440+08:00] Starting up
WARN[2023-12-31T01:09:09.592818578+08:00] could not change group /var/run/docker.sock to docker: group docker not found
INFO[2023-12-31T01:09:09.593393522+08:00] containerd not running, starting managed containerd
INFO[2023-12-31T01:09:09.595173573+08:00] started new containerd process                address=/var/run/docker/containerd/containerd.sock module=libcontainerd pid=78
INFO[2023-12-31T01:09:09.677807228+08:00] starting containerd                           revision=8e4b0bde866788eec76735cc77c4720144248fb7 version=v1.7.8
INFO[2023-12-31T01:09:09.707068940+08:00] loading plugin "io.containerd.snapshotter.v1.aufs"...  type=io.containerd.snapshotter.v1
INFO[2023-12-31T01:09:09.709401536+08:00] skip loading plugin "io.containerd.snapshotter.v1.aufs"...  error="aufs is not supported (modprobe aufs failed: exit status 1 \"modprobe: module aufs not found in modules.dep\\n\"): skip plugin" type=io.containerd.snapshotter.v1
INFO[2023-12-31T01:09:09.709471661+08:00] loading plugin "io.containerd.event.v1…iguration; server is not ready: https://<IP_ADDRESS>:26443/v1-k3s/readyz: 500 Internal Server Error
I1231 01:09:13.307442      67 cpu_manager.go:214] "Starting CPU manager" policy="none"
I1231 01:09:13.307513      67 cpu_manager.go:215] "Reconciling" reconcilePeriod="10s"
I1231 01:09:13.307541      67 state_mem.go:36] "Initialized new in-memory state store"
I1231 01:09:13.307796      67 state_mem.go:88] "Updated default CPUSet" cpuSet=""
I1231 01:09:13.307867      67 state_mem.go:96] "Updated CPUSet assignments" assignments=map[]
I1231 01:09:13.307954      67 policy_none.go:49] "None policy: Start"
I1231 01:09:13.309315      67 memory_manager.go:169] "Starting memorymanager" policy="None"
I1231 01:09:13.309386      67 state_mem.go:35] "Initializing new in-memory state store"
I1231 01:09:13.309535      67 state_mem.go:75] "Updated machine memory state"
E1231 01:09:13.309990      67 node_container_manager_linux.go:61] "Failed to create cgroup" err="systemd not running on this host, cannot use systemd cgroups manager" cgroupName=[kubepods]
E1231 01:09:13.310031      67 kubelet.go:1480] "Failed to start ContainerManager" err="systemd not running on this host, cannot use systemd cgroups manager"
[*] service 1 exited with exit status: 1

docker failed to start the container
% docker run -itd -p 803:80 nginx

84a8214fc53a43aef9c93de3e17fe9b7308cd67ed32e4a420bd63baa19294c4c
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: systemd not running on this host, cannot use systemd cgroups manager: unknown.

To Reproduce
When I enable Kubernetes cluster in my setup I get an error
Expected behavior
No response
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.3.0
Commit: c7cc1bd78adc76441a91befa2a50c0119c9d4703 (v1.3.0)
System info:
macOS: 13.0 (22A380)
CPU: amd64, 8 cores
CPU model: Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
Model: MacBookPro16,2
Memory: 16 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2023-12-30T17-11-19.766332Z.zip

Screenshots and additional context (optional)
No response

Where did you get this config snippet from?
{
  "exec-opts" : [
    "native.cgroupdriver=systemd"
  ]
}

Removing it will fix the issue. It shouldn't be there.

Solved. Thanks.

Where'd you get that config? Would be nice to understand because it's not the first time this issue has showed up.

I kind of forgot about it too, as I was browsing some blogs and some of them prompted that I needed to add this configuration. I actually don't get it, I'm just now getting to Kubernetes.


About C+T+S+K+H checkpoints

Thank you for sharing the code.
I wonder where I can find the checkpoint for the model stated as C+T+S+K+H in the paper.

Thank you for sharing the code.
I wonder where I can find the checkpoint for the model stated as C+T+S+K+H in the paper.

Hi, the sintel.pth file in https://drive.google.com/drive/folders/1K2dcWxaqOLiQ3PoqRdokrgWsGIf3yBA_


Use "anno.addAnnotation"

I am using the function but I do not get it to work. In the original library works. What about you can give an example?
Best regards

Take a look at the last comment of:
https://github.com/igorlino/angular-annotorious/issues/8

I try to run annotoriousService.AddAnnotation(myAnnotationObject) by following the api, your answers in the issue tracker but I still cannot see the result in the screen.
I try to add an annotation either when the controller loads or when the page loads but there is no difference. Also, I have used makeAnnotable but no result.
So, if you have time please give an example (or put it to demo) on how someone can dynamically could generate a annotation.
P.S: Very helpful module by the way.

I think all need information is already documented.
The only think is that you need a storage provider

https://github.com/igorlino/angular-annotorious#using-the-angular-annotarious-service
http://stackoverflow.com/questions/30720798/how-to-use-annotorious-with-angular
https://github.com/igorlino/angular-annotorious#storage-providers

The demo page is at :   http://igorlino.github.io/angular-annotorious/
source of the demo:  https://github.com/igorlino/angular-annotorious/tree/master/demo
Hope that helps.


SIG Maintainer Nomination: Jan Hańca

Nomination Guidelines
Reviewer Nomination Requirements

6+ contributions successfully submitted to O3DE
100+ lines of code changed across all contributions submitted to O3DE
2+ O3DE Reviewers or Maintainers that support promotion from Contributor to Reviewer
Requirements to retain the Reviewer role: 4+ Pull Requests reviewed per month

Maintainer Nomination Requirements

Has been a Reviewer for 2+ months
8+ reviewed Pull Requests in the previous 2 months
200+ lines of code changed across all reviewed Pull Request
2+ O3DE Maintainers that support the promotion from Reviewer to Maintainer
Requirements to retain the Reviewer role: 4+ Pull Requests reviewed per month

Reviewer/Maintainer Nomination
Fill out the template below including nominee GitHub user name, desired role and personal GitHub profile

I would like to nominate: jhanca-robotecai , to become a Maintainer on behalf of sig-simulation. I verify that they have fulfilled the prerequisites for this role.

Nominee's GitHub Profile https://github.com/jhanca-robotecai

Reviewers & Maintainers that support this nomination should comment in this issue.

I support this nomination.

I support this nomination

I support this nomination

Nomination has been accepted at sig-simulation triage.


[Feature] Add DolphinScheduler SPI module, Plugin database schema, PluginLoader. Alert SPI and Alert Plugin basic code development. Improvement of mail Alert Plugin.

A subtask of https://github.com/apache/incubator-dolphinscheduler/issues/3049
Database table design
Plugin definition table t_ds_plugin_define
id,
plugin_name,
plugin_type
plugin_params
Plugin instance table t_ds_alert_instance
id
plugin_define_id,
plugin_instance_params
Interface design
incubator-dolphinscheduler-maven-plugin
A custom maven plug-in, its role is to automatically check the spi and plug-in related dependencies, and can support adding dolphinscheduler-plugin logo in the pom file to allow DS to automatically generate related META-INF/services files at compile time. For detailed information, please refer to: https://github.com/gaojun2048/incubator-dolphinscheduler-maven-plugin
SPI
DolphinSchedulerPlugin
DS plug-in top-level interface, all DS plug-ins must implement this interface
AlertChannelFactory
Alert plug-in factory interface. All alert plug-ins need to implement this interface. This interface is used to define the name of the alert plug-in and the required parameters. The create method is used to create a specific alert plug-in instance.
AlertChannel
The interface of the alert plug-in. The alert plug-in needs to implement this interface. There is only one method process in the interface. The upper alert system will use this method and obtain the return information of the alert through the AlertResult returned by the method.
AlertData
alert content information, including id, title, content, log.
AlertInfo
For alert-related information, when an upper-layer system calls an alert plug-in instance, the instance of this type is passed into the specific alert plug-in through the process method. It contains the alert content AlertData and the parameter information filled in by the front end of the alert plug-in instance called.
AlertResult
The alert plugin sends alert return information.
org.apache.dolphinscheduler.spi.params
Under this package is the plug-in parameter definition. Our front-end uses the front-end library http://www.form-create.com, which can dynamically generate the front-end based on the parameter list json returned by the plug-in definition Ui.
Under this package, we currently only encapsulate RadioParam, InputParam, and PasswordParam, which are used to define text type parameters, radio parameters, and password type parameters, respectively.
PluginParams This class is the base class for all parameters, and these classes inherit from RadioParam. Each DS alert plugin will return a list of AbsPluginParams in the implementation of AlertChannelFactory.
org.apache.dolphinscheduler.alert.plugin
Under this package is the relevant code for the DS Alert module to load the Alert plug-in. In the AlertChannelManager class, we also need to save the loaded plugin to the database's plugin_define table.

I am working for this issue


Update secondary font

Hi, @benhuangbmj and @sgopalani12, I've updated the secondary font on the mockup to Source Sans Pro to more closely match the primary font. I also made a slight edit to the design system:

changed the font size above the event cards to 28 ("Biweekly Tech Jams" and "Happy Hours")

@adrianad2 Got you, thanks!


cors error

when tried to upload images it return cors error for upload url

have you accept from back end side?

If you are using google cloud storage perhaps this will help?  https://github.com/fortana-co/react-dropzone-uploader/issues/130


add appendSqlLiteral support for TIMESTAMP for dumping TIMESTAMP

This support is needed for fuzzer to persist expressions upon failure when there is a TIMESTAMP type in the expression.

Here is an example of adding support for DATE type: #2940 and #2949
CC: @kagamiori


Identify keyboardDismissMode platform-specific options

Similar to TextInput's returnKeyType, comments allow to see at a glance which options are cross-platform and which are not.

@hramos

Inline comments like these are not visible in the autodocs. Perhaps edit the text above where the parameters are documented as well?

i think the intent here is to help someone reading the code.
For documentation i think it's documented above already. On android this is not supported and it will have the same behavior as 'none'.

I see. I still think the documentation can be improved here. The older docs are a bit vague - they don't clearly state that interactive is iOS only, for example.

Inline comments like these are not visible in the autodocs. Perhaps edit the text above where the parameters are documented as well?

Updated to clarify in both code & docs now @hramos


MINOR: update .asf.yaml

More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Not needed any longer.
Cf https://github.com/apache/kafka/pull/13713


ambient: fix auto-allow waypoint

Taking over #50617

@stevenctl: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
aa7d00cdfbc187addbdaed94a8601b52d89cc901
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
aa7d00cdfbc187addbdaed94a8601b52d89cc901
link
true
/test lint

gencheck_istio
aa7d00cdfbc187addbdaed94a8601b52d89cc901
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
aa7d00cdfbc187addbdaed94a8601b52d89cc901
link
true
/test lint

gencheck_istio
aa7d00cdfbc187addbdaed94a8601b52d89cc901
link
true
/test gencheck

integ-ambient_istio
aa7d00cdfbc187addbdaed94a8601b52d89cc901
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
aa7d00cdfbc187addbdaed94a8601b52d89cc901
link
true
/test integ-ambient

unit-tests_istio
47740ebb50aa7d8d31a76dab306bf3df2f58f549
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
47740ebb50aa7d8d31a76dab306bf3df2f58f549
link
true
/test unit-tests

integ-ambient_istio
47740ebb50aa7d8d31a76dab306bf3df2f58f549
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
3df654d90dade12e14fd5f232b6ba83eb60c9895
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
3df654d90dade12e14fd5f232b6ba83eb60c9895
link
true
/test integ-ambient

unit-tests-arm64_istio
5151551a51a98f7a4df3a8742fc1ff56ae35da8c
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

In response to a cherrypick label: new pull request created: #50752


SFTP.DownloadFiles bug in downloadFile

Some SFTP servers have automatic delete action on the source directory. This might lead the task to fail to download the file before the action deletes the file. The Error: " is not a valid file path.". This happens because the file is deleted from the server before the transfer can be successfully handled.
This needs to be resolved by changing the downloading of the file as async function.

This is happening because ExecuteSourceOperationMoveOrRename method tries to get the file even if the SourceOperation is set to nothing or delete.


Responsive chart

Hi, sorry to write this as an issue I just don't know how else to contact you.
I can't figure out how to make the chart responsive to the width of the parent element. I am creating an axis chart and the chart is always whatever set width I set it to, but responsive widths like 100% don't work.
I know its possible because the axis chart demo on http://www.d2bjs.org/ does exactly what I'm looking for, but I can't seem to find the implementation in the documents.
Please help, thank you.

Hi there. I'm happy to help you get this working. By default all vue-d2b charts listen to the window resize event and then whenever this triggers they will re-render according to their parent dimensions. Here is a JS Fiddle to see this in action https://jsfiddle.net/t6Lo275w/. Of course if you are using node and es6, your library and module imports will probably look different. Here you can see that the styles of the outer '.chart' container influence how the chart will be bound. If you need more control than this you can use the updateDefer method on the chart component to programmatically trigger the resize.

Hey Kevin,
Thanks so much for the reply, I got it to work. Awesome library by the way!
On Sat, Dec 9, 2017 at 8:25 AM, Kevin Warne<EMAIL_ADDRESS>wrote:

Hi there. I'm happy to help you get this working. By default all vue-d2b
charts listen to the window resize event and then whenever this triggers
they will re-render according to their parent dimensions. Here is a JS
Fiddle to see this in action https://jsfiddle.net/t6Lo275w/. Of course if
you are using node and es6, your library and module imports will probably
look different. Here you can see that the styles of the outer '.chart'
container influence how the chart will be bound. If you need more control
than this you can use the updateDefer method on the chart component to
programmatically trigger the resize.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/d2bjs/vue-d2b/issues/1#issuecomment-350484873, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AOV3IJ5e_I3FZnHu36Qm4RpJqXJafF6Wks5s-rRegaJpZM4Q7-V1
.

Glad to hear you got it working! Let me know if you have any other questions or find bugs.


nixos/roon-server: open TCP ports 9330-9332 in firewall

Motivation for this change
During the bump to 1.8-880 these became necessary, debugging took place
in the relevant PR.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@anttisoikkeli is this sufficient to fix 1.8-880?

@lovesegfault sorry for the late reply. At least for me $ sudo iptables -I INPUT 1 -p tcp --dport 9330:9332 -j ACCEPT fixed the problem, but I haven't been able to fix it by changing the configuration. Will try again with reboot. There maybe something I don't know about how it all plays out (like, does NixOS edit iptables on reboot or something). Will get back during today if I get it working by just editing the config, without running manual iptables commands.

And confirmed, this fixes the problem.
The reason I didn't get it working earlier from config:
I was using:
nixpkgs.config.networking.firewall.allowedTCPPortRanges

While I should had been using:
networking.firewall.allowedTCPPortRanges

Thanks for confirming, glad it's all working again :)


Memory issues around creating id - solution

Currently, whenever we create an id, we are allocating 600 bytes of memory for each id.
This is because chromium has a bug that does not allow using the '+' operator to allocate memory correctly: https://bugs.chromium.org/p/v8/issues/detail?id=2869
Changing this to a join will fix the size difference:
Concatenate: Shallow Size 40, Retained Size 600
Join: Shallow Size: 64, Retained Size: 64

This repo has moved to https://github.com/kelektiv/node-uuid.    Please file this over there.


Exception when running harvesters with HARVESTERS_LOG_BUFFER_MANIPULATION enabled

Describe the Bug
When running Harvesters with the environment variable HARVESTERS_LOG_BUFFER_MANIPULATION set to True, Harvesters will throw an exception.
To Reproduce
Steps to reproduce the behavior:

Set environment variable HARVESTERS_LOG_BUFFER_MANIPULATION to True
Copy the minimal example script attached at the end of this issue and adapt the path to the cti file!
Run the minimal example script
Observe log output

Expected Behavior
No errors
Actual Behavior
The following error message can be seen:
Traceback (most recent call last):
  File "C:/Users/Stefan/AppData/Roaming/JetBrains/PyCharm2021.3/scratches/scratch_22.py", line 31, in <module>
    main()
  File "C:/Users/Stefan/AppData/Roaming/JetBrains/PyCharm2021.3/scratches/scratch_22.py", line 23, in main
    pass
  File "c:\users\stefan\pycharmprojects\harvesters\src\harvesters\core.py", line 1160, in __exit__
    self.queue()
  File "c:\users\stefan\pycharmprojects\harvesters\src\harvesters\core.py", line 1257, in queue
    _family_tree(self._buffer.module.parent)
  File "C:\Users\Stefan\.venvs\fipy38\lib\site-packages\genicam\gentl.py", line 4260, in <lambda>
    __getattr__ = lambda self, name: _swig_getattr(self, Buffer, name)
  File "C:\Users\Stefan\.venvs\fipy38\lib\site-packages\genicam\gentl.py", line 93, in _swig_getattr
    raise AttributeError("'%s' object has no attribute '%s'" % (class_type.__name__, name))
AttributeError: 'Buffer' object has no attribute 'module'

Configuration

OS: Windows
Python: 3.8
Harvester: from git (see below)
GenTL Producer: Matrix Vision
Camera:  Xenics Bobcat

Reproducibility
I bisected through the harvesters commits, and the first commit that shows this issue is 3d579a7dc917f7bb25333997cd9ac5b8cd29d5f0
This phenomenon can be reproduced by other versions:

[x ] Yes, all commits between at least 3d579a7dc917f7bb25333997cd9ac5b8cd29d5f0 and master (as of to date) are affected

Actions You Have Taken

[X] I've read the Harvester FAQ page.

Additional context
import logging

from harvesters.core import Harvester, ImageAcquirer

FORMAT = '%(name)s - %(asctime)s: %(message)s'
logging.basicConfig(level=logging.DEBUG, format=FORMAT)
logger = logging.getLogger('test_application')

def main():
    h = Harvester(logger=logging.getLogger("harvesters"))

    h.add_file(
        "!!!!CHANGE_ME!!!!/mvGenTLProducer.cti"
    )
    h.update()

    logger.info(f"{h.device_info_list=}")

    ia = h.create_image_acquirer(0)
    ia.start_acquisition()

    with ia.fetch_buffer() as buffer:
        pass

    ia.stop_acquisition()  # Harvesters will lock up here.

    ia.destroy()
    h.reset()

if __name__ == '__main__':
    main()

@StefanD986 Hi, thank you for the report. I will fix that. Regards, Kazunari.


FP8 KV cache doesn't work with prefix caching

FP8 KV cache doesn't work with prefix caching since the Triton kernel does not support KV8 for now.

Can be closed now


Unused Variable Warnings Breaks Check Target

I'm trying to build Hana against my fork of Clang (built with Debug mode), but I'm getting several "unused variable" warnings that halt the build of the check target.
I can easily work around this, but the warning seems legit as the variable is in fact not used.
Should these be fixed in Boost.Hana? I see fixes for these in other test files, but I have no idea why it is not triggered in the cases I've found.
Scanning dependencies of target test.tuple.cnstr.variadic_forward
[  4%] Building CXX object test/CMakeFiles/test.tuple.cnstr.variadic_forward.dir/tuple/cnstr.variadic_forward.cpp.o
/home/jason/Projects/hana/test/tuple/cnstr.variadic_forward.cpp:54:38: error: unused variable 't0'
      [-Werror,-Wunused-variable]
        constexpr hana::tuple<Empty> t0{Empty()};
                                     ^
1 error generated.

https://github.com/boostorg/hana/blob/develop/test/tuple/cnstr.variadic_forward.cpp#L54

It doesn't do this on the develop branch. Oh well, I'll just close this. sorry :sweat_smile:


markmap frontmatter?

I think you previously disabled frontmatter from being parsed, but would it be possible to parse markmap frontmatter (only)?
So like if I wanted to set colorFreezeLevel = 2 I would add this at the top:
---
markmap:
  colorFreezeLevel: 2
---

ref. https://markmap.js.org/docs/json-options#markdown-frontmatter

Same problem. It's rather annoying to use a mindmap without parameters in a frontmatter. Please add frontmatter support to the plugin.

AdrianSimionov/obsidian-mindmap-nextgen#19
There is a development branch which already implemented most of it, feel free to provide feedback.


Logger and thread name labels for logback appender.

Hello,
I am trying to get a logger and thread labels using the logback appender.
It looks like it is possible for log4j using log4j patterns (requested in https://github.com/tkowalcz/tjahzi/issues/56 and introduced in https://github.com/tkowalcz/tjahzi/pull/62) but not in logback.
I have found the predefined level label, I managed to have labels sourced from environment such as
<label>
 <name>server</name>
 <value>${HOSTNAME}</value>
</label>

I also have mdc labels
<mdcLogLabel>
  host
</mdcLogLabel>

but none of these allow me to tag the log line with logger or thread name.
Looking at the definition of ch.qos.logback.classic.spi.ILoggingEvent, both properties are information at the same level as loglevel

Thank you for a thorough analysis and code contribution. Please allow me a few day to investigate it and evaluate the PR. Much appreciated.


Are fishing rates altered?

Maybe I overlooked it if it says so in the documentation, but my fishing rates seem to be abnormal. I have caught 210 items, and zero of them were treasure. Treasure with a default rod should account for 5% of the catches, and for 210 items without 1 single treasure drop that would be a 0.002% chance of happening. The Junk rates seem to be normal, at around 10%.
Another weird thing I have noticed is that the more mobs you kill the better enchantments their loot have. For example, I got probably 300 bow drops before one had flame, then I started getting flame bows pretty consistently after the first one. Same for higher level protection enchantments, I never got level 4s until I got one then started getting them regularly. I don't see anything about drop rates being altered in the documentation either.

Nevermind, I didn't realize the dimensions of the pool used to fish matter now. Still confused about the weird drops from mobs though, but it is a non issue.

Fishing has required "open water" since 1.16 to discourage afk fish farms.
The improving mob drops is probably the result of increasing regional difficulty: https://minecraft.wiki/w/Difficulty#Regional_difficulty.
Essentially when you spend time in one place, the mobs that spawn there get stronger, so they are more likely to have weapons/armor and for it to be enchanted.


Build error when using Template10 version 1.0.9

When I use the latest master of Template 10 (pull via GitHub, compile in VS, using local Nuget source) I get the following error message when I try to compile my project:
Der Typ "Interaction" ist in "Microsoft.Xaml.Interactivity, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35" und "Microsoft.Xaml.Interactivity, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35" vorhanden,
meaning that a type is defined twice. Does anyone have an idea how to solve this issue?
Thank you for your help and time in advance.

Thanks. T10 does not support 10586 yet.

Please make sure you remove your reference to the Behaviors Extensions SDK.

Thanks, that solved the issue.

Template10 looks to be compatible with the 10586 SDK as of the latest Git pulls. It certainly compiles in Release mode, and runs absolutely fine. I'm testing this with a production app, BTW.

It doesn't compile for me.. I get a couple 1000s errors and this in the output
[Failure] Could not find file 'C:\Users\punko\Downloads\vsTemplate10-master\Template10-master\Samples\Converters\obj\x86\Debug\App.g.i.cs'.
[Failure] Could not find file 'C:\Users\punko\Downloads\vsTemplate10-master\Template10-master\Samples\IncrementalLoading\IncrementalLoading\obj\x86\Debug\App.g.i.cs'.
[Failure] Could not find file 'C:\Users\punko\Downloads\vsTemplate10-master\Template10-master\Samples\Settings\obj\x86\Debug\Views\MainPage.g.i.cs'.
[Failure] Could not find file 'C:\Users\punko\Downloads\vsTemplate10-master\Template10-master\Samples\Settings\obj\x86\Debug\App.g.i.cs'.
[Failure] Could not find file 'C:\Users\punko\Downloads\vsTemplate10-master\Template10-master\Samples\BottomAppBar\obj\x86\Debug\App.g.i.cs'.
[Failure] Could not find file 'C:\Users\punko\Downloads\vsTemplate10-master\Template10-master\Samples\BehaviorSample\obj\x86\Debug\App.g.i.cs'.

oops forgot to move it away from Any CPU.. Moved it to x86 and BusyIndicator project does not run but I deleted that


All-In-One Azure Active Directory data connector doesn't enable Audit or Sign-in Logs

Describe the bug
While the All-in-One "enables" the Azure Active Directory data connector it doesn't actually enable either of the diagnostics settings ("AuditLogs" or "SignInLogs") to be sent to the LA Workspace.
To Reproduce
Steps to reproduce the behavior:

Create custom deployment, using azuredeploy.json
Click into Sentinel -> Data Connectors -> Azure Active Directory
Note that it doesn't ever show "Connected"
Click into Azure Active Directory connector, and enable "Sign-in Logs" (in a Azure AD P1/P2 enabled environment) or "Audit Logs" (OR, go into Azure Active Directory, select Diagnostic Settings, add new diagnostic setting, and enable "AuditLogs" and "SignInLogs" (again, assuming Azure AD P1/P2) and direct it to your LA Workspace.

Expected behavior
I expected that the ARM Template would enable at least Audit Logs when you enabled the Azure AD connector.
Desktop (please complete the following information):

OS: Windows
Browser: Edge
Version: 92.0.902.67

HI @JonTheNiceGuy ,
There are two versions of All-in-One, one based on ARM template and one based on powershell script. The one based on powershell does enable Azure AD Audit and SignIn logs, but the one based on ARM doesn't do that.
We tried to make this clear in the documentation posted here: https://github.com/Azure/Azure-Sentinel/tree/master/Tools/Sentinel-All-In-One, but let me know if we should make it more clear.
Regards

answered above


Expose the handle bounds

Please describe the feature that you want to propose
Hi all 👋
I see that nodes are storing the position of their handles internally, but this is not exposed currently.
I have a use case where it would be very helpful to get the position of those handles (custom handles sticking out of the node + custom ConnectionLine that has a placeholder node on the tip snapping to the node when the cursor is either over the handle or the node itself).
Any reason to not expose this information, or is there any other way to access it that I am missing? I am currently using node[Symbol.for('internals')]?.handleBounds?.target which works but feels very hacky.
Thank you!

That's the way! You could import the symbol like:
import { internalsSymbol } from 'reactflow'

and then do:
node[internalsSymbol]?.handleBounds?.target


get_link does not url encode "+" symbols correctly, causing incorrect/corrupt URLs.

A get_link call on a file that has a "+" in it's name does not get URL encoded correctly, and thus the actual fetch results in a NoSuchKey error from Amazon S3.
i.e. given a key called "document_versions/123456/foo + bar.pdf"
this SHOULD ENCODE TO "document_versions/123456/foo%20%2B%20bar.pdf"
instead, it encodes to "document_versions/123456/foo%20+%20bar.pdf"
which in turn actually decodes to: "document_versions/123456/foo   bar.pdf" (the "+" is replaced by a space).

This is possibly related to https://github.com/rightscale/right_aws/issues/109

Indeed.  The problem was changing CGI.escape -> URI.escape in this commit:
https://github.com/rbroemeling/right_aws/commit/78d63f59c913546f371d5aa4eae1708267b25774
URI.escape does not properly escape + symbols:
irb(main):002:0> URI.escape("document_versions/123456/foo + bar.pdf")
=> "document_versions/123456/foo%20+%20bar.pdf"

Suggest that the code in https://github.com/rightscale/right_aws/commit/78d63f59c913546f371d5aa4eae1708267b25774 be changed back to CGI::escape, and then .gsub('+', '%20') be called on the result.  This results in an actually correct encoding, as far as I can tell:
irb(main):015:0> CGI.escape('foo + bar.pdf').gsub('+', '%20')
=> "foo%20%2B%20bar.pdf"

I have opened a pull request for this change:
https://github.com/rightscale/right_aws/pull/115

Hi
Could you plz try the "development" (not "master") branch and see if the issue is fixed there or not.
Thank you!

Hi,
I can confirm that the current development branch of right_aws fixes the issue and passes all known test cases that we have tried (i.e. spaces, plus signs, and other 'special' character tests).
When will we see the code move into master/into a release?
Thanks!


fix broken link

@gholliday Thank you for for fixing this. I am merging this PR and it should be live soon.


Implement static checks related to NNBD

The non-exhaustive list is the following (items can be further turned into issues):

Checks for null-aware calls at call sites (for example, int? x; x.isEven;).
Checks for nullable types in supertypes.

This issue was meant as an umbrella issue for static checks related to NNBD.  As such, it's a duplicate of https://github.com/dart-lang/sdk/issues/40054.


Functional Tests For Grype Integration

What this PR does / why we need it:
Add functional tests for five endpoints in policy engine that will be affected by the Grype integration.
These tests will allow us to check for regressions in vulnerability scanning after the integration work is complete.
Policy Engine endpoints tested:
From file anchore_engine/services/policy_engine/api/controllers/synchronous_operations.py

image_ingress

API ROUTE: POST /images
JIRA TICKET: ENTERPRISE-79

get_image_vulnerabilities

API ROUTE: GET /users/{user_id}/images/{image_id}/vulnerabilities
JIRA TICKET: ENTERPRISE-80

query_images_by_vulnerability_get

API ROUTE: GET /users/{user_id}/query/images/by_vulnerability
JIRA TICKET: ENTERPRISE-85

query_vulnerabilities_get

API ROUTE: GET /query/vulnerabilities
JIRA TICKET: ENTERPRISE-86

sync_feeds

API ROUTE: POST /feeds
JIRA TICKET: ENTERPRISE-87

Which issue this PR fixes (optional, in fixes #<issue number>)(, fixes #<issue_number, ...) format, will close the issue when PR is merged: fixes #:
Closes the following enterprise JIRA tickets:

ENTERPRISE-79
ENTERPRISE-80
ENTERPRISE-85
ENTERPRISE-86
ENTERPRISE-87

Special notes:
Commits on this branch are cherry-picked and and squashed from working branch.
Source branch: https://github.com/anchore/anchore-engine/tree/grype-tests
Related: https://github.com/anchore/test-images/pull/23
NOTE: 82 of the files changed are json. So filter those out if you want to skim over the PR.

change api env vars to default to CI values


[FLINK-29687] Do not throw exception when Lookup table is empty

PreAggregationITCase#testMergeInMemory is unstable


freeoffice: fix sha256

Motivation for this change
The sha256 sum has changed upstream.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @danieldk

This seems to be the hash of the new release (971). They seem to replace the older version as well. So, maybe you could also bump up the version?
I have also posted on their forum to ask if they can keep older tarballs as-is:
https://forum.softmaker.com/viewtopic.php?f=320&t=19327

Turned it into a version bump.


fix readme error and add a tip

fix config error, and add a tip for formatters list
Oh, it is prettierd, not prettier_d, it gives is that "No config found". At first I thought it was because the configuration of pretter was not given.
Then I started to troubleshoot my configuration file, and finally I found out that the sample configuration in the readme was wrong 🥹

Thanks!


Fix deprecation warning in Bifold core

This message shows up when running unti tests, and some times via the metro debug messaging when developing:
@hyperledger/aries-bifold-core:   ● Console
@hyperledger/aries-bifold-core:     console.error
@hyperledger/aries-bifold-core:       ViewPropTypes will be removed from React Native, along with all other PropTypes. We recommend that you migrate away from PropTypes and switch to a type system like TypeScript. If you need to continue using ViewPropTypes, migrate to the 'deprecated-react-native-prop-types' package.

Might have fixed with the new camera library


[Feature]  Throw an error or warning in components if a cloud name is not set

Feature Request
Is your feature request related to a problem? Please describe.
A Cloud name is required, whether set via VITE_PUBLIC_CLOUDINARY_CLOUD_NAME or via the config prop. The component should throw an error or warning in the event that it's not configured.

@matiasfha I can work on this issue

Hi @HeetVekariya Thanks for taking care of this issue.
Go ahead and work on it, let me know if you need any help or clarification

@HeetVekariya i have this same Issue filed in Next Cloudinary and one suggestion the person who wanted to work on it provided was to create a helper function to perform this check and add it to the various locations as ultimately this is something all of the components need:
https://github.com/colbyfayock/next-cloudinary/issues/264#issuecomment-1749912285
perhaps there's a similar solution
you both can feel free to discuss this in my discord server if you'd like: https://spacejelly.dev/discord
Cloudinary has a discord server but there's not really a place that makes sense for that kind of discussion at this time, but linking in case generally interested: https://discord.gg/cloudinary


Allow overriding number of cores used by reconstructors on the CLI

Please describe the use case that requires this feature.
Useful for GRID processing / other job systems with resource management.
Describe the solution you'd like
Add a CLI option that allows overriding the number of cores used by reconstructors e.g. SKLearn based reconstructors to the train and apply tools.
This is needed to be able to set different n_cores for training and application.
Describe alternatives you've considered
Additional context

I'd propose to add an n_jobs property to the Reconstructor base API. Reconstructors that don't do multiprocessing can just ignore this but reconstructors that are able to use multiple threads must obey this setting.


feat: Comment system, thumb up number or  reader number statistics

Anyway, implement something the reader can interact with me.

Powered by giscus currently:

May use Waline instead of it in the future.


Fix gdscript analyzer error when instantiating EditorPlugins.

Continue from originally https://github.com/godotengine/godot/pull/74025

Waiting to confirm that the original author has indeed abandoned their PR

@MikeSchulze Since the original author doesn't respond for several days, feel free to continue their work.

@dalexeev done

Ready for review

@dalexeev done

Thanks!


Wow W3TC on WP has been updated to 0.9.5!

And look at that change log ...Lots of fixes

Many of them taken from right here :)

Wow! Ok.. Many of them taken from right here... but many other are totally new...

Mhh same version of fix-w3tc <IP_ADDRESS>...

I hope he puts it on Github. The WPTavern article from a few months ago quoted him saying this.
Github is so much better than Wordpress forums for discussions.
#FrederickOrBust

I have an idea:
You contributors to fix-w3tc can offer a companion plugin. I think the new version at WP still has the AMP error and sitemap priority error.
In addition, the new version of W3TC offers progressively loading CSS as a paid option.
You could make a companion plugin which creates more tabs in the original plugin and have this (such as a box for critical css, unchecking W3TC css optimization) and bugfixes and other things such as pushing assets (HTTP2 server side push).

@vijayaraghavanramanan I wonder if will actually put it on GitHub. Also there is quite a lot of things going on in the new plugin that will cause issues for some. Such as the unannounced requirement of >=PHP 5.3.
Don't know what the minium PHP version is currently.

I don't understand Frederick, he disappears for a year and come back with a huge update, with so many new feature, so many bug fix an so many new and old bugs.
Why?
He could come back with a little update for fix some old bugs like the php7 compatibility and the latest security issue and all the people would be happy.
The old version works most of the time, this version has so many fatal issue.

I think he may have felt pressured to release the new version, given the newly discovered XSS vulnerability, so he pushed v0.9.5 without extensive testing ... but that's just my theory.
I already started fixing some of the bugs mentioned in the wordpress forums, in case Frederick decides to disappear again.
My branch can be found here: https://github.com/charlesLF/fix-w3tc/tree/w3tc-0-9-5
Moving on, wha about if we push the changes we have made in fix-w3tc as a new plugin in the WP repo. That way people who don't feel comfortable with the re-structured W3TC version could still its power with the 0.9.4-fix version for backward compatibility.
This is similar to what happened with the NextGen/NextCellent plugin

I already started fixing some of the bugs mentioned in the wordpress forums, in case Frederick decides to disappear again.

ehehhehe :D

Moving on, wha about if we push the changes we have made in fix-w3tc as a new plugin in the WP repo.

eh... a this point it's not bad idea.

Yeah I too think the vulnerability forced him to release. WP Tavern and Yoast's blog didn't sound good.
But Frederick is a great great guy. I am sure he has some important things due to which he couldn't keep his promises.
Also no other plugin comes even close. I mean I try them sometime but quickly uninstall soon. So W3TC is so good.
This fix-w3tc at Wordpress looks like a good idea.

But Frederick is a great great guy. I am sure he has some important things due to which he couldn't keep his promises.

yes I agree. however, it should improve communication with the community. Also at this time, he did not say anything: no tweet, no post, nothing! why?

But Frederick is a great great guy. I am sure he has some important things due to which he couldn't keep his promises.
I agree, and I admire the work done in W3TC. It is by far my favorite caching/optimization plugin and has done wonders on the many websites that I use it on, and the coding approach used in the plugin (whether in v0.9.4 or v0.9.5) shows great skill.
That was actually the main reason I got excited about contributing here. It felt as if I'm giving back to a plugin that has given me a lot for free!
I also understand the pressure of having a plugin used by 1+ million website, and having to keep up with all the problems that could arise from the different configurations.
My issue is with the lack of communication, as @nigrosimone pointed out. It is clear that there are a lot of people in the community that are ready to give back to W3TC, and for free. This repository is the biggest proof.
I don't appreciate all the reports on the WP support forum of people purchasing Premium support and never receiving any replies. Heck, the new version even increased the price for premium support https://plugins.trac.wordpress.org/changeset/1502418
Instead of keeping everyone in the dark, I would recommend that Frederick harnesses the power of open source by putting the plugin on github, and allowing for different people to contribute to the fixes and code quality of the project.

The other issue, ends up being if a user uses the GitHub Updater plugin to install the forked version of W3TC. But on the updates screen in WP it will show that the current update is 0.9.5. So if a user does update from the forked version to the repo current version, it will be confusing for the user, which version they are using.

@lukecav .. IF the fix-w3tc is to be released as a separate plugin, it should be released under a new name to clearly distinguish it from the official plugin.
It should also gracefully deactivate in case the official w3tc plugin is active and give the admin a notification saying that the community edition can not run side-by-side with the official edition.

I believe the best way is to see if the GitHub can be opened and we can work with Townes on it because creating a W3TC fix plugin won't help the million active users of that plugin only the few that switch.

I used to know the plugin like the back of my hand, at least pre 0.9.5. Even thought about making a proper fork. Talked with Simone about contributing here and I just might. But I wouldn't just want to fix issues with current release, but make it more structurally sound.

The best scenario is like wp-minify-fix which is a fix of wp-minify. Someone named NodeCode fixed the original plugin and even got the original author to be a co-author of wp-minify-fix!

The other issue, ends up being if a user uses the GitHub Updater plugin to install the forked version of W3TC. But on the updates screen in WP it will show that the current update is 0.9.5. So if a user does update from the forked version to the repo current version, it will be confusing for the user, which version they are using.

Luke has a point. Sometimes servers update Wordpress and/or plugins without asking even if you've set the option to not do so. And since there was a security issue, some hosts might run a patch across all sites to update it. So a solution with versioning is needed for users of this fork.

it will show that the current update is 0.9.5

this is a strange coincidence... same version of fix-w3tc.

I don't really see the naming of versions to be a strange coincidence. Think the update was planned to be 1.0.0 but because of the security issue he published everything under a point release .9.5 I see nothing weird about that naming convention since it's clear the actual release has done a ton when it comes to feature integration ~

new update it is going wrong...

This is one interesting thing that I noticed in the new release:
https://plugins.trac.wordpress.org/changeset/1502418

@Tarun80 yep, i too have noticed it.

Less than 15 Minute Email Support $175 USD

it seems a little too expensive....

From what i can tell most people who are complaining are those running older versions of php (5.2 in particular)

The minimum version of PHP seems to be 5.3 on W3 Total Cache on the repo now. https://wordpress.org/support/topic/new-w3tc-requires-php-5-3/

@lukecav we are at work https://github.com/charlesLF/fix-w3tc/pull/3/commits/a595a46ba6956fe594ba2871a6576da2eb746379

@nigrosimone
Nice.

Frederick Townes says he might push another release fixing bugs here:
https://www.w3-edge.com/weblog/2016/09/w3-total-cache-v0-9-5/
WP Tavern also wrote on it: https://wptavern.com/w3-total-cache-0-9-5-packages-xss-vulnerability-patch-with-major-update


Release/2.16.3

Let's use this PR for more next release.

The maintainers of this repo require that all pull request submitters agree and adhere to the following:

[ ] I have read and agree to the contribution guidelines.
(required)
[ ] All related documentation has been updated to reflect the changes made. (required)
[ ] My commit messages are cleaned up and ready to merge. (required)

The maintainers of this repository require you to select the semantic version type that
the changes in this pull request represent.  Please select one of the following:

[ ]  major
[ ]  minor
[x]  patch
[ ]  documentation only

Shall I tag 2.17.0 instead?

Cause it was new features 2.16.3 is ok since there are no super exciting features.

I just imagine that there would be an urgent bug that we need to fix and that would be 2.16.3 instead. I've never used git flow` to manage a project, is it a more common practice to release a minor than a patch version?

We need to also prepare a change log.

Added a message file, please review again.

it looks like maintainerd is not auto tagging the release.

I pushed 2.16.4 manually https://github.com/divmain/GitSavvy/releases/tag/2.16.4


Cannot compile with Profile build type

I'm trying to compile with CMAKE_BUILD_TYPE=Profile but I'm getting the following error:
/home/dan/anaconda3/envs/sparta/bin/../lib/gcc/x86_64-conda-linux-gnu/12.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: /home/dan/anaconda3/envs/sparta/bin/../x86_64-conda-linux-gnu/sysroot/usr/lib/../lib/gcrt1.o: relocation R_X86_64_32S against symbol `__libc_csu_fini' can not be used when making a PIE object; recompile with -fPIE
/home/dan/anaconda3/envs/sparta/bin/../lib/gcc/x86_64-conda-linux-gnu/12.3.0/../../../../x86_64-conda-linux-gnu/bin/ld: failed to set dynamic section sizes: bad value

Has anyone else encountered this?

I don't have that issue, but a different one.  Specifically stf is built with LTO while the linking stage doesn't accept it.  Got a flag mismatch.
Have you tried with clang?

Same error as this?
/home/dan/anaconda3/envs/riscv_perf_model/bin/../lib/gcc/x86_64-conda-linux-gnu/10.4.0/../../../../x86_64-conda-linux-gnu/bin/ld: stf_lib/lib/libstf.a: error adding symbols: file format not recognized
clang-14: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [CMakeFiles/olympia.dir/build.make:131: olympia] Error 1
make[1]: *** [CMakeFiles/Makefile2:360: CMakeFiles/olympia.dir/all] Error 2
make: *** [Makefile:91: all] Error 2

Managed to fix it by moving the setup_stf_linker out of the Release build only
diff --git a/CMakeLists.txt b/CMakeLists.txt
index bee99e2..4fc4298 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -38,9 +38,10 @@ set (DISABLE_STF_DOXYGEN ON)

 if (CMAKE_BUILD_TYPE MATCHES "^[Rr]elease")
   set (FULL_LTO true)
-  include(${STF_LIB_BASE}/cmake/stf_linker_setup.cmake)
-  setup_stf_linker(false)
 endif()
+include(${STF_LIB_BASE}/cmake/stf_linker_setup.cmake)
+setup_stf_linker(false)
+

 # Use ccache if installed
 find_program (CCACHE_PROGRAM ccache)

Will create PR

Yep. That’s the one. Thanks for debugging On Mar 5, 2024, at 4:42 PM, danbone @.***> wrote:
Managed to fix it by moving the setup_stf_linker out of the Release build only
diff --git a/CMakeLists.txt b/CMakeLists.txt
index bee99e2..4fc4298 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -38,9 +38,10 @@ set (DISABLE_STF_DOXYGEN ON)
if (CMAKE_BUILD_TYPE MATCHES "^[Rr]elease")
set (FULL_LTO true)

include(${STF_LIB_BASE}/cmake/stf_linker_setup.cmake)
setup_stf_linker(false)
endif()
+include(${STF_LIB_BASE}/cmake/stf_linker_setup.cmake)
+setup_stf_linker(false)

Use ccache if installed
find_program (CCACHE_PROGRAM ccache)
Will create PR
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

@danbone Can I take up this issue?

Unless Dan disagrees, feel free to take it.  I just reproduced the original issue.

@klingaard didn't this get fixed by
https://github.com/riscv-software-src/riscv-perf-model/commit/9d9a345060039594b2782520e743ab5ec2a613d3

@danbone Can I take up this issue?
If you allow me to do so..
I think in this issue we are supposed to work on "-fPIE" error during compilation, with "CMAKE_BUILD_TYPE=Profile" in conda environment. It will be solved by adjusting compiler flags for PIE compatiability. I am interested to work on this

Yes, absolutely fine by me


Avalonia

Upgrade Avalonia version？

If you're suggesting upgrading AvaloniaRibbon to Avalonia 0.10.0, I'll be looking into that at some point once the first 0.10.0 stable release is available.

If there are interface changes, you can keep the old version and update to 0.10 preview version

update 0.10?

I have an updated version mostly working with 0.10. To get it working I had to change the AvaloniaProperty.Register method since the signature changed (the verification thing Ribbon uses seems to do more than just verify). The extra particular syntax on some of the getters wanted explicit casts for the enums as well. With all of that it's running but I have two problems in the demo app. First, the initial ribbon renders but it's all white. Toggling back and forth across ribbon tabs work fine though. I'm not sure if it's a problem with that validation method doing some magic or something else. Second, the larger gallery sizes never re-expand with window resize. They will stay at whatever their smallest sizes are left the rest of the time.  You can see my progress in this branch:
https://github.com/HankG/AvaloniaRibbon/tree/update-avalonia-10

@HankG   thanks

@HankG  Can you help me solve a problem? I want to combine with dock, but I can't use ribbon window.
wieslawsoltes/Dock #168