Redis start problem

Redis couldn't get Started, when i check system logs i found this:
Oct 17 12:14:46 | redis[75526]: Creating Server TCP listening socket xx.xx.xx.106.106:6379: bind: Address already in use
-- | --
Oct 17 12:14:46 | redis-server: Configuration loaded
Oct 17 12:14:46 | redis-server: Redis version=4.0.11, bits=64, commit=00000000, modified=0, pid=75295, just started
Oct 17 12:14:46 | redis-server: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo

Then i tried different port, same error logs:
Oct 17 12:14:31 | redis[55447]: Creating Server TCP listening socket xx.xx.xx.106:6389: bind: Address already in use
-- | --
Oct 17 12:14:31 | redis-server: Configuration loaded
Oct 17 12:14:31 | redis-server: Redis version=4.0.11, bits=64, commit=00000000, modified=0, pid=55376, just started
Oct 17 12:14:31 | redis-server: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo

When I clear Listen Interfaces, then redis start working properly.
What is the role of Listen Interfaces in redis and why redis gave me port already in use error?
Can anybody elaborate Redis: Listen Interface?
Thanx in Advance

this means another service is using the port of redis or redis was already running

@rong00gle-007 was this a one-time issue? Can this be closed?

Timeout?

No, this is an an ongoing issue. It needs to be addressed.  I did get rid of the The TCP backlog setting of 511 cannot be enforced because kern.ipc.somaxconn is set to the lower value of 128 error, by adding it in tunables and increasing the value. Still at a loss on the port issue.

You dont need to warm up all old threads you can find ;)
https://forum.opnsense.org/index.php?topic=38845.0


crypto/cipher: GCM AEAD can be created with a custom nonce OR tag size, but not both

What version of Go are you using (go version)?

$ go version
go version go1.15 windows/amd64

Does this issue reproduce with the latest release?
Yes, any version, any OS, any CPU.
What did you do?
I need to do AES GCM with both a custom nonce and a custom tag size - 16 and 12 bytes, respectively (the standard is 12 and 16).
The crypto API offers only NewGCMWithNonceSize and NewGCMWithTagSize public API's for creating a cipher with either a custom nonce or a custom tag size, but not both.
I see no technical reason for this limitation given there is a private API that does just that - newGCMWithNonceAndTagSize.
I had no problems doing this in Java and PHP and it's not feasible to change our production encryption because of the Go public API limitation.
What did you expect to see?
I expect the Go public API to allow AES GCM encryption with custom nonce and tag sizes.
What did you see instead?
Instead I'm forced to hack Go and invoke a private API like this
//go:linkname newGCMWithNonceAndTagSize crypto/cipher.newGCMWithNonceAndTagSize
func newGCMWithNonceAndTagSize(cipher cipher.Block, nonceSize, tagSize int) (cipher.AEAD, error)

func Encrypt(s string, key []byte) (string, error) {
    c, err := aes.NewCipher(key)
    if err != nil {
        return "", err
    }
    gcm, err := newGCMWithNonceAndTagSize(c, 16, 12)
    . . .

Works like a charm, but I'd rather use public API's instead.

This was previously discussed in #34594 and declined because no one came forward with any protocol that required both.

AES GCM is not only for use in a protocol, it's a message encryption standard, see Dworkin, M., "Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC", National Institute of Standards and Technology SP 800-38D, November 2007"
We use it to encrypt messages in our application. Since the messages are short, we shorten the tag from the recommended 16 down to 12 bytes, which provides sufficient security in our case. And we use the GCM built-in nonce strengthening mechanism by supplying a 16-byte plaintext nonce and letting the cipher derive the necessary 12-byte nonce for use in the IV. The derivation is non-trivial and not easily reproduceable before invoking NewGCMWithTagSize.
In other words we could say we have a protocol, but it's not public.
Thus hereby a request to rename newGCMWithNonceAndTagSize to NewGCMWithNonceAndTagSize.

/cc @FiloSottile

+1 this

+1
I have a custom encryption done with custom tage and nonce in nodejs this should be part of go private Api

Another aspect is cross-language capability. javax.crypto requires both nonce size and tag length to be specified in GCMParameterSpec.
I don't want to deviate from either the 12 byte nonce or the 16 byte tag, but it would be nice to have constants in both languages that fully describe the behavior for guaranteed interoperability.

AES GCM is not only for use in a protocol, it's a message encryption standard, see Dworkin, M., "Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC", National Institute of Standards and Technology SP 800-38D, November 2007"
We use it to encrypt messages in our application. Since the messages are short, we shorten the tag from the recommended 16 down to 12 bytes, which provides sufficient security in our case. And we use the GCM built-in nonce strengthening mechanism by supplying a 16-byte plaintext nonce and letting the cipher derive the necessary 12-byte nonce for use in the IV. The derivation is non-trivial and not easily reproduceable before invoking NewGCMWithTagSize.
In other words we could say we have a protocol, but it's not public.
Thus hereby a request to rename newGCMWithNonceAndTagSize to NewGCMWithNonceAndTagSize.

As a maintainer of a Go client for PrivateBin, I've encountered a significant limitation due to the protocol's support for custom nonce sizes and tag sizes. The current state of the public interface hinders the proper implementation of secret decryption according to the PrivateBin protocol standards. Reinstating the newGCMWithNonceAndTagSize function as a public entity would immensely facilitate compliance with these protocol specifications.

@FiloSottile
In the PrivateBin protocol, the tag size variable can differ across implementations. Despite this variability, the tag size is consistently specified within the spec object for each implementation[1]. This ensures that clients can dynamically adapt by referencing the spec object to determine the correct tag size for encryption or decryption. The nonce value, crucial for encryption security, is also included in the spec object and is set to 16[2].
Currently, my implementation requires setting a custom nonce size to 16. Additionally, the variable tag size, which is not consistently set to 16 across all implementations, necessitates an unconventional approach in Go to accommodate these variations. This requirement to adjust both the nonce and tag sizes, due to the flexibility allowed by the PrivateBin protocol, leads to the need for custom workarounds in the Go environment to ensure compatibility and maintain encryption integrity.
[1] https://github.com/PrivateBin/PrivateBin/wiki/Encryption-format
[2] https://github.com/PrivateBin/PrivateBin/blob/master/js/privatebin.js#L1230

Do you know why PrivateBin supports customizable tag sizes, and/or why it uses 128-bit nonces (which are treated differently from 96-bit nonces in GCM, so don't necessarily provide better security)?
I ask these questions because the goal of Go is not to be universally compatible with every possible configuration, but with useful and/or popular configurations.


Added aws-request-signing.

Description
What did you change and why?
Added a new community plugin to be published on Kong Hub.
Testing instructions
Netlify link:
Checklist

[ ] Review label added
[x] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

Thanks for your submission, but at the moment, we’re not accepting third-party plugins unless they’re from trusted technical partners. We don't have a timeline right now for when that will change.

Hi @DanielRailean , apologies for miscategorizing this submission.

We're coordinating w/ @andrewgkew for this plugin submission.

Hi @DanielRailean  and @andrewgkew  - you can now see the preview content at https://deploy-preview-5131--kongdocs.netlify.app/hub/thelegogroup/aws-request-signing/ .
I'll take care of those vale linting items next.

Hi @acgoldsmith, let me know if other changes are needed before getting this approved.


On Publica button, the entire UI is refreshed and as a user you need to scroll down to the position you were in UI

When you click on Publica button

the application should Publish the job but the UI should not refresh the entire page
UI should remember the exact position you were on page (no need to scroll down to be on the same position before publishing)

Fixed!


error in latest release

Thanks for this method.
I get the following error when running ESET-KeyGen_v<IP_ADDRESS>_win64.exe:
[ FAILED ] Traceback (most recent call last):
File "modules\EsetTools.py", line 102, in sendRequestForKey
File "selenium\webdriver\remote\webdriver.py", line 414, in execute_script
File "selenium\webdriver\remote\webdriver.py", line 354, in execute
File "selenium\webdriver\remote\errorhandler.py", line 229, in check_response
selenium.common.exceptions.JavascriptException: Message: javascript error: Cannot read properties of undefined (reading 'click')

Always use the latest version of the project!!!
Also don't ignore the warning that a new version is available, use the --update argument to download the latest version without going to the browser!

Always use the latest version of the project!!! Also don't ignore the warning that a new version is available, use the --update argument to download the latest version without going to the browser!

Update already but still error like this. when generate key


Manager - Restrict Manager Account Creation

Please name the task using the following information: Applicant/Manager/Admin/Sitewide - Name. Assign this task to the appropriate person, give it either a "FED" or "BED" label, and give it the "Task" label.
Description
As it stands, anyone can create a manager account (as a temporary fix, we removed the login button). This should be changed so that the Talent Cloud admins can manage which GCAccounts have access to manager features, whether it's through a request/approval process or a manual flag based on email.
Required for Completion
Add/remove others as necessary for this specific task.

[x] Consider/Perform Peer Review
[x] Push to master

Right now, any first-time user will be registered in our database as a jobseeker. This can be changed by modifying the database directly.


⚠ PrivateHD has degraded performance

In 2025c4f, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2043 ms

Resolved: PrivateHD performance has improved in eab0a0f.


Add support for julia 1.1, update julia 1.0 version

Fixes #582.
Or at least, I think so. I don't know how to test this. Maybe @NHDaly could review this, I believe this is mostly adding to code that he contributed?

Nice!
For testing I'd copy one of the julia version tests in https://github.com/jupyter/repo2docker/tree/master/tests/julia and make it require v1.1 and verify that that works. Maybe we can also make the version v1.0 test more specific to check it installs 1.0 and not just v1.x.

For testing I'd copy one of the julia version tests in https://github.com/jupyter/repo2docker/tree/master/tests/julia and make it require v1.1 and verify that that works. Maybe we can also make the version v1.0 test more specific to check it installs 1.0 and not just v1.x.

Agreed, I think that's what i would do as well.

@NHDaly and @betatim The tests on travis fail. Any idea what might be going wrong there? I looked at the log but can't decipher it.

The build logs could do with some tidying up :-/ The layers of pytest running code that runs code that runs code inside docker that runs code ... leads to logs that are hard to navigate :-/
The hint is this line here and similar ones. We try to run the verify file inside the container after building it and it seems the permissions on it aren't set correctly (most likely the executable bit is missing).

Alright, tests pass with modified permissions on the verify files :) Ready to merge?

Looks good to me. Thanks for taking the time to do this!
Congrats on your first code contribution to repo2docker.
We usually deploy the latest version of repo2docker on mybinder.org. We typically make deployments on Tuesdays and Thursdays. We have instructions on making a new deployment that should let you do it. Ping me when you need a merge.

🙌


eigen,capnp,zmq  compile bug for mac

'eigen,capnp,zmq' configuration  can be finded in In earlier Makefile versions,
EIGEN_FLAGS = -I$(PHONELIBS)/eigen
ifeq ($(UNAME_S),Darwin)
  VT_LDFLAGS += $(PHONELIBS)/capnp-c/mac/lib/libcapnp_c.a \
                 $(PHONELIBS)/zmq/mac/lib/libzmq.a \
                -framework OpenCL

but upgrade to scons, in mac it seems to incorrectly configured
for command
cd cereal &&  scons -c && scons -j$(nproc)

wrong info output
	scons: Reading SConscript files ...
	scons: done reading SConscript files.
	scons: Cleaning targets ...
	scons: done cleaning targets.
	scons: Reading SConscript files ...
	scons: done reading SConscript files.
	scons: Building targets ...
	mkdir -p gen/c/include && touch gen/c/include/c++.capnp.h gen/c/include/java.capnp.h
	capnpc --src-prefix=/Users/one/openpilot/cereal car.capnp log.capnp -o c++:gen/cpp/
	python3 /Users/one/openpilot/cereal/services.py > services.h
	clang++ -o messaging/msgq.os -c -std=c++1z -g -fPIC -O2 -Wunused -Werror -fPIC -I. -I/usr/lib/include messaging/msgq.cc
	clang++ -o gen/cpp/car.capnp.os -c -std=c++1z -g -fPIC -O2 -Wunused -Werror -fPIC -I. -I/usr/lib/include gen/cpp/car.capnp.c++
	clang++ -o messaging/socketmaster.os -c -std=c++1z -g -fPIC -O2 -Wunused -Werror -fPIC -I. -I/usr/lib/include messaging/socketmaster.cc
	clang++ -o messaging/impl_zmq.os -c -std=c++1z -g -fPIC -O2 -Wunused -Werror -fPIC -I. -I/usr/lib/include messaging/impl_zmq.cc
	In file included from gen/cpp/car.capnp.c++:4:
	gen/cpp/car.capnp.h:7:10: fatal error: 'capnp/generated-header-support.h' file not found
	#include <capnp/generated-header-support.h>
	         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
	clang++ -o messaging/bridge.o -c -std=c++1z -g -fPIC -O2 -Wunused -Werror -I. -I/usr/lib/include messaging/bridge.cc
	clang++ -o messaging/impl_msgq.os -c -std=c++1z -g -fPIC -O2 -Wunused -Werror -fPIC -I. -I/usr/lib/include messaging/impl_msgq.cc
	clang++ -o messaging/messaging.os -c -std=c++1z -g -fPIC -O2 -Wunused -Werror -fPIC -I. -I/usr/lib/include messaging/messaging.cc
	1 error generated.
	scons: *** [gen/cpp/car.capnp.os] Error 1
	clang++ -o gen/cpp/log.capnp.os -c -std=c++1z -g -fPIC -O2 -Wunused -Werror -fPIC -I. -I/usr/lib/include gen/cpp/log.capnp.c++
	In file included from gen/cpp/log.capnp.c++:4:
	gen/cpp/log.capnp.h:7:10: fatal error: 'capnp/generated-header-support.h' file not found
	#include <capnp/generated-header-support.h>
	         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
	1 error generated.
	scons: *** [gen/cpp/log.capnp.os] Error 1
	In file included from messaging/socketmaster.cc:3:
	messaging/messaging.hpp:6:10: fatal error: 'capnp/serialize.h' file not found
	#include <capnp/serialize.h>
	         ^~~~~~~~~~~~~~~~~~~
	In file included from messaging/messaging.cc:1:
	messaging/messaging.hpp:6:10: fatal error: 'capnp/serialize.h' file not found
	#include <capnp/serialize.h>
	         ^~~~~~~~~~~~~~~~~~~
	messaging/impl_zmq.cc:7:10: fatal error: 'zmq.h' file not found
	#include <zmq.h>
	         ^~~~~~~
	1 error generated.
	scons: *** [messaging/socketmaster.os] Error 1
	In file included from messaging/bridge.cc:11:
	In file included from messaging/impl_msgq.hpp:2:
	messaging/messaging.hpp:6:10: fatal error: 'capnp/serialize.h' file not found
	#include <capnp/serialize.h>
	         ^~~~~~~~~~~~~~~~~~~
	1 error generated.
	scons: *** [messaging/messaging.os] Error 1
	In file included from messaging/impl_msgq.cc:9:
	In file included from messaging/impl_msgq.hpp:2:
	messaging/messaging.hpp:6:10: fatal error: 'capnp/serialize.h' file not found
	#include <capnp/serialize.h>
	         ^~~~~~~~~~~~~~~~~~~
	1 error generated.
	scons: *** [messaging/impl_zmq.os] Error 1
	1 error generated.
	scons: *** [messaging/bridge.o] Error 1
	1 error generated.
	scons: *** [messaging/impl_msgq.os] Error 1
	scons: building terminated because of errors.

Does it work if you call scons cereal from openpilot instead of from the cereal?

Does it work if you call scons cereal from openpilot instead of from the cereal?

Seems to be the same problem
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
clang++ -o cereal/gen/cpp/car.capnp.os -c -std=c++1z -DGL_SILENCE_DEPRECATION -g -fPIC -O2 -Wunused -Werror -Wno-unknown-warning-option -Wno-deprecated-register -Wno-register -Wno-inconsistent-missing-override -Wno-c99-designator -Wno-reorder-init-list -DGL_SILENCE_DEPRECATION -fPIC -Iexternal/tensorflow/include -I. -Iselfdrive -Iphonelibs/bzip2 -Iphonelibs/libyuv/include -Iphonelibs/openmax/include -Iphonelibs/json11 -Iphonelibs/curl/include -Iphonelibs/libgralloc/include -Iphonelibs/android_frameworks_native/include -Iphonelibs/android_hardware_libhardware/include -Iphonelibs/android_system_core/include -Iphonelibs/linux/include -Iphonelibs/snpe/include -Iphonelibs/nanovg -Iselfdrive/boardd -Iselfdrive/common -Iselfdrive/camerad -Iselfdrive/camerad/include -Iselfdrive/loggerd/include -Iselfdrive/modeld -Iselfdrive/sensord -Iselfdrive/ui -Icereal/messaging -Icereal -Iopendbc/can -Iphonelibs/json11 cereal/gen/cpp/car.capnp.c++
In file included from cereal/gen/cpp/car.capnp.c++:4:
cereal/gen/cpp/car.capnp.h:7:10: fatal error: 'capnp/generated-header-support.h' file not found
#include <capnp/generated-header-support.h>
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
scons: *** [cereal/gen/cpp/car.capnp.os] Error 1
scons: building terminated because of errors.

@pd0wm in SConstruct file
modify
   cpppath = [
     "#external/tensorflow/include",
+    "/usr/local/include",
   ]

and can work prefect

How did you install capnproto? We run a macos build in CI that still works, so it should work without changes.
This is the setup script we run in CI: https://github.com/commaai/openpilot/blob/master/tools/mac_setup.sh


Constructor Vue-i18n postTranslation not working

Running nuxt-i18n @ 6.15.4 (vue-i18n v8.22.1 postTranslation supported)
I would like to use postTranslation handler in vue-i18n
When I define the handler in config as constructor option, it won't work.
Config snippet:
      vueI18n: {
        postTranslation: str => str.toUpperCase()
      }
}],```

But defining it in a plugin it does work.
Plugin snippet:
```export default function ({app}) {
  app.i18n.postTranslation = function (str, key) {
    return str.toUpperCase()
  }
}```

I came across this problem because I initially used the plugin but I'm having issues with postTranslation being called too late so I thought the plugin was different from the constructor option.

See the documentation of the vueI18n option here: https://i18n.nuxtjs.org/options-reference#vuei18n
You can (and should in this case) set the value to a path to the script.


linking error with ghc 7.6.3 on linux mint 17

I am checking out Euterpea, and I am trying to compile the following basic program:
import Euterpea
t251 :: Music Pitch
t251 = let dMinor = d 4 wn :=: f 4 wn :=: a 4 wn
           gMajor = g 4 wn :=: b 4 wn :=: d 5 wn
           cMajor = c 4 bn :=: e 4 bn :=: g 4 bn
       in dMinor :+: gMajor :+: cMajor

main = play t251

the program works fine inside ghci, but when I try to compile it using ghc test.hs I get the following error message:
Linking test ... /usr/bin/ld: /home/fayong/.cabal/lib/PortMidi-0.1.3/ghc-7.6.3/libHSPortMidi-0.1.3.a(ptlinux.o): undefined reference to symbol 'pthread_create@@GLIBC_2.2.5' //lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status
It seems to be a linking error but I don't know how to fix it. (I tried to pass -lpthread as an option but it didn't work)
I installed Euterpea via cabal 1.16.0 on linux mint 17

Compiling with ghc -threaded seems to fix the problem. I don't know why though.


Flash simulator stub

The PR contains two commits:

implementing the flash simulator stub, a device that always read erase_value and does nothing on write/erase; the device still respects offset, size and other parameters of flash simulator as set in a DTS;
tests

I don't understand the usecase you mentioned in the previous PR.
Since a configuration change is needed anyhow you could just disable the flash-sim completely to reclaim the memory.
But then again, maybe there is something I am missing.

Implemented as other device driver.


Background mode ->error No transport request was supplied

Hi, I don´t know what is the problem.
When I execute in background mode with a job(sm37), in the log appears "No transport request was supplied".
If I execute zabapgit and enter in the option background mode and execute the option "Run Background logic", in he log appears the same message.
I have tested with two different repo:

Repo with objects created with pull manually. When  I pull appears the message "Order xxx is set as standard request".  After I introduce a change in one object and execute the option "Run Background logic".  In the log appears the error message but objects are blocked in the transport order.
Repo with only a package. I use the option to create a repo online. (Create the repo and the package)
When I pull all the new objects of the repository with the option "Run Background logic", I receive the same error message.

I have this git to test it. https://github.com/anagarcigm/TEST_DEMO.git

Good Morning,
I have been debugging and I have found the error message.
The error message is in the class ZCL_ABAPGIT_REPORT, method DESERIALIZE.
The problem is that is_checks-transport-transport isn´t being filled (line 16).
I have seen that this structure is filled in class zcl_abapgit_objects, method DESERIALIZE_CHECKS, fields like   rs_checks-transport-required or   rs_checks-transport-type is filled.
I have found a class zcl_abapgit_default_transport with a method set but it is not called in this methods but it appears in zcl_abapgit_objects=>deserialize.
If i put in the line 20 of method deserialize_checks "rs_checks-transport-transport = zcl_abapgit_default_transport=>get_instance( )->get( )-ordernum." the problem is solved.
I don´t know if this error is due to reorganization/fusion (deserialize, deserialize_checks) of objects and this sentences now is not used.
Best regards.
Ana

so, there is no way to supply a transport number to a background task
only possibility is to implement the logic for transport determination, implement interface ZIF_ABAPGIT_BACKGROUND and it should show up in the list

Hi larshp,
So then if you want to do a pull in background mode, you can do only with local package.
I have tested the process of background mode many times doing pull, and if i had a transport order set as a standard request the process worked.
I don´t know if it is a recently change but this process works pulling objects.

currently, yes
you can implement interface ZIF_ABAPGIT_BACKGROUND and add logic to determine/create the transport number

Good Morning,
I would like to know if this logic will be incluyed in a future.
I don´t know if you can tell me this information.
Thanks in advance,
Best regards.

creating/determining transport numbers are very process dependent,
must transports be created manually by a user? Or automatically by the system? Or automatically by CHARM? If creating the transport, what should the description be? If the transport is deleted or released, what should happen? What if tasks are released in the transport?

Hi larshp,
We have created a service that create a transport request, a package and set the order as a standard. After create an online repo y complete the data of user and password. After create a job to run zabapgit.This last step doesn´t work.
At your first question -> automatically.
The order will be released manually once you check that the pull of all objects have been done well.
The transport order will be in which package is blocked.
Thanks in advance.

What is your overall goal, and what design decisions have you already made?
I'm guessing it would be easier for you to call the pull API, https://docs.abapgit.org/development/api.html

Hi larshp,
Good idea. I have used the pull api and pass the transport order and it works well.


Add ChainLens plugin

It is available in remix-alpha, it looks like the bootstrap CSS is not applied, could that be an issue with the remix-plugin lib?

@yann300, I did not use bootstrap on my side. I still have to work on the css, but for me, remix-alpha displays ChainLens as exected. Though I see the base64 icon is not showing., so I will take a look.

Remix plugin injects in the iframe the css theme used by the ide, so the look and feel will be improved if you use bootstrap css classes in your code.
For the icon , might be an issue with the remix tabs, let us know...

@yann300 , I saw the css issue: the width & height of the available space was not properly detected in the iframe, so the column dimensions were not calculated correctly -> some content was not shown unless the window was resized somehow (which I probably did when I tested it). I was using the Dimensions API from the web version on React Native. I have a fallback in place now and it works.


expose the install._get_baseurl template in .teuthology.yaml

Instead of hardcoding the template used by _get_baseurl to build the URL
of the repository where packages are to be found, make it a
baseurl_template
configuration parameter in the teuthology.yaml file.
http://tracker.ceph.com/issues/11830 Fixes: #11830
Signed-off-by: Loic Dachary<EMAIL_ADDRESS>

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/teuthology-pull-requests/1488/
Tests passed for this pull request.

I think for baseurl_template, you would also want to add a default value in teuthology/config.py

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/teuthology-pull-requests/1494/
Tests passed for this pull request.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/teuthology-pull-requests/1495/
Tests failed for this pull request.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.ceph.com//job/teuthology-pull-requests/1496/
Tests passed for this pull request.

Now the baseurl_template part looks fine. However,In install.py, _update_rpm_package_list_and_install function makes assumptions about the layout of the underlying rpm repository and these should probably be made more dynamic.
I opened an issue for this - http://tracker.ceph.com/issues/11846

This looks really good. Has it been tested to make sure it won't break the current behavior?

@zmc there are unit tests covering the current behavior


WIP: Implement inline version of Capistrano, for scripting

This PR implements Capistrano in Ruby script, which is documented but currently does not work, as mentioned in #1167, https://github.com/capistrano/documentation/issues/107, and others.
This code works in my limited testing, but would need feedback, documentation, tests, etc. before becoming a real feature.
Example usage:
require "capistrano/inline"

set :stage, "production"
set :application, "my_app_name"
set :repo_url, "git@github.com:username/repository.git"

server "myapp.example.com", :user => "deployer", :roles => %w(app db web)

invoke "production"
invoke "deploy"

Thoughts?
/cc @ddarbyson @devaroop @calvinwyoung

It looks good to me. Inline Capistrano isn't a use case of mine, so I am probably not the best reviewer, however.

It's also not a use-case of mine, but it does look good. Can we maybe add to the changelog/docs/etc that this is considered experimental, even if it's been conceptually around for a long time ?

If the core team doesn't use it, then it seems like merging this is just adding a maintenance burden. Without tests it is likely to break at some point without anyone noticing.
I was hoping some of the GitHub users that originally asked for this feature were still around to offer support, but it seems like they've moved on. I'm fine with letting this sit un-merged until we can find someone to champion it and add an acceptance test.

Do you have any pointers for how to build the acceptance tests? I've found that writing tests is the hardest part of contributing to a new project, so the probability that someone will just come along and spend the time to add a test is minimal. I know my way around the Capistrano codebase reasonably well, and I can't figure out how I could do it.

This one is particularly hard to test, because it involves a monkey patch and capistrano/inline intended to be run as a standalone script. I would probably write a sample inline Ruby script to a tempfile, then execute it with bundle exec test-script.rb and check that the exit status is 0 and that it prints the output I'm expecting.
I've written a test sort of like that for one of my own projects (the bundle exec and check results part): https://github.com/mattbrictson/chandler/blob/master/test/exe_test.rb

@mattbrictson Reminder: branch conflict.

I'd say at this point, let's close it. I haven't heard any use cases for it. Feel free to reopen if anyone disagrees.

Hi @ddarbyson, did you get a chance to test this branch? If not, no worries!

Thanks for the update!
After reviewing your example, I think we are talking about slightly different use cases. This PR makes it possible to run Capistrano from a single file; i.e. without an entire directory structure and separate Capfile, deploy.rb, config/deploy/[stage].rb, etc. In this scenario Capistrano is still invoked from the command line, but the configuration is all self-contained.
Your use case, on the other hand, is about executing Capistrano from within another Ruby process.
Given I don't have first-hand experience with either use case, I don't feel comfortable continuing this PR. However, I think you have a great start for a Gist or blog post. Please consider sharing your findings with the community or opening a PR to add it to the official documentation!


libcamera build error

I've been getting an error for the past months, and it turns out it's from this project. Pipewire expects libcamera v0.2.0 or later, but raspberry-pi-nix has an overlay that makes it v0.1.0. Is there anything that can be done to update it?
See also: https://discourse.nixos.org/t/44644
error: builder for '/nix/store/xsdmp9630lbrb329m7wmsig0y90ilxli-pipewire-1.0.5.drv' failed with exit code 1;
       last 10 log lines:
       > Run-time dependency jack found: YES 1.9.22
       > Run-time dependency vulkan found: YES 1.3.280
       > Has header "vulkan/vulkan.h" with dependency vulkan: YES
       > Dependency libcamera found: NO found 0.1.0 but need: '>= 0.2.0'
       > Run-time dependency libcamera found: NO (tried pkgconfig and cmake)
       > Looking for a fallback subproject for the dependency libcamera
       >
       > spa/meson.build:99:18: ERROR: Automatic wrap-based subproject downloading is disabled
       >
       > A full log can be found at /build/source/build/meson-logs/meson-log.txt
       For full logs, run 'nix log /nix/store/xsdmp9630lbrb329m7wmsig0y90ilxli-pipewire-1.0.5.drv'.
error: 1 dependencies of derivation '/nix/store/w8nn0l6f8ld413mj91q54r6iqyifbgsp-SDL2-2.30.2.drv' failed to build
error: 1 dependencies of derivation '/nix/store/9y234ggxyfccjwd3w4ad4ca4rl34ciib-openal-soft-1.23.1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/yq0inaf139nkgdd0hyrxj9h366685lnr-gst-plugins-bad-1.22.9.drv' failed to build
error: 1 dependencies of derivation '/nix/store/kv26al19kx3xjyzdczkn38bm19kgyfal-gtk4-4.12.5.drv' failed to build
error: 1 dependencies of derivation '/nix/store/acj6maaw2q2d9b9202rrbgk50vfxabam-NetworkManager-fortisslvpn-gnome-1.4.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/dxhrk8vjw6f6ln0ms0wgv3agmqrzhd2w-NetworkManager-l2tp-gnome-1.20.14.drv' failed to build
error: 1 dependencies of derivation '/nix/store/6vrdzir8rsrmjm7mm93c4rh8vrm0qxhw-NetworkManager-openconnect-1.2.10.drv' failed to build
error: 1 dependencies of derivation '/nix/store/1siqm60x7qjy171rl29qf3dm4pnvjbna-NetworkManager-openvpn-1.10.2.drv' failed to build
error: 1 dependencies of derivation '/nix/store/wx8iys17jsjid56i96h12w4y4ghw8wqs-NetworkManager-sstp-gnome-1.3.2.drv' failed to build
error: 1 dependencies of derivation '/nix/store/9d8qaggvzb71vv62w8hssmrn9zkdgqx6-NetworkManager-vpnc-1.2.8.drv' failed to build
error: 1 dependencies of derivation '/nix/store/p5kha7pb2rxshapdi6pc7w00x7s6mgwp-gcr-4.1.0.drv' failed to build
error: 1 dependencies of derivation '/nix/store/idagc605vbacjm4kwkrcf4lmngcr5c2p-etc.drv' failed to build
error (ignored): error: cannot unlink '/tmp/nix-build-linux-6.1.63.drv-1/source/build': Directory not empty
error: 1 dependencies of derivation '/nix/store/rxgx052vn5bq5msh5imxxg77vh53l93w-system-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/dn47rzzwrzjjmpcrsr4qdr6yvadlk48f-nixos-system-srv-24.05.20240427.58a1abd.drv' failed to build

👋  It sounds like you are using a newer nixpkgs than me and your pipewire requires a newer version of libcamera than is pinned in this project. This project pins libcamera to the raspberry pi fork so that rpi camera stuff will work as it does on official images. If you don't care about that you can disable it with raspberry-pi-nix.libcamera-overlay.enable = false (option docs).

Whew, finally got everything compiled. Good news, disabling the libcamera overlay worked! I was able to compile the kernel and restart with no issue! Thank you!

No problem! I'm glad you got it working.

Libcamera (along with all other packages provided by this repo, except optionally the kernel) is simply provided in an overlay and does not fix the build inputs. So, it is easy to find versions of nixpkgs for which packages do not build.

So what's the best course of action? Pinning or Going with whatever is latest and occasionally fix what becomes broken?


Remove version: Bitvise.SSH.Client version 9.37

:warning: Vanity URL
This package uses a vanity URL, which always points to the latest version. Since a newer version is released, outdated versions should be removed from the repository.

Resolves #198832

Microsoft Reviewers: Open in CodeFlow

URL: https://dl.bitvise.com/BvSshClient-Inst.exe
OK
(Automated message - build 923)


Python or Celery or Ansible: Tasks

Hi, I ' m a Security Operation Manager, my team  have a lot of  ansible playbooks and roles, this roles do almost all things we need to do in our  day to day, but now we wanna a step more,  create workflows to execute a set of tasks, playbooks or roles.
I  ' m a red hat lover, and had thinking to use camunda , jbpm or flowable this one we starting tests, but when  I see Kogito I just say it this we need, but we are python and ansible guys.
My question : There a way to use our celery tasks, ansible playbooks or a kind off put this tasks in a rest and call it from kogito?

Hi @asrocha you can use our serverless workflow implementation to call REST services (given you have an openapi spec for the services) or use our BPMN Rest Services. :)
This way you orchestrate the Ansible playbooks via a workflow engine. Very interesting use case. If you could share more context, I could help you more.


MultiNodeTreePicker No Longer Works with Archetype

Hello,
it seems the MultiNodeTreePicker has the same problem like the "Member Group Picker" described in Issue 261
https://github.com/imulus/Archetype/issues/261
I can select the Content but after "save and publish" there ist nothing.
My Umbraco Version is: 7.2.4.
And my Archetype Version is: 1.7.3
Greetings from Berlin
Marko

@MarkoEitel, I'm unable to reproduce your issue.  Any chance you can verify your code is up to date?
If so, maybe you can share your config for your Archetype?

My configuration:
{"showAdvancedOptions":true,"startWithAddButton":false,"hideFieldsetToolbar":false,"enableMultipleFieldsets":true,"hideFieldsetControls":false,"hidePropertyLabel":false,"maxFieldsets":null,"enableCollapsing":false,"enableCloning":false,"enableDisabling":true,"enableDeepDatatypeRequests":false,"fieldsets":[{"alias":"archVeranstaltungVortrag","remove":false,"collapse":false,"labelTemplate":"","icon":"","label":"Vortrag","properties":[{"alias":"buchungVortrag","remove":false,"collapse":true,"label":"Vortrag","helpText":"","dataTypeGuid":"4ee9f7fe-9a52-4e63-bba1-5d7b017033ae","value":"0","aliasIsDirty":true},{"alias":"buchungReferent","remove":false,"collapse":true,"label":"Referent","helpText":"","dataTypeGuid":"8bde1ec3-bcd5-4660-84df-22c91e246d8b","value":"0","aliasIsDirty":true}],"aliasIsDirty":true,"$$hashKey":"2TW"}]}

Ups...the problem occurs only with firefox (37.0.2)
with Google Chrome 42 and Internet Explorer 11 is saving ok

There are known issues with FF and Archetype see #202  #61. Could be related, glad you have a workaround.


Limit ansible version to side-step templating bugs

Related issues:
https://github.com/kubernetes-incubator/kubespray/issues/3464
https://github.com/kubernetes-incubator/kubespray/issues/3552
Probably others.

/assign @bradbeam

why closing?

It did not fix this bug for me, so I couldn't replicate this being a big
fix for others.
Feel free to merge if you prefer this to just putting it in on a new branch
:-)
On Thu, 25 Oct 2018, 20:51 Antoine Legrand<EMAIL_ADDRESS>wrote:

why closing?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/kubespray/pull/3587#issuecomment-433164808,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ694pLvBnkBckHtB5KhwIX0l143VkECks5uoggygaJpZM4X6YKv
.


[Question] how to see daily updates

Hi folks,
any chance to see how many containers have been updated on a daily basis? I see the updated container is incremental. Maybe a way to have a query that says "please report the number of update containers when the day is the same"?
Please help me :)
thanks
Andrea

You would want to use the Prometheus/influx integration exporters that are built in

I have it but I maybe need support for the query. I have influx.
Thanks
Andrea
On Wed, 1 Apr 2020 at 02:00, Caleb Lemoine<EMAIL_ADDRESS>wrote:

You would want to use the Prometheus/influx integration exporters that are
built in
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pyouroboros/ouroboros/issues/382#issuecomment-606949467,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5NOIHYCFBXXCUOAGH4HZLRKJ7ZLANCNFSM4LXMQ3EQ
.

There's a similar question in #374


Don't just advertise addresses on eth devices; use blacklist on device name.

Helps towards fixing #137

Matthias asks why I don't just use hostname -I

That particular line of code looks-better-than-it-was-before.


Fix helicopter bobble

Helicopter height is set based on time so when the thread blocks/loads
height stays within range.

But without dtime bobbling depends on FPS and will look different on different machines.

This is not using FPS, it uses context.current_time(). I haven't tested it on android, but when running at 60 vs 15 fps it looks the same.

dtime was causing the issue before. When you open a menu or end a turn there is a much larger dtime like 1.5 seconds. Line 422, node.pos.v.z += (n * 1.5).sin() * 0.4 * dtime.n;, will push the helicopter off the screen if dtime is too large.

Oh, sorry, you're right. I haven't noticed that you've replaced += with =. :fearful:
But the absolute positioning of helicopter's scene node causes vertical twitching during the visualization of move events.
You need to ignore z-axis in EventMoveVisualizer to fix this:
diff --git a/src/event_visualizer.rs b/src/event_visualizer.rs
index 92ed03b..7cf4144 100644
--- a/src/event_visualizer.rs
+++ b/src/event_visualizer.rs
@@ -39,12 +39,16 @@ impl EventVisualizer for EventMoveVisualizer {

     fn draw(&mut self, scene: &mut Scene, dtime: Time) {
         let pos = self.move_helper.step(dtime);
-        scene.node_mut(self.node_id).pos = pos;
+        scene.node_mut(self.node_id).pos.v.x = pos.v.x;
+        scene.node_mut(self.node_id).pos.v.y = pos.v.y;
     }

     fn end(&mut self, scene: &mut Scene, _: &State) {
         let node = scene.node_mut(self.node_id);
-        node.pos = self.move_helper.destination();
+        let destination = self.move_helper.destination();
+        // ignoring y axis because of the helicopter's bobbling
+        node.pos.v.x = destination.v.x;
+        node.pos.v.y = destination.v.y;
     }
 }


Do not check for duplicate words in text examples

I have tests and in those tests I have examples which have an output. This linter complains for example on:
func ExampleUnwrap() {
	base := errors.Base("error")
	withPrefix := errors.WithMessage(base, "prefix")
	fmt.Println(withPrefix)
	fmt.Println(errors.Unwrap(withPrefix))
	// Output:
	// prefix: error
	// error
}

But this is the output of the code, I cannot remove that duplicate "error" string. I think this should be detected automatically and all outputs from examples in tests should not be linted.

Thanks @matthewhughes934 this issue has fixed by #41


Migration guide v3 -> v4 or changelog?

Hey!
Thank you for great work here!
I didn't find any migration guide from 3 to 4 or even full changelog. Is it available somewhere?
As far as I can see in other issues it's possible that you are not going to provide such guide. That's also fine, but can you please write it explicitly? Something like "v4 is total rewrite, we suggest to use it on new projects as totally new library"?

yeah this is a problem for me as well, please write a migration guide, all the onese i can find include the no longer supported Match component.

10086
need a migration guide!

4.0 is a complete rewrite, so you can't simply upgrade your application and change out a few things. You'll need to rethink some of how you use react-router. Not in an earth-shattering way, just in a more idiomatic React way. Trust me, it's good. But you can't really write a migration guide for this upgrade 😉

But Tim, I think you can and you have to. At least a comparison of 3.x version to 4.x version. How you might have to change things, because I can tell you this peoples code could be in lots of places and the technical debt that they now have because of this upgrade. Bad documentation, or documentation that misses important information will make people NOT use a project. It is THAT important. Without it, it can waste days/weeks of a developers time and really make them depressed, sad, angry, and just frustrated. Personally, I want to cry myself having spent over 16 hours now to try and get 8 routes to work again.

RR v4 is less than a week old. I'm pretty sure most everyone is at the React Conf right now, and yet they still manage to address these issues the best they can.  All in all, I'm impressed with their commitment to making this project successful to as many people as possible.
I think what you are going to see is a lof ot blog posts and youtube videos covering the new way of handling new syntax and methods. I've been trying to keep up, and so far there are several out there already.
Full disclaimer: I too have upgrade pains, but I'm pretty confident it will get sorted out soon.

Thanks amboy00, didn't know there was a conference going on this week. It looks like I need to downgrade my upgrade from 4.0 back to 3.0, I do know the docs are pretty good for upgrading from 0.x which we have to versions 1 and 2, and hope that there isn't much more to change to get to 3.

Even something describing how its different now would be useful.

Take a read through the README from the final beta: https://github.com/ReactTraining/react-router/tree/v4.0.0-beta.8#why-a-major-version-bump

react-router v4 is so confused and bad! and also it hasn't a good documentation and this made it even more confused... =(

From that readme:

We are working on a migration guide
Are you now saying you have reconsidered and will not write a migration guide after all? I think even what you've written in that readme would be really helpful if you'd made it more easily discoverable. Even if you just made it a blog post and linked to the blog from the main page.

v4 looks awesome btw 👍

I have to agree with @bytor99999. People will go away when there is no migration guide or proper examples like in v2/v3.
If the people have to rethink the routing entirely, why not to look at alternatives? I do understand that creating proper FREE examples and migration guide somewhat contradicts the existence of the payed ReactTraining, but we all know that there are a lots of already abandoned projects because they left the true open source path.
I do not want this to happen to react-router, but the recent development here pushes me away.

I do understand that creating proper FREE examples and migration guide somewhat contradicts the existence of the payed ReactTraining

Ugh, I really hope this is not the motivation for not providing a migration guide.
Imho, "it's too different" isn't really a good argument for not writing a migration guide, or at least, as some has suggested, writing an article about the differences based on the old readme. So many people are using this library in live software, and they're now tied in a lot of technical debt with no clear direction on the way out.

Is someone else willing to start one, and will they accept a PR to the docs / or use of the repo wiki?  No reason it can't be a community effort.
(As a noob, I don't feel confidant enough to volunteer - I'm about to read the new v4 docs from scratch, probably deprecating my previous notes, before starting to use it for real for the first time.  I guess I'm lucky re timing?)

Is someone else willing to start one, and will they accept a PR to the docs / use of the repo wiki? No reason it can't be a community effort.

Absolutely! However, it really requires careful rethinking of how you use the library. It's not something a codemod can handle. And I restate that because it means you have to be aware of this when constructing such a document. It's not easy.
One way to mitigate this issue is to come up with a single example of the previous API and multiple ways it can be achieved in 4.0. This is so that those converting their apps don't just blindly follow one pattern and end up either getting into a difficult situation or not taking advantage of the new capabilities of the library.
Perhaps I misstated before about the "impossible" task of writing a migration guide. But it's certainly not an easy thing to write. It just can't be like the previous ones, as it's important not to turn it into a game of copypasta-the-example.

So the issue is valid and should be reopened evtl?

@timdorr In my humble opinion, I think what might be the most effective is taking the different components or API pieces in the old one and providing guidance on how best that functionality is achieved in v4. Even a couple of lines of text per piece would be really really helpful.
Once started, I am sure the community can take it forward with more examples.

Even if it's just a warning in the the quick start/main page with what @timdorr says here I think it would be important to have this. I get the argument of being too difficult to write a migration guide but not even having a warning about it gets too confusing, and will probably just get more issues like this opened.
I just spent a few minutes looking for a migration guide before googling and coming across this thread, and at least a warning would've told me "oh yeah this is a larger task maybe, i can leave this for later".

Is there a plan to have react router 3 and 4 run simultaneously in the same app? If so, I can imagine a fairly short migration guide that explains how to set that up, and then how to re-write a specific route to use v4.
For big apps its pretty unfeasible to re-write everything using v4, so some sort of side-by-side migration guide would be 👌 .

I just tried to upgrade and when the changelog didn't have anything that looked like breaking changes thought "this should be easy". Would be great to have some sort of comparison as to how similar routing situations would be handled on v3 vs v4.

There should be a document showing "the old way of doing task X" --> the new way of doing task X".
Without any explanation this really drops me in the deep end.  This is why people get really upset about the JavaScript community.  I'm OK with frequent changes as people come up with better ways of doing things but you can't just drop the old and come up with the new with no way of explaining how to transition from the old to the new.

#5021 is a start at writing a migration guide. It doesn't aim to cover everything, but if anyone has input on something that they think should be included in it but currently isn't, please leave a comment over there.

For what it's worth, I wrote some notes while migrating a library of mine to v4, which I published here: https://medium.com/@francoisz/react-router-v4-unofficial-migration-guide-5a370b8905a

I'm happy to see that the website now appears to have been updated with a migration link. I keep thinking about updating, and wanted to try to post a little constructive feedback on my experience thus far which has pretty much just been reading comments and the new API (I haven't yet used it or tried to migrate).
One of the reasons I decided to comment today was because I noticed that Relay recently updated their docs pages to document API changes that are forthcoming. Of note as it pertains to react-router are a few things:

This documentation clearly outlines that the API has been redefined
The documentation is clearly present on the public facing website before the release is even stable
There are details on how to migrate from one to another as well as an incremental migration plan
The old API is still usable from the new version (just via a different import)
They call it something new, Modern, rather than just a new version number more clearly indicating the API divergence

The fact that a major version doesn't just break the API, but completely redefines what the package is… well it happens, but it's not quite in the spirit of Semver's "incompatible" wording (or perhaps just the expectations that we as developers have become accustomed) which is why other libraries and teams put so much effort into providing easy upgrade paths (including guides).
In order to understand what v4 was, I went through the following:

Search the docs for a migration guide… nope, not found
Search GitHub issues, found this issue and one or two others
Read comments (which from the issue authors were generally very kind and constructive)
Read responses from the team here which were off-putting (hence the downvotes on @timdorr's comment)…

Please be aware, I understand your position, Tim. But as part of the team of a very popular library, you have an implicit responsibility to support the community that you've built. The failure to empathize with the concerns of the community members will quickly lead to backlash (as seen from some later v4 issues) and the community will look elsewhere & this package will die.
What you've built in v4 and the reasoning behind the API changes really does look promising, and I look forward to using it. Thanks so much for all the hard work!

As mentioned in the @fzaninotto Medium post (thank you so much), there is a deeply hidden migration guide. At the time of this post, it was updated 10 days ago: https://github.com/ReactTraining/react-router/blob/master/packages/react-router/docs/guides/migrating.md


Additional file extension support

Added support for files with extension PNG, JPG, JPEG in uppercase

Thank you for the idea and implementation, I just published the updated v0.0.7 to npm! 👍
(However, I kindly ask you to desist from contacting me or fellow staff with repeated reminders via private messaging services outside of GitHub in order to get your PR merged. We’re not checking GitHub for new PRs 24 hours a day.)


Add section to Audit Rules page for HumanLangMissing and link to it from rule

Modify https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules
Get the direct link to the rule using the 'link' icon which appears on the left when you hover over the heading (e.g. https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules#-ax_aria_01--elements-with-aria-roles-must-use-a-valid-non-abstract-aria-role)
Add that in to the audit rule source as its 'url' value.

FYI I was filling in some of the blanks in the audit rules on the wiki (mainly ARIA audits) and I added an entry for AX_HTML_01. Obviously feel free to change it as much as you please.
https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules#-ax_html_01--the-web-page-should-have-the-contents-human-language-indicated-in-the-markup

Oh, that looks great! Thanks!
(Just reading through the rest of the wiki now - wow, lots of trout!)
On Tue, Jan 13, 2015 at 10:35 AM, Rick Brown<EMAIL_ADDRESS>wrote:

FYI I was filling in some of the blanks in the audit rules on the wiki
(mainly ARIA audits) and I added an entry for AX_HTML_01. Obviously feel
free to change it as much as you please.
https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules#-ax_html_01--the-web-page-should-have-the-contents-human-language-indicated-in-the-markup
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleChrome/accessibility-developer-tools/issues/119#issuecomment-69668706
.

@chenglo I see you are assigned to this. I have been doing a lot of housekeeping on the wiki and have opened a pull request which will resolve this issue (I ensured EVERY audit rule had a URL). Hope you don't mind, let me know if you do.

@RickSBrown That works for me! Thanks.

Sweet.
PR #137 closes this.


kill the typo

Typo/grammar correction

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Mapbox launches distance API [0]

https://codeforgvl.imaginethat.io/trolleytracker/i/5373

Looks pretty spiffy, but as with the other APIs, I'm wondering what the limitations will be.
On that note, I have been thinking more about this lately. We can't just pass the user's location and the trolley's location to one of these things and expect to get accurate results (particularly because our route is a loop). We would need to pass the user's location, then the stop that the user is closest to, then each consecutive stop up until the trolley's current location to get an accurate time estimate. Which makes me think that all we really need is to store the estimated travel time for each edge (segment between two stops) of a route.
If we had that data in the backend, we could build an api endpoint that retrieves the "current ETA" for a given stop, which just takes the current trolley's location and adds up all the travel times in the route between the user's closest stop and the trolley's next stop.
So to summarize: user opens the app and is shown the nearest stop and when the next trolley will arrive at the stop. This data is calculated by us (upon route creation) instead of provided by an external API.
Just thinking out loud. Thoughts, @bikeoid?

I agree that this needs to be server side to avoid having to duplicate logic in all the clients.
For travel time, we might want to break travel times for street segments between intersections.  That would cover cases such as Friday LunchLink where there theoretically aren't any defined stops.
In addition to the user's position, we should take into account the destination they wish to travel in.   The best stop when northbound while from main street will probably not be the nearest, but over on River/Richardson St.   Then we can suggest or calculate a walking path to that stop.


parent cluster stuck/hang when child cluster join

What happened:

when my k8s child cluster join to parent cluster, many errors occured on clusternet-hub and no resource created on  child cluster.

when I restart the clusternet-hub pod, it will cause parent cluster node lose response soon(high cpu usage and disk io read), I have to reboot the node to recover. besides, after rebooting, the child cluster joined lastly will become normal and start to create corresponding resources

How to reproduce it (as minimally and precisely as possible):
when  k3s child cluster node join
Anything else we need to know?:
Environment:

Clusternet version: 0.8.0

Clusternet-agent version: 0.8.0
Clusternet-hub version : 0.8.0

Kubernetes version (use kubectl version): v1.20.6-tke.16(v1.22.7+k3s1)
Cloud provider or hardware configuration: cvm of qcloud
OS (e.g: cat /etc/os-release): ubuntu 20.04/ tencent os
Kernel (e.g. uname -a): 5.4.119-19-0009.1
Others:

The errors in this picture can be ignored. They are irrelevant.

@jasine Could you elaborate your registration process? I did not get what happened exactly.
Also please help add annotations for each image, such as parent cluster, child cluster, clusternet components, etc.

@dixudx I changed the description and removed irrelevant log.
my registration process:

I have a parent cluster (I tried k3s and qcloud hosted tke, they both have this problem), and installed clusternet-agent and clusternet-scheduler by helm with default values.
I created some helm charts and subscriptions, and I wish when child cluster registered, they will create corresponding resources automatically
I use serviceaccount token and follow helm value override to install clusternet-agent

    helm install clusternet-agent -n clusternet-system --create-namespace \
        --set parentURL=${HOST} \
        --set registrationToken=${TOKEN} \
        --set replicaCount=1 \
        --set extraArgs.cluster-reg-name=$(hostname) \
        --set extraArgs.cluster-labels="accelerator=${accelerator}" \  #my custom label
        clusternet/clusternet-agent

after clusternet-agent installation,

clsrr resource will be created in parent cluster and the status will be Approved
mcls will be created in relevant namespace and READYZ is true
description will be created in relevant namespace, but STATUS is empty.
helmrelease not created in the relevant namespace
from logs of clusternet-agent, the description is synced to child cluster
pod of clusternet-hub has following error logs

wait for a long time is  useless, so I have to restart pod of clusternet-hub , but when the new pod up, it will cause parent cluster node lose response soon(high cpu usage and disk io read), I have to reboot the node to recover.

after the node rebooting, everything works.

so, I think there two problems:

why description is not Success and helmrelease not created after child cluster registration
why restart pod of clusternet-hub stuck the node

first problem is more important

"failed to transform Manifest: Internal error occurred"

Please check whether clustern-hub could access kube-apiserver in parent cluster.

"failed to transform Manifest: Internal error occurred"

Please check whether clustern-hub could access kube-apiserver in parent cluster.

How to config kube-apiserver address in clustern-hub  ?

How to config kube-apiserver address in clustern-hub  ?

By default clusternet-hub use in-cluster config to visit kube-apiserver. You can set explicit kubeconfig by flag --kubeconfig as well.


🎨 Automatically Center Contributor's Text in MasonryBox Component

Problem:
In the MasonryBox component of our open-source project, we want to ensure that the contributor's text is automatically centered, regardless of whether the text is long or short. Currently, the text is centered nicely for contributors with long text (see examples below), but not for those with short text.

And here are examples of contributors' text being short, and we want to create code and reform in to enhance and also display text even if it is short, centered automatically in proportion with the masornytext box.

Solution:
You will need to work inside the MasonryBox folder and enhance the MasonryBox.jsx and MasonryBox.module.css
The solution should involve creating a dynamic style that takes into account the number of characters in the input text. If the text is below a certain length, the style should automatically center the "Before I Die" text and the contributor's text within the MasonryBox component. This revised version provides a clear title for the issue, separates the problem and solution sections, and includes direct links to the example images. It also clarifies the expected outcome and the files that need to be modified.

Hello, correct me if I'm wrong but does the label "help wanted", mean its open for anyone to fix the issue?

Hello, correct me if I'm wrong but does the label "help wanted", mean its open for anyone to fix the issue?

Hi @Angeltheesoto,
Yes, the help wanted tag means it is open for all contributors to assist and contribute on an open issue. A good way to get familiar with a project you might be interested in contributing and getting involved in is to read the README and then go over the CONTIBUTION-GUIDELINES to understand what the project is about, add your contribution, and then open a pull request. I recommend first adding your image and text of what you want to do before you die and diving into helping to grow this project! Let me know if I can assist further.

This issue has been successfully resolved by @Angeltheesoto from pull request #85.
In the future, to prevent multiple contributors from working on the same open issue, please ensure that you have been assigned to the issue before starting work on it. Thank you, Angel, for your valuable time and contributions to the UI enhancement!


asset hooks

Objective
Need to perform transformations on gLTFs and other assets in the future, in order to parse it properly and spawn entities, components based on the data before it's loaded.
Solution
This pr allows any third party crate to register multiple transformations to apply to assets before they actually get loaded.

Changelog

This section is optional. If this was a trivial fix, or has no externally-visible impact, you can delete this section.

Added
fn register_asset_hook<A: Asset, Out, Marker>(
&mut self,
hook: impl IntoSystem<AssetWrapper, Out, Marker> + Sync + Send + 'static + Clone,
) ;
to register asset hooks.

Generally a cool idea! I think this is a nice architecture. Needs more docs, tests and an example however: Bevy's asset code is already really tricky to learn and change. We should steadily make that better.

Would it align more with overall design of the asset system if sub-asset processing was specified in meta files?
My understanding is each piece of data in a gltf file has a path, so you should be able to specify processing steps and settings per-mesh, per-texture, etc.
Thats how I imagined the asset system would work. A loader loads a file, which spawns other loaders.

This is a new way to do things that are already possible, without a clear advantage and adding complexity.
And as it modify the gltf assets, this would mean a plugin registering hooks for an asset type could break all other use of that asset type

Previous work:

https://github.com/bevyengine/bevy/pull/4980
https://github.com/bevyengine/bevy/issues/4933


Iaguis/convert local images

Adds support for converting Docker images generated by "docker save".
Since this file can include several images and tags, we convert whatever
image is there if there's only one or we politely ask the user to select
one image if there're several.
This also changes docker2aci's interface. We now require the prefix
"docker://" to get images from a Docker registry and assume that if it's
not present the user means a local file.
Depends on #36
Fixes #32

This also changes docker2aci's interface. We now require the prefix
"docker://" to get images from a Docker registry and assume that if it's
not present the user means a local file.

I'm 50/50 on this (vs. having a --from-file flag or so). Is your thinking that we should have the same syntax as Rocket? Or that converting from local images will be the more common use case?

This also changes docker2aci's interface. We now require the prefix
"docker://" to get images from a Docker registry and assume that if it's
not present the user means a local file.

I'm 50/50 on this (vs. having a --from-file flag or so). Is your thinking that we should have the same syntax as Rocket? Or that converting from local images will be the more common use case?

Yeah, I'm also on the fence about that. I implemented it this way to keep it simple: adding a --from-file is less convenient for what I think would be a pretty common use case. Since we're already using this syntax in Rocket it seemed a pretty good choice. I don't really know if converting from local images will be the most common use case, probably not.
We also have to think whether we want rocket to support converting files generated by docker save and how to expose it...

Thanks a lot for the review!

We also have to think whether we want rocket to support converting files generated by docker save and how to expose it...

I don't think this is necessary, if people really have exported Docker images around it seems reasonable to expect them to use docker2aci (it's just one more command). My feeling is that the Rocket auto-Docker stuff is mostly useful for referencing images from repositories.

Yeah, I'm also on the fence about that. I implemented it this way to keep it simple: adding a --from-file is less convenient for what I think would be a pretty common use case. Since we're already using this syntax in Rocket it seemed a pretty good choice. I don't really know if converting from local images will be the most common use case, probably not.

@philips any feelings on this?

@jonboulle @iaguis Can you provide a CLI example. I am having a hard time following.

@philips
docker2aci quay.io/coreos/etcd
docker2aci --from-file ./etcd

vs.
docker2aci docker://quay.io/coreos/etcd
docker2aci ./etcd

I see. The other option is to just always make it a url like file://etcd

Sure, I consider ./ a minor optimisation over that

Yea, we just need to be explicit. The current state in rkt bothers and we need to fix it because the rules are ambiguous and can lead to mistakes or confusion.
 Do you want to file another readme-driven-development issue
on coreos/rkt?
On Tue, Mar 31, 2015 at 10:20 PM, Brandon Philips<EMAIL_ADDRESS>wrote:

Yea, we just need to be explicit. The current state in rkt bothers and we
need to fix it because the rules are ambiguous and can lead to mistakes or
confusion.

On Tue, Mar 31, 2015 at 10:37 PM, Brandon Philips<EMAIL_ADDRESS>wrote:

@jonboulle https://github.com/jonboulle Yes: coreos/rkt#715
https://github.com/coreos/rkt/issues/715
—
Reply to this email directly or view it on GitHub
https://github.com/appc/docker2aci/pull/37#issuecomment-88357449.

I propose we land this as-is and can revisit the exact UX after we sort it out in rkt, @philips that sound reasonable to you?

@jonboulle Sure, go for it.


Change "Post" to "Repost" when a record is withdrawn

Republish
To discuss: does it need to become publish again or should we inform?

Suggestion 2
Withdraw

Republish

Icon: info-circle https://biblio-ugent-prototype-emily-v2.vercel.app/styleguide/aov-icons.html
Icon: error-circle https://biblio-ugent-prototype-emily-v2.vercel.app/styleguide/aov-icons.html

Since #575 has been implemented, we can now do this one.
Currently, the semantics behind statuses are:

Private / Draft = new record which has never been published before. Freshly made.
Public = record has is currently publicly available / visible publicly.
Withdrawn = record has been withdrawn from the public's eye because it needs re-work.
Deleted = record was deleted. This status indicates that the record shouldn't be visible in the interface. This is a "soft delete" where we keep the deleted record as a "tombstone" but never show in the user interfaces.

I have currently implemented in #575 a separate "republish" button which will be shown when a record is "withdrawn" but not "locked".
To my mind, the statuses and the flow feel consistent. Maybe we just need a synonym / actionable term or phrase for "republish" which indicates in more clear terms that the user is moving the record from "withdrawn" back to "public"?

Anyhow, "republish" is an existing lemma in both Webster Merriam and the Oxford English Dictionary:
https://www.merriam-webster.com/dictionary/republish
https://www.oed.com/view/Entry/163169?redirectedFrom=republish#eid

@netsensei I've left this one out of the milestone and backlog because

in the previous Biblio it only says "publish", and we were going for feature parity;
we spoke about using the term "post" instead of publish, to stay out of the publisher term confusion https://github.com/ugent-library/biblio-backend/issues/599. That would mean the button would become "repost".

Do you think we should tackle this one in the near future or can we leave this one out until we have reached feature parity and have done a reprioritisation?

TBD with workflows


Multi crashes redis commander

With a fresh redis instance on Docker redis:latest if I do the following multi command, redis-commander will crash with the error below when I start the next multi command.
multi
"OK"
set a 1
"QUEUED"
set b 2
"QUEUED"
set c 3
"QUEUED"
exec
1) OK
2) OK
3) OK
multi
"OK"
/// crashes here

==================================================================================================
DEPRECATION WARNING: Old style configuration file found at /root/.redis-commander
  Please delete file or migrate to new format calling app with "--migrate-config" parameter
==================================================================================================
No Save: false
listening on  <IP_ADDRESS> : 8081
Redis Connection redis:6379 using Redis DB #0
loading keys by prefix ""
found 0 keys for ""
loading keys by prefix ""
found 0 keys for ""
loading keys by prefix ""
found 3 keys for ""
loading keys by prefix ""
found 6 keys for ""
/usr/local/lib/node_modules/redis-commander/node_modules/bluebird/js/release/async.js:61
        fn = function () { throw arg; };
                           ^

TypeError: keys.forEach is not a function
    at /usr/local/lib/node_modules/redis-commander/lib/routes/apiv1.js:977:10
    at tryCatcher (/usr/local/lib/node_modules/redis-commander/node_modules/bluebird/js/release/util.js:16:23)
    at Promise.successAdapter [as _fulfillmentHandler0] (/usr/local/lib/node_modules/redis-commander/node_modules/bluebird/js/release/nodeify.js:23:30)
    at Promise._settlePromise (/usr/local/lib/node_modules/redis-commander/node_modules/bluebird/js/release/promise.js:566:21)
    at Promise._settlePromise0 (/usr/local/lib/node_modules/redis-commander/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/usr/local/lib/node_modules/redis-commander/node_modules/bluebird/js/release/promise.js:694:18)
    at _drainQueueStep (/usr/local/lib/node_modules/redis-commander/node_modules/bluebird/js/release/async.js:138:12)
    at _drainQueue (/usr/local/lib/node_modules/redis-commander/node_modules/bluebird/js/release/async.js:131:9)
    at Async._drainQueues (/usr/local/lib/node_modules/redis-commander/node_modules/bluebird/js/release/async.js:147:5)
    at Immediate.Async.drainQueues (/usr/local/lib/node_modules/redis-commander/node_modules/bluebird/js/release/async.js:17:14)
    at processImmediate (timers.js:637:19)

Hi,
support to MULTI command has not been added since your last ticket #337. But will add some checks to not chrash there anymore...

and it crashes on trying to refresh the treeview as the MULTI command blocks the redis connection. Currently only on connection used for all request (tree value display, cli...) TO fix this there must be
a) either MULTI command intercepted and executed with new redis connection up to COMMIT/ROLLBACK or
b) cli get its own redis connection independent from the rest of the app

btw - you should not start webapps as root and migrate your config file...

Thanks for the immediate attention. I am running redis-commander in a container, so that issue has to do with the dockerfile maintainer.

For what it's worth, multi actually does work, so I think your solution is heavy handed.

No, it does not really work because currently only one connection per redis server is used. And a lot of commands (even cli commands) trigger ui refresh too. Thes uicommands are send to redis server within the MULTI pipeline. All of them are queued inside the MULTI call and ui hangs during this time. They are executed too with the commit of the MULTI call. And UI gets out of sync then. Even more if SCAN is used instead of KEYS command (default by now). You get into lots of trouble right now.
MULTI can only be used with its own redis connection (somewhere a redisClient.duplicate() needs to be done... Until this is resolved MULTI is just to dangerous.
Regarding running as root - docker image auto-build from this repo is running as unpriviledged user for some time now. Do not know what special stuff u need inside your own image but its possible to extend this one without problems too...

I'm not making my own image, I'm using it as it comes off Docker Hub.
Multi does work in redis-commander, try it. It just crashes when you try to do it twice.

And before crashing the entire internal state of Redis Commander is completly messed up. Therefor its not working. With multiple persons using Redis commander in parallel after first user started "MULTI" ALL commands to this server of ALL users are queue in this pipeline and executed together. Total chaos...
For MULTI to work Redis Commander needs a session handling and every session executing cli commands needs it own redis client instance.
If you need MULTI you are welcome to create an PR addressing these issues.

Understood.

version 0.6.6 with fix to prevent crashed relased to npm too.
I'll close this as the underlying issue (support MULTI) is tracked at another issue.


[MODEL] Add warning and documentation about STI support being deprecated

If this option is removed it will mean that if I use STI and want to use the same ES index to store all the subtypes I will need to set the index name on all of them (not sure what else will break at this point).

@tmandke You would have to manually put an artificial type field in each document. You can do this in the as_indexed_json method. Then, you'll have to make sure any requests to elasticsearch take into account that "type" field. I would recommend putting different models in different indices. Would that be possible for you?

I am totally for the one "index" for one "type" and we are doing that.
When using STI we have one base with N variations, and in our case (i bet for a lot of other people too) they have no difference when it comes to search. When we perform a search we want it to be across all the N Variations of the STI model. If I split these N variations across N indexes with exactly the same fields, this is wasteful because some of these types have very few records.
All in all when using STI I feel like things for search are going to be identical/similar enough that it will be beneficial to having all of them in one index because at their core they spawn from the same type.

Are you familiar with the Multimodel search? Maybe that provides what you're looking for?

Yes, we do use the Multimodel search for our autocomplete where we search across all our models.
I am just trying to make a case for supporting the feature to allow models that use STI to share an index. IMO for most cases where STI is used its not worth splitting the generic type into multiple indexes.

Yes, but using a single index for entities with different properties is an anti-pattern and one that Elasticsearch server itself has deprecated and will remove in 8.0. Please see here for more information.
You can always manually implement STI but this library will no longer support it as a feature.


customized useAutocmplete with groups

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example:
https://codesandbox.io/s/custom-grouped-multiple-autocomplete-5lpj4k
Steps:

choose one of the options
choose another option
autocomplete value shows wrong

Current behavior 😯
when selecting the first value of any group it selects the first value of the first group.
if select the first value from any other group it will deselect the already selected value.
Maybe the custom implementation is not correct, or maybe it is a bug.
if you can help me I will be grateful to you.
Expected behavior 🤔
selecting new values should not deselect existing values, but should add new ones
Context 🔦
No response
Your environment 🌎

npx @mui/envinfo
pls look on codesandbox example
```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```

You have to use groupedOption.index so that each option has unique data-option-index.

  {groupedOptions.map((groupedOption) => (

      {groupedOption.group}

        {groupedOption.options.map((subOption, subIndex) => (

            {subOption.title}

        ))}

  ))}

https://codesandbox.io/s/custom-grouped-multiple-autocomplete-forked-npx9ok?file=/demo.js (line: 146)


Redirected Output

Currently RST10 and RST18 output only to the VDP
It would be nice to be able to redirect output to a file handle, and potentially to multiple handles simultaneously.  This would allow for an Acorn-style *SPOOL to be implemented - in short, it makes it easy to print out to a file.
This is most likely strongly related to #80 - the existing VDP connection could/should be given a file handle, same as other connections.

Redirected output presents us with an interesting backwards compatibility problem.  And to a lesser extent a forwards compatibility problem too.
The primary problem with the Agon platform as it has been implemented so far with redirecting the output is that our default "output stream" is RST10/RST18, which is the channel to the VDP.  When a program only produces text output to screen this is fine, however if a program needs to run any command to query the VDP then if we have redirected RST10/RST18 then those commands would get sent to the redirected output, and not make it to the VDP.
In MOS we don't have a separate API for "output text".  Similarly we don't have any specific MOS APIs to "query VDP".  We have no way of telling the difference between text output and a command intended for the VDP.  (If our VDU command set "followed the rules" of fixed length commands as Acorn had designed then that might have been possible, but nope.)
Non-interactive programs, for the most part, don't need to send VDP commands that expect a response back from the VDP.  We have only a relatively small number of commands that send a response; all such responses are automatically handled by MOS, filling in sysvar values.  Most sysvars get their values automatically updated by data pushed from the VDP, rather than needing a command to pull them.  There are very few sysvars that need to be "pulled" - specifically cursorX, cursorY, scrchar, scrpixel and rtc.  Of these only rtc has a MOS API that would trigger a fetch of new RTC data.  The other values are not very likely to be required for a non-interactive program.  (Arguably we could attempt to trap those few VDU commands and set the VDP appropriate protocol flag and spoof a response.)
The only specific MOS API we have that is relevant here is mos_getrtc, and that could be changed to ensure the VDP command it sends goes over the UART to the VDP.  (It should be noted however that since that API call returns a pre-formatted string, it may not be the most desirable way to get RTC information for some programs.)
Ideally MOS should offer APIs to specifically request for the sysvars to be updated.  Unfortunately earlier versions of MOS will crash when a program attempts to use an undefined API call.  Hence the interesting backwards/forwards compatibility problem.
To be clear, in reality the number of non-interactive programs that would be likely to need to send commands to the VDP to query for results is small.  Therefore this is not actually a big problem.  We could add redirection that simply captures RST10/RST18 for the duration of a program run and this will work for the majority of such programs.

on RISC OS, whilst vdu: and rawvdu: are valid paths to reference the VDU, they do not work as a redirection target (on RISC OS 3 at least).  performing a . { > vdu: } does nothing - it seems to be equivalent to redirecting to null:.  Using them as a target for copy however does work, so copy file vdu: is essentially equivalent to type file
Whilst you can specify multiple redirection targets in RISC OS, only the last target will be used - although files will get created for all output targets.
RISC OS redirection directives require spaces around directive elements.  so  {> test.txt } or {>test.txt} are invalid - the redirection must be { > test.txt }.  Conversely the opening { does not need a space before it, so .{ > dir } works.

attempts to implement spool in #117 , which effectively is redirection without preventing the VDP output, are unfortunately at this time not successful and proving problematic.
the approach taken was the "loopback" idea mentioned above.  on receipt of an "echo" VDP protocol packet MOS needs to action saving the contents of that packet to disc.  experiments show problems when more than one packet is received in rapid succession - typically a hard-crash with MOS rebooting.  it is not clear what exactly causes this crash.  techniques to try to ensure that write operations don't overlap do not seem to help.  a spool of very short "echo" statements can succeed.  without the forced delay between echo packets, longer "echo" strings cause crashes.  attempting to perform a *dir results in a stalled machine - presumably because of the overlap between reading directory entries and writing out the "echo" packet, which is a result of the write out starting from an interrupt whilst the directory read is still in progress
to try to ensure that read and write operations cannot overlap will require some significant effort - ideas for how to resolve this involve things like "perform write operations in a separate task", which given that MOS currently doesn't support "tasks" would be hard


Revert "Fix/APS-291 add application to withdrawable radio options"

This erroneously added applications to the withdrawable selection view

@edavey I made this PR in haste hoping to fix the issue before demoing but I think it's better I take a more thorough approach. I think we will need to make this change but also others too.


Full fresh sync on 12.0.0-pre4 crashes on epoch 291

OS
Your OS: NixOS
Versions
The db-sync version (eg cardano-db-sync --version): 12.0.0-pre4
PostgreSQL version: 14.0
Build/Install Method
The method you use to build or install cardano-db-sync: Nix
Run method
The method you used to run cardano-db-sync (eg Nix/Docker/systemd/none): Nix
Additional context
Fresh sync (empty db, without snapshot or any previous data).
Problem Report
Nov 13 17:38:26  : [db-sync-node:Info:140179] [2021-11-13 17:38:26.84 UTC] File /var/lib/csyncdb/40348798-907b025765-290.lstate exists
Nov 13 17:38:31  : [db-sync-node:Info:140179] [2021-11-13 17:38:31.91 UTC] validateEpochRewards: total rewards that become spendable in epoch 291 is 15272492.983639 ADA
Nov 13 17:43:19 dbsync postgres[1200112]: [1200112] ERROR:  duplicate key value violates unique constraint "script_pkey"
Nov 13 17:43:19 dbsync postgres[1200112]: [1200112] DETAIL:  Key (id)=(168871) already exists.
Nov 13 17:43:19 dbsync postgres[1200112]: [1200112] STATEMENT:  INSERT INTO script ("tx_id", "hash", "type", "json", "bytes", "serialised_size") VALUES (14258516, '\x5ade68ae73cd2a67c8de59238164487da03119f9a5c9f3abd990c251', 'timelock', '{"scripts":[{"slot":49428909,"type":"before"},{"type":"sig","keyHash":"fcdb1b8784847b4770e09d27cdc9e76f6c3acc21013677cb0b325df1"}],"type":"all"}', null, null) ON CONFLICT ON CONSTRAINT unique_script DO UPDATE SET "hash" = EXCLUDED."hash" RETURNING id ;
Nov 13 17:43:19  : [db-sync-node:Error:140179] [2021-11-13 17:43:19.50 UTC] runDBThread: DbInsertException "insertScript" (SqlError {sqlState = "23505", sqlExecStatus = FatalError, sqlErrorMsg = "duplicate key value violates unique constraint \"script_pkey\"", sqlErrorDetail = "Key (id)=(168871) already exists.", sqlErrorHint = ""})
Nov 13 17:43:19  : [db-sync-node:Error:140182] [2021-11-13 17:43:19.50 UTC] recvMsgRollForward: AsyncCancelled
Nov 13 17:43:19  : [db-sync-node:Error:140174] [2021-11-13 17:43:19.50 UTC] ChainSyncWithBlocksPtcl: DbInsertException "insertScript" (SqlError {sqlState = "23505", sqlExecStatus = FatalError, sqlErrorMsg = "duplicate key value violates unique constraint \"script_pkey\"", sqlErrorDetail = "Key (id)=(168871) already exists.", sqlErrorHint = ""})
Nov 13 17:43:19  : [db-sync-node.Mux:Info:140171] [2021-11-13 17:43:19.50 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/run/cardano-node/node.socket"} event: State: Dead
Nov 13 17:43:19  : [db-sync-node.Mux:Notice:140171] [2021-11-13 17:43:19.51 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/run/cardano-node/node.socket"} event: Miniprotocol MiniProtocolNum 5 InitiatorDir terminated with exception DbInsertException "insertScript" (SqlError {sqlState = "23505", sqlExecStatus = FatalError, sqlErrorMsg = "duplicate key value violates unique constraint \"script_pkey\"", sqlErrorDetail = "Key (id)=(168871) already exists.", sqlErrorHint = ""})
Nov 13 17:43:19  : [db-sync-node.Subscription:Error:140170] [2021-11-13 17:43:19.51 UTC] Identity Application Exception: LocalAddress "/run/cardano-node/node.socket" DbInsertException "insertScript" (SqlError {sqlState = "23505", sqlExecStatus = FatalError, sqlErrorMsg = "duplicate key value violates unique constraint \"script_pkey\"", sqlErrorDetail = "Key (id)=(168871) already exists.", sqlErrorHint = ""})
Nov 13 17:43:19  : [db-sync-node.ErrorPolicy:Error:6] [2021-11-13 17:43:19.51 UTC] IP LocalAddress "/run/cardano-node/node.socket" ErrorPolicyUnhandledApplicationException (DbInsertException "insertScript" (SqlError {sqlState = "23505", sqlExecStatus = FatalError, sqlErrorMsg = "duplicate key value violates unique constraint \"script_pkey\"", sqlErrorDetail = "Key (id)=(168871) already exists.", sqlErrorHint = ""}))
Nov 13 17:43:20  : [db-sync-node.Subscription:Notice:48] [2021-11-13 17:43:20.86 UTC] Identity Restarting Subscription after<PHONE_NUMBER>1s desired valency 1 current valency 0
Nov 13 17:43:20  : [db-sync-node.Subscription:Notice:48] [2021-11-13 17:43:20.86 UTC] Identity Starting Subscription Worker, valency 1
Nov 13 17:43:20  : [db-sync-node.Subscription:Notice:140204] [2021-11-13 17:43:20.86 UTC] Identity Connection Attempt Start, destination LocalAddress "/run/cardano-node/node.socket"
Nov 13 17:43:20  : [db-sync-node.Subscription:Notice:140204] [2021-11-13 17:43:20.86 UTC] Identity Connection Attempt End, destination LocalAddress "/run/cardano-node/node.socket" outcome: ConnectSuccessLast
Nov 13 17:43:20  : [db-sync-node.Handshake:Info:140204] [2021-11-13 17:43:20.86 UTC] WithMuxBearer (ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/run/cardano-node/node.socket"}) Send (ClientAgency TokPropose,MsgProposeVersions (fromList [(NodeToClientV_1,TInt 764824073),(NodeToClientV_2,TInt 764824073),(NodeToClientV_3,TInt 764824073),(NodeToClientV_4,TInt 764824073),(NodeToClientV_5,TInt 764824073),(NodeToClientV_6,TInt 764824073),(NodeToClientV_7,TInt 764824073),(NodeToClientV_8,TInt 764824073),(NodeToClientV_9,TInt 764824073),(NodeToClientV_10,TInt 764824073)]))
Nov 13 17:43:20  : [db-sync-node.Handshake:Info:140204] [2021-11-13 17:43:20.86 UTC] WithMuxBearer (ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/run/cardano-node/node.socket"}) Recv (ServerAgency TokConfirm,MsgAcceptVersion NodeToClientV_10 (TInt 764824073))
Nov 13 17:43:20  : [db-sync-node.Mux:Info:140204] [2021-11-13 17:43:20.86 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/run/cardano-node/node.socket"} event: Handshake Client end, duration 0.000452129s
Nov 13 17:43:20  : [db-sync-node.Mux:Info:140205] [2021-11-13 17:43:20.86 UTC] Bearer on ConnectionId {localAddress = LocalAddress "", remoteAddress = LocalAddress "/run/cardano-node/node.socket"} event: State: Mature
Nov 13 17:43:20  : [db-sync-node:Info:140208] [2021-11-13 17:43:20.86 UTC] Starting chainSyncClient
Nov 13 17:43:20  : [db-sync-node:Info:140208] [2021-11-13 17:43:20.87 UTC] Cardano.Db tip is at slot 40349231, block 6257385
Nov 13 17:43:20  : [db-sync-node:Info:140213] [2021-11-13 17:43:20.87 UTC] Running DB thread
Nov 13 17:43:20  : [db-sync-node:Info:140213] [2021-11-13 17:43:20.88 UTC] Rolling back to slot 40348798, hash 907b0257659c817a5e3dcf2fff293dfbe30bc6c5e17955d66b3e3888afefc77d
Nov 13 17:43:20  : [db-sync-node:Info:140213] [2021-11-13 17:43:20.88 UTC] Deleting 6 blocks up to slot 40349231
Nov 13 17:43:20  : [db-sync-node.Subscription:Notice:48] [2021-11-13 17:43:20.89 UTC] Identity Required subscriptions started
Nov 13 17:43:20  : [db-sync-node:Info:140213] [2021-11-13 17:43:20.97 UTC] Blocks deleted
Nov 13 17:43:34  : [db-sync-node:Info:140213] [2021-11-13 17:43:34.23 UTC] Found snapshot file for slot 40348798, hash 907b0257659c817a5e3dcf2fff293dfbe30bc6c5e17955d66b3e3888afefc77d
Nov 13 17:44:15  : [db-sync-node:Info:140213] [2021-11-13 17:44:15.16 UTC] File /var/lib/csyncdb/40348798-907b025765-290.lstate exists
Nov 13 17:44:20  : [db-sync-node:Info:140213] [2021-11-13 17:44:20.28 UTC] validateEpochRewards: total rewards that become spendable in epoch 291 is 15272492.983639 ADA
...

and it repeats over and over again.

Second time I tried it passed epoch 291.

Just FYI.
Could not reproduce, closing.


Allow credentials to be provided as an array

kreait_firebase:

projects:
    project_name:
        credentials:
            type: "%env(FIREBASE_CREDENTIALS_TYPE)%"
            project_id: "%env(FIREBASE_PROJECT_ID)%"
            private_key_id: "%env(FIREBASE_PRIVATE_KEY_ID)%"
            client_id: "%env(FIREBASE_CLIENT_ID)%"
            client_email: "%env(FIREBASE_CLIENT_EMAIL)%"
            private_key: "%env(string:FIREBASE_PRIVATE_KEY)%"

In the code of the Service account which is taking the credentials, there is a function to handle credentials being sent from array
But in the Configuration file it's not allowing it being sent in this way
The other way would be like this
        credentials: '{"type": "%env(FIREBASE_CREDENTIALS_TYPE)%","project_id": "%env(FIREBASE_PROJECT_ID)%","private_key_id": "%env(FIREBASE_PRIVATE_KEY_ID)%", "client_id": "%env(FIREBASE_CLIENT_ID)%", "client_email": "%env(FIREBASE_CLIENT_EMAIL)%","private_key": "%env(string:FIREBASE_PRIVATE_KEY)%"}'

Which is pretty much the same just a bit clearer
(Please note that this is the first time i contribute to an open source library so i really don't know about the process of what should be done)

Hey @AliMsayleb, and thank you for making your first contribution to this library, which makes me glad!
Could you please add the following tests to the ProjectFactoryTest class, right after the it_can_handle_a_credentials_path() test here?
/**
 * @test
 * @group legacy
 * @expectedDeprecation The %s method is deprecated (4.33 Use the component-specific create*() methods instead.).
 */
public function it_can_handle_a_credentials_string()
{
    $this->firebaseFactory
        ->expects($this->once())
        ->method('withServiceAccount');

    $credentials = file_get_contents(__DIR__.'/../../_fixtures/valid_credentials.json');

    $this->factory->create(['credentials' => $credentials]);
}

/**
 * @test
 * @group legacy
 * @expectedDeprecation The %s method is deprecated (4.33 Use the component-specific create*() methods instead.).
 */
public function it_can_handle_a_credentials_array()
{
    $this->firebaseFactory
        ->expects($this->once())
        ->method('withServiceAccount');

    $credentials = json_decode(file_get_contents(__DIR__.'/../../_fixtures/valid_credentials.json'), true);

    $this->factory->create(['credentials' => $credentials]);
}

I already tested those tests locally, but I would like them to be attributed to you as well instead of me adding them after the merge :)
This way we can make sure that the array support you added is fully tested and won't break with future changes.

Thanks! 🌺


Files without content break viewer

When a file no content it causes js error on browser and breaks it. Full reload neede to works again

fixed


Linestyle in 0.7 legend is less readable

Bug description
In version 0.6, the linestyle was legible in the legend regardless of the linewidth.

In version 0.7, it is harder to tell what linestyle the legend is trying to represent. The gap in the line looks either like a smudge or like it is representing a dash-dot type line.

Steps to reproduce
MWE:
using DataFrames, AlgebraOfGraphics, CairoMakie
df1 = DataFrame(
    x = 1:5,
    y = 1:5,
    label = "Label 1",
)
df2 = DataFrame(
    x = 1:5,
    y = 5:-1:1,
    label = "Label 2",
)
plot = visual(Lines, linewidth=3) *
       mapping(:x, :y, linestyle=:label=>"Data Label") *
       (data(df1) + data(df2))
draw(plot)

Version info
julia> versioninfo()
Julia Version 1.11.0-rc1
Commit 3a35aec36d (2024-06-25 10:23 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: Windows (x86_64-w64-mingw32)
  CPU: 8 × Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
  WORD_SIZE: 64
  LLVM: libLLVM-16.0.6 (ORCJIT, skylake)
Threads: 1 default, 0 interactive, 1 GC (on 8 virtual cores)
Environment:
  JULIA_EDITOR = code.cmd
  JULIA_NUM_THREADS =

⌅ [cbdf2221] AlgebraOfGraphics v0.6.20
  [13f3f980] CairoMakie v0.12.5
  [a93c6f00] DataFrames v1.6.1

One man's fix is another man's issue :)
This is because in 0.7, all the other plot attributes that are not mapped are also considered for the legend (which is generally desired), in your case it's thicker linewidth and that's what makes the legend less readable at default settings. You can either reduce the linewidth of the plot or increase the legend's patch size. Currently, one cannot individually modify legend entries, but you couldn't do that before, either.
I'm going to close this as it's neither a bug, nor is it planned to change the behavior.

patchsize is a good fix. Thanks.


Add MBart support for BetterTransformer

This PR adds the MBartEncoderLayerBetterTransformer class to support MBart.
During testing, the code is runnable but it yields different results compared with the original transformer model, as shown in the below picture. The specific models I tested are facebook/mbart-large-50 and facebook/mbart-large-cc25. The downstream task I tested is fill masks

Could you tell me what I can do to solve this problem and what other tests I need to run?
Thank you so much!

Very glad it worked @ravenouse ! Can't wait to see this PR to be merged!
Let me guide you step by step regarding the immediate next steps:
Step 1: Finish the integration for MBart

Since the refactoring for encoder-decoder based models tests has been recently addressed, adding the tests for MBart should be very easy. Just add a line with "hf-internal-testing/tiny-random-MBartModel" on the list ALL_ENCODER_DECODER_MODELS_TESTS here - push this change to see if the test pass (it should pass if everything works as expected , or you can just run the command pytest tests/bettertransformer/test_bettertransformer_encoder.py::BetterTransformersEncoderDecoderTest
Add a line stating that MBart is supported for BetterTransformer on the documentation. The addition should go here (make sure to respect the alphabetical order)

Step 2: Add the integration for NLLB

NLLB is a recent encoder-decoder model from Meta AI that is integrated in transformers. Since NLLB uses the same encoder layer as MBart (see this line) the addition is very easy. Just add the line "M2M100EncoderLayer":MBartEncoderLayerBetterTransformer here.
Once the model is integrated as follows. Follow the same procedure as Step 1, and you can use the model hf-internal-testing/tiny-random-nllb for the integration tests ;)
Let me know if anything is unclear! Again thanks a lot for your great contribution @ravenouse 💪

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Thanks a lot!
Could you just run the styling (run "make style") push the changes and we should be good to merge! 💪🏻

Thanks so much @ravenouse !
Sure yes, just make sure to notify other contributors in https://github.com/huggingface/transformers/issues/20372 too ;)


Bdd environment

Team has reviewed the code, discussion in the slack channel
Normally the same person who created the pull request shouldn't be the one merging but I'll do it just for the sake of getting it done


Unable to use multiple clients of different version like v3 and v5 in same application

Please use the following questions as a guideline to help me answer
your issue/question without further inquiry. Thank you.
Which version of Elastic are you using?
[ ] elastic.v7 (for Elasticsearch 7.x)
[ ] elastic.v6 (for Elasticsearch 6.x)
[ x ] elastic.v5 (for Elasticsearch 5.x)
[ x ] elastic.v3 (for Elasticsearch 2.x)
[ ] elastic.v2 (for Elasticsearch 1.x)
Please describe the expected behavior
I am using v5 client and v3 client together on same application since I have the use case where I have to send the data to the search clusters of different version. I'm expecting that it should work because I have kept a map of client object and using the specific version of client based on the request.
@olivere can you please shed some light on this as this is kind of urgent thing. Also, let me know if there is any work around to achieve this.
Please describe the actual behavior
Data for cluster A(version 2.x) is getting updated but the which is supposed to go to Cluster B(version 5.x) is not getting updated, even there is no log which says about any failure. I am using bulk processor.
Any steps to reproduce the behavior?
Just use two different version client objects (e.g. v3 and v5) and then send some data using v3 client and some data using v5.

Versions other than 6.x and 7.x are no longer supported. Furthermore, versions before 7.x do not support Go modules.
You can solve it by using a different approach. Here's an example.