Add exercise: rna-transcription

The tests coincide with:
https://github.com/exercism/x-common/blob/master/exercises/rna-transcription/canonical-data.json

Fabulous!


Provide support for minio STS tokens for artifact repositories

Summary
We need support for minio STS tokens to be used in the artifact repository defined in an argo workflow.
Currently, it is not intended to pass session tokens to access the artifact repository in minio.
See https://github.com/argoproj/pkg/blob/master/s3/s3.go#L122 where the passed session token is always an empty string.
Use Cases
We would love to use sts tokens to grant temporal access to the artifact repository as we are using a separate data access process before triggering the workflow.
This process is part of our workflow trigger job which ensures certain requirements.
It is intended that the access to the artifact repository is denied once the session token has expired and another token has to be issued to get access, and therefore the requirements must be checked again.
Our current work-around includes the creation of minio service accounts to grant temporal access to the repository. Eventually, this temporal service account is deleted by a separate tidy-up job.

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

would u like to raise PR @AndreasDisterhoeft ?


Priority in parallel jobs

Is there some way to indicate a priority order in the jobs to execute? We have a limited amount of hosted pipelines, so not all jobs in the pipeline can run at once. However, one of the jobs run significantly longer than the other jobs. We would like to be able to prioritize this job, so that once an agent becomes available for our pipeline, it will first start processing this job. The order of the jobs in the YAML file seems to help queue the job first, but sometimes it is still not the first job to be executed

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

ID: 7458d5b2-1bb7-7d87-7ce6-2b0c430b0155
Version Independent ID: edf5bbd3-a3f0-5426-e985-31290f8afd05
Content: YAML schema - Azure Pipelines
Content Source: docs/pipelines/yaml-schema.md
Product: devops
Technology: devops-cicd
GitHub Login: @vtbassmatt
Microsoft Alias: macoope

You can make a job depend on another job, which will cause the depended-upon job to run to completion before the other(s) start. We don't offer any other prioritization or control than that.


remove entry for individual register in china

remove entry for individual register in china mode
adjust some layout for create-account-modal to fit with & without individual register entry

Seems good when I manually tested it in Firefox.
Why did we remove the flex-grow and justify-content?
When testing the web page things seemed to work with the original CSS, just removing the Individual account html. Is there a specific reason to change the CSS?
The padding-bottom only appears required after removing the flex CSS.

There would be more space above if didn't remove flex css


Update docker images for speeding up volume binding

Ⅰ. Describe what this PR does
Ⅱ. Does this pull request fix one issue?

fixes #XXXX
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

/test fluid-e2e-nightly


Minimal client / server example fails handshaking with "ChunkInit recieved in state 'Closed'"

Your environment.

Version:   v1.6.10
Go 1.12.4

What did you do?
Created minimal client / server example as shown here: https://gist.github.com/richp10/b5afc98353e548533385af55f587da63
What did you expect?
Expected handshake to complete and be able to communicate across the stream.
What happened?
CLIENT:
sctp DEBUG: 08:36:56.509457 association.go:712: [0xc00008c1a0] state change: 'Closed' => 'CookieWait'
sctp DEBUG: 08:36:56.512453 association.go:305: [0xc00008c1a0] sending INIT
sctp DEBUG: 08:36:56.509457 association.go:395: [0xc00008c1a0] readLoop entered
sctp DEBUG: 08:36:56.509457 association.go:418: [0xc00008c1a0] writeLoop entered
sctp DEBUG: 08:36:59.512983 association.go:305: [0xc00008c1a0] sending INIT
sctp DEBUG: 08:37:05.513388 association.go:305: [0xc00008c1a0] sending INIT
sctp DEBUG: 08:37:17.513699 association.go:305: [0xc00008c1a0] sending INIT

SERVER:
sctp DEBUG: 08:36:47.848844 association.go:395: [0xc0000761a0] readLoop entered
sctp DEBUG: 08:36:56.514451 association.go:747: [0xc0000761a0] chunkInit received in state 'Closed'
sctp WARNING: 2019/09/24 08:36:56 [0xc0000761a0] failed to write packets on netConn: write udp [::]:10001: wsasend: A request
 to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a se
ndto call) no address was supplied.
sctp DEBUG: 08:36:56.515451 association.go:430: [0xc0000761a0] writeLoop ended
sctp DEBUG: 08:36:56.515451 association.go:446: [0xc0000761a0] writeLoop exited
sctp DEBUG: 08:36:59.512983 association.go:747: [0xc0000761a0] chunkInit received in state 'Closed'
sctp DEBUG: 08:37:05.513388 association.go:747: [0xc0000761a0] chunkInit received in state 'Closed'
sctp DEBUG: 08:37:17.513699 association.go:747: [0xc0000761a0] chunkInit received in state 'Closed'

This is more likely a misunderstanding on my part than a bug in the library, but I hope you can help in either event!

Huge thanks - yes that works perfectly.  Great project, btw..

That's what I thought too when I came across pion a year ago. I have been using it since then.
(let me close this issue)

@richp10 if you are interested in contributing a example client+server would be amazing!
Something like the DTLS Client/Server examples https://github.com/pion/dtls/tree/master/examples


Problems with the UnlockType

Hey thank you very much for the libraries controlling the Myo. I'm doing a project creating sound from the movements of a dancer. Without your work I would not be able to pull it off personally.
I found an issue though. For me setting the LockType did not work properly. The UNLOCK_TIMED did not do anything and the UNLOCK_HOLD seems to work like UNLOCK_TIMED.
I created a workaround by changing the ENUM.
public enum UnlockType {
UNLOCK_NULL,
UNLOCK_TIMED,
UNLOCK_HOLD
}
For some reason this works for me. UNLOCK_TIMED and UNLOCK_HOLD both react properly now. Maybe something to look into?
Best,
Maarten Zaagman

@zaagman Which version of the library are you using? I'm not sure why what you suggested would work, but older versions of the code may have had a problem.


Add support for Logback's FixedWindowRollingPolicy

With Fixed Window Rolling Policy (archivedLogFilenamePattern: -%i), we have control on the size (maxFileSize) and the number of log files (archiveFileCount) that will reside on the host. We will not have to worry about disk usage warnings.
Recently Size and Time Based Archiving (archivedLogFilenamePattern: -%d-%i) with maxFileSize option has been added as part of commit: 343680b. In this archival policy we have control on the size of each log file (it will rotate the logs and increment the index after maxFileSize is reached), but the archiveFileCount only applies to the number of days worth of files that should be maintained. So on any specific day, files will keep getting rolled over indefinitely with a new index when the maxFileSize is reached. These log files will continue to accumulate as long as it is within the number of days mentioned in archiveFileCount. So we will lose control on the number and size of log files on the host, and disk usage may be a concern.
Proposed Approach:
Include FixedWindowRollingPolicy in FileAppenderFactory. Rolling policy to be used will be based on the archivedLogFilenamePattern -
Time Based Rolling Policy - /tmp/application-%d{yyyy-MM-dd}.log.gz
Size and Time Based Rolling Policy - /tmp/application-%d{yyyy-MM-dd}-%i.log.gz
Fixed Window Rolling Policy - /tmp/application-%i.log.gz
I hope you find this useful. I'm open to suggestions as well. Thanks.

PS: Errors are unrelated to this change.

@jplock Please let me know if you have any suggestions, changes. Thanks!

I think this is a great feature because I just got bit twice in a short period of time by two different applications that spammed the log files and filled up the disk.


UI to change feed title

Many RSS feeds end up with titles like "Your source of the latest and greatest breaking news locally, nationally and worldwide - The Post" and I'd like it to appear as simply "The Post".
A quick scan of the API references the ability to change a feed title. (I'm not sure if this is globally or per user, hopefully the latter). It would be nice if this functionality were available via the UI. Or maybe it is and it's not clear to me?

The ability to change a feed title from the UI is in the to-do list, it's not currently implemented. Currently the API does not support per-user feed titles, that has to be implemented first so it's not just a UI change. For the moment the app simply displays whatever title the feed itself reports.
I'll keep in mind your feedback to give implementing this feature a higher priority.


Add wikipedia like popups

Adds popups for tsconfig links
Popup positioning is not ideal
Related to #1656

This is close! I want to auto-generate the JSON object and then we're good

There we go - thanks @alirezaghey !

Thanks @orta, this looks amazing! I'll look into how we can add MDN and internal documentation pages according to #1656 and also how we can make the popups aware of their position on the page so that they move a little bit to the opposite side like how they do on wikipedia.

I've left some of my ideas on the MDN and docs pages, the tricky thing is making a markdown summary but I've included a pretty reasonable idea for how that could happen.
Re: popup positioning, that's doable - it's just JavaScript and deciding which side is closest to the middle of the page and using that edge to position the popover instead of right now where it's the bottom always. I'd start with maybe doing either above or below first, and then look at left or right


HDFS-17057. RBF: Add DataNode maintenance states to Federation UI

Description of PR
as described in the issue HDFS-17057
add DataNode maintenance states to Federation UI

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
35m 47s

trunk passed

+1 :green_heart:
shadedclient
56m 47s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 34s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
shadedclient
20m 59s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

83m 26s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5775/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5775

Optional Tests
dupname asflicense shadedclient codespell detsecrets xmllint

uname
Linux 10b537e6d3f5 4.15.0-212-generic #223-Ubuntu SMP Tue May 23 13:09:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a23434c7ca181c313cc9e413431126a24cd37914

Max. process+thread count
555 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5775/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Thanks @zhangshuyan0 @goiri  help review and merge it.


OfferPassenger`` type should be DuffelPassengerType not string

OK I promise this is the last one from me today!
Pretty much the same as #653 but for OfferPassenger

Hey – thanks for this, we're very happy you're helping us find and fix issues! We've just released v1.19.0 which contains this fix.


Add real tooltip. Fixes #13

Fixes #13

Thnx for merging :shipit:

Thanks for submitting PR :) I'll release it asap.


Issues/Improvements to Shadertoy support

hey,
I have found this project and it looks really promising. I am working on a project that looks at language models generating shadercode.
Following the examples, I got it working for myself.
However I had several issues.

there is shader.show() but to stop there is shader._canvas.close() (in a Jupyter notebook).
to get the actual frames you can call shader._canvas.get_frame()
Shadertoy always uses the auto canvas, so you can't get it on a fake Canvas for example.
I have two instances of the Shadertoy class to then compare ground truth and generation, the 2nd shader is a frame ahead

Now my questions:

Is there a way to render a sinlge frame (perhaps given a time)?
How are erros in the shadercode handled? right now I seem to get a Jupyter kernal crash. (might be GPU dependant?)
can you access the parser/compiler to figure out where in the  source code a specific function is defined?

My suggestion:

add methods to the Shadertoy class to access the information inside the ._canvas directly
expose more arguments to the __init__() to set canvas, framerate, ... (keep defaults).

Will read through more docs and look at the source, but the low level stuff is too advanced for me, might find some time to contribute myself.

Hi!
General remarks regarding the shadertoy utility:

The current shadertoy is designed to be really plug-n-play, and is not (yet) very configurable.
That said, I'm sure it could be improved, perhaps by adding optional arguments?
The shadertoy was contributed by a user, and since it is not our priority, we are unlikely to improve it ourselves. Though we'd accept contributions to improve it 👍

Is there a way to render a sinlge frame (perhaps given a time)

Not at the moment. Perhaps an option could be added e.g. offscreen that will then use an offscreen canvas and return the screenshot?

How are erros in the shadercode handled? right now I seem to get a Jupyter kernal crash. (might be GPU dependant?)

In most cases the errors should be caught when the GPU shader module is created and a clear error should be printed. A kernel crash should be considered a bug (though it might be one that we cannot fix, because it's cause lies upstream in wgpu-native).

can you access the parser/compiler to figure out where in the source code a specific function is defined?

No, it's opaque. We just call a function that we pass the wgsl, and it produces a GPU module.

expose more arguments to the init() to set canvas, framerate, ... (keep defaults).

This sounds like the most feasible approach to make this utility more flexible 👍

Thank you got the answers.
The original contributor is @panxinmiao if I am reading the pull requests correctly. I will start to write an adapted Shadertoy class that incorporates some of the features mentioned above. From some more digging I did it looks like the time is based on a time.perf_counter() and therefore you don't even get a 0th frame on time 0 but slightly off. Which is one of the requirements I will try to implement first.

The current Shadertoy is a highly encapsulated utility that is used for testing and demonstrating shader code, with very limited customization options. It's great to see someone making improvements to it.

From some more digging I did it looks like the time is based on a time.perf_counter() and therefore you don't even get a 0th frame on time 0 but slightly off.

Actually, here the variable "time" is an accumulation of the increment in time obtained from calling "time.perf_counter()" at each frame rendering. It should start from 0 unless there is a bug, 😅

Here is my experimental setup (the aim is to compare two different shadercodes at the same, and do so via the frame the render). I do my development inside a Jupyter notebook. debug_code is copied from this shader https://www.shadertoy.com/view/4ts3R8 but with the decimal places for print(iTime ...) set to 4. near the end.
from PIL import Image, ImageChops
import numpy as np
from wgpu.utils.shadertoy import Shadertoy as ST

resolution = (512, 420)
# test_codes = [test_code, test_code] # replace with your list of test codes
test_codes = [debug_code, debug_code]
images = []

for code in test_codes:
    shader = ST(code, resolution)
    print(shader._uniform_data["time"])
    shader.show()
    shader._canvas.close()
    frame = shader._canvas.get_frame()
    print(shader._last_time)
    print(shader._uniform_data["time"])
    print(shader._frame)
    img = Image.fromarray(frame)
    images.append(img)
    # del shader # to remove any left overs?

# remove transparent alpha
for i in range(len(images)):
    images[i] = images[i].convert('RGB')

# display images
for img in images:
    display(img)

My output looks the following( and numbers change around a bit every time)

Do you have any direct idea on how to grab the frame when time is exactly 0 or what changes to make instead? I got one busy week, but will find the time to dig around myself soon.

_frame is used internally in Shadertoy and is not intended to be accessed externally. It may not correspond to the real-time variable values in the shader program (in fact, it should represent the corresponding variable values in the shader program at the rendering of the next frame). If you want to consider accessing these real-time properties externally, you would need to organize the code and the simplest way would be to directly map the values from the uniform_buffer.
Currently, Shadertoy does not provide a method for users to explicitly render a specific frame (off-screen). In practice, the rendering is handled by the GUI program, which calls the rendering at the appropriate time based on the refresh rate. Your rendering result above seems to have skipped the first frame, and I'm not sure what the reason is.
However, we can provide a function like snapshot. Iit will immediately render one frame and return the rendered result. This should not be complex to implement.

I just checked the code for “Jupyter Canvas”. As a temporary alternative, perhaps you can try directly calling the internal "Shadertoy._draw_frame()" method.
Like this:
.....
for code in test_codes:
    shader = ST(code, resolution)
    shader._draw_frame()
    frame = shader._canvas.get_frame()
    ......

Note that I did not test on Jupyter notebook, 😅

This kinda works. But it would always give me a single pixel. And I did not figure out why.
After some more digging through all the inherited classes, I found that there is shader._canvas.snapshot()
and put together the following code seems to do what I want: render a single frame at a given time
from PIL import Image, ImageChops
import numpy as np
from wgpu.utils.shadertoy import Shadertoy

resolution = (512, 420)
# test_codes = [test_code, test_code] # replace with your list of test codes
test_codes = [debug_code, debug_code]
frames = []

for code in test_codes:
    shader = Shadertoy(code, resolution)
    shader._uniform_data["time"] = 1.234 #set any time you want
    shader._canvas.request_draw(shader._draw_frame)
    frame = shader._canvas.snapshot().data
    frames.append(frame)

images = []
for frame in frames:
    img = Image.fromarray(frame)
    # remove transparent pixels
    img = img.convert('RGB')
    images.append(img)
    display(img)

I am have only tested this inside a Jupyter notebook. But it does work out for me so far - and I don't have to implement anything myself.

Essentially you're not actually using the shadertoy framework anymore. You're just rendering a full screen quad with a shader. I kind of suspected this earlier.
We could perhaps provide a utility function for this process, similar to the compute shader utility function.

here is the implementation I have been using
from PIL import Image
import numpy as np
import wgpu
from wgpu.utils.shadertoy import *
from wgpu.gui.offscreen import WgpuCanvas as OffscreenCanvas, run as run_offscreen

# custom Class
class ShadertoyCustom(Shadertoy):
    def __init__(self, shader_code, resolution=(800, 450), canvas_class=WgpuCanvas, run_fn=run):
        self._canvas_class = canvas_class
        self._fun_fn = run_fn
        super().__init__(shader_code, resolution)
        self._uniform_data = UniformArray(
            ("mouse", "f", 4),
            ("resolution", "f", 3),
            ("time", "f", 1),
            ("time_delta", "f", 1),
            ("frame", "I", 1),
        )

        self._shader_code = shader_code
        self._uniform_data["resolution"] = resolution + (1,)

        self._prepare_render()
        self._bind_events()

    def _prepare_render(self):
        import wgpu.backends.rs  # noqa

        self._canvas = self._canvas_class(title="Shadertoy", size=self.resolution, max_fps=60)

        adapter = wgpu.request_adapter(
            canvas=self._canvas, power_preference="high-performance"
        )
        self._device = adapter.request_device()

        self._present_context = self._canvas.get_context()

        # We use "bgra8unorm" not "bgra8unorm-srgb" here because we want to let the shader fully control the color-space.
        self._present_context.configure(
            device=self._device, format=wgpu.TextureFormat.bgra8unorm
        )

        shader_type = self.shader_type
        if shader_type == "glsl":
            vertex_shader_code = vertex_code_glsl
            frag_shader_code = (
                builtin_variables_glsl + self.shader_code + fragment_code_glsl
            )
        elif shader_type == "wgsl":
            vertex_shader_code = vertex_code_wgsl
            frag_shader_code = (
                builtin_variables_wgsl + self.shader_code + fragment_code_wgsl
            )

        vertex_shader_program = self._device.create_shader_module(
            label="triangle_vert", code=vertex_shader_code
        )
        frag_shader_program = self._device.create_shader_module(
            label="triangle_frag", code=frag_shader_code
        )

        self._uniform_buffer = self._device.create_buffer(
            size=self._uniform_data.nbytes,
            usage=wgpu.BufferUsage.UNIFORM | wgpu.BufferUsage.COPY_DST,
        )

        bind_group_layout = self._device.create_bind_group_layout(
            entries=binding_layout
        )

        self._bind_group = self._device.create_bind_group(
            layout=bind_group_layout,
            entries=[
                {
                    "binding": 0,
                    "resource": {
                        "buffer": self._uniform_buffer,
                        "offset": 0,
                        "size": self._uniform_data.nbytes,
                    },
                },
            ],
        )

        self._render_pipeline = self._device.create_render_pipeline(
            layout=self._device.create_pipeline_layout(
                bind_group_layouts=[bind_group_layout]
            ),
            vertex={
                "module": vertex_shader_program,
                "entry_point": "main",
                "buffers": [],
            },
            primitive={
                "topology": wgpu.PrimitiveTopology.triangle_list,
                "front_face": wgpu.FrontFace.ccw,
                "cull_mode": wgpu.CullMode.none,
            },
            depth_stencil=None,
            multisample=None,
            fragment={
                "module": frag_shader_program,
                "entry_point": "main",
                "targets": [
                    {
                        "format": wgpu.TextureFormat.bgra8unorm,
                        "blend": {
                            "color": (
                                wgpu.BlendFactor.one,
                                wgpu.BlendFactor.zero,
                                wgpu.BlendOperation.add,
                            ),
                            "alpha": (
                                wgpu.BlendFactor.one,
                                wgpu.BlendFactor.zero,
                                wgpu.BlendOperation.add,
                            ),
                        },
                    },
                ],
            },
        )

    def show(self, time: float = 0.0):
        self._canvas.request_draw(self._draw_frame)
        self._fun_fn()

    def snapshot(self, time):
        self._uniform_data["time"] = time #set any time you want
        self._canvas.request_draw(self._draw_frame)
        if issubclass(self._canvas_class, wgpu.gui.jupyter.JupyterWgpuCanvas):
            frame = self._canvas.snapshot().data
        elif issubclass(self._canvas_class, wgpu.gui._offscreen.WgpuOffscreenCanvas):
            frame = np.asarray(self._canvas.draw())
        img = Image.fromarray(frame)
        # remove transparent pixels
        img = img.convert('RGB')
        return img

def get_image(code, time= 0.0, resolution=(512, 420)):
    shader = ShadertoyCustom(code, resolution, OffscreenCanvas, run_offscreen) #pass offscreen canvas here (or don't)
    return shader.snapshot(time)

which let's you pass the canvas class and run function and also the snapshot method (for offscreen and jupyter)

@Vipitis are you still interested in working on this? To improve the shadertoy class?
ShaderToy is not a core feature of wgpu-py (the wgpu-native wrappers and the GUI backends are!) so it's not in a priority for us as maintainers.
If you're not interested to make the improvements and open a pull request, please close the issue. Thanks!

I am still working on the custom class that adds some functionality: validation via naga (although since it's now merged, maybe there is a less ugly way to do so), uffscreen canvas and off screen run. a snapshot method to render a frame at any given time (might add additional inputs like mouse position soon).
However I am noticing more and more that there is plenty of functionality that I really don't need. So I am close to simply using the compatibility layer (adding some shadercode Infront and some behind) and then using more native function.
I will likely write some form of error parser to point back at the location of the original code.
I will open a PR this weekend, which includes the features I currently have, so you can cherry pick the parts that make sense.
But it's more likely that I will strip a lot of the functionality in the next 2-3 weeks for my project. (which is hosted as a HF space: https://huggingface.co/spaces/Vipitis/shadermatch/blob/main/shadermatch.py#L131)

closing this far. Will work on PRs to add additional built-ins (iDate, iFramerate) and further features (like snapshot for juypter canvas) in the very near future.


Insights for Weather service is now deprecated.

See following URL for more details: https://console.ng.bluemix.net/docs/services/InsightsWeather/index.html
"The revised service is available in Bluemix as Weather Company Data for IBM Bluemix."

It looks like our weather insights service was migrated already to Weather Company Data. We could just change our service name and ensure that it still works, once OpenWhisk is working again. Depends on #379

To confirm, the insights weather service was migrated to be Weather Company Data service. Here is BluePic's service and newly created weather service for reference:
BluePic-Insights-for-Weather       weatherinsights          Free-v2             BluePic                      create succeeded
Weather Company Data-tempp         weatherinsights          Free-v2                                          create succeeded

The API did change, but Vince already updated the swift-watson-sdk awhile back
Additionally, OpenWhisk is currently using version 0.4.1 of that SDK so it includes the weather api updates.
In the end, no further action needs to be taken.


Remove gh-extension topic from this repository

Hi, thanks for sharing a cool project with the world, and for maintaining a GitHub CLI extension.
Your repository abdfnx/gh-resto is an installable CLI extension and has the gh-extension repository topic, which helps it get discovered by gh extension search command. We use the topic to discover public extensions made by the community. All is good here!
However, this repository abdfnx/resto is not an installable CLI extension, and therefore should not have gh-extension topic. By removing the topic from this repo, you could help make gh extension search more efficient. Thank you!

Hi @mislav , no problem


Swap: Use fees from Binance API

Currently fees are hard-coded. We already have transferFees$ to grab single fee for a single swap and multi for double-swap.
Check FreezeView as an example to see how it gets a single fee using useSingleTxFee hook (we don't have such hook for a multi fee yet)

Fee handling resolved by #663

Fee handling resolved by #663


udp_proxy: implement idle timeout and some stats

Another bunch of work towards
https://github.com/envoyproxy/envoy/issues/492.
The remaining work is proper wiring up of upstream cluster
management, host health, etc. and documentation. This will
be done in the next PR.
Risk Level: Low
Testing: New integration/unit tests
Docs Changes: N/A
Release Notes: N/A

@danzh2010 @goaway PTAL

@danzh2010 updated PTAL


Out of memory errors

Getting this with latest CLI:
$ pack-365-linux create-builder dsyer/builder -b builder.toml --no-pull
fatal error: runtime: out of memory

runtime stack:
runtime.throw(0x958008, 0x16)
    /home/travis/.gimme/versions/go1.11.1.linux.amd64/src/runtime/panic.go:608 +0x72

Not really sure what it means. If it means that pack is unusable with less than 32GB RAM then I think that's a bug (I have 8 and it's fine for everything else I do on this laptop).

Yeah, that honestly seems like a bug...

@dsyer The current implementation of create-builder is inefficient when it is run against a daemon. It is slow and essentially loads the entire image into memory. We will be fixing it when we play this issue https://github.com/buildpack/roadmap/issues/17. rebase has a similar problem https://github.com/buildpack/roadmap/issues/18. These issues are near the top of our backlog.
This is due to the way that the go-containerregistry library behaves when operating against a docker daemon (as opposed to a registry). We will be swapping out calls to go-containerregistry with our own implementation in the local case (as we have already done with pack build).

Any thought of improving go-containerregistry and submitting back upstream?

@dsyer We made performance improvements to the daemon implementation of create-builder in<EMAIL_ADDRESS>This problem should be fixed.
Feel free to reopen if you are still seeing suspiciously high memory usage in newer pack versions.


QOSF Monthly  Challenge

Hi @Dark-lord77, did you mean to create this issue? What is it for?

Sorry sir I didn't get that
Did I have done something wrong?
On Wed, 4 Nov 2020, 09:18 Aditya Giridharan<EMAIL_ADDRESS>wrote:

Hi @Dark-lord77 https://github.com/Dark-lord77, did you mean to create
this issue? What is it for?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/qosf/monthly-challenges/issues/3#issuecomment-721496194,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APAK67CHBE4JBHNDS234O2DSODFITANCNFSM4TJPKY5A
.

You opened this issue a couple of hours ago - do you wish to report or suggest something? If not, I will close this issue.

No sir
You can close it
On Wed, 4 Nov 2020, 09:27 Aditya Giridharan<EMAIL_ADDRESS>wrote:

You opened this issue a couple of hours ago - do you wish to report or
suggest something? If not, I will close this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/qosf/monthly-challenges/issues/3#issuecomment-721498335,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APAK67B2V5G63O34NRB3I4DSODGLNANCNFSM4TJPKY5A
.


Implement port mapping

The only current method of hole punching is using a relay (with dcutr being used first before falling back to a relay), however in many devices it may be possible to utilize port mapping as the primary choice before falling back to using a relay, if its available. This should make it possible to allow connections directly without using a relay for direct connections, however some things that should be decided on before implementing:

Should IGD or NAT-PMP be used? We could use both and fall back to former if the latter fails.
What libraries should be used? Should we implement those here, use a crate like igd, or use external library (eg libnatpmp)?
Should there be a interface sitting on top of any library we used so we can swap in and out different implementations to reduce breakage?
What impact would it have on libp2p? During past testing with igd, everything worked fine with peers being able to connect, however this was done with a fixed address and not catching swarm events on any address change. This may need testing to be sure we can add or remove the addresses during those events (by also catching loopback addresses so we can ignore those along with any p2p-circuit addresses).
Should we also have relays be used along side with port mapping in the event port mapping fails for whatever reason (eg device moving from a device that supports it to one that doesnt).
(Long term) What impact would this have on quic (when rust-libp2p supports the transport)? (May do separate testing)
Should this possibly be done upstream in libp2p with separate implementation?

Note:
We should check to determine if we are behind a nat prior to attempting port mapping.
Reference:

https://github.com/sbstp/rust-igd
https://github.com/fengyc/natpmp

Should IGD or NAT-PMP be used? We could use both and fall back to former if the latter fails.

Note that contributing this to rust-libp2p would be very much appreciated. See https://github.com/libp2p/rust-libp2p/issues/558

I completely forgotten about that issue @mxinden. It would be something I like to see in libp2p, just want to make sure its gone about it the right way.

Note:

This is implemented currently (as of 0.3.0-alpha.1) as a background task. If IpfsOptions::port_mapping is enabled, it will attempt to utilize port forwarding when listening on new addresses that contain a private ip (eg 10.xxx.xxx.xxx, 192.168.xxx.xxx, etc). If it been successful, you will be able to communicate with the node without the use of a relay (and if bootstrapping, the node would be dialable).
NatStatus would change to NatStatus::Public(_)
This might change to be in its own behaviour instead, which might allow for better tracking

Note:

UPnP related code been moved to libp2p-nat, which uses IGD and fall back to NATPCP (in the near future, it might get changed to use NATPCP by default)


[doc] ROM README update for fuses

Abandoning this PR in lieu of https://github.com/chipsalliance/caliptra-sw/pull/1742


Missing mapper does not raise an error

When a mapper is missing from the registry, it should throw an error. Instead, it is returning nil.
NoMethodError: undefined method `call' for nil:NilClass```

<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/18704522-missing-mapper-does-not-raise-an-error?utm_campaign=plugin&utm_content=tracker%2F155789&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F155789&utm_medium=issues&utm_source=github).
</bountysource-plugin>

The reason why it happens is that lazy relation sets its internal mapper
registry to an emtpy hash by default. A simple fix is to replace it with
MapperRegistry.new which raises an error when mapper is missing.
On Fri 29 May 2015 at 19:14 Carlisia Campos<EMAIL_ADDRESS>wrote:

When a mapper is missing from the registry, it should throw an error.
Instead, it is returning nil.
# »<EMAIL_ADDRESS>OM::Datastore.relation(:widgets).as(:widgets).one
NoMethodError: undefined method `call' for nil:NilClass
—
Reply to this email directly or view it on GitHub
https://github.com/rom-rb/rom/issues/251.


Release 1.5.2 confuses slot with typicals

I've a node with 4 typicals those use 10 slot as overall. SoulissApp in the DB area report 10 typicals.

Now I cannot control my Souliss network and with OH works well.
Waiting...
Regards
El 30/08/2015 10:10, "Dario Di Maio"<EMAIL_ADDRESS>escribió:

I've a node with 4 typicals those use 10 slot as overall. SoulissApp in
the DB area report 10 typicals.
—
Reply to this email directly or view it on GitHub
https://github.com/souliss/soulissapp/issues/33.

Mine is working.
On Sun, Aug 30, 2015 at 1:23 PM, juanpintom<EMAIL_ADDRESS>wrote:

Now I cannot control my Souliss network and with OH works well.
Waiting...
Regards
El 30/08/2015 10:10, "Dario Di Maio"<EMAIL_ADDRESS>escribió:

I've a node with 4 typicals those use 10 slot as overall. SoulissApp in
the DB area report 10 typicals.
—
Reply to this email directly or view it on GitHub
https://github.com/souliss/soulissapp/issues/33.

—
Reply to this email directly or view it on GitHub
https://github.com/souliss/soulissapp/issues/33#issuecomment-136129535.

which typs ?

I've 1 RGB (4 slots) and 3 Analog values (2 slot each).

could you post a screenshot to understand better? thanks

Haven't a screenshot, in Option/Souliss DB in DB Status is shown 10
typicals. But in the Manual menu I've 4 typicals, 10 are the slots.
Previous SoulissApp was showing the right number of typicals.

Problem solved with 142, my nodes was STALE for a few hours, but before
update was working well
Ty for your work
Regards.
2015-08-31 12:58 GMT+02:00 Dario Di Maio<EMAIL_ADDRESS>
Haven't a screenshot, in Option/Souliss DB in DB Status is shown 10
typicals. But in the Manual menu I've 4 typicals, 10 are the slots.
Previous SoulissApp was showing the right number of typicals.
—
Reply to this email directly or view it on GitHub
https://github.com/souliss/soulissapp/issues/33#issuecomment-136335205.

Are you sure that are we reffering to the same problem? This is coming with
the latest apk.

No, Im not sure... xD :P
I don't know why my problem (slots STALE) comes and it's solved... :S
About typicals and slots enumeration it works well for me on the lastest apk
Regards
2015-08-31 16:19 GMT+02:00 Dario Di Maio<EMAIL_ADDRESS>
Are you sure that are we reffering to the same problem? This is coming with
the latest apk.
—
Reply to this email directly or view it on GitHub
https://github.com/souliss/soulissapp/issues/33#issuecomment-136384018.

@plinioseniore have you used DB backup/restore functions?

Yes, DB exported with a previous version and then restored with the latest
one. The problem araise only while importing a DB from a CSV backup,
otherwise the proper information is displayed.

OK, found the bug then. Working to solve it


[core] GESTURE_DOUBLETAP, TAP_TIMEOUT and rgGetCurrentTime() issue.

[x] I tested it on latest raylib version from master branch
[x] I checked there is no similar issue already reported
[x] I checked the documentation on the wiki
[x] My code has no errors or misuse of raylib

Issue description
Unfortunately GESTURE_DOUBLETAP appears to have a timing issue on all platforms.
It appears that the problem is the TAP_TIMEOUT value (rgestures.h#L184). rgesture.h comments mention time being in milliseconds, but, in fact, it's all being handled in seconds from GetTime() (rgestures.h#L531) while using rgestures.h with raylib. So the inconsistency of GESTURE_DOUBLETAP was that it had an "open window" of 300 seconds instead of 300 milliseconds.
Proposed solution
The most straightforward solution (since rgGetCurrentTime() (rgestures.h#L526) is already returning the time in seconds) is to convert TAP_TIMEOUT to seconds (and also PINCH_TIMEOUT since we're already there, although it's not being used at the moment) and fix the rgesture.h comments to replace milliseconds with seconds.
For consistency, it's also necessary to adjust the rgGetCurrentTime() standalone implementations (rgestures.h#L530-L566) so they also return time in seconds.
Will send a PR with the proposed changes shortly.
Environment
Platform: Linux
Operating System: Linux Mint 21.1 (x86_64)
OpenGL version: 3.1 Mesa 22.0.5
GPU: Intel HD Graphics 3000
Platform: Android
Operating System: Android 5.1.1
OpenGL version: OpenGL ES 1.1/2.0
GPU: Mali-400
Issue Screenshot

Code Example
Minimal reproduction code to test the issue:
#include "raylib.h"

#if defined(PLATFORM_WEB)
    #include <emscripten/emscripten.h>
#endif

#define GESTURE_LOG_SIZE 20
char gestureLog[GESTURE_LOG_SIZE][12] = { "" };
int gestureLogIndex = GESTURE_LOG_SIZE;
int previousGesture = 0;
char const *GetGestureName(int i) {
   switch (i) {
      case 0:   return "None";        break;
      case 1:   return "Tap";         break;
      case 2:   return "Double Tap";  break;
      case 4:   return "Hold";        break;
      case 8:   return "Drag";        break;
      case 16:  return "Swipe Right"; break;
      case 32:  return "Swipe Left";  break;
      case 64:  return "Swipe Up";    break;
      case 128: return "Swipe Down";  break;
      case 256: return "Pinch In";    break;
      case 512: return "Pinch Out";   break;
      default:  return "Unknown";     break;
   }
}
int logMode = 1;
Rectangle logButton1 = {53, 7, 48, 26};
Rectangle logButton2 = {108, 7, 36, 26};
Vector2 gestureLogPosition = {10, 10};

void Update(void) {
    // Handling:
    int i, ii;
    const int currentGesture = GetGestureDetected();
    if (IsMouseButtonReleased(MOUSE_BUTTON_LEFT)) {
        if (CheckCollisionPointRec(GetMousePosition(), logButton1)) {
            switch (logMode) {
              case 3:  logMode=2; break;
              case 2:  logMode=3; break;
              case 1:  logMode=0; break;
              default: logMode=1; break;
            }
        } else if (CheckCollisionPointRec(GetMousePosition(), logButton2)) {
            switch (logMode) {
              case 3:  logMode=1; break;
              case 2:  logMode=0; break;
              case 1:  logMode=3; break;
              default: logMode=2; break;
            }
        }
    }
    int fillLog = 0;
    if (currentGesture !=0) {
        if (logMode == 3) {        // 3 hides repeated events and hide hold events
            if ((currentGesture != 4 && currentGesture != previousGesture) || currentGesture < 3) { fillLog = 1; }
        } else if (logMode == 2) { // 2 shows repeated events but hide hold events
            if (currentGesture != 4) { fillLog = 1; }
        } else if (logMode == 1) { // 1 hides repeated events
            if (currentGesture != previousGesture) { fillLog = 1; }
        } else {                   // 0 shows repeated events
            fillLog = 1;
        }
    }
    if (fillLog) {
        previousGesture = currentGesture;
        if (gestureLogIndex <= 0) { gestureLogIndex = GESTURE_LOG_SIZE; }
        gestureLogIndex--;
        TextCopy(gestureLog[gestureLogIndex], GetGestureName(currentGesture));
    }

    // Drawing:
    BeginDrawing();
    ClearBackground(RAYWHITE);
    DrawText("Log", gestureLogPosition.x, gestureLogPosition.y, 20, BLACK);
    for (i = 0, ii = gestureLogIndex; i < GESTURE_LOG_SIZE; i++, ii = (ii + 1) % GESTURE_LOG_SIZE) {
        DrawText(gestureLog[ii], gestureLogPosition.x, gestureLogPosition.y + 410 - i*20, 20, (i == 0 ? MAROON : LIGHTGRAY));
    }
    Color logButton1Color, logButton2Color;
    switch (logMode) {
      case 3:  logButton1Color=MAROON; logButton2Color=MAROON; break;
      case 2:  logButton1Color=GRAY;   logButton2Color=MAROON; break;
      case 1:  logButton1Color=MAROON; logButton2Color=GRAY;   break;
      default: logButton1Color=GRAY;   logButton2Color=GRAY;   break;
    }
    DrawRectangleRec(logButton1, logButton1Color);
    DrawText("Hide", logButton1.x + 7, logButton1.y + 3, 10, WHITE);
    DrawText("Repeat", logButton1.x + 7, logButton1.y + 13, 10, WHITE);
    DrawRectangleRec(logButton2, logButton2Color);
    DrawText("Hide", logButton1.x + 62, logButton1.y + 3, 10, WHITE);
    DrawText("Hold", logButton1.x + 62, logButton1.y + 13, 10, WHITE);
    EndDrawing();
}

int main(void) {
    InitWindow(400, 450, "Doubletap test");
    #if defined(PLATFORM_WEB)
        emscripten_set_main_loop(Update, 0, 1);
    #else
        SetTargetFPS(60);
        while (!WindowShouldClose()) Update();
    #endif
    CloseWindow();
    return 0;
}

@ubkp Thanks for the review! rgestures had not been reviewed in a long time and it required several improvements. Using seconds for time measures is the most standard and logic option, actually, it was already adopted for raylib long time ago.


Table can't work in Django project

I can‘t use the markdown syntax to insert a table, I input this:
| Tables        | Are           | Cool  |
| ------------- |:-------------:| -----:|
| col 3 is      | right-aligned | $1600 |
| col 2 is      | centered      |   $12 |
| zebra stripes | are neat      |    $1 |

then I get this:

It should be like this:

Tables
Are
Cool

col 3 is
right-aligned
$1600

col 2 is
centered
$12

zebra stripes
are neat
$1

How can I get the normal table?

Can you be more specific? Do you get the right HTML output?

Yeah, I got the right HTML output, but in my page can't show the table, just like above, the table have no border, here is my Django model code:
class Article(models.Model):
    title = models.CharField('Title', max_length=300)
    content = models.TextField()
    content_html = models.TextField(null=True)
    last_edit = models.DateTimeField('Last Edit', auto_now=True)
    timestamp = models.DateTimeField('Create Time', default=datetime.datetime.now)
    tags = models.ManyToManyField(Tag, blank=True)
    excerpt_img_url = models.URLField(max_length=500, null=True)
    excerpt_content = models.TextField(blank=True)

    @staticmethod
    def content_changed(sender, instance, **kwargs):
        renderer = HighlighterRenderer()
        markdown = misaka.Markdown(renderer, extensions=('tables',
            'fenced-code', 'footnotes', 'autolink',
            'strikethrough', 'underline', 'highlight',
            'quote', 'superscript', 'math'))
        instance.content_html = markdown(instance.content)
        soup = BeautifulSoup(instance.content_html, 'html.parser')
        if soup.find('img') is not None:
            instance.excerpt_img_url = soup.find('img')['src']
        instance.excerpt_content = bleach.clean(instance.content_html,
            tags=['a', 'b'], strip=True)

    def __str__(self):
        return self.title

pre_save.connect(Article.content_changed, sender=Article)

Ok, looks correct. Did you also check the CSS?

I have no CSS style about the table.

Try to add it. Maybe it works.

That's not Misaka's job. I would have to inline CSS, which is wrong and causes conflicts with the CSS of the user/developer.


Add files via upload

File to support compiled-with-nim.yml mentioned in https://github.com/fireeye/capa-rules/issues/268

Thanks, capa detects this as expected.
compiled with Nim
namespace  compiler/nim
scope      file


enableCodeCopy does not work when codeFences is set to false

enableCodeCopy does not work when codeFences is set to false

params.toml

enableCodeCopy = true

markup.toml

[highlight]
  codeFences = false

I can replicate this, but disabling code fences necessarily means all code block functionality would be removed, so this seems like expected behavior.

Thanks for raising this @eallion
Agree with @ragibson will close


Refactor graph

Originally wanted to include the PRUNEGRAPH into the creation step of the graph, but couldn't get that working(Needed something like the AST of a DeviceBuffer).
Removes a few lines, has a few readability improvements and adds the GRAPHPATH option to set the output location and name of the graph (I like to use ./net)
Produces the same graph for the test_efficientnet.py(except adding a prunable key to the nodes).

Can you add tests for the graph to know it's good to merge? :)

I will add some.

Added the tests and made some changes to make it testable.


Different id name in model?

Hi there, I'm having trouble creating a model with a different name for the id primary key field.
Is this just how the ORM works? And I can't do something like:
this.id = undefined;
this.other_id = [this.Id];

Cheers.

Ah yes I'm afraid id is hardcoded as primary key at several locations in the code at the moment. There are some comments/todos to replace it with a .getPrimaryKey() method instead.
To prevent the id from being created automatically, I think you can do something like:
function User() {
    // Setting the id property as empty array will prevent the property from being created.
    this.id = [];
    this.otherId = [this.UUID, this.CanUpdate(false)];
}

But a lot of things will stop working, like associations, the API, and probably some more parts. What do you want to achieve? You don't like id as primary key?

That's fine, I kinda like the abstraction, but having the flexibility is nice though. I was writing an import script and needed some hacks with renaming all primary key fields as "id" from the data source I was using.. namely the itunes data feed https://www.apple.com/itunes/affiliates/resources/documentation/itunes-enterprise-partner-feed.html

This issue is not relevant anymore. Please have a look at the new version.


ruruku should be able to serve files

UseCase
I play around with ruruku to monitor tests of zupfnoter (https://github.com/bwl21/zupfnoter/issues/245).
As a developer I create testcases before I make changes in Zupfnoter. As a "release manager"  I am using a scripting environment (rspec) to generate diff of all testcase-pdfs and messages produced by the app. But I need a quick way to investigate these diffs and collect findings. This is where ruruku comes in.
Solution approach

let the testsuite (rspec) generate a ruruku testplan. In the steps section of a particular test refer to or even embed the aforehead mentioned diff files.
go through all tests in ruruku and  do the investigation. Thereby show the test results. It could look like this:

I have created this screenshot by a testcase like tis
- description: "./test-source/083_Der_Mirjambrunnen_Bernhard.abc"
  group: ''
  id: "./test-source/083"
  minTesterCount: 0
  mustPass: false
  name: mal schaun ./test-source/083_Der_Mirjambrunnen_Bernhard.abc
  steps: "\n\n## investigate ./test-source/083_Der_Mirjambrunnen_Bernhard.abc\n\n<img
    src=\"http://localhost:3000/test-output/083_Der_Mirjambrunnen_Bernhard_-test_a3.png\"
    alt=\"drawing\" width=\"100%\"/>\n<img src=\"http://localhost:3000/test-diff/083_Der_Mirjambrunnen_Bernhard.diff.png\"
    alt=\"drawing\" width=\"100%\"/>\n\n  "
- description: "./test-source/1003_Jumplines.abc"

As you see I had to setup another webserver to serve the outputfiles of my testsuite. It would be great if ruruku could serve these files with an url resolved relative to the position of the testplan.yaml. It would even be better if testplan.yaml could specify the root of the server files.

It makes total sense to serve files together with the testplan, e.g. the artifact under test itself (e.g. some form of executable or firmware file). Or, such as in your case, additional images and data required to execute the test.
To that end, it would be great if one could submit the those files (let's call them context) together with the testplan. This is very similar to the way Docker works: for building a Docker image one uploads the build context (a tar file) which contains the build instructions (Dockerfile) and some additional files. In case of ruruku, one would upload a tar file as well - created and executed through the CLI - in addition to the testplan itself. Then ruruku could serve the files that were part of the testplan context.


Skip Semantic Test

The Semantic Test is enabled only for certain subscriptions and could not be executed now in CI (which causes the test failures). So, skipping it for now.
@xirzec Please review and approve.

/check-enforcer override


Allowing a data format for the cell to help handle dates, percentages…

…, etc.

What is this C# nonsense... 😉

Can you publish your NPOI code so I can see how you are consuming this? Also, can you think of a way to get test coverage for this? Maybe calling the constructor in a test a verify the property is what you expect.

Tests look good. Can you rebase on master because I added CI that runs the tests. Also, I wouldn't mind seeing your ExcelAbstraction.NPOI branch on how you're using this.

https://github.com/pjmeadmtu/ExcelAbstraction.NPOI/blob/cell-data-format/ExcelAbstraction.NPOI/ExcelService.cs - Lines 348 - 355

You know that Excel is :1st_place_medal: around here.

I'm on a mac at work, so I'll have to wait to upload to NuGet.

Thanks for jumping on that.
On Mon, Apr 24, 2017 at 1:26 PM, Kelly Selden<EMAIL_ADDRESS>wrote:

I'm on a mac at work, so I'll have to wait to upload to NuGet.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kellyselden/ExcelAbstraction/pull/1#issuecomment-296758096,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKQ0RuxdGUqTOETXfjp796ajY8c96SPhks5rzNtYgaJpZM4NDBnK
.


No license

Hi, could you please add a license file? So that it's clear if and how the library can be used in other projects.
Thanks!

License add in https://github.com/neilff/redux-ui-router/pull/79


Question on computing niche cell type composition

Dear developers,
I have a question regarding computing niche cell type composition from following tutorial.
https://scenvi.readthedocs.io/en/latest/tutorial/MOp_MERFISH_tutorial.html
I have two spatial dataset where one has corresponding scRNAseq but another one does not.
Can I run envi for both dataset to get similar plot like in step 153? If yes then what modification need to done.
Also why FDL_COVET and DC_COVET need to transfer from both spatial dataset to scRNAseq at step 21-24.
Can I compute cell type composition without COVET part?
Thanks and apologies for asking layman questions.

Hi!
Thank you for your interest in our work! The plot in step 153 shows the neighborhood prediction for the single-cell data, so you would only need to apply in on your scRNA-seq dataset which can be integrated via ENVI using the corresponding spatial data. For the other spatial data, you can compute the niche composition directly from its spatial coordinates (see the function 'niche_cell_type' in our utils.py file for an example of how we did it).
FDL_COVET and DC_COVET are calculated from both COVET representations of the scRNA-seq and spatial data. The spatial data COVET is calculated from its coordinates, while scRNA-seq COVET is predicted by ENVI. Employing DC and FDL serves as an easy way to visualize and capture trends in the COVET representations (such as cortical depth).
For the spatial data, you can compute cell type composition without COVET (again, see utils.py for how we did it), but the scRNA-seq relies on the COVET prediction to infer its cell type composition.
Hope this answered all your questions!


etcdserver: wait apply on conf change Raft entry

When apply-layer sees configuration change entry in
raft.Ready.CommittedEntries, the server should not proceed
until that entry is applied. Otherwise, follower's raft
layer advances, possibly election-timeouts, and becomes
the leader in single-node cluster, before add-node conf
change of other nodes is applied.
Fix https://github.com/coreos/etcd/issues/7595.
@xiang90 @heyitsanthony
Could you check if this is the correct approach?
I think we can also remove the isCandidate check,
if we had that only for config changes?
Thanks.

Codecov Report

Merging #7706 into master will decrease coverage by 0.33%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #7706      +/-   ##
==========================================
- Coverage   75.52%   75.18%   -0.34%
==========================================
  Files         330      330
  Lines       25936    25941       +5
==========================================
- Hits        19588    19504      -84
- Misses       4942     5008      +66
- Partials     1406     1429      +23

Impacted Files
Coverage Δ

etcdserver/raft.go
88.11% <100%> (+0.21%)
:arrow_up:

pkg/transport/timeout_conn.go
60% <0%> (-20%)
:arrow_down:

pkg/fileutil/purge.go
73.68% <0%> (-7.9%)
:arrow_down:

auth/simple_token.go
86.84% <0%> (-7.9%)
:arrow_down:

etcdserver/api/v3rpc/lease.go
92.85% <0%> (-7.15%)
:arrow_down:

etcdserver/api/v3rpc/watch.go
89.63% <0%> (-5.7%)
:arrow_down:

etcdserver/api/v3rpc/util.go
50% <0%> (-5.56%)
:arrow_down:

mvcc/watchable_store.go
81% <0%> (-5.04%)
:arrow_down:

pkg/adt/interval_tree.go
86.28% <0%> (-4.88%)
:arrow_down:

proxy/grpcproxy/watcher.go
89.58% <0%> (-4.17%)
:arrow_down:

... and 11 more

Continue to review full report at Codecov.

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

looks OK. defer to @xiang90

good catch. see my inline comments.

Fixed. Wait before sending messages blocks in case of single-node cluster.

Wait before sending messages blocks in case of single-node cluster.

can you explain why? it is actually important to wait apply before sending. or we might end up with collecting wrong votes (we have pending conf, we wait after send. but our raft routine is async, so it might run faster and start to collect and count vote responses incorrectly)

@xiang90
This is how single-node cluster blocks
r.raftStorage.Append(rd.Entries)
if !islead {
    if waitApply { rh.waitForApply() }
    r.sendMessages(rd.Messages)
}
raftDone <- struct{}{}

waitForApply blocks forever because server.go applyAll https://github.com/coreos/etcd/blob/master/etcdserver/server.go#L784 needs to receive from raftDone channel. So follower cannot proceed to next states. Will get publish error: etcdserver: request timed out.
If we do
r.raftStorage.Append(rd.Entries)
raftDone <- struct{}{}
if !islead {
    if waitApply { rh.waitForApply() }
    r.sendMessages(rd.Messages)
}

Now applyAll would miss receiving from msgSnapC because we signal raftDone before we call sendMessages (which signals msgSnapC.
To sum,

applyAll depends on raftDone channel, to proceed to process the received from msgSnapC
msgSnapC depends on sendMessages to get the snapshot data
we want sendMessages to be in sync with waitForApply
waitForApply again depends on applyAll to proceed

So for wait apply before sending, current implementation has cyclic dependency.
Breaking applyAll and sendMessages into smaller parts seems like the only way?

@xiang90 @heyitsanthony Had to add processMessages function
to get away with msgSnapC blocking issue in sendMessages.
Any better way to decouple this?
PTAL.

Now applyAll would miss receiving from msgSnapC because we signal raftDone before we call sendMessages (which signals msgSnapC).

I do not quite follow this part. More explanation?

@gyuho is it easy to reproduce the original issue? i want to confirm this patch fixes the issue if possible.

@xiang90 Yeah we can do some dumb sleeps here

// apply takes entries received from Raft (after it has been committed) and
// applies them to the current state of the EtcdServer.
// The given entries should not be empty.
func (s *EtcdServer) apply(es []raftpb.Entry, confState *raftpb.ConfState) (appliedt uint64, appliedi uint64, shouldStop bool) {
	for i := range es {
		e := es[i]
		switch e.Type {
		case raftpb.EntryNormal:
			s.applyEntryNormal(&e)
		case raftpb.EntryConfChange:
			if s.Lead() != uint64(s.ID()) && rand.Intn(1000)%2 == 0 {
				fmt.Println("WAIT!!!!!")
				time.Sleep(3 * time.Second)
			} else {
				fmt.Println("DID NOT WAIT!!!")
			}

And just set up cluster and restart, and will see this same issue.
But with this patch, it will block until the config change is applied.

@gyuho
awesome. can you turn it into a unit test or an integration test somehow? thanks!

@xiang90 I don't see any easy way to test applyAll routine or integration.
The blocking behavior is already being tested in TestConfgChangeBlocksApply?

@xiang90 Fixed. PTAL.

LGTM. Thanks for figuring out the root cause @gyuho!


Delivery Optimization?

Will the Teams client updates leverage Delivery Optimization?

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

ID: 7936ca5e-c658-4956-b174-99eaf1eb67d4
Version Independent ID: 9ecc0b61-a941-f5e1-96c3-d32fae59eacd
Content: Deploy Microsoft Teams with Office 365 ProPlus
Content Source: DeployOffice/teams-install.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

@PiKappZ746  -- We're checking on this. Will let you know what we find out and will update the article as needed. Thanks for your question.

@PiKappZ746 -- We're fairly certain Team isn't able to make use of Delivery Optimization for updates, but we're double-checking with another source.

@PiKappZ746  -- Got confirmation from a 2nd source that Teams doesn't make use of Delivery Optimization. Thanks for your question.


Improve parcel_provisioner.sh performance

In order to sync os buffers to disk, we can call the sync command:
https://linux.die.net/man/8/sync
which is both faster and deterministic.

I've read conflicting reports on that, but a short sleep doesn't really hurt.

I'll test this out soon, adding the short sleep. Can you tack that on to this PR? That way I can just merge this from here. Thanks!

I've merged this in manually -- thank you for the PR!


Bump Dependency

Signed-off-by: Utkarsh Srivastava<EMAIL_ADDRESS>Explain the changes
This PR is the first PR in an attempt to migrate from Node v14 to Node v16. This PR bumps patch/minor/major dependencies.
==========================================================
############## MAJOR DEPENDENCY UPGRADES #################
==========================================================
@google-cloud/storage    5.20.5  →    6.4.2 DONE
@types/mongodb           3.6.20  →    4.0.6 SKIPPED
@types/node            16.11.59  →  18.7.18 SKIPPED
mocha                     9.2.2  →   10.0.0 DONE - FIXED
mongodb                   3.7.3  →    4.9.1 SKIPPED
node-addon-api            4.3.0  →    5.0.0 DONE
node-gyp                  8.4.1  →    9.1.0 DONE
sinon                    13.0.2  →   14.0.0 DONE
uuid                      8.3.2  →    9.0.0 DONE
yaml                     1.10.2  →    2.1.1 DONE
==========================================================

==========================================================
########### MINOR/PATCH DEPENDENCY UPGRADES ##############
==========================================================
@azure/storage-blob              12.9.0  →   12.11.0 DONE
@google-cloud/storage            5.18.1  →    5.20.5 DONE - FIXED
@types/lodash                  4.14.182  →  4.14.185 DONE
@types/node                    16.11.33  →  16.11.59 SKIPPED
aws-sdk                        2.1127.0  →  2.1216.0 DONE
eslint                           8.14.0  →    8.23.1 DONE
ip                                1.1.5  →     1.1.8 DONE
istanbul-reports                  3.1.4  →     3.1.5 DONE
moment-timezone                  0.5.34  →    0.5.37 DONE
mongo-query-to-postgres-jsonb    0.2.14  →    0.2.15 DONE
nan                              2.15.0  →    2.16.0 DONE
pg                                8.7.3  →     8.8.0 DONE
pkg                               5.6.0  →     5.8.0 DONE
prebuild-install                  7.1.0  →     7.1.1 DONE
prom-client                      14.0.1  →    14.1.0 DONE
ts-node                          10.7.0  →    10.9.1 DONE
typescript                        4.6.4  →     4.8.3 DONE
ws                                8.6.0  →     8.8.1 DONE
==========================================================

Breaking changes:

@google-cloud/storage minor bump had a breaking change for us. We modified the useragent function which is internal to the module. This broke because of their code restructuring.
mocha major bump had a breaking change. They changed their binary name from /bin/mocha to /bin/mocha.js

Tested the above by running:

make test
make test-postgres
make tester; docker run --privileged --rm --name test1 noobaa-tester ./src/test/unit_tests/run_npm_test_on_test_container.sh -s sudo_index.js

[ ] Doc added/updated
[ ] Tests added

@utkarsh-pro does the mocha change affect the line below? https://github.com/noobaa/noobaa-core/blob/a89b385450f4aa3096df3f05e84c566d46e047da/package.json#L21
We should probably also change in:
https://github.com/noobaa/noobaa-core/blob/a89b385450f4aa3096df3f05e84c566d46e047da/src/deploy/NVA_build/Tests.Dockerfile#L58

@utkarsh-pro does the mocha change affect the line below?
https://github.com/noobaa/noobaa-core/blob/a89b385450f4aa3096df3f05e84c566d46e047da/package.json#L21

Nope, this symbolic link still points to the correct module.

We should probably also change in:
https://github.com/noobaa/noobaa-core/blob/a89b385450f4aa3096df3f05e84c566d46e047da/src/deploy/NVA_build/Tests.Dockerfile#L58

Yes, missed this. Thank you.


dotnet pack datetime versioning not guaranteeing that a newer package will have a higher version

A package generated on 8/8 had the version 1.0.0-CI-201788-, but then a build produced on 8/11 had the version 1.0.0-CI-2017811-.  The 8/11 package is seen as older than the 8/8 package.  The date time versioning should probably use 2 digit numbers for the month and day so the versions become 1.0.0-CI-20170808-* and 1.0.0-CI-20170811-*.

This issue will be solved by this PR.
The fix will go out in the next deployment.


How to disable chunk?

Hello. I have some questions about chunk.
When I build project, I get 2 or 3 js files like index.js & 1.index.js in dist.
I wanna disable chunk (like output js file will be only index.js)
Can you tell me how to do?
I also wanna disable wasm file's hash.
If anyone know about it, please tell me.
Thank you.

wasm-bindgen doesn't do any chunking or hashing of the final build, so I'm assuming you're using webpack?
If so I'd recommend:

If you don't need to use webpack, I'd personally recommend just using wasm-bindgen's --target web and not using a JavaScript bundler at all.

If you do need webpack, check out their documentation on chunks

Indeed I don't have anything to add over what @chinedufn already mentioned, so I'm gonna close this.


Temp Fix for Deprecation and Removes Scary Warnings

FYI I've forked this project as easy-json-table and plan on keeping it well maintained. You may wish to look at the contribution protocol and send a PR here: https://github.com/gazhayes/easy-json-table


Seed data1.7  READY

OK this PR is a bit big, but there were several changes that had to happen together.    Note: This PR contains the commits from #460 as well
In addition to the combined-query changes, there are a few more things to adjust in browser to make work for the app and end-to-end tests.

email addresses.  all email addresses in seed-data1.7 and the test data are example.com, include joe@ and mary@

Values for dateTimes are now marked with "Z" in the database so they are interpreted properly as GMT.  actual timezone support for browser is not in this PR, just data

revert "accepted" to boolean and get resolved searches all working again.

voting refactor.  /hasVoted goes away.  Change to voting as desribed is all set.

I got the browser working no problem with these changes-- I had to remove the call to /v1/hasVoted.  Voting works, but of course the new hasVoted behavior (examining upvotingContributorIds, etc) is not implemented.
When I re-enabled "show resolved only" it worked.  Unit tests all pass with and without the seed data loaded.  I know it would be preferable to have fewer commits in the PR, but the seed data synchronizes with all of these middle tier changes, so only with all of this can I expect the browser tests to pass again.
date facets still work as before.  timezone support next.

Error when re-enabling resolved only:
{
  "data":{
    "status":400,
    "message":"com.marklogic.client.FailedRequestException: Local message: search failed: Bad Request. Server Message: REST-INVALIDPARAM: (err:FOER0000) Invalid parameter: Invalid combined search\nREST-INVALIDPARAM: (err:FOER0000) Invalid parameter: Invalid query: XDMP-VALIDATEUNEXPECTED: (err:XQDY0027) validate strict { $q } -- Invalid node: Found search:boolean but expected ((search:text),search:weight?) at /search:search/search:query/search:and-query/search:value-constraint-query/search:boolean using schema \"search.xsd\""
  },
  "status":400,
  "config":{
    "method":"POST",
    "transformRequest":[
      null
    ],
    "transformResponse":[
      null
    ],
    "url":"/v1/search",
    "data":{
      "search":{
        "qtext":[
          "",
          "sort:active"
        ],
        "start":1,
        "query":{
          "and-query":{
            "queries":[
              {
                "value-constraint-query":{
                  "constraint-name":"resolved",
                  "boolean":true
                }
              }
            ]
          }
        },
        "timezone":"America/Los_Angeles"
      }
    },
    "timeout":30000,
    "headers":{
      "Accept":"application/json, text/plain, /*",
      "Content-Type":"application/json;charset=utf-8"
    }
  },
  "statusText":"Bad Request"
}

As far as I know, this worked before. Is there a change to the schema for boolean criteria?

I'm getting all excited about feature-complete :)
Yes, this is expected @laurelnaiad .  Erik discovered a schema bug -- and this is why we did the little dance around boolean for EA-3.
This got it working for me locally.  in mlSearch.js
    if (constraint.type === 'boolean') {
-              q.boolean = constraint.value;
+              q.type = 'boolean';
+              q.text = constraint.value;
             }

  "value-constraint-query":{
                  "constraint-name":"resolved",
                  "type":"boolean",
                   "text":true
                }

and using resovled:true resolved:false now will work in search box too.  (Of course now I'm going to go check to make sure)

OK the good news is that the seed data is correct and the browser works when you make the adjustment above.  the bad news is there's a bug in Java, where it's still putting "true" in at accept time -- it's still doing 1.6 things.  I'll prepare this patch and add to PR.

In other words, all scenarios except
"joe accepts answer then searches for it with resovled:true or the checkbox" will pass already, and my additional commit will fix this last scenario.

It may be a bug in Java or REST for JDON document patch. :(  I'm investigating reproduction/workarounds.

  "value-constraint-query":{
                  "constraint-name":"resolved",
                  "type":"boolean",
                   "text":true
                }

This would make a nice additional test fixture, to demonstrate how it's supposed to work for dolts like me! :)

I have added a patch that resolves the issue with accept.  Very weird and counter-intuitive what I had to do; I'll raise at least a docs bug about it.

Take s look here for some valid queries
/appserver/java-spring/src/test/resources/queries

Merged as of https://github.com/laurelnaiad/marklogic-samplestack/commit/bfa32254220732d3526521707f39976ca2f56f74


VAE reconstruction failed

System Info / 系統信息
CogVideo-2B
Information / 问题信息

[X] The official example scripts / 官方的示例脚本
[ ] My own modified scripts / 我自己修改的脚本和任务

Reproduction / 复现过程
I test inference/cli_vae_demo.py with 16-frame videos and 17-frame videos.
The 17-frame videos can be successfully reconstructed. But 16-frame videos failed in the previous frames.
The MSE loss for 17-frame videos is nearly 0.001 but for 16-frame videos is 0.01.
Expected behavior / 期待表现
Can you explain why this would happen?

Is there any update? @zRzRzRzRzRzRzR

It seems to be related to the frame count constraint of the Causal 3D VAE, which requires the number of frames to follow the formula 4N + 1. If you provide the VAE with 16 frames, the video will either be padded to 17 frames or truncated to 13, causing a discrepancy.


[web on macos] Nested navigator with transition, causes unintended drop shadow

Steps to Reproduce
minimal repo : https://github.com/Azzeccagarbugli/getx_navigation
results:
on windows (good):

on macos (bad):

Logs
flutter doctor -v
[✓] Flutter (Channel stable, 2.2.3, on macOS 11.4 20F71 darwin-x64, locale en-GB)
    • Flutter version 2.2.3 at /Users/azzeccagarbugli/fvm/versions/stable
    • Framework revision f4abaa0735 (11 days ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/azzeccagarbugli/Library/Android/sdk/
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] VS Code (version 1.57.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.24.0

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 91.0.4472.114
    ! Error: iPhone is not connected. Xcode will continue when iPhone is connected. (code -13)

• No issues found!

Thanks for filing the issue, I was able to reproduce the issue with the sample code provided but the code sample uses a lot of third party plugins, Is it possible to narrow down the project to use the minimal code without any third-party plugins to be sure that this issue is specific to flutter.

It's just a nested navigators, can you try it on any flutter example with nested navigators and transition animations ?

Here's the sample code I tried, but can't see any shadows, feel free to modify the sample code and get back with the reproducible code.

code sample
import 'package:flutter/material.dart';

void main() {
  runApp(App());
}

class App extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      initialRoute: "/",
      routes: {
        '/': (context) => SomeOneView(),
        '/two': (context) => SomeTwoView(),
      },
    );
  }
}

class SomeOneView extends StatefulWidget {
  @override
  _SomeOneViewState createState() => _SomeOneViewState();
}

class _SomeOneViewState extends State<SomeOneView> {
  @override
  Widget build(BuildContext context) {
    return Row(
      children: [
        Container(
          width: 100,
          color: Colors.white,
        ),
        Expanded(
          child: Container(
            width: double.infinity,
            color: Colors.indigo,
            height: double.infinity,
            margin: EdgeInsets.symmetric(horizontal: 30),
            child: Column(
              mainAxisAlignment: MainAxisAlignment.center,
              children: <Widget>[
                MaterialButton(
                  color: Colors.white,
                  child: Text('Next'),
                  onPressed: () => Navigator.of(context).pushNamed('/two'),
                ),
              ],
            ),
          ),
        ),
      ],
    );
  }
}

class SomeTwoView extends StatefulWidget {
  @override
  _SomeTwoViewState createState() => _SomeTwoViewState();
}

class _SomeTwoViewState extends State<SomeTwoView> {
  @override
  Widget build(BuildContext context) {
    return WillPopScope(
      onWillPop: () async {
        return false;
      },
      child: Navigator(
        initialRoute: "two/home",
        onGenerateRoute: (RouteSettings settings) {
          WidgetBuilder builder;
          switch (settings.name) {
            case "two/home":
              builder = (BuildContext context) => HomeOfTwo();
              break;
            case "two/nextpage":
              builder = (BuildContext context) => PageTwoOfTwo();
              break;
          }
          return MaterialPageRoute(
              builder: (x) => SomeOneView(), settings: settings);
        },
      ),
    );
  }
}

class HomeOfTwo extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Container(
      width: double.infinity,
      height: double.infinity,
      color: Colors.grey,
      child: Column(
        mainAxisAlignment: MainAxisAlignment.center,
        children: <Widget>[
          ElevatedButton(
            child: Text('Next'),
            onPressed: () => Navigator.of(context).pushNamed('two/home'),
          ),
        ],
      ),
    );
  }
}

class PageTwoOfTwo extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Container(
      width: double.infinity,
      height: double.infinity,
      color: Colors.teal,
      child: Column(
        mainAxisAlignment: MainAxisAlignment.center,
        children: <Widget>[
          MaterialButton(
            child: Text('Next'),
            onPressed: () => Navigator.of(context).pushNamed('/three'),
          ),
        ],
      ),
    );
  }
}

Thank you.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Climate history chart showing operating mode not operating state

<!-- READ THIS FIRST:

If you need additional help with this template please refer to https://www.home-assistant.io/help/reporting_issues/
Make sure you are running the latest version of Home Assistant before reporting an issue: https://github.com/home-assistant/home-assistant/releases
Do not report issues for components if you are using custom components: files in /custom_components
This is for bugs only. Feature and enhancement requests should go in our community forum: https://community.home-assistant.io/c/feature-requests
Provide as many details as possible. Paste logs, configuration sample and code into the backticks. Do not delete any text from this template!
-->

Home Assistant release with the issue:

0.76.2, probably later but I have not updated my main system.
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Hassbian
Component/platform:

climate.ecobee
maybe other thermostat devices per https://community.home-assistant.io/t/explanation-of-climate-history-chart/73926
Description of problem:
Currently the history chart is highlighting the time when the thermostat's operating mode is set to on (heat) and not when the system is running.
Highlighting that the system is on does not provide much useful information (as the system is enabled all day) compared to highlighting when the system is running.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
ecobee:
  api_key: !secret ecobee_API

Traceback (if applicable):

Additional information:

I have the same effect with a nest thermostat/climate control, however a climate control based on a generic thermostat shows the expected display (i.e. the periods when the heating device is actually working rather than "ready to work".)

I get the same thing with the Radio Thermostat/Climate control. What I did was create a sensor that shows the current status:

The icon has five possible states: Heat Pump Idle/Fan On=mdi:fan, Heat Pump Idle/Fan Off=mdi:fan-off, Heating=mdi:fire, Cooling=mdi:snowflake, Unknown=mdi:network-off.
Here’s the script if anyone finds it helpful. Obviously replace thermostat77083b with the name of your device.
 Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? Thanks!

As of 0.89.1 I still see this. I will be updating to 0.90.0 this evening
and will report then.

I can confirm that the issue is still in 0.90.
On Thu, Mar 21, 2019 at 5:32 PM Jon Pannell<EMAIL_ADDRESS>wrote:

As of 0.89.1 I still see this. I will be updating to 0.90.0 this evening
and will report then.

I just updated to 0.91.1 and still see the issue with the chart:
[image: image.png]

I just updated to 0.91.1 and still see the issue with the chart:

@nhorvath Can you chime in?

@robbiet480 this is NOT fixed. I had to revert my fix because changing it broke the operation mode see https://github.com/home-assistant/home-assistant/pull/20767#issuecomment-461819327
Fixing this will probably require moving a lot of variables around in a non backwards compatible way.

@robbiet480, Since this is not fixed can you please reopen the issue?

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum. Thanks!

@MartinHjelmare Is this not a bug? My heater is not heating all the time. It is in "heat" mode and showing as providing heat.

@MartinHjelmare I would agree this is a legitimate bug. The graph does not work the same way other thermostat providers work. It was just done inconsistently from the start so fixing it will be complicated.

Reopening as it does appear to be a legit bug

We don't have a state attribute for operating state, just operating mode, ie the setting heat, cool, auto etc. Unless this integration doesn't properly plot operating mode, I don't see why it it a bug.

The current web api uses the on/off attribute to highlight the time interval on the plot (which is wrong bug can't be fixed until the climate redesign) so if the derived climate class doesn't report that attribute, the plot shows always on.  So I would claim that the bug is that the on/off state is not being reported.  I believe this is the same as the bug of this type I fixed in radiothermostat which resolved the same issue and adding the on/off state to the derived class should fix it.

Ecobee climate platform doesn't implement is_on yet. It's optional, so this is a feature request and not a bug. PR is welcome. Closing.

Isn't aux_heat attribute providing information about heating enabled or not?

No aux_heat is a 3rd stage heating. For example electric strip backup
heaters in a geothermal system.
On Wed, Jul 17, 2019 at 4:00 PM Andrey Kozhyn<EMAIL_ADDRESS>wrote:

Isn't aux_heat attribute providing information about heating enabled or
not?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/18244?email_source=notifications&email_token=AABIJXFJEVMFQLBB32INYRLP7524PA5CNFSM4GB6HKQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2GNJ3A#issuecomment-512546028,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABIJXEVL3HAR3PS3NJEJULP7524PANCNFSM4GB6HKQA
.


wip! Resolve ignore options in standard-engine, not deglob

standard-engine has all the information it needs to resolve these
options. deglob shouldn't have to repeat the work of finding the
package.json.
This will make it easier to control the ignore globs in a custom
options parser, for which see
https://github.com/Flet/standard-engine/pull/135.
Requires https://github.com/Flet/deglob/pull/6 to be released and the
minimum version to be bumped.

LGTM


[2857] Use UUID to associate trainee with course

Context
https://trello.com/c/fHuUvyEK/2857-l-use-uuid-to-associate-trainee-with-course
Changes proposed in this pull request

Add course_uuid to trainees table
Use course uuid instead of course code where appropropriate

Guidance to review

Visit a trainee that can select a published course
Everything should work as normal

 [L] Use UUID to associate trainee with course


Initialization bugs out on dynamically loaded image

I load a page's content with jQuery's load function:
     $('#content').load(hash + ' #content >*');
And I get this:

So far so good, but when I try to initialize the cropper on my image, this happens:

I found out that the images stacked on top of each other are the canvas, crop box, etc.
Ideally, when I don't use dynamic load, the cropper looks like this and works correctly:

Event listener for picture upload:
   $(document.body).on('change', '#cover-picture-input, function(){...});
After it's uploaded I change my img's src to the uploaded's src and initialize the cropper:

Thanks!

Hey @sjilo , did you find out how to solve this? I am having the same problem.


compose: Fix breakage of LaTeX delimiters in quote-and-reply

String.prototype.replace and String.prototype.replaceAll interpret certain sequences such as $$ within a string provided as the replacement argument. Because of this, LaTeX delimiters $$ were turning into $, and other sequences could duplicate part of the existing draft.
Avoid this interpretation by providing a function.
Fixes: #5849

Thanks! Looks good; merging.


fix compilation without deprecated OpenSSL APIs

Signed-off-by: Rosen Penev<EMAIL_ADDRESS>

Many thanks for the pull request, but I already accepted another patch to fix deprecated APIs.
https://github.com/baresip/re/commit/7e3e5f24d3f087774689b90b2cbf3227a43e6b90


fix web.config.js to run client/index.js

adding node-modules to .gitignore

conflicts in node-modules need to be resolved locally


proxy_ssl_ciphers directive doesn't work

Summary
Specifying proxy_ssl_ciphers doesn't seem to have any impact on the CIPHERS offered during TLS Handshake. Tried specifying using custom nginx template as well as nginx_http_ directives. One caveat is that, if we change existing proxy_pass definition inside custom template from
proxy_pass   $upstream_scheme://kong_upstream$upstream_uri;
to
proxy_pass  https://ACTUAL_HOST.com
then proxy_ssl_ciphers starts working. This indicates that proxying via kong_upstream seems to ignore the directive.
Additional Details & Logs

Kong version: 1.1.2
Operating system: docker alpine and centos both

@thibaultcha : Looks like when we implmented https://github.com/Kong/kong/commit/c4b3b1a7be471ff97a60ecc56a8cb0d7749cf9b6, we started using our own SSL_CTX for balancer instead of default nginx one which supported proxy_ssl_ciphers directive. I see a TODO inside kong/init.lua that mentions
"-- TODO: copy proxy_ssl_* flags?"
Can you confirm if I am thinking in the right direction?

@mukgupta Yes, you are right. It's a known limitation on our end. We've planned to have a proper fix after 1.4.0

Thanks for confirming @guanlan . Is there a good workaround to this? I am currently using ngx.ctx.balancer_data.ssl_ctx:setCurvesList in a pre-function plugin to update the ciphers/curves

@guanlan in 1.2.1 I observe what I think is related: proxy_ssl_trusted_certificate is not respected (i.e. ssl handshake fails) while the same cert chain file works fine in nginx using proxy_ssl_trusted_certificate.  Am I conflating these things, or is it likely that this issue is the same for proxy_ssl_trusted_certificate?

Fixed in 1.4.0rc2 vis Service Mesh deprecation. Please give it a try!


ROX-24364: SummaryTest flake

Description
TODO
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
TODO(replace-me)
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/test ?

/test all

/test gke-version-compatibility-tests

/test gke-version-compatibility-tests


Update README.md with todo list

Hmmm maybe this should be trello board instead. Might close this and just do that. Actually probably will. But later.


link to rpc node docs from stacks api page

I think it would be helpful to link to documentation for the node's API endpoints (the /v2/ endpoints) from our API documentation. Users won't know (or care) that they are separate, since our API nodes will forward these /v2/ endpoints. This results in difficult discovery for those.
cc @obycode

Users won't know (or care) that they are separate

I think trying to present the RPC and API docs/endpoints as the same service has caused a lot of problems, and we should separate how they are presented. They are separate services with differing usage, rate limits, performance, etc.
Similar to how we present some of these other services as separate, there should be something like a Stacks core RPC:

I think trying to present the RPC and API docs/endpoints as the same service has caused a lot of problems, and we should separate how they are presented.

@zone117x i agree with separating these. what do you suggest as the best practice for maintaining this section if we aren't providing any v2 endpoints in the OpenAPI schema?
In the meantime I guess we could have a callout on the Stacks API overview that links out to the Stacks Docs (https://docs.stacks.co/reference/api) for anyone looking for these endpoints

great! ill merge these changes in with the short-term solution and add a new issue for adding the RPC section later

fixed: https://github.com/hirosystems/docs/pull/761


Fix the CUDA 10.2 build on linux64

Follow-up of #23.

Checklist

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

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


add-the-docs, fixes #18

@saylorsd feel free to check out this branch and run the commands in the README to take a look at what the final docs look like. I was planning on hosting them on readthedocs.org, but that site appears to be having some trouble ATM with their SSL certificates. I'm not totally sure what good alternatives might be.

:+1: Love it! Am I right in assuming that most of the future upkeep for this will lie in writing proper docstrings?

Yes. It uses sphinx to do documentation. There's two parts to the documentation, the API (which is largely done for now and documented via docstrings), and the actual "what are these pieces and how do I use them" bit, which is mostly under construction and will be written when things are a bit more stable (i.e. we've moved everything around).


Tool

tool for keystore

Codecov Report

Merging #7 into master will decrease coverage by 0.4%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master       #7      +/-   ##
==========================================
- Coverage   77.18%   76.78%   -0.41%
==========================================
  Files         204      205       +1
  Lines        4606     4617      +11
  Branches      220      219       -1
==========================================
- Hits         3555     3545      -10
- Misses       1051     1072      +21


“sewer” should be 𐑕𐑵𐑼, but is 𐑕𐑫𐑼

CUBE lists “sewer” with GOOSE+lettER*, but Readlex has it with CURE.

Cambridge has: sewer drain sʊəʳ, sjʊəʳ (US) ˈsuː.ɚ
And that's probably why ReadLex has that too. But it doesn't seem right indeed. All the other sources I checked seem to agree on  /(j)uː/ and I couldn't find any obvious evidence on the Youglish of it ever being anything else. So I also agree that 𐑕𐑵𐑼 would be more recognizable to everyone.
It's probably easily confusable with CURE in post-RP-like dialects, though. If you look at Lindsey's post about it, you'll see that /ʉw.ə/ is one of possible realizations of CURE (fate 2). Here CUBE generally follows whatever SSB does and even the word ‘cure’ itself is transcribed with /oː/ as in THOUGHT rather than with the distinct CURE phoneme /ɵː/ (cf. ‘secure’). But I think all the words that met the second fate are indeed transcribed only with the smoothed /ɵː/ in CUBE rather than with /ʉwə/ as in ‘sewer’.

Thanks for picking this up. Cambridge is anomalous. Oxford has /suːə(r)/ and it is more universally understandable. Note, 'sewerage' remains with the CURE vowel.


Fix broken list parsing in cli arguments --tags and --experiments

Currently, buildkite-agent start --tags "a=1,b=2" sets a single tag of a=1,b=2. This is a shortcoming of the upstream urfave.cli library (see https://github.com/urfave/cli/issues/62) which expects --tags "a=1" --tags "a=2".
This adds a normalization for --tags and --experiments that makes them behave as expected.

Oh, I assume it's fine with --tags "foo=bang,bar,bing"

(Where you specifically want foo to be a comma separated list..)

Nope! Won't work!

Wouldn't work in config either.

Just chatted with @lox in real life, we've never supported commas in tag values before, so it's fine to ship as-is!