Make immovable rod announce at the end of the event

fixes #27544
https://github.com/space-wizards/space-station-14/assets/124214523/e1911107-adfa-444e-8655-2400355c51f5
:cl:

tweak: Immovable rod announce now happens at the end of event.

A question, how long does the event last? Sometimes it felt like rod never even came when I was sitting on map terminal in hope to dodge it should it go after me.

A question, how long does the event last? Sometimes it felt like rod never even came when I was sitting on map terminal in hope to dodge it should it go after me.

the event itself has 25 sec duration, that means announce will be 25 seconds after rod spawn
the rod itself has 30 second lifetime, so it disappears  instead of going endless into space
i think you felt that because sometimes rod can go like this and even wouldnt touch the station
https://github.com/space-wizards/space-station-14/assets/124214523/1a7c237f-a4da-4d58-b769-31dd9e66f9fb


Fix wrong expansion for masked vmsge{u}.vx with temp register

The register 'vd' is unknown value in the instruction context,
and we could merge condition 'masked va >= x, vd == v0' and 'masked va >= x, any vd'

I believe it is correct as-is.  The fact that vd was previously unknown is fine - the point is, we need to preserve those unknown values for masked-off elements.

Yes, the current version is correct.  A masked vmsge should set the fields enabled by the mask, and not set the fields disabled by the mask.  The vmandnot will set every field, setting disabled fields to zero.  So we need two of them, one to copy the fields enabled by the mask from the vmsge result, and one to copy the fields disabled by the mask from the original dest.  And then or them together.  But there is a special case where the mask and dest are the same register, in which case we know that the fields disabled by the mask are all already zero in the dest, and hence we don't need to worry about preserving them, as the vmandnot will set all disabled fields to zero which is correct in this case.

@jim-wilson @aswaterman Got it, thanks for your detailed explanation :)


⚠ Bofrost.es has degraded performance

In 9cfd43f, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1665 ms

Resolved: Bofrost.es performance has improved in 1068332 after 7 minutes.


Debugging with smartstep is super slow.

Testing: #4954

VSCode Version: 1.1.0-alpha
OS Version: Windows10

Steps to Reproduce:

Create Basic nodejs JavaScript express3 project from Visual studio.
Launch VS code and open project folder.
update launch.json and set the value for smartstep:"true" and sourcemap: "true"
Start debugging and verify application behavior.

Note: I tried with all the possible combination of smartstep and sourcemap and observed this behavior when both the properties set to true.
Actual: Debugging is super slow and taking long time to render page.
Expected: Debugging should not be slow down when user enable smartstep.

@v-pavanp 'smart step' makes only sense if your project is using source maps and those sourcemaps cover most of the source code of the project. It seems your project is a plain JavaScript project without a single source map. Why would you use 'smart step' in this case? Just to be slower?

No, but how about mixed TypeScript and JavaScript projects.

Mixing works fine as long as the JavaScript you are stepping through is reasonable small (for instance because it is just glue code generated by a transpiler).
If you have lots of JavaScript that does not map to some source language, using this option makes you slow because node debug has to single-step through the JavaScript.
So the slowness you are seeing is expected and not a bug.


Lora is not updating weights when using app cli

I t seems only is set to true but not actually loading the weights?

think i am seeing this same issue.  dropping safetensors file into the lora_models folder, but the web-app never shows them in the drop-down?


v50: Verify spike trap compatiblity

New logic may be required

I have tested and it should work fine


igt-gpu-tools_git.bb: remove net-snmp

net-snmp is used for sending command to PDU to power cycle the
Chamelium. It is not necessary for igt-gpu-tools, so remove it for the
recipe.
Signed-off-by: Arthur<EMAIL_ADDRESS>

Makes sense not to include here (unless we merge support to i-g-t for controlling Chamelium power). However don't we still need this in the final image somehow? Does it need to be added to a packagegroup test group (e.g. something like https://github.com/96boards/meta-rpb/blob/master/recipes-samples/packagegroups/packagegroup-rpb-tests-weston.bb)

We do need it in the image. To add it to a packagegroup would be a good idea, just not sure which one is better. packagegroup-rpb-tests.bb or packagegroup-rpb-tests-weston.bb?


Issue with JSX runtime

I noticed an error when playing with the provided example. The only changes I made were in the package.json setting the dependency for @stylex-extend/react to whatever the last is on NPM because it was workspace:* or something before that.
Here is the error:
Cannot find module '@stylex-extend/react/jsx-runtime' or its corresponding type declarations.ts(2307)
Repro here: https://github.com/zaydek/nonzzz-stylex-extend

Also, thanks for creating this project, I'm really excite to play with it.

It's a warning from tsc. Can your share your tsconfig here?

@mengdaoshizhongxinyang Can confirm that worked. Thank you!
I have a superficial question; what is stylex={ ... } a shorthand for? I take it {...stylex.props( ... ))?

My current workaround is simply not using stylex={ ... } and just using stylex.props which seems like a usable workaround.

Not yet. But i think you can remove "jsxImportSource" and add ""@stylex-extend/react"" to types. then change the "moduleResolution" as "Bundler"

{
  "compilerOptions": {
    "baseUrl": ".",
    "outDir": "dist",
    "noImplicitThis": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "resolveJsonModule": true,
    "target": "ESNext",
    "module": "ESNext",
    "lib": ["ESNext", "DOM"],
    "jsx": "react-jsx",
    "moduleResolution": "Bundler",
    "types": ["vite/client", "react", "react-dom","@stylex-extend/react"],
    "jsxImportSource": "@stylex-extend/react"
  }
}

Getting some new errors. Let me know if you need a repro I can just commit my changes same repo.
https://github.com/nonzzz/stylex-extend/assets/58870766/f8cd4f28-e744-478c-8648-39c5a5dc0fdc

If I use the original config and just remove the JSX import source it all seems to work.
{
  "compilerOptions": {
    "lib": ["DOM"],
    "esModuleInterop": true,
    "jsx": "react-jsx",
    "moduleResolution": "Node",
    "types": ["vite/client", "react", "react-dom"]
  }
}

Which is fine because I don't currently plan on relying on stylex={{}} syntax.

:) We will fix theme as soon as possible. If you have some ideas about inline. Reports are also welcome

Thanks I really appreciate it. For inline, I'm a little confused -- am I supposed to import inline or do I just use {} like:

My only concern right now is if we assume StyleX does implement atom or inline, would it not make sense to implement an API that offers forward compat like
 so there's one less thing to worry about down the road?
I do really enjoy the {} syntax but it seems like I don't get auto complete anymore (could be related to the JSX thing). I can try to find it but either in the RSD or StyleX issues, I think they made an explicit point of wanting to use atom as opposed to {} probably has something to do with the ability for babel or more easily disambiguate static styles.

Don't worry about it, Currently i
implement the inline api like the Rfc. In my option this repo is a experimental field. If one day stylex has implemented it you can replace it. About short syntax {} it seems like a interesting idea. But it will cause trouble for future migrations. Import inline from extend package is enough.About jsxAttribute syntax is inspired by emoticon,I think is a easy way to write code

OK great. Currently I've been doing
 because I don't know any better but it looks like that's just spitting out inline styles:

Are you sure you want to continue? This action cannot be undone.

In any case, I have notifications on for this repo and I'll be really interested to try your inline implementation once it's ready. Feel free to ping me if you want me to test it.

Currently you can only import inline api from extend package. About short brackets syntax i thin k I can provide an option for that need it users

Like import { inline } from "@stylex-extend/react"; this?
If I alt click, this is what I see inside:
import { } from 'react'
import type { StylexProperty } from '@stylex-extend/shared'

declare module 'react' {

  interface Attributes {
    stylex?: StylexProperty
  }
}
export { }

I haven't been able to play with inline directly just yet.

install '@stylex-extend/core'
import { inline } from '@stylex-extrnd/core'
you can refer this repovite-bundle-analyzer

I think i need provide a simple document to describe how to use it:)

Ah OK that fixed everything. OK now I can use the tsconfig you provided previously and everything seems to work correctly now! This is awesome. I'll push changes to the repo as working proof of concept.
{
  "compilerOptions": {
    "baseUrl": ".",
    "outDir": "dist",
    "noImplicitThis": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "resolveJsonModule": true,
    "target": "ESNext",
    "module": "ESNext",
    "lib": ["ESNext", "DOM"],
    "jsx": "react-jsx",
    "moduleResolution": "Bundler",
    "types": ["vite/client", "react", "react-dom", "@stylex-extend/react"]
  }
}


Connection error

It is working in local. But when trying to run on server, I am getting error.
pylt port 8081
requests.exceptions.ConnectionError: HTTPConnectionPool(host='localtunnel.me', port=80): Max retries exceeded with url: /?new (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x7fb777790100>: Failed to resolve 'localtunnel.me' ([Errno -3] Temporary failure in name resolution)"))
Also, I am wondering why port=80 is taken when I am trying to run 8081 ?
My server is running is port 8081:
tcp        0      0 <IP_ADDRESS>:8081          <IP_ADDRESS>:*               LISTEN      191132/python3

Port 80 is localtunnel website port. Basically there is network problem on your system that why you got that error .

@Bk073 did you fix it ??


Fixing supervisor reading error

Just a small error in the atom for the rest-for-one strategy during the reading section.

Good catch! Thank you


Squash all PRs in Prow by default

Fixes the config to specify to squash all ACK repository PRs

Found a way to template the squashed commits with the commit message as the title of the PR and the commit body as the description of the PR.

/lgtm

Found a way to template the squashed commits with the commit message as the title of the PR and the commit body as the description of the PR

Does this mean that preferably we should have one commit per PR, or at least a a PR description containing summary of all the commits (if there is more than one) ?

Found a way to template the squashed commits with the commit message as the title of the PR and the commit body as the description of the PR

Does this mean that preferably we should have one commit per PR, or at least a a PR description containing summary of all the commits (if there is more than one) ? @RedbackThomson

This means that whatever the description of the PR is, that will be the body of the commit. I think this is preferable because typically the body of a PR gives more contexts and provides a better summary than any number of commits could ever provide.

I'm kinda worried about the current template (using PR body)... look the latest commit here it's starting with "issue N/A" , at one point we have By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. then the commit message...

Most of the developers are not aware of the new merge type and they will probably focus more on commit message than the PR body it self (https://github.com/aws-controllers-k8s/code-generator/pull/69#pullrequestreview-663996218).
I don't think that we should explain this to every current and future contributors. IMO i believe we should go back to "merge" method which more obvious and expected. @RedbackThomson

I'm kinda worried about the current template (using PR body)... look the latest commit here it's starting with "issue N/A" , at one point we have By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. then the commit message...

Yeah, that definitely was not the intention. That latest commit should have had github: find users personal fork using ListRepositoryForks as the commit message summary (since that is the title of the PR from which the commit was squash-merged).
The body of the commit message should have been the description of the PR, so this:
Issue: N/A

Recently Github API /user/{user}/repos endpoint changed and stopped returning information about repositories parents (repos from which they were forked) and started to cause some nil pointer panics in ensure repo command (which not in main branch yet).
This patch uses ListRepositoryForks in GetUserRepositoryFork to find a user personal fork. We could could have used GetRepository call to read the parent repository information, but it this approach will require way more API requests.

Description of changes:

    Call ListRepositoryForks in GetUserRepositoryFork to find a user personal fork.
    upgrade go-github version to v35
    regenerate pkg/github mocks
    renames ErrorForkNotFound to ErrForkNotFound

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I'm less concerned about the "By submitting this pull request.." wording being included in the commit message, but definitely agree the title and body content should not look like it does.


Pandas concat shows as unreachable

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: Version: 1.87.1 (Universal)
OS Version: Darwin arm64 21.6.0

I've been using the pandas.concat function successfully for the better part of a year but with the most recent update to VSCode, it shows anything following pandas.concat as unreachable within my code even though that's clearly NOT the case and the code runs successfully. This is absolutely infuriating!!!
Steps to Reproduce:

Create two dataframes df1, df2
Add in pandas.concat([df1, df2]) and some code after
You'll see that all of the code after is showing as unreachable even though it clearly is reachable

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.87.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

/extPython

It looks like this is caused by the Python extension. Please file the issue to the Python extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


new url link

This is the updated url, direct from the site.

Please amend the commit message to include the name of the updated cask.

i give up.

Simple change.


LFS cannot clone into current (empty) directory

In LFS 1.2 this worked:
mkdir MYPROJECT
cd MYPROJECT
git lfs clone git@bitbucket.org:ssmith/MYPROJECT.git .

With 1.3.1 it fails:
$ git lfs clone git@bitbucket.org:ssmith/MYPROJECT.git .
fatal: destination path '.' already exists and is not an empty directory.
Error(s) during clone:
git clone failed: exit status 128

This appears to be related to the premature initialisation of the LFS storage at the top level (see also #1231):
$ find
.
./lfs
./lfs/objects
./lfs/objects/logs
./lfs/tmp
./lfs/tmp/objects

Note that this top-level lfs dir is created even when the repo is cloned into it's default directory:
$ git lfs clone git@bitbucket.org:ssmith/MYPROJECT.git
Cloning into 'dacng'...
remote: Counting objects: 2363, done.
remote: Compressing objects: 100% (1724/1724), done.
remote: Total 2363 (delta 779), reused 1846 (delta 440)
Receiving objects: 100% (2363/2363), 34.38 MiB | 2.71 MiB/s, done.
Resolving deltas: 100% (779/779), done.
Checking connectivity... done.
Git LFS: (498 of 498 files) 129.13 MB / 130.33 MB
[] $ ll
total 0
drwxr-xr-x  4 ssmith wheel 136 Aug 10 10:54 .
drwxrwxrwt 11 root   wheel 374 Aug 10 10:37 ..
drwxr-xr-x 15 ssmith wheel 510 Aug 10 10:54 MYPROJECT
drwxr-xr-x  4 ssmith wheel 136 Aug 10 10:54 lfs

(A workaround for this is to do a git clone with GIT_LFS_SKIP_SMUDGE and then git lfs pull.)

Still present in LFS 1.4.

Hey @tarka, sorry I missed this when triaging. I knocked this one out in #1478 with a little write-up, and it should no longer be an issue. I'm planning to ship this in v1.4.1, but you're welcome to build and install LFS yourself if you need it sooner 😄

Merged!


Add inset text component example and guidance

Authors: @timpaul & @amyhupe.

You can preview this change here:
Built with commit 63fc203993a226a531355203617e36085bfcd370
https://deploy-preview-287--govuk-design-system-preview.netlify.com


Why Supabase and not just PG?

This is great, but for several reasons (including cost), I decided to roll my own PG instances.
I looked at the migrations and seems like just about everything is compatible with plain old postgres except the RLS which uses a function Supabase injects into their PG instances: auth.uid()
Do you have any advice on how to implement the same functionality without relying on Supabase?
PS:
Any example you guys offer with plain PG would work great with Supabase, just saying.

AFAIK, Supabase is open-source so you can deploy your own instance as well. They also provide a backend layer that makes this project nearly trivial to implement. On the other hand, doing all of that on top of Postgres directly would be much more time consuming.
PS: I'm not a maintainer on this project.

I'll leave this one for @leerob and team to answer as I'm highly biased as a Supabase employee. That being said, the big benefit of using Supabase here is the connectedness of Auth with the DB using row level security policies, making it easier to manage the business logic of who can see what data.

A few thoughts:

Supabase is open-source
This repo could be easily swapped out to use pg if you prefer, including your own auth provider


PX4 simulator kills all processes which contain 'px4' in name

There is a very appalling multiple instance detection built in px4 simulator.
It contains command "pgrep px4 && pkill px4"
This effectively kills all processes which happen to have 'px4' in their name.
simple solution would be to add anchors:
pkill '^px4$' so that it would match only 'px4' and not 'apx44'
Of course more sophisticated lock file based scheme would be much nicer.

Thanks @jdzerve . Could you open a pull request that fixes it to your liking?
https://github.com/PX4/Firmware/blob/master/Tools/sitl_run.sh#L61
It needs to work on OSX and Linux.

Created Pull request for this: https://github.com/PX4/Firmware/pull/6319


E_NOTICE with trait method aliases

I'm getting Notice: Undefined offset: 1 in /path/to/vendor/zendframework/zend-code/src/Scanner/ClassScanner.php on line 596 using 3.1.0. It looks like this happens with aliased trait methods:
trait A
{
    function a() {
        // does something
    }
}

class B
{
    use A {
        a as b;
    }

    function a() {
        b();
        // do something more
    }
}

Stepping through the code it looks like $alias['original'] does not contain '::', causing the notice. I ran into this using zend-expressive-tooling on an existing project. It doesn't seem to cause anything other than annoyance, but I'm not sure if just adding a check for '::' would hide a deeper problem. Thoughts?

Originally posted by @kynx at https://github.com/zendframework/zend-code/issues/104

No longer needed as per #58

Heavens to Betsy! I used to alias trait methods? What was wrong with me?!
Nice cleanup you’re doing @Ocramius 🙂


Change pod modal and alerts approach

At the moment we use a single template and switch on the confirmation action/notification type in order to avoid embedding copy in the code. The plan is to go with the approach discussed in #58, where one can provide copy for simpler cases, but provide a template url for other cases.

@rudigiesler ready for review

:+1:, looks good to me


Introduce a generic slice clone function

This is nil-preserving unlike the existing code.
We also add some missing []byte slice copies.
Fixes #1381

The go.mod / go.sum changes come from bumping the go version and running go mod tidy.


"Unknown environment 'tabular'" error in some tutorials

Report
Reading the page with sccoda tutorial, I noted that some illustrations (probably, with tables) are broken:

I didn't check other tutorials but they might suffer from the same problem. Probably, something is wrong with documentation rendering engine
Version information
No response

Potentially due to https://github.com/mathjax/mathjax-docs/wiki/LaTeX-Tabular-environment

Fixed https://github.com/theislab/pertpy/commit/7a2f8233d934b730a5605c8c53fdc65392992984


Updated the information about editing the wiki page.

As I understand it it is no longer possible to edit the wiki page. The sentence  "To contribute new documentation or add examples to the gallery, just edit the Wiki" in CONTRIBUTING.md was therefore misleading.

#3297

If I had an example I wanted to share on the Gallery/Examples, what would I do?

good


Draft: PHP 8 support

This PR allows Slim to be installed in PHP 8 and passes all the tests and checks.
History: I've raised some points in https://github.com/slimphp/Slim/issues/2977#issuecomment-703194522 and since that time I've worked around other repositories to make this possible. This is also my first open-source contribution to a major project :)
Test fixes:

Added a test for an uncovered branch of MiddlewareDispatcher->addDeferred. PHPUnit 8 was miscalculating coverage – see https://coveralls.io/builds/33553304/source?filename=Slim/MiddlewareDispatcher.php.

My questions:

I implemented disableXmlEntityLoader as a private static method. Is this okay? I thought about making it protected or extracting it to a class, but I'm unsure about creating new "contracts".
Coverage – conditional call to libxml_disable_entity_loader. Is it okay to just @codeCoverageIgnore some part that will only run in PHP 7 or PHP 8? How should situations like this be handled?

Dependencies:  I have gone through all dependencies that are blocking the PHP 8 upgrade and temporarily linked to development branches where the PHP 8 issues are solved. Surely this must be addressed before this can be merged (this is isolated in a single commit that can be removed). Those are the open PRs, some by me and some by others:

[ ] https://github.com/slimphp/Slim-Psr7/pull/169
[x] https://github.com/slimphp/Slim-Http/pull/142
[x] https://github.com/php-fig/http-message-util/pull/19
[ ] https://github.com/Nyholm/psr7-server/pull/40
[x] https://github.com/laminas/laminas-diactoros/pull/46

Coverage decreased (-0.3%) to 99.698% when pulling b92654f6ef0fc9482e499c1d3d6ddec5fde032fe on edudobay:php8 into 1b098e7d8dafb46713258e70f444d36f1133ab23 on slimphp:4.x.

@edudobay thank you for this PR

I implemented disableXmlEntityLoader as a private static method. Is this okay? I thought about making it protected or extracting it to a class, but I'm unsure about creating new "contracts".

I think that we could just make that method protected but does not need to be static unless I'm missing something

Coverage – conditional call to libxml_disable_entity_loader. Is it okay to just @codeCoverageIgnore some part that will only run in PHP 7 or PHP 8? How should situations like this be handled?

I don't think there's any way around this one in this particular case. We would have to overload the LIBXML_VERSION constant somehow to be able to stub the behavior.

Dependencies: I have gone through all dependencies that are blocking the PHP 8 upgrade and temporarily linked to development branches where the PHP 8 issues are solved. Surely this must be addressed before this can be merged (this is isolated in a single commit that can be removed). Those are the open PRs, some by me and some by others:

This particular issue bothers me a bit because we're going to have to do this work all over again when all the other libraries have official releases to support PHP 8. I would rather just do all the work at once than do it twice. We can just leave this PR open for now until the other libraries release official support for PHP 8.

@l0gicgate Sure, I'll make it protected then. But an instance method would not work inside the static anonymous function. I suppose that function is static for performance reasons. When I was implementing these changes, I benchmarked several kinds of function calls and I got differences up to 10x in memory usage — even though I don't think this is performance-critical code, I would be careful not to introduce a 10x factor in resource usage. I'll redo these benchmarks (I think I threw it away at the time), but I'll be happy to discuss other solutions too.
Regarding dependencies, I'll just watch them for releases and ping a comment when they're all ready.

Hi! I've updated the source branch and fixed some PHPStan issues that surfaced recently. I'm not sure if my solution was the way to go — the type hints that could go wrong are the ones for Closure::bindTo(), which can fail if called on a closure with static scope.

Hi @l0gicgate. All set for external projects! When https://github.com/slimphp/Slim-Psr7/pull/169 is merged and release tags are ready, we can remove the "TEMP" commit to go back to tagged release constraints.
I guess we will need to wait a few days for an official PHP 8.0 tag to be available in Travis CI, so we can fix that too, right? I'm not sure if we should otherwise remove "allowed to fail" from the nightly build.

I guess we will need to wait a few days for an official PHP 8.0 tag to be available in Travis CI, so we can fix that too, right? I'm not sure if we should otherwise remove "allowed to fail" from the nightly build.

Once they release the official PHP 8.0 tag we can add it to the CI builds and leave the nightly build as "allowed to fail" as we will need it to examine the behavior of future versions on CI e.g: PHP 9 (long time from now)

@l0gicgate Great, let me know if I can help with anything!

@edudobay see the releases below:
Slim-Psr7 1.3.0 Release
Slim-Http 1.2.0 Release
We should be good to go for this PR after!

@l0gicgate I've updated composer.json to require these latest slim/http and slim/psr7 if that's ok.

@l0gicgate I've fixed the issues you mentioned!


Upload to ESP32 failed

Hello,
I have a problem uploading to my ESP32. When I try to upload with pycharm I have an error: ampy.pyboard.PyboardError: could not enter raw repl
So I tried to upload directly from the terminal without a virtual environment. And it works. So I logged into the virtual environment, updated ampy to version 1.1.1 and was able to upload it from the terminal. On the other hand, I cannot upload with pycharm because it wants to update version 1.0.5. How do I get the extension to accept version 1.1.1 of ampy. I'm on big macos on.

Have you tried to change File -> Settings -> Languages&Frameworks -> MicroPython -> Device type to esp8266 in PyCharm?
As ampy is giving a pyboard error maybe you have forgotten to set this.
While esp32 is not directly supported it should work for most cases with the esp8266 settings (atleast it does for me)
Just watch out if you want to include folder structures - this did not work for me

This can be related to the issue solved here: https://github.com/vlasovskikh/intellij-micropython/pull/142
You can try to increase hardcoded delay on the following line and see if it helps: https://github.com/vlasovskikh/intellij-micropython/blob/0322fb7c50bed3e196ee253fbb0f613344a56a48/scripts/microupload.py#L121
Path to microupload.py can be found in the Terminal window that appears when you try to upload files.

You can try to increase hardcoded delay on the following line and see if it helps

Solution by @lensvol has worked for me. I have changed value from 0.5 to 2.5 and it works.

You can open file by following command
code "~/Library/Application Support/JetBrains/PyCharm2021.1/plugins/intellij-micropython/scripts/microupload.py"

Running:
OSx 11.5.2
PyCharm 2021.2 V 11.0.11+9-b1504.13 x86_64
Plug-in MicroPython 1.2
The described edit to:
"/Users/<USER_NAME>/Library/Application Support/JetBrains/PyCharm2021.2/plugins/intellij-micropython/scripts/microupload.py"
Fixed it.

Fix works for me as well. Can this be considered being fixed in a PR?

It's August 21st 2022 and I still had to use this hack to get my file uploading to work.
I'm using a five days old build.
PyCharm 2022.2.1 (Community Edition)
Build #PC-222.3739.56, built on August 16, 2022
Dear JetBrains, please fix this.

Hi! We'll try to include it in the next update.

Running: OSx 11.5.2 PyCharm 2021.2 V 11.0.11+9-b1504.13 x86_64 Plug-in MicroPython 1.2 The described edit to: "/Users/<USER_NAME>/Library/Application Support/JetBrains/PyCharm2021.2/plugins/intellij-micropython/scripts/microupload.py" Fixed it.

I just tried editing this file on Windows (Program Files\JetBrains\PyCharm.....\ etc) but there is no plugins\intellij-micropython\ folder.. I have downloaded the MicroPython Plugin from the Plugin Store, am I missing something?!

Have you checked app data folder?
W dniu pon., 28.11.2022 o 21:52 DanDan @.***>
napisał(a):

Running: OSx 11.5.2 PyCharm 2021.2 V 11.0.11+9-b1504.13 x86_64 Plug-in
MicroPython 1.2 The described edit to: "/Users/<USER_NAME>/Library/Application
Support/JetBrains/PyCharm2021.2/plugins/intellij-micropython/scripts/microupload.py"
Fixed it.
I just tried editing this file on Windows (Program
Files\JetBrains\PyCharm.....\ etc) but there is no
plugins\intellij-micropython\ folder.. I have downloaded the MicroPython
Plugin from the Plugin Store, am I missing something?!
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/intellij-micropython/issues/145#issuecomment-1329747839,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHHL4MWW5DZSZAJ7NL4OQSTWKULQRANCNFSM4YY24CJA
.
You are receiving this because you commented.Message ID:
@.***>

Have you checked app data folder?

ah Thank you i didnt think of checking there...
In Users\AppData\JetBrains...\plugins\  there is only intellij-micropython.zip in the plugins folder, should I extract it to the Program Files\JetBrains...\plugins\ folder?

@Elizaveta239 When will the next update be?

Are we still to do this hack? Kind of baffling that the ESP32 isnt already in the list.

Here works as well


New settings in Tabmode: F+J/L to cmd+alt+ctrl+left/right

I'm using this currently to change spaces in lion.
Also removed other strage cases where F was being used..

Thanks!


Update some points, ref #1330

/cc @dblock

Build fail :(

That is not grape issue, but mustermann19's ObjectSpace::WeakMap issue.
I fixed the problem and then released new version of mustermann19.
All specs are passed now ;)

Merging.


tests: speedup compaction tests

On my machine, compaction tests take half time as before.

PTAL @javaforfun

LGTM

PTAL

@nolouch PTAL


NaNpx values when font-size is set on the html element

I have posted this issue in cssnext#210 but feel that it really belongs here.
cat node_modules/pixrem/package.json | grep version: "version": "2.0.0",
node_modules/.bin/postcss -v: postcss version 5.0.4
Thanks to @ben-eb I have reduced a test case that reproduce the issue.
Running postcss/pixrem with the following command:
node_modules/.bin/postcss -u pixrem and/or node_modules/.bin/cssnext
Smaller test case:
html {
  font-size: 0.625vw;
}

h1 {
  font-size: 6rem;
}

Output:
html {
  font-size: 0.625vw;
}

h1 {
  font-size: NaNpx; /* only happens when font-size is set on the html element */
  font-size: 6rem;
}

Since you can't derive an absolute value from vh, vw, vmax, and vmin which are relative to the viewport, pre-runtime. I think pixrem should either throw a meaningful error or this must be a noop failing silently. I'm personal in favour of throwing, since it gives me an immediate response when preprocessing via either postcss -u pixrem or cssnext [--no-rem].
Note: by default the font-size of the root element (html) is 16px in all browsers on most systems. Even if you specify a percentage value, e.i. html { font-size: 62.5%; }, you can calculate the root font-size to be 10px.

Other values that might be problamatic is ex and ch, unless you can read the font being used in a meaningful way. Doable but not simple. This is however another issue, but one to be mindful of.

ex
This unit represents the x-height of the element's font. On fonts with the 'x' letter, this is generally the height of lowercase letters in the font; 1ex ≈ 0.5em in many fonts.
ch
This unit represents the width, or more precisely the advance measure, of the glyph '0' (zero, the Unicode character U+0030) in the element's font.

As Pixrem is one of the oldest PostCSS module, it needs to be rewritten to get better errors/warn messages, so for now, I'm in favor of failing silently to 16. All browsers that do support vw unit also support rem unit so this is not a big deal to fallback to 16 for older browsers.
Any opinion? cc @MoOx

All browsers that do support vw unit also support rem unit so this is not a big deal to fallback to 16 for older browsers.

indeed.

Unfortunately the unit test fails with<EMAIL_ADDRESS>which is a dev dependency of cssnext. It's unrelated to PR#217 though.

Hmm seems there is some info about telling travis to use GCC 4.8 and here. I don't have time to do more but wanted to share the info.
Of course the Windows issue seems to be totally unrelated: https://ci.appveyor.com/project/MoOx/cssnext/build/279


Current type not on the same line in Inheritance as base types

Describe the bug
In the Inheritance section, the current type is moved down, relative to its base types.
To Reproduce

Go to  ArgumentException.
Look at the Inheritance section.

Expected behavior
All types are on the same line.
Screenshots

Desktop:

OS: Windows 10
Browser: Firefox 68, Edge 44

This seems fixed. Can you confirm @svick?

Yeah, it looks correct now, closing.


PXT invalidates code even before a block has been dropped in the space

Drag a block but don't let go.
Pxt will invalidate the blockly editor and re-run the simulator, even before you drop a block in the workspace.

Looks like a blockly bug

Fixed by #668


Never got the Token & Never received the Notification sent from FCM Console

I got the Notifications the first time I have implemented this package three days ago (received couple of notifications), but from the next day I haven't got any notifications and the Token is always empty in debug mode. I have tried in Release mode also but i'm not getting Notifications. I have tried all possible troubleshooting methods, re-installed Packages, clean and rebuild, re-installing the application etc., but no success. I am not getting any build/runtime errors, and application is working fine, but just the notifications are not receiving, either in the background or in the foreground.
BTW, I am trying to send sample messages from FCM Console, with and without custom data.
And I believe all the FCM related settings are proper in the application.
I am running Xamarin.Forms with only Android and PCL projects.
Below is the PCL App.xaml.cs file OnStart() method
    protected override void OnStart()
    {
        CrossFirebasePushNotification.Current.Subscribe("general");

        CrossFirebasePushNotification.Current.OnTokenRefresh += (s, p) =>
        {
            System.Diagnostics.Debug.WriteLine($"TOKEN REC: {p.Token}");
        };

        CrossFirebasePushNotification.Current.OnNotificationReceived += (s, p) =>
        {
                System.Diagnostics.Debug.WriteLine("Received");
        };

        CrossFirebasePushNotification.Current.OnNotificationOpened += (s, p) =>
        {
            System.Diagnostics.Debug.WriteLine("Opened");
        };

        CrossFirebasePushNotification.Current.OnNotificationDeleted += (s, p) =>
        {
            System.Diagnostics.Debug.WriteLine("Dismissed");
        };
    }

Below is the MainApplication.cs from Android Platform Project
public override void OnCreate()
{
base.OnCreate();
RegisterActivityLifecycleCallbacks(this);
#if DEBUG
FirebasePushNotificationManager.Initialize(this, true);
#else
FirebasePushNotificationManager.Initialize(this, false);
#endif
        CrossFirebasePushNotification.Current.OnNotificationReceived += (s, p) =>
        {
            System.Diagnostics.Debug.WriteLine("NOTIFICATION RECEIVED", p.Data);
        };

        if (Build.VERSION.SdkInt >= Android.OS.BuildVersionCodes.O)
        {
            FirebasePushNotificationManager.DefaultNotificationChannelId = "DefaultChannel";
            FirebasePushNotificationManager.DefaultNotificationChannelName = "General";
        }
    }

I am using below IDE & Packages.

My MainActivity.cs
    protected override void OnCreate(Bundle bundle)
    {
        base.OnCreate(bundle);

        global::Xamarin.Forms.Forms.Init(this, bundle);

        LoadApplication(new App(new AndroidInitializer()));

        FirebasePushNotificationManager.ProcessIntent(this, Intent);
  }

    protected override void OnNewIntent(Intent intent)
    {
        base.OnNewIntent(intent);
        FirebasePushNotificationManager.ProcessIntent(this, intent);
    }

Version Number of Plugin: 2.3.0
Device Tested On: OnePlus 5T with Android 8.1
Version of VS: VS 2017 15.6.4
Version of Xamarin.Forms: <IP_ADDRESS>0146

Check your google-services.json (redownload it)
That is expected to happen if your key changes, as it's being unable to connect to firebase server.

@bMiquelin, thanks for your response, but unfortunately it didn't worked. I tried downloading the json file again but with no success, i removed the FCM project altogether and re-created a project with a new package name as well, updated the package name in my xamarin andorid project and downloaded the new json file and set the build action to "GoogleServicesJson", but the issue is same.
Do we need to specify a specific Notification Channel ID & Name?
Or is there any issue with the Latest versions of Firebase or Xamarin.forms?
Here is my full Application.cs file
using System;
using System.Collections.Generic;
using Android.App;
using Android.OS;
using Android.Runtime;
using Firebase;
using Plugin.CurrentActivity;
using Plugin.FirebasePushNotification;
using Plugin.FirebasePushNotification.Abstractions;
namespace QNPL.Mobile.Droid
{
[Application]
public class MainApplication : Application, Application.IActivityLifecycleCallbacks
{
public MainApplication(IntPtr handle, JniHandleOwnership transer)
: base(handle, transer)
{
}
    public override void OnCreate()
    {
        base.OnCreate();
        RegisterActivityLifecycleCallbacks(this);

#if DEBUG
FirebasePushNotificationManager.Initialize(this, new NotificationUserCategory[]
{
new NotificationUserCategory("message",new List {
new NotificationUserAction("Reply","Reply",NotificationActionType.Foreground),
new NotificationUserAction("Forward","Forward",NotificationActionType.Foreground)
        }),
        new NotificationUserCategory("request",new List<NotificationUserAction> {
            new NotificationUserAction("Accept","Accept",NotificationActionType.Default,"check"),
            new NotificationUserAction("Reject","Reject",NotificationActionType.Default,"cancel")
        })

        }, true);

#else
FirebasePushNotificationManager.Initialize(this,new NotificationUserCategory[]
{
new NotificationUserCategory("message",new List {
new NotificationUserAction("Reply","Reply",NotificationActionType.Foreground),
new NotificationUserAction("Forward","Forward",NotificationActionType.Foreground)
		}),
		new NotificationUserCategory("request",new List<NotificationUserAction> {
		    new NotificationUserAction("Accept","Accept",NotificationActionType.Default,"check"),
		    new NotificationUserAction("Reject","Reject",NotificationActionType.Default,"cancel")
		})

	    },false);

#endif
        CrossFirebasePushNotification.Current.OnNotificationReceived += (s, p) =>
        {
            System.Diagnostics.Debug.WriteLine("NOTIFICATION RECEIVED", p.Data);
        };

        //Set the default notification channel for your app when running Android Oreo
        if (Build.VERSION.SdkInt >= Android.OS.BuildVersionCodes.O)
        {
            //Change for your default notification channel id here
            FirebasePushNotificationManager.DefaultNotificationChannelId = "DefaultChannel";

            //Change for your default notification channel name here
            FirebasePushNotificationManager.DefaultNotificationChannelName = "General";
        }
    }

    public override void OnTerminate()
    {
        base.OnTerminate();
        UnregisterActivityLifecycleCallbacks(this);
    }

    public void OnActivityCreated(Activity activity, Bundle savedInstanceState)
    {
        CrossCurrentActivity.Current.Activity = activity;
    }

    public void OnActivityDestroyed(Activity activity)
    {
    }

    public void OnActivityPaused(Activity activity)
    {
    }

    public void OnActivityResumed(Activity activity)
    {
        CrossCurrentActivity.Current.Activity = activity;
    }

    public void OnActivitySaveInstanceState(Activity activity, Bundle outState)
    {
    }

    public void OnActivityStarted(Activity activity)
    {
        CrossCurrentActivity.Current.Activity = activity;
    }

    public void OnActivityStopped(Activity activity)
    {
    }
}

}

@bMiquelin i was able to find the issue...culprit is myself...a month ago..i have disabled most of my google background services in mobile data..as they are consuming lot of mobile data....i have realized this after analyzing the debug output of my app with this line "D/FirebaseInstanceId(32620): background sync failed: SERVICE_NOT_AVAILABLE, retry in 20s". When I first ran i was in wifi and hence the notifications started working...after that i was testing in office in my mobile data...and so the issue :)


Pin the paramiko version to 1.15.3

With the release of paramiko 1.16.0, we've experienced breakage in our tests.
We don't have an explicit dependency on paramiko, so we've never pinned a
version, and just taken what we got when the dependency was resolved
implicitly. Pending further investigation into the breakage, we're making our
dependency on paramiko explicit and pinning it to a known-good version.

I've re-run the failing tests (they pass) and have a smoke test running now.

looks good


Update background-img-opts.json

Addet iOS Safari Bug "iOS Safari has buggy behavior with background-size: cover; + background-attachment: fixed;"

Thanks!

Thank u too for the coolest web-developer tool ever ^-^
Am 04.01.2015 um 23:12 schrieb Alexis Deveria:

Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/Fyrd/caniuse/pull/845#issuecomment-68651773.


make admixpops (and spacetime) operate on blocks of SNPs

This should help with some sampling related issues and also preserve some degree of linkage disequilibrium. The block size could be an input argument.

The block size could also vary along the genome to simulate a first or X generation descendant


Own host - Quick start steps does not work for me

After following below steps in Quick start it does not show any url and shows just this
root@nodejs:/var/www/html/app# npm run dev

<EMAIL_ADDRESS>dev
node index.mjs

What is wrong? I went to ip address of server and tried there  with http://ip:3000 and without port as well and nothing comes.
Help is needed. thanks.

Clone this repository
git clone --recurse-submodules https://github.com/webaverse/app.git
Go into the repository
cd app/
Install dependencies
npm install
Run the app
npm run dev
# Navigate to the URL mentioned in the terminal

This is actually part of the build process. You just need to wait for a bit after doing npm run dev.
The Url would appear once the build completes.
https://user-images.githubusercontent.com/35926530/172625152-f5ed0b57-94aa-4ff7-9640-266200639c2d.mp4

Tried that now and got following error. What could be the reason? thanks
root@nodejs:~# cd /var/www/html/
root@nodejs:/var/www/html# cd app
root@nodejs:/var/www/html/app# PORT=3000 npm run dev

<EMAIL_ADDRESS>dev
node index.mjs

/var/www/html/app/node_modules/esbuild/lib/main.js:1237
return callback(new Error(error), null);
^
Error: The service was stopped
at /var/www/html/app/node_modules/esbuild/lib/main.js:1237:25
at /var/www/html/app/node_modules/esbuild/lib/main.js:629:9
at Socket.afterClose (/var/www/html/app/node_modules/esbuild/lib/main.js:607:7)
at Socket.emit (node:events:532:35)
at endReadableNT (node:internal/streams/readable:1346:12)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
root@nodejs:/var/www/html/app#

Have you installed node modules through npm install ?

yes after cloning the git and cd into app folder and installed npm as follows,
still the same error. What is the issue?
Node.js v17.9.1
root@nodejs:/var/www/html/app# npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving<EMAIL_ADDRESS>npm WARN Found<EMAIL_ADDRESS>npm WARN node_modules/three
npm WARN<EMAIL_ADDRESS>from the root project
npm WARN   3 more (@react-three/fiber, troika-three-text, troika-three-utils)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN packages/three-vrm
npm WARN<EMAIL_ADDRESS>npm WARN   node_modules/@pixiv/three-vrm
npm WARN
npm WARN Conflicting peer dependency<EMAIL_ADDRESS>npm WARN node_modules/three
npm WARN   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   packages/three-vrm
npm WARN<EMAIL_ADDRESS>npm WARN     node_modules/@pixiv/three-vrm
up to date, audited 1331 packages in 11s
136 packages are looking for funding
run npm fund for details
26 vulnerabilities (8 moderate, 17 high, 1 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run npm audit for details.
root@nodejs:/var/www/html/app#

did you git pull --recurse-submodules?

yes all of it is done sir as below. Not sure why I am getting this issue?

Resolving deltas: 100% (45496/45496), done.
Updating files: 100% (1487/1487), done.
Submodule 'packages/three' (https://github.com/webaverse/three) registered for p      ath 'packages/three'
Submodule 'packages/three-vrm' (https://github.com/webaverse/three-vrm) register      ed for path 'packages/three-vrm'
Submodule 'packages/totum' (https://github.com/webaverse/totum.git) registered f      or path 'packages/totum'
Submodule 'packages/wsrtc' (https://github.com/webaverse/wsrtc.git) registered f      or path 'packages/wsrtc'
Submodule 'packages/zjs' (https://github.com/webaverse/zjs.git) registered for p      ath 'packages/zjs'
Cloning into '/home/abjgd/app/packages/three'...
remote: Enumerating objects: 4883, done.
remote: Counting objects: 100% (11/11), done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 4883 (delta 5), reused 9 (delta 4), pack-reused 4872
Receiving objects: 100% (4883/4883), 242.96 MiB | 10.55 MiB/s, done.
Resolving deltas: 100% (1935/1935), done.
Cloning into '/home/abjgd/app/packages/three-vrm'...
remote: Enumerating objects: 137, done.
remote: Counting objects: 100% (137/137), done.
remote: Compressing objects: 100% (98/98), done.
remote: Total 137 (delta 42), reused 125 (delta 33), pack-reused 0
Receiving objects: 100% (137/137), 311.55 KiB | 4.05 MiB/s, done.
Resolving deltas: 100% (42/42), done.
Cloning into '/home/abjgd/app/packages/totum'...
remote: Enumerating objects: 3214, done.
remote: Counting objects: 100% (638/638), done.
remote: Compressing objects: 100% (196/196), done.
remote: Total 3214 (delta 521), reused 496 (delta 427), pack-reused 2576
Receiving objects: 100% (3214/3214), 481.68 KiB | 6.10 MiB/s, done.
Resolving deltas: 100% (2134/2134), done.
Cloning into '/home/abjgd/app/packages/wsrtc'...
remote: Enumerating objects: 758, done.
remote: Counting objects: 100% (55/55), done.
remote: Compressing objects: 100% (39/39), done.
remote: Total 758 (delta 28), reused 37 (delta 16), pack-reused 703
Receiving objects: 100% (758/758), 798.39 KiB | 7.53 MiB/s, done.
Resolving deltas: 100% (479/479), done.
Cloning into '/home/abjgd/app/packages/zjs'...
remote: Enumerating objects: 1045, done.
remote: Counting objects: 100% (4/4), done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 1045 (delta 1), reused 1 (delta 0), pack-reused 1041
Receiving objects: 100% (1045/1045), 168.82 KiB | 2.68 MiB/s, done.
Resolving deltas: 100% (629/629), done.
Submodule path 'packages/three': checked out 'ff70991543a05fdae9db93da4551ad72de      036f32'
Submodule path 'packages/three-vrm': checked out 'bedc92855f881e851114971f2e8f76      12fe12375d'
Submodule path 'packages/totum': checked out 'd8f87e8a203d6eed7d1d75e296ca316e4a      487d53'
Submodule path 'packages/wsrtc': checked out 'c0782accfa12cd0a9ff9203d65f9b59fde      4d2cc9'
Submodule path 'packages/zjs': checked out 'd226e1b0b258ae5710c613a6f2f0f5045530      dd1f'
abjgd@lamp-ubuntu-s-2vcpu-4gb-blr1-01:~$ # Go into the repository
abjgd@lamp-ubuntu-s-2vcpu-4gb-blr1-01:~$ cd app/
abjgd@lamp-ubuntu-s-2vcpu-4gb-blr1-01:~/app$ # Install dependencies
abjgd@lamp-ubuntu-s-2vcpu-4gb-blr1-01:~/app$ npm install
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving<EMAIL_ADDRESS>npm WARN Found<EMAIL_ADDRESS>npm WARN node_modules/three
npm WARN<EMAIL_ADDRESS>from the root project
npm WARN   3 more (@react-three/fiber, troika-three-text, troika-three-utils)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN packages/three-vrm
npm WARN<EMAIL_ADDRESS>npm WARN   node_modules/@pixiv/three-vrm
npm WARN
npm WARN Conflicting peer dependency<EMAIL_ADDRESS>npm WARN node_modules/three
npm WARN   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   packages/three-vrm
npm WARN<EMAIL_ADDRESS>npm WARN     node_modules/@pixiv/three-vrm
added 1325 packages, and audited 1331 packages in 1m
136 packages are looking for funding
run npm fund for details
26 vulnerabilities (8 moderate, 17 high, 1 critical)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run npm audit for details.
npm notice
npm notice New minor version of npm available! 8.11.0 -> 8.12.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.12.1
npm notice Run npm install -g<EMAIL_ADDRESS>to update!
npm notice
abjgd@lamp-ubuntu-s-2vcpu-4gb-blr1-01:~/app$ # Run the app
abjgd@lamp-ubuntu-s-2vcpu-4gb-blr1-01:~/app$ npm run dev

<EMAIL_ADDRESS>dev
node index.mjs

/home/abjgd/app/node_modules/esbuild/lib/main.js:1237
return callback(new Error(error), null);
^
Error: The service was stopped
at /home/abjgd/app/node_modules/esbuild/lib/main.js:1237:25
at /home/abjgd/app/node_modules/esbuild/lib/main.js:629:9
at Socket.afterClose (/home/abjgd/app/node_modules/esbuild/lib/main.js:607:7      )
at Socket.emit (node:events:539:35)
at endReadableNT (node:internal/streams/readable:1345:12)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
Node.js v17.9.1
abjgd@lamp-ubuntu-s-2vcpu-4gb-blr1-01:~/app$ # Navigate to the URL mentioned in       the terminal
abjgd@lamp-ubuntu-s-2vcpu-4gb-blr1-01:~/app$

Apologies for the inconvenience, I have tried on my end and the flow seems to be working working fine. There is some issue on your local. Please try these solutions:

npm install esbuild
-Make sure you are on latest node version

The custom host setup page no found https://docs.webaverse.com/docs/setup-custom-host Will be great if I get step by step process to setup it to work on cloud server like digital ocean with Ubuntu 20.04. thanks pls check below screenshot.

The custom host setup page no found https://docs.webaverse.com/docs/setup-custom-host Will be great if I get step by step process to setup it to work on cloud server like digital ocean with Ubuntu 20.04. thanks pls check below screenshot.

Yes both ports are open 3000/1
But not sure how to and why to change to local.webaverse.com
thanks.

Thanks Rob. I did that the other issue now I am facing is the service gets stopped. What is the reason for it? Any idea? thanks
root@ubuntu-s-2vcpu-4gb-amd-blr1-01:~/app# PORT=3000 npm run dev

<EMAIL_ADDRESS>dev
node index.mjs

Forced re-optimization of dependencies

Local: https://local.webaverse.com:3000/
World: wss://local.webaverse.com:3001/
The service was stopped

I'm not sure. You can try npm start instead of npm run dev. That will start the app running in the background with forever.

I used npm start and the result is the same. Maybe I am not able to run this webaverse and its so difficult to understand after changing host in hosts file to point to  (https://local.webaverse.com:3000/). There should be proper documentation for quick start which is missing. thanks, I will try Vircadia now.

I got it working on Ubuntu by doing this...

Clone repo: git clone --recurse-submodules https://github.com/webaverse/app.git

Go into the repository: cd app/

Pull recursively: git pull --recurse-submodules

Install dependencies:
. Instead of running "npm install" run "npm install --save-dev --ignore-scripts esbuild"

Run the app: npm run dev

@sumeru-digital we've rewritten the docs and quickstart. should be much more straightforward. Check out the README.md!

I used npm start and the result is the same. Maybe I am not able to run this webaverse and its so difficult to understand after changing host in hosts file to point to (https://local.webaverse.com:3000/). There should be proper documentation for quick start which is missing. thanks, I will try Vircadia now.

By the way, docs moved here:
https://docs.webaverse.com/docs/engineering/setup-custom-host


fix precommit

@keybase/react-hackers

The commits 5ae5cc799f23...cfc57b23d196 introduce visual changes on linux. :mag_right: 2 changed

Changed: unlock_folders-Success (before) (after)

Changed: Tracker-Tracker_Error (before) (after)

👍


Feature request: Ability to parse a stringified number on type-level

Suggestion
🔍 Search Terms
parse a number from stringified number on type-level, infer a number literal from a template string literal, template string literal to number literal
✅ Viability Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
Currently there is no way to parse "100" into 100 on type-level. One could try something like...
type T0 = "100" extends `${infer X}` ? X : never
// `T0` is `"100"`

But T0 is "100", rightfully so. And inferring 100 instead would be a breaking change. Let's try this...
type StringifyNumber<T extends number> = `${T}`

type T1 = "100" extends StringifyNumber<infer X> ? X : never
// `T1` is `number`

type T2 = "foo" extends StringifyNumber<infer X> ? X : never
// `T2` is `number`

Here T1 is number when it could have been inferred as 100. The feature request is to make T1 100, this too would be a breaking change but I think it'd break things a lot less. I think it makes sense to infer the narrowest possible type when we can.
📃 Motivating Example
Type-level arithmetic used to be impossible with large number prior to template literal types. But now we can stringify numbers on type-level then split them into digits and then do a carry-save addition. This makes type-level arithmetic very fast and "doable". Example adding 12345 & 6789...

But then there's no way to parse the string back to a number.
Type-level arithmetic makes working with dependent-ish types more complete. It'd be great we can have this feature, thanks!

Looks like a duplicate of #26382.
I would love to have built-in support for StringToNumber<T> and arithmetic operations like Add<M, N>, Subtract<M, N>.   I'd think the primary motivation for StringToNumber<T> would be to represent in the type level the conversion of strings to numbers at the value level (e.g., <T extends string>(x: T): StringToNumber<T> => +x or at least <T extends string>(x: T) => +x as StringToNumber<T>).
It's an... interesting approach to say that the motivating example for StringToNumber<T> is that it enables us to implement Add and Subtract and such via template literal types.  That's really neat, but I suspect that splitting strings and shuffling decimal digits around might not be the fastest nor most robust way for the TypeScript compiler to do arithmetic.  It's kind of like a child asking their parents for a smartphone "because it's the final ingredient of my elaborate Rube Goldberg machine".   Come on, kid, say "so I can text you in case of emergencies" or make up something about how it'll help you study for school.  You're saying the quiet part out loud! 😜

Hahaha yeah I was too honest with the motivation part, I just innocently wrote what motivated me instead of writing a more saner motivation that would perhaps motivate the typescript team :P
But yeah as you mentioned perhaps another motivation is to make the Number-like function's type more complete. Example as of today this wouldn't compile even when there are no problems with it...
declare let x: [string, number]
let foo: string = x[Number("0")]
//  ~~~
// Error: `string | number` is not assignable to `string`

With toNumber("0") which utilizes this feature the above code would compile.
Although I would not call this a duplicate of #26382 because it's not, but not even a spiritual duplicate because this feature would only enable arithmetic of number literals, whereas the linked feature (if implemented fully) would have to handle generics too.  Which would basically make typescript a dependently typed language, you'll be able to prove things with it...
declare const lhs =
  <A extends number, B extends B>
    (a: A, b: B) => (A + B) * (A + B)

declare const rhs =
  <A extends number, B extends B>
    (a: A, b: B) => A * A + A * B + B * A + B * B

const prove =
  <A extends number, B extends number>
    (a: A, b: B) => {

  let x = lhs(a, b)
  let y: typeof x = rhs(a, b)
  // If this compiles, which it would, lhs and rhs are equal
}

So having things like + and * on type-level are HUGEEEE features. And if we're not going to fully implement it and decide that that A + B would simply become number then meh, still useful with literals, but looses it's charm for me.
Although ofc it's still better than doing arithmetic with tricks and when involving decimals you'd have to make it IEEE 754 compat and what not, so yeah even arithmetic that only works with literals is great.
Regarding a StringToNumber intrinsic type: I don't mind it but I think I'd prefer keeping it as it is the description, feels more simple to me. It does make the feature less visible but then a lot of typescript features and tricks are like that :P

I didn't mean to bikeshed the naming; I was using StringToNumber<T> as a stand-in for however it happens to implemented.  If it's not intrinsic, that's fine, as long as you could define type StringtoNumber<T extends string> = ... yourself.

You can write
interface StringToNumber {
    "0": 0,
    "1": 1,
    "2": 2,
    "3": 3, // etc
}

if the numbers involved are too high for this approach to be reasonable, you are doing math that is not appropriate to be done in the type system.

The math part was just an example, what if one wants to make this compile...
const toNumber = <N extends number>(s: StringifiedNumber<N>) => Number(s) as N
type StringifiedNumber<N extends number> = `${N}`

const x: 1000 = toNumber("1000")

A type system that allows writing parsers, that added tail call optimization so that users can operate on larger strings and many more things, doesn't want to allow a simple operation of going from "1000" to 1000 doesn't make sense to me sir :) I'd love if you reconsider it.
You can always state that "We're adding this feature but it's not meant from doing typelevel maths with large numbers" and then people who still would do it (like in case of the rest of typescript features :P) would be on their own.

We're adding this feature but it's not meant from doing typelevel maths with large numbers

For context, this never works.

For context, this never works.

Haha yeah I know hence the "like in case of the rest of typescript features :P"
But what I meant was by stating that, the risk of "misusing" it is transferred to them. I'd do the same if I were to publish a library that does typelevel maths, I'd say "TypeScript team has said not to do this with large numbers" and then the risk further gets transferred to the person who actually would be responsible. In this way one is not deciding for someone else how much risk they should take, as different people have different amounts of courage to take risks.
Eitherway, I'm happy with typescript :P

We can have this trick to parse string to number from 0 to 999 since TS 4.5 has tail recursion optimization
type ToNumber<T extends string, R extends any[] = []> =
    T extends `${R['length']}` ? R['length'] : ToNumber<T, [1, ...R]>;

Ah that's nice especially the fact it can go upto 999

Ah that's nice especially the fact it can go upto 999

Yeah, this PR may help

I think this a duplicate of https://github.com/microsoft/TypeScript/issues/42938 .

Yeah it's essentially a duplicate as both issues are asking for same features


Allow test suites to be run on Windows

During my testing of Curve448, I tried running the test suites on Windows, but found that they don't compile, and can't be built without a bit of tweaking.
The compile error with Visual Studio is due to strcasecmp being missing.  Secondly, on Windows Perl scripts aren't executable and have to be run using the Perl interpreter directly; thankfully CMake is able to find cygwin Perl straight away without problems.

Automatic CI verification build not done, please verify manually.

Thanks! I seem to remember onlyfind_package(Perl) worked with recent versions of CMake, or maybe I'm confusing that with the integrated check for compiler version. Would you be able to check what the minimum version of CMake is? I don't think all our users are using the latest version.

Manuel, you don't work on a Saturday do you? I hope you enjoy your day off! :-)
The top-level CMakeLists.txt in mbedTLS specifies CMake 2.6 as the minimum version, which is quite old. I haven't installed it to test, but according to the CMake 2.6 documentation, the find_package() command is supported in that version, and it looks like FindPerl.cmake was distributed with v2.6. I would expect it therefore to work.

Anyway, thanks for checking that finding Perl this way works with the version of CMake we currently require.
I'm glad to see there was nothing more to do to get the test suites running on Windows :)

I was also trying to run tests on Windows 7 32 bits using the ENABLE_TESTING=On flag.
My environment:

Windows 7 32 bits
Cmake 3.5.0
Perl 5.22.1

I encountered the exact same issues as NWilson but also another one during the configure phase.
CMake Error at tests/CMakeLists.txt:122 (message):
  Could not create symbolic link for : E:/mbeddtls-development/tests/data_files
  --> Invalid option - "mbedtls-development".

The following lines are concerned:
file(TO_NATIVE_PATH "${CMAKE_CURRENT_BINARY_DIR}/data_files" link)
file(TO_NATIVE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/data_files" target)

if (NOT EXISTS ${link}
   if (CMAKE_HOST_UNIX)
      set(command ln -s ${target} ${link})
   else()
      set(command cmd.exe /c mklink /d ${link} ${target})
   endif()

Seems like TO_NATIVE_PATH is not doing is job as the path is still made of "/" after conversion instead of "" on Windows. Maybe related to this bug https://cmake.org/Bug/view.php?id=5939
For the moment, the only fix I found to be able to fully compile and test mbedtls on Windows is by making those changes:
+ if (CMAKE_HOST_WIN32)
+    string(REPLACE "/" "\\" link "${CMAKE_CURRENT_BINARY_DIR}/data_files")
+    string(REPLACE "/" "\\" target "${CMAKE_CURRENT_SOURCE_DIR}/data_files")
+ else()
+    file(TO_NATIVE_PATH "${CMAKE_CURRENT_BINARY_DIR}/data_files" link)
+    file(TO_NATIVE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/data_files" target)

- file(TO_NATIVE_PATH "${CMAKE_CURRENT_BINARY_DIR}/data_files" link)
- file(TO_NATIVE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/data_files" target)

Automatic CI verification build not done, please verify manually.


Find a UID match for pods with multiple ownerReferences

Change Overview
Currently, Kanister does not see any pods that have more than one item in their ownerReferences field as healthy. This PR aims to fix that.
Pull request type
Please check the type of change your PR introduces:

[x] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[x] :hamster: Trivial/Minor
[x] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test
[ ] :building_construction: Build

Issues

fixes #3208

Test Plan

I am not a go developer (unfortunately), but I tried my best. I think the basics are there and should work as expected, though I understand the static strings for Kind may be less than desirable.
Test/verify:

Create a Deployment/StatefulSet/etc.
Edit the pod(s) from the deployment, and add an item to ownerReferences
Create an ActionSet targeting this deployment
It should proceed without issues

[ ] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

I ran the tests in VSCodium, make golint and tried make test but make install-minio didn't work for me:
❯ make install-minio
make[1]: Entering directory '/home/alwyn/git/kanister'
running CMD in the containerized build environment
Running command within build container...
Deploying minio...
"minio" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "minio" chart repository
Update Complete. ⎈Happy Helming!⎈
The connection to the server localhost:8080 was refused - did you specify the right host or port?
real 0.47
user 0.14
sys 0.03
real 0,69
user 0,00
sys 0,00
make[1]: *** [Makefile:217: run] Error 1
make[1]: Leaving directory '/home/alwyn/git/kanister'
make: *** [Makefile:266: install-minio] Error 2

@Alveel Thank you for your contribution! 🎉 The team will review this soon.
We'll look into the minio issue. Added @hairyhum and @viveksinghggits.

@Alveel any particular reason why ownerKind is there?
Since we're using UID, it should not be necessary for matching (UIDs are global and not per resource kind).
It's a change in the public API of the library so it's a breaking change.
The change itself looks good, but it should be possible to implement without adding ownerKind.

Also tests are failing because we don't set the owner reference kind in unit tests.

You're right that the UID check is stringent enough. I'll remove it!

I've separated the check into a new function in utils and applied it to FetchReplicationController, FetchReplicaSet and FetchPods so they all have the same fix.
Let me know if this is okay!

@hairyhum @viveksinghggits done!


refactor(delete category): identify orphans

Not Ready. New Requirements

You need both back-end and front-end 'delete_category' branches
-Checkout back-end 'delete_category' branch
-Checkout front-end 'delete_category' branch

How to test:
2.  Test: Category with no associated listings

From 'Center Home' ensure that your category is has no listings
=Hamburger menu --> Manage: Center Settings
Select the category to be deleted
Press the 'Delete' selected record button(trash can)
Press 'Delete' button, in the Message box "Are you sure ...?"
Expected Result: The Category will be deleted

Test: Category with Listings that have multiple categories, and listings that only include the category you're deleting.

(Use 'Center Home' edit listing  to setup categories for your test cases)
=Hamburger menu --> Manage: Center Settings
Select the category to be deleted
Press the 'Delete' selected record button(trash can)
Press 'Delete' button, in the Message box "Are you sure ...?"
Expected Result: Message box displayed: Cannot delete category. Displays titles and number of listings that must be moved to another category before a deletion can be completed.

_Test: Category with Listings that have multiple categories. (No orphans)

(Use 'Center Home' edit listing  to setup categories for your test cases)
=Hamburger menu --> Manage: Center Settings
Select the category to be deleted
Press the 'Delete' selected record button(trash can)
Press 'Delete' button, in the Message box "Are you sure ...?"
Expected Result: Category is deleted

Will be added to automated delete category workflow


Can't Send WBI - or maybe anything other than EOS

The attached snaps will illustrate the problem. Logged into the Watch wallet and selected Worbli. From the Wallet, selected Send Tokens. The first blank screen looks good (snap 1), but once the amount to send is inserted into the field, it changes from displaying the number of WBI available to send, to the number of EOS in the account. (snap 2). From there it goes downhill. (snap 3.)
The trans exports to the Cold wallet OK, Signs OK, but when Broadcast  the error shows.

I'm able to reproduce - looks like the default token isn't being loaded and it's preventing the dropdown from populating.
A workaround, if you're in need right now, would be to go into Tools -> Airdrops / Custom Tokens, and add it manually with the following information:

Hi Aaron,
I did as you suggested on the Watch wallet. The correct number of WBI tokens did show up at that point. Then, getting back to the "staked" problem, I tried it again. This is the error when I try to broadcast:[Snap24.jpg]
Sent with Protonmail.com encrypted/secure email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, April 27, 2019 5:07 PM, Aaron Cox<EMAIL_ADDRESS>wrote:

I'm able to reproduce - looks like the default token isn't being loaded and it's preventing the dropdown from populating.
A workaround, if you're in need right now, would be to go into Tools -> Airdrops / Custom Tokens, and add it manually with the following information:
image
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

The attached image didn't make it into the github issue from the looks of it. What was the error?

At this point I'm pretty confident both this issue and issue #608 (your issue about staking) are both related. They both are returning that the signature being provided is being created by the public key of:
EOS5d9XJJcGtpxJ9PunCRKbJZnNUPWfgseCxTnQjQTqQiJKkjrbVv

This public key isn't associated to your account, but is somehow loaded in your cold wallet (or at least being used for signing). I was able to reproduce the error exactly in v0.7.8 by importing the incorrect key into the cold wallet.
You mentioned that when you go into Tools -> Manage Wallets on the cold wallet, and view the Worbli account, it displays one of these two public keys:
EOS72zCsA3patSjDdMShB1VKby5yWxhfpg4aRZku7s4UQMvEYb4hL
EOS7yiU4RkY2vUb2pvHxP7B1qcVv9NRbjy4fRmiGUNXQ8iG91R7qN

I'm not entirely sure how that's happening, unless somehow the public key was updated without updating the private key in storage associated to it. I'm trying to reproduce that currently.
One thing that might work is simply re-setting up the Worbli cold wallet. With the current version, the only way to do this is to either add a 2nd account, then removing the first -or- resetting the application completely (through Tools -> Reset Application) and going through the setup process again and importing the keys.


Report reasons for flutter driver test failure in test log

https://bugs.fuchsia.dev/p/fuchsia/issues/detail?id=37575. Conversation should occur there.
cc @iskakaushik, @zanderso as it seems to be tooling related.

This sounds like an artifact of Fuchsia choosing to run the Flutter driver on the device alongside the app under test. The solution here is to run the driver on the host instead. I will close this as not being actionable, but feel free to re-open the issue if I am mistaken. Thanks!


OTH-520 Update dependencies

@ThomasReyskens We've updated dependencies with a thorough look at the peer dependencies of all the tools involved. Meaning that we're sure the combination of these packages work together and no more "invalid peer dependency" warnings when you install the linting packages.
Do you agree that we enforce the use of these versions (both the latest) of eslint and typescript?


Update to 7.0 RTM

Thanks, will you ping me when 7.0.0 is published?

@ErikEJ Thanks for keeping the library updated! v7.0.0 should be live on NuGet.org now ✨


merge master

Temporary coordinate passing to apply forgotten in tti

You won't need to do this after the PR I am about to submit

As I said, temporary fix, don't know when next PR will land and what's in it, just want master to produce correct results.

if Travis was green without catching this issue, then we have a SERIOUS problem!!!

Closing as #273 fixes it.


Added output type s3

Signed-off-by: Yuvraj<EMAIL_ADDRESS>
What type of PR is this?
/kind feature

Any specific area of the project related to this PR?
/area outputs

What this PR does / why we need it:
Added new output type s3. Now you can upload json payload to s3
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign leodido after the PR has been reviewed.
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @evalsocket! It looks like this is your first PR to falcosecurity/falcosidekick 🎉

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

5c81327 wip: added stats and handler for new output type

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign issif after the PR has been reviewed.
You can assign the PR to them by writing /assign @issif in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

a15cd3c Small fixes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

2bf8e7e Small fixes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

f3b48fb Added docs for aws s3 output type

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Issif README changes are done

/lgtm
thanks for this addition

LGTM label has been added.  Git tree hash: fdaf143c5a068e758a25bd38992a80cffb415b29

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [cpanato]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Issif README changes are done

I can't see AWS S3 in List of available outputs 🤔

New changes are detected. LGTM label has been removed.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

d6b420d Updated output list in readme

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif,cpanato]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 966d98d929297f4bf1ef196bede23b0cfaaf111d


'No results page' enhancements

If a user makes a search that has no results, it might be nice to give the user some suggestions on how to widen the scope of their search. This could be handled in many ways, either with some simple text or with some actual controls that are contextual to the user's search. Some examples of what types of suggestions I'm thinking of are:

Try enabling other media types
Enable more licenses
Try other providers

This is not a high-priority concern at all.

hey @zackkrida  I want to work into this can you go ahead

Hi @vj27111997 this isn't ready for work yet. It needs more discussion. I can update you when it is ready though.


Start even if failed to parse certificate file

fluentd version: 1.4.2
Environment information:

Operating system: 16.04.6 LTS (Xenial Xerus)
Kernel version: 4.4.0-145-generic

Your configuration

<source>
  @type forward
  bind <IP_ADDRESS>
  port 24224

  <transport tls>
    cert_path /fluentd/etc/fluentd.pem
    private_key_path /fluentd/etc/fluentd.pem
  </transport>
</source>

<match **>
  @type null
</match>

It seems that fluentd start even if failed to parse certificate file in forward input with TLS.
If we use a certificate file that does not end with a newline (\n), it will not match Fluentd's internal pattern^1. However Fluentd seems to start and listen on TLS connection. If you connect to Fluentd with TLS in this state, all handshakes will fail.

I literally just had this exact issue, though in my case, it failed to even open port 24224, it just hung on the regex.
I think the regex in: plugin_helper/cert_option.rb:171
pattern = Regexp.compile('-+BEGIN CERTIFICATE-+\n(?:[^-]*\n)+-+END CERTIFICATE-+\n', Regexp::MULTILINE)

Should be changed from
'-+BEGIN CERTIFICATE-+\n(?:[^-]*\n)+-+END CERTIFICATE-+\n'

to
'-++BEGIN CERTIFICATE-++\n(?:[^-]*\n)+-++END CERTIFICATE-++\n?'

(The ++ is a "possessive" greedy match which should speed up non matches)

For both cases, adding ? to last fixes the problem, right?

Yes, adding '?' to the end is a simple way.

@summerwind If you have a chance, could you send a patch?

I sent a patch on #2466.


Use pad from numpy

skimage.util.pad was deprecated in favor of the same function from numpy and is removed in version 0.19.
Fix #528
Fix #544

Everytime I try to fix the code, it appears this everytime I use a custom video...
https://imgur.com/a/OZBswUc

@paburo-san666 Thanks for the comment. I can’t see the image. Could you please attach it here?

https://imgur.com/qkNP15j

@paburo-san666 Thanks for the comment. I can’t see the image. Could you please attach it here?

Sorry hehe
Here is it!

@paburo-san666 I've opened #570 to address the issue you mentioned. Sorry to keep you waiting.


Make sure local cluster is always in the managedcluster list

Make sure local-cluster is always a part of  internal managedcluster list and not depend on the CRUD events of the Managedcluster  resource because when disableHubSelfManagement: true, the resource for local-cluster will not be created.
Use sync.Map for thread safe read and writes
fix unit tests to run predicate tests against managedcluster resource and not deployment

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/test test-e2e

/test test-e2e

/cherrypick release-2.11

/cherrypick release-2.10

/cherrypick release-2.11

/cherrypick release-2.10


Add validator's priority retrieval into Factory

I noticed that it was impossible to set validator's priority using the "array notation", even if this feature was already there as it already exists for filters (see line 384 of Factory.php).
To add the priority, it will be enough to add the priority key in the array:
$inputFilter[] = [
    'name' => 'text_elt',
    'required' => true,
    'filters' => [
        ['name' => 'StripTags'],
        ['name' => 'StringTrim']
    ],
    'validators' => [
        [
            'name' => 'StringLength',
            'options' => [
                'max' => 256
            ],
            'priority' => 2
        ]
    ]
];

FactoryTest fix
I also noticed that the FactoryTest class had a minor issue, which was that validators where not tested inside the testFactoryWillCreateInputWithSuggestedValidators method.
I fixed the loop and added a final assert to verify that all the validators have been tested.

@webimpress
I think an unit test is missing here. Like this one:
https://github.com/zendframework/zend-inputfilter/blob/a23e67d41de09bbc325543acb756ba448f182c20/test/FactoryTest.php#L685-L726

@froschdesign test added. Would you mind to have a look on it, please?
It's a bit tricky as I mentioned in the commit comment - we can't use getValidators on ValidatorChain, as the result is not sorted by priority. When validators are called (in isValid) these are ordered, and this is how I check it.

@webimpress

When validators are called (in isValid) these are ordered, and this is how I check it.

👍

Thanks, @mtagliab!


Mayank del/issue693

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes:  #693

Type of change

[x ] New feature (non-breaking change which adds functionality)

Checklist:

[ x] I have made this from my own
[x ] My code follows the style guidelines of this project
[x ] I have performed a self-review of my own code
[x ] I have commented my code, particularly in hard-to-understand areas
[ x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@DEEPALI-SUK  maam ,try merging it fast. So that , I will create next PR soon.

@DEEPALI-SUK maam ,try merging it fast. So that , I will create next PR soon.

do the changes fast and u can create the next pr also, before 25th

@DEEPALI-SUK maam , now check it, i think , i have completed everything


Failed to parse source for import ... because content contains invalid JS syntax

Hello, I've just discovered docus and nuxt today, and I'm really hyped by the project and the idea behind it overall.
But I'm facing 2 issues, one that I could resolve, and the other one that I can't get my head to wrap around.
So I will just explain them here :
First error
Description
While trying to install Docus from scracthon a new project, I used the first command on the docs they have :
npx nuxi@latest init docs -t themes/docus
Everything went fine so I went onto the second step and executed :
npm install
Which brings me to my first error :
npm ERR! syscall open
npm ERR! path C:\work\mydocs\package.json
npm ERR! errno -4058

npm ERR! enoent ENOENT: no such file or directory, open 'C:\work\mydocs\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in: C:\work\npm-cache\today.log

Turns out the package.json file which is created when doing the npm install command gets created in this folder :
C:\work\mydocs\docs\package.json
But as is telling the error, the file should be at :
C:\work\mydocs\package.json
Solution
So I resolved this issue by moving the file to the right destination, re-executed the command, and it worked fine.
Second error
But now here comes my 2nd issue. So when trying to execute npm run dev I face another issue. The one in the title :
The command starts as normal, and as it should :
Nuxi 3.1.2
Nuxt 3.1.2 with Nitro 2.1.2

  > Local:    http://localhost:3000/
  > Network:  http://<IP_ADDRESS>:3000/

 ERROR  (node:20688) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

 ERROR  Failed to parse source for import analysis because the content contains invalid JS syntax. If you are using JSX, make sure to name the file with the .jsx or .tsx extension.

 ERROR  Failed to parse source for import analysis because the content contains invalid JS syntax. If you are using JSX, make sure to name the file with the .jsx or .tsx extension.

 ERROR  RollupError: Unexpected token (Note that you need plugins to import files that are not JavaScript)

For a moment I thought it was the tsconfig.json file that was making this error, because I have seen a red dot at the right of the name, and when I looked for the issue it said that it couldn't read the file because the syntax wasn't TypeScript. Which it isn't since it's a .json file.
So I gotta say I'm quite suprised by this error, as I've not added any file, apart from the base template generated, and I don't know if I need to install another package to fix this issue. Like a jsx and tsx support package or something.
Third error
Anyway, I don't have any clue of what's happening for the second error, plus I have a third error concerning an unexpected token :
i Vite client warmed up in 3565ms

 ERROR  RollupError: Unexpected token (Note that you need plugins to import files that are not JavaScript)                                                          nitro

1: const _lazy_7iGOyM = () => import('C:/work/mydocs/node_modules/nuxt/dist/core/runtime/nitro/renderer');
                                                                                ^
2:
3: export const handlers = [

√ Nitro built in 168 ms

Conclusion
So if anyone has an idea to help me solve all this issue, that would be awesome. And if you need more information tell me.

Turns out I'm a dummy, the problem was coming from my file name. I renamed the path files for privacy reasons in this issue, but my folder name had a ' in its name. And therefore, the program was unable to locate the files.
Sorry for the disturbance. I will close the issue with this comment.


enrich debug  w/ mixins[SLT-330]

[goreleaser]

Description

Summary by CodeRabbit

New Features

Introduced a new utility for converting Ethereum transaction data into a structured format for tracing and monitoring.
Added Mixins to enhance debugging capabilities in transaction processing.

Bug Fixes

Improved logging and error handling for transaction submissions.

Documentation

Updated README to include details on Mixins for better debugging.

Tests

Streamlined test suite by removing redundant tests while retaining core functionality tests.

accidentally merged this a tad prematurely


Update OSS Folder's Suffix

What changes are proposed in this pull request?
Update OSS Folder's Suffix
Why are the changes needed?

When you need to create a directory, you need to add / at the end of a key, instead of _$folder$.
OSS identifies whether there is / at the end of the key to determine whether the user wants to operate a file or a directory.

It is reasonable to throw a "NoSuchKey" exception when creating or deleting a directory:
When alluxio creates a directory, it will enter the ObjectUnderFileSystem#mkdirs method, and then it needs to determine whether the path already exists, and then call it accordingly.

Use the ObjectUnderFileSystem#isDirectory method, add / to the end of the directory, and then call the OSSUnderFileSystem#getObjectStatus method to send a getObjectMetadata request to OSS. If the directory does not exist, an exception "NoSuchKey" will be thrown, but the created directory itself cannot exist if there is already a directory with the same name.
Use the ObjectUnderFileSystem#isFile method to determine whether it is an existing file, and then call OSSUnderFileSystem#getObjectStatus to send a getObjectMetadata request to OSS. If the file does not exist, an exception "NoSuchKey" will be thrown, but the created directory itself cannot exist with a file with the same name.
Use the ObjectUnderFileSystem#mkdirsInternal method to add '/' to the end of the directory, and then call the OSSUnderFileSystem#createEmptyObject method to send a putObject request to OSS to create a new directory.
Call the ObjectUnderFileSystem#getStatus method to obtain the created key information
First call the OSSUnderFileSystem#getObjectStatus method and pass in the key without '/' suffix, an exception "NoSuchKey" will be thrown.
Then call OSSUnderFileSystem#getDirectoryStatus to determine whether it is a path, call the ObjectUnderFileSystem#isDirectory method, then call the OSSUnderFileSystem#getObjectStatus method, pass in the key with '/', and send getObjectMetadata to OSS to obtain the key information.

When deleting a directory, call the ObjectUnderFileSystem#getStatus method to obtain information about the deleted directory.

First call OSSUnderFileSystem#getObjectStatus and pass in the key without the '/' suffix. Since the key itself is a directory rather than a file, an exception "NoSudhKey" will be thrown.
Then call the OSSUnderFileSystem#getDirectoryStatus method, and then call the ObjectUnderFileSystem#convertToFolderName method in ObjectUnderFileSystem#isDirectory with the '/' suffix, and pass the key to the OSSUnderFileSystem#getObjectStatus method to obtain the key information.

Therefore, it is reasonable to throw three "NoSuchKey" exceptions when creating a directory, and throw one "NoSuchKey" exception when deleting a directory.
Does this PR introduce any user facing changes?
No.

More information: Aliyun OSS Java SDK - Manage Directory


Mio is not showing the section images according to section number

Hi,
We are preparing Mio (and later LZ links) where several series are mixed. We thought Mio would display the order according to the section numbers but apparently not: https://miosdv.apps-dev.hbp.eu/index.html?bucket=https://data-proxy.ebrains.eu/api/v1/public/buckets/img-439ccbe7-c645-11ec-b100-00090faa0001&collectionMode=true&limit=200
Could you change some settings so it can follow the section numbers? or is it possible only in LZ?

Noo, it’s only possible in LZ. Just kidding :)
Will sorting the file names alphabetically do the thing? Or you need something more advance?

Good! I am not sure an alphabetic sorting will help. It would be good if it is able to recognize the file naming convention: s_xxx

OK. Since LZ is the gold standard :) for sorting @Tevemadar do you sort them alphabetically?

Hi @darwinjob
What is the status here?


Using custom maven settings.xml to pull the maven dependencies from the remote repository

Description:
The settings.xml specified by settings-path will not take effect, the project deployment needs to pull the maven dependencies from the remote repository, but the default settings will blocker all the http requests, and cannot override the mirror.
Justification:
      - name: Set up Java version
        uses<EMAIL_ADDRESS>        with:
          java-version: ${{ env.JAVA_VERSION }}
          distribution: ${{ env.DISTRIBUTION }}
          cache: 'maven'
          server-id: nexus-snapshots
          server-username: ${{ secrets.MAVEN_REPO_USERNAME }}
          server-password: ${{ secrets.MAVEN_REPO_PASSWORD }}
          settings-path: ${{ github.workspace }}
      - name: Print workspace path
        run: |
            echo "Workspace Directory: $GITHUB_WORKSPACE"
            ls -la $GITHUB_WORKSPACE

      - name: check setting
        run: cat ${{ github.workspace }}/settings.xml

      - name: check mvn setting
        run: mvn help:effective-settings --settings ${{ github.workspace }}/settings.xml

      - name: Build with Maven
        run: mvn clean package -s ${{ github.workspace }}/settings.xml -gs /dev/null -X

and i put my personal settings.xml in project root directory
i try to overide the settings but it doesn't work, always blocker the request

Hello @loqiu,
Thank you for this feature request. We will investigate it and get back to you as soon as we have some feedback.

Hello @loqiu, Thank you for this feature request. We will investigate it and get back to you as soon as we have some feedback.

Thx, i fix with 'overwrite-settings: false' this setting, but although i have overwrite the settings.xml and overwrite the default-http-blocker, i still can't pull the dependency from the remote rep with right username and password, 'i can do it in local'. so the action will block the all http request?


[rfr] Contributor search: support filtering on multiple fields

Ticket
https://openscience.atlassian.net/browse/PREP-90
Purpose
Allow the /submit page "Authors -> search by name" box to search across a variety of name fields instead of just full_name.
See description of the multifield contributor search syntax here: https://github.com/CenterForOpenScience/osf.io/pull/6145
How to test this
In the OSF, go to the settings page (/settings). Edit the profile fields so that full_name, given_name, middle_names, and family_name all have different values.
Then on the "add a preprint" (/preprints/submit) page, search for each of those values in turn. (taking care to search for someone else in between so that it's clear your search is doing something)
In the old search, the user would only show up if you matched the value in the full_name field. Now, a match for any of those fields will return the user, and the search result will display their full name.

Tested functionality and reviewed code.


Skipped frames

The expand/collapse causes big frame skipping on Nexus 7 device when this layout is used in recycler view, but behaves seemingly on other devices. What might be the cause of such behavior?

A layout pass is called on the parent layout for each frame of the expansion/collapse animation. This operation can be expensive if your parent layout is too complex (if it has too many children, or very complex views, such as a mapview or a webview).
If you're having problems with performance you can try simplifying your parent layout, or disabling the animation on older devices.

I don't think problem is with layout as same one works without problem on other devices (Pixel xl, Axon 7, galaxy s3) but has horrible performance on Nexus 7

I assume you're talking about the original Nexus 7 which has horrible performance in general.
Honestly I don't think it's useful to spend much time optimizing code for very old devices, unless you have a lot of users with devices that are 5+ years old.
In any case this isn't a problem with ExpandableLayout. I've tried to make the expansion as efficient as possible, but the fact is that you need to perform a layout pass on the parent layout for each frame and that operation is inherently expensive on Android due to how the system is designed.
As I said above, if this is an important issue for you, you could try disabling animations on old devices.