Atlas visualize doesn't work with beta SQL Server driver

atlas version v0.13.4-5462430-canary

When trying use --visualize per this blog post, I selected "share privately".
After that, the following error was produced:
Error: template: format:1:3: executing "format" at <visualize .>: error calling visualize: unknown driver "sqlserver"

Hello @jrmcpeek, looks like our cloud doesn't support SQLServer yet. We will working on the support soon and back to you.

Fair enough. Wasn't sure of the expectations since the driver is in beta and the error message looked just like a failure versus "not yet supported".

Hello @jrmcpeek, We already support SQL Server on our cloud. Please give try a let me know if you got an issue. <3

Please give try a let me know if you got an issue. <3

With version atlas version v0.14.1-078bbe1-canary
@giautm - This now works for publishing, however, I am unable to locate the ERD/visualization in our cloud instance other than through the link generated at publishing time. Is this what is expected?
Additionally, it is only in that view that SQLSERVER is listed as a schema option, so I am not able to select it and import a schema through the web interface.
I can make a separate issue / separate issues for these if necessary.


[Feature Request]重命名时识别组名

Is your feature request related to a problem? Please describe.
重命名时识别关键字之类的然后，让emby显示更加完美!~!
Describe the solution you'd like
彻夜之歌 (2022) S01E04 XKsub.mp4

请转到 #41 讨论


"Saved" link redirects to home page before navigating to the saved page

This PR resolves the issue where clicking the "Saved" link in the header would first redirect users to the home page before navigating to the /saved page.
Changes Made:

Navigation Logic: Adjusted the renderLinks function to ensure that the "Saved" link doesn't trigger an unnecessary home page redirect when clicked.
Route Matching: Updated the route matching logic to properly identify and activate the correct navigation item based on the current URL path.

Possible Reasons for the Bug:

Next.js Partial Rendering: The issue could also be due to Next.js partially rendering the component instead of performing a full-page render, leading to the unexpected redirection behavior.
Route Mismatch: The route matching logic might have been too general, causing the link to match the home page route before navigating to the correct path.
Default Navigation Behavior: The "Saved" link could have been treated as a default link or fallback, resulting in the browser briefly redirecting to the home page.
State Handling: A potential race condition or state mismanagement could have caused the link to reset to the home page before properly setting the correct route.

Issue Link:
This PR addresses issue #2428.
Checklist:

[x] Verified that the "Saved" link now directly navigates to the /saved page without any intermediate redirection.
[x] Tested across different screen sizes to ensure consistent behavior.

Thanks, I will recheck this.

Thanks, I will recheck this.

Is there any update on this?

@drakeRAGE ?

Closing the PR due to inactivity


improvement: more general support for half-closable connections

Looks nice, but I wonder, what is the usecase?

actually, 2 cases (and I run into both in our project)

Not only net.TCPConn is half-closable, but also the net.UnixConn
sometimes we have to wrap net.TCPConn with some custom type (we are reporting traffic, for example)


Add revert_in parameter to napalm_configure (replaces #32)

Extends what was proposed in #32 but adds the ability to confirm a commit that was sent previously with a revert_in timer.

I will also see if I can fix the CI-CD issues...they look unrelated to your PR.

Yes, the CI issues are completely unrelated. If you don't beat me to it I may try to do it myself by the end of next week. My schedule is crazy nowadays :(

The CI issue should be easy to solve.
https://github.com/nornir-automation/nornir_napalm/blob/master/.github/workflows/main.yaml#L55
I believe you need to use snok/install-poetry@v1 instead of<EMAIL_ADDRESS>It works with v1 in the linter job, and I have other pipelines using v1.
If you both are busy I can make a PR

@ubaumann I will see if I can get to it this weekend...probably won't get to it before then.

Looks good with the caveat of the one comment I made regarding the need of logic of the form if revert_in is not None.
Also needs to be implemented in conjunction with adding rollback support to nornir-napalm

Superseded by https://github.com/nornir-automation/nornir_napalm/pull/44 to fix CI-CD issues.


require_keys method as figaro have

What do you think?

Thanks for asking. See https://github.com/bkeepers/dotenv/pull/201 and https://github.com/bkeepers/dotenv/issues/154 for previous discussion on this.


[REQUEST] Multiple wordlists queuing in jobs

Hello,
A very useful feature would be the multiple wordlists queuing management in jobs, I will explain why :

Useful for pins pentesting without having to load each different config with a different input (code1, code2, etc)
Useful for codes pentesting as some hits are valid one by one from within specific static ranges (eg: one hit within 100100 to 100199, next hit 100200 to 100299), so basically you would have to set a trigger in monitor on hit move to next wordlist in queue.

Hopefully my explanation is clear.
I think this feature is pretty much lacking right and would be awesome to implement, hopefully its not too much work !

Hello, is there any reason why it would be a problem to prepare a wordlist with all the combinations you need beforehand?

Hello, is there any reason why it would be a problem to prepare a wordlist with all the combinations you need beforehand?

please add because we get confuse


pull request for e2e test at 12/26/2016 11:56:16

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


Users/jdixon/show service name in UI

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Show the Display Name of the measurement service in the dialog when the service is running. Prior to this, it was impossible to tell which service was which if there were multiple running since it only displayed the Listening Port. Adding the Display Name to this.
Here's an example of two services running at the same time with the update.

I added a Get Measurement Details.vi to the base class for measurement services. This is used in Run Service.vi to set the display name on the front panel when launching. It is also used in a couple other places that had similar code to run the user's Get Measurement Details.vi and gather the information.
Why should this Pull Request be merged?
Improves the LabVIEW UI of a dynamically run service.
What testing has been done?
Built and installed the LV packages, generated two services and ran them to see the display name showing up.

Get Measurement Details.vi block diagram

Updated these VIs.

One note for potential discussion and/or posterity:
This modification carries a probably-innocuous change in the interface to the customer's Get Measurement Details.vi; we no longer send an error in to the customer's VI under any circumstance, and we no longer retrieve an error out from the user's VI if they were to throw one. One could argue there was never much value to having error in | error out in Get Measurement Details.vi (aside from dataflow that comes from error tracks in LV, which is no longer applicable, since it's not called as a subVI anymore..).
Perhaps it's fine to effectively remove them from the interface, which would technically allow us to remove the error in | error out terminals from the template version of the VI. The option on the other end of the spectrum would be to incorporate both error in and error out in the read/write by-label VI Server calls. It probably won't hurt to leave it all as-is, though one might reasonably consider an un-caught error coming from the customer's Get Measurement Details.vi as unexpected behavior.

IMO, it's very unlikely errors will be a concern with such a simple VI, so I'm ok with this change.


fix: added type="button" to NavButton

Description
Changed NavButton to use type="button" to prevent form submissions.
When the date picker component is used inside a form it will submit the form when a user clicks on the buttons.
https://github.com/tremorlabs/tremor/assets/8594759/effbbc0d-9a3d-46a3-b488-dfecd01cb2b3
The default for a button as documented in https://developer.mozilla.org/en-US/docs/Web/HTML/Element/button#attributes is "submit"

submit: The button submits the form data to the server. This is the default if the attribute is not specified for buttons associated with a <form>, or if the attribute is an empty or invalid value.

but I believe it should be changed to button which does the following:

button: The button has no default behavior, and does nothing when pressed by default. It can have client-side scripts listen to the element's events, which are triggered when the events occur.

This prevents any form submissions and still allows the onChange to fire as normal.
Related issue(s)
https://github.com/tremorlabs/tremor/issues/602
What kind of change does this PR introduce? (check at least one)

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New Feature (non-breaking change which adds functionality)
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
How has This been tested?
It will not change the onClick applied to the Icon and will behave in the same was as if there was no form around the component.

@MightySCollins Thanks for this!


Add endian type identifiers

These types are defined with the bitwise attribute, which is used to restrict their use as integers.
Used by sparse utility to make sure the variable is converted to the local processor type before other (unsafe) operations are performed on the variable
Useful when passing around data over network, etc

See this for more context

@jukkar A lot of cross-platform protocols (such as greybus) define the endianness of the data in the protocol spec. Using a type such as uint*_t loses this information. While it might be fine for people deeply familiar with the protocol, a beginner might not be aware or might just forget this leading to unexpected results.
Even for experienced users, I think having these types can be helpful to avoid a lot of problems since they can be integrated with sca to prevent errors.

Even for experienced users, I think having these types can be helpful to avoid a lot of problems since they can be integrated with sca to prevent errors.

But shouldn't the API for the given protocol hide the need for this knowledge from the users of said APIs?

But shouldn't the API for the given protocol hide the need for this knowledge from the users of said APIs?

Well, that depends on who the user here is. For an application writer, sure, it might make sense. However, a driver or subsystem developer probably needs this knowledge.

Found this via #67077
This seems a little cart-before-horse?  Types with this attribute are only supported by sparse right now?  Seems like we should start by adding a rig to detect these problems (note that SOF is already using sparse, so it's not alien to Zephyr), then add the types with integration to existing APIs (c.f. sys_be32_to_cpu() et. al.)?  The types themselves don't get us very far along that path.

I agree with the others in questioning if this is really needed, MCUmgr handles this fine without needing specific types.

Let me provide some clarification. These are type identifiers, not new types. The only use for this is to allow tools like sparse to detect endianness errors, such as passing __le16 to a function taking uint16_t without using conversion functions. It is useful for the same reason as using int * instead of void * (even though for llvm both are essentially opaque pointers), to provide some indication about the type to developer and tools.
For a real example of it's usefulness, take my gb_beagleplay Linux driver. It was accepted in linux-next a few months ago after around 9 rounds of patches. However, an endian bug slipped through, later detected and reported by the kernel bot. Since the driver only targets a device that is a little-endian, in all honesty, it would have never caused any actual runtime problem. However, it is considered a bug in the kernel because if someone else uses the driver as a starting point or example to write their own driver for a big-endian architecture, it can lead to a very hard-to-debug problem.

This seems a little cart-before-horse? Types with this attribute are only supported by sparse right now? Seems like we should start by adding a rig to detect these problems (note that SOF is already using sparse, so it's not alien to Zephyr), then add the types with integration to existing APIs (c.f. sys_be32_to_cpu() et. al.)? The types themselves don't get us very far along that path.

I completely agree with @andyross here. I thought Zephyr already used sparse and had a rig in place to detect its errors.


EOL check for kernel version

Hello,
I see EOL checks for openstack, but I was wondering if we could have an EOL check for the kernel version.
For example, when using the --kernel plugin, currently it is something along the lines of
kernel:
  version: 5.13.0-35-generic
  boot: ...
  cpu:
  ...

So perhaps something similar to Openstack, such as
kernel:
  version: 5.13.0-35-generic
  days-to-eol: xyz
  boot: ...
  cpu:
  ...

and a note when its past EOL

EOL info can be found at https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle (you need to zoom in a lot and the graph will turn into actual dates)


🚀 Feature: Techdocs "Watch documentation"

🔖 Feature description
Currently, it appears that there isn't a way to determine if techdocs documentation has been modified.
Introducing a feature that enables users to receive alerts when updates occur in the documentation they are monitoring would be a valuable addition. This could seamlessly integrate with the issue mentioned here (https://github.com/backstage/backstage/issues/10652) and enhance user experience. By providing real-time notifications, users can stay informed about changes in the documentation, ensuring they are always up-to-date with the latest information.
🎤 Context
In our organization, we currently host over 30 documents on our Backstage instance. Keeping track of when these documents become outdated or undergo changes is crucial, especially as we plan to introduce many more documents, potentially reaching into the hundreds.
The absence of a "watch" feature, similar to the one in Confluence, makes it challenging for us to promote widespread adoption of our Backstage instance for documentation among the broader audience within our organization.
✌ Possible Implementation
No response
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

This sounds super useful

Bump

Bumping this. Could play out really nice with the new notifications system

hey @alper98 while this could potentially be a very useful feature, it is largely dependent on the Backstage Notification System which is not currently being worked on. We can revisit this feature request when the notification API is built out and in a usable state.
For now, is the "Last Updated" date at the top of each TechDoc page useful enough to convey document recency?


Feature request: A keyword similar to its that refers to an instance

https://talonvoice.slack.com/archives/C026KPTJE6T/p1687163697513309
Message from slack reproduced here (some formatting issues):

I am trying to do this (^ being the hat I am targeting)

# comparison operators
(op | ^is) equal: user.code_operator_equal()
(op | is) not equal: user.code_operator_not_equal()
(op | is) (greater | more): user.code_operator_greater_than()
(op | is) (less | below) [than]: user.code_operator_less_than()
(op | is) greater [than] or equal: user.code_operator_greater_than_or_equal_to()
(op | is) less [than] or equal: user.code_operator_less_than_or_equal_to()

I want to replace every (op | is) with just is. If I had only one instance to change this way, I would say bring ink to its round. I am trying to do this with instances. from block ink bring every instance ink to its round However, this seems to bring every is to replace the first (op | is) so the result is
is is is is ... equal: user.code_operator_equal()
It seems like its refers to the original target. Can I say something different to make its behave as if it is scoped to the instance?

It would be nice to have a keyword like its that refers to the instance being operated on instead of referring to the last used target. This could enable some macro-like editing in one go, for instance swap every instance air with their second next token

Yeah I'm actually collecting examples for a more powerful command that allows you to do things like this.  There are a few ways to do it.  I'll file an issue with examples and possible implementations soon.  Thanks for filing

see https://github.com/cursorless-dev/cursorless/issues/1952#issuecomment-1772994742 for implementation proposal; should be fairly straightforward I think


TEIIDTOOLS-160 Adds repo info to git export success page

Adds repo information to the git export success page.  (Includes repo link, branch and folder)
see https://issues.jboss.org/browse/TEIIDTOOLS-160 for a screencap of the changed page.

Yeah, we'd have to use the info to build a link something like this:
https://github.com/mdrillin/exportTest/tree//

I amended the commit.  The folder and branch are no longer displayed in text.  They are used to build the URL which will take you directly to the repo/branch/folder location.


Corrected log call when the Tika server returns an unexpected HTTP status

The log call didn't provide a format for the status code, resulting in an exception.

Coverage remained the same at 43.506% when pulling 8df6a29ea9dc7662d28fd9adba6d4b051ad45492 on TiVoMaker:master into 368516dd48d7cfeab65594d16a63235a6b89f316 on chrismattmann:master.

Coverage decreased (-1.08%) to 42.431% when pulling fe87a2a3546ae0a8f73c5fae7b85e92daeee1ac1 on TiVoMaker:master into 368516dd48d7cfeab65594d16a63235a6b89f316 on chrismattmann:master.

Coverage decreased (-1.08%) to 42.431% when pulling<PHONE_NUMBER>2b783039f964ec49c88b0475c33d49 on TiVoMaker:master into 368516dd48d7cfeab65594d16a63235a6b89f316 on chrismattmann:master.

thank you @TiVoMaker !


Fix WebM and Theora video in HTML5 export

Fixes WebM for single-threaded platforms.
Enables Theora, which I confirmed already works without multi-threading.
Fixes #7720

Awesome, thanks!

Cherry-picked for 3.0.7.


More lenient operation when "SIMULATION" compile-time directive is defined

When using the POSIX OSAL implementation under Linux, certain things only fully work when running as root.  Specifically:

Attempts to create POSIX queues at depths greater than /proc/sys/fs/mqueue/msg_max (typically 10) will fail.
Attempts to raise the priority of user threads will fail.

The queue depth issue in particular is so frequently encountered that there is a special message printed if queue creation fails.  However, the suggested workarounds require root access, and this would not typically be the case when using an official ACES-issued Linux workstation (unless one has elevated privileges).
In order to make it easier for someone to initially get up and running with OSAL/CFE, the OSAL should be more lenient and allow the operation to succeed even if all the parameters were not met due to being a normal user and not root.
A workaround such as this can be employed if and only if compiling with the "SIMULATION" flag, as this indicates the user is performing a debug build and not running on a real target.  This way, the operation will still fail when performing a build for real hardware.

Trac comment by glimes on 2015-02-02 14:35:09:
The OSAL unit test for TIME also has a dependency on root privilege where it wants to call settimeofday() ... which is not something you want to do unless you own the whole system, as it can seriously mess up any make going on elsewhere, or in fact any process running that presumes sane behavior of gettimeofday() and timestamps in the file system.

Imported from trac issue 14.  Created by jphickey on 2015-01-13T16:45:07, last modified: 2019-08-14T14:11:46


[JOSS Review] KeyError when Well 20 data is missing

In the docs, specifically at https://bluebonnet.readthedocs.io/en/latest/forecast_varying.html#fit-wells, we use data from Well 20 that isn't directly included in the repo. Can you provide a note on using git lfs (or any other tool) to fetch that data? If left as is, we obtain the following error when running the example verbatim:
KeyError: "None of [Index(['Days', 'Gas', 'Pressure'], dtype='object')] are in the [columns]"

This is part of the reviewing process for JOSS: openjournals/joss-reviews#5255

Thank you for your comment. The data from Well 20 is available only after you install git-lfs. See the contributing part of the documentation.
I chose to use git-lfs for this with the expectation that several large files might be added to the repository for illustrative purposes.
Hope this helps.

Woops. Confirmed. I have it working, but I should be more precise in wording. Can you please include a blurb in the readme (maybe just after the python env/packages) or in the documents (where this error would otherwise appear) explicitly stating git lfs install/git lfs pull needs to be run to grab large files? Right now, the only mention of git lfs I see is under Contributing in local development. This means users who grabbed the package from pip will see this error if running through the documentation in order.

I decided the simplest solution was to move that particular file from git-lfs to git tracking. You can see the changes at #24.


Docs(web-react, web): Add Heading demo #DS-899

Description
Heading demo in web-react and web is now same as demo in web-twig
Additional context
ℹ Spaces are now different, we need fix CSS of DocsStack in all packages (WIP)
Issue reference
Demo: Heading má ve všech technologiích stejná dema

please remove web package changes

Removed

coverage: 96.46% (+25.9%) from 70.6% when pulling 39acf542d8a961e352e5dd4af082d1f072dfd91a on docs/DS-899-heading-demo into a2d8b85e4d87fef01357b4ca90f642041e5a8aa3 on main.


[Numpy]Fix einsum issue #18102

Description
Fix einsum gradient bug in Issue #18102
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@hanke580 Would you fix the lint check and add some test cases?

Sure, tests adding

This looks like something we should backport to 1.6, 1.7, 1.x branches @hanke580 @sxjscience?
cc @ciyongch

It should be backported to 1.7.

Hi @hanke580 , can you help to backport this PR to v1.7.x branch as suggested by @sxjscience and @leezu , and tag me in the new PR? Thanks.

Sure @ciyongch

@sxjscience Why isn't this backported to v1.x branch? Any specific reason or just a miss?

It's just a miss.

Can we get a cherry-pick for this?


Paths should not match at / when apiRoot is set

The router does not enforce the presence of the apiRoot when matching the request with a route. For example, with apiRoot set to /v1 both requests /v1/my/operation and /my/operation will call the handler.
Prior to normalizing the path, the router should ensure that the prefix is found.

Seems like a bug. Want to have a look? Currently busy with client work, unfortunately so might take me a bit to get around to this.

Same here, but I'll try. Meanwhile I use this workaround:
app.use((req, res, next) => {
    if (!req.path.startsWith('/v1/')) {
      return next(new NotFoundError());
    }
    api.handleRequest(req, req, res, next);
  };


Specify requirements

This project requires Microsoft Code Contracts, but does not specify it anywhere.
Please add it to the docs.

You got it, boss. Were you able to get up and running with it or are you
still stuck getting it to compile?
On 5:26AM, Fri, Jan 30, 2015 Tommy Mikalsen<EMAIL_ADDRESS>wrote:

This project requires Microsoft Code Contracts, but does not specify it
anywhere.
Please add it to the docs.
—
Reply to this email directly or view it on GitHub
https://github.com/tayfuzun/MyoSharp/issues/4.

It compiled fine when i installed ´Microsoft Code Contracts` :)

@timorzadir I updated the front page. Let me know if there's anything else you'd like me to add specifically, and I'll try to include it.

Looks great :+1:


Make Generated Cookbook Use ChefSpec Policyfile Mode

With this change, chef generate cookbook foo; cd foo; chef install; rspec works out of the box.
I also found and fixed deprecated chef library usage.

:+1:

I will follow up with a chef verify to make sure that generated cookbooks can chef install and ChefSpec out of the box.


consider using uma_profiles_supported

This issue tracks suggestion from PR https://github.com/solid/solid-oidc/pull/18#discussion_r772442817
https://docs.kantarainitiative.org/uma/wg/rec-oauth-uma-grant-2.0.html#rfc.section.2

uma_profiles_supported
OPTIONAL. UMA profiles and extensions supported by this authorization server. The value is an array of string values, where each string value is a URI identifying an UMA profile or extension. As discussed in Section 4, an authorization server supporting a profile or extension related to UMA SHOULD supply the specification's identifying URI (if any) here.

Now that the Solid-OIDC draft contains https://solid.github.io/solid-oidc/#obtaining-access-token, can this issue be marked as resolved?

Thank you @acoburn


01

01
Originally posted by @OTDGK in https://github.com/Uniswap/token-lists/issues/263

01
Originally posted by @OTDGK in https://github.com/Uniswap/token-lists/issues/263

01
Originally posted by @OTDGK in https://github.com/Uniswap/token-lists/issues/263


Revert "util: Add PrepareStmt into readOnly"

What problem does this PR solve?
What is changed and how it works?
Reverts pingcap/parser#1139
Detailed reason at https://github.com/pingcap/parser/pull/1139#issuecomment-752359369

@tangenta  PTAL

@tangenta  PTAL


an unknown error occurred. (Error code 0x80004005)

Hi, I'm getting the error in the title when trying to sync pictures and desktop folders. I used to have a folder redirection that redirect the documents folder to onedrive but it's been removed and the registry has been updated to %Userprofile%\documents. No other gpos applied. Any suggestions?

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

ID: a9fd3d64-02a4-74dd-1f2a-a25ed9a8cef8
Version Independent ID: cc17b035-3597-7194-2544-3805ad380d5d
Content: Redirect and move Windows known folders to OneDrive
Content Source: OneDrive/redirect-known-folders.md
Service: one-drive
GitHub Login: @kaarins
Microsoft Alias: kaarins

@atfernando  - thank you for submitting feedback.
Whith you getting this error I think support can address this and bring it to resolution.
I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. Based on outcome let me know if it is something that can be called out in the docs.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.


WIFI-2412: Fix radius client connectivity on OR/BDR

Update proxy config on DR to allow connection from other APs.
Signed-off-by: Arif Alam<EMAIL_ADDRESS>

Merged 25e73746, thanks


Not receiving first view Retained messages after subscribing

I have implemented the example “Advance use”. However, after subscribing do not receive all retained messages with log_filtered_messages.
With both your example and MQTTBox (Chrome browser extention) I subscribe to the same broker and topic ‘#’, and expect to receive 4 retained messages. With MQTTbox I receive all 4 messages, but with your client I only receive 2 retained messages. I tried looking into your code to explore what could be the issue, but lag the experience to debug.
My code for subscribing and handling the message:
       await client.subscribe('#')
        asyncio.create_task(log_filtered_messages(client, '#'))
        asyncio.create_task(log_unfiltered_messages(client))

What I managed to do is add debug logging and I have created the log below. In yellow highlighted the messaged that are received, but are not handled with my script.
2020-05-14 11:03:50,534 - root - DEBUG - Sending CONNECT (u1, p1, wr0, wq0, wf0, c1, k60) client_id=b''
2020-05-14 11:03:50,538 - root - DEBUG - Received CONNACK (0, 0)
2020-05-14 11:03:50,539 - root - DEBUG - Sending SUBSCRIBE (d0, m1) [(b'#', 0)]
2020-05-14 11:03:50,541 - root - DEBUG - Received SUBACK
2020-05-14 11:03:50,542 - root - DEBUG - Received PUBLISH (d0, q0, r1, m0), 'modules/...', ...  (421 bytes)
2020-05-14 11:03:50,544 - root - DEBUG - Received PUBLISH (d0, q0, r1, m0), 'modules/....', ...  (524 bytes)
2020-05-14 11:03:50,545 - root - DEBUG - Received PUBLISH (d0, q0, r1, m0), 'modules/...', ...  (498 bytes)
[topic_filter="#"]: MESSAGE 1
2020-05-14 11:03:50,546 - root - DEBUG - Received PUBLISH (d0, q0, r1, m0), 'modules/...', ...  (469 bytes)
[topic_filter="#"]: MESSAGE 2

Have you experienced this behavior before, or have an idea what is going wrong?

I actually found a solution, but lag experience to solve this in your code.
When I use mqtt_c._client.subscribe('#') I receive all 4 retained messages.

Thanks for reporting this issue. In order to help you, I need you to first make a reproducible example.
Your current example is not self-contained. That is, I can't run it from here, since I don't have:

The complete source code
The broker that you are connecting to

All that being said, I did a quick test to try and reproduce the issue anyhow. :) I used the following code:
import asyncio
from random import randrange
from asyncio_mqtt import Client

async def log_filtered_messages(client, topic_filter):
    async with client.filtered_messages(topic_filter) as messages:
        async for message in messages:
            topic = message.topic
            value = message.payload.decode()
            print(f'[topic_filter="{topic_filter}", topic={topic}]: {value}')

async def log_unfiltered_messages(client):
    async with client.unfiltered_messages() as messages:
        async for message in messages:
            print(f'[unfiltered]: {message.payload.decode()}')

async def main():
    async with Client('zeus2002003') as client:
        await client.subscribe('#')

        # You can create any number of message filters
        asyncio.create_task(log_filtered_messages(client, '#'))

        # All messages that doesn't match a filter will get logged here
        asyncio.create_task(log_unfiltered_messages(client))

        # Publish a random value to each of these topics
        topics = [
            'something/topic0',
            'something/topic1',
            'something/topic2',
            'something/topic3',
            'something/topic4',
            'something/topic5',
        ]
        while True:
            for topic in topics:
                message = randrange(100)
                print(f'[topic="{topic}"] Publishing message={message}')
                await client.publish(topic, message, qos=1, retain=True)
                await asyncio.sleep(0.1)

asyncio.run(main())

I connect to a Mosquitto MQTT broker running on another computer on the local network with hostname zeus2002003.
I first make an initial run to set the retained messages. Then, I run the code again and get the following output:
[topic="something/topic0"] Publishing message=83
[topic_filter="#", topic=floors/rooftop/illuminance]: 54
[topic_filter="#", topic=something/topic0]: 32
[topic_filter="#", topic=something/topic1]: 54
[topic_filter="#", topic=something/topic2]: 26
[topic_filter="#", topic=something/topic3]: 74
[topic_filter="#", topic=something/topic4]: 73
[topic_filter="#", topic=something/topic5]: 70
[topic_filter="#", topic=something/topic0]: 83
[topic="something/topic1"] Publishing message=20
[topic_filter="#", topic=something/topic1]: 20
[topic="something/topic2"] Publishing message=25
[topic_filter="#", topic=something/topic2]: 25
[topic="something/topic3"] Publishing message=23
[topic_filter="#", topic=something/topic3]: 23
[topic="something/topic4"] Publishing message=14
[topic_filter="#", topic=something/topic4]: 14
[topic="something/topic5"] Publishing message=25
[topic_filter="#", topic=something/topic5]: 25
[topic="something/topic0"] Publishing message=97
[topic_filter="#", topic=something/topic0]: 97
[topic="something/topic1"] Publishing message=84
[topic_filter="#", topic=something/topic1]: 84
[topic="something/topic2"] Publishing message=4
[topic_filter="#", topic=something/topic2]: 4
[topic="something/topic3"] Publishing message=80
[topic_filter="#", topic=something/topic3]: 80
[topic="something/topic4"] Publishing message=20
[topic_filter="#", topic=something/topic4]: 20
...

Note how all of the retained messages are instantly received in the beginning, as expected.
In summary, I can't reproduce the issue, sorry. Please provide a reproducible code sample so that we can get to the bottom of this. :)

Please also consider the QoS level of the retained message. Messages with a low QoS level can (and will) get lost.

I tried to create a reproducible example with the mosquito test server, but cannot reproduce it there.. I was wondering if it could be a timing issue. The broker (also mosquito) is on my machine in a virtual box, which is much faster.
import asyncio, logging, sys
from asyncio_mqtt import Client as MQTT_Client

async def mqtt_producer(logger):
    logger.info("Created new MQTT producer..")

    async with MQTT_Client('localhost', port=1883, logger=logger) as mqtt_c:

        logger.info("Connected MQTT client..")

        logger.info("Subscribing to #..")
        #mqtt_c._client.subscribe('#')
        await mqtt_c.subscribe('#')
        logger.info("Done subscribing to #..")

        while True:

            async with mqtt_c.filtered_messages('#') as messages:
                async for message in messages:

                    print('-----------')
                    print(message.payload.decode())
                    print('-----------')

            await asyncio.sleep(0)

if __name__ == "__main__":

    logger = logging.getLogger()
    logger.setLevel(logging.DEBUG)

    handler = logging.StreamHandler(sys.stdout)
    handler.setLevel(logging.DEBUG)
    formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s')
    handler.setFormatter(formatter)
    logger.addHandler(handler)

    # get event loop
    loop = asyncio.get_event_loop()
    # create producer task
    loop.create_task(mqtt_producer(logger))

These logs might help, since they show a message is already received before the log message that the subscription is done.
2020-05-14 16:12:13,715 - root - INFO - Created new MQTT producer..
2020-05-14 16:12:14,743 - root - DEBUG - Sending CONNECT (u1, p1, wr0, wq0, wf0, c1, k60) client_id=b''
2020-05-14 16:12:14,748 - root - DEBUG - Received CONNACK (0, 0)
2020-05-14 16:12:14,753 - root - INFO - Connected MQTT client..
2020-05-14 16:12:14,756 - root - INFO - Subscribing to #..
2020-05-14 16:12:14,758 - root - DEBUG - Sending SUBSCRIBE (d0, m1) [(b'#', 0)]
2020-05-14 16:12:14,762 - root - DEBUG - Received SUBACK
2020-05-14 16:12:14,765 - root - DEBUG - Received PUBLISH (d0, q0, r1, m0), 'modules/..', ...  (498 bytes)
2020-05-14 16:12:14,767 - root - INFO - Done subscribing to #..
2020-05-14 16:12:14,768 - root - DEBUG - Received PUBLISH (d0, q0, r1, m0), 'modules/..', ...  (564 bytes)
-----------
PRINTED PAYLOAD HERE..
-----------
2020-05-14 16:12:14,770 - root - DEBUG - Received PUBLISH (d0, q0, r1, m0), 'modules/..', ...  (421 bytes)
-----------
PRINTED  PAYLOAD HERE..
-----------
2020-05-14 16:12:14,772 - root - DEBUG - Received PUBLISH (d0, q0, r1, m0), 'modules/..', ...  (364 bytes)
-----------
PRINTED PAYLOAD HERE..
-----------
2020-05-14 16:13:14,758 - root - DEBUG - Sending PINGREQ
2020-05-14 16:13:14,759 - root - DEBUG - Received PINGRESP
2020-05-14 16:14:14,792 - root - DEBUG - Sending PINGREQ
2020-05-14 16:14:14,793 - root - DEBUG - Received PINGRESP
2020-05-14 16:15:14,825 - root - DEBUG - Sending PINGREQ
2020-05-14 16:15:14,830 - root - DEBUG - Received PINGRESP

Thanks for providing the full source code.

I tried to create a reproducible example with the mosquito test server, but cannot reproduce it there.. I was wondering if it could be a timing issue. The broker (also mosquito) is on my machine in a virtual box, which is much faster.

That is a very interesting observation! :)
It could very well be due to network issues. Remember that the QoS level affects how the message is delivered. Have you tried specifying qos=2 on the retained messages? Note that paho's default QoS level is 0, which means that the message will be delivered "at most once", i.e., "message may not be delivered".

I was looking through your original e-mail again and thought of something.
Hypothesis: It's due to a race condition between:

when you subscribe to the "#" topic
when you start start listening for messages

Right now, you first do step 1 and then do step 2. Try reversing these steps in your code.
That is, try to do:
import asyncio
from random import randrange
from asyncio_mqtt import Client

async def log_filtered_messages(client, topic_filter):
    async with client.filtered_messages(topic_filter) as messages:
        async for message in messages:
            topic = message.topic
            value = message.payload.decode()
            print(f'[topic_filter="{topic_filter}", topic={topic}]: {value}')

async def log_unfiltered_messages(client):
    async with client.unfiltered_messages() as messages:
        async for message in messages:
            print(f'[unfiltered]: {message.payload.decode()}')

async def publish_to_topics(client, topics):
    while True:
        for topic in topics:
            message = randrange(100)
            print(f'[topic="{topic}"] Publishing message={message}')
            await client.publish(topic, message, qos=1, retain=True)
            await asyncio.sleep(0.1)

async def main():
    async with Client('zeus2002003') as client:
        # Step 2: Start listening for messages.
        # You can create any number of message filters
        asyncio.create_task(log_filtered_messages(client, '#'))

        # All messages that doesn't match a filter will get logged here
        asyncio.create_task(log_unfiltered_messages(client))

        # Publish a random value to each of these topics
        topics = [
            'something/topic0',
            'something/topic1',
            'something/topic2',
            'something/topic3',
            'something/topic4',
            'something/topic5',
        ]
        asyncio.create_task(publish_to_topics(client, topics))

        # Wait a while to ensure that we start listening (step 2) before we
        # subscribe to the topic (step 1)
        await asyncio.sleep(1)

        # Step 1: Subscribe to the "#" topic
        await client.subscribe('#')

asyncio.run(main())

Let me know if that works for you. :)

That is it, nice find! Thanks a lot for thinking with me
Seems this is also the way it is described in the Paho example: https://github.com/eclipse/paho.mqtt.python/blob/master/examples/client_sub-multiple-callback.py

Will you change your example codes?

That is it, nice find! Thanks a lot for thinking with me

Great! I'm glad that it worked for you. :)

Seems this is also the way it is described in the Paho example: https://github.com/eclipse/paho.mqtt.python/blob/master/examples/client_sub-multiple-callback.py

Yes, same ordering between the steps.

Will you change your example codes?

Yes, I will. Even though there is technically nothing wrong with the examples as is, we might as well avoid future confusion.
Thanks again for raising this issue. :+1: Let me know if you run into other issues.
I'll leave this issue open as a reminder until I get the time to adjust the example.

I've updated the examples in README.md.


x/net/http2: too much coupling between connection and stream window sizes

I have not really reproduced the problem in the code yet, so this is based on pure source code analysis that I did a while ago (even before http2 was merged into Go 1.6), and since I was reminded of it recently and code didn't change much in that regard in my recent review I decided to finally report it.
There is too much coupling in go implementation of http2 server, which makes stream windows practically useless. The problem is that the only code path where server increments a connection window is in noteBodyRead, where both connection and stream windows are updated for the remote side. What this effectively means is that at any given time all received (but not yet read by user code) data on all streams combined cannot exceed the connection window, making only one of them dominating the flow control. And since by default connection and stream windows are equal and rather small a single stream can consume the whole connection window, making it impossible for clients to send data on all other stream.
A hypothetical problematic case would be a file uploading service, that does some database pre-processing before starting to read from Request.Body. If that pre-processing takes a long enough time it would block all other concurrent POST requests until connection window starts to finally be drained.
What's more it appears that this approach of coupling connection and stream windows does not even save memory, since newWriterAndRequest allocates the full initialWindowSize buffer, which means memory footprint is numberOfStreams * streamWindowSize anyway, so updating connection window immediately upon parsing data frames would not increase it.
As far as I could understand from the spec connection and stream windows are supposed to be separate, and one good example I've seen recently was http2 in grpc c++ implementation, where connection window is substantially larger than stream window, and the algorithm is also different, as far as I understand: connection window is used for connection-level parsing, decoupled from streams, and updates to client start when more than 3/4 of it is consumed.
Sorry for not providing a code sample to this behavior, I've been postponing this bug report for so long already because of it that I finally decided at least some bug report now would probably be better than no bug report in the foreseeable future again.

Just looking at this again. The current open bug for this is #16512 (which arose from #16510).
Even though this one came first, I'm going to close this in favor of the more succinct #16512 because I don't think there's actually any violation of the flow control specs in our http2 implementation. Let me know if I'm reading this wrong, though.


python3Packages.google-search-results: init at 2.4.2

Description of changes

add python3Packages.google-search-results
This Python package is meant to scrape and parse search results from Google, Bing, Baidu, Yandex, Yahoo, Home Depot, eBay and more, using SerpApi.
https://github.com/serpapi/google-search-results-python

add google-search-results to the dependencies of python3Packages.langchain

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

6 packages built:

python310Packages.google-search-results
python310Packages.google-search-results.dist
python310Packages.langchain
python310Packages.langchain.dist
python311Packages.google-search-results
python311Packages.google-search-results.dist

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2275

@ofborg build python310Packages.langchain python310Packages.google-search-results


Add default value in Attention layer docs

In https://www.tensorflow.org/api_docs/python/tf/keras/layers/Attention, default values of causal and dropout are not specified and a user have to look up in the source code.
I added default values to this document in this pull request.

It looks like your PR relates to the Keras component. Please submit it to the github.com/keras-team/keras repository instead. Thankyou.
@fchollet, @qlzh727

Thank you for your guidance.


Read json responses

I’d like to be able to view the actionRequestPayload which is returned from some queries.  It’s plain JSON, and our API lib chokes on trying to read it back.  I think it tried to parse it or something.  Could probably be solved by making the JSON type just resolve to a string, or maybe there are better ways.  Might be fun to try to determine, but also could be a rabbit hole of the .net graphQL provider.

@srkirkland  Looking into this, I saw you contributed something to their code, not sure if it was related, but I think we want our own scalar that just returns the raw JSON?
GetRawText


storage: add store field in watchableStore

We need to access the underlying store to use its RangeEvents function.
It is not good to use unnecessary type conversion.
The underlying store is also needed for further store upon
watchableStore.

Why do we need the KV then?

This does not make sense to me. :(

Why do we need the KV then?

Didn't notice that private field could be embedded too. Change it to avoid two same fields. Does it make sense now?

This will be conflict with https://github.com/coreos/etcd/pull/3588.
Please feel free to close my PR (I can push another PR or fetch from master after this merge).
Thanks,

LGTM

@gyuho Sorry for the conflict. :( I am merging this because this blocks my further work.
You could rebase on the master and force push to the original PR. A new PR will lose the context and conversation around the PR.

@yichengq No worry! I will just sync with this merge on the same PR.
Thanks!


Prepare database setup and upgrade script for new portal

Done https://github.com/level2-gis/gisportal/tree/master/database


Address should not be calculated automatically in neo-python prompt.py

Current behavior

What is the problem?
prompt.py is changing my strings, depending on what it "thinks" is my intention.

This is the test code:
using Neo.SmartContract.Framework;
using Neo.SmartContract.Framework.Services.Neo;
using System;
using System.Numerics;
namespace NeoContract1
{
    public class Contract1 : SmartContract
    {
        public static bool Main(string op, object[] arg)
        {
            Runtime.Notify(op);
            string arg1 = (string)arg[0];
            Runtime.Notify(arg1);
            return true;
        }
    }
}

I will put three different invocations (the second is strange because it interprets my string as I wanted to convert it to scripthash).
testinvoke 292313cbb1e0c663527c893d64182ddf87f450ff teste1 ["teste2"]
b'teste1'
b'teste2'
testinvoke 292313cbb1e0c663527c893d64182ddf87f450ff teste1 ["AK2nJJpJr6o664CWJKi1QRXjqeic2zRp8y"]
b'teste1'
b'#\xba'\x03\xc52c\xe8\xd6\xe5"\xdc2 39\xdc\xd8\xee\xe9'
testinvoke 292313cbb1e0c663527c893d64182ddf87f450ff teste1 ["AK2nJJpJr6o664CWJKi1QRXjqeic2zRp8y_"]
b'teste1'
b'AK2nJJpJr6o664CWJKi1QRXjqeic2zRp8y_'

Include a screenshot if it makes sense.

Expected behavior
testinvoke 292313cbb1e0c663527c893d64182ddf87f450ff teste1 ["AK2nJJpJr6o664CWJKi1QRXjqeic2zRp8y"]
b'teste1'
b'AK2nJJpJr6o664CWJKi1QRXjqeic2zRp8y'

What should be happening?
prompt.py shouldn't interfere in input string. If user wants address to be translated to scripthash, it must use an explicit function for it:

testinvoke 292313cbb1e0c663527c893d64182ddf87f450ff teste1 [ AddressToScriptHash("AK2nJJpJr6o664CWJKi1QRXjqeic2zRp8y")]
b'teste1'
b'#\xba'\x03\xc52c\xe8\xd6\xe5"\xdc2 39\xdc\xd8\xee\xe9'
I know this is verbose, and perhaps many people prefer things "automated", but it can limit the testing abilities of the user (like my case, where I simply cannot pass a regular address string).

Include a screenshot if it makes sense.

How to reproduce

Please explain the steps to reproduce the problem. If you are having an issue with your machine or build tools, the issue belongs on another repository as that is outside of the scope of this project.

Your environment
Let us know in what environment you're running into the issue:
Eco platform: https://neocompiler.io

OS: (Windows version/Linux distro/OSX version)
neo-python version: (hint: use np-prompt --version)
Python version: (hint: python -V)

Was this issue address in PR #483 ? cc @localhuman @ixje

Arguably. Let's see what @igormcoelho thinks of that PR in relation to his issue report.

ping @igormcoelho
will close in 2 weeks if no reaction

Oh! sorry for the delay!
It looks like it has been addressed: "Adds ability to not parse address strings such as AeV59NyZtgj5AMQ7vY6yhr2MRvcfFeLWSb when inputting to smart contract by passing the --no-parse flag"
Congratulations!

Thanks!


Git clone using ssh protocol fails on zos

01:31:39 Need passphrase for<EMAIL_ADDRESS>01:31:40 Enter passphrase for<EMAIL_ADDRESS>[Pipeline] // sshagent

@llxia @Mesbah-Alam fyi

Update: The infra team is working on making sure that curl does not tag downloaded sdk. Waiting for that work to complete.


Provide information about argument names to the IDE

TO BE SPECIFIED AFTER INTERNAL RELEASE
Summary
Blocks  https://github.com/luna/ide/issues/535
Value

Specification

Acceptance Criteria & Test Cases

Closing as not relevant due to the searcher database providing the necessary information.


OpenEvent should be more robust

As a Engineer
I want to be able to open non SCL files while keeping the current SCL file open
Background
If we want to make use of helper documents (Like XSD, NSD, NSDOC files), we need to make the OpenEvent more robust.
Currently, if the OpenEvent is emitted and is picked up by OpenSCD Core, The "docName" is set directly as the docName. This means that Docs that are opened via the OpenEvent, will always be the current document that is being edited.  This is a side effect that causes problems.
For helper Files, this should not be the case.
We can have multiple solutions for this

Split up Opening and Editing into 2 events
Add a flag to the OpenEvent
Add a fileType to the OpenEvent

Another possibility would be to have an array of editable file types as an attribute on the editor itself and let the distribution choose which opened files should be editable, then only switch to the opened file if it has an extension listed in the array. I have no strong preference for any of these solutions.
In the meantime, a hacky work-around solution for loading support documents would consist in checking if a document with that file name has already been loaded, and if not, add the document directly to the docs object.
Either way, well-known file names seem vital to dealing with supporting documents. Coming up with suitable conventions, especially as regards versioned files like schema and nsd files, would be an important task to solve.


SAM-2833 Create Survey Matrix question screen. Add Bootstrap

Added a couple of missing messages in AuthorMessages.properties too

After adding bootstrap

LGTM


Blog section issue

Hi @Suchitra-Sahoo ,
I've just submitted a pull request for the blog section issue branch. This pull request addresses the blogs in the website and I've added a few which would be useful. I've made sure to thoroughly test the changes.
Please take your time to review the code changes and provide any feedback or suggestions you may have. I'm open to making adjustments to ensure the quality and integrity of the codebase.
Thank you for taking the time to review this pull request. Your insights and expertise are highly valued!

Mention issue number and add some screenshots of changes made.

Mention issue number and add some screenshots of changes made.

Thank you for reviewing my pull request. I've attached screenshots of the changes I made and referenced the issue number as requested.
Screenshots:

Issue Number: #9
Please let me know if you need any further information or clarification.

issue #9


how to save a weights

is there a way to save and load a weghits

Hopefully something more official will come out soon, but I just published on npm my own solution for serializing and deserializing graphs for others to use:
https://www.npmjs.com/package/deeplearn-graph-serializer

@husseinabed
I have implemented a way of downloading and loading weights in pure javascript ES3/ES5. See it in the GAN demo

thanks guys that was very helpfull :)

Nice work everyone!
We will provide an official way of doing this soon. We are working hard on a new API as well as eager mode, once that solidifies we will be removing the Graph entirely and provide an official way of exporting weights :)

Good work guys


Is this repo still alive?

@muellan Is this project still being maintained? Seems like not much has happened on your side in the past 18 months?

I'm wondering the same thing. I would like to use this library in a project, but I have concerns it is dead. There's a pull request that adds C++20 though.

Wondering the same thing. I was running into some problems with C++20 and MSVC and even though I see a PR that might fix that I wonder if I should just abandon this (which would be a bummer because I quite like it) and look for something else.

after I pushed a few pullreqs I saw this issue. AFAICT no github activity since Q1 2020, but the man is still around it seems (his website is still active in Q1 2021, so keeping my options open 😄
Anyway, it's a git repo so the beauty is you can always pick what you like and work on t hat, than see about merging it back later. (My fork, for example: https://github.com/GerHobbelt/clipp -- if you use that stuff, cool, but be reminded that I currently do not test the stuff on Linux: Windows dev only ATM, as this is a small item in a bigger work, so little time for platforms that don't have my focus right now)

I have exchanged emails with @muellan  and he is still planning to maintain this library.


fixes #504 - Add trackBy functions to ngFor in component tree

Add trackBy functions to ngFor in component tree, using the unique
id field for each node.
This should improve performance when adding or removing nodes.

LGTM, though I am interested in know what @sumitarora thinks.

@sumitarora @ericjim @andrewlo I would like to understand why this works :)
I think I am probably missing something, but at the very quick and first glance it seems like it shouldn't.
Let's get some clarity on that.

@ericjim @igor-ka @andrewlo I tried on a small example with nested tree it seems to be initializing whole tree again even when using trackby. Here is the example https://github.com/sumitarora/angular2-examples

:shipit:


[Umbrella issue] Investigate, Fix and turn flaky tests on

Feel free to create new sub-issues.

[ ] #908
[ ] controllers/tc000031_plan_only_with_showplan_as_cm_no_outputs_test.go
[ ] #904
[ ] #905
[ ] #906
[ ] #907
[ ] controllers/tc000080_varsfrom_configmap_and_controlled_outputs_test.go
[ ] controllers/tc000081_varsfrom_accepts_many_configmap_controlled_outputs_test.go
[ ] controllers/tc000090_varsfrom_override_and_controlled_outputs_test.go
[ ] controllers/tc000111_with_backend_s3_no_outputs_test.go
[ ] controllers/tc000120_delete_test.go
[ ] controllers/tc000121_destroy_on_delete_test.go
[ ] controllers/tc000130_destroy_no_outputs_test.go
[ ] controllers/tc000131_destroy_no_changes_test.go
[ ] controllers/tc000140_auto_applied_should_tx_to_plan_then_apply_when_drift_detected_test.go
[ ] controllers/tc000150_manual_apply_should_report_and_loop_when_drift_detected_test.go
[ ] controllers/tc000160_auto_applied_should_tx_to_plan_when_unrelated_source_changed_test.go
[ ] controllers/tc000170_if_apply_error_we_should_delete_the_plan_and_start_over_test.go
[ ] controllers/tc000201_auto_approve_with_disabled_drift_detection_test.go
[ ] controllers/tc000230_drift_detection_only_mode_test.go
[ ] controllers/tc000241_auto_approve_with_health_checks_test.go
[ ] controllers/tc000242_bad_health_checks_test.go
[ ] controllers/tc000260_runner_pod_test.go
[ ] controllers/tc000280_inventory_test.go
[ ] controllers/tc000290_force_unlock_test.go

Relates to https://github.com/weaveworks/tf-controller/pull/863

We suspect that this is caused by the cluster state not being reset after each test run.

Note for testing:

Run the test once. If it fails, you see what's the error.
Run the test with -count: go test ./controllers -parallel 1 -count=3 -test.run Test_XXXXX [^1]
If everything is happy, run with all the tests in the same "group" (group of 10s) together with -count like go test ./controllers -parallel 1 -count=3 -test.run Test_00004 for all the 04x tests

[^1]: to use go test you need some env vars, check makefile, but these should be enough: export INSECURE_LOCAL_RUNNER=1; export DISABLE_K8S_LOGS=1; export DISABLE_TF_LOGS=1; export DISABLE_TF_K8S_BACKEND=1; export DISABLE_WEBHOOK_TLS_VERIFY=1; export KUBEBUILDER_ASSETS="$(pwd)/testbin/k8s/1.28.0-linux-amd64"


QIODevice::write (QTcpSocket): device not open

Which version of PhantomJS are you using? Tip: run phantomjs --version.
2.1.1
What steps will reproduce the problem?
Sporadically PhantomJS will hang loading a page. When this happens [WARNING] QIODevice::write (QTcpSocket): device not open is printed in the debug output. PhantomJS then hangs waiting for the resource to load (specifically one random resource will fail to load, and the rest will load just fine).
Interestingly I run this exact script in two identical Debian Jessie (also VMware) environments, one local and by a VPS provider, never had a problem. We have now switched VPS provider and have begun seeing this issue frequently, the only difference being it has 2 vCPU (could be entirely unrelated).
/opt/phantomjs/bin/phantomjs --debug=yes script.js
#10652 seems related.
Which operating system are you using?
Debian Jessie (VMware)
Did you use binary PhantomJS or did you compile it from source?
Binary
Please provide any additional information below.
Script:
var page = require("webpage").create();

page.onResourceRequested = function (request) {
  console.log(request.url + ' (request)');
};

page.onResourceReceived = function(resource) {
  console.log(resource.url + ' (' + resource.stage + ':' + resource.status + ')');
}

page.open('http://<<url>>', function (status) {
  // ...
  phantom.exit();
});

Full debug log:
2016-05-16T14:50:23 [DEBUG] CookieJar - Created but will not store cookies (use option '--cookies-file=<filename>' to enable persistent cookie storage)
2016-05-16T14:50:23 [DEBUG] Set  "http"  proxy to:  "" : 1080
2016-05-16T14:50:23 [DEBUG] Phantom - execute: Configuration
2016-05-16T14:50:23 [DEBUG]      0 objectName : ""
2016-05-16T14:50:23 [DEBUG]      1 cookiesFile : ""
2016-05-16T14:50:23 [DEBUG]      2 diskCacheEnabled : "false"
2016-05-16T14:50:23 [DEBUG]      3 maxDiskCacheSize : "-1"
2016-05-16T14:50:23 [DEBUG]      4 diskCachePath : ""
2016-05-16T14:50:23 [DEBUG]      5 ignoreSslErrors : "true"
2016-05-16T14:50:23 [DEBUG]      6 localUrlAccessEnabled : "true"
2016-05-16T14:50:23 [DEBUG]      7 localToRemoteUrlAccessEnabled : "false"
2016-05-16T14:50:23 [DEBUG]      8 outputEncoding : "UTF-8"
2016-05-16T14:50:23 [DEBUG]      9 proxyType : "http"
2016-05-16T14:50:23 [DEBUG]      10 proxy : ":1080"
2016-05-16T14:50:23 [DEBUG]      11 proxyAuth : ":"
2016-05-16T14:50:23 [DEBUG]      12 scriptEncoding : "UTF-8"
2016-05-16T14:50:23 [DEBUG]      13 webSecurityEnabled : "true"
2016-05-16T14:50:23 [DEBUG]      14 offlineStoragePath : ""
2016-05-16T14:50:23 [DEBUG]      15 localStoragePath : ""
2016-05-16T14:50:23 [DEBUG]      16 localStorageDefaultQuota : "-1"
2016-05-16T14:50:23 [DEBUG]      17 offlineStorageDefaultQuota : "-1"
2016-05-16T14:50:23 [DEBUG]      18 printDebugMessages : "true"
2016-05-16T14:50:23 [DEBUG]      19 javascriptCanOpenWindows : "true"
2016-05-16T14:50:23 [DEBUG]      20 javascriptCanCloseWindows : "true"
2016-05-16T14:50:23 [DEBUG]      21 sslProtocol : "default"
2016-05-16T14:50:23 [DEBUG]      22 sslCiphers : "ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-RC4-SHA:ECDHE-RSA-RC4-SHA:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:RC4-SHA:RC4-MD5"
2016-05-16T14:50:23 [DEBUG]      23 sslCertificatesPath : ""
2016-05-16T14:50:23 [DEBUG]      24 sslClientCertificateFile : ""
2016-05-16T14:50:23 [DEBUG]      25 sslClientKeyFile : ""
2016-05-16T14:50:23 [DEBUG]      26 sslClientKeyPassphrase : ""
2016-05-16T14:50:23 [DEBUG]      27 webdriver : ":"
2016-05-16T14:50:23 [DEBUG]      28 webdriverLogFile : ""
2016-05-16T14:50:23 [DEBUG]      29 webdriverLogLevel : "INFO"
2016-05-16T14:50:23 [DEBUG]      30 webdriverSeleniumGridHub : ""
2016-05-16T14:50:23 [DEBUG] Phantom - execute: Script & Arguments
2016-05-16T14:50:23 [DEBUG]      script: "longlinks.js"
2016-05-16T14:50:23 [DEBUG]      0 arg: "http://<<url>>/extra/thumbnail/5b7da345/"
2016-05-16T14:50:23 [DEBUG] Phantom - execute: Starting normal mode
2016-05-16T14:50:23 [DEBUG] WebPage - setupFrame ""
2016-05-16T14:50:23 [DEBUG] FileSystem - _open: ":/modules/fs.js" QMap(("mode", QVariant(QString, "r")))
2016-05-16T14:50:23 [DEBUG] FileSystem - _open: ":/modules/system.js" QMap(("mode", QVariant(QString, "r")))
2016-05-16T14:50:23 [DEBUG] FileSystem - _open: ":/modules/webpage.js" QMap(("mode", QVariant(QString, "r")))
2016-05-16T14:50:23 [DEBUG] WebPage - updateLoadingProgress: 10
http://<<url>>/extra/thumbnail/5b7da345/ (request)
http://<<url>>/extra/thumbnail/5b7da345/ (start:200)
2016-05-16T14:50:23 [DEBUG] WebPage - updateLoadingProgress: 30
http://<<url>>/static/ZFp0QlAMYG4J.png (request)
http://<<url>>/static/onBYO58oiIJR.png (request)
http://<<url>>/static/EQbyx502P9y9.jpg (request)
http://<<url>>/static/yZ09Y1iRu7lT.png (request)
http://<<url>>/static/GJqKXy2YFZjI.png (request)
http://<<url>>/static/LNtLBsD7WQoS.png (request)
http://<<url>>/static/jqHz46CNGzj3.jpg (request)
http://<<url>>/static/fvBV8Fgb42V1.jpg (request)
2016-05-16T14:50:23 [WARNING] QIODevice::write (QTcpSocket): device not open
http://<<url>>/static/bt4THB17u5Qj.jpg (request)
http://<<url>>/static/zFaNJgeXRyRp.png (request)
http://<<url>>/static/OUIs99Bk9MUY.png (request)
http://<<url>>/static/5NO8srxLf39z.png (request)
http://<<url>>/static/ifbRKeD0tzBm.png (request)
http://<<url>>/static/BlIAlMU3rUsY.png (request)
http://<<url>>/static/c3GYlR9bMQmU.png (request)
http://<<url>>/static/YTYcNDpZQmse.png (request)
http://<<url>>/static/VA0i27crKjQn.png (request)
http://<<url>>/extra/thumbnail/5b7da345/ (end:200)
http://<<url>>/static/ZFp0QlAMYG4J.png (start:200)
http://<<url>>/static/onBYO58oiIJR.png (start:200)
http://<<url>>/static/ZFp0QlAMYG4J.png (end:200)
http://<<url>>/static/EQbyx502P9y9.jpg (start:200)
2016-05-16T14:50:23 [DEBUG] WebPage - updateLoadingProgress: 32
http://<<url>>/static/onBYO58oiIJR.png (end:200)
http://<<url>>/static/EQbyx502P9y9.jpg (end:200)
http://<<url>>/static/yZ09Y1iRu7lT.png (start:200)
http://<<url>>/static/LNtLBsD7WQoS.png (start:200)
http://<<url>>/static/yZ09Y1iRu7lT.png (end:200)
http://<<url>>/static/bt4THB17u5Qj.jpg (start:200)
2016-05-16T14:50:23 [DEBUG] WebPage - updateLoadingProgress: 35
http://<<url>>/static/LNtLBsD7WQoS.png (end:200)
http://<<url>>/static/jqHz46CNGzj3.jpg (start:200)
http://<<url>>/static/fvBV8Fgb42V1.jpg (start:200)
http://<<url>>/static/OUIs99Bk9MUY.png (start:200)
http://<<url>>/static/zFaNJgeXRyRp.png (start:200)
http://<<url>>/static/ifbRKeD0tzBm.png (start:200)
http://<<url>>/static/bt4THB17u5Qj.jpg (end:200)
http://<<url>>/static/BlIAlMU3rUsY.png (start:200)
http://<<url>>/static/jqHz46CNGzj3.jpg (end:200)
http://<<url>>/static/c3GYlR9bMQmU.png (start:200)
http://<<url>>/static/fvBV8Fgb42V1.jpg (end:200)
http://<<url>>/static/OUIs99Bk9MUY.png (end:200)
http://<<url>>/static/zFaNJgeXRyRp.png (end:200)
http://<<url>>/static/5NO8srxLf39z.png (start:200)
2016-05-16T14:50:23 [DEBUG] WebPage - updateLoadingProgress: 37
http://<<url>>/static/YTYcNDpZQmse.png (start:200)
http://<<url>>/static/VA0i27crKjQn.png (start:200)
http://<<url>>/static/ifbRKeD0tzBm.png (end:200)
http://<<url>>/static/BlIAlMU3rUsY.png (end:200)
http://<<url>>/static/c3GYlR9bMQmU.png (end:200)
http://<<url>>/static/5NO8srxLf39z.png (end:200)
http://<<url>>/static/YTYcNDpZQmse.png (end:200)
http://<<url>>/static/VA0i27crKjQn.png  #(end:200)

+1 this is also happening to me as well

Also happening to us, both 2.1.1 and 2.1.0.
Happens only with phantomjs loading a site locally, maybe the network is too fast and triggered some bug?

happening in 2.1.7

Had this occur quite often on two machines running 2.1.1 (Win7 & Ubuntu 12.04). Both using --webdriver.
Sometimes there it works fine, other times this occurs and completely stalls the rest of the request/tests.
One thing I have noticed is this can occur regardless if the URL is valid or not which seems a bit strange.

I'm also facing this issue see log:
2016-11-24T10:44:59 [DEBUG] CookieJar - Created but will not store cookies (use option '--cookies-file=<filename>' to enable persistent cookie storage)
2016-11-24T10:44:59 [DEBUG] Set  "http"  proxy to:  "" : 1080
2016-11-24T10:44:59 [DEBUG] Phantom - execute: Configuration
2016-11-24T10:44:59 [DEBUG]      0 objectName : ""
2016-11-24T10:44:59 [DEBUG]      1 cookiesFile : ""
2016-11-24T10:44:59 [DEBUG]      2 diskCacheEnabled : "false"
2016-11-24T10:44:59 [DEBUG]      3 maxDiskCacheSize : "-1"
2016-11-24T10:44:59 [DEBUG]      4 diskCachePath : ""
2016-11-24T10:44:59 [DEBUG]      5 ignoreSslErrors : "false"
2016-11-24T10:44:59 [DEBUG]      6 localUrlAccessEnabled : "true"
2016-11-24T10:44:59 [DEBUG]      7 localToRemoteUrlAccessEnabled : "false"
2016-11-24T10:44:59 [DEBUG]      8 outputEncoding : "UTF-8"
2016-11-24T10:44:59 [DEBUG]      9 proxyType : "http"
2016-11-24T10:44:59 [DEBUG]      10 proxy : ":1080"
2016-11-24T10:44:59 [DEBUG]      11 proxyAuth : ":"
2016-11-24T10:44:59 [DEBUG]      12 scriptEncoding : "UTF-8"
2016-11-24T10:44:59 [DEBUG]      13 webSecurityEnabled : "true"
2016-11-24T10:44:59 [DEBUG]      14 offlineStoragePath : ""
2016-11-24T10:44:59 [DEBUG]      15 localStoragePath : ""
2016-11-24T10:44:59 [DEBUG]      16 localStorageDefaultQuota : "-1"
2016-11-24T10:44:59 [DEBUG]      17 offlineStorageDefaultQuota : "-1"
2016-11-24T10:44:59 [DEBUG]      18 printDebugMessages : "true"
2016-11-24T10:44:59 [DEBUG]      19 javascriptCanOpenWindows : "true"
2016-11-24T10:44:59 [DEBUG]      20 javascriptCanCloseWindows : "true"
2016-11-24T10:44:59 [DEBUG]      21 sslProtocol : "default"
2016-11-24T10:44:59 [DEBUG]      22 sslCiphers : "ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-RC4-SHA:ECDHE-RSA-RC4-SHA:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:RC4-SHA:RC4-MD5"
2016-11-24T10:44:59 [DEBUG]      23 sslCertificatesPath : ""
2016-11-24T10:44:59 [DEBUG]      24 sslClientCertificateFile : ""
2016-11-24T10:44:59 [DEBUG]      25 sslClientKeyFile : ""
2016-11-24T10:44:59 [DEBUG]      26 sslClientKeyPassphrase : ""
2016-11-24T10:44:59 [DEBUG]      27 webdriver : ":"
2016-11-24T10:44:59 [DEBUG]      28 webdriverLogFile : ""
2016-11-24T10:44:59 [DEBUG]      29 webdriverLogLevel : "INFO"
2016-11-24T10:44:59 [DEBUG]      30 webdriverSeleniumGridHub : ""
2016-11-24T10:44:59 [DEBUG] Phantom - execute: Script & Arguments
2016-11-24T10:44:59 [DEBUG]      script: "exportDashboardPhantom.js"
2016-11-24T10:44:59 [DEBUG]      0 arg: "http://secretdomain"
2016-11-24T10:44:59 [DEBUG]      1 arg: "1"
2016-11-24T10:44:59 [DEBUG]      2 arg: "307-1479984299"
2016-11-24T10:44:59 [DEBUG]      3 arg: "307"
2016-11-24T10:44:59 [DEBUG]      4 arg: ""
2016-11-24T10:44:59 [DEBUG] Phantom - execute: Starting normal mode
2016-11-24T10:44:59 [DEBUG] WebPage - setupFrame ""
2016-11-24T10:44:59 [DEBUG] FileSystem - _open: ":/modules/fs.js" QMap(("mode", QVariant(QString, "r")))
2016-11-24T10:44:59 [DEBUG] FileSystem - _open: ":/modules/system.js" QMap(("mode", QVariant(QString, "r")))
2016-11-24T10:44:59 [DEBUG] FileSystem - _open: ":/modules/webpage.js" QMap(("mode", QVariant(QString, "r")))
dashboardExportQueueId=1&queueId=307
2016-11-24T10:44:59 [DEBUG] WebPage - updateLoadingProgress: 10
> 1 - http://secretdomain/app/Reports/exportAdwordsReportHtml
2016-11-24T10:44:59 [DEBUG] WebPage - updateLoadingProgress: 30
> 2 - https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.6.3/css/font-awesome.min.css
> 3 - http://netdna.bootstrapcdn.com/font-awesome/3.2.1/css/font-awesome.css
> 4 - https://fonts.googleapis.com/css?family=PT+Sans:400,400i,700,700i
> 5 - https://fonts.googleapis.com/css?family=Work+Sans:100,200,300,400,500,600,700,800,900
> 6 - http://secretdomain/app/webroot/css/report-pdf.css
> 7 - http://secretdomain/app/webroot/css/cover-pdf.css
> 8 - http://secretdomain/app/webroot/js/jquery-1.10.2.js
2016-11-24T10:44:59 [DEBUG] WebPage - updateLoadingProgress: 32
2016-11-24T10:44:59 [DEBUG] WebPage - updateLoadingProgress: 34
> 9 - http://secretdomain/app/js/jquery-1.10.2.js?t=22222
> 10 - http://secretdomain/app/js/jquery.dataTables.js?t=2222222
> 11 - https://www.gstatic.com/charts/loader.js
> 12 - http://secretdomain/app/js/report_common.js
> 13 - http://secretdomain/app/js/jquery-dateFormat.js
> 14 - http://secretdomain/app/js/locale/eng.js
> 15 - http://secretdomain/app/js/common.js
> 16 - http://secretdomain/app/debug_kit/js/toolbar.js
1 200 - http://secretdomain/app/Reports/exportAdwordsReportHtml
2016-11-24T10:44:59 [DEBUG] WebPage - updateLoadingProgress: 37
2016-11-24T10:44:59 [WARNING] QIODevice::write (QTcpSocket): device not open
6 200 - http://secretdomain/app/webroot/css/report-pdf.css
2016-11-24T10:44:59 [DEBUG] WebPage - updateLoadingProgress: 39
2016-11-24T10:44:59 [DEBUG] WebPage - updateLoadingProgress: 41
2016-11-24T10:44:59 [DEBUG] WebPage - updateLoadingProgress: 43
7 200 - http://secretdomain/app/webroot/css/cover-pdf.css
8 200 - http://secretdomain/app/webroot/js/jquery-1.10.2.js
2016-11-24T10:44:59 [DEBUG] WebPage - updateLoadingProgress: 45
2016-11-24T10:44:59 [DEBUG] WebPage - updateLoadingProgress: 47
9 200 - http://secretdomain/app/js/jquery-1.10.2.js?t=22222
13 200 - http://secretdomain/app/js/jquery-dateFormat.js
12 200 - http://secretdomain/app/js/report_common.js
15 200 - http://secretdomain/app/js/common.js
14 200 - http://secretdomain/app/js/locale/eng.js
16 200 - http://secretdomain/app/debug_kit/js/toolbar.js
3 200 - http://netdna.bootstrapcdn.com/font-awesome/3.2.1/css/font-awesome.css
2016-11-24T10:44:59 [DEBUG] WebPage - updateLoadingProgress: 49
2 200 - https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.6.3/css/font-awesome.min.css
4 200 - https://fonts.googleapis.com/css?family=PT+Sans:400,400i,700,700i
5 200 - https://fonts.googleapis.com/css?family=Work+Sans:100,200,300,400,500,600,700,800,900
2016-11-24T10:45:00 [DEBUG] WebPage - setupFrame ""
> 17 - http://secretdomain/app/Reports/coverlogo.png
> 18 - http://secretdomain/app/Reports/Icons/cross.png
> 19 - http://netdna.bootstrapcdn.com/font-awesome/3.2.1/font/fontawesome-webfont.woff?v=3.2.1
> 20 - https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.6.3/fonts/fontawesome-webfont.woff?v=4.6.3
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 51
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 53
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 56
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 59
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 62
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 64
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 67
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 69
20 200 - https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.6.3/fonts/fontawesome-webfont.woff?v=4.6.3
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 72
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 75
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 77
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 79
19 200 - http://netdna.bootstrapcdn.com/font-awesome/3.2.1/font/fontawesome-webfont.woff?v=3.2.1
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 81
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 83
11 200 - https://www.gstatic.com/charts/loader.js
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 84
2016-11-24T10:45:00 [DEBUG] WebPage - updateLoadingProgress: 86
2016-11-24T10:45:00 [DEBUG] Network - Resource request error: QNetworkReply::NetworkError(ContentNotFoundError) ( "Error downloading http://secretdomain/app/Reports/coverlogo.png - server replied: Not Found" ) URL: "http://secretdomain/app/Reports/coverlogo.png"
Unable to load resource (#17URL:http://secretdomain/app/Reports/coverlogo.png)
Error code: 203. Description: Error downloading http://secretdomain/app/Reports/coverlogo.png - server replied: Not Found
17 404 - http://secretdomain/app/Reports/coverlogo.png
2016-11-24T10:45:01 [DEBUG] WebPage - updateLoadingProgress: 87
2016-11-24T10:45:01 [DEBUG] Network - Resource request error: QNetworkReply::NetworkError(ContentNotFoundError) ( "Error downloading http://secretdomain/app/Reports/Icons/cross.png - server replied: Not Found" ) URL: "http://secretdomain/app/Reports/Icons/cross.png"
Unable to load resource (#18URL:http://secretdomain/app/Reports/Icons/cross.png)
Error code: 203. Description: Error downloading http://secretdomain/app/Reports/Icons/cross.png - server replied: Not Found
18 404 - http://secretdomain/app/Reports/Icons/cross.png
1: Minimum wait time limit has been reached but the resources are not yet loaded completely.
1: Minimum wait time limit has been reached but the resources are not yet loaded completely.
1: Minimum wait time limit has been reached but the resources are not yet loaded completely.
1: Minimum wait time limit has been reached but the resources are not yet loaded completely.
1: Minimum wait time limit has been reached but the resources are not yet loaded completely.
1: Minimum wait time limit has been reached but the resources are not yet loaded completely.
1: Minimum wait time limit has been reached but the resources are not yet loaded completely.

In above log you can see only one entry for jquery.dataTables.js?t=2222222 (sent request id 10), whereas other resources like eng.js, loader.js, etc.. has 2 entries (sent request id and received response).
It happens with any js, css file.
Environment:
phantomjs version: 2.1.1
Server version: Apache/2.2.31 (Unix)
CentOS release 6.8 (Final)
Note:
Interestingly same phantomjs works fine with nginx 1.9.
Any clue ?

I am also experiencing this issue on Ubuntu 16 when running Drupal JavaScript tests (which require PhantomJS). It is totally random: a test that passes may get stuck on the next run by this error.

I am doing tests similar to juampynr's and I am seeing these occasional hangs, too:
Drupal 8 FunctionalJavascript tests on
Ubuntu 16.04
Apache 2.4.18-2ubuntu3.1
PHP 7.0.17-2+deb.sury.org~xenial+1
phantomjs version 2.1.1

I am also seeing this randomly in my CI env for Drupal javascript tests. Did any of you guys figure it out, or a workaround?

@eiriksm Nope

@eiriksm Actually the impact of this problem grew with the number of our Drupal FunctionalJavascript tests to the extent that our testsuite did not complete sometimes more than 5 times in a row.
That was no longer useful.
We are in the process of moving the tests to Webdriver / Chrome headless.
Starting point is the patch 64 at https://www.drupal.org/node/2775653.
With the additional patch from https://www.drupal.org/node/2894501 I can
configure the settings for JS without breaking the non-JS functional tests.
So I can run all four types of our tests (Unit, Kernel, Functional and FunctionalJavascript) from a single phpunit invocation.
Main issues were / are:

Screenshot support is broken in stable Chrome (60 I think), it is fixed in Canary.
mink / gastonjs / phantomjs allowed filling hidden fields, mink / webdriver / chrome does not.
mink / gastonjs / phantomjs allowed clicking elements outside the viewport (maybe even covered by other elements?), mink / webdriver / chrome does not.


Seeing empty sub modules while compiling resnet50 on Navi3x

Pass: gpu::compile_ops
x0 = @param:x0 -> half_type, {1}, {0}
@1 = @return(x0)

Validate ...

Pass: gpu::compile_ops
!x0 = @param:!x0 -> half_type, {1}, {0}
@1 = @return(!x0)

Validate ...

Pass: gpu::compile_ops
x0 = @param:x0 -> half_type, {1}, {0}
@1 = @return(x0)

Validate ...

Pass: gpu::compile_ops
!x0 = @param:!x0 -> half_type, {1}, {0}
@1 = @return(!x0)

Need to investigate why are we seeing such modules.
To reproduce run following on Navi3x
 MIGRAPHX_TRACE_COMPILE=1 ./migraphx-driver perf /models/mlperf/resnet50_v1.onnx --fp16 --exhaustive-tune

They could be coming from concat pointwise fusion which may introduce No-ops.


[WIP] Add userId parameter to signOutUser

Fixes #
Description
It was found that the TypeScript method signOutUser() differed from the C# implementation of signOutUserAsync()as it expected less parameters.
Specific Changes

userId optional parameter was added to the method
handling for when it is null was added

Testing

Pull Request Test Coverage Report for Build 220

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 87.407%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/botbuilder/src/botFrameworkAdapter.ts
0
1
0.0%

Totals

Change from base Build 214:
-0.03%

Covered Lines:
3004

Relevant Lines:
3306

💛  - Coveralls


Git sourcecontrol

We have written the needed data into your clipboard
Issue Type: Bug
in the last update, working with containers, the control of code (git) is lost, but if I use git lents it works are some problem
VS Code version: Code - Insiders 1.36.0-insider (33ba72fef9099c4b58ad812585babc3fbacb9427, 2019-06-12T19:10:50.182Z)
OS version: Windows_NT x64 10.0.17763
Remote OS version: Linux x64 4.9.125-linuxkit

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 2712)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.89GB (2.14GB free)

Process Argv

Screen Reader
no

VM
0%

Item
Value

Remote
Attached Container jhovanylinkin/shorestore:version1 (/nifty_wozniak)

OS
Linux x64 4.9.125-linuxkit

CPUs
Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (2 x 2676)

Memory (System)
1.93GB (0.13GB free)

VM
0%

Extensions (12)

Extension
Author (truncated)
Version

remote-containers
ms-
0.61.0

remote-ssh
ms-
0.42.2

remote-ssh-edit
ms-
0.42.2

remote-ssh-explorer
ms-
0.42.2

remote-wsl
ms-
0.38.0

vscode-remote-extensionpack
ms-
0.15.0

vscode-docker
Pet
0.6.2

vscode-icons
vsc
8.7.0

vscode-eslint
dba
1.9.0

gitlens
eam
9.8.2

sublime-keybindings
ms-
4.0.0

vscode-typescript-tslint-plugin
ms-
1.1.0

(1 theme extensions excluded)

because it was too large to send. Please paste.

i am also having a similar problem. as of the last update, remote ssh source control no longer works. it works however on a local copy of a repo. i uninstalled vscode server side and locally and it still does work.

https://github.com/microsoft/vscode/issues/75411


GH-40153: [C++][Python] Fix test_gdb failures on 32-bit

Rationale for this change
test_gdb.py would fail on 32-bit platforms because the gdb extension errors out when a timestamp value is larger than the platform's time_t.
What changes are included in this PR?

Catch OverflowError from the Python datetime module when trying to format a timestamp
Tweak the expected test results on 32-bit

Are these changes tested?
Yes.
Are there any user-facing changes?
No.

GitHub Issue: #40153

@github-actions crossbow submit -g python

No comment on the code, looks good to me.
The build that is testing 32-bit platforms is test-debian-11-python-3-i386 right?

The build that is testing 32-bit platforms is test-debian-11-python-3-i386 right?

Yes, it is.

@github-actions crossbow submit -g python

Test failures are unrelated.


optimize prop_set by eschewing instance_exec

Motivation

Turns out this way is ~10% faster (!).
Test plan

See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_PX5EKuGIyI6ltR
→ https://go/builds/bui_PX5EIsm0YBh4WJ
→ https://go/builds/bui_PX5FXM4wLaF79c
This change also has sorbet-runtime changes. Those tests:
→ https://go/builds/bui_PX5OLYOrnziELw

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_PX5JGW99mvkX3m
→ https://go/builds/bui_PX5Jh9I9TWDP5k
→ https://go/builds/bui_PX5JfPwwawhUDj
This change also has sorbet-runtime changes. Those tests:
→ https://go/builds/bui_PX5PMYr1nsy0s8


Image payload

This PR adds an image() method that allows the user to display an image url or local file in Ray.  It was created in response to this discussion.  I believe this could be quite useful, especially for developers generating images or image URLs dynamically.
Documentation and unit tests have been included.

Thanks!

Thanks!


When training the Chinese benchmark dataset with svtrv2_ctc, the loss drops to 64 and cannot go lower. How to resolve this?

When training the Chinese benchmark dataset with svtrv2_ctc, the loss drops to 64 and cannot go lower. How to resolve this?

Please post the details of the config file here.

I only modified the dataset path and the batch size. Could you help me figure out how to solve this?
Global:
device: gpu
epoch_num: 20
log_smooth_window: 20
print_batch_step: 10
output_dir: ./output/rec/u14m_filter/svtrv2_ctc/
eval_epoch_step: [0, 1]
eval_batch_step: [0, 500]
cal_metric_during_train: True
pretrained_model:
checkpoints:
use_tensorboard: false
infer_img:
for data or label process
character_dict_path: &character_dict_path ../tools/utils/benchmark_new1.txt
./tools/utils/EN_symbol_dict.txt
max_text_length: &max_text_length 25
use_space_char: &use_space_char False
save_res_path: ./output/rec/u14m_filter/predicts_svtrv2_ctc.txt
Optimizer:
name: AdamW
lr: 0.00065 # for 4gpus bs256/gpu
weight_decay: 0.05
filter_bias_and_bn: True
LRScheduler:
name: OneCycleLR
warmup_epoch: 1.5 # pct_start 0.075*20 = 1.5ep
cycle_momentum: False
Architecture:
model_type: rec
algorithm: SVTRv2
Transform:
Encoder:
name: SVTRv2LNConvTwo33
use_pos_embed: False
out_channels: 256
dims: [128, 256, 384]
depths: [6, 6, 6]
num_heads: [4, 8, 12]
mixer: [['Conv','Conv','Conv','Conv','Conv','Conv'],['Conv','Conv','FGlobal','Global','Global','Global'],['Global','Global','Global','Global','Global','Global']]
local_k: [[5, 5], [5, 5], [-1, -1]]
sub_k: [[1, 1], [2, 1], [-1, -1]]
last_stage: True
feat2d: False
Decoder:
name: CTCDecoder
Loss:
name: CTCLoss
zero_infinity: True
PostProcess:
name: CTCLabelDecode
character_dict_path: *character_dict_path
use_space_char: *use_space_char
Metric:
name: RecMetric
main_indicator: acc
is_filter: True
Train:
dataset:
name: RatioDataSet
ds_width: True
padding: &padding False
data_dir_list: ['/public/home/xujing2022/xqy/CDistNet_V1/Datasets/document/document_train',
'../Union14M-L-LMDB-Filtered/filter_train_hard',
'../Union14M-L-LMDB-Filtered/filter_train_medium',
'../Union14M-L-LMDB-Filtered/filter_train_normal',
'../Union14M-L-LMDB-Filtered/filter_train_easy',
]
transforms:
  - DecodeImage: # load image
      img_mode: BGR
      channel_first: False
  - PARSeqAug:
  - CTCLabelEncode: # Class handling label
      character_dict_path: *character_dict_path
      use_space_char: *use_space_char
      max_text_length: *max_text_length
  - KeepKeys:
      keep_keys: ['image', 'label', 'length']

sampler:
name: RatioSampler
scales: [[128, 32]] # w, h
# divide_factor: to ensure the width and height dimensions can be devided by downsampling multiple
first_bs: &bs 64
fix_bs: false
divided_factor: [4, 16] # w, h
is_training: True
loader:
shuffle: True
batch_size_per_card: *bs
drop_last: True
max_ratio: 12
num_workers: 4
Eval:
dataset:
name: RatioDataSet
ds_width: True
padding: True
data_dir_list: ['/public/home/xujing2022/xqy/CDistNet_V1/Datasets/document/document_test',
'../evaluation/IC13_857',
'../evaluation/IC15_1811',
'../evaluation/IIIT5k',
'../evaluation/SVT',
'../evaluation/SVTP',
]
transforms:
  - DecodeImage: # load image
      img_mode: BGR
      channel_first: False
  - CTCLabelEncode: # Class handling label
      character_dict_path: *character_dict_path
      use_space_char: *use_space_char
      max_text_length: *max_text_length
  - KeepKeys:
      keep_keys: ['image', 'label', 'length']

sampler:
name: RatioSampler
scales: [[128, 32]] # w, h
# divide_factor: to ensure the width and height dimensions can be devided by downsampling multiple
first_bs: 64
fix_bs: false
divided_factor: [4, 16] # w, h
is_training: False
loader:
shuffle: False
drop_last: False
batch_size_per_card: 64
max_ratio: 12
num_workers: 4

Here are my training logs. the accuracy starts at 86%, which is quite strange. Could you help me figure out how to solve this?

“I am using the document dataset from BCTR. The training set consists of 400,000 samples, and I used one GPU

Thank you so much for your help. I followed your instructions, and it worked!


Add CITATION.cff file

Overview
Currently there's a section in the README for citation. It would be great to add an official CITATION.cff file for citing this repository. See the github doc on how to set this up.

Working on this in #87


fix: remove rollup patch

Subj, this patch appends NODE_PATH to the moduleDirectories
which according to plugin docs would be used to
recursively search for modules.
It does, however, cause rollup to fail with an error, complaining
about absolute paths belonging in the modulePaths.
One way to work around this issue would be to split moduleDirectories
configuration across two lines, which would cause search and replace
to fail and subsequently rollup would not complain.
This workaround leads to working build, which leads me to believe that
existing comment is right and this patch is not needed in the first
place.

Thanks


Add support for running govulncheck

Add the possibility to run a Go vulnerability check on Prometheus Components

@simonpasquier - Could you review this, please?

Thank you for you pull requests, we are already using codeql and I am wondering what are the advantages of govulncheck and whether we should make the move to it?

We could also add an issue to add CI job for it or do it in this PR.

(During bug scrub)
Nice! Sounds like it's an official Go tool (https://go.dev/blog/govulncheck) and it's not in golangci-lint (golangci/golangci-lint#3199). However CI action exists for it (https://github.com/prometheus/prometheus/pull/12654/files) which means we don't technically need a Makefile cmd for that (this is what we do for golangci-lint too (https://github.com/prometheus/prometheus/blob/main/.github/workflows/ci.yml#L151).
Still we could merge this if you think it would be useful for local (pre PR) checks, WDYT @51n15t9r ?

Yes - That was my intention. To be able to run a check pre PR.

We could also add an issue to add CI job for it or do it in this PR.

If this change is okay to be merged, I can push the CI changes in a separate PR.

LGTM.
Do you have any comment though regarding @roidelapluie's question about the advantages versus CodeQL, and whether we should make the move to govulncheck instead of CodeQL? Are the two perhaps complementary?
Also, could you rebase on latest main, so we can try to pass the CI checks?

Thanks @aknuds1
Code has been rebased.
While I'm unfamiliar with CodeQL, it seems like a general-purpose code analysis tool, probably not ideal for pre-commit checks that should be used by developers.
govulncheck, on the other hand, could be a great add-on. It is simple to use and and is officially maintained by the Go team. While it does have limitations, it can be useful for initial checks during go dependency changes
In my opinion, both tools can complement each other.  govulncheck can be a developer's first check when managing dependencies, while CodeQL provides a more comprehensive analysis.

Sorry, forgot about this in the meantime :/


Azure support

Describe the bug
Application throws exception when configured to use Azure blob storage as storage.
      System.ArgumentNullException: Value cannot be null. (Parameter 'storage')
         at BaGetter.Core.PackageStorageService..ctor(IStorageService storage, ILogger`1 logger) in /_/src/BaGetter.Core/Storage/PackageStorageService.cs:line 27
         at InvokeStub_PackageStorageService..ctor(Object, Span`1)

To Reproduce
Steps to reproduce the behavior:

Download 1.1.0 version from GH releases and unzip
Configure the application to use Azure blob storage (see below my values). I followed the documented structure - https://www.bagetter.com/docs/Installation/azure#azure-blob-storage
Try to upload a package using nuget push - the exception is thrown

Expected behavior
Expected is the application use the configured storage correctly.
Screenshots
Additional context
Version 1.1.0 - downloaded from GH releases
The configuration in appsettings.json file:
  "Storage": {
    "Type": "AzureBlobStorage",
    "ConnectionString": "DefaultEndpointsProtocol=https;AccountName=...;AccountKey=...;EndpointSuffix=core.windows.net",
    "Container": "...",
  },

I have found this PR (https://github.com/bagetter/BaGetter/pull/6) describing the disable is temporary however it lasts many months now. Even project documentation is not aligned.
Is it still disabled by a reason? What is the reason? Do you have a plan/schedule to enable it back? When it might happen? Or should I make simple commit/PR to enable it?
Thank you much for your effort with the project overtaking and maintaining!

Yes Azure is disabled currently. The main problem: It cannot be activated that easily because the Azure API has changed too much and we have to make some huges changes or event make a whole rewrite of the module.
We know this is a problem, but currently no one tries to tackle it. If you want to have a look into it this would be awesome.
@Regenhardt You not currently looking into this, right?

I'm not currently on that, no. I could look into it this weekend though. I'd like to add Azure services one by one, starting with blob storage because it's the most obvious specific use case.

FYI: I've just deployed the application built locally based on https://github.com/bagetter/BaGetter/pull/128/commits/a8b4051f6f157c431bd16be6044590e7c1251a63 (one within https://github.com/bagetter/BaGetter/pull/128) and Azure blob storage usage works like a charm.
I think this issue is almost solved and ready to be closed once the PR gets merged.
Thank you very much for fast work!

@Pokorny-FirstIS thanks for testing this! I'll look at the PR now.


Fix access to Facebook avatar images

https://developers.facebook.com/blog/post/2020/10/14/required-migration-token-based-access-user-picture-oEmbed-endpoints/

Fixed by directly updating data in posts.avatar_url where the user avatar was linking to Facebook, and by updating hylo-node with correct link template for future Facebook sign-ups.
The PR:
https://github.com/Hylozoic/hylo-node/pull/554
The query used to directly updated the database was the following (where app-id and client-token are actual values) -- this has already been ran:
UPDATE users
SET avatar_url = CONCAT (avatar_url, '&access_token={app-id}|{client-token}')
WHERE avatar_url LIKE 'https://graph.facebook.com/%'


Do not hardcode Compiler flags

I tried to add an third build configuration (FastDebug) to vcpkg. As I recognized this is not easily possible.
So I decided to change the compiler flags of the default debug configuration instead.
However these are hardcoded into the the file vcpkg_configure_cmake.cmake
The user can only add additional flags by setting VCPKG_CXX_FLAGS Varibles
I suggest to put the configuration into the tripets files. Eg in variables as VCPKG_CXX_DEFAULT_FLAGS
The targeted code fragment where the flags are hardcoded:
common:
set(VCPKG_CXX_FLAGS " /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP ${VCPKG_CXX_FLAGS}")
set(VCPKG_C_FLAGS " /DWIN32 /D_WINDOWS /W3 /utf-8 /MP ${VCPKG_C_FLAGS}")
"-DCMAKE_SHARED_LINKER_FLAGS_RELEASE=/DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF ${VCPKG_LINKER_FLAGS}"
"-DCMAKE_EXE_LINKER_FLAGS_RELEASE=/DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF ${VCPKG_LINKER_FLAGS}"
"-DCMAKE_SHARED_LINKER_FLAGS_DEBUG="
"-DCMAKE_EXE_LINKER_FLAGS_DEBUG="
shared:
"-DCMAKE_CXX_FLAGS_DEBUG=/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 ${VCPKG_CXX_FLAGS_DEBUG}"
"-DCMAKE_C_FLAGS_DEBUG=/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 ${VCPKG_C_FLAGS_DEBUG}"
"-DCMAKE_CXX_FLAGS_RELEASE=/MD /O2 /Oi /Gy /DNDEBUG /Z7 ${VCPKG_CXX_FLAGS_RELEASE}"
"-DCMAKE_C_FLAGS_RELEASE=/MD /O2 /Oi /Gy /DNDEBUG /Z7 ${VCPKG_C_FLAGS_RELEASE}"
static:
"-DCMAKE_CXX_FLAGS_DEBUG=/D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1 ${VCPKG_CXX_FLAGS_DEBUG}"
"-DCMAKE_C_FLAGS_DEBUG=/D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1 ${VCPKG_C_FLAGS_DEBUG}"
"-DCMAKE_CXX_FLAGS_RELEASE=/MT /O2 /Oi /Gy /DNDEBUG /Z7 ${VCPKG_CXX_FLAGS_RELEASE}"
"-DCMAKE_C_FLAGS_RELEASE=/MT /O2 /Oi /Gy /DNDEBUG /Z7 ${VCPKG_C_FLAGS_RELEASE}"

Thanks for the suggestion!
On the master branch, these have been moved out into scripts\toolchains\windows.cmake, which can be entirely replaced by specifying (in your triplet file) VCPKG_CHAINLOAD_TOOLCHAIN_FILE.
However, this will currently suppress running vcvarsall.bat which means the build will not be able to locate cl.exe without you also specifying CMAKE_CXX_COMPILER (etcetera) in your toolchain file as well as the flags.

Closing as feature is finished. Thanks.


Upgrade to smoltcp 0.10

I'm not familial boringtun, so I upgrade smoltcp only. Since I'm not familiar to onetun too, Please check the changed code line by line to insure the changes are correct.
Now only left boringtun and clap not upgraded.

Thanks for your hard work @ssrlive, I merged and tweaked this upgrade in #58.


Fixing the commands and the Subscriber

Both encrypt and decrypt command have been modified to fix a couple of bugs :

mix of const and static variable in subscriber
could not display a class as a string

I recommand using CI for this bundle.

CI would indeed be awesome for a bundle like this

actually I just seen this pull request asking not to use any version of halite lower then 4.. any reason why you downgraded halite? https://github.com/michaeldegroot/DoctrineEncryptBundle/pull/2

@michaeldegroot yes indeed.
Halite v4 is asking for PHP7.2 as minimum requirements.
This bundle (DoctrineEncryptBundle) is claiming compatibility with PHP 7.0. This PHP version is only posible with Halite v3.