Issues with reduce

I'm using the following example for reduce
addprocs(2)
using ComputeFramework

numbers = [1, 2, 3 ,4, 5, 6, 7, 8, 9, 10]
parallel_numbers = distribute(numbers)
sum_of_numbers = reduce(+, 0.0, parallel_numbers)
println(gather(Context(), sum_of_numbers))

The first problem is that reduce returns a single element array, unlike filter and map. The second problem is that +,- and other arithmetic operators don't have methods that can work with the required types.
MethodError: `+` has no method matching +(::Float64, ::ComputeFramework.Distribute{Array{Int64,1},ComputeFramework.CutDimension{1}})

However push! works just fine:
sum_of_numbers = reduce(push!, 0.0, parallel_numbers)

Calling gather on a MapReduceNode will give an error. compute will get the value for you in this case without requiring a gather.
@shashi Should we create a special gather for MapReduceNodes, where it doesn't call gather on the computed values but just returns compute?

Using Compute gives similar results. I don't think that's the problem.

There was an issue which #7 solves. If you use compute on that branch, this should work. gather will give an error on #7 too.

Ah okay.


Update text for #144

Please ask Spanish/Brazilian Portuguese translators to confirm the text I added for those languages!

@bitcoinuser @jjmr007 can you check for translation and suggest edits if needed?
@soulBit in case you are using google translator you can just use english translations in each of translation files - it should be more easily spottable for translators.
Also, only english language file keys required but filling other files should help translators a lot.

@bitcoinuser @jjmr007 can you check for translation and suggest edits if needed?
@soulBit in case you are using google translator you can just use english translations in each of translation files - it should be more easily spottable for translators.
Also, only english language file keys required but filling other files should help translators a lot.

Portuguese Brazilian is ok.

Portuguese Brazilian is ok.

Ativo e valor a ser colaterizado.
@soulBit please change to this.

Ativo e valor a ser colaterizado.
@soulBit please change to this.

@bitcoinuser @jjmr007 can you check for translation and suggest edits if needed?
@soulBit in case you are using google translator you can just use english translations in each of translation files - it should be more easily spottable for translators.
Also, only english language file keys required but filling other files should help translators a lot.

Thanks, I actually got my flatmate to translate (but they are Spanish and non-crypto friendly). I've updated the pt-br text to match suggestion from @bitcoinuser

@bitcoinuser @jjmr007 can you check for translation and suggest edits if needed?
@soulBit in case you are using google translator you can just use english translations in each of translation files - it should be more easily spottable for translators.
Also, only english language file keys required but filling other files should help translators a lot.

Thanks, I actually got my flatmate to translate (but they are Spanish and non-crypto friendly). I've updated the pt-br text to match suggestion from @bitcoinuser


examples/rktnetes: Update to CoreOS Alpha 1192.0.0

rkt v1.14.0 is needed for rktnetes
Validated on lab hardware https://github.com/dghubble/metal/commit/68ac004a2345d04f4577f818f5765b8a0487114c

Still testing in QEMU/KVM.
closes #353

https://github.com/coreos/bugs/issues/1600

Looks like that's for AWS, are there expected issues on bare-metal?

Hm, I do have issues with the PXE image in QEMMU/KVM. Let's use CoreOS beta for now since it has rkt v1.14.0 too.

No expected issues. Can you file a bug?

Yep, lemme collect some info and test some other examples.

A rktnetes cluster with CoreOS Bet 1185.1.0,
kubectl get pods --all-namespaces
NAMESPACE     NAME                                        READY     STATUS    RESTARTS   AGE
kube-system   heapster-v1.2.0-4088228293-nfqyo            2/2       Running   0          11m
kube-system   kube-apiserver-node1.example.com            1/1       Running   0          11m
kube-system   kube-controller-manager-node1.example.com   1/1       Running   0          11m
kube-system   kube-dns-v19-bj1m8                          3/3       Running   0          12m
kube-system   kube-proxy-node1.example.com                1/1       Running   0          11m
kube-system   kube-proxy-node2.example.com                1/1       Running   0          15s
kube-system   kube-proxy-node3.example.com                1/1       Running   0          11m
kube-system   kube-scheduler-node1.example.com            1/1       Running   0          11m
kube-system   kubernetes-dashboard-v1.4.0-q3z3b           1/1       Running   1          12m


BufWritePre not working on startup until sourced

When I open a new project and save the file BufWritePre doesn't work. I have tried it in my ~/.vimrc and even ~/.vim/after/plugin/spaces.vim
set list
set listchars=trail:·

autocmd BufWritePre <buffer> :%s/\s\+$//e

Running vim -V I can see the file definitely gets sourced
sourcing "/Users/carlos/.vim/after/plugin/new.vim"
finished sourcing /Users/carlos/.vim/after/plugin/new.vim
Reading viminfo file "/Users/carlos/.viminfo" info oldfiles

Only when I manually source the file does it work.

why are you using a <buffer> autocommand?

New to vim I thought by adding <buffer> would ensure it only ran for that file.
You're right, I removed it and it worked.
Would you mind explaining why it didn't work with <buffer>


(feat): add support for matview

Introduction
Supports a target_table (TO table) for Materialized View, or it'd use its own table, which is fully configurable: engine, order by, partition by, etc... defaults to MergeTree() order by tuple().
Usage
A model to define a target table:
{{ config(order_by='(updated_at, id, name)', engine='MergeTree()', materialized='incremental', unique_key='id', inserts_only=True) }}

with actor_summary_table as (
    select id,
        name,
        num_movies,
        avg_rank,
        genres,
        directors,
        updated_at
    from {{ ref('actor_summary_transform') }}
) select *
from actor_summary_table

A mode to define a materialized view:
{{ config(materialized='view', matview=True, target_table='actor_summary_table`) }}

with actor_summary_transform as (
    SELECT id,
        any(actor_name) as name,
        uniqExact(movie_id)    as num_movies,
        avg(rank)                as avg_rank,
        uniqExact(genre)         as genres,
        uniqExact(director_name) as directors,
        max(created_at) as updated_at
    FROM (
        SELECT {{ source('imdb', 'actors') }}.id as id,
            concat({{ source('imdb', 'actors') }}.first_name, ' ', {{ source('imdb', 'actors') }}.last_name) as actor_name,
            {{ source('imdb', 'movies') }}.id as movie_id,
            {{ source('imdb', 'movies') }}.rank as rank,
            genre,
            concat({{ source('imdb', 'directors') }}.first_name, ' ', {{ source('imdb', 'directors') }}.last_name) as director_name,
            created_at
    FROM {{ source('imdb', 'actors') }}
        JOIN {{ source('imdb', 'roles') }} ON {{ source('imdb', 'roles') }}.actor_id = {{ source('imdb', 'actors') }}.id
        LEFT OUTER JOIN {{ source('imdb', 'movies') }} ON {{ source('imdb', 'movies') }}.id = {{ source('imdb', 'roles') }}.movie_id
        LEFT OUTER JOIN {{ source('imdb', 'genres') }} ON {{ source('imdb', 'genres') }}.movie_id = {{ source('imdb', 'movies') }}.id
        LEFT OUTER JOIN {{ source('imdb', 'movie_directors') }} ON {{ source('imdb', 'movie_directors') }}.movie_id = {{ source('imdb', 'movies') }}.id
        LEFT OUTER JOIN {{ source('imdb', 'directors') }} ON {{ source('imdb', 'directors') }}.id = {{ source('imdb', 'movie_directors') }}.director_id
    )
    GROUP BY id
)
select *
from actor_summary_transform

Thanks for your PR!  It would be extremely helpful if you could add a test for the new Materialized View functionality; if you don't have a chance to that I'll try to get to it later this week.

@genzgd sure would be great if you can add tests or I can try to get to it when I have time. I'm already using this feature on a local branch for a project and it works well.

Thanks -- at the moment the PR is failing a test and I haven't had the chance to dig into it.  If you any thoughts as to why that failure is happening that would be helpful.  In any case I'll try to get to it this coming week.

@genzgd The test fails with this error:
Table dbt_clickhouse_4727_test_basic_1672594971825.swappable already exists. (TABLE_ALREADY_EXISTS)

I don't think my PR should cause that failure. No new code is actually running unless matview=True:
{% if matview %}
  {{ clickhouse__create_matview_as(target_relation, sql) }}
{% else %}
  {{ get_create_view_as_sql(target_relation, sql) }}
{% endif %}

And tests aren't using matview so why should it affect tests?

I felt the same way :) but I haven't had a chance to figure out the problem.  There are no code changes since tests last successfully ran against the main branch, but maybe something has changed our test framework.  Have you tried running tests locally?

Hey! Any updates on this PR?

Hey! Any updates on this PR?

The short answer is there are no updates.  The broken test was not fixed and the ClickHouse team hasn't prioritized this functionality in dbt due to other work.  There is also concern about how materialized views will work on replicated tables and they are almost certain to break dbt incremental materializations (DELETEs, for example, are not propagated to materialized views in ClickHouse), so official support would require testing around these use cases.

Closed in favor of https://github.com/ClickHouse/dbt-clickhouse/pull/207


Synchronizing Sensor Polling with Simulation

Hi,
I am using the following versions:
BeamNG.tech: v<IP_ADDRESS>
BeamNGpy: 1.25.1
I spawn a vehicle with 3 front-facing cameras and an electronics sensor. My goal is for the vehicle to drive around the map using the span ai mode. While it is driving around, I want to capture camera data, steering, and throttle data at a set frequency (4Hz). To do this, I use the following code:
import time
import random

import matplotlib.pyplot as plt

from tqdm import tqdm

from beamngpy import BeamNGpy
from beamngpy import Scenario
from beamngpy import Vehicle
from beamngpy import set_up_simple_logging

from beamngpy.sensors import Camera
from beamngpy.sensors import Electrics

def initialize_cameras(bng, vehicle):
    camera_resolution=(200,150)
    # Create camera dnd lidar after starting simulation
    camera_l = Camera(name="camera_left",
                      bng=bng,
                      vehicle=vehicle,
                      requested_update_time=0.2,
                      dir=(0.75, -1, 0),
                      resolution=camera_resolution)
    camera_m = Camera(name="camera_middle",
                      bng=bng,
                      vehicle=vehicle,
                      requested_update_time=0.2,
                      dir=(0, -1, 0),
                      resolution=camera_resolution,
                      near_far_planes=(0.5, 400))
    camera_r = Camera(name="camera_right",
                      bng=bng,
                      vehicle=vehicle,
                      requested_update_time=0.2,
                      dir=(-0.75, -1, 0),
                      resolution=camera_resolution)
    # Return the cameras
    return [camera_l, camera_m, camera_r]

def initialize_electrics(vehicle):

    # Create the electrics
    electronic_sensor = Electrics()
    vehicle.sensors.attach('electrics', electronic_sensor)

    # Return the cameras
    return [electronic_sensor]

def plot_cameras(data_l, data_m, data_r):
    # Show the camera data
    try:
        plt.figure(1, figsize=(10,3))
        ax = plt.subplot(1,3,1)
        ax.axis('off')
        plt.imshow(data_l)

        ax = plt.subplot(1,3,2)
        ax.axis('off')
        plt.imshow(data_m)

        ax = plt.subplot(1,3,3)
        ax.axis('off')
        plt.imshow(data_r)

        plt.subplots_adjust(wspace=0, hspace=0, left=0, right=1, bottom=0, top=1)

        plt.pause(0.001)
    except Exception as e:
        print("{}".format(e))
    return plt

def main():

    # Set capture duration in seconds
    capture_time = 100
    # Set the capture rate in Hz
    capture_rate = 4
    capture_frequency = 1.0 / capture_rate

    # Generate a new random seed
    random.seed(1703)
    set_up_simple_logging()

    # Declare the BeamNG home and workspace
    bng_home = 'C:/Users/hilde/Desktop/SelfDriving/BeamNG.tech.v<IP_ADDRESS>'
    bng_user = 'C:/Users/hilde/Desktop/SelfDriving/BeamNGWorkspace'

    # Generate a new instance of BeamNG
    beamng = BeamNGpy('localhost', 64256, home=bng_home, user=bng_user)
    bng = beamng.open(launch=True)

    # Create the scenario
    scenario = Scenario('west_coast_usa', 'data_capture', description='Spanning the map with a LiDAR sensor')

    # Create and add ego ego_vehicle
    ego_vehicle = Vehicle(vid='ego', model='etk800', license='RED', color='Red')

    scenario.add_vehicle(vehicle=ego_vehicle,
                         pos=(-717.121, 101, 118.675),
                         rot_quat=(0, 0, 0.3826834, 0.9238795))
    scenario.make(bng)

    # Set simulator to 60hz temporal resolution
    bng.settings.set_deterministic(60)

    # Load simulation
    bng.scenario.load(scenario)
    bng.ui.hide_hud()
    bng.scenario.start()

    # Create the cameras
    cameras = initialize_cameras(bng, ego_vehicle)
    camera_l = cameras[0]
    camera_m = cameras[1]
    camera_r = cameras[2]

    # Create the electrics
    electrics =initialize_electrics(ego_vehicle)
    elec_sensor = electrics[0]

    # Set vehicle tro drive around randomly
    ego_vehicle.ai.set_mode('span')

    # Drive around
    for i in tqdm(range(int(capture_time / capture_frequency))):

        # Get the latest readings
        data_l = camera_l.poll()
        data_m = camera_m.poll()
        data_r = camera_r.poll()

        # Poll the electronic sensors
        ego_vehicle.sensors.poll()
        print("steering: {}".format(elec_sensor['steering']))
        print("steering_input: {}".format(elec_sensor['steering_input']))
        print("")
        print("throttle: {}".format(elec_sensor['throttle']))
        print("brake: {}".format(elec_sensor['brake']))
        print("--------------------")

        # Show the data
        plot_cameras(data_l['colour'], data_m['colour'], data_r['colour'])

        # np.save("./data/data_l{:04}".format(i), data_l['colour'])
        # np.save("./data/data_m{:04}".format(i), data_m['colour'])
        # np.save("./data/data_r{:04}".format(i), data_r['colour'])

        # Maintain the rate
        time.sleep(capture_rate)

    # Remove sensors
    camera_l.remove()
    camera_m.remove()
    camera_r.remove()

    # Close BeamNG
    bng.close()

if __name__ == '__main__':
    main()

When I ran my script, I noticed that the sensors did not record data anywhere near the set frequency, as you can see below (here I only get 2-3 camera readings in 10 seconds of driving):

I tried the following to improve the rate at which the sensors poll:

Save the camera data rather than plotting it
Reducing the camera resolution significantly
Using only a single front-facing camera

While some worked better than others, the sensors were always slower than the actual simulation. While I know, there are certain things I can do to my script (for example, tracking the time of the main loop and only waiting for the remaining time, etc.). I was wondering if there is a blocking function I can call. Something that would look as follows:
While driving:
    poll sensors
    wait for sensor readings
    continue simulation

Otherwise, I am open to other suggestions :) Thanks!

Hi Carl,
In your Python main loop you are pausing Python for 4 seconds each time.  This is why you are only getting 2.5 images per 10 second period.  Its this:  time.sleep(capture_rate) where capture_rate is a constant set to 4 at the top of the script.  If you remove this it updates faster.
Perhaps there is a misunderstand between what it means to 'poll' and what the 'update rate' is?  The update rate is a parameter we set which tells the physics engine how often to actually send requests to the GPU for new camera data.  Polling is when you want to send collect that new data from the physics engine and have it available for you in python, which is on a 4 second schedule in your script.
You have set the camera update rate to 0.2 seconds, which means the camera (internally) will automatically get itself new data every 0.2 seconds (on average - these jobs are actually scheduled for optimal GPU processing).  But in Python, you don't actually 'get' the data until you poll the camera, and this has a 4 second delay between each time in your script there.
If you want even faster streaming of the data, even at high resolutions, we currently recommend to switch the shared memory on (in the Camera constructor).   We can do that at least at 20 times per second (at least, with 1 camera).  You shouldn't need that for these resolutions, though.
Best regards,
Dave

Thank you, usingcapture_rate instead of capture_frequency was very silly of me.
However, its good to know that you are able to capture camera data up to 20Hz using 1 camera. As you said, I found using is_using_shared_memory=True to be a huge help. I also found that my plotting function was taking up to a second to render the images which is another reason I was seeing lag.
Thank you.


fix: set supportsLongRange to false on non-supporting controllers

@zwave-js-bot pack this

@zwave-js-bot pack this

@zwave-js-bot automerge


Slow first load

Hello!
This is an awesome resource, thank you for providing it.
Across all sprites I see a slow load first time, whereas subsequent requests are fine, e.g.
❯ time curl https://avatars.dicebear.com/4.5/api/human/test.svg
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" style="isolation:isolate" viewBox="0 0 20 20" version="1.1" shape-rendering="crispEdges"><path d="M3 20v-3h1v-1h4v-2H6v-1H5v-1H4v-1H3V9H2V7h1V4h1V3h1V2h10v1h1v1h1v3h1v2h-1v2h-1v1h-1v1h-1v1h-2v2h4v1h1v3H3z" fill="#EAC393"/><path d="M14 14v-1h1v-1h1v-1h1V9h1V7h-1V4h-1V3h-1V2H5v1H4v1H3v3H2v2h1v2h1v1h1v1h1v1h8z" fill="#FFF" fill-opacity=".1"/><path d="M5 7h3v2H5V7zm7 0h3v2h-3V7z" fill="#FFF"/><path d="M7 8h1v1H7V8zm5 0h1v1h-1V8z" fill="#697b94"/><path d="M8 4v1H7v1H5V5h2V4h1zm4 0h1v1h2v1h-2V5h-1V4z" fill-rule="evenodd" fill="#8c5a3b"/><path d="M9 12v1h1v1h1v-2H9z" fill="#d1a490"/><path d="M4 20v-2h1v-1h1v-1h2v1h1v1h2v-1h1v-1h2v1h1v1h1v2H4z" fill="#ae0001"/><path d="M1 17h3v-1h4v-2H6v-1H5v-1H4v-1H3V9H2V7h1V5h1V4h7V3h1v1h1V3h1v1h1V3h1v2h1v2h1v2h-1v2h-1v1h-1v1h-1v1h-2v2h4v1h3V4h-1V3h-1V2h-1V1H4v1H3v1H2v1H1v13z" fill="#a56b46"/></svg>curl https://avatars.dicebear.com/4.5/api/human/test.svg
0.01s user 0.01s system 2% cpu 2.354 total

❯ time curl https://avatars.dicebear.com/4.5/api/human/test.svg
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" style="isolation:isolate" viewBox="0 0 20 20" version="1.1" shape-rendering="crispEdges"><path d="M3 20v-3h1v-1h4v-2H6v-1H5v-1H4v-1H3V9H2V7h1V4h1V3h1V2h10v1h1v1h1v3h1v2h-1v2h-1v1h-1v1h-1v1h-2v2h4v1h1v3H3z" fill="#EAC393"/><path d="M14 14v-1h1v-1h1v-1h1V9h1V7h-1V4h-1V3h-1V2H5v1H4v1H3v3H2v2h1v2h1v1h1v1h1v1h8z" fill="#FFF" fill-opacity=".1"/><path d="M5 7h3v2H5V7zm7 0h3v2h-3V7z" fill="#FFF"/><path d="M7 8h1v1H7V8zm5 0h1v1h-1V8z" fill="#697b94"/><path d="M8 4v1H7v1H5V5h2V4h1zm4 0h1v1h2v1h-2V5h-1V4z" fill-rule="evenodd" fill="#8c5a3b"/><path d="M9 12v1h1v1h1v-2H9z" fill="#d1a490"/><path d="M4 20v-2h1v-1h1v-1h2v1h1v1h2v-1h1v-1h2v1h1v1h1v2H4z" fill="#ae0001"/><path d="M1 17h3v-1h4v-2H6v-1H5v-1H4v-1H3V9H2V7h1V5h1V4h7V3h1v1h1V3h1v1h1V3h1v2h1v2h1v2h-1v2h-1v1h-1v1h-1v1h-2v2h4v1h3V4h-1V3h-1V2h-1V1H4v1H3v1H2v1H1v13z" fill="#a56b46"/></svg>curl https://avatars.dicebear.com/4.5/api/human/test.svg
0.02s user 0.01s system 6% cpu 0.432 total

Now I see I am being firewalled from the HTTP API, I wasn't making a large number of requests. I shall just host it myself instead :)

Hello Oliver. I'm sorry you're having problems using the API. Unfortunately I can't explain your problems. A test on my part did not show any problems.

Hello Oliver. I'm sorry you're having problems using the API. Unfortunately I can't explain your problems. A test on my part (https://tools.bunny.net/http-test) did not show any problems.


Dotnet.ProjInfo.Inspect.getProjectInfo question

Not really a bug, just a quick question:

#66 introduced a change in Dotnet.ProjInfo.Inspect.getProjectInfo which removes the additionalArgs parameter. Should client repos (dotnet/fsharp, FCS, Fable, etc.) just adapt to it when they switch to the latest version of the Dotnet.ProjInfo package, or should a dummy parameter be added back so it's backwards-compatible?

My assumption here is that dotnet-proj-info is pre 1.0 version, and breaking changes in API may happen. After things are stabilized for 1.0 we will follow typical semantic versioning rules.


Table with headerless column as last column has side scroll

🐛 Bug Report

If a table has a headerless column (<Column hideHeader>...</Column>) as the last column, the table body contents will overflow horizontally and thus can be scrolled a tiny bit.
🤔 Expected Behavior

Should fill the space without the need for side scrolling
😯 Current Behavior

The row content extends beyond the viewable area, creating a horizontal scrollbar

💁 Possible Solution

🔦 Context

💻 Code Sample

Sandbox: https://codesandbox.io/s/peaceful-albattani-674nd?fontsize=14&hidenavigation=1&theme=dark
Code:
import React from "react";
import { Provider, defaultTheme, ActionButton } from "@adobe/react-spectrum";
import {
  Table,
  TableHeader,
  TableBody,
  Column,
  Row,
  Cell
} from "@react-spectrum/table";
import Add from "@spectrum-icons/workflow/Add";
import "./styles.css";

export default function App() {
  const items = [{ key: "1", name: "File 1" }];
  return (
    <Provider theme={defaultTheme}>
      <Table>
        <TableHeader>
          <Column key="name">Header</Column>
          <Column key="action" hideHeader>
            Action
          </Column>
        </TableHeader>
        <TableBody items={items}>
          {(item) => (
            <Row key={item.key}>
              {(column) => {
                if (column === "action") {
                  return (
                    <Cell>
                      <ActionButton>
                        <Add />
                      </ActionButton>
                    </Cell>
                  );
                }
                return <Cell>{item[column]}</Cell>;
              }}
            </Row>
          )}
        </TableBody>
      </Table>
    </Provider>
  );
}

🌍 Your Environment

Software
Version(s)

react-spectrum
3.5.0

react-spectrum/table
3.0.0-alpha.8

Browser
Chrome 86.0.4240.198

Operating System
MacOS Catalina

🧢 Your Company/Team

Adobe/quarry
🕷 Tracking Issue (optional)

Can't reproduce in the sandbox nor in local storybook, closing.


Support web_history_mode setting

fixes:

https://github.com/kiali/kiali-ui/pull/1882
https://github.com/kiali/kiali/pull/3113

Kiali v1.26 will be released in a few hours. It will include your work.
Thanks for your contribution @aimuz  !


[0.9.5-nightly]: CLI panics before auth

Hi,
I've set up a new instance of InfluxDB 0.9.5-nightly-6682752, and encountered a crash when starting CLI influx.
Here's my config file:
reporting-disabled = true

[registration]
enabled = false

[http]
auth-enabled = true

I set auth-enabled = true before creating any user. I then restarted the server and launch influx, which crashed with this panic:
$ influx
panic: runtime error: index out of range

goroutine 1 [running]:
main.(*CommandLine).DatabaseToken(0xc820152000, 0x0, 0x0, 0x0, 0x0)
        /tmp/tmp.wkkqd1PJBq/src/github.com/influxdb/influxdb/cmd/influx/main.go:552 +0x424
main.main()
        /tmp/tmp.wkkqd1PJBq/src/github.com/influxdb/influxdb/cmd/influx/main.go:172 +0xd77

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
        /root/.gvm/gos/go1.5.1/src/runtime/asm_amd64.s:1696 +0x1

goroutine 18 [syscall]:
os/signal.loop()
        /root/.gvm/gos/go1.5.1/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
        /root/.gvm/gos/go1.5.1/src/os/signal/signal_unix.go:28 +0x37

goroutine 19 [select, locked to thread]:
runtime.gopark(0xa89860, 0xc82003c728, 0x99f300, 0x6, 0x18, 0x2)
        /root/.gvm/gos/go1.5.1/src/runtime/proc.go:185 +0x163
runtime.selectgoImpl(0xc82003c728, 0x0, 0x18)
        /root/.gvm/gos/go1.5.1/src/runtime/select.go:392 +0xa64
runtime.selectgo(0xc82003c728)
        /root/.gvm/gos/go1.5.1/src/runtime/select.go:212 +0x12
runtime.ensureSigM.func1()
        /root/.gvm/gos/go1.5.1/src/runtime/signal1_unix.go:227 +0x353
runtime.goexit()
        /root/.gvm/gos/go1.5.1/src/runtime/asm_amd64.s:1696 +0x1

goroutine 24 [runnable]:
net/http.(*persistConn).writeLoop(0xc820166000)
        /root/.gvm/gos/go1.5.1/src/net/http/transport.go:1009 +0x40c
created by net/http.(*Transport).dialConn
        /root/.gvm/gos/go1.5.1/src/net/http/transport.go:686 +0xc9d

And this is the server http log:
[http] 2015/11/03 16:09:12 <IP_ADDRESS> - - [03/Nov/2015:16:09:12 +0800] GET /ping HTTP/1.1 204 0 - InfluxDBShell/0.9.5-nightly-6682752 2ae0ef79-8202-11e5-8001-000000000000 100.36µs

[http] 2015/11/03 16:09:12 <IP_ADDRESS> - - [03/Nov/2015:16:09:12 +0800] GET /query?db=&epoch=ns&q=SHOW+DIAGNOSTICS+for+%27registration%27 HTTP/1.1 401 74 - InfluxDBShell/0.9.5-nightly-6682752 2ae10690-8202-11e5-8002-000000000000 1.432099ms

I guess this is caused by PR #4514, which attempts to execute query SHOW DIAGNOSTICS for 'registration' but fails without authentication.

Fixed by https://github.com/influxdb/influxdb/pull/4644
Thanks for the report @iwinux


Ew-14122: Render profile HTML using JCEF and display it inside the IDE

This PR takes the profiling http response and converts it into a local HTML file which can be opened and displayed using the bundled copy of speedscope. If JCEF is unsupported, the HTML file will instead be opened using whatever default application the user has set for HTML files.
The bundled zip has also been updated to remove the help button and the export button. The help button throws an exception inside JCEF (and isn't really that necessary to use the app) and the export button doesn't seem to work at all when using JCEF. If users wish to export a file the cpuprofile file can be used just like the VsCode extension.

See the image below for an example:


[Request] Animated background tiles

Would it be technical possible to support animated tiles on the background layers? E.g for creating animated water?

I currently do not have much knowledge, but I believe this can be achieved by using sprites instead of backgrounds.
1 - Layer 1: Water
2 - Layer 2: Animated ripple effect.

that could work for just a few waves, but there's only 40 object slots and not much time during hblank.
a better plan is probably to just change the tile data at whatever position in tile memory every few frames

GB Studio would definitely need a proper tile editor (or support for an existing tilemap format, for example: Tiled Map Editor's TMX or JSON map formats) in order for animated background tiles to be feasible and user-friendly.

I was going to ask this same feature (animated tiles for background), like those used in zelda and pokemon.
With sprites only very few elements can be shown.
I don't see why a tiled map editor would be needed, one can use an external one like Tiled.
Can this feature please be added? If not, why not? Is it technically too difficult?  Or is it just a matter of time?
Thanks.

Support for tmx or json files from Tiled as backgrounds would also make it more convenient, so you don't have to export them to PNG when changed.
And when version controlling a GB project It would also make more sense to add the tmx/json files to git than the exported PNGs.


Missing combined index on issue_user issue_id and uid

Description
There is currently no combined index on issue_user uid and issueid.
For a lot of operations these two params are used in the where query and adding the index brought some noticeable performance benefits.
Gitea Version
1.20.5
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
gitea executable
Database
MySQL/MariaDB

Does XORM support combined Indexes?

From docs https://xorm.io/docs/chapter-02/4.columns/

index/index(indexname)
column is index. if add (indexname), the column is used for combined index with the field that defining same indexname.

But I'm not sure how to handle the current case - there is already an index on both fields but no combined.
@lunny how can we solve this? is there a way to add an additional combined index via xorm?

@JakobDev yes, with the same mechanism as for composite unique keys as @KazzmanK already pointed out.
@sebastian-sauer yes, using the mechanism described by @KazzmanK on top.

Not sure i understand correctly - can i just put sth like the following code:
type IssueUser struct {
	ID          int64 `xorm:"pk autoincr"`
	UID         int64 `xorm:"INDEX INDEX(uidtoissue)"` // User ID.
	IssueID     int64 `xorm:"INDEX INDEX(uidtoissue)"`
	IsRead      bool
	IsMentioned bool
}

As i want to keep the index only on UID and add a combined index.

Exactly.

Great - will create a pr with that.

Great - will create a pr with that.

If you need to keep UID index there is no need to have dedicated one, combined (UID,IssueID) index will support querying by UID alone. Just be sure, that XORM`s combined index will be created as (UID,IssueID), but not (IssueID,UID)
type IssueUser struct {
	ID          int64 `xorm:"pk autoincr"`
	UID         int64 `xorm:"INDEX(uidtoissue)"` // User ID.
	IssueID     int64 `xorm:"INDEX INDEX(uidtoissue)"`
	IsRead      bool
	IsMentioned bool
}

Other question, what if I need to have two combined indexes , (UID,IssueID) and (IssueID,UID), looks like it is not possible.

Currently, xorm doesn't support index sequences. But more than one index is supported.

Currently, xorm doesn't support index sequences. But more than one index is supported.

It supports.

Currently, xorm doesn't support index sequences. But more than one index is supported.

It supports.

Ah, yes. Just forgot that.


[HB-6922] BidMachine SDK 2.4.1

Updated BidMachine SDK to 2.4.1.
Updated Changelog, README, build script to <IP_ADDRESS>.0

@chauduyphanvu it currently does. Will help with the certification. Although, I will need to rebase this PR with main once PR https://github.com/ChartBoost/chartboost-mediation-android-adapter-bidmachine/pull/4 has been merged and released. 👍🏼


addLayout for custom error page is not providing the error props

Versions

nuxt:  v2.15.6
node: v14.17.0

Reproduction
Link to reproduce - https://github.com/fcieminski/nuxt-modules-bug
Steps to reproduce

Start clear nuxt project
Add module.js with new error layout to nuxt.config.js
Visit not created page to see what's happening

What is Expected?
The new registered error layout from module should mimic the way how normal error page is working, so extend the default layout with for example footer and header and also provide the error prop to manage errors.
What is actually happening?
The error page is treated as independent and standalone layout, not respecting the nuxt components structure and not having the error prop.
Here's the structure with error layout inside layout folder

Here's the structure after creating custom error layout module

Minimal code, it's also inside my repo:
Adding custom error page layout

Error page itself:

Empty error object:

The issue is still valid.

We are approaching the Nuxt 2 EOL date (June 30, 2024) - see this article for more information. This is advance warning that I'm going to close this issue then, as it's currently marked as a Nuxt 2 related bug.
If it's a critical or security issue, please do comment and let me know, in case it is possible to address it before the EOL date.
If it's a an issue you think is relevant for Nuxt 3, please feel free to open a fresh issue (or just comment here so I can update labels, etc.). 🙏
Thank you for your understanding and for your contribution to Nuxt. ❤

It's the day, at last. Nuxt 2 is now marked end-of-life.
My apologies we never got round to resolving this bug in the 2.x branch, but we do have to draw a line somewhere. Again, if you think this is still relevant for Nuxt going forward, please feel free to open a fresh issue (or just comment here so I can update labels, etc.). 🙏


fix: AngledGate equality checks angles

Issue #, if available:
Description of changes:
Testing done:
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[x] I have read the CONTRIBUTING doc
[x] I used the commit message format described in CONTRIBUTING
[x] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[x] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Can you briefly describe this change, e.g. what was the previous behavior?


Enable Direct2D and DirectWrite interop

Allow access to native DXGI and D3D resources, so integration with Direct2D and DirectWrite would be possible, I would use libraries like (https://github.com/Microsoft/Win2D), probably you need to create device with BGRA flags.

Hi, we've written a wiki page explaining how to interop ANGLE with other DirectX content. The page is available here: https://github.com/MSOpenTech/angle/wiki/Interop-with-other-DirectX-code
The page even includes a screenshot of interop between ANGLE and Win2D, as you mentioned. Feel free to let us know if you try to interop ANGLE with Win2D (or other DirectX content)- we'd be interested to hear about your experiences.
Thanks!


0.4.2: Startup Script failing due to "Could not connect to the endpoint URL"

Helm Chart version 0.4.2
Startup Script was working last week - now suddenly is not.
Could be something silly I am doing.
Following along with this suggestion for S3 bucket creation
https://github.com/localstack/helm-charts/blob/a470c3fd75187f1edac981a4dfe1ad85ed01e022/charts/localstack/values.yaml#L163
Deployed via binnacle as follows
    namespace: cogito
    release: localstack
    repo: localstack
    state: present
    version: 0.4.2
    values:
      enableStartupScripts: true
      startupScriptContent: "awslocal s3 mb s3://testbucket"
      resources:
        limits:
          memory: 128Mi
        requests:
          cpu: 100m
          memory: 128Mi
      services:
        localstack:
          image: localstack/localstack
          environment:
            - SERVICES=s3
          ports:
            - "4566:4566"
          volumes:
            - /docker-entrypoint-initaws.d

Logs
Waiting for all LocalStack services to be ready
2022-09-26 19:11:53,309 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2022-09-26 19:11:53,311 INFO supervisord started with pid 16
2022-09-26 19:11:54,313 INFO spawned: 'infra' with pid 21
2022-09-26 19:11:55,315 INFO success: infra entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

LocalStack version: 1.1.1.dev
LocalStack build date: 2022-09-26
LocalStack build git hash: 68c507ed

2022-09-26T19:11:57.986  INFO --- [  MainThread] localstack.utils.bootstrap : Execution of "prepare_installation" took 585.35ms
2022-09-26T19:11:58.996  WARN --- [  Thread-112] hypercorn.error            : ASGI Framework Lifespan error, continuing without Lifespan support
2022-09-26T19:11:58.996  WARN --- [  Thread-112] hypercorn.error            : ASGI Framework Lifespan error, continuing without Lifespan support
2022-09-26T19:11:58.998  INFO --- [  Thread-112] hypercorn.error            : Running on https://<IP_ADDRESS>:4566 (CTRL + C to quit)
2022-09-26T19:11:58.998  INFO --- [  Thread-112] hypercorn.error            : Running on https://<IP_ADDRESS>:4566 (CTRL + C to quit)
2022-09-26T19:11:59.052  INFO --- [  MainThread] localstack.utils.bootstrap : Execution of "start_runtime_components" took 1065.70ms
Ready.
/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initaws.d/localstack-init-scripts-config.sh
2022-09-26 19:12:00,515 INFO exited: infra (terminated by SIGKILL; not expected)
2022-09-26 19:12:01,522 INFO spawned: 'infra' with pid 149
2022-09-26 19:12:02,525 INFO success: infra entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

LocalStack version: 1.1.1.dev
LocalStack build date: 2022-09-26
LocalStack build git hash: 68c507ed

2022-09-26 19:12:03,701 INFO exited: infra (terminated by SIGKILL; not expected)
2022-09-26 19:12:04,722 INFO spawned: 'infra' with pid 219
2022-09-26 19:12:05,725 INFO success: infra entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

LocalStack version: 1.1.1.dev
LocalStack build date: 2022-09-26
LocalStack build git hash: 68c507ed

2022-09-26 19:12:06,389 INFO exited: infra (terminated by SIGKILL; not expected)
make_bucket failed: s3://testbucket Could not connect to the endpoint URL: "http://localhost:4566/testbucket"
2022-09-26 19:12:07,390 INFO spawned: 'infra' with pid 302
2022-09-26 19:12:08,392 INFO success: infra entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

LocalStack version: 1.1.1.dev
LocalStack build date: 2022-09-26
LocalStack build git hash: 68c507ed

2022-09-26T19:12:09.416  WARN --- [  Thread-110] hypercorn.error            : ASGI Framework Lifespan error, continuing without Lifespan support
2022-09-26T19:12:09.416  WARN --- [  Thread-110] hypercorn.error            : ASGI Framework Lifespan error, continuing without Lifespan support
2022-09-26T19:12:09.419  INFO --- [  Thread-110] hypercorn.error            : Running on https://<IP_ADDRESS>:4566 (CTRL + C to quit)
2022-09-26T19:12:09.419  INFO --- [  Thread-110] hypercorn.error            : Running on https://<IP_ADDRESS>:4566 (CTRL + C to quit)
Ready.
2022-09-26T19:13:04.771  INFO --- [  Thread-127] l.services.motoserver      : starting moto server on http://<IP_ADDRESS>:50151
2022-09-26T19:13:04.772  INFO --- [   asgi_gw_0] localstack.services.infra  : Starting mock S3 service on http port 4566 ...
2022-09-26T19:13:05.086  INFO --- [   asgi_gw_0] localstack.request.aws     : AWS s3.PutObject => 404 (NoSuchBucket)

Service looks OK
$ kubectl get service | grep "NAME\|localstack"
NAME                             TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)                               AGE
localstack                       NodePort       <IP_ADDRESS>     <none>        4566:31566/TCP,4571:31571/TCP         7m22s

Odd - when I remove
      resources:
        limits:
          memory: 128Mi
        requests:
          cpu: 100m
          memory: 128Mi

things start fine
2022-09-26T19:35:16.063  INFO --- [  MainThread] localstack.utils.bootstrap : Execution of "prepare_installation" took 626.57ms
2022-09-26T19:35:20.115  WARN --- [  Thread-112] hypercorn.error            : ASGI Framework Lifespan error, continuing without Lifespan support
2022-09-26T19:35:20.115  WARN --- [  Thread-112] hypercorn.error            : ASGI Framework Lifespan error, continuing without Lifespan support
2022-09-26T19:35:20.163  INFO --- [  Thread-112] hypercorn.error            : Running on https://<IP_ADDRESS>:4566 (CTRL + C to quit)
2022-09-26T19:35:20.163  INFO --- [  Thread-112] hypercorn.error            : Running on https://<IP_ADDRESS>:4566 (CTRL + C to quit)
2022-09-26T19:35:20.348  INFO --- [  MainThread] localstack.utils.bootstrap : Execution of "start_runtime_components" took 4284.39ms
Waiting for all LocalStack services to be ready
Ready.
/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initaws.d/localstack-init-scripts-config.sh
2022-09-26T19:35:37.514  INFO --- [  Thread-120] l.services.motoserver      : starting moto server on http://<IP_ADDRESS>:49657
2022-09-26T19:35:37.541  INFO --- [   asgi_gw_1] localstack.services.infra  : Starting mock S3 service on http port 4566 ...
2022-09-26T19:35:39.073  INFO --- [   asgi_gw_1] localstack.utils.bootstrap : Execution of "require" took 1720.91ms
2022-09-26T19:35:39.275  INFO --- [   asgi_gw_1] localstack.request.aws     : AWS s3.CreateBucket => 200
make_bucket: testbucket
2022-09-26T19:35:41.204  INFO --- [   asgi_gw_1] localstack.request.aws     : AWS s3.PutObject => 200

When I increase memory to 256Mi it appears better

Thanks for reporting @frankjkelly . Glad you were able to get it working. 👍 Depending on which commands are run and which services are started, potentially the process(es) running in the LocalStack container could take up more than 128MB. Also, seeing a PutObject call in the tests - as S3 objects are partially kept in memory, this might increase the memory consumption as well (depending on file sizes).
Please let us know if we can close this issue, or if there's anything else we can help out with.. Thanks!

@whummer sounds good - please feel free to close - thanks!

FYI ran into the same issue going from localstack 2.1.0 to 2.2.0 (and above) using Helm Chart 0.6.10.
I increased memory from 384Mi to 512Mi and the issue went away.
Basically any time folk hit this add more memory :-)


Limit to matplotlib<3.8.3

Description
Matplotlib 3.8.3 breaks anesthetic. Restricting to beneath this version until this is fixed.
Checklist:

[X] I have performed a self-review of my own code
[X] My code is PEP8 compliant (flake8 anesthetic tests)
[X] My code contains compliant docstrings (pydocstyle --convention=numpy anesthetic)
[X] New and existing unit tests pass locally with my changes (python -m pytest)
[X] I have added tests that prove my fix is effective or that my feature works
[X] I have appropriately incremented the semantic version number in both README.rst and anesthetic/_version.py

Incredible 😢

Actually it's now less clear to me whether this is matplotlib 3.8.3, or python 3.12.

I've been running almost exclusively on 3.12 locally since it released, so I would say probably not

I've just run the test suite locally and no issues on my end, what were you seeing?

Ah -- is the CI/latest-dependencies breaking because of pandas 2.2.0, i.e. #359 ?

yep


Split routes for FHIRcast into STU2+ and STU3

We should aim to support both STU3 and a PowerCast-compatible STU2. There are some conflicts between the two but this can be managed by creating separate routers, exporting the same routes, only with the STU2 router overriding STU3 routes where the PowerCast implementation or STU2 spec conflicts with STU3. These will be hosted on /fhircast/STU2 and /fhircast/STU3 respectively.

Closed as completed in #3292.


feat: add buf.build example

Type of change

New feature or functionality (change which adds functionality)

Test plan

New test cases added

I was expecting one that uses the buf npm package like that client who asked us about it, rather than an added toolchain. Is that the wrong way to do it, or just a different example?

I was expecting one that uses the buf npm package like that client who asked us about it, rather than an added toolchain. Is that the wrong way to do it, or just a different example?

that'd be rules_js + buf.build example which is far different than this one here.

Is that the wrong way to do it,

I can't say "wrong" but suboptimal as you have to workaround many things like plugin paths and output paths.

okay no need to block this one, but the JS one with https://github.com/bufbuild/protobuf-es is the example I'm really interested in.
At that client I think I resolved the problem with plugin paths, at least partway.


[backport] Fix Windows + CUDA 12.2 CI

Cherry-picked from #7851/#7869.

/test cuda122

win122 is green

/test mini

Q: is win + cuda102 known to fail?

Yes, win + cuda102 + float16 is known to be flaky. #7468


Refactor EditBlockoutModal update/delete handlers

Here https://github.com/OfficeMomsandDads/scheduler/blob/f9ec56a199829488c3716711c7cbda4bf54abe91/app/javascript/components/blockouts/EditBlockoutModal/index.js#L104
And here
https://github.com/OfficeMomsandDads/scheduler/blob/f9ec56a199829488c3716711c7cbda4bf54abe91/app/javascript/components/blockouts/EditBlockoutModal/index.js#L55
Both of these functions are huge and packed with complexity that is begging to be refactored but we have to move on to other things now.

Please add a non-dev description of this issue so we can groom it. Thanks! @benjaminwood @nvick

I'm going to close this. It's not a high-value target because the code literally has not been touched since it was implemented.


Nothing happens !

Hello !
So, I've installed Java and downloaded MercuryTrade.rar. I launch it, it shows in the tray but that's it. I double click the icon and nothing happens...

Sooooo, I've tried again. Ran the MercuryTrade.exe as admin and it worked...


Use trigen-scripts

[x] trigen-scripts
[x] deps update

Coverage remained the same at 86.792% when pulling 4fcdac73a61950d0ae11a10009a1973572465738 on enhancement/trigen-scripts into cf9aeb5ce54cafd15268012c520d4aad248b42ba on master.


GH-35125: [C++][Acero] Add a self-defined io-executor in QueryOptions

Rationale for this change

Support a custom io-executor in Acero QueryOptions.
What changes are included in this PR?

Allow user to define a customed io-executor.
Are these changes tested?

Currently not
Are there any user-facing changes?
User can specify an io-executor

Closes: #35125

Result<std::shared_ptr<Table>> DeclarationToTable(Declaration declaration,
                                                  QueryOptions query_options) {
  if (query_options.custom_cpu_executor != nullptr) {
    return Status::Invalid("Cannot use synchronous methods with a custom CPU executor");
  }

By the way, should I notice and add io-executor here? @westonpace

By the way, should I notice and add io-executor here? @westonpace

No, that's ok.  In a synchronous context we need to specify the CPU executor (because we are going to use a serial executor).  However, it is ok if there is a custom IO executor.

Got it, thanks! I'm a bit busy these days, I'll finish it and testing this weekend.

@westonpace comment fixed, mind take a look?

@westonpace I've fixed the comments :-)


Choice of Colors in Browser Coding Window in FreeCodeCamp Challenges for Accessibility for Color Blind

Challenge Name

All
Issue Description

A way to change the background color of the code window from black to white, and the default code color from white to black. I am color impaired and have trouble seeing red characters on a black background.  I believe about 6% of all men have a similar condition.
In the screenshot below, I can make out the characters in red, but it is not easy.  A white background with either black or colored text would make a big difference.
I know that as a workaround I can use an external editor and past the results in the code window, but that might be a little daunting for some absolute novices.
Browser Information

Browser Name, Version: 50.0.2661.102 m
Operating System: Windows 7 Professional Services Pack 1
Mobile, Desktop, or Tablet: Desktop

Your Code
// If relevant, paste all of your challenge code in here

Screenshot

@VincentDiCarlo thanks for the feedback. We strive to make the site as accessible as possible. The closest thing we have within the Free Code Camp site that might help is night mode. You can access this by typing g,t,n within the site. Let us know how that looks to you. Another solution is to look for extensions for your browser that enable color impaired friendly themes.
cc/ @FreeCodeCamp/issue-moderators

Maybe we could come up with a high contrast mode, without a key shortcut, for it most likely would be a permanently turned-on feature for some people.
Do we have an a11y milestone on the works anywhere? Or should this be a separate thing?

We sure should have one a11y milestone! and +1 for a high contrast mode.
/cc @QuincyLarson

@raisedadead @hallaathrad wait - our default mode is very high contrast.

Would this be a third mode?

@QuincyLarson I'd think so, yes. The "night mode" is more of a "stop burning my eyes, it's late and they hurt", rather than a full-on high contrast (less colourful, a11y oriented one). As the op correctly states, a lot of people have trouble reading non-bright colours over dark backgrounds... I'd advocate for a bright grayscale over black backgrounds —very simple, not precisely pretty... but highly functional in these cases in which impairments are actually the main focus over mere aesthetics.

@QuincyLarson as the OP mentions they are having trouble with the code editor itself:

I am color impaired and have trouble seeing red characters on a black background. I believe about 6% of all men have a similar condition.

Refer screenshot in the OP.

I'm red/green color blind (the most common kind) and I think the Night Mode editor is the hardest one to read, expecially when typing and that highlighter kicks in since (depending on what you do) it outputs green text with a red highlight behind the text while typing.
If I may suggest something along the lines of the Atom default syntax highlighter? It's not perfect, but it's a million times easier to read than both the current regular and especially the night mode editor. The editor and site on Codecademy is also a good example on what works.
As a side note: Readability in general can be quite challenging on most of the site that I've seen so far for the same reason; too much use of red/green as a combination as well as value of red/green.
For now I've recieved a tip to install something called GhostText so I can use my own editor instead. It's only a partial solution though as it doesn't change what's outside of the editor bit.

I would love it if there were more theme options, for the site, for the code editing window, etc. The same way that IDE's allow you to customize everything the way you like it.
I've only now found Night Mode; not colorblind, not coding through the night, I just prefer the colors. The default colors annoy and distract me, passively - I can feel a certain distaste in my brain after being on the site for a bit. Especially that darkish pink for  and  etc.

So we should have options to change coloring syntax theme too? @y-o-r-i-s

I also have trouble reading colored text on a black background. A high-contrast setting which keeps the black background would be just as hard to read.


SSO Project AAD B2C technical issues resolution

Describe the issue
To help resolve technical issues involving the SSO teams stand up of the Azure AD B2C service for usage testing
Additional context
In order to stand up the Azure AD B2C service it was found that Global Admin is needed.  This may possibly be done by another role or roles but it is unknown if this is indeed possible, and\or if these other roles could be used to administer the service on a more daily basis.

If this on-going management can be restricted to a B2C 'instance'
If management of this B2C service is more global in nature, and would involve the SSO project team to manage this for any other B2C instances that may have to be created in the future (ie. future responsibility accepted and security practices established that would safe guard this higher level management process - ie. An on-going Operations concern)

Definition of done

Coordinate a solution between MS best practices and SSO team implementation
Conduct research where necessary here to bring a solution together for the SSO testing team
Discuss any on-going operational concerns to be aware for for SSO team, so will be part of their findings
Ensure Azure AD B2C service is enabled and coordinate between the SSO testing team and the ADMS group when needed

B2C guest tenancy will be place under an alternate Dev tenancy being created with the ADMS group.  If there is any technical issue within this upcoming implementation then a PoC B2C guest tenancy will be created under TIDIR - Upcoming work with ADMS group will move this B2C PoC environment creation request forward

This might be solved via the pCard approach Julian is doing if this gets blocked by the time to complete a full review from ADMS

This was solved by way of pcard for the SSO team, as the ADMS team are still working on resolving whether there would be any possible connection back to our BC Gov prod tenancy (IDIR based).  Once they resolve it, a tenancy can be created for the Azure SEA Test enviro - likely will be based in TIDIR

Once ADMS group is comfortable with this process the SSO group can move to creating a 'B2C Service' (tenancy) for more permanent testing under a TIDIR Azure tenancy.  New ticket will be created once SSO team identifies that they are ready to move forward - Closing this initial issue


Default "sidenav-toggler" state

Forgive me for this simple question but how do I set the default state of the sidenav to "Collapsed"?
Thank you.

$("#sidenavToggler").click()

@davidtmiller
How is it possible to achieve collapsed sidenav on desktop but also for menu to remain unchanged (if only add "sidenav-toggled" to /body then mobile version drops link wording)on mobile device?
Thanks


Difference between npm run build/start and Netlify regarding webpack file-loader rules, locales and routing

Describe the bug
When using custom webpack rules in next.config.js and locales, a route such as /[locale]/some/path.js works with npm run build && npm run start but not on Netlify.
To Reproduce
Steps to reproduce the behavior:

Get the sample app with git clone https://github.com/phbernard/netlify-plugin-nextjs-locale-and-route-issue. In this app, next.config.js is using a file-loader webpack rule to expose a worker.
Start it with npm install && npm run build && npm run start
Visit the app, at http://localhost:3000
Using the Dev Tools, Network tab, spot the access to the worker (you may need to refresh the page). You should find a URL such as http://localhost:3000/_next/static/worker/ff2b3b2479e7a9fbaea2244ed1875dfa.js.
Open this URL in a new tab: it works.
Edit this URL to add fr (a locale configured in the app) as a path prefix. For example, http://localhost:3000/fr/_next/static/worker/ff2b3b2479e7a9fbaea2244ed1875dfa.js. This URL works, too.
The app has been deployed to https://silly-wilson-860691.netlify.app/. Visit https://silly-wilson-860691.netlify.app/_next/static/worker/a9f2364fa39c464e6ddf5fd2caccc8fd.js: it works. Visit the locale-prefixed version https://silly-wilson-860691.netlify.app/fr/_next/static/worker/a9f2364fa39c464e6ddf5fd2caccc8fd.js: it does not work

Expected behavior
App behavior should be identical with npm run start and Netlify: locale-prefixed routes should work.
Versions

Next.js: 11.0.1
plugin (if installed at fixed version): N/A

@phbernard lol hello again!! i think i know whats going on. ty x100 for the details/repo. will get to it when i can 🥴

@phbernard hey, i'm finally here! 😅 i tested this against our plugin rewrite and can confirm that it will be working in the rewrite. our goal is to release a beta of the rewrite in the next few weeks for all next users to test against. since you've always been a wonderful issue reporter over here, we'd love for you to try it out when it's ready. i'll circle back here but i wanted to give you an update since i did fork your repo and threw the label on here. hang tight!!!

I'm closing this because the new version of the plugin is out, which fixes this. Thanks for your report!


Retag candidate image after the tests pass

When testing image, retag the tested image if the test pass, so we can avoid doing an additional build in our CI.
Wasn't sure if we dont wanna have this behavior more explicit, by setting an extra envar, something like TEST_AND_RETAG.
@mfojtik @bparees PTAL

@jhadvig add TAG_ON_SUCCESS and make it disabled by default (we only need this in Jenkins). Also you will have to send PR for all other images and update the vagrant-plugin or the Jenkins job to add this variable.

one small naming suggestion, but LGTM

so.....I was already updating the vagrant plugin to just use the candidate images:
https://github.com/openshift/vagrant-openshift/pull/282


Assign a call park policy

Looks like the "Manage users" is not available in Teams Admin Center.
The way to assign a Call Part Policy is

Go to Microsoft Teams admin center > Users.
In the Users page, search for the user by display name or by user name, select the name, and then open user by clicking on the username.
In the Assigned policies section click Edit
Select the Call park policy from the drop down list.

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

ID: 3e03ef3d-81d8-c98f-8427-fe7c008ea30f
Version Independent ID: 17af3418-b94d-f233-60c0-778b2e8dc02b
Content: Call park and retrieve in Microsoft Teams
Content Source: Teams/call-park-and-retrieve.md
Service: msteams
GitHub Login: @lolaj
Microsoft Alias: lolaj

@officedocsbot assign @scanum

@lcansby Thank you for pointing this out.  I have amended the document to read correctly.

@lcansby - We appreciate any feedback that improves the content in the Microsoft docs but we have determined that these changes are not needed. However, in the future we might implement this.

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.

@officedocsbot close


Vue.$destroy(remove) does not trigger "detached" hook on second level children

I have experienced this issue where I have 3 levels of Vue components, calling $destroy on the top most component will not trigger the detached hook on the bottom most child.
By looking at the _destroy function, I think that the issue is that $remove is called last and at this point, on children in the hierarchy $destroy was called, causing them to remove event hooks ($off() as part of _cleanup).
I think that the removal should be brought before those cleanups, and the lifecycle order should be changed.
Evan, please excuse me if I breaking something or making faulty statement, but I couldn't anywhere when the detached hook is supposed to be called. I found one test that validates that is called after destroyed, but in my humble opinion I think that detached should be called before destroyed. After all shouldn't there be a state for a component from detached, to go back to attached, before we have destroyed the instance?
What I mean to say is that having such component hierarchy
A
-B
--C
when calling A.$destroy, the events would be
detached
-detached
--detached
beforeDestroy
-beforeDestroy
--beforeDestroy
--destroyed
-destroyed
destroyed
You can observe it here http://jsfiddle.net/pepbu9cf/
I have a pending proposal for fix, will post soon.

A possible workarround that I tried and works for me is instead of
vue.$destroy(true)

to call
vue.$remove(function() {
  vue.$destroy();
});

Merged #1967


Gdax withdrawFunds not working

I think it's using the wrong API endpoint Post accounts/{account_id}/transactions
It should be POST /withdrawals/crypto

Where do you get the 'crypto' bit from?  The docs says POST /withdrawals/payment-method

https://github.com/timmolter/XChange/pull/1637/commits/e6bb7c5522dae33095d1bac28b2bd60039855965

Thanks for your quick work.

@npomfret Can we also fix this for okcoin?

@MartianTech what's not working?

There are a few things wrong with the current implementation.
First it's the currency symbol. It should be changed to something like this. We also need to differentiate okcoin.com (International) with btc_usd and okcoin.cn with btc_cny.
--- a/xchange-okcoin/src/main/java/org/knowm/xchange/okcoin/service/OkCoinAccountService.java
+++ b/xchange-okcoin/src/main/java/org/knowm/xchange/okcoin/service/OkCoinAccountService.java
@@ -44,15 +44,27 @@ public class OkCoinAccountService extends OkCoinAccountServiceRaw implements Acc
   }

   @Override
-  public String withdrawFunds(Currency currency, BigDecimal amount, String address) throws IOException {
-    String okcoinCurrency = currency == Currency.BTC ? "btc_usd" : "btc_ltc";
+  public String withdrawFunds(Currency currency, BigDecimal amount, String withdrawAddress) throws IOException {
+         //    String okcoinCurrency = currency == Currency.BTC ? "btc_usd" : "btc_ltc";

-    OKCoinWithdraw result = withdraw(null, okcoinCurrency, address, amount);
+         String withdrawCurrency = null;

-    if (result != null)
-      return result.getWithdrawId();
+         if (currency == Currency.BTC) {
+                 withdrawCurrency = "btc_cny";
+         } else if (currency == Currency.LTC) {
+                 withdrawCurrency = "ltc_cny";
+         } else if (currency == Currency.ETH) {
+                 withdrawCurrency = "eth_cny";
+         } else {
+                 throw new IllegalArgumentException("Unsupported currency");
+         }

-    return "";
+         OKCoinWithdraw result = withdraw(null, withdrawCurrency, withdrawAddress, amount);
+
+         if (result != null)
+                 return result.getWithdrawId();
+
+         return "";
   }

Then it's the fee. They have different required fees for currencies.
+++ b/xchange-okcoin/src/main/java/org/knowm/xchange/okcoin/service/OkCoinAccountServiceRaw.java
@@ -1,14 +1,14 @@

 public class OkCoinAccountServiceRaw extends OKCoinBaseTradeService {
   private final String tradepwd;

@@ -38,9 +38,22 @@ public class OkCoinAccountServiceRaw extends OKCoinBaseTradeService {
     return returnOrThrow(futuresUserInfoCross);
   }

-  public OKCoinWithdraw withdraw(String assetPairs, String assets, String key, BigDecimal amount) throws IOException {
-    OKCoinWithdraw withdrawResult = okCoin.withdraw(exchange.getExchangeSpecification().getApiKey(), assets, signatureCreator, "0.0001", tradepwd,
-        key, amount.toString());
+  public OKCoinWithdraw withdraw(String assetPairs, String assets, String withdrawAddress, BigDecimal amount) throws IOException {
+         String fee;
+
+         if (assets.equals("btc_cny")) {
+                 fee = "0.0001";
+         } else if (assets.equals("ltc_cny")) {
+                 fee = "0.001";
+         } else if (assets.equals("eth_cny")) {
+                 fee = "0.01";
+         } else {
+                 throw new IllegalArgumentException("Unsupported currency");
+         }
+         fee = "0";
+
+    OKCoinWithdraw withdrawResult = okCoin.withdraw(apikey, assets, fee, tradepwd,
+                   withdrawAddress, amount.toString(), "okcom", signatureCreator);

     return returnOrThrow(withdrawResult);
   }

The withdraw method in OkCoin.java is missing a parameter "target" as required in the API doc
https://www.okcoin.com/about/rest_api.do
target: withdraw address type. okcoin.cn:"okcn" okcoin.com:"okcom" okes.com："okex" outer address:"address"

After I fix those, I keep getting a 10007 error code meaning "Signature does not match". I'm using the same API key and secrete key for trading, which works fine.
Then I'm stuck because I don't know how to debug the signing.
@npomfret Hopefully you can help. Thanks in advanced.

Sounds like you have a good handle on this - why not submit a PR yourself?

Signature does not match - sounds like a problem in the digest to me.  Maybe the parameters aren't being included in the signature?

I'm not sure. That part is beyond my understanding. Hope you can figure out.

#1710 Created a new issue to track this bug.


Check for python the varnish way

this fixes an issue where, if a python2 is found, this is attempted with vmodtool

Thanks for the PR. I've applied a slightly different fix.


[NetAppFiles] Anf 9085 update swagger rest api to 2020 11 01

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@audunn I think the only missing part is for you to reply the question about adding x-ms-secret. Since you didn't commit & push your base api (as the initial push) and then on top of that applied your new changes I don't have a base api to compare your updates with.
For future PRs, please commit and push your base api (as is) as the first push then start making changes as future commits, this expedites the review process and we can focus only on the changes.

@audunn I think the only missing part is for you to reply the question about adding x-ms-secret. Since you didn't commit & push your base api (as the initial push) and then on top of that applied your new changes I don't have a base api to compare your updates with.
For future PRs, please commit and push your base api (as is) as the first push then start making changes as future commits, this expedites the review process and we can focus only on the changes.

commit & push

Hi @jorgecotillo, well that is interesting, thing is initially I was told you just needed an initial commit for base comparison and that is what we have been doing for the past few updates. That is, we have been creating an initial commit then applying changes in subsequent commits and then we push. That you need that commit pushed as well actually explains a lot and we will make sure to push that initial commit from now to create a good base to compare from .
Thank you for clearing up that misunderstanding for us.

commit & push

Hi @jorgecotillo, well that is interesting, thing is initially I was told you just needed an initial commit for base comparison and that is what we have been doing for the past few updates. That is, we have been creating an initial commit then applying changes in subsequent commits and then we push. That you need that commit pushed as well actually explains a lot and we will make sure to push that initial commit from now to create a good base to compare from .
Thank you for clearing up that misunderstanding for us.

ARM signed off

ARM signed off

@yungezz  Can we move forward with this?

@yungezz  Can we move forward with this?

@yungezz Can we move forward with this, are there any more issues to address?

@yungezz Can we move forward with this, are there any more issues to address?

hi @msyyc, could you pls check impact to Python SDK? thanks

hi @msyyc, could you pls check impact to Python SDK? thanks

hi @audunn, is the change deployed to Prod already? thanks

hi @audunn, is the change deployed to Prod already? thanks

hi @audunn, is the change deployed to Prod already? thanks

@yungezz what do you mean?  The service yes.

hi @audunn, is the change deployed to Prod already? thanks

@yungezz what do you mean?  The service yes.

Please hold off on merging for now we are looking into possible small issue with python SDK. Should be resolved soon.

Please hold off on merging for now we are looking into possible small issue with python SDK. Should be resolved soon.

@yungezz can we move forward with this?

@yungezz can we move forward with this?

once @msyyc confirmed impact ot Python SDK, it's ok to merge. talking with him offline.

For python, the PR is OK

hi @j5lim you're in Change Request status, could you pls approve the PR if no more concern? thanks

@yungezz can we move forward with this?

/azp run

@yungezz can we move forward with this issue that was found just after this was merged https://github.com/Azure/azure-rest-api-specs/pull/12852?

@yungezz can we move forward with this issue that was found just after this was merged #12852? No SDK's have been created or released yet.

add @jianyexi to help on #12852


[proposal] CPU Normalization

What is your proposal:
Introduce mechanism to normalize CPU computing power of heterogeneous Kubernetes Nodes for CPUShare workloads.
In other words, it makes workloads with the same CPU request get the same CPU computing power on different Nodes with different CPUs.
Why is this needed:
It's quite common for users to have a Kubernetes cluster with heterogeneous nodes nowadays. As CPUs with different architecture and generations may have large performance gap, different pods of workload with the same CPU request may get very different CPU computing power and thus leads to resource waste (for those running on powerful CPUs) or unexpected application performance degradation (for those running on less powerful CPUs).

/assign

/remove-lifecycle stale


Improve line length calculation in ClassAndFunctionHeaderFormatRule

Fixes StringIndexOutOfBoundsException that can happen for class without body when max line length is specified.
Fixes line size calculation for secondary constructor and function.
How fix works: Just take entire line size, without any attempt to understand where is primary constructor, secondary constructor or class body. If line doesn't fit, than we should break parameter list definition into several lines.

As I understand test passes on Mac OS but fails on Windows? Strange... I tried to avoid that by using System.lineSeparator(). I'll investigate that further.

The problem is that System.lineSeparator() on Windows returns \r\n (as expected), but data used for tests  still uses \n.
Any ideas how to better handle that?

@MyDogTom Thank You :bowing_man:


desync prob liveshare

Product and Version [VS/VSCode]:
OS Version [macOS/Windows/Linux]:
Live Share Extension Version:
Target Platform or Language [e.g. Node.js]:
What were you doing when you encountered the desync?
How often have you encountered desyncs?

Hey @PaulTAI , could you provide some more info about the desync (the more the better!)? The questions listed above are good starter ones - what were you doing when it happened, and how often does this happen to you? Also, how long was the Live Share session running before it happened?

Closing this issue due to lack of activity.


Feature/more flexibility for managed object names

Our use case for frodo is not executing correctly due to the logic in place to decide what the managed object name should be.
In a cloud deployment, the managed objects (user, application and organization) get the realm prefix, but in other types that is omitted, e.g.

cloud: managed/alpha_user
forgeops: managed/organization

We are working on replicating the alpha & bravo realm in a local deployment, so having some flexibility on this is needed.
Do you think this can be retrofitted into the 2.X codebase and released?  Currently we are relying on a fork for our needs.
If this is accepted, once we can migrate to 3.X I am happy to apply this to v3 too.
Also added cli option in this PR: frodo-cli#464
Thanks!

There is no v2 branch - a branch would need to be created from v2.3.1-0 to allow this to correctly target the correct codebase.


Couldn't understand how to test on one instance

Hello i was trying to implement this model on a small application im having two problems:
1- is there a function that i d give the model and the niftii of one patient or the multiple niftii of one patient and it returns a segmented nifti something like test( OneData,Model) : segmentation or isn't there anything like that in this git.
2- Can this run on cpu only or do i need a gpu
Thanks in advance
Great work

You can use test.py https://github.com/himashi92/vizviva_brats_2021/blob/main/test.py to make predictions for the given patient data. In this repo, I primarily focus on brain tumor segmentation and patient data comprises multiple modalities.
Yes, you can use a CPU, but I recommend using GPU for both training and inference time.

Since there is the pretrained model I was thinking if im not doing a retraining but a simple one data segmentation it ll be fast even on gpu the problem i had working with your test.py is :
line 85 - 86 you have this :
if ngpus == 0:
raise RuntimeWarning("This will not be able to run on CPU only")
and to use test.py do I have to put data in the folder dataset ? cause I was looking to just load them by path each time

Remove that code fragment. Try using device = torch.device("cpu"), and load model to cpu instead of gpu like this model.to(device).
You have to give your folder dataset path for input_dir parameter https://github.com/himashi92/vizviva_brats_2021/blob/main/config.py#L6

yeah but this is used to do a bunch of predictions like all the test data or train data or ...
Sorry to bother you but what im looking for is just one data prediction im working on a niftii visualizer where he ll chose from the GUI the file he wants and i want based on the file he chose i do the prediction and segmentation just for that.
Can you tell me what i have to do ?
And thanks so much for your help

What is the dataset you gonna use? Is it this brats dataset?
So basically, this model works for multi-modal nifty images. Therefore, when you choose a nifty file you have to choose the folder which has four modalities in it, not a single nifty file. For example, if you choose the patient_01's folder (that is BraTS2021_00000),  the file structure looks like this.
BraTS2021_00000
|--------------BraTS2021_00000_flair.nii.gz
|--------------BraTS2021_00000_t1.nii.gz
|--------------BraTS2021_00000_t1ce.nii.gz
|--------------BraTS2021_00000_t2.nii.gz
|--------------BraTS2021_00000_seg.nii.gz
So the chosen input dir from GUI should be BraTS2021_00000 folder path.

It shouldnt use the file : BraTS2021_00000_seg.nii.gz isn't this the result file what the model should give as output ?
and for the rest yes i ll be giving it :
|--------------BraTS2021_00000_flair.nii.gz
|--------------BraTS2021_00000_t1.nii.gz
|--------------BraTS2021_00000_t1ce.nii.gz
|--------------BraTS2021_00000_t2.nii.gz

yes, you are right. But this will be handled by code.

Thanks so much


replace scipy

Replace scipy clustering with rust according #62 issue

Closes #62

Before merging, we should check clustering on some real-world examples that we have from OSS-Sydr-Fuzz.


docs: breaking changes to elevation need to be documented in guides

Bug, feature request, or proposal:
Proposal/Bug
What is the expected behavior?
New behaviors and breaking changes should include changes/updates to the existing guides, Elevation and Theming in this case.
What is the current behavior?
From the CHANGELOG:
Breaking Changes

elevation: Because mat-elevation usages have been moved out of component stylesheets, users who have
not invoked a theme mixin will not see any elevation shadows on Material components.
However, users that have created a custom theme which lacks the elevation property will
still see the default black shadows.

Additionally, users who want to use themed elevations in their custom components can create
their own shorthand mixin:
@import '~@angular/material/theming';

$myTheme: ...

@mixin my-elevation($zValue) {
  @include mat-theme-elevation($zValue, $myTheme);
}

and then invoke angular-material-theme with the $myTheme variable.
What are the steps to reproduce?

Have an Angular Material project with a custom theme based on v6
Upgrade to v7
It's not clear how to add the elevation property to a custom theme and it is not documented in Defining a custom theme
Try to learn more about mat-theme-elevation but it's not documented in the Elevation Guide

What is the use-case or motivation for changing an existing behavior?
The guides and docs should describe the new behavior and configuration. It shouldn't be required for new users to read the changelog to find out about mat-theme-elevation.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 6->7
Angular Material 6->7
TypeScript 2.7.2->3.1.x
All browsers
Is there anything else we should know?
This came from a question on Gitter.

This info is also not present at https://update.angular.io, and having it there would simplify the migration. Or just a quick reminder when there are breaking changes, with a link to the changelog. While most of us naturally goes to the changelog before upgrading (or after seeing something off in our layout), I think having the info directly in the update-context would be good as well.

Closing this since the transition was 4.5 major versions ago


it doesn't work on routers for some reason.

shodan generates a different  hash than the tool does and also the modems doesn't use the fav.icon direct url but
a custom one like images/banner.ico
or even gifs
so what's the work around ?

do you have a concrete and documented example?

Use the -fu / --favicon-url argument

@pielco11
python favUp.py --favicon-url https://xx.xxx.xxx.xxx/favicon.ico -sc
[+] iterating over favicon URLs | processing https://xx.xxx.xxx.xxx/favicon.ico: : 0it [00:00, ?it/s]

just tried it works thanks 😁


Catch exceptions in DoBuild and print them in a way that Github will highlight

From https://discord.com/channels/783806589991780412/803747594378936361/1183251540262277135

Open issue: should we (just) re-throw the same exception, or should we add a call to EditorApplication.Exit(); in this case?


Does not prefer ipv6 for connections to the VAC

When connecting to the VAC (when registering), the agent does not prefer ipv6.  It should.

Agent deprecated. Check https://github.com/varnish/vagent2


MetricLegendThrshold width weirdness

I tried to drop a map and a legend into my app with:
          <MetricUSNationalMap
            regionDB={regions}
            metric={MetricId.OPIOID_DEATHS}
          />
          <MetricLegendThreshold metric={MetricId.OPIOID_DEATHS} orientation="horizontal"/>

and got:

That is ridiculously wide, so I added width={300} and lost centering:

I think:

Setting the width explicitly should preserve centering.
We might want a default width that's not full-width so you don't have to explicitly set it.
We might want to consider having the map include a legend by default (with a good default width) and let you pass includeLegend={false} if you want to disable it.

I originally wrapped the legend in AutoWidth so that it would always grow to the size of whatever parent container it is wrapped in (in this case, it didn't have a wrapper of its own so it grew to the width of the wrapper it shares with the map assumedly).
In this PR, I add a wrapper in LegendThresholdHorizontal that applies the passed with as the legend's maxWidth (similar to our vax thermometer in CAN).
Im not 100% sold on the idea of making it centered by default -- I kind of feel like alignment should be set in the context of implementing (in the case of your demo homepage, a wrapper that centers all of the items it contains). what do you think @mikelehen?

re: your 3rd point, do you think this might call for a MetricMapBlock component? 😁

@chasulin Thanks, Chelsi!  I think that sounds good though I'm not 100% sure without trying it.  Mostly I just want to minimize the steps and fiddling necessary to get a map onto a homepage. 😁   So yeah, on that note a MetricMapBlock component does seem appealing as well!


Merge auxillary containers to reduce pressure on container runtime

https://github.com/neondatabase/autoscaling/issues/711#issuecomment-1893637974 suggests there is no system in how long every container takes to be created/started.
This can be explained by the fact that containerd has to create and run each container. In the peaks it might be overwhelmed, thus sporadic queues might occur.
The idea is to reduce the number of containers. In the best case we need only one - main container with QEMU.

A couple notes:

IIRC there's three reasons we require init containers:

To make image loading easier (see init-rootdisk, or [when using a custom kernel] init-kernel)
To perform privileged operations without giving neonvm-runner those privileges (see neonvm-runner)
For setting up iptables rules externally (cplane injects an extra init container to do this, because (a) it's not natively supported by neonvm, and (b) using an init container means the process is the same for k8s-pod computes)

Given this, there's several reasons in practice we may need to keep at least one init container. But I'm generally +1 to reducing the number of init containers where we're able to.

As the result of discussions with @sharnoff and @ololobus I intend to do the following changes:

Merge init-rootdisk and sysctl containers (#769)
Move iptables configuration logic from compute-init to neonvm-runner, thus dropping compute-init
Get rid of the init container by:
a. Merging compute and runner images, so there is no need to copy disk
b. Configuring parent network namespace, so that sysctl is not needed

status: Two PRs are ready (#769 and #782), need review on those. Planning to open a follow-up to #782 to refactor neonvm-runner.

status: #769 and #782 still pending, reviewed & need to reply. #790 opened and should help as well, WIP.
Previously blocked on deploy of startup metrics; they aren't yet on prod, but should be this week.

#769 is in production since yesterday, and the graph suggests 1s reduction it timings (at least for the fastest ones):

#782 is merged, but the enablement on cplane side is WIP: https://github.com/neondatabase/cloud/pull/10630
#790 is still WIP.


fix: update webGLContextAttributes powerPreference type

This PR is an addition to https://github.com/jeffreylanters/react-unity-webgl/pull/543
It updates the Type of the powerPreference attribute from the unityConfig object webglContextAttributes.
This attribute accepts the values of 0, 1 and 2 instead of 'default', 'low-power' and 'high-performance'.

@jeffreylanters
Hello!
I was wondering if there is something missing so as to merge this PR.

Excuse me @forforfos, I've had a lot going on privately, so release the PR was delayed a bit. I'll merge and release it this week. Thanks for checking with me! 🙌🏼

Released in https://github.com/jeffreylanters/react-unity-webgl/releases/tag/v9.5.1
Thanks for your contribution!

Excuse me @forforfos, I've had a lot going on privately, so release the PR was delayed a bit. I'll merge and release it this week. Thanks for checking with me! 🙌🏼

No worries friend! I was just wondering if I was missing something to complete the PR!
Thank you very much for your time and feedback! <3
On a separate matter, if you have time, check this out at some point! https://github.com/jeffreylanters/react-unity-webgl/discussions/544 I would really like to implement it, and it is really fast and easy I think!
kisses


fix(doc): fix salvo framework name

PR Info

Closes

Dependencies:

Dependents:

New Features

[ ]

Bug Fixes

[ ]

Breaking Changes

[ ]

Changes

[ ]

Thanks for catching this!


I want to use calc() in my map, with value-references

Simple solution allows calc(), but not internal references
Full solution requires a syntax proposal

closed by ee00ecf


include dormancy period in "winter" crop calendars

@angui3 could you confirm this is part of the reiteration of current adaptation of  crop calendars?


Auditing Enhancement

Hi @nobodyiam , I found that the auditing in this project is achieved by calling com.ctrip.framework.apollo.biz.service.AuditService#audit(java.lang.String, java.lang.Long, com.ctrip.framework.apollo.biz.entity.Audit.OP, java.lang.String) every time we perform CUD operations, one example is in the class com.ctrip.framework.apollo.biz.service.AppNamespaceService:
  @Transactional
  public void createDefaultAppNamespace(String appId, String createBy) {
    // ...
    auditService.audit(AppNamespace.class.getSimpleName(), appNs.getId(), Audit.OP.INSERT,
                       createBy);
  }

this causes the auditing scatters everywhere, I'm planing to refactor this by using EntityListeners and AuditingEntityListener provided by Spring, which gathers all auditing operations in one place and no need to call audit explicitly.
If it is good to you, I'll work on it ASAP.
Regards.

Sounds a good idea.


Link to documentation for vkEnumerateInstanceExtensionProperties links intead to docs for vkEnumerateDeviceExtensionProperties

This is under the "Command wrappers" section in Chapter 2. Overview

Fixed.


[Lovelace] Memory leak

After leaving running the home assistant tab with lovelace for a while ( approx. 10 hours ) the ui becomes more and more unresponsive, after another while ( after a day ) chrome kills the tab.
I attached a screenshot showing memory and cpu usage from the home assistant tab. It shows that ha is using more than 3 gigs of Ram with a constant 100% cpu. Usually a force refresh resolves the issue but it happens after some time again ...

This isnt happening with standard HA gui. Im also attaching my config maybe it helps.
ui-lovelace.yaml.zip

Let me guess, you are embedding live camera streams that you would not have in the normal UI?

i had them in normal ui before ( 1 doorbird live camere + 1 doorbird last motion )
and they are on a different tab than i am looking at currently.
Never experienced this with the notmal UI before

remove some cards and find the card-type that is causing issues

Closing for lack of feedback.


TypeError: undefined is not an object (evaluating 'args.length')  yslow.js:5 in global code

phantomjs yslow.js --help
TypeError: undefined is not an object (evaluating 'args.length')
yslow.js:5 in global code

Same issue here on version 3.1.8

I have the same issue with version 3.1.8


Pagination breaks if there are too many total results

It's a bug with the es query, it has limitations 10k results. Need to research scroll or search after (maybe wait for es upgrade )

ES can easily show the last 10k items, if you want to retrieve more it becomes very complex.
Recommendations :

remove endpoint  /api/v1/aquarius/assets . This will always fail because we have more than 10k assets. At the end of the day this is not that usefull.
when a search result returns more than 10k display only the pages ( 476 pages in our case)  for the first 10k results and show a message like More than 10k results were found, displaying the first 10k. Please refine your search

@kremalicious @alexcos20 thoughts?


Image preview aspect ratio incorrect

What system are you running Yazi on?
Windows
What terminal are you running Yazi in?
Windows Terminal v1.22.3232.0
yazi --debug output
Yazi
    Version: 0.4.2 (5cfcab3 2024-12-20)
    Debug  : false
    Triple : x86_64-pc-windows-msvc (windows-x86_64)
    Rustc  : 1.83.0 (90b35a62 2024-11-26)

Ya
    Version: 0.4.2 (5cfcab3 2024-12-20)

Emulator
    Brand.from_env      : Some(Microsoft)
    Emulator.detect     : Emulator { kind: Left(Microsoft), light: false, cell_size: Some((10, 20)) }
    Emulator.detect_full: Ok(Emulator { kind: Right(Unknown { kgp: false, sixel: true }), light: false, cell_size: Some((10, 20)) })

Adapter
    Adapter.matches: Sixel

Desktop
    XDG_SESSION_TYPE           : None
    WAYLAND_DISPLAY            : None
    DISPLAY                    : Some("<IP_ADDRESS>:0.0")
    SWAYSOCK                   : None
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

NVIM
    NVIM          : false
    Neovim version: 0.10.2

Variables
    SHELL           : None
    EDITOR          : Some("vim")
    VISUAL          : None
    YAZI_FILE_ONE   : Some("C:\\Users\\<username>\\Scoop\\apps\\git\\current\\usr\\bin\\file.exe")
    YAZI_CONFIG_HOME: Some("C:\\Users\\<username>\\.config\\yazi")
    YAZI_ZOXIDE_OPTS: None
    FZF_DEFAULT_OPTS: None

Text Opener
    default     : Some(Opener { run: "code %*", block: false, orphan: true, desc: "code", for_: None, spread: true })
    block-create: Some(Opener { run: "code -w %*", block: true, orphan: false, desc: "code (block)", for_: None, spread: true })
    block-rename: Some(Opener { run: "code -w %*", block: true, orphan: false, desc: "code (block)", for_: None, spread: true })

Multiplexers
    TMUX               : 0
    tmux version       : program not found
    tmux build flags   : enable-sixel=Unknown
    ZELLIJ_SESSION_NAME: None
    Zellij version     : program not found

Dependencies
    file          : 5.45
    ueberzugpp    : program not found
    ffmpeg/ffprobe: 7.1 / 7.1
    pdftoppm      : 24.08.0
    magick        : 7.1.1-41
    fzf           : 0.57.0
    fd/fdfind     : 10.2.0 / program not found
    rg            : 14.1.1
    chafa         : 1.14.5
    zoxide        : 0.9.6
    7z/7zz        : 24.09 / program not found
    jq            : 1.7.1

Clipboard
    wl-copy/paste: program not found / program not found
    xclip        : program not found
    xsel         : program not found

Describe the bug
The preview is always using a wrong aspect ratio. For instance, I have created a sample image of a 100x100 white square with
magick.exe convert -size 100x100 xc:white image.png

but it is rendered as a 160x205 white square in the preview.

Minimal reproducer
Create a sample image as mentioned above using magick.exe convert -size 100x100 xc:white image.png and then use yazi with the default config to preview the image.
Anything else?
Given that chafa results in the same aspect ratio, it might be something related to the pixel height and width. Can we manually set it to something else like with chafa's --font-ratio argument.
Checklist

[X] I tried the latest nightly build, and the issue is still reproducible
[X] I updated the debug information (yazi --debug) input box to the nightly that I tried
[X] I can reproduce it after disabling all custom configs/plugins (mv ~/.config/yazi ~/.config/yazi-backup)

I can't reproduce it by following your steps:

Are you sure you're using the default config right? Can you reproduce it on the latest nightly 0.4.3?

I can't reproduce it by following your steps:

I guess it's due to the different fonts we use. Please try setting the terminal to use Sarasa-Term-SC-Nerd to see if you can reproduce the problem. For me, the issue persists if I use another powerline font with CJK support like Consolas-with-Yahei, but goes away if I switch to the original Consolas font. That is why I was specifically bringing up the --font-ratio option in chafa as I think the issue is likely related to how the fonts are created/patched.

OK, after applying the Sarasa-Term-SC-Nerd font to the MS Terminal, I can reproduce the issue.
However, I can't reproduce it in any of the other terminals I have installed that support the Sixel graphics format (iTerm2, WezTerm). They all use the Sarasa-Term-SC-Nerd font, and the graphics maintain the correct aspect ratio:

So, I suspect this is a bug with MS Terminal - it should maintain the image's aspect ratio when rendering graphics, since it's an image, not text. This isn't too surprising because they recently added Sixel support and it's still in the preview phase.
In this case, I don't think adding --font-ratio is reasonable, since it only addresses an MS Terminal-specific bug, and it doesn't seem to be very user-friendly - users should always preview images with the correct aspect ratio, no matter what font they're using, without having to manually adjust any configurations.
I suggest you report this issue to MS Terminal to request their support. Closing as not Yazi


File log devices opened by mixlib-log should be closed.

Ruby does not have a destructor concept so the opened files should be closed explicitly.
The Ruby Logger which is used as a default logger here does not close log devices it opened until #close method is called. When #rest! happens the logger instance gets destroyed but the #close method
is not triggered.
This patch should help to solve the problem described here: https://github.com/chef/chef/issues/3435

I have addeed comment to the code explaining the "bad idea".

I have just rebased branch on latest master and make PR ready to be merged.

👍

Seems like a reasonable thing to do. @chef/client-core review?

👍

👍


🔄 Synced file(s) with product-os/secrets

Synced local file(s) with product-os/secrets.

This PR was created automatically by the repo-file-sync-action workflow run #1523534446

@balena-ci I self certify!

@balena-ci retest


Unit | Component | sl modal body: There are no references to Ember.$, $ or jQuery

not ok 530 PhantomJS 1.9 - Unit | Component | sl modal body: There are no references to Ember.$, $ or jQuery
    ---
        actual: >
            null
        message: >
            Died on test #1     at test (http://localhost:7357/assets/test-support.js:3025)
                at testWrapper (http://localhost:7357/assets/test-support.js:6192)
                at test (http://localhost:7357/assets/test-support.js:6205)
                at http://localhost:7357/assets/tests.js:25279
                at http://localhost:7357/assets/vendor.js:152
                at tryFinally (http://localhost:7357/assets/vendor.js:33)
                at http://localhost:7357/assets/vendor.js:158
                at http://localhost:7357/assets/test-loader.js:60
                at http://localhost:7357/assets/test-loader.js:51
                at http://localhost:7357/assets/test-loader.js:82
                at http://localhost:7357/assets/test-support.js:6024: Attempted to wrap $ which is already wrapped
        Log: |
    ...

Will likely be resolved by https://github.com/softlayer/sl-ember-components/issues/1503

Resolved by https://github.com/softlayer/sl-ember-components/issues/1503


Laravel 11.x Compatibility

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 11.x.
Before merging, you need to:

Checkout the l11-compatibility branch
Review all comments for additional changes
Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

:warning: The latest version of Laravel has a dependency for phpunit/phpunit of ^10.5. If you would like to also upgrade your tests, you may run the PHPUnit 10 Shift for free.

:warning: Shift detected GitHub Actions which run jobs using a version matrix. Shift attempted to update your configuration for Laravel 11. However, you should review these changes to ensure the desired combination of versions are built for your package.

:alembic: Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.
To do so, temporarily add Shift's fork to the repositories property of your composer.json:
{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/blade-iconsax.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:
{
    "require": {
        "saade/blade-iconsax": "dev-l11-compatibility",
    }
}

Finally, run: composer update


Incorrect price in Marketreporter.java        orderEntered.price       = price;

MarketReporter.java in orderEntered method is showing incorrect price in
orderEntered.price       = price;
For a price of 100, its printing 10000 with 2 leading Zero
However ticket is showing the correct price
Does it require some unpack?

The trading system as well as the native protocols use the minimum price increment, please see e.g. the PMD protocol specification.

It doesn't even look like a minimum price increment.
For the very first order of Quantity 1 and Price as 100, it shows Quantity as 1 and Price as 10000
I am still wondering, how ticker is showing the correct price, which is 100

Well, the minimum price increment for that particular instrument appears to be 0.01, right? 🙂

Where is the minimum price increment defined?
I am running the default system with AAPL instrument

It is defined in the configuration files for the applications.


typo: articles/backup/backup-azure-sql-database.md

Double word "up"
manuallly -> manually
MArkplace -> Markplace
Alternatily -> Alternately
pexisting -> existing

@nschonni : Thanks for your contribution! The author, @rayne-wiselman, has been notified to review your proposed change.

Thanks! #sign-off

@ktoliver : Thanks for your contribution! The author, @rayne-wiselman, has been notified to review your proposed change.