node-sass dependency breaks previously working sass

Hi, after a recent dependency clean and re-install I ran into this:
Error in plugin 'sass'
Message:
    path/to/some/style.sass
Error: You may not @extend an outer selector from within @media.
       You may only @extend selectors within the same directive.

This started happening, I noticed, because of gulp-sass now pulling<EMAIL_ADDRESS>and that breaks the parsing.
I also noticed #479 and saw a common pattern here.
I think this is due to the fact that dependencies aren't pinned; which usually at some point cause stuff like this. If I manually install<EMAIL_ADDRESS>it does work, but it will still break any automated build mechanism.
May I suggest you pinned your dependencies?
If you want to keep patches coming in without manually updating your deps, you may always use tilde ranges or X ranges instead of caret ranges.

Have you confirmed your Sass code is valid and compiles with the official
Sass compiler?
This error is likely due to your Sass being in invalid. More information in
https://medium.com/@xzyfer/why-node-sass-broke-your-code-and-semver-1b3e409c57b9
We will not pin our dependencies.
On 27 Apr 2016 4:21 AM, "Guido Vilariño"<EMAIL_ADDRESS>wrote:

Hi, after a recent dependency clean and re-install I ran into this:
Error in plugin 'sass'
Message:
path/to/some/style.sass
Error: You may not @extend an outer selector from within @media.
You may only @extend selectors within the same directive.
This started happening, I noticed, because of gulp-sass now pulling
<EMAIL_ADDRESS>and that breaks the parsing.
I think this is due to the fact that dependencies aren't pinned; which
usually at some point cause stuff like this. If I manually install
<EMAIL_ADDRESS>it does work, but it will still break any automated build
mechanism.
May I suggest you pinned your dependencies?
If you want to keep patches coming in without manually updating your deps,
you may always use tilde ranges
https://docs.npmjs.com/misc/semver#tilde-ranges-123-12-1 or X ranges
https://docs.npmjs.com/misc/semver#x-ranges-12x-1x-12- instead of caret
ranges https://docs.npmjs.com/misc/semver#caret-ranges-123-025-004.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/dlmanning/gulp-sass/issues/480

Will reopen this issue when you confirm the error is not caused by invalid code.

I can confirm that downgrading to<EMAIL_ADDRESS>makes it work, but I hadn't read that article before (thanks).
I'll double-check and confirm (or take back) my initial bug report.

@xzyfer, we double-checked our code and fixed them; the error went away.


liburing.h: Prevent unwanted addr 32bit truncations.

The addr field is used by several operations to match against a previous user_data field. Using void * for the io_uring_prep_rw parameter type causes undesired 32bit truncation when building the library for 32bit architecture and may fail to match a previously set 64bit user_data.
I think something like that should be done to fix https://github.com/axboe/liburing/issues/490

This is sure to trigger a bunch of warnings on compile now, for both 32-bit and 64-bit. Did you compile it?
Also please make sure to include a Signed-off-by line at the end of the commit, with your real name and email.

I did, but I think I have it compiled already and the tests don't have a dependency on the header, so they were not recompiled and I missed the warnings there.

My main worry here is not so much the tests, as they are under liburing and we can just fix them up, it's more applications currently using liburing and now throwing potentially a bunch of warnings when the library is updated. Need to ponder what the best approach is here.

Well, I understand the worry but I don't really see any good way to fix it. A good number of functions are just entirely unusable with 32bit pointers, and even worse, they will silently accept the parameters but not operate as expected.
The only other sane solution would be to deprecate all the problematic entry points to make new ones, which I'm not sure is much better. As I suspect io_uring and liburing are still pretty young I'm not sure it's worth the trouble (although that's up to you).
I think the warnings are harmless in any case, as it's all going to be cast to an integer type equal or larger than the current pointer arguments, and at least people will know what to fix.

Updated with signoff, fixes for the tests and examples, as well as changing the types in io_uring_cqe_set_data / io_uring_cqe_get_data too for consistency/

as well as changing the types in io_uring_cqe_set_data / io_uring_cqe_get_data too for consistency.

Let's please not do that, that's just unnecessary breakage. For those, I'd say just add io_uring_cqe_set_data64 and ditto on the get side.

The problem is really only if you want to use 64-bit types, if used for pointers then everything works just fine on 32-bit as-is. Should it work with 64-bit? Certainly! But it's not really a huge issue, at least nobody has complained about it yet :-)

The only other sane solution would be to deprecate all the problematic entry points to make new ones, which I'm not sure is much better. As I suspect io_uring and liburing are still pretty young I'm not sure it's worth the trouble (although that's up to you).

It is quite new, but it's still got a few years on its back  by now. If used with -Werror or similar, then it will break compile. At least it's a trivial fix. I'd probably lean towards fixing them up and throwing the warnings, I do wonder if it should be accompanied with a define or similar so applications at least have a chance to compile without warnings on regardless of liburing version.
It's not that it's a hard fix, it's trivial. But it is introduced breakage, which I try to always void.

I'll probably leave it to you then, but in my opinion and with the current state of the liburing api, you should definitely break things, and probably better now rather than later when more people will be using it. It is implicitly broken already, and that needs to be made obvious so that anyone who may have missed that, gets informed.
For the same reason, I don't think you should keep the get_data / set_data helpers untouched: the sqe structure is accessible, and there's even a lot of code out there, in examples, snippets, etc, which are advertising the direct use of user_data, packing things in it because it's convenient and more efficient than using a pointer in a lot of user cases. These helpers will always be broken when used at the same time and that should be prevented.
Maybe another way of cleaning things up would be to change that user_data member, hiding it or retyping it to void * like all the rest of the code seems to assume, but you can't have a 64bit member here when operations that are referencing it only support a 32bit value. It is too slippery. Then on the other hand, like I said above, having a 64bit user_data member is convenient and pretty useful, and as the kernel supports it, it would be a shame not to expose it.

I do agree that it should get fixed, no arguments on that one. I think where we disagree somewhat is the importance of it. I suspect the wine background means the 32-bit nature means a lot more to you, it's generally not something that anyone else has run into as most folks are on 64-bit anyway. And if they are on 32-bit, then storing pointers works just fine. It's only really a potential issue if you are running 32-bit and want to use the full 64-bit user_data space.
So while I do think that this should get fixed up, it's also potential pain for 99% of the users, that currently have no issues. Which is why I'm a bit hesitant to just do a flag day change like this.
user_data is part of the kernel-user ABI and cannot be changed, and you cannot have pointers in a shared struct like that or 32 vs 64-bit compatibility would be broken anyway. That's a potentially larger issue, with 32-bit applications on 64-bit kernels.
The changes might be more palatable if broken down somewhat, like first fixing up prep_rw. I'll take a stab at it.

user_data is part of the kernel-user ABI and cannot be changed, and you cannot have pointers in a shared struct like that or 32 vs 64-bit compatibility would be broken anyway. That's a potentially larger issue, with 32-bit applications on 64-bit kernels.

Well the structure definition could be duplicated in liburing, exposing a different type for user_data for better compatibility with the way you like the library to be used, while keeping the alignment with an union or something else.
Regarding the 32bit concerns, sure, it's less of a concern these days and most people don't notice, but I'm sure liburing users include or will include libraries that are meant to be portable, and although it's becoming less likely to be used or even tested on 32bit architectures, they may still be supporting them.
Even Wine is trying to move away from running pure 32bit applications, but I don't think we're free of it yet, and not before a long time.

Can you check current -git? I tried to do the bare minimum, and I tested it with both 32-bit and 64-bit applications on a 64-bit kernel.

Looks good, thanks.


fix(release): make sure we are not on a detached branch else semantic release has issues

@rawlingsj fabric8/fabric8-ui:SNAPSHOT-PR-2224-1 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2224-fabric8-planner.badger.fabric8.io


I look for a Open source video conferencing application powered by LikeKit, something like Jitsi

Hi,
I don't know where to post my question: do you know an open source video conferencing application powered on LiveKit, like Jitsi?
My goal: replace Jitsi by, maybe a better vidéo conferencing application.
Best regards,
Stéphane

Hi!
you can either try our (rather minimalistic) example app in https://github.com/livekit/livekit-react or ask the livekit community on slack https://livekit.io/join-slack, some people there might have built open source conferencing apps on top of livekit!

This one is built using LiveKit - https://www.plugnmeet.org/


Add horovod for distributed training

Fixes https://github.com/NVIDIA-Merlin/Merlin/issues/651
Goals :soccer:

Use horovod to enable data-parallel distributed training

Implementation Details :construction:
Horovod documentation lists the following steps for enabling horovod (link):

Run hvd.init().
Pin each GPU to a single process.
Scale the learning rate by the number of workers.
Wrap the optimizer in hvd.DistributedOptimizer.
Add hvd.callbacks.BroadcastGlobalVariablesCallback(0) to broadcast initial variable states from rank 0 to all other processes.

The high-level goal/design of this PR is to perform the above steps for the user automatically behind the Models API.

hvd.init() is run in merlin/models/tf/distributed/backend.py.
We pin GPU by using examples/usecases/multi-gpu/hvd_wrapper.sh. (Note: Horovod examples recommend using tf.config.experimental.set_visible_devices() but this sometimes work, e.g., on NGC.)
Learning rates are scaled automatically both for Keras optimizers and MultiOptimizer.
If users use a Keras optimizer or MultiOptimizer, they are automatically converted to hvd.DistributedOptimizer when hvd is installed there are more than one GPUs.
hvd.callbacks.BroadcastGlobalVariablesCallback(0) is automatically added to callbacks if hvd is installed and there are more than one GPUs.

From the user's perspective, the training script itself looks identical whether the script is for a single GPU or multi-GPU. There is likely no need for the user to import the upstream horovod library at all. When they run the script normally with python, e.g.,
python -m pytest tests/unit/tf -m horovod, it will run in a single process even if they have multiple GPUs. If the user wants to use multiple GPUs, the script has to be run executed with horovodrun: horovodrun -np 2 sh hvd_wrapper.sh python -m pytest tests/unit/tf -m horovod.
Sanity checks

[ ] Does the throughput scale as we go from 1 GPU to 2 GPUs, 4 GPUs, etc.
[ ] Does the performance stay the same (or increase) as we go from 1 GPU to 2 GPUs, 4 GPUs, etc.

Future work

Can we get rid of hvd_wrapper.sh by absorbing it either into horovodrun or Models?
Can we use ray to make the API cleaner?

Testing Details :mag:
Unit tests on CPU (Github Actions, python) and on multiple GPUs (Jenkins, horovodrun).
Sanity checks listed above on NGC.

rerun tests

@marcromeyn  @edknv  I am started to develop an example and have follow up questions:

We require to initialize a separate dataloader - we do not require it in any other example. Is it required we will do it in this case?
model.fit runs each worker on the full dataset. Therefore, each epoch is 2x larger than before.

train = Dataset(ddf, schema=train.schema)

    train_loader = mm.Loader(
        train,
        schema=train.schema,
        batch_size=batch_size,
        shuffle=True,
        drop_last=True,
    )

    target_column = train.schema.select_by_tag(Tags.TARGET).column_names[0]

    model = mm.DLRMModel(
        train.schema,
        embedding_dim=16,
        bottom_block=mm.MLPBlock([32, 16]),
        top_block=mm.MLPBlock([32, 16]),
        prediction_tasks=mm.BinaryClassificationTask(target_column),
    )

    opt = tf.keras.optimizers.Adagrad(learning_rate=learning_rate)
    model.compile(optimizer=opt, run_eagerly=False, metrics=[tf.keras.metrics.AUC()])

    losses = model.fit(
        train_loader,
        batch_size=batch_size,
    )

We require to initialize a separate dataloader - we do not require it in any other example. Is it required we will do it in this case?

@bschifferer Dataloader is used here to drop the last batch, i.e., drop_last=True, so we can drop the last batch if it's not full. It's not strictly required but I think in a distributed setting it makes sense to drop the last batch which might be small.

model.fit runs each worker on the full dataset. Therefore, each epoch is Nx larger than single GPU (where N is number of GPUs).

When I test this, each worker seems to have 1/Nth steps and the epochs are shorter. On a single GPU:
Epoch 1/2
2136/2136 [==============================] - 44s 18ms/step - loss: 0.6853 - auc: 0.5708 - regularization_loss: 0.0000e+00
Epoch 2/2
2136/2136 [==============================] - 39s 18ms/step - loss: 0.6846 - auc: 0.5738 - regularization_loss: 0.0000e+00

On 2 GPUs using horovodrun -np 2:
[1,0]<stdout>:Epoch 1/2
1068/1068 [==============================] - 31s 21ms/step - loss: 0.6850 - auc: 0.5719 - regularization_loss: 0.0000e+00stdout>::
[1,0]<stdout>:Epoch 2/2
1068/1068 [==============================] - 23s 21ms/step - loss: 0.6845 - auc: 0.5739 - regularization_loss: 0.0000e+00stdout>::>:

I added an assertion for testing the step sizes in the unit tests in 6013913.

One test on Jenkins which was added very recently in https://github.com/NVIDIA-Merlin/models/pull/841 is failing. It seems like introducing horovod in the dependency caused dependency conflict with dask, causing an error somewhere in nvtabular + dask, unrelated to horovod. I see:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
feast 0.19.4 requires dask<2022.02.0,>=2021.*, but you have dask 2022.5.1 which is incompatible.

which I don't see in other CI logs. Need to resolve the dependency conflict somehow.

One test on Jenkins which was added very recently in #841 is failing. It seems like introducing horovod in the dependency or something else caused a dependency conflict with dask, causing an error somewhere in nvtabular + dask, unrelated to horovod. I see:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
feast 0.19.4 requires dask<2022.02.0,>=2021.*, but you have dask 2022.5.1 which is incompatible.

which I don't see in other CI logs. Need to resolve the dependency conflict somehow, but I can't seem to reproduce the error locally.

This not a problem as far as we have seen. Its just that the older version of feast does not know that newer versions of dask exist. It has yet to cause problems in our merlin end 2 end level testing. However it is on our radar to update that version of feast.


Made Search work in calendar mode on schedule page and indent the script

code
Fixes #1234
Changes:

Enables search function in calendar mode on the schedule page.
The script code was badly indented. Made it indent properly.

Test Server
http://secure-meadow-20680.herokuapp.com
Test Website
http://princu7.github.io/websiteTest
@aayusharora @geekyd @sumedh123 @harshitagupta30 Please review. Thanks :)

Screenshots

Before

After performing search for 'Welcome'

Good job!


Plugins, shortcodes, and priorities

two times now I've run into a situation where plugins I'm developing simply don't run until I change the initial priority value, which makes no sense. Perhaps I'm not understanding how things work? Or maybe something happened in recent updates? I just now realized that these are both shortcode plugins that extend "Shortcode Core," so maybe that's part of it?
Here's the scenario:
All my plugins start with the following:
    public static function getSubscribedEvents()
    {
        return [
            'onPluginsInitialized' => ['onPluginsInitialized', 0]
        ];
    }

Then, in the onPluginsInitialized handle, I enable whatever other events I want to listen to.
But over the weekend I spent hours trying to figure out why my plugin wasn't executing. On a total lark I changed that initial onPluginsInitialized priority to 100 and everything worked. And then just now I tested a plugin and it, too, would not execute until I changed the value to 10. After some testing, I've found that these plugins only execute if the priority is greater than 0. Negative or zero values don't work at all.
Any idea why this might be happening? Thanks!

Can you upload one sample plugin with the problem? Privately if you need, on Gitter

Grazie, flavio. The one that triggered this post was the Google Charts plugin. You'll see onPluginsInitialized is set to 10. Let me know what else you might need. I can send you the whole user folder of my dev server, but it's big :smile:

I tried adding an exit() first thing in onPluginsInitialized() and it is called correctly also with 0 priority. I didn't test the plugin functionality yet.
Can you check this simple thing?

So here's the code. If onPluginsInitialized is set to 0, then the dump("In init") does indeed run but the shortcodes don't work. If I set it to anything greater than 0, then everything works as expected.
<?php
namespace Grav\Plugin;

use Grav\Common\Plugin;
use RocketTheme\Toolbox\Event\Event;

/**
 * Class GoogleChartsPlugin
 * @package Grav\Plugin
 */
class GoogleChartsPlugin extends Plugin
{
    /**
     * @return array
     *
     * The getSubscribedEvents() gives the core a list of events
     *     that the plugin wants to listen to. The key of each
     *     array section is the event that the plugin listens to
     *     and the value (in the form of an array) contains the
     *     callable (or function) as well as the priority. The
     *     higher the number the higher the priority.
     */
    public static function getSubscribedEvents()
    {
        dump("In subscribed");
        return [
            'onPluginsInitialized' => ['onPluginsInitialized', 0]
        ];
    }

    /**
     * Initialize the plugin
     */
    public function onPluginsInitialized()
    {
        dump("In init");
        // Don't proceed if we are in the admin plugin
        if ($this->isAdmin()) {
            return;
        }

        // Enable the main event we are interested in
        $this->enable([
            'onShortcodeHandlers' => ['onShortcodeHandlers', 0]
        ]);
    }

    public function onShortcodeHandlers()
    {
        $this->grav['shortcode']->registerShortcode('GChartShortcode.php', __DIR__);
    }
}

My user folder minus the 143 MB user/pages/01.blog folder can be downloaded from my site.

Not 100% familiar with the shortcode plugin event flow. Maybe adding it in onPluginsInitialized is too late? I see Shortcode UI listening on onShortcodeHandlers directly https://github.com/getgrav/grav-plugin-shortcode-ui/blob/develop/shortcode-ui.php#L15

Plugins are now sorted with Natsort, should resolve this.


How to upgrade this latest version from hackintosh(gnodipac886)<IP_ADDRESS>

Can I just simply copy the CLOVER from the latest release of this repo instead of <IP_ADDRESS>?
And which release I need to download, the OC zip or the regular one?
What's the difference between unlocking and lock Mojave?
I don't see any guide to lead me to upgrade. I used gnodipac886's package because there is an onekey.sh can let me install easily, but I am considering upgrading.
My system version is 10.14.5 (18F132) now.
Thank you very much for helping!

Atm, Clover is not supported in this repo... you could only see a very very old and no longer maintained version!
Honestly I could not promise anything but perhaps, during Christmas holidays, I could give a try to actual Clover release, but not before...


refactor(core): plugins iterator state-building & lookup algorithm

Data structure to store plugin scope configurations
This patch set changes how the Plugins Iterator finds suitable plugin configurations for defined precedence rules.
To achieve that, we move from a nested table structure that stores various combinations of route, service and consumer to a flat hashmap.
Before.
combos[name].rsc[cfg.route_id] =
combos[name].rsc[cfg.route_id] or {}
combos[name].rsc[cfg.route_id][cfg.service_id] =
combos[name].rsc[cfg.route_id][cfg.service_id] or {}
combos[name].rsc[cfg.route_id][cfg.service_id][cfg.consumer_id] = cfg

combos[name].rc[cfg.route_id] =
combos[name].rc[cfg.route_id] or {}
combos[name].rc[cfg.route_id][cfg.consumer_id] = cfg
-- and so on for all possible combinations

After:
-- Build a compound key using the route_id, service_id, and consumer_id
local compound_key = PluginsIterator.build_compound_key(route_id, service_id, consumer_id)

-- Store the plugin configuration in the 'combos' table using the compound key as index
combos[name][compound_key] = cfg

The build_compound_key function concatenates the ids of scoped entity to generate a unique index.
Lookup algorithm
The change to the data structure allows us to move away from the concept of combo_keys to an index based lookup.
Before:
if route_id and service_id and consumer_id and combos[COMBO_RSC]
  and combos.rsc[route_id] and combos.rsc[route_id][service_id]
  and combos.rsc[route_id][service_id][consumer_id]
then
  return combos.rsc[route_id][service_id][consumer_id]
end

After:
if route_id and service_id and consumer_id then
  key = build_compound_key(route_id, service_id, consumer_id)
  if combos[key] then
    return combos[key]
  end
end

Aligning db-less and db modes
This patch also streamlines the way these different modes handle configuration retrieval.
In traditional mode, we stored a placeholder value of true in the lookup tables to indicate that a configuration is in fact present. This would trigger a cache retrieval with transparent database lookup in case of a cache-miss.
In db-less mode, we saved the entire configuration alongside the lookup table. This reduces the lookup-time by avoiding potentially costly detours to the database, as well as the extra function call to cache
The obvious drawbacks are an increased memory footprint for traditional mode as we're saving configuration data alongside the lookup table.
In db-less mode, the memory footprint should be slightly reduced due to a more efficient/predictable table structure.
This change also allows to drop cache-warmups during Plugins Iterator rebuilds, which speeds rebuild times in traditional mode.
Past caching behavior in Traditional mode
In the past, we utilized kong.cache in traditional mode. When there was a change in the configuration of a plugin, route, service, or consumer Kong would invalidate the core, plugins, and the plugin iterator's cache. Consequently, this would initiate a rebuild process for the plugin iterator.
Whenever a new request was initiated, and the iterator had not completed its rebuild process, the request would bypass the cache and would pull the updated plugin directly from the database.
This approach must not necessarily pose problems, but the information obtained by a plugin is not bound to the state of the plugin iterator. As a result, the system ends up retrieving a prematurely updated plugin.
To resolve this, our latest implementation bypasses cache usage, opting instead to store all data directly in memory. This change guarantees a sealed system operation and facilitates atomic rebuilds, accurately reflecting the behavior we experience in hybrid mode. This is a more efficient and reliable approach, ensuring that plugins have access to the appropriate, timely data, thereby avoiding the earlier stated issue.
Tests
Tests to support the validity of this change are here:
kong/spec/02-integration/15-plugins-iterator
https://konghq.atlassian.net/browse/KAG-1882

@jschmid1 Interesting! I recall these functions have had many variations over the years... The reasoning for the nested combos structure in the past was that it allowed for the lookup algorithm to fetch the configuration for the request without performing string allocations. Did you notice any perf changes in the happy path by building these compound keys? Just spotted this commit randomly and got curious at where the memory allocations vs table lookups balance ended up!


spyder requires qtconsole >= 5.0.3, but highest version available in conda is 5.0.2

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[x] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[x] Reset preferences with spyder --reset
[x] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
Upon startup, the following error message appears:
You have missing dependencies!
Mandatory:
qtconsole >=5.0.3 : 5.0.2 (NOK)
Please install them to avoid this message.
Note: Spyder could work without some of these dependencies, however to have a smooth experience when using Spyder we strongly recommend you to install all the listed missing dependencies.
Failing to install these dependencies might result in bugs. Please be sure that any found bugs are not the direct result of missing dependencies, prior to reporting a new issue.
Versions
* Spyder version: 4.2.4
* Python version: 3.9.2 64-bit
* Qt version: 5.9.7
* PyQt version: 5.9.2
* Operating System name/version: Linux 4.15.0-122-generic

Dependencies

# Mandatory:
atomicwrites >=1.2.0            :  1.4.0 (OK)
chardet >=2.0.0                 :  4.0.0 (OK)
cloudpickle >=0.5.0             :  1.6.0 (OK)
diff_match_patch >=20181111     :  20200713 (OK)
intervaltree >=3.0.2            :  3.1.0 (OK)
IPython >=7.6.0                 :  7.21.0 (OK)
jedi =0.17.2                    :  0.17.2 (OK)
jsonschema >=3.2.0              :  3.2.0 (OK)
keyring >=17.0.0                :  22.3.0 (OK)
nbconvert >=4.0                 :  6.0.7 (OK)
numpydoc >=0.6.0                :  1.1.0 (OK)
parso =0.7.0                    :  0.7.0 (OK)
pexpect >=4.4.0                 :  4.8.0 (OK)
pickleshare >=0.4               :  0.7.5 (OK)
psutil >=5.3                    :  5.8.0 (OK)
pygments >=2.0                  :  2.8.1 (OK)
pylint >=1.0                    :  2.7.2 (OK)
pyls >=0.36.2;<1.0.0            :  0.36.2 (OK)
pyls_black >=0.4.6              :  0.4.6 (OK)
pyls_spyder >=0.3.2             :  0.3.2 (OK)
qdarkstyle >=2.8;<3.0           :  2.8.1 (OK)
qtawesome >=0.5.7               :  1.0.2 (OK)
qtconsole >=5.0.3               :  5.0.2 (NOK)
qtpy >=1.5.0                    :  1.9.0 (OK)
rtree >=0.8.3                   :  0.9.4 (OK)
setuptools >=39.0.0             :  52.0.0.post20210125 (OK)
sphinx >=0.6.6                  :  3.5.3 (OK)
spyder_kernels >=1.10.2;<1.11.0 :  1.10.2 (OK)
textdistance >=4.2.0            :  4.2.1 (OK)
three_merge >=0.1.1             :  0.1.1 (OK)
watchdog >=0.10.3;<2.0.0        :  1.0.2 (OK)
xdg >=0.26                      :  0.27 (OK)
zmq >=17                        :  20.0.0 (OK)

# Optional:
cython >=0.21                   :  None (NOK)
matplotlib >=2.0.0              :  3.3.4 (OK)
numpy >=1.7                     :  1.19.2 (OK)
pandas >=1.1.1                  :  1.2.3 (OK)
scipy >=0.17.0                  :  1.6.1 (OK)
sympy >=0.7.3                   :  None (NOK)

As can be seen from the dependencies, spyder requires qtconsole >=5.0.3. However, conda search -f qtconsole reveals that the highest version available is 5.0.2. The qtconsole docs say that the latest release is 5.0.3. Is this just an issue with conda not having the latest version yet?

I also encountered the same problem.
I use the following method to solve.
conda install qtconsole=5.0.3

Hey @gica3618, thanks for reporting. I'll inform the Anaconda team about this problem so they can fix it as soon as possible.

same with python 3.7 and windows setup
(arcgispro-py3) C:\arc_pro\bin\Python\envs\arcgispro-py3>conda install qtconsole=5.0.3 --dry-run
Fetching package metadata .............
PackageNotFoundError: Packages missing in current channels:

qtconsole 5.0.3*

Maybe it was removed.

Nop, it haven't been added.

I was able to fix this problem, by running:
conda install -c conda-forge qtconsole
The updated qtconsole lib (5.0.3) can be found here: https://anaconda.org/conda-forge/qtconsole

@ccordoba12
you can close...
All the updates are available on the main anaconda site today

Thanks for the update!


Adds clear support to import

Requires this Pilosa PR: https://github.com/pilosa/pilosa/pull/1699
Clear roaring import test currently fails, since it is not supported (yet) on that PR.

Coverage decreased (-0.01%) to 99.787% when pulling 67cbe6ace916f26ef0080c49ab9e6055b7d93ee8 on yuce:clear-import into 0a77ad601974ffc6bf6b53e40000223b86326187 on pilosa:master.


New release v0.6

add suport for python2.7
add sphinx documentation on readthedocs
refactor README.md
add CONTRIBUTING.md

Codecov Report

Merging #24 into dev will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##              dev      #24   +/-   ##
=======================================
  Coverage   97.58%   97.58%
=======================================
  Files          15       15
  Lines         496      496
=======================================
  Hits          484      484
  Misses         12       12

Impacted Files
Coverage Δ

decorating/__init__.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cb44962...9815e7f. Read the comment docs.


install aks cli

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks install-cli
Errors:
Connection error while attempting to download client ([Errno 13] Permission denied: '/usr/local/bin/kubectl')

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az aks install-cli

Expected Behavior
Environment Summary
Linux-4.4.0-19041-Microsoft-x86_64-with-debian-bullseye-sid
Python 3.6.10
Installer: DEB

azure-cli 2.26.1 *

Extensions:
interactive 0.4.5

Additional Context

route to service team

@or-etoro Please use the official K8s docs for installing kubectl and ideally close the ticket.

Looks like the issue is abandoned.
Official MS's documentation for installation of kubectl with azure-cli (https://learn.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-install-cli) says:
--install-location
Path at which to install kubectl. Note: the path should contain the binary filename.
default value: ~.azure-kubectl\kubectl.exe
This path should be fine in regards of permissions, and it is not in /usr/local/bin.
What is the reason of referring to official kubernetes docs of installing kubectl, if the whole topic is regarding azure-cli only?


Continuing the training of MegaDetector

Hi all! That's a lot for making this fantastic work available, the collective usefulness of the tools provided is truly staggering.
I was trying out MegaDetector and it's working really well. However, it consistently misses some smaller animals that are partially obscured in the grass (so, false negatives), and sometimes has a tendency to pick up inanimate objects like tree stumps as animals (false positives). Confidence thresholding doesn't help to weed out those false positives as it comes at a high price - basically, I'd have to set a threshold close to unity and miss on a lot of robust animal detection that way.
I see that there are checkpoints available for the 4.1 detector version, and was wondering if there's a code snippet one can use for continuing the training?
Alternatively (a bit of a general question, sorry), are they any good strategies to mitigate the issues above?

Thanks for your interest in MegaDetector.... we don't have a code snippet for resuming training, unfortunately, but I'm not sure I would recommend that anyway.  MegaDetector v4 is based on TensorFlow 1.x, which is starting to get pretty out of date, and you'd probably have to do a bunch of work to manage an outdated training environment.  We will be releasing a new version later this year that will (with very high probability) move to TF 2.x.
Regarding the false-negative/false-positive balance... a couple things I would add:

There definitely exist ecosystems and species that just give MDv4 a hard time.  These are exactly what we're trying to address with MDv5!  In fact one of our MDv5 training data sets is basically "tiny squirrels hiding in tall grass". :)  But for now, there's always a possibility that you simply have animals MD can't reliably find, and MD isn't the solution for you.

That said, I would start by seeing whether there are lower-confidence detections on those animals.  If you're getting those detections at 50% confidence, that may be fine, which brings us to...

Regarding false positives... first, we encourage users to think of MD as a way to accelerate image review, not to automate, so you will bang your head against the problem if you aim for 0% false positives.  We typically try to get to a level of false positives that will still save our users more time than it takes to add a new step into their workflow, often this is somewhere around 80% precision, as long as we can get very high recall at that level of precision.  So if you're somewhere around there, I'm not sure I would spend too much time trying to get rid of every false positive.

That said, this very inelegant technique has been magical for repeated false positives due to sticks, rocks, etc.:
https://github.com/microsoft/CameraTraps/tree/master/api/batch_processing/postprocessing/repeat_detection_elimination
It takes a little practice, but once you get the hang of it, you can get rid of hundreds of thousands of false positives in just a few minutes of semi-automated image review.

Hope that helps!  If you find that you're just in one of those situations where MDv4 can't reliably find your animals, stay tuned for MDv5, and report back here!
Thanks.
-Dan

Hi Dan, thanks a lot for your reply! Will be looking forward for a new detector version. On point 3: I'm aware of the precision/recall tradeoff and wasn't expecting a perfect detector - I was simply wondering what are the available tools, tips, and tricks to leverage that balance. Your reply sums that up nicely.
In the meanwhile, the postprocessing script you've linked too looks absolutely fantastic. It looks like something I was afraid I'd have to write myself. Again, thanks a lot for making these available! :1st_place_medal:
I'm going to close the issue now.

Just wanted to chime in with an update in case anyone else stumbles upon this. The script tools linked above worked like a charm with a few tricks:

Had to modify IOU threshold defaults in repeat_detections_core.py, because remove_repeat_detections f-ion doesn't allow for options to be passed from command-line driver.
The defaults for find_repeat_detections are quite sensitive to the project setup, and esp. occurrenceThreshold value depends heavily on how many images from a given location exist.

Other than this, it was a huge time saver to weed out the false positives!

Glad it worked out!  Yes, it takes a little fine-tuning and intuition, but it's magical once you get it going.  We typically use an occurrenceThreshold of ~10 (below that it isn't really meaningful), but for very large projects (millions of images, with tens of thousands per camera) where we don't really want to spend a long time on the repeat detection process, we'll bump that up to as much as 50.


ResNetDUC model can not converge in the dataset CamVid?

First thanks for your implementing for ResNetDUC, I try to train on the dataset CamVid, but it is trained slow and seem not converge. What should I do to get a better model?

Do you check whether there is any bug, such as forgetting to call loss.backward() ?

Sorry because it trains too slow, I thought it seems not converge.


Problem confirmation webhook

I always get the message while maintaining webhook

Did you select your facebook page for the bot?

Yes

No I mean Webhook section below the Token Generation section.

I get a request from facebook, but can not track whether

I figured out the problem was variable API. thank you


Make usage of grape >= 1.3

Coverage decreased (-0.1%) to 99.559% when pulling fd941f4cb3778d8c1b157de4e8664220f0142873 on LeFnord:master into 11d29c40c592c0b63e5dff6b13bd74cb133ec9a6 on ruby-grape:master.

Coverage decreased (-0.1%) to 99.559% when pulling fd941f4cb3778d8c1b157de4e8664220f0142873 on LeFnord:master into 11d29c40c592c0b63e5dff6b13bd74cb133ec9a6 on ruby-grape:master.


mdk-sdk: 0.29.0 -> 0.29.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/wang-bin/mdk-sdk/releases.
meta.description for mdk-sdk is: multimedia development kit
meta.homepage for mdk-sdk is: https://github.com/wang-bin/mdk-sdk
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.29.1 with grep in /nix/store/n2isjbm115fxq6ysnzpsr15a19qr8jgy-mdk-sdk-0.29.1
found 0.29.1 in filename of file in /nix/store/n2isjbm115fxq6ysnzpsr15a19qr8jgy-mdk-sdk-0.29.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

gyroflow
mdk-sdk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n2isjbm115fxq6ysnzpsr15a19qr8jgy-mdk-sdk-0.29.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A mdk-sdk https://github.com/r-ryantm/nixpkgs/archive/81c3d4cb13f7c104580c73cd859587756518d678.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/81c3d4cb13f7c104580c73cd859587756518d678#mdk-sdk

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n2isjbm115fxq6ysnzpsr15a19qr8jgy-mdk-sdk-0.29.1
ls -la /nix/store/n2isjbm115fxq6ysnzpsr15a19qr8jgy-mdk-sdk-0.29.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

gyroflow

1 package built:

mdk-sdk

Maintainer pings
cc @orivej for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 338518 run on x86_64-linux 1

2 packages built:

gyroflow
mdk-sdk


Update Prometheus documentation

Should be merged after https://github.com/minio/minio/pull/7453

blocked until minio/minio#7453 is merged


you can add an api for dot

val  inputStream = dot.getInputStream
so that it can be easily used for browser rendering  in many  scala web  framework or lib

@epiphyllum thanks for your advise, but I am not sure what you mean. Could you provide a more
specific details of how will you use this api?

for example:
when browser initiate a request   GET /give/me/graph/of/:flow_id.png  to my webserver, webserver will first load data from database using :flow_id,  then webserver should create a Digraph class provided by you, and render an image to the browser
val flowConfig = loadConfigFromDB(flowId)
val flowDot = new Digraph(comment = "The Flow Graph")
val inputStream = flowDot.getInputStream

val httpResponse = new HTTPResponse(inputStream, `Content-Type:image/png`)

blah blah...

this project provide an DSL wrapper for graphviz command.  it is a good start.
I think it is also can be used in the web for image rendering where performance is not some critical

Thanks for your detailed explaination. I will take a look into this.


[Bug]: Proxy database update error after delete not working proxy

Version of the software
0.2.5
Operating system
Windows 10 (Native), Ubuntu 20.04 (WebApp)
Browser / Native
Both
What happened?
This happens when delete Not Working proxy during Proxy Check task.
=> Proxy DB wont update anymore
=> This error occurs in version 0.2.5

screen-capture.webm
Relevant LoliCode if needed
No response

This has been fixed in 0.3.0


Added an event for default rule "Program run with disallowed http proxy env"

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind documentation

/kind tests

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area commands

/area pkg

/area events

What this PR does / why we need it:
Added an event for default rule "Program run with disallowed http proxy env"
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: GLVSKiriti
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Similarly a Notice log is produced on left terminal on executing the event code as expected


sync_streaming_ping_pong_test failed on macos

https://grpc-testing.appspot.com/job/gRPC_master/12020/config=dbg,language=c++,platform=macos/console
E1021 13:30:42.182922000<PHONE_NUMBER>04640 driver.cc:226] assertion failed: server->stream->Read(&server_status)

Caught signal 6
no backtrace
FAILED: bins/dbg/qps_test [ret=-6, pid=67832]
FAILED: Some tests failed

true
'[' '!' -e reports/index.html ']'
mkdir -p reports
echo 'No reports generated.'
[htmlpublisher] Archiving HTML reports...
[htmlpublisher] Archiving at BUILD level /jenkins/workspace/gRPC_master/config/dbg/language/c++/platform/macos/reports to /home/jenkins/jenkins_home/jobs/gRPC_master/configurations/axis-config/dbg/axis-language/c++/axis-platform/macos/builds/12020/htmlreports/HTML_Report
[copy-to-slave] Copying 'report.xml', excluding nothing, from 'file:/jenkins/workspace/gRPC_master/config/dbg/language/c++/platform/macos/' on 'hudson.slaves.DumbSlave[grpc-mac-node2]' to 'file:/home/jenkins/jenkins_home/jobs/gRPC_master/workspace/config/dbg/language/c++/platform/macos/' on the master.
Recording test results
Build step 'Publish JUnit test result report' changed build result to UNSTABLE
Finished: UNSTABLE

qps_test has the same problem:
https://grpc-testing.appspot.com/job/gRPC_master/12020/config=dbg,language=c++,platform=macos/consoleText

another failure:
https://grpc-testing.appspot.com/job/gRPC_master/12375/config=dbg,language=c++,platform=macos/testReport/(root)/tests/bins_dbg_sync_streaming_ping_pong_test/

Still failing:
I1102 12:48:58.794363000<PHONE_NUMBER>04640 sync_streaming_ping_pong_test.cc:51] Running Synchronous Streaming Ping Pong
D1102 12:48:58.794996000<PHONE_NUMBER>04640 test_config.c:155] test slowdown: machine=1.000000 build=1.000000 total=1.000000
E1102 12:48:58.796632000<PHONE_NUMBER>04640 tcp_client_posix.c:171] failed to connect to 'ipv6:[::1]:32767': socket error: connection refused
E1102 12:48:58.798218000<PHONE_NUMBER>04640 tcp_client_posix.c:171] failed to connect to 'ipv6:[::1]:32767': socket error: connection refused
E1102 12:48:58.800725000<PHONE_NUMBER>04640 tcp_client_posix.c:171] failed to connect to 'ipv6:[::1]:32767': socket error: connection refused
E1102 12:48:58.801732000<PHONE_NUMBER>04640 tcp_client_posix.c:171] failed to connect to 'ipv6:[::1]:32767': socket error: connection refused
D1102 12:48:58.804657000<PHONE_NUMBER> grpc_profiler.c:48] You do not have google-perftools installed, profiling is disabled [for qps_server.prof]
D1102 12:48:58.804682000<PHONE_NUMBER> grpc_profiler.c:52] To install on ubuntu: sudo apt-get install google-perftools libgoogle-perftools-dev
I1102 12:48:58.807648000<PHONE_NUMBER>04640 driver.cc:206] Warming up
I1102 12:49:03.808309000<PHONE_NUMBER>04640 driver.cc:212] Starting
E1102 12:49:33.811954000<PHONE_NUMBER>04640 driver.cc:229] assertion failed: client->stream->Read(&client_status)

I believe this flake has been fixed by #4018. Will watch and see.

I declare this closed based on a lack of failures in recent master builds since #4018 was merged.


feat: the Fourier transform a function with fast enough decay is smooth

[x] depends on: #11771
[x] depends on: #11772
[x] depends on: #11775
[x] depends on: #11779
[x] depends on: #11840

Thanks!
bors r+


Add function unsafeHumanReadablePartFromText.

This PR:

[x] Adds function unsafeHumanReadablePartFromText, which is similar to humanReadablePartFromText, except that it throws a runtime exception when provided with an invalid input.
[x] Adds simple unit tests to check that unsafeHumanReadablePartFromText throws exceptions appropriately. (Note that the original humanReadablePartFromText function is already tested with property tests.)
[x] Exports the unsafeHumanReadablePartFromText function from a new module Codec.Binary.Bech32.Unsafe.

Closing for now.
I've identified a better solution that doesn't involve exporting an unsafe function from this library.
Will add more details in a further comment.

In cardano-wallet we eventually opted to replace our run-time parsing of HRP literals with quasiquoted literals that are checked at compile time, thus negating the need to export a unsafeHumanReadablePartFromText function. See https://github.com/input-output-hk/cardano-wallet/pull/1326


SampleDataForSplitPoints and SplitTable don't work together

In the AccumuloStore, the SampleDataForSplitPointsHandler uses SampleDataAndCreateSplitsFileTool to sample some split points and write them to file. They are written to file base64 encoded.
The SplitTableHandler uses SplitTableTool to read the split points in from file and apply them to the table. The base64 encoding is not undone when they are read from file.
This explains why only one tablet server receives data even if split points have been applied.
This should be fixed and a unit test created.

Merged into develop.


Adaptive cards $when not actioned by bot framework composer in webchat or emulator

Describe the bug
I'm using Bot Framework Composer to make a chat bot. When using an adaptive card, json elements should be conditionally hidden when the following exists
"$when": "False"
However that doesn't seem to happen in emulator or webchat.
Is this a bot framework issue?
Version
Version:  2.1.2
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0
Browser

[ x] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[x ] Windows 10 pro
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Create adaptive card attachment for send response.
Add an textblock saying Hi, and include a $when line set to false.
Run the bot and you'll still see Hi.
You can try setting value of $when to "${1==2}", "False", "false", "FALSE", it will still show.

Expected behavior
Should not see Hi.
Screenshots

Additional context
{
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "type": "AdaptiveCard",
    "version": "1.3",
    "body": [
		{
            "type": "TextBlock",
            "text": "Hi 1=2",
            "spacing": "Small",
            "size": "Default",
            "wrap": true,
            "$when": "${1==2}"
        },
        {
            "type": "TextBlock",
            "text": "Hi false",
            "spacing": "Small",
            "size": "Default",
            "wrap": true,
            "$when": "false"
        },
        {
            "type": "TextBlock",
            "text": "Hi False",
            "spacing": "Small",
            "size": "Default",
            "wrap": true,
            "$when": "False"
        },
        {
            "type": "TextBlock",
            "text": "Hi FALSE",
            "spacing": "Small",
            "size": "Default",
            "wrap": true,
            "$when": "FALSE"
        }
	]
}

Hi @dweeb1937 Thank you for reporting this.
Unfortunately, adaptive card templating is not yet implemented in the SDK.
Please see more info here:

https://github.com/microsoft/BotFramework-Composer/issues/8798
https://github.com/microsoft/botframework-sdk/issues/6477


wireguard: 0.0.20170214 -> 0.0.20170223

Simple version bump.
Release notes: https://lists.zx2c4.com/pipermail/wireguard/2017-February/001068.html

Built fine. Thanks!


fix(operator): avoid reusing version in clone name

The version number could be very long so only expose
a short sha version of it in the clone name.
Fixes #683

/test openshift

/test openshift


weather.get_forecast is deprecated as of 2023.12

Describe the bug
As of 2023.12 weather.get_forecast is now deprecated and has been replaced with weather.get_forecasts
Information from the HA blog https://www.home-assistant.io/blog/2023/12/06/release-202312/#backward-incompatible-changes
weather.get_forecast uses an outdated response data format and is now deprecated, pending removal in Home Assistant 2024.6.
Please use weather.get_forecasts, which supports multiple entities instead.
The output of this newer service changed slightly, as it now returns a mapping of entity IDs to lists of forecasts instead of a list of forecasts.
(@eifinger - https://github.com/home-assistant/core/pull/102534) (documentation)
Expected behavior
See above
Actual behavior
See above
Home Assistant version
2023.12.3
Integration version
1.3.5
Other details
No response
Troubleshooting steps

[X] I have updated my Home Assistant installation to the latest version.
[X] I have updated the Pirate Weather Integration to the latest version.
[X] I have gone through the documentation, parameter documentation and sensor documentation before opening this issue.
[X] I have searched this repository and Pirate Weather Repository to see if the issue has already been reported.
[X] I have restarted my Home Assistant installation.
[X] I have checked to see if the issue is not an API issue.
[X] I have written an informative title.

Good idea to open the issue to track this. I'm going to update my end (without a template) and see if it flags this issue, which will show if it's something in the integration or just the template

Updated my template to use weather.get_forecasts and the error message is gone so the issue was with the template not with the integration.


[Frontend] Fix import for libdevice

This is a hotfix for issue 1 in https://github.com/openai/triton/issues/1017
@ptillet @crutcher We can resume reviewing this PR so that many frontend related problems can go away

LGTM. Can we merge?

Sure


Multiple URLs

Extend support to download multiple files in a single command.

Done:
https://github.com/ktechhub/pywgett/commit/d1d602d7794870178e7737c4a9a482668d124f1e


Create 1641-Count-Sorted-Vowel-Strings.cpp

File(s) Modified: 1641-Count-Sorted-Vowel-Strings
Language(s) Used: C++
Submission URL: _https://leetcode.com/submissions/detail/771361242/_

Thanks, @Vitali-Matteo!


Where is the fix for the "No type was specified for the decimal column" migration error?

Ignore the following warning message, you fix that in the next tutorial:
Microsoft.EntityFrameworkCore.Model.Validation[30000]
No type was specified for the decimal column 'Price' on entity type 'Movie'. This will cause values to be silently truncated if they do not fit in the default precision and scale. Explicitly specify the SQL server column type that can accommodate all the values using 'ForHasColumnType()'.

Source: https://docs.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/model?view=aspnetcore-2.1
The article mentions that the fix is in the next tutorial, but I cannot find it anywhere. Can anyone point to the location of the solution?

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

ID: 6719f08e-3bd7-dc1a-71df-f2ef9fbca9d8
Version Independent ID: 7096fdb3-612e-9e00-bd0b-8ea4886a09ce
Content: Add a model to a Razor Pages app in ASP.NET Core
Content Source: aspnetcore/tutorials/razor-pages/model.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@danielcongrove I should read "in a later tutorial". It's just a warning. I fixed the wording.

But where's the later tutorial? This doesn't fix the basic question.

https://docs.microsoft.com/en-us/aspnet/core/tutorials/razor-pages/new-field
public class Movie
{
    public int ID { get; set; }
    public string Title { get; set; }

    [Display(Name = "Release Date")]
    [DataType(DataType.Date)]
    public DateTime ReleaseDate { get; set; }
    public string Genre { get; set; }

    [Column(TypeName = "decimal(18, 2)")]
    public decimal Price { get; set; }
    public string Rating { get; set; }
}

Looks like no fix to now.


🐛 BUG: Could not resolve "@cloudflare/ai"

Which Cloudflare product(s) does this pertain to?
Pages
What version(s) of the tool(s) are you using?
wrangler 3.15.0,
What version of Node are you using?
No response
What operating system are you using?
mac
Describe the Bug
I tried work AI for pages via bindings and got the error when deploying from github.
It seems 'npm install @cloudflare/ai' does not work, I run this under /functions in the project folder, then push to github. Is it a bug or I missed anything?
thanks
https://developers.cloudflare.com/pages/platform/functions/bindings/
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs

21:20:46.889
Found Functions directory at /functions. Uploading.

21:20:48.570
✘ [ERROR] 1 error(s) and 0 warning(s) when compiling Worker.

21:20:48.571

21:20:48.571

21:20:48.573

21:20:48.575
✘ [ERROR] Could not resolve "@cloudflare/ai"

21:20:48.575

21:20:48.576
hello.js:1:19:

21:20:48.576
1 │ import { Ai } from '@cloudflare/ai'

21:20:48.576
╵                    ~~~~~~~~~~~~~~~~

21:20:48.576

21:20:48.576
You can mark the path "@cloudflare/ai" as external to exclude it from the bundle, which will remove this error.

21:20:48.576

21:20:48.576

21:20:48.578
✘ [ERROR] Build failed with 1 error:

21:20:48.578

21:20:48.579
hello.js:1:19: ERROR: Could not resolve "@cloudflare/ai"

21:20:48.579

21:20:48.579

21:20:48.592
Failed building Pages Functions.

21:20:49.525
Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH

@midshipman Could you provide a link to your repo/a minimal reproduction? Workers AI should work with Pages. One thing you could try is running npm install @cloudflare/ai at the root of your repo, rather than within the functions folder?

hi @midshipman :) we haven't heard from you in a while, so we’re going to close this issue for now. If this is still a problem, please feel free to open a new issue referencing this one. please be sure to include an updated summary, repro, and any additional requested details and we will revisit and investigate further. thanks!


Add Gadjah Mada University

Official Website: https://ugm.ac.id/en/
Faculty and School: https://ugm.ac.id/en/education/
Department of Computer Science: https://ugm.ac.id/en/prodi/bachelor-in-computer-science/
Official email for registered students to access the LMS: https://elok.ugm.ac.id/ or university email: https://ugmail.ugm.ac.id/

Domain email: @mail.ugm.ac.id

@barenbaruna I am sorry, the domain mail.ugm.ac.id is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Please invite me to the community

Name
Yash
Discord Username (if applicable)
kepler#9452
Additional Context
I want to deepen my knowledge in blockchain technologies.

Welcome to Web3Community!


Update the Databricks Documentation on Diagnostic Log Table Logs to Help the customer.

Hi,
Earlier I had raised a case #63883 for documentation updates but it was closed saying that no product issues were found. Basically I did not complain about Product Issues in the original case. The product works well in terms of Diagnostic Log generation, my point is that the Logs does not appear unless there is an activity on the databricks cluster or notebook or jobs.... So please update the below documentation with an additional statement saying that the logs will start appearing in the Diagnostic Logs table like DatabricksCluster, DatabricksNotebooks, DatabricksJobs or etc., only if there is any ACTIVITY. on the databricks workspace or cluster of jobs or notebooks.
https://docs.microsoft.com/en-us/azure/databricks/administration-guide/account-settings/azure-diagnostic-logs
Our customers have reported issues for not seeing the logs in such tables after configuring the Diagnostic Log setting even after 24 - 72 hours as per the current documentation. But the real fact is there should be some activity on the databricks end, so again requesting you to update the documentation and I am not complaining the product.
Regards,
Gowri Shankar

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

ID: aa60fa41-f753-9c55-c799-a870bdb219a4
Version Independent ID: 786b27ec-7f4d-ad35-e26d-5832c072536e
Content: Diagnostic logging in Azure Databricks - Azure Databricks
Content Source: databricks/administration-guide/account-settings/azure-diagnostic-logs.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@gopasupa  Thanks for the feedback! I have assigned the issue to the content author to review further and update the document as appropriate.

We have filed a ticket in the Databricks bug tracking system: DOC-3023. We will update this Git issue when the ticket has been resolved. #label:"in-progress".

Thanks for your dedication to our documentation. Unfortunately, we have been unable to address your issue and apologize for the delayed response. We are closing this issue, but if you feel that it's still a concern, please let us know directly at<EMAIL_ADDRESS>#please-close

#please-close


Open VSX Listing: Signing the Publisher Agreement

Thank you for being part of the Open VSX community by adding your extensions to the Open VSX Registry. Please note that the service was recently transferred to the Eclipse Foundation and urgent action on your part is needed so we can continue to list your extensions. To ensure uninterrupted service, please sign the Eclipse Publisher Agreement on or before January 8, 2021. If not signed by that date, your extensions will be delisted and will no longer appear on the site nor be available via the API. If you sign at a later date, your extensions will then be re-activated. The signing process is explained in the Wiki (steps 1 and 2).
Please also note that all extensions MUST have a license in order to be listed.
More details are in these recent blog posts:
https://blogs.eclipse.org/post/brian-king/open-vsx-registry-under-new-management
https://blogs.eclipse.org/post/brian-king/new-era-open-vsx-registry
Today, there’s growing momentum around open source tools and technologies that support Visual Studio (VS) Code extensions. Leading global organizations are adopting these tools and technologies. This momentum has spurred demand for a marketplace without restrictions and limitations. Thanks for joining us on this journey as we continue to build the Open VSX community. We look forward to continued innovation from you in 2021!

@huytd could you look into this?
This extension currently has no license. Please add one, preferably an open source license such as MIT.
A license is mandatory for publishing your extension to Open VSX. Its publishing tool ovsx offers to automatically add the MIT license when you try to publish without license. See the Open VSX Wiki for more details.

@huytd could you look into this?
This extension currently has no license. Please add one, preferably an open source license such as MIT.
A license is mandatory for publishing your extension to Open VSX. Its publishing tool ovsx offers to automatically add the MIT license when you try to publish without license. See the Open VSX Wiki for more details.

@spoenemann https://github.com/huytd/vscode-tokyo-city/blob/master/LICENSE FYI.

I believe this has been addressed. I'll close the issue for now, please feel free to reopen in the future if something came up. Thanks everyone!


Added support for alpha blend functions

Added GVRRenderData.setAlphaBlendFunc, GVRRenderData.getSourceBlendFunc and GVRRenderData.getDestBlendFunc
GearVRF DCO signed off by: Nola Donato<EMAIL_ADDRESS>The unit test for this feature is in GearVRF-Tests PR #48

Looks good. Planning to merge in the afternoon.


Security protocol from Bot connector to Bot

Hello,
The current Bot Connect's OpenID  document does not have as much information as the MSA's OpenID metadata, specifically the id_token for the "response_types_supported", this prevents the ability to setup the External ID Token Authentication ( OIDC ) for Rest APIs. Are there plans on updating the Security protocol from Bot connector to Bot to use the MSA's OpenID instead?
Thanks.

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

ID: d58bf70a-3263-93a1-5bc2-085431a7aa6b
Version Independent ID: c5e3de2f-58ad-1c6a-e0f3-93489d013114
Content: Authenticate requests - Bot Service
Content Source: articles/rest-api/bot-framework-rest-connector-authentication.md
Service: bot-service
Sub-service: sdk
GitHub Login: @RobStand
Microsoft Alias: kamrani

For question about the SDK roadmap, please log them in the botframework-sdk repo.


ui dropdown does not allow to clear dropdown values

When "ui dropdown" class is active on select element, it does not allow to reset it. But when only single class (only ui or only dropdown) is applied it allow to reset value.
HTML Code:
 <select ng-options="option for option in brands" ng-model="mdl.brandValue" class="ui dropdown">
 <option value="">Brands</option>
 </select>

Clear Filters

JS Code:
    $scope.brands = ["AT&T", "Apple", "HTC", "LG", "Motorola", "Samsung", "Sprint", "Verizon Wireless"];

Please create a JSfiddle test case, there is a link to fork in readme


Final Project: Convert Numba SSA to Python AST

Hi Professor Cheshmi, this is the pull request from Hanwei Wu for the course project: conversion from Numba SSA to Python AST.


FIX ensure the ClearIndexJob doesn't break during initialisation

QueuedJobs requires default values to be set in __construct which causes this job to be stuck in "Initialising" https://github.com/symbiote/silverstripe-queuedjobs/blob/89a057ce2c7e2f9560b8eea6d1974f423f45dc8b/docs/en/defining-jobs.md#api-overview

Huh, I think I've been burnt by this in other projects 😅
Does this prevent the job being created initially, but will run in the queue? Or does it "fail" if you don't pass in $indexName so you are forced to pass it in?

I can confirm this works as expected. The issue was that when queuedjobs instantiates the job internally it doesn't pass any arguments. However, the job descriptor which is actually run still has all the details (e.g. the index name), so data gets cleared from the correct index.

I'm happy merging this despite codecov packing a sad, there's no point testing the if(!$indexName) line


"sky & weather" subcategory should be in "Animals & Nature" not "Travel & Places"

At the moment the "sky & weather" emojis are grouped under "Travel & Places". I think they should be in "Animals & Nature" - which is where most platform emoji pickers have them.
(It's not clear to me how you construct the categories - I don't see them in the Unicode spec, but maybe I've just failed to find that info)

Huh, no! You get it from https://unicode.org/Public/emoji/14.0/emoji-test.txt
where, yes, weather is under travel and places.