unable to setup vscode extension

Component:

VSCode Extension

Extension version: 0.10.1
LSP version:
OS version and name: Linux Fedora 37

I am on the latest stable version of the extension/LSP.
I have searched the issues of this repo and believe that this is not a duplicate.

Issue
I don't know if this is an issue or a bad use, but I found that it is impossible to install successfuly the vscode
extension. There is always an error message when editing a .typ file about the connection to the language server.
Do I need to launch or install the language server on my system ? (I understood that a language server is imbeded
in the vscode extension.
Logs
[Trace - 09:51:44] Received response 'initialize - (0)' in 198ms. Request failed: Internal error (-32603).
[Error - 09:51:44] Server initialization failed.
Message: Internal error
Code: -32603
[Error - 09:51:44] Typst Language Server client: couldn't create connection to server.
Message: Internal error
Code: -32603
[Trace - 09:51:44] Received notification 'window/logMessage'.
Params: {
"message": "src/workspace/package/external/manager.rs:58 { message = got external package cache; cache = LocalProvider { root: "/home/ravard/.cache/typst/packages/" }; }",
"type": 3
}
[Info  - 09:51:44] src/workspace/package/external/manager.rs:58 { message = got external package cache; cache = LocalProvider { root: "/home/ravard/.cache/typst/packages/" }; }
[Trace - 09:51:44] Received notification 'window/logMessage'.
Params: {
"message": "src/workspace/package/external/manager.rs:48 { message = got user external package directory; user = LocalProvider { root: "/home/ravard/.local/share/typst/packages/" }; }",
"type": 3
}
[Info  - 09:51:44] src/workspace/package/external/manager.rs:48 { message = got user external package directory; user = LocalProvider { root: "/home/ravard/.local/share/typst/packages/" }; }
[Trace - 09:51:44] Received notification 'window/logMessage'.
Params: {
"message": "src/workspace/package/manager.rs:42 { message = initialized package manager; current = {Url { scheme: "file", cannot_be_a_base: false, username: "", password: None, host: None, port: None, path: "/home/ravard/workspace", query: None, fragment: None }: Package { root: "file:///home/ravard/workspace" }, Url { scheme: "ssh", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("olive2.ovh")), port: None, path: "/home/fedora/workspace", query: None, fragment: None }: Package { root: "ssh://olive2.ovh/home/fedora/workspace" }, Url { scheme: "file", cannot_be_a_base: false, username: "", password: None, host: None, port: None, path: "/home/ravard/win_drive_c/users/ravard/workspace", query: None, fragment: None }: Package { root: "file:///home/ravard/win_drive_c/users/ravard/workspace" }, Url { scheme: "file", cannot_be_a_base: false, username: "", password: None, host: None, port: None, path: "/home/ravard/workspace/", query: None, fragment: None }: Package { root: "file:///home/ravard/workspace/" }, Url { scheme: "file", cannot_be_a_base: false, username: "", password: None, host: None, port: None, path: "/home/ravard/workspace/", query: None, fragment: None }: Package { root: "file:///home/ravard/workspace/" }, Url { scheme: "ssh", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("olive3.ovh")), port: None, path: "/home/fedora", query: None, fragment: None }: Package { root: "ssh://olive3.ovh/home/fedora" }}; external = ExternalPackageManager { providers: [LocalProvider { root: "/home/ravard/.local/share/typst/packages/" }, LocalProvider { root: "/home/ravard/.cache/typst/packages/" }], cache: Some(LocalProvider { root: "/home/ravard/.cache/typst/packages/" }), repo: Some(RemoteRepoProvider { base_url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("packages.typst.org")), port: None, path: "/", query: None, fragment: None }, client: Client { accepts: Accepts, proxies: [Proxy(System({}), None)], referer: true, default_headers: {"accept": "/"}, timeout: 30s } }) }; }",
"type": 3
}
[Info  - 09:51:44] src/workspace/package/manager.rs:42 { message = initialized package manager; current = {Url { scheme: "file", cannot_be_a_base: false, username: "", password: None, host: None, port: None, path: "/home/ravard/workspace", query: None, fragment: None }: Package { root: "file:///home/ravard/workspace" }, Url { scheme: "ssh", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("olive2.ovh")), port: None, path: "/home/fedora/workspace", query: None, fragment: None }: Package { root: "ssh://olive2.ovh/home/fedora/workspace" }, Url { scheme: "file", cannot_be_a_base: false, username: "", password: None, host: None, port: None, path: "/home/ravard/win_drive_c/users/ravard/workspace", query: None, fragment: None }: Package { root: "file:///home/ravard/win_drive_c/users/ravard/workspace" }, Url { scheme: "file", cannot_be_a_base: false, username: "", password: None, host: None, port: None, path: "/home/ravard/workspace/", query: None, fragment: None }: Package { root: "file:///home/ravard/workspace/" }, Url { scheme: "file", cannot_be_a_base: false, username: "", password: None, host: None, port: None, path: "/home/ravard/workspace/", query: None, fragment: None }: Package { root: "file:///home/ravard/workspace/" }, Url { scheme: "ssh", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("olive3.ovh")), port: None, path: "/home/fedora", query: None, fragment: None }: Package { root: "ssh://olive3.ovh/home/fedora" }}; external = ExternalPackageManager { providers: [LocalProvider { root: "/home/ravard/.local/share/typst/packages/" }, LocalProvider { root: "/home/ravard/.cache/typst/packages/" }], cache: Some(LocalProvider { root: "/home/ravard/.cache/typst/packages/" }), repo: Some(RemoteRepoProvider { base_url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("packages.typst.org")), port: None, path: "/", query: None, fragment: None }, client: Client { accepts: Accepts, proxies: [Proxy(System({}), None)], referer: true, default_headers: {"accept": "/"}, timeout: 30s } }) }; }
[Trace - 09:51:44] Received notification 'window/logMessage'.
Params: {
"message": "src/server/lsp.rs:56 { message = could not register workspace files on init; err = the provider does not provide the requested URI; }",
"type": 1
}
[Error - 09:51:44] src/server/lsp.rs:56 { message = could not register workspace files on init; err = the provider does not provide the requested URI; }

I found the problem: this is an imcompatibility with the SSH FS extension.

What is the "SSH FS extension"? Is this something for VS Code, an extension to your Linux/Windows kernel, or something else? It might be possible to add support for this, depending on exactly how it works.

This IS a vscode extension
Le mer. 1 nov. 2023, 04:57, Nathan Varner @.***> a
écrit :

What is the "SSH FS extension"? Is this something for VS Code, an
extension to your Linux/Windows kernel, or something else? It might be
possible to add support for this, depending on exactly how it works.
—
Reply to this email directly, view it on GitHub
https://github.com/nvarner/typst-lsp/issues/341#issuecomment-1788369119,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFJ523CBQAQTV2K6TRSBO4TYCHCCBAVCNFSM6AAAAAA6SM4V6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBYGM3DSMJRHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Mostly for my own reference:
It looks like file need to be accessed via VS Code through the FileSystemProvider API (see this issue). This may mean modifying the VS Code extension in particular to allow the language server to access files via LSP by forwarding requests to this API.


Fully support SockAddr

Hi I made the change to fully support SockAddr using a newtype wrapper, it did require that I restrict the versions of hashable and network packages though. The network package from 2.6.1 adds an extra "can" constructor so that is the reason for the upper limit and the instance for hashable changed in 1.2 so that is the reason for the lower limit.

The implementation looks good. The only problem is that this package
stays in sync with Stackage and the network upper bound doesn't work in
the constraints of LTS-3.0. I don't mind upper bounds, in general, but I
would really like to keep compatibility with LTS wherever possible.
Is the problem with hashing the SockAddrCan that it really doesn't make
sense for network/web servers?
On Sun, Aug 16 2015, Handré Stolp<EMAIL_ADDRESS>wrote:

Hi I made the change to fully support SockAddr using a newtype wrapper, it did require that I restrict the versions of hashable and network packages though. The network package from 2.6.1 adds an extra "can" constructor so that is the reason for the upper limit and the instance for hashable changed in 1.2 so that is the reason for the lower limit.
You can view, comment on, or merge this pull request online at:
https://github.com/creichert/wai-middleware-throttle/pull/3
-- Commit Summary --

Changed the code to completely support SockAddr
fixed ordering function for Address
fixed version constraint on network

-- File Changes --
M Network/Wai/Middleware/Throttle.hs (27)
M wai-middleware-throttle.cabal (4)

-- Patch Links --
https://github.com/creichert/wai-middleware-throttle/pull/3.patch
https://github.com/creichert/wai-middleware-throttle/pull/3.diff

Reply to this email directly or view it on GitHub:
https://github.com/creichert/wai-middleware-throttle/pull/3

Hi, I wasn't hashing SockAddrCan because the version of network library I was wanting to use this with does not have that construtor yet and I was just lazy really. So I made a change to support both the newer and older versions of network library using CPP.

Perfect, thanks!

Just uploaded the new version to hackage (https://hackage.haskell.org/package/wai-middleware-throttle)


add build/installation instructions on different platforms

Add build and installation instructions on Fedora (37, 38), Rocky (8, 9) and RHEL 8. For RHEL 9, libev is not supported, we'll have to remove the dependency on that in the future, in order to support RHEL 9.
The main differences are the ways to fulfill depency requirements on different platforms in order to build pgmoneta. Luckily building and installing pgmoneta is the same on all the current primarily supported platforms.

So turns out I got the wrong version of EPEL installed on RHEL 9... So there is no need to remove dependency on anything for now 😃.

Rebased, and merged.
Thanks for your contribution !


feat(#83): Compile java classes dynamically for tests

Compile java classes dynamically for tests.
Closes: #83.

PR-Codex overview
This PR focuses on enabling the compilation of Java classes dynamically.
Detailed summary

Removed the disabled status from the compilesJavaAndTranspilesBytecodeToEo test.
Added import statements for various Java classes in JavaSourceClass.
Modified the constructor of JavaSourceClass to include the filename.
Implemented the compile method in JavaSourceClass to dynamically compile the Java class and return the bytecode.
Added the filename method in JavaSourceClass to extract the name of the Java class from the resource path.
Added the BytecodeManager class in JavaSourceClass to manage the compilation process and store the bytecode.
Added the SourceCode class in JavaSourceClass to represent the Java source code.
Added the Bytecode class in JavaSourceClass to represent the bytecode of the compiled class.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 3min)


Add color to scripts to increase readability

Probably better to leave as is, to keep it standardized. Might revisit this idea at some point though.


iOS (Cocopaods) dependency update - GoogleDataTransport

Could you 🙏  update dependency in MLKitCommon for GoogleDataTransport to version 10+.
Firebase seems to be using newer version.
The error:
[!] CocoaPods could not find compatible versions for pod "GoogleDataTransport":
  In Podfile:
    firebase_messaging (from `.symlinks/plugins/firebase_messaging/ios`) was resolved to 15.1.0, which depends on
      Firebase/Messaging (= 11.0.0) was resolved to 11.0.0, which depends on
        FirebaseMessaging (~> 11.0.0) was resolved to 11.0.0, which depends on
          GoogleDataTransport (~> 10.0)

     GoogleMLKit/BarcodeScanning (~> 6.0.0) was resolved to 6.0.0, which depends on
        MLKitBarcodeScanning (~> 5.0.0) was resolved to 5.0.0, which depends on
          MLKitCommon (~> 11.0) was resolved to 11.0.0, which depends on
            GoogleDataTransport (< 10.0, >= 9.4.1)

The fix, I talk with Google member and recommend this actions:
https://github.com/google/GoogleDataTransport/issues/149#issuecomment-2313898323
firebase_core: ^2.32.0
firebase_remote_config: ^4.4.7
firebase_analytics: ^10.10.7
...Other packages
Or the version old 3 month.

duplicate #669

[!] CocoaPods could not find compatible versions for pod "GoogleDataTransport":
In Podfile:
firebase_messaging (from .symlinks/plugins/firebase_messaging/ios) was resolved to 15.1.0, which depends on
Firebase/Messaging (= 11.0.0) was resolved to 11.0.0, which depends on
FirebaseMessaging (~> 11.0.0) was resolved to 11.0.0, which depends on
GoogleDataTransport (~> 10.0)
google_mlkit_face_detection (from `.symlinks/plugins/google_mlkit_face_detection/ios`) was resolved to 0.11.0, which depends on
  GoogleMLKit/FaceDetection (~> 6.0.0) was resolved to 6.0.0, which depends on
    MLKitFaceDetection (~> 5.0.0) was resolved to 5.0.0, which depends on
      MLKitCommon (~> 11.0) was resolved to 11.0.0, which depends on
        GoogleDataTransport (< 10.0, >= 9.4.1)

Same error with latest version:
firebase_messaging: ^15.1.0
firebase_analytics: ^11.3.0
firebase_crashlytics: ^4.1.0
firebase_core: ^3.4.0


unmount Listener error

RN 0.31. IOS and Andorid
page1 set prt
page2 set prt
page1 -> push -> page2 -> pop ->page1  then,show error:
undefined is not an object(evaluating 'this._listeners[id].x')
removeListener
AnimatedImplementation.js:897
componentWillUnmout
ScrollAnimationjs:116

Thanks for submitting this issue, and sorry for not looking into it earlier.  It is fixed now with commit 7b6e16ae9fc101cab9b91ad3eb4f7b667b849200


⚠ ClamAV has degraded performance

In 03511fd, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 95 ms

Resolved: ClamAV performance has improved in d58e366.


Some (de)serializers output a datetime object when parsing

Describe the bug
I'm using cbor2 as my (de)serializer for Pyseto. When parsing a bytestring, cbor2 already outputs a datetime object, causing an error when iso8601 tries to parse the datetime. Would it be possible to add a check to see if nbf and exp are datetime objects before trying to parse them?
To Reproduce
Steps to reproduce the behavior:

Set cbor2 as the Pyseto (de)serializer.
Try to decode a PASETO.

Expected behavior
No error, Pyseto takes the pre-parsed datetime and uses it.

Thanks in advance for your help! This is a really great library.

Thanks for the bug report. I will check and reply within a day.

@MrAwesomeRocks Could you put the sample code (PASETO payload j) which causes the error?
Following test code for cbor2 works:
    @freezegun.freeze_time("2021-01-01")
    def test_sample_v4_public_with_serializer_with_code(self):

        private_key_pem = b"-----BEGIN PRIVATE KEY-----\nMC4CAQAwBQYDK2VwBCIEILTL+0PfTOIQcn2VPkpxMwf6Gbt9n4UEFDjZ4RuUKjd0\n-----END PRIVATE KEY-----"
        public_key_pem = b"-----BEGIN PUBLIC KEY-----\nMCowBQYDK2VwAyEAHrnbu7wEfAP9cGBOAHHwmH4Wsot1ciXBHwBBXQ4gsaI=\n-----END PUBLIC KEY-----"

        private_key = Key.new(version=4, purpose="public", key=private_key_pem)
        token = pyseto.encode(
            private_key,
            {"data": "this is a signed message", "exp": "2022-01-01T00:00:00+00:00"},
        )
        public_key = Key.new(version=4, purpose="public", key=public_key_pem)
        decoded = pyseto.decode(public_key, token, deserializer=json)

        assert decoded.payload["data"] == "this is a signed message"
        assert decoded.payload["exp"] == "2022-01-01T00:00:00+00:00"

This throws an error
import cbor2
from datetime import datetime, timezone
import pyseto
from pyseto import Key

key = Key.new(version=4, purpose="local", key="test")

token = pyseto.encode(key, {"data": 5, "nbf": datetime.now(tz=timezone.utc)}, serializer=cbor2, exp=100)
decoded = pyseto.decode(key, token, deserializer=cbor2)

It works with OrJSON though.


How to use a factory definition in a separate file?

Hi, JS newbie here. Hopefully a quick one for one of the old maintainers or anyone else taking a look.
All of the examples are both defineing and building factories in the same file. How do I export my factory definitions so that I can require/use them in a separate test file?

If you are using babel you can use this example:
One file with all of your factories: test/factories.js
import { factory } from 'factory-girl';

factory.define('user', Object, {
  name: 'sam'
});

export default factory;

And in your tests: eg. test/test.js
import factory from './factories';

factory.build('user').then()


Small Typo

/07-malware/trojans.md
Line 123

software that's intend t find it
software that's intended to find it

Thanks @marburgja , would you like to create a PR? I'd merge it then.


Feature Request - Suppress breadcrumbs for notes without breadcrumbs metadata

Add option to fully suppress breadcrumb information at top of preview mode for any notes with no parent, child or siblings metadata.
If edit mode breadcrumb view is ever added as a new feature it should also have an option to suppress the breadcrumb information
The basis of this request is many notes will not be part of a parent/child/sibling breadcrumb network.
This will allow a clear visual delineation when viewing notes as to whether they are in the breadcrumb planned network (eg a zettelkasten) or in the overall obsidian link network.
Thanks for the plug-in.

Added in 0.8.19


repository 'https://github.com/Azure-Samples/emplate/' not found

When I execute
azd init --template todo-nodejs-mongo
I get the error message below
C:\Users\borget\source\repos\azdquickstart>azd init -template todo-nodejs-mongo
Initializing a new project (azd init)
|      =| Downloading template code to: C:\Users\borget\source\repos\azdquickstartinfo: please complete authentication in your browser...
(✓) Done: Downloading template code to: C:\Users\borget\source\repos\azdquickstart
ERROR: init from template repository: fetching template: failed to clone repository https://github.com/Azure-Samples/emplate: exit code: 128, stdout: , stderr: Cloning into 'C:\Users\borget\AppData\Local\Temp\az-dev-template982246579'...
remote: Repository not found.
fatal: repository 'https://github.com/Azure-Samples/emplate/' not found

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

ID: d31e2f07-64ce-ae10-e15b-4bc52e1c2fd5
Version Independent ID: d31e2f07-64ce-ae10-e15b-4bc52e1c2fd5
Content: Get started using Azure Developer CLI
Content Source: articles/azure-developer-cli/get-started.md
Service: azure-dev-cli
GitHub Login: @alexwolfmsft
Microsoft Alias: alexwolf

Thanks for the feedback, it appears this error is caused by running azd init -template todo-nodejs-mongo instead of azd init --template todo-nodejs-mongo (missing a hyphen on the first command). I have tested the init code on the linked document and it works correctly when both hyphens are there.

#please-close


ENH: Use OrderedDict in io.netcdf. Fixes #5537

Makes use of orderedDict instead of regular dict in io.netcdf. Scavved
from pupynere.
First commit. Please no hate :-)

Since @CallumJHays repo was deleted, I resubmitted this (with fixes) as gh-6932.
Thanks @CallumJHays


Adds alias Thanks @moura137 Fixes #327

Hello @andrewelkins , is not available, you can check please


Badges for the skillmap

This feature request asks to add badges to

[ ] Badges have image\icon, description, name
[ ] Skillmap authoring parsing:  Skillmap author can specific the badges  in the markdown
[ ] Badges saved in the backed along with the skillmap name and url.

This is implemented.


Production site is deployed from an unmerged feature branch

Problem
Presumably as a result of the surge to launch in time for the Members’ Assembly, the new IATI website is currently deployed from an unmerged feature branch (add-page-models) instead of the master branch. I guess this is okay, but it’s not really ideal.
Merging to dev and to master is blocked, because linting checks fail.
Proposed solution
I’ve sent the following pull requests to fix linting: #208, #205, #204, #203, #201, #199 (these pull requests replace #55). Once all of these are reviewed and merged, it should be fine to merge #4 (add-page-models -> dev) and subsequently #22 (dev -> master).

Fixed in #22!

Good to flag this @andylolz - was just going to say this can be closed once https://github.com/IATI/deployment/pull/49 is merged and a deployment is run!

Hadn’t spotted that one! Totally agree. Reopening – I’ll leave it with you.

I guess this can now be closed?


Possibility to run the apb pod at the different namespace than the target namespace

This form is for bug reports and feature requests. Major features will go through a spec process.

Feature:

Possibility to run the apb pod at the different namespace than the target namespace.
For example/use case:
Developer ordered a service called "oracle database" for the namespace "my-cool-app".
Apd pod for "oracle database" provisioning start at namespace  "my-cool-app" and provide the service "oracle database".
For the provisioning of the "oracle database" service it is necessary to have some secret credentials in the pod. I want to hide & protect those information and the pod from the Developer. And for me is the perfect solution is to run the apb pod at a different namespace.
The apb pods creates only the service and connection credentials at namespace "my-cool-app"
If I have seen this correctly, at one of the first alpha releases the apd pod run at the different namespace.
What happened:
Developer ordered a service called "oracle database" for the namespace "my-cool-app".
Apd pod for "oracle database" provisioning start at namespace  "my-cool-app" and provide the service "oracle database".
What you expected to happen:
Developer ordered a service called "oracle database" for the namespace "my-cool-app".
Apd pod for "oracle database" provisioning start at namespace  "my-secret-apb" and provide the service "oracle database".
How to reproduce it:

@rbo thank you for the issue, this sounds like a use case will will want to support.

@jwmatthews I believe this is closed by #428. Should we close this issue?

This was closed because the APB is being launched in a new namespace now. If this is not the desired behavior please re-open.


Fill dataless msgs with data if they're in wantRange

Problem
Suppose you're replicating with a peer that has a smaller haveRange than you have, e.g. they have goal newest-20 while you have goal newest-100. When you do the sync protocol, they will send new msgs in your wantRange, but many of them may be trails because they are applying a stricter GC policy.
So you accept those trail msgs anyway and store them in disk.
However, if you now replicate with another peer that happens to have a more generous haveRange (e.g. from the goal newest-500) then they will be able to provide the dataful msgs than you want. However, you will signal to them that you already have those msgs in disk (which you do, but they're stored as dataless/trails), and thus you won't get the dataful msgs, even though you would really want to.
This means that the strictest remote peer will practically dictate how many dataful msgs you can replicate. This is an undesired protocol behavior.
There is a difficulty here that goes beyond the sync protocol: msgs in the log are assumed to be either appended or shrunk (when erased), no other modification/addition is allowed. And in fact the log implementation will check that msgs can only be overwritten if the new size is $\leq$ the old size. So in the log we can't "replace" a dataless msg with its dataful equivalent.
Glossary

Dataless: when msg.data is null
Dataful: when msg.data is an actual content object
Trail: a msg that originally had msg.data but msg.data was erased and now this msg only serves the purpose of validating the sigchain back to the root
Erase: database log operation that deletes only msg.data from a msg record
Goal: for a given tangle, this informs how much we are interested in replicating/preserving this tangle
wantRange: a tuple [minDepth, maxDepth] of depths of msgs that we signal to a remote peer that we want to receive, for a given tangle
haveRange: a tuple [minDepth, maxDepth] covering all the depths of msgs that we have in the database log

Thought 2
Instead of toposorting all the records, we can also "rebuild" the entire tangle in question by (1) deleting all tangle msgs from the log but keeping them in memory temporarily, (2) appending the new low-depth msgs synced from the remote peer, (3) appending the high-depth msgs that were kept in memory temporarily.
This would create some holes in the log, but that's fine, we can compact the log.
This approach might be the most realistic so far.

Idea 3 (from Mix)
If I get less messages than I originally wanted, then save them in a temporary log and when you finally have all the msgs you want, you can transfer them to the main log, in the correct order.

This is fixed (I think) in ppppp-sync and ppppp-db, but requires new tests in ppppp-sync, so I'm busy with that.

Done


Bump to 0.2.45

Making a release to pull in https://github.com/rustwasm/wasm-bindgen/pull/1544 which fixes a pretty bad bug!


My output screen is glitched

I have read the FAQ.
I have searched in existing issues.

Environment

OS: Windows
scrcpy version: Latest
installation method: Windows release
device model: Xiaomi Redmi 9
Android version: 12

Describe the bug
There is no error and the console log run just fine, but the output is glitched and broken.
The control, audio etc is working fine it just the display that is broken, i've tried using wireless mode but the result is the same, i even tried changing the usb cable but it just keep broken.

Device encoder issue.
Either the default encoder does not support the resolution (try with a lower resolution, like scrcpy -m1024),
or it just does not work. Try with another encoder.

Thank you. you were right it was encoder issue.
i found this encoder to be working just fine
scrcpy -m 1024 -b 8M --max-fps 25 --video-codec=h264 --video-encoder='c2.android.avc.encoder' -Sw


Feature Request: Clear init_img in WebUI

After you provide an init_img to the dream WebUI the uploaded file is sticky and continues to be used for subsequent generations. There's no obvious UI element to clear it (but it can be done by opening the file select dialog and then cancelling). Can a suitable UI element be added? @bakkot @TesseractCat

I've simply been reloading the page to clear the image. If there's going to be a manual 'clear' option (which there should be) then reloading the page ought to remember the file so you don't have to re-browse for it.

Yes, I agree, this would be a convenient addition.
And I don't mean to hijack, but while we are on the topic of adding UI elements for the img2img portion of the WebUI, can you please consider adding a field for the --strength parameter? As mentioned in #134 and #202. I feel it is critical for img2img and as such, I have not been using the img2img feature of the WebUI because of it

As an alternative, we could consider splitting up the interface so there's different tabs for txt2img vs img2img. There's a few fields which are only relevant to each - width/height only make sense for txt2img, and init-img/strength only make sense for img2img. Also, that way if we add any further modes (here I am thinking of generating variants and interpolation) those features could go in their own tabs, instead of cluttering up the main interface with mutually-incompatible sets of UI elements.
Thoughts?

I think the most elegant solution would be to add/show the additional relevant fields when an image has been selected, and then remove/hide them again if the proposed 'clear' button for the img has been clicked.

Fix is in current development branch. Will go to release real soon.


Add ncurses

A dependency for R.

@IsabelParedes there is some dedicated section on crosscompiling mentioning the make_hash function
https://github.com/gittup/ncurses/blob/gittup/INSTALL#L1710

Thanks @DerThorsten ! I had missed this. Following the INSTALL and config instructions, I set BUILD_CC to gcc to compile make_hash and make_keys. It seems that that worked. Now I just need to fix the install.

These are all JS files:

bin/clear
bin/infocmp
bin/ncurses6-config
bin/reset
bin/tabs
bin/tput
bin/tset

Not sure if the file extension will be an issue. Leaving a comment in case it comes up later.

These are all JS files:

bin/clear
bin/infocmp
bin/ncurses6-config
bin/reset
bin/tabs
bin/tput
bin/tset

Not sure if the file extension will be an issue. Leaving a comment in case it comes up later.

I prefer to either have the bin files removed or we test them.
Because often they do not work as often the *.wasm file is not installed.
You could try to add a test in the test section where you try to run the binaries with node

Hi @DerThorsten, I added the *.wasm files to bin/ and I added a test with nodejs for one of the binaries. This seems to work ok. Should I add more tests?

Hi @DerThorsten, I added the *.wasm files to bin/ and I added a test with nodejs for one of the binaries. This seems to work ok. Should I add more tests?

lets just merge it


Update bubble_sort.py

Implemented bubble sort function using python (MEDIUM ISSUE)

Implemented bubble sort function using python (MEDIUM ISSUE)

Code looks good, well done!

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out my other projects. Just click here to find more. These projects contain real issues that you can help resolve. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


Requeue subscriptions on catalogsource change

This PR attempts to clean up several issues:

Subscriptions shouldn't be set to AtLatestKnown if we haven't created a CSV
Requeue dependent subscriptions when catalogsources change
Add sourceNamespace to packages subscription

/approve

tests are passing in ci, it's just stuck cleaning up the cluster


[BUG]

Information

Apktool Version (2.6.1) -
Operating System (Kali Nethunter) -
APK From? (ApkMonk Google Now Launcher) -

Stacktrace/Logcat
ng Apktool 2.6.1
I: Checking whether sources has changed...
I: Checking whether resources has changed...
I: Building resources...
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 2): [/tmp/brut_util_Jar_12056327982085289713948779721590040704.tmp, p, --forced-package-id, 127, --min-sdk-version, 16, --target-sdk-version, 19, --max-sdk-version, 25, --max-res-version, 25, --version-code, 104002, --version-name, 1.4.large, --no-version-vectors, -F, /tmp/APKTOOL2322373381550752404.tmp, -e, /tmp/APKTOOL545606803063370091.tmp, -0, arsc, -I, /root/.local/share/apktool/framework/1.apk, -S, /sdcard/Payloads/original/res, -M, /sdcard/Payloads/original/AndroidManifest.xml]
W: /tmp/brut_util_Jar_12056327982085289713948779721590040704.tmp: 1: ELF: not found
W: /tmp/brut_util_Jar_12056327982085289713948779721590040704.tmp: 1: Syntax error: end of file unexpected (expecting ")")

Steps to Reproduce

apktool

Frameworks
If this APK is from an OEM ROM (Samsung, HTC, LG). Please attach framework files
(.apks that live in /system/framework or /system/priv-app)
APK
If this APK can be freely shared, please upload/attach a link to it.
Questions to ask before submission

Have you tried apktool d, apktool b without changing anything? Yes
If you are trying to install a modified apk, did you resign it? I didn't sign it because i cant recompile it check the traces, can you guys help me with this??
Are you using the latest apktool version? Yes

I believe Nethunter is the Android edition of Kali, which is not supported being Android.


[Parameter] codeunit 6620 "Copy Document Mgt." - OnCopyArchSalesLineOnAfterToSalesLineInsert

After insertion of a new sales line copied from another sales line, we can add extra lines and update the NextLineNo via below publisher.
OnAfterInsertToSalesLine(ToSalesLine, FromSalesLine, RecalculateLines, DocLineNo, FromSalesDocType, FromSalesHeader, NextLineNo);
After insertion of a new sales line copied from another sales archive line, we can add extra lines but NOT set the NextLineNo via below publisher.
OnCopyArchSalesLineOnAfterToSalesLineInsert(ToSalesLine, FromSalesLineArchive, RecalculateLines);
Please add NextLineNo (var) to below publisher
[IntegrationEvent(false, false)]
    local procedure OnCopyArchSalesLineOnAfterToSalesLineInsert(var ToSalesLine: Record "Sales Line"; FromSalesLineArchive: Record "Sales Line Archive"; RecalculateLines: Boolean; var NextLineNo: Integer)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10804.


Textured sprite flicker when in perspective camera mode

The flickering happens when i am in perspective mode with the camera, and i move either the cameras Z position or a sprites Z position, and i use a textured sprite instead of solid colored sprite. If i use solid colored sprite(s) the bug doesn't happen.
Here's a link to an image of the bug:
To reproduce the bug you need to replace the current Renderer2D::DrawQuad with:
 Renderer2D::DrawQuad(transform, m_Tex, 1.0f, sprite.Color);
in Scene.cpp!
Where m_Tex is simply Ref<Texture2D> m_Tex; in the Scene.h.
And then in Scene::Scene() you need to create the m_Tex by doing something like:
m_Tex = Texture2D::Create("assets/textures/ChernoLogo.png"); Just really use a texture of your liking, that is good enough.
Then all you need to do if you have done it correctly, is to build the project, use one of the cameras and switch its view mode from Orthographic to Perspective, and zoom out. you can also now try to move the sprites Z position further away from the screen and it should still flicker.
I expected it to not flicker at all.

Can you show us the configuration of your perspective camera? Flickering usually happens because of z-fighting.
Also if you could post your GitHub repo, so we can download and test it by ourself (and see the code) would be easier to find out what's wrong.

Can you show us the configuration of your perspective camera? Flickering usually happens because of z-fighting.

It really doesn't matter which configuration i use on the perspective camera, because i already know what is causing the problem:
it is because we create and render a blank white texture at slot 0. and that interferes with the other texture.
And the only solution i could find to fix that problem, was to entirely pull everything about the white texture out of the code, but i don't know if that really solves anything.

Also if you could post your GitHub repo, so we can clone and test it by ourselves (and see the code) would be easier to find out what's wrong.

Ok, here is it: https://github.com/standtall007/Hazel.
The only change i have made is this repo has high DPI adjustment added to it, but i have also tried to see if the problem occured without high DPI mode on, and it does.

I can't reproduce the problem. Well, first of all when I use the perspective camera everything is being clipped!
I can't figure it out though... Cherno has created some quite messed up renderer also the shaders are quite messy and I can't figure out what's going on. When you switch to the perspective camera, you can see the texture fine but just
flickering? Because I don't see it at all!

When you say that everything is being clipped, do you then mean that you can't see any of the sprites?
Because if that's so, then you need to set the Z position to around +6.5 (positive, not negative) and if you set it higher you can of course see the sprite(s) getting smaller. Also the camera is normally set to 2.0 in the X axis, also this is the values for the Camera Entity, NOT the Clip-Space Entity. But try these values out and then write back the result. Also i think i had the camera entity's Z position to be = x: 0.0, y: 0.0, z: 8.5. I haven't changed the Fov, Near or Far at all. And the camera entity is set to primary.

It works fine for me: video
This is what I changed in the scene.cpp:
if (mainCamera)
		{
			Renderer2D::BeginScene(mainCamera->GetProjection(), *cameraTransform);

			auto group = m_Registry.group<TransformComponent>(entt::get<SpriteRendererComponent>);
			for (auto entity : group)
			{
				auto [transform, sprite] = group.get<TransformComponent, SpriteRendererComponent>(entity);

				//Renderer2D::DrawQuad(transform, sprite.Color);
                                 //THIS IS WHAT I CHANGED
				Renderer2D::DrawQuad(transform, m_Tex, 1.0f, sprite.Color);
			}

			Renderer2D::EndScene();
		}

I have updated my answer but maybe it is that particular texture i'm using?

I think i'm gonna close this issue for now, since it appears nobody else can reproduce the issue :( I have to take a guess that it is my GPU that is the problem though i honestly do not know for sure.

By the way, now that I remembered if the texture that you are using has dimensions that are not a power of 2 (for example 300x400) this can cause problems in some old drivers! Make sure the texture that you are using has dimensions like:
2x2, 4x4, 256x256, 512x512 , 1024x1024 . BOTH dimensions SHOULD be a power of 2. It is not required to be square you can also have images like 1024x512, as long as both dimensions are a power of 2!!!
This is because of something that is called alignment. Check it out here (OpenGL common mistakes)

That is not the issue, the texture is 16x16 so it is power of 2.

Then it's something else :) I just mentioned it cause I had a problem like that and took me a year to figure it out.

btw when you have the two sprites overlapping but not directly at the exact same positions, do you the see the top sprite having some kind of alpha issue? My sprites show the background where they should be absolutely transparent.

No, I only see one texture (since the other one is behind it) and I don't see any background color.
It sounds like you have quite a lot of issues. It might be your GPU. If you are on windows and you play games
they probably work because DirectX does not have any bugs, but OpenGL might do! Nvidia might not really care
about OpenGL, Linus Torvalds  (the creator of the Linux kernel) once said that Nvidia is the work company that
they dealt with, and since OpenGL is mostly being used on Linux, then chances are that your card might have a bug.

Yeah i thought so too. Well i do have a Amd vega i can put in and test with and report back.

Alright so i have tested with the rx vega 64 and now the z positions work but the alpha blending still doesn't work properly:

Alright so i have tested with the rx vega 64 and now the z positions work but the alpha blending still doesn't work properly:
Okay, i figured it out thanks to Cherno on his live stream today.

Hi,
I have this weird issue both on RTX 2080MQ as well as RTX 2060 Super... Any ideas till now? Thx!

It has to do with blend modes. Make sure you check OpenGL's blend modes to enable alpha blending correctly. That would be the most probable cause

It has to do with blend modes. Make sure you check OpenGL's blend modes to enable alpha blending correctly. That would be the most probable cause

This is my alpha blending mode:
glEnable(GL_BLEND); glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA);
which does not seem to work...

I have found that this issue can be fixed by making v_TexIndex flat.
See #362.


Update fonts cache

When fonts.fonts = [ ]; list is modified in nixos, it causes fonts cache update. It'd be handy to have such option for fonts installed via home-manager so that you don't need to execute fc-cache -f manually.

This looks like a good idea to me :+1:
Why fonts.fonts though? Maybe just a rootlevel fonts or do home.fonts?
I realize that NixOS uses fonts.fonts, i find the name weird though.

Why fonts.fonts though?  Maybe just a rootlevel fonts or do home.fonts?

There is already fonts.fontconfig, so it can't be just fonts. fonts.fonts is at least known from nixos.

Oh, there is. Makes sense to follow NixOS then. I'd probably have chosen fonts.packages, but yours makes sense :smiley:

@rycee, @wedens are you still interested in having this added to home-manager?

If anybody is able to try it out then please have a look at #682, which I believe will resolve this issue.


Create welcome.md

View rendered welcome.md

Not sure the intention here, maybe intended for a different repo.


Questions about reproduction.

Great job on your work, and thank you for sharing the code. I do have a few questions regarding running the experiments on vtab-1k.
Regarding VPT / Adapter / LoRA:

Acc performance: My results for Adapter and LoRA are significantly worse than the original paper (72.0 / 73.9 / 74.5), with my results being 72.81 / 71.65 / 72.35, respectively. I used your configuration files and scripts directly to run Adapter and LoRA, but I am not sure if the code is the exact version used to produce the results in the original paper.
Params: The prompt length of VPT varies across different datasets. How do you determine the parameters for VPT to be 0.64M?

Regarding NOAH:

The pipeline has three stages: 1) supernet training; 2) evolutionary search; 3) subnet retraining. In evolutionary search, should the parameter LIMITS be 0.64? However, it seems to make the searching process omit a lot of subnets (I'm not sure if this is correct)? The original paper says Output: a new subset C and its performance on val set: {C:Acc.}, but my searching logs cannot produce such results. For instance, *-caltech101-vtab-search.log shows the Acc@1 is only 1.000, which is very low and random.
Additionally, how can I obtain the subnet configuration files in experiments/NOAH/subnet/VTAB?

Regarding others:

The model config includes visual_prompt, lora, adapter, and prefix. What does prefix mean here? Is it another method different from VPT / Adapter / LoRA?

I look forward to your response.

Hi Mouxiao
Could you please kindly provide me with the training log of your experiments?

Thank you for getting back to me promptly.
Certainly. As an illustration, I have provided the training logs for Caltech101, which involve VPT, Adapter, LoRA, Supernet, and the corresponding searching log for Supernet, via the following link: link.

Regarding VPT / Adapter / LoRA:

I conducted evaluations for each configuration using three distinct random seeds, subsequently reporting the mean performance. It is recommended to replicate this process. In the event of persisting issues, we can further analysis.

Regarding NOAH:

Indeed, one potential limitation of NOAH lies in its efficiency during the search phase, particularly when faced with small "LIMITS" values. Exploring ways to enhance efficiency under these conditions may prove to be a fruitful direction for improving NOAH. Notably, some solutions have been proposed within the context of Neural Architecture Search (NAS).
It is imperative to verify the accurate loading of the supernet.

Regarding others:

Yes, it is the prefix-tuning method. I found this method perform similarly to VPT, so I do not report this performance.

Thank you for your response, which helped me clarify most of the questions I had.
In addition, I am still confused about the results of evolutionary search experiments. Would it be possible for you to provide a sample search log for any one of the vtab-1k sub-datasets?

Sure.
Check this:https://drive.google.com/file/d/1lW980rK9QIjOidCzdzzs_3s6cPevh1Ey/view?usp=sharing
The log for this configure:https://github.com/ZhangYuanhan-AI/NOAH/blob/main/experiments/NOAH/subnet/few-shot/ViT-B_prompt_oxford_pets_shot16-seed0.yaml

Oh, I figured out why my accuracy results from the search algorithm were confusing and nearly random. It turns out that the issue was caused by the difference in the timm.load_checkpoint function between version 0.4 and versions 0.5 or higher.
Thanks again for your prompt and helpful response.


add optional default value to GroupBy.get_group

I've used a try except block as opposed to and if else (below) to keep the non-default code path fast.  What I didn't do:
if default is None :
    inds = self.indices[name]
else :
    inds = self.indices.get(name, default)

Here is an example use case:
def foo(df, keys) :
    g = df.groupby('key')
    for key in keys :
        for x in g.get_group(key, default=[]).x :
            yield key, x

vs
def foo(df, keys) :
    g = df.groupby('key')
    for key in keys :
        if key in g.indices :
            for x in g.get_group(key).x :
                yield key, x

Many of the simple cases are actually handled by other higher level functions

@dwiel closing, but if you'd like to update, pls do and we can reopen


Upload should work with duplicate headings

After uploading a zip file the workflow.cfg is parsed using a toml library. The toml library does not like duplicate headings while duplicate headings are present in https://github.com/haddocking/haddock3/tree/main/examples .

There is dedupWorkflow() in @i-vresses/wb-core package, but that does not work nicely with remix when imported dynamically:
import { parse, unparse } from "papaparse";
         ^^^^^
SyntaxError: Named export 'parse' not found. The requested module 'papaparse' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'papaparse';
const { parse, unparse } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
    at ModuleJob.run (node:internal/modules/esm/module_job:190:5)

Fixed in https://github.com/i-VRESSE/bartended-haddock3/commit/414eb1169836979d541d3b50c8cf92877884fedc . Make sure @i-vresse/wb-core v1.2.0 is installed.


Added an animation effect to SplashActivity

Kindly merge it. It will provide a sense of motivation to me as its my first ever pull request

The Handler method can be replaced with the new Splash Screen Android 12 update would be better if this is used
https://developer.android.com/about/versions/12/splash-screen-migration

The Handler method can be replaced with the new Splash Screen Android 12 update would be better if this is used https://developer.android.com/about/versions/12/splash-screen-migration

What should i do? Please guide.

Is there any issue in merging this code?

Handler method is not the accurate one
This was introduced to make splash screen deployment easier

Can you please guide me on how to do this.I am not aware of this if you can
then i will be highly obliged to you.
On Sun, Oct 3, 2021 at 2:40 PM Rohan Babbar @.***>
wrote:

Handler method is not the accurate one
This was introduced to make splash screen deployment easier
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/IEEE-VIT/weatherbes-android/pull/44#issuecomment-932894228,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQFQOEK5ELPG7AYDLBPKSO3UFAMZDANCNFSM5FHKDWNA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@kritika-sharma130 we apperciate your efforts but this issue is already solved you can take another issues .
All the best


IR camera doesn't work well in darkness

Required Info

Camera Model
D435

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Win (10)

Platform
PC

SDK Version
legacy / 2.0

Language
C++/opencv

Issue Description
I use D435 in darkness and close laser,there is no difference between IR camera and RGB camera.
infrared image：

my codes:
`int main(int argc, char * argv[])
{
int width = 1280;
int height = 720;
int fps = 30;
rs2::config config;
config.enable_stream(RS2_STREAM_INFRARED, 1, width, height, RS2_FORMAT_Y8, fps);
config.enable_stream(RS2_STREAM_INFRARED, 2, width, height, RS2_FORMAT_Y8, fps);

// start pipeline
rs2::pipeline pipeline;
rs2::pipeline_profile pipeline_profile = pipeline.start(config);
rs2::device selected_device = pipeline_profile.get_device();
auto depth_sensor = selected_device.first<rs2::depth_sensor>();

depth_sensor.set_option(RS2_OPTION_EMITTER_ENABLED, 0.f);
while (1) // Application still alive?
{
	// wait for frames and get frameset
	rs2::frameset frameset = pipeline.wait_for_frames();

	// get single infrared frame from frameset
	//rs2::video_frame ir_frame = frameset.get_infrared_frame();

	rs2::video_frame ir_frame_left = frameset.get_infrared_frame(1);
	rs2::video_frame ir_frame_right = frameset.get_infrared_frame(2);

	cv::Mat dMat_left = cv::Mat(cv::Size(width, height), CV_8UC1, (void*)ir_frame_left.get_data());
	cv::Mat dMat_right = cv::Mat(cv::Size(width, height), CV_8UC1, (void*)ir_frame_right.get_data());
	cv::imshow("img_l", dMat_left);
	cv::imshow("img_r", dMat_right);
	char c = cv::waitKey(1);
	if (c == 's')
	{

	}
	else if (c == 'q')
		break;
}

return EXIT_SUCCESS;

}`

IR cameras do not "see in the dark". You need some source of light (in case of infrared cameras, infrared light) to see something...
One source you can use is the camera projector. Alternatively, you can use an IR-LED (this is what most face authentication systems are doing)
Alternatively, you may want to disable auto-exposure and crank-up both exposure and gain to amplify any ambient light available.

IR cameras do not "see in the dark". You need some source of light (in case of infrared cameras, infrared light) to see something...
One source you can use is the camera projector. Alternatively, you can use an IR-LED (this is what most face authentication systems are doing)
Alternatively, you may want to disable auto-exposure and crank-up both exposure and gain to amplify any ambient light available.

Thanks.One more question,In order to choose a approprite IR-LED ,I want to know the focal length of d435 IR camera .

@HIAI2019 The focal length is 1.93mm for D435 IR. For details you can check the datasheet in https://www.intelrealsense.com/wp-content/uploads/2019/10/Intel-RealSense-D400-Series-Datasheet-Oct-2019.pdf

@HIAI2019 Any other questions from your side? Looking forward to your reply. Thanks!


Question: How to build Kiwibrowser from fork using github actions

Closing in favor of kiwibrowser/src.next#123


bandwidth eating

Describe the bug
i installed the plugin on my vps with bandwidth 6TB/month before it i used maximum 1TB/month but after it the plugin eats all my 6TB bandwidth in 2 weeks

I can confirm that the bandwidth usage is way beyond what I would expect. Mail2most was pulling about 7MB/s constantly while the IMAP inbox had only occasional new email. The bandwidth consumption should be reasonable with the default settings.

I've rewritten this as a Mattermost plugin which also solves this bandwidth issue:
https://codeberg.org/mailmirror/mailmirror


zip file oversize, can't be uploaded to AWS

Describe the bug
I'm facing a 404LambdaFunction issue due to the oversize of the zip file.
My zip file is about 70mo, unzipped it became 270mo.
The project is using typescript.
It doesn't contain any assets as they are all on S3, moreover I excluded, in the serverless.yaml, all unecessary file.
service: 'ProjectName-${self:provider.stage}'
provider:
  name: aws
  runtime: nodejs10.x
  stage: ${opt:stage, 'dev','prod'}
  region: ap-southeast-2
plugins:
  - serverless-nextjs-plugin
  - serverless-dotenv-plugin
custom:
  name: ProjectName-${self:provider.stage}
  serverless-nextjs:
    assetsBucketName: 'ProjectName-${self:provider.stage}'
package:
  exclude:
    - ./**

Each page is about 13mo and looks like the following:

home.js 1ko
home.original.js 13mo
index.js 1ko
index.original.js 13mo

Version "serverless-nextjs-plugin": "^2.5.0-alpha.0",

I might forget something ?
I tried to :

publish with "individually : true"
add :  useServerlessTraceTarget: true

Thank you!

Just figuring that out the thread : https://github.com/danielcondemarin/serverless-next.js/issues/236#issuecomment-558512823 was the best answer

@CyrilleFormont you're using the serverless-nextjs-plugin which I'm not maintaining anymore. See https://github.com/danielcondemarin/serverless-next.js#getting-started for how to use the serverless component instead. useServerlessTraceTarget will only work with the component, not the plugin.


Fix upstream dev ci

The upstream dev build has been failing for a while. This is an attempt to fix it.

[x] Closes #286
[x] Passes black .

Im just going to merge this, since the RTD build is the only thing not done yet, and I did not change anything in the docs.

Im just going to merge this, since the RTD build is the only thing not done yet, and I did not change anything in the docs.


Problem address with RepeatedLabelError

1750 SW West Point Ct, Portland, OR, 97201
I've noticed that the most frequent false failures I run into happen with two or more word street names, particularly if the street name contains a directional keyword.

Same situation with 1234 SAN JUAN RD NE


[INTERNAL] Minifier: Use workerpool for terser

Rebased and refactored for ESM in https://github.com/SAP/ui5-builder/pull/875


migration testing: 1000 random processes

migrate 1000 random processes for first mass test. Make random checks for correctness

SQL query to get 1000 random processes:
select prozesseid from prozesse where IstTemplate = false order by rand() limit 1000;

DB and EFS have been cleared for another import run


Rankingnew

Initial ranking algorithm implemented
Comment out autocompletion for now

I've made some code level comments. It would be also useful for you to add in Class level Javadoc for the time being. It means that classes are documented and available for use as developer docs.

Thanks, I will revise it and submit the revision together with another branch. For now, I will just close this one.


Lower the OSX deployment target and drop Python 3.7

Also use a more modern cibuildwheel.

It's actually a bit of a misleading degree of specificity. Because cibuildwheel handles the environment of both the building and the testing and we use ~= python version so it pulls the latest patch. We probably could/should rework it a bit to make that clearer.

Oh, that's nice. Didn't catch the ~=. :tada:


rzc generate exited with code -2147450730

Using the final release of VS2019 (not preview as per docs) I get this:
rzc generate exited with code -2147450730 in :
file: C:\Program Files (x86)\dotnet\sdk\3.0.100-preview3-010431\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Microsoft.NET.Sdk.Razor.Component.targets
line :93
The error code lead me to an old (semi-unrelated) github issue which mentioned installing x86 onto x64 box - and swapping to x64 sdk fixing...
I had unintentionally installed the x86 .net core preview 3.x - so took that off, installed the x64 SDK, reboot etc... created brand new project - still get the same error:
rzc generate exited with code -2147450730
cannot proceed...

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

ID: dbdcc295-2262-311c-99d4-7ece67c5f6ed
Version Independent ID: 20152398-0971-0302-21f8-b17308f02183
Content: Get started with Blazor
Content Source: aspnetcore/client-side/spa/blazor/get-started.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

edit to above...  after posting that I double checked and had accidentally re-installed the x86 core preview 3 a second time.... after installing the x64 preview - this now compiles and works.
So.... rzc generate exited with code -2147450730 for me was fixed by uninstalling the x86 SDK and installing the x64 SDK

not preview as per docs

btw - Thanks for letting me know about that. I'll patch it up.

rzc generate exited with code -2147450730

See :point_right: https://github.com/aspnet/AspNetCore/issues/8755
Don't close this tho ... It will auto-close when I update the "preview" language in the topic on the PR.

Cool ... glad it had a happy ending.
Leave this open ... it will auto-close shortly.


ADD support for enum-casting of type field

With this PR, users will be able to make use of this trait also if the type column is casted to an Enum instance.
In one of my projects, for example, I have the following situation, where UserType is a backed enum holding possible values.
class User extends Authenticatable {
    protected $casts = [
        'type' => UserType::class,
    ];
}

When creating a new model instance Laravel resolves the cast providing the proper Enum instance, leading to an exception being thrown in classFromAlias where the $aliasOrClass is not a simple string, but the Enum instance.

I hope that too 😉

Any idea if/when this might be merged? Would love to switch from our custom solution to this package but we need Enum support too.

@marcoguido @lorenzolosa @binaryfire Tagged at 1.3.4
Thanks @marcoguido 🙌


feat: adds dot file default for rules

Implements: https://github.com/krupa-dev/manplan/issues/2

Closed in favour of #4


the tabs do not get whitelisted

tab:
  default:
    priority: 0
    commands:
      - "/spawn"
      - "/leave"
      - "/addbounty"
      - "/lobby"

blocked_command_default_actions:
  - "message: &8[&b&lECB&8] &cYou don't have permissions to use that command."
use_commands_as_whitelist: false
commands:
  - "/sad"
  - "/bukkit:?"
  - "/bukkit:ver"
  - "/bukkit:version"
  - "/bukkit:pl"
  - "/bukkit:plugins"
  - "/bukkit:help"
  - "/bukkit:about"
  - "/ver"
  - "/version"
  - "/plugins"
  - "/pl"
  - "/minecraft:me"
  - "/about"
  - "/icanhasbukkit"

the tabs on default (spawn , leave , ...)  do not get whitelisted and i have no idea why
paper 1.8 + waterfall also using ecb (tried on that too)

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Are those commands registered by another plugin? When you are OP, can you see those commands in the tab completion?


Un-pin dependencies

Change description
FSD-utils is a library package meant to be installed in a variety of
other applications.
Those applications may themselves require other/specific versions of
dependencies. This library should be compatible with as many variations
of dependencies as possible so that it can be installed in all of our
apps with minimal risk of compatibility issues.
So we should not be pinning specific versions here, and instead just say
what range of dep versions should be compatible.

[ ] Unit tests and other appropriate tests added or updated
[ ] README.md, CHANGELOG.md and other documentation has been updated / added (if needed)
[ ] Commit messages are meaningful and follow good commit message guidelines (e.g. "FS-XXXX: Add margin to nav items preventing overlapping of logo")

Yeah, that would be a good thing to do 👍


AttributeError: 'NoneType' object has no attribute 'output'

Hi,
Thnks for your good job.
I am trying to run the VGG_deconv.py flowed the README.  When I was loading the weight, I have encountered issue that
File "VGG_deconv.py", line 173, in
model = load_model('./Data/vgg16_weights.h5')
File "VGG_deconv.py", line 86, in load_model
model = VGG_16(weights_path)
File "VGG_deconv.py", line 72, in VGG_16
model.load_weights(weights_path)
File "/home/zhuwei/anaconda3/envs/theano2/lib/python2.7/site-packages/keras/models.py", line 719, in load_weights
topology.load_weights_from_hdf5_group(f, layers)
File "/home/zhuwei/anaconda3/envs/theano2/lib/python2.7/site-packages/keras/engine/topology.py", line 3056, in load_weights_from_hdf5_group
layer_names = [n.decode('utf8') for n in f.attrs['layer_names']]
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "/home/zhuwei/anaconda3/envs/theano2/lib/python2.7/site-packages/h5py/_hl/attrs.py", line 60, in getitem
attr = h5a.open(self._id, self._e(name))
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "h5py/h5a.pyx", line 77, in h5py.h5a.open
KeyError: "Can't open attribute (can't locate attribute: 'layer_names')"
So I replaced the  vgg16_weights.h5 with vgg16_weights_th_dim_ordering_th_kernels.h5 from https://github.com/fchollet/deep-learning-models/releases eliminated the error. And can run the forward pass. But I encountered another issue that
Traceback (most recent call last):
File "VGG_deconv.py", line 184, in
plot_deconv(img_index, data, Dec, target_layer, feat_map)
File "/home/zhuwei/visualization/DeepLearningImplementations/DeconvNet/utils.py", line 404, in plot_deconv
X_deconv = Dec.get_deconv(data[img_index], target_layer, feat_map=feat_map)
File "/home/zhuwei/visualization/DeepLearningImplementations/DeconvNet/KerasDeconv.py", line 187, in get_deconv
X_out = self._backward_pass(X, target_layer, d_switch, feat_map)
File "/home/zhuwei/visualization/DeepLearningImplementations/DeconvNet/KerasDeconv.py", line 135, in _backward_pass
"Invalid layer name: %s \n Can only handle maxpool and conv" % target_layer)
ValueError: Invalid layer name: conv2d_13
Can only handle maxpool and conv
I change the layer name since that was defined in the new weight files. Can you give me some hint what's going on?

It's caused by a change in the keras API.
This code was written at the time of keras 1.xx so convolutional layers are named convolution2d_xxx. Now they are named cond2d_xxx.
At some point in KerasDeconv.py, there is a check on the layer name, which does not recognize conv2d. So the simple fix is to change the check to something like if "conv2d" in layer_name instead of if "convolution2d" in layer name.

That problem solved. I replaced all the convolution2d with conv2d and maxpooling2d with max_pooling2d. Thanks a lot! Still, there are some other issues caused by the API version mismatch. Finally I installed the Keras API 1.2. And I can get the results.


Is it possible to get a public image?

The image in the statefulset is set to ghcr.io/hnts/vulnerability-exporter:v0.1.1. But it cannot be pulled.

I made a mistake and didn't set the image to public.
I've changed it to public now!

Thanks! I can pull it and will try your exporter.


Running Migrations with es modules

Describe the bug
There is no way of running migration using the CLI with es modules.
Stack trace
mikro-orm migration:create --initial

Create new migration with current schema diff

Options:
  -b, --blank    Create blank migration                                [boolean]
  -i, --initial  Create initial migration                              [boolean]
  -d, --dump     Dumps all queries to console                          [boolean]
  -p, --path     Sets path to directory where to save entities          [string]
  -v, --version  Show version number                                   [boolean]
  -h, --help     Show help                                             [boolean]

Error: No entities found, please use `entities` option
    at Configuration.validateOptions (/..../mikro-es-modules/node_modules/@mikro-orm/core/dist/utils/Configuration.js:169:19)
    at new Configuration (/...l/mikro-es-modules/node_modules/@mikro-orm/core/dist/utils/Configuration.js:24:18)
    at Function.getConfiguration (/.../mikro-es-modules/node_modules/@mikro-orm/core/dist/utils/ConfigurationLoader.js:55:20)
    at async Function.getORM (/.../mikro-es-modules/node_modules/@mikro-orm/cli/dist/CLIHelper.js:19:25)
    at async Function.handleMigrationCommand (/.../personal/mikro-es-modules/node_modules/@mikro-orm/cli/dist/commands/MigrationCommandFactory.js:88:21)

To Reproduce
Steps to reproduce the behavior:

Clone this repo repo

Expected behavior
I would like to be able to run migration-create --initial.
Versions

Dependency
Version

node
17.3.0

typescript
4.5.4

mikro-orm
5.0.0-dev.604

your-driver
postgres

I believe you can't use folder based discovery if you want native ESM. In other words, you can't use env vars for the CLI as that implies folder based discovery - you will need a CLI config file where you use entities: [A, B] just like in your app.

I believe you can't use folder based discovery if you want native ESM. In other words, you can't use env vars for the CLI as that implies folder based discovery - you will need a CLI config file where you use entities: [A, B] just like in your app.

Will try it out. Thanks.
Didn't work tho, but I see i can do `await connection.getMigrator().createMigration('./src/migrations/', false, true); and that works.
I think i'll just give up on this es-modules thing ( and just downgrade some of the projects that have moved to esm ) since that is the sole reason i am even trying this out.

right, i remember now, we compile the code to CJS, so effectively we still have require calls there even tho not in the TS source code

Yeah that's that. I remeber reading about something that you added via gen-esm-wrapper. Can that be used in any way ?

Yeah that's that. I remeber reading about something that you added via gen-esm-wrapper. Can that be used in any way ?

That has a different purpose, to allow using named imports. To support dynamic imports we will need to wait for TS 4.6+ most probably, as they removed the node12 thingy from TS 4.5
Maybe I could had this as part of some postprocessing - after tsc does the job, I could dynamically patch the compiled files to add the dynamic imports back to where they belong. It's ugly, but it works (used this technique on another project). Another ugly workaround is via eval.

We would have dynamic imports in the compiled ORM code, so folder based discovery would work out of box probably. So you could have just the .env file.

Just tried and it works fine for the compiled files, in CJS projects in behaves a bit weirdly but that would be workaroundable. But looks like it breaks with ts-node so it breaks tests that uses folder based discovery. I can offer doing this conditionally, based on an env var, e.g. MIKRO_ORM_DYNAMIC_IMPORTS=1.
But there is another gotcha, which is migrations. They also work with file system, and use require instead of dynamic import. But we use umzug for this, and it does not allow async callback in that place, so we can't just swap this with the same dynamic import helper. We could probably replace umzug with custom implementation, as it does not bring that much added value.
In general seems like the ecosystem is not ready yet, too many obstacles for no actual benefit (apart from being stuck on some older versions of things that moved forward of course, which sucks).

https://github.com/sequelize/umzug/issues/475#issuecomment-1011293931

In general seems like the ecosystem is not ready yet, too many obstacles for no actual benefit (apart from being stuck on some older versions of things that moved forward of course, which sucks).

yeah, maybe typescript 4.6 will have what we need. Anyways thanks for looking into this. Maybe umzug will add the async callbacks needed and maybe then it won't be a such a big change. ( providing a custom implementation is really not needed since we can just wait till we can use proper CJS/ESM imports ).
If you want feel free to close this and open/reopen if ever needed.

actually umzug does support this, although a bit more verbose than just swapping require/import
https://github.com/sequelize/umzug/blob/ad50a474bf872480786d48e60e08f03427a9386f/examples/2.es-modules/umzug.mjs#L17-L33

Looking good!
MIKRO_ORM_DYNAMIC_IMPORTS=1
MIKRO_ORM_ENTITIES=dist/entities/*.js
MIKRO_ORM_ENTITIES_TS=src/entities/*.ts
MIKRO_ORM_MIGRATIONS_PATH=dist/migrations
MIKRO_ORM_TYPE=postgresql

I guess we also need to introduce MIKRO_ORM_MIGRATIONS_PATH_TS so it can work for ts-node too out of box with pure env CLI config too.

Looking good!

that's great !

hey Martin, i've pushed to the same repo
1st bug, if you have any kind of relation when running migrations it won't work if the extension is not specified (ex: B.js).  This happens only for migrations, no other node files. If you put the extension to .js it work tho.
2nd bug, migrations are always created in the dist folder and not in src, maybe i missed something from the commit. if you have the time, any type of help is much appreciated.

Well, we can emit the migrations to "correct place" based on the emit option, that would be minor thing. But then it will emit the TS migration to src (if you keep emit: 'ts' which is the default), while running it won't work unless you first compile it yourself - at least if you want the CLI to run compiled migrations which I believe you want, right?

I did built the code and the tried to run migrations.

at least if you want the CLI to run compiled migrations which I believe you want, right?

that's ideal yes, but i am using ts-node so i can also run the ts migrations aswell

My point is, that if you set up the CLI to run in JS context, you will need to manually compile things first. The CLI can't do this dynamically, you need to provide the configuration so it knows what it should do. To run CLI in ts-node context, you would have to adjust your package.json to enable this behaviour (that's the useTsNode thing). If I do this, I start to get things like TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /Users/adamek/htdocs/mikro-orm/mikro-es-modules/src/entities/A.ts, which I believe is the broken ts-node support I was referring to above.
Note that I am able to get around that by using this:
node  --experimental-specifier-resolution=node --loader ts-node/esm ./node_modules/.bin/mikro-orm migration:create --initial

So again, I can offer the fix of where TS migration gets generated, with that you can generate TS, compile to JS and use the CLI to run the JS migrations. Will ship that in a minute.

const storage = new AsyncLocalStorage<EntityManager>();

Btw there is also no point of handling the ALS context explicitly, as ALS is used by default in v5.

This works really good, thanks !

Hey Martin,
I've run into problems again 😢. Running the same repo on windows will give this error.
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs.

After some debugging it seems it fails here
async getEntityClassOrSchema(path, name) {
        const exports = await Utils_1.Utils.dynamicImport(path);

And the error most likely comes from return Function(`return import('${id}')`)();.
This esm modules.. 😵💫
I would assume it needs to be somehow relative when using windows and es modules since absolute paths are not supported on windows. issue


Move group sample methods to SW/TE ModelParameter

Description

There are no breaking changes, but now users can use their own implementation of sample().
I did not add unit tests because it's difficult to test randomness.

closes: #308

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Linked to GitHub issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[ ] Wrote unit tests
[x] Updated relevant documentation in the code
[x] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[x] Re-reviewed Files changed in the GitHub PR explorer

@Pratyush ?

Since we don't want to allow customization of sample(), I scaled down the changes to only make a small refactor.

Never mind


Demo example link throwing 404

Looks like the demo example link is throwing a 404.

Which browser are you using?

Latest ver. of Chrome/Firefox.
The demo is available again, must have been something temporary.


Obsolete models gallery cleanup

Updated all_models.json with latest list of models
Removed 160x160, 192x192, 224x224 models from all_models.json
Removed models not in their respective image size pareto from all_models.json

Moved the models back to their previous location. Updated the .json file accordingly.


Smoothing improvement (small)

@redPanther
If you may have some time later, there is a small issue now. If you use the backlight option it is much more noticebale.
The smoothing should stop the output not immediately after "no change" -> stop output trigger.
It would be better to keep the output flow -until- the configured smoothing time is reached.
If you have a fast color change: the leds "hang" in a smoothed state between for example blue and black. (If you go from a blue to a black picture)
Thank you

The output is not stopped imidiatly, but perhaps we have to double the time ....
I'm thinking about a qtimer trigger for about 10 seconds + 2* smooth time.
I'm not satisfied with the modification I've made in the past. For my taste it is better always send in a defined frequency, regardless if there is new data or not. If the leds receives noise from somewhere, the leds would be refreshed and set to its last state. The current implemention wouldn't do that.
Perhaps an option to enable continous led refresh would be the best. I'll have a look ....

whats your smoothing settings? problems occured when updateDelay>0. Hopefully this is resolved now

update delay is 0.
That you delay the output explains why it is more a very light blue, instead something in between (a brighter blue - hald black half blue)

when delay=0 then my latest fix won't work. I disable writing to leds, when smoothing gets no new input.
problem for delay>0 was that the buffer wasn't flushed. e.g. if delay=10, then output stopped 10 frames before input stops. This should work now.

just a small report, i could easy recreate the issue when using kodicheck. If the state switches from background-effect to "grabbing" but the player is in pause mode. You see very good the effect mood blobs. We should enable continous as default.

This is done


python wont open for coding

python will not open when i open rocket league so i cant code my bot

thats not how its works

watch this: https://www.youtube.com/playlist?list=PL2MGDOTjPtl8fuoXmqxTmASW1ZtrPEXQ2


Validate dynamic-configuration value while updating or init

Motivation

Right now, broker doesn't validate dynamic-configuration value before updating it to zookeeper. So, user may update configuration with typo.
also, broker should validate dynamic-config value while starting in order to avoid picking up invalid value.
eg: if someone has dynamic-config present for loadManagerClassName in old release and release-1.19 has changed the className then broker startup should notify invalid config value.

Modifications

Do dynamic-config validation before updating it
Validate dynamic-config value on broker startup
Right now, we just have validation on loadManagerClassName configuration.

Result

broker will not allow update of invalid dynamic-config
broker startup will fail if it finds out invalid dynamic config.

retest this please

retest this please


Editing UI

Closes #14 .

@JakobVogelsang I fixed up the tests, this is ready for review now.

@JakobVogelsang nvm, I'm merging this after internal review from an acquaintance with some adapted changes incorporated. The regression tests have been verified to run on other platforms.


Function Not Called :  on ALFWorld code not execute 'solution_func'

Thank you for sharing your code.
I'm applying this code to query the DBMS.
However, I found that the current code does not execute the 'solution_func' because it only defines the function but does not call it.
Here is the code reference: link to code
I temporarily solved this issue with the following change:
execute = solution_func+'\nprint(solution(agent, start_from='+str(step)+'))'
exec(execute)

Sorry, I initially thought that line was supposed to execute the function, but I realized it only 'defines' the function and then executes it later in capture_output.
The issue was that capture_output couldn't find 'solution' because exec() was being called within a try block. I fixed it by changing the line to:
try:
            exec(solution_func, globals())

and that solved the problem.


Demo projects in IE

Hello,
I am currently learning to use the SBA functionality in Sinequa, and I seem to have walked upon an issue when running the vanilla-search app in IE.
I have carefully installed all the necessary dependencies to use angular in IE11, and I also made the appropriate modifications in the tsconfig.json file, but I get the error below when I serve the vanilla-search project in IE11.

This error is specific to the vanilla-search project, it doesn't appear in the hello-search project or any other angular projects I created.
I thought it might be a missing polyfill for a the implementation of a specific "for" loop in IE11, so I imported the full "core-js" package, but this didn't fix it.
EDIT: After careful investigation and debugging, I could find that the modules below are the ones that are causing IE to bug.

"@sinequa/components/baskets"
"@sinequa/components/facet"
"@sinequa/components/heatmap"
"@sinequa/components/metadata"
"@sinequa/components/preview"
"@sinequa/components/result"
"@sinequa/components/saved-queries"

Thank you for reporting this. We have noticed similar problems with IE, but these bugs are a bit random and depend on the exact version you are using, so they are very hard to solve.
One thing for sure: ng serve does not support the differential loading feature that is needed for IE (See https://angular.io/guide/deployment#local-development-in-older-browsers). So you can either customize your serve target or just use ng build to test your app in IE.

Thank you for your answer, indeed it works fine with an ng build, so I will test the application like this in IE, as you recommended.


Update Changelog ahead of major set of breaking changes

This PR is a proposal for a release that would contain several breaking changes.
If this PR is approved, the following PRs will be merged, and a new release will be cut:

#364
#370
#371
#372
#397
#429

I believe these changes represent all of the breaking changes that have been agreed upon. However, the overall effort to align this library with the logs data model will include some additive changes, such as enhancements to field syntax.
Additionally, #431 would be a notable breaking change but has not yet been agreed upon. Implementation of that depends on the enhancements to field syntax, and so may take a couple weeks. I'm inclined to cut this release sooner and if necessary a second breaking release in a couple weeks.
cc: @tigrannajaryan @jsirianni @pmm-sumo @dmitryax

Do we have a chance to make all the changes (or at least some of them) in a backward compatible way whenever it's feasible?
For example, can https://github.com/open-telemetry/opentelemetry-log-collection/pull/364 support both $body and body for now, throwing warning if it's configured with $?

Also it seems like we are accumulating all of them for one release. What is the reason for that? As a user, it would rather prefer adopting smaller amount of changes between upgrades rather than all at once, but others may not agree with me.

Also it seems like we are accumulating all of them for one release. What is the reason for that? As a user, it would rather prefer adopting smaller amount of changes between upgrades rather than all at once, but others may not agree with me.

This strategy was agreed in the Log SIG several weeks ago. I see tradeoffs either way, but I think this is the right approach. The risk with several consecutive breaking changes is that users have to keep revisiting and redeploying, and I think many would conclude at some point that it's not worth keeping up. At least with one, they have one painful experience and hopefully don't have to keep thinking about it. Besides, I think at this point it would introduce quite some delays to spread them out over several releases (of the collector).

Do we have a chance to make all the changes (or at least some of them) in a backward compatible way whenever it's feasible?
For example, can #364 support both $body and body for now, throwing warning if it's configured with $?
Sorry for bringing it too late.

Yeah, I think that one seems reasonable. I'll confirm and update it unless I'm forgetting a reason why it can't.
I'm not sure any of the others really can be made backwards compatible. I suppose technically #372 can add config flags and deprecate the old ones, but I think it's not worth it in that case.

I think it would be nice to write a quick doc somewhere showing how to update existing configs. I would be happy to help with this, I am not sure where this doc would live. Perhaps the changelog / release.
Example:

$body --> body
how to handle entry.Timestamp now that it does not have a default
restructure --> add / move / etc
etc

@jsirianni, that's a good idea. I tried to be verbose in the changelog, but something more end-user oriented would be great. If you want to rough out how you think that info would be best presented, I'm happy to help fill in the details. I think the best place for this info would be on the release page.

I've updated #364 to allow the former syntax as well. Unfortunately, there's not a great way to complain about the deprecated usage because it is processed during unmarshaling, where we don't yet have a handle to a logger.

@jsirianni, here is my draft for a special section at the top of the release notes. PTAL
Upgrading to version 0.90.0
Several changes have been made that affect configuration for the filelog, syslog, tcplog, udplog, and journald receivers.
Update all usages of field syntax
Field syntax no longer requires uses the $ character. Instead each field must begin with body, attributes, or resource.

Deprecated ExampleUpdated Equivalent

$attributes.["log.file.name"]

attributes.["log.file.name"]

$resource.["host.name"]

resource.["host.name"]

$body.foo

body.foo

$.foo

body.foo

foo

body.foo

Replace usages of restructure operator
The restructure operator has been removed. Use add, copy, flatten, move, remove, and retain operators instead.

Deprecated ExampleUpdated Equivalent

operators:
  - type: restructure
    ops:
      - add:
        field: set_me
        value: foo
      - add:
        field: overwrite_me
        value: bar
      - move:
        from: details.env
        to: env
      - remove:
        field: delete_me

operators:
  - type: add
    field: body.set_me
    value: foo
  - type: add
    field: body.overwrite_me
    value: bar
  - type: move
    from: body.details.env
    to: body.env
  - type: remove
    field: body.delete_me

Replace usages of metadata operator
The metadata operator has been removed. Use add, copy, or move operators instead.

Deprecated ExampleUpdated Equivalent

operators:
  - type: metadata
    attributes:
      environment: production
      file: 'EXPR( $body.file )'
    resource:
      cluster: blue

operators:
  - type: add
    field: attributes.environment
    value: production
  - type: copy
    from: body.file
    to: attributes.file
  - type: add
    field: resource.cluster
    value: blue
  - type: move
    from: body.foo
    to: attributes.bar

Update filelog attribute references
The filelog receiver has adopted slightly different attribute names in order to match newly established semantic conventions. Configurations that previously refered to the file.* attributes should be updated.

Deprecated AttributeUpdated Equivalent

file.name

log.file.name

file.path

log.file.path

file.name.resolved

log.file.name_resolved

file.path.resolved

log.file.path_resolved

Note to Vendors: A log record's Timestamp field may now be nil
A recent change to the Log Data Model has redefined the usage of the Timestamp field. Correspondingly, this field is no longer initialized by default. All Log Exporters should be evaluated to ensure this change is handled accordingly.
Log exporters can use the following logic to mimic the previous funcationality (psuedocode):
timestamp := log.ObservedTimestamp
if log.Timestamp != nil {
  timestamp = log.Timestamp
}

@djaglowski looks great, exactly what I had in mind.

@open-telemetry/log-collection-approvers, PTAL. Any additional feedback on this proposal? Can we move forward?
I would like to merge these PRs starting Wednesday if there are no objections.

Good catch @tigrannajaryan. Fixed.

LGTM.
@dmitryax you had concerns about this change, PTAL.

All prerequisite PRs are now merged.
Before this release is cut, I would like to call attention to the one remaining proposal that would be a breaking change. If #431 is accepted, it will ultimately require some users to perform a second update to their configurations. In many cases this will apply to lines that have just been updated due to this release. If this churn is coming and can be avoided, I think it is worth a slight delay in this release.
# Pre-v0.28.0 Config
parse_from: sev

# Post-v0.28.0 Config
parse_from: body.sev

# Config if #431 is accepted
parse_from: attributes.sev

At this point, being late in the week, I'd like to release on Monday so I can be more available to support upgrading users.
In the meantime, I would appreciate any additional thoughts on #431. I will work ahead on the implementation in case consensus can be reached quickly. We can update/validate the release timeline on Monday.
cc: @tigrannajaryan, @dmitryax, @jsirianni, @pmm-sumo

I will cut this release this afternoon.


Corrects mistaken async items in AirVisual

Description:
The AirVisual platform was incorrectly using asyncio (given that the underlying library doesn't utilize it) – the updates were fast enough to not mess with the scheduler too much, but still, it wasn't correct and could exacerbate things over time. This adjusts the platform to use the backwards-compatible API.
Related issue (if applicable): N/A
Pull request in home-assistant.github.io with documentation (if applicable): N/A
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: airvisual
    api_key:<PHONE_NUMBER>
    monitored_conditions:
      - us
    show_on_map: false

Checklist:
If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

@pvizeli: A remnant from my more naive days. 😆


Library Management System

Library management is a project that manages and preserves electronic book data based on the demands of students. Both students and library administrators can use the system to keep track of all the books available in the library. It allows both the administrator and the student to look for the desired book. The C files used to implement the system are: main.c, searchbook.c, issuebook.c, viewbook.c, and more.

hi

please help me sir


Fix crash on Android with TLSv1 disabled

Motivation
Our application runs in an Android 4.2 environment where TLSv1 has been disabled for security compliance. The recent code change in #14245 enables TLSv1 in all environments, without first checking to see if that version of the protocol is supported. This causes an exception:
FATAL EXCEPTION: OkHttp Dispatcher java.lang.IllegalArgumentException: protocol TLSv1 is not supported                                                                              at org.apache.harmony.xnet.provider.jsse.NativeCrypto.checkEnabledProtocols(NativeCrypto.java:569)                                                                              at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl.setEnabledProtocols(OpenSSLSocketImpl.java:782)                                                                              at com.facebook.react.modules.network.TLSSocketFactory.enableTLSOnSocket(TLSSocketFactory.java:74)                                                                              at com.facebook.react.modules.network.TLSSocketFactory.createSocket(TLSSocketFactory.java:49) <... remaining stack omitted for brevity...>
Test Plan
I rebuilt the app with a patched version of React Native 0.50, and it runs successfully.
Related PRs
#14245
Release Notes
[ANDROID] [BUGFIX] [Network] - Enable TLSv1 only if supported by the OS

Closing this PR because it is not merging to master. Replaced by #17309 .


Issue: Fix ESLint errors in project

The project build have several ESLint errors and warnings.
To Reproduce:

Run the build process using:npm run build

Observe the build fails due to the above issues.

Acceptance Criteria:

The build process runs successfully without any ESLint errors or warnings.
Unused variables are removed or utilized in the code.
Missing dependencies are addressed in useEffect hooks.

@vaibhavyadav-dev I can check this one

Hi @vaibhavyadav-dev can this issue be assigned to me?

Ok @Vixs101 ! you can take this issue.

@kalyan90 try to find bugs in this project, you've to be fishy, or is there something you think you can add new feature if there is, raise issue, get assigned and start working on it.


Email diff author instead of commit author in case build fails

Currently, whenever the build fails, an email is sent to the author of the last commit on which diff was applied, instead of the diff author. It'd be useful to email diff author who is more likely to understand what went wrong.
One example of where this happens is when the diff doesn't apply cleanly.
Update:
I forgot to mention that the emails are sent from Jenkins Mailer Plugin when Send separate e-mails to individuals who broke the build is enabled.

I'm not sure this is something that's fixable by the plugin, since the Jenkins mailer is reading your git history, and if you're applying the patch then jenkins thinks the commit being tested is actually master.
A failure applying the patch should be causing a harbormaster failure, and optionally you can have Jenkins post a comment with failures.


build: more stringent gold checks

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

This is the only site which allowed you to accidentally accept gold for targets
which are not ELFish.  For the time being, we can only add unit tests for the
host variant, so use the SWIFT_HOST_VARIANT_SDK to determine the target file
format.  This will make supporting cross-compiling to non-ELFish targets
simpler.

@swift-ci Please test and merge

Failure is related to the changes that @gottesmm did.

I think that this can be retested now.

@swift-ci Please test and merge


Timed out connections are not closed

Environment
HikariCP version: 3.1.0
JDK version     : 1.8.0_171
Database        : PostgreSQL
Driver version  : 42.2.5

My goal is to make sure that API calls fail in 10 seconds when database is not available. API operation makes one read call to Postgres RDS instance. Here is the Hikari Config -
HikariConfig hikariConfig = new HikariConfig();
hikariConfig.setJdbcUrl("*******");
hikariConfig.setUsername("******");
hikariConfig.setPassword("********");
hikariConfig.setDriverClassName("org.postgresql.Driver");
hikariConfig.setMaximumPoolSize(10);
hikariConfig.setConnectionTimeout(10000);

I restarted the database instance in the middle of performance testing and API calls started to fail after 10 seconds which was as expected. Problem was that timed out connections were returned to the pool and many calls failed after database was available after reboot. It was a force failover so different RDS instance (different IP) was master after reboot.
HikariPool-1 - Timeout failure stats (total=10, active=10, idle=0, waiting=189)
HikariPool-1 - Connection is not available, request timed out after 10000ms.

Java Exception -
org.springframework.transaction.CannotCreateTransactionException: Could not open JPA EntityManager for transaction; nested exception is org.hibernate.exception.JDBCConnectionException: Unable to acquire JDBC Connection
I am using spring-data-jpa-1.11.4.RELEASE and repository interface -
@Transactional(readOnly = true)
public interface XXRepository extends JpaRepository<SomeEntity, String> {
    SomeEntity findById(String id);
}

Is there a way to close the connections from the pool after they time out and create new connection objects?
⚠ Please verify that your issue still occurs on the latest version of HikariCP before reporting.

Have you searched the CLOSED issues already? How about checking stackoverflow?

HikariPool-1 - Timeout failure stats (total=10, active=10, idle=0, waiting=189)
@brettwooldridge active connection count remained 10 while database was down and getConnection call was throwing timeout exception.

@brettwooldridge Thanks. I tried setting socketTimeout as connectionProperties with Apache DBCP and it worked.
Should I pass it as data source property with Hikari? Or pass it in jdbc url?
hikariConfig.addDataSourceProperty("socketTimeout", "10000");

@brettwooldridge I tried following configuration and it worked.
hikariConfig.setConnectionTimeout(TimeUnit.SECONDS.toMillis(5));
 // Add Postgres Driver level properties in seconds
hikariConfig.addDataSourceProperty("socketTimeout", 5);
hikariConfig.addDataSourceProperty("connectTimeout", 5);

@tiwarivikash I always recommend using datasource properties for readability.  Long JDBC URLs with lots of options are difficult to manage and understand.


Highlight 'NetworkConfig' capability in manifest must be set to true before call Networking_SetInterfaceState API

The only place mentioned is in Networking_SetInterfaceState API reference part of document. Should provide all information in this single page to guide customer setup ethernet

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

ID: a3781077-8806-0de8-85c1-a0e08b3abe8c
Version Independent ID: f53b30fb-3874-c03e-bb5e-ab194b15fc53
Content: Connect Azure Sphere to Ethernet
Content Source: AzureSphere/articles/network/connect-ethernet.md
Product: azure-sphere
GitHub Login: @pennyo
Microsoft Alias: azurespheredocs

@xiongyu0523 Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

We will add this information in an upcoming release of the documentation.

@pennyo Thanks for the confirmation.
@xiongyu0523 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


project.yml mistype error

getting 500s from when calling ".../projects/jobserv/builds/../project.yml"

there's something else with this route that is a little off to me. The function signature has two parameters but I only see one from the route. Maybe this is provided elsewhere, so this "fix" may still hit some issues.
@blueprint.route('/builds/<int:build_id>/project.yml', methods=('GET',))
def build_get_project_definition(proj, build_id):

The "proj" parameter is in the blueprint itself: https://github.com/foundriesio/jobserv/blob/478b876018e6aa52262a008be91c5deb42c4fe8a/jobserv/api/build.py#L14

can you fix this line also:
https://github.com/foundriesio/jobserv/blob/master/tests/test_api_build.py#L63
that will get CI going. And now you know why you can't always trust test-driven-development :)

deployed to production curl https://api.foundries.io/projects/lmp/builds/422/project.yml works.


Create Cryptol implementation

Convert beamsplitter to an implementation in Cryptol
See related paper for context

Github link to Cryptol


Stylecop.MsBuild not adding target/import correctly

I manually added an ImportGroup to the csproj file. If I now install the Stylecop.Msbuild nuget package it will add its own 'Import Project' into this group causing it to not be executed as a build target.

+1