Gradle should fail early with a reasonable error message on non-static nested classes

Current behavior
Given the following plugin:
public class FooPlugin implements Plugin<Project> {

    public class FooTask extends DefaultTask {
        @TaskAction
        public void foo() {
            System.out.println("foo!");
        }
    }

    @Override
    public void apply(Project project) {
        project.getTasks().create("foo", FooTask.class);
    }
}

When applying it, the build currently fails with a cryptic error message:
FAILURE: Build failed with an exception.

* Where:
Build file '/path/to/build.gradle.kts' line: 35

* What went wrong:
Failed to apply plugin [class 'foo.FooPlugin']
> Could not create task ':foo'.
   > Could not create task of type 'FooTask'.
      > The constructor for class foo.FooPlugin$FooTask_Decorated should be annotated with @Inject.

Moreover, if you replace tasks.create() by tasks.register() in the plugin implementation, you lose the location in the error report.
Expected behavior
Gradle should detect non-static nested classes and fail early with a good error message. Failing early will allow for the exception to be location aware and provide with hints as to where the error comes from, pointing at the nested class source in the script.

 The instantiator should check whether a class is an inner class and fail instead of looking for a constructor.

This is fixed in https://github.com/gradle/gradle/pull/8117

@adammurdoch sorry for the delay, here it is: https://github.com/gradle/gradle/issues/8521


[WIP] gk-deploy: Deploy glusterblock provisioner containers

Depends on: #281, #289, #299, #300, #305
Signed-off-by: Jose A. Rivera<EMAIL_ADDRESS>

This change is

A small update: I am holding this PR in WIP status until the upstream Gluster containers and heketi are updated for gluster-block.

@jarrpa can this be merged now? :-)


contributing guide merge conflict issue

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/923
Originally created by @derek-knox on 2019-08-26 16:50:48

resolve merge conflict issue where undesirable characters got committed

View 2 previous comments from the original issue on GitLab


Challenge on Product Preview Card Component

THINGS I DID WHEN CARRYING OUT THIS CHALLENGE

During this project i make use of git flow init
Changed the root branch to develop branch

HTML
I created  the HTML file using the following tag

The heading tag: This is used to type the name of the product Gabrielle Essence Eau De Parfume
The paragraph tag: This is used to type the body content of the product
The image tag: Used to import the image of the product in the exercise
The section: Used to make the whole project into one section
The article tag is used to separate the content into left and right in the section

CSS
I created  the styles file using the following tag
{  color: ;
}
{ margin:
padding:
display: flex;
}
although i used some attribute which i did not listed here

Hi @tunde2023  ✋
Good job so far!
Hello ✋, you have done well reaching this point of the milestone 🤝 . But there are some issues that you still need to work on to go to the next project but you are almost there!
This project will be marked as Invalid and won't affect the number of your weekly reviews.
Kindly follow GITFLOW in your project. create another branch from which your project will be done and create pull request from there . Then you can merge into the development branch when the project is approved. From your pull request, this was not done.
This is a general requirement for this project.
Cheers, and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread and tag me @megagig if something is not 100% clear.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

STATUS: APPROVED
@tunde2023
Next time please always use correct gitflow. If you still don't understand gitflow, always ask your colleagues
happy coding


HAP returning secrets to the pool

Description
Changes proposed in this pull request:

Added logic to KEB for marking secrets as dirty when last SKR is deprovisioned
Added job for cleaning dirty secrets and Azure resources.

Related issue(s)

Issue -> https://github.com/kyma-project/control-plane/issues/42
This is follow up to this PoC: https://github.com/kyma-project/control-plane/pull/113

/test pre-master-control-plane-gke-integration

/test pre-master-control-plane-integration

/test pre-master-control-plane-gke-integration


Hydration strategies

I have implemented #434 to allow consumers of FactoryMuffin to configure the hydration of their model classes in higher detail, because not everybody is using public setters or public properties. I updated the docs accordingly and also implemented some tests.
The behavior of FactoryMuffin stayed the same if you don't use strategies explicitly, so this feature should be backwards compatible.

If I am not mistaking, an admin has to apply the StyleCI fixes.

Any chance this gets merged?

@0s1r1s I'm afraid the maintainers will take their time, judging by the latest activity in the repository


Location fails intermittently but quite often

I'm finding that on many of my clients pinpoint/location fails with an error, even on first run. But many times it runs once successfully and reports a stale location thereafter.
Error obtaining a location. LS was unresponsive or a lookup timeout occurred.
I ran pinpoint -f on a few clients, it found a new location and that appeared in MR after I ran managedsoftwareupdate

Please file an issue in https://github.com/clburlison/pinpoint


Fix CountTo

CountTo was ignoring the last uint64 in the slice when using a multiple of 64. This fixes it and adds a test for it.

@kelindar ping


Consider pad value and input zero point in FoldExplicitPading

This commit adds the following:
Do not fold nn.pad and qnn.conv2d if padding value is not
equal to input zero point of qnn operation. Added unit test
to check such behaviour.

cc @masahi

cc @masahi

LGTM but does this case happen in practice? It doesn't seem correct to use a different value than zero point for padding before qnn.conv2d.

We doesn't face such cases on practice yet. I absolutely agree, it is strange usage of pad+qnn.conv combination, but anyway it may happens.
This change is just to keep pass correct for all possible cases. Relay itself doesn't prevent user from constructing any combination of operators, including case with different pad value by mistake.

Hi, @masahi ! Should we merge this PR or discard it? What's your opinion?

@jwfromm @masahi could you please approve pipeline to start?


Allow setting architecture on SsrFunction

fix: allow setting SsrFunction architecture
closes #2876

I arrived here as we are currently using a package that is only distribution for x86. It would be nice if we could get this merged :blush:

Sorry let me check on this.

Merged. Will be in the next release.
Thanks @relsunkaev.

Thank you for the quick response time :bow:


Deprecate .persisted in favor of .from_name(..., create_if_missing=True)

These methods are almost the same at this point, so let's merge.
We'll merge .lookup as well later.
Before we merge this, we need to update examples, integration tests, and docs. Otherwise those will fail.

Might be bike-shedding names at this point, but wouldn't a default-creation of missing objects be more convenient?
I'd even go so far as to say .persisted()  and .ephemeral() would be preferable to .from_name() and new() to make things a bit more clear, with .persisted() having a default create_if_missing=True that can be set to False if the user prefers it to not exist (like if they are using a local env var to configure it). Wdyt?
Just a slight preference. But this is fine too :)

+1 on .from_name(create_if_missing=True) being a little verbose for the most common (one might say "modal") case. Though I also have a preference for constructors being named from_*} unless the name other obviously connotes creation. 🤔

I sort of agree with your point @freider and there's a school of thought that boolean arguments are "bad" vs having multiple functions.
However:

My concern is that .persisted and .from_name have such different names that I think it's really confusing what's the difference.
.persisted has a side-effect which isn't obvious at all right now, and pretty confusing
I think the mental model of how users think about the cloud is that you create buckets before you run the code, and I'd rather push for that in our docs – i.e. you run modal volume create and then you use .from_name to refer to it.

If we keep it as two separate methods then I'd rather have names that are somewhat similar and also make it clear that there's a side effect. I can't think of anything obvious though... from_name vs from_name_create_if_missing makes it very obvious but it seems pretty ugly

there's a school of thought that boolean arguments are "bad" vs having multiple functions.

Interesting! I don't find this super compelling though:

My reasoning here is that the separate methods communicate more clearly what my intention is when I make the call. Instead of having to remember the meaning of the flag variable when I see book(martin, false) I can easily read regularBook(martin).

since in Python you can always spell that with the keyword argument (and the API can even require that if it makes sense).
I think a counterargument from a user perspective (rather than a code maintainer) is that an unambiguous "call this to create the object" method that has a few parameters makes it easier to understand the full space of options, otherwise e.g. a user who sees most of our examples using Volume.persisted might not even realize that there is the option of having Volume.ephemeral until they find themselves browsing the API docs one day.

I think the mental model of how users think about the cloud is that you create buckets before you run the code, and I'd rather push for that in our docs – i.e. you run modal volume create and then you use .from_name to refer to it.

Not sure I feel too strongly here but just noting that this be thought of as running counter to the infra 2.0 manifesto ;)

I don't ever want to provision anything in advance of load.

(Though granted it's not exactly the same as what you're talking about there).

from_name_create_if_missing

🤮

running counter to the infra 2.0 manifesto ;)

That's roughly true, although I want to bring back ephemeral objects in a slightly different shape later – something like Dict.ephemeral() in a way where it's not associated with apps. That way you can also use it in non-app contexts.
The main challenge is that the garbage collection logic would be somewhat more complex.

I sort of agree with your point @freider and there's a school of thought that boolean arguments are "bad" vs having multiple functions.
However:

My concern is that .persisted and .from_name have such different names that I think it's really confusing what's the difference.
.persisted has a side-effect which isn't obvious at all right now, and pretty confusing
I think the mental model of how users think about the cloud is that you create buckets before you run the code, and I'd rather push for that in our docs – i.e. you run modal volume create and then you use .from_name to refer to it.

If we keep it as two separate methods then I'd rather have names that are somewhat similar and also make it clear that there's a side effect. I can't think of anything obvious though... from_name vs from_name_create_if_missing makes it very obvious but it seems pretty ugly

Ah if we are pushing users toward prior object creation then this definitely makes sense. I also prefer a single function w/ boolean flags rather than two separate functions in this case.
Perhaps we could even make the create_if_missing flag configurable at a CLI level, e.g. modal deploy --create-missing bla.py in order to have clean-slate deployments more streamlined without having to modify the code?

Perhaps we could even make the create_if_missing flag overrideable at a CLI level, e.g. modal deploy --create-missing bla.py in order to have clean-slate deployments more streamlined without having to modify the code?

Yeah I think this might be good!

Thank you @freider!


[YouTube] Expose metadata to differentiate between an upcoming livestream and video premiere

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm requesting a site-specific feature
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
No response
Example URLs
https://youtu.be/2xpyp_PyyE4
https://youtu.be/5S-Z87XtV2k
Since this functionality affects upcoming videos, any URLs used as examples may go out of date quickly.
Browse through https://holodex.net/ for upcoming streams and content premieres.
Provide a description that is worded well enough to be understood
In yt-dlp, upcoming live streams (broadcasts) and video premieres have identical fields:

live_status == "is_upcoming"
is_live == False

Previously one could differentiate between the two as YouTube exposed the lengthSeconds field on premieres (duration in yt-dlp output); in the last few months this information leak was removed and neither of those types have it.
My suggested fix is to extract the .videoDetails.isLiveContent field from the player response (true for broadcasts, false for premieres) and make it available in a field such as .is_live_content.
I'm open to implementing and submitting a PR; just wanted to put an issue in case there was any objection or concerns beforehand.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
# Note: jq is used to filter the output to relevant fields

yt-dlp -vU --ignore-no-formats-error -j "https://youtu.be/2xpyp_PyyE4" | jq "{live_status, is_live}"
[debug] Command-line config: ['-vU', '--ignore-no-formats-error', '-j', 'https://youtu.be/2xpyp_PyyE4']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out cp1252 (No VT), error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds [c699bafc5] (pip)
[debug] Python 3.11.9 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 3.0.13 30 Jan 2024)
[debug] exe versions: ffmpeg 5.0.1-full_build-www.gyan.dev (setts), ffprobe 5.0.1-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.20.0, brotli-1.1.0, certifi-2024.02.02, mutagen-1.47.0, requests-2.32.3, sqlite3-3.45.1, urllib3-2.2.1, websockets-13.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1838 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds)
[youtube] Extracting URL: https://youtu.be/2xpyp_PyyE4
[youtube] 2xpyp_PyyE4: Downloading webpage
[youtube] 2xpyp_PyyE4: Downloading ios player API JSON
[youtube] 2xpyp_PyyE4: Downloading mweb player API JSON
WARNING: [youtube] Premieres in 40 hours
WARNING: No video formats found!
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec, channels, acodec, lang, proto, size, br, asr, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
WARNING: Requested format is not available
{
  "live_status": "is_upcoming",
  "is_live": false
}

yt-dlp -vU --ignore-no-formats-error -j "https://youtu.be/5S-Z87XtV2k" | jq "{live_status, is_live}"
[debug] Command-line config: ['-vU', '--ignore-no-formats-error', '-j', 'https://youtu.be/5S-Z87XtV2k']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out cp1252 (No VT), error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds [c699bafc5] (pip)
[debug] Python 3.11.9 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 3.0.13 30 Jan 2024)
[debug] exe versions: ffmpeg 5.0.1-full_build-www.gyan.dev (setts), ffprobe 5.0.1-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.20.0, brotli-1.1.0, certifi-2024.02.02, mutagen-1.47.0, requests-2.32.3, sqlite3-3.45.1, urllib3-2.2.1, websockets-13.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1838 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds)
[youtube] Extracting URL: https://youtu.be/5S-Z87XtV2k
[youtube] 5S-Z87XtV2k: Downloading webpage
[youtube] 5S-Z87XtV2k: Downloading ios player API JSON
[youtube] 5S-Z87XtV2k: Downloading mweb player API JSON
WARNING: [youtube] This live event will begin in 39 hours.
WARNING: No video formats found!
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec, channels, acodec, lang, proto, size, br, asr, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
WARNING: Requested format is not available
{
  "live_status": "is_upcoming",
  "is_live": false
}

I missed the part where it yt-dlp was supposed to be on an unstable release.  One second…

It doesn't look like media_type is currently implemented for the YouTube extractor, so there shouldn't be any backwards compatibility concerns at least.
The way media_type is specified as a string does mean that there can't be overlapping types (shorts + livestream comes to mind as a possibility).
Actually, reading up on the documentation for InfoExtractor it sounds like is_live can also be used for upcoming streams.  So it may make more sense to mark that as true for the player's isLiveContent field.


Returning Error When using api.http.get_user_info

It works fine using the http method of api.http.get_user_info when using VPN/Proxy:
Cannot get MQTT endpoint
Listening to MQTT...
Connected with result code 0

but when i'm not using VPN/Proxy, I couldn't seem get it work:
Got this account's message region: PRN
Listening to MQTT...
Connected with result code 0

Error:
'NoneType' object is not subscriptable

My code:
api.http.get_user_info(
    <sender_fbid>
)

I will have a look into this

@NoapMat What's your OS, node version and country?

@NoapMat What's your OS, node version and country?

Hello there, i'm on Debian. What do you mean by node version? (Are you asking my Python Version?), I'm running this on Python 3.11.8.
Update: It is working as expected i just changed my ISP's IP,  i cannot replicate it as of now, and I got no Got this account's message region: PRN showing when i changed ISP IP.
Sorry, I couldn't provide logs/screenshot, and any other information about it. You could mark this as a can't reproduce.


[feature] Make it easier to use monero-javascript for front end development

For such a comprehensive and easy to use library for node, it's not possible to simply npm i monero-javascript and use it for front end/browser apps (yes, this is documented), and it's quite painful to integrate it with even basic create-react-app or vuejs boilerplate code.  I think this is a big problem and is likely a bottleneck for a lot of would-be front end development.
I would really like to be able to simply install and use this library with no fussing with webpack and build configs if such a thing is possible.... i.e. I should be able to run create-react-app, or npm init vue@latest, run npm i monero-javascript, and be ready to roll.
Example of what needs to be done to use the library with Vue (see the fallbacks and additional packages necessary in package.json): https://github.com/xmrdotgift/wallet/blob/master/webpack.config.js

I support this and would also like to see typescript implemented.
I'm looking for help on both.  Thanks.

I was looking to use this thing in sveltekit, but that seems to be blocked by the vite tooling.
https://github.com/vitejs/vite/issues/5075 links to a bunch of issues describing the problem.
It's not really a monero-javascript problem, as it's more a tooling not being ready for wasm problem, I think.

I've been messing around with this off and on. Here's a workaround to get something going with create-react-app:
npx create-react-app <app name>
cd <app name>

# necessary to avoid needing to eject or override create-react-app's defaults
# see: https://github.com/facebook/create-react-app/issues/11756
npm uninstall react-scripts && npm install react-scripts@4

npm i monero-javascript

cp node_modules/monero-javascript/dist/* public
cp node_modules/monero-javascript/src/main/js/common/MoneroWebWorker.js public/MoneroWebWorker.js

I'm hoping svelte-emscripten is up for the task.
The required emscripten linker flags got me worried, as I can't find those. What do you think @woodser ?
:heavy_check_mark:  -s MODULARIZE=1
:x: -s ENVIRONMENT='web'
:x: -s EXTRA_EXPORTED_RUNTIME_METHODS="['specialHTMLTargets', 'JSEvents', 'GL', 'callMain', 'abort']"
How to Use
When you compile your program in Emscripten, use the output filetype *.js and use the linker flags below. These are required to adapt your program into component form:
    -s MODULARIZE=1

    -s ENVIRONMENT='web'

    -s EXTRA_EXPORTED_RUNTIME_METHODS="['specialHTMLTargets',
           'JSEvents', 'GL', 'callMain', 'abort']"

Then, use the component in your Svelte app:
import { default as Emscripten } from 'svelte-emscripten';
import { default as module } from './module.js';

<Emscripten
  module={module}
  canvas={true}
  console={false}
  verticalOrientation={false}
  options={
    {
      autorun: true,
      wasmPath: 'path/to/module.wasm'
    }
  }
/>

The required emscripten linker flags got me worried, as I can't find those.

These linker flags are defined here.
You get an error if you add them? What's the error?
Sometimes external nodejs dependencies need to be excluded from the build, here.

I'm not getting far enough to start tweaking linker flags.
Trying to build standard on Slackware 14.2 (Intel x64) ends with:
-- Configuring done
-- Generating done
-- Build files have been written to: /path/to/build-monero-javascript/github-monero-javascript/build
make: cmake --build . -j4
Unknown argument -j4
Usage: cmake --build <dir> [options] [-- [native-options]]
Options:
  <dir>          = Project binary directory to be built.
  --target <tgt> = Build <tgt> instead of default targets.
  --config <cfg> = For multi-configuration tools, choose <cfg>.
  --clean-first  = Build target 'clean' first, then build.
                   (To clean only, use --target 'clean'.)
  --use-stderr   = Ignored.  Behavior is default in CMake >= 3.0.
  --             = Pass remaining options to the native tool.
emmake: error: 'cmake --build . -j4' failed (returned 1)

The build script:
#!/bin/bash

BASE=$(dirname "$(realpath "$0")")

cd "${BASE}" || exit 1

if [ ! -d "${BASE}/emsdk" ]; then
    git clone https://github.com/emscripten-core/emsdk.git
fi

cd "${BASE}/emsdk" || exit 1

git pull \
&& ./emsdk install latest-upstream \
&& ./emsdk activate latest-upstream \
&& source ./emsdk_env.sh

export EMSCRIPTEN="${BASE}/emsdk/upstream/emscripten"
export EMSDK="${BASE}/emsdk"
export EM_CONFIG="${BASE}/emsdk/.emscripten"
export EMSDK_NODE="${BASE}/emsdk/node/14.18.2_64bit/bin/node"

cd "${BASE}/github-monero-javascript" || exit 1

./bin/update_submodules.sh || exit 1
./bin/build_all.sh || exit 1

Removing -j$HOST_NCORES from bin/build_wasm_emscripten.sh moves past that error.
Next error is:
monero-project/src/common/i18n.cpp:36:10: fatal error: 'translation_files.h' file not found
#include "translation_files.h"

That file does not exist in external/monero-cpp/external/monero-project/translations/
Isn't it supposed to be generated by:
external/monero-cpp/external/monero-project/translations/generate_translations_header.c ?

That file does not exist in external/monero-cpp/external/monero-project/translations/

I'd try building the monero-project submodule directly to ensure it succeeds, and build twice since some files are not built the first time, e.g.:
cd ./external/monero-cpp/external/monero-project
make release-static -j4
make release-static -j4

Then the translations directory should exist.

Building monero in ./bin/build_all.sh should be after boost has been build.
Otherwise it will fail if system boost does not have static libraries installed.
Maybe setting BOOST_ROOT to build/boost will do the trick.

Nope, no cake.
BOOST_ROOT=$(realpath "/path/to/github-monero-javascript/build/boost") \
BOOST_LIBRARYDIR="${BOOST_ROOT}/lib/" \
make release-static -j4

results in:
CMake Error at /usr/share/cmake-3.5/Modules/FindBoost.cmake:1657 (message):
  Unable to find the requested Boost libraries.

  Boost version: 1.59.0

  Boost include path: /usr/include

Building monero standalone is just fine.
[ 98%] Built target gen_multisig
[ 98%] Building CXX object src/daemon/CMakeFiles/daemon.dir/command_server.cpp.o
[ 98%] Building CXX object src/daemon/CMakeFiles/daemon.dir/daemon.cpp.o
[100%] Building CXX object src/daemon/CMakeFiles/daemon.dir/executor.cpp.o
[100%] Building CXX object src/daemon/CMakeFiles/daemon.dir/main.cpp.o
[100%] Building CXX object src/daemon/CMakeFiles/daemon.dir/rpc_command_executor.cpp.o
[100%] Linking CXX executable ../../bin/monerod
[100%] Built target daemon
make :  OK

Building in external is not. Tried woodser/monero and that failed too.
CMake Error at /usr/share/cmake-3.5/Modules/FindBoost.cmake:1657 (message):
  Unable to find the requested Boost libraries.

  Boost version: 1.76.0

  Boost include path:
  /home/crypto/local/build/build-monero-javascript/github-monero-javascript/build/boost/include

  Could not find the following Boost libraries:

          boost_filesystem
          boost_date_time
          boost_program_options
          boost_locale

Changing bin/build_boost_emscripten.sh
./bootstrap.sh \
- --with-libraries=system,thread,chrono,serialization,regex \
+ --with-libraries=system,thread,chrono,serialization,regex,filesystem,date_time,program_options,locale \
2>&1

Results in:
CMake Error at /usr/share/cmake-3.5/Modules/FindBoost.cmake:1657 (message):
  Unable to find the requested Boost libraries.

  Boost version: 1.76.0

  Boost include path:
  /home/crypto/local/build/build-monero-javascript/github-monero-javascript/build/boost/include

  Could not find the following Boost libraries:

          boost_locale

The updated build script:
#!/bin/bash

BASE=$(dirname "$(realpath "$0")")

cd "${BASE}" || exit 1

if [ ! -d "${BASE}/emsdk" ]; then
    git clone https://github.com/emscripten-core/emsdk.git
fi

cd "${BASE}/emsdk" || exit 1

git pull \
&& ./emsdk install latest-upstream \
&& ./emsdk activate latest-upstream \
&& source ./emsdk_env.sh

export EMSCRIPTEN="${BASE}/emsdk/upstream/emscripten"
export EMSDK="${BASE}/emsdk"
export EM_CONFIG="${BASE}/emsdk/.emscripten"
export EMSDK_NODE="${BASE}/emsdk/node/14.18.2_64bit/bin/node"

cd "${BASE}/github-monero-javascript" || exit 1

./bin/build_boost_emscripten.sh || exit 1
./bin/update_submodules.sh || exit 1

PATCH_FILE="${BASE}/github-monero-javascript/external/monero-cpp/external/monero-project/src/crypto/wallet/CMakeLists.txt"
sed -i 's/set(MONERO_WALLET_CRYPTO_LIBRARY "auto"/set(MONERO_WALLET_CRYPTO_LIBRARY "cn"/g' "${PATCH_FILE}"

MONERO_BUILD="${BASE}/github-monero-javascript/external/monero-cpp/external/monero-project/build"
if [ ! -d "${MONERO_BUILD}" ]; then
    mkdir "${MONERO_BUILD}" || exit 1
fi

cd "${BASE}/github-monero-javascript/external/monero-cpp/external/monero-project/build" || exit 1

export BOOST_ROOT="${BASE}/github-monero-javascript/build/boost"
export BOOST_LIBRARYDIR="${BOOST_ROOT}/lib"
cmake .. || exit 1
make release-static -j2 || exit 1
make release-static -j2 || exit 1

#HEADER_FILE="${BASE}/../build-monero-pool/staging-area/monero/monero-build/translations/translation_files.h"
#HEADER_DEST="${BASE}/github-monero-javascript/external/monero-cpp/external/monero-project/build/release/translations/"

#if [ ! -f "${HEADER_DEST}/$(basename "${HEADER_FILE}")" ]; then
#    echo "*${WHITE} copy 'translation_files.h' ${RESTORE}"
#    sleep 3
#    cp "${HEADER_FILE}" "${HEADER_DEST}"
#fi

cd "${BASE}/github-monero-javascript/" || exit 1

./bin/build_all.sh || exit 1

Okay, this is beyond me. I can't get that locale thing to build.

It shouldn't be necessary to modify the boost libraries in bin/build_boost_emscripten.sh.
You still get boost errors without that modification? And have you installed boost with sudo apt install libboost-all-dev?

I'm on Slackware 14.2 (x64). Slackware does not include static libraries at all.

What would need to change in order to remove the need to copy files out of dist/ when targeting the browser? I'm interested in fixing this.

What would need to change in order to remove the need to copy files out of dist/ when targeting the browser? I'm interested in fixing this.

This is a bit out of my wheelhouse, but I did a little searching on npm and found a couple examples where they're providing their wasm as browser-importable js modules:
https://www.npmjs.com/package/brotli-wasm
https://github.com/jungomi/xxhash-wasm
Would be great if there was just one minified / tree-shakable js file that just works on browser or node.  We're definitely almost there.  Searching for libraries on npm with 'browser and node.js' might give some good examples of what might need to be done. Axios is one that's usable on node and browser without any user-involvement beside installing, and it just works.

What would need to change in order to remove the need to copy files out of dist/ when targeting the browser? I'm interested in fixing this.

This is a bit out of my wheelhouse, but I did a little searching on npm and found a couple examples where they're providing their wasm as browser-importable js modules: https://www.npmjs.com/package/brotli-wasm https://github.com/jungomi/xxhash-wasm
Would be great if there was just one minified / tree-shakable js file that just works on browser or node. We're definitely almost there. Searching for libraries on npm with 'browser and node.js' might give some good examples of what might need to be done. Axios is one that's usable on node and browser without any user-involvement beside installing, and it just works.

I think you're right, the solution involves bundling plus a package.json that points to the right files (xxhash for example). I think automating the emscripten part of the process to the point where all one needs to do after a fresh git clone should be to run npm run build-wasm should also be a goal, but maybe others have different thoughts on that. Assuming we do that too, the solution then looks like:

Automate building wasm bindings (this can be done with Docker and land as a separate PR if need be)
Bundle/tree-shake built JS with something like rollup
Point to built CJS/UMD/ESM modules with the package.json that gets published to npm

Having laid out everything like this I don't think it's a ton of work (automating all the wasm stuff would probably be the hardest part), but it's possible I've missed something.

@woodser @DangerOnTheRanger
Apparently, it's possible to generate WASM as a pre-bundled JS file rather than having separate .WASM that needs to be manually copied by downstream library consumers.  This would be a huge benefit for monero-javascript browser library users as they would simply import monero-javascript like any other JS library.  MyMonero had a very similar setup with their libraries, and they migrated to a 'unified' WASM/JS file in this commit: https://github.com/mymonero/mymonero-utils/commit/07d6a94d1d4cd23b95496243c93fa8d765888190

@CryptoGrampy I made the change from the PR and created single .js files. However, the .js file for the full wallet is 11.2 mbs, whereas the combined size of the old .js and .wasm is 6.7 mbs. Additionally, monero_web_worker.js punches out to 11.6 mbs, instead of the old 2.2 mbs. I need to find a way to optimize these.

Hopefully this issue is resolved with the latest v0.9.2 release (and project rename to monero-ts).

A lot of progress has been made since this issue was opened.
Yes, polyfills are still required to use functionality from Node.js in the browser, and I don't see how that can be easily changed. However, numerous other fixes have been made to make this library more friendly with various app frameworks.
First, as requested, we've updated the deprecated networking libraries to Axios, thanks to @mainnet-pat in #230.
Second, as requested, we've combined the dist assets into singular *.js files, completely removing the separate .wasm files, again thanks to @mainnet-pat in #250. Additionally, the dist assets no longer need to be copied manually to "public" (though the web worker must be copied or imported with a special line).
Third, we now support a variety of browser frameworks with sample applications to get up and running quickly, with the help of @mainnet-pat:

React (@j-berman)
Next.js
Vite (@trasherdk)
Webpack

What's not supported from the wishlist:

Removing polyfills, but the sample apps clearly demonstrate how to use them.
I haven't tested on Slackware :P

But with the networking libraries updated, the dist assets combined, and the sample apps supported, I'm going to go ahead and close this issue. Please if you encounter any sticking points, open a new issue for us to work through that specifically.
Thanks, and hope to see you guys around! :)


Frontend Host doesn't match the current host in the browser, so it's probably incorrect. Links in emails and file downloads from the API will not work. Click here to update.

Frontend Host doesn't match the current host in the browser, so it's probably incorrect. Links in emails and file downloads from the API will not work. Click here to update.         why?

this is my whatsapp : +1<PHONE_NUMBER>


AgentManager-SSLHandshakeHandler SSL error

I try to build and run apache cloudstack in my local  from https://github.com/apache/cloudstack and  use branch either 4.17-user-shared-networks or main I got below error in step 3

follow these step until the run jetty step under Build CloudStack
$ mvn -pl :cloud-client-ui jetty:run            # Run the management server on port 8080
 from https://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+CloudStack+Development+Environment+on+Linux

getting below error:
ERROR [c.c.u.n.Link] (AgentManager-SSLHandshakeHandler-5:null) (logid:) SSL error caught during wrap data: Empty server certificate chain, for local address=/<IP_ADDRESS>:8250, remote address=/<IP_ADDRESS>:56606.
WARN  [c.c.u.n.Link] (AgentManager-SSLHandshakeHandler-11:null) (logid:) This SSL engine was forced to close inbound due to end of stream.
javax.net.ssl.SSLException: closing inbound before receiving peer's close_notify
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:133)
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:336)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:292)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:283)
at java.base/sun.security.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:733)
at com.cloud.utils.nio.Link.doHandshakeUnwrap(Link.java:490)
at com.cloud.utils.nio.Link.doHandshake(Link.java:618)
at com.cloud.utils.nio.NioConnection$1.run(NioConnection.java:216)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
ERROR [c.c.u.n.Link] (AgentManager-SSLHandshakeHandler-11:null) (logid:) Failed to send server's CLOSE message due to socket channel's failure.
INFO  [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-7:null) (logid:) Connection from /<IP_ADDRESS> closed but no cleanup was done.
ERROR [c.c.u.n.Link] (AgentManager-SSLHandshakeHandler-11:null) (logid:) SSL error caught during wrap data: Empty server certificate chain, for local address=/<IP_ADDRESS>:8250, remote address=/<IP_ADDRESS>:56610.
WARN  [c.c.u.n.Link] (AgentManager-SSLHandshakeHandler-4:null) (logid:) This SSL engine was forced to close inbound due to end of stream.
javax.net.ssl.SSLException: closing inbound before receiving peer's close_notify
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:133)
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:336)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:292)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:283)
at java.base/sun.security.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:733)
at com.cloud.utils.nio.Link.doHandshakeUnwrap(Link.java:490)
at com.cloud.utils.nio.Link.doHandshake(Link.java:618)
at com.cloud.utils.nio.NioConnection$1.run(NioConnection.java:216)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
ERROR [c.c.u.n.Link] (AgentManager-SSLHandshakeHandler-4:null) (logid:) Failed to send server's CLOSE message due to socket channel's failure.
INFO  [c.c.a.m.AgentManagerImpl] (AgentManager-Handler-8:null) (logid:) Connection from /<IP_ADDRESS> closed but no cleanup was done.
ERROR [c.c.u.n.Link] (AgentManager-SSLHandshakeHandler-5:null) (logid:) SSL error caught during wrap data: Empty server certificate chain, for local address=/<IP_ADDRESS>:8250, remote address=/<IP_ADDRESS>:56612.
ERROR [c.c.u.n.Link] (AgentManager-SSLHandshakeHandler-5:null) (logid:) SSL error caught during wrap data: Empty server certificate chain, for local address=/<IP_ADDRESS>:8250, remote address=/<IP_ADDRESS>:56616.
ERROR [c.c.u.n.Link] (AgentManager-SSLHandshakeHandler-4:null) (logid:) SSL error caught during wrap data: Empty server certificate chain, for local address=/<IP_ADDRESS>:8250, remote address=/<IP_ADDRESS>:56618.
WARN  [c.c.u.n.Link] (AgentManager-SSLHandshakeHandler-9:null) (logid:) This SSL engine was forced to close inbound due to end of stream.
javax.net.ssl.SSLException: closing inbound before receiving peer's close_notify
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:133)
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:336)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:292)
at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:283)
at java.base/sun.security.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:733)
at com.cloud.utils.nio.Link.doHandshakeUnwrap(Link.java:490)
at com.cloud.utils.nio.Link.doHandshake(Link.java:618)
at com.cloud.utils.nio.NioConnection$1.run(NioConnection.java:216)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
ERROR [c.c.u.n.Link] (AgentManager-SSLHandshakeHandler-9:null) (logid:) Failed to send server's CLOSE message due to socket channel's failure.

I stucked and I'm new to apache cloudstack and my environments: ubuntu 20.04.
Can anyone suggest me how to fix that issue?

@sotheareth are you running KVM agent (cloudstack-agent) on the same host? Can you redeploy your dev-test env, or re-add the host with ssh allowed on root user using password (in sshd_config you've to permit root login by password). Alternatively, you can also explore using mbx: https://github.com/shapeblue/mbx
The specific user-shared network branch may not be ready for testing yet, cc @weizhouapache

@rohityadavcloud

I installed cloudstack-agent on the same host and
already allow sshd_config for root:
PermitRootLogin yes and PasswordAuthentication yes
I did not try your https://github.com/shapeblue/mbx yet

@sotheareth Assuming you're doing something for testing, you can set the ca.plugin.root.auth.strictness global setting to false temporarily (this doesn't require restarting mgmt server) and then go to UI->Infra->Hosts-> select the host -> click the provision certificate button (this will re-initiatlise the host certificates). Then you can change the auth strictness global setting to true again and restart cloudstack-agent.
The possible cause for this issue is usually that when adding the KVM host the certificates for some reason weren't correctly setup (you may check logs to investigate further).

@rohityadavcloud

I'm not sure if run from source code it requires to install cloudstack-agent or is there any cloudstack-agent startup when I run from jetty.
after I change ca.plugin.root.auth.strictness = false and it works fine
I can add secondary storage - success
now I have another issue
I cannot add new host - error said 'Error 530 Unable to add the host'
and I check there is no any record for host table in datatabase

* Zone Name : primary-zone
* Pod name: primary-pod
* Cluster name: primary-cluster
* Host: <IP_ADDRESS>
* Username: root
* Password: ...

how does cloudstack look up the host?

Hi @sotheareth - the cloudstack-agent package needs to be installed on your KVM host (assuming you are using KVM). Also, check if the port 8250 is open as it is the port the management server and the host agent connect to

@sotheareth were you able to get help? If not can you join our dev mailing list and continue there -
https://cloudstack.apache.org/mailing-lists.html
Or additional resources:
https://github.com/shapeblue/hackerbook/blob/main/2-dev.md


Can this test be rewritten to use waitsFor?
http://jasmine.github.io/1.3/introduction.html#section-32

Yes.

If you keep a hardcoded timeout, then some day or another you will need to increase it to 200, 300 and so on. Better alternative is to poll for expected changes. Check this https://gist.github.com/abreckner/110e28897d42126a3bb9

I'd suggest a number of edits to the runAsync function:

timeout functionality - either remove it completely or make it fail the test (I vote for removing, cannot see any use cases)
choose more reasonable default for checkInterval so you don't need to specify it often, probably 50 or 100
rename runFunction -> next, checkCondition -> predicate, and reorder them so that calls look more natural (first check, then continue)
cancel better to call clear or stop
choose better name for the utility itself, it's not "run async" it's "wait for condition" or maybe "wait for side effects"
fix the code style (opening brace)

/cc @AlekseyMartynov done

I see that you are still using different values of checkInterval (100, 200, 1000), even declaring special vars for them. What for? Just use the default interval and keep tests simple.
Another concern is code indentation:
It's rather hard to read:
wairFor(function() {
}, function() {

How about:
waitFor(
    function() {
    },
    function() {
    }
}

function() {
    done();
}

can be shortened to simply done, isn't it?

/cc @AlekseyMartynov

Good. Merge please.
P.S. There are still fixed timeouts used in other places. If would be good to refactor those tests, later on.


Add repository with Unifi Access Lock

PullRequest to HPM are not regularly reviewed in this DCMEGLIO repository. HPM has moved to HubitatCommunity and your PR should have been created there. Having stumbled onto this PR, I've manually merged it.


MIME4J-253: fix parsing encoded local part

hello, I'm proposing fixes for MIME4J-253. please let me know if you need any clarification. thanks

Does this need any further reviewing before merging?

Does this need any further reviewing before merging?

No we are good. Letting a little more time for people to review (~a week) is generally seen as a good practice within the ASF. Sorry for loosing track of this topic ;-)

Great, thanks!


Remove reference entry for template that got moved

This was my fault, forgot to update the docs when I moved the symbol. Thanks!!

Auto-merge toggled on


access error

Exception thrown at 0x00007FFB66115AB8 (GMod-SDK.dll) in gmod.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFF8.

/solved


Kafka- Handle produce async with callback

To get a better throughput - Instead of doing a simple produce and waiting for a record-meta-data,
perform a async produce with a callback.

Implementation, Dev and Test -Done.

TODO is

HelloWorld
Wiki page on how to


npm publish ignores NO_PROXY environment var (and AGENT_PROXYBYPASSLIST)

Environment

Server - TFS on-premises 2018.1
Agent - Private: Win10
Both agent and TFS server are on premises and behind a proxy

Issue Description
Using the NPM task -> publish to internal feed (registry I select here and selecting an existing private TFS NPM feed) -> results in error "socket hang up".
Since both
When checking the proxy logs, we see that the task hits it even that both NO_PROXY environment var and AGENT_PROXYBYPASSLIST are set correctly.
Looking at the source code it looks like the the proxy bypass list is not transferred in the _getProxyFromEnvironment method.
Based on the source code, this info is probably ignored for all NPM command type
Expected behaviour:
since npm supports the NO_PROXY environment var, the proper information should be set by the task.

Yep, this is a bug. I've taken a quick look, unfortunately there doesn't appear to be a trivial fix, since AGENT_PROXYBYPASSLIST is a list of regexes, but npm's no-proxy setting is expecting a list of hostnames.
For the publish task we can just run the regexes against the publish registry, but for install/custom I guess that we'll need to parse all the registries out of the npmrc, then run the regexes against them all to find matches (we have a handy list of all registries that require authentication, but no-proxy may need to include unauthenticated registries).


bring Makefile and icons up to date

I've discovered that very few of these are actually up-to-date with the template! I'm submitting PRs like tiliado/nuvola-app-deezer#6 as I find ones that need it.

Closing in favour of tiliado/nuvola-app-template#2 and the icons I have on shelve from Alex.


thoughts about new start page

Operation System: ubuntu 16.20
Beaker Version: 0.6.0 latest master commit: f3a95e4
I do have several thoughts about the new start page. I did mark the numbers with stars, so they are more visible.

1: The P2P icon is OK since users know the "share" icon. ... But it is still new and imo not established. So imo it needs some explanation (link). Eg: is the protocol secure ??
2: If I open info popup with the P2P button, it shows info about the URL, which is OK. But it should also contain information about the dat: protocol. Similar to FireFox https:// info. ... The new Chrome Info imo is way overloaded. .. but still has some info about the protocol. Most important: is it secure?
3: IMO this "footer" looks completely "lost". It spans 2 columns. So it's not clear, where it belongs to? ... Should it be a "call to action"?. If so, it needs to link to more possibilities and needs different styling. .. The whole page should use "Verdana", which is "sans serif". -> OK
But on my system, it uses "Liberation serif" as a fallback, which looks ugly. So imo the CSS needs a better definition: Verdana; sans-serif, which would fall back to "Liberation sans", which looks better. ... It should probably use the same setting as the "New tab"
4: Where is the sidebar? ... As I saw this page the first time, I was shocked. I thought. the "sidebar" is gone. ... As a new user, I'd "try to " open all the links and then get lost. ... What now?
5: IMO those icons are not visible enough, to get a newbie going. See 4: ... IMO we have a UX regression here.
6: all dat:/ links seem to be broken
7: icons?  IMO those icons don't fit the topics. ... but if these are placeholders only. .. it's just a reminder.
8: icons? github? IMO there should be the platform icons used.
As noted! ... just some thoughts.

6: all dat:/ links seem to be broken

IMO this is the worst thing, that can happen. As a newbie I'd think: "OK .. The whole thing is broken" .. I'm gone. ...
So those links should only be there, if they work. ...
Even as a dev, I'm not sure, if the resources are not ready yet, or if there is an issue with the code. .. So in any way, there is a problem.

Appreciate the feedback! You make some really good points. Let me go down the list.

It is secure. Maybe the label should be "Secure P2P"

We can definitely give more info, especially since this is the foremost indicator of the novel tech in Beaker. We'll make an issue for this for 0.6.2.

3 & 7 & 8. Agree, and thanks for the heads up on the fonts. There's lots more design to be done here.
4 & 5. This is something we went back-and-forth on. This site (dat://hostless.website) gets loaded on first open. The interface that you're familiar with is now loaded when you create a new tab.
The main reason for hostless.website is to give users (especially new users) content to interact with immediately. Specifically, websites hosted on dat, and help docs.
Knowing our motivation, what are your thoughts on this change?

That's a bug that surprises me. What happens? That probably needs to be a separate issue.

@pmario also, sorry this was a disappointing change. This is a WIP change that probably shouldn't be in master -- though I'm glad to get this feedback, so who knows.
Stick with us here, we'll get this right.

@pmario also, sorry this was a disappointing change.

... It's great to see progress :)
I try try to write things down, when they are fresh. .. Because after a day or two I get used to it. ... I think, we only have a very short period, to see things through "newbie" eyes. ...

Stick with us here, we'll get this right.

It already is a great browser, and a very interesting project!

Decided to revert back to beaker:start per your feedback, and rethink that idea.
@pmario Can you tell more about issue 6, and the failed dat loads? What did you see?

Can you tell more about issue 6, and the failed dat loads? What did you see?

I just found out, that both "beaker teamblog" links point to the same href ... Is there a link, to the page source?
@pfrazee  - I get a 408 timed out
dat://www.datprotocol.com  ... same thing. 408
I'll have a look, if I can create a local test page. ... didn't check this for a while.

Huh, that's strange. I've got the site hosted from a VPS, so there
shouldn't be any connectivity issues. And you've definitely had some
success syncing sites, because you downloaded hostless.website (which this
issue is about).
On Tue, Feb 7, 2017 at 2:44 AM, Mario Pietsch<EMAIL_ADDRESS>wrote:

Can you tell more about issue 6, and the failed dat loads? What did you
see?
I just found out, that both "beaker teamblog" links point to the same href
... Is there a link, to the page source?
@pfrazee https://github.com/pfrazee - I get a 408 timed out
dat://www.datprotocol.com ... same thing. 408
I'll have a look, if I can create a local test page. ... didn't check this
for a while.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/beakerbrowser/beaker/issues/278#issuecomment-277935364,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNhU5GYe-89jNaQoIyzS1Gf3UxvQM5Bks5raC7XgaJpZM4L3_h2
.

@pfrazee You may have missed this info: Both beaker team block links point to: dat://paulfranzee.com if you click the links.

dat://paulfrazee.com .. works now. .. strange.
What I did:

I wanted to save dat://hostless.website
Then clone it -> problem 2 files where missing: text.txt and steak_meat.png

beaker was unable to load them. ... It showed the spinning wheel for about 10 min, then I closed the page
CPU load went up to about 40% for every core. normal is: 30% 1 core, 3-5% 3 cores

I did save dat://hostless.website

I did manually open the 2 missing files.
They where loaded. -> Still a problem with the hidden files dat.json and .DS_Store
I did manually open them -> which worked.
Now it was possible to Fork dat://hostless.website

After all those steps -> I can open dat://paulfranzee.com now.

dat://www.datprotocoll.com -> shows 408

dat://taravancil.com manually typed into URL bar-> opens: dat://db3a51..17/#timeout and shows: "Searching the network for this site. Please wait..."  .. for ever

cpu load up to ~40% for all 4 cpus :/

My question now is: "Is there a fast way to spin up a dat:// server in the cloud, to play with" .. including DNS name resolution? like dat://paulfrazee.com..
Can it handle IPv6?

My question now is: "Is there a fast way to spin up a dat:// server in the cloud, to play with" .. including DNS name resolution? like dat://paulfrazee.com..

Yes. I'm using dathttpd on a VPS to host all of these sites, which, among other things, is a way to run dat. I'll announce this tool soon.

Can it handle IPv6?

I haven't tried, so I'm not sure.
About your other reports, I think there are three issues at work here. Here's what I see happening:

The original issue was a data-loss problem with dat. That has since been resolved, which is why some pages started to load.
A new problem seems to be that there are network connection errors. I'm seeing some signs of that in other tests, so I'll need to start debugging.
The high CPU usage. I have some guesses about why that might be happening, but it won't be easy to solve.

I'll let you know when I make progress on the second item

just some more feedback

4 & 5: This is something we went back-and-forth on. This site (dat://hostless.website) gets loaded on first open. The interface that you're familiar with is now loaded when you create a new tab.

I think at the moment, a live "Welcome" page is risky. ... It seems you only have the possibility to develop / test with macOS. ... Problems that I encounter (using ubuntu) may have several reasons.

real issue ... as we found out :)
OS specific quirks
dat: resource (temporary) unavailable or different issue

So it's very hard to decide, where to search. ... I didn't even try to compile the stuff on windows 10. (because of #55 and #103) ... which will open a new universe of possible issues :)
So I'd suggest: Give dat://hostless.website a new title eg:
Welcome to Beaker - Find and share you dat sites !
and PIN it as the first favourite. So we can be pretty sure, that it is clicked by every user.
PIN ... would be a new functionality, that removes the "x" - delete button, and moves the pinned-fav to the top of the list ;)

The main reason for hostless.website is to give users (especially new users) content to interact with immediately. Specifically, websites hosted on dat, and help docs.

I like this.. but as I wrote, If the first and the second click doesn't work, it looks broken. And the average user has no chance to see, what's the real problem. ...

Knowing our motivation, what are your thoughts on this change?

I like the structure of the page from the OP.

3 columns: "social"   |  "how to"  |  "geeky stuff"
Just the "Welcome to Beaker"  ... as it is now is missing
The new footer is better, but imo may be changed in the future.

but ...
At the moment for me it feels to risky. I like the "pinned - fav - page" idea :)
I don't know, the system well enough, to trust it. I don't know the community and there are too many new and unknown elements involved.

the beaker browser ... in heavy development .. a very fast moving target, which is good for beta software. .. But problems need to be expected.
the dat-protocol ... has version number 12 atm. It seems to introduce breaking changes every month. At least it looks like this, if you are used to semver versioning. And the update from instructions indicate: "problems ahead" (for me)
The whole ecosystem around dat:// is in flux. ...

just some thoughts.

Hey, I forgot to respond to your last comment but I found it insightful. Thank you for sharing.
I'm going to close this issue to keep the board clean. Please open similar issues in the future. We're rolling out another shot at the start page (which you can try on master) that I hope you'll like -- but, if not, let us know!

that I hope you'll like

-1

-- but, if not, let us know!

hmmm ... I'll sleep over it and post tomorrow. ..


Fixed bug in bokeh BarPlot colormapping integer values

When using a CategoricalColorMapper integer values need to be transformed. The logic to apply this transformation was incorrect leading to BokehJS errors in certain cases.

Will go ahead and merge since the change is tested.


Fix in parallel processing code snippet

Simple fix to the parallel processing code snippet that has the same line twice.
var firstOperation = telemetryClient.StartOperation<DependencyTelemetry>("task 1");
var firstOperation = telemetryClient.StartOperation<DependencyTelemetry>("task 1");

@fbeltrao : Thanks for your contribution! The author, @mrbullwinkle, has been notified to review your proposed change.

#sign-off


Enable --prune-registry flag

Adds the --prune-registry flag to the oc admin command in the pruner cronjob based on the management state of the image registry custom resource

/assign @adambkaplan @dmage

/retitle Bug 1806019: Enable --prune-registry flag

Test added.

@adambkaplan test added

Updated the test to wait for the cronjob to get updated

/retest

/close
added to https://github.com/openshift/cluster-image-registry-operator/pull/459


Search result details - Display „X von X Standorten haben geantwortet.“

After clicking “Details” button, the popup shows how many sites have responded (if it’s possible).
(If the site has not responded, a line is displayed (instead of “0”).)
For example:

@juliangruendner  - check if this is possible and if how exactly

@michael-82 , @alexanderkiel , @EmteZogaf
as we do not know the number of expected sites - do you think it would be a good idea to simply make the number of expected sites configurable in the backend?

If this requires manual updating anyways...why not do this in the gui? I don't see the benefit of looping a config value through from backend to gui.
Can we get the amount of sites a query was dispatched to from the middleware(s)?


[Release-AutoPatch] Prepare for 2023 September auto-patch release

API change check
API changes are not detected in this pull request.

Redo it in https://github.com/Azure/azure-sdk-for-java/pull/36924


a simple question

why when i try to use fedoraware with dxlevel 81 it gives me a warning that i have to increase to dxlevel 90 ?
(my computer is a complete garbage and i can only play with a nice fps in dxlevel 81, or i use dxlevel 90 in 144p)

fedoraware doesnt provide support for dxlevels below 90, that warning is just to stop people from posting about graphical issues that only occur because they are on a lower dxlevel.

fedoraware doesnt provide support for dxlevels below 90, that warning is just to stop people from posting about graphical issues that only occur because they are on a lower dxlevel.

but does this affect some function of the hack making it unusable?

we dont know as we dont provide support for it, as well as other things like non windows 10 operating systems and duel injection.


width problem

Hi, I have the EasyAutocomplete in a Div, like  a popup but the width didnt work. The ul acept just 1 character per line.

can you share your code? Also, try posting your question on StackOverflow. Then link that question to this post.

I had the same thing. easyComplete changes all settings of that input field. So you need to either overrule or give it a valid width in pixels.
I also found a issue with the main class. It uses PX and i tried fixing the core code by adding auto or 100% to the main DIV its creates and this fixes it for mobile.
But im by far no code guru or whatever.
You can see my example here www.promotiespullen.com Ive implemented it on a couple places. I used a custom setup with images and links. The links it generates are taken from the search query


Fixed typographical error, changed achievments to achievements in README.

@idooo, I've corrected a typographical error in the documentation of the tweeria project. You should be able to merge this pull request automatically. However, if this was intentional or if you enjoy living in linguistic squalor, please let me know and create an issue on my home repository.

Thank you!


operator apicast-community-operator (0.8.0)

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[x] Are you familiar with our operator pipeline?

[x] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Your submission should not

[x] Add more than one operator bundle per PR
[x] Modify any operator
[x] Rename an operator
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description of the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@valerymo update ci.yaml to add new reviewers. Keep me as a reviewer and add yourself and maybe Austin or Michal?

@valerymo update ci.yaml to add new reviewers. Keep me as a reviewer and add yourself and maybe Austin or Michal?

Thank you @eguzki , done

PR was changed - to be based on 2.14 instead of 2.15

@valerymo @eguzki Hey, the PR seems ready to be merged, but I don't see any explicit approval from ann, the operator owner. Can you approve or share the status of this PR? Thanks

@valerymo AFAIK you wanted to add some changes from https://github.com/3scale/apicast-operator/pull/228
let us know

@valerymo AFAIK you wanted to add some changes from 3scale/apicast-operator#228
let us know

@eguzki  current PR still need to be reviewed in our Team. It waited for merge of testing/image PR in apicast-operator repo - https://github.com/3scale/apicast-operator/pull/228 . Now it approved and hope will be merged very soon. So we will review again current PR and will send update.

Diff with previous version LGTM
iff -r 0.7.1/manifests/apicast-operator.clusterserviceversion.yaml 0.8.0/manifests/apicast-operator.clusterserviceversion.yaml
23c23
<     containerImage: quay.io/3scale/apicast-operator:v0.7.1
---
>     containerImage: quay.io/3scale/apicast-operator:v0.8.0
35c35
<   name: apicast-community-operator.v0.7.1
---
>   name: apicast-community-operator.v0.8.0
38c38
<   replaces: apicast-community-operator.v0.6.0
---
>   replaces: apicast-community-operator.v0.7.1
59c59
<     See [the upgrade guide](https://github.com/3scale/apicast-operator/blob/v0.7.1/doc/operator-user-guide.md#upgrading-APIcast) for more information.
---
>     See [the upgrade guide](https://github.com/3scale/apicast-operator/blob/v0.8.0/doc/operator-user-guide.md#upgrading-APIcast) for more information.
62c62
<     Documentation can be found on our [website](https://github.com/3scale/apicast-operator/tree/v0.7.1).
---
>     Documentation can be found on our [website](https://github.com/3scale/apicast-operator/tree/v0.8.0).
112,113c112,113
<                   value: quay.io/3scale/apicast:v3.13.2
<                 image: quay.io/3scale/apicast-operator:v0.7.1
---
>                   value: quay.io/3scale/apicast:3scale-2.14.1-GA
>                 image: quay.io/3scale/apicast-operator:v0.8.0
285c285
<     url: https://github.com/3scale/apicast-operator/tree/v0.7.1
---
>     url: https://github.com/3scale/apicast-operator/tree/v0.8.0
293c293
<   version: 0.7.1
---
>   version: 0.8.0
diff -r 0.7.1/manifests/apps.3scale.net_apicasts.yaml 0.8.0/manifests/apps.3scale.net_apicasts.yaml
220a221,238
>               openTelemetry:
>                 description: OpenTelemetry contains the gateway instrumentation configuration with APIcast.
>                 properties:
>                   enabled:
>                     description: Enabled controls whether OpenTelemetry integration with APIcast is enabled. By default it is not enabled.
>                     type: boolean
>                   tracingConfigSecretKey:
>                     description: TracingConfigSecretKey contains the key of the secret to select the configuration from. if unspecified, the first secret key in lexicographical order will be selected.
>                     type: string
>                   tracingConfigSecretRef:
>                     description: TracingConfigSecretRef contains a Secret reference the Opentelemetry configuration. The configuration file specification is defined in the Nginx instrumentation library repo https://github.com/open-telemetry/opentelemetry-cpp-contrib/tree/main/instrumentation/nginx
>                     properties:
>                       name:
>                         description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid?'
>                         type: string
>                     type: object
>                     x-kubernetes-map-type: atomic
>                 type: object
222c240
<                 description: OpenTracingSpec contains the OpenTracing integration configuration with APIcast.
---
>                 description: OpenTracingSpec contains the OpenTracing integration configuration with APIcast. Deprecated
273a292,295
>               serviceCacheSize:
>                 description: ServiceCacheSize specifies the number of services that APICast can store in the internal cache
>                 format: int32
>                 type: integer
311c333
<                 description: Represents the latest available observations of a replica set's current state.
---
>                 description: 'Represents the observations of a foo''s current state. Known .status.conditions.type are: "Available"'
312a335
>                   description: "Condition contains details for one aspect of the current state of this API Resource. --- This struct is intended for direct use as an array at the field path .status.conditions.  For example, type FooStatus struct{ // Represents the observations of a foo's current state. // Known .status.conditions.type are: \"Available\", \"Progressing\", and \"Degraded\" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition `json:\"conditions,omitempty\" patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"` \n // other fields }"
313a337,355
>                     lastTransitionTime:
>                       description: lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed.  If that is not known, then using the time when the API field changed is acceptable.
>                       format: date-time
>                       type: string
>                     message:
>                       description: message is a human readable message indicating details about the transition. This may be an empty string.
>                       maxLength: 32768
>                       type: string
>                     observedGeneration:
>                       description: observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance.
>                       format: int64
>                       minimum: 0
>                       type: integer
>                     reason:
>                       description: reason contains a programmatic identifier indicating the reason for the condition's last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty.
>                       maxLength: 1024
>                       minLength: 1
>                       pattern: ^[A-Za-z]([A-Za-z0-9_,:]*[A-Za-z0-9_])?$
>                       type: string
315c357,361
<                       description: Status of the condition, one of True, False, Unknown.
---
>                       description: status of the condition, one of True, False, Unknown.
>                       enum:
>                       - "True"
>                       - "False"
>                       - Unknown
318c364,366
<                       description: Type of replica set condition.
---
>                       description: type of condition in CamelCase or in foo.example.com/CamelCase. --- Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be useful (see .node.status.conditions), the ability to deconflict is important. The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
>                       maxLength: 316
>                       pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
320a369,371
>                   - lastTransitionTime
>                   - message
>                   - reason
324a376,378
>                 x-kubernetes-list-map-keys:
>                 - type
>                 x-kubernetes-list-type: map
327a382,385
>               observedGeneration:
>                 description: ObservedGeneration reflects the generation of the most recently observed spec.
>                 format: int64
>                 type: integer
diff -r 0.7.1/metadata/annotations.yaml 0.8.0/metadata/annotations.yaml
13c13
<   com.redhat.openshift.versions: v4.6
---
>   com.redhat.openshift.versions: v4.12

/lgtm

/pipeline restart operator-hosted-pipeline


parentNode is not defined

In using akkordion, I see errors in the console of Cannot read property 'parentNode' of null This is due to: https://github.com/TrySound/akkordion/blob/master/dist/akkordion.js#L128
Fix by changing the if statement to if((index = titleSet.indexOf(title)) > -1 || title === null) {

@0xdabbad00 PR welcome


feature: implement policy store

This changes from the native-tls to rusttls. This is cool from a certain POV, I'm thinking about a statically linked kwctl binary. However, this crate will be used also inside of the policy-server, which is stuck with the native-tls crate. I don't think this will cause issues, do you?

I don't think so, in principle. The policy-server will do the TLS termination of the requests made by the apiserver, whereas when fetching policies we'll use rustls. They have different CA default stores -- meaning, rustls has its own main CA store, while native-tls uses the system one.
I think we can add a task for checking if this is the best combination and possible hazards later. Meaning: for doing the TLS termination we don't care that much about root CA certificates (and we are using the system certs by using native-tls at this time), but we care a lot about the CA store of the policy-fetcher (using rustls). How secure is to rely on rustls for this? Before bumping dependencies in this case we should check that the store included by rustls only contains well-known CA's, and only those well known, nothing more.

We really need some tests for the methods that you introduced, like the ones that build all the paths for the local store. I'm not saying we have to go "crazy" and provide e2e tests that download things from real registries/http/https servers, but there are definitely some low hanging fruits from the testing POV that we must grab

:+1:


Context enum restructuring

What
Investigate whether enum class (rather than old-style enum) can/should be used for Context::Access and Context::Retention.
If old-stye enums are chosen for Context, then decide whether BatchElementError::ErrorCode should be likewise defined.
Why
Old-style enums do not create a namespace of their own, meaning that Access and Retention values are exported to the parent Context class, i.e. Context::kIgnored lives alongside Context::kUnknown, as opposed to Context::Retention::kIgnored and Context::Access::kUnknown, respectively.
On the other hand, old-style enum constants are trivially convertible to their underlying numeric representation, whereas enum class constants require a static_cast.  This is relevant to the Context::kRetentionNames code-to-string mapping.

Name lookup is relatively infrequent so increasing complexity there should not be a steering factor in choosing which option - the ambiguity around cases in the day-to-day is far more troublesome.


Remove Ant scripts and move to Maven only

I am opening a PR because of the changes to the action script so it can run before merging.
We have roughly equivalents of the previous tasks.
Use mvn clean compile -Pmanual to generate the manual. This will not run the tests by default.
Use mvn surefire-report:report-only to generate the report after running the tests. This uses the surefire-plugin, so the HTML looks different. The other option would be to utilize AntRun and add the jar for the junitreport task.
I also updated the scripts to default to the Maven build, and the GH action script to generate and upload the reports in case of test failures.
Closes #242.

OK, the action is working. Once we have a test failure, we check if the report generation and upload steps are correct.

At some point it would be nice to have a maven only build of the manual, rather than having to use ant-run.


Does this support API 24?

https://android-developers.blogspot.jp/2016/06/android-changes-for-ndk-developers.html
In this article,google seems prohibits the use of non-public ndk libraries.

API 24 is supported. Please kindly report here after you encountered some problem


[Ready for Review] Refactor API v2 comment routes

Purpose
With the addition of commenting on files, users must be able to see all of the comments on their project (whether they are on the project overview page or individual files), and comment on either the project or a specific file. Instead of adding more routes, change the create endpoint to require users to specify the comment target and type.
Changes
Make the user pass in the comment's target_id and type when creating a comment instead of getting the target from the url.

I can't create a deleted comment. The CommentCreateSerializer seems to ignore that attribute.

Hey @samanehsan,
This is looking pretty good!  I'm sending this back to In Progress.  Once you've made the above changes (including Steve's suggestion), please reassign me and I'll take another look.  I promise I'll get to it faster this time!  Sorry for the delay!
Cheers,
Fitz

I can't create a deleted comment. The CommentCreateSerializer seems to ignore that attribute.

I think that's because the deleted field is read_only...but it still works for updating so that's weird. I'll remove the read_only requirement since it should be a writeable field. Should users be able to create deleted comments though? That seems like something we shouldn't allow.

I can't create a deleted comment. The CommentCreateSerializer seems to ignore that attribute.
I think that's because the deleted field is read_only...but it still works for updating so that's weird. I'll remove the read_only requirement since it should be a writeable field. Should users be able to create deleted comments though? That seems like something we shouldn't allow.

Yeah, on second thought that does seem weird.  I guess deleted should be an update-only field.

I guess deleted should be an update-only field.

How can I make `deleted

Hey @samanehsan,
Looks fantastic to me!  Once you've added the JSON-API error pointers, this is Ready-to-Merge.
Cheers,
Fitz

Made those changes @felliott! The two failing tests have to do with HTTP connection errors...should I try restarting the build?

Made those changes @felliott https://github.com/felliott! The two failing tests have to do with HTTP connection errors...should I try restarting the build?

Perfect!  Thanks, @samanehsan!  Restarting the build isn’t necessary.  This is can go to Ready to Merge.
Cheers,
Fitz

Looks good. Comments above are not blockers.

I've restarted the build. This is good to merge when the build passes.

Merged into release/0.60.0 and develop.


Next 13 (app folder) + nextcrud

Integration with Next 13 with app folder isn't possible, due to the conventions changing. The handler export is changed to GET, POST, PUT, DELETE, etc.
For next, syntax should probably be something like:
export async function GET (req, res) {
  const nextCrudHandler = await NextCrud({
    adapter: new PrismaAdapter({
      prismaClient: prisma,
    })
  })

  return nextCrudHandler(req, res)
}

Has anyone managed to get APP route to work? I tried exporting as GET, POST, etc. But it turns out that in the code next-crud tries to send the response itself via res.send(), but in NextJS 14 this no longer works, it expects to receive a JSON response from the Response constructor.
Although NextApiResponse types have a send() method, in fact it is not presented and I get an error that res.send() is undefined.

Any update? It does not work on v14 too, I have 404 error

Workaround is to not use the App folder for the API: use pages/api/[...nextcrud].ts
The rest of my code base is still in the app folder and this works where app/api didn't.

Hello everybody
Sorry for the delay. I have opened a PR to add compatibility with the App Dir #67
There is a bit of breaking changes for on the callbacks but overall it is working for both App and Page router

@foyarash is it ready to use?

Published on v4.0.0.
Feel free to report any issue.

I too am unable to get v4.0.0 of next-crud to fully work using the App Router.  The GET requests work, but POST, PUT and DELETE all fail.  From what I can tell, the problem seems to be centered around the getRouteType() method and the matchers it uses to parse the path.  Every request appears to evaluate to false and the only API route that will work in spite of the matcher returning false is the GET (READ_ALL) route.


Convencion de nombres db

Current dependencies on/for this PR:

main:

PR #54

PR #60 👈

This comment was autogenerated by Freephite.


No mic access after build Rocket.Chat.Electron from source code

Regarding to desktop Rocket.Chat.Electron for Windows
My Setup

Operating System: Windows 10 pro ver 1909

App Version: rocketchat-setup-3.1.1.exe, rocketchat-setup-3.1.1.msi

Installation type: exe, msi

Description
Im using Lenovo Thinkbook 13s-Iml, with installed Windows 10 pro ver 1909.
When i download the latest release for Windows like .exe or .msi, everything works fine.
But when i try to build Rocket.Chat.Electron from source code, provided on the same release page,
builded app have no mic access when i try to record voice message or join to jitsi call.
https://github.com/RocketChat/Rocket.Chat.Electron/releases/tag/3.1.1
I can reproduce this issue only on laptop mentioned above,
on other laptops builded from source code by myself Rocket.Chat.Electron app works correctly.
Before build i set publish never in package .json
and go through the following steps:
with admin rights
yarn --check-files
set NODE_ENV=production
yarn build
yarn release
node v12.18.3
yarn v1.22.10
as well i tryed to build it via CI: github actions and jenkins - the same result, no mic access on my laptop.
Could you please advice, why builded from source code Rocket.Chat.Electron app have no mic access in opposit to .exe, .msi files provided on release page?
Current Behavior
builded from source code Rocket.Chat.Electron app have no mic access on my laptop
Expected Behavior
builded from source code Rocket.Chat.Electron works similar as .exe, .msi distributives apps, downloaded from release page, e.g. has mic access

The issue was caused by my anivirus (Kaspersky Entertaiment Security) and by incorrecet distributive signing.
If distributive not signed, or signed after build (the distributive shoud be signed along with build process) the issue above occurs.  KES is not provide mic access for not signed (or incorrectly signed) distributive.


Sorting of entries by name in project build phases doesn't work for framework build phases

Context 🕵♀
As part of cleaning up an Xcode project, I used the following to sort the files in build phases by name:
let settings = PBXOutputSettings(projBuildPhaseFileOrder: .byFilename)
try xcodeproj.write(path: path, override: true, outputSettings: settings)

What 🌱
I was expecting it to also sort the frameworks listed in a Link Binary with Libraries phase but inspecting the code showed that sortUsingNames(_:_:) only considers the file property which is nil for PBXBuildFile in a PBXFrameworksBuildPhase as those use product references instead.
Proposal 🎉
Since I wanted the frameworks sorted as as well, I made the following local changes.  Please do let me know if you want this behavior included in the project and I can raise a PR.
private func sortUsingNames(_ lhs: PBXBuildFile, _ rhs: PBXBuildFile) -> Bool {
    if let lhsFile = lhs.file, let rhsFile = rhs.file {
        return sortUsingNames(lhsFile, rhsFile)
    }
    // addition start
    if let lhsProduct = lhs.product, let rhsProduct = rhs.product {
        return sortUsingNames(lhsProduct, rhsProduct)
    }
    // addition end
    return lhs.uuid < rhs.uuid
}

And add the following overload for sortUsingNames(_:_:):
private func sortUsingNames(_ lhs: XCSwiftPackageProductDependency, _ rhs: XCSwiftPackageProductDependency) -> Bool {
    let lhsProductname = lhs.productName
    let rhsProductname = rhs.productName
    return lhsProductname == rhsProductname ? lhs.uuid < rhs.uuid : lhsProductname < rhsProductname
}

@kwriden do I need to assign this to someone to get it looked at?

Who do I need to assign this to someone to get it looked at?

is the issue that those aren't being sorted? or also other dependency types?

I am not sure, I didn't investigate it in more detail after I had fixed my specific use case.

worth including a test to that extent

Agreed but I don't have any time to work on this now.


Add image previews to notifications

https://stackoverflow.com/a/63991698

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @tneot01 in #android-requests.

not going to do this because it will delay and potentially fail to show notifications due to waiting to download the image from the server


libxlsxwriter: 1.0.8 -> 1.0.9

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libxlsxwriter/versions.
meta.description for libxlsxwriter is: "C library for creating Excel XLSX files"
meta.homepage for libxlsxwriter is: "https://libxlsxwriter.github.io/"
meta.changelog for libxlsxwriter is: "https://github.com/jmcnamara/libxlsxwriter/blob/RELEASE_1.0.9/Changes.txt"
Updates performed

Version 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

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

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

found 1.0.9 with grep in /nix/store/sf4lq3yi1hsyds7430i6zi90c90krxfq-libxlsxwriter-1.0.9

found 1.0.9 in filename of file in /nix/store/sf4lq3yi1hsyds7430i6zi90c90krxfq-libxlsxwriter-1.0.9

directory tree listing: https://gist.github.com/0723f1bb95287ac824de7ea0df7d3bf1

du listing: https://gist.github.com/494e7965a724bacafea78e3114e0e431

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

8 total rebuild path(s)

2 package rebuild(s)

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

First fifty rebuilds by attrpath
libxlsxwriter
sc-im

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/sf4lq3yi1hsyds7430i6zi90c90krxfq-libxlsxwriter-1.0.9 \
  --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 libxlsxwriter https://github.com/r-ryantm/nixpkgs/archive/92ff12c6d68cee8a70e9e786b16e3ab41811e1d4.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/sf4lq3yi1hsyds7430i6zi90c90krxfq-libxlsxwriter-1.0.9
ls -la /nix/store/sf4lq3yi1hsyds7430i6zi90c90krxfq-libxlsxwriter-1.0.9/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

2 packages built:

libxlsxwriter
scim (sc-im)

Maintainer pings
cc @dotlambda for testing.

Result of nixpkgs-review pr 129817 at 92ff12c6 run on aarch64-linux 1

2 packages built successfully:

libxlsxwriter
sc-im


MacOS 14.6.1 (Sonoma): can't copy UF2 file to Pico

This isn't really your issue, but thought I'd flag/document it.
Tried to drag (via Finder) and also copy (via Terminal) the UF2 file across but both times it would fail:
brett@Bretts-MacBook-Air build % cp roms+config.uf2 /Volumes/RPI-RP2
cp: /Volumes/RPI-RP2/roms+config.uf2: fcopyfile failed: Device not configured
cp: /Volumes/RPI-RP2/roms+config.uf2: fchmod failed: Device not configured

Using the same cable & UF2 file there was no issue dragging/dropping the file on Windows 10.  So seems to be an issue on the Mac (perhaps known from my quick search).

This should be fixed in the latest release V3.1.0


Update growl integration for notifications

The actual integration for growl notifications is using the UDP:9887 protocol. This seems to be superseded by the GNTP which uses TCP:23053.
There is already a usable version in pfSense which uses Net_Growl. As far as I can see Net_Growl is available in ports.
As I'm not into PHP I just tried to apply the patch und download Net_Growl into the include directory for testing. I came as far as trying to send a message where it bails out not having mbstring available.
So I assume the packages Net_Growl depends on are not available at all:

mbstring extension
pcre extension
SPL extension
mcrypt extension (optional)

I would build a new image including the patches, Net_Growl and its dependencies for testing myself but to be honest I don't know where all the knobs are that I need to turn.
If someone could point me in the right direction and there is interest in an integration update I could try to contribute a PR.
Best regards and sorry if the issue is not correct/missing information.

Hi @lopsch,
The current notification framework is scheduled for a full removal in 18.7. We already imported Monit into the core package for this reason. I don't see this code going anywhere because of it. Ok?
Cheers,
Franco

Sorry for the delay!


[zh-cn]sync command-line-tools-reference/kubelet.md

Ref: https://github.com/kubernetes/website/issues/39987
task-30

/approve
Need to retrigger the CI again.

/lgtm


VSTS Agents: Ant build step is getting added additional parameters for Options input

Agent version and platform
Version of your agent? 4.2.0

OS of the machine running the agent? Linux...

VSTS type and version
VisualStudio.com

If On-Prem TFS, which release, 2015 RTM/QU1/QU2?

If VisualStudio.com, what is your account name? http://aspectenterprise.visualstudio.com

What's not working?
Ant build step is adding additional parameters at the end of Option input value.
: /ci04_home/AspectAdmin03/ci04_agent03/_work/3/s -Dunit.test=com.oilspace.apps.aspect.admin.TestAspectAdmin -logfile tests_console_output.txt/src
/src - This is getting added at the end of the statement.
Actual out put should be
/ci04_home/AspectAdmin03/ci04_agent03/_work/3/s -Dunit.test=com.oilspace.apps.aspect.admin.TestAspectAdmin -logfile tests_console_output.txt/
Because of this our Junit test cases are getting failed. This issue started from 07th Sep onwards.
Can you please let us know how to resolve this?

## **Agent and Worker's diag log**
Logs are located at the `_diag` under agent root folder, agent log prefix with `Agent_`, worker log prefix with `Worker_`. all sensitive information should already be masked out, please double check before paste here.
[2016-09-08T14:37:34.796Z] vsoagent:> initAgent<<<<<<<<<<
2016-09-08T14:37:34.797Z: Agent Started.
2016-09-08T14:37:34.798Z: Listening for agent: AE-DT01-CI04_Lnx02
[2016-09-08T14:37:34.798Z] vsoagent:> created message listener
2016-09-08T14:37:34.798Z: starting listener...

Thanks @penupati.  I'm closing this issue as a duplicate of #2463 in the Microsoft/vsts-tasks repo.


Zero change to test CI

@baronfel This is a no-op change failing, we need a change to CI?
Thanks

This is most likely because the version of 7 previews has floated on the machines and something else is now the problem. So there's probably some actual code changes required.

This is most likely because the version of 7 previews has floated on the machines and something else is now the problem. So there's probably some actual code changes required.

@baronfel Oh dear, I see, so tricky.....

Closing as https://github.com/ionide/proj-info/pull/177 should have fixed dotnet 7/f# 7 issues


Go's interface to macOS's keychain certificate store is currently broken

See #24058 #24124 for context. Basically Go programs should be able to check the system keychain for certificates but they currently segfault when trying to.

"turns out" this is actually caused by https://github.com/NixOS/nixpkgs/issues/12346.
The go binary itself links against both the pure CF and Security.framework, the setup-hook added in https://github.com/NixOS/nixpkgs/pull/22571 only rewrites dylds at the moment.

Fixed by #27598


ci: add automatic-rebase.yaml

/rebase

Probably need to be merged before the first time execution.

https://github.com/autowarefoundation/autoware-github-actions/pull/8#issuecomment-990007429
-> https://github.com/autowarefoundation/autoware-github-actions/runs/4473168553?check_suite_focus=true

It couldn't fire pull_request workflows. :cry:


Make styled-jsx configurable

For the upcoming plugins in v2 zeit/styled-jsx#291. Continuation of #2991

@timneutkens ok I looked into this and unfortunately we need to resolve the plugins paths:
function styledJsxOptions(opts) {
  if (!opts) return {}
  if (!Array.isArray(opts.plugins)) return opts
  opts.plugins = opts.plugins.map(plugin => {
    if (Array.isArray(plugin)) {
      return [
        require.resolve(plugin[0]),
        plugin[1]
      ]
    }
    return require.resolve(plugin)
  })
  return opts
}

[require.resolve('styled-jsx/babel'), styledJsxOptions(opts['styled-jsx'])]

Okay, lets move it to next.config.js then 👍

@timneutkens your call, my example would work in server/build/babel/preset.js

@giuseppeg oh right, can simply use that and allow the user to use pretty names 😄 👍

@timneutkens if you want I can add the changes to this branch

@giuseppeg no worries I'll add them 👍


Update advertised Marathon version to 0.10.0

Please ping me when merged or do the gh-pages branch update yourself. Thanks!

Ok, I'll update the gh-pages branch now.


[Package request] Nix

If you could add a flake.nix to this project that would be awesome!

There's a PR up right now, waiting for it to get merged:
https://github.com/NixOS/nixpkgs/pull/286594

The nxpkgs PR (see last comment) has been merged! Please let us know it it isn't working as expected.

It's working great! Thanks for the awesome plugin and for making it nix compatible!

It is kind of wired. I can install sesh using nix-shell but my nixpkgs from nix/homemanager can not find the sesh value. Error msgs:
error:
       … while calling the 'derivationStrict' builtin
         at <nix/derivation-internal.nix>:9:12:
            8|
            9|   strict = derivationStrict drvAttrs;
             |            ^
           10|

       … while evaluating derivation 'home-manager-generation'
         whose name attribute is located at /nix/store/4fgs7yzsy2dqnjw8j42qlp9i1vgarzy0-sourc
e/pkgs/stdenv/generic/make-derivation.nix:348:7

       … while evaluating attribute 'buildCommand' of derivation 'home-manager-generation'
         at /nix/store/4fgs7yzsy2dqnjw8j42qlp9i1vgarzy0-source/pkgs/build-support/trivial-bui
lders/default.nix:87:15:
           86|       enableParallelBuilding = true;
           87|       inherit buildCommand name;
             |               ^
           88|       passAsFile = [ "buildCommand" ]

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: undefined variable 'sesh'
       at /nix/store/p3rd8nvgzpzdmfg13h4h2lvaqw2pmvr0-source/nix/home-manager/home.nix:74:5:
           73|     # session mangaer baseon tmux
           74|     sesh
             |     ^

Thank you!

As of today, sesh is in nixos-unstable. You might be using home manager which is on nixos-23.11. If that is the case, you will have to either move to unstable or install this one package from unstable.

Thank you for your reply!
I use nix/homemanager in wsl/ubuntu24.04. My nix pkgs is unstable.

Thank you for your reply! I use nix/homemanager in wsl/ubuntu24.04. My nix pkgs is unstable.

The most wired thing is that I can install it successfully using nix-shell -p


OpenGDS 1.2.41 (LV2017) GOOP2 -> GOOP3 conversion sometimes deletes class VI's

The GOOP2 -> GOOP3 conversion sometimes deletes class VI's.
ConvertGoop2ToGoop3.vi -> State 'OpenClassesInMemory' a number of specific GOOP2 vi's are deleted.
From example the 'class version.vi' containing the 'Class Template Version'.
The following file 'class GetProtocolversion.vi' will also get deleted since it match 'Version.vi$'.

Do you have a GOOP2 class I can test with?
I've not used GOOP2 for the last 10 years :-)

See attachment with a simple GOOP2 class. It has two methods that get deleted when I convert it to GOOP3 ('Goop2ToGoop3ConversionTest GetProtocolVersion.vi' and 'Goop2ToGoop3ConversionTest SetProtocolVersion.vi'
I used the old GOOP wizard default so it is an LLB.

Goop2ToGoop3ConversionTest.zip

Possible fix: Use the 'ClassPrefix' to get the file correct files.
Need to update the Update '\2Evit$' to '.*\2Evit$' to find all VIT of the class

Thanks for you feedback, this is now fixed in version 1.2.81.
You can find it in the beta testing listing soon.