Uncaught TypeError: atom.workspace.getActiveTextEditor(...).getSelection is not a function

[Enter steps to reproduce below:]

...
...

Atom Version: 1.3.2
System: Mac OS X 10.11.3
Thrown From: advanced-new-file package, v0.5.0
Stack Trace
Uncaught TypeError: atom.workspace.getActiveTextEditor(...).getSelection is not a function
At /Users/madnomad/.atom/packages/advanced-new-file/lib/advanced-new-file-view.coffee:276

TypeError: atom.workspace.getActiveTextEditor(...).getSelection is not a function
    at AdvancedFileView.module.exports.AdvancedFileView.attach (/Users/madnomad/.atom/packages/advanced-new-file/lib/advanced-new-file-view.coffee:276:56)
    at AdvancedFileView.module.exports.AdvancedFileView.toggle (/Users/madnomad/.atom/packages/advanced-new-file/lib/advanced-new-file-view.coffee:295:8)
    at atom-workspace.<anonymous> (/Users/madnomad/.atom/packages/advanced-new-file/lib/advanced-new-file-view.coffee:76:73)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:536:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:359:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands
  2x -0:58 tree-view:toggle (atom-text-editor.editor.is-focused)
     -0:45.8.0 find-and-replace:select-next (atom-text-editor.editor.is-focused)
     -0:40.9.0 find-and-replace:find-next (atom-text-editor.editor.is-focused)
     -0:32.7.0 fuzzy-finder:toggle-file-finder (atom-text-editor.editor.is-focused)
     -0:29.9.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -0:29.9.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -0:25.7.0 core:undo (atom-text-editor.editor.is-focused)
     -0:24.4.0 core:save (atom-text-editor.editor.is-focused)
     -0:22.6.0 core:undo (atom-text-editor.editor.is-focused)
     -0:22.1.0 core:save (atom-text-editor.editor.is-focused)
     -0:15.2.0 advanced-new-file:toggle (atom-text-editor.editor.is-focused)
     -0:05.9.0 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -0:05.9.0 core:cancel (atom-text-editor.editor.is-focused)
     -0:02.6.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -0:02.6.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -0:01.1.0 advanced-new-file:toggle (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "excludeVcsIgnoredPaths": false,
    "disabledPackages": [
      "power-mode",
      "remote-sync"
    ],
    "themes": [
      "one-dark-ui",
      "atom-dark-syntax"
    ]
  },
  "advanced-new-file": {
    "caseSensitiveAutoCompletion": true,
    "createFileInstantly": true,
    "showFilesInAutoComplete": true,
    "suggestCurrentFilePath": true,
    "addTextFromSelection": true
  }
}

Installed Packages
# User
advanced-new-file, v0.5.0
file-type-icons, v0.7.4
language-blade, v0.16.0
minimap, v4.18.2
navigation-history, v0.1.8
remote-edit, v1.8.23

# Dev
No dev packages

use advanced-open-file instead

this should be closed. @Trudko what do you think about closing issues? as far as project abandoned

@iamstarkov definitely.


Implementation of ObservableHashSet

This is an implementation of INotifyCollectionChanged that is backed by a HashSet instead of a List. This will then perform better in Contains when there are a large number of elements, which is something that ObservableCollection doesn't do well with. It also implements Clear in a way that can be used by EF notifications because the items being cleared are passed in the event.
Copies the API surface of HashSet.
Also implements INotifyPropertyChanged/Changing for the Count property.
Does not have an inherent ordering and so does not have support for indexers, etc., or the notifications that go with these.

:shipit:


Add fuzzing by way of ClusterFuzzLite

This adds fuzzing by way of ClusterFuzzLite, which is a GitHub action that will perform a short amount of fuzzing for new PRs. The goal is to use fuzzing to catch bugs that may be introduced by new PRs.
I added a fuzzer that targets json::parse and currently set the timeout of CFLite to 120 seconds. CFLite will flag if the fuzzer finds  any issues in the code introduced by a PR.
To reproduce this set up the way ClusterFuzzLite does it (by way of OSS-Fuzz) you can do:
git clone https://github.com/google/oss-fuzz
git clone https://github.com/DavidKorczynski/meojson
cd meojson
git checkout clusterfuzzlite

# Build the fuzzers in .clusterfuzzlite
python3 ../oss-fuzz/infra/helper.py build_fuzzers --external $PWD

# Run the fuzzer for 10 seconds
python3 ../oss-fuzz/infra/helper.py run_fuzzer --external $PWD parse_fuzzer-- -max_total_time=10

Thanks for your contribution!
and you found a crash issue, we will merge it with this PR after fixing it.

@dantmnf  https://github.com/MistEO/meojson/blob/master/include/json.hpp#L2302 这里跳出后没做检查崩了！


POST requests (well createOrder) Not Authenticating

Hi Nick.
First, thanks the package! Appreciate it.
An Issue I'm having (node.js) is that  .createOrder isn't working for me? and giving 'Authentication Failed'. The strange thing is the private GET based requests seem to be working ok (eg .getAccountBalances() works fine - so I don't think its issues with keys etc
Have you had any troubles with this recently? or are you able to point me in the right direction?
I get:

Authentication failed.: failed POST request to url https://api.btcmarkets.net/order/create with message /order/create
1520155928444
{"currency":"AUD","instrument":"BTC","price":"1449006000000","volume":"500000","orderSide":"Bid","ordertype":"Limit","clientRequestId":"10001"}. Success: false. Error message: Authentication failed.

to me it leaves two possible problems the order/format of the POST variables or the integer format for prices.
I was looking in the package index.js and noticed:
const options = {             url: this.server + path,             method: method,             headers: headers,             timeout: this.timeout,             json: params         };
could this have anything to do with the params in the options does this need to be stringified or similar? (excuse the javascript ignorance)
Cheers,
Kane.

Price and Volume need to be a number and not a string.
Let me know how you go
Nick

Thanks Nick. That did the trick. (facepalm)

That's why I like TypeScript :-)
Good to hear it's all working now

I will check out TypeScript!. Though Ive just started learning Javascript (a couple of days ago) so I thought it a bit too much to start with :) I was using Swift but had some fundamental crypto issues :/


phosh: 0.21.1 -> 0.22.0

Description of changes
https://gitlab.gnome.org/World/Phosh/phosh/-/tags/v0.22.0
The evince dependency is required ( https://gitlab.gnome.org/World/Phosh/phosh/-/merge_requests/1102 for displaying PDF tickets (trains, concerts, etc.) on the lock screen.
Tested with the phosh nixos test, recently introduced by @zhaofengli in https://github.com/NixOS/nixpkgs/pull/173108.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

deployed to my pinephone and everything works as it should :+1:
aside: upstream lists phosh-mobile-settings as a recommended package to improve the base phosh experience since 0.21.0. there's an outstanding nixpkgs PR for that: would love some eyes or testers on it if any phosh users/reviewers reading this have an extra moment.


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1687 ms

Resolved: Bofrost.de performance has improved in b0c3271.


fortify dplyr::mutate

hey @cbeleites
I found this project "hpersec" very interesting.
I want to work on this issue!
Already I have completed the easy task and pasted the result as well as the profile link on the home page.
please assign me this issue.
thanks and regards
Vishesh Tripathi

@12VISHESH: great, go ahead. Do not hesitate to contact us and ask in case you have questions or doubts.

@cbeleites sir I mailed you already you!
Please have a look and reply for the same
Thanks and regards

Dear @12VISHESH,
I got your email and had a look at your github repo: that is fine as far as it goes, so easy test: passed :+1:
But I could not find any concrete question that I can answer?
Also, please rather than emailing me in person, please use the issues here (also please post your introduction on the GSoC issue): that way the other mentors can see and answer your issues and results as well.

@cbeleites
Thank you for assigning this issue to me .I will start work on this issue and solve this as soon as possible.
According to your last reply I haven't find gsoc issue where I can introduce my self.
Please Redirect to me on that for the same
Thanks and regards

see https://github.com/cbeleites/hyperSpec/issues/99

mutate and transmute for hypeSpec objects have been implemented. Going to close this now.


rm: CI LUKS encryption

Document the variables that control CI disk encryption.
PR Template and Checklist
Please complete as much as possible to speed up the reviewing process.
Readiness and adding reviewers as appropriate is required.
All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.
Readiness

[ ] Merge (pending reviews)
[ ] Merge after date or event
[ ] Draft

Overview
Why merge this PR? What does it solve?
Checklist

[ ] Run spelling and grammar check, preferably with linter.
[ ] Avoid changing any header associated with a link/reference.
[ ] Step through instructions (or ask someone to do so).
[ ] Review for wordiness
[ ] Match tone and style of page/section.
[ ] Run make linkcheck.
[ ] View HTML in a browser to check rendering.
[ ] Use semantic newlines.
[ ] follow best practices for commits.

[ ] Descriptive title written in the imperative.
[ ] Include brief overview of QA steps taken.
[ ] Mention any related issues numbers.
[ ] End message with sign off/DCO line (-s, --signoff).
[ ] Sign commit with your gpg key (-S, --gpg-sign).
[ ] Squash commits if needed.

[ ] Request PR review by a technical writer and at least one peer.

Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

Docs for 0dfa7a362818165fe158f0b26feffb6e0187643b are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2754/docs/artifacts/html/index.html

Docs for c99f43ce967630afc871535e7ac55f3ec9ecb487 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2755/docs/artifacts/html/index.html

Docs for 8f93315b9433cd968c343ac04eb4c70fffcf8140 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2756/docs/artifacts/html/index.html

@kprosise can we merge?

@kprosise can we merge?

We should follow the process—which I've admittedly been a bit lax about lately for small changes—for the doc PRs. So along with my review, we need (1) a peer…whoever else best understands the technical content/subject, and (2) Customer Success, such as @vanmaegima or @caiotpereira

@quaresmajose can you check/approve this change please? I have ignored documenting the actual passphrase configuration at this point since it requires a fix in initramfs and that needs to be planned.


Error building for Android - package android.support.annotation does not exist

Bug
Compilation error on version 0.1.1
node_modules/@react-native-community/masked-view/android/src/main/java/org/reactnative/maskedview/RNCMaskedViewManager.java:3: error: package android.support.annotation does not exist
import android.support.annotation.Nullable;
^
1 error
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':@react-native-community_masked-view:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Environment info

React native info output:
info Fetching system and libraries information...
System:
    OS: macOS 10.15
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Memory: 330.52 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.15.3 - /usr/local/bin/node
    Yarn: 1.16.0 - /usr/local/bin/yarn
    npm: 6.4.1 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
    Android SDK:
      API Levels: 23, 26, 28
      Build Tools: 23.0.1, 26.0.2, 28.0.3
      System Images: android-26 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
  IDEs:
    Xcode: 11.0/11A420a - /usr/bin/xcodebuild
  npmPackages:
    react-native: 0.61.2 => 0.61.2
  npmGlobalPackages:
    react-native-cli: 2.0.1
    react-native-git-upgrade: 0.2.7

Library version: 0.1.1
Steps To Reproduce

Build for Android
...

Describe what you expected to happen:

Use the library without issues

you may check this out
https://stackoverflow.com/questions/40380519/error-package-com-android-annotations-does-not-exist

Could someone please merge in the following pull request which fixes this issue, and push out a new release? This package is broken for Android on react 0.6x in the meanwhile.
https://github.com/react-native-community/react-native-masked-view/pull/21

Temporary workaround , using jetifier via mom postinstall script @tlapuste

This package is building successfully on android for initial react native application (react-native init) for react native version less and above then 60. On what android device you try to run?

merged #21


Another Broadcom Adapter

This one is Bluettoth 4.1, so I added another table for 4.1 compatible devices in README, hopefully that is OK?
Tested it and it worked,
thanks for awesome libraries

@leviathan88 awesome, thanks!


Internal error T3014

Visual Studio 2017
My code
static void Main(string[] args)
{
TrinityConfig.CurrentRunningMode = RunningMode.Embedded;
    }

Error occurred：Internal error T3014
Maybe I did something wrong. What should I do

@shyleoking please check and make certain you've included the graph engine core package. Also, what does your TSL file look like; post it so I can take a look-see.

https://github.com/shyleoking/GETestSolution   Thank @TaviTruman

@shyleoking the project seems to be structured well enough but the version of Graph Engine packages is very old; were you able to get a local build?

@shyleoking It looks likes the structure of the solution and project is fine; however, the Graph Engine packages referenced are very out of date; have you tried to get a local build? The current version of the GE is v2.0.0 but you'll need to generate a successful local build. Once you have a local build must update you must Graph Engine Package to the latest version.

I Cloned your sample and was able to recreate the T3014 error using the old GE packages; I updated the packages to the latest version, recompiled the program is it ran with no errors. Also make sure to install the Graph Engine VSIX extension for Visual Studio - you can find the VSIX installer in the "build" directory in the GE repro on your machine.

Cool！thank @TaviTruman

@shyleoking I think we can close this right?


[MISC] Expanded readme

The equivalent PyPI badge does not work for some reason :(
https://repology.org/badge/version-for-repo/pypi/bidsschematools.svg?header=PyPI

@effigies good?


[FIX-7338] set h2 for default DATABASE_TYPE for standalone-server

close #7338
set h2 for default DATABASE_TYPE for standalone-server

Codecov Report

:exclamation: No coverage uploaded for pull request base (2.0.1-release@1488851). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             2.0.1-release    #7339   +/-   ##
================================================
  Coverage                 ?   31.88%
  Complexity               ?     1569
================================================
  Files                    ?      432
  Lines                    ?    14573
  Branches                 ?     1447
================================================
  Hits                     ?     4647
  Misses                   ?     9476
  Partials                 ?      450

Continue to review full report at Codecov.

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


mark button as stable

Button is ready to be stabilized.

Looks good to me, but I think we still need to discuss synthetic events, as we have lost the nice 'click' event.

Agreed! Peli and I were just chatting about this...


[CARBONDATA-2149]Fix complex type data displaying error when use DataFrame to write complex type data

The default value of 'complex_delimiter_level_1' and 'complex_delimiter_level_2' is wrong, it must be '$' and ':', not be '\$' and '\:'. Escape characters '\' need to be added only when using delimiters in ArrayParserImpl or StructParserImpl.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3480/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3641/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2403/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2453/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3693/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2455/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3695/

anyone can help to review this pr?

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3877/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2632/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3656/

LGTM


feat: add vulnerability report verifier

Description
What this PR does / why we need it:

Adds a new vulnerability verifier for Sarif reports generated by Trivy + Grype, that can:

enforce report content matches a schema (Sarif is default supported schema for now but it is extensible)
enforce a MaximumAge duration (ex: '24h')
enforce against existence of disallowedSeverity levels (ex: 'critical')
enforce against existence of denylistCVEs (ex: CVE-2021-44228 log4shell)
introduce a passthrough flag which will bypass all checks and append sarif content in verifier report

Adds new e2e test for verifier
Adds unit tests
Adds new notation-nested-validation Constraint + Constraint Template

requires every artifact in the tree to be signed by notation

Adds new vulnerability-report-validation Constraint + Constraint Template

at least one vulnerability report must be valid and signed by notation

Documentation PR here: https://github.com/deislabs/ratify-web/pull/35

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #1096
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[x] Does the affected code have corresponding tests?
[x] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[x] Do all new files have appropriate license header?

Post Merge Requirements

[ ] MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

Thanks @akashsinghal the video does help to understand the experience.
The workflow for users to enable vuln policy is

install Gatekeeper and Ratify
apply constraint
apply template
apply verifier

One question: If users want to enable for example signature validation or another policy like SBOM, will they apply a different constraint and template?
Will this PR include all the rules below?

[ ] Image should have vulnerability report
[ ] Evaluate the latest report, and the latest report should be less than maximumAge (Did you attach annotations so that you can check the time?)
[ ] Validate the signature of vulnerability report if signature validation is enabled ( It seems users need to enable it in the template)
[x] No high and critical vuln
[ ] No CVE in denylist

Thanks @akashsinghal the video does help to understand the experience.
The workflow for users to enable vuln policy is

install Gatekeeper and Ratify
apply constraint
apply template
apply verifier

One question: If users want to enable for example signature validation or another policy like SBOM, will they apply a different constraint and template?
Will this PR include all the rules below?

[ ]  Image should have vulnerability report
[ ]  Evaluate the latest report, and the latest report should be less than maximumAge (Did you attach annotations so that you can check the time?)
[ ]  Validate the signature of vulnerability report if signature validation is enabled ( It seems users need to enable it in the template)
[x]  No high and critical vuln --> the video demoed this one.
[x]  No CVE in denylist

Thanks for taking a look @yizha1

One question: If users want to enable for example signature validation or another policy like SBOM, will they apply a different constraint and template?

If they want to enable signature validation at the image level then yes they will need to apply a separate policy. Same goes with SBOM.

Will this PR include all the rules below?

If the user wants to check ONLY for existence of report, they can apply Template + constraint and apply a vuln report verifier that does not specify any of the fields. This will essentially just do a schema check to make sure the report exists with a valid SARIF format.
Currently, the sample template at library/vulnerability-report-validation/template.yaml does not filter based on latest report. I can look into adding that. The "latest" report filtering can only be considered at rego evaluation since it's an aggregate report filter and NOT per report.


Create hints/rules for better user experience

6bcea67

https://github.com/sopra-fs23-group-11/sopra-fs23-group-11-client/commit/9334f546d27ee78ac3e930441ccb7f913c2b5c7d
Polish hint


Is tensorflow-gpu version same with just tensorflow for cpu?

I've developed some Keras code using tensorflow with cpu on Windows7 on my pc, and trained it with GPU on linux.
After complete training, I have moved the trained model files to my pc and used them without any problems. But I don't know what happened, it doesn't work on my pc. I guess it is from Keras and tensorflow version issue.
The linux's Keras and tensorflow version are Keras (2.1.5), tensorflow-gpu (1.4.1), and my pc's version are Keras (2.1.5), tensorflow (1.4.0.).
Below is the error msg.
Traceback (most recent call last):
  File "C:\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\tensorflow\python\client\session.py", line 1323, in _do_call
    return fn(*args)
  File "C:\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\tensorflow\python\client\session.py", line 1302, in _run_fn
    status, run_metadata)
  File "C:\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\tensorflow\python\framework\errors_impl.py", line 473, in __exit__
    c_api.TF_GetCode(self.status.status))
tensorflow.python.framework.errors_impl.InvalidArgumentError: indices[22,3] = 13257 is not in [0, 13004)
         [[Node: embedding_1/Gather = Gather[Tindices=DT_INT32, Tparams=DT_FLOAT, validate_indices=true, _device="/job:localhost/replica:0/task:0/devi
ce:CPU:0"](embedding_1/embeddings/read, embedding_1/Cast)]]

and
File "C:\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\tensorflow\python\client\session.py", line 1336, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: indices[22,3] = 13257 is not in [0, 13004)
         [[Node: embedding_1/Gather = Gather[Tindices=DT_INT32, Tparams=DT_FLOAT, validate_indices=true, _device="/job:localhost/replica:0/task:0/devi
ce:CPU:0"](embedding_1/embeddings/read, embedding_1/Cast)]]

and
File "C:\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\tensorflow\python\framework\ops.py", line 2956, in create_op
    op_def=op_def)
  File "C:\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\tensorflow\python\framework\ops.py", line 1470, in __init__
    self._traceback = self._graph._extract_stack()  # pylint: disable=protected-access

InvalidArgumentError (see above for traceback): indices[22,3] = 13257 is not in [0, 13004)
         [[Node: embedding_1/Gather = Gather[Tindices=DT_INT32, Tparams=DT_FLOAT, validate_indices=true, _device="/job:localhost/replica:0/task:0/devi
ce:CPU:0"](embedding_1/embeddings/read, embedding_1/Cast)]]

Exception ignored in: <bound method BaseSession.__del__ of <tensorflow.python.client.session.Session object at 0x000000001A8DE198>>
Traceback (most recent call last):
  File "C:\WinPython-64bit-<IP_ADDRESS>Qt5\python-3.5.4.amd64\lib\site-packages\tensorflow\python\client\session.py", line 696, in __del__
TypeError: 'NoneType' object is not callable

There were several similar questions, but anything were helpful. To use trained model file from Keras (2.1.5) and tensorflow-gpu (1.4.1), which Keras and tensorflow(cpu) version should I use? Of course I use same python version with the linux which is 3.5 on 64bit.

@bughunter99 If you use Keras (2.1.5) and tensorflow-gpu (1.4.1), use the same versions for pc. Make sure your model doesn't have explicit device allocations to gpu. As an alternative, you can also install tensorflow-gpu on the pc.

Closing this issue, feel free to reopen if problem persists.


Is there a way to read in original numbers?

The numbers in the Excel file are too large. So it is showed like a 3.31928E+11
Is there a way to read in original numbers?

@seong007 You should be able to inspect the value field of each cell to see the original stored value.  The display text replicates the Excel General format, which tries to limit the output to 11 characters.  The raw number is more than 11 characters in standard form so Excel and this library would default to formatting the number as exponential.
As an example, suppose you set Cell A1 of Sheet "Sheet1" to the value<PHONE_NUMBER>00.  Then you can find the raw value as follows:
> var XLSX = require('xlsx'); XLSX.readFile('test.xlsx').Sheets.Sheet1.A12
{ t: 'n', v:<PHONE_NUMBER>00, w: '3.31928E+11' }

The v field shows the numeric value and w stores the formatted text.
If you are using an output function like sheet_to_json there are options to display the raw value.

This should be better described in the README. Almost felt in the same rabbit hole.

@leodutra It's mentioned in https://github.com/SheetJS/js-xlsx#cell-object but should be spelled out more clearly.  The v field should mirror what is stored in an XLSX/XLS/XLSB file and the w field should give you the text you would see if you open the file in Excel.
One of the main reasons for storing the raw value separately from the formatted text is date handling: Excel natively stores dates as numeric codes.  For example, I set A1 to the formula =TODAY() and A2 to the date 2/19/17 and saved as XLSX.  The following lines from the worksheet XML correspond to the cells:
      <c r="A1" s="1">
        <f ca="1">TODAY()</f>
        <v>42787</v>
      </c>
...
      <c r="A2" s="1">
        <v>42785</v>
      </c>

You can see that the actual values stored are numeric.  The xlsx library looks at the cell style and process the format to give you the dates, but it still stores the original values:
  A1: { t: 'n', v: 42787, f: 'TODAY()', w: '2/21/17' },
  A2: { t: 'n', v: 42785, w: '2/19/17' } }

The leap year bug is the main reason for not automatically trying to convert those cells to date type: Excel, in replicating a Lotus bug, treats 1900 as a leap year even though it wasn't (years that are multiple of 100 but not a multiple of 400 are not leap years), so it's not clear how you would handle dates in that day and arithmetic that straddles the day.

@reviewher thank you for the explanation, good to know about the date.
I were talking specifically about that utils function sheets_to_json or something like that.
I don't know if it is intended for public usage but I found it in your demo page and found it the easier and cleaner way to produce a JSON from my sheets... but I found no clear explanation about this useful method or its "raw" optional.
I know the project is not v1.0, but there's a huge amount of stars, downloads and I think a relevant maturity.
Maybe we should produce more examples or produce a more detailed documentation. I'm willing to help.

@leodutra we expanded that part: https://github.com/SheetJS/js-xlsx#json please take a quick look and let us know how to improve it

We changed how dates are handled in 0.9.5:  Passing cellDates:true to the readFile function will generate raw dates when the format is a date, and passing raw:true will ensure that you get a real date object.

Well done and thanks. This is very straightforward.

I get the same for mobile numbers "9.18149E+11"  using XLSX.utils.sheet_to_csv

@shanthakumarf22 I'm not sure if this is the best solution, but this worked for me
Object.keys(ws).forEach(function(s) {
    if(ws[s].t === 'n') {
        ws[s].z = '0';
        ws[s].t = 's';
    }
});

By default sheet_to_csv take the formatted numbers.
- To avoid the formatted value and to take raw inputs (original values) you have to add parameter in sheet_to_csv method you have to set rawNumbers to true
Try this code
var csvFile = XLSX.utils.sheet_to_csv({ rawNumbers: true });


[DO NOT MERGE] Merge from apache 3.3 to ccs 3.3

NOTE: This PR should be merged using CLI to preserve commit history
remote check
#  git remote -v
apache-kafka	git@github.com:apache/kafka (fetch)
apache-kafka	git@github.com:apache/kafka (push)
confluentinc-kafka	git@github.com:confluentinc/kafka.git (fetch)
confluentinc-kafka	no_push (push)
origin	git@github.com:confluentinc/ce-kafka.git (fetch)
origin	git@github.com:confluentinc/ce-kafka.git (push)

create the branches for the PR
# git checkout -b confluentinc-3.3 -t  confluentinc-kafka/3.3
confluentinc-3.3 # git checkout -b merge-from-apache-3.3-on-11-08

merge conflicts
merge-from-apache-3.3-on-11-08 # git merge apache-kafka/3.3 --log=10

Auto-merging tests/kafkatest/version.py
CONFLICT (content): Merge conflict in tests/kafkatest/version.py
Auto-merging tests/kafkatest/__init__.py
CONFLICT (content): Merge conflict in tests/kafkatest/__init__.py
Auto-merging streams/quickstart/pom.xml
CONFLICT (content): Merge conflict in streams/quickstart/pom.xml
Auto-merging streams/quickstart/java/src/main/resources/archetype-resources/pom.xml
CONFLICT (content): Merge conflict in streams/quickstart/java/src/main/resources/archetype-resources/pom.xml
Auto-merging streams/quickstart/java/pom.xml
CONFLICT (content): Merge conflict in streams/quickstart/java/pom.xml
Auto-merging gradle.properties
CONFLICT (content): Merge conflict in gradle.properties
Auto-merging core/src/test/scala/unit/kafka/utils/TestUtils.scala
CONFLICT (modify/delete): config/kraft/README.md deleted in apache-kafka/3.3 and modified in HEAD. Version HEAD of config/kraft/README.md left in tree.
Auto-merging build.gradle
Recorded preimage for 'gradle.properties'
Recorded preimage for 'streams/quickstart/java/pom.xml'
Recorded preimage for 'streams/quickstart/java/src/main/resources/archetype-resources/pom.xml'
Recorded preimage for 'streams/quickstart/pom.xml'
Recorded preimage for 'tests/kafkatest/__init__.py'
Recorded preimage for 'tests/kafkatest/version.py'
Automatic merge failed; fix conflicts and then commit the result.

git status
git status
On branch merge-from-apache-3.3-on-11-08
You have unmerged paths.
...
Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by them: config/kraft/README.md
	both modified:   gradle.properties
	both modified:   streams/quickstart/java/pom.xml
	both modified:   streams/quickstart/java/src/main/resources/archetype-resources/pom.xml
	both modified:   streams/quickstart/pom.xml
	both modified:   tests/kafkatest/__init__.py
	both modified:   tests/kafkatest/version.py

fixed the conflicts in above files:

kept the file: config/kraft/README.md
fix the version conflict: pick the version 7.3.0-0-ccs

    <groupId>org.apache.kafka</groupId>
    <artifactId>streams-quickstart</artifactId>
    <packaging>pom</packaging>
<<<<<<< HEAD
    <version>7.3.0-0-ccs</version>
=======
    <version>3.3.2-SNAPSHOT</version>
>>>>>>> apache-kafka/3.3

the steps used to push the change
confluentinc-3.3 # git pull
confluentinc-3.3 # git checkout merge-from-apache-3.3-on-11-08
merge-from-apache-3.3-on-11-08 # git merge confluentinc-3.3
merge-from-apache-3.3-on-11-08 # git push confluentinc-kafka merge-from-apache-3.3-on-11-08:3.3

merged with yellow build, with the following flaky test
kafka.network.ConnectionQuotasTest.testListenerConnectionRateLimitWhenActualRateAboveLimit()


simplify does not remove colinear edges.

Expected behavior and actual behavior.
Expected colinear edges to be dissolved after calling simplify, but after calling simplify, the three vertices (y=3.5) are still present. When the polygon is normalized prior to simplify, the points are dissolved as expected. There should be a bug in Pygeos that forgets to consider effects on the first and last elements of the coordinate string.
Steps to reproduce the problem.
from shapely import Polygon, simplify

s =Polygon([(18.5, 3.5),(15.5, 3.5),(15.5, 0.0),(20.0, 0.0),(19.286758931477863, 3.5),(18.5, 3.5)])
simplify(s,1e-3)
# output: <POLYGON ((18.5 3.5, 15.5 3.5, 15.5 0, 20 0, 19.287 3.5, 18.5 3.5))>
simplify(s.normalize(),1e-3)
# output: <POLYGON ((15.5 0, 15.5 3.5, 19.287 3.5, 20 0, 15.5 0))>

Operating system
Mac OS X 13.4.1
Shapely version and provenance
2.0.1, pip

Hi @JerryLingjieMei , thanks for your question. The implementation of simplify is however not in shapely, but it GEOS. Can you raise your issue there? https://github.com/libgeos/geos

I did not explicitly install pygeos but internally shapely is trying to call pygeos 3.8.0. Probably sometime between 3.8 and 3.12 the issue is fixed.

In that case the issue is solved by upgrading GEOS. Thanks for the report though!


Allow bundling of remote modules

I'm using this plugin with https://github.com/thgh/rollup-plugin-url-import which enables me to bundle remote modules as well as local ones. I've hacked it to external: false, but it would be good if this could be made configurable.

If I understand you correctly you are using this module to first map from a bare import statement to an absolute URL, then your next plugin will fetch this from the URL. The problem here is then that the modules altered by the Import Map is flagged as external: true and this causes the second plugin (the one loading the module over http) is not receiving these modules.
If we add a external: true argument, as I understand you are suggesting, this will affect all mappings. Is there cases where one would like to not mass all mapped modules on to the second plugin? In other words; is there cases where some modules should be flagged as external and others not flagged as external?

In the particular case I was looking at, I want all specifiers to be bundled, but that would be controlled by the rollup config file, right? Is there any need for this to be set by your module at all?

@trygve-lie I think your understanding is correct. Using this plugin effectively makes rollup-plugin-url-resolve useless.
Honestly, I hardly understand external here since I exclusively use native ES modules, but I do know that it is a rollup config option... Perhaps returning something derived from that config option instead of a fixed value (defaulting to false) would resolve this?


Repetier Server kills Printer

When a print job is sent to the printer and in the warm up phase the Repetier Server loses power supply (by e.g. a short circuit) it is not possible to sent any print jobs again to the printer. Only manual control is working but jobs are not being executed. The printer is useless. The only method is, removing the printer and add a new printer (same printer in real) with different name.

You can print, but the server has 2 modes. If there are no prints started/queued selecting a model starts the print directly.
If you crash server then there is a print in waiting to be printed queue. From that point on you can only start prints from waiting queue. Selecting a model to be printed just adds it to the waiting queue. That is what you have seen.
In host connector there are both queues visible also there is a bug in waiting queue that you can not start it. That will be fixed in next release. As a intermediate solution just delete prints in waiting queue.

Yes I understood that, but the problem is, after the reboot (after the server crashed), the queue was no longer visible. It was not possible to delete any jobs...


Duplicated params?

Hi!
Could you please explain the difference between envelopeFrom/envelopeTo and from/to?
Thank you!

Btw, in case of Russian language I got:
"headers"<EMAIL_ADDRESS>"from":[{"address":"some.email@gmail.com","name":"Александр"}]

but
"envelopeFrom":[{"address":"some.email@gmail.com","name":""}]

Why?

Actually, these are not duplicated params, they come from the specification of the SMTP protocol itself. Here comes an explanation, shamelessly pasted from utcc.utoronto.ca/usg/technotes/smtp-intro.html:

Just like physical letters, SMTP email has two different sets of address information: the envelope headers, like the addresses on the outside of an envelope, which are used by mail transport software to route and deliver the email, and the normal headers, which are part of the mail message and which are only read and interpreted by the user and his software, just like the address attached to a salutation at the start of a physical letter. Unlike the post office, SMTP usually throws away most of the envelope before it hands the message to the user, so many users are not aware of the envelope headers.

In fact, SMTP never looks at the message headers at all; as far as SMTP is concerned, the email message (headers and all) is just one big blob that it shuttles around. Many SMTP clients are perfectly happy to deliver email with badly broken or entirely nonexistent message headers.

And some handy links:
www.pobox.com/helpspot/index.php?pg=kb.page&id=260
stackoverflow.com/questions/4367358/whats-the-difference-between-sender-from-and-return-path
Hope this helps!

Okay, thank you for clarifying, but could you aslo anser to my 2nd post?
https://github.com/Flolagale/mailin/blob/master/lib/mailin.js#L296
Why Cyrillic envelopeFrom.name not properly parsed from from.name?
Thanks!

This one looks like a bug from the (addressparser)[https://github.com/andris9/addressparser] package because of the missing space between the name and the '<' char.

What would be the solution?


Re-deploy atk

https://github.com/RandomNinjaAtk/docker-ama
https://github.com/RandomNinjaAtk/docker-amvd

https://github.com/RandomNinjaAtk/docker-ama
https://github.com/RandomNinjaAtk/docker-amvd

https://github.com/RandomNinjaAtk/docker-lidarr-extended

https://artifacthub.io/packages/helm/truecharts/automatic-music-downloader
https://artifacthub.io/packages/helm/truecharts/amvd


⚠ Bofrost.at has degraded performance

In 77125d2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2527 ms

Resolved: Bofrost.at performance has improved in 1bf66aa after 13 minutes.


Fixes the array index unset issue

This addresses #17. I used slice & concat concat since this proved to be the most performant on  platforms I could test it - see #18
Sorry about the extra changes with whitespaces it was the VSCode formatter...

Fantastic. 😀


IE not working for me. 'Symbol' is undefined

My website stopped working in IE after adding vue-router. I decided to find a working example and was surprised to find the same error here.
All I did is

git clone https://github.com/gothinkster/vue-realworld-example-app.git
cd vue-realworld-example-app
yarn install
yarn serve
opened http://localhost:8080 in Internet Explorer

[Vue warn]: Error in render: "ReferenceError: 'Symbol' is undefined"
found in
---> at src/components/ArticleList.vue
...
This example is supposed to work in IE right?
Is there a new version of something in package.json that broke this?

Hey. This is an issue but can be fixed easily.
The problem here is that we develop with a recent version of JavaScript which is not supported in Internet Explorer. To get this new JavaScript working in old browsers it is compiled with Babel. You can try out their REPL here: https://babeljs.io/repl and type something like const a = 123. But Babel is just compiling code blocks and not simulating new methods for arrays and such for example. If you want to get a bit more in-depth check out this article: https://hackernoon.com/polyfills-everything-you-ever-wanted-to-know-or-maybe-a-bit-less-7c8de164e423
So with babel there is a plugin callend babel-preset-env which will check your browserlists file which can find here in this repository: https://github.com/gothinkster/vue-realworld-example-app/blob/master/.browserslistrc which is including compilation target Internet Explorer 10 and above. But like i said some things are not supported when it comes to new functionality. For this we would need to include polyfills. This can be done manually but then everyone would need to load them and this would bloat the application quite a bit. A better approach is to use a service like https://polyfill.io/v2/docs/ to automatically load polyfills depending on your browser.
I will try to create a Pull Request regarding this problem in this repository to show case how it is done.

As you guessed I'm new to these types of problems, so thank you for the helpful response.
If I'm understanding you right, vue-router must be using a feature that babel isn't handling?
It sounds like we need to add a symbol polyfilll?

I guessed that you are new so gave some more thoughtful answer :)

If I'm understanding you right, vue-router must be using a feature that babel isn't handling?

You are understanding it right. Every time you get errors like this, go to MDN and check the documentation about the type which is not supported. In this case, you can find it here:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol
As you can see in the Browser compatibility table no Internet Explorer support is given at all.
To solve this you can use a polyfill like https://babeljs.io/docs/en/babel-polyfill or https://github.com/medikoo/es6-symbol . I do not recommend this because then you would load the polyfill even if the browser is supporting this.
Like I said I would use Polyfill.io.
https://cdn.polyfill.io/v2/polyfill.min.js?features=default,Symbol is the URL which you can query. It will check the user-agent of the request and determine your browser as written as in the docs: https://polyfill.io/v2/docs/
The default user agent for Internet Explorer is Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv:11.0) like Gecko. You can mock the behavior of polyfill.io with the following URL: https://cdn.polyfill.io/v2/polyfill.min.js?features=default,Symbol&ua=Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv:11.0) like Gecko (do not use this in production. leave the ua off).
You can find examples like this also on the polyfill.io site: https://polyfill.io/v2/docs/examples

Hey @JonDReese ,
I have made a PR here: #105
Would be nice if you could check this out and see if it works on your machine.
Thanks, Kevin

Thanks so much! I will try it out. My personal Symbol polyfill is a little more complex than this one, so I've been trying to get it to work for myself first (selfishly)

Thanks! Trying it out now.

Works! You rock :)
Personally I'm still having an issue on my site, because my IE error is slightly different: ""Unable to get property '__symbol:toStringTag0.03521717070493940411' of undefined or null reference""
Something else must be already attempting to polyfill Symbol on my project. Regardless, I've got a much better idea of how to fix it now.

If you are using a custom polyfill then there might be a weird setup sometimes. Definitely recommend using the service above i mentioned.


Prepare August patch release for FR and MA

You should release the patch version from a release branch.

You should release the patch version from a release branch.

No ongoing beta development currently.


How to refresh tokens?

I'm currently trying to implement the refresh token functionality, but I always get the error:
Credentials are not provided

The request is made using axios with withCredentials: true enabled in the options.
Here's the code for the server:
@router.post(
    "/refresh",
)
async def refresh_token(
    response: Response,
    credentials: JwtAuthorizationCredentials = Security(refresh_security),
    db: Session = Depends(get_db),
):
    logger.info("Request: Refresh -> New Request to refresh JWT token.")

    user = get_user_by_id(db, credentials["id"])

    logger.info("Request: Refresh -> Returning new credentials.")

    set_authentication_cookies(response, user)

    return {
        "user": user,
        "detail": "Token refreshed successfully!"
    }

It appears to be because it doesn't read the refresh_cookie (if you have set it up). Try submitting the refresh_token string directly by opening the refresh route in Swagger UI and clicking on the lock icon.

@Sebsebzen Thanks for your answer. This does seem to do the trick, however I need to send the token via Axios. The refresh token is set up in a httpOnly cookie, so we can't read it. Is this an underlying problem with fastapi-jwt or am I doing something wrong?

I'm new to this library too, but it could be an underlying problem @k4black ?
After all, there is a staticmethod to set the refresh cookie, so logically there should be a way to refresh with it.

@Myzel394 I found the solution. You need to setup refresh_security like this:
refresh_security = JwtRefreshBearerCookie(
    secret_key=SECRET_KEY,
    auto_error=True  # automatically raise HTTPException: HTTP_401_UNAUTHORIZED
)

use JwtRefreshBearerCookie to read access token from both bearer and cookie

I had the same problem, no worries :)


feat: add a missing news

Sorry for the missing and thanks!

Just a small suggestion: perhaps we should add an SOP checklist when a new committer comes on board? I noticed that I am also missing from this doc; not sure if I am the only one.

Just a small suggestion: perhaps we should add an SOP checklist when a new committer comes on board? I noticed that I am also missing from this doc; not sure if I am the only one.

Sorry for that. This list is copied from our old status wihtout update. Would you like to help fix that?
Also we have an onboarding guide for committer: https://opendal.apache.org/community/committers/onboarding, maybe we can also add this task into it.

Sorry for that. This list is copied from our old status without update. Would you like to help fix that?
Also we have an onboarding guide for committer: https://opendal.apache.org/community/committers/onboarding, maybe we can also add this task into it.

Certainly! I'll open a PR to address this.


Please add this to Kivy Garden

https://github.com/gottadiveintopython/drag_n_drop2

I'm a bit uncomfortable that it basically has the same name as the drag_n_drop flower. Could you use another name? I would rather that people don't confuse it with drag_n_drop. Especially since it's drag_n_drop2, which may give the impression that this is a latter version of it.

I'm a bit uncomfortable that it basically has the same name as the drag_n_drop flower. Could you use another name? I would rather that people don't confuse it with drag_n_drop. Especially since it's drag_n_drop2, which may give the impression that this is a latter version of it.

got it. I'll fix it soon.

got it. I'll fix it soon.

@matham I fixed. Is it all fine?

@matham I fixed. Is it all fine?

Yeah, if you want to transfer it to me I'll transfer it to garden.

Yeah, if you want to transfer it to me I'll transfer it to garden.

Thanks, I asked to tranfer the repository :)

Thanks, I asked to tranfer the repository :)

Ok, done: https://github.com/kivy-garden/draggable. And you should have write access to it. Lemme know if you don't.

Ok, done: https://github.com/kivy-garden/draggable. And you should have write access to it. Lemme know if you don't.


Move Storyshot Snapshots to individual files

Update DOM snapshots to use single files. Our current file is 63000+ lines
import initStoryshots, {
	imageSnapshot,
	multiSnapshotWithOptions,
} from '@storybook/addon-storyshots';

initStoryshots({
	configPath: '.storybook-based-tests',
	storyNameRegex: new RegExp(`^((?!.*?(${skipStoryshotTest})).)*$`, 'g'),
	suite: 'DOM snapshots',
	integrityOptions: { cwd: __dirname }, // start searching from the current directory
	test: multiSnapshotWithOptions({}),
});

@interactivellama please assign the issue to me.

I can't assign it to you unless you are in the Salesforce org. You can take over my pull request and I can close mine if you'd like.

@zamhaq I haven't heard from you in a while. I'm going to take this one back. I think it will help with pull request conflicts


Unit test for QR with regularization

Unit test for QR with regularization should compare TSQR solve to local QR. Previous version compares TSQR solve to normal equations.

Thanks @rolloff - I'll cherry-pick the right commit and merge this.


Vim/neovim + NERDTree The first few mouse double clicks will select the text instead of expanding the directory

Recorded video demo:

Note: The first two mouse double click actions.
This problem has existed on my side since many versions. It only appears after the first few mouse double-clicks of vim/neovim.
Other terminals (such as Konsole) do not have this problem.
Alacritty Version: 0.3.3
OS: openSUSE Tumbleweed (x11)

When you say vim/neovim, do you mean you've actually tested both and both show this problem? They're quite different when it comes to mouse handling.

FYI, I can't repro it with neovim + set mouse=a + alacritty's terminfo. Anyway alacritty selection shouldn't work in mouse mode apps at all, unless you've pressed shift.

alacritty's terminfo

That's actually a very good point. Please make sure you're using the correct terminfo.
This seems like a bit of a strange issue to me, since we don't do selection in vim. This selection is started by vim itself.

Thanks Reply. I currently use neovim, but when I used vim before, I also had this situation.
Because my vim provided by openSUSE has some problems with the plugin, I will try to reproduce it in a brand new virtual machine system in a few hours.
I don't rule out my configuration or environmental issues.

I found the reason, it is my mouse problem, it will often generate a double click when clicked. This behavior can occur if you click the left button many times quickly.
It doesn't appear on Konsole because I rarely open neovim on Konsole.
Sorry to bother you.


Remove CreateInstanceIntrinsic workaround

\src\System.Private.CoreLib\src\System\Activator.cs has a workaround to add a method implementation which throws a NotSupportedException until support the intrinsic is added to the compiler and the method body is no longer needed.

Maybe a dupe of #368?

I agree.


when secret bridge agent is configured with bridge-url url having "/" at the end , it fails to contact  secrets-bridge server.

Rancher Version:v1.1.4-rc1
Set up secrets-bridge-server and secret-bridge-agent by following instruction in https://github.com/rancher/secrets-bridge/blob/master/docs/setup.md for k8s environment.
When starting secret bridge agent provide a bridge-url url having "/" at the end .
It fails to contact  secrets-bridge server.

Fix is in docker image rancher/secrets-bridge:v0.1.2 which is part of the community catalog now.

Tested with rancher/secrets-bridge:v0.1.2
This issue is not seen anymore.


More flexibility with custom typeface

Hello,
I would like to use my own .OTF fonts assets, but as for now it is not possible because of hard-coded file information :
                Typeface t = Typeface.createFromAsset(
                        c.getAssets(), String.format("fonts/%s.ttf", name));

Is it possible to permit to pass our own asset filename, for more flexibility ?
Regards,
Anthony Skrzypczyk

That's what typeface(Typeface, Typeface) is for

I have the same problem. I need to use a custom .OTF fonts but is not possible =/


Case(1): Add a changed line

Adds a changed line

Successfully created backport PR #108 for case1-backport-target.


Warnings when using with nuxt.js

WARNING in<EMAIL_ADDRESS>28:71-112
Critical dependency: the request of a dependency is an expression
<EMAIL_ADDRESS>@ ./store/distribution.js
@ ./.nuxt/store.js
@ ./.nuxt/index.js
@ ./.nuxt/client.js
@ multi ./.nuxt/client.js
WARNING in<EMAIL_ADDRESS>34:11-32
Critical dependency: the request of a dependency is an expression
<EMAIL_ADDRESS>@ ./store/distribution.js
@ ./.nuxt/store.js
@ ./.nuxt/index.js
@ ./.nuxt/client.js
@ multi ./.nuxt/client.js

Yes, and the browser stuck when you use crypto.generateKeyStore(privateKey, "1234567")

Hi. Does this cause an actual problem or only produce warnings for now?

Just warnings

Just warning


luci-app-dockerman: Update to play nice with recent changes

https://github.com/openwrt/luci/commit/180d39dcd2427e3c32c0ec7ecc3c7bfb48c0d0ab broke dockerman's appearance in the menus
Make a small change to dockerman's index entry to make it play nice with the new architecture, firstchild() was obtained using DAWN's controller/dawn.lua as an example
signed-off

Commit message updated/reworded to address the failures of the previous formalities check, and force-pushed.


[Improvement][IntegrationStudio] Allow add Environment Variables to the Embedded Microintegrator

Description:
In Integration Studio with the embedded microintegrator it does not allow us to add environment variables to the Launch Configuration. This would be very useful as with Docker Environments we heavily use environment variables and there is no easy way to achieve this with the embedded mi.
Suggested Labels:
Improvement
Suggested Assignees:

Affected Product Version:
Integration Studio 7.0.2
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Just got this link: https://medium.com/@rosensilva/how-to-inject-environment-variables-to-wso2-integration-studio-runtime-83b8f0cb882e
So, we can close the issue.


Bump design

I find it easier to store icons in the project for this moment. Also, our sidebar navigation uses icons from the project because icons in the design had grey fill what made them not accept current font colour. I found difficult to do the release cycle because of this change.
To accept a6c3393 we have to fix such behaviour. However, I would keep the script an icons.

Isn't the time to moving some components and some logic to @oacore/design?

Yes, it is but the move should not break anything

What do you propose then?
Should I remove grey fill of all icons in design and add puzzle icon there or forget about it?

If you want to use icons from the design, please update icons in the design with project icons, add my puzzle there too and merge first 2 commits.
However, please do not merge the last one because we may need it in the future and there is not need to look for it in the history.


Training breaks down after 100000 iterations

No bugs found, and the solver prototxt is OK, any ideas？

Hmmm, could you provide more details on your problem?
Is there anything written in the console? How many images do you have in your dataset and how many epoch did you ask the code to run? For example, with a dataset of 1000 images, a batch size of 1 and 100 epochs it's just normal that the code stops after 100000 iterations.
Do you have the A_to_B.png and B_to_A.png images? If yes it means the training has just ended normally.


add support for updating rancher labels in kubernetes

@alena1108

https://github.com/rancher/rancher/issues/5269


hyper-haskell: init at <IP_ADDRESS>

Motivation for this change
Hyper Haskell is a fun little program which is a little tricky to set up in Nix. This package makes it really easy to install, and provides a hook for overriding the package set available in the environment.
Cheers!
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[X] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

It's ready to go now. I have taken [WIP] off the title now that the following two things are done.

Merge HeinrichApfelmus/hyper-haskell#22.
Regeneration of hackage-packages.nix after NixOS/cabal2nix#276.

:pineapple: @copumpkin, would you be able to look at this? Cheers

Sorry for missing this, and thanks @matthewbauer for handling it 😄


Fixes for Realtek RTL8720CF

Hi, I successfully liberated a TP-Link Tapo P100 Mini smart plug and I want to share the modifications I had to do to make it work with LibreTiny and ESPHome.
First I had issues with the initial flashing, I used the UF2 image, but the device couldn't boot after flashing. With ltchiptool uf2 dump I found out that the partition table dump didn't start at zero and traced it back to collect_data, which skipped the block starting at zero.
But it still didn't boot, so I tried passing only one image to uf2ota (so using the SINGLE scheme instead of DUAL) and was confused that the flasher didn't write anything. I found out that the flasher skips parts with SINGLE scheme and fixed it, that also fixed the default config of libretiny, which uses DUAL for OTA1, but SINGLE for partition table and bootloader, so both of those were skipped and the chip didn't boot.
Thank you for all your hard work on this project!

Hi,
The SINGLE scheme is used for devices which have a separate "download" partition for OTA - for now it's only BK7231. Realtek chips, as well as ESP chips for example, use a DUAL scheme, which means that two application images are available at any point.
I'm not sure why the bootloader image wasn't flashed before - maybe this was an error on my side, and I never noticed it because I didn't have boot up problems.
To make ltchiptool flash the bootloader/partition table image, you could try passing two of the same image files while generating the image. Kind of like the app image itself, but with the same partition names.
I wonder why did you encounter issues with booting. It's possible that TP-LINK used their own firmware keys (or, more likely, different partition offsets).

I see you're also working on implementing OTA on this chip. My main problem was having to generate the app image hash on-device. The issue here is that the app header has a counter value. In order to flash an OTA update, the 2nd partition needs to have the counter value higher than the 1st partition. But this same value is also checksummed using the app hash key.
When LibreTiny generates an app image, it would need to set this value to a number higher than what's already on the device. But it can't possibly know the number - even if we used the build timestamp, it wouldn't allow for downgrading.
I had two solutions in mind:

When flashing OTA updates, clear the header of the other app partition. That works, but doesn't allow for rollback. Normally this isn't a problem, but the current API is made this way. I would even remove this feature.
Keeping the counter and hash values as 0xFF. The device could then flash the app and calculate the two values, then write it to flash without even erasing (I think that's possible). It's way harder and probably pointless, anyway.

Another problem (and the reason why OTA was never implemented on AmebaZ2) is partition tables. BK7231 has a fixed app offset and mostly fixed download offset - so it's not an issue.
It is, however, an issue on Realtek chips. AmebaZ has a fixed OTA1 offset, but OTA2 offset is stored on the flash. AmebaZ2 has both offsets changeable.
Manufacturers often change the offsets. They can also vary between chip types and are also different for devboards. You won't believe how many times I found myself flashing an OTA update without getting the desired results, just to find out that it was written to an offset that wasn't even used by the bootloader.
An obvious solution would be to flash the partition table along with the app (in UF2 images). It is implemented this way on AmebaZ2. There is normally no problem with that, but what if someone wants to change the partition table in an OTA update? (as in, not via ltchiptool, but OTA). Two things can happen:

the new offset can be larger than the current app's end address, this should be fine
the new offset can be smaller and will overlap the currently running app. This is a problem. LibreTiny (uf2ota) has measures to avoid that (it marks some regions as "protected") but it makes such an update impossible.

Another problem is flash wear out. There is no point in flashing the partition table and the bootloader every single time an OTA update is applied. Some people like to keep their devices up to date, which might mean flashing new versions even several times a month. Yeah, sure, flash chips can (theoretically) withstand like 100,000 erase cycles, but we have seen some cheaper devices fail prematurely because of this issue.
I tried to fail some middle ground here, but I got caught up in some other things and never got the opportunity to get back to this. I'm open for any ideas.

Fixing OTA issues is planned for the LibreTiny v2.0 refactor. That, as well as many more things. See issue libretiny#(insert issue number here). I have described most issues I would like to address there. I wanted to make partition offsets (and keys) configurable separately from the board type - currently, offsets change whether you select bw15, generic rtl8720cf, or wbr3.
However, I can't estimate when will I be able to work on this update.

I was thinking about it some more and had another idea. We can pre-corrupt the OTA image during build (only for the device scheme), flash the corrupted image and then repair it in the lt_ota_switch function. This would require minimal changes to the code and would be safe against interruptions during the OTA upgrade. I'll probably implement this in my fork.

Hi
1.

Maybe something like this would be better then:
Yes, that's what I meant. I think this was just a mistake that I forgot to set the dual schema to bootloader and partition table.

Erasing the current image could indeed cause problems if the XIP code would be erased by the operation too. You're right the empty header shouldn't be included for device scheme.
The ability of changing partition tables can be used if the currently flashed image is too small (e.g. you're adding more components over-the-air). But you're probably right it is a niche usecase - UART flashing is so far necessary anyway, so if the flashing tool updates the partition table, it will suffice.

About "universal" firmwares - yes, it would be good to support such a feature. This would be used, for example, by ESPHome-Kickstart (which is a GPIO scanning tool that allows to "adopt" a device in HA). But I still don't know how to support the partition table switching in OTA updates, so it's better to leave that feature for now.
There is one way I can think of: UF2 has a built-in partition table. It used to only rely on the device's own table, which wrote firmware to the previously used offsets. That worked on BK7231 (always same offsets), it would have worked on AmebaZ2 (OTA1/2 code is the same), but didn't work on AmebaZ (firmware is position-dependent, can't be simply reflashed to a different location). Perhaps this idea should be introduced again? Or perhaps another time, in the future... That solution still failed if the existing partition was too small to fit the new app.

About pre-corrupting the image: I meant something similar with setting the keys to 0xFF - that would make the bootloader ignore this application, unless it's manually fixed in the OTA activation code.
Your method with a simple XOR is much easier. However, it still requires to erase/write the first flash block twice.

Since UF2 is written sequentially, how about leaving the 1st block until the end of the process? That would fix the case where OTA is interrupted. However, it would mean that "activation" becomes pretty pointless because the UF2 writing itself makes the new image "valid". So flashing an UF2 without activation (and rebooting) would boot either of the two apps, depending on which one has a higher number.

Maybe a proper solution would be to actually bring back the "other app" header erasing? Of course, we would need to make sure that it can be erased safely. The last step of UF2 writing would then 1) write the new app's header, 2) erase the old app's header.

This would properly support the bootloader's app booting choice, but wouldn't support the "activation" mechanism. Maybe it should just be dropped? After all, what's the point of having to activate the app separately anyway?
Currently, BK7231's activation is a no-op, unless you want to "revert" the OTA update (that's pointless too, as it only allows to cancel the pending firmware switch before rebooting).
On AmebaZ it is actually needed to flip a bit in the system partition - maybe that should be part of the UF2 process (the last step, called by uf2ota in some kind of callback)? E.g. without the requirement to call that method separately.
Then, "activation" would be optional (per-family). It would only be implemented on AmebaZ.
AmebaZ2 would simply write the app headers (write new, erase old) as the last part of the UF2.

Hi, to move this forward a little bit, I've separated the first commit to https://github.com/libretiny-eu/ltchiptool/pull/48. That one is clearly a bug with an obvious fix, whereas this OTA stuff needs more discussion.
You've proposed a few times in this thread to remove the rollback functionality:

When flashing OTA updates, clear the header of the other app partition. That works, but doesn't allow for rollback. Normally this isn't a problem, but the current API is made this way. I would even remove this feature.

Currently, BK7231's activation is a no-op, unless you want to "revert" the OTA update (that's pointless too, as it only allows to cancel the pending firmware switch before rebooting).

I agree with you, because it complicates things and the usefulness is limited. It would help only if the firmware could detect that it is bootlooping and switch to the other image, but this would require firmware developers to implement this and the firmware would have to be working enough to reach this check in the first place. It cam also be mostly replaced by a safe mode built into the firmware, like the one in ESPHome.
Then the next decision needs to be made whether we want to put the cleverness into the UF2 file, or into the OTA functions inside the firmware. From your comments I see that you lean more into the UF2 direction and I don't disagree. My current solution is suboptimal, because it doubles the size of the UF2 file and also erases the first image block twice, but it was easy for me to implement.
I don't know Python much and moving the logic into UF2 would require some larger changes to uf2tool and if I implemented that, it would probably look out of place in your clean and well-thought-out code (at least to my eyes 🙃).

After merging https://github.com/libretiny-eu/libretiny/pull/307 it should be possible to flash RTL8720CF using the UF2 file produced by libretiny.


Inconsistency for reliance on transitivity of import

Issue https://github.com/semanticarts/gist/issues/80 added explicit imports to gistCore so as not to rely on transitivity. However, all the other ontologies still DO rely on transitivity of imports. Is there any justification for this inconsistency?
I propose that we either:

have all ontologies have all explicit imports, just like gistCore does
have a clear rational for why it makes sensed to do so ONLY for gistCore.

Discuss in the context of #292.

Closed as part of #292, demodularize gist.


Custom Elements

add support for custom elements

they can be configured like this:
custom_text=TEST
exec=echo "Test"
custom_text=TEST2
exec=echo "Test2"

custom elements also need to be available on the change order page

Requires #16 to be done first


⚠ Samsung has degraded performance

In 36c5673, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2812 ms

Resolved: Samsung performance has improved in 6c5a4e7.


tcp: add support for MPTCP option

Hello,
First, thank you for developing and maintaining this useful lib!
Currently, packets with MPTCP options are not recognised:
Unknown(30)

MPTCP packets are using the option 30 according to the IANA.
For more details about MPTCP:

RFC 8684
Website: https://www.mptcp.dev

Just after having created this PR, I found this other PR on the Google repo, doing a more complete work: https://github.com/google/gopacket/pull/870
Do you think this PR could be accepted here?

yep happy to bring those PRs here. might as well close this one and create another one from that one.

Replaced by #66


Bug item head slot

ViaVersion dump and Spigot version
/viaversion dump output :
-> http://hastebin.com/lubekugoko.json
Version: git-Spigot-e4d4710-e1ebe52 (MC: 1.8.8) (1.8.8-R0.1-SNAPSHOT)
-> No error in the console or else
Conflit with Magic
I'm using a Magic item. (Plugin)
An error using an item
With the Magic plugin, we can vanish ourselves by rightclicking with an item which is going directly to the head slot armor.
But in 1.9 :
=> Video to explain: https://streamable.com/clg0

Are you sure this is not part of the fact 1.9 now renders items in the head slot properly instead of what 1.8 would do?

No in 1.9, this is working fine.

@Blamo27 Could you also create a video in 1.8 that shows how you expect it to be?

Of course : https://streamable.com/10fh

This is something that renders differently for the client. We won't fix this issue.

@Matsv Is it possible to create a plugin that is replacing the item in the head slot with "MATERIAL.AIR" for 1.9 clients to prevent this bug ?


first result missing from csv file

Thanks so much for coming here to raise an issue. Please take a moment to 'check' the below boxes:

[x] I'm up-to-date with the latest release:
pip install -U talos

[x] I've confirmed that my Keras model works outside of Talos.

If you still have an error, please submit complete trace and a code with:

output of shape for x and y e.g. (212,12)
Talos params dictionary
The Keras model wired for Talos
Description of extra variables in the model

You can provide the code in pastebin / gist or any other format you like.

After fixing #30, I noticed that the first result is not saved to the .csv file.
The code here gives the following output:
Using TensorFlow backend.
2 scans will take roughly 0 seconds
Scan Finished!
csv output has only 2 lines instead of 3
round_epochs,val_loss,val_acc,val_fmeasure,loss,acc,fmeasure,first_neuron,hidden_layers,batch_size,epochs,dropout,kernel_initializer,optimizer,losses,activation,last_activation
 2,0.19118814039648624,0.906432733201144,0.5248427495621798,0.2075809771241854,0.8542713519915863,0.4982654840203386,10,0,30,2,0,uniform,<class 'keras.optimizers.Nadam'>,<function mean_squared_error at 0x10b3162f0>,<function relu at 0x10bc2af28>,<function sigmoid at 0x10bc2d0d0>

I believe the culprit is the logic in results.py:run_round_results, which only returns the header if round_counter==0. I think it should return both the header and first result, or the logic in scan.py has to be changed.

Thanks, this makes sense. It is a remnant from the past, and it should be fixed as it may effect use-cases where you do a small number of runs that take a long time.

Hi @mikkokotila:
To be clear, I think this will affect all use cases. The reporting will ignore the first experiment run, which could possibly be the best. It seems high priority, imho.
Otherwise, thanks for a great library!

@aronwc I'm glad you enjoy it :)
Sure I understand. What I mean is that generally the workflow involves scanning through hundreds or thousands of options, and at the end of the run you might have 10-20 that are very close to each other. But ok, I get the point that unless we have the result, we can't know (it could be notably better than others)..so I will prioritize this. Most likely tomorrow Friday.

gotcha, thanks!

This is now resolved in @dev


Upgrade Openjdk to jdk8u252-b09_openj9-0.20.0

Upgrade openjdk to address PSIRT issues for java/scala based components

PG1:724 is 🏃♂


chore(main): release faro-shop 0.34.0

:robot: I have created a release beep boop
0.34.0 (2024-08-01)
Features

Bump app to 0.37.1 (#642) (7525b1c)
Bump app to 0.37.2 (#647) (7f28281)
Bump app to 0.37.3 (#660) (468cfaf)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

faro-shop-0.34.0
:sunflower:


style(all): run rustfmt 0.5

There were the following issues with your Pull Request

Commit: d1bef702d6bdf6d8406ecc426ea14566b432a633
Your commit message does not contain a body

Guidelines are available at https://github.com/lettre/lettre/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

Coverage decreased (-0.2%) to 84.177% when pulling d1bef702d6bdf6d8406ecc426ea14566b432a633 on amousset:rustfmt-2 into d20d4f038b5201fe1c3581e8e1c54ca76fd3e075 on lettre:master.


Usage of contentFiles section

This should have a full example on the usage of the  section. With the snippet given, it lacks the relevant information that the  section must be placed under the  section, not besides the  section (at the root level).

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: 06a19d7d-253d-f17f-6421-624c9867473d
Version Independent ID: cc37eb17-f715-080c-7bfc-9eae868d50ba
Content: NUSPEC-Dateireferenz für NuGet
Content Source: docs/reference/nuspec.md
Product: nuget
GitHub Login: @karann-msft
Microsoft Alias: karann

Issue moved to NuGet/docs.microsoft.com-nuget #1351 via ZenHub

Hello, @pgrawehr
Your contribution is much appreciated. Your feedback is related to the original documentation.
Hence, we are migrating this issue to the English repo. Please review the status of the issue here - https://github.com/NuGet/docs.microsoft.com-nuget/issues/1351
We truly appreciate your contribution to our articles.
Kind regards,
Microsoft DOCS International Team


Expected interest earnings for Month/Week/Day calculated incorrectly.

It looks like the Monthly/weekly/daily earnings are simply calculated by taking the expected interest in APY for the year and dividing by 12/52/365. This is incorrect as the interest rate displayed is APY, meaning it compounds/accelerates over time
meaning just dividing is going to make the interest appear linear, which is not how it works in reality.
For example, if my balance is $1000, and the APY is 19.49%, the APR is 17.78%, which means the daily earnings should be $0.487 ((1000*.1778)/365).
Instead, the earn page will show $0.534 ((1000*.1949)/365), making it off by a significant margin.

Hey!
Thanks for reaching out. We are planning to have an upgrade on the actual contract level interest compounding mechanism changes in our next major upgrade (https://github.com/Anchor-Protocol/money-market-contracts/tree/dev/v1.1) , and will modify the webapp to calculate expected interest earned accordingly.


fix(tpc): directly import schema from valibot

🔗 Linked issue
fix #133

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
@harlan-zw is there a reason to have #nuxt-scripts-utils if it only exports everything from valibot ?

We use the alias to make sure we stub out the valibot exports outside of dev. For some reason, I couldn't get them to tree shake out otherwise.
It shouldn't cause an issue though? All of the other registry scripts are using it without issue :thinking:


How control plane/worker nodes identified by the cluster

Hello,
Lets say I have 4 control plane in a subnet, and I want three of them to connect to one cluster and one to another cluster.
Similarly with 4 worker nodes in same subnet, I want three to connect to one cluster and one to other cluster.
I know it will be a bad design but I just want to understand how cluster consider a node its control plane/worker node, Is it governed by the certificates? Please provide some details if possible!

If I am not wrong it is identified by the .kubeconfig created for kubelets and kube-apiserver file “—server”option?


[iPadOS] Added 18.2 and 17.7.3

Both released today; See https://support.apple.com/en-us/121837

Unsure if this means iPadOS 16 is EOL / End of Security Support?


SteamPP-master/steam++.cpp:29:2: error: ‘CMsgClientLogon’ was not declared in this scope

Several of these errors appear when attempting to build in KDevelop. I've read elsewhere this perhaps may be due to some proto's being moved around. Attempting suggested fixes didn't help.
Thanks for any correspondence.

Hi, i don't know if you already found the solution. I did the following to get it working:
I added these .proto files to the PROTOBUF_GENERATE_CPP List in the CMakeLists.txt file
        /root/SteamKit/Resources/Protobufs/steamclient/steammessages_clientserver_login.proto
        /root/SteamKit/Resources/Protobufs/steamclient/steammessages_clientserver.proto
        /root/SteamKit/Resources/Protobufs/steamclient/steammessages_base.proto
        /root/SteamKit/Resources/Protobufs/steamclient/encrypted_app_ticket.proto
        /root/SteamKit/Resources/Protobufs/steamclient/steammessages_clientserver_friends.proto
        /root/SteamKit/Resources/Protobufs/steamclient/steammessages_clientserver_2.proto

I also edited each of these .proto files and added syntax = "proto2"; to the first line of the file to get rid of the warnings.
After that I added all the new header files to the cmclient.h file
#include "steam_language/steam_language_internal.h"
#include "steammessages_clientserver.pb.h"
#include "steammessages_clientserver_login.pb.h"
#include "steammessages_base.pb.h"
#include "encrypted_app_ticket.pb.h"
#include "steammessages_clientserver_friends.pb.h"
#include "steammessages_clientserver_2.pb.h"

Atm. I'm just want to building the example. I'll create a pull request when I know that everything is working


Problem with point_triangulator

First, thanks for your amazing work.
There is a warning as follows when performing the step-by-step guides to localize with Aachen.

Could you please help me to address this problem when you are free?
Thanks a lot for your help.

See my comment: https://github.com/cvg/Hierarchical-Localization/issues/42#issuecomment-770637726 In short, check the RAM consumption and how much your system has.

Closing this issue due to inactivity. Feel free to reopen it.


Installer does not accept spaces in usernames

Hello,
The path of install doesn't read the spaces in the username, can fix it?
Like  "User Name" > installer read to "User " and no more

The only thing you can do right now is do the advanced installation here
There's no (known) workaround to get it working in the installer.
Also best off joining the support server for further help.

As mentioned in #55, this may cause the client to crash as well.


Whether Mediapipe supports the overall detection of multiple people

MediaPipe Solution (you are using)
Holistic Markerer
Programming language
No response
Are you willing to contribute it
None
Describe the feature and the current behaviour/state
Only one person can be identified in this example
Will this change the current API? How?
No response
Who will benefit with this feature?
No response
Please specify the use cases for this feature
Holistic
Any Other info
Holistic whether to support multiple user identification

Hello @jhlibra
MediaPipe holsitic landmarker does not support detection of multiple persons in a scene as of now. We are marking this as a feature request and will share it with our team. However, we cannot provide a timeline or confirm if it will be supported, as it will depend on further demand and discussions.


Git 99 remove etc autoscaling

This + https://github.com/samsung-cnct/k2/issues/105 resolves https://github.com/samsung-cnct/k2/issues/99.
This PR removes all of the dynamic resizing of etcd nodes in favor of individually creating a static set of nodes.
/cc @maratoid @venezia

Agreed.

argh, I see the problem.  I used the wrong list for calculating the index into an array.  Testing a fix now.

retest this please

farging tiller deploy flakes

retest this please

tiller flake has hit both AWS and GKE on different runs.  right, gotta sort that out.

retest this please

Thanks @l337ch.  And its not the ASG that was causing the problem.  It was the lambda function and other associated pieces that was causing the issues.  We may reinstate the ASG later but for now we need stability.


Remove extension if already installed with forceDownload

Currently I cannot upgrade the extension to latest version with forceDownload, it still using old version on the Electron runtime. I think it should remove already installed extension first.

It looks indeed overwrite the latest version to <userData path>/extensions, but I already getting old version number with require('electron').remote.BrowserWindow.getDevToolsExtensions().

@jhen0409 We already have a test for this
https://github.com/GPMDP/electron-devtools-installer/blob/master/test/download_spec.js#L38
That asserts that the new extension is downloaded and completely overwrites the old version.  Are you saying that Electron somehow "caches" the Extension and we have to remove it first.
If that is the case can you please add a test to this PR to that affect.

Added the test case, just make a fixture to simulate version update.

I'll push test case commit first, so we can see the test fail.

@jhen0409 Looks good, thanks for the test case.
Just a small semantic change and I'll merge

Published in 2.0.1


Increase path range

I checked path again and can verify the context.extension method was already added in 1.6.2. It's therefore possible to increase the range.
I verified it working by adding tests and then explicitly use 1.6.2 as dependency.
fixes #77
fixes #78

Verified it works with Flutter (Channel flutter-1.17-candidate.3, v1.17.1, on Mac OS X 10.15.4 19E287, locale en-GB)


Update price-adjustments-discounts.md

Added two more types of discounts that were released many releases ago.

:x: Organization membership check failed
Members of the MicrosoftDocs organization should use the private repo. Please move your changes to https://github.com/MicrosoftDocs/Dynamics-365-Operations, and close this pull request.


Update static typing

This updates how we do static type checking, and fixes some issues on main.
The biggest change is moving the mypy linting check out of .pre-commit. As mentioned in https://github.com/zarr-developers/VirtualiZarr/issues/209, we need all the typed dependencies in the environment running the check. The one managed by .pre-commit was lacking several dependencies (like xarray and Zarr) and so we weren't benefiting from static type checking at those boundaries. We can move it back into pre-commit, but we need to make sure that all our dependencies are duplicated there.
I'll explain some of the type changes inline.

[x] Closes https://github.com/zarr-developers/VirtualiZarr/issues/209
[x] Tests passing
[x] Full type hint coverage

CI is passing now.


Singleton behavior not in documentation

The fact that Passport exports a singleton by default and has a constructor if you need multiple instances only seems to be documented in the response to issue #27.
It would be helpful if that information was in the official documentation. When I set it up on a project, I was passing the returned object around because I hadn't seen that it was a singleton (and resulted in some unexpected behavior until finding that was the case).

What was the unexpected behavior?  What difference would it make to pass an exported instance around, as opposed to an instance your application constructed?

Sorry, I meant that passport was working properly, but we had actually misconfigured our app and couldn't figure out how it was be working (we were adding our strategies to what we thought was a new passport instance in a separate file).
To be clear, the only issue I'm reporting is that the singleton behavior isn't in any of the documentation.

Noted.  I've got it on my backlog to update the documentation.  When that gets to the top of the list, I'll make sure this is clarified.  Thanks.

Also, this should be here: https://github.com/passport/www.passportjs.org ?

@Kinnardian I wasn't sure if it was "encouraged" enough to put it on the standalone site versus in the README.md of this repo.

I just wanted to add that I had to look at the source code to figure out how to create multiple instances of Passport for testing purposes.  Wasn't too big of a deal, but +1 for a note in the docs.  Keep up the great work!

So how is it possible to create multiple instances of passport? Can we just do new Passport?

@pronebird
var passport = require('passport'); // default instance of passport

// to make a new one just do
var secondInstancePassport = new passport.Passport();


Implement agent reuse, toggled by a cluster profile config option

Description
This implements agent reuse following the approach outlined in these comments: https://github.com/gocd/kubernetes-elastic-agents/issues/53#issuecomment-1399398498 https://github.com/gocd/kubernetes-elastic-agents/issues/53#issuecomment-1406967391. Resolves https://github.com/gocd/kubernetes-elastic-agents/issues/53
Cluster profile has an option to enable agent reuse, defaulting to false:

The naming, and presentation of this option, are open to feedback! 🙂
Changes
When pods are created, they are annotated with a hash of the elastic config. This ensures that when elastic config is changed, agents created from the old config will not be reused, and will eventually expire after the timeout.
When agent reuse is enabled, the main behavior changes are:

Job completion request -> instead of terminating the agent, mark the agent as idle so it may be considered for reuse
Should assign work request -> assign work only if the agent is available for work and the elastic config hash matches the agent
Create agent request -> only create an agent if none are available for reuse

Other supporting changes:

KubernetesInstance is an immutable data class constructed by a builder, and no longer contains a Kubernetes client.
Improving field names (e.g. properties) for clarity between cluster profile properties and elastic profile properties.
Refreshing instances moved inside the ServerPingRequestExecutor instead of "inline" in the KubernetesPlugin request handling block.
Added a request handler for REQUEST_PLUGIN_SETTINGS that returns an empty map - just to silence some warnings about this request not being implemented.
Some classes are refactored to allow testing with less mocking.
Removed an unnecessary semaphore.

This ended up being a pretty large set of changes. Happy to explain in more detail if needed!
Testing
Many unit tests updated and added, and run with ./gradlew test. I've also tested this running GoCD on my machine with a Kubernetes cluster in kind.

Thanks for this. Appreciate all the work here. Unfortunately I have limited capacity to review, try out and give useful insight so might take me some time 🙏

Nice work +1 on this

Hi there @chadlwilson! Is there any chance that this PR could move forward in the next month or so? Is there anything I can do to help, or make you more comfortable merging this? If not - no worries - I would probably take a stab at forking the repo, building from a fork, and testing this out more in our production GoCD server.

Thanks for the ping.
Honestly the challenge with these elastic agent plugins is just my concerns around regression and most don't have any particular "integration" tests when actually working with GoCD - and there are a lot of weird timing and other scenarios that can arise with the elastic agent plugins. (e.g what happens if the GoCD server dies, when it comes back does it still correctly adopt the agents or do they end up orphaned? what happens if a pod dies that was expecting to be reused? what if the container restarts inside?). This plugin also happens to probably be the most actively used elastic agent approach.
But ya, the real limitation has been time and energy, distraction and the extra 'friction' on validating this one. it is still on my radar, I've just been kicking the can down the road. But it's a bit easier for me to validate locally now that we have smaller non-Alpine arm64 container images to use on elastic agents.
I naively expected you were probably running this off your own build anyway, is that not the case? :-)


Empty data sets in renewable_power_plants_DE.csv (2017_02_16)

There are 25755 empty datasets in the latest download of Germany's renewable power plants (see screenshot). It does not hurt but it is a little annoying and might be interesting for you.

The empty rows still exist in the new csv-file. It's no big deal, because they only need about 2MB.
I remove them (using pandas) by checking the capacity column (power plants without capacity do not help anyway).
re_power_plants = pandas.read_csv(orig_csv_file)
re_power_plants = re_power_plants[re_power_plants.electrical_capacity.notnull()]

You may add something like this to your code to avoid empty rows. If you want to be sure you can check several rows.


Fix close stale issues when user is commented.

In this PR:
Add file: stale-close-when-update.js close all issues and pull requests that have been marked as stale for more than 7 days for issues and 14 days for pull requests.
Update file: .github/workflows/stale-issues.yml to invoke the script from stale workflow.

I think you only need to remove remove-stale-when-updated: false.
If the issue receives comments it should not be marked as stale, there are people that still care about it!

Thank you for your suggestion @mihaimaruseac. I have made the necessary changes to the workflow accordingly.

PS: Note that your git config is wrong, your email gets quoted in the commit (https://github.com/tensorflow/tensorflow/pull/60672/commits/6140088e0eb5fd9d759f237493a1bffb490d9026) and that required forcing the CLA to pass.

Hi @mihaimaruseac,
I have modified my GitHub configuration. I also made a change so that if a user comments, it will also remove the stale dependent labels. This will eliminate the need for Probot to remove the labels.
Thank You!


iPadOS: Support drag and drop via touch

#83296

Run self hosting bits in iPadOS
Try to drag and drop in File Explorer or in the editor, no luck

This might be a duplicate of https://github.com/microsoft/vscode/issues/83719 but this one is talking about particular feature.

I think in general we lack support for DND with touch gestures. Not sure that is limited to iPad.

Btw: drag and drop works really well for me in Chrome on iPadOS. So they must be emulating the proper events that it works for us.

How use it in iPadOS, is there any doc?

See https://code.visualstudio.com/docs/remote/vsonline


Docker commands inaccurate

When attempting to get started using this article, it instructs a developer to run the command below which results in an error "Error response from daemon: invalid mode: \https".
docker run --rm -it -p 8000:80 -p 8001:443 -e ASPNETCORE_URLS="https://+;http://+" -e ASPNETCORE_HTTPS_PORT=8001 -e ASPNETCORE_Kestrel__Certificates__Default__Password="password" -e ASPNETCORE_Kestrel__Certificates__Default__Path=\https\aspnetapp.pfx -v $env:USERPROFILE\.aspnet\https:C:\https\ mcr.microsoft.com/dotnet/core/samples:aspnetapp

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

ID: 3e087007-7838-e0f9-d713-22182a5d9704
Version Independent ID: 2f32c7c3-8667-0e88-495b-c0c888572964
Content: Hosting ASP.NET Core Images with Docker over HTTPS
Content Source: aspnetcore/security/docker-https.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

What OS?

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core which hasn't been addressed, please file a new issue.


Fixed test modifying global logging config.

Running the following command
$ ./runtests.py logging_tests.tests.SetupConfigureLogging \
    logging_tests.tests.SecurityLoggerTest

results in output:
Testing against Django installed in '…/django'
System check identified no issues (0 silenced).
..Bad Request: /suspicious/
.Bad Request: /suspicious_spec/
.

The SetupConfigureLogging test case does not restore the logging config after its execution. It leaves the logger django.request with an empty handlers array.
From logging.Logger.callHandlers() docstring:

If no handler was found, output a one-off error message to sys.stderr.

That causes the string “Bad Request: /suspicious/” to be logged to stderr by django.core.handlers.BaseHandler.get_response(), because the response status code is >= 400.

Removes the last use of LOGGING_CONFIG, introduced in 43503b093a35ca4707c16d865f10929960bfa0b8 for ticket #16288, originally to test a backward compatibility shim.

Running the following command
$ ./runtests.py logging_tests.tests.SetupConfigureLogging \
    logging_tests.tests.SecurityLoggerTest

results in output:
Testing against Django installed in '…/django'
System check identified no issues (0 silenced).
..Bad Request: /suspicious/
.Bad Request: /suspicious_spec/
.

I cannot reproduce it :thinking:

Thanks for the trying to reproduce. I think the command reported in my commit message is missing --parallel=1. Otherwise the test suites run in parallel and the leak does not occur. I’ve been overzealous in simplifying the command I was using:
$ ./runtests.py logging_tests.tests.SetupConfigureLogging logging_tests.tests.SecurityLoggerTest.test_suspicious_operation_creates_log_message --parallel=1

@francoisfreitag Thanks :+1: I added finally, just in case.

Nevermind, not a good idea.


solr.Query fails

The code below used to work, but now it only returns "The remote server returned an error: (500) Internal Server Error":
Startup.Init<SolrResult>("http://xxx.xxx.xxx.x:xxxx/solr");
var solr = ServiceLocator.Current.GetInstance<ISolrOperations<SolrResult>>();
var query = (new SolrQuery("title:test"));
var results = solr.Query(query);

When I request directly from Solr in the browser it works normally:
http://xxx.xxx.xxx.x:xxxx/solr/query?q=title:test
The error is very generic and I can't track down what the actual cause is, any help is appreciated.

You're probably using an old build of SolrNet. Update to a recent build and it will probably work or at least it will give you more information about the error.


⚠ Bofrost.at has degraded performance

In c9b6a81, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1124 ms

Resolved: Bofrost.at performance has improved in d45ed28.