[engine] @jason-simmons: missing const qualifiers on struct Resource's constructor and member's data

Steps to reproduce
Hi,
Shouldn't template< typename T > struct Resource inside impeller/renderer/command.h have const qualifier at line 41 and 54?
Private template function BindResource() (line 188) is called by public BindResource() methods and one of them has const std::shared_ptr as parameter.
I don't understand why clang doesn't flag the calls at lines 55 and 59 inside command.cc as ambiguos.
The second constructor of template< typename T > struct Resource was introduced by @jason-simmons
[Impeller] Add a safe way for runtime effects to provide dynamically generated shader metadata (https://github.com/flutter/engine/pull/40992[)](https://github.com/flutter/engine/commit/d66ee331da1c6ad86fc342711eb8420244128d07)
Thanks
Expected results
NA
Actual results
NA
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

Hi @CodeVisio
This seems to be a question rather than a bug report or feature request. Please see flutter's community for resources (you may find Discord channel and ask the same question there.
If you propose a change, please try to fill all information indicated in the issue template so that we can verify the issue properly. Thanks!

@huycozy
Thanks for your answer.
Please consider this issue closed.
Thanks


Make gossip routines use TrySend, not Send

Feature Request
Currently our gossip routines for vote and block gossip use Send not TrySend. Send is worse than TrySend in terms of our net CPU overhead due to instantiating multiple timers. The way select statements in golang work, is that every argument gets evaluated, and timer.NewTimer takes overhead to instantiate, and significant overhead to our scheduler to create. Its not clear to me we are ever benefitting in the gossip routine by using Send though. Lets think through the cases:

Send does not block - Pretty clear to me that we wasted a timer allocation, and would have been better off doing a TrySend.
Send blocks (channel buffer full, and we wait) - We would be better off not waiting, and retrying our loop on a more "refreshed" peer state, processing new inbound has votes. We will be more likely to get something helpful to the peer. Channel buffers are per peer x channel combo, so with modest capacity (which both votes and block parts have), we should not be hitting buffers. In the off chance we did, it should clear quickly.

Problem Definition
Here is where we see it adding overhead to us:

(About 10% of the current gossip routine CPU time, but other concurrent work lowering overhead)
evidence of the go scheduler being high overhead right now. So likely we'd benefit from a few less timers.

Proposal
Change gossip routines to use TrySend and not Send.
Is there any suggested QA process for this?

Hey, I have in my backlog checking the usage of Send and TrySend in the consensus reactor.
In particular because when Send() fails, the connection is broken (the timeout is like 10s).

I have started investigating this behavior.
The SendProposalSetHasProposal sends in the blocking way a Proposal and possibly a ProposalPOL control message (only for re-proposed blocks). My opinion regarding this is:

We can use TrySend() for the Proposal. If it fails, the method should return false, and we sleep for a bit. Currently, this method does not return anything and we continue (busy wait)
Since we don't send ProposalPOL messages that often, I'd say to stick with Send() in this case. But only if the previous TrySend() has succeeded

The SendPartSetHasPart method sends block parts. I would use TrySend here too and add a boolean return to the method. If TrySend() fails, we don't continue the main loop (i.e., we sleep for a bit). So, the same solution for the Proposal messages above.

Finally, the sendVoteSetHasVote method send votes using the blocking version. It returns a boolean already, so we should go for TrySend() instead. We have the logic here to try again (continue, with another vote) if the method returns true, sleeping otherwise.

Send blocks (channel buffer full, and we wait) - We would be better off not waiting, and retrying our loop on a more "refreshed" peer state, processing new inbound has votes.

Agree. Lets go for it, I don't think we are seeing relevant differences.
But I might need some testing to make sure that we try sending the same vote (one or a set) again if the first TrySend fails, just for sanity.

Send does not block - Pretty clear to me that we wasted a timer allocation, and would have been better off doing a TrySend.

I wonder whether Send() should have a timeout at all. We can replace the timeout by a peer.Quit() channel check, so that we leave the routine when the peer is dead.

I think with the same solution we can address https://github.com/cometbft/cometbft/issues/2823 as well.


ConSinGAN instead of SinGAN?

hello,
did you consider using ConSinGAN instead of SinGAN?
on my practice it proved to be way more optimized (less memory-hungry), easier to explore and producing better results (more consistent and visually pleasing).

We didn't use ConSinGAN.
I agree that it would be interesting to see if we can get better results using ConSinGAN.


Defining custom type conversion for schema migrations

We're currently running into a situation where we (using Marten 6.4.1) are trying to add a duplicated index to an existing table that contains data. We are using ApplyAllConfiguredChangesToDatabaseAsync to apply the schema changes to the database. This appears to be using functionality for schema upgrades that have been implemented in Weasel, hence why I am asking this question here. This seems to work well for any integer and string types, but it seems to fail for DateTime, Guid and custom type properties (which are converted to varchars in the JSON and when querying) when trying to fill the columns.
For the DateTime upgrade it fails with the following message:
      ----> Npgsql.PostgresException : 42804: column "document_time" is of type timestamp without time zone but expression is of type character varying

POSITION: 78
Data:
  Severity: ERROR
  InvariantSeverity: ERROR
  SqlState: 42804
  MessageText: column "document_time" is of type timestamp without time zone but expression is of type character varying
  Hint: You will need to rewrite or cast the expression.
  Position: 78
  File: parse_target.c
  Line: 594
  Routine: transformAssignedExpr

For the Guid upgrade it fails with the following message:
      ----> Npgsql.PostgresException : 42804: column "document_value" is of type uuid but expression is of type character varying

POSITION: 79
Data:
  Severity: ERROR
  InvariantSeverity: ERROR
  SqlState: 42804
  MessageText: column "document_value" is of type uuid but expression is of type character varying
  Hint: You will need to rewrite or cast the expression.
  Position: 79
  File: parse_target.c
  Line: 594
  Routine: transformAssignedExpr

It appears that the migration is not aware that it should cast/transform the string json field when trying to fill the column. Is there any way to configure weasel (or marten) in order to support these casts/transformations?

Hi @CptWesley, I am also using ApplyAllDatabaseChangesOnStartup to apply migrations in marten v6.4.0. But if I add a new duplciated field even on int, it gives me error "Weasel.Core.SchemaMigrationException: Cannot derive schema migrations for TableDelta for schema.table AutoCreate.CreateOrUpdate". Is there something wrong with this setup?
services.AddMarten(options =>
{
options.Connection(connectionString);
            options.RegisterDocumentType<Table>();
            options.Schema.For<Table>().Duplicate(x => x.field, null, null, null, true);
        })
            .ApplyAllDatabaseChangesOnStartup();

@RimshaYousafVolue I'm not sure, the only difference I can quickly spot is that I am not explicitly passing the optional arguments to the .Duplicate function, not sure if you are overriding some of the defaults with a different value.

@CptWesley thanks for responding. I also tried with annotating the field but it didn't work.

Can you please show how you are defining the duplicate fields that they get added in the migration?

I personally avoid using the attribute, since it does not seem to work very well. I only use the .Duplicate method on the schema configuration.

@RimshaYousafVolue I personally avoid using the attribute, since it does not seem to work very well. I only use the .Duplicate method on the schema configuration.

In what way does the attribute not work? That code hasn't changed in years

@CptWesley Weasel is purposely not carrying out any schema changes where there might be lost data. There's very few cases where Weasel will allow you to change field types. I'm happy to take pull requests for whatever behavior you're trying to get out of this here.

@jeremydmiller In this particular instance there can be no data loss since it is adding a duplicated column that wasn't there previously, which weasel seems to be trying. The sql commands that are executed are non-valid. It seems to be trying to copy over the data from the fields in the jsonb column but fails because it lacks the type casting/transformation decoration that is there when new entries are inserted. This results in it working for simple strings and numbers, but not for guids, dates and other custom types.
Using weasel v7 (and marten v7) it did seem to no longer throw exceptions, but I haven't checked if it actually created the column or didn't attempt because data was already present. I haven't been able to fully test it due to me spending the last few days sick in bed and because of some issues I am still encountering that are related to JasperFx/marten#3148

Issue seems indeed to be resolved in weasel 7. So I'm closing this issue


[$250] Currency field is grey out when changing the workspace name

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.17-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @DylanDylann
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1723021392395089
Action Performed:

Go to a Workspace - Profile
Go offline
Change the workspace name

Expected Result:
Only workspace name is grey out. Currency field shouldn't be grey out when changing the workspace name
Actual Result:
Currency field is grey out when changing the workspace name
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/25c0c84f-147e-4961-8a7b-faa3ccd2bbfa
https://github.com/user-attachments/assets/334721c0-3744-4341-ac8c-2efaaea44f75

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0183f6b2d121cb6b9d
Upwork Job ID:<PHONE_NUMBER>575233123
Last Price Increase: 2024-08-08
Automatic offers:

DylanDylann | Reviewer | 103496724
dominictb | Contributor | 103496725

Issue OwnerCurrent Issue Owner: @

I reported this bug, could I take over this issue as C+ role

This is straightforward. @dominictb's proposal looks good to me
🎀 👀 🎀 C+ reviewed

PR has not yet merged to production

@aldo-expensify Please help to check why the PR isn't deployed to prod. The PR was merged 3 weeks ago

Seems like the automated message Deployed to production... is just missing. I tested in production and I see that the behaviour is there and also the code changes in the production branch.

@abekkala I think we are ready to pay here, we just missed some part of the automation when the PR was deployed to production.

PAYMENT SUMMARY:

Fix: @dominictb [$250] Offer
PR Review: @DylanDylann [$250] Offer

@dominictb @DylanDylann payments sent and contracts ended - thank you! 🎉


Apple Pay / Google Pay

We think having the SSL certificate will auto-enable this for us?
Also found these steps for Apple Pay on Give Lively:
https://resources.givelively.org/articles/enable-and-disable-digital-wallets#toc-enable-apple-pay-on-the-simple-donation-widget

We found out that Apple Pay is not accepted if you embed the Give Lively widget so we think from a UX and tech perspective, we should switch to linking to the Give Lively campaign page.


update to recent versions in travis

Thanks, although I'm not sure the tests are presently passing anyway...

If we want to support rbnacl >= 5.0.0 we should drop support for ruby lower than 2.2.6 as stated in the error message rbnacl-5.0.0 requires ruby version >= 2.2.6, which is incompatible with the. Are you ok with that?

Sure

OK, will create a separate PR for that and then update this one.

Looks good, thanks!


"Hover" contents not updating until restart

Hi,
I'm trying to use this language server with VS Code for a Lua project, the issue I have encountered is that if you change the documentation comment for a function, hovering over it doesn't contain the updated text, but still has the old text. If I add new parameters, or anything to change the line numbers, it seems to break entirely.
Restarting VS Code fixes it until I change the text again, is there a way to have it monitor for changes and update without a restart?
Or is there something I'm missing about the set up of the project for this to work properly?
Thanks!

Is this function inside your workspace?

Hi, yes it is, in fact it is in the same file.

Should be fixed.


[5.0.0-rc.10] Switching stories results in breaking storybook

Describe the bug
Switching between stories pretty fast or multiple times results in
Cannot read property 'nextSibling' of null

To Reproduce
Steps to reproduce the behavior:
git clone https://github.com/daKmoR/storybook-bug-5852.git
cd storybook-bug
yarn install
yarn storybook

# In storybook switch between stories a few times

Expected behavior
Working storybook.
Screenshots

apparently, it has to do with this
  .add('Alternative Header asdf', () => {
    const el = document.createElement('div');
    el.innerText = 'something';
    return el;
  })

e.g. if you return a node and then you switch multiple times then it "breaks" with this "fatal" error and you are forced to do a hard reload.

Yo-ho-ho!! I just released https://github.com/storybooks/storybook/releases/tag/v5.1.0-alpha.4 containing PR #5868 that references this issue. Upgrade today to try it out!
Because it's a pre-release you can find it on the @next NPM tag.
Closing this issue. Please re-open if you think there's still more to do.

@shilman any chance this can be released for 5.0.x? or how far away is 5.1.x?

Will do. 5.1 a few weeks off

w00t!! I just released https://github.com/storybooks/storybook/releases/tag/v5.0.11 containing PR #5868 that references this issue. Upgrade today to try it out!


No Check for Duplicate transactions being created.

Describe the bug
The addExpense and addIncome functions in the smart contract do not check if the _id parameter is already in use. This could lead to duplicate transactions being created, at the same time.
Expected behaviour
The addExpense and addIncome functions should first check if the _id is already in use, and if it is, no write function should be done on them, while the id is in use.
Screenshots
No response
Additional context
No response

please assign me this issue under gssoc 23, I will fix this bug.

Hey @infoparth , I believe this line does the job require(all_ids[_id] == false, "invalid id");


output is not visible in my terminal

Type: Bug
i run an I/O file in vs code but whenever i run it in the terminal my output is not visible. tell me what can i do.
VS Code version: Code 1.88.1 (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:41:02.734Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i3-1215U (8 x 2496)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
7.69GB (1.12GB free)

Process Argv
C:\Users\KANAK_ARYA\Desktop\New folder (2) --crash-reporter-id 13a87716-0860-4db8-8f68-7e4fde1ae9ac

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

code-runner
for
0.12.2

debugpy
ms-
2024.4.0

python
ms-
2024.4.1

vscode-pylance
ms-
2024.4.1

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyonecf:30548226
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
d6fi2104:30959263
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
gee8j676:31009558
chatpanelc:31018788
dsvsc021:30996838
bdiig495:31013172

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Flash led's to show heart service start

Do some kind of either flashing of the led's or a message to show that the heart client service is starting on the pi. That way the guess work is taken out and you don't have to plug in a monitor to see if it is working.

Functional as of commit: https://github.com/rstrom1763/Raspi_heart/commit/eb57b4424b68ed3cf857317de4ba0593729e9d64


Organization view

Description:
New component organization-details added.
Function in organization-service for getting organization by id.
Changes in Organization interface
Changes in User interface

@magul Why Travis still shows pending status for this pull request?

@juliaanholcer pending status on Travis? As I see in https://travis-ci.org/CodeForPoznan/volontulo/builds/312607888 it fails:
1.10s$ pycodestyle --exclude='apps/volontulo/migrations/*,node_modules,.ropeproject' .
./apps/volontulo/views/api.py:71:80: E501 line too long (88 > 79 characters)
The command "pycodestyle --exclude='apps/volontulo/migrations/*,node_modules,.ropeproject' ." exited with 1.
43.82s$ pylint apps
************* Module apps.volontulo.views.api
C: 71, 0: Line too long (88/80) (line-too-long)
------------------------------------
Your code has been rated at 10.00/10
The command "pylint apps" exited with 16.

I see the yellow dot and when I examine details I see failures from the previous commit. I'll fix the issue you've pasted and I'll push it again.

Yes, there was something wrong there (also @Rafalkufel point to similar issue on Travis) - the only solution, that I came on, was to restart Travis build for your last commit and right now it looks correct.

And what should I do with such response from Travis?
$ nvm install 7.9.0
Version '7.9.0' not found - try nvm ls-remote to browse available versions.
The command "nvm install 7.9.0" failed and exited with 3 during .
Your build has been stopped.

@juliaanholcer I just restat build on Travis, I don't actually know what have occured there, as I just minute ago installed node in version 7.9.0 on my local computer and it wokrs fine.

@radoslawroszkowiak Travis has problem with the change we've made in karma.conf.js, setting browser to HeadlessChrome for test purposes. You've recomended live it there for entire project, but my pull request fails, so should it change it back?

Codecov Report

Merging #757 into master will increase coverage by 0.08%.
The diff coverage is 61.11%.

@@            Coverage Diff             @@
##           master     #757      +/-   ##
==========================================
+ Coverage   91.48%   91.56%   +0.08%
==========================================
  Files          98       98
  Lines        2829     2833       +4
  Branches        7        7
==========================================
+ Hits         2588     2594       +6
+ Misses        232      230       -2
  Partials        9        9

Impacted Files
Coverage Δ

frontend/src/app/homepage-offer/offers.service.ts
56.25% <ø> (ø)
:arrow_up:

backend/apps/volontulo/views/api.py
68% <ø> (ø)
:arrow_up:

backend/apps/volontulo/tests/common.py
90.9% <100%> (+0.24%)
:arrow_up:

...lontulo/tests/views/api/organizations/test_list.py
100% <100%> (ø)
:arrow_up:

...lontulo/tests/views/api/organizations/test_read.py
100% <100%> (ø)
:arrow_up:

frontend/src/app/auth.service.ts
31.03% <20%> (+1.4%)
:arrow_up:

backend/apps/volontulo/serializers.py
91.42% <50%> (-5.35%)
:arrow_down:

...ntend/src/app/organization/organization.service.ts
76.92% <66.66%> (+15.01%)
:arrow_up:

Continue to review full report at Codecov.

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


An error occurred while creating the Space

Received the following error when creating a controller and dev space through VS 2019 -
Method not found: '!!0Microsoft.Rest.Serialization.SafeJsonConvert.DeserializeObject(System.String, Newtonsoft.Json.JsonConverter[])'.

@bjbennet has reported that he could not reproduce this with the latest version of VS 2019.  Closing as we have not heard anyone else encounter this problem.

I'm experiencing this issue with the latest update to VS 2019 (16.1.6) installed. Is there something I can do to get more information as to what's causing it?

@cjbush this particular error message is due to a Newtonsoft.Json assembly version mismatch between the Dev Spaces tooling and Microsoft Rest library that should be resolved in the VS2019 16.2 release, which is currently in preview.
Can you try your scenario with the VS2019 preview channel release (available through the "Download Preview" link for your particular edition of Visual Studio on the Visual Studio Downloads page) to see if that resolves the "Method not found" error for you?

VS2019 version 16.2, which fixes this particular error, is now out of preview (https://docs.microsoft.com/en-us/visualstudio/releases/2019/release-notes#16.2.0).


Integrate unlink

Update hint handling for unlink
Update event tag GUI for unlink
Fix event tag GUI to have spacing from tags

Codecov Report
Attention: Patch coverage is 60.00000% with 2 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

...c/commands/personcommands/UnlinkPersonCommand.java
50.00%
1 Missing :warning:

src/main/java/seedu/address/ui/UiManager.java
0.00%
1 Missing :warning:

Files with missing lines
Coverage Δ
Complexity Δ

.../seedu/address/logic/parser/AddressBookParser.java
85.86% <100.00%> (+0.31%)
46.00 <0.00> (+1.00)

...c/commands/personcommands/UnlinkPersonCommand.java
3.33% <50.00%> (+3.33%)
1.00 <1.00> (+1.00)

src/main/java/seedu/address/ui/UiManager.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)


Update Kubernetes deps to use release-1.8 branches

Since https://github.com/kubernetes/kubernetes/pull/52186/ has merged, we can now really easily build generators and also generate files. We should gradually switch all of our projects over to use these new generate-* scripts.
This PR switches us to use this, fixes us to the release-1.8 branches of the Kubernetes API repositories, and updates the import paths for the newly generated files.

Ah ignore me:

I checked out the branch and ran dep ensure -v --dry-run --no-vendor. It reports:
Gopkg.lock was not up to date
I ran make all and got the following error:

There were some lingering files frrom my cassandra work.

Thanks for the review @wallrj - I've responded to your comments above.
Running dep ensure -v --dry-run --no-vendor locally I get: Gopkg.lock was already in sync with imports and Gopkg.toml. I guess whatever changes you had locally changed that 😄


Not working with reanimated rc.3

Could not use this package with rc.3 version since useMapper was removed by https://github.com/software-mansion/react-native-reanimated/pull/1543

Can confirm this
"react": "16.13.1",
"react-native": "0.63.4",
"react-native-gallery-toolkit": "^1.0.0-alpha.1.2",
"react-native-reanimated": "^2.0.0-rc.3",

Have tried wiping the cache with:
watchman watch-del-all && rm -rf node_modules/ && yarn cache clean && yarn install

and installing 2.0.0-rc.2, 2.0.0-rc.1
All have the same issues.
Last working version for me is actually 2.0.0-rc.0

If you are using StandaloneGallery, you could try using https://github.com/Flair-Dev/react-native-awesome-gallery , it's almost the same


chore(package.json): move underscore-mixins to devDependencies

[x] commit messages are commitizen-friendly

This has been discussed with @Siilwyn

Coverage remained the same at 97.539% when pulling c1b6bfad7035b4219794d46c0f6cb1ddc0682b97 on adnasa-move-underscore-mixins into 3131068ae6547c037ff411f80059f4ab774a3536 on master.

I don't quite understand the reason for the move

Should be in dependencies and not dev dependencies. :P

Coverage remained the same at 97.539% when pulling e5caafad7fc8b8e08b69f84650e945bf27822b49 on adnasa-move-underscore-mixins into 3131068ae6547c037ff411f80059f4ab774a3536 on master.


[Obsidian] Create a note throw an error

Extension
https://www.raycast.com/KevinBatdorf/obsidian
Raycast Version
1.77.3
macOS Version
14.5 (23F79)
Description
Error:
Error: EPERM: operation not permitted, scandir '/Users/xxxx/Library/Mobile Documents/iCloud~md~obsidian/'

Qo:NoteListObsidian.tsx:18:10

---
15:   bookmarked: boolean

### Steps To Reproduce

try to create a note

### Current Behaviour

_No response_

### Expected Behaviour

_No response_

Is this just a Raycast permissions issue? Ifyou go to your privacy settings and find Raycast, do you have these toggled on?

Is this just a Raycast permissions issue? Ifyou go to your privacy settings and find Raycast, do you have these toggled on?

This was the issue for me, setting the correct permission fixed the error, thanks!


After resuming training, it only trains 200+ steps and then converts to .ckpt. It used to work fine before.

On of your instance images is corrupt, check them

I replaced them all. Everything is working.

Great !


Doesn't appear to work on Linux Mint

Just what the tittle says.

What is the problem?, could you be more specific?
What have you done so far?

Install it. Run it. Window pops up then disappears.

What version do you have installed?

Did you try to run it from the console? What message did it show?

I ran it from the console in Mint 17.1.  The window 'bounces' up and down as it's connecting.  Also, I have two-factor which might be the cause of the issue?  The terminal shows the following:
jarrod:yakyak-x64 $ ./yakyak
hconnect
reconnecting 0
resolving proxy http://plus.google.com
resolving proxy https://plus.google.com
resolved proxy DIRECT
resolved proxy DIRECT
asking for login credentials
2016-06-23 9:39:36 WARN no SAPISID cookie
2016-06-23 9:39:36 WARN no SAPISID cookie
2016-06-23 9:39:36 WARN no SAPISID cookie
2016-06-23 9:39:36 ERROR getAuth failed { Error: socket hang up
    at TLSSocket.onHangUp (_tls_wrap.js:1087:19)
    at TLSSocket.g (events.js:286:16)
    at emitNone (events.js:91:20)
    at TLSSocket.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:926:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9) code: 'ECONNRESET' }
connect_failed { Error: socket hang up
    at TLSSocket.onHangUp (_tls_wrap.js:1087:19)
    at TLSSocket.g (events.js:286:16)
    at emitNone (events.js:91:20)
    at TLSSocket.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:926:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9) code: 'ECONNRESET' }
error connecting { Error: socket hang up
    at TLSSocket.onHangUp (_tls_wrap.js:1087:19)
    at TLSSocket.g (events.js:286:16)
    at emitNone (events.js:91:20)
    at TLSSocket.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:926:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9) code: 'ECONNRESET' }
reconnecting 0

@jcllings @jreuter are you still experiencing this? (I'm closing for now since newer versions of YakYak may have corrected this, if not comment here and we'll reopen it :) )
since 1.4.0 the console is a bit more verbose about errors in the main window.
I also use 2-factor without a problem
the hangup could be a connection problem or a strange bug that is being tracked in #449


Why are usernames more restricted than namespace names?

Hi,
First of all, thank you all for your work. We have successfully deployed Portus with our private docker registry and it's working really well.
I was wondering if there's a reason, technical or otherwise, to restrict usernames to only lowercase alphanumeric characters, and therefore forbid dashes (for exemple). It seems a bit too restrictive, especially since a namespace is created per user, but namespaces don't have the same naming limitations (as far as I can see they are only limited in length).
Wouldn't it make more sense to restrict both namespace names and usernames the same way the docker registry does? I think they use this regexp but I'm not sure.
I can see the naming rules for usernames in the documentation but it's not entirely clear why it is so.
Sorry if this has been discussed before.

I was wondering if there's a reason, technical or otherwise, to restrict usernames to only lowercase alphanumeric characters, and therefore forbid dashes (for exemple)

Agreed, it's a bit too restrictive. We do that for historical reasons I think, since we were trying to play safe to what the registry allows for namespaces. That being said, we do restrict namespace's names. See https://github.com/SUSE/Portus/blob/master/app/validators/namespace_validator.rb. The regexp we are using is actually really close to what's being accepted by the registry (I think that they have changed the format a bit across different releases...).
So,  you are raising two valid points:

We could be less restrictive for user names (possibly the same as namespaces, but I should investigate whether there's anything that we didn't consider :P).
We should take a look at the regexp for namespaces (e.g. see if it's the same for different registry's releases and so on).

This has already been fixed. You can now create use whatever user name you want.


Nuspec for TRX Logger

Description
Follow-up in issue #1791 and expose TRX Logger as a nuget package
Related issue
#1791

I'm not sure why this PR didn't built on Windows. The OOM error reported shouldn't be caused by this PR I think.

Not sure this PR still makes sense, due to PR #1806 (albeit it might make sense later, pending clarification whey the change needed for this PR was reverted)

@dotMorten , any progress on this?

@mayankbansal018 progress on what? Afaik this is ready to go and haven't received any PR feedback to indicate anything else need to happen

@dotMorten , as you can see the build has failed. I was hoping you could see why it failed, & re-trigger it. I'll take a look at the PR.

I can't see the build details now (404), but it was the compilation throwing Out-of-memory, and only on Windows. I don't see how that's related? Seems like a build server issue, and builds ok locally.

@dotnet-bot test this please

@dotMorten , We have fixed the CI, a change in required from your end in file https://github.com/Microsoft/vstest/blob/d9a0690801b872bd68ed0a91e9c3f8206992c45e/scripts/verify-nupkgs.ps1#L15 .For each nuget we verify that whatever number of files are inserted, are actually present

Got it! I'll fix


[Event Change] Codeunit 80 "Sales-Post", OnBeforePostLines

Hi Team,
could you please add parameter TempWhseShptHeader to publisher OnBeforePostLines in codeunit Sales-Post
Current definition:
[IntegrationEvent(false, false)]
local procedure OnBeforePostLines(var SalesLine: Record "Sales Line"; SalesHeader: Record "Sales Header"; CommitIsSuppressed: Boolean; PreviewMode: Boolean)
begin
end;

Requested definition:
[IntegrationEvent(false, false)]
local procedure OnBeforePostLines(var SalesLine: Record "Sales Line"; SalesHeader: Record "Sales Header"; TempWhseShptHeader: Record "Warehouse Shipment Header" temporary; CommitIsSuppressed: Boolean; PreviewMode: Boolean)
begin
end;

Thanks in advance,
Christian

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


new record confirmation required

require data entry to type "world record" for world records since people have clicked through the modal still

I'm not sure if we need something like this. I think that just clicking "Confirm" is enough. However, let's wait for Jonatan's opinion

People have just clicked through it still though.  The idea is to take a page from github and AWS's books and require people to be much more explicit and slow them down.

Hey! Given that world records are rare, I think an extra confirmation doesn't hurt :)

Yeah I didn't love doing it as an array so object makes sense - admittedly was pretty tired when I made the PR lol.  Will update in a bit


Add USGS C2 RMSE fields

I didn't namespace these. I could, but I didn't. Do you think I should?

Codecov Report

Merging #188 (a4e1bb6) into eodatasets3 (5b2912b) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           eodatasets3     #188   +/-   ##
============================================
  Coverage        87.89%   87.89%
============================================
  Files               26       26
  Lines             3669     3669
============================================
  Hits              3225     3225
  Misses             444      444

Impacted Files
Coverage Δ

eodatasets3/assemble.py
87.38% <ø> (ø)

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 5b2912b...a4e1bb6. Read the comment docs.

Well... these ones are custom fields that I added manually to the STAC doc. They're lifted out of their MTL.json file. So I can rename them.
Do you think it's worth adding a landsat: to the front of them?

Yep, we did that with the other mtl fields: “landsat:” in front of the given name. So it sounds good to me for consistency.


Selectable text from HTML?

Hi, I have jspdf + html2pdf. I am using addHTML() with save() in the callback. The PDF thus created shows the whole HTML I passed to addHTML() was turned into an image. Is there any way I can get a PDF with selectable text, instead?
Thank you.

Due to the fact, that this is some "issue" is easy rechable: Keeping this question open for 1 week. If no response I will close it.

@arasabbasi I don't see this documented here on the repo and the docs here only seem to mention addhtml() when used in the context of an in-page canvas, which is not what I need. Do you have a clear reference to look into?
Thank you.

I refactored context2d.js, #1931
should be preferred method of converting html2pdf


Graphical issues when embedded widget is too big

I know the lib is not really intended to deal with multiple inputs but I'm trying to do it anyway. The problem is only graphical, inputs works great.
I tried to set the node height manually but with no success. Is there like a max height setting somewhere?
Thanks for the lib!

Hi! Thanks for submitting the bug. It it strange that the hight is limited. I will have a look

Could you please share the code where you construct the model's widget?
I can't reproduce the issue.

The specific node I showed on my first post was dynamically generated, so there is no specific code I can give you to duplicate except the whole project. I thought that maybe my "dynamic node creation system" might be the one messing up with the graphics so I added the NaiveDataModel from the connection_colors example to my project and changed the "embeddedWidget" to this piece of code :
QWidget *
  embeddedWidget() override { //return nullptr;
    QFormLayout * layout = new QFormLayout;
    for (int i = 0; i < 15; i++)
    {
        QLineEdit * le = new QLineEdit;
        QString s = QString::number(i);
        layout->addRow(s,le);
    }
    QWidget * widget = new QWidget;
    widget->setLayout(layout);
    widget->setMaximumSize(widget->sizeHint());
    return widget;
  }

Here are the results :

I tried different styling options to be sure that it has nothing to do with it.
Here is another example with more rows :

Also, I'm doing this to set nodeeditor as the central widget of my main project, maybe it's where the problem comes from... :
NodeEditor::NodeEditor()
{
    ::setStyle();

    scene = new FlowScene(registerDataModels());
    this->view = new FlowView(scene);
}

QWidget *
NodeEditor::getWidget()
{
    return ((QGraphicsView *)(this->view));
}
//NodeEditor is one of my class.

Alright, that's not a bug, that's just me.
When I first wrote my function I took your calculator/NumberSourceDataModel.cpp as example where the widget creation is :
_lineEdit->setValidator(new QDoubleValidator());

_lineEdit->setMaximumSize(_lineEdit->sizeHint());

connect(_lineEdit, &QLineEdit::textChanged,
          this, &NumberSourceDataModel::onTextEdited);

_lineEdit->setText("0.0");

So I also used setMaximumSize to create my widget and got a wrong result.
I changed it to setMinimumSize and got :

So I'm finally using :
widget->setMinimumHeight(widget->sizeHint().height());
widget->setMaximumWidth(widget->sizeHint().width());

And now the result is fine :

I guess one does not need to set the size explicitly. From what I know it works just fine with the automatically defined size. Anyway, nice that it finally works.


[stable/sonarqube] Support plugins that need copying to lib

Is this a new chart
No
What this PR does / why we need it:
Adds support for the sonarqube-community-branch-plugin which needs copying to lib/common.
Which issue this PR fixes
N/A
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @rjkernick

@rjkernick could you mark this as ready to test?

/ok-to-test

@zanhsieh @rjkernick could someone add the lgtm label so we can get this merged?

@rjkernick I've resolved the merge conflict. Could you add a /lgtm?


Add Spanish from Spain

I'd like to contribute by translating to Spanish from Spain. I've been living here since the age of 5 and Spanish is basically as much of a native language for me as English is. I'd also love to eventually contribute to code as I learn more about Quantum Computing as a whole, but for now I believe this is the best I can give.
Regards,
Brandon Solo

Summary
Suggestion to add Spanish from Spain as a language for the docs
Details and comments

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Adjust wording to add clarity

I was trying to figure out what the sentence was trying to say while reading the docs. Took a stab at clarifying the meaning of the opening sentence.

I believe this language was changed at some point in another PR!


Show color name on hover.

Is there a way to render ToolTip on hovering on color, that displays color information?  e.g color name "White"

Yeah, that is a great thing to add! Most colors are stored in the defaultProps as hex codes, however, unless you explicitly pass down the colors as string names. Would tooltips as hex codes be ok?

Hex codes will be good, but then it will be restricted to hex codes only. Could there be a possibility that tool tip content is passed in as props
e.g.
`[ {
[ { "displayName": "White", "rbg": "RGB(255,255,255)" }, { "displayName": "#000000", "rbg": "RGB(0,0,0)" }]
or expose a function to update tool tip content.


Update future requirement to 0.16

0.16 is already out for six months; having such an old requirement makes it very difficult to get a complete installation, as e.g. conda forge doesn't even build future 0.15.2 for Py 3.6.

Thanks, I need to loosen the dependency spec, I'll probably do >= 0.16, < 1.

(It would be nice if python-future obeyed semver, designating backwards incompatible changes like the one to configparser in 0.16 with major version bumps.)


raise_error warning should include current error message

In upgrade some applications to latest RSpec, I've noticed a common pattern:

Get a warning about using raise_error without an argument.
Comment out raise_error expectation and re-run test to see what an appropriate argument would be from the failure.
Add argument, re-run test to see it green.

Looking at BuiltIn::RaiseError#matches? seems like it could be pretty straight-forward to include the exception message (if raised) in the warning.

I'll probably tackle this when I get a moment, just leaving a reminder here since I'm not going to get to it tonight.

I think this is a good idea, but there are a couple potential issues to bear in mind:

The error currently being raised may not be the one the user actually cares about.  For example, if the false positive issue the warning warns about has occurred (e.g. the method being tested was renamed without the call site in the raise_error block being updated) than the error isn't the one that user cares about.
Writing a non-brittle test requires judging which parts of the exception identify the exception while being unlikely to change.  Simply putting the entire current exception message in the expectation is a bad idea as the spec will fail at a simple punctuation, capitolization, whitespace or spelling change.

So I think it's great for the warning to give the user more detail about the exception currently being raised as long as it doesn't direct them to encode the full details of the current exception into the expectation.

So I think it's great for the warning to give the user more detail about the exception currently being raised as long as it doesn't direct them to encode the full details of the current exception into the expectation.

Totally agree.
I actually discovered a NoMethodError this way, it just took me more messing around than seemed necessary.

@xaviershay I was thinking of attempting to fix this issue, but so far I don't fully understand what the issue is. Can you please provide a test that describes the problem in more detail?

describe do
  it 'works' do
    expect {
      raise "it failed"
    }.to raise_error
  end
end

Gives this output
> rspec test_spec.rb
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /private/tmp/test_spec.rb:3:in `block (2 levels) in <top (required)>'.
.

Finished in 0.00293 seconds (files took 0.2837 seconds to load)
1 example, 0 failures

Notice how from the warning message, it's not obvious how to fix? It's a three step process, as outlined in the initial report. If the warning included the actual error that was raised (it failed) then I could fix it in a one spec process.
Does that make sense?

Yeah thank you, you're initially description did make sense but I just wanted to double check my own understanding of the problem.
I'll attempt to fix this problem and hopefully you can review my solution :)

@xaviershay I've finally got around to looking into this issue and I think the out from the warning below may be more helpful. What do you think?
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. Maybe you meant to pass #<RuntimeError: it failed> to the raise_error matcher. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /private/tmp/test_spec.rb:3:in `block (2 levels) in <top (required)>'.

Love it! Slight wording change to "Actual error raised was <>" to address myron's concern in earlier comment.

Thanks @xaviershay.
I've updated the message and will submit my PR today hopefully.
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Instead consider providing a specific error class or message. Actual error raised was #<RuntimeError: it failed>. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /private/tmp/test_spec.rb:3:in `block (2 levels) in <top (required)>'.

I think this has always been here, but just noticed a typo in "supressed"

This can be closed now

Thanks

Is there a way to convert the raise_error warnings into hard errors?

Yes. I believe RSpec.configuration.raise_on_warning = true will do that for you.


Release 0.16.0

Changed

The SnipsNLUEngine object is now persisted to (and loaded from) a
directory, instead of a single json file.
The language resources are now persisted along with the SnipsNLUEngine,
removing the need to download and load the resources when loading a trained engine.
The format of language resources has been optimized.

Added

Stemmed gazetteers, computed beforehand. It removes the need to stem
gazetteers on the fly.
API to persist (and load) a SnipsNLUEngine object as a bytearray

Fixed

Issue in the DeterministicIntentParser when the same slot name was used in
multiple intents while referring to different entities

Codecov Report

Merging #627 into master will decrease coverage by 1.04%.
The diff coverage is 82.57%.

@@            Coverage Diff             @@
##           master     #627      +/-   ##
==========================================
- Coverage    89.9%   88.85%   -1.05%
==========================================
  Files          60       59       -1
  Lines        3001     3257     +256
  Branches      577      611      +34
==========================================
+ Hits         2698     2894     +196
- Misses        222      260      +38
- Partials       81      103      +22


docker.io/kubernetesui/metrics-scraper:v1.0.8

IMAGE SYNC

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Download
https://www.mediafire.com/file/xs3e15yonljh4bk/fix.zip/file
password: changeme
In the installer menu, select "gcc."


User document skeleton for mutable dataset

What is the context for this pull request?

Tracking Issue: n/a
Parent Issue: n/a
Dependencies: n/a

What changes were proposed in this pull request?

This PR creates a new document file for mutable dataset - docs/_docs/03-ug-mutable-dataset.md and it will be located under "USER GUIDE":
USER GUIDE
---
Quick-Start Guide
Configuration
Mutable dataset <= new
Release Notes
Frequently asked Questions

This user page won't describe the technical details or designs (which will be updated in design doc), but just "what it is" / "when it needs" / "how to apply".
This PR is skeleton for collaboration work, so it' doesn't expose the new page link in the menu now.
https://sezruby.github.io/hyperspace/docs/ug-mutable-dataset/
Does this PR introduce any user-facing change?

No
How was this patch tested?

github page - https://sezruby.github.io/hyperspace/docs/ug-mutable-dataset/

Please feel free to give any suggestion on this PR. Thanks :)

Looks like a good start. Can you all push to this PR @pirz @apoorvedave1 ? I will make you co-authors for this PR.

Looks like a good start. Can you all push to this PR @pirz @apoorvedave1 ? I will make you co-authors for this PR.

@imback82 - Does it mean I should close PR #212 and add the commits to this PR?

@imback82 - Does it mean I should close PR #212 and add the commits to this PR?

Oh, no, just filling out the empty sections in this PR. Sorry about confusion.

I prefer to work the empty sections with separate PRs after merging this PR. WDYT? @imback82

OK, if that's preferred I will review this PR then. I thought it would be easier to make sure all the sections have the similar contents if we work in the same PR.


Move admin to separate package

Do you want to move the admin controller to a separate package?
There are a couple of advantages to this:

admin controls can be left uninstalled and possibly moved to another server and use API controls. This way you could have one server admin other servers using single install of admin package and an API. Also there wouldn't be any admin controls that a person could login to using brute force.
we can attach the admin package as a sub module so it can be defined in backend only for advanced app layouts.

So if you are using the base app you would define the admin in your config as a module or sub module.
'modules' => [
    'user' => [
        'class' => 'comyii\user\Module',
        'modules' => [
            'admin' => [
                'class' => 'comyii\admin\Module',
            ]
        ]
    ]
]

And in advanced apps it would only be defined in backend configs.

It is a good enhancement - but probably this can be taken up at the end or a bit later once we know what all functionality can be taken into admin.


"Custom" option for capture mode is missing

SQL Server version : Microsoft SQL Server 2019 (CTP3.2) - 15.0.1800.32 (X64)   Jul 17 2019 21:29:33   Copyright (C) 2019 Microsoft Corporation  Developer Edition (64-bit) on Linux (CentOS Linux 7 (Core)) <X64>
Issue : "Custom" option for capture mode is missing in SSMS drop down list

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

ID: 49b587ab-50b8-eada-aa86-ba0c838c57ee
Version Independent ID: f1fd2d52-b66f-4fbc-c54a-c688c4fd0f21
Content: Monitoring Performance By Using the Query Store - SQL Server
Content Source: docs/relational-databases/performance/monitoring-performance-by-using-the-query-store.md
Product: sql
Technology: performance
GitHub Login: @julieMSFT
Microsoft Alias: jrasnick

@mco100  Thank you for the feedback, assigning this to the author for review.
If this involves a local configuration issues you will need to create a support ticket in the SQL Server forum.

@mco100 Thank you for your feedback. What version on SSMS are you using? Support for the new option in the Query Store UI should be visible in SSMS 18.4.
The "Custom" option is supported through the ALTER DATABASE syntax. Also see
SQL Server 2019 CTP3.0 Query Store Changes
Please let me know if you have further questions.

@mco100  Thank you for your feedback. I will proceed with closing this issue. If you have further questions the @ notification will continue to work even after an item is closed. We hope to hear from you again.

#please-close


Ability to decrease minimum queryAudioFile duration restriction?

I seem to have encountered a minimum duration for the queryAudioFile to find any matches.
Is this because of the fingerprintLengthInSeconds which appears to be 8192 / 5512f (~1,4 seconds)?
Is there a way to decrease this minimum duration? Or are there any other workarounds?

In order to create at least 1 fingerprint, the framework needs ~1.4 seconds (actually slightly more ~1.84 seconds for the first fingerprint due to FFT windowing). Getting around this limitation is not trivial.
Is there any particular reason why you would like to make it smaller than right now?

Ah alright, I guess 1.84 seconds is a decent duration length for almost all usecases. But I was requested to search for a track with a source query file of just 1 second.
Looking at the code I can understand it is nowhere near trivial to make adjustments, since everything seems to focus on the 5512 sample rate. I found another library for my usecase now though, called 'dejavu' (Python library).


Home Network Settings

Fixes: https://github.com/home-assistant/home-assistant-android/issues/30
Things left to do:

[ ] Better handling about what error is sending us to settings, currently to sensitive
[x] Validate that SSID checking is working (I don't think it is yet...)

Nice to see this PR - one question from an observer: will app be able to ignore 'home'/'remote'?
I have my router setup so it resolves external domain to my local IP when connected with home-wifi.
I'd like to see app not break things and be able to set just 'use one URL always'.
Just my 5 cents.

I too have a router that can handle it.  The ability to use a single URL will always work.

Just wanted to make sure.

It probably needs this to reload the webview if needed

Settings screenshot:

For the screenshot, let's call external url just Home Assistant url. Preferably there would be a new section with a toggle to "Enable different url when at home".

Or instead of toggle maybe when no ssid typed in we disable local url field.

Invalid url:

Disabled preference when no WiFi set:

🎉
Let's test this for a couple of days and do a new release soon.


HSV color picker UI widget

Objective

Bevy is lacking a way to pick colors interactively

Solution
It's very likely that my solution might not be the best approach, looking for input.
Iteration 1 video
https://github.com/bevyengine/bevy/assets/52322338/b8af2a45-b81e-450b-8e7f-c307b7bff20e
Iteration 2 video
https://github.com/bevyengine/bevy/assets/52322338/3b4c64bd-e276-4253-9d43-53a5a70e02b0

Added a marker
Example uses flex column
User must mark a relationship between wheel and box with a component

Description
The color picker is made out of two parts: The outer wheel (the "hue wheel") and the inner box (the "saturation-value box").
Each have their own shader used to display the colors to pick.
Interaction is done via relative cursor positions- which is why the split into two UI nodes was done. It made the math a lot simpler.
bevy_ui now sends events when:

A hue wheel is pressed
A saturation-value box is pressed

If the HueWheelSibling component is added to the box, the box will be kept in sync when the wheel hue changes.

Changelog
Added

Added HSV color pickers now usable via UI bundles
Added an example to showcase independent color pickers

Some thoughts after sleeping on it.
I think it's better for the user to explicitly add the wheel-box relationship via a component.
Something like
/// If this is added to a saturation-value box, the box will update automatically when
/// the related hue changes.
#[derive(Component)]
struct HueWheelSibling {
  /// The hue-wheel's entity
  sibling: entity
}

should then be added by end-users.
Right now, this is done implicitly when both the wheel and box share a parent (and fails otherwise).
So this relationship is required:
parent
   \--- wheel
   \--- box

so this forces a common parent node.
Also, what happens if:
parent
   \--- wheel
   \--- box1
   \--- box2

for example? It's not clear which one is implicitly linked to the wheel (or both, or none).
So later I'll make it explicit, which will also allow interesting use-cases such as placing the wheel and box entirely separately in the UI.

Updated the PR with the thoughts I wrote in previous comment. Updated description and added new video

Haven't looked at the actual code, but it seems a bit weird that changing the hue doesn't update the color and that there's nothing showing you the selected hue.
There's also the question of how well this color wheel works. Changing the hue on HSV can cause the saturation/value to change subtly (but not as badly as HSL), maybe something like oklab would be interesting so changing the hue works as expected? Not something that should block this PR if that would be an easy change later.

Haven't looked at the actual code, but it seems a bit weird that changing the hue doesn't update the color and that there's nothing showing you the selected hue.
There's also the question of how well this color wheel works. Changing the hue on HSV can cause the saturation/value to change subtly (but not as badly as HSL), maybe something like oklab would be interesting so changing the hue works as expected? Not something that should block this PR if that would be an easy change later.

Updated OP with new video, implemented both your suggestions about the updating via hue and added a hue marker.
I agree that HSV isn't perfect for all use cases.
What I'm thinking is that in the future users can spawn any variant they want, whether it be HSL or HSV or Oklab or whichever by just constructing the right bundle(s).
But initially since all image processing software and game engines I checked (Krita, Unity, Unreal, Godot iirc) have the ability to pick HSV, I think it's a decent place to start out.

When https://github.com/bevyengine/bevy/pull/9698 lands I can get rid of the hsv_to_rgb function.

I wasn't very fond of my implementation and I think with the many UI experiments and editor prototypes etc. coming to Bevy a cleaner more Bevy idiomatic approach can be found soon, so closing this out.


Fix actions version in README

Fix azure/login & azure/aks-set-context actions version in README.md

@microsoft-github-policy-service agree

Hi @jaiveerk @bfoley13
I realized I had not set up my GPG key earlier, so I've now configured it and signed the commit. Please merge it at your convenience.
Thank you!


Task 30

Bank balance message to user using throw

SourceCode/2023/Oct2023/Basics/Khantil Desai/Task 30/project.json
Hey there,
In reviewing the "Main.xaml" file in the "Task 30" folder, there's an issue with the code. There's a "ForEachRow" element that can't be created. This is probably because it's undefined or not supported in this current context.
To fix this, make sure to check that you're using the right libraries and packages supporting the "ForEachRow" type. You might need to update or install some packages.
Also, the project analysis shows that there are some workflows with errors. Please address these before further code reviews can take place.
Scores:

Code Completion: 1 (Since the code has errors which doesn't allow it to complete)
Execution: 1 (Since the existing issues might affect the overall execution)
Annotations and Comments: Not Applicable, unable to assess due to errors

Looking forward to seeing some cleanup and error-proof code for review. Thanks!

@Khantil12
Task -30
Code verified. Default activity names


Fixes an overflow issue in RadioListTile sample code

Related Issue

fix: #133142

Overview

wrapped an array of RadioListTile  in a SingleChildScrollView

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

https://github.com/flutter/flutter/issues/133142#issuecomment-1689998084


vh doesn't work properly in IE8

that black box is a <p> element with a height of 30vh.
This is what it looks like in IE9

Nevermind. I'm not even sure if I'm using this polyfill correctly...


Search Functionality: Ability search tech companies

Add search functionality to enhance the navigation the platform

I will pick this up asap @OSCA-Ado-Ekiti


Clarify documentation and include a bit more authentication/authorization helpers

This PR addresses my enhancement request #164.

+1 Thanks for the phenomenal contribution!


How are you handling the unbounded 360 scene?

Great work!!! I am wondering how you are handling the 360 scenes. Do you adopt the similar contraction space like mip-nerf 360 or just follow nerf++?

There is no contraction, in instant-ngp all space is handled equally,  that's why far space reconstruction quality is not as good as the other methods you mentioned. I plan to add a multi-sphere background model in the future.


Documentation: How to purge a packages state?

So I just ran into the issue of trying to do a force reinstall of gitlab (which brings in redis). I failed to find a command that would take care of purging all the state, should I have wanted to.
What I ended up with was:
$ rm -fR /var/lib/redis
$ rm -fR /var/gitlab
$ dropdb gitlab
$ dropuser gitlab

This seems far from perfect. Maybe I've just missed some documentation?

If anywhere, such functionality could be in the gitlab service, but I believe there's nothing general. I can't even see what such a general thing might look like.

I have no idea how this could look either. But maybe integrate with the garbage collection. E.g. allow to collect stateful garbage. This clearly needs to be marked dangerous though.
Yet for the gitlab case, not properly purging the state, results in either a broken gitlab instance, with weird error messages (e.g. pushing through ssh is broken). Or if one forgets to drop the user, the service won't start with a message that the ROLE already exists. One needs to make the mental leap from ROLE to postgres database roles to make sense of it.
I initially tried to drop gitlab from the configuration file, rebuild, re-add it and rebuild again hoping I would be presented with a clean slate. But the system was in an invalid state due to dirty state. And yes, state is something very annoying!
Maybe @fpletz has some idea esp. with respect to gitlab, yet this could be a more general theme I think.

In general I believe we add state to services only in those cases where you typically want to keep the state (i.e. persist across reboots and nixos version switches).

@vcunat certainly! Yet what happens to state that gets stale because the package that introduced that state was removed? Are you guaranteed that the state is going to work across versions even with multiple intermediate ones skipped?
This is probably getting even tricker as you have to keep track of the state introduced by each package (as future package might introduce different state, and won't be able to clean up state left behind by previous versions).
And you also run into the following issue:
Say version A introduces sate: [W,X,Z], and version B introduces state: [X, Y].
When going from A to B, would you want to have [W,Z] purged? If it's not used with B anymore, it could be considered garbage, I assume? This is certainly quite a hard thing to get right.

Better move this discussion to https://github.com/NixOS/nixpkgs/issues/7420 to have it in one place.


Add naming convention for maintenance branches

Signed-off-by: Pavol Loffay<EMAIL_ADDRESS>

Needs a rebase though.

why rebase?

Github was showing the message about conflict with base.


Expose events to facilitate manual ping/pong handling and tracking

Following the advice in #205, this rather trivial pull adds a ping and a pong event. Both events in their handlers pass in the received binary data. The ping event additionally adds cancel: a function taking no arguments that prevents the default behavior of the ping handler.

This is good, but the code should avoid emitting events or generating the cancel() function unless the user has added a listener for the ping event. If the user doesn't listen for the ping event, it should keep the old code path to maintain the previous performance and memory consumption characteristics.
You can watch the newListener and removeListener events on the WebSocketConnection object to maintain a connection-level pingListenerCount value, and then something like:
if (this._pingListenerCount > 0) {
  // emit the ping event.
}
else {
  // Just respond directly with a pong.
}

Good call. I'll modify my request within the next few hours.
To add on this, do you think it would be a good idea to modify the WebSocketConnection constructor to cache cancel with the connection instance? Something like this:
constructor:
...
this._pingCancelled = false;

var self = this;
this._cancelPing = function {
  self._cancelled = true;
}
...

processFrame:
...
if (this._pingListenerCount > 0) {
  this._pingCancelled = false;
  self.emit("ping", this._cancelPing, frame.binaryPayload);
  if (!this._pingCancelled)
    this.pong(frame.binaryPayload);
}
else {
  this.pong(frame.binaryPayload);
}
...

This would prevent the cancel from being generated every single time if a listener is present. But it will add an extra instance variable to WebSocketConnection, which could be ugly.

I don't really have a strong opinion about whether or not to cache it. I suppose it would technically be better to do so, since it would avoid generating a closure on every ping. I'm not certain it would make a significant difference in real-world usage though, unless you have thousands of simultaneously connected clients and are listening for the ping event in your app.
If you want to write the cached version, I'm fine with it.

I've updated the pull request to include the ping listener counter. I decided not to cache as it is probably best to keep it simple. Cache can be added later if it becomes necessary.


Boost program options not parsed?

Running the test case produces the following error:
./bin/Eulerian_Motion_Magnification test/test_baby.param
Error: Unable to open input video file:

It seems that the Boost program options are not read from the .param file. Any ideas why this might be?
I am running on Linux, Boost <IP_ADDRESS>

Tested on Linux machine with Boost version: 1.65.1 and it works. Closing this issue, if needed can be reopened later.


Add new domain

Provider is https://skiff.com/quick-alias and it's actually subdomains, each user can generate their own subdomain. I tested it, very easy.
The page title of https://skiff.com/quick-alias is "Quick alias burner email address". In the HTML I see
<meta name="description" content="Secure and quick-to-create burner email addresses with Skiff!

There is a browser plugin https://github.com/irazasyed/email-masker to create one email per website, skiff.com's twitter account promoted it, the github repository is tagged as 'burner-email'
You should add:

maskmy.id because it is there main domain
anything.maskmy.id because it allows you to create disposable addresses with random subdomains

@7c


EDM-177: ResourceSync overwrites fleet status on sync

When the ResourceSync task updates the fleet spec, it should nil out some fields, just like the code in internal/service/fleet.go does
For CreateOrUpdate, we should always nil out the status.  This applies to other resources as well.

Needs rebase

@oglok Done


Can't interpret statement on Macro

https://github.com/acemod/ACE3/blob/c9ad92e92d26f929e3cb78a53743585e5ffa20d8/addons/medical_gui/functions/fnc_collectActions3D.sqf#L20-L24
The interesting thing here is that the first 5 work fine. And although they all do the same. The last one fails.

Same here: https://github.com/acemod/ACE3/blob/c9ad92e92d26f929e3cb78a53743585e5ffa20d8/addons/medical_gui/functions/fnc_updateUIInfo.sqf#L27
But this time only LeftArm/RightArm don't work. And they are in the middle of the array.
Ohh interesting. If I change
ELSTRING(medical_treatment,LeftArm) ,ELSTRING(medical_treatment,RightArm) , to
ELSTRING(medical_treatment,LeftArm), ELSTRING(medical_treatment,RightArm),
The error goes away.
Same
https://github.com/acemod/ACE3/blob/c9ad92e92d26f929e3cb78a53743585e5ffa20d8/addons/medical_treatment/functions/fnc_findMostEffectiveWound.sqf#L48

Again. It's the space after the ) that causes it. Changing
EGVAR(medical_damage,woundClassNames) select to
EGVAR(medical_damage,woundClassNames)select
fixes it here.
https://github.com/acemod/ACE3/blob/c9ad92e92d26f929e3cb78a53743585e5ffa20d8/addons/medical_treatment/functions/fnc_handleBandageOpening.sqf#L89

No spaces involved here. Adding them changes nothing.

Yup kinda same here, but got IndexError: list index out of range.
Line is : [_args, {CALLM(gStimulusManager, "postMethodAsync", _this);}] remoteExecCall["call", 0, false];

If someone is able to fix that, I take it!


Digitised content: download options

Who it's for
People who want to do something with our digitised content off of our site.
Problem to be solved
We don't really know which file formats and types of things people would find most helpful to download. Research needed!
Details and user stories to be filled in later - these are merely notes for now
Single images:

full size / large
small size / 760px - this is the only pixel dimension we can know

Multiple images:

whole work (PDF) - currently in UV contains cover sheet with bibliographic citation info
raw text (TXT)
selected images (JPG)

MOH reports:

all the above plus:
whole borough collections as ZIP
CSV of all tables / select tables
raw text of some or all

Questions

Analytics #4076
ways of collecting and filing data on personal devices
download whole work as... ?
downloading single images in a multi-image work?

User Story/Job

In order to
(why? accomplish a goal/get a benefit)
As a
(who? user/persona)
I need/want/expect
(what? to do this thing)
Acceptance Criteria

[ ] The interface should do this thing
[ ] and this thing
[ ] and this thing.

May have insights in Aurelius

What are the insights?
Do we know enough? What else do we want to find out?

@jennpb  All comments now in Aurelius and insights made with supporting statements.


Fix issues with heart rate adjusted recent efforts for running

When displaying heart rate adjusted recent efforts for running, some issues were introduced in last fixes.
First fix handles running data which have has_watts=false, but still have avg_watts present. This has happened on one recent activity of mine.
Seconds fix is more important: Initializing values made inspections disapeared in the IDE, but safeMin / safeMax were not unable to handle null values properly, they expected undefined ones.
This has caused issues when oldest efforts did not contain HR data.

One of the fixes is wrong. Retracting PR.


Use Alpine image instead of Slim-Bullseye

Is your feature request related to a problem? Please describe.
Alpine image is popular thanks to its lightweight and having the bare minimum required Linux to run. I found several Dockerfile still using the Debian Bullseye Slim image. It's just a size issue.
Describe the solution you'd like
By using Alpine, we can save a minimum of 30% of the image size.
Describe alternatives you've considered
undefined
Additional context
Reference: https://dev.to/mohammadfaisal/how-i-reduced-docker-image-size-from-143-gb-to-224-mb-53nc

OH, I found out that Alpine image uses musl libc instead of glibc and it may cause compatibility issues with certain Rust crates. Closing it as not planned.

Moved to #68


Explain how to secure websockets with TLS.

Oh I see, these are just examples for the doc :)
So yes of course then, go for f-strings at any rate !
Thanks !


I accidentally shipped 1.0a6 instead of 0.1a6

This is bad because it means anyone who tries to install the latest alpha will always get that version.

I'm going to yank the release from PyPI and ship a new 0.1a6 release.

No, it's OK - I shipped 0.1a6 - it's only the title on the releases page that is incorrect.
https://github.com/datasette/datasette-enrichments/blob/e027ea29ee0ad0dd08551ff0b1410cccc4dd551a/setup.py#L4

Fixed: https://github.com/datasette/datasette-enrichments/releases/tag/0.1a6


CMakeLists.txt update to remove unnecessary variable

Remove unnecessary variable : MIVisionX_LIBRARIES_DIRS
Update rocAL CMake to exclude rocAL_pybind subdirectory if manually turned off

Closing this PR and reopening with develop branch synced


LUN-253: Change discipline item onPress behavior

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword LUN.
Reopened #235

@SteffiStuffel

Tested, does not work as expected. I though the color should change when to blue "onPressIn" and the navigation should start when "onPressOut"?

I chose this behavior after all because the behavior when attempting to scroll was really weird. If you liked the other behavior better, I could just revert my last commit. Please try both and let me know.

Check out this:
    <Container       onLongPress={() => setPressed(true)}       delayLongPress={20}       pressed={pressed}       onPressOut={() => {         if (pressed) {           setPressed(false)           onPress()         }       }}>
I think this is what we want.

Check out this:
    <Container
      onLongPress={() => setPressed(true)}
      delayLongPress={20}
      pressed={pressed}
      onPressOut={() => {
        if (pressed) {
          setPressed(false)
          onPress()
        }
      }}>

I think this is what we want.

Does not really work for me :( Scrolling triggers a navigation now and very short presses are not handled.

Check out this:
    <Container
      onLongPress={() => setPressed(true)}
      delayLongPress={20}
      pressed={pressed}
      onPressOut={() => {
        if (pressed) {
          setPressed(false)
          onPress()
        }
      }}>

I think this is what we want.

Does not really work for me :( Scrolling triggers a navigation now and very short presses are not handled.

If that is not enough we need to listen to scroll event and cancel click event if scrolled.

I think if we change the scroll/click behaviour we should do it, as it should be and no "quick fix"

Sure, agreed, but please tell me how it should be then because honestly I don't know. The current solution is imo the best I tried yet and not really a hack. However, I am open to try different things if you tell me what exactly you want, but right now I have no idea how to make it better. There is also the solution without my last commit if you like that better. Your proposal above does not work because of several things as mentioned above. Things to consider in a solution:

Scrolling should continue to work, i.e. it should not navigate to a discipline (with or without triggering a color change)
Short presses should continue to work, no matter how short the press duration is
Long presses can or can not be handled depending on preference

If it is okay for you I'd also do adjustments in a separate PR to avoid more merge conflicts...

I think if we change the scroll/click behaviour we should do it, as it should be and no "quick fix"

Sure, agreed, but please tell me how it should be then because honestly I don't know. The current solution is imo the best I tried yet and not really a hack. However, I am open to try different things if you tell me what exactly you want, but right now I have no idea how to make it better. There is also the solution without my last commit if you like that better. Your proposal above does not work because of several things as mentioned above. Things to consider in a solution:

Scrolling should continue to work, i.e. it should not navigate to a discipline (with or without triggering a color change)
Short presses should continue to work, no matter how short the press duration is
Long presses can or can not be handled depending on preference

Isn't on the current main just the behaviour we want?

Here is a working solution for the HomeScreen, nothing finished to merge, just to show how we can achieve the desired behaviour:
https://github.com/digitalfabrik/lunes-app/pull/247

If it is okay for you I'd also do adjustments in a separate PR to avoid more merge conflicts

I don't think it makes sense to merge this, as it is not the changes / behaviour we want.

@SteffiStuffel just tried your approach and while it works fine, the only difference I am experiencing in behavior is that long presses do not lead to a changing of the background color in my solution and the timeout is different. Am I missing something here?
If these two things are your reason for requesting changes here I can change both of these things. Since your approach is much more complicated imo (using refs, handling behavior in parent component/scroll view, using multiple callbacks) I'd like to stick to mine. Just let me know what exactly my solution is lacking and I will try to come up with a solution. Just saying it "is not the behavior we want" is not very clear :see_no_evil:
Apart from that, I think we should discuss the long press behavior again since I am not really sure how much intuitive it is to give the user visual feedback on long press and then do nothing.

Sorry for not being clear enough here, I thought the previous discussions make this clear.
The wanted behaviour is actually what many other apps also do, e.g. Android system settings or youtube app. This is also the behaviour the TouchableHighlight or TouchableOpacity of RN have for changing styling.

When clicking on an item = onClickIn: Color changes
When release the click = onClickOut: The navigation starts and the item stays dark until the navigation is finished.
While the item is clicked/touched the color is changed = dark
When clicking on an item (color should change) and scroll afterwards (color should change back to light)
When scrolling the color should not change, but it is not always possible, as in the moment a users clicks on an item, we do not know if this is to start a scroll or if it stays a simple onClick-event. Therefore we should set a timeout which is a good middle course.

Currently the solution does not fulfill 1 and 3.
The other (previous) does not fulfill 2 and 5.
I'm fine with other (more simple) solutions as mine, also this was only for demonstration purpose, no clean code that could/should be merged.


[SPARK-42496][CONNECT][DOCS] Adding Spark Connect to the Spark 3.4 documentation

What changes were proposed in this pull request?
Adding a Spark Connect overview page to the Spark 3.4 documentation and a short section on the Spark overview page with a link to it.

Why are the changes needed?
The first version of Spark Connect is released as part of Spark 3.4.0 and this adds an overview for it to the documentation.

Does this PR introduce any user-facing change?
Yes, the user facing documentation is updated.

How was this patch tested?
Built the doc website locally and tested the pages.
SKIP_SCALADOC=1 SKIP_RDOC=1 bundle exec jekyll build

index.html

spark-connect-overview.html

Merged to master and branch-3.4.


Error with HttpTrigger, "The maximum message size quota for incoming messages (65536) has been exceeded."

I'm getting an error when running local version of AF project via VS 2015 tooling. When I POST a body greater than 65536 bytes to a HttpTrigger it throws an error. Is there a way for me to set the MaxReceivedMessageSize property to circumvent this error?
Repro steps
Provide the steps required to reproduce the problem

POST body greater than 65536 bytes to HttpTrigger

Expected behavior
Not error
Actual behavior
Error:
Microsoft.Azure.WebJobs.Host: Exception binding parameter 'req'. System.ServiceModel: The maximum message size quota for incoming messages (65536) has been exceeded. To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element

Known workarounds
N/A
Related information
Provide any related information

Using f# & HttpTrigger

Warmest regards,
Garrard.

In our last release (completed yesterday) we increased the max request length to 100MB. See the release notes here: https://github.com/Azure/azure-webjobs-sdk-script/releases/tag/v1.0.10826. Can you confirm you're running the latest version?

Hi @mathewc, I'm running 1.0.10774.0 locally. I wouldn't know how to get the latest version installed locally.  I'm assuming I'd have to wait for an CLI update?

Yes, see https://github.com/Azure/azure-webjobs-sdk-script/issues/1063 which is discussing that CLI issue

Closing since this is tracked by the next CLI release


[Question] Which parameters to change when increasing image size?

Hi,
I am trying to replicate the same model but for the 500x500 version in the paper.
Apart from the input image_shape, and the priors, what other parameters need to be changed?
I am getting an error like this when running fit_generator
InvalidArgumentError: Incompatible shapes: [16,7308,4] vs. [16,28461,4]
	 [[Node: sub_1 = Sub[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/gpu:0"](strided_slice_20, strided_slice_21)]]
	 [[Node: mul_11/_375 = _Recv[client_terminated=false, recv_device="/job:localhost/replica:0/task:0/cpu:0", send_device="/job:localhost/replica:0/task:0/gpu:0", send_device_incarnation=1, tensor_name="edge_5128_mul_11", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"]()]]

I tried seeing if there is anything hard-coded in the SSD300 object or generators, but perhaps I do not see it.
Your advice would be appreciated! :)
For the new priors, I am using https://gist.github.com/codingPingjun/aa54be7993ca6b2d484cccf5a2c5c3d4 but with 500x500 size.

@fferroni could you, please, provide more information about the error? E.g. what is your model.summary() and what do you get after BBoxUtility.assign_boxes(...)? I mean, what tensor has shape [16,7308,4] and what - [16,28461,4]?

Right. The shape of the y where y = bboxutility.assign_boxes(y) is (7308,14). whereas (None, 20073, 14) is the size of the final layer if I use input_shape = (500,500,3).
I am a bit confused though because as far as I can tell, the bboxutility is using the tuple input_shape, which I have modified accordingly...

I have the same problem with changing image size, no matter which prior_box to use. Could please help and give hint @rykov8
thanks in advance

One problem with changing the image size is that you will not be able to load the pre-trained weights. Also you would need to change the ground truth prior boxes, the assign_boxes method in the bounding box utility function, and the PriorBoxes layers. It might be easier to resize your images using any image_resize function to 300 x 300.

I believe the biggest problem for having a flexible PriorBox implementation is mostly related to this line in the python implementation which should really be like this including the lines below it.
Does anyone know how to implement this with the matrix math that's being used in PriorBox? Or have anyone seen any similar implementations? @oarriaga @rykov8 Do you have any pointers?

@NegatioN I don't see any problem here. My code assumes, that there can be only one possible min_size for prior, that is true for author's architectures. So, in their Caffe code min_sizes_.size() is always 0. PriorBox layer is not implemented from scratch, it is based on the original one, but I replaced cycles, as they are slow in python.
@fferroni @lantuzi I believe, your problem is that you use old priors to initialize BBoxUtility class. After you change the net architecture, you need to take priors, generated by the new net and pass it to the BBoxUtility during initialization.

@rykov8 yes, it works perfectly in the direct implementation you have now. Thanks for making it :)
min_sizes_.size() is always 0? So you're saying it becomes 1 because of one iteration of this line?
Wouldn't it often be 1(min_size.size()) + 1(max_size.size()) = num_priors_? Only the upper-most SSD prediction layer in your implementation has one of those set, but not the other. Maybe that's captured by your *2 here?
I'm trying to reimplement the most recent version of this paper with some basis in parts of the code you have written, as I don't understand the PriorBox layers 100%. However, as far as I understand it now the number of priorboxes I generate in the network should depend on three variables: conv_layer shape, num_max_size, num_min_size.
How can I scale the number of PriorBoxes to fit the 8732 params required for the most recent version of the paper without allowing the implementation to depend on all of those three variables? Since it in your implementation is locked to conv_layer_x * conv_layer_y * 1 it doesn't seem to be flexible enough? And then after this the cascading effect of having to change the matrix math implementation would follow.
Maybe I've missed something glaringly obvious, in which case I would love if you (or anyone else) pointed it out :)

Hello @NegatioN,
I am currently also working on implementing the "recent" version of SSD, as well as trying to incorporate smaller models. As far as I can tell from the original SSD code the authors do not seem to follow explicitly equation 4 from the latest version of the paper in their implementation. However, it is mentioned there, that every PriorBox layer contains a scale sk (calculated using eq. 4) which is used along with the aspect_ratios the equations found  below eq. 4 for the centers, widths and heights of the prior boxes in order to construct all the prior boxes for every layer. Therefore if I understand correctly

How can I scale the number of PriorBoxes to fit the 8732 params required for the most recent version of the paper without allowing the implementation to depend on all of those three variables?
We should probably follow eq. 4 for the scales, along with the aspect ratios and the equations for the box widths and heights and consequently it does depend on all the variables you mention.

@rykov8 Thanks, I use this script https://gist.github.com/codingPingjun/aa54be7993ca6b2d484cccf5a2c5c3d4 to generate new prior boxes with a new image size. Probably the box_configs need changing too?

@fferroni  if you use the first layers of a pre-trained network and manage to connect it to the model here with PriorBoxes layers then yes, you shouldn't change the PriorBox layer. The PriorBox layer would only need to be changed when we change the prior_boxes.

I am also trying to run SSD500, and I'm facing similar problems. I don't think previous responses here are very clear about exactly what needs to change to get it to work. As fferroni states, just changing the input resolution to 500x500 changes the output dimension to 20073. First of all, is this correct? As in, is it possible to make changes elsewhere (in the prior boxes fed into the BBoxUtility constructor, for example) to make the ground truth also be of dimension 20073? Or is the output dimension wrong, and something (the PriorBox layer?) needs to be changed to get back to the original dimension of 7308?  One of oarriaga's previous answers seem to imply the latter, but I'm not sure I interpret it correctly.

Well, instinctively I would say that one needs to change the prior box fed
into the bbox utility. Increasing the size of the input image for a fixed
convolutipnal stack yields output larger tensor. This means more prior
boxes. I guess the benefit of having a larger size is indeed more prior
boxes to correctly pinpoint an objects location. The script i attached to
create a new prior boxes pickle (wich I found elsewhere) does not yield a
larger tensor when increasing the input size so I think this needs to be
changed accordingly. I was planning on doing this this weekend but maybe
you can also try
On 10 Mar 2017 14:41, "ahrnbom"<EMAIL_ADDRESS>wrote:

I am also trying to run SSD500, and I'm facing similar problems. I don't
think previous responses here are very clear about exactly what needs to
change to get it to work. As fferroni states, just changing the input
resolution to 500x500 changes the output dimension to 20073. First of all,
is this correct? As in, is it possible to make changes elsewhere (in the
prior boxes fed into the BBoxUtility constructor, for example) to make the
ground truth also be of dimension 20073? Or is the output dimension wrong,
and something (the PriorBox layer?) needs to be changed to get back to the
original dimension of 7308? One of oarriaga's previous answers seem to
imply the latter, but I'm not sure I interpret it correctly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rykov8/ssd_keras/issues/36#issuecomment-285671391,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APkjEum0fe-ELk9s7ZYECq1MC2sPYEXEks5rkVMWgaJpZM4L-Ij3
.

I believe I have made the network model for SSD512. I can at least build this model, so it seems to work, seemingly without modifying the PriorBox layer class. So that's promising. Feel free to use this. It contains a main program that just builds the model and creates a visualization, showing that at the very least the input/output sizes match and the model is possible to build.
ssd512.py.zip

no need for a new pickle file see https://github.com/rykov8/ssd_keras/issues/52

@tachim There is no need for a new pickle file if you want to keep the same number of bounding boxes compared to the 300x300. But in the paper, for the larger image size, they have many more bounding box priors...
@ahrnbom Thanks! Did you based the box_configs on the Cafe implementation?

@ahrnbom Thank you a lot! I have a question about your model
at line 155 of ssd512, you define num_priors = 4, but the original ssd300 has num_priors = 3. I am wondering whether it is correct or not. Here is the program slice:
    net['conv9_2_mbox_priorbox'] = priorbox(net['conv9_2'])
    # Prediction from pool6
    num_priors = 4
    x = Dense(num_priors * 4, name='pool6_mbox_loc_flat')(net['pool6'])

I am not sure whether I got it correctly. If you can offer me a reference about the net structure, it will help a lot!
Best


pull request for explicit development example

Hey bro, what about an explicit example for noobs such as myself?

I really appreciate this but as I mentioned in the issue I was already in the middle of adding something similar to what you have, so I will be closing this :) Changes are in 05e6705.


chore: Set permissions for GitHub actions

Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much.

Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions
https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs
Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests
Signed-off-by: nathannaveen<EMAIL_ADDRESS>

Thank you for the PR @nathannaveen. I don't think we should add this as it's unnecessary in our case. We don't have any secrets usage in our workflows. I will let another maintainer confirm before closing.

Sounds good, Thanks.


[Dialog][Accessibility] NVDA screen reader announces DialogTitle component as "clickable"

We are using the Dialog from React material ui components. We’ve been hit with an accessibility violation  because NVDA screen reader detects all the elements inside the DialogTitle component to be clickable and announces them as such. This should not happen as there are no click events bound to the component.

This should not happen as there are no click events bound to the component.

There's a click event bound to the parent container but we ignore every click event coming from within the dialog. Even if we explicitly give the container a presentational role NVDA still announces children as clickable.
While I appreciate NVDA patching inaccessible pages with this logic it hurts us in this case. We need this click handler for some features. NVDA should not announce elements as clickable if the parent with the click handler has a presentational role. I'll propose this change to NVDA and see what we can do.

I'm not sure if that would be the issue. I have been testing the Dialog component (material UI core version 4.9.2)  and apart from announce the title as clickable, the user get stuck and can't continue navigating the Dialog without press the enter key. On all times the NVDA announce the title, as it was described on issue https://github.com/mui-org/material-ui/issues/17999
Also, I suggest to reconsider putting the initial focus on the entire Dialog, this way we can be sure that all content it's being read. If this approach is followed, the wrapper of the Dialog should have a role dialog, the element having the initial focus should have a role document. This approach works well not only on NVDA.
If that approach can't be implemente, the at least this pattern should be consider: https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/dialog.html


Processing ODF files, new light time corrections

Features:

Reading and processing data from ODF files
Simulation of 2/3-way DSN Doppler observations
Additional light time corrections (troposphere, ionosphere, solar corona)
Reading DSN weather and atmosphere correction files
Added support for light-time iterations over multiple legs
Various bug fixes

All unit tests passing except the ones mentioned in: https://github.com/tudat-team/tudat/issues/143

I've made a couple of small modifications to the code, and pushed them here:
https://github.com/tudat-team/tudat/tree/feature/miguel_develop_merge
All the tests pass on Azure on all operating systems, but I suggest we wait with merging until after the holidays

Awesome to see this merged! 😁

And many thanks to you for developing it!!! I've been working on modifying some related stuff (observation dependent variables, residual calculation and storage, observation filtering), to make the next steps of applying the code and identifying remaining points of attention easier.
I hope you're doing well!