Unable to exec '/var/vcap/packages/mariadb/bin/mysqldump': fork/exec /var/vcap/packages/mariadb/bin/mysqldump: no such file or directory

Hello,
For shield v8.0.8, we are facing issue while running the jobs for bakcup of CF tenants.
Issue is:-
Unable to exec '/var/vcap/packages/mariadb/bin/mysqldump': fork/exec/var/vcap/packages/mariadb/bin/mysqldump: no such file or directory
For this issue we have tried by adding an addon into CF manifest file as follow-
name: shield-addon-mariadb-10.2
release: shield-addon-mysql
we have uploaded release using genesis into CF manifest file.But we are facing issue at the time of CF redeloyment with this addon as follow-
troff: fatal error: can't find macro file m
Error 450001: Action Failed get_task: Task### result: Compiling package shield-addon-mariadb-10.2: Running packaging script: Running packaging script: Command exited with 2; Truncated stdout: -- Installing: /var/vcap/packages/shield-addon-mariadb-10.2/
include/mysql/server/mysql/service_thd_autoinc.h
At global scope:
cc1plus: warning: unrecognized command line option "-Wno-implicit-fallthrough" [enabled by default]
cc1plus: warning: unrecognized command line option "-Wno-format-truncation" [enabled by default]
cc1plus: warning: unrecognized command line option "-Wno-misleading-indentation" [enabled by default]

make install
CMake Error at client/cmake_install.cmake:58 (FILE):
file INSTALL cannot copy file
"/var/vcap/data/compile/shield-addon-mariadb-10.2/mariadb-10.2.10/client/mysqltest"
to "/var/vcap/packages/shield-addon-mariadb-10.2/bin/mysqltest".
Call Stack (most recent call first):
cmake_install.cmake:122 (INCLUDE)

Is there more to that error?
I'd wager your compilation VM ran out of disk space; I recall that being a problem in my own testing and lab setups.  The rest of the error should mention something like "No space left on device" or something similar, in that case.

No, we was facing issue at compile time only.
As, Now we have increased the size of compilation vm ,  there is no issue at complie time.
Now we are facing error as follow-
'mysql_proxy_z1/0 ' is not running after update. Review logs for failed jobs: shield-agent
We checked logs for shield-agent
agent.log
/var/vcap/jobs/shield-agent/bin/shield-agent: line 53: LD_LIBRARY_PATH: unbound variable

Hi,
For this error we upgarded shield to v8.0.9 now there is no any error in cf deployment, but we are facing issue with import errand.
Import errand got failed with following error:-
[stderr]
/var/vcap/jobs/import/bin/run: line 8: token: unbound variable
!!! : failed to connect to : Get /v2/auth/id: unsupported protocol scheme ""

Yes, you are looking for the fix in 5e3cc10, via #132.  Try 8.0.12, which includes that fix.

Any luck?


Still return defaultState in handleActions reducer when no handlers are provided

Fixes #202

I think I misread https://github.com/acdlite/redux-actions/issues/202#issuecomment-287732099.
Why do you think an empty object is not an usage error? I'd have thought that we would be throwing an error (using invariant) and writing a test for that instead.

First: It was possible in previous versions of redux-actions. So it was a breaking change for us.
For sure it is an edge case.
But my argument would be that it is still semantically correct to give the handleActions function an empty object which would mean "please do not handle any actions (at the moment)". Returning the default state doesn't have anything to do with how many actions the reducer handles (0-infinity) and should always work.

Thanks for the reply. We're on 2.0 now, that breaking change should have been noted. Though I'm not sure when this break occurred.
I can't think of a use case in real apps. Could you give an example?

You're right there is no "real" use case for that. However we often start new redux/react apps with an empty skeleton of different reducers and this breaks our skeletons now.
Its not a huge deal. I would also be fine with an invariant check, but it shouldn't just silently break as it does now.

I think defaulting to defaultState is still correct for the created reducer. I'm wondering if this would also fix I think this will also fix https://github.com/acdlite/redux-actions/issues/197.
Can we do an invariant check in handleActions (maybe using isPlainObject), write some tests for the new API and defaultState behavior (with a valid action), and we can get this merged and released? Thanks for your time.

I update the PR with more tests and the invariant check. Hope the expected behaviour is better described now.
Regarding #197
It is not fixed yet with this PR. I think the origin of this issue is that the defaultState should not be forwarded to the handleAction calls at all. handleAction should be called with an undefined defaultState in this case. Let the handleActions handle setting the default itself as it is now implemented here. This of course would require the removal of the invariant check of defaultState in handleAction. Which for me would be OK because it is totally valid to have an undefined defaultState.

Thanks for the contribution!


Activity list wording for Challenger tx

** Suggestion **
Currently, Explorer lists activity for Challengers as "PoC Challenger" and "Challenger" respectively. I think this should be reworded to "PoC Challenger" and "PoC Challenger Receipt" or something along those lines. This will highlight that PoC Challenger is the start and PoC Challenger Receipt is the end of the challenge.

This has been updated to Created challenge > Challenged beaconer > Received mining rewards, this should be more logical now. Should this be closed?

Much more clear now. Thanks


UAT| judge_parites shown as N/A.

Hi @devarajd94  please confirm

Schedule of Hearing - Name of parties required to attend that hearing
Schedule Next Hearing - Name of parties required to attend that hearing
Warrant - warrantFor person
Notice - noticeFor person
summon - SummonsFor person
Order for Mandatory Submission - submissionParties and Respondent Parties
Order Section 202 CRPC - detailsSeekedOf
Order for Bail - partyName for which the submission was made
Voluntary Accept - partyName for which the submission was made
Voluntary Reject - partyName for which the submission was made
Reject Reschedule Hearing Request - partyName for which the submission was made
Checkout Rejection - partyName for which the submission was made
Others Order - All the parties
Transfer to ADR - All the parties
Initiate Reschedule - All the parties
Judgement - All the parties
Order of Case Settlment - All the parties
Order of Case Withdrawal - All the parties
Order of Case Transfer - All the parties
ASSIGNING_DATE_RESCHEDULED_HEARING - All the parties
Reschedule of Hearing Date - All the parties
Checkout Acceptance - All the parties
Submission Extension - All the parties
@rajeshcherukumalli @Ramu-kandimalla  @anirudh-0
These are the orderTypes and respective parties for the same. Kindly take a note

Hi @Ramu-kandimalla  @rajeshcherukumalli , Tested in QA env, Facing the issue's in Orders flow, will check & will confirm once the issues are fixed, below are the issue link for the references,
https://github.com/pucardotorg/dristi/issues/1918
https://github.com/pucardotorg/dristi/issues/1917

Verified that parties name is displayed.
Test cases:
https://docs.google.com/document/d/1VWn0Ev_pQKbPcfMNIP01EqGaWUj6bMTi_5Bi2du3Uro/edit?tab=t.0

Verified in UAT env, Working a Expected
https://jam.dev/c/04775488-d843-481c-b0a4-a4b2f55714b2
https://jam.dev/c/ca04797b-e557-449d-90bf-8b564f95c345


[T4A3][T09-B1] Gary Goh

@garygjy Some comments added. Please close the PR after reading comments.


Add flag to nbench to ensure synthetic tensor data is always positive

Some ops take input tensors which require their content to be all positive (e.g. the variance tensor in BatchNorm). This information isn't queryable by nbench on a per-op basis, and so I would suggest a flag be added to nbench that causes only positive synthetic data to be generated. Possible alternatives would be to add a min/max command line param. in nbench to specify the RNG domain.

What bad would happen if we just made all of the data positive all the time. I'm not positive but it should be ok. A flag is easy too. I'm not trying to be negative, just wondering.

Since nbench is meant only for performance testing and not correctness, I would say this is also likely a valid approach.


Increase memory & zip file count limits

Description

Increase main compile step max memory to 16g. This fails on anything less for azure-native.
Enable zip64 for the :jar task

Fixes #1087
Checklist

[ ] I have added tests that prove my fix is effective or that my feature works

[ ] I have updated the CHANGELOG-PENDING file with my change

[ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version

Looks like you need to regenerate the coegen changes to get CI to pass. I expect that's PULUMI_ACCEPT=true and rerunning tests.

Looks like you need to regenerate the coegen changes to get CI to pass. I expect that's PULUMI_ACCEPT=true and rerunning tests.

Couldn't see anything in the contributing docs on which targets are required to run before CI so just ran make. Will take a read of the makefile and CI and see if I can figure it out if in doubt.

make codegen_tests_update should do it.


Opening HTML files from the integrated terminal to the browser

The typical use case of mine is executing Django tests in the terminal and wanting to inspect the local coverage HTML files. As of now there seems no way of opening that HTML file directly in the default browser.
It would be useful to be able to do so from the tooltip shown in the screenshot below, which currently allows to open files in the editor only.

I believe this could be implemented using the TerminalLinkProvider API

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

Duplicate of https://github.com/microsoft/vscode/issues/200579


miniaudicle: <IP_ADDRESS> -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/miniaudicle/versions.
meta.description for miniaudicle is: Light-weight integrated development environment for the ChucK digital audio programming language
meta.homepage for miniaudicle is: https://audicle.cs.princeton.edu/mini/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS> with grep in /nix/store/bjhxqhidrrqy019r5z7y87l3mhll9f9k-miniaudicle-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/bjhxqhidrrqy019r5z7y87l3mhll9f9k-miniaudicle-<IP_ADDRESS>

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

miniaudicle

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bjhxqhidrrqy019r5z7y87l3mhll9f9k-miniaudicle-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The 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 miniaudicle https://github.com/r-ryantm/nixpkgs/archive/2c8966ef551a730212096188fe01bc3d78b002e6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2c8966ef551a730212096188fe01bc3d78b002e6#miniaudicle

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bjhxqhidrrqy019r5z7y87l3mhll9f9k-miniaudicle-<IP_ADDRESS>
ls -la /nix/store/bjhxqhidrrqy019r5z7y87l3mhll9f9k-miniaudicle-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

miniaudicle

Maintainer pings
cc @fgaz for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 361964

aarch64-darwin

:fast_forward: 1 package marked as broken and skipped:

miniaudicle


tests: refactor simulate transport

This pr introduce API to hijack receiving message. Resolving issue #866 depends on this pr.

@ngaut @siddontang @disksing @zhangjinpeng1987 PTAL

LGTM

LGTM


5.71: Error messages for thumbnail generation don’t display correctly

When trying to generate a thumbnail with an empty P1, the following cryptic error message is displayed:

We expect this message to say something about how P1’s name is empty instead

This has been fixed and is currently merged into main. It'll be included in the 5.74 release.


generate_schema_name compilation behavior has changed

Issue
Issue description
I actually don't know what has changed here, just that something has.
This macro used to throw an error if a model or seed didn't have a custom schema (the desired behavior), but as of 0.12.2 it doesn't throw the error.
Steps to reproduce:

Add this to your project:

{% macro generate_schema_name(custom_schema_name) -%}
    {%- if custom_schema_name == None and model.resource_type in ['seed', 'model'] -%}
     {%- set error_message -%}
       {{ model.resource_type | capitalize }} '{{ model.unique_id }}' does not have a schema configured.
     {%- endset -%}
    {{ exceptions.raise_compiler_error(error_message) }}
    {%- endif -%}

    {%- set default_schema = target.schema -%}
    {%- if target.name == 'prod' and custom_schema_name is not none -%}
        {{ custom_schema_name | trim }}
    {%- else -%}
        {{ default_schema }}_{{ custom_schema_name | trim }}
    {%- endif -%}
{%- endmacro %}

Don't configure a custom schema in your dbt_project.yml file.

3.dbt compile
Expected results
On 0.12.1 this would return:
(dbt0.12.1) $ dbt compile
Encountered an error:
Compilation Error
  Model 'model.jaffle_shop.stg_customers' does not have a schema configured.

  > in macro generate_schema_name (macros/get_custom_schema.sql)
  > called by <Unknown>

Actual results
From 0.12.2 onwards this returns
(dbt0.12.2) $ dbt compile
Found 8 models, 20 tests, 0 archives, 0 analyses, 96 macros, 2 operations, 0 seed files

15:25:51 | Concurrency: 1 threads (target='dev')
15:25:51 |
15:25:52 | Done.

Notes
I'm very happy for you to slap a #wontfix on this, since when I wrote this code I was hacking at the edges of dbt. But if there's a better way to do this, that would also be good to know!

This was not what I expected it to be! It's another generate_schema_name macro wart, with a twist. As of 0.12.2, In generate_schema_name the model context object is always the macro object itself. So the check that's not passing anymore is model.resource_type in ['seed', 'model'] (because model.resource_type is 'macro'.
Maybe generate_schema_name could take a model argument? That's easy for us to do but probably user unfriendly, and a bad compatibility break.
Or we could stash the context and defer the call to generator that's currently here until use-time, though that probably hurts performance since we have to call .generator() once per model that way.
Or maybe there's some way to override the environment after calling generator but before the actual macro call.
At a minimum, it does seem to me like we should probably not have model in the context for generate_schema_name if it's going to be this wrong!

Hm so the reason that that condition lives there is because otherwise it raises a compilation error since macros can't have schemas configured. I think this is a reasonable thing to want to do, but I don't know another way around it.

In 0.14.0, the generate_schema_name macro will accept a node argument (docs to come here). You can use this argument to generate a custom schema (or implement other logic) depending on attributes of the node that is being configured.
via: https://github.com/fishtown-analytics/dbt/pull/1483

For posterity, the code that works is:
{% macro generate_schema_name(custom_schema_name, node) -%}
    {%- if custom_schema_name == None and node.resource_type in ['seed', 'model'] -%}
     {%- set error_message -%}
       {{ node.resource_type | capitalize }} '{{ node.unique_id }}' does not have a schema configured.
     {%- endset -%}
     {{ log(node.resource_type, info=True) }}
    {{ exceptions.raise_compiler_error(error_message) }}
    {%- endif -%}

    {%- set default_schema = target.schema -%}
    {%- if target.name == 'prod' and custom_schema_name is not none -%}
        {{ custom_schema_name | trim }}
    {%- else -%}
        {{ default_schema }}_{{ custom_schema_name | trim }}
    {%- endif -%}
{%- endmacro %}


slice list in reverse

Implementation of slice list in reverse.

Hi @flacode -- thanks, this looks good!
The Travis build failed because of some style checks, can you have a look?


Error when running learn.py.

There is no argument 'no_graphics' in animalai.env init.  What argument does no_graphics match?

This was a legacy issue which I just fixed in v1.0.5, you can update via pip or the repo.


VNF on OneKE appliance doesn't NAT (or get any NAT related info)

Description
Once our team try instantiate the OneKE appliance (both the normal and the airgaped version) available from the public Opennebula marketplace  the VNF doesn't get any NAT rule, thus making the communication between the public network to the VNF and then to the private k8s cluster unavailable :-(
To Reproduce

Download the Appliance
Create 2 networks (one will be the public (in our case a real public IP) and the other will be the private (in this example we will use <IP_ADDRESS>/24) )
Instantiate the appliance under the Service tab using:

Please, note that we configure the MetalLB, but we also tried without the MetalLB and some other simple tweaks but got no NAT on VNF
We also tried in different OpenNebula versions (6.4.X and 6.8.2)

Expected behavior
A working k8s cluster
Details
If we go into the VNF via SSH and check the logs on /var/log/one-appliance/one-failover.log we got:

Telling us that the VRouter failed, but it doesn't say the why :-(
But, if we check on the /var/log/one-appliance/configure.log, we got:

Informing us that the /etc/iptables/rules-save file was created, but if we try to open the file, the file is indeed empty:

And if we check the iptables:
vrouter:~# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

And:
vrouter:~# iptables -L -t nat
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination

Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination

And if we try with the recommended command:
iptables -t nat -vnL NAT4
iptables: No chain/target/match by that name.

We got nothing :-(
If we try to get to the public network from the master, storage or slave nodes, (which have the DNS server (at /etc/resolv.conf) pointing to the private IP of the VNF node) we got no answer from the internet, meaning those k8s nodes can't get anything from the internet.
Additional context
We don't really know if the problem it's indeed VNF or if we are setting a wrong configuration, as the documentation doesn't give much :-(

Progress Status

[ ] Code committed
[ ] Testing - QA
[ ] Documentation (Release notes - resolved issues, compatibility, known issues)

@kCyborg + @sk4zuzu issue has been transferred to the right repo


NoneType error

hi there -
wondering if you could help out really quick?
when i refresh my pillar data, the salt master log prints out:
[salt.pillar      ][CRITICAL][13818] Pillar render error: Failed to load ext_pillar vault_store: 'NoneType' object has no attribute '__getitem__'
I'm pretty sure i've got the configuration right, here it is:
`ext_pillar:

vault_store:
url: https://vault.url:8200
config: /etc/salt/config.yml
token: redacted
unset_if_missing: True`

here is my config yaml
'*':   'aws_key_id': 'secret/service/salt/dev/aws-access-key?id'   'aws_secret_key': 'secret/service/salt/dev/aws-secret-access-key?secret'
i've made sure that the token can read and write to that path in Vault and that the salt master can reach the vault server.
Not too sure what to do at this point.

nevermind - i'm an idiot. got it worked out.

There are no dumb questions!
would you mind sharing the issue/solution so that others in the future that may find this thread can know what the answer is?

It turned out i had my config wrong
'aws_secret_key': 'secret/service/salt/dev/aws-secret-access-key?secret'
needed to be
'aws_secret_key': 'secret/service/salt/dev/aws-access-key?secret'


Adding support for a nonce

According to the OpenID connect spec:

nonce
String value used to associate a Client session with an ID Token, and to mitigate replay attacks. The value is passed through unmodified from the Authentication Request to the ID Token. If present in the ID Token, Clients MUST verify that the nonce Claim Value is equal to the value of the nonce parameter sent in the Authentication Request. If present in the Authentication Request, Authorization Servers MUST include a nonce Claim in the ID Token with the Claim Value being the nonce value sent in the Authentication Request. Authorization Servers SHOULD perform no other processing on nonce values used. The nonce value is a case-sensitive string.

Right now, if a client passes a "nounce", we don't give it back and
the client fails. This is happening to me right now with the client
from Matrix Synapse.
Here, I'm creating a new service (CurrentRequestService).
With this new service, I can get the current PSR-7 request.
I extend the AuthCodeGrant and inject this service into the extended class.
With this, I can:

read the "nonce" from the request
encode the "nonce" in the "code"

Then, in the IdTokenResponse, I read the "code" (if it is present),
extract the "nounce" and inject it in the ID token as a new claim.
The whole process is inspired by this comment: https://github.com/steverhoades/oauth2-openid-connect-server/issues/47#issuecomment-1228370632
With those changes, nounce is correctly handled and I've successfully
tested a connection with the OpenID client from Matrix Synapse.
This PR is built on top of #16

Hey @ronvanderheijden ,
Following your last review (and the fact I broke CI), I realized that the CI checks were not visible when making a PR from a fork. I slightly changed the configuration of the CI to be sure that when a PR is open, Github actions are run (and are visible in the PR).
So long story short, the CI is now ok! Let's merge this!


exportImage returns "empty" data URIs and blobs.

Wavesurfer.js version(s):
3.3.0 (latest as of this post's date)
Browser and operating system version(s):
Firefox Dev Edition, 72.0b11
Chromium 79.0
Arch Linux
Code needed to reproduce the issue:
var wavesurfer = WaveSurfer.create({
    container: '#waveform',
    waveColor: 'violet',
    progressColor: 'purple',
    cursorWidth: 0,
    interact: false,
});

wavesurfer.load('audio.mp3');

wavesurfer.on('ready', function () {
    var waveimage = wavesurfer.exportImage();
    document.getElementById('pngwave').innerHTML = '<img src="' + waveimage + '">';
});

Use behaviour needed to reproduce the issue:
Just loading the page returns the  object and it displays nicely. However, the data URI returns empty instead of showing the waveforms. The same happens with blobs.

Go the https://wavesurfer-js.org/, open a console, type wavesurfer.exportImage() and it seems to work fine.


Better support for browser history navigation on the client

Description
I heard you were working on V1 so I was hoping to get this issue on your radar!
I recently migrated a React app to Vike that made heavy use of HTML history calls like history.pushState. I ran into the problem that it was difficult to reproduce the history stuff using Vike's API.
In the past, I've used redux-first-history, which does a good job consolidating router state into the Redux store, so the app has a single source of truth.
Here are the problems as I see it:

Vike doesn't offer a client-side navigation function that allows you to push a new search or hash to the URL, equivalent to history.pushState({}, null, "/some/url?foo=bar). All you can do is navigate("/some/url?foo=bar"), which causes a whole new React render -- too heavyweight. The beauty of pushing a new search or hash is that the browser can update the URL without reloading the page, and that search or hash can then be picked up by the app's UI.
If I use the usePageContext provider to get the PageContext in a component, and then do my own history.pushState call to change the search or hash, the hook doesn't update! This prevents me from handling search updates by looking at  PageContext.urlParsed.search from the hook.
Even if the PageContext method worked, it wouldn't be ideal. I'd rather integrate the search or hash into a data store like Redux, so my app has all the state in one place. It would be nice if Vike's client routing API could support writing a Redux middleware or something to accomplish this.

Hope this feedback helps! Thanks for the awesome project.

Thanks for creating this feature request. It's always helpful to know what users want.

consolidating router state into the Redux store, so the app has a single source of truth.

I agree it would be nice.
In general, providing lower-level hooks for increased flexibility is very much on the radar.
That said, the priority right now is to 1. release the V1 design and 2. release v1.0.0. As you can imagine it's a lot of work so I need to prioritize accordingly.
While increased control over history.pushState is very much a consideration it isn't a priority. That's why I'm closing this for now; I'll re-open this ticket when it becomes a priority.
In the meantime, upvote this ticket (react with 👍) if you need this. Also feel free to comment here if it's somehow a blocker.
Also, would your company be up for sponsoring? The more we have company sponsors, the faster we can move Vike forward and the faster lower-level hooks are going to see the light. The truth is that I need your help as much as you need mine: it's best when we help each other.

Also, would your company be up for sponsoring?

Not at the moment unfortunately, but hopefully someday.

Also feel free to comment here if it's somehow a blocker.

I think I just ran into a blocker situation.
Like I mentioned, I want my app to be able to push new searches to the URL and pick these up in the React UI. The problem arises when you try to use the browser's forward/back buttons.
It seems that Vike's client runtime actually reacts to to the history popstate event in here. Sometimes Vike decides to try rerendering the page, which in my case is not desirable. I'll list an example sequence of events:

In a new browser tab, open /my/url?search=foo
Press a button in the UI that causes a history.pushState to set search=bar. Now we're at /my/url?search=bar and everything is fine (no rerender happens).
Press the back button: now we're back on /my/url?search=foo. The client router tries to set the scroll position, which is not desirable (this branch). The scroll position change has no effect in my case so everything still looks okay.
Press the forward button: now it tries to go to /my/url?search=bar again. This time we hit this branch, which tries to rerender the page--it redoes my GraphQL queries and screws up the app state.

I think there's an actual design question here:

If a Vike user wants to handle history changes themselves using react-router, the current design steps on their toes.
However, you could also imagine an app that does want to do a new client-side rerender when the search changes.
So, until Vike provides a complete story for how to handle history, maybe we need a way for the user to specify if a given history event should be handled by Vike or should be ignored so the user can handle it themselves?

As an API suggestion, maybe Vike could export a function shouldVikeProcessPopState. By default it always returns true, but the user could override it to look at a given popstate event and return false if they want Vike to ignore it.

After posting this I wondered if it might be possible to solve the problem with the onBeforeRender hook, perhaps to abort the render. But it doesn't seem to work.
It would be a convenient API though if I could just define a hook in the page(s) where I want to deal with my own URL search. Maybe the hook could be named onBrowserHistoryEvent.

I think I just ran into a blocker situation.

Correct me if I'm wrong, but I don't think it's a blocker: the workaround is to re-render the whole page while using React's caching mechanisms if you run into performance issues. That's actually the React idiomatic appraoch. (And that's also what Redux does, although an immutable store improves the caching story). I know it isn't what you want, but that's how React works. (Whereas Vue and Solid use an architecture based on signals: everything is essentially always cached while signals surgically update elements.)
That said, I'm open for providing lower-level hooks for increased flexibility, also regarding history.pushState. It just isn't the priority at the moment.

Well, I thought about it a while and I think that just letting React re-render does work in principle. But, it's quite inconvenient when you consider the other stuff that often happens in _default.page.client.tsx.
For example, I'm using GraphQL the way the example shows here. If I just let the page re-render, a whole new GraphQL client will be created using the page's original state. So I would have to take extra steps to pull out the current GraphQL client and/or state, and reuse it.
The same goes for preserving my app's Redux state, and every other wrinkle that occurs in a complex app.
I also think that doing a full React re-render is going to be expensive since it has to check the whole tree, though I haven't measured it yet.
Would you potentially accept a PR if I were to start hacking on the onBrowserHistoryNavigation function to make it more configurable?

I'm open for a PR but, before that, we'd need to settle on a feature/design that make sense.
 Correct me if I'm wrong but AFAICT you can actually already do what you want: adapt your render hook accordingly.
So instead of interecepting Vike's handling of the history push API, change your client-side render hook.

In the last week I did actually figure out a solution that works for me.
The solution was to move the creation of all stateful pieces (like the GraphQL client object, and the Redux store) into a React wrapper component wrapped around the app. They can be created in useState hooks. Then, you can pass the pageContext into this component and update these stateful things as needed with useEffect hooks.
I'm a little surprised this has worked as well as it has, but my current Frankenstein of Vike with react-router is passing all my tests.

Neat and makes sense. So I guess you're using some kind of cache mechanism (Redux/React?) to avoid a page re-render from triggering the rendering of all the page's components, correct?

Frankenstein of Vike

What makes you think that? Your setup seems legitimate to me. (As I was saying: AFAICT re-rendering the whole page while using a cache is idiomatic React usage.)

So I guess you're using some kind of cache mechanism (Redux/React?) to avoid a page re-render from triggering the rendering of all the page's components, correct?

It's just calling React's render function again with the given React nodes, on the same React root (which is defined at module scope so it will be reused). This is a fairly normal thing to do in React and the performance has been acceptable. I believe React does its DOM diffing magic over the entire tree.

What makes you think that? Your setup seems legitimate to me.

Well, it still troubles me that the onBrowserHistoryNavigation function is listening for window state changes, and so is my React router stuff. The code in there is rather complex and I can see that it may have at least one other side effect: calling setScrollPosition on certain hash changes. So I wouldn't want these two things stepping on each other.
I also have to be careful to use history.pushState in some situations and Vike's navigate function in others, which feels a little delicate.


fix: fixed incorrect calculation of image tokens for GTP-4o mini models

Resolves https://github.com/epam/ai-dial-adapter-openai/issues/165
Configuration changes
Added a new GPT4O_MINI_DEPLOYMENTS env var.
The migration procedure
Move gpt-4o mini deployments from GPT4O_DEPLOYMENTS to this new GPT4O_MINI_DEPLOYMENTS env var:
Conf before:
GPT4O_DEPLOYMENTS=gpt-4o-depl1,gpt-4o-depl2,gpt-4o-mini-depl1,gpt-4o-mini-depl2

Conf after:
GPT4O_DEPLOYMENTS=gpt-4o-depl1,gpt-4o-depl2
GPT4O_MINI_DEPLOYMENTS=gpt-4o-mini-depl1,gpt-4o-mini-depl2

/deploy-review


how do i use my own domain like seed1.exmaple.com

how do i use my own domain like seed1.exmaple.com
adding it in the ruweb.cnf doesn't seems to work.

nevermind forgot the /rutorrent.


loading vgg-face model and convert it to age, gender and race models

Age, Gender and Race models are using same VGG-Face infrastructure, instead of loading these giant models one by one, we may load VGG-Face once and update final layer weights. This will increase model loading time dramatically when all those models are available in actions.

Currently, vgg_face_weights.h5 is 580MB, but when I store the last 3 layers (conv2d_29, conv2d_30, predictions) weights, then it costs 480MB. So, it is not worth to do it! I still share how can I exclude last 3 layers weights in this ticket.
import numpy as np
import cv2
from deepface import DeepFace
from deepface.commons import functions as deepface_utils
from tensorflow.keras.models import Model, Sequential
from tensorflow.keras.layers import Convolution2D, Flatten, Activation

def findApparentAge(age_predictions) -> np.float64:
    output_indexes = np.array(list(range(0, 101)))
    apparent_age = np.sum(age_predictions * output_indexes)
    return apparent_age

vgg_model = DeepFace.build_model("VGG-Face")
age_model = DeepFace.build_model("Age")

classes = 101
base_model_output = Sequential()
base_model_output = Convolution2D(classes, (1, 1), name="predictions")(
    # -3 instead of -4!
    vgg_model.layers[-3].output
)
base_model_output = Flatten()(base_model_output)
base_model_output = Activation("softmax")(base_model_output)
age_model_v2 = Model(inputs=vgg_model.input, outputs=base_model_output)

def compare_layer_weights(model1, model2):
    for layer1, layer2 in zip(model1.layers, model2.layers):
        weights1 = layer1.get_weights()
        weights2 = layer2.get_weights()

        if len(weights1) != len(weights2):
            print(f"Layer {layer1.name} has different number of weight sets.")
        else:
            for w1, w2 in zip(weights1, weights2):
                if not np.array_equal(w1, w2):
                    print(f"Weights of layer {layer1.name} are not the same.")
                    break
            #else:
            #    print(f"Weights of layer {layer1.name} are the same.")

compare_layer_weights(age_model, age_model_v2)

final_layers_model1 = age_model.layers[-7:]
final_layers_model2 = age_model_v2.layers[-7:]
# for layer1, layer2 in zip(final_layers_model1, final_layers_model2):
#     layer2.set_weights(layer1.get_weights())

age_weights = {}
for i, layer in enumerate(final_layers_model1):
    age_weights[f'layer_{i + 1}_weights'] = layer.get_weights()
np.save('age_weights.npy', age_weights)

for i, layer2 in enumerate(final_layers_model2[-7:]):
    layer2.set_weights(age_weights[f'layer_{i + 1}_weights'])

faces = deepface_utils.extract_faces("target.jpg", target_size=(224, 224))
img = faces[0][0]
second_result = age_model_v2.predict(img)

result_new = findApparentAge(second_result)
result_old = DeepFace.analyze("target.jpg", actions=("age"))[0]["age"]

assert abs(result_old - result_new) < 1

here, age_weights.npy costs 480 MB. So, I gave up to do this ticket!


Merge recent changes into stable

It's been a while since the stable branch gets updated. Merge all new changes release 2.4.0 to stable

Do you mind adding a doc (maybe interally?) saying why this is necessary - why just making a release isn't good enough?

It's already documented:
A Copybara job will run automatically whenever commit is made to the `stable` branch of android-browser-helper.


Wrong order of mac and data for Aead.Xchacha20poly1305Ietf.decrypt()

Currently calls to Salty.Aead.Xchacha20poly1305Ietf.decrypt() always fail. Calls to Salty.Aead.Xchacha20poly1305Ietf.decrypt_detached() work as expected. This is probably caused by the following code in lib/salty/aead.ex which extracts the tag (mac) and data in a wrong order. IIRC in combined mode mac comes after the payload.
      def decrypt(nsec, cipher, ad, npub, key) do
        mac_size = abytes()
        <<mac::binary-size(mac_size),
          data::binary>> = cipher
        decrypt_detached(nsec, data, mac, ad, npub, key)
      end

You are correct, the libsodium source files indicate that the location of the MAC is after the data.
Should be fixed now, thanks!


Buffer plugin not respecting retry_forever true

The company I work for deals with PHI (Protected Health Information). As such, we must keep extensive logs for auditing purposes with local, state, and federal governments. We send logs ingested by fluentd to our proprietary database engine from which our customers run various analytical reports in order to have daily audit reports on the data that their clients have viewed.
When the system is under heavy load, our database engine may fail to receive the records from fluentd. The http_buffered plugin properly receives these errors and retries (using the exponential backoff). It appears that sometimes, fluentd is dropping chunks after 18 failed retries even though we clearly have retry_forever true.
I discovered this after we had reports from customers that some days are missing obvious amounts of log records when they run their daily audit reports. After some investigation, I am seeing the following error message in our fluentd log file:
[error]: failed to flush the buffer, and hit limit for retries. dropping all chunks in the buffer queue. plugin_id="object:16d9560" retry_times=18 records=1290207 error_class=Net::ReadTimeout error="Net::ReadTimeout

As the log message states, it's dropping almost 1.3 million records. That is an insane amount of information being lost. Luckily, restarting fluentd causes it to reprocess the log files and resend the information. It would be nice if we could just trust that retry_forever would actually just retry forever so we wouldn't have to burn through disk I/O and CPU by re-reading massive files.
Here's our fluentd config:
# System-wide configuration options
<system>
  # Configure the number of workers (AKA processes) that fluentd runs
  workers 11
  # Configure where the data for each worker is stored
  root_dir "/var/log/fluentd"
</system>

# We can set up certain plugins to only work on 1 worker process.
# This needs to be done for the tailing plugin since it only works on one
# thread at a time due to the position file (otherwise it would get clobbered)

##
## NOTE:
##       In order to increase the speed that fluentd processes files
##       (especially when large files are present), split up the processing
##       across multiple threads (each has to have a different position file).
##

# Set up processes that run only on worker 0
<worker 0>
  <source>
    @type tail

    # Tag all records from this plugin with this (used for routing the records)
    tag logentry.middleware

    # Read the files starting from the beginning and work to the end (normal
    # behavior starts at the end and continues from their)
    read_from_head true

    # This option is needed when read_from_head is true because of a bug in the
    # tailing plugin. When reading from head, this plugin begins reading files
    # during its startup phase. As such, it will not register as fully
    # "started" until after it finished reading every single file. This means
    # log records are not fed until after everything has been processed (which
    # can take days or weeks when there are a lot of logs). Having this set to
    # true will allow other plugins to start, while waiting to begin processing
    # log files until the first watch event (default: 60 seconds)
    skip_refresh_on_startup true

    # The paths to watch and process
    path /opt/search/appliance5/logs/ps-usage.[0-9]0*.log

    # The file that tracks the bytes that have been read and the inode of each
    # file being watched/processed (used to prevent redundant processing when
    # restarting the service and to detect file rotation)
    pos_file /opt/search/appliance5/logs/ps-usage.worker0.log.pos

    # Fluentd reads a batch of lines at a time, the amount of data in the batch
    # of lines MUST be less than the chunk_limit_size (in the <buffer> section
    # at the end of the file)
    read_lines_limit 1

    # This regex allows the timestamp to be preserved in fluentd, as well as the log level
    <parse>
      @type regexp
      expression /(?<logEntry>{.*)/
    </parse>

    # This option will default to false in the future because it reduces CPU
    # usage and I/O consumption and testing shows everything works normally
    # with it disabled anyways
    enable_watch_timer false
  </source>
</worker>
# END worker 0 config

# Set up processes that run only on worker 1
<worker 1>
  <source>
    @type tail

    tag logentry.middleware

    read_from_head true

    skip_refresh_on_startup true

    path /opt/search/appliance5/logs/ps-usage.[0-9]1*.log

    pos_file /opt/search/appliance5/logs/ps-usage.worker1.log.pos

    read_lines_limit 1

    <parse>
      @type regexp
      expression /(?<logEntry>{.*)/
    </parse>

    enable_watch_timer false
  </source>
</worker>
# END worker 1 config

# Workers 2-10 have nearly identical configs as worker 1 (with only different paths and pos_file)

# This plugin converts the JSON log entries to XML, assigns a category, and
# filters out the logs matching a no_log type
<filter logentry.**>
  @type psxml
  # A comma-separated list of log_types that should not be indexed to searchserver
  no_log_types BulkETL

  # The key name where log records are stored in the fluentd objects (This will
  # have to match the named regex, as configured in the tailing plugins, that
  # contains the log entry)
  record_key logEntry
</filter>

# This plugin feeds batches of records to the searchserver
<match logentry.**>
  # id is needed for multiprocessing with the file buffer
  @id http_buffered
  @type http_buffered

  # Where to send the records (Ruby date string formatters are allowed)
  endpoint_url http://localhost:30000/cache/addrecords?store=%Y
  # Statuses that mean we should retry sending the records
  http_retry_statuses 500, 403, 404, 400
  # How long to wait for a connection to be made to the endpoint
  http_read_timeout 60
  # How long to wait for a response, after a connection has been made
  http_open_timeout 30

  # How long each connection in the pool should be kept alive
  http_keep_alive_timeout 600
  # How many connections are kept in the pool
  http_pool_size 5

  # Do not add a record to the data to send unless it contains each of these strings
  record_contains <ps:record, <log_entry>, </log_entry>, </ps:record>

  # Stores data to be sent in buffers
  <buffer>
    # The buffers are kept in files located at the <system> root_dir/workerN/http_buffered
    @type file

    # How often to check and see if there is any buffer data to send
    flush_interval 30s
    # How many threads can be open for flushing data
    flush_thread_count 11

    # How large each chunk in the buffer can be
    chunk_limit_size 15m
    # How large the buffer size can reach per worker (multiply this number by
    # the number of workers to get the total max buffer size)
    total_limit_size 1g

    retry_max_interval 600

    # If a chunk fails to be flushed, keep retrying until it succeeds
    retry_forever true
  </buffer>
</match>

Let me know if you need any additional information.

My mistake. The logs I were given were apparently from before we upgraded to fluentd 1.1.0 and so there was no retry_forever parameter


lib.systems: add gnuabin32 to isGnu

Description of changes
The isGnu predicate was missing gnuabin32.  This commit corrects that by adding it.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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.11 Release Notes (or backporting 23.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.

I'm going to self-merge this without a review because (a) it is trivial and (b) I think I am the only person who cares about the obscure ILP32 ABI on mips.


Harbor issues

[ ] We should probably rename the default project from library to something more descriptive like neonkube or cluster.

[ ] AccessLevel for this project is Public.  Seems like this should be private, using the SSO credentials.  Users who really need a public project should create a new one, right?

We're leaving this as is.


default: Use updated CDN versions of libraries

Saves you the hassle of having to manage a local copy of the libraries.

Thanks fam


Fix some typos in AsyncThrowingStream.swift docs

nomally -> normally

@swift-ci please smoke test and merge


erro message when downloading

I have youtube-dl version 2021.12.17. When running:
youtube-dl "https://www.youtube.com/watch?v=ymSq4wHrqyU"
I got:
[youtube] ymSq4wHrqyU: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Ya. i have this is problem to.
I'm using my music bot in discord, and his can't load any music from youtube. ChatGPT sayd me - "This is problem with update, if you have latest version, go to (github of creator) for sayd about this bug"

Same issue.
Steps to reproduce :

youtube-dl --verbose --no-check-certificate

Actual Result :
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', '--no-check-certificate', 'https://www.youtube.com/watch?v=IzlIBgN_qYs']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.11.1 (CPython) - macOS-13.0-arm64-arm-64bit
[debug] exe versions: none
[debug] Proxy map: {}
[youtube] IzlIBgN_qYs: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/Users/neo/Dropbox/scripts/tools/youtube-dl/youtube_dl/YoutubeDL.py", line 815, in wrapper
return func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/neo/Dropbox/scripts/tools/youtube-dl/youtube_dl/YoutubeDL.py", line 836, in __extract_info
ie_result = ie.extract(url)
^^^^^^^^^^^^^^^
File "/Users/neo/Dropbox/scripts/tools/youtube-dl/youtube_dl/extractor/common.py", line 534, in extract
ie_result = self._real_extract(url)
^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/neo/Dropbox/scripts/tools/youtube-dl/youtube_dl/extractor/youtube.py", line 1794, in _real_extract
'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/neo/Dropbox/scripts/tools/youtube-dl/youtube_dl/extractor/common.py", line 1012, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Learn how to search the open issues, FFS
https://github.com/ytdl-org/youtube-dl/issues/30839

The issue obviously hasn't been sorted on a large scale, or else the error wouldn't keep popping up. I'm not a coder, developer or otherwise, and I've had to try and navigate this insane platform to try and find out why I couldn't download audio clips for training references.
HOW can this issue be corrected for those of us with limited cranial capacity for ones and zeros who simply want to explain to lesser developed craniums what health and safety in the workplace is by adding a YOUTUBE download to refer people to when they hurt themselves because they have no systematic discipline towards their surroundings, and if I have to listen to one more "catch up" about this topic I can see myself practising defenestration.


Fix dependencies and warnings

Bumping gl_generator to 0.14.0 seems to fix #1
If you also push to crates.io, I could also submit a PR for the lessons.
I also fixed warnings while at it.

Sorry, this was long overdue, but oh well.


Add a Vue example

Should we add a Vue client to the examples?
It should only be integrated into this repository if it does not bring a ton of dependencies (like Angular) and fits the overall dev approach with vite. But with VueI am positive it will work. Otherwise, it could live in an external repo.

I think we can pay attention to language-tools(volar).
I am also trying to add a Vue3 language on Monaco. I think this is helpful.

Hi @RSS1102 can you be more specific?

Hi @RSS1102 can you be more specific?

This is my personal understanding：
Each language has its own pattern, and Vue is no exception. In order to increase portability, such as compatibility with Vue systems such as vscode/vitepress, a separate warehouse has been developed for Vue.

this is vue-language-configuration.json,Here are the key strings for the Vue language.
@volar/monaco, is used to bridge the language capabilities implemented based on Volar.js to Monaco Editor.

https://github.com/Kingwl/monaco-volar ,
There is an example code here, but I don't think it is perfect, there are too many dependencies, and many features are outdated. I personally think that all you need is the vue-language-configuration.json file,and the rest needs to be done by ourself.
I personally believe that these functions mainly support:

Vue language support.
Language highlighting
Vue worker.

But I don't have enough understanding to implement it yet. But I am still working hard.

My understanding is that volar helps to ease building languageservers / languageclient. What we gain with @codingame/monaco-vscode-api is there is no more monaco-editor related fiddling needed as it behaves like it is running inside vscode. So monaco-volar is not needed as you can just use your languageclient implementation. @CGNonofr anything to correct or add here?

Yes, so maybe it's just a need for vue-language-configuration.json,i think.

Yes that and a textmate grammar. That is what we load for the Langium Statemachine DSL as well: https://github.com/TypeFox/monaco-languageclient/blob/main/packages/examples/src/langium/statemachineClient.ts#L77-L78
(The references are used in the extension configuration (a few lines above).

Okay, thank you. I'll give it a try this weekend.


FEAT: support more than one output image per input image

For the image batch extension, this change makes it so that when a workflow produces more than one output image for an input image, the output images after the first will be appended with a _1 _2 etc.  For example:
input -> output
File1.png -> File1.png, File1_1.png, File1_2.png   // for three generated images
File2.png -> File2.png   // only one output
File3.png -> File3.png, File3_1.png  // two generated
Addresses Issue https://github.com/mcmonkeyprojects/SwarmUI/issues/494

The code here is still wrong (the if check is redundant)
But more importantly, I realize a bit late - this code section is potentially multithreading sensitive, and needs a solution written with an understanding of thread-safe coding. I was wrong to have put an Easy PR label on that issue, my mistake there, I didn't realize that would apply.
I've gone ahead and implemented it correctly myself via the commit above


Infraction listing for permanent infractions lists "expired" time remaining

A permanent infraction will have its "Remaining" attribute displayed as "Expired" due to the following line of code:
https://github.com/python-discord/bot/blob/5df2fa2f948852826322409103c91565390110fe/bot/exts/moderation/infraction/management.py#L264
Remaining is "None" not because it has expired, but because there is no defined time remaining for an infraction that is not scheduled to expire. Previously, there was a suggestion in issue #668:

For fun, we could put (∞) next to permanent infractions.

I think this could be a good choice here. It's also unlikely to introduce much complexity, since all that's needed is an additional case to the "time remaining" if statement to handle unexpired permanent infractions.

@bast0006 After testing this on the master branch of the bot, it seems that this is no longer a problem. All permanent infractions show up as "permanent" instead of "expired".
Once I find which PR fixed this, I will update this comment.

@bast0006 After testing this on the master branch of the bot, it seems that this is no longer a problem. All permanent infractions show up as "permanent" instead of "expired".
Once I find which PR fixed this, I will update this comment.

This has not yet been fixed.

This has not yet been fixed.

I was looking at the wrong field, sorry about that.

I was looking at the wrong field, sorry about that.


Add support for LPC54608

Signed-off-by: Mahadevan Mahesh<EMAIL_ADDRESS>

@c1728p9 Can this be integrated into pyOCD. The DAPLink support is also available.

/morph test

@c1728p9 Anything else needed for this PR?

/morph test

Can this be merged?

Hi @mmahadevan108 please run the automated tests locally on this target. To run these use the command python test/automated_test.py. I'm seeing some failures on the LPC54608 when I run it locally.

Hi @c1728p9 . Can this be merged into the mainline

/morph test


[CLASS][ARCHETYPE] "Profane Commandment" from Dread knight Conqueror Archetype is not scaling with levels nor charisma modifier

Hello,
I have found a class-breaking issue regarding the Conqueror dread knigh archetype
It seems the "Profane Commandment" class feature from Dread knight Conqueror Archetype is not scaling with levels nor charisma modifier.
Step to repro :

Create a Dreadkight - Conqueror character with more than 14 Charisma (MC / Mercenary / Companion respec from scratch it doesn't matter)
1.1) Note the "Inspired Rage" feature is locked on 4 charges instead of (3+Cha.modif)
Level up the character
Note the "Inspired Rage" feature is locked on 4 charges instead of (3+2/level+Cha.modif)

Result
it seems the charges of Inspired Rage are not scaling accordingly with the class tooltip (that should duplicate the Skald scaling as 3+2/level+Cha.modif).
Observations :
Note this bug apply for all Conqueror's raging song like Dirge of Doom and so on. Not only the Inspire Rage one.
Additional infos
You will find some screenshot for my game to witness the actual issue (with green-scared higlighted infos).
On my personal run, the issue is occuring on a full respec. Regill .
Best regards and thx you for this wonderful mod

A random QA Analyst

I'll see if I can get this sorted for the next update.
Thanks for the extremely clean bug report!

Will be fixed for a release later tonight.
Can't test properly due to my location so I'll leave the ticket open until you confirm it works as intended.


moved path matching & reverse to special static class PathMatcher

What is the motivation behind this? I miss any description or example or use case you're in.

all this PathMatcher thing is good to decouple string matching from actually matching requests. with the proposed interface you can use also some other string matching patterns


better breakindent for numbered/bulleted lists

Detecting bulleted or numbered lists and applying an additional indentation for soft-wrapping is a bit of a popular request (see #1661). So here is a PR, that implements this. It makes use of the 'formatlistpat' option setting to detect such lines and if they match, Vim applies an additional indent, that can be specified using :set breakindentopt+=list:{n}. By default this is not set. This works currently best in combination with the 'linebreak' setting.
It also adds some tests to make sure it works correctly and also adds some documentation.

Thx for the patch, Christian!
I wonder if it is possible to have "dynamic" list:{n} ?
There are lists that are common in asciidoc format where sublilst level could be defined as a sequence of *:

With current implementation it is only possible to define a single indent for all list items but not per "level".
I am not sure if it is possible to capture what was in formatlistpat and count the length and use it somehow?
Anyway even with current impl it is better than it was before, thank you again!
PS, formatlistpat I use for asciidoc:
set wrap breakindent briopt+=list:2
let &formatlistpat = '^\s*[\[({]\?\([0-9]\+\|[a-zA-Z]\)[\]:.)}]\s\+\|^\s*-\s\+\|^\s*[*]\+\s\+\|^\s*[.]\+\s\+'

Hm, it might be possible. If you use the formatlistpat on such a line using len(matchstr(&formatlistpat, line)) does that return the length of the indent you need?

Hm, it might be possible. If you use the formatlistpat on such a line using len(matchstr(&formatlistpat, line)) does that return the length of the indent you need?

Nope, it reports:

lol we have used wrong position of the args

Hm, it might be possible. If you use the formatlistpat on such a line using len(matchstr(&formatlistpat, line)) does that return the length of the indent you need?

echo len(matchstr(getline(1), &formatlistpat))

returns 5 ^^^^, which is 1 char less than needed but that should be covered by `list:1` then.

I was more thinking, that when using briopt=list:-1 use the indent that formatlistpat matches. Not sure if this really makes sense for the normal formatlistpat usage.

I was more thinking, that when using briopt=list:-1 use the indent that formatlistpat matches. Not sure if this really makes sense for the normal formatlistpat usage.

Hmm, you are right -- I don't have to add anything to indent:

To be clear, yes, using indent of the matched formatlistpat should be ok


Extension causes high cpu load

Issue Type: Performance
Extension Name: code-spell-checker
Extension Version: 1.6.10
OS Version: Linux x64 4.15.0-47-generic
VSCode version: 1.33.0

:warning: Make sure to attach this file from your home-directory:
:warning:/home/cesar/streetsidesoftware.code-spell-checker-unresponsive.cpuprofile.txt
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Dupe of #309


Codeowners: update teams and add entry for GNOME

Motivation for this change
Alas, we need to manually keep our teams in sync with this file. See #124085. Also added an entry for GNOME and the extensions.

@saschagrunert, @adisbladis, @vdemeester: Heads up, you just got added to the file.
@jtojnar, @hedning: I added the GNOME team to /pkgs/desktops/gnome and myself for /pkgs/desktops/gnome/extensions.
@NixOS/darwin-maintainers: You are the only team left whose entries are broken. This affects /pkgs/stdenv/darwin and /pkgs/os-specific/darwin. I did not want to add over 30 people to the list, so please deal with this in a separate PR.

I did not want to add over 30 people to the list, so please deal with this in a separate PR.

Isn't it then just better to grant write access for the team?

Isn't it then just better to grant write access for the team?

Maybe? I don't know what the policies on this are. I know that teams with write access can only have members with write access, and that only the security team has write access at the moment.

I'm working on the Darwin stdenv but I don't have write-access so I can't be a codeowner. Maybe @thefloweringash, @copumpkin, @LnL7? I'm not sure anyone has time for the responsibility though.

Apparently @saschagrunert and @vdemeester don't have commit access at the moment. How should we deal with this?

FWIW, our experience with the Coq project has been to define a pushers team (equivalent to the committers team here) which has as many subteams as there are components (and being a member of a subteam automatically grants you write access). For a screenshot illustrating this, see Figure 3.4 in Section 3.7 of my PhD thesis. A benefit of this approach is that when one of the team members reviews a PR, the review request disappears for all the team members.


Introduce transform dialect Op for ukernel

This PR adds a new iree.microkernel_gpu_matmul transform dialect op to IREE. The purpose of this op is to take the linalg.matmul op whose outermost two loops are already tiled and lower into ukernel op. In order to use the op, one will need to pass a tile size for the last loop, as well as specify software pipeline stages.
The main functionality of the op is to call an existing pattern to generate a ukernel.generic  op.
Overall, this PR provides microkernel support to the transform dialect, and I believe it will be a useful tool for developers working on GPU-based projects.

Closing stale PR.


When I teleport i get stuck in the air

Closing as this is pretty old - sorry for not replying sooner - and is likely a vanilla bug


Backwards compatibility for renamed contrib modules

This adds backwards compatibility for the renamed contrib modules. A custom module loader is used that catches imports of wagtail.contrib.wagtail* modules, raises a DeprecationWarning, and imports the new prefix-free version instead.
This commit is intended to replace commits 74590f2..0a61806

Getting the following error on wagtaildemo:
Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/home/karl/projects/wagtaildemo/venv/lib/python3.5/site-packages/django/core/management/__init__.py", line 338, in execute_from_command_line
    utility.execute()
  File "/home/karl/projects/wagtaildemo/venv/lib/python3.5/site-packages/django/core/management/__init__.py", line 312, in execute
    django.setup()
  File "/home/karl/projects/wagtaildemo/venv/lib/python3.5/site-packages/django/__init__.py", line 18, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/home/karl/projects/wagtaildemo/venv/lib/python3.5/site-packages/django/apps/registry.py", line 115, in populate
    app_config.ready()
  File "/home/karl/projects/wagtaildemo/venv/lib/python3.5/site-packages/django/contrib/admin/apps.py", line 22, in ready
    self.module.autodiscover()
  File "/home/karl/projects/wagtaildemo/venv/lib/python3.5/site-packages/django/contrib/admin/__init__.py", line 24, in autodiscover
    autodiscover_modules('admin', register_to=site)
  File "/home/karl/projects/wagtaildemo/venv/lib/python3.5/site-packages/django/utils/module_loading.py", line 74, in autodiscover_modules
    import_module('%s.%s' % (app_config.name, module_to_search))
  File "/home/karl/projects/wagtaildemo/venv/lib/python3.5/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 986, in _gcd_import
  File "<frozen importlib._bootstrap>", line 969, in _find_and_load
  File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 664, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 634, in _load_backward_compatible
  File "/home/karl/projects/wagtail/wagtail/utils/renames.py", line 51, in load_module
    module = self._load_module(new_fullname)
  File "/home/karl/projects/wagtail/wagtail/utils/renames.py", line 65, in _load_module
    __import__(fullname)
ImportError: No module named 'wagtail.contrib.searchpromotions.admin'

It looks like it's because I still have a wagtailsearchpromotions folder which git didn't remove (deleting this fixed it).

Having left over .pyc/pycache files messes up many things, not just this custom loader. I dont think there is a way around this, as the actual problem is much lower level than Wagtail. I dont think it is a reason to not do this either, though, as this will only affect some people using Wagtail through git.

:+1:


Submaps poor quality

Hello.
I am using cartographer with a rotating planar 2d LIDAR. The thing is that the submaps are really poor. Besides the system does not close the loop.
I saw that the Z axis decreases continuously even though the robot is moving in a planar floor.
Any idea why is this happening?
These are the results of rosbag validation are showed below:
W0509 11:56:48.749516 15162 rosbag_validate_main.cc:103] frame_id imu_link time<PHONE_NUMBER>829814862: IMU linear acceleration is 0.458578 m/s^2, expected is [3, 30] m/s^2. (It should include gravity and be given in m/s^2.) linear_acceleration 0.0434229 -0.228816 00.395034
E0509 11:56:48.749853 15162 rosbag_validate_main.cc:326] frame_id "imu_link" is send on multiple topics. It was seen at least on /sensors/imu and /sensors/imu_raw
W0509 11:56:48.750057 15162 rosbag_validate_main.cc:352] frame_id "foxizuyo_hokuyo" on topic /foxizuyo/scan has serialization time<PHONE_NUMBER>.912360266 but sensor time<PHONE_NUMBER>.789593280 differing by -0.122767 s.
W0509 11:56:48.750074 15162 rosbag_validate_main.cc:103] frame_id imu_link time<PHONE_NUMBER>842995174: IMU linear acceleration is 0.230427 m/s^2, expected is [3, 30] m/s^2. (It should include gravity and be given in m/s^2.) linear_acceleration 000.156535 -0.0262548 000.167045
W0509 11:56:48.750098 15162 rosbag_validate_main.cc:103] frame_id imu_link time<PHONE_NUMBER>859665360: IMU linear acceleration is 0.841206 m/s^2, expected is [3, 30] m/s^2. (It should include gravity and be given in m/s^2.) linear_acceleration 0.028564 00.46092 0.703111
E0509 11:56:48.750174 15162 rosbag_validate_main.cc:315] Sensor with frame_id "imu_link" jumps backwards in time. Make sure that the bag contains the data for each frame_id sorted by header.stamp, i.e. the order in which they were acquired from the sensor.
E0509 11:56:48.750187 15162 rosbag_validate_main.cc:326] frame_id "imu_link" is send on multiple topics. It was seen at least on /sensors/imu and /sensors/imu_raw
E0509 11:56:48.750205 15162 rosbag_validate_main.cc:315] Sensor with frame_id "imu_link" jumps backwards in time. Make sure that the bag contains the data for each frame_id sorted by header.stamp, i.e. the order in which they were acquired from the sensor.
E0509 11:56:48.750217 15162 rosbag_validate_main.cc:326] frame_id "imu_link" is send on multiple topics. It was seen at least on /sensors/imu and /sensors/imu_raw
E0509 11:56:48.750239 15162 rosbag_validate_main.cc:315] Sensor with frame_id "imu_link" jumps backwards in time. Make sure that the bag contains the data for each frame_id sorted by header.stamp, i.e. the order in which they were acquired from the sensor.
E0509 11:56:49.294574 15162 rosbag_validate_main.cc:365] Average IMU linear acceleration is 5.9268 m/s^2, expected is [9.5, 10.5] m/s^2. Linear acceleration data should include gravity and be given in m/s^2.
I0509 11:56:49.294968 15162 rosbag_validate_main.cc:398] Time delta histogram for consecutive messages on topic "/foxizuyo/scan" (frame_id: "foxizuyo_hokuyo"):
Count: 8905  Min: 0.027727  Max: 0.040933  Mean: 0.033686
[0.027727, 0.029048)	                    	Count: 33 (0.370578%)	Total: 33 (0.370578%)
[0.029048, 0.030368)	               #####	Count: 2114 (23.739471%)	Total: 2147 (24.110050%)
[0.030368, 0.031689)	                  ##	Count: 710 (7.973049%)	Total: 2857 (32.083099%)
[0.031689, 0.033009)	                   #	Count: 662 (7.434026%)	Total: 3519 (39.517124%)
[0.033009, 0.034330)	                ####	Count: 1778 (19.966311%)	Total: 5297 (59.483437%)
[0.034330, 0.035651)	                  ##	Count: 1077 (12.094329%)	Total: 6374 (71.577766%)
[0.035651, 0.036971)	                 ###	Count: 1512 (16.979225%)	Total: 7886 (88.556992%)
[0.036971, 0.038292)	                   #	Count: 520 (5.839416%)	Total: 8406 (94.396408%)
[0.038292, 0.039612)	                    	Count: 90 (1.010668%)	Total: 8496 (95.407074%)
[0.039612, 0.040933]	                   #	Count: 409 (4.592926%)	Total: 8905 (100.000000%)
E0509 11:56:49.295166 15162 rosbag_validate_main.cc:389] IMU data (frame_id: "imu_link") has a large gap, largest is 0.0534519 s, recommended is [0.0005, 0.005] s with no jitter.
I0509 11:56:49.296026 15162 rosbag_validate_main.cc:398] Time delta histogram for consecutive messages on topic "/sensors/imu" (frame_id: "imu_link"):
Count: 48309  Min: -0.040272  Max: 0.053452  Mean: 0.006210
[-0.040272, -0.030899)	                    	Count: 2 (0.004140%)	Total: 2 (0.004140%)
[-0.030899, -0.021527)	                    	Count: 1 (0.002070%)	Total: 3 (0.006210%)
[-0.021527, -0.012155)	                    	Count: 0 (0.000000%)	Total: 3 (0.006210%)
[-0.012155, -0.002782)	                    	Count: 0 (0.000000%)	Total: 3 (0.006210%)
[-0.002782, 0.006590)	         ###########	Count: 27754 (57.450993%)	Total: 27757 (57.457203%)
[0.006590, 0.015963)	           #########	Count: 20544 (42.526237%)	Total: 48301 (99.983437%)
[0.015963, 0.025335)	                    	Count: 6 (0.012420%)	Total: 48307 (99.995857%)
[0.025335, 0.034707)	                    	Count: 0 (0.000000%)	Total: 48307 (99.995857%)
[0.034707, 0.044080)	                    	Count: 1 (0.002070%)	Total: 48308 (99.997932%)
[0.044080, 0.053452]	                    	Count: 1 (0.002070%)	Total: 48309 (100.000000%)
I0509 11:56:49.296891 15162 rosbag_validate_main.cc:398] Time delta histogram for consecutive messages on topic "/odometry/loc" (frame_id: "odom"):
Count: 29973  Min: 0.000000  Max: 0.031161  Mean: 0.010008
[0.000000, 0.003116)	              ######	Count: 8251 (27.528109%)	Total: 8251 (27.528109%)
[0.003116, 0.006232)	                   #	Count: 923 (3.079438%)	Total: 9174 (30.607546%)
[0.006232, 0.009348)	                   #	Count: 1342 (4.477363%)	Total: 10516 (35.084911%)
[0.009348, 0.012464)	                  ##	Count: 3051 (10.179161%)	Total: 13567 (45.264072%)
[0.012464, 0.015580)	               #####	Count: 8094 (27.004303%)	Total: 21661 (72.268372%)
[0.015580, 0.018696)	               #####	Count: 7465 (24.905748%)	Total: 29126 (97.174126%)
[0.018696, 0.021813)	                    	Count: 584 (1.948420%)	Total: 29710 (99.122543%)
[0.021813, 0.024929)	                    	Count: 158 (0.527141%)	Total: 29868 (99.649681%)
[0.024929, 0.028045)	                    	Count: 98 (0.326961%)	Total: 29966 (99.976646%)
[0.028045, 0.031161]	                    	Count: 7 (0.023354%)	Total: 29973 (100.000000%)
And my backpack 3d.lua:
options = {
map_builder = MAP_BUILDER,
trajectory_builder = TRAJECTORY_BUILDER,
map_frame = "map",
tracking_frame = "imu_link",
published_frame = "base_link",
odom_frame = "odom",
provide_odom_frame = true,
publish_frame_projected_to_2d = false,
use_odometry = false,
use_nav_sat = false,
use_landmarks = false,
num_laser_scans = 1,
num_multi_echo_laser_scans = 0,
num_subdivisions_per_laser_scan = 1,
num_point_clouds = 0,
lookup_transform_timeout_sec = 0.2,
submap_publish_period_sec = 0.3,
pose_publish_period_sec = 5e-3,
trajectory_publish_period_sec = 30e-3,
rangefinder_sampling_ratio = 1.,
odometry_sampling_ratio = 0.3,
fixed_frame_pose_sampling_ratio = 1.,
imu_sampling_ratio = 1.,
landmarks_sampling_ratio = 1.,
}
TRAJECTORY_BUILDER_3D.submaps.num_range_data = 10
TRAJECTORY_BUILDER_3D.num_accumulated_range_data = 12
MAP_BUILDER.use_trajectory_builder_3d = true
MAP_BUILDER.num_background_threads = 7
POSE_GRAPH.optimization_problem.huber_scale = 5e2
POSE_GRAPH.optimize_every_n_nodes = 10
POSE_GRAPH.constraint_builder.sampling_ratio = 0.01
POSE_GRAPH.optimization_problem.ceres_solver_options.max_num_iterations = 10
POSE_GRAPH.constraint_builder.min_score = 0.62
POSE_GRAPH.constraint_builder.global_localization_min_score = 0.66

But shouldn't 3D SLAM work with a rotating LIDAR? I am able to localize the robot , the problem is just the loop closure and the Z axis (This one might by caused by the IMU data).
The thing that worries me the most is the poor quality of the submaps, then the /map (projected map in 2D) is not generated

But shouldn't 3D SLAM work with a rotating LIDAR?

If you mean a 2D lidar that is tilting so its laser plane rotates up and down, yes.
But a tilting 2D lidar is hard to calibrate and configure correctly.
In that case, you would need an accurate tf publisher of the tilted lidar transform and have a flawless urdf config (which you haven't posted yet).

loop closure

First tune local slam alone and make sure your submaps look good. Please see the tuning guide how to tune local slam alone.

closing, as inactive for a long time


Use Protoc-Gen-Doc for protocol documentation

We've been commenting to their style guide, might as well generate readable documentation within this repo!
https://github.com/pseudomuto/protoc-gen-doc

@tyeth  Would you be interested in setting protoc-gen-doc up on this repository? We'd push the documentation it generates (only generated for master branch) to a docs/ folder on this repository.
The timebox would be about half a day of work.
Bonus Quest:  Generate and publish the HTML documentation pages on github pages

Documentation is located here: https://adafruit.github.io/Wippersnapper_Protobuf/


update dependencies

This is actually quite an import change (specifically the psr/log change) because users of Monolog cannot upgrade to Monolog 3.x with this package installed.

@neomerx this was merged with the broken version constraint. Users who are otherwise stuck on psr/log 1.x (or 2.x) won't be able to upgrade.

Never mind, I see that #41 was also merged. 👍🏼


Controllers

✔   For each URL I  create:
 ▶  A route.
  ▶  An action in the correct controller.
  ▶ A view file.

✔  I include only placeholders written in plain HTML
✔  I Make sure that I  added code to handle only the 4 required URLs.
✔ I Make sure that when I  run the rails routes command in your console


TAVOSS-TR:Spring-security

Version of the project
5.6.0-M1
Tech Stack
Application [A]
Project details
Spring Security provides security services for the Spring IO Platform
Languages used
Java
Domain
Both
Industry
All
Open Source Project type
Community led
Repo URL
https://github.com/spring-projects/spring-security
Webpage
https://spring.io/
License
Apache-2.0
Other license
No response
Why we should track it.
Spring Security provides security services for the Spring IO Platform

This project is accepted for tracking hence closing this issue with status as Tracked


[Bug]: OpenSearch randomly refuses to start on GitHub Actions with absolutely no error logs

Describe the bug
In the CI workflow (GHA) we use OpenSearch 1.2.4. Sometimes it refuses to start. Also we can't even see any logs from it.
To reproduce
Create a workflow with the following content:
name: ci

on:
  push:
    branches: [master]
  pull_request:

jobs:
  test:
    runs-on: ubuntu-latest

    services:
      opensearch:
         image: opensearchproject/opensearch:1.2.4 # we actually use our private custom image based on v1.2.4 where we just install mapper-murmur3 plugin
         ports:
           - "9200:9200"
         env:
           OPENSEARCH_JAVA_OPTS: "-Xms4096m -Xmx4096m"
           bootstrap.memory_lock: true
           discovery.type: "single-node"
           DISABLE_INSTALL_DEMO_CONFIG: true
           DISABLE_SECURITY_PLUGIN: true
           rootLogger.level: "DEBUG"
           logger.level: "DEBUG"
           logger._root: "DEBUG"
           logger.org.opensearch.index.reindex: "DEBUG"
           logger.org.opensearch.action: "DEBUG"
           logger.org.opensearch.action.admin.cluster.health: "DEBUG"
         options: >-
           --cap-add IPC_LOCK
           --ulimit nofile=65536:65536
           --ulimit memlock=-1:-1
           --restart always
    steps:
      # different sources suggest to tune system with sysctl for better OS stability
      - name: Configure environment
        run: |
          sudo swapoff -a
          sudo sysctl -w vm.swappiness=1
          sudo sysctl -w fs.file-max=262144
          sudo sysctl -w vm.max_map_count=262144

      # this step should restart OpenSearch, wait for 20 seconds, then render OS container logs and check OS connectivity by making a request with curl
      - name: Restart OpenSearch
        run: |
          docker restart "${{ job.services.elastic.id }}"
          sleep 20
          docker logs "${{ job.services.elastic.id }}" 1>&2
          curl --output /dev/null --silent --head --fail 'http://localhost:9200'
      ...

Expected behavior
OpenSearch service starts successfully.
Screenshots
No response
Host / Environment
GitHub Actions runner (Ubuntu 22.04)
Additional context
As you may see in the "To reproduce" section, we added two extra GHA steps in attempt to fix OS service startup and also to at least be able to see some error logs. They didn't really help though: yes, in case of a normal successful startup we see nice debug logs (because of the increased verbosity) but when it refuses to start, we see nothing (see example log output below).
Relevant log output
Run docker restart "e46b9cd3212fd41d3df13b3b6a4129bc4e90ab27e4fa998dd3f7d8b449b961df"
e46b9cd3212fd41d3df13b3b6a4129bc4e90ab27e4fa998dd3f7d8b449b961df
warning: ignoring JAVA_OPTS=-Xms4096m -Xmx4096m; pass JVM parameters via OPENSEARCH_JAVA_OPTS
Killing opensearch process 11                 <- killing OS by "docker restart"
Killing performance analyzer process 12
OpenSearch exited with code 143
Performance analyzer exited with code 143
[1]-  Terminated              "$@" "${opensearch_opts[@]}"
Killing opensearch process 10
Killing performance analyzer process 11
Error: Process completed with exit code 56.   <- curl reports error, OS is not running

@dblock thanks for your reply. We tried both suggestions, but unfortunately the issue still exists. Switching to GHA step (https://github.com/ankane/setup-opensearch) actually increased the chance of failure, no idea why. Also we added all the possible sleep n just to give OpenSearch more time to start.
For now we stick with the original strategy, the restart step helps to solve the situation when OS refuses to start initially, however there is always a small chance for OS to go down completely, resulting in a failed build.
Could it be an environmental or memory issue?

[Triage] Hey @arg can you try running the github workflow in debug mode, should give some logs there. Also can you try to disable the PA component and run the cluster, I suspect the exit is happening because of memory (Xmx).

Greetings, @arg, just wondering if you ever got a chance to try what @prudhvigodithi mentioned above? (on Jan 5th). If you haven't yet, please give it a shot. I once had an issue to bring up OpenSearch cluster abd later realized that I had memory issue on my EC2.. It might be the same situation to your case..  thanks!

@jordarlu @prudhvigodithi sorry for the late reply, re-running with debug mode on didn't bring much difference, there are absolutely no related logs in the output. I suspect the issue relates to memory consumption, since the standard GHA VMs are quite limited in resources. We ended up restructuring our GHA workflow in a way it minimizes the chance of a failed OpenSearch:
Services:

Run OpenSearch as a service

Steps:

Tune VM (sysctl commands I listed above)
Restart OS service with sysctl changes applied
Check for OS connectivity
If OS is not accessible, restart it again

This workflow organization is not perfect: logically if OpenSearch runs fine before sysctl stuff, we don't really have to tune the system and restart the service. However it (almost) eliminates the chance of a broken OpenSearch. Very occasionally it still fails to run, even after two consequent restarts but with no logs we're not able to track down the root cause.

Thanks for the prompt reply, @arg .. and happy to know and learn how you work around it to reduce the chances of the failure. It seems to be the MEM issue on GHA to me too as we couldn't reproduce it on EC2.
I do want to update you with two more info that might be helpful in your case:

Via other issues/cases, the team remove the dependancy of the Performance Analizer (short for PA) and OpenSearch at  https://github.com/opensearch-project/opensearch-build/pull/287, If there is a possibility for you to try v1.3.7 or higher with PA disabling, that may be helpful on possible GHA MEM concerns

You may also want to setup a Swap Space in Workflow as here https://github.com/pierotofy/set-swap-space

thanks again and hope to hear more good news from you!!

I am closing this issue for now, and please open a new issue/re-open it if you are still facing difficulties .. thank you!


Misleading explanation regarding virtual network peering

[Enter feedback here]
In this documentation, it is instructed to disable the virtual network peering before moving a virtual network to another resource group but there is no way to disable a vnet peering. We need to delete the virtual network peering and recreate it once the virtual network is moved.

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

ID: d9962fb6-03f4-fd30-ab93-d2086713dc9b
Version Independent ID: 9106c368-72fe-d2d8-9ed5-ef7a46241c75
Content: Move Azure Networking resources to new subscription or resource group - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/move-limitations/networking-move-limitations.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

Thanks for bringing this to our attention. We will investigate it further and update you shortly.

@francisbdn - This VNET peering article refers to disabling a peering as blocking all traffic. Does that setting then permit you to move the peered virtual network?

Hello and sorry about the delays, I was away and did not have access to a computer for 2 weeks.
To answer tfitzmac's question, no it doesn't because the peering needs to be deleted for anyone to be able to move their VNET. It works well, it's just that in the documentation I linked in the ticket, it says that we need to disable it, but there are no way to disable it.

@MonikaReddy-MSFT  please re-open the ticket. "Disable" of a peering doesn't exist. Blocking traffic still fails validation. So document should clarify that we must delete peering to move.
Error codes btw: (Code: CannotMoveVnetDueToPeering) (Code: ResourceMoveProviderValidationFailed)

Agreed - the existing documentation is incorrect and "disabling" the peering (even when done on both VNETs) fails validation.

This is still incorrect


add resume story support

Hey!
Thanks for the feature.
A few remarks:

my editor tells me id is a reserved keyword and should not be used a variable name
we cannot call r.raise_for_status() if we call directly .json() on the requests response object
I'm not super fan of printing every session_id line by line without any context

I propose something like the following instead (untested):
    def resume_story(self, session_id: str):
        r = self.session.get(
            "https://api.aidungeon.io/sessions"
        )
        r.raise_for_status()
        sessions_response = r.json()

        valid_id_list = [sess[id] for sess in sessions_response]
        if not session_id in valid_id_list:
            print_handler("No session found for id " + session_id
                          + ". Valid values: " + ', '.join(valid_id_list))
            return

        story_session = next(sess for sess in sessions_response if story['id'] == session_id)

        self.user_id = story["userId"]
        self.session_id = story["id"]
        self.public_id = story["publicId"]
        story_timeline = story["story"]
        i = len(story_timeline) - 1
        while(i > 0):
            if(story_timeline[i]['type'] == "output"):
                break
            i -= 1
        self.prompt_iteration = i

        last_story_output = story_timeline[self.prompt_iteration]["value"]
        self.prompt_iteration += 2
        print_handler(last_story_output)

my editor tells me id is a reserved keyword and should not be used a variable name

I can't find anything about that online or python doc, but i can make the change

we cannot call r.raise_for_status() if we call directly .json() on the requests response object

👍

I'm not super fan of printing every session_id line by line without any context

oops, that was there for debug only, i don't think we should return valid ids in that call, if thats needed it should be its own function*, while leads me to the next point, if we're not printing the ids, we dont need that part of the code and we can just id validity through story_session
* rough estimate, I have 50+ session, returning them is essentially spam

Yes indeed, if the backends can store that many sessions we should not display them.
I'll do a bit of testing and will come back to you.


[HELP] How to figure out the state of fullscreen

How do I figure out if the window is fullscreen or not?
There are functions fullscreen() and unfullscreen but I can't find out how to get the status of whether the screen is or isn't fullscreen.
I am also using Webkit2gtk-rs, so I found this but it doesn't seem to work.

I reckon I could compare the screen and window sizes, if they are the same I can be sure that it is in fullscreen. I cannot, however figure out how to detect when the window size has changed.

Please ask for general support on the GNOME discourse or the gtk-rs Matrix room.


automation: fixing a Swagger Tag issue

Fixes https://github.com/Azure/azure-rest-api-specs/issues/24740

@jaspkaur28 @sushil490023 @mahakjain314 any chance you'd be able to take a look at this one?


Incomplete list of categories

spikex version: 0.5.2
Python version: 3.9.7
Operating System: Windows 10

Description
I want to get all categories of a page, but most categories are missing
What I Did
from spikex.wikigraph import load as wg_load
page = "Peking_2022"
categories = wg.get_categories(page, distance=1)

What I get: ['Category:Olympische_Winterspiele_2022']
The output I expect: ['Austragung der Olympischen Winterspiele', 'Olympische Winterspiele 2022', 'Sport (Hebei)', 'Sportveranstaltung 2022', 'Sportveranstaltung in Peking', 'Wikipedia:Veraltet nach Jahr 2022', 'Zukünftige Sportveranstaltung']
Prove: https://de.wikipedia.org/wiki/Olympische_Winterspiele_2022
I created a categorylinks dictionary from the categorylinks.sql.gz, so that the keys are the page_ids and under each key is the list of categories. I used your functions to get the page_id: page_id = self.get_pageid(self.redirect(page)) and my categorylinks dictionary . With this method I get the expected output. If this behaviour is not desired, I would like to think that there is a problem with the processing of categorylinks.sql.gz on your side.

I'm facing the same problem in with a ptwiki_core


"Additional PostHog to HubSpot property mappings" Not working

Am using cloud version of plugin. I used following PostHog property created_at and mapped with a Hubspot property ph_signup_date like below on an identify event. I see that Contact is created but the customer properties aren't being synced
created_at:ph_signup_date

@oneshot-engineering are you seeing any specific error messages from the plugin? Is this for new contacts or updating existing contacts?

@marcushyett-ph  -  I am seeing the same errors that are mentioned in the other issue. It happens for both create or update happens for only date fields.
I think that's because of Hubspot needs the time to be 0:0:0:0 time. Should be easily reproducible for created_at field.

Thanks, will take a look.

I've special cased created_at as well as sent_at, this should now work.


git-co-author: init at 0.2.0

Description of changes
Adding git-co-author, which easily uses 'Co-authored-by' trailers in the commit template.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.05 Release Notes (or backporting 23.05 and 23.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 304123 run on x86_64-linux 1

1 package built:

git-co-author

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/2096


cifs install error

i install needed packages by cli:
#!/bin/sh
#安装所有需要的包
su - docker -c "tce-load -i /var/lib/boot2docker/tczpacks/*.tcz"
#挂载外部共享目录
if [ ! -e /mnt/ws ]; then
sudo mkdir /mnt/ws
fi
sudo mount -t cifs //wingate-sking/D /mnt/ws -o user=1,pass=1
root@nct1:/mnt/sda1/var/lib/boot2docker/tczpacks# ls
cifs-utils.tcz                      filesystems-4.14.10-tinycore64.tcz
docker-compose-Linux-x86_64         mtd-4.14.10-tinycore64.tcz
/dev/loop0 on /mnt/sda1/tmp/tcloop/cifs-utils type squashfs (ro,relatime)
/dev/loop1 on /mnt/sda1/tmp/tcloop/filesystems-4.14.10-tinycore64 type squashfs (ro,relatime)
/dev/loop2 on /mnt/sda1/tmp/tcloop/mtd-4.14.10-tinycore64 type squashfs (ro,relatime)
ls -la /sbin
mount.cifs -> /mnt/sda1/tmp/tcloop/cifs-utils/usr/local/sbin/mount.cifs.
root@nct1:/mnt/sda1/tmp/tcloop/cifs-utils/usr/local/sbin# ls -al
total 48
drwxr-xr-x    2 root     staff           70 Apr  6  2012 .
drwxr-sr-x    6 root     staff           72 Apr  6  2012 ..
-rwxr-xr-x    1 root     root          4448 Apr  6  2012 cifs.idmap
-rwxr-xr-x    1 root     root         21468 Apr  6  2012 cifs.upcall
-rwsr-xr-x    1 root     root         22752 Apr  6  2012 mount.cifs
root@nct1:/mnt/sda1/tmp/tcloop/cifs-utils/usr/local/sbin# mount.cifs
-sh: mount.cifs: not found
why?

Officially, we don't support tce-load.
The best I can do is recommend checking the output of ldd /mnt/sda1/tmp/tcloop/cifs-utils/usr/local/sbin/mount.cifs and see if you're missing any .so files it requires (because that's the mostly likely cause of the error you see).
It could also be that the tcloop path isn't in your PATH, so you should try doing ./mount.cifs directly too and see if that works any better.

(Closing since this is an issue with usage, not with the ISO/distro itself.)


Can I use this with an Ouster OS1-32 LiDAR

I've been using your repo with a Velodyne VLP-16 and it works perfectly fine. However, when I try to use it with an Ouster LiDAR, I get an error of there being no transformation from the base_link to the map frame. Is this caused by the velodyne_nodelet_manager?

Hello, I've been trying the same thing and getting the same error. Did you ever find a solution?

You may need to properly set TF tree by, e.g., changing the following line.
https://github.com/koide3/hdl_graph_slam/blob/cb7af42f3c358925b15f05d0d54979b047e39411/launch/hdl_graph_slam.launch#L31


How to do RBAC authorization when using tide?

How to do RBAC authorization when using tide?

This isn't really something that should be handled by tide directly as it's a fairly lightweight and unopinionated server framework/library.
RBAC can be implemented in many ways, and is largely schema dependent, but tools like casbin can be used - implementation and integration is up to you, however.


options update when accessing WSDL on server port

pull request due to fix issue #36

See comments issue #36.


Update README.md to reflect latest version

Thanks a lot @npwolf !

@mpdude I merged this PR but the tests fail, this seems to be because they try to clone something from your personal GitHub account (git clone https://github.com/mpdude/test-1.git test-1-http)


Can I get public IP address at the same time when I get VM information.

@00Kai0

https://github.com/Azure/azure-sdk-for-python/issues/15925
I will close this one

https://github.com/Azure/azure-sdk-for-python/issues/15925
I will close this one


Solves pasting of one line + newline into the codeeditor

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[ ] Included a screenshot or animation (if affecting the UI, see Licecap)

PR #16164 fixed bug #16159, where the indentation of code pasted into the editor was lost.
This failed the border case, when just one line + newline is pasted (https://github.com/spyder-ide/spyder/issues/16159#issuecomment-898484641 ff). This PR solves this by calculating the list of indentation and then only uses this list, if it is not empty.
Issue(s) Resolved

Fixes #16159
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:
sphh

Hey @sphh, thanks a lot for your contribution! Please make your branch to derive from our 5.x branch (instead of master), so I can include it in our next release. For that, please run the following commands:
git checkout 5.x
git checkout patch-1
git rebase --onto 5.x master patch-1
git push -f origin patch-1

Thanks @ccordoba12 for the git commands. I wouldn't have had a clue, how to do it without them. It did not help, that I did these changes only online with Edit this file …
I hope it works now. If not, please feel free to copy and paste these lines yourself!!


Add get note for use without optional fallback.

Clarify basic failure case with a small snippet and a test. @nhunzaker this might be overkill for something so simple, but it seemed like it might be useful enough to call out.
What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build tools
[x] Documentation
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
Does this PR fulfill these requirements:

[x] All tests are passing
[ ] Commits reference open issues

Codecov Report

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

@@          Coverage Diff          @@
##           master   #300   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          23     23
  Lines         807    807
=====================================
  Hits          807    807

Continue to review full report at Codecov.

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

Looks great! Thanks!