docker context is not respected

What happened?
Running gefyra status:
[CRITICAL] Docker init error: Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory'))
[ERROR] Could not create a valid configuration: Docker init error. Docker host not running?
[INFO] There was no --endpoint argument provided. Connecting to a local Kubernetes node.
[CRITICAL] Docker init error: Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory'))
[ERROR] Could not create a valid configuration: Docker init error. Docker host not running?
[CRITICAL] Docker init error: Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory'))
[CRITICAL] There was an error running Gefyra: Docker init error. Docker host not running?

What did you expect to happen?
I am using a non-default docker context.
Running docker context ls
NAME              DESCRIPTION                               DOCKER ENDPOINT                                         KUBERNETES ENDPOINT                ORCHESTRATOR
colima *          colima                                    unix:///Users/ventsislavg/.colima/default/docker.sock
default           Current DOCKER_HOST based configuration   unix:///var/run/docker.sock                             https://<IP_ADDRESS>:6443 (default)   swarm

How can we reproduce it (as minimally and precisely as possible)?
on macOS:
brew install colima
colima start
docker info
gefyra status

What Kubernetes setup are you working with?
N/A
OS version
Darwin ventsislavg 22.1.0 Darwin Kernel Version 22.1.0: Tue Sep 27 22:08:45 PDT 2022; root:xnu-8792.41.6~5/RELEASE_ARM64_T6000 arm64
Anything else we need to know?
No response

Hi @ventsislav-georgiev
Thank you very much for bringing this up. Is there an option to make Colima the default runtime on your machine (just to see it working)?
I had a glance at our underlying libs looking for the support of docker contexts. Well, it isn't supported at the moment. That means, we have to implement it in Gefyra ourselves. That is probably quite some effort.
We'll create an assessment to see if this can get on our short-term roadmap. I guess we may approach this once we're taking care of the Podman implementation, too.
In any case, if you see the capacity on your side to provide an intermediate solution for Gefyra, please let me know.

@Schille not completely sure - just saw this:
https://github.com/hakanardo/docker-py/blob/c239d66d5d261f0f956925705c679fffb61bdb05/docker/context/api.py
Maybe we could leverage this one somehow. We'll have to investigate anyways.

I tried to reproduce the issue with
brew install colima
colima start
docker info
gefyra status

Works fine. However, not sure whether gefyra uses some default from my system. I'll dig into it a bit further.

@ventsislav-georgiev not sure if you have access to this artifact:
https://github.com/gefyrahq/gefyra/suites/8831190960/artifacts/402347496
It contains a fixed binary from the PR above. If you could give it a try - that would be awesome. Please let us know whether this works for your setup.

Thanks @SteinRobert. I've tested the provided build and it indeed works.
However, there seem to be another issue. I tried gefyra up next and it took a long time:
[INFO] There was no --endpoint argument provided. Connecting to a local Kubernetes node.
[INFO] Installing Gefyra Operator
[INFO] Created network 'gefyra' (a2bbf4fae3)
[INFO] Pulling image "quay.io/gefyra/operator:0.11.4"
[INFO] Successfully pulled image "quay.io/gefyra/operator:0.11.4" in 8.311726046s
[INFO] Pulling image "quay.io/gefyra/stowaway:0.11.4"
[INFO] Successfully pulled image "quay.io/gefyra/stowaway:0.11.4" in 15.011779716s
[INFO] Operator became ready in 87.6396 seconds
[INFO] Deploying Cargo (network sidecar) with IP <IP_ADDRESS>

Also the operator has the following error:
[2022-10-18 21:01:34,545] kopf.activities.star [ERROR   ] Activity 'check_gefyra_components' failed with an exception. Will retry.
Traceback (most recent call last):
  File "/usr/lib/python3.9/kopf/_core/actions/execution.py", line 279, in execute_handler_once
    result = await invoke_handler(
  File "/usr/lib/python3.9/kopf/_core/actions/execution.py", line 374, in invoke_handler
    result = await invocation.invoke(
  File "/usr/lib/python3.9/kopf/_core/actions/invocation.py", line 116, in invoke
    result = await fn(**kwargs)  # type: ignore
  File "/app/gefyra/handler/components.py", line 211, in check_gefyra_components
    await aw_wireguard_ready
  File "/app/gefyra/stowaway.py", line 80, in get_wireguard_connection_details
    stream_copy_from_pod(
  File "/app/gefyra/utils.py", line 112, in stream_copy_from_pod
    raise e
  File "/app/gefyra/utils.py", line 107, in stream_copy_from_pod
    member = tar.getmember(source_path.split("/", 1)[1])
  File "/usr/lib/python3.9/tarfile.py", line 1790, in getmember
    raise KeyError("filename %r not found" % name)
KeyError: "filename 'config/peer1/peer1.conf' not found"

And gefyra status says that Gefyra is not running properly:
{
  "summary": "Gefyra is not running properly",
  "cluster": {
    "connected": true,
    "operator": true,
    "operator_image": "quay.io/gefyra/operator:0.11.4",
    "stowaway": true,
    "stowaway_image": "quay.io/gefyra/stowaway:0.11.4",
    "namespace": true
  },
  "client": {
    "version": "0.11.4",
    "cargo": true,
    "cargo_image": "gefyra-cargo:20221019000235",
    "network": true,
    "connection": false,
    "containers": 0,
    "bridges": 0,
    "kubeconfig": "~/.kube/config",
    "context": "colima",
    "cargo_endpoint": "<IP_ADDRESS>:31820"
  }
}

This is all on a M1 mac.
I probably should open another issue for that since this one is resolved now.

It's not resolved yet, since you only downloaded a pre-release binary. Please give us a bit of time to cleanly resolve the first issue. Thank you for opening another issue that makes sense indeed.


wrong code

in MVC -> Views -> Extending views
extend('MauticCoreBundle:Default:content.html.php');

?>
it should be
extend('MauticCoreBundle:Default:slim.html.php');

?>

@aliess heads up, you probably meant to sent this to another branch!


removed dash from the libtcod package name

I think you should just rename it to libtcod.

Might be mistaken for the original library then, no? http://roguecentral.org/doryen/libtcod/

Up to you, the alternative is to rename https://github.com/Vladar4/libtcod_nim/tree/master/libtcod to libtcod_nim.

Might moving https://github.com/Vladar4/libtcod_nim/tree/master/libtcod one level up be the option?
I.e.:
libtcod_nim/
    private/
    libtcod.nim
    README.md
    ...

yes, but private needs to be inside a libtcod_nim directory.

Done.


Fix Linux VM links

Hi @dondizon, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@dondizon - Thanks for the fix


checks for snapshot last index is wrong

Bug Report
https://github.com/tikv/tikv/blob/1fb8980ccab9ff40c1adc206df52952dab8e8ad8/components/raftstore/src/store/peer_storage.rs#L467-L475
Supposing a leader append a lot of logs without replicating any of them. After several elections, new leader compacts all previous logs. If the old leader rejoin the group, new leader will send it a snapshot. If old leader exits before updating raft state, then the condition will be false and result in corrupted state.

/severity major

/assign busyjay

/assign LintianShi

The root cause of this bug is that both apply state and raft state are updated during snapshot applying. However, apply state and raft state are seperately persisted in kvdb and raftdb. So we cannot write apply state and raft state atomically. If the instance crashes during snapshot applying, raft state may not be persisted successfully while apply state is persisted. When the instance recovers from the snapshot-applying state, the raft state is possible to be inconsistent with apply state.
The current solution is that we saves a copy of raft state into kvdb which is named snapshot_raft_state. When recovering from the snapshot-applying state, we check the snapshot_raft_state in kvdb with raft state in raftdb. If the last index of raft state is behind the snapshot_raft_state, we use snapshot_raft_state as the correct raft state. Unluckily, the above solution still has a corner case mentioned by Jay.
To ensure the correctness of recovering, we can use snapshot_raft_state to recover the raft state in every situation. The drawback of this solution is that the log entries appended during snapshot applying may be dropped after recovery. However, appending log entries during snapshot applying occurs with low possibility. So this solution may not hurt the performance a lot.

How about checking commit field instead?

I find weird that commit field in RaftLocalState.hard_state is not updated in fn apply_snapshot. Is it expected?

It should be updated in the end. You can verify it with a test case.

Yes, commit is updated out of fn apply_snapshot. It is updated in fn handle_raft_ready.

As the commit of raft state always increases monotonically, we can use commit to check snapshot raft state in kvdb with raft state in raftdb.
In save_snapshot_raft_state_to, the commit of snapshot_raft_state is set to snapshot_index (snapshot_index is the applied index of the leader). Since the peer rejects snapshot whose snapshot_index is smaller than commit of its raft state, we ensure that the commit of raft state cannot decrease if snapshot is applied successfully. When recovering from applying snapshot state, we can confirm that raft_state failed to persist if commit in raft_state is smaller than that in snapshot_raft_state.
If snapshot_index is equal to the commit of the follower, it seems difficult to handle. However, the follower will only forward its apply state if it receives a snapshot with snapshot_index equal to its commit. It can be seen as the follower has applied all its committed log. If the raft state fails to persist, it does not affect correctness. We just keep those uncommitted log entries.

PR: https://github.com/tikv/tikv/pull/13088


Consolidate documentation of visualization tools in Trixi

I wonder whether we should consolidate the documentation of our visualization tools in the Trixi docs. That is, whether it would make sense - mainly to avoid confusion and to avoid having to maintain three different parts of the documentation - to remove the docs/ folder from Trixi2Img and Trixi2Vtk and instead put all relevant documentation in the docs for Trixi?
Benefits:

Single source of truth (also for us) on where to learn about using Trixi, including postprocessing
Seemless cross-referencing between Trixi and its related tools
Thanks to Documenter.jl, all docstring documentation can be consolidated as well
No awkward back-and-forth referencing between the three repositories: all secondary repos just have a README with quick usage overview and a reference to Trixi's docs for detailed instructions
No more documentation that looks like a stub: Trixi2Vtk/Trixi2Img documentation currently looks like it is not really maintained since there is only very little information to find.

Downsides:

User expectation: Maybe some users might find it weird that a package does not have its own documentation.
API reference for Trixi2X can only include the stable (i.e., released) API docstrings, since we would rely on the Julia package mechanism to generate the API documentation

I am leaning towards going forward with this proposal, but I would like to solicit some thoughts on it first.

Sounds good to me :+1:

OK, I've added the API references and updated the descriptions in Visualization. @ranocha Could you maybe remove the docs/ folders from the Trixi2Vtk and Trixi2Img repositories except docs/src/assets with the png file in it (you may remove the favicon.ico) and disable the workflow that generated the docs there? I've already updated the README to remove the badges (since I thought it would be confusing if it forwards to the docs of another package), but we could consider to show at least the docs|stable badge and directly link to Trixi's stable/visualization docs.

Done. I've added a badge linking to the stable docs of Trixi.jl to the READMEs.


Unit tests and coverage

Before releasing 1.0.0, it would be nice to have basic functionality tested using Mocha and a coverage report

[ ] Write unit test for amqp-util.js
[ ] Mock out amqplib stuff.
[ ] Write unit test for listener.js.
[ ] Write unit test for client.js.

@disintegrator Could you give a hand here, if you are available?

@nfantone I have already started writing Mocha unit and functional tests that will cover the full module.  Will create an initial PR tomorrow.

Hey, @chefArchitect, that's awesome news! Thank you very much. Looking forward to that PR.

Work began in #34

Merged!


FEAT-#5481: implement dictionary groupby aggregation via MapReduce

Signed-off-by: Dmitry Chigarev<EMAIL_ADDRESS>
What do these changes do?
This PRs brings extended support for dictionary groupby aggregations implemented via MapReduce pattern.
Previously, dictionary aggregation was supported only for a limited set of functions. The PR enables dictionary aggregation support for the rest of MapReduce implementations, and in theory, it now requires zero effort for a new groupby MapReduce implementation to be supported in a dictionary aggregation.
Here are the key changes being made:

Moved MapReduce groupby implementations from PandasQueryCompiler to a separate class: storage_formats/groupby.py::GroupbyReduceImpl, so those implementations could be accessed for both direct (grp.mean()) and implicit usage (grp.agg("col": "mean")).

Added GroupByReduce.register_implementation method to register there implementations from GroupbyReduceImpl. This was done to distinguish between arbitrary callables in an aggregation dict and pre-written implementations.
Example:
agg_dict = {"col1": agg_func} # arbitrary callable, GroupByReduce would try
                              # to apply the func like:
pandas_groupby_object.agg(agg_dict)

GroupByReduce.register_implementation(agg_func) # the function is now registered
                               # as a phase of Map-Reduce implementation. After
                               # that GroupByReduce will apply the function
                               # like this: (which allows more efficient usage)
agg_func(pandas_groupby_object["col1"])

GroupByReduce now distinguishes between registered and unregistered functions. Unregistered functions are applied in a general way using .agg method:
unregistered_fns_res = grp_obj.agg(unregistered_fns)

And the registered ones applied one-by-one:
registered_fns_res = [
    func(grp_obj[col]) for col, func in registered_fns.items()
]

Then the results are concatenated together:
result = pandas.concat([unregistered_fns_res, *registered_fns_res], axis=1)

Q: why can't we just rewrite the 'registered' functions so they would also follow the general way of applying via .agg method?
A: Short answer - it would work much slower.
def compute_map_phase_for_mean(obj):
    return pandas.concat(
        [obj.sum(), obj.count()],
        axis=1
    )

# Applies an arbitrary callable against every group
# veeery slooooow....
grp_obj.agg(compute_map_phase_for_mean)

# Applies cython `.sum()` and `.count()` inside
# `compute_map_phase_for_mean`, works significantly faster
compute_map_phase_for_mean(grp_obj)

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #5481
[x] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date

@vnlitvinov ready for re-review

@YarShev ready for re-reviw

@YarShev all your comments have been addressed

@vnlitvinov, any other comments?

@vnlitvinov ready for re-review

@vnlitvinov all of the suggestion were applied


Prepare Carefully Compatibility

Really like the mod. Makes sense. Prepare Carefully compatibility would be wonderful

What specifically is broken?

Closed as inactive.


install rpm-py-installer ontop of SCL Python S2I container image

... so that python3 can import rpm.
As a developer, I want to import rpm with SCL's python3, so that I can use https://github.com/sclorg/s2i-python-container to build my application on OpenShift.

Okay, thanks for the reporting.
If you have something to request to me, feel free to ask me. I would encourage it.
Right now I am working for removing rpm-devel dependency from this installer in https://github.com/junaruga/rpm-py-installer/issues/70 .

@goern

Right now I am working for removing rpm-devel dependency from this installer in #70 .

The fixed version was released now.

@goern
The possible solutions for your request are

Run pip install rpm-py-installer on the SCL.
Right now There is python3-rpm package on Fedora.
https://src.fedoraproject.org/rpms/rpm/blob/master/f/rpm.spec#_263
Including the python3-rpm in the the Python SCL.


Compatibility with legacy versions of Pillow

Old versions of Pillow:Image don't support .tobytes(), so we use .tostring() instead.

lgtm. 👍


Separate lr_configs for generator optimizer and discriminator optimizer

Is there a way to specify a separate lr_config for the generator optimizer, and a separate lr_config for the discriminator optimizer? From my understanding, the lr_config specified in the config file applies to both the generator and the discriminator optimizer.

Sure, you can set a separate learning rate in the optimizer.
Example: https://github.com/open-mmlab/mmgeneration/blob/master/configs/base/models/biggan/biggan_128x128.py#L30-L32

I understand that; however, I wish to set up a separate lr_config; for example, using CosineAnnealing for the generator but no annealing for the discriminator. Is this possible?

Got your point, this feature is not supported now. We are currently working on a refactor which covers this feature, probably done by the end of June.

In 1.x, you can set parameter_scheduler like this for your purpose.
param_scheduler = dict(
generator = dict(
    type='LinearLrInterval',  xxx),
discriminator = dict(type=xxx)
)


Update audio_classification/overview.md

Fixed the broken link for TensorFlow Lite Task Library in line 29 and TensorFlow Lite Support Library in line 32

Hi @sirakiin Can you please review this PR ? Thank you!

Please don't use "update " commit messages. These make it harder to understand at a glance at commit history what the changes are.
https://cbea.ms/git-commit/

Hi @sirakiin Can you please review this PR ? Thank you!

Hi @sirakiin Can you please review this PR ? Thank you!

Hi @sirakiin Can you please review this PR ? Thank you!

Hi @sirakiin Can you please review this PR ? Thank you!

Hi @sirakiin Can you please review this PR ? Thank you!


Enable RTL, default textDirection to locale

Any reason we don't want these enabled by default?

I think it's fine as long as it's the platform expectation is that we'll support them even if we don't support any associated RTL languages.

I think it's fine as long as it's the platform expectation is that we'll support them even if we don't support any associated RTL languages.

The question is what's weirder if you are an Arabic speaker using our app right now: The entire UI of the app being totally opposite to what you're used to, or the UI being what you're used to but with english text right aligned instead of left aligned?

I'll just leave it disabled for now

It doesn't seem like the underlying API really makes sense? Like what if we supported arabic, but not hebrew? We'd have to have the flag enabled. As such, it seems like users are probably used to their UIs flipping around even when in english?

We'd have to have the flag enabled

No, we could enable it on a per-language basis, or dynamically using whatever logic we want

The question is what's weirder if you are an Arabic speaker using our app right now: The entire UI of the app being totally opposite to what you're used to, or the UI being what you're used to but with english text right aligned instead of left aligned?

I'm sure lots of apps don't support RTL or internationalization at all, so I don't think it would be a weird experience for anyone to have it disabled for locales we do not support.


method `store_formula' shouldn't be private

in 0.6.11 the store_formula method gives the error:
testExcel.rb:21:in <main>': private method store_formula' called for #Writeexcel::Worksheet:0x13a1840 (NoMethodError)
reverting back to 0.6.9 fixed the issue.

Can you show me source code (testExcel.rb) which cause NoMethodError ?
Worksheet#store_formula is called from writeexcel internal routine when writeexcel generates xls data, I think.

Sorry, i wrote mistake.
give me more time to solve this problem.

bug fixed and writeexcel v0.6.12 has uploaded.
thank you very much.
cxn03651


Add AsyncSeq merge function

Add a function to combine two ordered asynchronous sequences into a single ordered asynchronous sequence. Possible point for debate:

I started by followed the pattern of an IComparer.Compare method for determining the next element to be taken (fairly standard .Net pattern) but not convinced it's the clearest so switched to use a Choice<unit * unit> to indicate if the first or second element is next.

please submit to fsharpx.async repo

Closing this as the request is for code that has now moved elsewhere


Add noise animation

The idea is to use a computer generated noise function to control which LED lights up, rather than a LED pattern.
Expose a couple visually interesting parameters (like rand seed, noise speed, noise fade in & out, etc.) in the animation class, for the user to play with.

As you make progress in your understanding of the animation system, please you add some comments for each function of the AnimationInstance class in Animation.h


[Bug] items not displaying without hard refresh

Describe the bug
When you switch to a different category for the first time, the items do not display. A hard refresh (ctrl + shift + r) needs to be done in order to display them.
To Reproduce
Steps to reproduce the behavior:

Go to any category
Add an item
Go to another category
Hard refresh (ctrl + shift + r)
Navigate to the previous category (in which you added a new item)
The item does not show up

Expected behavior
The items should show up irrespective of when they are added, and whether the page has been hard refreshed

I am working on it.

The basic problem in this was basically that it was loading in back but was not showing anything on front


[WIP] Close #28126. Add Gist index

This PR adds the GIST index for PostGIS
ref: https://code.djangoproject.com/ticket/28126#ticket

close as duplicate of https://github.com/django/django/pull/8303


Setup your mac 1.12.4

Added user input with more pre-fill info, add pre-fill info to infobox and create receipts for Jamf Extension Attributes.

Sorry about that, didn't mean to re-request. Thanks for looking it over!

@AndrewMBarnett:
Ah, OK.
I recommend this PR be closed and you can re-submit another with just the additions.

@AndrewMBarnett:
I'm going to close this PR; please feel free to submit another one with just your additions.
Thanks.


Show Join distribution type in the Live Plan

Live Plans in Presto UI currently do not show the name of the table being scanned. It also does not show the type of join (distributed/replicated). These pieces of information are crucial in debugging queries. This issue is to add these pieces of information to the plan.

Live Plans in Presto UI currently do not show the name of the table being scanned.

I see this being shown:

What version are you using?

I was on 212. I see the table name in the latest (master). Thanks for changing the issue title.

I am concerned that showing distribution type is actually redundant information.
When join is broadcast, it's left source is within same stage.
When join is partitioned, both sources are connected with an exchange, separate stages.

@findepi with a co-located join the source is in the same stage also


tun device ip address and route tables not set in latest CoreOS (1688.5.3)

Everything works well (with docker host network mode) in CoreOS (1632.3.0). After CoreOS auto upgrade to 1688.5.3, openvpn cannot set tun device properly.
logs

openvpn_1     | Running 'openvpn --config /etc/openvpn/openvpn.conf --client-config-dir /etc/openvpn/ccd --crl-verify /etc/openvpn/crl.pem '
openvpn_1     | Sat Apr  7 05:52:22 2018 OpenVPN 2.4.4 x86_64-alpine-linux-musl [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov  9 2017
openvpn_1     | Sat Apr  7 05:52:22 2018 library versions: LibreSSL 2.6.3, LZO 2.10
openvpn_1     | Sat Apr  7 05:52:22 2018 Diffie-Hellman initialized with 2048 bit key
openvpn_1     | Sat Apr  7 05:52:22 2018 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
openvpn_1     | Sat Apr  7 05:52:22 2018 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
openvpn_1     | Sat Apr  7 05:52:22 2018 ROUTE_GATEWAY <IP_ADDRESS>/<IP_ADDRESS> IFACE=eth0 HWADDR=06:5f:cd:be:fa:a0
openvpn_1     | Sat Apr  7 05:52:22 2018 TUN/TAP device tun0 opened
openvpn_1     | Sat Apr  7 05:52:22 2018 TUN/TAP TX queue length set to 100
openvpn_1     | Sat Apr  7 05:52:22 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
openvpn_1     | Sat Apr  7 05:52:22 2018 /sbin/ip link set dev tun0 up mtu 1500
openvpn_1     | Sat Apr  7 05:52:22 2018 /sbin/ip addr add dev tun0 local <IP_ADDRESS> peer <IP_ADDRESS>
openvpn_1     | Sat Apr  7 05:52:22 2018 /sbin/ip route add <IP_ADDRESS>/24 via <IP_ADDRESS>
openvpn_1     | Sat Apr  7 05:52:22 2018 /sbin/ip route add <IP_ADDRESS>/24 via <IP_ADDRESS>
openvpn_1     | Sat Apr  7 05:52:22 2018 Could not determine IPv4/IPv6 protocol. Using AF_INET
openvpn_1     | Sat Apr  7 05:52:22 2018 Socket Buffers: R=[212992->212992] S=[212992->212992]
openvpn_1     | Sat Apr  7 05:52:22 2018 UDPv4 link local (bound): [AF_INET][undef]:1194
openvpn_1     | Sat Apr  7 05:52:22 2018 UDPv4 link remote: [AF_UNSPEC]
openvpn_1     | Sat Apr  7 05:52:22 2018 GID set to nogroup
openvpn_1     | Sat Apr  7 05:52:22 2018 UID set to nobody
openvpn_1     | Sat Apr  7 05:52:22 2018 MULTI: multi_init called, r=256 v=256
openvpn_1     | Sat Apr  7 05:52:22 2018 IFCONFIG POOL: base=<IP_ADDRESS> size=62, ipv6=0
openvpn_1     | Sat Apr  7 05:52:22 2018 Initialization Sequence Completed

OpenVPN server started successfully according to logs. Not error messages, and it call /sbin/ip to set ip address and routes. But those /sbin/ip not worked
ip address

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet <IP_ADDRESS>/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc fq_codel state UP group default qlen 1000
link/ether 06:5f:cd:be:fa:a0 brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/20 brd <IP_ADDRESS> scope global dynamic eth0
valid_lft 3106sec preferred_lft 3106sec
inet6 fe80::45f:cdff:febe:faa0/64 scope link
valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:43:a7:81:68 brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:43ff:fea7:8168/64 scope link
valid_lft forever preferred_lft forever
14: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 100
link/none
inet6 fe80::e876:a319:2839:312f/64 scope link stable-privacy
valid_lft forever preferred_lft forever

ip route:

default via <IP_ADDRESS> dev eth0 proto dhcp src <IP_ADDRESS> metric 1024
<IP_ADDRESS>/16 dev docker0 proto kernel scope link src <IP_ADDRESS> linkdown
<IP_ADDRESS>/16 dev br-bb9f41f9be54 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS>/20 dev eth0 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS> dev eth0 proto dhcp scope link src <IP_ADDRESS> metric 1024

I had to run /sbin/ip commands manually to fix the problem.

I got a workaround to fix this issue. It seems ip command executes too early before tun device complete opened and initialized.
So I wrote a delay-ip.sh and mount as /etc/openvpn/delay-ip.sh

#!/usr/bin/env bash
sleep 0.1
/sbin/ip $*

It just sleep 0.1 seconds before do actual ip command
Update openvpn.conf and add one line:

iproute /etc/openvpn/delay-ip.sh

Any updates on this being solved?  Really difficult to diagnose OpenVPN client and/or OpenVPN server if their is no error messages.  My OpenVPN container works on Ubuntu and locally on the Docker for Mac, but not able to ping the lan from newer CoreOS versions.
Trying to figure out the workaround mentioned above...

I've had this issue for some time running OpebVPN in Docker on CoreOS, but not on other hosts. The delay-ip.sh workaround above solves it for me, thanks.


Response Example Not Visible

Describe the bug
Using your example Petstore OpenAPI spec I am not seeing the Example button to the right of the Schema button which I would expect. I have used another API spec with similar results.
Expected behavior
I would expect the generated mdx file to have the details of the response example in it which would enable the Example button
Current behavior
There is no code in the generated mdx about the response example from the open API spec
Possible solution
I have not looked at the code but I suspect the example data is not being read correctly to be inserted into the mdx file. I notice you have made a fix to this recently and I did try an earlier version but it didn't improve things.
Steps to reproduce

Add the plugin for the spec into the docusaurus.config.js
   id: "apiDocs",
   docsPluginId: "classic",
   config: {
     petstore: { // Note: petstore key is treated as the <id> and can be used to specify an API doc instance when using CLI commands
       specPath: "apidocs/petstore.yaml", // Path to designated spec file
       outputDir: "docs/apis/petstore", // Output directory for generated .mdx docs
       sidebarOptions: {
         groupPathsBy: "tag",
         categoryLinkSource: "tag",
         sidebarCollapsible: true,
         customProps: {},
       },
     }

Add the entry into a sidebar somewhere
{
type: "category",
label: "Petstore",
link: {
type: "generated-index",
title: "Petstore API",
description:
"This is a sample server Petstore server. You can find out more about Swagger at http://swagger.io or on irc.freenode.net, #swagger. For this sample, you can use the api key special-key to test the authorization filters.",
slug: "/category/petstore-api"
},
// @ts-ignore
items: require("./docs/apis/petstore/sidebar.js")
}

Or you can just use your open API example template https://github.com/PaloAltoNetworks/docusaurus-template-openapi-docs.git

Generate the mdx files with npm run gen-api-docs all

Run the site with npm run start

Navigate to the defined page via the sidebar and pick Pets, Find pet by ID

Look in the responses section and you will see The Schema button but no Example button

Screenshots

Context
I see this as a fundamental part of your plugin as without it developers will find it hard to picture the data required
Your Environment

Version used: 1.1.8 and 1.1.5 before the last fix mentioning examples
Environment name and version (e.g. Chrome 59, node.js 5.4, python 3.7.3): Chrome Version 104.0.5112.81 (Official Build) (64-bit)
Desktop windows 10 PC running build 10.0.19044
Link to your project: Your template project https://github.com/PaloAltoNetworks/docusaurus-template-openapi-docs.git

Hi @julianbirkett, examples should only render if there is an example or examples key present under the operation. Otherwise only the schema should render.

I think you're saying we have to have a whole example section in the spec and that you render from that? Most specs I've seen have the example against each property e.g. In petstore.yaml Pet schema, the 'name' property looks like this
    name:
      description: The name given to a pet
      type: string
      example: Guru

Therefore, the example data of Guru is defined with the property and there isn't a separate example key
Would it be possible for you to give an example of what you mean please?
Regards,
Julian

Hi @julianbirkett, we do use the property-level example you're referencing when constructing an example request body. For response examples, we require an example or examples to be defined under the response schema.
Request body examples (I included ReDoc for comparison):
OpenAPI Docs Plugin: https://docusaurus-openapi.tryingpan.dev/petstore/add-pet
ReDoc: https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/PaloAltoNetworks/docusaurus-openapi-docs/main/demo/examples/petstore.yaml#tag/pet/operation/addPet
Response example:
OpenAPI Docs Plugin: https://docusaurus-openapi.tryingpan.dev/petstore/login-user
ReDoc: https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/PaloAltoNetworks/docusaurus-openapi-docs/main/demo/examples/petstore.yaml#tag/user/operation/loginUser

OK I understand where you're coming from and thanks for your help in explaining it.
Just to let you know what you've described isn't my experience with other OpenAPI parsers as they use the examples at the property level to build their response examples. You just need to look at how these are constructed in the swagger.io UI and extensions for VS Code. I have attached the petstore example of GET /pet/{petId} from swagger hub where you can see the response is just the name because that was the only example added in the properties. In my opinion, having the separate example makes it very difficult to keep your examples in line with the API properties if a separate definition of the example has to be created in the definition file. That's because the object definition does not live in close proximity to the example and, therefore, it's really hard to keep them in line. I think this will prevent many people using your plugin and it doesn't feel compatible with Swagger 2.0 or Open API 3.x.

Regards,
Julian

Hi @julianbirkett, thanks for the feedback.
As mentioned before, we already use a similar approach to build the request body. In theory, we should be able to apply this method to generate a response "Example" but it wouldn't be strictly based on the property-level example. For instance, in cases where a property doesn't have an example we could infer and display the type or generate an example value based on some predefined cases like date-time, boolean, etc. This appears to be what Swagger UI is doing.

In my opinion, having the separate example makes it very difficult to keep your examples in line with the API properties if a separate definition of the example has to be created in the definition file.

I hear what you're saying but schema-level example(s) are supported by OpenAPI and we see them used in some of our product API specs. That said, I think it would be entirely up to the user to decide which style of examples they wanted to use, i.e. schema example(s) vs property-level or inferred.

Yes doing the same thing you do for the request example would work well and be in line with Swagger UI. It would also give people the option to choose. Do you think this is something that could be changed please?
Regards, Julian

Still running tests but I think it should work.
https://user-images.githubusercontent.com/9343811/186010249-025ee77f-eb11-4fb7-9e80-d5d5b446631c.mov

That’s excellent. Thank you very much

Hi @julianbirkett, just published canary release 0.0.0-433. Can you please install and check to see if it addresses your issue? Thanks!

Yes @sserrata that looks to be working as expected now. Thanks Steven.


[Bug]: User is unable to navigate to API authentication page from Entity explorer

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When the user is on the canvas and tries to navigate to Authenticated API the user is unable to navigate to the respective page.
However, when a user tries to navigate from other data sources user is able to navigate to Authenticated API
Expectation :
It is expected the user is navigated to Authenticated API page
Steps To Reproduce

Create a new Authenticated API
Navigate to Canvas
Collapse the data source label
Click on the Authenticated API
and observe a blank page being disaplyed

Video:

Version
Release

Video Link :
https://www.loom.com/share/4d0dcf8df33a4d749b130ec162abf110

Duplicate issue


Add uv support for managing dependency and virtual env

Description
Add uv support for manage dependency and virtual env
Possible Solution
No response
Additional context
No response
Additional context
No response

closed by #236


Add 'spo homepage' command ?

Summary
I found only one way to define a page as HomePage spo page set.
I didn't find:

a cmdlet "dedied" to define a page as home page: spo homepage set --webUrl [...] --page [/sitepages|pages/mycustomhomepage.aspx]
a cmdlet to retrieve/get the current home page: spo homepage get --webUrl

Why? Because, if the home page is not home.aspx how can you retrieve the home page by script? (maybe with spo web get?)
The main idea is to facilitate the home page management by dedied cmdlet?
What do you think about this cmdlet? If you agree with this idea, I'll write a properly the specs of this issue ;)

Yes, we don't have support for setting the welcome page of a classic site at this moment. Rather than doing it through the page, I'd suggest extending the spo web set command with an additional option named --welcomePage where you can specify the URL of the page. How does that sound?

And for get the home page url?

Is there a way to extend the spo web get command to include it?

A sort of option that allow you to return only the home page url you mean? (I didn't check yet if this information is present to the current output)

Either that or to include the welcome page URL in the set of returned properties. If I'm not mistaken it's a property of SPWeb but I'm not sure if it's exposed through the client OM on Web or not.

Hi @waldekmastykarz,
I tried to get the welcome page from the current command spo web get and you can found at the last row:
WelcomePage                                         : SitePages/Home.aspx

And I tried to set welcomePage from rest api and it works but the property can be only set from RootFolder endpoint.
With this information in mind, how do you think we should implement the set --welcomePage?
From the current spo web set and if the parameter welcomePage is defined we add a second request or it's preferable to create a new command?

I'd opt for extending spo web set and handling the RootFolder nuance internally without bothering the user with it.

By the way, I thought about the "get" option... That could have sense to add for a command get a parameter that look like --value?
Examples:
spo web get --webUrl https://mysp.sharepoint.com/sites/project-x --value 'welcomePage'

spo web get --webUrl https://mysp.sharepoint.com/sites/project-x --value 'Title'

This behavior could be add progressively to other command... If I took as example the Starter Kit that you have create the provisioning script based on Office365-CLI, you have to use jq to extract the 'Id' of list... If you had this option with spo list get you could have used this command:
spo list get --webUrl $portalUrl --title 'Site Pages' --value 'Id'

I thought to used parameter like --value to not worry about the schema of the object... like that, it's generic.
Could it make it sense?

Is the use case here to avoid requiring jq for things like retrieving a specific property? It might be interesting to investigate the need for this with CLI's users.
While I like the simplicity, I have a few thoughts about it:

I'd prefer to use select instead of value as it more clearly reflects what's happening behind the scenes and maps to a concept people already know
select typically allows selecting multiple properties, so if we followed it consistently with the API, the result would be that even for a single property you'd get {"id": "abc"}, instead or just abc unless we did some output manipulation which could easily get confusing
if we introduced select, would the expectation be that we introduced other OData properties such as filter as well? Nothing against that per se, just trying to understand the reasoning behind it

In your proposal, you mention to introduce value to not have to worry about the schema of the object. Why would you worry about the schema? No matter if you use value or jq, you need to know that there is a property named Id in order to select it, so not quite sure what the difference is other than not needing to have jq and know its syntax.

Yes, it is the idea... If some users are not familiar with jq, this solution could make sense for them and save them time?
I understand the select choice and the purpose. It's a little bit more advanced than my idea. I thought kept simple by retrieving only one value. Why? Because, in lot of use case, you just need Id, title or whatever (ex: welcomePage) and not the entire object. If you need more, jq still the best way.
If you return an JSON object with select that means you have to use jq to work/manipulate this object in your script, isn't it? So, in this case, you don't need select? Or, what you earn by using select?
Yes, I just wanted precise that the object schema should not be an obstacle. Your explanation makes me think that we on the same wavelength 😉

I think we have a common understanding of what you're proposing. The benefit of using select would be alignment with an existing concept and minimizing the amount of data that's sent over the wire. It wouldn't address your specific use case though. How about we create a separate issue with the proposal for value as you mentioned it (select single property and return its value as plain text) and see what the interest for it would be?

Yes, we can do that in fact!
Create an issue that look like a question? Did you already do that on your repo?

Well, not really a question, but a spec that we could directly implemented if there is sufficient interest.

Ok

As we have implemented JMESPath querying since this issue was raised, you can now return the WelcomePage property using the below approach.
o365 spo web get --webUrl https://contoso.sharepoint.com --query "WelcomePage" -o json
A new issue has been raised to track the work required to extend the spo site set command with a spec and additional information, therefore I will close this issue.


fix: upgrade url to 0.11.4, resolves node 20+ punycode deprecation warnings

This should address #31

Thank you, deployed in https://github.com/niksy/node-stdlib-browser/releases/tag/v1.2.1!


WL-3588: Show sensible db error to client if db error occurs

Bad merge -  missed some properties

Do we need all these, don't we just need the ones that are different from the feedback.properties file?

Yeah some aren't needed  - I'll remove them

I'm also removing a duplicate property


Allow to set an array of x-ticks placements manually on 2D charts

Hi there
Many thanks for your great work on this project. I am currently dealing with realtime charts and encountered some minor flaws (one of them shown here).
One of the challenges is to have exact datetime ticks on the x-axis to follow streaming data. On the x-axis type datetime the ticks do not follow for minutes and seconds, which seems to be a bug on its own, and it might be impossible to control the granularity and placement.
To make Apexcharts the most versatile and accessible as possible, we should be allowed to set an array of x-ticks placements manually, such as
let xaxis = {
    tickAmount: undefined,
    tickPlacement: [1588838802,<PHONE_NUMBER>,<PHONE_NUMBER>, ... ]
    labels: {
        formatter: (value, timestamp) => {
            return new Date(timestamp).toLocaleTimeString()
        }
    },
}

This allows for more complex setups, at minimal added complexity to the library.
What is your opinion on this?
Best regards
Markus Wegmann, Technokrat GmbH

+1

@Atokulus I think that this is a good suggestion and can potentially solve a lot of x-axis related issues.


Test macos

May I ask what the reason is for switching from Ubuntu to MacOs?

There are no plans to actually merge this PR (however, we might add some CI tests on macos). The reason for opennin it were reports from people having problem to build the project on macos. And since I don't own a mac, I used this way to test it.


feature-request: built-in prompts

This is more of an idea for discussion. If any argument to .task after the first argument is a string that ends with ?, register it as a confirmation prompt, and conditionally run any arguments that follow if the prompt returns true.
Example:
composer.task('install', 'Want to install dependencies?', function(cb) {
  // this will only run if prompt is confirmed by user
  cb();
});

// or
composer.task('prompt-install', 'Want to install dependencies?', ['install', 'something', 'else']);

// or
composer.task('install', 'Want to install dependencies?', function(cb) {
  // run this if "true"
  cb();
}, function() {
  // run this if "false"
  cb();
});

The conventions for how "prompt tasks" work could differ from normal tasks.
Normally I would recommend this be done in a plugin or implementation, but after trying to create a plugin to do it, I'm thinking it would be really easy to do here. (Fwiw, I already have a working plugin that I can publish to npm if we decide to go that route. It just occurred to me that it would be awesome to have here as a built-in feature).
edit: the more I think about it, I think we should consider having Composer inherit from Enquirer, and have built-in support for all of the prompt types, or at least a handful of them. We just need to document how those prompt types work and expected behavior. This would make composer totally different than any other flow control library, and I think assemble, generate, verb and update users would really like this feature. It would also make composer more awesome for general CLI usage.
Ideas:

task and/or build can return the answers in the callback.
we can limit prompt functionality to specific conventions, like having the first and second args be strings
if composer inherits enquirer, we could allow prompts to be composed as tasks. Meaning that when task foo is run by build, composer would look for a prompt named foo and, if found, will run the prompt, otherwise, continue with the deps (how this is handled doesn't matter. composer might splice the prompt into the deps or something, but to the user it would be transparent)

this would resolve some of the items in [this checklist](related https://github.com/generate/meta/issues/1)

I like the idea of starting off with the confirmation prompt and going from there. I can already see how the code will work for based on the ideas above and the plugin you mentioned.
We could add additional prompts using the same convention (if second argument is a string ending with ?), and allowing the options to be passed into enquirer to specify the prompt type. Then instead of using y/n to determine which task function to run, the task function will just be run and this.answers will be populated with the answers. I think we can also return the answers in the .build callback when used directly.


Create one fake dataframe to test

Create one or two data frames to test the functions

I added an additional file from one of the lectures to test my function.


bugs in items module

pricelist-clciking on active / inactive is showing 500 error

[x]

[x] pricelist-

for row 10,only 10 pricelist are listed.But when making a pricelist inactive,all pricelist are displayed in the page with row as 10

for no values under currency list ,instead of blank space display with -

inventory adjustment - period filter is not functioning

[x]

items-barcode must not be same while cloning

[x]

[x] clicking on any transactions in detail page of any item,its displaying blank page

[x] history section -alignmnent issue of date and time displayed

[x] alignment issue in transaction section

[x] inactive items created from web are showing under item list table in all sections of sales and purchase modules

issue fixed !


HHH-15133 - Use specified result-type to better infer "shape" of query results with implicit selections

HHH-15133 - Use specified result-type to better infer "shape" of query results with implicit selections
https://hibernate.atlassian.net/browse/HHH-15133

2 things of note:

HqlInterpretation refs in QueryInterpretationCache are now expected-result-type sensitive in terms of array v. not-array
@beikov this reverted some changes you made in AbstractSharedSessionContract#createQuery(jakarta.persistence.criteria.CriteriaQuery<T>) for the TCK - at least according to the commit messages.  This was another "massive commit" and I was not about to dig through it all.  Pretty confident the changes I made follow the spec, but we should verify this does not cause TCK failures.

Oh nice! Thanks!

Another case where I cannot reproduce these failures locally.  Locally, the entire build passes with H2 specifically

Hm, actually I must have been on the wrong branch.  I am able to reproduce it.  Though as of yet I have no explanation why.
The only thing I can think of is that my change somehow messed up the ListResultsConsumer.UniqueSemantic used.  The result of the failing query returns a duplicated row whereas the assertions expect it to be "filtered".  The SQL is exactly the same.
I'll look further next week.

So this is actually an interesting discussion.  Consider this (the failing) query:
			List<Object[]> phonePayments = entityManager.createQuery(
				"select p " +
				"from Payment p, Phone ph " +
				"where p.person = ph.person ",
				Object[].class)
			.getResultList();

This comes from documentation.  The outcome is wrong even though the test actually passed.  The reason it is wrong is that an Object[] was not returned.  It passes because it never attempts to access the results.  Adding this causes a ClassCastException:
			final Object[] firstRow = phonePayments.get( 0 );

Basically, this was never supported in 6.0 at the moment.  My work here actually does add support for it.  So within this PR, accessing that first row as above is fine.
However the test now fails because there is currently a mismatch in terms of trying to ascertain whether the row is "duplicate".  The query selects Payment.  So we ultimately has a single assembler.  In the ListConsumer, we ask the RowReader for the result type[1] which is the selection, here Payment.  While checking for duplicates it is this JavaType descriptor for Payment used to perform the check.  However, because the row is now an array the rows are not considered duplicate.
Most likely, the correct solution is to use the JavaType descriptor for the expected return type[1] rather than the result type[1] when performing the comparisons - assuming the array JavaType descriptor does a proper "deep" comparison which I have not yet verified.  Wanted to allow a discussion of this situation before I play more with this.
Essentially, what is the correct outcome here considering an array per-row is being returned in terms of how we check for duplicates?  I think the "the filtered result" assertion in the test (the number of results) is correct; it just did not properly check previously for what is actually returned.  What say y'all?  Everyone agree with that?
[1] There is a distinction between the "result type" as determined strictly based on the query compared to the "expected return type" specified when creating the Query.

Ultimately this is the code block where this breaks down (ListResultsConsumer#consume):
			if ( uniqueSemantic != UniqueSemantic.NONE ) {
				final Class<R> resultJavaType = rowReader.getResultJavaType();
				if ( resultJavaType != null && !resultJavaType.isArray() ) {
					final EntityPersister entityDescriptor = session.getFactory()
							.getRuntimeMetamodels()
							.getMappingMetamodel()
							.findEntityDescriptor( resultJavaType );
					if ( entityDescriptor != null ) {
						uniqueRows = true;
					}
				}
			}

The only time we perform "unique-ing" is when a single entity is selected.

IMO when Tuple or Object[] is requested as query result type, we shouldn't do any deduplication/filtering, as the result type suggests that the resulting tuple is what people are interested in. If the select clause had one more item, no deduplication/filtering would happen, so not doing it in case of a single select item would be consistent.

List<TheEntity> entities = session.createQuery( "select e from TheEntity ..." ).list();
List<Integer> ids = session.createQuery( "select e.id from TheEntity ..." ).list();

assert entities.size() != ids.size();

That does not feel strange to you?  Sure feels strange to me.

Strange because (1) you think we shouldn't de-duplicate single SqmFrom select items or (2) because you think we should de-duplicate all single select items? IMO (2) might be surprising to many users and would be a change in behavior. De-duplicating single select item SqmFrom i.e. (1) was only introduce in 6.0 btw.

Strange because the same query will return different number of results based on whether I select the entity or its identifier e.g.

De-duplicating single select item SqmFrom i.e. (1) was only introduce in 6.0 btw.

Since I added it, yes I am aware ;)

Strange because the same query will return different number of results based on whether I select the entity or its identifier e.g.

Are you suggesting to remove the by default de-duplication for single entity select queries or to change to de-duplicating every single select item query?

I'm questioning whether I want to make these consistent.
I like to think of telling a user about this and how easy it is to explain a feature.  Not sure this is easy to explain/understand.  Let's talk about it tomorrow when we meet up

https://github.com/hibernate/hibernate-orm/discussions/4917

I'm questioning whether I want to make these consistent.

@sebersole I think what you're seeing is fine and perfectly consistent, as long as this in-memory dupe removal is only done to counteract the effect of a join fetch. Which is, I believe, the case.
OTOH, if dupe removal ever happens for anything other than a fetch join, I think we're really in trouble here. (But I don't think it does.)

It technically does it for all entity results, regardless of whether there are collection join fetches which is of course the only kind of join fetch we care about here.
So here's the question then... Changing this up causes a lot of test-suite failures.  Which at this point will affect early adopters of 6.0.
As a case-in-point, I'll work on a version of this that only does de-dup with entity results with collection join fetches.  I won't change any tests.  Then we can see the impact

I'll work on a version of this that only does de-dup with entity results with collection join fetches. Then we can see the impact

OK, perfect.

So this PR is finished as far as the outlined behavior.  See org.hibernate.orm.test.sql.results.ResultsShapeTests for assertions regarding de-dup.
I'll start on the other promised one shortly.  I plan on releasing 6.0 Final tomorrow, so let's get this sorted.  Final was supposed to be today, so not stopping that train again.


add happstack empire

Round II:
I have added a big old pile of packages. They all pass packdeps and build on travis CI.

Travis says:
aeson-<IP_ADDRESS> depended on by:

clckwrks-0.23.12 (>=0.5 && < 0.10). Jeremy Shaw<EMAIL_ADDRESS>@stepcut. @stepcut
clckwrks-plugin-page-0.4.2 (>=0.6 && < 0.10). Jeremy Shaw<EMAIL_ADDRESS>@stepcut. @stepcut

Can you upgrade clckwrks to aeson 0.10?

Arg. I have once again made the mistake of fixing the issues, testing them on travis, and then FORGETTING TO UPLOAD THEM HACKAGE.
Well.. no more! I have created a tool, https://www.reddit.com/r/haskell/comments/3xj9qu/ann_hackagewhatsnew_check_if_a_local_directory/
I have attempted to add hackage-whatsnew to this pull request -- but it I probably screwed that up. I just typed a bunch of good sounding git comments like, pull, stash, rebase, merge, add, commit, and push, in a variety of orders until something happened.
To the best my knowledge all my fixes are actually on hackage now.


Feature: Copy component REACT

I am working on adding a react tab for all components but I am running into an issue with the styling with prism.

Since react style takes {{ }} the highlighting is off as it does not seem to supper jsx.
I cannot seem to find out how to add support for it. Is it possible? Can you point me in the right direction?

I hardcoded the language to html on this component because I just needed HTML back then. I think if you pass it as a prop and change it to jsx that would fix it.
Let me know if you need anything

Sorry, I should have mentioned that I already tried passing jsx as language and it returns undefined. I've checked the list of languages and jsx is supported.

I've tested with javascript and it takes in and does not show undefined but is not what is required. But this means that it does take other languages

Does anything need to change here?  I am not very familiar with Prism or Svelte.

{#if language === "none"}{formattedCode}{:else}{@html formattedCode}{/if}

I was looking at Prism and seems to me that languages might need to be defined. Maybe the package does not contain the language? Sorry, I am shooting in the dark trying to see what hits.

I ended up passing svelte as a language.


html text showing in search card

Subject: html text showing in search card
Description:
clicked user on map search
Results:
The text in user's card is

[...] I am excited to join this community so I may meet fellow travelers from around the world! <span class="colour" sty...

It would be better if the html could removed so the text appears the same as on the profile https://app.couchers.org/user/priyav
Backend version: develop-8cfcaa68
Frontend version: develop-8cfcaa68
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0
Page: https://app.couchers.org/search#loc=13.48/40.72501/-73.99801
User: itsi (2)

Not mnay users have html in their profile luckily


Allow to drag the window with the search box

I often have to work with multiple VSCode instances that I need to drag around on the desktop. When the window is small, the areas I can grab onto to drag the window are very small, especially since the introduction of the command search area. It slows me down.
I've highlighted the draggable areas here:

It would be much better if the search area would be included for drag start, as it increases the grabbable area significantly.

this is an electron limitation unfortunately

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


ServiceImports are not being created after reboot

What happened?
ServiceExport resources are created for some of the services in both cloud instances and physical instances. Ideally, ServiceExport creates ServiceImport in other endpoints, including other connected clusters. However it's not the case when the cloud instance is rebooted since the deletion process of all of the ServiceExports is not triggered. (clusters are switching to the Connected phase so quickly, it bypasses the deletion/recreation process)
The problem causes ServiceExports to fail, as it's being followed by connection issues to discovery server from PI side and remote IDE connection problems in CI side.
What did you expect to happen?
I expect to see ServiceImports are always up-to-date w/ ServiceExports. To satisfy that, other parameters can be used such as "node's boot ID" (.status.nodeInfo.bootID).
How can we reproduce it (as minimally and precisely as possible)?
Can be reproduced by rebooting CI when a PI and a CI are connected.
Kubernetes version
All Kubernetes versions
Container network interface (CNI) and version
No response

A possible solution is to save boot ID to the labels of PI and CI resources. If the cluster is rebooted, operator will know that it needs to recreate ServiceExports between reboots.


Improve particle samplers warning message

This PR adds a bit of warning information for illy defined posteriors, e.g.

  @model normal() = begin
    a ~ Normal(4,5)
    b ~ Normal(a,1)
    n ~ Categorical(3)
    for i=1:n # random number of observations
       n ~ Normal(a,b)
    end
  end

  tested = sample(normal(), SMC(10))

Prerequisite: https://github.com/TuringLang/Libtask.jl/issues/41

Ready for another review @trappmartin

I'm merging now since there is no functionality in this PR and all the tests are passing.


Release build issue

Release build with Ignite - React Native boilerplate showing blank screen, it is working in debug mode. Did anyone get this issue?

yes

Hi @nithinvarghese-naico Can you please provide the information

Steps to reproduce. What commands did you run?
What is your ignite doctor output.

Would love more info, or better yet, a PR!

Closing this due to no activity for quite some time. If you're still experiencing this on the latest version of ignite, please open a new issue with output from npx ignite-cli doctor output


Rename elements starting with _ as they will be private in Dart

How about _foo -> $_foo? @liamappelbe @dcharkes


Sway support

Just started using this, and would love to see sway support ^^,

Ok, as my GC unexpectedly started working with Wayland so I added Wayland support. I have a few major issues though: sway starts on the wrong screen and freezes instantly. But I have optimus on my laptop: Could you try it and tell me if you have more luck with it ? Thank you!

Oh sorry, I installed a different distro with Xorg a month ago :/

Doesn't seem to work (sway-git, ly-git)
Did you include wayland support in the rewrite?

No I didn't because my laptop has an nvidia graphics card with optimus, which makes testing difficult. To stay polite nvidia does not support wayland, so I can't experiment easily. Support will come if nvidia change their mind (which they won't) or when I buy a new, full-amd computer.


Testnet issue with gpu miners

i got this errors in daemon log when i am on testnet
2018-04-18 14:24:41 ERROR: ContextualCheckTransaction: overwinter is active
2018-04-18 14:24:41 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-04-18 14:24:41 ERROR: ReadBlockFromDisk: OpenBlockFile failed for CBlockDiskPos(nFile=-1, nPos=0)
as i understand this issue is due i am using gpu in test not cpu miners, i don't know any CPU miner that
can help for testing

even with cpu miners i got this error when found a new block
2018-04-19 08:36:36 ERROR: ContextualCheckTransaction: overwinter is active
2018-04-19 08:36:36 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-04-19 08:36:36 ERROR: ReadBlockFromDisk: OpenBlockFile failed for CBlockDiskPos(nFile=-1, nPos=0)

same problem here,have you figure out what happen ?


Scan Settings

With the recent changes what scanning options is everyone using?  Im so used to using one account to cover a 10 scan size. I have to have two now. Thinking about adding one more ptc account too lol.

Just understand the times when you get a bigger scan radius going.  If we can only scan every 10 seconds then this is what we have:
Scan radius 4 has 37 circles.  After the 1st one appears, you have 10 seconds times 36 more.  That is 360 seconds to complete the scan.  That means the first, center circle will refresh in 6 minutes.  That will leave at most 9 minutes left on something that spawned 1 second after the circle appeared.
If you go to a scan radius of 5 there are 61 circles.  Do the math and that is 10 minutes for the center circle to refresh.  That will leave at most 5 minutes left on any Pokemon.

TY Mac.

How to scan like that @MacDogg o.0?


ConfigurationSet.load_xyz is slow

Loading in a ~100 MB trajectory takes forever with the current implementation. Running a quick cProfile shows that most of the time is been spent checking the equality: https://github.com/duartegroup/mlp-train/blob/fc54255fc14f4d48cba7cf9f88680f899d76461a/mlptrain/configurations/configuration_set.py#L226
which is a reasonably expensive operation (in the current implementation! not intrinsically). I suggest we have an additional constructor argument that skips this e.g.
import mlptrain as mlt

trajectory = mlt.ConfigurationSet(.., allow_duplicates=True)

thoughts @tristan-j-wood @vitartas ?

Definitely agree, this has been slowing down some of the internal functionality as well. I guess adding an additional argument to ConfigurationSet is the most straightforward way to go about this


Release for version 1.2.2-beta.1

PR for beta release version change

Coverage decreased (-1.2%) to 72.772% when pulling 281033dbc9e6e7e77c1350d526e443951e4075e1 on version-msal.1.2.2-beta.1 into ea6a415f678017237cc6d2f0ba493076950bdf8f on dev.


odd function definition in author name construction in apalike

https://github.com/citation-file-format/cff-converter-python/blob/main/cffconvert/ApalikeObject.py#L56-L68

This issue is now part of

#178

, closing this one


Azure AD banner to update endpoints is shown while creating RKE1/hosted clusters even when the endpoints are updated

Setup
Rancher version: 2.6-head a1abea5
Browser type & version: Chrome
Describe the bug
When we enable azure AD with the new endpoints, the banner to update endpoints is shown when we try to create an RKE1 node driver cluster or an EKS hosted cluster. This is not the case when we try to create an rke2 node driver cluster.
To Reproduce

Enable azure AD auth - new endpoints are enabled
Navigate to create an rke1 node driver cluster

Result
We get a banner to update the azure AD endpoints.
Expected Result
Do not expect any banner because the endpoints are already new.
Screenshots

Additional context

Banner is not seen anywhere else on the UI. only while creating a cluster is it seen.
Issue not seen on v2.6.9 and v2.6.10
Issue is not seen for rke2/k3s node driver clusters and custom clusters.

Verified on v2.6-head 6f7aebc

Enable azure AD auth - new endpoints are enabled
Navigate to create an rke1 node driver cluster
No banner was seen and post cluster creation, if we edit the cluster no banner is seen as well.

Verified upgrade from v2.6.5 to v2.6-head 6f7aebc

Enable azure AD auth - new endpoints are enabled
Create an rke1 and rke2 node driver cluster
Upgrade rancher server - login from /login
Update endpoints banner is seen click on it and update the endpoints from steve UI
Navigate to create an rke1 node driver cluster
No banner was seen and post cluster creation, if we edit the cluster no banner is seen as well.
Edit the cluster created before rancher upgrade - no banner is seen as well

Verified upgrade from v2.6.9 to v2.6-head 6f7aebc

Enable azure AD auth - new endpoints are enabled
Create an rke1 and rke2 node driver cluster
Upgrade rancher server - login from /login
Navigate to create an rke1 node driver cluster
No banner was seen and post cluster creation, if we edit the cluster no banner is seen as well.
Edit the cluster created before rancher upgrade - no banner is seen as well

This is not a regression - this was added in 2.6.11 and there was a bug in the PR


[SUGGESTION] Disable spawning from mob spawners

Can you add a config option to disable Eldritch mobs from spawning from mob spawners?
This would prevent farming them and the items they drop.
I know there is a block that does this, but I want to disable it across the whole server so it doesn't spawn from anyone's spawners.

Just gonna second this one - I love fighting Eldritch Mobs in the world, but if anyone has a mob grinder it gives an absolutely unbalanced number of drops

Agreed. This can cause quite a bit of unbalanced gameplay.

I would also like to see this as an option.


Preview files with dashes - are not used

Describe the bug
https://github.com/sofn-xyz/mailing/blob/56aba39c80b84e5707a35676272fc35f066bb1aa/packages/cli/src/commands/preview/server/setup.ts#L23 seems to filter out files that contain -. Is there a reason for this? Some of the code I'm using has conventions to have kebab-case.
To Reproduce
Steps to reproduce the behavior:
Have a file that is named previews/test-file.tsx. See that Mailing.run doesn't pick it up.
Expected behavior
Mailing.run picks up the file.
Screenshots
N/A.
Desktop (please complete the following information):
All versions.
Smartphone (please complete the following information):
All versions.
Additional context

Hey @oliverzheng thanks for reporting that.  That looks like a mistake to me, sorry about that.  I have a PR open for a patch and it should be available in 0.9.9.  Thanks for using Mailing!

Thank you, @alexfarrill! Mailing's great as a drop-in email previewer!


Incorrect data serialization within ArrayHash (Hashable trait)

First of all, I'm very thankful that this package exists. I'm using it to develop an API and have run into a problem related to JSON data serialization. When using the ArrayHash field within a schema, it appears to be incorrectly serializing empty arrays - it returns them as null. Which is a different behavior, compared to an ArrayList. To keep it simple, let's take an example:
Imagine there's a table with a non-nullable array/json column.
If I were to serialize the column's value {'foo': 'bar'}, the result would still be {'foo': 'bar'}. But if I were to serialize an empty array like [], then serializing it would return null. This doesn't properly reflect the structure of the data and can be misleading.
(on the other hand, serializing values ['foo', 'bar'] and [] within an ArrayList would still return both of the original values)
It appears to be caused by the usage of \LaravelJsonApi\Core\Json\Hash within ArrayHash's serialize() method. The Hash class uses the Hashable trait's jsonSerialize() method, which always returns null for an empty value.
My suggestion is to always return the original value within \LaravelJsonApi\Core\Json\Concerns\Hashable->jsonSerialize(), even when that value is empty.
I don't want to make any assumptions since I'm new to this repository and I haven't found any issues or PRs related to this. Perhaps the current behavior is intended? If not, I'd be willing to open a PR for this.

Hey! Glad you're finding the package useful.
This is intentional. Here's why...
In JSON, a PHP array hash is an object. Therefore, an empty array needs to be serialised to null in JSON. Because otherwise, clients would have to handle in Javascript the value being either an object or an array. It makes more sense for the client to expect an object or null.
For an array list, in JSON/Javascript that's an array. Therefore an empty PHP array list can be serialised to an empty array.
Hope that makes sense!


Rework UI

While making tweaks for #9, I noticed how abysmal SUI is to work with in a lot of edgecases.
It was never meant to be a forever-solution, so now would potentially be a good time to start looking into a "final" look and feel for the site.
I'm so not a UX person, so tossing a help wanted tag on this. Got an idea? Throw a comment or drop by on discord!

Claiming.
code is about half done already, all in all, not terrible.
The big issue is I'm having to do just a little cursed manipulation of the browser-side style sheet in JS, so well, we'll see how that passes review, or doesn't.


Spelling error in comment

https://github.com/kubernetes-sigs/cluster-api-operator/blob/eeab2cb6a294392b35da94acca81f65e33aa2ac1/docs/capi-operator-proposal.md?plain=1#L978-L980
Really simple change for any maintainer with the code checked out.
the has been misspelled as thw.

/assign


Single or multi additions

Makes some minor changes:

I had trouble applying the patches, so this adjusts some of the numbering to make them stick.
Combines the multi and single node docker files and replaces the split with the mpi_type flag.
Adds a feature_branch flag to allow the branch of neox-docker to use for the image to be specified at build time.

There's something strange going on with the 0002 patch, it looks like it might have changed in a way that I didn't intend, so some care is probably needed with that. The intention wasn't to change the patches.

On closer inspection, I think the 0002 patch is okay (as in, hasn't changed); it's only the lines following the change in the patch that have changed, which I think is correct.


How to redact sensitive information from logs?

Currently glog supports custom sinks, where users can implement custom logic. However, for a usecase like redacting information, or pre-processing log line, one needs to disable the default logging behaviour and enforce the custom sink.
The way I see it, it's hard to do since there is no simple way to disable the default logging. Adding a custom sink would introduce duplicate logs, and will not prevent the unfiltered logs from appearing. Most modern logging libraries provide some way to redact sensitive information from logs, since it's a common usecase.
What's the simplest way to do this with glog. Can something like this be supported? Where logs can be intercepted, edited, and then forwarded to the intended destination?
I think similar issue was discussed here https://github.com/google/glog/issues/470

cc @sergiud

Sounds like an unnecessary overhead. Why can't you redact sensitive information before you pass it to glog?

Thanks for your reply, the logs are usually scattered throughout hundreds/thousands of files. Every file is doing something like LOG(INFO) << password=123 . It's very hard to enforce this from caller side

It's very hard to enforce this from caller side.

What does that mean? If it is hard to transform the data on the call site how would the proposal simply the problem if you need to deal with the output in a generic way?

This would also be very powerful for usecases like enriching logs with additional information, defining custom formats for log lines etc. Since user has control over preprocessing the log. Thanks!

The library provides log prefix format customization. Thus the output is already fully customizable.

Thanks for your reply
For #1 instead of changing the log line before emitting it or introducing new macros, we can add user defined pluggable transformations in glog. Before emitting the logline, it can get transformed from a user defined function. This change inside the glog would be a central change where users can opt to make any change to the log message.
#2 IIUC,  log prefix format customization only customizes the prefix, but not the actual log message. It seems we can change the supplemental data (timestamp, filename etc), but not the main log message. If this can be extended to the log message, that would also work.
Or if there is any way to achieve this using existing glog functionality please let me know. Based on my reading we can't customize the actual log message, and additional sinks would not help. Thanks!

we can add user defined pluggable transformations in glog.

I already got that part. However, what I do not get why would that be easier than transforming data at the call site. You will need to deal with log output that can be formatted in any way. Handling arbitrary strings is evidently not easier that modifying values before you pass them to glog.
As for 2, clearly you can format the log line the way you want. There is not central customization in glog necessary. If you need to provide a consistent log line format, just write your own format function instead and use it consistently.

For #1 I think there is some gap here, I mean changing the log lines before sending to glog would require changing the whole codebase and transform every string that gets logged currently. It's better if we can have it in glog which can transform internally before streaming to destination.
For #2, I see thanks, just to be clear, we can change the log message itself with custom prefix? Is there any example for it, based on the documentation, it seems we don't get access to the log message, but other metadata like the timestamp/filename etc, and the user defined customization will be simply added as a prefix to the actual message. It does not seem like we can change the log message? Could you please share any documentation/example for changing the log message using prefix customization, it would be great if this can be done using existing functionality.
Thanks!

For #1 I think there is some gap here, I mean changing the log lines before sending to glog would require changing the whole codebase and transform every string that gets logged currently.

I would argue refactoring the code is the most reasonable and computationally efficient approach here and therefore a pretty bad argument for the proposed feature.

It's better if we can have it in glog which can transform internally before streaming to destination.

Again, this does not address my question in any way. You are just stating an opinion without providing a meaningful reasoning behind it.

It does not seem like we can change the main log line

Correct. As already mentioned, this is also completely unnecessary because the log line is generated by the user not the library. The user has full control of the log message and can modify using his own logic. Obviously, this is different to a log prefix which is generated by glog and therefore needs a hook for customization.

I would argue refactoring the code is the most reasonable and computationally efficient approach here and therefore a pretty bad argument for the proposed feature.

Sure, this is not feasible for codebases that have already hundreds/thousands of log lines, I was just proposing the user can choose the pros/cons, but atleast the flexibility could be offered. The default behaviour would remain the same, just that an additional feature could be offered to users (similar to custom sinks). It's upto the library owners to decide whether to support it. I understand if we prefer users changing thousands of log lines over providing an optional add-on. Thanks for your support!

Overall there are actually multiple issues here:

I argue that the use case is very uncommon but the implementation will potentially have a negative impact on the performance even if you do not use the filtering.
The proposal encourages bad software engineering practices ("I don't want to improve my code and instead let a third party implement a feature that causes more problems that one would expect at first")
Potentially enormous security risks due to unchecked logging of sensitive (user) information. The masking should be done before you log the corresponding data at the call site.

Note that the overall goal of glog is keep the logging implementation simple. Given the user can write a layer on top of glog to control the output a central filtering mechanism in glog is unnecessary. I also see arguments such as "our code base is too large" as bad excuses for not improving own code.

I'm closing the issue since this proposal is out of scope.


Added India + basic states (no union territories except Goa, Andaman/…

…Nicobar islands, Delhi, and Lakshadweep). In short, this map is detailed enough for most purposes, but not comprehensive as a source for geographically accurate information.

Hello,
Thanks for your contribution ! Your map seems to be ok except for one point : this is the old map format (for mapael 1.), you now get this warning if you use it with mapael 2; : "Extending $.fn.mapael is deprecated".
In order to fix this, you just have to take as base map a random map on this repository, and replace the 'map' object with the one in your map. Don't forget to update also the head comment.
Thanks !

Hi, have committed a modified map, based upon the template from Germany.  I am unable to test, since what I'm using is using Mapael 1, so let me know if there's a way to test the map in a neutral environment.

Hi,
Sorry for my late answer and thanks again ! It's almost perfect, you just missed to replace one line, l24 :
    $.extend(true, $.fn.mapael,

Should be replaced by
    $.extend(true, Mapael,

Hi, done.. Many thanks for your review.
I should really set up something at my end to test this with Mapael2 !

Hello @BlaidddDrwg ,
Thanks a lot ! It's ok now, I merge your pull request to the repository !
Thanks again !


Invincibility frames for newly minted latexes

Suggested by clkiscool, and others in the discord.

Added in d2cdce8dd855f72f394d7ad9303d132f19ae98fe


A11y_Azure Tools Storage Explorer_Queues_AddMessage_ScreenReader:When we edit the expire field and visibility timeout field and set a value that leads to appear of error message, the message is not read by the NVDA.

GitHub Tags:
#A11yMAS; #A11yTCS; #Win11; #DesktopApp; #A11ySev2; #BM_Azure Tools Storage Explorer_May2022; #Azure Tools Storage Explorer; #WCAG4.2.2; #ScreenReader; #NVDA; #FTP;
Actual results:
When we edit the "Expire in" and "Visibility timeout" field, and a error message appears at the bottom of the window, same message is not read by the NVDA.
For example: If "Expire in" field set to 8 and the dropdown present beside the field set to "Days", an error appears at the bottom of the screen -"The message's time to live must be no less than 1 second and no more than 7 days". The appeared message is not read by the NVDA.
Expected results:
If an error appears, it should be announced at that instant..
Environmental Details:
Application: Microsoft Azure Storage Explore
version: 1.24.0
OS Details
Microsoft Windows 11 Enterprise
version 21H2 OS Build 22000.613
Repro Steps:

Launch Storage Explorer
Navigate to "Open Connect dialog" pane and Sign in to Azure.
Go to "Manage Accounts" pane and Select the subscriptions you will use. Once selected, click on "Open Explorer" button.
Navigate to "Queues" of the selected subscription and expand it.
Navigate to "test" and click on it.
Navigate to "AddMessage" button and click on it.
Turn on the NVDA.
Edit "Expire in"/"Visibility Timeout" field and set a value that will leads to the appear of error message at the bottom of the pane.
Check whether NVDA is announcing the error message after modifying the fields.

User Impact:
Error message should be announced instantly when appears on the screen.
"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."
Attachments
https://user-images.githubusercontent.com/105198219/168733747-dbf17db7-218e-47c3-9342-fb7af179e334.mp4

@ManishC1 I cannot repro this bug. Can you let me know/reconfirm:

What Storage Explorer version you are using?
What version of NVDA you are using?

@MRayermannMSFT

Storage Explorer version is 1.24.0
NVDA version is 2021.3.5

Issue is resolved in the provided environment (ver 1.25.0). Hence closing the bug.

Github tags:#Closed

GitHubTags:#Closed;


path and typo fixes

Thank you for the great library, I'm using it in https://github.com/pbek/QOwnNotes!
If you like pull requests, here are some fixes I made.

Hi! Thank you for your contribution!
I could merge only one commit - fixed a typo (7650682).
I am not sure about your second commit (a9bee37). It seems to me that those changes are only specific to your project QOwnNotes.

The 2nd commit could be dangerous, but your project file built with the changes... I wonder why it can be built without them. :)

Build for 7650682 failed because Stephan Binner made some changes in his Qt repo. I updated my .travis.yml file so now there should be no build problems.
Commit db3e9a8. Well... man, you do it wrong :smile: .
qtcsv is a Shared Library. It is assumed that the library is compiled into *.so file on Linux or *.dll on Windows. When some application want to use functionality from shared library, it dynamically loads library file into memory so it could reach libraries' functions.
QTCSVSHARED_EXPORT - is a macro, that help to declare public functionality/symbols (classes, functions, variables and so on) of the library. This article explains how Qt generates this macro. And in this article author explains basic idea why it is useful to hide unnecessary symbols in the shared library and how to do it.
Why you have build problems with QTCSVSHARED_EXPORT in QOwnNotes? You do not use qtcsv as a shared library. You embed some of the qtcsv sources into your app so that they become part of the QOwnNotes.exe, not a qtcsv.dll library. Is it legitimate? Absolutely yes. Should you remove QTCSVSHARED_EXPORT from source files in your fork of qtcsv? Yes, because this macro is useless in your case. Also you can remove qtcsv_global.h where QTCSVSHARED_EXPORT declared.
So, finally. I could merge only 7650682 commit. It is in master branch with id 984e718895ccc050273b4f00e7494d0c84ce61f0.
Again, thank you @pbek!!

Stephan Binner made some changes in his Qt repo

I also had to switch to another Qt version ;)

Well... man, you do it wrong

Most certainly I did, because I wasn't able to build and deploy the library as shared library under Linux, macOS and Windows with qmake and cmake...
So in the end I removed QTCSVSHARED_EXPORT altogether, because I saw no point in building it as shared library, that only made troubles for me so far ;)


Having trouble installing. Installation ends with:

PiVPN Issue Template

Console output of curl install.pivpn.io | bash

Console output of pivpn add or pivpn add nopass

Console output of pivpn debug

Issue

: error fetching interface information: Device not found
: error fetching interface information: Device not found
Running Debian GNU/Linux 9 (stretch)

@Haraade please provide all the requested information in the issue template!!

curl install.pivpn.io | bash
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100   178  100   178    0     0    465      0 --:--:-- --:--:-- --:--:--   464
bash: line 1: html: No such file or directory
bash: line 2: syntax error near unexpected token <' 'ash: line 2: 301 Moved Permanently
curl -L https://install.pivpn.io | bash
Installation ends
: error fetching interface information: Device not found
: error fetching interface information: Device not found
Armbian Tinkerboard - Ubuntu and debian

@Haraade I am no magician to guess what is causing that!! I Will ask a few more questions ... if the details aren't good enough to for me to help you I will close the issue.
what distro are you using?
which user are you running the script with?
do you have sudo privileges?
can you log in as root?
try curl -L https://install.pivpn.io | sudo bash

Have tried to install on the following:
Armbian_5.34_Tinkerboard_Ubuntu_xenial_default_4.4.92.
Armbian_5.35_Tinkerboard_Debian_stretch_default_4.4.102.
Armbian_5.37_Tinkerboard_Debian_jessie_next_4.14.5.
Running the script with root user.
curl -L https://install.pivpn.io | sudo bash, ends with the same result.
After page setup for dhcp / static network setup. press OK (installation page 3) and the installation ends with:
: error fetching interface information: Device not found
: error fetching interface information: Device not found
curl -L https://install.pivpn.io | bash, worked excellent on
Armbian_5.33_Tinkerboard_Ubuntu_xenial_default_4.4.88.
So I have no idea what's the problem!

The problem is actually that first update creates a new mac address, on a device that has got static ip address. The tinkerboard will not be recognized on the network. The solution is first to update and restart with dhcp before static ip is set.
Thanks for Pivpn!

Same issue here, brand new Raspbian Stretch with Desktop:
version: November 2017
Release date: 2017-11-29
Kernel version: 4.9
Ran full apt-get update and apt-get upgrade on it
device already was configured with a static IP address.
running the curl command:

The issue happens right after these two screens:

and then

I ran into the same issue. Before your last screen, the installer gives you a list of devices to choose from.. You have to choose at least 1 from that list by pressing  and then . After that the installer actually continued.

@cfcolaco I see you self-assigned this issue. Do you have a PR ready? If not, please tell me and I'll make one.

@redfast00 I actually had this done tough a bunch of things changed so will have to review a lot of what I have done. =/ if you have time for it go ahead. sorry for taking so long =.

No problem, I haven't visited this repo in quite some time. I'll take a look at it.


The TokenHeadName cannot be set as "".

https://github.com/hertz-contrib/jwt/blob/00768db79340c5768e71a3ad3808216d9789157e/auth_jwt.go#L342-L344
I don't want to use the prefix of token but I cann't do it due to above codes.

https://github.com/hertz-contrib/jwt/blob/00768db79340c5768e71a3ad3808216d9789157e/auth_jwt.go#L342-L344
I don't want to use the prefix of token but I cann't do it due to above codes.

can you explain why you what to ignore it? I think it's JWT's specification (according to https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication#authentication_schemes)

The Bearer token is in the standard of oauth2.0, the jwt is just a way to generate the token. in jwt profile, it just say we can use the token as Bearer token not only.
in our scene, we often use it in query. I think in this way, it's not a standard Bearer token.

Can you give me a standard that has no TokenHeadName? I doubt its necessity

I think if users do not provide the TokenHeadName, we just don't valid it. also the standard auth we still support. how do you think about it?

ok, i will support this

solved @brotherlu-xcq


[ZEPPELIN-2439] Use babel-preset-env to specify browser compatibility explicitly

What is this PR for?
Use babel-preset-env to specify browser compatibility explicitly.

This will help to resolve some IE browser issues.
Additionally, we don't need to add more presets like es2017, just update preset env when we need.

Specified browser lists are

last 5 versions of major browsers
> %5 in the world
IE 9+
edge 12+
safari 7+
chrome 47+
firefox 31+ (due to travis CI)

See also - Browser Compatibility Table
What type of PR is it?
[Improvement]
Todos

[x] - Setup babel-preset-env for web
[x] - Setup babel-preset-env for helium

What is the Jira issue?
ZEPPELIN-2439
How should this be tested?

should be able to bundle existing helium packages
execute npm run build in zeppelin-web
should be able to see message like

babel-preset-env: `DEBUG` option

Using targets:
{
  "chrome": 47,
  "edge": 12,
  "firefox": 31,
  "ie": 7,
  "ios": 8,
  "safari": 7
}

Modules transform: commonjs

Using plugins:
  check-es2015-constants {"chrome":47,"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-arrow-functions {"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-block-scoped-functions {"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-block-scoping {"chrome":47,"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-classes {"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-computed-properties {"firefox":31,"ie":7,"safari":7}
  transform-es2015-destructuring {"chrome":47,"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-duplicate-keys {"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-for-of {"chrome":47,"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-function-name {"chrome":47,"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-literals {"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-object-super {"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-parameters {"chrome":47,"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-shorthand-properties {"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-spread {"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-sticky-regex {"chrome":47,"edge":12,"ie":7,"ios":8,"safari":7}
  transform-es2015-template-literals {"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-typeof-symbol {"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-es2015-unicode-regex {"chrome":47,"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-regenerator {"chrome":47,"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-exponentiation-operator {"chrome":47,"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  transform-async-to-generator {"chrome":47,"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}
  syntax-trailing-function-commas {"chrome":47,"edge":12,"firefox":31,"ie":7,"ios":8,"safari":7}

Screenshots (if appropriate)
NONE
Questions:

Does the licenses files need update? - NO
Is there breaking changes for older versions? - NO
Does this needs documentation? - NO

LGTM.
Merge to master if no further comment.


Fix nightly packaging

The nightly-dist-packaging builders have all been failing to package for the past few nights with the error:
Traceback (most recent call last):
  File "package-rust.py", line 151, in <module>
    if "CFG_PRERELEASE_VERSION" in line and CFG_PRERELEASE_VERSION is None:
NameError: name 'CFG_PRERELEASE_VERSION' is not defined

Thus, a new nightly hasn't been published since 2015-01-08.  This pull request should fix packaging.

Ping @brson, just in case you didn't happen to see this.


Does not detect all controller input

I will run the program and it says that it is recording but when I finish and playback nothing happens

do you have a controller connected?


Add env to config file

As a user of Sentinel, I want to be able to pass in environment through a config file, so that I can change my execution environment without causing a code conflict, and so that my config file setting can be overridden by the command line option "-Denv=".

Based on #35 this should be stored in a local configuration file, otherwise it will encourage users to have a separate pipeline installation for every env instead of passing that value in on tyhe command line.

Decided to fix this another way when I implemented the chrome headless browser. Instead I default to localhost as the environment. This encourages people to set the environment, but allows it to work out of the box - which was really the root problem I was having. Environment was never in the config file because you are supposed to be able to use this across all environments. Allowing that would have unintended consequences.


Missing a comma in the README

Statement was difficult to read, changed
x86 only today ARM support coming soon
to
x86 only today, ARM support coming soon

Hi @rubdos, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Thanks for bringing this to our attention. The relevant text has now been relocated to the Roadmap section of the Wiki and updated.