Design: Implement IPv6 Extension Routing Header

The Routing Header spec is at https://tools.ietf.org/html/rfc8200#section-4.4
Two questions about this:

What routing types should we implement? IANA routing types are at https://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xhtml#ipv6-parameters-3.

Type 0 (aka Source Route) was defined in the original IPv6 RFC but has since been deprecated. Should we implement this route?
Type 1 (aka Nimrod) looks to be abandoned, so that is clear.
Type 2 is related to IPv6 Mobility https://tools.ietf.org/html/rfc6275#section-6.4. I think this type only makes sense to implement if we implement the rest of RFC 6275.
Type 3 (aka RPL Source Route) is defined in RFC 6554 and is the successor to Type 0.
There are two experiment types defined in RFC 4727 - Section 3.6. There is no definitive format specified for these, as they are meant to be used for experiments.

How to represent the information for each routing type?

The format of the routing type contains 4 common fields and an unspecified section for type-specific data of variable length.

Should Header#check_len only ensure that there is enough data for the first 4 fields?
How should we deal with the different methods on each type? For example, there should be a Header#home_address method for a Type 3 header, but not one for a Type 2 header.
How should the Repr look? I can imagine something like:

pub struct Repr {
    pub next_header: Protocol,
    pub header_len: u8,
    pub routing_type: u8,
    pub segments_left: u8,
    pub type_spec_data: TypeSpecData,
}

pub enum TypeSpecData {
    Type2 { home_address: Ipv6Address },
    Type3 { cmpr_i: u8, cmpr_e: u8, pad: u8 } // would need to add a vector of addresses too
}

I spoke to @dlrobertson and the goal is to allow parsing of the 4 common fields in the header and ignore the type specific data.

What routing types should we implement?

IMO the first round should just implement Type 3.

How to represent the information for each routing type?

What about an enum repr with struct-like variants (like the ICMPs)

:+1:

Should Header#check_len only ensure that there is enough data for the first 4 fields?

No, it should check to ensure there is enough data for the Hdr Ext Len https://tools.ietf.org/html/rfc6554#section-3

How should we deal with the different methods on each type? For example, there should be a Header#home_address method for a Type 3 header, but not one for a Type 2 header.

See the ICMP packet types. There may be methods that are only valid for specific types. Make sure to add a Panics section if the function will panic when used with the wrong type.

How should the Repr look?

I thing an enum repr with struct like variants is the way to go here.
The Type 3 header has a variable number of addresses that need to be included. To get around having to use alloc you might just leave this as a &'a [u8] in the Repr similar to the ICMP Repr for EchoRequests etc. I can't really think of another way around this without requiring alloc.

Closed by a0009a0b614b71faffb3f0bd3490357e731baaa9


Add Llama 3

Hi, are they swapped? https://github.com/stanford-crfm/helm/pull/2579/files#diff-3785e5409ddffeb26d2ddc63be4f39481345eaafd42d74d0d23a6aa569f42337R233-R234

@mtake Yes, it is swapped. Thanks for catching this!


[Change Request]: Component story improvements

What type of enhancement/feature is this?
Documentation Improvements
Description
Consider the following improvements:

Improve Code Editor background styling.
Add Story descriptions. (extend the CSF 3 spec)
Ensure Stories are dark mode friendly.

Use Case/Reasoning for enhancement/feature.
Usability enhancements for component Stories.
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I have searched for existing issues and to the best of my knowledge this is not a duplicate
[X] This is a single enhancement/feature

Ensure that the contribution guide is updated accordingly.


Runtime value of a parameter node

Hi,
what is the best way to get the runtime value of an connected Exposed Parameter to an input port.
In my example I have a similar graph like the conditional graph.

Here a simple delay node
    public class DelayNode : BaseNode
    {
        [Input("Control")] public ControlLink controlIn;
        [Output("Control")] public ControlLink controlOut;

        [Input, ShowAsDrawer]
        public float duration;

        protected override async void Process()
        {
            await Task.Delay(TimeSpan.FromSeconds(duration));
        }

The problem is, I don't get the runtime value by default when I simple start my graph processor. (I wrote an custom editor script where I get all exposed graph properties by a given graph linked in the inspector)
public class SomeCallerClass
{
        public void Play()
        {
            foreach (var p in properties)
                graph.SetParameterValue(p.name, p.value);

            processor.Run();
        }
}

Processor code pieces:
public class CustomProcessor : BaseGraphProcessor
{
       // ...

        public override void Run()
        {
            InitializeNodes();
            startNode?.OnProcess();
        }

        private void InitializeNodes()
        {
            graph.nodes.ForEach(node => node.Initialize(graph));
        }
}

The delay node always get his default value, and not the parameter set before I call Run();
Only if I cache the ParameterNode at the first process by name and call it later like here
        protected bool GetInputParameterValue<T>(string name, out T output)
        {
            output = default(T);

            if (string.IsNullOrEmpty(name)) return false;

            if (!cachedInputNodes.TryGetValue(name, out var parameterNode))
            {
                parameterNode = inputPorts
                    .FirstOrDefault(x => x.fieldName == name)?
                    .GetEdges()?
                    .Select(x => x.outputNode as ParameterNode)
                    .FirstOrDefault();

                if(parameterNode?.output is T)
                    cachedInputNodes.Add(name, parameterNode);
            }

            if (!(parameterNode?.output is T value))
                return false;

            output = value;
            return true;
        }

Here the changed code that works, but I think its not really comfortable to use.
       protected override async void Process()
       {
           if (GetInputParameterValue<float>(nameof(duration), out var value))
               await Task.Delay(TimeSpan.FromSeconds(value));
       }

Maybe I missed something, but would be cool if I don't habe to find the ParameterNode value by my self.
Anyway, thank you for your great NodeGraphProcessor

Okay I can awnser myself :)
With the last version (Fixed parameter node returning a wrong value) I can extend my processor to push all parameter node datas.
public class CustomProcessor : BaseGraphProcessor
{
       // ...

        public override void Run()
        {
            #if UNITY_EDITOR
            InitializeParameterNodes();
            #endif
            startNode?.OnProcess();
        }

        private void InitializeParameterNodes()
        {
            foreach (var node in graph.nodes.OfType<ParameterNode>())
            {
                node.Initialize(graph);
                node.outputPorts.PushDatas();
            }
        }
}

That way I can delete my caching by name stuff and everything works great :)

Hello, sorry for the long delay.
I think the issue you have is 'expected' because if I follow correctly the logic of your graph, without your InitializeParameterNodes, the parameter nodes are never processed (because your nodes only process the one connected at the ControlLink). Can you confirm?
If that's the case, then the parameter value is not pushed out of the parameter node. A simple fix if you don't want to implement a dependency system on your nodes to process correctly all the nodes in the graph is to simply go over all the parameters like you did and call the OnProcess() instead of Initialize + PushData()


I had convert this into Swift

I had converted this project into swift how do  I upload it..?? So it will be easier for the new swift developers to use it..!! As I am new to github I don't know how to do this ?

Hi, you can add these 4 files to your swift project: https://github.com/Animaxx/A-ViewContainer/tree/master/A_ViewContainer/A_ViewContainer
and add these two line to your [projectName]_bridging.h file
#import "A_MultipleViewContainer.h"
#import "A_ViewBaseController.h"

then you can feel free to use this control :)

Oh, I am missing misunderstand you! You can go to your Repositories and create new project and update via Github desktop https://desktop.github.com/ :)

Thank you I will try


Shooting projectiles at the other tank to win the game.
How do you play your game?
Player 1 uses wasd to change direction. Player 2 uses ijkl to change direction. Upon changing direction, a projectile is launched. Both tanks move automatically every 500 ms. When a projectile hits a tank, the winning player's color is displayed on the screen, and the game can be restarted by pressing any key.
Code
Check off the items that are true.

[x] The game was made using the Sprig editor.
[x] The game is placed in the in the /games directory.
[x] The code is significantly different from all other games in the Sprig gallery (except for games labeled "demo").
[x] The game runs without errors.
[x] The name of the file/game contains only alphanumeric characters, -s, or _s.
[x] The game name is not the same as the others from gallery

Image (If an image is used)

[ ] The image is in the /games/img directory.
[ ] The name of the image matches the name of your file.

Thanks for your PR!

Cool game!  I do think there is at least one bug that could be fixed and perhaps you could debug that issue on your new Sprig device - if and only if, of course, you're a teen, and you haven't already received one - fill in this form).  Also feel free to say hi in Hack Club's Slack, perhaps in #sprig to share your app, or #lounge to just say hi.


update for employee names and income amount

add the employee name/display the employee name
update the values in incomeSources

One final comment just to note that we are talking about "employer" names.


Update readme.rst

based on the following issue, the import should be pandas_highcharts.core
https://github.com/gtnx/pandas-highcharts/issues/24

Coverage remained the same at 87.5% when pulling 34ebeb402e4f50a27d2f727bcb0bec81913106e6 on saeedesmaili:master into bf449b7db8b6966bcf95a0280bf2e4518f3e2419 on gtnx:master.


Step 3 Query Component step instructions causing errors

Instructions in step 3 are not working:
https://www.carbondesignsystem.com/tutorial/react/step-3#query-component
When following this section in step 3, the repo page is broken.
See this PR for an example: https://github.com/carbon-design-system/carbon-tutorial/pull/2894/files#submit-review

Here's the breaking change in apollo-react:
https://github.com/apollographql/react-apollo/blob/master/Changelog.md#potentially-breaking-change
So just needed to use data instead of data: {organization}, 'cause during loading or error state, the organization is unknown.
To carbon team:
Possibly just change the instructions for the Query function or change yarn add to a specific apollo-react version.

@IOIO72 do you mind opening a PR on the carbon website? Would be a super big help.
https://github.com/carbon-design-system/carbon-website

@IOIO72 do you mind opening a PR on the carbon website? Would be a super big help.
https://github.com/carbon-design-system/carbon-website

No problem. I'll do it during the day :)


Accept file input

Modifies the launcher and desktop files to accept file input using winepath.

Hey,
I'll add it to my google drive to avoid missing file or changing files without my permission once I checked if everything is OK.
if everything is OK I'll merge your file and change it back to my google drive so you'll be listed in the contributor section,
Also if you can tell me a bit more about this file input using winepath and how it can be useful it would be nice ^^
Thanks for your contribution anyway.

Ok I've tested it.
Thanks for your contribution, I'll add it to my google drive to avoid any file modification without my permission.
I'll merge it too so you'll have your account into the contributor list.


[SPARK-29973][SS] Use nano time to avoid 'NaN'/'Infinity'

What changes were proposed in this pull request?
Use nano time to calculate processedRowsPerSecond to avoid 'NaN'/'Infinity'
Why are the changes needed?
The processingTimeSec of batch may be less than 1 millis.  As processingTimeSec is calculated in millis, so processingTimeSec equals 0L. If there is no data in this batch, the processedRowsPerSecond equals 0/0.0d, i.e. Double.NaN. If there are some data in this batch, the processedRowsPerSecond equals N/0.0d, i.e. Double.Infinity.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Add new UT

Test build #114166 has started for PR 26610 at commit 7e02bc7.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/19020/
Test PASSed.

I don't think this is the right fix. Just handle the processingTimeSec = 0 case directly. The time here is used to generate a timestamp that escapes the JVM, so I'm also not sure if nanoTime is appropriate. It has slightly different guarantees.

Test build #114166 has finished for PR 26610 at commit 7e02bc7.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/114166/
Test FAILed.

There is a discussion in #26058. cc @vanzin Could you please take a review?

Test build #114190 has started for PR 26610 at commit 3a81b7c.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/19041/
Test PASSed.

I tend to agree with @srowen as handle the case explicitly given I'm not sure a micro-batch under 1ms is realistic in production cases, but if we still want to calculate it "accurately", define the new local variable for nanoTime to calculate duration instead of changing existing local variable which is also used for representing wall-clock.

Test build #114193 has started for PR 26610 at commit 0c76ea9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/19044/
Test PASSed.

Test build #114195 has started for PR 26610 at commit 245a197.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/19046/
Test PASSed.

Test build #114197 has started for PR 26610 at commit 50baee9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/19049/
Test PASSed.

Test build #114190 has finished for PR 26610 at commit 3a81b7c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/114190/
Test FAILed.

Test build #114197 has finished for PR 26610 at commit 50baee9.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/114197/
Test FAILed.

Test build #114193 has finished for PR 26610 at commit 0c76ea9.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #114195 has finished for PR 26610 at commit 245a197.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/114195/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/114193/
Test FAILed.

retest this please.

Test build #114219 has started for PR 26610 at commit 50baee9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/19069/
Test PASSed.

Test build #114219 has finished for PR 26610 at commit 50baee9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/114219/
Test PASSed.

@uncleGen can you give an example where a micro-batch is computed in less than 1ms?
Honestly I've seen clusters where at least 100ms is to schedule a micro-batch...

Agreed, it's unlikely to come up in practice (maybe local testing?) but seems OK to return something more correct than NaN in this case. It's low risk.

Yeah, I think it's low risk. Just want to understand it better how can I validate it, or even what's the impact...

@gaborgsomogyi Yeah, this is not very common in practice. But if it arises, it will impact rendering of streaming query statistics in #26201. Here is a test snippet:
spark.readStream.load(...).writeStream.start)

Test build #114289 has started for PR 26610 at commit 6a3271a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/19130/
Test PASSed.

Test build #114289 has finished for PR 26610 at commit 6a3271a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/114289/
Test PASSed.

Merged to master

Thanks for your code review. @srowen @HeartSaVioR @HyukjinKwon


Hello, can't he work normally now? Why can't I use it normally

I used it your way, but it didn't work

The command is UE4Dumper-IOS --newue --sdkw --gworld XXXXX --gname XXXX --package AClient,gname and uworld is true。

The command is UE4Dumper-IOS --newue --sdkw --gworld XXXXX --gname XXXX --package XXXX ,gname and uworld is true。


Add ability to "slab" 2D slices from 3D data

🚀 Feature

At the moment a 2D view of a 3D data set is limited to slices of thickness 1: I would like to be able to look at the (sum/average/max/min) of a slab of data e.g. in place of
image = data[n,:,:]

have
image = sum(data[j,:,:] for j in range(n,n+m))

The current viewer structure delegates much of the interaction to dask which does not give a window to allow this, e.g. using
import bitshuffle.h5
import dask.array as da
import numpy as np
import napari
import h5py
import sys

f = h5py.File(sys.argv[1])
d = f["/entry/data/data"]
s = d.shape

i = d[0]

a = da.from_array(d, chunks=(1, s[1], s[2]))

viewer = napari.view_image(a, title="DIALS Image Viewer",
                        contrast_limits=[0, 10])

napari.run()

Motivation

We in the DIALS team are looking to replace our image viewer with something a little more maintainable to fix numerous issues with performance etc. (e.g. https://github.com/dials/dials/issues/1776). A survey of the napari API suggested that this was the last missing feature. Discussion in community meeting yesterday indicated that this feature is indeed absent.
Pitch

Perfect world would have someone in napari work with us to get this done - am very happy that we contribute to the code base to get this done, but will need some guidance as there did not seem to be a simple way to do this.
Alternatives

This is likely to be a blocker for adopting napari for us, which would be a shame as it is otherwise perfect.
Additional context

We raised this in the community meeting yesterday and core developers there seemed pretty keen on this as a use case. Example from our existing viewer:

Appreciate anyone helping us our here.

Hey @graeme-winter ! Thanks for coming to the community meeting and for making the issue. As we discussed in the meeting, one option is to use plane rendering for things that fit in GPU memory (cc @alisterburt ). For doing the "slabbing" on the CPU, the "data source" refactor that is under discussion would probably be the way to go, but is not yet implemented.
As I understand it, you have images that are (time, x, y) and you want to view your image time slice by time slice such that each slice is the average of +/- n adjacent time slices. Is that correct?
For now, i am curious if there is a way to do this with dask and/or dask-image. If my understanding is correct, it seems like what you are after is a 1D sliding window filter along your "time" axis. I believe @grlee77 mentioned in the meeting chat that there is a 1D filter in dask-image, but I can't remember what it is called. Maybe it was in dask_image.ndfilters?
Since the filter can be evaluated lazily, I am wondering if you can do something like the following:

When you load your image as a dask array (datea and dask array likely should be chunked along time), apply the 1D sliding window averaging filter before passing it to napari .
load the filtered image as an image layer in napari
I think if the image is chunked along time and the filter is set up correctly it should calculate the average lazily with the dim slider
Add a GUI for setting the window size and when the user changes the window size, the image layer data gets updated with an image with the new filter size applied.

For some resources on performing lazy computations with dask/napari, here is a tutorial and an image.sc thread that may be of interes.
I am far from an expert on dask, so perhaps @GenevieveBuckley has some better ideas.

Ah, maybe what you are looking for is the uniform filter with shape (10, 1, 1) (or is it (10, 0, 0)?)for images that are ordered (time, y, x)

I was curious, so I gave it a go and I think it is working (see the script below). You can toggle the visibility of the filtered and raw image layers to see the difference. As I mentioned, I am not a dask expert, so others may have better ways to implement it.
import napari

import dask
import dask_image.ndfilters

slice_width = 100
n_t = 10000

# set the width of the averaging window
window_width = 10

# make a fake image
# note the chunk size is 1 along the 0th dimension
raw_im = dask.array.random.random(
    size=(n_t, slice_width, slice_width),
    chunks=(1, slice_width, slice_width)
)

# filter the image along the 0th dimension
filtered_im = dask_image.ndfilters.uniform_filter(
    raw_im, size=[window_width, 1, 1]
)

# add the images to the viewer
# note that the contrast limits are set. this is to
# prevent napari from trying to auto calculate the clims,
# which would require reading a lot of chunks
# (not sure this is strictly necessary)
viewer = napari.view_image(raw_im, contrast_limits=(0, 1))
viewer.add_image(filtered_im, contrast_limits=(0, 1))

napari.run()

Do you think this would work for you, @graeme-winter ?

@kevinyamauchi I love it! We should definitely consider trying to add this to core napari. Possible routes to this have been discussed/half implemented before at #1744 #1820 (there's a whole rabbit hole to go down here if you choose, this is clearly something people have wanted for a while.
I like the idea of exposing this with a 'thickness' parameter associated with the point slicing that we do currently in 2D (it fits well with how things are described in the GPU arbitrary plane stuff in #3023) but could also be convinced by a range slider with movable endpoints to set a 'slice range' for each dimension.
I'm not sure whether it makes sense to charge forwards on this with respect to the slice/chunk discussions going on around async/data source - maybe @perlman could add his thoughts here, does it make sense for us to implement something here which may be clobbered by your work in the near future?

@kevinyamauchi nailed it thank you
added:
a = dask_image.ndfilters.uniform_filter(a, size=[10, 1, 1])

now we have a stack of 10 images. So: time to start looking at this as a UI toolkit.
I suspect that the average user would find a "thickness" parameter as suggested by @alisterburt pretty useful, but from here I think we can get what we need doing done. Totally appreciate the fast feedback! ++ kudos

I'm not sure whether it makes sense to charge forwards on this with respect to the slice/chunk discussions going on around async/data source - maybe @perlman could add his thoughts here, does it make sense for us to implement something here which may be clobbered by your work in the near future?

Given the planned changes to the data model, I would lean towards keeping this outside of core napari if there is a reasonable way to do so. Also, depending on the image size and filter type, I could imagine that there is some tuning (e.g., chunk size, tile size) to get reasonable performance, so it might be too "fiddly" to make a core feature. That being said, I think it would be awesome to see something like this as a core feature in the future!
Related to chunking, I just remembered that @GenevieveBuckley made a nice blog post on choosing chunk sizes that may be useful here: https://blog.dask.org/2021/11/02/choosing-dask-chunk-sizes

makes sense @kevinyamauchi ! Let's leave for now. I might turn your example into something for the docs over the weekend, it's super powerful and I'll definitely be using it too 🙂
Glad that should get you going @graeme-winter - I'll close this now but don't hesitate to reach out if you run into more issues!

@kevinyamauchi nailed it thank you
added:
a = dask_image.ndfilters.uniform_filter(a, size=[10, 1, 1])

now we have a stack of 10 images. So: time to start looking at this as a UI toolkit.
I suspect that the average user would find a "thickness" parameter as suggested by @alisterburt pretty useful, but from here I think we can get what we need doing done. Totally appreciate the fast feedback! ++ kudos

Great! I am happy you're able to move forward! Happy to chat about adding GUI elements, etc.  In case you haven't seen it, we have a "zulip" (kind of like slack) that is a great place to get more "realtime" feedback/discussion:
Also, in case the uniform filter is too slow for your data, you could try the "coarsen" function. I haven't tried it, but I think it should be faster. You could use this to bin the data long the "time" axis (e.g., 100 time slices binned 10x would become 10 time slices). You can choose the bin size and function used to do the binning (e.g., mean, sum, etc.)
https://docs.dask.org/en/latest/generated/dask.array.coarsen.html

@graeme-winter thanks for the issue!

I would lean towards keeping this outside of core napari if there is a reasonable way to do so.

Actually I want to say that this is in fact something we've wanted to have in napari pretty much since its inception, though the only mention I can find for it is the top item in this list on #420! As you can see the item remains unticked :sweat_smile:, but we'll get there! So @kevinyamauchi @alisterburt I think I'll reopen this issue since as far as I can tell this is not written down in any specific issue!
The UI here would look like the contrast limits slider: changing the "mode" on a slider from "slice" to "projection" would separate the slider to two components, and napari would do whatever projection the user selected (e.g. dropdown arrow next to axis name) in the selected range of slices.
I also wanted to add dask-image is a powerful library but so is plain dask! I actually got the sum working by itself with NumPy/dask slice tricks:
import napari
from dask import array as da
from dask.array.lib.stride_tricks import sliding_window_view
from skimage import data

blobs = data.binary_blobs(length=64, n_dim=3)
blobs_dask = da.from_array(blobs, chunks=(1, 64, 64))
blobs_dask_windows = sliding_window_view(
    blobs_dask, window_shape=(5, 64, 64))[:, 0, 0, ...]
)  # original shape [60, 1, 1, 5, 64, 64], slice out singleton axes
blobs_sum = da.sum(blobs_dask_windows, axis=1)
viewer = napari.view_image(blobs_sum)

napari.run()

I had come across stride_tricks.as_strided but not sliding window view, you just blew my mind @jni 🤯

Recently ported to NumPy from scikit-image. :smiley:

@graeme-winter et al, check #3604 for an example using magicgui to change the window size dynamically from the UI. :heart: :snake: + Dask.


feat(pie-toggle-switch): DSW-991 toggle switch

Describe your changes (can list changeset entries if preferable)
Author Checklist (complete before requesting a review)

[ ] I have performed a self-review of my code
[ ] If it is a core feature, I have added thorough tests
[ ] If it is a PIE Docs change, I have reviewed the Docs site preview
[ ] If it is a component change, I have reviewed the Storybook preview
[ ] If there are visual test updates, I have reviewed them properly before approving

Reviewer checklists (complete before approving)
Reviewer 1

[ ] If it is a PIE Docs change, I have reviewed the PR preview
[ ] If there are visual test updates, I have reviewed them

Reviewer 2

[ ] If it is a PIE Docs change, I have reviewed the PR preview
[ ] If there are visual test updates, I have reviewed them

https://github.com/justeattakeaway/pie/assets/28605803/52293fbb-6f9e-4372-9a24-6b313260926f
the RTL styles seem to be off 👀

Screen.Recording.2023-08-03.at.16.02.38.mov
the RTL styles seem to be off 👀

Thanks @raoufswe, should be fixed now


Error setting up entry central for ocpp

Version of the custom_component
v.0.4.28

Configuration
Error occurs at the config flow, no additional YAML configuration.
It does not matter if I change any of the default values or leave them as they are during integration setup.
Modification of manifest.json to websockets==9.1 did not work (found here: https://github.com/lbbrhzn/ocpp/issues/172#issuecomment-939136784)
Describe the bug
Error setting up entry central for ocpp.
This error occurs when trying to configure the integration from the config flow, with the default configuration.
Debug log

This error originated from a custom integration.

Logger: homeassistant.config_entries
Source: custom_components/ocpp/api.py:171
Integration: Open Charge Point Protocol (OCPP) (documentation, issues)
First occurred: 19:33:47 (2 occurrences)
Last logged: 19:37:06

Error setting up entry central for ocpp
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 335, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/config/custom_components/ocpp/__init__.py", line 71, in async_setup_entry
    central_sys = await CentralSystem.create(hass, entry)
  File "/config/custom_components/ocpp/api.py", line 171, in create
    server = await websockets.server.serve(
  File "/usr/local/lib/python3.9/site-packages/websockets/legacy/server.py", line 1071, in __await_impl__
    server = await self._create_server()
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1494, in create_server
    raise OSError(err.errno, 'error while attempting '
OSError: [Errno 98] error while attempting to bind on address ('<IP_ADDRESS>', 9000): address in use

System Config

version
core-2022.3.8

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.9.9

os_name
Linux

os_version
5.10.92-v8

arch
aarch64

timezone
Europe/Berlin

Home Assistant Community Store

GitHub API
ok

Github API Calls Remaining
4880

Installed Version
1.22.0

Stage
running

Available Repositories
1007

Downloaded Repositories
6

Home Assistant Supervisor

host_os
Home Assistant OS 7.5

update_channel
stable

supervisor_version
supervisor-2022.03.5

docker_version
20.10.9

disk_total
457.7 GB

disk_used
59.6 GB

healthy
true

supported
true

board
rpi4-64

supervisor_api
ok

version_api
ok

installed_addons
Samba share (9.5.1), Check Home Assistant configuration (3.10.0), ESPHome (2022.3.2), File editor (5.3.3), Mosquitto broker (6.0.1), Terminal & SSH (9.3.0), pigpio (1.5.0), Z-Wave JS (0.1.55), deCONZ (6.12.0), Samba Backup (5.0.0), rtl_433 MQTT Auto Discovery (0.3.1), Portainer (2.11.1-3), rtl_433 (0.2.1)

Lovelace

dashboards
1

resources
4

views
5

mode
storage

Looks like some other service is installed op that uses port 9000. Can you try a different port number?
We should improve feedback to the user if this occurs...

Hello @lbbrhzn, that seem to have worked, I got the integration set-up properly by using another port (9123).
Thanks for the advice!


Change position of legend in 1D SAXS to bottom-right and outside the figure, if possible

The new caption tab is definitely nice, however there will eventually come a time where the SAXS is too crowded and the caption is too long for it to be placed anywhere on the frame. Is it possible to put it outside the frame?

Problem fixed; closing the issue


Flashlist produces warning when passed to StyledComponent

Current behavior
Our project is using StyledComponents. Now, while migrating to Flashlist I found that it is producing warning, even though I didn't pass any styles to it.
import styled from 'styled-components/native'

const List = styled(FlashList).attrs(({ theme }) => ({
  ListHeaderComponentStyle: {
    backgroundColor: theme.color.background,
    borderBottomWidth: 1,
    borderColor: theme.color.separator,
  },
}))({})

Expected behavior
No warning if styles are empty
To Reproduce
see code snipped above
Platform:

[x] iOS
[x] Android

Environment
"@shopify/flash-list": "1.1.0"

Styled component passes style prop as an array with an empty object to flashlist. I think we can change the condition in the warning by thinking that style props can be array.


Set withMuxing flags dynamically

Preview is available here:http://laboratory-pr535.previews.kube001.services.stellar-ops.com/

Passed testing w/ sending to both Muxed and regular accounts


new AssetMode does not implement Debug

Bevy version
0.12

This seems like a straightforward fix, could you open a PR?

Done @nicopap .


Description field in Articles is not active

When I'm creating new Article, the field 'description' is not active. I click on, but there is no action and I can't to type.
If I click on some special button, f.e. 'smiles' and choose one, I can type my description text.
If I edit Article there is no problem with it.
There is problem only with one field and only on one page.
I use docker containers with php 7.0, Ubuntu 14

Hi, sorry for late reply. Do you still have problem with description field?

Thanks for letter, the problem is decided.
Now I have no error.

2 февр. 2018 г., в 15:50, Mariusz Rajczakowski<EMAIL_ADDRESS>написал(а):
Hi, sorry for late reply. Do you still have problem with description field?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/mariocoski/laravel-blogger/issues/240#issuecomment-362524033, or mute the thread https://github.com/notifications/unsubscribe-auth/APZuszDgKH2SEzB11KxRxWKDmaeIpv_hks5tQsxygaJpZM4Q0tTA.


Quick typo fix in README

Description of changes:
Quick typo fix here.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@awsandy Mind reviewing?

Thank you


Unsupported object count in repo statistics

Add number of unsupported objects below "Number of objects"

@mbtools - FYI

good idea


PowerRegisterSuspendResumeNotification error on Azure App Services with go 1.13.7

What version of Go are you using (go version)?

Go version 1.13.7 (also with 1.13.6/5/4.. )   but works with 1.13

Does this issue reproduce with the latest release?
1.13.7 yes
Believe this might be related to issue 35447
What operating system and processor architecture are you using (go env)?
Note, building is fine (details below are just from the compile machine). It's on Azure App Services where the error happens (runtime).
go env Output
$ go env
C:\Users\kenfa\projects\gorepo> go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\kenfa\AppData\Local\go-build
set GOENV=C:\Users\kenfa\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\kenfa\projects\gopath
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\users\kenfa\packages\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\users\kenfa\packages\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\kenfa\AppData\Local\Temp\go-build929673298=/tmp/go-build -gno-record-gcc-switches

What did you do?
Running a binary (windows executable) in an Azure App Service generates the stack trace:
A simple repro can be achieved with:
package main
import "fmt"
func main() {
fmt.Printf("hello world\n")
}
What did you expect to see?
hello world
What did you see instead?
runtime: PowerRegisterSuspendResumeNotification failed with errno= 5
fatal error: runtime: PowerRegisterSuspendResumeNotification failure
runtime stack:
runtime.throw(0x4dbc9c, 0x37)
c:/users/kenfa/packages/go/src/runtime/panic.go:774 +0x79 fp=0x82fdd8 sp=0x82fda8 pc=0x42cf09
runtime.monitorSuspendResume()
c:/users/kenfa/packages/go/src/runtime/os_windows.go:307 +0x20a fp=0x82fe80 sp=0x82fdd8 pc=0x42992a
runtime.goenvs()
c:/users/kenfa/packages/go/src/runtime/os_windows.go:544 +0x1ba fp=0x82fed8 sp=0x82fe80 pc=0x42a2aa
runtime.schedinit()
c:/users/kenfa/packages/go/src/runtime/proc.go:554 +0xa9 fp=0x82ff30 sp=0x82fed8 pc=0x42f8f9
runtime.rt0_go(0x82ff60, 0x7fff2bc184d4, 0x82ff60, 0x0, 0x7fff2bc184d4, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
c:/users/kenfa/packages/go/src/runtime/asm_amd64.s:214 +0x13d fp=0x82ff38 sp=0x82ff30 pc=0x452e5d

@kpfaulkner, what are specifics of Azure App Services config?
This has appeared before in #35447 and #36557.
@gopherbot add OS-Windows release-blocker
cc @zx2c4 @aclements @ianlancetaylor

@gopherbot add OS-Windows
@gopherbot add release-blocker

@networkimprov In this case I simply made a free tier app service plan via the Azure Portal and made an empty app service within that.   I can make up a set of powershell/az commands to do the same if it helps, but if using the UI it's literally app service plan -> windows ->
The quickest way to deploy in this case is just drag/drop the go-built exe file via the SCM web interface. I can provide screen shots with literal step-by-step if it helps.

I'm pretty sure my original fix for this issue rather than the whack a mole as was requested by interlocuteurs is preferable.
 The Linux kernel in recent years has adopted this policy too, preferring WARN_ON to BUG_ON.

Prob should be milestoned to 1.14.

@gopherbot please backport. It's another instance of this regression...

@kpfaulkner please see, if you can test this change
https://golang.org/cl/219657

I'm pretty sure my original fix for this issue rather than the whack a mole as was requested by interlocuteurs is preferable.

I agree. My approach did not work.
Alex

Friendly ping @kpfaulkner. Did you see the message @alexbrainman has posted above? Are you able to test CL 219657 and let us know if it fixes this issue for you? Thanks.

Ah, didn't see that. Currently traveling. Will look at that in the next few days.


Why node-pty instead of childpty

Thanks for Open sourcing this ! :rose: ❤
Quick questions:

Is childpty pure js https://www.npmjs.com/package/childpty

If so why not use that instead of node-pty : https://github.com/speedterm/speedterm/blob/d4032cb4aadc26e4c827c64b0da1d17dffacf9b5/package.json#L42
In full disclosure I need a terminal support for alm.tools https://github.com/alm-tools/alm/issues/133#issuecomment-248539599 but don't want to force people to have a working node-gyp toolchain 😢

hi @basarat! thanks for your questions.
I made childpty package out of original https://github.com/Gottox/child_pty but compatible with rollup. Then I switched to node-pty which seems to be more recently updated and also works on Windows powershell.exe. Basically, Win support was the only reason to switch to node-pty.
Checked alm project and must say that I love it, I am also a heavy TypeScript user and never heard of that before. Back to your question, there are plenty of "childtty" forks around and I since now I did not notice one that works without node-gyp, I believe only thing that you can do is to provide package that already have compiled c++ bindings included, just like node-sass does.
I strongly believe that there is no pure JS/TS package that works with pseudo terminals, also cannot imagine how that could be possible.
Btw, let me know if you need help integrating that thing into your project.

I strongly believe that there is no pure JS/TS package that works with pseudo terminals, also cannot imagine how that could be possible.

Thanks for your answer, time and kind words :heart: :rose:

I believe only thing that you can do is to provide package that already have compiled c++ bindings included, just like node-sass does.

Fingers crossed that node-pty does that someday ❤


Fix: .editable(false) on "reference" type field in EditView

When applying .editable(false) field method on field of "reference" type for EditView - we get no visible representation of this field - we get a link with empty inner text. This is because of getReadWidget() which passes an empty value to corresponding directive.
So I've slightly changed this function to fix this issue.

It's not normal that you get an empty value. Does the related entity have an empty title or name?
For instance, for a Reference from Comment to Post:
comment.listView().fields([
    ...,
    nga.field('post_id', 'reference')
        .label('Post')
        .targetEntity(post)
        .targetField(nga.field('title'))
])

The displayed value when editable is false is the post title. Your patch makes it fallback to post_id, but you shouldn't represent the related entity by a nullable field in the first place...
So either I don't understand your use case, or the patch is wrong.

Related entity doesn't have empty title/name.
In your example you're talking about listView and it seems to be no problem there.
The problem takes place in editView. Let's say, that I'm in need to have a Reference from Comment to Post defined only once - on Comment creation. Therefore in editView this Reference shouldn't be editable. 1d7f47f illustrates my attempt to get such behavior. As a result we can see an empty string instead of post title, while editing any of the Comments.
But you were right about my patch. It was wrong. c8960a4 is my another attempt to fix this issue. Now it seems to work as expected.

You patch fixes the non-editable reference in edit view, but in return breaks the editable reference...

Fixed in b71d686ec268287d0166565ddfe2dc8dc6bda0b8
I'll try to be more attentive next time.

Thanks!


Implement non-caching, per-kustomization GC-client/statusPoller for cross-cluster kubeconfigs

Fixes #127
First shot at this after familiarizing myself with all of the clientcmd and restclient types/methods.
Pending extensive testing /w CAPI.
Clients are re-created from the KubeConfig SecretRef for each reconciliation of a particular Kustomization.
( kubeconfigs such as the ones used for CAPA managed EKS clusters are regularly refreshed behind the scenes. )
I chose not to create a cache for these clients since they only survive a single reconciliation.
We could instead maintain a map of NamespacedNames to restClients in the KustomizationReconciler.
This might be worthwhile and fairly simple -- let me know what you think.
Currently, when not specifying a KubeConfig, we return the Reconciler's general client and statusPoller.
I expect to change this for security reasons in the future Impersonation patches, since HealthChecking
could be a form of cross-tenant information disclosure, and it could be possible to trick the Garbage Collector
into deleting things you'd otherwise not have access to.
I wonder how we can e2e test this?

I chose not to create a cache for these clients since they only survive a single reconciliation.

I don't think we should be doing any caching,  re-creating the KubeConfig for each reconciliation is 💯

I expect to change this for security reasons in the future Impersonation patches, since HealthChecking
could be a form of cross-tenant information disclosure, and it could be possible to trick the Garbage Collector
into deleting things you'd otherwise not have access to.

Yes I think we should address this when we refactor the Impersonation.

@stealthybox can you please confirm that this works with CAPI (GC+HealthChecking)? If so I would merge this without e2e tests and figure out later how to spin un a CAPI Kind provider in GitHub Actions. I want to get this out os other people could test this with other CAPI providers. Before releasing this, we need to a add a section to the API docs that explains how the KubeConfig filed works and how it can be used from a CAPI management cluster.

I've verified that Apply, Prune/GC, HealthCheck, and Delete are all working reliably with spec.kubeConfig on a CAPI child-cluster. 🎉
I've added some rather verbose docs for these fields, inline with the API, along with a new section to the documentation.


USHIFT-60: Streamline R4E ISO creation on aarch64 platform for AWS environment

Minor fixes very necessary, mostly cosmetic:

Fixed R4E memory allocation to be 3GB
Make sure pull secret file is readable
Verify user home directory permissions and umask for Image Builder to work
Add scripts/image-builder/create-vm.sh script that streamlines R4E VM env setup and creation
Make sure virt-install is installed

Closes USHIFT-60

/retest-required


modify maven release to support GitHub packages

feat(jsii-release-maven): support publishing to GitHub packages maven repository (likely other repos as well)
Closes #11

These restructures the maven release script to support non-nexus based repositories. In particular, a parallel execution path exists that simply uses the maven deploy plugin.
At this particular time, signing is only supported for nexus repositories.
The username, password, and gpg passphrase are also kept out of files and replaced with environment variable lookups.
Did a bit of cleanup on error handling to route all single line errors through the error function

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I have tested the changes on GitHub packages, but unfortunately I don't have access to a Sonatype account for testing with Maven Central.

It should be easy to set up an account and perform some tests.

Getting an account was easier than expected. I should be able to test it out sometime this week.

I was able to successfully deploy to maven central. I also tested the already published case.
Getting gpg to correctly handle no user input is rather tricky and seems heavily dependent on which version you have installed. I had to add a wrapper script per https://stackoverflow.com/questions/60417391/pass-in-list-parameter-to-maven-using-the-cli-gpgsign-and-deploy-file.
Are there particular versions which compatibility needs to be ensured?


Unblock MonsterFixupTest for SQLCE (which only supports dates after 1753

fixes #8496

Thanks @ErikEJ. I merged this.


[Snyk] Upgrade mongoose from 7.6.0 to 7.6.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade mongoose from 7.6.0 to 7.6.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 23 days ago, on 2023-10-09.

Release notes

Package name: mongoose

7.6.1 - 2023-10-097.6.1 / 2023-10-09

fix: bump bson to match<EMAIL_ADDRESS>exactly #13947 hasezoey
fix: raw result deprecation message #13954 simllll
type: add types for includeResultMetadata #13955 simllll
perf(npmignore): ignore newer files #13946 hasezoey
perf: move mocha config from package.json to mocharc #13948 hasezoey

7.6.0 - 2023-10-067.6.0 / 2023-10-06

feat: upgrade mongodb node driver -> 5.9.0 #13927 #13926 sanguineti
fix: avoid CastError when passing different value of discriminator key in $or #13938 #13906

    from mongoose GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Pull request merged

This is an automated message from Fork, Commit, Merge - web [BOT].

Thank you for your contribution! Your pull request has been merged and your name has been added to the List of Contributors in README.md.
Please leave a star if you enjoyed working on this project.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects here.


Add Compliance check: pinActionsToSHA

How the Check Works
Provide a clear definition based on the spreadsheet
Pending Tasks
You can find more details in the contributing guide

[ ] 1. Define a Good Implementation Example

[ ] Read the documentation (guidelines, best practices...)
[ ] Brainstorm how to implement this check (logic, alerts, tasks, validations, edge cases...).
[ ] Achieve an agreement on the implementation details before starting to work on this.

[ ] 2. Update Check Record Example

[ ] Update the compliance_checks row with the following fields: how_to_url, implementation_status, implementation_type and implementation_details_reference
[ ] Check the migration scripts using npm run db:migrate and npm run db:rollback
[ ] Update the database schema by running npm run db:generate-schema

[ ] 3. Implement the Business Logic Validator Example and Check Example

[ ] Add the specific validator in src/checks/validators/index.js
[ ] Add the check logic in src/checks/complianceChecks
[ ] Ensure that the check is in scope for the organization (use isCheckApplicableToProjectCategory)
[ ] Ensure that the severity value is well calculated (use getSeverityFromPriorityGroup)
[ ] Add the alert row in the compliance_checks_alerts table when is needed.
[ ] Add the task row in the compliance_checks_tasks table when is needed.
[ ] Add the result row in the compliance_checks_results table.

[ ] 4. Ensure It Works as Expected

[ ] Add new unit tests for the validator check.
[ ] Add new integration test cases for this check.
[ ] Verify that all tests are passing.
[ ] Run the command check run --name {check_code_name} and verify the changes in the database. Update the seed script if needed (npm run db:seed)

[ ] 5. Update the website Example

[ ] Review the current content it in https://openjs-security-program-standards.netlify.app/details/{check_code_name}
[ ] Create a PR in https://github.com/secure-dashboards/openjs-security-program-standards to include how we calculate this check and include additional information on the mitigation if needed.

this can be solved using the OSSF Sorecard table, we can use the pinned_dependencies_score and the pinned_dependencies_details while it mention *GitHubAction not pinned by hash*, like in:
    "pinned_dependencies_reason": "dependency not pinned by hash detected -- score normalized to 2",
    "pinned_dependencies_score": 2,
    "pinned_dependencies_documentation_url": "https://github.com/ossf/scorecard/blob/ea7e27ed41b76ab879c862fa0ca4cc9c61764ee4/docs/checks.md#pinned-dependencies",
    "pinned_dependencies_documentation": "Determines if the project has declared and pinned the dependencies of its build process.",
    "pinned_dependencies_details": "Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:133: update your workflow using https://app.stepsecurity.io/secureworkflow/jshttp/http-assert/ci.yml/master?enable=pin\nWarn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:206: update your workflow using https://app.stepsecurity.io/secureworkflow/jshttp/http-assert/ci.yml/master?enable=pin\nWarn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:218: update your workflow using https://app.stepsecurity.io/secureworkflow/jshttp/http-assert/ci.yml/master?enable=pin\nWarn: npmCommand not pinned by hash: .github/workflows/ci.yml:166\nWarn: npmCommand not pinned by hash: .github/workflows/ci.yml:182\nInfo:   3 out of   4 GitHub-owned GitHubAction dependencies pinned\nInfo:   1 out of   3 third-party GitHubAction dependencies pinned\nInfo:   0 out of   2 npmCommand dependencies pinned",

I believe that we can add tasks but not sure if alerts on this case.... WDYT @ruddermann?


No suitable method found for addExternalAssessment

Hi All,
I use Sakai 12.5 in production server, and I want to install attendace tool.
I forked attendace tool, and I changed version from 12-SNAPSHOT to 12.5 in pom.xml
And I run below code in attendace directory, but I'm gettin getting error[1]
mvn clean install sakai:deploy -Dmaven.tomcat.home=/opt/tomcat -Dsakai.home=/opt/tomcat/sakai -Djava.net.preferIPv4Stack=true -Dmaven.test.skip=true
Apache Maven 3.3.9
java version "1.8.0_171"
Any help?
[1]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile (default-compile) on project attendance-impl: Compilation failure: Compilation failure:
[ERROR] /root/gtu/attendance/impl/src/java/org/sakaiproject/attendance/impl/AttendanceGradebookProviderImpl.java:[77,34] no suitable method found for addExternalAssessment(java.lang.String,java.lang.String,,java.lang.String,java.lang.Double,,java.lang.String,,boolean,)
[ERROR] method org.sakaiproject.service.gradebook.shared.GradebookExternalAssessmentService.addExternalAssessment(java.lang.String,java.lang.String,java.lang.String,java.lang.String,double,java.util.Date,java.lang.String) is not applicable
[ERROR] (actual and formal argument lists differ in length)
[ERROR] method org.sakaiproject.service.gradebook.shared.GradebookExternalAssessmentService.addExternalAssessment(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.Double,java.util.Date,java.lang.String,java.lang.Boolean) is not applicable
[ERROR] (actual and formal argument lists differ in length)
[ERROR] method org.sakaiproject.service.gradebook.shared.GradebookExternalAssessmentService.addExternalAssessment(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.Double,java.util.Date,java.lang.String,java.lang.Boolean,java.lang.Long) is not applicable
[ERROR] (actual and formal argument lists differ in length)
[ERROR] /root/gtu/attendance/impl/src/java/org/sakaiproject/attendance/impl/AttendanceGradebookProviderImpl.java:[123,38] no suitable method found for updateExternalAssessment(java.lang.String,java.lang.String,,,java.lang.String,java.lang.Double,,boolean)
[ERROR] method org.sakaiproject.service.gradebook.shared.GradebookExternalAssessmentService.updateExternalAssessment(java.lang.String,java.lang.String,java.lang.String,java.lang.String,double,java.util.Date) is not applicable
[ERROR] (actual and formal argument lists differ in length)
[ERROR] method org.sakaiproject.service.gradebook.shared.GradebookExternalAssessmentService.updateExternalAssessment(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.Double,java.util.Date,java.lang.Boolean) is not applicable
[ERROR] (actual and formal argument lists differ in length)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :attendance-impl
[root@sakai attendance]# vim pom.xml

I recommend using the 12.x maintenance branch:
https://github.com/sakaicontrib/attendance/tree/12.x
If you want to use Sakai 12.5 and not 12.6, you would need to use this Git commit:
https://github.com/sakaicontrib/attendance/commit/76bd548008170514418189e1c69982193636aabd

Hi @ottenhoff
I have already use 12.x maintenace branch for attendace.
I've changed from 12-SNAPSHOT to 12.5 before, I left it (12-SNAPSHOT) as it is now
[root@sakai gtu]# git clone https://github.com/sakaicontrib/attendance.git
Cloning into 'attendance'...
Resolving deltas: 100% (2293/2293), done.
[root@sakai gtu]# cd attendance/
[root@sakai attendance]# git checkout 12.x
Branch 12.x set up to track remote branch 12.x from origin.
Switched to a new branch '12.x'
[root@sakai attendance]# git checkout 12.x
Already on '12.x'
[root@sakai attendance]# mvn clean install sakai:deploy -Dmaven.tomcat.home=/opt/tomcat -Dsakai.home=/opt/tomcat/sakai -Djava.net.preferIPv4Stack=true
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.sakaiproject.attendance:attendance:20180412: Could not find artifact org.sakaiproject:master:pom:12-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 29, column 10
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.sakaiproject.attendance:attendance:20180412 (/root/gtu/attendance/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for org.sakaiproject.attendance:attendance:20180412: Could not find artifact org.sakaiproject:master:pom:12-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 29, column 10 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException


python311Packages.bravado-core: 6.1.0 -> 6.6.1

Diff: https://github.com/Yelp/bravado-core/compare/v6.1.0...v6.6.1
Changelog: https://github.com/Yelp/bravado-core/blob/v6.6.1/CHANGELOG.rst
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

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

5 packages built:

powerdns-admin
python310Packages.bravado-core
python310Packages.bravado-core.dist
python311Packages.bravado-core
python311Packages.bravado-core.dist

@ofborg test powerdns-admin


cpu very  high

start recording cpu very high on iphone 7plus

Have the same problem at Phone 8 plus. Also with friends noticed that it is low fps at new devices (iPad, iPhone 8 plus, iPhone 7 etc.) but at 3d iPad and iPhone 5s it is working good.

I'm using this library inside a react-native app via react-native-screen-recorder and running in similar performance issues has anyone already figured out how to handle this leaks?

@JanOwiesniak find any solution to this? Seems to work fine on iOS simulator, but I get a black screen video when recorded on a real device.

@ami9000 no i did not. My approach was to not use this library at all.
Luckily the part i wanted to record was part of a Unity Application (inside React Native) so that i could fallback to something from the Unity Asset Store.
My app stack is very specific so i guess this wont help here.


[UNTHEMED]: An option for a semi translucent background

Client Mod
Vencord
Please provide screenshots of the unthemed areas.
Vencord has a transparent window with background blur, but this theme is all solid and it would be cool to have a branch with it being translucent
Before Submitting

[X] I checked for similar reports of this issue.
[X] I am on the latest stable Discord version.
[X] I am on the latest version of the theme.
[X] I have reinstalled the theme.

Not worth the time or effort to do and maintain.


Switching to beta channel downloads beta channel every time

when i switch to beta channel from stable. the beta channel sdk downloads to my computer if i go back to stable channel and switch to beta channel cli downloads the beta channel again. is there any way to avoid downloading the beta channel every time i switch to beta.

Hi @tonydavidx
I see there's an open issue addressing the case you described (here https://github.com/flutter/flutter/issues/44212).
Please follow up on that issue, I'm closing the current one as a duplicate.
If you disagree, please write in the comments and I will reopen it.
Thank you


CRLF line endings cause scripts failures

I think I can make it brief, because it is a rather common issue which has been discussed on many places.
context

version freshly installed<EMAIL_ADDRESS>on platform : Linux

example failure
$ xml-js --help
/usr/bin/env: ‘node\r’: No such file or directory
/usr/bin/env: use -[v]S to pass options in shebang lines

some references for workarounds and solutions

npm/npm#12371
npm/npm#17161
nodecg/nodecg-cli#67

Sorry, my bad. I was hitting a conflict between npm and yarn. Changing path order solved the issue.


Support importing from thunder client json file

I have checked the following:

[X] I've searched existing issues and found nothing related to my issue.

Describe the feature you want to add
I've been using the Thunder Client extension for a while, but now I'm switching to Brono. However, I'm encountering issues when trying to import my Thunder Client collection into Brono.
I attempted to convert the Thunder Client collection to a Postman collection and then import the converted collection into Brono, but it didn't work. Is there a way to support importing from the Thunder Client JSON file?
Mockups or Images of the feature

We currently don't support importing a Thunderclient collection, but we are tracking it here #511. However, converting the Thunderclient collection to a Postman collection and then importing it into "Bruno" should work. Would you be able to share the collection you are working on so that we can debug this further?

thunder-collection_Mi9raa_postman.json

Closing this as this is a duplicate of #511


target from elements missing declarative reference

It is quite inconvenient when for HTML nodes/Web Components there is a need for JS while it could be done in primitive way on HTML level.
In mwc-menu component there is a anchor reference to another element which contradicts the declarative nature of HTML components as self-sufficient solution. In HTML such kind of references are usually provided by reference by for or href attribute which is treated as lookup by ID.
It is understandable that ID meant to be unique and does not work well for auto-generated code. But the way of using JS for relation definition goes against separation of concerns in css/js/html: it belongs to HTML as structure definition layer adding additional burden for HTML developers.
Proposing to add optional for attribute which would provide ID of referenced element.
If there is a will to fix the lack of classic for flexibility, the css selector would be more useful.
Going further, CSS does  not provide back reference up on dom  tree, which is essential for using HTML as structure. Proper solution should account such back-and-forward selectors. I.e. back-lookup following with usual forward lookup CSS.
<mwc-menu for="...li .another-child">
In sample above for attribute looks up up the dom  multiple levels until closest li element reached. Than .another-child css selector picks element.
Alternatives
custom element for element selection which would populate anchor property of menu. It allows to keep the html structure where it belongs - in DOM and allows to make app without engaging custom JS layer.
<wel-css-query src="#cornerButton" dst="#menu1" dstprop="anchor" ></wel-css-query>
https://github.com/EPA-WG/web-elements-loader/blob/master/src/wel-css-query.js

in this case, javascript-less declarative setup fights with encapsulated modularity. A component should only know about itself and its subtree. By adding for, the component would have to traverse its siblings or parent trees. This additionally runs into query selection issues and shadow dom. How far up and how many shadow roots should the querySelector traverse? What if it is slotted in and should actually traverse a slot's assignedNodes. This would lead to quite a performance hit as opposed to the user setting the anchor property themselves.
Our recommended approach here would be the mediator method where a common parent would mediate this data on menu's behalf. In lit-element it is possible to do the following pattern:
@customElement('my-element')
export class MyElement extends LitElement {
  @query(#button) buttonElement!: HTMLButtonElement;
  @query(#menu) menuElement!: Menu;
  render () {
    return html`
      <button id="button" @click=${this.menuElement.show}>This is the anchor</button>
      <mwc-menu id="menu" .anchor=${this.buttonElement}></mwc-menu>
    `;
  }
}

the @query decorator allows for declarative query selection; unfortunately there is not a native html way to do this.
I like your second recommendation more than the first, though, I feel that implementing a generic query selector or packaging one with the component is out of the scope of MWC.

@e111077, Sorry you did not want to collect counterarguments and closed the story. IMO without all arguments on hand.

A component should only know about itself and its subtree.

Which is OK, it does not know ahead of time about DOM where it would be injected. It also does not care if developer made a wrong reference, right? It is developer who sets an anchor in context where component resides. for is just another syntax to achieve same goal: reference the node, only declarative instead of JS.

This additionally runs into query selection issues and shadow dom.

What issues you foresee? I could not find any. Like none.

How far up and how many shadow roots should the querySelector traverse?

Node.getRootNode() method been made for a reason: defining available scope. It would limit "for" selector to scope. Developer also would work in the scope of current container and use relative selector only within. It is not intention of for attribute to refer outer scopes( that is subject of href BTW ).
The ... would traverse not more than Node.getRootNode() before failing. But usual use case is few levels up matching the complexity of container component. That is way less than using global IDs or global selectors. And even less than selector from rootNode which is current pattern for internal CSS selectors. So it is more performant.

What if it is slotted in and should actually traverse a slot's assignedNodes. This would lead to quite a performance hit as opposed to the user setting the anchor property themselves.

You have same issues with @query(#button) so argument of performance is not relevant. Instead of ID it could be any CSS selector which also would be sensitive to slot border.
As for code complexity try to compare your sample with this one:
@customElement('my-element')
export class MyElement extends LitElement {
  render () {
    return html`
      <button @click=${this.menuElement.show}>This is the anchor</button>
      <mwc-menu for="... button" ></mwc-menu>
    `;
  }
}

It is 3x smaller and simpler:

no IDs, making HTML readability simpler, less chances for typo-kind mistakes
no intermediate variables, which is a just initialization time garbage polluting JS

The primary advantage that developer is focusing on functional side skipping the plumbing coding.
Which I really hope is in scope of MWC :)

PS. JS has given a unique AOP ability to extend existing functionality of JS module, so I could mix-in  HTMLElement including MWC components by adding extra attributes support, including proposed one. Have to think about.

Heyo, sorry I'm on triage duty and our guidelines are to close proposals we don't immediately see as actionable / assignable and continue conversation while closed and reopen afterwards once it is; we discuss this as a team at a weekly triage meeting. Sorry I didn't notify you at the end of my post.
Just a few clarifications:

This additionally runs into query selection issues and shadow dom.

by this I meant that finding a node given a query selector may run into performance issues when it comes to traversing shadow roots (multiple calls to getRootNode vs the singular window.document most people are used to. Though I see that you clarified later that your proposal is to keep it within the shadow root.
Though there are 2 other points I'd like to make:
mwc-menu in its current form occasionally needs to be hoisted to body. In cases such as when inside a dialog or non-statically positioned element. See #832. This means that often the anchor is often not immediately query-selectable as their anchors are often in other shadow roots. This means that we will in one form or another need to keep the anchor property. And, if we keep the anchor property, I feel as if we have a sufficiently-declarative method for achieving for="..."'s behavior with LitElement and without adding more code to the menu component itself.
Secondly, the Polymer team tries to stick to the mediator method for component design style and again as this seems to be easily solvable by a mediating parent element.
Your CSS Query CE approach seems to be a great way to solve this without LitElement or starter javascript.

Sorry for long communication chain. for was not meant as full substitution of anchor, rather a complimentary initializer. In simple cases it is enough to use declarative for initializer, in other cases like you given or dynamic re-assignment the direct setting of node via anchor definitely beneficial.

I brought this proposal up to the team, and the decision was that the anchor property provides a sufficient API surface for what Menu needs to do as well as @query with LitElement

Also there is upcoming shadow dom-related work for the for and all of the a11y selectors coming up in the standards world and that we will be keeping a close eye on how that progresses.


Add logging for life-cycle changes

I find myself using the following pattern to make it easier to grep through logs to see if the script has been loaded:
@time_trigger
def run_on_startup_or_reload():
    log.info(f"Loading {__name__}")

It would be great if the "core" would do that on my behalf to avoid code duplication. I have a locally added info-level message under __init__.load_scripts, but I'm not sure if that's really the correct place to add such. Ideas/opinions?

Good idea - perhaps this debug message should be moved to the end of the function (ie, on success) and made an info message:
https://github.com/custom-components/pyscript/blob/666e3fcb42dbf3a233be74cb880fc9f45e3b3fcc/custom_components/pyscript/global_ctx.py#L269
Currently pyscript only has info messages for starting/stopping a Jupyter session.  While I don't like cluttering the logs, loading a new pyscript script or app seems like a worthy thing to appear in the log.


Add a pretty printer that returns information that is useful for the user

The information that is returned should be actionable for the user:

What family of models this sampler is compatible with / best used for;
The parameters and their signification. A brief description of their effect on the chain;
The adaptation schemes that can be used for the algorithm's parameters;
Literature reference;
Related samplers.

The pretty printer can use functools.singledispatch and the information can be dispatched right where the algorithms are implemented (rather than the kernel?). This will require careful work on the types beforehand.

Out of scope for v1.


Sort system usings first

Sort system usings first, rather than strict alphabetical.
See https://github.com/domaindrivendev/Swashbuckle.AspNetCore/pull/2768#issuecomment-2053936433.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.66%. Comparing base (9e77996) to head (65fa949).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2790   +/-   ##
=======================================
  Coverage   91.66%   91.66%
=======================================
  Files          91       91
  Lines        3010     3010
  Branches      517      517
=======================================
  Hits         2759     2759
  Misses        251      251

Flag
Coverage Δ

Linux
91.66% <ø> (ø)

Windows
?

macOS
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Improve UMP token handling

Refactors our Vuex store module for handling the Auth0 user
Distinguishes between being logged out of Auth0 vs. being logged in but having an Auth0 error
Makes it so we're only fetching new tokens if one is about to expire (as opposed to every 15 minutes)
Adds a conditional view to the "Confirm linked identity" route to account for someone who is logged into a different account than the one from which they initiated the email link (I came to realize this was a problem from this Sentry ticket)
Refactors the user portion of the Vuex module to account for some portal API changes per this PR

I kinda just clicked around the portal and that all WFM. I did hit a error when I tried to update info, but it kinda seems like that was just a weird network glitch. I worked fine after refreshing.


Regex muting not working on retweets

I'm glad that this program has regex mutes for tweets, but it doesn't seem to be working when people retweet a post with some of my muted words.

Hello.
What regex are you using?

And is there a maximum length of pattern?

case sensitive: yes
maximum of length: no

Could you add an option to make regexes case insensitive?

Inserting (?i) in the first will make regex case insensitive, but I will add the options for easy use.


Missing meta data

Dear Developer,
For readability and Search Engine Optimization (SEO) it would be great if you could do the followings:

[ ] Please provide more than 8 words in the "About" field

The description was added to "About".


Notebooks 2.0 // Backend // Deploy on Makefile

Implement and Setup deploy action on Makefile.

Hey @ederign, is this issue being worked on or I may start working on it?

Hey @KapilSareen not yet.
What we need here is a way to deploy the backend in a cluster, similar to what we have here for the controller:
https://github.com/kubeflow/notebooks/blob/notebooks-v2/workspaces/controller/Makefile#L137-L144
are you interested?

yes, you can assist it to me.. I'll start working on it.

@thesuperzapper can you please assign this to @KapilSareen

/assign @KapilSareen


fixup indentation

without  this, clang builds fail with error
AttributeError: 'NoneType' object has no attribute 'extend'
Changelog: (Feature | Fix | Bugfix): Describe here your pull request

[ ] Refer to the issue that supports this Pull Request.
[x] If the issue has missing info, explain the purpose/use case/pain/need that covers this Pull Request.
[x] I've read the Contributing guide.
[x] I've followed the PEP8 style guides for Python code.

current stack trace of jobs trying to build only linux clang configurations:
Traceback (most recent call last):
  File "build.py", line 8, in <module>
    builder = build_template_default.get_builder(build_policy="missing")
  File "/opt/hostedtoolcache/Python/3.7.4/x64/lib/python3.7/site-packages/bincrafters/build_template_default.py", line 23, in get_builder
    reference=reference)
  File "/opt/hostedtoolcache/Python/3.7.4/x64/lib/python3.7/site-packages/cpt/packager.py", line 456, in add_common_builds
    tmp = self.build_generator.get_builds(pure_c, shared_option_name, dll_with_static_runtime, reference)
  File "/opt/hostedtoolcache/Python/3.7.4/x64/lib/python3.7/site-packages/cpt/builds_generator.py", line 165, in get_builds
    builds.extend(get_linux_clang_builds(self._clang_versions, self._archs,
AttributeError: 'NoneType' object has no attribute 'extend'

https://dev.azure.com/bincrafters/packages/_build/results?buildId=872&view=logs&j=d1321064-f6c3-56b7-0172-6d994d01c836

Travis failed due incompatibility with Conan 1.21.0 (next release)


[TCGC] Change the responses and exceptions to be arrays

Fixes https://github.com/Azure/typespec-azure/issues/1453

All changed packages have been documented.

:white_check_mark: @azure-tools/typespec-azure-resource-manager
:white_check_mark: @azure-tools/typespec-client-generator-core

Show changes
@azure-tools/typespec-azure-resource-manager - feature ✏

x-ms-skip-url-encoding should be replaced with allowReserved

@azure-tools/typespec-client-generator-core - breaking ✏

The kind for unknown renamed from any to unknown.,> 2. The values property in SdkUnionType renamed to variantTypes.,> 3. The values property in SdkTupleType renamed to valueTypes.,> 4. The example types for parameter, response and SdkType has been renamed to XXXExampleValue to emphasize that they are values instead of the example itself.,> 5. The @format decorator is no longer able to change the type of the property.

@azure-tools/typespec-client-generator-core - fix ✏

Fix naming logic for anonymous model wrapped by HttpPart

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


Fe checkpoint failed: Failed to find key 25772638 in database 25770294

Steps to reproduce the behavior (Required)
Possible in this scenario: restarting the master node in case of high metadata write pressure
Expected behavior (Required)
Real behavior (Required)

StarRocks version (Required)

1.18.2

The databases in bdb are 25770294, 25772636, 25772642...

We can speculate that the database 25772636 is generated by transferring the master. Because there are only two cases to generate a new database: 1. Transfer master, 2. The number of logs in the database exceeds 50,000.
The max journal id in database 25770294 is 25772637

But the database name behind the 25770294 database is 25772636. There must be a problem calculating the new database name.
The newly database name is: latestDatabaseName + latestDatabaseCount.
There are two possible reasons for this problem: 1. database.count() is not accurate 2. two txns (25772636, 25772637) were not committed when the transfer master event was received, and they were committed after the new database was created.


[Django 3.0] provided an invalid language code in the LANGUAGES setti…

…ng: 'pt_BR'
What changes were proposed in this pull request?
from 'pt_BR' to 'pt-br'
How was this patch tested?
https://docs.djangoproject.com/en/3.0/topics/i18n/
https://github.com/django/django/blob/master/django/conf/global_settings.py
https://stackoverflow.com/questions/59156630/translation-e004-you-have-provided-a-value-for-the-language-code-setting-that-i

Another check: will it brake with Django 1.11?

Checked, not breaking, and also it passes the ci also


Create local copy of data to avoid repeat downloads from GitHub

While trying to verify changes with run.py I encountered high failure rates for downloading from GitHub. There are a large number of repeated downloads for the same run. Rather than downloading separately, download a copy of the public data once at the beginning of a run.

This implementation looks good, but should we consider a higher-level approach to this problem by wrapping the HTTP request in a cache? If we used Requests to fetch the files, we could choose to cache according to RFC or just for an arbitrary length of time.

@tsebens previous to this I was using a context manager variety of temp directory.I added back now that I got the rest settled. This will create at the start and delete once out of scope.
@davidstrauss I like the idea of httpcache, though I think read_csv is using urlib directly, not requests.

👍


Add cat command

what h

From: Cam K. @.>
Sent: Saturday, 11 June 2022, 01:12
To: CamK06/WinBot @.>
Cc: Frankie B. @.>; Author @.>
Subject: Re: [CamK06/WinBot] Add cat command (PR #51)
Merged #51https://github.com/CamK06/WinBot/pull/51 into main.
—
Reply to this email directly, view it on GitHubhttps://github.com/CamK06/WinBot/pull/51#event-6789306464, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH3WHBZQFX2VBRDF3F3YVNLVOPKWBANCNFSM5XTGZ6BQ.
You are receiving this because you authored the thread.Message ID: @.***>


Review react-virtualized

After couple round discussion, we will not to use anymore and stick to current infinite list.


Cookie with sameSite=None must be secure

This issue is imported from pivotal - Originaly created at Oct 28, 2019 by Okke Harsta
In Chrome we receive this warning: A cookie associated with a resource at http://connect.test2.surfconext.nl/ was set with SameSite=None but without Secure. A future release of Chrome will only deliver cookies marked SameSite=None if they are also marked Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5633521622188032.

It seems the auditors have missed this... (Bart Geesink - Nov 6, 2019)


Edit running time entry's start time

Every single day, I forget to start the tracker and remember about 10-30 minutes later, which means I have to open the app, to edit the start time of the currently running entry. Which is annoying, because the first load of the app is slow, because it's an SPA.
There is already the ability to edit the currently running entry, to change the project. I'm proposing to also allow edit the beginning of the time entry, the same way it can be edited in the web app.

I'd love to see this feature being implemented!


rhash: error while loading shared libraries: librhash.so.0: cannot open shared object file: No such file or directory

On a Centos 7
i tried to install rhash (i've already installed on 2 others servers this year).

clone the project
./configure --sysconfdir=/etc --exec-prefix=/usr --enable-lib-static
make install install-lib-so-link install-lib-shared

But when i do rhash, i get rhash: error while loading shared libraries: librhash.so.0: cannot open shared object file: No such file or directory
I also tried to do make install-headers but it said that no rules exists for target install-headers
Thanks for help

Try to fix it by running ldconfig as root,
also verify that the library is properly installed: ls -l /usr/lib/librhash.so.0.
The command to install headers is now make install-lib-headers.

I am running cmake in conda, may you know how to invoke it from conda env?


feat: Banner option in app.config.ts

Describe the feature
Possibility of having a banner at the top of the page on all pages (similar to Material for MkDocs or Fumadocs) with different styles, an icon prop, and an option for if it can be closed.
Additional information

[ ] Would you be willing to help implement this feature?

Noticed this was added, closing.

For the record, added in dfbc2433baae887cd7deeb7517e0a9f62450d081, released in v0.8.3
Usage guide: https://shadcn-docs-nuxt.vercel.app/api/configuration/banner


Text wrapping wrong in IE9 in when refreshed in non-100% zoom.

SVG has to be loaded at a 100% zoom in IE9 for the text wrapping to be properly placed. If you for example zoom out far in an IE9 window, then refresh the page, the text wrapping will not work properly.

I'm unable to duplicate this bug, can you post the code that's not working for you?

Here you go!
http://jsfiddle.net/unhztgf7/
And with that I just noticed another bug that applies in both Chrome and IE9. See how the text in the bottom line is wrong? It's repeating something from earlier rather than continuing as written. Should I post this as a separate issue?

I'm still not able to reproduce this issue.

Even the jsfiddle works for me.

Can you upload a screenshot of exactly what you're seeing, along with the full browser agent and any console messages/errors that may occur?

The repeating text error seems to be gone now...
Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
No errors in the console!
This bug isn't a huge deal, maybe it's not worth the effort.

I still haven't been able to duplicate this issue. Until I can, I'm de-prioritizing it.


Semantic PR and conventional commits

Hello there!
We all have diverse backgrounds, follow varying standards, and likely have differing opinions on managing this open-source project.
I suggest that we delegate those decisions so that we can spend more time developing "protobom." It would be best to adhere to well-accepted standards for commits, pull requests, and branch names.
I would like to suggest we do the following:

Follow conventional commits
Use either Github App or Github Action for semantic pull request
Use pre-commits hooks to ensure following those guidelines locally (before commit)
Use - as separators in branch names (fix-some-error)

looking forward to hearing your thoughts!

@manifestori, fine with me, as long as you can commit to tutoring those of us who haven't adhered to conventional commit conventions in the past :)

I don't like conventional commits much :( I find that it steals valuable characters from the commit title but if folks prefer to use them I can certainly play along. I would prefer fostering a culture of atomic changes and clear human-readable descriptions when needed. I'm curious about the branch naming, what's the motivation there?

It appears that you are correct about the limit of 72 characters (or 50 if following common standards) for commit names. However, I personally have not faced any issues with using longer commit names. In fact, in some projects, we have even included ticket numbers such as 'chore: do something [PRJ-000]'.
I fully support the idea of submitting atomic changes and providing clear, easy-to-understand descriptions, but that's very subjective when it comes down to formatting :)
Another benefit of utilizing conventional commits is that it can be combined with a .goreleaser configuration, for example:
changelog:
  use: github
  groups:
    - title: Features
      regexp: "^.*feat[(\\w)]*:+.*$"
      order: 0
    - title: 'Bug fixes'
      regexp: "^.*fix[(\\w)]*:+.*$"
      order: 1
    - title: 'Documentation'
      regexp: "^.*docs[(\\w)]*:+.*$"
      order: 2
    - title: Others
      order: 999

With this feature, change logs in Github Releases will be automatically ordered, sorted, and divided to the change, saving tons on manual work.
Regarding branch name, I'm fine with whatever, but we just need to figure out a style we want to follow, also, Github default squash commit tittle, follows the branch name and not the "first commit" or "pull request title", but we can change this.
A clean branch list is just better than a mixed branch list imho 🧹
chore-ori-test
feat/my_branch
feat/manifestori-add-integeration-test
feat_add_integration_test

VS
chore-ori-test
feat-my-branch
feat-add-ingration-test

(not sure we need to attach branch owner to name, but its a convention in some OSS project)


Rename insert, remove label argument

There's a couple of things I don't like about DataFrame.insert:

the name is less descriptive than the rest of the API
the argument label isn't really needed, because we have both Column.name and Column.rename

thanks all


Equation box

Equation box using vue katex: see https://www.npmjs.com/package/vue-katex-auto-render?activeTab=readme and github.com/lucpotage/vue-katex
Used prop not slot for equation, since slots break the rendering of the equations.
The equation is demonstrated in the description pane component as well as the equation box component.

Hiya,
Equation box looks good, the stylising works well. I notice that the equation prop doesn't seem to be responsive to changes in the prop, see image below.

Also I notice that you are importing the katex stuff (and Vue) in the component file, you should only need to do that once in the /src/main.js file for everything to work I believe. note that in main.js you should register the vue.directive line outside of the for loop else it will get called multiple times which might cause an error.

Hi, thanks for the feedback.
I have now cleaned up the imports and made the box responsive to changes in the prop.


Long options with =

Long options with values after = does not seems to be working:
$ go run main.go --env=dev
Error: Invalid trailing arguments: [--env=dev]
Usage: main [global options]

Global options:
        -e, --env     Application environment, defines config section (default: prod)
        -r, --rebuild Rebuild index only, do not start web server
        -h, --help    Show this help

exit status 1

W/out equal sign works fine.
$ go run main.go --env dev
[LOG] 2014/12/23 - 04:11:39 | Loading config with env set to dev

Sorry for taking so lang to answer, but you know... holidays ;)
This is working as intended, it even says so in the documentation:

Short flags can be combined (e.g. -nfv). Long flags take their value after a separating space. The equals notation (--long-flag=value) is NOT supported right now.

I am still unsure if I want to support both notations. If you feel you can make a good case for it, please post it here so I can consider it for v3 which I'm (theoretically) working on :D


Backend - Update Event Model to include Yes/No for Users Attending Question WAIT FOR #124

#124

#124 now complete
below is console logs of the updated fields and the outputs. Both are just booleans


Enable http caching in dev environments by default

I've often spent a lot of time trying to figure out why my cache headers haven't changed while testing after implementing http caching as per the docs. This is because there's some config in framework to disable this behaviour in dev mode.
Looks like it was disabled in dev intentionally as part of https://github.com/silverstripe/silverstripe-framework/pull/8086. Would people be happy for this to be removed? I'm sure there was a reason it was added but for me personally it's been more of a hindrance than a helper. If there are valid reasons to keep it in then I'd be happy to raise a PR to the docs to clarify the default behaviour on dev mode.

That config isn't mentioned anyway and its a really messy way to test something in dev (temporary yml file). This makes sense as an environment variable rather than config so it can be switched on and off easily.

I'd be inclined to say "yes" - caching is a touchy thing to implement and it would make sense for it to be easy to test in dev mode, and not behave differently from test/live so you can easily debug issues with it

I'm inclined to update the docs to mention "caching is disabled in dev". I'd hazard a guess that the amount of devs confused by "why is my stuff not updating" is greater than the amount of devs diagnosing HTTP caching issues in dev rather than test mode.

Closed by #8819 (docs update)


RP-17 Add file hadler for loggers

Write all the logs to the file in addition to the console.

Fixed by https://github.com/zwieback/relef-parser/pull/35


I know I am probably just missing something stupid, I have an sprig form and a sprig button since using another form to delete just deletes all other entries since all forms are submitted. So I made a sprig button but I cant seem to get it to delete the entry and throws 404 errors in console.log?  Am I missing something stupid?
<button  					sprig  					s-method="post"  					s-action="entries/delete-entry"  					s-val:entryId="{{ r.id }}"  					s-val:sectionId="14" 					class="btn btn-primary delete ml-1" 					s-replace="#client-listed-recommendations" 				> 					<i class="fas fa-trash-alt"></i> 				</button>

Thank you for becoming a Github sponsor 🎉
Try reading the response in the network tab of the browser console to see what is going wrong. Having devMode enabled should give you a detailed error message.

Error: Request missing required body param
Which makes me think the params are not correct. I took another look at the button in the inspector and saw this.

I noticed s-val:entryid="2225" and  s-val:sectionid="14" are changed to all lower case I know this breaks in the entry form if I make that all lower case. Is it possible it could be breaking this as well?

Ah yes, they should be in kebab-case:
s-val:entry-id="{{ r.id }}" s-val:section-id="14"

See https://putyourlightson.com/plugins/sprig#s-val

Cuh-ray-zee.   Thanks so much I promise I read that paragraph 15 times.


Add Unit type

Reason
Facilitate other generics to understand a zero-tuple struct
Use Cases
Returning Option<Unit> to indicate presence of a value

Consider predefining static readonly Option<Unit> Some and None

Odd issue when adding public static readonly Option<Unit> Some and public static Option<Unit> None and running unit tests:
Message: System.TypeLoadException : Could not load type 'Rlx.Unit' from assembly 'Rlx, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.


Meteostat Integration

Initial branch for adding support for Meteostat.
Currently includes:

[x] new models for WeatherStation and WeatherObservation (ultimately to replace the dark sky stuff)
[x] new data loader, using the MeteoStat interface in the analytics package
[x] admin interface to create and manage weather stations
[x] ability for admin to download CSV files of data for each weather station

Still to do around this bit of the code:

[x] associate weather stations with schools
[x] association of weather stations with school groups and onboarding?
[x] decide when to automatically add stations and associate them with schools
[x] whether to allow lat/long to be changed, or prefer switching to new station
[x] switching between Dark Sky and MeteoStat if a schools is associate with an active Weather Station, so right readings are passed to analytics
[x] decide how to handle/generalise current Area stuff (replace in favour of stations?)
[x] updates to EB config to add new cron job for Meteostat loading, as well as env variables to drive it

Separately need to decide how to handle Dark Sky migration, historical loading, and any improvements to the MeteoStat API client.

@jhigman I think this is ready for review.
The functionality thats not currently included is:

a crontab entry to run the loading of historical data from Meteostat. That could be added and deployed separately
attribution of data sources, but this isn't Meteostat specific, so suggest we do as a separate branch
any changes to the way that the client library is called, pending any refactoring. But again this could be done separately.

Deploying these latest updates to test won't trigger use of Meteostat data in the analytics until the feature flag is set to activate it.
That means I also think its safe, pending any feedback from review, to merge down and release to both test and live. Without any stations configured, and without the feature flag, none of the new code should run.

@jhigman I think this is ready for review.
The functionality thats not currently included is:

a crontab entry to run the loading of historical data from Meteostat. That could be added and deployed separately
attribution of data sources, but this isn't Meteostat specific, so suggest we do as a separate branch
any changes to the way that the client library is called, pending any refactoring. But again this could be done separately.

Deploying these latest updates to test won't trigger use of Meteostat data in the analytics until the feature flag is set to activate it.
That means I also think its safe, pending any feedback from review, to merge down and release to both test and live. Without any stations configured, and without the feature flag, none of the new code should run.

👍  all looks good

👍  all looks good

I need to make a change to allow the Dark Sky Areas to be deselected, so will do that before merging down.

I need to make a change to allow the Dark Sky Areas to be deselected, so will do that before merging down.


SQL to SEQUEL

Coverage increased (+0.0%) to 99.24% when pulling 3f2bc11a2ddec617911d344497ee804774e8efee on mokhan:sequel into 489cc730e166455ab4b6e7acc9af9424dac53b17 on stronglifters:master.

Coverage remained the same at 99.24% when pulling b7645ba226605615e20e22dab8925602ad9f271e on mokhan:sequel into 489cc730e166455ab4b6e7acc9af9424dac53b17 on stronglifters:master.

Coverage decreased (-0.0%) to 99.24% when pulling 62ae59dc09dcac43ef69491998da7cd98d74385a on mokhan:sequel into 489cc730e166455ab4b6e7acc9af9424dac53b17 on stronglifters:master.