Wrong last order time

For example, closing time is 22:00, delivery time is 45 minutes, last order time is 10 minutes, the customers are supposed to be able to place an order before 21:50, but actually the system doesn't allow customers to order after 21:15.
Version:
v3.0.4.beta.20.1

Use issues to report bugs, please start a discussion on the forums or better still search the forums for existing solutions.
If you strongly believe this is a bug, then create a new issue using the ISSUE TEMPLATE. The template is only there to help us spend reasonable time understanding your issue and finding a solution 😃.


Issue Fixed #7080

Issue Reference
Issue Fixed #7080

@akhtarkhan1
This is working fine, please find the screenshot Here

Resolve conflicts

@akhtarkhan1
Now, this issue is fixed. Please find the screenshot Here


Generating a video thumbnail?

Does anyone have ideas for how to generate a thumbnail of the video being recorded?
I'm trying to Camera.constants.CaptureMode.still as an option into the capture() instance method (as such capture([Camera.constants.CaptureMode.still]), but nothing is happening (the docs specify that it takes options, but also says the arg is just callback, so I'm not clear on this point).
Any ideas?

Nevermind, seems like the docs specify capture([options]), but should be capture({options})...
So capture({mode: Camera.constants.CaptureMode.still}) I believe is working (but I haven't finished yet).

@getnashty were you able to figure out how to get a thumbnail from the captured video? From the docs it seems like if you pass mode to options the camera will capture a still instead of a video.

hi @bsiddiqui - I did figure this out. The way I did it, was unfortunately hack-y. But because there is no video encoding going on before it hits the server, I had no other way of making a thumbnail.
So when someone starts recording, the first thing I do is take a picture, then immediately after start recording a video. So the video might miss a moment, but it works for this use-case.

@getnashty Something like this
  startRecording() {
    if (this.camera) {
      this.camera.capture()
        .then((data) => {
          console.log(data)
          this.camera.capture({mode: Camera.constants.CaptureMode.video})
            .then((data) => console.log(data))
            .catch(err => console.error(err));
        })
        .catch(err => console.error(err));
      this.setState({
        isRecording: true
      });
    }
  }

What about shutter sounds?

Is there a way to extract the thumbnail from a specific timecode in the video?

@GeoffreyPlitt you have to do that using a service on server side.

Nope, we're using react-native-video-processing which does it on the device.


may crash

function:htp_parse_authorization_basic
after "bstr_free(connp->in_tx->request_auth_username);" need to add "connp->in_tx->request_auth_username == NULL;"
Otherwise, it may cause crash

Should this be solved by https://github.com/OISF/libhtp/pull/367 ?

Let's continue discussion in PR if needed


Compute Engine Resource: Image Creation Time checks

Feature request to include Compute Engine resource checks, including Image Creation Time as a criteria to validate.
Idea is to have no VMs running that have an image >30 days. If one exists, produce finding.

@red2k18 Can you do a high level scoping of this work (is this a new scanner / updating an existing scanner / config validator rule)?

@GitJumpin can you describe in more detail the business use case you are trying to solve for? Is purely a 30 day old image file? Or would looking at image type or family more useful than just creation time?
e.g. example image / family
Image: ubuntu-1804-bionic-v20190813a
Image family: ubuntu-1804-lts

Hi @GitJumpin, please see @dekuhn's questions above. We will consider adding this, just want to make sure it is done right.

@GitJumpin we have not heard back from you in 2 weeks. Closing the issue for now. Please reopen and provide us more details about the business use case so we can consider how to best consider this feature request.
Thanks!


Prevent kubernetes auth from failing due to long running terraform apply as k8s auth token expires in 15 minutes (AWS caveat).

Prevent kubernetes auth from failing due to long running terraform apply as k8s auth token expires in 15 minutes (AWS caveat).
address Elastic Search timeouts...
│ Warning: Applied changes may be incomplete
│
│ The plan was created with the -target option in effect, so some changes requested in the configuration may
│ have been ignored and the output values may not be fully updated. Run the following command to verify that no
│ other changes are pending:
│     terraform plan
│
│ Note that the -target option is not suitable for routine use, and is provided only for exceptional situations
│ such as recovering from errors or mistakes, or when Terraform specifically suggests to use it as part of an
│ error message.
╵
╷
│ Error: Unauthorized
│
│   with module.es.data.kubernetes_secret.es_password,
│   on ../../modules/addons/elastic/main.tf line 52, in data "kubernetes_secret" "es_password":
│   52: data "kubernetes_secret" "es_password" {
│
╵
╷
│ Error: Unauthorized
│
│   with module.es.data.kubernetes_secret.es_cacert,
│   on ../../modules/addons/elastic/main.tf line 60, in data "kubernetes_secret" "es_cacert":
│   60: data "kubernetes_secret" "es_cacert" {
│
╵
╷
│ Error: Unauthorized
│
│   with module.es.data.kubernetes_service.es,
│   on ../../modules/addons/elastic/main.tf line 69, in data "kubernetes_service" "es":
│   69: data "kubernetes_service" "es" {
│
╵
make: *** [tsb_mp] Error 1

@smarunich Have you checked this article related to the same issue.
https://fixit-xdu.medium.com/debug-eks-unauthenticated-error-2d21dcc8f54

thank you @sreeharikmarar you let me review the actual module configuration that actually had a miss and relied on kubectl provider to initialize kubernetes provider which has stopped working and the existing kubectl module is not maintained anymore


[PORT] Add interdependencies graph to readme

Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/3921

Current graph is visible here
The build is here
Azure blob storage is here. Once all is final, we probably want to move it to a different subscription.

Closed as we're tracking via #2318


docker image

please create a Docker image with the dependency-track deployed

A dockerfile already exists, but I do plan on making an official release of it to Docker Hub

@stevespringett do you have the Dockerfile published somewhere?

@MichaelGissingNC I plan on changing the dockerfile a bit and publishing it to dockerhub once beta's of 3.0 are available in the fall.

Once RC's are available, I'll start publishing containers to https://hub.docker.com/r/owasp/dependency-track/

:+1:  I don't have a Java build environment, but I can get a Docker image running.

Snapshot releases are now being continuously delivered (via CI) to https://hub.docker.com/r/owasp/dependency-track/
The projects README has been updated with instructions on how to use the image.
https://twitter.com/DependencyTrack/status/960730100777082880


Issue templates typos

Description
The command for checking out and creating a branch was incorrect an issue template. Additionally, there were minor typos in other templates.
Type of change
Please select everything applicable. Please, do not delete any lines.

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

Issue

[ ] Is this related to a specific issue? If so, please specify:

Checklist:

[x] This PR is up to date with the development branch, and merge conflicts have been resolved
[ ] I have executed npm run lint and resolved any outstanding errors. Most issues can be solved by executing npm run format
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new warnings

Good catch Eric, thanks.


Fixed a bug where it found my localhost:80 somehow and returned parsed HTML

there was a crash, and i realized it'd parsed my localhost :) so I patched in a simple bypass.

Too soon. fixed the underlying problem with a new pull.


Scripts with hexadecimal names not executing without prefixing them with a path

Steps to reproduce
Put a script file name 0x.ps1 in your $env:path directory, like C:\scripts\.
Try to call the script:
PS C:\> 0x.ps1

Expected behavior
The script should execute

Actual behavior
The script is not executed. No output is produced and I'm back at the command prompt.

If I prefix the script name with its path or rename it to something that does not look like a hex digit (i.e. "0xqqq.ps1" but not "0xffff1337.ps1"), it works as expected.
This also does not appear to happen with script files that only contain decimal numbers like "1234.ps1"

This works in Windows Powershell (PSVersion 5.1.21390.1) just fine.

Environment data

Name                           Value
----                           -----
PSVersion                      7.1.3
PSEdition                      Core
GitCommitId                    7.1.3
OS                             Microsoft Windows 10.0.21390
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

0x.ps1 will parse as the numeral literal 0x, then the property accessor . and property name ps1. All hexadecimal literals would work similarly; it gets parsed as a number, then a property is queried. The property doesn't exist, so the only result is $null.
This is by design, I think. A workaround is to use & and quote the command name:
& "0x.ps1"

I would never expect the script to be run if you just specify it as 0x.ps1'. PowerShell does not run scripts in the current working directory, no matter what the name. If you had typed 0x.ps1>tab>, Powershell helpfully prepends a path and runs .\0x.ps1`.
I think this is by design.

@doctordns it will work if the script is in a directory specified in $env:PATH as @1F916 mentions it is.

The same with 0b1.ps1 like names.

0x.ps1 will parse as the numeral literal 0x, then the property accessor . and property name ps1. All hexadecimal literals would work similarly; it gets parsed as a number, then a property is queried. The property doesn't exist, so the only result is $null.

The strange thing though is that it does work just fine with strictly decimal names like 1234.ps1. Also it worked fine in previous versions of PowerShell, so I would consider it a regression. I have a couple of scripts with similar naming that call each other like that and this new behavior breaks them in a - what I would consider - surprising way.

This (imo) inconsistent behavior between the handing of decimal numbers and hex/binary/exponential numbers also leads to other surprising behavior:
PS C:\> 0xb.equals(11)
True
PS C:\> 11.equals(0xb)
11.equals: The term '11.equals' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Also the behavior between the 0x and 0b prefixes is inconsistent when they are not followed by a number:
PS C:\> 0x.equals(0)
True
PS C:\> 0b.equals(0)
0b.equals: The term '0b.equals' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
PS C:\> 0.equals(0)
0.equals: The term '0.equals' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Consequently, if the script in my initial example was named 0b.ps1 (or 0.ps1), it would work as expected, i.e. as it worked before.

Sorry if i'm spamming here while I'm digging deeper, but another thing I discovered is that calling a script that is called 0GB.ps1 (or 10.GB etc) doesn't work either, similar as I lined out in my initial post. Interestingly this one doesn't work in Windows PowerShell 5.1 either.
Windows PowerShell 5.1 did have support for hex literals as well as KB/MB/GB/... suffixes, but not binary literals. So it doesn't really make sense to me why "0GB.ps1" works in neither Windows PS 5.1 and PS7, but "0x.ps1" works in Windows PS 5.1 but not PS7. 0.ps1 on the other hand works on both versions. 0b1.ps1 works in Windows PowerShell 5.1 but not PS7.
I think it would be nice if there was some consistency in the handling of number literals so as to minimize surprise, particularly in light of the other examples I posted above.
For a command line interpreter, I would generally expect (existing) file names to have precedence over accessing properties of some - but not all - number literals.

Thanks for digging a bit deeper here! Yeah, I agree, the fact that certain literals, especially binary (which has a similar prefix) seems to suggest that the hex tokenization is subtly broken.
Hard to say exactly how without a deep dive though, but I do agree this could and should be fixed.

Some time ago there used to be a problem invoking 7z.exe in PowerShell. You could not just type 7z a .....  You had to invoke it using & e.g. & 7z a ....  The team fixed that issue but as with most "fixes" there are unintended consequences.

The error occurs here:
https://github.com/PowerShell/PowerShell/blob/7cf1ef8c8599a90cd9579c7bb7b7676e097c4938/src/System.Management.Automation/engine/parser/tokenizer.cs#L3985-L3990
We append a 0 character to the hex string initially due to a complication in the way that it's parsed. I believe we rely on BigInteger's hexadecimal parsing, which parses as signed hexadecimal by default. Prefixing the 0 forces it to parse as effectively unsigned, or something like that.
As a result, the following if (sb.Length == 0) check will never be hit, it will always have at least length 1. This issue should be resolved if we update that check on line 3987 to if (sb.Length == 1). Probably worth adding a comment explaining why the check must differ from the binary one not far below.

WG: definitely something that could be addressed - marked up for grabs


fry config installer does not set the installer

I've been trying to set the fry installer to ruby-build, but it does not seem to work.
fry config installer ruby-build

fry config
usage: fry config <name> [<value>]

Available configuration:

    auto [on|off|1|0]         switch ruby on directory change
    prepend [on|off|1|0]      prepend ruby path when used
    path, rubies [<path>]     path where fry looks for rubies
    installer [<installer>]   switch ruby installer to use

Current configuration:
    Auto-Switch: off
    Prepend Path: off
    Path: /Users/jord/.rubies
    Installer:

Am I doing something wrong? Quite possible as I've just started using both fry and fish.

Do you have ruby-build installed?

I am creating a Dockerfile for the repository to be able to debug this more throughly. It should be the correct way to do it. But won't work without the binary available in path.

Yes.
$ type ruby-build
ruby-build is /usr/local/bin/ruby-build
$ which ruby-build
/usr/local/bin/ruby-build

Mine is installed in /usr/local. It's also in my PATH.
$ echo $PATH
/Users/jord/bin:/usr/local/share/npm/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin

Looks alright, should work. Could you provide the output from these to help me debugging?
set -U | grep fry
set -g | grep fry
set -l | grep fry
fish --version

Sure, the top three don't return anything.
$ set -U | grep fry
/Users/jord exited 1

$ set -g | grep fry
/Users/jord exited 1

$ set -l | grep fry
/Users/jord exited 1

$ fish --version
fish, version 2.1.2

Sorry, I've just realised that I was running under tmux. Without tmux I get this output.
$ set -U | grep fry
fry_auto_switch 0
fry_prepend_path 0
fry_rubies /Users/jord/.rubies

$ set -g | grep fry
fish_complete_path '/usr/local/Cellar/fry/HEAD/share/fry/completions'  '/Users/jord'…
fish_function_path '/usr/local/Cellar/fry/HEAD/share/fry/functions'  '/Users/jord/.'…
history 'set -U | grep fry'  'clear'  'c'  'fry config'  'fry config install ruby'…

$ set -l | grep fry

$ fish --version
fish, version 2.1.2

I wonder if it is because of tmux or you tried to do the fry configure installer ruby-build.
You could always try to set it manually, fry configure is bascially just a wrapper around set.
Try to do: set -U fry_installer ruby-build
If that doesn't work something is seriously wrong.

I think I have a fix for this:
https://github.com/terlar/fry/pull/40

It should be working now, otherwise reopen.

Sorry for the late response. I had trouble updating to the latest version using Homebrew. This is now working. Thank you :+1:


Normalize em-size for BlackBerry OS6

All browsers in the universe (that I know of) use a default em-size of 16px. The only exception to this rule is BlackBerry OS6 which uses different default font-sizes on different devices. I've seen 22px and even 17px. This causes serious layout issues in em-based layouts on these devices.
The way to solve this is to put the following code into the stylesheet
:root {
    font-size: 16px;
}

This will normalize the base font-size for all current and future browsers. It does remove the ability to adjust the font-size in the browser in IE9 though so you might want to put the code in a somewhat restricting mediaquery:
@media all and (max-width: 480px) {
    :root {
        font-size: 16px;
    }
}

thanks for the information, I am just wondering if this should fall under wiki or it shall be included in the css by default
@necolas do you think this is considered normalization?

That depends on whether you consider em-based layouts and em-based font-sizes to be the default. Some people don't, but I think people should, especially when working on responsive websites.


window.close() can't be used

window.close() don't used

What do you mean?

"window.close()" cannot be used
<EMAIL_ADDRESS>From: niu tech
Date: 2016-08-30 11:53
To: niutech/showModalDialog
CC: W65138497; Author
Subject: Re: [niutech/showModalDialog] window.close() don't used (#20)
What do you mean?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

No, but you can type parent.document.getElementsByTagName('dialog')[0].close(); to close the dialog from inside.

Yes, I did the same，Thanks！
<EMAIL_ADDRESS>From: niu tech
Date: 2016-08-31 06:57
To: niutech/showModalDialog
CC: W65138497; Author
Subject: Re: [niutech/showModalDialog] window.close() can't be used (#20)
No, but you can type parent.document.getElementsByTagName('dialog')[0].close(); to close the dialog from inside.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


drop old php versions

Q
A

Bug fix?
no

New feature?
no

BC breaks?
no

Deprecations?
no

Related tickets
-

Documentation
-

License
MIT

What's in this PR?
Remove old PHP versions.
Why?
HHVM is dead, and PHP < 7.1 are not maintained at all anymore.

Once this is merged, could we get another tag?

unless there are other open questions or things you noticed, i think we can release a new version, yes. did you try if things actually work with dns 1.0 in your setup? that would be good to know before we release.

I'm updating the project right now. Once we know for certain that it worked, I'll ping back on this PR.

We just finished testing, no issues reported!

awesome, thanks for the notification

https://github.com/php-http/react-adapter/releases/tag/2.3.0


The Robot Logger for Python does not log the Exception trace

consider this python code that occurs e.g. in a library:
def do_something():
  raise IOError('my error')

logger = logging.getLogger(__name__)

def do_something_else():
  try:
      do_something()
  except IOError:
      logger.exception('Catching error')

...
    @keyword()
    def my_keyword(self):
        do_something_else()

If I am executing the My Keyword in my testcase then the exception printed by logger.exception will only print out the immediate exception message Catching error but nothing about the traceback of this exception.
This is due to the fact that https://github.com/robotframework/robotframework/blob/master/src/robot/output/pyloggingconf.py#L62 is not considering the exc_info on the logging record.
The behaviour is different compared to the standard python logger that would log the exc_info and provides information about the traceback.
The use of logger.exception as in this example is the suggested way - afaik - in python to log exceptions. You would not add the original exception message to the message argument to logger.exception because - normally - this would lead to a duplication of error messages.
The robot logger however swallows this exception hierachy.
The expected behaviour is to contain the exc_info structure in the log output.

See also exc_info on https://docs.python.org/3/library/logging.html#logrecord-attributes

See also exc_info on https://docs.python.org/3/library/logging.html#logrecord-attributes

I can reproduce this. Adding the traceback into the message would be pretty easy. That changes the error to something like this:
[ ERROR ] Catching error
Traceback (most recent call last):
  File "/home/peke/Devel/robotframework/tmp/3828.py", line 10, in do_something_else
    do_something()
  File "/home/peke/Devel/robotframework/tmp/3828.py", line 4, in do_something
    raise IOError('my error')
OSError: my error


Scraper for Vodafone is not running and page show wrong number of jobs

ENVIRONMENT:
URL: https://admin.peviitor.ro/
Browser: Chrome
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:
Enter URL "https://admin.peviitor.ro/" in to the browser
Press ENTER
Select on the top bar "CONT" and click
Check and click on folder "based_scraper_py" and load all the scraper.
Check "vodafone.py" and click on label.
Return to " https://admin.peviitor.ro/"
Select "Vodafone" box and clcik on "Vizualizeaza joburi (130)"
Open page for "Vodafone" and check on chart for jobs.
EXPECTED RESULTS:
The page shows scraper is working / load, received confirmation of running
Chart show 130 jobs.
ACTUAL RESULTS:
After running scraper "vodafone.py" this return error
See below screenshot.

"vodafone.py" not running from 14.08.2024 according to chart.

Fixed....


Make index.ts command line only and wrap server functionality in a separate module

Right now index.ts is mixing up the command-line setup and spin-up the server. It would be nice to have a separate module to wrap the business logic and let index.ts to be called purely on command line. This will help writing test cases and include servers in other applications as well.

Close via #110


RuntimeError: expand(torch.FloatTensor{[1, 512, 1, 1]}, size=[512]): the number of sizes provided (1) must be greater or equal to the number of dimensions in the tensor (4)

when I ran  the code i got a mismatched error
RuntimeError: expand(torch.FloatTensor{[1, 512, 1, 1]}, size=[512]): the number of sizes provided (1) must be greater or equal to the number of dimensions in the tensor (4)
can you please guide me on how to resolve this

You can change the
original code:  my_embedding = torch.zeros(512)
to:  my_embedding = torch.zeros(1, 512, 1, 1)
Then, your problem will be solved.


Why is @kixxzy still a collaborator?

since i used to own the repo im a collab.

:trollface: Could I be a collaborator?


How to set default value for DATETIME type

I have tried to use
type: "DATETIME"
defaultsTo: new Date(), but it failed.
Is there an elegant way to set default value?

Now that functions in defaultsTo are deprecated, what's the right way to do this?
{
  my_time: {
    type: 'ref',
    columnType: 'datetime',
    defaultsTo: () => new Date() // Causes an error
  }
}

Note that the type 'ref' and columnType 'datetime' are the new way to do mysql datetime fields in Sails 1.0.


Duplicate viewport tag

Bug report
Describe the bug
viewport tag gets duplicated in the browser (there's no custom viewport tag provided).
To Reproduce
This occurs on our site, but I've noticed that nextns.org has the same issue, so the instructions are for it:

Go to https://nextjs.org
Wait for the page to load
Inspect the element tree
Search for "viewport", you'll see two occurrences

Expected behavior
There should only be one.
Screenshots

System information

OS: macOS
Browser (if applies): Chrome
Version of Next.js: 9.0.5

@Dremora It seems like the provided page https://nextjs.org doesn't show the issue (anymore?).
In my case, I had a duplicate viewport tag because I defined mine in _document.js instead of _app.js. It also had a key property. Moving it to _app.js and removing the key property solved the issue for me.

Solved by https://github.com/zeit/next.js/pull/8960


style: Fix dropdown icon partially visible on small screens.

The dropdown icon for direct messages is partially visible on small screens. This was due to removing padding when the screen size is below a certain size by media query.
This PR adds only the padding-left for left-sidebar so that the dropdown is clearly visible.
Screenshots and screen captures:
Before:

After:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

LGTM

I changed the CSS to just not set the left/right/top padding, which were already correct, and just adjust padding-top, and merged this, thanks @lakshaykananiya!


Invalid white space character in example xml

If you copy the example xml provided on the page into your xml file and then try and import your solution, you will be given import failures because the space character used in the example xml is invalid. I had to replace the space characters in the "appsetting uniquename" elements with a space for the xml to be valid and import to be successful.

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

ID: ececc5fc-3e34-b309-7717-298f19e58bc1
Version Independent ID: 98e26d51-846c-3f62-a185-f181ee073262
Content: Add a custom app module to the Field Service (Dynamics 365) mobile app
Content Source: ce/field-service/mobile-powerapp-copy-app-module.md
Service: dynamics-365-field-service
Sub-service: field-service-mobile
GitHub Login: @FieldServiceDave
Microsoft Alias: daclar

Hello Adam @adamgatt  - thank you for sharing the feedback and apologies for the delay in getting back to you.
I've published an updated to the example without non-breaking space.
Thanks!
Michael


refactor(dbm-services): 优化mysql上架代码

关联研发信息
dev_branch: refactor/optimization_install_mysql_code/#1309
target_branch: v1.2.0


[Event Change Request] Codeunit 8612 - Procedure InsertTemplate / Event OnInsertTemplateCaseElse

Hi,
Object: codeunit 8612 "Config. Template Management"
Event: OnInsertTemplateCaseElse
It would be nice to extend event OnInsertTemplateCaseElse in procedure InsertTemplate to be aware from which Record we are inserting related template. With this change, we would be able to define and insert data for different tables in which PK is dependent on source Config. Template Table.
For example, we can create one template for Fixed Asset and define a related template for Depreciation Book, and if we try that, currently it won't be possible since Depreciation Book PK contains Fixed Asset No., but if we extend the event with RecRef, we would have Fixed Asset No. and we will be able to create Depreciation Book together with Fixed Asset
For that case, I would suggest the following structure
Event call (new parameter added RecRef at the end):
OnInsertTemplateCaseElse(ConfigTemplateLine, ConfigTemplateHeader2, FieldRef, RecRef2, SkipFields, TempSkipField, RecRef);
Event declaration:
    [IntegrationEvent(false, false)]
    local procedure OnInsertTemplateCaseElse(var ConfigTemplateLine: Record "Config. Template Line"; var ConfigTemplateHeader: Record "Config. Template Header"; FldRef: FieldRef; var RecRef: RecordRef; SkipFields: Boolean; var TempSkipField: record Field; OldRecRef: RecordRef)
    begin
    end;

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.


Neoantigens from SNV

Dear developers of Pandora
Do you have any tips about modeling MHC-I 9mers  of mut/wt peptides derived from Single nucleotide variants?
I have the following case of study
mut peptide:CVRVSGQGL (validated immunogenic neoantigen therefore it is surely bound by MHC)
wt peptide:RVRVSGQGL (predicted binder with an IC50 of 24nM)
I believed that for this special case the mut and wt counterpart would have a quite similar modeled structure
Instead after modeling both peptides with PANDORA i noticed that the models are quite different.
In particular PANDORA uses  2 different templates (4U1K for wt; 41US for mut). The 2 pdbs have the same MHC and differ only for the 9mer bound into the pocket.
I guess that  4U1K has been preferred as template for the mut peptide because its 9mer peptide starts with Arg.
Is there a way to force the modeling of mut peptide by using exactly the same pdb used for wt?
thank you for any tip
Guido

Dear @GuidoLeoni, first of all, thanks a lot for using our software and contacting us!
For sure you can force pandora to use a template selected by you.
If you are using PANDORA's Python interface, you have to retrieve the template from the template database and pass it to the Pandora object, as shown in the example below:
`from PANDORA import Target, Template, Database
db = Database.load()
target = Target(id = MyMutCase', #or whatever ID you prefer
allele_type = 'HLA-A*0201', # or whatever MHC allele you are using
peptide = 'RVRVSGQGL,
)
Selece a template from the template database using its PDB ID
template = db.MHCI_data['4U1K']
Pass the template to the modelling function
case = Pandora.Pandora(target, db,  template=[template])
case.model()
`
Also, please make sure you select the lowest molpdf model generated from each run (by checking the output file molpdf_DOPE.tsv. Indeed, considering how similar the sequences are and that the mutation is before the first anchor (unless you think the anchor positions are different for some reason), the lowest energy structures should look very similar to each other.
Unfortunately, the manual template selection has not been implemented yet for the command line interface of PANDORA. If you are using our package from the command line, please let me know and I can add this feature for the next pre-release.
Please let me know if you have any further questions!


Unable to get it work with IE11

Hi, I have implemented the toasty as suggested in example and it not working in IE11. However, I was able to get it work on Firefox.
Is there something I have missed in configuring it properly. Please help.

Hi,
It definitely doesn't work with IE11. Is there any fix issue scheduled?
Thanks a lot

Hello, what's the error? Don't have the means to test on IE11 at the moment.

Hello,
Thanks for your answer
Actually when several events are dispatched sequentially, toasty messages
are not systematically displayed.
For instance :

(1) We click on the button. The first toasty message is displayed
(2) We click on the button. The second toasty message is NOT displayed
(3) We click on the button. The second toasty message is displayed
(4) We click on the button. The third toasty message is displayed
(5) We click on the button. The fourth AND the fifth toasty message are
displayed.

EDIT : we've found a solution for this display issue : by encapsulating the
push with $apply, it works each time :
scope.$apply(function () {
// Push up a new toast item
scope.toasty.push(toast);
});
Thibaut Grappin
(lu)  +352 661 447 682
(fr)   +336 84 37 07 15
On Fri, Mar 4, 2016 at 2:39 PM, Elliot Hesp<EMAIL_ADDRESS>wrote:

Hello, what's the error? Don't have the means to test on IE11 at the
moment.
—
Reply to this email directly or view it on GitHub
https://github.com/teamfa/angular-toasty/issues/10#issuecomment-192287175
.

@Krazymins does this fix all issues with the $apply?

Hi Ehesp,
Actually it came with another issue. Unfortunately sometimes we have a "$digest already in progress" message.
This stinks. So we rollbacked to the previous situation, and removed $apply(...)
We have been able to resolve it by using a $timeout :
$timeout(function () {
    // Push up a new toast item
    scope.toasty.push(toast);
});

It also works if the fix is in our own code, when we call this.toasty.error(...), instead of using the $timeout in the component code.
The issue is when several toasties with the same message are displayed, there can be display issues as explained above.
With the $timemout workaround, everything works perfectly, including on IE11.
It may not be the most beautiful way to resolve the issue, but it works as expected.
Thanks a lot.

I suspect the timeout is pushing it onto the next "tick". Can you make a PR for me with the update? I'll test it on Chrome and things.
Cheers

I seem to be having this issue in chrome, just calling toasty.success every 5 seconds with the same details. The $timeout workaround works for me too.


feat: Add oracle interface

Adds a publicly callable interface for downstream contracts to query the QGB contract for attestations.
Depends on #32
Tests will be done in a future PR.

Updated to use data roots instead of messages.

Should we add tests for this still?

Could, yes. But there are no tests at all for anything, so I'd prefer to write tests for the rest of the contract first in a separate PR (i.e. submitting new events), since the oracle interface can't be tested without things to test against.

Could, yes. But there are no tests at all for anything, so I'd prefer to write tests for the rest of the contract first in a separate PR (i.e. submitting new events), since the oracle interface can't be tested without things to test against.

I'd still prefer if this had tests. But I also see this PR isn't against master/main but against a dev/feature branch. So I'm OK with doing them in a followup PR (but before merging to main).

What if the bridge halts due to a loss of honest majority (for example, more than 1/3 of the nodes shut down). Then, is there some recovery mechanism for the bridge? For example, fall back to a previous configuration and continue running? Or allowing updating the validatore set without all the validatore signatures?
Or, it should start fresh with a new contract and disgarding all the history (ie the batches that have been committed to) ?
Thanks.

If they shut down permanently, then there's no way for the bridge to recover, since the bridge can't hard fork. A new QGB contract would have to be deployed with a new bridge genesis.


Feature Request: Tensorboard visualization of what parts of a given training image were deemed as 'important' after a inception v3 has been retrained

After retraining inception v3 on my own image set, I'm running into where any new image that I ask it to recognize, that shouldn't match any of the training categories, is confidently scored as one of the image categories.
For example, if I train it on two types of steering wheels that are exactly the same except one category/type has two buttons on the right. After training has finished, if I show inception an image of some other random thing, like a horse, it confidently scores it as one of the steering wheel categories!
The issue is that there is no way to get insight as to why this is happening. In other words, there is no way to tell that the model has correctly learned that the real difference between the two steering wheel categories is presence or absence of the the two buttons on the right. It would be extremely useful to be able to upload an image in tensorboard and have it show you a heat map, overlaid on the image, of what specific parts of the image the model deemed important when classifying it as a particular category.
To elaborate further, if you have two categories that you retrained inception on, you would be able to upload an image, and you would see different regions of the image highlighted using two different colors (one color per category). Then you would be able to clearly see that the model has or has not correctly learned the real difference between the images. In addition, you could upload a image that should not be classified as one of the two categories and you would be able to see why it incorrectly thought it was one of the two categories.

Since this is more of a machine learning research question (rather than a concrete bug or feature request), it really is better asked on StackOverflow. Thanks!


Fix version switcher

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>4:
0.0%

Covered Lines:
764

Relevant Lines:
764

💛  - Coveralls


Konnected issue with manual discovery

Home Assistant release with the issue:
0.93.2
Last working Home Assistant release (if known):
at least since 0.91
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
https://www.home-assistant.io/components/konnected/
Description of problem:
I have my konnected setup manually. I get the below errors in log whenever I restart HA. Despite this, the component works fine.
2019-05-25 10:33:49 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/__init__.py", line 143, in manual_discovery
    dev.get(CONF_PORT))
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/__init__.py", line 117, in setup_device
    discovered.setup()
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/__init__.py", line 280, in setup
    self.sync_device_config()
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/__init__.py", line 384, in sync_device_config
    if self.desired_settings_payload() != self.current_settings_payload():
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/konnected/__init__.py", line 364, in current_settings_payload
    settings = self.status['settings']

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
konnected:
  access_token: !secret konnected_token
  api_host: !secret hass_url
  devices:
    - id: !secret konnected_mac
      host: !secret konnected_host
      port: !secret konnected_port
      discovery: False
      binary_sensors:
        - zone: 1
          type: motion
        - zone: 2
          type: motion
        - zone: 3
          type: motion
        - zone: 4
          type: motion
        - zone: 5
          type: motion
        - zone: 6
          type: lock
      switches:
        - zone: out
          momentary: 500
          name: Alarm Toggle

Traceback (if applicable):
refer  above in description of problem
Additional information:

Update the Konnected firmware on the device:
https://help.konnected.io/support/solutions/articles/32000023470-flashing-konnected-firmware-software

Thanks updating fw from 2.2.4 to 2.2.7 did the trick


Fix errant capitalisation in DNS TXT response

The DNS TXT record response mislabels the cert expiry as NotAFter, instead of NotAfter,  I don't think this is intentional.
This patch could technically be a breaking change to peoples infrastructure.

 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.

Thanks for the PR - rebased in #1127.


Fixed issue with backdrop causing IOExecption and closing

The only change is if (requestId == 0 && parsed.has("responseType")) {.
Since the backdrop sends a update without the responseType, I use the IDE from OpenHab and it has default formatting enable. I do think the styling changes are to the better.

The only change is if (requestId == 0 && parsed.has("responseType")) {.

You mean around line 156 in Channel class, or where?

Since the backdrop sends a update without the responseType, I use the IDE from OpenHab and it has default formatting enable. I do think the styling changes are to the better.

I don't want to switch to other styling scheme. I don't see much sense here, and the switch should be done for all files at once for consistency purpose. Anyway, this is out of scope of changes declared in this PR. If you want to discuss it, then please create a separate thread on the issue tracker with your suggestions.


FR: Possibility to disable download, installation, & updates to the icons

I already handle the download, install & updates myself to the Adwaita-colors icon pack, along with MoreWaita.
I only want the functionality of changing the icons when accent color changes, nothing else.

The extension is able to download, install and update it alongside with MoreWaita setup for you. But I see what you mean, you don't want to be notified that you're not in the latest version of Adwaita-colors right? That is because right now the extension rely on self defined settings that stands the version of Adwaita-colors you have installed it doesn't know if was installed previously.
I was focusing on the ability of handle custom icons, now that it is mostly done I'm going to focus on that:
The extension will be able to understand if the icons are being manually manipulated (installed, updated) from the user or a package manager. Meanwhile, I will add the ability to the user to just disable notifications all at once, if desire.

This is how I see it.
System-installed icons:

/usr/share/icons/

Disable any possibility of downloading, installing & updating the icon pack when detected.

I would also disable checking for any new version of the icon pack & notifications by default in this scenario. Can be toggled back to enabled by the user if desired.

User-installed icons:

/usr/local/share/icons/

${HOME}/.local/share/icons/

Possibility to download, install & update icon pack, enabled by default. Would also consider setting this as optional if user uses something like Topgrade

Checking for new version & notifications enabled by default, but optional.

This is how I see it.

That's the idea I'm going for, but in near future. The extension will seek for where Adwaita-colors were installed and determine it's behavior.
For now, I shared a temporary fix for this in the new release, alongside with custom places auto-updating to reflect accent colors, it now provides a switch to toggle notifications.


Extended Error Info

When we notify an error to bugsnag using bugsnag.notify(error), by default it shows Error name, stack trace and message in Bugsnag App.
If the error is a custom Error (extended), which may include more info, that data is not visible anywhere (not sure if it's captured in the first place).
For example, consider following error class -
EError.js
module.exports = class EError extends Error {
    constructor (message, statusCode, details) {
        super(message);
        this.statusCode = statusCode || 500;
        this.details = details;
        this.name = "EError" + (statusCode ? ` (${statusCode})` : "");
    }
};

I have 2 additional properties statusCode and details, which I want to be included in Bugsnag error. If I pass the error (instanceof EError) to bugsnag notify, the extra properties are no where to be found in the captured Bugsnag error.
let details = { sess: "7e5c1c4a-11e3-41a2-a935-c1a0068e521b" };
let err = new EError("Bad Email Address", 400, details);
bugsnag.notify(err);

I tried pushing the err as metaData, even then the details and statusCode is no where to be found on bugsnag.
bugsnag.notify(err, { metaData: {err} });

Only message and name captured in metadata.
What can I do to capture more info about the error. Not just that this custom error class has more info, most of the libraries has custom error with more details where message would not be sufficient to debug error. E.g check Sequelize Unique Constraint Error, it has so many info which is just lost when captured on Bugsnag.
I'm currently on v6.2.0 of @bugsnag/node (using with NodeJS v8.11.1)

Hi @enVolt thanks for getting in touch. The approach we'd recommend taking here is to extract the value of each property from the Error object and add it to the MetaData directly. This would look quite similar to the approach you've already arrived it, just with the following change:
bugsnag.notify(err, { metaData: {statusCode: err.statusCode} });

Bugsnag doesn't serialise every value on extended Error objects as in JavaScript Error's properties are not enumerable, which means we'd need to check for each key individually when serialising a report.

Hi @fractalwrench, this is actually not feasible, as there are multiple types of extended error instance. and all include different type of information.
By the way, extra attributes of extended Error are actually enumerable. Please correct me if I misunderstood you.
class EError extends Error {
    constructor (message, statusCode, details) {
        super(message);
        this.statusCode = statusCode || 500;
        this.details = details;
        this.name = "EError" + (statusCode ? ` (${statusCode})` : "");
    }
};

let e = new EError("xyz", 400, {foo: "bar"});

console.log(Object.keys(e));  // [ 'statusCode', 'details', 'name' ]

If Bugsnag, doesn't enumerate over Error or extended Error, then one possible solution I can thinks of is this -
let errorInfo = { message: error.message }; // though already captured
if (Object.keys(error).length) {
    Object.keys(error).forEach(key => { errorInfo[key] = error[key]; });
}

bugsnag.notify(err, { metaData: {errorInfo} });

Whilst this is true

extra attributes of extended Error are actually enumerable

The built in attributes (name, message) are not – see the following examples:
> Object.keys(new Error('oops'))
[]
> JSON.stringify({ error: new Error('oops') })
'{"error":{}}'

Now, we could go poking around in our serialisation library once we've established an error is being serialised and loop over all its possible, additional enumberable keys (we'd have to use a for x in obj loop because we have to support IE8) but that library can easily mess up the entire notifier by being a) too slow, b) too big or c) (worst of all) error prone.
I think the best solution for you right now is to add a beforeSend callback which runs for every error and extracts what you want from the report.originalError (added in v6.1.0, not yet documented – I'll add a note to update that). We'll add a ticket to our internal roadmap to see if some of these custom error properties like details and statusCode are common enough that we should extract them into metadata of the report.
const bugsnagClient = bugsnag({
  apiKey: 'YOUR_API_KEY',
  beforeSend: report => {
    report.updateMetaData('error info', {
      details: report.originalError.details,
      statusCode: report.originalError.statusCode
    })
  }
})

Agree with @enVolt here, getting all the extra enumerable properties from the Error object should be the default and it shouldn't be complex or error prone. Knowing how to handle Error objects properly is something I would expect out of the box.

Hello there.
Is there any easy way to display extended error?

Hi @GuillaumeCisco - please could you expand a bit more on this please? Are you able to share a code snippet or a link to an event in your Bugsnag dashboard to demonstrate what you mean? Feel free to write into<EMAIL_ADDRESS>if you'd prefer 👍


Add legrand dimmable switch v2 handler

In order to handle the new software version of the same switch we need one more device handler

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 79.989%

Totals

Change from base Build<PHONE_NUMBER>:
0.008%

Covered Lines:
5940

Relevant Lines:
7426

💛  - Coveralls

Codecov Report
Base: 79.98% // Head: 79.98% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (6984b71) compared to base (2cd9f10).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev    #1804   +/-   ##
=======================================
  Coverage   79.98%   79.98%
=======================================
  Files         239      239
  Lines        7423     7426    +3
=======================================
+ Hits         5937     5940    +3
  Misses       1486     1486

Impacted Files
Coverage Δ

zhaquirks/legrand/dimmer.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Update application-cdc.yml

Changed AUSSDA setspec. See #439

The linked issue is cessda/cessda.cdc.versions#439.


Enhancement: Option to enable/disable the R reset button

From what I understand, this feature was disabled because people kept hitting it by accident when mashing buttons very intensely. However, I think the option to die instantly without having to go through a menu is a pretty convenient thing to have. So, I suggest it be brought back as soon as possible, either made toggleable through options or simply rebound to a safer key.
Also, if there are no plans to bring the blue balls button back, could someone tell me if there's a way to enable it for myself in the code? I'm really missing this feature, but I'm new at Haxe and I wasn't able to figure it out myself. Thanks.

on it

Also maybe an option to set it to either R or ~ because ~ is what people might be used to from osu

#490 done

Also maybe an option to set it to either R or ~ because ~ is what people might be used to from osu

we'll probably do that when we merge in week 7 shit

resolved by #490


Add composer repositories configuration

It is a PR for #36.
With this PR, it is possible to use fork, private or local repositories (local maybe not useful).
<<<CONFIG
repositories:
    - type: vcs
      url: https://github.com/fabpot/Pimple
packages:
    - "pimple/pimple: 1.0.2"

In the implementation, I would have preferred to use the CLI composer to add a repository but without composer.json, composer throws an exception.
composer config repositories.pimple vcs https://github.com/fabpot/Pimple
[RuntimeException]
No composer.json found in the current directory

With this PR, we generate a full composer.json wich is validated by composer. It will be easy to fix https://github.com/sensiolabs/melody/issues/4  by simply removing validatePackage and let composer do the job.

@jderusse This PR seems good to me, and you?

:+1:

Thanks for your work on this new feature!


Unable to Serve NOTICES File in Flutter Web App Deployed on IIS

I am encountering an issue when deploying a Flutter web application on IIS. The application fails to load the NOTICES file and shows the following error in the browser console:
Uncaught Error: Unable to load asset: "NOTICES".
The NOTICES file is present in the deployment folder, but it doesn't have any file extension. Since the file lacks an extension, IIS does not serve it correctly.
Environment
Flutter Version: 3.24v
Dart Version: 3.5.3
Operating System: Windows Server
IIS Version: 10.0.22621.1
Build Command: flutter clean & flutter build web

What I’ve Tried

Adding MIME types for files without extensions in IIS (Which IIS does not allow)
Created the web.config to include:

<staticContent>
    <mimeMap fileExtension="" mimeType="text/plain" />
</staticContent>

Renaming the NOTICES file to include an extension (e.g., NOTICES.txt), which failed as the main.dart.js still references the original file name.

Request
Please advise on how to handle extensionless files like NOTICES in a Flutter web app deployed on IIS. If this is a limitation of the current Flutter build process, it would be helpful to:
Provide a way to customize the file name or extension of the NOTICES file.
Document any IIS-specific deployment considerations for Flutter web apps.
Thank you for your help!

I don't have such web server (IIS) to give it a try now but will label this for team's input.

Document any IIS-specific deployment considerations for Flutter web apps.

This request should be tracked on website repository, please open an issue there.


Add onSendBlock methods

Goal
Add missing add/remove/clearOnSendBlock() methods to Bugsnag and BugsnagConfiguration.  These are used in this notifier in lieu of equivalent onError methods in others due to the tight requirements of code run in error handlers (e.g. no ObjC, async etc).

Design
Straightforward exposure of access to the BugsnagConfiguration onSendBlocks array.

Changeset

Bugsnag, BugsnagConfiguration and associated tests.

Some small non-functional rearrangement refactoring of headers has also been done.

Tests
Unit tests.  Not tested prior to start being called.

Review
Outstanding Questions

This pull request is ready for:

[ ] Initial review of the intended approach, not yet feature complete
[ ] Structural review of the classes, functions, and properties modified
[X] Final review

[ ] The correct target branch has been selected (master for fixes, next for
features)
[ ] Consistency across platforms for structures or concepts added or modified
[X] Consistency between the changeset and the goal stated above
[ ] Internal consistency with the rest of the library - is there any overlap between existing interfaces and any which have been added?
[ ] Usage friction - is the proposed change in usage cumbersome or complicated?
[ ] Performance and complexity - are there any cases of unexpected O(n^3) when iterating, recursing, flat mapping, etc?
[ ] Concurrency concerns - if components are accessed asynchronously, what issues will arise
[X] Thoroughness of added tests and any missing edge cases
[ ] Idiomatic use of the language

is this functionality defined anywhere in the notifier spec?

No, it's a divergence.  Due to the limitations of the environment during a crash (no async, or ObjC etc) we can't implement onError like the other notifiers.  onSend is the best we can do.  There is a separate task to document the divergence.

There is a separate task to document the divergence.

It would be preferable if the spec was up-to-date before we consider merging this PR.
Without a written specification that has been agreed upon, we run the risk of having to rework this interface or even scrap it entirely in favour of another solution. Documenting and scrutinising the requirements down beforehand reduces this risk.

Without a written specification that has been agreed upon, we run the risk of having to rework this interface or even scrap it entirely in favour of another solution. Documenting and scrutinising the requirements down beforehand reduces this risk.

I've raised an issue, but I'd seen this more of a rename to get it more like the spec until such time as we have resolved whether the concept of OnSend is a Cocoa deviation or something we'll introduce as a broader concept.
I'm happy to merge this once we have the add and remove methods (with no rawEventData parameter) but I'll kick off discussion on the issue to make sure it's covered before we release.


Keras doesn't learn properly when tensor is passed to custom-layer by key-word argument

When I pass tensor to layer by keyword arguments the learning sometimes doesn't happen properly.
I would expect it not to matter if keyword or non-keyword argument is used as long as the model logic is unchanged.  Example below demonstrates that the learning doesn't happen properly for tensors passed by keyword arguments.
System information

Have I written custom code (as opposed to using example directory): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  happens everywhere - tested in colab and os x
TensorFlow backend (yes / no):   yes
TensorFlow version:  1.14.0
Keras version:  2.2.4-tf
Python version:  3.6

Describe the current behavior
Keras doesn't learn properly when tensor is passed to custom layer by keyword argument.
Below all the models should produce roughly same accuracy or loss. However when use MyLayer the loss is clearly higher than in other two case even though it shouldn't affect the model structure.
Describe the expected behavior
Learning shouldn't be affected if use keyword arguments or not as long as the logic is the same.
Code to reproduce the issue
Note that layer_type=1 gives much higher loss even though all the models are logically the same.
Colab: https://colab.research.google.com/drive/19iqhjJm2N8yOwVzdDK8j9yRNNdw7whZn
Code
import numpy as np
import tensorflow as tf
import sys
from tensorflow.python.keras import layers, callbacks
from tensorflow.python.keras.losses import MeanSquaredError
from tensorflow.python.training.gradient_descent import GradientDescentOptimizer

print(tf.__version__)
print(tf.keras.__version__)
print(sys.version)

N = 10000
FEATURES_D = 12

class MyLayer(tf.keras.layers.Layer):
    def call(self, inputs, mask=None, t=None):
        return t

class MyLayer2(tf.keras.layers.Layer):
    def call(self, inputs, mask=None, t=None):
        return inputs

np.random.seed(0)
X1 = np.random.rand(N, FEATURES_D)
X2 = np.random.rand(N, FEATURES_D)
W = np.random.randn(FEATURES_D)
y = X1.dot(W) + np.random.randn(N)

def model(layer_type):
    x1 = tf.keras.Input(shape=FEATURES_D)
    x2 = tf.keras.Input(shape=FEATURES_D)

    x11 = layers.Dense(10)(x1)

    if layer_type == 1:
        x11 = MyLayer()(x2, t=x11)
    elif layer_type == 2:
        x11 = MyLayer2()(x11, t=x2)

    out = layers.Dense(1)(x11)

    model = tf.keras.Model(inputs=[x1, x2], outputs=out)
    model.compile(optimizer=GradientDescentOptimizer(0.01), loss=MeanSquaredError())

    h: callbacks.History = model.fit(
        [X1, X2], y=y, batch_size=256, epochs=10, verbose=0
    )
    return h.history["loss"][-1]

for _ in range(3):
    for layer_type in [0, 1, 2]:
        print(f"{layer_type} - {model(layer_type)}")

    print("---")

output:
1.14.0
2.2.4-tf
3.6.8 |Anaconda, Inc.| (default, Dec 29 2018, 19:04:46)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)]
WARNING: Logging before flag parsing goes to stderr.
W0724 20:09:44.047463<PHONE_NUMBER> deprecation.py:506] From /anaconda3/envs/py36/lib/python3.6/site-packages/tensorflow/python/ops/init_ops.py:1251: calling VarianceScaling.__init__ (from tensorflow.python.ops.init_ops) with dtype is deprecated and will be removed in a future version.
Instructions for updating:
Call initializer instance with the dtype argument instead of passing it to the constructor
2019-07-24 20:09:44.151038: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
0 - 1.0245165932655333
1 - 1.788629257965088
2 - 1.0349093259811402
---
0 - 1.0278864135742187
1 - 1.6075011337280274
2 - 1.0326046692848205
---
0 - 1.0317546758651734
1 - 1.3196803382873534
2 - 1.0330685680389404
---

This problem doesn't happen with TF 2.3 anymore.  The exact same code from OP gives now result:
2.3.1
2.4.0
3.8.5 (default, Aug  5 2020, 03:39:04)
[Clang 10.0.0 ]
2020-12-06 12:02:16.072480: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN)to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2020-12-06 12:02:16.085526: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x7f9e25dd4870 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-12-06 12:02:16.085538: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
0 - 1.0734927654266357
1 - 1.0606768131256104
2 - 1.0399056673049927
---
0 - 1.026423454284668
1 - 1.0261292457580566
2 - 1.0366202592849731
---
0 - 1.0420615673065186
1 - 1.0303572416305542
2 - 1.0842583179473877
---

So all models have roughly same loss and accuracy as expected. I don't know what was the problem but it has now gone.


Improve usability of minimized/maximized editors

I tried as best I could to look for duplicates, but couldn't find any. For the longest time, when using cmd+X to set focus to a different editor group, only the focus (i.e. I-bar) would change to the last active editor in that group. Now, that still happens, but the editor group also gets maximized, and all my other groups minimized -- mega annoying for me! I don't want my editor layout to change; I still need to able to read stuff in other groups, and with all other groups minimized, that's not possible. I also don't want to spend my time resizing all my groups with the mouse (I haven't found any key sequence to revert back to non-maximized layout, not that it would solve my issue anyway).
How do I now set focus to another editor group with the keyboard without my workbench layout being altered? I've searched settings for things like "maximize", "minimize", "resize", nothing seems applicable except "workbench.editor.centeredLayoutAutoResize" but only kind of, and setting this to false (from default true) didn't fix the issue.

VSCode Version: 1.33.0 (1.33.0)
OS Version: macOS 10.14.4

Steps to Reproduce:

Press cmd+1 or cmd+2 or cmd+3 with a 3x2 grid.

Interestingly, the issue only occurs with cmd+2 and on. cmd+1 just sets the focus. Yet all sequences of cmd+N are tied to the same behavior: "set focus to editor group N"
Does this issue occur when all extensions are disabled?: Yes

@stefcameron can you try running the command Reset Editor Group Sizes and see if the issue still reproduces?

@stefcameron can you try running the command Reset Editor Group Sizes and see if the issue still reproduces?

@sbatten Certainly! But I'm not sure at what point I should run this command, and what I should expect. Do I just run this once and then expect the problem to go away? Or do I run this after I've focused to an editor and all other editors have been minimized (and so I'd have to run this command every time I focus to an editor group with cmd+N...)? Or once I've set focus to an editor group with cmd+N, then run this command, and after that, cmd+N should no longer minimize other editors? Please clarify.

If you run the command once, I expect that clicking into editor groups will no longer maximize them. If this not the case, please let me know and I will continue to investigate the issue.

@sbatten Thanks for clarifying. I gave it a try, and yes, it fixed the issue! I played around a bit more to see if I could get the issue to resurface, and I discovered that all is well until I click and drag an editor to resize it such that it causes another editor to get minimized (i.e. that editor's height gets to its minimum height). At that point, cmd+N will continue to work (i.e. not cause that editor to get maximized and all others to be minimized) until I set focus to the minimized editor. Then that editor will get maximized and all others will be minimized. From this point on, since all other editors got minimized, as I continue with the cmd+N sequence, they each get maximized and all others minimized. This until I issue the Reset Editor Group Sizes and editors come back to their original heights and the maximizing/minimizing on cmd+N finally stops.
So the trigger is causing an editor to be minimized just by resizing it to be (in my case, without the intent to minimize it, just to make it small).
I think here, because I had no visual cue that I had now minimized an editor, I'd expect that editor's height to maybe get increased just a bit on focus if it's so small focus can't be set, but suddenly causing it to get maximized and all others minimized was completely unexpected.

@stefcameron thanks for diving in.
@joaomoreno @bpasero

My pleasure!

@stefcameron if you make an editor group small enough it snaps into minimized mode (we had this behaviour for a long time). In that mode moving focus around will cause this state to be preserved. Maybe what you want is a way to disable this behaviour? Can you state what you expect here?

Not sure if this is related or the same thing, but I also work with multiple editor group columns and rows, and I've discovered that the automatic expand/collapse behaviour of minimised groups in one orientation also affects groups in other rows or columns. For example, if I have two primary columns, and then in the second column I have multiple rows that I keep in a minimised state (except for the one in focus), then, when I switch to another row, thus triggering the expand/collapse behaviour, the other column also collapses, and the current column expands. Automatic expand/collapse behaviour should be limited to the current row or column. The feature is currently unusable if using more than a single primary row or column of editor groups.

@bpasero I know you guys are probably swamped, but I figure pinging you can't hurt ... :-)


Feature request: Add a "Does not Inherit" clause in docs for spec

Just a thought here, if its possible-- add a "does not inherit clause in the docs for the specs.
Ran into some trouble, i assume that if defaults were not specificed ,
Say my spec was:
 "spec_1": {
    "timeout": 10000
  }

I assumed it would translate to:
  "spec_1": {
    "start_state": null,
    "in_progress_state": "in_progress",
    "finished_state": null,
    "error_state": "error",
    "timeout": 300000, // 5 minutes
    "retries": 0 // don't retry
  }

But the defaults (as far as i could tell) are note appended to the object that i create. Just a thought, could be completely off base, but thought I would at least raise the question!
Worker is great, thank you for the great product!

Right, I agree this is a little broken and inconsistent, but this was tricky because the queue uses a null timeout to switch it to an at-most-once mode (never time a job out) and in Firebase an undefined attribute is the same as a null attribute.
Was this suggestion to just make the docs a little clearer, or to change the behavior a little?
We can't fix the behavior in any 1.x release because it's too big a breaking change, but in 2.0.0 we could switch to using 0 for special-casing a task that doesn't timeout. I don't think that alone is worth a bump in major versions, but perhaps the addition of delayed, scheduled and repeating tasks along with it would be worthy of the bump...
As I use this more, I tend to be very explicit with my task specifications to avoid unexpected behavior, which suggests to me things aren't quite right. The biggest inconsistency other than the timeout is that in_progress_state doesn't have a default (if you specify a specId in the queue options). The reasoning behind this was that it's the attribute that defines the job that's running and what to look for to time out other jobs - having two task specs the same in_progress_state would cause very weird behavior, particularly around job timeouts and resetting jobs to a potentially wrong start_state.
I could perhaps be convinced that we could make a non-breaking change to get that to default to "in_progress" just like the error_state does to "error", but then timeout is the one attribute that doesn't work like the others.


Feature/#2486 add timeout

Description

This PR will provide support for the TIMEOUT argument in FT.Aggregate and FT.Search

Checklist

[ ] Does npm test pass with this change (including linting)?
[ ] Is the new or changed code fully tested?
[ ] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

@leibale I just saw that one test case was failing. I missed to add one param in expected results. My bad.
I have made the test case proper and pushed again.
please have a look

Codecov Report
Patch coverage: 100.00% and project coverage change: -6.46 :warning:

Comparison is base (3273c85) 95.67% compared to head (a4164e8) 89.21%.

:exclamation: Current head a4164e8 differs from pull request most recent head 2a2002e. Consider uploading reports for the commit 2a2002e to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2488      +/-   ##
==========================================
- Coverage   95.67%   89.21%   -6.46%
==========================================
  Files         455      455
  Lines        4552     4554       +2
  Branches      522      523       +1
==========================================
- Hits         4355     4063     -292
- Misses        128      419     +291
- Partials       69       72       +3

Impacted Files
Coverage Δ

packages/search/lib/commands/SEARCH.ts
82.60% <ø> (ø)

packages/search/lib/commands/AGGREGATE.ts
100.00% <100.00%> (ø)

... and 77 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

is this PR good to merge?

@Nanak360 yes :)


Dummy

Note: Please adhere to Contributing Guidelines.
Summary
Update this section with information on why change is necessary,
what it exactly does and how, if new feature shows up, provide
references (dependencies, similar problems and solutions), etc.
Impact
Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.
Testing
Update this section with details on how did you verify the change,
what Host was used for build (OS, CPU, compiler, ..), what Target was
used for verification (arch, board:config, ..), etc. Providing build
and runtime logs from before and after change is highly appreciated.

切换开发分支

这是来自QQ邮箱的假期自动回复邮件。你好，我最近正在休假中，无法亲自回复你的邮件。我将在假期结束后，尽快给你回复。


Build issues

I've tried building the fdroid flavor from source but failed, as it seemingly insists on signing the APK but fails. Recipe:
          - keytool -genkey -v -keystore keystore.jks -alias dummy -keyalg RSA -keysize 4096 -sigalg SHA512withRSA -validity 10000 -dname "cn=dummy" -storepass storepass -keypass keypass
          - export SIGNING_STORE_PASSWORD=storepass SIGNING_KEY_ALIAS=dummy SIGNING_KEY_PASSWORD=keypass
          - ./gradlew assembleFdroidRelease

Build error:
> Task :app:packageFdroidRelease FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:packageFdroidRelease'.
> A failure occurred while executing com.android.build.gradle.tasks.PackageAndroidArtifact$IncrementalSplitterRunnable
   > com.android.ide.common.signing.KeytoolException: Failed to read key dummy from store "/build/repo/keystore.jks": Get Key failed: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.

Even if I remove the signing call using sed -r '/signingConfig.release/d' -i app/build.gradle, same result. If I instead use ./gradlew buildFdroidRelease, as the Readme says, I don't get any APK.
Can you please explain how to build an unsigned APK of the fdroid flavor? The hint from the Readme seems not to produce it.

Signing the APK fails in your example, because the password for the keystore and the key are different: https://developer.android.com/studio/known-issues#ki-key-keystore-warning

But yeah, the README is not up-to-date with this. I'll look into it

Would be great if signing could be skipped altogether. I'd need an unsigned APK anyway. But are you saying passwords for store and key must be identical (then why separate variables for them)? The error message at the place you've linked to is different. But OK, I can give that a try, though I'd be surprised… Oh: surprise! WTF…
 Thanks a lot for your help!
PS: I leave this issue open as reminder for the Readme update. Feel free to close – my problem was solved :star_struck:

https://github.com/mjaakko/NeoStumbler/blob/dc83497e52c752af97fe1387765a9431e4831017/app/build.gradle#L55
The reason it failed is because sed -r '/signingConfig.release/d' -i app/build.gradle is wrong; it  should be sed -r '/signingConfigs.release/d' -i app/build.gradle (note the "s" before the ".").

Fixed, thanks!

This is now clarified in the README


For C++, autoconvert '.' to '->' when the type is a pointer

First off, the new intelliSense engine is awesome! Exactly what we've been waiting for. Thanks for taking our feedback and making that happen.
It seems to me that when the "Default" engine is enabled and doesn't need to fallback to the tag parser, you have enough type information to separate pointer objects from non pointer objects. It would be really nice in those cases to convert '.' to '->' if the object type is a pointer (or vice versa).

https://github.com/Microsoft/vscode-cpptools/issues


Research the plotting library "plotly"

plotly

https://plotly.com/python/histograms/
Interesting features called histfunc. Stacked histograms could also be useful to compare distributions. I intend to implement plotly and see if it is more useful than seaborn &matplotlib


Allow recordings to be accessible via a button

Is your feature request related to a problem? Please describe.
Clips and snapshots are available but not recordings.
Describe the solution you'd like
In the native frigate UI it is possible to view recordings on a per camera basis, would be nice to have this option on each camera in addition to using the HASS media browser.

With the v4 card pre-release you can access recordings via the timeline view, example:
https://github.com/dermotduffy/frigate-hass-card/tree/release-4.0.0#single-camera-recordings
I'm currently working on improvements to this, but that's available for now at least. Let me know if this is what you're looking for.

Looks good (updated to beta releases via HACS), does showing recording also depend on the frigate backend being a beta version or the main HA integration? Looks like by default show recordings is enabled but I am not seeing anything visualized.
Sound like this SHOULD do what I want but at the moment it doesn't appear to be working for me. I will try to read all the beta docs...

Had to upgrade the backend to 0.11.0, the integration to 3.0.0 in addition to the 4.0.0 card
Looks like the basics are covered.. Now I REALLY need to find a coral device.

I think there are still some improvements I can do here! Re-opening so I remember. There's also major rework for recordings going on, so I'll try to work this in ...

#1 is because it shades in any hour that has recording of any length. I figured out a way to address this that will be in my timeline rework I'm working on now.
#2 is a bug, mind opening a separate issue?

I have opened a separate bug for the download error.
Look forward to the improvements on the timeline.. It is looking good so far.
If there is a separate place I should give general feedback on the timeline let me know. Selecting days / going back and forth could maybe be improved at the moment all I see is the ability to drag and zoom out. Having a date / time picker to jump to a specific day at 2pm would be nice for example when going further back in time weeks.

Recordings will now be accessible via an optional button in  the next build, although it's still fairly limited until the 'infinite list' idea is implemented. I'll close this one for now, and  we can track that over at #835 .


Upped undertow version to 1.1.

Yeah, why not. Thanks! :)

Sorry, I forgot my gpg key passphrase again. I'll sort this issue out and will publish new version a bit later. :)

Sounds good. Thanks.
On Thu, Jan 15, 2015 at 7:19 AM, Alexander Solovyov <
<EMAIL_ADDRESS>wrote:

Sorry, I forgot my gpg key passphrase again. I'll sort this issue out and
will publish new version a bit later. :)
—
Reply to this email directly or view it on GitHub
https://github.com/piranha/ring-undertow-adapter/pull/6#issuecomment-70077925
.

Did you manage to deploy a new release yet?

I'm sorry it took so long! It's there.


Url.parse does not handle repeated query parameters correctly

Found an issue where flat parameters are discarded when passing in a URL to client.get. Specifically, I'm calling client.get(url) with an absolute URL that has a repeated parameter. Even though the client instance is configured to use the flat encoder, I'm seeing only the last value.
Looks like client.request is calling URL.join() to merge the URL with the base URL (in this case the base is null.) This is where it breaks:
Example:
Hurley::Url.join(nil, 'https://www.foo.com?a=b&a=b2')
#<Hurley::Url https://www.foo.com?a=b2>
Notice only the last value of a is preserved. Expected result is that both pairs would be retained.

Looks like changing the default query parser to flat helps. But it still is a bug in that it ignores the connection and request level preference.
Since I'm using this in a library, I don't want to rely on having to change the default behavior as it could interfere with other usages.


The constraint is equal to zero

What should I do if I have a constraint that equal to zero?

I had a similar question via E-Mail some time ago. It was about an equality constraint equals to 5.
Equality Constraints are in general challenging to handle using Genetic Algorithms. One way of handling them is see it as a small range.

g(x): x = 5

g'(x): 4.999 <= x <= 5.001  (this can be formulated as two inequality constraints)

Other options of coding it:
g''(x): |x -5| <= 0   or almost the same g'''(x): (x-5)^2 <= 0

But since the constraint is so strict introducing an epsilon is applied in practice:
g'''(x): (x-5)^2  - eps <= 0

However, all of that is possible I highly recommend using a repair operator.

The repair operators makes sure all solutions satisfy the equality constraint. An equality constraint often makes most of the design space infeasible.
I am going to add a repair tutorial soon. An example or a repair function for a knapsack problem:
import numpy as np

from pymoo.factory import get_algorithm, get_crossover, get_mutation, get_sampling
from pymoo.model.repair import Repair
from pymoo.optimize import minimize
from pymoo.rand import random
from pymop import create_random_knapsack_problem

class ConsiderMaximumWeightRepair(Repair):

   def _do(self, problem, pop, **kwargs):

       # maximum capacity for the problem
       Q = problem.C

       # the packing plan for the whole population (each row one individual)
       Z = pop.get("X")

       # the corresponding weight of each individual
       weights = (Z * problem.W).sum(axis=1)

       # now repair each indvidiual i
       for i in range(len(Z)):

           # the packing plan for i
           z = Z[i]

           # while the maximum capacity violation holds
           while weights[i] > Q:

               # randomly select an item currently picked
               item_to_remove = random.choice(np.where(z)[0])

               # and remove it
               z[item_to_remove] = False

               # adjust the weight
               weights[i] -= problem.W[item_to_remove]

       # set the design variables for the population
       pop.set("X", Z)
       return pop

method = get_algorithm("ga",
                      pop_size=200,
                      sampling=get_sampling("bin_random"),
                      crossover=get_crossover("bin_hux"),
                      mutation=get_mutation("bin_bitflip"),
                      repair=ConsiderMaximumWeightRepair(),
                      elimate_duplicates=True)

res = minimize(create_random_knapsack_problem(30),
              method,
              termination=('n_gen', 10),
              disp=True)

Thanks for your reply.


Account for FIM tokens in prompt

For the Fill-in-the-middle prompt we need extra tokens to designate start, middle and end. This is usually one token each, so need to subtract 3 token of the max context length

Hi @HennerM, thanks a lot for all your contributions. I'll take a look when I have some time, I'm currently busy on other subjects.
Stay put!


Videos are no longer working in 4.0.1

Look at the examples page
https://pixijs.github.io/examples/#/basics/video.js
And change the version to 4.0.1. You can hear, but not see the video. It works fine in 4.0.0
(ps. for some reason that examples page defaults to 4.0.0 as the 'latest version')

https://github.com/pixijs/pixi.js/issues/2873 broke it?

Is there an ETC for this ?

@themoonrat Am I just crazy or did we fix this recently? I don't remember...

Nopes, still broken after the commit listed above by @GoodBoyDigital which went in to the 4.0.1 release. I've personally just removed those lines in my build of pixi to get it working again, but not submitted a pr because clearly there was a reason for adding them in the first place!

@englercj Can be closed, fixed by https://github.com/pixijs/pixi.js/pull/3043


feat: support serialization of more event data

useful for getting key event data, mouse event data, etc.

I think we should also expose this function via a mixin so we can use it in templates


Support rolling log files base on file size and time

This pr implements #809
Add two flags max_logfile_num and log_rolling_policy, support rolling
log file by day or by hour, and use max_logfile_num to control the max
history log file num after rolling.

@sergiud I have edited according to your comments, please review again

Codecov Report

Merging #811 (5297433) into master (a34226c) will decrease coverage by 0.31%.
The diff coverage is 69.09%.

@@            Coverage Diff             @@
##           master     #811      +/-   ##
==========================================
- Coverage   73.19%   72.87%   -0.32%
==========================================
  Files          17       17
  Lines        3279     3366      +87
==========================================
+ Hits         2400     2453      +53
- Misses        879      913      +34

Impacted Files
Coverage Δ

src/glog/logging.h.in
80.00% <ø> (ø)

src/logging.cc
73.85% <69.09%> (-0.83%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Thanks! Unfortunately, Windows unit tests are failing now. Could you please take a look at these first?

Thanks! Unfortunately, Windows unit tests are failing now. Could you please take a look at these first?

Ok.  I will find a Windows device to test it in this weekend

Thanks! Unfortunately, Windows unit tests are failing now. Could you please take a look at these first?

Ok. I will find a Windows device to test it in this weekend

I have tested it on Windows vs 2022 and not failed now, would you please trigger the build again?

I just pull the branch code test roll file function, when restart test demo many times the file count will over  FLAGS_max_logfile_num. Is this a problem ?

@IceLemon99 I'll close the PR since it's heavily diverged from master. If you want continue working on this please rebase.


Prepare for release v0.8.6

also added small fixes to RELEASE.md.

rebased to pick up https://github.com/cilium/cilium-cli/pull/470

bump up retries:  https://github.com/cilium/cilium-cli/pull/473

rebased to pick up https://github.com/cilium/cilium-cli/pull/474


Disable colors in logs

The ANSI term sequences mess up Google Cloud logs.

We can do this at the code level with: https://docs.rs/tracing-subscriber/0.2.19/tracing_subscriber/fmt/struct.SubscriberBuilder.html#method.with_ansi
Will look into it.

Ok see #8

Closed in favor of #8


re-write bash scripts in boot process as native binaries

This should improve boot speed as well as reduce reliability issues with bash scripts at the boot phase.

Not necessary I think.


add ARM assembly

Thanks for your contribution!

If this is a Unix (Linux) host (The system call number "4" implies it may be) the third argument to the write system call needs to be the length of the string.
That is add a "mov     r2, #12" after setting r0 and r1.
Otherwise, it'd be nice to know the OS.


Missing recipeType for bulk blasting/smoking/washing

Hello, is there a way to add recipes for blasting, smoking or washing?
I can't find any documentation ore about that and no code in the source code for that.
With best regards,
Patrick15a

Minecraft Version: 1.16.4
Create Version: 0.3e
CreateTweaker Version: <IP_ADDRESS>
CraftTweaker Version: <IP_ADDRESS>

Blasting and Smoking use the vanilla registry for their recipes (so using blasting or smoking will add the recipe to those machines).
Washing I think is the Splashing recipe
Splashing I think is the

Thanks for the quick answer and clarification. 👍


After a Rancher Manager RC, ability to apply labels to issues to move to test and comment which RC it's available in

Current manual steps that occur after each RC:
Move any issues needing an alpha/RC tag to test and comment which version:
Update any issues with the label  "[zube]: Waiting for RC" tickets to "[zube]: To Test".
Under every issue moved, comment which RC they are available for testing on (e.g. "Available to test on v2.6.1-rc3")

This isn't that dissimilar to #255 and the work is likely to overlap significantly enough to lump into the same effort.


Rate limiting middleware improvements

Rate limiting middleware improvements
code updated in https://github.com/dotnet/AspNetCore.Docs.Samples/issues/45

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

ID: bb96b20f-0991-d6de-4d98-192cd469460f
Version Independent ID: bb96b20f-0991-d6de-4d98-192cd469460f
Content: Rate limiting middleware in ASP.NET Core
Content Source: aspnetcore/performance/rate-limit.md
Product: aspnet-core
Technology: aspnetcore-performance
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Per https://github.com/dotnet/AspNetCore.Docs/issues/27098
The first code sample doesn't work anymore, the types constructor was removed. A working example of the same would probably be something like this:
app.UseRateLimiter(new RateLimiterOptions()
                                .AddFixedWindowLimiter(
                                        policyName: "fixed",
                                        configureOptions: (tokenOptions) =>
                                        {
                                            tokenOptions.PermitLimit = 1;
                                            tokenOptions.Window = TimeSpan.FromSeconds(12);
                                            tokenOptions.QueueProcessingOrder = QueueProcessingOrder.OldestFirst;
                                            tokenOptions.QueueLimit = 2;
                                        }));

Other samples on the page using that type would also need to be updated.


Improvements to the E2E tests

This PR includes 2 small commits resulting from troubleshooting a bug:

Improve a log output.
Split the Delete function to Delete and DeleteAndCheck, to prevent failures from calling Delete on
an Incorrect_metallb resource where it shouldn't do the additional check whether the deployments and
daemonsets are deleted as well.

Thanks!


Update k8s version

We need update k8s version to v0.30 to avoid version mismatch.

[ ] https://github.com/cnoe-io/argocd-api/blob/ea0d78c4f335a39c4632e578fbff7b836453a9b8/go.mod#L10-L11
[ ] https://github.com/cnoe-io/argocd-api/blob/ea0d78c4f335a39c4632e578fbff7b836453a9b8/Makefile#L16 should be v0.15.0

@nabuskey could you assign me this issue?


What kind of licenses can we use in this project?

Some kinds of licenses make the product dirty.
For example, the GNU GPLv3 lets people do almost anything they want with your project, except to distribute closed source versions.
At the same time, there are ready-made solutions, the use of which code can simplify life.
Is there a limit to the kinds of licenses that we can use during development?

I just simply want it to remain open-source, so GNU GPLv3 is perfect in my opinion

Then we have to add license text to the header of each file that is licensed by the GPL. :(

I second this + its really no effort to get this issue closed 👍

Related to #34  - closed. MIT license added.


Server Plugin Developer Workflow - Document rebuild and redeploy steps.

It would be helpful to have some steps for making code changes, rebuilding, and redeploying server plugins for testing at the bottom of https://github.com/mattermost/mattermost-developer-documentation/blob/master/site/content/extend/plugins/server/hello-world.md#installing-the-plugin.
What's the most efficient approach?  Right now I disable the plugin in the Management Console, then:
<plugin dir> $ make deploy # this directory is parallel to the mattermost-server directory

Then I re-enable the plugin and I see my updates.  Is this the most efficient way?
Happy to type up the PR if someone can confirm the steps.
Thanks!

Hey @sadohert,
The most efficient approach is to run just make deploy. It takes care of removing the old plugin and enables the new installed version. No further steps are needed.
The site you linked is a generic introduction into plugins. make deploy is only available on plugins which use the Sample Plugin template. Hence I would much rather improve the readme on https://github.com/mattermost/mattermost-plugin-sample/.
What do you think about this?

Ahhh yes.   I wasn't thinking about the make deploy being a plugin project-specific thing.  So yes, probably makes sense to improve the readme.
But even within the context of someone building a plugin with their own build scripts, are you saying we should be able to just replace the plugin binary and the server will pick this up and start using it?  For me, I:

cloned the plugin-sample,
edited the hello world print statement with a new string,
rebuilt with make deploy, and then
refreshed http://<myserver>/plugins/<my cloned plugin>

... and I don't see the changed string (e.g., "Hello World 2").  I checked the timestamp of the plugin binary file on the server and it's updated.   Only way I'm able to get the plugin behaviour to change (i.e., print my new string) is to disable and re-enable the plugin.
Maybe something else I'm doing wrong?
My setup follows these server development instructions.
Incidentally, in previous testing I noticed that make stop-server wasn't actually killing the process for the 2 plugins I have installed (mattermost-plugin-sample, and mattermost-plugin-demo).  I had to manually kill them.... discussed this with @lieut-data  and was going to submit a separate report for that.

Thanks @levb .... I'll close this issue.  Ultimately I wanted to understand the "developer workflow" for code > build > deploy > test > repeat.  I wasn't finding repeating the steps in the server/plugin docs was resulting in a sane workflow (seemed like I was having to restart the server and kill plugins to see updated behaviour)... BUT, after:

Updating my server to the latest,
Removing the mattermost-demo-plugin from my local setup (this still doesn't seem to clean up properly on make stop-server, I'll submit somethign separate),
Setting up these environment variables:

export MM_SERVICESETTINGS_SITEURL=http://localhost:8065
export MM_ADMIN_USERNAME=<admin account>
export MM_ADMIN_PASSWORD=<admin password>

I can successfully code > build > deploy > test > repeat without server restarts or killing plugins.
Thanks

Thank you very much for your feedback @sadohert!


Remove groupBy statement to increase query speed.

🗣 Description

Removed groupBy statement on line 141 of backend/src/api/domains.ts, which relates to the /domain/search endpoint. The query results remain unchanged, but the speed of the query is reduced from ~27s to ~4s.

Enabled logging in docker-compose.yml. Users can access these using the logs tab associated with the crossfeed-db-1 docker container. Logs show the exact syntax of queries and their execution time.

💭 Motivation and context

This speeds up the load times for the domains view of the site.
This allows viewing the QueryBuilder queries after they've been translated for use by the postgres database. This will help optimize our queries.

🧪 Testing
Using the network tab in the developer console, I viewed the timings for the /domain/search POST request.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All future TODOs are captured in issues, which are referenced
in code comments.
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[ ] Tests have been added and/or modified to cover the changes in this PR.
[x] All new and existing tests pass.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

updated PR to include db logging

Backend tests are failing -- https://github.com/cisagov/crossfeed/actions/runs/4746708477/jobs/8430685814?pr=1816

@epicfaace - do you want me to merge this or would you rather maintain your position as the one who merges?

@Matthew-Grayson @mbachtell-nais feel free to merge this


Review 2.0

Hi @veewee,
Thanks for your thorough review. Sorry for the long response delay also!
I've been working from time to time to improve the typing of the library and it took me more than a month to make it working.
I had a lot of issues getting it working with PHPStan.
Right now the numbers are okayish.
I only have 31 errors in PHPStan and 53 in Psalm. It's already a huge improvement :-) I hope I will improve these numbers with time.
If you want to review the new 2.0.0 version, let me know :-)

Quickly clicked thourgh the source. Overall, It looks nice!
The type additions will make it very powerfull.


JOSS Review: No community guidelines

This is a minor one, but currently this requirement for a JOSS paper is missing:
"Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support"

Adding onto this: it took me a decent amount of time to find these, including having to come to this issue to realize where they were added. It is probably best to also add a section to the GitHub repository README.

We have now added the guidelines to the README file.

Fine from my end, this issue can be closed whenever @ben-cassese is happy with the changes.


Group cluster upgrade duration tests in renames

We removed the durations from the test name in 4.14.

/lgtm


Binding hotkey to F1-F12 doesn't register first letter in input

I have a Swedish QWERTY keyboard so "`" doesn't work for me as a hotkey ("§"-key doesn't work either, but I think that's a limitation from Unity itself. American "`" is positioned at "Ö" on the image I linked).
So I changed the hotkey to "f1" instead. The command terminal works but the first letter isn't registered when typing into the input.
Also: I changed the hotkey to "tab" and it enables the terminal but unable to close it again.

This is a bug, thanks for pointing it out! Fixed in 081406c.

Awesome work! Good to know. 👍


[fpga] Add Vivado pre-synthesis hook, also setup hooks for CW305 board

This PR adds a new pre-synthesis to hook to change the severity of messages. Also, two warnings are changed to errors:

If the boot ROM init file cannot be found, the tool should not proceed and generate a non-functional bitstream.
If latches are automatically inferred during synthesis, the tool should abort. This helps to prevent that such code ends up in the repo. Currently there is again a latch inferred inside OTBN (See #3773). For this reason CI for this PR should fail at the moment.

Existing hooks are also enabled on the ChipWhisperer CW305 FPGA board except for the placement check of the boot ROM (specific to the NexysVideo, required to use the boot ROM splicing script).

Thanks @imphil for reviewing and approving this PR.

Thanks for adding this check @vogelpi!


rkt/api: add --socket option to run as a systemd.socket(5) service

This allows rkt to run as a systemd socket-based unit.
When this looks good, I'll include the recommended unit files in #2272.

Do we need a --socket option or should we just check for LISTEN_FDS and use it if it's present?

We're discussing in the issue (#2794) the best UI for exposing this.

OK, ready for final review.
It needs some awkward machination to detect when --listen is actually passed, and (bah) dependency injection.

some nits but LGTM after that.


Improve docstrings and tests

Still in progress. Source files covered:

[ ] describe_codes.py
[x] file_name.py
[ ] generate_static_features.py
[ ] generate_summarized_reps.py
[ ] generate_ts_features.py
[ ] mapper.py
[ ] utils.py
[ ] scripts/cache_task.py
[ ] scripts/describe_codes.py
[ ] scripts/generate_permutations.py
[ ] scripts/launch_xgboost.py
[ ] scripts/sweep_xgboost.py
[ ] scripts/tabularize_static.py
[ ] scripts/tabularize_time_series.py

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella: