Mix of Rpi1/Rpi2+CubieTruck (or armv6 vs armv7)

Hi,
Did you try a mix of Rpi1 (armv6) and Rpi2/Cubietruck (armv7) on a kubernetes cluster ? I was thinking of using RPi1 as master and RPI2 as worker nodes so that only armv7 images are run on the Rpi2/CubieTruck.
Or should we have only armv7 k8s cluster on one side and armv6 k8s cluster on the other side ?
I should test your project soon. Do you think it could be compatible with CubieTruck boards top ?

It's already possible to mix and match armv6 and armv7.
Docker and Kubernetes are built for armhf, so they run on both.
So it shouldn't be a problem.
But it could be pointed out in the docs.
I have no experience with cubietruck, but I see arch linux has a guide here, so it should be quite easy to support it.
The guide how to make a Raspberry Pi SD Card is quite similar, which I am using
You could already try to write Arch to both your Rpi1 and 2.

Good to know, I thought that armv6 images could not be used with armv7. Otherwise, I don't see the point on docker hub for example to prefix images with armv6 / armv7 whereas I can see the point for armhf vs armel. Thanks for the precision/clarification.I can now plan having a 4 to 6 k8s cluster now :)
Regarding cubie support, let's try to have a look at it once you have some documentation about what I should do/test. I'll focus first with Rpis.

@nsteinmetz armv6/7 is now pointed out in the docs
I may add the Cubie scripts some day, but I will not be able to test it, because I haven't one

Hi Luxas,
Thanks,
Regarding cubie scripts, if you can provide me some docs on how I can build/use them, I'll be happy to test. But I don't know from where should I start now. So if you guide me, I'll be happy to help.
Nicolas

@nsteinmetz Uploaded code for the Cubie now.
These are the steps that the script does:

Write one ext4 partition that fills the whole SD Card.
Mount the sd card to a temp directory
Download latest Arch Linux ARM filesystem for armv7: http://archlinuxarm.org/os/ArchLinuxARM-armv7-latest.tar.gz
Get the bootloader and write it to the SD Card

Here are the guide: http://archlinuxarm.org/platforms/armv7/allwinner/cubietruck
What you could do to test: sudo sdcard/write.sh cubietruck archlinux kube-archlinux
Then, when you have your system up, run pacman -Syu uboot-cubietruck, reboot and do as usual.
I hope it will work!

As you may have seen, I'll start testing your project first with a Raspberry to get familiar with it. Then, I'll test on Cubie too.
Should ease the fact to distinguish specific cubie bugs from others ;)

Sounds good

Testing this by fetching the code on master.
For the cubietruck, seems code requires two partitions whereas the format builds only one.
In sdcard/os/archlinux.sh, on line 98 & 102, I think it should be $PARTITION1 and not $PARTITION2

Better but not perfect : too late to dive in your code.
As there is only one partition, the boot is expected to be (un)mounted which is not the case.
Partitions mounted
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.security.capability'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.security.capability'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.security.capability'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.security.capability'
tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.security.capability'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
tar: Ignoring unknown extended header keyword 'SCHILY.fflags'
--2015-10-24 23:27:16--  http://archlinuxarm.org/os/sunxi/boot/cubietruck/u-boot-sunxi-with-spl.bin
Résolution de archlinuxarm.org (archlinuxarm.org)… <IP_ADDRESS>
Connexion à archlinuxarm.org (archlinuxarm.org)|<IP_ADDRESS>|:80… connecté.
requête HTTP transmise, en attente de la réponse… 301 Moved Permanently
Emplacement : http://os.archlinuxarm.org/os/sunxi/boot/cubietruck/u-boot-sunxi-with-spl.bin [suivant]
--2015-10-24 23:27:19--  http://os.archlinuxarm.org/os/sunxi/boot/cubietruck/u-boot-sunxi-with-spl.bin
Résolution de os.archlinuxarm.org (os.archlinuxarm.org)… <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connexion à os.archlinuxarm.org (os.archlinuxarm.org)|<IP_ADDRESS>|:80… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 372016 (363K) [application/octet-stream]
Sauvegarde en : « u-boot-sunxi-with-spl.bin »

u-boot-sunxi-with-spl.bin                   100%[=============================================================================================>] 363,30K  --.-KB/s   ds 0,09s

2015-10-24 23:27:19 (3,78 MB/s) — « u-boot-sunxi-with-spl.bin » sauvegardé [372016/372016]

363+1 enregistrements lus
363+1 enregistrements écrits
372016 octets (372 kB) copiés, 0,101826 s, 3,7 MB/s
--2015-10-24 23:27:19--  http://archlinuxarm.org/os/sunxi/boot/cubietruck/boot.scr
Résolution de archlinuxarm.org (archlinuxarm.org)… <IP_ADDRESS>
Connexion à archlinuxarm.org (archlinuxarm.org)|<IP_ADDRESS>|:80… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : non indiqué [text/html]
Sauvegarde en : « /tmp/writesdcard/root/boot/boot.scr »

/tmp/writesdcard/root/boot/boot.scr             [ <=>                                                                                ]   1,62K  --.-KB/s   ds 0s

2015-10-24 23:27:20 (173 MB/s) - « /tmp/writesdcard/root/boot/boot.scr » sauvegardé [1654]

OS written to SD Card
umount: /tmp/writesdcard/boot : non monté

Guess you need something like in write.sh line 188:
if [ $MACHINENAME eq "cubietruck"]; then
    umount $ROOT
else
    umount $BOOT $ROOT
fi

So as is, cubietruck does not start ; will start from scratch with a vanillia archlinux install to check first it works well and then will try to find what's missing in our context.

Ok found the issue, my proxy blocked the download to the boot.scr files ; so it was an html file and not the expected file ;-)
Just need to whitelist this file :)

So beyond the mount issue and the whitelist issue on proxy side, works like a charm ; kubie-config install in progress :)

... I still have an issue with enabling k8s-worker but I'll open a different issue tomorrow.
Good night :)

OK, glad it (partially) worked.
I released a bugfix version yesterday, v0.5.6
I think you used the latest version as I uploaded it 22:42 EEST to master yesterday.
In that case the tar warnings didn't obey the redirect :)
Will test it. Already patched umount $BOOT on cubie.

FYI, I will make a new branch named dev for developing between releases.
Then when I make a release those changes are merged into master.
So if you want to download code between releases, switch to dev

Now I'm using curl instead of wget for getting the boot files.
So now wget isn't a dependency anymore.
I also fixed:

I think it should be $PARTITION1 and not $PARTITION2

Uploaded to dev
[archlinux.sh] (https://github.com/luxas/kubernetes-on-arm/blob/dev/sdcard/os/archlinux.sh)

Works now as expected on dev branch => close :)
thanks !

maybe the only point would be to remember at the end to do the:
pacman -Syu uboot-cubietruck

I only remind now that I should do it after many sdcard initialisation.
Or to add it in the kubie-config install process ?
As french with a azerty keyboard, I also need to set it correctly. Could be also an enhancement.
I also need to add a static ip but it's more my own issue than a generic one.

I am planning to make it possible to add customized scripts.
Will open a different issue for it.
The uboot install belongs to this project.
Here is a guide about keyboard layouts: https://wiki.archlinux.org/index.php/Keyboard_configuration_in_console
You may add static ip via your router or via arch linux

Yep, I'm a loadkeys fr && localectl set-keymap fr master now :)
So we keep this bug opened only for the uboot-cubietruck package.

I'm working on this right now.
The proposed tree:

os/

archlinux.sh - the file that writes the os to the card
archlinux/ - optional directory with extra commands for kube-config

commands.sh - specifies commands just for arch linux (like pacman commands)
cubietruck.sh - customized commands for cubietruck
rpi-2.sh - customized commands for Raspberry Pi 2

The good thing with this approach is that, long-term, kube-archlinux may evolve to systemd.
So the same rootfs could re-used on e.g. Debian 8 (Bananian or HypriotOS)
WDYT?

Hi,
Sounds good at a first glance ; I should test latest release this week-end rather than dev version (unless you tell me the opposite)

It worked well last time I tested v0.5.8 on Raspberry Pi 2
I will probably look at the Raspberry Pi 1 compilation after this.
go1.5.1 will be used then. Maybe bugs are fixed with latest version.

I am testing latest dev right now, but the Arch Linux ARM servers seems to be down.
I don't think dev is stable right now. I'll notify when you may test.
But, did everything work for you? The whole system with private registry and so on?

I was about to set up my 2nd cubietruck ; I started writing the sdcard and when I came back, I noticed  archlinuxarm servers were down. So my k8s-master seems fine but he's still alone right now. So I did not play wit it more so far (but so far, so good as per https://github.com/luxas/kubernetes-on-arm/issues/13 :)

You can use http://ftp.halifax.rwth-aachen.de/archlinux-arm/ as an alternative mirror it seems ;-)

Thanks for the link!
If the servers are down for a longer time, I maybe have to use that as a fallback.

Seems back online btw !

I think the dev branch is quite stable now. You may try to write the SD Card for cubietruck. It should install the uboot package at kube-config install.
I haven't tested everything on dev and RPi 1 isn't supported yet I think, I'll upload commits to dev regulary

Hi,
I'll wait for the RPI1 being supported to lead further tests ; quite busy (seems everyone for others projets I'm in just wake up these last days after months of hibernation ;-) )

@nsteinmetz Just now I'm working on on v0.6.0, and that release is a big one.
Some changes:

cubietruck full installation
Upgrade Kubernetes to v1.2.0-latest
Upgrade flannel => v0.5.4, etcd => 2.2.1, registry => 2.2.0, go => 1.4.3
Now it's possible to build the Kubernetes binaries with Go 1.5.1, but it's much slower so it's not default
Fix the bug that makes this not run on armv6, e.g. Raspberry Pi 1
Add windows downloads
Enhance security with certs and ServiceAccounts

This is something that isn't working on "real" machines either, and I found the solution :smile:
Upstream: https://github.com/kubernetes/kubernetes/issues/16965 and https://github.com/kubernetes/kubernetes/issues/16987

maybe add a loadbalancer

As you see, there is much to do.
I would be glad if you tested this when I release it.
I'll keep you updated.

It's a little bit early for Christmas ;-)
Let me know once I can test it !

Hi,
I'm sure you saw this ; are you aware of this project ? Looks quite close to yours.
Btw, any update for the 0.6.0 release ? ;-)

No, I hadn't seen that blog post. Thanks for notifying me. :smile:
The v0.6.0 is coming soon, I hope this weekend.
It has been so many things to do.
Just now I have a PR pending on mainline k8s. https://github.com/kubernetes/kubernetes/pull/17213
And this release is about a week delayed because of docker v1.9.0 bug on Arch Linux ARM at least: https://github.com/docker/docker/issues/18125
However, today I have got everything up and running as it should. This time it was harder than usual, because these things isn't in mainline k8s (yet).
Now I just have to package everything.

Finally released!
Now you may test it and (I hope not :smile:) return bugs.
This issue is open for the uboot package for cubietruck and for RPi 1 support.
They should both be fixed. Test it please!
There is also a lot of other fun things I mentioned earlier.
Soon, it's Christmas anyway :)

Woot ! :)
I'll test over the coming week and let you know !

Could this be closed?
Was the uboot-cubietruck package automatically installed?

Yes it was ! :)
The only investigation point could be that you need an extra "Y" to flash the boot files. Not sure you can enforce it as it may be sensible.
I thnk it's acceptable so far.
Thanks a lot for making cubietruck supported so fast ; Really enjoy it !

That was strange, I suppose you mean that this line asked for [Y/n] when installing uboot?
https://github.com/luxas/kubernetes-on-arm/blob/master/sdcard/rootfs/kube-archlinux/etc/kubernetes/dynamic-env/cubietruck.sh#L5

Exactly, it's maybe within uboot-cubietruck package itself and ouf of pacman control as flashing boot record is a sensible task ? That's why I say it's not a big issue to keep this [Y|n] step.


Improve textual representation of Process::Status

Process::Status currently has very intricate #to_s and #inspect formats. They're the default implementations inherited from Reference and don't convey much relevant information.
I'm proposing to implement a more meaningful representation.
#to_s currently returns the type name and object id in the typical format of Reference#to_s (e.g. #<Process::Status:0x7f9fd8a17c40>). That doesn't make much sense. The object id is pretty much irrelevant.
Instead, it should simply return a textual representation of the exit code or signal:
process_status(0).to_s           # => "0"
process_status(128).to_s         # => "128"
process_status(Signal::HUP).to_s # => "HUP"

(I'm using a ficticious process_status helper to represent instances with certain values because Process::Status doesn't have a public or easily usable constructor - which should probably be added as well.)
#inspect currently enhances the sparse information output of #to_s by the names of the instance variables and their values. @exit_status is the only ivar and its value is bit encoded, thus not trivial to read. This isn't very useful.
Instead, it should return a textual representation of the exit code or signal, like #to_s but enhanced with the type information of Process::Status for more expressiveness.
process_status(0).inspect           # => "Process::Status[0]"
process_status(128).inspect         # => "Process::Status[128]"
process_status(Signal::HUP).inspect # => "Process::Status[Signal::HUP]"

Shouldn't the second snippet use #inspect?
For Windows it might be helpful to have things like process_status(0xC0000005_u32).to_s # => "STATUS_ACCESS_VIOLATION", but this requires us to define an enum for the possible NTSTATUS values first; yet not all NTSTATUS values really correspond to abnormal exit codes either.

Shouldn't the second snippet use #inspect?

Yeah, fixed 😅

Process::Status[Signal::HUP] is technically ambiguous because it could also represent the signal that stopped a process (i.e. exit_status == 0x017F, like here) rather than terminating it. I think it is inevitable to support stop statuses in Process::Status too if #inspect is involved.

But currently there's no way to express a stopped signal, right? So I'm thinking this should be left for an enhancement later.
Now we only need make sure that the inspect syntax and constructor signature are compatible to such an amendment. And I think they are. One option could be to use a named parameterlike this: Process::Status[stopped: Signal::HUP]`.

I think they show up from Process#wait with ptrace, although I don't know about the details.


Image Scraping Algorithm Design

design efficient algorithms for image scraping, considering factors such as data volume, network latency, and resource utilization, to ensure scalability and performance.

assign this please

greeting's of the day ma'am kindly assign this issue to me . looking forward to your response to accept my request

If this issue is still pending, kindly assign this to me! @RituKumari98


chore: add auto-release process

📦 Published PR as canary version: 0.0.6--canary.11.9684054.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

self merging @ghengeveld


Roll engine 0816c040fbba..e43a100b3758 (20 commits)

https://github.com/flutter/engine/compare/0816c040fbba...e43a100b3758
git log 0816c040fbba..e43a100b3758 --first-parent --oneline
2020-02-03<EMAIL_ADDRESS>Roll src/third_party/skia f1e316ff39e7..af99f3ee6017 (13 commits) (flutter/engine#16335)
2020-02-03<EMAIL_ADDRESS>Update buildroot to 02b77827fd4ac639f1c048c6340262cdb4c2a3ab. (flutter/engine#16339)
2020-02-03<EMAIL_ADDRESS>Disable flaky MessageLoop tests on Fuchsia. (flutter/engine#16340)
2020-02-03<EMAIL_ADDRESS>[fuchsia] Add additional contributing instructions for Googlers (flutter/engine#16337)
2020-02-03<EMAIL_ADDRESS>Roll src/third_party/dart ed441e48d055..c8ed304e979a (1 commits) (flutter/engine#16328)
2020-02-03<EMAIL_ADDRESS>Roll fuchsia/sdk/core/linux-amd64 from AtXwP... to Tszo5... (flutter/engine#16334)
2020-02-03<EMAIL_ADDRESS>Roll src/third_party/skia 3d05192abedf..f1e316ff39e7 (3 commits) (flutter/engine#16329)
2020-02-03<EMAIL_ADDRESS>Roll fuchsia/sdk/core/mac-amd64 from jtwQF... to 6h3IH... (flutter/engine#16332)
2020-02-03<EMAIL_ADDRESS>Change NSLog to FML_DLOG (flutter/engine#16331)
2020-02-01<EMAIL_ADDRESS>Roll src/third_party/skia 5d92ae2b56df..3d05192abedf (1 commits) (flutter/engine#16326)
2020-02-01<EMAIL_ADDRESS>Roll src/third_party/skia 776293dceefd..5d92ae2b56df (1 commits) (flutter/engine#16325)
2020-02-01<EMAIL_ADDRESS>Roll src/third_party/skia 1b80c357926b..776293dceefd (2 commits) (flutter/engine#16324)
2020-02-01<EMAIL_ADDRESS>use echo to test whether host is up (flutter/engine#16322)
2020-02-01<EMAIL_ADDRESS>Revert "Modifies accessibility bridge to populate new node fields in semantic… (#15116)" (flutter/engine#16323)
2020-02-01<EMAIL_ADDRESS>Roll fuchsia/sdk/core/mac-amd64 from x6sVj... to jtwQF... (flutter/engine#16320)
2020-02-01<EMAIL_ADDRESS>Roll src/third_party/dart 91a3ea89c8e4..ed441e48d055 (4 commits) (flutter/engine#16319)
2020-02-01<EMAIL_ADDRESS>Remove all uses of the redundant flutter_root variable. (flutter/engine#16311)
2020-02-01<EMAIL_ADDRESS>Roll src/third_party/skia 4513cdde4912..1b80c357926b (1 commits) (flutter/engine#16318)
2020-02-01<EMAIL_ADDRESS>Roll src/third_party/dart 5ae5aff6406a..91a3ea89c8e4 (22 commits) (flutter/engine#16310)
2020-01-31<EMAIL_ADDRESS>Roll fuchsia/sdk/core/linux-amd64 from VMcGV... to AtXwP... (flutter/engine#16308)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Trybots failed. These were the failed builds: https://github.com/flutter/flutter/runs/424510130 , https://github.com/flutter/flutter/runs/424510096 , https://github.com/flutter/flutter/runs/424510003 , https://github.com/flutter/flutter/runs/424509989 , https://github.com/flutter/flutter/runs/424509980

Commit queue failed; closing this roll.


"Urgent Notification: Account Compromised - Please Take Immediate Action"

Unauthorized Access to Your GitHub Account
Dear valued GitHub user,
It has come to our attention that your GitHub account was accessed without authorization. To prevent any further security breaches, we kindly ask you to reset your password and revoke access to any unauthorized users by visiting the following link: Reset Password
We appreciate your prompt attention to this matter as the security of your account and personal information is our top priority.
Thank you for your cooperation.
Sincerely,
The GitHub Security Team

List of Potentially Compromised Accounts:

@jaradtke-aws
@jweite-amazon
@drewvanstone
@sauravonwww
@LienNguyen2910
@burhan
@navinsoni
@lewisdiamond
@cheeseandcereal
@kstribrnAmzn
[And many more...]

Note: This message is being sent to multiple GitHub users who may have been affected. Please take immediate action to secure your account.

DO NOT Click the password link in this issue. It does not take you to github.com. Hover over the link and you can see it actually takes you here http://github.hudevelopers.online/!


Support older fltk-1.3.3

Was able to compile and run the button example using my standard fltk-1.3.3 that is available on Fedora 25.
Needed to install several development libraries, nothing special: fltk, fltk-devel, fltk-static, libjpeg-turbo-devel, libXcursor-devel, libXinerama-devel.
After this cabal build.

Thanks for the PR! Can I ask the use case for supporting an older FLTK? Is it simply that package managers haven't caught up yet?

Another reason I ask is that I try to keep a list of 'nice' versions of the Haskell functions. In the case of Image, for example, I have a script the reads down the instances and generates the functions from the type signature. If older versions are supported the Haddocks will be wrong/missing. I can update the parser to take ifdef's into account if it's really needed.

Indeed, many distros still supply the older, stable, version it will take some time before 1.3.4 is the new standard. It will make it easier for new developers.

Ok, sounds good. I have a patch on your master branch with some fixes for your PR. Once you apply I'll merge. And once I fix the parser that generates the functions in the Haddocks I'll upload a new release.

Applied your patch, built and ran button example successful.

Great. Thanks!

Just came up with something I need to verify, is the FL_API_VERSION known in all files? If not I don't think it is a correct fix.

Ok, fltk-1.3.3 doesn't have the FL_API_VERSION so I think we're good.


Flutter app restarts when it is launched again from Recent apps after few seconds

I wrote my fairly simple flutter app and was testing in debug mode in my device. However when I try to relaunch the app again from recent apps of my device the app restarts, no state is saved for the app(even if I relaunch after few seconds).

Flutter doesn't support state saving on Android.

Can we expect flutter to support state saving in future releases?

What state do you expect to be saved?
You can save state yourself on lifecycle callbacks.
Also in debug mode restarting the app might not work if you used hot-reload because changes applied using hot-reload are not added to the APK, they are applied only in-memory to the Dart VM.

Flutter doesn't maintain state for you, you need to do that yourself.
You need to decide what state you want to persist, perist it, reload it, re-apply it after loading (like navigating to a route)

Maybe you know any examples how default Navigator state can be persisted?
All navigation in application is implemented with Navigator.push(Route)
Even official Flutter gallery doesn't maintain its navigation state.

/cc @Hixie

+1 This is an important feature to have in an app. It'd be good if there was some guidance somewhere how to persist the navigation state.
User experience deteriorates massively if one has to re-fill say a long form just because they left the app to look up something on a different app and then returned just to find themselves back to square 1...

It sounds like this is a duplicate of https://github.com/flutter/flutter/issues/6827. Please feel free to re-open with additional details if this issue is in fact about something not covered by the linked issue. Thanks!

You can also use the runApp(new MyWidget) function to do something similar
This is what this function does:
Inflate the given widget and attach it to the screen.
The widget is given constraints during layout that force it to fill the entire screen. If you wish to align your widget to one side of the screen (e.g., the top), consider using the Align widget. If you wish to center your widget, you can also use the Center widget
Calling runApp again will detach the previous root widget from the screen and attach the given widget in its place. The new widget tree is compared against the previous widget tree and any differences are applied to the underlying render tree, similar to what happens when a StatefulWidget rebuilds after calling State.setState.
https://icetutor.com/question/flutter-how-to-force-an-application-restart-in-production-mode


4 walletinfo

Description
After revisiting the component, I've seen that it's not looking great in dark mode, so I changed the className.
Before :

After :

Related Issues
Improves #4
Your ENS/address: yassirakh.eth

closing this I think we already merged this in #18, please feel free to add comment if I am mistaken 🙌


Drag volume control

Drag volume control is shown only on landscape mode.
Can this be shown on on portrait too?
How to disable this drag volume functionality completely?

I didn't implement the option to disable it , I can add it in next release
And It should work in portrait too, so I will check that

its not visible only on android (portrait)

can you test on flutter_meedu_videoplayer: ^4.0.9-dev.1
disabling volume swipes can be done like this
  final _meeduPlayerController = MeeduPlayerController(
    controlsStyle: ControlsStyle.primary,
    enabledControls: EnabledControls(
      volumeSwipes: false
    )
  );

volumeSwipes works as intended, brightnessSwipes is working.
When both are false, brightness is stuck and ui is shown forever

when i have this, then when i press volume button, drag bar is still showing up
    enabledControls: const EnabledControls(
      volumeSwipes: false,
      brightnessSwipes: false,
    ),

volumeSwipes works as intended, brightnessSwipes is working.
When both are false, brightness is stuck and ui is shown forever

Weird, will test again, that's on mobile right?

yes, tested on android.

fixed on 4.0.9


Fix unicode encode error

Fix UnicodeEncodeError when sys.stdout.encoding is None and Unicode is sent -- e.g.:
Traceback (most recent call last):
  File "/var/folders/gw/w0clrs515zx9x_55zgtpv4mm0000gp/T/tmp5eApc3", line 7, in <module>
    messages.message(bjork)
  File "/Users/marca/dev/git-repos/teamcity-python/teamcity/messages.py", line 30, in message
    self.output.write(message)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xf6' in position 14: ordinal not in range(128)

Cc: @shalupov, @djeebus, @georges

hey guys looks like you got the wrong georges :)

Oops, sorry @georges! :smile:

:+1:

Fixing the tests...

OMG, all the Travis tests are finally passing! \o/
Supporting everything from Python 2.4 to Python 3.4 is no walk in the park. :smile:

Thank you! Your test is failing on Windows, I'll fix ti myself.


Update test for #20577

Closes https://github.com/Microsoft/TypeScript/issues/20577.
https://github.com/Microsoft/TypeScript/issues/20577 seems fixed by https://github.com/Microsoft/TypeScript/pull/21027. I just updated the test with a new test case.

thanks!


Git VS Code issue when create new branch

Type: Bug
Creating issue scenario
Create a folder gittest
create a file in folder index.html
write some text in index.html
init git and commit everything
While index.html open in vs code
create a new branch by following command

git checkout -b test2

confirm currently opened branch, its test2

git branch

Make changes to index.html and commit
switch to master branch
open index.html all changes are here as well.
VS Code version: Code 1.70.2 (e4503b30fc78200f846c62cf8091b76ff5547662, 2022-08-16T05:35:13.448Z)
OS version: Windows_NT x64 10.0.19044
Modes:

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.71.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I checked my VS Code it says its a latest version

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette).
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


concurrently: command not found when running yarn create

yarn create ether-dapp my-dapp

output
Output:
/bin/sh: concurrently: command not found

yarn create ether-dapp my-dapp

output
Output:
/bin/sh: concurrently: command not found

Make sure to install dependencies at the root of the project.


Update UG features: addi, deletei

Update features section in UG for :

Adding inventory item: addi
Deleting inventory item: deletei

Codecov Report

Merging #46 (f9d791b) into master (4e2b1da) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #46   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Manage workflow data

CLOUDBLD-8271

This PR contains changes to manage workflow data so that it can be shared by different tasks through the build pipeline. The data is written into the context_dir, which is an input from the atomic-reactor command line. This PR covers most of the original design except:

build_result is kept as usual and written into the workflow.json together with others. The build result should be platform-specific, the build task should handle the details of build result for every platform. The load/dump for build result objects can be implemented based on the changes in PR.

some data are not removed since corresponding plugins are not updated yet and still reference those data, e.g. plugins_workspace and files.

*_results attributes are not combined into one plugin_results. After looking into more details, I found it probably introduce new problem by merging *_results, because every runner object has its own attribute plugins_results which references to a _results individually. From my point of view at this moment, it is probably not worth to merge and maybe we should reconsider a clearer way to collect results from plugins.

Maintainers will complete the following section

[x] Commit messages are descriptive enough
[x] Code coverage from testing does not decrease and new code is covered
n/a JSON/YAML configuration changes are updated in the relevant schema
n/a Changes to metadata also update the documentation for the metadata
n/a Pull request has a link to an osbs-docs PR for user documentation updates
n/a New feature can be disabled from a configuration file

rn updated

Finalized in #1789


Add prompt on logout

Right now it's a single click, make a prompt so you don't accidentally log out.

Should be fixed now


Logging to an xUnit compatible format XML file.

I've got some Symfony console based apps that currently write to the console and/or to Monolog. All works fine.
I want to incorporate some of these apps into our pipeline and have error logs be processed by the pipeline tear down process.
The pipeline only understands jUnit format (it is primarily for using PHPUnit testing, but, for example, PHP Code Styling can generate appropriate jUnit logs, so you get to see what unit tests have failed as well as the code styling issues in the results page).
And so I was wondering if anyone knew of formatter for Monolog that would achieve a similar result.
I suspect I'm going to have build my own and base it upon https://github.com/Seldaek/monolog/blob/master/src/Monolog/Formatter/HtmlFormatter.php
Suggestions/tips gratefully received.

Haven't heard of anything like that..


Abort unfinished transaction on Drop

It would be convenient if a transaction that wasn't explicitly flushed with done() or commit() instead automatically called abort() when dropped.
This would allow users to more easily bail with the ? operator without leaving uncommited, half-finished transactions around.

I agree with the intention but indexed db transaction behavior is dependent a lot on each browser's implementation.
Specification for abort() says that all the pending requests will be aborted (which does not mean all the requests make in that transaction). Depending on the browser implementation and user code, transaction may get auto committed even before calling commit(). I'm not sure if there's an easy way to handle this.
Worth reading: https://stackoverflow.com/questions/27326698/indexeddb-transaction-auto-commit-behavior-in-edge-cases

I wasn't aware of that behaviour, but it does make sense. Thanks for the link.
If I understand the answers from a linked question correctly, transactions may commit as soon as the callbacks for all requests finish. Given the way the crate waits for each request to finish before returning control to a caller, I can basically never assume that 2 consecutive actions on an object store don't have a commit occur between them? That's unfortunate.
Without the ability to resume execution from the callbacks then, I have to wonder how useful it even is to expose the transaction layer to a user that can only make limited use of it. Though if it does usually work as expected, maybe that's reason enough. I haven't done any testing yet.
A possible, albeit hacky workaround would be to explicitly not return from the callbacks, until the next request is started or the transaction is otherwise explicitly finished by the user. That might go against the spirit of being a light wrapper, but it would keep the transaction alive, and dropping would work as expected. However, given that transactions should not be kept active while doing other works such as web requests, it might cause other issues for unsuspecting users.
I'm just spitballing. You've clearly got a much better idea than me about how the internals work to judge what appoach might work. :)

@ShaddyDC If someone wants fine grained control over callbacks, they can always use idb-sys crate which exposes raw indexed db API without async/await.

I have to wonder how useful it even is to expose the transaction layer to a user that can only make limited use of it.

Most of the times, it works as expected. There're also tests for testing abort() of transaction. But, because indexed db implementation can choose to auto-commit a transaction (because of various reasons like doing IO in event loop), it is unreliable and does not guarantee that the transaction will be aborted.
Also, I'm not sure how to handle abort failures if we call abort() in Drop implementation.

That makes sense. Should I close the issue or would you prefer to keep it open in case you or anybody else has any good ideas for it in the future?

I think eventually this needs to be resolved. We can keep it open for now.

Hmm… maybe an idea: what if Transaction were not a type, but a function that takes a Future?
The usage would then be something like (pseudo-code for clarity):
db.transaction(&["store"], ReadWrite, |transaction| async move {
    transaction.get("foo")?.await;
})?;

Then, the various transaction functions would:

submit a request to the IdbTransaction
make the success and error callbacks both poll the provided future exactly once, to let it make progress
assert that polling the provided future once results to either the future completing, or a new request being submitted to transaction

WDYT? This is still a bit hand-wavy, but I'm thinking it could make sense to have something like that :)

Well, I gave it some more thought, and then decided to go ahead and implement it. It's now available at https://crates.io/crates/indexed-db ; though I have not implemented cursors yet — I'll first integrate it with my personal projects, check that the APIs are reasonably easy to use, and implement cursors after that :)

I can confirm that the API of indexed-db (as of version 0.2.2, I had to make some changes after trying to use it a bit more) seems to work fine for me, and AFAICT prevents any invalid use of transaction that'd cause it to auto-commit.
Hope this helps :)


meta-balena-raspberrypi:layer.conf: Add PoE+ overlay to rootfs

Include the PoE+ overlay to rootfs for supporting this newer hat
Changelog-entry: Add Raspberry Pi PoE+ overlay to rootfs
Signed-off-by: Florin Sarbu<EMAIL_ADDRESS>

@balena-ci I self-certify!

@resin-jenkins test this please

@resin-jenkins test this please

@resin-jenkins test this please

@resin-jenkins retest this please

@balena-ci rebase


issue on kali linux 2018.4

Issue Description
I experience an issue when I... and the results I expected are...
Reproduction Steps

Start King Phisher
Do something to trigger the crash

Environment Details

Host OS: Ubuntu 18.04 GNOME, Kali 2, etc.
King Phisher Version: x.y.z
Error Details / Stack Trace

If you are opening an issue regarding the client, copy text from the "Error
Details" of the error dialog in the client here. If you are opening an issue
regarding the server copy the relevant lines from the logs here.

journalctl -xe
Nov 23 15:43:59 Legion python3[22879]:     return list(lex)
Nov 23 15:43:59 Legion python3[22879]:   File "/usr/lib/python3.6/shlex.py", line 295, in next
Nov 23 15:43:59 Legion python3[22879]:     token = self.get_token()
Nov 23 15:43:59 Legion python3[22879]:   File "/usr/lib/python3.6/shlex.py", line 105, in get_token
Nov 23 15:43:59 Legion python3[22879]:     raw = self.read_token()
Nov 23 15:43:59 Legion python3[22879]:   File "/usr/lib/python3.6/shlex.py", line 136, in read_token
Nov 23 15:43:59 Legion python3[22879]:     nextchar = self.instream.read(1)
Nov 23 15:43:59 Legion python3[22879]: AttributeError: 'ArrayElement' object has no attribute 'read'
Nov 23 15:43:59 Legion systemd[1]: king-phisher.service: Control process exited, code=exited status=1
Nov 23 15:43:59 Legion systemd[1]: king-phisher.service: Failed with result 'exit-code'.
Nov 23 15:43:59 Legion systemd[1]: Failed to start King Phisher Server.
-- Unit king-phisher.service has failed.
-- The result is RESULT.
Nov 23 15:43:59 Legion sudo[21335]: pam_unix(sudo:session): session closed for user root
Nov 23 15:45:01 Legion CRON[22894]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 23 15:45:01 Legion CRON[22895]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Nov 23 15:45:01 Legion CRON[22894]: pam_unix(cron:session): session closed for user root
Nov 23 15:47:10 Legion org.gnome.Shell.desktop[1615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x34000f8 (server_con
sudo ./KingPhisherServer -f -L DEBUG server_config.yml DEBUG    target diretory: /opt/king-phisher INFO     checking for the pipenv environment DEBUG    pipenv path: '/usr/bin/pipenv' DEBUG    pipenv Pipfile: /opt/king-phisher/Pipfile Loading .env environment variables… Traceback (most recent call last):   File "/usr/bin/pipenv", line 11, in      load_entry_point('pipenv==11.9.0', 'console_scripts', 'pipenv')()   File "/usr/lib/python3/dist-packages/pipenv/v
[15:55]  journalctl -xe Nov 23 15:43:59 Legion python3[22879]:     return list(lex) Nov 23 15:43:59 Legion python3[22879]:   File "/usr/lib/python3.6/shlex.py", line 295, in next Nov 23 15:43:59 Legion python3[22879]:     token = self.get_token() Nov 23 15:43:59 Legion python3[22879]:   File "/usr/lib/python3.6/shlex.py", line 105, in get_token Nov 23 15:43:59 Legion python3[22879]:     raw = self.read_token() Nov 23 15:43:59 Legion python3[22879]:   File "/usr/lib/pytho
Linux Legion 4.18.0-kali2-amd64 #1 SMP Debian 4.18.10-2kali1 (2018-10-09) x86_64 GNU/Linux
i use pipenv v11.9.0-1

Please try starting the King Phisher Server from the command line and provide me the full stack trace.
sudo ./KingPhisherServer -L DEBUG -f -c server_config.yml

sudo ./KingPhisherServer -L DEBUG -f -c server_config.yml
DEBUG    target diretory: /opt/king-phisher
INFO     checking for the pipenv environment
DEBUG    pipenv path: '/usr/local/bin/pipenv'
DEBUG    pipenv Pipfile: /opt/king-phisher/Pipfile
Loading .env environment variables…
usage: main.py [-h] [-v] [-L {DEBUG,INFO,WARNING,ERROR,FATAL}]
[--logger LOGGER] [--gc-debug-leak] [--gc-debug-stats] [-f]
[--update-geoip-db] [--verify-config]
config_file
main.py: error: unrecognized arguments: -c

sorry about that drop the -c and make sure server_config.yml is your server configuration file, and run the command from you king-phisher folder.

resolved I deleted pipenv and proceeded to / tools / install
and the problem has been solved

Awesome! happy phishing.

thank you


EditorNode3DGizmo::add_unscaled_billboard improper scaling

Godot version
3.3.3.stable
System information
Windows 10
Issue description
Currently, in the implementation of add_unscaled_billboard there seems to be an unnecessary multiplication by 100
mesh->set_custom_aabb(AABB(Vector3(-selectable_icon_size, -selectable_icon_size, -selectable_icon_size)
* 100.0f, Vector3(selectable_icon_size, selectable_icon_size, selectable_icon_size) * 200.0f));

This makes p_scale higher than 0.05 overkill (this scale is used everywhere else in the editor for 3d billboard gizmos, which is why this problem might have been overlooked) and nothing around gizmo becomes clickable at this point.
Steps to reproduce

Creating a basic EditorSpatialGizmoPlugin, that calls add_unscaled_billboard on redraw with a scale larger than 0.05, even default argument of 1.0 would showcase this issue.
Realize that icon itself is pretty small, while the clickable area around it grows exponentially, making the huge area around gizmo unclickable.

Minimal reproduction project
No response

If this is exposed to scripting, this can only be fixed in 4.0 to avoid breaking existing plugins. In 3.x, we can add a note in the documentation to give a suggested p_scale value range.

It seems that I made few mistakes while setting up material for billboard use, after looking into the source code more in-depth I found out how the material is being set up by the editor itself, and now it works exactly like every other billboard. Code had to look something like this:
godot::Ref<godot::SpatialMaterial> new_material;
new_material.instance();

godot::Ref<godot::Texture> texture = godot::ResourceLoader::get_singleton()->load("res://Textures/Editor/Script.png");

new_material->set_flag(godot::SpatialMaterial::Flags::FLAG_UNSHADED, true);
new_material->set_flag(godot::SpatialMaterial::FLAG_ALBEDO_FROM_VERTEX_COLOR, true);
new_material->set_flag(godot::SpatialMaterial::FLAG_SRGB_VERTEX_COLOR, true);
new_material->set_cull_mode(godot::SpatialMaterial::CULL_DISABLED);
new_material->set_depth_draw_mode(godot::SpatialMaterial::DEPTH_DRAW_DISABLED);
new_material->set_feature(godot::SpatialMaterial::Feature::FEATURE_TRANSPARENT, true);
new_material->set_texture(godot::SpatialMaterial::TextureParam::TEXTURE_ALBEDO, texture);
new_material->set_flag(godot::SpatialMaterial::FLAG_FIXED_SIZE, true);
new_material->set_billboard_mode(godot::SpatialMaterial::BillboardMode::BILLBOARD_ENABLED);
new_material->set_render_priority(godot::SpatialMaterial::RENDER_PRIORITY_MIN);

add_material("main", new_material);


Configuring ErrorProne with Java 16

Description of the problem / feature request:
The Error Prone Installation page contains configuration for Java 16 that sets source and target down to Java 8. Is this intended?
<source>8</source>
<target>8</target>

It was intentional but it's just supposed to be an example, Error Prone works with other source versions and it's fine to change that to whatever language level your project is using. We could leave that part of the configuration out, or add a comment to that effect.

Since this is on the section that talks about Java 16, I think the documentation should reflect the proper configuration for that version.

It was intentional but it's just supposed to be an example, Error Prone works with other source versions and it's fine to change that to whatever language level your project is using. We could leave that part of the configuration out, or add a comment to that effect.

The doc could use <release> instead of <source>/<target> though, as that's a better way to cross-compile (doesn't work for everyone but should be OK most of the time); e.g. use <release>11</release>.
It could also have a note about Maven toolchains (https://maven.apache.org/guides/mini/guide-using-toolchains.html) rather than cross-compiling (and then maybe have <release>16</release> or <source>16</source><target>16</target>)

Since this is on the section that talks about Java 16, I think the documentation should reflect the proper configuration for that version.

You can very well cross-compile code for use with earlier JVMs though (not recommended, but possible: https://www.cloudbees.com/blog/beware-sirens-target-call, http://www.draconianoverlord.com/2014/04/01/jdk-compatibility.html; AFAICT, using -release is safe though)


Querier: Deterministic buffered queries

I plan to give a formal proposal + PoC, but starting an issue to cover the idea to solve the problem we have on the Querier fanout side which creates confusion, annoyance and overall extra latency.
I explained this problem to the team and on the latest Community Hours, but for initial info:
Problem
Current Querier algorithm looks following:

While it's not easy to spot, but what is happening in practice is that MergeSort is choosing which storeAPIs to fetch message from one-by-one. On average it's round robin, but that depends on order of series. In practice this looks as follows:
If we do query (start_timestamp_ms:1626134100000 end_timestamp_ms:1627344000000 matchers:<type:RE name:"__name__" value:"continuous_app_metric9.*" > ) for 2w from 5 different StoreAPIs (I literally used  interactive_test), it takes 6+ seconds on my machine:

This test has Jaeger so I added lower granularity spans that tells us exactly wait-times for (https://github.com/bwplotka/thanos/commit/e75ce708234384fbf7dfcab13294aaf17aaa18fd):

fetching single series message from store: querier.streamSeriesSet.waitForStoreResult
merge sort actually receiving it from this  goroutine: querier.streamSeriesSet.waitForMergeSort

What we see for this query is that those go routines are starved for most of the times. E.g this sidecar fetch was waiting 500ms just to be able to pass it's data to merge sort:

This means sidecar itself gRPC service was waiting to send its messages too.
This happens for all stores. Essentially computation and slowest Stores causes additive latency which adds up.
And ONLY when we merge all, PromQL can start doing it's job due to https://github.com/prometheus/prometheus/issues/7326
Consequences:

Latency is more or less cumulative, despite fetching concurrently. We essentially could do more concurrency here, since we buffer all messages anyway.
We CANNOT tell which StoreAPI was the slowest (or its network) because of this dependency on merge sort. As you can see above trace shows 1.7s for this Store, but literally, it waited for 500+ms for Querier to take its data.

Note we see many of those "wait" times being significant in many messages writes:

Solution
The solution is kind of... simple. We have to buffer all and then merge all on top of it, then start eval PromQL as soon as possible. We have to fetch as fast as possible so StoreAPIs are free to perform further fetches and free memory. (sooner we do the job, the more we can do it!). Following diagram shows the general idea:

Looks good, I didn't think about this :+1: what do you mean by mmap on entry??

Yeah, this is still needed. If no one will pick this up soon then I might try implementing something.

Taking a fresh look (I might use this case in my Efficient Go book) -  let's see how far I will get, there might be opportunity to work together on this.
First - we need solid e2e benchmark for this

:+1: That would be great, we would be able to compare then. I'm working on implementing a tournament tree in Go. We could use a min-heap but it's not as efficient.

Yeah. Planning to open a PR next week, almost done. Decided to go with a heap based solution for now since that is easier to maintain and I doubt there would be much of an improvement with a selection/tournament tree because it needs auxiliary nodes.

PTAL fix: https://github.com/thanos-io/thanos/pull/5296

Done  with k-way I believe.


Bootstrap style for multi-select is broken

Hello.
I want to thanks all of the contributors for the multi-select feature! :+1:
I have a little problem with the bootstrap theme. I use bootswatch's themes in my application (Paper) and it seems that the multi-select doesn't support it much.
It's exactly the same markup as bootstrap and the ui-select dropdowns without multi-select work just fine.
On the screen you can see two "single" ui-select and the multi-select at the third position :

As you can see, the text input is cut and there is no caret icon. I noticed that ui-select set a fixed width to the text input but if I manually set width:100% to it, it's fine.
I'll be very grateful if anyone can show me a solution. ^^

I'm closing this as a legacy issue as its close to two years old now and doesn't have a repro sample.
If you believe its still relevant please reopen with a plunkr (or similar) against the latest version of ui-select (currently v0.15.0)


Regex's in a grammar don't work over multiple lines

I'm making a syntax highlighter for Common Lisp, and one of the things I've noticed is that a regex will not work over multiple lines.  Example:
I'm using (effectively) this regex:
(?<=\()
(def[\S]*)\s+
([\S]*)\s+
  (\(\s*
    ((
      [^()\s]+[\n\s]*|
      \([^()\s]+\s+[^()\s]+\)[\n\s]*
     )*)
  \))

and I get this:

The meh & hex should also be red.  Using the built-in oniguruma in dev-mode gives me this:

and even trying it out in something like regex101.com says this should work just fine.  Ao there must be something else that is going on...
The actual implementation is located here.
BTW, this effects the Racket highlighting also:

Thanks for any help!

This is a limitation in TextMate's grammar-matching spec, which is also present in atom/first-mate which Atom uses.  See atom/first-mate#57 for more information.

  Thanks!  Here's a happy penguin: :penguin:

Haha, just happened to be going through my unread notifications at the time :P.


Incremental commit specification & scenarios

What

[x] Collect all scenarios we care about in #199 What
[ ] Update / review transaction traces in miro
[ ] Update the specification with the design (from here, to be adapted to be analogous to what we have now with incremental decommits) - marked in red

1: Commutativity of Increments
For all:

( u_1, u_2 ) in UTXO
( h ) in Hydra-Head (open + empty)

Incrementing with ( u_1 ) and then ( u_2 ) should be the same as incrementing with ( u_2 ) and then ( u_1 ):
[ h: i(u_1) -> i(u_2) == h: i(u_2) -> i(u_1) ]
2: Commutativity of Decrements
For all:

( u_1, u_2 ) in UTXO
( h ) in Hydra-Head (open + with ( u_1 U u_2 ) locked)

Decrementing with ( u_1 ) and then ( u_2 ) should be the same as decrementing with ( u_2 ) and then ( u_1 ):
[ h: d(u_1) -> d(u_2) == h: d(u_2) -> d(u_1) ]
3: Idempotency of Increments
For all:

( u_1, u_2 ) in UTXO
( h ) in Hydra-Head (open + empty)

Incrementing multiple times with u1 and then u2, should result in the same head state as a single increment u_1 U u_2:
[ h: i(u_1) -> i(u_2) == h: i(u_1 U u_2) ]
4: Idempotency of Decrements
For all:

( u_1, u_2 ) in UTXO
( h ) in Hydra-Head (open + with ( u_1 U u_2 ) locked)

Decrementing multiple times with u1 and then u2, should result in the same head state as a single decrement (u_1 U u_2):
[ h: d(u_1) -> d(u_2) == h: d(u_1 U u_2) ]
5: No Change on Redundant Decrement
For all:

( u ) in UTXO
( h ) in Hydra-Head (open + empty)

Attempting to decrement with ( u ) when ( u ) is not locked should not change the head state:
[ h: d(u) == h ]
5: Inverse Operations of Increment and Decrement
For all:

( u ) in UTXO
( h ) in Hydra-Head (open + empty)

Performing an increment followed by a decrement with the same UTXO should result in the original head state:
[ h: i(u) -> d(u) == h ]
7: Inverse Operations of Idempotent Increment and Decrement
For all:

( u_1, u_2 ) in UTXO
( h ) in Hydra-Head (open + empty)

Performing an increment and a decrement with the union of two UTXOs,
should be the same as performing separate increments and decrements for each UTXO:
[ h: i(u_1 U u_2) -> d(u_1 U u_2) == h: i(u_1) -> i(u_2) -> d(u_1) -> d(u_2) ]

happy increment

Performing an increment with a UTXO ( u ) should result in a state where the head has more locked value than its initial state:

for all:

( u ) in UTXO
( h ) in Hydra-Head (open + empty)

h: i(u) > h

where ( h_1 > h_2 ) means that ( h_1 ) has a larger UTXO set or a greater amount of locked value than ( h_2 ).
happy decrement

Performing a decrement with a UTXO ( u ) should result in a state where the head has less locked value than its initial state:

for all:

( u ) in UTXO
( h ) in Hydra-Head (open + with u locked)

h: d(u) < h

where ( h_1 < h_2 ) means that ( h_1 ) has a smaller UTXO set or a lesser amount of locked value than ( h_2 ).

Definition
reject(u)

indicates that the head rejects the increment/decrement of UTXO ( u )

implies condition on h (=>)

A => B means that if action ( A ) is attempted first, then action ( B ) must follow as a consequence.

Propositon
8. Handling Race Condition in Incremental Commit
for all:

( u ) in UTXO
( h_1, h_2 ) in Hydra-Head (both open + empty)

Attempting to incrementally commit the same UTXO ( u ) on two different heads ( h_1 ) and ( h_2 ) should result in a race condition where only one head can successfully lock the UTXO, causing the other head to reject the increment:

h_1: i(u) -> h_2: i(u) == h_2: reject(u)

or
h_2: i(u) -> h_1: i(u) == h_1: reject(u)

indicating that the head rejects the increment of UTXO ( u ) because it is already committed in another head.

Reviewed scenarios in #199:

Duplicate "Cannot commit while another decommit is pending": this should probably read that we "cannot commit while another commit or decommit is pending"?

"Cannot decommit funds you don't own" and "Cannot decommit more than what we own in the Head" is redundant.

List looks good, but could be merged with the "Properties" above:

Updated #199 to reflect the comments above.

We also painted a full scenario of increment, decrement, then close:

Did a review of the #1511 changes and we discussed that:

There are actually 6 cases how the head can be closed now: Initial, Normal, UsedInc, UsedDec, UnusedInc and UnuseDec
Keeping commit/decommit variables separately in the off-chain state is likely more beneficial.

smaller diff to existing decommits
less hand-wavyness on case separation
potential of having commits/decommits be pending at the same time
at the cost of a require check on ReqSn that only one of the two is allowed to be snapshotted (for now)


What other species are good biofuel crops?

@phenolphtalein
How might you answer the following ...
Given the Miscanthus and Switchgrass yield data that @sidewallme has used in his analysis, plus any other data in the yields table, determine:
Are there species that haven't been grown in agronomic trials (i.e. we don't have yield data in betydb.org/yields.csv) that might be good candidates for high yielding crops?
Notes:

in the plants table (betydb.org/species.csv) is full of categorical variables - for all species in plants.usda.gov
there are also many sparse rows that we have created, mostly for poplar and willow hybrids (bred across species) and non-US plants.

@phenolphtalein @dlebauer
It is good to look into other species but this is more of a method study ( you are comparing three different  modeling approach). Perhaps it will be best to remain focused on methods using just one species (Miscanthus) for this study. If we conclude that one of the three method is best then we can do a second study including multiple species and the best method.


Make carousel swipeable?

I saw in a closed comment thread where you suggested using touchswipe with jcarousel. I tried that, but still can't get it to swipe.
I have both scripts called in the head, and tried what you suggested in the body, as well as some other things. My inner div id="carousel" and class="jcarousel", and this is what I have for the function in the body:
<script>
$(document).ready(function() {
	var carousel.jcarousel();
	carousel
    .touchwipe({
        wipeLeft: function() {
            carousel.jcarousel('next');
        },
        wipeRight: function() {
            carousel.jcarousel('prev');
        }
    });
</script>

I also tried something else I found:
<script>
$(document).ready(function() {
	$('#carousel').cycle({
		timeout: 0,
		fx: 'scrollHorz',
		next: '#next',
		prev: '#prev'
	});

	$("#carousel").touchwipe({
 		wipeLeft: function() {
 	 		$("#carousel").cycle("next");
 		},
 		wipeRight: function() {
 	 		$("#carousel").cycle("prev");
 		}
	});
});
</script>

...but nothing's working. Please help. Thanks!

Please setup a reprocuible test-case with everything you have so far.

How do I set that up? The only thing I didn't include in the above is the trigger code (or whatever you call it) in the body. I tried several different things, as I tried to include above, but looking at it now, it seems that didn't post. I don't see how to include code on this forum, so I'll attach this screenshot of it:

You're mixing in some code from another plugin (jQuery Cycle). Have you tride this: https://alexbudeanu.wordpress.com/2012/11/11/adding-swipe-to-jcarousel/
For reproducibe test-cases, use jsfiddle or codepen.

I just tried that, still not working. I have the carousel inside a wrapping div, like so:

‹
›

... would that cause a problem?

Can you please setup a reproducibe test-cases on jsfiddle or codepen.


Aarch64 Compatible Jobber APK

Hi Team,
I am not able to find apk for aarch64 in its release. Is there any plan to release aarch64 compatible jobber apk.

Ping @dshearer could you please share your thoughts on this.

Let me look into it this weekend.

On Mar 24, 2020, at 11:55 PM, odidev<EMAIL_ADDRESS>wrote:

Hi Team,
I am not able to find apk for aarch64 in its release. Is there any plan to release aarch64 compatible jobber apk.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks @dshearer Please let me know if you have any suggestions.

@dshearer did you get the time to look at the issue?

Ping @dshearer could you please share your thoughts on this.

I’m trying to finish up making a Homebrew package for Jobber.  I’ll get to your task next.

On Apr 22, 2020, at 7:15 AM, odidev<EMAIL_ADDRESS>wrote:
Ping @dshearer https://github.com/dshearer could you please share your thoughts on this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/dshearer/jobber/issues/273#issuecomment-617805762, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABRCWRHLZELEBTVLZNTQVALRN33YRANCNFSM4LTHIWBQ.

Hi @dshearer, sure thanks for the response.
Can we add support for arm64 apk build in Travis-Ci so that we could obtain the apk binary from the Travis or are there any other methods to generate the apk binary for arm64?

Ping @dshearer could you please share your thoughts on this.

@odidev can you provide a PR to do an AArch64 APK build using Travis-CI?

I’ll look into this this weekend. I’d like to move toward using GitHub to do the builds rather than Travis or Circle.

On May 19, 2020, at 9:28 AM, Richard Henwood<EMAIL_ADDRESS>wrote:

@odidev can you provide a PR to do an AArch64 APK build using Travis-CI?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Looks like GitHub Actions does not support ARM (unless we use self-hosted runners). As I said, I want to stick with GitHub Actions from now on.  Sorry.

@dshearer,
As per our previous conversation I had tried to build this package for ARM64 in Github Action using qemu and was able to build and release the binaries for arm64 by implementing these changes.
ARM64 Binary: https://github.com/odidev/jobber/releases/download/1.4.4/jobber-1.4.4-arm64-r0.apk
Changes required: https://github.com/odidev/jobber/commit/ede10c7efcd8295150dce27f1fda8d9aa6b606d7
Do you have any plans for releasing an ARM64 Binaries?
May I know how the amd64 binaries are getting released?
If interested, I will raise a PR.


@conda-forge-admin add user @colinbrislawn

I'm working on osx-arm64 builds and would like push permissions.
Thank you!

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @colinbrislawn in conda-forge/r-xml2-feedstock#22.


cc2538: fix radio driver issue which would impact device acting as SED

The typo in otPlatRadioSleep() is the root cause for  issue #252, explained in #252
Hi @jwhui , please have a review.

Good catch!  Just one minor comment inline.

LGTM 👍
Fixes #252.


Market listeners tests

Some further listener tests and fix an issue where BroadcastListenerImpl without knowledge of the following node would try to use an undeclared variable.

Coverage increased (+0.4%) to 52.402% when pulling 4bd9fc8c86614d1ab6cacccfeb590be12b70acbc on tomgalloway:market_listeners_tests into da0c261c5b303c558075cd4666d25650d45a7509 on OpenBazaar:master.

Please take a look @Cpacia this has been here for a while

Thanks!


wrong MSDs in msd_translate.py

There's an error in msd_translate.py (<root_directory>\Cordex\cordex-master\cordex-master\cordex\readers).
The values "Ne", "Nh" and "Na" in lines 1920, 1921, 1922 should be corrected to "Xe", "Xh" and "Xa" respectively, as per the MULTEXT-East MSD table.

@cyplas


possibility to create relations with itself

this used to be a dangerous feature that made the database crash. currently when i create a new relation it offers me the possibility to link it to itself

closed with https://github.com/arthur-schnitzler/pmb-service/commit/03859514eaed28e8ad621bd5c0a30b0a2c940f2a


Add API to check OSX's Dark theme

Implements #4300

Alright, I renamed the event to be more generic and I simplified the isDarkModeEnabled check to be more legible.

:+1:

Nice!

I hope this works awesomely great with f.lux automatically setting the theme to dark mode at night (its an option :smile: )

BTW, @phamdaniel do you think you can make it able to change between light themes and dark themes when the Dark mode is on or off?
Example: Material Syntax Light when Dark Mode is disabled, Material Syntax Dark when Dark Mode is enabled.
Thanks a million!

Yup, this should play nice with f.lux
As for the second question, I'm guessing that your talking about Atom? It would definitely be possible as all the pieces are in place, though I personally wouldn't know how to implement it in that particular case.

any plans to extend this cross platform (i.e. Linux), or are you counting on someone (like me) to PR that?

@forivall is there a functional dark mode in Linux like in OS X?

Yup, In Gnome, there is a dark mode that you one can enable via tweak-tool. And with the terminology just being "platform theme changed", it could make sense for it to be any kind of theming change. Related: https://atom.io/packages/gtk-dark-theme

What about this for Windows? There's an option in windows 10, but it doesn't change much outside Windows store type apps. That said, the taskbar colour can change and setting icons can be problematic if they are too dark/light


Add specification for results

Closes https://github.com/mlcommons/mobile_app_open/issues/247

let's try to finish reviewing this by next meeting

Errrr.... looks like I'm not a reviewer. @AhmedTElthakeb, could we go over this?


[bug]: explorerExcludedWalletIds excludes all

Description
using explorerExcludedWalletIdsusing initialization excludes all wallets including explorerRecommendedWalletIds.
Experiencing this recently, before it was good, showed only explorerRecommendedWalletIds in both main modal and view all view.
WalletConnect Modal SDK version
1.0.0-rc.7
Output of npx react-native info
im using expo
Expo Version (if applies)
48.0.18
Steps to reproduce
<WalletConnectModal
            themeMode="dark"
            projectId={WC_PROJECT_ID}
            explorerExcludedWalletIds="ALL"
            providerMetadata={providerMetadata}
            explorerRecommendedWalletIds={explorerRecommendedWalletIds}
          />

Snack, code example, screenshot, or link to a repository

If I removed explorerExcludedWalletIds works, but i dont want ALL wallets in view all modal.
<WalletConnectModal
            themeMode="dark"
            projectId={WC_PROJECT_ID}
            // explorerExcludedWalletIds="ALL"
            providerMetadata={providerMetadata}
            explorerRecommendedWalletIds={explorerRecommendedWalletIds}
          />

@sasicodes thanks for reaching out!
You are right, I broke some cases in the latest release 🥲
I already created a PR to solve that, once it's merged i'll release a canary version for you to test it 💪

@sasicodes<EMAIL_ADDRESS>released 🎉  Can you check if it works with your case?

@sasicodes<EMAIL_ADDRESS>released 🎉 Can you check if it works with your case?

yes, now explorerExcludedWalletIds="ALL" is working fine. Only defined wallet are shown 👍🏻
Thanks.


Fatal Error: PubSubClient.h: No such file or directory

Hey there!
Please help me with the problem, did I do something wrong? How can I solve the problem?
Thanks in advance
Pete
Arduino Error:
C:\Users*****\Documents\McLighting-master\McLighting-master\Arduino\McLighting\McLighting.ino:29:28: fatal error: PubSubClient.h: No such file or directory

Hi Pete,
please have a look at the instructions here:
https://github.com/toblum/McLighting/wiki/Software-installation#used-libraries
Regards
Tobias

Oh, thx
I have overlooked it :D
Thanks again
Pete

No problem!


how to add images in the conversation?

hi Team,
firstly thanks very much for your work it's very nice
basically Im not a dev and I can use your script without difficulty
just one thing is missing for me. the robot is not able to send message with images.
did I miss something or it s not possible?
thanks
Louis

hi I fixed it with this method

in src= remove " and replace by  '

Hi Louis,
I didn't actively add support for images but it can work if you do like you described. I may add real support to this in the future.


github crashed

got a message saying atom has crashed and
Please report this issue to https://github.com/atom/atom.
i tried to start atom from the terminal and i had recently installed zsh shell and was trying to open the .zshrc file to change the theme of the terminal. how do i fix this?? i am using ubuntu linux and the version of atom is 1.3.3

@dzknj Please try updating Atom to the latest version, currently 1.5.3.  If that doesn't help, try launching Atom in safe mode: atom --safe.  And if that doesn't work, please comment here and I'll reopen this issue.  Thanks!


Intergrate tesseract changes

Description
Implement the modifications associated with MOI Protocol version 0.6.0.
Note: This document is a preliminary issue.
Changes

[x] #44

Interaction, Receipt and Tesseract schema changed. Click here to know about the changes.
The fields state_hashes and context_hashes have been consolidated into a singular field named hashes.

[x] moi.InteractionByTesseract

The address field is no longer obligatory. Utilization of tesseract_hash and ix_index for interaction retrieval.

[x] moi.GetTesseract

Modification enables fetching Tesseract using tesseract_hash without the necessity of providing an address.

closed in #45


Update Desktop FAQ, remove info on Service accounts

Update Desktop FAQ, remove info on Service accounts

do we need a redirect for the URL?

Good point. Added a redirect :)


Company logo should not be there on Footer and the footer should look different

Describe the bug
We have a  requirement, that we don't want a company logo in the footer.
Also we have a requirement of footer with a different look. Attached below.

Please tell, if this is possible. If yes, by when can we expect the changes.

We are going to allow removing the default logo by explicitly passing the logoSrc as null.
Not sure what you mean by "a different look". Please create a different issue for that, and elaborate a bit more on why or when do we want this new look.

@ppurumala This is not the right place for this issue. Please create a new issue in our Design Guidelines explaining why this is required https://github.com/dxc-technology/halstack-style-guide/issues. I am closing this one now. Thanks a lot again.


[deprecated] Removed User.organizations_pk #197

Removed organizations_pk method from AbstractUser class
of openwisp_users.base.models.py.
Reason - User.organizations_pk is deprecated in favor of
User.organizations_dict and will be removed in a
future version
Fixes #197

@codesankalp See travis builds are failed too, you should run tests locally first before pushing your code

Coverage decreased (-0.01%) to 98.458% when pulling 798d59868969482d7b07468348eec6e36d2871d4 on codesankalp:issue197 into 2bc6a51f81bc3bea5a41d0909dfb80aec2aa49c2 on openwisp:master.

Coverage decreased (-0.01%) to 98.458% when pulling 798d59868969482d7b07468348eec6e36d2871d4 on codesankalp:issue197 into 2bc6a51f81bc3bea5a41d0909dfb80aec2aa49c2 on openwisp:master.

@devkapilbansal @nemesisdesign
https://github.com/openwisp/openwisp-users/blob/2bc6a51f81bc3bea5a41d0909dfb80aec2aa49c2/openwisp_users/tests/test_models.py#L61
I think user creation with the name organizations_pk is odd.
Why don't we change this something to test_user?

Thanks, @Purhan for correcting my mistake :bow:

@devkapilbansal making a new issue for that will be good. What's your view?


Added missing ServiceAccount, ClusterRole and ClusterRoleBinding to DNS Horizontal Autoscaler.

Added missing ServiceAccount, ClusterRole, and ClusterRoleBinding.
Without these components, the deployment fails. It confuses new users as the document is not complete.
By updating this example code snippet, users can directly use the YAML to deploy DNS Horizontal Autoscaler.

https://github.com/kubernetes/website/issues/15280
https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns-horizontal-autoscaler/dns-horizontal-autoscaler.yaml

I have signed the  Contributor License Agreement (CLA) now.

Thanks @sanusatyadarshi .
/approve


Readme: Add intro to chapter Literals

I was trying to understand what zod literals are. The docs could benefit from an intro sentence. This is a suggestion for such an intro. However, this can probably be more specific. For example, which differences are there to TS literal types? Eg. with Symbol and BigInt (which I both know nothing about…).

Great work


Failure instance: Traceback: <class 'KeyError'>: 'summary.config.numCpu'

Started hitting this in one of my environments:
Dec 27 15:01:58 prometheus-01 docker-vmware-exporter[6744]: [2018-12-27 15:01:58.129410+00:00] Start collecting metrics from <vcenter>
Dec 27 15:01:58 prometheus-01 docker-vmware-exporter[6744]: [2018-12-27 15:01:58.213902+00:00] Starting inventory collection
Dec 27 15:01:58 prometheus-01 docker-vmware-exporter[6744]: [2018-12-27 15:01:58.832281+00:00] Finished inventory collection
Dec 27 15:01:58 prometheus-01 docker-vmware-exporter[6744]: [2018-12-27 15:01:58.832866+00:00] Starting datastore metrics collection
Dec 27 15:01:58 prometheus-01 docker-vmware-exporter[6744]: [2018-12-27 15:01:58.833736+00:00] Starting host metrics collection
Dec 27 15:01:58 prometheus-01 docker-vmware-exporter[6744]: [2018-12-27 15:01:58.834292+00:00] Starting VM metrics collection
Dec 27 15:01:58 prometheus-01 docker-vmware-exporter[6744]: [2018-12-27 15:01:58.875157+00:00] Finished datastore metrics collection
Dec 27 15:01:58 prometheus-01 docker-vmware-exporter[6744]: [2018-12-27 15:01:58.884837+00:00] Finished host metrics collection
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: [2018-12-27 15:01:59.011146+00:00] [Failure instance: Traceback: <class 'KeyError'>: 'summary.config.numCpu'
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: /usr/local/lib/python3.6/site-packages/twisted/internet/base.py:1276:mainLoop
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: /usr/local/lib/python3.6/site-packages/twisted/internet/base.py:902:runUntilCurrent
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: /usr/local/lib/python3.6/site-packages/twisted/internet/defer.py:460:callback
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: /usr/local/lib/python3.6/site-packages/twisted/internet/defer.py:568:_startRunCallbacks
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: --- <exception caught here> ---
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: /usr/local/lib/python3.6/site-packages/twisted/internet/defer.py:654:_runCallbacks
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: /usr/local/lib/python3.6/site-packages/vmware_exporter/vmware_exporter.py:687:generate_latest_metrics
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: /usr/local/lib/python3.6/site-packages/prometheus_client/exposition.py:63:generate_latest
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: /usr/local/lib/python3.6/site-packages/prometheus_client/core.py:97:collect
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: /usr/local/lib/python3.6/site-packages/vmware_exporter/vmware_exporter.py:216:collect
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: /usr/local/lib/python3.6/site-packages/vmware_exporter/vmware_exporter.py:442:_vmware_get_vms
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: ]
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: Traceback (most recent call last):
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: File "/usr/local/lib/python3.6/site-packages/twisted/internet/base.py", line 1276, in mainLoop
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: self.runUntilCurrent()
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: File "/usr/local/lib/python3.6/site-packages/twisted/internet/base.py", line 902, in runUntilCurrent
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: call.func(*call.args, **call.kw)
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: File "/usr/local/lib/python3.6/site-packages/twisted/internet/defer.py", line 460, in callback
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: self._startRunCallbacks(result)
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: File "/usr/local/lib/python3.6/site-packages/twisted/internet/defer.py", line 568, in _startRunCallbacks
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: self._runCallbacks()
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: --- <exception caught here> ---
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: File "/usr/local/lib/python3.6/site-packages/twisted/internet/defer.py", line 654, in _runCallbacks
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: current.result = callback(current.result, *args, **kw)
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: File "/usr/local/lib/python3.6/site-packages/vmware_exporter/vmware_exporter.py", line 687, in generate_latest_metrics
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: output = generate_latest(registry)
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: File "/usr/local/lib/python3.6/site-packages/prometheus_client/exposition.py", line 63, in generate_latest
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: for metric in registry.collect():
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: File "/usr/local/lib/python3.6/site-packages/prometheus_client/core.py", line 97, in collect
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: for metric in collector.collect():
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: File "/usr/local/lib/python3.6/site-packages/vmware_exporter/vmware_exporter.py", line 216, in collect
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: virtual_machines = self._vmware_get_vms(content, metrics, host_inventory)
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: File "/usr/local/lib/python3.6/site-packages/vmware_exporter/vmware_exporter.py", line 442, in _vmware_get_vms
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: metrics['vmware_vm_num_cpu'].add_metric(labels, row['summary.config.numCpu'])
Dec 27 15:01:59 prometheus-01 docker-vmware-exporter[6744]: builtins.KeyError: 'summary.config.numCpu'

There were no changes in the environment, we are pretty much in a freeze during the holidays, so no new VMs/etc...

I sent more or less this exact same thing in an email but it didn't go through.

I've modified my DEBUG to this as a kind of band-aid, but we should consider what other checks are needed:
diff --git a/vmware_exporter/vmware_exporter.py b/vmware_exporter/vmware_exporter.py
index f5a38b2..e59ad92 100755
--- a/vmware_exporter/vmware_exporter.py
+++ b/vmware_exporter/vmware_exporter.py
@@ -430,6 +430,13 @@ class VmwareCollector():
             ]

             if self.collect_only['vms'] is True:
+                # DEBUG
+                if 'summary.config.numCpu' not in row:
+                    log('VM ID: {0}, Name: {1} is missing Number of CPUs, Power state is: {2}, skipping this VM'.format(
+                        moid, row['name'], row['runtime.powerState'])
+                        )
+                    continue
+
                 vm_power_state = 1 if row['runtime.powerState'] == 'poweredOn' else 0
                 metrics['vmware_vm_power_state'].add_metric(labels, vm_power_state)

Along similar lines - There’s a check in my outstanding PR to only do performance metrics for vms that are on.

I hope to have some time to review your pending PR this year, if not, next year 😄

I'll be reviewing it shortly. So far my initial pass over looks gud!

@dannyk81 are you happy that v0.4.2 fixes this for your env?

@jc2k I don't have a chance to validate this now, but considering the safeguards we've added I don't think we'll hit this again.
Thanks! closing this...


P0209R2 make_from_tuple: apply for construction

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0209r2.pdf
__cpp_lib_make_from_tuple : 201606L

完了


filter subdomains on linode side

Otherwise for zones with a "production level" of subdomains it will take longer than 30 seconds just to iterate (it may also fail due to too many records for a single page)

Thanks! What's a "production level" of subdomains out of curiosity? like 1,000? 10,000? or 1,000,000?
I'm gonna try it out later - but since this is an "unofficial" fork, and my Go skills are very minimal, i highly suggest making the same PR in the https://github.com/slicen/cert-manager-webhook-linode original repo too - as that one is more likely to be maintained in future.

Not sure, linode doesnt provide an exact count. But it's in the ballpark of ~10,000 records. 550 pages in the linode ui.
external-dns creates one txt record per pod per node by default.


Velocity packet bug

The handshake packet write wrong velocity informations
    public HandshakePacket(BinaryReader reader) {         this(reader.readVarInt(), reader.readSizedString(BungeeCordProxy.isEnabled() ? Short.MAX_VALUE : 255),                 reader.readUnsignedShort(), reader.readVarInt());     }

This may have been fixed by e5d0a43ba42c7023a93e8e33356909e614783ac7, can someone confirm this?


Fix support for 'puppet generate types'

This works around SERVER-94 issues
Closes #40

Coverage remained the same at 97.087% when pulling 2b2575915eab2c8238315be93f7d7a2e7c794d0e on trevor-vaughan:fix-puppet-generate-types into b6268b38b6931ecb9f5a641d42f7cd9bbac530cf on hercules-team:master.

Coverage remained the same at 97.087% when pulling 2b2575915eab2c8238315be93f7d7a2e7c794d0e on trevor-vaughan:fix-puppet-generate-types into b6268b38b6931ecb9f5a641d42f7cd9bbac530cf on hercules-team:master.

Coverage remained the same at 97.087% when pulling 2b2575915eab2c8238315be93f7d7a2e7c794d0e on trevor-vaughan:fix-puppet-generate-types into b6268b38b6931ecb9f5a641d42f7cd9bbac530cf on hercules-team:master.

Coverage remained the same at 97.087% when pulling 2b2575915eab2c8238315be93f7d7a2e7c794d0e on trevor-vaughan:fix-puppet-generate-types into b6268b38b6931ecb9f5a641d42f7cd9bbac530cf on hercules-team:master.


Normalizes headings and direct children

Changes
Normalizes the margin of direct children
The last element within an alert should have it's bottom margin removed. This is to ensure that the alert has even padding/spacing. This is the desired effect for the majority of use cases.
Heading colours match the alert state
h1-h6 colours have been added to the default alert as well as the various alert states. This is the desired behaviour for the majority of use cases. These styles have fairly low specificity, which makes it easier to override if necessary.
These enhancements were suggested by @nfrancis <3
Resolves: https://github.com/helpscout/seed-alert/issues/1

@ItsJonQ thanks for doing this!  Seems you could use that class on anything, don't have to limit normalization to headings only. I'm sure you had a good reason for it, just curious.

@nfrancis Oh! Sorry about that. I forgot about that .c-alert__text feature! Will add that as an issue for the next update.


Tweaked nginx config to allow robots to use api.

The syntax is a bear because nginx doesn't support complex conditionals, but this seems to work.

Anyone want to have a look at this?  It is already installed on the production server and it works.  I temporarily blocked curl to test it, and sure enough curl was allowed to use the api but nothing else.

coverage: 93.67%. remained the same when pulling fe6eb5963b2f9ae6390fc4b3529b773694b2eefd on fix-nginx-con into 59335258e12e0ee3c4376576450ce61a8f8b9811 on main.

@pellaea: Thanks for doing this.
I think you should merge it. (I don't want to take the time to figure out the syntax.)


Forward 1.2.10 and 1.2.11

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.

What
Forward 1.2.10 and 1.2.11 changes
Why
[TODO: Why this change is being made. Include any context required to understand the why.]
Known limitations
[TODO or N/A]

Reference Server Preview is available here:https://anchor-ref-pr812.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr812.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr812.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr812.previews.kube001.services.stellar-ops.com/

Something went wrong with PR preview build please check

Reference Server Preview is available here:https://anchor-ref-pr812.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr812.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr812.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr812.previews.kube001.services.stellar-ops.com/


Build failure: python311Packages.extruct

Steps To Reproduce
Steps to reproduce the behavior:

build python311Packages.extruct on master (e5bc1cb431307c0a3943615151aeff0b9cc246c3)

Build log
Executing pythonImportsCheckPhase
Check whether the following modules can be imported: extruct
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "<string>", line 1, in <lambda>
  File "/nix/store/hyppxdhgqx7nbg394j97yhmi6vizl074-python3-3.11.9/lib/python3.11/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1147, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/nix/store/ahx97198xk2wjd4dbxax1l6yb22iiv3p-python3.11-extruct-0.16.0/lib/python3.11/site-packages/extruct/__init__.py", line 1, in <module>
    from ._extruct import SYNTAXES, extract
  File "/nix/store/ahx97198xk2wjd4dbxax1l6yb22iiv3p-python3.11-extruct-0.16.0/lib/python3.11/site-packages/extruct/_extruct.py", line 9, in <module>
    from extruct.dublincore import DublinCoreExtractor
  File "/nix/store/ahx97198xk2wjd4dbxax1l6yb22iiv3p-python3.11-extruct-0.16.0/lib/python3.11/site-packages/extruct/dublincore.py", line 6, in <module>
    from extruct.utils import parse_html
  File "/nix/store/ahx97198xk2wjd4dbxax1l6yb22iiv3p-python3.11-extruct-0.16.0/lib/python3.11/site-packages/extruct/utils.py", line 5, in <module>
    from extruct.xmldom import XmlDomHTMLParser
  File "/nix/store/ahx97198xk2wjd4dbxax1l6yb22iiv3p-python3.11-extruct-0.16.0/lib/python3.11/site-packages/extruct/xmldom.py", line 9, in <module>
    from lxml.etree import (
ImportError: cannot import name '_ElementStringResult' from 'lxml.etree' (/nix/store/0i7w9qrw41ih3sa45kpaihldn1d6fj9n-python3.11-lxml-5.2.2/lib/python3.11/site-packages/lxml/etree.cpython-311-x86_64-linux-gnu.so)

Additional context
Notify maintainers
@ambroisie

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

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

oops, misread the log, should be fixed by #327291


Add ability to show links in detail map

Show links between items plotted on the map.  When point is clicked, find related items and display them on the map with lines between the points.

Submitted PR: https://github.com/daveegrant/ml-ol-maps-ng/pull/3


OpenSource strategy

AlephAlpha has repeatedly emphasised in various publications and statements that it is committed to OpenSource. Looking at the activity in this repository and the available trained weights, the reality is different.
Apart from positive marketing, what role does OpenSource play at AlephAlpha? The French company Mistral has shown how important the OpenSource idea is, and has set international standards with its released models.
All I see are academic advances that are used as arguments for further funding rounds. The model code in this repository is two years out of date, as are the available checkpoints. There are no publications on Huggingface nor any other engagement in the community of LLM's tools. Once again it seems to be a special German way of compartmentalisation, combined with the belief that enough money will take care of it.
So what is AlpehAlpha's actual strategy regarding OpenSource?

They will not

After two years, signs of life w.r.t. open source:

Aleph-Alpha/Pharia-1-LLM-7B-control see here
Aleph-Alpha/Pharia-1-LLM-7B-control-aligned see here

@stefan-it  do you work for Aleph-Alpha? 😆


Measures back-pressure on the job queue, and exerts control strategies at Block Generation

Follows and supersedes #11, #9.

Wrong base


URL click not working on IE9 / IE10

We have this issue with our project and it is repeatable with the examples on the documentation page.
http://bootstrap-growl.remabledesigns.com/#growl-documentation
On the "passing a URL" example.
click the "create growl" button.
In IE9 / IE10 it works if you don't click on the text.  Nothing happens if you click on the text.
In IE11 and latest Chrome and Firefox, clicking on the text also loads the url.

This is a problem with IE9/10 not liking empty absolute anchor tags. The best way I found to fix this is to add an invisible image that stretches over the anchor tag. This is included in version 3.0.0 which will be released this weekend.

Thanks for the swift reply.  In the meantime, I have just made the message I'm displaying an anchor message and it now works.
I'll revisit it, once 3.0.0 is released.

Version 3.0.0 has been released and this should be fixed. If it isn't please re-open this case. It seemed to be resolved in my testing though.


Fix not supporting cors when options not defined

Purpose
$subject

Codecov Report
Patch coverage has no change and project coverage change: +0.78 :tada:

Comparison is base (1922539) 32.76% compared to head (3c9f688) 33.55%.

:exclamation: Current head 3c9f688 differs from pull request most recent head 47f59ea. Consider uploading reports for the commit 47f59ea to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1236      +/-   ##
==========================================
+ Coverage   32.76%   33.55%   +0.78%
==========================================
  Files         374       88     -286
  Lines       43924    12726   -31198
  Branches    14156     1791   -12365
==========================================
- Hits        14392     4270   -10122
+ Misses      29276     8327   -20949
+ Partials      256      129     -127

Flag
Coverage Δ

adapter
24.75% <ø> (-0.02%)
:arrow_down:

admin-domain-service
54.61% <ø> (ø)

backoffice-domain-service
57.51% <ø> (ø)

devportal-domain-service
?

idp-domain-service
80.10% <ø> (ø)

runtime-domain-service
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 287 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Task to prune uploaded snapshots

When also publishing nighly snapshots to bintray (using a version convention such as https://github.com/dwijnand/sbt-dynver), it would be nice to add a task that gets the versions from bintray (https://bintray.com/docs/api/#_get_package) and deletes (https://bintray.com/docs/api/#url_delete_version) all old snapshots except but a configurable number of most-recent ones?
For example if there's 1.2.3-1, 1.2.3-2, 1.2.3-3 and 1.2.4-1 and we keep 2, we should keep 1.2.3-3 and 1.2.4-1

I just successfully used bintrayUnpublish to clean up snapshots:
; set version in ThisBuild := "0.19+10-4995b08b" ; bintrayUnpublish
So combined with listing versions known by Bintray this could become usable, I guess.


Error: EISDIR: illegal operation on a directory, read

Getting an Error: EISDIR: illegal operation on a directory, read when running this from the command line:
uncss schedule-compiled.css > schedule-uncss.css
Any idea what's causing it or how to debug it?

Sounds like schedule-compiled.css is a directory.


Keeping derived answers up to date from data portals (such as data.gov.uk)

So far certificates that have been automatically awarded have been based off of batch imports run manually and have not been updated with changed answers or added to as new datasets are added to data.gov.uk
We have a few options to choose from in how we approach this

The ODI runs a regular collection process as part of certificates site.
DGU runs a regular batch process that uploads references to changed or added datasets.
DGU sends a message (webhook/callback etc) when a dataset is updated to certificates triggering an update of that certificate.

The downside of the background processes like in options 1 and 2 is that it's kept away from the publisher's view and as @sumikasan has said, the goal is to get publishers aware of good practices in data publishing. So having the certificate process be more visible upon submission may be a nice to have.
A benefit to option 1 is that it is a central process responsible for all updates that we can monitor and improve but it could be a waste of resources and a burden on portals if it has to make polling requests all the time. Once it is checking many portals it may take quite a lot of time to do the rounds also.
Option 2 has the benefit that data.gov.uk can only send what has changed at intervals that suit them but without monitoring the process could stop and we wouldn't necessarily know.
Option 3 might be architecturally more complex since it involves messages between both web servers.
A possible design would be:

publisher submits dataset
DGU sends a request to ODC giving the url of the dataset, ODC responds back with a job ID.
DGU mentions that a certificate is being issued or re-checked to the publisher
ODC fetches the changed data and creates or updates a certificate.
ODC sends a message back to DGU with the job ID with the outcome and certificate url or data so that DGU can update any references.

I like a combination of options 1 and 3: in the initial phase of integration with a portal we will need to poll (eg on a daily basis) for updates, but when the portal is properly integrated then they can ping us to perform updates for particular certificates, giving a better experience for their users. The integration is fairly lightweight for the portal, because they just have to do the pinging rather than working out exactly what to send via the API to update the certificate.
In a daily process that we run over supported portals we could check whether there have been pings from that portal during the last 24 hours, and not poll it if there have been. This would get around the potential problem of the portal removing the integration from their side and us not knowing.

@sumikasan if we add reporting to this feature, such as how many certificates failed for certain questions then we can use it as the sales/participation tool you mentioned.
So if we set it up to import everything from a portal or source it could certify everything but leave them in draft state.

Report how many reach each level
Report which questions we are having trouble answering

ability to provide default answers
instructions on how to add that to portal

Then the ability to re-run the import to catch updates.
Rinse and repeat
A button that publishes all of them at once.

@pkqk you've got my vote on that suggestion Adam

I have now split this story up - reporting story is here:
https://github.com/theodi/open-data-certificate/issues/1119

@pezholio - this is what we need to work on after you close the #1178.

:+1:


validators being called but failing to answer

It's not easy to pinpoint the exact source but I was checking my kube-controller-manager for a differnent issue and found a lot of errors regarding the kubedb validators.
I've pulled the following lines from the logs..
It appears as if the validator service is not available and therefore several other services which depend on it return errors. It's also telling me it gets timeouts which could point to a more serious issue
1 resource_quota_controller.go:408] unable to retrieve the complete list of server APIs: validators.ops.kubedb.com/v1alpha1: the server is currently unable to handle the request
I1201 09:14:49.345467       1 request.go:645] Throttling request took 1.043617374s, request: GET:https://<IP_ADDRESS>:6443/apis/ops.kubedb.com/v1alpha1?timeout=32s
I1201 09:14:50.695164       1 request.go:645] Throttling request took 1.04747659s, request: GET:https://<IP_ADDRESS>:6443/apis/admission.stash.appscode.com/v1beta1?timeout=32s
I1201 09:14:51.695127       1 request.go:645] Throttling request took 2.047369505s, request: GET:https://<IP_ADDRESS>:6443/apis/rbac.authorization.k8s.io/v1beta1?timeout=32s
W1201 09:14:52.297747       1 garbagecollector.go:642] failed to discover some groups: map[validators.ops.kubedb.com/v1alpha1:the server is currently unable to handle the request]

error: unable to retrieve the complete list of server APIs: validators.ops.kubedb.com/v1alpha1: the server is currently unable to handle the request

garbagecollector.go:642] failed to discover some groups: map[validators.ops.kubedb.com/v1alpha1:the server is currently unable to handle the request]

resource_quota_controller.go:408] unable to retrieve the complete list of server APIs: validators.ops.kubedb.com/v1alpha1: the server is currently unable to handle the request

 memcache.go:196] couldn't get resource list for validators.ops.kubedb.com/v1alpha1: the server is currently unable to handle the request

It looks a bit like: https://github.com/kubedb/project/issues/733

turns out kubedb-enterprise pod was crashlooping.
I still see:
1 request.go:645] Throttling request took 1.043454435s, request: GET:https://<IP_ADDRESS>:6443/apis/stash.appscode.com/v1beta1?timeout=32s
I1201 09:43:01.273213       1 request.go:645] Throttling request took 1.042295304s, request: GET:https://<IP_ADDRESS>:6443/apis/ops.kubedb.com/v1alpha1?timeout=32s
I1201 09:43:17.263099       1 request.go:645] Throttling request took 1.043780188s, request: GET:https://<IP_ADDRESS>:6443/apis/ops.kubedb.com/v1alpha1?timeout=32s
I1201 09:43:32.527017       1 request.go:645] Throttling request took 1.044986203s, request: GET:https://<IP_ADDRESS>:6443/apis/validators.kubedb.com/v1alpha1?timeout=32s

closing