SemanticUI with semantic-ui-react semantic-ui-less

I was trying to use your boilerplate and add SemanticUI (LESS Version) to this by myself with not much success.
Would you help if I fork and make a PR?
Thanks!

So I kept programming until 5AM and I got it working.
I feel silly because I was mix and matching from another tutorial on webpack2 and Semantic-ui, but innecessarily doing the JS part (when, react's semantic-ui-react manages it all)
FFS, I was even installing and loading jquery LOL
Anyway, I got it kinda working, should I tidy things up and PR with Semantic-UI less working?
It's kinda easy though, maybe just documenting in a blogpost would suffice!

I'm glad you got it working, but this starter kit is meant to be used with Stylus, not LESS, meaning I don't want to maintain different versions of the kit. But of course you can always fork it and use Semantic UI and LESS with it, I'd like to see that and link your project in this project's README.md, if you like.

@odiumediae Yeah that makes total sense, I didn't have any preference for a css preprocessor but semantic-ui doesn't seem to have stylus support (https://www.npmjs.com/package/semantic-ui-stylus) not official and 2y old code...


Bot deaths are not a statistic (fixes #176)

This fixes #176 by ignoring the first-death stat when the victim is a bot player.

Fixed in #179, thanks for raising! Forced me to make some important changes to player_stats. Please see the update in Discord for more info


feat: add more documentation

:tada: This PR is included in version 1.0.0-beta.19 :tada:
The release is available on:

npm package (@develop dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update tempto

I fixed the hive problem, but there still was a problem with loading data into MySQL.
Another change in Tempto is needed.


feat(layered-include_in_schema): Add include_in_schema option for all layers

Add include_in_schema option for all layers
Pull Request Checklist

[ ] New code has 100% test coverage
[x] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[x] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR

Description

https://github.com/litestar-org/litestar/issues/2267

Close Issue(s)

Closes #2267

include_in_schema sounds a bit long and duplicated .
since it is a Flag , how about in_schema or in_openapi

include_in_schema sounds a bit long and duplicated . since it is a Flag , how about in_schema or in_openapi

In the decorators, the argument's name is include_in_schema so it's probably best to keep it the same in this case as well for consistency.

include_in_schema sounds a bit long and duplicated . since it is a Flag , how about in_schema or in_openapi

In the decorators, the argument's name is include_in_schema so it's probably best to keep it the same in this case as well for consistency.

okay.


(wip) HL-499 Update user's name AD Graph API

Description :sparkles:
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #902 (97fd290) into develop (168a879) will increase coverage by 32.50%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop     #902       +/-   ##
============================================
+ Coverage    63.15%   95.65%   +32.50%
============================================
  Files          862      176      -686
  Lines        23198     7705    -15493
  Branches      2311        0     -2311
============================================
- Hits         14650     7370     -7280
+ Misses        8158      335     -7823
+ Partials       390        0      -390

Impacted Files
Coverage Δ

backend/benefit/helsinkibenefit/settings.py
95.20% <ø> (ø)

backend/shared/shared/azure_adfs/views.py
40.00% <0.00%> (-44.00%)
:arrow_down:

backend/shared/shared/common/tests/__init__.py
66.66% <0.00%> (-33.34%)
:arrow_down:

backend/shared/shared/common/tests/conftest.py
80.48% <0.00%> (-19.52%)
:arrow_down:

backend/shared/shared/audit_log/audit_logging.py
87.23% <0.00%> (-12.77%)
:arrow_down:

backend/shared/shared/oidc/auth.py
81.48% <0.00%> (-5.56%)
:arrow_down:

backend/kesaseteli/kesaseteli/settings.py

backend/shared/shared/azure_adfs/auth.py

.../shared/shared/azure_adfs/tests/test_adfs_login.py

backend/tet/tet/settings.py

... and 682 more

Continue to review full report at Codecov.

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


maxjob3.com

http://maxjob3.com/
Spam advertised that it was Google paying $17,000 - $23,000 a month to work from home.
Possible found in comments of many articles on the Internet.

Hi @strict-block – thanks for this input.
We're mostly an aggregator of hosts files from active and reputable curators of hosts files, and we package these amalgamated hosts files in various ways.
Please submit this request to one of our curated sources.
Closing.


client_for_proxy_worker -> worker_client

Motivation
A lot of the code around this function changed, and I think we forgot to also update the name
Proposal
Change it from client_for_proxy_worker to worker_client. This is already inside GrpcProxy, so I think having proxy in the name is redundant. The name of the struct that this returns is ValidatorWorkerClient, so worker_client seemed to make the most sense.
I think (IMHO) this makes it a lot easier to understand what this function is returning.
Test Plan
CI
Release Plan

Nothing to do / These changes follow the usual release cycle.

#2893  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ndr-ds and the rest of your teammates on  Graphite

Merge activity

Nov 15, 9:29 AM EST: A user started a stack merge that includes this pull request via Graphite.


[Feature]: reset mocks to their "initial implementation"

🚀 Feature Proposal
Currently mockFn.mockReset() replaces the mock implementation with an empty function returning undefined (docs).
My proposal is to have mockFn.mockReset() actually reset the mock implementation to the "initial mock implementation". The "initial mock implementation"

would be the first argument to jest.fn() and default to the empty function returning undefined
would be the existing implementation when using jest.spyOn()
would be readonly (unchangeable throughout the lifetime of the mock function)

Implications:

jest.resetAllMocks would use the altered .mockReset()
jest.fn(someFunction) would no longer be equivalent to jest.fn().mockImplementation(someFunction)

Motivation
This change addresses scenarios where some but not all tests in a test module require different implementations/return values of the same mock function/spy.
In such scenario a mock function should have a default implementation (possibly the actual implementation). Should any test change the mock implementation, that change needs to be undone afterEach. Trying to do this with existing tools:

Calling .mockClear() doesn't touch mock implementations/return values.
Calling .mockReset() overrides the mock implementation w/ the empty function returning undefined.
Calling .mockRestore() completely destroys the mock function and restores any "shadowed" original.

Options 2. & 3. would work this far but also require the default mock implementation or spy to be redefined beforeEach (this is what I currently do). Now what if the mock implementation is defined in a mock module?
Redefining a mock function imported from a mock module would require to afterEach(jest.resetModules) to get fresh one for each test. This seems a little expensive and a little unintuitive. Moving on with this solution.
Should any test now require a different mock implementation/return value, it may have to jest.doMock the complete module although calling .mockImplementation() or .mockReturnValue() could suffice.
It should be possible to scope mock implementations/return values to individual tests...

without redefining them from scratch for each test (possibly reloading mock modules)
without counting the number of calls (.mockImplementationOnce() / .mockReturnValueOnce())
without wrapping each test in yet another closure (mockfn.withImplementation())

Example
import { getit } from "datastore";

jest.mock("datastore", () => {
  const exports = jest.requireActual("datastore");
  jest.spyOn(exports, "getit");
  return exports;
});

describe("example", () => {
  it("should work", () => {
    makeItHappen(); // uses getit's actual implementation
    expect(getit).toHaveBeenCalled();
  });

  it("should work", () => {
    getit.mockReturnValue("special case"); // will bleed into subsequent tests
    makeItHappen();
    expect(...);
  });

  // cannot reset bc/ it overrides the actual implementation
  afterEach(() => getit.mockReset());

  // instead we have to reload the mocked module, wasteful
  afterEach(jest.resetModules);

  // looking for alternatives..
  it("should work", () => {
    getit.withImplementation(
      () => "special case",
      () => {
        makeItHappen();
        expect(...);
      }
    );
  });
  // ..not very ergonomic

  // looking for alternatives..
  it("should work", () => {
    getit.mockReturnValueOnce("special case");
    makeItHappen();
    expect(...);
  });
  // ..not very stable
})

Pitch
Here is a conversation I had with my colleague:

"Why do we resetModules here?"
"To redefine the mock function we import from that module for each test."
"Couldn't we just reset the mock function?"
"We can't, it would lose its actual implementation."

I'd have liked to see this as well. If there's an objection about being a breaking change we could introduce another type of mockReset—although having reset, clear and restore, are already confusing enough.
@SimenB any change this could be reopened?

+1 this would be useful


[SPARK-17075][SQL] implemented filter estimation

What changes were proposed in this pull request?
We traverse predicate and evaluate the logical expressions to compute the selectivity of a FILTER operator.
How was this patch tested?
We add a new test suite to test various logical operators.

Can one of the admins verify this patch?

cc @wzhfy @rxin @hvanhovell @cloud-fan

ok to test

Test build #70562 has started for PR 16395 at commit 56d1579.

cc @srinathshankar

Test build #70562 has finished for PR 16395 at commit 56d1579.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class NumericRange(min: JDecimal, max: JDecimal) extends Range

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70562/
Test PASSed.

Merged build finished. Test PASSed.

Test build #70788 has started for PR 16395 at commit e9d4f4d.

Test build #70788 has finished for PR 16395 at commit e9d4f4d.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70788/
Test FAILed.

Test build #70789 has started for PR 16395 at commit b1932fb.

Test build #70789 has finished for PR 16395 at commit b1932fb.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70789/
Test FAILed.

Merged build finished. Test FAILed.

Test build #70830 has started for PR 16395 at commit 1fc44a9.

Test build #70830 has finished for PR 16395 at commit 1fc44a9.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70830/
Test FAILed.

Test build #70894 has started for PR 16395 at commit 784015e.

cc @wzhfy @rxin @srinathshankar @hvanhovell @cloud-fan
Happy New Year!  This PR is ready for code review.

Test build #70894 has finished for PR 16395 at commit 784015e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70894/
Test PASSed.

Merged build finished. Test PASSed.

@ron8hu Can you update the test cases based on the latest master? We have a new test infrastructure now.

cc @rxin @wzhfy
Have updated code based on rxin's comments.  Please review again.

Test build #71180 has started for PR 16395 at commit 210b11b.

Test build #71180 has finished for PR 16395 at commit 210b11b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71180/
Test PASSed.

Test build #71386 has started for PR 16395 at commit 65c9635.

Test build #71386 has finished for PR 16395 at commit 65c9635.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71386/
Test FAILed.

cc @rxin @wzhfy
Have updated code. Please review again.  Thanks.

Test build #71387 has started for PR 16395 at commit f83c713.

Test build #71387 has finished for PR 16395 at commit f83c713.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71387/
Test PASSed.

Test build #71405 has started for PR 16395 at commit 890b126.

Test build #71405 has finished for PR 16395 at commit 890b126.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71405/
Test PASSed.

Test build #71465 has started for PR 16395 at commit 09c86bf.

Test build #71465 has finished for PR 16395 at commit 09c86bf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71465/
Test PASSed.

Test build #71563 has started for PR 16395 at commit 1631153.

Test build #71563 has finished for PR 16395 at commit 1631153.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71563/
Test FAILed.

Merged build finished. Test FAILed.

Test build #71613 has started for PR 16395 at commit 78e3e1e.

Test build #71613 has finished for PR 16395 at commit 78e3e1e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71613/
Test PASSed.

Merged build finished. Test PASSed.

@ron8hu @rxin It seems we don't need logics for binary filter conditions for date/timestamp types, because currently spark will always cast all relative timestamp/data/string comparison into string comparisons. Thanks @cloud-fan for indicating the code here
Thus in tpcds benchmarks tests, filter estimation for date type is unsupported:
[CBO] Unsupported filter condition: cast(d_date#119 as string) IN (2000-06-30,2000-09-27,2000-11-17)
[CBO] Unsupported filter condition: (cast(d_date#63 as string) >= 2000-01-27)
...

ok after more testing, estimation for timestamp/date comparison is still useful.
e.g. users can write cast to date explicitly:
where d_date > date('2000-08-23'), or
where d_date > cast('2000-08-23' AS DATE)

then the condition becomes d_date#132 > 11192, the string is evaluated to an Int after optimization.
So I think it's better to simulate this case in the test suite, instead of assuming the literal is a String.

@wzhfy For predicate condition d_date >= '2000-01-27', we do not support it because Spark SQL cast d_date column to String first before comparison.  For predicate condition d_date >= cast('2000-01-27' AS DATE), CBO supports it by comparing values in date type.

Test build #71734 has started for PR 16395 at commit ce0c30c.

Test build #71734 has finished for PR 16395 at commit ce0c30c.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71734/
Test FAILed.

Merged build finished. Test FAILed.

Test build #71737 has started for PR 16395 at commit 96b14de.

Test build #71737 has finished for PR 16395 at commit 96b14de.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71737/
Test PASSed.

retest this please

Test build #72718 has started for PR 16395 at commit 96b14de.

Test build #72718 has finished for PR 16395 at commit 96b14de.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72718/
Test PASSed.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #72847 has started for PR 16395 at commit 662acc0.

Test build #72847 has finished for PR 16395 at commit 662acc0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72847/
Test PASSed.

Hi @ron8hu , the join PR has been merged and the Range stuff is in, can you update this PR? thanks!

Test build #73010 has started for PR 16395 at commit 4414642.

Hi @cloud-fan I revised the code using latest Range class.  Thanks for reviewing the code.

Test build #73010 has finished for PR 16395 at commit 4414642.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73010/
Test PASSed.

Test build #73093 has started for PR 16395 at commit 0b151bd.

Test build #73093 has finished for PR 16395 at commit 0b151bd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73093/
Test PASSed.

Merged build finished. Test PASSed.

Test build #73116 has started for PR 16395 at commit 1317712.

Test build #73118 has started for PR 16395 at commit c11073f.

Test build #73116 has finished for PR 16395 at commit 1317712.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73116/
Test FAILed.

Test build #73118 has finished for PR 16395 at commit c11073f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73118/
Test PASSed.

Test build #73133 has started for PR 16395 at commit 954d2fc.

@cloud-fan I have updated code based on your feedback.  Please review it again.  Thanks.

Test build #73133 has finished for PR 16395 at commit 954d2fc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73133/
Test PASSed.

Merged build finished. Test PASSed.

Test build #73376 has started for PR 16395 at commit eac69af.

Test build #73376 has finished for PR 16395 at commit eac69af.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73376/
Test FAILed.

Test build #73377 has started for PR 16395 at commit a48a4fd.

LGTM except some minor comments, you can address them in follow-up

Test build #73377 has finished for PR 16395 at commit a48a4fd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73377/
Test PASSed.

thanks, merging to master!


[ENH] Batch process pod events for memberlist manager

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

This PR add batch processing of pod related events.
This diff reduces the unnecessary number of memberlist propagation to the downstream in the following cases:

Pod delete followed by a pod add
Multiple pods added to the deployment at similar time.

A follow up PR will be added to the compaction and query service to allow graceful shutdown to speed up the propagation of deleted pods by the informer to the memberlist manager.

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

The current way works. We can refactor later to use channels instead of shared memory.


Cnpg kubectl plugin subcommand to run pgbench

We forgot to move https://github.com/EnterpriseDB/cnp-bench to https://github.com/cloudnative-pg/charts, when cnpg was open-sourced, but instead of just moving the helm chart now, we could take the chance to introduce a new command in the kubectl cnpg plugin which will directly run a benchmark.
We agreed to start by addressing only pgbench for now and leave fio for another time.
A user should be able to run a benchmark using pgbench simply running kubectl cnpg pgbench CLUSTER_NAME ..., the subcommand should by default apply the job and output the command to see the results, but should also have a flag to output only the manifests, so that any customization can be directly done on the generated manifest, which can then be applied simply using kubectl apply.
The deletion of the completed job should also be addressed, therefore either we print the cleanup command together with the command to read the results or we add a flag to delete instead of creating the jobs, obviously in case the pure manifests were used it will be the users' duty to delete whatever he created by hand.
Previously the chart was also deploying a cluster to target, the subcommand should instead focus on benchmarking existing clusters directly.

I completely forgot we had this ticket. I have created another one #847 with more details on the task.


[Web-18] reusable toast

Develop Re-usable AppToast with ChakraUI Toast
Create a custom hook useAppToast
Change anteater logo

 [Web] Reusable Toast

Great work!
just a few comments and here's one place you might need some update:

We will have a use case where we do not pass highlightedData to the AppToast. We don't want to show the empty highlight box.


No Updating Hash on Click Events

Hello!
First, thanks for the plugin; love it.
Second, I set up a navigation bar and pagination for scrolling to certain pages, but I would like it if it would remove the hash each time it did that, so that if I were to reload the page, it would bring me back to the first panel. Any advice? Any clarification?
Thanks!

https://github.com/lukehaas/Scrollify#setup-with-sectionname


Determine which optimization passes to run based on the query being optimized

Both for logical and physical plan optimization, some optimization passes do not apply. For example, ImplicitJoinPass will have no effect if the query only references a single table. We can skip those optimization passes to minimize the overhead of logical/physical plan generation.

Has been addressed by 6423f597e65f726b818f163a4095a15961fdb132.


[SITE] "has" and "is" stuff

There are many checks to see if a font has something, or is something, usually by simply checking if a specific key exists, or if an array/object contains more than 0 entries.
Sometimes this happens directly in the HTML side (
...
), sometimes as computed value (
...
) where we do the check in the Vue JS, and sometimes there's a check in the engine (
...
).
I'd prefer to have all these checks on one side. Either the site, or the engine. The engine feels like a good place, but some checks are purely for meant for if/else-ing blocks of HTML, and might bloat the engine. Feels overkill to have a has/is-check for each and every thing that can be in the font.
@pascalw Do you have any thoughts on this?

As most things; it depends ;-)
I'd say if there's 'business logic' involved, so something more elaborate than checking null/true/length, then move it to the engine otherwise it's fine to keep it in the library consumers.


Add Var.CI integration

This pull request aims to demonstrate the power of VarCI, the missing assistant for GitHub issues.
--
Automatic update by Var.CI

@VarCI-bot what is this i don't even

@VarCIbot wait--what's your name?

Hey @boneskull - not sure if it was you that brought this to my attention now but the project was listed on the homepage because the repo was connected.
I see you have tried playing with it and it stalled. Anything I can help you with to maybe get this reviewed again?

@jadb Thanks for following up.  We do have a need for a solution like Var.CI (though probably not even that powerful), but I'm dubious about using a closed-source SaaS product (even if it's free for open source; I can't find details on the pricing structure).
I'd prefer to just download, configure, and run this type of bot on my own server.

After you said chat app blocked I remembered I had replied to one of your messages back in September and you had run into some bug (which got fixed the next day). My bad I didn't follow up by email. Chat app provider is supposed to do that when message does not reach you but apparently it does not.
--
Just read your next comment so I'll reply here.
While I understand your concerns, there was no plans on having a private offering until we saw the demand (currently behind feature toggle).
There was plans on open-sourcing the whole thing (ala-Travis) which stalled (not dropped) when we decided to offer private repo support. We might still reconsider that, and you'd be on top of my list of people to reach out to for feedback (if that's OK with you).
That been said, like some testing or styling CIs, may I ask why you prefer hosting the bot? I see your using services like AppVeyor and Travis' hosted version.
I hustle because it would be an honour and privilege to have MochaJS among the OSS projects that trust us. Don't blame me for going the extra mile 😄

@jadb re Travis & AppVeyor:

They are both well-established and thusly low-risk
Last time I checked, AppVeyor is the only show in town for what it does
I don't have the expertise nor desire to safely configure, deploy and maintain--or pay for--our own CI server; the benefits of self-hosting are few

We have very, very few requirements for this type of bot.  If self-hosting turns out to be a rabbit hole, I'll look more closely at SaaS solutions--Var.CI will be on the list.  :smile:

Fair enough. My hope is to be well established at some point too, gotta start somewhere!
I like to believe we are also unique in town (in terms of feature set) and have more in the pipeline (hopefully before the new year). Wished I could say more at this point but if you allow me, I won't hesitate to hustle again ;)
I just merged changes to remove the logo - CI systems will deploy in a few minutes.
Cheers!

UPDATE: in case it was unclear after latest changes on the website, even with a pricing structure in place, it will ALWAYS be free for OSS.

:+1:

Chat app provider is supposed to do that when message does not reach you but apparently it does not.

I'm aggressively blocking many services via uBlock Origin.  Looking at my logs, I'm not seeing any requests to *.smooch.io blocked:

My WAG is one of:

"Disable hyperlink auditing beacon", or
"Disable pre-fetching"
Smooch has to pass through New Relic/Segment/etc. to work properly.

Not sure if you care to ask Smooch about it, but mainly I was interested in discovering what was happening here.


Request for code

Dear author, I am very interested in your work on "Counterfactual Fairness Filter for Fair-Delay Multi-Robot Navigation". I would appreciate it if you could share your project code.

I appreciate your interest in our project.
We are preparing to release the source code and expect to have the code available by 31 August. We apologize for the delay in releasing the code.


Update 2016-01-18-segwit-wallet-dev.md

BIP141 states: "The only item in scriptSig is hashed with HASH160" under the section titled: "Witness program nested in BIP16 P2SH"

ACK


Add a ByteBufHttpData that is backed by ByteBuf and use it in THttpSe…

…rvice.
This is a straw-man's proposal for allowing internal logic, like a thrift or grpc service layer, to take advantage of ByteBuf for faster response writing. What do you think?

@trustin PTAL

@trustin I'm not sure how to interpret the sites build failure. I guess it doesn't like that I split the RequestContext into an external and internal API, is there a better pattern for it?

@anuraaga It currently relies on simple textual pattern matching on the generated .html files, so some of them may be false positives. Let me take a close look tomorrow.

Updated - changed both internal APIs to abstract classes, which allows me to keep the new methods in protected scope, which is a bit better than public. The site build failure still happens since I think it's only looking at the classes, not the method scope. What do you think a good workaround is?

Protected methods are also part of public API because a user can use/override it. Let me think a little bit about this..

@anuraaga What about just adding RequestContext.alloc()? We already have RequestContext.eventLoop() which exposes Netty API there, it seems like some services need to use the allocator and it is not as unsafe as exposing Channel.

@trustin thanks - seems reasonable to me, and tried to document the caveats in the javadoc, let me know if it sounds ok. I also learned that mockito doesn't call interface default methods, which makes sense since it doesn't call abstract ones either, but somewhat dirties the sanctity of interfaces...

Ah also FYI, the reason I learned about the interface behavior is that an exception during encodeException causes an infinite response (infinite loop in unit tests) - defensively catching and closing the connection is probably a good idea but wasn't sure so didn't add to this PR.

Thanks for your patience. Merged finally. :-)

FYI, the reason I learned about the interface behavior is that an exception during encodeException causes an infinite response (infinite loop in unit tests) - defensively catching and closing the connection is probably a good idea but wasn't sure so didn't add to this PR.

I'm not sure I understood this fully. How does it trigger an infinite response?

Yeah nevermind I thought a little more and it's just a symptom of unit tests with futures - if an exception happens in a weird place the future is never completed, but this only happens in tests so it's fine.

@anuraaga OK. Thanks for explaining. :-)


Redis spec fix

 https://github.com/Azure/azure-sdk-for-python/pull/801

 https://github.com/Azure/azure-sdk-for-node/pull/1903

 https://github.com/Azure/azure-sdk-for-ruby/pull/474


build vignettes into package

inst/doc

i think we've decided that most vignettes would live more properly in powstreams


tugboatrc seems to override with_machine_options in bad ways

Despite not setting an image default in .tugboatrc, and setting an image_name within machine_options, it seems that imageid is defaulting to 0.
~/.tugboatrc
---
authentication:
  client_key: XXXX
  api_key: YYYY
ssh:
  ssh_user: jblack
  ssh_key_path: /home/jblack/.ssh/id_rsa
  ssh_port: '22'
defaults:
  region: 4

linuxguru::simple_stack
require 'chef_metal_fog'

with_driver 'fog:DigitalOcean', :compute_options => {
   ¦ :digitalocean_api_key => Chef::Config[:digital_ocean_api_key],
   ¦  ¦:digitalocean_client_id => Chef::Config[:digital_ocean_client_id]
}

with_chef_server 'https://chef.linuxguru.net',
   :client_name => Chef::Config[:node_name],
   :signing_key_filename => Chef::Config[:client_key]

with_machine_options(
   :bootstrap_options => {
   ¦  image_name: 'Ubuntu 14.04 x64',
   ¦  region_name: 'New York 2',
   ¦  key_name: 'jblack'
   }
)

machine 'testbox' do
   tag 'itsname'

root@comet
~$ chef-client -r 'linuxguru::stack_simple'
[2014-09-16T22:50:40-07:00] WARN:

SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the middle
attacks.
To fix this issue add an entry like this to your configuration file:
  # Verify all HTTPS connections (recommended)
  ssl_verify_mode :verify_peer

  # OR, Verify only connections to chef-server
  verify_api_cert true

To check your SSL configuration, or troubleshoot errors, you can use the
knife ssl check command like so:
  knife ssl check -c /etc/chef/client.rb

Starting Chef Client, version 11.16.2
resolving cookbooks for run list: ["linuxguru::stack_simple"]
Synchronizing Cookbooks:

linuxguru
apache2
iptables
logrotate
pacman
apt
asterisk
build-essential
unimrcp
yum
bind
bind9
chef-client
cron
chef-server
docker
aufs
modules
device-mapper
git
dmg
windows
chef_handler
runit
yum-epel
golang
homebrew
lxc
dpkg_autostart
sysctl
ohai
elasticsearch
ark
7-zip
gitolite
perl
hostname
hostsfile
iptables-ng
java
jenkins
kibana
mysql
yum-mysql-community
nfs
line
openvpn
rsyslog
selinux
ssh-keys
sudo
swap
td-agent
users
Compiling Cookbooks...
Converging 1 resources
Recipe: linuxguru::stack_simple

machine[testbox] action converge[2014-09-16T22:51:24-07:00] WARN: Mismatched key size!  /home/jblack/.ssh/id_rsa is 4096 bytes, desired is 2048 bytes.  Use action :regenerate to force key regeneration.

creating machine testbox on fog:DigitalOcean:df6b7ab16f7acfd50d15fa2a46d1cc5d
image_name: "Ubuntu 14.04 x64"
region_name: "New York 2"
key_name: "jblack"
region_id: 4
image_id: 0
size_id: 4
private_networking: false
backups_enabled: false
key_path: "/home/jblack/.ssh/id_rsa"
tags: {"Name"=>"testbox", "BootstrapId"=>"https://chef.linuxguru.net/nodes/testbox", "BootstrapHost"=>"comet", "BootstrapUser"=>"jblack"}
flavor_name: "512MB"
flavor_id: 66
ssh_key_ids: [174936]
name: "testbox"
================================================================================
Error executing action converge on resource 'machine[testbox]'
================================================================================

Excon::Errors::NotFound
Expected([200]) <=> Actual(404 Not Found)
excon.error.response
:body          => "{"status":"ERROR","error_message":"You specified an invalid image for Droplet creation.","message":"You specified an invalid image for Droplet creation."}"
:headers       => {
"CF-RAY"        => "16b3082e13be11d7-SJC"
"Cache-Control" => "no-cache"
"Connection"    => "keep-alive"
"Content-Type"  => "application/json; charset=utf-8"
"Date"          => "Wed, 17 Sep 2014 05:51:26 GMT"
"Server"        => "cloudflare-nginx"
"Set-Cookie"    => "__cfduid=d88e2b3dafbd7571ecdd7ce6004089ea71410933086411; expires=Mon, 23-Dec-2019 23:50:00 GMT; path=/; domain=.digitalocean.com; HttpOnly"
"Status"        => "404 Not Found"
"X-Rack-Cache"  => "miss"
"X-Request-Id"  => "42ec76c3d5a9c5226611f48154f82148"
"X-Runtime"     => "0.236418"
}
:local_address => "<IP_ADDRESS>"
:local_port    => 35763
:remote_ip     => "<IP_ADDRESS>"
:status        => 404
Resource Declaration:
In /var/chef/cache/cookbooks/linuxguru/recipes/stack_simple.rb
22: machine 'testbox' do
23:    tag 'itsname'
24: end
25:
Compiled Resource:
Declared in /var/chef/cache/cookbooks/linuxguru/recipes/stack_simple.rb:22:in `from_file'
machine("testbox") do
action :converge
retries 0
retry_delay 2
guard_interpreter :default
chef_server {:chef_server_url=>"https://chef.linuxguru.net", :options=>{:client_name=>"comet", :signing_key_filename=>"/etc/chef/client.pem"}}
driver "fog:DigitalOcean"
machine_options {:bootstrap_options=>{:image_name=>"Ubuntu 14.04 x64", :region_name=>"New York 2", :key_name=>"jblack"}}
cookbook_name "linuxguru"
recipe_name "stack_simple"
attribute_modifiers [["tags", #Proc:0x000000021ae990@/var/lib/gems/1.9.1/gems/cheffish-0.8.2/lib/cheffish.rb:149]]
end

Results in:
Running handlers:
[2014-09-16T22:51:26-07:00] ERROR: Running exception handlers
Running handlers complete
[2014-09-16T22:51:26-07:00] ERROR: Exception handlers complete
[2014-09-16T22:51:26-07:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 46.625909816 seconds
[2014-09-16T22:51:26-07:00] ERROR: machine[testbox] (linuxguru::stack_simple line 22) had an error: Excon::Errors::NotFound: Expected([200]) <=> Actual(404 Not Found)
excon.error.response
  :body          => "{\"status\":\"ERROR\",\"error_message\":\"You specified an invalid image for Droplet creation.\",\"message\":\"You specified an invalid image for Droplet creation.\"}"
  :headers       => {
    "CF-RAY"        => "16b3082e13be11d7-SJC"
    "Cache-Control" => "no-cache"
    "Connection"    => "keep-alive"
    "Content-Type"  => "application/json; charset=utf-8"
    "Date"          => "Wed, 17 Sep 2014 05:51:26 GMT"
    "Server"        => "cloudflare-nginx"
    "Set-Cookie"    => "__cfduid=d88e2b3dafbd7571ecdd7ce6004089ea71410933086411; expires=Mon, 23-Dec-2019 23:50:00 GMT; path=/; domain=.digitalocean.com; HttpOnly"
    "Status"        => "404 Not Found"
    "X-Rack-Cache"  => "miss"
    "X-Request-Id"  => "42ec76c3d5a9c5226611f48154f82148"
    "X-Runtime"     => "0.236418"
  }
  :local_address => "<IP_ADDRESS>"
  :local_port    => 35763
  :remote_ip     => "<IP_ADDRESS>"
  :status        => 404

[2014-09-16T22:51:26-07:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
root@comet

This should be fixed with https://github.com/chef/chef-provisioning-fog/pull/87


Integrate Chromium

This PR integrates Chromium into Orbit by using Qt's WebEngine module.
It consists of 5 commits:

Prepare the windows docker containers for additional build requirements
Prepare the linux docker containers for additional build requirements
Adds Qt as a downstream fork of bincrafter's conan recipe. This was needed because the latest version of MSVC2017 lead to a couple of compilation errors which needed to be patched. This also updated Qt to the latest version.
Integrates the new webengine module into our conan recipe and require it in cmake. No further integration is done in this PR. This will come in multiple follow-up PRs.
Add an extra NOTICE file which only contains the licenses from Chromium dependencies. This is needed to simplify the licensing review. All these licenses are also added to our standard NOTICE file.

Hello to both of you,
since you both said you don't know how to review the conan-part some words from me on how to check my work:

The conan recipe (commit 3) was copied from bincrafters and changed. So it should contain a license file in the same directory and the license should be permissive. It's MIT in this case which is the only license I've seen so far for conan recipes. Apart from that I would say there is nothing more to review here.
The conan-integration (commit 4) mostly proves itself by compilation and running tests. But there are some things which can be verified. Every self.requires-call in the conanfile should specify a recipe revision (that's the hash after the pound sign). If it's not there then conan will choose the latest available revision and that might break things. Furthermore the lockfile changes can be roughly checked for validity. These are created by a script, so there is not much that can go wrong, but sometimes package changes slip in here which are unrelated to the actual change. In this case we change the Qt-package. So the lockfile-changes should resemble that. The diff shows the change of the qt-package and a change for the jom-package. jom is Qt's build system, so a new version was needed for the new Qt version. This is fine.

Thanks for the review by the way!
Henning


t2.micro instances in ECS guide are too anaemic

The ECS guide/script starts t2.micro instances. These instance types operate with CPU credits. Once the credits are exhausted, the machine grinds to a halt until sufficient time passes for credits to be replenished. This makes these instances types a poor choice for experimentation, since the dramatic performance degradation can be mistaken for a problem with weave scope/net.
cc @2opremio

Yep, noticed this in https://github.com/weaveworks/scope/issues/897 but AFAIK only t2.micro instances are covered by the free tier. We could add a warning mentioning that a beefier type of instance will be needed to anything running for more than a couple of hours.

A warning in the setup script? Won't that get drowned by the general noise?
We may also want to add some pointers for finding out whether VMs are being throttled.

A warning in the setup script? Won't that get drowned by the general noise?

I meant the guide but we could do both. In fact we will be able to show it more explicitly when we replace the script with Cloudformation.

We may also want to add some pointers for finding out whether VMs are being throttled.

I don't myself know how to do this but I will look into it.

I don't see a good reason to work around this, I think we should just use m3 or other type of instances of substantial size.

I don't see a good reason to work around this, I think we should just use m3 or other type of instances of substantial size.

Only t2.micro instances are covered by the free tier. Remember it's a guide which people probably will use for testing, we don't want them to spend money if necessary.

Sure, but may be that is less important whether they will spend a few
dollars or not... they will have card on file at this point anyway.
On Wed, 8 Jun 2016, 09:54 Alfonso Acosta<EMAIL_ADDRESS>wrote:

I don't see a good reason to work around this, I think we should just use
m3 or other type of instances of substantial size.
Only t2.micro instances are covered by the free tier. Remember it's a
guide which people probably will use for testing, we don't want them to
spend money if necessary.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/guides/issues/181#issuecomment-224529069,
or mute the thread
https://github.com/notifications/unsubscribe/AAPWS8eL3ZDq8v0GtidS6hJwPrvEAs0cks5qJoMrgaJpZM4IvJ8U
.

they will have card on file at this point anyway.

I don't think we should be assuming this

Another use run into this https://weaveworks.slack.com/archives/weave-users/p1466154335000239
However, he is using t2.micro instances in production, using larger instances apparently isn't an option for him.

When I set up my account a few years ago, I remember I couldn't do much
before I added a card.
On Fri, 17 Jun 2016, 10:09 Alfonso Acosta<EMAIL_ADDRESS>wrote:

they will have card on file at this point anyway.
I don't think we should be assuming this
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/guides/issues/181#issuecomment-226719792,
or mute the thread
https://github.com/notifications/unsubscribe/AAPWS0ifyXMt36Nm1eJMm5qiWmNVVm9uks5qMmRYgaJpZM4IvJ8U
.

Yes, I meant we shouldn't be assuming that people can spend money away even if the card is added.

Yes, I meant we shouldn't be assuming that people can spend money away even if the card is added.

Ok, that's true.

In any case, we should start working on #175 and figure out some nice UX. Current page is a bunch of screenshot, and it can be turned into a much more enhanced experience, where people will learn information like what's being discussed here. We can also consider merging it with the current plain text guide or linking in some cleaver way.

Perhaps we should add a note somewhere explaining the symptoms and linking to instructions for discovering when instances have been throttled.


Add media queries for post objects!

I had a great 1:1 with @docal56 this morning and he mentioned how posts will have set widths in Buffer for Business! I'd love to follow on with this for the Individual and Awesome area post objects, too! For now, we might do this in Style Guide and once we're ready to rebuild these components, we might use what we've got in the Style Guide! :smile:
cc: @emily-plummer @KatieLo @federicoweber @lorenzvs @msanroman @alvarezmelissa87 @pioul

Hey, folks! I'm closing this one up for now -- keen to reflect on this a little more with our priorities! 😄 Happy to re-open if necessary!


Integration of tbDex into Current Testing Frameworks for Web5

Introduction
This issue aims to explore and discuss the integration of tbDex into our existing testing strategies for Web5. Our objective is to ensure comprehensive testing coverage, enhancing the reliability and stability of our releases.
Context
As part of our release process, we conduct extensive tests to guarantee the flawless functionality of our SDKs. The OSE team is primarily responsible for initial test creation, while the Open Source Programs team extends these tests in various dimensions.
Specific Areas for Integration
1. Bundler Bonanza

URL: Bundler Bonanza
Objective: To conduct acceptance tests for Web5 across diverse environments such as Node, Browser, ESM, CJS, React Native, Vite, etc.
Proposal: Consider incorporating tbDex into the Bundler Bonanza framework.

2. Code Snippet System

URL: Developer Site
Overview: Our developer site features executable code snippets, ensuring their relevance and accuracy.
Action: Plan to include tbDex code snippets on the developer site, necessitating similar testing rigor.

3. Browser Tests for Tutorials

URL: Tutorials
Current Practice: We conduct basic tests on tutorials to ensure basic interactivity and functionality.
Suggestion: Extend these tests to include tbDex, ensuring seamless integration and functionality.

Key Questions and Considerations

Consistency in Approach: Should the approach to testing tbDex mirror that of Web5?
Multi-Language Support: How can we integrate multi-language support within the Code Snippet system effectively?
Interdependency Challenges: What are the potential challenges in co-locating tbDex and Web5? Are additional polyfills necessary?
Testing Standards for tbDex: What constitutes the minimum acceptable testing criteria for tbDex within the Bundler Bonanza?

Going to be handled as more comprehensive initiative in https://github.com/TBD54566975/open-source-programs/issues/131


Segmentation fault: 11

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Mac OS X 10.14.6
TensorFlow installed from (source or binary): Using pip
TensorFlow version (or github SHA if from source): 2.3.0

Command used to run the converter or code if you’re using the Python API
If possible, please share a link to Colab/Jupyter/any notebook.
python3 tensorflow/lite/python/tflite_convert.py --output_file=model-float.lite --output_format=TFLITE --inference_type=FLOAT --inference_input_type=FLOAT --input_shape="1,224,224,3" --input_array="serving_default_input_1" --output_array="StatefulPartitionedCall" --mean_value=0 --std_dev_value=1 --saved_model_dir=/Users/z004njq/Projects/save_models/mobilenetv4-exp-1004-export/ --experimental_converter=True

The output from the converter invocation
2020-07-28 13:29:05.763703: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN)to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2020-07-28 13:29:05.781147: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x14dc421f0 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-07-28 13:29:05.781174: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-07-28 13:29:14.581147: I tensorflow/core/grappler/devices.cc:78] Number of eligible GPUs (core count >= 8, compute capability >= 0.0): 0 (Note: TensorFlow was not compiled with CUDA or ROCm support)
2020-07-28 13:29:14.581230: I tensorflow/core/grappler/clusters/single_machine.cc:356] Starting new session
2020-07-28 13:29:14.677045: I tensorflow/core/grappler/optimizers/meta_optimizer.cc:816] Optimization results for grappler item: graph_to_optimize
2020-07-28 13:29:14.677069: I tensorflow/core/grappler/optimizers/meta_optimizer.cc:818]   function_optimizer: Graph size after: 1835 nodes (1614), 2696 edges (2475), time = 64.086ms.
2020-07-28 13:29:14.677092: I tensorflow/core/grappler/optimizers/meta_optimizer.cc:818]   function_optimizer: function_optimizer did nothing. time = 2.02ms.
I0728 13:29:16.315555<PHONE_NUMBER>11424 lite.py:624] Using experimental converter: If you encountered a problem please file a bug. You can opt-out by setting experimental_new_converter=False
2020-07-28 13:29:16.359263: W tensorflow/compiler/mlir/lite/python/tf_tfl_flatbuffer_helpers.cc:313] Ignored output_format.
2020-07-28 13:29:16.359292: W tensorflow/compiler/mlir/lite/python/tf_tfl_flatbuffer_helpers.cc:316] Ignored drop_control_dependency.
Fatal Python error: Segmentation fault

Current thread 0x00007fff6b6d45c0 (most recent call first):
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/lite/python/wrap_toco.py", line 38 in wrapped_toco_convert
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/lite/python/convert.py", line 199 in toco_convert_protos
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/lite/python/convert.py", line 574 in toco_convert_impl
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/lite/python/lite.py", line 633 in convert
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/lite/python/lite.py", line 900 in convert
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/lite/python/lite.py", line 1076 in convert
  File "tensorflow/lite/python/tflite_convert.py", line 239 in _convert_tf2_model
  File "tensorflow/lite/python/tflite_convert.py", line 623 in run_main
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/absl/app.py", line 250 in _run_main
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/absl/app.py", line 299 in run
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/tensorflow/python/platform/app.py", line 40 in run
  File "tensorflow/lite/python/tflite_convert.py", line 640 in main
  File "tensorflow/lite/python/tflite_convert.py", line 644 in <module>
Segmentation fault: 11

Also, please include a link to the saved model or GraphDef
mobilenetv3-exp-1004-export.zip
Failure details
If the conversion is successful, but the generated model is wrong,
state what is wrong:

Producing wrong results and/or decrease in accuracy
Producing correct results, but the model is slower than expected (model generated from old converter)

RNN conversion support
If converting TF RNN to TFLite fused RNN ops, please prefix [RNN] in the title.
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Can you provide the model / a minimal reproducer please?

I had included the saved model before, it's available at: https://github.com/tensorflow/tensorflow/files/4991052/mobilenetv3-exp-1004-export.zip

Apologies, it was not showing properly in the original message due to formatting.

Thank for your correcting the formatting, I am looking forward to solving the issue and understand the underlying cause.

@dipendra009 Can you please share a standalone code to reproduce the issue? I am sharing a gist that you can use and update later part of the code. Here is the gist with your model. Thanks!

I have already uploaded the saved model file and the code I am using is tensorflow/lite/python/tflite_convert.py from TF 2.3.0 as mentioned in the issue. The model is successfully loaded by the converter but it gives the segmentation fault while trying to convert it to tf-lite format.

Sorry for the late update. I can reproduce and working on a fix for the issue.
Thanks for reporting the issue and sorry for the delay

Sorry for the late update. This should be fixed now on the master branch.


M02-LABNAME: Configure agent pools and understanding pipeline styles

Contact Details
No response
What happened?
Last screenshot needs to be replaced as it show a windows-latest agent and according to the instructions it should be ubuntu-latest.
Lab
Configuring agent pools and understanding pipeline styles
Relevant screenshots
paste here 😉
Do you want to help us? 👏

[ ] Create a Pull Request by following this project's Contribution Guide

Thanks @tiagocostapt!


Nerd cli hangs on some api calls

Nerd calls authentication for listing the cluster in several cases. The endpoint is currently really slow (i've seen times up to 30 seconds).

I think it's nice to show the cli is doing stuff on the background
Actual Behavior
Currently it's just blank, like the process hangs.
Steps to Reproduce the Problem

Login in using a nerdalize account shows this issue the most.

Same for catalog files fetching, a timeout should always be added (see https://medium.com/@nate510/don-t-use-go-s-default-http-client-4804cb19f779)


add google-style and refactor

Add google-style linter rules
Refactor
Add Gemfile.lock to .gitignore

While I think there is a lot of value in having a consistent contributor/user experience across Google's ruby repos, I'm not convinced every rule works equally well for samples. I'd be really interested in hearing everyone's thoughts about the rules. Some in particular I'm questioning for this context are

%w[string string] vs ["string", "string"]
the Style/GuardClause cop
Metrics/LineLength - how does docsite handle long lines, what are its limits, etc.

This is amazing @TheRoyalTnetennba.
Responding to questions:

%w[string string] vs ["string", "string"]

I prefer ["string", "string"] given it's easier to parse in a sample.

the Style/GuardClause cop

Could you provide more background here?

Metrics/LineLength - how does docsite handle long lines, what are its limits, etc.

When samples are long a user has to scroll horizontally. I think the sample column length is 80, but I can't recall where we document this.

Add Gemfile.lock to .gitignore

We still used this to help keep a consistent test given Gemfile's don't specify a specific version. We'd need to use pessimistic versioning.

Swinging by with some +1's

%w[string string] vs ["string", "string"]

+1 to @frankyn
This includes %i[ for symbols ] as well, I prefer [:foo, :bar] for Google's code samples

Add Gemfile.lock to .gitignore

+1 to @frankyn
That said, I would be happy to be convinced otherwise ~ what's the case for ignoring lock files?
It's pretty important for us to be able to reproduce working samples. If the reason is to ensure our samples continue to work with latest (sans lock), I would argue the way to fix this is to make sure we rm Gemfile.lock; bundle install in CI scripts. If it starts failing, at least the debugger can get themselves back to a working state first. tl;dr there are other approaches which don't require ignoring the lock file.

Reverted to ["string", "string] [:symbol, :symbol] notation
Enforced braces for chaining blocks
Reverted Gemfile.lock

This is probably out of scope for this PR, but is there a way we are keeping track of what samples list dependency versions and which don't? How would we know if a sample no longer works if a user naively installs latest gem version b/c the sample doesn't specify?

I don't think we have a dependency tracker for samples that list dependencies or not. At least I've never seen one.

@frankyn regarding Style/GuardClause currently we are using the following rules:

# bad
def test
  if something
    work
  end
end

# good
def test
  return unless something
  work
end

# also good
def test
  work if something
end

# bad
if something
  raise 'exception'
else
  ok
end

# good
raise 'exception' if something
ok

Personally, I would prefer to read this. I felt it was worth asking if y'all thought that in, the context of samples, it might be better to more consistently write in a
if something
  work
end

style

Thanks @TheRoyalTnetennba,
I'd prefer having in samples:
if something
  work
end

Burn Style/GuardClause with fire.

Regarding Gemfile.lock, normally I advocate .gitignoreing them in most cases except for production-destined "final" products. This is because we want to be able to test against the latest dependencies, to ensure we find out about broken dependency updates. (Otherwise our users will find those before we will). But @beccasaurus 's argument about giving debuggers a known good starting point, is well taken. I'd just say that it then becomes very important that we bundle update in our CI scripts.

But @beccasaurus 's argument about giving debuggers a known good starting point, is well taken. I'd just say that it then becomes very important that we bundle update in our CI scripts.

If we're not bundle updating in CI scripts, or might not, then I'm super +1 adding them to .gitignore. It's a blunt but very functional correction. So maybe I was wrong. Simply not having the .lock file is a very effective strategy. Except ~ yeah, it's really nice to be able to get back to a working state.

We still used this to help keep a consistent test given Gemfile's don't specify a specific version. We'd need to use pessimistic versioning.

We have been warned. I would hate to see us, as a result, make our version numbers super pessimistic in our Gemfiles.
If the goal is to test that new users have a working experience, versions should only be specified when there's an explicit reason to, right?
Rebecca's...
Advice for production systems:

Use Gemfile.lock and be very mindful of versions at all times! While also bumping consistently because security!

Advice for developers:

Think about locking your dependencies to major versions (minor for 0.x), or else know that they will one day explode.

 Versions are for the weak. Bring on the pain!   📍 You are here

@tbpg could spanner api be enabled?

@TheRoyalTnetennba I enabled the Spanner API for cloud-samples-ruby-test-2.

Anyone have access to the 2.5 logs? I can't see why this is failing

Looks like we're all green. Could I get a review? No rush, it's a big PR.

Rubocop is currently unable to enforce our rules for the following:

Style/GuardClause
Style/IfUnlessModifier
Style/LineEndConcatenation
Style/Next

Rubocop is currently unable to enforce our rules for the following:

What are our rules for those? I'm not seeing much in the style guide but maybe I'm looking at the wrong one or I'm just not processing it correctly?
I enabled each in turn and looked at the results:

Style/GuardClause - no failures
Style/IfUnlessModifier - some of these look legit
Style/LineEndConcatenation - some of these look legit too, in particular the bigquery and spanner samples where the queries could be heredocs
Style/Next - one failure that may be a subtle violation of the style guide that I'm just missing:

dialogflow/context_management.rb:34
    if context.parameters
      puts "Fields:"
      context.parameters.fields.each do |field, value|
        if value.string_value
          puts "\t#{field}: #{value.string_value}"
        end
      end
    end

It wants that to be next unless context.parameters, which seems reasonable to me.

It's not really relevant to this PR per se but I noticed a lot of keyword args as I was reading through the samples. Are keyword args a thing that people actually use out in the world? Basically I'm wondering all the same things as we talked about in this thread.

@bleything by "rules", I just meant, the desired style based on the discussion in this PR. These are all cops w/out the appropriate EnforcedStyle options - we can only disable/enable them.
Style/GuardClause - it seemed to me that consensus was to disallow if possible. If this is possible, I don't know how. I've currently settled for disabling it.
Style/IfUnlessModifier - love to hear your thoughts on it. Personally, I like it. Others didn't seem to, and the broader trend of opinions seem to be anti-code-golfy? :woman_shrugging: not that it's the code-golfiest of conventions... Anyway, the mention of lack of enforcement options stems from only being able to turn the cop off or on, no EnforcedStyle: spread_that_conditional_out option.
Style/LineEndConcatenation - no enforced style options. No use_pluses_instead_of_backslashes as others mentioned, and no make_it_a_heredoc.
Style/Next - again, love to hear your thoughts. I would prefer to see this enabled. I don't know that it would be a good idea to require people to favor conditionals over next, but if that's what we wanted, we can't using any of the currently provided EnforcedStyle options.
Incidentally, there doesn't seem to be a way to require people to avoid the safe navigation operator. You can only disable Style/SafeNavigation

I'd like to explore enabling Metrics/LineLength at some point, along with any other Metrics cops that make sense. I do want this to happen in a different PR. The diff is big enough as is and LineLength isn't really the same kind of discussion as other style issues.

@TheRoyalTnetennba: thanks for the explanation, that all makes a lot of sense. I didn't realize how late I was to this PR and how much I'd missed, I'm sorry for the added noise.

@bleything no worries. This matters to all of us and I'm happy for the feedback

Anyone willing to give me the much-coveted LGTM

@frankyn You beat me by 20 seconds!!

lol!!! :smile: @dazuma


HNC slow to become Ready on 1.21 and earlier

I've found that HNC becomes Ready on 1.22 after about 10s, while on 1.20 and 1.21 it takes about 80+ seconds. Adding a Readiness probe seems to solve the problem - I'm not sure why, since "no readiness probe" is supposed to be equivalent to "always ready" and this does seem to be the case in 1.22. But I can't find any evidence of a bug that got fixed in 1.22 and I'm surprised that something this obviously wrong would have survived so long.
Either way, the solution seems pretty straightforward and I'll make the fix today.
/cc @erikgb

This looks vaguely related to https://github.com/kubernetes/kubernetes/issues/101064 but that bug was introduced in 1.21 (whereas I'm seeing the same behaviour in 1.20) and besides, it doesn't seem to be the same issue.

Hmm, https://github.com/kubernetes/kubernetes/pull/98376 looks possibly related

https://github.com/kubernetes/kubernetes/pull/101738 looks like a more likely candidate - introduced in 1.22, designed to fix https://github.com/kubernetes/kubernetes/issues/99979. It explicitly was not backported to 1.21 (https://github.com/kubernetes/kubernetes/pull/102681#issuecomment-859026916).

Note that I verified that the healthz and readyz endpoints were actually working well this entire time. E.g. I started a busybox, pinged the endpoints directly, and verified that they returned ok long before the containers actually became Ready. The fact that adding a readiness probe with no change to the container fixes the problem is more evidence IMO that this is a workaround to a K8s-side problem.


Update bigtable.column_family to use V2 protos

Uses #1912 as a base.
Note that {Create,Update,Delete}ColumnFamily messages all collapse to ModifyColumnFamilies.

Rebased after merging #1912.


Add common ArtifactLoaders to make nnbench provide them out of the box

This is a follow up issue to #92
A few ArtifactLoaders come to mind.

AWS
Azure
GCP
fsspec

Is covered by #94 .


Migration Feature Gate: Testnet

https://github.com/anza-xyz/feature-gate-tracker/issues/56

https://explorer.solana.com/address/Config1111111111111111111111111111111111111?cluster=testnet


Powerlevel9k colors are washed out in integrated terminal

Not sure how relevant this would be for other people, but the colors of the Default powerlevel9k settings in zsh appear washed out in the Integrated terminal making them a bit difficult (for me at least) to read.

For comparison, here's the Dracula theme:

Totally, I didn't do adequate testing for the terminal, thanks for bringing it up! I'll fix it up for the next release

Hey! I think I might have fixed this. Can you please double check? Thanks!

Looks a bit better, but the blacks are a bit off. I took a shot at adjusting the ansiBlack colors a bit.
Published Theme:

Adjustments:
"terminal.ansiBlack": "#333333",
"terminal.ansiBrightBlack": "#787878",

⚠ I changed the brightBlack value because of that autocomplete plugin using it for its "this is the next set of characters in the auto complete" as illustrated in the screenshot.
I think the blacks are the only things that need changing.
I checked the pygmalion theme as well and it looks good.

Ok I think I got it sorted, please reload and let me know what you think :)

Yeah! Looking great now. Thank you!

Excellent. Thanks!


seriously consider reverse proxy to provide permalink urls

Overall goals which IMHO could be achieved:

hide any "platform/web ui platform dependent" URLs behind, so to have

https://dandiarchive.org/dandiset/000003/draft instead of https://gui.dandiarchive.org/#/dandiset/5e6eb2b776569eb93f451f8d ATM;
https://deploy-preview-341--gui-dandiarchive-org.netlify.app/dandiset/000006/draft instead of https://deploy-preview-341--gui-dandiarchive-org.netlify.app/#/dandiset/000006/draft (no #/ fragment)

use permalinks as much as possible in the user facing (web) UI. That would make it easier for users to embed references to dandisets (in tweets, documentation, blog posts, etc) without fear that the URLs would mutate whenever web UI frontend also changes
keep those URLs congruent with the API (which we hope would be stable)
"bind" services to the (web) UI, so that for a particular deployment it would be possible to contact API (or may be even a service like girder) from the server name, e.g. to have

dandiarchive.org/api for dandiarchive.org
myownlabdandi.org/api for myownlabdandi.org
localhost:8092/api for the localhost:8092 deployed locally.
This would largely address the need for /server-info (#316) although it would remain a good idea regardless

I am not yet sure either it should be just an overall reverse proxy instead of the redirector we have at http://dandiarchive.org or to become more specific to the web UI on the netlify.  I am thinking more of a front-end  http://dandiarchive.org since

netlify is just a service we are using. Eventually we should provide "turnkey" deployment of the "personal" dandiarchive instances. For that most likely with docker compose/clear recipe on "howto"

One immediate concern with above -- I am not sure if it would play nicely with netlify preview deployments (an immediate idea: our main reverse proxy could provision /netlify-X/ to proxy to https://deploy-preview-X--gui-dandiarchive-org.netlify.app/)
If on netlify level -- details on how to establish reverse proxy, with an example for an /api mapping could be found at  https://docs.netlify.com/routing/redirects/rewrites-proxies/:
Proxy to another service
Just like you can rewrite paths like /* to /index.html, you can also set up rules to let parts of your site proxy to external services. Let's say you need to communicate from a single-page app with an API on https://api.example.com that doesn't support CORS requests. The following rule will let you use /api/ from your JavaScript client:
/api/*  https://api.example.com/:splat  200

Now all requests to /api/... will be proxied through to https://api.example.com straight from our CDN servers without an additional connection from the browser. If the API supports standard HTTP caching mechanisms like ETags or Last-Modified headers, the responses will even get cached by our CDN nodes.

couldn't just let it go.  Here is a demonstration of reverse proxy setup for "DANDI publish" version: https://dandi.centerforopenneuroscience.org/ where you can browse the netlify PR instance and https://dandi.centerforopenneuroscience.org/api (/api also works via http://) for API calls -- from the same "server"

An example of working /api query
$> curl --silent -X GET "https://dandi.centerforopenneuroscience.org/api/dandisets/000006/versions/0.200714.1807/assets/" -H "accept: application/json" -H "X-CSRFToken: WIAs3781WY4OZyx3JRL267KTaFDXQuh4xw3TimmzIle7dG5nkVOedLpV8G9orVVa" | jq . | head -n 5
{
  "count": 53,
  "next": "http://publish.dandiarchive.org/api/dandisets/000006/versions/0.200714.1807/assets/?page=2",
  "previous": null,
  "results": [

The use of fragment (/#/) in the URL (thus relying on web UI browser client side queries based on fragment, not on e.g. part of the URL path) though makes it difficult (if not impossible?) to reverse proxy to those pages. Or may be it is simply due to some redirect to /#/ the platform mandates

I made dedicated `/hash/` rev proxied path which demonstrates it (`#` is not passed to the server)
$> wget -S -O- https://dandi.centerforopenneuroscience.org/hash/ | head
--2020-07-14 17:39:48--  https://dandi.centerforopenneuroscience.org/hash/
Resolving dandi.centerforopenneuroscience.org (dandi.centerforopenneuroscience.org)... <IP_ADDRESS>
Connecting to dandi.centerforopenneuroscience.org (dandi.centerforopenneuroscience.org)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response...
  HTTP/1.1 301 Moved Permanently
  Date: Tue, 14 Jul 2020 21:39:48 GMT
  Server: Netlify
  Cache-Control: public, max-age=0, must-revalidate
  Content-Length: 1063
  Content-Type: text/html; charset=UTF-8
  Etag: "da4d27f941124705afdc01f14e394d15-ssl"
  Strict-Transport-Security: max-age=31536000
  X-Robots-Tag: noindex
  Age: 0
  X-NF-Request-ID: 5f9af44e-7003-4c97-8ad3-8c6d78b637db-4113663
  Location: /
  Keep-Alive: timeout=5, max=100
  Connection: Keep-Alive
Location: / [following]
--2020-07-14 17:39:48--  https://dandi.centerforopenneuroscience.org/
Reusing existing connection to dandi.centerforopenneuroscience.org:443.
HTTP request sent, awaiting response...
  HTTP/1.1 200 OK
  Date: Tue, 14 Jul 2020 21:39:48 GMT
  Server: Netlify
  Cache-Control: public, max-age=0, must-revalidate
  Content-Length: 1063
  Content-Type: text/html; charset=UTF-8
  Etag: "da4d27f941124705afdc01f14e394d15-ssl"
  Strict-Transport-Security: max-age=31536000
  X-Robots-Tag: noindex
  Age: 2
  X-NF-Request-ID: 5f9af44e-7003-4c97-8ad3-8c6d78b637db-4113982
  Vary: Accept-Encoding
  Keep-Alive: timeout=5, max=99
  Connection: Keep-Alive
Length: 1063 (1.0K) [text/html]
Saving to: ‘STDOUT’

-                              0%[                                            ]       0  --.-KB/s               <!DOCTYPE html><meta charset=utf-8><meta http-equiv=X-UA-Compatible content="IE=edge"><meta name=viewport content="width=device-width,initial-scale=1"><link rel=icon href=/favicon.ico><title>DANDI Archive</title><link rel=stylesheet href="https://fonts.googleapis.com/css?family=Roboto:100,300,400,500,700,900"><link rel=stylesheet href=https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>href=/css/app.331b4330.css rel=preload as=style><link href=/css/chunk-vendors.a64f58f8.css rel=preload as=style><link href=/js/app.96849cfc.js rel=preload as=script><link href=/js/chunk-vendors.98b889ae.js rel=preload as=script><link href=/css/chunk-vendors.a64f58f8.css rel=stylesheet><link href=/css/app.331b4330.css rel=stylesheet>We're sorry but the DANDI Archive doesn't work properly without JavaScript enabled. Please enable it to continue.

%

altogether
- it is relatively easy to provide reverse proxied setup (my apache config is below)
- reliance on the fragment in web client limits applicability

Relevant apache setup
falkor# cat /etc/apache2/sites-available/dandi.centerforopenneuroscience.org.conf
######## #### #### #### ### ### ## ## # # # # # * * *
##  Just an attempt for DANDI reverse proxy setup
#   See https://github.com/dandi/dandiarchive/issues/427

Define dandiui deploy-preview-341--gui-dandiarchive-org.netlify.app/
#Define dandiui gui.dandiarchive.org
Define dandiapi publish.dandiarchive.org

<VirtualHost *:80>
 Define hosturl dandi.centerforopenneuroscience.org
 Include /etc/apache2/sites-available/_base_/public-base.conf

 ProxyRequests Off
 <Proxy *>
     Order deny,allow
     Allow from all
 </Proxy>

 SSLProxyEngine on

 ProxyPass /api/ http://${dandiapi}/api/
 ProxyPassReverse /api/ http://${dandiapi}/api/

 ProxyPass /swagger/ http://${dandiapi}/swagger/
 ProxyPassReverse /swagger/ http://${dandiapi}/swagger/

 ProxyPass /accounts/ http://${dandiapi}/accounts/
 ProxyPassReverse /accounts/ http://${dandiapi}/accounts/

</VirtualHost>

<VirtualHost <IP_ADDRESS>:443>
 Define hosturl dandi.centerforopenneuroscience.org

 SSLEngine On
 SSLCertificateFile /etc/letsencrypt/live/${hosturl}/fullchain.pem
 SSLCertificateKeyFile /etc/letsencrypt/live/${hosturl}/privkey.pem

 Include /etc/apache2/sites-available/_base_/public-base.conf

 ProxyRequests Off
 <Proxy *>
     Order deny,allow
     Allow from all
 </Proxy>

 SSLProxyEngine on

 # Having # in the target url doesn't work -- causes infinite redirect loop
 #ProxyPass / "https://${dandiui}/#/"
 #ProxyPassReverse / "https://${dandiui}/#/"

 # but not for simple GET request, so it might be somehow inflicted
 # but the platform trying to access original URL, which is somewhat demonstrated
 # with following which causes redirect to the top page (with #)
 ProxyPass /hash/ "https://${dandiui}/#/"
 ProxyPassReverse /hash/ "https://${dandiui}/#/"

 ProxyPass /api/ http://${dandiapi}/api/
 ProxyPassReverse /api/ http://${dandiapi}/api/

 ProxyPass / "https://${dandiui}/"
 ProxyPassReverse / "https://${dandiui}/"

</VirtualHost>
#
######## #### #### #### ### ### ## ## # # # # # # # #

I think this could use some more discussion. I am not sure precisely what problems are solved by a reverse proxy. I think much of the recent work in abstracting the form of URLs used in a given deployment solves much of what was brought up in this issue, and I also believe shedding the redirector can perhaps solve the rest.

@yarikoptic, could you weigh in on how much of the original issue report is still valid now?


Pushing bike speed

Describe the bug
In the cycle profiles (all of them), GrahphHopper sometimes selects route where bike needs to be pushed, whether due to legal constraints (access) or pyhsical constraints (smoothness).
Funnily, biking durations still beat walking durations by a lot.
To Reproduce
Pseudo route with access forbidden -- ETA 3 min.
Same route walking profile -- ETA 10 min.
Cycle route with via node -- ETA 4 min.
If bikers would not run when pushing bike, they would get another route?

Thank you for this catch. This way is tagged like:
        way.setTag("highway", "track");
        way.setTag("surface", "concrete");
        way.setTag("vehicle", "agricultural");

The problem here is that we overwrite our PUSHING_SECTION speed by the later evaluated surfaceSpeed  :cry:. I'm going to provide a PR for a fix later today.


Feature Request: IP-Adapter

Hi Searge. Thanks for all your hard work, especially the new FreeU integration in 4.2.
I was just wondering if IP-Adapter is supported in the custom_checkpoint for Controlnet Models Selector. I tried using it, but I'm not sure if there is an effect.

There was a discussion here from sd-webui-controlnet. They adapted it from a Japanese repository here. There is also a standalone IPAdapter workflow for SDXL here by cubiq. So, it seems to be possible already.
On a side note, is there a way to ''break out'' or preserve the latent data during the ControlNet processing phase? Thanks again.

I'll look into ip adapter for potential inclusion in a future update.

Hello, has there been any update on this? I too would really like to use IPAdapter with your workflow 👍


Hello, may I ask why I can't find any information about this paper of yours?

Thank you for your interest in our paper. It's not on arXiv or similar repositories yet due to external factors but is set to be published around June.


iOS 9 content blockers block events from tracking

In iOS 9, if a user has a content-blocker installed (in my testing it was 1Blocker installed) MixPanel events will not be sent. The content-blocker will see it as a different domain and it gets blocked.

Unsure of how to get around this issue but this is obviously effecting a significant number of users, especially for our mobile web app.

Hi @himynameisdave, unfortuantely 1Blocker and other content blockers explicitly block requests to api.mixpanel.com - the only way around this would be to proxy the calls to your own server via the mixpanel.serverURL property: https://github.com/mixpanel/mixpanel-iphone/blob/master/Mixpanel/Mixpanel.h#L78-L88
Or alternatively, to implement Mixpanel on your server side.

For the JS lib, you can set a custom tracking URL with the api_host config property (https://github.com/mixpanel/mixpanel-js/blob/7bf72bf4dc00e1406cc756bea675db57865cb286/src/mixpanel-core.js#L101). If you'd like more personalized guidance for your situation, I'd suggest writing in to<EMAIL_ADDRESS>We're always happy to help!

@tdumitrescu & @jaredmixpanel thanks for the speedy reply!


C++ compilation of rule '//tensorflow/python:tf_session_helper' failed

I am trying to compile build_pip_package on Ubuntu 12.04 with gcc 4.8, but it gives an error during compilation:
$ bazel build -c opt //tensorflow/tools/pip_package:build_pip_package --verbose_failures

tensorflow/python/client/tf_session_helper.cc:418:41: error: 'PyArray_SHAPE' was not declared in this scope
   dims.push_back(PyArray_SHAPE(array)[i]);

ERROR: /home/local/ANT/x/tensorflow/tensorflow/python/BUILD:666:1: C++ compilation of rule '//tensorflow/python:tf_session_helper' failed: gcc failed: error executing command
  (cd /home/local/ANT/x/.cache/bazel/_bazel_x/29843df2d2b24eaae7acd7ee881b7bec/tensorflow && \
  exec env - \
    INTERCEPT_LOCALLY_EXECUTABLE=1 \
    PATH=/home/local/ANT/x/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games:/home/local/ANT/x/bin:/home/local/ANT/x/bin:/home/local/ANT/x/bin:/home/local/ANT/x/bin:/home/local/ANT/x/bin:/home/local/ANT/x/bin:/home/local/ANT/x/bin \
  /usr/bin/gcc -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -fPIE -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 -DNDEBUG -ffunction-sections -fdata-sections '-std=c++0x' -iquote . -iquote bazel-out/local_linux-opt/genfiles -isystem google/protobuf/src -isystem bazel-out/local_linux-opt/genfiles/google/protobuf/src -isystem tools/cpp/gcc3 -isystem external/jpeg_archive/jpeg-9a -isystem bazel-out/local_linux-opt/genfiles/external/jpeg_archive/jpeg-9a -isystem external/png_archive/libpng-1.2.53 -isystem bazel-out/local_linux-opt/genfiles/external/png_archive/libpng-1.2.53 -isystem external/re2 -isystem bazel-out/local_linux-opt/genfiles/external/re2 -isystem third_party/gpus/cuda -isystem bazel-out/local_linux-opt/genfiles/third_party/gpus/cuda -isystem third_party/gpus/cuda/include -isystem bazel-out/local_linux-opt/genfiles/third_party/gpus/cuda/include -isystem third_party/eigen3 -isystem bazel-out/local_linux-opt/genfiles/third_party/eigen3 -I/usr/include/python2.7 -no-canonical-prefixes -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' '-frandom-seed=bazel-out/local_linux-opt/bin/tensorflow/python/_objs/tf_session_helper/tensorflow/python/client/tf_session_helper.pic.o' -MD -MF bazel-out/local_linux-opt/bin/tensorflow/python/_objs/tf_session_helper/tensorflow/python/client/tf_session_helper.pic.d -fPIC -c tensorflow/python/client/tf_session_helper.cc -o bazel-out/local_linux-opt/bin/tensorflow/python/_objs/tf_session_helper/tensorflow/python/client/tf_session_helper.pic.o): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1: gcc failed: error executing command
  (cd /home/local/ANT/x/.cache/bazel/_bazel_x/29843df2d2b24eaae7acd7ee881b7bec/tensorflow && \
  exec env - \
    INTERCEPT_LOCALLY_EXECUTABLE=1 \
    PATH=/home/local/ANT/x/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games:/home/local/ANT/x/bin:/home/local/ANT/x/bin:/home/local/ANT/x/bin:/home/local/ANT/x/bin:/home/local/ANT/x/bin:/home/local/ANT/x/bin:/home/local/ANT/x/bin \
  /usr/bin/gcc -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -fPIE -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 -DNDEBUG -ffunction-sections -fdata-sections '-std=c++0x' -iquote . -iquote bazel-out/local_linux-opt/genfiles -isystem google/protobuf/src -isystem bazel-out/local_linux-opt/genfiles/google/protobuf/src -isystem tools/cpp/gcc3 -isystem external/jpeg_archive/jpeg-9a -isystem bazel-out/local_linux-opt/genfiles/external/jpeg_archive/jpeg-9a -isystem external/png_archive/libpng-1.2.53 -isystem bazel-out/local_linux-opt/genfiles/external/png_archive/libpng-1.2.53 -isystem external/re2 -isystem bazel-out/local_linux-opt/genfiles/external/re2 -isystem third_party/gpus/cuda -isystem bazel-out/local_linux-opt/genfiles/third_party/gpus/cuda -isystem third_party/gpus/cuda/include -isystem bazel-out/local_linux-opt/genfiles/third_party/gpus/cuda/include -isystem third_party/eigen3 -isystem bazel-out/local_linux-opt/genfiles/third_party/eigen3 -I/usr/include/python2.7 -no-canonical-prefixes -Wno-builtin-macro-redefined '-D__DATE__="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' '-frandom-seed=bazel-out/local_linux-opt/bin/tensorflow/python/_objs/tf_session_helper/tensorflow/python/client/tf_session_helper.pic.o' -MD -MF bazel-out/local_linux-opt/bin/tensorflow/python/_objs/tf_session_helper/tensorflow/python/client/tf_session_helper.pic.d -fPIC -c tensorflow/python/client/tf_session_helper.cc -o bazel-out/local_linux-opt/bin/tensorflow/python/_objs/tf_session_helper/tensorflow/python/client/tf_session_helper.pic.o): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
Target //tensorflow/tools/pip_package:build_pip_package failed to build
INFO: Elapsed time: 3.223s, Critical Path: 2.46s

I can compile that particular source file after adding this to the gcc command:
-I/usr/local/lib/python2.7/dist-packages/numpy/core/include/

But when I rerun the bazel command it tries to compile it again without the needed include path and fails.

@markusdr: what version of numpy do you have installed, by any chance?  I have a suspicion that it's probably earlier than numpy 1.8.2 :)

I believe it's numpy 1.9.2.

Gotcha -- that version does have PyArray_SHAPE.  Do you have any other numpy directories installed on your machine that might be interfering somehow?
If not, can you try changing tf_session_helper.cc to switch from PyArray_SHAPE to PyArray_DIMS ? (That one is available in earlier versions of numpy and apparently PyArray_SHAPE is an alias)

Right, the installation is using /usr/include/python2.7/, which doesntt have PyArray_SHAPE.
It is defined in /usr/local/lib/python2.7/dist-packages/numpy/core/include.
How can I tell bazel to use the latter python installation path?

When I add the correct numpy include path to the tensorflow/python/BUILD file it seems to compile, but at the end it complains:
$ bazel build -c opt //tensorflow/tools/pip_package:build_pip_package
tensorflow/python/BUILD:666:1: in cc_library rule //tensorflow/python:tf_session_helper:
The include path '/usr/local/lib/python2.7/dist-packages/numpy/core/include' references
a path outside of the execution root..

OK, this workaround gets it to compile:
cd third_party
ln -s /usr/local/lib/python2.7/dist-packages/numpy/core/include/numpy .

Then add -Ithird_party to the includes in tensorflow/python/BUILD and tensorflow/tensorflow.bzl

There may be a way to infer the numpy header  location at compile time. I'll take a look.

@markusdr
how to add -Ithird_part to tensorflow/python/BUILD and tensorflow/tensorflow.bzl
thanks

@auroua Here is the diff:
diff --git a/tensorflow/python/BUILD b/tensorflow/python/BUILD
-    copts = numpy_macosx_include_dir + ["-I/usr/include/python2.7"],
+    copts = numpy_macosx_include_dir + ["-Ithird_party", "-I/usr/include/python2.7"],

diff --git a/tensorflow/tensorflow.bzl b/tensorflow/tensorflow.bzl
-                    ] + ["-I/usr/include/python2.7"],
+                    ] + ["-Ithird_party", "-I/usr/include/python2.7"],

Alternatively, I could have symlinked /usr/local/lib/python2.7/dist-packages/numpy/core/include/numpy into /usr/include/python2.7, but I didn't have root access.

@markusdr
I have a problem in #251. Can you help me to solve this problems.
I tried you method but it not working.
thanks

Does @markusdr 's changes still apply? I don't think that the diff corresponds to the current version of tensorflow/python/BUILD anymore. Suggestions?

Symlinking the numpy headers in util/python worked for me. python_config took care of the rest.

If you sync to HEAD you should be able to use ./configure to select which python to use.

@vrv Is configure auto detecting the location of numpy headers now (from distconfig possibly?). If not, this issue will still exist.

I believe so:  ./configure will call python_config.sh (https://github.com/tensorflow/tensorflow/blob/master/configure#L25) which gets the numpy headers from https://github.com/tensorflow/tensorflow/blob/master/util/python/python_config.sh#L64

Confirmed. python_config auto detects the location of numpy. None of the changes suggested in this thread are needed anymore as long as python has access to the correct numpy location. Thanks, @vrv.


Bulletproofing

Additional variables (VRID and INTERFACE) to improve flexibility in varying environments. Variable checks and improved process checking in main entrypoint script.

Sorry about the delay, I was away last week


Provide getting started with release trains mapping to Spring Boot generation

I am working with the Wavefront team (Hi @shavidissa) on improving their getting started documentation for the Spring Boot starter. The starter has optional support for tracing via Sleuth so we need to tell users how they can include that in their existing project.
The doc sandbox is here. We're considering reusing this section of the project's page.
I'd like as much as possible to not include too much information for existing projects. Each release announcement has a section that describes how to get started for both Maven and Gradle.
Would it be possible to get a page somewhere that summarises all that, that is:

Build instructions to get started
Mapping between Spring Cloud release train and Spring Boot generation

In an ideal world, rather than the name of the release train, it would be very nice to get the actual version that we have to use (latest service release or milestone, depending on the situation).
Thanks!

Mapping between Spring Cloud release train and Spring Boot generation

This would be possible to retrieve programmatically using
https://spring-cloud-info.cfapps.io/docs/spring-cloud-info.html#_spring_cloud_version_given_spring_boot_version
I wonder if we could make a page that would allow the user to either pick the Boot version or Cloud version and then automatically generate the Maven and Gradle getting started info.
Would that help @snicoll?

This would be possible to retrieve programmatically using
https://spring-cloud-info.cfapps.io/docs/spring-cloud-info.html#_spring_cloud_version_given_spring_boot_version

I had forgotten about that one!

I wonder if we could make a page that would allow the user to either pick the Boot version or Cloud version and then automatically generate the Maven and Gradle getting started info.

Yeah that would be more than ideal of course!

Thank you, @snicoll and @ryanjbaxter!

This would be possible to retrieve programmatically using
https://spring-cloud-info.cfapps.io/docs/spring-cloud-info.html#_spring_cloud_version_given_spring_boot_version

This is cool! I will use this :)

I wonder if we could make a page that would allow the user to either pick the Boot version or Cloud version and then automatically generate the Maven and Gradle getting started info.

Yeah that would be more than ideal of course!

This would be great for Spring Cloud and all the other dependencies in spring.io. It will make it easier for the user to get this info in one place. As Stéphane showed, I think this information is already captured in https://start.spring.io/actuator/info.

@shavidissa

This is cool! I will use this :)

So does that get you what you need?  Or is there still missing information?

@ryanjbaxter No. The endpoint doesn't provide what was requested in the original description, specifically
Would it be possible to get a page somewhere that summarises all that, that is:

* Build instructions to get started
* Mapping between Spring Cloud release train and Spring Boot generation

@snicoll I have updated the page, please let me know what you think!

Thanks @ryanjbaxter. Just to make sure I got this right, you mean https://spring.io/projects/spring-cloud#getting-started right?

@snicoll yup!

Hi @ryanjbaxter,
Thanks a lot! This is much better and user friendly. We have it in our Wavefront docs :)

Looks good indeed, I think this can be closed. Thanks a lot for the quick turnaround!

Great thanks!


Not giving the daily steps count. Its giving the 0 steps on stream

I am listening to the stream and its giving me the 0 steps. even I am walking. My phone built in step counter counts my steps

You need to go into the app settings and enable the permissions for ACTIVITY_RECOGNITION and alarms.

I am listening to the stream and its giving me the 0 steps. even I am walking. My phone built in step counter counts my steps
permissions
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
<uses-permission android:name="android.permission.ACTIVITY_RECOGNITION" />
<uses-permission android:name="android.permission.SCHEDULE_EXACT_ALARM"/>

try on samsung a14


[httphandler/data] get canceled payment status for disbursement and receivers metrics

What
Get canceled payments for disbursement and receiver metrics
Why
statistics metrics on FE
Known limitations
N/A
Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).
[x] This PR's title starts with the name of the package, area, or subject affected by the change.

Thoroughness

[x] This PR adds tests for the new functionality or fixes.
[ ] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[x] This is not a breaking change.
[x] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[ ] Does the deployment work after merging?

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr82.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr82.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr82.previews.kube001.services.stellar-ops.com


chore: documentation

Codecov Report

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

@@           Coverage Diff           @@
##           master      #48   +/-   ##
=======================================
  Coverage   98.67%   98.67%
=======================================
  Files          10       10
  Lines         605      605
=======================================
  Hits          597      597
  Misses          8        8

Continue to review full report at Codecov.

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

@JohannesMerz I think we should use this state of the documentation already. We can adjust it later on :)


Error in a private net; Chain database in Chains/privnet is for a different private network than the current container.

Hi, I just tried to start neo-python and I have trouble with setting up private net in a docker container.
I was following  this guy's way. https://medium.com/@nickfujita/neo-dev-environment-setup-tutorial-e495f5364ada
I finished setting up the container but when I put command neopy,
Privatenet useragent '/NEO:2.7.4/', nonce:<PHONE_NUMBER>
[E 180410 06:51:52 prompt:1044] Chain database in Chains/privnet is for a different private network than the current container. Consider deleting the Chain directory with 'rm -rf /root/.neopython/Chains/privnet/privnet*'.
root@c0a7d9680785:/neo-python#

this error occured.  Why is this error occured and how can I fix it? The error is still happening even if I deleted the container once. docker rm -f neo-privatenet
I'm currently installing Docker on Windows10pro and using command line.

I'll check...

Thanks for reporting! I actually made some kind of error in the latest CoZ/neo-privatenet Docker image. Fixed it and pushed a new image. Please update with docker pull cityofzion/neo-privatenet.
Thanks a lot for reporting!


Drop production base path from fallback link

The type of this PR is: Fix

Description
Regardless of environment (staging, local) the trove fallback link on our homepage goes to production. This PR removes the base path to keep the user in their current environment.

@erikdstock - Going to close this as it appears to be stale. Feel free to reopen if you still need it!


Bugfix: Input Datatime config schema

Description:
Has_at_least_one_key_value only works if parameter are optional
Example entry for configuration.yaml (if applicable):
input_datetime:
  both_date_and_time:
    name: Input with both date and time
    has_date: true
    has_time: true
  only_date:
    name: Input with only date
    has_date: true
  only_time:
    name: Input with only time
    has_time: true

Checklist:

[x] The code change is tested and works locally.

@tinloaf It would work on required parameters as well, but than voluptuous catches it first if not given.

I just saw that https://home-assistant.io/components/input_datetime/ already listed the parameters as being optional. Thanks for catching this!


swap  aex-meme

Swap failed: [ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"data":{"code":-32603,"message":"Internal Error - BadGatewayError. Please report a bug at https://github.com/aurora-is-near/aurora-relayer/issues","data":{"host":"r002.westcoast.us.testnet.internal.aurora.dev","cf-ray":"6e7cda0e425d16ec-IAD"}}}}'

Same as #216
Please don't open the same issue several times.