Support for Julia language

Hi,
This seems a great plugin. Could it be implemented for Julia as well? The syntax is very similar to the Ruby one.
Thank you!

I'm open to having Julia support added, but since it's not a language I've ever used I wouldn't implement it myself and instead would be willing to help guide someone with Julia experience to implement it. I'll give some details below on how to write the queries.
You'll need to know how to write tree-sitter queries, see https://tree-sitter.github.io/tree-sitter/using-parsers#pattern-matching-with-queries. Make a file queries/julia/endwise.scm, this is where the queries will go. There will be generally two queries for each thing which can have an end node added to it: when the parsing fails, and when the parsing succeeds. To get a better understanding of this, let's take a look at Lua which has a decently simple grammar.
In Lua, we have the following queries, https://github.com/RRethy/nvim-treesitter-endwise/blob/master/queries/lua/endwise.scm. Let's focus on the function definition queries, of which there are two:
((ERROR ("function" . (_)? . (parameters) @cursor) @indent) (#endwise! "end"))

The first query with ERROR is simple and will match the following:
function foo()<cursor>

Since we are working with syntax trees that have an error in them, we will expect the parser to be in a weird state and not be able to parse this code into a function_definition node, instead it gets parsed as a sequence of tokens and nodes and placed into the generic ERROR node to signify that the parser couldn't make sense of this sequence of tokens. In this example, we have a "function" followed by an (identifier) followed by (parameters). We also have two captures, @cursor to mark where we expect the users cursor to be in the query match, and @indent to signify what kind of indentation the end node should have when we place it. Lastly, we also have the #endwise! directive which is how we can configure the end node, if we made it foo then the text that gets inserted would be that.
Let's now take a look at the second query:
((function_definition parameters: (_) @cursor) @endable @indent (#endwise! "end"))

This one is a bit more complicated but it's a side effect of tree-sitter generating parsers which follow maximal-munch. Let's take a look at a piece of code:
function foo()
  function bar()<cursor>
end

If we look at this, we know that the end token is for the foo function, but the parser will parse it as part of the bar function which means the bar function will have a valid parse tree even though it shouldn't. To get around this, we can use the @indent in conjunction with the @endable capture group, if the last child of the node captured by @endable has a different indentation than the node captured by @indent, and if an ancestor node in the syntax tree has an error, then we can assume that the end node is actually meant to be a part of a different node. As such, we insert an end node with matching indentation.
To help you with writing queries, try writing some Julia code which you would expect to have an end node added, then run :TSPlayground and inspect the syntax tree (pressing a in the playground shows anonymous nodes). You can also add tests in tests/endwise/julia.rb that follow tests/endwise/lua.rb to verify your queries work. The consist of a few lines prefixed by a - with a █ to mark the initial cursor position, followed by lines prefixed by a + to show the expected end state of the text.

Thank you much for the detailed guidelines. I am myself still learning the language, so it will be a good challenge. I am however quite occupied these days, so i will not be able to give it a grasp in the coming days, but as soon as I do, I will start working on it.
As you say, I think it will be straightforward since the syntax is so similar to ruby and lua.
I will try to make a PR when it is ready 😄.

I think @jasonrhansen has started work on adding Julia support FWIW (https://github.com/jasonrhansen/nvim-treesitter-endwise/tree/julia).

Oh, I just saw that! Well awesome then.

Can you review the Julia PR linked to go through the use-cases.

I will be able to check it after next week (exams).
Sorry for the delay!

Have you had a chance to take a look through the PR?

Yes, it seems OK!
The only thing I don't understand is why, when I'm here
for i in 1:5
    |
end

and press ENTER, then it triggers another end.

Can you comment that on the PR as part of a PR review.

Bumping this, can you provide a PR review on that PR raising the issues you found.

https://github.com/RRethy/nvim-treesitter-endwise/pull/4#issuecomment-1066255471


feat: fields and population selection with Local API / REST

Description

The problem: you want to create a link field, which has relation to Pages collection. But your Pages collection contains many many fields and as well relations, fetching all of that just for slug seems too much unnecessary.
This PR perfectly solves this i believe.
Added 2 parameters to operations / endpoints (select, populate) and 1 parameter to a relationship field config (defaultPopulate), more examples in the separated test config:
select - allows to specify which fields to return from a database.
Considerations: the document's id, array / blocks items  that are selected id's, blockName, blockType, relationship ids within selected field depth - are automatically selected.
// returns only title and label - doc.title, doc.label
const post = await payload.findByID({
  collection,
  id,
  select: {
    title: true,
    label: true,
  },
})

// returns array items and `title` inside of them, doc.array[0].title
// this could be a group / tab as well, if so - doc.group.title
const post = await payload.findByID({
  collection,
  id,
  select: {
    array: {
      title: true,
    },
  },
})

// returns array items and all fields inside of them. This could be a group / tab as well.
const post = await payload.findByID({
  collection,
  id,
  select: {
    array: true
  },
})

// the same as with array, but with block that has slug "section" - doc.blocks[0].title
const post = await payload.findByID({
  collection,
  id,
  select: {
    blocks: {
      section: {
        title: true,
      },
    },
  },
})

populate - allows you to specify which relationship fields to populate, as well you can specify select for the current population and nested populate. It still respects depth parameter just to not break the current logic, but we can tweak that i think, it won't populate other relations in the same depth, but if your depth value is not enough it won't populate specified fields.
Example:
// Populates only `item` field doc - all fields.
const doc = await payload.findByID({
  collection: docWithRelationSlug,
  id: docWithRelationId,
  depth: 1,
  populate: {
    item: true,
  },
});

// Populates only `item` feield doc and selects only title field from population
const doc = await payload.findByID({
  collection: docWithRelationSlug,
  id: docWithRelationId,
  depth: 1,
  populate: {
    item: {
      select: {
        title: true,
      },
    },
  },
});

// Populates `item` field doc and `nested` field doc inside, all fields
const doc = await payload.findByID({
  collection: docWithRelationSlug,
  id: docWithRelationId,
  depth: 2,
  populate: {
    item: {
      populate: {
        nested: true,
      },
    },
  },
});

// Populates `item` inside nested to array field
const doc = await payload.findByID({
  collection: docWithRelationSlug,
  id: docWithRelationId,
  depth: 1,
  populate: {
    'array.item': true,
  },
})

// Polymorphic population of the field named `polymorphic`
const doc = await payload.findByID({
  collection: docWithRelationSlug,
  id: docWithRelationId,
  populate: {
    polymorphic: [
      {
        relationTo: "relationships-items-nested",
        value: {
          select: {
            title: true,
          },
        },
      },
    ],
  },
});

defaultPopulate - configuration for relationships / upload fields:
// By default if in query `populate` is not provided, will be used this configuration for that field
{
  name: 'withDefaultPopulate',
  type: 'relationship',
  relationTo: 'relationships-items',
  defaultPopulate: {
    select: {
      title: true,
    },
  },
},

// The same for polymorphic
{
  name: 'polymorphicDefault',
  type: 'relationship',
  defaultPopulate: [
    {
      relationTo: 'relationships-items',
      value: {
        select: {
          title: true,
        },
      },
    },
  ],
  relationTo: ['relationships-items', 'relationships-items-nested'],
},

[x] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] I have added tests that prove my fix is effective or that my feature works
[x] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

Hi again!
I've implemented this feature for relationships with separated populate property.
Examples:
`

Hey @r1tsuu super interesting PR, thank you for your contribution!
One thing I'm worried about are hooks. What if you added a field or collection hook to a field which depends on the value on another field? That hook would break if the other field isn't queried.

Hey @r1tsuu super interesting PR, thank you for your contribution!
One thing I'm worried about are hooks. What if you added a field or collection hook to a field which depends on the value on another field? That hook would break if the other field isn't queried.

Yes i worried about that too, but what i think is just if you're using you just need to be ensure that not selected data isn't used outside, like in hooks

Hey @r1tsuu super interesting PR, thank you for your contribution!
One thing I'm worried about are hooks. What if you added a field or collection hook to a field which depends on the value on another field? That hook would break if the other field isn't queried.

Yes i thought about this too and i think  that's basically the cost of optimizations. You need to ensure that the non selected data isn't used in the hooks. Also it's only a problem here with beforeRead and afterRead i believe, most of our business logic in the other hooks, in beforeValidate beforeChange afterChange nothing should be changed since this PR doesn't add select for update and create.

@AlessioGr Hi, any chance it could be reviewed? Or is it something that you don't want bring to now? While there's no a discussion with roadmap to this, i believe i saw somewhere that field selection feature is planned.

Hey @r1tsuu just a quick update from our side, this definitely needs to make its way into Payload but our team won't likely have bandwidth to give this PR the justice that it needs until at least a week from now or so. But we'll get there.
My big question will be TypeScript. I have not looked at the code yet here, but have you solved typing accordingly as well?
I will report back here shortly!

Hey @r1tsuu just a quick update from our side, this definitely needs to make its way into Payload but our team won't likely have bandwidth to give this PR the justice that it needs until at least a week from now or so. But we'll get there.
My big question will be TypeScript. I have not looked at the code yet here, but have you solved typing accordingly as well?
I will report back here shortly!

Hi, thank you for the message here!
About TypeScript:
Altought i typed parameters populate and select

export type Select = {
  [key: string]: Select | boolean
}

export type PopulatePolymorphicValue = {
  relationTo: string
  value:
    | {
        populate?: Populate
        select?: Select
      }
    | boolean
}[]

export type PopulateSingleValue = {
  populate?: Populate
  select?: Select
}

export type PopulateValue = PopulatePolymorphicValue | PopulateSingleValue

export type Populate = {
  [key: string]: PopulateValue | boolean
}

It's far from full-typed system for this feature of course, but it matches our current implementation of type for where.
Do you mean it should work like in for example Prisma or Drizzle?
I don't think i have a good idea on how to implement that for populate, especially for polymorphic relations, these are hard ones here. We also haven't solved that for our current depth parameter.
It maybe would be better if we had some additional type-gen for these params, like i believe we plan with Where.
I can try to experiment with it this week, do you think it's fine for type-gen here or should i avoid it?
Also i have few considerations:

Currently not selected array/blocks fields are returned as [], not undefined. As well for non selected group fields - {}. Altough i'm not fetching them from database, it seems like we're applying to them this default value in afterRead,
Non selected fields are still present in the returned data object, but with undefined value. (the reason here is the same as in 1)
Depth parameter is still respected, meaning that:

// This will work
const doc = await payload.findByID({
  collection: docWithRelationSlug,
  id: docWithRelationId,
  depth: 1,
  populate: {
    item: true,
  },
});

// This will work. And only `item` will be populed on the depth level 1
const doc = await payload.findByID({
  collection: docWithRelationSlug,
  id: docWithRelationId,
  depth: 1,
  populate: {
    item: true,
  },

// This - won't, as haven't increased `depth` to 2.
const doc = await payload.findByID({
  collection: docWithRelationSlug,
  id: docWithRelationId,
  depth: 1,
  populate: {
    item: {
      populate: {
        nested: true,
      },
    },
  },
});
});

This was done in order to ensure that we can't exceed maxDepth and to keep changes as small as possible.

I did some research on how i can add type safetely here for select property
But to achieve full type safetely i need to rethink some parts

for select property instead of writing this for nested fields:
array: { nested: true }
write
array.nested: true

Keys generation:

type-fest package with it's PickDeep type should help here
Also i think i still need some additional utillity type generation here to payload-types.ts

Don't select any fields by default if select property is provided, even id. I think it would be more right actually.

Fix those, probably i'd need to modify a bit afterRead to not assign undefined or [] to non selected fields.

Currently not selected array/blocks fields are returned as [], not undefined. As well for non selected group fields - {}. Although i'm not fetching them from database, it seems like we're applying to them this default value in afterRead,

Non selected fields are still present in the returned data object, but with undefined value. (the reason here is the same as in 1). They could be deleted with JSON.stringify, meaning also that it's only in Local API, in REST API response we won't see them.

Made select a bit less verbose, now it's just an array of string paths - `['array.title', 'description']
Made ensure that fields are deleted in afterRead, for example before i had for non selected fields:

// non selected
{
id: 1;
selected: "value",
group: {},
array: [],
blocks: [],
title: undefined
}

now it's just
{
id: 1,
selected: "value"
}

which is more right i think.

Hey @r1tsuu just a quick update from our side, this definitely needs to make its way into Payload but our team won't likely have bandwidth to give this PR the justice that it needs until at least a week from now or so. But we'll get there.
My big question will be TypeScript. I have not looked at the code yet here, but have you solved typing accordingly as well?
I will report back here shortly!

Hi, managed to do types in my API client client package that integrates with my plugin for fields-selection
// Generated
export interface Page {
  id: string;
  title: string;
  updatedAt: string;
  createdAt: string;
  _status?: ('draft' | 'published') | null;
}

const client = new PayloadApiClient<P>({ apiURL: 'http://localhost:3000/api' });

const { docs } = await client.find({ collection: 'pages', select: ['id', 'createdAt'] });

docs[0].createdAt; // ok
docs[0].id; // ok
docs[0].updatedAt; // err, Property 'updatedAt' does not exist on type 'Pick<Page, "id" | "createdAt">'

As well suggestions for select option

The magic behind this: https://github.com/r1tsuu/payload-enchants/blob/5ee60d40c2e31ce34625e36a397c3d461a99fd9a/packages/sdk/src/index.ts#L102
async find<T extends keyof C['collections'], K extends (keyof C['collections'][T])[]>({
    collection,
    ...toQs
  }: {
    collection: T;
    depth?: number;
    draft?: boolean;
    fallbackLocale?: C['locale'];
    locale?: 'all' | C['locale'];
    page?: number;
    select?: K;
    sort?: `-${Exclude<keyof C['collections'][T], symbol>}` | keyof C['collections'][T];
    where?: Where;
  }): Promise<
    PaginatedDocs<K extends undefined ? C['collections'][T] : Pick<C['collections'][T], K[0]>>
  > {
    const qs = buildQueryString(toQs);

    const response = await this.fetcher(`${this.apiURL}/${collection.toString()}${qs}`);

    return response.json();
 }

But this works only for 1-st level fields. I honestly have no idea about nested fields.

This work has been restarted from a new PR: https://github.com/payloadcms/payload/pull/8550


mos_fopen returns 0 after bbcbasic exits

Hi Dean,
An ADL=1 binary, written in C with the standard init.asm from the 'Hello World' example, that opens a file using the bare minimum assembly code for mos_fopen, mos_fopen only works when no bbcbasic.bin has been running previously.
After *bye from bbcbasic, mos_fopen just returns 0
Before running bbcbasic, manually, or from the autoexec.txt, mos_fopen returns a valid filehandle.
I'm attaching a minimalistic example that just fopens/fcloses 'autoexec.txt', and does it statically to avoid using the C arg parser. But opening other existing files behave similarly.
fopenbug.zip
I have reverted back to running MOS 1.02/VDP 1.02 and also tried bbcbasic 1.02/1.03/1.04.
Thnx!

Issue: In misc.asm
_exec16 preserves MB as it changes it to run 16-bit applications
_exec24 doesn't bother as it does not change MB
Preserve the register in case 24-bit apps change MB


Publish the library to maven central

The library looks pretty interesting. Would you please publish it on maven central as bintray is mostly blocked in many corporate environments?

I was planning to do that at some point. Will give it another try!

The library has been published to Maven Central. Please see the README for details: the groupId has changed.


Regression with exception handling from coroutines (was: Assertion Failure in Nuitka 2.5.1 with Telethon Integration)

Nuitka Version:
2.5.1
Commercial: None
Python: 3.12.4 (tags/v3.12.4:8e8a4ba, Jun  6 2024, 19:30:16) [MSC v.1940 64 bit (AMD64)]
Flavor: CPython Official
Executable: C:\Users\Devs\Desktop\BUILD\Scripts\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 10
Version C compiler: C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\bin\Hostx64\x64\cl.exe (cl 14.3).

Installation:

Nuitka: Installed via pip.
Python: Installed using the official Windows setup installer.

PyPI Packages and Versions (venv):
Package     Version
----------- -------
Nuitka      2.5.1
ordered-set 4.1.0
pip         24.0
pyaes       1.6.1
pyasn1      0.6.1
rsa         4.9
Telethon    1.38.1
zstandard   0.23.0

Command Used:
The following command was used to compile the script:
python -m nuitka --msvc=latest --debug --standalone test.py

Code Snippet:
The script that produces the error is as follows:
from telethon import TelegramClient

client = TelegramClient("test", 6, "eb06d4abfb49dc3eeb1aeb98ae0f581e")

async def main():
    print("Starting client with bot_token...")
    await client.start(bot_token="8173941128:AAHU1XdBGhvXN93aK6TxWpgeQVWSpEhRSqI")

    print("Fetching client details...")
    me = await client.get_me()

    print(me.stringify())

    # sometimes same error comes here on disconnect too
    await client.disconnect()
    await client.log_out()

client.loop.run_until_complete(main())

Error Message:
The error message encountered during runtime is:
Starting client with bot_token...
Assertion failed: HAS_ERROR_OCCURRED(tstate), file C:\Users\Devs\Desktop\BUILD\Lib\site-packages\nuitka\build\static_src\CompiledGeneratorTypeUncompiledIntegration.c, line 1

Additional Context:

The issue began after upgrading to Nuitka 2.5.1, with the previous version of Nuitka working fine.
The error occurs when running the executable compiled by Nuitka, either during the start-up (client.start()) or sometimes during the disconnect operation (client.disconnect()).
Also The keys and tokens used in this code snippet are default and for demo purpose. You can use the same without replacing anything.

This is a regression made during the 2.5 development, where we abstracted and unified exception handling, and made a mistake, since the code expects to be called with an exception set, but needs to also accept no exception set and return a value for that too.
Thanks for your report. This is fixed on the factory branch, which is a development version that is under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html
Feedback on whether this is working is very welcome. Please do not share plans to do it; only confirm or deny that it is working.

Yes, its working fine! thank you for the quick fix.

Part of the 2.5.2 release I just made.


ZEPPELIN-2268. Adding png and jpg support for helium module imports.

What is this PR for?
To allow helium modules to import CSS that contains references to png or jpg images.
What type of PR is it?
Improvement
Todos

[ ] - Task

What is the Jira issue?

[ZEPPELIN-2268]

How should this be tested?
The volume-leaflet helium module [https://github.com/volumeint/helium-volume-leaflet] imports the Leaflet css file.  That css file references a couple of png files.  Before this change, the helium module would fail to enable, after the change it succeeds.
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No.
Is there breaking changes for older versions?  No.
Does this needs documentation? No.

\cc @1ambda

LGTM
however, Could you setup travis-ci for your fork and see if it passes the test? Please take a look CI.

I configured travis-ci for my fork.  Build passes, but I had to re-run two of the build jobs due to flaky tests.
https://travis-ci.org/volumeint/zeppelin

LGTM and merge to master if no further discussions.


[Snyk] Upgrade graphql from 16.7.1 to 16.8.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade graphql from 16.7.1 to 16.8.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released a month ago, on 2023-08-14.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Check out a preview of your pull request here: https://alphasite-appservice-dev-pr-preview-1.azurewebsites.net


Tow entities for Fenipropidin?

I queried the CAS and received the two results CHEBI:83291 and CHEBI:81917. Aren't these the same entity? At least according to PubChem.

Hi,
Thanks. I have now removed the CAS number from CHEBI:83291 since this entry contains unspecified stereochemistry.
The issue is that most databases do not distinguish between unspecified stereo-chemical structures wheras ChEBI does. Most databases including PubChem will be showing the structure of fenpropidin as unspecified but this isn't correct since fenpropidin (CHEBI:81917) contains one stereocenter, therefore it is a racemic mixture comprising of equimolar amounts of both the (R)- and (S)-enantiomers. At the moment, we are unable to display two structures side-by-side for a given ChEBI entry hence we do not show the structure for the racemate, but in the ontology we mention that it has part the R-enantiomer and part S-enantiomer, so you can view the components of this racemate which are (CHEBI:83293 and CHEBI:83294).
ChEBI:83291 is

Thanks for the clarification!


.groupBy method does not recognise model column alias

I have noticed that both PostgreSQL column names and and Waterfront column name aliases, such as
        region: {
            type: "string",
            columnName: 'operations_region_code',
        },

are accepted indiscriminately by .find. However, when I chain
        Model.find({select:['region']}).groupBy(['region'])

I get undefined. On the other hand, if I chain
        Model.find({select:['region']}).groupBy(['operations_region_code'])

I get the expected response.

@dmvianna @devinivy @TylerBre - hey, we've moving all the Waterline issues to our main Sails issue hub. It looks like this one was fixed in an update. Thanks for contributing experiences and info for this case and I hope everything it's working now. 👍

Hi all @dmvianna @devinivy @TylerBre, We are further cleaning up Sails issues by closing older ones. As @johnabrams7 mentioned I believe this issue has been resolved in the newer version of Sails/Waterline

This has been published.


Addresses issue DCOS_OSS-1629.  Replaced Mesos version number with 1.…

Description
https://jira.mesosphere.com/browse/DCOS_OSS-1629
Urgency

[ ] Blocker
[ ] High
[ ] Medium

I believe this is low urgency.
Test

Built content locally and test for formatting/links.

Can one of the admins verify this patch?


[Improvement] netty performance tracking

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

What would you like to be improved?
Tested with grpc and netty.
Environment
Software: Uniffle master / Hadoop 3.2.2 / Spark 3.1.2
Hardware: Machine 96 cores, 512G memory, 1T * 4 SSD, network bandwidth 8GB/s
Hadoop Yarn Cluster: 1 * ResourceManager + 40 * NodeManager, every machine 1T * 4 SSD
Uniffle Cluster: 1 * Coordinator + 5 * Shuffle Server, every machine 1T * 4 SSD
Configuration
spark's conf
spark.executor.instances 400
spark.executor.cores 1
spark.executor.memory 2g
spark.shuffle.manager org.apache.spark.shuffle.RssShuffleManager
spark.rss.storage.type MEMORY_LOCALFILE

uniffle grpc-based server's conf
JVM XMX=200g

...
rss.server.buffer.capacity 100g
rss.server.read.buffer.capacity 20g
rss.server.flush.thread.alive 20
rss.server.flush.threadPool.size 50
rss.server.high.watermark.write 80
rss.server.low.watermark.write 70
...

uniffle netty-based server's conf
XMX_SIZE="140g"
MAX_DIRECT_MEMORY_SIZE=200g

...
rss.server.buffer.capacity 100g
rss.server.read.buffer.capacity 20g
rss.server.flush.thread.alive 20
rss.server.flush.threadPool.size 50
rss.server.high.watermark.write 80
rss.server.low.watermark.write 70
...

report

type
5T (run with 400 executors)

grpc-based
3.6min/5.9min

netty
3.4min/7.7min

And I found the spark executor with netty uniffle gc time is higher than grpc based.
How should we improve?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Could you enable spark.rss.client.off.heap.memory.enable?

Could you enable spark.rss.client.off.heap.memory.enable?

This is only for hdfs.

Another problem: the remote fetch from localfile is unstable, compared with grpc, it costs too much time.


Made grammatical changes

Coverage decreased (-0.1%) to 92.445% when pulling 37c2989640727fcdca223a1de14b0b04f9f0ba9a on Xylegen:master into 45916fe72f64c96b9c2344787272b653c2d3085a on Hrabal:master.


update ug again

glossary went behind (note help window does not have glossary)
update help window to reflect changes in ug

how u failed checkstyle for user guide dawg


[Improvement] Lint and format amoro web code before commit

Background
I found that the web project contains some code with lint errors and formatting issues many times.
I add two packages to lint and format code before commit. It is helpful to improve code quality and keep unified coding style.
Result

after I saw it have 2 errors, can we fix it?

Yes.


do not norm URL source paths on windows

Description
Otherwise, slashes would be replaced with backslashes.
QC

[x] The PR contains a test case for the changes or the changes are already covered by an existing test case.
[x] The documentation (docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).

Test

test

test


Update documentation about Auth service initialization

Just started reviewing :) :octocat: Sent from GH.

Merged!


return type must be bigint

What current issue(s) does this address, or what feature is it adding?
According to a fruitful discussion in neo project ( https://github.com/neo-project/neo/pull/253 ), we concluded that the return type must be coded as a BigInteger, not a simple hex... For most types it doesn't matter (eg. boolean is 01, and BigInt(1).toHex is also 01), but for Void, the neo machine expects to receive \xff00 which is the real BigInt(255), not \xff, which is BigInt(-1)... This will also cause problems with InteropInterface type, that is passing now as \xf0, but it's supposed to be the BigInt representation of it.
How did you solve this problem?
Struggling for many months, and this last discussion in NEO: https://github.com/neo-project/neo/pull/253
How did you make sure your solution works?
Sorry, I haven't tested well yet... this may have some impacts in FunctionCode, and I still haven't time to view all of it yet. But still, this needs to be fixed as soon as possible, in order to avoid other strange errors (such as https://github.com/CityOfZion/neo-python/pull/422 and https://github.com/CityOfZion/neo-python/issues/217)
Are there any special changes in the code that we should be aware of?
Not yet, we have to see the impacts.
Please check the following, if applicable:

[x] Did you add any tests?
[x] Did you run make lint?
[ ] Did you run make test?
[X] Are you making a PR to a feature branch or development rather than master?
[ ] Did you add an entry to CHANGELOG.rst? (if not, please do)

please dont take a look at this yet.i will improve and try to put some tests, when I have time

@igormcoelho I am reopening this, you can commit any test fix directly to your branch and it will appear in the PR automatically. Thanks for the catch.

Guys, make test is still failing (on 6 cases) and I don't have any idea on the outcome (they are complaining on some TypeError: 'module' object is not callable, but that should be some random message, I don't know the exact failures). Sorry, but I don't know if I will manage to finish all these tests, my time is quite constrained and I was just trying to help. If someone else manages to finish this, I believe it's a good direction (better a breaking code than a code that compiles but has misleading behavior).

I can take a look

Closing this in favor of #448


added numberOfAttempts to promptOptions

Fixes https://github.com/Microsoft/BotBuilder-Samples/issues/1257
Description
Adds a numberOfAttempts property to the promptOptions

Pull Request Test Coverage Report for Build #2178

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 87.666%

Totals

Change from base Build #2177:
0.06%

Covered Lines:
3202

Relevant Lines:
3509

💛  - Coveralls


FileNotFoundError: unknown test annotation JSON file

Thanks for your work on this project.
I am trying to infer over one example image, but I encountered the following error:
FileNotFoundError: [Errno 2] No such file or directory: 'data/annotations/test/InterHand2.6M_test_camera.json'

You mentioned in the instructions to “Edit your Interhand2.6M PATH in conf/ih_sfsseq.conf->data_path, which should contain ./images and ./annotations.” However, you did not provide information about the annotation or the structure of the json file referenced in my error.
Could you please provide a sample data folder with ./images and ./annotations so the inference python code sfs_lbs_test.py --exp_path interhand_out/Capture0_ROM03_RT_No_Occlusion/xhand runs smoothly?

Thank you for your interest in our work. Currently, we have only provided testing code on the dataset. We plan to release more practical inference code in the future. Alternatively, you can download the InterHand2.6M dataset (https://mks0601.github.io/InterHand2.6M/) to try our code, which contains the necessary files. The structure of the FOLD is the same as InterHand2.6M.


[CARBONDATA-1100] Tool to generate dictionaries for input csv.

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[CARBONDATA-<Jira issue #>] Description of pull request

[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).

[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.

[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

[ ] Testing done
 Please provide details on
 - Whether new unit test cases have been added or why no new tests are required?
 - What manual testing you have done?
 - Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/70/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1242/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/611/


services: enable count on searches

param version is not allowed in count queries, therfore has to be optional
closes https://github.com/inveniosoftware/invenio-app-rdm/issues/2092

This PR is an utility and can be merged independently of its issue. However, it needs work to be merged (i.e. pass tests)

Tests were failing on BLACK, I've pushed a commit to fix it


LlamaForCausalLM requires the PyTorch library but it was not found in your environment

Traceback (most recent call last):
  File "/output/LWM/scripts/sample_pyt.py", line 8, in <module>
    model = LlamaForCausalLM.from_pretrained(args.model)
  File "/usr/local/envs/lwm/lib/python3.10/site-packages/transformers/utils/import_utils.py", line 1112, in __getattribute__
    requires_backends(cls, cls._backends)
  File "/usr/local/envs/lwm/lib/python3.10/site-packages/transformers/utils/import_utils.py", line 1100, in requires_backends
    raise ImportError("".join(failed))
ImportError:
LlamaForCausalLM requires the PyTorch library but it was not found in your environment. Checkout the instructions on the
installation page: https://pytorch.org/get-started/locally/ and follow the ones that match your environment.
Please note that you may need to restart your runtime after installation.

separately install torch


fix(material-experimental): errors with latest MDC canary version

A few hours ago MDC switched all their Sass to use the new Sass modules (see https://github.com/material-components/material-components-web/commit/faa9af310d1a18ec2c183830c84eb14d0492feab). This breaks our MDC components since they've been set up to use global Sass variables. These changes switch all the imports to the .import files which use the old approach for exposing variables.

Hmm, this was passing locally. Looks like I'll have to spend a bit more time on it. Will ping when Circle is passing as well.

It should be good to go now. @devversion I don't know whether you want to take one more look at it. I had to switch us to use the Dart version of Sass, because node-sass hasn't implemented Sass modules yet.

Right, I should have given you all a heads up about this (MDC switching to the new Sass module system); we'd been talking about it for a while. The Sass team is working on a project to make dart-sass faster to minimize the perf gap. It looks like libsass (on which node-sass is based) is now unmaintained and won't be matching Sass features going forward.


onFlipped listener?

Any way or example to listen when my widget flip animation is done (when the back side is fully shown)?

At the moment, there's just callback indicating the begin of animation.
Is what you want is something like  onFlipDone  or onFlip(status)?

onFlipDone is fine along with existing onFlip, I need to do some stuff at the end of animation, thank you.


PARQUET-2310: implementation status

Moved from: https://github.com/apache/arrow/pull/36027
I only can agree with @westonpace:

Although...to play devil's advocate...it might be odd when a feature is available in the parquet reader, but not yet exposed in the query component. For example, there is some row skipping and bloom filters in the C++ parquet reader, but we haven't integrated those into the datasets layer yet.

The original goal was not copying https://arrow.apache.org/docs/cpp/parquet.html#supported-parquet-features, but quite orthogonal to this: showing which high level APIs are available for the end-user.
What I mean by this is that based on the document I should be able to know if I can manipulate Parquet files without decoding some values or do I have to convert it to actual objects / Apache Arrow table first. This was the info what is missing from all the docs and I'd like maintain something which reflects the public API functionalities.
Many of you were surprised by including xy metadata, what I was referring to was the availability of the https://arrow.apache.org/docs/python/generated/pyarrow.Schema.html#pyarrow.Schema.metadata or https://arrow.apache.org/docs/python/generated/pyarrow.Field.html#pyarrow.Field.metadata
Similar happens with the Column Index. It's available internally, but if it's not used when adding filters to the parquet reader, that's useful info for the Apache Arrow and Parquet developers, but not for the library users.
This is a limitation of the pyarrow API and this might be temporary or by design, but making this transparent was my intention.
It's absolutely OK if parquet-mr doesn't have a dataset API using the parquet features and it's OK for pyarrow not exposing the raw objects / byte arrays (ever). Different ecosystems have different abstractions and there doesn't have to be a "correct" or "standard" one. This is actually a nice thing - DataFusion, pyarrow, Acero, Iceberg etc have all different communities complementing each other.
Let me know if this is too vague or doesn't belong to the standard docs (or help me achieving a concise summary reflecting the above)

@alippai Perhaps you'd like to start filling in the table for Rust?

I am very interested in helping this post along. Is there any interest in pursuing this PR or would it be better to make a new one?

Thanks @pitrou for the comments. Yes, I’ll address them and fill the table best to my knowledge and online resources

I can certainly fill the one in for Rust

I’ll open a new draft later this week

FYI https://github.com/apache/parquet-site/pull/53 is a related conversation. Once that PR merges perhaps there will be a more natural location for this chart / location

Totally agree, thanks for the guide. What do you think about the non-Apache or other projects? (Duckdb, fastparquet, impala, cuff)

IMHO, any currently maintained open source implementation of Parquet deserves mentioning there. But that also requires involvement from their respective maintainers (we shouldn't expect us Parquet maintainers to make sure the information is up to date).

Totally agree, thanks for the guide. What do you think about the non-Apache or other projects? (Duckdb, fastparquet, impala, cudf)

Echoing what @pitrou  said, I suggest we add a note somewhere that "this table includes any open source currently maintained implementation of parquet whose maintainers have helped fill it out. If you wish to add a new implementation to this table, please open a PR to do so"
It might also be worth adding a column with some sort of placeholder (? for example) for those implementation (as a way of encouraging their help). However, that might be a good thing to do as a follow on PR as well

I like both!

I think it would also help to define what is required of an implementation to have a "check" in the corresponding feature row.

I worry about this becoming a little bit of a pedantic discussion.  My 2 cents: I think a reasonable approach is to let maintainers decide on checking the box or not.  Maybe we can have a ternary value.    If they think reasonable people might be confused it gets '-' or check without footnote to explain the exception.  If it is completely not supported it gets an 'X'.  We can always adjust criteria as we get feedback.

IMHO, any currently maintained open source implementation of Parquet deserves mentioning there. But that also requires involvement from their respective maintainers (we shouldn't expect us Parquet maintainers to make sure the information is up to date).

Agreed with that. I would be happy to contribute on cudf's behalf!

It is my opinion that we should try and address any outstanding comments that are straightforward, but then merge this PR even if there are other more substantial ones unresolved (like guidance https://github.com/apache/parquet-site/pull/34/files#r1635005006).

I agree with this sentiment.  @alippai do you have bandwidth do another pass?  I can merge after another pass (or do so now if you don't have bandwidth for an update).

Yes, the input is great and I’ll give it a go tomorrow

Please mark PRs that are ready for review as such. I have not given this as a review as it showed up as Draft in my notification. I will do this now in the next 2h.

I've learned a ton and I see that many of us saw a few surprises. Looks like the page is needed indeed :)
Following the advice a few of you raised I removed any controversial or too detailed items, we'll handle it in a next PR.
Most of the comments are addressed and if we are happy with the changes, I'll:

Rename the existing and add the additional implementations (DuckDB, Impala, Fastparquet etc)
Fill them out with initial values and reach out to the communities (if not present here already)
Create issues for the followup work (like the read/write distinction, query engine or dataset features, date or version based grouping of the features)

@alippai thanks for updates! I agree with @alamb and @emkornfield that it's the right time to merge this and let the various implementations take a crack at filling in their columns. Questions that arise while doing that can drive the next iteration.

@alippai this sounds like a good plan.  I think if you are going to fill out some columns it might make sense to do so in this PR to avoid merge conflicts.  It sounds like @alamb and @etseidl want to update for Rust and CUDF respectively but hopefully can coordinate to avoid merge conflicts.

It sounds like @alamb and @etseidl want to update for Rust and CUDF respectively but hopefully can coordinate to avoid merge conflicts.

Actually @mhaseeb123 will be handling cuDF. I'm just an interested bystander 😅.

It sounds like @alamb and @etseidl want to update for Rust and CUDF respectively but hopefully can coordinate to avoid merge conflicts.

Actually @mhaseeb123 will be handling cuDF. I'm just an interested bystander 😅.

I would be happy to contribute on cuDF's behalf. I am just not fully sure if we are changing column names from language names (C++, Python etc) to implementation names (Arrow, cuDF etc) as @pitrou suggested or filling the rows with implementation names that support a feature in that language?

It seems there are no objections. Let me do one more round tomorrow with the update mentioned

I tried to address @julienledem 's comments in  https://github.com/alippai/parquet-site/pull/1

Hi @alamb, thank you for the all work and addressing comments. I saw you added a legend and some description in https://github.com/alippai/parquet-site/pull/1 but I don't see cuDF in there and also am not sure how to exactly fill the table for cuDF. This is confusing especially as cuDF provides C++, Python and (limited? @etseidl) Java Parquet interfaces with GPU-accelerated backends.

@alippai were you planning on adding anything else here or should we merge?

I saw you added a legend and some description in alippai#1 but I don't see cuDF in there and also am not sure how to exactly fill the table for cuDF. This is confusing especially as cuDF provides C++, Python and (limited? @etseidl) Java Parquet interfaces with GPU-accelerated backends.

My suggestion is to add a column/columns for cuDF in a future PR when you have information to fill out.
I think the intent of these tables is to describe the parquet implementations (so it lists parquet-cpp, not its python bindings in pyarrow, for example). Perhaps the same model would apply to the parquet reader in cuDF
In terms of how to fill out the table, we are discussing various option for "what does it mean to support a feature" on https://github.com/apache/parquet-format/issues/441

@alippai thank you for getting this sarted, I'm going to merge now to let others try to fill it out.


RAM listed in Parts List is not compatible with NUC7i7BNH 3.5GHz i7-7567U

The RAM listed in the Parts List section is DDR3/DDR3L, whereas the NUC7i7BNH requires DDR4 memory.
Here's the link with the memory requirements for NUC7i7BNH:
https://www.intel.com/content/www/us/en/support/articles/000023165/mini-pcs/intel-nuc-kits.html
Thanks

Hi sfmig,
Thank you for your comment and you were right as described: https://www.intel.com/content/www/us/en/support/articles/000023165/mini-pcs/intel-nuc-kits.html
This happened due to a miss-matched NUC model number. Intel NUC 5i7RYH was the one we used for this project as described in https://github.com/ethz-asl/mav_dji_ros_interface/wiki/Hardware-and-Software-Versions
I updated the part list accordingly. If one wants to use a higher-performance NUC (e.g., NUC7i7BNH), it is recommended to find the correct combination of RAM, SSD, and etc.


Drop custom bash completion in favour of default one

Summary
This PR makes use of the default bash completion added in https://github.com/spf13/cobra/releases/tag/v1.2.0 and drops the custom one.
Ticket Link
None

Codecov Report

Merging #210 (306c94f) into master (7a2443f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #210   +/-   ##
=======================================
  Coverage   25.53%   25.53%
=======================================
  Files          25       25
  Lines        1402     1402
=======================================
  Hits          358      358
  Misses       1013     1013
  Partials       31       31

Continue to review full report at Codecov.

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


FilterList: add parameter for last separator

Filter List could be really useful for listing/numeration of elemnts in a text, if we had a possibility to change last separator. Multiple words separated by comma look unnatural.
Proposition:
const ITEMS = ["apples", "oranges", "bananas"]; filterList(ITEMS, {   isHtml: false,   isSimpleArray: true,   separator: ",", lastSeparator="and" }); // apples, oranges and bananas

merged in master


Spyder missing dependencies after adding path to Python Path Manager

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
You` have missing dependencies!

# Mandatory:
nbconvert >=4.0 : None (NOK)

Please install them to avoid this message.

Note: Spyder could work without some of these dependencies, however to have a smooth experience when using Spyder we strongly recommend you to install all the listed missing dependencies.

Failing to install these dependencies might result in bugs. Please be sure that any found bugs are not the direct result of missing dependencies, prior to reporting a new issue.
```

To remedy I did the following steps after reading about them here [](https://github.com/spyder-ide/spyder/issues/8941) :

pip install nbconvert #used pip instead of conda as conda was returning nothing.

I also did

import rtree
>>> rtree.__file__
'/Applications/Spyder.app/Contents/Resources/lib/python39.zip/rtree/__init__.pyc'

### What steps reproduce the problem?

1. I put a link to my python site library using the pythonpath manager so it would link yfinance
2.
3.

### What is the expected output? What do you see instead?
I don't want to see the error.

### Paste Traceback/Error Below (if applicable)
<!--- Copy from error dialog or View > Panes > Internal Console --->

```python-traceback

You have missing dependencies!

# Mandatory:
nbconvert >=4.0 : None (NOK)

Please install them to avoid this message.

Note: Spyder could work without some of these dependencies, however to have a smooth experience when using Spyder we strongly recommend you to install all the listed missing dependencies.

Failing to install these dependencies might result in bugs. Please be sure that any found bugs are not the direct result of missing dependencies, prior to reporting a new issue.

```

## Versions
<!--- You can get this information from Help > About Spyder...
or (if Spyder won't launch) the "conda list" command
from the Anaconda Prompt/Terminal/command line. --->

* Spyder version: 5.2.1
* Python version: 3.9.5 (this is what spyder is saying it's using but I have installed 3.10.2
* Qt version:
* PyQt version: 5
* Operating System name/version: Mac OS Monterrey

### Dependencies
<!--- Please go to the menu entry Help > Dependencies,
press the Copy to clipboard button and paste below --->

```
PASTE DEPENDENCIES HERE
```

Hi @Aman1242 thank you for the feedback! Did the path you added to the Python Path Manager point to an env? If you want oto work with an different interpreter/env than the one that comes with the installer you should use the custom interpreter preference instead of adding paths to the Python Path Manager. If that is the case maybe this could help: https://docs.spyder-ide.org/current/faq.html#using-packages-installer
Let us know if something of the above helps!

Closing due to lack of response


handling _wp_old_slug ?

Is there any code that processes the meta key _wp_old_slug?
Perhaps it could be a simple HTML redirect (like refresh) or output for .htaccess.

Hi @joyously,
There's no redirection handling within this plugin. https://github.com/leonstafford/wp2static has support for redirect handling, but that will depend on where you're deploying to, as each static host may handle differently.
You mentioned .htaccess, so I assume that you want to host your static site on another Apache server?
I may get to redirect support in the future, but for now, I'd propose manually creating the redirect rules for the URLs you are aware of. You may be able to grab all the _wp_old_slug entries from the WordPress database to help if there's a lot.
If you want a smoother experience for redirects, I can recommend Strattic, the company I now work for, who have a complete end to end WordPress to static site hosting/publishing platform with redirect support. If you're interested in that, there's a free trial and our team's really nice at onboarding people.


Transparent Rendering of Isospheres Completely Screwed Up

Bevy version
0.3, 0.2.1, 0.2, latest
Operating system & version
Windows 10, Ubuntu 20.04
What you did
Rendered two transparent icospheres on top of each other.
What you expected to happen
I should be able to see both of them.
What actually happened
One of them clips the other, and it changes depending on viewing angle/

@iMplode-nZ, does this still occur with the new renderer?

This is because bevy doesn't have order-independent transparency yet. See https://github.com/bevyengine/bevy/issues/2223

Sounds good. Closing in favor of #2223 then to keep this tidy.


Use isinstance() rather than type() for a typecheck.

LGTM, could you update the code to leverage the fact that isinstance can work with a tuple of classes for the second ? It'll return true if the first argument is an instance of any of the types in that sequence.

Excellent idea @SMoraisAnsys . I sort of automated the process.

Codecov Report
Attention: Patch coverage is 86.53846% with 7 lines in your changes are missing coverage. Please review.

Project coverage is 76.46%. Comparing base (e9c7290) to head (4c7cfc6).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4488      +/-   ##
==========================================
- Coverage   81.43%   76.46%   -4.98%
==========================================
  Files         110      110
  Lines       53482    53482
==========================================
- Hits        43554    40895    -2659
- Misses       9928    12587    +2659


Feature Request - Define width & order of kanban columns

Really like this project! A couple of usability suggestions, if it's OK to suggest...

My columns on the kanban board are 2x wider than I'd like. I wish there were a way to define the default size in the settings.
Is there a way to define the order of the columns? Right now, they are out of order for my workflow :)
Finally, I'd like the option of hiding a column (especially when there's no value for the field)

Thanks!
JB

Thank you! 🙏

Can definitely add this!
Not right now, I've been meaning to figure out how to implement drag and drop, and have been pushing this until then. I could potentially also make this configurable through other means until drag and drop happens.
Sounds like your use case is hiding empty columns rather than manually hiding them? Is that correct?

On point 3, it’s more an intuition than use case. screen real estate is precious, so anything (like an empty column) that occupies space without relaying information is frustrating. I suppose manually hiding may be more universally helpful than auto hiding.
Thanks again for this great work!

This would be very useful!
Regarding hiding empty columns, I've seen some Kanban boards where empty columns are auto collapsed, thus they stay in correct order, but only take up a fraction of a full width column. This would be my personal preference as it makes it clear that there is a status/column, where it sits, and that there are currently no cards in that column.

I've added a setting in 0.19.2 for adjusting the column width.

Let's continue the discussion on auto-collapsing columns in #68 and column ordering in #2.


Support callback refs in highlightable subcomponents

Context
Some nested components that use ref props/forwardRef don't support callback (function) refs e.g. by directly inspecting ref.current.
Summary
Fixes these components to support both normal refs and callback refs.
Relevant Technical Choices
N/A
To-do

[ ] Merge follow-up #8523

User-facing changes
N/A
Testing Instructions
N/A
QA

[x] This is a non-user-facing change and requires no QA

UAT

[x] UAT should use the same steps as above.

Reviews
Does this PR have a security-related impact?
No.
Does this PR change what data or activity we track or use?
No.
Does this PR have a legal-related impact?
No.
Checklist

[x] This PR addresses an existing issue and I have linked this PR to it in ZenHub
[x] I have tested this code to the best of my abilities
[x] I have verified accessibility to the best of my abilities (docs)
[x] I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
[x] This PR contains automated tests (unit, integration, and/or e2e) to verify the code works as intended (docs)
[x] I have added documentation where necessary
[x] I have added a matching Type: XYZ label to the PR

Related to #8259. Prerequisite for #8309.

@samwhale Thanks for the review!


libosmium: 2.17.3 → 2.18.0, osmium-tool: 1.13.2 → 1.14.0

Motivation for this change

libosmium: Changelog
osmium-tool: Changelog

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 158496 run on x86_64-linux 1

5 packages built:

libosmium
osm2pgsql
osmium-tool
python310Packages.pyosmium
python39Packages.pyosmium


docker-sync start produces error

Spun out of #117. I'm seeing the following when running docker-sync-stack start:
       note:  You can also run docker-sync in the background with docker-sync --daemon
          ok  Starting unison
       error  Error starting sync, exit code 0
     message
     message  Contacting server...
Fatal error: Failed to connect to the server on host <IP_ADDRESS>:32770
     success  Unison server started
       error  Error starting sync, exit code 0
     message
     message  Contacting server...
Fatal error: Failed to connect to the server on host <IP_ADDRESS>:32770
          ok  starting compose
Contacting server...
Fatal error: Failed to connect to the server on host <IP_ADDRESS>:32770

As I'm running dingy, I needed to add sync_host_ip: '<IP_ADDRESS>' to my docker-sync.yml file. I then ran docker-sync clean and also manually deleted the sync container and then ran docker-sync start and its all looking good now. I think if you're using Docker for Mac then the default localhost will work, otherwise you need to add your host IP.


Set maximum size of webhook request to 10MB

As discussed here: https://github.com/google/go-github/pull/693#discussion_r141508166 this ticket is to track/discuss whether we should be adding a 10MB limit to the size of the body for webhook requests.

@gmlewis this issue can be closed

@gmlewis this issue can be closed

Thank you, @wesleimp.
Closing.


update some info

Update README.md based on the latest information from MLPerf.
PTAL :)

Awesome, thank you very much for the updates!


Fix: Landing Page

Description
This PR fixes #1713
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@psankhe28
Let's discuss this on websites call today. I've added this as an agenda item to the meeting minutes.
Meeting details: https://meet.layer5.io

Thank you @psankhe28 for fixing this 👏🚀


[MBL-1458 pt 5] Card view for pledged projects overview

📲 What
This PR implements the card view for pledged projects, as well as the relevant subviews. It adds a view model to cover handling actions like tapping buttons and sending the creator a message. This builds on previous PRs to add the individual pieces.
Connecting to real data will come in a future PR.
🛠 How
The project card is built from the individual pieces added in previous PRs.
Each card view gets its own view model instance, which is a container that holds the relevant data and can forward messages from the card view to a caller via Combine.
Views were tested via snapshot testing of the card in various configurations listed in Figma. View model inputs and outputs have unit tests.
👀 See
Figma
♿ Accessibility

[x] Tap targets use minimum of 44x44 pts dimensions

Should support Dynamic Type and VoiceOver, but that hasn't been confirmed
🏎 Performance
Performance will be validated when these are integrated into the pledged project list.
✅ Acceptance criteria
Feature will be more thoroughly tested against real data in a future PR after integrating. For now, all tests should pass.
⏰ TODO
Future PRs will integrate into the app UI itself and more testing can happen at that time.

          1 Warning

:warning:
Big PR

SwiftFormat found issues:

File
Rules

Kickstarter-iOS/Features/PledgedProjectsOverview/CardView/PPOProjectCardViewModel.swift:27:1
warning: (trailingClosures) Use trailing closure syntax where applicable.

Kickstarter-iOS/Features/PledgedProjectsOverview/CardView/PPOProjectCardViewModel.swift:31:1
warning: (trailingClosures) Use trailing closure syntax where applicable.

  Generated by :no_entry_sign: Danger


add a way to generate a did and verkey from seed

Thanks, I extended the script to directly grep for the interesting line from the output and only show this, also stopping automatically. Please have a look and check if this works for you as well, from my perspective the PR can be merged.

thanks it works correctly


Age Calculator Modified

Description 📜
The user interface of the Age calculator has been modified, and the format of displaying current date and time changed as well.
Fixes #72

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GSSOC'22 contributor

Screenshots / Gif (Optional) 📸

Similar one is already there
https://vashishth.me/CalcHub/Calculators/Age_Calculator/
Can't merge this pull :)
Closing this !

incase of any quires, feel free to reach out me on discord :)

sry for this 👍🏻


Is there anyway to fetch secret file that is not on the same repository?

I have a scenario in which buildkite infrastructure codes (such as secrets ejson) are placed in an external git repository. I would like to propose that we extend the functionality to fetch remote file via HTTP/HTTPS:
steps:
  - name: Tests
    plugins:
      - envato/ejson2env#v0.1.0:
          ejson_file: https://path.to/secrets.ejson
          ejson_private_key_env_key: EJSON_PRIVATE_KEY

I am happy to cook up a patch if you are okay with this @stevehodgkiss

I think that scenario would be better solved by fetching the ejson file from the git repo from a Buildkite hook inside the repo, or potentially a different plugin before this one if one exists to do what you're after.

@stevehodgkiss Yes, that is exactly what I am doing atm by having a plugin to fetch & place the file into the build folder. On second thought I think it is better not to have too many responsibilities in this plugin. Thanks for your response :)


how to continue to sync data

I delete meilisync docker by accident. Now it can not be started any more. How can I do to continue to sync data?

fixed, wrong issue


Crc is taking long time to boot up...

CRC is taking long time to boot up.
using : crc start -p pull-secret. to start
Is there way to Directly start the cluster?
WARN A new version (1.9.0) has been published on https://cloud.redhat.com/openshift/install/crc/installer-provisioned
INFO Checking if oc binary is cached
INFO Checking if podman remote binary is cached
INFO Checking if running as non-root
INFO Checking if Virtualization is enabled
INFO Checking if KVM is enabled
INFO Checking if libvirt is installed
INFO Checking if user is part of libvirt group
INFO Checking if libvirt is enabled
INFO Checking if libvirt daemon is running
INFO Checking if a supported libvirt version is installed
INFO Checking if crc-driver-libvirt is installed
INFO Checking if libvirt 'crc' network is available
INFO Checking if libvirt 'crc' network is active
INFO Checking if NetworkManager is installed
INFO Checking if NetworkManager service is running
INFO Checking if /etc/NetworkManager/conf.d/crc-nm-dnsmasq.conf exists
INFO Checking if /etc/NetworkManager/dnsmasq.d/crc.conf exists
INFO Starting CodeReady Containers VM for OpenShift 4.3.1...
INFO Verifying validity of the cluster certificates ...
INFO Check internal and public DNS query ...
INFO Check DNS query from host ...
INFO Starting OpenShift cluster ... [waiting 3m]
INFO
INFO To access the cluster, first set up your environment by following 'crc oc-env' instructions

Regards

Is there way to Directly start the cluster?

Not really understanding what you mean.

Crc is taking long time to boot up...

You are starting a VM with a full production-like cluster, which needs time to reconcile state before it becomes usable, hence the

INFO Starting OpenShift cluster ... [waiting 3m]

The total start up time can take over 5minutes due to this. Even if the VM was 'pre-heated' (hot start - by having it run ALL the time), the startup would still take 3 minutes for OpenShift itself to get into a full working state. Note: having memory consumption when not using is a no-go, so this scenario can not be persued.
What are you suggesting?

CRC is taking long time to boot up.

How much time?
Which platform? Windows, macOS, or Linux?
What are the specs of your machine? Brand, memory, CPU, etc
What else is running in the background?

Time 10 minutes
Linux Ubuntu
Dell, 4 core cpu, 8gb ram
Intellij running in background
Thanks for the reply

As the crc virtual machines needs 8GB of RAM by itself, I'm afraid 8GB of total RAM on the system is not going to be enough, and will contribute to the perceived slowness.

Dell, 4 core cpu, 8gb ram

As mentioned, this is using the defaults already... the VM actually needs 8GB of free memory, besides the OS overhead and such.
Note: 10 minutes is long, but sounds about the top end of the cases we have seen. Usually it is around 3 to 5 minutes. But it depends really on the machine and hwo resource intensive it is being used in the meantime.
We are looking into optimizations, but they might take some time. If you do not mind, I will close the issue as there have been several along the same lines, but with slightly more details or discussions.


stepmania: switch to clangStdenv

Fixes #54227
Motivation for this change
Stepmania crashes on every NixOS computer I have tried without this patch, after this patch it works fine.
Like I said in #54227, I don't know if this is a mis-compilation or UB in stepmania that I can't find, and if it is mis-compilation I don't know what specific gcc bug it is.
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 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)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thanks!
Cherry-picked to 19.03 in 35845b0b2a215b09f5dbb2a4bbb9f2956f567910
Cherry-picked to 18.09 in 28e30399a90e94987812eaedba80dba5131d1d8c


Script the creation of the initial tiers and workloads

Is your feature request related to a problem? Please describe.
I am in the process of building out the primary tiers along with multiple workload tiers for a customer and would like to automate the entire process into a single script.
Describe the solution you'd like
I would love to be able to gather all the information for all of the tiers that need to be built. Put the data into one file or location. Then run a single script that will build all of the tiers from the information.
Describe alternatives you've considered
I recently built a PowerShell script that will read data from a JSON file and create the primary tiers.  It will then gather the information about the deployment and use that information to build the workload tiers whose build information is also in the JSON file. (I also have a separate script that will also build out just the workload tiers.  this is in case you need to build out more of them after the initial build has been completed) But it's all a bit clunky and can probably be done better.
Additional context

Thank you @agoodmiller for creating this excellent issue! I think this will be highly valuable as a new example in the src/bicep/examples folder. I'm closing this issue because I created #597 as a backlog item to represent this work. Please add feedback there and help us set the right acceptance criteria for that issue.


HasManyList::foreignIDFilter() doesn’t include table name

HasManyList::foreignIDFilter() does not include the table name for the component class, which can result in Column '<column>' in where clause is ambiguous errors when related models share the same component names. Example model setup below:
class Company extends DataObject
{
    private static $has_many = [
        'Searches' => 'Search',
        'Responses' => 'Response'
    ];
}

class Search extends DataObject
{
    private static $db = [
        'Status' => 'Enum(array("Inactive", "Active"), "Inactive")'
    ];

    private static $has_one = [
        'Company' => 'Company'
    ];

    private static $has_many = [
        'Responses' => 'Response'
    ];
}

class Response extends DataObject
{
    private static $has_one = [
        'Search' => 'Search',
        'Company' => 'Company'
    ];
}

// SELECT DISTINCT count(DISTINCT "Response"."ID") AS "Count" FROM "Response" LEFT JOIN "Search" ON "Search"."ID" = "Response"."SearchID" WHERE ("CompanyID" = ?) AND ("Search"."Status" = ?)
// Query error: Column 'CompanyID' in where clause is ambiguous
echo $company->Responses()->filter([
    'Search.Status' => 'Active'
])->count();

Workaround for the issue is just to give the relations different names on each model

Closed via https://github.com/silverstripe/silverstripe-framework/commit/99a364a24c573a4e0a2bcc1ec59e9bc63761391f


ValueError: initial_value must have a shape specified: Tensor("random_normal:0", shape=(2, ?), dtype=float32)

Hello,
I am using Songbird stand alone, and it has worked perfectly until I ran into this issue using a very specific .biom file as input. This .biom file is a subset of samples from a "parent" .biom file, but when I use the parent .biom file or other subsets of samples in this same file songbird runs to completion without this error (and I've used it many times at this point).
Any chance of figuring out what the issue is here? (see error message below)
Thank you!!!
Brett
OMP: Info #212: KMP_AFFINITY: decoding x2APIC ids.
OMP: Info #210: KMP_AFFINITY: Affinity capable, using global cpuid leaf 11 info
OMP: Info #154: KMP_AFFINITY: Initial OS proc set respected: 10-29
OMP: Info #156: KMP_AFFINITY: 20 available OS procs
OMP: Info #158: KMP_AFFINITY: Nonuniform topology
OMP: Info #179: KMP_AFFINITY: 2 packages x 14 cores/pkg x 1 threads/core (20 total cores)
OMP: Info #214: KMP_AFFINITY: OS proc to physical thread map:
OMP: Info #171: KMP_AFFINITY: OS proc 10 maps to package 0 core 13
OMP: Info #171: KMP_AFFINITY: OS proc 11 maps to package 0 core 14
OMP: Info #171: KMP_AFFINITY: OS proc 12 maps to package 0 core 16
OMP: Info #171: KMP_AFFINITY: OS proc 13 maps to package 0 core 17
OMP: Info #171: KMP_AFFINITY: OS proc 14 maps to package 0 core 18
OMP: Info #171: KMP_AFFINITY: OS proc 15 maps to package 0 core 20
OMP: Info #171: KMP_AFFINITY: OS proc 16 maps to package 0 core 21
OMP: Info #171: KMP_AFFINITY: OS proc 17 maps to package 0 core 22
OMP: Info #171: KMP_AFFINITY: OS proc 18 maps to package 0 core 24
OMP: Info #171: KMP_AFFINITY: OS proc 19 maps to package 0 core 25
OMP: Info #171: KMP_AFFINITY: OS proc 20 maps to package 0 core 26
OMP: Info #171: KMP_AFFINITY: OS proc 21 maps to package 0 core 28
OMP: Info #171: KMP_AFFINITY: OS proc 22 maps to package 0 core 29
OMP: Info #171: KMP_AFFINITY: OS proc 23 maps to package 0 core 30
OMP: Info #171: KMP_AFFINITY: OS proc 24 maps to package 1 core 0
OMP: Info #171: KMP_AFFINITY: OS proc 25 maps to package 1 core 1
OMP: Info #171: KMP_AFFINITY: OS proc 26 maps to package 1 core 2
OMP: Info #171: KMP_AFFINITY: OS proc 27 maps to package 1 core 4
OMP: Info #171: KMP_AFFINITY: OS proc 28 maps to package 1 core 5
OMP: Info #171: KMP_AFFINITY: OS proc 29 maps to package 1 core 6
OMP: Info #250: KMP_AFFINITY: pid 17161 tid 17161 thread 0 bound to OS proc set 10
WARNING:tensorflow:From /gpfs0/export/apps/opt/Songbird/1.0.3/bin/songbird:191: The name tf.Session is deprecated. Please use tf.compat.v1.Session instead.
2020-12-14 10:27:59.621442: I tensorflow/core/platform/cpu_feature_guard.cc:145] This TensorFlow binary is optimized with Intel(R) MKL-DNN to use the following CPU instructions in performance critical operations:  SSE4.1 SSE4.2 AVX AVX2 FMA
To enable them in non-MKL-DNN operations, rebuild TensorFlow with the appropriate compiler flags.
2020-12-14 10:27:59.668857: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2020-12-14 10:27:59.672470: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x55999e7fdae0 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-12-14 10:27:59.673363: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-12-14 10:27:59.676186: I tensorflow/core/common_runtime/process_util.cc:115] Creating new thread pool with default inter op setting: 2. Tune using inter_op_parallelism_threads for best performance.
WARNING:tensorflow:From /gpfs0/export/apps/opt/Songbird/1.0.3/bin/songbird:194: The name tf.set_random_seed is deprecated. Please use tf.compat.v1.set_random_seed instead.
WARNING:tensorflow:From /gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/songbird/multinomial.py:70: multinomial (from tensorflow.python.ops.random_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.random.categorical instead.
WARNING:tensorflow:From /gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/songbird/multinomial.py:81: The name tf.random_normal is deprecated. Please use tf.random.normal instead.
Traceback (most recent call last):
File "/gpfs0/export/apps/opt/Songbird/1.0.3/bin/songbird", line 225, in
songbird()
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/click/core.py", line 829, in call
return self.main(*args, **kwargs)
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/gpfs0/export/apps/opt/Songbird/1.0.3/bin/songbird", line 196, in multinomial
model(session, trainX, trainY, testX, testY)
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/songbird/multinomial.py", line 81, in call
tf.random_normal([self.p, self.D-1]), name='qB')
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/tensorflow_core/python/ops/variables.py", line 258, in call
return cls._variable_v1_call(*args, **kwargs)
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/tensorflow_core/python/ops/variables.py", line 219, in _variable_v1_call
shape=shape)
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/tensorflow_core/python/ops/variables.py", line 197, in
previous_getter = lambda **kwargs: default_variable_creator(None, **kwargs)
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/tensorflow_core/python/ops/variable_scope.py", line 2519, in default_variable_creator
shape=shape)
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/tensorflow_core/python/ops/variables.py", line 262, in call
return super(VariableMetaclass, cls).call(*args, **kwargs)
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/tensorflow_core/python/ops/variables.py", line 1688, in init
shape=shape)
File "/gpfs0/export/apps/opt/Songbird/1.0.3/lib/python3.7/site-packages/tensorflow_core/python/ops/variables.py", line 1853, in _init_from_args
self._initial_value)
ValueError: initial_value must have a shape specified: Tensor("random_normal:0", shape=(2, ?), dtype=float32)
Job Statistics for 76837:
JobID       User               Start                 End    Elapsed     MaxRSS   TotalCPU      State Exit        NodeList                                  ReqTRES

       76837     brl003 2020-12-14T10:27:55 2020-12-14T10:28:00   00:00:05             00:04.216     FAILED  1:0   r1pl-hpcf-h03     billing=20,cpu=20,mem=855000M,node=1
 76837.batch            2020-12-14T10:27:55 2020-12-14T10:28:00   00:00:05          0  00:04.214     FAILED  1:0   r1pl-hpcf-h03
76837.extern            2020-12-14T10:27:55 2020-12-14T10:28:00   00:00:05          0  00:00.001  COMPLETED  0:0   r1pl-hpcf-h03

CPU Efficiency: 4.00% of 00:01:40 core-walltime

Hi @BrettLoman thank you for raising this issue.  These sorts of issues can arise if an empty dataset is inputted.  This can happen for the following reasons

The samples are all filtered out, either because the table is normalized to 1 or all of the samples have too few reads
There are too few samples in your subset ( it is worth checking out the --min-feature-count and min-sample-count args)
The sample metadata sample names don't match the sample names in the biom table