Update dependencies

Due to its very specific dependency requirements (exactly equal to specific subversions), this library is starting to become incompatible with other libraries in the ML space. I propose to follow the convention of only requiring a specific major version, and allowing the package manager freedom to decide on the minor version. I don't see specific reasons why OCTIS is not compatible with higher minor versions of gensim, scikit-learn and numpy.

Thank you for reviewing and approving these changes. I do not have write access to this repo, so I cannot perform the merge myself.

I am also facing an issue with the dependencies, and this PR seems to solve them. I think it would solve #114 as well.
@silviatti, if you have a moment, can you have a look and merge it?
Thanks a lot!

Speaking up again to sa that I am facing this issue and merging this PR would be really helpful!
@silviatti or @pietrotrope could you please have a look at this.
I excited to be able to try this properly in my project.

@silviatti or @pietrotrope
Can we please merge this PR?

Hey everyone, thank you for your patience. I couldn't merge this PR because the tests were failing. However, I have fixed the dependencies in a separate branch and merged this into master today (pip install octis==1.14.0 should do the trick). Please let me know if have any issues with the dependencies and I'll try to address them. Finding the right combination wasn't trivial :) I'll close this PR for now

Did this really end up fixing dependency issues for everyone? Still seeing related w/ python 3.12.7 even while installing octis==1.14.0, specifically:
AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you mean: 'zipimporter'?

as previously resolved by Yfke's PR


⚠ ClamAV has degraded performance

In 357f117, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 209 ms

Resolved: ClamAV performance has improved in eff7806.


pynitrokey: 0.4.36 -> 0.4.37

https://github.com/Nitrokey/pynitrokey/releases/tag/v0.4.37
Fixes fido2 list-credential issues with missing name of relying party.
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 234023 run on aarch64-linux 1

2 packages built:

pynitrokey
pynitrokey.dist


testing pull request with updated readme

Hi @katya450
Not sure what the purpose of this pull request other than testing.
Can I close this?

Sure, close it! Sorry about that :-)
//Katja
On Tue, Jul 4, 2017 at 12:45 PM, Dharmanshu Singh<EMAIL_ADDRESS>wrote:

Hi @katya450 https://github.com/katya450
Not sure what the purpose of this pull request other than testing.
Can I close this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dsingh07/adop-doa-materials/pull/3#issuecomment-312834435,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ5jflM5my-iUVYHt9yrFKYZbPXEwa4rks5sKgm3gaJpZM4OMbRL
.


Duplicate meters after initial setup

This attempts to resolve the issue of duplicate meters appearing after initial setup.
Some inverters do not provide stable meter model and serial number information for unknown reasons. Unfortunately choosing to base the entity Unique ID on either of these values causes new entities to be created if the inverter suddenly reports different values.
The issue has not been observed in the inverter information, so this PR changes the Unique ID for meter entities to be based on the parent inverter's model and serial number.

I'm also applying the same change to battery Unique ID. Even though there haven't been any reports that the battery device info is unstable, I don't want to take the chance and have to do another breaking release.
Because the Unique ID changes this will be a breaking release v2.2.0.
Recommended upgrade procedure:

Delete integration from Settings -> Devices & Services.
Update to v2.2.x release (manually or through HACS).
Add the integration under Settings -> Devices & Services.

This procedure will preserve entity names. If updated in place, any existing entities with the updated Unique ID will have a _2 suffix.


upgrade deps and run through cargo.toml through prettier

mostly making this pr to confirm that the build is fixed, since the important update would happen automatically

@jbr sorry for not catching this before I made other changes... could you rebase this?

May be worth bumping isahc, which hit 1.0 (now 1.1), again before this is merged! :)


request: scene challenge tracker

ref: ironsworn, p. 234.

pretty much a progress track with the countdown track bolted on. the countdown track is 4 boxes, and unlike normal progress boxes it's either filled or not. it'd also be good to make the visually distinct from normal progress boxes. i reckon  :green_square: :green_square: and :negative_squared_cross_mark: :negative_squared_cross_mark: would work for that.
scene challenges default to the Dangerous rank, and the text strongly recommends keeping them there unless there's a very compelling reason it should be otherwise. so i think it would make sense for the command to default to Dangerous in the absence of a specified rank
emoji reacts as per progress tracks, with the addition of :negative_squared_cross_mark: :negative_squared_cross_mark: to mark the countdown track, and perhaps :green_square: :green_square: to remove it (to my knowledge there's no mechanic that removes marks from the countdown track, but it's probably a good idea to make it reversible in case someone misclicks)

Added in commit 94f25ad
Closing.


chore(deps): update common-dev-assets digest to b7148db

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
9403075 -> b7148db

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

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

GitHub release
v1.2.4

Your semantic-release bot :package::rocket:


EKS Addon: IsUpToDate loop does not work as expected

What happened?
The isUpToDate function does not work as the result is always true (i.e. different AddonVersion).
The referred line: https://github.com/crossplane/provider-aws/blob/96a15aa76c5060da9769605acb4a3824ec521d0f/pkg/controller/eks/addon/setup.go#L133
What environment did it happen in?
Current master (96a15aa76c5060da9769605acb4a3824ec521d0f)

fixed & implemented via https://github.com/crossplane/provider-aws/pull/1068


C applications compiled with playground do not run with qemu

When I try to run a C application compiled with the method described in this repository with qemu, I always get the error message below.
The application runs without any error when using uhyve.
I am not sure if this is a bug or just not supported (yet). However , it would be great to be able to use qemu, as uhyve behaves not exactly the same and/or lacks of debugging messages in certain cases.
$ qemu-system-x86_64 -display none -smp 1 -m 64M -serial stdio  -kernel /path/to/rusty-loader -initrd /path/to/application -cpu qemu64,apic,fsgsbase,rdtscp,xsave,xsaveopt,fxsr
[LOADER] Loader: [0x100000 - 0x335018]
[LOADER] Found Multiboot information at 0x9500
[LOADER] Found module: [0x337000 - 0x4e0e20]
[LOADER] Module length: 0x1a9e20
[LOADER] Found an ELF module at 0x337000
[LOADER] Map 201 pages at 0x337000 (page size 4 KByte)
[LOADER] Map 1 pages at 0x400000 (page size 2048 KByte)
[LOADER] Allocating 0x70 bytes at 0x132D80, index 0
[LOADER] Allocating 0x4C8 bytes at 0x132E00, index 128
[LOADER] PANIC:
[LOADER] src/lib.rs:149:
[LOADER] assertion failed: elf.header.e_type == elf::header::ET_DYN
[LOADER]

It should now work. I updated the loader to support Qemu.


Inheritance + class variable + method missing = compiler error

The code:
http://play.crystal-lang.org/#/r/ak0
It breaks down on the second instantiation since typeof(@child) changes from Child to Parent and I suppose the compiler doesn't know which classvar to expect anymore?
Was really tricky to find the cause and minimum way of reproducing from the larger codebase I'm working on. Hope we can actually get it to work apart from avoiding compiler panic.
Might be related to: https://github.com/manastech/crystal/issues/916

Yes, this is a duplicate of #916, I'll comment there.


Update to Cassandra v3.11.9

This effort is based on version 2.1 of Cassandra, which is no-longer being supported. Update to version 3.11.9 so that is synchronized with the version being used by the RDK XConf server source code.

The branch module-refactor contains an update to Cassandra version 3.11.9. As soon as testing is complete, it will be merged into the master branch.

Testing has been completed and update has been applied to master branch.


⚠ Bofrost.es has degraded performance

In 99be446, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1722 ms

Resolved: Bofrost.es performance has improved in 5f4634c after 9 minutes.


Ocaml lsp improvements

Motivation for this change
specify the dependencies of ocamllsp and jsonrpc more accurately
Things done

Dropped unnecessary dependencies for jsonrpc 1.7.0
Fixed the minimum OCaml version for ocamllsp 1.7.0
Fixed the set of dependencies ofr ocamllsp 1.7.0

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

cc @vbgl

I don’t understand the second commit.
Please double check the contribution guidelines and include the attribute path of the modified package on the first line of the commit message.

@vbgl updated the commits to follow the convention.

Thanks. The second commit still looks like obfuscation to me, but I did probably not get its purpose.


Move add_for_decode_as() out of zmtp_proto.init

I'm writing a subdissector and I noticed that every time I run Analyze->Reload Lua Plugins (Ctrl+Shift+L), I would lose the saved "Decode As..." configuration I set to enable ZMTP dissection. I assumed the plugin wasn't being reloaded correctly and noticed that the WireShark examples don't use an init function. I tried removing it and the issue is gone. I'm not sure exactly what the implications are, but I'll leave this PR for your review.

Thanks!


[BUG] Foundry v10 Door Sounds play simultaneously with v11 configured door sounds.

Module Version: v2.3.3
DnD5e 2.2.2, Foundry v11.306
This module comes with the default door sounds from v10 I think. Foundry v11 lets you choose from a list of preconfigured door sounds. For some reason when interacting with a door, I hear both sounds, both the Foundry v11 door sound, and the default door sounds from v10 that come with this module, both playing simultaneously. Disabling this module fixes it.

Yup...same here for me as well.

The sounds are from Ambient Doors. I have uninstalled Ambient Doors and am getting this issue.

The sounds are from Ambient Doors. I have uninstalled Ambient Doors and am getting this issue.

I'm not sure what you mean when you say this. The sounds are in the assets/defaultSounds folder of Arms Reach, so they're not from Ambient Doors.
Ambient Doors also is not compatible with v11 of Foundry, and so I don't have it installed either, and therefore is not related to this problem.

I dont know if its related but for me and my players the doors makes no sounds at all

Was there any fix on this? I'm still hearing double sounds.

same, any news ? it seems to also have incompatiblity with doors sound module

on my to-do list, but not in the short term, any help is welcome

For starters it helps to just delete the "\Data\modules\arms-reach\assets\defaultSounds" folder. Just be aware that on a module update that folder ist back there again.
Would be nice to have the option to disable sound integration from the "Arms Reach" Module at all.


Prettier 2.5.1 issue

Description
Prettier 2.5.1 adds value in the imports with a certain configuration (might be related to Typescript version)
https://stackoverflow.com/a/71043924/7910299
Steps to Reproduce

Expected behavior:

import { something} from './somewhere';

Actual behavior:
import { value something} from './somewhere';

Reproduces how often:

Versions

Additional Information

is there a repo that this is happening too?


Fix mongoose generation

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

v3.21.1
GitHub release

Your semantic-release bot :package::rocket:


macrobot: clear cmds on remove

Depends on https://github.com/keybase/go-keybase-chat-bot/pull/71

you can GOPROXY=direct go get -u github.com/keybase/go-keybase-chat-bot@marcel/HOTPOT-2505-remove-advertisement if you want to test locally

just refetch and go mod tidyonce the bot library is merged

Oh wow I didn't know you could do that! I've been using replace in my go.mod locally


Particle 3D Draw Pass Error

Godot version:
Godot 3.1 beta 11 and 3.1 Daily Builds
OS/device including version:
Windows 10 x64
Issue description:
ERROR: get_draw_pass_mesh: Index p_pass=3 out of size (draw_passes.size()=1)
   At: scene/3d/particles.cpp:204

Steps to reproduce:
Create a 3D particle node. add a draw pass mesh to it. then Run the project.
Minimal reproduction project:
increasing the pass count to > 3 seems to "fix" the issue. must be something with the way pass counts are handle? N-1 instead of N=1?

Happens on linux too, and it is only shown on the terminal output, not on the editor's error panel.

I think the issue is that get_mesh is being called when the draw_mesh property is being registered.

It can be reproduced in the 3d/navmesh demo.
Open it, save the main scene, and this is printed to stdout:
ERROR: get_draw_pass_mesh: Index p_pass=1 out of size (draw_passes.size()=1)
   At: scene/3d/particles.cpp:204.
ERROR: get_draw_pass_mesh: Index p_pass=2 out of size (draw_passes.size()=1)
   At: scene/3d/particles.cpp:204.
ERROR: get_draw_pass_mesh: Index p_pass=3 out of size (draw_passes.size()=1)
   At: scene/3d/particles.cpp:204.

These errors started appearing in 3.1 alpha 2.

I think the issue is that get_mesh is being called when the draw_mesh property is being registered.

Most likely yes. To be clearer: get_draw_pass_mesh is called when the draw_pass_[123] properties are registered in https://github.com/godotengine/godot/blob/0fec83bc9207cfff64d5b390c94ff554210bfa25/scene/3d/particles.cpp#L373-L376


Render Whitespaces in Stackblitz Editor Filetree

Describe the bug
Hello, I encountered a rather rare issue that nearly gave me a few grey hairs. 😅
I attempted to create a Nuxt reproduction but struggled to render my pages until I identified my error.

It turns out I inadvertently included a whitespace in the directory name, which wasn't visible, causing me a significant delay in diagnosing the problem.

Link to the blitz that caused the error
https://stackblitz.com/edit/github-om7hsq-kbhgm2
Steps to reproduce

Go to the provided Stackblitz.
Look at the Filetree (./apps/web/) and look at the pages dir's.
You cannot see the used whitespace

Expected behavior
Whitespaces should be rendered similiar to vscode.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
No response
Additional context
Interestingly, in the isolated StackBlitz environment for this issue, the Nuxt terminal output was helpful. However, when I initially created the correct reproduction, there was no such message indicating the problem. This was making it even harder to find the issue.

The fix for this issue is rolling out and should be live soon.


Choosing a specific NIC when there are multiple NICs with calico and kube-vip

Details
This is advanced configuration but I figured it would be worth opening an issue to inform people how to deal with situations where your nodes have multiple active NICs and you want to choose which one Kubernetes uses.
If you nodes have different network interface names, it's advised to make the names consistent across devices. Review this question on AskUbuntu on how to make that happen.
These changes should be made prior to running task configure in the guide.
Calico
By default, attaches to the first available internet interface (https://projectcalico.docs.tigera.io/networking/ip-autodetection).
The way around this could be achieved by setting a interface name regex in the Calico Installation resource.
# ./provision/ansible/playbooks/templates/calico-installation.yaml.j2
---
apiVersion: operator.tigera.io/v1
kind: Installation
metadata:
  name: default
spec:
  calicoNetwork:
    nodeAddressAutodetectionV4:
      interface: "eno.*"
...

kube-vip
By default kube-vip choose the NIC with the default gateway. To assign a specific NIC update the configuration below.
# ./provision/ansible/playbooks/templates/kube-vip-daemonset.yaml.j2
...
          env:
...
            - name: vip_interface
              value: "eno1"
...

# ./tmpl/cluster/kube-vip-daemonset.yaml
...
          env:
...
            - name: vip_interface
              value: "eno1"
...

Perhaps we could automate this with Ansible using the CIDR for IP detection? https://projectcalico.docs.tigera.io/networking/ip-autodetection
spec:
  calicoNetwork:
    nodeAddressAutodetectionV4:
      cidrs:
        - "{{ (ansible_default_ipv4.network + '/' + ansible_default_ipv4.netmask) | ipaddr('network/prefix') }}" # <IP_ADDRESS>/24

@brettinternet how would that help when a node has multiple active NICs, and for example each nic is part of a different network?

Oh, I just mean as a default for hardware with multiple NICs but where only one is used. Otherwise I believe they'll find these Calico errors on those nodes:
[INFO][76] felix/route_table.go 1200: Failed to access interface because it doesn't exist. error=Link not found ifaceName="vxlan.calico" ifaceRegex="^vxlan.calico$" ipVersion=0x4 tableIndex=0
[INFO][76] felix/route_table.go 1268: Failed to get interface; it's down/gone. error=Link not found ifaceName="vxlan.calico" ifaceRegex="^vxlan.calico$" ipVersion=0x4 tableIndex=0
[ERROR][76] felix/route_table.go 1035: Failed to get link attributes error=interface not present ifaceRegex="^vxlan.calico$" ipVersion=0x4 tableIndex=0
[INFO][76] felix/route_table.go 618: Interface missing, will retry if it appears. ifaceName="vxlan.calico" ifaceRegex="^vxlan.calico$" ipVersion=0x4 tableIndex=0

@brettinternet this should help certain people so if you want to open a PR to add that, please do otherwise I'll get to it later.


Load key "/root/.ssh/id_rsa": invalid format

Hi, i just got this error.
here is my github actions
      - name: SSH and Deploy
        uses<EMAIL_ADDRESS>        with:
          host: myhost.com
          user: myuser
          private_key: ${{ secrets.AWS_PEM }}
          command: ls -lah

and here is my secret key.
-----BEGIN RSA PRIVATE KEY-----
...
-----END RSA PRIVATE KEY-----

Hi @Keda87,
thanks for reporting your error.
After a short research, I figured out that you might have an incompatible key format.
If your RSA key looks like this:
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: AES-128-CBC,25737CC2C70BFABADB1B4598BD8AB9E9

uTo43HGophPo5awKC8hoOz4KseENpgHDLxe5UX+amx8YrWvZCvsYRh4/wnwxijYx
...
-----END RSA PRIVATE KEY-----

You can try to convert your current RSA to a OpenSSH key or generate a new one and register it on your remote server.
The new/converted key should look something like this:
-----BEGIN OPENSSH PRIVATE KEY-----
uTo43HGophPo5awKC8hoOz4KseENpgHDLxe5UX+amx8YrWvZCvsYRh4/wnwxijYx
...
-----END OPENSSH PRIVATE KEY-----

Next replace the secret and you should be good to go.


Incorrect documentation for Pico Scroll

In the https://github.com/pimoroni/pimoroni-pico/tree/main/micropython/modules/pico_scroll It shows using the update method to display new content to the screen however in the micropython it should be show()

The demos don't seem to work with show() instead of update() either.

Looks like the docs never got updated when we rejigged things to make Scroll Pack work with PicoGraphics - I've attempted to improve things a little with #876 :)


InputSharder: borrowing Reader from img2dataset to serve as our InputSharder

WIP, will edit this so it works exactly right with current pipeline

probably fine to do exact same as img2dataset for now but note a change coming to img2dataset soon https://github.com/rom1504/img2dataset/issues/188

did in my pr


ResourceReaperException in CI/CD environment

Describe the bug
In my local environment I launch the tests without problem but in CI/CD environment where we launch the tests on a docker image  and docker in docker enabled in the host I get the following error:
DotNet.Testcontainers.Containers.ResourceReaperException : Initialization has been cancelled. StackTrace:    at DotNet.Testcontainers.Containers.ResourceReaper.GetAndStartNewAsync(Guid sessionId, IDockerEndpointAuthenticationConfiguration dockerEndpointAuthConfig, String ryukImage, TimeSpan initTimeout, CancellationToken ct) at DotNet.Testcontainers.Containers.ResourceReaper.GetAndStartNewAsync(Guid sessionId, IDockerEndpointAuthenticationConfiguration dockerEndpointAuthConfig, String ryukImage, TimeSpan initTimeout, CancellationToken ct) at DotNet.Testcontainers.Containers.ResourceReaper.GetAndStartDefaultAsync(IDockerEndpointAuthenticationConfiguration dockerEndpointAuthConfig, CancellationToken ct)    at DotNet.Testcontainers.Clients.TestcontainersClient.RunAsync(ITestcontainersConfiguration configuration, CancellationToken ct)    at DotNet.Testcontainers.Containers.TestcontainersContainer.Create(CancellationToken ct)    at DotNet.Testcontainers.Containers.TestcontainersContainer.StartAsync(CancellationToken ct)    at Tools_Core_Api_Tests.IntegrationTests.ContainerIntegrationTest.LoadData() in /datos/workspace/tools_tools-core_pipelines_developdeploy/Tools-Core/Tools-Core-Api-Tests/IntegrationTests/ContainerIntegrationTest.cs:line 28    at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter1.BlockUntilCompleted()    at NUnit.Framework.Internal.MessagePumpStrategy.NoMessagePumpStrategy.WaitForCompletion(AwaitAdapter awaiter)    at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func1 invoke)    at NUnit.Framework.Internal.Commands.SetUpTearDownItem.RunSetUpOrTearDownMethod(TestExecutionContext context, IMethodInfo method)    at NUnit.Framework.Internal.Commands.SetUpTearDownItem.RunSetUp(TestExecutionContext context)    at NUnit.Framework.Internal.Commands.OneTimeSetUpCommand.<>c__DisplayClass0_0.<.ctor>b__0(TestExecutionContext context)    at NUnit.Framework.Internal.Commands.BeforeTestCommand.Execute(TestExecutionContext context)    at NUnit.Framework.Internal.Commands.BeforeTestCommand.Execute(TestExecutionContext context)    at NUnit.Framework.Internal.Execution.CompositeWorkItem.PerformOneTimeSetUp()
I have tried to update the version of TestContainers to the one indicated in this issue but now both locally and in the CI environment I get the error:
 Docker.DotNet.DockerApiException : Docker API responded with status code=Conflict, response={"message":"Container 239e3824a1de91cab903aeecc070440ab3a7df503965e421539e6c6fefb2a7af is not running"} StackTrace:    at Docker.DotNet.DockerClient.HandleIfErrorResponseAsync(HttpStatusCode statusCode, HttpResponseMessage response, IEnumerable1 handlers)    at Docker.DotNet.DockerClient.MakeRequestAsync(IEnumerable1 errorHandlers, HttpMethod method, String path, IQueryString queryString, IRequestContent body, IDictionary2 headers, TimeSpan timeout, CancellationToken token)    at Docker.DotNet.ExecOperations.ExecCreateContainerAsync(String id, ContainerExecCreateParameters parameters, CancellationToken cancellationToken)    at DotNet.Testcontainers.Clients.DockerContainerOperations.ExecAsync(String id, IList1 command, CancellationToken ct)    at DotNet.Testcontainers.Configurations.UntilUnixCommandIsCompleted.Until(ITestcontainersContainer testcontainers, ILogger logger)    at DotNet.Testcontainers.Containers.TestcontainersContainer.<>c__DisplayClass35_1.<<Start>b__0>d.MoveNext() --- End of stack trace from previous location ---    at DotNet.Testcontainers.Configurations.WaitStrategy.<>c__DisplayClass1_0.<<WaitUntil>b__0>d.MoveNext() --- End of stack trace from previous location ---    at DotNet.Testcontainers.Configurations.WaitStrategy.WaitUntil(Func1 wait, Int32 frequency, Int32 timeout, CancellationToken ct)    at DotNet.Testcontainers.Containers.TestcontainersContainer.Start(String id, CancellationToken ct)    at DotNet.Testcontainers.Containers.TestcontainersContainer.StartAsync(CancellationToken ct)
I don't know how to solve this.
To Reproduce
I'm using a base clase for tests using Nunit framework in this way:
`[SetUpFixture]
internal class OracleContainerTest : WebApplicationFactory
{
internal static HttpClient Client;
    internal static WebApplicationFactory<Program> Factory;

    private static readonly TestcontainerDatabase oracleTestContainer = new TestcontainersBuilder<OracleTestcontainer>()
        .WithDatabase(new OracleTestcontainerConfiguration())
        .Build();

    public ContainerIntegrationTest()
    {
    }

    [OneTimeSetUp]
    public async Task LoadData()
    {
        await oracleTestContainer.StartAsync();

        Factory = new IntegrationTestWebApplicationFactory(oracleTestContainer);
        Client = Factory.CreateClient();

        Utilities.InitializeDbForTests(oracleTestContainer);
    }

    [OneTimeTearDown]
    public async Task DisposeContainer()
    {
        await oracleTestContainer.DisposeAsync().AsTask();
    }
}`

Expected behavior
I want to be able to launch the tests without exceptions in both environments
Desktop:
Testcontainers: 2.1.0
OS: Windows 11
Docker Desktop 4.12.0
CI environment
Docker Server Version: 19.03.12
Kernel Version: 4.19.0-9-amd64
Operating System: Debian GNU/Linux 10 (buster)
docker image:  debian:11-slim
Thanks

The Oracle configuration requires at least a password. You snippet cannot work. Also the class name and constructor does not match. Does your CI environment have the Unix socket /var/run/docker.sock?

Can you take a look into the Docker container logs? For some reason the container dies at the start. That is why you get:

Container 239e3824a1de91cab903aeecc070440ab3a7df503965e421539e6c6fefb2a7af is not running

yes, of course. I attach de log file, in this execution es for container 3eac277d7b314621a9fd5b160402a25b105f763ca93dbe6c9294e11c3c4c7483 in my local machine
log.txt

I need the logs from the container too.

ohh, thanks for the clue! the problem was the value of the password that i was assigning Password = Guid.NewGuid().ToString(), in the container log I could see the real problem!
...
CONTAINER: Resetting SYS and SYSTEM passwords.
ALTER USER SYS    IDENTIFIED BY "47406670-deca-4aba-959a-cb1097efdb2c"
*
ERROR at line 1:
ORA-00972: identifier is too long

In local it work fine! I have to test this in CI environment but now I can't. When I do it I will give you feedback.

Hi, the new version "2.2.0-beta.3123645733" work fine in my CI environment too! :)
Thanks @HofmeisterAn,
good job wtih the library!


Bridgewatcher fallbacks

Description

adding topic filtering to scribe backend
server config
origin and destination fallback
scribe indexer/backend modularity to use in bw fallback api
scribe check rpc flakes
Added cctp event search with all standard filters (pending, chain, amount, time, etc.)
Updated partial info type, return information about event type in bridge query (for fe updates)

Todo

[x] compete cctp destination filtering
[x] add scribe backend functions to ethergo + clean up (in another PR)

Tests temporary commented out to speed up runtime of tests locally

Some quick notes I want to add since #1243 got merged. This caused a small outage on the activity page and want to post some notes  on why this happened and how it can be prevented

After this was merged, @abtestingalpha reported issue w/ activity loading. This despite, extreme spikes in error %'s in signoz:

Leraning: @bsgrigorov, would be good to get alerting in place for both of these services.

At first, this looked to be an artifact of a large increase in explorer api usage caused by #1243 deployment, so @bsgrigorov scaled up instance to use  n2-highmem-32 (32CPU,256Gb). This resolved the issue for about 4 minutes until the limit was hit again. Oh boy.
At this point it became clear use_mv was se to false on the fe. This meant every query was doing a ton of joins for slightly fresher data:
. Use mv was enabled on the fe #1363
Lesson: API Consumers shouldn't have to think about underlying data structures. Should rename or remove use_mv
In between #1363, #1364 and later #1365 was made to determine how many users were on the page to see how big the load was. Signos showed approx. ~20 queries over the 20 minute period. At some point when moving to the new fe, GA was disabled so that was re-enabled
Once that was deployed, usage was still high. Turns out a lot of users just sit on the page for a while as this happens in the background. Makes sense.  22fb121c7edfe393c3b9a62cdca47c5126cbcc8f was made that forces use_mv to be false. Usage dropped from 94% cpu to between 2% and 20%  based on wether the materialized view shell generator is being ran.

This took slightly longer to debug and apply since the explorer latest was on feat/bw-final instead of master. Lesson: merge fast
Anyway good + fast resolution

btw @dwasse just merged this #1371 which deals w/ flake retries in ci, recommend merging here for explorer

@nautsimon let me know if this coderabbit thing feels at all useful


refactorings according comments on the first transaction PR

Goal of this PR:
implement the suggestions and comments of the first transaction PR

Goal of this PR:
implement the suggestions and comments of the first transaction PR

Best to actually link the PR #64


HTTP Error 400: Bad Request

Stacktrace
[
  {
    "parsedStack": [
      {
        "assembly": "Unknown",
        "method": "_make_request",
        "level": 11,
        "line": 176,
        "fileName": "/usr/local/lib/python3.6/site-packages/python_http_client/client.py"
      },
      {
        "assembly": "Unknown",
        "method": "http_request",
        "level": 10,
        "line": 252,
        "fileName": "/usr/local/lib/python3.6/site-packages/python_http_client/client.py"
      },
      {
        "assembly": "Unknown",
        "method": "send_email",
        "level": 9,
        "line": 35,
        "fileName": "/app/opwen_email_server/services/sendgrid.py"
      },
      {
        "assembly": "Unknown",
        "method": "_send_email",
        "level": 8,
        "line": 49,
        "fileName": "/app/opwen_email_server/services/sendgrid.py"
      },
      {
        "assembly": "Unknown",
        "method": "__call__",
        "level": 7,
        "line": 43,
        "fileName": "/app/opwen_email_server/services/sendgrid.py"
      },
      {
        "assembly": "Unknown",
        "method": "_action",
        "level": 6,
        "line": 60,
        "fileName": "/app/opwen_email_server/actions.py"
      },
      {
        "assembly": "Unknown",
        "method": "__call__",
        "level": 5,
        "line": 33,
        "fileName": "/app/opwen_email_server/actions.py"
      },
      {
        "assembly": "Unknown",
        "method": "log_exception",
        "level": 4,
        "line": 95,
        "fileName": "/app/opwen_email_server/utils/log.py"
      },
      {
        "assembly": "Unknown",
        "method": "__call__",
        "level": 3,
        "line": 37,
        "fileName": "/app/opwen_email_server/actions.py"
      },
      {
        "assembly": "Unknown",
        "method": "send",
        "level": 2,
        "line": 45,
        "fileName": "/app/opwen_email_server/integration/celery.py"
      },
      {
        "assembly": "Unknown",
        "method": "__protected_call__",
        "level": 1,
        "line": 641,
        "fileName": "/usr/local/lib/python3.6/site-packages/celery/app/trace.py"
      },
      {
        "assembly": "Unknown",
        "method": "trace_task",
        "level": 0,
        "line": 382,
        "fileName": "/usr/local/lib/python3.6/site-packages/celery/app/trace.py"
      }
    ]
  }
]

Log
SendOutboundEmails|error in action SendOutboundEmails (BadRequestsError(<HTTPError 400: 'Bad Request'>,))

Resolving as duplicate of https://github.com/ascoderu/opwen-cloudserver/issues/209


Disable link checking for GitHub Alerts

GitHub uses the following syntax for "Alerts":
> [!NOTE]
> Useful information that users should know, even when skimming content.

markdownlint will flag the [!NOTE] as a link, and will tell you No link definition found: '!NOTE'(link.no-such-reference). Can we turn this off for the keywords that make up alerts? Specifically:

[!NOTE]
[!TIP]
[!IMPORTANT]
[!WARNING]
[!CAUTION]

The error error message you show above is not coming from this tool. You can see that your example produces no violations: https://dlaa.me/markdownlint/#%25m%23 Issue 1418

> [!NOTE]
> Useful information

It looks like the message you show is coming from VS Code instead:  https://stackoverflow.com/questions/75252767/have-vscode-ignore-specific-reference-links-in-markdown-validation

Ah, thanks and sorry for the trouble! For those wondering, it looks like there's a follow-on ticket for VSCode here: https://github.com/microsoft/vscode-markdown-languageservice/issues/152


Oath without json file

We are attempting to create an application that will handle multiple users (Search Console), they will first provide permissions through oauth, then the application will continue to work in the background whether they are logged in or not. Due to the absolutely crazy 1 hour limit on tokens, we need to utilize refresh token, which are documented well, its just you never actually mention how you do it. Can you provide direct link to an example that does not use credentials json file and covers refresh tokens? TIA.

Ok I've done it. You really need to sort your documentation out. It's almost as if you don't want people to know how to use your APIs :)


Improving quality of background removal

I've tried this script to test background removal and compared it to commercially available AI powered solution and found that this model is not as good as commercial ones. If you zoom in image and compare you will see that this model doesn't produce smooth edges.
Can it be improved? Is there any further plan to improve it?

you can use pymatting to improve it. example https://github.com/danielgatis/rembg


Header files?

Where are the header files included in the .cc files?

You need to clone the dsp and code repositories

I see you play with Rust. Did you know that @bastibl ported Rattlegram to Rust?
https://github.com/bastibl/FutureSDR/tree/main/examples/rattlegram


Support for multiple RGB instances

I could not get multiple instances to work and modified the library to achieve this. I don't know how to create a branch etc in github - how do I send you my changes etc ?

Create a fork with the "Fork" button and make your changes in this repository. When your code is ready, create a pull request which I'll be able to merge into the main code.

You may want to make a reference to this issue by including #7 in the title of your pull request. :)


Added Urgent Contracts

Not sure why it says the checks have failed.

Warning: JSON document was prefixed by a BOM (Byte Order Mark): '\xef\xbb\xbf'
   |  At line 1, column 0, offset 0 (AT-START)

Your Timekeeper netkan also had a BOM in it. What software (text editor) do you use to create these files?

I use Notepad++.

Ok, I see the problem is in the encoding I use. I'll resubmit the PR now.


DBT version 1.2.4 not supported on dbt_cloud_environment resource

I'm trying to spin up a DBT environment and job using the dbt-cloud provider. However, when I try to apply my terraform plan, I'm running into the following error:
Error: POST url: https://cloud.getdbt.com........., status: 400, body: {"status":{"code":400,"is_success":false,"user_message":"The request was invalid. Please double check the provided data and try again.","developer_message":""},"data":{"dbt_version":"dbt version 1.2.4 is not supported."}} in resource "dbt_cloud_environment" "dbt_environment"
Here is my resource block in my terraform config
resource "dbt_cloud_environment" "dbt_environment" {
  dbt_version = "1.2.4"
  name        = "test_environment"
  project_id  = "projectID"
  type        = "deployment"
  is_active   = true
}

I'm using dbt-cloud provider version "0.1.4"
dbt = {
  source   = "GtheSheep/dbt-cloud"
  version   = "0.1.4"
}

I've tried changing the dbt_version value to "1.2.0", and "1.2" as well, but get the same error about the version not being supported. Is there something wrong with my config or does the terraform provider not support more recent dbt versions?
Thanks!

Hey, it's likely to be something like "1.2.0-latest" or something like that? Annoyingly dbt Cloud only allows dbt versions in the way that the drop-down does in the UI, and then they give it a different name instead of just the version number 🙄

Got it, appreciate the response! Will give that a try

@ajmunoz411 - Did this work ok in the end? 😸

This works with dbt_versions = "1.2.0-latest", dbt Cloud versions aren't specified like core, will make a note of this in the docs


ERROR in Directive ɵd in .../nativescript-angular.d.ts has no selector, please add it Angular 8

Environment

Angular CLI: 8
NativeScript-Angular: 10.0.0
Angular: 8

Describe the bug
After I had migrated angular project(use nativescript/schematics), I ran tns build android. But I got warnings "Can't resolve all parameters for NativeScriptPlatformRef", "Can't resolve all parameters for NativeScriptRenderer", "Can't resolve all parameters for EmulatedRenderer" then build error "ERROR in Directive ɵd in .../nativescript-angular.d.ts has no selector, please add it"
Expected behavior
The application should start in an Android simulator.

Same problem here.

Any update on this?

Any update on this?


feat(compiler): disallow "unknown" operation types

Operation types are parsed as an enum of Mutation | Query | Subscription | Other(unknown).
I would love to be able to call compiler.disallow_unknown_operation_types() that would emit diagnostics when calling compiler.validate() on a context that contains operations with unknown types.

When creating the hir, we assume that if there isn't a operation type token, it's a query:
https://github.com/apollographql/apollo-rs/blob/69311af67bfcd0ef36012f2a7f3221017190a6d3/crates/apollo-compiler/src/database/hir_db.rs#L1312-L1327
The parser doesn't allow any other keyword other than mutation, query or subscription, and emits an error:
https://github.com/apollographql/apollo-rs/blob/69311af67bfcd0ef36012f2a7f3221017190a6d3/crates/apollo-parser/src/parser/grammar/operation.rs#L77-L91
So I am not sure how you'd get to having an unknown operation type, other than having anonymous operations, which are in actuality queries. Did you run into an issue with an unknown operation type that isn't an anonymous operation? Otherwise, if it's only the anonymous operations that you'd like to disallow, then the other issue you opened is a good place to discuss that #625

Oh... I got confused w/my internal OperationType (which has an Other(string) variant and the OperationType provided by the compiler - I just hadn't imported the one from apollo-compiler and so my autocomplete was leading me astray. Appreciate the help 😄


Allow knex to infer config from a knex instance (when using the --knexpath flag)

Environment
Knex version: 0.19.3
Database + version: Postgres 11
OS: Linux
Bug / Documentation Error
This bug is related to a documentation issue: knex/documentation#234
Expected Behavior:
A developer should be able to the --knexpath flag to pass in a pre-configured knex instance to the CLI for use in operations like migrate:latest.
Test Code & Error Message:
If I have a file that exports a valid knex instance, for example:
// Located in './services/knex.js'

const knex = require('knex');

const config = require('./config');

module.exports = knex({
  client: 'pg',
  connection: {
    host: config.postgres.host,
    port: config.postgres.port,
    database: config.postgres.database,
    user: config.postgres.user,
    password: config.postgres.password,
  },
  // `migrationsDirectory:` should use the default path './migrations' without being specified
});

I should be able to use this instance to run my latest database migrations:
knex migrate:latest --knexpath ./services/knex.js

Note: I purposely do not create a default knexfile.js file or pass one in using the --knexfile flag, because the CLI should infer all the configuration data it needs from the passed knex instance.

However, when running this command, I encounter the following error:
Error: No default configuration file [...] found and no commandline connection parameters passed
This means that knex still expects a configuration file (or command-line parameters) despite already having a valid knex instance...

If I have to pass in the configuration "a second time", then what is the point of supporting the --knexpath flag anyway?
A developer should have options besides using a knexfile.js file to give configuration to knex.

@CodyEakins Why not just use Knex API for running migrations then? https://knexjs.org/#Migrations-API (probably could be documented better)
Personally I find knex CLI cumbersome and much prefer writing JS scripts for invoking knex migrations programmaticaly in all my projects.

@kibertoad
This was my work around for the time being -- I've seen pros and cons on both method`...
Either way, this is still a bug, correct?
It should be fixed to help those who choose to use Knex like this, for as long as it is a supported option.

@CodyEakins I'm not sure it's a bug, considering that I don't think we ever supported passing knex instance from knexfile.js, only configuration itself. I would consider it more of an improvement, but PR for it would still be welcome.
What is the advantage that you see with using migrations API via CLI while instantiating knex programmatically?

@kibertoad
If it is unsupported, then why not just remove the flag then? Or am I misunderstanding you?
One benefit of using knex through the command-line is to help keep app initialization clean when using Docker (e.g. - CMD knex migrate:latest && yarn run start).
While I don't use this approach, I have seen it recommended by other developers as a method for running the latest migrations during app startup.
I prefer to run migrations through the migrations API, however.

Rather than directly impacting my workflow, this bug is more about the --knexpath flag itself.
How to use it and why? In the current API, this is unclear.
And if --knexpath and --knexfile are meant to be used together, this just means that --knexpath has little to no affect on Knex's behavior (given the current API and presumed behavior).

@CodyEakins To the same effect you could be calling node scripts/migrateLatest.js && yarn run start that would be invoking knex.migrate.latest(youConfig) inside of it.
I guess --knexpath needs better explanation about what it is, and how it is supposed to be used. Looking at the tests I happen to think that "knex instance" does not mean what it appears to mean in this context.

@kibertoad
In Knex's current state, a developer has to make certain sacrifices:

They must include a knexfile.js in their project's root.
They cannot pass a valid config file to knex using the --knexfile flag if the config file is not strictly named knexfile.<ext>
They cannot pass a valid, pre-configured instance to knex using --knexpath.
(If relying only on the API, without a knexfile.js) They must make their own scripts to run even basic commands like creating a new blank migration.

All these sacrifices negatively impact the developer experience of using knex...

In my opinion, the --knexpath and --knexfile flags should be dropped in support of better, more usable flags like --config and --instance.
Using --config would allow a developer to pass a valid config file of any name and in any location to knex.
Using --instance would allow a developer to pass a valid, pre-configured instance of knex to knex, which would infer any required configuration values from it.
Libraries like babel and webpack follow approaches similar to these. I don't see why knex shouldn't...

We can't drop existing flags for the sake of backwards compatibility. However, we would accept PRs that would implement more intuitive and convenient to use configuration approaches.

Right, my mistake. But thanks for understanding.
I'll try to make some PRs in the near future to correct this behavior. See if it makes the library easier to use.

From what I can tell, it looks like the support for --knexpath might have been broken in a previous release.  More specifically: the --knexpath and --knexfile flags are being passed to the Liftoff library incorrectly; as a result, the values are being dropped before the Knex CLI can use them.
Fortunately, it looks like you can still provide a custom Knex path via the KNEX_PATH environment variable.  Ex:
KNEX_PATH=./services/knex.js knex migrate:latest

I might end up inadvertently fixing this as part of another CLI bug fix.  Stay tuned!

They must include a knexfile.js in their project's root.
Re install sqlite3 (npm install sqlite3 --save)
Run migrations command ( ex: npx knex migrate:latest --knexfile knexfile.ts migrate:latest)


Ubuntu Mate raspberrypi 4. libcec4

[x] I confirm that this is an issue rather than a question.

Bug report
At install of Hyperion on Ubuntu Mate 20.10
(
Steps to reproduce
Fresh Ubuntu mate installation and try install Hyperion  2.0. 0 apha9 linux-x86_64.deb
What is expected?
What is actually happening?
The terminal says it needs libcec4 but can't install
I already tryed to install ist with sudo apt install - y libcec4
But only an error that he can't find the paket
System

Duplicate issue
The bug fix has been in the master/main since December 27, 2020.
Fix will be available with the next release.


Incorrect parsing of image link in messages

In the constructor of GenericMessage class there is a check for an image link (lines 41-43). It's done incorrectly, only the presence of the substrings "http" and ".jpg" is checked.
The correct check should be on the MIME type of response from the server on the detected link. Do not forget about other types of images like gif or png.
It would also be nice to display images links which are inserted in the middle of the text. At first, we check the message with a regular expression for the presence of links and then check the response from the server for the MIME type.
In the future, you can implement the ability to display multiple images by links in a single message.

Closed due to project is abandoned.


New-TemporaryFile returns a object without extended filesystem provider properties

New-TemporaryFile returns a native .Net FileInfo object without extended PowerShell filesystem provider properties.
The problem is in PowerShell Core 6 but not in Windows PowerShell.
Steps to reproduce
$temp =  New-TemporaryFile
$temp | Select-Object PS*

Expected behavior
PSPath        : Microsoft.PowerShell.Core\FileSystem::C:\Users\username\AppData\Local\Temp\tmpE88E.tmp
PSParentPath  : Microsoft.PowerShell.Core\FileSystem::C:\Users\username\AppData\Local\Temp
PSChildName   : tmpE88E.tmp
PSDrive       : C
PSProvider    : Microsoft.PowerShell.Core\FileSystem
PSIsContainer : False

Actual behavior
<empty>

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.0.0-beta
PSEdition                      Core
GitCommitId                    v6.0.0-beta.6-60-g4ad313aafb1a1b747aaec0f975dcc823e4c907fc-dirty
OS                             Microsoft Windows 10.0.10240
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

I don't see how we can fix this in a simple way so maybe Won't fix.

Привет!
Good find; please fix the typos (both in the title and in the body): privider -> provider.

One way to fix this is to call Get-Item on it and the FileSystemProvider will decorate it and return that object.

@SteveL-MSFT I tried to do it, but I was having troubles. (1) We should create GetItemCommand for every new temp file - it seems looks not good. (2) I can not create GetItemCommand in the New-TemporaryFile cmdlet - unresolved name. If we have to add reference from Utility assembly to Management assembly - it seems looks not good?

Maybe this is an opportunity to revisit https://github.com/PowerShell/PowerShell/issues/4347#issuecomment-318098122 (making these properties part of the ETS rather than having the filesystem provider add it)?

@mklement0 yes, I think doing this as part of ETS makes sense, perhaps we should resolve this as dupe of that one

Good catch about ETS! Thanks!
What is right place for the fix?

@SteveL-MSFT:
Glad to hear it.
Re dupe:
Given that #4347 was just framed as a  question, I suggest creating a new, focused issue that reflects the intent to actually implement this (note that @lzybkr's original comments suggest that there may be conceptual problems).
@iSazonov:
From what I can tell, the relevant ETS members are defined here:
System.IO.FileInfo:
https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/engine/Types_Ps1Xml.cs#L192
System.IO.DirectoryInfo:
https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/engine/Types_Ps1Xml.cs#L180

@mklement0 Thanks for clarify!
I'm afraid I don't see all the side effects. Maybe @jeffbi can fix this?

@iSazonov @jeffbi was a vendor we hired to do some work, he's no longer on the project unless he wants to contribute personally


Window is not defined.

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[X] Other... Please describe:

I don't think my issue is either of the above, probably more so my lack of understanding.
Browser:

[ ] Chrome version XX
[ ] Firefox version XX
[ ] IE version XX
[ ] Edge version XX
[ ] Safari version XX
[X] Terminal/Console, no  browser, UI

Library version
Library version: 0.2.4

Current behavior

When the browser storage is set, and i am not using a browser?
Expected behavior

I want to use MSAL in console only Msal.UserAgentApplication object
Minimal reproduction of the problem with instructions

Save this js to index.js.  Install the msal module.  run index.js
const Msal = require('msal')
var applicationConfig = {
  clientID: "<clientID>",
  authority: "https://login.microsoftonline.com/<guid>"
};

var myMSALObj = new Msal.UserAgentApplication(applicationConfig.clientID, applicationConfig.authority, acquireTokenRedirectCallBack, {storeAuthStateInCookie: true, cacheLocation: "localStorage"});

function acquireTokenRedirectCallBack(errorDesc, token, error, tokenType) {}

I have the same issue with my azure function. Is there a different library which is also supporting non-Single-Page Apps?

I have the same issue in NativeScript application - Window context is not available.
`System.err: java.lang.RuntimeException: Unable to create application com.tns.NativeScriptApplication: com.tns.NativeScriptException:
System.err: Error calling module function
System.err: ReferenceError: Window is not defined`

Msal is oriented around user login flows and so it is expected to be run in a browser.
We do have an Adal node lib
I am new to the team, but from what I understand msal node is on the horizon.  @navyasric  do you have insight into the roadmap?

As mentioned above by DarylThayil, MSAL.js is designed to be used in client side JavaScript running in a web browser such as in case of single page apps.
For your console application, you may want to take a look at MSAL .Net. If your application is built in Node.js, we don't have concrete timelines to share on the plans for MSAL Node.js as yet.
You can also find a list of the libraries we offer here. Closing this issue.

For those interested i have a working nodejs console app against the Microsoft Graph, based off the https://github.com/microsoftgraph/nodejs-apponlytoken-rest-sample


Enable selecting the server for each operation request

I tried to put list of API server at operations(API) level, but still it is showing on top only, ideally it should give features to select under each and every api as it might be things we are having multiple server and for different APIS we might need to run on different server.
Thank you.

If I understand correctly you would want to the user to pick the server at the operation request for use with executing against that server. That isn't implemented as far as I know, but it would be possible for you to use a slot to configure a custom component and set the url accordingly.
Would that be feasible for your use case?

Does custom components work in middle of page? I wanted to keep server url selection before/after the request body so before executing request user can select particular server for that request.

Check out <slot name="${pathElementId}"></slot> where pathElementId you can grab from the website url when you navigate there. If you edit that you'll get a section that is right about in the middle of the page.


Add support for comparison operators in version numbers

Hi,
Re-opening after the great heroku-ing of 2014.
When specifying the version number it would be great to be able to have it work like : {tag, gt, "0.9.0"} which would be greater than 0.9.0.
Obviously this only works for a subset of values which people stupidly put there but if we set a precedent to show the usefulness of having version numbers orderable then we'll be happy :)

Hi, this issue was closed in an attempt to do quick basic filtering. All tickets prior to March 2017 were closed and will be reopened on a per-request basis, please give rebar3 a try and feel free to reopen if it's a pressing issue that is still unresolved.


Implement an UnsafeEval binding

This adds a new UnsafeEval binding APi that is intended only for use with workerd and only when the --experimental flag is specified. See the included test for an example on how to use it.
console.log(env.unsafe.eval('1+1'));  // 2

const fn = env.unsafe.newFunction('return m', 'foo', 'm');
console.log(fn(1));  // 1
console.log(fn.name);  // foo
console.log(fn.length); // 1 argument

/cc @mrbbot @IgorMinar

Yes, that's a good example.
If we wanted user code to have unrestricted access to eval then we could have implemented this feature as a workerd flag which makes globalThis.eval available. We chose to restrict access to eval by making it available via a binding instead, so I'd expect any recursive eval if really needed, to access the functionality via the binding and not global.
Since dynamic code evaluation is only meant to be used by development tooling (test runner code, dev server code) I think we should be intentional about not easily exposing it to user code running within this development tooling.

Is eval available yet in cloudflare workers? Would love to use it / enable it for use. @mrbbot @IgorMinar

Since dynamic code evaluation is only meant to be used by development tooling (test runner code, dev server code) I think we should be intentional about not easily exposing it to user code running within this development tooling.

I'm a bit confused. How is allowing env.unsafe.eval('eval("1+1")') less safe than allowing env.unsafe.eval('1+1')?

@jasnell the goal is not "safety" but about preventing accidental code interoperability. Accidental use of eval in applications will result in some apps running locally, but breaking in production, which is bad DX.
Our use of eval in Workers tooling is for dev-only code that wraps the application code to make it run during local development workflows - this wrapper code will never run in production as it only enables hot module reloading and other dev-only features.
Since our code runs in the same VM as the application code we need a way to access eval but ideally without polluting the runtime globals with eval. Application code could be using eval directly, or indirectly via 3rd party libraries/generated code, without developers knowing about it, and learning about it only when the production deployment fails for an app that ran well locally.
You could argue that exposing eval via binding is not a high bar to overcome, but in that case you are using a non-standard API which is behind an experimental flag both of which reduce the likelihood of surprises in production.


atlantis: 0.10.1 -> 0.11.1

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/runatlantis/atlantis/releases.
meta.description for atlantis is: "Terraform Pull Request Automation"
meta.homepage for atlantis is: "https://github.com/runatlantis/atlantis"
Updates performed:

Golang update
Quoted meta.homepage for RFC 45

Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.11.1 with grep in /nix/store/9z46r02pj0nshgmr338m03cwskbjp745-atlantis-0.11.1

directory tree listing: https://gist.github.com/630181de6175c85cddaaa9aa46020438

du listing: https://gist.github.com/26044aa8fb900e24c180be431b981997

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
atlantis

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9z46r02pj0nshgmr338m03cwskbjp745-atlantis-0.11.1 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A atlantis https://github.com/r-ryantm/nixpkgs/archive/d5c2e72f8b3d27a5f782fb957be11edb5fd4a72e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9z46r02pj0nshgmr338m03cwskbjp745-atlantis-0.11.1
ls -la /nix/store/9z46r02pj0nshgmr338m03cwskbjp745-atlantis-0.11.1/bin

cc @jpotier @kalbasit for testing.

@GrahamcOfBorg build atlantis

Thanks for testing


supporting ImageMagick 6 and 7

This PR supports building the magick plug-in for both ImageMagick 6 and 7.

@zwoop fyi

I was getting this before this PR:
experimental/magick/magick.cc:42:10: fatal error: MagickWand/MagickWand.h: No such file or directory
 #include <MagickWand/MagickWand.h>
          ^~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.


First try at WAST printer

TODO

Make it lint (Flow don't get it)

I think we should remove the flowtype check

@johnsudaar do you think we need an unified interface for our printers?
The wasm printer can't use the same recursive code gen tho since it's divided into sections.

Looks good to me, it's a first implementation we can iterate on this later.


Fix grammatical typo in desktop-src/desktop-programming.md

Adds missing "that", properly joining the restrictive clause to the beginning of the sentence.

Thank you!


feat: introduce canonical url audit

closing in favor of https://github.com/adobe/spacecat-audit-worker/pull/326


Can't create a standalone, no python dll.

<IP_ADDRESS>
Commercial: None
Python: 3.7.10 | packaged by conda-forge | (default, Feb 19 2021, 15:37:01) [MSC v.1916 64 bit (AMD64)]
Flavor: Anaconda Python
Executable: C:\Users\jeans\miniconda3\envs\fresh\python.exe
OS: Windows
Arch: x86_64

I used to compile with Nuitka with hinted compilation before. I am now trying to compile without it on <IP_ADDRESS>.
This seems like an easy to solve issue but I can't figure it out. I get a "success" compile and an executable. When I try to run it, I get an error message stating "python37.dll not found"  (in french, so it's something similar).  If I add the .dll in the same folder, I get rid of the error, but nothing happens, there is no message in the console.
Also, only an exec and a bat file are created. No folder or dll is created or moved to the destination, which surprises me because with hinted compilation I end up with hundreds of files and folders.
I am using these arguments:
    "--standalone",
    "--mingw64",
    "--follow-imports",
    "--assume-yes-for-downloads",
    "--warn-implicit-exceptions",
    "--warn-unusual-code",
    "--windows-icon-from-ico=logo.ico",
    "--static-libpython=no",

in a .py file for my own sanity and calling nuitka directly from the file, similar to how nuitka-hints was doing it:
import sys
from nuitka.__main__ import main
...
do some stuff, options
...
sys.argv = my_opts
main()

Also, it seems to always fail at a first attempt, then succeed. That's the only warning I get:
Nuitka-Postprocessing:WARNING:
Failed to add resources to file 'C:\\Users\\jeansDev\\project\\DIST\\cor.exe' in attempt 1 with error code 22.
Disable Anti-Virus, e.g. Windows Defender for build folders. Retrying after a second of delay.
Nuitka-Postprocessing:WARNING: Succeeded with resource update in attempt 2.

Edit: I was getting that same error on the latest dev version, then rolledback to stable <IP_ADDRESS>. before submitting this issue.

Quite similar to this:  #1313

It seems you want to use standalone mode, check out the user manual. The binary you create ought to run on the same machine, but mostly only there, and often only if started through a cmd file also generated.

@kayhayen I need clarification on this. I seem to be trying to do the exact same thing.
Pasted from the User Manual:

Moving binaries to other machines
The created binaries can be made executable independent of the Python installation, with --standalone and --onefile options.

I also caught a post from you stating that hinted-compilation is not maintained anymore and that you consider it obsolete with the new anti-bloat plugin.
That, and the manual explanation led to me think that I can get the same result with --standalone and distribute my application.
Are you saying that it is not possible to distribute my application anymore with the latest versions of Nuitka?

I might also be worth noting that --standalone is not creating a program.dist folder for me, only a program.build.

If you want to be able to copy it to another machine, use --standalone and copy the created program.dist directory and execute the program.exe (Windows) or program (other platforms) put inside.

I changed the order of the arguments and I now have expected warnings for plugin detection, which means that my argument
--standalone was being ignored when at the first position, which I understand now:
    if "NUITKA_BINARY_NAME" in os.environ:
        sys.argv[0] = os.environ["NUITKA_BINARY_NAME"]

Conclusion: reserve 1st spot for this when calling Nuitka from a python file.

Are you aware of nuitka-project: style options. I am not sure what your wrapper is aiming at achieving, but I am trying to make these things unnecessary. The sys.argv[0] is always the program. And Nuitka wants to re-execute, in case certain conditions are not met, you better avoid that trouble by running it as a process.


fix burger menu overlaps with logo

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/25646
PROPOSAL: https://github.com/Expensify/App/issues/25646#issuecomment-1687594198
Tests

Open https://help.expensify.com/ or run it locally using cd docs && bundle install && bundle exec jekyll serve --livereload
Resize window width
Verify that the burger icon will not overlap the logo

[x] Verify that no errors appear in the JS console

Offline tests

Same as tests
QA Steps

Same as tests

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@getusha Can you please update the steps of testing to include how to run this locally?

@allroundexperts included how to run it locally.

Going to check if we can merge this now despite the merge freeze, since it's only a visual change.

Yeah agreed. Let's go ahead and merge then.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/francoisl in version: 1.3.62-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🎉

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.62-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


BSON.stringify slower than JSON.stringify?

0.188 s
vs
0.049 s

is bson stringily something you wrote ? BSON will always be slower than JSON as it cheats in v8 and has optimizations unavailable for any js or c++ code.

Ex. msgpack is only 2 times slower

msgpack also does not have to scan 0 terminated key names as it gives you the key size up front.