Picodes10

Pull Request for PyVerse 💡
Issue Title : Restaurant Landing Page

Info about the related issue (Aim of the project) : The goal of the project is developing a functional landing page.
Name: Sushree Biswal
GitHub ID: Picodes10
Email ID<EMAIL_ADDRESS>**Idenitfy yourself: GSSOC Extended - 2024

Closes: #61
Describe the add-ons or changes you've made 📃
I have added a frontend project to the "web development" section of the website.
Type of change ☑
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested? ⚙

Tested the project in my local environment.
To run the project use command "npm install" to install node modules, and then use "npm start" to view it using local host.

Checklist: ☑

[X] My code follows the guidelines of this project.
[X] I have performed a self-review of my own code.
[X] I have commented my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[X] I have added things that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published in downstream modules.

Hlo @UTSAVS26, I am closing this PR and will raise a new one for the same issue.

Hlo @UTSAVS26, I am closing this PR and will raise a new one for the same issue.

Yeah sure


Checkbox question not displayed properly

If a plan includes checkbox question, the options are not displayed correctly. For instance, create a plan based on NERC Template.

I'm not sure how they were mis-displaying earlier, but having just created a NERC plan they're displaying fine now. Closing out


add quic + http/3 fuzz test

This PR adds a fuzzer targeting HTTP/3 on top of QUIC.

/retest

/retest

@robertfemmer Are you waiting for another round of review, or do you still have changes to make?
/wait

Waiting for review

/retest

/retest


No volume in Chrome for youtube player

Current Behavior
I've got a video component in my react application, I'm using Chrome 76. I'm not autoplaying the video. Looks like a standard youtube embed. It is not muted. But, if I click to play, there's no sound. However, in Firefox, the sound is heard fine.
Here's the code for my component.
import React from 'react';
import ReactPlayer from 'react-player/lib/players/YouTube';

import { Jacket } from './moduleVideoStyles';

export default class ModuleVideoPlayer extends React.Component {
    render() {
        return (
            <>
                <Jacket>
                    <ReactPlayer
                        url={this.props.source}
                        width="100%"
                        height="100%"
                        config={{
                            youtube: {
                                playerVars: {
                                    volume: 1,
                                    muted: false,
                                    autoPlay: 0,
                                    playinline: 1,
                                    modestbranding: 1,
                                }
                            },
                        }}
                    />
                </Jacket>
            </>
        )
    }
}

I previously had this instead...
<ReactPlayer
     url={this.props.source}
     width="100%"
     height="100%"
     autoplay={false}
     controls
     playsinline
     volume={1}
/>

But this does the same thing. Tried searching for hours for solutions and can't find anything. Any help would be appreciated.

This seems very strange.. Does the same thing happen on the demo page?

@CookPete Demo page works perfectly fine in Chrome, but my local version has just has no sound output. However, a friend of mine said it worked fine for him (when he viewed through vsliveshare).

Sounds like something weird going on locally with your machine/specific setup?

For posterity: check the tab in Chrome and see if it has a muted icon as you could have muted the site by mistake like I did just now.


bcmap argnum

Add an option to select which argument to broadcast to in bcmap
import sepes as sp
def func(x, y):
    return x + y
# broadcast x to y structure
# this effectively converts 1 -> [1,1,1]
sp.bcmap(func, broadcast_to="y")(x=1, y=[2,3,4]) # [3,4,5]
# broadcast x to y structure (argnum=1)
sp.bcmap(func, broadcast_to=1)(1, [2,3,4]) # [3,4,5]

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

Comparison is base (5ac33c3) 94.31% compared to head (e5c9251) 79.33%.

Additional details and impacted files
@@             Coverage Diff             @@
##             next      #13       +/-   ##
===========================================
- Coverage   94.31%   79.33%   -14.99%
===========================================
  Files          13       13
  Lines        2322     2332       +10
===========================================
- Hits         2190     1850      -340
- Misses        132      482      +350

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


Use image information programmatically from Kubernetes test.util.image package

Describe the solution you'd like
Currently, the procedure to prepare a release for a new Kubernetes version involves copying/changing code from upstream K/K test package into the image package for Sonobuoy.  That step is documented in the release and is known to be time consuming and error prone.  This practice may have evolved organically as Sonobuoy has code based has changed and the upstream K/K test packages have diverged over the years.
This issue is to propose a way to programmatically integrate with the Kubernetes/Kubernetes upstream test utility package to pull the registry and the image information dynamically instead of the manual copy/paste approach currently done. This could be done as follows:

Import package k8s.io/kubernetes/test/utils/image
In function NewRegistryList use an initialize an instance of *image.RegistryList
Function getImageConfigs() here would call k/k package function that return a value of type map[int]image.Configs here
In this section of the code, imageConfig.GetFullyQualifiedImageName would be replaced with the equivalent method on image.Config.GetE2EImage found here
In this section of the code, similar adjustment would be made as listed in the previous bullet point.
This section of the code would use type image.Registry to setup and return default image registries

Implications
This proposal would imply the followings, if adopted:

Reduce time to release: the code would be in lock-step with upstream K/K tests manifest automatically
This would pin Sonobuoy to a kubernetes version
Instead of two-minor-version spread, each release of Sonobuoy targets a single family of minor releases (i.e. 1.18.0 - 1.18.99) only.
E2e of earlier versions of K8s would require the use of exact Sonobuoy version

This is awesome research! I think it would be great to remove that manual step from the release process. I'm concerned about reducing the supported versions and having to pin the Sonobuoy version to the K8s version that you want to test. I think it could be an annoying experience for people wanting to test against multiple cluster versions - especially as this change would only be in place to improve the air-gapped use case. It would also mean that any new features/bug fixes would have to be backported to older versions so that people running Sonobuoy against older clusters can still take advantage of them.
What do you think about removing all of this image handling from Sonobuoy altogether and instead creating a separate utility that is just for prepping an airgapped environment for e2e/conformance testing? That way it could have pinned versions that line up with the cluster that is being tested and it would help remove some of the (painful) coupling that exists between Sonobuoy and upstream K/K.

@zubron thanks for the awesome feedback. I failed to consider all implications you mentioned above in your comment, mainly the ability to run Sonobuoy against multiple cluster versions.  That said, I think starting with then next release of Sonobuoy, the tool should rigidly apply the two-version regression limit.  For instance, Sonobuoy 0.19.0 should only back support K8s 1.17, and 1.18.
As you alluded to, the portion of the code that requires this sync, during release, is for the support of airgap.  I wholeheartedly think that portion should be extracted as a separate tool.  This would remove the need to carry that information with each release of Kubernetes.

This can be closed as of v0.20, a different approach was taken.


Enable "branch must be update to date before merging"

We just had a semantic conflict between https://github.com/firezone/firezone/pull/1610 and https://github.com/firezone/firezone/pull/1613 that results in a broken state on the cloud branch.
Can we enable the merge requirement mentioned in the title? That would have surfaced this in one of the two PRs.

Sure. Looks like I need to require status checks to enable the feature (did GH change this recently? I dont recall this being the case before)

That should hopefully take care of it.

I believe this is completed -- feel free to reopen if it still needs addressing


Documentation/update stacked services documentation

Update stacked services documentation to include registering locator always as future

LGTM 🔥


IdentifiedReference invoking Lifecycle Hooks

Detected within the same example/setup as #2364, except if you expand the BaseMikro like so:
@Entity({ tableName: 'base', discriminatorColumn: 'type', abstract: true })
export default abstract class BaseMikro {
  @ManyToOne(() => BaseMikro, { fieldName: 'parentId', wrappedReference: true })
  parent: IdentifiedReference<ActivityMikro<any>>;

  @OnInit()
  test() {
   throw new Error('NOOOO!');
  }
}

the test method is invoked, but it is a "partial" object (BaseMikro, not the discriminated class), with just the primary key available, i would expect the lifecycle hooks to only happen on hydrated objects?

Yes, that is how it works, the onInit hook might be executed twice, once when the reference is created, once when it gets hydrated. I believe it should fire just once if you load the relation via joined strategy in the same query, but with select-in strategy the parent is loaded separately and that is where the first event might be fired on the reference.
You can distinguish between those via wrap(this).isInitialized() from inside the hook.


feat: add lighthouse to ci

:tada: This PR is included in version 1.27.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Bug] error message showing vue3.2.45

vue-datepicker-next:1.0.2
Vue version:3.2.45
Browser: chrome
Steps to reproduce
Any time show the date picker, the browser will show the error message.

i had the same issue! DOes any body know what is this?

@Skivs29
Can you help me reproduce？
https://codesandbox.io/s/busy-babycat-v462gi?file=/src/App.vue

This bug is very very wired. I have another lib got a similar problem. It is a little different warning message, but the same thing is it is good locally but not good on publish. It super confused me, I guess the problem is the relative Vue version. Lib depends on one version, and the project depends on another version. Not very sure. Let me know if anyone got some info. Thanks, guys.
I am happy to do any test. Just let me know.

Also I found this in vue-core.js:  https://github.com/vuejs/core/issues/4260 , is possible we can move the 'vue' from "dependencies" to "devDependencies":

Hi @Skivs29  try this way: https://github.com/vuejs/vue-cli/issues/4271 , if it is not work let me know. Thanks.


Add lower bound and upper bound similar to c++ in Java.

Add lower bound and upper bound in Java. Comment the code properly.

I'd like to work on this! Is there a specific structure type you'd like me to use in the example?

Yes use any any integer array to find lower bound and upper bound of any integer that you like in the arraylist. And remember to use ArrayList.


extend noop-example status timeout

*** BUILD #53 ***
Test Name: test_node_workflows_post
Error Details: valid != succeeded
-------------------- >> begin captured logging << --------------------
urllib3.connectionpool: INFO: Resetting dropped connection: localhost
tests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 0 sec(s)
tests.workflows_tests: INFO: Curent status valid
--------------------- >> end captured logging << ---------------------
Stack Trace:   File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/usr/local/lib/python2.7/dist-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/usr/local/lib/python2.7/dist-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/usr/local/lib/python2.7/dist-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/var/lib/jenkins/jobs/RackHD/workspace/build/test/tests/workflows_tests.py", line 135, in test_node_workflows_post
    assert_equal(status,"succeeded")
  File "/usr/local/lib/python2.7/dist-packages/proboscis/asserts.py", line 55, in assert_equal
    raise ASSERTION_ERROR(message)
'valid != succeeded\n-------------------- >> begin captured logging << --------------------\nurllib3.connectionpool: INFO: Resetting dropped connection: localhost\ntests.workflows_tests: INFO: Attempting to check the status of the posted workflow after 0 sec(s)\ntests.workflows_tests: INFO: Curent status valid\n--------------------- >> end captured logging << ---------------------'

hey @jlongever, did you change whitespace or something on every line? Diff is terrible to read - reads like you replaced the whole thing, although visually scanning the lines look nearly identical.
(BTW: the failure result annotation as a comment is really cool - looking forward to learning how you arranged that!)

bah,  yeah i did a 'fromdos' on the file... i'm really just using this PR to resolve a workflow timing issue introduced with a new functional test.  no plans to merge it... actually i can reproduce the error locally so i'll just close it.


Simple error prevents import of ALAC files into beets

I just noticed this when trying to import a few ALAC files into my new beets library:
user configuration: /path/to/.config/beets/config.yaml
data directory: /path/to/.config/beets
Sending event: pluginload
library database: /path/to/.config/beets/library.db
library directory: /path/to/Music
Sending event: library_opened
Traceback (most recent call last):
  File "/path/to/env/python-beets/bin/beet", line 9, in <module>
	load_entry_point('beets==1.3.9', 'console_scripts', 'beet')()
  File "/path/to/env/python-beets/local/lib/python2.7/site-packages/beets/ui/__init__.py", line 935, in main
	_raw_main(args)
  File "/path/to/env/python-beets/local/lib/python2.7/site-packages/beets/ui/__init__.py", line 925, in _raw_main
	subcommand.func(lib, suboptions, subargs)
  File "/path/to/env/python-beets/local/lib/python2.7/site-packages/beets/ui/commands.py", line 872, in import_func
	import_files(lib, paths, query)
  File "/path/to/env/python-beets/local/lib/python2.7/site-packages/beets/ui/commands.py", line 844, in import_files
	session.run()
  File "/path/to/env/python-beets/local/lib/python2.7/site-packages/beets/importer.py", line 299, in run
	pl.run_parallel(QUEUE_SIZE)
  File "/path/to/env/python-beets/local/lib/python2.7/site-packages/beets/util/pipeline.py", line 249, in run
	msg = self.coro.next()
  File "/path/to/env/python-beets/local/lib/python2.7/site-packages/beets/importer.py", line 1070, in read_tasks
	task = task_factory.album([toppath], dir=toppath)
  File "/path/to/env/python-beets/local/lib/python2.7/site-packages/beets/importer.py", line 997, in album
	items = map(self.read_item, paths)
  File "/path/to/env/python-beets/local/lib/python2.7/site-packages/beets/importer.py", line 1015, in read_item
	return library.Item.from_path(path)
  File "/path/to/env/python-beets/local/lib/python2.7/site-packages/beets/library.py", line 391, in from_path
	i.read(path)
  File "/path/to/env/python-beets/local/lib/python2.7/site-packages/beets/library.py", line 443, in read
	mediafile = MediaFile(syspath(read_path))
  File "/path/to/env/python-beets/local/lib/python2.7/site-packages/beets/mediafile.py", line 1344, in __init__
	if self.mgfile.codec and self.mgfile.codec.startswith('alac'):
AttributeError: 'MP4' object has no attribute 'codec'

The fix is trivial, line 1344 in mediafile.py:
            if self.mgfile.info.codec and self.mgfile.info.codec.startswith('alac'):

Original state:
            if self.mgfile.codec and self.mgfile.codec.startswith('alac'):

This allows import of ALAC, iTunes bought AAC (256 kbit) and custom encoded AAC (varying kbit), but this is only after some happy testing with my 'fix'.

I like the sound of this.

Thank you! Please see #1117.

Not sure how I missed this other issue, I thought I had looked through the list. Sorry for this issue :)

welp. there's a few closed copies of this exact issue..and I hate to rain on anyones parade. But I still havn't been able to get ALAC files thru (several of the last few) source builds of beets.
Not sure if I should open the issue back up, so hopefully someone'll see this and weigh in on what they're experiencing.

Are you seeing the same error as in #1117 on the latest source version of beets? If so, please comment there. And if it's a different error, please do open a new issue.

**and of course I have been collecting all the error logs & and anything else that I'll upload if need be


event.ctrlKey

Supporting event.ctrlKey would be great

Available via MDN: https://caniuse.com/?search=ctrlKey


HDMI2USB target is broken on the Opsis

See https://travis-ci.org/timvideos/HDMI2USB-misoc-firmware/jobs/80203042
Release 14.7 - ngdbuild P.20131013 (lin64)
Copyright (c) 1995-2013 Xilinx, Inc.  All rights reserved.

Command Line:
/home/travis/build/timvideos/HDMI2USB-misoc-firmware/build/Xilinx/opt/Xilinx/14.
7/ISE_DS/ISE/bin/lin64/unwrapped/ngdbuild -uc
opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf opsis_hdmi2usb-hdmi2usbsoc-opsis.ngc
opsis_hdmi2usb-hdmi2usbsoc-opsis.ngd

Reading NGO file
"/home/travis/build/timvideos/HDMI2USB-misoc-firmware/build/misoc/build/opsis_hd
mi2usb-hdmi2usbsoc-opsis.ngc" ...
Gathering constraint information from source properties...
Done.

Annotating constraints to design from ucf file
"opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf" ...
WARNING:NgdBuild - The value of SIM_DEVICE on instance 'PLL_ADV_1' of type
   PLL_ADV has been changed from 'VIRTEX5' to 'SPARTAN6' to correct
   post-ngdbuild and timing simulation for this primitive.  In order for
   functional simulation to be correct, the value of SIM_DEVICE should be
   changed in this same manner in the source netlist or constraint file.
WARNING:NgdBuild - The value of SIM_DEVICE on instance 'PLL_ADV_2' of type
   PLL_ADV has been changed from 'VIRTEX5' to 'SPARTAN6' to correct
   post-ngdbuild and timing simulation for this primitive.  In order for
   functional simulation to be correct, the value of SIM_DEVICE should be
   changed in this same manner in the source netlist or constraint file.
WARNING:NgdBuild - The value of SIM_DEVICE on instance 'PLL_ADV_3' of type
   PLL_ADV has been changed from 'VIRTEX5' to 'SPARTAN6' to correct
   post-ngdbuild and timing simulation for this primitive.  In order for
   functional simulation to be correct, the value of SIM_DEVICE should be
   changed in this same manner in the source netlist or constraint file.
Resolving constraint associations...
Checking Constraint Associations...
WARNING:ConstraintSystem - TNM : GRPsys_clk was distributed to a DCM but new TNM
   constraints were not derived. This TNM is used in the following user groups
   or specifications:
   <TIMESPEC "TSise_sucks7" = FROM "GRPpix0_clk" TO "GRPsys_clk" TIG;>
   [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(145)]
   <TIMESPEC "TSise_sucks8" = FROM "GRPsys_clk" TO "GRPpix0_clk" TIG;>
   [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(146)]
   <TIMESPEC "TSise_sucks9" = FROM "GRPpix1_clk" TO "GRPsys_clk" TIG;>
   [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(147)]
   <TIMESPEC "TSise_sucks10" = FROM "GRPsys_clk" TO "GRPpix1_clk" TIG;>
   [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(148)]
   <TIMESPEC "TSise_sucks11" = FROM "GRPusb_clk" TO "GRPsys_clk" TIG;>
   [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(153)]
   <TIMESPEC "TSise_sucks12" = FROM "GRPsys_clk" TO "GRPusb_clk" TIG;>
   [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(154)]

INFO:ConstraintSystem:178 - TNM 'GRPbase50_clk', used in period specification
   'TSbase50_clk', was traced into DCM_CLKGEN instance DCM_CLKGEN_1. The
   following new TNM groups and period specifications were generated at the
   DCM_CLKGEN output(s):
   CLKFX: <TIMESPEC TS_hdmi_out0_clocking_clk_pix_unbuffered = PERIOD
   "hdmi_out0_clocking_clk_pix_unbuffered" TSbase50_clk HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPclk100', used in period specification
   'TSclk100', was traced into BUFIO2 instance BUFIO2. The following new TNM
   groups and period specifications were generated at the BUFIO2 output(s):
   DIVCLK: <TIMESPEC TS_hdmi2usbsoc_clk100b = PERIOD "hdmi2usbsoc_clk100b"
   TSclk100 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPclk100', used in period specification
   'TSclk100', was traced into DCM_CLKGEN instance DCM_CLKGEN. The following new
   TNM groups and period specifications were generated at the DCM_CLKGEN
   output(s):
   CLKFX: <TIMESPEC TS_base50_clk = PERIOD "base50_clk" TSclk100 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPrecord0_hdmi_in_clk_p', used in period
   specification 'TSrecord0_hdmi_in_clk_p', was traced into PLL_ADV instance
   PLL_ADV_1. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s):
   CLKOUT1: <TIMESPEC TS_hdmi_in0_pll_clk1 = PERIOD "hdmi_in0_pll_clk1"
   TSrecord0_hdmi_in_clk_p / 2 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPrecord0_hdmi_in_clk_p', used in period
   specification 'TSrecord0_hdmi_in_clk_p', was traced into PLL_ADV instance
   PLL_ADV_1. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s):
   CLKOUT0: <TIMESPEC TS_hdmi_in0_pll_clk0 = PERIOD "hdmi_in0_pll_clk0"
   TSrecord0_hdmi_in_clk_p / 10 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPrecord0_hdmi_in_clk_p', used in period
   specification 'TSrecord0_hdmi_in_clk_p', was traced into PLL_ADV instance
   PLL_ADV_1. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s):
   CLKOUT2: <TIMESPEC TS_hdmi_in0_pll_clk2 = PERIOD "hdmi_in0_pll_clk2"
   TSrecord0_hdmi_in_clk_p HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPrecord1_hdmi_in_clk_p', used in period
   specification 'TSrecord1_hdmi_in_clk_p', was traced into PLL_ADV instance
   PLL_ADV_2. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s):
   CLKOUT1: <TIMESPEC TS_hdmi_in1_pll_clk1 = PERIOD "hdmi_in1_pll_clk1"
   TSrecord1_hdmi_in_clk_p / 2 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPrecord1_hdmi_in_clk_p', used in period
   specification 'TSrecord1_hdmi_in_clk_p', was traced into PLL_ADV instance
   PLL_ADV_2. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s):
   CLKOUT0: <TIMESPEC TS_hdmi_in1_pll_clk0 = PERIOD "hdmi_in1_pll_clk0"
   TSrecord1_hdmi_in_clk_p / 10 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'GRPrecord1_hdmi_in_clk_p', used in period
   specification 'TSrecord1_hdmi_in_clk_p', was traced into PLL_ADV instance
   PLL_ADV_2. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s):
   CLKOUT2: <TIMESPEC TS_hdmi_in1_pll_clk2 = PERIOD "hdmi_in1_pll_clk2"
   TSrecord1_hdmi_in_clk_p HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi_out0_clocking_clk_pix_unbuffered', used in
   period specification 'TS_hdmi_out0_clocking_clk_pix_unbuffered', was traced
   into PLL_ADV instance PLL_ADV_3. The following new TNM groups and period
   specifications were generated at the PLL_ADV output(s):
   CLKOUT1: <TIMESPEC TS_hdmi_out0_clocking_pll_clk1 = PERIOD
   "hdmi_out0_clocking_pll_clk1" TS_hdmi_out0_clocking_clk_pix_unbuffered / 2
   HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi_out0_clocking_clk_pix_unbuffered', used in
   period specification 'TS_hdmi_out0_clocking_clk_pix_unbuffered', was traced
   into PLL_ADV instance PLL_ADV_3. The following new TNM groups and period
   specifications were generated at the PLL_ADV output(s):
   CLKOUT0: <TIMESPEC TS_hdmi_out0_clocking_pll_clk0 = PERIOD
   "hdmi_out0_clocking_pll_clk0" TS_hdmi_out0_clocking_clk_pix_unbuffered / 10
   HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi_out0_clocking_clk_pix_unbuffered', used in
   period specification 'TS_hdmi_out0_clocking_clk_pix_unbuffered', was traced
   into PLL_ADV instance PLL_ADV_3. The following new TNM groups and period
   specifications were generated at the PLL_ADV output(s):
   CLKOUT2: <TIMESPEC TS_hdmi_out0_clocking_pll_clk2 = PERIOD
   "hdmi_out0_clocking_pll_clk2" TS_hdmi_out0_clocking_clk_pix_unbuffered HIGH
   50%>

INFO:ConstraintSystem:178 - TNM 'hdmi2usbsoc_clk100b', used in period
   specification 'TS_hdmi2usbsoc_clk100b', was traced into PLL_ADV instance
   PLL_ADV. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s):
   CLKOUT3: <TIMESPEC TS_hdmi2usbsoc_pll_3_ = PERIOD "hdmi2usbsoc_pll_3_"
   TS_hdmi2usbsoc_clk100b / 2 PHASE 2.916666667 ns HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi2usbsoc_clk100b', used in period
   specification 'TS_hdmi2usbsoc_clk100b', was traced into PLL_ADV instance
   PLL_ADV. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s):
   CLKOUT5: <TIMESPEC TS_hdmi2usbsoc_pll_5_ = PERIOD "hdmi2usbsoc_pll_5_"
   TS_hdmi2usbsoc_clk100b / 0.5 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi2usbsoc_clk100b', used in period
   specification 'TS_hdmi2usbsoc_clk100b', was traced into PLL_ADV instance
   PLL_ADV. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s):
   CLKOUT0: <TIMESPEC TS_hdmi2usbsoc_pll_0_ = PERIOD "hdmi2usbsoc_pll_0_"
   TS_hdmi2usbsoc_clk100b / 4 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi2usbsoc_clk100b', used in period
   specification 'TS_hdmi2usbsoc_clk100b', was traced into PLL_ADV instance
   PLL_ADV. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s):
   CLKOUT4: <TIMESPEC TS_hdmi2usbsoc_pll_4_ = PERIOD "hdmi2usbsoc_pll_4_"
   TS_hdmi2usbsoc_clk100b HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi2usbsoc_clk100b', used in period
   specification 'TS_hdmi2usbsoc_clk100b', was traced into PLL_ADV instance
   PLL_ADV. The following new TNM groups and period specifications were
   generated at the PLL_ADV output(s):
   CLKOUT2: <TIMESPEC TS_hdmi2usbsoc_pll_2_ = PERIOD "hdmi2usbsoc_pll_2_"
   TS_hdmi2usbsoc_clk100b / 2 PHASE 3.194444444 ns HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'base50_clk', used in period specification
   'TS_base50_clk', was traced into DCM_CLKGEN instance DCM_CLKGEN_1. The
   following new TNM groups and period specifications were generated at the
   DCM_CLKGEN output(s):
   CLKFX: <TIMESPEC TS_hdmi_out0_clocking_clk_pix_unbuffered_0 = PERIOD
   "hdmi_out0_clocking_clk_pix_unbuffered_0" TS_base50_clk HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi_out0_clocking_clk_pix_unbuffered_0', used
   in period specification 'TS_hdmi_out0_clocking_clk_pix_unbuffered_0', was
   traced into PLL_ADV instance PLL_ADV_3. The following new TNM groups and
   period specifications were generated at the PLL_ADV output(s):
   CLKOUT1: <TIMESPEC TS_hdmi_out0_clocking_pll_clk1_0 = PERIOD
   "hdmi_out0_clocking_pll_clk1_0" TS_hdmi_out0_clocking_clk_pix_unbuffered_0 /
   2 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi_out0_clocking_clk_pix_unbuffered_0', used
   in period specification 'TS_hdmi_out0_clocking_clk_pix_unbuffered_0', was
   traced into PLL_ADV instance PLL_ADV_3. The following new TNM groups and
   period specifications were generated at the PLL_ADV output(s):
   CLKOUT0: <TIMESPEC TS_hdmi_out0_clocking_pll_clk0_0 = PERIOD
   "hdmi_out0_clocking_pll_clk0_0" TS_hdmi_out0_clocking_clk_pix_unbuffered_0 /
   10 HIGH 50%>

INFO:ConstraintSystem:178 - TNM 'hdmi_out0_clocking_clk_pix_unbuffered_0', used
   in period specification 'TS_hdmi_out0_clocking_clk_pix_unbuffered_0', was
   traced into PLL_ADV instance PLL_ADV_3. The following new TNM groups and
   period specifications were generated at the PLL_ADV output(s):
   CLKOUT2: <TIMESPEC TS_hdmi_out0_clocking_pll_clk2_0 = PERIOD
   "hdmi_out0_clocking_pll_clk2_0" TS_hdmi_out0_clocking_clk_pix_unbuffered_0
   HIGH 50%>

Done...

INFO:NgdBuild:1222 - Setting CLKIN1_PERIOD attribute associated with PLL
   instance PLL_ADV_1 to 12.000000 ns based on the period specification
   (<TIMESPEC "TSrecord0_hdmi_in_clk_p" = PERIOD "GRPrecord0_hdmi_in_clk_p" 12
   ns HIGH 50%;> [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(161)]).
INFO:NgdBuild:1222 - Setting CLKIN1_PERIOD attribute associated with PLL
   instance PLL_ADV_2 to 12.000000 ns based on the period specification
   (<TIMESPEC "TSrecord1_hdmi_in_clk_p" = PERIOD "GRPrecord1_hdmi_in_clk_p" 12
   ns HIGH 50%;> [opsis_hdmi2usb-hdmi2usbsoc-opsis.ucf(164)]).
WARNING:NgdBuild:1212 - User specified non-default attribute value (20.000000)
   was detected for the CLKIN_PERIOD attribute on DCM "DCM_CLKGEN_1".  This does
   not match the PERIOD constraint value (10 ns.).  The uncertainty calculation
   will use the non-default attribute value.  This could result in incorrect
   uncertainty calculated for DCM output clocks.
INFO:NgdBuild:1222 - Setting CLKIN1_PERIOD attribute associated with PLL
   instance PLL_ADV_3 to 20.000000 ns based on the period specification
   (<TIMESPEC TS_hdmi_out0_clocking_clk_pix_unbuffered = PERIOD
   "hdmi_out0_clocking_clk_pix_unbuffered" TSbase50_clk HIGH 50%>).
WARNING:NgdBuild:1440 - User specified non-default attribute value (20.000000)
   was detected for the CLKIN1_PERIOD attribute on PLL "PLL_ADV_3".  This does
   not match the PERIOD constraint value (10 ns.).  The uncertainty calculation
   will use the PERIOD constraint value.  This could result in incorrect
   uncertainty calculated for PLL output clocks.
Checking expanded design ...
WARNING:NgdBuild:440 - FF primitive 'FDPE_7' has unconnected output pin
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<15>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<14>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<13>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<12>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<11>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<10>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<9>' has no legal driver
WARNING:NgdBuild:470 - bidirect pad net 'fx2_data<8>' has no legal driver

Partition Implementation Status
-------------------------------

  No Partitions were found in this design.

-------------------------------

NGDBUILD Design Results Summary:
  Number of errors:     0
  Number of warnings:  15

Writing NGD file "opsis_hdmi2usb-hdmi2usbsoc-opsis.ngd" ...
Total REAL time to NGDBUILD completion:  45 sec
Total CPU time to NGDBUILD completion:   44 sec

Writing NGDBUILD log file "opsis_hdmi2usb-hdmi2usbsoc-opsis.bld"...

NGDBUILD done.
Release 14.7 - Map P.20131013 (lin64)
Copyright (c) 1995-2013 Xilinx, Inc.  All rights reserved.
Using target part "6slx45tfgg484-3".
Mapping design into LUTs...
Writing file opsis_hdmi2usb-hdmi2usbsoc-opsis_map.ngm...
Running directed packing...
Running delay-based LUT packing...
Updating timing models...
WARNING:Timing:3159 - The DCM, DCM_CLKGEN_1, has the attribute DFS_OSCILLATOR_MODE not set to PHASE_FREQ_LOCK. No phase relationship exists
   between the input clock and CLKFX or CLKFX180 outputs of this DCM. Data paths between these clock domains must be constrained using
   FROM/TO constraints.
WARNING:Timing:3159 - The DCM, DCM_CLKGEN, has the attribute DFS_OSCILLATOR_MODE not set to PHASE_FREQ_LOCK. No phase relationship exists
   between the input clock and CLKFX or CLKFX180 outputs of this DCM. Data paths between these clock domains must be constrained using
   FROM/TO constraints.
INFO:Map:215 - The Interim Design Summary has been generated in the MAP Report
   (.mrp).
Running timing-driven placement...
Total REAL time at the beginning of Placer: 1 mins 59 secs
Total CPU  time at the beginning of Placer: 1 mins 56 secs

Phase 1.1  Initial Placement Analysis
Phase 1.1  Initial Placement Analysis (Checksum:2547d81e) REAL time: 2 mins 9 secs

Phase 2.7  Design Feasibility Check
ERROR:Place:836 - Not enough free sites available for the components of the
   following type(s).
      LUTM   	Number of Components 17430   	Number of Sites 12816

ERROR:Place:375 - The design does not fit in device.
    Total LUT Utilization      : 42868 out of 54576
    LUTs used as Logic         : 25438
    LUTs used as Memory        : 17430
    FF Utilization             : 12857 out of 54576

Phase 2.7  Design Feasibility Check (Checksum:2547d81e) REAL time: 2 mins 13 secs

Total REAL time to Placer completion: 2 mins 13 secs
Total CPU  time to Placer completion: 2 mins 10 secs
ERROR:Pack:1654 - The timing-driven placement phase encountered an error.

Mapping completed.
See MAP report file "opsis_hdmi2usb-hdmi2usbsoc-opsis_map.mrp" for details.
Problem encountered during the packing phase.

Design Summary
--------------
Number of errors   :   3
Number of warnings :   2
Traceback (most recent call last):
  File "make.py", line 200, in <module>
    vns = platform.build(soc, build_name=build_name, **build_kwargs)
  File "/home/travis/build/timvideos/HDMI2USB-misoc-firmware/build/migen/mibuild/xilinx/platform.py", line 28, in build
    return self.toolchain.build(self, *args, **kwargs)
  File "/home/travis/build/timvideos/HDMI2USB-misoc-firmware/build/migen/mibuild/xilinx/ise.py", line 197, in build
    self.map_opt, self.par_opt)
  File "/home/travis/build/timvideos/HDMI2USB-misoc-firmware/build/migen/mibuild/xilinx/ise.py", line 124, in _run_ise
    raise OSError("Subprocess failed")
OSError: Subprocess failed
make: *** [gateware] Error 1
travis_time:end:0dd82a26:start=1442227993825402124,finish=1442228663016460292,duration=669191058168

The command "/trusty/run.py $PWD/.travis/run.sh" exited with 2.

Done. Your build exited with 1.

Opsis
Selected Device : 6slx45tfgg484-3

Slice Logic Utilization:
 Number of Slice Registers:           12865  out of  54576    23%
 Number of Slice LUTs:                24868  out of  27288    91%
    Number used as Logic:             14991  out of  27288    54%
    Number used as Memory:             9877  out of   6408   154% (*)
       Number used as RAM:             9680
       Number used as SRL:              197

Slice Logic Distribution:
 Number of LUT Flip Flop pairs used:  29331
   Number with an unused Flip Flop:   16466  out of  29331    56%
   Number with an unused LUT:          4463  out of  29331    15%
   Number of fully used LUT-FF pairs:  8402  out of  29331    28%
   Number of unique control sets:       481

IO Utilization:
 Number of IOs:                         125
 Number of bonded IOBs:                 109  out of    296    36%

Specific Feature Utilization:
 Number of Block RAM/FIFO:              114  out of    116    98%
    Number using Block RAM only:        114
 Number of BUFG/BUFGCTRLs:               13  out of     16    81%
 Number of DSP48A1s:                     22  out of     58    37%
 Number of PLL_ADVs:                      4  out of      4   100%

WARNING:Xst:1336 -  (*) More than 100% of Device resources are used

Atlys
Device utilization summary:
---------------------------

Selected Device : 6slx45csg324-3

Slice Logic Utilization:
 Number of Slice Registers:           12504  out of  54576    22%
 Number of Slice LUTs:                20768  out of  27288    76%
    Number used as Logic:             14855  out of  27288    54%
    Number used as Memory:             5913  out of   6408    92%
       Number used as RAM:             5638
       Number used as SRL:              275

Slice Logic Distribution:
 Number of LUT Flip Flop pairs used:  25181
   Number with an unused Flip Flop:   12677  out of  25181    50%
   Number with an unused LUT:          4413  out of  25181    17%
   Number of fully used LUT-FF pairs:  8091  out of  25181    32%
   Number of unique control sets:       490

IO Utilization:
 Number of IOs:                         137
 Number of bonded IOBs:                 122  out of    218    55%

Specific Feature Utilization:
 Number of Block RAM/FIFO:              116  out of    116   100%
    Number using Block RAM only:        116
 Number of BUFG/BUFGCTRLs:               12  out of     16    75%
 Number of DSP48A1s:                     22  out of     58    37%
 Number of PLL_ADVs:                      4  out of      4   100%

related to https://github.com/timvideos/HDMI2USB-misoc-firmware/issues/53, buf_fifo is taking too much ressource. I'm trying to reduce ram usage of others peripherals to allow building opsis target.
The reason it broke it that I increased a little bit firmware_ram.

https://github.com/timvideos/HDMI2USB-misoc-firmware/commit/70d371c54dc18f8162bbdfb2cd09065b2b7e0fb4 should fix it.

Fixed!


Add support for translations in actual addons

Similar to #480, but this PR adds support for actual addons, also issued in #5 (and closes #5). Not too sure if this covers all scenarios (I just looked up translations folders in node_modules/* and node_modules/@*/*, the latter for scoped addons), but at least it works for our codebase.
To elaborate a bit: translations in actual addons are available for use in an app, but since they're not owned by the app, they show up under Missing translations (the ones that are used). Just adding them to the translationFiles won't work properly yet, as that would cause such translations to end up under Unused translations while they could still be used by the addon itself (and that's not the purpose here). So, I split it up into own translations and addon translations, so that just the own translations can be used to detect unused translations, and the maps combined to detect missing translations.
~Note that I didn't add tests yet, I'd first like to have some confirmation that this a good approach.~ After I added a test for in-repo addons, it was quite simple to add a test for actual addons as well.

Thanks for the approval! I understand your thoughts about addon translations, so maybe good to quickly elaborate on how we use them. Our app consists of a few in-repo addons and a few actual addons, which are scoped dependencies, called @feedbackfruits/.... These addons are basically part of the application, but they're in their own repos to separate the concerns (and separate dummy apps, etc).
So that's why we can safely rely on using some translations from these addons in our app, and it's the reason why I wanted to add support for it here :)


docs/UCD Principles doc

Documentation on UCD Principles for front-end team of any trimester to work on
Please delete options that are not relevant.

[ ] Documentation (update or new)

How Has This Been Tested?
Github tests
Testing Checklist:

[x] Tested in latest Chrome
[ ] Tested in latest Safari
[ ] Tested in latest Firefox

Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have requested a review from ... on the Pull Request

 Research UCD principles


CommamdBar issue (WinUI 3 Desktop)

Describe the bug
The CommandBar background is nearly 100% transparent
Steps to reproduce the bug
1- Put a TextBlock on your WinUI 3 layout
2- Compile the app
3- Type a text and right click on it, you will find a weird menu with copy and paste options but with a transparent background
Expected behavior
Expected: Actual CommandBar with a background
Actual: Transparent CommandBar
Screenshots

Version Info
Windows app type: Win32
WinUI version: 3 (Project Reunion 0.5 preview)
NuGet package version:
[WinUI 3 - Project Reunion 0.5 Preview: 0.5.0-prerelease]

Windows app type:

UWP
Win32

No
Yes

| Windows 10 version                  | Saw the problem? |
| October 2020 Update (19042)        | Yes  |

Device form factor
Saw the problem?

Desktop
Yes

Additional context

This is by design, as a background appears when you press the "more" button.  You should probably place the control into a panel which has a background set on it already

This is the same issue as #4579


Misclasify noisy live images as spoof

I believe you have already known this problem exists. I just wanna ask if you can suggest any solutions

@xxxpsyduck may I ask a question:what's the method you get the depth map of the training data or do training datasets contain depth map of images?Thx in advance.

@xxxpsyduck may I ask a question:what's the method you get the depth map of the training data or do training datasets contain depth map of images?Thx in advance.

@EmmettJZK There are depth maps in the training set already

@EmmettJZK There are depth maps in the training set already

@xxxpsyduck : I think you use something like laplacian filter (some edge detection unit) to check sharpness of images and then feed images to model.


add axes visual

Description
This PR will close #1687 close #952 and address https://forum.image.sc/t/show-axes-reference-in-the-3d-canvas/43578 by adding an axes visual that shows the position of the axes in 2d and 3d
It's still a WIP, (toggling between 2d and 3d currently has a bug) but I'd love to get some input on what people want to see in more detail.
Right now the axes are tied to the world origin and have a fixed length in world space (hard coded to 100), this means that as you zoom in and out they change size instead of remaining fixed. It's probably worth making them remain fixed in length, say always 100 canvas pixels.
Another question is where the origin should be, should it be tied to the world coordinate 0, which it is now, or should it be tied to the center of the camera (which can move) or should it always just be in the bottom left corner say fixed in canvas space?
I'll be working on a fix for #1688 and a scale bar soon, which I see as somewhat related.
Here's a gif of where we are at now

Input welcome!! cc @jni @GenevieveBuckley @kevinyamauchi @bkcooper
Type of change

[x] New feature (non-breaking change which adds functionality)

It's still a WIP, (toggling between 2d and 3d currently has a bug)

Just fixed this

Options for axes location are

Fixed at world origin
Fixed at camera origin
Fixed in a corner of the canvas (say bottom left/ top right)

Options for axes lengths are

Fixed in world coordinates
Fixed in canvas coordinates

In theory all of these could be toggle-able / settable, and one day we could support all of them. I think I've seen examples of all of these in different 3D imaging software, so clearly they all can have pros/ cons, but it would be great to know how people are leaning at this stage!!

@Czaki not sure if this would be helpful to you too, but very curious what you think also

This is great! I like fixed at world origin and fixed as a small proportion (~5-10%?) of the world extent.
I'd also suggest using CYM as the colours, as blue is really low contrast on black.

@Czaki not sure if this would be helpful to you too, but very curious what you think also

I like this idea.

Another question is where the origin should be, should it be tied to the world coordinate 0, which it is now, or should it be tied to the center of the camera (which can move) or should it always just be in the bottom left corner say fixed in canvas space?

I prefer tie to world coordinate 0 or corner. Axes going through data not looks like something witch produce clear image.

I'd also suggest using CYM as the colours, as blue is really low contrast on black.

I suggest to think about colorblind persons. There should be some way to control at least one of colors, thickness, length to allow person with problem with color distinguish to use this feature (and produce publication figure which satisfy coloring requirements in publication).

This is great! I like fixed at world origin and fixed as a small proportion (~5-10%?) of the world extent.

Ok nice, when you say small proportion of world extent do you mean

like in the scale bar PR #1720 where they do change size with zoom, but it always stays ~100 canvas pixels
or should it always just be 100 canvas pixels independent of the zoom level of the camera?

I prefer tie to world coordinate 0 or corner. Axes going through data not looks like something witch produce clear image.

Ok seems like people like world coordinate 0 which is where it is now.

I'd also suggest using CYM as the colours, as blue is really low contrast on black.

I suggest to think about colorblind persons. There should be some way to control at least one of colors, thickness, length to allow person with problem with color distinguish to use this feature (and produce publication figure which satisfy coloring requirements in publication).

I like both these ideas, we could also add text labels, or little arrows / dashes too?

I like both these ideas, we could also add text labels, or little arrows / dashes too?

I think yes. Maybe instead of single position add submenu in view with options like:

None
Colored
Dashed (one solid, one dotted, one dased)
Text labels

Ok I've now update the scaling behavior so that the axes are always 100 canvas pixels long, irrespective of zoom and always located at the world coordinates origin using some code also present in #1720. I've also changed the coloring to CYM.
Do people like the zoom / positioning behaviour now?

I think yes. Maybe instead of single position add submenu in view with options like:

None
Colored
Dashed (one solid, one dotted, one dashed)
Text labels

I like this idea, can give this a go next!! Thanks @Czaki!

Ok, I've now added support for dashed axes. I currently default them to be white, but I wonder if I should keep them CYM or make them black, or something more complicated, like the opposite of the canvas background (I can do that, it's not too hard).
Here's what it looks like.

I've also realized that the "magic scale factor" I use for 3D (both here and in #1720) actually depends on canvas size, so I need to do some more looking into that before we're ready to merge.
I'll also add to the menubar an option to turn this stuff on. I like the None, Colored, and Dashed choices right now and can add those. I'll probably wait on text for followups unless people really want

Ok, I've fixed things so color of dashed will update to be opposite of color of background canvas
I've also added a menubar with the None, Colored, and Dashed options, see here

The only thing not quite right is the scaling in 3D, but I think that is less important to fix in this PR, but very important to fix in #1720. I suggest we review and merge this one without worrying about that, and then get right in #1720. It will be much easier there.
This is now ready for review!! cc @jni @GenevieveBuckley @Czaki

Following discussion here https://github.com/napari/napari/pull/1719#discussion_r503021234 and suggestion from @GenevieveBuckley I've now made it so that the axes can be both dashed and colored. I ended up adding a little Axes class that will be super simple once #1475 merges.
I didn't make the dashed lines different widths yet, let me know if that is still important.
I dropped that enum and have hopefully improved / centralized some of the doc strings.
Here's a gif of the drop down menu as it is now

Amazing.
How hard it will be to add arrows to inform about orientation?

Hi people, I hope you are ok!
Nice axes! I agree with everything I read in the comments, I think with toggle-able options most application cases will be covered. I have some thoughts/comments based on my normal usage (big bias, sorry!):

Length of axes: I think both fixed or variable size would be fine
I think, If axes are non-colored, then text labels are very important
Editable text label is another good feature, in medical imaging typical case is Right, Superior, Anterior, etc.
Corner axes location is a great idea, several times the only requirement is known the view rather than origin of the object. In this sense, a cube instead axes is good too.
Sorry for my lack of knowledge, but what the view would look like with axes at camera origin?

Cheers!

Thanks for weighing in @sfcaracciolo!

I think, If axes are non-colored, then text labels are very important
Editable text label is another good feature, in medical imaging typical case is Right, Superior, Anterior, etc.

We could do something here leveraging the axes labels stored in dims.axes_labels. I need to think about the best way to do this though, and maybe we end up making an issue and saving for a new PR, but it's a good idea.

Corner axes location is a great idea, several times the only requirement is known the view rather than origin of the object. In this sense, a cube instead axes is good too.
Sorry for my lack of knowledge, but what the view would look like with axes at camera origin?

I've actually gone ahead now and implemented a centered option which keeps the axes at the camera origin. It was a bit easier to implement than the corner and I don't think looks to bad. Maybe in the future if people prefer we can put it in the corner.

How hard it will be to add arrows to inform about orientation?

I think I can do that. I'll give it a try.

I've actually gone ahead now and implemented a centered option which keeps the axes at the camera origin. It was a bit easier to implement than the corner and I don't think looks to bad. Maybe in the future if people prefer we can put it in the corner.

I strongly prefer to have corner options. At least for publication screenshots.
I'm worry about multiple images with coloring (RGB for example). I work with confocal microscopy data which are multichannel and need coloring to distinguish objects. I such data axes on camera center may looks bad.
And if You use dashed without coloring on given example there could be problem with readability.

I strongly prefer to have corner options. At least for publication screenshots.
I'm worry about multiple images with coloring (RGB for example). I work with confocal microscopy data which are multichannel and need coloring to distinguish objects. I such data axes on camera center may looks bad.

Ok I hear you, will give that a go! Should be doable.

How hard it will be to add arrows to inform about orientation?

I've given this a go, see here now. Thoughts @Czaki?

Seems to me like last thing to do is make the centered option move to the bottom corner of the screen instead and then maybe we can finalize this and make additional improvements like text in followup PRs.

Wow, this is looking really nice!
I also agree that having the option to put the axes orientation marker in the bottom corner would be desirable for screenshots intended for publication.
Last question: I'm sure you've checked already, but the behavior when you "roll" through the 2D axes orientations (the button next to the 2D -> 3D one on the GUI) is what we'd expect to see, right?

Last question: I'm sure you've checked already, but the behavior when you "roll" through the 2D axes orientations (the button next to the 2D -> 3D one on the GUI) is what we'd expect to see, right?

It did not, but it does now! Thanks for the suggestion. If you have a 4D dataset it will cycle through the same 3 colors for the all axes, we could add a 4th color in the future, but I'd rather not for this PR, it's already grown quite a bit.

I also agree that having the option to put the axes orientation marker in the bottom corner would be desirable for screenshots intended for publication.

Absolutely agreed, this has actually proven a little more challenging, but will be much easier to do once we have a proper camera model with #854. I've removed the centered mode which no one really liked and we can then add this later.
I think functionality wise this is now good enough for a first pass and in the interest of keeping this PR small and reviewable we should probably save further enhancements like text, bottom right corner, and more colors for more axes for follow up PRs.
I still need to add some tests for this PR, but I think it is now ready for another round of code review.

I've now added a couple of minimal tests - just instantiating the axes object, making the axes visible/ not visible, and a screenshot test to determine that you can indeed see something when axes turn on. I think this is sufficient for now, will catch major regressions in functionality, we can then work on more comprehensive tests at a future date I think, unless the reviewers have additional suggestions

I've made the additional clarifications and minor updates requested by @jni. I've also made a new issue #1726 to capture some of the additional enhancements that people have requested. Thanks all for the input and suggestions here. It will be great to get this first pass in, but I'm sure we'll be making improvements to it quickly. I will merge once all tests pass


Devs SBAT know how target speeds in OKRs are measured

Expected Behavior
A document clarifying how measurements on app speed are taken in order to test whether OKRs are met.
Current Behavior
We have listed target times for starting the app to seeing up to date balances, but have not aligned on a consistent way to measure.
Measurement options include going through the Stackdriver logs or logging locally to the debugger.

Closing as this can now be done in clabs-pipeline


The compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions

Bug Report
XCode Version 10.2 (10E125)
UICircularRingLayer.swift
line : 247
The compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions
:warning: Your issue will be closed if these are not filled out. :warning:
Version 5.1.0 -> last version (6.0.2)
ANSWER HERE
Overview of what you tried to do
ANSWER HERE
What is the expected outcome?
ANSWER HERE
What is the actual outcome?
ANSWER HERE
Post sample code or example here
If sample code can't be provided because it's too long, please provide a small example project,
where I can test, if you cannot provide either. There is not much I can do.
let offSet = max(ring.outerRingWidth, ring.innerRingWidth) / 2 + ((valueKnobStyle?.size ?? 0) / 4) + (borderWidth * 2)
ANSWER HERE

Have you tried fixing this yourself?
let a = max(ring.outerRingWidth, ring.innerRingWidth) / 2
let b = (valueKnobStyle?.size ?? 0) / 4
let c = borderWidth * 2
let offSet = a + b + c
This project is open source, and I'm a student with very minimal amount of time.
Please give an attempt at fixing the issue first before creating a bug report.
This saves everyone time and benefits anyone who uses the library.
Pull requests are welcome!

Fixed in https://github.com/luispadron/UICircularProgressRing/pull/179 but Travis doesn't accept Swift 5 as of now.

Now out in version 6.1.0


Array iteration bugfix

Hi - I noticed this discrepancy when I was comparing post-merge - I'm guessing it's a bug..

Well that was a miss on my part. Thanks


WDS classnames and empty lines

@djghosh13  when comparing the results of benchmark with local files vs WDS equivalent, I noticed that for wds/vtab/clevr_closest_object_distance,  reading the classnames from https://huggingface.co/datasets/clip-benchmark/wds_vtab-clevr_closest_object_distance/blob/main/classnames.txt will cause it to ignore the 4th line because there is a if line.strip() as a condition https://github.com/LAION-AI/CLIP_benchmark/blob/main/clip_benchmark/datasets/builder.py#L724, there it was actually meant to be empty, I was using classnames from LiT paper:

Otherwise, everything else was fine.

Thanks for catching that! The line.strip() was an attempt to remove empty lines at the end of the file, not having realized that .splitlines() already factors in trailing newlines. That can be easily fixed to simply return the lines as is with no filtering.

Fixed.


Group 4 compression support

Hi!
I am building an Android App and I need to compress an image in group 4. But I am not seeing the option in TiffSaver.CompressionMode. Is there any way I can call COMPRESSION_CCITTFAX4 ??

Hello. I apologize for the long response time. I have not add this compression mode to library, but I will add it tomorrow

Also libtiff may have some bugs with this format. I check all compression mods that libtiff is supporting(http://www.awaresystems.be/imaging/tiff/tifftags/compression.html) and left only mods that can be decoded by GIMP

Hello. my apologize for long answer time. I didn't added support for most compression mods of libtiff(http://www.awaresystems.be/imaging/tiff/tifftags/compression.html) cause it's not work. Libtiff requires additional configuration and additional dependencies to work with most of compression mods. This feature will be added in future release.

+1 This compresion method Group 4 could be really interesting also for me.

Sorry guys, I'm working on it. As soon as I added support for COMPRESSION_CCITTFAX4 I will leave message in this topic

@iguron @gussorribas
In version 0.9.6 COMPRESSION_CCITTFAX4 and COMPRESSION_CCITTFAX3 has been added

Great!!!!!!!!
Igotz Urgoitia Ondiz
<EMAIL_ADDRESS>T:618967435

El 8 mar 2017, a las 22:44, Aleksey<EMAIL_ADDRESS>escribió:
@iguron https://github.com/iguron @gussorribas https://github.com/gussorribas
In version 0.9.6 COMPRESSION_CCITTFAX4 and COMPRESSION_CCITTFAX3 has been added
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Beyka/Android-TiffBitmapFactory/issues/6#issuecomment-285179348, or mute the thread https://github.com/notifications/unsubscribe-auth/AY8Kqthmk9VzCKNe1sqoPKTjEDWXy33qks5rjyFPgaJpZM4H9KWk.

So you can check it and if there is some kind of problems - please, write it down to this topic or new topic.

Great I will do it…
--
Igotz Urgoitia Ondiz
<EMAIL_ADDRESS>T:618967435

El 8 mar 2017, a las 22:50, Aleksey<EMAIL_ADDRESS>escribió:
So you can check it and if there is some kind of problems - please, write it down to this topic or new topic.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Beyka/Android-TiffBitmapFactory/issues/6#issuecomment-285180754, or mute the thread https://github.com/notifications/unsubscribe-auth/AY8KqltdPrnzInEXXH94Ayq59jn0SfUhks5rjyKUgaJpZM4H9KWk.


'For' has been mistakenly repeated

There was a repetition of "for" in below segment.

Respective url: https://docs.microsoft.com/en-us/azure/azure-sql/azure-hybrid-benefit?tabs=azure-powershell#next-steps
Though this is very minute one, thought of sharing this.

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

ID: 00f3b642-1d0d-363b-ed6e-a52dd93090e6
Version Independent ID: 5f3d7946-3455-650e-d21b-c2601495e876
Content: Azure Hybrid Benefit - Azure SQL Database & SQL Managed Instance
Content Source: articles/azure-sql/azure-hybrid-benefit.md
Service: sql-db-mi
Sub-service: features
GitHub Login: @stevestein
Microsoft Alias: sstein

@dspreddy77 Thanks for pointing this out. The document is updated and changes will go live soon.


Fix local flow

CC @oharboe
This is a follow up PR to https://github.com/The-OpenROAD-Project/megaboom/pull/34
It pins the bazel-orfs version to the one from https://github.com/The-OpenROAD-Project/bazel-orfs/pull/20 which should fix the local flow.
There seems to be some kind of issue with build for the L1MetadataArray, however the macros build properly. Please check this on your local machine.

@lpawelcz rebased manually and pushed to master.


SAM-200 Fix Reaper-instigated write-write errors

Moves the check made to exclude documents with recent timestamps to _check_col_updated from _delete_version_and_node_docs (thereby protecting both the update AND delete conditions), renames _deletion_delay to _reaper_updatable_delay (if anyone has a better name for that please lmk)

LGTM

@scanon it looks like there are some test failures, I'm checking them out


add transfer

Please makes sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

Pending English doc and tests.


When installed in a docker container, the wasmtime path is not found

I am not facing this issue with wasmer or wasmedge, only wasmtime.
I hava simple dockerfile which installs wasmtime and prints its version
# Use a base image with the desired Linux distribution
FROM ubuntu:latest

# Install necessary dependencies
RUN apt-get update && apt-get install -y curl

# Download and install Wasmer
RUN curl https://wasmtime.dev/install.sh -sSf | bash

# Add Wasmer binaries to the system PATH
ENV PATH="/root/.wasmtime/bin:${PATH}"

# Print the version of Wasmtime
RUN wasmtime --version

# Print Wasmer version
# CMD ["wasmtime", "--version"]

But it errors out saying wasmtime not found
/bin/sh: 1: wasmtime: not found

What is the value of $HOME when running the install command? It should install to $HOME/.wasmtime/bin if $WASMTIME_HOME is not set.

I tried ENV PATH="$HOME/.wasmtime/bin:${PATH}" but get the same error. $HOME should be root. Please ELI5

What messages does the install script print?

here are the portion of docker logs related to wasmtime install
[3/4] RUN curl https://wasmtime.dev/install.sh -sSf | bash
#6 1.363   Installing latest version of Wasmtime (v9.0.3)
#6 1.363     Checking for existing Wasmtime installation
#6 1.371     Fetching archive for Linux, version v9.0.3
#6 1.376 https://github.com/bytecodealliance/wasmtime/releases/download/v9.0.3/wasmtime-v9.0.3-x86_64-linux.tar.xz
######################################################################## 100.0%
#6 3.098     Creating directory layout
#6 3.103   Extracting Wasmtime binaries
#6 3.106 tar (child): xz: Cannot exec: No such file or directory
#6 3.106 tar (child): Error is not recoverable: exiting now
#6 3.107 tar: Child returned status 2
#6 3.107 tar: Error is not recoverable: exiting now
#6 3.110 cp: cannot stat '/tmp/tmp.oihoTMRyxk/wasmtime-v9.0.3-x86_64-linux/wasmtime': No such file or directory
#6 3.112 cp: cannot stat '/tmp/tmp.oihoTMRyxk/wasmtime-v9.0.3-x86_64-linux/LICENSE': No such file or directory
#6 3.112 cp: cannot stat '/tmp/tmp.oihoTMRyxk/wasmtime-v9.0.3-x86_64-linux/README.md': No such file or directory
#6 DONE 3.4s

Try installing xz.

worked, thanks!


Operator precedence for x?.y seems to be listed wrong

Under the section "Operator precedence" the following are listed as having equal precedence: "x.y" and "x?.y"
Also none of them are listed as being right associative.
This would then mean that the following two lines should be semantically identical:
var x = a.b?.c.d;
var x = (a.b?.c).d;
This how ever is not how the language works!
The first example will never try to access d on c if b is null. The final result will simply be null if b is null.
in the second example it will try to access d on the result of the expression in parentheses, even if b is null. (resulting in a null reference exception if b is null)
I am not sure exactly where in the precedence hierarchy "x?.y" belongs, but at least lower than primary expressions.

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

ID: 7eeac581-6235-2192-d909-e7fe3d21197f
Version Independent ID: 9d8e2a57-1c18-8cba-9bd4-eef546fe2dcb
Content: C# operators and expressions - C# reference
Content Source: docs/csharp/language-reference/operators/index.md
Product: dotnet-csharp
Technology: csharp-language-reference
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for noting this @initram
Ill add this to our backlog pending work currently in progress in the ECMA standards committee. The committee is evaluating two different strategies for the normative language in this feature:

dotnet/csharpstandard#7
dotnet/csharpstandard#251

Once one of those is merged, we'll update this article to match.

@initram @BillWagner there is some history about the precedence of the null-conditional operator (once it was moved away from the primary row but then returned back):
#18037
#18001 (that one contains a discussion about the operator precedence)

Your assertion that var x = a.b?.c.d; should mean the same thing as var x = (a.b?.c).d; only works if a.b?.c is a subexpression of the former.  But it isn't a subexpression of the former (even though it is a substring of the former).

Adding this to the sprint as I'm making other changes in the same file.

Already fixed in #34945.
Closing.


Document the new model structure

Document the new Data Dictionary in Mauro model structure and how to 'Edit' the content within Mauro.
Definition of Done:

Every Data Dictionary UML stereotype, there is a map to it's destination in Mauro model.
Similarly for Terminologies Data Sets and Code Sets.

Is this required?

Work Instructions and Wiki being created with help from James so issue closed.


Consider switching to the upstream GC version of CSL

We are using our vendored fork of CSL with GC added: https://www.npmjs.com/package/@mlabs-haskell/cardano-serialization-lib-gc
But Emurgo recently introduced their own bundles with GC enabled as a feature of wasm-bindgen:
https://www.npmjs.com/package/@emurgo/cardano-serialization-lib-nodejs-gc

Not sure if it makes sense to proceed with this, given that we are planning to switch to https://github.com/mlabs-haskell/cardano-data-lite


improve error message from createWorkflow

When I bring my local workflow to CI, all I got was
googleapi: got HTTP response code 404 with body: Not Found

add some log to trace down where it actually fails :-\
/assign @adjackura

(can we merge this?)

thanks ^^


Update step-scaling.yaml

Added action on scale in that wasn't currently configured.

Fix lambda invoke

Fix lambda invoke


CEPGP Migrate Roster Glitch

Describe the bug
CEPGP migration created an invalid roster which broke tooltips and required a rollback.
To Reproduce
Steps to reproduce the behavior:

Run CEPGP migration tool, new roster is created as expected
Renamed roster to 'Weekend' (I suspect this is what went wrong)
Reload
Note that new roster does not appear in item tooltip values even when checked
Remove other rosters
Item tooltips now produce a LUA error citing roster array index is nil, adding new rosters and even deleting this one does not fix

Expected behavior
Migration created roster to coexist peacefully, OR to obliterate all others and stand on its own.
I suspect that it collided with an existing roster upon reload. Perhaps it would occur baseline for anyone who happens to have created a roster named 'CEPGP' previously.
AddOn and Game Version:

CLM 2.6.1
WotLKC 3.4.0 (46368)

This sounds like migration misuse because it shouldnt be executed if there are any events in the system (even if you dont have them they would be synced back to you). I would need to see the SV that Has this happening to determine anything


Feature Request: Adding Leetcode problems 1300 - 1399

Description: Leetcode problems 1300 - 1399 are missing.
Use Case: Will add it up.

@Ajay-Dhangar Kindly assign me this issue!

@Ajay-Dhangar I can complete this

@Ajay-Dhangar I can complete this

already assigned so, work on other.

@Code-eat-sleep-include complete your task today's only and #222 is reference for you, If you don't done then I will assign to @Tirth-chokshi, because @Tirth-chokshi is done this task.

@Ajay-Dhangar Sure, I'll complete it by tonight.


Fixing Run Functional Test Task

Problem: Currently default working directory for RunFunctionalTests task on remote test agents is temp directory and the test settigns file is created there. Therefore, if any deployment items are specified within the test settings file with relative path, they are searched within the temp and not in the test drop location.
Issue Link: #1638
Fix: Checking if the path of depoyment items is not absolute and then prefixing them with test drop location, generating absolute path in the process.
Testing: Manual

Approved


Bug MissingPluginException in ios and rootbeer version update

Bug correction from isSafeDevice and canMockLocation in ios and updater RootBeer to 0.1.0

Thanks :)


Not able to view Edirotial Sample Code

Hi 31b4, would you be able to add this feature?
The smaple code in editorial page is not working as shown below.

Your work is really helpful. I really appreciate this.

Hey @pink-flames,
Can you provide with more information, i dont really get your suggestion,
in editorial codeblocks are working for me

How can i get "This Playground is Unavailable" error?

Thanks @31b4 refer the following link: https://leetcode.com/problems/insert-delete-getrandom-o1/?envType=study-plan-v2&envId=top-interview-150

Hey @praveen027,
This feature was already added, it was just outdated for this problem, i've updated the database with the new playground, now you should e able the see it. If you are running your own database with google sheets api, here you can download the updated one: https://github.com/31b4/Leetcode-Premium-Bypass/tree/database
Please if you see more outdated editorials, let me know.

Hi @31b4, I noticed this question also needs to be updated for the "This Playground is Unavailable" error: https://leetcode.com/problems/design-linked-list/description/


1.0.1 update

1.0.1 update

@chrislovecnm I've made the changes in the latest push

/lgtm
Squash and I will merge


Foreign Currencies don't appear to function correctly on map

Example:

I think this was 75 Rand, not £75

Good spot. I'm actually working on a brand new rebuild of Monzoweb at the moment so will fix it there and tag this issue 😄


🛠 [TASK] : Implement campaign details modal

Summary
A modal that contains a full description and all details of a specific Campaign, which can appear across product segments (e.g. Discovery Space, Voting Space). Includes full descriptions of each funding category within the campaign.
Composed of components:
#1185
#1184
#1183
User Value
As a Proposer I want to be able to view the full details of an active campaign, including the funding categories so I can align my idea with the objectives of the campaign and choose an appropriate category in which to submit my proposal.
As a Voter I want to be able to view the full details of an active campaign, including the funding categories so I can remind myself of the objectives of each category I order to inform my proposal evaluation and decision-making process.
Requirements
Modal contents should include — in MVE3

Campaign 'Hero' Image_  later
Campaign Title
Campaign Description
Campaign Requirements later
Campaign Dates: Start, End
Campaign Next Milestone/Deadline later
Campaign Categories Count
Proposals Submitted Count
Campaign Total Fund/Treasury later
Campaign Min. Proposal Ask later
Campaign Max. Proposal Ask later
Campaign Funds Requested later
Campaign Category Names
Campaign Category Descriptions (all sections)

Modal controls should include — in MVE3

Close Modal
Toggle Modal Section Collapse/Open
Select Campaign Category to view details
'Start Proposal' CTA (using currently viewed Category)
Favourite/Follow Campaign discuss/later
Share Campaign later
Other (Contextual Menu Dropdown) discuss/later
Previous / Next Campaign later

Figma Design: Campaign Details Modal
Relates to : #1069

UI is implemented
Waiting for backend integration.


[SPARK-16251][SPARK-20200][Core][Test]Flaky test: org.apache.spark.rdd.LocalCheckpointSuite.missing checkpoint block fails with informative message

What changes were proposed in this pull request?
Currently we don't wait to confirm the removal of the block from the slave's BlockManager, if the removal takes too much time, we will fail the assertion in this test case.
The failure can be easily reproduced if we sleep for a while before we remove the block in BlockManagerSlaveEndpoint.receiveAndReply().
How was this patch tested?
N/A

Test build #78095 has started for PR 18314 at commit 7515a5b.

Test build #78098 has started for PR 18314 at commit 4c792b9.

Test build #78095 has finished for PR 18314 at commit 7515a5b.

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/78095/
Test PASSed.

Test build #78098 has finished for PR 18314 at commit 4c792b9.

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/78098/
Test PASSed.

LGTM, merging to master/2.2/2.1/2.0


[Bug Report]: Failing E2E test suite

Bug Title
bug: found for civo and aws
Steps to Reproduce
run the e2e test suite for aws, civo
Expected Behavior
both should pass
Actual Behavior
civo is failing due to some invalid aka duplicate error,
aws is failign due to nil pointer in listlocation
and some os.Stat is not wrapped in a ksctl error type
https://github.com/ksctl/ksctl/actions/runs/9443629322/job/26007833422
Environment
github actions
Additional Context
No response
Confirmation

[X] I have searched the existing issues and this is a new and unique bug report.
[X] I agree to provide follow-up information if needed.

Scope of changes

[ ] Cli
[ ] UI
[ ] Docs

Agreement

[X] I agree to engage in constructive discussion and follow the Contribution Guidelines.

Resolve

[ ] Civo (@dipankardas011)
[ ] Aws (@Horiodino)
[ ] Os.Stat is not gettting wrapped in storage level (@dipankardas011 )

Also latest commits also has error in azure
{"time":"2024-06-10T06:47:52.669258877Z","level":"DEBUG","msg":"Printing","component":"azure","virtualNetworkConfig":{"location":"eastus2","properties":{"addressSpace":{"addressPrefixes":["<IP_ADDRESS>/16"]}}}}
{"time":"2024-06-10T06:47:53.940431628Z","level":"ERROR","msg":"handled error","catch":"FailedKsctlClusterOperationErr: failed to create virtual network component=azure Reason=PUT https://management.azure.com/subscriptions/***/resourceGroups/ksctl-resgrp-ha-test-e2e-ha-azure/providers/Microsoft.Network/virtualNetworks/test-e2e-ha-azure-vnet\n--------------------------------------------------------------------------------\nRESPONSE 400: 400 Bad Request\nERROR CODE: InUseSubnetCannotBeDeleted\n--------------------------------------------------------------------------------\n{\n  \"error\": {\n    \"code\": \"InUseSubnetCannotBeDeleted\",\n    \"message\": \"Subnet test-e2e-ha-azure-subnet is in use by /subscriptions/***/resourceGroups/ksctl-resgrp-ha-test-e2e-ha-azure/providers/Microsoft.Network/networkInterfaces/test-e2e-ha-azure-vm-cp-0-nic/ipConfigurations/ksctl-resgrp-ha-test-e2e-ha-azure and cannot be deleted. In order to delete the subnet, delete all the resources within the subnet. See aka.ms/deletesubnet.\",\n    \"details\": []\n  }\n}\n--------------------------------------------------------------------------------\n"}
{"time":"2024-06-10T06:47:53.940483419Z","level":"INFO","msg":"Local Storage Got Killed","component":"store-local","msgType":"SUCCESS"}
{"time":"2024-06-10T06:47:53.940490164Z","level":"ERROR","msg":"Failure","err":"FailedKsctlClusterOperationErr: failed to create virtual network component=azure Reason=PUT https://management.azure.com/subscriptions/***/resourceGroups/ksctl-resgrp-ha-test-e2e-ha-azure/providers/Microsoft.Network/virtualNetworks/test-e2e-ha-azure-vnet\n--------------------------------------------------------------------------------\nRESPONSE 400: 400 Bad Request\nERROR CODE: InUseSubnetCannotBeDeleted\n--------------------------------------------------------------------------------\n{\n  \"error\": {\n    \"code\": \"InUseSubnetCannotBeDeleted\",\n    \"message\": \"Subnet test-e2e-ha-azure-subnet is in use by /subscriptions/***/resourceGroups/ksctl-resgrp-ha-test-e2e-ha-azure/providers/Microsoft.Network/networkInterfaces/test-e2e-ha-azure-vm-cp-0-nic/ipConfigurations/ksctl-resgrp-ha-test-e2e-ha-azure and cannot be deleted. In order to delete the subnet, delete all the resources within the subnet. See aka.ms/deletesubnet.\",\n    \"details\": []\n  }\n}\n--------------------------------------------------------------------------------\n"


Unit test fs, ftp, network functions

Close the easy part of #31

Simply perfect!

Going to merge


Faked os.link is missing the follow_symlinks parameter

Describe the bug
Pretty much what it says on the tin.
How To Reproduce
def link_nofollow(s: Path, d: Path):
    s.unlink(missing_ok=True)
    d.unlink(missing_ok=True)
    s.symlink_to("nowhere")
    os.link(s, d, follow_symlinks=False)
    assert os.readlink(d) == "nowhere"

def test_realfs():
    link_nofollow(Path("file.txt"), Path("another.txt"))

def test_fakefs(fs):
    link_nofollow(Path("file.txt"), Path("another.txt"))

Your environment
Please run the following in the environment where the problem happened and
paste the output.
$ python -c "import platform; print(platform.platform())"
Linux-6.7.6-arch1-1-x86_64-with-glibc2.39
$ python -c "import sys; print('Python', sys.version)"
Python 3.11.7 (main, Jan 29 2024, 16:03:57) [GCC 13.2.1 20230801]
$ python -c "from pyfakefs import __version__; print('pyfakefs', __version__)"
pyfakefs 5.4.dev0
$ python -c "import pytest; print('pytest', pytest.__version__)"
pytest 7.2.0

This was actually implemented in fake_filesystem, but not added fake_os.
As usual: please check!


Meshes set to "Shade Smooth" from blender not working with fur

Hello! If you're still working on this I just want to say that this is a really cool shader thing, but for some reason every time when I use this shader on a mesh I've imported from blender with the "Shade Smooth" setting turned on (something I actually just realized not gonna lie) the shader instead spits out a cloned version of the entire mesh as though it were one giant face, but it does this for like, every face, so it looks wrong, but costs just as much performance lol. I'll try with no shade smooth, since I'm sure the fur will cover the blockiness of the model, but this could maybe be something included in the instruction...? I lowk spent like 25 minutes trying to change everything about my model until I realized this just now.

Hello again! Soooo... the shade smooth thing worked, but now all the fur particles are the same size and shape as the individual faces in the model, and don't do the normal fur scaling. Honestly I have no idea why and if you don't either that's cool. Either way this is one of the coolest godot shaders ive ever seen personally, and I hope that this finds its way to you somehow!

The distribution of the fur is based on UV coordinates, which may be why you are getting strange scaling issues. Not sure how that might be related to smoothing, but if you could post your blender file, I can take a look.


Add initial implementation of Table's BIR Model

Purpose
This PR contains the implementation which generates the BIR of Ballerina tables. The PR will add the model classes and the visitor implementation to generate the BIR of Table
Approach
Introduce the NewTable instruction in BIR generation phase to create a new table. Along with that, the primary keys indexes and the initial data set is passed.
The instruction looks like below.
target_Address = new_table [columns, indices, keys, data]

columns is the location of columns array.
indices is the location of indices array.
keys is the location of primary keys array.
data is the location of initial data array of records.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #15176 into master will decrease coverage by 30.79%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master   #15176      +/-   ##
============================================
- Coverage     53.96%   23.17%   -30.8%
- Complexity     3103     4969    +1866
============================================
  Files           320     1304     +984
  Lines         18049    65721   +47672
  Branches       3274     8871    +5597
============================================
+ Hits           9741    15230    +5489
- Misses         7053    48811   +41758
- Partials       1255     1680     +425

Impacted Files
Coverage Δ
Complexity Δ

...llerinalang/compiler/bir/writer/BIRTypeWriter.java
0% <0%> (ø)
0 <0> (?)

...2/ballerinalang/compiler/bir/model/BIRVisitor.java
0% <0%> (ø)
0 <0> (?)

...rinalang/compiler/semantics/model/SymbolTable.java
0% <0%> (ø)
0 <0> (?)

...erinalang/compiler/bir/model/BIRNonTerminator.java
0% <0%> (ø)
0 <0> (?)

...va/org/wso2/ballerinalang/compiler/bir/BIRGen.java
0% <0%> (ø)
0 <0> (?)

...lerinalang/compiler/bir/model/InstructionKind.java
0% <0%> (ø)
0 <0> (?)

...rg/wso2/ballerinalang/compiler/bir/BIREmitter.java
0% <0%> (ø)
0 <0> (?)

...lang/compiler/bir/writer/BIRInstructionWriter.java
0% <0%> (ø)
0 <0> (?)

tool-plugins/vscode/src/utils/logger.ts

tool-plugins/vscode/src/core/index.ts

... and 1058 more

Continue to review full report at Codecov.

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


On the page "Contributing" I read that "The source code of Dart follows the: Dart style guide". Should be filled the issue on each found deviations from this rule in Dart SDK?

According to the Contributing:
Coding style
The source code of Dart follows the:
Google C++ style guide
Dart style guide
Does this means that each line of source code in Dart SDK that does not follow these rules is an oversight of Dart Team?
If not, then what means the statement The source code of Dart follows Dart style guide
And what will means if the source code of Dart does not follows Dart style guide?
Or this is normal and these rules can be not followed only by Team members?

The code in the Dart SDK have developed over a number of years, and style guides have changed over time. In general new code should follow the style guides. We don't go update all files to follow the current style guide, and when editing a file which for some reason follows a different style it is sometimes better to keep that style to not pollute the diff.


Unable to run android app after flutter upgrade command

Error:
Launching lib/main.dart on MI 5 in debug mode...
Initializing gradle...
Resolving dependencies...
Running Gradle task 'assembleDebug'...
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.

java.lang.RuntimeException: com.android.builder.dexing.DexArchiveMergerException: Unable to merge dex

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Get more help at https://help.gradle.org

BUILD FAILED in 13s
Finished with error: Gradle task assembleDebug failed with exit code 1
Gradle:
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
localPropertiesFile.withReader('UTF-8') { reader ->
localProperties.load(reader)
}
}
def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}
apply plugin: 'com.android.application'
apply plugin: 'kotlin-android'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"
android {
compileSdkVersion 28
sourceSets {
    main.java.srcDirs += 'src/main/kotlin'
}

lintOptions {
    disable 'InvalidPackage'
}
dexOptions {
    preDexLibraries = false
}

defaultConfig {
    // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
    applicationId "in.krsolutions.xyz"
    minSdkVersion 21
    targetSdkVersion 28
    versionCode 1
    versionName "1.0"
    multiDexEnabled true
    testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"

}

buildTypes {
    release {
        // TODO: Add your own signing config for the release build.
        // Signing with the debug keys for now, so `flutter run --release` works.
        signingConfig signingConfigs.debug
    }
}

}
flutter {
source '../..'
}
dependencies {
implementation "org.jetbrains.kotlin:kotlin-stdlib-jre7:$kotlin_version"
testImplementation 'junit:junit:4.12'
androidTestImplementation 'com.android.support.test:runner:1.0.2'
androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'
implementation 'com.android.support:multidex:1.0.3'
}
apply plugin: 'com.google.gms.google-services'
Error while upgrading firebase libraries
/FlutterProjects/flutter/bin/flutter --no-color packages get
Running "flutter packages get" in leader...                     Because firebase_storage 1.0.4 depends on firebase_core ^0.2.3 and cloud_firestore >=0.9.0 depends on firebase_core ^0.3.0, firebase_storage 1.0.4 is incompatible with cloud_firestore >=0.9.0.
So, because leader depends on both cloud_firestore ^0.9.5+2 and firebase_storage 1.0.4, version solving failed.
pub get failed (1)
Process finished with exit code 1

The problem is most likely that firebase_storage is on 2.1.0+1, the version you have is from about 1 year ago. If you have problems with dependencies, its best to check pub.dartlang.org for newer versions.
For example, https://pub.dartlang.org/packages/firebase_storage#-versions-tab-

Getting below error after upgrading to libraries.
Launching lib/main.dart on MI 5 in debug mode...
Initializing gradle...
Resolving dependencies...
Running Gradle task 'assembleDebug'...
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedFolders(FileCollection)
Note: /FlutterProjects/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_core-0.3.1+1/android/src/main/java/io/flutter/plugins/firebase/core/FirebaseCorePlugin.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: /FlutterProjects/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_messaging-4.0.0+1/android/src/main/java/io/flutter/plugins/firebasemessaging/FlutterFirebaseInstanceIDService.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
/FlutterProjects/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.1+4/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:9: error: cannot find symbol
import androidx.annotation.NonNull;
^
symbol:   class NonNull
location: package androidx.annotation
/FlutterProjects/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.1+4/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:10: error: cannot find symbol
import androidx.annotation.Nullable;
^
symbol:   class Nullable
location: package androidx.annotation
/FlutterProjects/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.1+4/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:706: error: cannot find symbol
private void reportException(Result result, @Nullable Exception exception) {
^
symbol:   class Nullable
location: class FirebaseAuthPlugin
/FlutterProjects/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.1+4/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:610: error: cannot find symbol
public void onComplete(@NonNull Task task) {
^
symbol:   class NonNull
location: class FirebaseAuthPlugin.SignInCompleteListener
/FlutterProjects/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.1+4/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:629: error: cannot find symbol
public void onComplete(@NonNull Task task) {
^
symbol:   class NonNull
location: class FirebaseAuthPlugin.TaskVoidCompleteListener
/FlutterProjects/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.1+4/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:647: error: cannot find symbol
public void onComplete(@NonNull Task task) {
^
symbol:   class NonNull
location: class FirebaseAuthPlugin.GetSignInMethodsCompleteListener
/FlutterProjects/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.1+4/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:187: error: cannot find symbol
public void onComplete(@NonNull Task task) {
^
symbol: class NonNull
/FlutterProjects/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.1+4/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:492: error: cannot find symbol
public void onComplete(@NonNull Task task) {
^
symbol: class NonNull
/FlutterProjects/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.1+4/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:559: error: cannot find symbol
public void onAuthStateChanged(@NonNull FirebaseAuth firebaseAuth) {
^
symbol: class NonNull
9 errors
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':firebase_auth:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Get more help at https://help.gradle.org

BUILD FAILED in 36s

The Gradle failure may have been because of AndroidX incompatibilities in this Flutter app.
See https://goo.gl/CP92wY for more information on the problem and how to fix it.

Finished with error: Gradle task assembleDebug failed with exit code 1


Did anybody meat this problem“no matching function for call to..."

D:/msys64/dev/SdlGui-master/SdlGui-master-/src/gui/panel.cpp:11:134: error: no matching function for call to 'std::shared_ptrgui::Component::shared_ptr(bool)'
Panel::Panel() : mouseMotionInsideComponent_(false), mouseDownInsideComponent_(false), layoutManager_(std::make_shared()) {
^
In file included from D:/msys64/mingw64/include/c++/6.3.0/memory:82:0,
from D:/msys64/dev/SdlGui-master/SdlGui-master-/MwLibrary2/src/mw/shader.h:6,
from D:/msys64/dev/SdlGui-master/SdlGui-master-/src/gui/graphic.h:6,
from D:/msys64/dev/SdlGui-master/SdlGui-master-/src/gui/component.h:5,
from D:/msys64/dev/SdlGui-master/SdlGui-master-/src/gui/panel.h:4,
from D:/msys64/dev/SdlGui-master/SdlGui-master-/src/gui/panel.cpp:1:
D:/msys64/mingw64/include/c++/6.3.0/bits/shared_ptr.h:327:7: note: candidate: std::shared_ptr<_Tp>::shared_ptr(const std::weak_ptr<_Tp>&, std::nothrow_t) [with _Tp = gui::Component]
shared_ptr(const weak_ptr<_Tp>& __r, std::nothrow_t)

I have never seen this problem before. I mostly compiles using Visual studio, though. But it seems to be that a shared pointer is initialized to a false (bool) value. It should be a nullptr, but a more forgiving compiler accepts false. I removed the initialization in my last commit. Hopefully, this resolves the issue.

Yeah，I compiled this new file and it works，but the example in "srcTest"  I can't make done，Sounds foolish.Do you have any useful suggestion.

Good, that my changes solved the first problem. I have updated the submodule used by this library due to some compilation error I got when I tested to compile the project using gcc in linux.
(You can run in a git terminal "git pull" and then run "git submodule update --init --recursive" so you get the latest submodule updates)
You succeeded to compile? Did you try to run the excecutable? It could be some error specfic to your hardware, E.g. your OpenGl version on your computer. I tested to run on an old machine and I only got a black screen due to some shader compilation error during runtime.
Did you get any error messages which could be seen in the terminal?

 I mean that the example in the srcTest for Mwlibrary , Signal  or SdlGui I can't make successful.In solo filefloder,they gcc always have errors.
 In Signal/srcTest   ：

CMakeFiles/SignalTest.dir/srcTest/main.cpp.obj:main.cpp:(.text+0x4a9): undefined reference to operator new(unsigned long long)' CMakeFiles/SignalTest.dir/srcTest/main.cpp.obj:main.cpp:(.text+0x54d): undefined reference to operator delete(void*, unsigned long long)'
and so on,many similar errors.
In MwLibrary/srcTest:
CMake Error at /usr/share/cmake-3.6.2/Modules/FindPackageHandleStandardArgs.cmake:148 (message):
Could NOT find OpenGL (missing: OPENGL_gl_LIBRARY OPENGL_INCLUDE_DIR)
Call Stack (most recent call first):
/usr/share/cmake-3.6.2/Modules/FindPackageHandleStandardArgs.cmake:388 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.6.2/Modules/FindOpenGL.cmake:172 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:78 (find_package)
But I have GL/glew.h.Those problem occured me.

I tested to compile under GCC 5.4 and no errors. Which version do you use?
My first guess would be that you missing the GLEW library, But it could be that FindGLEW.cmake is missing something in order to find GLEW on your computer. On windows I use the environmental variable SDL2DIR to point to where my dependencies lies. E.g SDL2DIR variabel equals D:\Programmering\SDK\SDL2_net-2.0.1;D:\Programmering\SDK\SDL2_ttf-2.0.14;D:\Programmering\SDK\SDL2_mixer-2.0.1;D:\Programmering\SDK\SDL2_image-2.0.1;D:\Programmering\SDK\glew-2.0.0;D:\Programmering\SDK\SDL2-2.0.5

I use msys2 with gcc under 6.3.0，and install SDL2;SDL2_ttf ;SDL2_image;SDL2_net with online.They are in the same floder :D:\msys64\mingw64\include\SDL2;GLEW library is in D:\msys64\mingw64\include\GL.Signal
srcTest also have some conflict with gcc 6.3.0 x86_64.


How to set notification's tag property

How can I set tag property of notifiation object on backend?

You can send whatever you want in the payload, so you could send a JSON:
{"message":"your_message","tag":"your_tag"}

In the push listener of your service worker, you can then set the tag with:
// ...
const payload = event.data.json();
// ...
self.registration.showNotification(title, {
  body: payload.message,
  tag: payload.tag,
});
// ...
```. You'll send set

If you need more info, please reopen the issue, thanks!

Thanks for your answer issue is closed.