Allow Conan references with user and channel in conan.lock files

Problem Statement
When cdxgen parses conan.lock files, it fails to detect Conan packages whose reference specifies user and channel attributes.
Consider the following conan.lock file, where the listed package's reference does not specify user and channel. This sample is similar to a conan.lock already present in test data. When running cdxgen -t cpp ., the created bom.json reflects the package accurately:
/* excerpt from conan.lock */
{
 "graph_lock": {
  "nodes": {
   "0": { /* ... */ },
   "1": {
    "ref": "libcurl/8.1.2#3ddeb44d32deb27b1e0b027ad1c0e673",
    /* ... */
   }
  }
 }
}

/* excerpt from bom.json */
{
    "components": [
      {
        "group": "",
        "name": "libcurl",
        "version": "8.1.2",
        "purl"<EMAIL_ADDRESS>        "type": "library",
        "bom-ref"<EMAIL_ADDRESS>      }
    ]
}

However, any packages with user and channel specified in the conan.lock file (note the @internal/stable) are not found in the resulting bom.json:
/* excerpt from conan.lock */
{
 "graph_lock": {
  "nodes": {
   "0": { /* ... */ },
   "1": {
    "ref": "libcurl/8.1.2@internal/stable#0528972de6fa5f9c3ec7958fb8875338",
    /* ... */
   }
  }
 }
}

/* excerpt from bom.json */
{
    "components": []
}

Summary of Changes

Adds function mapConanPkgRefToPurlStringAndNameAndVersion to utils.js (+ a new test conan package reference mapper to pURL in utils.test.js) capable of parsing Conan references and transforming them to a pURL string.
Removes in-place Conan reference parsing logic in parseConanLockData and replaces it with a call to mapConanPkgRefToPurlStringAndNameAndVersion.
Removes in-place Conan reference parsing logic in parseConanData and replaces it with a call to mapConanPkgRefToPurlStringAndNameAndVersion.
Adds new test parse conan data where packages use custom user/channel to verify behavior of the above on added test files conanfile.with_custom_pkg_user_channel.txt and conan.with_custom_pkg_user_channel.lock.
Changes pURL format to comply with the latest revision of Package URL Type definitions for Conan by renaming a currently generated specifier revision to rrev.
Allows including specifiers user, channel, prev in the Conan pURL when their counterparts are present in the parsed Conan reference.
Adjusts the parse conan data test from utils.test.js to:

Expect 43 instead of 42 results. The test file conanfile1.txt actually contains 43 package references, the entry libx264/cci.20220602@iw/stable#018d183cfa8ac8c55af9f4406d6d40e4 appears not to have been recognized by the original parsing logic.
Expect the channel, user and rrev specifiers for the verified package, which are newly added by the new parsing logic.

@Khubajsn could you kindly run pnpm lint && pnpm run gen-types

Let me merge this and do it in my PR branch since I have a large drop coming.


CORS configuration

Assuming a default CORS configuration, it seems it's only possible to make a GET request to app.piratepx.com (namely the /ship endpoint) from:

the same domain (i.e. piratepx.com)
a non-browser client such as curl

More info here: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS

Hey @jmoore34 – Hmmm. It's true that only GET /ship supports CORS, but it should allow any origin. To help me reproduce, what specifically are you trying to do?

Here's a minimal reproduction
and the login

Hey @jmoore34 – Sorry for not getting back to you on this.
It looks like that CORS test site you used for the minimal reproduction is no longer around, but just looking at the URL, it appears that you're missing the /ship path:
https://app.piratepx.com?p=308dd021-f843-43df-88d4-6119a7a0dbe3&i=test

It should be:
https://app.piratepx.com/ship?p=308dd021-f843-43df-88d4-6119a7a0dbe3&i=test

Here's another CORS test site with the correct URL: CORS Tester. You can see that it's correctly configured to support CORS.
Let me know if I'm missing something, or if it's still not working for you!


arch: fixed error in the calculation of nwords caused an out of bounds

Summary
Fixed an error in the calculation of nwords caused an out of bounds.
Impact
stack
Testing
ostest pass

@masayuki2009 can this cause an issue that needs your workaround for stm32discovery?

@masayuki2009 can this cause an issue that needs your workaround for stm32discovery?

@pkarashchenko
Let me check this PR tomorrow but I think this PR just fixes stack coloring and would not fix the issue on stm32f4discovery because the feature was disabled when I encountered the hardfault on the board.

@masayuki2009 could you merge it?


Update README.md

Updating command to install package via composer. Do not edit composer.json or composer.lock directly and don't run composer update

👍


[Revise logical def] 'Townes-Brocks syndrome 2'

Mondo term (ID and Label)
'Townes-Brocks syndrome 2'
Suggested revision of logical definition
'disease has basis in dysfunction of' some 617466 should be
'disease has basis in dysfunction of' some DACT1

[ ] need to import http://identifiers.org/hgnc/17748

related to #1855


groupby on dask objects doesn't handle chunks well

80% of climate data analysis begins with calculating the monthly-mean climatology and subtracting it from the dataset to get an anomaly. Unfortunately this is a fail case for xarray / dask with out-of-core datasets. This is becoming a serious problem for me.
Code Sample
# Your code here
import xarray as xr
import dask.array as da
import pandas as pd
# construct an example datatset chunked in time
nt, ny, nx = 366, 180, 360
time = pd.date_range(start='1950-01-01', periods=nt, freq='10D')
ds = xr.DataArray(da.random.random((nt, ny, nx), chunks=(1, ny, nx)),
                   dims=('time', 'lat', 'lon'),
                   coords={'time': time}).to_dataset(name='field')
# monthly climatology
ds_mm = ds.groupby('time.month').mean(dim='time')
# anomaly
ds_anom = ds.groupby('time.month')- ds_mm
print(ds_anom)

<xarray.Dataset>
Dimensions:  (lat: 180, lon: 360, time: 366)
Coordinates:
  * time     (time) datetime64[ns] 1950-01-01 1950-01-11 1950-01-21 ...
    month    (time) int64 1 1 1 1 2 2 3 3 3 4 4 4 5 5 5 5 6 6 6 7 7 7 8 8 8 ...
Dimensions without coordinates: lat, lon
Data variables:
    field    (time, lat, lon) float64 dask.array<shape=(366, 180, 360), chunksize=(366, 180, 360)>

Problem description
As we can see in the example above, the chunking has been lost. The dataset contains just one single huge chunk. This happens with any non-reducing operation on the groupby, even
ds.groupby('time.month').apply(lambda x: x)

Say we wanted to compute some statistics of the anomaly, like the variance:
(ds_anom.field**2).mean(dim='time').load()

This triggers the whole big chunk (with the whole timeseries) to be loaded into memory somewhere. For out-of-core datasets, this will crash our system.
Expected Output
It seems like we should be able to do this lazily, maintaining a chunk size of (1, 180, 360) for ds_anom.
Output of xr.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 3.6.2.final.0
python-bits: 64
OS: Darwin
OS-release: 16.7.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: en_US.UTF-8
xarray: 0.10.0+dev27.g049cbdd
pandas: 0.20.3
numpy: 1.13.1
scipy: 0.19.1
netCDF4: 1.3.1
h5netcdf: 0.4.1
Nio: None
zarr: 2.2.0a2.dev91
bottleneck: 1.2.1
cyordereddict: None
dask: 0.16.0
distributed: 1.20.1
matplotlib: 2.1.0
cartopy: 0.15.1
seaborn: 0.8.1
setuptools: 36.3.0
pip: 9.0.1
conda: None
pytest: 3.2.1
IPython: 6.1.0
sphinx: 1.6.5

Possibly related to #392.
cc @mrocklin

@rabernat I recommend trying with a combination of these two PRs.  These do well for me on the problem listed above.

https://github.com/dask/dask/pull/3066
https://github.com/dask/distributed/pull/1730

There is still some memory requriement, but it seems to be under better control

@mrocklin thanks for the updates. I should have some time on Friday morning to give it a try on Cheyenne.

The relevant PRs have been merged into master on both repositories.

@rabernat you shouldn't need the spill to disk comment above, just things on master branches.  Ideally you would try your clmatology computation again and see if memory use continues to exceed expectations.

Checking in here.  Any luck?  I noticed your comment in https://github.com/dask/distributed/issues/1736 but that seems to be a separate issue about file-based locks rather than about task scheduling priorities.  Is the file-based locking stuff getting in the way of you checking for low-memory use?

Short answer...no luck. With the latest masters (but without the suggested dask config), I am still getting the same basic performance limitations.
I can update you more when we talk in person later today.

In recent versions of xarray (0.12.1) and dask (0.12.1), this issue has been ameliorated significantly. I believe this issue should now be closed.

I am trying a new approach to this problem using xarray's new map_blocks function. See this example: https://nbviewer.jupyter.org/gist/rabernat/30e7b747f0e3583b5b776e4093266114


We should improve error handling in Felix

Two particular examples that we should improve in Felix.

Felix is not very robust at all to invalid messages. For now, that is OK (since we control both ends of the API), but we should ensure that we toughen that up and send correct error messages before we integrate with any third parties.

Felix can be caught out by errors from (for example) "ip route add" - which we have seen intermittently. In practice, it just restarts and recovers, but we ought to find the things that can fail and handle them better.

I'm going to close this down. We are doing general testing and hardening of Felix, and having the catch all issue is not useful. The second bug mentioned turns out to have been bug #180, now fixed.


Unable to load images with trimmed whitespace at end of line

The Canvas.fromText function currently determines the canvas width by looking at only the first line of the file content.
ASCII art might have longer lines in later lines. The canvas should be sized to fit the entire art.
Trimmed whitespace on line endings needs to then be filled with empty strings when iterating through the pixels to set them.

This has been added to the v1 tracker, as issues with loading might lead to delayed bugs down the line that might become more difficult to troubleshoot

This is also a great candidate for TDD


Can this mode find the references of a var or func?

it is better to find where a var or func is used. ^_^

You want to look into the Go Oracle for this kind of functionality.


Add preview label to PCR read on standby docs

Fixes DOC-11751
We've decided to move PCR read on standby to the public preview phase.
Note on the main example on the CREATE VIRTUAL CLUSTER page, I've added a custom "preview" note since cluster virtualization is in preview but PCR generally is GA. See files for details.

Thanks for the quick reviews!


The Video preview image is not displayed in mobile browsers.

Description: The Video preview is not displayed in mobile browsers.
-Env:
Device: Android 7.1.1
Google Chrome Version <IP_ADDRESS>.83
Mozilla Firefox 53.0.2
Device: Iphone 7 IOS 10.3
Google Chrome Version <IP_ADDRESS>.113
Safari IOS 10.3
STEPS:
Steps

Open the Crafter studio with the Event site.
Go to the “Video ” section.
https://www.screencast.com/t/BRyD540Xwi
https://www.screencast.com/t/zNf4AwPoAi
https://www.screencast.com/t/9wkGr2mm

CURRENT RESULT:
The Video preview image is not displayed in mobile browsers.
EXPECTED RESULT:
The Video preview image should be displayed in mobile browsers.

Please test again using the recent version of crafter.

Fixed

Bug verified and closed as fixed in build 3753745.


Fix wrong text shortening in some corner cases ('...' being longer than 2 chars)

Description
The goal of this PR is to fix text shortening (nbgl_textWrapOnNbLines()) in some corner cases ("..." being longer than 2 chars)
Changes include

[x] Bugfix (non-breaking change that solves an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[ ] Documentation
[ ] Other (for changes that might not fit in any category)

Codecov Report
Attention: Patch coverage is 0% with 18 lines in your changes missing coverage. Please review.

Project coverage is 35.76%. Comparing base (603cf09) to head (8fa9f90).
Report is 68 commits behind head on API_LEVEL_21.

Files with missing lines
Patch %
Lines

lib_nbgl/src/nbgl_fonts.c
0.00%
18 Missing :warning:

Additional details and impacted files
@@                Coverage Diff                @@
##           API_LEVEL_21     #781       +/-   ##
=================================================
- Coverage         60.19%   35.76%   -24.44%
=================================================
  Files                12       13        +1
  Lines              1726     1591      -135
=================================================
- Hits               1039      569      -470
- Misses              687     1022      +335

Flag
Coverage Δ

unittests
35.76% <0.00%> (-24.44%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fixing the test case failure behind proxy.

Fixes Issue #1493
Description of Change
Though probably I could have changed that artifactory host URI protocol to http instead of https but I was not sure if you had any reason to choose that. Hence I just made sure, that particular test case runs in non proxy environment. Hence the change.
Have test cases been added to cover the new functionality?
Not Applicable.

Can one of the admins verify this patch?


Cleanups to metadata, docs, and tests

Updated the metadata in setup.py
Added tests for set comparison operators
Cleanups to docstrings
Simplified the ordered version of __eq__
Removed the coverage check for now; it doesn't appear to work out of the box on Travis
Dropped support for Python 2.6 (which has already been dropped by Python and pytest)

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8e6f096). Click here to learn what that means.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             master    #29   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      1
  Lines             ?    130
  Branches          ?     28
=======================================
  Hits              ?    130
  Misses            ?      0
  Partials          ?      0

Impacted Files
Coverage Δ

ordered_set.py
100% <100%> (ø)

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 8e6f096...5c37ed0. Read the comment docs.

@Erotemic This PR contains changes on top of your recent PR; would you like to review it?

LGTM!


merge access violation errors

I see several different error classes across the gems, e.g. Hyperloop::AccessViolation and ReactiveRecord::AccessViolation. It would be useful if they all shared a parent class e.g. HyperloopError rather than inheriting from StandardError.

Thanks ReactiveRecord::AccessViolation was deprecated long ago, but never removed from the code.  Taking it out now.  Given this I think its okay to continue having the single error Hyperloop::AccessViolation inherit from standard error?  If not the issue needs to be on either the Hyperloop-config gem (since its the common base) or on Hyper-operation (since its where it comes from)  closing this for now.


Info about Linux not being supported should be more visible

Information that this task is not supported on Linux should be put in bold at the beginning of the page.
Also it should be supported on Linux, it is not 1995 anymore.

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

ID: ddb32280-1779-eb6e-0f78-8707be623a9a
Version Independent ID: ddb32280-1779-eb6e-0f78-8707be623a9a
Content: SqlAzureDacpacDeployment@1 - Azure SQL Database deployment v1 task
Content Source: task-reference/sql-azure-dacpac-deployment-v1.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-tasks
GitHub Login: @steved0x
Microsoft Alias: sdanie

Thank you for your feedback. We are migrating this issue to our new documentation feedback system, and closing this issue.
As we phase out GitHub issues for this repository, we encourage you to propose changes using public PRs or submit feedback through our updated control at the top of the page. For more information on our feedback systems, see https://aka.ms/contentuserfeedback.


bluez also install gatttool

Motivation for this change
bluez does not install gatttool by default, although it does build it.
https://bugzilla.redhat.com/show_bug.cgi?id=1141909
Things done

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

[yes] 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/)
[ ] Fits CONTRIBUTING.md.

Do we also need mpris-proxy? Please reword your commit to bluez: also install gatttool

Seems you have pushed something else to this branch now (simavr).

Hi, i got the impression that git would stick the pull request to the commits at the time of the request, and further work would not be included? I have the branch so I can do my own stuff with nixpkgs... I didn't realise it would add it to this ticket.

GitHub allows you to update the branch with a Pull Request and this updates the Pull Request. GitLab allows the same with their Merge Requests, by the way.
The choice is not on the level of Git, it is determined by the Web UI software anyway.

deprecated by https://github.com/NixOS/nixpkgs/pull/23540


Update README.md explainable ai

please verify the updated clone commands for the new repo are accurate.

@riacheruvu  please review it and merge if ok


2024 HxGN TIFF Tiles

Benefit
Provide the actual flight dates of imagery in the Hexagon services via OpenData. Also facilitate requests for the original imagery tiles
Acceptance Criteria

[x] Inventory what Hexagon provided
[x] Create layer and update Utah Hexagon Service Dates OpenData layer
[ ] Create tile index with attributes for the folder and drive

Notes

Risks

None

Issue Reference

Atlas shows the flight data. Will we need to repoint to this data when it's available?

I doubt it but I really don't know what you are using. I simply added the
new tiles to
https://opendata.gis.utah.gov/datasets/7df5278c3e1a46389693c957a75b2b99_0/explore
then deleted the old tiles. This task is complete.
Rick Kelson
Utah Geospatial Resource Center (UGRC)
801.433.7891
gis.utah.gov
On Mon, Dec 23, 2024 at 3:16 PM steveoh @.***> wrote:

Atlas shows the flight data. Will we need to repoint to this data when
it's available?
—
Reply to this email directly, view it on GitHub
https://github.com/agrc/planning-queue/issues/509#issuecomment-2560371975,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPJ43JDYFENV7Y6PE7KBQL2HCDSXAVCNFSM6AAAAABUDW67D6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRQGM3TCOJXGU
.
You are receiving this because you were assigned.Message ID:
@.***>

this is complete

Atlas uses indices.hexagon_service_dates in the open sgid.
https://github.com/agrc/atlas/blob/ce562f16bceda3fe54de6c90da7e9437a1370fec/src/components/Identify.jsx#L10-L19


Fix pagination

Incorrect data return from methodDescriptor.value in pagination middleware

Sorry, worked on the old examples, a new use only in the tests saw


opentelemetry-collector: 0.26.0 -> 0.31.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/open-telemetry/opentelemetry-collector-contrib/releases.
meta.description for opentelemetry-collector is: "OpenTelemetry Collector"
meta.homepage for opentelemetry-collector is: "https://github.com/open-telemetry/opentelemetry-collector"
meta.changelog for opentelemetry-collector is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

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

/nix/store/1pwyrxxnpx1347ycah56mb3wm4idcfib-opentelemetry-collector-0.31.0/bin/otelcontribcol passed the binary check.

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

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

found 0.31.0 with grep in /nix/store/1pwyrxxnpx1347ycah56mb3wm4idcfib-opentelemetry-collector-0.31.0

found 0.31.0 in filename of file in /nix/store/1pwyrxxnpx1347ycah56mb3wm4idcfib-opentelemetry-collector-0.31.0

directory tree listing: https://gist.github.com/adec721aa4f4604c2a38e34485d1ca81

du listing: https://gist.github.com/431480db107ae7ae1c442ee280a1363b

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
opentelemetry-collector

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1pwyrxxnpx1347ycah56mb3wm4idcfib-opentelemetry-collector-0.31.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1pwyrxxnpx1347ycah56mb3wm4idcfib-opentelemetry-collector-0.31.0
ls -la /nix/store/1pwyrxxnpx1347ycah56mb3wm4idcfib-opentelemetry-collector-0.31.0/bin

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

1 package built:

opentelemetry-collector

Maintainer pings
cc @uri-canva @kalbasit for testing.

Result of nixpkgs-review pr 134240 at 4e2ec502 run on aarch64-linux 1

1 package built successfully:

opentelemetry-collector

1 suggestion:

warning: unused-argument
Unused argument: stdenv.
Near pkgs/tools/misc/opentelemetry-collector/default.nix:3:3:
  |
3 | , stdenv
  |   ^


Add links to web posts and video content

Teku Snapshot Sync from Infura: https://www.youtube.com/watch?v=ce9uVRl23zI


Add Antares Solar System from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of electricpantz, to add Antares Solar System to CKAN.
Mod details:
name = /mod/754/Antares%20Solar%20System
author = electricpantz
abstract = A planet pack that adds 1 red giant star, 2 planets, and 1 moon to the game.
license = MIT
Homepage =
description = ANTARES: Antares is a red giant about 10x the size of Kerbol, and orbits very far away, making use of FTL-Drive mods out there. Also has 2 planets.
CORBID: Corbid is a relatively large gas giant, which has a particularly strong calming effect on all kerbals who witness it's red and beautiful glory.
COASTER: A habitable moon with many islands, however, all but the largest are the same color as the map view water, as to confuse kerbals.
JERREN: An ice giant that is a nice blueish-teal. It is very pleasing to the kerbal eye, as it's colors are calm, as is it, with absolutely no storms anywhere.
Please direct questions about this pull request to electricpantz.

Closing in favour of #4232


failed to load module for ssr

Describe the bug
when I using dynamic import like this:
function load (component) {
  return () => import(`../pages/${component}.vue`)
}

export default [
  {
    path: '/',
    component: load('index'),
    meta: { title: '首页' }
  }
]

I got an error: Error: failed to load module for ssr: ../pages/index.vue
but it can work like this:
export default [
  {
    path: '/',
    component: () => import('../pages/index.vue'),
    meta: { title: '首页' }
  }
]

Reproduction
https://github.com/dongnaebi/vite-ssr-repro

System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
  System:
    OS: Windows 10 10.0.19041
    CPU: (4) x64 Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
    Memory: 8.10 GB / 15.88 GB
  Binaries:
    Node: 14.4.0 - D:\Program Files\nodejs\node.EXE
    npm: 6.14.5 - D:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 89.0.4389.128
    Edge: Spartan (44.19041.906.0), Chromium (90.0.818.42)
    Internet Explorer: 11.0.19041.1

Used package manager: npm
Logs

Error: failed to load module for ssr: ../pages/index.vue
    at instantiateModule (E:\project\jiuyun-pc\node_modules\vite\dist\node\chunks\dep-5c642f9e.js:68989:15)
Error: Couldn't resolve component "default" at "/"
    at E:\project\jiuyun-pc\node_modules\vue-router\dist\vue-router.cjs.js:1998:47
(node:4672) UnhandledPromiseRejectionWarning: Error: Couldn't resolve component "default" at "/"
    at E:\project\jiuyun-pc\node_modules\vue-router\dist\vue-router.cjs.js:1998:47
(node:4672) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). T
o terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 16)

Before submitting the issue, please make sure you do the following

[ 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 ] Provide a description in this issue that describes the bug.
[ x ] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[ x ] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

This may be fixed by #2934 :thinking:
Could you try this branch? (build locally and use yarn link)


Gallery fullscreen view is not always working well

fullscreen image is not always the correct image, animation going back out of detail view is slow

https://github.com/stfalcon-studio/StfalconImageViewer might be a good replacement, with the added bonus that it supports swipe-to-dismiss


Delete governance/roles-and-responsibilities.md

This is an outdated file and it is confusing to keep this active. This information now lies in another document.

@germonprez indeed it is.


Should the Bridge's send() method require a mutable reference?

Description
I'm submitting a Question
I would expect the Bridge's send() method to require a mutable reference to self. Because it only requires a reference, it is possible to send messages via the bridge in the view(&self) function defined in the Responder trait. I think that this isn't idiomatic with the rest of Yew, in that code responsible for rendering HTML shouldn't be able to affect the rest of the application. Obviously, the send() method in the Bridge doesn't need a mutable reference to self, but I think that it should in order to mandate good code organization for users of Yew.
Expected Implementation

/// Bridge to a specific kind of worker.
pub trait Bridge<AGN: Agent> {
    /// Send a message to an agent.
    fn send(&mut self, msg: AGN::Input);
}

Current Implementation
Currently the Bridge trait is specified as:

/// Bridge to a specific kind of worker.
pub trait Bridge<AGN: Agent> {
    /// Send a message to an agent.
    fn send(&self, msg: AGN::Input);
}

This allows you to send messages via bridges in the Responder trait's view() function because view's reference to self isn't mutable.

Context (Environment)

Rust: not relevant

yew: commit(current): 5e110bcf2ddc0b163f4b864ab69c7b058befe484

target: not relevant

cargo-web: not relevant

browser if relevant
not relevant

it is possible to send messages via the bridge in the view(&self)

@hgzimmerman Excellent! :trophy: Could you please change it to &mut self?
It's great find, but I'm in a business trip and couldn't fix it right now.

I've been busy for the last few days. I'll try to get a PR to you tomorrow.


⚠ ClamAV has degraded performance

In 7cab9b6, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 105 ms

Resolved: ClamAV performance has improved in 9bf3d27.


Speed up depthgauge

Is there a way to increase the speed of depthgauge besides setting / increasing threads? When running on ~100 viral samples it takes around a day and a half to complete and seems to run more slowly when the number of samples is increased. In the beginning, it quickly works through the first 50 or so, but then slows to an approximate rate of 1 per ~40mins towards the end of processing the samples.
With having threads set to 4, on ~190 samples it took >3 days to finish running. So the average time expected for calculating the depth of viral samples is around ~40mins per sample.

probably the python code is very inefficient; should never take that long

It should take like an hour at most


Fix link to auth example

The link to the authentication example is incorrect. This fixes it.

This change is

Linux foundation CLA has now been signed.

thanks


RDK-29649 : CEC Menu Language Support changes

RDK-29649 : CEC Menu Language Support changes

Please rebase and fix the conflicts.

Please rebase and fix the conflicts.

Done


feat: add nixd

Describe your changes
Adds the nixd LSP at the latest version 2.4.0. The previous PR has become stale.
Issue ticket number and link
Closes https://github.com/williamboman/mason.nvim/issues/1570
Updates the stale, but already approved PR, https://github.com/mason-org/mason-registry/pull/4822

I attempted this in

https://github.com/mason-org/mason-registry/pull/6725

but I'm not positive that nixd can be installed via mason that easily, for three reasons:

it doesn't offer (pre-built) binary distributions
it has exotic dependencies which users would need to pre-install for the build to succeed outside of nix build
the build produces shared libraries which nixd links against, this isn't supported by Mason

See https://github.com/mason-org/mason-registry/pull/6725#issuecomment-2351015814 for more details.

I attempted this in
* [feat: add nixd #6725](https://github.com/mason-org/mason-registry/pull/6725)

but I'm not positive that nixd can be installed via mason that easily, for three reasons:
* it doesn't offer (pre-built) binary distributions

* it has exotic dependencies which users would need to pre-install for the build to succeed outside of `nix build`

* the build produces shared libraries which `nixd` links against, this isn't supported by Mason

See #6725 (comment) for more details.

Gotcha, thanks for outlining that, @antoineco.
I will close this one as well, and share the context in the original GitHub issue too. 🙏


Add Maven Central badge to Readme

To help users discover latest published artifact.

Thank you.

WTF, man. Do I honestly have to review edits to README nowadays?

Not sure what you mean.

README badge was broken after merge. I didn't see it until today and fixed it. Don't know what happened there but it showed the markdown source of that image include as unparsed. In your commit it looks fine actually.

Ooh interesting. Might have been related to the new markdown parser github rolled out recently. Sorry for the hassel. Glad to see it's working now.


Rails 5.2

Do yo plan to support rails 5.2?

Yes, thanks for asking, rails 5.2 support should be coming shortly.


optimizing docker build process and using smaller base image

This PR includes changing the kexpand docker image to be based on alpine:3.4 over debian:jessie.  This resulted in a size decrease from 130MB down to just 8MB.
The build process is now completed using golang:1.7 image instead of debian:jessie and installing go onto that container.  This takes a long step out of the process and reduces initial runs of make images by over half in my tests.
current method
Successfully built 16c67599fd0c
      280.54 real         0.16 user         0.22 sys
~/work/src/github.com/kopeio/kexpand (master) $ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
kopeio/kexpand      latest              16c67599fd0c        2 minutes ago       129.2 MB
kexpand-builder     latest              ca79a5c903b4        2 minutes ago       667.2 MB
debian              jessie              7b0a06c805e8        2 weeks ago         123 MB

proposed method:
Successfully built f90b43e855ee
      129.63 real         0.18 user         0.21 sys
~/work/src/github.com/kopeio/kexpand (feature/docker-optimize) $ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
kopeio/kexpand      latest              f90b43e855ee        7 minutes ago       7.923 MB
golang              1.7                 f69c27b2f59a        13 days ago         672.4 MB
alpine              3.4                 baa5d63471ea        2 weeks ago         4.803 MB

I'm also playing with bazel, which has a really cool feature that it can build Docker images directly, but has the flipside that you have to install bazel.

(see #13)


Sometimes the mod does not work with saves that previously did not have the mod enabled.

save attached, this should give you everything you need to reproduce it.
Attempt doing anything, get your first level, try to spend points in Magic and it doesn't work for some reason.
bug.zip
Modlist is contained inside of the save. The 2 I added are this mod, and Editor Extensions. This should let you figure out what went wrong.
Note that it only happens on this save apparently, and I'm not sure what is causing the trouble. Any new saves work fine.

Hi @Famous5000 - sorry for the 1 year delay respons :sadge:
This is fixed in 1.0.8.


Not Found Page should be added

If you navigate to any non existing path;; for example : https://kucc.ku.edu.np/abc
There should be a page displaying PageNotFound or something like that
But instead nothing is rendered

working on it


texinfo: 7.0.3 -> 7.1

Description of changes

Things done
Add texinfo 7.1 and make it the default.

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Not sure if it's just texonfo-7.1 update or some extra patches I have locally, but I am seeing the following failure against this PR on ffmpeg-headless:
ffmpeg-headless> makeinfo: error parsing ./doc/t2h.pm: Undefined subroutine &Texinfo::Config::set_from_init_file called at ./doc/t2h.pm line 24.
ffmpeg-headless> POD    doc/libavfilter.pod
ffmpeg-headless> make: *** [doc/Makefile:69: doc/libavformat.html] Error 1 shuffle=3953956671
ffmpeg-headless> make: *** Waiting for unfinished jobs....

Does it work for you by chance?

Thanks for testing, @trofi. I'm seeing the same issue as you are when trying to run ffmpeg-headless in combination with the changes in this PR.
It seems the subroutine in question (among others) was prefixed with texinfo_ (see this commit) in September 2021 along with other refactorings that break producing the FFmpeg docs.
Applying the patch below in pkgs/development/libraries/ffmpeg/generic.nix fixes the issue. What is the best course of action from your point of view?
Report the patch to FFmpeg upstream and add it to the ffmpeg nix package for the time being?
fix-t2h-for-texinfo-7_1.patch
diff --git a/doc/t2h.pm b/doc/t2h.pm
index d07d974..fc85e04 100644
--- a/doc/t2h.pm
+++ b/doc/t2h.pm
@@ -21,7 +21,7 @@
 # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

 # no navigation elements
-set_from_init_file('HEADERS', 0);
+texinfo_set_from_init_file('HEADERS', 0);

 sub ffmpeg_heading_command($$$$$)
 {
@@ -55,8 +55,9 @@ sub ffmpeg_heading_command($$$$$)
         $element = $command->{'parent'};
     }
     if ($element) {
-        $result .= &{$self->{'format_element_header'}}($self, $cmdname,
-                                                       $command, $element);
+        $result .= &{$self->formatting_function('format_element_header')}($self,
+                                                       $cmdname, $command,
+                                                       $element);
     }

     my $heading_level;
@@ -112,8 +113,8 @@ sub ffmpeg_heading_command($$$$$)
                 $cmdname
                     = $Texinfo::Common::level_to_structuring_command{$cmdname}->[$heading_level];
             }
-            $result .= &{$self->{'format_heading_text'}}(
-                        $self, $cmdname, $heading,
+            $result .= &{$self->formatting_function('format_heading_text')}(
+                        $self, $cmdname, undef, $heading,
                         $heading_level +
                         $self->get_conf('CHAPTER_HEADER_LEVEL') - 1, $command);
         }
@@ -127,22 +128,22 @@ foreach my $command (keys(%Texinfo::Common::sectioning_commands), 'node') {
 }

 # determine if texinfo is at least version 6.8
-my $program_version_num = version->declare(get_conf('PACKAGE_VERSION'))->numify;
+my $program_version_num = version->declare(texinfo_get_conf('PACKAGE_VERSION'))->numify;
 my $program_version_6_8 = $program_version_num >= 6.008000;

 # print the TOC where @contents is used
 if ($program_version_6_8) {
-    set_from_init_file('CONTENTS_OUTPUT_LOCATION', 'inline');
+    texinfo_set_from_init_file('CONTENTS_OUTPUT_LOCATION', 'inline');
 } else {
-    set_from_init_file('INLINE_CONTENTS', 1);
+    texinfo_set_from_init_file('INLINE_CONTENTS', 1);
 }

 # make chapters

-set_from_init_file('CHAPTER_HEADER_LEVEL', 2);
+texinfo_set_from_init_file('CHAPTER_HEADER_LEVEL', 2);

 # Do not add

-set_from_init_file('DEFAULT_RULE', '');
-set_from_init_file('BIG_RULE', '');
+texinfo_set_from_init_file('DEFAULT_RULE', '');
+texinfo_set_from_init_file('BIG_RULE', '');

 # Customized file beginning
 sub ffmpeg_begin_file($$$)
@@ -159,7 +160,7 @@ sub ffmpeg_begin_file($$$)
     my ($title, $description, $encoding, $date, $css_lines,
         $doctype, $bodytext, $copying_comment, $after_body_open,
         $extra_head, $program_and_version, $program_homepage,
-        $program, $generator) = $self->_file_header_informations($command);
+        $program, $generator) = $self->_file_header_information($command);

     my $links = $self->_get_links ($filename, $element);

@@ -223,7 +224,7 @@ if ($program_version_6_8) {
 sub ffmpeg_end_file($)
 {
     my $self = shift;
-    my $program_string = &{$self->{'format_program_string'}}($self);
+    my $program_string = &{$self->formatting_function('format_program_string')}($self);
     my $program_text = <<EOT;

         $program_string
@@ -244,7 +245,7 @@ if ($program_version_6_8) {

 # Dummy title command
 # Ignore title. Title is handled through ffmpeg_begin_file().
-set_from_init_file('USE_TITLEPAGE_FOR_TITLE', 1);
+texinfo_set_from_init_file('USE_TITLEPAGE_FOR_TITLE', 1);
 sub ffmpeg_title($$$$)
 {
     return '';
@@ -262,7 +263,7 @@ sub ffmpeg_float($$$$$)
     my $args = shift;
     my $content = shift;

-    my ($caption, $prepended) = Texinfo::Common::float_name_caption($self,
+    my ($caption, $prepended) = Texinfo::Convert::Converter::float_name_caption($self,
                                                                 $command);
     my $caption_text = '';
     my $prepended_text;
@@ -335,21 +336,21 @@ sub ffmpeg_float($$$$$)
             $caption->{'args'}->[0], 'float caption');
     }
     if ($prepended_text.$caption_text ne '') {
-        $prepended_text = $self->_attribute_class('div','float-caption'). '>'
+        $prepended_text = $self->html_attribute_class('div', ['float-caption']). '>'
                 . $prepended_text;
         $caption_text .= '
';
     }
-    my $html_class = '';
+    my @html_class = ();
     if ($prepended_save =~ /NOTE/) {
-        $html_class = 'info';
+        push @html_class, 'info';
         $prepended_text = '';
         $caption_text   = '';
     } elsif ($prepended_save =~ /IMPORTANT/) {
-        $html_class = 'warning';
+        push @html_class, 'warning';
         $prepended_text = '';
         $caption_text   = '';
     }
-    return $self->_attribute_class('div', $html_class). '>' . "\n" .
+    return $self->html_attribute_class('div', \@html_class). '>' . "\n" .
         $prepended_text . $caption_text . $content . '
';
 }

ℹ Testing the proposed changes here with ffmpeg 6.1

Sure! I applied both to staging and got ffmped_6 failure as:
$ nix build --no-link -f. ffmpeg_6 --keep-going

error: builder for '/nix/store/nl2h321i26ccgmdbfwi9br1qh0m4dgkk-ffmpeg-headless-6.1.drv' failed with exit code 1;
       last 10 log lines:
       > Running phase: configurePhase
       > patching script interpreter paths in ./configure
       > configure flags: --disable-static --prefix=/nix/store/8lf8dsd42v79p9z0mgwnifhyybag32jh-ffmpeg-headless-6.1 --target_os=linux --arch=x86_64 --pkg-config=pkg-config --enable-gpl --enable-version3 --disable-nonfree --enable-shared --enable-pic --disable-small --enable-runtime-cpudetect --disable-gray --enable-swscale-alpha --enable-hardcoded-tables --enable-safe-bitstream-reader --enable-pthreads --disable-w32threads --disable-os2threads --enable-network --enable-pixelutils --datadir=/nix/store/svy6ssg03rz40hz743xwznhsam4hidgg-ffmpeg-headless-6.1-data/share/ffmpeg --enable-ffmpeg --disable-ffplay --enable-ffprobe --bindir=/nix/store/7rhxw2llf53jwcpf7hqr78aal6kw101x-ffmpeg-headless-6.1-bin/bin --enable-avcodec --enable-avdevice --enable-avfilter --enable-avformat --enable-avutil --enable-postproc --enable-swresample --enable-swscale --libdir=/nix/store/c596idk22gd4wni7krvhkx6qfwzbxpsl-ffmpeg-headless-6.1-lib/lib --incdir=/nix/store/gaqkwwq9pmqaa6zljrbn2bxn07zf9sdl-ffmpeg-headless-6.1-dev/include --enable-doc --enable-htmlpages --enable-manpages --mandir=/nix/store/mi6x2ykpvb3yrr7jgc3725v31k74d763-ffmpeg-headless-6.1-man/share/man --enable-podpages --enable-txtpages --docdir=/nix/store/frg6p28dav1i2l7fbx42fn6758b2pcmn-ffmpeg-headless-6.1-doc/share/doc/ffmpeg --enable-alsa --enable-bzlib --disable-libcelt --disable-cuda --disable-cuda-llvm --enable-libdav1d --disable-libfdk-aac --disable-libflite --enable-fontconfig --enable-libfreetype --disable-frei0r --disable-libfribidi --disable-libgme --enable-gnutls --disable-libgsm --disable-ladspa --enable-libmp3lame --disable-libaom --enable-libass --disable-libbluray --disable-libbs2b --disable-libdc1394 --enable-libdrm --enable-iconv --disable-libjack --disable-libmfx --disable-libmodplug --disable-libmysofa --enable-libopus --disable-librsvg --enable-libsrt --enable-libssh --disable-libtensorflow --enable-libtheora --enable-libv4l2 --enable-v4l2-m2m --enable-vaapi --disable-vdpau --enable-libvorbis --disable-libvmaf --enable-libvpx --disable-libwebp --disable-xlib --disable-libxcb --disable-libxcb-shm --disable-libxcb-xfixes --disable-libxcb-shape --disable-libxml2 --enable-lzma --enable-cuvid --enable-nvdec --enable-nvenc --disable-openal --disable-opencl --disable-libopencore-amrnb --disable-opengl --disable-libopenh264 --disable-libopenjpeg --disable-libopenmpt --disable-libpulse --disable-librav1e --enable-libsvtav1 --disable-librtmp --disable-sdl2 --enable-libsoxr --enable-libspeex --disable-libvidstab --disable-libvo-amrwbenc --enable-libx264 --enable-libx265 --disable-libxavs --enable-libxvid --disable-libzmq --enable-libzimg --enable-zlib --disable-vulkan --disable-libglslang --disable-libsmbclient --disable-debug --enable-optimizations --disable-extra-warnings --disable-stripping
       > ERROR: cuvid requested, but not all dependencies are satisfied: ffnvcodec
       >
       > If you think configure made a mistake, make sure you are using the latest
       > version from Git.  If the latest version fails, report the problem to the
       ><EMAIL_ADDRESS>mailing list or IRC #ffmpeg on irc.libera.chat.
       > Include the log file "ffbuild/config.log" produced by configure as this will help
       > solve the problem.
       For full logs, run 'nix log /nix/store/nl2h321i26ccgmdbfwi9br1qh0m4dgkk-ffmpeg-headless-6.1.drv'.

Does it build for you?

Please remove the merge commit from the PR. It could cause issues if a merge conflict is on it.

Of course. Thanks for calling this out, @SuperSandro2000, the merge commit has now been removed.

The eval failure is probably because texinfo is so deep into the tree and causes to many rebuilds.
@ofborg eval

Friendly ping to @AndersonTorres and @SuperSandro2000 on this 🙂

Let's send it to the Discourse thread.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3208

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

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

@afh please add link to Diff / change log to commit message and PR, eg 44bee06d90d444d26903fb967811f5c0b29c2ab1

Sure think @kirillrdy, the commit message and PR description have been updated.
Not that the diff link seems to work, but stalls for me after some time, not sure if the diff is too large…

Sure thing, @kirillrdy, the commit message and PR description have been updated.
Not that the diff link seems to work, but stalls for me after some time, not sure if the diff is too large…

for major releases link to chagelog/release log is sufficient. as you stated, if diff is too large, then its probably not that useful

@infinisil sorry to bother you, can you recommend what to do about by-name check in this case ?

Would moving texinfo into the pkgs/by-name tree be something people would find acceptable? I'd be happy to draft a PR, if folks see value in it.

No, not good. Use this instead:
https://github.com/NixOS/nixpkgs/pull/287918
https://github.com/NixOS/nixpkgs/pull/287918#issuecomment-1939243084

Very interesting, @AndersonTorres, thanks for sharing. Will this also address/fix the by-name check failures?

Also could you provide more context, please, on why moving texinfo into the by-name tree is bad? I'm genuinely curious.

@AndersonTorres, I have some local changes for texinfo in the same vein as the PRs you referenced. Should this PR be re-used for that or would a new (draft?) PR be more appropriate?

Eager to learn more about nixpkgs and motivated by @AndersonTorres' comment I drafted #289690. Since you, @AndersonTorres and @kirillrdy, have been so kind to share your knowledge and expertise on this PR recently, maybe you'd like to leave a feedback on the draft PR as well; I'd appreciate it greatly.

Closing as #289690 got merged.


setup-dev issues

Opening a new issue based on https://github.com/PRQL/prql/issues/2282#issuecomment-1599423029
@khoa165 do you want to try running brew install npm? I saw the same logs that you pointed out. It's possible that very old versions of npm handled paths differently.
We do test the Taskfile, and it runs fine on my system — so it likely a versioning issue rather than a problem with the Taskfile itself.

It may be necessary to mention in the documentation the required version of rustc, Node.js, etc.

We do try and install npm with brew but only if it can't be found at all (https://github.com/PRQL/prql/blob/baf3ba7dc21005c56c0cbe625d9f3ad2d270c77d/Taskfile.yml#L145).
Possibly we need to check the version too — I can add that check if it indeed is the cause of @khoa165's issue.
An automated check is more reliable and less overhead for the user, relative to adding docs — so let's default to that if we can...

That said, I am concerned that implicitly using the brew command may not be good manners (at least for me it is quite surprising that something will be installed implicitly via the brew command).
And of course, the brew command can only be executed on macOS and amd64 Linux.
I think it would make sense to add a version check to the task of running npm.

That said, I am concerned that implicitly using the brew command may not be good manners (at least for me it is quite surprising that something will be installed implicitly via the brew command).

Yeah, I think this is relevant. It's a difficult balance to strike — for example it only suggests vscode extensions at https://github.com/PRQL/prql/blob/baf3ba7dc21005c56c0cbe625d9f3ad2d270c77d/Taskfile.yml#L53.
We could do the same with brew dependencies, only suggesting — I would be open to that.
I had thought of brew dependencies similar to the cargo tools — that generally it's fine to add things, and brew doesn't support old versions, so it's fine to upgrade things. But maybe this is too aggressive...

Hi @max-sixty, afer I did npm install -g npm@latest and then re-run task setup-dev and then run task run-playground, it works, I could see the playground on localhost!!!! It must have been b/c of npm version then. My NPM was previously 6.14.14 and it's now 9.7.1

Also I have another question, are we only able to run either playground or book at once and not both? I opened 2 tabs of terminal and ran task run-playground first (which works) and then task run-book (which works but now playground does not work). Is it b/c they use the same port?

OK great! The new Taskfile will not proceed on an old version of npm; hopefully that should mean we don't hit this again...

Is it b/c they use the same port?

Possibly. It's worth trying to change the ports in the taskfile, re-running, and seeing whether that helps...

(closing but feel free to ask any more questions here)


[BUG] Longhorn manager find_kubelet_cmdline causing 100 % CPU Usage

Describe the bug
I currently have high CPU usage on one node of my cluster. The CPU usage seems to be caused by the call to the find_kubelet_cmdline function in longhorn-manager.
The issue arised after i upgraded from K3S 21.1.3 to 21.1.4
To Reproduce
Don't really know what causes the issue.
A reboot didn't solved it.

Expected behavior
No high cpu usage.
Log
Didn't find anything useful in the longhorn-manager log.
longhorn-support-bundle_4e91f477-6e47-4da1-9d1b-0b295235e9ca_2021-08-24T19-39-28Z.zip
Environment:

Longhorn version: 1.1.2

Installation method: Helm

Kubernetes distro: K3S 1.21.4

Number of management node in the cluster: 2
Number of worker node in the cluster: 0

Node config

OS: Ubuntu Server 21.04
CPU per node: 4
Memory per node: 4GB
Disk type: USB (64GB OS & 256GB Longhorn)
Network bandwidth between the nodes: 1GBit

Underlying Infrastructure: Baremetal Raspberry Pi 4

Number of Longhorn volumes in the cluster: 8

Additional Context:
lsof of the running process:
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF    NODE NAME
bash    69511 root  cwd    DIR  0,289     4096 2102851 /
bash    69511 root  rtd    DIR  0,289     4096 2102851 /
bash    69511 root  txt    REG  0,289  1046904 2636050 /bin/bash
bash    69511 root  mem    REG  0,289          2637342 /lib/aarch64-linux-gnu/libnss_files-2.27.so (stat: No such file or directory)
bash    69511 root  mem    REG  0,289          2637336 /lib/aarch64-linux-gnu/libnsl-2.27.so (stat: No such file or directory)
bash    69511 root  mem    REG  0,289          2637346 /lib/aarch64-linux-gnu/libnss_nis-2.27.so (stat: No such file or directory)
bash    69511 root  mem    REG  0,289          2637338 /lib/aarch64-linux-gnu/libnss_compat-2.27.so (stat: No such file or directory)
bash    69511 root  mem    REG  0,289          2637302 /lib/aarch64-linux-gnu/libc-2.27.so (stat: No such file or directory)
bash    69511 root  mem    REG  0,289          2637312 /lib/aarch64-linux-gnu/libdl-2.27.so (stat: No such file or directory)
bash    69511 root  mem    REG  0,289          2637380 /lib/aarch64-linux-gnu/libtinfo.so.5.9 (stat: No such file or directory)
bash    69511 root  mem    REG  0,289          2637284 /lib/aarch64-linux-gnu/ld-2.27.so (stat: No such file or directory)
bash    69511 root    0u   CHR    1,3      0t0     313 /dev/null
bash    69511 root    1w  FIFO   0,12      0t0  249564 pipe
bash    69511 root    2w  FIFO   0,12      0t0  248284 pipe
bash    69511 root    3r  FIFO   0,12      0t0  251999 pipe
bash    69511 root    4r  FIFO   0,12      0t0  251998 pipe
bash    69511 root    5w  FIFO   0,12      0t0  251999 pipe

strace doesn't return anything.

After deleting the pod, the pod got stuck in terminating. After rebooting the node, the problem seems to be resolved.

I will close this for now, please feel free to re-open if you are able to reproduce or encounter the issue again.


Adding search bar animation

Please assign me this issue @pranjay-poddar @MohitGupta121

@MohitGupta121 now you can review it and label it.


Resolve file directory to resource path

I have the following:
/* foo.scss */
@import './bar.scss';
/* ... */

/* bar.scss */
@import '~module/variables`;
/* ... */

/* ../../node_modules/module/_variables.scss */
/* ... */

I get the following error:
Error:
@import '~module/variables';
       ^
      File to import not found or unreadable: ~module/variables/Users/jerrysu/foo/src/styles/
      in /Users/jerrysu/foo/src/styles/bar.scss (line 2, column 9)
    at options.error (/Users/jerrysu/foo/node_modules/node-sass/lib/index.js:277:32)

By modifying this code so that the directory context is resolved from the resource path, I no longer have these issues with these sort of dependencies.

Thx for your pull-request.
However, I don't understand why this is necessary. We already have a test case which covers this use-case. Why doesn't it work for you?
Could you add a test that demonstrates the problem?

I'll see if I can put together a test to demonstrate this issue. Sorry if my original description of the problem was vague, I wasn't sure exactly how to explain it.
The difference between the test case you pointed out and my own case is that the module is being imported from a dependency of a file that I imported.
While debugging the issue that I was having, I noticed that the output of fileToDirContext for the dependencies of imported files was returning the path under the root directory. So, for example, if my root directory was ./src and I wanted the directory context of ./src/components/Button.scss, fileToDirContext returned just components. If Button.scss tried to import a file from node_modules using ~, it did not resolve correctly without the change that I made.

Any progress on this?

@jhnns @jerrysu I think a problem I have is related to this - I'm not sure. Sorry if it's not - in that case, I'll probably delete this comment and open up a new issue. But I believe it has something to do with this and I didn't find another existing issue which sounds like it's related.
Example
_inuitCss.scss
// Settings
@import "~inuit-defaults";
@import "~inuit-responsive-settings";

// Tools
@import "~inuit-functions";
@import "~inuit-mixins";
@import "~inuit-responsive-tools";

.. which is imported by another SCSS file. But.. it fails transpiling:
Module build failed: ModuleBuildError: Module build failed:
@import "~inuit-defaults";
^
      File to import not found or unreadable: ~inuit-defaults
Parent style sheet: /home/nico/workspace/web-boilerplate/src/components/app/_inuitCss.scss
      in /home/nico/workspace/web-boilerplate/src/components/app/_inuitCss.scss (line 8, column 1)
    at DependenciesBlock.onModuleBuildFailed (/home/nico/workspace/web-boilerplate/node_modules/webpack-core/lib/NormalModuleMixin.js:315:19)
    at nextLoader (/home/nico/workspace/web-boilerplate/node_modules/webpack-core/lib/NormalModuleMixin.js:270:31)
    at /home/nico/workspace/web-boilerplate/node_modules/webpack-core/lib/NormalModuleMixin.js:292:15
    at context.callback (/home/nico/workspace/web-boilerplate/node_modules/webpack-core/lib/NormalModuleMixin.js:148:14)
    at Object.onRender (/home/nico/workspace/web-boilerplate/node_modules/sass-loader/index.js:272:13)
    at /home/nico/workspace/web-boilerplate/node_modules/async/lib/async.js:906:35
    at _arrayEach (/home/nico/workspace/web-boilerplate/node_modules/async/lib/async.js:85:13)
    at Object.<anonymous> (/home/nico/workspace/web-boilerplate/node_modules/async/lib/async.js:898:17)
    at Object.callback (/home/nico/workspace/web-boilerplate/node_modules/async/lib/async.js:44:16)
    at options.error (/home/nico/workspace/web-boilerplate/node_modules/node-sass/lib/index.js:280:32)
 @ ./src/components/app/index.js 3:0-21

.. but as soon as I change line two in _inuitCss.scss from @import "~inuit-defaults"; into @import "~inuit-defaults/_settings.defaults";, it works.
No matter what I do, I have to specify the module + the file I want to import on the first import in this file, otherwise it fails. It doesn't matter which imported node module is the first, it just fails if I do not specify the file directly.
The repository where you can test this yourself can be found here: https://github.com/nightgrey/web-boilerplate
I'm using node version 5.9.1, npm version 3.7.3, sass loader 3.2.0 on Ubuntu 15.10.  I hope it's not just a webpack configuration problem or something.

@jerrysu is module a dependency that is referenced in your package.json?  You even made a pull request - thank you very much!

@jhnns: sorry, haven't had time to look into writing the test case. module is a dependency referenced in package.json. In many of the broken cases, they reference a pancake installed from a GitHub repo if that makes a difference.

What is a pancake in this context? :grin:

Since it's unclear what this actually about, I'll close it for now


Show delivery failure reasons if provided by Mailgun

This PR was successfully deployed to production by CircleCI build 180 at 2017-05-02 10:06 BST.


[WIP] Add test for initThisClass from a generic method on a nongeneric type

This doesn't need a runtime lookup, but RyuJIT is asking for one.
The test is not expected to pass, but I don't want to forget it. It needs a RyuJIT change.

This will be checked in through #2849.


feat(gatsby-theme-docz): create MainContainer component

Description
There were no way to target the main container, where the content is. With this, you can shadow this component without impacting any other component.

👍 Released in v2.3.0-alpha.11 or docz@next


Not Refreshing when using OctoPrint 1.3.11

Since OctoPrint upgraded to 1.3.11 I’m not getting any statistics regarding the print. All I get is video feed with nozzle and bed temps.

See #175

My apologies. Should’ve searched the issues first. It happened straight after the upgrade, so I figured they’d messed with something.
Thanks for the super fast reply.

This is a valid error that was introduced when this ticket was resolved in OctoPrint. https://github.com/foosel/OctoPrint/issues/3024
You can use the workaround mentioned by @jollino until I release a new version with the proper fix. OctoPrint increased the security in the websockets area (see CORS) so now OctoPod is running into an issue. I solved it locally but need to test other things before the new release. Will see if I can push new version by the end of this weekend.


sort by len(field) produces incorrect output

If I tried to sort by len(field), it doesn't work right...
% cat bug.zson
{u:|["ACME Hotels","Smithsonian"]|}
{u:|["Lakers"]|}
{u:|["MOMA"]|}
{u:|["Disney","Universal"]|}
{u:|["Dell"]|}
{u:|["FedEx","Staples","Home Depot"]|}
{u:|["DHS","IRS"]|}
{u:|["Fidelity"]|}
{u:|["Exxon","Shell"]|}
% zq "sort len(u)" bug.zson
{u:|["Dell"]|}
{u:|["Fidelity"]|}
{u:|["Exxon","Shell"]|}
{u:|["Lakers"]|}
{u:|["MOMA"]|}
{u:|["Disney","Universal"]|}
{u:|["FedEx","Staples","Home Depot"]|}
{u:|["DHS","IRS"]|}
{u:|["ACME Hotels","Smithsonian"]|}

But if I do this, it works
% zq "x:=len(u) | sort x | drop x" bug.zson
{u:|["Dell"]|}
{u:|["Fidelity"]|}
{u:|["Lakers"]|}
{u:|["MOMA"]|}
{u:|["Exxon","Shell"]|}
{u:|["Disney","Universal"]|}
{u:|["DHS","IRS"]|}
{u:|["ACME Hotels","Smithsonian"]|}
{u:|["FedEx","Staples","Home Depot"]|}

Also, the order below seems sensible but we may want to revisit and confirm the natural-order semantics of Zed sets...
% zq "sort u" bug.zson
{u:|["ACME Hotels","Smithsonian"]|}
{u:|["DHS","IRS"]|}
{u:|["Dell"]|}
{u:|["Disney","Universal"]|}
{u:|["Exxon","Shell"]|}
{u:|["FedEx","Staples","Home Depot"]|}
{u:|["Fidelity"]|}
{u:|["Lakers"]|}
{u:|["MOMA"]|}

I've verified in Zed commit 5c4868d that the original repro steps now produce output ordered by the length of the sets.
$ zq -version
Version: v0.30.0-5-g5c4868de

$ zq "sort len(u)" bug.zson
{u:|["Lakers"]|}
{u:|["MOMA"]|}
{u:|["Dell"]|}
{u:|["Fidelity"]|}
{u:|["ACME Hotels","Smithsonian"]|}
{u:|["Disney","Universal"]|}
{u:|["DHS","IRS"]|}
{u:|["Exxon","Shell"]|}
{u:|["FedEx","Staples","Home Depot"]|}

For whatever reason, I can't seem to reproduce the order among the sets of the same length that @mccanne showed above, even using the variation on the query he showed.
$ zq "x:=len(u) | sort x | drop x" bug.zson{u:|["Lakers"]|}
{u:|["MOMA"]|}
{u:|["Dell"]|}
{u:|["Fidelity"]|}
{u:|["ACME Hotels","Smithsonian"]|}
{u:|["Disney","Universal"]|}
{u:|["DHS","IRS"]|}
{u:|["Exxon","Shell"]|}
{u:|["FedEx","Staples","Home Depot"]|}

In fact, I went back to some Zed commits from around five days ago when this issue was opened and that's the order I can reproduce with those as well. So I'm not sure how to explain that part of the original repro.
In any case, it does seem like we've addressed the primary issue, and as @mccanne notes above, we could reconsider the natural order semantics of sets as a separate topic if we choose.
Thanks @mccanne!


Misinformation in the "Python library usage" documentation section

Hello gaetano-guerriero, today I just started using pypjlink and found out that command line utility works fine for my Vivitek projector, but when I tried using Python library, it raises assert in the protocol.py, in the parse_response function, on the "assert header == '%'" line. After spending some time I understood that the difference between command line interface and the way I used library is that CLI calls "authenticate" method on Projector instance before issuing command requested by user. But the "Python library usage" section in documentation both on GitHub and PyPi says nothing about this. So it would be great to fix the "Python library usage" documentation section and mention the "authenticate" call in it.

thank's for writing this down. I can confirm the behaviour you describe with a Mitsubishi projector. Calling of .authenticate() is needed always, even if no password is set.

I've opened a PR https://github.com/gaetano-guerriero/pypjlink/pull/3 to fix this and some other small issues in the readme.


test failed

Dear Lucas,
I made a change for the package, to include the change of APIs and input table structure https://github.com/xapple/waste_flow/commit/ec639cf155867ee1bbf7321b778412341ede0401.
Unfortunately the tests are not working in the CI https://github.com/xapple/waste_flow/actions/runs/11182949528/job/31090390997, but I'm not able to reproduce the issue since on my local machine they have been passed. If you have time, you may look at it.
Thanks a lot,
Selene

In the setup.py file, I see that pandas is fixed to an old version (1.5.3) while numpy is not fixed to any version.
Then using these specific requirements, the package is installed with pip which does not "solve" environments for compatibility issues such as miniconda does.
So either:

Upgrade and use latest version of pandas.
Downgrade numpy to an old version that used to work.
Use conda for the github actions testing.


python312Packages.tesserocr: 2.6.3 -> 2.7.0

https://github.com/sirfz/tesserocr/releases/tag/v2.7.0
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

@mweinelt Will this be ok for #325541?

No idea, it was reverted because the substitution did not longer apply. I fixed that and here we are.
If an apps needs an older version it can always use packageOverrides fwiw.


Running Linux program Android Application

How to run an Android application and run a Linux application? After I finished the installation, I logged into the Google account system and did not automatically install anything except plug-ins I have in Google,

You can't install Android or Linux apps afaik. This is just regular Chromium, and right now there aren't any plans for Android app support.

Maybe we can provide crostini in the future for rpi4. But I don't think it is an attractive idea for rpi4.

@au-top  @Jerry8538   https://releases.fydeos.io/11.4/rpi4-fydeos you may want to check out this one, it's FydeOS for You, not Chromium OS, and it supports Android and Linux.

@au-top  @Jerry8538   https://releases.fydeos.io/11.4/rpi4-fydeos you may want to check out this one, it's FydeOS for You, not Chromium OS, and it supports Android and Linux.

@fydeos-alpha That's amazing! I have a few questions, however. How exactly do I use Android apps on FydeOS? It doesn't mention that anywhere, and what exactly does it support as of now, like does the GPU work, and WiFi etc. If everything works correctly, I might just use FydeOS, because running Android apps is pretty sweet!

@fydeos-alpha That's amazing! I have a few questions, however. How exactly do I use Android apps on FydeOS? It doesn't mention that anywhere, and what exactly does it support as of now, like does the GPU work, and WiFi etc. If everything works correctly, I might just use FydeOS, because running Android apps is pretty sweet!

@Jerry8538  I believe this video has got all your questions explained, and perhaps this one too.

@Jerry8538  I believe this video has got all your questions explained, and perhaps this one too.

use balenaEtcher out data a fail ,  I tested it many times , Is there a problem like mine ?

use balenaEtcher out data a fail ,  I tested it many times , Is there a problem like mine ?

I checked that sha256sum is correct

I checked that sha256sum is correct

run etcher as Administrator if you are using Windows. Otherwise, try
Raspberry Pi Imager
On Tue, 19 Jan 2021 at 18:51, autop<EMAIL_ADDRESS>wrote:

I checked that sha256sum is correct
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FydeOS/chromium_os-raspberry_pi/issues/99#issuecomment-762763141,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAJK3JTQ5L34KGVLZP4PSLS2VP2DANCNFSM4R734Q7Q
.

run etcher as Administrator if you are using Windows. Otherwise, try
Raspberry Pi Imager
On Tue, 19 Jan 2021 at 18:51, autop<EMAIL_ADDRESS>wrote:

I checked that sha256sum is correct
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FydeOS/chromium_os-raspberry_pi/issues/99#issuecomment-762763141,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAJK3JTQ5L34KGVLZP4PSLS2VP2DANCNFSM4R734Q7Q
.

The Mac OS I borrowed was successfully written, but after I inserted the raspberry pie and connected it to the HDMI monitor, I successfully displayed the rainbow test picture of raspberry pie when it was turned on, and then there was no picture. Later, only the monitor indicated that there was no signal. The hard disk light (green light) of my raspberry pie flickered from time to time. I tried to restart the power after 40 minutes, but the problem remained, My raspberry pie 4b4g

The Mac OS I borrowed was successfully written, but after I inserted the raspberry pie and connected it to the HDMI monitor, I successfully displayed the rainbow test picture of raspberry pie when it was turned on, and then there was no picture. Later, only the monitor indicated that there was no signal. The hard disk light (green light) of my raspberry pie flickered from time to time. I tried to restart the power after 40 minutes, but the problem remained, My raspberry pie 4b4g

Seems the kms graphics mode isn't compatible with your monitor. Try editing
the config.txt and change it to fake-kms mode to achieve some extra
compatibility:
https://github.com/FydeOS/chromium_os-raspberry_pi/issues/16#issuecomment-586219347
On Tue, 19 Jan 2021 at 22:24, autop<EMAIL_ADDRESS>wrote:

The Mac OS I borrowed was successfully written, but after I inserted the
raspberry pie and connected it to the HDMI monitor, I successfully
displayed the rainbow test picture of raspberry pie when it was turned on,
and then there was no picture. Later, only the monitor indicated that there
was no signal. The hard disk light (green light) of my raspberry pie
flickered from time to time. I tried to restart the power after 40 minutes,
but the problem remained, My raspberry pie 4b4g
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FydeOS/chromium_os-raspberry_pi/issues/99#issuecomment-762872120,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAJK3OVBL7FZTGGYQ5O2LTS2WI2TANCNFSM4R734Q7Q
.

Seems the kms graphics mode isn't compatible with your monitor. Try editing
the config.txt and change it to fake-kms mode to achieve some extra
compatibility:
https://github.com/FydeOS/chromium_os-raspberry_pi/issues/16#issuecomment-586219347
On Tue, 19 Jan 2021 at 22:24, autop<EMAIL_ADDRESS>wrote:

The Mac OS I borrowed was successfully written, but after I inserted the
raspberry pie and connected it to the HDMI monitor, I successfully
displayed the rainbow test picture of raspberry pie when it was turned on,
and then there was no picture. Later, only the monitor indicated that there
was no signal. The hard disk light (green light) of my raspberry pie
flickered from time to time. I tried to restart the power after 40 minutes,
but the problem remained, My raspberry pie 4b4g
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FydeOS/chromium_os-raspberry_pi/issues/99#issuecomment-762872120,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAJK3OVBL7FZTGGYQ5O2LTS2WI2TANCNFSM4R734Q7Q
.

@Jerry8538 I believe this video has got all your questions explained, and perhaps this one too.

Ah, my bad for not looking it up first, but thanks a lot for linking them!

@Jerry8538 I believe this video has got all your questions explained, and perhaps this one too.

Ah, my bad for not looking it up first, but thanks a lot for linking them!

Maybe we can provide crostini in the future for rpi4. But I don't think it is an attractive idea for rpi4.

Please provide. I need it


Strange ALTER TABLE issues in e_sqlite3

I feel like I'm going crazy, but the following code fails:
using System;
using System.Diagnostics;

using static SQLitePCL.raw;

class Program
{
    static void Main()
    {
        int rc;
        SQLitePCL.Batteries_V2.Init();

        rc = sqlite3_open(":memory:", out var db);
        Debug.Assert(rc == SQLITE_OK);

        rc = sqlite3_exec(db, "CREATE TABLE People ( Id INTEGER NOT NULL )");
        Debug.Assert(rc == SQLITE_OK);

        // SQLITE_ERROR: Cannot add a column with non-constant default
        rc = sqlite3_exec(db, "ALTER TABLE People ADD Sum INTEGER NULL DEFAULT(1 + 2)");
        if (rc != SQLITE_OK)
            Console.WriteLine(sqlite3_errmsg(db).utf8_to_string());
    }
}

If I run the same SQL inside sqlite3.exe (using the same SQLite version), it succeeds. Any ideas?

Ditto for stored computed columns:
-- SQLITE_ERROR: cannot add a STORED column
ALTER TABLE People ADD Sum AS (X + Y) STORED;

I tried running the first example above (DEFAULT (1+2)), with both SQLitePCLRaw and with sqlite3.exe.  I get the same error (Cannot add a column with non-constant default) both ways.

Same for (X + Y) STORED -- I get "cannot add a STORED column" both ways of running it.

So I have gone crazy... 🥴

lol 🤷♂

Ha. That's 3.32.2 but I'm still on 3.31.1.  Maybe that's the difference.

Ah, that makes sense. I probably misread it as 3.32.1 when I "used the same version"

I don't see anything in the sqlite release history bullets that would suggest a difference.
I'll try 3.32.2 and see what happens.

Yeah, I've been digging through their issue tracker too. Just one of those "fixed by coincidence" bugs. Maybe in 3.32.1 under "Other minor compiler-warning fixes and whatnot."

Confirmed. Repros on 3.31.1 but not 3.32.0. External

Confirmed here as well -- 3.32.3 does not show the problem.


Make error message more verbose when creating a repo

I recently had some issues which could have been easily found if the error message was more verbose.
Before:

requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://huggingface.co/api/repos/create

After:

requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://huggingface.co/api/repos/create - Only regular characters and '-', '_', '.' accepted

r.json() would already raise an error if not a json response.
In terms of speed, the method uses simplejson which is supposed to be very fast.


linux-hikey960: move to 4.13rc kernel

4.9 doesn't build and doesn't ship image and dtb, so move to 4.13rc
Signed-off-by: Koen Kooi<EMAIL_ADDRESS>

@docularxu something wrong with the kernel. 4.9 is now broken and we lost the last working commit. Which kernel should be used and you're commited to keep updated?

I think hikey960_defconfig is for android and defconfig should be used instead. @docularxu will have to confirm.

@vchong hikey960_defconfig is the config that Guodong told us to use. If things have changed, indeed I expect @docularxu to have informed us before the breakage.

@fboudra
For v4.9 based kernel, it is here:
https://github.com/96boards-hikey/linux/commits/hikey960-v4.9
For mainline based kernel, it's in this branch:
https://github.com/96boards-hikey/linux/commits/hikey960-upstream-rebase
I will maintain both of them.
'hikey960-upstream-rebase' will be rebased to latest -rc kernels.

@docularxu on your last rebase, hikey960-v4.9 with hikey960_defconfig is broken. See also https://bugs.96boards.org/show_bug.cgi?id=562

On Thu, Aug 3, 2017 at 5:03 PM, vchong<EMAIL_ADDRESS>wrote:

I think hikey960_defconfig is for android and defconfig should be used
instead. @docularxu https://github.com/docularxu will have to confirm.

That's true.
For generic linux, should use defconfig
-Guodong
—

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/96boards/meta-96boards/pull/170#issuecomment-319911829,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHnKpzqMFexD-2WSq79O_4OqwT9zKLqeks5sUYzEgaJpZM4OsFeo
.

@docularxu @koenkooi let's switch to defconfig then, instead of hikey960_defconfig. I'm pretty sure you told me to use hikey960_defconfig when I set up the build and it was working fine on Linux until recently.
@docularxu would you also tag the tree after your rebase to avoid to lose the commit that has successfully built. for example, we don't have e74c7e1b28b13056e7fb3c6d8901ba708efbec8d anymore

fixed in https://github.com/96boards/meta-96boards/commit/bed50a97ab5dd53899f54089468e716b616678e0

On Thu, Aug 3, 2017 at 8:17 PM, Fathi Boudra<EMAIL_ADDRESS>wrote:

@docularxu https://github.com/docularxu @koenkooi
https://github.com/koenkooi let's switch to defconfig then, instead of
hikey960_defconfig. I'm pretty sure you told me to use hikey960_defconfig
when I set up the build and it was working fine on Linux until recently.
@docularxu https://github.com/docularxu would you also tag the tree
after your rebase to avoid to lose the commit that has successfully built.
for example, we don't have e74c7e1b28b13056e7fb3c6d8901ba708efbec8d
anymore

I can do that if there is a need.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/96boards/meta-96boards/pull/170#issuecomment-319952471,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHnKp_Dj80rDlke6cMr3PTLAQdNkaRN5ks5sUbpigaJpZM4OsFeo
.

@docularxu yes, please. It will help to keep the build reproducible. The recipe is static and we explicitely set the commit. If it goes away, it's broken.

@docularxu the branch hikey960-v4.9 with defconfig failed to build:
| drivers/built-in.o: In function `kbase_ipa_model_ops_find.isra.0':
| debugfs.c:(.text+0x18e4c4): undefined reference to `kbase_g71_ipa_model_ops'
| debugfs.c:(.text+0x18e4c4): relocation truncated to fit: R_AARCH64_ADR_PREL_PG_HI21 against undefined symbol `kbase_g71_ipa_model_ops'
| debugfs.c:(.text+0x18e4c8): undefined reference to `kbase_g71_ipa_model_ops'
| debugfs.c:(.text+0x18e4d0): undefined reference to `kbase_g71_ipa_model_ops'
| /srv/oe/build/tmp-rpb-glibc/work-shared/hikey960/kernel-source/Makefile:969: recipe for target 'vmlinux' failed
| make[2]: *** [vmlinux] Error 1
| Makefile:150: recipe for target 'sub-make' failed
| make[1]: *** [sub-make] Error 2
| Makefile:24: recipe for target '__sub-make' failed
| make: *** [__sub-make] Error 2


Disable font family optimisation

Ref: https://twitter.com/m_strehl/status/620563733362921472
In relation to https://github.com/ben-eb/cssnano/issues/31, postcss-font-family should be given the font namespace so that it may be disabled.

Fixed in https://github.com/ben-eb/cssnano/commit/8ea2ed82f74e59c37251273ef7e432e7e50bfed6.


[FEATURE] Get-PnPDeletedTenantSite Restore-PnPDeletedTenantSite Remove-PnPDeletedTenantSite Request

Is your feature request related to a problem? Please describe.
It looks like currently there is no way to retrieve list of deleted sites using PnP.PowerShell module. At least this is something I am unable to locate:

Describe the solution you'd like
We need some kind of alternative to Get-SPODeletedSite and Restore-SPODeletedSite Remove-SPODeletedSite cmdlets:
https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/get-spodeletedsite?view=sharepoint-ps
https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/restore-spodeletedsite?view=sharepoint-ps
https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/remove-spodeletedsite?view=sharepoint-ps

Describe alternatives you've considered
The only alternatives available are Get-SPODeletedSite and Restore-SPODeletedSite

Added the commands, please check tomorrow.
Thanks !

Oh wow, that was lightning fast!
Thanks a lot @garrytrinder , you rock!


Competitive CTF Mode server crash on dropship

From my understanding, dropship shouldn't be in competitive CTF in the first place, currently, it is.
After the animation of the dropship, the server crashed. Here are the logs:
mature-oracle.log.zip

Drop ship at the start of match or evac ship?

Drop ship at the start of match or evac ship?

evac ship, sorry

Closing as stale


Record max depth reached in CFG construction

Add this information to the statistics in the DFS.
Add the result to the title of the CFG to indicate the size of the deepest branch.

I think this is done?


Reduced energy consumption

Greetings, thanks for such a useful code.
I'm trying to use it on the LoRaDuino V1.2 board. (Https://www.electrodragon.com/product/atmega328p-arduino-plus-lora-sx1278-board-loraduino/)
I want to create a battery-powered receiving device.
But in order to minimize current consumption, I want my MCU to be in sleep mode, and the HPDTeK HPD14A V1.2 receiver (probably SX1278 Lora or RF95) was in standby mode and, upon detecting the preamble, woke the MCU, through an interrupt, process the incoming packet data in the future switch back to low consumption mode.
I added the MCU sleep function to the code (ReceiveInterrupt Sample), it works great. I successfully send the MCU to sleep (((LowPower.powerDown (SLEEP_FOREVER, ADC_OFF, BOD_OFF);)), by interrupt DIO0 - the MCU wakes up the data and then falls asleep. But in this mode the LoRaDuino V1.2 board consumes about 15 mA. For me 15 mA is a lot, and I also want to reduce consumption ..
When I call the lora.standby () function after the MCU I send to sleep by interrupt (LowPower.powerDown (SLEEP_FOREVER, ADC_OFF, BOD_OFF);), the board consumes about 5 mA, which is much better. But when receiving new packets, the interruption from the DIO0 or DIO1 pins does not go to the MCU and is not activated for processing ...
When I use the lora.scanChannel () function; (which reads the preamble) the data is lost and I cannot read them, and I do not understand how the MCU can be sent to sleep with this function.
Tell me, please, how with lora.standby () get the “CAD Detect” interrupt on DIO0 or DIO1?
If it is not difficult, you can make an example for this mode, I think it will be useful for many. Thanks again for the help and understanding.
ReceiveInterrupt.zip

By calling lora.standby(), you put the SX1278 chip into standby (idle) mode, which stops any ongoing operations, including channel activity detection. That's the reason for the current draw droppping from
15 mA to 5 mA.
From SX1278 datasheet, page 45, you can see that current draw is about 11 - 14 mA when in CAD mode. The way I see it, the only way to decrease power consumption in CAD is to lower the bandwidth.

Similar request, if possible could you please make an example for CAD driven interrupt to wake up MCU from sleep. Many Thanks

Oh, thanks for the quick reply. But this consumption is in continuous
reception mode (Full Rx). And I mean for the mode which is described in
clause 7.3.1. Wake on Preamble Interrupt, 7.3.2. Wake on SyncAddress
Interrupt (On page 117).
чт, 28 Фев 2019, 21:45 Jan Gromeš<EMAIL_ADDRESS>
By calling lora.standby(), you put the SX1278 chip into standby (idle)
mode, which stops any ongoing operations, including channel activity
detection. That's the reason for the current draw droppping from
15 mA to 5 mA.
From SX1278 datasheet
https://cdn-shop.adafruit.com/product-files/3179/sx1276_77_78_79.pdf,
page 45, you can see that current draw is about 11 - 14 mA when in CAD
mode. The way I see it, the only way to decrease power consumption in CAD
is to lower the bandwidth.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jgromes/LoRaLib/issues/61#issuecomment-468410865, or mute
the thread
https://github.com/notifications/unsubscribe-auth/APN5_0AXCh055Phy7caG8Fw6BblSSsD4ks5vSDHIgaJpZM4bXkDN
.

I understand that for this mode in the library you need to configure the Sequencer registers - page 101, 102 (RegSeqConfig) and timers (as I understand RegTimerResol), after which DIO4 will trigger an interrupt, detecting the preamble as mentioned on page 118.

@divya0056 The examples are supposed to show how to use the library features, not what to use them for. Furthermore, different platforms might have different ways of putting the MCU to sleep and waking it up. It's just too broad to write a meaningful example.

@GusakIurii The sequencer you're refering to is used in FSK mode. However, channel activity detection can only be used in LoRa mode. Which one are you using? LoRa or FSK?

@GusakIurii Секвенсор, на который вы ссылаетесь, используется в режиме FSK. Однако обнаружение активности канала можно использовать только в режиме LoRa. Какой вы используете? ЛоРа или ФСК?

I plan to use the LoRa mode, but if in FSK mode you can achieve less consumption, then FSK mode can also be.
https://lowpowerlab.com/forum/low-power-techniques/lora-low-power-cad/ - It looks like the CAD mode in the RadioHead library has been implemented, which I need, but here the controller interrupt in time, why not interrupt it Preamble detection, I do not understand yet. Thanks for the help, I will deal with this example.

Greetings. The chip maker has a separate document (Reading channel RSSI during a CAD) where it says that: "Even if the end platform does not support antenna diversity, the energy saving made while reading the RSSI during a CAD made this technique essential for all battery powered systems.
2. Channel Activity Detection principles. The Channel Activity Detection mode is designed to detect a LoRa preamble on the radio channel with the best possible power efficiency. Once in CAD mode, the SX127x will perform a very quick scan of the band to detect a LoRa packet preamble."
those. This mode of operation is provided for LoRa modulation, and it is simply necessary for battery power.
Please help me figure it out and make a separate function in the library for working in CAD mode.

CAD mode is implemented - see the ChannelActivityDetection example.

I use two examples:
On the first module: "LoRaLib Transmit with Inerrupts Example"
On the second module: "LoRaLib Channel Activity Detection Example"
LoRa module default settings.
But the second module does not receive a single packet, the message is
constantly "channel is free!"
--
Regards, Iurii Gusak / С уважением, Юрий Гусак
Skype: GYura2010
Mob. KyivStar UA +38(068) 269-60-08
Mob. Life UA +38(093) 301-53-79
пн, 4 мар. 2019 г. в 15:18, Jan Gromeš<EMAIL_ADDRESS>
CAD mode is implemented - see the ChannelActivityDetection example.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jgromes/LoRaLib/issues/61#issuecomment-469249872, or mute
the thread
https://github.com/notifications/unsubscribe-auth/APN5_79BjcY6GxQ3IFRrtr2QAYwaqDMMks5vTR0ygaJpZM4bXkDN
.

I was unable to to verify this - my module can detect preamble fine in each transmission. I suggest you check the wiring (especially DIO0 and DIO1 pins).


WitchyBND

I notice this project currently uses Yabber, but would it not be better to use WitchyBND instead, since it's a continuation of Yabber that was made with ACVI in mind?

I second this

Yabber does the job just fine. Can you explain what you hope a switch to Witchy or any of the other tool would bring to the project?

I don't think bugs are much of a concern here since the only format that is touched is BND4 which is well established and hasn't changed in a long time.
The main reason why I wouldn't want to switch to Witchy is binary size. The latest Witchy release weighs in at 50MB, more than 50 times the size of Yabber. I wouldn't want to add this kind of bloat for little to no benefit at all.

Replacing the Yabber folder with WitchyBND and renaming the folder/executable accordingly seems to work just fine. Progress is being saved, and my emblem shows up properly.


AssetPack syntax sugar for static assets

Objective
Currently there's not a ton of boilerplate for loading assets, either using embedded_asset! or not. But this can still add up, and does especially in rendering code.
Solution

Add AssetPack trait and derive macro to wrap the pattern of "initialize some resources, potentially through embedded_asset!, and lazy load them when required"

#[derive(AssetPack)]
#[src_path = “bloom/my_custom_src”] //optionally override embedded asset root directory
struct BloomShaders {
  #[embedded("upscale.wgsl")] //lazy-loads upscale.wgsl as an embedded asset
  upscale_shader: Handle<Shader>,
  #[load("downscale.wgsl")] //lazy-loads downscale.wgsl from the default asset source
  downscale_shader: Handle<Shader>,
}

Limitations
Currently, all assets are loaded at once in Pack<T>::get() and never unloaded. This fits the need of rendering (and I assume other cases as well), where each shader is needed every frame and each pack is accessed (usually) all at once. Loading assets separately and unloading assets when unused would require a function-like proc-macro to be able to rewrite each struct field. For this PR I decided to continue with the simpler implementation.
Testing
I did some quick manual testing to make sure the macro worked as expected. Frankly, I'm not super familiar with macro testing or style for error reporting. Please let me know how to improve this!

Changelog

Add AssetPack trait and derive macro
Add AssetPackPlugin<T> to setup asset pack state
Add Pack<T> resource to wrap access to an AssetPack
Add GetPack<T> SystemParam so users don't have to pass in AssetServer themselves
Add asset_pack example and docs

Instead of AssetPackPlugin, you could just provide a register_asset_pack fn.

I tried running the example but got...
Apparently this is due to the weird workspace setup examples use. I just added a new top-level attribute to override the workspace root for embedded_asset!, so the example should be fixed :)

I haven't particularly encountered the pain that this is fixing yet, but my projects are not heavy on complex rendering or elaborate assets.

It's not an unbearable level of pain even, just the simple but pretty repetitive boilerplate of loading a fixed set of static assets into a resource handle and accessing them later. In terms of more tangible benefits, we lazy load assets (although not individually) and only refer to the path of the asset once rather than twice (potential for mismatch).

Decided to spin this off as a separate crate since there's not much attention here and any in-engine use seems far off (rendering refactor)


Update to 16MAR2022 build

Description
Use recent build with latest formats of localization and static B files.
amsua_metop-b is disabled in Variational and HofX applications to avoid an error during coefficient file reading.
Tests completed

[x] 3dvar_OIE120km_WarmStart
[x] 3denvar_OIE120km_WarmStart
[x] 3dvar_OIE120km_ColdStart
[x] 3denvar_O30kmIE60km_WarmStart
[x] eda_OIE120km_WarmStart

@metdyn, you'll see in this PR that amsua_metop-b has to be commented out in two places in order for the develop branch to pass all tests.

Hi @jjguerrette, the coefficient files that give the error when reading are related to the B? Is there a way that we can fix that?

All tests completed successfully.

Hi @jjguerrette, the coefficient files that give the error when reading are related to the B? Is there a way that we can fix that?

The issues is with amsua_metop-b. See here for a discussion.  We might not want to merge this PR until that fix is in place.  Then I can uncomment amsua_metop-b.

Thanks @jjguerrette for the information! I agree that it would be better to wait until that is fixed.

amsua_metop-b.SpcCoeff.bin.gz
FYI. I changed the version info in this file from 3 to 2.

Fix from @jamiebresch worked.  Tests passing. Ready for review.

Fix from @jamiebresch worked. Tests passing. Ready for review.

Great. I will test it.

FYI @ibanos90, maybe still waiting on some info in the UFO issue: JCSDA-internal/ufo#1929
Likely we do not need to wait though. I still have the old amsua_metop-b.SpcCoeff.bin file with internal version 3. So we can revert any time we need without a PR.

Ok, sounds good. I am approving the PR since I ran the tests and all succeeded.

Merging to get up-to-date with latest localization and covariance files.  If we need to use a newer build, somebody can submit a new PR.


Enforce types

Since version 4 will be a major, BC break is allowed.
What about changing interfaces (and, of course, implemented classes) to enforce types?
I mean adding real type hints and return types, that now are only suggested via phpdoc comments.

Better yesterday than today!

Merged into 4.x in https://github.com/ramsey/uuid/commit/3c6b7fe96e1605d161c82fa49c2d949d67534af5. Thanks!


Rc

:tada: This PR is included in version 8.0.0-rc.2 :tada:
The release is available on:

v8.0.0-rc.2
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 8.0.0-rc.3 :tada:
The release is available on:

v8.0.0-rc.3
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 8.0.0-rc.4 :tada:
The release is available on:

v8.0.0-rc.4
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 8.0.0-rc.5 :tada:
The release is available on:

v8.0.0-rc.5
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 8.0.0-rc.6 :tada:
The release is available on:

v8.0.0-rc.6
GitHub release

Your semantic-release bot :package::rocket:

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

v8.0.0
GitHub release

Your semantic-release bot :package::rocket:


Update IT translations

Harmonize IT terminology to use "trivellazione".
Removed Ticino from the list of unavailable cantons
@cype @nrohrbach

Wow... I did not notice how useless is the DIFF on this one. Probably due to the fact that I used the GitHub editor directly and it automatically prettyprinted the JSON, while it was not the case beforehand.
Should I try to fix the diff?


#415 errors

When I try to use negative keywords api, I am getting a 415 error.
But there is no workaround for this error in the documentation.
the link is : /v2/sp/campaignNegativeKeywords
My json data is:
[
  {
    "campaign_id":<PHONE_NUMBER>89297,
    "state": "enabled",
    "keywordText": "helloworld",
    "matchType": "negativeExact"
  }
]

Hi @24ChangQing, I believe this issue could be due to use the of the Content-Type header. Make sure it is set to application/json as seem in the curl sample here:
curl --location --request POST 'https://advertising-api.amazon.com/v2/sp/campaignNegativeKeywords' \
--header 'Amazon-Advertising-API-ClientId: amzn1.application-oa2-client.xxxxxxxxxxxxxxx' \
--header 'Authorization: Bearer Atza|xxxxxxxxxxxxxx' \
--header 'Amazon-Advertising-API-Scope: xxxxxxxxxxxxx' \
--header 'Content-Type: application/json' \
--data-raw '[
  {
    "campaignId":<PHONE_NUMBER>7055,
    "state": "enabled",
    "keywordText": "helloworld",
    "matchType": "negativeExact"
  }
]'

We are also working on enhancements to the documentation for Sponsored Products to provide more code samples, so look out for that soon!

@24ChangQing Let me know if you are still not able to make a successful call, otherwise I will close the issue for now.


chore: fixes restart without indy pool disconnect

What
Fixes: Unable to reinitialize agent once shut down #2135

@GHkrishna When is the pool close method called?

@GHkrishna When is the pool close method called?

Tha pool close from the IndyVDR is not initiated for now as it seems to be fixed first. We are just resting the pool variable, as if the pool was never initialised. But since we know we did, we'll reuse the same pool.

Yes @GHkrishna We have to close the pool. We can do that by subscribing to the stop$ subject.


Compiling fails if there is whitespace between style tag and brace

The following tag will fail, because the whitespace causes styled-jsx to think that the style tag has three children, when really two of them aren't real/are just empty whitespace.

Error:
ERROR in ./src/components/FullCalendar.js
Module build failed: SyntaxError: Expected a child under JSX Style tag, but got 3 (eg: )

  32 |
  33 | 		return (
> 34 |

     | 			^
  35 |

  36 |

I just kind of like the former syntax a little better personally, the style tags line up correctly this way at the expense of some horizontal space.
This is purely a preference quip, and since the workaround is very straightforward it's certainly not a priority, but it would be appreciated.
Thanks for everything! :hatching_chick:

This should absolutely be fixed. I was somewhat mindful about this situation while I was writing the transformation, but never wrote a test for it.

Fixed

Thanks! 👍


Replace chart images with Markdown

Images had a typo.
https://github.com/irresponsible/anarchy/issues/2

Awesome! Thank you :)


Remove 'no information' section underneath page number

Hi again,
Since I have updated to 1.1, I have noticed another thing pop up.
If you look in the picture, underneath the page number, it says no information, circled. Is there a way to remove that bit, seeing as it doesn't really serve a purpose, or make that one line customisable from the no_info parameter?
Thanks again.

This problem has now been fixed in 1.2 of the module (releasing later today hopefully).
Instead of shoing the "No information" label, if there is no bot description set the description will remain empty.
Example: (before)

Example: (after)

Oh, that's great, thank you very much!