Atom Crashes on Start after initial install

Prerequisites

[X ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
After install, when attempting to start Atom, application crashes. I receive a message from Windows stating:  "The editor has crashed. Please report this issue to https://github.com/atom/atom".
Windows then gives three options: "Close Window", "Reload", or "Keep It Open".
All three do as described, however, "Keep It Open" just keeps the window open and doesn't allow anything to actually work.
"Reload" will restart the application sometimes without the same error, but once you are working with the application and try to save, another crash occurs.
Steps to Reproduce

Click on Atom.exe icon.
View error.
Close.
repeat 1-2.
Reload.
View error.

Expected behavior:
Expect application to open and be operational.
Actual behavior:
Application crashes on start.
Reproduces how often:
Every time.
Versions
You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.
Atom    : 1.23.3
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0
Additional Information
System Info:
Windows 10 Home
Processor: AMD A9-9430 RADEON R5, 5 COMPTE CORES 2C+3G
RAM: 8.00GB
System type: 64-bit Operating System
Internet connection: Ethernet
[37e13f9a-ed87-4e51-8343-646c37bdda48.txt](https://github.com/atom/atom/files/1692094/37e13f9a-ed87-4e51-8343-646c37bdda48.txt)
operation_log.txt
Any additional information, configuration or data that might be necessary to reproduce the issue.

Yes, it's the newest version and I've never had any other version of Atom on my PC.
Yes, I tried it in safe mode, but it was the same behavior.
I tried to attached the related files in my initial post.

"Reload" will restart the application sometimes without the same error, but once you are working with the application and try to save, another crash occurs.

Are you working on a particular project or file at this point or it doesn't matter what file you try to save (e.g. what about a tiny test file), Atom will crash on save?
Also, if you leave the console tab open while working (http://flight-manual.atom.io/hacking-atom/sections/debugging/#check-for-errors-in-the-developer-tools), do you notice any errors?

No particular project. I just tried a basic "Hello world" in HTML to test it. It really doesn't matter what file is opened or being saved.
I just tried it again and this is the first time I got anything other than the generic windows errors. See attached.

I just tried it again and this is the first time I got anything other than the generic windows errors. See attached.

Oh huh, so now it doesn't crash it just shows those errors?  Which issue is the stack trace linking to?

No, it still crashed first and I reloaded it.
All I did was try to save the file and those are the errors I got.

OK so, I installed Atom on my laptop (which has the same version of Windows 10) and it came up looking entirely different and no crash.

So, I uninstalled the problem Atom on the PC. I even went in and deleted the registry entries and all files. I then installed it again using the same exe file as above. The first time I launched it, this is what I got:

I chose "Close Window" and relaunched it from the desktop shortcut and got the Telemetry tab (but not the welcome tab or the dark theme). When I added a Project folder, I got 4 or 5 of those errors which say:
`[Enter steps to reproduce:]

...
...

Atom: 1.23.3 x64
Electron: 1.6.15
OS: Microsoft Windows 10 Home
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Path must be a string. Received undefined
At path.js:7

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.join (path.js:468:7)
    at ~/AppData/Local/atom/app-1.23.3/resources/app/src/path-watcher.js:184:48
    at Array.map (native)
    at handler (~/AppData/Local/atom/app-1.23.3/resources/app/src/path-watcher.js:177:36)

Commands
     -1:27.1.0 application:add-project-folder (atom-workspace.workspace.scrollbars-visible-always.theme-one-light-syntax.theme-one-light-ui)

Non-Core Packages

However, it does add the Project Folder. When you try to remove the folder or do anything else, I get 1 to 8 of these errors:
`[Enter steps to reproduce:]

...
...

Atom: 1.23.3 x64
Electron: 1.6.15
OS: Microsoft Windows 10 Home
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Path must be a string. Received undefined
At path.js:7

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.join (path.js:468:7)
    at ~/AppData/Local/atom/app-1.23.3/resources/app/src/path-watcher.js:184:48
    at Array.map (native)
    at handler (~/AppData/Local/atom/app-1.23.3/resources/app/src/path-watcher.js:177:36)

Commands

Non-Core Packages

OK so, I installed Atom on my laptop (which has the same version of Windows 10) and it came up looking entirely different and no crash.

Thanks for trying that :+1:

I chose "Close Window" and relaunched it from the desktop shortcut and got the Telemetry tab (but not the welcome tab or the dark theme). When I added a Project folder, I got 4 or 5 of those errors which say:

Can you share the issue link that you get from those errors?
And the files you're working on, are they just on your local drive, no remote/network drive or anything like that?  Not sure what's unique about the machine that's having trouble....
One last thing to confirm, when you went through the debugging steps, did you also try clearing saved state?
http://flight-manual.atom.io/hacking-atom/sections/debugging/#clearing-saved-state

Thanks again for your issue!
We haven't received a response to our question in this comment https://github.com/atom/atom/issues/16680#issuecomment-364549943. With only the information that is currently in the issue, we don't have enough information to take action. I'm going to close this but don't hesitate to reach out if you have or find the answers we need, we'll be happy to reopen the issue.


MaslLibrary should validate the code it compiles

miden-base uses MaslLibrary::read_from_dir to compile the rollup stdlib
MaslLibrary only parses the code with ModuleAst::parse
The parser ignores errors, the test below does not fail:

#[test]
fn call_invalid_loc_store() {
    ModuleAst::parse(
        "\
    proc.invalid.1
        loc_store.1
    end
    ",
    )
    .unwrap();
}

The invalidated library above is serialized to disk
The library is read with the invalid opcode and added to the ModuleProvider with the invalid opcode
Later on:

for re-exports referencing a module with broken code

code that re-exports any procedure from the invalid module will fail to compile
the compilation will fail on the first re-export, which does NOT have to be related to the invalid procedure
the compilation error is swallowed
the result of re-exporting a invalid procedure is AccountCodeAssemblerError(ReExportedProcModuleNotFound(..., name: ProcedureName { name: "receive_asset" })), which is very deceiving.

for execs referencing a module with broken code

the compilation will fail with  AccountCodeAssemblerError(ParamOutOfBounds(1, 0, 0)), which is the right error but no useful context

I split the above into multiple, smaller issues. Some of them may already be worked on, or even fixed on some of the existing PRs.

I wonder if this issue is going to remain relevant once we switch to distributing MAST instead (which I expect to happen shortly after 1277 is merged, as the next in that series of changes):

We won't need to parse/compile the code, since that's already been done
We will need to validate the MAST, but we have to do most of that to properly deserialize it anyway. I think the main thing we'll probably have to do in addition to the validation we already be doing during deserialization is validating the MAST hashes are correct.

As part of that switch, the new package format would also be introduced and used in place of MASL libraries. As a result, I'm not sure MASL libraries will even need to exist at that point. So I suppose my question is: do we try to address these issues before that happens, or do we address them in the switch to MAST?

My preference would be to fix this as a part of transition to MAST-based libraries.

Closing this as libraries are now not just parsed but also compiled to MAST.


Figure out why vpr can't route between PLB.lutff_0_out[0] and BLK_TL-PIO_T.io_0_D_OUT[0]

Figure out why vpr can't route between PLB.lutff_0_out[0] and BLK_TL-PIO_T.io_0_D_OUT[0]
Cannot route from BLK_TL-PLB.lutff_0_out[0] (rr_node: 3352 type: SOURCE ptc: 35 xlow: 5 ylow: 5) to BLK_TL-PIO_T.io_0_D_OUT[0] (rr_node: 5620 type: SINK ptc: 0 xlow: 7 ylow: 10) to -- no possible path
Warning 2290: Unable to route between blocks at (5,5) and (7,10) to characterize delay (setting to inf)
Warning 2291: Empty heap occurred in get_heap_head.
Warning 2292: Some blocks are impossible to connect in this architecture.
Cannot route from BLK_TL-PLB.lutff_0_out[0] (rr_node: 3352 type: SOURCE ptc: 35 xlow: 5 ylow: 5) to BLK_TL-PIO_R.io_0_D_OUT[0] (rr_node: 5732 type: SINK ptc: 0 xlow: 8 ylow: 5) to -- no possible path
Warning 2293: Unable to route between blocks at (5,5) and (8,5) to characterize delay (setting to inf)
Warning 2294: Empty heap occurred in get_heap_head.
Warning 2295: Some blocks are impossible to connect in this architecture.
Cannot route from BLK_TL-PLB.lutff_0_out[0] (rr_node: 3352 type: SOURCE ptc: 35 xlow: 5 ylow: 5) to BLK_TL-PIO_R.io_0_D_OUT[0] (rr_node: 5760 type: SINK ptc: 0 xlow: 8 ylow: 6) to -- no possible path
Warning 2296: Unable to route between blocks at (5,5) and (8,6) to characterize delay (setting to inf)
Warning 2297: Empty heap occurred in get_heap_head.
Warning 2298: Some blocks are impossible to connect in this architecture.
Cannot route from BLK_TL-PLB.lutff_0_out[0] (rr_node: 3352 type: SOURCE ptc: 35 xlow: 5 ylow: 5) to BLK_TL-PIO_R.io_0_D_OUT[0] (rr_node: 5788 type: SINK ptc: 0 xlow: 8 ylow: 7) to -- no possible path
Warning 2299: Unable to route between blocks at (5,5) and (8,7) to characterize delay (setting to inf)
Warning 2300: Empty heap occurred in get_heap_head.
Warning 2301: Some blocks are impossible to connect in this architecture.
Cannot route from BLK_TL-PLB.lutff_0_out[0] (rr_node: 3352 type: SOURCE ptc: 35 xlow: 5 ylow: 5) to BLK_TL-PIO_R.io_0_D_OUT[0] (rr_node: 5816 type: SINK ptc: 0 xlow: 8 ylow: 8) to -- no possible path
Warning 2302: Unable to route between blocks at (5,5) and (8,8) to characterize delay (setting to inf)
Warning 2303: Empty heap occurred in get_heap_head.
Warning 2304: Some blocks are impossible to connect in this architecture.
Cannot route from BLK_TL-PLB.lutff_0_out[0] (rr_node: 3352 type: SOURCE ptc: 35 xlow: 5 ylow: 5) to BLK_TL-PIO_R.io_0_D_OUT[0] (rr_node: 5844 type: SINK ptc: 0 xlow: 8 ylow: 9) to -- no possible path
Warning 2305: Unable to route between blocks at (5,5) and (8,9) to characterize delay (setting to inf)
Placement delay look-up took 0.311494 seconds

What is an easy way to test this?

Run vpr with the rr_graph? make route on the 4mcmaster branch for example. Also can be tested with https://github.com/SymbiFlow/symbiflow-arch-defs/pull/133


Request timed out while fetching Whois data

I am testing the latest release on an AWS US region host, and it's frequently showing an "Error: Request timed out" in the WHOIS download stage.
[ripe] Downloading whois data
[afrinic] Downloading whois data
[apnic] Downloading whois data
[afrinic] Parsing whois data: inetnum,inet6num
[ripe] Parsing whois data: inetnum,inet6num
Error: Request timed out
    at RedirectableRequest.<anonymous> (/snapshot/geofeed-finder/node_modules/nodejs-file-downloader/makeRequest.js:31:37)
    at RedirectableRequest.emit (node:events:537:28)
    at Timeout.<anonymous> (/snapshot/geofeed-finder/node_modules/follow-redirects/index.js:209:12)
    at listOnTimeout (node:internal/timers:564:17)
    at process.processTimers (node:internal/timers:507:7) {
  code: 'ERR_REQUEST_TIMEDOUT'
}
[arin] Downloading stat file
[lacnic-rir] Downloading whois data
[arin] Fetching sub allocations ipv4
[lacnic-rir] Parsing whois data: inetnum
[arin] It was not possible to download precompiled sub allocations ipv4, I will try to compile them from whois instead
[lacnic-rir] Using cached whois data
[lacnic-rir] Parsing whois data: inet6num

Note: The compile command for the ARM64 binary in use is, please upstream this into build.sh: ./node_modules/.bin/pkg ./package.json --targets node18-linux-arm64 --output bin/geofeed-finder-linux-arm64 --loglevel=error

With the latest v1.12.1 , the error is no longer visible in my first test. The entire run finished in 6h3m, so the build isn't timing out. Thanks for the parallelization!
[Container] 2024/01/10 01:54:03.675376 Running command ./bin/geofeed-finder-linux-arm64 -k -o auto-geofeed-latest.csv
[ripe] Downloading whois data
[afrinic] Downloading whois data
[apnic] Downloading whois data
[afrinic] Parsing whois data: inetnum,inet6num
[ripe] Parsing whois data: inetnum,inet6num
[apnic] Parsing whois data
[arin] Downloading stat file
[lacnic-rir] Downloading whois data
[arin] Fetching sub allocations ipv4
[arin] It was not possible to download precompiled sub allocations ipv4, I will try to compile them from whois instead
[lacnic-rir] Parsing whois data: inetnum
[lacnic-rir] Using cached whois data
[lacnic-rir] Parsing whois data: inet6num
[arin] Fetching sub allocations ipv6
[arin] It was not possible to download precompiled sub allocations ipv6, I will try to compile them from whois instead
[arin] Fetching NetRanges
[arin] Using cached whois data: inet6num
https://www.in-berlin.de/geofeed.csv [download]
https://geofeed.bahnhof.net/geofeed.csv [download]

Thank you :)

The latest version was released to fix performance issues.
It uses resumable cache to avoid hammering the RIRs.
I do not think your problem is a matter of high RTT, because the timeout at the moment is 30 seconds. The various RIRs have implemented policies to avoid hammering their server.
Do not wipe the cache at every run and proceed in running the script in crontab once per day.
Any corrupted cache is auto cleaned, the cache is resumable, any error will be solved in the next run. The first run is the slowest one (empty cache).


Unexpected character '`' [./~/vue-bootstrap-pagination/vue-bootstrap-pagination.js:2,0]

I'm having problems again, now with Laravel 5.4 when try to do npm run production. I'm having this:
`[14:27:58] ldelcampo:crm git:(v1.5*) $ npm run production

@ production /Users/ldelcampo/Sites/crm
cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

95% emitting
ERROR  Failed to compile with 1 errors                                                                                2:28:31 PM
error
/js/app.js from UglifyJs
Unexpected character '`' [./~/vue-bootstrap-pagination/vue-bootstrap-pagination.js:2,0][/js/app.js:32970,14]
                                                                                Asset      Size  Chunks                    Chunk Names

fonts/vendor/bootstrap-sass/bootstrap/glyphicons-halflings-regular.eot?f4769f9bdb7466be65088239c12046d1   20.1 kB          [emitted]
fonts/vendor/bootstrap-sass/bootstrap/glyphicons-halflings-regular.svg?89889688147bd7575d6327160d64e760    109 kB          [emitted]
fonts/vendor/bootstrap-sass/bootstrap/glyphicons-halflings-regular.ttf?e18bbf611f2a2e43afc071aa2f4e1512   45.4 kB          [emitted]
fonts/vendor/bootstrap-sass/bootstrap/glyphicons-halflings-regular.woff?fa2772327f55d8198301fdb8bcfc8158   23.4 kB          [emitted]
fonts/vendor/bootstrap-sass/bootstrap/glyphicons-halflings-regular.woff2?448c34a56d699c29117adc64c43affeb     18 kB          [emitted]
/js/app.js   1.24 MB       0  [emitted]  [big]  /js/app
/css/app.css    119 kB       0  [emitted]         /js/app
mix-manifest.json  66 bytes          [emitted]
npm ERR! Darwin 16.5.0
npm ERR! argv "/usr/local/Cellar/node/7.9.0/bin/node" "/usr/local/bin/npm" "run" "production"
npm ERR! node v7.9.0
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! @ production: cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the @ production script 'cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.
`
this is my package.json
{   "private": true,   "scripts": {     "dev": "npm run development",     "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",     "watch": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",     "watch-poll": "npm run watch -- --watch-poll",     "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",     "prod": "npm run production",     "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"   },   "devDependencies": {     "axios": "^0.15.3",     "babel-preset-latest": "^6.24.1",     "bootstrap-sass": "^3.3.7",     "cross-env": "^3.2.3",     "jquery": "^3.1.1",     "laravel-mix": "0.*",     "lodash": "^4.17.4",     "vue": "^2.2.*"   },   "dependencies": {     "vue-bootstrap-pagination": "^2.10.2"   } }

Try to use dev branch

I have the same issue. So I tried to work on the dev branch but I have :
ERROR in static/js/vendor.0d9db1cdebcbd774ed3c.js from UglifyJs
Unexpected token: punc (() [./~/vue-bootstrap-pagination/dist/vue-bootstrap-pagination.esm.js:19,0][static/js/vendor.0d9db1cdebcbd774ed3c.js:29108,9]

Same error here.

ERROR  Failed to compile with 1 errors                                                                                5:38:54 PM
error
/js/vue_bundle.js from UglifyJs Unexpected character '`' [./~/vue-bootstrap-pagination/vue-bootstrap-pagination.js:2,0][/js/vue_bundle.js:53313,14]

I got this issue too:

ERROR in build.js from UglifyJs
Unexpected character '`' [./~/vue-bootstrap-pagination/vue-bootstrap-pagination.js:2,0][build.js:64199,14]

i have same error

UglifyJS still doesn't seem to be supporting ES6 stuff webpack-issue-2545.
I propose you use this workaround for the time being. It's the least time consuming one.
Install Babili Webpack Plugin using npm install babili-webpack-plugin --save-dev or yarn add babili-webpack-plugin --dev, whichever you're using.
Now - inside the webpack.mix.js file insert this:
const BabiliPlugin = require('babili-webpack-plugin');
and
mix.webpackConfig({      plugins: [        new BabiliPlugin()      ]    });
`let mix = require('laravel-mix');
const BabiliPlugin = require('babili-webpack-plugin');
mix.js('resources/assets/js/app.js', 'public/js')
.sass('resources/assets/sass/app.scss', 'public/css')
.options({
uglify: false
})
.webpackConfig({
plugins: [
new BabiliPlugin()
]
});`
This should make your production build pass.

Suggested solution helps with the previous problem, but unfortunately it causes a new one.
Production build takes over 2 minutes, same with watch. It was taking couple seconds before. Waiting 2 minutes to see changes  is unacceptable

Require the dev version of the package and import the .vue file in src folder.

thanks for help

@pogachar @code2prog can you help me? dev version of which package? using Babili my app.js still big, only 23kb difference.

After all i get this file https://github.com/Media24si/vue-pagination/blob/dev/src/vue-bootstrap-pagination.vue from Dev version and include my self in project instead use npm

@ldelcampof don't use babili, use the dev version of the project
put this in your package.json
"vue-bootstrap-pagination": "git://github.com/Media24si/vue-pagination.git#dev",
@code2prog @ldelcampof if you're using the dev branch try updating the package. The production builds should now run successfully without the need to import the .vue file in the src folder. #18

The issue was fixed, so I am closing this thread.

I don't see how this is fixed? Using a development version is a fix? Sounds more like a hazard waiting to happen.


Added Privilege Count and Group Count columns

I don't know why you opened this PR. We didn't reach a consensus in the enhancement request.


Authorization for regions != EU or US

The value of phoneNumber needs to add country code such as: +86
phoneNumber or email, only one of them need to be passed. In China mainland only "phoneNumber" can be passed. In the rest of Asia region, "phoneNumber" or "email" can be passed, and "email" can be passed in Europe and America.

done https://github.com/PJanisio/ewelinkApiPhp/commit/f1981bc732a590b6699d1e3a0fa52d4bf5a781c2


Changed the tabs style

Made it look better. Just some more work needed till it's better.

One other thing, the CSS won't make it look like this but you're going to have to add classes to the left side columns and right side columns.
Just a minor suggestion, allow the user to select a themed colour for their theme.

@OnlyTwentyCharacters It looks like not all your commits were included in the pull request. If you look at your repo it seems like you have multiple branches (patch-1, patch-2, patch-3, patch-4) and commits spread across them. If you could merge all the commits into one (maybe submit pull requests on your repo merging from the patch- branches to master), that would be great. Thanks!


Unbind expressions instead of repeatedly splitting at runtime

Hopefully this will reduce the overhead of multiset functions.

Done


Next Session never starts

After a session is finished it will hold till the next session is ready to start.
However, the next session never starts.
it holds at this:
Ready for botting!🤫
[04/05 10:29:32]     INFO | FastInputIME is the default keyboard.
[04/05 10:29:32]     INFO | Instagram version: <IP_ADDRESS>.123
If I click on the emulator and just open and view atx-agent it will continue to this:
[04/05 13:36:54]    ERROR | Exception: App has crashed / has been closed!
[W 230405 13:36:54 init:492] [pid:95055] [emulator-5554] jsonrpc call got: -32001 Jsonrpc error: <java.lang.NullPointerException> data: java.lang.NullPointerException: Attempt to read from field 'int android.accessibilityservice.AccessibilityServiceInfo.flags' on a null object reference in method 'void androidx.test.uiautomator.UiDevice.setCompressedLayoutHeirarchy(boolean)'
at androidx.test.uiautomator.UiDevice.setCompressedLayoutHeirarchy(UiDevice.java:234)
at com.github.uiautomator.stub.AutomatorServiceImpl.dumpWindowHierarchy(AutomatorServiceImpl.java:295)
at com.github.uiautomator.stub.AutomatorServiceImpl.dumpWindowHierarchy(AutomatorServiceImpl.java:284)
at java.lang.reflect.Method.invoke(Native Method)
at com.googlecode.jsonrpc4j.JsonRpcBasicServer.invoke(JsonRpcBasicServer.java:467)
at com.googlecode.jsonrpc4j.JsonRpcBasicServer.handleObject(JsonRpcBasicServer.java:352)
at com.googlecode.jsonrpc4j.JsonRpcBasicServer.handleJsonNodeRequest(JsonRpcBasicServer.java:283)
at com.googlecode.jsonrpc4j.JsonRpcBasicServer.handleRequest(JsonRpcBasicServer.java:251)
at com.github.uiautomator.stub.AutomatorHttpServer.serve(AutomatorHttpServer.java:100)
at fi.iki.elonen.NanoHTTPD.serve(NanoHTTPD.java:2244)
at fi.iki.elonen.NanoHTTPD$HTTPSession.execute(NanoHTTPD.java:945)
at fi.iki.elonen.NanoHTTPD$ClientHandler.run(NanoHTTPD.java:192)
at java.lang.Thread.run(Thread.java:1012)
, method: dumpWindowHierarchy
[D 230405 13:36:56 init:661] [pid:95055] [emulator-5554] kill process(ps): uiautomator
/opt/homebrew/lib/python3.11/site-packages/packaging/version.py:127: DeprecationWarning: Creating a LegacyVersion has been deprecated and will be removed in the next major release
warnings.warn(
[D 230405 13:36:57 init:682] [pid:95055] [emulator-5554] uiautomator-v2 is starting ... left: 40.0s
[D 230405 13:36:59 init:682] [pid:95055] [emulator-5554] uiautomator-v2 is starting ... left: 38.2s
[D 230405 13:37:00 init:682] [pid:95055] [emulator-5554] uiautomator-v2 is starting ... left: 37.1s
[D 230405 13:37:00 init:696] [pid:95055] [emulator-5554] show float window
[D 230405 13:37:01 init:682] [pid:95055] [emulator-5554] uiautomator-v2 is starting ... left: 36.0s
[D 230405 13:37:02 init:682] [pid:95055] [emulator-5554] uiautomator-v2 is starting ... left: 35.0s
[D 230405 13:37:03 init:682] [pid:95055] [emulator-5554] uiautomator-v2 is starting ... left: 34.0s
[D 230405 13:37:04 init:682] [pid:95055] [emulator-5554] uiautomator-v2 is starting ... left: 33.0s
[I 230405 13:37:04 init:643] [pid:95055] [emulator-5554] uiautomator back to normal
[04/05 13:37:04]     INFO | Crash saved as crashes/3.2.4_2023-04-05-13-36-54.zip
[04/05 13:37:04]     INFO | If you want to report this crash, please upload the dump file via a ticket in the #lobby channel on discord
[04/05 13:37:04]     INFO | https://discord.gg/66zWWCDM7x
[04/05 13:37:04]     INFO |
[04/05 13:37:04]     INFO | TOTAL
[04/05 13:37:04]     INFO | Completed sessions: 0
[04/05 13:37:04]     INFO | Total duration: 3:08:33
[04/05 13:37:04]     INFO | Total interactions: (0) 0
[04/05 13:37:04]     INFO | Successful interactions: (0) 0
[04/05 13:37:04]     INFO | Total followed: (0) 0
[04/05 13:37:04]     INFO | Total likes: 0
[04/05 13:37:04]     INFO | Total comments: 0
[04/05 13:37:04]     INFO | Total PM sent: 0
[04/05 13:37:04]     INFO | Total watched: 0
[04/05 13:37:04]     INFO | Total unfollowed: 0
[04/05 13:37:04]     INFO | This bot is backed with love by me for free. If you like using it, consider donating to help keep me motivated: https://www.buymeacoffee.com/mastrolube
I can't figure out why it seems to be timing out or how to fix this issue.
I am using an M1 mac w/ Android Studio. The emulator is Pixel 4 w/ Android 12.
Any help on this would be much appreciated so i do not need to keep manually starting sessions.

Have you tried the supported version of Instagram?  <IP_ADDRESS>.117 instead of <IP_ADDRESS>.123?

Yeah, I also tried it with that version too.
I think it's something with the atx-agent like it's timing out.

Also came across this: https://github.com/openatx/uiautomator2/issues/813

What android version are you running?  If not 12 try that if possible.

I suspect you already ran "python3 -m uiautomator2 init" to make sure it's updated.  I am on a physical pixel 4a with android 12 and it's not having this issue.

I have my screen on 100% of the time (in developer options) and have screen-sleep: false in the configuration file.  If you are on an emulator, you probably do that already, but might be something to try.

I found the same issue using the same setup as yours.  You might try commenting out line 347 kill_atx_agent(device) on bot_flow.py which kills the atx agent during bot turn off.  Worked for me, but haven't fully tested it.

There are a few others in utils.py.  I commented out both and am still testing.

Did you find any fix for this? It happens to me also on Android 12.

Same here, uiautomatro2 check does fix it, but error occurs later.


When tina is synchronized by the save button, can the git command be configured?

Description
Due to project issues, my repository needs to pass -n to ignore some eslint syntax when submitting. I want to modify the commit command to -n.
Is this parameter configurable?

git commit -n

Hey @sk894703472 this is currently not possible. It's late here, but I'll start looking into it in the next couple days.
Thanks for bringing this up 😄


GitHub token is not verified

There should be simple verification on the GitHub tokens users enter in their profile to ensure it at least conceivably is a token.  Only hexadecimal digits, and 40 digits (I think) long.

We should probably also try to verify the token is valid.  That is as easy as checking the rate limit for the given token:
$ curl -H "Authorization: token BAD-TOKEN" https://api.github.com/rate_limit
{
  "message": "Bad credentials",
  "documentation_url": "https://developer.github.com/v3"
}
$ curl -H "Authorization: token GOOD-TOKEN" https://api.github.com/rate_limit
{
  "resources": {
    "core": {
      "limit": 5000,
      "remaining": 4997,
      "reset":<PHONE_NUMBER>
    },
    "search": {
      "limit": 30,
      "remaining": 30,
      "reset":<PHONE_NUMBER>
    },
    "graphql": {
      "limit": 5000,
      "remaining": 5000,
      "reset":<PHONE_NUMBER>
    },
    "integration_manifest": {
      "limit": 5000,
      "remaining": 5000,
      "reset":<PHONE_NUMBER>
    }
  },
  "rate": {
    "limit": 5000,
    "remaining": 4997,
    "reset":<PHONE_NUMBER>
  }
}

if we do an actual verification, we can also test the response headers to look for X-OAuth-Scopes: public_repo


Update Harbor version to "0.5.0" in About Harbor dialog.

Please update the Harbor version to "0.5.0" in About Harbor dialog.

this tag generate by Github status
if github tag 0.5.0 rc or some else, image make process will generate new version label for harbor.

Verified and passed on 0.5.0 rc1 build .

Verified and passed on 0.5.0 rc2 build.


Not working with iOS

i can't move the range slider with IOS devices like Ipad, Iphone
Controls are visible, when i try to move nothings is happenning .

i added touch simulate events with Javascript, so now it's working for all the touch devices, so am closing this issue


bump glob, handlebars, object.assign and promise

bump glob, handlebars, object.assign and promise

https://david-dm.org/ericf/express-handlebars

Thanks!


docs(showcase): add SSE urql exchange package

Summary

Set of changes

Thanks @kitten ❤

No worries! 🙌 Very excited for the first service, Grafbase, to my knowledge proliferating live queries, finally!
I'm currently not sure whether it complies with the hasNext flag and such in its current implementation, and was a little surprised to see  the JSON patch responses rather than the Incremental Delivery payloads as laid out in the GraphQL spec proposals 🤔
I'm hoping overlap here will increase over time, since this allows us to potentially support SSE for @live queries built into the core library.
But happy to learn more soon to dig into this. Currently, it seems the custom exchange is a good choice since multiple transports are obviously possible. I was just surprised to see there's less overlap than expected to @defer/@stream's reference payloads & implementation 👀

@kitten thanks! I believe we're the first to provide Live Queries with packages like this exchange that make it a breeze to adopt. I'm excited!
That said, we're still early days with Live Queries. We plan to add an arg to the @live(...) directive so we should be able to cover a range of different implementations.
We'll soon explore @stream/@defer with the above considerations too.


New transactions (Boost, Article)

[x] Boost Post
[x] Article Post

I encounter unexpected node drops in the test network - unfortunately without details. I'm building a debug version

@tawmaz @lostystyg The main works are finished - it is necessary to review

Have these new transactions been tested to not cause a fork in the chain?  If they do cause a fork we should define a block height in the code where they become active (example: 1600000) and bump protocol version, and communicate this to node operators so they have time to update nodes.

Have these new transactions been tested to not cause a fork in the chain? If they do cause a fork we should define a block height in the code where they become active (example: 1600000) and bump protocol version, and communicate this to node operators so they have time to update nodes.

By the way, a good note, we forgot to prohibit the processing of such transactions through the ROC. But I think we can go further and ban them at the consensus level so as not to release an additional version. I'll do it in the morning.
Do you have any ideas about the protocol version? I've been wanting to start implementing new functionality for a long time along with changing the protocol version, but I don't have enough time for this


Creating Stub users in D365 online doesn't assign the security role

I have tried creating a stub user both through code as well as through data import, but the CRM platform doesn't assign a security role to the stub user. What should I do to get the security role assigned?

Is there any solution for this? I created a stub user in V9 and the role is not assigned. Not sure what is the purpose of the stub user, if we are not able to assign role.

Hi there - now end of september - is this fixed?

This is fixed.  Please verify.  Thanks.


brew update gives lots of "Permission denied (publickey)" git errors

[x] Ran brew doctor, fixed as many issues as possible and retried your prior step?

Bug reports:
Unable to use brew update, output:
> brew update
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Error: Fetching /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask failed!
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-php failed!
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core failed!
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-dupes failed!

Brew version:
> brew -v
Homebrew 1.0.5-35-g8608e48
Homebrew/homebrew-core (git revision 227e; last commit 2016-09-22)

brew update --verbose will help you figure out which repositories you need to fix your GitHub access credentials for.

If you've upgrade to macOS Sierra there's a known issue (which seems deliberate on Apple's part) where it no longer reads your SSH passphrase from the Keychain, so every time you reboot you have to manually ssh-add -A if you fetch stuff from Git over SSH, otherwise you will see issues like that.
See https://github.com/jirsbek/SSH-keys-in-macOS-Sierra-keychain and the various sources linked to from there.

@DomT4 ssh-add -A fixed the problem, thanks.

(although, weirdly, git-over-ssh has been working for me this entire time, just not with homebrew)

@gfarrell Same thing here. Only experienced the issue with Homebrew for some reason.
Thanks to @DomT4, ssh-add -A did the job 👍


Empty Url Params

node.js version: v8.11.2
npm/yarn and version: 6.1.0
koa-router version: 7.4.0
koa version: 2.5.1
Code sample:
var Koa = require('koa');
var Router = require('koa-router');

var app = new Koa();
var router = new Router();

router.get('/avatar/email/:email', (ctx, next) => {
  ctx.status = 200;
  ctx.body = 'text'
});

app
  .use(router.routes())
  .use(router.allowedMethods());

app.listen(3000);

Expected Behavior:
When I use this url: http://localhost:3000/avatar/email/ I want the route to be catched.
It works when is use<EMAIL_ADDRESS>Actual Behavior:
When I use this url: http://localhost:3000/avatar/email/ It returns Not Found

This is how route matching works. A named param in your route :email is not optional unless it ends with a ?. See the path-to-regexp readme for more info.


feat: add Display trait to Keycode

This crate already provides a way to convert strings to keycodes, not the other way round though: This is a quick implementation simply using the write macro.

I don't know whether there are better ways to process keycodes as strings but the Display trait. Feel free to educate me!

Nope, this is the right approach. Thanks for the PR!


Fix ORR to account for the different behavior of its MOV alias

Description:
Fix spec. of ORR to account for the behavior of its "alias" MOV.
Testing:
make all succeeded on my M3.
License:
By submitting this pull request, I confirm that my contribution is
made under the terms of the Apache 2.0 license.

Update description of the PR.


Add hlint --grep and --sed

HLint can do a bit of stuff for grep/sed like functionality. I should package it more nicely and expose it.

This got added, but never encouraged for people to use it. Honestly, it's a bit slow, and real grep isn't that bad. If someone wants to develop and promote it go for it, but otherwise, it's probably just going to sit there rotting.


Is there support for Jenknis and Gerrit?

According to the documentation only GitHub and GitLab are supported.
Is a local instance of Gerrit supported? couldn't find a mention of it.
Is there in integration with Jenkins?
If not, is it possible to interact with python-semantic-release from command line?

As far as I know we don't support either of these, however if you need this functionality feel free to open a feature request for each.
For interacting from the command line, take a look at this page.


add 1 worker ,but get 2 record on rancher UI

I install rancher with rke ,the I update the cluster.yml to add a worker host,but I get 2 record  on rancher UI

duplicated of https://github.com/rancher/rancher/issues/14011


⚠ Cioos National CKAN Sitemap has degraded performance

In 21be05f, Cioos National CKAN Sitemap (https://catalogue.cioos.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 14223 ms

Resolved: Cioos National CKAN Sitemap performance has improved in e51dda8 after 3 minutes.


Add Tekton Install to the cluster build

We can use tekton to support any demo that requires a git repo.

Do we still want this?  Or do we want to try this instead https://cloud.google.com/deploy


(fix) Script (Lite) Strategy incorrect subclass import

Before submitting this PR, please make sure:

[x] Your code builds clean without any errors or warnings
[x] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
The creation of the class for a new subclass of ScriptStrategyBase incorrectly select the base class ScriptStrategyBase when the getmembers() ordering puts the new class lower than ScriptStrategyBase.
This is because in the next() lookup function because issubclass(cls, cls) = True (a class is a subclass of itself in Python)
Tests performed by the developer:
Passed the failed import of the user local class ScriptStrategyReload, which fails when hummingbot attempts to initialize the markets, which in ScriptStrategyBase is None
Tips for QA testing:
Updated the existing Unittests case with a loading of the test_dca_example.py

Hello @MementoRC. It seems like your configuration is not the correct one. You should not be defining new script classes in the same module where ScriptStrategyBase class is defined. When you create new script classes in their own modules then getmembers() will never return the superclass, because it is not part of that module.
Also, please don't commit new script strategies to the project. We are not expecting the community to submit new script strategies to the baseline.

I am not defining it in the same module, I did debug and see to my surprise that ScriptStrategyBase was picked up
It seems to me that the ScriptStrategyBase will be defined in the module due to:
from hummingbot.strategy.script_strategy_base import ScriptStrategyBase
My Lite Strategy is very basic. simply importing the base class and running the test. I added the test_dca... because I needed to put a testcase in place and hummingbot looks into the scripts directory to find the Lite scripts
I will look into this more carefully
Thank you

Please look at the screenshot below of the debugger. The module does include ScriptStrategyBase, and a printout of inspect.getmembers(script_module) has ScriptStrategyBase as a member

As you can see, when the PR is removed, the test fails:


chore(goreleaser): [Policy Assistant] fix format of checksum file

For the tag v0.0.1-policy-assistant, the checksum file looks like:
policy_assistant_0.0.1_checksums.txt
This PR:

Changes policy_assistant to policy-assistant
Stops truncating the version at the first hyphen (0.0.1 to v0.0.1-policy-assistant)

New checksum file:
policy-assistant_v0.0.1-policy-assistant-SNAPSHOT-8a8d312_checksums.txt
goreleaser output
noting the full output:

$ goreleaser release --snapshot --clean
  • only configurations files on  version: 2  are supported, yours is  version: 0 , please update your configuration
  • skipping announce, publish and validate...
  • cleaning distribution directory
  • loading environment variables
  • getting and validating git state
    • git state                                      commit=8a8d31217326e5cb23c955995d2adddcb73daea0 branch=goreleaser current_tag=v0.0.1-policy-assistant previous_tag=v0.1.5 dirty=false
    • pipe skipped                                   reason=disabled during snapshot mode
  • parsing tag
  • setting defaults
  • snapshotting
    • building snapshot...                           version=0.0.1-policy-assistant-SNAPSHOT-8a8d312
  • ensuring distribution directory
  • setting up metadata
  • writing release metadata
  • loading go mod information
  • build prerequisites
  • building binaries
    • building                                       binary=dist/policy-assistant_windows_amd64_v1/policy-assistant.exe
    • building                                       binary=dist/policy-assistant_darwin_amd64_v1/policy-assistant
    • building                                       binary=dist/policy-assistant_linux_amd64_v1/policy-assistant
  • archives
    • creating                                       archive=dist/policy-assistant_windows_amd64.zip
    • creating                                       archive=dist/policy-assistant_darwin_amd64.tar.gz
    • creating                                       archive=dist/policy-assistant_linux_amd64.tar.gz
  • calculating checksums
  • writing artifacts metadata
  • release succeeded after 5s
  • thanks for using goreleaser!

/ok-to-test

ok
/lgtm


Support channels_first in rnn layers

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

Comparison is base (ee2252e) 79.07% compared to head (a59fdf5) 56.12%.
Report is 1 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #18806       +/-   ##
===========================================
- Coverage   79.07%   56.12%   -22.95%
===========================================
  Files         336      336
  Lines       34234    34234
  Branches     6694     6694
===========================================
- Hits        27070    19215     -7855
- Misses       5582    13562     +7980
+ Partials     1582     1457      -125

Flag
Coverage Δ

keras
56.12% <ø> (-22.84%)
:arrow_down:

keras-jax
?

keras-numpy
56.12% <ø> (+<0.01%)
:arrow_up:

keras-tensorflow
?

keras-torch
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Thread ‘main’ panicked at ‘attempt to subtract with overflow’

Entering 0 to go back (because that's what I learned from gild), this is what I get:
thread 'main' panicked at 'attempt to subtract with overflow', src/menu.rs:556:68
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

Setting the suggested environment variable doesn't add any information, just 24 lines with
N: <unknown>

where N is in the interval 0..23.

Whoops sorry, I have always been bad at maths...
It should be fixed now in 7119c5f6061b89382ca1d0d15cf65d7ef447d075, I'll push a new release soon. Thank you for trying phetch!


Can´t connect traccar client on android.

Cheers,
the reason why I write on this platform is because I have a drawback with traccar client for android, the point is that we assign the IP address of the computer that hosts the server and port as well, but does not mark the position of device. I appreciate help me.

Are you sure the port is visible from internet? You can check here: http://www.tananaev.com/port.html

let me check if the port is open.. Thanks
2016-01-15 14:24 GMT-05:00 Anton Tananaev<EMAIL_ADDRESS>
Are you sure the port is visible from internet? You can check here:
http://www.tananaev.com/port.html
—
Reply to this email directly or view it on GitHub
https://github.com/tananaev/traccar-client-android/issues/176#issuecomment-172059708
.

anton, i created a new rule on the firewall for open the port 5055 on my
computer but still showong port is closed.
what can i do ?
2016-01-15 14:26 GMT-05:00 Sistemas Trans. Chevalier <
<EMAIL_ADDRESS>
let me check if the port is open.. Thanks
2016-01-15 14:24 GMT-05:00 Anton Tananaev<EMAIL_ADDRESS>
Are you sure the port is visible from internet? You can check here:
http://www.tananaev.com/port.html
—
Reply to this email directly or view it on GitHub
https://github.com/tananaev/traccar-client-android/issues/176#issuecomment-172059708
.

Are you sure your ISP provide you with public IP address?

the ip must be public ?
what if is private ?
2016-01-16 2:04 GMT-05:00 Anton Tananaev<EMAIL_ADDRESS>
Are you sure your ISP provide you with public IP address?
—
Reply to this email directly or view it on GitHub
https://github.com/tananaev/traccar-client-android/issues/176#issuecomment-172167520
.

If it's private, it means it's technically impossible for the Traccar Client app to connect to it.

but exists any possibility to make the app works?
2016-01-16 15:46 GMT-05:00 Anton Tananaev<EMAIL_ADDRESS>
If it's private, it means it's technically impossible for the Traccar
Client app to connect to it.
—
Reply to this email directly or view it on GitHub
https://github.com/tananaev/traccar-client-android/issues/176#issuecomment-172256888
.

As I said, if you don't have a public IP address, it's not possible to host your own server.


How to correctly configure Envoy to work as an HTTPS Proxy?

Have trouble configuring Envoy to correctly proxy HTTPS-over-HTTPS proxy request.
Description:
I have a use a case to support HTTPS-over-HTTPS proxy, where the inner TLS is not terminated by the proxy.
I have a test upstream server running at localhost:4443, which serves HTTPS.
I also have envoy configured as below, which listens on port 10000, and has TLS turned on.
static_resources:
  listeners:
  - address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 10000
    filter_chains:
    - filters:
#     - name: envoy.filters.network.tcp_proxy
#       typed_config:
#         "@type": type.googleapis.com/envoy.extensions.filters.network.tcp_proxy.v3.TcpProxy
#         cluster: tcp-https
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          route_config:  # config.route.v3.RouteConfiguration
            name: local_route
            virtual_hosts:
            - name: ingress_http
              domains: ["*"]
              routes:
              - name: connect_request
                match:
                  connect_matcher: {}
                route:
                  cluster: tcp-https
                  upgrade_configs:
                  - upgrade_type: CONNECT
                    connect_config: {}
          upgrade_configs:
          - upgrade_type: CONNECT
      transport_socket:
        name: envoy.transport_sockets.tls
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext
          common_tls_context:
            tls_certificates: <redacted>
  clusters:
  - name: tcp-https
    type: STRICT_DNS
    lb_policy: ROUND_ROBIN

The expected result is:

Envoy receives the CONNECT request over TLS, and terminates this layer's TLS.
Envoy selects the upstream cluster tcp-https as TCP forward proxy.

Resolves the destination from the CONNECT request.
Uses the DNS result as the upstream server address.
Envoy establishes a TCP connection to my test server.

Envoy then TCP proxies the packets received in the tunnel.

The second TLS is established between the downstream and the upstream directly, which envoy doesn't terminate.

The test command I ran was curl -v --proxy-insecure -kx "https://localhost:10000" "https://localhost:4443"
However, when ran the test command, it cannot work.
After TLS is established between downstream and envoy, the inner TLS message cannot be forwarded  properly.
*   Trying <IP_ADDRESS>:10000...
* Connected to (nil) (<IP_ADDRESS>) port 10000 (#0)
* ALPN: offers http/1.1
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server did not agree on a protocol. Uses default.
* Proxy certificate:
*  subject: CN=front-envoy
*  start date: Jul  8 01:31:46 2020 GMT
*  expire date: Jul  6 01:31:46 2030 GMT
*  issuer: CN=front-envoy
*  SSL certificate verify result: self-signed certificate (18), continuing anyway.
* allocate connect buffer
* Establish HTTP proxy tunnel to <IP_ADDRESS>:4443
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> CONNECT <IP_ADDRESS>:4443 HTTP/1.1
> Host: <IP_ADDRESS>:4443
> User-Agent: curl/7.86.0
> Proxy-Connection: Keep-Alive
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS alert, close notify (256):
* Proxy CONNECT aborted
* CONNECT phase completed
* Closing connection 0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS alert, close notify (256):
curl: (56) Proxy CONNECT aborted

From Envoy's log, the CONNECT request is correctly received and parsed, but it doesn't try to connect to the upstream. Any idea how this can work? Did I miss something in the config?
[2023-01-26 18:09:14.268][92777][trace][misc] [envoy/src/source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x5bb7f36b570 for 3600000ms, min is 3600000ms
[2023-01-26 18:09:14.268][92777][debug][conn_handler] [envoy/src/source/extensions/listener_managers/listener_manager/active_tcp_listener.cc:147] [C0] new connection from <IP_ADDRESS>:50934
[2023-01-26 18:09:14.268][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:568] [C0] socket event: 2
[2023-01-26 18:09:14.268][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:679] [C0] write ready
[2023-01-26 18:09:14.268][92777][trace][connection] [envoy/src/source/extensions/transport_sockets/tls/ssl_handshaker.cc:93] [C0] ssl error occurred while read: WANT_READ
[2023-01-26 18:09:14.271][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:568] [C0] socket event: 3
[2023-01-26 18:09:14.271][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:679] [C0] write ready
[2023-01-26 18:09:14.271][92777][trace][connection] [envoy/src/source/extensions/transport_sockets/tls/ssl_handshaker.cc:93] [C0] ssl error occurred while read: WANT_READ
[2023-01-26 18:09:14.271][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:608] [C0] read ready. dispatch_buffered_data=0
[2023-01-26 18:09:14.271][92777][trace][connection] [envoy/src/source/extensions/transport_sockets/tls/ssl_handshaker.cc:93] [C0] ssl error occurred while read: WANT_READ
[2023-01-26 18:09:14.272][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:568] [C0] socket event: 3
[2023-01-26 18:09:14.272][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:679] [C0] write ready
[2023-01-26 18:09:14.276][92777][trace][connection] [envoy/src/source/extensions/transport_sockets/tls/ssl_handshaker.cc:93] [C0] ssl error occurred while read: WANT_READ
[2023-01-26 18:09:14.276][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:608] [C0] read ready. dispatch_buffered_data=0
[2023-01-26 18:09:14.276][92777][trace][connection] [envoy/src/source/extensions/transport_sockets/tls/ssl_handshaker.cc:93] [C0] ssl error occurred while read: WANT_READ
[2023-01-26 18:09:14.278][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:568] [C0] socket event: 3
[2023-01-26 18:09:14.278][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:679] [C0] write ready
[2023-01-26 18:09:14.279][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:423] [C0] raising connection event 2
[2023-01-26 18:09:14.279][92777][trace][conn_handler] [envoy/src/source/extensions/listener_managers/listener_manager/active_stream_listener_base.cc:111] [C0] connection on event 2
[2023-01-26 18:09:14.279][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:608] [C0] read ready. dispatch_buffered_data=0
[2023-01-26 18:09:14.279][92777][trace][connection] [envoy/src/source/extensions/transport_sockets/tls/ssl_socket.cc:87] [C0] ssl read returns: 112
[2023-01-26 18:09:14.279][92777][trace][connection] [envoy/src/source/extensions/transport_sockets/tls/ssl_socket.cc:87] [C0] ssl read returns: -1
[2023-01-26 18:09:14.279][92777][trace][connection] [envoy/src/source/extensions/transport_sockets/tls/ssl_socket.cc:127] [C0] ssl error occurred while read: WANT_READ
[2023-01-26 18:09:14.279][92777][trace][connection] [envoy/src/source/extensions/transport_sockets/tls/ssl_socket.cc:163] [C0] ssl read 112 bytes
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:625] [C0] parsing 112 bytes
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:567] [C0] message begin
[2023-01-26 18:09:14.280][92777][debug][http] [envoy/src/source/common/http/conn_manager_impl.cc:306] [C0] new stream
[2023-01-26 18:09:14.280][92777][trace][misc] [envoy/src/source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x5bb7f36a910 for 300000ms, min is 300000ms
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:524] [C0] completed header: key=Host value=<IP_ADDRESS>:4443
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:524] [C0] completed header: key=User-Agent value=curl/7.86.0
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:818] [C0] onHeadersCompleteBase
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:524] [C0] completed header: key=Proxy-Connection value=Keep-Alive
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:863] [C0] codec entering upgrade mode for CONNECT request.
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:1135] [C0] Server: onHeadersComplete size=3
[2023-01-26 18:09:14.280][92777][debug][http] [envoy/src/source/common/http/conn_manager_impl.cc:972] [C0][S17099123925864753453] request headers complete (end_stream=false):
':authority', '<IP_ADDRESS>:4443'
':method', 'CONNECT'
'user-agent', 'curl/7.86.0'
'proxy-connection', 'Keep-Alive'

[2023-01-26 18:09:14.280][92777][debug][connection] [envoy/src/source/common/network/connection_impl.h:92] [C0] current connecting state: false
[2023-01-26 18:09:14.280][92777][trace][misc] [envoy/src/source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x5bb7f36a910 for 300000ms, min is 300000ms
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:922] [C0] message complete
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:930] [C0] Pausing parser due to upgrade.
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:675] [C0] parsed 112 bytes
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:602] [C0] direct-dispatched 0 bytes
[2023-01-26 18:09:14.280][92777][trace][http] [envoy/src/source/common/http/http1/codec_impl.cc:1222] [C0] body size=0
[2023-01-26 18:09:14.280][92777][trace][misc] [envoy/src/source/common/event/scaled_range_timer_manager_impl.cc:60] enableTimer called on 0x5bb7f36a910 for 300000ms, min is 300000ms
[2023-01-26 18:09:14.280][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:568] [C0] socket event: 2
[2023-01-26 18:09:14.280][92777][trace][connection] [envoy/src/source/common/network/connection_impl.cc:679] [C0] write ready
[2023-01-26 18:09:14.897][92752][debug][main] [envoy/src/source/server/server.cc:265] flushing stats
[2023-01-26 18:09:19.901][92752][debug][main] [envoy/src/source/server/server.cc:265] flushing stats
[2023-01-26 18:09:24.904][92752][debug][main] [envoy/src/source/server/server.cc:265] flushing stats
[2023-01-26 18:09:29.909][92752][debug][main] [envoy/src/source/server/server.cc:265] flushing stats

cc: @alyssawilk

Hi @ikimonogakari, do you config the cluster transport socket? I just saw the config in listener. You may need a config in the cluster like:
clusters:
  - name: some_service
    # Upstream TLS configuration.
    transport_socket:
      name: envoy.transport_sockets.tls
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext

Correct me if I understand wrongly.
The upstream connection should a pure TCP connection in my use case, a HTTPS over HTTPS proxy.
The outer TLS is terminated by Envoy, and then forward whatever it receives to the upstream.
The upstream assumes the incoming traffic is HTTPS, and establishes a TLS session with it.
If the upstream is also configured to use TLS, which means the inner TLS is then wrapped with another layer of TLS again. So that my upstream server should understand to terminate two layers of TLS.

I have the following test configure working. Copied from this example.
  clusters:
  - name: forward_https
    type: ORIGINAL_DST
    lb_policy: CLUSTER_PROVIDED
    original_dst_lb_config:
      use_http_header: true
      http_header_name: ":authority"

However, this upstream cannot do DNS for the destination. If the destination defined in the :authority is not a plain ip:port, it cannot resolve it correctly. So that is why I used STRICT_DNS at first. But how can I configure the cluster to do DNS in the ORIGINAL_DST mode?

@ikimonogakari did you ever get this working with DNS


Prepare for release and memory leak fix

/azp run net - servicebus - tests

API change check
API changes are not detected in this pull request.

/check-enforcer override

Failure is a timeout for an unrelated test.   Merging.


Visual Studio 2022 Issue

Hey! I just downloaded Visual Studio and am a completely new user. I am not in full screen mode, but have no Tool menu option. Only  "File | Edit | Selection | View | Go | Run | Terminal | Help". I would really appreciate it if someone could help me figure out how to get the Tools and other menu options working in Visual Studio 2022.

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

ID: 49fe9dd7-3720-5ea9-6c5a-7bde27cb993e
Version Independent ID: c7c693df-ef68-dc9f-268e-ffac03132a29
Content: Customize menus and toolbars - Visual Studio (Windows)
Content Source: docs/ide/how-to-customize-menus-and-toolbars-in-visual-studio.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @TerryGLee
Microsoft Alias: tglee

Hi @drag737 From the list of menu options you listed, it appears that you are running Visual Studio Code, not Visual Studio IDE.
What does your editor say on the top menu bar?
You can check your installation by running Help > About and you should see "Visual Studio Code" in the dialog.
If you are running Visual Studio IDE, you can check by running Help > About Microsoft Visual Studio.


New command: Create a Microsoft Teams team with a custom template

Create a new Microsoft Teams team by specifying a custom template.

command: graph teams add --templateFile <templateFilePath>
templateFilePath - Path of the json file describing the teams custom template
Graph API Endpoint (beta) - https://docs.microsoft.com/en-us/graph/api/team-post?view=graph-rest-beta

I could pickup this one up @waldekmastykarz if you think the syntax is fine.

Great suggestion @vman! This is actually a duplicate of #794. @kshsbala has just submitted a PR with the basic add command #862. Once I've processed it, we could extend it with the support for templates. @BobGerman wanted to pick it up initially, but I haven't heard from him lately, so let's see where we stand when the PR is merged, ok? I'm going to close this one so that we can track it in #794.

Ideally you should be able to use the CLI to both extract a template from an existing Team and provision a Team using a template. The latter is already supported by a Graph API and uses a formalized template structure which makes it better to ensure that the generated template is exchangeable between the CLI and other solutions/provisioning engines.

@vman if you're still interested in doing this, would you mind creating a new issue with a spec to extend the existing graph teams add command with support for templates?

@waldekmastykarz I will create the new issue with the proposed spec but I don't think I will have the cycles to work on it soon. Happy for someone else to pick it up.

Perfect! Appreciate your help 👏


Extraction of custom files/tree from archive is not done during domain creation

Hi,
The 1.9.18 release touts this feature:

User can create a folder in the archive to store custom files like application config, see #944

This is then intended to be implemented by PR https://github.com/oracle/weblogic-deploy-tooling/pull/969
Unfortunately, it doesn't work. Looking at the PR, it adds a line of 'self.library_helper.extract_custom_files()' in topology_updater.py, which (I assume) will do extraction during an update. But during a create, this code is not called. Instead there is an addition of just an empty line in domain_creator.py; I'm assuming the intention was to insert the same extract_custom_files() call there and a test confirms this will indeed cause the files to extract during create.
Thanks,
ken1

Working on this bug

@CarolynRountree i tested the nw WDT (1.9.19).
I had a running domain created with 1.9.18, i added a new auxilary image, and was expecting the custom folder to be expanded on the $DOMAIN_HOME, but not the case.
Could you confirm the update scenario should work?
In the pod
[oracle@sample-domain1-managed-server1 weblogic-deploy]$ pwd
/auxiliary/weblogic-deploy
[oracle@sample-domain1-managed-server1 weblogic-deploy]$ cat VERSION.txt
WebLogic Deploy Tooling 1.9.19[oracle@sample-domain1-managed-server1 weblogic-deploy]$
[oracle@sample-domain1-managed-server1 base_domain]$ pwd
/u01/domains/base_domain
[oracle@sample-domain1-managed-server1 base_domain]$ ls -lrt
total 488
-rw-r----- 1 oracle oracle    327 Apr 26  2019 fileRealm.properties
drwxr-x--- 2 oracle oracle   4096 Jan  7 10:09 console-ext
drwxr-x--- 3 oracle oracle   4096 Jan  7 10:09 common
drwxr-x--- 2 oracle oracle   4096 Jan  7 10:09 autodeploy
-rwxr-x--- 1 oracle oracle    240 Jan  7 10:09 startWebLogic.sh
drwxr-x--- 2 oracle oracle   4096 Jan  7 10:09 security
drwxr-x--- 6 oracle oracle   4096 Jan  7 10:09 bin
drwxr-x--- 2 oracle oracle   4096 Jan  7 10:09 nodemanager
drwxr-x--- 3 oracle oracle   4096 Jan  7 10:09 init-info
drwxr-xr-x 2 oracle oracle   4096 Jan 12 14:41 lib
drwxr-xr-x 8 oracle oracle   4096 Jan 12 14:41 wlsdeploy
drwxr-x--- 4 oracle oracle   4096 Jan 12 14:41 servers
drwxr-x--- 2 oracle oracle   4096 Jan 12 14:42 logs
drwxr-x--- 9 oracle oracle   4096 Jan 12 14:43 config
[oracle@sample-domain1-managed-server1 custom]$ pwd
/u01/domains/base_domain/wlsdeploy/custom
[oracle@sample-domain1-managed-server1 custom]$ ls -lrt
total 8
drwxr-xr-x 4 oracle oracle 4096 Jul 14 07:42 _application_files
drwxr-xr-x 2 oracle oracle 4096 Jan 12 10:09 classes
the 2 custom folder are not extracted to $DOMAIN_HOME

@belfo We followed the structure of the archive file to extract under wlsdeploy/custom https://oracle.github.io/weblogic-deploy-tooling/concepts/archive/. This is under $DOMAIN_HOME but I take it you need it directly under domain home. Can you clarify what and why please?

@CarolynRountree That was my comprehension of extracting in the idea of "custom is extracted under $DOMAIN_HOME" So i misunderstood.
They why is because we have an app that look for the $DOMAIN_HOME/classes for a config file.
Will look into it to see if it work by having a wlsdeploy/custom in in the path
Thx for the reply


Ensure session.disconnect() properly Drops on all clients

Cases where there could be a memory leak:

Apple client in the reasserting state
Android client in the reasserting state
Windows client after sending packets through the tunnel
Linux client after sending packets through the tunnel

I think this should no longer be an issue now that we have full control of the ICE state machine


Client timeout doesn't work, searches hang forever if remote server goes down

To reproduce:

Create a client, setting the timeout option (eg. 4 seconds):

ldap.createClient({url: 'ldap://directory:389', timeout: 4000, connectTimeout: 4000});

starttls then bind
search -> The search is successful
Shut down the server (slapd), then start it up again
Issue another search -> The callback is never called, the search never succeeds or fails, and the client doesn't emit any 'error' event

Ideally, ldapjs should notice that its TCP connection has gone down (due to the server restarting), and would automatically reconnect when the next query is issued.
But at minimum, it should notice that it hasn't received a response to the search within the 4-second timeout window, and emit an error so that I can reconnect manually.

Concerning the issue of the never resolving promise, I use the workaround of wrapping the res EventEmitter in a bluebird promise:
const resultPromise = new Promise((resolve, reject) => {
  const entries = [];
  res
  .on('searchEntry', ({object: entry }) => {
    entries.push(entry);
  })
  .on('error', err )> {
    reject(err);
  })
  .on('end', ({status}) => {
    if (status !== 0) {
      return reject(new Error(`LDAP error: ${status});
    }
    resolve(entries);
  });
}).timeout(4 * 1000, 'LDAP search timed out');

This solution is not clean as we don't know the state of the TCP connection at this point but it works.
We found out that a concurrency issue (solved with https://github.com/joyent/node-ldapjs/pull/424) cause the EventEmitter to hang forever without emitting any error. The timeout & connectTimeout did not seems to work neither.
Hope it helps.

👋
On February 22, 2023, we released version 3 of this library. As a result, we are closing this issue/pull request.
Please see issue #839 for more information, including how to proceed if you feel this closure is in error.


Add cupyx.scipy.get_array_module

jenkins, test this please.

Jenkins CI test (for commit 87cad88482a2c9aa49ff3f3b329172f5402f0159, target branch master) succeeded!

Thanks. Please add test and fix rst file?

jenkins, test this please.

LGTM!


flow : use xxHash and eBPF fixies

Hi guys,
as promised this commit includes a few changes.
Flow table is now banded - no memory leaks
Hash function was replaced - no collisions
Only one copy of the flow table is kept in ebpf now
This is still the first commit. Still need to report the number of deleted flows so this is on our todo list.


network-interfaces: use altered interface name for setting use_tempaddr

Motivation for this change
Fixes #86764
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested nixos/tests/ipv6.nix
[x] Deployed on a server and checked that the log message which previously appeared no longer appears
[ ] 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.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/740

This also fixed a problem that I had while using links to rename an interface. Thanks!


Fix/kernel 5

Adds extra check for Kernel 5.x support
Adds gitignore for idea

Hi @matteocrippa
thanks for the PR but there are few things we would have to address:

we need a backward compatibility from kernels 4.2 (this is checked by travis)
You can run checks by issuing ./ci/build_against_kernel (see --help for all options)
we want to be as style compliant as possible (also checked by travis)
You can run check by issuing ./ci/run_style_check

When you will  make travis happy we can do a proper review :)
(things will change so it is better to wait with it).
Thanks,
Dawid


Bump STS for additional user management fixes

Fixes for https://github.com/microsoft/azuredatastudio/issues/22426 and https://github.com/microsoft/azuredatastudio/issues/22447.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 41.678%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
30328

Relevant Lines:
67360

💛  - Coveralls


Use sqlite3 database as default for Docker image

The app.ini template file in the Docker image is currently using mysql as default database engine. However, it's not practical as default. Because,

It require more setup to run gitea, such as:

run a mysql instance inside docker, which has to be named as mysql,
prepare a database called gitea,
and the password of the mysql's root user has to be empty.

People, who are going to use mysql as the database, are more likely provide their own app.ini file, to specify the server address, mysql IP/name, reasonable user & password, etc.

So, my suggestion is that replacing the mysql with sqlite3 as default. So, anyone who just want to simply run the gitea image to get an idea, can just run the image without providing a customized app.ini file or preparing a MySQL server.
Signed-off-by: Tao Wang<EMAIL_ADDRESS>

LGTM

This will display by default sqlite3 on /install page if I am not mistaken.

Yes, the default database type is SQLite3 on the install page:

User still need to go through the install process to get a running server though. My another PR https://github.com/go-gitea/gitea/pull/2201  goes one step further, with environment variable, user can run the gitea docker image with some customization abilities, but without necessary go through the install process, and without the necessary given the app.ini file.

LGTM

make L-G-T-M work


Install LFS in docker

I had trouble trying to use this action on a repo which uses Git LFS as this wasn't installed in the Docker image.  The error show was that it couldn't checkout FROM_HASH.  This PR installs Git LFS on the Docker image, solving the problem.

Hi @jamiesandenr, thanks for the PR and sorry for the delay - I am just getting back into things after some time off. This PR is easy! I'll take a look at your other one shortly.


linter-julia dosen't work on win10

Did you follow installation instructions? Namely have you typed Pkg.checkout ("Lint")?

Sorry for the bothering.


ImportError: cannot import name 'TestDataDirectory' from 'robot.api'

Using robotframework-3.2rc1
While running tests from a bash script wrapper following error appears.
from robot.api import TestDataDirectory
ImportError: cannot import name 'TestDataDirectory' from 'robot.api'

Fix: Downgrading to last stable version 3.1.2 fixed it.

The reason is that RF 3.2 has new and totally rewritten test data parser (#3076) and the whole parsing API has changed. I noticed this isn't explicitly mentioned in RF 3.2 rc 1 release notes but I'll write something there soon.
Good news is that the new parsing API is a lot better than the old one. I recommend studying the new API docs and starting to think how/when to migrate.

This is now explicitly mentioned in RF 3.2 rc 1 release notes:
https://github.com/robotframework/robotframework/blob/master/doc/releasenotes/rf-3.2rc1.rst#parsing-apis-have-been-rewritten

Thanks @pekkaklarck . This helps.


[refactor]: Remove debug log in module.utils.ts

Overview
I've noticed that this log is always displayed, which may not be necessary within the library. If users wish to view log information, they can use the verbose option instead
https://github.com/logicspark/berryjam/blob/53a1eb4e70cec12e72b1a0a3d9d8d589d26acba6/src/utils/module.utils.ts#L247
Expected Behavior
Remove the line and the code still work per normal.

@ravut8 Review my pull request


Add tag workflow

Tag workflow def:

Generate changelog
Deploy

/cib

:tada: This issue has been resolved in version 1.1.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


AppTrackingTransparency: The permission always return unavailable, even when NSUserTrackingUsageDescription is added

Bug summary
We have added the key NSUserTrackingUsageDescription in the info.plist and enabled in podfile as well, still when we make a call the request method always result in RESULTS.UNAVAILABLE
Library version
4.0.1
Environment info
System:
  OS: macOS 14.1.2
  CPU: (8) arm64 Apple M1
  Memory: 87.41 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.16.1
    path: ~/.nvm/versions/node/v18.16.1/bin/node
  Yarn:
    version: 1.22.17
    path: /usr/local/bin/yarn
  npm:
    version: 9.5.1
    path: ~/.nvm/versions/node/v18.16.1/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.14.3
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.0
      - iOS 17.0
      - macOS 14.0
      - tvOS 17.0
      - watchOS 10.0
  Android SDK:
    API Levels:
      - "17"
      - "23"
      - "27"
      - "28"
      - "29"
      - "30"
      - "31"
      - "33"
      - "34"
    Build Tools:
      - 29.0.2
      - 30.0.0
      - 30.0.1
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 33.0.0
      - 33.0.1
      - 34.0.0
    System Images:
      - android-26 | Google APIs ARM 64 v8a
      - android-28 | Google ARM64-V8a Play ARM 64 v8a
      - android-29 | Google Play ARM 64 v8a
      - android-30 | Google APIs ARM 64 v8a
      - android-31 | Google APIs ARM 64 v8a
      - android-32 | Google Play ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2023.1 AI-231.9392.1.2311.11076708
  Xcode:
    version: 15.0.1/15A507
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.6
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.1
    wanted: 0.73.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Steps to reproduce
Add the latest version and add the keys in info.plist and run app to ask permission
Reproducible sample code
Code:

requestPermission() {
    request(PERMISSIONS.IOS.APP_TRACKING_TRANSPARENCY).then(result => {
      switch (result) {
        case RESULTS.UNAVAILABLE:
          console.log(
            'Permission',
            'This feature is not available (on this device / in this context)',
          );
          break;
        case RESULTS.DENIED:
          console.log(
            'Permission',
            'The permission has not been requested / is denied but requestable',
          );
          break;
        case RESULTS.LIMITED:
          console.log(
            'Permission',
            'The permission is limited: some actions are possible',
          );
          break;
        case RESULTS.GRANTED:
          console.log('Permission', 'The permission is granted');
          break;
        case RESULTS.BLOCKED:
          console.log(
            'Permission',
            'The permission is denied and not requestable anymore',
          );
          break;
      }
    });
  }

@imanshul You cleared the Xcode cache, just in case? (DerivedData)

yeah removing derived data solved the problem, but the package was installed earlier, and i just enable the permission and did pod install. so do i have to do it everytime I enable or disable any permission?

@imanshul Not if you follow the setup in the README

All of the steps are followed by podfile is:
# Resolve react_native_pods.rb with node to allow for hoisting
# ----- Uncomment below code, if removing the react-naitve-permissions ----
# require Pod::Executable.execute_command('node', ['-p',
#   'require.resolve(
#     "react-native/scripts/react_native_pods.rb",
#     {paths: [process.argv[1]]},
#   )', __dir__]).strip

# ------ Start Used for react-native-permissions --------
def node_require(script)
  # Resolve script with node to allow for hoisting
  require Pod::Executable.execute_command('node', ['-p',
    "require.resolve(
      '#{script}',
      {paths: [process.argv[1]]},
    )", __dir__]).strip
end

node_require('react-native/scripts/react_native_pods.rb')
node_require('react-native-permissions/scripts/setup.rb')
# ------ END Used for react-native-permissions --------

platform :ios, min_ios_version_supported
prepare_react_native_project!

# ------ Start Used for react-native-permissions --------
# ⬇ uncomment wanted permissions
setup_permissions([
   'AppTrackingTransparency',
  # 'Bluetooth',
  # 'Calendars',
  # 'CalendarsWriteOnly',
   'Camera',
  # 'Contacts',
  # 'FaceID',
  # 'LocationAccuracy',
  # 'LocationAlways',
  # 'LocationWhenInUse',
  # 'MediaLibrary',
  # 'Microphone',
  # 'Motion',
   'Notifications',
   'PhotoLibrary',
  # 'PhotoLibraryAddOnly',
  # 'Reminders',
  # 'Siri',
  # 'SpeechRecognition',
  # 'StoreKit',
])

# ------ END Used for react-native-permissions --------

# If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set.
# because `react-native-flipper` depends on (FlipperKit,...) that will be excluded
#
# To fix this you can also exclude `react-native-flipper` using a `react-native.config.js`
# ```js
# module.exports = {
#   dependencies: {
#     ...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
# ```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.disabled

linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
  Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
  use_frameworks! :linkage => linkage.to_sym
end

target 'App13Karat' do
  pod 'WebEngage'
  config = use_native_modules!

  use_frameworks! :linkage => :static
  $RNFirebaseAsStaticFramework = true

  use_react_native!(
    :path => config[:reactNativePath],
    # Enables Flipper.
    #
    # Note that if you have use_frameworks! enabled, Flipper will not work and
    # you should disable the next line.
    :flipper_configuration => flipper_config,
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

  target 'App13KaratTests' do
    inherit! :complete
    # Pods for testing
  end

  # ServiceExtension Target
  target 'NotificationService' do
      platform :ios, min_ios_version_supported
      pod 'WebEngageBannerPush'
  end

  # ContentExtension Target
  target 'NotificationViewController' do
    platform :ios, min_ios_version_supported
    pod 'WebEngageAppEx/ContentExtension'
  end

  post_install do |installer|
    # https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
    react_native_post_install(
      installer,
      config[:reactNativePath],
      :mac_catalyst_enabled => false
    )
    workAroundForSharedApplication(installer)
  end
end

# Fix for MMKV after adding WebEngage, especially NotificationService and NotificationViewController as App Extension
def workAroundForSharedApplication(installer)
    installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings['APPLICATION_EXTENSION_API_ONLY'] = 'No'
        end
    end
end

In this case, it will work after a pod install and a cache clean.


[kube-up][scale-out] system tenant coredns pod cannot be created

What happened:
using poc 1-30 branch, start 1 TP + 1 RP,
$ kubectl get rs coredns-default-<IP_ADDRESS>-d76d87fcd -n kube-system
NAME                                     HASHKEY               DESIRED   CURRENT   READY   AGE
coredns-default-<IP_ADDRESS>-d76d87fcd<PHONE_NUMBER>384191128   1         0         0       29m
$

What you expected to happen:
system tenant's codedns deployment/rs has one pod created as replicas specified
How to reproduce it (as minimally and precisely as possible):
use kube-up.sh to start 1 TP +1 RP (with 1 worker) scale-out env, identify the deployment/rs for the system tenant's coredns, then run the kubectl kubectl get rs -n kube-system <coredns-name>
Anything else we need to know?:
the status of rs has error message:
status:
  conditions:
  - lastTransitionTime: "2022-01-28T16:45:16Z"
    message: 'Pod "coredns-default-<IP_ADDRESS>-d76d87fcd-c5jmq" is invalid: [spec.volumes[1].name:
      Invalid value: "coredns-<IP_ADDRESS>-token-7sqlg": a DNS-1123 label must consist
      of lower case alphanumeric characters or ''-'', and must start and end with
      an alphanumeric character (e.g. ''my-name'',  or ''123-abc'', regex used for
      validation is ''[a-z0-9]([-a-z0-9]*[a-z0-9])?''), spec.containers[0].volumeMounts[1].name:
      Not found: "coredns-<IP_ADDRESS>-token-7sqlg"]'
    reason: FailedCreate
    status: "True"
    type: ReplicaFailure
  observedGeneration: 1
  replicas: 0

Environment:

Arktos version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools: kube-up, {1 tp+1 rp x 1 worker} scale-out
Network plugin and version (if this is a network-related bug):
Others:

This issue can be closed after PR1319 is verified and merged into branch poc-2022-01-30.


Add core option --debug

Stories are now automatically synced to docs:
https://tmt.readthedocs.io/en/latest/stories/core.html#debug


dd2 jace vs chandra japanese

the Japanese product is not accounting for the two Japanese promos, should we redo the deck entirely or should we invent something else? like a syntax to remove a card from a deck and just use the normal card syntax to add it
or should we just add the two promo cards?

It's consistent with how we've handled other decks to add a second [jp promo] version.


the version of pytorch

There are several problems of train-loader from torch.vision using my torch version (1.0.1), so could you show the requirements.txt or a latest code version using torch 1.0.1 ?

Hi, I have updated and tested the code to support PyTorch 1.1.0. Please feel free to check it out!


fix bug in mysql: default value CURRENT_TIMESTAMP #1391

fix mysql  table structure default value 'CURRENT_TIMESTAMP' and 'CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP' will lead to dump sql fail

Codecov Report

Merging #1392 into master will decrease coverage by <.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #1392      +/-   ##
==========================================
- Coverage   57.46%   57.45%   -0.01%
==========================================
  Files          44       44
  Lines        7915     7918       +3
==========================================
+ Hits         4548     4549       +1
- Misses       2804     2805       +1
- Partials      563      564       +1

Impacted Files
Coverage Δ

dialect_mysql.go
58.55% <50%> (-0.23%)
:arrow_down:

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 ce79b1c...77b41f9. Read the comment docs.

Fix import sql file split with ';'  提交修复的是导入sql文件时用';'改为';\n' , 因为部分有些表结构comment注释字段会包含';', 例如:
CREATE TABLE IF NOT EXISTS `tb_tasklinkrule` (`ID` INT(11) PRIMARY KEY AUTO_INCREMENT NOT NULL COMMENT '自增长ID', `TASK_ID` INT(11) NULL COMMENT '任务ID', `LINKRULE_ID` INT(11) NULL COMMENT '规则ID; xxx') ENGINE=InnoDB DEFAULT CHARSET utf8;

注释里包含分号，则会导致sql切成不完整, 导致无法导入sql

I have merged #1437 . Is this still a problem?

no problem


bsearch_custom seems to swap arguments depending on "before" argument.

Tested versions
v4.3.dev.custom_build [9f4499c10]
System information
Godot v4.3.dev (9f4499c10) - Ubuntu 22.04.4 LTS 22.04 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2060 (nvidia; 535.161.07) - Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 Threads)
Issue description
The code is below. This is the output, with the error included.
When before is true, arg1 is the sub-array. When false, arg1 switches to become the float. I'm not sure if this is intended or not, but it feels like a bug.
When before is true
arg1:[2, 2]
arg2:1.1
arg1:[3, 2.5]
arg2:1.1
4

When before is false
arg1:1.1
arg2:[2, 2]

Invalid access to property or key '1' on a base object of type 'float'.

PS - Can anyone explain what before is supposed to do anyway? The docs need an example.
Steps to reproduce
extends Node2D

func _ready() -> void:
	test()

func test():
	# "The custom method receives two arguments (an element from the array and the value searched for)"
	var cmp = func(arg1,arg2): print("arg1:",arg1); print("arg2:", arg2);return arg1[1]>=arg2
	var X:=[ [0, 1.0], [1, 1.5], [2, 2.0], [3, 2.5] ]
	print("When before is true")
	var index = X.bsearch_custom( 1.1, cmp, true )
	print(index)
	print()
	print("When before is false")
	# We get an error:
	#  Invalid access to property or key '1' on a base object of type 'float'.
	# Because the arguments to `cmp` have swapped!
	index = X.bsearch_custom( 1.1, cmp, false )
	print(index)

Minimal reproduction project (MRP)
https://gitlab.com/dbat/array_bsearch_issue

What the argument does is given in the documentation:

Optionally, a before specifier can be passed. If false, the returned index comes after all existing entries of the value in the array.

It's essentially changing between lower/upper bound search, the code is this:
https://github.com/godotengine/godot/blob/aef11a14274f6f9e74ad91ead1d7c07ea1dd7f5f/core/templates/search_array.h#L44-L63


⚠ ClamAV has degraded performance

In 64db0a5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in b645715 after 18 minutes.


[requires.io] dependency update on master branch

Codecov Report

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

@@           Coverage Diff           @@
##           master       #8   +/-   ##
=======================================
  Coverage   23.61%   23.61%
=======================================
  Files           3        3
  Lines          72       72
  Branches       16       16
=======================================
  Hits           17       17
  Misses         54       54
  Partials        1        1

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 ae20461...a29ada0. Read the comment docs.


Update script to accept research_question as an argument and highlight paper titles

Update README and script to accept research_question as an argument and highlight paper titles

First contribution 🥳
Great updates!


placeholder added

placeholder added to input tag

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

This is wrong — you're solving the exercise for the user. The whole solution needs to be in the solution block and the seed text needs to remain.

Hi,
Thanks for this pull request (PR).
Unfortunately, we are closing this PR, because we do not believe it adds a significant improvement.
Feel free to submit another PR though.
Thank you


Mark Linux_android_emu_34 flutter_driver_android_test bringup: true

Mark Linux_android_emu_34 flutter_driver_android_test bringup: true
Related issue: https://github.com/flutter/flutter/issues/156903

Since this is just a CI yaml guy I'm going to merge it manually.


near-shell only allows creating subaccounts

When entering this command:
near create-account alice007.testnet --masterAccount bridge03.testnet

I am getting this error message:
New account doesn't share the same top-level account. Expecting account name to end in ".bridge03.testnet"

There is no reason to have this restriction in near-shell since near-api-js does not have it.

@nearmax aren't we supposed to have this restriction in nearcore though?

@nearmax this is not allowed on the protocol level

I believe this is working as intended. We added this check to help explain to people why they are not allowed to do this action. Getting an error from the RPC is suboptimal so this was added. May I close this, @nearmax or are you still concerend?

I should add, you are also allowed to create a TLA if it's >= 32 characters. I believe there is discussion to increase this size, and we'll increase it at that time. Again, the main reason we have this messaging is to inform users.

Closing as I believe this is addressed


Object detection model to find ROI

Integration of the elements to crop images according to bounding boxes (#218 ).
Changes:

Addition of a new folder for object detection. For now there is only a utils.py file, eventually we could add one or different models (models.py) and maybe the custom parts of the bounding box loader (loader.py).
Function for generation of a json file containing  bounding box coordinates in the following format:

{"path/to/img.nii.gz": [height_max, height_min, width_max, width_min, depth_max, depth_min]}

The bounding boxes are generated this way:

Train UNet model to segment the ROI (e.i. spinal cord).
Predict ROI segmentation
Generate bounding boxes from segmentation

Addition of new transform BoundingBoxCrop
Support to resample bounding boxes and generate dimensions divisible by 16 (requirement for our current version of 3D unet)
Add GPU option on segment_volume. -> To generate the ROI segmentation, the code from segment_volume is reused. Using a GPU accelerates the bounding box generation.

To do:

[ ] Add 2D support
[ ] Add test
[ ] Update all config files
[ ] Refactor of some classes in loader to pass context variable instead of multiple parameters

In future PR:

Integrate object detection unet for 3D images (e.i. Retina Unet)

* Function for generation of a json file containing  bounding box coordinates in the following format:

{"path/to/img.nii.gz": [height_max, height_min, width_max, width_min, depth_max, depth_min]}

Great idea! --> could be further used as metadata in the segmentation Module.
For the implementation / format --> we may want to keep in mind the "multiple object case" as in the future we may want to use this avenue for the MS lesions for instance.

* Function for generation of a json file containing  bounding box coordinates in the following format:

{"path/to/img.nii.gz": [height_max, height_min, width_max, width_min, depth_max, depth_min]}

Great idea! --> could be further used as metadata in the segmentation Module.
For the implementation / format --> we may want to keep in mind the "multiple object case" as in the future we may want to use this avenue for the MS lesions for instance.

Yes good point! How about a list of coordinate list -> could then convert into a numpy array after the loading. What do you think?

Yes good point! How about a list of coordinate list -> could then convert into a numpy array after the loading. What do you think?

Yep great :-)
Do we want to also consider multi-label detection? in that case we would have something like:
{"path/to/img.nii.gz": {
    "label_1": [[height_max, height_min, width_max, width_min, depth_max, depth_min]],
    "label_2: [[height_max, height_min, width_max, width_min, depth_max, depth_min]]
    }
}

Following changes were made:

3D Loader:

Training and testing by patch
Change padding (overlap) to stride (amount of movement) for the patches
Addition of 'coord' parameter in metadata for volume reconstruction

Tranforms:

'crop_params' is now a dictionary where the key is the class name. This is needed in cases where there are 2 types of cropping (ex: Bounding box (Resample) CenterCrop). If there is only one 'crop_params' then the transforms are not undone properly (since they have different crop_params)
Addition of 'preresample_shape' param. When undoing  the transform Resample, the original data shape was used, but this supposes that Resample is the first parameter applied.

segment_volume:

GPU support of segment_volume.py if available. To generate the spinal cord tumor mask I use the function segment_volume.py, but with cpu only the first detection step is very long.

The BoundingBoxCrop is applied after Resample, because the other way around required adding 2 transforms automatically rather than one (BoundingBoxCrop, Resample, CenterCrop).
Glad to discuss/modify these topics :)

This is a significant addition to the repo @andreanne-lemay Many Many thanks!

Before reviewing the PR, I am not exactly sure of what would be the typical succession of the different events, eg detection module, BBox data generation, segment_volume for mask generation, patch extraction, resample, BBoxCrop, CenterCrop...
Could you please provide us an overview of your pipeline? That would really help me. Thanks in advance.

Before reviewing the PR, I am not exactly sure of what would be the typical succession of the different events, eg detection module, BBox data generation, segment_volume for mask generation, patch extraction, resample, BBoxCrop, CenterCrop...
Could you please provide us an overview of your pipeline? That would really help me. Thanks in advance.

Gladly :)

Load images with Bids loader

Load bounding box file (with function load_bounding_boxes) if the path exists or create a json file if the param 'object_detection_path' is not None.
Add 'bounding_box' param in metadata that is unique to every image

Prepare indices (load_filenames)

The preprocessing transforms are applied to seg_pair. If the 'bounding_box' param exists throughout all metadata -> BoundingBoxCrop is automatically added after the Resample transform (if it exists) with function adjust_transforms.  For the 3D loader, since the training is by patch now, I modify the bounding box so that it is at least the size of the patch and so that there are a whole number of strides (avoids mismatch dimension errors during training).

Training as usual
Testing: During testing transformations are undone. Since all images don't have the same bounding box params (different size) the transform is adapted to the specific metadata of the image with function adjust_undo_transforms.

Volume reconstruction in 3D: the transformed whole image is initialize to zero. For every coordinates of a given image, prediction are added to this image and a weight matrix is updated (number of predictions for a given voxel). At the last patch of the image, the image adjusted with the weight matrix.

Note: For 2D training, since it works by slice rather than by patch, a cropping method (CenterCrop) needs to be added to the transforms of the config file. This way, all the cropped images by the bounding box are the same size. We might also want to consider implementing patch wise training in 2D one day.

We might also want to consider implementing patch wise training in 2D one day.

ha! @mariehbourget will definitely be interested in that


DISCOVERY/WIREFRAMES: Build Report: view contextual data on recommendations

As a user of Fabric8, when I view recommendations in the Build Report, I want to be able to dig deeper to view contextual information on each recommendation.
Wireframes can include:

expandable rows in recommendation list
tool tips
help

1st draft idea: https://redhat.invisionapp.com/share/RJAJCSXX4

1st draft wireframes