Is there a way to run Singularity tasks as non root and still have access to sandbox

I'm wondering if there's a knob somewhere to make the sandbox accessible to the uid or globally (obviously the last is worse)

Basically the question is how to set a mode/user for the sandbox?

MESOS-8332 was the update that changed the sandbox permissions. As far as I know there is not a mesos input or flag to change the sandbox permissions per task. We do a little munging in the SingularityExecutor depending on how the users are setup (with our executor can either run the whole thing as a user, or run as root and have executor switch user, we munge sandbox permissions for the second of those), because we ran into a similar problem after that upgrade.
What version are you on and are you using the default mesos executor or the Singularity one?

I believe we are on singularity .23 though it might be .22. We use the default mesos executor . I’m gleaning you are saying yes there might be a way but only on singularity executor

hmm, the default mesos slave + executor should already be setting the permissions correctly for a non-root user to utilize the sandbox. What mesos version as well?

I’ll try to check tomorrow thanks

Wasn't able to get this working, but we no longer need this so clearing your board.


Prevent compiler from casting object to value

Not strictly a bug, but would it be feasible in Boost.JSON to explicitly disallow automatic casting from boost::json::object to boost::json::value?  At the moment, even though boost::json::object is not AFAICT a subclass of boost::json::value, the compiler happily allows it (eg you can pass a reference to a boost::json::object as a parameter to a function that takes a reference to a boost::json::value) and the code compiles without warning but you get garbage results at runtime.

(I'm using Boost version 1.79 on Ubuntu Linux with GCC 11.2 compiler BTW.)

Can you provide an example of code that leads to garbage at runtime? The conversion from object to value should work properly.

Hi,
I've tried to extract the relevant bits from my application in the code below.
class MyClass {
public:

   MyClass(boost::json::value const & recordData) : recordData{recordData} {return; }
...
   void load() {
      std::cout << "Loading record containing" << this->recordData.as_object().size() << "elements";
...
   }
...
protected:
   boost::json::value const & recordData;

};

// Calling code
boost::json::value & inputDocument;
...
boost::json::object & documentRoot = inputDocument.as_object();
boost::json::value & rootRecordData = documentRoot["beerjson"];
boost::json::object & rootRecordDataObject = rootRecordData.as_object();

// This logs correctly - eg "Root record contains 2 elements"
std::cout << "Root record contains" << rootRecordDataObject.size() << "elements";

MyClass myClassWorking{rootRecordData};
myClassWorking.load(); // Logs correct info - eg "Loading record containing 2 elements"

MyClass myClassBroken{rootRecordDataObject};
myClassBroken.load(); // Logs garbage info - eg "Loading record containing<PHONE_NUMBER> elements"

I'm entirely prepared to believe I'm doing something idiotic, but I can't immediately see what it is!

When you acquire a reference to an element, the reference can become invalidated if you modify the container it came from. Are you changing something in load?

As far as I can tell I am not changing anything.  It is certainly not my intent, as I am only trying to read the file, not modify it (hence why recordData is a const reference.
I changed the other variables to const (which means using *documentRoot.if_contains("beerjson") instead of documentRoot["beerjson"] etc) but I got the same results.
Is there any increased logging or diagnostics I can turn on to flag when a container is getting modified?

well where is inputDocument coming from? If someone modifies that container, it doesn't matter that you hold a const reference to it, things will become invalidated.

I hear what you're saying.  I would love to give a self-contained example, but I'm using the Qt framework so it's non-trivial to change everything to use only libraries available on godbolt.org.
That said, I think I can convince myself that inputDocument is not invalidated by adding a log line at the end:
class MyClass {
public:

   MyClass(boost::json::value const & recordData) : recordData{recordData} {return; }
...
   void load() {
      std::cout << "Loading record containing" << this->recordData.as_object().size() << "elements";
...
   }
...
protected:
   boost::json::value const & recordData;

};

// Calling code
boost::json::value & inputDocument;
...
boost::json::object & documentRoot = inputDocument.as_object();
boost::json::value & rootRecordData = documentRoot["beerjson"];
boost::json::object & rootRecordDataObject = rootRecordData.as_object();

// This logs correctly - eg "Root record contains 2 elements"
std::cout << "Root record contains" << rootRecordDataObject.size() << "elements";

MyClass myClassWorking{rootRecordData};
myClassWorking.load(); // Logs correct info - eg "Loading record containing 2 elements"

MyClass myClassBroken{rootRecordDataObject};
myClassBroken.load(); // Logs garbage info - eg "Loading record containing<PHONE_NUMBER> elements"

// This logs correctly - eg "At the end, root record contains 2 elements"
std::cout << "At the end, root record contains" << rootRecordDataObject.size() << "elements";

I'll keep plugging away at my code, making sure I avoid the casts, and see if I hit any other errors.  That might throw light on whether I'm doing something wrong with object lifetimes etc.

OH... I see the problem. If MyClass::MyClass( value const &) is constructed from object, then the class will be retaining a reference to a temporary. To prevent this from happening, change your parameter types to pointers. This will give you a compiler error if you attempt to pass a temporary to the class:
MyClass::MyClass( json::value const* jv )
  : recordData( *jv )
  {
  }

I had to do the same thing in the serializer, for the same reason:
https://github.com/boostorg/json/blob/2cbc263ced1e2e8151fd8096e1f4e8b87eaeaa28/include/boost/json/serializer.hpp#L165

Ah, OK, thanks, I think I see.  We are implicitly constructing a temporary json::value from the json::object and then that json::value goes out of scope, the reference to it is invalid?

Since the problem has been resolved, I am closing the issue.


Remove deployment from Codeship test commands

Since the deployment is already triggered through the Add a deployment script section, I don't think it is necessary in the test commands.
Apologies if I'm missing something here.
Great work btw, the new token feature and these guides are really great! :+1:

Thanks for the PR! I originally wrote it that way and then discovered the proper deployment section, I must have missed updating this example.
Glad it’s working out for you :)


Can't send HTML email

How does one send HTML email with this node?

@grantwparks Any progress on this? Would love to have html email.


Fix linting issues

What type of PR is this?

cleanup

What this PR does / why we need it:
Fixes 100% of golangci-lint linting issues
Which issue(s) this PR fixes:
Partially fixes #1663
Testing
https://asciinema.org/a/ucDYTAfRZzASFpkmpfdrTxQHJ
ran make
Release Notes
Update to pass `golangci-lint`

Can we override the patch diff, or should I add test cases for the error checks?

@meatballhat

can either this PR or a near future follow-up PR add golangci-lint integration in CI to assert that new linting errors are not introduced?

I'd love to make this change, but i'm not sure where to start with CI integrations.


InputToolbar does not follow keyboard

I am using version 6.1.0, the latest commit on master branch.
When I tap on the UITextField, the keyboard appears on top of it. That is, the InputToolbar does not follow the keyboard. Since the keyboard is on top, user has to get rid of the keyboard to be able to press the "send" button.
Interesting thing is, it works perfectly in the demo project. I removed the dependency from Podfile and added the code from the demo project. And it still doesn't work with my project. Any help would be useful.
I could reproduce the same bug on all devices, simulator and real.

Hi. I am facing the same issue, and i am calling [super viewDidAppear] ... and nothing changed. Moreover, i removed the code from the demo, and the keyboard is working perfectly without this method: - (void)viewDidAppear:(BOOL)animated
{
[super viewDidAppear:animated];
/**
 *  Enable/disable springy bubbles, default is NO.
 *  You must set this from `viewDidAppear:`
 *  Note: this feature is mostly stable, but still experimental
 */
//self.collectionView.collectionViewLayout.springinessEnabled = [NSUserDefaults springinessSetting];

}
What am i doing wrong?


Adding keoni to be maintainer

@Keong101 this will add you as a maintainer to the conda-forge repository.
Signed-off-by: Vanessa Sochat<EMAIL_ADDRESS>
Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Pete's functional review comments 2024-07-25

Here's my functionality review comments (I have a few editorial / stylistic comments that can wait for another iteration):

We should probably add a section describing how "vendor specific variants" should be handled, especially their impact on overallStatus.  Also, discuss when to extend NcReceiverMonitor or create an additional class for monitoring additional functionality (for example, what should be done for my recorder scenario and licensed receiver scenario?).

I think support of late and lost packets methods is optional.  If so, we should say this and what is returned if they are not supported (e.g. "MethodNotImplemented")

Add comment that the touchpoints in NcStatusMonitor's NcObject base class MUST be used to indicate the IS-04 receiver the status relates to (i.e. move comments from the Feature Set document to the BCP) and the userLabel can be used as well.

Current wording says counters will be reset when a new set of addresses is applied (i.e. on re-activation).  Is this the desired behaviour?

Should lost/late packets be counted or ignored in the reporting delay period?

This has been superseded by changes to the spec during activity meetings.


Run all unit tests on CI.

What
We were only running a subset of unit tests on CI. Let's run all of them.
How
Instead of trying to list the (growing) package names, let's just filter out the database tests.
This also updates the snapshots to include the new connection URI default value, as these tests were failing.
I had to move some tests into the databases-tests package as they weren't really unit tests.

@soupi, I have moved the CLI and configuration tests causing problems into databases-tests.

@SamirTalwar test unit do not seem to be running

I've made the change.


Error in process_chat_message: API 请求出错: 404, message='Not Found', url='https://api.openai.com/v1/chat/completions'

{
"error": {
"message": "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}
我配置文件里有api-key呀，不懂为啥报这个错，求大佬指教

{
"error": {
"message": "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}
我配置文件里有api-key呀，不懂为啥报这个错，求大佬指教

有填model.json里的配置吗，如果只需要GPT，可以把model.json里的model的值去掉，如果不去掉会覆盖掉config.json里的GPT的配置


Add check host-src and container-dest folder should be abspath

As title, the host-src and container-dest folder should be abspath when 'hyperctl --v'
@laijs

@laijs updated, User Abspath


Update Dashboards for Grafana 11.4.0

Hi @jheredianet - i've opened several PRs that ensure all Dashboards working properly in latest Teslamate Grafana.
Do you want me to combine to ease merging / can I support in keeping things up to date?
(There will be one additional bump with all Dashboards exported for Grafana 11.4.0 but i did not want to open to many PRs at a time)

Would like to avoid that - if I remember correctly it had been busy times for @jheredianet
Also available to step in as a maintainer for this repo for a period of time. Let's wait a week or two.


Partial matrix updates

Performance improvement. Addresses #17

julia> include("src/datasets.jl")
julia> G = datasets.dblp()
{425956, 1049850} undirected simple Int64 graph

Previously:
julia> @time q_color(G, n_colors=25)
  9.668592 seconds (864.92 k allocations: 4.306 GiB, 0.85% gc time)
julia> @time q_color(G, n_colors=200)
125.482487 seconds (1.44 M allocations: 41.244 GiB, 0.90% gc time)

Now:
julia> @time q_color(G, n_colors=25)
 11.162688 seconds (865.82 k allocations: 4.247 GiB, 0.69% gc time)
julia> @time q_color(G, n_colors=200)
181.203694 seconds (1.45 M allocations: 48.911 GiB, 1.38% gc time)

After 85eda44:
julia> @time q_color(G, n_colors=25)
  6.055234 seconds (871.74 k allocations: 3.791 GiB, 1.18% gc time)
julia> @time q_color(G, n_colors=200)
 35.470032 seconds (1.65 M allocations: 39.466 GiB, 2.58% gc time)

Still too much memory being allocated but better performance now.


[CLS] [SEP] bug

https://github.com/gabeur/mmt/blob/ef81f96f3a77db273b247c4b60194edefd3e9e52/base/base_dataset.py#L343
The class transformers.tokenization_bert.BertTokenizer does not have cls_token_ids. Here must be cls_token_id
Due to this mistake all text examples do not have SEP and CLS tokens.

Good catch, thanks!
Fixing this bug seems to improve the results a bit. I will re-run pretraining and finetuning experiments and update the repo once the checkpoints are ready.

I have pushed a fix, re-run the experiments and updated the checkpoints accordingly.


[ICE: 20] The estimation algorithm for ETA is not working correctly

Describe the bug
#5966
I suppose something is wrong with the estimation algorithm we deployed on Friday, May 17th. The estimation for Eth-Linea ezETH is below:
To Reproduce
Steps to reproduce the behavior:

Go to 'transfers'
Click on Eth-Linea ezETH,
See that 100% transfers were on slow path past 2 days
Check bridge, it estimates me 2 mins

Screenshots

@jwtong @just-a-node
SLA: 3 working days

It works as expected


Acer R11 Xorg Bugs in Debian and Kali-rolling Chroots

name: kali-rolling
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/kali-rolling...
crouton: version 1-20161129162558~master:5f2f11f9
release: kali-rolling
architecture: amd64
xmethod: xorg
targets: xfce,keyboard,extension
host: version 8872.73.0 (Official Build) stable-channel cyan
kernel: Linux localhost 3.18.0-13436-g8b496ef #1 SMP PREEMPT Sat Dec 17 11:06:39 PST 2016 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/kali-rolling...
name: sid
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/sid...
crouton: version 1-20161129162558~master:5f2f11f9
release: sid
architecture: amd64
xmethod: xorg
targets: xfce,extension,keyboard
host: version 8872.73.0 (Official Build) stable-channel cyan
kernel: Linux localhost 3.18.0-13436-g8b496ef #1 SMP PREEMPT Sat Dec 17 11:06:39 PST 2016 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/sid...

Please describe your issue:
I've tried creating several Jessie, Stretch, Sid, and Kali-Rolling chroots since getting my Acer R11 over Christmas. In maybe half of the instances, once the install is finished, I have been able to successfully boot into xfce. The other half of the time, Xorg will hang on startup, and will give the appearance of my machine locking up. Using the shortcut to switch between ChromeOS and the chroot will allow me to regain control, though Xorg will then fail and exit.
In the instances where I've been able to at least enter the chroots when starting them up for the first time, after two or three starts, Xorg will hang in the same way it does for the chroots that I was never to enter xfce in in the first place.
Strangely enough, I've had zero issues of this sort when using Xenial. I haven't tried other Ubuntu releases, though.
Apologies if I'm not describing this well. If I can clarify anything or provide logs, let me know. I have found bug reports involving black screens, but nothing that seems to match this exactly. I did try the uxa fix in #2923 in my latest Kali-rolling chroot, but to no avail.
If known, describe the steps to reproduce the issue:

Create Jessie, Stretch, Sid, or Kali-rolling chroots with xfce, keyboard, and extension targets.
Attempt to enter xfce, either with sudo enter-chroot, followed by startxfce4 inside the chroot, or sudo startxfce4 from crosh.
If able to enter the DE, wait awhile and try starting xfce later.

After reporting my issue, I saw that this one had been closed earlier today: #3010 . I hadn't noticed the solution another R11 user posted there:
Section "Device" Identifier "Intel Graphics" Driver "intel" EndSection
Tried editing my /etc/crouton/xorg-intel-sna.conf this way in my Kali-rolling chroot, and have been able to get back in so far. I'll keep using it and see if that holds.
Is there likely to be any adverse effect from not including the SNA+Tear Free identifier and the 'Option "AccelMethod" "uxa"' entry? This sounds like it may be related to #2926. Whether the issue's fixed for me or not, I'd be happy to supply some more information, if it will help.

@Admiral-Irony,
Sorry to hear your fix didn't stick, usually the 'uxa' method works so your issue may be a little different.
If you show us your Xorg log(s), someone may be able to pinpoint the problem. It's a little out of my area of expertise but I'll take a look.
Another option you might want to try is adding the 'xiwi' xmethod/target to your chroot.
It won't have hardware acceleration but if don't use a lot of graphics intense apps it may work well for you.
Hope this helps,
-DennisL

Here's the output of cat /tmp/Xorg.crouton.1.log from a test start I ran this morning, which had the same result (screen lockup as if the Xorg window started, and a Xorg hangup after using the shortcut to move between Chrome and crouton twice):
`[   532.763] _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
[   532.764]
X.Org X Server 1.19.0
Release Date: 2016-11-15
[   532.764] X Protocol Version 11, Revision 0
[   532.764] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[   532.764] Current Operating System: Linux localhost 3.18.0-13436-g8b496ef #1 SMP PREEMPT Sat Dec 17 11:06:39 PST 2016 x86_64
[   532.765] Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 3584000 verity payload=PARTUUID=9cd8e084-c341-ba40-a8e5-f5cdde035ce4/PARTNROFF=1 hashtree=PARTUUID=9cd8e084-c341-ba40-a8e5-f5cdde035ce4/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=258106db6679e005ade61f96c43e12e57aa9d9cb salt=02423cd971bb657eba8df9b139d38988bf28758d62eeb0929851eb2a6755a23a" noinitrd vt.global_cursor_default=0 kern_guid=9cd8e084-c341-ba40-a8e5-f5cdde035ce4 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
[   532.765] Build Date: 16 December 2016  07:30:27PM
[   532.765] xorg-server 2:1.19.0-3 (https://www.debian.org/support)
[   532.765] Current version of pixman: 0.34.0
[   532.765]    Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   532.765] Markers: (--) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   532.765] (++) Log file: "/tmp/Xorg.crouton.1.log", Time: Thu Jan 12 06:14:55 2017
[   532.765] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   532.766] (==) No Layout section.  Using the first Screen section.
[   532.766] (==) No screen section available. Using defaults.
[   532.766] () |-->Screen "Default Screen Section" (0)
[   532.766] (**) |   |-->Monitor ""
[   532.766] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   532.766] (==) Automatically adding devices
[   532.766] (==) Automatically enabling devices
[   532.766] (==) Automatically adding GPU devices
[   532.766] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   532.766] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   532.766]    Entry deleted from font path.
[   532.766] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   532.766] (==) ModulePath set to "/usr/lib/xorg/modules"
[   532.766] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[   532.766] (II) Loader magic: 0x7f2814b2de00
[   532.766] (II) Module ABI versions:
[   532.766]    X.Org ANSI C Emulation: 0.4
[   532.766]    X.Org Video Driver: 23.0
[   532.766]    X.Org XInput driver : 24.1
[   532.766]    X.Org Server Extension : 10.0
[   532.768] (--) using VT number 7
[   532.768] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[   532.769] (II) xfree86: Adding drm device (/dev/dri/card0)
[   532.770] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
[   532.774] (--) PCI:*(0:0:2:0) 8086:22b1:8086:7270 rev 33, Mem @ 0xd0000000/16777216, 0xc0000000/268435456, I/O @ 0x00001000/64
[   532.774] (II) LoadModule: "glx"
[   532.774] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   532.777] (II) Module glx: vendor="X.Org Foundation"
[   532.777]    compiled for 1.19.0, module version = 1.0.0
[   532.777]    ABI class: X.Org Server Extension, version 10.0
[   532.777] (==) Matched modesetting as autoconfigured driver 0
[   532.777] (==) Matched fbdev as autoconfigured driver 1
[   532.777] (==) Matched vesa as autoconfigured driver 2
[   532.777] (==) Assigned the driver to the xf86ConfigLayout
[   532.777] (II) LoadModule: "modesetting"
[   532.777] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   532.777] (II) Module modesetting: vendor="X.Org Foundation"
[   532.777]    compiled for 1.19.0, module version = 1.19.0
[   532.777]    Module class: X.Org Video Driver
[   532.777]    ABI class: X.Org Video Driver, version 23.0
[   532.777] (II) LoadModule: "fbdev"
[   532.778] (WW) Warning, couldn't open module fbdev
[   532.778] (II) UnloadModule: "fbdev"
[   532.778] (II) Unloading fbdev
[   532.778] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   532.778] (II) LoadModule: "vesa"
[   532.778] (WW) Warning, couldn't open module vesa
[   532.778] (II) UnloadModule: "vesa"
[   532.778] (II) Unloading vesa
[   532.778] (EE) Failed to load module "vesa" (module does not exist, 0)
[   532.778] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   532.792] () modeset(0): claimed PCI slot 0@0:2:0
[   532.793] (II) modeset(0): using default device
[   532.793] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[   532.793] (II) modeset(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[   532.793] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[   532.793] (==) modeset(0): RGB weight 888
[   532.793] (==) modeset(0): Default visual is TrueColor
[   532.793] (II) Loading sub module "glamoregl"
[   532.793] (II) LoadModule: "glamoregl"
[   532.793] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[   532.802] (II) Module glamoregl: vendor="X.Org Foundation"
[   532.802]    compiled for 1.19.0, module version = 1.0.0
[   532.802]    ABI class: X.Org ANSI C Emulation, version 0.4
[   532.802] (II) glamor: OpenGL accelerated X.org driver based.
[   532.825] (II) glamor: EGL version 1.4 (DRI2):
[   532.828] (II) modeset(0): glamor initialized
[   532.829] (II) modeset(0): Output eDP-1 has no monitor section
[   532.837] (II) modeset(0): Output HDMI-1 has no monitor section
[   532.853] (II) modeset(0): Output DP-1 has no monitor section
[   532.941] (II) modeset(0): Output HDMI-2 has no monitor section
[   532.989] (II) modeset(0): Output DP-2 has no monitor section
[   532.991] (II) modeset(0): EDID for output eDP-1
[   532.991] (II) modeset(0): Manufacturer: AUO  Model: 405c  Serial#: 0
[   532.991] (II) modeset(0): Year: 2015  Week: 0
[   532.991] (II) modeset(0): EDID Version: 1.4
[   532.991] (II) modeset(0): Digital Display Input
[   532.991] (II) modeset(0): 6 bits per channel
[   532.991] (II) modeset(0): Digital interface is undefined
[   532.991] (II) modeset(0): Max Image Size [cm]: horiz.: 26  vert.: 14
[   532.991] (II) modeset(0): Gamma: 2.20
[   532.991] (II) modeset(0): No DPMS capabilities specified
[   532.991] (II) modeset(0): Supported color encodings: RGB 4:4:4
[   532.991] (II) modeset(0): First detailed timing is preferred mode
[   532.991] (II) modeset(0): Preferred mode is native pixel format and refresh rate
[   532.991] (II) modeset(0): redX: 0.584 redY: 0.333   greenX: 0.338 greenY: 0.571
[   532.991] (II) modeset(0): blueX: 0.158 blueY: 0.133   whiteX: 0.313 whiteY: 0.329
[   532.991] (II) modeset(0): Manufacturer's mask: 0
[   532.991] (II) modeset(0): Supported detailed timing:
[   532.991] (II) modeset(0): clock: 69.3 MHz   Image Size:  256 x 144 mm
[   532.991] (II) modeset(0): h_active: 1366  h_sync: 1414  h_sync_end 1446 h_blank_end 1456 h_border: 0
[   532.991] (II) modeset(0): v_active: 768  v_sync: 772  v_sync_end 778 v_blanking: 793 v_border: 0
[   532.991] (II) modeset(0): Unknown vendor-specific block f
[   532.991] (II) modeset(0):  AUO
[   532.991] (II) modeset(0):  B116XAN04.0
[   532.991] (II) modeset(0): EDID (in hex):
[   532.991] (II) modeset(0):   00ffffffffffff0006af5c4000000000
[   532.991] (II) modeset(0):<PHONE_NUMBER>1a0e780299859555569228
[   532.991] (II) modeset(0):<PHONE_NUMBER>0001010101010101010101
[   532.991] (II) modeset(0):<PHONE_NUMBER>01121b565a500019303020
[   532.991] (II) modeset(0):<PHONE_NUMBER>0000180000000f00000000
[   532.991] (II) modeset(0):<PHONE_NUMBER>0000000020000000fe0041
[   532.991] (II) modeset(0):   554f0a202020202020202020000000fe
[   532.991] (II) modeset(0):<PHONE_NUMBER>58414e30342e30200a00cc
[   532.992] (II) modeset(0): Printing probed modes for output eDP-1
[   532.992] (II) modeset(0): Modeline "1366x768"x60.0   69.30  1366 1414 1446 1456  768 772 778 793 -hsync -vsync (47.6 kHz eP)
[   532.992] (II) modeset(0): Modeline "1360x768"x59.8   84.75  1360 1432 1568 1776  768 771 781 798 -hsync +vsync (47.7 kHz d)
[   532.992] (II) modeset(0): Modeline "1360x768"x60.0   72.00  1360 1408 1440 1520  768 771 781 790 +hsync -vsync (47.4 kHz d)
[   532.992] (II) modeset(0): Modeline "1024x768"x120.1  133.47  1024 1100 1212 1400  768 768 770 794 doublescan -hsync +vsync (95.3 kHz d)
[   532.992] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz d)
[   532.992] (II) modeset(0): Modeline "960x720"x120.0  117.00  960 1024 1128 1300  720 720 722 750 doublescan -hsync +vsync (90.0 kHz d)
[   532.992] (II) modeset(0): Modeline "928x696"x120.1  109.15<PHONE_NUMBER> 1264  696 696 698 719 doublescan -hsync +vsync (86.4 kHz d)
[   532.992] (II) modeset(0): Modeline "896x672"x120.0  102.40<PHONE_NUMBER> 1224  672 672 674 697 doublescan -hsync +vsync (83.7 kHz d)
[   532.992] (II) modeset(0): Modeline "960x600"x120.0   77.00<PHONE_NUMBER> 1040  600 601 604 617 doublescan +hsync -vsync (74.0 kHz d)
[   532.992] (II) modeset(0): Modeline "960x540"x120.0   69.25<PHONE_NUMBER> 1040  540 541 544 555 doublescan +hsync -vsync (66.6 kHz d)
[   532.992] (II) modeset(0): Modeline "800x600"x120.0   81.00  800<PHONE_NUMBER>  600 600 602 625 doublescan +hsync +vsync (75.0 kHz d)
[   532.992] (II) modeset(0): Modeline "800x600"x60.3   40.00  800<PHONE_NUMBER>  600 601 605 628 +hsync +vsync (37.9 kHz d)
[   532.992] (II) modeset(0): Modeline "800x600"x56.2   36.00  800<PHONE_NUMBER>  600 601 603 625 +hsync +vsync (35.2 kHz d)
[   532.992] (II) modeset(0): Modeline "840x525"x120.0   73.12  840<PHONE_NUMBER>  525 526 529 544 doublescan -hsync +vsync (65.3 kHz d)
[   532.992] (II) modeset(0): Modeline "840x525"x119.8   59.50  840 864 880 920  525 526 529 540 doublescan +hsync -vsync (64.7 kHz d)
[   532.992] (II) modeset(0): Modeline "800x512"x120.3   51.56  800 800 828 832  512 512 514 515 doublescan +hsync +vsync (62.0 kHz d)
[   532.992] (II) modeset(0): Modeline "700x525"x120.0   61.00  700 744 820 940  525 526 532 541 doublescan +hsync +vsync (64.9 kHz d)
[   532.992] (II) modeset(0): Modeline "640x512"x120.0   54.00  640 664 720 844  512 512 514 533 doublescan +hsync +vsync (64.0 kHz d)
[   532.992] (II) modeset(0): Modeline "720x450"x119.8   53.25  720 760 836 952  450 451 454 467 doublescan -hsync +vsync (55.9 kHz d)
[   532.992] (II) modeset(0): Modeline "640x480"x120.0   54.00  640 688 744 900  480 480 482 500 doublescan +hsync +vsync (60.0 kHz d)
[   532.992] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz d)
[   532.992] (II) modeset(0): Modeline "680x384"x119.6   42.38  680 716 784 888  384 385 390 399 doublescan -hsync +vsync (47.7 kHz d)
[   532.992] (II) modeset(0): Modeline "680x384"x119.9   36.00  680 704 720 760  384 385 390 395 doublescan +hsync -vsync (47.4 kHz d)
[   532.992] (II) modeset(0): Modeline "576x432"x120.1   40.81  576 608 668 760  432 432 434 447 doublescan -hsync +vsync (53.7 kHz d)
[   532.992] (II) modeset(0): Modeline "512x384"x120.0   32.50  512 524 592 672  384 385 388 403 doublescan -hsync -vsync (48.4 kHz d)
[   532.993] (II) modeset(0): Modeline "400x300"x120.6   20.00  400 420 484 528  300 300 302 314 doublescan +hsync +vsync (37.9 kHz d)
[   532.993] (II) modeset(0): Modeline "400x300"x112.7   18.00  400 412 448 512  300 300 301 312 doublescan +hsync +vsync (35.2 kHz d)
[   532.993] (II) modeset(0): Modeline "320x240"x120.1   12.59  320 328 376 400  240 245 246 262 doublescan -hsync -vsync (31.5 kHz d)
[   533.001] (II) modeset(0): EDID for output HDMI-1
[   533.016] (II) modeset(0): EDID for output DP-1
[   533.104] (II) modeset(0): EDID for output HDMI-2
[   533.151] (II) modeset(0): EDID for output DP-2
[   533.151] (II) modeset(0): Output eDP-1 connected
[   533.151] (II) modeset(0): Output HDMI-1 disconnected
[   533.151] (II) modeset(0): Output DP-1 disconnected
[   533.151] (II) modeset(0): Output HDMI-2 disconnected
[   533.151] (II) modeset(0): Output DP-2 disconnected
[   533.151] (II) modeset(0): Using exact sizes for initial modes
[   533.151] (II) modeset(0): Output eDP-1 using initial mode 1366x768 +0+0
[   533.152] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[   533.152] (==) modeset(0): DPI set to (96, 96)
[   533.152] (II) Loading sub module "fb"
[   533.152] (II) LoadModule: "fb"
[   533.152] (II) Loading /usr/lib/xorg/modules/libfb.so
[   533.153] (II) Module fb: vendor="X.Org Foundation"
[   533.153]    compiled for 1.19.0, module version = 1.0.0
[   533.153]    ABI class: X.Org ANSI C Emulation, version 0.4
[   533.153] (==) Depth 24 pixmap format is 32 bpp
[   533.340] (==) modeset(0): Backing store enabled
[   533.340] (==) modeset(0): Silken mouse enabled
[   533.340] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[   533.341] (==) modeset(0): DPMS enabled
[   533.341] (II) modeset(0): [DRI2] Setup complete
[   533.341] (II) modeset(0): [DRI2]   DRI driver: i965
[   533.341] (II) modeset(0): [DRI2]   VDPAU driver: i965
[   533.341] (--) RandR disabled
[   533.347] (II) SELinux: Disabled on system
[   533.356] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[   533.357] (II) AIGLX: enabled GLX_ARB_create_context
[   533.357] (II) AIGLX: enabled GLX_ARB_create_context_profile
[   533.357] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[   533.357] (II) AIGLX: enabled GLX_INTEL_swap_event
[   533.357] (II) AIGLX: enabled GLX_SGI_swap_control
[   533.357] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[   533.357] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[   533.357] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[   533.357] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[   533.357] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[   533.357] (II) AIGLX: Loaded and initialized i965
[   533.357] (II) GLX: Initialized DRI2 GL provider for screen 0
[   533.363] (II) modeset(0): Damage tracking initialized
[   533.363] (II) modeset(0): Setting screen physical size to 361 x 203
[   533.459] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[   533.460] () Power Button: Applying InputClass "libinput keyboard catchall"
[   533.460] (II) LoadModule: "libinput"
[   533.460] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[   533.464] (II) Module libinput: vendor="X.Org Foundation"
[   533.464]    compiled for 1.19.0, module version = 0.22.0
[   533.464]    Module class: X.Org XInput Driver
[   533.464]    ABI class: X.Org XInput driver, version 24.1
[   533.464] (II) Using input driver 'libinput' for 'Power Button'
[   533.464] () Power Button: always reports core events
[   533.464] () Option "Device" "/dev/input/event2"
[   533.464] () Option "_source" "server/udev"
[   533.465] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
[   533.465] (II) input device 'Power Button', /dev/input/event2 is a keyboard
[   533.490] () Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[   533.490] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[   533.492] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
[   533.492] (II) input device 'Power Button', /dev/input/event2 is a keyboard
[   533.493] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[   533.494] () Power Button: Applying InputClass "libinput keyboard catchall"
[   533.494] (II) Using input driver 'libinput' for 'Power Button'
[   533.494] () Power Button: always reports core events
[   533.494] () Option "Device" "/dev/input/event1"
[   533.494] () Option "_source" "server/udev"
[   533.495] (II) input device 'Power Button', /dev/input/event1 is tagged by udev as: Keyboard
[   533.495] (II) input device 'Power Button', /dev/input/event1 is a keyboard
[   533.520] () Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[   533.520] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[   533.522] (II) input device 'Power Button', /dev/input/event1 is tagged by udev as: Keyboard
[   533.522] (II) input device 'Power Button', /dev/input/event1 is a keyboard
[   533.523] (II) config/udev: Adding input device Lid Switch (/dev/input/event0)
[   533.523] (II) No input driver specified, ignoring this device.
[   533.523] (II) This device may have been added with another device file.
[   533.523] (II) config/udev: Adding drm device (/dev/dri/card0)
[   533.523] (II) xfree86: Adding drm device (/dev/dri/card0)
[   533.524] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
[   533.526] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event7)
[   533.526] (II) No input driver specified, ignoring this device.
[   533.526] (II) This device may have been added with another device file.
[   533.527] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event8)
[   533.527] (II) No input driver specified, ignoring this device.
[   533.527] (II) This device may have been added with another device file.
[   533.528] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event9)
[   533.528] (II) No input driver specified, ignoring this device.
[   533.528] (II) This device may have been added with another device file.
[   533.529] (II) config/udev: Adding input device chtmax98090 Headset Jack (/dev/input/event6)
[   533.529] () chtmax98090 Headset Jack: Applying InputClass "libinput keyboard catchall"
[   533.529] (II) Using input driver 'libinput' for 'chtmax98090 Headset Jack'
[   533.529] () chtmax98090 Headset Jack: always reports core events
[   533.529] () Option "Device" "/dev/input/event6"
[   533.529] () Option "_source" "server/udev"
[   533.530] (II) input device 'chtmax98090 Headset Jack', /dev/input/event6 is tagged by udev as: Keyboard
[   533.530] (II) input device 'chtmax98090 Headset Jack', /dev/input/event6 is a keyboard
[   533.552] () Option "config_info" "udev:/sys/devices/platform/808622A8:00/cht-bsw-max98090/sound/card0/input6/event6"
[   533.552] (II) XINPUT: Adding extended input device "chtmax98090 Headset Jack" (type: KEYBOARD, id 8)
[   533.554] (II) input device 'chtmax98090 Headset Jack', /dev/input/event6 is tagged by udev as: Keyboard
[   533.554] (II) input device 'chtmax98090 Headset Jack', /dev/input/event6 is a keyboard
[   533.555] (II) config/udev: Adding input device Elan Touchscreen (/dev/input/event4)
[   533.555] () Elan Touchscreen: Applying InputClass "libinput touchscreen catchall"
[   533.555] (II) Using input driver 'libinput' for 'Elan Touchscreen'
[   533.555] () Elan Touchscreen: always reports core events
[   533.555] () Option "Device" "/dev/input/event4"
[   533.555] () Option "_source" "server/udev"
[   533.556] (II) input device 'Elan Touchscreen', /dev/input/event4 is tagged by udev as: Touchscreen
[   533.556] (II) input device 'Elan Touchscreen', /dev/input/event4 is a touch device
[   533.579] () Option "config_info" "udev:/sys/devices/platform/808622C1:00/i2c-0/i2c-ELAN0001:00/input/input4/event4"
[   533.579] (II) XINPUT: Adding extended input device "Elan Touchscreen" (type: TOUCHSCREEN, id 9)
[   533.580] () Option "AccelerationScheme" "none"
[   533.580] () Elan Touchscreen: (accel) selected scheme none/0
[   533.580] () Elan Touchscreen: (accel) acceleration factor: 2.000
[   533.580] () Elan Touchscreen: (accel) acceleration threshold: 4
[   533.581] (II) input device 'Elan Touchscreen', /dev/input/event4 is tagged by udev as: Touchscreen
[   533.581] (II) input device 'Elan Touchscreen', /dev/input/event4 is a touch device
[   533.583] (II) config/udev: Adding input device Elan Touchpad (/dev/input/event5)
[   533.583] () Elan Touchpad: Applying InputClass "libinput touchpad catchall"
[   533.583] (II) Using input driver 'libinput' for 'Elan Touchpad'
[   533.583] () Elan Touchpad: always reports core events
[   533.583] () Option "Device" "/dev/input/event5"
[   533.583] () Option "_source" "server/udev"
[   533.584] (II) input device 'Elan Touchpad', /dev/input/event5 is tagged by udev as: Touchpad
[   533.584] (II) input device 'Elan Touchpad', /dev/input/event5 is a touchpad
[   533.609] () Option "config_info" "udev:/sys/devices/platform/808622C1:05/i2c-2/i2c-ELAN0000:00/input/input5/event5"
[   533.609] (II) XINPUT: Adding extended input device "Elan Touchpad" (type: TOUCHPAD, id 10)
[   533.610] () Option "AccelerationScheme" "none"
[   533.610] () Elan Touchpad: (accel) selected scheme none/0
[   533.610] () Elan Touchpad: (accel) acceleration factor: 2.000
[   533.610] () Elan Touchpad: (accel) acceleration threshold: 4
[   533.612] (II) input device 'Elan Touchpad', /dev/input/event5 is tagged by udev as: Touchpad
[   533.612] (II) input device 'Elan Touchpad', /dev/input/event5 is a touchpad
[   533.613] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3)
[   533.613] () AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[   533.613] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[   533.614] () AT Translated Set 2 keyboard: always reports core events
[   533.614] () Option "Device" "/dev/input/event3"
[   533.614] () Option "_source" "server/udev"
[   533.615] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event3 is tagged by udev as: Keyboard
[   533.615] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event3 is a keyboard
[   533.636] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input3/event3"
[   533.636] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[   533.638] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event3 is tagged by udev as: Keyboard
[   533.638] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event3 is a keyboard
[   533.645] (EE) modeset(0): failed to set mode: Invalid argument
[   534.155] (II) modeset(0): EDID vendor "AUO", prod id 16476
[   534.155] (II) modeset(0): Printing DDC gathered Modelines:
[   534.155] (II) modeset(0): Modeline "1366x768"x0.0   69.30  1366 1414 1446 1456  768 772 778 793 -hsync -vsync (47.6 kHz eP)
[   534.523] (II) modeset(0): EDID vendor "AUO", prod id 16476
[   534.523] (II) modeset(0): Printing DDC gathered Modelines:
[   534.523] (II) modeset(0): Modeline "1366x768"x0.0   69.30  1366 1414 1446 1456  768 772 778 793 -hsync -vsync (47.6 kHz eP)
[   545.317] (II) AIGLX: Suspending AIGLX clients for VT switch
[   550.807] (II) AIGLX: Resuming AIGLX clients after VT switch
[   550.807] (EE) modeset(0): failed to set mode: Invalid argument
[   550.807] (EE)
Fatal server error:
[   550.807] (EE) EnterVT failed for screen 0
[   550.807] (EE)
[   550.807] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[   550.807] (EE) Please also check the log file at "/tmp/Xorg.crouton.1.log" for additional information.
[   550.807] (EE)
[   550.807] (II) AIGLX: Suspending AIGLX clients for VT switch
[   550.824] (EE) Server terminated with error (1). Closing log file.`

I should have also mentioned that I've attempted xiwi a number of times, to no success. I wanted to attempt it one more time, to get the log. The attempt failed without a window starting up. Here's the output of cat /tmp/Xorg.crouton.2.log:
[  1360.790] _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
[  1360.791]
X.Org X Server 1.19.0
Release Date: 2016-11-15
[  1360.791] X Protocol Version 11, Revision 0
[  1360.791] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[  1360.791] Current Operating System: Linux localhost 3.18.0-13436-g8b496ef #1 SMP PREEMPT Sat Dec 17 11:06:39 PST 2016 x86_64
[  1360.791] Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 3584000 verity payload=PARTUUID=9cd8e084-c341-ba40-a8e5-f5cdde035ce4/PARTNROFF=1 hashtree=PARTUUID=9cd8e084-c341-ba40-a8e5-f5cdde035ce4/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=258106db6679e005ade61f96c43e12e57aa9d9cb salt=02423cd971bb657eba8df9b139d38988bf28758d62eeb0929851eb2a6755a23a" noinitrd vt.global_cursor_default=0 kern_guid=9cd8e084-c341-ba40-a8e5-f5cdde035ce4 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic
[  1360.791] Build Date: 16 December 2016  07:30:27PM
[  1360.791] xorg-server 2:1.19.0-3 (https://www.debian.org/support)
[  1360.791] Current version of pixman: 0.34.0
[  1360.791]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[  1360.791] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1360.792] (++) Log file: "/tmp/Xorg.crouton.2.log", Time: Thu Jan 12 14:34:39 2017
[  1360.792] (++) Using config file: "/etc/X11/xorg-dummy.conf"
[  1360.792] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1360.792] (==) ServerLayout "Layout0"
[  1360.792] (**) |-->Screen "Screen0" (0)
[  1360.792] (**) |   |-->Monitor "Monitor0"
[  1360.793] (**) |   |-->Device "Card0"
[  1360.793] (**) Option "DontVTSwitch" "true"
[  1360.793] (**) Option "AllowMouseOpenFail" "true"
[  1360.793] (**) Option "AutoAddDevices" "false"
[  1360.793] (**) Option "AutoEnableDevices" "false"
[  1360.793] (**) Option "AutoAddGPU" "false"
[  1360.793] (**) Not automatically adding devices
[  1360.793] (**) Not automatically enabling devices
[  1360.793] (**) Not automatically adding GPU devices
[  1360.793] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  1360.793] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  1360.793]    Entry deleted from font path.
[  1360.793] (==) FontPath set to:
        /usr/share/fonts/X11/misc,
        /usr/share/fonts/X11/100dpi/:unscaled,
        /usr/share/fonts/X11/75dpi/:unscaled,
        /usr/share/fonts/X11/Type1,
        /usr/share/fonts/X11/100dpi,
        /usr/share/fonts/X11/75dpi,
        built-ins
[  1360.793] (==) ModulePath set to "/usr/lib/xorg/modules"
[  1360.793] (==) |-->Input Device "<default pointer>"
[  1360.793] (==) |-->Input Device "<default keyboard>"
[  1360.793] (==) The core pointer device wasn't specified explicitly in the layout.
        Using the default mouse configuration.
[  1360.793] (==) The core keyboard device wasn't specified explicitly in the layout.
        Using the default keyboard configuration.
[  1360.793] (II) Loader magic: 0x7f9a5d9eee00
[  1360.793] (II) Module ABI versions:
[  1360.793]    X.Org ANSI C Emulation: 0.4
[  1360.793]    X.Org Video Driver: 23.0
[  1360.793]    X.Org XInput driver : 24.1
[  1360.793]    X.Org Server Extension : 10.0
[  1360.827] (EE) systemd-logind: failed to get session: Launch helper exited with unknown return code 1
[  1360.828] (II) xfree86: Adding drm device (/dev/dri/card0)
[  1360.829] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
[  1360.833] (--) PCI:*(0:0:2:0) 8086:22b1:8086:7270 rev 33, Mem @ 0xd0000000/16777216, 0xc0000000/268435456, I/O @ 0x00001000/64
[  1360.833] (II) LoadModule: "glx"
[  1360.833] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1360.836] (II) Module glx: vendor="X.Org Foundation"
[  1360.836]    compiled for 1.19.0, module version = 1.0.0
[  1360.836]    ABI class: X.Org Server Extension, version 10.0
[  1360.836] (II) LoadModule: "dummy"
[  1360.837] (II) Loading /usr/lib/xorg/modules/drivers/dummy_drv.so
[  1360.837] (II) Module dummy: vendor="X.Org Foundation"
[  1360.837]    compiled for 1.19.0, module version = 0.3.8
[  1360.837]    Module class: X.Org Video Driver
[  1360.837]    ABI class: X.Org Video Driver, version 23.0
[  1360.837] (II) LoadModule: "mouse"
[  1360.837] (WW) Warning, couldn't open module mouse
[  1360.837] (II) UnloadModule: "mouse"
[  1360.837] (II) Unloading mouse
[  1360.837] (EE) Failed to load module "mouse" (module does not exist, 0)
[  1360.837] (II) LoadModule: "kbd"
[  1360.838] (WW) Warning, couldn't open module kbd
[  1360.838] (II) UnloadModule: "kbd"
[  1360.838] (II) Unloading kbd
[  1360.838] (EE) Failed to load module "kbd" (module does not exist, 0)
[  1360.838] (II) DUMMY: Driver for Dummy chipsets: dummy
[  1360.838] (WW) Falling back to old probe method for dummy
[  1360.838] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[  1360.838] (II) DUMMY(0): Chipset is a DUMMY
[  1360.838] (**) DUMMY(0): Depth 24, (--) framebuffer bpp 32
[  1360.838] (==) DUMMY(0): RGB weight 888
[  1360.838] (==) DUMMY(0): Default visual is TrueColor
[  1360.838] (**) DUMMY(0): VideoRAM: 32768 kByte
[  1360.838] (--) DUMMY(0): Max Clock: 230000 kHz
[  1360.838] (II) DUMMY(0): Output default using monitor section Monitor0
[  1360.838] (II) DUMMY(0): Not using default mode "320x175" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "320x200" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "360x200" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "320x240" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "320x240" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "320x240" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "320x240" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "400x300" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "400x300" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "400x300" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "400x300" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "400x300" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "1024x768i" (interlace mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "512x384i" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "512x384" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "512x384" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "512x384" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "512x384" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "576x432" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "640x480" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "640x480" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "640x512" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "640x512" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "640x512" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "800x600" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "800x600" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "800x600" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "800x600" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "800x600" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "896x672" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "896x672" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "928x696" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "928x696" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "960x720" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "960x720" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "416x312" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "576x432" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "576x432" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "576x432" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "576x432" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "576x432" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "576x432" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "1360x768" (monitor doesn't support reduced blanking)
[  1360.838] (II) DUMMY(0): Not using default mode "680x384" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "680x384" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "700x525" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "700x525" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "700x525" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "700x525" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "720x450" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "800x512" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "1680x1050" (monitor doesn't support reduced blanking)
[  1360.838] (II) DUMMY(0): Not using default mode "840x525" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "840x525" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "840x525" (doublescan mode not supported)
[  1360.838] (II) DUMMY(0): Not using default mode "840x525" (doublescan mode not supported)
[  1360.839] (II) DUMMY(0): Not using default mode "840x525" (doublescan mode not supported)
[  1360.839] (II) DUMMY(0): Not using default mode "1920x1080" (monitor doesn't support reduced blanking)
[  1360.839] (II) DUMMY(0): Not using default mode "960x540" (doublescan mode not supported)
[  1360.839] (II) DUMMY(0): Not using default mode "1920x1200" (monitor doesn't support reduced blanking)
[  1360.839] (II) DUMMY(0): Not using default mode "960x600" (doublescan mode not supported)
[  1360.839] (II) DUMMY(0): Not using default mode "960x720" (doublescan mode not supported)
[  1360.839] (II) DUMMY(0): Not using default mode "1024x768" (doublescan mode not supported)
[  1360.839] (II) DUMMY(0): Not using default mode "1024x768" (doublescan mode not supported)
[  1360.839] (II) DUMMY(0): Not using default mode "1024x768" (doublescan mode not supported)
[  1360.839] (II) DUMMY(0): Printing probed modes for output default
[  1360.839] (II) DUMMY(0): Modeline "1024x768"x85.0   94.50  1024 1072 1168 1376  768 769 772 808 +hsync +vsync (68.7 kHz UdP)
[  1360.839] (II) DUMMY(0): Modeline "2048x1536"x85.0  388.04  2048 2216 2440 2832  1536 1537 1540 1612 -hsync +vsync (137.0 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "2048x1536"x75.0  340.48  2048 2216 2440 2832  1536 1537 1540 1603 -hsync +vsync (120.2 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "2048x1536"x60.0  266.95  2048 2200 2424 2800  1536 1537 1540 1589 -hsync +vsync (95.3 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1920x1440"x85.0  341.35  1920 2072 2288 2656  1440 1441 1444 1512 -hsync +vsync (128.5 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1920x1440"x75.0  297.00  1920 2064 2288 2640  1440 1441 1444 1500 -hsync +vsync (112.5 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1920x1440"x60.0  234.00  1920 2048 2256 2600  1440 1441 1444 1500 -hsync +vsync (90.0 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1856x1392"x75.0  288.00  1856 1984 2208 2560  1392 1393 1396 1500 -hsync +vsync (112.5 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1856x1392"x60.0  218.30  1856 1952 2176 2528  1392 1393 1396 1439 -hsync +vsync (86.4 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1792x1344"x75.0  261.00  1792 1888 2104 2456  1344 1345 1348 1417 -hsync +vsync (106.3 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1792x1344"x60.0  204.80  1792 1920 2120 2448  1344 1345 1348 1394 -hsync +vsync (83.7 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1600x1200"x85.0  229.50  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (106.2 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1600x1200"x75.0  202.50  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (93.8 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1600x1200"x70.0  189.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (87.5 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1600x1200"x65.0  175.50  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (81.2 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1600x1200"x60.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1680x1050"x84.9  214.75  1680 1808 1984 2288  1050 1053 1059 1105 -hsync +vsync (93.9 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1680x1050"x74.9  187.00  1680 1800 1976 2272  1050 1053 1059 1099 -hsync +vsync (82.3 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1680x1050"x69.9  174.00  1680 1800 1976 2272  1050 1053 1059 1096 -hsync +vsync (76.6 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1680x1050"x60.0  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1600x1024"x60.2  103.12  1600 1600 1656 1664  1024 1024 1029 1030 +hsync +vsync (62.0 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1400x1050"x85.0  179.26  1400 1504 1656 1912  1050 1051 1054 1103 -hsync +vsync (93.8 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1400x1050"x74.8  155.80  1400 1464 1784 1912  1050 1052 1064 1090 +hsync +vsync (81.5 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1400x1050"x70.0  145.06  1400 1496 1648 1896  1050 1051 1054 1093 -hsync +vsync (76.5 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1400x1050"x60.0  122.00  1400 1488 1640 1880  1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1280x1024"x85.0  157.50  1280 1344 1504 1728  1024 1025 1028 1072 +hsync +vsync (91.1 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1280x1024"x75.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1440x900"x59.9  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1280x960"x85.0  148.50  1280 1344 1504 1728  960<PHONE_NUMBER> +hsync +vsync (85.9 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960<PHONE_NUMBER> +hsync +vsync (60.0 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1360x768"x59.8   84.75  1360 1432 1568 1776  768 771 781 798 -hsync +vsync (47.7 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1152x864"x100.0  143.47  1152 1232 1360 1568  864 865 868 915 -hsync +vsync (91.5 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1152x864"x85.1  121.50  1152 1216 1344 1568  864 865 868 911 +hsync -vsync (77.5 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1152x864"x85.0  119.65  1152 1224 1352 1552  864 865 868 907 -hsync +vsync (77.1 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1152x864"x75.0  104.99  1152 1224 1352 1552  864 865 868 902 -hsync +vsync (67.6 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1152x864"x70.0   96.77  1152 1224 1344 1536  864 865 868 900 -hsync +vsync (63.0 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1152x864"x60.0   81.62  1152 1216 1336 1520  864 865 868 895 -hsync +vsync (53.7 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1024x768"x75.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1024x768"x70.1   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "832x624"x74.6   57.28  832<PHONE_NUMBER>  624 625 628 667 -hsync -vsync (49.7 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "800x600"x85.1   56.30  800<PHONE_NUMBER>  600 601 604 631 +hsync +vsync (53.7 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "800x600"x72.2   50.00  800<PHONE_NUMBER>  600 637 643 666 +hsync +vsync (48.1 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "800x600"x75.0   49.50  800<PHONE_NUMBER>  600 601 604 625 +hsync +vsync (46.9 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "800x600"x60.3   40.00  800<PHONE_NUMBER>  600 601 605 628 +hsync +vsync (37.9 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "800x600"x56.2   36.00  800<PHONE_NUMBER>  600 601 603 625 +hsync +vsync (35.2 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "640x480"x85.0   36.00  640 696 752 832  480 481 484 509 -hsync -vsync (43.3 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "640x480"x72.8   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "720x400"x85.0   35.50  720 756 828 936  400 401 404 446 -hsync +vsync (37.9 kHz d)
[  1360.839] (II) DUMMY(0): Modeline "640x400"x85.1   31.50  640 672 736 832  400 401 404 445 -hsync +vsync (37.9 kHz d)
[  1360.840] (II) DUMMY(0): Modeline "640x350"x85.1   31.50  640 672 736 832  350 382 385 445 +hsync -vsync (37.9 kHz d)
[  1360.840] (II) DUMMY(0): Output default connected
[  1360.840] (II) DUMMY(0): Using user preference for initial modes
[  1360.840] (II) DUMMY(0): Output default using initial mode 1024x768 +0+0
[  1360.840] (==) DUMMY(0): Using gamma correction (1.0, 1.0, 1.0)
[  1360.840] (==) DUMMY(0): DPI set to (96, 96)
[  1360.840] (II) Loading sub module "fb"
[  1360.840] (II) LoadModule: "fb"
[  1360.840] (II) Loading /usr/lib/xorg/modules/libfb.so
[  1360.840] (II) Module fb: vendor="X.Org Foundation"
[  1360.840]    compiled for 1.19.0, module version = 1.0.0
[  1360.840]    ABI class: X.Org ANSI C Emulation, version 0.4
[  1360.840] (II) Loading sub module "ramdac"
[  1360.840] (II) LoadModule: "ramdac"
[  1360.840] (II) Module "ramdac" already built-in
[  1360.840] (--) Depth 24 pixmap format is 32 bpp
[  1360.840] (==) DUMMY(0): Backing store enabled
[  1360.840] (==) DUMMY(0): Silken mouse enabled
[  1360.840] (II) DUMMY(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[  1360.841] (--) RandR disabled
[  1360.847] (II) SELinux: Disabled on system
[  1360.848] (II) AIGLX: Screen 0 is not DRI2 capable
[  1360.848] (EE) AIGLX: reverting to software rendering
[  1360.895] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[  1360.896] (II) IGLX: Loaded and initialized swrast
[  1360.896] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[  1360.896] (II) DUMMY(0): Setting screen physical size to 270 x 203

Built the new crouton script following the instructions posted by @jernic in #2997 (comment). After updating the chroot, I still had the same problem starting xorg, but xiwi's been working fine so far.
I'm still trying to figure out what's going on, as xorg has worked in several Xenial chroots with no problem. It only fails in the Kali and Debian chroots, and in those instances it fails in the same way it failed in the kali-rolling log I posted.

Updating chroot should fix this.


Map shows uninformative error when not enough results

Fixed in https://github.com/CityofEdmonton/text_depot/pull/10


Add click popup for clipboard links on downloads page

If you click on links in the Copy link column on the downloads page, you'll get a little popup indicating that the link has been coped to the clipboard.

I can remember when it used to only take a couple lines of code to put up a message. 4k of js seems a bit heavy.. just sayin.

@mikebrow True, but I unfortunately don't have the bandwidth for that. You're welcome to take a crack at it, though 😄

@mikebrow True, but I unfortunately don't have the bandwidth for that. You're welcome to take a crack at it, though 😄

fair enough :-) let's merge this and I'll put it on my stack of to dos

@mikebrow Sounds good to me!

@mikebrow:
| fair enough :-) let's merge this and I'll put it on my stack of to dos
no, just no. 👴 you and I and our hand-crafted HTML/CSS/JS was great in the 90s; we have better things to do than worry about modern Javascript framework sizes 😄


CosmWasm W3F grant submission

Milestone 1 commits to the following: the core pallet for the CosmWasm VM and the pallet supporting the following features: XCM integration, native asset support, allow calling extrinsics, verification through Fuzzing & Kani and Benchmarking. See full details including submission format, testing and requirements here
The end goal is to show production-ready contract deployment.
Milestone 2 is integrating with PolkadotJS. This milestone is also what we need for existing CosmWasm projects to deploy on Picasso. See here.

@JafarAz no dev is required for this right? just for tracking purposes?

This requires a dev familiar with pallet-cosmwasm to provide the submission.

I have not plans yet to write fuzzying and kani, I would like to do it, but not sure how it adds to delivery. As company we do not do it and it will be waste to make it in one no so critical place (tbh ibc is more critiical)

I have not plans yet to write fuzzying and kani, I would like to do it, but not sure how it adds to delivery. As company we do not do it and it will be waste to make it in one no so critical place (tbh ibc is more critiical)

What alternative verification can we provide instead of Fuzzing & Kani?

@dzmitry-lahoda ignore milestone 2, Kostya is working on some FE packages with Pyramation.
In terms of milestone 1:

This milestone includes the pallet supporting the following features: XCM integration, native asset support, allow calling extrinsics, verification through Fuzzing & Kani and Benchmarking.

A local network setup running a substrate chain with the pallet and a contract showing the functionality described in the milestones, so that it can be inspected and called through Polkadotjs.org.

We'll try to amend the milestone in regards to Fuzzing and Kani, is there anything else from the above that is not ready?

10a yes
10b yes
10c depends, any rust can run cargo tests. what guide? yes
10d yes
1a yes
1b xcm - no, depends, can do 1b exteinics. so no examples in codebase.
1b native assets - partial (precompiles were never done, so bank module works), kind of yes, depends
1b extriniscs - yes, via precompiles, not - not as in ink calling abitrary extrinsics, yes - one can code precompile to call any extinics. so depends
1b fuzzy/kani - good to have, but there are so many productions things, so fuck it.
1b benchamrking - yes
1c yes
20a yes
20b - kind of yes
20c - kind of yes
20d - yes
20e - ??????? i guess yes
21 - depends kind of yes. can query binary blobs, must need to query easy decodable blocks tbh,  can interact, it kind of works. so kind of yes, depends.

Can we do Fuzzing and Kani over a simple example? Like a simple ping pong test?
CC @blasrodri

cc @0xBrainjar2

Would there be an interface to interact with XCM from CW? That's probably enough

probably sending XCM transfers from CW would be enough. how shallow are grant reviewers? i mean it can suffice checkmark for calling extrincis and XCM integration, or may not.

so to finalize, can tru add simole xcm precompile for xcm transfer and simple kani/fuzzy tests, i guess to cosmwasm vm repo.


pidginPackages: re-add recurseIntoAttrs

Description of changes
I erroneously removed this in 3abc5f7093e5849eccc7e1ab82a48861c4ac4489 (part of PR https://github.com/NixOS/nixpkgs/pull/323867).
https://hydra.nixos.org/eval/1807900?compare=1807880#tabs-removed
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] Fits CONTRIBUTING.md.

Looks good. (but why not wait for ofborg eval)

It now passed 🎉

@vcunat I'm just on my phone right now, but from what I can see, ofborg did succeed in the original PR. The problem here seems to have not been an eval failure, but rather the accidental removal of some Hydra jobs (see PR description)

I didn't mean to imply there was any eval failure.

@vcunat Ah I see, I misunderstood your comment, all good!


Error message disappears in about 5 seconds

Error message on top of the screen disappears in about 5 seconds, it will be hard to read if message is long.

Does it make sense to have an error timeout at all? It's a call-to-action we want the user to see and respond to. We also probably want them to manually dismiss it.

I'm going to bump this to 30s for now.


Feature request: PPID for Windows

Seems like Parent PID is not supported in Windows.
It could be added using this command:
wmic process get processid,parentprocessid

Please ask if you need PR.

Hi @aecz sorry for the late reply.
It will be awesome if you can send a PR : )

Supported by this https://github.com/neekey/ps/pull/34


Celestine aura base size doesn't change

Describe the bug
When attempting to change the base size for auras (with numpad 6 & 7) for the Celestine model, the following error occurs:
Error in Script (6/6 Celestine - d2c6b0) function : chunk_3:(576,2-23): table index is nil
Expected behavior
For the base size on the aura to change as with other models.
Upload the Roster
just celestine.zip

Is this still an issue for you?

No, it seems to have been fixed


Research best chart library

Suggest React Chart: https://react-charts.js.org/

Using Column Chart
Bubble Chart?

This site doesn't exist, please fix.

Fixed https://github.com/reactchartjs/react-chartjs-2

https://github.com/apexcharts/react-apexcharts


NVM downgrades node (v8.7.0), but npm not downgrading to correct compatible version (v5.4.2).

Operating system and version:
macOS 10.13.6
nvm debug output:

nvm --version: v0.38.0
$TERM_PROGRAM: Apple_Terminal
$SHELL: /bin/bash
$SHLVL: 1
whoami: ''
${HOME}: /Users/
${NVM_DIR}: '${HOME}/.nvm'
${PATH}: /usr/local/opt/mysql@5.7/bin:${NVM_DIR}/versions/node/v8.7.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/Cellar/mysql@5.7/5.7.23/bin/:${HOME}/.npm-global/bin
$PREFIX: ''
${NPM_CONFIG_PREFIX}: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin17)'
uname -a: 'Darwin 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64'
checksum binary: 'shasum'
OS version: Mac 10.13.6 17G65
curl: /usr/bin/curl, curl 7.54.0 (x86_64-apple-darwin17.0) libcurl/7.54.0 LibreSSL/2.0.20 zlib/1.2.11 nghttp2/1.24.0
wget: not found
sed: /usr/bin/sed
cut: /usr/bin/cut
basename: /usr/bin/basename
rm: /bin/rm
mkdir: /bin/mkdir
xargs: /usr/bin/xargs
git: /usr/bin/git, git version 2.17.2 (Apple Git-113)
grep: /usr/bin/grep, grep (BSD grep) 2.5.1-FreeBSD
awk: /usr/bin/awk, awk version 20070501
nvm current: v8.7.0
which node: ${NVM_DIR}/versions/node/v8.7.0/bin/node
which iojs:
which npm: ${NVM_DIR}/versions/node/v8.7.0/bin/npm
npm config get prefix: npm WARN npm npm does not support Node.js v8.7.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm You can find the latest version at https://nodejs.org/
${NVM_DIR}/versions/node/v8.7.0
npm root -g: npm WARN npm npm does not support Node.js v8.7.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm You can find the latest version at https://nodejs.org/
${NVM_DIR}/versions/node/v8.7.0/lib/node_modules

nvm ls output:

         v6.0.0
         v6.1.0
        v7.10.0
->       v8.7.0
        v8.10.0
        v9.10.0
       v10.13.0
       v11.12.0
       v12.12.0
       v13.11.0
       v14.15.1
       v14.17.5
        v15.5.1
         system
default -> 8.7.0 (-> v8.7.0)
iojs -> N/A (default)
unstable -> N/A (default)
node -> stable (-> v15.5.1) (default)
stable -> 15.5 (-> v15.5.1) (default)
lts/* -> lts/fermium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.6 (-> N/A)
lts/fermium -> v14.17.6 (-> N/A)

How did you install nvm?

Install script
What steps did you perform?
Trying to run an old app that needs to use<EMAIL_ADDRESS>and<EMAIL_ADDRESS>nvm use 8.7.0
What happened?
The node version downgrades to 8.7.0, but the npm version only downgrades to
7.23.0. Any further action with npm outputs error:
npm does not support Node.js v8.7.0 npm WARN npm You should probably upgrade to a newer version of node as we npm WARN npm can't make any promises that npm will work with this version
What did you expect to happen?
I've run this before, and nvm will downgrade to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Honestly, not sure what changed.
Is there anything in any of your profile files that modifies the PATH?

Solved this by going to the nvm node installed versions directory, and manually removing the 8.7.0 version. Did nvm install 8.7.0, and it worked.
cd ~/.nvm/versions/node

I'm pretty confused how this was an issue in the first place - maybe you have a global node/npm, and this was what was being used?

I have no idea how I came to that point either, but I had upgraded and downgraded many times before when switching between projects. It appears at least one other person has come across the same issue, too:
https://stackoverflow.com/questions/62606120/node-installs-with-the-wrong-version-of-npm


Adding region value into Gauge charts

At the moment the region value is set to 4.6 in all gauge charts. Add code so correct region value automatically pulls through,

Added code in the anneka_development branch which pulls the regional value from the data.


feat: alternate payment method

We revisited the naming decision of the feature because the current name "alternate payment method" doesn't provide the necessary background to understand what it is. we (pubudu, stefan, rebecca) agreed to call the different payment methods applied to a project active and substitute payment method.


spatial consideration: ST_INTERSECTION() vs ST_INTERSECTS()

Hi @geocoug,
To tabulate spatial data wrt area of interest (aoi) drawn, we're currently using ST_INTERSECTS(), which returns the entire features from the dataset, whereas ST_INTERSECTION() would return just the spatial intersection of aoi with the dataset.
This would be especially relevant to datasets in which we summarize data within based on area, like cetacean-pacific-summer Fin Whale, Pacific Summer Density;Humpback Whale, Pacific Summer Density;Sperm Whale, Pacific Summer Density;Blue Whale, Pacific Summer Density in spatial | marineenergy.app - Google Sheets.
functions.R: tabulate_dataset_shp_within_aoi():
if (!is.na(ds$summarize_sql)){
    x_df <- dbGetQuery(
      con,
      glue("
        with
          tmp_selarea as (
            select ST_BUFFER({aoi_sql}, {ds$buffer_nm}) as geom ),
          tmp_aoi as (
            {ds$select_sql} as ds
            inner join tmp_selarea on ST_INTERSECTS(ds.geometry, tmp_selarea.geom) )
         {ds$summarize_sql}
         "))
  } else {
    x_sf <- st_read(
      con, query = glue("
        with
          tmp_selarea as (
            select ST_BUFFER({aoi_sql}, {ds$buffer_nm} * 1852) as geom)
          {ds$select_sql} as ds
          inner join tmp_selarea on ST_INTERSECTS(ds.geometry, tmp_selarea.geom )
          "))

Would want an area-weighted avg.


disable irc notifications for shippable and travis

They are pretty spammy. If no objections, I'd like to get rid of them. We would still have kubot notifications.

+1

I say we just merge this and people can readd it if they notice and don't like it :)

SGTM.
ccing @thockin @lavalamp incase they disagree.
also @vishh the current oncall as fyi.

Could we make the notifications only fire when head starts failing/is fixed? I agree it's not useful for every random PR.

Can we instead have a separate IRC channel and redirect all the bot messages to that channel?

Posting on failures also sounds like a good alternative.

Can we post only on error?
On Thu, Jul 23, 2015 at 4:52 PM, Vish Kannan<EMAIL_ADDRESS>wrote:

Posting on failures also sounds like a good alternative.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/11770#issuecomment-124271562
.

for shippable on_success and on_failure are not yet confiurable: http://docs.shippable.com/yml_reference/#irc-notifications
travis doesn't do much but I reenable notifications when we change to failing.

Shippable notifications are the ones we care about as of now. I would recommend not getting rid of it since it helps catch PRs that breaks HEAD quickly.

Also a number of people enable shippable/travis to build there local changes and #google-containers gets notifications from forked repos as well. It's not great signal for me and seems spammy in a channel that is used pretty much only for support. If other people get good signal from it then we should leave it but I think we should consider moving ci build notifications into a dev-notification channel.

Why not report to a different channel and tell oncall to sit on both?
On Thu, Jul 23, 2015 at 5:20 PM, Mike Danese<EMAIL_ADDRESS>wrote:

Closed #11770
https://github.com/GoogleCloudPlatform/kubernetes/pull/11770.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/11770#event-363976976
.

Yeah, reporting to a different channel seems good.

Ok moving all ci notifications to #kubernetes-dev

SGTM
On Thu, Jul 23, 2015 at 5:33 PM, Mike Danese<EMAIL_ADDRESS>wrote:

Ok moving all ci notifications to #kubernetes-dev
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/11770#issuecomment-124278082
.

+1 for moving to #kubernetes-dev
On Thu, Jul 23, 2015 at 5:39 PM, Tim Hockin<EMAIL_ADDRESS>wrote:

SGTM
On Thu, Jul 23, 2015 at 5:33 PM, Mike Danese<EMAIL_ADDRESS>wrote:

Ok moving all ci notifications to #kubernetes-dev
—
Reply to this email directly or view it on GitHub
<
https://github.com/GoogleCloudPlatform/kubernetes/pull/11770#issuecomment-124278082
.

—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/11770#issuecomment-124279433
.

We should update the wiki to reflect this change.


add tree-for-react demo commit,jquery

i import tree-for-react
add tree-for-react demo commit,but it depend on query .and it seems that "expose-loader for web pack” can resolve this problem.
but i do’t know where and how to add this require,does Preact support this mechanism
when i access http://<IP_ADDRESS>:8080/ ,the console display:
.....
bundle.js:784 ReferenceError: jQuery is not defined
at eval (jquery.ztree.all.js?28c8:1822)
at Object.../node_modules/ztree/js/jquery.ztree.all.js (route-home.chunk.2fdf7.js:1502)
at webpack_require (bundle.js:689)
at fn (bundle.js:110)
at eval (ztree-for-react.js?5696:17)
at Object.../node_modules/ztree-for-react/lib/ztree-for-react.js (route-home.chunk.2fdf7.js:1495)
at webpack_require (bundle.js:689)
at fn (bundle.js:110)
at eval (index.js:4)
at Object../components/ztree/index.js (route-home.chunk.2fdf7.js:1533)
webpack_require.oe @ bundle.js:784
Promise rejected (async)
load @ index.js?80af:7
Async @ async.js?e133:11
createComponent @ preact.js?10a9:220
renderComponent @ preact.js?10a9:279
setComponentProps @ preact.js?10a9:252
buildComponentFromVNode @ preact.js?10a9:338
idiff @ preact.js?10a9:136
innerDiffNode @ preact.js?10a9:178
idiff @ preact.js?10a9:154
diff @ preact.js?10a9:111
renderComponent @ preact.js?10a9:292
setComponentProps @ preact.js?10a9:252
buildComponentFromVNode @ preact.js?10a9:338
idiff @ preact.js?10a9:136
diff @ preact.js?10a9:111
render @ preact.js?10a9:370
init @ entry.js?44aa:20
(anonymous) @ entry.js?44aa:25
../../../.nvm/versions/node/v7.7.4/lib/node_modules/preact-cli/lib/lib/entry.js @ bundle.js:807
webpack_require @ bundle.js:689
fn @ bundle.js:110
0 @ bundle.js:1590
webpack_require @ bundle.js:689
(anonymous) @ bundle.js:790
(anonymous) @ bundle.js:793
jquery.ztree.all.js?28c8:1822 Uncaught (in promise) ReferenceError: jQuery is not defined
at eval (jquery.ztree.all.js?28c8:1822)
at Object.../node_modules/ztree/js/jquery.ztree.all.js (route-home.chunk.2fdf7.js:1502)
at webpack_require (bundle.js:689)
at fn (bundle.js:110)
at eval (ztree-for-react.js?5696:17)
at Object.../node_modules/ztree-for-react/lib/ztree-for-react.js (route-home.chunk.2fdf7.js:1495)
at webpack_require (bundle.js:689)
at fn (bundle.js:110)
at eval (index.js:4)
at Object../components/ztree/index.js (route-home.chunk.2fdf7.js:1533)
.....

/Users/qk/myosgit/equipment/node_modules/ztree-for-react
➜  ztree-for-react git:(master) ✗ npm install
when install success in the abover project.

it seems that i did't load correct the jQuery lib location

Hello,
This doesn't have anything to do with Preact, it's more of a Webpack question.


[WIP] Feature - pagemenu home ui

Github Issue URL/Tags (required)
What's this PR do? Please give a technical summary (required)

[] page menu

Any references (stackoverflow …) (optional)

:+1: There are no linter violations.


Database Refactoring

The changes proposed in this PR are:

Making KeyedImportExport non-abstract such that a table is created on the DB.
Renaming:
KeyedImportExport --> IOContent
ImportExportAcitivity --> Activity

Requires extended functionality for the migration.builder API coming from the platform. It will be addressed on a separate PR / issue on the board.


fatal: Could not read from remote repository.

I set up a new gogs install.

Configured nginx reverse proxy from myhost to myhost:3000

Created a user

Made a repo

Generated an ssh key

Added the ssh key to gogs

I can see that it's the only key in /home/gogs/.ssh/authorized_keys

I can clone the repo from its http URL

I can do successfully ssh -T gogs@myhost

But when I try to clone it from its ssh URL, I get
$ git clone gogs@myhost:bon/testrepo.git
Cloning into 'testrepo'...
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
$

The config file app.ini has
[repository]
ROOT = /srv/gogs/repo
SCRIPT_TYPE = bash

I can see that /srv/gogs/repo/bon/testrepo.git exists and that the whole
/srv/gogs tree is owned by gogs.

Any ideas what's happening here?

Hi there,
I rushed yesterday in the same problem and was able to solve it.
The ssh-user needs a shell.
So something like
gogs:x:994:994:gogs daemon users:/home/gogs:/bin/false

doesn't work.
But
gogs:x:994:994:gogs daemon users:/home/gogs:/bin/sh

works for me.
Hope that helps.

@Stormwind Thanks, I will include the hint into the AUR packages in the next days.

It won't work, as it can't find the config file..
Btw: You said earlier that you will implement this, so it should be implemented now?
"@klausenbusk: Ok, in the next version of the AUR gogs package I add the chsh gogs -s /usr/bin/bash to the pre_install. This will be execute for the install and upgrade process."

Den 16/01/2015 kl. 16.20 skrev Thomas Fanninger<EMAIL_ADDRESS>@Stormwind Thanks, I will include the hint into the AUR packages in the next days.
—
Reply to this email directly or view it on GitHub.

@klausenbusk I add it add the moment only at the git-dev version. I updated now in the git and the release version.

Please follow on https://github.com/gogits/gogs/pull/905 for updates.


Task: RBAC Model Design

Story: #2694
Description
Define the structure of the RBAC model including roles, permissions, and hierarchical scopes, establishing relationships between them.
Determine the parent-child relationships between scopes within the hierarchy.

Make sure that the RBAC structure is flexible enough to adapt to future changes, and robust enough to handle complex structures.

Regular Markdown here.

@TLeoDev please review your previous comments regarding our internal discussions about the actions and access control managements

Roles

Description: Collections of actions that define specific permissions.
Implementation: The Role class includes a Name and a list of Actions.

Access Control

Description: Associates roles with specific hierarchical scopes, defining where the permissions of a role are applicable.
Implementation: The AccessControl class links a Role to a Scope (a string representing the hierarchical path).

Users and Groups

Description: Users are associated with access controls, which define their permissions within various scopes. Groups also have access controls that apply to all their members.
Implementation:

The User class includes Name and a list of AccessControls.
The Group class contains Name, a list of Members, and AccessControls.

Hierarchical Scopes

Concept: Represent hierarchical paths in the system (e.g., "Client/CompanyX/ProductionA/devices/deviceId").
Parent-Child Relationships: Higher-level (parent) scopes include the permissions of their lower-level (child) scopes. For exemple : “Client/CompanyX/Product/devices/*” is the parent of the child “Client/CompanyX/Product/devices/deviceID”
Scope Management: Handled through an interface for creating, modifying, and deleting scope paths.

Examples

User Permissions: A user's permissions are determined by their AccessControls, each linking a role to a specific scope.
Group Permissions: Groups have AccessControls that provide role-based permissions within specific scopes for all group members.

Conclusion
This RBAC model is structured to provide secure and flexible permission management across different hierarchical scopes. It allows for the dynamic assignment of roles within specific scopes to users and groups, aligning with our system's needs.

This documentation is intended for development purposes, explaining the RBAC model as defined in Story #2694.


add topics

I suggest adding topics such as chatgpt, chatgpt4 in the About section at https://github.com/paul-gauthier/aider

Great suggestion. Done.


Run gofmt

Produced via: gofmt -s -w $(find -name '*.go' | grep -v vendor)

/assign @bobcatfish

/assign @bobcatfish
/ok-to-test

how do we get this sockpuppet to get involved before the merge happens
/lgtm
/approve


Enhanced Movie Recommendation System with 90%+ Accuracy and Scalable Dataset Integration

🎉 Project-Guidance Contribution! 🎈
🎯 Have you reviewed the Contributing Guidelines?

[x] YES
[ ] NO

📝 Description
I have upgraded the Movie Recommendation System code to achieve over 90% accuracy while retaining all existing features.
The improvements are organized in a newly created folder:
Machine Learning and Data Science/Basic/Movie Recommendation System/upgraded movie recommendation system.
This ensures the original system remains untouched, and the enhanced version is easily accessible.
Key updates include:

Improved algorithms and methods for recommendation accuracy.
Uploaded a new dataset containing 5,000 movies, which is used in the updated code.
Added proof of accuracy in the final cell of the code to demonstrate results.

🚀 Upcoming Features
I plan to deploy this system on a live website in the future to make it more accessible.

🔧 Fixes #1633
This contribution addresses issue #1633 by enhancing the Movie Recommendation System to improve scalability and accuracy for larger datasets.

🏷 Initiative Participation (Required)
This pull request aligns with the following initiative:

[ ] 🌸 GSSoC (Girl Script Summer of Code)
[ ] 🌼 GSSoC 2024 Extd.
[ ] 🍂 Hacktoberfest 2024
[ ] ❄ Script Winter of Code (SWoC)
[ ] ⛄ Winter of Blockchain (WoB)
[ ] 🙋♂ Personal
[x] 📌 Other: This repository was introduced via GSSoC, but this is now a peer-to-peer contribution for personal learning and growth.

📊 Proof of Accuracy and Code
I’ve attached a visual proof of the achieved accuracy. The results demonstrate improved performance, particularly on larger datasets:

Hi @Kushal997-das,
Could you please review this pull request when you get a moment? Once you’ve reviewed it, I’d appreciate it if you could merge it.


Delete useless blank lines and backporting the code and it's test files to python 2

1- Update the script to remove useless empty lines:
Some VTT files are downloaded from sites like YouTube and other sites like Udemy, some of those files have many empty lines that have no use and there is no data in them, such as captions, time stamps, or identifiers, this commit will remove those blank lines.
I have attached some sample files for testing.
sample files.zip
2- Backporint the script to Python 2 :
I know that there is a Python 2 version in https://github.com/jansenicus/vtt-to-srt.py but it's 4 years old and many of the functions that have been added to the program are not in there so I backport the vtt_to_srt file to python 2 so that if anyone still uses python 2 can benefit from it.
also, I backport the test files so they can be used with Python 2 but the last version of pytest library that can be used in this case is version  4.6.11 because it's the last version from pytest that still supports Python 2.

Hi @KarimReefat
I created a fork of this project to have a version for python2, if possible I could open the pull request there. This makes it easier to manage, and does not create problems when packaging.

Hi @KarimReefat
I created a fork of this project to have a version for python2, if possible I could open the pull request there. This makes it easier to manage, and does not create problems when packaging.
https://github.com/jsonzilla/vtt_to_srt2

I already make a pull request with the changes in the new Rebo.

I created a separate repository at https://github.com/jsonzilla/vtt_to_srt2 with this pull request. Thanks, @KarimReefat, for this initiative!


BDMA: request stop after busy loop in blocking_wait()

Otherwise the channel cannot be used again, since CR.EN remains set and the DMA channel registers are read-only while it is set.

I can confirm that it does not work with the current implementation and this PR fixes it on my STM32L432KC


Nicer app icon screen

https://github.com/user-attachments/assets/b3d770b9-d31f-48e5-b2c6-1ebc5a6ce0d2

that's our lightest shade (contrast_25). maybe we need a contrast_10
yeah on iOS that's the system API giving that notification. Kinda silly

One change I made:

Before
After

50px was entirely arbitrary, no particular reason or significance


Breaking change introduced in 2.6.0

The @keyv/redis version 2.6.0 introduced a breaking change in its constructor:
2.5.8:
if ((uri.options && uri.options.family) || (uri.options && uri.isCluster)) {

2.6.0:
if (uri instanceof Redis) {

Here's how to reproduce it:
import KeyvRedis from '@keyv/redis';
import { Cluster } from 'ioredis';

const cluster = new Cluster([{ host: 'remote-redis-host' }], {
  scaleReads: 'all'
});

const keyvRedis = new KeyvRedis(cluster);

@diogoazevedos looks like the unit test is missing the family option. can you draft up a unit test to handle it and get 100% code coverage?

Working on a pull request here https://github.com/jaredwray/keyv/pull/836

Fixed. https://app.codecov.io/gh/jaredwray/keyv/tree/main/packages%2Fredis


schema: remove uri-confirmance for autoupdate urls

So myself and @Calinou have come across a package here https://github.com/Calinou/scoop-games/pull/108 that should technically be correct, but fails the schema validation.  The package in question extracts the complete autoupdate URL from the page text, and thus the value is just a regex match, which doesn't resemble a URL.  We have come to the conclusion this is a problem with the schema which can be fixed like so.  Unfortunately this makes it slightly less rigorous but I think it's necessary unless support for checkver regex matches is removed from the autoupdate URLs which would be a bad idea.

Oh, that's a much better solution @Ash258 .  I was worried that the mirror might be geo-located based on your source IP but I just visited from an EU IP and got the same link.  I'll use that instead, thanks!


Meeting Room Standard licensing

This article should update the Meeting Room license to "Meeting Room Standard" license - as there was a name change to the SKU in recent months. There may also be a need to include the "Meeting Room Premium" license which is the Standard license with additional Managed Services for the room devices.

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

ID: a2070d20-21d1-c8bb-bbb4-697083efcd20
Version Independent ID: f4998e3c-74ed-4a2b-fe7c-c55044b9a6b4
Content: Microsoft Teams Rooms licenses - Microsoft Teams
Content Source: Teams/rooms/rooms-licensing.md
Service: skype-for-business-online
GitHub Login: @dstrome
Microsoft Alias: dstrome

@NickElniff Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@NickElniff Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@NickElniff thank you for pointing this out and helping improve Microsoft Docs. Please can you clarify which section of the article needs to be updated and I'll look into it.

@NickElniff thank you for pointing this out and helping improve Microsoft Docs. Please can you clarify which section of the article needs to be updated and I'll look into it.

The Meeting Room license has been renamed and we now have 2 flavors of the Teams Room License (Standard and Premium)
As seen in this blog post from this past summer - Great meeting room experiences: Meet the new Microsoft Teams Rooms Standard and Premium - Microsoft 365 Bloghttps://www.microsoft.com/en-us/microsoft-365/blog/2020/07/21/microsoft-teams-meetings-hybrid-workplace-options/
Nick Elniff
Teams TS
nielniff<EMAIL_ADDRESS>Teams:<PHONE_NUMBER>
My Calendar<EMAIL_ADDRESS>From: Lindsay<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 3:10 AM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness<EMAIL_ADDRESS>Cc: Nick Elniff<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Meeting Room Standard licensing (#6528)
@NickElniffhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNickElniff&data=04|01|nielniff%40microsoft.com|0a10192554d1485acec308d8bdec660c|72f988bf86f141af91ab2d7cd011db47|1|0|637468170308560340|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=rgBJlX8jWI%2B468Lj%2FQKfeHazY9OeqKdTpWY8LrzbpvU%3D&reserved=0 thank you for pointing this out and helping improve Microsoft Docs. Please can you clarify which section of the article needs to be updated and I'll look into it.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SkypeForBusiness%2Fissues%2F6528%23issuecomment-764492014&data=04|01|nielniff%40microsoft.com|0a10192554d1485acec308d8bdec660c|72f988bf86f141af91ab2d7cd011db47|1|0|637468170308570302|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=KlN%2B2n4Cndcn%2Fz7C1HJBh4JcVKVqKLRa62Jm2Kjpvoc%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJNU5HQGD5YF2IO72ALJ2T3S27VQLANCNFSM4WLFMOWQ&data=04|01|nielniff%40microsoft.com|0a10192554d1485acec308d8bdec660c|72f988bf86f141af91ab2d7cd011db47|1|0|637468170308570302|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3tgbnqGZjCPuSbYg%2FKN1mYTTgbhgPFTQ36umxPl2czs%3D&reserved=0.

The Meeting Room license has been renamed and we now have 2 flavors of the Teams Room License (Standard and Premium)
As seen in this blog post from this past summer - Great meeting room experiences: Meet the new Microsoft Teams Rooms Standard and Premium - Microsoft 365 Bloghttps://www.microsoft.com/en-us/microsoft-365/blog/2020/07/21/microsoft-teams-meetings-hybrid-workplace-options/
Nick Elniff
Teams TS
nielniff<EMAIL_ADDRESS>Teams:<PHONE_NUMBER>
My Calendar<EMAIL_ADDRESS>From: Lindsay<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 3:10 AM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness<EMAIL_ADDRESS>Cc: Nick Elniff<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Meeting Room Standard licensing (#6528)
@NickElniffhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNickElniff&data=04|01|nielniff%40microsoft.com|0a10192554d1485acec308d8bdec660c|72f988bf86f141af91ab2d7cd011db47|1|0|637468170308560340|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=rgBJlX8jWI%2B468Lj%2FQKfeHazY9OeqKdTpWY8LrzbpvU%3D&reserved=0 thank you for pointing this out and helping improve Microsoft Docs. Please can you clarify which section of the article needs to be updated and I'll look into it.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SkypeForBusiness%2Fissues%2F6528%23issuecomment-764492014&data=04|01|nielniff%40microsoft.com|0a10192554d1485acec308d8bdec660c|72f988bf86f141af91ab2d7cd011db47|1|0|637468170308570302|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=KlN%2B2n4Cndcn%2Fz7C1HJBh4JcVKVqKLRa62Jm2Kjpvoc%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJNU5HQGD5YF2IO72ALJ2T3S27VQLANCNFSM4WLFMOWQ&data=04|01|nielniff%40microsoft.com|0a10192554d1485acec308d8bdec660c|72f988bf86f141af91ab2d7cd011db47|1|0|637468170308570302|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3tgbnqGZjCPuSbYg%2FKN1mYTTgbhgPFTQ36umxPl2czs%3D&reserved=0.

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


UI was not updated with the Array item

I defined one class like this
class P{}
Object.assign(P.prototype,{
add(){},
remove(){},
//...
})

And did as follows:
//1. include this file
//2. make an instance of the Outright let leg=new P()
//3. use the methods or properties of the instance leg.clm;leg.mockData;leg.add();leg.insert();leg.remove();leg.change;//...

If you are still having an issue, could you please follow the instructions in https://github.com/Polymer/polymer/blob/master/CONTRIBUTING.md#filing-bugs and re-open using the issue template with proper live reproduction steps (e.g. jsBin showing issue)?  Thank you.