Only your gold limits how much vendors can train you to

Even after deleting the e_trainer event from vendors, vendors can still train you to unlimited hights, only gold is the limit.
You can go well above 1000, 2000 or 3000% skill. - Fault is both in click menu and spoken "train"

Please note if you have below (whatever "train up to max" you have set in sphere.ini) it works, they only offer you to train to that, but then as soon as you are above (lets say 30.0) you can go and talk to them again, and then they will give you 1 skill pr. 1 gold, for as long as you have gold

Have you tried with the default scriptpack? I can't replicate here

Thats wierd, i have no scripts interferring with vendors, but if you cant recreate it, i apologize for the waste of time, i will do some further investigation on my end. Thought maybe there was something hardcoded with this new: @PayGold ... because as soon as i have surpassed the limited 30.0 skill, i can just drop gold on them and they train directly scaled with the gold i drop.. aint no limit, can go well above 100.0 skill - But thanks for the testing

No problem, feel free to reopen this issue if you find it isn't script related!


Update statsd-instrument wrapping code to be compatible with 2.5.0

Bug report
kubernetes-deploy tried to do optimistic versioning for statsd-instrument, but this allowed for it to be bumped to 2.5.0 which is API incompatible. This will cause deploy failures like those in #575 if an app is not using a gemfile to pin the version already. If a bundle update occurs, deploys will fail.
Expected behavior:
Deploys should proceed and not fail in the monkey-patched statsd code
Actual behavior:
Deploys fail with a stacktrace like:
Traceback (most recent call last):
--
  | 11: from /usr/bin/kubernetes-deploy:23:in `<main>'
  | 10: from /usr/bin/kubernetes-deploy:23:in `load'
  | 9: from /usr/lib/ruby/gems/2.5.0/gems/kubernetes-deploy-0.27.0/exe/kubernetes-deploy:71:in `<top (required)>'
  | 8: from /usr/lib/ruby/gems/2.5.0/gems/kubernetes-deploy-0.27.0/lib/kubernetes-deploy/options_helper.rb:28:in `with_processed_template_paths'
  | 7: from /usr/lib/ruby/gems/2.5.0/gems/kubernetes-deploy-0.27.0/exe/kubernetes-deploy:83:in `block in <top (required)>'
  | 6: from /usr/lib/ruby/gems/2.5.0/gems/kubernetes-deploy-0.27.0/lib/kubernetes-deploy/deploy_task.rb:140:in `run!'
  | 5: from /usr/lib/ruby/gems/2.5.0/gems/kubernetes-deploy-0.27.0/lib/kubernetes-deploy/statsd.rb:67:in `block in measure_method'
  | 4: from /usr/lib/ruby/gems/2.5.0/gems/kubernetes-deploy-0.27.0/lib/kubernetes-deploy/statsd.rb:37:in `distribution'
  | 3: from /usr/lib/ruby/gems/2.5.0/gems/statsd-instrument-2.5.0/lib/statsd/instrument.rb:462:in `distribution'
  | 2: from /usr/lib/ruby/gems/2.5.0/gems/statsd-instrument-2.5.0/lib/statsd/instrument.rb:373:in `measure'
  | 1: from /usr/lib/ruby/gems/2.5.0/gems/statsd-instrument-2.5.0/lib/statsd/instrument.rb:537:in `collect_metric'
  | /usr/lib/ruby/gems/2.5.0/gems/statsd-instrument-2.5.0/lib/statsd/instrument/backends/udp_backend.rb:110:in `collect_metric': undefined method `<' for nil:NilClass (NoMethodError)

Version(s) affected:
0.27.0 at least, but probably all versions.
Steps to Reproduce
Deploy any app that doesn't use a Gemfile.lock, or do a bundle update and try to deploy.

I should be clear though, getting #575 out fixes the immediate issue, but we still need to port the API forward, which is what this issue is for.

If we move straight to 2.7.0 we can drop (some of?) the monkeypatching: https://github.com/Shopify/statsd-instrument/blob/master/CHANGELOG.md#version-270.

Fixed by https://github.com/Shopify/kubernetes-deploy/pull/594, though the new min version is 2.9


ci: Cache mdbook installs to reduce CI build time

We spend a lot of time installing and compiling mdbook from source. This caches mdbook across builds.

Looks good to me.

Thanks!


Commands not interactive, login not working

Trying this on a Windows 7 machine. The commands don't seem to go into interactive mode when I run them without flags like:
pinoccio login
When I try running with flags or with unflagged variables, login returns without a message:
pinoccio login -e<EMAIL_ADDRESS>-p password
Afterwards, a command that needs a token like pinoccio bridge will fail with the message:
you must login or register first. try 'pinoccio register'

Hi,  have you seen anything from the pinoccio creators about this promise of providing an open version of HQ?  "We will continue to support the Pinoccio API and HQ services that we run until 11:59p PDT, May 31, 2015. We will release the open-source versions of those services well before that date, "

hey. i did implement the pinoccio api in a self contained module. https://github.com/Pinoccio/pinoccio-api
ill have to clone it and test it out to see what's "done"

the work to clean up the hq UI and open it up may have died on the vine.

On 09/01/2015 10:03 AM, Ryan Day wrote:

the work to clean up the hq UI and open it up may have died on the vine.

Hmm.. Doesn't that bug you?  They promised to make it available, if not continue improving it.
I just stumbled onto this platform and the web apps and server code,
and am interested in whatever might be FOSS licensed.
John Griessen

only so much time in the day. :)
To be honest I never used hq much. i found the command line tools to be
exactly the ones I needed.
On Sep 1, 2015 3:34 PM, "John Griessen"<EMAIL_ADDRESS>wrote:

On 09/01/2015 10:03 AM, Ryan Day wrote:

the work to clean up the hq UI and open it up may have died on the vine.

Hmm.. Doesn't that bug you? They promised to make it available, if not
continue improving it.
I just stumbled onto this platform and the web apps and server code,
and am interested in whatever might be FOSS licensed.
John Griessen
—
Reply to this email directly or view it on GitHub
https://github.com/soldair/pinoccio-server/issues/2#issuecomment-136835381
.

I just got word from filament that they plan to release an open version of HQ by year end.  So they are keeping their promises.


Feature request: support for Docker DNS proxy, or equivalent

NB: I'm not sure if this is something specific to my setup.
For some reason, after updating my Gentoo system, DNS resolution from inside Docker containers managed by dfw in nftables mode ceased to work. It seems that Docker is attempting to create iptables forwarding rules for its DNS proxy, and failing.
time="2021-01-18T18:41:48+01:00" level=error msg="set up rule failed, [-t nat -I DOCKER_OUTPUT -d <IP_ADDRESS> -p udp --dport 53 -j DNAT --to-destination <IP_ADDRESS>:53982]"
time="2021-01-18T18:41:48+01:00" level=error msg="set up rule failed, [-t nat -I DOCKER_POSTROUTING -s <IP_ADDRESS> -p udp --sport 53982 -j SNAT --to-source :53]"
time="2021-01-18T18:41:48+01:00" level=error msg="set up rule failed, [-t nat -I DOCKER_OUTPUT -d <IP_ADDRESS> -p tcp --dport 53 -j DNAT --to-destination <IP_ADDRESS>:32987]"
time="2021-01-18T18:41:48+01:00" level=error msg="set up rule failed, [-t nat -I DOCKER_POSTROUTING -s <IP_ADDRESS> -p tcp --sport 32987 -j SNAT --to-source :53]"

I would like to request a dfw option for creating equivalent rules on docker's behalf. As the ports are randomized, this is tricky, but not impossible; a netstat -lp call from inside the container shows that dockerd is listening on two ports, one TCP and one UDP.
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:32987        <IP_ADDRESS>:*               LISTEN      3624/dockerd
udp        0      0 <IP_ADDRESS>:53982        <IP_ADDRESS>:*                           3624/dockerd

Alternatively, dfw could run its own DNS proxy, obtaining container names from the network configuration data to provide 'equivalent' behaviour for docker stacks which use container names to connect services together.
For anyone who stumbles on this from Google, my temporary workaround is to bind-mount the host's /etc/resolv.conf file into the container, which prevents Docker from overriding the DNS with its <IP_ADDRESS> address. This allows me to run single containers, but not stacks.

Looks like https://crates.io/crates/procfs gives us the netstat bits, but I'm not sure how that will interact with dfw itself being inside a container; may have to bind-mount the host's /proc or something?
Some playing with nsenter and netstat indicates that the answer to that seems to be yes; at least read-only access to /proc will be needed to get the network namespace of the other docker container.

Hi @Georgiy-Tugai, thank you for reaching out and for all the detail you provided!
As documented in the getting started guide for nftables, Docker should be configured to not manipulate any iptables rules by setting the daemon option iptables to false. This is required for dfw to function correctly, and in my experience does not break DNS resolution; at least I never had issues.
I cannot rule out that Docker >=20.10.0 might have "broke" compatibility by introducing new DNS-resolution or firewall-handling behaviour, and although a quick check of the release notes does not necessarily suggest this, I currently cannot confirm this since I have not yet upgraded the Docker daemons in my setup past 19.03.
Maybe you can check if you have iptables-handling in your Docker daemon deactivated, and if it isn't, whether deactivating fixes your issues? I'll also try to get around to upgrading to Docker 20.10 to test this myself, too!

Hi @Georgiy-Tugai, thank you for reaching out and for all the detail you provided!
As documented in the getting started guide for nftables, Docker should be configured to not manipulate any iptables rules by setting the daemon option iptables to false. This is required for dfw to function correctly, and in my experience does not break DNS resolution; at least I never had issues.
I cannot rule out that Docker >=20.10.0 might have "broke" compatibility by introducing new DNS-resolution or firewall-handling behaviour, and although a quick check of the release notes does not necessarily suggest this, I currently cannot confirm this since I have not yet upgraded the Docker daemons in my setup past 19.03.
Maybe you can check if you have iptables-handling in your Docker daemon deactivated, and if it isn't, whether deactivating fixes your issues? I'll also try to get around to upgrading to Docker 20.10 to test this myself, too!

Thanks for your quick response! 😄
I do have iptables set to false, of course. Going by docker debug logs (see my first post) and https://github.com/moby/libnetwork/issues/1085#issuecomment-399782903 docker ignores the iptables setting specifically when it comes to the eDNS system.
/etc/conf.d/docker
DOCKER_OPTS="--storage-driver zfs --data-root /var/lib/docker --cgroup-parent docker --init --log-driver json-file --log-opt max-size=10m --log-opt max-file=3 --log-opt compress=true --iptables=false"

# prevent race between dfw and nftables init
rc_after="nftables"

The breakage initially happened when I upgraded from app-emulation/docker-19.03.8 to app-emulation/docker-19.03.14 and from sys-kernel/gentoo-sources-4.19.86 to sys-kernel/gentoo-sources-5.4.80-r1. I later upgraded to app-emulation/docker-20.10.1 hoping that it might help.
I also suspect kernel configuration issues, given the major version upgrade, but I haven't found anything weird in the iptables/nftables section so far. I have both iptables and nftables built as modules, and ipt_MASQUERADE blacklisted since it is known to interact poorly with the nftables version.

Thanks for your quick response! 😄
I do have iptables set to false, of course. Going by docker debug logs (see my first post) and https://github.com/moby/libnetwork/issues/1085#issuecomment-399782903 docker ignores the iptables setting specifically when it comes to the eDNS system.
/etc/conf.d/docker
DOCKER_OPTS="--storage-driver zfs --data-root /var/lib/docker --cgroup-parent docker --init --log-driver json-file --log-opt max-size=10m --log-opt max-file=3 --log-opt compress=true --iptables=false"

# prevent race between dfw and nftables init
rc_after="nftables"

The breakage initially happened when I upgraded from app-emulation/docker-19.03.8 to app-emulation/docker-19.03.14 and from sys-kernel/gentoo-sources-4.19.86 to sys-kernel/gentoo-sources-5.4.80-r1. I later upgraded to app-emulation/docker-20.10.1 hoping that it might help.
I also suspect kernel configuration issues, given the major version upgrade, but I haven't found anything weird in the iptables/nftables section so far. I have both iptables and nftables built as modules, and ipt_MASQUERADE blacklisted since it is known to interact poorly with the nftables version.

I attempted to reproduce the issue on a Debian Buster VM. DNS resolution in that environment worked correctly, which led me to re-examine the kernel configuration aspect.
Manually invoking the failing iptables commands in the container's namespace gave cryptic error messages; could not find "tcp" and the like. Translating the rule via iptables-translate allowed the rule to install successfully via an nft invocation, but that is not what Docker is doing.
In the end, it turned out that I was missing the nft_compat module (CONFIG_NFT_COMPAT) which seems to be required even if iptables-nft is being used rather than iptables-legacy.
@pitkley This can now be demoted from "blocking issue" to "neat feature maybe"; might be worth adding some blurb about this to the nftables guide, I guess, if nothing else.
Sorry for bothering you with what turned out to be my kernel config silliness 😄
For people who might find this later, here's the relevant fragment of my kernel configuration; I'm using a config-merging tool based on https://github.com/ulfalizer/Kconfiglib so this is a "delta" config relative to x86+Gentoo defaults.
CONFIG_BRIDGE=y
CONFIG_IPVLAN=m
CONFIG_MACVLAN=m
CONFIG_TUN=m
CONFIG_IPVTAP=m
CONFIG_MACVTAP=m
CONFIG_VETH=m
CONFIG_VXLAN=m

CONFIG_NET_KEY=y

# IP Payload Compression Protocol (RFC3173), typically needed for IPsec
CONFIG_INET6_IPCOMP=y

# Support for INET socket monitoring, used by tools such as ss
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_INET_UDP_DIAG=y
CONFIG_INET_RAW_DIAG=y
CONFIG_UNIX_DIAG=y

# allow setting weird netfilter modules
CONFIG_NETFILTER_ADVANCED=y

# let arp/iptables see bridged traffic... does this apply to nftables?
 DNS resolution in that environment worked correctly, which led me to re-examine the kernel configuration aspect.
Manually invoking the failing iptables commands in the container's namespace gave cryptic error messages; could not find "tcp" and the like. Translating the rule via iptables-translate allowed the rule to install successfully via an nft invocation, but that is not what Docker is doing.
In the end, it turned out that I was missing the nft_compat module (CONFIG_NFT_COMPAT) which seems to be required even if iptables-nft is being used rather than iptables-legacy.
@pitkley This can now be demoted from "blocking issue" to "neat feature maybe"; might be worth adding some blurb about this to the nftables guide, I guess, if nothing else.
Sorry for bothering you with what turned out to be my kernel config silliness 😄
For people who might find this later, here's the relevant fragment of my kernel configuration; I'm using a config-merging tool based on https://github.com/ulfalizer/Kconfiglib so this is a "delta" config relative to x86+Gentoo defaults.
CONFIG_BRIDGE=y
CONFIG_IPVLAN=m
CONFIG_MACVLAN=m
CONFIG_TUN=m
CONFIG_IPVTAP=m
CONFIG_MACVTAP=m
CONFIG_VETH=m
CONFIG_VXLAN=m

CONFIG_NET_KEY=y

# IP Payload Compression Protocol (RFC3173), typically needed for IPsec
CONFIG_INET6_IPCOMP=y

# Support for INET socket monitoring, used by tools such as ss
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_INET_UDP_DIAG=y
CONFIG_INET_RAW_DIAG=y
CONFIG_UNIX_DIAG=y

# allow setting weird netfilter modules
CONFIG_NETFILTER_ADVANCED=y

# let arp/iptables see bridged traffic... does this apply to nftables?
CONFIG_BRIDGE_NETFILTER=m

# Ethernet bridge stuff
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_T_NAT=m

# turn off iptables
CONFIG_IP_NF_IPTABLES=n
CONFIG_IP6_NF_IPTABLES=n
CONFIG_IP_NF_FILTER=n
CONFIG_IP6_NF_FILTER=n
CONFIG_IP_NF_TARGET_REJECT=n
CONFIG_IP6_NF_TARGET_REJECT=n
CONFIG_IP_NF_NAT=n
CONFIG_IP_NF_TARGET_MASQUERADE=n
CONFIG_IP_NF_MANGLE=n
CONFIG_IP6_NF_MANGLE=n
CONFIG_IP6_NF_MATCH_IPV6HEADER=n

# shut up linter
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_STATE=m

# nftables
CONFIG_NF_TABLES=m
CONFIG_NF_TABLES_INET=y
CONFIG_NF_TABLES_IPV4=y
CONFIG_NF_TABLES_IPV6=y
CONFIG_NF_TABLES_BRIDGE=m

CONFIG_NF_FLOW_TABLE=m

# needed for some iptables-compatibility stuff... sigh
CONFIG_NETFILTER_XTABLES=m
CONFIG_NFT_COMPAT=m

CONFIG_NFT_NAT=m

CONFIG_NFT_MASQ=m

CONFIG_NFT_CONNLIMIT=m
CONFIG_NFT_COUNTER=m
CONFIG_NFT_CT=m
CONFIG_NFT_LIMIT=m
CONFIG_NFT_LOG=m
CONFIG_NFT_OBJREF=m
CONFIG_NFT_QUOTA=m

CONFIG_NFT_REDIR=m

CONFIG_NFT_REJECT=m
CONFIG_NFT_REJECT_INET=m
CONFIG_NFT_REJECT_IPV4=m
CONFIG_NFT_REJECT_IPV6=m

CONFIG_NFT_TUNNEL=m
CONFIG_NF_TABLES_SET=m

# stuff that doesn't work because SECURITY=n
CONFIG_NETLABEL=n
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=n
CONFIG_NETFILTER_XT_TARGET_SECMARK=n

# docker wants these
CONFIG_IP_VS=m
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_NFCT=y
CONFIG_IP_VS_RR=m
CONFIG_DUMMY=y
CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=m
CONFIG_NETFILTER_XT_MATCH_IPVS=m

I'm glad you were able to resolve it, and I greatly appreciate the amount of detail you have provided. I have added a section to the troubleshooting document which references this issue! 👍

I'm glad you were able to resolve it, and I greatly appreciate the amount of detail you have provided. I have added a section to the troubleshooting document which references this issue! 👍


[Revert](partial update) Revert "Fix missing rowsets during doing alignment when flushing memtable due to compaction #28062 (#28468)"

This reverts commit 8c8f322574df58e900d9ccef0d680d723d594368.
Proposed changes
revert pr #28468 that may result in duplicate key for mow table.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Support renaming databases

Description
SQL has the ALTER command, Pilosa has no analogous command.
Success criteria (What criteria will consider this ticket closeable?)
The ability to rename databases.

This is really dependent upon using internal names for indexes. We don't want to change the name of an index directly, because that would require moving fragments around (based on the hash algorithm). But if we kept an internal index name, and the external index name was just an alias, then that could easily be changed.


Dump Shape FIles  into GeoJson

Is there a way to use this package and convert the shp files into JSON?
Thanks

No, there is not. That is not within the scope of this package.
I'd recommend using ogr2ogr for converting shape files to GeoJSON or a variety of other vector formats for geo-information.


Race detector tests fail on netbsd-amd64

The netbsd-amd64 builder currently fails every build because the exitcode test case in the Race detector tests is failing.
A representative log is at https://build.golang.org/log/ccd6b1b37fe12e4ec1399381b8b83e0d391b6a23; the interesting part is this:
##### Testing race detector
--- FAIL: TestOutput (12.61s)
    output_test.go:76: failed test case exitcode, expect:
        exit status 13
        got:
        ==================
        WARNING: DATA RACE
        Write at 0x00c0000160e8 by goroutine 5:
          main.main.func1()
              /tmp/go-build795352810/main.go:7 +0x38

        Previous write at 0x00c0000160e8 by main goroutine:
          main.main()
              /tmp/go-build795352810/main.go:10 +0xb5

        Goroutine 5 (running) created at:
          main.main()
              /tmp/go-build795352810/main.go:6 +0xa7
        ==================
        Found 1 data race(s)
        exit status 66
FAIL
FAIL	runtime/race	12.621s
2018/08/26 22:06:36 Failed: exit status 1

/cc @krytarowski

Is this something new? We were passing of 98% race tests, but we have not enabled them in the tests.
I propose to keep it disabled.
I'm working now on improving the C and C++ runtime of sanitizers on NetBSD.

Looks like 7e64377903b3abd922150e35601e0df597a8af9f added netbsd to the list of supported architectures. Are you proposing we remove it from there, so as not to run the race detector tests in a normal build?

I propose to not run the race detector tests in a normal build. There was already a meta ticket for TSan/NetBSD in this repo.

See #26403 for the umbrella bug.
I don't think it is a regression, it's just that the change above makes the race detector test run as part of all.bash. The failure can be reproduced by running
go test -race runtime/race


Reflowing doc comments containing examples breaks stdsimd

This doc comment
/// Foo
///
/// # Example
/// ```
/// # #![cfg_attr(not(dox), feature(cfg_target_feature, target_feature, stdsimd))]
/// # #![cfg_attr(not(dox), no_std)]
/// ```
fn foo() {}

is formattted to:
/// Foo
///
/// # Example
/// ```
/// # #![cfg_attr(not(dox), feature(cfg_target_feature, target_feature,
/// stdsimd))] # #![cfg_attr(not(dox), no_std)]
/// ```
fn foo() {}

which fails to compile (with max_width = 79).

@nrc would it be possible to add stdsimd as a test to rustfmt's ci ?
That is, a test that checks out stdsimd master, builds everything (including tests and doc tests), then formats it with rustfmt, and then re-builds ?

I think we should not be reformatting examples in rustdoc without an opt-in.

@nrc would it be possible to add stdsimd as a test to rustfmt's ci ?

That sounds like a good idea for a smoke test!

I think we should not be reformatting examples in rustdoc without an opt-in.

I think it is ok to disable this for now, but ideally rustfmt would detect examples into doc comments, and would format them as normal rust code but handling rustdoc idiosyncrasies appropriately (like lines that start with #).


Final changes before introducing database interface

As agreed with @dnldd, this PR will contain all of the additional work required before introducing a database interface. I will mark this as a draft and only approve it once all of the necessary changes are included. Each commit will be a standalone change with a proper description, so they can be reviewed individually. The next PR following this one will be the interface.
Part of #257

Looking good, reviewed the first two commits and haven't spotted any issues so far.

I've rebased everything above without making any changes. Going to continue adding new changes below.


There is a typo in the second line.

"...while policies..."  should be "which policies..."

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

ID: 7e746c38-18e2-56fd-becf-a4d0d05127f6
Version Independent ID: d4be02d5-a0c5-a614-f206-e3448bd337cc
Content: Details of the policy assignment structure - Azure Policy
Content Source: articles/governance/policy/concepts/assignment-structure.md
Service: azure-policy
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

#assign:DCtheGeek

@AndreasFrangopoulos Thanks for catching this! I’ll get it fixed later today.
@MicrosoftDocs/azure-cxp-triage Please label ‘doc-bug’ and #in-progress.

@DCtheGeek Thanks for the quick response. :+1: Added labels 'doc-bug' and 'in-progress'.

@AndreasFrangopoulos The change is building and once the fix merges, this issue will close automatically. Thanks again for pointing this out!


Docs and demo should make osm namespace more generic

**Please describe what should be documented
Currently docs and demos assume osm control-plane is installed in the osm-system namespace. We should make this more generic.
**Please suggest where in the repo the document should be located

I have updated the demo docs to not hardcode the install namespace: https://docs.openservicemesh.io/docs/demos/
osm-system is still being used as a default in some docs for convenience.


[App]: Custom chart shows "no data available"

Current Behavior
Hi, I really like using wandb and I am very grateful for the services you provide!
However, today I encountered a bug:
Similar to #4368, I get the message "No data available." when trying to plot my key "Val mIoU" on the y axis when creating a custom chart on the Web App, as the screenshot below:

I tried this solution (https://community.wandb.ai/t/no-history-data-in-custom-charts/2087/2) and did not work either.
However, I tried the same solution with another key (val_loss) and it worked (see next screenshot). The same is true for other keys that do not contain the space character in their name.

I am therefore suspecting that if a key contains the space character in its name the above does not work, because I tried with two keys without the space character and worked, while with other two without the space character did not.
Could you please help me?
Expected Behavior
No response
Steps To Reproduce
No response
Screenshots

Environment
OS:
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Browsers:

Firefox 118.0.2

Version:

wandb, version 0.15.12

Additional Context
No response

Hi @lucamarini22, thanks for reporting this one! I just tested on my end and was able to get custom charts both using metrics with and without spaces (see here). Would you mind sharing a link to your Workspace so I can take a look and also a code snippet of how you're logging your metrics so I can reproduce this on my end?

@luisbergua thanks for the reply!
Are the following code snippets enough? Or do you also need to know when the following functions are called?
wandb.log(
    {
        "Val mIoU": eval["IoU"],
        "Max Val mIou": max_val_miou_among_epochs,
        "epoch_max_val_miou": epoch_max_val_miou
    }
)

and in another function:
wandb.log(
    {
        "epoch": epoch,
        "train_loss_mean": train_loss,
        "val_loss": val_loss,
        "min_val_loss_among_epochs": min_val_loss_among_epochs,
        "epoch_min_val_loss": epoch_min_val_loss,
        "sup_component_loss": sup_loss,
        "unsup_component_loss": unsup_loss
    }
)

and in another function:
wandb.log(
    {
        "train_loss": train_loss,
        "step": (epoch - 1) * len_dataloader + idx_dataloader,
    }
)

With normal charts I'm able to plot:

"step" on the x-axis and "Val mIoU" on the y-axis
but not "epoch" on the x-axis and "Val mIoU" on the y-axis

With custom charts I'm not able to plot any of the 2 above.
Is there a way I can share a link to my workspace without putting it as public?

Hi @lucamarini22, thank you so much for providing this! For now, those snippets are enough, just a quick question, are those variables float? About the link, you can share it without making it public and I'll be able to see it

Thanks for the reply @luisbergua

"Val mIoU" is float
"epoch" is int
"step" is int

and her's the link to my workspace:
https://wandb.ai/elmaren/anomaly-marine-detection/sweeps/9q0ohnkv?workspace=user-lucamarini22

Thanks for sharing this @lucamarini22! I took a look at your Workspace, reason why you cannot get that chart is because metric Val mIoU was logged at a different step than epoch. The same happens with Max Val mIou and epoch_max_val_miou and you can check that if you try to change the x-axis for the created line plots ('epoch' doesn't appear as an option). To fix this, you could log them all at the same step (you can set commit=False to wait until that's set to True and log everything together, docs here), use define_metric (docs here) or create a Weave plot with an expresion like [{epoch: runs.history.concat["epoch"].dropna, Val_mIoU: runs.history.concat["Val mIoU"].dropna}]

Thanks @luisbergua ! I'll try your suggestions and let you know if I'll encounter any issue.
In the meanwhile, do you also know why I get the message

No data available

even when I try to create the custom chart by putting:

step on the x-axis
Val mIoU on the y-axis
?

Are also these two logged at different step?

Thanks @luisbergua ! I'll mark the issue as solved since both:

using _step in the x-axis
using Weave worked for me (even though I did not find a way to download the chart once it was created with Weave (maybe it's something that could be of interest)


Keyboard popup view auto-scroll not working for  or

npm version 6.2.0
react-native 0.56.0
native-base 2.7.2
I cannot get the soft keyboard popup to auto-align with input text position or cursor. The view doesn't autoscroll at all, and the keyboard covers the inputs.
With the following View layout:
<Container>   <Content padder enableAutomaticScroll>     <Form>       <Textarea rowSpan={5} />       <Textarea rowSpan={5} />       <Textarea rowSpan={5} />       <Textarea rowSpan={5} />     </Form>   </Content> </Container>
Some screenshots of a textarea with and without the keyboard

It's at least present in iOS.
Any thoughts?

@SupriyaKalghatgi I went through that whole issue, and attempting to use a ScrollView + KeyboardAvoidingView doesn't produce any better results for me.
Keep in mind, my structure is using the suggested NativeBase  and  components, so that shouldn't be a problem...
It does work properly on Android, FYI.

I shared #1518 to share an example where Keyboard works fine with

Similar issue here in iOS.
The normal  does trigger a scroll into focus with the keyboard visible.
The multiLine  does not.
<Container >
                <Content scrollEnabled>
                    <StatusBar hidden />
                    <Grid>
                        <Row style={{height: 600, backgroundColor: 'green'}}>
                            <Text>Image placeholder</Text>
                        </Row>
                        <Row >
                            <Form >
                                <Item regular>
                                    <Input  />
                                </Item>
                                <Item stackedLabel last>
                                    <Input   multiline placeholder='Type your text here'/>
                                </Item>
                            </Form>
                        </Row>
                    </Grid>
                </Content>
            </Container>

https://github.com/facebook/react-native/issues/20996
Happens to be React Native issue


Update bindings for firmware version 0.83.1

https://github.com/flipperdevices/flipperzero-firmware/releases/tag/0.83.1
From what I can tell, it's a relatively large diff because the order of a lot of structs and functions got changed without any actual changes. Seems like the order of include paths got shuffled around a bit probably because of this item in the release notes:

Libs: STM32CubeWB replaced with it's stand-lone, stripped version

Update

I've updated the tools/Dockerfile, it should produce byte-for-byte identical bindings.rs.

Any updates on this? I tried making an app with @kitterion's branch but I still get the same API mismatch error.

So is this ready?

I believe so, although I now see that upstream bumped their SDK version again yesterday with firmware version 0.84.0-rc, so the upcoming firmware release will be incompatible again. From that perspective, I'm inclined to merge this (so people can work from the main branch), but wait the extra week or so until the next official firmware release, and then push out a crate version targeting that.

Any updates on this? I tried making an app with @kitterion's branch but I still get the same API mismatch error.

@gmelodie that implies your Flipper Zero's firmware version is not either 0.82.3 (required for the version 0.9.0 crates) or 0.83.1 (required for this branch). Can you check what version you are running (either via qFlipper, or `Settings -> About -> last page)?

0.84.1 was released 2 hours ago! I'll merge this and then get another PR up for that bump.


RabbitMQ Basic Sources Added

Great, Thanks, dear Reza, Your changes are notable! Keep up the excellent work!

Thank you dear mohammad, I appreciate it.


Change ADS Update Infra to client side

https://github.com/microsoft/azuredatastudio/pull/25677
https://github.com/microsoft/azuredatastudio/pull/25694
Port PRs:
https://github.com/microsoft/azuredatastudio/pull/25682
https://github.com/microsoft/azuredatastudio/pull/25695


Redesign of packing type to support CBOR decoding

The Decoder type is parameterzsed by some * -> * type.
A packing type need not (shouldn't) be inhabited, but must be an instance of the new PackingType class which determines concrete monadic context for encoding and decoding. For existing store and binary packing types these are all Identity.
To use a packing type instance packingType to run a node over m, a Packing packingType m must be given. See unpack and pack in Node.Message.Class.
Fix recvNext in case end of input happens during a partial parse. Previously it would End but now it correctly throws NoParse.
continueDecoding now takes a single ByteString rather than [ByteString].

@dcoutts

On it as we speak guys, I hope to be able to give you the final 👍  as soon as I can!

@avieth @dcoutts This is the initial, horrid prototype:
https://github.com/adinapoli-iohk/cardano-sl/commit/cb8ee2389794f8188a9e9562614364f79152227d
Let me know if it makes any kind of sense to you!

Weird CI failure... looks like everything went OK but then it timed out, even after the test suite was successfully run.

Let me know if it makes any kind of sense to you!

Makes perfect sense! Is everything working well with the revision I sent you? Even after this is merged, we'll still have to keep that special revision until #1116 of cardano-sl lands.

Makes perfect sense! Is everything working well with the revision I sent you?

It does! I had to make only one minor tweak to my instance which was generalise bipPacking to run in MonadIO m so that we can now use it in places like Pos.Launcher.Runner.runServer. This is ofc completely unrelated to your work but I thought I would share it. In a nutshell, great success indeed! 😀


Update virtual-machines-windows-guidance-compute-single-vm.md

Fixing typos.

Hi @alexandair, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@alexandair : Thanks for your contribution to the Azure documentation! The author, @mikewasson, has been notified to review your proposed change.

The text in square brackets doesn't appear in the rendered topic.
#please-close

That's true. But, why should have a typo in a Markdown text if it can be easily fixed. :)


Programmatically changing invalid value to empty/null value does not clear value in UI

Description
If a user inputs an invalid value (eg: "asdfasdf") and then you try to programmatically clear the value (set the value to null or datePicker.getEmptyValue()), the value in the text field does not change and remains as the original, invalid value (eg: "asdfasdf").
Steps to reproduce

From the UI, input an invalid string into the date picker (eg: "asdf")
In the code, attempt to clear the field: datePicker.setValue(datePicker.getEmptyValue()) or datePicker.setValue(null)

Expected outcome
Value in the field should change to empty.
Actual outcome
Value in the field does not change at all and still shows the original, invalid input.
Example

   	 	DatePicker dp = new DatePicker();
   	 	dp.setValue(LocalDate.now());
   	 	Button btn = new Button("Clear", e -> dp.setValue(dp.getEmptyValue()));
   	 	add(dp, btn);

Environment
Vaadin 14.1.17
Pure Java environment

Still an issue with DatePickerFlow 2.2.0 (Vaadin 14.4.0)


inlineStr cell type support #1575

Summary

Implementing inlineStr cell type fixing issue #1575
Test plan

Tested stream reading of the xlsx file that has cells defined as <c ... t="inlineStr"><is><t>value here</t></is></c> - values gets populated, instead of null values before the fix.

Could you please add a new test with that test file to make sure we don't lose this functionality over time?

Could you please add a new test with that test file to make sure we don't lose this functionality over time?

@alubbe, added integration test with the sample file.

@alubbe, added integration test with the sample file.

@Siemienik, could you please review and merge this PR?

Yes, I will if only I found free time.

When will this be released?

when will this be release, because right now in "4.3.0" also this fix is not present. We are getting the inlineStr cell as "NULL", please make a small release for this issue, if possible... Currently we are using the npm release version. Do we have to pull from github directly and then use the fix, or will you be making a release in npm also ?

@Siemienik please release a new version with this fix

@adrian-morariu-modus-create see #2351 ,


rafthttp: TestTransportErrorc fails

--- FAIL: TestTransportErrorc (0.06s)
	transport_test.go:153: cannot receive error from errorc

https://semaphoreci.com/coreos/etcd/branches/pull-request-5265/builds/3

Duplicates #5210?

Right. Closing. Thanks!


Added react-styling to FAQ

The corresponding issue:
https://github.com/FormidableLabs/radium/issues/162#issuecomment-121193028

@ianobermiller Ok, I've made the changes and repushed. If I missed something let me know.

@ianobermiller By the way, I've just implemented support for quotes in CSS syntax style values. So I can add quotes to the first CSS example if you'd like it better.

Why would you need quotes in CSS syntax style values? Can you show an example?
How come &:first require an ampersand, but :hover doesn't?

Let's remove the second example to keep it concise, and just link to react-styling for more examples and information. Also, can you update the comparison doc to indicate that radium supports CSS syntax when using react-styling?

@ianobermiller made the push: faq and comparision


[Question]: I want to share an instagram post with my app.

What is your question?
I see that this package is helpful in sharing content from your application externally.
My use case is to share external content with my app. For example i want to share an instagram reel using share button in instagram and use it inside my flutter application.
Checklist before submitting a question

[X] I searched issues in this repository and couldn't find such bug/problem
[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I am using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

The share_plus plugin can help you with that. The README contains some information regarding Meta apps (e.g. Instagram).


Add clamped vector polylines

Opening as a draft to make sure things are in their place before adding specs.

Moves decodeVectorPolylinePositions logic to its own file in Core
Adds examineVectorLinesFunction and minimumMaximumVectorHeights properties to Cesium3DTileset
Adds the Vector3DTileClampedPolylinesclass
Adds logic for floating vs clamped polylines to Vector3DTileContent
Adds vert and frag shaders for clamped polylines
Adds a worker for creating clamped polylines

Thanks for the pull request @ebogo1!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I removed the unused property in Cesium3DTileset, marked the callback as @experimental, and renamed CornerIds + shader variables in a2ac850. Do you think any of the other changes are in scope for this PR?

@likangning93 had some minor changes for CI to pass but should be ready now. I added the examine callback function as an option for the tileset constructor along the way.

@ebogo1 you mentioned it above, but make sure to address https://github.com/CesiumGS/cesium/pull/9399#discussion_r586419097 soon because otherwise polylines won't be clamped at all.

Is there a sandcastle that we could play with? Screenshots? Maybe we can tile some non-customer data. @likangning93 do you know if we have any data like that?
Normally I would also suggest a new official sandcastle example but given that this is for the older vctr format I don't think we need one. However we should add a vector tile polylines (clamped) option to the Development/Picking sandcastle to easily test the picking behavior.
Also, we should have units tests for the new behavior.

The code is currently crashing because the startFaceNormalAndVertexCorners property rename was not applied to createVectorTileClampedPolylines.js. Just to reiterate a point, it's always a good idea to be testing new features with a sandcastle example of some sort to catch mistakes like this (unit tests being the other line of defense).
Here's a sandcastle I put together for testing: Sandcastle

What's interesting is that even after that problem is fixed there's still some issue where the polylines don't show up at all. Is it because of our usage of ApproximateTerrainHeights and the area being flat on the ocean?

This one's kind of random, but in https://github.com/CesiumGS/cesium/pull/8726 I had to render shadow volumes with premultiplied alpha blending instead of regular alpha blending since alpha blending against a black framebuffer like the globe translucency framebuffer would result in darker colors than normal. The same sort of change needs to happen here - I pushed the change: https://github.com/CesiumGS/cesium/pull/9398/commits/0351120f0763b88677d20326cdcb31e2cc05e1fc.
This is what I was starting to test in the comment above. The commented out lines will enable globe translucency.
I think similar changes will be needed in https://github.com/CesiumGS/cesium/pull/9399 as well and I'll look at that once the changes here are confirmed to work.

What's interesting is that even after that problem is fixed there's still some issue where the polylines don't show up at all. Is it because of our usage of ApproximateTerrainHeights and the area being flat on the ocean?

False alarm, the sandcastle was wrong. classificationType: Cesium.ClassificationType.CESIUM_3D_TILE should have been classificationType: Cesium.ClassificationType.TERRAIN.
Updated sandcastle

Can confirm clamping behavior is working on Cartersville TIN mesh after 4668ca6

I realized I had to make some adjustments to the premultiplied alpha code because it wasn't taking into account the fact that the batch table overwrites gl_FragColor. I pushed the changes in https://github.com/CesiumGS/cesium/pull/9398/commits/7ada1a79c6529d17236b4211cacc84dab76ab583. This also makes b3dm classification tileset use premultiplied alpha which was missed in https://github.com/CesiumGS/cesium/pull/8726.
These are the sandcastles I used for testing:
vctr-sandcastle, b3dm-classification-sandcastle, geom-sandcastle

Pushed some specs for the new code, based on Vector3DTilePolylineSpec. I used xit for now since the rendering is failing due to a bug I found:

When viewing a clamped polyline tileset from above, artifacts like this begin to appear. I don't believe this is related to different LODs, and it happens both in Chrome and FF. This behavior doesn't occur with regular polylines with clampToGround = true.

When viewing a clamped polyline tileset from above, artifacts like this begin to appear. I don't believe this is related to different LODs, and it happens both in Chrome and FF. This behavior doesn't occur with regular polylines with clampToGround = true.

Here's the relevant chunks of Vector3DTilesClampedPolylines:
import CullFace from "./CullFace.js";

//...

function getRenderState(mask3DTiles) {
  return RenderState.fromCache({
    cull: {
      enabled: true, // prevent double-draw. Geometry is "inverted" (reversed winding order) so we're drawing backfaces.
      face: CullFace.FRONT
    },

I don't know why this is the case though, since the geometry code in the vertex shader and the indices for each volume should basically be creating "inside-out" geometry already.
This also doesn't seem to be a complete fix, so there might still be something else at play. Maybe something's also depth-testing where it shouldn't.
Here's the Sandcastle I'm testing with

There might also be something about the CullFace.FRONT thing combining with clamping the "min depth" of the polyline volumes to about -1000 (the value it's getting from ApproximateTerrainHeights right now seems to be -100000) also producing better results, but... that's yet another mystery.

Investigating  "When viewing a clamped polyline tileset from above, artifacts like this begin to appear."
I made some shader and render state changes off 6e4d7ef to try to get to the bottom of these, resulting in the two commits below. Here's the Sandcastle I used for testing.

fix clamped vector polylines not drawing when camera is inside volume by culling front faces da38f78

The algorithm we're using to draw clamped line segments does something like:

draw a "decal" that covers the whole onscreen area the line segment is likely to cover onscreen. Conceptually this is a little bit like a shadow volume, except it doesn't involve stencil buffers etc.
for each fragment in the decal, figure out if that fragment is part of the line segment

The goal is to draw the "inside" faces of the volume instead of "outside," so that when the camera enters the volume it should still see the decal instead of backface-culling it all.
The diagrams and REFERENCE_INDICES in createVectorTileClampedPolylines.js indicate that we try to use winding order to accomplish this "inside-drawing," but for some reason that doesn't seem to work. I simplified the vertex shader for clamped vector polylines to make the volumes a little easier to grok, and noticed that when we crash through the surface of the volume, the volume (and therefor the clamped polyline) is no longer drawn:

In other words, we were drawing front/outside faces, not back/inside faces. Flipping the face culling (or reversing the indices in the geometry) fixes the problem, but I still don't fully understand why the geometry is drawing front/outside faces in the first place.
Here's a patch for further investigation:
investigateFaceFlip6e4d7ef.patch.zip

use bounding volume that covers whole shadow volume for draw commands in Vector3DTileClampedPolylines 6602501

With face-flipping turned on and no other changes, "smaller" chunks of the polyline were still missing. Moving the camera along the line segment caused the artifacts to "slide" instead of staying where they can't hurt us.

This looked a little like parallax to me, so I switched the debug bounding volumes back on. Lo and behold! Even drawing back/inside faces correctly (as evidenced by the "sides" of the current volume being visible), the bottom of the volume wasn't drawing, hence the lack of classification!

Now, this was drawing using the actual-size shadow volumes, which go something like -100,000 meters below and 9,000 meters above the ellipsoid in this area.
I noticed that the draw command bounding volumes though were using the 3D Tile's bounding sphere, not its enormously deep and tall bounding volume. I think Cesium was using those "shallow" bounding spheres to compute the far plane for the top-down view. As a result the bottom part of the shadow volume was getting clipped by the depth plane, since in the top-down view it's far from the shallow now. Updating the draw command to use a bounding volume based on the shadow volume seems to fix that problem.
Side-note, I also noticed that czm_depthClamp (depthClamp.glsl) doesn't do anything when the renderer is in log-depth mode, which was also a helpful observation pointing at depth clipping being the problem.

With some more help from @likangning93 I was able to get rendering and picking specs to pass as well. I think this is good for another round of review!

I renamed noClassificationModels to vectorClassificationOnly and marked it as @experimental since other vctr-related properties are also marked as experimental.
Make sure to do the same rename in SC once the newer version of CesiumJS is pulled in.

I also left a comment above: https://github.com/CesiumGS/cesium/pull/9398#pullrequestreview-602167702

By the way, excellent detective work @likangning93

Thanks @ebogo1 @likangning93 !


How to make a GET request to server and get response code and response body separately

Hello, I need to make a GET request to server and get response code and response body separately.
How can I do that?
https://stackoverflow.com/questions/25414324/get-response-code-and-response-body-ina-a-single-request-using-http-request

calling HttpRequest.body() and HttpRequest.code() needs to be placed inside of an ansyctask, so how can i call them both if that's the case?

calling HttpRequest.body() and HttpRequest.code() needs to be placed inside of an ansyctask, so how can i call them both if that's the case?

I'm not sure I understand your question, can you include a code snippet of what you are trying to do or what isn't working for you?

when i call HttpRequest.body() or HttpRequest.code() directly, it causes NetworkOnMainThread

Yes, you need to put it in a separate thread (AsyncTask/Service), different
than main/UI thread. It's a Android rule.
2015-08-21 0:33 GMT-03:00 rsbulanon<EMAIL_ADDRESS>
when i call HttpRequest.body() or HttpRequest.code() directly, it causes
NetworkOnMainThread
—
Reply to this email directly or view it on GitHub
https://github.com/kevinsawicki/http-request/issues/86#issuecomment-133267942
.

--
Marcelo Quinta
-----------------------------@mrquinta

Yeah i'm aware that i need to put it inside of an AsyncTask, but my question is, how can i get the status code and body at once. It seems that i need to provide two different asynctask because .code() returns integer and .body() returns String.


Show topic on summary

https://trello.com/c/5tAUflyY/331-show-current-taxons-for-a-document
This adds the ability to see the current topics for a document on the summary page. We extended the TopicsService to allow us to get the current topics, which meant doing some renaming to keep the purpose of the methods clear. We also cope with the Publishing API being down or slow.
We have some duplication of stubs in the tests, but I don't think it's enough to get a clear refactoring out of it. I'm expecting the final piece of work - to enable editing of topics - will involve revisiting these specs, rather than creating new ones, so it seems unlikely the duplication will spread.

@kevindew I think I've responded to everything here. This is a branch off #422, but I can't see anything that's leaked onto this one. Was there something in particular that looked anomalous?


fix pip8 warnings

Signed-off-by: Hiroshi Miura<EMAIL_ADDRESS>

@brosner @paltman Can this be merged?


IOS Core Data relationships support

Some time ago, you said there were no plans to support relationships on the client. Is there already been any change in plans ? I'd like to use Azure mobile services but not supporting relationships between tables limits very much the use of any advanced DB model.

I am having the same concerns. Looking forward to see what are your solutions for this.

Relationship support is planned, and is an ongoing work item, with the main blocker at the moment being getting support on the server to accept batched changes.  (so we can send the parents, children, etc in one server transaction without violating those constraints)
Depending on what relationships you need, there are ways we can get support for them now. Mainly if you only need to deal with 1:1 or 1:N relationships.
Technically nothing (is supposed) to stop them from being used on the client side if your server data model can deal with each table being synced by itself.  We have a bug atm that really needs fixed that is breaking the push action here.
If you let me  know what relationship types you are dealing with and main needs, I can see if there are some short term workarounds that may work for you.  (This would probably involving having a custom MSCoreDataStore to hide those from our SDK atm)

I also need to resolve 1:1 and 1:N relationship.
Thanks.
Sent from my iPhone

On 30-Sep-2015, at 9:36 PM, Phillip Van Nortwick<EMAIL_ADDRESS>wrote:
Relationship support is planned, and is an ongoing work item, with the main blocker at the moment being getting support on the server to accept batched changes. (so we can send the parents, children, etc in one server transaction without violating those constraints)
Depending on what relationships you need, there are ways we can get support for them now. Mainly if you only need to deal with 1:1 or 1:N relationships.
Technically nothing (is supposed) to stop them from being used on the client side if your server data model can deal with each table being synced by itself. We have a bug atm that really needs fixed that is breaking the push action here.
If you let me know what relationship types you are dealing with and main needs, I can see if there are some short term workarounds that may work for you. (This would probably involving having a custom MSCoreDataStore to hide those from our SDK atm)
—
Reply to this email directly or view it on GitHub.

1:1 relationships are easiest to handle by having the Client <-> Server treat it as one object.  Then in your table scripts on the server you actually separate it back out.
For 1:N, again the simplest is if you can get away with having them as one entity on the client.
Given you want to work with the model on the client the next question is, can your server handle inconsistent states or not (i.e is Parent allowed to point to a missing child, etc)  If so, you can just run things as they are.
In the more likely event that is not acceptable, the next step would involve customizing the action taken on push (via the delegate's per operation method) and/or making a custom MSCoreDataStore, whose upsert & read methods can separate & combine the item when dealing with the parent object.
It's a little hard to fully explain here, I'll see I can get a couple hours to whip up a simple prototype.
What backend language are you working in (Node.js or Managed)?

I am using Node.js, I am not worried about backend because this article
http://blogs.msdn.com/b/carlosfigueira/archive/2013/08/23/complex-types-and-azure-mobile-services.aspx
explains it very nicely. I need help/sample for iOS.
On Sat, Oct 3, 2015 at 3:29 AM, Phillip Van Nortwick <
<EMAIL_ADDRESS>wrote:

1:1 relationships are easiest to handle by having the Client <-> Server
treat it as one object. Then in your table scripts on the server you
actually separate it back out.
For 1:N, again the simplest is if you can get away with having them as one
entity on the client.
Given you want to work with the model on the client the next question is,
can your server handle inconsistent states or not (i.e is Parent allowed to
point to a missing child, etc) If so, you can just run things as they are.
In the more likely event that is not acceptable, the next step would
involve customizing the action taken on push (via the delegate's per
operation method) and/or making a custom MSCoreDataStore, whose upsert &
read methods can separate & combine the item when dealing with the parent
object.
It's a little hard to fully explain here, I'll see I can get a couple
hours to whip up a simple prototype.
What backend language are you working in (Node.js or Managed)?
—
Reply to this email directly or view it on GitHub
https://github.com/Azure/azure-mobile-services/issues/810#issuecomment-145170339
.

--
Attiqe Ur Rehman

@phvannor any sample prototype ?
-A

tracking now at: https://github.com/Azure/azure-mobile-apps-ios-client/issues/30

@attiqeurrehman i Never got a chance to really work on any prototype yet.  I did put together half of what will be needed here: https://github.com/phvannor/azure-mobile-apps-ios-client/commit/9065be3c4e45b9c586871f5022305f35b0347d8b
Once in, that will allow an easy solution to the pull half (assuming your dont have cycles / can live ok w/portions of records) but leaves the push half left undone.
Closing this issue, as the ios-client will be the main repo going forward for this.

Even the simplest of backends need core data relationships. Can you please tell me how can I make this work? One solution I see is that I create independent tables with foreign key/primary keys concept and then do the same in Core Data. OfCourse it breaks the essence of Core Data but is it ok to go forward with that solution?
Please update me on this.
Thanks


Added go-e for device go-eCharger

Ursprünglich für Request #852

Hello, Why the automated scripts are not starting here :(
https://adapter-check.iobroker.in I passed here (except E802, E801), but is there in my repo Topics and About text.

RE-CHECK!

Automated adapter checker
ioBroker.go-echarger

[ ] :heavy_exclamation_mark: [E020] Name of adapter in package.json must be lowercase and be equal to "iobroker.go-echarger". Now is "undefined"
[ ] :heavy_exclamation_mark: [E103] common.name in io-package.json must be equal to "go-echarger". Now is go-e
[ ] :heavy_exclamation_mark: [E200] Not found on npm. Please publish
[ ] :heavy_exclamation_mark: [E300] Not found on travis. Please setup travis
[ ] :heavy_exclamation_mark: [E801] No repository about text found. Please go to "https://github.com/MK-2001/ioBroker.go-echarger", press the first "Edit" button you will find on the page and add the description.
[ ] :heavy_exclamation_mark: [E802] No topics found in the repository. Please go to "https://github.com/MK-2001/ioBroker.go-echarger" and press Manage topics
[ ] :eyes: [W400] Cannot find "go-echarger" in latest repository

ioBroker.go-e

[ ] :heavy_exclamation_mark: [E801] No repository about text found. Please go to "https://github.com/MK-2001/ioBroker.go-e", press the first "Edit" button you will find on the page and add the description.
[ ] :heavy_exclamation_mark: [E802] No topics found in the repository. Please go to "https://github.com/MK-2001/ioBroker.go-e" and press Manage topics
[ ] :eyes: [W400] Cannot find "go-e" in latest repository

Add comment "RE-CHECK!" to start check anew

RE-CHECK!

Automated adapter checker
ioBroker.go-echarger

[ ] :heavy_exclamation_mark: [E020] Name of adapter in package.json must be lowercase and be equal to "iobroker.go-echarger". Now is "undefined"
[ ] :heavy_exclamation_mark: [E019] Invalid repository URL: https://github.com/MK-2001/ioBroker.go-e. Expected: git+https://github.com/MK-2001/ioBroker.go-echarger.git
[ ] :heavy_exclamation_mark: [E103] common.name in io-package.json must be equal to "go-echarger". Now is go-e
[ ] :heavy_exclamation_mark: [E200] Not found on npm. Please publish
[ ] :heavy_exclamation_mark: [E300] Not found on travis. Please setup travis
[ ] :heavy_exclamation_mark: [E801] No repository about text found. Please go to "https://github.com/MK-2001/ioBroker.go-echarger", press the first "Edit" button you will find on the page and add the description.
[ ] :heavy_exclamation_mark: [E802] No topics found in the repository. Please go to "https://github.com/MK-2001/ioBroker.go-echarger" and press Manage topics
[ ] :eyes: [W400] Cannot find "go-echarger" in latest repository

ioBroker.go-e

[ ] :heavy_exclamation_mark: [E801] No repository about text found. Please go to "https://github.com/MK-2001/ioBroker.go-e", press the first "Edit" button you will find on the page and add the description.
[ ] :heavy_exclamation_mark: [E802] No topics found in the repository. Please go to "https://github.com/MK-2001/ioBroker.go-e" and press Manage topics
[ ] :eyes: [W400] Cannot find "go-e" in latest repository

Add comment "RE-CHECK!" to start check anew

RE-CHECK!

Automated adapter checker
ioBroker.go-echarger

[ ] :heavy_exclamation_mark: [E020] Name of adapter in package.json must be lowercase and be equal to "iobroker.go-echarger". Now is "undefined"
[ ] :heavy_exclamation_mark: [E019] Invalid repository URL: https://github.com/MK-2001/ioBroker.go-e. Expected: git+https://github.com/MK-2001/ioBroker.go-echarger.git
[ ] :heavy_exclamation_mark: [E103] common.name in io-package.json must be equal to "go-echarger". Now is go-e
[ ] :heavy_exclamation_mark: [E200] Not found on npm. Please publish
[ ] :heavy_exclamation_mark: [E300] Not found on travis. Please setup travis
[ ] :heavy_exclamation_mark: [E801] No repository about text found. Please go to "https://github.com/MK-2001/ioBroker.go-echarger", press the first "Edit" button you will find on the page and add the description.
[ ] :heavy_exclamation_mark: [E802] No topics found in the repository. Please go to "https://github.com/MK-2001/ioBroker.go-echarger" and press Manage topics
[ ] :heavy_exclamation_mark: [E812] file test/ found in repository, but not found in .npmignore
[ ] :heavy_exclamation_mark: [E815] file .travis.yml found in repository, but not found in .npmignore
[ ] :heavy_exclamation_mark: [E816] file tsconfig.json found in repository, but not found in .npmignore
[ ] :eyes: [W400] Cannot find "go-echarger" in latest repository

ioBroker.go-e

[ ] :heavy_exclamation_mark: [E801] No repository about text found. Please go to "https://github.com/MK-2001/ioBroker.go-e", press the first "Edit" button you will find on the page and add the description.
[ ] :heavy_exclamation_mark: [E802] No topics found in the repository. Please go to "https://github.com/MK-2001/ioBroker.go-e" and press Manage topics
[ ] :eyes: [W400] Cannot find "go-e" in latest repository

Add comment "RE-CHECK!" to start check anew

Was muss ich machen, damit der alte Name iobroker.go-echarger nicht mehr gefunden wird? Der Name ist nicht mehr in Verwendung und musste bei Norm zu Go-e geändert werden.

Name in der io-Package und Package.json ändern

Name in der io-Package und Package.json ändern

Am einfachsten wäre mit Adapter creator neuen Adapter erstellen mit richtigen Namen, Code übernehmen alten Name aus repo löschen

Ich habe das mal nun so getan. ich habe keine einzige Codezeile ausbessern können.
 Wenn ich das RePo nochmals neu Forken muss, mache ich da auch gerne, aber unter Files in diesem Merge wird ersichtlich, dass nur noch der go-e enthalten ist.

Dutchman hatte mir das so gesagt.Und meinte da wäre noch viel zu tun.Hat aber auch angeboten über any ne sitzung zu machen und uns das zu zeigen.

RE-CHECK!

Automated adapter checker
ioBroker.go-e

:thumbsup: No errors found

[ ] :eyes: [W400] Cannot find "go-e" in latest repository

ioBroker.go-echarger

[ ] :heavy_exclamation_mark: [E020] Name of adapter in package.json must be lowercase and be equal to "iobroker.go-echarger". Now is "undefined"
[ ] :heavy_exclamation_mark: [E019] Invalid repository URL: https://github.com/MK-2001/ioBroker.go-e. Expected: git+https://github.com/MK-2001/ioBroker.go-echarger.git
[ ] :heavy_exclamation_mark: [E103] common.name in io-package.json must be equal to "go-echarger". Now is go-e
[ ] :heavy_exclamation_mark: [E200] Not found on npm. Please publish
[ ] :heavy_exclamation_mark: [E300] Not found on travis. Please setup travis
[ ] :eyes: [W400] Cannot find "go-echarger" in latest repository

Add comment "RE-CHECK!" to start check anew

Geschlossen, da ich ohne ein ReBase den Fehler zum veralteten Namen nicht weg bekommen habe. Neu: #867
(Die Analyse der repo-scripts und das checker-tool von Böuefox war echt nicht leicht.. ;-) )


Updated README to link to new rvm.io website.

Simple documentation update. Thanks for your hard work, everyone.

Hi @smartperson,
Thanks for your making your first contribution to Cucumber, and welcome to the Cucumber committers team! You can now push directly to this repo and all other repos under the cucumber organization! 🍾
In return for we ask you to:

✅ Please continue to use branches and pull requests. When someone on the core team approves a pull request (yours or someone else's), you're welcome to merge it yourself.
💚 Commit to setting a good example by following and upholding our code of conduct in your interactions with other collaborators and users.
💬 Join the community Slack channel to meet the rest of the team and make yourself at home.
ℹ Don't feel obliged to help, just do what you can if you have the time and the energy.
🙋 Ask if you need anything. We're looking for feedback about how to make the project more welcoming, so please tell us!

On behalf of the Cucumber core team,
Aslak Hellesøy
Creator of Cucumber

Fixes #49!


Tensorflow GPU Instructions should be updated for TF 2.5 and CUDA 11.2

URL(s) with the issue:
https://www.tensorflow.org/install/gpu#windows_setup
https://github.com/tensorflow/docs/blob/master/site/en/install/gpu.md
Description of issue (what needs changing):
TensorFlow 2.5 is built against CUDA 11.2 and cuDNN 8.1.0. However, the GPU instructions still refer to CUDA 11.0 and cuDNN 8.0.4. I believe that for the sake of clarity these should be updated to match TF 2.5. This includes both the installation commands for Linux and the path commands for Windows.
Submit a pull request?
I'd be glad to submit a PR for the windows instructions, but I don't currently have access to a machine I can use to verify the Linux steps.

I just refreshed 3 machines on Ubuntu 20.04 to run machine learning using tf.  I noticed when installing tf that we are now version 2.5.  I made a specific check on tf web site to determine cuda and cudnn versions to install.  All machines have dual GPU and getting them running in tf is very dependent on the right cuda/cudnn.
You wasted my time by NOT updating GPU instructions - in fact the page I found shows that 2.4 and 2.5 still want 8/11.

@TylerADavis
The GPU page has been updated with latest information on test build configurations, kindly move this to closed status as resolved.

@Saduf2019 Which page is it that got updated? While I can see that the GPU tested configurations reference CUDA 11.2 and cuDNN 8.1, the GPU install page still references CUDA 11.0 and cuDNN 8.0, both on github and the live site

This issue should not be closed yet. It has been partially addressed by #1900, but not fully addressed yet.

Moving this issue to closed status as PR is merged.

The PR https://github.com/tensorflow/docs/pull/1900 did not solve this issue.  The installation instructions still refer to out-of-date libraries.  Section https://www.tensorflow.org/install/gpu#install_cuda_with_apt instructions still refer to CUDA 11.0, not 11.2 as the first half of docs specify.
This: https://github.com/tensorflow/tensorflow/issues/49855#issue-905015666 is currently the only source of how to install the proper libnvinfer libraries.  It needs to be added to the gpu.md page install_cudo_with_apt instructions.


Error using Pode with IIS as Reverse proxy in DotnetCore hosting module

When using a Pode Server in IIS like we use Asp.Net Core applications with out of process hosting, I encounter the following error:
In browser
HTTP Error 502.5 - ANCM Out-Of-Process Startup Failure
In logs
Exception setting "TreatControlCAsInput": "There is no console."
At D:\dev\Pode\src\Public\Core.ps1:134 char:13
+             [Console]::TreatControlCAsInput = $true
When I disable this line everything works okay.
Steps To Reproduce

Install IIS or IIS Express
Install DotnetCore Windows Hosting (choco install dotnetcore-windowshosting -y)
Create website in IIS and set physical folder to dir with pode server script and add web.config file with contents

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <location path="." inheritInChildApplications="false">
    <system.webServer>
      <handlers>
        <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
      </handlers>
      <aspNetCore processPath="pwsh.exe" arguments=".\webpages.ps1" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" hostingModel="OutOfProcess"/>
    </system.webServer>
  </location>
</configuration>

Update Pode\examples\web-simple-pages.ps1 with detecting ASPNETCORE port and address

	$port = 8090
	$address = 'localhost'
	# detect if running in IIS dotnet core app-pool
	if ($env:ASPNETCORE_PORT)
	{
	    $port = $env:ASPNETCORE_PORT
	    $address = '<IP_ADDRESS>' # localhost not working
	}

	Add-PodeEndpoint -Address $address -Port $port -Protocol Http # replace line

Suggested fixes
1: Add to function Start-Server -Type IIS-Hosting and change Core.Ps1 line 132 with checking ServerType and don't set TreatControlCAsInput
        # set it so ctrl-c can terminate, unless serverless
        if (!$PodeContext.Server.IsServerless) {
            [Console]::TreatControlCAsInput = $true
        }

2: Quick fix ignore error in try/catch or detect no console

Hey @ehagen,
I've managed to reproduce the same error you're getting, though once commented out the page for me still fails to load - but with no errors. I don't know if there was anything else you also did to make the pages load?
The errors do go away though once [Console]::TreatControlCAsInput = $true is removed.
For the fix, I'm thinking of either:

An -IIS switch on Start-PodeServer. or
We could check if $env:ASPNETCORE_PORT (or $env:APP_POOL_CONFIG) is present internally, and flag the server as being hosted by IIS automatically

There does appear to be a fair few environment variables that only exist when hosted by IIS, so checking for these could be more ideal 🤔
On another note, having the steps on how to host Pode via IIS is really cool! So if you're ok with it, and we can get this working, I could also use these steps to add into Pode's docs.

I have attached my sample to this comment. Put it into the repo samples folder and change the web.config to point to 'web-static2.ps1'. Don't use a folder inside the c:\inetpub folder (security issues). See the samples\logs folder for issues.
web-static2.ps1.txt
Would be nice if you added this as a standaard option.

Just one more remark: You need to start your site with type Pode, a lot of the samples don't do this.
Start-PodeServer -Type Pode -Threads 2

Yep, adding -Type Pode worked! Interesting, there must be something that HttpListener is doing to block the requests 🤔
As for the -Type Pode, this is Pode's pure powershell web server which allows xplat HTTPS support. If you don't supply the type then HttpListener is used as default - which is why the majority of the samples don't specify the type unless HTTPS is required. But in this case, it would appear to be needed!
As for the fix, I'll make it so Pode checks for the existence of the $env:ASPNETCORE_PORT environment variable. If it exists, then [Console]::TreatControlCAsInput = $true will be skipped.

Just for the record. A webserver based on http.sys (Like System.Net.HttpListener) is not supported in an ASP.NET Core Module (see https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-3.1)
This is why we can only use Start-PodeServer -Type 'Pode'.
Did you check the query string handling of PodeServer. Things like
Add-PodeRoute -Method Get -Path '/api/diag' -ScriptBlock {
    param($e)
    if ($e.Query -ne $null)
    {
        if ($e.Query.ContainsKey('id'))
        {
           # do something with id
        }
    }
    Write-PodeJsonResponse -Value "{`"result`" : `"true`"}]"
}

are not working anymore

Aah, that makes sense!
As for the query strings, it seems on the PodeServer it's being left as a NameValueCollection - rather than been converted to a HashTable. The first query anme/value pair is also a little weird at times, where the key could contain the ?.
I haven't tested everything running from IIS yet - I'll do that as a part of this - but since the query string logic appears to be separately broken, I'm going to move that to it's own issue.

That above commit works with IIS, I did some extra testing as well and query strings now also appear to be working.
I've also made it so that Add-PodeEndpoint will default to using $env:ASPNETCORE_PORT as the -Port (if not supplied) when Pode detects it's running under IIS. Also, the -Type on Start-PodeServer is set to Pode when under IIS.
So you can now just do the following, and the Server Type and Endpoint Port are defaulted:
Start-PodeServer -Threads 2 {
    Add-PodeEndpoint -Address '<IP_ADDRESS>' -Protocol Http

   # routes, auth, etc
}

I checked the commit and it's working.
Maybe it's nice to modify function Add-PodeEndpoint $Address to '<IP_ADDRESS>' when inIIS to prevent required '<IP_ADDRESS>' in address. This also prevents the 'Must be running with administrator privileges to listen on non-localhost addresses' error if you changed it before the check.
This would be working when running in IIS and as stand-alone
Add-PodeEndpoint -Protocol Http
and
Add-PodeEndpoint -Address * -Protocol Http
I have still some issues with the PodeServer using Get-PodeSessionMiddleware (Sessions.Store is null or $e.Session is null) / Authentication but this has nothing to do with IIS hosting but more with difference between Webserver and PodeServer

Something I'm also going to do is force the Port to be ASPNETCORE_PORT regardless, when in IIS and the protocol is HTTP/HTTPS.
One thing I did manage to get working though was it listening on hostnames - so localhost or test.pode.com etc. For the test.pode.com for example, I had to supply -Force to Add-PodeEndpoint, but I could use SNI in IIS 🤔. One idea could be to check if the Address is local or a hostname and skip the Admin check when running as IIS?
I also got HTTPS working too; IIS deals with all the certs and SSL streams, so we can leave Pode on a normal HTTP endpoint.
On the Authentication and Sessions, I just tried these in IIS, and outside of IIS, and both worked - with both Web/Pode server types as well. I imagine you mean Enable-PodeSessionMiddleware, and by the looks of it you're setting a custom Storage? Outside of the two server types, everything else is pretty much identical - the only real difference in the server types is the Request/Response parsing.
Feel free to raise an issue for it though, in case it is a problem!

Did a bit more playing and I agree, under IIS:

the Address will be forced to <IP_ADDRESS>
the Port will be forced to ASPNETCORE_PORT
the server Type will be forced to Pode
the endpoint Protocol will be forced to HTTP (as IIS deals with all HTTPS)

So even if you had the below to run locally, under IIS it'll still work:
Start-PodeServer -Threads 2 {
    Add-PodeEndpoint -Address <IP_ADDRESS> -Port 8080 -Protocol Http

    # etc
}

Top, I give it a try

Maye it's nice to add the IIS Authenticated user from the Request and surface it in Pode
$Win32CloseHandle = Add-Type -Name Win32CloseHandle -PassThru -MemberDefinition @'
    [DllImport("kernel32.dll", SetLastError = true)]
    public static extern bool CloseHandle(IntPtr handle);
'@

in Invoke-PodeSocketHandler for example

        if ($WebEvent.Request.Headers.ContainsKey('MS-ASPNETCORE-WINAUTHTOKEN'))
        {
            $winAuthToken = [System.IntPtr][Int]"0x$($WebEvent.Request.Headers['MS-ASPNETCORE-WINAUTHTOKEN'])"
            $winIdentity = New-Object System.Security.Principal.WindowsIdentity($winAuthToken, 'Windows')
            $Win32CloseHandle::CloseHandle($winAuthToken)
            Write-Host "user: $($winIdentity.Name) type: $($winIdentity.AuthenticationType)"
        }

For details see
IIS midlleware
https://github.com/dotnet/aspnetcore/blob/f6c3f9e02ab7c4ae5c395245f2792ba18c33075a/src/Servers/IIS/IISIntegration/src/IISMiddleware.cs line 164
And maybe it's nice to add the email address to the (Windows)User (also in Add-PodeAuthWindowsAd) like
$windowsIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()
$sidbind = "LDAP://<SID=" + $windowsIdentity.user.Value.ToString() + '>'
$MailAddress = ([ADSI]$sidbind).mail.tostring()

Lots of times I need user & email :)

The first part should be OK, as it'll only be on Windows for IIS. Something like $WebEvent.IIS.User with Name and Type properties?
For the Windows AD and Email, that's definitely possible - I'll make it apart of #474 to include the user's email :)
For the example you've put, is that apart of the IIS user logic? (So get the Name, Type, and Email?)

<<is that apart of the IIS user logic
Standard is getting the WindowsIdentity, which gives you the authenticated User if available. The rest is extra and up to the developer but very nice to have. So you can surface the Identity and the Email for IIS. To keep everything standard in all auth providers surface Name, Type and Email with optionally Identity if in IIS.

Since this is about authentication, it sounds like it could be best as a new authentication type, something like:
New-PodeAuthType -IIS | Add-PodeAuthWindowsAd -Name 'Auth' -IIS

The New-PodeAuthType -IIS checks for the MS-ASPNETCORE-WINAUTHTOKEN header and returns a 401 if not present. Otherwise, it's passed to Add-PodeAuthWindowsAd that runs similar logic to yours above, and sets the web event's Auth.User to the same as what the current LDAP WindowsAd does:
$Win32CloseHandle = Add-Type -Name Win32CloseHandle -PassThru -MemberDefinition @'
    [DllImport("kernel32.dll", SetLastError = true)]
    public static extern bool CloseHandle(IntPtr handle);
'@

try {
    $winAuthToken = [System.IntPtr][Int]"0x$($IISToken)"
    $winIdentity = New-Object System.Security.Principal.WindowsIdentity($winAuthToken, 'Windows')
    $adUser = [ADSI]"LDAP://<SID=$($winIdentity.User.Value.ToString())>"

    return @{
        User = @{
            AuthenticationType = $winIdentity.AuthenticationType
            DistinguishedName = @($adUser.distinguishedname)[0]
            Username = ($winIdentity.Name -split '\\')[-1]
            Name = @($adUser.name)[0]
            Email = @($adUser.mail)[0]
            Fqdn = $Server
            Domain = ($winIdentity.Name -split '\\')[0]
            Groups = $groups
        }
    }
}
finally {
    $Win32CloseHandle::CloseHandle($winAuthToken)
}

^ something along these lines could work.

I've created a new Add-PodeAuthIIS function - this is just a standalone function that sets up a custom authentication to parse for the AUTHTOKEN header. It has a similar makeup to Add-PodeAuthWindowsAd, and the User object in $e.Auth is the same.
If the AUTHTOKEN is missing a 401 is returned. I've managed to test it a little for both Local and AD users.
Start-PodeServer {
    Add-PodeEndpoint -Address <IP_ADDRESS> -Protocol Http

    Add-PodeAuthIIS -Name 'IISAuth'

    Add-PodeRoute -Method Get -Path '/test' -Middleware (Get-PodeAuthMiddleware -Name 'IISAuth') -ScriptBlock {
        param($e)
        Write-PodeJsonResponse -Value @{ User = $e.Auth.User }
    }
}

(I've also added a Test-PodeIsIIS in case you need to switch between logics locally and under IIS)

Been able to test this a little more today and seems to be working as expected. If it looks good to you I can look to merge this for 1.6.0 😄

Looks very good. I will implement it next week into production and let you know if issues arise. Nice to have IIS integration now.

When testing the Add-PodeAuthIIS -Name 'IISAuth' -NoGroups I noticed that
$noGroups = $options.NoGroups

 is missing in function Get-PodeAuthWindowsADIISMethod. Now it's always true…

Can you also move the vars
                        $localUser = $winIdentity.Name -replace '\', '/'
                        $ad = [adsi]"WinNT://$($localUser)"

Into the (dirty) NoGroups check clause

                    if (!$NoGroups) {
                        $localUser = $winIdentity.Name -replace '\', '/'
                        $ad = [adsi]"WinNT://$($localUser)"
                        $cmd = "$ad = [adsi]'WinNT://$($localUser)'; @($ad.Groups() | Foreach-Object { $_.GetType().InvokeMember('Name', 'GetProperty', $null, $_, $null) })"
                        $user.Groups = [string[]](powershell -c $cmd)
                    }

For the rest everything is working very good.

Woops on the $NoGroups! I can fix  those to be $options.NoGroups.
On the following lines:
$localUser = $winIdentity.Name -replace '\', '/'
$ad = [adsi]"WinNT://$($localUser)"

I can move them, however it would also mean losing (or moving) the following line to get that user's name:
$user.Name = @($ad.FullName)[0]

What's the reason in wanting those lines moved?
Glad to hear it's working though!

I had issue on workstation with no AD present, call was very slow initially. With AD present it was working okay. Keep the $user.Name from $ad. I missed that.

Ah yeah, when adsi is done locally using WinNT the first couple of calls go slow; but it normally goes quick after the first couple 🤔 .
Instead of moving it into NoGroups, I could add a new switch (-NoLocalAD or -NoLocalCheck), and if supplied that stops the local user AD/Groups check?:
$user.UserType = 'Local'

if (!$options.NoLocalAD) {
    $localUser = $winIdentity.Name -replace '\\', '/'
    $ad = [adsi]"WinNT://$($localUser)"
    $user.Name = @($ad.FullName)[0]

    if (!$options.NoGroups) {
        $cmd = "`$ad = [adsi]'WinNT://$($localUser)'; @(`$ad.Groups() | Foreach-Object { `$_.GetType().InvokeMember('Name', 'GetProperty', `$null, `$_, `$null) })"
        $user.Groups = [string[]](powershell -c $cmd)
    }
}

Top good solution

Added a new -NoLocalCheck, which will stop Pode from doing local user lookups.

Works as expected. Everything working good now.

Excellent!


Consider using ASTCENC_FLG_SELF_DECOMPRESS_ONLY for compression

For your astcenc compressor contexts consider creating them with the ASTCENC_FLG_SELF_DECOMPRESS_ONLY flag. This allows the codec to repack the data tables with only the entries it needs for the compression configuration in use. However, it cannot reliably decompress arbitrary images as the table entries are missing for things the current compressor configuration isn't using, so only do this for compression-only contexts or cases where you are decompressing images made in the same compressor session.
Using this option for compression give 10-20% more performance, depending on block size, so is highly recommended.

Will look into that.  I also need to hookup the block diagnostics that you added a while back.

I'm a little confused by the naming on this.  Is this for the compressor too?
I do use both the ASTC compress and decompress.  Decompress mostly on x64 where ASTC isn't supported, but I want to still display the pixels.   There's also this flag ASTCENC_FLG_DECOMPRESS_ONLY which I do set on the decompressor.

Yeah it's an odd name - couldn't think of a better one.
The flag is designed to help context creation and compression performance (optimize data tables for the specific config in use, rather than storing complete tables).
Decompression is still supported, but only for the subset of block modes and partitionings that were needed by the compressor config, so it's only safe to use for decompressing images created in that compression session (i.e. for testing image quality by doing compress -> decompress pairs). For general arbitrary image compression, don't use it.
Summary:

Use ASTCENC_FLG_SELF_DECOMPRESS_ONLY on contexts you use for compression, or compression->decompression pairs.
Use ASTCENC_FLG_DECOMPRESS_ONLY on contexts you plan to use only for decompression.
For arbitrary contexts which may compress and decompress arbitrary images then set neither.

Closing this, and thanks for the suggestion.  I'll do some more timing numbers next week now that the bad blocks are fixed.


Change URLs to link directly to page being viewed

Feature description 💡
When within a organization > workspace, moving between the different tabs (Overview/Runs/States/Variables) does not update the URL, it always sticks to the format https://terrakube-ui/workspaces/<uuid>
If I share the link with someone else, they must firstly be already in the right organization for the workspace to show, or they get a Data loading... page:

This is handy in situations when I want to share a specific Run with other users for approval for example.
This even happens when I use the link from the CLI, it only takes me to the workspace: https://terrakube-api/app/simple/sample_simple/runs/17 will take me to https://terrakube-api/workspaces/5ed411ca-7ab8-4d2f-b591-02d0d5788afc
Anything else?
No response

Hello @calvinbui,
I recently added a this feature please check out this PR: https://github.com/AzBuilder/terrakube/pull/797.
This feature will be available in version 2.21 We'll release a beta version in the upcoming days if you'd like to try it.
This will change also the url when you change between tabs.

I think I still need to add organization context to url so will keep this issue open

Hello @calvinbui,
I recently added a this feature please check out this PR: #797.
This feature will be available in version 2.21 We'll release a beta version in the upcoming days if you'd like to try it. This will change also the url when you change between tabs.

I can confirm this works

I've added the organization ID to the URL path to fix the loading issue. I'm closing this issue; it will be released in v2.21. You can test it in the next beta if you want a preview.


Init method does do match documented behavior when using as module

Hello.
I'm willing to integrate the SDK on our NextJS application (TS).
It is said in the documentation for the init method that:

This function initializes a new instance of the Mixpanel tracking object.
All new instances are added to the main mixpanel object as sub properties (such as
mixpanel.library_name) and also returned by this function

and in the code I can see that it appears to do so:
MixpanelLib.prototype.init = function (token, config, name) {
    if (_.isUndefined(name)) {
        console$1.error('You must name your new library: init(token, config, name)');
        return;
    }
    if (name === PRIMARY_INSTANCE_NAME) {
        console$1.error('You must initialize the main mixpanel object right after you include the Mixpanel js snippet');
        return;
    }

    var instance = create_mplib(token, config, name);
    mixpanel_master[name] = instance;
    instance._loaded();

    return instance;
};

However, when using the library as a module (mixpanel.cjs.js) there is a call to override_mp_init_func which overrides the init code of the master instance
 mixpanel_master['init'] = function(token, config, name) {
        if (name) {
            // initialize a sub library
            if (!mixpanel_master[name]) {
                mixpanel_master[name] = instances[name] = create_mplib(token, config, name);
                mixpanel_master[name]._loaded();
            }
            return mixpanel_master[name];
        } else {
            var instance = mixpanel_master;

            if (instances[PRIMARY_INSTANCE_NAME]) {
                // main mixpanel lib already initialized
                instance = instances[PRIMARY_INSTANCE_NAME];
            } else if (token) {
                // intialize the main mixpanel lib
                instance = create_mplib(token, config, PRIMARY_INSTANCE_NAME);
                instance._loaded();
                instances[PRIMARY_INSTANCE_NAME] = instance;
            }

            mixpanel_master = instance;
            if (init_type === INIT_SNIPPET) {
                window$1[PRIMARY_INSTANCE_NAME] = mixpanel_master;
            }
            extend_mp();
        }
    };

Should it not return the master instance? If not I'm sorry for the trouble.
Thank you.

Yeah this is a little weird - technically the documentation you quoted only specifies that it will return new instances added to the main instance, which it does, but it's odd that it doesn't return anything in the case of just initializing the main instance. Mainly this is a legacy of the loading patterns available before the SDK supported CommonJS, where you were expected to access mixpanel via a global reference on the window object in the browser.
If you have a need to get the main mixpanel instance back from this function, I'm pretty sure we can add that without any issues.

Thank you @tdumitrescu for your answer.
I think I can achieve what I want without it. It was mainly to check if I understood the behavior properly.


Add schema for the externalarray type

We try to include a description field in all schemas. Could you please add one.
Also, when possible, include examples. Here's an example
https://github.com/spacetelescope/asdf-standard/blob/master/schemas/stsci.edu/asdf/unit/unit-1.0.0.yaml


Feature/swift3 refactor

Codecov Report

:exclamation: No coverage uploaded for pull request base (alpha@c983caf). Click here to learn what that means.
The diff coverage is 90.35%.

@@           Coverage Diff            @@
##             alpha       #2   +/-   ##
========================================
  Coverage         ?   90.48%
========================================
  Files            ?       11
  Lines            ?      767
  Branches         ?        0
========================================
  Hits             ?      694
  Misses           ?       73
  Partials         ?        0

Impacted Files
Coverage Δ

Source/FutureComposition.swift
100% <100%> (ø)

Source/Promise.swift
100% <100%> (ø)

Source/FunctionComposition.swift
100% <100%> (ø)

Tests/XCTest+Extension.swift
100% <100%> (ø)

Tests/PromiseTests.swift
88% <80%> (ø)

Tests/FunctionCompositionTests.swift
76.47% <80%> (ø)

Source/Future.swift
87.35% <84%> (ø)

Tests/FutureTests.swift
90.57% <92.18%> (ø)

Source/ExecutionContexts.swift
91.66% <95.23%> (ø)

Tests/FutureCompositionTests.swift
95% <95.83%> (ø)

... and 1 more

Continue to review full report at Codecov.

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


Fix tests and use web-console for dev only

Avoiding the error below when running bundle exec rake :
Web Console is activated in the test environment, which is
usually a mistake. To ensure it's only activated in development
mode, move it to the development group of your Gemfile:

    gem 'web-console', group: :development

If you still want to run it the test environment (and know
what you are doing), put this in your Rails application
configuration:

    config.web_console.development_only = false

I signed it!


web login message

Maybe we can remove the "<IP_ADDRESS>"-message after the "SUCCESS"-message when using the web-login

I removed that already in the latest code.


Russian letters are not used for filename of downloaded file

I use latest youtube-dl 2016.05.01 and this syntax
youtube-dl -f 22 https://www.youtube.com/watch?v=hNqG7-dwmRo
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. Alle Rechte vorbehalten.

This is intentional behavior for now. See #4787 for the rationale and #5527 for alternative solution discussions.

I read the threads but I'm unsure what I have to do.

Build youtube-dl.exe with python 3 or run from sources with python 3 or use any supported OS apart from Windows.

OK, sadly I'm not a programmer but I know some things about it. Why isn't Python 3 not used as default? If youtube-dl.exe is built with Python 3, does it then work on Win 10?

Python 3 build has it's own problems.


Display warnings and errors by default, not suggestions #137

Display warnings and errors by default, not suggestions #137

I apologize, I didn't meant to close the issue before we reach consensus. I made a typo in a commit.

@michaelryanpeter

How to use use the --minAlertLevel flag

See: https://redhat-documentation.github.io/vale-at-red-hat/docs/end-user-guide/defining-a-vale-onboarding-strategy/#_focus_on_errors

A brief explanation of why suggestions are useful, and a fewcontexts where one might want to turn off suggestions

See: https://redhat-documentation.github.io/vale-at-red-hat/docs/end-user-guide/understanding-vale-output/#understanding-vale-alert-levels_docs
and https://redhat-documentation.github.io/vale-at-red-hat/docs/end-user-guide/defining-a-vale-onboarding-strategy/#_focus_on_errors

Maybe we could have a small shell script to turn off suggestions?

Wouldn't is be more complex than learning to use the --minAlertLevel flag?

Thank you for pointing these out, @themr0c. I have spent more time in the documentation over the past few weeks. I think that you are right, having writers copy and paste something into their .bashrc is probably more complex than learning how to use the flags.
I have an idea for discussion. It is a tangent from @rolfedh's original issue, but it might help. I will open an idea/issue and refer back to here.