K2 defaults should conform to community large cluster config

Community documentation here:
https://github.com/kubernetes/community/blob/master/sig-scalability/provider-configs.md
For the control plane config:

Split etcd
5 node config
Note instances sizes specified

This issue is specific to the control plane config, not the number of nodes brought up, which could also use some discussion.

@lostlivio @jandrake  Opened per our conversation.

and 2. are currently the case, however, the default k2 configuration uses m4.large for master nodes instead of m4.16xlarge. That equates to an 8x increase in memory and a 16x increase in cores.

I am not sure the defaults should assume such a large k8s installation. Our CI system is overwhelmingly the largest consumer of k2 defaults, and in that case, there are only 10 worker nodes. Instead, it might be faster and cheaper to have a weekly scalability CI test which specifically tests the proposed configuration.

The default I'm requesting is smaller than the current default.
Alternatively, a single-node non-HA system would be reasonable.

@davidewatson Now I see your concern. My primary issue was the size of the control plane config, not the default number of started nodes.

Another area k2 defaults differ from the SIG scale testing proposal is 100GB vs. 256 GB etcd storage partitions for etcd.

The 5 node cluster is total. Etcd configs share the same 5 nodes but the storage is partitioned for iops isolation. Total of 5 nodes for all control plane. @davidewatson do you want to open issues for these specific issues?

@joejulian @sostheim Can you please comment based on customer requirements you are aware of? Note that customers should not be named in this thread.

Since we know etcd has a fixed ceiling in size, I feel 100gb might be way too big?
Mike

On Jul 13, 2017, at 2:48 PM, davidewatson<EMAIL_ADDRESS>wrote:
Another area k2 defaults differ from the SIG scale testing proposal is 100GB vs. 256 GB etcd storage partitions for etcd.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@countspongebob: Currently, k2 provisioned etcd servers must exist within a single k2 nodePool. Allowing multiple etcd instances to share a single node might be substantially easier once we support self-hosted k8s (e.g. #153 and #168), although, that is quite a bit of work, and may not even be acceptable for users large enough to require split etcd.
@venezia: The 256GB number was determined during SIG scale based on the number of IOPS required.
@coffeepac: We'll need to decide how to prioritize this.

Iops are pegged to size only on GCE, on AWS you could use a smaller partition with committed iops.

For clarity, the Kubernetes community doc is the target here. The doc above was studied and referenced in the development of the target configuration.

This topic (etcd node size) actually came up today in working with a staging cluster and the planned production cluster.  A few thoughts:

There is sensitivity to the cost of the cloud provider infrastructure used for dev/staging clusters.
Production deployments are unlikely to use these defaults except in the rarest of cases where a maxima cluster is desired.
Specifically, the production deployment targets are very much in line with the coreos hardware guide linked in the previous comment.
An active area for cluster tuning is in the individual sizing of the:

load balanced API servers
etcd cluster state store
etcd cluster event store
Each of these has a very different performance characteristic and should be sized independently.  The number of API servers is a factor of client network traffic and is severable from the number of etcd nodes for the cluster state store.
The number of etcd nodes in the cluster state and event processing clusters is clearly unrelated.

If I could summarize the all of the above simply, the defaults need to evaluated for every cluster deployment.
It's fair to assume that whatever the defaults selected for k2 are, they need to be modified for every cluster deployment.

I believe the current K2 defaults are oversized. The scalability defaults (community) are smaller and more reasonable. For many clients just sizing those nodes should get them in the right zone.

Agree, but K2 needs to support colocating the split etcd instances and iiops partitioning strategies.
ALTERNATIVELY the default could be a really small non-ha cluster, but I like the default representing community best practice in HA/scalable clusters.

@coffeepac am I right in understanding this will be a "breaking config file change"?

My understanding of what we want out of this ticket, taking into considerations the k8s large cluster doc, coreos etcd specs, this conversation and the current kraken config:

Increase master node size to: m4.16xlarge
Etcd version bump to: 3.1.8 (currently 3.1.0)
Run etcd and etcd-events in the same node (5, m4.16xlarge nodes) - Etcd and Etcd-events will mount to separate storage & run in separate RKT containers
Up etcd and etcd-events storage volume size from 100 to 256

One question - should we wait for @davidewatson 's etcd container work to be done before proceeding with the unification of etcd and etcd-event nodes?

In regards to "support [for] colocating the split etcd instances and [IOPS] partitioning strategies."
tl;dr The schema should be fine, but we will want to test k2 upgrades.
We can avoid making this a breaking schema change by allowing the existing etcdConfig property to accept either an etcdConfig, or a list of etcdConfigs. If we do this, a comment should be added to the v2alpha ticket noting that in the next version there should be only a single property etcdConfigs, with a single type of list.
In order to allow different etcdConfigs to target different partitions, we will also need a way to point a particular etcd instance at a particular directory. This is to provide IOPS isolation. Note that the mount points are defined in nodeConfig.
The larger concern I have is whether this is a breaking change for existing users. Some testing will be needed (in particular I have not considered k2cli update), but I think we may be okay since we disallow reconfiguration of etcd after up.

Have the config mostly in the right state to adhere to these standards. Working through tweaking terraform today. Hope to get to the final component (modding: k2/ansible/roles/kraken.nodePool/kraken.nodePool.etcd/templates/etcd.units.etcd.part.jinja2) soon.
Ectd v3.2.5 upgrade passed CI.

Backwards compatibility code added, parameterized drunkensmee scripts, need to test. Dryrun is running successfully.

Meeting with @davidewatson & @alejandroEsc today to scope this ticket, established to not cover following issues:

backwards compatibility for etcdConfig
refactoring extra loops in: kraken.provider.aws.module.etcd.tf.jinja2

I am going to close #781 as I feel I am too far in the weeds, I will be opening a new PR with this newly scoped work.

going to save moving certs to: /etc/etcd/etcd-name/... for another PR, would require too many changes to make this PR feasible.

Etcd nodes will spin up but, currently failing at:
core@ip-10-0-69-54 /etc $ systemctl list-units --state=failed   UNIT                          LOAD   ACTIVE SUB    DESCRIPTION               ● kraken-etcd-ssl.service       loaded failed failed Setup Network Environment ● kraken-etcdEvents-ssl.service loaded failed failed Setup Network Environment
possibly related to location of certs (etc/etcd/etcd-name/...) updating drunkensmee pathing to see if this is where the error is originating.

Still on same bug, some approaches I have tried to find the problem:

comparing user-data with working etcd node
comparing unit files with working etcd node
examining unit files/status of services that kraken-etcdEvents-ssl.service require and after on
examining RKT logs, only setup-network-environment available in state exited garbage (the garbage is concerning as it is different than a working nodes state of `exited)
drunkensmee never started indicating it's failing on Setup Network Environment

@davidewatson found issue: must pass variables to shell script with -- prepended (script in drunkensmee)

ETCD nodes seem to be up and healthy. Apiserver currently crashing. Working on solution, currently investigating "RBAC DENY" error and "TLS TIMEOUT" (both of which also occur in healthy master nodes/apiserver containers) but the TLS TIMEOUT is followed by a golang stacktrace that might indicate the problem.

Reverting work to use same certs for etcd and etcdEvents - Kubernetes api only supports single etcd certs (due to --etcd-cafile= flag).

Added backwards compatibility for configs with "etcdConfig" https://github.com/samsung-cnct/kraken-lib/pull/858

Instead of making 16xlarge the default for all clusters, it would be better if we provided an option to generate different default configs for different purposes (e.g. AWS vs. GKE, small, medium, and large clusters, etc.).
Some reasons include:

Additional documentation and manual actions will be required for all users.
The default AWS instance limit for 16xlarge's is 5. Since the default etcd cluster size is 5, if we make this the default then users of kraken will not be able to create more than one cluster at a time. It may also complicate recovery since a new instance cannot be provisioned until the failed instance is destroyed.
45x (= 15 * 5 etcd nodes) cost increase for each developer, user, and customer.
Increased boot time.

For large scale cluster testing we need a separate CI job, probably running density e2e tests. This is similar to what Kubernetes does.
@countspongebob: Please review this comment to ensure development meets the spirit of the issue.

After reviewing all of the above, my view is this:

Best practices for HA control plane for kubernetes is the goal
HA and Load are separate beasts, but related
Kraken should default to HA control plane CONFIGURATION always (5 nodes, deployed as described)
Kraken should allow for choice in sizing and provide scaling options based on proven testing
It should be very feasible for a dev to run a low node count Kraken cluster (and this may help with our CI challenges as well)
CNCT should own expertise in control plane SCALING which is translated to each provider appropriately.  This is a matrix test suite of provider and scalability thresholds
CNCT should have test suites demonstrating these SCALING configurations and be run regularly as part of Kraken release processes.
Kraken should never be deployed with less than a five node control plane as our focus is solely on production clusters

Likely there are some detail regarding etcd scaling and risks as described in the community standard for cascading problems the may inform the above.  Happy to hear them.

@jandrake: Kraken clusters are configured for HA, and according to Best Practices, by default.
There are three different changes recommended by this issue.

Etcd instances should have sufficient memory and CPU resources. For 5k node clusters, the etcd instances should be m4.16xlarge.

etcd instances should have sufficient IOPs. For 5k node clusters on GCP, this can be ensured by giving each etcd instance a 256 GB partition.

Split (logical) etcd clusters should share the same hardware (https://github.com/samsung-cnct/kraken-lib/pull/858).

and 3) are in progress. I claim we do satisfy 1) for most clusters with our current default instance size of m4.xlarge, and therefore shouldn't make m4.16xlarge the default since most clusters do not have 5k nodes. If we want to make it the default anyway, we can. It's just problematic for the reasons I enumerated above.

I think our current defaults are a good starting point for building a ClusterOps ready k8s cluster. I recommend anyone creating a production deployment consider whether the defaults are optimal for their use case.

@dwat I think we're in violent agreement here.  I'm actually agreeing with your prior comments about instance sizes.  Obviously, Kraken users can manually modify instance sizes for etcd clusters.  I am going one step further and suggesting that we take your recommendation and formalize it.  Specifically, if we know m4.xlarge service 5K clusters, we should know various size clusters all the way down to single developer size clusters in tested variations that make sense to us.  I would advocate a kraken flag for number of expected nodes and/or use cases.  I would advocate for us to have as part of our release tests full regression for each size of cluster we create a flag for.  I would expect that the two flags supported initially would be "5K production" and "development" conceptually (don't care about what the flags specifically are).
HA != Capacity.  HA = architecture and instancing as related to load.  Anyway, dead horse.  Stopping beating it.

Working on issues raised in: https://github.com/samsung-cnct/drunkensmee/pull/2
Currently configuring drunkensmee to write individual peer certs for each etcd instance on node. Seeing error:
Error:  client: etcd cluster is unavailable or misconfigured
error #0: dial tcp <IP_ADDRESS>:2379: getsockopt: connection refused
error #1: dial tcp <IP_ADDRESS>:2379: getsockopt: connection refused
error #2: dial tcp <IP_ADDRESS>:2379: getsockopt: connection refused``` but I am confused how clientport (2379) is being affected as I am under the impression I have only altered peer certs and peer cert locations.

Updates to: https://github.com/samsung-cnct/drunkensmee/pull/2 in working order.

Drunkensmee PR review resulted in choice to swap drunkensmee repo to new team standard: https://github.com/samsung-cnct/drunkensmee/issues/4

Created new drunkensmee: https://github.com/samsung-cnct/container-drunkensmee
Another commit to the Kraken-lib PR - this should be close once we get the new image of drunkensmee to replace my dev image.

https://github.com/samsung-cnct/container-drunkensmee working and Jenkins pushing image to quay.
Started giant rebase of kraken-lib work to pull in new dict commit
Got a successful CI run for kraken-lib


Support for generic type matching

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I am trying to make an object that supports the following type of method:
class Foo {
    T get<T>() {
        // implementation
    }
}

and I was hoping to mock it like so
class MockFoo extends Mock implements Foo { }

test('get returns proper values', () {
    final foo = MockFoo();
    when(() => foo.get<int>()).thenReturn(5);
    when(() => foo.get<String>()).thenReturn('test');

    expect(foo.get<int>(), 5);
    expect(foo.get<String>(), 'test');
});

Unfortunately, this throws the following error:
_TypeError (type 'String' is not a subtype of type 'int')
Describe the solution you'd like
It would be awesome if when mocking generics, Mocktail would be able to tell the difference between these two methods so the above test would pass.
Describe alternatives you've considered
I really don't think I could have an alternative solution without substantially changing how the object works.
Additional context
I believe the _useMatchedInvocationIfSet method (in lib/src/_is_invocation.dart, line 102) may be where a check that the invocation supports not only the same arguments but the same generic type definitions as well. In the passed invocation object, there is a field called _typeArguments that contains a list of the generic types passed into the invocation. I think we could add this as criteria for matching invocation and it would support this feature.
Thanks in advance! As always, I'm super grateful for everything you and this package bring to the Dart ecosystem, and I'm happy to help with a PR if you think this is worthwhile!

Only now realizing this is probably a duplicate of #66 and fixed by #67. If it is I can close it and I'll drop a thumbs up on the PR :)

Hey @mtwichel yup it’s a duplicate and I’ll try to get that merged and published in the next few days 👍

Thanks as always @felangel 🎉🎉

@felangel @mtwichel I think the prs 66/67 were referring to fixing the verify issue:
final result = verify(() => stub.someMethodWithTypeArgs<SomeType>());
But I am still having the issue with when/return as described in the original question:
when(() => foo.get<int>()).thenReturn(5);
Could either of you confirm whether the when/return generic been implemented or not?

@felangel @mtwichel I think the prs 66/67 were referring to fixing the verify issue: final result = verify(() => stub.someMethodWithTypeArgs<SomeType>());
But I am still having the issue with when/return as described in the original question: when(() => foo.get<int>()).thenReturn(5);
Could either of you confirm whether the when/return generic has been implemented or not?

Can you provide a link to a minimal reproduction sample? I'm happy to take a look 👍

So making a simplified project proved that Mocktail does handle generics correctly. From that I have managed to solve my issue 🎉
Thanks for the quick response and making this great package 👍


[tests-only] some fixes to make more files tests pass in the provider

get rid of unneeded CORS headers
use matchers for etag and file ids
create states for creating files & folders

this is part of #709

LGTM :+1:


WebID delegation and tests

I added the code for WebID delegation and tests, as well as the cleanup tests.
One of the webID tests is commented out because of the fetcher issue and the fix should be part of other commit.
All the other tests pass just fine. This completes all the tests that are included in gold.

3 failing tests? :)

I have no idea why it's happening. All the tests pass on my machine.


Gateway support register with DNS name

Refactor Request
Describe the Refactor Request
We need access to some properties that can't be gathered from the namehash of the domain. We need to have access to the DNS-encoded domain name instead.
Describe Preferred Solution
Change register handler to support the name instead of node.
function register(bytes memory name, uint32 ttl)

We then need to store the following properties onto the database:

[ ] name
[ ] label name
[ ] labelhash
[ ] parent
[ ] subdomains

handled by #140


Users able to access cart inventory from far away

Minecraft 1.12.2
astikorcarts-1.12.2-<IP_ADDRESS>.jar
Forge 1.12.2 - <IP_ADDRESS>60
Had a user1 open a astikorcarts:cargocart on a server, and had user2 ride away with the cart. As long as user1 keeps the inventory open, they are able to essentially remote-trade with those who access the cart's inventory at it's new location.

This bug has already been fixed in the most recent version.
https://www.curseforge.com/minecraft/mc-mods/astikorcarts/files/3517236
Closing.


Fixes: #1351 ... auto update stopped working

Category
This change is exactly one of the following (please change [ ] to [x]) to indicate which:

[x] a bug fix (Fix #1351)
[ ] a new Ripper
[ ] a refactoring
[ ] a style change/fix
[ ] a new feature

Description
Fixes the update batch file to work in directories with spaces.
Testing
Result:
timeout 1
copy "ripme.jar.update" "D:\Cloud\GitHub\ripme\target\ripme-1.7.84-jar-with-dependencies.jar"
del "ripme.jar.update"
"D:\Cloud\GitHub\ripme\target\ripme-1.7.84-jar-with-dependencies.jar"
del "D:\Cloud\GitHub\ripme\target\update_ripme.bat"

Required verification:

[x] I've verified that there are no regressions in mvn test (there are no new failures or errors).
[x] I've verified that this change works as intended.

[x] Downloads all relevant content.
[x] Downloads content from multiple pages (as necessary or appropriate).
[x] Saves content at reasonable file names (e.g. page titles or content IDs) to help easily browse downloaded content.

[x] I've verified that this change did not break existing functionality (especially in the Ripper I modified).

Optional but recommended:

[ ] I've added a unit test to cover my change.

LGTM

So this is broken again.. no quotes (like before)

How did you test it?


Fix scrollbar showing at bottom of chat box when using long messages.

old behaviour:

new behaviour:

note that even if a word is really long it will get wrapped correctly, including URLs.

looks good, thank you!


ROS2 Support

Does this library support ROS2? if not then any plans to support ROS2.
Thanks in advance

Absolutely YES but first i need to implement the missing features.

I'd love to see this awesome library getting support for ROS2 as well!

The main problem of ROS2 is that it's based on another, more generic, protocol, that is DDS, that is relatively newer. There isn't a Go implementation, and it must be build from scratch. This is long and expensive, but i hope it will be done at some point.
After it, a pure-Go ROS2 implementation can be set up.
https://en.wikipedia.org/wiki/Data_Distribution_Service
https://www.omg.org/spec/DDS/About-DDS/

Any progress on getting ROS2 support? I'd love to use Golang instead of Python

The main problem of ROS2 is that it's based on another, more generic, protocol, that is DDS, that is relatively newer. There isn't a Go implementation, and it must be build from scratch. This is long and expensive, but i hope it will be done at some point. After this step, a pure-Go ROS2 implementation can be developed.
https://en.wikipedia.org/wiki/Data_Distribution_Service https://www.omg.org/spec/DDS/About-DDS/ https://design.ros2.org/articles/ros_on_dds.html

Is this library useful for handling the DDS  part: https://github.com/rticommunity/rticonnextdds-connector-go?

Still too young, but can be better than nothing.

Hey, any updates to support ROS2? Looking forward to it~~

Is anyone working on this feature? I'd be happy to help out where I can.

Is anyone working on this feature? I'd be happy to help out where I can.

I’m going to start working on the DDS implementation. @aler9 I’d love to confer with you during the course of development.

@LarryDCJ hello,
First of all, this library is practically in maintenance mode, since all ROS1 features have been implemented a while ago. Recent commits have been about updating dependencies or bug fixing.
The reason why a Golang ROS2 implementation was not developed yet is because there are not enough reasons to do it. Personally i can't use ROS in my job since its role as middleware is already taken by Kafka, AMQP or SQS, all of which can be horizontally scaled and have a better handling of undelivered messages, while its role as message encoder is already taken by gRPC. The time i can spend on OSS is currently focused on some other protocols which are way more popular.
Furthermore, this porting was never recognized by the official organization (although it's one of the most popular ones), so until now no one showed up offering concrete help.
If someone is willing to start a DDS implementation, i'm willing to review the work, but i can't do more than that at the moment.

@aler9 Thanks for the insight!
I'm currently writing a driver for the YDLidar G2 and wanted to implement Ros2 written in Go when it's all done.
This is all super new to me as I'm just learning to work with serial data.

Did you ever look at
https://github.com/yangchenxing/go-dds
?
It's quite old, so I would expect you found it before, but... figured I'd ask.

For anyone who's wants to give a Golang ROS2 interface a shot, rather than native golang all the way to the DDS layerz interfacing Go to ROS2's rcl and rmw libraries via C might be a better path. This is how the Python and JavaScript implementions work, and allows the language interface to be independent of the actual middleware that is used, which is good because while DDS is the default, there are other middleware implementations.
The nodejs implementation may be useful as a starting point:
https://github.com/RobotWebTools/rclnodejs

Hi,
Does this library support ros2-galactic ? do you have plan for ros2-humble as well?
BR,
Mark

Hi, Does this library support ros2-humble ?


Tweak the Makefile to allow the use of cross-compilers.

That's hilarious.  Why would they do that??  Their images have like 15 compilers installed.


ContextualLogger overwrites min level

It doesn't pass the inner min level down to the DefaultLogger

Fixed in v0.2.1


Use high-precision vblank timings, if available

This (work-in-progress) PR implements the use of more accurate vblank timestamps, as suggested in #30 :
It requires a small kernel patch (submitted to the mailing list here), that extends the drm_vblank_event with two fields: time holding a monotonic clock timestamp, and high_prec, a boolean indicating whether or not the timestamp came from a DRM driver that is able to generate HW-corrected high-precision vblank timestamps, or not.
GPUVis is fully backwards-compatible to how it worked before. High-precision vblank timestamps are only used in GPUVis if the following is true:

the overall trace was created with monotonic clock (see below)
the user turned ON the option to use high-prec timestamps (OPT_VBlankHighPrecTimestamps, default is OFF) (bound to Ctrl-Shift-K, or right-click to toggle in option pop-up)
time field is set in the drm_vblank_event data, and high_prec is true

Opening an enriched trace, you can now toggle back and forth using Ctrl-Shift-K and see how the purple lines jump back and forth (on my laptop, diff is ~ 200ms).
As described above, you need to configure ftrace to use monotonic clock as the source for timestamps:
echo mono > /sys/kernel/tracing/trace_clock
Without that, we can't easily align the timestamps of the vblank event along the ftrace/GPUVis timeline.

Hi Heinrich. This looks good to me. Let me know when you want to have it pulled and I'll get it in. Thanks much.

The kernel patch has been accepted and is currently in drm-misc-next. It's supposed to land for 5.5. I think this MR is ready to be merged.

It's in. Thanks Heinrich!


Crashes Firefox 10.0

I am seeing a consistent crash of FF 10 when closing FF, doing stuff on the addon page and other actions too.

Can you try the latest version (1.5)? I updated to the latest addon sdk and made other improvements. I am hoping that solves your issue. Thanks.

Fixed - Thanks a lot for that amazing addon!


pcsclite: polkit policy actions not registered

Describe the bug
pcsc-lite uses two actions org.debian.pcsc-lite.access_pcsc and org.debian.pcsc-lite.access_pcsc do get necessary authorization via polkit. but these actions are not properly registed, leading to error:
journalctl --unit=pcscd --follow
Jan 13 23:34:19 jaghut pcscd[79235]: 00607239 auth.c:125:IsClientAuthorized() Error in authorization: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.debian.pcsc-lite.access_pcsc is not registered
Jan 13 23:34:19 jaghut pcscd[79235]: 00000005 auth.c:143:IsClientAuthorized() Process 79228 (user: 1000) is NOT authorized for action: access_pcsc
Jan 13 23:34:19 jaghut pcscd[79235]: 00000039 winscard_svc.c:355:ContextThread() Rejected unauthorized PC/SC client
Jan 13 23:34:19 jaghut pcscd[79235]: 00141489 auth.c:125:IsClientAuthorized() Error in authorization: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.debian.pcsc-lite.access_pcsc is not registered
Jan 13 23:34:19 jaghut pcscd[79235]: 00000005 auth.c:143:IsClientAuthorized() Process 79228 (user: 1000) is NOT authorized for action: access_pcsc
Jan 13 23:34:19 jaghut pcscd[79235]: 00000037 winscard_svc.c:355:ContextThread() Rejected unauthorized PC/SC client
Jan 13 23:34:19 jaghut pcscd[79235]: 00002007 auth.c:125:IsClientAuthorized() Error in authorization: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.debian.pcsc-lite.access_pcsc is not registered

(It can be verified that these actions don't exist by using pkaction)
This breaks yubioauth-flutter and gpg.
I tried both pcsclite 1.9.5 and 2.0.1 ending up with the same error.
Steps To Reproduce
Steps to reproduce the behavior:

Set services.pcscd.enable = true and security.polkit.enable = true in configuration.nix, configure your smartcard (yubikey)
Try to use yubikey
Get error

Expected behavior
There actions are registered correctly and usable.
Notify maintainers
@anthonyroussel
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
I'm using flakes (no channels).
[user@system:~]$  nix-shell -I nixpkgs=./src/nixpkgs -p nix-info --run "nix-info -m"
this path will be fetched (0.00 MiB download, 0.00 MiB unpacked):
  /nix/store/2bk3cqpj26fi3fwgshgg3k0fxwz0h55g-nix-info
copying path '/nix/store/2bk3cqpj26fi3fwgshgg3k0fxwz0h55g-nix-info' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 6.7.0, NixOS, 24.05 (Uakari), 24.05.20240113.76a31fd`
 - multi-user?: `no`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `""`
 - nixpkgs: `not found`

Add a :+1: reaction to issues you find important.

correct description of your effect, i am not able to use my yubikey with gpg.

This can be solved by
    environment.systemPackages = with pkgs; [
      # fix pcscd
      pcscliteWithPolkit.out
    ];

This can be solved by
    environment.systemPackages = with pkgs; [
      # fix pcscd
      pcscliteWithPolkit.out
    ];

this works, thanks! but this is really unintuitive, given that pcscd is already adding the package to environment.systemPackages: https://github.com/NixOS/nixpkgs/blob/428544ae95eec077c7f823b422afae5f174dee4b/nixos/modules/services/hardware/pcscd.nix#L55
I am leaving this open as I believe a proper fix should be provided in the module itself.

Same issue here. It was working approx. last Dec. I don't have a specific commit hash. Adding pcscliteWithPolkit.out to systemPackages works for me.
Jan 15 20:41:28 yuki systemd[1]: Started PC/SC Smart Card Daemon.
Jan 15 20:41:38 yuki pcscd[485297]: 00000000 auth.c:125:IsClientAuthorized() Error in authorization: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.debian.pcsc-lite.access_pcsc is not registered
Jan 15 20:41:38 yuki pcscd[485297]: 00000016 auth.c:143:IsClientAuthorized() Process 480685 (user: 1000) is NOT authorized for action: access_pcsc
Jan 15 20:41:38 yuki pcscd[485297]: 00000052 winscard_svc.c:355:ContextThread() Rejected unauthorized PC/SC client
Jan 15 20:42:39 yuki systemd[1]: pcscd.service: Deactivated successfully.

❯ nix-info -m
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.11, NixOS, 24.05 (Uakari), 24.05.20240113.9b19f5e`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels($user): `"home-manager"`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Looks like a regression in 9ac6715549ce35ce0170a4dbf9965e477f5878b4 - makeFlags is implying to me that polkit actions get included in the out output, however:
nix-repl> :p pkgs.pcscliteWithPolkit.meta.outputsToInstall
[ "bin" "man" ]

out isn't included, which explains why adding pcscliteWithPolkit.out to environment.systemPackages fixes the issue.

I was bitten by this when attempting to update over the weekend as well. In my case it prevented login because I use smartcards for user login which made debugging difficult due to the number of reboots required.
I tend to agree with @Sorixelle that going back to having the polkit actions file in the bin output instead of out  makes the most sense. That will mean that this line of the pcsc module will again result in the polkit action file being added to the system configuration.

    environment.systemPackages = with pkgs; [
      # fix pcscd
      pcscliteWithPolkit.out
    ];

This unbroke gpg and yubikeys for me as well
Cc: @marsam @anthonyroussel (https://github.com/NixOS/nixpkgs/pull/272529)

Looks like a regression in 9ac6715 (#272529) - makeFlags is implying to me that polkit actions get included in the out output, however:
nix-repl> :p pkgs.pcscliteWithPolkit.meta.outputsToInstall
[ "bin" "man" ]

out isn't included, which explains why adding pcscliteWithPolkit.out to environment.systemPackages fixes the issue.
Solution ideas:
* Add `out` to `meta.outputsToInstall`. Not sure about this one? `out` seems to also contain some libraries that probably don't need to be installed.

* Install polkit actions to `bin` instead of `out`. IMO this one makes the most sense, especially as it seems to have been the previous behaviour before this change.

I also think the bin location should be fine, the systemd files are also there.

I ran into this issue when I couldn't access my yubikey anymore via pcsc for commits.
The above solution worked for me.

I'm going to add some comments for SEO so this is easier to find
gpg: selecting card failed: Service is not running
gpg: OpenPGP card not available: Service is not running

scdaemon[4644]: pcsc_establish_context failed: inserted card

Add out to meta.outputsToInstall. Not sure about this one? out seems to also contain some libraries that probably don't need to be installed.

We want to commit this?
Otherwise I think we can close this as the fix got already merged.

I've created #283452 to make the outputs a lot more expected by moving the udev file and the systemd service to the out output and the libraries to the lib output:
 result
├──  bin
│   └──  pcscd
├──  lib
│   └──  systemd
│       └──  system
│           ├──  pcscd.service
│           └──  pcscd.socket
├──  sbin
│   └──  pcscd
└──  share
    └──  polkit-1
        └──  actions
            └──  org.debian.pcsc-lite.policy
 result-dev
├──  bin
│   └──  pcsc-spy
├──  include
│   └──  PCSC
│       ├──  debuglog.h
│       ├──  ifdhandler.h
│       ├──  pcsclite.h
│       ├──  reader.h
│       ├──  winscard.h
│       └──  wintypes.h
├──  lib
│   └──  pkgconfig
│       └──  libpcsclite.pc
└──  nix-support
    └──  propagated-build-inputs
 result-doc
└──  share
    └──  doc
        └──  pcsc-lite
            ├──  install_spy.sh
            ├──  README.polkit
            └──  uninstall_spy.sh
 result-lib
└──  lib
    ├──  libpcsclite.la
    ├──  libpcsclite.so
    ├──  libpcsclite.so.1
    ├──  libpcsclite.so.1.0.0
    ├──  libpcscspy.la
    ├──  libpcscspy.so
    ├──  libpcscspy.so.0
    └──  libpcscspy.so.0.0.0
 result-man
└──  share
    └──  man
        ├──  man1
        │   └──  pcsc-spy.1.gz
        ├──  man5
        │   └──  reader.conf.5.gz
        └──  man8
            └──  pcscd.8.gz

I didn't test it yet, so it is still in draft.
If someone could verify that it doesn't break security keys again, that would be great and then please undraft it, otherwise I do it in the evening.

I do not think I can fully test this due to the amount of rebuilds, so please chime in for reviews and find the one mistake I might have done (which I hope I didn't)

I do not think I can fully test this due to the amount of rebuilds, so please chime in for reviews and find the one mistake I might have done (which I hope I didn't)

Tried to build but it fails on my machine:
error: builder for '/nix/store/wc590z8yj6cs043rycgz7sd5id0727kg-python3.11-dulwich-0.21.7.drv' failed with exit code 1;
       last 10 log lines:
       > dulwich/tests/test_repository.py::RepositoryRootTests::test_fetch_ignores_missing_refs
       >   /build/dulwich-0.21.7/dulwich/refs.py:1280: UserWarning: ref refs/heads/blah points at non-present sha<PHONE_NUMBER>123456789123567891234657373833
       >     warnings.warn(
       >
       > -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
       > =========================== short test summary info ============================
       > FAILED dulwich/tests/compat/test_client.py::DulwichTCPClientTest::test_fetch_pack_no_side_band_64k - AssertionError: Lists differ: [b'07a4f52db4e20c8e63d58a342eb7f5a23b2b5d7[85...
       > FAILED dulwich/tests/compat/test_client.py::DulwichTCPClientTest::test_send_pack_nothing_to_send - AssertionError: {b'HEAD': b'514dc6d3fbfe77361bcaef320c4d21[141 chars]be9'} ...
       > ===== 2 failed, 1468 passed, 33 skipped, 1 xfailed, 251 warnings in 5.63s ======
       > /nix/store/v5irq7wvkr7kih0hhnch5nnv2dcq8c4f-stdenv-linux/setup: line 1557: pop_var_context: head of shell_variables not a function context
       For full logs, run 'nix log /nix/store/wc590z8yj6cs043rycgz7sd5id0727kg-python3.11-dulwich-0.21.7.drv'.
error: 1 dependencies of derivation '/nix/store/mqwvy609gvix7nhc1f28nlxyx03m48w5-python3.11-breezy-3.3.4.drv' failed to build
error: 1 dependencies of derivation '/nix/store/q655714kpc1pk5g62r2vggmh5ag67wcj-nix-prefetch-bzr.drv' failed to build
error: 1 dependencies of derivation '/nix/store/9hgcfpwsf3nhi7lasbifjhsrpv9bkam0-nix-prefetch-scripts.drv' failed to build
error: 1 dependencies of derivation '/nix/store/5pgl5jvpcvp0kp6d9hss3h57r06ppnd3-system-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/0gxnj3603ybw3qirn233xa1857nmjs2x-nixos-system-jaghut-24.05.20240124.ecc103f.drv' failed to build

I've added xdist to dulwich here https://github.com/NixOS/nixpkgs/pull/281170 . Let me see if we can just disable some tests as a speed up from 66s to 9s is quite good.

This should be a lot better with #284028 . I did a lot of rebuilds locally on a low and high core machine and didn't encounter any failures anymore.

This was fixed in #283452, works fine for me.


Server side filtering for JobManagement event streams

Same filters that can be used with FindJobs and FindTasks.

This was the simpler way to add criteria filters to the ObserveJobs API, but in a future iteration we should consider making filteringCriteria an explicit type, with explicit Criteria fields.


Fix Transformer Engine hipifying

Narrowing mapping to prevent updating names that should not be updated

@ipanfilo Sorry for not getting around to this PR sooner. I've scheduled a call next week for us to go over some of the concerns regarding changes in this PR.


Attr-compatible init_subclass variant: attr_init_subclass

Say I have a base class Foo, where for every derived class I want to compute some class fields. This can easily be done with __init_subclass__ in python. However, it's not possible to use the class's attribute data in __init_subclass__, since they will only get initialized by the decorator after the class is created.
What I'd like to see is a  __attrs_init_subclass__ method, that is called just before the decorator returns. In that method, attr.fields(cls) could then return the correct value. This method could obviously not take the kwargs like __init_subclass__. What might be useful is to pass a list of attributes declared in that class; there is currently no way to get those otherwise.
The only current alternative is to have the base class and a custom decorator after the attrib decorator, that means every user of the class needs two separate declarations to get it working correctly.

I also hit this one. For me, one classic use-case of __init_subclass__ is for registering sub-classes in some kind of registry, e.g. for deserialisation given some kind of type-key. However, with attrs, that obviously doesn't work because __init_subclas__ will be called on a temporary type only - attrs is going to create a new type from scratch that happens to share most of it's __dict__ contents.

Barely 5 years later, I present #1321 for your consideration.


[WIP] Mix dep

@sivsushruth can you add a task in travis to test this build? simply adding a line after rebar ct is done to launch a build with mix would be enough for now.


Non-atomic increment of volatile fields

There are two non-atomic increments of volatile fields in com.microsoft.sqlserver.jdbc.SocketFinder#noOfThreadsThatNotified and com.microsoft.sqlserver.jdbc.TDSWriter#packetNum. In Java the pre- and post-increment operators on volatile fields are not atomic. In Java volatile fields indicate that state is intended to be changed by multiple threads.
Since com.microsoft.sqlserver.jdbc.SocketFinder#noOfThreadsThatNotified is only used in updateResult and guarded by socketFinderlock I would remove volatile there.
com.microsoft.sqlserver.jdbc.TDSWriter#packetNum is a bit less obvious. The warning could simply be fixed by using either java.util.concurrent.atomic.AtomicInteger or java.util.concurrent.atomic.AtomicIntegerFieldUpdater, the latter has a bit lower overhead. On the other hand without knowing any details about the threading model it's hard to know if that is enough or even necessary. All the other fields changed in methods where packetNum is accessed seem to be non-volatile and the changes don't seem to be atomic. This suggests to me that those methods are not intended to be thread-safe and as a result removing volatile from packetNum would be my recommendation here as well.

Thanks @marschall for your inputs.

Thank you@marschall for reporting the issue. After investigation, we totally agree with your suggestions. However, we are working on a new multi-threading feature right now, We decide to mark this issue as enhancement and re-consider it in the future after the multi-threading feature is done. Thank you.

Yes @v-xiangs I agree it doesn't seem to be a correctness issue, just a bit confusing.

@marschall Thank you very much for the findings! We have created a PR for this issue. Thanks!

Hello @marschall , thank you very much for your contribution. The PR is merged and we are closing this issue now.


[PDI-16580] - Webservices auth failed when using parameters for usern…

…ame and password.
@duarteteixeira @pamval

Hello, This is an automated comment from our build system. Since this pull request originated from a user  not in the Pentaho organization, we will not proceed  with automatic validation of the pull request.  However, rest assured that it will be reviewed manually as soon  as we get the chance. Thanks for your contribution!


#2949 - Attachment points should be within S-Group brackets

How the feature works? / How did you fix the issue?
(Screenshots, videos, or GIFs, if applicable)
Check list

[x] unit-tests written
[ ] e2e-tests written
[ ] documentation updated
[x] PR name follows the pattern #1234 – issue name
[x] branch name doesn't contain '#'
[x] PR is linked with the issue
[x] base branch (master or release/xx) is correct
[ ] task status changed to "Code review"

change the commit message from #197 to #2949

pull request base branch is wrong


Fix panic when aggregator param is not a literal.

The return value for checkForSeriesSetExpansion
is always nil, simplify.
Fixes #5276
Signed-off-by: Brian Brazil<EMAIL_ADDRESS>

Fixes #5276

This seems to fix the problem. Can we also have a test for topk? LGTM otherwise.

:+1:

Can we also have a test for topk?
Done

:+1:


Add SemVer compatibility badge to README

Would you be up for adding a badge that shows how SemVer compliant / bug free new releases are? I was looking through the data we gather at Dependabot and realised we could put one together, so threw together the below. We've done a lot of moment.js upgrades already!

If you click through then there's a description of how it's calculated - basically it takes all of the relevant updates Dependabot has done for projects that use moment and checks what percentage of the time specs pass on the upgrade PR.
The score is slightly lower than 100% because some projects have flaky specs, but I'm working on filtering them out from the data, too :octocat:.

Coverage increased (+0.04%) to 94.691% when pulling 22d7727c135f87ea875a19e8fc0586d318aa090f on greysteil:add-semver-badge into 2e2a5b35439665d4b0200143d808a7c26d6cd30f on moment:develop.

Nice!


Add sequence-aware shutdown

Would you be able to rebase this on main? The main branch should be formatted now, so it'll make your changes easier to see.

@Tabrizian I don't think this will improve the BLS case, like the ensemble, it will try to send request to the inner model and the inner model will still reject the request (but with different error message). To allow BLS to complete the current request, the inner models will need to be aware of "who" is sending the request and not rejecting the request.


Add Mobile Link to Editor

Routing

[ ] Modify the initial app to accept different routes, look into: https://vaadin.com/learn/tutorials/lit-element/navigation-and-code-splitting or some other tool for routing.

Editor Changes

[ ] Create a unique link for each session of the editor
[ ] POST to https://ppng.io/ as is done in: https://github.com/karanganesan/model-viewer-bridge
[ ] NEW: POST the current model-viewer state as well.

Linking

[ ] Create a view for modelviewer https://modelviewer.dev/editor?id=UNIQUE_LINK
[ ] GET from https://ppng.io/ as is done in: https://github.com/karanganesan/model-viewer-bridge
[ ] NEW: Read model-viewer data from GET request

tagging @mounirlamouri for visibility


Captions not working in stories.

Bug Report
Form
Put an [x] if you meet the condition, else leave [ ].
Requirements

[x ] I've searched the Issues
[x ] I've read the basic concepts
[ x] I'm using the latest version
[ ] I've debugged my code using the DEBUG variable.

Platform

[ ] I'm using Node.js version YOUR_VERSION (node -v)
[ ] I'm using electron

Description
Captions not working in stories, the image is posted but without any caption.
YOUR DESCRIPTION HERE
Code
Add a meaningful section of your code here. If you are using TypeScript replace js with typescript.
(async () => {
  await login();
  const path = './story.jpg';
  const storyfile = await readFileAsync(path);
  await ig.publish.story({
    file:storyfile,caption:"foo"
  });
})();

API is older, may be that's why not working


Unable to install flannel on kubernetes 1.14.0 with error: error: SchemaError(io.k8s.api.autoscaling.v2beta2.MetricValueStatus): invalid object doesn't have additional properties

Unable to install flannel on kubernetes 1.14.0
Expected Behavior
kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/k8s-manifests/kube-flannel.yaml

Should setup flannel
Current Behavior
Failes with the following output
kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/k8s-manifests/kube-flannel.yaml
error: SchemaError(io.k8s.api.autoscaling.v2beta2.MetricValueStatus): invalid object doesn't have additional properties

Steps to Reproduce (for bugs)

Install k8s

yum install -y kubectl kubelet kubeadm

Init control plane:
kubeadm init --pod-network-cidr=<IP_ADDRESS>/16

kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:45:25Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

Attempt to install flannel

kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/k8s-manifests/kube-flannel.yaml

Context
I am setting up a new k8s cluster but my pods are lonely.
Your Environment

Flannel version:
latest master
Kubernetes version (if used):

kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:45:25Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

Operating System and version:

CentOS Linux release 7.6.1810 (Core)
Derived from Red Hat Enterprise Linux 7.6 (Source)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

cat: /etc/prelink.conf.d: Is a directory
CentOS Linux release 7.6.1810 (Core)
CentOS Linux release 7.6.1810 (Core)
cpe:/o:centos:centos:7

It may be that client kubectl (1.10.11)  differs from server kubectl (1.14.0) thus producing validation errors.
--validate=false flag might be helpful while applying kube-flannel.yaml
Just try this way kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/k8s-manifests/kube-flannel.yaml --validate=false

@stumanov I tried the same thing from the kubernetes master so the server and client matched version and got the same issue. Ill retry with --validate=false

@jspenc72 your init command should be
kubeadm init --pod-network-cidr=<IP_ADDRESS>/16

@stumanov I tried the same thing from the kubernetes master so the server and client versions matched and got the same issue. Ill retry with --validate=false

This omits the error but the overall status of the node is still NotReady with the output of sudo kubectl get pods --all-namespaces:
NAMESPACE     NAME                                 READY     STATUS    RESTARTS   AGE
kube-system   coredns-fb8b8dccf-5c4l7              0/1       Pending   0          1h
kube-system   coredns-fb8b8dccf-tvr49              0/1       Pending   0          1h
kube-system   etcd-k8s-master                      1/1       Running   0          59m
kube-system   kube-apiserver-k8s-master            1/1       Running   0          59m
kube-system   kube-controller-manager-k8s-master   1/1       Running   0          59m
kube-system   kube-flannel-ds-amd64-4bwmk          0/1       Evicted   0          3m
kube-system   kube-proxy-vnd8q                     0/1       Evicted   0          14m
kube-system   kube-scheduler-k8s-master            1/1       Running   0          59m

@seenitall I run into the same issue, kube-flannel and kube-proxy being evicted. I fix it by setting systemd as Cgroup driver of docker and Kubernetes
and executing the following as root:
modprobe overlay
modprobe br_netfilter
Setup required sysctl params, these persist across reboots.
cat > /etc/sysctl.d/99-kubernetes-cri.conf <<EOF
net.bridge.bridge-nf-call-iptables  = 1
net.ipv4.ip_forward                 = 1
net.bridge.bridge-nf-call-ip6tables = 1
EOF
sysctl --system
you can check this link for it:
https://kubernetes.io/docs/setup/cri/
I then perform,
1.) kubeadm reset (as root)
2.) copy the config file to ~/.kube
3.) kubeadm init --pod-network-cidr=<IP_ADDRESS>/16 (as root)
4.) kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
Host OS : Ubuntu 18.04
Kubeadmn and Kubectl client/server version: 1.14.1
Docker client/server version: 18.09.5

@stumanov I tried the same thing from the kubernetes master so the server and client versions matched and got the same issue. Ill retry with --validate=false

This omits the error but the overall status of the node is still NotReady with the output of sudo kubectl get pods --all-namespaces:
NAMESPACE     NAME                                 READY     STATUS    RESTARTS   AGE
kube-system   coredns-fb8b8dccf-5c4l7              0/1       Pending   0          1h
kube-system   coredns-fb8b8dccf-tvr49              0/1       Pending   0          1h
kube-system   etcd-k8s-master                      1/1       Running   0          59m
kube-system   kube-apiserver-k8s-master            1/1       Running   0          59m
kube-system   kube-controller-manager-k8s-master   1/1       Running   0          59m
kube-system   kube-flannel-ds-amd64-4bwmk          0/1       Evicted   0          3m
kube-system   kube-proxy-vnd8q                     0/1       Evicted   0          14m
kube-system   kube-scheduler-k8s-master            1/1       Running   0          59m

I have the same error on Ubuntu 16.04 with the following output from kubectl describe node
Name:               skyuuka
Roles:              master
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=skyuuka
                    kubernetes.io/os=linux
                    node-role.kubernetes.io/master=
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
                    node.alpha.kubernetes.io/ttl: 0
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Tue, 17 Sep 2019 00:06:18 -0700
Taints:             node-role.kubernetes.io/master:NoSchedule
                    node.kubernetes.io/disk-pressure:NoSchedule
                    node.kubernetes.io/not-ready:NoSchedule
Unschedulable:      false
Conditions:
  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------
  MemoryPressure   False   Tue, 17 Sep 2019 00:13:19 -0700   Tue, 17 Sep 2019 00:06:14 -0700   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure     True    Tue, 17 Sep 2019 00:13:19 -0700   Tue, 17 Sep 2019 00:06:29 -0700   KubeletHasDiskPressure       kubelet has disk pressure
  PIDPressure      False   Tue, 17 Sep 2019 00:13:19 -0700   Tue, 17 Sep 2019 00:06:14 -0700   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready            False   Tue, 17 Sep 2019 00:13:19 -0700   Tue, 17 Sep 2019 00:06:14 -0700   KubeletNotReady              runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
Addresses:
  InternalIP:  <IP_ADDRESS>
  Hostname:    skyuuka
Capacity:
 cpu:                44
 ephemeral-storage:<PHONE_NUMBER>Ki
 hugepages-1Gi:      0
 hugepages-2Mi:      0
 memory:<PHONE_NUMBER>Ki
 pods:               110
Allocatable:
 cpu:                44
 ephemeral-storage:<PHONE_NUMBER>750
 hugepages-1Gi:      0
 hugepages-2Mi:      0
 memory:<PHONE_NUMBER>Ki
 pods:               110
System Info:
 Machine ID:                 3087eb2f22d568d6800ce4c957a12a75
 System UUID:                4C4C4544-004C-3310-804D-B1C04F4B4232
 Boot ID:                    c090d61b-0ab4-4e20-a15d-897cfd086401
 Kernel Version:             4.4.0-47-generic
 OS Image:                   Ubuntu 16.04.6 LTS
 Operating System:           linux
 Architecture:               amd64
 Container Runtime Version:  docker://18.9.7
 Kubelet Version:            v1.15.3
 Kube-Proxy Version:         v1.15.3
Non-terminated Pods:         (4 in total)
  Namespace                  Name                                   CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE
  ---------                  ----                                   ------------  ----------  ---------------  -------------  ---
  kube-system                etcd-skyuuka                       0 (0%)        0 (0%)      0 (0%)           0 (0%)         6m36s
  kube-system                kube-apiserver-skyuuka             250m (0%)     0 (0%)      0 (0%)           0 (0%)         6m34s
  kube-system                kube-controller-manager-skyuuka    200m (0%)     0 (0%)      0 (0%)           0 (0%)         6m52s
  kube-system                kube-scheduler-skyuuka             100m (0%)     0 (0%)      0 (0%)           0 (0%)         6m40s
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests   Limits
  --------           --------   ------
  cpu                550m (1%)  0 (0%)
  memory             0 (0%)     0 (0%)
  ephemeral-storage  0 (0%)     0 (0%)
Events:
  Type     Reason                   Age                    From                     Message
  ----     ------                   ----                   ----                     -------
  Normal   NodeHasSufficientMemory  7m59s (x8 over 7m59s)  kubelet, skyuuka     Node skyuuka status is now: NodeHasSufficientMemory
  Normal   NodeHasNoDiskPressure    7m59s (x8 over 7m59s)  kubelet, skyuuka     Node skyuuka status is now: NodeHasNoDiskPressure
  Normal   NodeHasSufficientPID     7m59s (x7 over 7m59s)  kubelet, skyuuka     Node skyuuka status is now: NodeHasSufficientPID
  Normal   Starting                 7m39s                  kube-proxy, skyuuka  Starting kube-proxy.
  Normal   Starting                 7m37s                  kube-proxy, skyuuka  Starting kube-proxy.
  Normal   Starting                 7m6s                   kube-proxy, skyuuka  Starting kube-proxy.
  Normal   Starting                 6m36s                  kube-proxy, skyuuka  Starting kube-proxy.
  Normal   Starting                 6m5s                   kube-proxy, skyuuka  Starting kube-proxy.
  Normal   Starting                 5m35s                  kube-proxy, skyuuka  Starting kube-proxy.
  Normal   Starting                 5m5s                   kube-proxy, skyuuka  Starting kube-proxy.
  Normal   Starting                 4m32s                  kube-proxy, skyuuka  Starting kube-proxy.
  Normal   Starting                 3m5s                   kube-proxy, skyuuka  Starting kube-proxy.
  Warning  ImageGCFailed            2m59s                  kubelet, skyuuka     failed to garbage collect required amount of images. Wanted to free<PHONE_NUMBER>84 bytes, but freed 0 bytes
  Normal   Starting                 17s                    kube-proxy, skyuuka  Starting kube-proxy.

@seenitall I run into the same issue, kube-flannel and kube-proxy being evicted. I fix it by setting systemd as Cgroup driver of docker and Kubernetes
and executing the following as root:
modprobe overlay
modprobe br_netfilter
Setup required sysctl params, these persist across reboots.
cat > /etc/sysctl.d/99-kubernetes-cri.conf <<EOF
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-ip6tables = 1
EOF
sysctl --system
you can check this link for it:
https://kubernetes.io/docs/setup/cri/
https://blog.heptio.com/properly-resetting-your-kubeadm-bootstrapped-cluster-nodes-heptioprotip-473bd0b824aa
I then perform,
1.) kubeadm reset (as root)
2.) copy the config file to ~/.kube
3.) kubeadm init --pod-network-cidr=<IP_ADDRESS>/16 (as root)
4.) kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml
Host OS : Ubuntu 18.04
Kubeadmn and Kubectl client/server version: 1.14.1
Docker client/server version: 18.09.5
@nightcoder824
what is mean"copy the config file to ~/.kube"?
I run into the same issue,


Failed to add user extension while using gazelle

Describe the bug
When we start spark with user spark extension and gazelle, it will throw "Spark extensions are already specified before enabling Gazelle plugin: ".
To Reproduce
Start spark with use spark extension and gazelle, which means we would set spark.sql.extensions in spark-defaults.conf to another extension.
Expected behavior
This exception should only be thrown when user set spark.sql.extensions to GazelleSessionExtensions or ArrowWriteExtension.
Additional context
None

Assume it is already fixed. Please re-open it if necessary.


Self-signed SSL certificate is used on minetest.net (but not www.minetest.net)

Just letting you all know!

It seems minetest.net is a self-signed certificate whereas www.minetest.net is still a valid certificate signed by Let's Encrypt:
minetest.net

www.minetest.net

Bump :slightly_smiling_face:  The comment above is still relevant today (I just tried again).

minetest.net still uses the wrong cert.

Bump since this issue still is a problem

I tried to fix this and got rate limited by letsencrypt.org. Meanwhile minetest.net now has another self signed certificate.
Anyone know how long a ban I might have gotten?

Rate limit cooldown looks to have passed and... knew it, this time it worked!
Please check if it looks fixed to you all.

Working in Firefox 103:


WinUI 3 preview c# blank desktop app exception on launch "Cannot locate resource from 'ms-appx:///Microsoft.UI.Xaml/Themes/themeresources.xaml'"

created a new c# desktop project from the template, no modifications made, getting an exception on launch. using nuget package 3.0.0-preview3.201113.0, exception is not thrown after removing the line "XamlControlsResources xmlns="using:Microsoft.UI.Xaml.Controls" />" from the app.xaml.

@aoshiwik Do you see two projects in your solution ? Do you have the start up project as the package ?

Setting the package as the startup project fixed the issue.


Subset refactor

Fixes #164. Like suggested, I implemented a Subset class which factors out the logic of indexing/slicing through multiple data types, in the context of a subset of the data.
I refactored H5PYDataset and IndexableDataset to make use of Subset.
One of the main highlights of this implementation is that Subset does sanity checks on requests (e.g. making sure that a slice won't produce an empty or truncated output), which means that it would be safe to bring slices back into Fuel.
It also has the ability to merge two subsets in the most efficient way possible (e.g. two overlapping slices with step size of 1 would be merged into a single slice, as opposed to converted to a list, which is currently the case in H5PYDataset), and to detect when a list is a contiguous sequence and convert it into a slice. This behaviour could be expanded to accomodate more complex cases, if it's ever needed.

There is one tests failing which I'd like to have an opinion on. Right now the assumption for H5PYDataset is that if we pass it an unsorted list as subset in the constructor, this subset will remain unsorted. Subset breaks that, because it sorts list-based subsets and makes sure indices are unique. I was wondering if it was okay to remove this assumption altogether (and notify users via the mailing list), or if there's a use case for that which I haven't thought of.

I think if a user explicitly requests unsorted or duplicated indices, the result should either be an error, or the examples in the requested order. Returning the examples in a different order, or a different number of examples (in the case of duplication), could lead to all sorts of bugs that are hard to detect.
This could happen for instance if the user is iterating over several indexable objects at the same time, not all of which are HDF5Datasets.

It seems like there might be legitimate uses for returning the same example
twice...

Regarding unsorted / duplicate indices:

I feel like iteration schemes are better suited for iterating over a dataset subset in shuffled order. If the user wants to re-shuffle at every batch, ShuffledScheme is the way to go. I the user wants to shuffle only once before training, SequentialScheme's constructor accepts a list as its examples argument which can be used for that.
Allowing duplicates may make things very hard to debug. For instance, if the user merges two subsets which overlap, it may make the resulting subset unbalanced without the user noticing.

On the other hand, a user may want to sample examples with replacement, or explicitly include a subset more than once to compensate for an existing inbalance in the dataset.

@lamblin These issues can also be solved with iteration schemes.

@vdumoulin , I agree with you that the order of iteration should be defined by the iteration scheme, but it seems to me that the code from this PR does not preserve the order defined by iteration scheme requests. I think that it is okay to sort the indices of the subset, but requests might need more delicate handling.

@rizar and I talked offline. Bottom line: the code in the PR does preserve the order of requests.

@rizar Sorry about the delay. I think I addressed all of your comments. Would you mind having another look?

It is getting better and better! Can you please rebase it so that the test for Python 2.7 were run?

Anyone know if #244 is resolved by this PR?

@dwf #244 is resolved by this PR: the statement instantiating valid produces a dataset with 0 examples, and get_data raises
ValueError: slice-based requests cannot have a stop value greater than the number of
examples the subset spans (this would produce a return value with smaller length
than expected)

@rizar I caved in and simplified the nested ifs structure. I also factored out creating Subset objects.
I think I covered all of your comments, please let me know if there's something I forgot.

Okay, thanks! I updated the ticket description so that #244 auto-closes.

By the way, would it make sense to add the code in #244 as a test for this PR?

@dwf sure, I included a regression for that.

LGTM, great job!


Bug: Container does not honor PUID/GUID environment variable. Installation fails complaining about being run as root.

Describe the bug
When using the default docker-compose.yml file with docker-compose or podman-compose (rootless), the environment variables for PUID and GUID are not honored and installation exits complaining about being run as root.
Steps to reproduce

Download official docker-compse file
Set PUID/GUID to the output of id -u and id -g (manually)
docker-compose run archivebox init --setup

Screenshots or log output
compose file:
...
environment:
        - ALLOWED_HOSTS=*                   # restrict this to only accept incoming traffic via specific domain name
        # - PUBLIC_INDEX=True               # set to False to prevent anonymous users from viewing snapshot list
        # - PUBLIC_SNAPSHOTS=True           # set to False to prevent anonymous users from viewing snapshot content
        # - PUBLIC_ADD_VIEW=False           # set to True to allow anonymous users to submit new URLs to archive
        # - ADMIN_USERNAME=admin            # create an admin user on first run with the given user/pass combo
        # - ADMIN_PASSWORD=SomeSecretPassword
        - PUID=3330
        - PGID=3331

error:
podman run --name=databases_archivebox_tmp42009 -i --pod=databases --label io.podman.compose.config-hash=123 --label io.podman.compose.project=databases --label io.podman.compose.version=0.0.1 --label com.docker.compose.project=databases --label com.docker.compose.project.working_dir=/mnt/mpathh/{username}/databases --label com.docker.compose.project.config_files=docker-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=archivebox -e ALLOWED_HOSTS=* -e PUID=0 -e PGID=0 -v /mnt/mpathh/{username}/databases/data:/data --tty archivebox/archivebox:dev init --setup

[X] Error: Got PUID=0 and PGID=0 but ArchiveBox is not allowed to be run as root, please change or unset PUID & PGID and try again.
    Hint: some NFS/SMB/FUSE/etc. filesystems force-remap/ignore all permissions,
          leave PUID/PGID unset, disable root_squash, or use values the drive prefers (default is 911:911)
    https://linux.die.net/man/8/mount.cifs#:~:text=does%20not%20provide%20unix%20ownership

ArchiveBox version

I can't get version due to error preventing executing archivebox. But using latest docker image from 2024-03-13.

You have -e PUID=0 -e PGID=0 above in the command you shared, which superseeds any values set in docker-compose.yml.

Can you try again without those flags?

You have these flags -e PUID=0 -e PGID=0 above in the podman command you shared (which supersede any values set in docker-compose.yml).

Can you try again without those flags?

I'm not the one who is inserting those. That command is what is generated when I run docker-compose up.

Whatever is generating that command is your culprit, it's not controlled by archivebox.
I haven't used podman much, but it looks like it could probably be a podman configuration thing?

It's possible but i don't have any control over it. Podman is rootless, so anything that get  executed is not actually being run as root, but having PUID=0 in the container throws off archivebox i suppose.

ArchiveBox always drops down to a non-privileged user, we don't allow running it as root for security reasons.
If you pass a valid, non-root PUID (ideally >500, lower UIDs may behave strangely), it will set the archivebox user use that uid and drop down to that user to run the archiving processes.
Trying to explicitly set PUID = 0 is prohibited because the underlying archiving processes are not safe to run as root (too much shell execution->downloading->parsing RCE escalation risk).
https://github.com/ArchiveBox/ArchiveBox/wiki/Security-Overview#do-not-run-as-root

You reasoning is sound and i understand it, however this makes the docker solution unusable in my environment. I will look into how to disable this check.

As a workaround you can use docker exec instead of docker run / modify the entry point to not run ./bin/docker_entrypoint.sh. Youll need to also add --user=archivebox manually or user: archivebox.

I can't find any reference to PUID/PGID tampering in the podman-compose codebase, are you sure there isn't something else in your setup that could be causing this?
https://github.com/search?q=repo%3Acontainers%2Fpodman-compose+puid&type=code
What is the PUID/PGID you're intending to set (i.e. the result of $(id -u) in your screenshot)?
At this point I'm just genuinely curious how those vars are getting set, because as far as I know they're not "part of docker" they're just a convention created by linuxserver.io, so I'd be very surprised to see a docker alternative like podman or a container management environment like Proxmox/TrueNAS/Cloudron/etc. forcibly setting them.
Are you running in a special managed hosting environment of some kind or using an OS/container management solution that I could look into?
I'm going to close this for now since it's not really a problem with ArchiveBox per-se, but I do love devops spelunking and I am still curious, so if you're willing to share more about your setup I'd be happy to keep investigating and help find a solution in the comments here.

Hi, the issue is that this setup is not managed by me. It's managed by a provider, so unfortunately i can't provide you info beyond guesswork. All I can say is that I am not adding PUID=$(id -u) myself, and that I believe podman is indeed being run inside docker.


Network Error: Device Unreachable', 'Err': '905' on ubuntu

@jasonacox Hi Hows it going ?
I have a new device its a wifi plug but it says:
`DEBUG:TinyTuya [1.2.11]
DEBUG:status() entry (dev_type is default)
DEBUG:ERROR Network Error: Device Unreachable - 905 - payload: null
DEBUG:status() received data={'Error': 'Network Error: Device Unreachable', 'Err': '905', 'Payload': None}
{'Error': 'Network Error: Device Unreachable', 'Err': '905', 'Payload': None}
`
Even though the scan command found it and there is an entry for it in the tuya-raw.json file.
However the dps data has not gone to the snapshot file if that's any help.
Ps smart life works turning it on and off, I can also see it in iot toya dev site

Oh hey my bad I think i fixed it with a power cycle as i couldn't ping it with local ip address but i could with external one

I'll close this for now but feel free to re-open if there is an issue to raise.


Error level with dev/nodev

Hi, I think the error level should be displayed regardless of the dev/nodev option.
Thank you

@dgfmdrv  I'm very sorry, I didn't get the any notification by github.
Then, it is a  good idea，I had add forceLevel that would be regardless of the dev option


Update interactive_investigation.rst

The text starting at line 118 refers to proc twice but it should refer to opt and then to proc.

Thanks!


Split CI into Code & Markdown Lint

Splits the one CI job into two, one for Code CI and one for linting markdown. Just makes the CI a bit easier to understand and brings consistency with #163

I don't have strong opinions on this, up to Johan

There are two minor drawbacks as i see it:

The "on" config is now duplicated.
Might be harder to depend on success of previous jobs? e.g. "only tag release if all test jobs were successful". But we could always just move it back when/if we run into that i suppose.

There are two minor drawbacks as i see it:

The "on" config is now duplicated.
Might be harder to depend on success of previous jobs? e.g. "only tag release if all test jobs were successful". But we could always just move it back when/if we run into that i suppose.

Yeah, can't do much about duplicating the "on" config, at least it's pretty simple.
We can actually use "on" the completion of another job, so if we wanted to lint markdown etc before release we could include that alongside the "Code" workflow. The only issue with this is that github doesn't render a line in the awaiting checks until the previous workflows complete, but this isn't a huge issue, especially not for releases


scripts\npm install fails on Windows 10

I'm trying to install the source code, but I hit a number of errors at the "scripts\npm install" phase, starting with the below.
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\jongg\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "run" "compile"
npm ERR! node v4.2.6
npm ERR! npm  v3.6.0
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>compile: tsc -p .
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>compile script 'tsc -p .'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the vscode-json-server package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     tsc -p .
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs vscode-json-server
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls vscode-json-server
npm ERR! There is likely additional logging output above.

I'm not able to reproduce this. I see you use node 4.2, I also tried with that and it works.
Can you cd vscode\extensions\json\server and run npm install there?
This should install node_modules\.bin\tsc which is then used in the postinstall action.

Thanks!
So if I followed your directions to manually run npm install from that folder, no errors. Then when I run scripts\npm install again, it works!
Maybe this issue only affects new/unused repos?
From: Martin Aeschlimann<EMAIL_ADDRESS>Sent: Monday, February 1, 2016 6:50 AM
To: Microsoft/vscode<EMAIL_ADDRESS>Cc: jayongg<EMAIL_ADDRESS>Subject: Re: [vscode] scripts\npm install fails on Windows 10 (#2594)
I'm not able to reproduce this. I see you use node 4.2, I also tried with that and it works.
Can you cd vscode\extensions\json\server and run npm install there?
This should install node_modules.bin\tsc which is then used in the postinstall action.
—
Reply to this email directly or view it on GitHub https://github.com/Microsoft/vscode/issues/2594#issuecomment-178000792 .  https://github.com/notifications/beacon/AKhX-f9rfcS3BYHsUmv9z9UhGw9PmLG8ks5pf2gzgaJpZM4HQKtM.gif

I tested with a clean repo, and it works. Also so for no one else has seen that error.
Strange.

Thanks.  Consider this closed.  Much appreciated.


Fix default recipe to reference correct resource names

Description
Fixing the default recipe to reference updated resource names.
Issues Resolved
#261
Contribution Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable

This change is

Awesome, thank you I will merge asap.


Free trial?

Is your feature request related to a problem? Please describe.
The app looks nice, but for $23 it's very pricey - especially when combined with the lack of trial.
Describe the solution you'd like
It would be good to at least have a free trial version available to test out.
Describe alternatives you've considered
Another option might be to reconsider the pricing model, $23 is a lot of money for a relatively simple app.
Additional context
Add any other context or screenshots about the feature request here.

Hey Sam - you're right, it's too pricey.  I dropped the price a bunch, let's hope that lets more folks try it out. I'll look into a free trial too!
In the mean time, here's a one-time promo for you (I looked for your email address and could not find it on your website, etc).
TNRJWH43XWJX

Hey Eric!
Oh wow that's awesome, thank you so much for the code - I'll definitely be trying it out this week and I'll drop you a donation or buy it for a friend if I find it useful.
I see the price is now $15 on the AU store - I think that's far more reasonable, thank you for considering this.

No need to worry about a donation or buying it, I appreciate the feedback and the time it took you to do so!

Thanks Eric, I'll definitely log some feature suggestions, if you don't agree with any of them please just feel to close them - I don't want to be demanding 😅.
(I'm completely new to 3d printing but within just a few days I've amounted a huge mess of files across multiple devices - I have a few ideas on what might help.)

This is exactly what led me to build Depot! To be honest, Depot pushed the limits of the available technology in macOS at the time of coding, and now that things have moved forward, I may go back and rebuild some large portions, so feedback is welcome!

Hey @destari I've had a bit of a play and I've got quite a few ideas.
I don't want to overwhelm you, come off as demanding or spam the issues - I was thinking perhaps I'd just create one issue for feature suggestions and then you could pick which ones (if any) you'd like individual issues / feature requests for - does that work for you?

Yea that works for me - as long as it is pretty clear what you are thinking, why, etc, and for any issues (bugs) call those out as clearly as you can.
Thanks!


Statsig justin patch 1

🚀 Deployed on https://66a17dd62472e259e547b04f--cozy-fox-0defec.netlify.app


Require compliant devices for Android webview

If we have this condition access policy and it Require compliant devices. Is it possible to satisfy this condition, we are performing the authentication for the web application in Android webview ?
Note - Have a Android native app, which is trying to open a SharePoint in webview and they also have conditional access policy with condition require compliant device.

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

ID: 5c01b1bb-61e2-96ff-8d9f-a9ad3ab8b5a4
Version Independent ID: d9677f14-5bab-4760-e6aa-0254deb6cea1
Content: Conditional Access - Require compliant devices - Azure Active Directory
Content Source: articles/active-directory/conditional-access/howto-conditional-access-policy-compliant-device.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@Visinghr Thank you for a quick discussion offline. As checked you would need to confirm if this is something feasible and if this can be update in current document. I will engage the Author to comment on that.

@MicrosoftGuyJFlo John, can you please look into this and see if this can be updated in the current document.

It would depend on how the device is configured. If this is still an issue I would raise the question to support. #please-close

It would depend on how the device is configured. If this is still an issue I would raise the question to support. #please-close


16 - CSS:  (Show) Style list of existing shows.

Style list of existing shows displayed on shows page.

completed


Latest Release Breaks SVN Integration

Issue Type: Bug
After installing the latest release the SVN icons are no longer apearing. There are 'placeholders' where the SVN actions icons were located in the source control tab, and the tooltips still appear when the mouse is moved over the placeholders, but the actions no longer work.
 Please update and see if your issue remains.

Update: it seems 1.56.1 was a security update. The fix I think you're looking for will be in 1.56.2

Can you reproduce this in the insider release?

Hi,This is now fixed in v1.56.2Cheers, PhilSent from my Galaxy
-------- Original message --------From: João Moreno @.> Date: 17/5/21  04:04  (GMT+10:00) To: microsoft/vscode @.> Cc: phila213 @.>, Author @.> Subject: Re: [microsoft/vscode] Latest Release Breaks SVN Integration (#123623)
Can you reproduce this in the insider release?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.


Ascom cannot import bundled assets on legacy circumstances

Please verify the version of auro-dropdown you have installed
v2.9.9
Please describe the bug
We're looking to import the auro-datepicker, auro-combobox &  auro-dropdown into the homelet on the Ascom homepage.
https://github.com/Alaska-ECommerce/AlaskaAirCom/blob/users/anikris1/auro/Source/Sites/alaska/Areas/BEX/Views/BEX/hotelFormlet.cshtml
script tag doesn't seem to import assets after page load event as this is invoked as a Ajax request. so
we're packaging these assets in CH, but running into issue where auro-dropdown isn't mounted as shown :

Reproducing the error
None
Expected behavior
auro-dropdown should get imported and rendered.
What browsers are you seeing the problem on?
Chrome
Additional context
No response

This is in continuation from https://github.com/AlaskaAirlines/auro-datepicker/issues/129

@anikris1  and @rdasan-alaska, please add more context regarding how you install these dependencies and your expectations. Running a local test using the CDN installing method, I can not repro an issue with the auro-dropdown element.

@blackfalcon we did it in ComponentLibrary https://github.com/Alaska-ECommerce/ComponentLibrary/blob/users/anikris1/auro-import/components/shared/auro-components.js

npm i

npm run build

@anikris1, when we last discussed, we agreed that using the component hangar to import auro into the modern environment is an antipattern. Is there a reason why we chose to move forward with that strategy I'm not aware of?

@gusnaughton as mentioned script tag doesn't seem to import assets after page load event as this is invoked as a Ajax request. cc: @rdasan-alaska

Is there a page or branch where we can see this issue + help investigate?

@anikris1 , we have recently changed how we are bundling our dependencies on the beta branches of these components.  Are you still encountering this issue?  And if so, could you please try with the Beta versions of Dropdown, Datepicker, and combobox?

This issue will be solved by the rebuild of the homepage.  If there are any other instances of this happening in the monolith, please create new issues.


Nothing happens after ng test is successfully run

Hello, I am trying to make run your precommit hook on this environment:

angular 2.3.1
jasmine-core 3.3.1
karma-jasmine 1.0.2
karma 1.2.0
pre-commit 1.2.2
W10

When I run git commit the test pass successfully but then nothing happens.

This wasn't a pre-commit problem, it came from the fact that ng test watch the files by default.
I needed to add this script to my package.json :     "test-once": "ng test --watch=false",

Thanks for the update <3


E-Mails with uppercase letters are rejected on signup

/api/v1/users/register returns status code 422 (unprocessable entity) if the email contains uppercase letters.

In my opinion, the backend should store lower(signup_email) in the database. When a user tries to login, the stored email should be compared to lower(login_email).
select * from users where email=lower($LOGIN_EMAIL);

@Nick-Triller the referenced PR should solve this, thanks for reporting it.


Holder and friends removal

Coverage remained the same at 100.0% when pulling 63ecdd4371743fbc4afa8c7e1c7eb927982f4b64 on holder_removal into 4d40afef74ecf986e2df86075ff259e1e844feb8 on master.

Coverage remained the same at 100.0% when pulling 63ecdd4371743fbc4afa8c7e1c7eb927982f4b64 on holder_removal into 4d40afef74ecf986e2df86075ff259e1e844feb8 on master.

Delay merge until https://github.com/ba-st/Willow/pull/23 is merged in master.

Coverage remained the same at 100.0% when pulling 20c68940fec6496fb76a2100af8b39f81b6a2724 on holder_removal into 0ab47f960a22accadf1b733519f3a23cc34a928d on master.


Please add js css minify options to the project context and not only globally

The problem is, I enabled the "Minify on save" because I used this in a project, but after using an other project, it minifies too but this is wrong from my expectation. Yes the feature has ONLY global options which is not good, because there are a lot of cases, where you use js css minify with this plugin in specific projects and in other cases you use a build tool like grunt or gulp or normal npm scripts. So please remove those things from the global options and add it to the project context to project properties. This make more sense. Maybe you can have it inside options too for defaults and override it from the project properties.
Regards
Chris

duplicate of #23


Upkeep error

Hi @tobymao!
Out of nowhere, our saq process started emitting Upkeep task failed unexpectedly errors, where the exception logger contains the following traceback:
Traceback (most recent call last):
  File \"/opt/venv/lib/python3.11/site-packages/saq/worker.py\", line 180, in poll
    await func(arg or sleep)
  File \"/opt/venv/lib/python3.11/site-packages/saq/worker.py\", line 167, in schedule
    scheduled = await self.queue.schedule(lock)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File \"/opt/venv/lib/python3.11/site-packages/saq/queue.py\", line 248, in schedule
    return await self._schedule_script(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File \"/opt/venv/lib/python3.11/site-packages/redis/commands/core.py\", line 4983, in __call__
    return await client.evalsha(self.sha, len(keys), *args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File \"/opt/venv/lib/python3.11/site-packages/redis/asyncio/client.py\", line 487, in execute_command
    return await conn.retry.call_with_retry(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File \"/opt/venv/lib/python3.11/site-packages/redis/asyncio/retry.py\", line 59, in call_with_retry
    return await do()
           ^^^^^^^^^^
  File \"/opt/venv/lib/python3.11/site-packages/redis/asyncio/client.py\", line 463, in _send_command_parse_response
    return await self.parse_response(conn, command_name, **options)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File \"/opt/venv/lib/python3.11/site-packages/redis/asyncio/client.py\", line 505, in parse_response
    response = await connection.read_response()
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File \"/opt/venv/lib/python3.11/site-packages/redis/asyncio/connection.py\", line 963, in read_response
    raise response from None
redis.exceptions.ResponseError: user_script:12: too many results to unpack script: 15c892840ce49156b99eaf77c367913a8c069ed5, on @user_script:12.

Not sure if this is really a saq issue, but any ideas as to what could be wrong? I've flushed scripts in the redis instance, but the problem persists.

Looks like it's failing on this line calling RPUSH.
Flushing all records in redis solved the problem. Is it possible that RPUSH will return multiple items in some cases, or that the number of arguments it can receive is limited?

how many jobs are you trying to schedule? perhaps you could batch them up?

this could be a limitation in lua? https://stackoverflow.com/questions/35582647/whats-the-maximum-values-accepted-by-redis-lpush-list-operation
it seems like you can do at least 100k, can you confirm how many values you're trying to schedule?

It's possible we've exceeded 100k. Seems to be non-saq related. Thanks @tobymao :+1:

I'm facing this issue when I accumulate 22k tasks scheduled, is there any workaround for this or it's just not viable for scheduling that many tasks?

it seems like maybe we need to update the schedule script to batch this up. feel free to create a PR for this, it shouldn't be too difficult but i don't have the bandwidth for it.

playing with ChatGPT I got this:
        redis.call('SETEX', KEYS[1], ARGV[1], 1)
        local jobs = redis.call('ZRANGEBYSCORE', KEYS[2], 1, ARGV[2])
        local limit = 8000  -- Adjust limit based on your environment's capabilities

        local start_index = 1
        while start_index <= #jobs do
            local end_index = math.min(start_index + limit - 1, #jobs)
            local scores = {}

            for i = start_index, end_index do
                table.insert(scores, 0)
                table.insert(scores, jobs[i])
            end

            redis.call('ZADD', KEYS[2], unpack(scores))
            redis.call('RPUSH', KEYS[3], unpack(jobs, start_index, end_index))
            start_index = end_index + 1
        end

        return jobs
    end

First it created this:
if redis.call('EXISTS', KEYS[1]) == 0 then
    redis.call('SETEX', KEYS[1], ARGV[1], 1)
    local jobs = redis.call('ZRANGEBYSCORE', KEYS[2], 1, ARGV[2])

    if next(jobs) then
        for _, v in ipairs(jobs) do
            redis.call('ZADD', KEYS[2], 0, v)
            redis.call('RPUSH', KEYS[3], v)
        end
    end

    return jobs
end

But this would add too much overhead because it's doing a call for each item without batching, I don't know if the first code is valid because it failed on my tests at the moment, maybe the 8k limit is too high, i'll keep testing

why don't you make the limit 1000?

please don't submit any chat gpt code that you don't fully understand. you can use it as a starting point, but you should deeply understand the reasoning behind every single line of code that you submit in the PR.

that's why I didn't submit the PR :), I started using the library a week ago, so untill today had no idea what this code did, or how the scheduler works etc

why don't you make the limit 1000?

still, I thought that if I understood correctly to get the less calls possible the idea would be to batch them as big as the limit is no?

yea, i guess find a reasonably large number.

i decided to do the simple approach, it's only 10% slower on a million jobs, taking around 4 seconds. i don't think it's worth the complexity of the lua script since i don't know lua very well.
this is released in v0.12.5
https://github.com/tobymao/saq/commit/314314a1d624b4a08deb1b89ef8a632d0a4c6226


Deployment issue - Step 5 unblocking provisioning folder

Trying to deploy the Teams EOC solution. At Step 5 - unblock the deployment script, I run into the following issue:

Hi @kkay82,
Thanks for reaching out to us. Please allow us some time and we will get back to you on this.
Thanks.

@v-saikirang Disregard, chatted with Josh and all deployed!


Allow off[Value|Error|Any|End] functions to have a zero argument that clears all callbacks

For the off~ equivalent to on~ functions, a callback is needed to unregister the function used as the onValue callback.  This requires a seperate definition of the callback or function definition as a reference to use in the offValue function.  a simple preferred scenario is something like
let mouseClick = Kefir.fromEvents(document.body, 'click').onValue((evt) => console.log(evt.target))
mouseClick.onValue() //<--This should unregister the anonymous function

For a simple scenario where it would be more terse to use an anonymous function in the on value, onValue should provide a zero argument equivalent that clears the callback (and possibly others).

I don't think this is a good idea. This will break the guarantee that only the module that have added a subscription can remove it.
But we have plans for better subscription methods: https://github.com/rpominov/kefir/issues/151
It will look like this:
let unsub = Kefir.fromEvents(document.body, 'click').observe((evt) => console.log(evt.target))
unsub()

What do you think?

That would be a good solution.  I guess in the mean time I can write up a simple unsubscribe function for my implementation via
clickTest.offValue(mouseClick._dispatcher._items[0].fn).

Ok, I think we can close this then.


Design improvement for shortcut guide

This is a possible solution for the lack of space for new shortcuts ( #179 ).
When holding Win only show shortcuts with single keys. When pressing either Shift, Alt or Ctrl display all options including those keys (and hide those, not requiring the specific key). Hint the user to try that.

I think we have the same idea. Didn't see this issue before, probably because it is old and pushed away by the new issues. Here it is in my words...
There is no way to collect all the possible combinations on one page, that is clear.
You can make the Guide dynamic. If you press the Win key, you first see all the combinations that start with that single key. With a label like "Win + ..." at the top to make this more clear. Then, when you also press down Shift, for example, you see the possible combinations that start with "Win + Shift + ..." Same idea for the other keys/combos.

@gnaatz @Jay-o-Way
please add you suggestions to https://github.com/microsoft/PowerToys/issues/890


add <projectDir>/docs/indextoc.sh, which is equivalent to cd docs; ./adoc2md.sh -t

No, I don't need this. I would just type $ ./adoc2md.sh -t


Old Spotify used to support browsing and now doesn't

This is a weird bug. Browse used to work with this old Spotify version, and then the only thing that changed between when I know it worked and now is that I did a pending Android update. I was on 9, and am still on 9, but with the Dec 2019 security update. It might have worked since the update, I don't recall exactly when it stopped working because I don't use Browse often. This app detects that it supports browsing, but under browse, it now says No Data. Maybe some Samsung crapware updated and it thinks it's blocking something for security?
Maybe this is a non issue since I see you are soon to replace the Spotify integration, but thought I'd file the bug anyways just in case someone did have this happen.

One thing to check is whether it automatically upgraded your Spotify to the latest version from the store, even though you manually installed the old version. In which case, you'll need to uninstall the store version and reinstall the older version.
Alternatively, you could try testing the new app version with Spotify API support! Sentry or nonalytics

The new version of the app has been published, bringing the new Spotify API method for browsing. I think this provides another way to solve this bug, so I'll close it for now.


this._ir.once is not a function

Do you want to request a feature or report a bug?
bug

What is the current behavior?

rails/webpacker#570
source code: https://github.com/AirDwing/vuetify-demo
If the current behavior is a bug, please provide the steps to reproduce.

have no idea
What is the expected behavior?
perhaps it's related to devserver
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

node v8.1.4
webpack 3.5.1
webpack-dev-server 2.7.1

@webpack-bot move to webpack/webpack-dev-server