AWS Toolkit for Visual Studio Deployment Green but returns 404

We normally deploy our site via AWS Toolkit for Visual Studio, so far without issue.
Upon recent deploys the AWS Console is showing Green with "Environment update completed successfully.".
However when accessing the site via the Route53 Url of https://xxxxxx.com or the EB Url - xxxxxx-env.xxxxxx.us-west-1.elasticbeanstalk.com it is returning
Error for https://XXXX.com
This xxxxx.com page can’t be found
No web page was found for the web address: https://xxxxx.com/
HTTP ERROR 404
Error for xxxxxxxx-xxxxxxxxx.us-west-1.elasticbeanstalk.com
This xxxxxx-env.xxxxxx.us-west-1.elasticbeanstalk.com page can’t be found
No web page was found for the web address: http://xxxxxxxxxxx-xxx.xxxxxxxx.us-west-1.elasticbeanstalk.com/
Go to http://elasticbeanstalk.com/
Cannot see any obvious issue. The project works locally in Development and Production mode set.
Expected Behavior

The deployment should continue as normal, succeed, provide a Green status and then be available via the url.
Current Behavior

Status is Green.
Url returns 404 for direct environment URL and Route53 URL.
Context

Unable to access instance after successful deployment
logs.txt
Your Environment

AWSSDK.Core version used:
Service assembly and version used:
Operating System and version:
Visual Studio version:
Targeted .NET platform:

AWSSDK.Core 3.3.24
.NET Core 2.0
Visual Studio 2017 4.7.03056
.NET Core Info

.NET Core version used for development:
.NET Core version installed in the environment where application runs:
Output of dotnet --info:
Contents of project.json/project.csproj:

.NET Core 2.0.8
Target .NET runtime 4.0
'dotnet --info'
.NET Core SDK (reflecting any global.json):
Version:   2.1.300-preview2-008533
Commit:    996eb6c92c
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.17134
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\2.1.300-preview2-008533\
Host (useful for support):
Version: 2.1.0-preview2-26406-04
Commit:  6833f3026b
.NET Core SDKs installed:
1.0.4 [C:\Program Files\dotnet\sdk]
1.1.0 [C:\Program Files\dotnet\sdk]
2.0.0 [C:\Program Files\dotnet\sdk]
2.0.2 [C:\Program Files\dotnet\sdk]
2.1.102 [C:\Program Files\dotnet\sdk]
2.1.201 [C:\Program Files\dotnet\sdk]
2.1.300-preview2-008533 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.0-preview2-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.0-preview2-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 1.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.0-preview2-26406-04 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Although I've tagged this as the toolkit, I think this needs the service team to look at - I'll raise an internal ticket to alert them to the issue,

I think the issue was my csproj file. If anyone faces this issue, then please check all files and folders are correct after any merges.


Swiper React  calculates the height zero when rendering for the first time

Swiper Version: 6.5.7

React Version: 17.0.1

I'm using REACT version of swiper with autoHeight  true like this:
<Swiper
slidesPerView   = {1}
grabCursor      = {true}
pagination      = {{ clickable: true }}
effect          = "fade"
autoHeight      = {true}
>

but when page rendered calculates the height zero for the first time but if resize the window or go to another slide its work perfectly you can see it for one slide in 2 situation when page startup and when i resize browser or change slide and go back to first slide

Would still be good to see live CodeSandbox/Stackblitz example

Closing due to inactivity, missing demo and/or no responses from issue author


frontend: Prefill fields in request form

Some of the fields in the request form can be prefilled when the page is opened in order to improve usability. The source chain can be set to the currently connected chain. The target address can be set to the address of the current account.
See also: https://github.com/beamer-bridge/beamer/issues/365

The first part is already done. Second is still relevant and part of UX discussions.

Closing in favor of https://github.com/beamer-bridge/beamer/issues/878


README.md needs instructions for how to manually update the lib for developers

Seriously, either keep it simple or tell people how to do it. I've tried:
# on the ev3
mkdir ev3dev
# on development laptop:
<make changes>
scp ev3dev/*.py robot@ev3dev.local:ev3dev/
# on ev3
sudo mv *.py /usr/lib/python3/dist-packages/ev3dev/

but after that I only get python errors (e.g. instantiating motors fails).

What I do in order to test things out, is
ssh robot@ev3dev
git clone https://github.com/rhempel/ev3dev-lang-python
cd ./ev3dev-lang-python

Now, you can do your changes to the local copy. When you do
import ev3dev.ev3 as ev3

while in the ev3dev-lang-python folder, it should import from local folder instead of from system-installed one.

Unfortunately this won't work for installed stuff. The openrobertalab is a package with a service run by systemd.

Well, the installed stuff is installed with apt-get, so I guess the only correct way to test things would be to uninstall the system package first, then run ./setup.py install from the cloned repo.

Nah, just need to get the right files to the right locations. I'll check the layout of the src tree and the installed files.

It sounds like you're looking for the equivalent of npm link from the JavaScript world... I can't seem to find anything similar in Python package managers though.

You can do
ssh robot@ev3dev
git clone https://github.com/rhempel/ev3dev-lang-python
cd ./ev3dev-lang-python
sudo python3 setup.py install

Then whenever you make changes run the "sudo python3 setup.py install" again

@ensonic can you confirm that does the trick for openrobertalab

@dwalton76 if I follow your instructions, it will be installed to /usr/local/lib/python3.4/dist-packages/ where as the debian package is in /usr/lib/python3/dist-packages/. That usually is a recipe for disaster (especially so since setup.py cannot easily uninstall stuff).

Right you do end up with two copies which is not ideal but I've never run into issues with it since the copy in /usr/local/lib/python3.4/dist-packages/ is found first via your PYTHON_PATH.  I just rm -rf the /usr/local/lib/python3.4/dist-packages/ copy if I want to go back to using the version installed via the deb.  Most of the time I just end up using the copy installed via setup.py though as I'm continuing to do dev on it.
You could always uninstall the copy from the debian package to avoid having two copies.

I can't uninstall the python library, since that will install packages depending on it. I'll send a PR for the docs with the gist of this thread.

I believe this is the currently recommented list of options:

Update PYTHON_PATH
Do development from the directory of a local copy of the library (current working directory is searched for modules)

Feel free to update this with more. I'm not going to close this immediately as it would be nice to add complete instructions to the README.

no underscore in PYTHONPATH environment variable name.

Updated. I could've sworn there was one 🤔


Suppress HUGE diffs

I would like Midje to suppress big diff output so I don't get a screenful of OMG!
Some sort of setting so that this could be overridden in a fact would be great (you might want to see a massive diffed output on occasion).

This is somewhat handled in the post 1.7 printing.


documentation: fix link to license

The link to the license was broken, so I changed it to the license for this repository.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix: typo in image modal's caption markup

Jira
N/A
Summary
Fixed a typo in the image modal caption's markup that causes the caption text to not render.
Details
slot="footer" was accidentally used on the figcaption container, which is a goof from an older mockup.
How to test
Run the branch locally and make sure image modal examples have captions.

@mikemai2awesome I'm all for getting as many eyes on a PR as we can but for super simple PRs like this, only one code reviewer is really needed. 😉

Verified fix working as expected - thanks @mikemai2awesome!


tests failing on rev. 81bbd2b04b5a322b

This is a bug in mastodon-graph that is fixed with https://github.com/mastodon-sc/mastodon-graph/pull/14

Fixed in 9b24d63f27e62f502c8690964b628f74c4652c99


How to fine-tune on custom dataset?

Hey guys, I have this classification dataset with currency denominations but I'm not sure how to use model-soup for fine-tuning. The way my dataset is structured is that I have several folders for each denomination and each folder has thousands of images. I have a train, valid, and test folder overall. Can someone help me with this please?

The example finetune.py may be helpful -- it's for imagenet but I believe the structure is similar


Remove trackupstream for Train+

Currently noone cares about that, lets stop the bleeding

@dirkmueller actually, we might need it after all, as announced during the last QBR

We'll restore one when one is needed.


Use DependentHandle or CWT for SilkMarshal.StringArrayToMemory

Instead of hoping for GC to catch on eventually, we should make the relation clear using DependentHandle (NET6+, thanks sergio) / CWT

How did you envision this working? StringArrayToMemory copies all of the data contained within the string array, so the lifetime of the returned memory is not dependent on the lifetime of its original array and vice versa, so there are no GC issues here really.

Closing per my previous comment.


Implement exporting span events as message/exception telemetry

Fixes https://github.com/Azure/azure-sdk-for-python/issues/21747
Fixes https://github.com/Azure/azure-sdk-for-python/issues/20281
Fixes https://github.com/Azure/azure-sdk-for-python/issues/16413
Fixes https://github.com/Azure/azure-sdk-for-python/issues/20111

API change check for azure-monitor-opentelemetry-exporter
API changes are not detected in this pull request for azure-monitor-opentelemetry-exporter


FIX: Small changes to fix PR #3747

Follow up changes to make PR #3747 just so. @Eric89GXL @agramfort

LGTM, I'll merge once the CIs come back happy (which they should)

Thanks @kdoelling1919


Fix skittles when flying under blue stim influence

From Commandaguy:

Is there a way for all the ticks to be displayed on the buildings even when I'm using a blue stim?

I haven't tested myself, but apparently this is broken.

Info to fix, cheers @BartKieviet

The BLDGTILE_XPATH is not correct due to the div direct after the td that is not present in non stimmed life.
I'm not touching the Xpath stuff with a ten-foot pole.


ci: 'MIT' license verification fail on permissive license

Describe the bug
PR #10885 contains files that are licensed "mit" ( see https://spdx.org/licenses/MIT.html). This is a much more permissive license than apache-2.0.  It should not make CI fail.
To Reproduce
Add a file wirh "SPDX-License-Identifier: mit" and run CI.
Expected behavior
CI license verification shall pass on  "SPDX-License-Identifier: mit".
Impact
CI of PR #10885, #10888 declared failed.
Screenshots or console output
PR #10885
Environment (please complete the following information):
Zephyr CI
Additional context

Any file going into the zephyr tree with a different license that the project license needs to be reviewed. This check in CI is currently not 'required' for merging and still under heavy development, so a maintainer can override this check after reviewing the warnings and determining that the files are ok.
Will add some text explaining the above in the comment posted by CI.

Reviewers usually do not review until the CI status is "passed".
Can this become a hint for reviewers and CI set to "passed"?


[eradicate] ignore # language= in commented-out-code rule (ERA001)

Fixes one common case cited on #6019

Summary
The commented-out-code rule (ERA001) from eradicate is currently flagging a very common idiom that marks Python strings as another language, to help with syntax highlighting:

This PR adds this idiom to the list of allowed exceptions to the rule.
Test Plan
I've added some additional test cases.

Do you mind pushing the test cases? I only see the code changes.
For reference: https://www.jetbrains.com/help/pycharm/using-language-injections.html

Sorry @charliermarsh , forgot to force-push after I amended the commit with the test cases.

No prob, thanks for the PR.

And looks like I need to fix the formatting... Working on it.

For reference: https://www.jetbrains.com/help/pycharm/using-language-injections.html

I've added some more test cases and fixed the regexp with the additional cases described here.

Thanks and welcome to the project.


[Exiv2] Add feature to enable BMFF support

Fixes #31777
Add feature bmff to enable BMFF support

[x] Changes comply with the maintainer guide
[ ] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Tesetd feature bmff successfully in the follwoing triplet:

x86-windows
x64-windows
x64-windows-static
x64-linux

Please remove the option.
https://github.com/microsoft/vcpkg/blob/75059166857a374297e5edd6e1e7a60912907a46/ports/exiv2/portfile.cmake#L40


refactor: rework FRAME codegen

Resolves #901

For all the other codegen, we don't indent the template tags

I think it helps with legibility. Certainly makes it easier for newcomers.

Unlike the rest of our formatting, though, dprint doesn't handle it, and so the indentation can get out of sync with the surrounding code.


Document Row#content

API doesn't make it clear how to get the data, so I think this should help.

Row is an ObjectProxy. This means that every property not defined on the ObjectProxy itself is proxied / forwared to the object that is content.
In order to get or set properties, you do not need to access content. You can just use the Row instance. You only need to acces the content object when one of its properties is shadowed by the proxy ('selected' for instance) or when passing it to an Ember Data Model as a relationship IIRC.

I think this is ok. Users should be aware that this property exists.

I think so too, but I was trying to say that a more elaborate description
would be in order. (?)
On Tue, Nov 1, 2016, 23:45 Offir Golan<EMAIL_ADDRESS>wrote:

Merged #250 https://github.com/offirgolan/ember-light-table/pull/250.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/offirgolan/ember-light-table/pull/250#event-844143643,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAy8TNfdIaJM9TCokl4cyUEXWz1dABckks5q58EngaJpZM4KmdcT
.

@buschtoens I updated the description to the following which is already in master:
  /**
   * Data content for this row. Since this class extends Ember.ObjectProxy,
   * all properties are forwarded to the content. This means that instead of
   * `row.content.foo` you can just do `row.foo`. Please note that methods are
   * not forwarded. You will not be able to do `row.save()`, instead, you would have
   * to do `row.content.save()`.
   *
   * @property content
   * @type {Object}
   */
  content: null

👍
On Wed, Nov 2, 2016, 09:58 Offir Golan<EMAIL_ADDRESS>wrote:

@buschtoens https://github.com/buschtoens I updated the description to
the following which is already in master:
/**   * Data content for this row. Since this class extends Ember.ObjectProxy,   * all properties are forwarded to the content. This means that instead of   * row.content.foo you can just do row.foo. Please note that methods are   * not forwarded. You will not be able to do row.save(), instead, you would have   * to do row.content.save().   *   * @property content   * @type {Object}   */
content: null
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/offirgolan/ember-light-table/pull/250#issuecomment-257807282,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAy8TOAembK6WF8dhn9FiS1qwQmpfFLPks5q6FCpgaJpZM4KmdcT
.


Added network label

Please provide a description of this PR:
With this, we can support weighted traffic routing to different networks.
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: httpbin
spec:
  host: httpbin
  trafficPolicy:
    loadBalancer:
      simple: LEAST_CONN
  subsets:
  - name: network1
    labels:
      topology.istio.io/network: cluster1
  - name: kubernetes
    labels:
      topology.istio.io/network: network2

To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
90dc0b69d0f66110424e98215778dc26804e26f0
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Generally LGTM.
How does this work for WorkloadEntry? We have an explicit network field there that should be translated into this label. Not sure if it is today

I think we'd need similar logic here:
https://github.com/istio/istio/blob/eea231b5a2a7d88258a73de903fe556d7c970bce/pilot/pkg/serviceregistry/serviceentry/conversion.go#L367

Yes, will add them

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
9953a3c43bae83e514669f0807002baa4949e8bd
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl Another look?

LGTM – the workloadentry part still needs a few things but we can iterate; this doesn't break anything

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
27ea8bec9f9e94ce8a861a2aa28d85fb0eabc11d
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

In response to a cherrypick label: new pull request created: #34548


RI cannot be applied to Spot VMs

[Enter feedback here]
Hello Team,
I believe RI cannot be applied to Spot VMs. However, there is no document and TSG mentioning it.
Could you help update the document and add some explanation regarding to this? Thank you!
Best regards,
Tina

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 43852e1b-711e-98e6-7f3e-e98578cad660
Version Independent ID: 71897988-d633-024c-209e-a02997ccf4e0
Content: Understand Azure Reserved VM Instances discount - Microsoft Cost Management
Content Source: articles/cost-management-billing/manage/understand-vm-reservation-charges.md
Service: cost-management-billing
Sub-service: reservations
GitHub Login: @bandersmsft
Microsoft Alias: banders

@LingYi-Wu Thanks for your comment! We will review and provide an update as appropriate.

Hello KrishnaG,
Thank you! Any update about this one? Is an ETA available?

https://github.com/MicrosoftDocs/azure-docs-pr/pull/246545
@LingYi-Wu Thanks for the suggestion. I've updated the article to state that Azure doesn't offer reservations for Spot VMs.
#please-close

Hello @bandersmsft,
Will you also update the article that displaying in different language?
Or it will take some time to sync?
https://learn.microsoft.com/zh-tw/azure/cost-management-billing/manage/understand-vm-reservation-charges

@LingYi-Wu All of our articles are sourced in EN-US. It takes about 5-10 business days for all localized languages to get localized and republished live.


Refactor leaf generation

This moves instantiation of the leaf generation rules to the main function, which makes future work to support generating different types of leaves (e.g. x509 certs) easier to implement. Probability of duplicates has been moved to a flag, and some minor code inlining makes code better co-located.

Codecov Report
Attention: Patch coverage is 0% with 11 lines in your changes missing coverage. Please review.

Project coverage is 28.62%. Comparing base (46ec9c2) to head (2fc54ee).
Report is 33 commits behind head on main.

Files
Patch %
Lines

hammer/hammer.go
0.00%
11 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #115      +/-   ##
==========================================
- Coverage   35.80%   28.62%   -7.18%
==========================================
  Files          16       31      +15
  Lines        1363     2683    +1320
==========================================
+ Hits          488      768     +280
- Misses        801     1828    +1027
- Partials       74       87      +13

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


44 / 5.000 Resultados de traducción .lua file for Spanish localization

First of all apologies for my English (google translator).
I attach a .lua file with the translations for Spanish.
If possible I would like them to be added to the addon.
Thank you.
Note: The extension has been changed to be able to attach the file.
esES.txt

@Stoytovisiao
Thank you for the contribution! I have created PR for it #279 however some strings are missing.
Please also join our discord for easier communication of further updates :)


{history} undefined

I am trying to follow the examples from 1.0.0-beta2 or even the readme.md from master.
If I do (in browser)
import {history} from 'react-router/lib/BrowserHistory';

React.render((
	<Router history={history}>
...

I get Uncaught Error: Invariant Violation: Server-side <Router>s need location, branch, params, and components props. Try using Router.run to get all the props you need
Turns out that history is undefined this way.
Even when I do
import BrowserHistory from 'react-router/lib/BrowserHistory';
React.render((
	<Router history={BrowserHistory}>
...

as other examples suggest, it doesn't work. I get
Warning: Failed propType: Invalid prop historysupplied toRouter, expected instance of History. Uncaught Error: Invariant Violation: A <Router> needs a valid Location
The only way I got it to work was with <Router history={new BrowserHistory()}> but this is definitely not in the examples.
Am I doing something wrong or are the docs outdated?

Are you using beta2 or the master branch? { history } isn't available yet in the npm package.

beta2 from npm. But I did look at the beta2 docs and they are incorrect: http://rackt.github.io/react-router/tags/v1.0.0-beta2.html

You are correct. They are incorrect. The PR that fixes that was merged to master. Meanwhile, you should initiate a new History object

Looks like in beta3 the docs are still incorrect.

I'm running into this same error even after trying <Router history={new BrowserHistory()}> using beta3
This is the entirety of my routing/rendering
import React from 'react'
import ReactDOM from 'react-dom'
import { Router, Route } from 'react-router';
import BrowserHistory from 'react-router/lib/BrowserHistory'
import App from './app.jsx'
import Dashboard from './dashboard.jsx'

ReactDOM.render(
  <Router history={ new BrowserHistory() }>
    <Route path='/' component={ App }>
      <Route name='dashboard' path='/dashboard/:filter' component={ Dashboard } />
    </Route>
  </Router>,
  document.getElementById('main-content')
)

@aflanagan Using beta3 you just

// lower case history is already an instance of browser history
import { history } from 'react-router/lib/BrowserHistory';

// ...
ReactDOM.render(
  <Router history={ history }>
    <Route path='/' component={ App }>
      <Route name='dashboard' path='/dashboard/:filter' component={ Dashboard } />
    </Route>
  </Router>,
  document.getElementById('main-content')
)

This project is moving fast and you should rely more on the source than the docs.

@BerkeleyTrue I started with
import { history } from 'react-router/lib/BrowserHistory'

and got the same error @terebentina did in beta2. I tried instantiating BrowserHistory myself per @terebentina's suggestion, but am still getting the same error.
If I set a breakpoint at the createElement call for the Router I can see that _reactRouterLibBrowserHistory.history is the history prop that's being passed in.
console.log(_reactRouterLibBrowserHistory.history instanceof History) // false

The _reactRouterLibBrowserHistory.history object looks like this
{
  changeListeners: Array[0]
  getScrollPosition: getWindowScrollPosition() {
  handlePopState: () { [native code] }
  isSupported: true
  location: null,
  parseQueryString: (str, options)
 __proto__: BrowserHistory
}

@aflanagan  Is there a reason you are sticking with beta2? If not then consider updating to beta3.

This project is moving fast and you should rely more on the source than the docs.

beta2 history module also only exports the class, no instances.
beta2 is way out of date, is missing a bunch of patches and does not follow docs very well.
@terebentina and @aflanagan  The reason {history} is undefined is because the browserHistory module in beta2 only exports a class called BrowserHistory. So when you tried import { history } from 'react-router/lib/BrowserHistory';  you are trying to read a property that is undefined. Its the same as trying to do:
var history = require('react-router/lib/BrowserHistory').history;
// when the module is defined as

export.BrowserHistory = BrowserHistory;

This has since been fixed and this issue should be closed.

@BerkeleyTrue, per my previous comment this issue still exists in beta3.
The beta3 docs show:
import { Router, Route } from 'react-router';
import BrowserHistory from 'react-router/lib/BrowserHistory';

React.render((
  <Router history={BrowserHistory}>
    <Route path="about" component={About}/>
    <Route path="dashboard" component={Dashboard}/>
  </Router>
), document.body);

But in reality (in beta 3), we need to do this:
import { Router, Route } from 'react-router';
import BrowserHistory from 'react-router/lib/BrowserHistory';

React.render((
  <Router history={new BrowserHistory()}>
    <Route path="about" component={About}/>
    <Route path="dashboard" component={Dashboard}/>
  </Router>
), document.body);

This issue should not be closed.

@BerkeleyTrue per my original comment I am using beta3 not beta2.

I'm running into this same error even after trying <Router history={new BrowserHistory()}> using beta3

Again, per my previous comment, regardless of whether I instantiate the BrowserHistory object myself
(new BrowserHistory()) or import the instance using
import { history } from 'react-router/lib/BrowserHistory'

the instanceof validation still fails
console.log(_reactRouterLibBrowserHistory.history instanceof History) // false

@aldendaniels any suggestions?

My apologies. My impression was that this issue was with beta2.
Which bundler are you using?

@BerkeleyTrue No problem. I'm using babelify/browserify.
One thing that I realized I did wrong when debugging this was checking that this instance type of the history object.
If I import the History module import History from 'react-router/lib/History' and check the instance type at the point where createElement is being called then my instanceof check passes as expected.
console.log(_reactRouterLibBrowserHistory.history instanceof History) // true

I realized I was comparing it to the browser's History class before. However...it's strange that when this same check runs as part of the prop validation that it is failing.

@aflanagan I have a theory. It could be that you have two instances of BrowserHistory (or History) Class. The one you import and the one react-router imports. In this case instanceof will fail. I'm not sure how you could verify this.

@aldendaniels Are you also using browserify?

@BerkeleyTrue I was just wondering that same thing. I'm not sure how to verify this either. If anyone has any thoughts on how to verify that please let me know.

You could try doing a global search in your bundler to see if the exports['default'] = BrowserHistory or  exports['default'] = History Comes up more than once.
You could also try to use something like disc to get a visual layout of the modules in your bundle.
Or try getting a webpack version up and running and see if you have the same issue.
The first two are not sure fire as you could overlook a module pretty easily. The third takes more effort and time but if it turns out it does work then you know for sure this is the issue. here is my webpack config for reference.

@aflanagan I was running into the same problem as you and falling back to commonjs require syntax seems to have fixed it. This is working for me.
var history = require('react-router/lib/BrowserHistory').history;

So, maybe this is a Babel issue?

@kjs3 - yup, switching back to commonjs syntax fixed it for me as well. :/
Not sure whether this should stay open here or whether I should file an issue with babel. I still don't have a clear picture of what is causing the error, though, like @BerkeleyTrue mentioned above, I suspect that there are multiple instances of BrowserHistory being imported. I have not yet had a chance to test this theory out.

@aflanagan, @kjs3 Look at the last lines of BrowserHistory.js
exports.history = history;
exports['default'] = BrowserHistory;

you can stick with es6 module syntax by doing
import { history } 'from 'react-router/lib/BrowserHistory';
...
<Router history={ history }>

or
import BrowserHistory from 'react-router/lib/BrowserHistory';
...
<Router history={ new BrowserHistory() }>

@aflanagan, sorry I didn't get back.
In the current version of babel, babel seems to do the right thing (try it out) so it's interesting that CommonJS syntax is fixing this for you.
ES6 syntax does work for me... I'm using browserify/babelify:
import BrowserHistory from 'react-router/lib/BrowserHistory';
<Router history={new BrowserHistory()}>

Maybe try blowing away node_modules and re-installing? Also run npm dedupe to check for duplicate copies of ReactRouter getting imported by dependencies. I'm really grasping at straws here though.

Getting the same with beta3. Tried everything from here and I still get the same as OP.
Warning: Failed propType: Invalid prop `history` supplied to `Router`, expected instance of `History`. Check the render method of `Provider`.
Uncaught Error: Invariant Violation: A <Router> needs a valid Location

If I log it before serving it to the Router, the oject looks ok
HashHistory {changeListeners: Array[0], location: null, queryKey: null}
changeListeners: Array[1]
getScrollPosition: getWindowScrollPosition() {...}
handleHashChange: () { [native code] }
location: Location
parseQueryString: (str, options) {...}
queryKey: null
__proto__: HashHistory

I use ES6 syntax, latest from browserify, babelify, watchify, uglify, and no server (as I am just building first a mock-up of the real application, with some UI, functionality and some routing around, for demo purposes to the client). Any other ideas? Thanks.

Seems like the common issue is the use of es6 modules and browserify. @stefanmihoc Can you try using commonjs require for history?

Like I mentioned in my previous comment I tried everything above, and also everything mentioned in similar raised issues that are related to this. require with or without .default, requiring/importing HashHistory and new-ing it, requiring/importing already constructed history directly etc.

Ok, so I have just found the culprit. The problem was indeed at bundling with browserify.
So, I have in my app the imports like this:
import { Router, Route, Link } from 'react-router';
import { history } from 'react-router/lib/HashHistory';

but I was using this kind of scripts to build the dependencies separately from the app (as watching a combined build with watchify would have been very slow):
  "scripts": {
    "builddep": "browserify -r classnames -r material-ui -r react -r react-redux -r react-router -r react-tap-event-plugin -r redux -r whatwg-fetch | uglifyjs -cm > lib/dependencies_bundle.js",
    "buildsrc": "browserify . -x classnames -x material-ui -x react -x react-redux -x react-router -x react-tap-event-plugin -x redux -x whatwg-fetch | uglifyjs -cm > lib/main.js",
    "watchsrc": "watchify . -x classnames -x material-ui -x react -x react-redux -x react-router -x react-tap-event-plugin -x redux -x whatwg-fetch -o lib/main.js -v -d",
    "test": "jest"
  },
  "browserify": {
    "transform": [
      [
        "babelify",
        {
          "stage": 0
        }
      ]
    ]
  }

So what was missing was the explicit requiring of react-router/lib/HashHistory in these scripts, like this:
    "builddep": "browserify -r classnames -r material-ui -r react -r react-redux -r react-router -r react-router/lib/HashHistory -r react-tap-event-plugin -r redux -r whatwg-fetch | uglifyjs -cm > lib/dependencies_bundle.js",
    "buildsrc": "browserify . -x classnames -x material-ui -x react -x react-redux -x react-router -x react-router/lib/HashHistory -x react-tap-event-plugin -x redux -x whatwg-fetch | uglifyjs -cm > lib/main.js",
    "watchsrc": "watchify . -x classnames -x material-ui -x react -x react-redux -x react-router -x react-router/lib/HashHistory -x react-tap-event-plugin -x redux -x whatwg-fetch -o lib/main.js -v -d",

If bundling like this (all scripts, app&dependencies, together):
    "buildsrcwithdep": "browserify . | uglifyjs -cm > lib/main.js",
    "watchsrcwithdep": "watchify . -o lib/main.js -v -d",

there are no problems.

@stefanmihoc that's a great hint! I use babelify via gulp tasks and I generate separate vendors.js based on package.json like this:
var dependencies = Object.keys(packageJson && packageJson.dependencies || {});

I had to manually add this line below:
dependencies.push('react-router/lib/HashHistory');

and it works. Strange thing.

I have the same problem, I get this error:
Module not found: Error: Cannot resolve module 'react-router/lib/HashHistory'
I can't find HashHistory and BrowserHistory anywhere in the project. Anyone has a solution for that?

@knowbody
It's gone in 1.0.0-beta4.
Now you get hash history by default (no need to specify it).
If you want the pushstate history, do this:
import { createHistory } from 'history'; // you need to install this package
let history = createHistory();

ok got it, just realised that after removing the old: 'react-router/lib/HashHistory' it still kept the history. Need to read more source code in the future. thanks @gaearon

sorry for the churn folks, docs are getting better as we approach 1.0 release. Hang in there.

Hey @knowbody Trying to get history into my react-router set-up to prevent the links outside of history errors, is this along the right lines if I'm not writing this the ES6 way?
var history = require('history/lib/createBrowserHistory').createHistory;
and then...
React.render((
	<Router history="{history}">
		<Route path="/"     component={HomeController}/>
		<Route path="about" component={AboutController}/>
		<Route path="blog"  component={BlogController}/>
		<Route path="work"  component={WorkController}/>
		<Route path="*"     component={NotFoundController}/>
	</Router>
), site);

I've done as much reading around as I can but this issue is probably the closest I've come to finding a solution.

@davetgreen something like this should do:
var BrowserHistory = require('history/lib/createBrowserHistory');

<Router history={new BrowserHistory}>...<Router />

@knowbody You sir, are a gentlemen. tips hat

@davetgreen sorry I was wrong :smile:
like this:
var createBrowserHistory = require('history/lib/createBrowserHistory');

<Router history={createBrowserHistory()} >...<Router />

@knowbody Thanks! Now I get the history object but now I have TypeError: history.listen is not a function. If it's beyond the scope of this issue I'll research it myself. :+1:

not sure where that happens. try to look at the current issues, if there is nothing then create a new issue

@davetgreen (@knowbody): I have the same problem. Did you find a solution for getting the TypeError?
 TypeError: history.listen is not a function

FYI: The readme example still says this import { Router, Route, Link, browserHistory } from 'react-router' .. Which is obviously wrong.

The readme example is against 2.0.0-RC, for which that syntax is absolutely correct.

Gotcha.. i just did the standard npm install.. which installed v^1.0.3. Had no idea that the readme was for 2.0. Makes sense now tho thanks.

Please update the readme file!

+1. This sent me down a bit of a rabbit hole. It seems unconventional that master is pointed to a version that isn't installed via npm, so a more explicit warning about what version master is on would probably be really helpful.

@wayspurrchen yea.. never seen this issue before. Shouldn't the README for 2.x branch be on 2.x branch and not master?

In most git repos, master is the latest version of the code, including any in progress, unreleased bits. It's generally where all active development is happening, so the code there may be unstable. But you come here to see what is being developed, that is the whole point of Github.  We, unfortunately, do not have a separate website for the project. If we did, I think this would end up being a lot clearer. I want to get that going shortly, since we get daily issues related to mismatched docs.

@timdorr That makes a ton of sense. I think the reason this hasn't been an issue on other project docs is in fact because their documentation is external.

Cool, @timdorr, thank you for the clarification. :)


docs: make projectId variable consistent in quickstart.js comments

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #135 🦕

@asrivas thank you for the contribution 👍


Deployment Host fix and Export Build/Image fix

Initial fix for resolving the following bugs:

#16 - self.__get_services() referred to a ConfigDict. This referenced the correct name as it was populated in the service dict.
#17 - the change from alias to key can be changed back if needed. When debugging, it appeared we were referencing the key name for the container_ships. When referencing the alias, it was taking the key not the provided alias by the user.

-                    container_ships[alias] = {}
+                    key = hosts.alias
+                    container_ships[key] = {}

Current coverage is 49.50%

Merging #18 into master will decrease coverage by -0.01% as of 2b2531d

@@            master    #18   diff @@
=====================================
  Files           33     33
  Stmts         3829   3830     +1
  Branches       898    898
  Methods          0      0
=====================================
  Hit           1896   1896
  Partial        277    277
- Missed        1656   1657     +1

Review entire Coverage Diff as of 2b2531d

Powered by Codecov. Updated on successful CI builds.

Submitting another pull requests with tests.


Size options for custom list.

This PR fixes #9077.
I found this issue tricky because it could affect a lot of elements in the UI. For instance, a lot of form components use this custom list internally.
The custom max height of the list view should depend on the inner item's height, and how many items we want to show without scrolling. So I'm introducing a size option for the custom list, that it handles how many items are visible at first sight. This is customizable for every custom view.

In the screencast above you can see the context menu has a custom size of 5, to fix the issue. And I set the default size to 3, because TBH, those huge form controls bugged me up and I want to save some vertical space. In any case, now we can show some of them with different sizes.
Thoughts @xavijam @piensaenpixel @saleiva?

I really like the idea, just those two comments. I'm a bit afraid about the places where we are using the styles of the custom list and we could hide the list, could you double check where that is happening (it is likely we are not using it in that way so :+1:)?

ohh!

@xavijam I can't see any element using custom list styles outside the context menu or custom list view context. Do you remember any case in particular? @piensaenpixel does it ring your bell?

For me it's chachi piruli

"pues dale niño"


Fix broken format on master

Ran spotlessApply globally

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

Thanks for fixing. Do you have any idea how this could have slipped through? PreCommit ran fine before merging and this is a new file. It seems PreCommit doesn't run spotless?

Hmm, that would be a major issue. On master when I run ./gradlew --dry-run :javaPreCommit it does seem to include spotless tasks.

I do see the appropriate green checkboxes on #6726:
https://builds.apache.org/job/beam_PreCommit_Java_Commit/2017/
https://scans.gradle.com/s/fpucua3h2plj6/timeline?taskFilter=:beam-runners-flink_2.11:spotlessJavaCheck
But of course the issue was found because the very same precommit was failing, in its Cron variant:
https://builds.apache.org/job/beam_PreCommit_Java_Cron/502/
https://scans.gradle.com/s/byyjmuj377jgy/console-log?task=:beam-runners-flink_2.11:spotlessJava

@mxm what occurred was that #6791 modified the spotless configuration concurrently. Since we don't have a serialized merge queue, this sort of thing can happen.

That makes perfect sense! Thanks for taking the time to clarify.
It would be very convenient and less erorr-prone if we had a bot which merged pull requests serially.

We had one for the web site, but it is probably not something we want to maintain or administer. There are a few others out there; most have weird processes/rules/limitations. This one looks OK at first glance: https://github.com/bors-ng/bors-ng

Yes, I remember the ASF merge bot was fragile. Bors looks good, but whichever we would choose, the question is, how do we integrate it with the ASF infrastructure?
Asked INFRA to clarify: https://issues.apache.org/jira/browse/INFRA-17177

To be clear, this should go to dev@, and we frankly have a lot of infrastructure churn lately so folks might want to relax on that for a bit.

The discussion about whether the community wants a serial merge feature of course needs to go to<EMAIL_ADDRESS>Just wanted to know about the formalities. Yes, I agree, Infra should not be bothered too much :)


aiohttp stub throws away all recorded responses to the same endpoint except for the last one

Hi,
we are using vcrpy to test our api client, built on aiohttp. When upgrading to the 2.1.0 release we noticed our tests started failing. In the failing test, we are making multiple calls to the same URL in succession. It seems that when playing back the casette, vcrpy throws away all but the last response.
I have created a minimal script to demonstrate the behavior. It seems to be specific to the aiohttp stub:
#! /usr/bin/env python3

import asyncio
import aiohttp
import vcr

@vcr.use_cassette("test_casette.yaml")
async def main():
    async with aiohttp.ClientSession() as session:
        async with session.get('https://postman-echo.com/get') as resp:
            print('FIRST RESPONSE:')
            print(resp.headers)
        async with session.get('https://postman-echo.com/get') as resp:
            print('SECOND RESPONSE:')
            print(resp.headers)

loop = asyncio.get_event_loop()
loop.run_until_complete(main())

When running the script twice in succession, we can observe the difference in output between the first run (with real requests) and the second (requests recorded by vcr):
(venv)[hugo@hugos-mbp vcr_demo]$ python demo.py
FIRST RESPONSE:
<CIMultiDictProxy('Content-Encoding': 'gzip', 'Content-Type': 'application/json; charset=utf-8', 'Date': 'Fri, 16 Aug 2019 10:47:11 GMT', 'Etag': 'W/"e4-Us7L+i6yExRm9KG9mNvMvSP9DQ8"', 'Server': 'nginx', 'Set-Cookie': 'sails.sid=s%3AI6gIdE3cbaI1pza-0CWg621ScWcCNBAV.b8XF%2FDL42icPhHSBA8Cdl50FV%2BthHFk5ztcMdxySJ5M; Path=/; HttpOnly', 'Vary': 'Accept-Encoding', 'Content-Length': '171', 'Connection': 'keep-alive')>
SECOND RESPONSE:
<CIMultiDictProxy('Content-Encoding': 'gzip', 'Content-Type': 'application/json; charset=utf-8', 'Date': 'Fri, 16 Aug 2019 10:47:11 GMT', 'Etag': 'W/"14e-BBSrIh8nOQJ4wopc8Pj851uldcU"', 'Server': 'nginx', 'Vary': 'Accept-Encoding', 'Content-Length': '271', 'Connection': 'keep-alive')>
(venv)[hugo@hugos-mbp vcr_demo]$ python demo.py
FIRST RESPONSE:
<CIMultiDictProxy('Connection': 'keep-alive', 'Content-Encoding': 'gzip', 'Content-Length': '271', 'Content-Type': 'application/json; charset=utf-8', 'Date': 'Fri, 16 Aug 2019 10:47:11 GMT', 'Etag': 'W/"14e-BBSrIh8nOQJ4wopc8Pj851uldcU"', 'Server': 'nginx', 'Vary': 'Accept-Encoding')>
SECOND RESPONSE:
None

The expected behavior is that both runs are identical, but when using the recording the second response is returned for the first request, and the second request returns nothing at all. It seems that first response is dropped entirely, although when examining the cassette file it is present.

Thanks for reporting this! This might be related to #463 too.
If you could compose the above into a toy repo that could be cloned to replicate the issue that’d be appreciated.
Even better opening a pull request to address the issue. I appreciate you may not have the bandwidth for that and that’s totally fine.
In the mean time, pinning to 2.0.1 is recommended until we get a fix out.
Thanks again for raising this issue.

Thank you for the response. We have indeed pinned the version for the moment.
I am open to contribute towards resolving this issue but am somewhat limited on time. Depending on the complexity and time required I will try to help out. For the moment I have a toy repo that demonstrates the issue: https://github.com/HugoArts/vcrtoy-aio/tree/master
I will try to do some investigation into your codebase this week to see if I can identify the problem.

Thanks this is perfect and saves me a lot of time as I'm not familiar with aiohttp personally but now it'll be easier to step through vcrpy with the debugger later tonight.
I was able to clone and replicate the issue on my laptop

@HugoArts it's possible that @nickdirienzo has found the cause of this issue in #481  if that helps.

Hey y'all. I finally found time and energy to resolving this issue via #495.
@HugoArts if you have time and are interested in seeing if my fork resolves your issue that would be awesome. No worries if not! There are test cases that should resemble the behavior we both identified.

@HugoArts this should be fixed in the 3.0.0 release now via #495.

Closing as fixed but please reopen if it hasn’t.


http listen on unix socket

Hello,
I'm currently facing an issue with listening to the HTTP server on a Unix socket. I attempted to implement it using the following code snippet:
new Swoole\Http\Server("unix:/tmp/socket.sock") ( I tried without "unix:" too )
However, it doesn't seem to be working as expected. The server isn't listening on the specified Unix socket, and the corresponding file isn't being created. I've searched extensively online and in the documentation but haven't found any relevant information.
This situation is quite perplexing, and I'm having a heated debate with GPT about it. GPT is confident that this functionality should be possible, but I haven't been able to achieve it. My goal is to create a configuration similar to the following:
proxy_pass http://unix:/tmp/socket.sock;
I've successfully used Unix sockets with Node.js Express in the past, and I'm eager to replicate the same with Swoole. Could you please provide guidance on whether this is achievable with Swoole? Any assistance would be greatly appreciated.

I have successfully did it. The only method I found effective is as follows:
$http = new Swoole\Http\Server("/tmp/captcha.sock",0,OpenSwoole\Server::POOL_MODE,OpenSwoole\Constant::UNIX_STREAM);
docs sucks btw.
*broken link https://openswoole.com/docs/modules/swoole-coroutine-http-server

clicking there I get to the settings for the TCP server, not the HTTP one.
yeah I get it, the settings are almost the same for TCP and HTTP, but you guys should be more explicit about it.

I have successfully did it. The only method I found effective is as follows:
$http = new Swoole\Http\Server("/tmp/socket.sock",0,OpenSwoole\Server::POOL_MODE,OpenSwoole\Constant::UNIX_STREAM);
docs sucks btw.
*broken link https://openswoole.com/docs/modules/swoole-coroutine-http-server

clicking there I get to the settings for the TCP server, not the HTTP one.
yeah I get it, the settings are almost the same for TCP and HTTP, but you guys should be more explicit about it.


Fall back to default locale if the translation is null

Hey, I'm not sure if It's there, and I totally missed it, but I'm trying to translate properties, and if no translation is given NULL is saved to the db. When retrieving properties, the NULL properties don't fall back to the default locale, and just display blank!
I could possibly create a helper for
$model->property ?: $model->translate($default_locale)->property;

For example
$model->translateOrDefault($current_locale)->property;

Will check if a translation exists, and if it does, it will return it, but if the property is null, it will not fall back to the default!
Have I missed something, or is this the intended behaviour?

Please have a look at what translate() is doing. You'll see that this doesn't return any fallback by default. Check the code for public methods to use what you need.

Hey @dimsav, I have looked at the source, and as far as I can tell most methods rely on getTranslation($locale = null, $withFallback = null) which returns a ModelTranslation instance for the current (given) locale, or the default locale, and lastly if none is found, returns null.
Let's say I have a Model with
Model:
  en:
    - title: Some English Title
    - name: Some name
  other-language:
    - title: Some translated title
    - name: NULL

If I want to display the title, I would use:
$model->title

And that will display the title in the current locale. If I want to display the name property, I'd like to use the same markup: $model->name which would work properly for the en locale, but display an empty string for the other-language since it will find the ModelTranslation and it's field is null, so it will not fall back.
Is this the intended behaviour?
If it is, then I'm not sure if this should be implemented on the package level or not, that's your call!
Anyways just thought I'd share this particular use case, where not all translations are required, if they are the same the default should be displayed.

Hi @rigor789,
thanks a lot for sharing your ideas! Unfortunately that's not how fallback in Translatable works. As you can see in the getTranslation() method, we don't check if the translation of a specific field exists. What we check is if there is a translation relationship for the selected locale.
However your question makes totally sense. Maybe we can build this feature but it has to be done very carefully to not break existing conventions or worsen the performance.

I would think a config option to fall back for falsy values could be an appropriate solution! Something along the lines of
'fallback_for_empty_values` => true

which would be false by default for backwards compatibility.
Another idea would be to force the behaviour independant of the configuration, with a method
$model->translateOrFallback('property');

That would ignore the configuration, and display the localized property if it's not empty or null, and fall back to the default locale otherwise.
Note:The translateOrDefault() method could be replaced, but that would possibly break backwards.
I'm unsure about the name for the method though!

For this case I wrote this abstract class. Override only toArray method is enough for me, because data always go to JSON.
abstract class FallbackTranslationModel extends Model
{
    use \Dimsav\Translatable\Translatable {
        toArray as translatableToArray;
    }

    public function toArray()
    {
        $attributes = $this->translatableToArray();
        $hiddenAttributes = $this->getHidden();

        $fallbackLocale = $this->getFallbackLocale($this->locale());
        $translations = $this->getTranslation($fallbackLocale);

        if($translations)
        {
            foreach ($this->translatedAttributes as $field)
            {
                if (in_array($field, $hiddenAttributes)) {
                    continue;
                }

                if (empty($attributes[$field])) {
                    $attributes[$field] = $translations->$field;
                }
            }
        }

        return $attributes;
    }
}

Break many conventions adding this to "getAttribute" method to add this feature?
        if($this->useFallback() && empty($this->getTranslation($locale)->$key)) {
            return $this->getTranslation($this->getFallbackLocale())->$key;
        } else {
            return $this->getTranslation($locale)->$key;
        }

@dimsav Hi there...
I think it related to the subject.
I want to select the fallback translation if I have NULL or '' in current translation. Do we have a good method for it?
Thanks

@dimsav Hi there...
I think it related to the subject.
I want to select the fallback translation if I have NULL or '' in current translation. Do we have a good method for it?
Thanks

@rigor789 I have exactly problem as yours! Have you found a solution for this ?

Hi!
I have the same problem, and I opted to not save the empty translations in the database. I have an application with a dozen of languages, and I think that is not necessary to save rows that have all fields empty.
I modified the following two methods in the trait Dimsav\Translatable\Translatable

trait Translatable {

    ...

    /**
     * @param \Illuminate\Database\Eloquent\Model $translation
     *
     * @return bool
     */
    protected function isTranslationDirty(Model $translation)
    {
        $dirtyAttributes = $translation->getDirty();
        unset($dirtyAttributes[$this->getLocaleKey()]);

        /* START ADDED */
        if(! $translation->exists) {
            // We are creating the record
            foreach ($this->translatedAttributes as $attribute) {
                if (empty($dirtyAttributes[$attribute])) {
                    unset($dirtyAttributes[$attribute]);
                }
            }
        }
        /* END ADDED */

        return count($dirtyAttributes) > 0;
    }

    /**
     * @return bool
     */
    protected function saveTranslations()
    {
        $saved = true;

        foreach ($this->translations as $translation) {
            if ($saved && $this->isTranslationDirty($translation)) {
                /* START ADDED */
                if($translation->exists) {
                    // We are editing the translation
                    $isEmptyTranslation = true;
                    foreach ($this->translatedAttributes as $attribute) {
                        if (!empty($translation->getAttribute($attribute))) {
                            $isEmptyTranslation = false;
                            break;
                        }
                    }

                    if($isEmptyTranslation) {
                        $saved = $translation->delete();
                        continue;
                    }
                }
                /* END ADDED */

                $translation->setAttribute($this->getRelationKey(), $this->getKey());
                $saved = $translation->save();
            }
        }

        return $saved;
    }

    ...

}

For now seems to work fine. Any comment is very welcome.
Regards,
Rubén
P.D:  Thanks for make this library.

For me this depends on input! If you want fallback for all translated keys just fill them with fallback locale values, ...It will be a little bit complicated when doing updates.

I made a little change in the "getAttribute" method, instead of return null, the method will return the original parent method.
Original
if ($this->getTranslation($locale) === null) {
return null;
}
With changes
if ($this->getTranslation($locale) === null) {
return parent::getAttribute($key);
}
I don't know if break some conventions but it solve my problem.

getAttributeOrFallback is the solution here.


Clarification of error message PKG_005.

The extra fields feature of the ZIP format is forbidden for the mimetype file in the ZIP container because it would break support for magic numbers. The previous error message mislead to the impression that the error has something to do with filename extensions, while the extra field and the filename are separate things. Hopefully users will get enabled to search for ZIP extra fields and then look into the documentation of their ZIP generator to turn the extra fields feature off for the mimetype file or report an error for their EPUB generator program.

:+1:
This sounds reasonable and matches the actual checks performed. Going to merge this.

I encountered it in an EPUB file, checked https://users.cs.jmu.edu/buchhofp/forensics/formats/pkzip.html against section 4: "ZIP Container" of the Open Container Format 2.0.1 v1.0.1 specification (page 18+) and can provide this screenshot of the effect:

The actual mimetype "application/epub+zip" is supposed to start directly after mimetype, so reading systems don't need logic to skip over the extra field and can look for "application/epub+zip" from (including) byte 39.

Great, thanks for adding the extra information!
That's exactly what is going to be checked in checkEpubHeader() in https://github.com/IDPF/epubcheck/blob/5c7c4ad01014d71ff7f9ccab3d3519601c1420c1/src/main/java/com/adobe/epubcheck/api/EpubCheck.java#L275


[Definition] Remove no-op code in expanded_deps

While troubleshooting my bundler-fixture gem, which hacks up a
Definition class with a fake Index, and needed updating for 1.14
support for ruby and RubyGems version in the Definition index, I
noticed this block of code appears to not do anything, since a 2nd
argument is not being passed into concat_ruby_version_requirements
method.
The specs that were altered in the same commit that added these lines
pass with or without the lines of code, so I'm committing this up to do
a full Travis run to see if there are any other consequences. If not,
then we either can remove these lines, or need to hook them up properly
and add proper failing specs.

@segiddins dunno if i'll get time soon to dive into this, to figure out if this code should stay and be connected properly, and what the failing spec would be for it - or if this code can just be removed.

Let's rip it out for now

Or change it to concat_ruby_versions(version, ruby_versions) which is what I think it should be

@chrismo which approach would you prefer?

@chrismo ping

ping @chrismo

Closing due to no response from the author.


Fixed issue with typing related to Issue #42

As described here. This pull request fixes an issue with typing that affects python 3.8 and lower

Thanks!


Provide prescriptive guidance on use of Private Hosted Agents for DevOps

There is a preference from certain customers / industries to use Private Hosted Agents for DevOps. Seeking guidance from the ES documentation to provide a recommendation for the placement of these to include:

Azure Management Group location recommendations
Security of Private Hosted Agents
ACI vs VMSS
Agent pool recommendations (single shared vs multiple pools)

Trigger ADO Sync 1

Trigger ADO Sync 2


chore: Update to Node16

Description
Update from Node12 to Node16
Problem
There is a deprecation note for Node 12 on every run.
Solution
Changed the string node12 to node16
Notes
Everything seems to work as expected.
Checklist

[x] The title starts either with feat:, fix:, or chore:

feat should be used if this pull request implements a new feature
fix should be used if this pull request fixes a bug
chore should be used for maintenance changes

Thank you for your contribution! ❤


添加模板  award-template-plugin

通过下面命令，开发者可以快速创建一个开发award插件的模板
初始化插件模板命令npm init award -t plugin <你插件的项目名称，不指定就在当前目录创建>

Codecov Report

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

@@           Coverage Diff           @@
##           master       #8   +/-   ##
=======================================
  Coverage   86.05%   86.05%
=======================================
  Files          83       83
  Lines        2073     2073
  Branches      493      493
=======================================
  Hits         1784     1784
  Misses        282      282
  Partials        7        7

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 11c1b04...1b595b1. Read the comment docs.


mailmap: Update mailmap with full names and  emails

Helps with git shortlog -ns

remove<EMAIL_ADDRESS>
@cvinayak the purpose of this file is to document aliases for different identities the same person has used in the commit history. That way we get correct results e.g. for git shortlog. Are you saying this gmail alias is already part of the file or that you don't have any commits in the history that use that address?

@jhedberg I should not have used gmail id. But it appears in git  log, its got in once. Hence, its ok to have it in the mailmap.


super worked in older browsers without loose mode, now doesn't?

Before 726451f86fcb69a32abb3075c361830c3f9644fe super worked as far back as IE 8, using core-js of course. After 726451f86fcb69a32abb3075c361830c3f9644fe my tests started failing. If I enable loose mode it works again, but then my methods are enumerable:true in IE 9 and above, instead of the spec compliant false.
I couldn't find any reference to that commit, other than #690. What was the reason for going from:
_get(One.prototype, "constructor", this).call(this);

To:
_get(Object.getPrototypeOf(Two.prototype), "constructor", this).call(this);

For example, this was working in IE8 and now it's not:
class One {
  constructor() {
    this.test = "test";
  }
}

class Two extends One {
  constructor() {
    super();
  }
}

console.log((new Two()).test);

In cavets it says that super won't resolve correctly in IE 10 or below. Ignoring that it did work in IE 8, it currently works in IE 9 (without loose mode), at least it does in my project. Does that seem correct? Should that page be updated?

I was under the assumption for a short amount of time that the HomeObject was set at definition time and it was changed back as it's more inline with the spec.
The reason the caveats says that super wont resolve correctly is that super constructors will but the following wont:
class Foo {
  foo() { return "foo"; }
}

class Foo extends Bar {
  foo() { return super.foo() + "bar"; }
}

@sebmck
Is class Foo extends Bar supposed to be class Bar extends Foo. If so, that appears to work to me:
https://6to5.org/repl/#?experimental=false&playground=false&evaluate=true&loose=true&code=class Foo {
  foo() { return "foo"%3B }
}

class Bar extends Foo {
  foo() { return super.foo() %2B "bar"%3B }
}

console.log((new Bar).foo())%3B

@lukescott Whoops yeah it is. Not sure, I've had reports that it doesn't work and if I recall correctly whenever I've tested it hasn't. I'm not really willing to excessively document browser support, especially in such older browsers, because I'm going to have to maintain and support that.

@sebmck I switched back to strict mode. core-js just released a fix (0.5.2) for Object.getPrototypeOf that returns the correct value. Other than no getter/setter support (not using those intentionally), I'm not sure what doesn't work. My tests pass all the way back to IE 7 now.
I know you don't care about older browsers, but if there are more caveats, it would be nice to have them documented. Just out of curiosity, how do you run tests across browsers? Do you use something like Browserstack?


updateLinkedToService requires redeploy

Hi Allan,
Awesome work on this!!!!!
I've updated my code to use your master branch and all is working great,
it just seems that when using updateLinkedToService ( https://github.com/allansun/docker-cloud-php-api/blob/master/src/API/Service.php#L215 ) that the links in that service do get updated but are not activated until a redeploy
I'm using updateLinkedToService to update the load balancer service to newly created web services
//set load balancers links
$DockerCloud_LoadBalancer->setLinkedToService($link);

//do update - no redeploy?
DockerCloud_Service_API = new DockerCloud\API\Service();
$DockerCloud_Service_API->updateLinkedToService($DockerCloud_LoadBalancer);

note: am using the tutum/haproxy image for the load balancer
quite possible I'm doing somethign wrong - but if you have any thoughts/info on this it would be greatly appreciated!!!!!!!!!!
Cheers
Justin

update: just udpated the haproxy to dockercloud/haproxy instead of tutum/haproxy and this may be resolved
will do more testing and update this issues
thanks again!!!

Hi Justin,
There must be some weird settings in my Gmail I didn't get the notification .... sorry about the late reply.
I'm very glad this lib actually helped people
Yes you are in the right direction. the tutum/haproxy and dockercloud/haproxy problem puzzled me quite a while and I fixed it exactly like what you have done.
What caused that not working as expected was because in the HAProxy image, they expected some environment variables like DOCKERCLOUD_* in order to get HAProxy update script correctly detect newly linked service, where tutum/haproxy was looking for TUTUM_*.
@sonytwo (twitter) is the one developed tutum/haproxy and dockercloud/haproxy you can contact him for any questions regarding haproxy image

Ha! Just found it in my Gmail’s ‘Forums’ category, which is now shown in
the inbox!
Filtered out these emails hopefully I will see notifications in the future!
Best regards,
Allan Sun
On Mon, Apr 4, 2016 at 5:20 AM, Justin Kelly<EMAIL_ADDRESS>wrote:

update: just udpated the haproxy to dockercloud/haproxy instead of
tutum/haproxy and this may be resolved
will do more testing and update this issues
thanks again!!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/allansun/docker-cloud-php-api/issues/2#issuecomment-205131273

thanks @allansun !!! this project has been a HUGE help to me!
1 question: will you be tagging the master/dev branch soon - had some issue with composer trying to get the latest code
cheers
justin

@justinkelly I've just tagged the latest commit to be version 1.4, which you will be able to retrieve from @stable tag. I wasn't sure if that last commit was satisfactory enough to be 1.4 so it wasn't tagged, and as you know, once you are satisfied with your code, you forgot to maintain it ... :laughing:
{
"require-dev": {
"dockercloud/api": "@stable"
}
}

thanks allan!!!!! keep up the awesome work


Heightfields with negative values will fire face normal errors

To reproduce, change all heightfield data points in the heightfield.html demo to -5. You will see 1,000+ errors thrown from ConvexPolyhedron when computing convex triangle pillars.
This was also an issue from 2014: https://github.com/schteppe/cannon.js/issues/149

The failure to collide might just be due to lack of CCD, not a heightfield issue. Removing that part of the issue (though still a big issue).

I found the issue, which stems from the convex triangle pillar being upside down when the heightfield has a negative value. Will send a PR in the next few minutes.

Awesome, great work digging in and hunting down the issue. I'll cut a quick release with your fix.

I've published a new version of cannon-es with the fix to heightfields<EMAIL_ADDRESS>

Awesome, thanks for being so responsive.

Absolutely, we welcome any further contributions 👍


Feature/aws sqs utility allow fifo messages

This allows --list and  --load commands to read from and write to FIFO type SQS queues. Currently only works for Standard queues as MessageGroupId isn't stored or sent.
The --list command will now include MessageGroupId and MessageDeduplicationId columns in the generated CSV for FIFO queues. If MessageGroupId is not present then it is a Standard queue, and neither new column will be included in the CSV.
The --load command will now include MessageGroupId and MessageDeduplicationId in messages sent to the queue if present. MessageGroupId is required when adding to a FIFO queue. MessageDeduplicationId is optional and can be undefined.

lgtm :stuck_out_tongue_winking_eye:


Create Test Application

Break out the test harness from the primary class.

Completed with pull request #19


Collapsable sidebar on mobile

0 clue how to implement it closing on route change XD
i hope ive abstracted it in the correct place and really sorry if i didn't I have 0 confidence in my angular skills XD

0 clue how to implement it closing on route change XD

As router links are deep in the tree and will change over sidebar lifecycle, I think the only and reasonable way is to listen for router events and close sidebar on NavigationStart or NavigationEnd event.
You could do that in this way:
  constructor(readonly router: Router) {
    router.events
      .pipe(
        takeUntilDestroyed(),
        filter((e) => e instanceof NavigationEnd),
      )
      .subscribe(() => {
        this.open = false;
      });
  }

But this won't work until you change ChangeDetectionStrategy to ChangeDetectionStrategy.Default.
And the version working for OnPush strategy:
export class SidebarComponent implements AfterViewInit {
  @ViewChild(TuiActiveZoneDirective)
  private _button!: TuiActiveZoneDirective;

  open$!: Observable<boolean>; // *tuiSidebar="(open$ | async) ?? false"

  private readonly _router = inject(Router);

  ngAfterViewInit() {
    this.open$ = merge(
      this._button.tuiActiveZoneChange,
      fromEvent(this._button['el'].nativeElement, 'click').pipe(
        map(() => true)
      ),
      this._router.events.pipe(
        filter((e) => e instanceof NavigationEnd),
        map(() => false)
      )
    ).pipe(distinctUntilChanged());
  }
}


Make cell collapsed state a UI properly

We have done some last minute clean-up and removes collapse states from cell metadata. This was an API only change and needs further clean-up. We

define collapsed state as a view property (not a model property)
expose the view state via the NotebookEditor API (set/get property and event)

Do we still need this? @jrieken

Yes, pretty sure because at the time we made this an API only change, e.g the data is still there and used wrongly. Tho @roblourens will know best.

Not actually sure what we want to do with this, because I think we still might want to support Jupyter's feature of persisting this state to share.
@rebornix should I assume that even if we do that, we definitely don't want to use our metadata for that?


Save images and videos in different folders

Save images and videos in different folders.
Currently the camera application saves the images and videos in the same folder (DCIM), I think that most users do not know what DCIM means, it would be good if the main folder of the camera application was called (Graphene Os camera) and inside In this folder there are two folders by default, a folder called (Videos) and another folder called (Photos). This would simplify the transfer of files using applications such as Android Transfer and would make it easier to quickly find items in the file manager.

This is the standard location to save them, which we're going to keep as the default. You can set a different location to save the files. It doesn't seem necessary to put them in different locations since they're distinguished by the file extension. Can you explain why you want them in different locations?

The screenshots could be saved within the (downloads) folder in a folder called (Screenshots), the images downloaded from the internet could be saved in another folder within the downloads folder called (images) and the videos downloaded from the internet in a folder inside the downloads folder called (videos)

Because how images and videos are saved today makes those files less accessible to the average user who does not know what DCIM means and it does not seem the most rational to me to save images and videos downloaded from the Internet in the same folder as the images and videos. taken with the camera

Screenshots are already saved in Pictures/Screenshots and that has nothing to do with this Camera app.

Screenshots are already saved in Pictures/Screenshots and that has nothing to do with this Camera app. Screenshots are not downloads and don't belong there.

Images and videos downloaded from the internet are not saved to DCIM/Camera. DCIM/Camera is already a dedicated place for this. It's not clear what the purpose would be of splitting captured images and videos into separate folders.

We're going to continue following the standard Android approach to the media directories.

Even if I don't agree, thank you very much for your quick response :)


Setting up CI to check for formatting

Fixes: #111 (sort of)
With this PR, we support Github Actions for openai-python. For every push or pull request for the "main" branch, we run Gitleaks, isort, flake8, black, and codespell.
I've tested this on my own repository, which works fine with this. I referenced Gym's CI for some of this work and I tried to keep it as similar as possible.

https://github.com/Yadnyawalkya/openai-python/pull/1
https://github.com/Yadnyawalkya/openai-python/actions/runs/3213445651/jobs/5253123863

Also added CONTRIBUTING.md that includes instructions on how to work with pre-commit (this I guess needs more info later on).
Please let me know if there is anything that needs to be changed.

Thanks for this!
We've added this in a separate PR using ruff and other tools.


API Getting Started Section

Getting Started content section that should display the following bits of information:

Overview
Endpoints (Base URLs)
Openapi Spec, Postman Collection
Authentication (overview based on the Auth Flow)
Further Reading (links to documentation)

Adding to Epic #155 as it is to do with the API Directory redesign.


feat(env): Make selected env vars configurable

Fixes #278
Environment variables added to the Cryostat CRD:

CRYOSTAT_REPORT_GENERATION_MAX_HEAP. This is only set when the sidecar reportsUrl does not exist
CRYOSTAT_MAX_WS_CONNECTIONS, default 2
CRYOSTAT_TARGET_CACHE_SIZE, default -1
CRYOSTAT_TARGET_CACHE_SIZE, default 10

I wonder if CRYOSTAT_ALLOW_UNTRUSTED_SSL=true would ever be needed. jfr-datasource doesn't use HTTPS. The reports sidecar doesn't yet, but Cryostat talks to it using the internal service hostname whose certificates would be managed by cert-manager.

I also removed CRYOSTAT_ALLOW_UNTRUSTED_SSL.

No worries Elliott, thanks for the review


Moved full site from lauralorenz/sig-multicluster-site-proposal

A full copy of the staging web site to the official k8s multicluster doc site.

/lgtm
/approve


odd bug with workspace copying

I am in safari and I am copying a private job to a public workspace directory.  When I do this I get this odd proliferation of up arrows next to the name:

@nconrad can you fix this please?


Reward Modal - "Recieve" Typo

Description
This change corrects a typo
Types of changes

[ ] Technical Debt (non-breaking change which removes unused code/assets)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The related ClickUp task has been linked to this PR
[x] The person creating the pull request is listed in "Assignees"
[x] My code follows the code style of this project .
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Task linked: CU-2kw8f5b UI: Reward Modal - "Recieve" Typo


iFrame .mp4 videos not playing in Safari 12

When opening links to MP4 videos in Safari, the lightbox pops open but the entire media player within has been reduced to a height of 31px. This is because the video element has the class of
class="media-document audio mac"
and there are related styles which set the height to the height of the inline-control-bar variable which has a height of 31px;
If the same video is opened directly, outside of the Magnific Popup lightbox, they have the correct class of
class="media-document video mac"
which in turn applies the styles of min-width: 700px;
The classes only appear to be applied in Safari and set by the browser? I've researched and these appear to be related to webkit. However, this is only an issue in Safari and I cannot seem to replicate it in Firefox, Chrome etc.

@taoball Any update on this? I am facing the exact issue and would like to know if you were able to figure out the root cause and fix it? Thanks in advance

Adding a comment here since I am having this issue as well. Unfortunately, Magnific Popup seems to be abandoned. MP4's don't work in an iframe popup on Safari. The solution I'm about to implement is switching to an inline pop-up instead. This seems to be a Safari bug and I haven't found a work-around. It makes no sense that it would add an .audio class to a video element. Thank you @taoball for shining light on this problem for me. I wish I had a better solution.


wraith giving error "can't convert String into Integer"

Suddenly, wraith is giving an error, even on the example file:
/regression$ wraith validate 'configs/capture.yaml'
/var/lib/gems/1.9.1/gems/wraith-3.1.6/lib/wraith/wraith.rb:172:in `[]': can't convert String into Integer (TypeError)
	from /var/lib/gems/1.9.1/gems/wraith-3.1.6/lib/wraith/wraith.rb:172:in `verbose'
	from /var/lib/gems/1.9.1/gems/wraith-3.1.6/lib/wraith/wraith.rb:11:in `initialize'
	from /var/lib/gems/1.9.1/gems/wraith-3.1.6/lib/wraith/validate.rb:10:in `new'
	from /var/lib/gems/1.9.1/gems/wraith-3.1.6/lib/wraith/validate.rb:10:in `initialize'
	from /var/lib/gems/1.9.1/gems/wraith-3.1.6/lib/wraith/cli.rb:48:in `new'
	from /var/lib/gems/1.9.1/gems/wraith-3.1.6/lib/wraith/cli.rb:48:in `block in validate'
	from /var/lib/gems/1.9.1/gems/wraith-3.1.6/lib/wraith/cli.rb:28:in `within_acceptable_limits'
	from /var/lib/gems/1.9.1/gems/wraith-3.1.6/lib/wraith/cli.rb:47:in `validate'
	from /var/lib/gems/1.9.1/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
	from /var/lib/gems/1.9.1/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
	from /var/lib/gems/1.9.1/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
	from /var/lib/gems/1.9.1/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
	from /var/lib/gems/1.9.1/gems/wraith-3.1.6/bin/wraith:5:in `<top (required)>'
	from /usr/local/bin/wraith:23:in `load'
	from /usr/local/bin/wraith:23:in `<main>'

I validated that the capture file contains valid YAML.
I don't know Ruby, but the line in question appears to involve the verbose parameter.
    @config["verbose"] || false

I'm fairly certain I last ran wraith with the same version, as it had the fix to issue #419 (Thank you, BTW).
Since the last time I run wraith, I installed linkchecker, which is running as I type this. However, linkchecker does not appear to use Ruby.
[Update:]
linkchecker has finisher running and the problem is still happening.
wraith version returns 3.1.6

This is almost identical to #405 (though the exact error message for that issue is no implicit conversion of String into Integer (TypeError) rather than your message of can't convert String into Integer (TypeError) - probably because you're using ruby version 1.9.1, and the person in the other issue is using ruby version 2.3.0.
Can you check if any of the fixes in #405 work for you?

Aak, I was one directory up from where I needed to be to find the configuration file.
If I can edit this issue, I'm changing it to "Respond that config file is not found when config file is not found," otherwise, I'll file a new issue.

So, the request is that if the configuration file is not found, wraith respond with an error message that the configuration file is not found rather than the current mysterious Ruby error message.

Fixed in https://github.com/BBC-News/wraith/releases/tag/v3.1.7


Add type role on Eff

The inferred roles of Eff are Eff phantom representational, but we want Eff nominal representational.

Thanks! Will just wait for CI.


dotnet-sdk_7: 7.0.100 -> 7.0.101

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for dotnet-sdk_7 is: ".NET SDK 7.0.101"
meta.homepage for dotnet-sdk_7 is: "https://dotnet.github.io/"
meta.changelog for dotnet-sdk_7 is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 7.0.101 with grep in /nix/store/d66l0kal1wlz4cnmb4isyw29vv8c4x87-dotnet-sdk-7.0.101
found 7.0.101 in filename of file in /nix/store/d66l0kal1wlz4cnmb4isyw29vv8c4x87-dotnet-sdk-7.0.101

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
BeatSaberModManager
dotnet-aspnetcore_7
dotnet-runtime_7
dotnet-sdk_7
dotnetCorePackages.aspnetcore_7_0
dotnetCorePackages.runtime_7_0
dotnetCorePackages.sdk_7_0
ryujinx

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d66l0kal1wlz4cnmb4isyw29vv8c4x87-dotnet-sdk-7.0.101 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dotnet-sdk_7 https://github.com/r-ryantm/nixpkgs/archive/19e27ad3bd244be7bcf122488760ee3c7d4861b0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d66l0kal1wlz4cnmb4isyw29vv8c4x87-dotnet-sdk-7.0.101
ls -la /nix/store/d66l0kal1wlz4cnmb4isyw29vv8c4x87-dotnet-sdk-7.0.101/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

BeatSaberModManager

4 packages built:

dotnet-aspnetcore_7
dotnet-runtime_7
dotnet-sdk_7
ryujinx

Maintainer pings
cc @kuznero @mdarocha for testing.

duplicate of #206768


Is there a library that support can use?

Now the support is still used in the project, there is currently no way to upgrade androidx。Ask support, which version is available

You can use version 3.1.2 if ur project has not been transfered to androidx
Details:
https://github.com/Kyson/AndroidGodEye/wiki/0x00-QuickStart_zh
https://github.com/Kyson/AndroidGodEye/wiki/0x00-QuickStart_en


L2 mode stops announcing

Is this a bug report or a feature request?:
BUG
What happened:
Following a MetalLB re-install (kubectl replace --force), MetalLB responds to arp requests immediately a ConfigMap is created. Then stops responding.
What you expected to happen:
MetalLB should keep responding
How to reproduce it (as minimally and precisely as possible):
pi@rpi3-k8s-2:~ $ sudo arping <IP_ADDRESS>
ARPING <IP_ADDRESS>
Timeout
Timeout
Timeout
Timeout
Timeout
60 bytes from b8:27:eb:42:e4:45 (<IP_ADDRESS>): index=0 time=293.422 msec
60 bytes from b8:27:eb:42:e4:45 (<IP_ADDRESS>): index=1 time=412.592 msec
60 bytes from b8:27:eb:42:e4:45 (<IP_ADDRESS>): index=2 time=541.828 msec
60 bytes from b8:27:eb:42:e4:45 (<IP_ADDRESS>): index=3 time=571.218 msec
60 bytes from b8:27:eb:42:e4:45 (<IP_ADDRESS>): index=4 time=700.696 msec
Timeout
Timeout
Timeout
Timeout

The responses always start as soon as the ConfigMap is created. I sometimes receive 4 and sometimes 5 responses. Then timeouts.
pi@rpi3-k8s-2:~ $ ip neigh show <IP_ADDRESS>
<IP_ADDRESS> dev wlan0 lladdr b8:27:eb:42:e4:45 STALE

Anything else we need to know?:
My cluster is 5 nodes (rpi if that wasn't clear...). Is the number of nodes related to the 4 or 5 responses received?
On Linux, arp-scan gives:
$ sudo arp-scan --interface=wlan0 --localnet
does not find the IP address.
On windows, arp -av gives:
<IP_ADDRESS>         b8-27-eb-42-e4-45     invalid
The speaker logs end with:
2019-01-06T10:51:42.583195812Z {"caller":"arp.go:102","interface":"weave","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"22:00:80:0e:30:36","senderIP":"<IP_ADDRESS>","senderMAC":"ca:d0:74:68:fc:23","ts":"2019-01-06T10:51:42.582389665Z"}
2019-01-06T10:51:42.583962844Z {"caller":"arp.go:102","interface":"datapath","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"e2:bf:95:52:d8:f9","senderIP":"<IP_ADDRESS>","senderMAC":"22:00:80:0e:30:36","ts":"2019-01-06T10:51:42.582458102Z"}
2019-01-06T10:51:42.584566491Z {"caller":"arp.go:102","interface":"datapath","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"e2:bf:95:52:d8:f9","senderIP":"<IP_ADDRESS>","senderMAC":"ae:72:aa:f2:b4:26","ts":"2019-01-06T10:51:42.58392774Z"}
2019-01-06T10:51:42.585505868Z {"caller":"arp.go:102","interface":"weave","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"22:00:80:0e:30:36","senderIP":"<IP_ADDRESS>","senderMAC":"e2:bf:95:52:d8:f9","ts":"2019-01-06T10:51:42.584846544Z"}
2019-01-06T10:51:43.684302668Z {"caller":"arp.go:102","interface":"datapath","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"e2:bf:95:52:d8:f9","senderIP":"<IP_ADDRESS>","senderMAC":"22:00:80:0e:30:36","ts":"2019-01-06T10:51:43.683827824Z"}
2019-01-06T10:51:43.68449246Z {"caller":"arp.go:102","interface":"datapath","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"e2:bf:95:52:d8:f9","senderIP":"<IP_ADDRESS>","senderMAC":"ae:72:aa:f2:b4:26","ts":"2019-01-06T10:51:43.684145064Z"}
2019-01-06T10:51:43.685356784Z {"caller":"arp.go:102","interface":"weave","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"22:00:80:0e:30:36","senderIP":"<IP_ADDRESS>","senderMAC":"ca:d0:74:68:fc:23","ts":"2019-01-06T10:51:43.68440371Z"}
2019-01-06T10:51:43.68549892Z {"caller":"arp.go:102","interface":"weave","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"22:00:80:0e:30:36","senderIP":"<IP_ADDRESS>","senderMAC":"e2:bf:95:52:d8:f9","ts":"2019-01-06T10:51:43.68467595Z"}
2019-01-06T10:51:44.787808847Z {"caller":"arp.go:102","interface":"weave","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"22:00:80:0e:30:36","senderIP":"<IP_ADDRESS>","senderMAC":"ca:d0:74:68:fc:23","ts":"2019-01-06T10:51:44.786328949Z"}
2019-01-06T10:51:44.787998014Z {"caller":"arp.go:102","interface":"datapath","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"e2:bf:95:52:d8:f9","senderIP":"<IP_ADDRESS>","senderMAC":"22:00:80:0e:30:36","ts":"2019-01-06T10:51:44.786320459Z"}
2019-01-06T10:51:44.788081087Z {"caller":"arp.go:102","interface":"weave","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"22:00:80:0e:30:36","senderIP":"<IP_ADDRESS>","senderMAC":"e2:bf:95:52:d8:f9","ts":"2019-01-06T10:51:44.786907335Z"}
2019-01-06T10:51:44.788157077Z {"caller":"arp.go:102","interface":"datapath","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"e2:bf:95:52:d8:f9","senderIP":"<IP_ADDRESS>","senderMAC":"ae:72:aa:f2:b4:26","ts":"2019-01-06T10:51:44.787013898Z"}
2019-01-06T10:51:44.866967879Z {"caller":"announcer.go:98","event":"createNDPResponder","interface":"vethweplbf787ba","msg":"created NDP responder for interface","ts":"2019-01-06T10:51:44.86636293Z"}
2019-01-06T10:51:45.889114185Z {"caller":"arp.go:102","interface":"datapath","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"e2:bf:95:52:d8:f9","senderIP":"<IP_ADDRESS>","senderMAC":"ae:72:aa:f2:b4:26","ts":"2019-01-06T10:51:45.88837658Z"}
2019-01-06T10:51:45.892047628Z {"caller":"arp.go:102","interface":"weave","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"22:00:80:0e:30:36","senderIP":"<IP_ADDRESS>","senderMAC":"e2:bf:95:52:d8:f9","ts":"2019-01-06T10:51:45.88976877Z"}
2019-01-06T10:51:45.892213305Z {"caller":"arp.go:102","interface":"datapath","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"e2:bf:95:52:d8:f9","senderIP":"<IP_ADDRESS>","senderMAC":"22:00:80:0e:30:36","ts":"2019-01-06T10:51:45.889886791Z"}
2019-01-06T10:51:45.892293566Z {"caller":"arp.go:102","interface":"weave","ip":"<IP_ADDRESS>","msg":"got ARP request for service IP, sending response","responseMAC":"22:00:80:0e:30:36","senderIP":"<IP_ADDRESS>","senderMAC":"ca:d0:74:68:fc:23","ts":"2019-01-06T10:51:45.890392521Z"}

Environment:

MetalLB version: 0.7.3, although I've tried 0.7.2 and 0.6.2
Kubernetes version: 1.13.1
BGP router type/version: N/A
OS (e.g. from /etc/os-release): Raspbian stretch
Kernel (e.g. uname -a): Linux rpi3-k8s-2 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux

Same issue here :(

Sorry, but I no longer have the time to debug MetalLB deployments for people. I want to keep this tracker specifically for bugs and features, so I'm going to close this. At some point I may have time to write general troubleshooting documentation, but as a first step towards that I need to clear up the issue tracker.
You could try asking for help on the #metallb channel on the Kubernetes slack, where there are people other than me who can assist.

Hi @danderson,
Just for information, I had the same issue on a CoreOS/Typhoon cluster deploy on Oct 2018, which start suddenly to misbehave on Feb 2019. L2 ARP reply is not sent by the nodes, even after a reboot (it works for 5min, then fail again).
The workaround I found is to enable promiscuous (or start tcpdump...).
Note: The node are using an LACP bond of 2x10GB interfaces.
I don't know yet if it's a metallb issue or not, since the CoreOS node has been auto-updated recently. Or is it because we just recently deploy more workloads (pods) on the cluster? Still investigating...

@johnmarcou did you find a solution for LACP?
having the same problem

@johnmarcou did you find a solution for LACP? ...

@zzzuzik it’s been a while ago. I never figured out how to fix, except the promiscuous mode workaround.
The applications has been migrated to a new updated cluster, then the failed cluster has been decommissioned.

@johnmarcou no problem, thanks for answering.. cheers!

Hi, we're using LACP too, I've created new issue https://github.com/metallb/metallb/issues/535, probably iy is related with this one


Back-propagating gradients through a sparse tensor?

I have a normal feed-forward network that produces a vector v. The elements of v are then used as the non-zero entries of a sparse matrix M (assume the coordinates are predefined). The sparse matrix is then multiplied by a dense vector and a loss is defined on the resulting scalar. I want to back-propagate the loss w.r.t. the weights of the network, which entails going through the sparse matrix.
This seems like a perfectly reasonable use-case for a sparse matrix, but it appears that such functionality is not supported. Indeed, even calling tf.gradients(M,[v]) produces an error:

AttributeError: 'SparseTensor' object has no attribute 'value_index'

Am I doing something wrong or am I correct in presuming that this functionality doesn't (yet?) exist? If the latter, then is there a work-around for this particular use-case short of rewriting all of the sparse tensor operations with gradients defined?

cc @martinwicke since he recently answered some q's about state of sparse tensor support

This is a great question for StackOverflow. It looks to me that there is no bug, but that the error message could be improved. I'll leave this open while I improve this error.

Wait a second -- the error message wasnt the primary concern here. The question was about whether or not my use case is currently  (or planned to be) supported by tensorflow.

Not sure what's the status of sparse gradients is, I see a recent commit referencing gradients and sparse together -- ef489fb3

If you just pass M.values instead, I bet your code will just work. I think I'll just fix this though, just have to add tests.

Yup, that solved it -- thanks!

If you just pass M.values instead, I bet your code will just work. I think I'll just fix this though, just have to add tests.

hi, sir,  I meet the problem too,  if I need  get the gradients wrt the sparse tensor's zero elements, what should I do?

Use tf.sparse.to_dense first. Since you'll be expanding the tensor for the
backward pass anyway, there's little reason to keep it sparse.
On Thu, Dec 27, 2018, 04:36 王吉宏<EMAIL_ADDRESS>wrote:

If you just pass M.values instead, I bet your code will just work. I
think I'll just fix this though, just have to add tests.
hi, sir, I meet the problem too, if I need get the gradients wrt the
sparse tensor's zero elements, what should I do?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/6998#issuecomment-450142625,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjO_VQASehTbpSJeZzZOM1Ke7iamRzNks5u9L6-gaJpZM4LqKtC
.

On TF 2.0rc this does not work, the gradient for the sparse_dense_matmul op is not defined.

Is the gradient only undefined in 2.0? That would be very surprising. I
find it more likely that we never had this gradient. It would be great to
add it -- an issue with this feature request would be a good start.
On Tue, Sep 3, 2019 at 2:51 AM László Mérő<EMAIL_ADDRESS>wrote:

On TF 2.0rc this does not work, the gradient for the sparse_dense_matmul
op is not defined.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/6998?email_source=notifications&email_token=AAEM57JSXUFX6JEVEALA3UTQHYXSPA5CNFSM4C5IVNBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5XUMBQ#issuecomment-527386118,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEM57JCALE2R2XNQXMUE2DQHYXSPANCNFSM4C5IVNBA
.


[Bug]fix mmdet bc breaking

Motivation
After pr #1388, if the user installed mmdet version is not the newest, err:
Traceback (most recent call last):
File "tools/test.py", line 259, in
main()
File "tools/test.py", line 151, in main
setup_multi_processes(cfg)
File "/home//.local/lib/python3.8/site-packages/mmdet/utils/setup_env.py", line 30, in setup_multi_processes
if 'OMP_NUM_THREADS' not in os.environ and cfg.data.workers_per_gpu > 1:
File "/home/*/.local/lib/python3.8/site-packages/mmcv/utils/config.py", line 49, in getattr
raise ex

Modification
fix test.py to import setup_multi_processes from mmdet3d to resolve back-compatibility.

I have changed the base and please merge the dev into your branch to avoid potential doc conflicts.


Character overflow for multisig names

Multisig name and account name needs a character limit, also if you create a huge multisig name it breaks out of the layout on the review screen (large account name are ok because they get truncated).

Hey @Tbaut, yeah it's still happening. I could enter one with 418 characters.

Weird, I checked it. That's probably a browser incompatibility. I tested on Firefox. I don't contraint the number of char, I'll do it, but it's wrapping for me.