Library does not run on Python3

Hey guys,
This library is only running on Python2, the init part gives following error on python3, let me know if someone can help me.
`Python 3.5.2 (default, Nov 23 2017, 16:37:01)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.

from helium_client import Helium
helium = Helium("/dev/ttyS5")
Traceback (most recent call last):
File "", line 1, in
File "helium_client/_helium.pyx", line 128, in helium_client._helium.Helium.cinit (helium_client/_helium.c:2066)
TypeError: expected bytes, str found
`

the following works, but a bit weird lol
helium = Helium(b"/dev/ttyS5")


Ingest folder wide search

Description
A new feature to search/manipulate some text throughout the CSV files present in the ingest folder.

Hey @techsavvyash, I have added this feature in the File Validator project of Cqube, so that I could test it in a controlled environment with limited CSV files. It looks good to me, You can check the feature  here. If everything looks fine, I'll add this feature here.

or shall i just add the code here and make a pull request ?

Hey @masterismail,
There is already #119 open for this, can you built and on top of that and fix that same PR?
Thanks

yup, will do it !


Container topology cleanup - remove unused code

@miq-bot add_label wip
@miq-bot add_label ui
@miq-bot add_label providers/containers

@miq-bot remove_label wip

@martinpovolny @himdel please review. thanks
I don't see how coveralls indicator is correct here, I think it's safe to ignore it.
Same goes for Hakiri that warns on code that wasn't touched in this patch


Not able to jailbreak

I have been trying to jailbreak my iPhone on every public version of Dopamine, the results are always the same.
Some attempts to jailbreak cause the device to boot for a long time (tries to boot then restarts while booting) before returning to ios.
Those times when the device takes longer to boot change the success ratio but no jailbreak is achieved ( the button always says jailbreak).
I have had hundreds of attempts to jailbreak across versions, removing jailbreak, turning tweak injection on/off, restarting/not restarting before jailbreak attempts but nothing seems to work.
I have attached some panic and reset logs. I have more logs if needed.
Thank you.
Logs.zip

Never seen the kernel data or static panics but the userspace panic will be mitigated in the next release. For now you can Jailbreak while holding volume up to enter safemode then you will have to diagnose which tweak is bad.

@

Likely caused by you having installed Sileo or Zebra via TrollStore, remove it from there.


DA-350: Pillow Fight should support Scope & Collection

i have indented the PillowFightDialog manually now. 9e7369ea98e641b8ca70ea1a40485dae062efa5c
Working on point 3 to restore the scope and collection previously.


Resize not reported for particular case where listener element is in flex layout

Please see this Plunker.  It is based on one of your examples, but partially replicates the UI of a component in an app my team is developing.
Note how the reported width stays the same after resizing the window.  However, if the display style of the first div is changed to block, the reported width changes with each resize.  Also, if you instead remove the div with the explicitly specified size (or, just remove the size), the reported width changes with each resize.
Is this a bug, or is it a case your package is not designed to handle?

HI and thanks for the question. You are not getting any resize events since the element you are listening to does not change size when you resize the window. If you want the element to resize you'll need to review your layout.


Feature: line markers with long text labels

Hello and thanks for the "labels to line markers" feature which is very useful: https://expressive-code.com/key-features/text-markers/#adding-labels-to-line-markers
I have an example where my annotations are in the form of:
// 1. Register the ContentsquareWebViewController by mapping InAppWebView's controller
{lines of code}
// 2. Register the javascript channels
{lines of code}
etc.
If I try to port these with the current syntax...
```dart {"1. Register the ContentsquareWebViewController by mapping InAppWebView's controller": 8-18})

..the text will overlap the code.

I'm used to working in AsciiDoc, which can handle these cases as follows (see example 54 right below the anchor target).
Is there something I missed or was this not the intent or the original version of the feature?
Do you have any idea how I could work around this without working around the feature?
Thanks!

Hehe, interesting use case!
The original intent of these labels is for them to be very short, as shown in the example in the docs:

So, in your case you would just make the label "1" without any additional text, and then put a numbered markdown list below your code block in markdown where you explain what to do.
It's interesting to see the AsciiDoc example which seems similar to footnotes. This could be another new feature. 😄

No personal preference on foonotes vs. the inline labels.
With footnote style annotations you have to go back and forth but it might be cleaner with dense blocks.
Also, I actually skipped the note in your screenshot but I assume adjusting the setting could mess up some occurrences while fixing other ones (long vs short labels) ?

Yes, adjusting the codePaddingInline setting increases the space available for annotations on the sides of all code blocks. This is meant to allow slightly longer labels, e.g. 2-3 characters instead of just 1.
This would not work for your example though, because making the side paddings so large to fit these long labels would lead to a ton of wasted space in all code blocks.
I think your use case would be better solved with custom annotations that have their own line. Basically a way to convert some special comment syntax right inside a code line to a styled box. This would make a great optional plugin!

Alright! Thanks for your feedback 👍
I updated the issue description, let me know if we need to do anything for now.

Actually, I just realized while looking at the code that this is already possible with the current implementation! :) All you need to do is add an empty line at the beginning of the line range to reserve space where the label should appear. I've added an example to the docs on how to do it:
https://expressive-code.com/key-features/text-markers/#adding-long-labels-on-their-own-lines
Does this solve your use case?

I found this by testing myself — found the EC docs only today and again missed that :|
If this is an official way of doing this then yes it works for me :)
Thanks again!

Don't worry about missing that, I just added this example right now based on your use case! You couldn't have found it before. 😄
I realize that adding empty lines to reserve space isn't the most elegant solution, but it works for now and will continue to work. I have a feature planned that unlocks various cool inline comment syntax possibilities that will become a better solution for this use case as well and that doesn't require you to count line numbers. Stay tuned for future versions! :)
Closing this for now as there's a solution available.


forms: change to new form style

[x] employee
[x] farm
[x] abattoir
[ ] task. add react-bootstrap to form

old farm form

old abattoir form

old task form


Use the k8 cert-manager

With the new outlined here we should be using cert-manager to take care of the certificates.
From the docs, we need to add cert-manager.io/cluster-issuer: "letsencrypt-prod" to the ingress.

This was done in 1a08ec73f1eb0a376a5b5c63b1f5f470a70a6717. In the event log below, we can see the successful cert creation from the cert-manager
Name:             gnis
Namespace:        gnis
Address:          <IP_ADDRESS>
Default backend:  default-http-backend:80 (<error: endpoints "default-http-backend" is forbidden: User "system:serviceaccount:gnis:gnis" cannot get resource "endpoints" in API group "" in the namespace "kube-system">)
TLS:
  ingress-nginx-tls-cert terminates stage.gnis-ld.org
Rules:
  Host               Path  Backends
  ----               ----  --------
  stage.gnis-ld.org
                     /   gnis:80 (<IP_ADDRESS>:80)
Annotations:         cert-manager.io/cluster-issuer: letsencrypt-prod
                     nginx.ingress.kubernetes.io/cors-allow-credentials: true
                     nginx.ingress.kubernetes.io/cors-allow-methods: GET, POST, OPTIONS
                     nginx.ingress.kubernetes.io/cors-allow-origin: $http_origin
                     nginx.ingress.kubernetes.io/enable-cors: true
                     nginx.ingress.kubernetes.io/rewrite-target: /
Events:
  Type    Reason             Age               From                      Message
  ----    ------             ----              ----                      -------
  Normal  Sync               8s (x7 over 28d)  nginx-ingress-controller  Scheduled for sync
  Normal  CreateCertificate  8s                cert-manager              Successfully created Certificate "ingress-nginx-tls-cert"


Problem with user update

Hello I installed ciims through vagrant. Everything seems ok but I have this strange problem. I created a new user and after that I tried to change his personal details from User to collaborator, author or everything else. After update user button the spinner does a short cyrcle and after that it stays like that. If I change to another user / tab and come back again everything are as initally (After the creation)

Hi @whsecurity,
Sorry for the trouble. It looks like some debug code got pulled in whenever the last merge occurred. It should be patched now. You can correct it inside the Vagrant box either by:

SSH-ing into the box and updating the source code

vagrant ssh
cd /var/www
git pull

Or by destroying and re-provisioning the box

vagrant destroy
vagrant up --provision

That should resolve the issue for you.

After the
vagrant destroy vagrant up --provision
I encounter this error

CDbException

CDbCommand failed to execute the SQL statement: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'root.configuration' doesn't exist
Any Ideas?

The box doesn't appear to be provisioned. Make sure the vagrant up --provision task actually provisions the box. After running vagrant destroy that the box is fully destroyed in Virtualbox before bringing the box back up.

@whsecurity,
Were you able to resolve your issue?


Broken with 4.03.0

I have this issue:
File unavailable: typerep.install
I also have the same issue with sexplib and typerep, both on 4.03.0.

Do you mean ppx_core.install?

Yep. Sorry.

What version of jbuilder and ppx_core do you have?

On 23/12/2016 13:24, Jérémie Dimino wrote:

What version of jbuilder and ppx_core do you have?

Both 114.20+69

What's the output of jbuilder -drules ppx_core.install?

On 23/12/2016 14:57, Jérémie Dimino wrote:

What's the output of |jbuilder -drules ppx_core.install|?

I can install those packages when pinning them. Seems an OPAM problem (I'm using
opam2).
Upstream bug report: https://github.com/ocaml/opam/issues/2799


Recipe books

About the PR
adds a system of forgotten recipes. To craft such things, you must first study a special book that unlocks these recipes.

[x] storing learned recipes in the mind
[x] learning new recipes
[x] prevents from crafting unlearned items.
[ ] a system that hides recipes from the player that he has not yet studied
[ ] a small portion of content in the form of new crafting recipes, and books that teach these recipes.

Why / Balance
PR as part of the system for the future librarian rework
https://github.com/space-wizards/docs/pull/173
Media
https://github.com/space-wizards/space-station-14/assets/96445749/3d5b9ab9-2e95-4c00-90e9-57e70b253bf0

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
later
:cl:

add: Added fun!

tiders when they can't craft 8000 bats roundstart:

Time to raid the library like it's Project Zomboid :trollface:

love this, but I fear books being stolen or hoarded, perhaps a printing press machine that is librarian locked that can print copies for a price? A cheap price but a price. late join librarian could mean a RANSACKED library so yeah, also book loaning and just filling up spares would be nice using the press.

I think that all libraries will have to be rebuilt, perhaps blocking half of the bookcases behind librarian access.  So he can have more personal space to work with books

love this, but I fear books being stolen or hoarded, perhaps a printing press machine that is librarian locked that can print copies for a price? A cheap price but a price. late join librarian could mean a RANSACKED library so yeah, also book loaning and just filling up spares would be nice using the press.

Let librarians print books maybe

Sound like a real work for librarian! Hit book thiefs, keep the library is clean, and give people recipes

Does this work for construction as well (e.g need to read a book to build a girder)? Also can we make the book consumable somehow? This would be fantastic for downstream!

this kinda open pandora's box of, imagine role starting knowledge like, Engineers round start can make walls and grilles but nobody outside of engie can unless they learn it from the library.

Not for SS14 that would be a slippery slope indeed but it would be nice for downstream which is exactly what you described. In CM-13 only certain roles can build stuff (e.g only ComTechs and engineers can build barricades and set up APCs) but your average marine can't.
I was thinking of a way to do this in CM-14 when bam this PR showed up! It is cool if you don't get to it though, just would be nice to have the options and flexibility if you ever get to it. Sorry for sort of derailing this.

this kinda open pandora's box of, imagine role starting knowledge like, Engineers round start can make walls and grilles but nobody outside of engie can unless they learn it from the library.

I would imagine this isn't the use case.  All current crafts wouldn't be included (weapons, walls, etc). The same would go for most future crafts. This is more for specific cases - like an improved maint shotgun or maybe antagonist exclusive construction.

love this, but I fear books being stolen or hoarded, perhaps a printing press machine that is librarian locked that can print copies for a price? A cheap price but a price. late join librarian could mean a RANSACKED library so yeah, also book loaning and just filling up spares would be nice using the press.

give all library books a GPS tracker, and librarian gets a computer to track down any book with a tracker in it?

maybe later


Update README.md

Added an example

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: [Pull request #111 opened]

Start Time: 2020-10-29T16:42:45.506+0000

Duration: 14 min 1 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
42

Skipped
0

Total
42


BUG: Don't overwrite b in lfilter's FIR path

Fixes a small bug introduced in #4628.  I've left it unmarked, but this would be good to backport if a 0.16.1 were going to happen.  It could potentially break things and is a regression from 0.15.

I don't think this is a small bug.
statsmodels won't be affected because a[0] and b[0] are 1 in all our applications, AFAIK.

Rebased following #5118.

This has had 11 days.  I'm going to merge it.  It fixes a real bug.

Thanks @ewmoore. Backported in bdabe45


swap: change randomEncryption to plainOpen

Motivation for this change
Instead of creating a luks container with "secretkey" as password, decrypting it and removing the luks header, it's much easier and faster to use plainOpen with /dev/urandom. And you also get some bytes more swap because you have no luks header.
That's the way it's often done and proposed in other linux distributions.
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Thanks! TBH I did it the way it is now only because I didn't know better.
I'll test and merge it later if noone beats me to it.

Just some more information:

luksFormat needs at least 2 seconds to hash the password (see cryptsetup --help for --iter-time, default is 2 seconds)
plainOpen uses absolutely no header, therefore the whole space of the partition is used for swap
using /dev/urandom as password is much better than a static pasword, even in the luks method the luks header was removed and therefore the master key lost forever
luks defaults to aes-xts-plain64, plain defaults to aes-cbc-essiv:sha256
But I'm thinking about to add a new config option to let the users modify this, because I personally like Serpent and Twofish more than AES. Also on some low-end devices Serpent and Twofish can be faster than AES, which is nice-to-have for swap.

Let's forget about this one and focus on the better one: https://github.com/NixOS/nixpkgs/pull/25999


Data Science with Python : Outliers Detection

Description 📜
Complete Outliers Detection Explained, What are Outliers, different methods to detect, causes of outliers along with codes to describe how to remove the outliers #381

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Datascience with Python

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

You're not supposed to close your PR's instead you could say me to do so. @Vidit-Ostwal

Sorry, making a new one felt easier than fixing this one,
Didn't knew to not to delete the PR,
I have also closed that LightGBM PR and made a new one. (did before reading yoyr comment)
Won"t happen next time


Prediction: typo fixes

FYI @natashadsouza re-targeted my branch to the 3.0 branch as advised.Thanks!


xmonad-extras no longer builds

Issue description
Something weird is going on with xmonad-extras and because I am largely unfamiliar with the Haskell infrastructure, I don't really know how to fix it.
It requires xmonad as a dependency but seems unable to find it. (despite the derivation pulling it in)
λ nix-build -A haskellPackages.xmonad-extras
these derivations will be built:
  /nix/store/9vjsa89hi35bsmq02bn6j8l7xahadpmp-xmonad-extras-0.13.3.drv
building '/nix/store/9vjsa89hi35bsmq02bn6j8l7xahadpmp-xmonad-extras-0.13.3.drv'...
setupCompilerEnvironmentPhase
Build with /nix/store/v2qr71m53qpcgjkbc84iggr72f0zivhw-ghc-8.4.3.
ignoring (possibly broken) abi-depends field for packages
ignoring (possibly broken) abi-depends field for packages
unpacking sources
unpacking source archive /nix/store/1dmxj3wijxyls6gl3xyq050dq83xzaz5-xmonad-extras-0.13.3.tar.gz
source root is xmonad-extras-0.13.3
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file xmonad-extras-0.13.3/xmonad-extras.cabal
patching sources
compileBuildDriverPhase
setupCompileFlags: -package-db=/build/setup-package.conf.d -j4 -threaded
[1 of 1] Compiling Main             ( Setup.lhs, /build/Main.o )
Linking Setup ...
configuring
configureFlags: --verbose --prefix=/nix/store/jflkh8yfm3zmsm94a6h1nricai7ap86v-xmonad-extras-0.13.3 --libdir=$prefix/lib/$compiler --libsubdir=$pkgid --docdir=/nix/store/p0fl4wx03d2ali2fna50r84angfqzjvb-xmonad-extras-0.13.3-doc/share/doc/xmonad-extras-0.13.3 --with-gcc=gcc --package-db=/build/package.conf.d --ghc-option=-j4 --disable-split-objs --enable-library-profiling --profiling-detail=all-functions --disable-profiling --enable-shared --disable-coverage --enable-static --disable-executable-dynamic --enable-tests --enable-library-vanilla --enable-library-for-ghci --ghc-option=-split-sections -f-with_hlist -fwith_parsec -fwith_split --extra-lib-dirs=/nix/store/q8rg4mca5zqv98arpxd7164pqa72hf1n-ncurses-6.1/lib --extra-lib-dirs=/nix/store/hhzvw77vrmn5f506kfyb1yh1sdinkbwf-gmp-6.1.2/lib
Using Parsec parser
Configuring xmonad-extras-0.13.3...
CallStack (from HasCallStack):
  die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:958:20 in Cabal-<IP_ADDRESS>:Distribution.Simple.Configure
  configureFinalizedPackage, called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:462:12 in Cabal-<IP_ADDRESS>:Distribution.Simple.Configure
  configure, called at libraries/Cabal/Cabal/Distribution/Simple.hs:596:20 in Cabal-<IP_ADDRESS>:Distribution.Simple
  confHook, called at libraries/Cabal/Cabal/Distribution/Simple/UserHooks.hs:67:5 in Cabal-<IP_ADDRESS>:Distribution.Simple.UserHooks
  configureAction, called at libraries/Cabal/Cabal/Distribution/Simple.hs:178:19 in Cabal-<IP_ADDRESS>:Distribution.Simple
  defaultMainHelper, called at libraries/Cabal/Cabal/Distribution/Simple.hs:115:27 in Cabal-<IP_ADDRESS>:Distribution.Simple
  defaultMain, called at Setup.lhs:4:10 in main:Main
Setup: Encountered missing dependencies:
xmonad >=0.10 && <0.14

builder for '/nix/store/9vjsa89hi35bsmq02bn6j8l7xahadpmp-xmonad-extras-0.13.3.drv' failed with exit code 1
error: build of '/nix/store/9vjsa89hi35bsmq02bn6j8l7xahadpmp-xmonad-extras-0.13.3.drv' failed

Steps to reproduce
nix-build -A haskellPackages.xmonad-extras
Technical details
λ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 4.14.53, NixOS, 18.09pre145524.2a8a5533d18 (Jellyfish)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.0.4`
 - channels(root): `"nixos-18.09pre145679.dae9cf6106d"`
 - channels(nequi): `"unstable-18.09pre145524.2a8a5533d18"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Git checkout of master @ NixOS/nixpkgs@b34a147eef37ac881f83c349fd51ccd14f5acc6c

@peti and @Ericson2314 updated some haskell infrastructure a few days ago. Maybe they know ;)

The whole xmonad ecosystem is in bad shape because the code is largely unmaintained and no updates get published. :-(

Same

@BadDecisionsAlex It's "fixed" now on master


initial implementation

Available Templates here https://github.com/StrongMonkey/rancher-catalog/tree/gc-manager/infra-templates/gc-manager

@cjellick PR and associated templates are avaiable and ready to be reviewed.

https://github.com/rancher/rancher/issues/8685

The logging seems really verbose. There would be a lot of stuff printed at info level. You can keep some of it, but I think you should go back and knock some of the info statements down to debug (and then add support for a RANCHER_DEBUG environment variable that is also presented as a question in the catalog

In thinking about how this will be used and configured in Rancher, I think it should have a health check. It should fail the healtcheck if errors were encountered while deleting images. On the catalog side, the healthcheck should be configured to "do nothing" so that the container isnt deleted, it just gets a /!\ next to it so that user can investigate.

@cjellick PR is updated based on your comments.

LGTM


[FLINK-2462] [streaming] Major cleanup of streaming task structure

This pull request addresses exception handling, code duplication, and missed resource cleanups in the streaming operators.
I mixed multiple issues in this pull request, which would have been better separated, but many were recognized in the rework, and it was tricky to pull the fixes apart.
Exception handling
The exceptions are no longer logged by the operators themselves. Operators perform only cleanup in reaction to exceptions.
Exceptions are reported only the the root Task object, which knows whether this is the first failure-causing exception (root cause), or is a subsequent exception, or whether the task was actually canceled already. In the later case, exceptions are ignored, because many cancellations lead to meaningless exceptions.
Added more exception in signatures, less exception wrapping where not needed
Unified setup / teardown structure in streaming tasks
Core resource acquisition/release logic is in StreamTask, reducing code duplication.
Subtasks (e.g., OneInputStreamTask, IterationTailStreamTask) implement slim methods for certain parts of the life cycle. The OneInputStreamTask becomes as simple as this
public void init() throws Exception {
	TypeSerializer<IN> inSerializer = configuration.getTypeSerializerIn1(getUserCodeClassLoader());
	InputGate[] inputGates = getEnvironment().getAllInputGates();
	inputProcessor = new StreamInputProcessor<IN>(inputGates, inSerializer,
			getCheckpointBarrierListener(),
			configuration.getCheckpointMode(),
			getEnvironment().getIOManager(),
			getExecutionConfig().areTimestampsEnabled());

	// make sure that stream tasks report their I/O statistics
	AccumulatorRegistry registry = getEnvironment().getAccumulatorRegistry();
	AccumulatorRegistry.Reporter reporter = registry.getReadWriteReporter();
	inputProcessor.setReporter(reporter);
}

protected void run() throws Exception {
	while (running && inputProcessor.processInput(streamOperator));
}

protected void cleanup() throws Exception {
	inputProcessor.cleanup();
}

protected void cancelTask() {
	running = false;
}

Guaranteed cleanup of output buffer and input buffer resources (formerly missed when other exceptions where encountered).
Unified StreamRecordWriter and RecordWriter usage.
Cleanup in the StreamSource
Fix mixup in instantiation of source contexts in the stream source task
Auto watermark generators correctly shut down their interval scheduler
General
Improve use of generics, got rid of many raw types

Fixed the issues with the tests. Builds locally, waiting for Travis to confirm.

This looks like a very nice continuation of the cleanup work. I'd suggest to merge it rather sooner than later.

Allright, if there are no further comments, I'll merge this...


[spaceship] remove application and version from app submission params

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
json parse error occured when I submit for review.
I checked request params and params included not key value objects but spaceship class objects.
SystemStackError: stack level too deep
 /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:140:in `initialize_dup'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:140:in `dup'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:140:in `block in as_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:140:in `map'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:140:in `as_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:140:in `block in as_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:140:in `map'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:140:in `as_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:128:in `as_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:159:in `block in as_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:159:in `each'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:159:in `map'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:159:in `as_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:50:in `as_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:159:in `block in as_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:159:in `each'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:159:in `map'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:159:in `as_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:140:in `block in as_json'

-------

/Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:159:in `block in as_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:159:in `each'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:159:in `map'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:159:in `as_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/json/encoding.rb:35:in `encode'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/json/encoding.rb:22:in `encode'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/activesupport-4.2.10/lib/active_support/core_ext/object/json.rb:37:in `to_json_with_active_support_encoder'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/fastlane-2.108.0/spaceship/lib/spaceship/base.rb:66:in `to_json'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/fastlane-2.108.0/spaceship/lib/spaceship/tunes/tunes_client.rb:1104:in `block in send_app_submission'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/faraday-0.15.3/lib/faraday/connection.rb:384:in `block in run_request'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/faraday-0.15.3/lib/faraday/connection.rb:398:in `block in build_request'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/faraday-0.15.3/lib/faraday/request.rb:26:in `block in create'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/faraday-0.15.3/lib/faraday/request.rb:25:in `tap'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/faraday-0.15.3/lib/faraday/request.rb:25:in `create'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/faraday-0.15.3/lib/faraday/connection.rb:394:in `build_request'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/faraday-0.15.3/lib/faraday/connection.rb:379:in `run_request'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/faraday-0.15.3/lib/faraday/connection.rb:175:in `post'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/fastlane-2.108.0/spaceship/lib/spaceship/client.rb:699:in `block in send_request'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/fastlane-2.108.0/spaceship/lib/spaceship/client.rb:532:in `with_retry'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/fastlane-2.108.0/spaceship/lib/spaceship/client.rb:698:in `send_request'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/fastlane-2.108.0/spaceship/lib/spaceship/client.rb:586:in `request'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/fastlane-2.108.0/spaceship/lib/spaceship/tunes/tunes_client.rb:1102:in `send_app_submission'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/fastlane-2.108.0/spaceship/lib/spaceship/tunes/app_submission.rb:162:in `complete!'
  /Users/marumemomo/code/myProject/Bundler/ruby/2.3.0/gems/fastlane-2.108.0/deliver/lib/deliver/submit_for_review.rb:28:in `submit!'

Description
I removed spaceship class objects from request params app_submission.complete! .
I cannot release by deliver now, I wish merge this PR.
Thank you!

I signed it!


RedirectFallback does not preserve path

To be able to use the RedirectFallback in fallback.go for slightly more complex situations, it would be nice if it could be used to preserve the path of the current request on the redirect. For example, if the current request is
http://something/basepath/rest/of/path
and if redirect is set to
http://somethingelse/otherbasepath
then I'd expect the redirect to go to
http://somethingelse/otherbasepath/rest/of/path
I'd like to add some code to either redirectfallback, or create a new fallback method, that can support this. Would a change like this be acceptable?

yes, go for it


The description in the section "Burstable virtual machine with non-burstable disks" is different from the graph. It said 2 P10 data disks. But the graph shows 2 P50 data disks.

[Enter feedback here]
The description in the section "Burstable virtual machine with non-burstable disks" is different from the graph. It said 2 P10 data disks. But the graph shows 2 P50 data disks.
https://docs.microsoft.com/en-us/azure/virtual-machines/disk-bursting#burstable-virtual-machine-with-non-burstable-disks
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5e6dcff8-b7b3-68b3-2364-dffa15b28356
Version Independent ID: 6401288f-c695-2d25-1198-07b237242005
Content: Managed disk bursting - Azure Virtual Machines
Content Source: articles/virtual-machines/disk-bursting.md
Service: virtual-machines
Sub-service: disks
GitHub Login: @roygara
Microsoft Alias: rogarana

@fliang-ms Thanks for pointing this out.
The document is updated and changes will go live soon.


Cannot parse field with Double.MaxValue

The following code fails with an exception stating "Input string '1.79769313486232E+308' is not a valid number. Path 'field', line 1, position 30".
var json = $"{{\"field\":{double.MaxValue}}}";
var obj = JObject.Parse(json);

Ideally, I would just change the code to format double.MaxValue.ToString("r"), which works without issue. Unfortunately this is an excerpt from a server that I do not control and have no power to change.
I don't suppose a special case could be put in here to account for double.MaxValue.ToString() and double.MinValue.ToString()? I am happy to submit a PR for that if it is something that you would consider.

The problem is that string has to rounded so that it is no longer valid. I want to avoid changing parsing of floating point numbers. Every change opens up unknown cans of worms.


Handle data fields correctly

Fixes https://github.com/nimakaviani/managed-delivery-k8s-plugin/issues/50.

Decouple the data field from K8sData. The data field is now a Map<String, Any?>?
With this, credentials resource spec is changed slightly. The spinnaker account name is now placed in metadata.
Remove the strategy.spinnaker.io/versioned annotation when generating diffs.
ConfigMaps created through clouddriver is versioned by default. We add the strategy.spinnaker.io/versioned annotation to disable it for now.  We may need to revisit this in the future to take advantage of versioned secrets and configmaps.

really like the final outcome. moving the annotation to toResolvedType for CredentialsResourceHandler has made it much cleaner.
LGTM


Update joda-time to 2.12.6

About this PR
📦 Updates joda-time:joda-time from 2.12.4 to 2.12.6
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "joda-time", artifactId = "joda-time" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "joda-time", artifactId = "joda-time" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #667.


4.2. Records for a single species: record count appearing in UI

Record count is appearing in the UI. Is this supposed to be here? It is not in the wireframes.

Suggest we keep for now, as useful given we don't get proper paging results from NBN.

As discussed, not in the specs, but until we get pagination working correctly I think it serves a purpose, both for development & user testing.  May be useful beyond that.
From: Charles Roper @.>
Sent: 17 April 2021 00:03
To: jdrever/ShropBotSoc @.>
Cc: James Drever @.>; Assign @.>
Subject: [jdrever/ShropBotSoc] 4.2. Records for a single species: record count appearing in UI (#96)
Record count is appearing in the UI. Is this supposed to be here? It is not in the wireframes.
[image]https://user-images.githubusercontent.com/176/115091215-db262200-9f0e-11eb-84ea-7e266f2de543.png
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/jdrever/ShropBotSoc/issues/96, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAPKYJPZJVVIZHFAHGFFAJTTJC6ZJANCNFSM43CL7U5Q.


[Question]Can filer.sync support clusters with multiple filers?

Describe the question
I see that filer.sync allows cross cluster replication. Can a single cluster that contains say, two Filers, replicate to a cluster containing two Filers? Following the example format in the documentation that would look like this in my mind:
cluster1  <-- filer.sync --> cluster2
    |                               |_______
    +- filer1 <-- filer.sync --> filer2     +- filer1 <-- filer.sync --> filer2

Would this be possible to achieve by simply having the metadata store that the two Filers in a cluster talk to be a single database instance like Cassandra(in our case ScyllaDB)?
Desired behavior
Two clusters with two filers each in Active-Passive or Active-Active configuration. Both clusters would sit behind a single reverse proxy that would identify two Filers as the primary cluster and two as the secondary or backup cluster.
Additional context
With our use case, we are looking to have something like two separate data centers each with identical data. We are interested in having a primary data center and a back up.
I'm open to hearing any whys or why nots on this potential set up!

If we have two clusters, cluster a and cluster b, each with three Filers, would we have to run filer.sync between each filer?
Like:
filer1a <-- filer.sync --> filer1b
filer2a <-- filer.sync --> filer2b
filer3a <-- filer.sync --> filer3b

I understand this may not be possible because each Filer in this case is not representing it's own cluster.

filer1a <-- filer.sync --> filer1b this should be enough. If not, it is a bug.

Ok! We may try this. Thanks.


Wrong usage of react-ids

You're not setting the correct react-ids in your views, which causes the list to be empty or showing one item.
# localhost:3000
react.js:20209 Warning: Each child in an array or iterator should have a unique "key" prop. Check the render method of `PokemonList`. See https://fb.me/react-warning-keys for more information.
    in tr (created by PokemonList)
    in PokemonList (created by PokemonListContainer)
    in div (created by PokemonListContainer)
    in PokemonListContainer

This error mostly occurs when you are not setting a correct and unique react-key (or sometimes key) property for each item in your list. Maybe I will send you a pull request if I find the time for this in the evening.
The latest release of reactjs seems to be very fussy concerning the usage of these keys. Older versions had no problem with this.

Good catch. This project started out as a way for me to learn React, but since people actually seem to be using it, I might switch to AngularJS in the near future. Either way, I'll push a fix for this later today.

React.js is awesome (although I never used it directly with JavaScript, since I am a ClojureScript developer), and I have worked with Angular, but i don't like it, since it is too complicated. And the way react.js handles views is currently one of the best approaches in my opinion.

Agreed. I actually like the methodology of React a lot. I am an Angular/Node dev at work, though, and I know I'd be able to update this more frequently if I went with React.


[Development check up]: things that need attention

[x] Disabled text color must be chosen based on fieldset -

text/border neutral 400, background 200

[x] Ghost disabled appearance model -

inner content (text, icon) - neutral 400

[x] What happens to the field label in different states? -

I think it stays the same, still would like to check

[x] Read only field -

background: neutral 100

border: neutral 400

icons, label, helper text: neutral 600

Input text: neutral 1000

@yinonov

[ ] Chosen state - The background will be changed to neutral 200
since 1000 creates kind of a dark mode situation with inner components  @yinonov

[ ] Listbox with options (multiple select) - is it problematic? How should be handled? -

@yinonov  The a11y proposes the solution of checkboxes with options that create a checklist:

https://a11y-style-guide.com/style-guide/section-forms.html#kssref-forms-select-lists
But I also saw this really cute solution with tags in a few places:
https://ant.design/components/select/
https://atlassian.design/components/select/examples
But the issue that needs to be considered is what happens when the field is full?
What I saw is that it just becomes higher.
Probably it is the same treatment with the checkboxes option.
Honestly, I prefer the checkbox solution,
But basically what are your thoughts about this?

[x] Should there be an appearance difference between "selected" and "checked" states -

@yinonov

Based on what a saw in ARIA:
https://w3c.github.io/aria-practices/examples/#examples_by_props_label

"Checked" state applies only to a handful of components that need special treatment:

checkbox
radio button
menubar (the checked option we discussed for the menu-item)
switch
toolbar

Each and every one of them is a completely separate component in which the "checked" state looks different.
If we give the "selected" state to the entire box (the moment the choice is being made, and a ui component with a text have a certain background color for example) then it is something different, as it gives the indication about a choice being made.

[x] Add distance (padding) between options -

4px distance between the option items
2px padding-top + padding-bottom
Just like here:

https://www.figma.com/file/QG5hvuw5qsfS0XYMVJ6V3L/Vivid-UI-Kit---Exploration?node-id=4278%3A61829
@yinonov

[ ] Check what happens to padding when a component has icon + text / icon only -

Needs to be checked

[ ] Clickable/unclickable icon - what color should it receive? -

After some research and meditation:
I agree with Joella's convention,
by which unclickable  (decoration) icon will be 600,
& clickable icon will be 1000.
Although, I wonder, maybe we can consider allowing cta color to clickable icon?
@yinonov @rachelbt

[x] Note component - check connotations needed, and remove the unnecessary ones -

Based on the research I did the connotations we have appear in the most of design systems, the only change I would propose is to change announcement (magenta) connotation to confirmation (accent) @yinonov

[x] Should outline appearance receive a background color? -

@yinonov So this is the situation:
Ant design: No bg
Carbon: Present but with opacity 0
Fluent: Present
Fast: No bg
Semantic UI: No bg
Bootstrap: No bg
Lightning: No bg

So basically we can see that there isn't one single practice that is always present,
although what I saw in more cases was the transparent background,
Which is the option I, personally, like muck more

Listbox with options (multiple select) - is it problematic? How should be handled? -
@yinonov The a11y proposes the solution of checkboxes with options that create a checklist:
https://a11y-style-guide.com/style-guide/section-forms.html#kssref-forms-select-lists
But I also saw this really cute solution with tags in a few places:
https://ant.design/components/select/
https://atlassian.design/components/select/examples
But the issue that needs to be considered is what happens when the field is full?
What I saw is that it just becomes higher.
Probably it is the same treatment with the checkboxes option.
Honestly, I prefer the checkbox solution,
But basically what are your thoughts about this?

we use menu for these type of usages

@yinonov
I think it's better to have an actual checkbox in this situation.
Checked menu item can be confusing

what the menu item checkbox for then? how's it different than an option with a prefixed checkmark?

List item with checkbox is used more in situations like form,
while the checked menu item is used mostly for options that affect the display.

@yinonov @rachelbt @rinaok @YonatanKra
I think about the unclickable icon convention,
I am not sure that it is enough difference between neutral 600 & 1000 for user to understand that one of them is actionable and the other is not.
I think that unclickable icon color should be changed to 500.
What are your thoughts on this?


hadoop-resource-manager 'Liveness probe failed'

After build and install the latest code, the hadoop-resource-manager Liveness probe failed.
Liveness probe failed: Get https://<IP_ADDRESS>:9459/: tls: oversized record received with length 20291 Back-off restarting failed container

Due to the not matched network protocol schema, fixed in PR #1490


Disable ToolTip for Today's button

How can i disable tooltip for today's button in DateTimePicker

The today button is part of the Date component. If there is no way to turn it off, you will need to contact Sencha Support for it.


fix: prevent occasional overflow in Fixed tree queries by using a saturating_add

Codecov Report

Merging #75 (884b915) into next (44ba591) will increase coverage by 4.19%.
The diff coverage is 93.54%.

@@            Coverage Diff             @@
##             next      #75      +/-   ##
==========================================
+ Coverage   84.40%   88.59%   +4.19%
==========================================
  Files          29       32       +3
  Lines        3636     3964     +328
==========================================
+ Hits         3069     3512     +443
+ Misses        567      452     -115

Impacted Files
Coverage Δ

src/lib.rs
100.00% <ø> (ø)

src/types.rs
30.76% <ø> (ø)

src/nearest_neighbour.rs
46.15% <33.33%> (ø)

src/best_neighbour.rs
46.15% <46.15%> (ø)

src/fixed/distance.rs
53.57% <53.57%> (+30.31%)
:arrow_up:

src/fixed/query/within_unsorted_iter.rs
80.14% <80.14%> (ø)

src/float/query/within_unsorted_iter.rs
93.10% <93.10%> (ø)

src/common/generate_best_n_within.rs
100.00% <100.00%> (ø)

src/common/generate_nearest_n.rs
100.00% <100.00%> (ø)

src/common/generate_nearest_one.rs
100.00% <100.00%> (ø)

... and 17 more

... and 2 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


viz_cameras nothing show

i run "python viz_cameras.py",but shows nothing. I found the folder "output" doesn't have "output\cameras".

i run code on ubuntu 20.04, thanks.

Thanks for your interest! I can successfully obtain the output camera file by running "python main.py --config cfg_files/fit_smpl.yaml" on my machine.
You can check whether the --opt_cam is true in the configuration file.
If you still have the problem, please contact with me. I will check the code in detail.

thank you very much for your reply @boycehbz
According to your advice, I checked the --opt_cam which shows true, but there is still noting to show. Need your help again! Thanks!

Sorry for the mistake. The path of the output camera file in viz_camera.py is incorrect for the current code, which should be "output/camparams/doubleB/00064.txt". I have revised the code. You can pull the latest code and check it again.

thank you very much for your reply @boycehbz
But I don't have any 3D models except a few cameras in my window

I have added a sample for the mesh visualization in viz_cameras.py. You can modify the code for visualizing more results.

thank you very much @boycehbz

Can you share the complete code for playing 3d animation in your demo video. Thank you very much. @boycehbz

The demo video is rendered by private rendering codes. I guess the Open3D can also obtain the same results, but it may exist minor differences for the mesh visualization.


Failed building wheel for faiss-gpu

while run pip install gedml
my env:
ubuntu18
python3.8
pytorch1.8.2
cuda11.1

[Possible cause] Sorry for the late reply. We need to specify the faiss-gpu version as 1.5.3, which may not be compatible with the latest PyTorch and python.
[Solution] It is ok to install gedml without faiss-gpu package. We write the related code in src/gedml/core/evaluators/metrics.py as follows (Line 10-17):
# faiss
try:
    import faiss
except ModuleNotFoundError:
    logging.warning("Faiss Package Not Found! (metrics package)")

_USE_FAISS_ = False
_NORMALIZE_ = True

You need to keep the flag _USE_FAISS_ to be False and delete the faiss-gpu related item in requirements.txt and try to re-install again.

You can always contact me if any other problem occurs. 😄


Problem communicating with hadoop server

Hi there,
I'm pretty excited about using libhdfs3, but having problems authenticating with my local hadoop server.  I don't have administrator privileges on it, or a lot of transparency on the install for that matter, but I do know that it's running a Hadoop 2.6.0 build with (I think) protobuf 2.5.0.
I'm getting this error:
2015-09-03 13:15:38.962745, p114445 th139816236222784, ERROR Failed to invoke RPC call "getFsStats" on server "server_name_removed:port":
RpcChannel.cpp: 413: HdfsRpcException: Failed to invoke RPC call "getFsStats" on server "server_name_removed:port"
@ Hdfs::Internal::RpcChannelImpl::invokeInternal(std::shared_ptrHdfs::Internal::RpcRemoteCall)
@ Hdfs::Internal::RpcChannelImpl::invoke(Hdfs::Internal::RpcCall const&)
...
Caused by SaslClient.cpp: 84: HdfsIoException: Cannot initialize client (2) : Unknown SASL mechanism
...
This hadoop package is pretty old I suspect, but I built libhdfs using protobuf 2.5.0 and the latest libgsasl and libuuid, so I'm not sure how important having those match the hadoop package is.  Do you think that's a problem?  Any ideas on how to troubleshoot and fix this?  Thanks.

Hi
It an issue of libgsasl. To solve this issue, you should rebuild libgsasl to support gssapi.
cd libgsasl-<version>
./configure --with-gssapi-impl=mit
make install


Save people literally hours of debugging

What does this fix?
On Wed, May 19, 2021, 2:58 AM Ryan Romanchuk @.***>
wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/DavidWittman/ansible-redis/pull/266
Commit Summary

Save people literally hours of debugging

File Changes

M README.md
https://github.com/DavidWittman/ansible-redis/pull/266/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5
(2)

Patch Links:

https://github.com/DavidWittman/ansible-redis/pull/266.patch
https://github.com/DavidWittman/ansible-redis/pull/266.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DavidWittman/ansible-redis/pull/266, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFOML37RV7VU2FVXJLQEALTONVTVANCNFSM45ECN3IA
.

I wonder the same: is it because the published version on Galaxy is old (https://galaxy.ansible.com/davidwittman/redis), or because of another problem?

I'm not sure anymore, i need sleep. I made a mistake when modernizing and moving aws ssm to execute my plays, where my legacy local requirements.yml was using git, and new deployment was galaxy when i realized the galaxy-installed-on-the-fly role was using different source. Probably user error and being dramatic while fighting fires. aka, took master down because i deployed a bogus/miconfigured service file 🤣

All good... We've all been there!
On Wed, May 19, 2021, 6:16 PM Ryan Romanchuk @.***>
wrote:

I'm not sure anymore, i need sleep. I made a mistake when modernizing and
moving aws ssm https://aws.amazon.com/systems-manager/ to execute my
plays, where my legacy local requirements.yml was using git, and new
deployment was galaxy when i realized the galaxy-installed-on-the-fly role
was using different source. Probably user error and being dramatic while
fighting fires. aka, took master down because i deployed a
bogus/miconfigured service file 🤣
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/DavidWittman/ansible-redis/pull/266#issuecomment-844559702,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFOML23GOKJLVPMHS5BHU3TORBGLANCNFSM45ECN3IA
.

[finally tailing logs now] looks like i also forked without forking. I'm sure i made some sort of bargain with myself that it was only "temporary, just for a quick test", i have a monkey patched redis.service.j2 that looks like i would update from upstream with -f then hand patch for at least a couple of versions now, ....so much for temporary.
In my context, the server has no inbound/outbound www access from/to the vpc. To make provisioning a delight, there is an efs mount on ~/, ready to go at boot, with this role, hosts of any arch can load/save the .rdb by just changing the tag value on ec2.  The ProtectHome=yes line causes systemd to implode on ExecStart, and in my case, if someones reading my process list, it's already game over.  So it wasn't even from the version change, which at most lost some .conf values like redis_config_additional,  just the classic case of lazy developer kindling their own fire for future self to enjoy a year later lol


Updates to examples, tests, POD, overloading in Scalar.pm, more units…

… in Unit.pm
Hi! I hope you consider my pull request. I have made the following changes:-

The examples and POD for Scalar.pm incorrectly referred to "div()" instead of "divide()", causing the examples to crash (updated).
A test in unit.t appears to be failing on quad-precision systems because they have the fortune of being able to represent a number without resorting to e notation (patched).
I have added some overloading to operators in Scalar.pm, as that made things easier for what I was working on. I have added an example and a test file for this.
I have added some new units in Unit.pm, relating to different planets.
Thanks.

Hi. I don't want to let this slip through the cracks, I don't have much time for open source these days. To facilitate that, can you split this PR into two? The first being the obvious bugfixes etc (including the new units) and the second being the new overloading feature? I'll want to run that second one past a few people but the first should be an easy one.

Sure, thanks for the reply. I have just created a separate PR for the bug fixes. It's getting late here so I will have to work on the overloading PR tomorrow.

Closed in favor of #36 and #37

Though the code was included through separate PRs this was the initial entrypoint. I noticed that #30 was considered by the original author and I asked around for any thoughts on performance or compatibility concerns and no one said anything, so today I had a few minutes and merged the #37 PR as well. It has now been released to CPAN as 0.60 (which should show up soon as https://metacpan.org/release/JBERGER/Physics-Unit-0.60 ). Cheers and thanks!


Height issue

Expected Behavior
The height is not getting adjusted.
Current Behavior
The height is staying the same when there are a lot of items. I tried a few things, and I'm not sure if it's a bug actually.
Steps to Reproduce (for bugs)
This is the issue:
https://node-track.com/addresses/<IP_ADDRESS>
https://node-track.com/addresses/einfallslos.ddnss.de
The first one gets display correctly, but the second one bugs out.
Environment

Chart.js version: 2.8.0
Browser name and version: Latest Chrome (Jan 2020)
Link to your project: https://node-track.com/js/chart/node-reputation-multiple.js?v=20190105

Basically the legend fills up the whole chart. You could disable the legend as a workaround. I don't know how useful the legend is with that many items in it?

Basically the legend fills up the whole chart. You could disable the legend as a workaround. I don't know how useful the legend is with that many items in it?

Usually I will have around 5 items there and it's fine, this is exceptional case, but I still want to fix it.
I tried changing the aspectRatio option, but it doesn't seem to do anything

You could make the canvas larger yourself based on how many items there are. Chart.js won't change the size of the canvas because we don't know how that will affect the overall webpage layout

Closing as duplicate of https://github.com/chartjs/Chart.js/issues/3761


pycromanager==0.19.2 depends on numpy < 1.24.0

Yesterday's numpy 1.24.0 release deprecates np.bool which pycromanager depends on, which is breaking (fresh installations of) recOrder including our tests.
I think we can:

Pin to numpy==1.23.0 and/or
Wait for the next release of pycromanager that's compatible with numpy==1.24.0 (see this PR I just opened) and upgrade our pycromanager dependency.

What do you think @ziw-liu? I'm leaning towards 1 now, then 2 later.

Thanks for the PR to upstream!
It makes sense to pin NumPy before PM's next release with the fix.

https://github.com/micro-manager/pycro-manager/pull/475 has been merged. However, pycro-manager with this new patch won't be installed with recorder since we have pinned its version:
https://github.com/mehta-lab/recOrder/blob/655a7643f0b9cba3dc51ccb932cf3abc8db38037/setup.cfg#L41
@talonchandler @ieivanov What should we do to confidently bump PM dependency to latest?

I think manually testing the MM connection and acquisitions on hummingbird will be enough to upgrade the PM dependency confidently. We might need to upgrade MM as well, but I don't think we'll know until we test.
I'm not in any rush to upgrade. I think it can wait until after 0.3.0.

@ziw-liu I just realized that this issue affects new installations of recOrder==0.2.0. Would you mind releasing 0.2.1 with numpy==0.23.5?
In the meantime, an easy workaround is pip install recOrder-napari followed by pip install numpy==0.23.5.

Now that we have automated testing, pycromanager should be a lot more reliable. We can more confidently upgrade and add tests for features we depend on

@ziw-liu I just realized that this issue affects new installations of recOrder==0.2.0. Would you mind releasing a patched version 0.2.1 with pinned numpy==0.23.5?

Just to be clear, should 0.2.1 be 0.2.0 with only the NumPy version patch, not any other additional commits?

👍 that’s perfect…just the pinned numpy version on top of 0.2.0. If you’re keen it might be worth testing a local install before releasing, but I have tested a by-hand numpy pin on two installations, so I’m quite confident it’ll be fine.

Heads up, as an added complication, dexp currently requires numpy < 1.22


New Project, preps and physics

Creating two new projects (jenga and driving simulator)
Preparations for the other teams (creating cubes etc...)
Add physic to cubes

done

done


"Delete # Blocks" counts numbers as blocks in horizontal mode

This was the only block I dragged out (I even refreshed the page and deleted all blocks). However, it still thinks there's an extra block there.
The problem is the number field as included in blocks/math.js is a separate block and counts towards the total.
The solution would be to check if the block being counted in the total is a number block or not:
// arbitrary pseudocode
if (block.Type != block.math.number) {
  // Only count non-number blocks
  blockCounter++;
}

The code to count which blocks are deletable is here: core/workspace_svg.js:863
// Option to delete all blocks.
// Count the number of blocks that are deletable.
var deleteList = [];
function addDeletableBlocks(block) {
  if (block.isDeletable()) {
    deleteList = deleteList.concat(block.getDescendants());
  } else {
    var children = block.getChildren();
    for (var i = 0; i < children.length; i++) {
      addDeletableBlocks(children[i]);
    }
  }
}

We could sift through block.getDescendants() and then exclude any number blocks or related types.

This is a great observation. I think it's the same problem we observed and fixed here:
https://github.com/LLK/scratch-blocks/issues/241
The context menu you're noticing - the one that pops up when you right click the workspace - must be counting blocks differently from the one that pops up when you right click a block.
The solution I think will be to not count the "shadow" blocks (context: https://groups.google.com/forum/#!topic/blockly/bXe4iEaVSao) which we are using in scratch-blocks for all of the fields/inputs. Rather than special-case for math.number, I think it's safe to never include shadow blocks in these numbers.
I'm going to close this issue and re-open the old one, just so we keep all the context in one place :)


Bug: Lines of unit tests marked when using keyboard mode

I've self-assigned this but it might take me a while before I can fix it.
It should be a really easy fix, so if you have the time - please go for it.


Add suggested dictionaries for spellchecking and remove unneeded words

Added some pre-existing dictionaries suggested by the spellchecking action (e.g. for win32) and removed some that didn't make much sense for us to have (why did we even have html and aws?). Also removed the words that we don't need to have in our excludes.txt or allow.txt because they are already in one of the dictionaries (either existing or added).
Microsoft Reviewers: Open in CodeFlow

@jsoref why is the result different here than in a run from my fork?

Thanks @jsoref
I removed the win32 dictionary and added back all the items I had removed from it.
I put all of the items that aren't needed with the new dictionary at the end of allows.txt and will remove them in another PR


add dev label from my fork

Please push a tag on your fork 0daa1f7540998e9c75ea300b176cc2848ea31948 s.t. https://github.com/0xbe7a/rattler-build/archive/0daa1f7540998e9c75ea300b176cc2848ea31948.tar.gz will not be lost once the branch has been deleted on your fork.

remote: error: GH002: Sorry, branch or tag names consisting of 40 hex characters are not allowed.

I meant a tag on this exact commit, not with this name. You can name the tag for example 0.6.2dev1


How to run the scapegoat task when compiling the test code

The scapegoat sbt scope extends the compile scope, which to my understanding means that scapegoat will be run against the compile scope and not against the test scope:
val Scapegoat = config("scapegoat") extend Compile

Is there a way to get a scapegoat task that runs when we compile the test code? This might be a feature request.

To actually run scapegoat against the test code itself. I suppose scapegoatTest would be sufficient.


chore: appease black on ergo/schematic.py

ergo==0.9.1 did not deploy; i'm taking a wild guess that this is the reason

it seems pep8 and black disagree:
black:

pep8:

anyway my original problem is that 0.9.1 did not seem to be deployed and i'm trying to debug why...

i know i can just massage the code to not trigger this conundrum but does black really have that much power over me?

since i named my pr 'appease black' maybe deep down i already know the answer...

@xytxytxyt so weird that the linting issue got caught on master, but on your test branch...


Publish wpe-lightning-cli

Running npm install -g wpe-lightning-cli.
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/wpe-lightning-cli - Not found
npm ERR! 404
npm ERR! 404  'wpe-lightning-cli@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR!      C:\Users\matti\AppData\Roaming\npm-cache\_logs\2020-01-23T11_58_16_967Z-debug.log

@michielvandergeest I've open an issue here:
https://github.com/WebPlatformForEmbedded/Lightning-SDK/issues/57


Is the user allowed to specify a unit for blood pressure terms?

The Expected value says that the values are to be entered as 'mm mercury'. Then why does the Value syntax allow users to enter a unit?
Shouldn't these  Structured comment names be soemthing like

host blood pressure diastolic, mm Hg
host blood pressure systolic, mm Hg

Then the Value syntaxes would just be {float}

Environmental package
Structured comment name
Package item
Definition
Expected value
Value syntax
Example
Requirement
Preferred unit
Occurrence
MIXS ID
github ticket

host-associated
blood_press_diast
host blood pressure diastolic
Resting diastolic blood pressure, measured as mm mercury
measurement value
{float} {unit}

X
millimeter mercury
1
MIXS:0000258

host-associated
blood_press_syst
host blood pressure systolic
Resting systolic blood pressure, measured as mm mercury
measurement value
{float} {unit}

X
millimeter mercury
1
MIXS:0000259

Based on the definition, the value syntax should be just {float}.
Let's go look at what people actually record.

@lschriml checked biosamples, and no one uses units, so we can just change the expected value.

The definition describes the reading on the gauge of the blood pressure cuff.
The standards description for this is:
The gauge uses a unit of measurement called millimeters of mercury (mmHg) to measure the pressure in your blood vessels.
https://www.cdc.gov/bloodpressure/measure.htm
Update for v6.2:  the value syntax should be just {float}.
Cheers,
Lynn


README misconceptions

https://github.com/TheR1D/shell_gpt/blob/7ac1f98a8b7003f08e879743aae67860e47828e0/README.md?plain=1#L16C1-L29C4
https://github.com/TheR1D/shell_gpt#simple-queries

Simple queries
We can use it as normal search engine, asking about anything:

This claim is a misconception. I think It's crucial to clarify that Language Models (LLMs) are not search engines.
I feel like there's a common misconception spreading that LLMs do have direct access to the to real-time information.
Relying on an LLM as a replacement for a search engine can lead to spread of misinformation due to hallucinations, which is why I think it's important to separate the two.
This should be rephrased to something like

Simple prompts
We can use it as normal chat bot, asking about anything:

The examples below are also questionable, they sound more like google searches than LLM prompts:

sgpt "nginx default config file location"
# -> The default configuration file for Nginx is located at /etc/nginx/nginx.conf.

sgpt "mass of sun"
# -> = 1.99 × 10^30 kg

sgpt "1 hour and 30 minutes to seconds"
# -> 5,400 seconds

Math is also not a strength of GPT. The last example is very simple, so that works but anything more complicated doesn't.
While these are question an LLM is typically able to answer because they most likely quite common in the training data, they might give a user the idea that they should rather ask sgpt simple questions about any topic than googling it (and there are shell clients for search engines).
To be clear, I think these are perfectly fine examples of prompts for an LLM, they just shouldn't be presented without context or they might spread the misconception that LLMs can replace search engines, not yet.

The word "queries" is used quite a lot, "prompt" is the correct term and is known quite well to the general public

This is highly subjective.
From my equally subjective opinion, I strongly disagree. LLMs are well on their way to replacing traditional search engines and I've all but cut out Google search (and StackOverflow) from my personal workflow, specifically by using this tool.
Managing hallucinations isn't that different from managing misinformation in search engines, you train yourself to be skeptical by default.

LLMs are well on their way to replacing traditional search engines

Yes. But currently they are still not quite there

Managing hallucinations isn't that different from managing misinformation in search engines, you train yourself to be skeptical by default.

That's a good point but search engines can generally be expected to be managing misinformation, but for LLMs that's not the case by default. The first google result (after ads) usually is trustworthy, but with LLMs it depends on the query and how well it's represented in the dataset.
I think there's no harm in implementing my proposed wording changes but there may well be harm in spreading the belief that LLMs are currently equally truthful as search engines.

Calling it a search engine also implies that results are directly based on a specific source that was found on the internet. You wouldn't call your professor a search engine.

I agree with the point made by @jeanlucthumm.

Managing hallucinations isn't that different from managing misinformation in search engines, you train yourself to be skeptical by default.

The reason it was written this way is that I initially aimed to solve the constant "googling" problem for myself when I started developing ShellGPT. The main use case for sgpt is essentially a replacement for "googling" in my opinion.
Closing this issue as the examples in question appear to have been removed in a prior releases.


WIP: Improve inference of unflatten

This is pretty minor but I noticed that there are a few cases where unflatten doesn't seem to infer.
Some exampes in master on 1.6:
v, unflatten = flatten(deferred(vec, rand(5,)))
@inferred unflatten(rand(5,)) # return type ParameterHandling.Deferred{typeof(vec), Tuple{Vector{Float64}}} does not match inferred return type ParameterHandling.Deferred{typeof(vec), _A} where _A

v, unflatten = flatten(rand(4,4))
@inferred unflatten(rand(5,)) # return type Matrix{Float64} does not match inferred return type Any

Adding a test for type inference into the test sets shows up a few. I'm aware of the  gotcha listed on the docs - ironically that one seems to work on master (Normal => normal)
This MR:

Adds inference tests into the test suite
Improved types inferece for a few of the flatten functions that showed up errors. This is through a revised 'oftype' function that has a type annotation. I tend not to see these used, is there a reason not to? It is a little surprising because this is the output of oftype, so it should know the output.

I came to this because I was seeing some inference issues as part of the CRTU tests using a program with deferred, so put this MR together

Thanks for opening this. I like the general thrust (getting type stability). I'm concerned about the things you've had to do to get it.
In particular, one of the things we're trying to do in https://github.com/invenia/ParameterHandling.jl/pull/39 is remove these kinds of casting operations, so that we can push dual numbers through unflatten. I'm kind of intruiged that it helps to be honest. I'll have a play around locally to try and understand what's going on better.

I had meant to add in my descrition that this was speculative because I was a little suspicious of these changes (using an annotation) but couldn't see a way for this without that. Regardless, I should have looked closer at the other MRs in play - if the longer term intention is to remove these these operations then this of course is incompatible with that, and i'm happy if this gets closed.

I'm actually struggling to replicate your problem locally @AlexRobson . Could you provide your versioninfo()?

I'm actually struggling to replicate your problem locally @AlexRobson . Could you provide your versioninfo()?

julia> versioninfo()
Julia Version 1.6.2
Commit 1b93d53fc4 (2021-07-14 15:36 UTC)
Platform Info:
OS: macOS (x86_64-apple-darwin18.7.0)
CPU: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-11.0.1 (ORCJIT, skylake)

Ah, interesting. Could you try running on 1.6.3? I'll see if I can get a copy of 1.6.2.

Hmm i still see this on 1.6.3. Is it possible my base environment is interfering? (I've been caught out by revise loading up before). I'll check that:
(@v1.6) pkg> activate .
  Activating environment at `~/Projects/Squads/2021-08-FlowsSquad/testing/dev/ParameterHandling/Project.toml`

julia> using ParameterHandling
[ Info: Precompiling ParameterHandling [2412ca09-6db7-441c-8e3a-88d5709968c5]

julia> using ParameterHandling: positive, deferred, fixed, value, flatten

julia> v, unflatten = flatten(deferred(vec, rand(5,)))
<snip>

julia> v, unflatten = flatten(rand(4,4))
<snip>

julia> using Test

julia> v, unflatten = flatten(deferred(vec, rand(5,)))
<snip>

julia> @inferred unflatten(rand(5,)) # return type ParameterHandling.Deferred{typeof(vec), Tuple{Vector{Float64}}} does not match inferred return type ParameterHandling.Deferred{typeof(vec), _A} where _A

ERROR: return type ParameterHandling.Deferred{typeof(vec), Tuple{Vector{Float64}}} does not match inferred return type ParameterHandling.Deferred{typeof(vec), _A} where _A

julia> v, unflatten = flatten(rand(4,4))
<snip>

julia>

julia> @inferred unflatten(rand(16,)) # return type Matrix{Float64} does not match inferred return type Any
ERROR: return type Matrix{Float64} does not match inferred return type Any

shell> git status
On branch master
Your branch is up to date with 'origin/master'.

Hmm. So I think I've managed to track down the problem, and it's in the unflattener for Vector{<:Real}.
Could you confirm that changing the method of flatten for Vector{<:Real} to
function flatten(::Type{T}, x::Vector{R}) where {T<:Real,R<:Real}
    unflatten_to_Vector(v) = Vector{R}(v)
    return Vector{T}(x), unflatten_to_Vector
end

also solves the problem on your end?

Hmm. So I think I've managed to track down the problem, and it's in the unflattener for Vector{<:Real}. Could you confirm that changing the method of flatten for Vector{<:Real} to
function flatten(::Type{T}, x::Vector{R}) where {T<:Real,R<:Real}
    unflatten_to_Vector(v) = Vector{R}(v)
    return Vector{T}(x), unflatten_to_Vector
end

also solves the problem on your end?

Aha! Looks like it.
This does fix the majority of the inference tests - thanks. The one that doesn't work is the one related to mvnormal.
@inferred flatten(deferred(mvnormal, fixed(randn(5)), deferred(pdiagmat, positive.(rand(5) .+ 1e-1)))) # Fine - what's already tested
v, unflatten = flatten(deferred(mvnormal, fixed(randn(5)), deferred(pdiagmat, positive.(rand(5) .+ 1e-1))));
@inferred unflatten(rand(10,)) # Fails

This does seem fixed with this change to Deferred though - is this one problematic?
function flatten(::Type{T}, x::Deferred) where {T<:Real}
    v, unflatten = flatten(T, x.args)
    unflatten_Deferred(v_new::Vector{T}) = Deferred(x.f, unflatten(v_new))
    return v, unflatten_Deferred
end

->
function flatten(::Type{T}, x::D) where {T<:Real, D<:Deferred}
    v, unflatten = flatten(T, x.args)
    unflatten_Deferred(v_new::Vector{T}) = D(x.f, unflatten(v_new))
    return v, unflatten_Deferred
end

Hmm yeah, it'll have the same issue regarding pushing dual numbers through.
I'm a bit confused as to why this is failing to infer, because when I dig down a bit everything else seems to infer. I wonder whether we're hitting some kind of compiler heuristic and it's giving up trying to infer or something.

Hmm yeah, it'll have the same issue regarding pushing dual numbers through.

Hmm yeah this is very true. This is still just casting.

I'm a bit confused as to why this is failing to infer, because when I dig down a bit everything else seems to infer. I wonder whether we're hitting some kind of compiler heuristic and it's giving up trying to infer or something.

I've been playing around with this a bit - descent and REPL play. For what it's worth, I think the point at which inference breaks is the output of the map in unflatten_to_Tuple(v::Vector{T}). Stepping through, it looks like it infers fine before then, but then breaks after. I found as I think you did, looking at the component pieces of that seem to infer fine, but then fails when put all together, and although I haven't used descend much, I think that that's what I was seeing there too. Could be a general issue with chained deferred expressions which is the general use case.

Maybe we could ask around a bit? See if someone who knows the compiler better could assist?

That makes sense. Definitly beyond me!


Cannot update vuex state with RxJS subscribe

I have two functions in my mutations and two state
const state = {
  files: [],
  uploadProgress: 0
}

const mutations = {

  SET_UPLOAD_IMAGE: (state, files) => {
    state.files = files
  },

  UPLOAD_IMAGE: (state) => {
    StandbyService.uploadImage(state.files).subscribe(progress => {
      state.uploadProgress += progress
      console.log(`Upload Progress ${progress}%`)
    })
  }

}

SET_UPLOAD_IMAGE is used to set the files state and UPLOAD_IMAGE is used to trigger uploading the image to the server. The upload process run and return the upload progress. My uploadImage() return an Observable and I want to update the uploadProgress state whenever the progress is received, but I can't do such that. It keep on giving error in the console as shown in the picture below:

I don't know what to do with this error. I already spent more than 4 hours with this.
I really appreciate for helps and suggestions. Thank you very much.

You should call your service in an action and commit the progress to the mutation.
i.e.
action.js
import StandbyService from '../StandbyService';
import type from '../types';

[type.UPLOAD_IMAGE]({ commit }) => {
StandbyService.uploadImage(state.files).subscribe(progress => {
   commit(type, progress);
 });
}

mutation.js
import type from '../types';

[type.UPLOAD_IMAGE]: (state, payload) => {
  state.uploadProgress = payload
}


Opened application does not show icon

Hi, whatever app I open from the taskbar groups, it is missing the icon which is annoying since its hard to differentiate when multiple apps are opened.

See if the build here works and solves that issue.
I think it may be an issue when it is reading the icon from the application but may not completely finish and locks the icon file. I will look into the icon creation process.

Hey I have the same issue ;/ . But I solved this problem : when  option "Combine taskbar buttons" is set to "never" or "when taskbar is full" in taskbar settings all icons are correctly displayed ;)


Support tarball upgrade

What type of PR is this?

[ ] bug
[ ] cleanup
[ ] documentation
[X] feature

What this PR does / why we need it:
This PR supports upgrading (and downgrading) RKE2 via the tarball method. It is informed by work done in this ticket.
The Rancher Federal Ansible already supports upgrading a cluster using the RPM method. But for some reason it prevents this in the tarball method. The PR simply enables the tarball method to achieve consistency with the RPM method. (It also supports downgrading via tarball because that comes along with the change for free but that's not really the goal.) This branch takes a minimalist approach: It will do what you tell it. It doesn't try to protect the person installer from doing wrong things, such as upgrading Kubernetes in a disallowed way. I made this choice because the converse would require codifying logic in Ansible that fundamentally is owned by the k8s maintainers.
Which issue(s) this PR fixes:
#154
Special notes for your reviewer:
N/A
Testing
I have tested the following scenarios in AWS :
ONE: With a two-instance cluster consisting of one controller and one worker and after each step the resulting cluster version matched the install version.
Airgap install: v1.25.11+rke2r1
Airgap install: v1.25.13+rke2r1
Airgap install: v1.25.11+rke2r1
Uninstall
Airgap install: v1.25.11+rke2r1
Airgap install: v1.25.11+rke2r1
TWO: Tested the same scenarios above with the RPM install method to ensure the changes didn't affect the RPM path:
RPM install: v1.25.11+rke2r1
RPM install: v1.25.13+rke2r1
RPM install: v1.25.11+rke2r1
The RPM downgrade to v1.25.11+rke2r1 was ignored by the Ansible. This was consistent with the pre-PR behavior, and so I stopped here for the RPM testing, satisfying myself that I had not impacted the RPM behavior.
THREE: Tested one scenario with an H/A cluster consisting of 3 control plane instances and 2 workers:
Airgap install v1.25.11+rke2r1
Airgap install v1.25.13+rke2r1
Release Notes
NONE

Thank you for the contribution, @aceeric . In reviewing this I realized a few flaws and decided to take this opportunity to refactor a few things.
The first thing is it doesn't make sense to provide both a install_rke2_version string and a tarball file. I can see confusion arising if a tarball version differs from that var so I decided to have the playbook inspect the version of the tar to determine it's version and ignore that var input if the tar is supplied.
The second thing is I rearranged the version determining logic so that both rpm and tar installation methods use the same task file. this makes it easier to control when/how it's run.
I took your idea of finding the current version of RKE2 and moved it to the previous_install task file to run all the time and make those variables more consolidated.
Lastly, this should now not only allow upgrading via tar, but it should also be idempotent and only do the installation if it's not installed or the versions differ. I didn't like that it seemed to do the binary swap regardless.
 Let me know if you find an issue with any of this.

@mddamato All your points make sense. Regarding the install_rke2_version, the way we use that is so that we don't have to spend time cleaning out the tarball_install directory... This enables one to easily switch between RKE2 versions when testing things. By removing that check, it requires the person installer to remember to clean that directory if they want a different version. Secondly, by removing the check and using the tarball dir, it is now inconsistent with the RPM version which always requires the version variable. So - IMHO it is actually better, more consistent, and more convenient to always require and use the install_rke2_version variable. (My $.02). For our internal project we provide a fair bit of documentation to the person installer to help them understand the variables and what their meaning is. So - we avoid confusion that way.

@mddamato to amplify - We have an Ansible role that supports staging the binaries based on the existing install_rke2_version var and our var stage_rke2: true. The salient part of the role is:
- name: Download objects
  ansible.builtin.get_url:
    url: "{{ url + '/' + item }}"
    dest: "{{ playbook_dir }}/tarball_install"
    validate_certs: false
  with_items:
  - rke2-images.linux-amd64.tar.zst
  - rke2.linux-amd64.tar.gz
  - sha256sum-amd64.txt

So by simply changing install_rke2_version it is possible to perform successive tarball installs with various versions i.e. for compatibility testing. I provide that info as background for why my initial contribution decisioned on the version var. Anyway our additional Ansible will integrate with your approach. Possibly we could contribute our stage_rke2 role at some point. It's pretty simple.


xcode: 8.3.2 is latest version

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you successfully run brew tests with your changes locally?

The Sierra CI will need to be updated accordingly.
Given the content of this PR: cc @MikeMcQuaid

Is the Xcode document no longer getting updated regularly?

This one to be more specific.

@DomT4 Thanks for pointing that out. I based this PR off of the one MikeMcQuaid did for the 8.3.1 bump, so I didn't even think to look around.

@DomT4 Care to take a look and see if I got everything?

No worries, Homebrew has too many moving parts sometimes to remember where they all are 😅. I think you got everything looking at it now 👍.

Is the Xcode document no longer getting updated regularly?

I'd like to see this replaced with autogenerated output somewhere. It's generally a bit of a pain to update it.

@MikeMcQuaid Yeah, bumping the Xcode version requires remembering to modify at least three separate files. Finding some way of centralizing all of that, and then simply pulling from that central store or using it to autogenerate/autoupdate the rest of the associated files seems like a much better approach.


toThrowError fixes.

Found and hotifxed this issue on www: toThrowError('string? that could be a (.*) regex') would throw because we weren't escaping it properly. Fixed it here and added a test.

@cpojer maybe if we're matching the error to string we should use error.message.indexOf(string) instead of converting it to regexp?

although that's not how String.prototype.match works, but it's probably what people are mostly going to do


update to fix bug for lab 1-4

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@Xiaoyuao988 Can request the merge to develop branch? And then we'll merge from develop to main.


feat(status-code): impl Deref for StatusCode to read the inner value

With this PR, it is possible to access the inner NonzeroU16 value without modifying it. This avoids NonZeroU16::try_from(status_code.as_u16()).unwrap(), which introduces a panic, which will be optimised away by the compiler, but e.g. clippy might complain about a missing # Panic-section in the documentation. Due to impl Copy for NonZeroU16, one can simply convert StatusCode to NonZeroU16. DerefMut was not implemented, because this would make the range-check useless.

I would not merge this. This exposes the inner representation of the type, which would prevent ever changing it.

Will this ever change?

Possibly not, but it's good practice for libraries to keep internals private to allow for that without breaking changes. If the representation did change, we could still cheaply produce a u16 in the as_u16() method.
The current solution, .as_u16().try_into().unwrap(), looks fine to me.


imports do not work in flat config yarn pnp

While using Flat Configs with yarn pnp, the CLI command works, but eslint Extension throws error
Uncaught exception received.
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'eslint-config-custom' imported from yarn-flat-config-eslint-error/a/eslint.config.js
    at new NodeError (node:internal/errors:405:5)
    at packageResolve (node:internal/modules/esm/resolve:887:9)
    at moduleResolve (node:internal/modules/esm/resolve:936:20)
    at defaultResolve (node:internal/modules/esm/resolve:1129:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
    at link (node:internal/modules/esm/module_job:76:36)

Error also occurs if public packages are imported
Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@eslint/eslintrc' imported from yarn-flat-config-eslint-error/eslint.config.js
Did you mean to import<EMAIL_ADDRESS>    at new NodeError (node:internal/errors:405:5)
    at packageResolve (node:internal/modules/esm/resolve:887:9)
    at moduleResolve (node:internal/modules/esm/resolve:936:20)
    at defaultResolve (node:internal/modules/esm/resolve:1129:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
    at link (node:internal/modules/esm/module_job:76:36)

Here is a minimal reproduction: https://github.com/agarwalvaibhav0211/yarn-flat-config-eslint-error

Which version of ESLint are you using. Good support for ESLint flat config requires 3.0.5 pre-release.

I am having the exact same issue.
Commands to reproduce the error
yarn install
yarn add @eslint/js #not needed
yarn add eslint        #not needed
yarn dlx @yarnpkg/sdks vscode

Error message
[Error - 9:48:06 PM] An unexpected error occurred:
[Error - 9:48:06 PM] Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@eslint/js' imported from C:\Users\timmi\VSCodeProjects\yarn-flat-config-eslint-error\eslint.config.mjs
Did you mean to import<EMAIL_ADDRESS>    at new NodeError (node:internal/errors:405:5)
    at packageResolve (node:internal/modules/esm/resolve:863:9)
    at moduleResolve (node:internal/modules/esm/resolve:912:20)
    at defaultResolve (node:internal/modules/esm/resolve:1105:11)
    at nextResolve (node:internal/modules/esm/loader:166:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:840:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:429:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
    at link (node:internal/modules/esm/module_job:76:36)

Environment data
Version: 1.88.0 (user setup)
Commit: 5c3e652f63e798a5ac2f31ffd0d863669328dc4c
Date: 2024-04-03T13:26:18.741Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22631
ESLint Extension: v3.0.5 (pre-release)
A reproducible repository can be found here:
https://github.com/HajekTim/yarn-flat-config-eslint-error

This is a problem with yarn pnp and flat config module files (mjs). See https://github.com/microsoft/vscode-eslint/issues/1620#issuecomment-2033982223
Will close the issue since this is something that needs to be fixed in yarn or the yarn sdk generation.

I created https://github.com/yarnpkg/berry/issues/6219 to track this in yarn.


mouse does not worked at core-image-sato in morty

Hello.
I tried to use core-image-sato with vc4graphics.
Sato is booted however mouse pointer does not moved in spite of mouse is moved.
I added the following line to my local.conf.
It seems to work fine.
IMAGE_INSTALL_append = " xf86-input-evdev"

I think xf86-input-evdev should be included IMAGE_INSTALL or dependencies to core-image-sato or else...
Would you let me know your opinion.
Thanks.

The BSP is not maintaining that components and how the input driver is deployed. This issue should be directed to the yocto/poky/oe-core mailing list.

mmm...
but other platform is not happend such a problem.
for exapmle meta-ti, xf86-input-evdev is included XSERVER varibale in omap4.inc.
Such as follows.
PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg"
XSERVER = "xserver-xorg \
           xserver-xorg-module-exa \
           xf86-input-evdev \
           xf86-video-omap"

It really oe-core's issue?
Whether xf86-input-evdev should be used or not depends on the board?
I know already workaround.
So I think that you do not have to fix meta - raspberypi by force.
Thanks.

We can address this in meta-raspberry too by adding this package to the XSERVER too. This will fix your problem so feel free to send a patch to mailing list.

I should have send the patch to mailing list.
I am sorry, I do not know whether it was successfully transmitted.

Discussion is ongoing in mailing list.
It seems that the problem was that meta-raspberrypi did not correspond to the following oe-core's commit.
xorg-xserver recommends xf86-input-libinput since oe-core's commit

| commit 2d005faff6341a81a2afae28860101ba9db51ae8
| Author: Jussi Kukkonen<EMAIL_ADDRESS>| Date:   Wed Oct 26 11:37:38 2016 +0300
|
|    conf: Use xf86-input-libinput by default
| ...

I think it will be accepted Andreas Müller's patch.
I just want the mouse to work on core-image-sato, so that's fine.
Thanks.

I should have read more carefully the open issues earlier.
I also noticed that for any X11 built. Those lines have been removed in december 2016.
https://github.com/agherzan/meta-raspberrypi/commit/c40558173ffd96c499d101155f6c4c2be85d9f0f
They're present in several other BSP layer such as the beagleboard :
https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/conf/machine/beaglebone.conf

Current changes in master should get this back working. Can you give it a try?

Sorry I'm late.
I tried in master. It works fine! thanks!!
By the way, would you fix it in morty branch?

@mickey-happygolucky Would you be able to cherry pick the needed patches from master and send a PR to morty? That would help.

I tried cherry-pick the 52bec45b into morty. However mouse does not work.
I checked a log in a meta directory(oe-core).  I realized that a1668c8721709f3d1bc0078737514111e1985bdd is not in the oe-core in morty.
It seems 52bec45b depends on a1668c8721709f3d1bc0078737514111e1985bdd.
I don't know what I should do...
I think easiest way to make mouse work in morty is revert c4055817.(It is workaround.)
Do you have any ideas?

Hi @mickey-happygolucky . I would take this to the mailing list but my recommendation would be to push a commit to morty which adds a bbeppend xserver-xorg which includes xf86-input-libinput in XSERVER_RRECOMMENDS.

Hello @agherzan . Thanks for your reply.
I have opened a PR according to your advice. Would you check it out?

Thanks @mickey-happygolucky . Looks good. Would I ask too much to push the commits to the mailing list? This is the official way of pushing commits for meta-raspberrypi as stated in README. In this way more people will have a chance of reviewing this change.

Hello @agherzan .
Okay I sent patches to yoctoproject mailing list.
Thanks.


Allow DFS to take in pd.DateOffset objects

Currently DFS and TimeDelta does not take in pd.DateOffset objects. This could require more refactoring with our TimeDelta class. Certain areas to take into consideration:

[ ] training_window must support this new functionality
[ ] use_previous must support this new functionality. Take into account that we need to be able to serialize features.

Addressed by #732


Add examples

For example, how to do depends on Fortran. Perhaps should be bundled rules, if we can figure out what the general form looks like?
http://lagrange.mechse.illinois.edu/f90_mod_deps/

Perhaps a curated list of stack overflow questions would be better? If the FAQ linked to a list they might offer a better format.

I was looking at this more. Fortran dependencies seem like they require a multi-phase build, or a module detector. Say we have a file foo.f90 that needs a module bar.mod. Fortran imposes no restrictions on file naming or search paths, so bar.mod might be generated by baz.f90, in another directory.
As a multi-phase build, the solution is to just keep running shake in staunch and forward-dependencies mode over every Fortran file. On the first build, foo.f90 will fail, due to the missing bar.mod, but baz.f90 will successfully compile and generate bar.mod. On the next build, foo.f90 will succeed and add bar.mod as a dependency, while baz.f90 will be skipped because it's up to date. This can continue through however deep the module dependency graph is (it's not allowed to be cyclic because the fortran compiler doesn't support that).
Using the module detector, you run a program which outputs all modules in a file, once for each file, to foo.f90.mods. Then you create a ModMap rule which depends on all the f90.mods files and concatenates them together, and finally a ModLookup rule which looks the module up in the ModMap and then depends on building the file containing the module; then you scan each file for module usages and run ModLookup for each one. The only hard part is specifying the file list given to ModMap; I'm not sure where it would be constructed or how it would be passed around.


Temsten

Temsten and tRue

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[x] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[x] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Block all
On Sat, 26 Feb 2022, 18:17 TemSten, @.***> wrote:

Temsten and tRue
Why:
Closes [issue link]
What's being changed: Check off the following:

I have reviewed my changes in staging (look for "Automatically
generated comment" and click Modified to view your latest changes).
For content changes, I have completed the self-review checklist
https://github.com/github/docs/blob/main/contributing/self-review.md#self-review
.

Writer impact (This section is for GitHub staff members only):

This pull request impacts the contribution experience

I have added the 'writer impact' label
I have added a description and/or a video demo of the changes
below (e.g. a "before and after video")

You can view, comment on, or merge this pull request online at:
https://github.com/github/docs/pull/15877
Commit Summary

e088d51
https://github.com/github/docs/pull/15877/commits/e088d514d23f5ccc1f151aa2f977570997c69575
Temsten

File Changes
(1 file https://github.com/github/docs/pull/15877/files)

R
content/desktop/installing-and-configuring-github-desktop/indexedTemsten
https://github.com/github/docs/pull/15877/files#diff-c9bdbd6991394342f5554bd3f7b0ad6266de2817894680129345f93a122c6a28
(0)

Patch Links:

https://github.com/github/docs/pull/15877.patch
https://github.com/github/docs/pull/15877.diff

—
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/15877, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWKMZ57XGZCSDN23ZHNRF43U5DHHZANCNFSM5PM5MEZQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>