Add all event dates to UI

Some of these will need to be hidden behind another field, but adding them all for now. I also removed a test line in NewCaseForm.test.tsx since I don't think it adds much value. Let me know if you disagree.

Codecov Report

Merging #279 into master will increase coverage by 1.31%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #279      +/-   ##
==========================================
+ Coverage   62.15%   63.46%   +1.31%
==========================================
  Files          18       18
  Lines         473      490      +17
  Branches      127      141      +14
==========================================
+ Hits          294      311      +17
  Misses        179      179

Impacted Files
Coverage Δ

.../curator-service/ui/src/components/NewCaseForm.tsx
77.14% <100.00%> (+5.71%)
:arrow_up:

.../ui/src/components/new-case-form-fields/Events.tsx
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


test: move workflow test to example schemas

Codecov Report

Merging #364 (9b857b6) into tagged-release/q1-release (b58f601) will not change coverage.
The diff coverage is n/a.

@@                    Coverage Diff                     @@
##           tagged-release/q1-release     #364   +/-   ##
==========================================================
  Coverage                      93.14%   93.14%
==========================================================
  Files                             37       37
  Lines                           1429     1429
  Branches                         316      316
==========================================================
  Hits                            1331     1331
  Misses                            96       96
  Partials                           2        2

Continue to review full report at Codecov.

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


All rolls are 99

Describe the bug
All attack/skill/check rolls are 99, Initiative is 20
To Reproduce
If applicable, provide steps to reproduce this issue
Screenshots
If applicable, add screenshots to help explain your problem.
Version Numbers
7.0.3, 6.6.1
Foundry:
wfrp4e:

Ensure core module is updated by reinstalling it.


value of hyper parameter to reproduce the experiment

It seems that the values of hyper parameters provided in config file could not promise results reported in the paper? Could you provide specific values, especially for smooth ratio, degree ratio, and sparsity ratio

It seems that the values of hyper parameters provided in config file could not promise results reported in the paper? Could you provide specific values, especially for smooth ratio, degree ratio, and sparsity ratio

@lipingcoding thank you for your interest to our work! We ran multiple runs with different random seeds in our experiments. You may want to do multiple runs with different random seeds. I think the hyperparameteres values in the config files should be updated. Which config file are you specifically referring to?

@hugochan For example, in src/config/cora/idgl.yml, the values of both zero. Are they right?

sorry, my fault.


Home Assistant: error loading config

Just installed fresh copy of HA and also added lxp-bridge but get this error when trying to start it up.  Also note the log level is listed as INFO even though I have the config set as TRACE.
[20:24:31] INFO: Creating lxp-bridge config from options...
Done.
[20:24:31] INFO: Starting lxp-bridge...
Error: inverters[0]:  must be exactly 10 characters at line 3 column 5

loglevel: trace
inverters:
  - enabled: true
    host: <IP_ADDRESS>
    port: 8000
    serial: ""
    datalog: ""
    heartbeats: false
    publish_holdings_on_connect: false
databases:
  - enabled: false
    url: postgres://lxp:lxp@localhost/lxp
mqtt:
  enabled: true
  host: localhost
  port: 1883
  username: ""
  password: ""
  namespace: lxp
influx:
  enabled: false
  url: http://localhost:8086
  username: ""
  password: ""
  database: lxp

It looks like a bit of crucial detail is missing in that error, it should be referring to the serial/datalog - they need to be 10 characters for the config parser to give it a pass.
So currently you have:
    serial: ""
    datalog: ""

They need 10 chars in the strings. I think the documentation might actually say you don't need to set this if you don't want to control the inverter but thats obviously wrong, I'll see if I can improve that actually. The correct advice should probably be "if you don't want to control the inverter, just monitor it, you can put ten zero's here" or 10 of anything really.
As to the logging level, so you've set trace which means you'll get full debugging, but those lines having INFO just means those particular lines are logged at INFO level.

I installed lxp-bridge - and when filling in the serial number of the inverter, an error pops up; if you change one digit to a letter, it is saved - what could it be? (I enter the real serial numbers from the inverter

That looks like it's  because it's interpreting it as a number not a string (no letters in it). just surrounding the value with quotes should fix it :)

Thanks for the quick response!!! It’s just that
sensor.lxp_ba35204810_active_eps_power always shows only 0 in the ON,
although in the application the power consumption is always shown well

I thought this was the problem... maybe you know what this problem
could be? (I put the serial number in quotes - the configuration is
saved)

сб, 17 февр. 2024 г. в 18:27, Chris Elsworth @.***>:

That looks like it's because it's interpreting it as a number not a string
(no letters in it). just surrounding the value with quotes should fix it :)
—
Reply to this email directly, view it on GitHub
https://github.com/celsworth/lxp-bridge/issues/225#issuecomment-1950249331,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BB52Y65KXBLJWNSMGKTGNGTYUDK5RAVCNFSM6AAAAABAXIKUSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJQGI2DSMZTGE
.
You are receiving this because you commented.Message ID:
@.***>

Thanks for the quick response!!! It’s just that
sensor.lxp_ba35204810_active_eps_power always shows only 0 in the ON,
although in the application the power consumption is always shown well - I
thought this was the problem... maybe you know what this problem could be?
(I put the serial number in quotes - the configuration is saved)
сб, 17 февр. 2024 г. в 19:12, Nemirow Nemirow @.***>:

Thanks for the quick response!!! It’s just that sensor.lxp_ba35204810_active_eps_power always shows only 0 in the ON, although in the application the power consumption is always shown well - I thought this was the problem... maybe you know what this problem could be? (I put the serial number in quotes - the configuration is saved)
сб, 17 февр. 2024 г. в 18:27, Chris Elsworth @.***>:

That looks like it's because it's interpreting it as a number not a
string (no letters in it). just surrounding the value with quotes should
fix it :)
—
Reply to this email directly, view it on GitHub
https://github.com/celsworth/lxp-bridge/issues/225#issuecomment-1950249331,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BB52Y65KXBLJWNSMGKTGNGTYUDK5RAVCNFSM6AAAAABAXIKUSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJQGI2DSMZTGE
.
You are receiving this because you commented.Message ID:
@.***>

EPS power being 0 I think is normal when AC is present. I don't think it has a way to measure it since its basically bypass.
If you yank AC power so it starts acting like a UPS then I think it starts to show EPS power.


[Bug]-[1644]:Handle client side migration for git discard functionality to avoid seeing uncommitted changes

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When user's application has client-side migration since last commit, and if user triggers the discard and pull flow user ends up seeing uncommitted changes as client-side migrations run after the successful response from server. This gives the false impression that discard failed for some unknown error though UI does not show any error state. To resolve this issue we will be doing a autocommit when we detect the client-side migrations in get status flow:

[x] #19209
[ ] Chain get status API with migrations so as to avoid the race condition i.e. run all the migrations and then trigger get status API @IAmAnubhavSaini
[x] #14412

Steps To Reproduce

Connect application to git
Reduce the page DSL version from DB by 1 (manual update)
Commit changes without refreshing the page
Hard refresh from browser to trigger client side migrations along with get status call
Try pull and discard flow
Even if discard is successful we will see migrations changes to be committed

Public Sample App
No response
Version
Cloud: v1.7.1

Stats

Stat
Values

Reach
822

Effort (months)
1

@IAmAnubhavSaini roughly estimating time for this to be 2 person-weeks for prioritisation. Feel free to call out for a change if you think different.

Closing this as its covered via the Auto Commit flows


keras, tensorflow, theano versions?

Hi,
I'm tripping over a few 'module has no attribute' errors that may simply be version incompatibilities (I'm working from a fresh install of everything). Can you include version info for your major dependencies in the README?
Thanks

Oh weird, I just added a requirements.txt if you want to try that. (which I should have had to begin with!) I tried running it from a fresh virtualenv with Python 3.5 and it seemed to work.
What was the exact error you were getting? One thing is that I typically use the TensorFlow backend, so there might be bugs if you're using Theano instead. I didn't include TensorFlow in the requirements.txt since it's not managed through PyPI and is platform-dependent, but you can try installing that if you run into problems.

I was attempting this under python2.7, as scipy 0.18.x for python3 on macos has issues, and I fell back just in case this could be made to work in my healthier 2.7 env. I am currently re-installing 3.5 with scipy 0.17.0 0 as a workaround, we'll see how far I get.
(Did not look into 2/3 compatibilities, but the missing items were keras.models.load_model plus several items from keras.backend incl image_dim_ordering)

all better now, a training run succeeded (python 3.5, scipy 0.17.0).
I did need to manually install h5py, it's optional for keras
and is needed for save_model.

@welch Cool! Glad it's working for you.


[staging] ffmpeg: ffmpeg_4 → ffmpeg_5

Description of changes
Things done
Currently building and testing

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Estimating rebuild amount by counting changed Hydra jobs (parallel=unset).
    161 x86_64-darwin
   2910 x86_64-linux

Oh, that's relatively tame as far as rebuilds go. We might not need a hydra jobset for that. I'll see whether I can run nixpkgs-reivew on that tomorrow.
Is there a good easy way to exclude already broken packages in nixpkgs-review?

Not that I know of :c

Speaking of cleanup, ffmpeg 6 is out
I tried to package it with:
diff --git c/pkgs/development/libraries/ffmpeg/6.nix i/pkgs/development/libraries/ffmpeg/6.nix
new file mode 100644
index<PHONE_NUMBER>0..37bdf5b060f
--- /dev/null
+++ i/pkgs/development/libraries/ffmpeg/6.nix
@@ -0,0 +1,4 @@
+import ./generic.nix {
+  version = "6.0";
+  sha256 = "sha256-RVbgsafIbeUUNXmUbDQ03ZN42oaUo0njqROo7KOQgv0=";
+}
diff --git c/pkgs/top-level/all-packages.nix i/pkgs/top-level/all-packages.nix
index 1ddec927d95..fedc4500268 100644
--- c/pkgs/top-level/all-packages.nix
+++ i/pkgs/top-level/all-packages.nix
@@ -19762,6 +19762,18 @@ with pkgs;
     ffmpegVariant = "full";
   };

+  ffmpeg_6 = callPackage ../development/libraries/ffmpeg/6.nix {
+    inherit (darwin.apple_sdk.frameworks)
+      Cocoa CoreServices CoreAudio CoreMedia AVFoundation MediaToolbox
+      VideoDecodeAcceleration VideoToolbox;
+  };
+  ffmpeg_6-headless = ffmpeg_6.override {
+    ffmpegVariant = "headless";
+  };
+  ffmpeg_6-full = ffmpeg_6.override {
+    ffmpegVariant = "full";
+  };
+
   # Aliases
   # Please make sure this is updated to the latest version on the next major
   # update to ffmpeg

But it fails to detect the cuvid dependency:
ERROR: cuvid requested, but not all dependencies are satisfied: ffnvcodec

Although according to this upstream commit and the fact we add nv-codec-headers-<IP_ADDRESS> as a dependency.

 Ignore the chromium-unwrapped failure, I stopped that intentionally because I didn't want to build chromium. I'll just set it to ffmpeg_4 too and let the chromium maintainers upgrade it themselves if they feel like it.
I'll also mark entirely broken packages as such.

Wait hold on, that list is broken. I'll need to get tmux to copy and paste properly somehow after eating. The list of broken packages is correct though.

@ofborg eval

I forgot I still had some TODOs and unfortunately I lost my scratch buffer to a restart. It was only a few packages and I'm running nixpkgs-review on my tree to find them again and do some final QA. One was haskellPackages.ffmpeg-light which we'll need to somehow get on ffmpeg_4 and another was sonic-pi which doesn't compile on my machine but doesn't directly depend on ffmepg in any way?
I can no longer effectively review changes done now on staging; too many rebuilds. I'm not sure we really need a hydra jobset for this anymore though.

seems like the staging-main conflict has been resolved.
Rebased to the merge-base of both again.

I assume all the meta.broken changes are related to ffmpeg?

Likely broken before this change:
    Found while changing ffmpeg from 4 to 5; these all depend on ffmpeg either
    directly or transitively.

 pkgs/applications/blockchains/bitcoin-unlimited/default.nix | 2 +-
 pkgs/applications/blockchains/dogecoin/default.nix          | 1 +
 pkgs/applications/blockchains/pivx/default.nix              | 2 +-
 pkgs/applications/gis/zombietrackergps/default.nix          | 1 +
 pkgs/applications/graphics/fluxus/default.nix               | 1 +
 pkgs/applications/graphics/gnome-decoder/default.nix        | 1 +
 pkgs/applications/terminal-emulators/syncterm/default.nix   | 3 ++-
 pkgs/applications/video/rtabmap/default.nix                 | 1 +
 pkgs/desktops/gnome/extensions/EasyScreenCast/default.nix   | 2 +-
 pkgs/development/libraries/openhmd/default.nix              | 1 +
 pkgs/development/python-modules/apache-beam/default.nix     | 1 +
 pkgs/development/python-modules/pims/default.nix            | 1 +
 pkgs/development/python-modules/pydevd/default.nix          | 1 +
 pkgs/development/python-modules/python-efl/default.nix      | 1 +
 pkgs/development/python-modules/spectral-cube/default.nix   | 2 +-
 pkgs/development/python-modules/sunpy/default.nix           | 1 +
 pkgs/development/python-modules/wxPython/4.0.nix            | 1 +
 pkgs/development/python-modules/wxPython/4.1.nix            | 1 +
 pkgs/development/tools/shadered/default.nix                 | 1 +
 pkgs/games/openclonk/default.nix                            | 1 +
 pkgs/games/spring/default.nix                               | 1 +

bitcoin-unlimited: broken since 2023-01-14 / last build 2022-12-30
https://hydra.nixos.org/build/210662522
dogecoin: broken since 2023-01-14 / last build 2023-01-07
https://hydra.nixos.org/build/210775530
pivx: broken since 2020-12-11 / last build 2020-12-06
https://hydra.nixos.org/build/210831321
zombietrackergps: broken since 2023-02-13 / last build 2023-02-12
https://hydra.nixos.org/build/211324850
fluxus: broken since 2023-02-13 / last build 2023-02-06
https://hydra.nixos.org/build/211234819
etc

@SuperSandro2000 the packages were already broken; that's unrelated to ffmpeg. It's just that I noticed they were broken because they depend on ffmpeg transitively which causes them to show up as "changed" in nixpkgs-review of course.

Rebasing, give me a minute

This was the conflict:
--- a/pkgs/applications/gis/zombietrackergps/default.nix
+++ b/pkgs/applications/gis/zombietrackergps/default.nix
@@@ -62,6 -62,6 +62,11 @@@ mkDerivation rec
      license = licenses.gpl3Plus;
      maintainers = with maintainers; [ sohalt ];
      platforms = platforms.linux;
++<<<<<<< HEAD
 +    broken = true;  # doesn't build with latest Marble
++||||||| parent of 4eafc2c0c16 (tree-wide: mark broken packages as such)
++=======
+     broken = true;
++>>>>>>> 4eafc2c0c16 (tree-wide: mark broken packages as such)
    };
  }

We can also pull out the brokeness markings into a separate PR. I've got some more at https://github.com/atemu/nixpkgs/tree/ffmpeg_5.

I think this is ready from mass-rebuild perspective.  Further tweaks can come later.

Start2

Start2

Arg-2

Sorry?


Support for Collapse/Expand Without Notifying Listeners

Allows views to expanded/collapsed without notifying listeners
original API and functionality is maintained

thanks, published in 1.2.4


Rancher v0.59.1 serves http when in https

When accessing https://url-to-rancher.com on my setup the page fails to load and shows a timeout page with this request being the one that timed out: http://url-to-rancher.com/v1/userpreferences?limit=1000.
ELB config

ProxyProtocol is enabled.  Our setup is: elb -> ec2 instance with docker running rancher on port 80 on a private subnet so we can talk to our internal systems.
I've retraced my steps and I don't believe I've missed anything.

Useful
Info

Versions
Rancher v0.59.1 Cattle: v0.148.1 UI: v0.90.0

Access
github admin

Route
null

The API returns absolute URLs based on the headers/ProxyProtocol info it's sent, and then the UI is following them.  I know you've said it's enabled, but the obvious answer is it isn't in fact enabled/working.  You can look for it on the host with something like tcpdump -A -s0 port 80, it would be at the beginning of each request.

Thanks for the followup.  I'll dig into this a bit more!


BasicAuth not allowing certain characters in password

When using a password with * an error message occurs:
panic: [ PANIC ] NodeConfig: Error while loading config from .: While parsing config: invalid character '*' in string escape code
Same happens when using \ etc.

This works for me...
    "basic_auth": {
      "enabled": true,
      "username": "muxxer",
      "password": "test*123"
    }

Which OS are you running? Did you compiled the source on your own? Which GO version?

I use Debian 10 with the HORNET-0.1.0_Linux_x86_64.tar.gz from the release page. The config.json file was included and I only changed the password to a secure one with 32 characters containing special characters. Of course I also set "enabled" to true.
I tried a short password without special characters and it works.

Maybe you have other special characters in it? Can you remove special character by character until it works?

I created a new one (since I didn't save the first one).
"password": "*a[PmoH?C'2^$%\MO*Iy9^Uta0M/64wo1P" gives me the error
2019/12/12 21:40:51 [ PANIC ] NodeConfig: Error while loading config from .: While parsing config: invalid character 'M' in string escape code panic: [ PANIC ] NodeConfig: Error while loading config from .: While parsing config: invalid character 'M' in string escape code

you can't use \ because it is an escape sequence! That is not HORNET related but json.
If you want \, you have to type \\

https://www.freeformatter.com/json-escape.html
Backslash is replaced with \\

Oh wow I never thought about this. You are right.


Cyclic EOF

Which version are you using?
v0.17.2
Which operating system are you using?
OS

[x] Linux
[ ] Windows
[ ] macOS

Architecture

[x] amd64
[ ] arm64
[ ] arm7
[ ] arm6

Describe the issue
We are using the rtsp-simple-server to relay/proxy multiple camera streams over TCP to save bandwidth at the camera side when multiple viewers are connected. Of the 5 camera's we have connected over RTSP/TCP right now, there are two camera's constantly giving an EOF error and then reconnecting after 10 seconds. This is a very predictable behaviour. The EOF is given +/- 1 minute after the stream becomes ready again, after which it becomes ready again in 10 seconds, then EOF's after a minute, etc.
2021/09/02 08:17:25 I [0/5] [path camera1] [rtsp source] ready
2021/09/02 08:17:29 I [0/5] [RTSP] [conn redacted.ip.address:38378] opened
2021/09/02 08:17:29 I [0/5] [RTSP] [session 721715509] opened by redacted.ip.address:38378
2021/09/02 08:17:29 I [0/6] [RTSP] [session 721715509] is reading from path 'camera1', 1 track with TCP
2021/09/02 08:18:01 I [0/6] [path camera2] [rtsp source] ERR: EOF
2021/09/02 08:18:01 I [0/5] [RTSP] [conn redacted.ip.address:37734] closed
2021/09/02 08:18:01 I [0/5] [RTSP] [session 985793389] closed
2021/09/02 08:18:07 I [0/5] [path camera2] [rtsp source] ready
2021/09/02 08:18:11 I [0/5] [RTSP] [conn redacted.ip.address:41070] opened
2021/09/02 08:18:11 I [0/5] [RTSP] [session 362872492] opened by redacted.ip.address:41070
2021/09/02 08:18:11 I [0/6] [RTSP] [session 362872492] is reading from path 'camera2', 1 track with TCP
2021/09/02 08:18:25 I [0/6] [path camera1] [rtsp source] ERR: EOF
2021/09/02 08:18:25 I [0/5] [RTSP] [conn redacted.ip.address:38378] closed
2021/09/02 08:18:25 I [0/5] [RTSP] [session 721715509] closed
2021/09/02 08:18:30 I [0/5] [path camera1] [rtsp source] ready
2021/09/02 08:18:35 I [0/5] [RTSP] [conn redacted.ip.address:41592] opened
2021/09/02 08:18:35 I [0/5] [RTSP] [session 158226186] opened by redacted.ip.address:41592
2021/09/02 08:18:35 I [0/6] [RTSP] [session 158226186] is reading from path 'camera1', 1 track with TCP
2021/09/02 08:19:07 I [0/6] [path camera2] [rtsp source] ERR: EOF
2021/09/02 08:19:07 I [0/5] [RTSP] [conn redacted.ip.address:41070] closed
2021/09/02 08:19:07 I [0/5] [RTSP] [session 362872492] closed
2021/09/02 08:19:12 I [0/5] [path camera2] [rtsp source] ready
2021/09/02 08:19:17 I [0/5] [RTSP] [conn redacted.ip.address:42140] opened
2021/09/02 08:19:17 I [0/5] [RTSP] [session 311210718] opened by redacted.ip.address:42140
2021/09/02 08:19:17 I [0/6] [RTSP] [session 311210718] is reading from path 'camera2', 1 track with TCP
2021/09/02 08:19:30 I [0/6] [path camera1] [rtsp source] ERR: EOF
2021/09/02 08:19:30 I [0/5] [RTSP] [conn redacted.ip.address:41592] closed

When viewing these camera streams directly (with ffplay, for instance) we observe no such issues.
Describe how to replicate the issue
I have no clue how to recplicate this, as I don't understand what's causing or triggering this. Is it a bug or is it a configuration error?
###############################################
# General parameters

# sets the verbosity of the program; available values are "warn", "info", "debug".
logLevel: info
# destinations of log messages; available values are "stdout", "file" and "syslog".
logDestinations: [file]
# if "file" is in logDestinations, this is the file which will receive the logs.
logFile: /var/log/rtsp-simple-server0.17.log

# timeout of read operations.
readTimeout: 10s
# timeout of write operations.
writeTimeout: 10s
# number of read buffers.
# a higher number allows a higher throughput,
# a lower number allows to save RAM.
readBufferCount: 512

# enable the HTTP API.
api: no
# address of the API listener.
apiAddress: <REDACTED>

# enable Prometheus-compatible metrics.
metrics: no
# address of the metrics listener.
metricsAddress: <IP_ADDRESS>:9998

# enable pprof-compatible endpoint to monitor performances.
pprof: no
# address of the pprof listener.
pprofAddress: <IP_ADDRESS>:9999

# command to run when a client connects to the server.
# this is terminated with SIGINT when a client disconnects from the server.
# the server port is available in the RTSP_PORT variable.
runOnConnect:
# the restart parameter allows to restart the command if it exits suddenly.
runOnConnectRestart: no

###############################################
# RTSP parameters

# disable support for the RTSP protocol.
rtspDisable: no
# supported RTSP stream protocols.
# UDP is the most performant, but doesn't work when there's a NAT/firewall between
# server and clients, and doesn't support encryption.
# UDP-multicast allows to save bandwidth when clients are all in the same LAN.
# TCP is the most versatile, and does support encryption.
# The handshake is always performed with TCP.
protocols: [tcp]
# encrypt handshake and TCP streams with TLS (RTSPS).
# available values are "no", "strict", "optional".
encryption: no
# address of the TCP/RTSP listener. This is needed only when encryption is "no" or "optional".
rtspAddress: :9554
# address of the TCP/TLS/RTSPS listener. This is needed only when encryption is "strict" or "optional".
rtspsAddress: :9555
# address of the UDP/RTP listener. This is needed only when "udp" is in protocols.
rtpAddress: :8000
# address of the UDP/RTCP listener. This is needed only when "udp" is in protocols.
rtcpAddress: :8001
# IP range of all UDP-multicast listeners. This is needed only when "multicast" is in protocols.
multicastIPRange: <IP_ADDRESS>/16
# port of all UDP-multicast/RTP listeners. This is needed only when "multicast" is in protocols.
multicastRTPPort: 8002
# port of all UDP-multicast/RTCP listeners. This is needed only when "multicast" is in protocols.
multicastRTCPPort: 8003
# path to the server key. This is needed only when encryption is "strict" or "optional".
# this can be generated with:
# openssl genrsa -out server.key 2048
# openssl req -new -x509 -sha256 -key server.key -out server.crt -days 3650
serverKey: server.key
# path to the server certificate. This is needed only when encryption is "strict" or "optional".
serverCert: server.crt
# authentication methods.
authMethods: [basic, digest]
# read buffer size.
# this doesn't influence throughput and shouldn't be touched unless the server
# reports errors about the buffer size.
readBufferSize: 2048

###############################################
# RTMP parameters

# disable support for the RTMP protocol.
rtmpDisable: yes
# address of the RTMP listener.
rtmpAddress: :1935

###############################################
# HLS parameters

# disable support for the HLS protocol.
hlsDisable: yes
# address of the HLS listener.
hlsAddress: :8888
# by default, HLS is generated only when requested by a user;
# this option allows to generate it always, avoiding an initial delay.
hlsAlwaysRemux: no
# number of HLS segments to generate.
# increasing segments allows more buffering,
# decreasing segments decreases latency.
hlsSegmentCount: 3
# minimum duration of each segment.
# the final segment duration is also influenced by the interval between IDR frames,
# since the server changes the segment duration to include at least a IDR frame in each one.
hlsSegmentDuration: 1s
# value of the Access-Control-Allow-Origin header provided in every HTTP response.
# This allows to play the HLS stream from an external website.
hlsAllowOrigin: '*'

###############################################
# Path parameters

# these settings are path-dependent.
# it's possible to use regular expressions by using a tilde as prefix.
# for example, "~^(test1|test2)$" will match both "test1" and "test2".
# for example, "~^prefix" will match all paths that start with "prefix".
# the settings under the path "all" are applied to all paths that do not match
# another entry.
paths:
 <REDACTED - PRIVATE>
  <EXAMPLE:>
  camera1:
    source: rtsp://private-ip.etc
    sourceProtocol: tcp
    sourceOnDemand: yes
  all:
    # source of the stream - this can be:
    # * publisher -> the stream is published by a RTSP or RTMP client
    # * rtsp://existing-url -> the stream is pulled from another RTSP server
    # * rtsps://existing-url -> the stream is pulled from another RTSP server, with RTSPS
    # * rtmp://existing-url -> the stream is pulled from a RTMP server
    # * redirect -> the stream is provided by another path or server
    source: publisher

    # if the source is an RTSP or RTSPS URL, this is the protocol that will be used to
    # pull the stream. available values are "automatic", "udp", "multicast", "tcp".
    # the TCP protocol can help to overcome the error "no UDP packets received recently".
    sourceProtocol: automatic

    # if the source is an RTSP or RTSPS URL, this allows to support cameras that
    # don't provide server ports. This is a security issue and must be enabled only
    # when interacting with old cameras that require it.
    sourceAnyPortEnable: no

    # if the source is an RTSPS URL, the fingerprint of the certificate of the source
    # must be provided in order to prevent man-in-the-middle attacks.
    # it can be obtained from the source by running:
    # openssl s_client -connect source_ip:source_port </dev/null 2>/dev/null | sed -n '/BEGIN/,/END/p' > server.crt
    # openssl x509 -in server.crt -noout -fingerprint -sha256 | cut -d "=" -f2 | tr -d ':'
    sourceFingerprint:

    # if the source is an RTSP or RTMP URL, it will be pulled only when at least
    # one reader is connected, saving bandwidth.
    sourceOnDemand: no
    # if sourceOnDemand is "yes", readers will be put on hold until the source is
    # ready or until this amount of time has passed.
    sourceOnDemandStartTimeout: 10s
    # if sourceOnDemand is "yes", the source will be closed when there are no
    # readers connected and this amount of time has passed.
    sourceOnDemandCloseAfter: 10s

    # if the source is "redirect", this is the RTSP URL which clients will be
    # redirected to.
    sourceRedirect:

    # if the source is "publisher" and a client is publishing, do not allow another
    # client to disconnect the former and publish in its place.
    disablePublisherOverride: no

    # if the source is "publisher" and no one is publishing, redirect readers to this
    # path. It can be can be a relative path  (i.e. /otherstream) or an absolute RTSP URL.
    fallback:

    # username required to publish.
    # sha256-hashed values can be inserted with the "sha256:" prefix.
    publishUser:
    # password required to publish.
    # sha256-hashed values can be inserted with the "sha256:" prefix.
    publishPass:
    # ips or networks (x.x.x.x/24) allowed to publish.
    publishIPs: []

    # username required to read.
    # sha256-hashed values can be inserted with the "sha256:" prefix.
    readUser:
    # password required to read.
    # sha256-hashed values can be inserted with the "sha256:" prefix.
    readPass:
    # ips or networks (x.x.x.x/24) allowed to read.
    readIPs: []

    # command to run when this path is initialized.
    # this can be used to publish a stream and keep it always opened.
    # this is terminated with SIGINT when the program closes.
    # the path name is available in the RTSP_PATH variable.
    # the server port is available in the RTSP_PORT variable.
    runOnInit:
    # the restart parameter allows to restart the command if it exits suddenly.
    runOnInitRestart: no

    # command to run when this path is requested.
    # this can be used to publish a stream on demand.
    # this is terminated with SIGINT when the path is not requested anymore.
    # the path name is available in the RTSP_PATH variable.
    # the server port is available in the RTSP_PORT variable.
    runOnDemand:
    # the restart parameter allows to restart the command if it exits suddenly.
    runOnDemandRestart: no
    # readers will be put on hold until the runOnDemand command starts publishing
    # or until this amount of time has passed.
    runOnDemandStartTimeout: 10s
    # the runOnDemand command will be closed when there are no
    # readers connected and this amount of time has passed.
    runOnDemandCloseAfter: 10s

    # command to run when a client starts publishing.
    # this is terminated with SIGINT when a client stops publishing.
    # the path name is available in the RTSP_PATH variable.
    # the server port is available in the RTSP_PORT variable.
    runOnPublish:
    # the restart parameter allows to restart the command if it exits suddenly.
    runOnPublishRestart: no

    # command to run when a clients starts reading.
    # this is terminated with SIGINT when a client stops reading.
    # the path name is available in the RTSP_PATH variable.
    # the server port is available in the RTSP_PORT variable.
    runOnRead:
    # the restart parameter allows to restart the command if it exits suddenly.
    runOnReadRestart: no

Note: I have had to remove some specifics (IP addresses, usernames, passwords) for obvious reasons.

Hello, this is a communication bug between the server and the specific model of your cameras, please attach a network dump, that can be generated in this way:

Download wireshark (https://www.wireshark.org/)
Start capturing on the interface used for exchanging RTSP (if the server and the target software are both installed on your pc, the interface is probably "loopback", otherwise it's the one of your network card)
Start the server and replicate the issue
Stop capturing, save the result in .pcap format
Attach

I have the same issue when connect to VIVOTEKNVR RTSP stream in TCP mode
I recorded packet data in pacap format.
vivoteknvr_eof.zip

To solve this, we need a full packet dump (unfortunately the one provided by @Vukia is not enough) and the server log. Unfortunately, since it's hardware-specific, user's help is needed.

Hello, I have the same issue. Pcap and log file in archive.
https://drive.google.com/file/d/16tY8E3b05O58AzreKCAx5nbJQ8sa-reA/view?usp=sharing

The log provided by @icrab is interesting (thanks!), it shows that a camera in TCP mode closes the TCP connection with the server after a timeout (120 secs):
2021/11/03 05:35:58 INF [0/0] [path proxied0] [rtsp source] ERR: EOF
2021/11/03 05:35:58 DEB [0/0] [path proxied0] [rtsp source] c->s TEARDOWN rtsp://<IP_ADDRESS>:554/user=test-user

In TCP mode, the server doesn't send periodic keepalive packets to the camera, but probably it should.

@icrab @Vukia @WillemvdKletersteeg please try the attached nightly release and let me know if there's a difference. It sends keepalive packets to the camera even when the transport protocol is TCP:
rtsp-simple-server_v0.17.7-31-g4f7f2d7_darwin_amd64.tar.gz
rtsp-simple-server_v0.17.7-31-g4f7f2d7_linux_amd64.tar.gz
rtsp-simple-server_v0.17.7-31-g4f7f2d7_linux_arm64v8.tar.gz
rtsp-simple-server_v0.17.7-31-g4f7f2d7_linux_armv6.tar.gz
rtsp-simple-server_v0.17.7-31-g4f7f2d7_linux_armv7.tar.gz
rtsp-simple-server_v0.17.7-31-g4f7f2d7_windows_amd64.zip

thanks for quick answer, @aler9! keepalive packets donesn't resolve problem, I was write dump of ffmpeg, it show periodic messages like
[rtsp @ 0x55c8d728abc0] Too short data for FU-A H.264 RTP packet speed= 1.1x
[rtsp @ 0x55c8d728abc0] Too short data for FU-A H.264 RTP packet speed=1.06x
[rtsp @ 0x55c8d728abc0] Too short data for FU-A H.264 RTP packet speed=1.05x
[rtsp @ 0x55c8d728abc0] Too short data for FU-A H.264 RTP packet speed=1.05x
[rtsp @ 0x55c8d728abc0] Too short data for FU-A H.264 RTP packet speed=1.04x
[rtsp @ 0x55c8d728abc0] Too short data for FU-A H.264 RTP packet speed=1.04x
[rtsp @ 0x55c8d728abc0] Too short data for FU-A H.264 RTP packet speed=1.04x
[rtsp @ 0x55c8d728abc0] Too short data for FU-A H.264 RTP packet speed=1.03x
[rtsp @ 0x55c8d728abc0] Too short data for FU-A H.264 RTP packet speed=1.03x
[rtsp @ 0x55c8d728abc0] Too short data for FU-A H.264 RTP packet speed=1.03x
[rtsp @ 0x55c8d728abc0] Too short data for FU-A H.264 RTP packet speed=1.02x
[rtsp @ 0x55c8d728abc0] Too short data for FU-A H.264 RTP packet speed=1.02x
and dump file of ffmpeg by url:
https://drive.google.com/file/d/1nGt3lQwCY14UuMsfgOksjrgSKyIRYVYx/view?usp=sharing
mb it it will help resolve problem

That's another issue that depends on the fact that the bitrate is too high for your network, the question is: does the connection stays open for more than 120 secs?

and i mean the connection between the camera and the server, in which ffmpeg is not involved.

not always:
2021/11/08 09:24:22 INF [path proxied43] [rtsp source] ready
2021/11/08 09:26:22 INF [path proxied43] [rtsp source] ERR: EOF
2021/11/08 09:26:27 INF [path proxied43] [rtsp source] ready
2021/11/08 09:28:27 INF [path proxied43] [rtsp source] ERR: EOF
2021/11/08 09:28:32 INF [path proxied43] [rtsp source] ready
2021/11/08 09:37:05 INF [path proxied43] [rtsp source] ERR: EOF
2021/11/08 09:37:10 INF [path proxied43] [rtsp source] ready
2021/11/08 09:39:10 INF [path proxied43] [rtsp source] ERR: EOF
2021/11/08 09:39:16 INF [path proxied43] [rtsp source] ready
2021/11/08 09:44:49 INF [path proxied43] [rtsp source] ERR: EOF
2021/11/08 09:44:54 INF [path proxied43] [rtsp source] ready
2021/11/08 09:46:54 INF [path proxied43] [rtsp source] ERR: EOF
2021/11/08 09:46:59 INF [path proxied43] [rtsp source] ready
2021/11/08 09:50:32 INF [path proxied43] [rtsp source] ERR: EOF
2021/11/08 09:50:37 INF [path proxied43] [rtsp source] ready
2021/11/08 09:52:37 INF [path proxied43] [rtsp source] ERR: EOF
2021/11/08 09:52:42 INF [path proxied43] [rtsp source] ready
2021/11/08 10:01:13 INF [path proxied43] [rtsp source] ERR: EOF
2021/11/08 10:01:18 INF [path proxied43] [rtsp source] ready
2021/11/08 10:03:18 INF [path proxied43] [rtsp source] ERR: EOF
2021/11/08 10:03:23 INF [path proxied43] [rtsp source] ready
2021/11/08 10:12:27 INF [path proxied43] [rtsp source] ERR: EOF
2021/11/08 10:12:32 INF [path proxied43] [rtsp source] ready

2021/11/08 09:28:32 INF [path proxied43] [rtsp source] ready
2021/11/08 09:37:05 INF [path proxied43] [rtsp source] ERR: EOF

rtsp-simple-server.log

@icrab could you produce a pcap that shows a working connection between the camera and VLC? in this way we can find out the difference. thanks

@icrab could you produce a pcap that shows a working connection between the camera and VLC? in this way we can find out the difference. thanks

@aler9

and dump file of ffmpeg by url: https://drive.google.com/file/d/1nGt3lQwCY14UuMsfgOksjrgSKyIRYVYx/view?usp=sharing
mb it it will help resolve problem

ffmpeg is not suitable?

Yes, ffmpeg is suitable, sorry for not looking at it. The differences between ffmpeg and rtsp-simple-server that i could spot are:

ffmpeg inserts a x-Dynamic-Rate: 0 header in SETUP requests
ffmpeg doesn't send any RTCP receiver report during transmission

please try again with this nightly release and let me know if it works:
rtsp-simple-server_v0.17.8-9-g9c466fc_darwin_amd64.tar.gz
rtsp-simple-server_v0.17.8-9-g9c466fc_linux_amd64.tar.gz
rtsp-simple-server_v0.17.8-9-g9c466fc_linux_arm64v8.tar.gz
rtsp-simple-server_v0.17.8-9-g9c466fc_linux_armv6.tar.gz
rtsp-simple-server_v0.17.8-9-g9c466fc_linux_armv7.tar.gz
rtsp-simple-server_v0.17.8-9-g9c466fc_windows_amd64.zip

Thank you very much! It'is works!

added in v0.17.10


[QUESTION] Selecting different midi input devices

Question
How do I select a different midi input device? I can scroll to it on the available midi devices but I can't figure out how to actually select it. Im not sure what the floppy disk and X buttons do, as pressing them doesn't change anything. I got my piano working once before, but I've never figured out how to replicate that again. I have a Yamaha P-125 if that helps. The one time it worked for me, the mod was great :)
Environment (if applicable):

OS: Windows 10
Mod Version: 1.19-3.0.3
Minecraft Version: 1.19.2
Forge Version: 43.2.0

not sure what fixed it but i restarted both server and computer, as well as added cobblemon to the modpack and it now works fine. :)


Update APIs to ret ChInfo on open/update/close ch

Description

This is changeset 4 (final) for using uniform data formats accross different
APIs.

Update RespondChProposal, SendChUpdate, RespondChUpdate and CloseCh
APIs to return ChInfo on successful execution. Update ch.GetBalInfo also
to return ChInfo and rename it to ch.GetChInfo.

In [app/payment] SendPayChUpdate, two mutex protected calls were used
in succession:To fix this, add methods to read fixed parameters of a channel without mutex
protection and use it read Currency and Parts.

Category

Implementation Task
Relevant issue

Closes #108.
Testing

No new functionality / tests were added, all existing tests should pass.
One test
Steps to run the tests

Checklist

[x] Name is added to the NOTICE file, if it is not present already.
[x] Changes are rebased onto the target branch.

This should be merged only after #115.


[mongodb] Add 8.0

https://www.mongodb.com/blog/post/top-4-reasons-to-use-mongodb-8-0

Close in favor #5832


Cleanup error usage

What this PR does / why we need it:
Use github.com/pkg/errors for defining errors.
Instead of masking errors with fmt.Errorf(), uses errors.Wrap where appropriate.
Incidentally this also fixes some formatting issues in certain error messages.

@cpuguy83 thanks for this! In general we like to pave vendor/ changes discretely, and in advance to avoid merge conflicts. But because you authored the PR that induced these conflicts we're probably 👍 here :)

Thanks! I did at least put the vendor change in a separate commit here (though I guess I did not on the last change).
This is rebased.

/lgtm


Auto fix minor issues (w)

Might be a bit of a silly question - is it possible to auto correct minor issues much like fixmyjs?

Could this postcss project help with this?
https://github.com/postcss/postcss-scss

@sds is this a new addition to the Sass library since this was discussed? http://sass-lang.com/documentation/Sass/SCSS/Parser.html

@evoactivity No, that doesn't expose a parse tree outside of the JavaScript runtime. Since it is written in JavaScript, integration would be difficult except via a command line interface of some kind. Even then, it does not support "rewriting" the parse tree and re-serializing back to SCSS.
@thegranddesign: No, the problem is not parsing. The problem is being able to modify the parse tree and serialize it back into code without inadvertently changing the rest of the indentation/formatting in the document.
Sass::Tree::Node's to_sass method is not a 1:1 mapping of the original source code that generated the Sass::Tree::Node, making it impractical for use in an auto-correction feature.


Improve automatic dark mode support

for prefers-color-scheme: dark @media query
and [data-color-mode: auto]

LINKED ISSUES:
https://github.com/sindresorhus/refined-github/pull/3806#issuecomment-761849635

TEST ENVIRONMENT:

Dark Mode is enabled for GitHub
System-wide dark mode is enabled

some way where the <html> tag has data-color-mode: auto

STEPS TO TEST

Show Whitespace

open any source file
confirm whether whitespace indicators are displayed

Conflict Markers

open a pull request with merge conflicts
confirm whether the :warning: sign is darker

Reaction Avatars

open any issue page
react on any comment
confirm whether there are incorrect white borders on the reaction
emoji or the reaction avatars

Rather than duplicating the selector and color we should prefer existing variables

This isn't resolved in conflict-marker

Rather than duplicating the selector and color we should prefer existing variables

This isn't resolved in conflict-marker


Update He-Chain

Project Abstract

Please provide a brief description of your project here summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

For which grant level are you applying?

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $50,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for > $100k Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[x] A BTC or Ethereum (DAI/USDT) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledged the terms and conditions.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted.

Update He-Chain:

Rename He-Chain to Gafi (gafi.network)
Add pallet_proof_mapping to milestone 1
Add pallet_staking_pool to milestone 1

Thank you, please check the pull request again

Hi @semuelle, thank you for your quick advice, please let me explain the two new pallets.
pallet_staking_pool: this is the additional pallet to provide users one more option to join the pool so it does not replace original modules. Sorry for the name "staking" making confusion, this option basically locks the amount of token to give users a discount on transaction fees.
pallet_proof_mapping: this is extended from the default trait (AddressMapping)[https://github.com/paritytech/frontier/blob/master/frame/evm/src/lib.rs#L504] of Frontier and claim token of Polkadot. The Unified Accounts of Moonbeam is great for EVM compatible projects, we only affair that took us a lot more resources to integrate, and the trade-off for scalability in the future when completely using H160 so we think using the default mechanism is fitted with our philosophy "support EVM" not "EVM compatible".

Just to add for reference https://github.com/w3f/Grants-Program/pull/836

Sorry for the late reply. Besides frontier the only thing that comes to my mind, which might be helpful for you are the evm efforts by acala, e.g. https://github.com/AcalaNetwork/bodhi.js

Ah and https://github.com/AstarNetwork/astarbase


org-journal default path conflicting with user set path on update

Hi,
Just noticed after last melpa update that the org-journal default path overrides the user set path after update. I am not sure this is an issue to post here (never interacted like this before) - I thought I'd signal about it; it would be nice if somehow an update would not require ulterior user interaction regarding custom path settings - if possible.

Thank you for the heads-up. I am currently on vacation and won't be able to look into it. I will investigate once I get back home.
Could you describe in a little more detail how org-journal overrides your path? Please tell me your operating system, and your org-journal related settings in your init.el or .emacs file.

Thank you for the heads-up. I am currently on vacation and won't be able to look into it. I will investigate once I get back home.
Could you describe in a little more detail how org-journal overrides your path? Please tell me your operating system, and your org-journal related settings in your init.el or .emacs file.

Thanks :)
Now that you asked about init.el org-journal related settings - well, looking into it I had nothing (and it worked even so, starting a new entry from calendar view only). I vaguely remember getting into org-journal very tired, without paying too much attention. What I did then was to search for "~/Documents/journal/" and add my own path instead (at line 106) in org-journal.el.
Now I added this to init.el:
(require 'org-journal)
(setq journal-dir "~/org/journal")
Much likely it will now work on a subsequent update.
Sorry for the mess, I am not a programmer and the "journal-dir is also a customizable variable. The default value for journal-dir is ~/Documents/journal/." comment/explanation from the beginnings of org-journal.el did not really ring any bell to me. I now looked it up how to define a variable (setq) and hopefully it is all right the way I wrote up here.
Please close this when you see fit as there is no issue at all (except for the fact that someone who is not a programmer does not see - without an example as babies :)) - what and how exactly should be in init.el.
Have a nice vacation! Happy 2016! :)

Thanks :)
Now that you asked about init.el org-journal related settings - well, looking into it I had nothing (and it worked even so, starting a new entry from calendar view only). I vaguely remember getting into org-journal very tired, without paying too much attention. What I did then was to search for "~/Documents/journal/" and add my own path instead (at line 106) in org-journal.el.
Now I added this to init.el:
(require 'org-journal)
(setq journal-dir "~/org/journal")
Much likely it will now work on a subsequent update.
Sorry for the mess, I am not a programmer and the "journal-dir is also a customizable variable. The default value for journal-dir is ~/Documents/journal/." comment/explanation from the beginnings of org-journal.el did not really ring any bell to me. I now looked it up how to define a variable (setq) and hopefully it is all right the way I wrote up here.
Please close this when you see fit as there is no issue at all (except for the fact that someone who is not a programmer does not see - without an example as babies :)) - what and how exactly should be in init.el.
Have a nice vacation! Happy 2016! :)

Update:
With this in my init.el:
(require 'org-journal)
(setq journal-dir "~/org/journal")

it seems that it is still not working as it should.
I get this error message:

Warning (initialization): An error occurred while loading /home/*username*/.emacs.d/init.el': File error: Cannot open load file, no such file or directory, org-journal To ensure normal operation, you should investigate and remove the cause of the error in your initialization file.  Start Emacs with the --debug-init' option to view a complete error backtrace.
What exactly should I putin init.el so this message does not appear?
I can still start a new entry with C-c C-j, nut this error message obviously means that something is not correct.
Starting Emacs with '--debug-init' option it says:
Debugger entered--Lisp error: (file-error "Cannot open load file" "no such file or directory" "org-journal")
require(org-journal)
eval-buffer(#<buffer  load> nil "/home/username/.emacs.d/init.el" nil t)  ; Reading at buffer position 163
load-with-code-conversion("/home/username/.emacs.d/init.el" "/home/username/.emacs.d/init.el" t t)
load("/home/username/.emacs.d/init" t t)
#[0 "^H\205\262^@     \306=\203^Q^@\307^H\310Q\202;^@ \311=\204^^^@\307^H\312Q\202;^@\313\307\314\315#\203*^@\316\202;^@\313\307\314\317#\2$
command-line()
normal-top-level()
Location of org-journal related files on my computer:
~/.emacs.d/elpa/org-journal-20151228.603

Thank you for this further investigation. Since org-journal in general is working in your Emacs, you should not need to (require 'org-journal) manually. Without the require, your init.el and setq should work as intended.
However, it might be easier to use customize instead to change your org-journal-dir. Select Options --> Customize --> Options Matching from your menubar, then type org-journal, and you should see a clickable interface to change and save org-journal-dir. Alternatively, type M-x, then customize and use the search box to search for org-journal to access the same page.
In general, the Emacs packaging system assumes that you do not change the contents of the packages themselves. Instead, most packages define customizable options (such as org-journal-dir), which can be changed either in your init.el or through customize. This is the preferred way of changing the behavior of Emacs packages.
As a side note, there are many ways to change things in Emacs, and customize only scratches the surface of what is possible. One of the main features of Emacs is that absolutely everything can be changed by the user. And none of these require you to change the original source code.
Did this solve your issue?

Interestingly (and now I am completely confused regarding some aspects) - now journal and all its keybindings seem to work without any init.el customizations.
The above lines I put in init.el still keep giving me the error on startup, so I commented them out and org-journal works.
I was not aware of customization possibilities in the menubar, Emacs runs in Gnome Terminal stripped down to menu-less view here and rarely in graphic mode. But I get the point, it is worth looking into the menus once in a while. I guess it was scary all the time looking into the mirad of options there, that's why life felt better without.
Thanks for the feedbacks!
Issue solved (I just don't know how it happened) - no more problems.

Should I close or you do it?


Windows build missing ucrtbased.dll and VCRUNTIME140D.dll

Issue:
Fresh conda installation of gmt==6.0.0 on Windows doesn't seem to work. After installing gmt inside a clean conda environment using conda create -n gmt gmt, running gmt in Anaconda prompt results in the popups below:

Transcription: The code execution cannot proceed because ucrtbased.dll was not found. Reinstalling the program may fix this problem.

Transcription: The code execution cannot proceed because VCRUNTIME140D.dll was not found. Reinstalling the program may fix this problem.

Environment (conda list):

$ conda list
# Name                    Version                   Build  Channel
boost-cpp                 1.70.0               h6a4c333_2    conda-forge
bzip2                     1.0.8                hfa6e2cd_1    conda-forge
ca-certificates           2019.9.11            hecc5488_0    conda-forge
certifi                   2019.9.11                py38_0    conda-forge
cfitsio                   3.470                hfa6e2cd_2    conda-forge
curl                      7.65.3               h4496350_0    conda-forge
expat                     2.2.5             he025d50_1004    conda-forge
ffmpeg                    4.2                  h6538335_0    conda-forge
fftw                      3.3.8           nompi_hbc43ac9_1110    conda-forge
freetype                  2.10.0               h563cfd7_1    conda-forge
freexl                    1.0.5             hd288d7e_1002    conda-forge
gdal                      3.0.2            py38h2fee047_2    conda-forge
geos                      3.7.2                he025d50_2    conda-forge
geotiff                   1.5.1                ha8299ad_6    conda-forge
gettext                   <IP_ADDRESS>          hb01d8f6_1002    conda-forge
ghostscript               9.22                 he025d50_1    conda-forge
glib                      2.58.3          py38hc0c2ac7_1002    conda-forge
gmt                       6.0.0                h54a23f7_0    conda-forge
hdf4                      4.2.13            hf8e6fe8_1003    conda-forge
hdf5                      1.10.5          nompi_ha405e13_1104    conda-forge
icu                       64.2                 he025d50_1    conda-forge
intel-openmp              2019.4                      245
jpeg                      9c                hfa6e2cd_1001    conda-forge
kealib                    1.4.10            hf7dc31f_1005    conda-forge
krb5                      1.16.3            hdd46e55_1001    conda-forge
libblas                   3.8.0                    14_mkl    conda-forge
libcblas                  3.8.0                    14_mkl    conda-forge
libcurl                   7.65.3               h4496350_0    conda-forge
libffi                    3.2.1             h6538335_1006    conda-forge
libgdal                   3.0.2                hd349289_2    conda-forge
libiconv                  1.15              hfa6e2cd_1005    conda-forge
libkml                    1.3.0             h4ece8bf_1010    conda-forge
liblapack                 3.8.0                    14_mkl    conda-forge
libnetcdf                 4.7.1           nompi_h8d74e2a_101    conda-forge
libpng                    1.6.37               h7602738_0    conda-forge
libpq                     11.5                 hb0bdaea_2    conda-forge
libspatialite             4.3.0a            h2b2ca8d_1032    conda-forge
libssh2                   1.8.2                h642c060_2    conda-forge
libtiff                   4.1.0                h2e92f26_0    conda-forge
libxml2                   2.9.10               h9ce36c8_0    conda-forge
lz4-c                     1.8.3             he025d50_1001    conda-forge
m2w64-expat               2.1.1                         2
m2w64-gcc-libgfortran     5.3.0                         6
m2w64-gcc-libs            5.3.0                         7
m2w64-gcc-libs-core       5.3.0                         7
m2w64-gettext             0.19.7                        2
m2w64-gmp                 6.1.0                         2
m2w64-libiconv            1.14                          6
m2w64-libwinpthread-git   <IP_ADDRESS>34.697f757               2
m2w64-xz                  5.2.2                         2
mkl                       2019.4                      245
msys2-conda-epoch         20160418                      1
numpy                     1.17.3           py38hc71023c_0    conda-forge
openjpeg                  2.3.1                hb24c2e3_1    conda-forge
openssl                   1.1.1d               hfa6e2cd_0    conda-forge
pcre                      8.43                 h6538335_0    conda-forge
pip                       19.3.1                   py38_0    conda-forge
poppler                   0.67.0               h92819f6_7    conda-forge
poppler-data              0.4.9                         1    conda-forge
postgresql                11.5                 h06f7779_2    conda-forge
proj                      6.2.1                ha7a8c7b_0    conda-forge
python                    3.8.0                hc9e8b01_3    conda-forge
setuptools                41.6.0                   py38_1    conda-forge
sqlite                    3.30.1               hfa6e2cd_0    conda-forge
tbb                       2018.0.5             he980bc4_0    conda-forge
tiledb                    1.6.2                h6bfbd54_2    conda-forge
tk                        8.6.9             hfa6e2cd_1003    conda-forge
vc                        14.1                 h0510ff6_4
vs2015_runtime            14.16.27012          hf0eaf9b_0
wheel                     0.33.6                   py38_0    conda-forge
wincertstore              0.2                   py38_1003    conda-forge
xerces-c                  3.2.2             h6538335_1004    conda-forge
xz                        5.2.4             h2fa13f4_1001    conda-forge
zlib                      1.2.11            h2fa13f4_1006    conda-forge
zstd                      1.4.3                hd8a0e53_0    conda-forge

Details about  conda and system ( conda info ):

$ conda info
     active environment : gmt
    active env location : C:\Users\username\AppData\Local\Continuum\miniconda3\envs\gmt
            shell level : 2
       user config file : C:\Users\username\.condarc
 populated config files : C:\Users\username\.condarc
          conda version : 4.7.12
    conda-build version : not installed
         python version : 3.7.4.final.0
       virtual packages :
       base environment : C:\Users\username\AppData\Local\Continuum\miniconda3  (writable)
           channel URLs : https://conda.anaconda.org/conda-forge/win-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/win-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/win-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://repo.anaconda.com/pkgs/msys2/win-64
                          https://repo.anaconda.com/pkgs/msys2/noarch
          package cache : C:\Users\username\AppData\Local\Continuum\miniconda3\pkgs
                          C:\Users\username\.conda\pkgs
                          C:\Users\username\AppData\Local\conda\conda\pkgs
       envs directories : C:\Users\username\AppData\Local\Continuum\miniconda3\envs
                          C:\Users\username\.conda\envs
                          C:\Users\username\AppData\Local\conda\conda\envs
               platform : win-64
             user-agent : conda/4.7.12 requests/2.22.0 CPython/3.7.4 Windows/10 Windows/10.0.16299
          administrator : False
             netrc file : None
           offline mode : False

It shouldn't happen. VCRUNTIME140D.dll is a required library for debug version, but the conda-forge package is built with CMAKE_BUILD_TYPE=Release.

Right, I can reproduce the same issue on my Windows machine.

This is the DLL dependency tree reported by Dependency Walker.

It's obvious that the zstd library needs the debug version libraries (i.e. vcruntime140d.dll and ucrtbased.dll), which causes the trouble. This is a bug of the zstd feedstock and was fixed in https://github.com/conda-forge/zstd-feedstock/pull/36.
GMT should work well if the latest zstd (1.4.4, build 1) is installed, but the conda --list shows zstd 1.4.3 is installed. Not sure what we should do here.

It's possible that libtiff is pinning zstd to 1.4.3 in your environment. See conda-forge/libtiff-feedstock#44.

That makes sense. Thanks for letting us know.

Actually, I just learned it's a global pinning issue:
https://github.com/conda-forge/libtiff-feedstock/pull/45#issuecomment-554495921

Thanks for the information @jpgill86. Didn't know about global pinning before! I found some documentation at https://conda-forge.org/docs/maintainer/infrastructure.html#conda-forge-pinning and will read up on it now.

The global pinning has migrated to zstd 1.4.4 (https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/334). @weiji14 Could you try if gmt works now?

If not, we probably need to rebuild the gmt package.

Ok, I'll try and make a push at https://github.com/GenericMappingTools/pygmt/pull/354 and see how the tests go. Might take ~15min.

Thanks for the information @jpgill86. Didn't know about global pinning before! I found some documentation at https://conda-forge.org/docs/maintainer/infrastructure.html#conda-forge-pinning and will read up on it now.

We are in exactly the same boat, at the same time! 🤣 I'm currently wondering how long the migration process takes if zstd is used by many packages. Minutes? Days?

Minutes? Days?

Sorry, it will be a few days. But thanks the @CJ-Wright's automation it is way faster than before!

Minutes? Days?

Sorry, it will be a few days. But thanks the @CJ-Wright's automation it is way faster than before!

Gotcha. I'm reading about it now and am very impressed by the orchestration required to keep everything running!

If not, we probably need to rebuild the gmt package.

I've removed the "gmt" conda environment and creating a fresh one using conda create -n gmt gmt still wants to install zstd 1.4.3. Let's wait for https://github.com/conda-forge/libtiff-feedstock/pull/46 😄

The status page lets you check on the state of the migration. You can also look at the graph plot.

Cool, thanks everyone! libtiff is now updated but conda create -n gmt gmt won't work directly (yet) as it's still trying to get 4.1.0 build 0 instead of build 1. It'll just take some time for the repodata.json file to update itself and there shouldn't be a need to rebuild the gmt package.
Meanwhile, following this stackoverflow post on installing a specific build of an anaconda package, conda create -n gmt gmt libtiff=4.1.0=h21b02b4_1 or conda install  libtiff=4.1.0=h21b02b4_1 works so I'll close this issue.

Once the new packages are available on the channel, in a few hours, please let me know if they work.

Once the new packages are available on the channel, in a few hours, please let me know if they work.

I'm not using gmt, but the (possibly) related issue that prompted me to open conda-forge/libtiff-feedstock#44 is now fixed by the migration of zstd to 1.4.4. Thanks @ocefpaf!

Thanks for letting us know!

There's still some conflicts if we want to install python into the mix... libgdal depends on tiledb but the zstd rebuild in https://github.com/conda-forge/tiledb-feedstock/pull/48 only updated tiledb 1.7.0 and not 1.6.*
(base) C:\>conda create --name pygmt python=3.6 gmt=6.0.0 libtiff=4.1.0=h21b02b4_1
Solving environment: failed

UnsatisfiableError: The following specifications were found to be in conflict:
  - gmt=6.0.0 -> gdal[version='>=3.0.1,<3.1.0a0'] -> libgdal==3.0.1=h2491c49_10 -> tiledb[version='>=1.6.2,<<IP_ADDRESS>a0'] -> zstd[version='>=1.4.0,<<IP_ADDRESS>a0']
  - libtiff==4.1.0=h21b02b4_1

(base) C:\>conda create --name pygmt python=3.6 gmt=6.0.0 libtiff=4.1.0=h21b02b4_1 gdal=3.0.2
Solving environment: failed

UnsatisfiableError: The following specifications were found to be in conflict:
  - gmt=6.0.0 -> gdal[version='>=3.0.1,<3.1.0a0'] -> libgdal==3.0.1=h2491c49_10 -> tiledb[version='>=1.6.2,<<IP_ADDRESS>a0'] -> zstd[version='>=1.4.0,<<IP_ADDRESS>a0']
  - libtiff==4.1.0=h21b02b4_1

(base) C:\>conda create --name pygmt python=3.6 gmt=6.0.0 libtiff=4.1.0=h21b02b4_1 libgdal=3.0.2
Solving environment: failed

UnsatisfiableError: The following specifications were found to be in conflict:
  - libgdal=3.0.2 -> tiledb[version='>=1.6.2,<<IP_ADDRESS>a0'] -> zstd[version='>=1.4.0,<<IP_ADDRESS>a0']
  - libtiff==4.1.0=h21b02b4_1

but the zstd rebuild in conda-forge/tiledb-feedstock#48 only updated tiledb 1.7.0 and not 1.6.*

We can build the older tiledb with the new zstd but we can also update tiledb global pin. I'll work on this tomorrow.

We can build the older tiledb with the new zstd but we can also update tiledb global pin. I'll work on this tomorrow.

@ocefpaf, I've put in two pull requests to update tiledb on conda-forge, hopefully that helps a bit?

Guys, you should not be building GDAL against an external TIF lib. Just let it use it's internal TIF library. This lib is maintained by the same person I (Even Rouault) is is always most up to date. With this the zstd issue will simple go away.

Could you elaborate a bit more @joa-quim? Do you mean the GMT source code contains the TIF library already? Looking at the meta.yaml file, my impression was that we're not building gdal here (I could be wrong though), just getting the already-built gdal library on conda-forge.

No, GMT doesn't have any TIF lib. What I mean is when building GDAL, let it use its own TIF library instead of linking against an external one. See the dependencies of my GDAL (the one shipped with the GMT installer). No TIF, still one can read and create GeoTIFFs with GMT.

Ok, let me know if this makes sense. So you're saying we shouldn't be using the conda-forge built gdal because it links to an external TIF library. Instead, we should be building our own gdal without that external TIF link?

What I'm saying is that your dependency issue is coming from a GDAL that was built against an external `TIF(and, btw, aJpeg`` one). I don't know how things work on the Conda build and if you have to use the Conda GDAL's or if you can use another build.
Also, though we all would like to have a completely scriptable GMT build, please be aware that the Conda GMT build will rather more limited than the one we provide with the official installer. For example, no MEX and the GDAL build will not come with its GDAL_DATA as well as PROJ_DAT included and automatically detectable by GMT. This mean that the -Jepsg:xxx syntax will not be available with that build.
(Very late here, going to bed)

Ah I see, good to keep that in mind. Anyways, best to continue that discussion in a separate issue.
I think the upstream dependencies are settled now (i.e. conda create -n gmt gmt works), and I'll close this issue shortly after I run some tests.


[MM-26762] Archived Channels are not shown in the System Console > Channels page

Summary

Archived Channels are not shown in the System Console > Channels page. This PR addresses this problem by setting includeDeleted flag to true.
Ticket Link

https://mattermost.atlassian.net/browse/MM-26762

@srkgupta
Sorry about that. The problem you mentioned has been addressed.


Wiki Incomplete??

Someone Links trow me at localhost

Yup the wiki is incomplete for now, feel free to join the Discord if you have questions :)

Related to these issues :

https://github.com/Sygmei/ObEngine/issues/68
https://github.com/Sygmei/ObEngine/issues/70
https://github.com/Sygmei/ObEngine/issues/71
https://github.com/Sygmei/ObEngine/issues/72
https://github.com/Sygmei/ObEngine/issues/73
https://github.com/Sygmei/ObEngine/issues/74


docs(readme): update the readme

Description

Add installation and usage instructions to the readme. I will write the English version after the Japanese version is accepted.
Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

It's just a suggestion. You can have it completely rewritten.

I fixed them.

Updated the English version.


Update links to graphql client repository

@dblock The CI builds should be fixed by https://github.com/ashkan18/graphlient/pull/113.

Rebase this please?

Done @dblock 🚀


fix broken lasagna test file

I tried running this exercise on the website and it failed. It appears the test_lasagna.R file lost the source() line as well as the context() line, so it can't find the student's code.

It works correctly now. I passed the exercise and unlocked the next concept.


JS exception: "Unable to get property 'boxSizing' of undefined or null reference"

Hi!
I faced with the following issue. I'm getting JS error in console when the page contains inline SVG elements.
Link to test: https://jsfiddle.net/xL8fseze/5/embedded/result/
Environment: IE11 in "Document mode 9"

This may be due to the current style not being accessible on those elements. In this case, I’ll provide an plain object fallback so this doesn’t choke the whole process.

This has now been pushed into 0.3.0! Thanks for spotting this, @mistakster!

Cool. Thank you!


stop bleeding modifications between the different outputs

Fixes #7 :)

Nice work! I couldn't figure out why this was happening. 👍


Get the field name from its parent when it doesn't have one when collecting fields (bug 1864136)

Some fields, somewhere under the Fields entry in Acroform, could have no name (in T)
but with a parent which has a name but which isn't somewhere under Fields.
As a side-effect, this patch prevents infinite loops because of potential cycles
under Fields.

/botio integrationtest

The test failures was because of some fields with no name but with a parent which has one, but the parent was visited during the Fields collection.

/botio integrationtest


fixed text overlap issue in startblock, changed md screensize

What

Changed spacing to work on many more screen sizes without overlap
Changed medium screen size back to the tailwind config default value in useBreakpoints and tailwind.config.js

Commenting to prevent the need for scrolling through Discord later:
-I'd add a full-height flexbox and position the elements with position: absolute inside that flexbox
including the whale, the text, the gems
-I'd stick the text and arrows to the bottom
-position the gems maybe with %
-position whale in the middle
-and change the layout for smaller devices when needed


Update the Code or Documentation in order to support Laravel 5.3

Update the Code or Documentation in order to support Laravel 5.3.

I want to know when you can  Update the Code or Documentation in order to support Laravel 5.3

may be they will not  Update the Code or Documentation.
in the file 'reademe.md',I get this:

For answers you may not find in the Wiki, avoid posting issues. Feel free to ask for support on the dedicated Slack room. Make sure to mention @jasonlewis so he is notified.

I use dingo/api with Lumen 5.3  with no problem
Do you have problems?

$this->response->item($user, new UserTransformer)->getContent();
why not get the data after transform?  I use laravel 5.3

just $this->response->item($user, new UserTransformer) will suffice.

I want get the array after transform, but $this->content is orginal data;


Avoid infinite retry on closeAsync

Motivation
In MultiTopicsImpl, When the receive concurrently with close, it has a chance that make receiveAsync infinitely retry in the internalPinnedExecutor.
Modifications
If the exception is AlreadyCloseException, we don't retry.
Documentation

[ ] no-need-doc

internal bug fix

@hangc0276 @merlimat PTAL


Update PLT detail for make build_plt

The PLT that rebar will have dialyzer use is now created with make build_plt - this commit/PR explains that.
Related to PR https://github.com/rebar/rebar/pull/336

+1


MultiProcessor Implementation

MultiProcessor Implementation with Scale, Translate, and Opacity Processors
Use SceneProcessor Set's, setting up multiple processors in the sets constructor.

Hey @thedjnova
That's amazing! Really great work.
I need some time for review these changes. Then let's merge it and I will refactor code.

SetupAppearingContexts -- can't find this method (

Clamp method not found too =(

Ill check over it all on lunch, I had to pull out some project specific changes that couldn't come over and obviously missed some things.

No problem, thank you for you contributing
I will appreciate if you modify SceneView for using new processors. I will check the sample, which already exist

@thedjnova can you add extension method (Clamp) ?

Its an Internal Xamarin extension, just pushed a commit that should resolve issues. Also remove the condition, doesn't hurt my builds removing so better to lose the useless config options.

http://www.giphy.com/gifs/1dLRxDQ9VLoBPwLP6U

This is good base for scene feature, but as you can see sometime items blink a little during navigating.
And there is a bug with size of new current element during pan action.
I think, We can merge this PR, but there is a lot of work for refactoring and bugfixing =)

Thanks, Ill get some time in on it over the weekend.
If its merged in raise the bugs and ill pick them up Saturday (depending on the wife ha).

@jaspervanmegroot if you adjust the InitialBackPositionPercentage value in the BaseTranslationProcessor then it adjusts where the offscreen cards are. (@AndreiMisiukevich had that in there already)

Ok, cool
I won't merge it until you end with bugs =)
I think it would better if you end with this part, then I will refactor code =)

@thedjnova should I wait some new code improvements? =)

I don't think I'll be able to get much done until maybe Sunday, so yea hold off on merging until I can have a look.

@thedjnova u r  superstar )

I hope we will figure out with it


Remove Mozilla Public License

https://github.com/xspec/xspec/tree/master/java/com/jenitennison/xslt/tests is under the Mozilla Public License.
The reason I guess is that Jeni started the code from one of the Saxon source code files which originally was contributed by Edwin Glaser. If we remove the remnant of the original code (mostly comments, I guess) and get Jeni's approval, we're probably allowed to change its license to MIT.
(Also we may want to change its namespace from com.jenitennison.xslt.tests to io.xspec.xspec.saxon.something.)

the remnant of the original code (mostly comments, I guess)

Indeed, comparing these files, the original Mozilla Public License portion appears to be, essentially, only comments.

net/sf/saxon/trace/TraceListener.java in Saxon <IP_ADDRESS>
Jeni's initial commit

@JeniT : do you have any comments on this issue?

I don't have any objections to changing the licence or the namespace :)

@JeniT : Thanks for your reply.
@AirQuick : Did you have in mind something like the following?

In the Java source file, remove the comments that Jeni didn't change between the Saxon <IP_ADDRESS> TraceListener.java file and her initial commit of the XSLTCoverageTraceListener.java file.
Change the set of comments at the bottom of the file to something that gives credit without asserting the Mozilla license. Perhaps something like the block of code below
In README.md at the top of this repo, remove the sentence that mentions the Mozilla license.

// This file is part of the XSpec repository, github.com/xspec/xspec.
//
// Development credits:
// - Methods implemented by Jeni Tennison
// - Extended for Saxon 9.7 by Sandro Cirulli, github.com/cirulls
// - Extended for Saxon 12.4 by AirQuick, github.com/AirQuick
//
// Portions created by Jeni Tennison are Copyright (C) Jeni Tennison.
// All Rights Reserved.
//
// This file was inspired by net/sf/saxon/trace/TraceListener.java
// in Saxon <IP_ADDRESS>. That file was developed by Edwin Glaser and
// heavily modified by Michael Kay.

Cc: @xspec/xspec to keep others informed and in case anyone else has advice or opinions.


Archive fabric-private-chaincode which has transitioned to Fabric

Signed-off-by: Arnaud J Le Hors<EMAIL_ADDRESS>

@trbs @vipinsun : Can you please review?

@lehors @tkuhrt I propose deleting this repo: https://github.com/hyperledger-labs/fabric-private-chaincode-wasm since it was never used (as a part of this process)

Sounds good to me.


Update the ReactiveUI.Wpf project to new format

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Attempts to update the ReactiveUI.WPF project to SDK format

@bradphelan,
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://cla2.dotnetfoundation.org.
It will cover your contributions to all .NET Foundation-managed open source projects.
Thanks,
.NET Foundation Pull Request Bot

@bradphelan, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, .NET Foundation Pull Request Bot

The Cake file needs to pull in the submodule.

"C:\projects\reactiveui\src\WpfNetStandardSample\CustomProjectSystem\CustomProject.props" was not found

Any idea how to do that?

I updated the YML file and it now seems to be working

There is an error with the Nuget Pack of the WPF project

C:\Program Files\dotnet\sdk\2.0.2\Sdks\NuGet.Build.Tasks.Pack\build\NuGet.Build.Tasks.Pack.targets(245,15): error MSB4064: The "AllowedOutputExtensionsInPackageBuildOutputFolder" parameter is not supported by the "PackTask" task. Verify the parameter exist

I'll wait till I get an answer on
https://stackoverflow.com/questions/47218910/what-is-the-source-of-the-error-allowedoutputextensionsinpackagebuildoutputfolde

I would just copy the files in your local repo instead of working with a submodule. If the remote repo breaks now also your build will break.

Changes Unknown when pulling 9c9411b801da65a0cd94e96b5ab684d27095273f on bradphelan:feature/wpf-sdk into ** on reactiveui:develop**.

Hi @njannink this is just a temp work around for a feature that I hope within 6 month MS implements. WPF support in SDK style projects must be a short term goal for them ( I hope ). I don't think the upstream repo for the submodule is going anywhere and if the author fixes problems with it then integration is easier than copying files over.

@kentcb Was this helpful?

@bradphelan totally - thanks!
I'm not sure that we're gonna merge it though, since it is likely to make a complicated build all the more complicated for little benefit. I suspect the right thing to do is wait for official support.

np
On Thu, 23 Nov 2017, 21:30 Kent Boogaart<EMAIL_ADDRESS>wrote:

@bradphelan https://github.com/bradphelan totally - thanks!
I'm not sure that we're gonna merge it though, since it is likely to make
a complicated build all the more complicated for little benefit. I suspect
the right thing to do is wait for official support.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/reactiveui/ReactiveUI/pull/1533#issuecomment-346693773,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABE8qSXG5IXwBPhR8Qh9W18A0e4IuY6ks5s5dXegaJpZM4QZK5n
.

Closing as this has been done.


Need to verify if Triangle is installed

Need some way to check to see if Triangle is installed long before it is called so that we don't waste time setting up the meshing if Triangle can't be found.

Done in 0.0.4


Fix hasher

This PR finally fixes what I was experiencing in #83.
Turns out that the HasherObject implementation assumes that, in Hasher,  all the write_TYPE functions delegate their implementation to write. As in, it is only necessary to have an FFI-safe callback for write. This is true in the standard library, where write_u8 and similars rely on the default implementation of the Hasher trait. However, as soon as the hasher is changed to one that doesn't do this, HasherObject stops working as intended.
The AHash hasher overrides write_TYPE so that, for example, write_u8 delegates to write_u64 instead of write for performance reasons. If someone hashes a u8 with Hasher and then with HasherObject, they will be different. Hasher will call write_u64, but HasherObject will call write.
This issue propagated to other structs like MapKey or MapQuery, breaking more parts of abi_stable. It can be fixed by just implementing each write_TYPE function in HasherObject, rather than just write.
The only part that's left is implementing the write_{i,u}128 functions, for which I would love to have your opinion, @rodrimati1992. Should I implement them as opaque types somehow (not sure if that would be possible)? Or do I throw a panic! in there indicating that it's unsupported?
Thanks to @darach, @Licenser, and @mfelsche for their help in solving this issue!

@rodrimati1992, would it be possible to merge this & release v0.11? Or what's the schedule for that release? Do you have anything else planned?


refactor: collapse eg-metrics-svc into eg-svc

What type of PR is this?
refactor: Collapse envoy-gateway-metrics-service into envoy-gateway service with a metrics port
Which issue(s) this PR fixes:
Fixes #2919

/retest

please kindly wait for https://github.com/envoyproxy/gateway/pull/2935

@ShyunnY can you run make gen-check locally?

@zirain  Actually I can't run it, I need to change the existing helm/default.yaml file

/retest

@zirain Actually I can't run it, I need to change the existing helm/default.yaml file

make helm-template will update it, and it's part of make gen-check


Add durable and exchange to QueueConfig

Adds an option to QueueConfig that allows you to set the durable flag on the queue.
Also adds the ability to specify the exchange to bind to when configuring a handler. Only adds support for the topic exchange so far.
I'm not 100% clear on the AMQP implications of this but it is believed this is required for event handlers.

Support for the "durable" flag is missing.


Name of the container

Am i missing something or cant you set the name of the container manually?

Hello @larsbloch, actually the name of the container is based on the registry path


Slight improvements that address some of the submitted issues plus other minor tweaks

Examples:

They are minor tweaks, but I believe that they can improve the overall experience.

I still got a problemo. Look at the attached file pls

In the file you attached in the main post, it shows the text, but for me, it only shows it when I hover over the button. Not sure if this is intentional or not.

I am sorry I had a lot of school work, but now I want to finish it.
@darkknightSup  When you clone my repo, it doesn't work for you?
I tested it on two devices, and it works fine. So I am wandering.

I am sorry I had a lot of school work, but now I want to finish it.
@darkknightSup When you clone my repo, it doesn't work for you?
I tested it on two devices, and it works fine. So I am wandering.

Here is a screen recording:
https://user-images.githubusercontent.com/105766552/169626806-ec1e586b-1843-43c8-b6e5-2741dac76180.mov
As you can see, for the undo, it is fine, but for everything else, nothing works...

It seems like the original version, but I have no idea; as you said that it's from my clone. So you probably need to do it manually yourself - if you want it, and this pull request is not working, I should close it.


Platform Key Vault Secret Scope Permissions

Add permissions to platform secret scope backed by KV in ADB to specific admin group.

Already implemented in main


cancelling node drop in "beforeDrop" not possible with a delay?

so it seems like you can easily cancel dropping of a node in beforeDrop by
params.source.nodeScope.$$apply = false
or even with a confirmation popup:
params.source.nodeScope.$$apply = confirm("Are you sure?");
that will however work only if it can run instantly - if there is some delay in choosing between true and false, it will just default to true and finishes the drop instantly
In my case, i want to make an api call to the backend before it drops - if it succeeds, i would let it drop, if it fails, i would revert it..
the code would looks something like this:
var updateNodes =  function() {
$http({ url: /api/saveStructure, })
.then(function(response) {
//success
return true
}, function(response) {
//fail
return false
});
}
params.source.nodeScope.$$apply = updateNodes()
anyone has ideas how to make it wait for a response before dropping the node?

Closing this issue due to inactivity. See #815 for more information.
Please create a new issue is this still occurs with the current version of the component.


[Docs]Add RVM Description to Meshery Documentation

Current State:
Windows users are having issues using Jekyll and there's no description to help with that.
Desired State:
Provide a description of RVM to the set up your development environment section of the Meshery Doc by adding this line.
Note: Windows users can run Jekyll by following the [Windows Installation Guide](https://jekyllrb.com/docs/installation/windows/) and also install Ruby Version Manager [RVM](https://rvm.io) - a command-line tool which allows you to easily install, manage and work with multiple ruby environments on your local machine. Alternatively, if you're running Windows 10, updated to version 1903 Build 18362 or higher you can upgrade to Windows Subsystem for Linux [WSL](https://docs.microsoft.com/en-us/windows/wsl/install-win10)

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

I'd like to do this

Sure @MoeRayo do go ahead. 👍🏽

@PluckyPrecious The above is what the site looks like currently, and i saw that some of the things i am required to add are already in the current page. so I would like to know, do I remove the current one totally and add this new one or do I add some of the things you just sent and reconstruct it?

Good question. @MoeRayo 😊 This issue is to add an extra note for Windows users, as Jekyll doesn’t officially support windows. It will help guide them on the necessary step to follow during installation specifically for windows in order to have it run on their local machine. Please leave the current one as it is, you can add the additional lines right after Jekyll Docs .👍🏽


[extractor/cspan] Support of C-Span congress videos

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
A new extractor for C-Span congress videos:
https://www.c-span.org/congress/?chamber=house&date=2017-12-13&t=1513208380

I added the necessary corrections. I hope it looks better now.

Also added a small fix for wrong title code, like this: "U.S. Senate"
It's found on this page:
https://www.c-span.org/video/?517228-1/senate-debates-russian-sanctions-voting-rights-legislation

All necessary corrections are added.

Imports are fixed. Everything works fine, except for the bug with the wrong H2 tag.

I added the necessary corrections.


[Peek] Include resolution information in tooltip for media files

Description of the new feature / enhancement
The file size is currently shown for media files, but not the resolution, which is commonly useful, and is displayed in Explorer's tooltip.
In Explorer, the specific string format is: "Dimensions: 1920 x 1080".
Scenario when this would be used?
When viewing any media file in Peek.
Supporting information
This information is available to use already, as it's retrieved when sizing the window for preview display. The method UpdatePreviewSizeAsync in FilePreview.xaml.cs calls GetPreviewSizeAsync on the current previewer, which yields back the size of the media being displayed.
It would be straightforward to add this information to the tooltip, as that is the very next thing that is updated in FilePreview.xaml.cs.
I think this would be a good first issue for someone to work on.
Note: there is already an issue to add image metadata to Peek - #28566. This new issue is just to add the resolution, however, and not EXIF information, so I don't think it's a duplicate.

@daverayment  issue does call out resolution and uplevels to "details".  This is the type of subset item i'd include into the that.
/dup https://github.com/microsoft/PowerToys/issues/28566


Trying to compile VTK 4.13.3 with only ITKGroup_Core is generating few errors with xutility

Description
Compilation doesn't work for gdcmMSFF
Steps to Reproduce
OPTIONS
ITK_BUILD_DEFAULT_MODULES:OFF
ITKGroup_Core:ON

Download from repo revision tag 4.13.3
Open CMake-GUI on Windows
Set ITK_BUILD_DEFAULT_MODULES:OFF and ITKGroup_Core:ON

Expected behavior
Normal compilation
Actual behavior

Reproducibility
100%
Versions
v4.13.3
Environment
Windows 10, Visual Studio 2019 Community, vcpkg, CMake 3.18.2

I cannot reproduce this. But I do not have vcpkg. So that might be the source of your problem.

How come that vcpkg is the problem? Based on what analysis?

I use Windows 10, CMake 3.20.1, and up to date VS2019. And I cannot reproduce your problem. Hence, vcpkg is the most likely culprit.

Ok you mean that I have packages installed within vcpkg which are also included inside of VTK that are conflicting?

Do you have the latest VS? I have Version 16.9.4.

ITK 4.13 is no longer supported. These issues have been resolved in the latest version of ITK 5. Please migrate to ITK 5.

I cannot migrate to ITK 5 because a lot of files are not present anymore and will require a huge refactoring of main project.

ITK 4.13 is now over 3 years old. While we will still accept other people's patches to it, we have stopped working on it.


[incubator/kafka] "found invalid field updateStrategy for v1beta1.StatefulSetSpec" on install

Is this a request for help?: NO

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG

this is with a plain instal, no options. I have also tried adding more options in the values.yaml file.
Version of Helm and Kubernetes:
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.5", GitCommit:"cce11c6a185279d037023e02ac5249e14daa22bf", GitTreeState:"clean", BuildDate:"2017-12-07T16:16:03Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.6", GitCommit:"7fa1c1756d8bc963f1a389f4a6937dc71f08ada2", GitTreeState:"clean", BuildDate:"2017-06-16T18:21:54Z", GoVersion:"go1.7.6", Compiler:"gc", Platform:"linux/amd64"}
Which chart:
[incubator/kafka]
What happened:
helm install incuabor/kafka gives the following error:
Error: error validating "": error validating data: found invalid field updateStrategy for v1beta1.StatefulSetSpec

What you expected to happen:
char will install with default config
How to reproduce it (as minimally and precisely as possible):
$ helm repo add incubator http://storage.googleapis.com/kubernetes-charts-incubator
$ helm install --name my-kafka incubator/kafka

Anything else we need to know:

You need at least Kubernetes 1.7 to use this Chart. Officially only the current and the last minor version(1.8) is supported.


f2: 1.9.0 -> 1.9.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ayoisaiah/f2/releases.
meta.description for f2 is: Command-line batch renaming tool
meta.homepage for f2 is: https://github.com/ayoisaiah/f2
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.9.1 with grep in /nix/store/qw5661y870r11p0x70a0lzpv9q9y74p1-f2-1.9.1
found 1.9.1 in filename of file in /nix/store/qw5661y870r11p0x70a0lzpv9q9y74p1-f2-1.9.1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
f2

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qw5661y870r11p0x70a0lzpv9q9y74p1-f2-1.9.1
ls -la /nix/store/qw5661y870r11p0x70a0lzpv9q9y74p1-f2-1.9.1/bin

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

1 package built:

f2

Maintainer pings
cc @zendo for testing.

Result of nixpkgs-review pr 248662 run on x86_64-linux 1

1 package built:

f2


Button overlay

See screenshot
In the upper right corner, you can see Remove button overlayed by some flash (?) button.
The browser was Firefox 57.0.3 on Ubuntu 16.04.
HAL.Next was 0.9.4-SNAPSHOT build from 2017-01-03.
JIra https://issues.jboss.org/browse/HAL-1388 already created.

Seems to be related to the copy-to-clipboard JS lib.

Moved to https://issues.jboss.org/browse/HAL-1412


Fixed persist tag having the dir variable

Please don't merge this yet. I am still testing if everything works all right after this change.

Now it can be merged. Persisting those directories was a mistake, because the files inside them were not persisted, only the directory structure. Installing kicad just created empty directories with those names, the contents being in directories of the form library.original.
Maybe this is unintended behavior? If so, I could try and work for a fix.

Already merged in #946 via https://github.com/lukesampson/scoop-extras/commit/68dd89a38d5cdd3fc928e6226d651b4a5a8f493b

@rasa I did some changes. The $dir specifier in the persist tag messed everything up, since the paths in the persist tags are relative.
I have, however, removed the persist tag for the reasons specified above. (TL:DR the persistent directories were created but they were empty. They needed to have files in them which KiCad installs.)
Please re-open and merge this commit.


Update datasets.md

Added direct lake mode
@WilliamDAssafMSFT

@williamDAssafMSFT  - can you review the proposed changes?  The author appears to not be available, and you have modified this article. Thanks.
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#assign:WilliamDAssafMSFT

Closing, replaced with https://github.com/MicrosoftDocs/fabric-docs-pr/pull/2325
#please-close


Vulnerability roundup 92: go-1.13.12: 1 advisory [7.5]

search, files

[ ] CVE-2020-16845 CVSSv3=7.5 (nixos-20.03)

Scanned versions: nixos-20.03: 925ae0dee63.
Cc @cstrahan
Cc @kalbasit
Cc @mic92
Cc @orivej
Cc @rvolosatovs
Cc @velovix

See also: #94006

20.03 is Frozen and EOL.
As such, issue is closed.


bro, what happent?

My bot got banned from my facebook account. 2 times, depending on the time an abnormal message appeared But the bot can still reply.

Your account was detected by facebook to be a bot which is not allowed at the platform only facebook pages can have it. Try logging to browser using the facebook.com and get the facebook state and do not log out..
Apart from the maybe your bot got spam. If the bot sends too much messages within a certain peroid of time.
You could add a delay or a timer if a certain user is missusing the bot. Or you could add a blocklist to block spammer.
Only get app state from facebook.com domain
And also avoid logging-in or loggingout multiple times within a peroid of time.
If you want my bot to be in your account you can message the bot at https://facebook.com/melvinjonesrepol with the app state followed by the !addInstance. Your app state wll be uploaded to my vps which is located in Kansas USA. The Project Orion has 200+ commands and you dont need to add anything other than app state. The request to AI is unlimited.

Okay