UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'CLIEngine' of undefined

(node:2850) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'CLIEngine' of undefined
at n.then.e (/Users/raksa/.vscode/extensions/dbaeumer.vscode-eslint-1.9.0/server/out/eslintServer.js:1:47836)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:2850) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2850) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:2850) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'CLIEngine' of undefined
at n.then.e (/Users/raksa/.vscode/extensions/dbaeumer.vscode-eslint-1.9.0/server/out/eslintServer.js:1:47836)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:2850) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)

@raksa do you have any steps how to reproduce this. Do you have a GitHub repository I can clone that demos this?

hi @dbaeumer  you can follow clone and follow the step in README.md
the repo https://github.com/raksa/eslint_error

hope you can catch the bug, thanks

I have same issue with ESLint 6.1.0 and VSCode 1.36.1

bug with<EMAIL_ADDRESS>

@raksa But for me its not worked with 6.1.0 and works with 6.0.0

@raksa Not working with 6.1.0

VSCode Version 1.36.1 (1.36.1)
Eslint Version 6.1.0
VSCode ESLint Extension version 1.9.0
Working for now

I am running with exactly the same versions and still cannot get it to work

@dbaeumer @raksa in my opinion this is not fixed yet, the example code provided by @raksa is still giving me the same error.
For eslint version 6.0.0 and 6.0.1 as well.
Please reopen.

Actually even eslint fails when executed in the terminal.
bugs\eslint\eslint_error [master ≡ +1 ~0 -0 !]> .\node_modules\.bin\eslint .\index.js
internal/modules/cjs/loader.js:583
    throw err;
    ^

Error: Cannot find module 'acorn'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (C:\Users\dirkb\Projects\mseng\VSCode\Playgrounds\bugs\eslint\eslint_error\node_modules\acorn-jsx\index.js:8:15)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)

So I think that this is a problem with ESLint itself, however I agree that the error message should be better in the extension.

Improved ESLint extension to print the additional information to the Output panel. You now get
[Info  - 3:44:52 PM] ESLint server stopped.
Debugger listening on ws://<IP_ADDRESS>:6011/e37ff1de-8ee1-40c9-b187-8f4a3dbcdd77
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
[Info  - 3:45:10 PM] ESLint server running in node v10.11.0
[Info  - 3:45:10 PM] ESLint server is running.
[Error - 3:45:39 PM] Error: Cannot find module 'acorn'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:584:15)
    at Function.Module._load (internal/modules/cjs/loader.js:510:25)
    at Module.require (internal/modules/cjs/loader.js:640:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (c:\Users\dirkb\Projects\mseng\VSCode\Playgrounds\bugs\eslint\eslint_error\node_modules\acorn-jsx\index.js:8:15)
    at Object.<anonymous> (c:\Users\dirkb\Projects\mseng\VSCode\Playgrounds\bugs\eslint\eslint_error\node_modules\acorn-jsx\index.js:443:3)
    at Module._compile (internal/modules/cjs/loader.js:693:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:704:10)
    at Module.load (internal/modules/cjs/loader.js:602:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:541:12)
[Error - 3:45:39 PM] Failed to load eslint library from c:\Users\dirkb\Projects\mseng\VSCode\Playgrounds\bugs\eslint\eslint_error\node_modules\eslint\lib\api.js. See output panel for more information.

@raksa I will close the issue again. If you want to see the issue reopened, please explain why.

okay when I see the problem reopen and report again, thanks

This is fixed internally in the code base, but it requires a new ESLint version. But as always issues get closed when fixed in the code base.

And please remember this in your example this is a setup issue of eslint and not a problem with the extension itself.


Heroku demo doesn't load

Loading over ssl gives and error, and over regular http gives no content. The dyno is probably down.
 ➜ curl https://pjax.heroku.com
curl: (60) SSL certificate problem: Invalid certificate chain
More details here: https://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.
 ➜ curl http://pjax.heroku.com

The link is wrong, it should be  https://pjax.herokuapp.com

Fixed. Thank you!


[WIP] test: testing against func templates

Signed-off-by: Matej Vasek<EMAIL_ADDRESS>

/cc @lkingland @lance

I love seeing this! So much better than my hackey shell scripts

also I am planning to write build script in Go to simplify Makefile, I find the makefile even messier than shell.

@lance right now the action takes too long (one hour) we could cut it to half by running only snapshot func (build from main).
Another speed up might be done just by building one template, but I don't like the idea, we might miss bug that is preset for example in http and not in events.

and I suspect that half of the time is spend on rust alone :laughing:

and I suspect that half of the time is spend on rust alone

You're welcome! :stuck_out_tongue_winking_eye:

Should I make this fast fail? Right now all builds are run even if one of them failed.

Can be GH action speed up by running multiple gorutines?

Should I make this fast fail? Right now all builds are run even if one of them failed.

Given that it takes a long time, I'd say yes, this should fail fast.

and I suspect that half of the time is spend on rust alone

And quarkus native!

@lance right now the action takes too long (one hour) we could cut it to half by running only snapshot func (build from main).

Hmm - that's a tough one. I think both are important. What if we run snapshot on pull requests to ensure that current / ongoing work is compatible, and run stable when a commit lands on main to ensure compatibility with existing release?

Another speed up might be done just by building one template, but I don't like the idea, we might miss bug that is preset for example in http and not in events.

Agree - I don't think this is worth the risk.

Hmm - that's a tough one. I think both are important. What if we run snapshot on pull requests to ensure that current / ongoing work is compatible, and run stable when a commit lands on main to ensure compatibility with existing release?

@lance  I think we just need to known if ongoing work is compatible.
Stable version of func should have fixed tag (since v.0.16.1)

@lance would it be possible to make "snapshot" builds from main in func so I don't have to build it in CI here?

Can be GH action speed up by running multiple gorutines?

I think this won't work, java native image will probably cause OOM

@lance PTAL

@lance @zroubalik I did some minor changes PTAL


Template #1 ("old template") issue - text is occasionally cut off

Description
It does not appear to be a very common issue, but occasionally the question text on the left side of the document can be cut off.
Screenshots

Before

After

Attachments
before-and-after.zip

@tulvit Just adding some of your comments here for later reference:

issue#17 - it's because of a long strings (your_name_check, etc.) - should be solved automatically right after other issue (these strings -> human readability format) will be closed.


F superfluid validate transactions (WIP, not ready for review)

Almost ready for review
Related: https://github.com/Giveth/impact-graph/pull/1352

@MohammadPCh Preparing a branch to generate real data.


added biscuit test data

This contains the test data for multiqc to work with BISCUIT. The data is obtained by running BISCUIT with QC.sh on GEO (GSM1370557, GSM1370558 and GSM1370559).

Hi @zwdzwd,
Why did you close this PR again?
Phil

If you're still planning to open a PR on the main MultiQC repo for this new module at some point, then it's good to merge this first. I have no problem doing this before the code is ready. In fact, it helps as the automated tests will run correctly when you do come to opening the main code PR.


Yaml config additions

#2589 accidentally closed, included it here.
added support for playwright_stealth
added support for libusb_package, fixes #2598

nuitka/plugins/standard/standard.nuitka-package.config.yml
  Warning: 2930:13 [comments] too few spaces before comment
  Warning: 2932:6 [comments] missing starting space in comment

So these warnings are not treated as errors, that is of course terrible, I didn't notice that yet. GitHub displays them when viewing the diffs. I will try and make a change for develop that turns them into proper errors.

Playwright downloads Chromium, WebKit and Firefox browsers into the OS-specific cache folders:
%USERPROFILE%\AppData\Local\ms-playwright on Windows
~/Library/Caches/ms-playwright on MacOS
~/.cache/ms-playwright on Linux

this can be overriden via the PLAYWRIGHT_BROWSERS_PATH env variable
an solution to this would be for nuitka to first check the PLAYWRIGHT_BROWSERS_PATH env, if it's set to 0 (background can be found here: https://github.com/Nuitka/Nuitka/pull/2589#issue-2020704147) , then we can look inside driver/package/.local-browsers/, if it's other than 0, then whatever path it's provided to the env variable, else look into the paths i've referenced above.


OpenAPI spec wrong URL

I was using Traefik with these match rules.
Host(`domain.com`) && PathPrefix (`/api`)

This will route all domain.com with the prefix /api to the desired service which is our backend running Elysia with swagger. With #16 it was fixed to use the prefix from Elysia configuration, but on the latest version the Swagger option url is in the wrong url. (Does not respect prefix at all).

While #162 fixes externally set prefixes from Traefik for example, it does not respect Elysia prefix as stated in
https://github.com/elysiajs/elysia-swagger/pull/162#issuecomment-2423836154


Latest master will not build (MSBUILD project)

I just cloned and tried to build T10 for the first time... The MSBUILD project fails..
Severity	Code	Description	Project	File	Line	Suppression State
Error		Could not copy "C:\code\git\Template10\Template10 (Installer)\Template10.MSBUILD\bin\Debug\Template10.MSBUILD.dll" to "C:\code\git\Template10\Lib\Template10.MSBUILD.dll". Exceeded retry count of 10. Failed.	Template10.MSBUILD	C:\code\git\Template10\Template10 (Installer)\Template10.MSBUILD\Template10.MSBUILD.csproj	77

...and...
Severity	Code	Description	Project	File	Line	Suppression State
Error		Unable to copy file "C:\code\git\Template10\Template10 (Installer)\Template10.MSBUILD\bin\Debug\Template10.MSBUILD.dll" to "C:\code\git\Template10\Lib\Template10.MSBUILD.dll". The process cannot access the file 'C:\code\git\Template10\Lib\Template10.MSBUILD.dll' because it is being used by another process.	Template10.MSBUILD	C:\code\git\Template10\Template10 (Installer)\Template10.MSBUILD\Template10.MSBUILD.csproj	77

I saw this issue, but there was no real resolution I could see.. https://github.com/Windows-XAML/Template10/issues/693
What's the magic trick?

Delete that file. You may need to close vs.


Fix kafka broker config defaults

Description
Fixing broker default configs as per the Kafka prod cluster recommendations and best practices.

Testing
Please describe the tests that you ran to verify your changes. Please summarize what did you test and what needs to be tested e.g. deployed and tested helm chart locally.
Checklist:

[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Any dependent changes have been merged and published in downstream modules

Documentation
Make sure that you have documented corresponding changes in this repository or hypertrace docs repo if required.

Worth to check with @jbahire as in local autocreation of topics might be
handy (hence could be configurable) but I am not sure if we use this
feature.
On Sun, 20 Dec 2020, 08:34 Laxman Ch<EMAIL_ADDRESS>wrote:

Description
Please include a summary of the change, motivation and context.
Testing
Please describe the tests that you ran to verify your changes. Please
summarize what did you test and what needs to be tested e.g. deployed and
tested helm chart locally.
Checklist:

My changes generate no new warnings
I have added tests that prove my fix is effective or that my feature
works
Any dependent changes have been merged and published in downstream
modules

Documentation
Make sure that you have documented corresponding changes in this
repository or hypertrace docs repo
https://github.com/hypertrace/hypertrace-docs-website if required.
You can view, comment on, or merge this pull request online at:
https://github.com/hypertrace/kafka/pull/24
Commit Summary

Fix kafka broker config defaults

File Changes

M helm/values.yaml
https://github.com/hypertrace/kafka/pull/24/files#diff-81801117ec01136c8a49bfcd42af8e104f4efad1f2daccda9da9d960eaad5279
(9)

Patch Links:

https://github.com/hypertrace/kafka/pull/24.patch
https://github.com/hypertrace/kafka/pull/24.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hypertrace/kafka/pull/24, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYASV6CNHELYNJ7K47J3SVWSG5ANCNFSM4VC4NWJA
.

@jcchavezs : We use kafka streams. Kafka streams doesn't allow to auto create the topics.
https://kafka.apache.org/26/documentation/streams/developer-guide/config-streams.html#id26

If you try to change allow.auto.create.topics, your value is ignored and setting it has no effect in a Kafka Streams application.


Implement hover for literals

Currently, hovering is only supported for TerminalIdentifier, while there are multiple Expressions that are not supported there:

Literal
ShortString
String
False
True

(possibly more?)
After hovering, we want to display the type info in the appropriate form (new hover style)

For short strings/strings we might also want to show their numeric value (basically bring https://www.stark-utils.xyz/converter into LS)


[SMALLFIX] Added test for FileWorkerMasterSyncExecutor

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7857/
Test PASSed.

left two comments. thanks for improving the test coverage.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7896/
Test PASSed.

The PR looks good to me. I left one comment on the javadoc part

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8001/
Test PASSed.

@apc999 doc added, PTAL

+1 LGTM


Fixes overflow below 1024px

This is what happens in Google Chrome on Windows, when resizing the website below 1024px.

This change fixes this behaviour ^_^

Thanks! First I need to test in local to be sure that doesn't break other os browsers :-)

Sure! Test it as much as you like, I still have to see if it does the same
thing on my Mac 😁
BTW, I'm also working in a parallel branch with the zoom.js integration 😉
El El jue, 18 jun 2015 a las 17:42, Kiko Beats<EMAIL_ADDRESS>escribió:

Thanks! First I need to test in local to be sure that doesn't break other
os browsers :-)
—
Reply to this email directly or view it on GitHub
https://github.com/Kikobeats/uno-zen/pull/28#issuecomment-113196771.

Checked for Chrome in Mac, Chrome and Internet Explorer on Windows, it happens the same :worried:

@kutyel so is ready to be merge?

Aye aye 😊


Support records experimental feature

I forget how we enable experiments in dartpad, but we should soon-isssh start supporting the 'records' experiment. The command-line flag should be something like --enable-experiment=records.
We should not start now; things are too early. I think static support is largely complete, but the web support is not there yet, for when the user clicks "Run."
Additionally, there is likely a big change to the syntax coming. https://github.com/dart-lang/language/issues/2469.
Just putting this on the radar. Maybe we can enable this in a few weeks on one channel or another.

I'd guess the master channel will be the best place to do it, as that'll have the most up to date version of Dart

I would really like to test the records feature in DartPad. Is there a way for me to enable it manually in the master channel or do I have to wait for it to be enabled by default?

No, it is not implemented yet. It will be some months.

Records is now supported in stable. Closing.


[eloquent backport] Check allocation of requester and replier (#60)

Signed-off-by: Stephen Brawner<EMAIL_ADDRESS>

Linux
Linux-aarch64
macOS
Windows

Linux is marked unstable due to a flake8 incompatibility
https://ci.ros2.org/job/ci_linux/12108/testReport/
Windows is marked unstable due to unrelated errors in rcl
https://ci.ros2.org/job/ci_windows/12017/testReport/


Spaces (or other characters) in parameter names results in TypeScript Syntax Error

What are the steps to reproduce this issue?
Have a schema with a parameter type like this, with a space in the name:
{ "paths": { "/foo": { "get": {
  "parameters": [
      {
        "name": "My weird parameter name",
        "in": "query",
        "schema": { "type": "array", "items": {"type": "object'} }
      }
  ]
} } } }

What happens?
export type GetFooParams = { My weird parameter name?: GetFooMyWeirdParameterNameItem[] };

What were you expecting to happen?
The object key needs to be quoted:
export type GetFooParams = { 'My weird parameter name'?: GetFooMyWeirdParameterNameItem[] };

Any logs, error output, etc?
n/a
Any other comments?
I acknowledge this should be rare for a parameter name, but the general case is that any character that can't be printed as an object key should be quoted (such as a dash).
One fairly simple way to accomplish this would be to quote all object keys everywhere, and run prettier over orval's output (which would remove unnecessary quotes, as well as generally being nicer).
What versions are you using?
Operating System: …
Package Version: …
Browser Version: …

Fixed with 5.5.7


Fixed wrong command in Example 1

Exmaple 1 used the command to remove a Device registered Owner instead of a User.

Docs Build status updates of commit 83999cf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureadps-2.0/AzureAD/Remove-AzureADDeviceRegisteredUser.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Hi @LeonB87
Per the read me file:
Please be aware that if you have any updates to automatically generated reference content, you should create an issue and not a PR.  The issue will then be created into a bug and triaged accordingly.  We do this because the reference content must mirror the *dll-help.xml file and subsequent updates to the reference content may overwrite any changes made through the repo.  Capturing it in the source code ensures that this does not occur.  Any PR with changes to automatically generated reference content will be closed.
Automatically generated reference content is any of the content under this Reference node, such as Get-AzureADUser
This only applies to reference content and not conceptual content.  Pull requests for changes to conceptual content are accepted and encouraged.  An example of the conceptual content is the Overview or a scenario such as importing data.
Thank you!
Bill


emoji: Fix mis-alignment of realm emoji div with other div in emoji picker.

Replaces PR #5250.
Thanks to @tejaskasetty for reporting this issue.
Fixes: #5229.

@brockwhittaker can your review this one?

@HarshitOnGitHub I think this doesn't quite work for me in terms of alignment in Chrome on Linux:

@HarshitOnGitHub if you get a chance, it'd be great to finish this up.  If you need help, ping @brockwhittaker.

Heads up @HarshitOnGitHub, we just merged some commits that conflict with the changes your made in this pull request! You can review this repository's recent commits to see where the conflicts occur. Please rebase your feature branch against the upstream/master branch and resolve your pull request's merge conflicts accordingly.

The alignment is now wrong in the compose typeahead:

OK, after some fiddling, I figured out that this seems to work: 923fb7be167172b92aba729f79b9e27d6263b9b5
@HarshitOnGitHub @lonerz can you try testing that carefully to see if now the emoji are always rendered at the correct vertical offset, whether in typehead/reaction picker/emoji picker/etc?  Thanks!
Thanks for your help with this!

@timabbott We would definitely not want to keep two different offsets since that would cause more emoji positioning issues in future, like for e.g. I was expecting merging of this PR will fix the realm emoji positioning issues but it is not the case with the merged version. I think the correct fix here would be this: 5667fd2e11ab67e231a47940d2dfb94524a7834c.

Did you test 5667fd2 in various places where we render emoji?  While I definitely don't want to have the different offsets, I care more about having it work in each of them.  If that CSS does work in all of them, I'd be happy to merge it.

Yep I have tested it on:

Messages
Emoji picker
Reactions picker
Composebox typeahead
Stream descriptions
Composebox preview mode

Just noticed that on latest master emojis are not rendered properly in stream descriptions:

Re: 5667fd2, OK, if you open a PR that's good.  Though now I'm wondering: is that CSS going to be incompatible with your work in #3923?
Re: streams, nice find!  I bet that's just the stream description container not having the right overflow behavior.  Open an issue for that?

is that CSS going to be incompatible with your work in #3923?
I am not 100% confident but AFAICS I am pretty sure that it will not. Opened PR #6323.


Resolve nancy CVE CVE-2023-39325

Fix required for fixing internal nancy issues,
<EMAIL_ADDRESS>1 known vulnerabilities affecting installed version
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ [CVE-2023-39325] CWE-400: Uncontrolled Resource Consumption ('Resource Exhaustion')                                                                                ┃
┣━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃ Description        ┃ A malicious HTTP/2 client which rapidly creates requests and immediately                                                                                ┃
┃                    ┃ resets them can cause excessive server resource consumption. While the                                                                                ┃
┃                    ┃ total number of requests is bounded by the                                                                                ┃
┃                    ┃ http2.Server.MaxConcurrentStreams setting, resetting an in-progress request                                                                                ┃
┃                    ┃ allows the attacker to create a new request while the existing one is still                                                                                ┃
┃                    ┃ executing. With the fix applied, HTTP/2 servers now bound the number of                                                                                ┃
┃                    ┃ simultaneously executing handler goroutines to the stream concurrency limit                                                                                ┃
┃                    ┃ (MaxConcurrentStreams). New requests arriving when at the limit (which can                                                                                ┃
┃                    ┃ only happen after the client has reset an existing, in-flight request) will                                                                                ┃
┃                    ┃ be queued until a handler exits. If the request queue grows too large, the                                                                                ┃
┃                    ┃ server will terminate the connection. This issue is also fixed in                                                                                ┃
┃                    ┃ golang.org/x/net/http2 for users manually configuring HTTP/2. The default                                                                                ┃
┃                    ┃ stream concurrency limit is 250 streams (requests) per HTTP/2 connection.                                                                                ┃
┃                    ┃ This value may be adjusted using the golang.org/x/net/http2 package; see                                                                                ┃
┃                    ┃ the Server.MaxConcurrentStreams setting and the ConfigureServer function.                                                                                ┃
┣━━━━━━━━━━━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃ OSS Index ID       ┃ CVE-2023-39325                                                                                ┃
┣━━━━━━━━━━━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃ CVSS Score         ┃ 7.5/10 (High)                                                                                ┃
┣━━━━━━━━━━━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃ CVSS Vector        ┃ CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H                                                                                ┃
┣━━━━━━━━━━━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃ Link for more info ┃ https://ossindex.sonatype.org/vulnerability/CVE-2023-39325?component-type=golang&component-name=golang.org%2Fx%2Fnet&utm_source=nancy-client&utm_medium=integration&utm_content=1.0.37 ┃
┗━━━━━━━━━━━━━━━━━━━━┻━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

:thumbsup: Coverage increased from [%] to [80.9286%]


Succeed to select and upload one folder when using the action 'Upload Files...' on Linux

Storage Explorer Version: 1.35.0-dev (100)
Build Number: 20240810.1
Branch: rel/1.35.0
Platform/OS: Linux Ubuntu 22.04
Architecture: x64
How Found: From running test cases
Regression From: Previous release (1.34.0)
Steps to Reproduce

Expand one storage account -> Blob Containers.
Create a blob container -> Click 'Upload -> Upload Files...'.
Click the 'Selected files' field -> Select one folder.
Click 'Open'.
Check whether the folder is opened in local file explorer.

Expected Experience
The folder is opened in local file explorer.
Actual Experience
The folder is selected on the upload dialog.
Additional Context

This issue doesn't reproduce on Windows11/Windows 10/MacOS Sonoma 14.6(Apple M1 Pro).
Here is the record:

I am attempting to reproduce on my Linux machine. It's been some time since I've been able to seriously develop on Linux, so I'm ironing out some system/build issues first.

I'm experiencing a slight difference. When I click Open after selecting a folder, the system dialog closes, but nothing is actually selected in the "Selected files" field. Furthermore, if I double-click the folder, the dialog navigates into the folder as expected.
I'm going to chalk this up to OS weirdness. We are passing the correct values to the native OS dialog, so it's up to the system to handle it from there. We don't have any control over it.


Issue 153 - bower-friendly version number

bower requires a semver-compatible version number, e.g. x,y.z.  Currently, the version 19.0 that's there is causing Issue #153.  This is a simple change to allow bower to more reliably fetch and cache jssor.

I make this change, please check it out.


[Documentation] Formatting fix s3

Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

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

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

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

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

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

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

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

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

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

LGTM


Support Persistent Identifiers in DOI Registrations

Is your feature request related to a problem? Please describe.
As a user, when registering a DOI for a model or dataset, it would be great to have the ability to be able to use the persistent identifiers supported in the DataCite schema when making the DOI registration.
Describe the solution you'd like
Add the option to identify individuals with ORCID IDs or institutional creators and contributors with ROR IDs, as described here:
https://datacite-metadata-schema.readthedocs.io/en/4.5/properties/creator/
https://datacite-metadata-schema.readthedocs.io/en/4.5/properties/contributor/
ROR IDs can also be used to identify publishers and funders:
https://datacite-metadata-schema.readthedocs.io/en/4.5/properties/publisher/
https://datacite-metadata-schema.readthedocs.io/en/4.5/properties/fundingreference/
Additional context
Other repository services provide this functionality (e.g. Zenodo) and in some cases, use of these values is mandated by institutional or funder policies.
Full disclosure: I work at Crossref on ROR, but am also a long time, happy Hugging Face user.

cc'ing @Kakulukian and @cakiki for visibility, and also cross-linking to #453 and #25

This would be extremely helpful. We have chosen Hugging Face for publishing our data and models partly because we can generate DOIs for them, but the auto-generated citation never matches what we put in the README. This is concerning particularly when working with external collaborators, but is also just not helpful for proper citation in papers and such.

I second this. The feature is crucial because some publishers require that DataCite metadata of in-review papers is properly filled-in.


Upgrade Flutter and packages; hold back firebase_core; record Flutter commit IDs

Fixes #1118.
Fixes #1119.
This upgrades Flutter and some of our other dependencies.
OTOH firebase_core and the other Firebase packages can't immediately be upgraded; I ran into #1116, which I just filed. So hold those back.
And at the start of the branch, I augment tools/upgrade a bit so that it records the actual commit ID in the Flutter tree in a comment in pubspec.yaml, and give tools/check a tiny new suite flutter_version that validates that information.
On several occasions I've wanted the ability to look back and see what Flutter commit was used in a given published (beta) release, in particular. I already make a practice of doing so with the exact minimum version recorded in pubspec.yaml, in order to make it reproducible; but it's somewhat annoying to identify that commit from the version number that normally appears there. So this solves that problem. (… OK, and filed #1118 to describe that.)
Selected commit messages
f5395d990 tools/upgrade: Record commit ID of Flutter into pubspec.yaml
Fixes #1118, or anyway the main part of it.
Upcoming commits will add a suite in tools/check that validates
this information, in case this line gets updated manually rather
than using this script.
a940b8a0e check: Add suite flutter_version
72e01d146 check: In flutter_version, verify version bound matches commit
a29b6143a notif: Add vm:entry-point pragma on class, too
Fixes #1119.
[…]
479c51808 deps: Upgrade Flutter to 3.27.0-1.0.pre.744
b1e77284e deps: Upgrade packages within constraints (tools/upgrade pub)
This required a manual fixup step to update generated files
for the Drift upgrade:
$ tools/check --fix --all-files build_runner drift

CI failed initially but should be fixed now. The fix was adding this commit:
9618f40aa check: Fix branch name for clone of Flutter repo in CI

Oh I did notice an auto-generated change:
diff --git ios/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme ios/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme
index 5e31d3d34..c53e2b314 100644
--- ios/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme
+++ ios/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme
@@ -48,6 +48,7 @@
       ignoresPersistentStateOnLaunch = "NO"
       debugDocumentVersioning = "YES"
       debugServiceExtension = "internal"
+      enableGPUValidationMode = "1"
       allowLocationSimulation = "YES">
       <BuildableProductRunnable
          runnableDebuggingMode = "0">

Hmm, seeing some iOS build issues actually—please hold off merging while I investigate. Here is the output:
Launching lib/main.dart on iPhone 15 Pro in debug mode...
Running pod install...
Running Xcode build...
Xcode build done.                                           30.5s
Failed to build iOS app
Semantic Issue (Xcode): Duplicate interface definition for class 'Sqlite3FlutterLibsPlugin'
/Users/chrisbobbe/dev/zulip-flutter/build/ios/Debug-iphonesimulator/sqlite3_flutter_libs/sqlite3_flutter_libs.framework/Headers/Sqlite3FlutterLibsPlugin.h:2:0

Modules Issue (Xcode): Definition of 'Sqlite3FlutterLibsPlugin' must be imported from module 'sqlite3_flutter_libs.Swift' before it is required
/Users/chrisbobbe/dev/zulip-flutter/ios/Runner/GeneratedPluginRegistrant.m:105:3

Could not build the application for the simulator.
Error launching application on iPhone 15 Pro.

Hmm, the build succeeded just now when I requested it from the Xcode gui. The output above is from flutter run as triggered from the "Run 'main.dart'" button (with a green "play" icon) in Android Studio.

The output above is from flutter run as triggered from the "Run 'main.dart'" button (with a green "play" icon) in Android Studio.

OK, and it succeeds for me now after running flutter clean. 🤷♂ Please merge at will, then.

Thanks for the review! Evidently I had not tried flutter run for iOS. << >>
I reproduce that build failure, and also reproduce that flutter clean resolves it — good find.
Before flutter clean, I tried flutter build ipa, prompted by thinking of #773. That actually succeeded. More data points FTR though I'm not sure they'll be useful:

flutter run --release succeeded too
but OTOH flutter build ipa --debug still succeeded, so wouldn't have been a way to detect the issue.

Merging, after adding this:

Oh I did notice an auto-generated change from flutter run:

There was also a similar change in macos/ after flutter run for that. I'd noticed that change yesterday — I was experimenting with the macOS target to try to resolve #1116 and unblock upgrading Firebase — but had assumed it was an existing discrepancy that we just hadn't noticed because we don't use that target as often.


Vickel: Watch aaroncrosby.co.nz

Vickel requests the watch of the watch_keyword aaroncrosby\.co\.nz. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

aaroncrosby\.co\.nz has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Filter fields in form's "excludeFromCopy" from prepopulated/accepted document when requesting named places

Currently named places` prepopulatedDocument is returned as it is, the whole document. This is a security problem, allowing users to see documents they otherwise wouldn't be able to see.
This is to be fixed by filtering the prepopulatedDocument with the associated form's excludeFromCopy. It's a list of JSON paths for fields that should not be used in the document form when using the named place's prepopulatedDocument. This is currently done in front-end (https://github.com/luomus/laji/blob/b17d0d51afa6ba154aadf78b506302dd1c1b6ad3/projects/laji/src/app/%2Bproject-form/form/document-form/document-form.facade.ts#L443-L450)

I'll close this as wontfix after all, because:

The units are already filtered by default from the prepopulatedDocument. If units are to be included, it has to be deliberately enabled with MHL.includeUnits option for the form. So security wise the situation isn't as bad as we though first.
If the full document isn't in prepopulatedDocument, then if a user first fetches a named place and then saves it, the original prepopulatedDocument would be lost because it was saved with the filtered version.

FYI @esko-piirainen

@olzraiti FYI there is a little arrow next to close issue button where you can select "close as not planned"


Hooks not working when loaded from an external vitest.setup.js file

Describe the bug
Hooks (i.e. beforeEach and friends) do not work as expected when loaded from an 'external' setup file.
The hooks run for the first test file but not the following. For example, when your setup file has this:
import { beforeEach } from "vitest";

console.log('setup loading...');
beforeEach((a) => {
  console.log(`Detected: ${a.meta.file.name}`);
});

Then you only see "Detected: src/math.spec.js" for the first test; it proceeds to the following test files without executing this beforeEach again.
I'm not entirely sure what "external" means here, but whenever a setup file is loaded from an 'externalize' location from vite-node, the problem occurs:
https://github.com/vitest-dev/vitest/blob/6433224c0a05d29968eead273d1c57c680034566/packages/vite-node/src/client.ts#L278-285
I can reproduce it by putting the vitest.setup.js file inside a sibling directory. Please take a look at the reproduction instructions below.
Reproduction
external-setup.zip

Unzip this file unzip external-setup.zip -d external-setup.
cd external-setup
npm install
cd project
npx vitest run.

You see this output:
 RUN  v0.31.1 /home/nicojs/github/tmp/project

stdout | unknown test
setup external...

stdout | src/math.spec.js > add > should add 40, 2 = 42
From external: src/math.spec.js

 ✓ src/math.spec.js (1)
 ✓ src/min.spec.js (1)

 Test Files  2 passed (2)
      Tests  2 passed (2)
   Start at  23:56:41
   Duration  205ms (transform 21ms, setup 6ms, collect 13ms, tests 2ms, environment 0ms, prepare 55ms)

As you can see, the beforeEach hook is only executed for math.spec.js, not min.spec.js.
System Info
System:
    OS: Linux 5.15 Ubuntu 20.04.5 LTS (Focal Fossa)
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz
    Memory: 13.05 GB / 15.49 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.12.1/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Chrome: 110.0.5481.77

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

It's not a bug. Externalized dependencies are imported by Node.js and cached by Node.js.
When second test starts, Vitest imports setup files but since it's already evaluated, Node doesn't run it.
There is no way to clear ESM cache in Node.js.
This can only happen when tests are running in a single context where cache is shared between tests.

Thanks for your reaction again @sheremet-va ❤

Without looking at the reproduction yet, it doesn't sound like it's a bug.

The fact that the file is only loaded once shouldn't mean that beforeEach and friends aren't executed for subsequent files, right? That's a strange side effect.

You can bypass it by specifying setup file in deps.inline.

Interesting... this does seem to work, but only when I put it as a regex:
export default defineConfig({
  test: {
    // ...
    deps: { inline: [/vitest.setup.js/] }
  },
})

The full file path or relative file path doesn't seem to work: '/home/nicojs/github/tmp/dist/vitest.setup.js' or 'vitest.setup.js'. Any idea why?

The fact that the file is only loaded once shouldn't mean that beforeEach and friends aren't executed for subsequent files, right? That's a strange side effect.

All hooks are removed between each test file.

The full file path or relative file path doesn't seem to work: '/home/nicojs/github/tmp/dist/vitest.setup.js' or 'vitest.setup.js'. Any idea why?

The string is the dependency name. Regexp is checked against the full file path.

All hooks are removed between each test file.

So you disagree that this is a bug?

The string is the dependency name. Regexp is checked against the full file path.

What would the dependency name be for this file?
I just yesterday realized that the afterAll hook is executed per file. It makes sense after reading to your answers here. Is there a way to detect that it is the last afterAll? Like afterAllInContext or something?

Like afterAllInContext or something?

No, there is no way to do that when you run tests in a single thread. The fact that you run all test files in the same global context is some kind of workaround and there is no abstraction for it. The highest abstraction we operate upon is the test file. You can also use globalSetup which runs before every test, and its teardown runs when all tests are completed, but it is running in a different global context.

What would the dependency name be for this file?

I don't know 🤷🏻 When a string is received, deps.internal basically checks /node_modules/${string}.

I don't know 🤷🏻 When a string is received, deps.internal basically checks /node_modules/${string}.

Right. This workaround works for us: we're using new RegExp(escapeRegExp(vitestSetup)). I will also add this to the e2e test I've discussed at https://github.com/vitest-dev/vitest/discussions/3017#discussioncomment-5901751
I personally think that "external" vs. not-external is not something users should be aware of when configuring a setup file. So I would like to keep this issue open. If you disagree, feel free to close.

I think we should always internalize the setup file.


Suggestion: Add option to alter webhook name and avatar used.

It would be quite awesome if this action could receive options to alter the name and avatar of the webhook.

I will look into this. On my projects I just change the avatar and name using the webhook settings.
Are you looking for something dynamic?

Not really, but I think many people would appreciate having such an option.

Should be possible in >=v1.5.  For example, you can customize the embed.author.icon_url
https://github.com/Sniddl/discord-commits/blob/v1.6/discord-commits/templates/avatar-with-link.mjs


TypedData.buffer and identical

Consider following code:
import 'dart:typed_data';
void main() {
  final buf = Uint8List(0);
  print(identical(buf.buffer,buf.buffer)); // supposed to be true
}

Running it in browser (dartpad) it works as expected (returns true).
However running it in VM (windows), it returns false.
My usage case is following: I was trying to use ByteBuffer with Expando for some data management, which failed because same buffer that references same memory is suddenly not identical and Expando fails.

It's working as implemented. The VM doesn't promise that the buffer is a unique object, just that it gives access to the same memory. (Maybe it should, but it doesn't.)
The VM's implementation of typed data actually allocates the Uint8List directly, with no separate buffer.
It then creates a buffer object when you read the .buffer, which is just a wrapper around the Uint8List.
If you use that buffer to create a new typed data view, it's actually storing into the memory of the original Uint8List.

Thanks for the answer!
The fact that buffer references the same memory, that's the property I was looking to exploit actually (the reason to use Expando, was to tie memory back to allocator as long as it wasn't GC'd)
I would be nice to have buffer object somehow be the same instance every time because you can't store hashcode (int doesn't work with Expando).
The one way I think is to cache TypedData.buffer getter result, or make it a final field that will be populated from the start, I presume that .buffer is called internally as well and often enough, so one object won't make much of memory overhead.

The VM's ByteBuffer implementation does have a compatible == and hashCode, so you can always check if it's the same underlying bytes again by doing ==. That doesn't allow you to use Expando, though, unless you do your own canonicalization, which will probably mean keeping something alive anyway (or using a Finalizer, but that sounds overly complicated and error prone for something like this).
It's probably possible for the VM to cache the buffer object. (Heck, it could use an expando on the underlying TypedData object). It's probably not completely trivial if it changes the layout of typed-data objects, which are heavily specialized and optimized by the VM (but if they all get a field, maybe it'll still work out to having a uniform access mechanism for all the subtypes).

I think field approach will add additional capability: Using Finalizer on such field would make it possible to track that buffer is no longer used by any view, not only one it was created for.

I'm not sure such a finalizer is needed for anything.
If the typed-data object uses as backing store has a reference to the buffer, set the first time the buffer is accessed, it'll just keep that buffer alive as long the typed-data or the buffer is still used by anyone else.
There should be no GC-related difference between having a field on the type-data to store its buffer, anf having an expando which stores it.

Although I can see the intention here, it's not that simple. An interesting corner case is that we sometimes intentionally return a buffer that has to be different:
final mutable = Uint8List(10);
final immutable = UnmodifiableUint8ListView(mutable);
if (identical(mutable.buffer, immutable.buffer)) throw 'should have mutable & immutable buffers';

As can be seen here we have a mutable buffer and then we make immutable view on top. Asking for the buffer of the immutable view will return an immutable buffer (definitely a different object than a mutable buffer). We do that to prevent an owner of an immutable view to gain write access.

Sorry I wasn't made myself clear.
I meant the other way around, something like that:
ByteBuffer fn() {
  Uint8List list;
  // Some work
  return list.buffer;
}
// Somewhere else
ByteBuffer buf = fn();
var list = buf.asFloat64List();
// Work

I already have a case where I return buffer, not a TypedData, because I cast it or use .readX/.writeX methods.
And I need to keep track when buffer dies, so I can do after-write job.
Right now I use weak_cache to achieve that, but I still have to manually call my release extension method.
I can provide more detailed example if needed.

@Zekfad Maybe instead of returning a ByteBuffer you could return the original Uint8List or TypeData? Then at places where you need to cast it you can "unwrap" it to buffer:
TypedData fn() {
  Uint8List list;
  // Some work
  return list;
}
// Somewhere else
TypedData mem = fn();
var list = mem.buffer.asFloat64List();

Then you can associate cleanup routine (e.g. via a Finalizer) with this TypeData object.

@mraleph thanks for suggestion, but I don't think that'll work, because Uint8List would be GC'd right after access if you won't use it later in a code, e.g. doing final buf = fn().buffer.asFloat64List() would not remain strong reference to returned Uint8List if I understand everything correctly.

From what I think it's some internal "byte buffer" that actually powers TypedData rather than ByteBufffer.
My initial assumption was that ByteBuffer is a reliable way to reference that internal buffer and track it's GC.
So if modifying ByteBuffer is a no-go, maybe we can add property to it like MemoryPointer that will be strong referenced from internal buffer, that way as long as such "pointer" is alive we can track that internal buffer is used somewhere in views, that we haven't seen from our side (e.g. used made unmodifiable view and scrapped the original TypedData).
I'm not really happy with such approach though because in my vision it's ByteBuffer that should serve such role (at least from what docs phrasing implies).

@mraleph thanks for suggestion, but I don't think that'll work, because Uint8List would be GC'd right after access if you won't use it later in a code, e.g. doing final buf = fn().buffer.asFloat64List() would not remain strong reference to returned Uint8List if I understand everything correctly.

The object returned from typed data constructors is the underlying backing store / memory (in the Dart VM - possibly not on dart2js).
So for the VM:
final bytes = Uint8List(...);
final buffer = bytes.buffer; // This is a wrapper object that actually holds on to [bytes]
final float = buffer.asFloat64List(); // This is a wrapper object that actually holds on to [bytes].

Alternatively, the VM could change it's implementation, make the byte buffer be the object which represents the underlying memory, and let every typed data view be a view on a byte buffer. Instead of having both direct typed data and views, and avoid one source of polymorphism that way.
It would allocate one extra object per typed data list, the view wrapper, but would avoid the byte buffer wrapper whenever the buffer is accessed. And it would allow the byte buffer to keep it's identity.

The object returned from typed data constructors is the underlying backing store / memory (in the Dart VM - possibly not on dart2js).

@mkustermann, thanks for clarification! This holds true for other TypedData I assume?
@lrhn proposal to make byte buffer be the actual source for underlying data seems to be the best possible solution for my case. That would be very appreciated!

The object returned from typed data constructors is the underlying backing store / memory (in the Dart VM - possibly not on dart2js).

Definitely not on the web.
The specification of typed data arrays on the web, which Dart copied because it could then be supported on the web, is based on a byte buffer (ArrayBuffer) containing the memory, and different views (like Uint8Array) on that memory.
By having only one view class per type, so Uint8Array is always a view, they avoid polymorphism. There is really only one implementation of Uint8Array.
I'm sure there are both external and internal byte buffers in V8, so they cheat in other ways to get good performance in either case, but that's another issue. If you work with a Uint8Array, it's always the same kind of object.
In Dart, I used to convert my Uint8List(42) to a view immediately, to avoid polymorphism on the VM (the specialization of typed data should have made that unnecessary today.)


ssl_cert_lookup_by_pkey() assumes the EVP_PKEY contains legacy internal key

There are two ways to deal with this:

downgrade the input key (this should be a temporary measure)
change it to deal with provider side internal keys as well (this should be the ultimate result, before the final 3.0 release)

Ref: https://github.com/openssl/openssl/issues/11549#issuecomment-623297414

@mattcaswell, I would like some input from you here

ssl_cert_lookup_by_pkey() assumes the EVP_PKEY contains legacy internal key

By this do you mean that it calls EVP_PKEY_id()? In practice all algorithms that we're ever going to use will exist as legacy algorithms. i.e. you can't just drop in an algorithm for use by a certificate that libssl has never heard of and expect it to work. To do that, its a level of refactoring beyond the scope of 3.0. So we should be able to make EVP_PKEY_id() work for all interesting algorithms - even if we've only got provider side keys.

There's the new related issue #11823 that points out the EVP_PKEY_id() response as well.
ssl_cert_lookup_by_pkey() should really be remade into using EVP_PKEY_is_a()

Searching for EVP_PKEY_id() in libssl gives me 20 matches.

... and most of them probably succeed because we downgrade keys

Actually, I think I have a fix...

So, tentative fix in #11828.  @beldmit, @mouse07410, would you mind trying this out?

Gost engine tests are passed.

@levitte, could you please take a look at #11792 to enable GOST engine tests as a part of external tests?


FAILED STK-PUSH: ACCOUNTREFERENCE

{"status":"error","message":"The element AccountReference is invalid.","data":"20"}; Status code: 400 [] {"uid":"021d69b"}
Can't find a clear cause of the error

Hi @AustinOyugi , I believe the AccountReference parameter on the request body should be of type string and have a Maximum of 12 characters. Maybe check that

{
"BusinessShortCode": "1850908",
"Password": "",
"Timestamp": "20220615022333",
"TransactionType": "CustomerBuyGoodsOnline",
"Amount": "20",
"PartyA": "254721373685",
"PartyB": "1850908",
"PhoneNumber": "254721373685",
"CallBackURL": "https://7cb2-196-108-161-29.ngrok.io/v1/payment/mpesa/stkpush/callback",
"AccountReference": "5BPW2EMS67XE",
"TransactionDesc": "CustomerBuyGoodsOnline",
"Remark": "CustomerBuyGoodsOnline"
}

The payload I'm sending

@kisese any updates?


Technical Hotline available hours inconsistent

Where to find the issue

https://www.coronawarn.app/en/faq/results/#who_can_help "Who can help with questions regarding the Corona-Warn-App?"
https://www.coronawarn.app/de/faq/results/#who_can_help "Wer hilft bei Fragen zur Corona-Warn-App?"

Describe the issue
The Technical Hotline (0800 7540001 / +49 30 498 75401) has changed the operating hours and the languages offered.

Technical hotline
Previously
Now

Availability
Mo - Sa 7 am to 10 pm
Mo - Fr 9 am to 5 pm

Language
Turkish, English and German
German

This is already reflected in the information shown by the app (CWA Android 2.20.3, three-dot symbol > App Information > Technical Hotline)

The article https://www.coronawarn.app/en/faq/results/#international_phone_numbers has also already been modified to state: "It is available Monday to Friday from 9 a.m. to 5 p.m. German local time (except on German national holidays):"
The following two articles still contain the old operating hours:

https://www.coronawarn.app/en/faq/results/#who_can_help "Who can help with questions regarding the Corona-Warn-App?" - "You can reach the technical hotline from Monday to Saturday from 7 a.m. to 10 p.m. (except on German national holidays) ..."
https://www.coronawarn.app/de/faq/results/#who_can_help "Wer hilft bei Fragen zur Corona-Warn-App?" - "Sie erreichen sie von Montag bis Samstag von 7 bis 22 Uhr (außer an bundesweiten Feiertagen) ..."

Suggested change
In the following FAQ articles:

https://www.coronawarn.app/en/faq/results/#who_can_help "Who can help with questions regarding the Corona-Warn-App?"
https://www.coronawarn.app/de/faq/results/#who_can_help "Wer hilft bei Fragen zur Corona-Warn-App?"

change the operating hours of the Technical Hotline from Mo - Sa 7 am to 10 pm to Mo - Fr 9 am to 5 pm.
Related issue / PR

https://github.com/corona-warn-app/cwa-hotline/issues/23
https://github.com/corona-warn-app/cwa-website/pull/2597

PR #2676 is submitted to resolve this issue.

The FAQs on

https://www.coronawarn.app/en/faq/results
https://www.coronawarn.app/de/faq/results

now consistently list the new operating hours for the Technical Hotline (0800 7540001 / +49 30 498 75401):

Technical hotline
Operating hours

Availability
Mo - Fr 9 am to 5 pm


Fixed issue with Resolve-Path breaking UNC keypaths.

Fixes https://github.com/microsoft/ReportingServicesTools/issues/384 .
Changes proposed in this pull request:
Changes Resolve-Path to examine the path as a Parent and Child instead of as a single unit to avoid damaging the proper UNC path.
How to test this code:
Restore-RSEncryptionKey -ReportServerInstance "Instance" -Password "Password" -KeyPath "\domain\share\folder\keyfile.snk"
(Testing outside the module requires functions in ShouldProcess.ps1 and ConnectionObjectRequests.ps1)
Has been tested on (remove any that don't apply):
PSVersion 5.1.17763.2931
Windows Server 2019 Datacenter
SQL Server 2016

@jtarquino I think the appveyor build failed out during the execution of the setup functions and didn't get to the point of testing the change I made. I'm unsure if there is anything I need to do to proceed.


Add hosts data source

This is a continuation of #120
Todo

[x] ~Update the data sources id to be a hash of the parameters to prevent collisions~ - the current implementation should be fine for now
[x] ~Add check for length of pool variable to prevent multiple pools matching~ - not necessary since the the lookup is by pool id (so guaranteed to fail or be a single result)
[x] Fix TestAccXenorchestraDataSource_host test (the required id attribute is causing it to fail)
[x] Consolidate xoa/data_source_host.go and xoa/host.go
[x] Brainstorm ideas on how to increase coverage on TestGetSortedHosts and the acceptance tests (testing that sorting works, etc) - Verify that number of hosts in acceptance test is greater than 1 and create a new TestCheckTypeListAttrSorted to validate the sorting is correct
[x] Create GitHub issue to allow server side filtering to include tags and other attributes - #143
[x] Add documentation for the data source
[x] make testacc passes (currently all new tests are passing)

@gohumble I made additions on top of your changes in #142. The largest changes were around improving the acceptance tests to verify that the sorting works.
This should be done aside from the docs that need to be written but I'd appreciate it if you could give this a review.

sorry for replying bit late. tested your changes in my home lab. everything is still looking good :)

Is it worth doing a release with these changes in?

@brd I will. I'm trying to merge #144 before making the next release.

@brd it's now available in v0.19.0 of the provider


Grafana shows warning if metric name does not follow naming convention

Grafana now shows a warning on panels that use PromQL queries that use functions like rate() which only work on counters but the metric name does not suggest that it is a counter.

We have plenty of metrics like this, e.g. attestation summary on validator monitor dashboard
https://github.com/ChainSafe/lodestar/blob/3076b4cbe34bbe4ebadb005f78f90c256ab31aae/packages/beacon-node/src/metrics/metrics/lodestar.ts#L1009-L1010
To get rid of the warning and more strictly follow Prometheus best practices we would have to update the metric name
-validator_monitor_prev_epoch_attestation_summary
+validator_monitor_prev_epoch_attestation_summary_total

I am not sure if it's worth fixing as it would break existing dashboards but the warnings might also be confusing to users and it would generally be good to follow the recommended naming convention.

Those warnings seem to be gone on the latest Grafana release, I don't think it's worth the rename all of those metrics but we should make sure to follow best practices when naming new metrics.

@nflaig can you provide the version of Prometheus and Grafana in which they resolved the warnings??
because i can still see those warnings in my grafana
for my case these were the versions.
prometheus v : 2.52.0
grafana v : 11.1.4

@nflaig can you provide the version of Prometheus and Grafana in which they resolved the warnings??

Right it seems like they show up on v11.1.x again, I honestly can't remember what version they were gone again but in any case I think it's not worth renaming the metrics as it would force users to re-import the modified dashboards.
We should definitely make sure to properly name all new metrics from now on.


Pass along the base value in the end_access writeback for diagnostics

rdar://44147745

@swift-ci Please smoke test and merge.


Prebuilt image enhancements

Build all image variants, fix OAI image build, and provide document instructions.
Maybe it's worthy to cherry-pick those changes to all branches, so images will be built for all configurations.

Amazing contribution.. thanks a lot.

@FlyGoat Hey, I will merge this once I am back from vacation


chore(model): add 2 application flags

Fixes #1238.

Codecov Report

Merging #1267 (33dfc21) into main (b28fdde) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1267      +/-   ##
==========================================
- Coverage   31.06%   31.05%   -0.01%
==========================================
  Files         359      359
  Lines       14231    14231
==========================================
- Hits         4421     4420       -1
- Misses       9810     9811       +1

Impacted Files
Coverage Δ

model/src/oauth/current_application_info/flags.rs
80.00% <ø> (ø)

http/src/routing/route_display.rs
9.78% <0.00%> (-0.77%)
:arrow_down:

http/src/request/mod.rs
85.71% <0.00%> (ø)

http/src/routing/route.rs
6.62% <0.00%> (+0.63%)
:arrow_up:

model/src/application/callback/mod.rs
53.96% <0.00%> (+1.58%)
:arrow_up:

Continue to review full report at Codecov.

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


How to add "keyword" and "text" field types in the mapping?

Hey there,
I managed to make this package work with ES6, but as long as the "string" data type has been dropped there, I'm trying to add the "keyword" and "text" fields in the mapping like this:
$map->addField('keyword', 'type');
$map->addField('text', 'description');
But for some reason those fields are being ignored and they do not appear in the mapping at all. Any ideas why?

You should take a look at Grammer

@killtw I just went lower level with Elasticsearch\Client itself and problem solved.
Still the support for those fields should be added in the upcoming release of this package.

@andrey-bahrachev How did you resolve this issue?

@thitami Do something like this:
$client = Plastic::getClient();

$params = [
    'index' => 'your-index-name',
    'type' => '_doc',
    'body' => [
        '_doc' => [
            '_source' => [
                'enabled' => true,
            ],
            'properties' => [
                'uuid' => [
                    'type' => 'keyword',
                ],
                'path' => [
                    'type' => 'text',
                ],
            ],
        ],
    ],
];

$client->indices()->putMapping($params);

Thanks alot , @andrey-bahrachev. Appreciated!

really amazing , why did not provide text mapping, because string dropped in ES6. i am using Plastic but because of some advances that exist in ES6 i want also use ES6. what i must to do?

I do some thing like this and seems to work:
i changed this:
 public function string($field, $attributes = [])
    {
        return $this->addField('string', $field, $attributes);
    }

to this:
 public function text($field, $attributes = [])
    {
        return $this->addField('text', $field, $attributes);
    }

is this true action?
and finally mapped successfuly


snowflake_stage recreates every apply regardless of an actual change

Terraform CLI and Provider Versions
v1.5.0
0.85.0
Terraform Configuration
resource "snowflake_stage" "LANDING_8X8_STAGE_INBOUND_CALLS_S3" {
  name                = "LANDING_8X8_STAGE_INBOUND_CALLS"
  url                 = var.s3_uri_8x8_inbound_calls
  database            = "AWS_LANDING_INGEST_DB_${var.SF_ENVIRONMENT}"
  schema              = "LANDING_8X8_SCHEMA"
  comment             = "Landing stage for inbound calls s3 bucket"
  file_format         = "FORMAT_NAME = AWS_LANDING_INGEST_DB_${var.SF_ENVIRONMENT}.LANDING_8X8_SCHEMA.LANDING_FF_CSV"
  copy_options        = "ON_ERROR = 'CONTINUE'"
  storage_integration = var.aws_storage_integration
}

Expected Behavior
Stage doesn't destroy and recreate
Actual Behavior
Stage recreates, this causes snowflake pipes to break having a status STOPPED_STAGE_DROPPED
Steps to Reproduce

terraform apply

How much impact is this issue causing?
High
Logs
No response
Additional Information
No response

Hey @bmhah. Thanks for reaching out to us.
Please share the terraform run logs with TF_LOG=DEBUG enabled.

plan.txt.gz

Hey @bmhah. I will confirm in the morning, but it looks like an easy fix, so we may even be able to include it in tomorrow's release. I will keep you posted.

Sounds good, we'll get to testing this later this week. I'll keep this issue open in the meantime

Hey @bmhah. Have you have a chance to test the newer versions after the introduced fixes?

Yes, we've done the provider upgrade to 88 and have also used others, they haven't worked for us, the stage for this pipe still drops and recreates causing the pipe to break again

The fix was introduced in 0.89, not 0.88, so please provide the config and logs (run terraform with TF_LOG=DEBUG) on the 0.89+ version (I could not reproduce the issue given your config on the 0.89 version).

We were having the same issue with:
file_format         = "FIELD_DELIMITER = '|' PARSE_HEADER = true"

Fix in https://github.com/Snowflake-Labs/terraform-provider-snowflake/pull/2885

The fix was included in v0.93.0. Please check it @guillaumelecerf @bmhah.

Hey @sfc-gh-asawicki.
I have the same issue on the version 0.93.0.
terraform configuration
resource "snowflake_stage" "stage" {
      database = "DATABASE_NAME"
      file_format = "TYPE = CSV NULL_IF = []"
      name = "NAME"
      schema = "SCHEMA_NAME"
      storage_integration = "INTEGRATION_NAME"
      url = "s3://aaaaa"
    }

I will take a look this week. Thanks for providing the config; it helps reproduce the issues.

Hi @sfc-gh-asawicki.
Do you have any updates for this issue?

Hey @harukitake. Sorry, I missed this one, I will check it this week.

Hey @harukitake. I've finally reproduced the error.
The current implementation of the stage resource filters out all the file format properties that have default values in Snowflake. TYPE = CSV is the default value, so after reading the resource's state, it is programmatically removed from the file format string, which causes the permadiff you see.
This is, of course, not the expected behavior. For now, please just remove TYPE = CSV from your config, because this is the default in Snowflake.
We will fix the handling of these parameters during the stage resource rework in the next few weeks. I have added a test to confirm it and the note in the resource documentation.


Use booster implementation for get-model endpoint

get-model is implemented in booster and should be used, rather than forwarding to the legacy code.

If getting a model fails in booster, we should still consult the old backend.


PostgreSQL should be configurable with multiple instances

What do you want to improve?
PostgreSQL should be configurable with multiple instances
What is the current behavior?
Currently Postgresql will run on a single instance.
What is the new behavior?
Should have a way to specify a number of replicas.

This should be already possible... where is this comming from? When values are specified via YAML it should work just fine. Maybe we need to regenerate values.schema.json for postgresql to propagate this into OCP Helm UI.
https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml#L166
https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml#L717
etc...

Great, we will add that to the documentation

Should be fixed upstream via: https://github.com/bitnami/charts/pull/21237 (+ propagated back)


Transpiled async generators return a promise value

At least Chrome unwraps promise values. This makes a different runtime behavior.
TypeScript Version:  2.7.0-dev.201xxxxx

Search Terms:
Code
(async function* () {yield Promise.resolve(0)})().next().then(console.log)

Expected behavior:
Outputs {value: 0, done: false}.
Actual behavior:
Outputs {value: Promise, done: false}.
Playground Link:
Related Issues:

Related to https://github.com/Microsoft/TypeScript/issues/21115

Thanks, it seems to address the same issue.


Issue:  Apply skip to content template changes to Design System website.

This is done and merged.


Add icons for top-level nav items in side-nav

Remove the icons for cluster and namespace show for the 2nd level in the nav to indicate if a resource is namespaced
Add icons for the root-level elements - e.g. Cluster, Workload etc - need to make suer we have icons for each item across the 'products'

Won't fix


Buckle rework

Just cleaning it up a lot. Probably going to break vehicle sprites even harder than they are atm but we can fix that later.
TODO:

[ ] Make sure vehicle stun immunity not back.

re-open if you come back to this


1.3.6 suggest inout at callsite for inout parameters

My objection is to this line: f2(out myb); given the declaration void f2(inout   B b);.
Here it is communicated to the reader at the call site that the argument will be modified. It is ambiguous at the callsite whether the value passed in is relevant. Furthermore inout doesn't guarantee that all paths will mutate the argument (whereas out does).
if a reader sees f2(out myb); I think it would be surprising if they could not assume that

the value of myb before the call will not affect the behavior of the function
the value of myb after the function call is the value explicitly selected by the function

yet given the declaration of f2 above neither of these things can be assumed. I see no reason not to maintain symmetry between the modifiers on the declaration and the modifiers at the call site (aside from defaulting to in at the callsite)

Right, that's a typo and should read f2(inout myb). I've fixed it and it'll be in the next update to the paper, probably later this month. Thanks!

Right, that's a typo and should read f2(inout myb). I've fixed it and it'll be in the next update to the paper, probably later this month. Thanks!


Adding StableRNGs.

This PR adds a StableRNG to the package, along with minor configuration changes to the CI. The StableRNGs package ensures that the generated random streams are consistent across Julia versions.

Good to merge, but the other minor changes should be in separate PRs in the future.


Bulk convert SVG files to PPT

With a single command, convert multiple SVG files into a PPT file with a slide for each SVG.

Commit: 3d65cd0


Removing compiled Polybar

I've installed it via sudo make install provided by tutorial on readme file. How do I undo and remove polybar?

sudo make uninstall


0024 - Code stability, versioning - continuation

Continuation of #15.
Originally, I posted the following:

I am wondering if we could come up with rules, ideas to make our codes more stable for outside users? E.g., rules about breaking changes, release frequency and similar.
I have left out the proposal part so far as I have no clear idea on solutions just yet and I would love to discuss this

We have then been discussing a meta package as one potential solution. However, the workload has always been mentioned as a big con. To find out more about the workload, we then came up with the following action:

Suggested next action: prototype a meta package in a repo, possibly with a upload to test PyPI.

Instead of building a meta package, would it be feasible to add an optional workflow on the pymatgen, emmet repo etc to test against atomate2 so that breakages can be anticipated? (Pinging @janosh to see if there are further ideas). My feeling is that most of the breakages show up in atomate2.

since the atomate2 CI is constantly evolving and would cause extra maintenance burden to keep a copy in sync in pymatgen maybe better to trigger the actual atomate2 CI in its own repo on merges to pymatgen master (with the only difference being to install pymatgen from master). that could be done with a simple curl request from the pymatgen CI:

You can also trigger a GitHub Actions workflow from another GitHub Actions workflow by calling the workflow through the API. To do this, you can use the following command:
curl -L \ -X POST \ -H ``Accept: application/vnd.github+json'' \ -H ``Authorization: Bearer $(( secrets.GITHUB_TOKEN ))'' \ -H X-GitHub-Api-Version: 2022-11-28''

since the atomate2 CI is constantly evolving and would cause extra maintenance burden to keep a copy in sync in pymatgen maybe better to trigger the actual atomate2 CI in its own repo on merges to pymatgen master (with the only difference being to install pymatgen from master). that could be done with a simple curl request from the pymatgen CI:

You can also trigger a GitHub Actions workflow from another GitHub Actions workflow by calling the workflow through the API. To do this, you can use the following command:
curl -L \ -X POST \ -HAccept: application/vnd.github+json'' \ -H Authorization: Bearer $(( secrets.GITHUB_TOKEN ))'' \ -H  X-GitHub-Api-Version: 2022-11-28''

This sounds great. My feeling is that this might be easier to organize than a meta package.

Within the meeting, we agreed that @janosh will try this on the pymatgen repository. We hope this is not too much effort and might therefore be more easily adapted for other important packages  (e.g., the influence of emmet on atomate) than building a meta package.

@JaGeo i hope what i pushed in https://github.com/materialsproject/atomate2/pull/835 and https://github.com/materialsproject/pymatgen/commit/46b018ddc66bc8b60c9528a040bf7fce010f2dca works, in which case atomate2 will raise an alert as soon as a change in pymatgen caused breakage

@JaGeo i hope what i pushed in materialsproject/atomate2#835 and materialsproject/pymatgen@46b018d works, in which case atomate2 will raise an alert as soon as a change in pymatgen caused breakage

Awesome. Thank you :). Let's just  test  it  until  our next meeting.

During the meeting, we decided to test the workflow solution on emmet-core. Here, we will try to run the tests after new release candidates have been made.


Re-think how async methods work

Much of the async code is duplicated as well, so perhaps that should be refactored to depend on the corresponding synchronous calls (reduce duplication of logic). Use of async_std tools could work here.

test comment

test comment


feat: add [GitlabStars] service

re https://github.com/badges/shields/issues/8077

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @sunny0826!

  Generated by :no_entry_sign: dangerJS against d080e9f93c40f1a3918c2ab01bbc9b052aa3fe5d


Add Plugins to simulate Shadow, Ambience and SEDensity related features

coverage: 58.736% (-25.0%) from 83.784%
when pulling d37e4947614779b54306dcc5312b5f64f305bdc6 on sample_correlation
into 5e45b4b2762bd5915b2c07ded2be6b5daf4e0f27 on main.


All routes are greedy?

Hi @krasimir - thanks for your work Navigo, really liking it so far.
I have encountered one issue that I wanted to raise , and that is that all routes seem to be greedy. Meaning that, given a route of /foo, the findMatchedRoutes function will return a positive match for the path /foo/bar, regardless of whether or not a wildcard is used. I believe this RegExp is to blame: https://github.com/krasimir/navigo/blob/master/src/index.js#L5.
Was this an intentional design decision? If not, I am happy to open a PR to fix this issue. Regardless, probably should add a spec to cover this case.

That's a bug. So PR are welcomed. Feel free to submit some or I'll do it next few days.
P.S.
thanks for reporting

Hi I have
router.on('/', IndexPage).resolve();

however it is fired on every page, I've also tried without 1st param.

@Mevrael can you please post all of your code. I mean the initialization of the router and all the attached routes.

Hi @krasimir
Thank you for response. Here is my code. Basically I just started with only 1 route, I have a new page where I don't need what is happening on index but it is also executed.
Init with default settings.
import Navigo from 'navigo/src/index';
import IndexPage from './pages/IndexPage';

const router = new Navigo;
router.on('/', IndexPage).resolve();

Ok, but do you have anohter .on call?

No

So you have an index page which is represented with IndexPage. You registered only this function to the router and nothing else. If you want to get another method fired you need to add another .on line with the appropriate route and function.

I don't want to register any other routes (for now), I just don't need to call my IndexPage function on every route /*
There is no specific logic on 2nd page, it just uses global plugins. But because IndexPage is called there I got some errors since 2nd page does not have those DOM elements and data from the index.

I see ... then I'll suggest to organize your code like that so you don't have the router initialize on the second page at all.


Mauria Hebert Lab 0

{
    "preferred_name": "Mauria",
    "csulb_email"<EMAIL_ADDRESS>    "pronouns": "she/her/hers",
    "previous_gis_experience": "Minored in GIS in undergrad at UCLA, then went on to work as a GIS Technician, and later became a Team Lead at Apple Maps. I now work for a company called Ushr/DMP (make maps for autonomous vehicles) as a QC engineer.",
    "previous_remote_sensing_experience": "Took a few remote sensing classes in undergrad for my minor and worked a lot with satellite imagery at Apple. I now work a lot with LiDAR at Ushr.",
    "previous_programming_experience": "Python programming class with a focus on Arcpy, and a programming class for Google Earth Engine with a focus on Javascript in undergrad.",
    "github_repo_link": "https://github.com/MauriaH/GISC606MH",
    "github_project_link": "https://github.com/users/MauriaH/projects/2",
    "what_you_hope_to_get_out_of_this_class": "Honestly, I'm not sure what to expect from this class at this point, but I'm coming into it with an open mind and as long as I learn something new I'll be satisfied.",
}

Hey @MauriaH,
Thanks for submitting. I appreciate your open mindedness with respect to the class and hope you'll gain something from participating.
I'm curious to learn more about your work ate Apple and Ushr. Are/were you in an analyst-type role analyzing remote sensing data? Or more of an engineer-type role building tools to analyze remote sensing data. Or something entirely different?
Looking forward to learning more about your background and working together this semester.
Best,
Alex

https://github.com/MauriaH/GISC606MH/blob/main/GISC606_Lab1.ipynb

Hey @MauriaH,
Thanks for submitting. I appreciate your open mindedness with respect to the class and hope you'll gain something from participating.
I'm curious to learn more about your work ate Apple and Ushr. Are/were you in an analyst-type role analyzing remote sensing data? Or more of an engineer-type role building tools to analyze remote sensing data. Or something entirely different?
Looking forward to learning more about your background and working together this semester.
Could you share a bit about the larger MS project you're working on outside of this class?
And before I forget, do you have a general idea about the broad topic/area of interest of your final report for this course? No worries if not since I know it's pretty early in the semester. I've been encouraging students to pick a report topic related to their larger MS project (and relevant to Applied Remote Sensing), but feel free to pick another area of interest.
Best, Alex

Hi Alex,
At Apple my role was essentially to develop workflows for generating data into the map. So, the stakeholders would present an idea they'd want to integrate into the map and I would have to manipulate the data, create documentation and present an overall process to get that data into the map.
The project I'm working on is for the San Francisco Public Utilities Commission and we are essentially making a web map application cataloging all of the parcels they own and also helping them highlight areas that are impacted by their locally unwanted land use. We'll also assist with providing recommendations for where they should place environmental justice-centered projects in communities that are impacted most by their land use and also are in the highest need of assistance.
I was thinking about doing some sort of NDVI centered project to highlight how much open space is on the parcels owned by SFPUC and also determine suitable building sites.

https://github.com/MauriaH/GISC606MH/blob/main/GISC606_L2.ipynb


TImeout on deployments

My cluster becomes to return a timeout error always after few times deployment.
Is it degrade to #1015 ?
-----> Discovering process types
       Procfile declares types -> web, worker, rake, console, clock
       Default process types for Ruby -> rake, console, web, worker
-----> Compiled slug size is 39M
-----> Creating release...
remote: Error deploying app release: timed out waiting for deployment completion
To ssh://git@{{censored}}:2222/redmine.git
 ! [remote rejected] monami -> master (pre-receive hook declined)
error: failed to push some refs to 'ssh://git@{{censored}}:2222/redmine.git'

https://gist.github.com/8f5015fc463161f332cc
https://gist.github.com/8c0cccb8e46a2608fc38
https://gist.github.com/9640751c1a42a68ebdde

It looks like the cause is etcd failure: https://gist.githubusercontent.com/anonymous/8f5015fc463161f332cc/raw/etcd-app-monaflynn3-2b9fda20957548849064dcb1f18688a6.log
As I said, there is work in progress to fix this.

Any word on when we can expect a fix for this issue? And is it somewhat random or predictive?

@paul-e-cooley There are a few root causes for this error message, one is caused by network instability in multinode that causes etcd to fail (#1612 is the underlying change necessary to resolve this). I believe someone from your team also reported #1682 which appears to be slightly different, did it reoccur?

Yes. We are testing deployment automation and after a number of deploys to the flynn cluster, the error occurs and continues. Even setting environment variables at that point fails.

@paul-e-cooley Okay, please post the cluster debug info and we'll look for the root cause.

@titanous here is the debug info - https://gist.github.com/c1492577d7e320868a5f

@titanous I currently don't have system metrics logging at the moment. I doubt that high load is causing this. However, I'll install system metrics logging (dd-agent from Datadog) today to have data to back up my claim.

@tianx2 I'm also working on updating to etcd v2.1.1 which claims to fix some related issues and may improve the situation.

Closing, as we no longer use etcd.


Interaction feedback story example should be full-screen

Currently the interaction feedback story in storybook is just a basic button, and for some reason also isn't very performant (compare InteractionFeedback/Button with the Dropdown story)
AC:

Create a full-screen experience for the InteractionFeedback story
Add text in the center of the screen which says "Click anywhere!"
Ensure it is performant

@aVileBroker This is a two parter but I looked over the performance issue and your parsefloats will always cause headaches when animating SVGs. Adding this defaultInterpolationFunctions will significantly increase the performance of the animations:
const defaultInterpolationFunctions = {
  r: (r: any) => r.to((val: string) => `${Math.abs(parseFloat(val).toFixed(1))}`),
  opacity: (opacity: any) => opacity.to((val: string) => `${parseFloat(val).toFixed(1)}`),
};

Love it! Hit me with a PR if you get the chance.


[QUERY] Performance difference between UploadBlobAsync and OpenWriteAsync

Library name and version
Azure.Storage.Blobs 12.19.1
Query/Question
Hi, I am trying to figure out the reason behind the performance difference between UploadBlobAsync and OpenWriteAsync methods.
Here is the minimal test code that I have -
using Azure.Storage.Blobs;
using Azure.Storage;
using System.Runtime.CompilerServices;
using System.Diagnostics;
using Azure.Storage.Blobs.Specialized;

namespace BlobUploadTest
{
    internal class Program
    {
        static async Task Main(string[] args)
        {
            var accountName = "accountname";
            var accessKey = "accessKey";
            var containerName = "containerName";

            var keyCred = new StorageSharedKeyCredential(accountName, accessKey);
            var blobClient = new BlobServiceClient(new Uri($"https://{accountName}.blob.core.windows.net"), keyCred);

            var containerClient = blobClient.GetBlobContainerClient(containerName);

            var sw1 = new Stopwatch();
            sw1.Start();

            {
                using var fs1 = new FileStream(@"C:\temp\LocalExport\dataFile.data", FileMode.Open, FileAccess.Read);

                await containerClient.UploadBlobAsync("dataFileUploadBlobAsync.data", fs1, CancellationToken.None);
            }

            sw1.Stop();
            Console.WriteLine($"Time taken by UploadBlobAsync is {sw1.ElapsedMilliseconds} ms");

            var sw2 = new Stopwatch();
            sw2.Start();

            {
                using var fs2 = new FileStream(@"C:\temp\LocalExport\dataFile.data", FileMode.Open, FileAccess.Read);

                var blockClient = containerClient.GetBlockBlobClient("dataFileOpenWriteAsync.data");

                using var blobUploadStream = await blockClient.OpenWriteAsync(true, null, CancellationToken.None);

                await fs2.CopyToAsync(blobUploadStream);
            }

            sw2.Stop();
            Console.WriteLine($"Time taken by OpenWriteAsync is {sw2.ElapsedMilliseconds} ms");
        }
    }
}

Both the ways to upload blobs use a file stream that reads from a locally present file (to make sure the incoming stream isn't involving any network I/O etc.) and upload it to a blob store container.
This program was run on an Azure VM (with release configuration built, if it matters) in the East US region, and it was pointed to a storage account in the East US region. The blob being uploaded was of size 256MBs. The output was -
Time taken by UploadBlobAsync is 31936 ms
Time taken by OpenWriteAsync is 165537 ms

Can you please help me understand why there's a significant difference in the two upload methods? I checked that if no BlockBlobOpenWriteOptions are given to OpenWriteAsync, the default BufferSize is 4MB. So not sure what else could be a contributing factor to the slowness of OpenWriteAsync.
Environment
Host:
  Version:      8.0.4
  Architecture: x64
  Commit:       2d7eea2529
  RID:          win-x64

.NET SDKs installed:
  No SDKs were found.

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.29 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.29 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

The purpose of UploadBlobAsync is optimized for uploading the entire content of a blob in a single or a few operations.
The purpose of OpenWriteAsync is to provides a stream for writing data to a blob, allowing for continuous writing over time (like appending to a file).
UploadBlobAsync is designed to upload large blocks of data in a single call (or few calls), which minimizes overhead, whereas OpenWriteAsync performs incremental writes, resulting in more API calls and more network latency. UploadBlobAsync is optimized for scenarios where the entire blob is known upfront, and the SDK can optimize the upload process by combining or batching blocks more efficiently.


allow subdirs for blog (at least)

structure blogs in subdirectories

missing is the inclusion of directories in the index


Login credentials do not work, outdated code?

I hardcoded the credentials into main.py but get an error:
  File "C:\XXX\Python\Python311\Lib\site-packages\atprototools\__init__.py", line 19, in login
    raise ValueError("No access token, is your password wrong?")
ValueError: No access token, is your password wrong?

OS: windows 10
Put complete freshly downloaded archive in a network drive (mapped)
added the extracted repo there
followed instruction from readme.md
login to bsky works in browser on same machine
latest python as well as pi and the dependencies (atprotocl?) installed.
Tried already:
updated atprototools to 0.0.17 Err: no method login.
What can I try to transfer my archive to bsky?

Update
same problem on a linux based NAS
and a Linux desktop (debian based distro)
File "/XXX/python3.11/site-packages/atprototools/__init__.py", line 19, in login
    raise ValueError("No access token, is your password wrong?")
ValueError: No access token, is your password wrong?
```

my bad: used the preceding part of the login as username only.

I had few issues:

I used wrong version of at protocol
I used user handle instead of my email
I did not set env variables correctly... it is different on Windows :-D


Support for custom data, or data from other exchanges

Is your feature request related to a problem? Please describe.
I want to analyze portfolio in other exchanges.
Describe the solution you'd like
Ability to provide other exchange data.

Hi @suvojit-0x55aa,
There is actually a way to use custom data but the problem is that it is impossible to use rebalancing if you use custom data. That's the problem. But, I'm curious to know why you would like to use custom data and where is your data from?
Best 😄

@ssantoshp I wanted to use it with NSE data.

@suvojit-0x55aa Ok, yeah I get it. So, if you want to use custom data you can't rebalance, that's the problem, sorry. But you can also access Indian stock with yfinance, right?

Hi, thanks for this great work! Can you give a toy example about how to use customized data?


Support for Infinity, NaN?

Any plans on being able to serialise Infinity or NaN objects?

Already supported: https://github.com/yeoman/stringify-object/commit/6b6f29a384b79de424d13afaccfeca53a56cb97d


Fatal Error after a while of usage

Hi,
I'm enjoying your repo, I've come across the same fatal error after using the development process - after awhile of changing code and saving changes, the script crashes out - I've tested this on Windows and Mac OSX with the same results - the error below is output upon crashing.
**<--- JS stacktrace --->
==== JS stack trace =========================================
0: ExitFrame [pc: 0x1009ce8d9]

Security context: 0x10eebe6808d1
1: handle(aka handle) [0x10ee39e76f09] [/Users/ahaan/Documents/GitHub/CC-a-haan-jekyll-SRC-Tailwind/node_modules/tailwindcss/lib/lib/substituteClassApplyAtRules.js:~123] [pc=0x741ccdf2719](this=0x10eec2b401b9 ,0x10ee39e76f49 <JSFunction (sfi = 0x10eeacb9e5a9)>,0x10ee884eeb71 )
2: /* anonymous /(aka / anonymous */) [0x1...
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 0x1011bdf85 node::Abort() (.cold.1) [/usr/local/bin/node]
2: 0x10009d569 node::Abort() [/usr/local/bin/node]
3: 0x10009d6cf node::OnFatalError(char const*, char const*) [/usr/local/bin/node]
4: 0x1001de957 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
5: 0x1001de8f7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/bin/node]
6: 0x100364635 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/usr/local/bin/node]
7: 0x100365e8a v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/local/bin/node]
8: 0x10036290e v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/usr/local/bin/node]
9: 0x1003606c0 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/bin/node]
10: 0x10036c4ea v8::internal::Heap::AllocateRawWithLightRetry(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node]
11: 0x10036c571 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/local/bin/node]
12: 0x10033a78a v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/local/bin/node]
13: 0x100689cc0 v8::internal::Runtime_AllocateInOldGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/local/bin/node]
14: 0x1009ce8d9 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_NoBuiltinExit [/usr/local/bin/node]
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>dev: cross-env NODE_ENV=development gulp serve
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/ahaan/.npm/_logs/2021-02-14T18_20_41_950Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: npm run dev
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/ahaan/.npm/_logs/2021-02-14T18_20_42_027Z-debug.log**
Below is whats found in the debug log
**0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'dev' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
8 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/ahaan/Documents/GitHub/CC-a-haan-jekyll-SRC-Tailwind/node_modules/.bin:/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/ahaan/Documents/GitHub/CC-a-haan-jekyll-SRC-Tailwind/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle<EMAIL_ADDRESS>CWD: /Users/ahaan/Documents/GitHub/CC-a-haan-jekyll-SRC-Tailwind
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'cross-env NODE_ENV=development gulp serve' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec dev script
13 verbose stack Error<EMAIL_ADDRESS>dev: cross-env NODE_ENV=development gulp serve
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:315:20)
13 verbose stack     at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:315:20)
13 verbose stack     at maybeClose (internal/child_process.js:1021:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /Users/ahaan/Documents/GitHub/CC-a-haan-jekyll-SRC-Tailwind
16 verbose Darwin 19.6.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "dev"
18 verbose node v12.18.2
19 verbose npm  v6.14.5
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>dev: cross-env NODE_ENV=development gulp serve
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
**

I'm also getting this, @a-haan. I'll have a look at it tomorrow if I've got some time, from a quick read of your message looks like a memory issue. So I'm thinking maybe the constant rebuilds of the site take up a lot of memory (which explains why my laptop fans have randomly been starting), I'll try and workout if there's a way to increase the memory in npm if i can't make the builds more efficient. This kinda thing also happens sometimes when using composer so hopefully a fix for this won't be too hard to find

@lincoln-chawora thank you

Getting the same error. 😕
Any luck @a-haan @lincoln-chawora that you found a solution?