When flutter reports an exception "thrown building Widget", tell users the exact widget type (will PR)

Close https://github.com/flutter/flutter/issues/126306
Again, this is just the rough draft. If you think this looks acceptable I will add tests and polish the error message (e.g. avoid code duplication)
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

OK, let's close this one then for now.


docs(sdk): Update README.md

Fixes WB-NNNN
Fixes #NNNN
Description
First draft of new README.
Questions:

What picture to use below the W&B logo? Do we have a nice-looking, informative image we like?
Whichever image we use, it would be could to make the images click-able; when selected they redirect you to said page info. e.g. See what Yolov5 did in their environments section: https://github.com/ultralytics/yolov5#environments
Where do we store new images? In ./.github or maybe wandb/assets?

Testing
See my forked repo's update_README for preview of the new README draft: https://github.com/ngrayluna/wandb/tree/update_README
Checklist

[ ] Include reference to internal ticket "Fixes WB-NNNN" and/or GitHub issue "Fixes #NNNN" (if applicable)
[ ] Ensure PR title compliance with the conventional commits standards

I think a mention & link to W&B Server is important to highlight, with a couple of quick value props (local, private etc) https://docs.wandb.ai/guides/self-hosted - @sephmard can message here
Possibly mentioning that we work in a distributed setting too as another value prop. Its a question that comes up fairly often, https://docs.wandb.ai/guides/track/advanced/distributed-training - this one I'm less sure about

@ngrayluna @dmitryduev we've just updated the Quickstart in the app that users land on. It includes end to end runnable examples for 6 libraries
The list of libraries and runnable code for each are all here, it'd be great to replace the code in the current Integrations sections with these

@ngrayluna @dmitryduev we've just updated the Quickstart in the app that users land on. It includes end to end runnable examples for 6 libraries
The list of libraries and runnable code for each are all here, it'd be great to replace the code in the current Integrations sections with these

Updated the Keras, Lightning, and HG examples. Didn't update Torch example since it doesn't use wandb.log .

Added a Server section. It's basic at the moment. We are working to revamp those docs so I don't want to add conflicting info.


Support -q/--quiet on tile-join

Can tile-join be quiet?

Oh, sure, yes, I'll add that option. Thanks for pointing out that it is missing!

This will be fixed in https://github.com/mapbox/tippecanoe/pull/433


build error

From @spiritelf on April 9, 2016 13:51
Execution failed for task ':CordovaLib:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Copied from original issue: driftyco/ionic#6098

Hello! As this issue is more related to the ionic cli and not the framework itself i will be moving this issue over to that repo. Thanks!

Hello @spiritelf ! Are you still having this issue?

Hello all! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!

ok thanks


improve warning/error distinction in mapping validation

Currently, the mapping validation has some odd choices in terms of error vs warning. Ending parameter javadoc with a period, a very minor mistake that doesn't impact readability at all throws an error, while using improper casing only throws a warning.
note:
maybe we should only error? strict validation is always nice

update on this: my plan is to make everything error once #317 is merged


Error when running benchmark from node-swc

bench-runner:
Error in :transform:swc
Error: Error(Msg("missing field `react`"), State { next_error: None, backtrace: None })

node: v10.15.0
rustc: 1.33.0-nightly (b2b7a063a 2019-01-01)
Please help :)

It was my mistake. I fixed it it<EMAIL_ADDRESS>


How to use translation with serversideprops

I am using getServerSideProps in class component. When I am using next-translate/withTranslation api like this
import withTranslation form next-translate/withTranslation
export const getServerSideProps = async (ctx) => {
   console.log("hello");
  return ;
  };
 class Test from React.Component{

}
export default withTranslation (Test)

then I am getting error
Error: You can not use getInitialProps with getServerSideProps. Please remove getInitialProps. . How can we use next-translate api with getServerSideProps in class componet?

How is your _app.js file?

import { wrapper } from "../redux/store/store";
import { csrfToken } from "../utils/common/csrftoken";
const MyApp = ({ Component, pageProps }) => (
<>
<Component {...pageProps} csrfToken={csrfToken}/>
</>
);
export default wrapper.withRedux(MyApp);

Using a HOC (wrapper.withRedux(MyApp)) in _app.js is using getInitialProps by default in _app.js.
To avoid it, you can use this:
https://github.com/vinissimus/next-translate/issues/801#issuecomment-1059800473

Using a HOC (wrapper.withRedux(MyApp)) in _app.js is using getInitialProps by default in _app.js.
To avoid it, you can use this:
#801 (comment)

If add
export let getStaticProps = undefined

then this kind of problem occures:
"common:profile" is missing in current namespace configuration. Try adding "profile" to the namespace "common"

I believe this issue has been resolved with Next-translate 2.0, as we have rewritten the plugin and replaced the use of regex with a parser. This update has automatically addressed many of the issues related to attempting to parse items with regex.
I trust that this solution has fully resolved the matter, and as such, I will proceed to close the issue. Additionally, I would like to inform you that we have moved the plugin to this repository: https://github.com/aralroca/next-translate-plugin.
If, for any reason, you find that the issue has not been fully resolved, please feel free to reopen the issue on the next-translate-plugin repository.
Thank you very much.


Just (Video) Player

Package name
Just (Video) Player
Hash(es)
3C:B9:7D:BA:57:D3:D0:BC:19:0B:AE:5F:1F:3A:84:16:43:BC:D9:39:9B:C3:10:28:CE:25:77:5D:93:D0:10:9D
Source code link (Optional)
https://github.com/moneytoo/Player

As of now, contributing through issues won't be accepted. Please check the updated https://github.com/soupslurpr/AppVerifier/blob/master/CONTRIBUTING.md for instructions. Thanks.


Migrate devicelab to null safety.

Part of #84014.
May break this up into a couple of PRs after tests run to make it easier to review.

Broke this up into #85993, #85996, #85997, #85998, and #85999 to make it easier to review for everyone.


Yield * support

I have a hierarchical structure in a Mongo database that I'm accessing thru Mongoose. Each record has an optional field next, which has the ObjectId of the next node in the chain, if applicable. I'm trying to use ogen to ascertain this chain does not loop back onto itself, with the following code:

function* getNext(from, count) {
  let record = yield Node.findById(from).exec();
  console.log('record: ', record);
  if (record.next && count < 16)
    yield * getNext(record.next, count + 1);

  return;
}

const findNext = ogen(getNext);

function loopsBack(to, from, callback) {
  let gen = findNext(to, 0);

  const subs = gen.subscribe(
    (current) => { console.log('g: ', current); callback(true) },
    (error) => callback(false),
    () => callback(false)
  );

  subs.dispose();
}

The code works correctly until it finds a record without a next field (or where the field is null), whereby it hangs. Any ideas?

Can you reproduce the issue with no external dependencies?

Eric, the problem lies in subs.dispose(). Essentially, I was calling that method before the subscription ran its course. moving that line into the onComplete callback fixed the issue. Perhaps it's worth mentioning on the README?

Oops! This probably shouldn't be called out explicitly in this README, because that has more to do with just using observables correctly -- but we probably should link to RxJS docs. =)
Glad you figured it out!  👍


Update to ranges column in the node status command

PR: https://github.com/cockroachdb/cockroach/pull/23180
From release notes:

Previously, the ranges column in the node status command output only included ranges whose raft leader was on the node in question. It now includes the count of all ranges on the node, regardless of where the raft leader is.

No updates needed. Docs already say The number of ranges that have replicas on the node.


[Bugfix] Coordinate image removals after stopping containers

I have been using ImageFromDockerFile to build images on the fly for my tests, which are supposed to be cleaned up by default.
However, I noticed that the images were being untagged and left as dangling images in most cases (see https://github.com/dev-tools-for-enterprise-java/system-test/issues/9)
Currently Testcontianers registers shutdown hooks for:

stopping and removing containers
removing images

However, it does not coordinate these shutdown hooks. Typically the remove image hook fires before the stop+remove container hook completes, which leaves the dangling images. To solve this, we can merge the two shutdown hooks into one and therefore guarantee containers are stopped+removed before we attempt to do the image removal.

Aha, thanks @aguibert. This looks very sensible. We probably should have consolidated much sooner.
I'll have a review and think about this, but on the face of it this seems fine.
Cheers

I have the same problem in version 1.17.5. defined image as below but after test execution created image is not removed.
new CmApplicationContainer(new ImageFromDockerfile().withDockerfile(Path.of(dockerfile)))
I checked the changed code in this commit. but changes doesn't seem to exist in 1.17.5 version. thanks in advance for your help.


Invalid redirect for Wagtail Admin when browser language is not English

Steps to reproduce

Set your browser language to German
Open https://guide.wagtail.org/admin

Expected result
Login view for Wagtail Admin is shown
Actual Result
Request is redirected to https://guide.wagtail.org/de-latest/admin/ which results in a 404
Workaround: Set browser language to English to acccess the admin

Looks like this is a side effect of the locale handling middle ValidateLocaleMiddleware


Feature: support Print image pull error log during sealos run cluster

What is the problem this feature will solve?
in the first node, let the 5000 port used by another registry.
podman run -d -p 5000:5000 registry

run cluster
sealos run labiring/kubernetes:v1.25.3 --single

Sealos will be stuck all the time to pull cluster image,  and sealos don't know that his own registry is not started because 5000 port used by others.
If you have solution，please describe it
Check whether the registry is alive and throw an error to user before pulling the image.
What alternatives have you considered?
No response

I have this quitsion before, shell we support user can customize registry port?

if registry down, sealos will pull from registry.k8s.io, This registry is not accessible, just give a error:
local registry connect failed, pulling from registry.k8s.io

pulling from registry.k8s.io faild, timeout.

https://github.com/labring-actions/runtime-cache/blob/dac3c56d21ea6d40095d4d10e59f3401cdecb2e3/registry/scripts/init-registry.sh#L26
check_registry_port_inuse $registryPort in rootfs registry scripts


Better Accessibility Support

Add Better Accessibility Support To The App.

Completed In Release: v1.2.1
Commit: https://github.com/markydoodled/Note.it/commit/7dcc5ab5431b97c2077660911b3c442544634a82


vrx.launch fails in our docker noetic container

Attempting to launch VRX with:
roslaunch vrx_gazebo vrx.launch

fails with the following error:
unknown macro name: xacro:wamv_camera
when processing file<EMAIL_ADDRESS>RLException: Invalid <param> tag: Cannot load command parameter [wamv/robot_description]: command [['/opt/ros/noetic/lib/xacro/xacro', '--inorder'<EMAIL_ADDRESS>'locked:=false', 'thruster_config:=T', 'vrx_sensors_enabled:=true', 'namespace:=wamv']] returned with code [2].

Param xml is <param name="$(arg namespace)/robot_description" command="$(find xacro)/xacro --inorder '$(arg urdf)'          locked:=$(arg wamv_locked)               thruster_config:=$(arg thrust_config)          vrx_sensors_enabled:=$(arg vrx_sensors_enabled)          namespace:=$(arg namespace) "/>
The traceback for the exception was written to the log file

This same command succeeds in launching gazebo on the host using the host-based install instructions, even without rebuilding vrx. Maybe there is a missing dependency in the container?

Continuing to document this issue:
Running the xacro command directly fails in the docker image whenever the argument vrx_sensors_enabled:=true is included. This argument indirectly sets camera_enabled to true, which triggers the error. A simpler test is:
/opt/ros/noetic/lib/xacro/xacro /home/username/vrx_ws/src/vrx/wamv_gazebo/urdf/wamv_gazebo.urdf.xacro camera_enabled:=true

This works fine on the host, and fails in the Docker container with a similar error:
unknown macro name: xacro:wamv_camera
when processing file: /home/username/vrx_ws/src/vrx/wamv_gazebo/urdf/wamv_gazebo.urdf.xacro

All the files in the sensors directory are included by macros.xacro.
macros.xacro is included by wamv_gazebo.xacro at line 6
wamv_gazebo.xacro is included in wamv_gazebo.urdf.xacro at line 36.

Changing the default value of vrx_sensors_enabled to true in wamv_gazebo.urdf.xacro, i.e.
  <xacro:arg name="vrx_sensors_enabled" default="true" />

causes the build to fail in the Docker image and succeed on the host.

The contents of wamv_gazebo.xacro are:
<?xml version="1.0"?>
<robot xmlns:xacro="http://ros.org/wiki/xacro">
  <!-- Macro to create a WAM-V with dyanmics plugins and a customizeable thruster layout -->
  <xacro:macro  name="wamv_gazebo" params="thruster_layout">
    <!-- Include macros for dynamics plugins -->
    <xacro:include filename="$(find wamv_gazebo)/urdf/macros.xacro" />
    <!-- Defines the base vehicle -->
    <xacro:include filename="$(find wamv_description)/urdf/wamv_base.urdf.xacro" />
    <!-- Thruster Layout -->
    <xacro:include filename="${thruster_layout}"/>
    <!-- Attach hydrodynamics plugin -->
    <xacro:usv_dynamics_gazebo name="wamv_dynamics_plugin"/>
  </xacro:macro>
</robot>

Changing to the following resolves the problem:
<?xml version="1.0"?>
<robot xmlns:xacro="http://ros.org/wiki/xacro">
  <!-- Include macros for dynamics plugins -->
  <xacro:include filename="$(find wamv_gazebo)/urdf/macros.xacro" />
  <!-- Macro to create a WAM-V with dyanmics plugins and a customizeable thruster layout -->
  <xacro:macro  name="wamv_gazebo" params="thruster_layout">
    <!-- Defines the base vehicle -->
    <xacro:include filename="$(find wamv_description)/urdf/wamv_base.urdf.xacro" />
    <!-- Thruster Layout -->
    <xacro:include filename="${thruster_layout}"/>
    <!-- Attach hydrodynamics plugin -->
    <xacro:usv_dynamics_gazebo name="wamv_dynamics_plugin"/>
  </xacro:macro>
</robot>

I'm not sure yet why this is the case and why it works on one system but not the other.

It appears that the ROS GPG Key Expiration Incident was causing package updates on the host to fail, so these were not as up to date as the packages installed on the Docker image. I have now updated them and I'm seeing the same error on both the Docker image and the host. Something in this update appears to have changed the behavior of how include files work. A full list of the packages updated (including a few not related to the ROS problem) is below, but the update to ros-noetic-xacro seems potentially relevant. The changelog for this package has not been updated since October 2020, but I think this may be related to PR 272, which addresses this issue.
Bottom Line

Apparently the intended behavior is for macros defined within macros to be locally scoped, so they are only visible within that macro.
Previously, this was broken so internally declared macros were globally visible.
Our code relies on this behavior, so fixing it breaks our code.

Solution

For now, moving the include statement for macros.xacro as shown above fixes this problem.
Longer term, we may want to review how we have organized our macros.

List of upgraded packages (just in case someone finds a mistake in my reasoning above):
apt
apt-transport-https
apt-utils
bluez
bluez-cups
bluez-obexd
libapt-pkg6.0
libbluetooth3
libgupnp-1.2-0
linux-base
python3-rosdep
python3-rosdep-modules
ros-noetic-controller-interface
ros-noetic-controller-manager
ros-noetic-controller-manager-msgs
ros-noetic-desktop
ros-noetic-desktop-full
ros-noetic-diff-drive-controller
ros-noetic-effort-controllers
ros-noetic-forward-command-controller
ros-noetic-gazebo-ros-control
ros-noetic-geodesy
ros-noetic-geographic-info
ros-noetic-geographic-msgs
ros-noetic-hardware-interface
ros-noetic-hector-gazebo-plugins
ros-noetic-joint-limits-interface
ros-noetic-joint-state-controller
ros-noetic-joy
ros-noetic-librviz-tutorial
ros-noetic-position-controllers
ros-noetic-robot
ros-noetic-robot-localization
ros-noetic-rqt-robot-plugins
ros-noetic-rqt-rviz
ros-noetic-rviz
ros-noetic-rviz-plugin-tutorials
ros-noetic-rviz-python-tutorial
ros-noetic-simulators
ros-noetic-teleop-twist-joy
ros-noetic-transmission-interface
ros-noetic-urdf-sim-tutorial
ros-noetic-urdf-tutorial
ros-noetic-velodyne-description
ros-noetic-velodyne-simulator
ros-noetic-visualization-tutorials
ros-noetic-viz
ros-noetic-xacro

Resolved with PR #255.


Enable observability by updating service deployment pipelines through CLI automation

As a:
Developer/operator
I want:
Add service(s) deployment introspection through CLI command.
So that:
I can observe all my service deployments in GitOps process which involves many stages and pipelines before getting deployed in a Kubernetes cluster.
Describe the solution you'd like:
A CLI based tool to enable service deployment GitOps flow observability, that modifies all three Azure pipelines to call a service and persist the deployment details available at that stage in an Azure table storage.
Describe alternatives you've considered:
Setup manually by following the docs which is tedious and error prone.
Additional context:
Simplified and improved user experience for many customers.
Does this require updates to documentation?:
Yes
Implementation details:
CLI command onboard that will:

[ ] Create a script that will let us inject a task into a pipeline to update storage db

[ ] Update the first pipeline (Source repo to Container registry) in the GitOps process to call service and update the table storage.
[ ] Update the second pipeline (Container registry to HLD repo) in the GitOps process
[ ] Update the third pipeline (HLD repo to Manifests repo) in the GitOps process

[ ] Make sure that this automation does not interfere with existing manual pipeline that is already sending data to spektate storage

Acceptance Criteria:
It provides deployment observability for a service deployments in GitOps process. Once the service is enabled in GitOps observability, the user/admin can issue additional spk commands as listed in #584 epic to understand the service deployment details.

@samiyaakhtar @sarath-p @edaena this is marked as a effort -L
Seems like  Create a script that will let us inject a task into a pipeline to update storage db is really about creating a reusable piece of code of script that appends tasks to an existing yaml file. This seems complicated. Do we have a prototype of something that would give us confidence about being able to do this?
I could see complexity based upon the various parts of in a azure-pipelines.yaml file. If a client adds a new application code repo when should they run this new tool to update their azure-pipelines.yaml file?
Perhaps let's break this down to a smaller piece or investigate?

Will need to update this issue based on the outcome of microsoft/bedrock#582 and prioritize.


Table templates needed

Before we collect/generate dataset of real excel tables we need to decide on the table format that we need to find correctly.

My suggestion on format to start with (all terms according to scheme below strictly)
1. Flat table (Rows zone only)

rzone_header may be 1 or more lines
rzone_header and rzone must have same number of columns
rzone_header and rzone are directly adjacent to each other
every row in rzone must have at least one non-empty cell

3. Matrix table (Rows zone and Columns zone)

czone_header is not used in real Excel data. So we do not deal with it
Tail zone is rare in Excel. So we do not deal with it
czone may be 1 or more lines
Body zone uniquely determined by rzone and czone coordinates
rzone_header and czone may be not alligned,
rzone_header and czone may be not directly adjacent with each other (!!!)

https://www.youtube.com/watch?v=WkKh8szsRWM&list=PLsZDW92vSqQ6kVv9AW4oNmJAZPZj0jCYW&index=4


keys.py for open-source community

We should have file specific for OS devs that does not include secrets or access keys

@TylerDiorio Just FYI

Seems  to not be  related  to keys


Converting manifests/base/crd.yaml to be openAPIV3 compliant

(issue 1304)

@pa8mm Can you sign CLA first please?

Ref #1304

/ok-to-test

We use Kubebuilder to generate crds which are openapiv3 complaint. I think we don't need this change anymore?


x/text/message/catalog: documentation mentions type that doesn't exist

In the documentation for golang.org/x/text/message/catalog it says:

Package catalog defines various interfaces: Dictionary, Loader, and Message.

But there is no such type Loader. I started to change the documentation, but wasn't sure if this was an oversight, something that was removed, or some functionality that hadn't been committed yet.
/cc @mpvl

Looks like this has been missing since this package was added.


"runtimes" folder isn't a valid TFM

I'm not sure if this causes any actual problem or not, but the current folder structure of the package might not be ideal:

NuGet expects folders underneath the build folder to be valid TFMs.
It might be worth moving all of the MinVer.Cli bits into a new MinVer root folder in the package, and then update the path in MinVer.targets to be aware of the change.

@adamralph I was looking at alpha 10 in NuGet Package Explorer and noticed the following:

It turns out that as part of the .NET Core Global Tool work, the tools folder also expects subfolders to be TFMs!
Again, not sure if this would actually be a real problem (and possibly only if the PackageType metadata indicates it is a tool package), but I'm still wondering if a top-level MinVer folder would be a better idea, just to avoid any potential complications.

Ah, yes, that is less than ideal. Perhaps a custom folder is indeed best. One more thought though: what if we acknowledge that the CLI is .NET Core 2.1 app and put it in a tools TFM folder? NPE seems to like it:

That does seem like it might work, but I wonder if it's a good idea to put things in that folder structure when it's not actually a global tool?

Perhaps it's not the best idea. The best documentation I've found so far says:

Folder
Description
Action upon package install

tools
Powershell scripts and programs accessible from the Package Manager Console
The tools folder is added to the PATH environment variable for the Package Manager Console only (Specifically, not to the PATH as set for MSBuild when building the project).

That implies that all the files in that folder should be suitable to appear in the Package Manager Console's PATH, and I don't think that's the case with this package. It would actually be quite nice to be able to run dotnet MinVer.Cli.dll in the Package Manager Console, but it doesn't work because PATH can't be used in that way.
Let's go with your suggestion of a top level MinVer folder then.

Looks good:

Released in [alpha 11(https://www.nuget.org/packages/MinVer/1.0.0-alpha.11).


Header files for tests?

Most of the test cases consist of a header file along the lines of
/*
 * FooBar.h
 *
 *  Created on: look, it's a date
 *      Author: VIP
 */

#ifndef FOOBAR_H_
#define FOOBAR_H_

#include <gtest/gtest.h>
class FooBarGTest: public testing::Test {};

#endif /* FOOBAR_H_ */

The only two meaningful lines here are
#include <gtest/gtest.h>
class FooBarGTest: public testing::Test {};

I do not see any advantage from having these header files, since the unit tests are meant to be self-contained. On the contrary: they clutter any directory listing, are a nuisance to create, and typically no one reads them.
Am I missing something? Do they have a purpose? Are they required?
If not, should we get rid of them (or at least do not create them for new code)?

I agree. Those headers are useless. We can remove them in the future and they are definitely not needed for new code.

This has been resolved.


a problem running the code

The code is running ,but it has error as the picture shown.
I don't know if this will affect the results.
Please give me  some advices

I can not reproduct this error in my computer. It's caused by visdom? (please test it not use visdom) --- there is another people meet this problem, however, i am not sure how to reproduct this bug :cry: (I think it is caused by visdom)

OK，I will test it not use visdom .Thank you very much！

i try it without using visdom ,it also has this problem

i have solved this problem. I don't   python  -m visdom.server.


Improve anchor escaping logic, fixing navigation to more section names.

Bug/issue #, if applicable: 57111953
Summary
Fixes navigating to a tutorial heading with a dot in the name. This should allow having other symbols in the section names as well.
Dependencies
NA
Testing
Use the attached archive  - SlothCreator.doccarchive.zip
Steps:

Go to http://localhost:8080/tutorials/slothcreator/creating-custom-sloths#Create-a-new-project-and-add-SlothCreator.
Assert the section is scrolled to

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran npm test, and it succeeded
[x] Updated documentation if necessary

@swift-ci test


feat: Expose devenv options for nixd

This PR exposes options for modules which is required if we want to support nixd lsp natively. We would need this before https://github.com/nix-community/nixd/pull/584 is merged.

We need to expose the options from .devenv.flake.nix, so that local options are picked up.
This way if users define local options they are part of auto-complete as well.

Going another route

Is something like this being implemented? would be really helpful with some autocompletion!

@sebb3 There is ongoing work in https://github.com/cachix/devenv/tree/work/keys/lsp. I got pretty busy with my university the last few weeks, going to pick it up again.


TimezoneActions incorrect return.

in time zone actions when I copy a country that returns the time zone id instead of the local time

Needs more info. What data is incorrect. What data is correct?

if i copy for example a country like nederland the notification gives now the timezone id as return i want the local time of that country we need to use 1 paramter specific for the class timezoneactions to make this work properly i think

example if I copy netherlands it must give 15:50 (the correct local time) as a return example if I copy netherlands it should give 15:50 as return and not the time zone id


RSS feeds?

Does this page support RSS feeds? Tried adding /rss.xml and /feed.xml but I'd rather ask here now if you support it. And if not, can you enable support for it? Very useful way for us to track update releases.

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

ID: 3ffcaf54-ce86-1b30-e947-540bf07a54c3
Version Independent ID: 81267e97-e284-ff00-b081-476934538326
Content: Microsoft Edge release notes for Stable Channel
Content Source: edgeenterprise/microsoft-edge-relnote-stable-channel.md
Product: microsoft-edge
GitHub Login: @dan-wesley
Microsoft Alias: leahtu

@kbjc11686 Thank you for your feedback.  Currently, we do not support RSS feeds and we do not have anything on our short term roadmap regarding new features to notify users about documentation updates but I have passed your suggestions on to the team.


build & serve immediately quit after update to 12.0.1

🐞 Bug report
Command (mark with an x)

[ ] new
[x] build
[x] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

 Yes, the previous version in which this bug was not present was: 11.2.13
Description
 Even with --verbose, build and serve just quit. No error is prompt.
PS C:\Users\amoscatelli\Documents\Visual Studio Code\optoplus-client-ui> ng build
Node.js version v15.14.0 detected.
Odd numbered Node.js versions will not enter LTS status and should not be used for production. For more information, please see https://nodejs.org/en/about/releases/.
Option "extractCss" is deprecated: Deprecated since version 11.0. No longer required to disable CSS extraction for HMR.
PS C:\Users\amoscatelli\Documents\Visual Studio Code\optoplus-client-ui>
The same applies disabling AOT, build optomization, both in dev or prod enviroments.
🔬 Minimal Reproduction

🔥 Exception or Error

🌍 Your Environment

PS C:\Users\amoscatelli\Documents\Visual Studio Code\optoplus-client-ui> ng version
Node.js version v15.14.0 detected.
Odd numbered Node.js versions will not enter LTS status and should not be used for production.

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1200.1
@angular-devkit/build-angular   12.0.1
@angular-devkit/core            12.0.1
@angular-devkit/schematics      12.0.1
@angular/cli                    12.0.1
@angular/compiler-cli           12.0.1
@angular/language-service       12.0.1
@schematics/angular             12.0.1
typescript                      4.2.4

Anything else relevant?

As the error suggests Node.JS 15 is not supported.
Please use a supported Node.JS version. 12.20 or 14.x.x
See: https://github.com/angular/angular/issues/42076


correct clevis askpass unit conditional

A bug was introduced in PR Add default clevis luks askpass unit #79 which silently fails to configure the clevis askpass unit correctly on RHEL 8.2 and 8.3 with certain versions of the clevis-systemd package installed. This PR fixes it by changing the conditional such that if the clevis-luks-askpass.path service exists, it is enabled. If it doesn't exist, then a version of clevis-systemd that uses templated units is installed, and the unit will be enabled by dracut. Tests have been successful with templated, and static clevis-luks-askpass.path units.

[citest]


Implement the threading command line flag

Implement gradle build
Allow target image scaling, allows creation of very large mosaics
Allow multiple target images to be generated in a single execution
-The slowest part of reading and generating a large mosaic from
a long file list is reading the images.

Hey @JBirdVegas, thanks for your awesome contribution! I really appreciate it and will look into it on the weekend. Cheers, Jens


Allow to choose among a <field></field> or a <field/>.
Add a tab stop in the middle of the element if you want a closing tag.
Add a tab stop in the end.

Thanks @Yajo
Tab index inside choices will not work (Have you tested on your side). In your case ${40} will not work.
Instead of the self-closing tag can't you use a normal <field></field> tag? Is there any reason?
If you really want self-closing <field/> tag then you can create a newer snippet with the same prefix.

I don't like personally adding a closing tag to an empty element. It's just a matter of taste. :man_shrugging:
How about it now? I can write a / when I get to that tabstop and get done.

Changed! :blush:


917 update docs

Cherry pick the changes since the release

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "917-update-docs" git@github.com:moxiegirl/machine.git somewhere
$ cd somewhere
$ git rebase -i HEAD~3
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

ping @nathanleclaire @ehazlett

@moxiegirl can you sign and squash these commits?  thanks!

Didn't realize this was a cherry pick.  Thanks

LGTM


Fix babel-node, package.json intl:* scripts

Fixes: #1485
Add the current @babel/node runtime and adjust the presets
everywhere it is used to the current standards.  All of the intl:*
scripts now work.

(needs a pre-seed)

pre-seed: https://gerrit.ovirt.org/c/ovirt-engine-nodejs-modules/+/115827

ci test


CSS Variables and Multi Themes

Hey
Would like to know why CSS variables are still not used? They are generated, but the colors are taken from the already compiled ones.
If you replace everything with CSS variables, then it will be possible to create multi themes (for example, color schemes that depend on the root class)
If you suddenly need help here, then I'm always ready to help.

There are multiple issues and PRs addressing this already :). We're making more use of them in each release of v5. For example, #34100 and #34443.


Staff QR Scanner, Profile bugs

Staff QR Scanner

[ ] Display dietary restriction (exactly as it is in the API) on staff's end

Profile Dietary Restriction

[ ] Need placeholder for "None" (see screenshot) --> I believe API is sending an empty array now

[ ] Display anything not from the standard options as "custom" on profile, but display full form on staff's end when scanned

https://github.com/HackIllinois/iOS/pull/516 might need some more testing to make sure it works.

#519


Update threadpool.rst

From here: https://github.com/libuv/libuv/issues/145
Just so that someone won't ask the same thing again.

LGTM but can you amend the commit log per the guidelines in CONTRIBUTING.md?

Check it out :ok_hand:

The "subsystem" for the commit log should be "doc".

@saghul There it is and thanks for the reference about the threadpool handle. If everything's fine and you're going to merge, could it please be @bnoordhuis the one that does the commit? It would be nice for me.

If everything's fine and you're going to merge, could it please be @bnoordhuis the one that does the commit? It would be nice for me.

Sure, after that last nit Ben will do the honors :-)

Ready.

LGTM :+1:

@almosnow I don't want to be that guy but... can you sign the commit with your real name?  Thanks!

Ok
[Definitely learning a lot about git/github today]

Thanks Alex, landed in ea5f1f9!


What does EOP stand for?

In the docs, the abbreviation EOP is used in many places. Unfortunately it doesn't appear the doc discloses what it stands for.
First appears on line 204.

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

ID: 7861a800-7643-dca5-1046-232a51d6e61e
Version Independent ID: d78fc416-516b-15ab-4719-068f7d13ecca
Content: Use DMARC to validate email - Office 365
Content Source: microsoft-365/security/office-365-security/use-dmarc-to-validate-email.md
Service: o365-seccomp
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

@LeonardPeris Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/2770
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @LeonardPeris Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Github Action workflow not working as expected.

I'm having an issue here with the workflow file. I'm not sure if its an issue with my setup of something wrong with the workflow itself.
I've set up the action file in this way:
      - name: Install cargo-llvm-cov
        uses: taiki-e/install-action@cargo-llvm-cov
      - name: Run llvm-cov coverage analysis
        run: cargo llvm-cov --fail-under-functions 70 --fail-under-lines 75

These are the results of the pipeline:

Could you provide more info on the workflow?
It does not appear to be a GitHub-hosted runner and probably GITHUB_PATH does not handled correctly.

They are self hosted. Here is the complete job:
  coverage:
    strategy:
      fail-fast: false

    runs-on: [ self-hosted, default ]

    steps:
      - uses: actions/checkout@v2
      - name: Cargo cache
        uses: actions/cache@v2
        with:
          path: |
            ~/.cargo/registry
            ./target
          key: build-cargo-registry
      - name: Install cargo-llvm-cov
        uses: taiki-e/install-action@cargo-llvm-cov
      - name: Run llvm-cov coverage analysis
        run: cargo llvm-cov --fail-under-functions 70 --fail-under-lines 75

Worst case scenario I can just install via cargo and use it like that.

Setting CARGO_HOME env var with the actual cargo home for name: Install cargo-llvm-cov may work...

Thanks I'll do that!


@AfterClass not run when using groups and include methods in suite xml

I have the following test class
import org.testng.annotations.AfterClass;
import org.testng.annotations.BeforeClass;
import org.testng.annotations.Test;

public class MyTest {

    @BeforeClass(groups = {"G1"},alwaysRun = true)
    public void setup9(){
        System.out.println("In Setup");
    }

    @Test(groups = {"G1"})
    public void test(){
        System.out.println("In Test 1");
    }

    @Test()
    public void test1(){
        System.out.println("In Test 2");
    }

    @AfterClass(groups= {"G1"}, alwaysRun = true)
    public void tearDown(){
        System.out.println("In TearDown");
    }
}

Suite file specifies the two test methods:
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name="MySuite">
    <test name="MySuite" preserve-order="true">
        <classes>
            <class name="MyTest">
                 <methods>
                    <include name="test"/>
                    <include name="test1"/>
                </methods>
            </class>
        </classes>
    </test>
</suite>

When I run via maven just for group G1 the AfterClass is not run even though the G1 group is set.

mvn clean install -Dsuites=MySuite.xml -Dgroups=G1

In Setup
In Test 1

It doesn't like that test1 doesn't have the G1 group set for some reason.
If you just specify the class in the suite xml file the AfterClass runs:
<!DOCTYPE` suite SYSTEM "http://testng.org/testng-1.0.dtd" >
<suite name="MySuite">
    <test name="MySuite" preserve-order="true">
        <classes>
            <class name="com.ericsson.cifwk.taf.taffit.test.cases.MyTest">
            </class>
        </classes>
    </test>
</suite>

mvn clean install -Dsuites=MySuite.xml -Dgroups=G1

In Setup
In Test 1
In TearDown

Any ideas why the groups functionality breaks AfterClass in this scenario.

You didn't share your pom.xml but as suites is not a valid parameter for surefire, so I suppose you use it to configure suiteXmlFiles.

groups:
[...]
This parameter is ignored if the suiteXmlFiles parameter is specified.
[...]
User property is: groups.

(from surefire documentation: https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#groups)

Hi @juherr I have a similar problem.
I have a @BeforeClass method that initialized the ITestContext object which is used in my @Test class through inheritance. But when I included groups in my pom.xml, @BeforeClass is not working. I know groups have higher precedence than class, but alwaysRun =  true does not solve my purpose as some of my other methods are getting affected.

UTF-8
1
fullRegression.xml

<build>
	<pluginManagement>
		<plugins>
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-surefire-plugin</artifactId>
				<version>2.19.1</version>
				<configuration>
					<groups>${testngGroups}</groups>
					<argLine>-Xms1024m -Xmx2048m</argLine>
					<suiteXmlFiles>
						<suiteXmlFile>src/test/resources/${suiteXmlFile}</suiteXmlFile>
					</suiteXmlFiles>
					<parallel>methods</parallel>
					<threadCount>${num.threads}</threadCount>
					<failIfNoTests>true</failIfNoTests>
					<systemProperties>
						<property>
							<name>org.uncommons.reportng.escape-output</name>
							<value>false</value>
						</property>
					</systemProperties>
					<properties>
			            <property>
			              <name>testnames</name>
			              <value>${test}</value>
			            </property>
						<property>
							<name>usedefaultlisteners</name>
							<value>false</value>
						</property>
					</properties>
					<workingDirectory>target/surefire-reports/</workingDirectory>
				</configuration>
				<executions>
					<execution>
						<phase>test</phase>
						<goals>
							<goal>test</goal>
						</goals>
					</execution>
				</executions>
			</plugin>

@praveentata Could you share your xml suite file and the command you use to run it?

Suite XML -> fullRegression.xml

Command Line -->
-Dnum.threads=4 -DtestngGroups=masterData,  -DsuiteXmlFile=fullRegression.xml -Dsfdc.env=TEST -Drun.local=true -Dbrowser.type=chrome  -Dwebdriver.chrome.driver="Path" clean compile test-compile test

@praveentata According to surefire documentation, you can't mix <groups> and <suiteXmlFiles> in the same configuration.

Oh okay. What we are trying to achieve is to give Bamboo users the freedom to mention the group name and run whichever groups they want to.
The other work around we can think of is to separate Suite XML files for groups and ask them to pass the XML file names from Bamboo.
Can you suggest any other workaround for this?

@praveentata You can have a xml suite template and use the resource feature of maven to inject appropriate values.
Any other idea @krmahadevan ?

@praveentata - If all you are looking for is to provide the ability to dynamically choose groups but not have the users create multiple suite xml, then you should be looking at leveraging a beanshell.
In a nutshell, the below beanshell method selector lets you dynamically choose groups. You just need to ensure that you choose the packages appropriately.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Suite" parallel="false">
    <test name="Test">
        <method-selectors>
            <method-selector>
                <script language="beanshell">
                <![CDATA[whatGroup = System.getProperty("groupToRun");
                groups.containsKey(whatGroup);
                ]]>
                </script>
            </method-selector>
        </method-selectors>
        <classes>
            <class name="organized.chaos.GroupsPlayGround" />
        </classes>
    </test> <!-- Test -->
</suite> <!-- Suite -->
--

For a more detailed documentation on how to work with beanshell in TestNG take a look at my blog post https://rationaleemotions.wordpress.com/2013/08/21/beanshell-and-testng/

Thanks @juherr @krmahadevan  This seems to solve most of my problem.
I am trying to define the beanshell at Suite level, which doesn't seem to work. I am trying to this because I have xml like this :

I am trying to this because I have xml like this

@praveentata - I don't see the xml.

@krmahadevan I updated his message (xml is not well displayed by default in markdown)

testng.txt

I have uploaded the example file as a txt.

@juherr - Thanks.
@praveentata - This should be pretty easy to do. Here's what you need.

Make sure you are using TestNG 6.12 (latest released version of TestNG)
Build a listener that implements org.testng.IAlterSuiteListener
Within the alter() method, you basically iterate through each of the XmlTest which represents every <test> tag and inject the <method-selector> tag into it via org.testng.xml.XmlTest#getMethodSelectors().add()wherein you add an instance of org.testng.xml.XmlMethodSelector. The XmlMethodSelector can be constructed to include the beanshell that I shared earlier.

This would now ensure that each of your <test> tags have a beanshell method selector added dynamically.
For more information on how to work with IAlterSuiteListener in general and look at some of the other use cases wherein it can be leveraged, please refer to my blog posts :
https://rationaleemotions.wordpress.com/2017/09/29/building-dynamic-testng-suites/
To learn how to work with TestNG listeners in general, please refer to my blog post here : https://rationaleemotions.wordpress.com/2012/01/27/listen-to-what-i-have-to-say-about-testng-listeners/

@krmahadevan Thanks for the solution. I will try and let you know. @juherr Thank you too for the help.

Hi All,
I am facing similar issue, when I am using group then testNG control is not going to @Afterclass or @AfterSuit method and also extent report is not generating. Please help


[ja] Translate "Completing the largest migration in Kubernetes history" into Japanese

Issue
Fix https://github.com/kubernetes/website/issues/46789
Change. List
Translate content/en/blog/_posts/2024-05-20-cloud-provider-migration.md
Comment

/assign

/lgtm

/approve


Updating admins in code of conduct

Changed date format at top to make it unambiguous internationally,
Removed emails for all admins - kept it to slack username and github (feedback?)
Tried to make sure I got everyone's GitHub ID correct, please review

I was unsure on the version number - I left it as is since the contents remained the same for what people adhered to, but I'd be fine bumping it if you think we should. Alphabetizing it makes sense too. I'll update the pull request

Decided to just close it - I'll reach out to Madison in Slack to make sure she's OK with it and then we can still update the version number if we think that's appropriate. Just figured it was ready enough to merge.


[riverpod_generator] returns "Running build completed" without actually completing the build (just throwing a warning)

running locally flutter pub run build_runner build I'm not encountering any issues,
but running it in github actions I come across this warning (imho should be more than a warning)
maps:
[INFO] Generating build script...
[INFO] Generating build script completed, took 531ms

[INFO] Precompiling build script......
[INFO] Precompiling build script... completed, took 12.5s

[INFO] Initializing inputs
[INFO] Building new asset graph...
[INFO] Building new asset graph completed, took 1.1s

[INFO] Checking for unexpected pre-existing outputs....
[INFO] Checking for unexpected pre-existing outputs. completed, took 1ms

[INFO] Running build...
[INFO] Generating SDK summary...
[INFO] 3.3s elapsed, 0/13 actions completed.
[INFO] 5.8s elapsed, 0/13 actions completed.
[INFO] 7.0s elapsed, 0/13 actions completed.
[INFO] Generating SDK summary completed, took 7.0s

[INFO] 8.2s elapsed, 12/13 actions completed.
[INFO] 9.3s elapsed, 12/13 actions completed.
[INFO] 10.3s elapsed, 12/13 actions completed.
[INFO] 22.5s elapsed, 12/13 actions completed.
Warning:  No actions completed for 15.4s, waiting on:
  - riverpod_generator on lib/src/logic/map_controller.dart

[INFO] Running build completed, took 22.9s

[INFO] Caching finalized dependency graph...
[INFO] Caching finalized dependency graph completed, took 46ms

[INFO] Succeeded after 23.0s with 2 outputs (27 actions)

maps: SUCCESS

that translates in analyze error
Analyzing maps...

  error • Target of URI hasn't been generated: 'package:maps/src/logic/map_controller.g.dart' • lib/src/logic/map_controller.dart:4:6 • uri_has_not_been_generated
  error • Undefined class 'MapControllerRef' • lib/src/logic/map_controller.dart:10:37 • undefined_class

2 issues found. (ran in 8.1s)

I can only assume that build_runner wrongly claimed to have completed the build
info
I'll attach the pubspec, melos (see setup:codegen script) , and workflow files for completeness
bunch of yaml files.zip

build_runner issue:

https://github.com/dart-lang/build/issues/3546

Please share a way to reproduce the issue. There's no way to do anything otherwise

after some trouble shooting seems that the file is indeed generated and may be the analyzer yelling for no reason, closing the issue for now


[feature] Make quantum entangloporters use energy for doing their job (same way as teleporters need energy)

I guess the easiest way would be to have an additional energy input slot with it's own color. Thus if you pipe energy into it, that energy will only be used to power the connection itself.
If you want to input energy for the network, do it from another side.
Alternatively:
Just consume some of the energy that flows around in the network (even if it is a constant amount of consumption that is independent of the amount of items, gas etc that passes the network)
Right now it simply is a free global connection and feels a little bit op.
But who am I to judge what's op :D

I'm going to leave this the way it is- so many other mods offer the same technology without any kind of cost.

if i wanted it like they do it, i'd go there :/

I think a config option would be a nice middle ground.


Leverage nftoken_id, nftoken_ids and offer_id meta fields in transaction parsers

The nftoken_id, nftoken_ids and offer_id meta fields are being added to rippled 1.11.0 responses for NFToken transactions.  These can be used instead of manually parsing out the values once this version of rippled has gained more adoption.
See:

https://github.com/XRPLF/rippled/pull/4447
https://github.com/ripple/explorer/blob/staging/src/containers/shared/components/Transaction/NFTokenMint/parser.ts
https://github.com/ripple/explorer/blob/staging/src/containers/shared/components/Transaction/NFTokenAcceptOffer/parser.ts
https://github.com/ripple/explorer/blob/staging/src/containers/shared/components/Transaction/NFTokenCreateOffer/parser.ts
https://github.com/ripple/explorer/tree/staging/src/containers/shared/components/Transaction/NFTokenCancelOffer/parser.ts

Picking this one up


parse VFIO_USER_VERSION JSON stanza

This also fixes up devices w/o migration (like the gpio sample)

Do you mean in pci_config_setup()? We use dev_info there aside from checking ->migration

Do you mean in pci_config_setup()? We use dev_info there aside from checking ->migration

Ah yes, you're right.


control panel

i noticed that in this release the web control panel is gone.
is the code still in the tree ? I would really like to use it and maybe extend it. useful to me.

Very sorry about that, the control panel was served by this package called "go-rice" that does not work at all when packaged into an RPM. Also, when tiedot v3 came out, the API for handling document ID changed and several of us couldn't figure out how to fix it.
If you happen to have some extra time, you are certainly more than welcomed to create the next generation web CP for tiedot :+1:

Just curious, what exactly was the problem with the ID's? (Besides the RPM issue)
I cloned the latest master, and added the control panel from the 32bit branch, and it seems to work just fine for creating data, and querying by ID.
(I had some variables missing in main.go, and some imports that needed to be local, "github.com/HouzuoGuo/tiedot/..." -> "tiedot/...")

about a year and half ago, tiedot used to store document ID along with other document attributes, so that the ID would be deserialised along with other document attributes when retrieved.
Starting from v3, the document ID is no present in the document content. on the web UI, if user attempts to create a document with an attribute called "_id" (or "id", I do not remember clearly), the attribute will be removed before HTTP API is called.

Yes I see. It is "id" which causes the problems, but "_id" is allowed though.
Do you mind if I try to fix it, or perhaps create a new control panel?
(I am not a designer, so it might end up being ugly)

that's much appreciated! please feel free to bring it back in master, i added you as collaborator.

I am creating the control panel from scratch, so here is a quick status update:

Re-enabled the user interface section
Added functionality for localizing both html templates and errors (Using key / value pairs in JSON files)

I have created the following very basic pages: (No layout or styling yet)

List collections
List documents in a collection (Using paging, approximately 30 documents on each page)
View / edit documents (No problems when saving "id" and "_id" values)

I am new to Go, and my spare time is rather limited, so it might take some time to complete.
But it's a great learning experience for me.

Thank you soooo much for making the effort!

ktw, are you pushed your dev ?

bleve-explorer is a panel for bleve, a json-support fulltext indexer.

Did this ever happen? I'm keen to help out if it did or start something if it didn't.

@lukerodham not much progress has been made in regards to making the control panel application. Your help would be very much appreciated!


When existing task configuration loaded, the chosen KBs and chosen primary KB are not selected

They are, this is implemented. The load is asynchronous (no other way, otherwise browser would freeze), so it may take a few seconds. If the load fails, it should display an alert with an appropriate message.
...so, what exactly is not working for you? Because it works perfectly fine on my browser(s) (not just firefox).

Hopefully it works now...


[WFLY-14156]: Remove MicroProfile REST Client from Wildfly ee.

Making rest-client api optionnal in resteasy-cdi and removing it from the Jaxrs subsystem
Adding a new microprofile-rest-client in the microprofile galleon pack

Jira: https://issues.redhat.com/browse/WFLY-14156

@ehsavoie When I build this and do various comparisons of dists with and without this changeset or between various kinds of dists (legacy vs 'modern', regular vs ee-9) I see some issues:

A comparison of ee-9/build with and without this shows that standalone-microprofile.xml and standalone-microprofile-ha.xml are missing the jaxrs extension and subsystem in a build of this branch.

A comparision of the 'build' output with and without this shows that the opentracing extension and subsystem are missing in domain.xml and a bunch of configs in docs/examples/configs.

I built with -DlegacyBuild. The configs in build-legacy vs those in ee-build differ in ways they should not. The opentracing extension and subsystem are still present in build-legacy. I'll send a PR to your repo against the branch that just has the opentracing commit.

https://github.com/ehsavoie/wildfly/pull/8
Please feel free to squash that in.
I misspoke above. Without ^^^ the build fails when -DlegacyBuild is used.

@bstansberry I've fixed your issues.

The problem is that we are overwriting the jaxrs layer from ee with the one from micropfile so I had to 'merge' them in e99 to provide the full support.
and 3. were fixed in WFLY-14148 PR

@ehsavoie could you please rebase and resolve conflicts?

@ehsavoie thanks!


Control height and width of image preview

Is  there any way control this?

Did it by doing -
.st-block__editor img{
width:300px;
height:300px;
}

Also to centre image :+1:
.st-block__editor img{
width:300px;
height:300px;
display: block;
margin-left: auto;
margin-right: auto;
}


Roll engine 0602dbb27547..ddd36e8338ab (17 commits)

https://github.com/flutter/engine/compare/0602dbb27547...ddd36e8338ab
git log 0602dbb27547cd03d8f8e816b7995cace854f7e6..ddd36e8338ab4c4369ec5d46c1085d8caad6fe9a --no-merges --oneline
ddd36e833 Revert "Keyboard support for embedded Android views. (#9203)" (flutter/engine#9239)
afb5dc400 Roll src/third_party/skia 14c8ca93db18..53ae936b8447 (1 commits) (flutter/engine#9236)
069e38a0b Document AccessibilityBridge.java (flutter/engine#9237)
3590e55e5 Roll src/third_party/dart 6d608fb52b..d10dffbfbf (3 commits)
06dbe28e3 Fix instantiateImageCodec api diff with web (stub) (flutter/engine#9234)
99240b7ad Remove unnecessary whitelisted flags for --dart-flags (flutter/engine#9233)
8eaddd606 Add web integration test to build_and_test_host (flutter/engine#9218)
a7fb7da34 Roll src/third_party/dart 9f2f5adb64..6d608fb52b (5 commits)
041c79114 Roll src/third_party/skia fe18de506097..14c8ca93db18 (11 commits) (flutter/engine#9231)
086b5a48d move webOnlyScheduleFrameCallback off of window (flutter/engine#9222)
8a6bad6ef Roll src/third_party/dart 40ef0c6d9f..9f2f5adb64 (4 commits)
91ee78068 Roll src/third_party/skia 6faf8d662af8..fe18de506097 (1 commits) (flutter/engine#9228)
828191990 Roll src/third_party/dart 6e0d978505..40ef0c6d9f (7 commits)
9dafb40a2 Roll src/third_party/skia 0e8362655a66..6faf8d662af8 (1 commits) (flutter/engine#9225)
e3b8b6120 Roll src/third_party/skia 3431d9d1dcc6..0e8362655a66 (2 commits) (flutter/engine#9223)
e80df363d Keyboard support for embedded Android views. (flutter/engine#9203)
2ec6dada6 Roll src/third_party/skia 6e4fee8c812e..3431d9d1dcc6 (17 commits) (flutter/engine#9221)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (bmparr@google.com), and stop
the roller if necessary.

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/5641567742722048

Commit queue failed; closing this roll.


Feat: Attach NFT media from connected wallet to Media Gallery

Description
Secondary upload button on media gallery screen added, opens up a modal when pressed that displays all owned NFTs of that connected wallet through Alchemy NFT API.
When the user selects an NFT, it takes the NFT image file and uploads to web3storage and populates the CID and the name.
Issue
fixes #449
dework task - https://app.dework.xyz/geo-web/cadastre?taskId=07cf1133-493e-4ef4-b986-14ecf1bba69e
Checklist:

[x] My commit message follows the Conventional Commits specification
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have tested my code
[x] My changes generate no new warnings
[x] My PR is rebased off the most recent develop branch
[x] My PR is opened against the develop branch

Alert Reviewers
@codynhat @gravenp @tnrdd

Thanks for the feedback @gravenp.

The "Wallet Icon" on the new button on the Media Gallery page isn't loading for me

Looks like I forgot to commit the icon file. I will add it.

Could we add support to pull NFTs from Ethereum mainnet in addition to the network that the user is currently connected to? I think most users will have the bulk of their collections there.

Makes sense, I will look into a way to do this with the Alchemy sdk.

There's a noticeable delay between clicking Select on the "NFTs Held by..." page and returning to the "Media Gallery" page. Seems like there's some processing going on before navigation. Since there is already a spinner on the "Media Gallery" page, is it possible to navigate instantly and have all the processing take place with that pending spinner shown? If that's not appropriate, we should add a spinner to the Select button to let the user know something is going on. I found myself clicking multiple times thinking it didn't work.

Yes I agree with this. We can make it instantly navigate back to the main media gallery modal for a better user experience.

I will try to get these changes done by either tomorrow night or Monday.

Hey @jordang7. Thanks for the PR! We met on a call earlier today to discuss this. The main outstanding issue is that this currently assumes that NFT metadata are all IPFS URIs and attempts to re-upload assets to Web3.storage. To make this cleaner and easier, we think it is best to just take the URI from NFT metadata and insert directly into the content field of the MediaObject. There is no need to re-upload or check the URI at all. Browsers will read the URI and decide how to fetch the content.

Hey @jordang7. Looks like I messed something up with the build settings for geo-web-cadastre-testnet. We are going to review this preview (https://bafybeieixxalspz732cp5a55lx4rnrdyfspp6m4suui537jd6a3ml2zuoe.on.fleek.co/) at geo-web-cadastre-staging, which uses mainnet config.


Add support for aarch64-apple-darwin architecture

I tried to run the installer script, and was met with this error:
ERROR: there isn't a package for aarch64-apple-darwin

Thanks ! I saw somewhere that supports for mdbook was planned (or already implemented, are there some instructions available ?

hi! yes- mdbook is supported and already on main. we haven't officially released oranda yet - so the docs are not in the best place but you can see an example in the cargo-dist repo:

config: https://github.com/axodotdev/cargo-dist/blob/main/cargo-dist/oranda.json#L11 (takes a single key that represents the path to your built mdbook)
ci: https://github.com/axodotdev/cargo-dist/blob/main/.github/workflows/web.yml (note that CI installs mdbook and builds the book, then runs oranda)

i'm hoping to auto generate the CI for folks in #188 - the main thing is that oranda won't build your mdbook for you (yet?) but can grab your built mdbook for you and publish it as part of your site.

Perfect! I'm really interested in the project, but i'll wait for the first release before adopting it.


added  Hadolint configuration file

Changes:
Added Hadolint configuration file for configuring rules

@xinredhat Also, I see just the config file. What about the GitHub actions for hadolint? Or have you set this up in openshift-ci? If so, please update that link in this PR's description.

Or have you set this up in

@bnallapeta yes, as they helped fixed the openshift CI issue. I will continue using Openshift CI for Hadolint check. This is the CI PR implemented with Openshift CI.
https://github.com/openshift/release/pull/31602


Implement Publish Modal in Editor

The publish modal should do two things on the editor page:

Option to get mosaic tile server URL that can be embedded in a leaflet map
Download PNG of mosaiced image

In the future the publish dialog will go through a process of actually generating a new scene via a spark job; however, for now we want to give users these options.

Are there any mockups for this?

No there are not, don't worry about the styling for now - just use our
default modal.
On Wed, Jan 4, 2017 at 10:12 AM, Alex Kaminsky<EMAIL_ADDRESS>wrote:

Are there any mockups for this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/azavea/raster-foundry/issues/831#issuecomment-270393856,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA20DD1ldAZC71OHvqP6Q2pRnldwlGOpks5rO7bXgaJpZM4LW7tk
.

--
Chris Brown, GIS Software Developer
Azavea |  990 Spring Garden Street, 5th Floor, Philadelphia, PA
<EMAIL_ADDRESS>| P<PHONE_NUMBER> | F<PHONE_NUMBER>
Web azavea.com http://www.azavea.com/  |  Blog azavea.com/blogs
http://www.azavea.com/Blogs  | Twitter @azavea http://twitter.com/azavea

Closed by #879


document using this.element with addEventListener

This would have saved me a few minutes of head scratching when upgrading from the old jQuery-compatible API (this.addEventListener(this.$(), 'scroll', fn);)

I've addressed this in #67. We now support the following API:
addEventListener(this, 'click', fn);

This will use the component's element by default if no element is provided.


Predict next Sequence of numbers Using LSTM

Fixed: #806
Here, I have Taken Long Term Short Memory (LSTM) approach with importing libraries like numpy, pandas and PyTorch.
Loaded the dataset (Created on my own self) based on the airline passengers like monthly, number of passengers on that date.
Done Data Preprocessing, Split the data into testing and training set, Defined the LSTM Model, Trained the model, Evaluated and Got the final result.
The model's performance is evaluated, demonstrating its capability to generate sequences that follow the learned pattern from the training data.
Created a README file with the step wise and kept Output (Final Result).
I have done with this issue. Kindly Review and Merge my Pull Request.
I have resolved file and added new outputs.

@Niketkumardheeryan I have resolved the entire file and added new outputs,
Please review and merge it.

@vivekvardhan2810 For each PR, a new branch must be created first and then commit to it. Avoid pushing changes directly to master branch.

Okay


How can I extend the original mxGraph prototype?

How can I extend the original mxGraph prototype?
Something like this.
mxGraph.prototype.pageBreakColor = '#c0c0c0';
....
 var graphUpdatePageBreaks = mxGraph.prototype.updatePageBreaks;

mxGraph.prototype.updatePageBreaks = function(visible, width, height)
{
	var useCssTranforms = this.useCssTransforms, scale = this.view.scale,
		translate = this.view.translate;

	if (useCssTranforms)
	{
		this.view.scale = 1;
		this.view.translate = new mxPoint(0, 0);
		this.useCssTransforms = false;
	}

	graphUpdatePageBreaks.apply(this, arguments);

	if (useCssTranforms)
	{
		this.view.scale = scale;
		this.view.translate = translate;
		this.useCssTransforms = true;
	}
};

@rabpeter have you been able to fix you issue?
It seems that you have copied/adapted this repository to manage your own solution

https://github.com/rabpeter/ts-mxgraph-factory
https://github.com/rabpeter/ts-mxgraph

@tbouffard Yep. I solved the problem with my own packages and published them on NPM.
https://www.npmjs.com/package/ts-mxgraph

@rabpeter cool, good news then.
I am aware of your package because I work on a project that have forked it (https://github.com/process-analytics/ts-mxgraph) to add missing mxGraph type defintions.
That's why I contacted you in https://github.com/rabpeter/ts-mxgraph-typings/issues/1 as I did with the asual/mxgraph-factory repository owner (see #9) to know if you would be interested in joining a dedicated community initiative to provide mxGraph type definitions through the DefinitelyTyped project.

@rabpeter hello are you still interested in or working on mxgraph typescript integration?
I would like to talk to you about https://github.com/rabpeter/ts-mxgraph-typings/issues/1


Can't save host

When I add my host url it just spins.

Hi there. Thank you for trying out my app, I really appreciate it.
The infinite loop on startup is my bad, I overlooked that. But I could recreate it and will fix it in the next release.
The issue occurs when trying to add an address as host that doesn't exist. In that case, the code wouldn't know what to do and would freeze in that state. Make sure your Ollama instance is located in the root of your URL; with protocol, subdomains and port. Are you sure you're online and the host you entered is accessible?


Rename preset wind

UnoCSS version
Any
Describe the bug
WindiCSS is sunset. That would lead one to believe you shouldn't use preset wind in new projects. However it's unclear if preset wind is sunset as well. There was a bit of discussion about this on the Svelte Discord. It'd probably be clearer to call it preset tailwind
Reproduction
Library available via npm
System Info
No response
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

It's wind not windi. Meaning it would be a common part between tailwind and windi.
WindiCSS the tools are sunsetting (but not deprecated btw), that said it doesn't mean the good conventions it brought up should be sunset as well.
preset-wind is not a 1:1 equivalent of tailwind, and we are not going to maintain one (leaving that to the community if someone finds that valuable). I don't think we are going to rename it any sooner. Thanks for bringing this up.


Intermittent DNS issues with Windows containers

This will be a long explanation of the issue and the investigations that were performed, so best grab a coffee first. Also this issue was initially reported at https://github.com/docker/for-win/issues/12638 but suggested to report it here.

[x ] I have tried with the latest version of Docker Desktop
[x ] I have tried disabling enabled experimental features

Actual behavior
Running this powershell in a Windows container, results in 1-3 timed out responses: for ($i=0;$i -lt 100;$i++) {nslookup google.com}
Expected behavior
No DNS requests should fail.
Information
The issue original issue is that our applications (.net core in windows containers in a kubernetes cluster) intermittently fail with the error: "No such host is known" when communicating with various resources (other services, database, etc).
We managed to reproduce the issue on a dev machine by running the powershell script in a windows container: for ($i=0;$i -lt 100;$i++) {nslookup google.com}
To exclude any issues with our work environment, I took this to a beefy vanilla machine (my personal gaming pc), with no prior docker installed. Installed Docker, activated Hyper-V, ran the container and the script, and same issue. In depth details bellow.

Windows version: 20H2 10.0.19042.1586 (reproduces on different versions of windows)
Docker version: 20.10.13 (on earlier versions as well)
Docker image: mcr.microsoft.com/windows/servercore:10.0.19042.1586
Hyper-V (AFAIK)

Steps to reproduce the behavior

Run the docker command to start the container and enter interactive mode

docker run -it mcr.microsoft.com/windows/servercore:10.0.19042.1586 cmd

After starting the container, run powershell to switch to powershell.

First thing I ran the following powershell scripts inside the container, on my setup, to set Google DNS servers, as the default DNS server wasn't working. In our work setup we also inject custom DNS servers, but it should not be related as I'll explain below :

get-netadapter "Ethernet" | Set-DnsClientServerAddress -ResetServerAddresses

$network = (get-netadapter).name | Select-Object -Last 1
Set-DnsClientServerAddress -InterfaceAlias $netwowrk -ServerAdresses ("<IP_ADDRESS>","<IP_ADDRESS>")

Next, after confirming with ipconfig /all that only the Google DNS servers are used, I run the following powershell script:

for ($i=0;$i -lt 100;$i++) {nslookup google.com}

On my setup, almost all the time, the script pauses 3 times, for 2 seconds each time, and in that case I see DNS request timed out.. On the work setup, it's about once in two runs.

To confirm that it's not a Google DNS issue, I run the same script for ($i=0;$i -lt 100;$i++) {nslookup google.com} from the host machine, with no timeouts. (repeated the test multiple times with no timeouts).

 First, investigate the packets for the Ethernet adapter vEthernet (nat) (I'll share the capture if it's deemed useful, but for the sake of already long issue, I'm skipping it). To best of my knowledge, this is the adapter that the container communicates with. Here we see DNS UDP packets that are sent, but don't have a reply packet.

Sidenote: It's not necessarily just the DNS UDP that don't get a reply, I suspect there might be some other packets that don't get a reply in time, and blocks nslookup; but ATM I can not confirm.

Now that we know there are packets lost, let's check if those packets reach our physical network interface. I run Wireshark on my physical network interface, and filter only DNS A type packets dns.qry.name == "google.com" && dns.qry.type == 1. Run the script again in the container. I can see 198 packets filtered (request/reply). So only 99 out of 100 DNS requests reached physical interface (I did check that all requests have a response).

Notice that I mentioned earlier that there are usually 3 timeouts but in this Wireshark I usually see just 1 missing request/response because of the Wireshark filter. So far that's the one type of packet I identified for sure as missing in action, but there are more types that I can't put my finger on.
Conclusions
Based on that research I draw the conclusion that some DNS (and maybe not only DNS) UDP packets get lost between the vEthernet NAT interface and the physical ethernet interface.
Questions
Can I investigate something further? I'm not a network guy, and best I can do is reading Wireshark logs, but how the routing behind is done or what is involved is all black-box to me.

Hey! Thanks for posting this detailed writeup. Have you had a look at #216?

Opening MSFT internal 38848137 to track.

Hi @cwilhit, I took a quick look now, but it doesn't seem to be the same issue. As mentioned, I could not reproduce the issue outside the container.  Also the message from the nslookup when it times out is:
DNS request timed out.
    timeout was 2 seconds.
Name:    google.com
Address:  2a00:1450:400d:80d::200e

Server:  dns.google
Address:  <IP_ADDRESS>

@haiduc32 : Can you please try Resolve-DNSName instead of nslookup? Let me know if u see the same issue.

Any update on this? I'm having a similar issue running IIS containers on Azure VMSS hosted in Service Fabric. Sometimes especially after high load, the outbound connections from the containers will intermittently time out for whatever reason. Restarting the containers doesn't fix it. Only thing that fixes it is restarting the host VM.

If you hit the issue in Azure VM/VMSS, please reference the mitigation in https://github.com/Azure/AKS/issues/2988

@haiduc32 : Can you please try Resolve-DNSName instead of nslookup? Let me know if u see the same issue.
@haiduc32 were you able to see the same issue after trying Resolve-DNSName?

If you hit the issue in Azure VM/VMSS, please reference the mitigation in Azure/AKS#2988
Abel also referenced a mitigation if you see this issue in Azure VM/VMSS.

Fixed it for our use case by setting --dns flag explicitly when a container is getting run e.g. docker run --dns <IP_ADDRESS>.

Fixed it for our use case by setting --dns flag explicitly when a container is getting run e.g. docker run --dns <IP_ADDRESS>.

I guess that the dns issue occurs when policies for dns are being updated (deleted and added) so adding a static dns  could fix this issue.

@cwilhit any updates here?


any time src/ files change, how do we run a build and also commit dist/?

Description
Related to:

https://github.com/lint-staged/lint-staged/issues/1346

Is the question in the title even possible? Or is the design of lint-staged limited and it is not possible?
If it is possible, is there an example somewhere I can take a look at?

Closing this as duplicate of the linked issue

Lint-staged is currently built to run only on the files originally staged for the commit. Any new files created by the task would have to be manually staged.
Maybe you can reduce concurrency to 1 to avoid git race conditions and run git add for the build files.


Preparing for new release to test new pipeline.

Let's see how it goes.

Codecov Report

Merging #96 (8cb801d) into main (8d88fca) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #96   +/-   ##
=======================================
  Coverage   86.39%   86.39%
=======================================
  Files          77       77
  Lines        3264     3264
=======================================
  Hits         2820     2820
  Misses        444      444

Flag
Coverage Δ

unittests
86.39% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


fix: eslint warnings for object type defs

This PR fixes the ESlint warnings for JSDoc type checking (issue #509). All the 25 warnings have been fixed 🎉
For the Iterable type warning problem, this was fixed based on github issue help
JIRA

Looking great, thanks for doing this! I just have one change I didn't spot the first time around. Because this is a fix: level commit this will cause new releases to be tagged up for all packages, however there's no actual benefit to end-users of Reliability Kit, nothing changes about the way they use the packages.
For this reason I think all the commits should be chore:-level, which is more appropriate if we're doing internal tidying with no actual impact. Does that make sense?

Yeah this makes total sense, no point to cause unnecessary bumps. Let me rebase and change the commit message of the commits 😌


Multipage support

I'm learning Marko, I come from Pug and NunJucks. But I do not get a multipage output configuration.
It's possible?
And it would be great if I could inject the dependencies css and javascript as does html-webpack-plugin but for each page.
Thanks,
Nice work!

Marko is only a loader, both of the things you mention are handled by Webpack and work just like any other webpack build. You can use html-webpack-plugin and you can do multi-page entries. :)

I asked this same question and it looks like you can get multipage support by configuring your project like the Marko+Webpack sample repo, with each page inside the /pages/ folder.


Linking of rule '//tensorflow/contrib/factorization:gen_gen_clustering_ops_py_wrappers_cc' failed (missing -lcuda?)

Trying to build Tensorflow from a6f856b2f7920d4f74d7ca4e71967258423cc9f0 with CUDA and just started running into this issue:
____[7,182 / 7,674] Compiling tensorflow/core/graph/node_builder.cc
____[7,183 / 7,675] Compiling tensorflow/core/graph/costmodel.cc
____[7,245 / 7,715] Linking tensorflow/contrib/factorization/gen_gen_clustering_ops_py_wrappers_cc [for host]
____[7,246 / 7,715] Linking tensorflow/contrib/tensor_forest/hybrid/gen_training_ops_py_wrappers_cc [for host]
____[7,247 / 7,715] Linking tensorflow/cc/ops/lookup_ops_gen_cc [for host]
____[7,248 / 7,715] Linking tensorflow/contrib/tensor_forest/gen_gen_model_ops_py_py_wrappers_cc [for host]
____[7,249 / 7,715] Linking tensorflow/contrib/tensor_forest/gen_gen_tensor_forest_ops_py_wrappers_cc [for host]
____[7,250 / 7,715] Linking tensorflow/python/gen_set_ops_py_wrappers_cc [for host]
____[7,251 / 7,715] Linking tensorflow/python/gen_linalg_ops_py_wrappers_cc [for host]
ERROR: /build/tensorflow-git/src/tensorflow-cuda/tensorflow/contrib/factorization/BUILD:106:1: Linking of rule '//tensorflow/contrib/factorization:gen_gen_clustering_ops_py_wrappers_cc' failed (Exit 1).
/usr/bin/ld: warning: libcuda.so.1, needed by bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so, not found (try using -rpath or -rpath-link)
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemFree_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemsetD32Async'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuEventCreate'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuStreamAddCallback'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuModuleLoadFatBinary'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuCtxEnablePeerAccess'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemGetInfo_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuLaunchKernel'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuStreamSynchronize'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuEventQuery'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuEventElapsedTime'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDeviceCanAccessPeer'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuCtxSynchronize'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDeviceGetAttribute'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuFuncGetAttribute'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemcpyDtoH_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuStreamQuery'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDevicePrimaryCtxGetState'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuCtxSetCurrent'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuStreamWaitEvent'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuEventSynchronize'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuModuleUnload'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDeviceGet'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemsetD32_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuCtxGetSharedMemConfig'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemFreeHost'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuFuncSetCacheConfig'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuStreamCreate'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemGetAddressRange_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuCtxGetDevice'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDeviceGetProperties'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemcpyDtoHAsync_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDeviceGetCount'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuModuleGetFunction'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemHostRegister_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDevicePrimaryCtxRelease'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemcpyHtoDAsync_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemcpyDtoD_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuModuleLoadDataEx'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDevicePrimaryCtxRetain'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemHostAlloc'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuInit'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDriverGetVersion'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDeviceGetPCIBusId'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuEventRecord'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuPointerGetAttribute'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDeviceTotalMem_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemsetD8_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDeviceComputeCapability'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemAlloc_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDeviceGetName'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuDevicePrimaryCtxSetFlags'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemHostUnregister'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuModuleGetGlobal_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemcpyDtoDAsync_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuEventDestroy_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuOccupancyMaxActiveBlocksPerMultiprocessor'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuCtxGetCurrent'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuStreamDestroy_v2'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuCtxSetSharedMemConfig'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemsetD8Async'
bazel-out/host/bin/_solib_local/_U_S_Stensorflow_Scontrib_Sfactorization_Cgen_Ugen_Uclustering_Uops_Upy_Uwrappers_Ucc___Utensorflow/libtensorflow_framework.so: undefined reference to `cuMemcpyHtoD_v2'
collect2: error: ld returned 1 exit status
____Building complete.
____Elapsed time: 1247.002s, Critical Path: 405.23s

My previous successful build (I haven't tried revisions in between) was from abfc9deb7. My build environment hasn't changed significantly since then (no compiler, CUDA, or relevant library changes). I suspect it must be a recent change in the Tensorflow repo that's the cause.
The only difference I see between abfc9deb7 and a6f856b2f7920d4f74d7ca4e71967258423cc9f0  in the tensorflow/contrib/factorization path is this:
diff --git a/tensorflow/contrib/factorization/kernels/BUILD b/tensorflow/contrib/factorization/kernels/BUILD
index 9a6d3c6f5..44eab5601 100644
--- a/tensorflow/contrib/factorization/kernels/BUILD
+++ b/tensorflow/contrib/factorization/kernels/BUILD
@@ -6,6 +6,8 @@ exports_files(["LICENSE"])

 package(default_visibility = ["//tensorflow:__subpackages__"])

+load("//tensorflow:tensorflow.bzl", "tf_cc_test")
+
 cc_library(
     name = "all_kernels",
     deps = [
@@ -50,7 +52,7 @@ cc_library(
     alwayslink = 1,
 )

-cc_test(
+tf_cc_test(
     name = "clustering_ops_test",
     srcs = ["clustering_ops_test.cc"],
     deps = [

I'm not super familiar with how Bazel works, but this looks innocuous to me. I guess something else must be implicated?
Any idea what could cause it to not add -lcuda on the link line? Or perhaps why it didn't need to before but does now?
$ pacman -Q | grep -e gcc-mult -e ^cuda -e ^glibc -e ^cudnn -e ^gcc5 -e '^python ' -e bazel
bazel 0.5.4-1
cuda 8.0.61-3
cudnn6 6.0.21-2
gcc-multilib <IP_ADDRESS>70910-1
gcc5 5.4.0-1
glibc 2.26-3
python 3.6.2-1

Not sure how, but could be a result of https://github.com/tensorflow/tensorflow/pull/13224/commits/5c7f9e316d8c7735308a217310350d416d7498cc
I'll take a look.

Yeah, seems related. You can work around the issue with --config=monolithic while I figure out how to fix it.

Just checked, adding --config=monolithic does work. My non-chroot build didn't need that though, presumably because of previous build artifacts sitting in the bazel cache?

Looks like it might be a Bazel linking bug. Building the pip package (bazel build --config=cuda //tensorflow/tools/pip_package:build_pip_package) works, and the resulting pip package has contrib/factorization/python/ops/gen_clustering_ops.py. But building this rule explicitly (bazel build //tensorflow/contrib/factorization:gen_gen_clustering_ops_py_wrappers_cc) messes up the dependence of libtensorflow_framework.so on CUDA libraries (the rpaths are wrong).
I'm tempted to just add something like "-Wl,-rpath,/usr/local/cuda/lib64" until this gets fixed...

Another workaround is to use --action_env=LD_LIBRARY_PATH=/usr/local/cuda/lib64 (or your CUDA installation directory).

I think we're only seeing this on chroot environments because they're missing CUDA drivers (the linker complains about a missing libcuda.so).
I think the following is a better solution than LD_LIBRARY_PATH:
echo "/usr/local/cuda-8.0/targets/x86_64-linux/lib/stubs" > /etc/ld.so.conf.d/cuda-8.0-stubs.conf
ldconfig

It has been 14 days with no activity and this issue has an assignee.Please update the label and/or status accordingly.

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @allenlavoie: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @allenlavoie: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @allenlavoie: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @allenlavoie: It has been 46 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

add --action_env=LD_LIBRARY_PATH=/path/to/cuda/lib64 still got the error.
What does --config=monolithic mean ? What's the difference without this config ?

Does symlinking in /usr/local/cuda and using --action_env help? I needed to do both.
For monolithic see https://github.com/tensorflow/tensorflow/blob/694892d4c0fba6bd4322e943f8b1483b36f1ae99/tools/bazel.rc#L19 and https://github.com/tensorflow/tensorflow/blob/694892d4c0fba6bd4322e943f8b1483b36f1ae99/tensorflow/BUILD#L423
(FYI this is still blocked on the Bazel bug)

I'm able to reproduce this error on 1.8, I include --action_env, and I've made sure libcuda.so and a symlink for libcuda.so.1 are on the path.

Nagging Assignee @allenlavoie: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @allenlavoie: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @allenlavoie: It has been 44 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @allenlavoie: It has been 59 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @allenlavoie: It has been 76 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @allenlavoie: It has been 92 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Yeah I'm still seeing this bug. Symlinking and adding location of libcuda.so (and symlinked libcuda.so.1) to LD_LIBRARY_PATH isn't helping.

Nagging Assignee @allenlavoie: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @allenlavoie: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

This issue still exist in TF-1.11

I'm seeing similar issue on 1.12-rc1, goes away when doing a monolithic build

This and the similar issue with cublas (https://stackoverflow.com/questions/47080760/tensorflow-fails-to-compile) cost me a bunch of time yesterday. It would be nice to get this fixed by default.

Recently I compiled tensorflow 1.10 from source using gcc 5.4, I have collected some errors may occurred:
https://gist.github.com/HawkAaron/575fc12e6598a7a5f93423ee9677847f
Hope this can help you.

This issue exists on tf1.10.1 with bazel 0.18. I haven't gotten an error so far with --config=monolithic.

Nagging Assignee @allenlavoie: It has been 17 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @allenlavoie: It has been 31 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Hi @tycho !
It seems you are using older versions(1.x versions) of Tensorflow. We recommend that you upgrade  your code base to 2.x  versions as many features and bug fixes has been done in newer versions and let us know if the issue still persists in newer versions. Thanks!

I'd forgotten this issue even existed. Closing.