Add a feature to directly import a cURL request

Tell us about the task you want to perform and are unable to do so because the feature is not available
Currently the only way to make a request in APIDash is by using http request format.
Describe the solution/feature you'd like us to add
We can add a feature where it is possible to make a request using the cURL format

@ashitaprasad @animator I am working on this!

Ohh cool! Will close this


Scanning recipes from alt gives different / wrong results

As discussed on Discord, when I scan recipes from an alt, I get very different results than on the actual character. The amount of recipes scanned, the concentration value, the profit, ... All different
I use Auctionator data and had just done a full scan of the auction house.
Scanned from alt:

Scanned from actual char:

Cheers

should be fixed in 19.4.2


Add PoliCheck tool to aggregate report pipeline

Start compliance stage in the aggregate report pipeline.
Add PoliCheck tool to the compliance stage.

/js - dataplane - pr

/azp run js - dataplane - pr

/check-enforcer override

Merging this after consulting with @praveenkuttappan


Unsupported texture format

Getting a bunch of this in the console:
[46057:0613/091910.975627:ERROR:gles2_cmd_decoder.cc(16945)] [.DisplayCompositor-0x7fd0f00bda00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[46057:0613/091910.979481:ERROR:gles2_cmd_decoder.cc(11694)] [.DisplayCompositor-0x7fd0f00bda00]GL ERROR :GL_INVALID_VALUE : glScheduleCALayerCHROMIUM: unsupported texture format

OS X Sierra 10.12.5 (16F73)

@keturn I can't reproduce this on OS X Sierra 10.12.5. When do you get these errors? Maybe a driver issue.

I'm afraid I haven't quite figured that out. It's not all the time, so there's some precondition for it ... and when it happens, there's roughly a dozen repetitions of that.
I'll let you know if I start to see any pattern.

Please re-open if it happens again.


Fix version of prom-operator to 0.11 to provide consistent config for…

… Kubernetes and Openshift

@jpkrohling @theute Could you take a quick look.
cc @jmazzitelli


Too much restriction on pyarrow dependency

What went wrong? 🤔
There is a breaking change in dependencies going from 3.1.1 to 4.0 by a restriction on pyarrow.
Packages like databricks-sql-connector==3.4.0 cannot be installed now because of this conflict.
INFO: pip is looking at multiple versions of taipy to determine which version is compatible with other requirements. This could take a while.
ERROR: Cannot install databricks-sql-connector==3.4.0 and taipy==4.0.0.dev4 because these package versions have conflicting dependencies.

The conflict is caused by:
    databricks-sql-connector 3.4.0 depends on pyarrow<17 and >=14.0.1
    taipy 4.0.0.dev4 depends on pyarrow<=17.9.9 and >=17.0.0

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Expected Behavior
We should be able to install Taipy alongside databricks-sql-connector==3.4.0.
Steps to Reproduce Issue
pip install git+https://github.com/Avaiga/taipy.git databricks-sql-connector==3.4.0

Version of Taipy
develop - 10/9/24
Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%.
[ ] Create related issue in taipy-doc for documentation and Release Notes.

Code of Conduct

[X] I have checked the existing issues.
[ ] I am willing to work on this issue (optional)

I can work for this issue! Kindly assign me this issue under hacktoberfest 2024

This is not yet open for contribution. We will assign you if it is. Thank you @SaumyaSubham !

What is databricks take on this ?
Do they have a planning for supporting  Arrow version 17+ ?

I have found this: https://github.com/databricks/databricks-sql-python/issues/427

@FredLL-Avaiga DO you remember any reason to update the minimal supported version?
Supporting 17+ only is very restrictive. I would like to avoid so much restriction.

@SaumyaSubham
I labeled this issue as staff only because we need to make sure the Pyarrow version of the Taipy Community edition matches the version in Taipy Enterprise Edition. Indeed, Taipy Enterprise has a native integration with Databricks.
Thank you for your understanding.

@FredLL-Avaiga DO you remember any reason to update the minimal supported version?
Supporting 17+ only is very restrictive. I would like to avoid so much restriction.

I suppose for the time being we can support 16+
There was no API changes in front or back

@S-YED thanks for your contribution!
Seems to me that the databricks team is working on a change that will remove the upper bound for dependencies => You will be able to install taipy (even with pyarrow>=17.0.0,<18.0) after their PR is merged.
https://github.com/databricks/databricks-sql-python/pull/452
However, this may take a while, so I would suggest 2 approaches:

@S-YED can you taipy and databricks-sql-connector by installing them separately

pip install git+https://github.com/your-username/taipy.git
pip install databricks-sql-connector-3.4.0

@jrobinAV we can expand pyarrow on our side to include 16.0 as the baseline as 16.0 is acceptable by databricks-sql-connector

Sounds fair.

@toan-quach
THe related PR https://github.com/Avaiga/taipy/pull/1988 has been closed without merging. PLease proceed with the issue by your own. Thank you.


Drop duplicate copy of server code for tests

truss_container_fs resulted in maintaining duplicate code, and updating it via the command was not super stable because we only rebuild the docker image if the hash of the truss changes (as opposed to the files in the truss/templates directory.
This PR removes the duplicate code, in favor of generating this directory at test time with a single docker build.

They don't become integration tests. All the tests in the CI still run in about 2 minutes. The truss_container_fs image is generated once for the whole test session because of the way the fixture is used.

Discussed offline, this seems fine for now, until we can offload truss_fs creation to a github action.

🤩


Deadline cutoff for 1.0

Will support all requests prior to this in the upcoming release. The proceeding issues filed will be processed for the next version. Thanks for all of the engagement and stay tuned for 1.0!

1.0 is out -> https://github.com/cncf/landscape#current-version

@shawnpreissner As 1.0 is out, is this issue to be closed?

@tnir I leave open until next rev is out, for a quick way to count net new GitHub requests between versions. Total issues aren't an accurate representation, since some open issues are longer term requests.

Thanks all for the feedback! Closing as 1.1 has now released, check out the most recent version https://github.com/cncf/landscape#current-version


change transfromer to transformers

Ⅰ. Describe what this PR does
Fixed #4101
this pr is to corrected 'transfromer' to 'transformers' of file pkg\ddc\jindo\load_data.go:21:47;

/lgtm


Destination Host Unreachable ubuntu 14.04 on aws

Hi I am running docker swarm together with docker-compose on AWS.
I added the following lines to my docker-compose to prevent the addresses colliding:
networks:
   default:
     ipam:
       config:
         - subnet: <IP_ADDRESS>/24

docker info returns the following information:
ubuntu@ip-10-0-0-7:~/prems$ docker info
Containers: 26
 Running: 3
 Paused: 0
 Stopped: 23
Images: 19
Server Version: swarm/1.2.0
Role: replica
Primary: <IP_ADDRESS>:4000
Strategy: spread
Filters: health, port, dependency, affinity, constraint
Nodes: 3
 ip-10-0-0-164: <IP_ADDRESS>:2375
  └ Status: Healthy
  └ Containers: 8
  └ Reserved CPUs: 0 / 2
  └ Reserved Memory: 0 B / 4.052 GiB
  └ Labels: executiondriver=, kernelversion=3.13.0-74-generic, operatingsystem=Ubuntu 14.04.3 LTS, storagedriver=devicemapper
  └ Error: (none)
  └ UpdatedAt: 2016-05-02T10:41:16Z
  └ ServerVersion: 1.11.0
 ip-10-0-0-165: <IP_ADDRESS>:2375
  └ Status: Healthy
  └ Containers: 9
  └ Reserved CPUs: 0 / 2
  └ Reserved Memory: 0 B / 4.052 GiB
  └ Labels: executiondriver=, kernelversion=3.13.0-74-generic, operatingsystem=Ubuntu 14.04.3 LTS, storagedriver=devicemapper
  └ Error: (none)
  └ UpdatedAt: 2016-05-02T10:41:17Z
  └ ServerVersion: 1.11.0
 ip-10-0-0-166: <IP_ADDRESS>:2375
  └ Status: Healthy
  └ Containers: 9
  └ Reserved CPUs: 0 / 2
  └ Reserved Memory: 0 B / 4.052 GiB
  └ Labels: executiondriver=, kernelversion=3.13.0-74-generic, operatingsystem=Ubuntu 14.04.3 LTS, storagedriver=devicemapper
  └ Error: (none)
  └ UpdatedAt: 2016-05-02T10:40:57Z
  └ ServerVersion: 1.11.0
Plugins:
 Volume:
 Network:
Kernel Version: 3.13.0-74-generic
Operating System: linux
Architecture: amd64
CPUs: 6
Total Memory: 12.16 GiB
Name: 238051dcadf4
Docker Root Dir:
Debug mode (client): false
Debug mode (server): false
WARNING: No kernel memory limit support

My problem is that the created network works only for some of the machines and not for all.
when i enter a container in a machine that fails and I try to curl an address in the network range i get:
curl <IP_ADDRESS>:5672
curl: (7) Failed to connect to <IP_ADDRESS> port 5672: No route to host
ping returns:
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
92 bytes from 427914c370a9 (<IP_ADDRESS>): Destination Host Unreachable
92 bytes from 427914c370a9 (<IP_ADDRESS>): Destination Host Unreachable
92 bytes from 427914c370a9 (<IP_ADDRESS>): Destination Host Unreachable
92 bytes from 427914c370a9 (<IP_ADDRESS>): Destination Host Unreachable
92 bytes from 427914c370a9 (<IP_ADDRESS>): Destination Host Unreachable
I thought that these issues were gone by now,
Thanks,
Ofer

Just to add a note here... I also get Destination Host Unreachable responses from ping until I enable the "All Traffic" rule on my AWS VPC security-group.
e.g. even with specific rules 2377/TCP,  7946/TCP/7946/UDP and 4789/TCP/4789/UDP setup in the security-group overlay networking fails.

UPDATE: Just to update on my previous note, it seems to be something in AWS Security Groups that isn't working. If I add an "All Traffic" for the subnet my swarm lives on then suddenly things start working. I don't like blanket "Allow All" rules (even if only from a know private subnet) but at least it's a workaround.

@OferE It has been detected that this issue has not received any activity in over 6 months. Can you please let us know if it is still relevant:

For a bug: do you still experience the issue with the latest version?
For a feature request: was your request appropriately answered in a later version?

Thank you!
This issue will be automatically closed in 1 week unless it is commented on.
For more information please refer to https://github.com/docker/libnetwork/issues/1926


Writing floats is locale dependent

Hi,
CJSON is not locale independent. Specifically, if the current locale wants us to encode the decimal point as a comma, as in Germany, CJSON will happily do so.
This makes the other side rather unhappy. Worse, if the problem occurs in a list it's not even recognized by the receiving parser.
Please fix!

Afaik, this bug was fixed in 1.0.4.
Can you please provide some more details about the platform you are using, and how you are compiling Lua CJSON?
There are 2 ways of compiling floating point support:

Adapting the system strtod/snprintf routines to use "." with any locale (the default)
Using internal dtoa/g_fmt routines to avoid any locale issues and increase performance. (USE_INTERNAL_FPCONV).

This is documented in the manual under Built-in floating point conversion.

I'm using the Debian package for 2.1 which doesn't use specific preprocessor arguments.
Apparently the program I'm linking with manages to change the current locale after your "fpconv_init" gets called.
I'll ask the Debian maintainer to build with USE_INTERNAL_FPCONV, but cjson still needs to support that use IMHO.

Anyhow, what about locales that don't even use "our" digits?
Please consider unconditionally switching to USE_INTERNAL_FPCONV and/or using that as the default.

While the hack to detect/adapt the decimal separator for different locales is ugly, I'm not aware of any specific locales where it doesn't work (happy to hear otherwise).
Changing the locale after the program has started is typically a bad strategy. setlocale isn't thread-safe, and various code might make assumptions based on the previous configuration.
I agree it would be better to have a single implementation. However, there are tradeoffs:

Platform routines

Pro: Work everywhere
Con: Slower, breaks if locale changes to a different decimal separator mid-execution (ideally that should never happen).

Internal dtoa routines

Pro: Faster
Con: Needs to be correctly built for little/big endian, and with/without Pthreads.

It's an awkward tradeoff. I wanted Lua CJSON to just work out of the box, which means using the platform routines. The internal dtoa has advantages but must be build correctly for the platform and the codebase.
If Debian wants to use the internal routines it will need to correctly set the endianness, and probably always enable/link pthreads (since it may be used in a multi-threaded application).

Another option: Can you call fpconv_init after the locale has been changed? fpconv_init isn't thread safe, but neither is setlocale, so it shouldn't be any worse.

Another option..
You could use compiler defines to autodetect the correct endianness for USE_INTERNAL_FPCONV by adapting something like this: https://stackoverflow.com/a/58642785
It might be reasonable to add something similar to CJSON as well, but it would need testing across a wide range of compilers/platforms first.

Another option..
You could use compiler defines to autodetect the correct endianness for USE_INTERNAL_FPCONV by adapting something like this: https://stackoverflow.com/a/58642785
It might be reasonable to add something similar to CJSON as well, but it would need testing across a wide range of compilers/platforms first.


update readme

Update readme with

more comparisons to existing tools
instructions on how to make a package pipx-compatible
instructions on installing from source in the readme
try to more clearly differentiate install vs. run. I saw a case where someone was installing a package, and thought they needed to pipx run it after installing.

This is a lot clearer in general, nice.
I think we need to find a gentler introduction to the idea of "entry points".  I'd be willing to bet that's an unfamiliar term to many people who would like to use python applications via pipx.
For example, in Overview: What is pipx?, instead of "In fact, it uses pip, but is focused installing and managing packages that have entry points." maybe instead "In fact, it uses pip, but is focused on installing and managing packages that contain applications."  It could be some other text (not sure what's the clearest and most accurate), but at least in the overview we shouldn't require people to know what entry points are.  (Also, note there's a missing "on" in the original sentence.)
Later you have a very nice explanation of what an entry point is.

Another typo:
If you're a poetry user, use these instruction.
should be
If you're a poetry user, use these instructions.

Good feedback, thanks. I updated it again. It still feels like it could use some more smoothing out, but I think it's a little better. LMK what you think.

As of now:

It's closely related to pip. In fact, it uses pip, but is focused installing and managing packages that can be run from the command line directly as applications. pip is a general-purpose package installer for both libraries and apps with no environment isolation. For library installation you should use pip (or a similar tool), not pipx. But for application installation, consider pipx since it adds a layer of isolation on top of pip specifically for command-line tools.

How about adding "Python" to the first sentence, just to be clear we are not a generic package manager (like brew, apt suggestions in paragraph above):
Before

"but is focused installing and managing packages"

After

"but is focused on installing and managing Python packages"

How about explaining in a phrase what isolation means:
Before

"consider pipx since it adds a layer of isolation on top of pip specifically for command-line tools."

After

"consider pipx since it also adds isolation: pipx creates a separate virtual environment for each application and its associated packages."


Update postgres-configs.md

In line with request here: https://github.com/dbt-labs/dbt-core/issues/6052
Description & motivation
I've changed the documentation to show how to use the configuration option for columnar in the postgres adapter. The pull request can be found here: 6053
To-do before merge
Include any notes about things that need to happen before this PR is merged, e.g.:

[ ] Ensure https://github.com/dbt-labs/dbt-core/issues/6052 is merged

hey @Dennis8 , thanks for opening this up. Closing this PR for now, given the rationale explained in https://github.com/dbt-labs/dbt-core/issues/6052


fix: always calculate child rel field offsets for join predicates

The confusion for me has been the location of the field lookup,
referenced in the
expression->scalar_function->arguments->value->selection->direct_reference->struct_field
Where is the list of columns that pokes in to?
It doesn't explicitly exist -- it is the flattened list of all columns
from the
left and the right tables.
We were correctly calculating the relative_offset -- the offset within the
left- or right-table -- but our base_offset was wrong.  Why?
Because in some situations, we don't have the child_rel_field_offsets
to pass to the translate call for the join predicates and they need
to be there.
So we check if that has been calculated, and if it hasn't, then we
calculate them and pass them in.
Also, I am sure there are edge cases that this doesn't cover, but this is a distinct improvement.

Found an edge case -- if we use named_table.column as a predicate in a nested join, the field offset is wrong.
Not sure that should block this, but I'll work on fixing that

Found an edge case -- if we use named_table.column as a predicate in a nested join, the field offset is wrong. Not sure that should block this, but I'll work on fixing that

Can you make a small issue for it?


About the open time

Hi. When will this project open source. I’m looking forward to it now.

Hi. When will this project open source. I’m looking forward to it now.

plan to open xquic at january, 2021.
we are catching up the new features and working on the interop project.

Thanks for your reply，wait for its coming


update Makefile to work on Mac OS X

Docker for Mac doesn't allow to mount /var symlink (have to use a resolved /private/var/... path) (see /var mounts in Docker for Mac)
sed on Mac doesn't allow blank -i option (see GNU vs BSD sed -i)

mktemp -d is not creating a temporary directory in /var but in /tmp :confused:
still lgtm

@paulfantom on Mac, $TMPDIR is set by default to something like /var/folders/xx/xxxxx/T/, which (I assume) is rotated by OS. So most OS X users will end up with a /var/... path after mktemp.
Now that I think about it, the Makefile could set $TMPDIR explicitly, although I have no idea about the consequences for non-mac environments.


bugfix: fix trackHover hideDelay inheritance from the original action

:tada: This PR is included in version 3.0.0-beta.20 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


⚠ Bofrost.lu has degraded performance

In 2474009, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1886 ms

Resolved: Bofrost.lu performance has improved in dd48aff after 19 minutes.


Fix Debian image version for acceptance tests

Cron runs are failing with Error resolving image name 'debian-cloud/debian-9': Could not find image or family debian-cloud/debian-9
To fix, replace image names with debian-11 to ensure viability of integration tests.

Closing via #870


Mouse Click/Scroll + Key Combinations

I'm working on an application where key combinations along with mouse click/scroll events are used as hotkeys, is there a way to define these type of combinations in angular-hotkeys?

That sounds kind of neat.  Can you give an example?

Sure, the use-case I'm working on is a drawing application where simply scrolling could be configured to zoom and pressing Ctrl while scrolling could, perhaps, adjust the brush size.
However, since making this post, I realize now that this is a limitation of the Mousetrap library. I guess adding mouse events to that would be the first step in gaining support for them here.
Now that I think about it though, implementing that would then raise issues on rather or not support for PointerEvents should be implemented too since it's already supported by IE and is being worked on by Firefox and Chrome as well.


Pages are rendered outside the layout when page transitions are enabled

Environment

Operating System: Linux
Node Version:     v21.1.0
Nuxt Version:     3.8.2
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      app, modules, build, plugins, directus, css, i18n, shadcn, tailwindcss, gsap
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-tf41bf?file=layouts%2Fdefault.vue
Describe the bug
This behavior appeared recently, when navigating from one page to another with page transitions enabled and a layout such as:
  <AppNavbar />
  <slot />
  <AppFooter />

NuxtPage is rendered after AppFooter in the DOM.
Additional context
No response
Logs
No response

When wrapping a div around, it should work fine:
<template>

  <AppNavbar />

    <slot />

  <AppFooter />

</template>

Hey :wave: https://nuxt.com/docs/guide/directory-structure/layouts layouts must have a single root element

This is indeed an oversight. I forgot that I had removed the div enclosing the layer content when editing, and as it worked without the transitions, I thought that was the cause. I obviously needed some sleep, thanks for the fix.

@huang-julien

Hey 👋 https://nuxt.com/docs/guide/directory-structure/layouts layouts must have a single root element

After checking the original project, the layout-wrapping div was indeed present, it was an oversight in the reproduction.
@manniL

When wrapping a div around, it should work fine. Not sure if this is a bug or a requirement though 🤔

Wrapping slot in a div does fix the issue.
This behavior did not occur in previous versions of Nuxt, if it wasn't intended I'll reopen this issue.

@huang-julien

Hey 👋 https://nuxt.com/docs/guide/directory-structure/layouts layouts must have a single root element

After checking the original project, the layout-wrapping div was indeed present, it was an oversight in the reproduction.
@manniL

When wrapping a div around, it should work fine. Not sure if this is a bug or a requirement though 🤔

Wrapping slot in a div does fix the issue. This behavior did not occur in previous versions of Nuxt, if it wasn't intended I'll reopen this issue.

@e-tho I've got the exact same issue since running yarn install again this morning, this worked fine before.

Nuxt layouts should only have one root element with transitions, there should be a console warning about that, do you have it ?

yep 👍🏽

Nuxt layouts should only have one root element with transitions, there should be a console warning about that, do you have it ?

@huang-julien But even with a wrapping div around everything, it is not enough. A div around the <slot /> is needed too (see repro + my fixed option. This is different from what the docs describe, right?

Indeed sorry ! :eyes: i'll take a look, seems like something is happening with vnodes

@huang-julien Strange, for me it also work with the nightly build in the StackBlitz 🤔

Nuxt version where issue show up:

"nuxt": "^3.8.2",

Issue resolved when is used
 wrap for <slot/>

I got this error in nuxt 3.7.3.
As mentioned before, changing mode from out - in to in -out fixes the issue.
And my layout have only one parent element.

Hello,
I encountered this bug for the first time today after upgrading to 3.9.
The exact same project with the exact same code did not had this bug before upgrading.
Now my page content is placed after my footer, completely ignoring the  placement.
I do have a single div element as root of my layout.

This behavior has been introduced in Vue 3.3.10

Let's track in https://github.com/nuxt/nuxt/issues/24632#issuecomment-1850842639

@manniL I just happened to run into this issue in Nuxt 3.9.1. It looks as if the Vue 3.4.6 update fixed the original attached Stackblitz example, but I ran into more issues with reordering on my project. I discovered that if you change to a page using a different layout structure, then transition back, the reordering layout bug comes back. Here is an example updated Stackblitz using the latest Nuxt 3.9.1 and Vue 3.4.6:
https://stackblitz.com/edit/github-tf41bf-kqwznh?file=layouts%2Fdefault.vue
I introduced a new layout called "blank" and a third page using the blank layout. Navigating between home page and second page do not break no matter how many times you toggle between the two until you navigate to "third page" with the different layout.
Steps to reproduce:

Navigate to "third page"
Navigate home
Navigate to "second page"
Notice that the second page appears below the footer.

Unfortunately it looks like this causes the original reordering bug to come back just as before https://github.com/vuejs/core/issues/9996 was marked fixed with https://github.com/vuejs/core/commit/a3fbf2132b0cd3655e969e290548c8fabc08fd33
Thanks for all the help getting to the bottom of this bug! Let me know if there are any other details I can provide to help.

@volkipp Thanks for reporting ☺
best would be to reproduce as I did in https://github.com/vuejs/core/issues/9996 and create a new issue there!

@manniL I'd be happy to help out, though it seems my knowledge of how the inner workings of Nuxt layouts are lacking. If you have any advice on how to get this bug resolved or flagged for people with a little better working knowledge than me, it would be much appreciated.
This was my (failed) attempt at reproducing the problem in the Vue SFC Playground in case you have any ideas on how to recreate my Stackblitz link:
https://play.vuejs.org/#eNqNVE1v2zAM/SuCL06AxM6WYQcvabsOBbZhWIe2t3kYVJtJ1MqSIclOiyL/fZTk+CNJh55sUnyP5COll+BzWUZ1BUESLHSmWGmIBlOVZ6lgRSmVIS9EbyjncnsDqwnZkB1ZKVmQEEHhp1SkIpNCG3ItgCzJaEyWZ2QzCnNWhxPEZpxqnZDQgDYh2U1IKAWE4z3qbivfhjJbaVF73A/6LCvT5PxrIZpLo8nOMaWCnGLjDuT4ftsQF7R5b2NsCs9JvgLNQYXjiQ9xvFEOK1pxQ86HNhaOvKGN/DNGMfrFNa0dFdcVdlAX1vCGZD6YHOhRM9hitm5SI9SmVbnBDM5bBduojLPssZ3Gi23K0kY15ZXVuW8sl27g526Aif1PxW5A1Kg5oPN1tIRDEym7qZ73REw6v0uyiP2i4oqiYaAoOTWAFiELVPbsTpaL2P44z22lSxDan6OdSVxrAcKQhOllGvgi0qA5xwijqNDMMCmIoAVgTEnXkAakkLm1MHzKBNpJXilq49A5n836HAdZT2a2eiJL3KHiI9gi7qrpOVuqfVdDpJPhUhoji54S9xU6BGE55jZyveZwaWwbF25e6HRf7MIHLmL/fQ3sh3KKwp8gUbN3R3zYVTc1NLV55vY3skJPsS1QU5oZVgNeQu/kQGtonH6ZOmESgltNZtEHjVcQF2RIZF+rAxojPYUsacbMc0JmCCRkxTgCEnLPKzV6p6CwV9ovXFNgMAn8qzgtaBk9aCnw3XRUaXOg0yDx5NaHb6S102BjTKmTOM5ygbAcOKtVJMDEoiziCwyLVSUMK2Cay+JiHn2IPuLgtOm7I9DF9F7JrQaFJGnQvFAuTYzOGrtVIPD1AvXWtAewfuqDo6P0Njuqs0NRjMabv2LrA0nsmjIO6rq0YxpK4x6i785nVGUH7f3ZBrLHE/4H/eR7+qXAVdbr31C1Blw4e3x1+xOe8L89xFtb8WYMrxzegJa8sjX6sMtK5Fh2L85V+81NmIn1nb56Mnjb9k3ZQp0aLt7N48t/Wu/KnUfzVsXdPzdRhKg=

// main.scss
.page-enter-active,
.page-leave-active {
  position: absolute;
  top: 20px;
  transition: all 0.4s;
}

.page-enter-from,
.page-leave-to {
  filter: blur(1rem);
  opacity: 0;
}

I have added position: absolute; top: 20px to the transition class and then set position: relative on the parent element. This way, when the page changes, it automatically positions itself at the top 20px of the parent. I know this is a workaround solution, but it’s the only solution I have.


feat: Rename service/pkgs from "buffer" to "stream

Jira: https://keboola.atlassian.net/browse/PSGO-288
Changes:

Renamed service/directories/packages from buffer to stream.

:thinking: ... so many deleted lines :question:

Historically, the repo contained a generated client for the Buffer service, which was not used, and is not generated anymore.

(no change here)
https://github.com/keboola/keboola-as-code/blob/71d3aaab7d07af7145fb15dca5ca517b615108a8/scripts/generate-api.sh#L37-L42

that's nice to look at


emails: Add realm name to footer of missed message emails.

Missed message emails for mentions come from streams and possibly orgs you
don't normally get missed message emails for, so they can be hard to place.

Merged, thanks @rishig!


Space and tabs being displayed as "f"s

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

VS Code Version: 1.92.0 (Universal)
OS Version: macOS 11.4

Steps to Reproduce:
Open a file in VSCode.
Type any text including spaces.
Notice that typing space results in an "f" character instead of a space.

Expected Result:
Typed characters should appear as expected, with spaces being inserted when the spacebar is pressed.
Actual Result:
Typing the spacebar inserts an "f" character instead of a space.
Additional Information:
I have tried disabling all extensions and the issue persists. Here is a screenshot of the issue:

If I open a new document and type space, it gives me a bunch of "f"s instead as well; tabs are shown as 4 "f"s:

Are you using custom font for editor? Is this problem reproducible if you reserve font family setting?

related? https://www.reddit.com/r/vscode/comments/1ehwtih/can_anybody_tell_me_what_has_happened_to_my/
if you copy paste the 'space' into https://apps.timwhitlock.info/unicode/inspect does it say its a 'normal' space character?

@IllusionMH @RedCMD
I checked again last week, the issue is still there. However, I just checked again today (without doing anything else), seems like the issue is gone now.
Closing this for now. Thank you for checking!


Cannot escape pattern in curly braces with single quotes

Hello, thank you for this package.
Could you please check if this is a bug.
I am trying to escape a message pattern argument using single quotes. The argument is defined as index in curly braces.
The problem is I have no luck to obtain the message that contains the unchanged pattern.
Short code:
...
`Globalize.loadMessages({
en: {
escaped: "Escaped '{0}'"
}
});
Globalize.locale( "en" );
var escaped = Globalize.messageFormatter( "escaped" );
console.log( escaped() ); // here "Escaped {0}" is expected, but got "Cannot read property '0' of undefined"
`
...
Output with error:
return function(d) { return "Escaped '" + d["0"] + "'"; }
^
TypeError: Cannot read property '0' of undefined
at eval (eval at MessageFormat.compile (D:\skre\projects\JavaScript\Globalize\EscapeTest\node_modules\globalize\dist\globalize\message.js:1820:13), :3:44)
Thank you.

We should update Globalize to use a newer messageformat version.


fix: maximize toString coverage

Code coverage for toString should now be 100%
npm run test ./test/toString.test.js -- --coverage

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.9%) to 88.889%

Totals

Change from base Build<PHONE_NUMBER>:
0.9%

Covered Lines:
43

Relevant Lines:
45

💛  - Coveralls


Updates to fix bugs

This is the current version of stashcp and downloading_timeout.sh I have been using locally that has fixed many of the original errors for me.
downloading_timeout.sh now kills xrdcp properly in the case of a timeout, keeps its exit code whether it is killed or aborts itself, and reports it to ES.
stashcp has variables added to its ES index, including checkpoints of where stashcp aborted if it did, and why. It also uses a newer version of xrootd.

I would prefer to keep the download_timeout.sh script to manage to the timeouts.

Sorry about that - didn't meant to push that last change...

You will probably have to test to see if the watchdog script is still running rather than just trying to kill it.  Or... send the stderr of the kill command to /dev/null.

If you think these latest commits are OK, Ilija was wondering if we could merge and publish the changes in a new stashcp 3.2 version.

Have you tested all of these changes?

I've run 1,000 jobs using these scripts through condor, looked at the results in Kibana on the index "stashcp-2016.7", and they look good.

Yes, but did the files successfully transfer?  If you did a md5sum of the files after the transfer, are they correct?
-Derek

On Jul 6, 2016, at 4:20 PM, Tony Aburaad<EMAIL_ADDRESS>wrote:
I've run 1,000 jobs using these scripts through condor, looked at the results in Kibana on the index "stashcp-2016.7", and they look good.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm going to do another submit of 1,000 jobs checking the transferred file using md5sum and let you know.

Ok, 1,000/1,000 files transferred are correct (they all have the same md5 hash).


support encode for datetime and bytes

depends on release of: https://github.com/Azure/cadl-ranch/pull/355
currently, only query and header could accept datetime and bytes format, need to discuss how to support model serialization for different format of datetime and bytes.
resolve: https://github.com/Azure/autorest.python/issues/1970
also resolve: https://github.com/Azure/autorest.python/issues/1996

Changes of version tolerant model could be found in this PR.

@iscai-msft could you help to review this PR?


Add new tutorial for CodeSpaces in Dev Hub

Update:
https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/overview
Add to:
https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/get-
started?tabs=baremetal&pivots=programming-language-nodejs

Completed


CHANGES.md: document BLAKE2b's "size"-setting support

Per https://github.com/openssl/openssl/pull/22444#discussion_r1377955906
Checklist

[x] documentation is added or updated

Thank you @nabijaczleweli

This pull request is ready to merge

Merged to master and 3.2. Thank you.


Crashes on invalid multipart data

dicer, which is used by busboy, emits an error event on invalid end of multipart data. the dicer error is re-emmitted as a busboy error. As the busboy error event isn't listened to the EventEmitter throws this error causing server shutdown.
It looks like the finish event is also sent, so beware of double callbacks.

Fixed by #5


Feature/vcs manager styling improvements

Adds Icons to the VCS pane and replaces statusbar icons with react octicons

👍 had to reign myself in not to put icons everywhere 😆


Unregistered returned with a valid token

I just found that some of my users stopped receiving push notification recently. Checked the log and found that Apple returned "Unregistered" with a timestamp.
I've verified the token using the old protocol (which I used "notnoop" java library) with the same cert and token, the device successfully received the push message.
The strange thing is not all my users failed, just some of them.
The only clue I got is those users which failed to receive the push message, are all using iOS 10.0.x.
Anyone have idea on what's going on? Is it pushy's issue or Apple's issue?
Thanks a lot!

Ios10 can receive.our project is used pushy,it's work very well.Would you sure the 'TOPIC' is right?And use pushy,you need your certificate is Apple based on http2 certificate.

most of the users can receive the push, only a few of them have this problem, so I don't think it's the problem with certificate or topic.

Okay,That I don't know what problem,You can see such as the author to reply you.

This does sound like an upstream issue to me. By all appearances, we are (a) sending the notification to Apple's servers correctly and (b) receiving/processing their reply. Granted, the reply isn't what we'd expect, but that's beyond our control. I'd say it's muuuuuuuch more likely that there's some difference in the way Apple is implementing the two different APNs protocols than it is that the specific libraries are doing something differently.
My strong recommendation would be to file a bug report with Apple. You might also mention it on the push notification forums, though the latter doesn't seem to be the most effective route to getting problems addressed in an official capacity.

ok, I agree it should be upstream problem. Close this issue.

did someone opened a but report with Apple? this happens to me too.


hi/lo id generation

Our table and sequence id generators don't support the hi/lo optimization.

I think this is the issue we should work on next. (It's a potential performance bottleneck.)

This is now done in #318.


Spam on the Wiki pages for this github project

It looks like the same guy who created an issue spam, at about the same time.

Thanks for letting us know!  I expect to delete the wiki pages soon, but I'll report it first to LF to see if there is anything else that should be done.
I will leave this issue open until it's resolved.

I went ahead and deleted the pages. Thanks for letting us know.

You can also disable wikis: https://help.github.com/articles/disabling-wikis/

@bkeepers: True, we could disable the wiki.  However, we've toyed with the idea of adding wiki pages (e.g., perhaps to write suggestions on how to implement some criteria if it's not obvious).
We haven't (so far) had a serious spam problem; I'd like to keep the wiki area in case we suddenly decide to start using it.


iana-etc: 2.30 -> 20170313

Motivation for this change

Move away from an outdated package and fetch content directly from IANA
Align the attribute name with the package name for clarity

Some time ago I push a quick PR to fix the source of the old iana-etc package : see #23167
When looking at it I realised NixOS relied on an outdated package that does not seem maintained anymore. The last version is from 2008-MAR-05.
Present /etc/services and /etc/protocols content is just as old as this package and probably incomplete/outdated.
This PR propose to fetch the information directly from IANA.
Truth be told, this is heavily inspired by what Arch does.
As an added bonus, this PR rename the attribute name to iana-etc instead of iana_etc. For clarity it seems proper to align attr and pkg name.
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Feedbacks and opinions are welcome before merging.
The files produced by this are also much less chatty.
Excerpt from protocols :
# See also protocols(5) and IANA official page :
# https://www.iana.org/assignments/protocol-numbers
#
# Last updated: 2016-06-22

hopopt             0 HOPOPT
icmp               1 ICMP
igmp               2 IGMP
ggp                3 GGP
ipv4               4 IPv4
st                 5 ST
tcp                6 TCP
cbt                7 CBT
egp                8 EGP
igp                9 IGP

Excerpt from services :
# See also services(5) and IANA official page :
# https://www.iana.org/assignments/service-names-port-numbers
#
# Last updated: 2017-03-03

tcpmux               1/tcp
tcpmux               1/udp
compressnet          2/tcp
compressnet          2/udp
compressnet          3/tcp
compressnet          3/udp
rje                  5/tcp
rje                  5/udp
echo                 7/tcp
echo                 7/udp
discard              9/tcp
discard              9/udp
discard              9/sctp
discard              9/dccp
systat              11/tcp
systat              11/udp
daytime             13/tcp
daytime             13/udp
qotd                17/tcp

The "last updated" dates are the ones from the source XML from IANA.

For comparison here is the beginning of the present protocols :
# See also: protocols(5), http://www.sethwklein.net/projects/iana-etc/
#
# (last updated 2008-02-27)
#
# Registries included below:
# - Assigned Internet Protocol Numbers
#
# Registry Name: Assigned Internet Protocol Numbers
# Reference: [RFC5237]
# Registration Procedures: IESG Approval or Standards Action
# Note: In the Internet Protocol version 4 (IPv4) [RFC791] there is a field
# called "Protocol" to identify the next level protocol.  This is an 8
# bit field.  In Internet Protocol version 6 (IPv6) [RFC1883], this field
# is called the "Next Header" field.
#
# Registry:
# Decimal    Keyword     Protocol                                 References
# ---------  ----------  ---------------------------------------  ----------
# protocol   num aliases      # comments
hopopt         0 HOPOPT       # IPv6 Hop-by-Hop Option                   [RFC1883]
icmp           1 ICMP         # Internet Control Message                 [RFC792]
igmp           2 IGMP         # Internet Group Management                [RFC1112]
ggp            3 GGP          # Gateway-to-Gateway                       [RFC823]
ip             4 IP           # IP in IP (encapsulation)                 [RFC2003]
st             5 ST           # Stream                                   [RFC1190][RFC1819]
tcp            6 TCP          # Transmission Control                     [RFC793]
cbt            7 CBT          # CBT                                      [Ballardie]
egp            8 EGP          # Exterior Gateway Protocol                [RFC888][DLM1]
igp            9 IGP          # any private interior gateway             [IANA]
#                        (used by Cisco for their IGRP)
bbn-rcc-mon   10 BBN-RCC-MON  # BBN RCC Monitoring                       [SGC]
nvp-ii        11 NVP-II       # Network Voice Protocol                   [RFC741,SC3]
pup           12 PUP          # PUP                                      [PUP,XEROX]
argus         13 ARGUS        # ARGUS                                    [RWS4]
emcon         14 EMCON        # EMCON                                    [BN7]

And the present services :
# See also: services(5), http://www.sethwklein.net/projects/iana-etc/
#
# (last updated 2008-02-29)
#
# The port numbers are divided into three ranges: the Well Known Ports,
# the Registered Ports, and the Dynamic and/or Private Ports.
#
# The Well Known Ports are those from 0 through 1023.
#
# DCCP Well Known ports SHOULD NOT be used without IANA registration.
# The registration procedure is defined in [RFC4340], Section 19.9.
#
# The Registered Ports are those from 1024 through 49151
#
# DCCP Registered ports SHOULD NOT be used without IANA registration.
# The registration procedure is defined in [RFC4340], Section 19.9.
#
# The Dynamic and/or Private Ports are those from 49152 through 65535
#
# A value of 0 in the port numbers registry below indicates that no port
# has been allocated.
#
# ************************************************************************
# * PLEASE NOTE THE FOLLOWING:                                           *
# *                                                                      *
# * IESG STATEMENT TO THE IANA                                           *
# *    THE IESG BELIEVES THAT IANA MAY ALLOCATE AN ADDITIONAL PORT IN    *
# *    THE 'USER PORT' RANGE TO PROTOCOLS WHOSE CURRENT PORT ALLOCATION  *
# *    REQUIRES ACCESS TO A PRIVILEGED PORT. THIS ALLOCATION SHOULD NOT  *
# *    BE AUTOMATIC, BUT MAY OCCUR UPON APPLICATION BY AN INTERESTED     *
# *    PARTY WHOSE APPLICATION WOULD OTHERWISE FIT IANA'S POLICIES.      *
# *                                                                      *
# * 1. UNASSIGNED PORT NUMBERS SHOULD NOT BE USED.  THE IANA WILL ASSIGN *
# * THE NUMBER FOR THE PORT AFTER YOUR APPLICATION HAS BEEN APPROVED.    *
# *                                                                      *
# * 2.  FIREWALL AND SYSTEM ADMINISTRATORS SHOULD      *
# * CHOOSE HOW TO CONFIGURE THEIR SYSTEMS BASED ON THEIR KNOWLEDGE OF    *
# * THE TRAFFIC IN QUESTION, NOT WHETHER THERE IS A PORT NUMBER          *
# * REGISTERED OR NOT.                                                   *
# ************************************************************************
#
#
# WELL KNOWN PORT NUMBERS
#
# The Well Known Ports are assigned by the IANA and on most systems can
# only be used by system (or root) processes or by programs executed by
# privileged users.
#
# Ports are used in the TCP [RFC793] to name the ends of logical
# connections which carry long term conversations.  For the purpose of
# providing services to unknown callers, a service contact port is
# defined.  This list specifies the port used by the server process as
# its contact port.  The contact port is sometimes called the
# "well-known port".
#
# To the extent possible, these same port assignments are used with the
# UDP [RFC768].
#
# The range for assigned ports managed by the IANA is 0-1023.
#
# Port Assignments:
#
# Keyword         Decimal    Description                     References
# -------         -------    -----------                     ----------
#                 0/tcp    Reserved
#                 0/udp    Reserved
#                          Jon Postel <postel&isi.edu>
# spr-itunes        0/tcp    Shirt Pocket netTunes
# spl-itunes        0/tcp    Shirt Pocket launchTunes
#                          David Nanian <dnanian&shirt-pocket.com> 28 September 2007
tcpmux            1/tcp    # TCP Port Service Multiplexer
tcpmux            1/udp    # TCP Port Service Multiplexer
#                          Mark Lottor <MKL&nisc.sri.com>
compressnet       2/tcp    # Management Utility
compressnet       2/udp    # Management Utility
compressnet       3/tcp    # Compression Process
compressnet       3/udp    # Compression Process
#                          Bernie Volz <volz&cisco.com>
#                 4/tcp    Unassigned
#                 4/udp    Unassigned
rje               5/tcp    # Remote Job Entry
rje               5/udp    # Remote Job Entry
#                          Jon Postel <postel&isi.edu>
#                 6/tcp    Unassigned
#                 6/udp    Unassigned
echo              7/tcp    # Echo
echo              7/udp    # Echo
#                          Jon Postel <postel&isi.edu>
#                 8/tcp    Unassigned
#                 8/udp    Unassigned
discard           9/tcp    # Discard
discard           9/udp    # Discard
#                          Jon Postel <postel&isi.edu>
discard           9/sctp   # Discard
#                          IETF TSVWG
#                          Randall Stewart <rrs&cisco.com>
#                          [RFC4960]
discard           9/dccp   # Discard SC:DISC
#                          IETF dccp WG, Eddie Kohler <kohler&cs.ucla.edu>, [RFC4340]
#                10/tcp    Unassigned
#                10/udp    Unassigned
systat           11/tcp    # Active Users
systat           11/udp    # Active Users
#                          Jon Postel <postel&isi.edu>
#                12/tcp    Unassigned
#                12/udp    Unassigned
daytime          13/tcp    # Daytime (RFC 867)
daytime          13/udp    # Daytime (RFC 867)
#                          Jon Postel <postel&isi.edu>
#                14/tcp    Unassigned
#                14/udp    Unassigned
#                15/tcp    Unassigned [was netstat]
#                15/udp    Unassigned
#                16/tcp    Unassigned
#                16/udp    Unassigned
qotd             17/tcp    # Quote of the Day

I agree with @LnL7 about the alias, but LGTM.

$ wc -l /etc/protocols && wc -l /nix/store/23x5l7i5rfhgkkfkbylq0khnz5xmnlxs-iana-etc-20170307/etc/protocols
522 /etc/protocols
139 /nix/store/23x5l7i5rfhgkkfkbylq0khnz5xmnlxs-iana-etc-20170307/etc/protocols

and
$ wc -l /etc/services && wc -l /nix/store/23x5l7i5rfhgkkfkbylq0khnz5xmnlxs-iana-etc-20170307/etc/services
15551 /etc/services
11358 /nix/store/23x5l7i5rfhgkkfkbylq0khnz5xmnlxs-iana-etc-20170307/etc/services

@LnL7 @grahamc yes indeed I will add an alias for iana_etc

Alias iana_etc now points to iana-etc

Remove the unnecessary buildInputs

Do we have more concerns on this ?

@c0bw3b I created a github project, which automatically check for new IANA updates and create protocol files using python: https://github.com/Mic92/iana-etc

So IANA has edited service-names-port-numbers.xml many times in the last few days, proving my initial assumption to be false.
I've looked at what @Mic92 proposed and while it is a good way to keep track of IANA revisions I feel this is somewhat overkill to rely on 200 python LOC and a TravisCI job for this. I'm inclined toward following KISS principles. Plus the XML parsing is done in a jiffy with awk scripts.
Moreover, we don't really need to keep a close track of what IANA changed. On many occasions, the update concerns people and organizations info, not the actual services numbers. We only need to have XML sources that are recent enough.
I just pushed a refactor where I copy the two XML here on the GH repo newt to default.nix and they are parsed directly with no fetching involved. This seems the most sensible way to handle this.

@c0bw3b if you download the tarballs, there is no python included just the processed files. I used python because xml cannot be parsed reliable with awk and it also seems that it skipped some lines:
$ wc -l /nix/store/b52ycacfij4y5grcda5vqzz09g60g8m1-iana-etc-20170307/etc/services
11358 /nix/store/b52ycacfij4y5grcda5vqzz09g60g8m1-iana-etc-20170307/etc/services

$ wc -l services
11546 services

Mhm adding service-names-port-numbers-20170317.xml directly to this repo adds 3.5 MB of data to nixpkgs. Usually we try to avoid that.

if you download the tarballs, there is no python included just the processed files.

And 200 LOC in python to redo what can be done in 2x15 lines of awk is just making things unnecessarily complicated. + relying on a TravisCI job + python tends to break over time (version change, libs change, ...) + relying on a personal repo that can disappear or move.

I used python because xml cannot be parsed reliable with awk

Yes it can. This is an empty claim. The source can be XML or plain text it would just change the script.
Arch also disagree with you.
Last but not least : the old package we were using is actually just another awk parsing but done on the IANA files in plain text.

and it also seems that it skipped some lines:

A quick check reveals you have duplicated entries in your processed services file :
[...]
subntbcst-tftp   247/tcp    # SUBNTBCST_TFTP
subntbcst_tftp   247/tcp    # SUBNTBCST_TFTP
subntbcst-tftp   247/udp    # SUBNTBCST_TFTP
subntbcst_tftp   247/udp    # SUBNTBCST_TFTP
[...]
redstorm-join    2346/tcp   # Game Connection Port
redstorm_join    2346/tcp   # Game Connection Port
redstorm-join    2346/udp   # Game Connection Port
redstorm_join    2346/udp   # Game Connection Port
redstorm-find    2347/tcp   # Game Announcement and Location
redstorm_find    2347/tcp   # Game Announcement and Location
redstorm-find    2347/udp   # Game Announcement and Location
redstorm_find    2347/udp   # Game Announcement and Location
redstorm-info    2348/tcp   # Information to query for game status
redstorm_info    2348/tcp   # Information to query for game status
redstorm-info    2348/udp   # Information to query for game status
redstorm_info    2348/udp   # Information to query for game status
redstorm-diag    2349/tcp   # Diagnostics Port
redstorm_diag    2349/tcp   # Diagnostics Port
redstorm-diag    2349/udp   # Diagnostics Port
redstorm_diag    2349/udp   # Diagnostics Port
[...]
mapper-nodemgr   3984/tcp   # MAPPER network node manager
mapper-nodemgr   3984/udp   # MAPPER network node manager
mapper-mapethd   3985/tcp   # MAPPER TCP/IP server
mapper-mapethd   3985/udp   # MAPPER TCP/IP server
mapper-ws-ethd   3986/tcp   # MAPPER workstation server
mapper-ws_ethd   3986/tcp   # MAPPER workstation server
mapper-ws-ethd   3986/udp   # MAPPER workstation server
mapper-ws_ethd   3986/udp   # MAPPER workstation server

Also proving the point that XML parsing done in Python is not more reliable just because it's Python.
We could also do a proposer XSLT transformation to build the text files but it would be utterly pointless.

This has been reworked one last time to :

fetch latest content directly from IANA
use curl instead of fetchurl because it is not the right tool for the job : in this situation we want to fetch content from a trusted third-party over a secure channel rather than being able to check a hash

With this Nix(OS) won't rely on a third-party for the generation of system files (like the old iana-etc package).
Also : this needs virtually no maintenance. Once it runs on Hydra, it will continuously produce etc files from the most up-to-date information available at build time.

Could this infrastructure be used to generate the /etc/protocols and /etc/services files which we just track directly? I know that's not the usual practice but

they're rather tiny, around the size of many patches we keep in-tree
even if IANA updates somewhat frequently, we probably don't need to update it more than once a year or on request (look at the dates for the release tags for debian's netbase)

@dtzWill it could have been a solution also yes.
FWIW Arch is having the same questions in FS#53221
Debian's netbase does not track IANA additions. They handpick and add only ports/services they deem important. So it contains much fewer entries.

Okay SGTM, thanks for the reponse (here and on the other PR)!


Error encountered when calculating coastal change rates in Coastal Erosion Real World Example

Hello,
I encountered an issue while working on the Coastal Erosion Real World Example in the Digital Earth Australia Sandbox. After doing all the recommended steps, I attempted to calculate the rates of coastal change, similar to the same example provided for Africa. However, when running the annual_movements function, I consistently encountered the error message "TypeError: No matching signature match," despite correctly setting the input parameter data types.
To resolve this problem, it was necessary to change the data type of the "MNDWI" values in the "landsat_summaries" dataset from float32 to float64:
landsat_summaries["MNDWI"] = landsat_summaries["MNDWI"].astype("float64")

Thank you

Thanks so much for this @mariarodriguezn! This turns out to be a bug with scipy version 1.10: https://github.com/scipy/scipy/issues/17718
We'll update the package on the DEA Sandbox and hopefully that will resolve it. For now, you can temporarily work around the issue by upgrading scipy before running your analysis:
!pip install scipy==1.10.1

Hey @mariarodriguezn, we've now updated scipy in the DEA Sandbox, so this should work fine now.
Closing this issue for now, but let us know if you still have problems!


Core: Updating all packages within the project to their most up to date versions

Detailed:
The modules in use on this project were seriously out of date, and
represented a potential security risk on websites currently using it.
I have updated all modules to their most modern versions possible,
and fixed tests within the application, alongside the build process
to ensure security is maintained.
Signed-off-by: Andrew Lowther<EMAIL_ADDRESS>

=== npm audit security report ===

found 0 vulnerabilities
 in 10808 scanned packages

@leozdgao May I have a review on this please?


server not implemented

My webcam is  Logitech C270 however when i node server.js it only display
WebSocket server listening on port 8084
HTTP server listening on port 8080
Listening for video stream on port 8082
According to your documentation, there is a missing line of
"Stream Connected: <IP_ADDRESS>:52995 size: 320x240"
Also, when i run my web server of http://<IP_ADDRESS>:8084 , only a white screen with words "not implemented" is displayed.
Can you suggest where did i go wrong?
Cheers!

Hi, a couple things:

Can you open the developer console in your web browser? Are there any messages shown?
Can you double-check that wsUrl has been updated web/client/index.html per the instructions?

The developer console seems to be blank.
My wsUrl is as followed:
var wsUrl = 'ws://<IP_ADDRESS>.local:8084/';
However when i navigate to my server, I am using http://<IP_ADDRESS>.local:8084/
Do i have to change my wsUrl to http:// instead ?

Can you try ws://<IP_ADDRESS>:8084 instead? You typically need to write local after the network name of your Edison, but not with the IP address. Let me know if that resolves your problem!

Hi, I tried replacing 8084 with 8080 and I am able to run my server with http://<IP_ADDRESS>:8080/
However, now it only shows "Loading"
Any idea where did i went wrong this time?

Can you use 8084 instead of 8080? The WebSocket server is listening on port 8084.

My wsUrl in index.html is currently saved as:
var wsUrl = 'http://<IP_ADDRESS>:8084/';
However i can only run the server using  172.27.152:8080 and not 8084.

Hmm, not sure if I fully understand the issue you're experiencing. Can you explain in more detail what's going on?

My apology for not detailed explanation. I'm new to programming :)
There are a few issues I'm currently facing.
Web server told me it was "not implemented" when i tried with ws://<IP_ADDRESS>:8084 and http://<IP_ADDRESS>:8084 however I'm able to run only with http://<IP_ADDRESS>:8080 with only the "loading" word without any live footage of my webcam which you told me were wrong.
Is there a difference between navigating with ws:// and http://?
For installation of ffmpeg, I only wget http://johnvansickle.com/ffmpeg/releases/ffmpeg-release-64bit-static.tar.xz into my bin folder and did not change anything. Did i execute this step correctly?
According to your guide, After node server.js there should be four lines being output, however I'm missing the last line of
"Stream Connected: <IP_ADDRESS>:52995 size: 320x240"
Cheers!

Thanks for providing more details!
Can you try installing ffmpeg with the shell script (bin/install_ffmpeg.sh) I provide? Please see the instructions on installing ffmpeg. The reason why is that I download the 32-bit version of ffmpeg, unpack it, and move it to another directory that the code is expecting. This might actually be the source of the issues you're experiencing.
Also, ws:// is used for the WebSocket server instead of http://as its URI scheme. So, try using ws:// instead of 'http://.

Do you mean i have to vi install_ffmpeg.sh and then replace this line:
FNAME=ffmpeg-release-32bit-static.tar.xz ?
Do i replace it with the 64bit 3.0.1 release version or the 64bit that is built on 20160409 ?
I think this is the issue im facing.

You should be able to run install_ffmpeg.sh without making any modifications. Can you try that?

What do you mean by run "install_ffmpeg.sh".
My apology, I'm a beginner and don't quite understand. What commands do i have to run?
Also, i discover another issue, when i run lsmod I'm able to find my uvc driver however there isnt any light appearing on my Logitech C270 webcam. Is this normal? Am i suppose to see lights on my camera yet if it is already connected ?

Can you try running the commands below? Also, please see the comments above each command.
# If necessary, please change this to wherever edi-cam is located on your Edison
cd ~/edi-cam/bin

# Run install_ffmpeg.sh
./install_ffmpeg.sh

It should be okay if the webcam light isn't appearing. It should turn on when the server runs successfully without errors.

This is the output when i run the command of ./install_ffmpeg.sh
Creating ~/bin directory if it doesn't exist...
Removing old versions of ffmpeg...
Downloading ffmpeg...
--2016-04-11 23:00:09--  http://johnvansickle.com/ffmpeg/releases/ffmpeg-2.4.3-32bit-static.tar.xz
Resolving johnvansickle.com... <IP_ADDRESS>
Connecting to johnvansickle.com|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2016-04-11 23:00:10 ERROR 404: Not Found.
Unpacking...
tar: can't open '/home/root/bin/ffmpeg-2.4.3-32bit-static.tar.xz': No such file or directory
Cleaning up...
rm: can't remove '/home/root/bin/ffmpeg-2.4.3-32bit-static.tar.xz': No such file or directory
mv: can't rename '/home/root/bin/ffmpeg*/': No such file or directory

When running ./install_ffmpeg.sh, did you use the original version of the script? It should run just fine... at least when I tried this morning.
When you open install_ffmpeg.sh, can you double-check that FNAME is the same as my original version, i.e. FNAME=ffmpeg-release-32bit-static.tar.xz?

I think i accidentally edited it before, but now  that i've change back to the original version im able to unpack it.
Now, that I'm done unpacking, does this mean I'm ready to view my webcam?

Okay, great! Can you please try re-running the web server? Hopefully, it'll work now.

It's working perfectly now! Thank you so much Esther :)
Also, if i want to adjust the resolution i would just need to edit the following numbers right?

Glad it's working for you now!
Please see https://github.com/drejkim/edi-cam/issues/6 if you want to adjust the resolution


Fixed the link to AST Types

Hi – Your link to ast-types was broken (you had benjamin whereas the user is benjamn without the i). I swapped in the correct link – wasn't sure whether to do this as an Issue or a PR.
Cheers,
joe

Cool thanks @JoeArizona!


embedded jetty is accepting HTTP TRACE method

How  to  disable it ?

最近同样遇到了一样的问题，
我的解决方案是修改源代码（因为配置jetty host是无效的）使其监听强制为<IP_ADDRESS>，这样子我用nginx 反向代理一下   软件扫描 就无法扫描出该漏洞。

I am not aware of a reason that AZ would need to use TRACE method. It seems reasonable to have it disabled if so.
What are your concerns with it enabled?


Language Understanding documentation

Describe the bug
When searching for language understanding the only option is cognitive services. I feel there needs to be an added step to the documentation.
To Reproduce
Expected behavior
Screenshots
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context

I need more information. When I do a search for "language und" I get the following results:


What happened to the vertical score txt?

What is your question?
in the updates before 1.23 there was 2 vertical HUD: mic'd up and box funkin
so the question is why are they removed?

they were buggy and just caused problems


websockets draft

Here's an initial proposal of what a websockets API might look like.
I'm deliberately sticking with JSON for now - this will lead to an easier websockets implementation (on both client and server side) and it should be easy enough to offer other encodings later on.
The proposal includes an RPC layer which is inspired by JSON-RPC.
Todo:

[ ] note rationale for limiting the number of available methods
[ ] decide whether an initial /sync is necessary, and remove it if not

oh, and I think we're missing the spec for how one should decide when to try to talk WS, and when to give up and talk REST, which from a UX perspective is pretty critical so we don't end up with transports getting wedged on nasty timeouts or whatever because WS is broken on their setup/network/proxy/etc.  E.g. should I start talking both REST & WS simultaneously and then continue on WS if it's available?  Or is there a very quick keepalive thing I can do on WS as an initial sanity check which won't block and slow everything down if WS is awol?
Also, do we not need a WS keepalive ping/pong style mechanism in general?

@ara4n: the quick "does my websocket work" is "do I get the '101 Switching Protocols' response back". Basically the idea is that you either get that back, in which case you carry on with websockets - or you get some other response, in which case you fall back to REST. It's hard to envisage a situation in which the upgrade request or response gets swallowed such that things block.
I'll add some notes to make the fallback to REST explicit.
WS has a built-in ping/pong mechanism; however, the browser APIs don't expose it. So yes, we may need to spec one at the app level too, depending on what the browsers do by default.

How is presence intended to work? When is a client "active" when using this API?

About presence: I guess I'm assuming that the websocket being open will mark the user as present. But I haven't looked at presence much: is there detail I'm missing?


docs: distributed execution is invalid

This probably beyond just the docs, but the docs are what brought me here.
In the section on Distributed Execution, it suggests running the "client" (really the runner, I guess?) as silverback run "example:app".
This would run the entire app, runner and worker. Then suggests running silverback worker. I don't think this is really what's intended.
I think we either need an idler app (similar to platform runner) or maybe a command that executes without the worker, if possible.

That was somewhat my intent behind making the runner "stateless" (e.g. not dependent on having any particular app)
What we could do actually is make the app "optional" in silverback run e.g. if you don't add a bot there it defaults to an "idle app" for the runner to run with and collect tasks from the worker (but maybe also display something that says like "please run your app w/ silverback worker" if you use that configuration)

That was somewhat my intent behind making the runner "stateless" (e.g. not dependent on having any particular app)
What we could do actually is make the app "optional" in silverback run e.g. if you don't add a bot there it defaults to an "idle app" for the runner to run with and collect tasks from the worker (but maybe also display something that says like "please run your app w/ silverback worker" if you use that configuration)

Still not really sure what you mean by stateless. But generally the suggested interface sounds okay. Though the default InMemoryBroker won't play nice with this behavior. And forcing a redis configuration equally sounds bogus.
So if we're going to lean into the distributed running, we should come up with something easy for local dev.
Though I'm not sure distributed use cases are ever going to be common.

Still not really sure what you mean by stateless.

Maybe "app-less" or "app-agnostic" is a better way to say it

Though I'm not sure distributed use cases are ever going to be common.

I agree with this, that for like 80% of users they will be happy if they have an easy way to take a local app they've developed, build it into an image, and upload that to the cluster and have it work the first time they do it. Some people are always going to have problems though, and they're gonna need a way to debug why it's not working properly both in a container (mostly this) and in the cluster environment. We can pull their images and debug ourselves locally at first, but that is definitely not going to scale well, so we should try to give users a few tools for debugging purposes.

Some people are always going to have problems though, and they're gonna need a way to debug why it's not working properly both in a container (mostly this) and in the cluster environment. We can pull their images and debug ourselves locally at first, but that is definitely not going to scale well, so we should try to give users a few tools for debugging purposes.

This should absolutely not being the concern of the user. If their bot runs locally but does not on the platform, that's a bug in Silverback. There's no case where I would want a regular user to have to have intimate knowledge of how the platform works to debug their bot.
Though I'm not really sure this issue has anything to do with the platform. More on the Silverback CLI and how we expose the distributed configuration.

Some people are always going to have problems though, and they're gonna need a way to debug why it's not working properly both in a container (mostly this) and in the cluster environment. We can pull their images and debug ourselves locally at first, but that is definitely not going to scale well, so we should try to give users a few tools for debugging purposes.

This should absolutely not being the concern of the user. If their bot runs locally but does not on the platform, that's a bug in Silverback. There's no case where I would want a regular user to have to have intimate knowledge of how the platform works to debug their bot.

We're saying the same thing, I'm just saying we will never get it 100% right, and we need to think of how the user is gonna quickly give us the information they need for us to debug with that doesn't require an hours long debug session in discord.

We're saying the same thing, I'm just saying we will never get it 100% right, and we need to think of how the user is gonna quickly give us the information they need for us to debug with that doesn't require an hours long debug session in discord.

I don't think we're saying the same thing. You suggested we bring the distributed concept to the forefront. I'm saying I think that's probably confusing to users and only useful in edge cases. But you chose your favorite solution.
We just either need to fix the CLI or the docs because right now the suggested way to run distributed silverback is incorrect.

I'm saying I think that's probably confusing to users and only useful in edge cases

We're saying the exact same thing
We don't want this to be the suggested way to do things, but there are corner cases that people will occasionally hit and we need docs and/or CLI command to run so they can get unstuck easily


fix problem with auth by cookie when cross site

Fixes #507
Solution
Under the hood, Angular uses XMLHttpRequest. When the app is configured to be deployed under another domain, setting withCredentials option to true allows the server to set third party cookies.
The app configuration properties which pilot this behavior are authType and sameSite. When authType === 'cookies' && sameSite === false, credentials are enabled.
If authentication still doesn't work for algorea apps with another domain, it means that the user's browser is configured to block third party cookies, s⋅he will have to change to browser configuration.

Close in favor of #522


HDDS-5706. Fix ReplicationManager zero metrics for inflight actions.

What changes were proposed in this pull request?
Fix ReplicationManager zero metrics for inflight actions.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5706
How was this patch tested?
manual test
after change we could get actual numbers instead of all 0.

@ChenSammi PTAL, thanks~


"Didn't get typechecked module" message

From what I understand the cache of typechecked modules is supposed to be "monotonic": once completion works for a module, it never stops working.
But apparently it's not the case. I load a haskell file in neovim and completion works. But after some time it stops working, and when I try to complete something there is the following message in hie.log:
 setTypecheckedModule: Didn't get typechecked module for: "/home/foo/bar/Main.hs"

The message is produced by hie-ghc-mod:
https://github.com/haskell/haskell-ide-engine/blob/4001c3e9fea3ad36ec7eddcb3ddbb5c08b4dbd1e/hie-ghc-mod/Haskell/Ide/GhcModPlugin.hs#L150-L159

I've been looking at this as well.  I have the same messages, but I think its related to Language Client, it seems to correspond to the errors there:
Some arguments are missing, requesting from vim. Keys: ["buftype", "filename", "line"]. Exps: ["&buftype", "s:Expand(\'%:p\')", "line(\'.\') - 1"]
I am thinking the rust wrapper maybe failing to expand those properly and confusing ghc-mod, but I've not had time to look at it further. Perhaps @autozimu has a insight? The completion was working before the new rust based version

No, that’s not an error and that message is totally fine. The message basically says those information are not included in the request, languageclient needs to ask vim to fulfill those info though RPC call.

@autozimu You definitely need to have it at INFO log level so people don't get misleaded


fix: DEV-3693: Explore reviews module show buggs

Hi @yyassi-heartex!
This PR was created in response to a PRs in upstream repo:

https://github.com/heartexlabs/label-studio-frontend/pull/1002

/git merge develop


[Storage] BREAKING CHANGE: az storage blob upload/upload-batch: Fix --overwrite, no longer overwrite by default

Description

Used to overwrite everything by default. In storage-blob-preview extension, we introduced --overwrite to change this default behavior.
Testing Guide

az storage blob upload-batch -d {containername} -s {filedirectory}
#should show error
az storage blob upload-batch -d {containername} -s {filedirectory}
#should succeed
az storage blob upload-batch -d {containername} -s {filedirectory} --overwrite
History Notes

[Storage] BREAKING CHANGE: az storage blob upload/upload-batch: Add --overwrite, by default no longer overwrites

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Storage


Moving from base Routes to addRoutes fails to deploy

When we move a route that was initially defined in the constructor props into the addRoutes method, sst deploy fails. Even though it is the same configuration.
    // Initial config
    const api = new sst.Api(this, 'Api', {
      routes: {
        'GET /': 'src/lambda.handler',
        'GET /test': 'src/lambda.handlerEvent',
      },
    });

    // New config
    const api = new sst.Api(this, 'Api', {
      routes: {
        'GET /': 'src/lambda.handler',
      },
    });

    api.addRoutes(this, {
      'GET /test': 'src/lambda.handlerEvent',
    });

Error message (w/ IDs removed)
my-stack | CREATE_FAILED | AWS::ApiGatewayV2::Route | RouteGETtest... Route with key GET /test already exists for this API (Service: AmazonApiGatewayV2; Status Code: 409; Error Code: ConflictException; Request ID: ...; Proxy: null)

Since it is the same configuration it really should not be an issue. The workaround is currently to:

Remove the endpoint completely
Deploy
Add the endpoint back in with the new config
Deploy

Ideally it would just work as expected.

Hey @justindra, thanks for bringing this up! Unfortunately this is the expected behaviour given how CDK generates the ids (CloudFormation Logical IDs) for the routes.
When defined through the constructor, the Logical ID for the GET /test route looks like ApiRouteGETtestXXXXXXXX. But if added via the addRoutes call, the Logical ID looks like RouteGETtestXXXXXXXX. This is because in the former case, the route is a child of the sst.Api construct, so CDK prefixes its Logical ID with the construct name Api. Whereas in the latter case, the route is a child of the stack directly, hence not prefixed with Api. And when the ID for a resource change, CloudFormation tries to recreate it.
As a side note, the addRoutes() function is mostly used to add routes across stacks (ie. sst.Api created in stackA, and addRoutes called in stackB). If a route (ie. /test) is "moved" from stackA to stackB, CloudFormation would deploy stackA first to remove the route, then deploy stackB to add the route. So for some time during the deployment, the /test route does not exist.
The recommended way to move a route around is actually similar to what you have described:

Create a new route complete, ie. /test2
Deploy
Change the frontend to call /test2
Remove /test
Deploy
Add /test
Deploy
Change the frontend to call /test
Remove /test2
Deploy

I hope this makes sense.

Gotcha. Yea that's a really great explanation for that. Thanks @fwang!


🕵 EC2 instances should use Instance Metadata Service Version 2 (IMDSv2)

Checks if your Amazon Elastic Compute Cloud (Amazon EC2) instance metadata version is configured with Instance Metadata Service Version 2 (IMDSv2). The check passes if HttpTokens is set to required for IMDSv2. The check fails if HttpTokens is set to optional.
Source
AWS Security Hub
Security Hub control ID: EC2.8
Alert Criteria
Red: Critical or High. Security Hub control failed.
Recommended Action
Follow the Security Hub documentation to fix the issue.
Definition of Done
Establish which accounts this applies to and resolve in each

[ ]  Development
[ ]  Pre-production
[ ]  Production

Hey team! Please add your planning poker estimate with ZenHub @ASTRobinson @bagg3rs @kyphutruong @mitchdawson1982 @moontune @mTouhid @wanieldilson


mutableUsers=false and root.hashedPassword is set, yet nixos-install prompts for password:

Describe the bug
From my configuration.nix:
{
    users.users."root".hashedPassword = "redacted";

    security.sudo.wheelNeedsPassword = false;
    users.mutableUsers = false;
}

Yet:
$ nixos-install ...

setting root password...
New password:

For what it's worth, an activation script failed, but that shouldn't matter.
This is on top of eac5ef8aa9c0ddd948b20e83d9d7b37cd0132a81 (current nixos-unstable-small).

try initialHashedPassword

I have a failing activation script and am seeing the same problem.
I saw this:
# Ask the user to set a root password, but only if the passwd command
# exists (i.e. when mutable user accounts are enabled).
if [[ -z $noRootPasswd ]] && [ -t 0 ]; then
    if nixos-enter --root "$mountPoint" -c 'test -e /nix/var/nix/profiles/system/sw/bin/passwd'; then
        set +e
        nixos-enter --root "$mountPoint" -c 'echo "setting root password..." && /nix/var/nix/profiles/system/sw/bin/passwd'

in https://github.com/NixOS/nixpkgs/blob/c7b9a25365b3d90f1d34ddab43e4e218c61e388e/nixos/modules/installer/tools/nixos-install.sh#L200-L205 and wondered if there was a regression in that test. However, I checked channel versions all the back to 09e59ad5791d965d9bfbc51fdc27a687cae2e6b9 -- 17.09 -- and:
[...]
/nix/store/zqrpfxj7vmf5qx8l15q1dm67rir7h8zg-nixos-system-nixos-17.09.git.09e59ad

[grahamc@Petunia:~/projects/github.com/NixOS/nixpkgs]$ test -L result/sw/bin/passwd; echo $?
0

Now I'm wondering if this is still a bug in the script, or a bug with the activation scripts ...

Fixing my activation scripts did not fix it. Hmm...

This is caused by c1a202de051c197675d3ae67dd0d934329309090 somehow.

02:22 <clever> nixos/modules/config/users-groups.nix:      filter types.shellPackage.check shells;
02:22 <clever> gchristensen: this looks fishy
02:22 <clever> 156         type = types.either types.shellPackage types.path;
02:22 <clever> 157         default = pkgs.shadow;
02:22 <clever> 422   systemShells =
02:22 <clever> 426       filter types.shellPackage.check shells;
02:22 <gchristensen>     environment.systemPackages = systemShells;
02:23 <clever> gchristensen: yeah, the default .shell for users is shadow (aka nologin)
02:23 <clever> despite the users.defaultShell being bash
02:23 <gchristensen> yeah so
02:23 <clever> and then it will filter the .shell of each user, on it being a valid shell
02:23 <clever> and install them in systemPackages for you
02:23 <gchristensen> it used to not add shadow to systemPackages b/c it wasn't a "shell"
02:23 <clever> when shadow got fixed, it started passing that test

The underlying issue is the config iterates over the defined users, and if their shell is marked as a shell, the shell is installed in systemPackages, and the collection of systemPackages is made available at /run/current-system/sw/bin. the "do they want us to set the password?" was determined by "is passwd installed?". passwd was only explicitly installed if mutableUsers = true, and the correction of the shell marking made it implicitly installed because mkpasswd and nologin are from the same package.

This issue is still present in 21.05 and is not limited to installations.
On a fresh installation, the following configuration can show the problem.

this simple config will not produce a password entry in /etc/shadow: https://gist.github.com/grische/e539d807401baf1ebd5991fa8b009802[root@cs-nixos:~]# grep root /etc/shadow
root:!:1::::::

changing mutableUsers = false; will produce a password entry in /etc/shadow[root@cs-nixos:~]# grep root /etc/shadow
root:$6$970P0wvKXqp8ZGO6$HbAHNz1fgC8mbJgKtjBt3dr3L2SrUEDNUnbp0OPHqI.WK8iW/O.B9WeHcK3B1oBkS/1k2tYDR5pnjXaXzszcF/:1::::::

Having the same problem on a current install

No solution for this yet?

I can't authenticate as root as it does not seem to have a password.


Compilation fails because of typo

Compilation fails on this line, removing it fixes the issue.
Is this a typo?
https://github.com/lvgl/lvgl_esp32_drivers/blob/4afc03a9fa18600f508b0d8b593ddcb96376e004/lvgl_tft/EVE_commands.c#L337

It seems like a copy paste error, what display were you using?

Thank you, I'm using a FT81X with configuration EVE_RiTFT43


Disallow Void type in type restrictions except for C bindings

The main purpose of the Void type is for C bindings where it represents no value. In Crystal's type system it maps to Nil. The philosophical difference is that a Nil value is still a value and not nothing. Practically, it doesn't have any effect.
There should be no reason to use the Void type in Crystal code for anything else but C interfaces.
And you can't really get a Void value in Crystal. It's just Nil.
Void is already disallowed as a field type for lib structs. So why should it be valid in a Crystal struct?
I propose to disallow a plain Void type from any type restriction in Crystal except for lib functions. The only relevant use case is a void pointer indicating untyped memory. So Pointer(Void) should be allowed. Subsequently Void should probably be valid as a generic type argument for any generic type.
But any type restriction x : Void just doesn't make sense, nor does uninitialized Void which can even break the compiler (#5364).
Previous discussion: #10146

IMO we should go one step further and represent void pointers as some other concrete type, say RawPointer, and make it so that Pointer(T) < RawPointer, keeping pointer arithmetic operations in the generic type. This RawPointer, like Int and Float, is never a union root (to prevent unions of different pointers from coalescing into void pointers).
Void* would still be allowed within libs, but it would be the parser that transforms them into ::RawPointers, and any invalid use of Void results in a parsing error; thus Void will be gone during semantic analysis.


issue with running the program on a Pi ZeroW

Hello! I want to preface this by saying that I have absolutely no programing experience, so this guide has been very helpful. I've run into an issue though.
First off, I am running the setup somewhat unconventionally. I am using a pi zero W. I've found that when I run the microphone off of the USB port of the pi, I don't actually have enough power to boot. My solution is this: run the microphone off of a powered USB bank, and, since I don't have the proper conversion cable, run that powered bank into my unpowered bank which has a micro connector to my pi.
I've found that I am able to plug my keyboard and mouse into the powered bank and use it on the pi just fine, so on some level it's working at least somewhat. After a lot of troubleshooting, I managed to get it to the point where it runs the code just as it shows in the video.
Here is the problem. The LEDs do not light, and the FPS only updated 3 times before everything just stopped.
What should I do here? Is this just a limitation of the zero? Is there anything I could try to do to fix it? Any help would be appreciated. This was just a "getting my toes wet" sort of project, so it's no big deal if it will be impossible to run on my Zero. Thanks in advance for any assistance!
Attached is a photo of what my command prompt was displaying when it stopped working.

Hey there,
Unfortunately, it is a limitation with the Zero :( in my original video, I think I mentioned trying to get it to work on a Pi Zero but failed. Even after I use external power for the lights, the Pi just can't handle the script before it crashes.
My experience was that the FPS started at 50 and slowly dropped to single digits before becoming unresponsive. Sorry, I don't think there's anything you can do with this project. I need to spend time to figure out where it gets stuck but the Pi Zero just may not have the processing power this project needs so I don't know if it's worth it.
If you want to get your toes wet with the Pi and WS2812b, I have a couple of other projects that would help:
https://github.com/naztronaut/FCW - Flask Controlled WS2812b - it'll let you control your lights remotely and the code I have is pretty simple so if you do want to get into python, a good place to start might be to change some of the visualizations or create some new ones yourself.
https://github.com/naztronaut/AIIM - Detects if you're in a meeting on Zoom or Microsoft Teams and triggers lights to be turned on remotely. It requires a python script to be run on your computer as well as a Pi.
Both projects above work on the Pi Zero.

Those look awesome! Thanks for the help. It was fun to at least try something out, even if it didn't work out in the end. Thanks man!

Best of luck! I have other projects and most of them are Pi Zero friendly. This just happens to be the only one that needs to be run on a full Pi.
More guides here: https://www.easyprogramming.net/raspberrypi.php
I'm pretty responsive on my site and github if you get stuck.


Cleos changes for REX are incorrect: from_net == amount to be unstaked from CPU.  from_CPU == amount to be unstaked from NET

Resolved by #7277, #7282, #7283.


Added forgotten last slash in result of getUrl function

Hello!
When i try upload image from ckeditor's "image properties" window, in "upload" tab, "/laravel-filemanager/upload" route response JavaScript code has wrong image url.
For example: he returns a '/photos/1577488c96564f.png' string, while real url is '/photos/1/577488c96564f.png'
before:

after:

thank you @shooter0106 , we just merged #81, did it fix this bug as well?


Node.js have moved to new domain so update the links

Describe the bug
If a user clicks on the node.js links provided it doesn't redirect to new domain of node.js
Reproduction
https://github.com/arclix/core
Steps to reproduce
No response
System Info
System:
    OS: Windows 10 10.0.22621
    CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
    Memory: 1.91 GB / 7.90 GB
  Binaries:
    Node: 18.14.2 - C:\Program Files\nodejs\node.EXE
    Yarn: 3.4.1 - C:\Program Files\nodejs\yarn.CMD
    npm: 9.5.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.1255.0), Chromium (111.0.1661.51)

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Arclix issue and not a React specific issue.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] Please follow minimal reproducible example of the bug and Refer the example issue

[ Triaged ] : Good to start the development


--skip doesn't seem to do anything anymore

Hello,
Around a month or two ago isort started ignoring all the items listed under skip in my .isort.cfg. I cannot get it to skip even when explicitly passing it skip from the command line:
(my.project) bash-3.2$ isort --skip /Users/gaffney/workspace/my.project/app/my-project/x/gen/constants.py --check-only app/my-project/x/gen/constants.py
ERROR: /Users/gaffney/workspace/my.project/app/my-project/x/gen/constants.py Imports are incorrectly sorted.

Hi @gaffney,
isort no longer skips items directly passed in from the command line, due to the confusion this caused. In general, in your example, both saying explicitly that you want to sort something, and also explicitly don't want to sort it leads to some ambiguity. For example, there used to be a default to skip __init__.py, but then when people ran isort __init__.py it wouldn't do anything, even though they explicitly asked it to. The skips now, intentionally, only affects recursive or plugin based usage. If you have a .isort.cfg with that skip in it and run isort . --recursive it should be skipped.
Thanks!
~Timothy

The skips now, intentionally, only affects recursive or plugin based usage.

👍 --recursive did it. The issue was that we were doing find blah | xargs isort.
Guessing this is a result of not reading the docs closely enough 😄

So glad to hear it's working for you now! Could also very well be a case of not writing enough docs as well! I'll add a question flag to this to make sure I know I recheck its documentation status.
Thanks!
~Timothy


Update sbt-mdoc to 2.2.21

Updates org.scalameta:sbt-mdoc from 2.2.20 to 2.2.21.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "sbt-mdoc" } ]

labels: sbt-plugin-update, semver-patch

Codecov Report

Merging #221 (f8bd86e) into main (e1d0cb7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #221   +/-   ##
=======================================
  Coverage   96.37%   96.37%
=======================================
  Files           7        7
  Lines         966      966
  Branches       93       93
=======================================
  Hits          931      931
  Misses         35       35

Impacted Files
Coverage Δ

core/shared/src/main/scala/cats/parse/Parser.scala
96.10% <0.00%> (ø)

Continue to review full report at Codecov.

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


[jsx] Automatic HTML indentation and cursor position in JSX

VSCode Version:1.8.1
OS Version:10.12.2

VS code is not properly indenting and moving the cursor when writing HTML elements in JSX:

Atom does it correctly:

Does anybody know an extension or setting to fix it? I've been researching and I haven't been able to find a solution.

Hi @aeschli,
I downloaded the night build and verified the the issue was fixed:

But I noticed a new issue in the night build that wasn't happening on the current stable release.
Autocomplete is not working on the night release:

On stable it is:

I got the same behavior in Javascript and Javascriptreact files.
Should I open a new issue to report this?
Thanks!

Yes, please file a new issue. Thanks!

Marking as verified based on https://github.com/Microsoft/vscode/issues/18284#issuecomment-271896612


String concatenation

It would be good to have string concatenation.
Key examples:
T-SQL allows using the + operator on strings.
MySQL has the CONCAT() function.

Thanks! It looks good to have both.

I've reviewed several databases and it looks good to follow PostgreSQL's policy.
It implements both ANSI SQL || operator and CONCAT function.
However, CONCAT's behavior is different from ||.
"Foo" || NULL => NULL but CONCAT("Foo", NULL) => "Foo".
CONCAT ignores NULL value.
Both can be useful for different purposes.

This has been implemented in PR #521.  Can we close this issue?


adjustment of content to window size

Content doesn't get adapted to changing window size which can result in garbled output.
The main window doesn't seem to be able to wrap the actual content or adjust it to decreasing window size by any other means. As a consequence content starts overlapping if width and/or height of a window decrease.

Sometimes the headers get cut besides sufficient horizontal space is available.

The window is already tightly packed, so adjusting layout on resize probably won't help much.
I think the best solution is to display only one configuration section at a time, and have a tab bar or list box to switch between sections. That should also solve your problem with section headers coincidentally (although I haven't been able to reproduce it). What do you think?

Actually I still think it could be an option to just wrap the text and make those forms to fill in paths and the like adjust their size automatically if this is technically feasible.
Maybe revamping the UI in general is the better option, though. If you should consider this I for one would find an UI as used to configure LXQt's panel

the most convenient.
The cutting of headers could be seen on Xfce only, no matter whether Openbox or Xfwm were running, neither on KDE Plasma 5 nor LXQt.
Maybe this is because on Xfce only those headers are in bold font (for whatever reason, didn't try to look into this any further).

In a06bf050865d82ab38a2e136ab2a3c756acb5c9e I switched to a tab based UI. It still can't make adjustments on window resize, but the window should fit in smaller screens easily now.
It should be easy to convert the tabs to a vertical list like configuration dialogs in LXQt and KDE, but before working on that, I wanted to see if this version solves any of your problems.

Just had a look at a06bf05:
Still it's not possible to wrap text which seems a bit odd to me. But probably this won't matter any longer due to the new layout.
Those cut headers are gone as well, both on LXQt/Openbox and Xfce/Xfwm. If horizontal space decreases characters are replaced by '...' which makes senses, IMO.
Notes (unrelated stuff I deem worth mentioning but not worth putting into an issue on its own or so):
Depending on the font explanatory text may be bold and larger than the text it refers to like here (DejaVu Sans 10)

When using those tabs or something similar I'm not sure whether alphabetical order of headers is intuitive. Not sure how to do it better either, though.
Aside from this I wonder whether it wouldn't make sense to integrate 'Autologin' into 'Users'.
sddm.conf is saved 600. Isn't this a bit strict? IMHO 644 would do as well as there are no credentials in that file and allow ordinary users to quickly check which options are set.
Latest commit / afd6003 doesn't build here but fails with some error messages regarding translation I can't judge.

I've fixed the build error about translations. Note that you need to have lrelease (part of qt5-tools on ArchLinux).
To minimize hard-coding, sddm-config-editor displays settings in the same structure as the sddm configuration file, so merging Autologin and Users sections isn't an option.
The program doesn't change the mode of sddm.conf, but I guess it uses mode 600 to create it if sddm.conf doesn't exist before running it. This shouldn't happen often, but I will fix it later.

The program doesn't change the mode of sddm.conf, but I guess it uses mode 600 to create it if sddm.conf doesn't exist before running it. This shouldn't happen often, but I will fix it later.

You're right, this is exactly what happens: if sddm.conf doesn't exist yet, it's saved 600, if it exists, the permission bits aren't touched.
Not sure whether a missing sddm.conf is that seldom, btw. E. g. Arch Linux doesn't ship it by default.


refactor!: config dataclasses

BREAKING_CHANGE: TODO
Closes #122

Blocked by https://github.com/datamole-ai/edvart/pull/119 which unifies interface of .add_... methods and section __init__()s

@mbelak-dtml Would you please review this draft? I would like to have the design approved before proceeding with creating more dataclasses.

Hi @lukany, IMHO introduction of config classes would make the API less user-friendly by adding an extra step in configuring of the sections. I understand the simplification of the code base by removing duplicate parameters, but IMO this is not a big issue and not worth the added complication for the user. Additionally, with #36 (addition of a generic Report.add_section), we could remove the add_<section> methods of Report, removing the duplicated parameters.

Agree. Closing this PR.


API: represent tuply declarations in the syntax tree

extend the syntax-tree to represent tuply declarations
add traversals for concrete syntax trees (trees that have tuply declarations) to the modules:

E_visit
P_visit

add functions for creating syntax-tree nodes relevant to tuply declarations

Unless I'm mistaken, this is superseded by #140.


typo: betweeen -> between

Docs Build status updates of commit ed36438:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference-architectures/hybrid-networking/troubleshoot-vpn.md
:white_check_mark:Succeeded
View

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


Fix @frozen typing to work on PEP-681 checkers

Summary
Currently, @frozen does not disallow setting instance properties in type checkers that implement PEP-681. Now the following is marked as an error in both mypy and pyright:
from attrs import frozen

@frozen
class Frozen:
    a: str

f = Frozen("a")
f.a = "new"

Pull Request Check List

[x] Added tests for changed code.
Our CI fails if coverage is not 100%.
[x] New features have been added to our Hypothesis testing strategy.
[x] Changes or additions to public APIs are reflected in our type stubs (files ending in .pyi).

[x] ...and used in the stub test file tests/typing_example.py.
[x] If they've been added to attr/__init__.pyi, they've also been re-imported in attrs/__init__.pyi.

[x] Updated documentation for changed code.

[x] New functions/classes have to be added to docs/api.rst by hand.
[x] Changes to the signature of @attr.s() have to be added by hand too.
[x] Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.
Find the appropriate next version in our __init__.py file.

[x] Documentation in .rst files is written using semantic newlines.
[x] Changes (and possible deprecations) have news fragments in changelog.d.
[x] Consider granting push permissions to the PR branch, so maintainers can fix minor issues themselves without pestering you.

LGTM