Autobump fails on release workflow

Description
https://github.com/whylabs/whylogs/runs/7526093630?check_suite_focus=true#step:8:29

I think bump2version is not correctly setup in our dependencies. I can repro this error locally running the line from our workflow-ci:
 poetry run bump2version patch --verbose --commit --no-tag --new-version 1.0.9

  FileNotFoundError

  [Errno 2] No such file or directory: b'/sbin\nexport PYSPARK_PYTHON=/usr/bin/python3/bump2version'

  at /usr/lib/python3.8/os.py:601 in _execvpe
       597│         path_list = map(fsencode, path_list)
       598│     for dir in path_list:
       599│         fullname = path.join(dir, file)
       600│         try:
    →  601│             exec_func(fullname, *argrest)
       602│         except (FileNotFoundError, NotADirectoryError) as e:
       603│             last_exc = e
       604│         except OSError as e:
       605│             last_exc = e

and then it goes away after manually running:
 pip install --upgrade bump2version


How to proceed for Version Upgrades or adding nodes

Hello
What is the process for upgrading the kubernetes version? Do I just have to change the version in group_vars and then run the playbook again or is this not supported with the current playbook.
Can I extend an installed cluster with more nodes. Do I just have to add more nodes to the inventory and then run the playbook again?
Thanks for your help.

I just replaced the version number in group_vars and ran the playbook again to upgrade and it works perfectly.

In my case, ansible also returned a message that is shown below.

The error you're facing is already described in #188.

As for the upgrade: I think updating the variable and re-run the playbook is fine for now (see also https://github.com/k3s-io/k3s-ansible/issues/94#issuecomment-715667638). Please keep in mind, that any upgrade may break you system. Also check keep in mind that any bugfixes done in scripts should be mirrored on your system, too. For a safe upgrade path I suggest:

Drain your node(s)
Upgrade your nodes using k3s-ansible, restart them afterwards
Drain your master(s) and upgrade them too, restart them afterwards
make sure everything is up and running

How about addint new nodes? just editing the host.ini file and adding new masters, or nodes works?

I just replaced the version number in group_vars and ran the playbook again to upgrade and it works perfectly.
I had to restart nodes to receive the effect."Destination /usr/local/bin/k3s is not writable", "owner": "root", "secontext": "system_u:object_r:bin_t:s0", "size": 53239808,
In my case, ansible also returned a message that is shown below.

I did the same thing - changed K3s version in group_vars/all.yml - but when I re-run the Playbook I get this error on all my nodes:
"Destination /usr/local/bin/k3s is not writable", "owner": "root", "secontext": "system_u:object_r:bin_t:s0", "size": 53239808,

I did this, and jumped right to the latest 1.25 from 1.22.  And that resulted in a lot of weirdness that I'm trying to triage over in https://github.com/k3s-io/k3s/issues/6314.  Don't do that.

I'd also like to know how to upgrade a k3s installed with this Ansible code.
Should be a section in the README describing how to do this imo

Now Supported via playbook.


Changed base tag to voidTag

According to mdn,the base tag is an empty one.
See https://developer.mozilla.org/nl/docs/Web/HTML/Element/base

Great spot, thanks as always!


[docs] DataGrid documentation for MUI v4 is no longer available (404)

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
https://v4.mui.com/components/data-grid/
Even from the menu, DataGrid doc returns 404
Current behavior 😯
No response
Expected behavior 🤔
No response
Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

My bad, I broke it. A fix is on its way.

Fixed with https://github.com/mui/mui-x/commit/5895a953970dd16eb6cb26299209308c4d2e5e2a, it's now live and working https://v4.mui.com/components/data-grid/.


I have a question about View Formatting in SP 2019

I dont see any option to format views in sharepoint 2019 (on-premise)
Is there a plan to bring these to onpremise? Is there any place I can track? userVoice?
https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/building-immersive-user-experiences-with-sharepoint-view/bc-p/1844276#M5466

Unfortunately, only a subset of Column Formatting is supported in SharePoint 2019. There are no plans to bring view formatting to SharePoint 2019. I cannot speak to future on-premises versions though.


Not seeing publish task for new theme.

If I do rake -T | grep theme on a fresh clone of http://github.com/bullet-train-co/bullet_train, I only see:
rake bullet_train:themes:light:eject[destination]                # Fork the "Light" theme into your local repository

If I do rake bullet_train:themes:light:eject\[special\] and then rake -T | grep theme, I still only see:
rake bullet_train:themes:light:eject[destination]                # Fork the "Light" theme into your local repository

So it seems like something isn't quite right.

Hmm... it's weird, because if I bin/develop on the light theme, then the task appears. Interesting. Might be a release issue? I'll look at this.


Fixes the issue of switching to a non-existing component using set command

Signed-off-by: mik-dass<EMAIL_ADDRESS>Issue : #127

@mik-dass , run gofmt

@surajnarwade Done


cmake: Exclude some targets

What problem does this PR solve?
Issue Number: ref #6201
Problem Summary:
What is changed and how it works?

Exclude most targets from All.
Number of builds when building the All target (ninja):

Before this PR: 3928
This PR: 3366
Baseline (ninja tiflash): 3360

No need to execute post_install scripts for debug profiles. We only care about the binary size in release profile.

Extracted from https://github.com/pingcap/tiflash/pull/6112
Check List
Tests

[ ] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/merge


How to use

Once this is installed, how do I configure and use it? Where should I put my maps?

Hey @cdecinkoKnight
Thanks for the feedback. I haven't added samples yet but will do so.
Let's say you have a console-application. Within that application you have the profiles as well.
One profile would be something like this
public class CustomerProfile : Profile
{
   public CustomerProfile()
   {
      CreateMap<Customer, CustomerDto>();
   }
}

Your Program.cs would kind of look like this
   public static void Main(string[] args)
   {
      var builder = new ContainerBuilder();
      builder.AddAutoMapper(typeof(Program).Assembly); // here you need to pass in one or more assemblies that container your profiles
     // more registrations
   }

I will add some samples soon. In the meanwhile I hope this helps. You can also take a look at the tests that can be found here.

Thanks.  Looking for an example using it with .NET 4.5+ and Global.asax.

Thanks. Looking for an example using it with .NET 4.5+ and Global.asax.

That would be the same given that you are already using Autofac as your dependency provider in your ASP.NET applciation. Sadly, this package does only support .netstandard2.0 therefor you will have to update your project to net461

I added some samples in this repository. I hope it gives you an idea about how it works in general. It should be the same for classic ASP.NET given the fact, that you have already registered Autofac as your service provider.


Convert some sample OGC documents

Testbed: https://github.com/opengeospatial/D012-MapML_Engineering_Report
Standard: https://github.com/opengeospatial/WFS_FES

OGC TC Policies and procedures (all done)

Repo: https://github.com/riboseinc/ogc-tcpnp
Rendered: https://riboseinc.github.io/ogc-tcpnp/

Maybe we just need one more repo/doc.

Candidate (already in AsciiDoc): https://github.com/ogcscotts/eo-wcs
Make a new repo for it please.

Is this still required? And if so, could you get someone else to do it?

@ronaldtse: So I'll do https://github.com/opengeospatial/WFS_FES ?

Done as https://github.com/riboseinc/ogc-wfs


Fix toctree issues with documentation

Summary
In #1631 the docs were updated to use a new version of the qiskit_sphinx_theme and enable some new features it included. However, in doing this a few issues were introduced to the documentation. The biggest of which was the removal of the aer, circuit library, and the ibmq provider from the table of contents tree. Looking at the review comments on #1631 this was a consious choice to rely on hard coded navigation in the theme (i.e. the top bar). However, doing this breaks navigation in the sphinx documentation because it relies on the toctree to build the pathing for navigation from leaf pages in the toctree. For example, if you want to find the QuantumVolume class documentation currently you must search to find it because you can't get to it from any other page. Then when you find you're not able to get back to the parent page for the circuit library because it's an orphaned page outside the toctree. While aer and the ibmq provider get around this to a certain degree because you can get the per project index via the top bar (which I personally find non-obvious) navigation within that namespace is broken because they're not reachable from the root index. This commit adds back the missing references back to the root table of contents so navigation works again.
The other changes are relatively minor as it just fixes up the FAQ page which I mostly didn't realize existed prior to looking at the docs just now. Primarily it cleans up some irrelevant questions and also uses proper sphinx references to point to the install guide when needed.
Details and comments

I feel strongly that we should not implement the sidebar changes in this PR. The issues you are describing with the navigation seem pretty minor (ultimately, the user can still always get to where they need to go) whereas reverting the sidebar to the old style would be a major UI change for the user and would be a big step back in what we're trying to do with standardising docs and making things more terra focused. I could maybe see the argument for including the circuit library back in the sidebar as it is terra specific, but I don't think the Aer, provider and contributing links should go back.
Alternatively, I would suggest we make a small change to the sphinx theme (that we could get released before the next terra release) that would mean we don't display toctrees with the :hidden: directive - what do you think?
So in this case the index.rst would look something like this:
.. toctree::
  :maxdepth: 1

  getting_started
  intro_tutorial1
  tutorials
  API Reference <apidoc/terra>
  release_notes
  configuration
  GitHub <https://github.com/Qiskit/qiskit-terra>
  faq

.. toctree::
  :maxdepth: 1
  :hidden:

 apidoc/circuit_library
 apidoc/aer
 apidoc/ibmq-provider
 contributing_to_qiskit
 deprecation_policy
 maintainers_guide

This way we keep the new sidebar as is but we still have those other files as part of the toctree just not visible in the sidebar (if i understand the hidden directive properly)
If theres a reason this doesn't work then I still prefer @HuangJunye's  suggestion earlier (about moving the other api references under the api reference page)

It's not a minor issue, navigation is fundamentally broken especially if you are building locally (the top bar doesn't work for builds outside of qiskit.org as the full url is hard coded into the links). There is no path for discovery of any content in the circuit library, aer, or ibmq outside the search bar. Then when you find the pages you're interested in there is no navigation between any of those pages as the hierarchy is broken without the toctree entries. As an aside, I also feel the new top bar is a big regression in the UX because none of the navigation is visible by default anymore. Before I could see the navigation content I cared about on every page of the documentation and now it's hidden behind a menu I have to know to click in the upper left. But, if the toctree was fixed and navigation were actually working I can just ignore this.
That all being said this has been broken for over a month now and it's quite frustrating to actually use the hosted documentation to get work done (so much so that I've stopped using the qiskit,org hosted documentation and am using a local build with this PR applied). So instead of bikeshedding on what the sidebar should look like where everyone clearly has a different opinion, we need to merge this to get this fixed ASAP and then you can change the sidebar to whatever makes you happy (as long as there aren't sections of the docs orphaned anymore)

ok I understand you're frustrated but I think we can still find some middle ground here, and taking a bit of time now to understand the problem properly and put together a solution will prevent more confusion for users.
If i'm interpreting your frustrations correctly there are 2 aspects to the issue: a) that the sidebar/topbar UI has changed making it less intuitive (in your opinion) to find what you need and b) important pieces are missing from the toctree making the navigation broken. a) is highly subjective and we can debate it another time, and b) is the more pressing issue that needs to be resolved asap, and I believe we can resolve that without completely reverting to the old sidebar view.
So let's break it down even further:

the circuit library. As you pointed out this is missing from the toctree and not linked from either the sidebar or the top bar meaning the only way users can get there is through searching. I agree this is not great so we should add the circuit library back to the sidebar

the contributing guidelines etc. Users can still access them through the top menu and they are top level standalone pages so there isn't the navigation issue moving backwards as they anyway live directly under the docs homepage so there isn't the same toctree issue (unless I'm mistaken?). So i don't think these critically need to be moved back to the sidebar. As a side note these pages also aren't specific to terra (and the goal with sidebar is to only include terra specific links there and reduce duplication with the top menu)

Aer and IBM provider. As we are trying to move towards the narrative that qiskit=terra in an ideal world these would not be part of the sidebar (which should only contain terra specific pieces). Multiple design choices have been made throughout the docs revamp process specifically with the intention of making it clear to users that Aer and the IBM provider are not Qiskit, they are separate and should be accessed via the top menu. BUT I understand that currently because of how the metapackage is set up we have to include aer and ibm provider docs under the qiskit docs umbrella for the time being and removing them from the sidebar has caused issues with the toctree navigation. So for these I suggest we add them back to the sidebar but in a separate section where we make sure to signpost to users that these are separate. This also makes it easier for us to remove at a later date.

So ultimately I suggest the following:
.. toctree::
  :maxdepth: 1
  :hidden:

  getting_started
  intro_tutorial1
  tutorials
  API Reference <apidoc/terra>
  Circuit Library <apidoc/circuit_library>
  release_notes
  configuration
  GitHub <https://github.com/Qiskit/qiskit-terra>
  faq

.. toctree::
  :maxdepth: 1
  :caption: Other API References
  :hidden:

 apidoc/aer
 apidoc/ibmq-provider

I think this is a reasonable compromise that solves the crux of the issue for the time being with minimal disruption to the users 😄

That works fine for me except for the contributing guidelines, as I said before every document included in the sphinx build must be included in the toctree at some level. It doesn't need to be the top level root/index page but we must link to it from a toctree somewhere. The top bar by itself is not a solution in general because it is divorced from sphinx itself (meaning if you use other builders the documents are orphaned) and it also hard codes the url to qiskit.org which will not work for local builds or anyone using the documentation outside of our hosted build. This rule will also be enforced in the future during sphinx builds when we add -W to the sphinx-build call which we already do everywhere else except ibmq and here (because of ibmq).

That works fine for me except for the contributing guidelines, as I said before every document included in the sphinx build must be included in the toctree at some level. It doesn't need to be the top level root/index page but we must link to it from a toctree somewhere. The top bar by itself is not a solution in general because it is divorced from sphinx itself (meaning if you use other builders the documents are orphaned) and it also hard codes the url to qiskit.org which will not work for local html builds or anyone using the html builder output for something outside of our hosted build. This rule will also be enforced in the future during sphinx builds when we add -W to the sphinx-build call which we already do everywhere else except ibmq and here (because of ibmq).

I suggest to add a new section "Interested in contributing to Qiskit?" and add the non-hidden toctree in the home page at the bottom. That way the pages are listed in a toctree and it won't show up in the sidebar. Do you think that's a good solution?

After discussions with @javabster and @mtreinish I updated the PR with the latest agreed sidebar

.. toctree::
   :hidden:

   Overview <self>
   qc_intro
   getting_started
   intro_tutorial1
   tutorials
   API Reference <apidoc/terra>
   Circuit Library <apidoc/circuit_library>
   release_notes
   configuration
   GitHub <https://github.com/Qiskit/qiskit-terra>
   faq

.. toctree::
   :caption: Contributing
   :hidden:

   contributing_to_qiskit
   deprecation_policy
   maintainers_guide

.. toctree::
   :caption: Other API References
   :hidden:

   apidoc/aer
   apidoc/ibmq-provider

The circuit library entry is added because the docs is built with Terra release not main branch (fixed in https://github.com/Qiskit/qiskit-terra/pull/9533). We can remove it after the next terra patch release 0.23.2 which is targeted to release on Feb 16.


DispatcherTimer.Tick can be executed when the timer is not running (#15626)

What does the pull request do?
It fixes the issue #15626.
How has the PR been implemented?

added check whether the field _isEnabled in the class DispatcherTimer has been set to true before raising the Tick event
added synchronization wrapper class ReaderWriterLockWrapper, which relies on the .NET class ReaderWriterLockSlim
replaced the lock() synchronization primitive with the ReaderWriterLockWrapper, which matches the use case more closely
added a read synchronization block around the getter for the property IsEnabled in the class DispatcherTimer, as consumers of the getter were previously not synchronized
fixed a potential race condition when checking for null before raising the Tick event
decided against marking the field _isEnabled in the class DispatcherTimer as volatile, since all access to it has now been properly regulated

@Mihnea Rădulescu,
Please read the following Contributor License Agreement (CLA). If you agree with the CLA, please reply with the following:
@cla-avalonia agree

Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ),
and conveys certain license rights to the AvaloniaUI OÜ ( “AvaloniaUI OÜ” ) for Your contributions to
AvaloniaUI OÜ open source projects. This Agreement is effective as of the latest signature date below.
1. Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to AvaloniaUI OÜ under this Agreement.
“Project” means any of the projects owned or managed by AvaloniaUI OÜ and offered under a license
approved by the Open Source Initiative (www.opensource.org).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
3. Originality of Work.  You represent that each of Your Submissions is entirely Your
original work. Should You wish to Submit materials that are not Your original work,
You may Submit them separately to the Project if You (a) retain all copyright and
license information that was in the materials as you received them, (b) in the
description accompanying your Submission, include the phrase "Submission
containing materials of a third party:" followed by the names of the third party and any
licenses or other restrictions of which You are aware, and (c) follow any other
instructions in the Project's written guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
5. Licenses.
a. Copyright License. You grant AvaloniaUI OÜ, and those who receive the Submission directly
or indirectly from AvaloniaUI OÜ, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable
license in the Submission to reproduce, prepare derivative works of, publicly display, publicly perform,
and distribute the Submission and such derivative works, and to sublicense any or all of the foregoing
rights to third parties.
b. Patent License. You grant AvaloniaUI OÜ, and those who receive the Submission directly or
indirectly from AvaloniaUI OÜ, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license
under Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.
6. Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3 ). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6 , THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to AvaloniaUI OÜ. You agree to notify AvaloniaUI OÜ in writing of any facts or
circumstances of which You later become aware that would make Your representations in this
Agreement inaccurate in any respect.
8. Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the Republic of Estonia, and
the parties consent to exclusive jurisdiction and venue in the courts sitting in Talinn,
Estonia. The parties waive all defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by AvaloniaUI OÜ.
AvaloniaUI OÜ dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1.

Mihnea Rădulescu doesn't seem to be a GitHub user.
Please add the emails used in your commits to your Github account accordingly.

@cla-avalonia agree

DispatcherTimer.Stop() aborts the enqueued operation, so it won't be executed after Stop is called. If there is a bug, it's definitely elsewhere and most likely not in the timer code that is mostly a copy of WPF one.

@cla-avalonia agree


Call to primitive regrst has not been updated in Mantle.hpp

In line 61 of Mantle.hpp:
https://github.com/rdaly525/coreir/blob/4f85bab3aa1990f28bd188fdfa330050074c1839/src/ir/headers/mantle.hpp#L61
Mantle.reg calls coreir.regrst, not coreir.reg_arst. This results in an error when a mantle.reg is instantiated with a reset.

closed by #586


Considering short name of the course

some classes are 3 'words' long like C D 10G because we are only getting 2 \w.
sample data. Original link
--------------------------------------------------------------------------------
                                  FOUNDATION CORE
--------------------------------------------------------------------------------
CHLD 250    Child Development         (3)|C D 10G  &  Child Development (The (4)
                                         |            Early Years)
                                         |   Same as: PSYC 10G
                                         |C D 10H     Child Development      (4)
                                         |            (Middle Childhood and
                                         |            Adolescence)
                                         |   Same as: PSYC 10H
                                         |   OR
                                         |PSYC 10G &  Child Development (The (4)
                                         |            Early Years)
                                         |   Same as: C D 10G
                                         |PSYC 10H    Child Development      (4)
                                         |            (Middle Childhood and
                                         |            Adolescence)
                                         |   Same as: C D 10H
--------------------------------------------------------------------------------
...

New algorithm does not have this issue.


O> 20180207 RChain Active Members Meeting

[ ] Prepare report for Greg's Debrief (2018-02-07)
[x] Prepare RAM meeting agenda - would like to keep it to five discussion points so we have time to cover in enough detail
[x] Re-cap on and status of action points
[ ] @n10n to confirm he's available for a more comprehensive update on the KYC and validation process - continued from last week's meeting
[x] Any key discussion points anyone wants to address should be added to the agenda here and we can allocate time accordingly.

Feedback about the past few meetings is welcome. I want to make sure this is a useful hour of everyone's time.
Budget: $2000
Time: 1 week

@dcpnlau what about a discussion on the allocation of budgets  using  issue #284 as a pointer on what needs to be addressed

@dcpnlau what about a discussion on the allocation of budgets  using  issue #284 as a pointer of what needs to be addressed

@dcpnlau Is the meeting slated for tomorrow? or on 2018-02-08?
I added a 6th point.

@BelovedAquila - happy for you to give your take on this as part of the 1-min member updates up front. We can dive into this conversation at the end of the meeting if there's time left or take it to next week's agenda if there's a need from the wider members team to discuss this.

@dcpnlau alright, looking  forward to it. Thanks

RChain Active Members Meeting
https://zoom.us/j/197490909 (webinar)
2018-February-07, 20:00 UTC (after Greg's Debrief)
Sydney +11, Beijing +8, Lagos +1, Amsterdam +1,
New York -5, Seattle -8
Agenda (Key discussion points can be added to the agenda):
https://docs.google.com/document/d/1jvUn8AKLmvnibNk2KT-tqJdWDV5FoYZfVPIF8czxy64/edit#heading=h.b6i526d9dxs1
Above is a post of the upcoming meeting which I posted on discord and telegram but am wondering if it would be a good idea to post it on reddit. :\

@dcpnlau and @ojimadu wasn't able to connect for the meeting yesterday, all it noticed through out the time was "waiting for the Host to start the meeting" why is that?

The link to the meeting was changed.

I demo'd the budget/rewards web app in #260 and added a couple notes into the doc


JWT ECSDA - used private key instead of public and public instead of private

Usage
scala> val token = Jwt.encode("""{"user":1}""", ecKey.getPrivate, JwtAlgorithm.ES512)
token: String = eyJ0eXAiOiJKV1QiLCJhbGciOiJFUzUxMiJ9.eyJ1c2VyIjoxfQ.AS8XjhcOx8L4wtDgcnHZt2e4UueqlCSmT_d6EiHAnUZTclFc62QPbcKO8ikz_HJXN-Lhi5fN3JUv0ZC3xGOvR2-NAbv7hZdYxQocBugXouLL7Ryn2P21IEDdi4EjOu19kPdp9cfN15XNGRV5VpIVBQ1n4-VVDiWpByy0r8yhrhC_bHsn
scala> Jwt.decode(token, ecKey.getPublic, JwtAlgorithm.allECDSA)
res7: scala.util.Try[pdi.jwt.JwtClaim] = Success(pdi.jwt.JwtClaim@a0b74282)
public key for encode and private key for decode

Are you sure about this @sim732 ? Do you have any reference?
According to the spec

A JWT is signed with an ECDSA P-256 SHA-256 signature as follows:

Generate a digital signature of the UTF-8 representation of the JWT Signing Input using ECDSA P-256 SHA-256 with the desired private key. The output will be the EC point (R, S), where R and S are unsigned integers.
Turn R and S into byte arrays in big endian order. Each array will be 32 bytes long.
Concatenate the two byte arrays in the order R and then S.
Base64url encode the 64 byte array as defined in this specification.

So this is encoding using the private key. And then:

The following procedure is used to validate the ECDSA signature of a JWT:

Take the JWT Crypto Segment and base64url decode it into a byte array. If decoding fails, the token MUST be rejected.
The output of the base64url decoding MUST be a 64 byte array.
Split the 64 byte array into two 32 byte arrays. The first array will be R and the second S. Remember that the byte arrays are in big endian byte order; please check the ECDSA validator in use to see what byte order it requires.
Submit the UTF-8 representation of the JWT Signing Input, R, S and the public key (x, y) to the ECDSA P-256 SHA-256 validator.
If the validation fails, the token MUST be rejected.

The public key for the decoding and validation.


Cannot sync an archive node from genesis

Hello I have attempted to sync an archive node and run into the same issue on block 1961577
12:29PM INF ABCI Replay Blocks appHeight=1961577 module=consensus stateHeight=1961577 storeHeight=1961578
63
12:29PM INF Replay last block using real app module=consensus
62
Error: error during handshake: error on replay: wrong Block.Header.LastResultsHash.  Expected 0F0FCA6D59D478E1DA095B4110E70EF72E11DD37648EA89119431B4EABDB1C74, got 5FB95E17A8638237E6C556750DBC232DCF4353ED6EA7DBB68C8EC74D3CD192F1

this occurs after the v3 hardfork. the version i am using when this error occurs is v3.0.0. i have tried multiple different deployments and each time it fails on the same block.
The sync from genesis I have run and upgraded from the following versions:
v1.1.2 upgrading to v2.0.1 for the v2 hardfork then upgrading to v3.0.0 for the v3 hardfork.
I cannot sync from genesis with v12 as I get an instant go panic on startup, its the same with v11. I have trying to sync from genesis with v10 and it does not panic but after leaving it for a few days it never progresses past block 1.
How can an archive node be synced and how can I get past block 1961577. No matter what I try I just cant get past this block.

Hey there how are you building the binaries? from v2 to v3 it will require having specific go version of preference. Another way could be using the docker container we publish to docker hub.


[WIP] (docs): update docs/performance/reduce-reconcilation.md

Summary of changes:

correct spelling
increase readability

Checklist before submitting:

[ ] Added entry to CHANGELOG.md
[x] Added/updated relevant tests
[x] Added/updated documentation

You should mark this as a draft if you don't want it to be reviewed yet 😛

Coverage remained the same at 94.775% when pulling 7ae71622db9babaac5787e9c5bdda413cd014c36 on vladdoster:patch-1 into 4796c79e2015fae51f2734ba2eb4dac07b212ae2 on Roblox:master.

Hi Vlad! Can you follow the CLA workflow?


Provide nodeSelector option for Ambassador

I see a couple of options to support this. This allows to install ambassador on select nodes.

In the ambassador-rbac and no-rbac yaml files support the nodeSelector option
To provide it via templates in helm charts.

Not a difficult thing to add, but with mixed clusters it is very important.

Closing -- checked with @campbelldgunn and he confirms that adding his own nodeSelector works.


Unable to include scripts in AssetBundle

It seems that regular scripts aren't allowed to be included in the AssetBundle.
I thought having the scripts in a dll would resolve it but while loading in the game tells me:
Warning: Unity Log] The referenced script (mydllfile.myscript) on this Behaviour is missing!
Even though the gameobjects definitely has the correct script attached.
Not sure if this is my fault but I'm a bit confused now.

It seems that regular scripts aren't allowed to be included in the AssetBundle. I thought having the scripts in a dll would resolve it but while loading in the game tells me: Warning: Unity Log] The referenced script (mydllfile.myscript) on this Behaviour is missing! Even though the gameobjects definitely has the correct script attached. Not sure if this is my fault but I'm a bit confused now.

this is not allowed, a bundle can't be scanned with any antivirus so it's easy to put malwares in them
theres a whitelist of allowed components

That makes sense.
So I'm guessing there is no way to have custom stuff happen like.. a box trigger enabling some particles or having a sound play every so many seconds for instance.

That makes sense. So I'm guessing there is no way to have custom stuff happen like.. a box trigger enabling some particles or having a sound play every so many seconds for instance.

i planned to add some scripts to do that, but i never did it, and the mod is in end of support so.. :/

That makes sense. So I'm guessing there is no way to have custom stuff happen like.. a box trigger enabling some particles or having a sound play every so many seconds for instance.

i planned to add some scripts to do that, but i never did it, and the mod is in end of support so.. :/

Wouldn't it be possible to include these scripts in a separate DLL and run them from there?

Wouldn't it be possible to include these scripts in a separate DLL and run them from there?

Yes, you need to make a DLL, bundles can't store scripts
Load this DLL in unity by placing it in a plugins folder

I did try this but whenever I referenced a script from my dll on objects in the prefab, when loaded, the game couldn't find them.

I did try this but whenever I referenced a script from my dll on objects in the prefab, when loaded, the game couldn't find them.

Same on that, Little success. I have tried using a bepinex plugin to add the dll via bepinex, but it still couldn't find the reference. won't stop me from trying to figure it out lol

Does your bepinex plugins was loading before lethal Expansion?

Does your bepinex plugins was loading before lethal Expansion?

Nope, it seems lethalSDK has priority over the plugin, and I lack the knowledge on how to increase priority.

Does your bepinex plugins was loading before lethal Expansion?

Nope, it seems lethalSDK has priority over the plugin, and I lack the knowledge on how to increase priority.

Add a dependency for Lethal Expansion in your plugin

Does your bepinex plugins was loading before lethal Expansion?

Nope, it seems lethalSDK has priority over the plugin, and I lack the knowledge on how to increase priority.

Add a dependency for Lethal Expansion in your plugin Look for Bepinex dependency flag

What I'm guessing is doing something along the lines of
 [BepInPlugin(GUID, Name, Version)]
 [BepInDependency("HolographicWings-LethalExpansion-1.3.30", BepInDependency.DependencyFlags.HardDependency)]

On top of the class inheriting BaseUnityPlugin?

Yes but the id of the mod is just LethalExpansion
A tip is to check the name of the config file

I've tested that, yet still comes out as not being found on the object inside the map,
Using a simple class "ExistanceNotifier"
public class ExistanceNotifier : MonoBehaviour
    {

        [SerializeField] private string message;

        public void Awake()
        {
            Debug.Log(message);
        }
    }

Using the reference
[BepInPlugin(GUID, Name, Version)]
[BepInDependency("LethalExpansion", BepInDependency.DependencyFlags.HardDependency)]

Inside the editor of the moon itself, simple awake checker

Yet, in the command line, twice:
Once, before the game has started and everything is being initialized

And once the moon has loaded.

So, I'm not sure exactly what the root cause of the missing dependencies could be at this point.

I tried on my side too
LethalExpansion need your DLL as dependance, so it will need every DLL of every peoples who make custom script as dependance
I will look for an alternative, like Lua scripting

Lua is not made for Unity, it works but i will have to write every unity function which will take me months..


feat(init): deprecating init command

Relates to #11
This pull request brings back the init command, but deprecated and working as a proxy to the preset command, in case we need to release a new tag before 2.0.0

@danielsuguimoto thanks! this is good so we can have 1.6.0 prior, and wait for 2.0 with other bigger changes - we should use major versions to really do most of the breaking changes we can at once :D

@danielsuguimoto now that this one is on master, I will create master -> 2.0; after that, we should create a new PR removing the init proxy once again, so 2.0 do not keep it.


PIC32 port

PIC32 port including BSPs targeting the Digilent Wi-Fire board and the 6LoWPAN Clicker board. Kernel mode only, soft floating point only.

Looks good to be merged.
PS: What would be the difference between pic32mx and pic32mz? (Their respective arch files look very similar)

I belive they are currently the same. The MZ port still has some functionality to drop in so to minimise the changes that would need to be made in the future I made 2 copies, Thinking about it now, it might be better to use preprocessor options to conditionally compile from one architecture. Again, any suggestions would be appreciated.


UP-4643 updates commons collections

Updates commons collections library, while updating portlets that were patched to update the commons collections library.

:+1:  Looks good. I implemented this change locally.

:+1:


Fixed swapped parameters in property registration

UWP Chart binding was crashing (Failed to assign to property) due to swapped propertyType and ownerType parameters.

I added this fix to my branch, thanks for your contributions.


feat: add mainnet-renderer page

This PR adds a mainnet-renderer route that renders mainnet code fetched from testnet social db on a testnet VM. It's dependent on the networkId config introduced to Widget components in https://github.com/NearSocial/VM/pull/69
Example of DevHub running out of testnet SocialDB path dev-1685373830583-51701575881136/widget/NearSocialComponent

holding this PR until discussion and approval on PR to VM repo

@mpeterdev @charleslavon @DavidM-D https://github.com/NearSocial/VM/pull/69 has been merged into dev and should make it into the next release. We can start reviewing this PR to get it into a releasable state.

closing as inactive but can be reopened for discussion if necessary


[BUG] Types JsonRpcProvider and SignerOrProvider are incompatible

This simple code doesn't work with ethers v6.7.1 and typescript v5.2.2:
ethers.ts
import { JsonRpcProvider } from 'ethers'

export const provider = new JsonRpcProvider(process.env.RPC_PROVIDER)

eas.ts
import { EAS } from '@ethereum-attestation-service/eas-sdk'
import { provider } from './ethers.js'

export const eas = new EAS(process.env.EAS_CONTRACT)

eas.connect(provider)

Argument of type 'JsonRpcProvider' is not assignable to parameter of type 'SignerOrProvider'.
  Type 'JsonRpcProvider' is not assignable to type 'Provider'.
    The types returned by 'getNetwork()' are incompatible between these types.
      Type 'Promise<import("d:/Desktop/Hackathons/Newforum/EAS/node_modules/ethers/lib.esm/providers/network", { assert: { "resolution-mode": "import" } }).Network>' is not assignable to type 'Promise<import("d:/Desktop/Hackathons/Newforum/EAS/node_modules/ethers/lib.commonjs/providers/network").Network>'.
        Type 'import("d:/Desktop/Hackathons/Newforum/EAS/node_modules/ethers/lib.esm/providers/network", { assert: { "resolution-mode": "import" } }).Network' is not assignable to type 'import("d:/Desktop/Hackathons/Newforum/EAS/node_modules/ethers/lib.commonjs/providers/network").Network'.
          Property '#private' in type 'Network' refers to a different member that cannot be accessed from within type 'Network'.ts(2345)

What version of the SDK are you using? Are you sure you're using ethers v6? Are you using its correct types? The same code works for me without any modifications.

What version of the SDK are you using? Are you sure you're using ethers v6?

Should have attach the package.json as well, sorry
{
  "type": "module",
  "scripts": {
    "start": "ts-node --esm --files ./src/index.ts"
  },
  "dependencies": {
    "@ethereum-attestation-service/eas-sdk": "^1.2.0-beta.0",
    "dotenv": "^16.3.1",
    "ethers": "^6.7.1"
  },
  "devDependencies": {
    "@types/node": "^20.6.3",
    "@typescript-eslint/eslint-plugin": "^6.7.2",
    "@typescript-eslint/parser": "^6.7.2",
    "eslint": "^8.49.0",
    "eslint-config-standard": "^17.1.0",
    "eslint-plugin-import": "^2.28.1",
    "eslint-plugin-n": "^16.1.0",
    "eslint-plugin-promise": "^6.1.1",
    "ts-node": "^10.9.1",
    "typescript": "^5.2.2"
  }
}

Are you using its correct types?

ethers supports TS from the box

I'm still unable to reproduce it. I've created a sample project with your package.json (including "type": "module") with an appropriate tsconfig.json and everything works, so perhaps the problem is with your tsconfig.json?
Can you try to reproduce it on a sample project yourself and share it with us?

Node18 + Strictest tsconfig.json:
{
    "compilerOptions": {
    "rootDir": "src",
    "outDir": "ts-build",
    "lib": ["es2023"],
    "module": "node16",
    "target": "es2022",
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "moduleResolution": "node16",
    "allowUnusedLabels": false,
    "allowUnreachableCode": false,
    "exactOptionalPropertyTypes": true,
    "noFallthroughCasesInSwitch": true,
    "noImplicitOverride": true,
    "noImplicitReturns": true,
    "noPropertyAccessFromIndexSignature": true,
    "noUncheckedIndexedAccess": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "isolatedModules": true,
    "checkJs": true,
  }
}

It seems that your module resolution isn't fully compatible with ethers and how the SDK is compiled. Changing the configuration to "module": "CommonJS" and "moduleResolution": "node" seems to resolve this. Can you give it a shot?

Yes, it did work. I think the problem is with the types of eas-sdk. In runtime everything is fine, I tried to ignore the line:
// @ts-ignore
eas.connect(provider)

Both JsonRpcProvider and Provider are ethers types and are usually fully compatible (JsonRpcProvider implements AbstractProvider which implements Provider), unless they are imported in an incompatible way, which what happens in your case. Since no other project/protocol stumbled upon this problem - I'll resolve this issue for now.


stage1-coreos.aci and sysctl call in kubernetes deployment

During running kube_proxy on CoreOs with rkt stage1-coreos.aci' 'm getting error:
/opt/bin/rkt run --insecure-options=all --debug=true --pod-manifest /home/core/manifest-kube-proxy-<IP_ADDRESS>-627568834.kson --stage1-path /opt/rkt/stage1-coreos.aci
image: using image from file /opt/rkt/stage1-coreos.aci
stage0: Preparing stage1
stage0: Writing image manifest
stage0: Loading image sha512-0380d33f9d6e22a46656c29c6e5b3484016bf8a5acdf65bf9d049f4e6ecc57db
stage0: Writing image manifest
stage0: Writing pod manifest
stage0: Setting up stage1
stage0: Wrote filesystem to /var/lib/rkt/pods/run/c5138466-7cd0-4c31-9350-6059ecc59914
stage0: Pivoting to filesystem /var/lib/rkt/pods/run/c5138466-7cd0-4c31-9350-6059ecc59914
stage0: Execing /init
networking: loading networks from /etc/rkt/net.d
networking: loading network default with type ptp
Spawning container rkt-c5138466-7cd0-4c31-9350-6059ecc59914 on /var/lib/rkt/pods/run/c5138466-7cd0-4c31-9350-6059ecc59914/stage1/rootfs.
Press ^] three times within 1s to kill container.
systemd 225 running in system mode. (-PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS -ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
Detected virtualization systemd-nspawn.
Detected architecture x86-64.

Welcome to Linux!

Set hostname to <rkt-c5138466-7cd0-4c31-9350-6059ecc59914>.
Initializing machine ID from container UUID.
[  OK  ] Created slice -.slice.
[  OK  ] Listening on Journal Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Created slice system.slice.
[  OK  ] Started Pod shutdown.
         Starting Journal Service...
[  OK  ] Started kube-proxy Reaper.
[  OK  ] Created slice system-prepare\x2dapp.slice.
[  OK  ] Started Journal Service.
         Starting Prepare minimum environment for chrooted applications...
[  OK  ] Started Prepare minimum environment for chrooted applications.
[  OK  ] Started Application=kube-proxy Image=gcr.io/google_containers/hyperkube.
[  OK  ] Reached target rkt apps target.
[ 9810.152170] hyperkube[4]: I0420 14:08:53.832111       4 server.go:200] Using iptables Proxier.
[ 9810.152700] hyperkube[4]: F0420 14:08:53.832270       4 server.go:208] Unable to create proxier: can't set sysctl net/ipv4/conf/all/route_localnet: open /proc/sys/net/ipv4/conf/all/route_localnet: read-only file system
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Container rkt-c5138466-7cd0-4c31-9350-6059ecc59914 failed with error code 255.

Tested with rkt from master branch
kube_proxy:
{
    "acKind": "PodManifest",
    "acVersion": "0.7.4+git",
    "annotations": [
        {
            "name": "rkt.kubernetes.io/managed-by-kubelet",
            "value": "true"
        },
        {
            "name": "rkt.kubernetes.io/uid",
            "value": "d161ae04446b87417ec229528e2264ed"
        },
        {
            "name": "rkt.kubernetes.io/name",
            "value": "kube-proxy-<IP_ADDRESS>"
        },
        {
            "name": "rkt.kubernetes.io/namespace",
            "value": "kube-system"
        },
        {
            "name": "rkt.kubernetes.io/created",
            "value": "1461152700"
        },
        {
            "name": "rkt.kubernetes.io/restart-count",
            "value": "14"
        }
    ],
    "apps": [
        {
            "annotations": [
                {
                    "name": "rkt.kubernetes.io/container-hash",
                    "value": "897891205"
                },
                {
                    "name": "rkt.kubernetes.io/termination-message-path",
                    "value": "/var/lib/kubelet/pods/d161ae04446b87417ec229528e2264ed/containers/kube-proxy/5093cea5-06ed-11e6-9976-0cc47a0c6fd2"
                }
            ],
            "app": {
                "environment": [
                    {
                        "name": "KUBERNETES_PORT",
                        "value": "tcp://<IP_ADDRESS>:443"
                    },
                    {
                        "name": "KUBERNETES_PORT_443_TCP_PROTO",
                        "value": "tcp"
                    },
                    {
                        "name": "KUBERNETES_PORT_443_TCP_PORT",
                        "value": "443"
                    },
                    {
                        "name": "KUBERNETES_PORT_443_TCP_ADDR",
                        "value": "<IP_ADDRESS>"
                    },
                    {
                        "name": "KUBERNETES_SERVICE_HOST",
                        "value": "<IP_ADDRESS>"
                    },
                    {
                        "name": "KUBERNETES_SERVICE_PORT_HTTPS",
                        "value": "443"
                    },
                    {
                        "name": "KUBERNETES_SERVICE_PORT",
                        "value": "443"
                    },
                    {
                        "name": "KUBERNETES_PORT_443_TCP",
                        "value": "tcp://<IP_ADDRESS>:443"
                    },
                    {
                        "name": "PATH",
                        "value": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
                    }
                ],
                "exec": [
                    "/hyperkube",
                    "proxy",
                    "--proxy-mode=iptables",
                    "--master=https://<IP_ADDRESS>:443",
                    "--kubeconfig=/etc/kubernetes/worker-kubeconfig.yaml"
                ],
                "group": "0",
                "isolators": [
                    {
                        "name": "os/linux/capabilities-retain-set",
                        "value": {
                            "set": [
                                "CAP_MKNOD",
                                "CAP_CHOWN",
                                "CAP_LINUX_IMMUTABLE",
                                "CAP_SYS_MODULE",
                                "CAP_SYS_PTRACE",
                                "CAP_SYS_CHROOT",
                                "CAP_SYS_BOOT",
                                "CAP_SYS_TIME",
                                "CAP_AUDIT_WRITE",
                                "CAP_NET_BROADCAST",
                                "CAP_NET_RAW",
                                "CAP_IPC_LOCK",
                                "CAP_SYS_RAWIO",
                                "CAP_FSETID",
                                "CAP_WAKE_ALARM",
                                "CAP_MAC_OVERRIDE",
                                "CAP_BLOCK_SUSPEND",
                                "CAP_AUDIT_READ",
                                "CAP_DAC_READ_SEARCH",
                                "CAP_SETUID",
                                "CAP_SYS_TTY_CONFIG",
                                "CAP_AUDIT_CONTROL",
                                "CAP_DAC_OVERRIDE",
                                "CAP_NET_ADMIN",
                                "CAP_IPC_OWNER",
                                "CAP_SYS_RESOURCE",
                                "CAP_LEASE",
                                "CAP_SETFCAP",
                                "CAP_MAC_ADMIN",
                                "CAP_KILL",
                                "CAP_SETPCAP",
                                "CAP_NET_BIND_SERVICE",
                                "CAP_SYS_NICE",
                                "CAP_FOWNER",
                                "CAP_SETGID",
                                "CAP_SYS_PACCT",
                                "CAP_SYS_ADMIN",
                                "CAP_SYSLOG"
                            ]
                        }
                    }
                ],
                "mountPoints": [
                    {
                        "name": "ssl-certs",
                        "path": "/etc/ssl/certs"
                    },
                    {
                        "name": "kubeconfig",
                        "path": "/etc/kubernetes/worker-kubeconfig.yaml",
                        "readOnly": true
                    },
                    {
                        "name": "etc-kube-ssl",
                        "path": "/etc/kubernetes/ssl",
                        "readOnly": true
                    },
                    {
                        "name": "termination-message-5093cea5-06ed-11e6-9976-0cc47a0c6fd2",
                        "path": "/dev/termination-log"
                    }
                ],
                "user": "0"
            },
            "image": {
                "id": "sha512-0380d33f9d6e22a46656c29c6e5b3484016bf8a5acdf65bf9d049f4e6ecc57db"
            },
            "name": "kube-proxy"
        }
    ],
    "isolators": null,
    "ports": null,
    "volumes": [
        {
            "kind": "host",
            "name": "termination-message-5093cea5-06ed-11e6-9976-0cc47a0c6fd2",
            "source": "/var/lib/kubelet/pods/d161ae04446b87417ec229528e2264ed/containers/kube-proxy/5093cea5-06ed-11e6-9976-0cc47a0c6fd2"
        },
        {
            "kind": "host",
            "name": "ssl-certs",
            "source": "/usr/share/ca-certificates"
        },
        {
            "kind": "host",
            "name": "kubeconfig",
            "source": "/etc/kubernetes/worker-kubeconfig.yaml"
        },
        {
            "kind": "host",
            "name": "etc-kube-ssl",
            "source": "/etc/kubernetes/ssl"
        }
    ]
}

CoreOs version:
bash
cat /etc/os-release
NAME=CoreOS
ID=coreos
VERSION=1010.1.0
VERSION_ID=1010.1.0
BUILD_ID=2016-04-07-0355
PRETTY_NAME="CoreOS 1010.1.0 (MoreOS)"
ANSI_COLOR="1;32"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"

Docker image: gcr.io/google_containers/hyperkube:v1.2.0

can't set sysctl net/ipv4/conf/all/route_localnet: open /proc/sys/net/ipv4/conf/all/route_localnet: read-only file system

systemd-nspawn mounts /proc/sys read-only in the pod (see mount_all()) so the pod cannot do sysctls.
One option is to use "rkt fly" (--stage1-path /opt/rkt/stage1-fly.aci in your example). Iit will then run on the host namespaces and the sysctl would be done in the host network namespace.
Another way would be to use the tuning CNI plugin (added in rkt 1.1 by https://github.com/coreos/rkt/pull/2140) to configure the sysctl before starting the application. But the application (hyperkube) would need to be told not to do sysctls itself.

@yifan-gu pinging, what would be the canonical way of running the k8s proxy in rkt(netes)?

@pskrzyns do you mind retrying with --net=host?

@s-urbaniak ok, i will have results tommorow, cause at this moment i have cluster occupied ;)

@s-urbaniak @pskrzyns
Hmm, unfortunately as @alban mentioned, --net=host might not solve the problem as the /proc/sys is still readonly..

I feel the near term, we need to tell rktnetes to use rkt-fly in such cases.
Ref https://github.com/kubernetes/kubernetes/issues/23944

@s-urbaniak --net-host, didnt solve the case (sysctl is still called)
@yifan-gu cant test rkt-fly cause https://github.com/coreos/rkt/issues/2480

@pskrzyns Are you able to mount for rkt-fly after giving the --mount flag?

@yifan-gu Yes
But now when using kubelet i have similar problem to https://github.com/coreos/rkt/issues/2141,
and suggested solution isn't working for me.
I think i will start with creating kubernetes cluster using binary or docker, and rkt + kubelet just for running pods

This is related to https://github.com/coreos/rkt/issues/2751.

https://github.com/coreos/coreos-kubernetes/blob/master/multi-node/generic/controller-install.sh
this script contains the annotation configuration in kube-proxy that fixes this problem.


Ehancement request: option to turn off console logging

First, thank you for your extremely handy and easy to use package.
If you are considering enhancement requests, could we have an option to turn off console logging of things this package does?  Unless I'm actively debugging a problem with file uploads, all of these messages tend to distract me when resolving other problems:
Server:

Client:

Valid point. It is solved in next release of both server and client.
The client is configurable via:
Uploader.logLevel = Uploader.logLevels.debug;


Question / colors

I'm using Darcula theme, but when I use this tmbundle in a jetbrains product, the background colors are white etc (not at all like the lovely screenshot of the dark theme)
Has anyone else encountered this?
This has a white background, but should be dark:

Figured it out (duh):
So, on the screen for Textmate Bundles, below it is a little table that has "IDE color scheme =-> textmate color scheme" mapping.
So set Darcula on the left (IDE) & Darcula on the right (probably set to Mac Classic at the moment, which makes it white)

@rstudner Same shit, thanks.
@ruswerner It would be better if you will add this info into readme =)

@se-panfilov sorry mate. I'm not supporting this anymore, but you can fork it if you like. It was actually quicker to convert our entire codebase to JavaScript/JSX than wait for JetBrains to build support into the tool; and we're better off anyway :)

@ruswerner Okay, np. It's works anyway, and tbh I believe that we will move away from cjsx asap =)


Update handlebars dependency

There is an NPM Security Advisory for handlebars:
https://www.npmjs.com/advisories/755

Coverage remained the same at 97.523% when pulling 513550dee757a453c54698838f0bded61e0cbfe6 on mobilutz:patch-1 into bc84c315271a5dd4d39bcefc5925cfb61a3d174a on gotwarlost:master.

Hoping this change is accepted.

@SteveSonoa I don't think that this Deprecated repo will see any change anymore. 🙁
But lets hope.

Maybe an exceptional release could be made as many libraries still rely on this dependency.
Lets hope.

I do not need this fix anymore. Closing this as it is also 3 years old!


Cumulative changes to DeviceUpdate

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[x] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[x] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@ArcturusZhang, @raych1,
Changes:

Removed bogus operation Instances_ListBySubscription
Used the inner error model from common types v1 (kept the outer model)
Fixed license for Go SDK

See also https://github.com/Azure/azure-rest-api-specs-pr/pull/3243/

@raych1 please complete the PR and I will fill a request to publish new version of SDK.

It's out of breaking change policy scope since this service isn't GAed.


Unable to tell when NATs Transport is ready

Similar to #131 but for NATS rather than HTTP.
I only started learning Go last week, so I apologise if I'm missing anything obvious.
Is there any specific reason why StartListener is a blocking call? It's documented within NATS transport.go that it's a blocking call, but the documentation on the Transport interface doesn't specify.
https://github.com/cloudevents/sdk-go/blob/73126cd029da7aed7b2ca33d5f4b135d8e66d051/pkg/cloudevents/transport/nats/transport.go#L116-L118
https://github.com/cloudevents/sdk-go/blob/73126cd029da7aed7b2ca33d5f4b135d8e66d051/pkg/cloudevents/transport/transport.go#L11-L22
I'd suggest changing the implementation to return after the subscription is created, something like this?
t.sub, err = t.Conn.Subscribe(t.Subject, func(m *nats.Msg) {
    ...
})

go func() {
	<-ctx.Done()
	if sub != nil {
		err := sub.Unsubscribe()
		if err != nil {
			// we're in a goroutine, just log the error
		}
	}
}()

return err

This would be a breaking change, but I notice you haven't actually made a tagged release for this feature yet?

In general it is a blocking call so that you can do lifecycle management using the go context and not have to pass around stop channels. I think what you have suggested could be how the transport manages its self or adding some options to help with these lifecycle events.

and not have to pass around stop channels

^^ this is my point in the opposite argument, you'd have to provide a start channel which emits once the subscriber is ready.
I will look at making a separate PR as the same time as I tackle #258, as it's not much work to implement, and we can have a proper discussion once we have some actual code to review if that works for you?

Just to clarify as well. I have only just started learning Go, so I'm open to being told my way isn't "the Go way", just so long as some alternative solution to the issue is agreed ☺

Just about to pick this back up and notice that v1.0.0 has been released which now makes the proposed solution a breaking change.
What's the thoughts on this? An alternative solution is to provide an additional transport Option to invoke a callback when the transport has established the subscription, but I'd prefer the initial solution.

Is this one still valid with the latest refactoring of nats from transport to the new protocol?

Yeah this isn't relevant anymore, this was back when receivers/handlers would be invoked by the subscribers, rather than consumers blocking on receiver.Receive().


[Plugin] Replacing a piece of source code

WebPack does that a lot with require and define. But how does a plugin implement that?
Let's say we have this in our entry:
foo("bar");

That gives me:
{ range: [ 0, 10 ],
  loc: WrappingSourceLocation { start: { line: 1, column: 0 }, end: { line: 1, column: 10 } },
  type: 'CallExpression',
  callee:
   { range: [ 0, 3 ],
     loc: SourceLocation { start: [Object], end: [Object] },
     type: 'Identifier',
     name: 'foo' },
  arguments:
   [ { range: [Object],
       loc: [Object],
       type: 'Literal',
       value: 'bar',
       raw: '"bar"' } ] }

But how do I replace it to come out as:
bar("bar");

I can see how it somehow is being done:
https://github.com/webpack/webpack/blob/master/lib/dependencies/LocalModuleDependency.js#L22
But that piece doesn't quite make me understand. Would be nice to hear back :)

a plugin can add a Dependency to the module. For a Dependency a template is registered, which can do string replacements or inserts on the source code.


Social Login example with Auth0

Hey, was wondering if it would be possible to add an example on how to use social login with auth0?
https://stackoverflow.com/questions/66727836/custom-scopes-using-angular-oauth2-oidc-with-auth0-and-github
Thank you

I saw your cross-post of the same thing at my sample repo. My answer there holds to a lesser degree for the library, but there are some bits of docs around integration with specific server solutions.
There is an example of integrating with Auth0. It does not include full integration examples that show how to integrate with a party beyond the IDS (e.g. a third party login server). But if you or another community member wants to contribute some extra details, feel free to add it!
PS. It might be good form to make your post here at GitHub a fully self-contained feature request. Currently it reads as a "can you answer my Stack Overflow question" issue, as opposed to a feature request you might be after? E.g. a few specifics of what/why you want things.

will do


Basic sample with React/GraphQL/Apollo client - failing to run

`Nested Exception
Exception: Sitecore.JavaScriptServices.ViewEngine.NodeServices.HostingModels.NodeInvocationException
Message: 2 errors were thrown when executing your fetchData functions. See the Sitecore logs preceding this error for details.
Error: 2 errors were thrown when executing your fetchData functions. See the Sitecore logs preceding this error for details.
    at C:\inetpub\wwwroot\sc90.local\dist\gh-app\server.bundle.js:1:328251
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
Source: Sitecore.JavaScriptServices.ViewEngine.NodeServices
   at Sitecore.JavaScriptServices.ViewEngine.NodeServices.HostingModels.Http.HttpNodeInstance.<InvokeExportAsync>d__7`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Sitecore.JavaScriptServices.ViewEngine.NodeServices.HostingModels.OutOfProcessNodeInstance.<InvokeExportAsync>d__13`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Sitecore.JavaScriptServices.ViewEngine.NodeServices.DefaultNodeServices.<InvokeExportWithPossibleRetryAsync>d__10`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Sitecore.JavaScriptServices.ViewEngine.NodeServices.DefaultNodeServices.<InvokeExportWithPossibleRetryAsync>d__10`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Sitecore.JavaScriptServices.ViewEngine.Node.Helpers.AsyncHelpers.RunSync[TResult](Func`1 func)
   at Sitecore.JavaScriptServices.ViewEngine.Presentation.JssRenderer.PerformRender(TextWriter writer, IRenderEngine renderEngine, String moduleName, String functionName, Object[] functionArgs)
   at Sitecore.JavaScriptServices.ViewEngine.Presentation.JssRenderer.Render(TextWriter writer)
   at Sitecore.Mvc.Pipelines.Response.RenderRendering.ExecuteRenderer.Render(Renderer renderer, TextWriter writer, RenderRenderingArgs args)
   at Sitecore.Mvc.Pipelines.Response.RenderRendering.ExecuteRenderer.Process(RenderRenderingArgs args)
   at (Object , Object[] )
   at Sitecore.Pipelines.CorePipeline.Run(PipelineArgs args)
   at Sitecore.Pipelines.DefaultCorePipelineManager.Run(String pipelineName, PipelineArgs args, String pipelineDomain)
   at Sitecore.Mvc.Pipelines.PipelineService.RunPipeline[TArgs](String pipelineName, TArgs args)
   at Sitecore.Mvc.Presentation.RenderingView.Render(ViewContext viewContext, TextWriter writer)
   at System.Web.Mvc.ViewResultBase.ExecuteResult(ControllerContext context)
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult)
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult)
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList`1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult)
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionResultWithFilters(ControllerContext controllerContext, IList`1 filters, ActionResult actionResult)
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass21.<BeginInvokeAction>b__1e(IAsyncResult asyncResult)`

I'm trying to run the graphql sample app but the application is throwing a query error. Does anyone know if there is anything else I need to change to get the sample application running?
I already completed the following tasks:

Enabled websockets on IIS
Configured the host file with the url found on the app.config file
Added the appropriate bindings in IIS
Deployed the app to sitecore
Change the web.config

I'll debug the code, but I was expecting a working example. Any help will be appreciated.

Reference https://sitecore.stackexchange.com/questions/11579/jss-graphql-sample-application-failed-to-run#comment17848_11579
As mentioned there the Sitecore logs are needed to diagnose.


support resources copying between instances

Current Behavior
resources are hled by isolated instances.
Proposed Behavior
resources can be copied between instances including

model
dataset
runtime

Solution Proposal
When swcli trigger a copy command, the instance which receives the resource is the instance which really interacts with swcli. For example:
swcli model copy <source model uri> <destination model uri>
The instance of destination model uri is the one who interacts with swcli.
Interaction API
Post Uri: {targetInstanceServer}/api/{version}/system/resource/copy
Key Headers:

name
description

Authorization
the auth token for target instance

Authorization_source
the auth token for target instance

Form Params:

name
description
required

sourceResourceUri
the resource uri without Instance URI in the source instance
true

destResourceUri
the resource uri without Instance URI in the target instance
false, default the same with sourceResourceUri

The sourceResourceUri and destResourceUri must be of the same type which could be model/dataset/runtime.
Json Response:

name
description
required

copyId
the id of this copying use wich client could query the copy progress
true

Get Uri: {targetInstanceServer}/api/{version}/system/resource/copy/{copyId}
Json Response:

name
description
type

progress
the progress of this copying 0-100
integer

currently swcli could do it independently , this issue is less important

local  project a -> local project b （cli, local fs）
local project a -> remote project b（cli, upload）
remote project a ->  local project b（cli，i,  pull）
remote 1 project a -> remote 1 project b （controller，copy api）
remote 1 project a -> remote 2 project b（controller，copy api）


expose system detail component

adding @karelhala into loop for review

Hello @terezanovotna, @karelhala,
Attaching screenshots for reference.

With View in Inventory link on ROS system detail page:

Resource Optimization Tab under Inventory details page:

Looks good to me!

@kgaikwad the order should be this PR and then inventory one so we won't end up with broken system detail.


update fresh version to 1.2

#260
For some reason when I updated fresh version to 1.2, the button on the island VoteButton.tsx stopped working. I had to remove the disabled={!IS_BROWSER}. Doesn't seem to have any impact.

makes sense. let me investigate these two new features and try to use them.

Cool. Hopefully, adding these in makes things easier/better. If that's not the case, feel free to leave them out.

@iuioiua , can you check if this last commit makes sense?
I basically created an _app.tsx wrapper, Layout component to it and removed the Layout component from the specific routes.
For the feature that allows sharing signals between islands: not sure if this is useful here so far. We only have the VoteButton.tsx island and I couldn't see much advantage in having signals being passed via props there. What do you think?

Having ctx.state in most instances of ctx.render() is no longer needed. This will need to be validated on a case-by-case basis.

If we remove the ctx.state, the sessionId doesn't get passed to the _app.tsx and the Layout component doesn't change as it is supposed to change (when the user is logged in, show 'account' in the navbar)


Move ValidationExceptions.scala to Snowplow Scala Utils

This can be closed as we're removing scala-utils.


Problems at elemental installation

Guys, why is it so difficult to install your package?
First, I had to include the elemental.less in my main, because the components doesn't style itself.
Then I had to require react-date-select, because you hadn't installed
Now, i am at:
"Module build failed: error evaluating function data-uri: Cannot 'resolveSync' because the fileSystem is not sync. Use 'resolve'!"
Using webpack, with less-loader and babel-loader
Why dont require styles at the component?

Hi, @TCMiranda you basically just named our major concerns about assets. We have just discussed those yesterday and hopefully they will be resolved soon.
Including styles in the component itself has some implications. There is an issue opened asking for the opposite thing #1 =)

Hi @nkbt
Thanks very much, I can see, so, my opinion
I think that it is great to offer the styles when you are building some ui package, really makes sense, but the components are raw without requiring css
As in ReactJS Why React

Build Composable Components
React is all about building reusable components. In fact, with React the only thing you do is build components. Since they're so encapsulated, components make code reuse, testing, and separation of concerns easy.

Another example is Polymer, which follows principles of web components, reusable and self-contained, defining the HTML, CSS and JS inside the component
The css "bootstrap" may be a great feature, but the components are something else, i can't find a reason to not make them work out of the box.
In my projects i follow the structure (with stylus, but could be less)

core.styl -> Used by components (doesn't print anything)

Variables -> Colors, sizes, etc..
Helpers -> Functions

base.styl -> HTML5 Boilerplate + my generic styles (Uses core.styl)

Only html, no .classes or #ids
Required at my root component

Components -> Require within the component (uses core.styl)

Prints the component styles

So, hope it helps somehow!
Thaks!

Just an update on this, it's looking like we'll go with http://projects.formidablelabs.com/radium

Going with pure JS styles solution has noticeable downsides. As well as going old good css way. So far the best what worked out is a combination of https://github.com/css-modules/css-modules for purely visual styling and plain js styles for state-related styling.
But the problem we have here is packaging. We cannot rely on all consumers using Webpack. There are heaps of folks using bower, browserify, sprockets, plain old <script> tags. Real challenge is to find a universal solution that will not break existing developer's environment.
I definitely have some ideas how to solve this in a long term and will make some initial prototype hopefully quite soon.

Have you heard about the myth css preprocessor? www.myth.io
Whats your opinion on that?
Its supposed to work like a CSS polyfill, and it uses the W3C proposed syntax for future versions of CSS.

@jossmac could you clarify, please. are you going with radium or sticking with less? I'd personally favor radium now, but if you stick with less I will do the same. Thanks =)

With this tool it is possible to use css modules.
https://www.npmjs.com/package/css-modules-require-hook

@LorbusChris we'll likely transition the components to Radium when there's time, and like @TCMiranda mentioned leave CSS to do the things it's good at like resets, grids, etc.
The thing is we also maintain KeystoneJS and TouchstoneJS, not to mention the full-time commercial business Thinkmill.
So if you're up for it we welcome pull requests, but otherwise please be patient :smile:

N.B. this issues has been resolved so please continue any discussion related to CSS, LESS, Radium etc. over on #1

sure thing! Thank you @nkbt @jossmac


Use idiomatic new JS array immutable helpers

Fixes #138
Added toSorted, toReversed, toSpliced and with, per spec.
Which means moving sortInPlace to sort. Same for reverseInPlace -> reverse and spliceInPlace -> splice.
This is a small breaking change, thankfully caught by the type system, and by Core typing these mutable helpers' return as unit.
Did the same for TypedArray. Though its reverse and sort did return the array itself, so this breaking change should be carefuly advertized.
The toBla-ed naming convention seems to be the way to go in JS in the future. We should consider that for us as well. Otherwise we'd end up diverging more and more when JS releases more immutable helpers.

Ouf I think I committed a wrong draft. Thanks for catching these. Fixed.
I'll let others comment on these bigger philosophical decisions, but my personal opinions are:

There ought to be a guideline for what should be bound to, and whether it should be polyfilled

This'd create more discussions & scheduling around when to un-polyfill, which would create another round of surprises. Plus Node in the future. We should specify that we're binding to version X of node for example, but for browsers I don't think we should be in the game of watching and communicating these. It's much less surprising if it's a uniform, consistent message that we'll bind to what's landing in browsers, but the user's codebase's still responsible for polyfilling, which they might already do.

because the difference is only in return type the actual errors might be located far away from its cause

Yeah the error location is unfortunate, but I think that ship might have sailed when we decided to keep full inference instead of mandatory annotation at function boundary (to be clear I prefer the former); from here on it's all best-effort, and as long as it's communicated clearly in the changelog I'd say we'd done our job right.
(Btw there's the edge-case of polyfilling if we ever upgrade and change an API such that folks now need to polyfill, in which case I think we should definitely polyfill. But that doesn't seem likely)

The toBla-ed naming convention seems to be the way to go in JS in the future. We should consider that for us as well. Otherwise we'd end up diverging more and more when JS releases more immutable helpers.

Agreed. I am fine with these changes if they are clearly advertised in the CHANGELOG including a note regarding polyfilling.


[Feature] Math Formula LET

Initial checklist

[X] Is this really a problem?
[X] I have searched the Github Issues for similar issues, but did not find anything.

Problem
Formula LET is not implemented
Solution
Implement formula LET
Reference https://support.microsoft.com/en-us/office/let-function-34842dd8-b92b-4d3f-b325-b8b8f9908999
@Dushusir : I can solve it

implement


Data Volume grown when ran Compaction API

I observed like when I ran the compaction API , my data volume has grown up to 5-times more than that . I just wanted to know It is happening because of more metadata are getting added into file .?
Note : my retention period is less than 10 sec , So I deleted those files which has marked removed.

how are you measuring the data volume? sum total of all the files in the directory?

yes you right , before doing compaction , i checked the volume and after compaction I checked the volume . Could you please explain like why it grown-up .
Thanks,

I followed below step to reproduce
formed a delta lake from input of size 121 MB , It became 128MB.
Did some merge operation after that It became 180 MB (got so many small files).
Ran Vacuum API to delete those removed file , after that It became 157 MB.
Ran Compaction API, after that It became 478MB.
Ran Vacuum API to delete those removed file , after that It became 322 MB.

Delta using multi-version concurrency control, so it maintains data files for previous versions of the table. So when you are compacting, it writing new data files to create a new version of the table, but it is still keeping around the previous version's data files. Hence, just be directory listing, it will look like the size multiplied. But in reality, only some of the files are used by the latest version of the table, and in case of compaction, those latest version files should be the larger files.
To see the real data size of only the latest version, you should vacuum with 0 retention (with caution, see https://docs.delta.io/0.4.0/delta-utility.html#vacuum). So in your test, did you run vacuum with 0 retention?

Yes , I did it , if you see the above my steps which I followed ( step 3 and step 5), but even-though the size is more than 3-times.
Please explain me , if possible .

That is indeed pretty odd. How did you do the compaction? Can you share the code?
Also can you do something like a count before and after the compaction to double check that the compaction is correct?

SparkConf conf = new SparkConf().setMaster("local[*]").setAppName("SparkFileSumApp");
JavaSparkContext sc = new JavaSparkContext(conf);
SparkSession spark = SparkSession.builder().config(conf).getOrCreate();
DataFrameReader dataFrameReader = spark.read();
Dataset<Row> pData = dataFrameReader.parquet("/Users/kumars3/Documents/workspace-sts/espn-deltalake/input-data/3-sep/");
pData.write().mode("append").option("mergeSchema", "true").format("delta").save("delta-table/clickstream/");

Took Sample of 166MB of input data. : Total number Records : 1630168
Once Delta Lake formed It became of 176MB : Total number of Records : 1630168

This does not make sense to me.

Ran Compaction Now size became 781MB : Total number of records : 3260336 (double of original)
Your compaction code seems correct to me but how can it double the number of rows if you are overwriting the table. The only way that can happen is if instead of overwrite, you ran it in append mode, which would precisely duplicate the data.

Thats what I am doing . Please suggest , what can I do to figure it out .
One thing I noted like , if I keep the repartition count ( less than 10) , then size is getting increase comparatively if you keep  repartition count bigger . Could you explain the logic behind this .
Thanks

@tdas Could you please help me to figure it out the issue .? I am using above code for all my activities , will be great help to fix my issue . Unable to fix it .

@sanjiv1980

Try compression. e.g. snappy
Try sorting instead of doing repartition. (I used sort by uid on my dataset, it saves 10%)

Hi @sanjiv1980
After two years I might, can give you an answer.
The documentation example uses repartition instead of coalesce to decrease the number of partitions -> number of files.
repartition does full data shuffle and your data will be quite unsorted in a partition.

In general columnar storage formats like Parquet are highly sensitive when it comes to data distribution (data organization) and cardinality of individual columns. The more organized is data and the lower is cardinality the more efficient is the storage.

In this article it is well defined how data sorting affect the final size of your file.
close
Sources:
https://stackoverflow.com/questions/54218006/why-does-the-repartition-method-increase-file-size-on-disk
https://stackoverflow.com/questions/38153935/why-are-spark-parquet-files-for-an-aggregate-larger-than-the-original
https://mrpowers.medium.com/managing-spark-partitions-with-coalesce-and-repartition-4050c57ad5c4#.36o8a7b5j
https://towardsdatascience.com/merging-too-many-small-files-into-fewer-large-files-using-apache-spark-in-datalake-ff9a32807056
https://towardsdatascience.com/about-sort-in-spark-3-x-f3699cc31008
https://towardsdatascience.com/notes-about-saving-data-with-spark-3-0-86ba85ca2b71
https://towardsdatascience.com/best-practices-for-bucketing-in-spark-sql-ea9f23f7dd53


Use full error messages for unknown collection type

When misusing db.createCollection() the error message is meaningless to a novice user. improve this.

hm, for some reason this contains more than it should. Please cherrypick only my last commits
[ 5f48fdf692df11dbcc173e9a536df5972c154ab1 , 2041860fceab100f931bf51b21aad12ac6486c09, f52c004ab711110a2e8a941b764d9c75b2a43c2e ]
sorry for causing inconvenience.

I've also changed everything according to http://python-future.org/compatible_idioms.html - only the travis tests fail to pick the authentication values; which fails for me locally too. @brennv may hopefully better know how to fix this other than editing tests.js and putting the credentials in there? ;-)

I think we need to remove everything that relies on tests being executed as a main process so that tests.py looks like this:
https://github.com/brennv/pyArango/blob/db9f435aa911789cc574effd10c35a86595edda8/pyArango/tests/tests.py
I'll reopen this PR.

@brennv what would be the manual way to invoke the tests?
Btw, I've tried in tests.py:
if __name__ == "__main__" :
...
    import figleaf
   figleaf.start()

    unittest.main(exit=False)
    print("stopping!")
    figleaf.stop()

    figleaf.write_coverage('/tmp/.figleaf')

and generate the results:
figleaf2html -d ~/public_html/figleaf-output/ /tmp/.figleaf

(only works with python 2.7.8 for me... )
But gives a good picture which tests areproperly covered. Some itsy bitsy remaints are there, plus errors aren't tested in most cases.

Right now I'm running tests with python -m unittest discover pyArango/tests/

Me too. You can also just call python tests.py.


Mobile: White space in between black and red bars in header

Either make intentionally or fix the spacing for mobile header.

Addressed in release 0.3.1


change require - see deprecation

Noticed this on startup, looks like next/prefetch is being deprecated.
https://github.com/zeit/next.js/blob/540a86f007da211cd8aaea68ea50fd8739b3d3a4/lib/prefetch.js#L13

Thanks!


Choose the right kernel for this noisy training data set?

Hi, every one!
Currently I am working on Gaussian Process Prediction algorithms, I am a rookie for GP, so I have some questions here:
My dataset looks like this:

First, I started with normalization of data: new_y = (raw_y - mean_y)/std_y
Then, I choose Gaussian Likelihood and my kernel setting is : SE_cov + Periodic_cov + noise_cov
I used first 1000 points as training set and rest of points for prediction. But the result doesn't look good。
Is this because my data is with high noise? And what I can do to improve?
Thanks!

You should not use the white noise kernel, as the likelihood takes care of that. What measure do you use for the test error? What does the GP fit look like? What is the initialization of your lengthscale? Best would be to send this to the email list (see front page) with the code to reproduce a minimalistic example of your fit and error.

For such data an idea is to use a summation of kernels, e.g. SE + Matern3/2, where the SE is initialized with long lengthscale (smooth) and the Matern with short, therefore one capturing the long trend and the other explaining the "wiggliness".

@adamian Thanks for advice! My data is about the respiratory disease prevalence in time. I want to find the relationship between outpatient number and time. We could observe clear periodicity in data and slightly linear trend. I suspect one reason is because outpatient number is discrete, not continuous. That could be one reason explaining "wiggliness". Anyway, I will do as @mzwiessele suggested, send my questions to email list

Also the period of the periodic kernel can be a difficult parameter to learn. Maybe you should put the period close to the expected period at initialization.

hi @peiyaoli @adamian  @mzwiessele ,
I am doing some similar work of respiratory prediction. As I have large scale of data, therefore I split the data set into many pieces for training, i.e. shape = (10000 * 500), in which every sample contains about 5 respiratory cycles.
I also want to try kernel of ( SE + Periodic or Matern ). However, the GPy periodic kernels only allow input_dim = 1
Do you have any suggestion? thanks a lot.
Best Regards,
kingaza

Which GP model would you like to apply?
What is the input and output dimension of your dataset, respectively, please?

On 17 Sep 2018, at 23:59, kingaza<EMAIL_ADDRESS>wrote:
hi @peiyaoli @adamian @mzwiessele ,
I am doing some similar work of respiratory prediction. As I have large scale of data, therefore I split the data set into many pieces for training, i.e. shape = (10000 * 500), in which every sample contains about 5 respiratory cycles.
I also want to try kernel of ( SE + Periodic or Matern ). However, the GPy periodic kernels only allow input_dim = 1
Do you have any suggestion? thanks a lot.
Best Regards,
kingaza
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@mzwiessele
My case looks like auto regression, that predict the future about 1 second from history over a long time.
Given the sampling frequency is 20Hz, I will use the data of past 20 seconds for training. Therefore, the input and output dimensions are 400 and 20 respectively.
Actually I have not decided which kernel I shall apply. I try to follow the CO2 example in chapter 5, GPML, but it seems not work for my case.
So I would like to ask for any suggestion.
thanks again.
Best Regards,
kingaza


.5 zoom not working on iOS when pinch screen

Steps to Reproduce
Create a custom layout of Camerawesome:
CameraAwesomeBuilder.custom(
    builder: (cameraState, preview) {
      return cameraState.when(
        onPreparingCamera: (state) {
          return _buildLoadingInterface();
        },
        onPhotoMode: (picState) {
          return _buildInterface(picState);
        },
      );
    },
    previewFit: CameraPreviewFit.cover,
    sensorConfig: SensorConfig.single(
      sensor: Sensor.position(SensorPosition.back),
      flashMode: FlashMode.auto,
      aspectRatio: CameraAspectRatios.ratio_16_9,
    ),
    progressIndicator: _buildLoadingInterface(),
    saveConfig: SaveConfig.photoAndVideo(
      exifPreferences:
          ExifPreferences(saveGPSLocation: true),
      photoPathBuilder: (sensors) async {
        return await _cameraProvider
            .photoPathBuilder(sensors.first);
      },
      videoPathBuilder: (sensors) async {
        return await _cameraProvider
            .videoPathBuilder(sensors.first);
      },
    ),
  );

Expected results
In the initial camera state, if the device has the ultrawide sensor (0.5 zoom), if you pinch the screen, the camera should zoom out.
Actual results
It only works on Android. On iOS it works with the AwesomeZoomSelector widget.
Your flutter version
Flutter 3.22.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision b0850beeb2 (9 weeks ago) • 2024-07-16 21:43:41 -0700
Engine • revision 235db911ba
Tools • Dart 3.4.4 • DevTools 2.34.3

Same issue here


Catalog of My Things

Kanban Board
There are 3 Team Members and They are
Team # 1 @MenendezON
Team # 2 @Mahdi-Niazi
Team # 3 @Abdulwhbhussain.

Hi @Abdulwhbhussain, @MenendezON and @Mahdi-Niazi,
Good job so far!
Highlights!

Descriptive issue ✔

Hello ✋, you have done well reaching this point of the milestone 🤝 . But there are some issues that you still need to work on to go to the next project but you are almost there!
Status: Required Changes ♻⛔

[ ] Kindly split these tasks into their own issues. Each point on the list of requirements should have an issue for it.

[ ] Kindly give your tasks a more descriptive title. Titles like "Group task", and "Team member #1" are not descriptive.

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread and tag me @julie-ify if something is not 100% clear.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

I have made changes based on your request.

Hi Team,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights

good job implementing the requested changes.

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Add a informational banner on Try it to direct users to GE main site.

We can have the messaging as:
"To experience more functionalities, please access the main Graph Explorer site here"
Make "here" a link to the main Graph Explorer site.


fix indexOfBounds bug

Guidelines
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce?

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

Preparing a pull request for review
Ensure your change is properly formatted by running:
$ ./gradlew spotlessApply

Please correct any failures before requesting a review.

LGTM! 👍
Thanks for your contribution :)

You are welcome ;)
Can close this issue)
https://github.com/skydoves/PowerSpinner/issues/66
And maybe you build minor releaze with this fix?
P.S. I found another height issue.
When a new size is set, and it is larger than the previous one, the recycler retains the old height, it may be that the height of 1 element remains and there will be scrolling inside this window. This is not very convenient, in my project I made a crutch and when setting the value, I simply set the height equal to the element's height multiplied by 6 (I think this is the optimal value that fits well under any screens).

@umbrellait-dmitry-volkov
Thanks for your contribution.
That issue can be resolved if we find measuring the exact size of the recyclerView before inflation on the PopupWindow.
Currently, it applies the static initial size of the height of the recyclerView.


improved tea reference

修改 Tea 的引用版本至0.0.9

Codecov Report

Merging #109 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #109   +/-   ##
=======================================
  Coverage   95.79%   95.79%
=======================================
  Files          12       12
  Lines         690      690
  Branches       48       48
=======================================
  Hits          661      661
  Misses         27       27
  Partials        2        2

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 e4aee53...d4aefe8. Read the comment docs.