error CS8802: Only one compilation unit can have top-level statements.

Type of issue
Missing information
Description
[Enter feedback here]
"error CS8802: Only one compilation unit can have top-level statements." is displaying in my device please fix it
Page URL
https://learn.microsoft.com/en-us/dotnet/csharp/misc/sorry-we-don-t-have-specifics-on-this-csharp-error?f1url=%3FappId%3Droslyn%26k%3Dk(CS8802)
Content source URL
https://github.com/dotnet/docs/blob/main/docs/csharp/misc/sorry-we-don-t-have-specifics-on-this-csharp-error.md
Document Version Independent Id
58a19505-ac46-c5c8-12cc-fe87b6aa18a7
Article author
@BillWagner
Metadata

ID: bbb051ee-f020-66ba-c601-4a08ad32ef61
Product: dotnet-csharp
Technology: csharp-diagnostics

Hi @soujanya30
This is one of the issues we need to add help for. Thanks for pointing that out.
One file in a C# program can contain top level statements. Those top level statements represent the entry point to the program. (This would often be the Main method in earlier C# versions or other languages).
Because it's the entry point to the program, only one file may have top level statements. All other statements must be in members defined in classes or structs.

so what should i do to start c# in all file in place of only one file , please provide a solution for it

Hi @soujanya30
We've got a few articles that will help. I recommend starting with this article on top-level statements. Then, this tutorial has an introduction to classes,
Finally, when you get stuck, post a short sample to our Q & A site. There are a number of folks that can answer these specific questions.

? be open
S.Shabani
On Tue, 26 Nov 2024 at 15:05, Bill Wagner @.***> wrote:

Closed #38811 https://github.com/dotnet/docs/issues/38811 as completed
via #43728 https://github.com/dotnet/docs/pull/43728.
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/docs/issues/38811#event-15436875276, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BICZHW5V3CIK7H6FLADXPCT2CR5ZXAVCNFSM6AAAAABSQQW33OVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGQZTMOBXGUZDONQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


fix(express.js): use tracer object

:tada: This PR is included in version 1.26.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.26.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support multiple policies

At the moment, chefspec assumes tested policy is always described in Policyfile.rb at the root of the repository.
Some repositories might have multiple policies (for instance contained into a policies directory).
It would be convenient to be able to support specifying which policy needs to be run.

Ideally, I'd like to write:
require 'spec_helper'

describe 'minimal' do
  context 'When all attributes are default, on centos' do
    let(:chef_run) do
      runner = ChefSpec::ServerRunner.new(
        platform: 'centos',
        version: '7.2.1511',
      )
      runner.converge_policy(policy_name: described_policy, policy_group: 'default')
    end

    it 'converges correctly' do
      expect { chef_run }.to_not raise_error
    end
  end
end

This will not be supported. The use of policyfiles is purely for fetching dependencies, they are not a thing that it makes sense to unit test directly.

Thanks for the answer


Allow disable code tab

I know some users created a repository in an organization but just use issues and projects to handle the whole organizations issues. So that Code could be disabled per repository.

It could also become a wiki repository.

What about optionally renaming the "Code" tab to "Files"? In some cases git (and gitea) is used as a general purpose file repository not necessarily for programming.

What about optionally renaming the "Code" tab to "Files"? In some cases git (and gitea) is used as a general purpose file repository not necessarily for programming.

I'm not against it but need other maintainers' opinions.

What about optionally renaming the "Code" tab to "Files"? In some cases git (and gitea) is used as a general purpose file repository not necessarily for programming.

I'm not against it but need other maintainers' opinions.

My opinion: both options (hiding code and renaming to files) are very useful.

What about optionally renaming the "Code" tab to "Files"? In some cases git (and gitea) is used as a general purpose file repository not necessarily for programming.

I'm not against it but need other maintainers' opinions.

My opinion: both options (hiding code and renaming to files) are very useful.

The renaming should be another PR.

Imho this should also check to not allow push to git etc?

Imho this should also check to not allow push to git etc? Or absence of record in unit will already take care of it?

push to git has been checked before.

make L-G-T-M work


Fix for NumberFilter Issue webbingbrasil#9

This change fixes the bug in NumberFilter found in #9

Thanks

You're welcome @dmandrade


[BACKPORT] [BUG] Restored volume wrongly restarts restoration during migration

#3210

Validation: PASSED
Longhorn Version: 1.2.x Fri Nov 12 01:07:07 AM EET 2021
Test steps:

Prepare a Backup
Create a StorageClass with fields migratable and fromBackup set.
Use the StorageClass to create a PVC with the accessMode ReadWriteMany
Attach the volume.
Start the migration by sending an attach request with parameter hostId set to another node
Check if the restore is not wrongly restarted. (PASSED)


Simplify #include statements

Commit 4736fde moved header files into include/networkit which resulted in error-prone #include statements such as
#include "../../../../include/networkit/io/METISGraphReader.hpp"

They should be written as:
#include <networkit/io/METISGraphReader.hpp>

The first option is harder to read, less flexible and tedious to write (as I've seen while working on #320).
Also the second format is more consistent for external users linking against NetworKit.
This PR does the following:

Add search path in CMakeList.txt with higher priority than system search path (to prevent usage of installed headers)
Rewrite include in networkit/cpp/ and include/networkit such that no relative includes are used (see below)
Rewrote some occurences of #include "omp.h" to #include <omp.h>

If you think this change is worth-while, there's a decision to make:
How do we treat includes of siblings within the same directory (e.g. A/bar.hpp includes A/foo.hpp). Do you prefer #include "foo.hpp" (shorter) or #include <networkit/A/foo.hpp> (more verbose).
I feel the more consistent second options is better, as it leaves no exceptions which have to communicated in the style guide.

Just to support my claim on: there are a lot of includes in subdirectories -- typically tests -- which in fact use the wrong number of "../". One of many examples is networkit/cpp/algebraic/test/GraphBLASGTest.cpp:
#include "../../../include/networkit/algebraic/GraphBLAS.hpp"

This points to [PRJROOT]/networkit/include/networkit/algebraic/GraphBLAS.hpp rather than [PRJROOT]/include/networkit/algebraic/GraphBLAS.hpp.

Thank you for the PR, Manuel. This was already on our TODO list since we moved the headers to include/. Hence, I am very grateful that you did the work to implement this :).
The second option for local files should be preferred in public headers. In principle, the first option could be used for private headers but as far as I can see, we don't have private headers right now.

I consider this PR complete. We should definitely add some automatic checks for CI. But this should be done in a separate PR. Please let me know, if you spot anything else.

What do you mean by automated checks for CI? Checking that nobody introduces relative includes again?

Exactly. I used a script for these conversions which could in theory be modified. However, I think it's for the best, if we first commit to some form of infrastructure for that; otherwise each checker will solve similar issues such as finding all relevant header/source files redundantly.

This has been open for a week now; I don't see any issues with this patch set, so I will merge it. Future PRs should now always use <> includes.


Enhancement: Support Quallcoms AllJoyn protocol

Enhancement request:
Please add support for Quallcoms AllJoyn protocol for connected speakers. OpenHAB has that already included and @glennpierce has already written Python bindings for it.

Feature request please into forum. Thanks


Dump MESSAGE_TYPE_UNKNOWN

This code throws a short dump
zcl_logger=>new(   )->add( |Test|   )->export_to_table( ).

Shouldnt line 19, "IF sy-subrc is initial.", rather be "IF sy-subrc not initial" ?

No, I don't think so. This works if TYPE is supplied while adding log entries.


pywalfox: init at 2.7.4

Description of changes
pywalfox-native is the native messaging host for the Pywalfox dynamic themer that dynamically sets up/changes themes of Firefox & Thunderbird based on themes generated from pywal (which is in nixpkgs).

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

@tsandrini  greetings !
could you please squash at least last two commits, or even all three. This is done so that all commits  evaluate, (helps with automatic bisecting )

@tsandrini greetings ! could you please squash at least last two commits, or even all three. This is done so that all commits evaluate, (helps with automatic bisecting )

Hi! Thanks for the review! I completely missed the SRI format so I was looked how it works and such, thanks for the patience! I've squashed and rebased the commits into one as expected :)


Burn Probability to Terra and add Future Parallelization

Working to ugrade the data management to terra and perform any parallel methods where possible.

[x] Upgrade to Terra
- [ ] Add parallelization Unnecessary afterall

https://github.com/BurnP3/BurnP3Plus/blob/b43450217554c2ad399fa05aac5ab1f35ad758c8/src/burnProbability.R#L105-L106
The terra::rast() call should probably be within the tryCatch() in case of a missing collection of burn maps.

https://github.com/BurnP3/BurnP3Plus/blob/b43450217554c2ad399fa05aac5ab1f35ad758c8/src/burnProbability.R#L116
This change does not work with the Prometheus fire growth model, as the values of pixels in the per-iteration burn maps indicate the fire ID in which the pixel was first burned, not just 1/0.

Scratch that second comment, I went ahead an made that change to BurnP3Plus-Prometheus. Let me know if you'd like to change both fire models and this line if you'd like the other behaviour though.

These changes and removal of RGDAL dependencies have been made to this branch and merged into main. BadgerOnABike/issue1 can probably closed now


Store sensor data in SAP Vora

I've followed this tutorial with SAP Data Hub 1.4 Trial Edition on GCP to the letter. This final part has failed repeatedly, and I turned on tracing to identify the cause. The error message, which included my password in plain text (removed from below), seems to be the root issue. I thought perhaps the GCS function call might have caused issues because of the insane key, but it seems to have gotten past that and has an issue with the Vora Client operator.
I've configured the SAP Vora Client operator with
dsn = v2://vora-tx-coordinator:10002/?binary=true
user = default/datahub (seemingly requires tenant/username)
password = <my "master" SDH password"
Error pasted from exported trace file:
Failed to initialize 'com.sap.vora.client': failed to ping SQL connection with DSN v2://default%2Fdatahub:MyPasswordInPlainText@vora-tx-coordinator:10002/?binary=true: authentication failed: error in first SCRAM server message: expected 3 fields, got 1: [] {graph_id="2f9b669eab3b461bbd794c838b7cc099",subgraph="default",operator_id="sapvoraclient1"}

@schneidertho Can you help here?

Hi Doug,
good question. I don't have an immediate idea. I will try to reproduce on our side. Will take a moment.
Two questions
a) have you restarted your system (if no, can you suspend and activate the CAL instance)?
b) Do you have special characters (like $, & etc.) in your password? I just want to narrow down where the problem comes from.
Cheers
Thorsten

Hi Thorsten,
a) I've not restarted the SDH or HXE since activation, but I have suspended and reactivated the solution from CAL a few times since activation. I will activate it again now. Also, I have successfully been using Vora tools and modeler as part of the SDH 1.4 trial, including loading data from GCS with the same Iss, project and key as in the javascript operator, but via the Vora Modeler UI.
b) No, there are no special characters in my password.
Can you confirm that tenant and user should be formatted default/datahub as opposed to default\datahub (as in an Active Directory domain\user)? I'll try this once reactivated.
Thanks for looking into it. Truly appreciate it!
Doug

Hey Thorsten,
I've just reactivated SDH 1.4 from CAL, ran the pipeline with Vora user both ways and confirmed that the issue is in fact the Vora client parameter for user.
The Vora Client user must be in the format "tenant\user", so the tutorial step 3 needs to be updated.
Here is a screenshot of the running process flow, including the Vora client user formatted "default\datahub". I also confirmed sensor data is successfully stored in a disk table in Vora.
Once the tutorial is updated, this issue can be closed.
Thanks!
Doug

Hi Doug,
thanks. You were faster than me. We will update the tutorial (target is tomorrow or Friday). Best regards
Thorsten

@schneidertho Let us know if we can close this issue?

The tutorial is still incorrect. The Vora client user format in step 3 should be shown as "default\datahub", NOT "default/datahub". After fixing the tutorial, the issue can be closed.
https://www.sap.com/developer/tutorials/datahub-trial-pipelines-part05.html

Thanks,
Doug

Hi Doug,
the change has been made. Cheers
Thorsten


Sending guarantee

How do I get a goddamn answer to a sales related question without setting up an account?
Your FAQ is useless and there is no way to ask a question.
I had a question regarding inclusions that are not specifically documented
Good business model - don't provide any sales assistance and watch potential customers find an alternate solution!

The struggle is real, @whitsey - it takes at least two clicks to get to the contact us page - https://sendgrid.com/contact-us-form/

@whitsey ... I am sorry about that. I shared your comment with our UI/UX people. Were you able to get in touch with our sales team?
@mikegreen thanks for the assist!

Closing this issue since there's not a specific docs request here. Let us know if you have any other issues!


test: unit tests for server module

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Codecov Report

Merging #5154 into dev will increase coverage by 0.54%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##              dev   #5154      +/-   ##
=========================================
+ Coverage   96.06%   96.6%   +0.54%
=========================================
  Files          73      72       -1
  Lines        2463    2447      -16
  Branches      625     620       -5
=========================================
- Hits         2366    2364       -2
+ Misses         81      68      -13
+ Partials       16      15       -1

Impacted Files
Coverage Δ

packages/server/src/middleware/nuxt.js
100% <ø> (+1.47%)
:arrow_up:

packages/server/src/middleware/error.js
100% <100%> (+2.12%)
:arrow_up:

packages/vue-renderer/src/renderer.js
95.85% <0%> (+1.03%)
:arrow_up:

packages/server/src/listener.js
100% <0%> (+1.88%)
:arrow_up:

packages/server/src/middleware/modern.js
100% <0%> (+3.12%)
:arrow_up:

packages/server/src/middleware/timing.js
100% <0%> (+4.54%)
:arrow_up:

packages/server/src/server.js
100% <0%> (+5.74%)
:arrow_up:

Continue to review full report at Codecov.

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


Redis Connector 5.2 - Mule 4 - Incorrect Mule Runtime Version

Team,
Redis Connector Page shows incorrect Mule Runtime Version
div class="flex align-center justify-justified row">
| Runtime
  | Mule 5.2 or later
Page Link : https://docs.mulesoft.com/redis-connector/5.2/

@bharathChamala Thank you for pointing this out. It has been fixed.


Add instructions to the prevalence inputs.

I had meant to re-point this PR at the manual-entry-v1 branch per the process, but when I re-ran the failing test, it passed and auto-merge was already set, so it merged.


makerst: Fix file name not appearing in error message

Follow-up to https://github.com/godotengine/godot/pull/61920 (it's not a regression from that PR though).
Before
ERROR: {}.xml: Four spaces should be used for indentation within [codeblock].
1 error was found in the class reference XML. Please check the messages above.

After
ERROR: MovieWriter.xml: Four spaces should be used for indentation within [codeblock].
1 error was found in the class reference XML. Please check the messages above.

Thanks!


Cannot read properties of undefined (reading 'map')

As follow, i am working on changing mode when editing.
There seems this.instance.setOption("mode",mode) has no error, but then, the editor can't be focused on and Cannot read properties of undefined (reading 'map') appears.
What should i do? please help me.

Have you tried reducing this problem to the minimal script needed to trigger it? That might help reproduce the issue (dynamically changing the mode generally works).

Have you tried reducing this problem to the minimal script needed to trigger it? That might help reproduce the issue (dynamically changing the mode generally works).

As follow, it is just a single *.vue file.  After changing mode and input again, the issue will reproduce.
<template>

                <select v-model=" mode " class="float-r" @change=" setOption( 'mode', mode ) ">
                    <option v-for="(v, k) in    modes    " :key=" v " :value=" k ">{{ k }}</option>
                </select>

                <textarea ref="ta" />

</template>

I don't know a lot about Vue, but I do know that is does strange things to objects managed as part of its state, and you don't want to put complicated stateful objects like a CodeMirror instance in there. Try refactoring your code to not have the CodeMirror instance in the data object.

Okay, thank you.

Thank you so much I was having the same issue Cannot read properties of undefined (reading 'map') occasionally and I removed codemirror instance from data object and instance just assigned it to a const.

Thank you so much！！！

Thank you so much @marijnh, I recently had the same problem using Vue3's composition API.
I'll put my code here and how I fixed it in case someone (or even me again) addresses the same issue in the future...
BEFORE:
const codeEditor: Ref<any> = ref({});

onMounted(() => {
  codeEditor.value = CodeMirror.fromTextArea(textAreaRef, opts);
  codeEditor.value.setSize('100%', props.fullHeight ? '100%' : 500); // This line was triggering the error.
});

AFTER:
const codeEditor: Ref<any> = ref({});

onMounted(() => {
  // I created a local variable inside this 'onMounted' scope just to configure my CodeMirror instance.
  const codeMirror = CodeMirror.fromTextArea(textAreaRef, opts);
  codeMirror.setSize('100%', props.fullHeight ? '100%' : 500);

  // After finishing the setup I assign the instance to my ref variable (because I need it outside this scope)
  codeEditor.value = codeMirror;
});


Deprecated force on first-level dependencies

Context
This commit deprecates using force in favor of using the
new "strictly" behavior. The "force" flag is still used
internally, in particular in case of virtual platforms, but
its usage should be discouraged as we have a solution which
is better now.
Closes #10706

There's one performance regression I'm honestly not sure is related to those changes...

We should also add a note to the deprecations for 6.0 section in upgrading_version_5.adoc.

Still need to update the "forcing dependency versions" section of the docs, but there are different changes in different PRs for this so for simplicity this is going to be a follow-up.


Renaming HTTP 'key' query parameter to 'code'

So we have consistency with WebHooks. Addresses https://github.com/Azure/azure-webjobs-sdk-script/issues/61

Merged. Still open for feedback.


fix(ci): outputs are always strings 🙄 See https://github.com/actions/runner/issues/1483, again 🤣

The linter is failing.
It says only single quotes should be used.


Don't change case in Auto-link feature

Is it possible to add one more configuration option?
Almost everything can be customized, except that auto-anchors are lowercase.
Can you make that optional? With one simple flag in settings?
I need auto-anchors like "One_Two_Three", and not like "one_two_three".
Thanks in advance.

It may be technically possible. But I want to know why you need it. Would you mind explaining your situation ?

I am using https://github.com/Dynalon/mdwiki to present my .md files.
Please note that I also asked for the similar request (reversed) on that project,
because it looks like one-two-three is standard.

It should not lowercase [^A-Z]. Currently when it lowercases İ (which is not ASCII), it generates a i and an invisible character next to it.

Hi @naokazuterada
I have labelled this as an new-feature, perhaps we should extract the observation by @maliayas as a bug report, so we do not have bugs/new-features mixed up in the same issue.

This problem fixed on 2.6.0.


Squeel doesn't play nice with to_param

Squeel 0.9.3 with Rails 3.0.11
Consider the following query:
User.find(params[:id])
Now if you have overwritten to_param in your model to get pretty URLs you might end up with this:
User.find("1-Firstname-Lastname")
With a stock Rails 3 app this yields:
SELECT "users".* FROM "users" WHERE "users"."id" = 1 LIMIT 1
But with Squeel:
SELECT "users".* FROM "users" WHERE "users"."id" = '1-Some-Name' LIMIT 1
I.e. Squeel potentially breaks existing apps. Is this expected behavior?

Works after updating to Rails 3.1.


fixed grammar 🧐

Typo fix: tranfer => transfer
Grammar fix: transfer you data => transfer your data

As Microsoft will not transfer "me" data in this context but, it will transfer "my" data

@undergroundwires : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Attachment views disappeared after tableView scrolling

I've put a SubviewAttachingTextView textView inside a tableView, and it contains several images and subviews, when I scroll the tableView, the images and subviews disappear, leaving blank spaces, I've tried to reset attributedString in willDisplayCell, but it doesn't solve the problem, can you give me a hint on how to fix that? Or is it just a tableView caching issue?

I have experienced SubviewAttachingTextView rendering issues when SubviewAttachingTextView is inside reusable table view cell.
I have resolved this issue by adding invalidate function and call it form UITableViewCell.prepareForReuse function.
`func invalidate() {
attachmentBehavior = SubviewAttachingTextViewBehavior()
attributedText = nil
bindAttachmentBehavior()
}
private func bindAttachmentBehavior() {
    attachmentBehavior.textView = self
    layoutManager.delegate = self.attachmentBehavior
    textStorage.delegate = self.attachmentBehavior
}`


feat(AgmMap): Tilt option.

Issue #1581
Adds the Google Maps Option tilt.
By default for AGM value: 0 to disable it. Set it to 45 to enable it.
The type number not 0 | 45 is correctly in my option and conform with the google api type specs.

@SebastianM  Any chances on landing this PR? I was planning to create the exact same PR as I need to set the tilt option (https://developers.google.com/maps/documentation/javascript/reference/map#MapOptions.tilt).
If this PR needs work and I can help, please do let me know.

@frederikprijck we plan to merge this PR and others into our crowdsourced fork github.com/agm-preview/angular-google-maps

hey, @SebastianM is away for now. Can you please submit your PR to our crowdsourced fork
https://github.com/agm-preview/angular-google-maps ?


update qodana action

Codecov Report

Merging #5 (0c28317) into master (ac9baa0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #5   +/-   ##
=========================================
  Coverage     23.21%   23.21%
  Complexity       57       57
=========================================
  Files           168      168
  Lines          4261     4261
  Branches        611      611
=========================================
  Hits            989      989
  Misses         3238     3238
  Partials         34       34

Impacted Files
Coverage Δ

...otlin/org/jetbrains/projector/agent/common/Misc.kt
0.00% <ø> (ø)

...common/transformation/ProjectorClassTransformer.kt
0.00% <ø> (ø)

...gent/common/transformation/TransformationResult.kt
0.00% <ø> (ø)

...or/agent/common/transformation/TransformerSetup.kt
0.00% <ø> (ø)

...ins/projector/agent/ijInjector/BatchTransformer.kt
0.00% <ø> (ø)

...ector/agent/ijInjector/IjBrowserUtilTransformer.kt
0.00% <ø> (ø)

...nt/ijInjector/IjFastNodeCellRendererTransformer.kt
0.00% <ø> (ø)

...jetbrains/projector/agent/ijInjector/IjInjector.kt
0.00% <ø> (ø)

...ains/projector/agent/ijInjector/IjInjectorAgent.kt
0.00% <ø> (ø)

...agent/ijInjector/IjLigaturesDisablerTransformer.kt
0.00% <ø> (ø)

... and 158 more

Continue to review full report at Codecov.

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


Reference to unreleased version 2.1.0

Good morning!
I tried to run the samples in this project and realized that in
EntityFramework.Docs/samples/core/Saving/Saving/packages.config
there are references to
package id="Microsoft.EntityFrameworkCore" version="2.1.0" targetFramework="net461"
package id="Microsoft.EntityFrameworkCore.Relational" version="2.1.0" targetFramework="net461"
package id="Microsoft.EntityFrameworkCore.SqlServer" version="2.1.0" targetFramework="net461"
Standard Nuget doesn't find them cause they are not released yet under https://www.nuget.org/packages/Microsoft.EntityFrameworkCore/.
Consider changing it to:
package id="Microsoft.EntityFrameworkCore" version="2.1.0-preview2-final" targetFramework="net461"
package id="Microsoft.EntityFrameworkCore.Relational" version="2.1.0-preview2-final" targetFramework="net461"
package id="Microsoft.EntityFrameworkCore.SqlServer" version="2.1.0-preview2-final" targetFramework="net461"

Convert to package references and...use floats or whatever...something that works.


Update download button copy

[description]:

Update site-wide CTA button copy to indicate "Download" instead of "Install"
Update header button style to vertically center copy

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c307e8a1bd7456666e33d63f92559c2481666f4b/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c307e8a1bd7456666e33d63f92559c2481666f4b/

LGTM.
I just restarted the Team City job; it had failed on a link. Once it's green, we can merge.

TC kept failing on the link to the Sequelize docs. Updated that link. Once TC is green, I'll merge.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/951ab0131477b06560b78dfb219400f170a91fd1/


FOR UPDATE and FOR NO KEY UPDATE  Examples

Hey Russell, I just found your page about Postgres locks and it looks awesome in it is really useful. Thank you for creating it.
I do have some questions/suggestions regarding the examples for FOR UPDATE and FOR NO KEY UPDATE .
Your page states following statements take FOR UPDATE lock:

SELECT * FROM t FOR UPDATE
DELETE FROM

However in Postgres documentation we can find this:

The FOR UPDATE lock mode is also acquired by [..] an UPDATE that modifies the values of certain columns. Currently, the set of columns considered for the UPDATE case are those that have a unique index on them that can be used in a foreign key (so partial indexes and expressional indexes are not considered), but this may change in the future.

So it seems that the page is missing this statement from the list:

UPDATE t SET id = 1

When id is column is part of a unique index (eg. a primary key).
This statement is actually filed under FOR NO KEY UPDATE on your page. Even though the example is correct considering the schema (id does have an index, but it is non-unique) it can mislead reader not familiar with it. It is reasonable to assume that column named id would be a primary key of a table and under that assumption, update would acquire FOR UPDATE lock when the column value is being updated.

Great spot, thanks for looking at it in detail. I'm Busy at the moment, but will try get a fix in on Monday, thanks again!

I think I agree with your reading of the docs. I may be doing something dumb in the setup, but I can't reproduce.

Hey @leontrolski, thanks for looking into this.
As I understand you are not getting  55P03 on the SELECT ... FOR KEY SHARE NOWAIT statement in the new test.
This is the output I get using two psql sessions. I think it matches your example closely. So, I'm not sure why you wouldn't see the exception 🤔
Session 1:
test=# create table v (id int unique);
CREATE TABLE
test=# insert into v (id) values (1);
INSERT 0 1
test=# begin transaction;
BEGIN
test=*# update v set id = 2;
UPDATE 1
test=*#

Session 2:
test=# \set VERBOSITY verbose
test=# begin transaction;
BEGIN
test=*# select * from v for key share nowait;
ERROR:  55P03: could not obtain lock on row in relation "v"
LOCATION:  heap_lock_tuple, heapam.c:4708
test=!#

I'm not sure what I was doing before, but it works now 🤷 - again thanks for your help - you get a namecheck in the "sources" :-)


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67446

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/68347


Adding WPT metadata by itself doesn't result in any warnings

https://tabatkins.github.io/bikeshed/#testing

As this defeats Bikeshed’s ability to tell you when you’re missing any tests, Bikeshed will emit a warning as long as a wpt-rest element is in use.

By default, wpt elements don’t display in the output document; they’re intended to annotate the source file to help with spec authoring, and trigger Bikeshed’s checks.

These two bits together make it sound like just "WPT Path Prefix: /fullscreen/" in the metadata section, or combined with "WPT Display: inline" might warn about missing tests, but that's not the case. Running make local at https://github.com/whatwg/fullscreen/commit/12765d7d0d233e11dfd29ce8aea87d869be8cc39 doesn't result in any output.

Bikeshed version was 5888e02cf0071ba98c44312075d6903689282c04.

It does indeed work as you'd expect, but I had a bug where it wouldn't find any omitted tests if your prefix started with a /.  Fixed in 16c2f3f1.

Confirmed working now, thanks!


fix swift4.1 bug; support other coin, such as LTC; mnemonic isLegal

support other coin like this:
let seed = Mnemonic.seed(mnemonic: words)
let net = CommonNet(symbol: token.symbol, bip32HeaderPub: token.bip32HeaderPub, bip32HeaderPriv: token.bip32HeaderPriv, wif: token.wif, addressHeader: token.addressHeader, p2shHeader: token.p2shHeader)
let hdKeyChain = HDKeychain(seed: seed, network: net)
let address = hdKeyChain.getAdress(coin_type: token.bip44Index, address_index: address_index)

Hi @Jax1993 ! Thanks for dropping us the PR!
I think CommonNet is outside of this library's scope. This library is focusing on Bitcoin(BTC/BCH).
But it's interesting so can you implement this as one of examples?


⚠ Bofrost.de has degraded performance

In d6161ad, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1160 ms

Resolved: Bofrost.de performance has improved in 1dc4883.


Move column name to config object and make it optional

Fairly sure this has been implemented in the latest release with the optional column aliases feature. Correct me if I'm wrong @AndriiSherman.


When I train the net, loss is nan, What should I do?

I use the dateset you suggest，witch has 5822653 imges.

if you use arcface, pretrain the model with softmax firstly
or try to decrease the learning rate

@muyoucun thank you very much ,i wil try.

minimize the learning rate maybe help for this issue.
close. when necessary reopened.


Introduce a buffer line class

At a minimum this should hold the current data array and the isWrapped property added in https://github.com/sourcelair/xterm.js/pull/693
This should wait until after a buffer class is introduced https://github.com/sourcelair/xterm.js/issues/694 (this is split out to reduce diff size/complexity).

We now have type LineData and the Buffer class


feature(etl): improve metadata ergonomics

The purpose of this change is to make working with datasets & tables & metadata more ergonomic. Currently we have something like this
# create new dataset and reuse walden metadata
    ds = Dataset.create_empty(dest_dir, metadata=convert_snapshot_metadata(snap.metadata))
    ds.metadata = convert_snapshot_metadata(snap.metadata)
    ds.metadata.version = "2020-01-01"

    # create table with metadata from dataframe
    table_metadata = TableMeta(
        short_name=snap.metadata.short_name,
        title=snap.metadata.name,
        description=snap.metadata.description,
    )
    tb = Table(df, metadata=table_metadata)

    # underscore all table columns
    tb = underscore_table(tb)

    ds.metadata.update_from_yaml(N.metadata_path, if_source_exists="replace")
    tb.update_metadata_from_yaml(N.metadata_path, "dummy")

which is terrifying... especially those update_from_yaml pieces. This now changes to
# create new dataset and reuse walden metadata
ds = Dataset.create_empty(dest_dir, metadata=convert_snapshot_metadata(snap.metadata))
ds.metadata.version = "2020-01-01"

# create table with metadata from dataframe
tb = Table(df, short_name=snap.metadata.short_name, underscore=True)

ds.add(tb)

ds.update_metadata(N.metadata_path)

ds.save()

This cleans up walkthrough generated datasets and motivates to use YAML metadata file. I've excluded part with TableMeta:
table_metadata = TableMeta(
        short_name=snap.metadata.short_name,
        title=snap.metadata.name,
        description=snap.metadata.description,
    )

as I don't think copying metadata from dataset to tables has any value (we don't show it anywhere and if we wanted we could copy it automatically).
New ergonomics are demonstrated on a couple of examples (I don't plan to refactor everything, but only encourage users to use this going forward). I've spent quite some time testing different alternatives and this seemed like the most straightforward one. There's a PR in owid-catalog-py.
@pabloarosado what do you think? Is it better or worse? Do you have any ideas how to improve it?

I wasn't sure whether it's more idiomatic to use
tb_garden = Table(df, like=tb_meadow, underscore=True)

or perhaps
tb_garden = Table(df).like(tb_meadow).underscore()

Dunno... I don't have an opinion, but maybe you might have.

I wasn't sure whether it's more idiomatic to use
tb_garden = Table(df, like=tb_meadow, underscore=True)

or perhaps
tb_garden = Table(df).like(tb_meadow).underscore()

Dunno... I don't have an opinion, but maybe you might have.

I also have no strong opinion on this, both look reasonable.

I wasn't sure whether it's more idiomatic to use

tb_garden = Table(df, like=tb_meadow, underscore=True)

or perhaps

tb_garden = Table(df).like(tb_meadow).underscore()

Dunno... I don't have an opinion, but maybe you might have.

No strong opinion, but perhaps first one seems easier to follow?


sensor does not get created

this is the error i get in the logs, the sensor does not want to be created
Logger: homeassistant.components.sensor
Source: custom_components/telenet_telemeter/sensor.py:113
Integration: Sensor (documentation, issues)
First occurred: 7:49:28 PM (1 occurrences)
Last logged: 7:49:28 PM
Error while setting up telenet_telemeter platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 289, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/telenet_telemeter/sensor.py", line 65, in async_setup_entry
await dry_setup(hass, config, async_add_devices)
File "/config/custom_components/telenet_telemeter/sensor.py", line 46, in dry_setup
sensor = Component(data, hass)
File "/config/custom_components/telenet_telemeter/sensor.py", line 113, in init
self._used_percentage = round(100 * ((self._data._telemeter.get('internetusage')[0].get('availableperiods')[0].get('usages')[0].get('totalusage').get('includedvolume') + self._data._telemeter.get('internetusage')[0].get('availableperiods')[0].get('usages')[0].get('totalusage').get('extendedvolume')) / ( self._data._telemeter.get('internetusage')[0].get('availableperiods')[0].get('usages')[0].get('includedvolume') + self._data._telemeter.get('internetusage')[0].get('availableperiods')[0].get('usages')[0].get('extendedvolume').get('volume'))))
TypeError: unsupported operand type(s) for +: 'NoneType' and 'NoneType'

Hi, could you enable debug logging and show log of:
"telemeter result ..."
Pleases remove personal info before posting the log details.

I see you have a peak and offpeak usage in your result (json.internetusage[0].availableperiods[0].usages[0].totalusage) which I don't have. So probably related to another product type subscription.
I'll try to detect which info is available and use it accordingly.
I'll keep you posted as soon as I have a new version that you could try.

thanks, i have the ONE subscription, offpeak doesnt count to my usable volume
are you also planning to integrate mobile data usage?

thanks, i have the ONE subscription, offpeak doesnt count to my usable volume
are you also planning to integrate mobile data usage?

ok, yes still planning to integrate mobile data usage too. (altough I don't have it myself, so I may request some feedback for that too...).
But first want to get the base stable. As I just noticed the sensor is not always updated as expected. And it's still my very first custom component I created, so still requires some more in depth analysis to grasp is all ;)

okay, if you need data or testing just ask, im happy to help

Hi all, support for peak/offpeak data elements has been added since release 0.1.0. Could you please validate? as I don't have this product myself.


Change flag behavior to introduce metric priority levels

Change flags from binary to string arguments, and introduce the concept of disabled, core, and extended.
Signed-Off-By: Joe Handzik<EMAIL_ADDRESS>Fixes issue #116.

@roclark Just took a quick hack at what I thought might sit in "core" or "extended" categories. I welcome other thoughts!

@roclark Fixed the two issues you identified. Agreed that we can expand testing to include more permutations of core vs extended, but also agree that the path to adding that is a bit complex.

Fire away!


needs: { job: value, artifacts: true }

See: Artifact downloads with needs .
Test:
  stage: build
  script:
    - "mkdir build"
    - "echo building >> build/file"
  artifacts:
    paths:
      - build/

release:
  stage: test
  needs:
    - job: build_job
      artifacts: true
  script:
    - "ls"
    - "echo finished building"

Is this syntax new?
None the less, needs: [build-job] will download the artifacts, for now, use that syntax until I have implemented this "new" way ... @ColdIce1

Not new, introduced in: GitLab 12.6.
Thanks for the suggestion!

Done https://github.com/firecow/gitlab-ci-local/commit/7a684cefe635199dcec13b0ef68f7cac0b283150 @ColdIce1


Added support for bulk updates to RLMResults

Warning, rusty programmer ahead. Review carefully. I needed to de-stress a bit, so I implemented a fix for #1172
This allows you to to bulk updates on query results, so you can nice one-liners like this:
[[Emails objectsWhere:@"unread = YES"] setValue:@NO forKey:"unread"];

@realm/cocoa

I believe I already have an open pull request that implements this?
-Samuel E. Giddins
On Mar 2, 2015, at 5:02 PM, astigsen<EMAIL_ADDRESS>wrote:
Warning, rusty programmer ahead. Review carefully. I needed to de-stress a bit, so I implemented a fix for #1172
This allows you to to bulk updates on query results, so you can nice one-liners like this:
[[Emails objectsWhere:@"unread = YES"] setValue:@NO forKey:"unread"];
@realm/cocoa
You can view, comment on, or merge this pull request online at:
https://github.com/realm/realm-cocoa/pull/1563
Commit Summary
Added support for bulk updates to RLMResults
File Changes
M CHANGELOG.md (1)
M Realm/RLMResults.h (10)
M Realm/RLMResults.mm (161)
M Realm/Tests/RLMTestObjects.h (2)
M Realm/Tests/ResultsTests.m (193)
Patch Links:
https://github.com/realm/realm-cocoa/pull/1563.patch
https://github.com/realm/realm-cocoa/pull/1563.diff
—
Reply to this email directly or view it on GitHub.

I believe I already have an open pull request that implements this?

That would be great. If you have a more efficient implementation, we can just use that. What PR is it?

https://github.com/realm/realm-cocoa/pull/1536

Nice. It seems like it would be best if we could merge the two PR's. Then you could avoid all the unnecessary row accessor creations and object conversions.

Ah we can't avoid that because there's no guarantee the user is attempting to set the value for a persisted property (it might be a computed property). Ari and I already agreed that directly hitting the database might be a premature optimization (and an increase in complexity).
-Samuel E. Giddins
On Mar 2, 2015, at 5:24 PM, astigsen<EMAIL_ADDRESS>wrote:
Nice. It seems like it would be best if we could merge the two PR's. Then you could avoid all the unnecessary row accessor creations and object conversions.
—
Reply to this email directly or view it on GitHub.

Ok, I just benchmarked them, and it seems like my approach is around two times as fast as yours. That is probably not enough to justify the extra complexity, so we can just go with yours.
If there are any parts of my PR that you find useful as optimizations, you can just reuse them in your PR.


PushPlugin notification icon is too big

PushPlugin notification icon is too big
Hi everyone,
I successfully installed  push plugin on my app, but the notifications icon doesn’t look good
See the attached photo
Does someone know how to fix it?
Thank you in advanced!

@jff1981 the space used to display your icon appears to be exactly the same as the Motorola and voicemail icons so I'm not sure what you mean by too big? Regardless, if you check the README you'll see that you can control what is displayed here by setting options.android.icon and options.android.iconColor.

Thank you for your quick response!
I wasn't sure how to use this feature
let's say i got an image  res/drawable/notify.png

I tried this but it's not working
var push = PushNotification.init(
{ "android": {"senderID": "XXXXXX", "icon":"R.drawable.notify"},
"ios": {}, "windows": {} } );
what am i doing wrong here?
Thanks in advanced!

You just need to do:
var push = PushNotification.init(
{ "android": {"senderID": "XXXXXX", "icon":"notify"},
"ios": {}, "windows": {} } );

as long as the notify.png image is somewhere in your drawables folder.

Thanks!


error in ULP macro I_WR_REG when trying to use I_GPIO_HOLD_DIS in the wake stub (IDFGH-10643)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v4.4.4
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
PowerShell
What is the expected behavior?
expected that  I_GPIO_HOLD_DIS can be used from the wake stub.
What is the actual behavior?
In function 'void esp_wake_deep_sleep()':
C:/Users/xxxxl/.platformio/packages/framework-espidf/components/ulp/include/esp32/ulp.h:347:5: error: expected primary-expression before '.' token
     .wr_reg = {\

C:/Users/xxxx/.platformio/packages/framework-espidf/components/ulp/include/esp32/ulp.h:375:39: note: in expansion of macro 'I_WR_REG'
 #define I_WR_REG_BIT(reg, shift, val) I_WR_REG(reg, shift, shift, val)

Steps to reproduce.
call I_GPIO_HOLD_DIS((gpio_num_t)16); in the default wake stub.
Build or installation Logs.
C:/Users/xxxxl/.platformio/packages/framework-espidf/components/ulp/include/esp32/ulp.h:347:5: error: expected primary-expression before '.' token
     .wr_reg = {\

C:/Users/xxxx/.platformio/packages/framework-espidf/components/ulp/include/esp32/ulp.h:375:39: note: in expansion of macro 'I_WR_REG'
 #define I_WR_REG_BIT(reg, shift, val) I_WR_REG(reg, shift, shift, val)

More Information.
So, i use ESP32D0WDR2 which has internal 2M PSRAM, just before when entering deep sleep I hold GPIO16 high to avoid a current leak.
  pinMode(16,OUTPUT);
  digitalWrite(16,1);
  gpio_hold_en((gpio_num_t) 16);

However, when waking from sleep the PSRAM fails to initilize (cannot read ID), which makes sense, the GPIO16 is still held high, and for some reason the PSRAM init function do not disable the HOLD.
However, calling
  gpio_hold_dis((gpio_num_t) 16);
  gpio_deep_sleep_hold_dis();
  rtc_gpio_force_hold_dis_all();

At the very beginning of the firmware does not solve the problem, i assume the reason is simply that the PSRAM is initilized either in early boot or even in bootloader, so disabling the HOLD afterwards cannot solve the issue.
Since i use the wake stub for other purposes i figured i should disable the HOLD here, and found this macro, sadly the macro wont compile, i assume there is a trick perhaps related to the scope of some structures used in ulp.h, but i could not find anything.
Just to clarify, the macro i use comes from here : https://github.com/boarchuz/HULP/blob/63266e18e4b3c09ae840dbf72999a36df67ab746/src/hulp_macros.h#L389
Just a wrapper for ulp.h macros.

I think you might be getting some things mixed up here.
ulp.h contains macros intended to be used from the ULP co-processor, while the wake-up stub is code that is ran from the main cpu (but ran at a early stage in the boot up process)

Closing this for now, but feel free to reopen if there is still anything unresolved here.


feat: Make the coercion ℝ≥0 → ℝ≥0∞ commute defeqly with nsmul and pow

by tweaking the definition of the AddMonoid and MonoidWithZero instances for WithTop. Also unprotect ENNReal.coe_injective and rename ENNReal.coe_eq_coe → ENNReal.coe_inj.
From LeanAPAP

[x] depends on: #10275

Also reorder WithOne material. Algebra.Group.WithOne.Defs was hiding a Ring import! I credit Johan and Mario for leanprover-community/mathlib#2707.

This PR is getting quite big; can you do this separately?

bors merge


BVN404 11.2.3 custom redirects with parameters not working in episerver 11.12

Hi Team,
We have upgraded episerver from 10.10 to 11.12 also upgrade BVN404 to 11.2.3. After the upgrade we migrated the custom redirect url from dds to sql. After performing this step we noticed that some custom url not working.
Issue is with the urls having parameters.
if entry is like below in custom redirect manager:
old url: /content/file
new url: /legacy
we are accessing with the url http://mysite.com/content/file?doc=filename
On BVN version 10.1 we were redirected to http://mysite.com/legacy?doc=filename
On BVN version 11.2.3 we are redirected to http://mysite.com/legacy/?doc=filename
(somehow an extra '/' is added at the end of url after 'legacy')
Thank you in advance.
Looking forward to your response as we are totally stuck.

Hi Team,
After enabling debug for BVN i got below logs and it looks like the extra slash is coming from BVN only.
2019-09-26 20:57:34,064 DEBUG [82] BVNetwork.NotFound.Core.CustomRedirects.CustomRedirectHandler.get_Current -
[REMOTE_ADDR: <IP_ADDRESS>] [AUTH_USER: ] [HostName: P4ALAP-7221ZPR]
Begin: Get Current CustomRedirectHandler
2019-09-26 20:57:34,077 DEBUG [82] BVNetwork.NotFound.Core.CustomRedirects.CustomRedirectHandler.get_Current -
[REMOTE_ADDR: <IP_ADDRESS>] [AUTH_USER: ] [HostName: P4ALAP-7221ZPR]
Returning cached handler.
2019-09-26 20:57:34,084 DEBUG [82] BVNetwork.NotFound.Core.CustomRedirects.CustomRedirectHandler.get_Current -
[REMOTE_ADDR: <IP_ADDRESS>] [AUTH_USER: ] [HostName: P4ALAP-7221ZPR]
End: Get Current CustomRedirectHandler
2019-09-26 20:57:34,088 DEBUG [82] BVNetwork.NotFound.Core.RequestHandler.LogDebug -
[REMOTE_ADDR: <IP_ADDRESS>] [AUTH_USER: ] [HostName: P4ALAP-7221ZPR]
Handling 404 request.

Request URL: http://upgrade.ade4local.com/legacy/?doc=filename
Response status code: 404
2019-09-26 20:57:34,229 DEBUG [36] BVNetwork.NotFound.Core.RequestHandler.LogDebug -
[REMOTE_ADDR: <IP_ADDRESS>] [AUTH_USER: ] [HostName: P4ALAP-7221ZPR]
Not handled. Current URL is ignored or no redirect found.

Request URL: http://upgrade.ade4local.com/Error/Error404/?404;http://upgrade.ade4local.com:80/legacy/?doc=filename
Response status code: 404
2019-09-26 20:57:34,297 DEBUG [36] BVNetwork.NotFound.Core.RequestHandler.LogDebug -
[REMOTE_ADDR: <IP_ADDRESS>] [AUTH_USER: swati.a.awasthi] [HostName: P4ALAP-7221ZPR]
Skipping request with 404; in the query string.
Request URL: http://upgrade.ade4local.com/Error/Error404/?404;http://upgrade.ade4local.com:80/legacy/?doc=filename
Response status code: 404
2019-09-26 20:57:34,300 DEBUG [88] BVNetwork.NotFound.Core.CustomRedirects.CustomRedirectHandler.get_Current -
[REMOTE_ADDR: <IP_ADDRESS>] [AUTH_USER: ] [HostName: P4ALAP-7221ZPR]
Begin: Get Current CustomRedirectHandler
2019-09-26 20:57:34,303 DEBUG [88] BVNetwork.NotFound.Core.CustomRedirects.CustomRedirectHandler.get_Current -
[REMOTE_ADDR: <IP_ADDRESS>] [AUTH_USER: ] [HostName: P4ALAP-7221ZPR]
Returning cached handler.
2019-09-26 20:57:34,307 DEBUG [88] BVNetwork.NotFound.Core.CustomRedirects.CustomRedirectHandler.get_Current -
[REMOTE_ADDR: <IP_ADDRESS>] [AUTH_USER: ] [HostName: P4ALAP-7221ZPR]
End: Get Current CustomRedirectHandler
2019-09-26 20:57:34,312 DEBUG [88] BVNetwork.NotFound.Core.RequestHandler.LogDebug -
[REMOTE_ADDR: <IP_ADDRESS>] [AUTH_USER: ] [HostName: P4ALAP-7221ZPR]
Not a 404 response.
Request URL: http://upgrade.ade4local.com/legacy/?doc=filename
Response status code: 200


AnimationKeyable - normalize() is not a function

So I wanted to test the glTF viewer with a simple mesh with simple animation and it just doesn't work.

The issue is here:

It calls "normalize" when the resKey (which is an AnimationKeyable), doesn't contain a normalize function.

Can you share the mesh that causes this?

Sure, I'm attaching it. Could you share an animated mesh which is working for you?
character_base_idle.zip

Fixed in 6eac172477085bd8f32e936be9d4239ace58bd4e


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_d6c2ir2yig/clone/recipe/meta.yaml:41: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_6aro9wo804/clone/recipe/meta.yaml:41: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
Errors were found


auto-ingest has multiple channels

a collaborator is trying to use auto-ingest, and has multi-channel data.
the current generatejson.py file only uses one channel in the example,
but the function seems to support multichannel data.
so, can we make the example have 2 channels?
@kunallillaney

@jovo So I think the best way to do this without having to hard-code 3-4 channels worth of variables is to explain how they can add dictionary entries to the channels dictionary variable in the ingest doc. @kunallillaney sound good to you?

@Aeusman examples are king.  so i vote both :-)

@Aeusman If is this done, then we can close it.

@kunallillaney @jovo I think this is done


chore(package): update config-expander to version 7.0.2

https://greenkeeper.io/

Coverage remained the same at 93.878% when pulling dcf635972a4bc2dea9c2889155fa9eb108d2f349 on greenkeeper/config-expander-7.0.2 into 8a9b1a20e76f163dcedfa0d88e04f5d821be8089 on master.

Codecov Report

Merging #16 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #16   +/-   ##
=======================================
  Coverage   93.87%   93.87%
=======================================
  Files           2        2
  Lines          49       49
=======================================
  Hits           46       46
  Misses          3        3

Continue to review full report at Codecov.

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


[Dependencies] CUDA compatibility issues in linux

Description of changes:
CUDA compatibility issues in linux - fixing torch to < 1.8.x
This fixeds CUDNN_STATUS_NOT_INITIALIZE errors during inference.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

When does this error occur? I just tested on linux with torch 1.8 (no GPU):
>>> predictions = predictor.predict(test_data)
>>> leaderboard = predictor.leaderboard(test_data)
                 model  score_test  score_val  pred_time_test  pred_time_val   fit_time  pred_time_test_marginal  pred_time_val_marginal  fit_time_marginal  stack_level  can_infer  fit_order
0      NeuralNetFastAI     0.85976     0.8648        0.583807       0.179888  53.181877                 0.583807                0.179888          53.181877            1       True          1
1  WeightedEnsemble_L2     0.85976     0.8648        0.587145       0.186265  53.185163                 0.003338                0.006376           0.003286            2       True          2

When does this error occur? I just tested on linux with torch 1.8 (no GPU):
It works on CPU instances. The issue happens when GPU is available and only during inference time.

Tracking:
https://github.com/pytorch/pytorch/issues/53336
https://github.com/pytorch/pytorch/issues/54047

Job PR-1023-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1023/2/index.html


Upgrade to V1.1.0 format Version

Upgrade to V1.1.0 -> https://github.com/UltraStar-Deluxe/format/issues/31
Add these:

[x] Audio
[x] Vocal
[x] Instrumental
[ ] Tags
[ ] ProvidedBy

Remove:
MedleyStartBeat and MedleyEndBeat is currently unsupported so nothing to do 😄
Check:

[] Deprecation of "diffrent time units"

There are currently no Tags for automation and ProvidedBy is for hoster
Everything is documented in the class.
So done i guess.


Add RegexSet functionality to C API

These functions implement a C interface to the RegexSet api.
Some notes:

These do not include start offsets as the standard regex functions
do. The reason being is down to how these are implemented in the core
regex crate. The RegexSet api does not expose a public is_match_at
whilst the Regex api does. I would actually like to change this if possible
as the inconsistency this makes between rure and rure_set types is
not great.

This only tests a complete compile/match mainly for sanity. One or
two more tests targeting the specific areas would be preferred.

Set matches take a mutable array to fill with results. This is more
C-like and allows the caller to manage the memory on the stack if
they want.

Wanted to make a request before targeting these changes to clarify.

These functions implement a C interface to the RegexSet api.

Thanks for doing this! At a first glance, this looks pretty good with a few nits.
So one thing that we should consider before merging this is how to incorporate rure_options into RegexSet compilation. We probably also need to think about flags as well.
The core problem you'll run into is that neither of these things is actually exposed in the regex crate proper.
Maybe we can come up with a straw man proposal for the C API and convince ourselves that it can be added later, so that we can merge this sooner.

These do not include start offsets as the standard regex functions
do. The reason being is down to how these are implemented in the core
regex crate. The RegexSet api does not expose a public is_match_at
whilst the Regex api does. I would actually like to change this if possible
as the inconsistency this makes between rure and rure_set types is
not great.

The inconsistency is in the regex crate as well.
The inconsistency exists for a reason. Getting the match offsets is hard.

This only tests a complete compile/match mainly for sanity. One or
two more tests targeting the specific areas would be preferred.

This is probably OK. Mostly, I think the C tests should just make sure that FFI is working. Testing the semantics of RegexSet is better suited for the regex crate proper. But I won't stop you from adding more tests. :-)

Set matches take a mutable array to fill with results. This is more
C-like and allows the caller to manage the memory on the stack if
they want.

Perfect.

So one thing that we should consider before merging this is how to incorporate rure_options into RegexSet compilation. We probably also need to think about flags as well.

The core problem you'll run into is that neither of these things is actually exposed in the regex crate proper.

Maybe we can come up with a straw man proposal for the C API and convince ourselves that it can be added later, so that we can merge this sooner.

I had a bit more of a look into RegexSet and would the following work for the actual crate implementation. Correct me if I've overlooked something:

Extend RegexBuilder with two new functions from_set and compile_set. from_set just takes a slice of patterns instead of a single. compile_set is similar but maps using From::RegexSet instead of From::Regex. This seems compatible since the types Regex and RegexSet just wrap an Exec type, with the bulk of the work already implemented within Exec.

And actually, just that seems like it would be sufficient for the lack of options to me. This can easily be exposed to the C API. This would be a backwards compatible API change, so would adjust the versioning however you are doing it. A corresponding compile_must for the rure_set type may be of use then at this point, too.

The inconsistency is in the regex crate as well.

The inconsistency exists for a reason. Getting the match offsets is hard.

If that is the case and I can just omit the start argument from the match functions.

This is probably OK. Mostly, I think the C tests should just make sure that FFI is working. Testing the semantics of RegexSet is better suited for the regex crate proper. But I won't stop you from adding more tests. :-)

I'll just add a regex failure test for sanity.
Thanks for the quick response, let me know if the RegexBuilder modifications outline sounds fine and if so, I'll implement those changes hopefully tomorrow.

I noted previously that we would need some extra functions in the regex crate. This seems like an incompatible change however (after reading the regex 1.0) RFC (at least in the short-term as you previously said). It looks like enough of the interface is public that we can just construct the RegexOptions ourselves and call use the ExecBuilder directly, though, so should still be feasible.

Sorry I'm dragging, but the past few days have been action packed (including a trip to the animal ER). Using RegexOptions and ExecBuilder is regrettable (they are technically exposed, but not really part of the public API), but I'm OK with it as long as there is a straight-forward way to expand the C API.
These options do need to get exposed in the regex crate proper though too. Your from_set and compile_set idea is one I've tossed around too, but my problem with it is that if you build with from_set, then it'd be nice to not call compile. I guess we could just return an error instead of ruling it out statically.
To be clear, I'm happy merging this PR without these options in the C API, as long as there's a reasonable path to adding them in the future.

Not a problem.
I'd like to get something thought out in that would minimize any breaking future api changes. I'd also like to avoid modifying the regex crate if possible right now.
With these goals in mind, here is what I suggest.

Add options to the c api regex set by using RegexOptions directly. This would be an implementation detail and can be adjusted to use a proper interface when one lands in the core crate.

Add a dummy start variable to the rure_set match functions. This is supported internally but no public way of acessing this is present. This unused field can be updated when support lands in the core crate. For the moment, it would require callers of this to use a 0 value to ensure future compatibility.

This should be flexible enough for future improvements without any breaking api changes.
Also, as an aside regarding the RegexBuilder and its compatibility with RegexSet. The cleanest way I see is to just create a seperate builder for a RegexSet itself. That is a topic for another time though.
I'll be offline till Monday but that day (which is thankfully a public holiday for me) I'll implement these and see how it all fits.

Sounds good. Two things:

You'll need to add RegexOptions to the internal module, which is in src/lib.rs.
You can implement the start functionality by using Exec and calling searcher.

In fact, I think both of these things means that you end up working around the use of RegexSet proper entirely.

Just a note that I've finished adding these features.

@tiehuis Thank you!


anti drag maybe?

this will gain a lot of new players + a lot of pkers!

https://gyazo.com/32234173b40d30b3dcd46e2e77df8d63
^this gyzo shows where i drag but we want a anti drag version where you are not able to drag at all meaning that when you try to move your items it wouldn't move @jpabeem do you get it?

https://i.imgur.com/JwEaPQp.gifv

Do not add that unless it is purely cosmetic. I'm a Dh'er and that would be very op

Maybe have a switch like click shift to enable no dragging then shift to allow it something like that

OSB prevents dragging when holding shift, so I do not see why we cannot add an equivalent feature.

I understand that Adam but hes talking about pking with this , holding shift the entire time while switching is hell why not just an off/on button

Just make the hotkey to be custom bind.

This is a duplicate of #1062 afaik

i agree with fox4148 i would like to enable and disable it.
having to hold shift for no drag its no fun you are not able to pk properly and will be the same as other clients, this client is awesome it has its own features i think there should be a feature where you can enable and disable it and not copy osb where they have to hold shift and it wouldn't drag. :(

¿porque no los dos?
Similar to @Fox4148 said, we could have it where right clicking the inventory icon can toggle between dragging and not dragging AND the shift action gets inverted. So by default (can drag freely), pressing shift prevents dragging, but when toggled (cannot drag freely), pressing shift allows dragging.

I agree with @jplsek.

Yes toggling options would make this great !

Duplicate of #1062


fix memory leak cause by the spanStore.(census-instrumentation/opence…

…nsus-go#1245)

when enable the spanStore and call startSpan and End in a loop, it cause memory leak. Found that it delete the wrong ptr in active set of spanStore in span's End() Method

@googlebot I signed it!

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

@googlebot I signed it!

Ah, I think I broke this when I added the SpanInterface.  I think we can fix this by changing the spanStore methods to use the SpanInterface instead of the *Span

sounds reasonable


Discord Bot cant send more than 8mb

So, discord bot cant send zip more than 8mb, to can send zip more than 8mb = you must have to buy server booster up to level 2
but, server booster is expensive, right?
so, to solve it = add HTTP + Password (Protect of leaking worlds and players)
and every backup, the password changed
Sorry if my grammar is bad

Solved = #2


Strange theme background color

VSCode Version:
OS Version: macOs Sierra 10.12.3 macbook 13'

Steps to Reproduce:

Install VS on mac

same, it seems to be only with dark themes.

https://github.com/Microsoft/vscode/issues/12473


Development: Add bamboo build agent container to atlassian compose file

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

There is a new bamboo build agent docker image available, that is build from this file:
https://github.com/ls1intum/Artemis-Local-Setup-Docker/blob/main/bamboo-build-agent/Dockerfile
This will replace the custom bamboo build for C and swift in the future.
The PR adds the needed parts to the atlassian.yml docker compose file, so the build agent service is created a long site the bamboo server.
Description

Adds the custom bamboo build image compose definition to the atlassian.yml file.
Steps for Testing

Use the docker compose file to run the atlassian services.
Go to this path, to approve the build agent /admin/agent/configureAgents!doDefault.action under Remote agents and then Agent authorisation
Approve the request
Wait some minutes until the build agent has finished its setup
Look for this line under the build agents executables (it should be automatically be detected):

Now bamboo can use this agent to run docker tasks (like build, publish images etc.)

Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Test Coverage

Class/File
Branch
Line

Screenshots

Please change the merge destination to the deployment develop branch. Other than that - it is looking good to me

@Mtze Done!


Behaviour of enableMoveInput(eventHandler, color = undefined)

Hi Stefan,
could you shed some light on the behaviour of enableMoveInput() when the color is not specified? In other words, how does (or could) the method determine which side to enable input for?
The reason for the question is hard to explain but I'm experiencing frozen boards (i have multiple concurrently open ones) when the color is specified but some seem to behave normally when the color is not specified.
Another thing i noticed is that Chrome gives me a memory low error in its dev tools when color is specified.
More info (maybe useful): say it is black to move. I click one of white's pieces, moveInputStarted is triggered for white but i cannot complete the move. I then click one of black's pieces and complete the move. the move is completed but i get the following error:

The error seems to be happening inside VueJS
This is how set up the inputHandler:
    activeBoard.board.enableMoveInput(
      (event) => this.inputHandler(event),
      activeBoard.turn
    )

I don't think I'm handling enablingMoveInput correctly but then again if I always move the piece of the side whose turn it is everything works perfectly.
I just think that for some reason, the board is getting confused about whose turn it is.
While on the topic of enableMoveInput() is there a reason why would a moveInputStarted event is triggered when a piece is clicked but no validateMoveInput event follows when a valid destination is clicked? I have noticed this happening when the board becomes unresponsive for either side.
thank you,

Hard to say, maybe you enable the MoveInput many multiple times and don't disable it.

Hey Stefan, I took a break and reviewed the code. Sure enough it was a bug in my code that was causing all the issues I was inquiring about. That caused the validateMoveInput event not to fire. It also caused the whole inputHandler() to misbehave when using the color parameter.
I still get the occasional Message length exceeded.... in Chrome and I'm unable to figure out what is causing it. Lots of reports online about that message in different environment and nothing specific.
So, cm-chessboard is still humming along beautifully and I'm very happy with what I was able to achieve with it. Can't wait to share the final product when it's done. Lots more to work on still.
thanks for getting back to me.

Hi! Many thanks for your feedback. Glad to hear that it kind of works now. Unfortunately i have not seen yet these "Message length exceeded" messages yet. For me it looks also more like a thing of Vue when I google about it. I look forward to read more about your project. Don't hesitate to ask, if you have more questions about the cm-chessboard or my other projects.

Ah! the Spectrum and its gummy keyboard. the good o'days! my next project is a time machine to travel back. I miss hearing the sound of the loading programs off the cassette tapes. Funny.

Haha, yes, like waiting 45 minutes for a program to load and having a loading error after 30 minutes. :) I loved the sound. Also the keyboard. It was very fast in coding because all possible commands have been as shortcuts on the keyboard. Therefore and because of the gummy keyboard, coding was more like kneading on the ZX Spectrum.


Fix the gesture handling

Fix a detection of a long press gesture in content VC
Fix a SwipeActionPanGesture is not working in the tracking scroll

Update DebugTableViewController to test it

@trungnguyen1791,
Could you please try this PR? This commit should fix the bug you reported at https://github.com/SCENEE/FloatingPanel/issues/8#issuecomment-439174889.

A swipe action in a table view should be working at 281504c.

@SCENEE Sorry for reply late:D. It's now working properly :D


Network Commissioning : Add platform driver support

Problem
Network commissioning clusters requires the platform to implement the platform driver.
(The list comes from src/platform directory)

[ ] [TBD]General OpenThread ThreadDriver
[ ] Ameba
[ ] Darwin
[ ] EFR32
[x] ESP32
[ ] Linux (Minor issue fix & small refactor)
[ ] P6
[ ] Tizen
[ ] Android
[ ] cc13x2
[ ] nrf
[ ] k32w
[ ] QPG
[ ] telink

Proposed Solution
<suggested fix, suggested enhancement>

@woody-apple Need to break this apart


exec doesn't work like other commands, specifically cd

Node version (or tell us if you're using electron or some other framework):
6.10.1
ShellJS version (the most recent version/Github branch you see the bug on):
0.7.7
Operating system:
Ubuntu 16.04
Description of the bug:
What I'd expect is for exec to always be equivalent to the special purpose commands. But as the example below shows, it's not. I found this confusing. Maybe this should be noted in the docs at least?
Example ShellJS command to reproduce the error:
#!/usr/bin/shjs
require('shelljs/global');

// creates `test.txt` in `./dir1/`
cd('dir1/');
exec('echo "test" > test.txt');
cd('../');

// creates `test.txt` in `./`
exec('cd dir1/');
exec('echo "test" > test.txt');
exec('cd ../');

Duplicate of #496
exec runs in a separate process, which makes things like cd, set, and other environment-modifying commands infeasible. Do you have a suggestion for how we might make this clearer? 😄
For what it's worth, I added a quick note in the README about it running inside a separate shell:

Not seeing the behavior you want? exec() runs everything through sh by default (or cmd.exe on Windows), which differs from bash. If you need bash-specific behavior, try out the {shell: 'path/to/bash'} option.


The select2('data') method was called on an element that is not using Select2

someone else has the same problem? [version: 1.0.0-beta.11]

I'm using the matcher option and seeing the same error message.

fixed with #115 in version 1.0.0-beta.13


[1.1.8] Different Clients injected for snc_redis.default[_client]

With the following configuration, I get different clients injected with the snc_redis.default[_client] service id with the bundle version 1.1.8:
snc_redis:
    clients:
        default:
            type:    phpredis
            alias:   default
            dsn:     "%redis_dsn%/0"
            logging: %kernel.debug%

In dev environment the client is an instance of Snc\RedisBundle\Client\Phpredis\Client but in prod environment its an instance of \Redis. I guess that's not how it should work, right?

I have the exactly same issue (type hinting broken in production environment). And it's a bad issue - I removed all type hints from my services injecting "redis.default".

Also just ran into this problem. Does it make sense to always wrap the client but only set the logger when logging is on? Otherwise we're stuck with ugly docs and no strict type checks like in RedisSessionHandler:
class RedisSessionHandler
{
    /**
     * Redis session storage constructor
     *
     * @param \Predis\Client|\Redis $redis   Redis database connection
     *
     * ...
     */
    public function __construct($redis, ...)
    {
        $this->redis = $redis; // <- Hopefully that's what we think it is
    }

    ...
}

I don't think returning different type of objects in different environments is a Good Thing. I can't think of worst scenario actually.

I've the same issue and in my opinion the object type have to be always the same.

I can't follow the reasoning behind this behaviour either. @snc, can you explain why?

There one case which is completely broken. If you try to inject the redis service to doctrine cache driver. It will work for logging: false but not for logging: true. You obviously cannot remove the type hint from there easily.

Facing the same issue: when logging is set to true, the doctrine cache provider (which relies on snc redis) gets a \Snc\RedisBundle\Client\Phpredis\Client injected, but it needs to receive a \Redis instance. This breaks the whole application when logging is enabled.

@dennis-hh What version of SncRedisBundle are you using ?

Hi, I've the same issue, my SncRedisBundle version is 1.1.10 and if I config with logging: true all work properly.
Thanks

@Pouix I'm using 1.1.10

@dennis-hh Try 2.0@dev version.
\Snc\RedisBundle\Client\Phpredis\Client has been rewritten and extends \Redis class.

Thanks for the update. Will do so asap. :)

In version 2.0.0  Redis clas is  still injected in prod env as before

I've got a failing service because I'm type-hinting Snc\RedisBundle\Client\Phpredis\Client in a service constructor (and injecting @snc_redis.cache), but with SncRedis v2.0.1 and PHP7's declare(strict_types = 1);, it is throwing a \TypeError exception.
Typehinting with \Redis does allow it to work.

The logging wrapper is to be considered an implementation detail, its job is to be invisible as stated above since 2.0.
Always assume there is no wrapper, type hint for \Redis and it will work fine, including Symfony autowiring, in every environment.


Internal server error if weight of non-hidden tests is zero

Describe the bug

When the summed up weight of all non-hidden tests (tests that aren't set to never) is zero an error occurs in the last Jenkins phase while sending the test results back to Artemis. The error does only occur if the sum of all the weights is zero and therefore a single non-zero weighted test leads to a successful Jenkins post actions phase. A picture of the exact error message from Jenkins is provided below.
To Reproduce

Create a new course and task
Push some tests to the task's tests repository
Edit the test's weight and visibility in order to achieve a zero sum of weights of all non-hidden tests
Trigger a build
Explore the post actions of the triggered build in Jenkins

Expected behavior

The expected behavior is that no internal server error occurs because zero is a valid input for a test weight.
Screenshots

Environment

Artemis 4.12.1

FYI @dfuchss @LDAP


Docker - MacOS - Build fails  - fails to patch mpfe

See details here: https://github.com/crops/poky-container/issues/16

The root cause is the file insensitive filesystem in newer versions of MacOS.
Workaround:
Use volume mapping for the tmp directory.
The README.md file had been updated with the necessary steps.


[CSL-2268] Fix restart logic in 'retrievalWorker'

Before the bugfix:

retrievalWorker starts, sets up an error handler mainLoopE
mainLoop starts
an error occurs in the mainLoop
the handler  mainLoopE catches it
mainLoop starts again, this time without an error handler
an error occurs in the mainLoop
thread dies

After the bugfix we restart the main loop with the error handler in place, so subsequent exceptions will be caught.

Does handleAll let async exception through?

Not in this branch, unfortunately.

Do we need to back port it to develop?

In some form, yes.

Do we need runIfNotShutdown? Can't we just killThread to stop this?

I'm not sure how exactly shutdown works, I placed this function where @georgeee suggested.

Overall it's fine, and does count as a fix. But ideally, an exception would kill the retrieval worker, and by extension the thread which spawned it (the main thread), and by extension the whole program.

I see where you're coming from. Indeed, we could adopt this policy and use exceptions only for scenarios that should outright kill the entire app. The problem is that there are many libraries that throw exceptions in situations that should be considered normal, and this includes most common libraries (including base). For example, trying to open a file that doesn't exist will result in an exception.
And the real problem is that the exceptions thrown by other libraries aren't reflected in the types or anywhere, so it's easy to accidentally let some exception through and it will kill the entire node, when we actually would prefer the worker to restart.
So the usual solution to this is to let async exceptions crash the app, but to use sync exceptions for "normal" scenarios since it's the approach used by so many libs.

I'm not sure how exactly shutdown works

In master branch shutdown doesn't work.

This PR:

Was created months ago, and now is lagging severely behind develop;
It touches delicate part of the logic;
Since then the wallet and the overall system seem to have stabilised.

For this reason, I'm inclined to follow the British's motto of "if isn't broken, do not fix it", and close this PR without merging it.


Sample bug

Search existing issues

[X] I have searched the issue tracker and confirmed that I was unable to find existing issues for the problem I am experiencing.

Describe the problem
Description
Release version
0.1.0
Platform
Windows
Operating system
Windows 11
Steps to reproduce the behavior
No response
Additional context
No response
Screenshots
No response
Anything else ?
No response

https://github.com/Azure/azure-functions-host/blob/d6bfa188521b213e65b8ddd037b958f9c2b6544a/src/WebJobs.Script.WebHost/WebJobs.Script.WebHost.csproj#L83-L84


Sign-in Error: Only loopback redirect uri is supported, but urn:ietf:wg:oauth:2.0:oob was found

Below is the error I am facing when trying to sign-in to Azure Storage explorer. It was working fine earlier and started getting this error after a week of not logging in.
{
"message": ""Only loopback redirect uri is supported, but urn:ietf:wg:oauth:2.0:oob was found. Configure http://localhost or http://localhost:port both during app registration and when you create the PublicClientApplication object. See https://aka.ms/msal-net-os-browser for details""
}

@SSG11082

What version of Storage Explorer are you using?
What Azure environment are you signing into? (Azure, Azure China, etc.)
What sign-in method do you have selected in settings? (Auth broker, default browser, integrated sign-in, etc.)

I'm having the same problem after updating:

Signing into Azure:

@SSG11082

What version of Storage Explorer are you using?  1.36.0
What Azure environment are you signing into? (Azure, Azure China, etc.) Azure
What sign-in method do you have selected in settings? (Auth broker, default browser, integrated sign-in, etc.)  - After I select Subscription and Azure, it redirects me to direct sign-in and then error. not giving any option to choose sign in method
Can you try doing "Help" -> "Reset" -> choose only authentication -> select reset/ok -> restart Storage Explorer and try signing in again : Tried it and did not work. Still facing the same error.

Hello

If you are still able to reproduce the issue, could you please do us a favor to turn on the verbose logging, collect the authentication logs and share the logs with us? The logs may help us locate the cause of the issue and make a fix.
There are detailed instructions in this section of our troubleshooting guide
https://learn.microsoft.com/en-us/troubleshoot/azure/azure-storage/blobs/alerts/storage-explorer-troubleshooting?tabs=Windows#authentication-logs

While we are investigating the issue, could you try changing the sign-in method to "default browser" and see if allows you to work around the issue as suggested by comments in this issue https://github.com/microsoft/AzureStorageExplorer/issues/8237? It would be very appreciated if you can reproduce the issue one more time and share the log with us.

Due to how widespread this issue is, we will be releasing 1.36.2 very soon to revert the default authentication method for Windows users.
For anyone having this issue, we invite you to do the following:
Help us diagnose

Install Storage Explorer 1.36.x.
Ensure you are signed out and that the "Sign in with:" setting is set to "Authentication Broker".
Follow the troubleshooting docs to gather authentication logs.
Please clear out any existing logs from the logs folder if you can.
Share your logs by posting a comment in #8237!

Unblock yourself

Install Storage Explorer 1.36.x.
Change the value for the "Sign In with:" setting to be "Default Web Browser".
Try signing in.

Thank you everyone for your patience and your help in diagnosing this issue!


Fix parsing of generic type parameters in arrow functions with JSX syntax

Potentially fixes #15713
This PR addresses an issue where the TypeScript parser incorrectly interprets generic type parameters in arrow functions as JSX elements. Specifically, the code const a = <T>(b: T) => b was being parsed as a JSX element instead of a generic type parameter.
Testing:
Added a new test case jsxGenericArrowFunction.tsx to verify the fix. Before the change, the following errors were observed:
jsxGenericArrowFunction.tsx(1,12): error TS2304: Cannot find name 'T'.
jsxGenericArrowFunction.tsx(1,12): error TS17008: JSX element 'T' has no corresponding closing tag.
jsxGenericArrowFunction.tsx(1,22): error TS1382: Unexpected token. Did you mean `{'>'}` or `>`?
jsxGenericArrowFunction.tsx(1,25): error TS1005: '</' expected.

After the change, these errors no longer occur.
This change ensures that generic type parameters in arrow functions are correctly parsed, improving TypeScript's type-checking and syntax parsing capabilities.
Additionally, as noted in the Design Meeting Notes, there has been anticipation for a fix to this issue from the TypeScript community

@microsoft-github-policy-service agree

This would technically be a breaking change for if someone wrote something like
const a = <Formatted>(b: T) => b</Formatted>

I'm surprised that we don't have a test like that at all though.

@DanielRosenwasser
You're right, I didn't take this case into account until the CI failed. Parsing this case as an arrow function and backtracking when we hit the JSX closing element would solve the issue, but it could potentially have exponential time complexity. If that's acceptable, it could be a viable solution.


How to login in AdminUI

I Have Seed the data by your readme, is there no user account? I Register an account , but when i open the admin website,it show that 'http://localhost:9000/Account/AccessDenied?ReturnUrl=%2F'  Access Denied!
I Can't login in the admin ,so i can't set anything.

Here is default admin user account:
https://github.com/skoruba/IdentityServer4.Admin/blob/master/src/Skoruba.IdentityServer4.Admin/Configuration/Identity/Users.cs
Thanks

thanks

May I close it? Thx

OK  close it
发自我的iPhone
------------------ Original ------------------
From: Jan Škoruba<EMAIL_ADDRESS>Date: Sat,Sep 28,2019 2:41 PM
To: skoruba/IdentityServer4.Admin<EMAIL_ADDRESS>Cc: cehui0303<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [skoruba/IdentityServer4.Admin] How to login in AdminUI (#366)
May I close it? Thx
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Fix CTS issue: Level information expected at least 2 but got 1

case: android.mediav2.cts.EncoderProfileLevelTest#
testValidateProfileLevel[8_c2.intel.avc.encoder_video/
avc_128kbps_176x144_15fps_yuv420flexible_2_0-bframes]
For Level 1b, we want to update the level anyway,
so we set it to next level in these cases
Tracked-On: OAM-118631

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

SUCCESS: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.

SUCCESS: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has started Engineering Build for this issue ,Please check the linked Tracked-On issue/Android CI Web  for more details.

SUCCESS: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.

SUCCESS: Android CI has completed Engineering Build for this issue.Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has started MERGE Build for this pr ,Please check the linked Tracked-On issue/Android CI Web  for more details.

Android CI has completed MERGE Build for this pr, build is SUCCESS. Please check the linked Tracked-On issue/Android CI Web  for more details. For Binaries: /cactus-absp-or-local/celadon-merge/510


Social share data and image

Social share data like og:image, description, twitter:title, etc.

Hi @sbddesign
Could you give more details about this issue? I would like to help.

@paulosacramento Basically, need to ensure that something nice looking is represented when each page of the website is shared to social.
From a design perspective, it means making a 16x9 graphic that will appear when a TC page is rendered to social media.
From a content strategy perspective, it means determining the description text that renders when we share it to social.
From a frontend dev perspective, it means going into the NextJS site and making this happen. (Needs to use the NextJS metadata object if memory serves, I think that is the most current way of handling these things in NextJS land)

@sbddesign This is what I have in mind.
Image

Title
Twelve Cash
Description
A simple way to share your bitcoin payment info with the world.
Can I improve it somehow?

Great, thank you. I will add this.

Thi wil lget merged in #44


Test Comp

Need
As a developer
I need a test comp
So that I can present the result of the test

Deliverables
A test component that presents the state, i.e pass or fail, and other details, i.e baseline/screenshot/diff or Error etc.
Solution
The Test comp will display the test title and its state.
The other details will be displayed by another component, that will be rendered by the Test comp through a transition, like jQuery toggle, but using CSS3 transition.

@andrei-picus-hs please review specs

@andrei-picus-hs please review my code.

@andrei-picus-hs

Finished review.

@andrei-picus-hs please review

LGTM


Make status messages expire

As we discussed, make them disappear after a short time? Or leave them but change the appearance (e.g. grey+strikethrough).

These messages will now fade after 6 seconds, live on the production site now
Let me know if this works out well in practice

That works! Maybe a little too quick. Would probably be good on the digiroms page too.

On QA the messages will go away after 60 seconds now, up from 6.  Digiroms page code sending will also remain for 60 seconds, and works with ACKs.

Great! Also make the message go away immediately if we change any of the related inputs (and stop listening for that ack code)?
I think there's something odd happening on the digiroms page when I change the input - it seems to disappear and then come back even though I haven't pressed the button.

See #10


Mccalluc/v0.0.16 rc

Add the spatial demo (which demonstrates bug #250). Other changes are automatically generated by the push-demo script.

Actually, can you review the last addition, too. Fixes #250.
(Down the road, I think each component should be responsible for saying which data layers it needs, but for now, this is sufficient.)

Looks good, I tested and the please wait now disappears on the spatial-only config.


test: udpated 3rd party api for Commandclick nav spec

replace 3rd API with TED
/ok-to-test<EMAIL_ADDRESS>

/ci-test-limit-count run_count=25


build: pin zstd-sys to 2.0.7

Which issue does this PR close?

Closes #.
Rationale for this change

I hit this while trying to upgrade arrow for datafusion.
Parquet depends on zstd-sys and datafusion depends on async-compression which then depends on zstd-sys via zstd-safe.
Parquet cannot use zstd-sys beyond 2.0.9 due to https://github.com/gyscos/zstd-rs/issues/269. And zstd-safe has two available versions 7.0.0 which depends on zstd-sys 2.0.7 and 7.1.0 on zstd-sys 2.10.0.
So to make parquet be compatible with projects use async-compression, the only available version to zstd-sys is 2.0.7
What changes are included in this PR?

Downgrade and pin zstd-sys to 2.0.7
Are there any user-facing changes?
Yes, the dependences

This patch needs to be included in the next release https://github.com/apache/arrow-rs/issues/5688 if possible

Maybe <= 2.0.9?

Maybe <= 2.0.9?

That looks better 👍 Changed in fc4c06a

Well, it turns out that cargo does not support "less than" comparison on patch position. The patch version is ignored in <2.0.10 and leads to a selection on 1.x.

package zstd-sys v1.4.3+zstd.1.3.4
... which satisfies dependency zstd-sys = "<2.0.10" (locked to 1.4.3+zstd.1.3.4) of package parquet v51.0.0 (/__w/arrow-rs/arrow-rs/parquet) links to native library zstd

I'm afraid we have to use =2.0.7 instead...

I'm somewhat inclined to think we should just remove the version pin, and document that people using wasm32 will need to manually pin zstd-sys themselves. We're creating pain for all of our users by pinning this crate, to save some pain for a very small subset of our community...

I'm somewhat inclined to think we should just remove the version pin, and document that people using wasm32 will need to manually pin zstd-sys themselves.

I agree that libs like parquet should not pin dependencies. This forces users to adopt the same pinned version, increasing the likelihood of conflicts. Instead of pinning versions downstream, it's better for us to collaborate upstream to address the issue.

I'm somewhat inclined to think we should just remove the version pin, and document that people using wasm32 will need to manually pin zstd-sys themselves. We're creating pain for all of our users by pinning this crate, to save some pain for a very small subset of our community... Ultimately if zstd-sys broke support for wasm32 it is on them to fix it

That's also an option. Cargo provides patch mechanism to override deps

Cargo provides patch mechanism to override deps

They shouldn't need to go that far, if they have a lockfile they can just use cargo update --precise, otherwise they can just declare an explicit dependency on zstd-sys and pin it there.

Removed them in d7d5e9b based on above discussion

Thank you all :heart:


Initial sauerbraten yml recipe.

This recipe generates an AppImage for the the FOSS game Cube 2 Sauerbraten. This is the initial recipe and may not work on all systems.

Ubuntu 22.04.1 LTS (Jammy Jellyfish) is way too new. Need to use the oldest still-supported Ubuntu LTS release, so that the resulting AppImage will run on all still-supported releases of Ubuntu.

Sure thing, will change it
On Sat, Sep 3, 2022, 07:35 probonopd @.***> wrote:

Ubuntu 22.04.1 LTS (Jammy Jellyfish) https://releases.ubuntu.com/22.04/
is way too new. Need to use the oldest still-supported Ubuntu LTS
release, so that the resulting AppImage will run on all still-supported
releases of Ubuntu.
—
Reply to this email directly, view it on GitHub
https://github.com/AppImage/pkg2appimage/pull/522#issuecomment-1236101606,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXAEJE6BY7MSSYAGRQGJFCTV4MZYJANCNFSM6AAAAAAQANRDKE
.
You are receiving this because you authored the thread.Message ID:
@.***>

I have updated the recipe.

Thanks @Hercules2048. Is it working for you? Which distributions and versions have you tested it on?

Please do test at least on the oldest still-supported LTS release of Ubuntu.


Refactor the factory method for reduction forecasters

Reference Issues/PRs
Refactors #757

What does this implement/fix? Explain your changes.
Refactoring the factory method in reduction forecasters.

creating new method which includes helper functions to check user inputs
keeping the old method but adding deprecation warning

@mloning What was the reason for adding ReducedRegressionForecaster in your PR? It looks identical to ReducedForecaster, and seems redundant.

I included it again because we didn't deprecate it properly when we removed it and a lot of tutorials are based on it.

Alright. Can you point me to an example tutorial, to check the latest deprecation works as expected?

Can't think of a tutorial on deprecation. We could add additional warning if the signature changed. But this way at least user don't get a ModuleNotFound error but a somewhat more helpful invalid input argument error and can then look up the new signature.

@mloning Sorry, I meant an example sktime tutorial in which ReducedRegressionForecaster is used. I will then locally run the sktime tutorials and see if the error message/deprecation message makes sense.

Ah - the forecasting tutorial in the examples folder uses it.

@mloning I looked at the forecasting notebook in examples. ReducedRegressionForecaster had already been updated to ReducedForecaster.
More importantly, the deprecation warning did come up for ReducedForecaster, so looks like that works fine, and it should work similarly for ReducedRegressionForecaster.  However, the notebook will need to be updated as the scitype names have changed. I will update it now (and update it to make_reduction)

a common motif is to print a warning message "is deprecated in v.123 and will be removed in future major release v.234", see also
https://docs.python.org/3/library/exceptions.html#DeprecationWarning

Closed in favour of #757


#383: Added support for collapsing duplicate dependencies and data re…

…quirements, as well as reporting referenced properties

Merging because this doesn't impact the production code base