fix(dashmate): set permissions for dashcore log file

Issue being fixed or feature implemented

Set permissions for dashcore log files to R+W for anyone. This is needed because we dashcore container being run as its own user (1000:1000), and dashmate cannot change file owners without sudo. This PR explicitly sets 666 mode for dashcore log file (~/.dashmate/logs//core.log)
What was done?

Added chmod command in the ensureFileMountExists
Set 666 mode for dashcore log files

How Has This Been Tested?

Locally
Devnet

Breaking Changes

No
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[x] I have assigned this pull request to a milestone

This issue does not reproduces on the macos, because of the tricky permissions system. This issue reproduces on the Ubuntu, devnet as an example. After start, core container continuously crash with message  Error: Could not open debug log file /var/log/dash/core.log
Test results:

I tested this branch on my local computer, dashcore container is working in both regular and local modes
Deploying nodes with v0.24-dev crash my dashcore containers on hpmns in the devnet. After redeploying my devnet with this branch applied, my dashcore containers start working correctly.


[Mutlisig UI] Multisig Transaction History

The transaction table should show:

Transaction ID
Status (Pending, Confirm)
Details of the transaction

@kanniec826 any difference from the existing transaction list UI?


Segmentation fault when using :mode => :objects

I use Rails 3.1.0 on ruby version:
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2011.03
in application.rb:
config.middleware.use ::Rack::PerftoolsProfiler, :default_printer => 'gif', :bundler => true, :mode => :objects

Traceback:
$ script/rails server -p8888
=> Booting Mongrel
=> Rails 3.1.0 application starting in development on http://<IP_ADDRESS>:8888
=> Call with -d to detach
=> Ctrl-C to shutdown server

Then I make request http://localhost:8888/?profile=true&times=3 and console show:
Segmentation fault

Closing for now (if you can reproduce and it's not a problem with perftools.rb, please reopen).


Adding a middleware for validating result field values

Hi @Aryainguz , I noticed that the result fields are expecting two values only (5 for frequently/affirmative and 0 for negative/rarely). But this is not being validated on the backend currently. It will be good to have a middleware validating these values.
Here I tried passing random values to the result fields and it ended up affecting the calculations.

@Aryainguz  If this issue is accepted, I would like to work on this for SWOC.

Great idea to add a middleware @poseidontor go ahead and feel free to reach out in case of any help needed

@Aryainguz I noticed that the Affirmative value for the question "Do you feel a sense of purpose and direction in your life?" is 6. For rest of the questions, the accepted value is either of 5/0. Is this intensional or a bug?
https://github.com/Aryainguz/Euphoria-Check-PERMA-Meter-Express/blob/5d04632c4de04eeb8b765def53192ad6bfe4b800/views/questions.ejs#L154C48-L154C48
If it's a bug, should I be opening a new issue or can I fix it in the PR for this one it self?

Hi @Aryainguz, I would to like to contribute to this issue. Can you please assign this to me?

I found a bug when I tried signing in with my email- it accepted for meet@j since I did not entered the complete email id which should be this<EMAIL_ADDRESS>it accepted my email, can I create one issue like validation of email id ? or I send a pr?


V1.5 implementation

Refactored from Email attribute to Website attribute
Phone default null value changed to '000' instead of '-'
Implemented command to load latest PSI value in Singapore
Updated the bugs found during Acceptance tests

#72  #38  #32  #70 #71

THANKS!


Bump kernels

Related to #950
Signed-off-by: Ettore Di Giacinto<EMAIL_ADDRESS>

Merging it, master is blocked..


Bugfix for GCC 9.

Closes #214

This could have been a small fix to just small fix to HAS_MEMBER_FUNCTION_NO_RTYPE but I realized that just using foo() const && = delete is probably the way to go for functions / operators that I want to disallow. You don't get the nice static assert message but it's much cleaner.
I also found a way to allow the UDC from Array< T > const & to ArrayView< T const > and from ArrayView< T > && to ArrayView< T const > while disallowing Array< T > && to ArrayView< T const >. Previously all of three were disallowed. The changes to the tests are to prevent the instantiation of Array< T const > which now produces a UDC never used warning from NVCC.


SCM plugin for Roundtable

Repository URL
https://github.com/AcornIT/jenkins-roundtablecommander
New Repository Name
roundtablecommander-plugin
Description
A SCM plugin for Roundtable TSMS - https://www.roundtable-software.com/products/roundtable-tsms/
This is a more centralised SCM with additional functionality for Progress/OpenEdge that we try to extend with a more distributed approach and include it in the CI/CD pipelines. The 'commander' part is the add-on library we've built in cooperation with Roundtable hence the name 'roundtablecommander' instead of just 'roundtable' to make it more clear.
GitHub users to have commit permission
@akera-io
Jenkins project users to have release permission
marian_edu
Issue tracker
GitHub issues

Security audit, information and commands
The security team is auditing all the hosting requests, to ensure a better security by default.
This message informs you that a security scan was triggered on your repository.
It takes ~10 minutes to complete.
Commands
The bot will parse all comments, and it will check if any line start with a command.
Security team only:

/audit-ok => the audit is complete, the hosting can continue :tada:.
/audit-skip => the audit is not necessary, the hosting can continue :tada:.
/audit-required => the superficial audit was not sufficient, a deeper look is necessary :mag:.
/audit-findings => the audit reveals some issues that require corrections :pencil2:.

Anyone:

/request-security-scan => the findings from the security scan were corrected, this command will re-scan your repository :mag:.
/audit-review => the findings from the audits were corrected, this command will ping the security team to review the findings :eyes:.
	It's only applicable when the previous audit required changes.

Only one command can be requested per comment.

(automatically generated message, version: 1.15.8)

:x: CodeQL Scan failed.
The Security team was notified about this.

/request-security-scan

:x: CodeQL Scan failed.
The Security team was notified about this.

The dependency should be in our Artifactory repo - https://artifactory.acorn.ro/artifactory/acorn-maven2.
I do think I've added that to the pom but I'm upgrading the jenkins version/name and scm developerConnection as per hosting checker recommendations.

/hosting re-check

/hosting re-check

/request-security-scan

The CodeQL Scan discovered 2 finding(s) :mag:.
For each of them, either apply the recommended correction, suppress the warning or provide a justification.
Once you're done, either re-run the scan with /request-security-scan or request the Security team to review your justifications with /audit-review.

Stapler: Missing POST/RequirePOST annotation
You can find detailed information about this finding here.
RemoteConfig.java#118
Potential CSRF vulnerability: If DescriptorImpl#doCheckCredentialsId connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST

RemoteConfig.java#99
Potential CSRF vulnerability: If DescriptorImpl#doFillCredentialsIdItems connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST

Hey @akera-io,
I took a look over your hosting request and have some feedback:

Please create a .github folder in the root directory with the following files and directories: https://github.com/jenkinsci/archetypes/tree/master/common-files/.github
Please create a Jenkinsfile in the root directory with the following content: https://github.com/jenkinsci/archetypes/blob/master/common-files/Jenkinsfile
Please create a .mvn folder in the root directory with the following files: https://github.com/jenkinsci/archetypes/tree/master/common-files/.mvn
Please delete https://github.com/AcornIT/jenkins-roundtablecommander/blob/master/.classpath and https://github.com/AcornIT/jenkins-roundtablecommander/blob/master/.project. These files don't belong here.
Can you clarify the involvement of Nicolas De loof in your hosting request, please? https://github.com/AcornIT/jenkins-roundtablecommander/blob/65667324c453e70a5c971097cf0fdd0599eef975/MIT-LICENSE.txt#L1
Please provide more constructive information in the README, what this plugin does, how it works, how to set it up etc.
https://github.com/AcornIT/jenkins-roundtablecommander/blob/65667324c453e70a5c971097cf0fdd0599eef975/pom.xml#L15 is obsolete and not considered by Jenkins, should be removed.
https://github.com/AcornIT/jenkins-roundtablecommander/blob/65667324c453e70a5c971097cf0fdd0599eef975/pom.xml#L22-L23 is obsolete and should be removed. This is no longer configured on a per-plugin basis.
Please update https://github.com/AcornIT/jenkins-roundtablecommander/blob/65667324c453e70a5c971097cf0fdd0599eef975/pom.xml#L34 pointing to the target location in the jenkinsci organization.
https://github.com/AcornIT/jenkins-roundtablecommander/blob/65667324c453e70a5c971097cf0fdd0599eef975/pom.xml#L47-L53 the bom should match your jenkins.version you depend on.
https://github.com/AcornIT/jenkins-roundtablecommander/blob/65667324c453e70a5c971097cf0fdd0599eef975/pom.xml#L57-L61 please include the a link to the source code of this dependency.
https://github.com/AcornIT/jenkins-roundtablecommander/blob/65667324c453e70a5c971097cf0fdd0599eef975/pom.xml#L62-L66 instead of shading jackson-databind yourself, you can depend on the jackson databind Jenkins plugin, which provides the functionality without the need to bundle it yourself: https://plugins.jenkins.io/jackson2-api/dependencies/
https://github.com/AcornIT/jenkins-roundtablecommander/blob/65667324c453e70a5c971097cf0fdd0599eef975/pom.xml#L111-L175 is obsolete and can be removed. These settings are already configured and inherited by the parent pom.
https://github.com/AcornIT/jenkins-roundtablecommander/tree/master/src/main/java/jenkins/plugins/roundtablecommander move your classes from this path to io.jenkins.plugins.roundtablecommander, to align with the group ID standards defined in the pom.xml
https://github.com/AcornIT/jenkins-roundtablecommander/blob/65667324c453e70a5c971097cf0fdd0599eef975/src/main/resources/index.jelly#L4 the link does not work. Please provide a working URL.

Hi guys,
first let me say wow, really impressed by the process and although this might not lead to anything it did help a lot.

https://github.com/AcornIT/jenkins-roundtablecommander/blob/65667324c453e70a5c971097cf0fdd0599eef975/pom.xml#L57-L61 please include the a link to the source code of this dependency.

I guess this might be a show stopper if everything used by the plugin must be open sourced, the Roundtable TSMS (the SCM solution we're extending) is a commercial product and although we have an agreement with them to build the connector that piece is still proprietary software so we do not have (nor we can provide) a public source code repository for this dependency :(
Other than that we can certainly fix all the other issues, however if the full open-source requirement is mandatory we will probably have to stick with the hpi manual deployment for the time being.
Thank you.
Marian

I guess this might be a show stopper if everything used by the plugin must be open sourced, the Roundtable TSMS (the SCM solution we're extending) is a commercial product and although we have an agreement with them to build the connector that piece is still proprietary software so we do not have (nor we can provide) a public source code repository for this dependency :(

Jenkins plugin dependencies have to be open source and publicly accessible too. Having the dependency public accessible on https://artifactory.acorn.ro/ui/native/acorn-maven2/ro/acorn/roundtable/roundtable-client/0.0.5/ does not suffice.

Jenkins plugin dependencies have to be open source and publicly accessible too. Having the dependency public accessible on https://artifactory.acorn.ro/ui/native/acorn-maven2/ro/acorn/roundtable/roundtable-client/0.0.5/ does not suffice.

Thanks and sorry for all the trouble, I think it's safe to close the issue for now.


add gtk-4-rs-docker

I noticed that gtk4 + rust is a popular boilerplate for building apps, so it will be cool if we add this packaging tool

Is there an AppImage made in such a way available for testing? I'd like to test first whether it works properly on the oldest still-supported Ubuntu LTS
Please don't edit other files than the .md

Thanks @Drsheppard01


Tag a version that works with the current nightly?

0.8.1 doesn't, so I can't have a REQUIRE in my packages that will download a working version for people on .4.

Bump

Pushed 0.8.2.


naabu: 2.1.9 -> 2.2.0

Diff: https://github.com/projectdiscovery/naabu/compare/refs/tags/v2.1.9...v2.2.0
Changelog: https://github.com/projectdiscovery/naabu/releases/tag/v2.2.0
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] Fits CONTRIBUTING.md.

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

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

1 package built:

naabu


Do JavaScript file parsing in JavaScript

This means we now extract the correct versions of JavaScript dependencies. Previously, if a package.json requested "^1.0.0", but we'd installed "1.0.1", the parser would incorrectly return "1.0.0" as the current dependency version. This fixes that as we're now relying on the lockfile rather than the package.json.
Key changes

Adds JavaScript helpers that use yarn as a library to parse the yarn.lock.
Introduces the concept of language helpers, which make it easy to shell out to JavaScript, and possibly for other languages in due course.

Caveats
Using bump core now depends on doing a yarn install in the helpers/javascript directory.

At the time I spent a while searching for a gem that would parse yarn.lock but sadly and unsurprisingly there's no such thing

👍


Add Yavrio to ConnectivityAppDefinitions.Codeunit.al

Fixes AB#496420

@jonathanwentworth please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Yavrio"

Availability update: We will publish a fix for this issue in the next update for release 23.
Build ID to track: 15318.

This should have gotten merged. Will reopen and try!


Formly ESLint rules

ESLint is a great tool that allows us to write consistent, clean code.
Formly as an additional framework in the tech stack is another layer of abstraction and can lead to confusion and mistakes from devs.
I propose adding custom ESLint rules to catch common mistakes and guide developers. Two that come to mind are:

Disallowing explicit definition of types that follow the pseudo-type pattern #presetName. The (not yet merged, see #3256) preset feature comes with new syntax which might be confusing to people (I have seen this first hand). This rule could help avoid mistakes. Also, I have already written this rule and would only need to port it to ngx-formly: Rule Code
Warning devs when they reassign single model properties. I have often had trouble when trying to reassign single model properties instead of creating a new model object like this.model = { ...this.model, xyz: 'test' }. Writing this rule might be a little complex but doable and would help prevent errors.

I'm sure there are many other formly-specific rules that could be written. They could be published as @ngx-formly/eslint-rules and imported. Please let me know what you think and if you have any ideas for additional rules, feel free to comment!

Hey @aitboudad now that #3256 is merged, I would like to start on this. Do you think it's a good idea?

I'd prefer to give that issue more time, we may revisite it after V6.
if you would like to work on some schematics tasks instead, let me know.

Yeah sure actually. There's no props converter yet, right?
Let me know what you have in mind for schematics.

Here are some tasks:

ng update: props and expressions +  https://github.com/ngx-formly/ngx-formly/blob/main/UPGRADE-6.0.md
Generating a custom type / custom wrapper


fixes #4

Fixes #4. See dylanblokhuis/svelte-feather-icons#10 for drawbacks, i.e. build time super slow if imported this way. With this, one can do
import { BsBox, Bs123, BsActivity, Icon } from "svelte-icons-pack";
Another option is to put an index.ts in each subfolder and it should only build that icon pack.
I opted to not use it given the slowness in build but it doesn't break existing behavior so thought I'd submit.
Please feel free to modify and submit another PR if you think its still worth it or if there is a way to avoid the build delay.

I think I found a way - will need more changes. Will resubmit once I get to it.


Projects API enhancements

Describe the changes you have made in this PR -

Serialize author_name in projects serializer.
Add selective including of author details.
Update/Add specs for above mentioned changes.

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Coverage increased (+0.07%) to 84.45% when pulling c874aca1627f9991f9e041802a517b9e66a0bf74 on Nitish145:project_enhancements into 0b0e7fc69deb771204aa2740deb55e4b81a0a228 on CircuitVerse:master.

@tachyons please have a look!!


default_time_range isn't working

After adding this to my dashboard YAML...
default_time_range: "P4W"

... I'd expect to open the dashboard and see the Last 4 Weeks. Instead I see the "All time" range.

This issue was fixed by #3182 and should be available in the latest release. The support for free form ISO duration is in #3175


collectionView: viewForHeaderInSection: does not work in iOS 5

I have tested this in 4.3 then in 5.  4.3 builds a nice header view for each header in my collection view.  Running it in 5 does nothing and seems to not create the headerView at all.

Are you using the latest version? I believe I recently fixed this.

Sorry, you are right, I had not upgraded.  My bad.


Mac M2 Unity：No code highlighting and automatic prompts with C#v2.0.372

Environment data
.NET SDK:
Version:   7.0.400
Commit:    73bf45718d
运行时环境:
OS Name:     Mac OS X
OS Version:  13.4
OS Platform: Darwin
RID:         osx.13-arm64
Base Path:   /usr/local/share/dotnet/sdk/7.0.400/
Host:
Version:      7.0.10
Architecture: arm64
Commit:       a6dbb800a4
.NET SDKs installed:
6.0.413 [/usr/local/share/dotnet/sdk]
7.0.400 [/usr/local/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.21 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 7.0.10 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.21 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.10 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Other architectures found:
x64   [/usr/local/share/dotnet/x64]
registered at [/etc/dotnet/install_location_x64]
Environment variables:
Not set
global.json file:
Not found
VS Code version:
Version: 1.81.1
Commit: 6c3e3dba23e8fadc360aed75ce363ba185c49794
Date: 2023-08-09T22:40:25.698Z
Electron: 22.3.18
ElectronBuildId: 22689846
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.5.0
C# Extension version:
v2.0。376
Unity Extension version:
v0.9.0

rollback to c# 1.26.0

For unity projects using legacy csproj, see https://github.com/dotnet/vscode-csharp/blob/main/README.md#how-to-use-omnisharp to switch back to using O# until we resolve https://github.com/dotnet/vscode-csharp/issues/5721
If you're on Unity 2021 or higher though, we recommend upgrading your Unity project's 'Visual Studio Editor' package as described in https://devblogs.microsoft.com/visualstudio/announcing-the-unity-extension-for-visual-studio-code/#getting-started-with-the-unity-extension which should allow it to load in the current version of the extension.


has no method forEach

I learned the heard way that you have to be careful with the key name of loaders.
I was following this tut http://goo.gl/tfVK4L and forgot to change the key loaders to loader once I implemented extract-text-webpack-plugin
            { // SASS & CSS FILES
                test: /\.scss$/,
                loader: ExtractTextPlugin.extract('css!sass')
            }

pay specific attention to..
loader: ExtractTextPlugin.extract('css!sass')
and not
loaders: ExtractTextPlugin.extract('css!sass')

I'm using webpack-2 and using use, I'm still getting this error.
part of the config:
        test: /\.scss$/,
        exclude: [
          /node_modules/,
          /\.mod\.scss$/,
        ],
        use: ExtractTextPlugin.extract({
          fallback: 'style-loader',
          use: [
            'dynamic-style-loader',
            {
              loader: 'css-loader',
              options: CSS_LOADER_OPTIONS,
            },
            {
              loader: 'postcss-loader',
              options: POSTCSS_LOADER_OPTIONS,
            },
            {
              loader: 'sass-loader',
              options: SASS_LOADER_OPTIONS,
            },
          ],
        }),
      },```

@iDVB dynamic-style-loader and style-loader seems weird

@iDVB options.fallback - {String}/{Array}/{Object}.Try to using fallback: ['style-loader', 'dynamic-style-loader']


chore: make v3 default

Description

Make v3 as the default
When loading V3 is default

Related issue(s)
Fixes #832

@Amzani Should I update the default doc as well?

/progress 80
Read to review

LGTM, however let's merge it once we fix https://github.com/asyncapi/studio/pull/842

/rtm

LGTM, however let's merge it once we fix #842

Sorry, didn't see this and added the ready-to-merge label by force of habit 😿 . Should I revert it?


Modify Makefile of Harbor based on photon to build adminserver

Coverage remained the same at 52.18% when pulling 537a3706ef458704fa5a1f628e96ba001589e2b8 on ywk253100:170221_makefile into 4bc69f294fd90e61f5aed61c72888f443b1622fb on vmware:configuration.

ac9487f63367        vmware/harbor-adminserver:v1.1.2   "/harbor/harbor_ad..."   8 minutes ago       Restarting (1) 8 seconds ago


Unnecessary GitGuardian Security Checks

GameMaker in general and a camera library like STANNcam does not use secrets, making the GitGuardian Security Checks unneeded.

i've no idea what that is, i'm up for removing it, but i don't know how 😬 Where is it?

Look in the Security tab on the repo.

there's no such option to turn it off

scratch that, it was in user settings, not repo settings. It's off now


'Cannot read property 'defineClass' of undefined' error

I've loaded the files according to the instructions.
https://github.com/nhnent/tui.time-picker/blob/production/docs/getting-started.md
    <link rel="stylesheet" href="https://uicdn.toast.com/tui.time-picker/latest/tui-time-picker.css">

    <script src="https://code.jquery.com/jquery-3.3.1.min.js"></script>
    <script src="https://uicdn.toast.com/tui.time-picker/latest/tui-time-picker.js"></script>
    <script src="/resources/js/tui-code-snippet.min.js"></script>

    <script>
        $(function () {
            var tpSelectbox = new tui.TimePicker('#timepicker-selectbox', {
                inputType: 'selectbox'
            });
        });
    </script>

But, I encountered this error.
Uncaught TypeError: Cannot read property 'defineClass' of undefined
    at Object.<anonymous> (no-conflict.js:13)
    at __webpack_require__ (no-conflict.js:13)
    at Object.<anonymous> (no-conflict.js:13)
    at __webpack_require__ (no-conflict.js:13)
    at Object.<anonymous> (no-conflict.js:13)
    at __webpack_require__ (no-conflict.js:13)
    at no-conflict.js:13
    at no-conflict.js:13
    at webpackUniversalModuleDefinition (no-conflict.js:11)
    at no-conflict.js:11

there is something wrong what I did?

self solved...
tui-code-snippet.js should load faster than tui-time-picker.js
so it should be
    <script src="/resources/js/tui-code-snippet.min.js"></script>
    <script src="https://uicdn.toast.com/tui.time-picker/latest/tui-time-picker.js"></script>


add docs on how to debug Pulsar Functions

rerun java8 tests
rerun integration tests

Python 🐍

rerun java8 tests

@Jennifer88huang or @Anonymitaet can any of you help reviewing this documentation change?

@sijie Glad to help.

hello @jerrypeng , logTopic and ./bin/pulsar-admin functions  command line parameters provided can help users to locate function-related problems. Do we consider adding them?
$ ./bin/pulsar-admin functions trigger
$ ./bin/pulsar-admin functions putstate
$ ./bin/pulsar-admin functions querystate
$ ./bin/pulsar-admin functions stats
$ ./bin/pulsar-admin functions status(getstatus)
...

@wolfstudy yup there are many ways to instrument a function.  We can keep adding to this document

@jerrypeng can you take a look at @Anonymitaet 's comments?

@Jennifer88huang @Anonymitaet thanks for the review.  Please take another look.

run cpp tests
run java8 tests

rerun cpp tests


Addressing VMXNET3 performance issues

Addressing VMXNET3 performance issues on Windows Server 2012 R2
This issue may be caused by Windows TCP Stack offloading the usage of the network interface to the CPU.
To resolve this issue, disable the several features that are not supported by VMXNET3 driver.
Steps to disable TCP chimney, AutoTuning, Congestion Provider, Task Offloading and ECN Capability

No changes...closing


Unable to install on windows 10

I have created a new conda environment with python 3.10 and then run the following commands on Windows OS, but failed to install scglue.
conda install -c conda-forge -c bioconda scglue
or
pip install scglue
Getting the following error,
FileNotFoundError: [WinError 2] The system cannot find the file specified
      # pysam: no cython available - using pre-compiled C
      # pysam: htslib mode is shared
      # pysam: HTSLIB_CONFIGURE_OPTIONS=None
      # pysam: htslib configure options: None

Hi @Khalid-Usman! Sorry for the late reply.
I'm afraid scglue doesn't support installing on Windows because it's dependency pybedtools, which subsequently depends on bedtools and htslib, does not support Windows. My suggestion would be to use a Linux machine or WSL.
Please let me know if there were further issues.


Error: 'Blob' is not a valid variable typeAL(AL0157)

I'm trying to find a way to open an image that is local to my extension and store it in a BLOB so that I can  display it on my report.
Unfortunately, i cannot find a way to have a var of type Blob anywhere on a report page other than if it is coming from a Table.
Can it be done?

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

ID: bb91a43d-5d1d-05b3-754e-652b3163f7cc
Version Independent ID: 0c8292ac-f940-7795-1d04-553b963f7dd9
Content: BLOB Data Type - Dynamics NAV
Content Source: dynamics-nav/BLOB-Data-Type.md
Product: dynamics-nav-2018
GitHub Login: @edupont04

I'm not from the staff, but since BC v.15 there is a new Codeunit that might help you:
https://github.com/microsoft/ALAppExtensions/blob/master/Modules/System/BLOB Storage/src/TempBlob.Codeunit.al

also you submitted issue to the NAV-Documentation where the TempBLOB Rec ist still available

Thanks. I'll keep this in mind when we move to 15, we are currently held back at 13 because of our ISV.

As far as I remember, TempBlob still works on BC13 it's just flagged as going inactive... Something like this

Hello @yannstlo and @CptBlaubart ,
Questions like this are best managed in the NAV community, such as here: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum


MINOR: Don't assume number of dns results (stabilize ClusterConnectio…

ClusterConnectionStatesTest#testMultipleIPsWithUseAll assume the number of addresses is 3. That assumption is unstable since it can be changed in the future. For example, the addresses of kafka.apache.org is changed to 2 recently.
It seems to me the test case is used to make sure all addresses (from resolving) are used when building connections. Hence, we can rewrite it by for-loop to make sure all addresses are used across connections.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@chia7712 I think this got fixed yesterday on trunk with the addition of a new HostResolver interface. Now we can precisely control what IPs are resolved during testing. https://github.com/apache/kafka/commit/131d4753cfed65ed6dee0a8c754765c97c3d513f

@mumrah Thanks for kind reminder. close this now.


[Snyk] Upgrade react-bootstrap from 2.10.0 to 2.10.1

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

The recommended version is 1 version ahead of your current version.
The recommended version was released a month ago, on 2024-02-10.

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

Check out a preview of your pull request here: https://app-servicecanadalabs-dev-pr-preview-1.azurewebsites.net


fix: Grammatical and Punctuational errors in the Home Page

I checked the paragraph on Grammarly, which displayed a lot of errors.
Fixed Paragraph:

Due to the prolonged pandemic, people are increasingly feeling isolated, which is likely to worsen their mental health. We feel like everything is just messed up, and we can’t do anything about it, and this feeling brings depression and mental illness. This website will be having information about how to deal with depression and how to keep good mental health. Experts say music really helps people who are going through any mental health issues, so taking that in mind, we have added a quiz that detects your mood and play songs, respectively. To boost morale/motivation, I have added motivational thoughts as well.

I would like to fix this error. Please assign me the issue. 😊

you are Good to go!


CraftTweaker complains about null file running script

General Information
This CraftTweaker file seems to work fine, but I still receive a null error on line 0 upon loading my world. Pastebin: https://pastebin.com/ZUzu26Jp
Describe the issue:
[20:27:11] [Client thread/INFO] [minecraft/GuiNewChat]: [CHAT] ERROR: [crafttweaker]: Error executing {[0:crafttweaker]: RootsAnimalHarvest.zs}: null
Have I simply done something incorrectly? I have a similar script for Untrue Pacifist entries which also yields the same result, regardless of whether I use an include method or prefix every command.

One of your entity names is incorrect then and is resulting in a null value being passed i n.

I'll scan through and try to find what is causing it, since I don't get a line number.  My only clue is that one of the entities is in both files. Thanks for the help!


Drop support for Python 2.7?

Are there any votes against dropping the Python 2.7 support?

Actually 0.7.6 version cannot be built with Python 2.7 because of using encoding argument to open function in setup.py.

Ah, you are right.
Since 0.7.6 (a week ago) nobody raised the issue, maybe is it a good indicator that the support could be dropped?

Anyway I'll release 0.7.7 with the support restored, thanks for the catch @daa :)


Add Threat prevention debug from gateway side

export TDERROR_ALL_ALL=5
fw -d amw fetchlocal -d $FWDIR/state/__tmp/AMW &> /var/log/amw_fetch_local_debug.txt

Check if $FWDIR/state/__tmp/AMW exists and present user with option of what policy to debug.
Need to test if this directory is removed if threat prevention policy is uninstalled.

Directory exists even if threat prevention is uninstalled. Added feature in next commit.


wiki: Installing NixOS from a USB stick

https://nixos.org/wiki/Installing_NixOS_from_a_USB_stick

We seem to have https://nixos.org/nixos/manual/index.html#sec-booting-from-usb nowadays. Should we close this?

Maybe merge the corresponding wiki info too.
2016-04-09 15:39 GMT-03:00 Tuomas Tynkkynen<EMAIL_ADDRESS>
We seem to have
https://nixos.org/nixos/manual/index.html#sec-booting-from-usb nowadays.
Should we close this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/issues/13310#issuecomment-207828201

Did this merge ever occur in full?

Dunno. After all the wiki is officially dead.


can i load css from public folder

can i load css from public folder is this best practice from reactjs

You can load CSS from a public folder if you're importing it from the index.html;
%PUBLIC_URL%/filename.css

You can load CSS from a public folder if you're importing it from the index.html;
%PUBLIC_URL%/filename.css

which is the best practice to import css from public or from components


TLS support for replicator

Currently, the replicator will not support SSL/TLS connections. LiteCore is defaulting to civetweb for WebSocket support. Unfortunately the TLS support in civetweb uses OpenSSL, which is large and has a poor security/quality record.
We'll need to either:

Give in and configure civetweb's OpenSSL support
Hack civetweb to use some other TLS library like mbed TLS
Replace civetweb with a library that supports a better TLS library

(The work will likely be in LiteCore itself, but it manifests as an issue for CBL-C so I'm posting it here.)

As of 2ca4b2afac16c6d71d5be6c4bbf01982fb74e134, we're now using libwebsockets and mbedTLS.
A remaining issue is that mbedTLS needs to be told what the trusted root certs are, and we don't have code or API for doing that (except on macOS.)

831c33567d56187415ce108a6fbeef8bb45c4600: OK, I've added code to read the system CA certs from /etc/ssl/certs if present (this is where OpenSSL installs them, apparently.)


hello

Hi. An interesting project. Can I see a demo photos or videos? thank

I'm a beginner. I have two dht22 sensor is connected to tx, and bmp180 connected to the SDA pin to GPIO2, SCL GPIO0 to the scheme:

I tried to change the pin file /app/sensor/dht22.c and bmp180.c but the temperature does not show. Tell me where else you need to change?


add initial app_for_spawners fixture

created an initial app_for_spawners fixture that performs the following tasks:

creates an instance of a mocked JupyterHub application with ssl protocol enabled if the value of the SSL_ENABLED environment variable is present
initializes and starts the mocked application with the keyword arguments
configures the mocked application to use the spawner class of the spawner it is being used in
configures the spawner to utilize the Kerberos protocol if the KEYTAB_PATH exists
yields the mocked application for testing session
disconnects the logs, clears the mocked instance and stops it when testing is completed

Reference https://github.com/jupyterhub/pytest-jupyterhub/issues/13

@GeorgianaElena 👋 your input is needed here

In the current pull request, I have made a basic app_for_spawners fixture that will allow me to build up and modify as I go. So far I have tested it against DockerSpawner, I am getting an error that the app doesn't have an attribute db which I am working to sort out. The next thing I want to do is test against YarnSpawner.

@Sheila-nk, sorry for taking me so long to respond! I was just wrapping up my feedback just now. Also, thanks for opening this PR for early feedback @Sheila-nk ✨
I suggest focusing on the following aspects in order to further refine the app_for_spawners implementation:

try not to include spawner-specific configuration (the configuration that makes sense for a specific spawner implementation, rather than for spawners in general)
focus on finding waya to make anything that seems specific to a spawner implementation be configurable by a spawner in its own test suite.
find common JupyterHub-specific configuration for the two spawners mentioned in the initial issue #13 (DockerSpawner and YarnSpawner)
the DockerSpawner and the YarnSpawner code linked in the initial issue, provide two examples on hub customization. One, where the hub is configured before the app is started and another where the hub's config options are modified while the hub application is running.
have app_for_spawners be the simplest hub app, that's responsible for starting and stopping the hub (like the one in the jupyterhub repo), but also for allowing a spawner to configure the hub
Fell free to add other helper fixtures and also to "copy" any other fixture from the two spawners to that seem to be helpful for a spawner in general and not just for that specific implementation (the copying part doesn't need to happen in this PR however)

This is really helpful feedback. Thank you!

With this recent commit, I was able to sort out the error I had mentioned earlier, that the mocked app doesn't have an attribute db. I am having trouble with the hub customization, I have not figured out how to go about that.


feat: implement merge-styles

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Not working in Laravel 10

Describe the Bug
I'm can't run your plugin. I'm not see stats showing in console after build. I'm not have optimized images.

Steps to reproduce

I have image by path: ./resources/img/logo.png
I'm run command: npm run build
I'll hope to see my image by path ./public/build/assets/img/logo.png

System Info
No error info. I'm not see stats showing in console after build

Used Package Manager
npm
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

You should add to Readme.md this code in app.js:
import.meta.glob([
    '../img/**',
])

It's resolve my problem

You should add to Readme.md this code in app.js:
import.meta.glob([
'../img/**',
])
It's resolve my problem

I have the same problem, the plugin doesn't run and I don't know why it could be.
Have you added that in resources/js/app.js?

I have the same problem, the plugin doesn't run and I don't know why it could be. Have you added that in resources/js/app.js?

Yes, I'm put to resources/js/app.js:
import.meta.glob([
    '../img/**',
])

and u should update folder name.


Chore/upgrade gatsby version

I noticed, that Gatsby v2 support has ended in April, so I upgraded Gatsby (and other packages). Upgrading meant some refactoring (mainly, with rich text). There shouldn't be any breaking changes, with, for example stripe.
Please, make sure to double test everything when reviewing this PR, I tried to do my best but it's possible that I missed something 😊
This PR resolves #25

Oh, shoot, it's too early so I committed the env-variable to this branch and realised it only after pushing 😅  oh well, I think it's ok to be here, so not doing a revert & force push.
I actually found a problem with the open letter form, so I need to investigate that a bit and fix it before merging this 😊

Oh, shoot, it's too early so I committed the env-variable to this branch and realised it only after pushing sweat_smile oh well, I think it's ok to be here, so not doing a revert & force push.

:D yeah, that shouldn't be a problem.

I actually found a problem with the open letter form, so I need to investigate that a bit and fix it before merging this blush

Oooh :eyes: Sure thing!


fix: [#4684] ESLint issues in botframework-streaming

Addresses # 4684
#minor
Description
This PR fixes all the new ESLint errors and warnings that appeared after the ESLint packages' upgrade in the botframework-streaming project.
Specific Changes

Removed 'only-warn' plugin from 'botframework-streaming/eslint.config.cjs' and its dependency.
All updated TS and JS files were due to prettier, mocha, and jsdoc new rules.
We replaced all test assertions that use expect(...).to.be.undefined / to.be.true / to.be.false, to to.equal(undefined | true | false) due to mocha rule.
Separated a few tests describe in different files due to mocha rule.

Testing
The following image shows that there are no more ESLint issues, and the tests are passing after the changes.

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

23 of 24 (95.83%)  changed or added relevant lines in 12 files are covered.
4 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.3%) to 84.355%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/botframework-streaming/src/webSocket/browserWebSocket.ts
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

libraries/botframework-streaming/src/webSocket/nodeWebSocket.ts
1
87.76%

libraries/botframework-streaming/src/namedPipe/namedPipeClient.ts
1
37.5%

libraries/botframework-streaming/src/webSocket/browserWebSocket.ts
1
42.42%

libraries/botframework-streaming/src/contentStream.ts
1
75.0%

Totals

Change from base Build<PHONE_NUMBER>2:
-0.3%

Covered Lines:
20433

Relevant Lines:
23064

💛  - Coveralls

/promoted 4825


Fastnlight: Watch micro-lube.com

Fastnlight requests the watch of the watch_keyword micro-lube\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

micro-lube\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Bug/escape chars

Fixes ##55, PXBLUE-<some ticket number>.
Changes proposed in this Pull Request:

Escape the vertical divider in readmes
Word the readme according to suggestion proposed in #55
Change the brandImage to say 'alpha' in localhost, 'beta' in angular-dev, and nothing otherwise

@daileytj I made some changes to the Drawer readmes. Please merge incoming dev changes in the next time you merge any conflicts

Ok, so what's happening here:

the three backticks syntax \`\`\` can escape | on GitHub but is not supported by storybook
including the | in between a pair of backticks is supported by storybook but not by GitHub

So right now I am going back to the "string|number" syntax


BoT/EoT chrono adaption

We now don't run into chrono panics when using TimeInterval::default()
I had to fix the time snap when it ran out of bounds
The raster-vector-join now emits nulls when querying with points that have TimeInterval::default(). It is quite slow because the GdalSource seems to collect every time interval from BoT to EoT. The aggregator, however, returns early if everything is null.
I changed From<i64> to TryFrom<i64> for TimeInstance. This is more correct but somewhat unergonomic.

 Begin of time und EoT auf Chrono anpassen

i think it is fine. please unify the source of  max min values.

0fc1dff changes the Vec to Iterator of tile parts such that the CI runs through.

Pull Request Test Coverage Report for Build 728941965

194 of 227 (85.46%)  changed or added relevant lines in 12 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.03%) to 81.977%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

datatypes/src/util/helpers.rs
9
10
90.0%

operators/src/processing/raster_vector_join/points.rs
7
8
87.5%

operators/src/source/ogr_source.rs
1
3
33.33%

datatypes/src/primitives/time_step.rs
13
16
81.25%

datatypes/src/primitives/time_instance.rs
14
19
73.68%

datatypes/src/primitives/time_interval.rs
28
33
84.85%

operators/src/processing/raster_vector_join/aggregator.rs
45
52
86.54%

operators/src/source/gdal_source.rs
33
42
78.57%

Files with Coverage Reduction
New Missed Lines
%

datatypes/src/primitives/time_step.rs
2
89.15%

Totals

Change from base Build 728724911:
0.03%

Covered Lines:
15647

Relevant Lines:
19087

💛  - Coveralls


Create separate Build All Release task

We were naively transforming the arguments of the returned Build All task to create one that would run a release version of Build All. Unfortunately the task.execution remained the same and so while upon inspection the task looked like it would run a release build it was not.
Create two separate versions of the Build All task, one for Debug and one for Release builds, and use the release version when building tests in release mode.

Are you saying even though it is printing -c release to the terminal it isn't running a release build

@adam-fowler correct, we print the task’s description which isn’t necessarily what is executed. What runs, in this case, is determined by the tasks execution which is a SwiftExecution with its own set of args. If you check the terminal panel after running a test in release mode you see a build all has run, but without -c release.

Verified

I'm not a great fan of this. It creates a release build all task which virtually nobody needs and is only needed for running tests in release. Do we need to include the release task in the list of tasks returned by the task provider?

@adam-fowler https://github.com/swiftlang/vscode-swift/pull/1005 should address that


The wiki is outdated

Page: https://gridcoin.world/wiki/
Please migrate the wiki pages from the original .us website, as the current pages are outdated.
If we will move 100% of wiki pages to here it is worth to upgrade the link in the footer as well, as atm it points to the .us website.

I am rather confused by this.  The original stated intention of the .world site was to be a separate, lighter landing page for Gridcoin marketing and to refer users to the .us site for more in-depth content.  Is the wiki not something we should be keeping separate on the .us site?

I was not aware of the intention. The website looks like atm more like a updated version of the .us website (consider those links in the bottom to the guides and wiki pages). So I made an assumption.

@barton2526 in this case this issue could be resolved I guess.

But there was an opinion to migrate things here
https://teamgridcoin.slack.com/archives/C6U7BQUR1/p1638291623035400

The opinion of one developer does not supersede the entire premise of the .world's site's creation

Then feel free to close this issue

I would prefer linking to the us site for the wiki if it can be done in an attractive way. There is no reason to have to maintain two separate versions of that.

Then feel free to close this issue

The intention was to leave it open for now for dialogue.  If everyone agrees, we can close it.

I would agree that the wiki should probably just be in one place and not duplicated

Theoretically, the problem of maintenance of 2 copies could be solved. It is possible to make the .us site to be a subpackage of the .world repo and use .md files from the subpackage. Will look ugly but will work. Same with guides.
Otherwise, we need to get rid of the wiki page completely and make the links in the footer point to the .us website.

So I guess we are getting rid of the wiki pages here and we will instead change the link to point to the .us website. Is this aligned? I will close this issue then and will add appropriate tasks later.

I would be interested in @jring-o 's opinion


ci: merge staging to master

This is an automatic PR generated by the pipeline CI/CD. This will be automatically fast-forward merged if successful.

Pipeline Attempt on 546736287 for 15afd89ba4f05143271f5cfa63400544606eb6ac
https://gitlab.com/MatrixAI/open-source/typescript-demo-lib-native/-/pipelines/546736287

Pipeline Succeeded on 546736287 for 15afd89ba4f05143271f5cfa63400544606eb6ac
https://gitlab.com/MatrixAI/open-source/typescript-demo-lib-native/-/pipelines/546736287


Add parameters to compute launch call

What this PR does / why we need it:
Add all launch parameters exposed by compute API(except for extendedMetadata)
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #156

unit tests
vtest_env /Users/shyaradh/oke/src/github.com/oracle/cluster-api-provider-oci/testbin; go test ./... -coverprofile cover.out && go tool cover -html=cover.out -o cover.html
Using cached envtest tools from /Users/shyaradh/oke/src/github.com/oracle/cluster-api-provider-oci/testbin
setting up env vars
?   	github.com/oracle/cluster-api-provider-oci	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta1	1.211s	coverage: 17.9% of statements
?   	github.com/oracle/cluster-api-provider-oci/cloud/config	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/ociutil	0.516s	coverage: 25.0% of statements
ok  	github.com/oracle/cluster-api-provider-oci/cloud/scope	167.121s	coverage: 73.2% of statements
?   	github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base/mock_base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine/mock_containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/controllers	28.270s	coverage: 69.0% of statements
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta1	1.954s	coverage: 10.1% of statements
ok  	github.com/oracle/cluster-api-provider-oci/exp/controllers	1.884s	coverage: 43.4% of statements
?   	github.com/oracle/cluster-api-provider-oci/feature	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/version	[no test files]

e2e test
Workload cluster creation
/home/ubuntu/go/src/github.com/oracle/cluster-api-provider-oci/test/e2e/cluster_test.go:50
  ClusterClass - with 1 control-plane nodes and 1 worker nodes [PRBlocking]
  /home/ubuntu/go/src/github.com/oracle/cluster-api-provider-oci/test/e2e/cluster_test.go:471
------------------------------
STEP: Tearing down the management cluster

Ran 5 of 22 Specs in 1808.906 seconds
SUCCESS! -- 5 Passed | 0 Failed | 0 Pending | 17 Skipped


[Feature]: Copy or Clone Object

Is your feature request related to a problem?
Just like the Carbon Date copy() or clone() function, Kasir maybe can have a function that will clone the object too.
Describe alternatives you've considered
A function that returns a clone of the object.
public functione clone(){
    return new clone $this
}

public function copy(){
   return $this->clone()
}

Additional context
No response
Terms of Agreement

[X] I have searched this issue I am experiencing in GitHub Issue and I ensure it is not a duplicated issue.

Closed in #33.


Basic: add a comment about the "complex" code

This addresses comments from Joe to document the special behaviour that
we do in the addSubsitution functions which cause a subtle failure on
Windows.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @jckarter

@swift-ci please smoke test

Thanks!

@swift-ci please smoke test


homebrew-ddev deprecation warnings

Run a Diagnostic and Paste Link Here

Describe the bug
Just got this while running brew upgrade.
Warning: Calling cellar in a bottle block is deprecated! Use brew style --fix on the formula to update the style or use sha256 with a cellar: argument instead.
Please report this issue to the drud/ddev tap (not Homebrew/brew or Homebrew/core), or even better, submit a PR to fix it:
/usr/local/Homebrew/Library/Taps/drud/homebrew-ddev/Formula/ddev.rb:16
Warning: Calling sha256 "digest" => :tag in a bottle block is deprecated! Use brew style --fix on the formula to update the style or use sha256 tag: "digest" instead.
Please report this issue to the drud/ddev tap (not Homebrew/brew or Homebrew/core), or even better, submit a PR to fix it:
/usr/local/Homebrew/Library/Taps/drud/homebrew-ddev/Formula/ddev.rb:17
Warning: Calling sha256 "digest" => :tag in a bottle block is deprecated! Use brew style --fix on the formula to update the style or use sha256 tag: "digest" instead.
Please report this issue to the drud/ddev tap (not Homebrew/brew or Homebrew/core), or even better, submit a PR to fix it:
/usr/local/Homebrew/Library/Taps/drud/homebrew-ddev/Formula/ddev.rb:18
Warning: Calling sha256 "digest" => :tag in a bottle block is deprecated! Use brew style --fix on the formula to update the style or use sha256 tag: "digest" instead.
Please report this issue to the drud/ddev tap (not Homebrew/brew or Homebrew/core), or even better, submit a PR to fix it:
/usr/local/Homebrew/Library/Taps/drud/homebrew-ddev/Formula/ddev.rb:19
Warning: Calling cellar in a bottle block is deprecated! Use brew style --fix on the formula to update the style or use sha256 with a cellar: argument instead.
Please report this issue to the drud/ddev tap (not Homebrew/brew or Homebrew/core), or even better, submit a PR to fix it:
/usr/local/Homebrew/Library/Taps/drud/homebrew-ddev/Formula/ddev.rb:16
Warning: Calling sha256 "digest" => :tag in a bottle block is deprecated! Use brew style --fix on the formula to update the style or use sha256 tag: "digest" instead.
Please report this issue to the drud/ddev tap (not Homebrew/brew or Homebrew/core), or even better, submit a PR to fix it:
/usr/local/Homebrew/Library/Taps/drud/homebrew-ddev/Formula/ddev.rb:17
Warning: Calling sha256 "digest" => :tag in a bottle block is deprecated! Use brew style --fix on the formula to update the style or use sha256 tag: "digest" instead.
Please report this issue to the drud/ddev tap (not Homebrew/brew or Homebrew/core), or even better, submit a PR to fix it:
/usr/local/Homebrew/Library/Taps/drud/homebrew-ddev/Formula/ddev.rb:18
Warning: Calling sha256 "digest" => :tag in a bottle block is deprecated! Use brew style --fix on the formula to update the style or use sha256 tag: "digest" instead.
Please report this issue to the drud/ddev tap (not Homebrew/brew or Homebrew/core), or even better, submit a PR to fix it:
/usr/local/Homebrew/Library/Taps/drud/homebrew-ddev/Formula/ddev.rb:19
To Reproduce

Expected behavior

Screenshots

Version and configuration information (please complete the following information):

Host computer OS and Version: [e.g. Windows 10, macOS Big Sur, Linux (distro), WSL2 (distro)]
Docker Desktop version if on macOS or Windows (from "About Docker Desktop")
ddev version information (use ddev version)
config.yaml contents for the misbehaving project (the part before the comments)
Do you have any custom configuration (nginx, php, mysql) in the .ddev folder? If so, have you tried without them?

Additional context

Thanks, I didn't notice this, but a colleague did, will get it fixed.

Also, https://github.com/drud/homebrew-ddev/issues/43


fix: unpin requirements to not trigger dependabot

Issue #, if available:
https://t.corp.amazon.com/D38327909
Description of changes:
Unpinning requirements to prevent dependabot from triggering. Pip will pull the latest versions.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Approving as code in not being used in actual solution.


Tests ignore custom board config overlays

Describe the bug
If you place a boards/my_board.conf in a test folder it is ignored if the test case calls out extra_args: CONF_FILE=some_config.conf.
To Reproduce
Steps to reproduce the behavior:

Use sensors.build.a_h: in tests/drivers/build_all/testcase.yaml as an example.
place boards/my_board.conf file along side tests/drivers/build_all/testcase.yaml, your board config will be ignored and not merged when case sensors.build.a_h is run.

Expected behavior
Board config overlays should never be ignored.
Impact
showstopper
Environment (please complete the following information):
CI system on Github.

This is the documented behaviour, see https://docs.zephyrproject.org/latest/guides/kconfig/setting.html?highlight=conf_file#the-initial-configuration

This is the documented behaviour, see https://docs.zephyrproject.org/latest/guides/kconfig/setting.html?highlight=conf_file#the-initial-configuration

Thanks for pointing that out.  How can we deal with this use case though? One option I see is editing the sample or test cmake file to include a board specific config...

@tejlmand is this something you could look into?

In #27755 I came across a lot of samples or tests where I just need to increase CONFIG_MAX_THREAD_BYTES for my board.

@rerickson1 Thanks for raising this.
Last week I actually noticed this myself, but there is a risk in simply changing current behavior.
There might be downstream users of Zephyr who relies on current behaviour, so that when they simply do:
cmake -DBOARD=my_board -Bbuild my_sample

then they know any board overlays will be included, but when they do:
cmake -DBOARD=my_board -Bbuild -DCONF_FILE=test_settings.conf my_sample

then they know that no overlays are included, so if we suddenly start including board overlays, then it might create a lot of issues to downstream users.
What I have been considering, is to extent the current functionality, so that if you specify a conf file following this pattern prj_<confname>.conf, then any board overlay of the form <board>_<confname>.conf will be considered.
That way you could have:
prj.conf
prj_debug.conf
boards/pinnacle_100_dvk.conf
boards/pinnacle_100_dvk_debug.conf

and then when using:
cmake -DBOARD=pinnacle_100_dvk -Bbuild <sample>

then prj.conf and boards/pinnacle_100_dvk.conf are used, and when doing:
cmake -DBOARD=pinnacle_100_dvk -Bbuild -CONFFILE=prj_debug.conf <sample>

then prj_debug.conf and boards/pinnacle_100_dvk_debug.conf are used.

Note, this is more an enhancement request than a bug.

Thanks, that makes sense. I agree that extending the functionality as you describe is probably the best approach.

Fixed here: https://github.com/zephyrproject-rtos/zephyr/pull/28039


[AutoDiff] Finish #adjoint expression (Sema and SILGen).

The purpose of #adjoint is to lookup and return the adjoint function
corresponding to a @differentiable function.

Change AdjointExpr to represent original function as a DeclName (and optional
base type) rather than an expression.

The argument of #adjoint(...) is a function identifier: this is better
modeled as a DeclName (and optional base type) rather than an expression,
which is overly general.
Representing the original function as an expression also makes
type-checking difficult. The relationship between the types of the original
and adjoint cannot be easily modeled using the constraint system.

SILGen AdjointExpr.

Rather than rewriting AdjointExpr to a different Expr in CSApply (e.g.
a DeclRefExpr referencing the adjoint function), custom SILGen is used
because AdjointExpr can represent functions that are normally inaccessible.
Such DeclRefExprs would be invalid in the AST.

Unfortunately, parseFunctionIdentifier in ParseExpr.cpp duplicates ~150 LOC from parseTypeIdentifier in ParseType.cpp.
parseFunctionIdentifier parses a "function identifier", which consists of an optional base type identifier followed by an unqualified DeclName. It is used for parsing the argument of #adjoint expression.
Examples:
// base type: none, decl name: "+"
#adjoint(+)
// base type: "A.B.C", decl name: "foo"
#adjoint(A.B.C.foo)
// base type: "Tensor<Float>", decl name: "convolved2D"
#adjoint(Tensor<Float>.convolved2D)

Most of the function is copied from parseTypeIdentifier, which parses the base type. However, custom backtracking logic is necessary to "undo" parsing the final identifier so that it can be parsed as a DeclName.
To avoid code dupe and use parseTypeIdentifier, I would need the ability to:

Backtrack the parser after calling parseTypeIdentifier to the position of the last "component"
"Pop off" the last component in a IdentTypeRepr

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

Thanks for reviewing!


Tooltip discrepancy #1012

I am reviewing this.

Comments from the review on Reviewable.io

Review status: 0 of 7 files reviewed at latest revision, 3 unresolved discussions.

addon/mixins/sl-tooltip-enabled.js, line 50 [r1] (raw file):
add "popover" property to this component. it is currently undefined.

addon/mixins/sl-tooltip-enabled.js, line 116 [r1] (raw file):
remove this.

addon/mixins/sl-tooltip-enabled.js, line 141 [r1] (raw file):
remove this.

Comments from the review on Reviewable.io

backlogged for future milestone.


[BUG] Palomabots are not showing successful bots in the MyBots Page

This Curve TWAP Bot https://etherscan.io/tx/0x7fb727ea0071dfab005ee612c6f3f88425f4902916512abb1370533e0f19e4f0 does not show up in the Mybpots Page so must not be in the bots API.

superseeded by https://github.com/VolumeFi/paloma/issues/2074


Task: Figure out how to enforce AS and NMP properties on DT filters without affecting the gain

This issue concerns the method _identify_uncertainty_upper_bound as it appears in the module src/dkpy/uncertainty_bound.py in the branch feature/22-add-equivalent-of-matlabs-ucover as of the time of this post.
As it stands, the method does not handle discrete-time (DT) models. However, most of the code present in this version is ready to handle them. The only exception is the portion enforcing the properties of asymptotic stability (AS) and nonminimum phase (NMP) on the final filter. This is easy to handle in the continuous-time (CT) case.
Is it possible to make a DT linear filter AS and NMP without affecting its gain?
A (possibly too obvious) solution would be to

convert it to CT,
enforce AS and NMP properties in CT, and
convert it back to discrete time.

Would this work? Which discretization method would be appropriate?

If you want, you can focus on just the CT case for now since D-K iteration is really only practical in CT. Maybe someone will want to use this library for uncertainty characterization in the DT case eventually, so it would be nice to support it if we can at some point.


Kernel: Poll: Code Suspected Logic Problem

I found that there is a bug in the poll source code, the code as below:
static inline int register_events()
{
int events_registered = 0;
for (int ii = 0; ii < num_events; ii++) {
	k_spinlock_key_t key;
	uint32_t state;

	key = k_spin_lock(&lock);
	if (is_condition_met(&events[ii], &state)) {
		set_event_ready(&events[ii], state);
		poller->is_polling = false;
	} else if (!just_check && poller->is_polling) {
		int rc = register_event(&events[ii], poller);
		**if (rc == 0) {
			events_registered += 1;
		} else {
			__ASSERT(false, "unexpected return code\n");
		}**
	}
	k_spin_unlock(&lock, key);
}

return events_registered;

}
register_event function code as below:
static inline int register_event()
{
switch (event->type) {
case K_POLL_TYPE_SEM_AVAILABLE:
__ASSERT(event->sem != NULL, "invalid semaphore\n");
add_event(&event->sem->poll_events, event, poller);
break;
case K_POLL_TYPE_DATA_AVAILABLE:
__ASSERT(event->queue != NULL, "invalid queue\n");
add_event(&event->queue->poll_events, event, poller);
break;
case K_POLL_TYPE_SIGNAL:
__ASSERT(event->signal != NULL, "invalid poll signal\n");
add_event(&event->signal->poll_events, event, poller);
break;
case K_POLL_TYPE_IGNORE:
/* nothing to do */
break;
default:
__ASSERT(false, "invalid event type\n");
break;
}
event->poller = poller;

**return 0;**

}
As you can see, rc is the return value of the function register_event. The judgment condition is whether rc is equal to 0. Analysis of the function register_event code shows that the function has only one return value 0, so if the function runs without an ASSERT error, the return value must be 0, so I think logic of this code is a bug and needs to be fixed.

This issue fixes by https://github.com/zephyrproject-rtos/zephyr/pull/31283

This issue fixes by https://github.com/zephyrproject-rtos/zephyr/pull/31283


Unhelpful stack traces for async functions with multiple async calls

What is your Test Scenario?
I have a test block that calls an async helper function. That helper function makes more than one async assertion. If any of those sub-assertions fail except for the first assertion, the error stack trace unhelpfully only lists the helper function and doesn't mention the line in the original test block where the helper function was called.
Since we use helper functions in multiple tests, this leaves us with no easy way to determine which helper invocation led to a logged error.
Here is a simple reproduction:
fixture`Example`

test
  .page('https://google.com')('loads Google', async t => {
    await myHelper(t)
  })

async function myHelper (t) {
  await t.expect(null).eql(null)     // assertion 1
  await t.expect(null).notEql(null)  // assertion 2
}

What is the Current behavior?
When myHelper fails at assertion 2, the stack trace looks like this:
   5 |    await myHelper(t)
   6 |  })
   7 |
   8 |async function myHelper (t) {
   9 |  await t.expect(null).eql(null)     // assertion 1
> 10 |  await t.expect(null).notEql(null)  // assertion 2
  11 |}

at <anonymous> (foo.spec.js:10:24)
at asyncGeneratorStep (foo.spec.js:1:114)
at _next (foo.spec.js:1:452)

This lists the correct line in the helper function where the assertion failed, but it then just lists the first line in the file instead of indicating where in the original test block the helper was called.
However, if I flip assertion 1 and 2, then the stack trace is more helpful:
   4 |  .page('https://google.com')('loads Google', async t => {
   5 |    await myHelper(t)
   6 |  })
   7 |
   8 |async function myHelper (t) {
>  9 |  await t.expect(null).notEql(null)  // assertion 2
  10 |  await t.expect(null).eql(null)     // assertion 1
  11 |}
  12 |

 at <anonymous> (foo.spec.js:9:24)
 at asyncGeneratorStep (foo.spec.js:1:114)
 at _next (foo.spec.js:1:452)
 at <anonymous> (foo.spec.js:1:617)
 at <anonymous> (foo.spec.js:1:358)
 at _myHelper (foo.spec.js:46:153)
 at myHelper (foo.spec.js:8:33)
 at <anonymous> (foo.spec.js:5:11)
 at asyncGeneratorStep (foo.spec.js:1:114)
 at _next (foo.spec.js:1:452)

The at <anonymous> (foo.spec.js:5:11) line correctly points to the line in the test block where myHelper is called.
What is the Expected behavior?
TestCafe should output the full, helpful stack trace from the second example output above even when it is not the first assertion that fails in the helper.

testcafe version: 1.12.0
node.js version: 14.15.5
command-line arguments: testcafe chrome -L
browser name and version: Chrome 89.0.4389.90
platform and version: macOS 10.14.6

Such a stack trace is caused by Babel preprocessing. We'll look into it.

I have this same issue. Trying to divide common test code into utility classes results in a stack trace that doesn't tell you anything about where the error started, only where it happened in the utility class.

Is it possible to raise the priority on this? At the very least, if it's possible to identify this problem and print a link back to this issue, that would've saved me hours of research. I thought it was a node flag I needed to set.

I think I found a workaround to this issue.

Install https://www.npmjs.com/package/trace
Run testcafe like this in your package.json scripts: npx --node-options='--stack_trace_limit=100 -r trace' testcafe ...

Note: I got errors on different lines when I included clarify, so I recommend not using it.

Hi @DanKaplanSES,
Thank you for the workaround.

@Aleksey28 No problem. Are there any updates about this issue? It can make life very difficult when you attempt to reuse test code.

We don't have any updates yet. We'll update this thread once we have any results.

Bumping. Is this still an issue?

Hello @DanKaplanSES ,
We understand the difficulties users may have with an async stack, but this is a low priority issue at the moment. We may reprioritize it in the future or if the number of requests for this feature grows

We also urgently need this fixed.

@Dvoreth
This issue has low priority so we do not have plans to start working on this in near future.

This still affects me and I would like it to be reopened.

Hello,
Unfortunately, it is currently difficult to determine the cause of this issue.
In addition, it has a low priority, so we do not have plans to start working on this issue in the near future.
We can reopen it if things change and the issue becomes a higher priority.

Hello! Thank you for reaching out about this issue.
At the moment, we’re unable to prioritize reevaluation of this matter.
We understand that it can complicate debugging, especially with CI and local testing. For now, you may find the workaround provided by DanKaplanSES helpful.
Currently, there are no plans to allocate resources to address this directly, but we appreciate your understanding.

Currently, there are no plans to allocate resources to address this directly, but we appreciate your understanding.

Would you accept a PR?

Hello @DanKaplanSES,
We always appreciate and encourage your contributions. You can review our contribution guidelines. Once you've submitted your pull request, our team will review it. If everything looks good, we'll merge it into the project.


allow build behind firewall blocking ssh

Firewalls that block external SSH access make this awkward to build.
This simply makes bower grab everything from GitHub over https instead

LGTM. Thank you.


Fix the include callback

as well as a few typos in the README file.

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

Comparison is base (130bf39) 89.50% compared to head (6cc709f) 90.12%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #30      +/-   ##
==========================================
+ Coverage   89.50%   90.12%   +0.61%
==========================================
  Files          19       19
  Lines         753      749       -4
  Branches      183      182       -1
==========================================
+ Hits          674      675       +1
+ Misses         48       45       -3
+ Partials       31       29       -2

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

LGTM - Optional, want to add a test case that meets your criteria per #29?src structure should be a good place to toss it. Added #32 to replicate

LGTM - Optional, want to add a test case that meets your criteria per #29? src structure should be a good place to toss it. Added #32 to replicate

will try to


Don't use jQuery

Not all websites use jQuery (eg Angular, React or VanillaJS apps).
Using jQuery isn't needed in your case:
http://youmightnotneedjquery.com/

I think you are right, but unfortunately I don't have time to improve this plugin.


FYI: public observation for Goofspiel

FYI I'm currently implementing public observations for Goofspiel.

Addressed by #344


Cannot Connect to mongodb 3.2.8

When trying to connect to mongodb version 3.2.8, it crashes with error,
bad argument in call to erlang:hd([]) in mc_connection_man:request_raw/4 line 34.
It seems that only mongodb 2.x is supported.
Following is shell output:
(mongo@dev)4> Database = <<"test">>.
<<"test">>
(mongo@dev)5> {ok, Connection} = mc_worker_api:connect ([{database, Database}]).
{ok,<0.108.0>}
(mongo@dev)6>
** exception error: bad argument
(mongo@dev)6> 11:18:50.890 [error] CRASH REPORT Process <0.108.0> with 1 neighbours crashed with reason: bad argument in call to erlang:hd([]) in mc_connection_man:request_raw/4 line 34

No, I have no issues with 3+ mongo.
Reason of this error is - empty list is returning on buildinfo cmd. This command is sending when you connecting to db.

I tried again , still does not work.
mc_connection_man:request_raw:35 Resonpse: [] ,
the received packet from server Packet.
<<246,5,0,0,40,0,0,0,3,0,0,0,1,0,0,0,8,0,0,0,0,0,0,0,0,0,
0,0,0,...>>  cause mc_worker_logic:decode_responses to turn an empty list,
because  this guard    byte_size(Data) >= (Length - 4) is false.

The command response seems not received by one frame, it should call NetModule:recv(Socket, 0, Timeout) more times. I wrote a new recv function to use in mc_connection_man:request_raw to handle this, and it fixed my issue.
recv(Socket, Timeout, NetModule) ->
  recv(Socket, Timeout, NetModule, <<>>).
recv(Socket, Timeout, NetModule, Rest) ->
  {ok, Packet} = NetModule:recv(Socket, 0, Timeout),
  case mc_worker_logic:decode_responses(<<Rest/binary, Packet/binary>>) of
    {[], Unfinished} -> recv(Socket, Timeout, NetModule, Unfinished);
    {Responses, _} -> Responses
  end.

Please try the latest develop branch. I added j3r0lin's recv.
Hope it helps you.

Thanks comtihon, it works now.


Move Provable<T> methods to a separate .provable namespace, on each provable type

Why: Provable<T> interface methods, like .toFields() and .fromFields(), are supposed to be an internal thing, used in circuit creation plumbing, or by advanced users to create general-purpose methods like Provable.if(). They work in very specific ways and circumstances. But, because of our interfaces right now, these functions have to be static methods on all our provable type classes, which are highly visible to users. So they are treated as public API. Sometimes they are used as conversion helpers, i.e.

trying PrivateKey.fromFields([x]) to convert a field element to a private key (which makes sense as a use case, but is not what fromFields() does and will create a PrivateKey with the wrong number of internal fields, that will cause breakage somewhere else)
using UInt64.fromFields([x]) to create a UInt64 (dangerous, as it bypasses the 64-bit range constraint we would usually add when instantiating a UInt64)

I think we should move those internal methods to less visible namespaces where they are clearly marked as serving a special purpose: PrivateKey.provable.{toFields, fromFields, ...}, UInt64.provable, etc
How:

Step 1: Create a type Provable<T> | { provable: Provable<T>}, and accept that as input in all APIs that right now expect a Provable<T>. Same for variants like FlexibleProvable<T> and ProvablePure<T>
Step 2: Deprecate provable methods on their current locations (hand-written provable classes, Struct, etc), and move them to .provable

To discuss: "provable" is quite an overloaded term here. We often use it to refer to code that becomes part of a proof. Here we use it for helper methods to define a type that can be used in provable code -- very different. What could be a less ambiguous namespace than .provable?

I think we should definitely still do this one, especially now that we got .provable types to work just as well as old ones everywhere


Omni Core v0.0.11-rc2 Takes too long to initialize

My system is Windows 7
I was using the Bitcoin Core 0.12.1 for win64, when I decided to switch to Omni.
But it didn't was running on my pc. I was told that likely my chain data were corrupted.
So I had to run the Omni Core wallet from the command prompt as
"omnicore-qt.exe -reindex"
in order to fix the blocks in my database. It took several days.
Now Omni is running well on my PC, but each time I initialize the wallet, it takes too long
"verifying blocks"... 1%... 2%... 3%... (an eternity), some times over an hour!.
Is there something I need to do to have run Omni Core in a "normal way"?
How can I fix this (If it can be fixed at all)?

Hi @jjmr007 welcome & thanks for the report!
Your experience is expected - the blockchain for Bitcoin Core 0.12 is not backwards compatible with Bitcoin Core 0.10 (which Omni Core 0.0.11 is based on).  This is why your local copy of the blockchain needed to be reindexed.
That sounds like an awfully long time to verify blocks - you can start with the parameter --checkblocks=1 to change the amount of latest blocks that'll be verified on startup from the default of 288 to 1.
Is this a relatively fast computer?
Thanks
Z

Hi @zathras-crypto ... thank you very much it worked perfectly, almost inmediately!
https://www.dropbox.com/s/n1rpps1eijkak8r/Omni%20Initialized.PNG?dl=0


download file from URL

Hi,
maybe it's a simple question, but I can't make it myself:
how has the function to look alike if I want to download an existing file?
like the filename is "image.jpg"?
thank you!

you can use bind() to force download() to act a callback to an ajax request that loads the existing file from a url on your server. with jQuery, that looks like:
$.ajax({         url: "/download.html",         success: download.bind(true, "text/html", "dlAjaxCallback.html") });
with vanilla, it would be more like:

var x=new XMLHttpRequest();
x.open( "GET", "/download.html" , true);
x.onload= download.bind(true, "text/html", "newLocalFileName.html");
x.send();

I might add an option in the future to allow passing just an exiting url, and have download() do the ajax itself. sounds like that would be helpful, and i like it to be helpful. thanks for the interest!

I couldt get either the vanilla, nor the JQuery suggestion to work.
It would be nice to download a file from an URL. I need a solution for an image file atm.

@LaKing Have you found a solution ?

In my javascript I use ...
                if (window.ActiveXObject || "ActiveXObject" in window) {
                    // IE
                    var _window = window.open(fileURL, '_blank');
                    _window.document.title = fileName;
                    setTimeout(function() {
                        _window.document.execCommand('SaveAs', true, fileName);
                        _window.document.close();
                        _window.close();
                    }, 2000);

                } else {
                    // for non-IE
                    var save = document.createElement('a');
                    save.href = fileURL;
                    save.download = fileName;
                    var event = document.createEvent("MouseEvents");
                    event.initMouseEvent("click", true, false, window, 0, 0, 0, 0, 0, false, false, false, false, 0, null);
                    save.dispatchEvent(event);
                }

IE does not name the file for some reason.

Because of the different onload event arguments, Binary files can't use the built-in download callback feature, and apparently jQuery can't handle fetching binary files like images... I may make binary support a bug and fix it, but for now, you can use a tiny vanilla JS callback to get it done:
http://pagedemos.com/xmymv4cgcajx/3/
		var x=new XMLHttpRequest();
		x.open( "GET", "/diff6.png" , true);
		x.responseType = 'blob';
		x.onload= function(e){ download(e.target.response, "icon.png", "image/png" ) }
		x.send();

i'm going to close this issue since there's a way to accomplish the goal as-is, but i will strongly consider tweaking it to get binary ajax operational.


Remove Set from the ECMAScript5 reserved words

Set is an ECMAScript 6 proposal; in 5 it must be required or manually defined. This fixes an erroneous "Redefinition of..." warning.
(Set is already in the newEcmaIdentifiers object, so it didn't need to be added)

Coverage remained the same at 94.82% when pulling 19cddd339b7847dca34e2fe23060a43d9586e6bc on AndrewLorente:master into 4e59553f7e2e09ba6c15643fdcb5b4416301148f on jshint:master.

Coverage remained the same at 94.82% when pulling 19cddd339b7847dca34e2fe23060a43d9586e6bc on AndrewLorente:master into 4e59553f7e2e09ba6c15643fdcb5b4416301148f on jshint:master.

s/proposal/object (it's not going anywhere).
For polyfills, you can simply do /* jshint globals: -Set */ to prevent the redefinition warning, I believe.
@rwaldron / @jugglinmike does that seem fair to you (given 54c29007f26a719e3c100f4088d92d190dd0192a?) or does it make more sense to only issue the redefinition warning if esnext is used

@caitp Your recommendation is definitely consistent with that commit, so if we want to "stay the course", then I agree with that.
But if we're opening this up for more general discussion, I think that it's a bit inconsistent for JSHint to require explicit opt in for certain parts of ES6 but implicitly enable other parts of the spec. See also Rick's comments on gh-1995

For polyfills, you can simply do /* jshint globals: -Set */ to prevent the redefinition warning, I believe.

Right. JSHint doesn't know what environment the source its operating on will run in, or what its capabilities are.

I think that it's a bit inconsistent for JSHint to require explicit opt in for certain parts of ES6 but implicitly enable other parts of the spec.

It seems wise to warn about redefinition of any built-ins, but take a look at this case: for Set, any code would be paving it V8, SpiderMonkey and JSC (not sure about Chakra)—regardless of whether or not ny esnext flag is set. Does that make sense?
(This is why I haven't rolled anything back yet)

any code would be paving it V8, SpiderMonkey and JSC (not sure about Chakra)

https://status.modern.ie/set?term=set --- IE11+, apparently

@rwaldron Oh, good point! In making that commit, your intention was to prevent
users from writing code that wasn't portable to future versions of the
language. I completely agree.
That said, that motivation honestly never occurred to me. You can even tell
from my previous response: I called the current behavior "inconsistent" because
I assumed that the change was simply assuming users were in an ES6-compliant
environment.
I think the reason I made that assumption is the same reason we have seen
multiple issues filed against this behavior. A warning like "Redefinition of
'Promise'." is inaccurate in ES5 environments and does nothing to explain the
logical motivation you just described.
I think this is simply a documentation problem. I think we should keep the
current behavior, but we should also (1) do a better job helping users
understand why JSHint is issuing a warning and (2) force them to think about
what it means to suppress that warning. I've opened gh-2172 to demonstrate what
I have in mind: a new option named futurehostile.

(1) do a better job helping users understand why JSHint is issuing a warning and (2) force them to think about what it means to suppress that warning. I've opened gh-2172 to demonstrate what I have in mind: a new option named futurehostile.

Great!

JSHint 2.8.1 (released today) includes a new option named futurehostile which we designed to be a more explicit way for users to enable the overwriting of future-reserved identifiers.

Thanks for handling this, y'all! :)


[BUG] Ошибка при запуске Bloxstrap (V 2.5.4)

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
I sit for an hour and try to solve the problem, I don't understand anything. Please explain, I'm stupid.. It has been broken for a long time, not how the problem with this is not solved(

I'll try it now, if it works, thank you very much!


Change Course-net logo

Course-net logo on the home page is different (Partners section). Please add the correct logo.

I will do it


Fix CASE invalid error expressions

Problem

Some VerifyOrExit did not set err =  properly in the
macro, which dropped errors to the floor and raised
warnings for some.

Change overview

Added err = XXX where missing in VerifyOrExist calls

Testing
Testing done: ran all unit tests

Great catch!
I run the following regex: VerifyOrExit\((.*), CHIP_ERROR and see two other files "infected" (unless not done intentionally):

https://github.com/project-chip/connectedhomeip/blob/master/src/controller/CHIPDeviceController.cpp#L915
https://github.com/project-chip/connectedhomeip/blob/master/src/platform/mbed/BLEManagerImpl.cpp#L624
https://github.com/project-chip/connectedhomeip/blob/master/src/platform/mbed/BLEManagerImpl.cpp#L790
https://github.com/project-chip/connectedhomeip/blob/master/src/platform/mbed/BLEManagerImpl.cpp#L817
https://github.com/project-chip/connectedhomeip/blob/master/src/platform/mbed/BLEManagerImpl.cpp#L1031

I fixed those too. Thanks for catching!

@tcarmelveilleux Needs rebase

I run the following regex: VerifyOrExit\((.*), CHIP_ERROR

How about we just add lints for this, since compiler warnings are not doing it?  Something like so:
# Copyright (c) 2021 Project CHIP Authors
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

name: Code lint

on:
    push:
    pull_request:
    workflow_dispatch:

jobs:
    code-lint:
        name: Codebase lints

        runs-on: ubuntu-18.04
        if: github.actor != 'restyled-io[bot]'

        steps:
            - name: Checkout
              uses: actions/checkout@v2
              with:
                  submodules: true

            # git grep exits with 0 if it finds a match, but we want
            # to fail (exit nonzero) on match.
            - name: Check for incorrect error use in VerifyOrExit
              run: |
                git grep -n "VerifyOrExit(.*, CHIP_ERROR" && exit 1 || exit 0

I can do a followup for that once this PR lands.

Maybe we could use constexpr functions instead of constructors in the error macros to make -Wunused-value do the job?
struct ChipError
{
    [[nodiscard]]
    ChipError() = default;
};

[[nodiscard]]
constexpr ChipError MakeChipError() { return ChipError{}; }

#define CHIP_ERROR_DEFINED_OLD_WAY ChipError{}
#define CHIP_ERROR_DEFINED_NEW_WAY MakeChipError{}

void foo()
{
    CHIP_ERROR_DEFINED_OLD_WAY; // does NOT generate warning
    CHIP_ERROR_DEFINED_NEW_WAY; // DOES generate warning
}

Maybe we could use constexpr functions instead of constructors in the error macros to make [[nodiscard]] do the job?

We could; we would need to change the existing places that do CHIP_ERROR(args) to make them benefit from this...


webpack 3 compatibility

Is<EMAIL_ADDRESS>really not compatible any more with webpack 3 ? (like suggested in the package file
https://github.com/webpack-contrib/url-loader/blob/v1.1.1/package.json#L42) ?

It is compatible, the peerDependency is just wrong/unneeded. In my opinion it should simply be relaxed, but there doesn't seem to be consensus to make this change (see https://github.com/webpack-contrib/url-loader/issues/142)

Just ignore the warning

ok thanks !

@michael-ciniawsky can we close issue?


How to tell CMake to use Anaconda environment?

When I add this to the CMake file:
execute_process (
    COMMAND bash -c "which python"
    OUTPUT_VARIABLE outVar
)

message(STATUS "path: ${outVar}")

I get the correct Python path for my current conda environment.
But, I am getting ModuleNotFoundError: No module named 'taichi' errors when running python ./ci/run_tests.py -l $TAICHI_C_API_INSTALL_DIR.

That's interesting, I am using CMake 3.26.1, but it sounds like it could be a similar issue.
I couldn't find any info about how to possibly intervene with FindPython that might help here though https://cmake.org/cmake/help/latest/module/FindPython3.html
Maybe the 'someone' you mentioned might know? Or do you remember anything else about their issue/solution?

Ok, changing this to 3.26 fixed it!
https://github.com/taichi-dev/taichi-aot-demo/blob/a6c35b6a8b1cc17768bc66ed628c2b44cf889bf7/CMakeLists.txt#L1


Gauges behavior

According to original Statsd:

If the gauge is not updated at the next flush, it will send the previous value. You can opt to send no metric at all for this gauge, by setting config.deleteGauges

https://github.com/etsy/statsd/blob/master/docs/metric_types.md#gauges
As I can see Brubeck by default doesn't send previous value if no data. Is it bug or feature?
Do you have an option for changing that?

It was my bad. Gauges are fine there.

@ipeacocks how did you solve it? I am in the same situation, brubeck sends my value just once.

Sorry, but I dont remember.

I also ran into this problem.
In the config exists expire parameter. The documentation about it does not say anything.
This parameter indicates time expire gauge in seconds.
HTTP Endpoint GET /metric/{{metric_name}} displays status expire.
My /etc/brubeck.conf
{
  "sharding" : false,
  "server_name" : "brubeck",
  "dumpfile" : "./brubeck.dump",
  "capacity" : 15,
  "expire" : 1800,
  "http" : ":8080",

  "backends" : [
    {
      "type" : "carbon",
      "address" : "localhost",
      "port" : 2003,
      "frequency" : 10
    }
  ],

  "samplers" : [
    {
      "type" : "statsd",
      "address" : "<IP_ADDRESS>",
      "port" : 8125,
      "workers" : 3,
      "multisock" : true,
      "multimsg" : 1
    }
  ]
}

This working for me. Gauges send 30 minute.


Add authorization support for Telemetry APIs

What this PR does / why we need it:
This adds support for the Telemetry APIs to be authorized.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
The authorization level for each API is given in the release note section. This will be tested with the UI integration (which will be done in a day or so).
Release note:

"metrics:get": "rule:admin_or_owner",
"metrics:collect": "rule:admin_or_owner",
"metrics:uploadconf": "rule:admin_api",
"metrics:downloadconf": "rule:admin_api",
"metrics:urls": "rule:admin_or_owner"```

@wisererik @leonwanghui @skdwriting @xing-yang @NajmudheenCT please review.

Coverage decreased (-0.009%) to 28.041% when pulling 9623834edd38d936b2e5a7f5f57196ac462f18d4 on rhsakarpos:auth into 8c504aa2abb9b57e7bb8dc2dea2a8ec2bad389d3 on opensds:development.

@rhsakarpos Please also pull a PR on opensds-installer project, thanks!


Fix typo in SHIT token symbol

Hello I am Shitoshi Crapamoto the creator of https://www.shitcoin.io/ A typo has appeared in our great and honorable symbol! Here is a PR to fix this travesty. Please get on the rocket ship and see you on Uranus!
Warm Regards,
Dr. Shitoshi Crapamoto
<EMAIL_ADDRESS>

MY MOTHER USES THIS SITE GUIZ CMON.
You can explain it to her, k?

Woohoo thank you! Yes I can explain to her please have her contact me<EMAIL_ADDRESS>and also send me her MEW address and I'll send some


Changes to storage need to be reverted also in Volumes

Type of change

Bugfix
Enhancement / new feature
Refactoring

Description
When changing between ephemeral and persistent storage of running cluster, it is not sufficient to just revert the PersistentVolumeClaim change. Also the Volumes list has to be patched. Otherwise a rolling update will still be triggered and the Cluster will get into strange state with two volumes using the same name (Volume and PVC).

BTW: I think the current solutions is not particularly good. This patch should do it for 0.3.0. But I think we need to make sure the storage change is captured and filtered out already in the model. With adding more storage types this kind of hack will get more and more complicated. It also relies on hardcoded order of volumes etc.

We need tests for this (should be easy to do in the KafkaAssemblyMockIT).

@tombentley Ok, I:

Added test for this
I also slightly improved the message a moved a bit more stuff into the new function. As discussed above
I will raise separate issue to better refactoring of this.

Hope this is OK for you so that we can move forward.