https:// URL is not allow for images for generating PDF

Hello,
I am generating PDF using gem 'pdfkit', '~> 0.7.0', with HTML content.
I am facing issue with rendering image with HTTPS:// url. it is renderrd blank, if the image url is HTTP:// it's render fine.

What version of wkhtmltopdf are you using?
Can you do wget https:// url and get back the image?

Closing due to inactivity. This is not a PDFKit bug, but rather an issue of getting access to the file via HTTPS.

I have a slightly different, but similar issue. I am 100% sure image url is working. The problem is that image gets rendered properly in my local, which is on http, but on staging or production, which is on https, image doesn't get rendered.


[dif] Add tests for dif_alert_handler.h

Still pending >16 alert support, I suspect that will be its own PR.

Most recent CI run is green: https://dev.azure.com/lowrisc/opentitan/_build/results?buildId=24540&view=results, merging.


Issue used to copy CT labels

From @lfunkhouser on August 14, 2018 22:50
Copied from original issue: Esri/coordinate-conversion-addin-dotnet#515

This issue was moved to Esri/military-tools-desktop-addins#64


meson: mesonconf broken

Issue description
$ nix run -f '<nixpkgs>' meson ninja -c mesonconf build
Traceback (most recent call last):
  File "/nix/store/fir23185m103db7ddwjmhnqb2jd7baqa-meson-0.44.0/bin/mesonconf", line 18, in <module>
    from mesonbuild import mesonmain
  File "/nix/store/fir23185m103db7ddwjmhnqb2jd7baqa-meson-0.44.0/lib/python3.6/site-packages/mesonbuild/mesonmain.py", line 18, in <module>
    from . import environment, interpreter, mesonlib
  File "/nix/store/fir23185m103db7ddwjmhnqb2jd7baqa-meson-0.44.0/lib/python3.6/site-packages/mesonbuild/environment.py", line 17, in <module>
    from . import coredata
  File "/nix/store/fir23185m103db7ddwjmhnqb2jd7baqa-meson-0.44.0/lib/python3.6/site-packages/mesonbuild/coredata.py", line 20, in <module>
    from .mesonlib import MesonException, commonpath
  File "/nix/store/fir23185m103db7ddwjmhnqb2jd7baqa-meson-0.44.0/lib/python3.6/site-packages/mesonbuild/mesonlib.py", line 60, in <module>
    meson_command = python_command + [detect_meson_py_location()]
  File "/nix/store/fir23185m103db7ddwjmhnqb2jd7baqa-meson-0.44.0/lib/python3.6/site-packages/mesonbuild/mesonlib.py", line 51, in detect_meson_py_location
    raise RuntimeError('Could not determine how to run Meson. Please file a bug with details.')
RuntimeError: Could not determine how to run Meson. Please file a bug with details.

Fortunately meson configure still works.
Technical details
Nixpkgs: b19c50cec9dd811b27d6141ecac1ac3b2697b096

This was removed in 0.48.0


counterparty-cli.py: set_up() got an unexpected keyword argument 'logfile'

v9.49.3 with changed counterparty-cli.py (based on fix in #591)
I downloaded the newest version of the file and replaced the old one. I'm not sure if I should clone the entire develop branch instead. When I run it with the master version, I get the same error as in #591. I think the bug may have been introduced later because the Jan 1 commit also has this issue.

C:\Windows\system32>python c:\counterpartyd_build\dist\counterpartyd\counterpart
y-cli.py --testnet --data-dir c:\bitcoin-core-0.10\counterparty-testnet --config
-file c:\bitcoin-core-0.10\TESTNET.counterpartyd.conf market
Traceback (most recent call last):
  File "c:\counterpartyd_build\dist\counterpartyd\counterparty-cli.py", line 736
, in <module>
    testcoin=args.testcoin)
  File "c:\counterpartyd_build\dist\counterpartyd\counterparty-cli.py", line 261
, in set_options
    log.set_up(args, logfile=False)
TypeError: set_up() got an unexpected keyword argument 'logfile'

You need to clone the whole thing.

Good, confirmed to work with develop..


Measures seems unreliable when working with IRQ

Working with interrupts on an Arduino Uno seems to give incorrect result when the acquisition runs over a long period of time (more than a couple of minutes).
I've done a series of tests using alternatively:

my fork of the Arduino library with IRQs, or the one from Tourmal
The Arduino library from thomasaw, which is an adaptation of the Radiation Watch Arduino sketch into an Arduino library
The very original Arduino sketch from Radiation Watch sample codes

The first gives results around 11 nSv/h after more than, whereas the two others gives measures of ~50 nSv/h, with stable results over all the acquisition time. Note that the first one have also results around 50 nSv/h the first minutes of the acquisition, but after some time the results drops to stabilize around 11 nSv/h.
The tests were run on the same environnement and over a period of time superior than 20 minutes (knowing that the recommanded acquisition time to have reliable results with the type 5 Radiation Watch is 2 min see Radiation Watch spec chart).
I have no test bench or other counter geiger to validate that the measures are good, but something seems wrong with the Arduino library that uses IRQ.
I'll do tests again with data logging to be able to really compare the results

80750d54614d80596ac4b86483a97dfd1351f780

Thanks for tracking down this problem.

Hey! While you're here, do you mind if we open-source the library? (for e.g. under a MIT licence)
I think we are far away from the original lib to make this without asking them. But maybe it's better to send Radiation Watch a message before?

I have the problem again, the measurements drop after about 15 minutes.
It must be related to the history management, but I'm not sure how. I'll track the changes I've made to identify what exactly causes the issue.

I'll look into the licensing issue.

Ok, the problem was here.
I simply made an invalid calculation of the history duration.
To allow to change dynamically the history length correctly (see the issue spotted in 80750d54614d80596ac4b86483a97dfd1351f780) I've changed the code to dynamically calculate the history duration after the length of the history array. Each cell of this array stores the count for N seconds, so we only need to make a simple calculation to determine the duration of the history (duration = duration of a cell * number of cell).
It is now possible to change the history length by modifying only the value of the define, the following being ajusted accordingly.
I will make the history length an optional argument of the RadiationWatch constructor, because it has a serious impact on the memory footprint. Allowing to reduce the history length will make it possible to run the SD card data logger on an Arduino Uno.

This time it's good, all run fine. I've made the HISTORY_LENGTH configurable. ab37d3588bfa0c286b2e92e1aa4ef5eaeb4e8b79
@thomasaw Would be cool to have your feedback concerning the licence. You can sent me a message directly (check my profile for my email). :)

For the record, before the fix (measurements constantly dropping):
After:


Migrate to FreeBSD 14.0-CURRENT for better GPU support.

Is your feature request related to a problem? Please describe.
It is, limited hardware has fully working graphics hardware. My laptop has a newer iGPU so the version of drm-kmod available does not support it. Switching to the FreeBSD 14.0-CURRENT snapshot allows you to get drm-devel-kmod which supports up to the soon-releasing 12th gen intel chips and tons of AMD and nVidia GPUS.
Describe the solution you'd like
I would like it if helloSystem migrates to FreeBSD 14.0-CURRENT so it can use drm-devel-kmod. This would give better GPU support. It would be nice if you put exec="mode 0" in /boot/loader.conf so a GPU not supported by the updated driver support will still run at the monitors resolution and supported GPUs will still have the native resolution before the drivers loads.
Describe alternatives you've considered
The only alternative would to be putting exec="mode 0" in /boot/loader.conf without the GPU driver which for me at least will force FreeBSD to go to the displays maximum resolution but that would not fix any bugs relating to no hardware acceleration.
Additional context
I know both of these work because I used exec="mode 0" in the loader.conf file when I used FreeBSD 13.0-RELEASE (also in helloSystem 0.5 but just entering mode 0 in the loader prompt and not the file) which does not have drivers that support my iGPU and I am currently using FreeBSD 14.0-CURRENT with the exec="mode 0" option in my loader to get a widescreen boot splash and have drm-devel-kmod so I have graphics acceleration.

I like this idea, however I'd prefer the system and packages to be upgradeable. Respectively:

https://github.com/helloSystem/Utilities/issues/33
https://github.com/helloSystem/ISO/issues/55

… drm-devel-kmod …

Maybe too adventurous. See for example https://github.com/freebsd/drm-kmod/issues/93
As a default for -CURRENT, graphics/drm-kmod is probably safer.

At this point we still have documented showstoppers that prevent us from going from 12 to 13, let alone 14

Fixed whilst testing an upgrade: https://github.com/wulf7/utouch/pull/2

@grahamperrin can you please elaborate? What is "utouch_softc's mutex" and how is it related to this ticket?

Can graphics/drm-devel-kmod not be compiled from ports on 13-stable? Sorry if this has been answered elsewhere; i've looked but not found anything to suggest it can't.

… graphics/drm-devel-kmod … 13-stable? …

Let's take this to https://forums.freebsd.org/forums/general.3/

I am really confused about all the FreeBSD versions that are available and partly supported in parallel. 12.x seems the one where most things work, 13.x is still the new kid on the block where things are broken, and now people are already talking about 14.x...

FreeBSD

… versions … partly supported in parallel. …

We have full support for multiple versions:

https://www.freebsd.org/security/#sup

Support is tiered by platform/architecture:

https://www.freebsd.org/platforms/
[FreeBSD-Announce] FreeBSD/i386 demoted to Tier 2 for FreeBSD 13.x (2021-01-28)

13.x is still the new kid on the block where things are broken,

No, there were release engineering (releng) processes during which things were fixed for all three releases:

https://www.freebsd.org/releases/11.4R/schedule/
https://www.freebsd.org/releases/12.2R/schedule/
https://www.freebsd.org/releases/13.0R/schedule/

Orientation
https://cgit.freebsd.org/src/log/?h=main

main a.k.a. HEAD uppermost
this is CURRENT.

https://cgit.freebsd.org/src/log/?h=stable/13
https://cgit.freebsd.org/src/log/?h=releng%2F13.0

releng/13.0 uppermost
release/13.0.0 part-way down.

Example
I built and installed 14.0-CURRENT a few hours ago.

Not really.
Ignoring FreeBSD 11.4-RELEASE, which is nearly end of life …

a binary for 12.⋯ should run on 13.⋯ and greater

– and so on. For example, a few weeks ago I built editors/nano on 13.0-RELEASE-p3 then ran it on 14.0-CURRENT. From https://forums.FreeBSD.org/threads/80117/post-523432:

… COMPAT_FREEBSD11, COMPAT_FREEBSD12, COMPAT_FREEBSD13, etc are in the GENERIC kernel. …

Nothing OS version-specific in the makefile for editors/nano; nothing OS version-specific in the makefile for www/falkon; and so on.

I am really confused about all the FreeBSD versions that are available and partly supported in parallel. 12.x seems the one where most things work, 13.x is still the new kid on the block where things are broken, and now people are already talking about 14.x... all the while Ports make some (which?) implicit assumptions about the FreeBSD version users are running.

The way I think about it is:
11.x and 12.x is legacy but is still production
13.x is mainstream and production
14 is development
https://www.freebsd.org/releases/
Some things (like *kmod; another one is lsof) need to be built against the relevant kernel sources, in order to run.

… 13.x is mainstream …

Undoubtedly.
People are often advised to upgrade from 11.4 or 12.2 to 13.0-RELEASE.
Downgrade situations are extremely rare.
https://old.reddit.com/r/freebsd/comments/pbdyo8/-/hab19cy/ is a rare example of a use case where the installer for 13.0-RELEASE is not usable, so there's a plan to simply install 12.2 then update to 13.0-RELEASE-p4.

Can graphics/drm-devel-kmod not be compiled from ports on 13-stable?

Posing the question: Linux 5.5.19 DRM or greater i.e. graphics/drm-devel-kmod on FreeBSD 13⋯ | The FreeBSD Forums

https://github.com/helloSystem/ISO/issues/271#issuecomment-907674668

Can graphics/drm-devel-kmod not be compiled from ports on 13-stable?

It can be built ▶ https://forums.FreeBSD.org/threads/81919/post-531421

There is now a (crashing) build based on 14-CURRENT.
https://github.com/helloSystem/ISO/releases/tag/tmpfs-14.0
Maybe someone can figure out what is going on.

There is now a non-crashing experimental build based on 14.0-CURRENT.

https://github.com/helloSystem/hello/issues/161#issuecomment-1236402512 graphics/drm-510-kmod is now building for FreeBSD:13:amd64.

Migrate to FreeBSD 14.0-CURRENT for better GPU support.

Some drm-510-kmod use cases might get more mileage from 14.0-CURRENT than from 13.1-RELEASE-p2, however — for purposes such as security and support https://www.freebsd.org/security/#sup – I think that 13.1-RELEASE will be a better base for helloSystem.


ASF not performing given task

After giving ASF the command "!play botname GameID" there's the correct feedback in group chat from the bot but when looking at the command line interface I can see that actually nothing happened.
I've asked someone else to try it - but he ran into the same problem of getting a reply in the chat but with the bot actually not doing what it should.
Months back this worked without any issues, but for the last months this doesn't work anymore as it should.
Other commands like status or redeem work without problem.

Looks like nothing changed since https://github.com/JustArchi/ArchiSteamFarm/issues/801

@Abrynos , if you care to read only the 2 first lines of mine then there's all the information you need in regards of a bug report, it's description, the expected behaviour and it's current behaviour.
I'm also telling you exactly what the log would tell: "when looking at the command line interface I can see that actually nothing happened" - i.e. the log doesn't show anything either!
And lastly, considering that it worked before and now it doesn't although the setting haven't changed, a copy of the json's content would tell you anything neither. Besides correct settings with which it should work. Hence and considering the other guy experienced the same issue, the report of mine here in the first place.
So much for next time reading text. If it works for you, good for you but just saying so doesn't actually help me and others having the same problem.

Hey there! Thank you for contacting our development team at GitHub.
We believe that your issue does not meet our contributing guidelines referenced during issue creation.

Before you open an issue please review the contributing guidelines for this repository.
(...)
I understand that if my issue is not meeting contributing guidelines specified above, especially if it's a question or technical issue that is not related to ASF development in any way, then it will be closed and left unanswered.

Reason for closing: this is intended ASF behaviour / technical issue / not a bug.
Please check out our wiki if you need further help.
Have a nice day!
~Archi


How to set user-agent string in generated SDKs

What can be improved
I'm trying to figure out if it's currently possible to set a user-agent string in generated SDKs.
I found this Issue about it: https://github.com/fern-api/fern/issues/2264. Hard to tell from the history on that Issue whether support was added, and if it was I can't find "user-agent" anywhere in the docs.
If this is supported, could somebody advise on how to set it?

@dannysheridan you closed #2264 that this ticket references – any chance you can provide any guidance on this? Thank you! 🙏

Howdy @Arkessler and @mstade! Sending a user-agent string (e.g., User-Agent: ${package}/${version}) is not currently supported.
Today Fern includes the following request headers for the same purpose:
"X-Fern-Language": "${language}",
"X-Fern-SDK-Name": "${package}",
"X-Fern-SDK-Version": "${version}",

A user of Fern has added a UserAgent themselves. If helpful, here's a link the PR: https://github.com/AssemblyAI/assemblyai-java-sdk/pull/105/files

@amckinney do you plan to support this feature? If not, let's close this issue as not planned.

This feature is being rolled out now that its part of Fern's IR (PR). For example, this is available in TypeScript and C#.
Fern SDKs will send the User-Agent header in the <package>/<version> format. If you want to send a custom User-Agent header, you can set an arbitrary HTTP header using the specific language's mechanism.
For example, consider the following Go use case:
header := make(http.Header)
header.Add("User-Agent", "your/custom/user-agent")
client := acmeclient.NewClient(
  option.WithHTTPHeader(header), // These headers are sent on every request.
)


hello,where can I find the file 'javadoc_train_ngram.txt' and 'inside_train_ngram.txt'

In the code '/N-Grams/main.py',Line 258 and Line 259,there are two files  'javadoc_train_ngram.txt' and 'inside_train_ngram.txt'.But i can't  find these two files in your project.Do you have them?Thank you

Hello, the material needed to replicate the experiments and how to set the environments is detailed in the readme of the replication package. What you are looking for is available here:  https://drive.google.com/drive/folders/1VX4YV6BNxKt1cElXQd_b4e0YAI6thBgM


Build error: jsoncpp

Build Process
Describe how you build polybar, list the exact commands you are using: This repository
If you build polybar directly from this repository:

Output of git describe --tags: 3.4.0-180-g5002297

Build Log
Post everything that is output to the terminal while building polybar below. This HAS to include the output of the cmake and make commands, if you used them.
$ ./build.sh -d
** Fetching submodules

** A build dir already exists (pass -f to replace)

** Setting build options

** Use GCC even if Clang is installed ----------------------------- [y/N]: y
** Include support for "internal/i3" (requires i3) ---------------- [y/N]: n
** Include support for "internal/alsa" (requires alsalib) --------- [y/N]: y
** Include support for "internal/pulseaudio" (requires libpulse) -- [y/N]: y
** Include support for "internal/network" (requires libnl/libiw) -- [y/N]: y
** Include support for "internal/mpd" (requires libmpdclient) ----- [y/N]: y
** Include support for "internal/github" (requires libcurl) ------- [y/N]: y
** Build "polybar-msg" used to send ipc messages ------------------ [y/N]: y
** Parallelize the build using make -j4 --------------------------- [y/N]: y
** Executing cmake command

-- Trying to enable ccache
-- Couldn't locate ccache, disabling ccache...
-- No build type specified; using Release
-- Using supported compiler GNU-9.3.0
--  Build:
--    Version: 3.4.0-180-g5002297
--    Type: Release
--    CXX: /usr/bin/g++  -Wall -Wextra -Wpedantic -O3 -DNDEBUG
--    LD: /usr/bin/ld
--  Install Paths:
--    PREFIX:  /usr/local
--    BINDIR:  /usr/local/bin
--    DATADIR: /usr/local/share
--    DOCDIR:  /usr/local/share/doc/polybar
--    MANDIR:  /usr/local/share/man
--  Targets:
-- [X]   polybar-msg
-- [ ]   testsuite
-- [ ]   documentation
--  Module support:
-- [X]   alsa (1.2.2)
-- [X]   curl (7.68.0)
-- [X]   dwm
-- [ ]   i3
-- [X]   mpd (2.18)
-- [X]   network (wireless-tools)
-- [X]   pulseaudio (13.99.1)
-- [X]   xkeyboard (1.14)
--  X extensions:
-- [X]   xcb-randr (1.14)
-- [X]   xcb-randr (monitor support) (1.14)
-- [X]   xcb-composite (1.14)
-- [X]   xcb-xkb (1.14)
-- [X]   xcb-xrm (1.0)
-- [X]   xcb-cursor (0.1.1)
--  Log options:
-- [X]   Trace logging
-- XCB[XCB]: Found component XCB
-- XCB[ICCCM]: Found component ICCCM
-- XCB[EWMH]: Found component EWMH
-- XCB[UTIL]: Found component UTIL
-- XCB[IMAGE]: Found component IMAGE
-- Found XCB: /usr/lib/x86_64-linux-gnu/libxcb.so;/usr/lib/x86_64-linux-gnu/libxcb-icccm.so;/usr/lib/x86_64-linux-gnu/libxcb-ewmh.so;/usr/lib/x86_64-linux-gnu/libxcb-util.so;/usr/lib/x86_64-linux-gnu/libxcb-image.so
-- Searching for xcbgen with /usr/bin/python3
-- Found xcbgen in /usr/lib/python3/dist-packages
-- XCB[RANDR]: Found component RANDR
-- Found XCB: /usr/lib/x86_64-linux-gnu/libxcb.so;/usr/lib/x86_64-linux-gnu/libxcb-icccm.so;/usr/lib/x86_64-linux-gnu/libxcb-ewmh.so;/usr/lib/x86_64-linux-gnu/libxcb-util.so;/usr/lib/x86_64-linux-gnu/libxcb-image.so;/usr/lib/x86_64-linux-gnu/libxcb-randr.so
-- XCB[COMPOSITE]: Found component COMPOSITE
-- Found XCB: /usr/lib/x86_64-linux-gnu/libxcb.so;/usr/lib/x86_64-linux-gnu/libxcb-icccm.so;/usr/lib/x86_64-linux-gnu/libxcb-ewmh.so;/usr/lib/x86_64-linux-gnu/libxcb-util.so;/usr/lib/x86_64-linux-gnu/libxcb-image.so;/usr/lib/x86_64-linux-gnu/libxcb-randr.so;/usr/lib/x86_64-linux-gnu/libxcb-composite.so
-- XCB[XKB]: Found component XKB
-- Found XCB: /usr/lib/x86_64-linux-gnu/libxcb.so;/usr/lib/x86_64-linux-gnu/libxcb-icccm.so;/usr/lib/x86_64-linux-gnu/libxcb-ewmh.so;/usr/lib/x86_64-linux-gnu/libxcb-util.so;/usr/lib/x86_64-linux-gnu/libxcb-image.so;/usr/lib/x86_64-linux-gnu/libxcb-randr.so;/usr/lib/x86_64-linux-gnu/libxcb-composite.so;/usr/lib/x86_64-linux-gnu/libxcb-xkb.so
-- xpp: including xcb proto composite.xml
-- xpp: including xcb proto randr.xml
-- xpp: including xcb proto xkb.xml
-- xpp: including xcb proto xproto.xml
-- Font not found: fixed:pixelsize=10
-- Font not found: unifont:fontformat=truetype
-- Font not found: siji:pixelsize=10
-- Configuring done
-- Generating done
-- Build files have been written to: /home/jesus/git/polybar-dwm-module/build
** Building project

Scanning dependencies of target dwmipcpp
[  5%] Built target xpp
[  6%] Building CXX object lib/dwmipcpp/CMakeFiles/dwmipcpp.dir/src/connection.cpp.o
[ 11%] Built target polybar-msg
[ 12%] Linking CXX static library libdwmipcpp.a
[ 16%] Built target dwmipcpp
Scanning dependencies of target poly
[ 17%] Building CXX object bin/CMakeFiles/poly.dir/components/controller.cpp.o
[ 18%] Building CXX object bin/CMakeFiles/poly.dir/modules/dwm.cpp.o
In file included from /home/jesus/git/polybar-dwm-module/include/modules/dwm.hpp:3,
                 from /home/jesus/git/polybar-dwm-module/src/modules/dwm.cpp:1:
/home/jesus/git/polybar-dwm-module/lib/dwmipcpp/include/dwmipcpp/connection.hpp: In instantiation of ‘static void dwmipc::Connection::run_command_build(Json::Value&, T) [with T = long unsigned int]’:
/home/jesus/git/polybar-dwm-module/lib/dwmipcpp/include/dwmipcpp/connection.hpp:138:26:   required from ‘void dwmipc::Connection::run_command(std::string, Types ...) [with Types = {long unsigned int}; std::string = std::__cxx11::basic_string<char>]’
/home/jesus/git/polybar-dwm-module/src/modules/dwm.cpp:266:47:   required from here
/home/jesus/git/polybar-dwm-module/lib/dwmipcpp/include/dwmipcpp/connection.hpp:354:9: error: conversion from ‘long unsigned int’ to ‘const Json::Value’ is ambiguous
  354 |         arr.append(arg);
      |         ^~~
In file included from /usr/include/jsoncpp/json/json.h:10,
                 from /home/jesus/git/polybar-dwm-module/lib/dwmipcpp/include/dwmipcpp/connection.hpp:10,
                 from /home/jesus/git/polybar-dwm-module/include/modules/dwm.hpp:3,
                 from /home/jesus/git/polybar-dwm-module/src/modules/dwm.cpp:1:
/usr/include/jsoncpp/json/value.h:312:3: note: candidate: ‘Json::Value::Value(bool)’
  312 |   Value(bool value);
      |   ^~~~~
/usr/include/jsoncpp/json/value.h:289:3: note: candidate: ‘Json::Value::Value(double)’
  289 |   Value(double value);
      |   ^~~~~
/usr/include/jsoncpp/json/value.h:287:3: note: candidate: ‘Json::Value::Value(Json::Value::UInt64)’
  287 |   Value(UInt64 value);
      |   ^~~~~
/usr/include/jsoncpp/json/value.h:286:3: note: candidate: ‘Json::Value::Value(Json::Value::Int64)’
  286 |   Value(Int64 value);
      |   ^~~~~
/usr/include/jsoncpp/json/value.h:284:3: note: candidate: ‘Json::Value::Value(Json::Value::UInt)’
  284 |   Value(UInt value);
      |   ^~~~~
/usr/include/jsoncpp/json/value.h:283:3: note: candidate: ‘Json::Value::Value(Json::Value::Int)’
  283 |   Value(Int value);
      |   ^~~~~
/usr/include/jsoncpp/json/value.h:437:30: note:   initializing argument 1 of ‘Json::Value& Json::Value::append(const Json::Value&)’
  437 |   Value& append(const Value& value);
      |                 ~~~~~~~~~~~~~^~~~~
make[2]: *** [bin/CMakeFiles/poly.dir/build.make:492: bin/CMakeFiles/poly.dir/modules/dwm.cpp.o] Error 1
make[2]: *** Se espera a que terminen otras tareas....
make[1]: *** [CMakeFiles/Makefile2:528: bin/CMakeFiles/poly.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
** Failed to build project

Environment:

Distro (with Version): Ubuntu 20.04.1 LTS

Additional context
Add any other context that you think is necessary about the problem here.
I don't have enough experience with these things, but I think the problem originates from the jsoncpp version used to build. On my distro, the latest version available in apt is 1.7.4-3.1ubuntu2. That seems to be much older than the latest version shown on jsoncpp repository (1.9.3). I seem to have been able to "install" the newer version with vcpkg, but there probably are a couple extra steps to get the compiler to use it. Is there a workaround to this?

Sorry about that, I didn't merge the fix to master. It should be good now. Let me know if it works.

Now it builds correctly. Thank you very much!


[ENHANCEMENT] Introduce cwd Setting in robot.toml to Specify Start Path for Robot

Description:
In many projects, RobotFramework tests and their associated libraries are organized in subdirectories. To improve the flexibility and usability of these projects, I propose adding a cwd (current working directory) setting in the robot.toml file. This setting will allow users to specify the start path for robot, making it easier to manage and execute tests located in various subdirectories.
Proposed Changes:

Add a new cwd setting in the robot.toml configuration file.
Modify the RobotFramework execution logic to use the specified cwd as the starting path for test discovery and execution.

Benefits:

Enhanced flexibility for projects with complex directory structures.
Simplified configuration and execution of tests in subdirectories.
Improved usability for teams organizing their tests and libraries in various folders.

Example robot.toml Configuration:
[robot]
cwd = "path/to/tests"

Currently, I have the following in my .vscode/settings.json:
{
  "robotcode.robot.env": { "EXECDIR": "${workspaceFolder}" }
}

Our team "anchors" our path references to ${EXECDIR} in our suites and keywords so we don't have to worry about relative/absolute pathing issues. Hence - the above declaration.
Abridged Example
*** Settings ***
Resource          ${EXECDIR}/Resources/keywords/global.resource
Library           ${EXECDIR}/Resources/python_libraries/RobotFrameworkUtilities.py

It would be also useful if this enhancement could include/resolve VS Code variables such as the ${workspaceFolder} is via the settings file.

Perhaps this is already in play, but I wanted to raise visibility for this as well.

@GLMeece, just to say a few words about this: and I'm sorry, that's not good style, because with RobotCode the ${EXECDIR} is always the ${workspaceFolder}, which you don't have to set explicitly
And instead of always having to specify such long paths and variables for the imports, you can simply put them in the Python path.
Simply add something like this to your robot.toml and then shorten it:
python-path = ["Resources/keywords", "Resources/python_libraries"]

the way you write your imports to that:
*** Settings ***
Resource          global.resource
Library           RobotFrameworkUtilities.py

This avoids unnecessary code duplication ;-)


Script hangs in Reboot-Loop due to Re-Launch WorkAround

Installing SP 2016 with Language Pack with AutoSPInstaller runs currently into a Reboot-Loop.
This is cause by a Script-Block within AutoSPInstallerMain.sp1 that checks for SPVersion and LanguagePacksInstalled:
if (($env:SPver -eq "16") -and ($languagePackInstalled))
Because the Re-Launch is not registered somewhere, the script will Re-Launch at this step over and over again.

I'm not exactly sure what's going on in your environment, but this doesn't happen (and has never happened) in any of mine. LanguagePackInstalled is actually a registry value that indicates that a langage pack was just installed and therefore requires configuration (PSConfig or PSConfigUI), Once configuration has successfully completed, LanguagePackInstalled should be set back to 0 and therefore the script re-launch should be skipped. Perhaps there's something in your environment that's preventing PSConfig from completing successfully?
Also, are you saying that the script is actually causing your servers to actuall re-boot?
Brian

Hey Brian, I am on a longer trip and are currently not able to test it again.
Your answer "works on my machine(s)" is not exactly what I expected.
In my setup, on a Windows 2016 Server with SP2016 and German language pack, runs into a loop of the script. Not the server reboots, but the script reboots. I pasted the script block above, so here it is again (currently line 213 in AutoSPInstallerMain.ps1:
languagePackInstalled = (Get-Item -Path "HKLM:\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\$env:spVer.0\WSS\").GetValue("LanguagePackInstalled")

...

if (($env:SPver -eq "16") -and ($languagePackInstalled))
    {
        Write-Host -ForegroundColor Yellow " - We need to re-launch the script to work around a known issue with SP2016 when language packs are installed."
        $scriptCommandLine = $($MyInvocation.Line)
        If (Confirm-LocalSession)
        {
            $scriptCommandLine = "$env:dp0\AutoSPInstallerLaunch.bat $inputFile"
            Write-Host -ForegroundColor White " - Re-Launching:"
            Write-Host -ForegroundColor White " - $scriptCommandLine"
            Start-Process -WorkingDirectory $PSHOME -FilePath "powershell.exe" -ArgumentList "-ExecutionPolicy Bypass $scriptCommandLine -RemoteAuthPassword $password" -Verb RunAs
            $script:aborted = $true
            Start-Sleep 10
            exit
        }
    }
    CreateWebApplications $xmlinput

So, for me it looks like it is checking on SP-Version (== 16) and if a Language Pack is installed in the registry (what is true in my case), and then goes into reboot. but with the next run of the script, the same variables are set (since the language pack is still installed!) and therefore, it always restarts at this point (for me!!).
It never reaches "CreateWebApplications".
What the script actually should do is check if the language pack is installed AND the reboot has not happened yet, then go into script-reboot, otherwise continue to CreateWebApplications.
Can you explain what I am not seeing in this Code?

Hi XristophD,
you overlooked the line below the registry "GetValue("LanguagePackInstalled")"-statement:
ConfigureLanguagePacks $xmlinput
This function executes psconfig for embedding the changes of the installation program(s) of the language pack(s). When the configuration wizard has done its work successful, it automatically changes (psconfig) this registry value to '0' - and therefore no loop at all.
Maybe you have overlooked the error messages in the output RTF file?
Greetings,
Oliver

I was having the same issue where autospinstaller would loop over and over stating "We need to re-launch the script to work around a known issue with SP2016 when language packs are installed." Running psconfig manually seemed to resolve this issue in my case.


#PURE not honored in tree-shaking

Bug report
I intially formulated this as a stackoverflow question but failed to get an answer there. I'm submitting this here as I have now become convinced this is a bug.
What is the current behavior?
When importing a named export marked with #__PURE__ webpack fails to tree-shake the remainder of the file.
Given the following files:
//a.js
export const X = /*#__PURE__*/ "X";

const a = function () {
  return "About a!";
};
a.foo = function () {
  return "foo";
};
export default a;

and
//main.js
import { X } from "./a";
import { Y } from "./b";

console.log(X, Y)

Webpack 4.43 in production mode inlines the whole a.js file in the resulting bundle.
Rollup only includes X from a.js (demo) which is what I expected.
The following didn't help :

Adding "sideEffect": false to package.json
Adding optimization.usedExports: true to webpack.config.js

The bailout debugging of the concatenation plugin doesn't yield additional insight.
I have a sandbox repository which exhibits the problem.
Clone the project, then run yarn to install the dependencies.

you can run webpack to build dist/purejs.bundle.js in dev mode and confirm that the default export is flagged /* unused harmony default export */
you can run webpack -p to build dist/purejs.bundle.js in prod mode and confirm that the bundle still contains return"About a!" and foo=function(){return"foo"}
you can run webpack --display-optimization-bailout  -p  to see that the concatenation plugin doesn't warn of bailout on a.js or b.js

Other relevant information:
webpack version: 4.43
Node.js version: 12.16.3
Operating System:  Linux
Additional tools: n/a

You can fix that with this configuration:
const TerserWebpackPlugin = require("terser-webpack-plugin");

/** @type {import("webpack").Configuration} */
module.exports = {
    optimization: {
        minimizer: [
            new TerserWebpackPlugin({
                terserOptions: {
                    compress: {
                        passes: 3
                    }
                }
            })
        ]
    }
}

Seems like a single compression pass in terser is not enough to compress this code.
cc @evilebottnawi maybe we should increase the default?

@sokra I’m afraid that this could have a very negative effect on build speed. I will look deeply today

@sokra thanks a lot for the pointer I had looked at terser options but I was at a loss which to enable. Your configuration indeed helps with the sample I provided.
Unfortunately for me it seems my reproduction was too simple, once I reinject the proposed change in the next.js build (even upping the passes to 30) the inlining comes back. I'll try digging in next.js now.

Ok. Please create a new repro case if you want more help.
 /*#__PURE__*/ "X" is not valid. /*#__PURE__*/ f() is valid.

/#PURE/ has only an effect if it is in front of a function call.

I was unaware of this specificity, thanks again.


Dev storageimportexport microsoft.import export 2016 11 01

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

I have added new version of api swagger along with examples and have reverted changes from swagger and examples of previous version of API

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Looks like this is dupe of https://github.com/Azure/azure-rest-api-specs/pull/10124
@nivats please confirm.

@nivats could you please confirm this PR is still valid? If not, I am gonna close it.

Hi Gaurav,
I will close this PR as original PR has been merged and this stayed as duplicate it seems.
Thanks
Nishu Vats
From: njucz<EMAIL_ADDRESS>Date: Thursday, 3 September 2020 at 7:53 AM
To: Azure/azure-rest-api-specs<EMAIL_ADDRESS>Cc: Nishu Vats<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-rest-api-specs] Dev storageimportexport microsoft.import export 2016 11 01 (#10110)
@nivatshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnivats&data=02|01|Nishu.Vats%40microsoft.com|a8072cf2020a4c3b31ab08d84fb05483|72f988bf86f141af91ab2d7cd011db47|1|0|637346966040149548&sdata=EvIOhcuhR4Y%2Bl%2BfMUZEC1MA7HNcgWk8wpgs7K2SO4aU%3D&reserved=0 could you please confirm this PR is still valid? If not, I am gonna close it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fpull%2F10110%23issuecomment-686193416&data=02|01|Nishu.Vats%40microsoft.com|a8072cf2020a4c3b31ab08d84fb05483|72f988bf86f141af91ab2d7cd011db47|1|0|637346966040149548&sdata=sTAK%2F%2Fg4oyDV4cSXX5VDj0pEZj8CauZf397quTzGBMA%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJ7TGMYELMWCO3TMDZGJKKDSD34ZVANCNFSM4OYSBLBQ&data=02|01|Nishu.Vats%40microsoft.com|a8072cf2020a4c3b31ab08d84fb05483|72f988bf86f141af91ab2d7cd011db47|1|0|637346966040159543&sdata=nbzSYq%2BFHYWBEEADBv5YRipzr39Z%2BUYD1kly6PG0LB8%3D&reserved=0.


CI: Re-enable integration tests

#9 re-enables make build in the CI, but make test is still failing. Needs more investigation.

#35 solved this and we have #37 to track adding tests for spin registry push


feat(cluster): pass target_databases to custom-queries

This PR is linked to the issue https://github.com/cloudnative-pg/charts/issues/479
I pushed it to the branch dev/479 but the link didn't seem to work :(

I now got the same problem for the "primary" key of the custom queries.
I changed it to just pass everything straight into the configmap.
Maybe the pipeline retry is going to clear the failed pipeline timeout ^^


[Feature Request] Support for Facebook payments

Bot Info

SDK Platform: Node.js
SDK Version: 3.15.0
Active Channels: Facebook
Deployment Environment: Channel Registration

Issue Description
I have a lot invested in Bot Framework, and now realized it's not capable of handling Stripe payments natively through Facebook. I had been led to believe that I could just use SourceEvent to pass the code.
Am I correct in assuming that I will need to bypass Microsoft's channel registration, and write my own Facebook webhook connection to allow this? The apps are hosted on my own servers.

This issue is tracking all Feature Requests for FB Messenger: https://github.com/Microsoft/BotBuilder/issues/4360

Help me!
Thomas
On Sat, May 26, 2018, 03:11 Jason Haala<EMAIL_ADDRESS>wrote:

Bot Info

SDK Platform: Node.js
SDK Version: 3.15.0
Active Channels: Facebook
Deployment Environment: Channel Registration

Issue Description
I have a lot invested in Bot Framework, and now realized it's not capable
of handling Stripe payments natively through Facebook. I had been led to
believe that I could just use SourceEvent to pass the code.
Am I correct in assuming that I will need to bypass Microsoft's channel
registration, and write my own Facebook webhook connection to allow this?
The apps are hosted on my own servers.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotBuilder/issues/4664, or mute the thread
https://github.com/notifications/unsubscribe-auth/AM3U2SuRCnf56UpzIOJRt60H-oQ-_ieDks5t2SpcgaJpZM4UO3EP
.


python3Full.withPackages (ps: [ps.virtualenv]) no longer builds

Python withPackages environments can no longer include virtualenv (and a whole lot of other packages). The command

nix-build --no-out-link -E 'with (import  {}); python3Full.withPackages (ps: [ps.virtualenv])'

fails to build in current versions of master because of the following error:
[...]
Found duplicated packages in closure for dependency 'py':
  py 1.9.0 (/nix/store/rng1bjykyyn9szqkjqp9l2cy4hflwkzy-python3.8-py-1.9.0/lib/python3.8/site-packages)
  py 1.9.0 (/nix/store/scxn78yv6fgcjkxc3rxv5xbyrmh8bwin-python3.8-py-1.9.0/lib/python3.8/site-packages)
Found duplicated packages in closure for dependency 'toml':
  toml 0.10.2 (/nix/store/5z2vm93qapr07m3zwy0xyb3csndray1i-python3.8-toml-0.10.2/lib/python3.8/site-packages)
  toml 0.10.2 (/nix/store/wq9j40q3zc9fps1pmm0xc89dk2wid5jw-python3.8-toml-0.10.2/lib/python3.8/site-packages)
Found duplicated packages in closure for dependency 'wcwidth':
  wcwidth 0.2.5 (/nix/store/47g8s5nhlv956yhpgyanqi5ybbmvk5jf-python3.8-wcwidth-0.2.5/lib/python3.8/site-packages)
  wcwidth 0.2.5 (/nix/store/xk5h4z2ggf38bvj7344qqjv8kbbh1a7i-python3.8-wcwidth-0.2.5/lib/python3.8/site-packages)

Package duplicates found in closure, see above. Usually this happens if two packages depend on different version of the same dependency.

According to git bisect, that issue was introduced in e975b7508269b2f487ffd4a2ecc0aded28ce0ec3 by @fabaff. I'm not sure whether it is really the cause of that issue, though, because I tried reverting it and that did not seem to fix the build.

Yikes, these type of errors are bad. Turns out it was a regression from improving cross-compilation support https://github.com/NixOS/nixpkgs/pull/114538.

Fixed with https://github.com/NixOS/nixpkgs/pull/114538


improve end to end control latency measurement

pixracer (multicopter)
nsh> perf
fmu control latency: 31096 events, 6985713us elapsed, 224us avg, min 201us max 566us 16.366us rms

pixracer (fixedwing)
nsh> perf
fmu control latency: 3182 events, 1534797us elapsed, 482us avg, min 171us max 5798us 395.665us rms

pixhawk 2 (multicopter)
nsh> perf
fmu control latency: 0 events, 0us elapsed, 0us avg, min 0us max 0us 0.000us rms
io control latency: 1016 events, 290388us elapsed, 285us avg, min 225us max 621us 33.261us rms

pixhawk 2 (fixedwing)
nsh> perf
fmu control latency: 0 events, 0us elapsed, 0us avg, min 0us max 0us 0.000us rms
io control latency: 5014 events, 2387356us elapsed, 476us avg, min 156us max 1745us 362.783us rms

pixhawk 2 (VTOL)
nsh> perf
fmu control latency: 29874 events, 445943798us elapsed, 14927us avg, min 3747us max 28028us 6376.741us rms
io control latency: 25358 events, 10419801us elapsed, 410us avg, min 316us max 1397us 35.020us rms

Note how VTOL FW output. This is mainly the result of the fmu module running in the high priority work queue. A small portion is also the vtol attitude controller. The FW numbers are still only counting the time from the vehicle_attitude publication.

Comments addressed and I also added the perf counter to linux_pwm_out, snapdragon_pwm_out, and pwm_out_sim for consistency.


Add icon set to IED editor containers

As a CoMPAS user
I want to see better distinguished IED sections by using icons in the separate IED containers
So I can have a quicker recognition of different IED sections.

OpenSCD design guidelines: https://material.io/design

These only need icons: IED (see the exsiting icon), server, LD, accespoint (communication icon)
https://materialdesignicons.com/

Proposal:
IED: mdi:developer-board
Accespoint: mdi:access-point
Server: mdi:server
Logical device: mdi:gate-or / mdi:code-greater-than-or-equal / mdi:consolidate


Contact Us or Call Phone Number missing link and number

Contact Us should link to Contact form and call should be followed by a phone number instead of placeholder text.

sample data issue


fix: multiapp ui fixes

What new features does this PR implement?
Please summarize the features that this PR implements. As relevant, please indicate the issues that the PR closes.

platform: adjusts simulation-log-component family ui layout (fixes #4761)
platform: adjusts simulation-log-component whitespace in log tab (fixes #4763)
platform/dispatch: allows window to reset to (0,0) upon dispatch submission (fixes #4762)
platform: implements fixed width in dispatch component (fixes #4764)
dispatch: adjusts simulation-log-component family ui layout (fixes #4766)

What bugs does this PR fix?

fixes a major ui issue in simulation-log component for both platform and dispatch apps

Does this PR introduce any additional changes?

style(ui): implements several continuity stylings for both platform and dispatch apps

How have you tested this PR?

CI/CD & compilation testing

Additional information
This is the first adjustment pull request since the most recent deployment of the dev to prod after over a year. Since then, numerous updates and changes occurred across the entire stack, resulting in the need for such a re-deployment.

:tada: This PR is included in version 9.52.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Download button on website is broken

Triggers an error: Uncaught (in promise) ReferenceError: url is not defined

@jxhug You said that the urls are being automatically grabbed from appcast.xml right? The link there (https://github.com/phoenixlauncher/phoenix/releases/download/v0.1.2-beta/Phoenix.dmg) is valid so something in your button code isn't working right

will look

fixed


Revert "Disable ARM builds until there is an upstream fix"

This reverts commit 7be1d8f105339aad18b6c27016e95e8440c062a3.

According to https://packages.ubuntu.com/focal-updates/openssl Ubuntu is still on openssl 1.1.1f but the fix is in 1.1.1i.
Or have you tried it on your ARM Mac already?


⚠ Samsung has degraded performance

In b3b2795, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2118 ms

Resolved: Samsung performance has improved in 2cea5fb.


Document the reasons for not using a released version of libgit2

To make life easier for packagers, could you document and update the reasons why this package requires a particular commit of libgit2?
For the current version I am not seeing any reason this wouldn't work with v0.25.1 upstream, but the current submodule commit a59545de5e57769f858ed2657b9fb850675f227f differs from this by about 105 commits. The CHANGELOG diff is:
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8544ac451..0ae75e156 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -3,12 +3,20 @@ v0.25 + 1

 ### Changes or improvements

+* `GIT_MERGE_OPTIONS_INIT` now includes a setting to perform rename detection.
+  This aligns this structure with the default by `git_merge` and
+  `git_merge_trees` when `NULL` was provided for the options.
+
 ### API additions

 ### API removals

 ### Breaking API changes

+* `clone_checkout_strategy` has been removed from
+  `git_submodule_update_option`. The checkout strategy used to clone will
+  be the same strategy specified in `checkout_opts`.
+
 v0.25
 -------
 [.. stuff below this hopefully isn't relevant since it's just retroactively updating descriptions of what is already in 0.25 ..]

git_submodule_update_option does not seem to be used by this rust crate, it's commented out in lib.rs.

Historically libgit2 has never had a released version with all the various bug fixes that we needed .If it does now then I'd love to move to a released version! If a bug fix comes in though that we need I'd be likely to switch away from a released version to get the bugfix.

I've just updated to 0.25.1, which should have fixes for all those, and the readme now has a note.

Thanks!


Add basic dashboards to qhub-hpc deployment by default

This would make it easy to demo dashboards feature

Similar to https://github.com/Quansight/qhub/tree/main/qhub/template/stages/07-kubernetes-services/modules/kubernetes/services/jupyterhub/files/examples. Ensure that there are examples of basic dashbaords for qhub-hpc.
Additionally check that each dashboard work.


Resolving bug in config refactor.

Summary of the Pull Request
What is this about?
A bug was introduced with the recent config refactor. list commands were not working properly. Resolving with this PR.
PR Checklist

[ ] Applies to work item: #xxx
[ ] CLA signed. If not, go over here and sign the CLI.
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

Codecov Report

Merging #2811 (7afd834) into main (c5700b4) will decrease coverage by 3.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2811      +/-   ##
==========================================
- Coverage   29.93%   26.80%   -3.13%
==========================================
  Files         324      125     -199
  Lines       38990    13236   -25754
==========================================
- Hits        11671     3548    -8123
+ Misses      27319     9688   -17631

Impacted Files
Coverage Δ

src/agent/input-tester/src/logging.rs

src/agent/onefuzz/src/auth.rs

src/agent/onefuzz-agent/src/agent/tests.rs

src/agent/coverage/src/binary.rs

src/agent/onefuzz-agent/src/done.rs

src/agent/onefuzz-file-format/src/hex.rs

src/agent/coverage-legacy/src/sancov.rs

src/agent/win-util/src/file.rs

...agent/onefuzz-task/src/tasks/regression/generic.rs

src/agent/onefuzz/src/syncdir.rs

... and 189 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


VS2017 Pack includes GitVersioning as a dependency in nupkg

Is this a known issue?

Yes: https://github.com/NuGet/Home/issues/4125
In the meantime, just add PrivateAssets="all" to your PackageReference item.

I understand it might be out of scope for you, but it would be nice to have info about some of these gotchas in the GitVersioning docs, since the Core/Standard/VS2017 experience is so different from Framework/VSearlier. It would save people like me from asking all these questions!

Very good point. The https://github.com/AArnott/Nerdbank.GitVersioning/blob/master/doc/nuget-acquisition.md doc hasn't been updated.

The correct syntax appears to be:
<PackageReference Include="Nerdbank.GitVersioning" Version="1.6.25">
  <PrivateAssets>all</PrivateAssets>
</PackageReference>

(The comment above says PrivateAssets="all"and the doc page says PrivateAssets="true".)

Whoops. Thanks for catching. I fixed it to all instead of true. As for the child-element vs. attribute, both work with MSBuild 15.1.

I used the element, because that's what was first mentioned in the other thread you linked to. Now that I try it, I see that the attribute also works, although it's not one of the attributes suggested by IntelliSense. Makes me wonder if that usage is something undocumented that shouldn't be relied on. (The PrivateAssets element is suggested by IntelliSense.)

It definitely works by a reliable design: metadata can now be expressed as attributes. Intellisense is evidently lacking.


Document (un-)supported AsciiDoc features

Using the TOC of documentation at https://docs.asciidoctor.org/asciidoc/latest as the list of items that can potentially be supported.

Wiki page about AsciiDoc Compatibility Matrix closes this.


Populated opengcs with initial GCS soruce files

@soccerGB,
Thanks for your contribution.  To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
The agreement will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot


Fix broken edit filters

fix file filter restriction was applied to folders: / was not allowed in folder flters
fix \\ prefix was no longer allowed even in v1 filters
add same non allowed characters to file filter

The last commit broke the directory edit filters + it broke \\ prefix for v1 filter

About / in file filter: can you keep it allowed ? It doesn't break anything, and doesn't slow the code if no / included
I really need it to exclude specific files in a folder only: exclude /cache/data/*.log while keeping all other files in the cache folder
I also need to exclude a specific 2 Gb file:  /cache/debug/cache.dat

Hope you understand this use scenario. FolderSync could support this.
Best regards


Support only containerized build

Fixes #227
cc @duglin

in general I'm +1 on this but I'll hold off reviewing until #230 goes in as that'll force a big rebase.
But we need more people to buy into this since it might be controversial.

I am willing to be convinced but am starting from a strong do not want
standpoint.
On Fri, Jan 6, 2017 at 3:52 PM Doug Davis<EMAIL_ADDRESS>wrote:

in general I'm +1 on this but I'll hold off reviewing until #230
https://github.com/kubernetes-incubator/service-catalog/pull/230 goes
in as that'll force a big rebase.
But we need more people to buy into this since it might be controversial.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/service-catalog/pull/231#issuecomment-271003022,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWXmB7iE6KYpZDmnByyiAPeOsPRlRk7ks5rPqmPgaJpZM4Lc8Ek
.

@pmorie since you're willing to be convinced...
It's likely that we've all been in one or more of the following positions before:

Spending more time that we'd like ensuring we have the right toolchain to work on product x.
Having difficulty troubleshooting someone else's issue because you can't account for minute environment differences. We've all heard "it worked on my machine."

I often cite these as reasons why using Docker to provide a standardized development environment, where changes to the environment itself are tracked and versioned along with the rest of our codebase, is A Good Thing™. You probably didn't need to be sold on this idea, and it's great that we already do this...
The trouble is that we don't enforce that way of doing things. As long as we support the option to bypass all of that by building out-of-container, some people will, and that means we don't get the full benefit. What's worse is that our Makefile incurs extra complexity to support that option that we might wish people wouldn't actually exercise. 😿
As it stands now, here are three different permutations we support:

In-container build

Whether on Mac or Linux should be of only minor consequence

Out-of-container build on Mac
Out-of-container build on Linux

It's tedious having to test all these permutations each time we make an improvement to the build/test process.
But since you were a good sport in saying you were willing to be convinced, I am willing to be convinced in the other direction. Can you articulate specific reasons you would like to see continued support for out-of-container builds?

I can't speak to the debugging side of things because I don't use any tools for debugging - I get by with just trying to do the test's steps manually. So, from my perspective, the most important thing is to make sure that our testing infrastructure is easy to follow and there's limited "magic".  If a newbie can look at a test and easily figure out how to reproduce those same steps outside of the test framework we have then I tend to think we've complicated it too much. This also means that it should be easy for someone new to add new tests too - no big learning curve.
How does this relate to @pmorie's comment? People should be able to use whatever debugging tools they want, and they should be able to set them up to reproduce a particular test easily/quickly - meaning look at a test and be able to know how to manually reproduce that test outside of the framework. So, running in a container (which should for the most part be just wrapping some command with "docker run") shouldn't really impact much.
Side note: this is why I had such a negative reaction to the possibility of using ginko. I love tools/helper-funcs to save me typing, but not to hide (or introduce) complexity.

There are definitely benefits to hermetic (containerized) builds so in principle I don't object, but we need to ensure the following use case is supported: CI/CD pipeline which uses containers as workers. That's the Jenkins setup we are using. I am not sure if with this change it will actually work because docker-in-docker is quite tricky.
@krancour, can you please demonstrate that with these changes one can spin up Jenkins worker - a container - and all make commands will be supported? build, tests, package into Docker images, push etc.?
Personally, when I did the initial set up the only way to enable running CI/CD worker in container was to support non-containerized build in our makes; otherwise, the build would be running docker in docker which works in some cases but requires amount of control over the worker container that I could not attain in Jenkins/Kubernetes combination.
Perhaps it is not a goal to support CI/CD with containerized workers, although there would be an element of irony in it. Or perhaps it works but to my knowledge this project is not yet set up to demonstrate it.
Thus, I'd strongly urge to wait, build a serious CI/CD (or revive the one we had but which got broken by the series of make changes and refactorings) and only then proceed with that safety net.
Just my 2c though.

@martinmaly I'm interested in trying to setup what you asked about. But to be clear, are you running Jenkins itself in a container or is Jenkins running natively and the jobs it starts runs in containers?

Jenkins master runs on a VM and uses Kubernetes Plugin to spin up workers.
I actually tried to have the master run on Kubernetes as well but I had difficulty setting it up so I had to fall back on a VM-hosted master.

FWIW, just did this and it worked:
root# docker run -ti --privileged ubuntu bash

root@ecb0857919c4# apt-get -y update
root@ecb0857919c4# apt-get -y uprade
root@ecb0857919c4# apt-get -y install curl git make
root@ecb0857919c4# curl -sSL https://get.docker.com/ | sh
root@ecb0857919c4# service docker start
root@ecb0857919c4# git clone https://github.com/kubernetes-incubator/service-catalog.git
root@ecb0857919c4# cd service-catalog
root@ecb0857919c4# DOCKER=1 make all images

of course this all depends on whether the jenkins container has the right privileges to run docker in docker.

wow, cool! Hopefully it'll also work on the k8s Jenkins worker.

https://github.com/kubernetes-incubator/service-catalog/pull/231#issuecomment-271107587

root@ecb0857919c4# apt-get -y uprade

... uprade ? j/k

yea well I had do some manual extraction from my "script" output :-)

@martinmaly I tried to look back on our conversation history in Slack and found it was gone. (I think the k8s Slack doesn't preserve history for as long as I'd like.) Anyway... I was looking there to try to recall the reasons out-of-container build was even a thing. You've reminded me of it now-- Jenkins slaves. Thanks!
I'm not going to close this just yet, but I am going to see if I can come up with a more palatable, k8s-inspired alternative that allows us to build in or out-of container, but with less complexity.

Trying to provide some nonpartisan analysis here: this patch doesn't prevent doing things directly on the host or within an editor. You won't have a make target for them.
For example, I have been building & testing, both in the console and in-editor, using raw commands (go et al.). See below for how to do so.
Testing on the Host
If you have the correct go toolchain, Go environment, glide installed, and dependencies installed, run go test $(glide nv) to unit-test all packages in the repo. I already do this with a hotkey in atom.
Debugging on the Host
Many debugging tools rewrite code and then run go test on the rewritten source. godebug, for example, is a one-liner on the console.
A few debugging tools execute against machine code directly, so they need to go build. This is the most complex workflow with standard (non-make) tools because you need to know which package to build (you can't build them all because there are multiple mains).
That is, you can't go build ./..., you have to go build ./something-with-a-main instead.
CI/CD
Looks like @krancour is still looking at ways to provide scripts that facilitate CI/CD as it stands now. Note that we have a meeting scheduled for 1/11/2017 to discuss the future of CI/CD. We should discuss options to run containerized builds/tests on our CI/CD system of the future.
Using a hermetically sealed "dev container" or VM (we do not want to do this. happy to expand on why) is the only way I know of to ensure the same dev, test and e2e environments

On the plus side, if we did just docker builds then our CI would be about 1/2 the time since we build/test both ways  :-)

On the plus side, if we did just docker builds then our CI would be about 1/2 the time since we build/test both ways :-)

This is actually a pretty powerful argument to me.  I am leaning towards saying let's go for this, but make it explicit that we expect people to do whatever they need to to test / debug locally.

Closed in favor of #238


Crash

Crash while first starting and connect to server. (just for first time)

Do you have any reliable reproduce, otherwise I can't help you there.

Make sure to Run as Administrator. You should crash if you don't.


NotebookCellMetadata conflicts with user defined metadata

Based on the type definitions, Notebook Cell metadata has the following properties:

inputCollapsed
outputCollapsed

However VS Code adds its own custom propperties into this object which causes issues.

I think these internal properties lastRunSuccess executionOrder should not be stored in here, as these are available via the lastExecutionSummary.
I can see plenty of issues here, its possible for users to edit the metadata and cause issues in VS Code or VS Code blowing away user defined metadata & overwriting it with its own internal state.
@jrieken @roblourens /cc

I think these internal properties lastRunSuccess executionOrder should not be stored in here, as these are available via the lastExecutionSummary.

We talked about storing execution state not as internal metadata but outside the document. Tho unsure what todays plans are

Tho, generally these "conflicts" can arise we recommend that extension have all their metadata under one key, like metadata.jupyter.foo and metadata.jupyter.bar

We recommend that extension have all their metadata under one key, like metadata.jupyter.foo and metadata.jupyter.bar

Then I would suggest bringing back the custom property, else its really pointless having an object with ability to store any data, that makes it look like anything can be stored (when your recommendation is the opposite). I.e. someone creating an extension tomorrow might not come across this issue. I.e. i'd prefer if we went back to the older api:
    export class NotebookCellMetadata {
        /**
         * Whether a code cell's editor is collapsed
         */
        readonly inputCollapsed?: boolean;

        /**
         * Whether a code cell's outputs are collapsed
         */
        readonly outputCollapsed?: boolean;

        /**
         * Additional attributes of a cell metadata.
         */
        readonly [key: string]: any;

Instead it should be:
    export class NotebookCellMetadata {
        /**
         * Whether a code cell's editor is collapsed
         */
        readonly inputCollapsed?: boolean;

        /**
         * Whether a code cell's outputs are collapsed
         */
        readonly outputCollapsed?: boolean;

        /**
         * Additional attributes of a cell metadata.
         */
        readonly custom:  Record<string, any>;

This way there is never any ambiguity nor any accidental conflicts.

This way there is never any ambiguity nor any accidental conflicts.

Really? What about the other extension that also stores stuff inside custom? You have the exact same problem except for the potential conflict with VS Code's properties. Even with the custom-property extensions are expected to create a "root node" under which their data goes.
Also note that our strategy is very similar to nbformat: https://nbformat.readthedocs.io/en/latest/format_description.html#metadata

Because it is a shared namespace, any custom metadata should use a sufficiently unique namespace, such as metadata.kaylees_md.foo = “bar”.


Application icon hard to read / lens should have a "real" logo

What would you like to be added:
I think, the icon that currently ships with Lens is not suited to represent the application.

it is barely readable / understandable (especially in small sizes such as 16x16 or even 32x32)
It does not contain any pictogram and basically contains only the text "Lens by Kontena"
Kontena has ceased operations :-( -- even though I do believe, that it's name should be mentioned somehow, I have the feeling that the icon might be the wrong place

Why is this needed:

Improve UX
Establish a strong (app) brand

Here is a very first proposal:

A shutter lens that zooms onto the Kubernetes logo. Well,......

Yes, I agree. We need to change the icon and have proper logo for the app.
Same icon/logo should be used throughout the app and any related services like https://k8slens.dev website, https://twitter.com/k8slens Twitter account, this GitHub account etc.

This shutter concept with K8S logo is very nice. Some ideas / feedback:

I'd probably change the shutter shape from "hexagon" to "heptagon" to match kubernetes logo shape. And have K8S logo in the center.
The choice of colors is important too; I'd change the color of kubernetes logo to something that is more bright. To cut some corners, we could simply use #3d90ce in memory of Kontena (that was Kontena brand color). The added benefit in here is that we don't need to change color throughout the app UI itself since kontena primary color is already used in there. The color of shutter itself would work well in gray.
We could try to use some subtle gradients in RGB version.

Lens 3.1 will have a new logo that is used already on the website. I think this issue is still valid, we need a better logo at some point.

Website just got a new "shutter" like logo, we should also change app logo. https://github.com/lensapp/lensapp.github.io/pull/2


Rumour Infobox not disabling

I have the infobox disable time down to 1 minute and force show info box unchecked but the infobox never actually hides itself

Turn on force show and turn it back off that should fix it


No C++11/14 support even if it's explicitly specified in init.vim MacOS

OS: Mac OS High Sierra
NVIM: v0.2.2
Deoplete-clang2: 787dd4dc7eeb5d1bc2fd3cefcf7bd07e48f4a962
Summarry: There is no functions suggestions from C++11 and above even if
let g:deoplete#sources#clang#std#cpp='c++14' is set.
Everything work fine from C++98.
My init.vim
inoremap jj <esc>
inoremap <C-k> <return>
map <C-n> :NERDTreeToggle<CR>
map <C-s> :call CurtineIncSw()<CR>
map <space> /
map <c-space> ?
vnoremap . :norm.<CR>
let mapleader = "\<Space>"
set ignorecase
set incsearch

set nu
set nohlsearch
syntax on
call plug#begin()
if has('nvim')
  Plug 'Shougo/deoplete.nvim', { 'do': ':UpdateRemotePlugins' }
else
  Plug 'Shougo/deoplete.nvim'
  Plug 'roxma/nvim-yarp'
  Plug 'roxma/vim-hug-neovim-rpc'
endif
Plug 'tpope/vim-surround'
Plug 'Shougo/neopairs.vim'
Plug 'vim-airline/vim-airline'
Plug 'tweekmonster/deoplete-clang2'
Plug 'SirVer/ultisnips'
Plug 'scrooloose/nerdtree'
Plug 'mhinz/vim-janah'
Plug 'honza/vim-snippets'
Plug 'neomake/neomake'
Plug 'ericcurtin/CurtineIncSw.vim'
call plug#end()
let g:neopairs#enable = 1
let g:deoplete#sources#clang#flags = ['-darwin=10.13']
let g:deoplete#enable_at_startup = 1
let g:deoplete#sources#clang#libclang_path="/Library/Developer/CommandLineTools/usr/lib/libclang.dylib"
let g:deoplete#sources#clang#clang_header ="/usr/local/Cellar/llvm/5.0.0/lib/clang"
let g:chromatica#enable_at_startup=1
let g:chromatica#libclang_path="/Library/Developer/CommandLineTools/usr/lib/libclang.dylib"
let g:deoplete#sources#clang#std#cpp='c++14'
"--------------------
" ultisnips
"--------------------
" Trigger configuration. Do not use <tab> if you use https://github.com/Valloric/YouCompleteMe.
"
" ATTENTION: don't map this to keys which are the first part of a 'two part'
" command. E.g. don't map to `<c-g>` because `g` is part of `gt`, `gT`, ...
" This will slow down jupming between tab stops, but only when 'vim-surround'
" is installed.
let g:UltiSnipsExpandTrigger="<C-j>"
let g:UltiSnipsJumpForwardTrigger="<C-j>"
let g:UltiSnipsJumpBackwardTrigger="<C-h>"

" If you want :UltiSnipsEdit to split your window.
let g:UltiSnipsEditSplit="vertical"

let g:UltiSnipsSnippetDirectories=["mysnippets", "copiedsnippets"]
call neomake#configure#automake('nw', 750)
autocmd ColorScheme janah highlight Normal ctermbg=235
colorscheme janah

Interesting fact:
Completion works with no regard for the following globals presence.
g:deoplete#sources#clang#libclang_path="/Library/Developer/CommandLineTools/usr/lib/libclang.dylib"
g:deoplete#sources#clang#clang_header ="/usr/local/Cellar/llvm/5.0.0/lib/clang"

Completion still works although I put this variables in a comment section. Weird!

Thanks for using my plugin @Posto578  ! I wrote a new little one recently. Feel free to try and star if you like! :smile:
https://github.com/ericcurtin/VimBlame.vim


Change default value of libsc preference

As discussed in #73. I also added a short section in the docs about troubleshoots for the preferences in P4est.jl.

I like this!  Nice addition @JoshuaLampert.


How to use DumpUnitary utility in UnitaryPatterns notebook

I tried the following steps:

Built the DumpUnitary project to produce a NuGet package.
Copied the generated .nupkg file to the UnitaryPatterns kata.
Set up NuGet.config file so that it allows the project to discover a NuGet package in the current folder in addition to the standard sources.
Added the following cells in IQ# notebook

%package DumpUnitary::1.0.0
%workspace reload
open Quantum.DumpUnitary;
%simulate DumpUnitaryToFiles N=3 unitary=MainDiagonal

Getting the following error when running simulate
Received invalid parameters. Please fix and try again:
 unitary: Error converting value "MainDiagonal" to type 'Microsoft.Quantum.Simulation.Core.ICallable'. Path '', line 1, position 14.

I've never tried calling DumpUnitary from Q# notebooks (it's so old it predates the notebooks support for Q#!), but I think %simulate doesn't like taking a callable as a parameter. I'd suggest writing a wrapper operation without any parameters that would call DumpUnitary with the parameters you want, and %simulate that operation.

Thank you @tcNickolas for the help. Now, I am able to call it through UnitaryPattern notebook

Great!
Just to offer another option, you can use DumpOperation similarly to dump the raw matrix, without conversion to a pattern, if you need more information about the unitary.

Thank you @tcNickolas. Would be glad to try it out.


operator manifest: improve error message

Inform users that they have to update container.yaml config.
Signed-off-by: Martin Bašti<EMAIL_ADDRESS>Maintainers will complete the following section:

[x] Commit messages are descriptive enough
[x] "Signed-off-by:" line is present in each commit
[x] Code coverage from testing does not decrease and new code is covered
[x] JSON/YAML configuration changes are updated in the relevant schema
[x] Changes to metadata also update the documentation for the metadata
[ ] Pull request includes link to an osbs-docs PR for user documentation updates
[ ] New feature can be disabled from a configuration file

RN:

When mapping for operator repo replacements is missing or ambiguous tell user to specify mapping in container.yaml


Feature: Add icon/SVG specific options?

Working on an app that requires a custom twitter button as icon (but no text) and would love to leverage this code!
Is there any way to pass in a custom SVG without altering the module itself? I see you pass props for: tag, text content, dimensions, style/className (for component but not icon), and whether or not to show the SVG icon.
But how might one pass in their own SVG path with a custom size? For example, I'm trying to use a variation on the twitter logo featured here then alter the dimensions, fill, etc.
It would be great if it were possible to pass in some svg options with a specified {path:"", width, height} and/or perhaps add a unique className for css fills, transforms, etc.

Hi marcaaron,
I looked at the code, and find out that actually you can change content of button, but I forgot to put it in documentation. There is children prop, and so if you put your desired SVG into component together with text that you want you will override current content of SVG button. So that would look like this:
//convert svg into react element
const TwitterIcon = React.createClass({
  render() {
    return (
      <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24"><path d="M19 0h-14c-2.761 0-5 2.239-5 5v14c0 2.761 2.239 5 5 5h14c2.762 0 5-2.239 5-5v-14c0-2.761-2.238-5-5-5zm-.139 9.237c.209 4.617-3.234 9.765-9.33 9.765-1.854 0-3.579-.543-5.032-1.475 1.742.205 3.48-.278 4.86-1.359-1.437-.027-2.649-.976-3.066-2.28.515.098 1.021.069 1.482-.056-1.579-.317-2.668-1.739-2.633-3.26.442.246.949.394 1.486.411-1.461-.977-1.875-2.907-1.016-4.383 1.619 1.986 4.038 3.293 6.766 3.43-.479-2.053 1.08-4.03 3.199-4.03.943 0 1.797.398 2.395 1.037.748-.147 1.451-.42 2.086-.796-.246.767-.766 1.41-1.443 1.816.664-.08 1.297-.256 1.885-.517-.439.656-.996 1.234-1.639 1.697z"/>
      </svg>
    );
  }
});

  //use icon like this in other component
  <div>
        <TwitterLogin loginUrl="http://localhost:4000/api/v1/auth/twitter"
                      onFailure={this.onFailed}
                      onSuccess={this.onSuccess}
                      requestTokenUrl="http://localhost:4000/api/v1/auth/twitter/reverse"
                      showIcon={true}
                      customHeaders={customHeader}>
          <TwitterIcon/> Twitter Login
        </TwitterLogin>
      </div>

I will update documentation. Do you still think that there is need for icon, iconProps and iconClassName props?

Nice! Very cool! No I think adding options is probably unnecessary if you can overwrite the svg content but up to you :)

Sorry it took me that much time to find that out. But I had really crazy week.
I will add option to change size and color of icon. I could imagine that that could be useful if you desire just to style button.
Thank you very much. I think that this will improve documentation a lot.


Fix ENTRYPOINT to use 'dbt'

resolves #2470
This is a copy of #2471 targeting dev/octavius-catto after @beckjake pointed out it is a bugfix
Description
Change the entrypoint to be able to pass arguments and use DBT as it is used outside the container
Checklist

[X] I have signed the CLA
[X] I have run this code in development and it appears to resolve the stated issue
[X] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

Just rebased it against the bugfix branch, updated the CHANGELOG and removed the Dockerfile changes @beckjake

I think you accidentally pulled in some tests from dev/marian-anderson in your changelog branch!

and oops I included files I didn't mean to include

Should be good now!

Added! Although the change is so small it feels undeserved 😆


Add front-end test pipeline

Add a way to run tests for the front-end, too. This is a bit of a hassle, since Truffle decided to roll their own version of Mocha with some things injected.

People should be free to choose this themselves, so I am closing this.


[CI] Add wheels and java-jars to vcpkg group tasks

Describe the enhancement requested
As suggested here: https://github.com/apache/arrow/pull/42171#issuecomment-2172095401
We could add the java-jars and wheels to the vcpkg group on our tasks
Component(s)
Continuous Integration

Issue resolved by pull request 43419
https://github.com/apache/arrow/pull/43419


Docs: External DNS

Description
Create an example doc page showing how to integrate with external-dns to allow whitelabel domains to be created automatically.
Use Case
This is a good example of integrating with other tools in the ecosystem that we want to show
Related issues
No response

https://ngrok.com/blog-post/ngrok-ingress-controller-differentiators we did do a blog post!


comparative experiment

Dear author, thank you very much for your work.
I have some questions about the comparative experiment.
How can we ensure that the random, entropy, core-set, and CDAL algorithms have the same MAP score in the initial round as shown in Figure 5 of the paper?
Because when I conducted my own experiments, I found that even if I used the same initial dataset, there were still differences in the initial round results. I think this may be related to the initialization parameters of the model, the random selection of samples in the batch, etc., which may cause the model to produce different weights and biases during the training process. Could you please advise me on how to address this issue?

Thanks for attention to our work.
The reason why there are still differences in the results of setting the same random seed and using the same initial labeled set may be that the convolution algorithm selected by the model is different, which can be solved by adding  --deterministic after the training command.
When --deterministic is set to True, it will make the network no longer search for the most suitable convolution algorithm (cudnn.benchmark = False), but use the default convolution algorithm (cudnn.deterministic = True), which helps to enhance the reproducibility of the results, but may reduce the running speed of the network.

Thank you very much for your reply. It was very helpful and I will use your suggestion to redo the comparison experiment.


Feature request: option to save tags and favorites on external files.

Import and export data added in 0.9.4


Version bump to<EMAIL_ADDRESS>

Release notes at https://github.com/Squirrel/Squirrel.Windows/releases/tag/1.0.5, this adds the ability to use query parameters in update URLs

Thanks @paulcbetts!


Fix typo in FF_CreateIOManager issue #40

Fix typo in FF_CreateIOManager
Description
Fix typo in API
Test Steps
Cosmetics change, no actual step to reproduce.
Checklist:

[x] I have tested my changes. No regression in existing tests.
[ ] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Tested on a port for PIC32 that is not part of this porject.
Tested on Linux/POSIX using test/build-combination.
Related Issue
issue #40
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Please fix the failing formatting check.

Please fix the failing formatting check.

main is failing too: https://github.com/FreeRTOS/Lab-Project-FreeRTOS-FAT/actions/workflows/ci.yml
see: https://github.com/FreeRTOS/Lab-Project-FreeRTOS-FAT/pull/42
Will rebase once #42  is closed.


Seems Mojave broke the app

This is the first time I try this app so it might be something else that is causing this to fail.
I'm trying to open the app on a MacBook Pro (Retina, 15-inch, Mid 2015) with Mojave installed and 2 extra screens connected.
I installed the app with brew
brew cask info keycastr                                                                                 ✔  0.18   08:06:59
keycastr: 0.9.6
https://github.com/keycastr/keycastr
/usr/local/Caskroom/keycastr/0.9.6 (64B)
From: https://github.com/Homebrew/homebrew-cask/blob/master/Casks/keycastr.rb
==> Name
KeyCastr
==> Artifacts
KeyCastr.app (App)

After I add the app to Preferences -> Security & Privacy -> Accessibility I try to run the app and I get the following screen:

If after this I go again to Preferences -> Security & Privacy -> Accessibility the list is empty (although I had other apps there as well) and I can not add apps (I press the + sign I go through the motions of adding an app but nothing appears).

A reboot will fix the pane but if I try again I get the same results.
If you generate logs anywhere, let me know and I grab them.

For anyone following this thread, I have a half-assed fix but it works.
Add the following
    NSDictionary *options = @{(__bridge id) kAXTrustedCheckOptionPrompt : @YES};
    BOOL accessibilityEnabled = AXIsProcessTrustedWithOptions((__bridge CFDictionaryRef) options);

    if (!accessibilityEnabled) {
        if (error != NULL) {
            *error = [self constructErrorWithDescription:@"Could not create keyDown event tap!"];
        }
        return NO;
    }

to KCKeyboardTap.m, in this method -(BOOL) installTapWithError:(NSError **)error {.
So it looks like this
-(BOOL) installTapWithError:(NSError **)error {
    if (tapInstalled) {
        return YES;
    }

    NSDictionary *options = @{(__bridge id) kAXTrustedCheckOptionPrompt : @YES};
    BOOL accessibilityEnabled = AXIsProcessTrustedWithOptions((__bridge CFDictionaryRef) options);

    if (!accessibilityEnabled) {
        if (error != NULL) {
            *error = [self constructErrorWithDescription:@"Could not create keyDown event tap!"];
        }
        return NO;
    }


rollup how to package multi-page application？

hi,I would like to ask a question, rollup how to package multi-page application, it seems to be only a single entry (a string), unlike the webpack entry can be an array or object. My current solution is to traverse the rollup configuration file to generate multiple bundles, but can not generate a common bundle like webpack.
thanks a lot.

Hey, @tedyhy — this is probably a better question for either Stack Overflow or the Rollup repo. In general, though, once you get into more advanced use cases you'll probably have an easier time using Webpack 2, which offers the same tree-shaking benefits of Rollup, but also has extra tools for use cases like you've described.

thanks a lot @jlengstorf 😊


Hello,Iissnan.I created my blog with the NextT recently.Here is my question:I want to add the award function into my blog ,but after I do what you interduce in the instructions,there is no reward fuction in my blog.

Expected behavior

Actual behavior

Steps to reproduce the behavior
Link to demo site with this issue: N/A
Link(s) to source code or any usefull link(s): N/A
NexT Information
NexT Version:

[x] Master
[ ] Latest Release
[ ] Old version -

NexT Scheme:

[ ] All schemes
[ ] Muse
[ ] Mist
[x] Pisces

Other Information

Read Docs please.

this my theme-config imformation


Add new methods to get more details about a task

I needed to retrieve more specific details about Swarm tasks and as such I added new methods in order to get a task's slot number, the status timestamp and the status message of a task. This might be useful to others, reason for my pull request.

Cheers!

@mikejmoore I was wondering if my changes included in this PR #5 have been integrated into your code? if yes it can be closed.

@mikejmoore I actually found that in commit f04c416fcb8b146baa069590d6fa7e697b3d2b0a you implemented both my status_timestamp and status_message methods in task.rb but you did not take the slot method. Any reasons for not taking that method?

@mikejmoore unfortunately I never got an answer from you to my https://github.com/mikejmoore/docker-swarm-sdk/pull/5#issuecomment-372151832 above regarding the slot method. I am still wondering if you might have forgotten to add this method? Thank you very much in advance for your feedback.

@mikejmoore I would be very thankful if you could answer back in this PR and add the slot method too.


SyntaxError: invalid syntax. Can not import the package

I installed this package in my py2.7 environment, but after I import it I got this error.
I don't know how to fix it, beacause it seems all the code is right.
import test_tube
│Traceback (most recent call last):
│  File "<stdin>", line 1, in <module>
│  File "/home/andy/.conda/envs/dynet/lib/python2.7/site-packages/test_tube/__init__.py", line 5, in <module>
│    from .argparse_hopt import HyperOptArgumentParser
│  File "/home/andy/.conda/envs/dynet/lib/python2.7/site-packages/test_tube/argparse_hopt.py", line 38
│    def add_opt_argument_list(self, *args, options=None, tunnable=False, **kwargs):
│
│SyntaxError: invalid syntax

ummmm.  which version of test_tube?  is it only happening on python 2.7?


Stripping style and script tags in clean function

Hey mate, great module, just started using it, just wondering why i can't pull out any script tags, and i can see they're getting stripped in your clean() function.
This could be just what you want, but i'm actually wanting to parse these out! Ah well could just fork it ay.
Thanks again.
Cheers
Rob

Hey robert,
You are correct that, currently, we remove all script tags to make it easier to parse the html file. If you can come up with a solution in your fork that can handle parsing the script tag with out incorrectly removing html/including html tags that should not be please send us a pull request.
Thanks.


How to use angular2-multiselect-dropdown in the form tag

I want to use "angular2-multiselect-dropdown" in the ..
Please help me to resolved it,
form>
angular2-multiselect [data]="dropdownList" [(ngModel)]="selectedItems"
[settings]="dropdownSettings"
(onSelect)="onItemSelect($event)"
(onDeSelect)="OnItemDeSelect($event)"
(onSelectAll)="onSelectAll($event)"
(onDeSelectAll)="onDeSelectAll($event)">/angular2-multiselect

Error:
vendor.bundle.js:80244 ERROR Error: If ngModel is used within a form tag, either the name attribute must be set or the form
      control must be defined as 'standalone' in ngModelOptions.
BUT:
form>
angular2-multiselect [data]="dropdownList" name="selectedItems"
#selectedItems="ngModel" ngModel
[settings]="dropdownSettings"
(onSelect)="onItemSelect($event)"
(onDeSelect)="OnItemDeSelect($event)"
(onSelectAll)="onSelectAll($event)"
(onDeSelectAll)="onDeSelectAll($event)">/angular2-multiselect>
/form>
It still not working....

Its simple. Example coming soon..

Please refer to this example https://cuppalabs.github.io/angular2-multiselect-dropdown/#/usinginform

Thanks for your support @CuppaLabs


The experimental setting of comparison with fully-supervised methods

Fascinating work! However, I had some questions about the experimental setup while reading your article.
When compared with the fully-supervised method Mask3D, how is AGILE3D set up? Does the number of clicks (#clicks) in Table 3 refer to the average number of clicks per object? If so, why is this experiment placed in 4.1 EVALUATION ON SINGLE-OBJECT SEGMENTATION?

Hi @panzhiyi , thanks for your interest! Feel free to ask questions.
When compared Mask3D, we evaluate AGILE3D in the single-object segmentation setting. For each object in a scene, we add positive and negative clicks. We then feed the binary segmentation masks of all objects into Mask3D's evaluation protocol to calculate AP. In table 3, for example, #clicks = 1 means each object is given one (positive) click. #clicks = 10 means each object is given 10 clicks.
Hope this helps! Let me know if you have any further concerns.

Hi @panzhiyi , thanks for your interest! Feel free to ask questions.
When compared Mask3D, we evaluate AGILE3D in the single-object segmentation setting. For each object in a scene, we add positive and negative clicks. We then feed the binary segmentation masks of all objects into Mask3D's evaluation protocol to calculate AP. In table 3, for example, #clicks = 1 means each object is given one (positive) click. #clicks = 10 means each object is given 10 clicks.
Hope this helps! Let me know if you have any further concerns.

Thanks for your prompt response! One more small question, when training and testing with a multi-object segmentation setup, how is the number of objects set?

Hi @panzhiyi , this is a great question! We gave a description on how do we select objects for multi-object segmentation setup in section D.2 DATA PREPARATION in the appendix of the paper:

In practice, it would not be feasible for a user to simultaneously annotate all the objects in a large scene. Motivated by this consideration, we set the maximum number of target objects in each evaluation sample as 10. For each scene, we randomly select M ∈ [1, 2, ..., 10] nearby objects as evaluation samples.

I will try to clean and release the our data preparation code within next month. If you want to check the code immediately, feel free to leave me an email and I will send it to you.

Thank you very much for your answer! My issues have been resolved. Here's my email<EMAIL_ADDRESS>


Add syntax check support for projects with several build targets

Current implementation of syntax checking silently fails on cargo projects with several build targets (when there is src/main.rs and src/lib.rs at the same time or src/bin/foo.rs, src/bin/bar.rs and src/lib.rs).
I've added customization support for cargo rustc -- {target} -Zno-trans -Zunstable-options --error-format=json command. One can affect on the {target} part via tweaking per-projects settings.
Also since now the plugin writes explicit error message when cargo rustc command ends up with error.

I will try and test this when i get time

@Ostrovski is this a fix for https://github.com/rust-lang/sublime-rust/issues/94 ?

@Jayflux yes, it is. The issue #94 was added a few days later my PR, so I didn't see it at that time. Have read comments on #94 and I think that using proposed in my PR "smart" target detector is better than just using cargo flags, because it's pretty expensive to check all targets at once.

@Ostrovski do you mind updating the documentation? Maybe adding it to the settings heading?
I've seen you've done it in the comments which is good, but just so people can find it in the readme
Thanks

@Jayflux I've updated README.md in my fork, but it significantly changed it the main repo. I'll merge them on this weekend.

@Ostrovski thanks

@Jayflux, I've updated the fork with the fresh master.

@Jayflux, could you please remove this forgotten debug line? https://github.com/rust-lang/sublime-rust/blob/8cdb525a3d422c4cf7a25810d1378d8312b416ee/plugin.py#L14


Shim maxPacketLifeTime -> maxRetransmitTime in Chrome

We should shim maxPacketLifeTime to maxRetransmitTime when calling createDataChannel in Chrome.

:+1: have you filed an upstream bug? Ideally we can convince @henbos  this is trivial to fix :-)

You mean this one? https://bugs.chromium.org/p/chromium/issues/detail?id=696681

ah, nagging @guidou then :-)


ONNX Engine

I Will be adding in support for loading onnx models on the cpu/gpu such as https://huggingface.co/Qdrant/bge-large-en-v1.5-onnx
@StevenGann,  you might be interested in this.
I will link pull request here upon completion for further input.

How is this coming along?
Can you explain a bit more about it?
Will this provide a way to do embeddings without connecting to external software or servers?

reopening

Working with the ONNX engine,  one of the major challenges I am facing with this is reliable tokenization in dotnet.
Yes it will provide a way to do embeddings from within dotnet without using an external api.

https://learn.microsoft.com/en-us/azure/machine-learning/how-to-use-automl-onnx-model-dotnet?view=azureml-api-2
Looks like ONNX is natively supported by ML.NET.
If you push what you have, I could take a look.

@StevenGann,  Yes that is what I am using,  I have pushed a remake into my other repo,  I haven't had much time to work on this as I am finishing up a project for another client however feel free to check it out.


[ENHANCEMENT] BaseOS related update

Is your enhancement related to a problem? Please describe.
This issue is used to track BaseOS (OS image, Elemental) related PRs for v1.2.2
Describe the solution you'd like
task list:

[x] https://github.com/harvester/harvester/pull/4822
[x] https://github.com/harvester/harvester-installer/pull/609
[x] https://github.com/harvester/os2/pull/85
[x] https://github.com/harvester/harvester/issues/4856

Describe alternatives you've considered
None
Additional context
TBD

After I bump the new baseos, I will move this to ready for testing again.

@lanfon72 Do you think our e2e should be enough to test it?

We would still need to manually check versions, but no new automation test required.

Verified this change has been applied.

Basic operations tested by daily e2e and it works.
Basic Rancher integration tested by daily e2e and it works.
Packages and release version hit the required in https://github.com/harvester/harvester/issues/4857#issuecomment-1920917361


systemd: copy systemd-binfmt.service in

proc-sys-fs-binfmt_misc.mount was already in the list — adding this service makes it easy to configure.

Along with a demo of why this is rad:
{ pkgs, ... }:
let pkg = pkgs.wine; in
{
  environment.systemPackages = [ pkg ];
  environment.etc."binfmt.d/wine.conf" = {
    text = ":DOSWin:M::MZ::${pkg}/bin/wine:\n";
  };
}

Maybe worthy for inclusion as a module under nixos/modules/virtualisation?

Or, ideally: have some piece of config infrastructure for binfmt, so we can also include Mono and qemu-user and things like that?

Having infrastructure for that could also ensure systemd-binfmt.service is restarted when binfmts are changed.

Along with a demo of why this is rad

For anyone wondering, @nathan7's code would allow you to invoke ./foo.exe and have the OS implicitly call Wine for you.

nice!

@copumpkin Yup! I made one that dispatches to WINE and Mono based on whether it's a CLR executable too: https://gist.github.com/nathan7/a8118bf5b047f5f77c6c

Turns out this unit doesn't properly depend on proc-sys-fs-binfmt_misc.mount, which causes it to break. What's the best way to patch it up?

Hm, units/systemd-binfmt.service.in in systemd has:
After=proc-sys-fs-binfmt_misc.automount

and the Makefile installs proc-sys-fs-binfmt_misc.automount as a dependency of sysinit.target. So it should work, except that we don't restart sysinit.target in switch-to-configuration, so it may require a reboot. I guess we could add a line like
systemd.services.systemd-binfmt.wants = [ "proc-sys-fs-binfmt_misc.automount" ];

Ping?

@joachifm Pong!
I've integrated @edolstra's suggestion into the PR now, and I've been using this on my laptop for months with no issues.

Cool beans. As far as I can tell, there was no fundamental objection to this, so I'm merging it.

This seems to still pop up as an issue.
systemd reports:
proc-sys-fs-binfmt_misc.automount   not-found inactive dead      proc-sys-fs-binfmt_misc.automount

See also https://github.com/NixOS/nixops/issues/574 for a mitigation, but this could use a proper solution.

Remove this line?
https://github.com/NixOS/nixpkgs/blob/92a047a6c4d46a222e9c323ea85882d0a7a13af8/nixos/modules/system/boot/binfmt.nix#L135


Missing product links

The page should include links to Azure Load Testing and Azure Chaos Studio product doc pages

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

ID: ded56014-b7da-2acd-6b38-e71611a50200
Version Independent ID: ded56014-b7da-2acd-6b38-e71611a50200
Content: Continuous validation with Azure Load Testing and Azure Chaos Studio - Azure Architecture Center
Content Source: docs/guide/testing/mission-critical-deployment-testing.md
Service: architecture-center
Sub-service: guide
GitHub Login: @heoelri
Microsoft Alias: msimecek

@algattik - we have added links to both.


add note about build deps in readme

imagine not everyone have cmake installed

actually messed up more than 1 hour trying to compile it and still did not succeeded....
I have installed cmake and it says it is not installed, I restarted my laptop and it still says it is not installed...
are guys sure it is a good idea to have C++ dependencies? i recommend using winit and egui

btw I am on Windows if it matters

Do you know what is trying to build that's using cmake? I'm thinking it might be shaderc or imgui but I'm not sure, so I'd appreciate the info. I think cmake is installed for other reasons on all the machines I use, so I didn't notice it. I also don't recall adding it to CI as a dependency, although it's possible it's available by default in github's CI environment.
I don't think avoiding C++ dependencies will be possible. I'd rather not re-implement a GLSL compiler or maintain a spirv_cross equivalent. That said, some crates (like SDL2 unfortunately) are flaky to build. I'd rather see those issues be fixed than throw out an option that has shipped a huge number of titles on many platforms. (I've thought about making a minimal SDL2 crate, I only use a very small fraction of APIs from SDL2).
Regarding winit and egui, rafx uses raw-window-handle so you can use whatever windowing crate you would like. I use SDL2 because of bugs like this https://github.com/rust-windowing/winit/issues/1418 that have been open for a year and would block shipping a real product. I will probably switch to egui at some point for the demo. It was not as mature a year ago when I went with imgui. But there's no reason why egui could not be implemented in your own project that uses rafx.

Removed cmake from path on a windows machine, it's used by SDL2 and some upstream crates in the shader pipeline. (So switching away from SDL2 would not remove the need to have cmake installed)
Added a note in the README: https://github.com/aclysma/rafx/commit/0047f2ce734353e48af654acafc93ebad64b2daa
Happy to look at an error/compile message if you have one

Do you know what is trying to build that's using cmake? I'm thinking it might be shaderc or imgui but I'm not sure, so I'd appreciate the info. I think cmake is installed for other reasons on all the machines I use, so I didn't notice it.
==It fails when compiling sdl2.==
I don't think avoiding C++ dependencies will be possible. I'd rather not re-implement a GLSL compiler or maintain a spirv_cross equivalent. That said, some crates (like SDL2 unfortunately) are flaky to build.
==I'm not sure, but projects like wgpu and gfx now are working hard to get rid of C++ deps, so consider what they've done in order to do so==

The C/C++ dependencies that I use are mature, stable, and successfully used in commercially shipped titles. For me that carries a lot of weight.
If you are still unable to build after installing cmake, please feel free to reopen/paste the compile error. I do frequently build/run rafx on windows.