[SPARK-17812][SQL][KAFKA] Assign and specific startingOffsets for structured stream

What changes were proposed in this pull request?
startingOffsets takes specific per-topicpartition offsets as a json argument, usable with any consumer strategy
assign with specific topicpartitions as a consumer strategy
How was this patch tested?
Unit tests

Test build #67025 has started for PR 15504 at commit 2e53e5a.

Test build #67025 has finished for PR 15504 at commit 2e53e5a.

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

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

Merged build finished. Test PASSed.

Test build #67026 has started for PR 15504 at commit 5e4511f.

Test build #67026 has finished for PR 15504 at commit 5e4511f.

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

Merged build finished. Test PASSed.

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

Test build #67288 has started for PR 15504 at commit c72562e.

Test build #67288 has finished for PR 15504 at commit c72562e.

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

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

Merged build finished. Test PASSed.

Test build #3368 has started for PR 15504 at commit c188461.

Test build #3368 has finished for PR 15504 at commit c188461.

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

Test build #3369 has started for PR 15504 at commit c188461.

Test build #3369 has finished for PR 15504 at commit c188461.

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

LGTM. Merging to master and 2.0. Thanks!


Rewrite multi-GPU documentation

Closes #1860. The changes to the document are quite in-depth and there is new added info, so this PR needs to be fact-checked aside of proofreading.
The resulting compiled document looks as intended.
Overview of the changes

The document was generally rewritten to be better laid out and is significantly more detailed.
DP is explicitly recommended against and is noted as deprecated, which seems to be the general stance of SB core contributors. (I made it go as far as saying SB does not support it anymore, considering we generally always tell DP users to use DDP instead when they face DP-related bugs)
I tried to make the phrasing much more explicit in what DDP enables and how multi-GPU training works.
"Writing DDP-safe code" gets its own, more detailed subsection.

Additional notes
The Colab tutorial (which was brought up in the issue here) is not linked in the document as of this PR. It should probably be updated to the contents of this PR, but as unless it actually gets any different content from the documentation, it probably doesn't need to be linked from the docs.
@anautsch (in DMs) mentioned DDP tests and some changes from #1817 that indirectly affect DDP. This PR mentions neither at the time, but perhaps someone more qualified than me could enhance the DDP-safety subsection further.

Ugh, pre-commit checks fail to intended trailing whitespaces in the markdown. I'll remove them for now.

Thanks @AsuMagic!


Rename .cargo/config to .cargo/config.toml

Fixes a deprecation warning.

Ok, looks like cargo xbuild (which we still use in this branch for some reason) doesn't support .cargo/config.toml files. So this PR doesn't work.


Translate special strings

Some strings can't be translated using a normal strings file because they include React components.
For example:

Are you sure you want to delete {this.props.name} file?

Figure out what is the best way to translate these. Splitting the string does not really work because the order in another language may differ.

The translation function now accepts react components:

{t('Are you sure you want to delete {name} file?', {name: {this.props.name}})}


Multimonitor i3 module icon bug

Describe the issue
When using polybar with multiple monitors with the i3 window manager (and using i3 module), when the focus goes to a different monitor, the workspace that is active on another monitor (not the one in focus) displays both the icon and the workspace name.
Expected behavior:
When going to another monitor, the icons should retain 'unfocused' mode.
Actual behavior:
The Polybar icon on the other monitor seems to go into a fifth unconfigured state, as it loses all padding configuration and does not respect the settings of mode, focused, unfocused, or urgent.
Was it working before?
No

Did you also experience this bug in an earlier version of polybar?
N/A

To Reproduce
A minimal but complete config with which the problem occurs:
[colors]
;background = ${xrdb:color0:#222}
background = #99282a36
background-alt = #282a36
;foreground = ${xrdb:color7:#222}
foreground = #f8f8f2
foreground-alt = #f8f8f2
primary = #ffb52a
secondary = #e60053
alert = #bd2c40
underline = #b070f9

[bar/example]
monitor = ${env:MONITOR:}
width = 100%
height = 35
;offset-x = 1%
;offset-y = 1%
radius = 0
fixed-center = true

background = ${colors.background}
foreground = ${colors.foreground}

line-size = 3
line-color = #f00

border-size = 0
border-color = #00000000

padding-left = 0
padding-right = 2

module-margin-left = 0
module-margin-right = 4

font-0 = "Noto Sans Display:size=12;3"
font-1 = "Font Awesome 5 Free:style=Solid:pixelsize=10;3"
font-2 = "Font Awesome 5 Free:style=Regular:pixelsize=10;3"
font-3 = "Font Awesome 5 Brands:pixelsize=10;3"

; removed modules for succinctness
modules-left =
modules-center = i3
modules-right =

[module/i3]
type = internal/i3
format = <label-state>
pin-workspaces = true
strip-wsnumbers = true
index-sort = true
enable-scroll = false

ws-icon-0 = 1;
ws-icon-1 = 2;
ws-icon-2 = 3;
ws-icon-3 = 4;
ws-icon-4 = 5;5
ws-icon-5 = 6;6
ws-icon-6 = 7;7
ws-icon-7 = 8;
ws-icon-8 = 9;
ws-icon-9 = 10;

label-mode = %icon%
label-mode-padding = 2
label-mode-foreground = #000
label-mode-background = ${colors.primary}
;label-focused-foreground = ${colors.underline}

label-focused = %icon%
label-focused-padding = 2
;label-focused-underline = #ff79c6
label-focused-background = #ff79c6

label-unfocused = %icon%
label-unfocused-padding = 2
label-unfocused-foreground = #ffffff

label-urgent = %icon%
label-urgent-padding = 2
label-urgent-foreground = #FF5555

List any other steps needed to reproduce the issue besides starting polybar with the config you posted above.
Use the following polybar script to launch it on two monitors:
#!/usr/bin/env bash

# Terminate already running bar instances
killall -q polybar

# Wait until the processes have been shut down
while pgrep -u $UID -x polybar >/dev/null; do sleep 1; done

if type "xrandr"; then
  for m in $(xrandr --query | grep " connected" | cut -d" " -f1); do
    MONITOR=$m polybar --reload example &
  done
else
  polybar --reload example &
fi

Polybar Log
Post everything polybar outputs to the terminal when you run it and the issue occurs below
.config/polybar/launch.sh
xrandr is /usr/bin/xrandr
error: Disabling module "bspwm" (reason: Could not find socket: /tmp/bspwm_1_0-socket)
error: Disabling module "bspwm" (reason: Could not find socket: /tmp/bspwm_1_0-socket)
warn: pulseaudio: using default sink alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.iec958-stereo
warn: pulseaudio: using default sink alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.iec958-stereo
error: Disabling module "battery" (reason: No suitable way to get current charge state)
error: Disabling module "battery" (reason: No suitable way to get current charge state)
error: tray: Failed to put tray above 0x0800002 in the stack (XCB_MATCH (8))
error: tray: Failed to put tray above 0x0a00002 in the stack (XCB_MATCH (8))
warn: Systray selection already managed (window=0x0800006)
warn: Dropping unmatched character  (U+e19c)
warn: Dropping unmatched character  (U+e0ca)
warn: Dropping unmatched character  (U+e19c)
warn: Dropping unmatched character  (U+e0ca)
warn: Dropping unmatched character  (U+e19c)
warn: Dropping unmatched character  (U+e0ca)
warn: Dropping unmatched character ⛅ (U+26c5)
warn: Dropping unmatched character  (U+fe0f)
warn: Dropping unmatched character  (U+e19c)
warn: Dropping unmatched character  (U+e0ca)
... just a bunch of unmatched characters

Screenshots
If applicable, add screenshots to help explain your problem.
https://imgur.com/a/OOKgLeX
Environment:

WM: i3-gaps
Distro: Arch
Output of polybar -vvv:

polybar 3.3.1

Features: +alsa +curl +i3 -mpd +network(libnl) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) -render -damage -sync +composite +xkb +xrm +xcursor

Build type: RelWithDebInfo
Compiler: /usr/bin/c++
Compiler flags:  -Wall -Wextra -Werror -Wno-noexcept-type -pedantic -pedantic-errors
Linker flags:

Additional context
Add any other context that you think is necessary about the problem here.
It SEEMS that the problem is that there is a weird edge case where on a different monitor, the icon does not go into any of the states that it is meant to go to, and instead goes into a fifth weird state that is not configurable.

When your workspace doesn't have the focus and is visible on your other screen, polybar uses the label-visible rather than the label-unfocused.
In pseudo-code:
if (workspace_has_focus) {
  state = FOCUSED;
} else if (workspace_has_urgent_flag) {
  state = URGENT;
} else if (workspace_is_visible) {
  state = VISIBLE;
} else {
  state = UNFOCUSED;
}

You're exactly right. Not sure if I missed this in the documentation somewhere but thank you for pointing it out. Issue resolved.


support auth for rancher/agent during upgrade

Rancher 1.6 doesn't support upgrading rancher/agent if it requires auth.
Steps to reproduce:

launch rancher server by specifying rancher/agent to a auth-required repo
rancher/agent stuck at upgrading saying auth required.

Expected:

successfully upgrade.

This won't be supported natively, but you can set up your private registry and pre-pull these images with these steps:
https://rancher.com/docs/rancher/v1.6/en/upgrading/#upgrading-rancher-when-using-private-registry-with-authentication


Generate View does not add Connection to Connections

Version of Archi, Operating System

Archi 4.0.2. All OS.
Expected Behaviour

When selecting "Generate View For..." an element that connects to other elements via a connection to connection, all elements should be added.
Actual Behaviour

Some elements are missing.
Steps to Reproduce the Behaviour
See http://forum.archimatetool.com/index.php?topic=415.0

Created branch:
https://github.com/archimatetool/archi/tree/generate_view_fix
Started a fix. If anyone would like to contribute the full fix please do so...

Fixed for next release


[excel] (PivotTable) Adding ManualFilter samples for PivotTables

Docs Build status updates of commit a9df560:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/docs-ref-autogen/excel/excelscript/excelscript.pivotfilters.yml
:white_check_mark:Succeeded
View (office-scripts)

docs/docs-ref-autogen/excel/excelscript/excelscript.pivotmanualfilter.yml
:white_check_mark:Succeeded
View (office-scripts)

docs/docs-ref-autogen/excel/excelscript/excelscript.pivottable.yml
:white_check_mark:Succeeded
View (office-scripts)

docs/sample-scripts/excel-scripts.yaml
:white_check_mark:Succeeded

generate-docs/json/excel/snippets.yaml
:white_check_mark:Succeeded

generate-docs/tools/API Coverage Report.csv
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Merging based on @peronald's offline approval.


Week number ticks

The ISO week numbers are not right when trying to display them on the x-axis using tickformat.
var parseDate = d3.time.format("%Y%W").parse;
var x = d3.time.scale().range([0, width]);
x.domain([parseDate(from_year_week), parseDate(to_year_week)]);

var xAxis = d3.svg.axis().scale(x)
        .orient("bottom")
        .ticks(d3.time.monday,1)
        .tickFormat(d3.time.format("%Y"))

This works fine with most of the scenario except when year has 53 weeks.
example: from week 201552 to week 201602. In this scenario it always skips week 53 so the the tick I get are [52, 01, 02]. although the expected output is [52,53,01,02]
Here is a piece of the code demonstrating the issue.

The %W directive used by d3-time-format is not the ISO week date; it is the zero-based Monday-of-year in [00, 53]. This means that the first Monday in any given year is always number 1; any date prior to this first Monday in the same year is 0.
For example:

201500 is Monday, December 29, 2014.
201501 is Monday, January 5, 2015.
201552 and 201600 is Monday, December 28, 2015.
201553 and 201601 is Monday, January 4, 2016.

The ISO week date has a much more complicated definition of the first week. D3 has no support for parsing ISO week dates, so you may need to use another library or another representation in order to parse them.


Feedback v0.17.0

job结束后 stdout和stderr 点开都提示 not found是怎么回事？谢谢

it may because the container didn't produce any output. or the output is too short that the container exits w/o flushing the output to the disk.

根据您的分析，我增加输出肯定超过40k bytes，但依然是 Not Found。另外“Go to Application Tracking Page” 点击后也报{"message":"Page not found","error":{}}，盼回复，谢谢。
------------------ 原始邮件 ------------------
发件人:                                                                                "microsoft/pai"<EMAIL_ADDRESS>发送时间: 2020年7月21日(星期二) 晚上9:45
收件人<EMAIL_ADDRESS>抄送: "甲骨文"<825223581<EMAIL_ADDRESS>主题: Re: [microsoft/pai] Feedback v0.17.0 (#4754)
it may because the container didn't produce any output. or the output is too short that the container exits w/o flushing the output to the disk.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Are you deploying YARN in v0.17? YARN is not supported in v0.17. Please do not use v0.17 as it is an internal version. Please use v1.x.

https://github.com/microsoft/pai/issues/4675

找到原因了，谢谢。
------------------ 原始邮件 ------------------
发件人:                                                                                "microsoft/pai"<EMAIL_ADDRESS>发送时间: 2020年7月21日(星期二) 晚上10:25
收件人<EMAIL_ADDRESS>抄送: "甲骨文"<825223581<EMAIL_ADDRESS>主题: Re: [microsoft/pai] Feedback v0.17.0 (#4754)
Are you deploying YARN in v0.17? YARN is not supported in v0.17. Please do not use v0.17 as it is an internal version. Please use v1.x.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

job结束后 stdout和stderr 点开都提示 not found是怎么回事？谢谢

Hi @ypbustc thanks for following openpai and interact with us. would you mind share more info about what's the major usage for you when considering openPAI for yourself or your organization. if you don't mind, would you please share the org name? so that we can clustering issues together by org names.

job结束后 stdout和stderr 点开都提示 not found是怎么回事？谢谢

Hi @ypbustc thanks for following openpai and interact with us. would you mind share more info about what's the major usage for you when considering openPAI for yourself or your organization. if you don't mind, would you please share the org name? so that we can clustering issues together by org names.

Closing the issue as the problem has been addressed according to the comment history. But looking forward for feedback on the Org info and usage scenario sharing. thanks.

USTC ，openPAI主要用于管理AI集群。
------------------ 原始邮件 ------------------
发件人:                                                                                "microsoft/pai"<EMAIL_ADDRESS>发送时间: 2020年7月22日(星期三) 下午2:45
收件人<EMAIL_ADDRESS>抄送: "甲骨文"<825223581<EMAIL_ADDRESS>主题: Re: [microsoft/pai] Feedback v0.17.0 (#4754)
job结束后 stdout和stderr 点开都提示 not found是怎么回事？谢谢
Hi @ypbustc thanks for following openpai and interact with us. would you mind share more info about what's the major usage for you when considering openPAI for yourself or your organization. if you don't mind, would you please share the org name? so that we can clustering issues together by org names.
Closing the issue as the problem has been addressed according to the comment history. But looking forward for feedback on the Org info and usage scenario sharing. thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

USTC ，openPAI主要用于管理AI集群。
…
------------------ 原始邮件 ------------------ 发件人: "microsoft/pai"<EMAIL_ADDRESS>发送时间: 2020年7月22日(星期三) 下午2:45 收件人<EMAIL_ADDRESS>抄送: "甲骨文"<825223581<EMAIL_ADDRESS>主题: Re: [microsoft/pai] Feedback v0.17.0 (#4754) job结束后 stdout和stderr 点开都提示 not found是怎么回事？谢谢 Hi @ypbustc thanks for following openpai and interact with us. would you mind share more info about what's the major usage for you when considering openPAI for yourself or your organization. if you don't mind, would you please share the org name? so that we can clustering issues together by org names. Closing the issue as the problem has been addressed according to the comment history. But looking forward for feedback on the Org info and usage scenario sharing. thanks. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

收到，是BITA的deploy还是新的Deploy?如果是BITA的我就重用之前的tag了。@ypbustc

是新的集群，不是bita。
------------------ 原始邮件 ------------------
发件人: "Scarlett<EMAIL_ADDRESS>发送时间: 2020年7月22日(星期三) 下午2:58
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [microsoft/pai] Feedback v0.17.0 (#4754)
USTC ，openPAI主要用于管理AI集群。
…
------------------ 原始邮件 ------------------ 发件人: "microsoft/pai"<EMAIL_ADDRESS>发送时间: 2020年7月22日(星期三) 下午2:45 收件人<EMAIL_ADDRESS>抄送: "甲骨文"<825223581<EMAIL_ADDRESS>主题: Re: [microsoft/pai] Feedback v0.17.0 (#4754) job结束后 stdout和stderr 点开都提示 not found是怎么回事？谢谢 Hi @ypbustc thanks for following openpai and interact with us. would you mind share more info about what's the major usage for you when considering openPAI for yourself or your organization. if you don't mind, would you please share the org name? so that we can clustering issues together by org names. Closing the issue as the problem has been addressed according to the comment history. But looking forward for feedback on the Org info and usage scenario sharing. thanks. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
收到，是BITA的deploy还是新的Deploy?如果是BITA的我就重用之前的tag了。@ypbustc
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


increase t_end for rico

Purpose

Increases t_end to 8 hours for rico. Also allows enthalpy to be negative in plotting.
To-do

Content

[ ] I have read and checked the items on the review checklist.

bors r+


Assign the enums to toplevel globals to make it easier to use

e.g.
class SendMode(Enum):
    PUBLISH = auto()
    ROUNDROBIN = auto()

PUBLISH = SendMode.PUBLISH
ROUNDROBIN = SendMode.ROUNDROBIN

In hindsight, I think this would add complexity. I think it's simpler to just use the enums directly.  Closing.


ENH/FIX: allow for reject API  that is more consistent with MNE C

In MNE-C it is possible to specify epoching parameters using a config file like this:
average {
outfile __OUTFILE__
eventfile __EVEFILE__
logfile __LOGFILE__
grdReject 200e-12
magReject 4e-12
eegReject -1
eogReject -1
emgReject -1
name "WordOnsets"

category {
name "VerbNP"
event 71
tmin -0.3
tmax 1.2
}
}

MNE-Python new comers might be tempted to construct a reject dict like this:

reject = dict(mag=4e-12, grad=200e-12, eog=-1, ecg=-1)

# or

reject = dict(mag=4e-12, grad=200e-12, eog=None, ecg=None)

Which can / will lead to unexpected results, e.g. in Python comparisons None is always smaller than any numerical value ...
I would suggest to either allow for the MNE C style API or throw nice + concise errors once values like -1 or None are passed.
cc @agramfort @Eric89GXL
Thanks to @bmaess to bringing this to my awareness

any action needed here?
do we allow reject keys for absent channels?

Moving to 0.10, haven't heard responses or found volunteer


Add text converting to Hexadecimal Converter page

Adds an input box for converting from/to text on the Hexadecimal Converter page, so you can easily convert e.g. bytes32 to text

Thank you for this awesome tool! :rocket:

@apoorvlathey Hello! It seems to me that you are the main contributor, could you take a look at this please?

Hey, thanks for the contribution. I'll check it out

Hey @matejos what's your Base/Optimism/Arbitrum address? I'm rewarding the contributors with some ETH.
Here's the post: https://x.com/apoorvlathey/status/1791475159054127184

Hey there, thank you very much! Just sent you a DM on X :relaxed:


Investigate CI failure and add CI with ocaml/setup-ocaml@v2

File "melange/kxclib.ml", lines 1320-1363, characters 10-13:
1320 | ..........struct
1321 |             let impl_flavor = `float_impl
1322 |             let (to_int, of_int) =
1323 |               match Sys.backend_type with
1324 |               | Other "js_of_ocaml" | Other "BS" -> (Obj.magic, Obj.magic)
...
1360 |             let to_nativeint = let open Int64 in to_nativeint % of_float
1361 |             let of_nativeint = let open Int64 in to_float % of_nativeint
1362 |             let of_string = float_of_string
1363 |           end.
Error: Signature mismatch:
       ...
       Values do not match:
         val to_string : ?radix:int -> int53p -> string
       is not included in
         val to_string : int53p -> string
       The type ?radix:int -> int53p -> string
       is not compatible with the type int53p -> string
       File "melange/kxclib.ml", line 1275, characters 8-40:
         Expected declaration
       File "melange/kxclib.ml", line 1349, characters [20](https://github.com/kxcinc/kxclib-ocaml/actions/runs/8167179599/job/22327162739#step:8:21)-29:
         Actual declaration
Error: Process completed with exit code 1.

Explicitly define to_string as a function so that the optional argument Float.to_string is not used by the environment.

Another error occured
File "melange/kxclib_js.ml", line 62, characters 48-62:
62 |       | `arr arr -> arr |. Belt.List.toArray |. Belt.Array.map to_json |> Js.Json.array
                                                     ^^^^^^^^^^^^^^
Error: Unbound module Belt

install melange              3.0.0-51

https://github.com/kxcinc/komo/pull/85


Zap update repo6

Problem
This PR updates ZAP as the master branch contains some fixes needed for #9725
Change overview

Update ZAP
Regenerate the code

/rebase


Add column_types

We're currently processing your upload.  This comment will be updated when the results are available.


Retire \transn

Better use the CSS hack below or #5:
.mjx-mn > .mfliph.mar > .mjx-char {
    direction: ltr;
}

Anyway, this will probably break v2 and probably require another version.

This is interesting. Maybe I'm misunderstanding, but how will you be able to know if the comma separated numbers are a single number vs. a list of numbers? E.g.:
(1,234) --> a coordinate on a graph, two numbers
1,234 --> a single number with a comma in the thousands place
Don't we still need \transn to be able to tell arabic-mathjax that first case should be rendered as:

but the second case should be rendered as:

That's great question @barillax! I don't have an answer for it now. Perhaps we should just keep the current setup as-is.
This issue remains open, for the moment, but based on your comment, it'll likely be closed soon.


How to use it as a DaemonSet with hostNetwork? - bug in chart ?

Hi,
I'm trying to figure out how to use haproxy-ingress as a DaemonSet with hostNetwork so it listens on 80 and 443 on all my nodes.
I have the following config:
    controller:
      hostNetwork: true
      kind: DaemonSet
      daemonset:
        useHostPort: true
      config:
        use-proxy-protocol: "true"

And I get a LoadBalancer type service listening on high ports.
 k get svc
NAME              TYPE           CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
haproxy-ingress   LoadBalancer   <IP_ADDRESS>   <pending>     80:31738/TCP,443:30543/TCP   13m

So, it does listen to host network after all.
However I remember the load balancer part should be fixable as well.

Hi, regarding the services, they are always created by default but shouldn't hurt. I've some more deployment docs in the backlog, writing them should lead to some chart improvements - eg create a lb service only if needed.
The config you provided should be enough to run HAProxy Ingress as a DaemonSet and using the host network. HAProxy itself should bind 80/443 ports using all the host IPs and you should reach it using the host IP. Please provide a few more details of your deployment, netstat -pltn of a node that runs HAProxy Ingress, and so on.

Thanks,
It does work, I managed to configure it with cert-manager.
Here are the details, I hope they are useful.
root@w001:~# netstat -pltn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:37107         <IP_ADDRESS>:*               LISTEN      21494/k3s agent
tcp        0      0 <IP_ADDRESS>:53           <IP_ADDRESS>:*               LISTEN      438/systemd-resolve
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*               LISTEN      540/sshd: /usr/sbin
tcp        0      0 <IP_ADDRESS>:31738           <IP_ADDRESS>:*               LISTEN      21494/k3s agent
tcp        0      0 <IP_ADDRESS>:10010         <IP_ADDRESS>:*               LISTEN      21511/containerd
tcp        0      0 <IP_ADDRESS>:443             <IP_ADDRESS>:*               LISTEN      84464/haproxy
tcp        0      0 <IP_ADDRESS>:514             <IP_ADDRESS>:*               LISTEN      79718/syslog-ng
tcp        0      0 <IP_ADDRESS>:10248         <IP_ADDRESS>:*               LISTEN      21494/k3s agent
tcp        0      0 <IP_ADDRESS>:10249         <IP_ADDRESS>:*               LISTEN      21494/k3s agent
tcp        0      0 <IP_ADDRESS>:9100          <IP_ADDRESS>:*               LISTEN      902/node_exporter
tcp        0      0 <IP_ADDRESS>:10253           <IP_ADDRESS>:*               LISTEN      84464/haproxy
tcp        0      0 <IP_ADDRESS>:30543           <IP_ADDRESS>:*               LISTEN      21494/k3s agent
tcp        0      0 <IP_ADDRESS>:1936            <IP_ADDRESS>:*               LISTEN      84464/haproxy
tcp        0      0 <IP_ADDRESS>:80              <IP_ADDRESS>:*               LISTEN      84464/haproxy
tcp        0      0 <IP_ADDRESS>:10256         <IP_ADDRESS>:*               LISTEN      21494/k3s agent
tcp6       0      0 :::32086                :::*                    LISTEN      21494/k3s agent
tcp6       0      0 :::22                   :::*                    LISTEN      540/sshd: /usr/sbin
tcp6       0      0 :::10250                :::*                    LISTEN      21494/k3s agent
tcp6       0      0 :::10254                :::*                    LISTEN      79638/haproxy-ingre


buildPerlPackage: phase out "name"

Some time ago perlPackages.* have been refactored to use buildPerlPackage with pname and version instead of name
and a warning was printed when it was used with name to prompt users fix their code.
As time passed, now the warning is being replaced with a fatal error and the support for name is removed.
PS. rebuild is not expected

I believe there was throw in stdenv.mkDerivation that did the same thing and it was reverted.
I think having the builder functions inconsistent like this would be confusing to users, for example every buildPythonPackage pretty much uses pname but it doesn't throw for name.
I think the warning is good if it only affects external expressions.

I believe there was throw in stdenv.mkDerivation that did the same thing and it was reverted.

I think stdenv.mkDerivation should print a warning right now (and maybe throw next year).
The name -> pname migration is stalled, up to new PRs get with name (well, I make them too, in the absence of warning it is easy to forget after years of using name)
The migration is important for various lang2nix and repology (https://github.com/NixOS/nixpkgs/issues/61691) because name is tricky to split to package name and version.

I believe there was throw in stdenv.mkDerivation that did the same thing and it was reverted.

I think stdenv.mkDerivation should print a warning right now (and maybe throw next year).
The name -> pname migration is stalled, up to new PRs get with name (well, I make them too, in the absence of warning it is easy to forget after years of using name)
The migration is important for various lang2nix and repology (#61691) because name is tricky to split to package name and version.

Indeed all of this is true, and we'll clearly benefit from having pname and version everywhere.
So perhaps just a warning in stdenv.mkDerivation should be discussed?

So perhaps just a warning in stdenv.mkDerivation should be discussed?

Yes.
Replacing warning with throw is to be postponed till 20.03 or 20.09

Oh, a warning in stdenv.mkDerivation emits a lot of false positives
(so I doubt there has been a PR proposing throw in stdenv.mkDerivation)
warning: stdenv.mkDerivation:
  name = "d851fada460d42508a6f82b19867f63853062583.patch"
is deprecated, please use
  pname = "d851fada460d42508a6f82b19867f63853062583.patch";
  version = "";

warning: stdenv.mkDerivation:
  name = "source"
is deprecated, please use
  pname = "source";
  version = "";

warning: stdenv.mkDerivation:
  name = "daemon.conf"
is deprecated, please use
  pname = "daemon.conf";
  version = "";

warning: stdenv.mkDerivation:
  name = "Net-DBus-1.1.0.tar.gz"
is deprecated, please use
  pname = "Net-DBus";
  version = "1.1.0.tar.gz";

warning: stdenv.mkDerivation:
  name = "unit-user-.service"
is deprecated, please use
  pname = "unit-user";
  version = ".service";

warning: stdenv.mkDerivation:
  name = "CVE-2017-6827+CVE-2017-6828+CVE-2017-6832+CVE-2017-6835+CVE-2017-6837.patch"
is deprecated, please use
  pname = "CVE";
  version = "2017-6827+CVE-2017-6828+CVE-2017-6832+CVE-2017-6835+CVE-2017-6837.patch";

warning: stdenv.mkDerivation:
  name = "ntfs-3g_ntfsprogs-2017.3.23.tgz"
is deprecated, please use
  pname = "ntfs";
  version = "3g_ntfsprogs-2017.3.23.tgz";

Ah it was an assert that was reverted from the original implementation #51183

BTW, some language builders do not support name.
https://github.com/NixOS/nixpkgs/blob/ad135f051837538b7486250075e94540018feb2d/pkgs/build-support/emacs/generic.nix#L7-L8
https://github.com/NixOS/nixpkgs/blob/ad135f051837538b7486250075e94540018feb2d/pkgs/build-support/build-dotnet-package/default.nix#L4-L5
https://github.com/NixOS/nixpkgs/blob/ad135f051837538b7486250075e94540018feb2d/pkgs/build-support/ocaml/oasis.nix#L3
So perl won't be pioneering if pname and version will be required params of buildPerlPackage

I'd say those are bugs that should be fixed before release.

If we're going to do this we'd need to update all the examples at

https://nixos.org/nixpkgs/manual/#sec-language-perl

and still people may think they could use name but at least it will give a message.

Let's keep it open and collect people opinions

On the other hand, fetchurl (which is kind of default builder for data/fonts/*) does not accept pname
That result in weird code
https://github.com/NixOS/nixpkgs/blob/94b155aa8be0b039c5cf5bc3b95771609f2af401/pkgs/data/fonts/agave/default.nix#L3-L7


Data Batching, precompilation, and autotune

In this PR we implemented a couple of functionailties:

Precompilation: Now the kernels and updates are constructed and compiled outside the make_xxx functions, inside a function precompilation in LocalSampler_Base.py. Previously there are multiple copies of likelihoods, kernels and update in the code, which bloated the compilation time. Now there should only be two compilation. This should address the concern in #111
Moved autotune for MALA inside the MALA class. In previous version of the code, MALA autotune would makes its own vmap kernel, which would trigger recompilation. This is now handled properly so no recompilation should be needed.
Data batching. Now the sampler can take some additional data. This should address the concern in #93.

There are a couple more to-do items before we can merge this PR:

[x] Modify random walk Gaussian
[x] Modify HMC
[ ] Update examples
[ ] Update documentations
[x] Update tests

Basic documentation on the top level are restructured. Specific tutorials and more example needs to be refactor too.


agent "intro message" to start chat

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.

🔖 Feature description
For certain agent use cases, it is helpful to have the agent/chatbot start the conversation. (As opposed to the user.)
The feature request is for the optional ability to give the agent an "intro message". This serves both the function of prompting the user, as well as initializing the LLM's chat context the same way for every use.
One example of a tool with this feature is Poe:
https://poe.com/create_bot

📝 Additional Context
No response
Acknowledgements

[X] My issue title is concise and descriptive.
[X] I have searched the existing issues to make sure this feature has not been requested yet.
[X] I have provided enough information for the maintainers to understand and evaluate this request.

@rawwerks this is now added to the UI, SDKs and API

thank you so much! that was fast. can't wait to try it out.

@homanp - almost there, but not quite: the intro message works on the internal chat UX, but it is not displayed on the "share" UX https://beta.superagent.sh/share/...


Update to use fcrepo-ocfl-storage

Jira: https://jira.lyrasis.org/browse/FCREPO-3403
What does this Pull Request do?
Updates the migration-utils to use the new fcrepo-storage-ocfl library. I had to add another partial implementation to handle the vanilla OCFL output. There should be no difference in the output, just a change in implementation.
How should this be tested?
Run the migration utils on a a F3 export and start F6 on the output.
Interested parties
@fcrepo4/committers

Hmm... I'm not sure if I agree about the variable names. All this class can claim to do is migrate from F3 to F6. What were the datastream ids in F3 are no longer the ids in F6. Calling them simply fedora does not clarify what they are.

I guess my concern is that we'll be able to use this tool to migrate to F7, F8, etc so we don't want the code to indicate a specific version.  But I see your point as well.  I'll leave it up to your professional judgement.

@awoods :  would you be willing to take a look at my suggestions here re Fedora 6 method and variable names in the code? I don't think it's a big deal if we leave as is  since this tool will likely serve as a migration path from F3->F6.  If the on disc format changes from F6->F7 or Fn we will need a separate migration/upgrade tool to accomplish that task. Perhaps it is in fact better to indicate Fedora6 to make it clear that this is migrating to F6 only.   I only brought this up because I thought our goal with the OCFL setup  was to have a file layout less subject to major changes between versions.  So in theory, users of migration-utils could migrate from F3-> any Fedora readable OCFL regardless of the version.

I tried running the following per the instructions on the README:
Daniels-MBP$ java -jar target/migration-utils-4.4.1-SNAPSHOT-driver.jar --source-type=legacy --limit=100 --target-dir=target/test/ocfl --objects-dir=src/test/resources/legacyFS/objects --datastreams-dir=src/test/resources/legacyFS/datastreams
INFO 15:05:57.804 (InternalIDResolver) No index directory specified.  Creating temporary index at "/var/folders/pt/cd6hk_2x7314mj5h1_f43v7h0000gn/T/tempfile12253528601569998631basedir/index".
INFO 15:05:57.896 (InternalIDResolver) Building an index of all the datastreams in "src/test/resources/legacyFS/datastreams"...
INFO 15:05:58.533 (Migrator) Processing "example:1"...
Resource info:fedora/example:1/AUDIT's file size does not match expectation. Expected: -1; Actual: 3481
Usage: migration-utils [-hrVx] [--debug] -a=<targetDir> [-d=<f3DatastreamsDir>]
                       [-e=<f3ExportedDir>] [-f=<f3hostname>] [-i=<indexDir>]
                       [-l=<objectLimit>] [-m=<migrationType>]
                       [-o=<f3ObjectsDir>] [-p=<pidFile>] -t=<f3SourceType>
                       [-u=<user>] [-U=<userUri>]
...
INFO 15:05:58.879 (InternalIDResolver) Deleting index directory at "/var/folders/pt/cd6hk_2x7314mj5h1_f43v7h0000gn/T/tempfile12253528601569998631basedir/index"...

Trying it with the uw-madison tar gz file @awoods  sent me  I got this error:
Daniels-MBP$ java -jar target/migration-utils-4.4.1-SNAPSHOT-driver.jar --source-type=legacy --limit=100 --target-dir=target/test/ocfl --objects-dir=/Users/danielbernstein/Downloads/uw-madison-fedora-3-sample/objects --datastreams-dir=/Users/danielbernstein/Downloads/uw-madison-fedora-3-sample/datastreams
INFO 15:08:36.291 (InternalIDResolver) No index directory specified.  Creating temporary index at "/var/folders/pt/cd6hk_2x7314mj5h1_f43v7h0000gn/T/tempfile17955120112426763856basedir/index".
INFO 15:08:36.437 (InternalIDResolver) Building an index of all the datastreams in "/Users/danielbernstein/Downloads/uw-madison-fedora-3-sample/datastreams"...
INFO 15:08:37.483 (Migrator) Processing "1711.dl:XMLSchema-UWDC-MODS-3.6-PEERS"...
Unable to resolve internal ID "1711.dl:XMLSchema-UWDC-MODS-3.6-PEERS+SCHEMA+SCHEMA.0"!
Usage: migration-utils [-hrVx] [--debug] -a=<targetDir> [-d=<f3DatastreamsDir>]
                       [-e=<f3ExportedDir>] [-f=<f3hostname>] [-i=<indexDir>]
                       [-l=<objectLimit>] [-m=<migrationType>]
                       [-o=<f3ObjectsDir>] [-p=<pidFile>] -t=<f3SourceType>
                       [-u=<user>] [-U=<userUri>]

@pwinckles  or @awoods : do you see anything that I'm doing wrong in my command line?

@dbernstein Try it with --source-type=akubra

@pwinckles : thanks for the suggestion.  I tried that:
Daniels-MBP$ java -jar target/migration-utils-4.4.1-SNAPSHOT-driver.jar --source-type=akubra --limit=100 --target-dir=target/test/ocfl --objects-dir=/Users/danielbernstein/Downloads/uw-madison-fedora-3-sample/objects --datastreams-dir=/Users/danielbernstein/Downloads/uw-madison-fedora-3-sample/datastreams
INFO 15:48:03.998 (InternalIDResolver) No index directory specified.  Creating temporary index at "/var/folders/pt/cd6hk_2x7314mj5h1_f43v7h0000gn/T/tempfile274630286553936104basedir/index".
INFO 15:48:04.131 (InternalIDResolver) Building an index of all the datastreams in "/Users/danielbernstein/Downloads/uw-madison-fedora-3-sample/datastreams"...
INFO 15:48:05.368 (Migrator) Processing "1711.dl:XMLSchema-UWDC-MODS-3.6-PEERS"...
Resource info:fedora/1711.dl:XMLSchema-UWDC-MODS-3.6-PEERS/RELS-INT's file size does not match expectation. Expected: 618; Actual: 604

I wondering if this may be a cross platform issue?

Interesting... That could very well be

What's strange is that both the uwm sample set as well as the test dataset at src/test/resource/legacyFS are running into problems, albeit they appear to be different issues.

@dbernstein I'm seeing those errors now when I'm running the tests. The cause is that the storage layer was updated to verify content size after creating this PR. Some of the F3 resources are reporting incorrect content sizes, which is causing them to be rejected. Will fix

@dbernstein Okay, I just pushed the fix for the content size as well as most of your pr comments. I did not change the "f6" variable names, because I think it makes the code in that class substantively harder to understand because it is simultaneously dealing with F3 and F6 identifiers.

@pwinckles :  thank you sir.   I will test and assuming all goes well will merge.


Try launch tensorflow and get error

i have install tensorflow on windows 10 and when i put a demo he gives me this error plz help me tanks

Could you please try to install Microsoft Visual C++ 2015 Redistributable Update 3 and let me know if it solves for you?
In a future situation when you need to report an issue please fill the template and post your log instead of screenshots as it helps us assess the situation, otherwise is quite difficult.

I have same error and above solution doesn't work.
(Windows 10)

@dzid26 Could you please provide all the info (OS, Python distribution and version, TensorFlow version, stack trace etc and other relevant information)? Otherwise we won't be able to help you. Thanks.

Win10 64bit,
Python.org v3.5.2:4def2a2901a5, MSC v.1900 64 bit (AMD64)] on win32
Tensorflow 0.11.10 for GPU,
> >pip3 install --upgrade tensorflow-gpu
> Requirement already up-to-date: tensorflow-gpu in c:\program files\python35\lib\site-packages
> Requirement already up-to-date: werkzeug>=0.11.10 in c:\program files\python35\lib\site-packages (from tensorflow-gpu)
> Collecting protobuf>=3.2.0 (from tensorflow-gpu)
>   Downloading protobuf-3.3.0.tar.gz (271kB)
>     100% |################################| 276kB 1.0MB/s
> Requirement already up-to-date: wheel>=0.26 in c:\program files\python35\lib\site-packages (from tensorflow-gpu)
> Requirement already up-to-date: six>=1.10.0 in c:\program files\python35\lib\site-packages (from tensorflow-gpu)
> Requirement already up-to-date: numpy>=1.11.0 in c:\program files\python35\lib\site-packages (from tensorflow-gpu)
> Requirement already up-to-date: setuptools in c:\program files\python35\lib\site-packages (from protobuf>=3.2.0->tensorflow-gpu)
> Requirement already up-to-date: appdirs>=1.4.0 in c:\program files\python35\lib\site-packages (from setuptools->protobuf>=3.2.0->tensorflow-gpu)
> Requirement already up-to-date: packaging>=16.8 in c:\program files\python35\lib\site-packages (from setuptools->protobuf>=3.2.0->tensorflow-gpu)
> Requirement already up-to-date: pyparsing in c:\program files\python35\lib\site-packages (from packaging>=16.8->setuptools->protobuf>=3.2.0->tensorflow-gpu)
> Building wheels for collected packages: protobuf
>   Running setup.py bdist_wheel for protobuf ... done
>   Stored in directory: C:\Users\dzidm\AppData\Local\pip\Cache\wheels\1b\42\a0\4c7343df5b629ec9c75655468dce7652b28026896b0209ba55
> Successfully built protobuf
> Installing collected packages: protobuf
>   Found existing installation: protobuf 3.2.0
>     Uninstalling protobuf-3.2.0:
>       Successfully uninstalled protobuf-3.2.0
> Successfully installed protobuf-3.3.0

And then the full error:
Python 3.5.2 (v3.5.2:4def2a2901a5, Jun 25 2016, 22:18:55) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
Traceback (most recent call last):
  File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 18, in swig_import_helper
    return importlib.import_module(mname)
  File "C:\Program Files\Python35\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 986, in _gcd_import
  File "<frozen importlib._bootstrap>", line 969, in _find_and_load
  File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 666, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 577, in module_from_spec
  File "<frozen importlib._bootstrap_external>", line 906, in create_module
  File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed
ImportError: DLL load failed: The specified module could not be found.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 41, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 21, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 20, in swig_import_helper
    return importlib.import_module('_pywrap_tensorflow_internal')
  File "C:\Program Files\Python35\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ImportError: No module named '_pywrap_tensorflow_internal'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Program Files\Python35\lib\site-packages\tensorflow\__init__.py", line 24, in <module>
    from tensorflow.python import *
  File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\__init__.py", line 51, in <module>
    from tensorflow.python import pywrap_tensorflow
  File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 52, in <module>
    raise ImportError(msg)
ImportError: Traceback (most recent call last):
  File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 18, in swig_import_helper
    return importlib.import_module(mname)
  File "C:\Program Files\Python35\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 986, in _gcd_import
  File "<frozen importlib._bootstrap>", line 969, in _find_and_load
  File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 666, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 577, in module_from_spec
  File "<frozen importlib._bootstrap_external>", line 906, in create_module
  File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed
ImportError: DLL load failed: The specified module could not be found.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 41, in <module>
    from tensorflow.python.pywrap_tensorflow_internal import *
  File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 21, in <module>
    _pywrap_tensorflow_internal = swig_import_helper()
  File "C:\Program Files\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 20, in swig_import_helper
    return importlib.import_module('_pywrap_tensorflow_internal')
  File "C:\Program Files\Python35\lib\importlib\__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ImportError: No module named '_pywrap_tensorflow_internal'

@dzid26 could you check if your cuDNN and CUDA DLLs are properly set in your %PATH%?

Seems ok, I guess. The same error was present, when I tried running the command without cuDNN even being installed.
I am actually surprised that the error message isntt more detailed. Is there a way to see what DLL is it complaining about ?

Your CUDA is an unsupported version. TensorFlow only supports CUDA 8.0 and cuDNN 5.1 on WIndows.

@skye shouldn't we wait if @tonymdsl solved on his side?

@dzid26 @tonymdsl did you have any progress with the solution provided? Please let us know if it worked. Thanks!

No is the same error
Python 3.5.2 (v3.5.2:4def2a2901a5, Jun 25 2016, 22:18:55) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import tensorflow as tf
Traceback (most recent call last):
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 18, in swig_import_helper
return importlib.import_module(mname)
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\importlib_init_.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 666, in _load_unlocked
File "", line 577, in module_from_spec
File "", line 906, in create_module
File "", line 222, in _call_with_frames_removed
ImportError: DLL load failed: Impossível localizar o módulo especificado.

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 41, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 21, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 20, in swig_import_helper
return importlib.import_module('pywrap_tensorflow_internal')
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\importlib_init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError: No module named '_pywrap_tensorflow_internal'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow_init_.py", line 24, in
from tensorflow.python import *
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python_init_.py", line 51, in
from tensorflow.python import pywrap_tensorflow
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 52, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 18, in swig_import_helper
return importlib.import_module(mname)
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\importlib_init_.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 666, in _load_unlocked
File "", line 577, in module_from_spec
File "", line 906, in create_module
File "", line 222, in _call_with_frames_removed
ImportError: DLL load failed: Impossível localizar o módulo especificado.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 41, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 21, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 20, in swig_import_helper
return importlib.import_module('pywrap_tensorflow_internal')
File "C:\Users\Tonymds\AppData\Local\Programs\Python\Python35\lib\importlib_init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError: No module named '_pywrap_tensorflow_internal'
Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/install_sources#common_installation_problems
for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

hello = tf.constant('Hello, TensorFlow!')
Traceback (most recent call last):
File "", line 1, in
NameError: name 'tf' is not defined
sess = tf.Session()
Traceback (most recent call last):
File "", line 1, in
NameError: name 'tf' is not defined

Just by seeing your %PATH% screenshot is still difficult to infer everything is properly installed. Could you make sure your cuDNN DLLs are properly set as CUDA's? This is most likely a CUDA/cuDNN misconfiguration, assuming of course your TF version is the latest with GPU support as you didn't specify.

is working now the problem is i use cudNN 6.0 and now i put the cudNN 5.1 and now it's working tank u very much for the help

TensorFlow only supports cuDNN 5.1 on Windows, glad it's working now!
Thank you for reporting, this issue can be closed.

Finally it worked for me too. But it was not obvious that /bin folder
within cudann was supposed to be add.
Also this instruction on the website is inaccurate because CUDA 8.0
documentation doesn't mention setting up %path%. And that is not even
relevant, since the path is added automatically by the installer.
The main problem is with cudann nvidia's instructions.
Anyway, hopefully better installation process will be developed in the
future. Thanks guys
Radek
On Wed, May 3, 2017 at 5:24 PM, Skye Wanderman-Milne <
<EMAIL_ADDRESS>wrote:

Closed #9603 https://github.com/tensorflow/tensorflow/issues/9603.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/9603#event-1068015874,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAzVZY915eM0fzDAs3Pg8983EUXswMZQks5r2PCGgaJpZM4NOzR3
.

For users who find this issue when searching for the error message, I've created a script for diagnosing common TensorFlow on Windows installation issues. Please download the script from https://gist.github.com/mrry/ee5dbcfdd045fa48a27d56664411d41c and run python tensorflow_self_check.py. It will print suggestions for how to fix your installation. Let me know if you are still facing problems after running the script.


Small delay on authentication.

There is small delay of a few seconds when users get authenticated with this .so. Here is an example:
Fri Jun  7 14:51:22 2019 us=127255 MULTI: multi_create_instance called
Fri Jun  7 14:51:22 2019 us=127302 Re-using SSL/TLS context
Fri Jun  7 14:51:22 2019 us=127356 Control Channel MTU parms [ L:1623 D:1210 EF:40 EB:0 ET:0 EL:3 ]
Fri Jun  7 14:51:22 2019 us=127369 Data Channel MTU parms [ L:1623 D:1450 EF:123 EB:406 ET:0 EL:3 ]
Fri Jun  7 14:51:22 2019 us=127403 Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1559,tun-mtu 1500,proto TCPv4_SERVER,cipher AES-256-CBC,auth SHA1,keysize 256,key-method 2,tls-server'
Fri Jun  7 14:51:22 2019 us=127409 Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1559,tun-mtu 1500,proto TCPv4_CLIENT,cipher AES-256-CBC,auth SHA1,keysize 256,key-method 2,tls-client'
Fri Jun  7 14:51:22 2019 us=127450 TCP connection established with [AF_INET]<IP_ADDRESS>:47448
Fri Jun  7 14:51:22 2019 us=127456 TCPv4_SERVER link local: (not bound)
Fri Jun  7 14:51:22 2019 us=127463 TCPv4_SERVER link remote: [AF_INET]<IP_ADDRESS>:47448
Fri Jun  7 14:51:23 2019 us=127998 <IP_ADDRESS>:47448 TLS: Initial packet from [AF_INET]<IP_ADDRESS>:47448, sid=64d63019 fa9c6f15
Fri Jun  7 14:51:23 2019 us=154159 <IP_ADDRESS>:47448 peer info: IV_VER=2.4.7
Fri Jun  7 14:51:23 2019 us=154195 <IP_ADDRESS>:47448 peer info: IV_PLAT=linux
Fri Jun  7 14:51:23 2019 us=154208 <IP_ADDRESS>:47448 peer info: IV_PROTO=2
Fri Jun  7 14:51:23 2019 us=154220 <IP_ADDRESS>:47448 peer info: IV_NCP=2
Fri Jun  7 14:51:23 2019 us=154230 <IP_ADDRESS>:47448 peer info: IV_LZ4=1
Fri Jun  7 14:51:23 2019 us=154241 <IP_ADDRESS>:47448 peer info: IV_LZ4v2=1
Fri Jun  7 14:51:23 2019 us=154251 <IP_ADDRESS>:47448 peer info: IV_LZO=1
Fri Jun  7 14:51:23 2019 us=154261 <IP_ADDRESS>:47448 peer info: IV_COMP_STUB=1
Fri Jun  7 14:51:23 2019 us=154272 <IP_ADDRESS>:47448 peer info: IV_COMP_STUBv2=1
Fri Jun  7 14:51:23 2019 us=154283 <IP_ADDRESS>:47448 peer info: IV_TCPNL=1
Fri Jun  7 14:51:23 2019 us=155778 <IP_ADDRESS>:47448 PLUGIN_CALL: POST /root/openvpn-plugin-auth-script.so/PLUGIN_AUTH_USER_PASS_VERIFY status=2
Fri Jun  7 14:51:23 2019 us=155880 <IP_ADDRESS>:47448 TLS: Username/Password authentication deferred for username 'FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3' [CN SET]
Fri Jun  7 14:51:23 2019 us=156630 <IP_ADDRESS>:47448 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384
Fri Jun  7 14:51:23 2019 us=156721 <IP_ADDRESS>:47448 [FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3] Peer Connection Initiated with [AF_INET]<IP_ADDRESS>:47448
Fri Jun  7 14:51:24 2019 us=283465 <IP_ADDRESS>:47448 PUSH: Received control message: 'PUSH_REQUEST'
Fri Jun  7 14:51:24 2019 us=283627 FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3/<IP_ADDRESS>:47448 MULTI_sva: pool returned IPv4=<IP_ADDRESS>, IPv6=(Not enabled)
okFri Jun  7 14:51:24 2019 us=311863 FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3/<IP_ADDRESS>:47448 OPTIONS IMPORT: reading client specific options from: /dev/shm//openvpn_cc_3ebc5a271b15743f1ae661976e3ed9a2.tmp
Fri Jun  7 14:51:24 2019 us=312057 FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3/<IP_ADDRESS>:47448 MULTI: Learn: <IP_ADDRESS> -> FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3/<IP_ADDRESS>:47448
Fri Jun  7 14:51:24 2019 us=312101 FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3/<IP_ADDRESS>:47448 MULTI: primary virtual IP for FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3/<IP_ADDRESS>:47448: <IP_ADDRESS>

Fri Jun  7 14:51:29 2019 us=444439 FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3/<IP_ADDRESS>:47448 PUSH: Received control message: 'PUSH_REQUEST'
Fri Jun  7 14:51:29 2019 us=444563 FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3/<IP_ADDRESS>:47448 SENT CONTROL [FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3]: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS <IP_ADDRESS>,route <IP_ADDRESS>,topology net30,ifconfig <IP_ADDRESS> <IP_ADDRESS>,peer-id 0,cipher AES-256-GCM' (status=1)
Fri Jun  7 14:51:29 2019 us=444628 FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3/<IP_ADDRESS>:47448 Data Channel: using negotiated cipher 'AES-256-GCM'
Fri Jun  7 14:51:29 2019 us=444711 FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3/<IP_ADDRESS>:47448 Data Channel MTU parms [ L:1551 D:1450 EF:51 EB:406 ET:0 EL:3 ]
Fri Jun  7 14:51:29 2019 us=445077 FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3/<IP_ADDRESS>:47448 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jun  7 14:51:29 2019 us=445140 FadZR0cO1YnqMeXOXH7k1KbghDmbO6ttBISLuCgh3MHQZ87WE3mYXROZx9jk3/<IP_ADDRESS>:47448 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key

This behavior was strange since the bash script returned successful result at Fri Jun  7 14:51:23 UTC 2019, but access was granted at 14:51:29

My memory on this functionality is a bit hazy but I believe this behavior is actually caused by the way OpenVPN manages the interface this plugin implements. Once the auth process is initiated OpenVPN essentially continues about its business for several seconds before polling the result file to see if access was granted or rejected. I want to say that polling window is 5 seconds to minimize the impact on active network flows, however, it might be configurable.
The log entries you're referencing at 14:51:23 in that log detail the OpenVPN process triggering the plugin call.

The log entries you're referencing at 14:51:23 in that log detail the OpenVPN process triggering the plugin call.

The script was also spitting out timestamp and it returned at the same second, without delay.

I want to say that polling window is 5 seconds to minimize the impact on active network flows, however, it might be configurable.

If that is the case, than this is more an OpenVPN issue than anything related to the plugin. Do you have any idea where in the OpenVPN code I should start looking?

Do you have any idea where in the OpenVPN code I should start looking?

Hi @g00nix ,
Were you able to figure that out? Any hints @pdemonaco ?

@ss-17 nope, we just figured we can run a high number of users with serial authentication, so we gave up on the script. Just make sure your authentication script is fast.

As I mentioned earlier, this is likely intentional behavior from the perspective of the OpenVPN process as it is single threaded. The purpose of the asynchronous authentication hook is to prevent a slow authentication action for a single new connection from causing traffic for other active VPN clients to pause. Instead of actually waiting for a response, it kicks off the authentication attempt and then returns to its normal business of processing traffic. After some wait interval (5 seconds possibly) it rechecks the authentication provider to see if a result has been found. This process will repeat for as long as it takes for the provider to return.
In my use case, the authentication provider was tied to a phone-app based multi-factor solution. As a result, each authentication event included the following time components:

OpenVPN -> Auth Server ~ 5 ms
Auth Server -> Cloud ~ 20 ms
Cloud -> Mobile Phone ~ 50 - 300 ms
User delay ( users don't immediately answer / notice the push) ~ 5000 - 45000 ms
Mobile Phone -> Cloud ~ 50 - 300 ms
Cloud -> Auth Server ~ 20 ms
Auth Server -> OpenVPN ~ 5 ms

This yields something on the order of 5 seconds delay  in the best case and in the worst case it can easily extend beyond a minute. It's important to note that no traffic will be processed by OpenVPN during this time as it blocks waiting for the response from the authentication provider on each authentication request.
When we first implemented without asynchronous authentication, the concurrent connection of 10 to 15 users would totally disrupt all VPN traffic for about 15 minutes by creating an authentication storm. I suspect this was a combination of different authentication events timing out during the delay of the first connection and users retrying connections and queuing up a series of authentication attempts.
If your authentication provider returns immediately there is no reason to use code which implements this asynchronous hook. If you do have lengthy delays, I'm struggling to understand why this brief client-side delay is a concern.

Thanks for your reply @g00nix . Its not the plugin's shortcoming as the delay is because of how OpenVPN works to achieve this more or less asynchronous authentication.

I'm struggling to understand why this brief client-side delay is a concern.

@pdemonaco, its not a cause of concern. Just a curiosity to figure out whether this delay is reducible in code. I might be wrong but after some digging in the relevant files in order to understand the mechanism, my conclusion is that you cannot reduce this delay by changing something in the code on the server side. It works like this:

Client -> Sends auth details.
Server -> Server initiates the deferred auth mechanism (creates auth_control_file) and moves on.
Client -> Sends PUSH_REQUEST to check status on the auth.
Server checks the auth_control_file and if its updated by the background process sends the auth status to client (success or failed). Otherwise doesn't reply anything and moves on (just like the step 2).
If client gets the auth status = all good. Otherwise client waits for PUSH_REQUEST_INTERVAL (by default 5 seconds in src/openvpn/common.h) and sends another PUSH_REQUEST (back to step 3).

So as you can see the delay on re-checking the auth status is determined by the client OpenVPN and not the server which does it only when the client asks for it. If the background process updates the auth_control_file by the time client sends the first PUSH_REQUEST, the authentication is almost instantaneous. But if that doesn't happen (which is normal and happens randomly), client will ask for rechecking of auth status after a period of 5 seconds and thus the delay. Server isn't the guilty party here. The relevant code is in forward.c:

/*
* Periodically resend PUSH_REQUEST until PUSH message received
*/
void
check_push_request_dowork(struct context *c)
{
send_push_request(c);

/* if no response to first push_request, retry at PUSH_REQUEST_INTERVAL second intervals */
event_timeout_modify_wakeup(&c->c2.push_request_interval, PUSH_REQUEST_INTERVAL);
}

The impossible and impractical solution would be to ask every client to compile OpenVPN after reducing PUSH_REQUEST_INTERVAL to 1 or 2 from 5 in the common.h file. The other workaround is to compile server with --enable_async_push. But then you have to have a fixed and same "cipher ALGO" (ALGO here is case sensitive. "cipher AES-128-CBC" on server won't match "cipher aes-128-cbc" on client) on both server and client side and disable cipher negotiation by putting "ncp-disable" in server config. I checked this configuration and it does remove the delay at the cost of sticking to a fixed encryption cipher for every client. The inability to use NCP with async-push was fixed in the latest version of OpenVPN (2.4.9) but I am yet to test this.
https://community.openvpn.net/openvpn/ticket/1259
https://github.com/OpenVPN/openvpn/blob/release/2.4/Changes.rst
Hope this helps.

When we first implemented without asynchronous authentication, the concurrent connection of 10 to 15 users would totally disrupt all VPN traffic for about 15 minutes by creating an authentication storm.

That is not the case any more. Authentication doesn't disrupt traffic with the latest version of OpenVPN. The only issue today is that authenticating 5 users with a delay of over 3 seconds each will take over 15 seconds.


Functionality of the screen is operable through Tab and arrow kays but there is no such indication, Widget Builder issue.

Describe the bug
Functionality of the screen is operable through Tab and arrow kays but there is no such indication, Widget Builder issue.
To Reproduce
Steps to reproduce the behavior:
Go to Widget Builder  (http://localhost:9992/cm/app/?view=widgetbuilder&site=test2&mode=readonly&name=index.html&path=%2FSites%2Ftest&pathType=page)
Click create new widget.
Content, Resources and Display tabs are accessible through Tab and Arrow key but not indicated.
Expected behavior
if Functionality of the screen is operable through Tab and arrow kays then indication should be there.
Additional context
Navigate all the options available for similar issue and fix.

Not reproducible. It got fixed while fixing some other bug.


Better error message for threadsafe test case like looking functions

Straight from the MIES tests:
#include "unit-testing"

threadsafe Function myTest()

End

gives
•runtest("procedure")
  Error: Prototype function TEST_CASE_PROTO_DGEN was called.

and the user has no clue what is going wrong.

@MichaelHuth I think the statement in https://github.com/byte-physics/igor-unit-testing-framework/pull/68/files#r275903221 is not correct as this is exactly the point there this bugs out.


Improve nightly functional tests

🗣 Description
This PR adds Teams to the nightly tests (along with SharePoint).  Several small configuration changes enable multiple products to be supported, not just one.
This closes:  https://github.com/cisagov/ScubaGear/issues/731
💭 Motivation and context
The nightly functional tests provide developers with information about product changes that have created new and unexpected issues.  As functional testing is time consuming, these tests are run nightly instead of on push.
🧪 Testing
These tests are implemented as a GitHub Action workflow, so I ran the workflow.
Note that the Team tests are currently failing due to an issue in Teams test plans.  This PR, however, is functioning as intended.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] PR targets the correct parent branch (e.g., main or release-name) for merge.
[x] Changes are limited to a single goal - eschew scope creep!
[x] Changes are sized such that they do not touch excessive number of files.
[x] All future TODOs are captured in issues, which are referenced in code comments.

The remaining nightly tests will be finished via this issue:  https://github.com/cisagov/ScubaGear/issues/824

[x] These code changes follow the ScubaGear content style guide.
[x] Related issues these changes resolve are linked preferably via closing keywords.
[x] All relevant type-of-change labels added.
[x] All relevant project fields are set.
[x] All relevant functional tests passed.
[x] All automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ Pre-merge checklist

[ ] PR passed smoke test check.

[ ] Feature branch has been rebased against changes from parent branch, as needed
Use Rebase branch button below or use this reference to rebase from the command line.

[ ] Resolved all merge conflicts on branch

[ ] Notified merge coordinator that PR is ready for merge via comment mention

✅ Post-merge checklist

[ ] Feature branch deleted after merge to clean up repository.
[ ] Verified that all checks pass on parent branch (e.g., main or release-name) after merge.

Would recommend changing the PR summary of changes to indicate that the change is to support testing multiple products vs a single product rather than saying it's just adding SharePoint support.

Done.

@nanda-katikaneni , I think this one is ready to merge.  Thanks!


Clean commented-out code

Removes most of the commented-out code from sonarqube. There's definitely more hiding throughout the codebase, but this should be most of it.


at what level should cancellations be allowed, if at all?

 This feature is particularly useful for people executing cross-domain arbitrage.
There are 2 possible 'types' of cancellations:

searchers cancelling their bundles to the builder
the builder cancelling their block to the relay/proposer

The former is introduced by the builder, in which case this doesn't affect mev-boost code. The latter would concern mev-boost. We focus on this second case.
Naturally, no cancellation is possible after a header has been signed upon by the proposer - aside from a 'brute-force cancellation' where a relay does not reveal the body of a block.
Questions

Does allowing cancellations at the mev-boost level opens up a DoS vector for the relay?

The DoS here would be a builder submitting blocks, relay checking validity and then receiving cancellation request for it. There is a likely asymmetry between compute needed to cancel a body and re-submit a new one vs checking the validity of a body

Does allowing cancellations mean bidding is now messed up? please refer to issue #112 for more details here.

In particular, I worry this means someone could bid very high, scare other builders from participating in a round then cancel right before the end. This feel pretty harmless though but I would like to surface the concern.

I have a related but very specific proposal at the relay level: always use latest block sent by each builder.
Let's look at block templates that come within a single slot, and how the relay handles them to decide what to forward to proposers:
Currently, it seems like relays will use the most profitable block sent by each builder. This is a proposal to use the latest block sent by each builder, instead.
Why? This would allow for builders for more sophisticated strategies, where they can decide to not propose a transaction anymore in their blocks.
Nothing else changes. The relay still simulate every block templates that it receive, etc.
Pros:

It's makes the design space for builders bigger as they are not locked in old block templates that may contain transactions they don't want to submit anymore.
Lowers the DoS risk a little: you could imagine builder spamming the relay and relying on it to simulate every block, and select the most profitable one. This is impossible if the relay only keeps the last block sent.

Cons:

If a builder sent a less profitable or invalid block, their previous more profitable block is dropped. However this has no reason to happen, apart from a software bug in the builder: a well-behaved builder should only sent more profitable block templates to relays than their previous one (in the duration of a single slot).


Command Not Found

Microsoft PowerToys version
0.77.0
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce
Go to the new Command not found module
It will show that you don't have powershell 7.4 or above because it's only searching for the included version and not the one on program and files
✔ Expected Behavior
Work fine
❌ Actual Behavior
Not working
Other Software
No response

Same issue here:

@glenncarr @CesarSant2000 , PowerToys tries to use the pwsh.exe it finds on PATH.
For example if you try to run (Win+R) "pwsh.exe" which version do you get?
/needinfo

@jaimecbernardo  That's it...

@jaimecbernardo I uninstalled the x86 version and all is well.  Thank you!

@jaimecbernardo I uninstalled the x86 version and all is well. Thank you!

Thanks for the feedback!
Although I'm not quite sure why it would pick up the x86 version 😆
We're using ProcessStartInfo from C#. Perhaps the x86 appears first in the path resolution logic.

Glad you found the fix, @CesarSant2000 and @glenncarr. I'll be marking this resolved and renaming the issue to help others find it in the future. If you run into any problems, feel free to open a new issue. Thanks! :)


Settings  broken

Setup: dev server running with recent (v29) evidence template.
Problem: Under Settings there is an "open accordion" down-arrow button, but it does not work.
It worked w/ evidence v28.
JS Console also says:
[Warning] <AccordionItem> received an unexpected slot "title". (client.js, line 2002)
[Warning] <AccordionItem> was created with unknown prop 'small' (client.js, line 2002)

The problem seems to be related to https://github.com/evidence-dev/evidence/commit/15a6eeabf22762919f725eda0537489326bad724.
In fact, replacing the following code in https://github.com/evidence-dev/evidence/blob/next/packages/core-components/src/lib/unsorted/ui/Deployment/EnvironmentVarListing.svelte
		<AccordionItem small>
			<div slot="title" class="w-full flex justify-between items-center">
				All Environment Variables
				<Button on:click={copyVars} type="button" outline icon={Clipboard} size="sm">
					Copy All
				</Button>
			</div>

with
		<AccordionItem title="All Environment Variables">

improves the situation (somewhat).
Environment

Node version (node -v): v20.11.1
OS: Linux 6.1.0-13-amd64
Browser: Mac Safari

Fixed in https://github.com/evidence-dev/evidence/pull/1736


Bump swift version to 5.0

OP, will this library be updated to this and be maintained? I'd love to use this, but it doesn't seem that there's been much attention to it. This merge would be nice.

Thank you for your contribution. Merging.


Some limitations of the built-in DNS service

I spent some time testing various DNS scenarios while looking into https://github.com/rancher-sandbox/rancher-desktop/issues/1181 and noticed the following issues:

on systemd instances mDNS lookup would not work. The request never goes to our own server, but is presumptively handled directly by systemd-resolved. Since it can only broadcast on the slirp interface, it can't find any devices on the host network.

*.local names that are provided by DNS and have no corresponding mDNS response are reported too late, so get a DNS timeout. It looks like our DNS server is waiting for the mDNS query to time out before returning the DNS name (or from /etc/hosts).

While looking for a workaround, I tried (on Alpine, to avoid systemd) various entries in /etc/hosts. Specifying a .local name as an alias works, and both names can be resolved in the guest:
<IP_ADDRESS> foo.internal foo.local

If the .local name is the canonical name, then neither name returns a result before an error occurs:
<IP_ADDRESS> foo.local foo.internal

On the host system, the .local names from /etc/hosts are resolved without any delay, so why is this different?

Assigning low priority because using .local with unicast DNS is discouraged.
Providing mDNS lookup to systemd-based instances may be regular priority though.

cc/ @dee-kryvenko

Furthermore, it looks like with systemd-resolved, the host resolver is still configured as a backup even when useHostResolver is false.

I'm also facing some issues with dns right now because I have a dnsmasq container I'm trying to run and I'm wondering if there is ever a scenario where you'd want a VM to use it's own private dns resolver opposed to your machines dns setup. Wouldn't that mean there are two dns resolvers, one on my machine and one inside the VM? Is there a scenario where my machine would not have dns configured and access to the internet but the VM would?


Getting error related to lodash typings recent update.

We are getting this issue related to lodash typings.
Typescript version in use is 1.6.
Any help would be appreciated ?

I have the same issue. Typescript 1.5, lodash 2.4.1.

Nice builds perfectly. Please merge.
Screenshot...


Feature request: Filter collection

For example, we collected all data from the OpenOpps API, and now @camilamila wants to generate summaries for each country within the data.
I think the condition would only need to be added to release_tmp.sql
We can maybe add a CLI option (multiple=True) to express the field and value to filter on, for example, --filter buyer.address.countryName="United States", and the script would convert this to data->'buyer'->'address'->>'countryName' = 'United States'. (Using > on the command line would likely lead to user errors if the user forgets to quote the argument, so I used periods which we use elsewhere.)
The script would have to trim quotation marks from the value in this case. Alternately, we can use a pair of options --filter-field and --filter-value (like Flatten Tool), to avoid that step. However, we want to support multiple filters, so in this case, users will have to be careful to use the same order in --filter-field and --filter-value.
Update: Actually, Click has multi-value options so we can do: --filter buyer.address.countryName 'United States'.

It would also be useful to filter by release date. For example, I would like to compare the field_counts table for uk_fts and uk_contracts_finder, but only for 2021, when the publications were running in parallel.

@Camilamila @yolile Based on your work, what common filters do you use?

Release dates, buyer names/ids, and sometimes items classifications

I've been trying out some SQL/JSON Path Language locally, and it's pretty powerful. It seems to fit this kind of use case well.
Filtering on item classification id: (it defaults to lax mode, where there's no need to explicitly expand arrays)
AND jsonb_path_match(data.data, '$.contracts.items.classification.id == "SOME-ID"')

It looks like it can even handle lookups against the parties array. Here's filtering for a particular buyer name:
AND jsonb_path_match(data.data, 'exists($.parties[*] ? (@.id == $.buyer.id && @.name == "Buyer Name"))')

To support these more complex queries, I think it makes sense to let users pass SQL/JSON Path Language from the command line.
We could also make users supply SQL/JSON Path Language for the simpler cases too, as there's no problem with escaping greater than signs, but it is necessary to get the quotes right.

@jpmckinney What do you think?

Sounds good. I'll ask Dogsbody about a schedule for upgrading PostgreSQL. It might be early next year, but we'll see.

Should I finish off the PR that works with the current PostgreSQL version, or should I switch to assuming SQL/JSON Path Language support? I'd rather do the latter, but obviously that will delay anything going live.
BTW, there's some useful features in PostgreSQL 13 for dealing with dates within JSON, which are missing in 12. (And probably best to upgrade to the latest version anyway.)

We could also make users supply SQL/JSON Path Language for the simpler cases too, as there's no problem with escaping greater than signs, but it is necessary to get the quotes right.

I'm happy with this, as long as we can have a documentation page with examples.

Should I finish off the PR that works with the current PostgreSQL version, or should I switch to assuming SQL/JSON Path Language support? I'd rather do the latter, but obviously that will delay anything going live.

Switching to SQL/JSON Path Language sounds good to me - no issue with delaying the deploy until the server has been upgraded from my perspective.
@jpmckinney just double checking you agree with the above. Thanks!

I think the PR is just about ready, so we might as well merge it, and then come back and add SQL/JSON Path support.

The PR for the current postgres version is merged and deployed.
I've just made a PR for SQL/JSON Path Language based filters https://github.com/open-contracting/kingfisher-summarize/pull/217 (this can't be merged until postgres is upgraded on the live server).

Closing as merged and deployed.


Use evaluate implementation from granite

We currently have 2 implementations of evaluate, one in granite-form and one in granite. This PR brings implementation from granite and replaces one in granite. In practice this means 2 changes:

enum: -> (model) { model.field } is no longer supported and needs to be replaced with enum: -> { field }, a version that both evaluate implementations support.
We now support enum: :some_method which calls the method with that name on model.
Same goes for default, readonly, normalize, except that default: :symbol doesn't call a method but just sets the default value to :symbol.

@toptal-anvil ping reviewers


ETA for Screenshot / getPixel(s) ?

I was taken a look at the src files and they do seem pretty straight forward. Kudos to the writers! Unfortunately I don't know any C or C++, really frustrating to sort of understand the code but being unable to contribute :P
Any idea when there will be a function that returns a bitmap or something like a typed array that can be manipulated in JavaScript?

Just for fun I tried making a little function that creates a typed array that can be used for an image with the current version.
It took almost 14 minutes to create a picture of my 1366 x 768 screen :D
var robot = require("robotjs");

var WIDTH = robot.getScreenSize().width;
var HEIGHT = robot.getScreenSize().height;

console.time("perf");

var img_data = create_Screen_Shot(WIDTH, HEIGHT);

console.timeEnd("perf");

function create_Screen_Shot ( width, height ) {

	var buffer = new Uint8ClampedArray(width * height * 4);

	var hex = "";
	var rgb = "";

	for ( var i = 0, il = width; i < il; i += 1 ) {
		for ( var j = 0, jl = height; j < jl; j += 1 ) {

			hex = robot.getPixelColor( i, j );
			rgb = hexToRgb(hex);

			position = (i * width + j) * 4;

			buffer[ position ]     = rgb.r;
                buffer[ position + 1 ] = rgb.g;
                buffer[ position + 2 ] = rgb.b;
                buffer[ position + 3 ] = 255;

		}
	}

	return buffer;

};

// http://stackoverflow.com/a/5624139/1502407
function hexToRgb(hex) {
    var result = /^#?([a-f\d]{2})([a-f\d]{2})([a-f\d]{2})$/i.exec(hex);
    return result ? {
        r: parseInt(result[1], 16),
        g: parseInt(result[2], 16),
        b: parseInt(result[3], 16)
    } : null;
}

You can preview and use the screen capture code on Mac, I'm struggling to get it to work on Windows though.
http://blog.robotjs.io/post/130642552013/i-spent-a-few-hours-yesterday-and-today-working-on
Things have also been really crazy at work, it might be a while till I can finish this unfortunately.
Also see:
https://github.com/octalmage/robotjs#can-i-take-a-screenshot-with-robotjs


Add Separation event

Add Separation to the family events table.

Discussion in GEDCOM Steering Committee meeting 9 MAY 2024:

We are merging this based on the statement that existing programs may be doing this already.
We will separately track the request to have a Separated attribute.

@dthaler looked like you merged main into my branch and not the PR into main so just force pushed my branch again to reset it.


Annotation errors in StanfordExtra_V12

I've noticed systematic errors in the annotations included in StanfordExtra_v12.json
In particular, when an image contains more than two dogs, bounding box and keypoint annotations are included for only one of them.
Some sample image with this issue are:
n02085620-Chihuahua/n02085620_1152.jpg
n02085782-Japanese_spaniel/n02085782_749.jpg
n02085936-Maltese_dog/n02085936_2020.jpg

I'll let Ollie confirm, but I believe this is deliberate. Labels were only obtained for the 'primary dog (largest)' in the image. I believe images with multiple dogs were ultimately filtered from the evaluation set for Who Left the Dogs Out. Hoping @OllieBoyne can clarify/verify.

Hi,
I should clarify our procedure. As Ben said, keypoint labels were obtained for the 'largest' dog in the image, segmentations for all dogs in the image, and the bounding boxes are from an external dataset (StanfordDogs).
As a result, there may be some discrepancies when there are multiple dogs in the image. To avoid this, we added the tag, 'is_multiple_dogs' to these labels, so they can be discarded if necessary.
However, it appears this label is not operating as expected, and is set to False for the images you have described. I will look into this and see if I can fix it.
Many thanks,
Ollie

Hi Ollie,
Thanks for the clarification! Did you have a chance to fix the issue?
Thanks,
Anastasis


feat: add focusNode parameter (#33)

Thank you for this pull request, and I apologize that I'm just now seeing it. I will try to take a look at it in the coming weeks

looks good to me


Change Markdown table Gather mode for Emoji's

Change the markdown table to use emojis instead of using the name of gather modes
Example
🧭

Icon
Mode
Emoji
Measure
Performance
Accessibility
Best Practices
SEO
PWA

Navigation
🧭
Page load
100% / 30
100% / 30
100% / 30
100% / 30
✔ / 7

Timespan
⏱
User Interaction
10  / 10
❌
7  /  7
❌
❌

Snapshot
📷
Current page state
4  /  4
16  / 16
5  /  5
9  /  9
❌

we could try to use inline SVG graphics.

If we alter the markdown table string this should be a separate method that does not get called as part of stdout as it makes it very hard to read the table as console log


Question

This mod looks a little complex.
Does it affect server performance in any way?
Does it constantly perform calculations that would otherwise not take place?

Every time the server attempts to spawn a mob, it will have to iterate over every entity in the world in order to find villagers. I haven't measured how much this iteration affects performance, but I think it should be minimal.
Beyond that, the calculations on each villager are limited to measuring its (squared) distance to the target spawn point; this is as similar as it can be to the Vanilla calculations that take place on every  players.
The server attempts to spawn mobs on more or less every tick, so performing those calculations constantly is technically unavoidable.

"... it will have to iterate over every entity in the world in order to find villagers."
I suppose this refers to only the loaded chunks right?
That's still a lot of entities, with limited server resources, it makes me worry a bit.

Yes of course.
Trying to include unloaded entities would honnestly be too absurd to even attempt. Completing a single iteration would require loading all chunks at least once, or to keep them loaded at all time. The performance cost of just that would not go unnoticed, regardless of the amount of entities.

That's still a lot of entities, with limited server resources, it makes me worry a bit.

To put things into perspective: On every tick, the base game has to iterate over all entities in order to update them. For each entity, it then has to iterate again over every other one in order to check for entity collisions.
Vanilla already does many such iterations per ticks, so each loop really must have a really negligible computation cost. These cases are just those I could come up with off the top of my head, there are probably more. Compared to that, this mod's iteration loop add little to the workload.

Thanks for the information, I'll try it out then, I suppose it can safely be removed in any case.


Error after Update to 10.0.41

After updating our 10.0.40 environment with D365FO Admin Toolkit Installed to 10.0.41 I get the following error message when trying to add the System Administrator Role to a user:
Method not found: 'Dynamics.AX.Application.SysApplicationInsightsEventTelemetry Dynamics.AX.Application.SysApplicationInsightsEventTelemetry.addProperty(Dynamics.AX.Application.SysApplicationInsightsProperty)'.
The issue does not happen when I add another role. It does not help to add the user to excluded Users and it does not help to turn off Reason Message.
Since the message contained "Dynamics.AX.Application.SysApplicationInsightsEventTelemetry" I thought it might have something to do with @jofme s latest addition around logging so I tried disabling the telemetry... did not help...
Does anyone have any idea?

No idea. I'm still on 10.0.40, that's why I haven't seen the issue.
I just landed back in Denmark, but  I'll have a look at it later today.

Yes I have... Does not solve it... That was my first thought when I saw SysApplicationInsightsEventTelemetry. I had just read your request/issue from the other day,

@jofme @JoPe72 - Hey all, based on the error I agree that it looks like Microsoft has changed the method signatures on the SysApplicationInsightsEventTelemetry class in the 10.0.41 update
I am deploying an environment currently to take a look and will follow up with any findings

Awesome... Let me know if I can help
Med vänliga hälsningar/Best regards,
Johan Persson
+46 70 609 49 99

From: Alex Meyer @.>
Sent: Tuesday, August 20, 2024 15:58
To: ameyer505/D365FOAdminToolkit @.>
Cc: Johan Persson @.>; Mention @.>
Subject: Re: [ameyer505/D365FOAdminToolkit] Error after Update to 10.0.41 (Issue #40)
@jofmehttps://github.com/jofme @JoPe72https://github.com/JoPe72 - Hey all, based on the error I agree that it looks like Microsoft has changed the method signatures on the SysApplicationInsightsEventTelemetry class in the 10.0.41 update
I am deploying an environment currently to take a look and will follow up with any findings
—
Reply to this email directly, view it on GitHubhttps://github.com/ameyer505/D365FOAdminToolkit/issues/40#issuecomment-2298933325, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADCD3PEPKUBPCSUP7MSIKS3ZSNDSHAVCNFSM6AAAAABMZWKS5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJYHEZTGMZSGU.
You are receiving this because you were mentioned.Message ID: @.***>

@JoPe72 @ameyer505  I managed to reproduce the issue in my OneBox machine after updating to the PEAP version in LCS's shared library.

To fix the issue, I simply had to rebuild the model. My going assumption is that there is some kind of binary incompatibility between the builds... Need to play with this a bit more.
@JoPe72 I can send you a deployable package build on 10.0.41 to test my theory?

@ameyer505 you are correct, they have refactored SysApplicationInsightsEventTelemetry, so it now extends from SysApplicationInsightsTelemetryContractBase that contains the addProperty.
Updates should not break interfaces, and should always be backwards compatible; This is clearly a bug in the PEAP release.
I haven't gotten access to the Insider Yammer yet (Requested it a few months ago when I started at my new job). Can you check there for me?
The work-around is simple, I just move the check out of the method, so it never enters the method with the changed (and broken) interface. Then we at least can add admin roles, disregarding the telemetry. What do you say?

@jofme thanks for confirming and appreciate the quick turnaround on this.
I am favor of the workaround and am happy to put out a 'hotfix' release once the new code is checked in.
I do not see anything within Yammer recently about either class you mentioned. I can go ahead a log a bug because I 100% agree with your assessment of 'updates to D365 should not break interfaces'.

@JoPe72 @ameyer505 I managed to reproduce the issue in my OneBox machine after updating to the PEAP version in LCS's shared asset library.
To fix the issue, I simply had to rebuild the model. My going assumption is that there is some kind of binary incompatibility between the builds... Need to play with this a bit more. @JoPe72 I can send you a deployable package build on 10.0.41 to test my theory?

Yes Please :-)

@JoPe72 here you go 😄
D365AdminToolkit_<IP_ADDRESS>_10041.zip

Thanks @jofme, Great work. The fix worked perfectly!

Thanks @jofme, Great work. The fix worked perfectly!

Thats what weird, it's the <IP_ADDRESS> version without changes, but built on a machine with 10.0.41... Think I'm writing a blog post about it

@jofme - whoa that is weird, would be really curious on the underlying root cause of this (irrespective of the impact to the toolkit but just for my knowledge as an ISV)

I got feedback today from a client testing the D365 Admin toolkit. They have the same error when removing the SysAdmin role from an user. I'm awaiting their Dynamics 365 version information. If they are on 10.0.41, then I will send the deployable package as shared above by @jofme to @JoPe72.

@Dynamicspedia - I have created a new release that includes the changes for this bug
I have built the solution against a 10.0.39 and a 10.0.41 version of D365FO and have a release for each to hopefully support all current D365FO clients


[Experimental] First attempt at replacing AST traversal with Maybe

Prototyping of Maybe monad in AST traversal
This is intended to further discuss whether/how Maybe monad would be a good fit in

writing internal AST traversal
jQuery style helpers for Rules development

src/angular/metadataReader.ts seems to be a good target to start. Most of the work goes into extracting AST traversal code into astQuery and ngQuery.
A few realizations so far

Maybe monad introduces a bit a learning curve, but the structure makes the intent easier to understand (e.g. decoratorArgument)
There are a few wrinkles getting the proper type returned, but type guard helps (e.g. callExpression)

Looks hot, happy to see your suggestion in action! Will take a look at it in the next a couple of days and give you feedback. Thanks!

Had some more thoughts about refactor experience so far.
Can codelyzer develop against a different TS than the runtime TS? I have a feeling you can, but if not, it harder to write compatible type-friendly code as a lot of useful features like 'control flow based type analysis' and 'dot name type guards' landed only in TS 2.0
More refactoring can be done in src/angular/metadataReader.ts, but that likely require adding a 'seam' to urlResolver and fileResolver to make it Maybe friendly.
Also there may be a few minor bugs, I'll highlight them below.

Added Walker builder (a builder approach and a functional approach) in attempt to make Rule definition easier.

I left some comments. The linter is failing:
src/componentClassSuffixRule.ts(15,31): error TS2304: Cannot find name 'suffix'.
src/componentClassSuffixRule.ts(25,32): error TS2334: 'this' cannot be referenced in a static property initializer.
src/componentClassSuffixRule.ts(25,37): error TS2339: Property 'getOptions' does not exist on type 'typeof Rule'.
src/componentClassSuffixRule.ts(25,63): error TS2334: 'this' cannot be referenced in a static property initializer.
src/componentClassSuffixRule.ts(25,68): error TS2339: Property 'getOptions' does not exist on type 'typeof Rule'.
src/componentClassSuffixRule.ts(26,61): error TS2346: Supplied parameters do not match any signature of call target.

Nothing new yet, just fixed the above error resulted from merging master.

Awesome! I just published beta.4, we can introduce this new AST traversal mechanism in beta.5.


CockroachCloud docs should be self-contained

tl;dr: Our Cloud docs build should include all of the things a user needs to be productive in the Cloud environment in its build without the jarring "open non-Cloud things in a new tab" experience
Currently, when you go to the SQL page in the CockroachCloud docs and want to check out our SQL support, you are given a link to the non-cloud SQL Statements page.  The page opens in a new tab and the experience is very jarring.  You are thrown into a completely new context with no clear map of "where you are", which is confusing.  This is especially the case since you were probably not expecting a new tab to be opened in a completely different documentation set that you do not understand, much of which is not relevant to your needs.
Estimated scope of this issue is:

Identify what docs are missing from Cloud to be truly self-contained
Figure out how to update the Cloud build process to include those docs under the Cloud TOC
Figure out what changes are necessary to said docs (includes, etc.) to get them into Cloud build while enabling re-use of as much as possible
Ensure that no links point from Cloud to non-Cloud things
... probably many other things that I can't think of right now

cc @Amruta-Ranade @jseldess FYI
Y'all already know about the need for this work, but Amruta asked me to file an issue since (AFAICT) there isn't one for this work.

Thanks, @rmloveland. This really needs to be handle in the context of an overall information architecture revamp. I'm planning to schedule an offsite soon for us and other informed/interested people to get ideas generated.

I'm going to close this for now since we did some work to change the hierarchy. This could obviously be iterated on in the future, but will open a new issue for that later.


Wrong hover state of links on footer

Description

The color of footer links turn green on hover state, when it should keep dark-turquoise color, according to the pattern.
Reproduction

Go to https://opensource.creativecommons.org/ or any derivated page.
Position the mouse over any menu link on footer.
See error.

Expectation

Keep footer uniform, keep the color of links.
Resolution

[ ] I would be interested in resolving this bug.

This is a good first issue for new contributors 🐣

@krysal can I work on this?
I plan to change the main.scss file for this issue, it looks like that would solve the problem.Would that be enough or do I need to work on some other files too?

Since the bug originates in Vocabulary (explanation), this issue is more suited to be solved there.