Build fails Tor framework from Carthage

In the cartfile, I wrote github "iCepa/Tor.framework" "master" and ran carthage update.
The build fails with the following error:
*** Building scheme "Tor-Mac" in Tor.xcodeproj
** BUILD FAILED **
The following build commands failed:
ExternalBuildToolExecution openssl-Mac
(1 failure)
A shell task failed with exit code 65:
** BUILD FAILED **
The following build commands failed:
ExternalBuildToolExecution openssl-Mac
(1 failure)
I don't know what I'm doing wrong.
Please help. Thanks

Update:
The following is from the build log,
cp: /Xcode/DerivedData/Tor-aqvflbpdbbukfahhupszphsxowds/Build/Intermediates/Tor.build/Release/openssl-x86_64/lib/*.a: No such file or directory
fatal error: /Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: can't open input file: /Xcode/DerivedData/Tor-aqvflbpdbbukfahhupszphsxowds/Build/Products/Release/libssl.*.a (No such file or directory)
fatal error: /Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: can't open input file: /Xcode/DerivedData/Tor-aqvflbpdbbukfahhupszphsxowds/Build/Products/Release/libcrypto.*.a (No such file or directory)
rm: /Xcode/DerivedData/Tor-aqvflbpdbbukfahhupszphsxowds/Build/Products/Release/libssl.*.a: No such file or directory
rm: /Xcode/DerivedData/Tor-aqvflbpdbbukfahhupszphsxowds/Build/Products/Release/libcrypto.*.a: No such file or directory

Can you post the full build log somewhere? The above is not particularly useful for debugging the issue.
Do you have autoconf and automake installed?

Might be due to a known issue with the new XCode 7.3 and Tor 0.2.7.X. See https://github.com/ursachec/CPAProxy/issues/40 and https://trac.torproject.org/projects/tor/ticket/18626 There's a patch in that Tor ticket (and it’s been fixed in <IP_ADDRESS>-alpha, though we might not get a fix for 0.2.7.x).
Though it could always be something else; could definitely use the full build output from @ali-ht10 to diagnose.

@mtigas  I have XCode 7.3.
@conradev autoconf and automake is installed.
PFA the log file
carthage-xcodebuild.rtf.zip

Thanks for the reply.
@conradev I have automake and autoconf installed.
@mtigas I have XCode 7.3
PFA the log file,
carthage-xcodebuild.rtf.zip

It seems to compile fine, just runs into an error installing:
/bin/sh: /Users/Downloads/iCepa-master: is a directory
make: *** [install_docs] Error 126

Will attempt to reproduce this!

Thanks alot @conradev

I can't seem to understand how tun2tor is working in this project. Can you give me any directions so that it can help me understand how tun2tor is working in this project.
Thanks

Apparently the openssl issue was fixed because I had a space in the directory path. Once I removed that openssl compiled and installed successfully.
But libevent is causing an issue. This is the error:
configure.ac:101: error: possibly undefined macro: AC_PROG_LIBTOOL
configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."
I did ran brew install automake autoconf. automake and autoconf are in /usr/local/bin/. But I can't seem to understand the README requirements section in Tor.framework, autoconf and automake in your PATH. Where should autoconf and automake be installed? What PATH should I need to specify?
PFA the updated log file
carthage-xcodebuild-update.rtf.zip
Thanks again

Thanks for discovering that! I will need to make sure that the build scripts function with spaces in the path.
If you run echo $PATH in Terminal and the directory that contains automake or autoconf is printed, then they are in your PATH. According to the script, your copies of automake and autoconf are in your PATH correctly.
It seems that I missed a required dependency! You also need libtool in your PATH. Run brew install libtool to fix that.

What questions do you have about tun2tor specifically?

Thanks for the response.
Running brew install libtool did however worked in a way.** "Tor-Mac"** scheme built successfully. But there were errors when "Tor-iOS" scheme was building.
Here is the error which showed up on terminal:
*** Building scheme "Tor-Mac" in Tor.xcodeproj
*** Building scheme "Tor-iOS" in Tor.xcodeproj
** BUILD FAILED **
The following build commands failed:
Ld /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Intermediates/Tor.build/Release-iphoneos/Tor-iOS.build/Objects-normal/arm64/Tor normal arm64
(1 failure)
configure.ac:14: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated.  For more info, see:
regress_buffer.c:199:12: warning: logical not is only applied to the left hand side of this comparison [-Wlogical-not-parentheses]
regress.c:715:2: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress.c:716:2: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress.c:717:2: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress_bufferevent.c:772:2: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress_bufferevent.c:773:2: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress_thread.c:379:8: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress_thread.c:379:21: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress_thread.c:393:3: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
/Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/shlib_wrap.sh: line 96: /Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/../apps/openssl: Undefined error: 0
/Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/shlib_wrap.sh: line 96: /Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/../apps/openssl: Undefined error: 0
/Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/shlib_wrap.sh: line 96: /Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/../apps/openssl: Undefined error: 0
/Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/shlib_wrap.sh: line 96: /Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/../apps/openssl: Undefined error: 0
/Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/shlib_wrap.sh: line 96: /Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/../apps/openssl: Undefined error: 0
/Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/shlib_wrap.sh: line 96: /Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/../apps/openssl: Undefined error: 0
/Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/shlib_wrap.sh: line 96: /Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/../apps/openssl: Undefined error: 0
/Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/shlib_wrap.sh: line 96: /Users/Downloads/iCepa-master/Carthage/Checkouts/Tor.framework/Tor/openssl/util/../apps/openssl: Undefined error: 0
regress_buffer.c:199:12: warning: logical not is only applied to the left hand side of this comparison [-Wlogical-not-parentheses]
regress_buffer.c:199:12: warning: logical not is only applied to the left hand side of this comparison [-Wlogical-not-parentheses]
regress.c:715:2: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress.c:716:2: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress.c:717:2: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress_bufferevent.c:772:2: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress_bufferevent.c:773:2: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress_thread.c:379:8: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress_thread.c:379:21: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
regress_thread.c:393:3: warning: absolute value function 'abs' given an argument of type 'long' but has parameter of type 'int' which may cause truncation of value [-Wabsolute-value]
configure: error: Missing libraries; unable to proceed.
ld: warning: ignoring file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libor.a, missing required architecture arm64 in file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libor.a (1 slices)
ld: warning: ignoring file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libor-trunnel.a, missing required architecture arm64 in file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libor-trunnel.a (1 slices)
ld: warning: ignoring file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libcurve25519_donna.a, missing required architecture arm64 in file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libcurve25519_donna.a (1 slices)
ld: warning: ignoring file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libtor.a, missing required architecture arm64 in file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libtor.a (1 slices)
ld: warning: ignoring file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libor-event.a, missing required architecture arm64 in file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libor-event.a (1 slices)
ld: warning: ignoring file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libed25519_ref10.a, missing required architecture arm64 in file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libed25519_ref10.a (1 slices)
ld: warning: ignoring file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libed25519_donna.a, missing required architecture arm64 in file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libed25519_donna.a (1 slices)
ld: warning: ignoring file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libor-crypto.a, missing required architecture arm64 in file /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Products/Release-iphoneos/libor-crypto.a (1 slices)
clang: error: linker command failed with exit code 1 (use -v to see invocation)
A shell task failed with exit code 65:
** BUILD FAILED **
The following build commands failed:
Ld /Users/Library/Developer/Xcode/DerivedData/Tor-cqwwpuougygethcwxgmrvujovwzm/Build/Intermediates/Tor.build/Release-iphoneos/Tor-iOS.build/Objects-normal/arm64/Tor normal arm64
(1 failure)
Questions for tun2tor:

How does tun2tor parse packets?

How can I use tun2tor to send the traffic to tor?

Link to log file: https://gist.github.com/ali-ht10/b9ad6eec872c9928a9c14c9907ce5328
Thanks again :D

Looking at the log file, I noticed this:
"checking for openssl directory... configure: WARNING: Could not find a linkable openssl.  If you have it installed somewhere unusual, you can specify an explicit path using --with-openssl-dir
configure: error: Missing libraries; unable to proceed.
make: *** No targets specified and no makefile found.  Stop."
I can't figure out why openssl directory is missing.

Basically what I want to achieve is that all my internet traffic on the device routes through Tor. Is it even possible to do that? Does this involve working at the network layer?
Thanks

I went ahead and fixed all of the issues you were seeing in the build:

I added libtool and gettext to the README
I made the build work in directories with spaces
I fixed the Could not find a linkable openssl issue (backported from here as @mtigas suggested)

Let me know if it builds successfully for you now!
I would like to point out the following from the README:

The project does not work yet, and is in progress.

The goal of the project is indeed to route all internet traffic through Tor, but because it is not finished yet it does not yet achieve that goal.

How does tun2tor parse packets?

I wrote simple IPv4, IPv6, UDP and TCP packet parsers as a part of tun2tor.

How can I use tun2tor to send the traffic to tor?

tun2tor isn't fully functional yet, but it has a SOCKS client that it will use to send traffic to tor. Right now, tun2tor only supports DNS traffic.

Thanks @conradev . It successfully builds.


Add hook to mark application as in maintenance mode

Even though hapistrano keeps downtime relatively low, by building in a separate directory, and then changing the "current" application symlink, there may be downtime necessary, for example, if a database migration has to take place.
Generally, the deploy process is as follows:

new application is built
current running app is placed in maintenance mode
then the schema can be migrated
then the app can be brought back up

If you don't follow this process, application errors may occur since any given version of the code generally depends on a particular database schema.
Capistrano handles this case by allowing for a hook to bring up a maintenance page, and then to take it down once the deploy tasks are done. See the hapistrano maintenance library for their implementation. Hapistrano should support something similar in order to support these cases when downtime is required.

 hapistrano - Add hook to mark application as in maintenance mode

 Add hook to mark application as in maintenance mode

Hello @jsl  After taking a look at capistrano maintenance, it seems it's used as a short hand for some simple commands:

cap maintenance:enable could be replaced with:

echo '<html>...' > /path/to/server/maintenace.html
# or
cp /path/to/my/maintenance.html /path/to/server/maintenace.html

cap maintenance:disable could be replaced with:

rm -rf /path/to/server/maintenace.html

And these could be easily added in the build script:
build_script:
 - cp /path/to/my/maintenance.html /path/to/server/maintenace.html
 - db migrations
 - # another task that will affect the server
 - rm /path/to/server/maintenace.html

I think we could also implement something similar as capistrano-maintenance in hapistrano to quickly create a maintenance file from the command line (e.g. hap maintenance enable/disable). However, these could be done from the server without so much effort:
ssh user@server 'cp /path/to/my/maintenance.html /path/to/server/maintenace.html'

and
ssh user@server 'rm /path/to/server/maintenace.html'

Therefore, I don't think it's worth the effort to implement these tasks in hapistrano.

Hello! I reviewed this internally with the team and I proposed the following two ideas:

Implement a maintenance enable/disable CLI commands in hapistrano:
hap maintenance enable => will create a maintenance file in a specific file
hap maintenance disable => will remove the maintenance file, so the proxy can keep redirecting the requests to the application

Implement a with_maintenance yaml object will run some specific tasks in the build script in maintenance mode:

build_script:
 - build
 - build_something_else
 - with_maintenance:
    steps:
       - db migrations
       - other_task_that_affects_the_server

The steps defined within with_maintenance will run while the proxy serves a maintence.html file.
I think both implementations can be useful. However, the second option will be a better fit for this particular issue. Therefore, we'll implement this option first.

We already have a maintenance mode in hapistrano. It does something similar to what capistrano-maintenance does. Therefore, a user can do something like:
hap maintenance enable # Creates maintenance file (up to the user to set up his server to redirect the request there)
hap deploy
hap maintenance diasble # Removes maintenance file

There are other ways to improve this. I'll open another issue to improve the maintenance mode.


Research the options for event migration

Pls research https://github.com/scalapenos/stamina.

Does this library automatically detect accidental changes to the events, introduced by the programmer? That's what I'm most afraid of in Hydra TBH (or any event-based software, for that matter)
It seems that Stamina runs on the top of spray-json... can this be replaced by Borer or Kryo (#27)?
Provide some short example of event migration in code... does the API feel mature enough? did you need to hack anything/check the source code of library to fix unexpected problems?
Are there any alternatives that claim to do the same thing out there on GitHub?

I think this task has already been completed and could be linked with #46

Actually... unlinked from #46. I'd say the output for this task should be the examples of migration that you've prepared for Borer/Circe... pls add them under examples/ or sth like that


[crypto] update proof system

testing https://github.com/o1-labs/proof-systems/pull/877

!ci-build-me

!ci-build-me


(#1646) replaces KeyError handling logic

Switches out KeyError handling with walrus operator based alternative logic in the run_engine script

Note: Auto-formatting changes have included themselves in other parts of the script

Description

Each clause which used to catch raised KeyError instances has
had its logic replaced by a suggested walrus operator based flow control
checking for None in the getter return from a dict key look up
Motivation and Context

The older, replaced logic was considered clunky and inappropriate for flow control

Fixes issue #1646
How Has This Been Tested?

Only tests are the usual CI suite.
No new tests are added as this is a like for like refactoring replacement,
not a development of new features nor new methods.

@callumforrester Can we sort out why the auto-formatters are fighting each other?  I would really like to avoid the code churn when some other tool puts it back....
Can we only commit the relevant lines in this PR?

mostly 👍🏻 on the content of the changes, but I have a concern that we are sure that in all of these dictionaries than None will never be a valid value.  It may be safer to do something like
_RE_EMPTY_MARKER = object()

...

if (val := dictionary.get(key, _RE_EMPTY_MARKER)) is _RE_EMPTY_MARKER:
   ...

....

which checks for a value that can never (well, if it does it is a bug) end up in a dictionary.

... but I have a concern that we are sure that in all of these dictionaries than None will never be a valid value.
It may be safer to do something like...

I think of the dozen or so instances where KeyError handling has been touched by the change, most of them go on to use the dict value as an instance of an object and try to invoke a method via the dot operator.  In that majority of examples - I think None is (or should not be) permitted as a value ( even if the dict was storing value None against the key )
There are one or two where None is fine and the next pull request should tackle that (I'll submit it once I'm done typing this)

Even in the cases where None is a bad value, debugging "How did a None end up where it should not?" is a very different journey than debugging "Why is a key missing?".

re: different debugging journeys...

Good point - and well made!


Adds preparation instructions for the Event-Sourced Domain Models wor…

The PR adds some instructions for workshop participants so they can prepare their laptops in advance of the workshop (hopefully!)

Great, thanks!


Audit of existing notebooks

bicycle2dof

topics:

multi degree of freedom systems
turning a system of second order equations of motion into first order in matrix form
the eigenvalue problem (in general)
phasors
mode shapes
odeint
stability

needs a sketch of the system with steering and roll state variables
needs explanation for the two different stiffness matrices
I think this example would be good for teaching some of the topics listed above, whereas they are currently treated more like dependencies and this is just a real-world example for motivation
the benchmark_parameters could benefit from being a class where you can set attributes rather than a function that returns a dict
benchmark_par_to_canonical should probably be hidden
the exercises at the end are good, including some exploration and design tasks

book_balancing

topics:

non-linear dynamics
linearization
Lagrange method
odeint

linearization exercise maybe should be testable in some way
having them approximate the period of the nonlinear oscillations by looking for zero crossings is nice as a practical exercise
the real demo up in front of the class went well I think
the final question (derive the equations of motion) was frustrating to them and may not have been all that enlightening

bumpy_road

topics:

base excitation
homogeneous and particular solution
damper design
force transmissibility

needs a drawing (currently refers to book example)
currently is a bunch of code and a couple design exercise prompts -- need to determine if/how much they should code
needs significantly more text and equations

forced_vibrations_with_viscous_damping

topics:

harmonic excitation (force)
homogeneous and particular solution
phasors
resonance

this notebook is pretty well fleshed out
the vector representation section could be the introduction to the topic rather than assuming it's a prereq -- a little phasor widget could be useful here
there is a lot of plotting code here

nonlinear_vibrations

topics:

2nd-order equation of motion to system of first ODEs
nonlinear dynamics
Coulomb friction
pendulum
stability (inverted pendulum)
comparing linear vs. nonlinear free responses

this was the first notebook introducing numerical ODE integration
the intro material of this notebook could be good to just add to the top of the book balancing notebook, since that's a bit more interesting of an example

sawtooth_forcing

topics

arbitrary periodic forcing
Fourier series
symbolic computation

if used as standalone notebook on Fourier series and periodic forcing, needs more intro material
when moving to numerical use of the Fourier coefficients, should we use subs on the sympy expressions?
needs a real-world example
the concept of using Fourier series coefficients to approximate a complicated forcing function and analytically evaluate the output seems somewhat antiquated -- it's fairly theoretical and I can't come up with a good real-world example

vibrating_building

topics:

multi-dimensional systems (>2dof)
the eigenproblem
mode shapes
spring only

needs a diagram/model
assumes they've already seen the theoretical material -- needs more text and equations
seems common for students to be lost by all of the matrix manipulations

viscous_damping

topics:

linear damping
under/over/critical damping

needs a mass-spring-damper diagram
a motivational real-world example would be cool
programming of the damping regimes was not great, e.g. hard to choose a c value to make zeta=1

Closing this. We incorparted everything in some modified form. Thanks for laying this out in August.


Send typing when a messge starts processing.

This just simply closes #30.


Killer Joe and Dimensional Transciever stop functioning

Killer Joe stops killing mobs after only using a quarter tank of nutrient distillation and will not work again. I just have to make a new one. Dimensional Transciever worked once. When I tried to move one of the units I could not reestablish a connection even with new transcievers or channels.

One more thing. I use Ubuntu and Windows. The problem has persisted across multiple instances on both OS.

both Killer Joe & Zombie generator requires you to have at least 75% of nutrient distillation any lower it will stop functioning
the Dimensional Transciever needs power to work each one have 250k internal storage and uses 10rf/tick
if the problems still occurs what version of EIO are you using ? provide more information

What @6210classick said is accurate. The killer joe needs to be filled up to the red line in the GUI to function and the DimTrans needs constant power to keep a channel active.


Which commit corresponds to the PyPi 0.2.1 release?

At https://github.com/AnacondaRecipes, we are trying to build fairseq2 0.2.1, but noticed the GH project is not tagged at that version, but looking at the history, this commit seems to correspond to the PyPi release. Can you confirm?

@boldorider4
Yes this is the PyPi release for v0.2.1


Cancel commands after disconnect in at-most-once mode.

Commands that are queued/on the protocol stack should be completed exceptionally (canceled) if the connection disconnects. Lettuce does not reconnect in such case and commands remain within the queue until the connection is closed.
Leaving this ticket here as a reminder, not necessarily to implement it immediately.

Addressed with #547 to cancel commands on disconnect in at-most-once mode (disabled auto-reconnect).


Systems missing from usage example in README.md

Hi,
The example in README.md is a bit contrived (string/int components -- useful for testing though). In particular, it doesn't explain how to use systems.
ECS libraries can do things different ways, and I think Eskimo is missing a sort of "philosophical design" part that states things like (if I got this right):

Entities are just an ID and a bag of components
Components can be any class, and are usually just data
Views allow you to filter (and operate) on entities that have a particular set of components
Systems ... ???

In particular, I thought systems are supposed to be a "super-set" of views: they filter and select entities with the right set of components, and they have some "update" method or something that they operate across all components (eg. find all entities with position and velocity components, and move the position according to the velocity).
How is Eskimo supposed to work with regards to systems?

Good call!
Originally, I didn't even want to add Systems to Eskimo, since they are completely utility/helper objects, rather than core to the design.
Your descriptions are good, I'll probably copy-paste them + expand on them if I may : )
Systems are modular pieces of logic. You can easily use ECS data and entity management, but program all of your functionality in 1 class, 1 function, or however you want to split everything, but Systems offer a very compartmentalized way of doing so, and sort of enforces stricter logic boundaries. I use it usually, but at the same time I've started to be less strict about how they communicate.
Systems are a utility to organize your own code, but definitely not necessary to use Eskimo as an ECS.

Ah, that's the trick. Sneaky! You're not committing to any one particular "style" of ECS, but allowing users to use it to fit whatever design they like.
Thanks for clarifying. You can close this issue if you like, or leave it open until you're done documenting whatever it is you want to add.


Generated Mock Data

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix
[ ] New feature
[ ] This change requires a documentation update

Checklist:

[x ] My code follows PEP8 style guide
[ x] I have removed unnecessary print statements from my code
[ x] I have made corresponding changes to the documentation if necessary
[ x] My changes generate no errors
[x ] No commented-out code
[ x] Size of pull request kept to a minimum
[x ] Pull request description clearly describes changes made & motivations for said changes

Hi Archana, you should update the pull request with a description, per the guidelines. Also attach a Trello User story to the description.
And there must be some markdown explaining the flow of the notebook. Especially the complex parts like why you chose a poisson and what the weightedchoice objects are doing.


Javi/spinq10q 12 zcu111

Platform and runcard for Spinq10q chip qubits 2, 3, and 4 controlled with ZCU111. This PR works with qibosoq, qibolab, and qibocal main.

This PR works with qibosoq, qibolab, and qibocal main.

Ah, sorry, I haven't read it. But I don't expect to work with current main. At least not after:
https://github.com/qiboteam/qibolab/commit/83bdae5c601aa5f939ff77168a14bdcc37705661

This PR works with qibosoq, qibolab, and qibocal main.

Ah, sorry, I haven't read it. But I don't expect to work with current main. At least not after: qiboteam/qibolab@83bdae5

I have the impression that the yaml is redundant. There’s also another platform for three qubits committed here that is using json. This may be the one we need and should be compatible with latest main.

Hi guys, I just want to put in main the platform qibolab_platforms_qrc/spinq10q_12_zcu111. There is no yaml or weird things, just a json file for parameters and python code for the platform, and everything working with the last versions of qibolab and qibocal.

You're both right: I was confused because I started from the first file in the "Files Changed" tab.
This PR is actually adding 4 files, but only those within the folders most likely are relevant, while the other two are related to a supposed Qblox platform (not even sure if it's connected), that is indeed using the YAML.
Should I remove those files from the PR?

I tried to run, but I'm getting the following error from QICK:
  File "/home/xilinx/qibosoq/src/qibosoq/server.py", line 140, in handle
    results = execute_program(data, self.server.qick_soc)
  File "/home/xilinx/qibosoq/src/qibosoq/server.py", line 103, in execute_program
    toti, totq = program.perform_experiment(
  File "/home/xilinx/qibosoq/src/qibosoq/programs/base.py", line 246, in perform_experiment
    res = self.acquire(  # pylint: disable=E1123,E1120
  File "/usr/local/share/pynq-venv/lib/python3.10/site-packages/qick/averager_program.py", line 106, in acquire
    avg_d = super().acquire(soc, soft_avgs=self.soft_avgs, load_pulses=load_pulses, start_src=start_src, threshold=threshold, angle=angle, progress=progress)
  File "/usr/local/share/pynq-venv/lib/python3.10/site-packages/qick/qick_asm.py", line 1145, in acquire
    self.config_all(soc, load_pulses=load_pulses)
  File "/usr/local/share/pynq-venv/lib/python3.10/site-packages/qick/asm_v1.py", line 672, in config_all
    super().config_all(soc, load_pulses)
  File "/usr/local/share/pynq-venv/lib/python3.10/site-packages/qick/qick_asm.py", line 668, in config_all
    self.config_readouts(soc)
  File "/usr/local/share/pynq-venv/lib/python3.10/site-packages/qick/qick_asm.py", line 748, in config_readouts
    soc.configure_readout(ch, output=cfg['sel'], frequency=cfg['freq'], gen_ch=cfg['gen_ch'])
  File "/usr/local/share/pynq-venv/lib/python3.10/site-packages/qick/qick.py", line 698, in configure_readout
    buf.set_freq(frequency, gen_ch=gen_ch)
  File "/usr/local/share/pynq-venv/lib/python3.10/site-packages/qick/drivers/readout.py", line 553, in set_freq
    self.readout.set_freq(f, self.readoutport, gen_ch=gen_ch)
  File "/usr/local/share/pynq-venv/lib/python3.10/site-packages/qick/drivers/readout.py", line 297, in set_freq
    self.set_freq_int(freq_int, in_ch, out_ch)
  File "/usr/local/share/pynq-venv/lib/python3.10/site-packages/qick/drivers/readout.py", line 308, in set_freq_int
    raise RuntimeError("frequency collision: tried to set PFB output %d to %f MHz and output %d to %f MHz, but both map to the PFB channel that is optimal for [%f, %f] (all freqs expressed in first Nyquist zo
ne)"%(out_ch, newfreq, self.out_chs[in_ch], oldfreq, lofreq, hifreq))
RuntimeError: frequency collision: tried to set PFB output 2 to 118.631001 MHz and output 1 to 81.351999 MHz, but both map to the PFB channel that is optimal for [-128.000000, 128.000000] (all freqs expressed
 in first Nyquist zone)

Should I remove those files from the PR?

Yes, I think we should remove.

Yes, I think we should remove.

Ok, I'm waiting for @JavierSerranoGarcia approval, and I'll remove them.
In the meanwhile, I rebased the branch, since it was still containing old tii_* platforms, that are not any longer in main.
@JavierSerranoGarcia in case you have troubles pulling, just use instead:
git pull --rebase

Hi, the only files that should be merged are parameters and platform in the folder spinq10q_12_zcu111. The rest of the file can be removed ...
Regarding the problem of the frequency collisions happens that the resonator are very close in this chip and qick use a polyphase filter with very wide passband and often collisions happens. The trick is using a LO frequency 7.43 GHz for qubits 3 and 4, and LO frequency 7.39 GHz with qubits 2 and 3.
By the way, it would be very useful if we could write these tricks in the parameters.json file.

The trick is using a LO frequency 7.43 GHz for qubits 3 and 4, and LO frequency 7.39 GHz with qubits 2 and 3.

If I understand correctly, it seems you're talking the two-qubit gates (since 2-3 and 3-4 are the pairs connected in the runcard's topology).
If you'd like to change the LO frequency during execution, we can consider what's the best we could do, but changing the external LO frequency is a considerably slower operation, that can not happen in real-time. Instead, if it is about the pulses' frequency (as it seems, since the frequencies you're quoting are close enough to be in range for the IF), that's of course already available in parameters.json. You just need to change the frequency of the natives
However, I got the problem above just running single-shot classification for all qubits at the same time (so no two-qubit gates). If you can slightly adjust the frequencies of the natives to fix the problem above it would be optimal. Otherwise, maybe I should ask you more details about the issue, because I may have misunderstood.

If I understand correctly, it seems you're talking the two-qubit gates (since 2-3 and 3-4 are the pairs connected in the runcard's topology).

I don't think the issue is related to two-qubit gates. If I understand it correctly, it is about the LO used for readout, so basically means that we cannot measure all three qubits in the same execution, regardless of what drive gates are used before.

If you'd like to change the LO frequency during execution, we can consider what's the best we could do, but changing the external LO frequency is a considerably slower operation, that can not happen in real-time.

Indeed, changing the LO frequency is not possible in real-time. The particular LO used here is external (R&S) so it is certainly not possible. I think that even for other instruments with internal LO, changing its frequency requires some time for the signal to stabilize, so it is not recommended for real-time. Therefore, I don't think there is much we can do from the qibolab side to solve this problem. We already provide interfaces to update LO frequencies in the script but these are not real-time.

Instead, if it is about the pulses' frequency (as it seems, since the frequencies you're quoting are close enough to be in range for the IF), that's of course already available in parameters.json. You just need to change the frequency of the natives

I also don't fully understand what is causing this frequency collision. Usually we need to change LO frequency if the frequencies we want to send are beyond the IF bandwidth, but this doesn't seem to be the case here. Note that the frequency of the natives is mainly dictated by the chip so we cannot change it much if we want to measure properly. We can probably get away with a few Hz-kHZ but not MHz, so I am not sure if we can fix the problem this way. Another solution could be to plug two LOs to the same line, but this will probably create other side effects.

However, I got the problem above just running single-shot classification for all qubits at the same time (so no two-qubit gates). If you can slightly adjust the frequencies of the natives to fix the problem above it would be optimal.

For now I tried running the single shot on just qubits 3, 4. This does not give the frequency issue, but it gives another one:
qibosoq.client.QibosoqError: Traceback (most recent call last):
  File "/home/xilinx/qibosoq/src/qibosoq/server.py", line 140, in handle
    results = execute_program(data, self.server.qick_soc)
  File "/home/xilinx/qibosoq/src/qibosoq/server.py", line 103, in execute_program
    toti, totq = program.perform_experiment(
  File "/home/xilinx/qibosoq/src/qibosoq/programs/base.py", line 257, in perform_experiment
    return self.collect_shots()[-2:]
  File "/home/xilinx/qibosoq/src/qibosoq/programs/base.py", line 294, in collect_shots
    tot.append(stacked[:, idx].reshape(shape).tolist())
ValueError: cannot reshape array of size 10000 into shape (2,1,10000)

I tried with both qibosoq relase and main.

The last issue I believe is related to https://github.com/qiboteam/qibocal/issues/737.
@rodolfocarobene updated Qibosoq after that, and now we're always reshaping. Though I'm not sure why the initial 2, since it seems just the number of qubits.
I could investigate myself, but maybe @rodolfocarobene already has a clearer picture of what's going on.

The problem with the frequency collisions is due to the polyphase filter. The bandpass width of one filter in the bank is around 160 MHz and we can only read one qubit per filter. However the resonator  frequencies in our chips are every 50 MHz (approx), too close for these filters. Choosing  the frequency of the LO properly we can get two qubits in different filters and read them simultaneously but not 3.
The solution is redesigning the polyphase filter and we are working on it. But in the meantime just let's merge this platform.
The problem with the reshaping is something I already commented to Rodolfo.

The problem with the frequency collisions is due to the polyphase filter. The bandpass width of one filter in the bank is around 160 MHz and we can only read one qubit per filter. However the resonator frequencies in our chips are every 50 MHz (approx), too close for these filters. Choosing the frequency of the LO properly we can get two qubits in different filters and read them simultaneously but not 3.
The solution is redesigning the polyphase filter and we are working on it. But in the meantime just let's merge this platform.

Ok, so I get your problem is demultiplexing the signal you're receiving on an individual physical channel.
Since you can only split signals in bands of a certain minimum bandwith, you'd like to have a specific LO frequency, such that different qubits are falling in different minimum bands (though it is impossible to disentangle in this way 3 qubits, because you can tune one threshold, but the second one would be too far in any case).
This of course you can do ahead of time: having measured the qubit frequencies, you can compute your desired LO frequency, and set that to your external LO. And it's definitely in your runcard:
https://github.com/qiboteam/qibolab_platforms_qrc/blob/4eea3fbe7f65edeabe9dfaf8cec4c3a4248499e7/spinq10q_12_zcu111/parameters.json#L23-L25
In principle, you can even change dynamically during an experiment, but it makes little sense for Qibolab to switch LO frequency according to the pulse is being given.
What you could do, instead, is to create two different platforms: one for qubit 2 and 3, with LO 7.39 GHz, and one for qubit 3 and 4, with LO 7.43 GHz.
They will both work, and it's not very useful anyhow to have a single platform with all three qubits, since (as you're saying) you can never use all the three of them at the same time.

Thank you @alecandido, it is a good solution.

@JavierSerranoGarcia this PR is most likely outdated now. Can we close it?

Hi @alecandido, It is certainly outdated. The ZCU111 is connected to a different chip (but the same wires, so the platform should be OK). Would you like me to create a new, updated platform so you can test code on it?

THe platform on branch Javi/spinq10q 12 zcu111 is no longer used

Hi @alecandido, It is certainly outdated. The ZCU111 is connected to a different chip (but the same wires, so the platform should be OK).

Hi @JavierSerranoGarcia, thanks for the update!

Would you like me to create a new, updated platform so you can test code on it?

For the time being, it is not urgent: we will try to update the driver to the new version of Qibolab. At the beginning, we won't need anything, just to make sure it's barely consistent.
Then, a board in loopback should be sufficient for another while (flashed with QICK tproc v1, non-modified firmware - either the basic or multiplexed firmware should be equally good). We can discuss the optimal connections when we'll get there.
We will only need a qubit connection for the final part (to make sure all routines will be correctly supported). However, if you already have a connected board (with the aforementioned firmware) and that's simpler to you, we can work with that from the beginning.
For as long as it respects the requirements (i.e. v1 non-modified), we should not be sensitive to which specific board, since Qibosoq is supposed to work with all of them (111, 216, 4x2).

@alecandido, @aorgazf ,  we are maintaining a QPU based on our chips and our control electronics. So, we change the chip and firmware from time to time with better versions and I am raising a PR  for every new version of the platform just in case someone wants to use it.
We are starting to test the tProc V2 and think it will be the standard firmware shortly. So if you are developing any software it should be for this version and, in addition, we are adapting the firmware to fix some issues we are finding in the standard version. Take it into account when you develop something.

We are starting to test the tProc V2 and think it will be the standard firmware shortly. So if you are developing any software it should be for this version and, in addition, we are adapting the firmware to fix some issues we are finding in the standard version. Take it into account when you develop something.

Hi @JavierSerranoGarcia, I'm aware of it, and perfectly agree with you.
However, I'm just proceeding methodically in steps: as you may know, we have a new major version of Qibolab around (0.2), and the current upgrade is to support this new version.
In order to make minimal changes, we're going to first upgrade the driver, without touching Qibosoq at all.
Of course, after that, the next steps will involve a closer integration with the tProc v2 (on top of a generally closer integration with QICK, than what is currently provided by Qibosoq, as agreed with @aorgazf as well).

in addition, we are adapting the firmware to fix some issues we are finding in the standard version. Take it into account when you develop something.

That I'm aware of, especially from the meetings with QICK team. There is no single person fully dedicated to that. But as soon as we can get there, we will keep supporting the driver for all the firmware(s) in current use.


Error when loading: AutoLogin requires Piwik <5.0.0-b1

Shown message in administration:
The plugin AutoLogin could not be loaded as it has missing dependencies: AutoLogin requires Piwik <5.0.0-b1. Please contact your Matomo administrator.
Plugin version:  (0.1.2)
Matomo: 5.0.2
Do you need any more info?
Thanks!

@tangkevkev Could you have a look here please?

@StaffanMelin: This plugin has only been tested with Matomo version 4.
We have not tested it for version 5 and cannot guarantee that it will work. If you still want to use it right now, I think you can copy the source code and change this entry: https://github.com/inventage/matomo-autologin-plugin/blob/main/plugin.json#L16 to your Matomo version. Let me know if it works.
We will try to offer support for version 5 in the near future.
Cheers
Kevin

Thank you @tangkevkev ! We don't currently use it, so no rush.


LaTeX fails install -- help?

scoop install latex
installing latex (2.9.5987)
downloading https://miktex.org/download/ctan/systems/win32/miktex/setup/miktex-portable-2.9.5987.exe#/dl.7z...(8.4 KB) done
checking hash...hash check failed for https://miktex.org/download/ctan/systems/win32/miktex/setup/miktex-portable-2.9.5987.exe#/dl.7z. expected: b6773ba988007a88c361f63d27833e63fefdb8011238f0ca843135a3c4ffded9, actual: d0367fbd968123bacf00247b3c5ba1067a47f16538196cef2eba1a8a7e7927e5!

Thanks!

The download URL was broken (see 048e9364b984a66c1235548992dba3d1c4b891d9). It's fixed now, so you need to run scoop update;scoop uninstall latex;scoop install latex.
Thank you for reporting the problem. We could use your help if you'd like to consider submitting a manifest patch via pull request.

 scoop update; scoop uninstall latex; scoop install latex
updating scoop...
updating extras bucket...
updating versions bucket...
scoop was updated successfully!
uninstalling latex (2.9.5987)
latex was uninstalled
installing latex (2.9.5987)
downloading http://wbc.upm.edu.my/tex-archive/systems/win32/miktex/setup/miktex-portable-2.9.5987.exe#/dl.7z...(188.6 MB) done
checking hash...hash check failed for http://wbc.upm.edu.my/tex-archive/systems/win32/miktex/setup/miktex-portable-2.9.5987.exe#/dl.7z. expected: b6773ba988007a88c361f63d27833e63fefdb8011238f0ca843135a3c4ffded9, actual: 56ad665b96ceeae63d60ec0c00c05a43ee1c461113b4b5f60e8bc05be89f5cf5!


Fix high memory usage in python when initializing stack_search

Doesn't seem to be causing a problem anymore


Update gemspec

Pull Request Test Coverage Report for Build 726

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 95.821%

Totals

Change from base Build 725:
0.09%

Covered Lines:
321

Relevant Lines:
335

💛  - Coveralls

Pull Request Test Coverage Report for Build 726

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 95.821%

Totals

Change from base Build 725:
0.09%

Covered Lines:
321

Relevant Lines:
335

💛  - Coveralls


engines: Add XTS, OFB and CFB AES algorithm for use with openssl speed

Based on a PR for cryptodev-linux this change allows to use openssl speed
with HW accelerated XTS AES algorithms that are exposed through
cryptodev-linux.
Without this patch there is an error: EVP_CipherInit_ex failure when trying
to run openssl speed -evp AES-128-XTS when the algorithm is present with
openssl engine -c -t.
Signed-off-by: Daniel Kestrel<EMAIL_ADDRESS>This PR requires another PR in cryptodev-linux.

It is quite unclear to me whether this is a bug fix or not and what are the ramifications of the change.
We would also need a CLA signed. Although the change could be also considered as CLA: trivial.

I have sent in the cla with the email address from the commit, but I saw<EMAIL_ADDRESS>was mentioned, but I don't have access to that mail address and have not mentioned it in the cla.
@t8m I have converted the lantiq crypto hardware deu driver to skcipher and have implemented the xts algorithm for the lantiq hardware and for aes xts performance/regression tests I had to use cryptsetup benchmark because openssl with cryptodev-linux did not support aes xts. For other algorithms I have used openssl speed -evp so I thought adding xts to openssl would be a good idea. Thats probably not a bug.
In the mean time I have also managed to get AES OFB and AES CFB to work, but the change is a couple of lines more than for XTS.

You'll need to set up your user information in git to get the correct email address.
I've not seen your CLA come through for some reason.

This PR has the label 'hold: cla required' and is stale: it has not been updated in 30 days. Note that this PR may be automatically closed in the future if no CLA is provided.  For CLA help see https://www.openssl.org/policies/cla.html


Unable to get runners to register using GHES 3.3rc1

Describe the bug
I'm attempting to deploy this using EKS in AWS and a GHES 3.3rc1 instance. I can see in the actions-runner-controller log that it's unable to update the registration token.
Relevant log output from the actions-runner-controller pod:
2021-11-15T22:29:03.500Z	DEBUG	controller-runtime.manager.events	Warning	{"object": {"kind":"Runner","namespace":"default","name":"k8s-runner-deployment-2kxgw-6r6g2","uid":"7d84ab88-c111-459b-abb2-b46350239a9c","apiVersion":"actions.summerwind.dev/v1alpha1","resourceVersion":"60543"}, "reason": "FailedUpdateRegistrationToken", "message": "Updating registration token failed"} 2021-11-15T22:34:31.198Z	ERROR	actions-runner-controller.runner	Failed to get new registration token	{"runner": "k8s-runner-deployment-2kxgw-6r6g2", "error": "failed to create registration token: Post \"https://ec2-3-238-43-81.compute-1.amazonaws.com/api/v3/orgs/harkonnens/actions/runners/registration-token\": x509: certificate signed by unknown authority"} github.com/actions-runner-controller/actions-runner-controller/controllers.(*RunnerReconciler).Reconcile 	/workspace/controllers/runner_controller.go:189 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler 	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:298 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem 	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:253 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2 	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:214
Checks

[ ] My actions-runner-controller version (v0.x.y) does support the feature
[ ] I'm using an unreleased version of the controller I built from HEAD of the default branch

To Reproduce
Steps to reproduce the behavior:

Launch GHES 3.3.rc1 instance.
Create test org in GHES
Launch EKS cluster in AWS.
Enable Actions in the GHE instance and then create the PAT with the appropriate scope.
Install cert-manager in EKS cluster.
Create actions-runner-system namespace.
Create secret for controller-manager with the PAT value.
helm upgrade --install -f values.yml --namespace actions-runner-system --wait actions-runner-controller actions-runner-controller/actions-runner-controller
kubectl set env deploy actions-runner-controller -c manager GITHUB_ENTERPRISE_URL=https://<public DNS hostname of the ec2 instance) --namespace actions-runner-system
Deploy my runnerdeployment.yml into EKS which has the org in it that I created in step 2.
Deploy my horizontalrunnerautoscaler.yml into EKS.
Check to see if the runner now appears in the org's Actions settings(it does not).

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

Controller Version - I'm not sure. I assume it's pulling the latest release(0.15) but possibly not?
Deployment Method - Helm
Helm Chart Version [e.g. 0.11.0, if applicable]

Additional context
Add any other context about the problem here.

https://github.com/actions-runner-controller/actions-runner-controller/issues/712#issuecomment-892242319

@toast-gear Thank you for the reply. I did read through the other issues and saw that someone was able to do this but didn't provide any instruction on how exactly it was done. And it's not documented in this repo. What I'm trying to do seems fairly standard in that any customer using GHES and trying to implement this would be doing the same and we would want to have this documented. Can you help me in defining the steps here that need to be done to get the certificate chain added into the controller? I'm happy to get a PR submitted to update the documentation if we can determine what exactly needs to be done.
I also noticed that the documentation in the README.md seems to be incorrect for GHES. It states that the following must be executed to be able to properly point the actions-runner-controller to your GHES instance.
kubectl set env deploy controller-manager -c manager GITHUB_ENTERPRISE_URL=<GHEC/S URL> --namespace actions-runner-system
There is no 'controller-manager' deployment and instead the deployment is 'actions-runner-controller'.

The controller image is based on distroless and the code in written in Go. I assume you just do a custom build of the controller and add CA in a location Go looks for them:
https://stackoverflow.com/questions/40051213/where-is-golang-picking-up-root-cas-from/40051432#40051432
https://stackoverflow.com/questions/52636213/docker-distroless-image-how-to-add-customize-certificate-to-trust-store

@toast-gear Thanks again for the feedback on this.
So here's what I've tried so far and I'm still having issues with the runners connecting to the GHES instance.

Launch GHES 3.3.rc1 instance.
Create test org in GHES
Launch EKS cluster in AWS.
Enable Actions in the GHE instance and then create the PAT with the appropriate scope.
Install cert-manager in EKS cluster.
Create actions-runner-system namespace.
Create secret for controller-manager with the PAT value.
I've checked internally here and since I'm using a self-signed certificate for GHES, that certificate is contained in /etc/haproxy. There's ssl.crt and ssl.crt+key. I've taken ssl.crt+key and used 'kubectl create secret from file' to generate a secret called "ghecert" that contains the filename ghe.crt and the contents of ssl.crt+key in the actions-runner-system namespace.
I've cloned this actions-runner-controller repo so that I can modify the deployment.yaml as follows:
       volumeMounts:      - mountPath: "/etc/actions-runner-controller"        name: secret        readOnly: true      - mountPath: /tmp        name: tmp      - mountPath: /tmp/k8s-webhook-server/serving-certs        name: cert        readOnly: true      - mountPath: /etc/ssl/certs        name: ghe-cert        readOnly: true

and
      volumes:       - name: secret         secret:           secretName: {{ include "actions-runner-controller.secretName" . }}       - name: cert         secret:           defaultMode: 420           secretName: {{ include "actions-runner-controller.servingCertName" . }}       - name: ghe-cert         secret:           secretName: ghecert       - name: tmp         emptyDir: {}

Deploy the helm chart from my local copy of it. helm upgrade —install -f values.yml -n actions-runner-system actions-runner-controller ./actions-runner-controller
kubectl set env deploy -n actions-runner-system actions-runner-controller -c manager GITHUB_ENTERPRISE_URL=https://<hostname of my ec2> --namespace actions-runner-system
Attempt to point Go to the cert dir kubectl set env deploy -n actions-runner-system actions-runner-controller -c manager SSL_CERT_DIR=/etc/ssl/certs --namespace actions-runner-system
I then deploy the runnerDeployment and HorizontalRunnerAutoscaler.

This is the error I see in the actions-runner-controller manager container:
2021-11-17T20:01:40.154Z	ERROR	actions-runner-controller.runner	Failed to get new registration token	{"runner": "k8s-runner-deployment-x56pz-d7s89", "error": "failed to create registration token: GET https://<ec2- hostname>/api/v3/orgs/harkonnens/actions/runners/registration-token: 404 Not Found []"} github.com/actions-runner-controller/actions-runner-controller/controllers.(*RunnerReconciler).Reconcile 	/workspace/controllers/runner_controller.go:286 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler 	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:298 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem 	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:253 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2 	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:214 2021-11-17T20:01:40.154Z	ERROR	controller-runtime.manager.controller.runner-controller	Reconciler error	{"reconciler group": "actions.summerwind.dev", "reconciler kind": "Runner", "name": "k8s-runner-deployment-x56pz-d7s89", "namespace": "default", "error": "failed to create registration token: GET https://<ec2 hostname>/api/v3/orgs/harkonnens/actions/runners/registration-token: 404 Not Found []"} sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem 	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:253 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2 	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:214 2021-11-17T20:01:40.154Z	DEBUG	controller-runtime.manager.events	Warning	{"object": {"kind":"Runner","namespace":"default","name":"k8s-runner-deployment-x56pz-d7s89","uid":"c4ccac4d-d351-4b7a-abb9-49a4e2c020da","apiVersion":"actions.summerwind.dev/v1alpha1","resourceVersion":"47729"}, "reason": "FailedUpdateRegistrationToken", "message": "Updating registration token failed"}
And in the runner pod logs:
`Github endpoint URL https:///
mv: inter-device move failed: '/runnertmp/bin' to '/runner/bin'; unable to remove target: Directory not empty
mv: inter-device move failed: '/runnertmp/externalstmp' to '/runner/externalstmp'; unable to remove target: Directory not empty
mv: inter-device move failed: '/runnertmp/patched' to '/runner/patched'; unable to remove target: Directory not empty
Configuring the runner.

|        ____ _ _   _   _       _          _        _   _                      |
|       / () || | | | | |_      / \   | |() ___  _ __  ___      |
|      | |  | | __| || | | | | ' \    / _ \ / | | |/ _ | ' / |     |
|      | || | | ||  _  | || | |) |  / ___ \ (| || | () | | | _ \     |
|       _||_|| ||_,|./  /_/   __|_||_/|| ||_/     |
|                                                                              |
|                       Self-hosted runner registration                        |

Authentication
The SSL connection could not be established, see inner exception.
Configuration failed. Retrying`
So obviously the SSL connection is still an issue but I'm not quite sure where I'm going wrong here. I don't know if the ssl.key+crt(contains the cert and the private key) isn't sufficient and I'm needing a bundle instead, or if it's not being mounted and accessed properly on the manager container.
Tagging @exploiz65 to see if they were able to get this working based off this issue.

@toast-gear
The other question I have is whether or not the ca bundle needs to be presented just to the controller or also to the runners. Is the controller natively able to pass the certificates down to the runners when they spawn, or do we have to make that happen?

The runners will definitely needs the ca-bundle as they make API calls to GHES independent from the controller. I believe the controller would also need the bundle as it communites with GHES to create tokens. Please do test and report back because whilst we probably can't provide a guide as we don't have a GHES environment we can link to dicussions.
The runners are ubunut based so you should be able to test the runner side fairly easily.

@toast-gear Got this working today with some help from our Actions team. You were indeed correct that both the runners and the controller needed the certs. I'm going to test out the procedure again this afternoon and iron out the steps. What's the best means of getting a guide put together? Do you want me to PR against the README.md or do you want to start a separate document for the GHES implementation?
It required me to edit both the actions-runner-controller/templates/deployment.yaml as well as the runnerdeployment.yml I used. In these, I needed to create volumes and volume-mounts in both of them for the certificate of my GHES appliance which I stored as a secret in the cluster. So there are several steps involved in getting this to work and don't want to bloat that smallish GHES section in the README.md.

I've got the process written up in a private gist for now which I can share with you or anyone else until we can get it tested out and find a more suitable location for it.

Awesome news! I think having a write up as a show and tell entry in the dicussions will be a good starting point.

@toast-gear Done!

I'm going to consider this resolved and close the ticket now that we have a guide.


SteamTradeMatcher integration

Now when we have EQ part done, it would be really cool to add STM integration.
This is rather easy, all that is needed is to properly detect when to accept or decline the trade that bot receives. Currently bot accepts trades coming from SteamMasterID and trades where bot is not losing any items (donations). It should also accept trades of dupes - which is a bit hard to code, but possible to do with a bit of effort.
TODO, with rather short ETA as it's useful feature especially for main accounts.

Dupes is not so hard to find, it's just items where classid and instanceid are both the same. More complex problem is to find, if the requested and received cards are from the same game, because for this you would have to deserialize item descriptions too (that I just ignored when making trade offer sending). When you would implement this I would also suggest one more improvement that a few people asked for (because with descriptions it would be easy).

After rather a longer while, the feature I wanted to see since a long time in ASF is now completed. Go ahead and give it a try: https://github.com/JustArchi/ArchiSteamFarm/releases/tag/<IP_ADDRESS>
Fast doc before I add proper text in the documentation:
If SteamTradeMatcher is true, bot in addition to donations and trades from SteamMasterID will also accept trades that are valid in terms of SteamTradeMatcher.
Trade is valid in terms of STM if:

Both parties receive same amount of items
Trade consists only of items from the same game
Trade consists only of steam trade cards

Possible TODO for future:

Allow STM integration also for items different than trade cards, that can be done as I have EType of Item implemented already, it's only a matter of adding all possible rules and some checks.
Check our own inventory to decide if trade is indeed worth it for us, in addition to checking if it's valid in terms of STM.

Still, quite a big milestone has been done, so feel free to test it and give feedback. I think I covered all possible steam fuckups, abuses and other unwanted scenarios properly, so bot will not accept trades we don't want, but I can't assure it without tests and feedback - it works for me.
Have fun.

And bugfix: https://github.com/JustArchi/ArchiSteamFarm/releases/tag/<IP_ADDRESS>
Allow STM integration also for items different than trade cards, that can be done as I have EType of Item implemented already, it's only a matter of adding all possible rules and some checks.

Done with foil cards (price of other items vary and we might not want to trade them automatically)

Last one, I promise :+1:
https://github.com/JustArchi/ArchiSteamFarm/releases/tag/<IP_ADDRESS>
Should be absolutely bugless now.

Added new bot config property called SteamTradeMatcher with default value of false. As always, you can find more information in the wiki.

Don't forget to add information to wiki.

Documentation is always done as last stage, when I'm done with adding logic and precising how it works. You should never expect documentation of things in work-in-progress state, especially if they didn't make it's way to stable release.

Final version of ASF STM integration is now ready: https://github.com/JustArchi/ArchiSteamFarm/releases/tag/<IP_ADDRESS>
This is the version I've been testing since some time. It has everything I wanted to see implemented, including not only check if STM trade is valid, but also if it's worth for us. Trades are done for steam cards and foils, as value of other items may vary and we might look into those trades manually.
I think it's bugless for now, I fixed all bugs I could spot. I'm leaving this issue open in case somebody else spots a potential bug or something interesting regarding that feature - it'll get closed with stable release (which will happen when I'm sure everything is working as supposed to, so probably a few more days).


Hide top navigation bar when in an iFrame

TODO: decide whether we also want to hide the search, chat, notifications and profile links
Fixes https://github.com/Hylozoic/hylo-evo/issues/912

no longer needed because layoutFlags=mobileSettings now does exactly this from the URL!


Meaning of padding_idx in get_sinusoid_encoding_table?

Hi 👋
Thank you for this repository.  I noticed that padding_idx appears to be hard-coded in these lines, and in my project I have some special handling around padding, But I’m having a hard time following exactly what is happening here.  Is it intended that padding_idx is hard-coded to 0?  Or should it be set to Constants.PAD?  How should I decide what to set this value to?  It appears to set the 0th embedding index to zeros...  then it also looks like the positional encoding is similar to list(range(1, max_seq_len+1))... which I’m guessing is then filled with Constants.PAD at positions outside the src/tgt sequence?  Does that sound right?  So then it really should be set as padding_idx=Constants.PAD?
https://github.com/jadore801120/attention-is-all-you-need-pytorch/blob/20f355eb655bad40195ae302b9d8036716be9a23/transformer/Models.py#L71
https://github.com/jadore801120/attention-is-all-you-need-pytorch/blob/20f355eb655bad40195ae302b9d8036716be9a23/transformer/Models.py#L117

Same question here. I think the padding_idx should be the position of the last word in one sentence. The current syntax makes the first position to be all zeros. I recommend padding_idx to be an array of all the real sentence lengths.

I think padding_idx=0 is the purpose of letting PAD positions of sentences equal to zeros, because the PAD positions have no efftect. The PAD positions are always encoded to zeros.
https://github.com/jadore801120/attention-is-all-you-need-pytorch/blob/20f355eb655bad40195ae302b9d8036716be9a23/dataset.py#L22

Hi all, I think it is actually useless, so I remove it now.
Thanks for point out!


docs: params is async on async layout

Since NextJS 15 the params props is async on async layout.
If we don't specify the async an error is raised in console in dev mode
Error: Route "/[locale]" used `params.locale`. `params` should be awaited before using its properties. Learn more: https://nextjs.org/docs/messages/sync-dynamic-apis
    at createParamsAccessError (node_modules/.pnpm/next@15.0.3_react-dom@19.0.0-rc-66855b96-20241106_react@19.0.0-rc-66855b96-20241106__react@19.0.0-rc-66855b96-20241106/node_modules/next/dist/src/server/request/params.ts:467:9)
    at getMessage (node_modules/.pnpm/next@15.0.3_react-dom@19.0.0-rc-66855b96-20241106_react@19.0.0-rc-66855b96-20241106__react@19.0.0-rc-66855b96-20241106/node_modules/next/dist/src/server/create-deduped-by-callsite-server-error-logger.ts:46:20)
    at warnForSyncAccess (node_modules/.pnpm/next@15.0.3_react-dom@19.0.0-rc-66855b96-20241106_react@19.0.0-rc-66855b96-20241106__react@19.0.0-rc-66855b96-20241106/node_modules/next/dist/src/server/request/params.ts:445:4)
    at syncIODev (node_modules/.pnpm/next@15.0.3_react-dom@19.0.0-rc-66855b96-20241106_react@19.0.0-rc-66855b96-20241106__react@19.0.0-rc-66855b96-20241106/node_modules/next/dist/src/server/request/params.ts:403:10)
    at LocaleLayout (src/app/[locale]/layout.tsx:32:65)
  30 | }>;
  31 |
> 32 | export default async function LocaleLayout({ children, params: { locale } }: Props) {
     |                                                                 ^
  33 |   // Ensure that the incoming `locale` is valid
  34 |   if (!routing.locales.includes(locale as string)) {
  35 |     notFound();

see: https://nextjs.org/docs/app/building-your-application/upgrading/version-15#asynchronous-layout

Thanks for the PR! There's already one open at https://github.com/amannn/next-intl/pull/1089 though, I'm currently waiting for upstream bugs in Next.js 15 to be fixed before broadly updating docs.

Sorry I miss this PR. I'll close this one


Client Allocation Request for: ABC Inc.

Client Allocation Questions
Core Information

Name: ABC Inc.
Website / Social Media: https://foo.com, (@foo, Twitter)
Region: Oceania
DataCap Requested: 192 GiB
Addresses to be Notarized: f1495978707
Notary Requested: Claudia Richoux

This user’s identity has been verified through filplus.storage


Save in temp file before replacing destination file

This way, in case of a crash during saving,
the current destination file will not become blank or corrupt.
Idea here:
http://qlcplus.org/forum/viewtopic.php?f=5&t=9227&p=40548&hilit=crash+while+saving#p40548

Neat idea, but it would be nice to understand what happened to the user that got a crash during the save process. Actually that was the first case I saw in 3 years.
Usually it happens the other way around: QLC+ crashes when loading a project.
A more generic approach would be like what QtCreator does: as long as you edit a file (and don't save it) the program creates a .autosave file for you.
If the program explodes or the power goes down, that's your backup point.
I don't know the save policy they adopt. could be based on the number of changes or time-based. Don't know. Surely we cannot afford to hook such feature to the Doc::setModified method.
Ideas ?

Neat idea, but it would be nice to understand what happened to the user that got a crash during the save process. Actually that was the first case I saw in 3 years.

It never happened to me either, but it could easily happen: When saving, the whole QLC+ instance is read through. 1 single issue may cause a crash.
I think both ideas are complementary.
It would be nice to have an autosave feature.
It would also be nice to no break the target file if QLC+ crashes while saving.

I gave a second thought to this and I believe the autosave can cover both cases.

When Doc::setModified is called, a timer is started, with one minute timeout, recurring every minute.
After one minute a .autosave file is created. If there are save issues and QLC+ crashes, you will loose one minute of work maximum.
If more setModified are called and the timer is already on, no action is taken.
If the user manually saves the project, the timer is killed and the autosave file is removed.

How does this sound ?

I agree with david that those two are quite independent. For saving, it's safer to create the new file first and destroy the original only after the new one is created completely.
With this approach the recovery is to delete excess files, while with .autosave, you have to rename the proper file to proper name.
Problems I see is that it will not keep the created timestamp (but that can be handled separately).
That said, I agree that auto save is useful as well.

The code in this commit seems like repeating the same pattern. Itmay be worth to create helper method (e.g. in qlcfile).


JPA mapping values coverage

The aim of this PR is to cover JPA convert annotation, motivated by this issue
We have created a new field over the Book entity called comments. The type of this field is a mutable type (a Map), and is converted to a JSON String through a JPA convert annotation.

BookRepositoryTest remove unused import org.hibernate.annotations.SQLUpdate;


Fix missing package in Docker build

It appears that in Alpine 3.12, the man package was renamed to mandoc.
To prevent similar issues from re-occurring, I also added version constraints to the images referenced in the Dockerfile.

Thanks!


Error 7 Days to Die

Hi
Y have proble when start server:
Kestouf@ns3554546:~/7daytodie$ ./sdtdserver start
[ .... ] Starting sdtd-server: session not found: sdtd-server
[ FAIL ] Starting sdtd-server: Unable to start
[ FAIL ] Starting sdtd-server: Unable to start : Tmux error:
Command
tmux new-session -d -s "sdtd-server" "./7DaysToDieServer.x86 -logfile /home/Kestouf/7daytodie/log/server/output_log__2016-07-03__18-58-44.txt -quit -batchmode -nographics -dedicated -configfile=/home/Kestouf/7daytodie/serverfiles/sdtd-server.xml"
Error
create session failed: ./7DaysToDieServer.x86 -logfile /home/Kestouf/7daytodie/log/server/output_log__2016-07-03__18-58-44.txt -quit -batchmode -nographics -dedicated -configfile=/home/Kestouf/7daytodie/serverfiles/sdtd-server.xml: Exec format error
Fix
No known fix currently. Please log an issue.
https://gameservermanagers.com/issues
On forum of steam :
https://steamcommunity.com/groups/linuxgsm/discussions/0/358416640397539877/
Have you idea?
Thx

Please, go back to Steam forum, but provide relevant information following those instructions http://steamcommunity.com/groups/linuxgsm/discussions/0/458604254471755996/


#5 fix uncaught ReferenceError

Uncaught ReferenceError: SRS_CLASS is not defined

As I don't have write access to your repo, you have to merge the PR ;-)

Thank you!


fix big sur b3 paths

When installing a package via MDM on Big Sur, the behavior of arguments are different:
A manual install will show something like this for $0/$1/$2/$3
/tmp/PKInstallSandbox.l3yeSQ/Scripts/com.uber.pkg.mdm.OffRLT/postinstall
/Users/erikg/Desktop/mdmtest-1.0.pkg
/
/

whereas a MDM installation will show something like this:
/Library/InstallerSandboxes/.PKInstallSandboxManager/16D65155-E119-4290-913D-9C772D60D921.activeSandbox/Scripts/com.uber.pkg.mdm.Wp0Zrx/postinstall
/var/folders/zz/zyxvpxvq6csfxvn_n0000044000011/C/com.apple.appstore/9ABF6C5F-1FA8-41FE-B73D-1435E3B7A4A0/b58ebfa3-3f2c-48db-97a7-6994164585d7.pkg
/System/Volumes/Data
/System/Volumes/Data

This means that for the launch agents and daemons, the path could be:
/Library/LaunchAgents and /Library/LaunchDaemons pre beta 3
post beta 3 /System/Volumes/Data/Library/LaunchAgents and /System/Volumes/Data/Library/LaunchDaemons

I've confirmed this fixes the issue for big sur.


[Publishing] [Java] Blog for GCSToMongo

Publish a blog on exporting data from GCSToMongo using Dataproc Serverless (Java)

Submited for review https://medium.com/google-cloud/importing-data-from-gcs-to-mongodb-using-java-dataproc-serverless-6ff5c8d6f6d5


Pins board function argument missing

Describe the bug
The .py file generated after using function does not have allow_pickle_read=True option set, which is needed to write models as pins
To Reproduce
Run vetiver.vetiver_write_app function to generate the file
vetiver_write_app(
        board,
        "username/modelname",
        file="superbowlads.py"
)

Expected behavior
allow_pickle_read=True should be set by default
Desktop (please complete the following information):

OS: Ubuntu
Browser: Chrome
Version: 0.1.3

CC: @xuf12

This part of the app file is coming from [board_deparse()](https://github.com/rstudio/pins-python/blob/c97b2a49da2f7a84e48f57faf6f739e64ef8b1fd/pins/constructors.py#L17) function in pins. I wonder if this is a vetiver-specific issue, or makes sense to be part of pins? WDYT @machow? I'm happy to help with a PR in pins if that seems appropriate!

Ah, thanks for catching--that makes to fix this in pins! I opened an issue to track!:  https://github.com/rstudio/pins-python#123

Merged in pins-python, so closing here.

released to pypi as pins v0.2.1!


[BUG] - Image crop not work got the Full size image in Android 11

🚨🚨 Before open the ticket please check if you can reproduce the bug in the sample code

Lib Version [e.g. 1.1.0]
3.3.5

Describe the bug
When I am open cmera and gallery from both place crop not work means i am getting original size image in Android 11
I am using java Code :
Uri tempUri = Uri.fromFile(new File(path));
CropImage.activity(tempUri)
.setGuidelines(CropImageView.Guidelines.ON)
.setBorderLineColor(Color.parseColor("#FF7A2A"))
.setGuidelinesColor(Color.parseColor("#696969"))
.setAllowRotation(true)
.start(mActivity);
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Media
Please add screenshots and/or screen recordings to help explain your problem.
We cannot help without more information
Smartphone (please complete the following information):

Device: [e.g. Pixel 3XL]
OS: [e.g. iOS8.1]

Additional context
Add any other context about the problem here.

When you opened this issue you said was version 3.3.5 of this library, but you just update now.
So this issue is not valid and I will close it, please open issues with the complete information so I can help better =)

@Gauravyadav101 you have many unnecessary code in your sample
Please check the Java Sample implementation we have and use the library like suggested in this file.
Suggestion to use the method startCameraWithoutUri() as North, where you let the library pick the image and return the value
private final ActivityResultLauncher<CropImageContractOptions> cropImage =
            registerForActivityResult(new CropImageContract(), presenter::onCropImageResult);

Where presenter::onCropImageResult is how you handle the answer, like:
public void onCropImageResult(@NonNull CropImageView.CropResult result) {
        if (result.isSuccessful()) {
            view.handleCropImageResult(result.getUriContent().toString().replace("file:", ""));
        } else if (result.equals(CropImage.CancelledResult.INSTANCE)) {
            view.showErrorMessage("cropping image was cancelled by the user");
        } else {
            view.showErrorMessage("cropping image failed");
        }
    }

etcs


Fix craftax imports

I made a breaking change to the Craftax folder structure in v1.2.0, so the imports now require a craftax. prefix.

sorry for the late reply, I will review this PR asap. thx!


[doc issue] example not runnable; no manifest.json

Issue description
Hello,
during implementation of the first step of the getting started I encountered an issue.
Running this example with the given package.json results the following error:

Error Message:
Could not find required manifest.json for project sap-m-tutorial-quickstart-01: Could not find resource /manifest.json in project sap-m-tutorial-quickstart-01`

Serving the manifest.yaml would solve this issue :-)
Feedback Type (Optional)
content gaps
Page Title on SAP Help Portal (prefilled)
Step 1: Ready...
Page URL on SAP Help Portal (prefilled)
https://github.com/SAP-docs/sapui5/blob/main/docs/03_Get-Started/step-1-ready-851bde4.md

Hi @RobertFent, thanks for your contribution. We'll look into this and get back to you.

Hi @RobertFent, thanks for opining this issue. We are already working on a fix for this in back log item CPOUI5FOUNDATION-713. I'll update this issue here when the fix is available.

Quickstart tutorial has been fixed from 1.120.1 / 1.121

https://people.sap.com/robertfent


Async/Lazy load photo

dev
GitHub Project

Main GitHub Project ticket

Code reviewers

[x] @iuriikhrystiuk

Second Level Review

[ ] @sand0

Summary of issue
Photos was loading with all users data and that was consuming a lot of time
Summary of change
Added posibility of photo lazy loading
If photo haven't been found than it will be replaced by default photo
Testing approach
Tested manually
CHECK LIST

[ ]  PR is reviewed manually again (to make sure you have 100% ready code)
[ ]  I've checked new feature as logged in and logged out user if needed
[ ]  PR meets all conventions

So, if we ignore all PhotoUrl when do mapping, do we use that property in any place? If not I guess we should delete it at all

done.


Application gets stuck while scrolling speedily in UITableView for the first time

I have list of 500-600 records in a UITableView and when I scroll speedily up and down for the first time, application gets stuck and I can not do anything.  If I provide nil as URL and use placeholders instead, it works fine.
I am running the app in iPad 2 having iOS version 5.1.1. Unable to replicate the same in simulator

@agiokas had the same issue a while ago ... are you using the image you downloaded from downloadImageWithURL:options:progress:completed:'s completed block ? If so, make sure you dispatch to the main queue before using using the image ;)

solution for getting stuck tableview while scrolling .If you are using image from url then use it
[cell.imgView setImageWithURL:[NSURL URLWithString:[NSString stringWithFormat:@"%@",[dict objectForKey:@"profile_pic"]]] placeholderImage:[UIImage<EMAIL_ADDRESS>


Changes to contributing + readme formatting

Hi, I noticed that there wasn't much guidance on contributing to the project.
There's just a few changes, but moving to a prominent place will I hope encourage people to contribute! Hope this is ok and helpful to you, it's a great plugin.

Hello, no worries - changes submitted


Show marker for each single event in specific events page

check commit #https://github.com/sopra-fs23-group-07/sopra-fs23-group-07-client/commit/d239665fae7bb94b6121e09599d24e5d678c6c18

#d239665

commit d239665


Add hix_bulk command

Short description

This pr adds a hix_bulk command which saves the hix store for all pages for which the score is missing.
Proposed changes

Add hix_bulk management command

Side effects

/
Resolved issues

Fixes: #2101

Pull Request Review Guidelines

Do we need a test for the new command management in tests/core/management/commands ?

Do we need a test for the new command in tests/core/management/commands ?

Would definitely be cool, yes, but in sight of the deadline, I guess it would be fine to merge this first and hand in the tests later :see_no_evil:


Feat:header content flowing outside the card in mobile

Describe the feature
Feat:header content flowing outside the card in mobile
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Hello @SUGAM-ARORA please assign this issue to me under gssoc 24

@kapilG0 Issue assigned to you

@SUGAM-ARORA It's been a month I think author is not working on it anymore can i work on this I am gssoc'24 participants


v2-beta various bugs

Issue type: bug report
**Python version: 2.7
**NetBox version: v2-beta
During installation I had to fix the following things

pytz is missing from requirement file
pyasn1 is missing from requirement file
had to add libjpeg-dev and python-pyparsing packages
python-ldap package is not installed by default (could be my installation)
ldap is not working for me with the same config i used as for 1.8.4.

pytz is missing from requirement file
pyasn1 is missing from requirement file

These are not direct requirements of the project and don't need to be listed.

had to add libjpeg-dev and python-pyparsing packages

This should not be necessary. If you believe this is a bug, please open a bug report specifically for this including the steps needed to reproduce as indicated in out contributing guidelines.

python-ldap package is not installed by default (could be my installation)

The LDAP package is not installed by default because not everyone uses LDAP for authentication.

ldap is not working for me with the same config i used as for 1.8.4.

Please post to the mailing list if you require configuration assistance.


Brainscanning PSOS

Codecov Report

Merging #24 (0cae41a) into master (93d116b) will decrease coverage by 0.12%.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##           master     #24      +/-   ##
=========================================
- Coverage    3.89%   3.76%   -0.13%
=========================================
  Files          11      12       +1
  Lines        1027    1062      +35
=========================================
  Hits           40      40
- Misses        987    1022      +35

Impacted Files
Coverage Δ

src/InteractiveChaos.jl
6.34% <ø> (ø)

src/chaos/brainscan.jl
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


[BUG] Change PIN and PUK retry counts for PivSession Incorrectly Set

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When calling the TryChangePinAndPukRetryCounts(admin key, pin, count, count, out var x), it is not set as expected by the passed value. Instead, it is being set to 0. Tested with USB C and USB A tokens.
Expected Behavior
Retry count should be properly set.
Steps To Reproduce

Reset the PIV session
Call the change PIN and PUK count with default credentials with retry more than 1
Verify the PIN with incorrect PIN -> fails and claims no retries left on first attempt

Version
1.11.0
Version
5.7.1 and 5.4.3
Anything else?
Tested on multiple tokens

Tested on Both MacOS and Linux. Did not test on Windows

Hi guys!
You mean like this?

Yes! We are calling it the exact same way but with different retry values (3, 3).

Ok, strange. As you can see it passed for me on a 5.4.3 key.
Are you getting any interesting logs you can share?

We are using VerifyPin() instead and passing the PIN via a KeyCollector, so that's the only difference I can notice. It says that it uses TryVerifyPin under the hood. Let me know if this is useful information!

I just now looked at the source code. The way we setup the KeyCollector means that calling VerifyPin() would block the PIN if incorrect.
Sorry for the bad issue.


[Question] FLARE-VM AMI?

I wanted to throw this out there to gauge interest. I'm developing the cloud lab lecture material for PMAT and part of the setup is to have the student create their own FLARE-VM AMI and use Terraform to provision and tear down their malware analysis lab.
That got me thinking - is there any interest in maintaining an official FLARE-VM AMI that's publically available on the AMI catalog?

Hmm interesting idea! I'd be interested in a GCP option 😄 Do you have any experience in that?

I don't have any experience with GCP, unfortunately.
I've created a FLARE-VM AMI and made it publically available if anyone wants to check it out for evaluation purposes. It's built on Windows Server 2022 and seems to work great! It's a t2.medium so it costs about $0.04 USD/hour to run the instance and probably about $3/month to maintain the AMI.
ami-0fa27ee2696dde5c9

Hey HuskyHacks, which AWS region is that being hosted on? I can't find it on Asia Pacific.

@sshakoor98 the AMI is on us-east-1. You have to host AMIs by region and it would get a little expensive to host across the different regions, so I'm keeping it to us-east-1 for now.


Implement 'coastal realization' formulation

Per https://github.com/NOAA-OWP/ngen/issues/547#issuecomment-1896392842

Sketching out notes for how input variables will come from the forcings engine to feed into SCHISM:
SCHISM has three BMI grids that its inputs are defined over:

Variables defined at every node in SCHISM's mesh
Lateral flow defined at elements along the coastal boundary
Water level defined at nodes along the open-water boundary

All of these are covered by bmi_grid_{size,x,y}, and if SCHISM is configured appropriately, it'll provide geographical coordinates in degrees of longitude and latitude for x and y.

The input variables defined on grid 1 at all nodes seem pretty straightforward to address with the forcings engine as I understand it:

Surface pressure SFCPRS
Temperature TMP2m
Wind velocity UU10m, VV10m
Specific humidity SPFH2m

One potential hitch I've seen suggested here is that the forcings data may not extend as far off-shore as the mesh. I think for a first cut, we can probably just use a nearest-neighbor value until we integrate a secondary source of data with broader/supplemental coverage.

Q_bnd (m^3 / s) is the lateral inflow in grid 2 coastal elements, that we'll have to carefully digest from t-route's output at downstream/coastal/terminal nexuses.

Precipitation averaged over specific elementsRAINRATE (kg / m^2 s), confusingly defined over the same grid 2 of elements along the on-shore coastal boundary. I've asked Jason about whether it should actually be over the whole domain instead.

Open boundary water level ETA2_bnd defined for grid 3 of nodes along the open-water boundary. This is coming from output of another simulation system. I'm not at all sure how we're getting this one yet. For an initial "get things running", we can probably pin this at a constant until we're prepared to wire that up.

From discussion with Jason

I'm going to recode RAINRATE to an element grid over the whole domain mesh
We talking about what happens to precipitation over land, and whether it should pass through an LSM like Noah or other catchment model code to partition water that does or doesn't become part of the coastal waterbody in a given step
For expedient simplicity, we'll defer any digestion of precipitation over land from Noah, and just force with RAINRATE uniformly for now.
Lake Champlain is a special case for the ETA2_bnd forcing, because it doesn't actually have an off-shore water level estimate like the Great Lakes or the oceans from circulation models (FVCOMM or STOFS). We think it may be fine without, since the SCHISM code handles an absence of files providing that variable.


FIX: import_gds_file

@SMoraisAnsys I committed the proposed changes. As long as there is an input GDS (even without map or tech file), the translator should be ran so I didn't add the exception RuntimeError. Let me know if that makes sense.


BREAKING-CHANGES has a mismatched format

Bug report
What is the current behavior?
I get the following error:
COMMIT MESSAGE FAILED CHECKS: Breaking changes must be denoted by one of {'BREAKING-CHANGE', 'BREAKING CHANGE'} in uppercase followed by ': ' and a description e.g. 'BREAKING CHANGE: Change MyPublicClass interface'; received 'BREAKING-CHANGE: Uncategorised commits contain breaking changes including the use of tabulate as a dependency and refactor to use stream rather than list, as well as substantive changes to wrapping and line termination defaults'.

What is the expected behavior?
This commit check should pass, I don't see anything wrong with it?
More Information
The full commit command was:
gc -am "FEA: Set correct version for incoming updates

BREAKING-CHANGE: Uncategorised commits contain breaking changes including the use of tabulate as a dependency and refactor to use stream rather than list, as well as substantive changes to wrapping and line termination defaults"

Thanks, I'll fix this imminently


Loosen the dependency version of Kaminari (1.0.0)

Kaminari v1.0.0 is released.

https://rubygems.org/gems/kaminari/versions/1.0.0
https://github.com/kaminari/kaminari/blob/master/CHANGELOG.md#100

It seems no problem at my environment. (Ruby 2.3.3, Rails <IP_ADDRESS>)

The test with Rails 4.0 has failed.
https://travis-ci.org/sferik/rails_admin/builds/190896753
I propose to dropped support for Rails 4.0.
These are the reasons below.

Rails 4.0 has not been maintained.
Kaminari 1.0.0 supports Rails 4.1, 4.2, 5.0, 5.1. In other words 4.0 is not supported.

How do you think about this?

There are other approaches. For Rails 4.0, use version of Kaminari < 1.0.0.
This approach has a small impact on existing users.
This PR has passed Travis CI with this approach.  https://github.com/sferik/rails_admin/pull/2810/commits/72f15a32eb047ef2c8ac0f3d4fa1882c33e99112
Thanks.

I prefer that approach, thanks!

I get it. Thank you for the reply and merging!


Allow reordering answer options for multiple choice questions

Description
Makes it easy to change the order of answer options for multiple choice question types (dropdown, checkbox, radio) by adding up and down buttons to move the option. For code simplicity, there is still an up button on the first option and a button option on the last option, but they don't do anything. Re-ordering the HTML elements causes Play Java to bind the form with the fields in the correct order and for the configuration to be stored correctly.
Release notes
The title of the pull request will be used as the default release notes description. If more detail is needed to communicate to partners the scope of the PR's changes, use this release notes section.
Checklist
General

[x] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[x] Created tests which fail without the change (if possible)

Issue(s) this completes
Fixes #4558

Hmm yeah I can't seem to get that working correctly with Tailwind.


ImportError: DLL load failed: The specified module could not be found.

If I run this test command
python3 -m manim example_scenes.py SquareToCircle -pl
this error occurs.

Can any one please help me how to solve this issue. thanks in advanced :)

Seems like your scipy installation is borked. Try reinstallation or use the mkl distribution https://stackoverflow.com/questions/17480779/importerror-when-importing-certain-modules-from-scipy

I reinstall scipy but the same problem remains. And tried to install numpy‑1.16.3+mkl‑cp37‑cp37m‑win_amd64.whl but it is showing an environment error

try using absolute path

It is installed using absolute path. but now it is showing this  error

I went ahead and installed manim on my windows8 installation. I was not able to replicate any of the errors. How did you installed python and manim?

I am currently using windows 10 Pro and my python version is 3.7.3
For python I just downloaded it from . and installed it. I checked my environment path. it looks ok to me.

for manim I run
python -m pip install -r requirements.txt
after installing ffmeg
Bit backstory- I  started using manim about 5 month before. every thing was working fine. But 5-6 days ago the videos were not rendering. ffmeg and python was not in my environment path.(may be windows update massed that up). Then I again installed python and ffmeg. and then the scipy issues occurred.

are you running from anaconda environment or using the system python ?
https://stackoverflow.com/questions/44537131/numpy-library-importerror-dll-load-failed-the-specified-procedure-could-not-be
https://stackoverflow.com/questions/17480779/importerror-when-importing-certain-modules-from-scipy/17511983#17511983
might not solve your problem but worth checking out.

System python.
Now I am just planning to install manim in a VM. See how that works out.


build: Add tox

Adding tox to build tooling.
Tox supports checking the package against multiple supported Python versions on th local development machine.

I split PR #92 into several pull request, so you can comment on them incrementally.
Nevertheless due to the dependencies they are still cummulative and thus hould be applied in the folloing order:
#91 > #95 > #96 > #97 > #92
If you don't like some of the features (e.g. flake8 or tox) - although it would be a pitty ;-)  - let me know and I will rebase and modify the subsequent once to fit.

I see this PR contains also pre-commit and black configuration, but no conflicts.. can I merge it?

Yes, I just rebased it.

Merging then.


You will need to merge with the latest master changes before I can merge. ;)

merged

@artemkaint you're comment says 'merged' but the master branch says different ;)

Merged as 1c8e69209269591d26c84173b30de1fd943a20fb. Thanks for your contribution!