Try Python 3.10

I'm not sure what the problem is, but it seems wrong that there are no py310 wheels in the dipy 1.5 list here:
https://anaconda.org/conda-forge/dipy/files

https://github.com/conda-forge/dipy-feedstock/pull/39#issuecomment-1066920757

@hoechenberger can you try removing dipy from the installer in this PR temporarily? That way we can see if https://github.com/conda-forge/dipy-feedstock/pull/40 is likely to fix things here or if there are other things that we need to figure out...

@larsoner It's actually a dependency of mne but I think we can force-exclude it, yes. Will try…

Ok there's still a problem, I'm canceling the CI run

@larsoner Let's wait until the dipy package is up and then retry, I'm not too sure about the exclude parameter I've just added.
If things still fail with a fresh dipy, we can start to dig deeper.

@larsoner Ah, in fact, I believe exclude only means that those packages won't be shipped with the installer, however it does not mean that they're excluded from the dependency resolution procedure that has to run before the installers are actually being created. So this was not the right approach anyway.

The mne-base approach should work though, right? I can make a PR if you are working on instructions

@larsoner Yes you can do it, but I don't think it's time-efficient … I'd just wait until the new dipy packages are up and then restart CI here
But feel free to do it if you're impatient :)

@larsoner WE'RE GREEN 💚


Put up basic about page

Create a basic About page with words from Isabelle Young

actually this should be in ghu_main heck

heck it we'll keep all issues here


Introducing Module-NMC controller

This PR introduces a new controller, that is responsible for reconciliation of NMC based on the data in Module and Node The following are the main points:

It watches for changes in Modules, Nodes (labels, becoming
schedulable) and Jobs belonging owned by Modules (in order to
reschedule once Build/Sign job are finished)
Per reconciled Module, go over all the nodes in the cluster
and reconcile their NMCs based on the Module/Node state

Changes in the PR:

adding functions to filter package that are resposible for filtering
the events (nodes. modules, jobs) and finding out which modules
should be reconciled
changing the NMC handler logic a little, adding verification for
container image presence in case module should be enable.
Module-NMC Reconciliation is being done both in case Kernel Mapping
exists and in case it does not exists ( solves the garbage
collection flow)

This PR does not include Module status updates based on NMC updates

/assign @ybettan

/assign @qbarrand

/test pull-kernel-module-management-unit-tests

/lgtm

/lgtm


Updating application disables the implicit and code grant types

Description:
while updating application in store UI by default below grant types are getting disabled, which are enabled after creating an application

Implicit
code

Suggested Labels:
APIM-2.1.0
Suggested Assignees:
Affected Product Version:
APIM 2.1.0
OS, DB, other environment details and versions:
Steps to reproduce:
Below are the steps performed
1)After creating application enabled below two grant types and callback URL is updated
Grant: implicit, code
2)Next Editing the application without touching any field and just clicked on update
3)After updating the application the particular grant types are getting disabled by default

Fixed in https://github.com/wso2/carbon-apimgt/pull/5335


[Req]: More data in Config JSON File

Contact Details
<EMAIL_ADDRESS>Explain the proposed feature
As of now, there is some static data in the file and I want it to be inside JSON file. To implement this feature, the first step would be to locate all the static data in the file. This can be done manually by reviewing the file and identifying any static data, or it can be done automatically using a tool or script to search for and identify static data. Once all the static data has been identified, it can be converted to a JSON file format and stored in a JSON file
Explain the possible use cases for the feature
The Static Data to JSON File Conversion can help improve the efficiency, organization and access of data for easier editing.
Any other details you would like to provide?
This is a simple task but due to amount of time required to cover all static data, I'll assign it Intermediate.

@TechSpiritSS May i give it a try to resolve it?

Sure 🚀

Are you still working on this?

Are you still working on this?

Yeah!! Will push a PR ASAP.

Are you still working?

Are you still working?

Yes!! Will push the PR now.

Can you assign this issue to me, If not completed?

Hey, can I do this? I already moved the neofetch data to config.js in my PR #146. I can move all the data to a JSON file?

For reference, here is the exact commit: here

I will fix this issue on Monday.


Update MD file on new branch 2017-11-08_04-22-25

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/content1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Include any directory queried via ConfigurableFileTree at configuration time in configuration cache fingerprint

Fixes #?
Context
This PR is a first step in treating file system state queried using the FileCollection APIs at configuration time as inputs to the configuration state. This PR instruments the query methods of ConfigurableFileTree. A later PR will instrument the remaining implementations.
Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation

@bot-gradle test and merge

I've triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

I've triggered a build for you.


Tear-down address observations properly

namerd's thrift interface has no mechanism to release observations. This is
troublesome, because there is no way to obtain a reference to a new address
if a service is deleted and re-created.
In order to fix this, we simplify the thrift interface in the following ways:

Do not cache Addr observations when bind-ing a name.
Bind concrete names passed to the addr call if not cached.
addr observations now take NameTree state into account.  When a concrete
name becomes anything other than a NameTree.Leaf, its observation is torn
down and removed from cache.

Fixes #237

It occurs to me that the namerd annotations should be thrift-specific since there are other namerd servers.  Let's do that separately.

@adleong https://github.com/BuoyantIO/linkerd/pull/246/commits/bc3061625cb243e1601dda04196b819e61276125 alters addr resolution to skip delegation entirely so that we have a safeguard against user-provided dtabs interfering with addr binding.  This approach isn't set in stone -- let's weigh our options.

I think I like this.  Seems like a nice separation of concerns.  Skipping delegation on the addr call makes perfect sense to me.

:star: 👓

:star: looks nice, although git's diff really makes this a difficult read :disappointed: . I'd feel more confident if there was a regression test, but don't worry if it's a pita

@esbie good point.  the thrift tests are slightly unwieldy but I'll at least give it a try.  maybe i can make them less unwieldy, even

simplified tests ThriftNamerInterface addr tests and added a test that properly reproduces this issue (i.e. fails as expected against master and passes on this branch).

:star: :leaves: :fallen_leaf:


Statistical functions fail with dask

xclim version: 0.33 (bug is there since 0.32)
Python version: 3.9
Operating System: Linux

Description

The recent use of xarray.apply_ufunc to vectorize statistical functions (like fit) is incomplete in that there are missing parameters to fully run this with dask-backed arrays.
What I Did

import xclim as xc
from xclim.testing import open_dataset

ds = open_dataset('ERA5/daily_surface_cancities_1990-1993.nc')
xc.land.fit(ds.pr.chunk({'location': 1}))

What I Received

---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-4-b50a25471104> in <module>
----> 1 xc.land.fit(ds.pr.chunk({'location': 1}))

~/Python/xclim/xclim/core/indicator.py in __call__(self, *args, **kwds)
    788             elif nm not in compute_das and nm in params:
    789                 kwargs[nm] = params[nm]
--> 790         outs = self.compute(**compute_das, **kwargs, **var_kwargs)
    791
    792         if isinstance(outs, DataArray):

<boltons.funcutils.FunctionBuilder-156> in fit(da, dist, method, dim, **fitkwargs)

~/Python/xclim/xclim/core/units.py in wrapper(*args, **kwargs)
    688                 check_units(val, bound_units.arguments.get(name, None))
    689
--> 690             out = func(*args, **kwargs)
    691
    692             # Perform very basic sanity check on the output.

~/Python/xclim/xclim/indices/stats.py in fit(da, dist, method, dim, **fitkwargs)
    115     dist_params = shape_params + ["loc", "scale"]
    116
--> 117     data = xr.apply_ufunc(
    118         _fitfunc_1d,
    119         da,

~/.local/lib/python3.9/site-packages/xarray/core/computation.py in apply_ufunc(func, input_core_dims, output_core_dims, exclude_dims, vectorize, join, dataset_join, dataset_fill_value, keep_attrs, kwargs, dask, output_dtypes, output_sizes, meta, dask_gufunc_kwargs, *args)
   1163     # feed DataArray apply_variable_ufunc through apply_dataarray_vfunc
   1164     elif any(isinstance(a, DataArray) for a in args):
-> 1165         return apply_dataarray_vfunc(
   1166             variables_vfunc,
   1167             *args,

~/.local/lib/python3.9/site-packages/xarray/core/computation.py in apply_dataarray_vfunc(func, signature, join, exclude_dims, keep_attrs, *args)
    288
    289     data_vars = [getattr(a, "variable", a) for a in args]
--> 290     result_var = func(*data_vars)
    291
    292     if signature.num_outputs > 1:

~/.local/lib/python3.9/site-packages/xarray/core/computation.py in apply_variable_ufunc(func, signature, exclude_dims, dask, output_dtypes, vectorize, keep_attrs, dask_gufunc_kwargs, *args)
    700             for key in signature.all_output_core_dims:
    701                 if key not in signature.all_input_core_dims and key not in output_sizes:
--> 702                     raise ValueError(
    703                         f"dimension '{key}' in 'output_core_dims' needs corresponding (dim, size) in 'output_sizes'"
    704                     )

ValueError: dimension 'dparams' in 'output_core_dims' needs corresponding (dim, size) in 'output_sizes'

Solution
This block : https://github.com/Ouranosinc/xclim/blob/f29edd04e663905f027a289a84ab518641188e48/xclim/indices/stats.py#L117-L132
is missing :
    dask_gufunc_kwargs={'output_sizes': {'dparams': len(dist_params)}},

and a dask-backed test as well!
More
I put 0.34 as a milestone, but one might argue that this merits a bugfix release, 0.33.1?

I put 0.34 as a milestone, but one might argue that this merits a bugfix release, 0.33.1?

If this is the case, we can solely update pre-commit hooks and push something that still supports Python3.7. Let me know.


Fix bookdown rendering

Getting this error on call bookdown::render_book("index.Rmd")
Error in x[i] <- sprintf("<a href=\"%s#%s\"", filenames[which.max(lines[lines <=  :
  replacement has length zero

Neither editing the contents of index.Rmd to bare minimum, removing _output.yml, nor excluding all body .Rmds helps.

Seems to work again?


Added suspendable property resolvers

Coverage decreased (-0.1%) to 87.511% when pulling be6327c3e715fe6d64428bdc87ee1701e07abcb4 on jeggy:master into 15262db356c82a7be77bd4147a00b6cc14c387f3 on pgutkowski:master.

Figured it wasn't this simple to implement this. Opened issue #38


Feature/275 masstransit rabbitmq

**Closes #275 **

Host & client projects for masstransit rabbitmq. And example project. Readme's are in the src projects.

PR Checklist

[x] Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
[x] Based off latest main branch of toolkit
[x] PR doesn't include merge commits (always rebase on top of our main, if needed)
[x] New integration

[x] Docs are written
[x] Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)

[ ] Tests for the changes have been added (for bug fixes / features) (if applicable)
[x] Contains NO breaking changes
[x] Every new API (including internal ones) has full XML docs
[ ] Code follows all style conventions

Other information

Contributor @dotnet-policy-service agree

Hi @MichielBrys , I noticed the AddMassTransitClient and I was just wondering what would happen if, in the future we also have Aspire packages for other transports like Service Bus for example.
Maybe it could be named AddMassTransitRabbitMqClient in order to not make it ambiguous?

Can you explain what this solution adds on the ease of use as compared to https://github.com/anoordover/MassTransitJobConsumer?
What would the impact of using this component be for my example?

Thanks for the reviews, I read them and indeed realised the hosting package isn't doing anything extra so I got rid of it. Currently only have the client which uses the connection string from the .AddRabbitMQ().
I also fixed the nuget versioning to use the Directory.Packages.props file.

Thanks for the reviews, I read them and indeed realised the hosting package isn't doing anything extra so I got rid of it. Currently only have the client which uses the connection string from the .AddRabbitMQ().
I'm thinking it would be pretty usefull to have in the community toolkit and I'd like to expand it to support all the implementations that work with masstransit so people have a nice wrapper to use with aspire to easily set up masstransit
I also fixed the nuget versioning to use the Directory.Packages.props file.

Given that it doesn't provide any functionality over the standard RabbitMQ integration, I don't see that there's a need for the hosting integration.
The client integration should be able to use the connection string provided by the standard RabbitMQ integration just fine.

Thanks for the reviews, I read them and indeed realised the hosting package isn't doing anything extra so I got rid of it. Currently only have the client which uses the connection string from the .AddRabbitMQ().
I'm thinking it would be pretty usefull to have in the community toolkit and I'd like to expand it to support all the implementations that work with masstransit so people have a nice wrapper to use with aspire to easily set up masstransit
I also fixed the nuget versioning to use the Directory.Packages.props file.

Given that it doesn't provide any functionality over the standard RabbitMQ integration, I don't see that there's a need for the hosting integration.
The client integration should be able to use the connection string provided by the standard RabbitMQ integration just fine.

Agreed its the client package I meant that could be nice to have in the toolkit, the hosting one I already removed yesterday.

Also, can the examples be moved into a sub-folder of examples, such as examples/masstransit-rabbitmq (and a solution folder to match), so that it's consistent with the others.

Could someone merge the pr? I don't have write access I think. Thanks :)

Yeah. CodeQL didn't run for some reason so I'll have to override that to merge.

I merged locally (wanted to do a few bits of tidying up) and it looks like it's freaked out this PR a little, so I'll close the PR as everything is already in the main branch.
Should be live on NuGet soon.


[📊 DATA] Check Likehoood Bots Are Coming to Vulnerabile Stamps like NEAR Social Check, 5 Accoutns Connected

Description
Objective / Business Insight

have nadabot working
=revent from donating through quadratic funding round

Acceptance Criterion

[] ways to check if a thing is getting botted
did the account just get made
does the name follow autogenerated nomenclature
are the links to the social link valid or also autogenerated
is the description seem like autogenerated patterns
did they use an ipfs upload image or an existing link, twitter link is more highly likely https://pbs.twimg.com/
does their profile names see augenerated
if account got created and all came from similar wallet

Data Sources
= query social.near contract

query other contracts they have interacted with
-query speed in which verify on contract and add stamp happened
query how much funds was orignally put on
query source of funds if about to donate to a subaccount under v1.potfactory.potlock.near (active round example build.v1.potfactory.potlock.near)
nadabot contracts is v1.nadabot.near, and they all the sybil rpoviders are nameofcontract:method, so we can query the contracts to see who is calling it

Similar Queries
Challenges
Resources
How to Present

[https://flipsidecrypto.xyz/sunxian2000/2024-03-26-01-54-pm-72XMPB]
not sure if I am doing the right thing, I tried to find the contract that botted accounts interacted with and the total deposit.


Expose Language Features

I've done this personally for my own project, but I think that it would be useful to expose language features from the different monaco-* packages. For example, in my project in particular, I've implemented a similar "problems" list to vscode. I cloned the monaco-typescript project and exposed the features, which has helped for instances where I wanted to use the DiagnosticsAdaptor or the CodeActionAdaptor instead of implementing essentially the same logic. Currently, I don't believe there is a method to import/utilize these methods in the current monaco-editor.
I can submit a pull request for monaco-typescript if it is found useful for others.

@StefanRetief I think the demand is there given #1885 though I'm not positive if what you are proposing is the same as what's described in that other issue.

@rcjsuen I believe this might be slightly different? From what I can tell (and I could be completely off here), they are describing being able to communicate directly with the worker here: https://github.com/microsoft/monaco-html/blob/master/src/htmlWorker.ts. I'm proposing something a little different, as exposing the methods/classes here: https://github.com/microsoft/monaco-html/blob/master/src/languageFeatures.ts

@StefanRetief Yes, I see what you mean. The two pieces are related but serve two different purposes.


Will we get events as well?

To be able to listen to in plugins. Stuff like "on new layer created", "on symbol renamed", etc. ? Or is that too much regarding performance (which is hanging by a thread as it is ;) ).

There's already an Actions API. See an example at http://developer.sketchapp.com/examples/plugins/selection-changed/, and a list of events at http://developer.sketchapp.com/reference/action/ : )

Very cool stuff, but what I meant was, will this JS wrapper provide some api for those events as well? Or is that a silly question :)

Events are dealt with in a plugin's manifest.json file, so they don't really care whether your script uses the JS API or the old style : )

Ah, didn't know that. Good to know thanks.

technically the API will likely need a pub/sub event model. For instance pumping an event to ReloadInspector once you adjust a SharedStyle .. that or invoke an event to Sync sharedstyles via code.


[Bug] forbidden create materialized view with distinct

Search before asking

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

Version
0.15
What's Wrong?
when user create materialized view with distinct, the materialized view can be created. it is not fit for the current condition, because  it is not can be used and doris does not suppot create materialized view for count distinct. so should forbid the operator.
What You Expected?
we should forbid the operator when user create materialized view for count distinct.
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

This pr #7494 prohibits the distinct semantics that may appear in aggregate functions.
For example, select count(distinct c1) from table1
But there is another situation that is distinct in the select item.
For example, select distinct c1, c2 from table
And this situation can actually be supported. It is equivalent to select c1, c2 from table group by c1, c2.
Can you help us add this part of the changes in the follow-up pr?

This pr #7494 prohibits the distinct semantics that may appear in aggregate functions. For example, select count(distinct c1) from table1
But there is another situation that is distinct in the select item. For example, select distinct c1, c2 from table And this situation can actually be supported. It is equivalent to select c1, c2 from table group by c1, c2. Can you help us add this part of the changes in the follow-up pr?

ok，i would commit follow-up pr to improve the function，thanks.


bio-gappa: init at 0.8.4

Description of changes
Package for a tool that is used into my HPC center.
Actively in contact with the upstream Author (see https://github.com/lczech/grenedalf/issues/19)

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[X] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

1 package built:

bio-gappa

The " bio-gappa.passthru.tests on aarch64-darwin" is stuck since more than a month ago. What should we do?

@ofborg bio-gappa.passthru.tests on aarch64-darwin

@ofborg bio-gappa.passthru.tests

Maybe asking ofborg to build passthru again will help :sweat_smile:

@ofborg build bio-gappa.passthru.tests


Tests/improve-windows

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

14 of 14 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
769

Relevant Lines:
769

💛  - Coveralls


C100 bug fix

JIRA link (if applicable)
Change description
Bug fixes for c100
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Closing as not required.


Your Demo isn't working!

It says "Graph returned an error: (#10) This endpoint requires the 'manage_pages' permission or the 'Page Public Content Access' feature. Refer to https://developers.facebook.com/docs/apps/review/login-permissions#manage-pages and https://developers.facebook.com/docs/apps/review/feature#reference-PAGES_ACCESS for details."
Which brings me to the next point, could you update your documentation to outline precisely what facebook application permissions are required? For example, aside from the manage_pages and page public content access, do we need additional login permissions, for example if we want visitors to post comments on the video's?

I thought I set it up how Facebook wants it but apparently not. I'll do my best to work on when I have time but I can't promise that will be soon.
I'd be more than happy to take a pull request.
Also a question: Who this be just as useful if I rewrote it in Javascript?


0.4.0 release

The latest tagged release was 0.3.0 which happened around October 2020.
It would be nice to get a newer release given that the development has been relatively active since then.

Released.


[#Wave-Control: Add NetSuite] Settings Configuration in NewDot: Advanced

Tracking Issue: https://github.com/Expensify/Expensify/issues/377671
Design Doc Section: https://docs.google.com/document/d/1WubNv_VAv78IxG4FKsi9aS0pWESfWvUYbqBAAy5b4bc/edit#heading=h.1vf74ijo8qpn

(High-Level Section)
Routes

Route: /settings/workspaces/{policyID}/accounting/netsuite/advanced

PageComponent: NetSuiteAdvancedPage
Calls / Parameters:

Auto-sync

Calls UpdateNetSuiteAutoSync
Parameters:

enabled - TRUE / FALSE, depending on the toggle

Config that will be affected - config.syncOptions.hasChosenAutoSyncOption
The pendingAction for the OfflineWithFeedback component will be policy.pendingFields.syncOptions

Sync reimbursed reports

Calls UpdateNetSuiteSyncReimbursedReports
Parameters:

enabled - TRUE / FALSE, depending on the toggle

Config that will be affected - config.syncOptions.syncReimbursedReports
The pendingAction for the OfflineWithFeedback component will be policy.pendingFields.syncOptions

Invite employees and set approvals

Calls UpdateNetSuiteSyncPeople
Parameters:

enabled - TRUE / FALSE, depending on the toggle

Config that will be affected - config.syncOptions.syncPeople
The pendingAction for the OfflineWithFeedback component will be policy.pendingFields.syncOptions

Auto-create employees/vendors

Calls UpdateNetSuiteAutoCreateEntities
Parameters:

enabled - TRUE / FALSE, depending on the toggle

Config that will be affected - config.autoCreateEntities
The pendingAction for the OfflineWithFeedback component will be policy.pendingFields.autoCreateEntities

Enable newly imported categories

Calls UpdateNetSuiteEnableNewCategories
Parameters:

enabled - TRUE / FALSE, depending on the toggle

Config that will be affected - config.syncOptions.enableNewCategories
The pendingAction for the OfflineWithFeedback component will be policy.pendingFields.syncOptions

Route: /settings/workspaces/{policyID}/accounting/netsuite/advanced/reimbursement-account/select

PageComponent: NetSuiteReimbursementAccountSelectPage
API Call/Parameters:

UpdateNetSuiteReimbursementAccountID

Parameters:

bankAccountID - one of the payable accounts available (present under data.payableList)

Config that will be affected - config.reimbursementAccountID
The pendingAction for the OfflineWithFeedback component will be policy.pendingFields.reimbursementAccountID

Route: /settings/workspaces/{policyID}/accounting/netsuite/advanced/collection-account/select

PageComponent: NetSuiteCollectionAccountSelectPage
API Call/Parameters:

UpdateNetSuiteCollectionAccount

Parameters:

bankAccountID - one of the payable accounts available (present under data.payableList)

Config that will be affected - config.collectionAccount
The pendingAction for the OfflineWithFeedback component will be policy.pendingFields.collectionAccount

Route: /settings/workspaces/{policyID}/accounting/netsuite/advanced/report-approval-level/select

PageComponent: NetSuiteExpenseReportApprovalLevelSelectPage
API Call/Parameters:

UpdateNetSuiteExportReportsTo

Parameters:

value - one of the values in ExpenseReportApprovalLevelTypeEnum (REPORTS_APPROVED_NONE, REPORTS_SUPERVISOR_APPROVED, REPORTS_ACCOUNTING_APPROVED, REPORTS_APPROVED_BOTH)

Config that will be affected - config.syncOptions.exportReportsTo
The pendingAction for the OfflineWithFeedback component will be policy.pendingFields.syncOptions

Route: /settings/workspaces/{policyID}/accounting/netsuite/advanced/vb-approval-level/select

PageComponent: NetSuiteVendorBillApprovalLevelSelectPage
API Call/Parameters:

UpdateNetSuiteExportVendorBillsTo

Parameters:

value - one of the values in VendorBillApprovalLevelTypeEnum (VENDOR_BILLS_APPROVED_NONE, VENDOR_BILLS_APPROVAL_PENDING, VENDOR_BILLS_APPROVED)

Config that will be affected - config.syncOptions.exportVendorBillsTo
The pendingAction for the OfflineWithFeedback component will be policy.pendingFields.syncOptions

Route: /settings/workspaces/{policyID}/accounting/netsuite/advanced/je-approval-level/select

PageComponent: NetSuiteJournalEntryApprovalLevelSelectPage
API Call/Parameters:

UpdateNetSuiteExportJournalsTo

Parameters:

value - one of the values in JournalEntryApprovalLevelTypeEnum (JOURNALS_APPROVED_NONE, JOURNALS_APPROVAL_PENDING, JOURNALS_APPROVED)

Config that will be affected - config.syncOptions.exportJournalsTo
The pendingAction for the OfflineWithFeedback component will be policy.pendingFields.syncOptions

Route: /settings/workspaces/{policyID}/accounting/netsuite/advanced/approval-account/select

PageComponent: NetSuiteApprovalAccountSelectPage
API Call/Parameters:

UpdateNetSuiteApprovalAccount

Parameters:

value - one of the payable accounts available (present under data.payableList) or APPROVAL_ACCOUNT_DEFAULT

Config that will be affected - config.approvalAccount
The pendingAction for the OfflineWithFeedback component will be policy.pendingFields.approvalAccount

Refer to here and here in order to get the corresponding routes and parameters.
We'll discuss the Export and Advanced Sections together, as these are very similar in design.
The set of pages needed for the export configurations is similar to that for the import configurations.
The first part “UI Components” explains the UI components and their arrangement on the pages. The second part, “Data Retrieval,” discusses how data or options displayed on the pages are fetched or retrieved.
UI Components
We need two types of pages for configuring export/advanced settings. The first type of page displays menu items, each representing a setting that can be configured. When clicked or pressed, it navigates to a configuration detail page. This is the second type of page. On the configuration detail page, the user can edit the chosen configuration.
Menu Items Page

Configuration Detail Page

This section UI Components will be divided into two subsections: Menu Items Page, explaining the first type of screen, and Configuration Detail Page, explaining the second.
Menu Items Pages
NetSuiteAdvancedPage

Configuration Detail Page
The other page type is the Configuration Detail pages. On a Configuration Detail page, users can alter a configuration by selecting from various options or toggling a specific item.
When an option item is selected, a function corresponding to the Selector Page from policy.ts should be invoked to update the connection configuration data. For more information about the API, please refer to the “Saving Connection Settings” section.
We’ll reuse the SelectionScreen component to render the option list. You can find an example of its implementation here.
Data Retrieval
On all pages related to export configuration, we need access to the current configuration. This information is stored in Onyx as part of the policy object, all pages need to subscribe to it.
export default withPolicy()(ComponentForPage);

The Menu Items pages display the preset list of items. Each item of the list is a pair of the configuration item (ex. Preferred exporter) and the current configuration value for the item (ex. The email of the admin who is used as the preferred exporter). The items are static and the values are simply read from the policy object that is provided by Onyx subscription.
For Configuration Detail Pages, we will subdivide the pages into 2 categories:

Static Options Page
Dynamic Options Page

Static Options Pages display a preset list of options, i.e., they do not depend on the current data stored in the policy. In this category of pages, the policy data will only be used to determine the currently selected option (initiallyFocusedOptionKey). The pages that fall under this category are -

NetSuiteDateSelectPage
NetSuiteExportExpensesDestinationSelectPage
NetSuiteExportExpensesJournalPostingPreferenceSelectPage
NetSuiteInvoiceItemPreferenceSelectPage
NetSuiteExpenseReportApprovalLevelSelectPage
NetSuiteVendorBillApprovalLevelSelectPage
NetSuiteJournalEntryApprovalLevelSelectPage

Dynamic Options Pages are the pages where we show a list of options dynamically, i.e., they depend on current data stored in the policy. In this category of pages, the policy data will be used to determine the set of options being shown to the user and the currently selected option (initiallyFocusedOptionKey). The pages which fall under this category are:

NetSuitePreferredExporterSelectPage
NetSuiteExportExpensesVendorSelectPage
NetSuiteExportExpensesPayableAccountSelectPage
NetSuiteReceivableAccountSelectPage
NetSuiteInvoiceItemSelectPage
NetSuiteTaxPostingAccountSelectPage
NetSuiteProvicincialTaxPostingAccountSelectPage
NetSuiteReimbursementAccountSelectPage
NetSuiteCollectionAccountSelectPage
NetSuiteApprovalAccountSelectPage

Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @shubham1206agra
Issue OwnerCurrent Issue Owner: @shubham1206agra

@shubham1206agra is almost done with Export and will be moving onto this one shortly.

We're paying @mananjadhav and @shubham1206agra holistically for the entire project, so closing this out


Re-add readme

Overview
Hopfully re-add README to released package, by updating semantic-release.

Testing recommendations

Publish it.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: add ERC721 token standard

Depends on https://github.com/paulrberg/prb-contracts/pull/32.

[x] feat: add ERC721 token standard
[x] build: update git submodules
[x] test: ERC721 contract

Due to too many git conflicts I'm closing this PR in favor of https://github.com/paulrberg/prb-contracts/pull/34.


net: don't keep reading from UDP resolver after truncated packet

When the host or dig programs see a malformed packet from a resolver when using UDP, they fall back to using TCP.  The net package resolver does not do this; it simply ignores the malformed packet (in (*dnsPacketConn).dnsRoundTrip in net/dnsclient_unix.go).  This was done for #13281.  I suggest that we do the same.
This is showing up right now for me when I run go test -test.run=TestLookupLongTXT net.  I see this:
--- FAIL: TestLookupLongTXT (10.00s)
	lookup_test.go:334: lookup golang.rsc.io on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:39779-><IP_ADDRESS>:53: i/o timeout
FAIL
FAIL	net	10.023s

If I run dig -t txt golang.rsc.io the output starts with
;; Warning: Message parser reports malformed message packet.
;; Truncated, retrying in TCP mode.

I suggest that we keep the current behavior for the !resp.IsResponseTo(query) case but change the behavior for an Unpack failure to drop right back to TCP.
CC @mdempsky

This should be re-checked given the work done for #21160.

See also #22857.

CC @mikioh @iangudger

With the new DNS client, the chances of truncated DNS messages causing problems is greatly reduced, not not eliminated. I believe that now in cases where not all answers are contained in the read UDP message we will either try another DNS server or error out. I agree that trying TCP would be better, but at least failing fast is better than waiting for a timeout.


Add Bucket of XP

Describe the your request
Hey, I was wondering if it was possible to make the liquid xp from this mod able to be spouted out into a bucket?
This way for other mods that require a bucket of liquid xp for a crafting recipe, one can just have one system for getting buckets of liquid xp as opposed to having this for just enchanting books/armor/weapons/tools.
One notable mod for this would be Mob Grinding Utils and their chicken feeds for making Dreadful Dirt or Delightful Dirt.
I could get the buckets by using that mods xp drain and getting the buckets that way, but if I already have a setup for this mod to drain my xp into a big tank, why not allow us to pump it into a spout and then into buckets for crafting use?
Thanks for considering :)

Please use Bottle O' Enchant (bottled exp). We do not consider bucket of exp because exp container already exists.


 When the website is deployed there is the following console message:
4:18:09 PM:  ==== PROCESSING  hugo-bingo  ======
4:18:09 PM: Building site for theme hugo-bingo using default content to ../themeSite/static/theme/hugo-bingo/
4:18:10 PM: Error: Error building site: failed to render pages: render of "home" failed: "/opt/build/repo/hugo-bingo/layouts/index.html:13:27": execute of template failed: template: index.html:13:27: executing "main" at <partial $path (dict "class" "social-media-icon")>: error calling partial: partial "social-icons/%!s(<nil>).svg" not found
4:18:10 PM: FAILED to create exampleSite for hugo-bingo

The .svg file that you reference under line 12 `/layouts/index.html does not exist in the theme repo.
Either add the .svg file or remove the reference.
Once you do the above feel free to close this issue.
Also note that once gohugoio/hugoThemes#668 is addressed you will need to keep an eye on whether the Bingo theme demo generates on the Hugo website.
We are a very small team and we just cannot keep up opening issues in the various theme repositories. Whenever a theme demo breaks and remains broken for a while, then at some point it will be removed from the list without prior warning.
Thank you.
cc: @digitalcraftsman

Thanks for reporting the issue. I'll fix it ASAP. 🙇


Upgrade Linux Kernel for flatcar-3602 from 5.15.129 to 5.15.130

Subject says it all.

See instead https://github.com/flatcar/scripts/pull/1119


Need ability to store Recommendations through DB with published schema

As a Backend Engineer,
I need to be able to store recommendations
so that Users/customers can interact seamlessly and effectively with our recommendation system.
Details & Assumptions:

Our choice of database is PostgreSQL

Acceptance Criteria:

Primary keys and foreign keys should be explicitly stated.
Duplication of records should be avoided.
The database model should be designed for scalability

Hey team! Please add your planning poker estimate with Zenhub @christyekim @olluyeancah @andersonnyc @jrubnitz

Scrum Master’s Note from Backlog Refinement Meet:
Finalized label, estimate, and sprint assignment as discussed during meeting

Add details on keys

Updated the description to include DB schema and list of supported methods

Test Report:
Test Flask CLI Commands

It should call the db-create command

Test Cases for Recommendation Model

It should Create a Recommendation and add it to the database
It should Create a Recommendation and assert that it exists
It should Delete a Recommendation
It should deserialize a Recommendation
It should not deserialize a bad bought_in_last30d attribute
It should not deserialize bad data
It should not deserialize a bad recommendation_type attribute
It should not deserialize a bad viewed_in_last7d attribute
It should not deserialize a Recommendation with missing data
It should Find Recommendations after last_relevance_date
It should Find Recommendations by bought_in_last30d
It should Find Recommendations by last_relevance_date
It should Find Recommendations by Product ID
It should Find Recommendations by recommendation_type
It should Find Recommendations by User ID
It should Find a Recommendation by User Segment
It should Find Recommendations by viewed_in_last7d
It should Find a Recommendation by ID
It should Find a Recommendation by ID or return 404_NOT_FOUND if not found
It should return 404_NOT_FOUND for ID not found
It should List all Recommendations in the database
It should Read a Recommendation
It should serialize a Recommendation
It should Update a Recommendation
It should Not Update a Recommendation with no ID

Recommendation Server Tests

It should be healthy
It should call the Home Page

Name                               Stmts   Miss  Cover   Missing
service/init.py                   18      3    83%   31-34
service/common/cli_commands.py         7      0   100%
service/common/error_handlers.py      38     19    50%   32, 38-40, 51-53, 62-64, 77-79, 92-94, 107-109
service/common/log_handlers.py        11      1    91%   35
service/common/status.py              45      0   100%
service/config.py                      5      0   100%
service/models.py                    119      0   100%
service/routes.py                     14      1    93%   54
TOTAL                                257     24    91%
Ran 28 tests in 0.694s
OK
App Summary on Browser:
{
"name": "Recommendations REST API Service",
"paths": "http://<IP_ADDRESS>:8000/recommendations",
"version": "1.0"
}


Upgrading to version 0.26.0 breaks PV access

Suspect that this is possibly the result of https://github.com/coreos/prometheus-operator/pull/2109
What did you do?
Upgraded from prometheus-operator v0.25 to v0.26
What did you expect to see?
Prometheus pods should come up with Prometheus v0.25
What did you see instead? Under which circumstances?
Pods crashlooping with
level=error ts=2018-11-30T13:20:02.660393999Z caller=main.go:625 err="opening storage failed: open /prometheus/wal/00000949: permission denied"

This may be only apparent when using persistent volumes
Environment
Azure

Prometheus Operator version:

v0.26

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:46:06Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.1", GitCommit:"b1b29978270dc22fecc592ac55d903350454310a", GitTreeState:"clean", BuildDate:"2018-07-17T18:43:26Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:

kubeadm

Can you share your PV configuration?

apiVersion: monitoring.coreos.com/v1
kind: Prometheus
spec:
  storage:
    volumeClaimTemplate:
      spec:
        storageClassName: prometheus
        resources:
          requests:
            storage: 150Gi

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: prometheus
provisioner: kubernetes.io/azure-disk
parameters:
  kind: Managed
  storageaccounttype: Standard_LRS
allowVolumeExpansion: true
reclaimPolicy: Delete

Running on Ubuntu 16-LTS
Previously the wal files were created with 1000 2000, now they are created with root root
Previously prometheus ran as 1000, now it runs as root
Creating a new prometheus on operator 0.26.0 with prometheus 2.5.0 works fine
This is pretty surprising to me too, so I hope you might have some ideas how I could try get more information for you next.

That’s odd, typically the kubelet ensures correct ownership on content of a volume before mounting it. Could you explicitly set the security context to what it was before? That would at least fix your situation.

Thanks for the info, I'll give it a try.
I'm concerned that this isn't a safe upgrade to push without breaking the Helm charts for folks who already have persistent storage provisioned, so I wanted to find out what could cause it.
It's odd that prometheus finds WAL files but isn't able to read them

^^ Having the same problem

That seems like a bug with the volume provider though, this doc says that before mounting the kubelet sets the owner/permissions recursively. https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/volume-ownership-management.md

So whats the solution ? not very clear in the post. Is it just to roll back to the previous version ?

I was having the same issue. Based on @brancz comments I added and it appears to work fine.
securityContext:
  runAsNonRoot: false
  runAsUser: 0
  fsGroup: 0

Is there a way to set the SecurityContext at the Operator level instead of on each individual Prometheus resource?
Updating all of our Prometheus resources individually is going to be a pretty big pain for us. We have several different Prometheus instances running for different sets of users or use cases. To make it more fun, these are set up and configured differently. For instance, the Prometheus instance which monitors the cluster itself might use the kube-prometheus helm chart, while those dedicated to individual teams or technologies would obviously be deployed differently.
The Operator is great because it automates and manages much of the "business logic" (or "operations logic?") for each of these centrally. Ideally, if we need to set a SecurityContext, we'd be able to do that with the Operator.

This is something that should typically be done fleet wide with pod security policies no?

Is this fixed in a specific version? I'm not getting much of a solution from this discussion

Any update on this issue ? I am facing same problem

Latest Prometheus operator (0.34), the same error on freshly created prometheus.

Encountering same issue on version: 8.5.0, unable to write data to the mounted volume
level=info ts=2020-01-02T13:08:17.241354943Z caller=main.go:679 msg="Notifier manager stopped"
level=error ts=2020-01-02T13:08:17.241420366Z caller=main.go:688 err="opening storage failed: create dir: mkdir /prometheus/wal: permission denied"

That doesn’t seem like an issue with the prometheus operator but rather with either your setup and or the helm charts. I can see that there is a linked issue regarding the helm chart in this thread. Maybe check that out. Just FYI we don’t use nor maintain the helm charts, they’re entirely community maintained.


Instruction suggestion

How to change these files
Follow these steps:

In the github UI, click the "Fork" button, un-check the "Copy the main branch only" option, then click the green "Create Fork" button

Go to your shell command prompt and...

Grab the source you just forked
git clone -o your_github_id https://github.com/your_github_id/creators.git

Change into that folder
cd creators/

Tell it where the real source lives
git remote add creationid https://github.com/creationid/creators.git

Get any updatates needed
git checkout main
git fetch creationid
git merge creationid/main

make your own new branch
git checkout -b add-ids

Make the required changes and/or add new files:
vi creations/sunton.md creations/freenove.md README.md

Add your changes
git status
git add .

 will have shown you a URL on the screen (example below) - visit it and submit the form.

Username for 'https;//github․com': your_github_id
Password for 'https://your_github_id@github․com':
Enumerating objects: 10, done.
Counting objects: 100% (10/10), done.
Delta compression using up to 72 threads
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 1.09 KiB | 1.09 MiB/s, done.
Total 6 (delta 2), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (2/2), completed with 2 local objects.
remote:
remote: Create a pull request for 'add-ids' on GitHub by visiting:
remote:      https://github.com/your_github_id/creators/pull/new/add-ids
remote:
To https;//github․com/your_github_id/creators.git
* [new branch]      add-ids -> add-ids

Feel free to make a PR to add this in the README. Thanks!


API Gateway Cognito User Pool 401

Hello,
I am trying to fetch data from an API Gateway endpoint with an custom authorizer (Cognito User Pool).
However, I successfully logged in via amplify I get an 401 whenever I try to send an request to whatever endpoint
Thats my amplifyconfiguration
{     "auth": {         "plugins": {             "awsCognitoAuthPlugin": {                 "UserAgent": "aws-amplify/cli",                 "Version": "0.1.0",                 "IdentityManager": {                     "Default": {}                 },                 "CognitoUserPool": {                     "Default": {                         "PoolId": "eu-central-1_XXXX",                         "AppClientId": "XX",                         "AppClientSecret": "XX",                         "Region": "eu-central-1"                     }                 },                 "CredentialsProvider": {                     "CognitoIdentity": {                         "Default": {                             "PoolId": "eu-central-1XXX",                             "Region": "eu-central-1"                         }                     }                 },                 "Auth": {                     "Default": {                         "authenticationFlowType": "USER_SRP_AUTH",                     }                 }             }         }     },     "api": {         "plugins": {             "awsAPIPlugin": {                 "shipsoul": {                     "endpointType": "REST",                     "endpoint": "https://XXXXXX",                     "region": "eu-central-1",                     "authorizationType": "AMAZON_COGNITO_USER_POOLS"                 }             }         }     } }
Using latest version of Amplify
Device Information (please complete the following information):
iphone SE / 11 / 12
iOS 14

Hi @nkb1337
formatting your amplifyconfiguration.json using triple backticks
{
   "auth":{
      "plugins":{
         "awsCognitoAuthPlugin":{
            "UserAgent":"aws-amplify/cli",
            "Version":"0.1.0",
            "IdentityManager":{
               "Default":{

               }
            },
            "CognitoUserPool":{
               "Default":{
                  "PoolId":"eu-central-1_XXXX",
                  "AppClientId":"XX",
                  "AppClientSecret":"XX",
                  "Region":"eu-central-1"
               }
            },
            "CredentialsProvider":{
               "CognitoIdentity":{
                  "Default":{
                     "PoolId":"eu-central-1XXX",
                     "Region":"eu-central-1"
                  }
               }
            },
            "Auth":{
               "Default":{
                  "authenticationFlowType":"USER_SRP_AUTH"
               }
            }
         }
      }
   },
   "api":{
      "plugins":{
         "awsAPIPlugin":{
            "shipsoul":{
               "endpointType":"REST",
               "endpoint":"https://XXXXXX",
               "region":"eu-central-1",
               "authorizationType":"AMAZON_COGNITO_USER_POOLS"
            }
         }
      }
   }
}

The configuration looks good to me. After sign in, you can get the token and use it to test connectivity in the API Gateway console.
Get the token https://docs.amplify.aws/lib/auth/access_credentials/q/platform/ios
if let cognitoTokenProvider = session as? AuthCognitoTokensProvider {
            let tokens = try cognitoTokenProvider.getCognitoTokens().get()
            print("Id token - \(tokens.idToken) ")
        }

I've outlined my experience here https://github.com/aws-amplify/amplify-cli/issues/3390

under Authorizers section there should be a testing section to pass your token in to validate connectivity
make sure to deploy your API or the authorization changes will not be propagated

Once you can verify this, there's another thing to watch out for; the api configuration with AMAZON_COGNITO_USER_POOLS authorizationType will intercept the request with the accessToken and Not the idToken. If you require the idToken, you'll have to follow these steps to introduce your own token provider under OIDC authorizationType. See https://docs.amplify.aws/lib/restapi/authz/q/platform/ios#oidc for more details.

Hi,
I think I found the issue(?). When I send a request instantly after signing it seems like there is no session available. (Obtaining an identity id in another thread failed or didn't complete within 5 seconds.")
However after couple of seconds I can send the requests without any issues and an session is available and I can get the tokens etc. without any issues.

Hi @nkb1337
Thank you for providing this information. When you say that you send a request instantly after signIn, are you calling it in signIn callback? Like this:

Amplify.Auth.signIn(username: "", password: "") { (result) in
            // Call api request here
}

Or outside the callback? Something like this:
2)
Amplify.Auth.signIn(username: "", password: "")
// Call api request here

You should follow # 1 approach ie wait for the signIn to complete before invoking api request. Can you provide a code snippet on how and when you invoke the api request to help us debug further.

@lawmicha I'm having some similar issues. I've followed all the steps provided by documentation, but API Gateway doesn't seem to accept access tokens. AWS says that you can use access tokens if you enable OAuth scopes, but when you enable OAuth scopes, it seems like it changes from looking for the id token to looking for what appears to be an AWS Version 4 Signature.
Nothing I do seems to work with these Cognito access tokens. Any ideas?

@wedouglas Just to confirm, did you follow the steps as mentioned in this GH issue - https://github.com/aws-amplify/amplify-cli/issues/3390 . There seems to be some manual steps as mentioned in step 7 to 11.

@royjit We were able to figure it out a while back. I don't recall offhand what we ended up changing, but I think our issue was just the documentation being unclear for how you call the API. We were calling it with the custom scope in the endpoint url since that's what the documentation showed as an example.
I think it's just another case of AWS documentation being, well, less than great haha.
In any case, thanks for your help after the fact!

@lawmicha i am facing a similar issue , i have a project setup which uses cognito to authenticate users , it logs in successfully but all api's return 401.
I have followed all 11 steps and the concerning part is this is happening after i updated amplify to the following
Installing AWSAuthCore 2.25.0 (was 2.14.2)
Installing AWSCognitoIdentityProvider 2.25.0 (was 2.14.2)
Installing AWSCognitoIdentityProviderASF 2.25.0 (was 1.0.1)
Installing AWSCore 2.25.0 (was 2.14.2)
Installing AWSMobileClient 2.25.0 (was 2.14.2)
Installing AWSPluginsCore 1.13.4 (was 1.0.4)
Installing AWSS3 2.25.0 (was 2.14.2)
Installing Amplify 1.13.4 (was 1.0.4)
Installing AmplifyPlugins 1.13.4 (was 1.0.4)
Installing AppSyncRealTimeClient 1.5.0 (was 1.1.6)

The earlier version is also provided above.
If i switch back to the earlier version of amplify plugins it works fine.Can you pls help me out?


Feat: add helper text on cards

Soldier, ranged, and magical are a little confusing to new players.  We added some help text to units on board to assist with displaying them

Closes: #155


fix(error): add datetime and email parse error to ParsingError enum

Type of Change

[ ] Bugfix
[ ] New feature
[x] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

This PR adds two more parsing errors i.e., DateTimeParsingError and EmailParsingError to ParsingError enum
Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

Are we not planning to raise these error variants anywhere yet?

Nope


Be able to list targets?

Before this is implemented, the source of truth is here $HOME/.copy-pastarc

Use copy-pasta targets to list the targets.


bump amazon music to version <IP_ADDRESS>7

Thank you for the contribution. It was merged directly as 9dfabb8d931481559ea88e4b537692dbd86907ab to keep commit history cleaner. Your contribution is still credited to you.


Will fast-rtps suitable for auto-driving scenario?

Hi all
I know rtps is designed for end-to-end, real-time, transfer of data. It can be used in scenarios of many machines so they can discover each other.
In auto-driving scenario, realtime and reliability is essential. Normally, only one or two powerful machines for deep learning computing. So is it suitable for auto-driving scenario?
Thanks

HI @journey-wang,
Sorry the late response. Please take a look here https://github.com/ros2/rmw_fastrtps/issues/202#issuecomment-394180035


Implement lottery

To attract users to create more transactions, we can implement lottery in the system.
In the lottery, every user buys a ticket with a fixed price and enrolls in the lottery. The price of the ticket paid by the user is added to the prize pool. A user can enroll multiple times but needs to create separate transactions for all of them (This requires support for multiple transactions in the same block, therefore can be discussed) .
After a minimum number of users are gathered and a minimum amount of time has passed, transfer the tokens in the prize pool to the winner that is selected randomly.

Ideally, I'd like to increase the volume of transactions between actual people. However, this might fit into the "testnet" phase since it can be driven by low number of people, even 1.
Which reminds me, the project desperately needs a way to switch between different modes of operation. I can implement the lottery system after that, since there is a need for multiple game scenarios (between different semesters and between testnet and realnet (?)). That will be a separate issue though.
Let's put this on hold and reopen it once the mode of operation switching is implemented.

I see, transactions between actual people requires a different approach for creating incentives. First idea coming to my mind is to allow exchange of different types of tokens, similar to Decentralized Finance. This idea is also suitable for "chaos mode" that is mentioned in TODO.md


Logo

@davesnx do you need help? I can help with this... I created reform's logo and if u want, can check my porfolio here :)

Hey @vmarcosp, I currently have a plan for the logo which will happen at some point.
Thank you very much for your suggestion, I do love reforms logo and your portfolio a lot. I will let you know if the plan goes away.
Thanks for the interest

@davesnx ahh great! No problem! If you need any help with something like this, you can count on me :)


Failed to refresh Docker (Client.Timeout exceeded)

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Start OrbStack app
In a terminal, type docker run -it -p 80:80 docker/getting-started
Open OrbStack and click on "Containers" tab
See failure (screenshot)

Expected behavior
I expect to see the new container.
Screenshots

Logs
Not available
Info report
OrbStack info:
  Version: 0.5.2 (50200)
  Commit: 1070de4aca19fab0c2c0b57d7c0bacca7812ca23 (v0.5.2)

System info:
  macOS: 13.2.1 (22D68)
  CPU: arm64, 10 cores
  CPU model: Apple M1 Pro

Additional context
Thanks!

Please attach console.log from the OrbStack menu -> Show Logs.

I believe this was due to me not allowing permissions to the app. Once I restarted the computer, it asked for the permissions again which I allowed and now it's working fine.
Thanks!

Thanks for the update. Do you remember which specific permissions you had to allow? Ideally it shouldn't time out even if you don't allow them.

I have the same problem，Here is the error log
time="04-01 13:58:25" level=error msg="host-tcp forward: dial failed" addr="{1 <IP_ADDRESS> 8000}" error="connect tcp <IP_ADDRESS>:8000: connection was refused"
time="04-01 13:58:25" level=error msg="host-unix forward: dial failed" addr="{1 <IP_ADDRESS> 2375}" error="connect tcp <IP_ADDRESS>:2375: connection was refused"
time="04-01 13:58:25" level=error msg="host-tcp forward: dial failed" addr="{1 <IP_ADDRESS> 8000}" error="connect tcp <IP_ADDRESS>:8000: connection was refused"
time="04-01 13:58:25" level=info msg="data ready"
time="04-01 13:58:25" level=info msg="Mounting NFS..."
time="04-01 13:58:25" level=info msg="data ready"
time="04-01 13:58:25" level=error msg="host-unix forward: dial failed" addr="{1 <IP_ADDRESS> 2375}" error="connect tcp <IP_ADDRESS>:2375: connection was refused"
time="04-01 13:58:25" level=error msg="host-vsock forward: dial failed" error="Error Domain=NSPOSIXErrorDomain Code=54 \"Connection reset by peer\""
time="04-01 13:58:27" level=error msg="NFS mount failed" error="mount nfs: mount(): connection reset by peer"
time="04-01 13:58:27" level=info msg="Mounting NFS..."
time="04-01 13:58:27" level=info msg="NFS mounted"
time="04-01 13:58:33" level=info msg="Setup not done in time, running setup..."
 Does the error happen consistently or was it just one-time? Did you have any permission prompts?

@kdrag0n This error persists

@asasas234 Are you still experiencing this issue? If so, please attach the info requested above. Thanks!

Should be fixed in the upcoming version. Let me know if anyone sees it again after it's released and I'll reopen this issue.

Fixed in v0.7.0.


EKS nodes do not become ready when MutatingWebhookConfiguration enabled

I hope this is the right place to report this issue.
Describe the bug
In AWS EKS, when the vault-secrets-webhook MutatingWebhookConfiguration is enabled Kubernetes nodes remain in a NotReady state and never enter a Ready state.
According to the kubelet logs of affected hosts the amazon-vpc-cni-k8s cni plugin appears to have issues when the webhook is enabled.
To Reproduce
This assumes you have provisioned an AWS EKS cluster and an autoscaling group for worker nodes and have also installed helm/tiller.
Steps to reproduce the behavior:

Install the vault-secrets-webhook chart. The steps I have used are:

kubectl label namespace default name=default vault-injection=enabled
helm install --name vault-secrets-webhook banzaicloud-stable/vault-secrets-webhook \
  --namespace default \
  --set env.VAULT_ENV_IMAGE=banzaicloud/vault-env:0.4.17 \
  --set env.VAULT_IMAGE=vault:1.1.3 \
  --set image.tag=0.4.17 \
  --set replicaCount=3 \
  --set namespaceSelector.matchLabels.vault-injection=enabled \
  --set debug=true \
  --no-hooks --tls

Ensure the vault-secrets-webhook pods have been created and are running
Terminate an ec2 instance in the eks autoscaling group
Wait for a new ec2 instance to be created by the autoscaling group and become healthy
The new node attempts to join the cluster but never becomes ready

Expected behavior
The new node to successfully join the cluster and become ready
Logs
Below are the kubelet logs from an affected node.
-- Logs begin at Thu 2019-06-27 01:49:23 UTC, end at Thu 2019-06-27 03:58:32 UTC. --
Jun 27 02:22:09 ip-10-10-120-128 systemd[1]: Starting Kubernetes Kubelet...
Jun 27 02:22:09 ip-10-10-120-128 systemd[1]: Started Kubernetes Kubelet.
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: Flag --allow-privileged has been deprecated, will be removed in a future version
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: Flag --kube-reserved has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kuberne
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: Flag --system-reserved has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kuber
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: Flag --eviction-hard has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kuberne
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: Flag --allow-privileged has been deprecated, will be removed in a future version
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: Flag --kube-reserved has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kuberne
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: Flag --system-reserved has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kuber
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: Flag --eviction-hard has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kuberne
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: I0627 02:22:19.191092    4616 server.go:407] Version: v1.13.7-eks-c57ff8
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: W0627 02:22:19.191313    4616 plugins.go:118] WARNING: aws built-in cloud provider is now deprecated. The AWS provider is deprecated and will be removed
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: I0627 02:22:19.240696    4616 aws.go:1041] Building AWS cloudprovider
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: I0627 02:22:19.240748    4616 aws.go:1007] Zone not specified in configuration file; querying AWS metadata service
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: I0627 02:22:19.680019    4616 tags.go:77] AWS cloud filtering on ClusterID: dev-kube
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: I0627 02:22:19.820561    4616 container_manager_linux.go:248] container manager verified user specified cgroup-root exists: []
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: I0627 02:22:19.820579    4616 container_manager_linux.go:253] Creating Container Manager object based on Node Config: {RuntimeCgroupsName: SystemCgroups
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: I0627 02:22:19.820741    4616 container_manager_linux.go:272] Creating device plugin manager: true
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: I0627 02:22:19.820796    4616 state_mem.go:36] [cpumanager] initializing new in-memory state store
Jun 27 02:22:19 ip-10-10-120-128 kubelet[4616]: I0627 02:22:19.823430    4616 kubelet.go:306] Watching apiserver
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.060416    4616 client.go:75] Connecting to docker on unix:///var/run/docker.sock
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.060880    4616 client.go:104] Start docker client with request timeout=2m0s
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.062939    4616 docker_service.go:236] Hairpin mode set to "hairpin-veth"
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: W0627 02:22:20.063019    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: W0627 02:22:20.064447    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.064474    4616 docker_service.go:251] Docker cri networking managed by cni
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.070952    4616 docker_service.go:256] Docker Info: &{ID:R3EC:LFVY:7IWE:YU4I:VAPK:YL5Y:BJDM:IGKX:HSLV:JBN4:YM7X:LQEE Containers:0 Containe
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.071061    4616 docker_service.go:269] Setting cgroupDriver to cgroupfs
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.080482    4616 kuberuntime_manager.go:198] Container runtime docker initialized, version: 18.06.1-ce, apiVersion: 1.38.0
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: W0627 02:22:20.156459    4616 probe.go:271] Flexvolume plugin directory at /usr/libexec/kubernetes/kubelet-plugins/volume/exec/ does not exist.  Stats initialization may not have completed yet: failed to get imag
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.160373    4616 server.go:333] Adding debug handlers to kubelet server.
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.162371    4616 fs_resource_analyzer.go:66] Starting FS ResourceAnalyzer
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.162411    4616 status_manager.go:152] Starting to sync pod status with apiserver
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.162425    4616 kubelet.go:1829] Starting kubelet main sync loop.
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.162441    4616 kubelet.go:1846] skipping pod synchronization - [container runtime status check may not have completed yet PLEG is not hea
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.162471    4616 volume_manager.go:248] Starting Kubelet Volume Manager
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.162492    4616 desired_state_of_world_populator.go:130] Desired state populator starts to run
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: W0627 02:22:20.163459    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: E0627 02:22:20.163548    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.230317    4616 kubelet_node_status.go:279] Setting node annotation to enable volume controller attach/detach
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.230335    4616 kubelet_node_status.go:327] Adding node label from cloud provider: beta.kubernetes.io/instance-type=c5.2xlarge
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.230340    4616 kubelet_node_status.go:338] Adding node label from cloud provider: failure-domain.beta.kubernetes.io/zone=ap-southeast-2a
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.230344    4616 kubelet_node_status.go:342] Adding node label from cloud provider: failure-domain.beta.kubernetes.io/region=ap-southeast-2
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.231872    4616 cpu_manager.go:155] [cpumanager] starting with none policy
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.231884    4616 cpu_manager.go:156] [cpumanager] reconciling every 10s
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.231890    4616 policy_none.go:42] [cpumanager] none policy: Start
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: W0627 02:22:20.240718    4616 manager.go:537] Failed to retrieve checkpoint for "kubelet_internal_checkpoint": checkpoint is not found
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: E0627 02:22:20.240948    4616 eviction_manager.go:247] eviction manager: failed to get summary stats: failed to get node info: node "ip-10-10-120-128.ap
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.262553    4616 kubelet_node_status.go:279] Setting node annotation to enable volume controller attach/detach
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.262584    4616 kubelet_node_status.go:327] Adding node label from cloud provider: beta.kubernetes.io/instance-type=c5.2xlarge
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.262592    4616 kubelet_node_status.go:338] Adding node label from cloud provider: failure-domain.beta.kubernetes.io/zone=ap-southeast-2a
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.262599    4616 kubelet_node_status.go:342] Adding node label from cloud provider: failure-domain.beta.kubernetes.io/region=ap-southeast-2
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: E0627 02:22:20.262934    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: I0627 02:22:20.264052    4616 kubelet_node_status.go:72] Attempting to register node ip-10-10-120-128.ap-southeast-2.compute.internal
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: E0627 02:22:20.363040    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: E0627 02:22:20.463149    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: E0627 02:22:20.563262    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: E0627 02:22:20.663369    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: E0627 02:22:20.763480    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: E0627 02:22:20.863588    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:20 ip-10-10-120-128 kubelet[4616]: E0627 02:22:20.963692    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:21 ip-10-10-120-128 kubelet[4616]: E0627 02:22:21.063815    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:21 ip-10-10-120-128 kubelet[4616]: E0627 02:22:21.163935    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:21 ip-10-10-120-128 kubelet[4616]: E0627 02:22:21.264041    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:21 ip-10-10-120-128 kubelet[4616]: E0627 02:22:21.364150    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:21 ip-10-10-120-128 kubelet[4616]: E0627 02:22:21.464264    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:21 ip-10-10-120-128 kubelet[4616]: E0627 02:22:21.564373    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:21 ip-10-10-120-128 kubelet[4616]: E0627 02:22:21.664486    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:21 ip-10-10-120-128 kubelet[4616]: E0627 02:22:21.764593    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:21 ip-10-10-120-128 kubelet[4616]: E0627 02:22:21.864713    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:21 ip-10-10-120-128 kubelet[4616]: E0627 02:22:21.964816    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:22 ip-10-10-120-128 kubelet[4616]: E0627 02:22:22.064931    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:22 ip-10-10-120-128 kubelet[4616]: E0627 02:22:22.165044    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:22 ip-10-10-120-128 kubelet[4616]: E0627 02:22:22.265148    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:22 ip-10-10-120-128 kubelet[4616]: E0627 02:22:22.365249    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:22 ip-10-10-120-128 kubelet[4616]: E0627 02:22:22.465355    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:22 ip-10-10-120-128 kubelet[4616]: E0627 02:22:22.565467    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:22 ip-10-10-120-128 kubelet[4616]: E0627 02:22:22.665597    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:22 ip-10-10-120-128 kubelet[4616]: E0627 02:22:22.765716    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:22 ip-10-10-120-128 kubelet[4616]: E0627 02:22:22.865840    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:22 ip-10-10-120-128 kubelet[4616]: E0627 02:22:22.965970    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:23 ip-10-10-120-128 kubelet[4616]: E0627 02:22:23.066088    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:23 ip-10-10-120-128 kubelet[4616]: E0627 02:22:23.166203    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:23 ip-10-10-120-128 kubelet[4616]: E0627 02:22:23.266306    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:23 ip-10-10-120-128 kubelet[4616]: E0627 02:22:23.366409    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:23 ip-10-10-120-128 kubelet[4616]: I0627 02:22:23.465282    4616 reconciler.go:154] Reconciler: start to sync state
Jun 27 02:22:23 ip-10-10-120-128 kubelet[4616]: E0627 02:22:23.466505    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:23 ip-10-10-120-128 kubelet[4616]: E0627 02:22:23.566609    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:23 ip-10-10-120-128 kubelet[4616]: I0627 02:22:23.626205    4616 kubelet_node_status.go:75] Successfully registered node ip-10-10-120-128.ap-southeast-2.compute.internal
Jun 27 02:22:23 ip-10-10-120-128 kubelet[4616]: E0627 02:22:23.666708    4616 kubelet.go:2266] node "ip-10-10-120-128.ap-southeast-2.compute.internal" not found
Jun 27 02:22:25 ip-10-10-120-128 kubelet[4616]: W0627 02:22:25.241866    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:22:25 ip-10-10-120-128 kubelet[4616]: E0627 02:22:25.241947    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:22:30 ip-10-10-120-128 kubelet[4616]: W0627 02:22:30.242505    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:22:30 ip-10-10-120-128 kubelet[4616]: E0627 02:22:30.242584    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:22:35 ip-10-10-120-128 kubelet[4616]: W0627 02:22:35.243211    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:22:35 ip-10-10-120-128 kubelet[4616]: E0627 02:22:35.243286    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:22:40 ip-10-10-120-128 kubelet[4616]: W0627 02:22:40.243865    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:22:40 ip-10-10-120-128 kubelet[4616]: E0627 02:22:40.243942    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:22:45 ip-10-10-120-128 kubelet[4616]: W0627 02:22:45.244499    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:22:45 ip-10-10-120-128 kubelet[4616]: E0627 02:22:45.244586    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:22:50 ip-10-10-120-128 kubelet[4616]: W0627 02:22:50.245163    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:22:50 ip-10-10-120-128 kubelet[4616]: E0627 02:22:50.245249    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:22:55 ip-10-10-120-128 kubelet[4616]: W0627 02:22:55.245852    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:22:55 ip-10-10-120-128 kubelet[4616]: E0627 02:22:55.245941    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:23:00 ip-10-10-120-128 kubelet[4616]: W0627 02:23:00.246494    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:23:00 ip-10-10-120-128 kubelet[4616]: E0627 02:23:00.246576    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:23:05 ip-10-10-120-128 kubelet[4616]: W0627 02:23:05.247257    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:23:05 ip-10-10-120-128 kubelet[4616]: E0627 02:23:05.247359    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:23:10 ip-10-10-120-128 kubelet[4616]: W0627 02:23:10.247857    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:23:10 ip-10-10-120-128 kubelet[4616]: E0627 02:23:10.247946    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:23:15 ip-10-10-120-128 kubelet[4616]: W0627 02:23:15.248496    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:23:15 ip-10-10-120-128 kubelet[4616]: E0627 02:23:15.248578    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:23:20 ip-10-10-120-128 kubelet[4616]: W0627 02:23:20.249263    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:23:20 ip-10-10-120-128 kubelet[4616]: E0627 02:23:20.249363    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:23:25 ip-10-10-120-128 kubelet[4616]: W0627 02:23:25.249926    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d
Jun 27 02:23:25 ip-10-10-120-128 kubelet[4616]: E0627 02:23:25.250012    4616 kubelet.go:2192] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: netw
Jun 27 02:23:30 ip-10-10-120-128 kubelet[4616]: W0627 02:23:30.250530    4616 cni.go:203] Unable to update cni config: No networks found in /etc/cni/net.d

The logs continue in this fashion with the last two lines repeated over and over.
Note, if delete the helm release or even just the MutatingWebhookConfiguration I can restart the kubelet and the node becomes ready.

Which version of EKS are you using? I am running bank-vaults 0.4.15 with EKS 1.11 and it is fine.

I have experienced this in EKS 1.12 and now also 1.13. It only happens when the vault-secrets-webhook is enabled.
I am not sure about installing the webhook in another namespace however I don’t have any workloads in the default namespace.

Hi @stephenmuss I think your issue is related to that the webhook tries to mutate containers in the kube-system namespace as well. Could you please configure it via the labelSelectors in the chart so the kube-system namespace gets ignored?

Maybe I’m missing something but as per the description I installed the helm chart  with --set namespaceSelector.matchLabels.vault-injection=enabled
It still seems to have the issue.
I agree that it still appears to be attempting to mutate pods in kube-system.
I will try again and also install in its own namespace when I am at a computer.

If you still have the issue with that setup could you please get the definition of the MutatingWebhookConfiguration in yaml format?

Hi @bonifaido I just reinstalled vault-secrets-webhook in its own namespace with the same flags above and it now seems to work. I terminated an instance and a new node joined and entered into a ready state.
I might still play around with this to see if I can replicate it again. Otherwise, sorry for the noise.

Ok, it seems to be consistently working now regardless of whether it's in the default namespace or another. I must have got stuck with an old MutatingWebhookConfiguration even after using --set namespaceSelector.matchLabels.vault-injection=enabled.
I'm going to close the issue.
Thanks for your help.

Thank you @stephenmuss, no worries, feel free to ask questions or report bugs any time!

Just wanted to add another comment to this as I was bitten again today.
I was updating another cluster and ran into the same problem. It looks like the MutatingWebhookConfiguration is quite different in newer versions of the helm chart.
I had to run helm repo update before reinstalling the chart to resolve the issue.


fix make-raw to properly handle stdin and to not adjust partitions for usbconf

tools/makeusbconf.sh -d -i -f ./usb.json -s 8000 usb.img
doesn't work with defined usb.json and stops with empty filesystem and error /parts/*: No such file or directory.
It comes from lines where we check for /parts and if it not exists, we extract file comes from tar in stdin. But /parts exists, we create it in Dockerfile. So, I add check for tty connected to stdin, if not, we assume that it is pipe from tar.
Another problem I can see is that in case of makeusbconf we create only one partition (from function do_usb_conf) and seems our logic for protective mbr is not applicable there.
cc @milan-zededa

I am actually really not sure about deciding this based one whether this is called with a tty attached or not. Typically this is not what one wants to do -- I'd like to dig deeper into the underlying cause first

As another option we can check for empty/not empty /parts directory to use stdin or not. Also I made explicit check for usb_conf in script to skip hybrid MBR changes.


Fix i18n discovery on dev restart

This isn't an ideal implementation, but necessary given the current setup with Babel caching. Fortunately, this code won't be needed once https://github.com/fusionjs/fusion-cli/issues/426 is implemented because the compilation pipeline will be rather different.

Can you update the description to describe how this PR fixes it?

!merge


Cannot supply THREAD_OPTIONS to lzmq.threads

there should be an api form which allows the user to supply their own THREAD_OPTIONS
something like
function zthreads.fork(ctx, code, ...)
  local fork_starter = {code = code}
  return zthreads.fork_opts(ctx, fork_starter, ...)
end

function zthreads.fork_opts(ctx, thread_opts, ...)
  local pipe, endpoint = make_pipe(ctx)
  if not pipe then return nil, endpoint end

  ctx = ctx:lightuserdata()
  local ok, err = Threads.new(thread_opts, ZMQ_NAME, ctx, endpoint, ...)
  if not ok then
    pipe:close()
    return nil, err
  end
  return ok, pipe
end

use case (supplying package paths to child thread)
loca lua_init = [[
  package.cpath="]] .. package.cpath .. [["
  package.path="]] .. package.path
local opts = {lua_init = lua_init, code =<EMAIL_ADDRESS>zthreads. fork_opts(ctx, opts)

im willing to implement this. Do you have input on what the api should look like?
i'm suggesting
zthreads.run_opts(ctx, thread_options, ...)
zthreads.fork_opts(ctx, thread_options, ...)
zthreads.actor_opts(ctx, thread_options, ...)
where thread_options is
https://github.com/moteus/lua-llthreads2/blob/master/src/lua/llthreads2/ex.lua#L196

Closed by #29 and #30


\overline converting to mathml with attribute [accent="true"] causes j without dot

Hello,
MathJax converts $\overline{A_i}$ to
<math xmlns="http://www.w3.org/1998/Math/MathML">
  <mover>
    <msub>
      <mi>A</mi>
      <mi>i</mi>
    </msub>
    <mo accent="true">―</mo>
  </mover>
</math>

The [accent="true"] attribute can cause i(or j) in subscript to have no dot, in native MathML output. How to fix this problem (let MathJax set accent attribute of \overline to be false)?
Thanks!

What are you using to render the MathML?  I am not able to reproduce the issue you are describing.  The subscript "i" renders properly for me.  In any case, this sounds like a problem with the native MathML renderer, not MathJax itself.
You could use a TeX input jax post-filter to alter the accent attribute, but since you haven't given any indication of how you are actually calling MathJax, I can't really tell you what is the best way to do that in your situation.

Hello,
I was using Firefox Release 100.0 .

Yes. This is a problem with the native MathML renderer, not MathJax itself. The subscript "i" renders properly in CommonHTML output.

Hello,
I don't have a custom stylesheet. I was using Windows 10. The font for MathML engine is Latin Modern Math. But it works great for Cambria Math.

Yes. This is a problem with the native MathML renderer, not MathJax itself.
I have reported at BugZilla


Update to Nuxt 2.14

Upgraded dependencies, html serializer, link handling.

@samlfair I just tested this and previews/releases seem to be failing. Can you test this on your side with the repo I just invited you to?

@phillysnow Yeah, the previews are failing for me with that repo. I found your comment about Toolbar V1 vs V2, so I duplicated the repo as multi-language-example-sam, and the preview seems to be working. I'll send you an invite to my repo so you can test it out.
However, these two fields don't seem to exist in the custom types, so they're breaking the page for me:
https://github.com/prismicio/nuxt-multi-language-site/blob/50e508c87f6fabe9bff54e2ef752145e03ba73cf/components/slices/InfoWithImage.vue#L19
https://github.com/prismicio/nuxt-multi-language-site/blob/50e508c87f6fabe9bff54e2ef752145e03ba73cf/components/slices/TextInfo.vue#L4
I'm not sure why it works in your repo but not in mine — I don't see those fields in your repo either. Is it okay if I remove them and commit?

@samlfair OK, I see what you mean. I finally got time for this, yeah it's strange that this didn't cause issues before. You can go ahead and removed them and commit like you said. Then we're good to go.

@phillysnow Cool I removed those icons, so this should be good to merge.


[WIP][SPARK-40822][SQL] Stable derived column aliases

What changes were proposed in this pull request?

Why are the changes needed?
To improve user experience with Spark SQL. It is always best practice to name the result of any expressions in a queries select list,  if one plans to reference them later. This yields the most readable results and stability. However, sometimes queries are generated or we’re just lazy and trust in the auto generated names. The problem is that the auto-generated names are produced by pretty printing the expression tree which is, while “generally” readable, not meant to be stable across long durations of time. For example:
spark-sql> DESC SELECT substring('hello', 5);
substring(hello, 5,<PHONE_NUMBER>)	string

the auto-generated column alias substring(hello, 5,<PHONE_NUMBER>) contains not-obvious elements.
Does this PR introduce any user-facing change?
Yes.
How was this patch tested?
By running the modified test suites:
$ build/sbt -Phive -Phive-thriftserver "test:testOnly *SparkThriftServerProtocolVersionsSuite"
$ PYSPARK_PYTHON=python3 build/sbt "sql/testOnly org.apache.spark.sql.SQLQueryTestSuite"
$ build/sbt "test:testOnly *AvroV2Suite"
$ build/sbt "test:testOnly *SQLQuerySuite"
$ build/sbt -Phive-2.3 -Phive-thriftserver "test:testOnly *HiveDDLSuite"
$ build/sbt -Phive-2.3 "test:testOnly *HiveOrcSourceSuite"

@cloud-fan @srielau Could you review generating of column aliases, please.


Maybe change to Creative Commons License

Since this is a specification and not an actual program, I recommend using a Creative Commons License for the specification.
For example CC-BY-SA

Most fitting Creative Commons is CC-AT.
CC-AT


"Expected 11, got 13" error anytime 'atom' is required.

I have no idea why this happens, but I can trace it down to running a coffee-script with 'atom' required:
Error: Module version mismatch. Expected 11, got 13.
  at Module.load (/usr/lib/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:312:12)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at bindings (/usr/local/share/atom/resources/app/node_modules/pathwatcher/node_modules/bindings/bindings.js:76:44)
  at Object.<anonymous> (/usr/local/share/atom/resources/app/node_modules/pathwatcher/lib/main.js:6:32)
  at Object.<anonymous> (/usr/local/share/atom/resources/app/node_modules/pathwatcher/lib/main.js:207:4)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (/usr/lib/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:312:12)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.<anonymous> (/usr/local/share/atom/resources/app/node_modules/text-buffer/lib/text-buffer.js:15:10)
  at Object.<anonymous> (/usr/local/share/atom/resources/app/node_modules/text-buffer/lib/text-buffer.js:954:4)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (/usr/lib/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:312:12)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.<anonymous> (/usr/local/share/atom/resources/app/exports/atom.js:4:10)
  at Object.<anonymous> (/usr/local/share/atom/resources/app/exports/atom.js:28:4)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (/usr/lib/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:312:12)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.<anonymous> (/home/squirtle/github/git-plus/lib/views/select-list-multiple-view.coffee:2:33)
  at Object.<anonymous> (/home/squirtle/github/git-plus/lib/views/select-list-multiple-view.coffee:1:1)
  at Module._compile (module.js:456:26)

I've spent the day trying:

Different node versions
Different coffee versions
Building atom with node versions v0.10.x and v0.11.x

I'm using Xubuntu 14.04.
Nothing I could do. Works perfectly, aslong as I don't include atom anywhere. Ideas? :weary:

Closing due to age, reopen if its an issue still


Generate seeds from db table

Problem
We have seed data that is regularly updated by my colleagues with prisma studio. There is no way I can make these changes visible in my code easily.
Suggested solution
A prisma seed command that checks the database table and shows you the differences between local seed and db.  And you can easily see and update your local seedfile with the latest data in the database.

Possible manual solution:
//dump data to file
const artists = await prismaClient.artist.findMany({});
fs.writeFileSync("./artists.json", JSON.stringify(artists));

Seed database
import artists from "./artists.json";

//use this to remove id, if you use an autogenerated ID
const artistData = artists.map(({ id, ...rest }) => rest);

//insert data to current db
await prismaClient.artist.createMany({ data: artistData });

That is actually pretty similar to an internal prototype we have been using for something. It depends on the data already to be in the database, but if you got it into that state once it is a pretty nice option.

I'm looking writing something similar too, however there are many edge cases that become complex and would be great to see a more general solution; manual seed creation is fine for smaller apps & teams, but once you cross the threshold it's too hard to maintain

here for this ...

✨, here for this!


Cuda out of memory error

Hi,
I was trying to run the command
python test.py --trained_model=./craft_mlt_25k.pth --test_folder=./test_data and got the error.

RuntimeError: CUDA out of memory. Tried to allocate 100.00 MiB (GPU 0; 3.95 GiB total capacity; 2.88 GiB already allocated; 58.25 MiB free; 42.71 MiB cached)

There is no other process running on my laptop and I have a 4GB NVIDIA 1080 TI GPU.

reduce your image image size to 100 pixel width, i too was having this problem on nvidia mx150 2gb for image with bigger resolution and size, when i reduced it to 100 pixel width it worked.

I moved onto 24 GB Titan RTX and it worked, thanks for your response

I realize I'm posting on an issue that was closed a month ago, but thought this might help others who come across it.  I had a similar issue, but was able to solve it by using "with torch.no_grad():" before the "# load data" loop in the test.py file.  That disables the gradient computation (and memory usage), which isn't needed for inference/deployment/evaluation.  Alternatively, I think you could place the "with torch.no_grad():" statement right before the forward pass in the test_net in test.py, and that would work as well.