feat: event rendering

There seems to be no nice event rendering solutions 'out-of-the-box' that would slot into this project.
I am in favour of our Lichess display their events:

Ref: https://lichess.org/tournament
And I have found the following depreciated React component that fits this model:

Ref: https://github.com/JSainsburyPLC/react-timelines
It is important that our users are able to easily see upcoming events at a glance, which can be viewed easily on Web & Mobile.
Solutions like FullCalendar maybe a solution but this seems relatively inflexible for styling. And there is currently no support for TailwindCSS theming.

Logged In
Initial attempt to make an easy to understand calendar

Home page calendar
Covering different layout defaults for mobile and desktop

Leaving ticket open. The following tasks are still outstanding:

[ ] When filter selected i.e only rapid events && a month is empty, disable toggle months with no corresponding filter
[ ] Add "next" and "prev" buttons to the bottom when list > n for better UX
[ ] Add "rest all" filters for when no events are displayed
[ ] Add click through logic to internal app calendar - requires sub-task ticket

WIll move the above tasks into individual tickets.


Problems with not seeing wikilink text

hello
'[[wikilink|custom display text]]' is visible
but '[[wikilink]]' is not visible
Is this an intended feature?

Oh, I like the fourth option.
- [ ] [[AAA]]BBB[[CCC|DDD]]

⬇
🔲 AAABBBDDD


[CI pipeline] scripts/azure-pipelines/test-modified-ports.ps1 preinstall failed

https://github.com/microsoft/vcpkg/blob/master/scripts/azure-pipelines/test-modified-ports.ps1#L101
It preinstall x86 tools for port protobuf, boost-build and sqlite3 in CI pipeline, the thread failed with WinHttpReceiveResponse() failed: 12152 when download powershell-core, that cause the 3 ports preinstall failed. however, it doesn't failed CI pipeline.
Related PR: https://github.com/microsoft/vcpkg/pull/12612
CI pipeline: https://dev.azure.com/vcpkg/public/_build/results?buildId=41977&view=logs&jobId=440d5d2e-7b5f-5979-92a7-896b72338e4c&j=440d5d2e-7b5f-5979-92a7-896b72338e4c&t=223f498b-1424-5859-bc4f-c47d906dd0dc
Downloading nuget...
  https://dist.nuget.org/win-x86-commandline/v5.5.1/nuget.exe -> D:\downloads\22ea847d-nuget.exe
The following packages will be built and installed:
    boost-build[core]:x86-windows
  * boost-uninstall[core]:x86-windows
    protobuf[core]:x86-windows
    sqlite3[core]:x86-windows
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x86-windows...
A suitable version of powershell-core was not found (required v6.2.1). Downloading portable powershell-core v6.2.1...
Downloading powershell-core...
  https://github.com/PowerShell/PowerShell/releases/download/v6.2.1/PowerShell-6.2.1-win-x86.zip -> D:\downloads\PowerShell-6.2.1-win-x86.zip
WinHttpReceiveResponse() failed: 12152
Creating failure logs output directory C:\agent\_work\1\a\failure-logs
Loading dependency information for 116 packages...
Detecting compiler hash for triplet arm-uwp...
A suitable version of powershell-core was not found (required v6.2.1). Downloading portable powershell-core v6.2.1...
Downloading powershell-core...
  https://github.com/PowerShell/PowerShell/releases/download/v6.2.1/PowerShell-6.2.1-win-x86.zip -> D:\downloads\PowerShell-6.2.1-win-x86.zip
Extracting powershell-core...

Similar issue encountered before https://github.com/microsoft/vcpkg/pull/12918

preinstall no longer exists.


no connected

since 03/17/2023 he has been disconnected.

Mine is also offline, did you find a solution?

Mine is offline too since many days!

comigo a mesma coisa a carteira nao conecta de jeito nenhum

Carteira foi atualizada.
Link: https://github.com/Antares-RXD/electron-novo/releases/tag/0.3.0

version 0.3.0 of electron wallet has not been able to connect to the servers for many days.

Não estou conseguindo conectar na Electron v0.3.0

Hi everyones, I am mining NOVO and I just discovered that my Electron Novo 0.3.0 is offline, network wallet seems down, anyone has the same problem ?

@Supermurat2016
Estou com o mesmo problema a alguns dias

Is there any solution yet?


DEV | Add Interests & Recommendation to Spaces

Description:
This feature adds a new field "interests" to the Space model, which represents various interests that are associated with a particular space. Each space can have multiple interests, and each interest can be associated with multiple spaces.
This will allow us to filter spaces based on a user's interests and make space recommendations accordingly.
Brief of the changes made:
Added a ManyToMany relationship between Space and Interest models.
Updated the my_spaces_list view to handle form submissions for selecting an interest.
Updated the my_spaces_list.html template to include a form for interest selection.
Added error handling to account for cases where a selected interest does not exist.

I am closing this pull request due to the change of recommendation algorithm.


feat: Add ISC license

Description
resolves https://github.com/aeternity/smart-contract-verifier/issues/55
Demo

Checklist:

[x] I have read and followed the Contributing Guide
[x] Add ISC license

Smart Contracts verification doesn't work with ISC license:
https://github.com/aeternity/aescan/assets/69896204/fc3a4e57-1753-4a69-bc26-075098f650ae
or am I doing something wrong?

added on verifier side https://github.com/aeternity/smart-contract-verifier/pull/56

It works for me now. You can retry @Liubov-crypto

Tested on testnetwork, works fine. LGTM


chore: fix some spelling errors

Description
Fix some of the spelling errors reported by cspell; other words added to a custom dictionary.
Checklist

[x] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[x] I have followed the Contributor Guide when preparing my PR.

Breaking Change?

[-] Yes, this PR is a breaking change.
[x] No, this PR is not a breaking change.

Related Issues
WIP for #2108

It fixes more than was in 2108, though not all that we have in the repo

It fixes more than was in 2108, though not all that we have in the repo

So 2108 can be closed?


Improve end-to-end experience of annotating model and flowing thru migrations to schema

Spun off from https://github.com/aspnet/EntityFramework/issues/5297 (flowing [Description] into SQL Server extended properties).

We need to verify the end to end experience and then look at ways to improve what is generated in migrations (i.e. can providers replace the code that shows what annotations were altered with there own first class methods, etc.).
As part of this, we should consider whether providers play a part in model diffing and if we allow custom migration operations.

Possible overlap with #6546


Signer>UI issue bleeding text

Issue: Text bleeds onto other icons in key management.
Steps: 1. Go to Key management and edit a key
2.  Give a long name , grt 14 char and save > Text bleeds as in the screenshot

I'm closing this as it will be moot issue once the new UI/UX overhaul is completed.


As a Project coordinator, I want to see "Edit Project" in the task list, so that I know that I am editing a project

Description:
The current text in the task list only makes sense when creating a project. This user story makes the wording in the task list change when the user is editing a project, as illustrated below

Acceptance Criteria:
Given that I am editing a project
When I view the task list
Then it has a text consistent with the "Editing" action
Development Checklist:

[ ] The TaskList component should have a mode variable, where mode is "view" | "create" | "update" (may have been added in #440 , depending which issue is done first). To avoid duplicating the mode determination logic, it should be done within the TaskList
[ ] To determine whether the page is in add or edit mode, one option would be to follow the projectByProjectId relation in the TaskList_projectRevision fragment. If the project doesn't exist yet, we are in "add" mode. We need to follow this relation to find the proposalReference either way (see below)
[ ] The title of the TaskList should be Editing <proposal reference>.
[ ] In edit mode, there will be no "optional" in the second section heading.
[ ] the links the the various forms should start with "Edit".
[ ] The last step should say Submit Changes instead of Submit Project (ignore the screenshot above on this one)
[ ] Meets the DOD

Hey team! Please add your planning poker estimate with ZenHub @BCerki @dleard @gurjmatharu @mikevespi @pbastia

Awesome @gurjmatharu ! Thank you for your work on this one. I tested in dev by editing an existing project and editing a field within each task list. Worked as expected.


Inconsistencies with pageSize, queryDocuments and QueryAPI

I recently reached over 100 documents in my collections however I encountered an issue. Newer documents wouldn't be fetched by Stored Procedures.
After investigation I think it's related to the pageSize property of the Feed Options.
Consider the following stored procedure scripts:
function sqlQueryWithoutContains(ids) {
    __.queryDocuments(__.getSelfLink(),
    "SELECT * FROM i WHERE i.id = '" + ids[0] + "'",
    { pageSize: 100 },
    function (err, feed, options) {
        __.response.setBody(feed);
    });
}

function sqlQueryWithContains(ids) {
    __.queryDocuments(__.getSelfLink(),
        "SELECT * FROM i WHERE ARRAY_CONTAINS(" + JSON.stringify(ids) + ", i.id)",
        { pageSize: 100 },
        function (err, feed, options) {
        __.response.setBody(feed);
    });
}

function parameterizedQueryWithoutContains(ids) {
    __.queryDocuments(__.getSelfLink(), {
        query: "SELECT * FROM i WHERE i.id = @id",
        parameters: [{ name: "@id", value: ids[0] }]
    }, { pageSize: 100 },
    function (err, feed, options) {
        __.response.setBody(feed);
    });
}

function parameterizedQueryWithContains(ids) {
    __.queryDocuments(__.getSelfLink(), {
        query: "SELECT * FROM i WHERE ARRAY_CONTAINS(@ids, i.id)",
        parameters: [{ name: "@ids", value: ids }]
    }, { pageSize: 100 },
    function (err, feed, options) {
        __.response.setBody(feed);
    });
}

function queryAPIWithoutContains(ids) {
    __.filter(function (i) {
        return i.id == ids[0];
    }, { pageSize: 100 },
    function (err, feed, options) {
        __.response.setBody(feed);
    });
}

function queryAPIWithContains(ids) {
    __.filter(function (i) {
        return ids.indexOf(i.id) > -1;
    }, { pageSize: 100 },
    function (err, feed, options) {
        __.response.setBody(feed);
    });
}

I would execute each script above with ids = ["e073396f-c49c-4399-9db5-9992804930fa"]
For every script involving queryDocuments() I'd get the desired item.
However when using filter() I wouldn't get it.
If I increase the pageSize enough I will get the item with filter()
The other thing I have noticed is that the request charge for queryAPIWithoutContains() is way higher than the queryDocuments() counterparts (~40 vs ~12)
When avoiding ARRAY_CONTAINS in queryDocuments() I'm saving ~30 RU however doing the same with filter() only saves ~5 RU.
I guess filter() iterates through each document until pageSize is reached and each iteration uses RU.
But queryDocuments() will get my item as long as my pageSize value is at least 1 which is the expected behaviour according to the documentation.

SQL: ARRAY_CONTAINS
ARRAY_CONTAINS is optimized to be used on arrays inside your JSON document, rather than an array coming in from a query parameter.
Example Query:
SELECT food
FROM food
WHERE ARRAY_CONTAINS(food.tags, {"name":"babyfood"})

Where food.tags is an array:
  {
    "id": "05740",
    "description": "Turkey, thigh, from whole bird, meat only, raw",
    "tags": [
      {
        "name": "turkey"
      },
      {
        "name": "thigh"
      },
      {
        "name": "raw"
      }
    ],
    "version": 1,
    "foodGroup": "Poultry Products",
    "nutrients": [
      {
        "id": "262",
        "description": "Caffeine",
        "nutritionValue": 0,
        "units": "mg"
      },
      {
        "id": "307",
        "description": "Sodium, Na",
        "nutritionValue": 124,
        "units": "mg"
      }
    ]
  }

SQl: IN
In your example, it is better to use the IN keyword.
Example Query:
SELECT food
FROM food
WHERE food.id IN ("05740", "07050")

Example Stored Procedure:
function(ids) {
  var inParam = JSON.stringify(ids).replace("[", "(").replace("]", ")");

  __.queryDocuments(__.getSelfLink(),
    "SELECT * FROM i WHERE i.id IN " + inParam,
    { pageSize: 100 },
    function(err, feed, options) {
      __.response.setBody(feed);
    });
}

JS Query API: filter
queryAPIWithoutContains should return a result properly. I'd like to look deeper if aren't getting one.
As for queryAPIWithContains - I believe the query is behaving as expected.
The JS Query API is able to optimize the following JavaScript constructs so that the query runs on DocumentDB's indices:

Simple operators: = + - * / % | ^ & == != === !=== < > <= >= || && << >> >>>! ~
Literals, including the object literal: {}
var, return

However, DocumentDB is unable to optimize these JavaScript constructs:

Control flow (e.g. if, for, while)
Function calls

The method call, indexOf(), will result in scanning through the collection (which is why it get's missed given the page-size), rather than a quick index lookup.
Query Paging
Similar to running direct queries; queries in stored procedures are returned in pages.
Here is a thorough code sample demonstrating how to handle query paging, response size limits, and script execution bounds.
function (continuationToken) {
  var query = 'SELECT * FROM root';
  var responseBody = [];
  var responseSize = 0;
  var lastContinuationToken;

  tryQuery(continuationToken);

  function tryQuery(continuationToken) {
    // Tune the pageSize to fit your dataset.
    var requestOptions = {
      continuation: continuationToken,
      pageSize: 1
    };

    var accepted = __.queryDocuments(__.getSelfLink(), query, requestOptions,
      function(err, feed, responseOptions) {
        // The size of the current query response page.
        var queryPageSize = JSON.stringify(feed).length;

        // DocumentDB has a response size limit of 1 MB.
        if (responseSize + queryPageSize < 1024 * 1024) {
          // Append query results to responseBody.
          responseBody = responseBody.concat(feed);

          // Keep track of the response size.
          responseSize += queryPageSize;

          if (responseOptions.continuation) {
            // If there is a continuation token... Run the query again to get the next page of results
            lastContinuationToken = responseOptions.continuation;
            tryQuery(responseOptions.continuation);
          } else {
            // If there is no continutation token, we are done. Return the response.
            __.response.setBody({
              "message": "Query completed succesfully.",
              "queryResponse": responseBody
            });
          }
        } else {
          // If the response size limit reached; run the script again with the lastContinuationToken as a script parameter.
          __.response.setBody({
            "message": "Response size limit reached.",
            "lastContinuationToken": lastContinuationToken,
            "queryResponse": responseBody
          });
        }
      });

    if (!accepted) {
      // If the execution limit reached; run the script again with the lastContinuationToken as a script parameter.
      __.response.setBody({
        "message": "Execution limit reached.",
        "lastContinuationToken": lastContinuationToken,
        "queryResponse": responseBody
      });
    }
  }
}

I forgot about IN. Seems like I should use that instead.
I supposed if we have pageSize = 100 we should be able to get up to 100 documents (in the feed response).
I initially didn't check if I had a continuation token and I actually had a continuation token that allowed me to get the desired document.
After further digging I noticed that this happens when I work with arrays.
Consider the following collection:

    var ids = ["471962d3-a021-4c12-86c9-01cca307b2a2", "d8f2966d-d1ea-4fef-8c1f-03b14678b5fd", "50d0ec4f-1c80-4ac8-a43a-fdfd62823414"];
    __.filter(function (i) {
        return i.id == ids[0];
    }, { pageSize: 1 }, function (err, feed, options) {
        __.response.setBody(feed);
    });

I initially thought this would get me the document whose id was 471962d3-a021-4c12-86c9-01cca307b2a2 but it didn't.
I got no result but I got a continuation token.
    var ids = ["471962d3-a021-4c12-86c9-01cca307b2a2", "d8f2966d-d1ea-4fef-8c1f-03b14678b5fd", "50d0ec4f-1c80-4ac8-a43a-fdfd62823414"];
    __.filter(function (i) {
        return i.id == ids[0];
    }, { pageSize: 1 }, function (err, feed, options) {
        __.filter(function (i) {
            return i.id == ids[0];
        }, { pageSize: 1, continuation: options.continuation }, function (err, feed, options) {
            __.response.setBody(feed);
        });
    });

However, doing this gets the document (I suppose it's because it's the 2nd item in the collection).
    var ids = ["471962d3-a021-4c12-86c9-01cca307b2a2", "d8f2966d-d1ea-4fef-8c1f-03b14678b5fd", "50d0ec4f-1c80-4ac8-a43a-fdfd62823414"];
    var id = ids[0];
    __.filter(function (i) {
        return i.id == id;
    }, { pageSize: 1 }, function (err, feed, options) {
        __.response.setBody(feed);
    });

If I'm not using an array I'm getting the document.
    var ids = ["471962d3-a021-4c12-86c9-01cca307b2a2", "d8f2966d-d1ea-4fef-8c1f-03b14678b5fd", "50d0ec4f-1c80-4ac8-a43a-fdfd62823414"];
    __.filter(function (i) {
        return i.id == ids[0];
    }, { pageSize: 5 }, function (err, feed, options) {
        __.response.setBody(feed);
    });

Increasing the pageSize allows me to get the document.
The same behaviour is expected when using indexOf().
I believe the scanning that you mentionned happens as soon as an array is involved.
This is crazy and I'm currently questionning my sanity :sweat_smile:
But now I understand what's going on with indexOf() thanks !


Introduce Writer Callback

Refactor internal Stan code to use a writer callback class left for the interfaces to implement.  Using the writer callback everywhere will remove the last traces of cout/cerr from the code (addressing #699) while giving the interfaces complete control over output (addressing #453).

[ ] #1601: remove unused code
[ ] #1602: implement writers

I appreciate what you're doing here, but it seems a bit hasty (esp. probe_args). It feels like one is inventing a protocol from scratch to communicate key value pairs via strings. At minimum, I think I'd prefer we pick something recognizable (like JSON) -- or do a little bit more work to articulate what are valid types of values and spec it in Protobuf.
I suppose I'd also like to see what the big C++ object approach looks like. I don't have that much time this week, but I'd be willing to give a shot at articulating my ideas in a cmdstan branch like this one.

To be clear, the argument stuff is not new.
probe_args is for automated testing.
On Mar 19, 2015, at 5:52 PM, Allen Riddell<EMAIL_ADDRESS>wrote:

I appreciate what you're doing here, but it seems a bit hasty (esp. probe_args). It feels like one is inventing a protocol from scratch to communicate key value pairs via strings. At minimum, I think I'd prefer we pick something recognizable (like JSON) -- or do a little bit more work to articulate what are valid types of values and spec it in Protobuf.
I suppose I'd also like to see what the big C++ object approach looks like. I don't have that much time this week, but I'd be willing to give a shot at articulating my ideas in a cmdstan branch like this one.
—
Reply to this email directly or view it on GitHub.

Hmm.. it would be cool if the branch was referenced here somehow (maybe add "Closes #1361" in the commit?). Here's a commit I was looking at: c68ac51d2edb3fb8e59cbeccdfffa31c1879338d
For Python and R I think it's fair to say that it's much easier to create a (pointer to) a struct (or C++ class) and pass that around than to write a C++ callback.

The callbacks here are just classes that implement
certain functions — they should be straightforward
to implement (see the cout/cerr and stream
implementations that will eventually move to CmdStan).
On Mar 19, 2015, at 6:36 PM, Allen Riddell<EMAIL_ADDRESS>wrote:

Hmm.. it would be cool if the branch was referenced here somehow (maybe add "Closes #1361" in the commit?). Here's a commit I was looking at: c68ac51
For Python and R I think it's fair to say that it's much easier to create a (pointer to) a struct (or C++ class) and pass that around than to write a C++ callback.
—
Reply to this email directly or view it on GitHub.

I suppose the argument against having interfaces have to write C++ functions starts like this: it's easier to for interfaces to pass around a pointer or a chunk of bytes without knowing too much about it. In fact, with JSON or protobuf they don't even need to touch C++ code potentially. Having them implement a C++ class with specific properties is a significantly bigger hurdle.
It might be helpful to check out how RStan (and PyStan, more or less) currently deal with getting config and defaults setup:
https://github.com/stan-dev/rstan/blob/master/rstan/rstan/inst/include/rstan/stan_args.hpp

If you really don't want to work at the C++ level, it
should be possible to completely rewrite PyStan to follow
Stan.jl and MatlabStan (and my original code for RStan), which
would have the user specify a command-line argument as a string,
write the data out to a file, and then execute a CmdStan process
and then collect up the CSV data.
The major problem with this is that it involves an I/O roundtrip,
but that's not usually a bottleneck.
It solves all of Michael's issues with drift.  And it means you
don't need to write any C++ at all.
It would still mean implementing all the posterior analysis stuff
in Python.  Or you could call the print function in CmdStan and
just show it as a string.  Or you could call the C++, but that'd
put you back in C++ land.

Bob

On Mar 20, 2015, at 7:26 AM, Allen Riddell<EMAIL_ADDRESS>wrote:
I suppose the argument against having interfaces have to write C++ functions starts like this: it's easier to for interfaces to pass around a pointer or a chunk of bytes without knowing too much about it. In fact, with JSON or protobuf they don't even need to touch C++ code potentially. Having them implement a C++ class with specific properties is a significantly bigger hurdle.
It might be helpful to check out how RStan (and PyStan, more or less) currently deal with getting config and defaults setup:
https://github.com/stan-dev/rstan/blob/master/rstan/rstan/inst/include/rstan/stan_args.hpp
—
Reply to this email directly or view it on GitHub.

On Thu, Mar 19, 2015 at 11:36:19AM -0700, Allen Riddell wrote:

Hmm.. it would be cool if the branch was referenced here somehow (maybe add "Closes #1361" in the commit?). Here's a commit I was looking at: c68ac51d2edb3fb8e59cbeccdfffa31c1879338d
For Python and R I think it's fair to say that it's much easier to create a (pointer to) a struct (or C++ class) and pass that around than to write a C++ callback.
I also think callback should not be used too much. It adds indirection and inflexibility.

Jiqiang

Reply to this email directly or view it on GitHub:
https://github.com/stan-dev/stan/issues/1361#issuecomment-83708981

I think shelling out to call cmdstan is a mistake but my only evidence is that RStan and PyStan are working rather smoothly right now and could be working even more smoothly if the steps outlined in the Stan 3.0 wiki page were carried through (i.e., the Python and R interface/classes need to be refactored).
I suspect Julia would be following the same route as Python and R if the interface could be accessed without C++.

I like the callback plan!  It's the right way to
write these kind of interfaces for flexibility.
Jiqiang --- what did you think was inflexible?
It does add a bit of indirection, or more specifically,
infersion of control:
http://en.wikipedia.org/wiki/Inversion_of_control
How do you propose returning results without something
like a callback?  Were you thinking just getting a protocol
buffer object as a string or something like a C++ data
structure returned?  Both are heavy compared to callbacks,
which don't produce any long-lived memory overhead, much less
conversions to strings and back, which is really slow.  They
also require all the memory to be buffered up, whereas CmdStan
is going to stream answers to an output stream (typically a file).
I'm having a bit of trouble seeing how we can stay away
from C++ and avoid just calling CmdStan as an independent
process doing everything through files.

Bob

On Mar 20, 2015, at 10:04 AM, maverickg<EMAIL_ADDRESS>wrote:
On Thu, Mar 19, 2015 at 11:36:19AM -0700, Allen Riddell wrote:

Hmm.. it would be cool if the branch was referenced here somehow (maybe add "Closes #1361" in the commit?). Here's a commit I was looking at: c68ac51d2edb3fb8e59cbeccdfffa31c1879338d
For Python and R I think it's fair to say that it's much easier to create a (pointer to) a struct (or C++ class) and pass that around than to write a C++ callback.
I also think callback should not be used too much. It adds indirection and inflexibility.

Jiqiang

Reply to this email directly or view it on GitHub:
https://github.com/stan-dev/stan/issues/1361#issuecomment-83708981
—
Reply to this email directly or view it on GitHub.

Are these things really as mutually exclusive as it sounds?  With a consistent C++-level interface which requires callbacks I don't think it would be too hard to write standard callbacks for interfacing with protocol buffers much like Michael wrote some standard ones for working with streams.  At least that's my impression based on the simple tutorials: https://developers.google.com/protocol-buffers/docs/cpptutorial.  That adds that pinch point where interfaces could be standardized without pushing protocol-buffers stuff deep into Stan.  It also gets you around C++ being harder to call than C and if somebody wants to make a high-performance interface they can write custom callbacks in C++.  I'm having a hard time telling if that's over-engineering but I don't think so.

All else being equal, I'd prefer not to have a chain of
dominos in the interface --- they're hard to maintain.
Also, if the Protocol Buffer to C++ structure isn't in Stan,
it doesn't solve the interface's problem of not wanting to
write so much C++.
One place where Protocol buffers aren't sufficient is for
interrupts --- we need at least one interface-driven callback
for interrupts so we can stop C++ Stan's looping if the interface
wants to stop.

Bob

On Mar 21, 2015, at 4:12 AM, Krzysztof Sakrejda<EMAIL_ADDRESS>wrote:
Are these things really as mutually exclusive as it sounds? With a consistent C++-level interface which requires callbacks I don't think it would be too hard to write standard callbacks for interfacing with protocol buffers much like Michael wrote some standard ones for working with streams. At least that's my impression based on the simple tutorials: https://developers.google.com/protocol-buffers/docs/cpptutorial. That adds that pinch point where interfaces could be standardized without pushing protocol-buffers stuff deep into Stan. It also gets you around C++ being harder to call than C and if somebody wants to make a high-performance interface they can write custom callbacks in C++. I'm having a hard time telling if that's over-engineering but I don't think so.
—
Reply to this email directly or view it on GitHub.

On Mar 20, 2015, at 10:16 AM, Allen Riddell<EMAIL_ADDRESS>wrote:
I think shelling out to call cmdstan is a mistake but my only evidence is that RStan and PyStan are working rather smoothly right now and could be working even more smoothly if the steps outlined in the Stan 3.0 wiki page were carried through (i.e., the Python and R interface/classes need to be refactored).

Things are definitely much smoother than they use to be, but we
still face:

installation issues in PyStan and RStan

compatiblity of C++ toolchain with RStan issues

limitations imposed by R and Python w.r.t. C++11, which
we'd really like to start using for code cleanliness and
efficiency

crashing issues in RStan (presumably due to saved state and/or
RStudio --- nobody can give us a reproducible example, and everyone
says it doesn't happen in the terminal version of RStan).

Also, a thin wrapper would solve the

not require any C++ coding on the interface side

requiring updates to RStan or PyStan with every Stan C++
release

A very thin wrapper (just passing a string) would mean

no updates needed at all to interfaces when CmdStan changes

I suspect Julia would be following the same route as Python and R if the interface could be accessed without C++.

See Rob's response.

Bob

Hi Bob,
On 03/20, Bob Carpenter wrote:

All else being equal, I'd prefer not to have a chain of
dominos in the interface --- they're hard to maintain.

I agree, but the potential gains of having an extremely smooth
installation experience (via install.packages or "pip install pystan")
could trump this, I think. I realize there are some R packages that
compile and call external programs (topicmodels comes to mind, which I
think compiles and runs GibbsLDA++), but this approach is less common in
Python.

Also, if the Protocol Buffer to C++ structure isn't in Stan,
it doesn't solve the interface's problem of not wanting to
write so much C++.

This reflects my thinking as well.

One place where Protocol buffers aren't sufficient is for
interrupts --- we need at least one interface-driven callback
for interrupts so we can stop C++ Stan's looping if the interface
wants to stop.

I'm perfectly fine with the callback here. It happens that the callback
can be in C -- which is nice for (future) interfaces that do not have
support for interfacing with C++.

It has occurred to me that it would be helpful if we had some examples of other software projects that deal with similar problems. Clearly Google has solved the problem by passing around Protocol Buffers for everything. But closer to home (i.e., scientific computing) is the Juypter/IPython project, which is a bit like RStudio but supports working with Octave, R, Julia, and Python. Here's how it works: http://ipython.org/ipython-doc/3/development/how_ipython_works.html
Basically IPython exposes ZeroMQ sockets and passes around everything with JSON. It's easy to appreciate that this makes interoperability trivial for any language that supports JSON and ZeroMQ (i.e., everything). Of course, in principle it's not too far removed from the Google approach. It's also pretty slow.
That this discussion is taking time makes perfect sense to me. Up until this point there hasn't been much/any effort to coordinate development between R/Py/CmdStan when that coordination involved more than 2 people.
Perhaps it would be helpful if I added more details to an alternative that avoided callbacks to the Wiki page? I'd also like to hear with @maverickg thinks about all of this.

(in response to @bob-carpenter's earlier comment; github needs threaded issue discussions!)
I don't mind updating PyStan every release of Stan (especially if library path renaming is kept to a minimum).
Here's Rob's comment from the list:
"As far as Julia and today’s Stan.jl are concerned, for Julia 0.3.x Allen’s earlier comment about following R and Python without C++ is correct. As alternatives folks can also fall back to RCall.jl and/or PyCall.jl."

Replying to two mails from Allen at once:
...

I agree, but the potential gains of having an extremely smooth
installation experience (via install.packages or "pip install pystan")
could trump this, I think. I realize there are some R packages that
compile and call external programs (topicmodels comes to mind, which I
think compiles and runs GibbsLDA++), but this approach is less common in
Python.

Many R packages compile and run extern C, C++ or Fortran
code.  The obstacle presented by Stan is that we need to
compile each model at runtime.
So that smoothe installation is only going to happen for
Stan for someone who has a recent enough C++ compiler installed.
...

Perhaps it would be helpful if I added more details to an alternative that avoided callbacks to the Wiki page? I'd also like to hear with @maverickg thinks about all of this.

That would be helpful to me at least.

Bob

Added to the wiki a sketch of how the command function would work in a
Protocol Buffer world:
https://github.com/stan-dev/stan/wiki/Stan-API-Refactor#command-with-protocol-buffers
Let me know what you think.
On 03/21, Bob Carpenter wrote:

Replying to two mails from Allen at once:
...

I agree, but the potential gains of having an extremely smooth
installation experience (via install.packages or "pip install pystan")
could trump this, I think. I realize there are some R packages that
compile and call external programs (topicmodels comes to mind, which I
think compiles and runs GibbsLDA++), but this approach is less common in
Python.

Many R packages compile and run extern C, C++ or Fortran
code.  The obstacle presented by Stan is that we need to
compile each model at runtime.
So that smoothe installation is only going to happen for
Stan for someone who has a recent enough C++ compiler installed.
...

Perhaps it would be helpful if I added more details to an alternative that avoided callbacks to the Wiki page? I'd also like to hear with @maverickg thinks about all of this.

That would be helpful to me at least.

Bob

Reply to this email directly or view it on GitHub:
https://github.com/stan-dev/stan/issues/1361#issuecomment-84494026

I don't think passing C++ objects is a problem --- we're
connecting to them directly in C++, not trying to serialize
as in protocol buffers.
As popular as protocol buffers are at Google (not an uncorrelated
set of independent choices to use protocol buffers), are they used
to communicate between C++ programs in memory (the way PyStan and
RStan link to Stan) or just for serialized for transport via file or
socket?
We looked at something like JSON, and it's very heavy to have
structure per parameter group because of all the added brackets.
Right now, we're just passing the parameter values for a draw as
an unstructured array, the downside of which is that it needs to
be translated back to structure for the extractors (at least in RStan).

Bob

On Mar 24, 2015, at 12:19 PM, Allen Riddell<EMAIL_ADDRESS>wrote:
Added to the wiki a sketch of how the command function would work in a
Protocol Buffer world:
https://github.com/stan-dev/stan/wiki/Stan-API-Refactor#command-with-protocol-buffers
Let me know what you think.
On 03/21, Bob Carpenter wrote:

Replying to two mails from Allen at once:
...

I agree, but the potential gains of having an extremely smooth
installation experience (via install.packages or "pip install pystan")
could trump this, I think. I realize there are some R packages that
compile and call external programs (topicmodels comes to mind, which I
think compiles and runs GibbsLDA++), but this approach is less common in
Python.

Many R packages compile and run extern C, C++ or Fortran
code. The obstacle presented by Stan is that we need to
compile each model at runtime.
So that smoothe installation is only going to happen for
Stan for someone who has a recent enough C++ compiler installed.
...

Perhaps it would be helpful if I added more details to an alternative that avoided callbacks to the Wiki page? I'd also like to hear with @maverickg thinks about all of this.

That would be helpful to me at least.

Bob

Reply to this email directly or view it on GitHub:
https://github.com/stan-dev/stan/issues/1361#issuecomment-84494026
—
Reply to this email directly or view it on GitHub.

My impression is that protocol buffers are used to communicate between distinct machines running services written in C++ (or Go).
Ultimately, I think the reason I'm attracted to Protocol Buffers is because it could make communication to and from Stan easier in a variety of settings (including the case where one machine is compiling and running the model and sending results to another machine). Allowing communication to and from R and Python has been the source of a lot of interesting work recently, including IPython and Shiny.
IPython and Shiny (somehow R and node.js talk to each other, right?) are making scientific computing much more accessible by abstracting (in some cases) away the computer (e.g., you can run IPython and RStudio on an ephemeral cloud server). In this context having some platform-agnostic way of sending and receiving data to and from stan seems like a good goal.
From the meeting yesterday I think we all agreed that the callback method would go forward and then I would be free to try things out on my own using Protocol Buffers and see how much of a performance hit (or gain?) there was.
re: callback method refactoring. I mentioned that I particularly like Bob's command function signature in the Wiki. I hope we can eventually get to something that simple.

On Mar 26, 2015, at 12:40 AM, Allen Riddell<EMAIL_ADDRESS>wrote:
My impression is that protocol buffers are used to communicate between distinct machines running services written in C++ (or Go).
Ultimately, I think the reason I'm attracted to Protocol Buffers is because it could make communication to and from Stan easier in a variety of settings (including the case where one machine is compiling and running the model and sending results to another machine). Allowing communication to and from R and Python has been the source of a lot of interesting work recently, including IPython and Shiny.

I guess that need comes up because people want to mix R and Python
packages and neither language has a complete set.
The danger is robustness and performance from having to write all the
adapters and munge data back-and-forth, but I guess for most of what
people do, neither of these is an issue --- if it were they probably
wouldn't be using R or Python!  R users seem to be happy to just restart
R or RStudio when something crashes.  I think that stems from them primarily
being user-facing front ends rather than back-end servers and so not
requiring any kind of service level agreements.

IPython and Shiny (somehow R and node.js talk to each other, right?)

Apparently not very robustly --- Jonah just told me there's a known (or suspected)
bug in R's JSON transport package that causes Shiny apps to hang.  I
unfortunately ran into that one during a demo of shinyStan two days ago.
As soon as things start to break like this, I begin to lose confidence in
them.  (Not an issue with shinyStan yet --- it's still early days there and
I'm not expecting a lot of robustness yet, though I think I'm going to stay
away from live demos until I can convince myself I can do them without freezing.
It is a major issue with Stan, and we're still struggling with robustness,
especially across platforms;  it's why we keep prioritizing robustness and
error checking over new features.)

are making scientific computing much more accessible by abstracting (in some cases) away the computer (e.g., you can run IPython and RStudio on an ephemeral cloud server). In this context having some platform-agnostic way of sending and receiving data to and from stan seems like a good goal.

Agreed.  I just wanted to point out that it's a different goal
than communicating between PyStan and the Stan C++ layer.  We
control both ends of that pipeline.

From the meeting yesterday I think we all agreed that the callback method would go forward and then I would be free to try things out on my own using Protocol Buffers and see how much of a performance hit (or gain?) there was.

Sounds good --- I think that's the right level of abstraction.
We'd implement some kind of data serialization on top of a
direct C++ API.  The costs of encoding/decoding are usually
fairly small compared to transport between machines, or even between
disk and back.

Bob

Michael, did you change interface to interface_callbacks?

I did — I though it was more descriptive and would avoid confusion.
On Apr 3, 2015, at 3:34 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

Michael, did you change interface to interface_callbacks?
—
Reply to this email directly or view it on GitHub.

ok. I merged develop into the branch.

@betanalpha, were you able to run the unit tests on this branch? I've fixed a handful, but can't get all of it to run.

@betanalpha, don't worry about it... I'm almost through it, I think.

The tests were all working at my commit, but I haven’t
checked anything after all of the recent merges...
On May 27, 2015, at 11:02 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

@betanalpha, don't worry about it... I'm almost through it, I think.
—
Reply to this email directly or view it on GitHub.

That's what I was hoping you'd say. I'll get it working.
On Wednesday, May 27, 2015, Michael Betancourt<EMAIL_ADDRESS>wrote:

The tests were all working at my commit, but I haven’t
checked anything after all of the recent merges...
On May 27, 2015, at 11:02 PM, Daniel Lee<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

@betanalpha, don't worry about it... I'm almost through it, I think.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/issues/1361#issuecomment-106098154.

Ok, so there was definitely a test that wasn't running --
src/test/unit/mcmc/chains_test.cpp. I've gotten it to compile, but there's
still an issue: the parser() function doesn't like the output generated by
the current version of Stan. Know what's going on?
On Wed, May 27, 2015 at 6:42 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

That's what I was hoping you'd say. I'll get it working.
On Wednesday, May 27, 2015, Michael Betancourt<EMAIL_ADDRESS>wrote:

The tests were all working at my commit, but I haven’t
checked anything after all of the recent merges...
On May 27, 2015, at 11:02 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

@betanalpha, don't worry about it... I'm almost through it, I think.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/issues/1361#issuecomment-106098154.

Or the updated CSV reader doesn’t like static, deprecated
files in the test_csv_files folder?  I’ve hated these tests
from the beginning because they never catch anything
and just require us to change them every f’ing time to
pass.
On May 28, 2015, at 11:10 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

Ok, so there was definitely a test that wasn't running --
src/test/unit/mcmc/chains_test.cpp. I've gotten it to compile, but there's
still an issue: the parser() function doesn't like the output generated by
the current version of Stan. Know what's going on?
On Wed, May 27, 2015 at 6:42 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

That's what I was hoping you'd say. I'll get it working.
On Wednesday, May 27, 2015, Michael Betancourt<EMAIL_ADDRESS>wrote:

The tests were all working at my commit, but I haven’t
checked anything after all of the recent merges...
On May 27, 2015, at 11:02 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

@betanalpha, don't worry about it... I'm almost through it, I think.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/issues/1361#issuecomment-106098154.

—
Reply to this email directly or view it on GitHub.

This one isn't a false-positive. I just regenerated the test files. I tried
to debug it, but the parse method is just choking.
I'll take an alternative if you have one. You're right: this isn't a really
good way to do a unit test. We need to separate out the file processing
from the chains object, but we don't have a good way to do that right now.
PS. these files haven't changed since Dec 2013. The history before that
isn't easy to get to. If you want to have these generated as part of the
test, let me know. I think I can figure that out. But... I don't think that
really helps, right?
On Thu, May 28, 2015 at 6:42 PM, Michael Betancourt <
<EMAIL_ADDRESS>wrote:

Or the updated CSV reader doesn’t like static, deprecated
files in the test_csv_files folder? I’ve hated these tests
from the beginning because they never catch anything
and just require us to change them every f’ing time to
pass.

Did you regenerate them with the corresponding cmdstan branch?
It doesn’t look like the test files have the update format, hence
the lexical cast errors.  I’ll try to fix the test later this afternoon.
On May 29, 2015, at 1:35 AM, Daniel Lee<EMAIL_ADDRESS>wrote:

This one isn't a false-positive. I just regenerated the test files. I tried
to debug it, but the parse method is just choking.
I'll take an alternative if you have one. You're right: this isn't a really
good way to do a unit test. We need to separate out the file processing
from the chains object, but we don't have a good way to do that right now.
PS. these files haven't changed since Dec 2013. The history before that
isn't easy to get to. If you want to have these generated as part of the
test, let me know. I think I can figure that out. But... I don't think that
really helps, right?
On Thu, May 28, 2015 at 6:42 PM, Michael Betancourt <
<EMAIL_ADDRESS>wrote:

Or the updated CSV reader doesn’t like static, deprecated
files in the test_csv_files folder? I’ve hated these tests
from the beginning because they never catch anything
and just require us to change them every f’ing time to
pass.

—
Reply to this email directly or view it on GitHub.

By the way, at the end of the whole refactor it will be easy to
run models solely through the C++ API allowing us to auto generate
files for tests like these independent of any interface.  The interfaces
can then test their own implementations independently.
On May 29, 2015, at 9:55 AM, Michael Betancourt<EMAIL_ADDRESS>wrote:

Did you regenerate them with the corresponding cmdstan branch?
It doesn’t look like the test files have the update format, hence
the lexical cast errors.  I’ll try to fix the test later this afternoon.
On May 29, 2015, at 1:35 AM, Daniel Lee<EMAIL_ADDRESS>wrote:

This one isn't a false-positive. I just regenerated the test files. I tried
to debug it, but the parse method is just choking.
I'll take an alternative if you have one. You're right: this isn't a really
good way to do a unit test. We need to separate out the file processing
from the chains object, but we don't have a good way to do that right now.
PS. these files haven't changed since Dec 2013. The history before that
isn't easy to get to. If you want to have these generated as part of the
test, let me know. I think I can figure that out. But... I don't think that
really helps, right?
On Thu, May 28, 2015 at 6:42 PM, Michael Betancourt <
<EMAIL_ADDRESS>wrote:

Or the updated CSV reader doesn’t like static, deprecated
files in the test_csv_files folder? I’ve hated these tests
from the beginning because they never catch anything
and just require us to change them every f’ing time to
pass.

—
Reply to this email directly or view it on GitHub.

Thanks. I used the latest develop branch: there was still something
incompatible about this branch. If all it takes is to run again, I'll do
that.
On Friday, May 29, 2015, Michael Betancourt<EMAIL_ADDRESS>wrote:

By the way, at the end of the whole refactor it will be easy to
run models solely through the C++ API allowing us to auto generate
files for tests like these independent of any interface. The interfaces
can then test their own implementations independently.
On May 29, 2015, at 9:55 AM, Michael Betancourt<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','betanalpha@gmail.com');>> wrote:

Did you regenerate them with the corresponding cmdstan branch?
It doesn’t look like the test files have the update format, hence
the lexical cast errors. I’ll try to fix the test later this afternoon.
On May 29, 2015, at 1:35 AM, Daniel Lee<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

This one isn't a false-positive. I just regenerated the test files. I
tried
to debug it, but the parse method is just choking.
I'll take an alternative if you have one. You're right: this isn't a
really
good way to do a unit test. We need to separate out the file processing
from the chains object, but we don't have a good way to do that right
now.
PS. these files haven't changed since Dec 2013. The history before that
isn't easy to get to. If you want to have these generated as part of the
test, let me know. I think I can figure that out. But... I don't think
that
really helps, right?
On Thu, May 28, 2015 at 6:42 PM, Michael Betancourt <
<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

Or the updated CSV reader doesn’t like static, deprecated
files in the test_csv_files folder? I’ve hated these tests
from the beginning because they never catch anything
and just require us to change them every f’ing time to
pass.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/issues/1361#issuecomment-106750344.

Yeah, fixing the format of the output files avoid the read_csv issue.
But all the tests fail because the diagnostics are all slightly off due
to the chains being rerun.  I’ll let you figure out what you want to do
there.
Also, perhaps we might as well move stan_csv_reader to cmdstan
in this pull request?  None of the Stan tests should depend on the
cmdstan output or require that it be run.
On May 29, 2015, at 12:16 PM, Daniel Lee<EMAIL_ADDRESS>wrote:

Thanks. I used the latest develop branch: there was still something
incompatible about this branch. If all it takes is to run again, I'll do
that.
On Friday, May 29, 2015, Michael Betancourt<EMAIL_ADDRESS>wrote:

By the way, at the end of the whole refactor it will be easy to
run models solely through the C++ API allowing us to auto generate
files for tests like these independent of any interface. The interfaces
can then test their own implementations independently.
On May 29, 2015, at 9:55 AM, Michael Betancourt<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','betanalpha@gmail.com');>> wrote:

Did you regenerate them with the corresponding cmdstan branch?
It doesn’t look like the test files have the update format, hence
the lexical cast errors. I’ll try to fix the test later this afternoon.
On May 29, 2015, at 1:35 AM, Daniel Lee<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

This one isn't a false-positive. I just regenerated the test files. I
tried
to debug it, but the parse method is just choking.
I'll take an alternative if you have one. You're right: this isn't a
really
good way to do a unit test. We need to separate out the file processing
from the chains object, but we don't have a good way to do that right
now.
PS. these files haven't changed since Dec 2013. The history before that
isn't easy to get to. If you want to have these generated as part of the
test, let me know. I think I can figure that out. But... I don't think
that
really helps, right?
On Thu, May 28, 2015 at 6:42 PM, Michael Betancourt <
<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

Or the updated CSV reader doesn’t like static, deprecated
files in the test_csv_files folder? I’ve hated these tests
from the beginning because they never catch anything
and just require us to change them every f’ing time to
pass.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/issues/1361#issuecomment-106750344.

—
Reply to this email directly or view it on GitHub.

Here are the things that weren't included in stan-dev/stan#1616:

src/stan/services/mcmc/warmup.hpp / src/stan/services/mcmc/sample.hpp -> src/stan/services/sample/run_adaptive_sampler.hpp / src/stan/services/sample/run_adaptive_sampler.hpp
from CmdStan -> src/stan/services/diagnose/diagnose.hpp
from CmdStan -> src/stan/services/optimize/optimize.hpp
remove: src/stan/services/io/write_interation_csv.hpp

I'm leaving this here so I don't forget.

@syclik Is this all done and rolled into the refactor?  If so, would you mind closing?

This is done.


feat: pin exact dependency versions

Pin the dependency version and replace the 'tweetnacl' package with @noble/curves, this PR contains the commits from 'update-naj-to-v4' branch.

close in favor of PR#2


update to use ibm-clang or clang

I would prefer if it checks for the presence of ibm-clang, and if it exists in your path, then it will use, else check for clang. This logic can be applied to zopen_append_to_env()

I would prefer if it checks for the presence of ibm-clang, and if it exists in your path, then it will use, else check for clang. This logic can be applied to zopen_append_to_env()

This makes sense to me. If there is both a supported and unsupported version of clang available, I would think people will want the supported one.

I would prefer if it checks for the presence of ibm-clang, and if it exists in your path, then it will use, else check for clang. This logic can be applied to zopen_append_to_env()

Sounds good.  So, use ibm-clang if it exists and fallback to xlclang if it doesn't.   Put mod in zopen_append_to_env().  I'll get right on it.  Thanks for the pointer!

fwiw, the above second revision is an effort to meet Igor's objectives.

The above commit, removes xlclang.  This is good to know there is another comp_xxx wrapper.  I also, adjusted so that in case a compiler is not found, it will pass to the install message.

You are welcome.  By the way, I'm in the zotsample repo but not this one. I can not merge it.


Fix right margin for landscape phones with button navigation

If you don't have gesture navigation, the navigation buttons go above the comments button - this is bad.

I started looking into this and reworking all the other code related to paddings, but I've noticed that #8 has changed some margins, at least on the main screen. For example here's before and after with compact header:

Before
After

There are also some differences with tablets. Which version should I match?

The left version is definitively the one to go for, that is the way it used to look.
Really glad you are digging into the paddings! I'm currently fixing the squished icons issue by reworking the bottom sheet margins but the rest would be great.


feat(import): sync cli cdk8s import <url> with cdk8s.yaml config file (#890)

Backport
This will backport the following commits from 2.x to 1.x:

feat(import): sync cli cdk8s import <url> with cdk8s.yaml config file (#890)

Questions ?
Please refer to the Backport tool documentation

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1145

Questions ?
Please refer to the Backport tool documentation


⚠ Avatar API Endpoint has degraded performance

In 200d39b, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 2037 ms

Resolved: Avatar API Endpoint performance has improved in 6237a6a.


LBRY will not open on Mac OS.

The Issue
LBRY will not open on Mac OS.
Steps to reproduce

Got email from LBRY at 14:51 EST, clicked on MAC OS button to download latest app.
Opened .dmg and dragged LBRY to Applications folder.
Message says "The daemon has unexpectedly shutdown. Goodbye."

Expected behaviour
should open
Actual behaviour
does not open
System Configuration

Version 0.11.9 (<IP_ADDRESS>2)

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

Can you:

Make sure no lbry processes are running
Run the application
Email ~/lbrynet/lbrynet.log to<EMAIL_ADDRESS>
Thanks!

And sorry it didn't work! :(

@jackrobison - same issue as the guy on slack recently? db migration?
@rcanolty did you have lbry installed previously?

i had lbry installed previously, when I put app in Applications folder, was asked if I wanted to replace old version, i said yes. i do not recall using lbry before, however (i may have just installed without opening).

I don't see this file. Terminal command "ls -a" shows me a hidden file .lbryum, but no .lbrynet.

on os x the lbrynet data folder is ~/Library/Application Support/LBRY @kauffj
https://lbry.io/faq/lbry-directories

Ah, got it. log file attached as text.
lbrynet.txt

Looks like the issue is a failure for the claim_ids table to be corrected. We'll get this fixed.
Appreciate your help on this @rcanolty, if you send me or post a wallet address, happy to send you a tip.
(And if you can't get a wallet address until we fix this, you'll get a notification when this is closed.)

to manually bypass this, delete blockchainname.db and db_revision in the lbrynet data folder

@rcanolty what was the very first version you installed, or around when did you initially install it?

Not sure of first version number, but first email from LBRY was 2016 may 08.
Glad to help, I'd like to see this project succeed.

While definitely a bug, this only affects a small number of old installs and may never get fixed.
Please contact<EMAIL_ADDRESS>and reference this GitHub issue if you'd like assistance from our team in migrating and getting it running again.

And sorry!

If the LBRY tip offer still stands, here is my address: bVxY4EtVtakjxhJqjVLX
632RsaQVci7nLs
Looks like the project is doing well! Just joined the discord group.
Best,
Ryan
On Wed, Jun 14, 2017 at 1:00 PM, Jeremy Kauffman<EMAIL_ADDRESS>wrote:

Looks like the issue is a failure for the claim_ids table to be
corrected. We'll get this fixed.
Appreciate your help on this @rcanolty https://github.com/rcanolty, if
you send me or post a wallet address, happy to send you a tip.
(And if you can't get a wallet address until we fix this, you'll get a
notification when this is closed.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/219#issuecomment-308494677,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMmFDrwm81wNUAL8HvbXdsdDzjzALBFqks5sEBHAgaJpZM4N1v2y
.

@rcanolty sent

ah, sorry, I went with rtc as my channel name, so @rtc? i also just learned
about discord tipbot, if that is easier.
On Mon, Dec 4, 2017 at 9:21 AM, Jeremy Kauffman<EMAIL_ADDRESS>wrote:

@rcanolty https://github.com/rcanolty sent
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/219#issuecomment-348975430,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMmFDkVcC0r_xBPFbX2XEqXtM_bptlw3ks5s8__ogaJpZM4N1v2y
.

Ah, welcome to our Discord... We had some interactions yesterday :)

ah, just looked and it is there, so no worries. keep it up guys, this is
the project that got me into blockchain (better than cryptokitties.co !)
On Mon, Dec 4, 2017 at 10:11 AM, Thomas Zarebczan<EMAIL_ADDRESS>wrote:

Ah, welcome to our Discord... We had some interactions yesterday :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-app/issues/219#issuecomment-348990439,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMmFDic_LdOp7rVL32VF5bhN1JU-bJWPks5s9AuSgaJpZM4N1v2y
.


[C3] add information on using pnpm in c3.md

closes https://github.com/cloudflare/next-on-pages/issues/747
This can happen when using pnpm from corepack in a recent LTS version of node (v20.9.0)

Howdy @razin99, thanks for the submission.
Definitely understand why you want to add this, but we'd view this as more of an edge case (and sorta out of place in the context of a getting started guide).
If we hear of more folks running into this, totally open to re-evaluating this stance.


Add Node Name annotation

Why we need this PR
This annotation will be used by several components - it'll be set by NHC and read by any remediator which supports multiple templates of the same kind.
It makes sense to place it in a centralized location in order to avoid code duplication.
Changes made
annotation added
Which issue(s) this PR fixes
ECOPROJECT-1918 , but will be relevant for others in the future
Test plan

/lgtm


MRG, BUG: Fix scaling of sources

Closes #6615.
@jshanna100 can you confirm this fixes your problem?

It doesn't fix it on my end.

neither for me

Whoops, I tested it incorrectly. Should be fixed now!

LGTM

thx heaps @larsoner


Dose UCF101  dataset need to extract frames when I train the  network on it ?

Thanks for you to public your code ! If  the UCF101 dataset need to extract frames ,the "tools/vid2img_kinetics.py" didn't woark .It  just  build  a lot of empty  folders.  can you tell me the version of the  FFmpeg.  I think it the  the key  cuase.

Hi, you can check the TSN repo (https://github.com/yjxiong/temporal-segment-networks). It contains detailed guide to process UCF data.
Meanwhile, you can also change the vid2img_kinetics.py code to extract frames on UCF. I tried different versions of FFmpeg, and they both work fine. What is the error message that you got?

@Snowballing Hi, I have the same issue. Have you solved it? Hope to get your reply.

Hi, you can check the TSN repo (https://github.com/yjxiong/temporal-segment-networks). It contains detailed guide to process UCF data.
Meanwhile, you can also change the vid2img_kinetics.py code to extract frames on UCF. I tried different versions of FFmpeg, and they both work fine. What is the error message that you got?

Thanks for  your code and advice ! I tried the TSN repo（https://github.com/yjxiong/temporal-segment-networks#extract-frames-and-optical-flow-images）, but  just build a lot of empty folders.

I will close the issue now due to inactivity. Feel free to reopen if the problem persists.

OK，thanks for your answer!

hi @Snowballing  did u find/write the code for UCF101 to extract frames and labels?

I used the author's code finally

can u please guide me about the input parameters of this model? and some guides on how can i train this model on custom dataset. any help would be appreciated.
Actually i am new deep learning models and pytorch.
I am aiming to use this model in my capstone project.

@tonylins please give some guidance in training a custom dataset.. and about the input paramters of TSM.

Hi @Nauman007 , training on a new dataset is kind of straightforward. You need to first prepare the dataset following the guide and then perform training. What is the difficulty you encountered?

@tonylins  thanks for your reply..
I am having difficulty in preparing the dataset (UCF101)
when i try to extract the frames i get a bunch of empty directories. Frames donot get extracted.
Can u (if possible) guide me in a way seeing me as a beginner.

how do i prepare my dataset for TSM ?
and if i want to use your module on UCF-crime dataset would that be a good choice ? what are your suggestions?


feat(ingest/bigquery) - Emit cross-project usage from gcp logs

Adding option to emit all the lineages we get from Bigquery Audit logs and not just which belongs to that specific project.
Earlier, for each project we built a lineage map and we only emitted those ones which belonged to a project (we iterated over all the tables we found during metadata extraction and tried to find lineage for them).
Now it emits all the lineage we found when we built the lineage map. This means it will contain lineage edges for other projects as well.
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@treff7es Does this handle the scenario of deleted tables ? Let's say we found upstream lineage for some table in audit logs but this table does not exist anymore. Do we still emit lineage for this deleted table ?

We are assigning a timestamp to the lineage edges when we saw it. Hopefully this way those deleted edges will fade out with time.


[draft] pledge dashboard footprint categories

Description

Related Ticket

Resolves #

Checklist

[ ] Building the site with npm run build-site works without errors
[ ] Building the app with npm run build-app works without errors
[ ] I formatted JS and TS files with running npm run format-all

Closed to rebase appropriate commits on top of staging


Support for military time in MDTimePicker

Description of the Feature
Are there plans to implement support for military time (24 hour clock) in the circular time picker?
I've looked through the source code of kivy.vendor.circularTimePicker, and it seems like some work has already been done on this feature. There is some code commented out, but it seems to be a bit incomplete.
Any status on this feature? Almost ready to be released, or nowhere near completion?
I would like to offer my help on this functionality, but I am unsure if my python-skills are good enough to pull this off. In any case, any additional information would be helpful.
Below is the code, where I found the commented sections.
Code and Logs
kivymd.vendor.circularTimePicker @ line 503:
class CircularHourPicker(CircularNumberPicker):
    """:class:`CircularNumberPicker` implementation for hours.
    """

    # military = BooleanProperty(False)

    def __init__(self, **kw):
        super().__init__(**kw)
        self.min = 1
        self.max = 13
        # 25 if self.military else 13
        # self.inner_radius_hint = .8 if self.military else .6
        self.multiples_of = 1
        self.number_format_string = "{}"
        self.direction = "cw"
        self.bind(shown_items=self._update_start_angle)
        # self.bind(military=lambda v: setattr(self, "max", 25 if v else 13))
        # self.bind(military=lambda v: setattr(
        #     self, "inner_radius_hint", .8 if self.military else .6))
        # Clock.schedule_once(self._genitems)
        Clock.schedule_once(self._update_start_angle)
        Clock.schedule_once(self.on_selected)

    def _update_start_angle(self, *a):
        self.start_angle = (360.0 / self.shown_items / 2) - 90

Versions

OS: Ubuntu 18
Python: 3.7+
Kivy: 1.11.1
KivyMD: 0.102.0

I think that 24-hour time picker is very useful feature. We should implement it as two rows of numbers how it did Google.

We always welcome if you want to improve KivyMD. You need to read CONTRIBUTING.md before pull request.

If someone is already doing this, let me know, then I will solve other problems.

@HeaTTheatR
I tried looking into this, but I'm afraid it's a bit outside the range of my Python skills.
I will try to look into other ways of contributing to this project.
Any work that needs to be done, which would fit my intermediate skill level?
If not, I will start working on expanding the documentation, one my schedule clears up next week.

@EsbenLorenzen I can send you draft of this.

@HeaTTheatR
Looks good - I won’t have time to look at at it in about a week, but I’ll be happy to take a look and see what I can come up with.

https://github.com/kivymd/KivyMD/pull/712

Dear All,
could you please illustrate on the basic example below how to turn on this new feature? I just couldn't make it work. Whatever I do, I get the AM/PM layout.
Many thanks for your help in advance!
from kivy.lang import Builder

from kivymd.app import MDApp
from kivymd.uix.pickers import MDTimePicker

KV = '''
MDFloatLayout:

    MDRaisedButton:
        text: "Open time picker"
        pos_hint: {'center_x': .5, 'center_y': .5}
        on_release: app.show_time_picker()
'''

class Test(MDApp):
    def build(self):
        return Builder.load_string(KV)

    def show_time_picker(self):
        '''Open time picker dialog.'''

        time_dialog = MDTimePicker()
        time_dialog.open()

Test().run()

Thanks for the answer @HeaTTheatR. Although I don't quite get it. According to Wikipedia: "The 12-hour time convention is common in several English-speaking nations and former British colonies, as well as a few other countries. ... In most countries, however, the 24-hour clock is the standard system used, especially in writing." https://en.wikipedia.org/wiki/12-hour_clock This means that there are a few billions of people (apparently the majority of humanity) who's preference is deemed unnecessary to consider here, even as an optional feature?.. To be honest, I find this pretty disappointing.

@Babber

@HeaTTheatR
I know that the military time support is apparently not part of this rather exclusive specification (I assume, this is what you would like to say with this image), but adding a militaryTimePicker.py file to the repo doesn't have to ruin this design at all. Or just another class in the same file, or another method to the same class, which is called with a mode=military option, I don't really mind. None of the time pickers have to have a button to switch between the two. Keeping the above design as it is and also offering the military time picker are not mutually exclusive. I think it's rather obvious that there is a demand for the military option (see Wikipedia), and I don't see the arguments against it. Apparently it has even been implemented once already, although I am not sure at what stage it failed to get released. Is there now nobody to code it again? I would get that. A bounty is missing? How much? I am seriously considering sponsoring this specific feature. As I see, there was a $20 bounty on adding support for military time in MDTimePicker. I am willing to give more than that if a working implementation of this gets released in the master branch. Details can be discussed if someone is interested.

@Babber I don't think we will include this functionality in the library again. At the developer level, you can easily transform the time into any format depending on the AM/PM values. But in any case, no one bothers you to assign a reward for adding this functionality.

@HeaTTheatR
I see. Yeah, thanks, I know how to convert between the two systems.
Finally, just to be clear: even if I implement it myself, you won't add it to the library? If I have some free time, and I may actually do it anyway and host it on my own, but of course, it would give me more motivation if I could add it as a contribution to the KivyMD library.

@Babber
KivyMD library packages of the kivymd.uix.ickers type currently have functionality and design consistent with Google Material Design. You must understand how difficult it is to add the functionality that you describe here to the functionality that currently exists. Moreover, we consciously got rid of the functionality that you describe.

@HeaTTheatR
Alright. I get it.
Just for the record, even on Material.io, they also show the 24h time picker (although a less sophisticated version of it) if you click on "Implementation":

While elsewhere, in js, supposedly also following Material Design:

...just like on my own Android, like I guess on most of the mobile devices (although I don't know this for a fact, just judging by the overall popularity of the 24h system in the world).
But anyway, I don't want to pester you any more with this. You're the core developer here and I respect your decisions of course. KivyMD is still a great project, I do like it and I do appreciate your work! Thank you for this and many thanks for the discussion too.

For anyone who's interested in the same TimePicker extended with the 24-hour clock:
https://github.com/Babber/KivyMD-TimePicker-with-24h-support


The sx property in the muiTableHeadCellsProps in the column definitions overwrites the same property in the table instance

material-react-table version
v2.13.0
react & react-dom versions
v17.0.2
Describe the bug and the steps to reproduce it
When customizing a table through instances in the muiTableHeadCellsProps sx property and subsequently adding sx for certain cells already in the column definition, the styles are not supplemented, but overwritten.
Minimal, Reproducible Example - (Optional, but Recommended)
codesandbox
In the example, the first column should have red text.
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
No, because I do not have time to dig into it
Terms

[X] I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

This is intended. In fact, I'll probably be removing the all muiProp table options that can be defined on individual columns or the default column to remove this ambiguity a bit.


[WebGPU] Use staging_buffer->bind_group_layout during pipeline creation.

This fixes an error I was seeing when trying to initialize a posenet program:
The entry-point uses bindings in group 3 but [PipelineLayout] doesn't have a BindGroupLayout for this index
 - While calling [Device "IREE WebGPU device"].CreateComputePipeline([ComputePipelineDescriptor]).

The next error message is this:
The buffer type in the shader (BufferBindingType::Storage) is not compatible with the type in the layout (BufferBindingType::Uniform).
 - While validating that the entry-point's declaration for @group(3) @binding(0) matches [BindGroupLayout]
 - While validating the entry-point's compatibility for group 3 with [BindGroupLayout]
 - While calling [Device "IREE WebGPU device"].CreateComputePipeline([ComputePipelineDescriptor]).

That should be fixed with https://github.com/iree-org/iree/issues/11183 and a change to WGSLReplacePushConstants.cpp (descriptor type from StorageBuffer to UniformBuffer).

nice - I hadn't seen how to put that together when I was originally hacking it out (hence the total brokenness - sorry :) - this is slick!


cli: add WG Commander

I have recently created an open-source tool for a simple WireGuard configuration management.
I would be happy if it is possible to mention my project on the awesome-wireguard list. I think the project is compliant with most of the list requirements. Thank you.

Your project is welcome here. Thank you for sharing your work.

Thank you @cedrickchee


Search does not return existing conda-forge packages and pixi add complains about "no candidates found"

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
pixi search neuron*

pixi.toml is
[project]
authors = ["XXXXXXXXXXXXXXXXX"]
channels = ["conda-forge"]
description = "Add a short description here"
name = "testme2"
platforms = ["osx-arm64"]
version = "0.1.0"

[tasks]

[dependencies]
python = ">=3.12.5,<4"
numpy = ">=2.1.1,<3"
matplotlib = ">=3.9.2,<4"
jupyterlab = ">=4.2.5,<5"

Issue description
Both "neuron" and "neunorm" are valid conda-forge packages, see here and here.
When the search command is invoked, pixi returns
Using channels: conda-forge
Package                                  Version             Channel
neunorm                                  1.4.3               conda-forge/noarch

Similarly, pixi add neuron returns "missing candidate".
Expected behavior
pixi should return another hit, showing two results and should allow to install neuron.
Where am I wrong? Thank you for your patience with me.

I confirm it must be a bug. I just found here that the suggested pixi command to install that specific package is:
pixi add neuron

which unfortunately does not work and returns
➙ pixi add neuron
  × failed to solve the conda requirements of 'default' 'osx-arm64'
  ╰─▶ Cannot solve the request because of: No candidates were found for neuron *.

The package is only available for osx-64 try using that in your platforms.

The package is only available for osx-64 try using that in your platforms.

Thank you.
If I manually add to pixi.toml
[pypi-dependencies]
neuron = ">=8.0.0,<9"

the package gets installed and works perfectly.

I added neuron and neunorm to the osx-arm64 migration, if everything goes right these packages will then also be available for osx-arm64 from conda-forge.

@baszalmstra seems to be looking good on that feedstock!

I am in debt with you, @baszalmstra and @tdejager  !!!

Haha thank you @mgiugliano, is it okay to close this?


fix: empty callback in promise .then

Description of the Changes
Please add a detailed description of the change, whether it's an enhancement or a bugfix.
If the PR is related to an open issue please link to it.
Checklist

[ ] Changes have been done against master branch, and PR does not conflict
[ ] New unit / functional tests have been added (whenever applicable)
[ ] Test are passing in local environment
[ ] Docs have been updated
[ ] PR title is follow the Conventional Commits convention: <type>[optional scope]: <description>, e.g: fix: prevent racing of requests

This change is

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Open multiple packages at once

Feature request
It would be nice to be able to open multiple packages at once, each in its own tab. I often need to compare the content of several packages, and having multiple instances of NPE isn't very convenient.

Can you just open multiple instances of NPE? I don't think it's likely we'll be adding tabs to the existing UI.

That's what I do. It's less comfortable than tabs, but I can live with it.


Expose the resolved platform

The value of the resolved platform may be of use to other tasks. Please consider exposing it using the extra properties container, for example
detectPlatform(project);
project.ext.platform = platform

Indeed. I suggest make this a read-only property on the javafx extension class.

You may as well consider other values such as the specific Linux distribution. This is important for the kind of package to be generated (deb/rpm).

Agreed. Mentioning that both osdetector and modules plugins are already included and applied should lead people into the right direction.

Yes, I agree with that. That would then be part of #9.


Possible improvements to predicates

Some new experimental predicates are now available, but the concept is still a bit unpolished.
This issue tracks a few potential improvements.

We decided not to add more predicates, so closing this one.


Comment out combinePrimitives and add a TODO for now

Coverage decreased (-0.007%) to 93.862% when pulling f9661cf3fd2cc67b33610980d8efc365405f5a26 on remove-combine-primitives into 13f29f37d63d5081eb232de1b03fa81f83888fe3 on master.

Ok this is fine for now.


No search results, wordpress in subdirectory

Will this plugin work if wordpress is in a subdirectory?
The query generated by the plugin always returns no results for a search. The SQL statement generated by the query:
SELECT SQL_CALC_FOUND_ROWS wp_posts.* FROM wp_posts WHERE 1=1 AND wp_posts.ID IN (0) AND wp_posts.post_type IN (\'post\', \'page\', \'attachment\', \'events\', \'testimonies\', \'leadership\') AND (wp_posts.post_status = \'publish\' OR wp_posts.post_author = 1 AND wp_posts.post_status = \'private\') ORDER BY wp_posts.post_type ASC LIMIT 0, 500'
It always has wp_posts.ID IN (0) which would seem to always be false? Maybe this is how the plugin overrides wordpress default search?  All the posts are in elasticsearch and I am able to run queries on the data from the command line. I am new to elasticsearch and this plugin, maybe I am missing something simple?

From what i understand from the plugin, this plugin will use elasticsearch to obtain a list of ID's it should show. It then hands it over to wordpress to get the actual posts, using the query you show. So that it tries to match to 0, means the original elasticsearch query failed.
I run the plugin on a site with wordpress in a subdir as well and that works ok. So i doubt it has to do with that. Can you check there are actually records in your elasticsearch?

There are records in eleasticsearch.  I was able to get the plugin elasticpress working, so I'm using that instead now.  I liked the back end UI for this plugin but couldn't get it working :(.


fix(@angular-devkit/build-angular): added warning for ES2017

Fixes https://github.com/angular/angular-cli/issues/13477

Kindly squash your commits into a single one.
Thanks.

Thanks!

@filipesilva PTAL

LGTM, thanks for taking this on @hrocha16!

Hi, is there a way to hide the warning? I dont even use zone.js (its an Angular Element) but I get this warning anyway.
Thanks


When will the code be released?

This is an excellent work, and I look forward to its source code. So when will the code be released? 😄

Thanks for  your interest. The source code will be released while our work is formally published.


fix(batch-processing): post fix

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Broker: scaffolding

ASP.NET Core project, configured for standalone (IIS-less) operation with NTLM auth and websockets.

https://github.com/Microsoft/RTVS/pull/2083


bug: crashed when select from internal tables

Describe the bug
thread 'risingwave-main' panicked at 'output_indices must be a subset of value_indices', /Users/eric/Workspace/risingwave-dev/src/storage/src/table/batch_table/storage_table.rs:180:9
stack backtrace:
   0: rust_begin_unwind
             at /Users/eric/.rustup/toolchains/nightly-2022-12-12-aarch64-apple-darwin/lib/rustlib/src/rust/library/std/src/panicking.rs:575:5
   1: core::panicking::panic_fmt
             at /Users/eric/.rustup/toolchains/nightly-2022-12-12-aarch64-apple-darwin/lib/rustlib/src/rust/library/core/src/panicking.rs:64:14
   2: risingwave_storage::table::batch_table::storage_table::StorageTable<S>::new_inner
             at ./src/storage/src/table/batch_table/storage_table.rs:180:9
   3: risingwave_storage::table::batch_table::storage_table::StorageTable<S>::new_partial
             at ./src/storage/src/table/batch_table/storage_table.rs:122:9
   4: <risingwave_batch::executor::row_seq_scan::RowSeqScanExecutorBuilder as risingwave_batch::executor::BoxedExecutorBuilder>::new_boxed_executor::{{closure}}
             at ./src/batch/src/executor/row_seq_scan.rs:248:25
   5: <core::pin::Pin<P> as core::future::future::Future>::poll
             at /Users/eric/.rustup/toolchains/nightly-2022-12-12-aarch64-apple-darwin/lib/rustlib/src/rust/library/core/src/future/future.rs:124:9
   6: risingwave_batch::executor::ExecutorBuilder<C>::try_build::{{closure}}
             at ./src/batch/src/executor/mod.rs:195:29
   7: <core::pin::Pin<P> as core::future::future::Future>::poll
             at /Users/eric/.rustup/toolchains/nightly-2022-12-12-aarch64-apple-darwin/lib/rustlib/src/rust/library/core/src/future/future.rs:124:9
   8: risingwave_batch::executor::ExecutorBuilder<C>::build::{{closure}}
             at ./src/batch/src/executor/mod.rs:179:25
   9: risingwave_batch::task::task_execution::BatchTaskExecution<C>::async_execute::{{closure}}
             at ./src/batch/src/task/task_execution.rs:316:9
  10: <risingwave_batch::rpc::service::task_service::BatchServiceImpl as risingwave_pb::task_service::task_service_server::TaskService>::execute::{{closure}}
             at ./src/batch/src/rpc/service/task_service.rs:124:53

To Reproduce
Create tables and insert some data:
create table t2 (k int, v varchar, primary key(k));
create table t1 (k int, v varchar, primary key(k));
create materialized view mv1 as select t1.k as k, t1.v as v1, t2.v as v2 from t1, t2 where t1.k=t2.k;
insert into t1 values (1,2), (3,4);
insert into t2 values (1,200), (3,400);

Then,
dev=> select * from mv1;
 k | v1 | v2
---+----+-----
 3 | 4  | 400
 1 | 2  | 200
(2 rows)

dev=> select * from __internal_mv1_5_hashjoindegreeleft_1005;
ERROR:  QueryError: internal error: transport error

Note that the internal table name __internal_mv1_5_hashjoindegreeleft_1005 can be inspected via command ./risedev ctl table list
Expected behavior
No response
Additional context
No response

I am also considering to expose internal tables to users/developers in SQL besides the little-known ./risedev ctl table list. Let me open another issue for that.

Oops, @Enter-tainer has leaved. @chenzl25 can you help to take a look?

Oops, @Enter-tainer has leaved. @chenzl25 can you help to take a look?

OK, I will take a look.

I think that is because we do not implement batch scan on the table after introducing the value_indices in the state table. c.c. @wcy-fdu

BTW, should we add some e2e tests for querying the internal tables, if we can decide the table name by querying the system tables.


go119

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 42.799%

Files with Coverage Reduction
New Missed Lines
%

pkg/session/context.go
1
52.94%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1361

Relevant Lines:
3180

💛  - Coveralls


CredentialsParameterDefinition is unsupported, PT_CHECKBOX is unsupported?

any idea?
any plan to support?
thx

I have to look why this happens
normally these are supported. Which plugin version do you use?
and which jenkins server version?
cany you also send pipeline configuration with parameters?


Move EntitySignature from output to signature

Seems more fitting to place it here.

Something is up with codecov. This doesn't seem like the random error we are used to:
[2023-07-05T13:25:45.339Z] ['error'] There was an error running the uploader: Error uploading to [https://codecov.io:](https://codecov.io/) Error: There was an error fetching the storage URL during POST: 404 - {'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}

That's unrelated to these changes though. Merging.


feat: create form input component

Create a new FormInput component.
In the following example:
<Form>
  <FormField
    control={...}
    name="..."
    render={() => (
      <FormItem>
        <FormLabel />
        <FormControl>
          <Input {...form.register('title')} />
        </FormControl>
        <FormDescription />
        <FormMessage />
      </FormItem>
    )}
  />
</Form>

We would only be able to see the error for the current <FormItem /> (in this case for the title input)  appear in the <FormMessage /> component that sits right under the input.
In many forms, including the ones in Tailwind UI:

We often see the border and ring of the current input change color to red/destructive in addition to the error form message appearing below.
This change creates that error styling when an error occurs. The above example can now look like this:
<Form>
  <FormField
    control={...}
    name="..."
    render={() => (
      <FormItem>
        <FormLabel />
        <FormControl>
          <FormInput {...form.register('title')} />
        </FormControl>
        <FormDescription />
        <FormMessage />
      </FormItem>
    )}
  />
</Form>

I just found this PR - I opened a similar one. I don't think creating a second very-similar component would be the most reasonable approach for an UI Library.
In this PR I added only the border-destructive style, but did it to the FormControl component, which would allows us to still use the regular Input component and get a similar effect that what you are implementing here.


Add a check to prevent null values from breaking the advanced file search

In certain circumstances null values can enter a saved file search this has caused some issues when trying to run subsequent searches.
Once resolved I've not been able to replicate the issue, so believe it could be a legacy issue that's since been fixed?
But without this if a null value exists in the Users config then then the site search breaks with the exception listed in the bug tracker link below.
https://www.concrete5.org/developers/bugs/8-1-0/running-an-advanced-search-returns-an-exception/

Steps taken to create the issue.
From the File manager
Select Advanced
Press Search
Once the error appears, subsequent freshes display the Exception until the cookies are cleared
recordit link http://recordit.co/1ES6Fne1B0

I can't reproduce this personally, but it doesn't look like there's a lot of harm in including this code.

Once resolved I was not able to reproduce it either, but I assume something before #5666 allowed me to save a null value into the users config which if present caused this issue.


Extend unixfs builders to optionally produce file references instead of blobs - hackish version

We don't know yet where this will happen (on the cli or on the store side), but to turn the store into a store that optionally just stores metadata, we do need to extend the builders.

This is going to be fun. Not much you don't have to touch in unixfs...

So here is the hackish version: https://github.com/n0-computer/iroh/tree/block-references


XMLSchemaKeyError on valid xml files

With the current xmlschema-1.0.3 I ran into this issue on a xml file (attached below) which is successfully validated at several other validation services:
import xmlschema
xmlschema.validate('fuelPriceExample_v01-01-00.xml', 'PetrolStationPublication_v01-01-00.xsd')
XMLSchemaKeyError: "missing a XsdSimpleType or XsdComplexType object for 'FuelPricePublication'!"
The same error persists using the other functions like is_valid() or to_dict().
fuelPriceExample_v01-01-00.zip

It's an error related to the default namespace mapping for the value of the xsi:type attribute. The error is the same because it's generated by the common inner method iter_decode.
Also I forgot to insert a protection for lookup_type call, then a KeyError is raised instead of a validaton error. Probably I'll make an hotfix release for this and other lookup related issues ASAP.
Thank you for reporting it.

Thank you for your help and for maintaining this important library!
I am looking forward to use it after the hotfix release is published.

Hi, the hotfix v1.0.5 is released. Try it with your data and report for further errors or close this issue.
Thanks


chore: multi package updates

It also contains a fix found by eslint 😅

The build size seems increased; weird!

The build size seems increased; weird!

Not cool to upgrade packages. The good news is that the test pass :)

Nice chore work! Super weird that the actual size of the lib went up 11kb gz:

https://bundlesize-store.now.sh/build?info={"files"%3A[{"maxSize"%3A102400%2C"path"%3A".%2Fdist%2Finstantsearch.min.js"%2C"size"%3A109294%2C"compression"%3A"gzip"%2C"master"%3A97781}]%2C"repo"%3A"algolia%2Finstantsearch.js"%2C"branch"%3A"misc%2Fmulti-package-updates"%2C"commit_message"%3A"Merge 594e300dcfca7a4046f9c300249ee91cb686c966 into 79ebd66bda1b7ccc4f2d8a47ef67f2bb8c5b39c5"%2C"sha"%3A"594e300dcfca7a4046f9c300249ee91cb686c966"}
Maybe it's just because bundlesize itself was updated. Because I see no other lib that could be responsible for this in the updates.

Maybe it's just because bundlesize itself was updated. Because I see no other lib that could be responsible for this in the updates.

I'm reading the same size from our own compile script. Digging into the dependencies I have updated: so far keeping the old lodash would have been worse.

Ok let's move on. Maybe we could try to think about some wins that we could implement to reduce the size later.


Seeking back doesn't update currentTime

Current behavior
When using seek to go back in time, currentTime reported through onProgress doesn't update and stays at last reported value until caught up with. Seeking forward seems to work fine.
Platform
Which player are you experiencing the problem on:

Android ExoPlayer

Related to #1564


add new protocol to traccar server

Hi tananaev.
i need to add new protocol to traccar server to make it identify my new device. Here what i get from my device:
-1515-$GPRMC,120017.000,A,1725.6760,N,03355.9001,E,22.67,36.96,160215,,,A*6F,%{000028015180",1DT
where is the 1515 is the id of our new device id we make it by the device configuration software given by manufacturer.
we made all the process required to add new protocol. please give an advice.

It looks very similar to T55 protocol, so you probably just need to slightly modify T55 decoder to handle your format.


Consolidate error messages

Resolves #149

Codecov Report

Merging #206 into master will increase coverage by 0.03%.
The diff coverage is 93.02%.

@@             Coverage Diff              @@
##             master     #206      +/-   ##
============================================
+ Coverage     82.67%   82.70%   +0.03%
  Complexity     1065     1065
============================================
  Files           148      148
  Lines          3168     3174       +6
  Branches        381      381
============================================
+ Hits           2619     2625       +6
  Misses          455      455
  Partials         94       94

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/tutorspet/commons/core/Messages.java
0.00% <ø> (ø)
0.00 <0.00> (ø)

...ain/java/tutorspet/logic/commands/ExitCommand.java
100.00% <ø> (ø)
2.00 <0.00> (ø)

...ain/java/tutorspet/logic/commands/RedoCommand.java
100.00% <ø> (ø)
3.00 <0.00> (ø)

...in/java/tutorspet/logic/commands/ResetCommand.java
100.00% <ø> (ø)
2.00 <0.00> (ø)

...ain/java/tutorspet/logic/commands/UndoCommand.java
100.00% <ø> (ø)
3.00 <0.00> (ø)

.../commands/moduleclass/ClearModuleClassCommand.java
100.00% <ø> (ø)
2.00 <0.00> (ø)

...et/logic/commands/student/ClearStudentCommand.java
100.00% <ø> (ø)
2.00 <0.00> (ø)

...c/main/java/tutorspet/logic/parser/ParserUtil.java
93.58% <ø> (ø)
22.00 <0.00> (ø)

...parser/attendance/EditAttendanceCommandParser.java
88.00% <ø> (ø)
6.00 <0.00> (ø)

...t/logic/parser/lesson/EditLessonCommandParser.java
92.30% <0.00%> (ø)
8.00 <0.00> (ø)

... and 31 more

Continue to review full report at Codecov.

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


Question related to importing in to webpack projects

Hello,
I was hoping that there might be some guidance or example of using this library in the context of a webpack project.
Looking for a way to import it like this.
import {Drawing} from "dxf-writer";

Hi,
Why not using it like:
import Drawing from "dxf-writer";

It's working fine in<EMAIL_ADDRESS>At least for me.
I have a package @tarikjabiri/dxf. It supports ES Modules and CommonJS out of the box written in Typescript. See docs.
import { DxfWriter, point3d } from "@tarikjabiri/dxf";

const dxf = new DxfWriter();
dxf.addLine(point3d(0, 0, 0), point3d(100, 100, 0));
// To get the dxf string just call the stringify() method
const dxfString = dxf.stringify();

Regards.


Update Dockerfile.ci_adreno

The image name has a typo and there is no image tagged with latest on the docker hub. This should be fixed and is likely an issue with all the dockerfiles as well.

@tvm-bot rerun

@tvm-bot rerun

Since then I discovered there were other things wrong with the docker build, and I just gave up and built directly from source. The docker builds could perhaps be taken down if they are difficult to maintain


PsGithub.java:54-56: There is currently no unit...

Puzzle 229-401562da in src/main/java/org/takes/facets/auth/social/PsGithub.java:54-56 has to be resolved: There is currently no unit test in PsGithubTest that checks that the request parameters are passed to the request body, instead of the URI. Let's add this test.... The puzzle was created by cyberone on 1-May-2015.
If you have any technical questions, don't ask me, submit new tickets instead

@dmzaytsev the task is yours,please go ahead

@davvd I will resolve the puzzle in the PR #228

@yegor256 since there is no milestone yet I set it to "1.0"

@davvd waiting for #253

@davvd the #PR 228 has been merged. Please close the task

@davvd waiting for #253

@yegor256 right, let's wait for #253

@davvd you can see pull request #228 that is fixing this issue, if that's all here please close.

@davvd please close the task

@yegor256 Closing..

@elenavolokhova please, let us know what do you think about this ticket, according to our QA rules

@davvd Quality is good.

@davvd Quality is good.

@elenavolokhova many thanks

@dmzaytsev just added 10 mins to @elenavolokhova (for QA), payment ID is 57168002. thank you, added 30 mins to your acc, payment num is 57168022, 169 hours and 42 mins spent in total to complete. +30 to your rating, your total score is +1460


Refactor API: use interfaces instead of filenames

How about to use this api
func TrimCommand(input io.ReadSeeker, output io.WriteSeeker, pageSelection []string, config *pdf.Configuration) *Command

instead of current
func TrimCommand(pdfFileNameIn, pdfFileNameOut string, pageSelection []string, config *pdf.Configuration) *Command

?
With reader/writer possible to use in-memory storage instead of files. Also it's faster than read from disk, and write to disk.

Hi there,
Right now there are two ways to call into pdfcpu:

api.Process(cmd *api.Command) which is also used by the CLI
io.ReadSeeker/io.Writer based like in this example for ReadContext

Also check out these functions in api.process_test.go to get started:

TestReadSeekerAndWriter (which is really optimize using ReadSeeker)
TestMergeUsingReadSeekerCloser

I am aware this is not clean but it works.
Refactoring the api and providing ReadSeeker across the board makes sense.

This is fixed with v0.2


Doubly-linked list and/or sentinel node implementation guides

Crawl the web to find high-quality open-source samples for doubly-linked lists and/or sentinel nodes. Specifically, the implementations should contain code that students could adapt to implement the LinkedDeque class.

Enhanced slide deck to show steps in Winter 2023.