Sulum interface no longer working with latest version.

When compiling Sulum with the latest or-tools version, I get the following error:
src/linear_solver/sulum_interface.cc: In member function ‘virtual operations_research::MPSolver::ResultStatus operations_research::SLMInterface::Solve(const operations_research::MPSolverParameters&)’:
src/linear_solver/sulum_interface.cc:607:9: error: ‘class operations_research::MPConstraint’ has no member named ‘set_activity’
     ct->set_activity(row_activity);
         ^
make: *** [objs/linear_solver/sulum_interface.o] Error 1

Is it possible that the Sulum-interface is out of sync with the headers provided in the latest sulum43 version? The file in question is probably /src/linear_solver/sulum_interface.cc

I pushed a tentative fix.
I do not have sulum installed to try it.
Can you check?

Thanks for the quick response. Just tried the latest available version and still getting the same error.
g++ -fPIC -std=c++0x -fwrapv -O4 -DNDEBUG -Isrc -Iexamples -Isrc/gen -I/home/manu/ortools/or-tools/dependencies/sources/gflags-2.1.2/include -DARCH_K8 -Wno-deprecated -I/home/manu/ortools/or-tools/dependencies/install/include     -I/home/manu/ortools/sulum43/BraunDesert/header -DUSE_SLM   -DUSE_GLOP -DUSE_BOP -I../sparsehash-1.11/include -c src/linear_solver/sulum_interface.cc -o objs/linear_solver/sulum_interface.o
src/linear_solver/sulum_interface.cc: In member function ‘virtual operations_research::MPSolver::ResultStatus operations_research::SLMInterface::Solve(const operations_research::MPSolverParameters&)’:
src/linear_solver/sulum_interface.cc:607:9: error: ‘class operations_research::MPConstraint’ has no member named ‘set_activity’
     ct->set_activity(row_activity);
         ^
make: *** [objs/linear_solver/sulum_interface.o] Error 1

Please update again, I pushed the code after the mail
Thanks
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
2015-09-30 14:48 GMT+02:00 Manuel Riel<EMAIL_ADDRESS>
Thanks for the quick response. Just tried the latest available version and
still getting the same error.
g++ -fPIC -std=c++0x -fwrapv -O4 -DNDEBUG -Isrc -Iexamples -Isrc/gen -I/home/manu/ortools/or-tools/dependencies/sources/gflags-2.1.2/include -DARCH_K8 -Wno-deprecated -I/home/manu/ortools/or-tools/dependencies/install/include     -I/home/manu/ortools/sulum43/BraunDesert/header -DUSE_SLM   -DUSE_GLOP -DUSE_BOP -I../sparsehash-1.11/include -c src/linear_solver/sulum_interface.cc -o objs/linear_solver/sulum_interface.o
src/linear_solver/sulum_interface.cc: In member function ‘virtual operations_research::MPSolver::ResultStatus operations_research::SLMInterface::Solve(const operations_research::MPSolverParameters&)’:
src/linear_solver/sulum_interface.cc:607:9: error: ‘class operations_research::MPConstraint’ has no member named ‘set_activity’
ct->set_activity(row_activity);
^
make: *** [objs/linear_solver/sulum_interface.o] Error 1
—
Reply to this email directly or view it on GitHub
https://github.com/google/or-tools/issues/93#issuecomment-144386063.

That solved it. I just had to change sulum10 to sulum43 in makefiles/Makefile.unix to make it work from there. Should I change it everywhere and submit a PR for that? @lperron

No,
I have added a new flag in Makefile.local
please add
UNIX_SULUM_VERSION=43
or
WINDOWS_SULUM_VERSION=43
in Makefile.local
You need to update from github.
Thanks
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
2015-10-01 9:23 GMT+02:00 Manuel Riel<EMAIL_ADDRESS>
That solved it. I just had to change sulum10 to sulum43 in
makefiles/Makefile.unix to make it work from there. Should I change it
everywhere and submit a PR for that? @lperron https://github.com/lperron
—
Reply to this email directly or view it on GitHub
https://github.com/google/or-tools/issues/93#issuecomment-144642253.

Works now great on Linux. On Mac I'm running into some new issues. I'm posting the failing command. First thought it had something to do with makefiles/Makefile.unix and the path being set to -L$(UNIX_SLM_DIR)/linux64/bin/ instead of mac64. But still failing after that.
The latest (and probably last) Sulum release is here. Maybe you have a point for me.
https://drive.google.com/open?id=0B_Bi-aTO9UR0Mko2ZjVrVjFJM1E
clang++ -fPIC -std=c++11 -O4 -DNDEBUG -Isrc -Iexamples -Isrc/gen -I/Users/manu/Workspace/build-ortools/or-tools/dependencies/sources/gflags-2.1.2/include -DARCH_K8 -Wno-deprecated -I/Users/manu/Workspace/build-ortools/or-tools/dependencies/install/include -I/Users/manu/Workspace/build-ortools/or-tools/dependencies/install/include -DUSE_CBC -I/Users/manu/Workspace/build-ortools/or-tools/dependencies/install/include -DUSE_CLP   -I/Users/manu/Workspace/build-ortools/sulum43/BraunDesert/header -DUSE_SLM   -DUSE_GLOP -DUSE_BOP -I../sparsehash-1.11/include objs/glop/solve.o lib/liblinear_solver.a lib/libbop.a lib/libsat.a lib/libsplit.a lib/libalgorithms.a lib/libglop.a lib/libutil.a lib/libbase.a  /Users/manu/Workspace/build-ortools/or-tools/dependencies/install/lib/libCbcSolver.a /Users/manu/Workspace/build-ortools/or-tools/dependencies/install/lib/libCbc.a /Users/manu/Workspace/build-ortools/or-tools/dependencies/install/lib/libCgl.a /Users/manu/Workspace/build-ortools/or-tools/dependencies/install/lib/libOsi.a /Users/manu/Workspace/build-ortools/or-tools/dependencies/install/lib/libOsiCbc.a /Users/manu/Workspace/build-ortools/or-tools/dependencies/install/lib/libOsiClp.a /Users/manu/Workspace/build-ortools/or-tools/dependencies/install/lib/libClp.a /Users/manu/Workspace/build-ortools/or-tools/dependencies/install/lib/libCoinUtils.a       /Users/manu/Workspace/build-ortools/or-tools/dependencies/sources/gflags-2.1.2/lib/libgflags.a -lz /Users/manu/Workspace/build-ortools/or-tools/dependencies/install/lib/libprotobuf.a  -o bin/solve
Undefined symbols for architecture x86_64:
  "_SlmAddEmptyCons", referenced from:
      operations_research::SLMInterface::ExtractNewConstraints() in liblinear_solver.a(sulum_interface.o)
  "_SlmAddEmptyVars", referenced from:
      operations_research::SLMInterface::ExtractNewVariables() in liblinear_solver.a(sulum_interface.o)
  "_SlmClear", referenced from:
      operations_research::SLMInterface::Reset() in liblinear_solver.a(sulum_interface.o)
  "_SlmFreeEnv", referenced from:
      operations_research::SLMInterface::~SLMInterface() in liblinear_solver.a(sulum_interface.o)
  "_SlmFreeModel", referenced from:
      operations_research::SLMInterface::~SLMInterface() in liblinear_solver.a(sulum_interface.o)
  "_SlmGetANz64", referenced from:
      operations_research::SLMInterface::ExtractNewConstraints() in liblinear_solver.a(sulum_interface.o)
  "_SlmGetAVarsI", referenced from:
      operations_research::SLMInterface::ComputeScaledBasisL1Norm(int, int, double*, double*) const in liblinear_solver.a(sulum_interface.o)
  "_SlmGetBasisHead", referenced from:
      operations_research::SLMInterface::ComputeInverseScaledBasisL1Norm(int, int, double*, double*) const in liblinear_solver.a(sulum_interface.o)
  "_SlmGetCons", referenced from:
      operations_research::SLMInterface::ComputeExactConditionNumber() const in liblinear_solver.a(sulum_interface.o)
  "_SlmGetDbInfo", referenced from:
      operations_research::SLMInterface::Solve(operations_research::MPSolverParameters const&) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::best_objective_bound() const in liblinear_solver.a(sulum_interface.o)
  "_SlmGetIntInfo", referenced from:
      operations_research::SLMInterface::iterations() const in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::nodes() const in liblinear_solver.a(sulum_interface.o)
  "_SlmGetSolDualConsI", referenced from:
      operations_research::SLMInterface::Solve(operations_research::MPSolverParameters const&) in liblinear_solver.a(sulum_interface.o)
  "_SlmGetSolDualVarsI", referenced from:
      operations_research::SLMInterface::Solve(operations_research::MPSolverParameters const&) in liblinear_solver.a(sulum_interface.o)
  "_SlmGetSolKeyPrimConsI", referenced from:
      operations_research::SLMInterface::row_status(int) const in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::ComputeScaledBasisL1Norm(int, int, double*, double*) const in liblinear_solver.a(sulum_interface.o)
  "_SlmGetSolKeyPrimVarsI", referenced from:
      operations_research::SLMInterface::column_status(int) const in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::ComputeScaledBasisL1Norm(int, int, double*, double*) const in liblinear_solver.a(sulum_interface.o)
  "_SlmGetSolPrimVarsI", referenced from:
      operations_research::SLMInterface::Solve(operations_research::MPSolverParameters const&) in liblinear_solver.a(sulum_interface.o)
  "_SlmGetSolStatus", referenced from:
      operations_research::SLMInterface::Solve(operations_research::MPSolverParameters const&) in liblinear_solver.a(sulum_interface.o)
  "_SlmGetSulumVersion", referenced from:
      operations_research::SLMInterface::SolverVersion() const in liblinear_solver.a(sulum_interface.o)
  "_SlmGetTypeVarsI", referenced from:
      operations_research::SLMInterface::SetVariableInteger(int, bool) in liblinear_solver.a(sulum_interface.o)
  "_SlmGetVars", referenced from:
      operations_research::SLMInterface::ComputeExactConditionNumber() const in liblinear_solver.a(sulum_interface.o)
  "_SlmHintAMaxNz64", referenced from:
      operations_research::SLMInterface::ExtractNewConstraints() in liblinear_solver.a(sulum_interface.o)
  "_SlmInitBasisSolves", referenced from:
      operations_research::SLMInterface::ComputeInverseScaledBasisL1Norm(int, int, double*, double*) const in liblinear_solver.a(sulum_interface.o)
  "_SlmMakeEnv", referenced from:
      operations_research::SLMInterface::SLMInterface(operations_research::MPSolver*, bool) in liblinear_solver.a(sulum_interface.o)
  "_SlmMakeModel", referenced from:
      operations_research::SLMInterface::SLMInterface(operations_research::MPSolver*, bool) in liblinear_solver.a(sulum_interface.o)
  "_SlmOptimize", referenced from:
      operations_research::SLMInterface::Solve(operations_research::MPSolverParameters const&) in liblinear_solver.a(sulum_interface.o)
  "_SlmSetAConsI", referenced from:
      operations_research::SLMInterface::ClearConstraint(operations_research::MPConstraint*) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::ExtractOneConstraint(operations_research::MPConstraint*, int*, double*) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::ExtractNewConstraints() in liblinear_solver.a(sulum_interface.o)
  "_SlmSetAIJ", referenced from:
      operations_research::SLMInterface::SetCoefficient(operations_research::MPConstraint*, operations_research::MPVariable const*, double, double) in liblinear_solver.a(sulum_interface.o)
  "_SlmSetDbParam", referenced from:
      operations_research::SLMInterface::ConfigureSLMParameters(operations_research::MPSolverParameters const&) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::SetRelativeMipGap(double) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::SetPrimalTolerance(double) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::SetDualTolerance(double) in liblinear_solver.a(sulum_interface.o)
  "_SlmSetIntParam", referenced from:
      operations_research::SLMInterface::SetOptimizationDirection(bool) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::Solve(operations_research::MPSolverParameters const&) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::SetPresolveMode(int) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::SetLpAlgorithm(int) in liblinear_solver.a(sulum_interface.o)
  "_SlmSetKeyConsI", referenced from:
      operations_research::SLMInterface::SetConstraintBounds(int, double, double) in liblinear_solver.a(sulum_interface.o)
  "_SlmSetKeyVarsI", referenced from:
      operations_research::SLMInterface::SetVariableBounds(int, double, double) in liblinear_solver.a(sulum_interface.o)
  "_SlmSetLoConsI", referenced from:
      operations_research::SLMInterface::SetConstraintBounds(int, double, double) in liblinear_solver.a(sulum_interface.o)
  "_SlmSetLoVarsI", referenced from:
      operations_research::SLMInterface::SetVariableBounds(int, double, double) in liblinear_solver.a(sulum_interface.o)
  "_SlmSetLoggingCallback", referenced from:
      operations_research::SLMInterface::SLMInterface(operations_research::MPSolver*, bool) in liblinear_solver.a(sulum_interface.o)
  "_SlmSetNameConsI", referenced from:
      operations_research::SLMInterface::ExtractNewConstraints() in liblinear_solver.a(sulum_interface.o)
  "_SlmSetNameVarsI", referenced from:
      operations_research::SLMInterface::ExtractNewVariables() in liblinear_solver.a(sulum_interface.o)
  "_SlmSetObjFix", referenced from:
      operations_research::SLMInterface::ClearObjective() in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::ExtractObjective() in liblinear_solver.a(sulum_interface.o)
  "_SlmSetObjName", referenced from:
      operations_research::SLMInterface::SLMInterface(operations_research::MPSolver*, bool) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::Reset() in liblinear_solver.a(sulum_interface.o)
  "_SlmSetObjVarsI", referenced from:
      operations_research::SLMInterface::ClearObjective() in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::ExtractNewVariables() in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::ExtractObjective() in liblinear_solver.a(sulum_interface.o)
  "_SlmSetParamDefault", referenced from:
      operations_research::SLMInterface::Reset() in liblinear_solver.a(sulum_interface.o)
  "_SlmSetUpConsI", referenced from:
      operations_research::SLMInterface::SetConstraintBounds(int, double, double) in liblinear_solver.a(sulum_interface.o)
  "_SlmSetUpVarsI", referenced from:
      operations_research::SLMInterface::SetVariableBounds(int, double, double) in liblinear_solver.a(sulum_interface.o)
  "_SlmSolveFtranDense", referenced from:
      operations_research::SLMInterface::ComputeInverseScaledBasisL1Norm(int, int, double*, double*) const in liblinear_solver.a(sulum_interface.o)
  "_SlmWriteProblem", referenced from:
      operations_research::SLMInterface::SLMInterface(operations_research::MPSolver*, bool) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::~SLMInterface() in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::Reset() in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::WriteModel(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::SetOptimizationDirection(bool) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::SetVariableBounds(int, double, double) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::SetVariableInteger(int, bool) in liblinear_solver.a(sulum_interface.o)
      ...
  "_SlmWriteSolution", referenced from:
      operations_research::SLMInterface::SLMInterface(operations_research::MPSolver*, bool) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::~SLMInterface() in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::Reset() in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::WriteModel(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::SetOptimizationDirection(bool) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::SetVariableBounds(int, double, double) in liblinear_solver.a(sulum_interface.o)
      operations_research::SLMInterface::SetVariableInteger(int, bool) in liblinear_solver.a(sulum_interface.o)
      ...
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [bin/solve] Error 1

Copied some of the sulum-specific settings from Linux to Mac in the Makefile and that fixed it. Will add a PR shortly.


Msg: Undefined symbols for architecture x86_64: when iOS simulator is the target

New Issue Checklist

[x] I have read and understood the CONTRIBUTING guide
[x] I have read the Documentation or CocoaDocs
[x] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
ios

Platform Version
10.1

CocoaLumberjack Version
3.0.0

Integration Method
cocoapods

Xcode Version
8.1

Repro rate
all the time

Demo project link
None

Issue Description and Steps
I am upgrading my app to Swift 3 and I have run into a problem linking when the iOS simulator is the target.
I get several messages of the sort:
Undefined symbols for architecture x86_64:
  "CocoaLumberjack.DDLogDebug (@autoclosure () -> Swift.String, level : __C.DDLogLevel, context : Swift.Int, file : Swift.StaticString, function : Swift.StaticString, line : Swift.UInt, tag : Any?, asynchronous : Swift.Bool, ddlog : __ObjC.DDLog) -> ()", referenced from:
      ScanmonListener.SMLViewController.buttonTitle.didset : Swift.String in SMLViewController.o
      ScanmonListener.SMLViewController.viewDidLoad () -> () in SMLViewController.o
      ...

I have tried a pod deintegrate and then an install and that had no effect.

With Xcode 8.1, I recommend you  use master branch because it has been tested with Xcode 8.1.
And if you'd like to Swift version(CocoaLumberjack/Swift subspec), ensure the followings before you integrate the project with CocoaPods.

Check the CocoaPods version is 1.1.0 or later.
In your main app project's Build Settings, set Use Legacy Swift Language Version to No.

I hope this will clear up the problem.

Unfortunately I still have the problem.
My cocoapods versions is 1.2.0.beta.3
I deintegrated the project, verified the Legacy Swift setting is No.
Changed my Podfile to:
platform :ios, '10.2'

target 'ScanmonListener' do
    pod 'CocoaLumberjack/Swift', :git => 'https://github.com/CocoaLumberjack/CocoaLumberjack.git', :branch => 'master'
    use_frameworks!
end

...

But I still get:
Undefined symbols for architecture x86_64:
  "CocoaLumberjack.(DDLogVerbose (@autoclosure () -> Swift.String, level : __C.DDLogLevel, context : Swift.Int, file : Swift.StaticString, function : Swift.StaticString, line : Swift.UInt, tag : Any?, asynchronous : Swift.Bool, ddlog : __ObjC.DDLog) -> ()).(default argument 1)", referenced from:
      ScanmonListener.SMLViewController.buttonTouch (__ObjC.UIButton) -> () in SMLViewController.o

31 times when I build against the iOS Simulator but if I choose "Generic iOS Device" it compiles and links fine.
I haven't built this in a while, probably against XCode 7.x last, but it did build and run on the simulator.

Solved!
For each of the targets under Pods I had to edit the Valid Architectures setting to add x86_64
Compile and link against the iOS Simulator now works and my app now runs under the simulator again.

Just an Information.
At my local machine(Xcode: 8.2.1, toolchain: Swift 3.0.2), I was actually able to build CocoaLumberjack only with a normal procedure.
IMHO, if you reinstall a library with CocoaPods, pod deintegrate is not enough.
You need to execute not only pod deintegrate but also pod cache clean CocoaLumberjack and rm -rf /Library/Developer/Xcode/DerivedData.
Summary is here.
Podfile
source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '10.2'
use_frameworks!
inhibit_all_warnings!

target 'CocoaLumberjackSample' do
  pod 'CocoaLumberjack/Swift', :git => 'https://github.com/CocoaLumberjack/CocoaLumberjack.git'
end

Check Use Legacy Swift Language Version is set to No and close xcworkspace.
Then execute the followings.
pod deintegrate
pod cache clean CocoaLumberjack
rm -rf /Library/Developer/Xcode/DerivedData
pod install

I hope this will be helpful for someone.


remove unmaintained node.js server library

Remove https://github.com/SeyZ/jsonapi-serializer implementation because
it is not actively maintained.
Following the discussion in https://github.com/json-api/json-api/issues/733 and https://github.com/json-api/json-api/issues/1313, I think it would be incredibly helpful to have some way for libraries to prove their adherence to a given version of the specification.

/cc @SeyZ

Could we replace it with https://github.com/danivek/json-api-serializer

I'm reluctant to remove this library because there's been commit activity within the past two months: https://github.com/SeyZ/jsonapi-serializer/commits/master
Given this, I'd want confirmation from @SeyZ before doing anything.

Could we replace it with https://github.com/danivek/json-api-serializer

@ckeboss That seems fairly popular and doesn't appear to be a fork of SeyZ/jsonapi-serializer. Perhaps danivek/json-api-serializer should have an entry of its own?

I'd second making https://github.com/danivek/json-api-serializer a new entry. Given both have similar goals (framework agnostic), perhaps we could annotate that in their descriptions?

@dgeb Sure. Perhaps a little emphasis that the names are very similar.


Chain DB: audit and test the iterators/readers for race conditions

The ChainDB iterators and readers will have to read blocks that have been copied from the ImmutableDB and garbage-collected from the VolatileDB. Check whether we deal with this correctly (no race conditions) and test it thoroughly (inspiration: http://hackage.haskell.org/package/dejafu).
Note that in practice there will be a non-trivial overlap between the ImmutableDB and the VolatileDB, so the potential race conditions will probably happen only very rarely (or not at all). Still, we have to test this.

A start was made in #810. Next steps for the iterator-specific tests:

Write a generator for TestSetup (Test.Ouroboros.Storage.ChainDB.Iterator) and a model implementation (reuse ChainDB.Model) to turn this into a property test.
Instead of simply reading all blocks, use:data Action = IterNext .. | CopyToImmDB .. | GCFromVolDB ..

And write a generator for it.
Run multiple Actions in parallel


Flutter video player no audio

I created a simple video player in flutter. Many small size videos are working fine in this player. But when i tried some high definition videos, Audio is not working. So what may be the problem ? Do i need extra codecs to support this audios?

can you drop some code or a screen recording so we can dig into this @MahmoudQassass ?

There is no bug to see, When i playing high quality video, The video works fine but the issue is about no sound appear in high quality video!

Hi @MahmoudQassass,
Can you please provide your flutter doctor -v?
Please specify which version of videp_player you're using and if possible, kindly provide an example of the video that plays without audio.
Thank you


Multiple syntax and loop errors in build

error cleaned up!
all syntax and loop errors removed
hence issue closed


Title does not update

Counter in the title works fine when we select media but when we unselect all the media and back to the first screen then the title is not refreshed.
I think its a BUG.

Can you please try with the new version 1.0.5 ? 😄


Add support for ip igmp snooping querier per vlan

Enhancement summary
For L2 EVPN multicast to function, it's required to enable ip igmp snooping querier on the vlan, along with a querier address, e.g.
ip igmp snooping vlan 100 querier
ip igmp snooping vlan 100 querier address <IP_ADDRESS>
Looking to add this support to eos_cli_config_gen and eos_designs.
Which component of AVD is impacted
eos_designs, eos_cli_config_gen
Use case example
Since the ip igmp snooping querier functionality is defined outside of the vlan config, structure can be added similarly to the enable/disable capability which exists today;
ip_igmp_snooping:
vlans:
3501:
querier:
address: <IP_ADDRESS>
Since the number of vlans can be high with the same requirement, this can be added to l2vlan config under tenant networks
  l2vlans:
    3501:
      name: Deadnet_3501
      tags: [ compute_leaf ]
      ip_igmp_snooping_querier:
        address: <IP_ADDRESS>

Both can be accomplished with minor changes to the ip-igmp-snooping.j2 templates in both the eos_cli_config_gen and eos_designs modules.
Describe the solution you would like
As above would like the ability to configure ip igmp snooping querier and ip igmp snooping querier address via eos_cli_config_gen and eos_designs.  Sample j2 template for eos_cli_config_gen:
{# eos - IP IGMP Snooping #}
{% if ip_igmp_snooping.globally_enabled is arista.avd.defined(false) %}
!
no ip igmp snooping
{% elif ip_igmp_snooping.vlans is arista.avd.defined %}
!
{%     for vlan in ip_igmp_snooping.vlans | arista.avd.natural_sort %}
{%         if ip_igmp_snooping.vlans[vlan].enabled is arista.avd.defined(false) %}
no ip igmp snooping vlan {{ vlan }}
{# Begin changes to add querier #}
{%         endif %}
{%         if ip_igmp_snooping.vlans[vlan].querier is arista.avd.defined %}
ip igmp snooping vlan {{ vlan }} querier
{%         endif %}
{%         if ip_igmp_snooping.vlans[vlan].querier.address is arista.avd.defined %}
ip igmp snooping vlan {{ vlan }} querier address {{ ip_igmp_snooping.vlans[vlan].querier.address }}
{# End changes to add querier #}
{%         endif %}
{%     endfor %}
{% endif %}
And sample j2 template for eos_designs:

{# ---------------------------- #}
{# L2VLANs services             #}
{# ---------------------------- #}
{%         for l2vlan in tenant.l2vlans %}
{%             if l2vlan.igmp_snooping_enabled is arista.avd.defined %}
    {{ l2vlan.id | int }}:
      enabled: {{ l2vlan.igmp_snooping_enabled }}
{%             endif %}
{# Begin Changes to add igmp snooping querier #}
{%             if l2vlan.ip_igmp_snooping_querier is arista.avd.defined %}
    {{ l2vlan.id | int }}:
      querier:
{%               if l2vlan.ip_igmp_snooping_querier.address is arista.avd.defined %}
        address: {{ l2vlan.ip_igmp_snooping_querier.address }}
{%               endif %}
{%             endif %}
{# End changes to add igmp snooping querier #}
{%         endfor %}
{%     endfor %}
{% endif %}
Describe alternatives you have considered
Have looked into using raw_eos_cli, however, this is a lot of raw CLI in a network with a large number of vlans.  Additionally, the l2vlans under tenants already supports ip_igmp_snooping_enabled to toggle support for igmp snooping per vlan defined in the tenants.  Adding support for querier and querier address in the tenants would seem natural.
Additional context
This configuration is required for L2 EVPN multicast to work.
Contributing Guide

[X] I agree to follow this project's Code of Conduct

Solved in #1464 a few days ago.


Implement description updating

Repost of #222

Fixed merge conflict

Is it possibe to modify repo url? it would make sense to set it to chaosthebot.com

But that's not the repo URL. That's where the code is hosted...

I mean homepage in terms of github and here is the link, that anwers my question: https://developer.github.com/v3/repos/#edit

There, used repo name from settings.

@reddraggone9 I'm so blind, you posted link above 🤦♂

Okay, I put them on the same line.


refactor: wiki incremental example uses REST API for CRUD

As much as I love your assumption that I could review this, please add like someone like @bwanglzu , @rutujasurve94 or

@cristianmtr if this looks no more changes are needed for this, we are good to merge.


Create Twitter Action

So discussed a method of tweeting to twitter with @KrauseFx.
Implementation could use https://github.com/muffinista/chatterbot underneath which makes it straight forward to do twitter actions.
Hopefully once I have some freetime, I'll be able to implement an action for this :) :rocket:

https://github.com/fastlane/fastlane/pull/1202

Closing and moving further discussion to https://github.com/fastlane/fastlane/pull/1202, thanks @hjanuschka :+1:


Renderer crash with amdgpu-pro OGLP driver on Linux, nullptr festival

When running proprietary amdgpu-pro OGLP driver version 23.20-1664987.22.04 (from amdgpu-pro 5.7.1) on Ubuntu 23.10, I get a crash.
The glContext pointer is properly set to something that is not nullptr so the game believes everything is right and crashes elsewhere.
For example, while glContext is not nullptr and is considered valid, doing things like glGetString( GL_VERSION ) is returning a nullptr, if I add a workaround for this, I get some other nullptr error somewhere else in the code, like with GL_RENDERER.
What's weird is that the driver works, for example I can run Xonotic 0.8.6 without problem and the DarkPlaces engine prints:
GL_VENDOR: ATI Technologies Inc.
GL_RENDERER: AMD Radeon PRO W7600
GL_VERSION: 4.6.0 Compatibility Profile Context 23.20.230929

But more curiously, if I run an older prebuilt version of Unvanquished, like the 0.51.2, the game runs and the engine prints:
GL_VENDOR: ATI Technologies Inc.
GL_RENDERER: AMD Radeon PRO W7600
GL_VERSION: 4.6.0 Compatibility Profile Context 23.20.230929
GL_SHADING_LANGUAGE_VERSION: 4.60

The proprietary OGLP driver is not recommended by AMD (they recommend the stock free open source Mesa driver instead), unless you know why you need it. Anyway, it is distributed withing AMDGPU-PRO package, and then people may use it, either intentionally, either by mistake.
Since other games run, and especially older versions of the game, it's possible we may be doing something wrong.

Our current release (0.54.0) works… but

It was not built on the same system.
We have updated SDL2.

A release build from master runs properly, the release build has a statically self-built SDL2, so maybe it's a bug in stock SDL2 from Ubuntu 23.10?

Building on Ubuntu 23.10 but with our own SDL2 external_deps reproduces the bug, so the stock Ubuntu SDL2 is probably not the culprit.

For reference, here is the backtrace:
Thread 1 (Thread 0x7ffff5500a80 (LWP 859175) "daemon"):
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76
#1  0x00007ffff7092674 in _IO_str_init_static_internal (sf=sf@entry=0x7fffffffcd10, ptr=ptr@entry=0x0, size=size@entry=0, pstart=pstart@entry=0x0) at ./libio/strops.c:41
#2  0x00007ffff705c222 in _IO_strfile_read (string=0x0, sf=0x7fffffffcd10) at ../libio/strfile.h:90
#3  __GI___isoc23_sscanf (s=0x0, format=format@entry=0x5555557a2c5a "%d.%d") at ./stdio-common/isoc23_sscanf.c:28
#4  0x000055555570fafc in GLimp_RegisterConfiguration (highestConfiguration=..., requestedConfiguration=...) at Unvanquished/daemon/src/engine/sys/sdl_glimp.cpp:1240
#5  GLimp_SetMode (mode=<optimized out>, fullscreen=fullscreen@entry=false, bordered=bordered@entry=false) at Unvanquished/daemon/src/engine/sys/sdl_glimp.cpp:1422
#6  0x0000555555710759 in GLimp_StartDriverAndSetMode (mode=<optimized out>, fullscreen=false, bordered=false) at Unvanquished/daemon/src/engine/sys/sdl_glimp.cpp:1521
#7  0x00005555557109df in GLimp_Init () at Unvanquished/daemon/src/engine/sys/sdl_glimp.cpp:1951
#8  0x00005555556c1e8e in InitOpenGL () at Unvanquished/daemon/src/engine/renderer/tr_init.cpp:307
#9  0x00005555556c3b60 in R_Init () at Unvanquished/daemon/src/engine/renderer/tr_init.cpp:1414
#10 0x00005555556d2f23 in RE_BeginRegistration (glconfigOut=0x555555d7cdb4 <cls+2802484>, glconfig2Out=0x555555d7d9e0 <cls+2805600>) at Unvanquished/daemon/src/engine/renderer/tr_model.cpp:259
#11 0x0000555555616b12 in CL_InitRenderer () at Unvanquished/daemon/src/engine/client/cl_main.cpp:2134
#12 0x0000555555616dd5 in CL_StartHunkUsers () at Unvanquished/daemon/src/engine/client/cl_main.cpp:2208
#13 CL_StartHunkUsers () at Unvanquished/daemon/src/engine/client/cl_main.cpp:2194
#14 0x000055555578686f in Sys::Init (argc=<optimized out>, argv=0x7fffffffdc38) at Unvanquished/daemon/src/engine/framework/System.cpp:721
#15 0x00005555555a24df in main (argc=<optimized out>, argv=<optimized out>) at Unvanquished/daemon/src/engine/framework/System.cpp:741

This may not be a bug in dæmon, maybe we face some library mismatch between the driver and daemon, but it's still useful to document this.
It looks like @cu-kai is reproducing a very similar bug when running a custom-built Mesa on Arch and using some Wayland/Prime options:

Thread 1 "daemon" received signal SIGSEGV, Segmentation fault.
0x00007ffff7178edd in ?? () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007ffff7178edd in ?? () from /usr/lib/libc.so.6
#1  0x00007ffff70a5b85 in ?? () from /usr/lib/libc.so.6
#2  0x00007ffff7073d34 in __isoc23_sscanf () from /usr/lib/libc.so.6
#3  0x00005555556b6992 in GLimp_RegisterConfiguration (highestConfiguration=..., requestedConfiguration=...) at daemon/src/engine/sys/sdl_glimp.cpp:1240
#4  0x00005555556b6fcd in GLimp_SetMode (mode=<optimized out>, fullscreen=fullscreen@entry=false, bordered=bordered@entry=true) at daemon/src/engine/sys/sdl_glimp.cpp:1422
#5  0x00005555556b7253 in GLimp_StartDriverAndSetMode (mode=<optimized out>, fullscreen=false, bordered=bordered@entry=true) at daemon/src/engine/sys/sdl_glimp.cpp:1521
#6  0x00005555556b7e12 in GLimp_Init () at daemon/src/engine/sys/sdl_glimp.cpp:1951
#7  0x0000555555676039 in InitOpenGL () at daemon/src/engine/renderer/tr_init.cpp:307
#8  0x000055555567894c in R_Init () at daemon/src/engine/renderer/tr_init.cpp:1414
#9  0x0000555555686bd5 in RE_BeginRegistration (glconfigOut=0x555555d28714 <cls+2802484>, glconfig2Out=0x555555d29340 <cls+2805600>) at daemon/src/engine/renderer/tr_model.cpp:259
#10 0x00005555555e424c in CL_InitRenderer () at daemon/src/engine/client/cl_main.cpp:2135
#11 0x00005555555e44b8 in CL_StartHunkUsers () at daemon/src/engine/client/cl_main.cpp:2209
#12 0x000055555557c78f in Application::ClientApplication::Initialize (this=<optimized out>) at daemon/src/engine/client/ClientApplication.cpp:92
#13 0x00005555556ee55f in Application::Initialize () at daemon/src/engine/framework/Application.cpp:71
#14 0x000055555570a3d9 in Sys::Init (argc=16, argv=0x7fffffffe2d8) at daemon/src/engine/framework/System.cpp:720
#15 0x000055555570a53b in main (argc=<optimized out>, argv=<optimized out>) at daemon/src/engine/framework/System.cpp:740

I summon @slipher as I would need some master wizard opinion on such dark magic bug.
I actually suspect some library mismatches between the driver and the game: maybe the game or SDL2 is built against a version of a library, but the driver already loaded an incompatible variant of that library, or something like that?

Yeah updating GLEW would be a good thing to try if there is a new version. On Mac there was a problem that GLEW started to hand us some null function pointers, which was fixed by updating GLEW.

I get this error when I build the engine with Ubuntu 23.10 system's GLEW 2.2.0
The Debian buster static build with non-system GLEW 2.2.0 we do with docker doesn't suffer from that bug on my end.

Building against our own GLEW with those external deps:
./build.sh linux-amd64-default glew naclsdk install

Brings me the same bug…

I don't know if that's related, but building GLEW 2.2.0 on Ubuntu 23.10 with GCC 13.2.0 brings me those warnings:
src/glew.c: In function ‘_glewStrSame1’:
src/glew.c:256:29: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘*a + (sizetype)i’ must not be NULL [-Waddress]
  256 |     while (i < nb && (*a)+i != NULL && b+i != NULL && (*a)[i] == b[i]) i++;
      |                             ^~
src/glew.c:256:44: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘b + (sizetype)i’ must not be NULL [-Waddress]
  256 |     while (i < nb && (*a)+i != NULL && b+i != NULL && (*a)[i] == b[i]) i++;
      |                                            ^~
src/glew.c: In function ‘_glewStrSame2’:
src/glew.c:272:29: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘*a + (sizetype)i’ must not be NULL [-Waddress]
  272 |     while (i < nb && (*a)+i != NULL && b+i != NULL && (*a)[i] == b[i]) i++;
      |                             ^~
src/glew.c:272:44: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘b + (sizetype)i’ must not be NULL [-Waddress]
  272 |     while (i < nb && (*a)+i != NULL && b+i != NULL && (*a)[i] == b[i]) i++;
      |                                            ^~
src/glew.c: In function ‘_glewStrSame3’:
src/glew.c:288:29: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘*a + (sizetype)i’ must not be NULL [-Waddress]
  288 |     while (i < nb && (*a)+i != NULL && b+i != NULL && (*a)[i] == b[i]) i++;
      |                             ^~
src/glew.c:288:44: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘b + (sizetype)i’ must not be NULL [-Waddress]
  288 |     while (i < nb && (*a)+i != NULL && b+i != NULL && (*a)[i] == b[i]) i++;
      |                                            ^~
src/glew.c: In function ‘_glewStrSame1’:
src/glew.c:256:29: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘*a + (sizetype)i’ must not be NULL [-Waddress]
  256 |     while (i < nb && (*a)+i != NULL && b+i != NULL && (*a)[i] == b[i]) i++;
      |                             ^~
src/glew.c:256:44: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘b + (sizetype)i’ must not be NULL [-Waddress]
  256 |     while (i < nb && (*a)+i != NULL && b+i != NULL && (*a)[i] == b[i]) i++;
      |                                            ^~
src/glew.c: In function ‘_glewStrSame2’:
src/glew.c:272:29: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘*a + (sizetype)i’ must not be NULL [-Waddress]
  272 |     while (i < nb && (*a)+i != NULL && b+i != NULL && (*a)[i] == b[i]) i++;
      |                             ^~
src/glew.c:272:44: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘b + (sizetype)i’ must not be NULL [-Waddress]
  272 |     while (i < nb && (*a)+i != NULL && b+i != NULL && (*a)[i] == b[i]) i++;
      |                                            ^~
src/glew.c: In function ‘_glewStrSame3’:
src/glew.c:288:29: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘*a + (sizetype)i’ must not be NULL [-Waddress]
  288 |     while (i < nb && (*a)+i != NULL && b+i != NULL && (*a)[i] == b[i]) i++;
      |                             ^~
src/glew.c:288:44: warning: the comparison will always evaluate as ‘true’ for the pointer operand in ‘b + (sizetype)i’ must not be NULL [-Waddress]
  288 |     while (i < nb && (*a)+i != NULL && b+i != NULL && (*a)[i] == b[i]) i++;
      |

When building your own deps are you sure that you are actually using them? You probably have to manually set the cmake variables (in the release script they are only used automatically because we set USE_STATIC_LIBS or whatever.) The slipher/printdepversions branch might be interesting to make sure.

Both CMake and ldd tells me I use my custom GLEW.

Nice find! I don't remember why I had to put -DOpenGL_GL_PREFERENCE=LEGACY there (compatibility with old systems maybe) but apparently it's a good thing

@cu-kai confirmed on IRC that building with -DOpenGL_GL_PREFERENCE=LEGACY also fixes the segfaults he gets when running the engine on Wayland with Prime:
2023-11-30 19:59:06 +0100 <illwieckz> cu-kai, what if you build daemon with -DOpenGL_GL_PREFERENCE=LEGACY
2023-11-30 20:15:24 +0100 <cu-kai> how do i compile with this option?
2023-11-30 20:15:51 +0100 <illwieckz> cd build ; cmake -DOpenGL_GL_PREFERENCE=LEGACY .. ; make -j$(nproc)
2023-11-30 20:16:03 +0100 <cu-kai> i did exactly this
2023-11-30 20:16:26 +0100 <cu-kai> fixes for me too

I renamed this thread as “Renderer segfault with GLVND OpenGL ABI on Linux, nullptr festival”, so this thread is not about the specific OGLP use case that triggers that GLVND issue, but about this family of GLVND issues in general.

It looks like the reason why we use -DOpenGL_GL_PREFERENCE=LEGACY in release builds is that despite GLVND is something introduced by Nvidia, they never re-released their legacy drivers so it seems that only engines build with LEGACY can run on older Nvidia drivers and then older Nvidia hardware (if nouveau is not performant enough).
Unless I miss something, it looks like building with GLVND would immediately make the engine incompatible with a whole range of hardware and drivers that are totally capable to run the game:

https://github.com/DaemonEngine/Daemon/issues/474

Here, @necessarily-equal said that “Not having a GLX context is not a bug: wayland uses EGL for example”, I wonder if that's related:

https://github.com/DaemonEngine/Daemon/pull/483

So, here are quotes from #dri-devel @ OFTC (basically the historical Mesa developer channel).
TL;DR:

Building with a binary with LEGACY ABI is compatible with GLVND-aware libGL.so and legacy libGL.so.
Building a binary with GLVND ABI is incompatible with libGL.so, it uses backward-incompatible new libOpenGL.so instead.
A software developer shouldn't have to use GLVND ABI (and explicitly target backward-incompatible libOpenGL.so) unless he wants to and knows why he explictly needs such backward-incompatible ABI.
CMake is likely breaking people's apps in unknowingly developer's back and against their will by setting GLVND the default ABI.

The quotes:
2023-12-01 00:49:59 +0100 <illwieckz> Do someone knows a bit about glvnd? What
                          problems is it trying to solve? Unless we do something
                          wrong with the Dæmon game engine, accumulated
                          experience over two years is that building an OpenGL
                          application with GLVND ABI instead of LEGACY one
                          1. breaks compatibility with legacy Nvidia drivers,
                          2. breaks compatibility with AMD OGLP driver,
                          3. breaks compatibility with Wayland with Prime…
2023-12-01 00:53:00 +0100 <illwieckz> Is glvnd expected to be backward
                          compatible and all of these problems are bugs, or is
                          it considered OK that maybe only current Nvidia
                          drivers on Xorg is expected to work and we are just
                          lucky if current Mesa drivers are compatible with it
                          on Xorg too ?

2023-12-01 00:54:18 +0100 <Kayden> so there are two aspects to glvnd
2023-12-01 00:55:08 +0100 <Kayden> first is just the new vendor neutral dispatch
                          library.  glvnd provides libGL.so, and it loads the
                          vendor drivers (libGLX_mesa.so, libEGL_mesa.so,
                          libGLX_nvidia.so, etc)
2023-12-01 00:55:36 +0100 <Kayden> that should be fully backwards compatible,
                          and is meant as a way to let you parallel install mesa
                          drivers, nvidia proprietary drivers, fglrx (not that
                          that's a thing anymore) & whatever else
2023-12-01 00:56:06 +0100 <Kayden> as long as you're linking against libGL.so it
                          should not matter whether it's glvnd or mesa or nvidia
                          directly

2023-12-01 00:56:18 +0100 <Kayden> but it sounds like you may be running into
                          the second aspect
2023-12-01 00:56:30 +0100 <Kayden> which is...glvnd decided to define a new ABI
                          for OpenGL, libOpenGL.so
2023-12-01 00:56:45 +0100 <Kayden> which is not backwards compatible
2023-12-01 00:57:00 +0100 <Kayden> IIRC it only has OpenGL core profile support.
                          It also does not contain GLX
2023-12-01 00:57:12 +0100 <Kayden> libGL has both OpenGL core, OpenGL
                          compatibility (legacy), and GLX
2023-12-01 00:57:28 +0100 <Kayden> which is awkward if you're trying to do, say,
                          EGL only, on a non-X11 windowing environment
2023-12-01 00:57:54 +0100 <illwieckz> so, does it mean that I can build an app
                          with -DOpenGL_GL_PREFERENCE=LEGACY
2023-12-01 00:58:05 +0100 <illwieckz> but use a glvnd libGL.so ?
2023-12-01 00:58:16 +0100 <Kayden> I've not heard of that flag, but yes, it
                          should be possible
2023-12-01 00:58:33 +0100 <Kayden> you shouldn't have to target libOpenGL.so as
                          an app / engine author unless you -want- to

2023-12-01 00:58:37 +0100 <illwieckz> that's the cmake flag for selecting either
                          LEGACY ABI or GLVND ABI
2023-12-01 00:58:48 +0100 <illwieckz> ok, good to know
2023-12-01 00:59:01 +0100 <illwieckz> because CMake defaults to
                          -DOpenGL_GL_PREFERENCE=GLVND
2023-12-01 00:59:31 +0100 <illwieckz> even if the developer has no idea this
                          will break backward compatibility if I understand it
                          right
2023-12-01 01:00:13 +0100 <Kayden> yeah, I think that would break compatibility
                          with super legacy drivers that never transitioned

2023-12-01 01:03:17 +0100 <illwieckz> so, I assume the good thing to know for a
                          developer is: don't use GLVND ABI unless you know why
                          you need it
2023-12-01 01:04:20 +0100 <illwieckz> Maybe we may report to CMake that setting
                          the GLVND ABI the default is probably a mistake.

With the acquired knowledge, I now believe we need to use LEGACY by default and that CMake using GLVND by default is a mistake from CMake.
So I added a commit to use LEGACY OpenGL ABI on Linux by default unless OpenGL_GL_PREFERENCE is explictely set (and setting it to empty string is expected to use CMake default instead) to that PR:

https://github.com/DaemonEngine/Daemon/pull/976


Geode 6374 - Fixing DistributedNoAckRegionCCEOffHeapDUnitTest.testNoLoaderWithInvalidEntry

The "org.apache.geode.internal.cache.PartitionedRegionSizeDUnitTest > testBug39868 FAILED"
is the basis for GEODE-7510 which has a PR on it already.

This PR turned into a refactor of a bunch of files due to a number of periodic failures throughout.
This PR addresss GEODE-6374, GEODE-6326, GEODE-7472, GEODE-7512, and GEODE-7514.

Sorry I rebased due to a conflict, so a force push was required.


Zooming and Panning not working

Merging #97 and #111, I will try to explain what is going on here, zooming an panning are not working in 0.6.5 and wont work in the future 0.6.6 release
Why?
Zooming, Panning and High performance charts are directly related to how the charts are drawn the last releases have been really hard and now as you might see LiveCharts behave much better, all shapes are cached, in previous version everything was redrawn every time, this will improve the performance of the library a lot also improved animations, sadly in previous reelase (0.6.5) I only focused in improving the animations not the features (zooming and panning) because I knew I had to fix #21 and this will drop again the zooming and panning functionality. the good news it that #21 is already supported (will be released with 0.6.6) and I don't see any other feature that could affect zooming and panning again.
When will zooming and panning work?
in my experience I have rewritten zooming, panning and high performance too many times that I really don´t want to fix it until all major changes are done,. The good news is that I think we already built all the major enhancements, I would like to tell you that next release will be about fixing these 2 functionalities, but I can't promise that.

Zooming and panning are now working, here is an example
https://github.com/beto-rodriguez/Live-Charts/tree/master/WPFExamples/Line Examples/ZoomingPanningAndCursor
this is the result

Hey Beto,
Thank you very much, awesome work.
I can not find the ZoomingPanningAndCursor example on GitHub and the link above dead, could you please update the link.
Thank you very much!!

@AchimHaller Hi, I think I renamed the sample to:
https://lvcharts.net/App/examples/v1/wpf/Zooming and panning
It had suffered some modifications already, the site pulls the samples from the repo
https://raw.githubusercontent.com/beto-rodriguez/Live-Charts/master/Examples/Wpf/CartesianChart/ZoomingAndPanning/ZoomingAndPanning.xaml.cs

@beto-rodriguez  Hi, thanks for the quick answer.
Yes I found this sample in Git, what I meant is the Zooming and Panning sample that has the cursor function included, this I couldn't find.
Thanks for your help in advanced!

But Zooming doesn't work with Visual Elements. If I zoom, Visual Elements behave very strangely. I'm trying to put a background image under the plot, but it seems that it's not possible with this library


A problem with an xml2js dependency

Hi,
I swapped over to needle from request the other day, it seems you keep on top of the issues and there are far fewer dependencies. However, on rebuilding today I got the following error:
Error: Cannot find module 'xml2js' from '/home/james/Development/Occam/node_modules/needle/lib'
at /home/james/Development/Occam/node_modules/browser-resolve/node_modules/resolve/lib/async.js:46:17
at process (/home/james/Development/Occam/node_modules/browser-resolve/node_modules/resolve/lib/async.js:173:43)
at ondir (/home/james/Development/Occam/node_modules/browser-resolve/node_modules/resolve/lib/async.js:188:17)
at load (/home/james/Development/Occam/node_modules/browser-resolve/node_modules/resolve/lib/async.js:69:43)
at onex (/home/james/Development/Occam/node_modules/browser-resolve/node_modules/resolve/lib/async.js:92:31)
at /home/james/Development/Occam/node_modules/browser-resolve/node_modules/resolve/lib/async.js:22:47
at FSReqWrap.oncomplete (fs.js:123:15)

Installing the xml2js module did in the end fix it, but I only resorted to this because nothing else seemed to work.
Have you come across this before?

No, not really. It seems to be related to the build process, though. Which tool are you using?

Hi,
thanks for the prompt reply, firstly.
It's a weird one, certainly.
 The last but one line...
at /home/james/Development/Occam/node_modules/browser-resolve/node_modules/resolve/lib/async.js:22:47

...mentions browser resolve.
Here are the dependencies in the project I'm building:
"dependencies": {
  "express": "^4.11.2",
  "minimist": "^1.2.0",
  "necessary": "^1.4.2",
  "occam-open-cli": "^0.1.38"
},

I'm not using needle in the project I'm building, it's used in the last dependency. This one:
https://github.com/occam-proof-assistant/Open-CLI
I hope this helps.

Typically browser build tools parse and look for require('package') declarations in your code, and replace that with whatever dependency method they use.
Since needle does have a require('xml2js') line in the parsers.js file, it would explain both the error and fix (package missing, then not missing). The thing is that needle wraps that require line within a try/catch block so normally it won't blow up if you don't have the package. You'll just not have XML parsing support.
I'll give a thought and see if there's a cleaner way of solving this, in order to remove that require line altogether. In the meantime I think I'll add something in the Readme file to help out anyone that might also run into this.
Thanks for the heads up, by the way.

Hi,
no worries.
I'd be grateful if you could leave this issue open and close it when you have a solution. That way I'll get notified and can grab the latest version.
Kind regards,
James

Will do!
Any suggestions regarding a solution for the optional xml2js dependency?

Yes! I'd just thought of one although you won't like it. In fact, I intended not to add a comment on the subject for fear of offending you. But here goes...
In short, you should drop XML support. It's okay to parse JSON because it's trivial to do so and many get confused between JSON and stringified JSON anyway. However, you should not bother to parse XML because it goes beyond the remit of what needle should be. I'm probably going over things that you know well yourself but a good principle is not try to be all things to all men. Your spiel seems to be that you do HTTP/HTTPS stuff very well, with few dependencies. So stick to that. Few of your users expect needle to parse XML, probably. And all should be capable of doing it themselves.
Beyond that, your 'trick' of requiring xml2js and catching the error assumes that build tools won't fall foul of this and this is increasingly not going to be the case. I'm surprised that you've gotten away with it up until now. I don't think there is a clean way of doing what you want to do, so you shouldn't even try.
In short, drop XML support and bump your major version number, and save yourself and everyone else a big headache!


thought of how to address "alternatives" to fix inconsistency

currently, what m3u8 package calls alternatives seem to be handled inconsistently.  Namely, only the first "variant" after the set of alternatives gets the alternative and if the altneratives are at the end of the file, none get them.

the breaks somethings (i.e. is not complete), but is pushed as a POC in terms of perhaps a better API.
With that said, even with that, I'm not sure how it should work with multiple groups of alternatives, I'm not sure it matters so much (the end user can figure it out via group tag), but the current code doesn't work for real life cases at the moment either.


[i2c dif] Add headers for functions to control i2c device in the dif

Changed documentation references to consistently refer to FMT and RX buffers as FIFOs when applying names and short descriptions
Added a documentation referring to ability to reset the I2C block (because it might be useful)
Changed documentation references to RESTART to repeated START to make them more consistent with I2C standards
Annotated states with Shared, host and device mode to help track which features acted in which modes
Updated header for i2c_dif to support device mode and clarify which registers control which modes
corrected FIFO references in device tx rx test portion of testplan and added requirement to perform an I2C read

This PR should further but this commit doesn't yet:

implement the new dif functions
get unit tests for new dif functions
fix unit tests for modified dif functions

Signed-off-by: Drew Macrae<EMAIL_ADDRESS>

@drewmacrae could you check this against the i2c_host_tx_rx test that was VERY recently merged?
I can also move that into CI (was planning to anyways) so that you get some signal on the impact of i2c dif changes.

@drewmacrae could you check this against the i2c_host_tx_rx test that was VERY recently merged? I can also move that into CI (was planning to anyways) so that you get some signal on the impact of i2c dif changes.

Yes, I'll be sure to do that!

just FYI I merged i2c_host_tx_rx test directly into CI. It doesn't do a ton, but tweaks on the dif interface "may" change how it behaves.  So if you see any failures and it looks weird, just let me know and i can help look.
The test right now doesn't really implement the "full" read sequence. Ie, there's no direction change or repeated started in there.  So just keep that in mind for now.


Problem getting python include path while building tensorflow lite using Bazel

Issue type
Build/Install
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
2.5
Custom code
No
OS platform and distribution
No response
Mobile device
No response
Python version
3.10.12
Bazel version
3.7.2
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
While building tensorflow lite using bazel, I encountered the following errors in the log output. Here is my bazel command:
/c/tensorflow-2.5.0/tflite_build$ bazel build --config=elinux_armhf -c opt --crosstool_top=//toolchain:armv7-toolchain //tensorflow/lite:libtensorflowlite.so
Standalone code to reproduce the issue
NIL

Relevant log output
ERROR: An error occurred during the fetch of repository 'local_execution_config_python':
   Traceback (most recent call last):
        File "/mnt/c/tensorflow-2.5.0/third_party/py/python_configure.bzl", line 212, column 41, in _create_local_python_repository
                python_include = _get_python_include(repository_ctx, python_bin)
        File "/mnt/c/tensorflow-2.5.0/third_party/py/python_configure.bzl", line 152, column 21, in _get_python_include
                result = execute(
        File "/mnt/c/tensorflow-2.5.0/third_party/remote_config/common.bzl", line 219, column 13, in execute
                fail(
Error in fail: Problem getting python include path.
<string>:1: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives
<string>:1: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead
Is the Python binary path set up right? (See ./configure or PYTHON_BIN_PATH.) Is distutils installed?

These are my default python paths:
INFO: Reading rc options for 'build' from /mnt/c/tensorflow-2.5.0/.tf_configure.bazelrc:
'build' options: --action_env PYTHON_BIN_PATH=/usr/bin/python3 --action_env PYTHON_LIB_PATH=/usr/lib/python3/dist-packages --python_path=/usr/bin/python3

@Thunderzen,
There are a few more simultaneous issues... If you feel you can make progress on a root cause PR please feel free to submit one that we can review.
As a Temporary fix,  could you please try adding python definitions in the {project}/WORKSPACE file, then it might work. and Project can be built successfully.
# bazel_skylib and rules_python are from @org_tensorflow/WORKSPACE.
http_archive(
    name = "bazel_skylib",
    sha256 = "74d544d96f4a5bb630d465ca8bbcfe231e3594e5aae57e1edbf17a6eb3ca2506",
    urls = [
        "https://storage.googleapis.com/mirror.tensorflow.org/github.com/bazelbuild/bazel-skylib/releases/download/1.3.0/bazel-skylib-1.3.0.tar.gz",
        "https://github.com/bazelbuild/bazel-skylib/releases/download/1.3.0/bazel-skylib-1.3.0.tar.gz",
    ],
)

http_archive(
    name = "rules_python",
    sha256 = "9d04041ac92a0985e344235f5d946f71ac543f1b1565f2cdbc9a2aaee8adf55b",
    strip_prefix = "rules_python-0.26.0",
    url = "https://github.com/bazelbuild/rules_python/releases/download/0.26.0/rules_python-0.26.0.tar.gz",
)

# Copied from `@org_tensorflow//:WORKSPACE`.
load(
    "@rules_python//python:repositories.bzl",
    "py_repositories",
    "python_register_toolchains",
)
py_repositories()

load(
    "@org_tensorflow//tensorflow/tools/toolchains/python:python_repo.bzl",
    "python_repository",
)
python_repository(name = "python_version_repo")
load("@python_version_repo//:py_version.bzl", "HERMETIC_PYTHON_VERSION")

# Toolchain setup here is to please the TF workspace scripts,
# and we do not use this Python version to build pip packages.
python_register_toolchains(
    name = "python",
    ignore_root_user_error = True,
    python_version = HERMETIC_PYTHON_VERSION,
)

Also tensorflow v2.5 is pretty old, please try to upgrade to the latest tensorflow v2.15 or v2.16. Thank you!


Replace amchart with d3

main page
inspector view

We would like to replace amchart  with d3, any d3 experts out there?

@denzelsN @nstopkimsk any update about this?

Not yet started. @denzels  is focusing on issues related to real time charts.  after that we will consider this feature.

@nstopkimsk @denzelsN Any update replacing GO JS for server mapping real time charting?

We have no plan yet.

GoJS and Amchart are different libraries.
Amchart is replacing the ChartJS.

@denzelsN You mean replace Amchart by using ChartJS? I saw in the main page right panel, the amchart is replaced, while in inspector page, it is still showing amCharts. So the job of replacing amCharts is half done? Any plan to replace amCharts all?

Open source chart lack functionality.
So we have not yet decided on the chart replacement plan.

@emeroad What functionality? In inspector page, I used Chart.js. While it can show the 5 charts, while the 5 charts cannot show a tooltip (a boolean tip showing datasets at a time stamp) synchronized. Is this the feature lack? Is there any lack feature else?

Hi Team,
Can you please mention this limitation in Licence or tool description as we cannot use it commercially without goJS lic. Also I would like know to if any changes expected in near future to overcome this issue.
Thanks,
Khushal wadake

hi Team ,
can be replace other name with below screen.
actually we did not want to show right side in pinpoint view page
please suggest how to remove this

@prashantnitt07
sorry.
can not replace go.js yet.
You have to buy a license to get rid of the phrase.

@denzelsN @emeroad Hello, is it still not possible to use Pinpoint in production or commercially without having a go.js license?

@simoelmou  Hi
We are now developing a UI that supports the new angular.
(https://naver.github.io/pinpoint/ui_v2.html)
The new UI source supports vis.js as well as go.js


Keyboard dismisses automatically after a few seconds (Android only)

Keyboard dismisses automatically after a few seconds (Android only) after upgrading from 0.59 -> 061
React Native version:
System:
OS: macOS 10.15.1
CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 1.33 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.9.0 - ~/.nvm/versions/node/v12.9.0/bin/node
Yarn: 1.17.3 - /usr/local/bin/yarn
npm: 6.11.3 - ~/.nvm/versions/node/v12.9.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 26, 27, 28
Build Tools: 27.0.2, 27.0.3, 28.0.2, 28.0.3
System Images: android-24 | Google APIs Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom
Android NDK: 17.2.4988734
IDEs:
Xcode: 11.2.1/11B500 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
Steps To Reproduce

render

Describe what you expected to happen:
I expected the Keyboard to stay open
Snack, code example, screenshot, or link to a repository:

Figured it out ... it was a ViewPagerAndroid component that dismissed the keyboard whenever it was skipping to the next page. solved by addingkeyboardDismissMode='none' to the ViewPager.


Final Capstone

In this Milestone We:
Completed all the project requirements both in front and on the backend..
The learning objectives of this project are:

[x] Apply technical knowledge and skills gained in previous modules in a complex project.
[x] Understand pros and cons of different approaches of connecting Ruby on Rails back-end with React front-end.
[x] Understand principles of Ruby on Rails and React frameworks.
[x] Apply JavaScript best practices and language style guides in code.
[x] Apply React best practices and language style guides in code.
[x] Learn about and practice giving constructive feedback to teammates.
[x] Perform a code review for a team member.
[x] Use the "Review change"" feature from GitHub.
[x] Write clear, professional, and respectful review comments for other team members.
[x] Explain "why" a change is requested when giving a code review.
[x] Plan a 2+ week project with no interim Microverse-set milestones and submit it on time.
[x] Apply knowledge of setting working agreements to set group project teams up for success.
[x] Independently implement best practices for group agreements to improve teamwork in larger group project.
[x] Demonstrate ability to apply best practices of communication for resolving teamwork challenges.
[x] Understand that respect is the foundation of strong relationship-building with teammates.
[x] Show up throughout group projects as a reliable and committed team member who communicates and manages your time effectively.
[x] Recognize the importance of investing in good working relationships with teammates.
[x] Understand principles of strong teamwork (being reliable, committed, and consistent) and how to apply them in group projects.
[x] Recognize the value of making equal contributions to group projects to produce the best outcome.
[x] Use empty Kanban board to manage tasks with the team and own time on the project.

Here is the link to our Frontend repo: Rent-A-Car-Repo

Thanks a lot for the review @mcrd25


Introduce FluentChain class for formatting qualified expressions

This fixes several issues around formatting chains with trailing lambdas, array acccess, and the !! operator. It should also be easier to understand and extend in the future.
Right now this path is only use when --google_style is set.

importing for easier review
Can we move the branching between google and non-google styles into the FluentChain class? first, this looks like something that can benefit non-Google styles. second, I don't want big branches in the code.

Can we move the branching between google and non-google styles into the FluentChain class? first, this looks like something that can benefit non-Google styles. second, I don't want big branches in the code.

I'm not sure what that would look like. Right now, there's only one branch related to FluentChain, which is inside interceptFluentChainForGoogleStyle.
I'd be happy to have other styles use FluentChain, but I was afraid to touch the existing code related to qualified expressions. There are a lot of heuristics/special cases that I didn't want to interfere with.
Could be try to get this merged just for google-style? After that, owners of other styles can experiment with how to leverage FluentChain to fit their needs.

Since this seems to be a larger discussion, I've extracted out my key points into https://github.com/facebookincubator/ktfmt/issues/296


Add CheckpointSubmitted event

This PR adds emit of a CheckpointSubmitted event on the submit function in CheckpointManager contract.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.08%) to 82.418%

Files with Coverage Reduction
New Missed Lines
%

contracts/bridge/CheckpointManager.sol
1
94.06%

Totals

Change from base Build<PHONE_NUMBER>:
-0.08%

Covered Lines:
1283

Relevant Lines:
1509

💛  - Coveralls


npm test occasionally yields "weird error" but hangs most of the time. pump instance seems to work

node-v0.10.17 installed globally
GraphicsMagick-1.3.18 installed globally
mongodb-linux-x86_64-2.4.6 installed globally and running
pump.io 0.3.0-alpha.1 installed locally
databank-mongodb installed locally in node_modules/databank
npm test occasionally yields this:
â Errored Â» callback not fired
in When we require the event module and we get its Event class export and we create an event instance
in event module interface
in test/event-test.jsâ Errored Â» 779 honored â 1 broken â 1 errored â 3 dropped
npm ERR! weird error 1
npm ERR! not ok code 0
But most of the time it runs for some time and then hangs with the node process sleeping.
My instance seems to work nevertheless: https://pump.brunni.de/brunni
BTW: How do I do upgrades of pump.io ? Will a fresh install of a new version work with the old config file and database ?

Closing as a dupe of #1228 (even though that's the newer one) because the newer one has more info. Thanks for reporting this!


Feature Request: Verlet lists

This is not something that I need now, but it is almost certainly a feature that you'll eventually want to include. The standard (e.g. in LAMMPS and HOOMD) for fast neighbor detection is to use a combination of cell lists (which you already have) and Verlet lists, i.e. use cell lists to create and periodically update Verlet lists. I've noticed a non-negligible speedup compared to just cell lists in my own code, and for people who really care about these things, I think it's pretty important.
I would be happy to chat more about this.

Added a version of this in 65d0ecf8fd8cbbd55b5c21955b780a8aa13bd074.


Error code: 10351-4001 (Abnormal activity detected on your device's operating environment, please restart your machine.)

This error started at December 18, 2024 (I was using Yaagl since a month or two, and I have had a smooth experience using it until now)
I tried changing the wine distribution a few times, but it did not solve the issue for me. Obviously, I tried restarting and reinstalling. For the other games, Honkai: Star Rail and Zenless Zone Zero, i do not encounter this error, only in Genshin
System Information

macOS: 15.3 Beta (24D5034f)
Device: 13-inch, M1, 2020
CPU: Apple M1
RAM: 16GB
Wine Distribution: Wine 9.9 DXMT (Experimental)

game_1734583712052.log

We are aware of this issue and we think it is related to what happened on the CN server #466 .
Unlike everyone being affected by it on CN, I personally have not experienced this issue. After we confirm this can be a fix to global servers as well, we will probably push the fix. However, it is also worth noting that CN players got banned recently. So, be careful when playing.

Thank you for responding and yes, I will be careful

I have 2 accounts. All accounts are in the Asia server. Whenever I play the main account, this error occurs, but never occurs when playing the sub-account.

I have 2 accounts. All accounts are in the Asia server. Whenever I play the main account, this error occurs, but never occurs when playing the sub-account.

Can confirm, error could possibly account-related. I also have 2 accounts, both in Asia, and only one is affected by the error (but on mobile both are fine), and I always get the error right after loading the game (after white screen loading the error pops-up)

Same issue for me

having the same issue just today :(

same situation here ;-;
tried changing to:

Wine-Staging-TkG
Wine-GE-Proton
GE-Proton

none worked...

hello Im on the steam deck OLED running through the official launcher using the proton compatibility layer and connecting to the CN server I just started getting this issue today after playing perfectly fine for the past week
OS: SteamOS Holo
OS Version: 3.6.20
Proton version: 9.0-4
Genshin Server: Asia

Same thing happened to me, it just happened yesterday, i've been playing the last months without any issues

EndeavourOS
Lutris with wine-ge 8-26
Asia server

I tried changing the wine prefix location but that didn't work

Same problem ‼
• KDE Neon
• Heroic Game Launcher
• Wine GE 8-26
Starting from 20/12/24 just after new update live stream. I have been playing on Linux since way before 4.0.
Today I was able to complete the daily adventure quest, but to do the domain once I have to open the game twice.

I am playing on desktop and it is also happening to me. When will it be fixed?

Hi! Any update on this guys? I am running an anime game launcher when playing GI and this issue still keeps on popping out.

Check the new pre-release. You need to manually update. Use at your own risk.

Hi,
Thank you for replying specifically to my inquiry. If ypu don't mind brother, can you specifically direct me by sending me the link where can I manually update my launcher. I am sorry, I am quite not that techy and linux is just my familiar place.
Thank you.
Sincerely,
Brian
Yahoo Mail: Search, Organize, Conquer
On Sun, Dec 22, 2024 at 8:42 pm, @.***> wrote:
Check the new pre-release. You need to manually update. Use at your own risk.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

@feltryzyke This is for macOS. You came to the wrong repository.

Oh sorry for that.
Yahoo Mail: Search, Organize, Conquer
On Sun, Dec 22, 2024 at 8:56 pm, @.***> wrote:
@feltryzyke This is for macOS. You came to the wrong repository.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@Lzyct This is closed for a reason. If you are on macOS, check releases for pre-release. If you came from AAGL, you are in the wrong repo.

try adding -platform_type CLOUD_THIRD_PARTY_PC in the environment: it works for me and i am on linux

@UdayPrakashMinz THIS IS CLOSED FOR A REASON. THE FIX IS ALREADY THERE ON THE PRE-RELEASE FOR MACOS. FOR LINUX, YOUR FIX WORKS AND IT IS THE SAME FOR MACOS.

Many thanks! it was our Christmas gift!

@UdayPrakashMinz THIS IS CLOSED FOR A REASON. THE FIX IS ALREADY THERE ON THE PRE-RELEASE FOR MACOS. FOR LINUX, YOUR FIX WORKS AND IT IS THE SAME FOR MACOS.

Is there any fix for YAAGL os?

@SatanOPhehe bruh, you are joking right? Read the exact sentence you replied to. CHECK THE PRE-RELEASE. Go to releases. I am not replying to this issue starting from now on.


adds support for enterprise product related fields on compliance policy

Coverage remained the same at 0.671% when pulling 30a47ca43057cb85f0016c9156a6a716979bd430 on theseyi:enterprise-fields into c7d4130fab9bda7c213cf7dc9abbf015e79c642b on linkedin:master.


Throw away sasl client/server handlers after authentication

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4034/
Test PASSed.

@bf8086 PTAL. Thanks.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4043/
Test FAILed.

Jenkins, test this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4055/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/4075/
Test PASSed.

alluxio-bot, merge this please.

alluxio-bot, cherry-pick this to branch-2.0 please.


Remove version: Ruihu.Apifox version 2.4.1

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: http://cdn.apifox.com/download/2.4.1/Apifox-2.4.1.exe
Status Code: 200
(Automated message - build 896)

I approved this without fully paying attention. Feel free to revert.


GROOVY-10813: Fix NullPointerException for lambdas with raw types

I've added a test case and a fix for the bug reported in GROOVY-10813.
I'm not sure if there are any other edge cases that will now break because of this change, but one test, that failed with another solution that I tried, passes with this solution.

I relocated the lambda tests and reworked the generics tests to ensure the placeholders are not returned.
https://github.com/apache/groovy/commit/ef9b58463e83f842b56f24dff0ac4df0e02f112f


Default 'toggle' hotkey does not work

Browser: Chrome Version 65.0.3325.181 (Official Build) (64-bit)
OS: Win10

Default Alt+Shift+D does not toggle
Tried on multiple machines
If I set the same hotkey combination to other shortcuts, like "Toggle current site", it works fine. Only generic "Toggle" doesn't work

Fixed in v4.0.1


Set HTTP Strict Transport Security (HSTS) on site

http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
Configure via .htaccess:
Header set Strict-Transport-Security "max-age=31536000" env=HTTPS
This will likely cause all Acquia environments to enforce HSTS, which should actually be fine. Looking for a method to conditionally set the header via hostname, unsuccessfully.
OR
Configure via drupal module:
https://www.drupal.org/project/hsts
https://www.drupal.org/project/seckit

Attempts at configuring via .htaccess failed, likely do to Acquia hosting architecture/caching layer. Need to contact Acquia support or just use module.

I enabled the seckit module and the HSTS setting. Will be available on production on next release.


CLI Progress shows user lazily.

Issue
When making a backup, the user in question isn't displayed in a progress bar until items are queried by graph.  Ex:
Connecting to repository:     13s done
Connecting to M365:      1s done
Discovering items to backup:     21s done
∙ contacts -<EMAIL_ADDRESS>     2s done
∙ email -<EMAIL_ADDRESS>    10s done
∙ events -<EMAIL_ADDRESS>     7s done

This design made sense when backups could contain multiple resource owners.  Now that backups have a single-owner constraint, this information is both repetitious and lazily displayed.  A more effective display would be a prior header like, "Backing up<EMAIL_ADDRESS>

Closing this, we now show user at the start of a backup.


Inference isn't working with constructor that contextually types 'this' with intersections of itself

TL;DR: There should be no errors in the below example.
I am trying to model a library that takes an options bag for its constructor, and exposes those properties onto the instance that is eventually produced.
For example, if I wrote
let instance = new Component({
    methods: {
        hello() { }
        world() {
            this.hello();
        }
    }
});

I should be able to write instance.hello() or instance.world().
Additionally, since this in world will be bound to the instance, this.hello should be legal and well-typed in the above example.
However, I'm not able to come up with a version of this that works.
/**
 * Ensures all properties have a `this` param of type `T`.
 */
interface ThisEnforced<T> {
    [prop: string]: (this: T, ...args: any[]) => any;
}

interface ComponentOptions<Methods> {
    methods?: Methods
}

interface Component<Methods extends ThisEnforced<Component<Methods> & Methods>> {
    $methods: Methods;
}

interface ComponentStatic {
    new <Methods extends ThisEnforced<Component<Methods> & Methods>>(options: ComponentOptions<Methods>):
        // Returns...
        Component<Methods> & Methods;
}
declare var Component: ComponentStatic;

let inst = new Component({
    methods: {
        hello() {
            // ...
        },
        world() {
            this.hello;
            //   ~~~~~
            // Error: Property `hello` does not exist on this type.
        }
    },
});

inst.hello;
//   ~~~~~
// Error: Property `hello` does not exist on this type.

In the above example, there should be no errors - however, it appears that no inferences are being drawn as a type argument for Methods, and both this.hello and inst.hello are causing errors.

For those wondering, the reason is that the circular dependency between the type of this and the type of the object being passed in can't be supported using the way our inference process currently works.
Having discussed with @ahejlsberg, the problem is that as soon as we try to check the body of each method, the type of this is demanded. This requires type arguments that this depends on in each method (such as the Methods type argument) to be "fixed".
But since TypeScript needed to figure out the type of the methods object before it could infer the type of Methods, it never drew any inferences and just resorted to {}.

Just so that this is easier to search for, this issue is one of the bigger ones for libraries like Vue.


Not include Android dependencies

Question:
Is there a way to exclude dependencies that are related to Android?
Im thinking of not including them so that my list is not that too long and just focus on other 3rd parties other than Android.

Please have a look here: https://github.com/mikepenz/AboutLibraries#exclude-libraries

hi @mikepenz Thanks  fort his but
I tried
aboutLibraries {
    exclusionPatterns = [~"androidx_.*"]
}

But this code
val libraries = Libs(this).libraries
for (lib in libraries) {
    Log.e("AboutLibraries", "classPath=${lib.libraryArtifactId} ${lib.libraryName} from ${lib.author}")
}

still returns the the libs from  AOSP like androidx.activity:activity:1.2.3
Same for the LibsBuilder, the list still includes the excluded library.

@iadcialim thank you for the report. will be fixed in v8.9.3.


[fx_importer] segfault when trying to create a DenseResourceElementsAttr with a scalar value

Fix: 0d tensors should be special cased here as DenseElementsAttr not DenseResourceElementsAttr:
https://github.com/nod-ai/SHARK-Turbine/blob/main/core/shark_turbine/importers/fx_importer.py#L932

This was also reported by someone else a few days back but I can't remember who/where. I have not seen a patch to fix it yet.
The issue is that DenseResourceElementsAttr does not properly handle 0d tensors. While it arguably should behave better than this, it begs the question that it is the wrong thing to be doing for such a case.
The best thing to do would be to update the code listed above to special case on 1-element tensors (0d or 1d-1element) to instead generate a splat value: https://github.com/llvm/llvm-project/blob/main/mlir/lib/Bindings/Python/IRAttributes.cpp#L33
That API is more than a bit wobbly and I would recommend adding a peephole unit test for these literal conversion cases that pokes it with lasers from all sides. Here are the full upstream unit tests for it: https://github.com/llvm/llvm-project/blob/main/mlir/test/python/ir/array_attributes.py
I think if you pass DenseElementsAttr.get(array=np_tensor, type=tensor_type) it will do the right thing (i.e. conditional code after line 927 if the np_tensor has one element vs not). You can skip all of the memoryview mapping stuff in the 1-element case.


Oni exits without prompting to save

Please allow salvaging unsaved data - presently Oni exits disregarding whether a file is persisted to disk/saved.
Prevent valuable data and thus work lost by prompting to save a file.
Thank you!

Hi, thanks for logging this issue and trying out Oni!
Could you please list the steps for reproduction?

Yeah, this was filed as #264.  I agree, it does need to be fixed.  Personally, I think this is one of those things that prevents Oni from being a daily use text editor since if you accidentally close an edited file there's nothing you can do.

@keforbes I think we can close this one, right?

I think so too - closing since #264 tracks this.
Just for the record, :q<CR> does warn you.

@TalAmuyal Indeed, I tried on another machine and this behaviour is preserved, I'll investigate what's the difference, thanks!


Update ssh and sshd config highlighter from last release

I am already maintainer for the sshdconfig because the previous maintainer was not responsive. We have the same maintainer for the sshconfig, which is more updated, but is missing the latest changes too.

So, can you add yourself as maintainer for sshconfig too?

So, can you add yourself as maintainer for sshconfig too?

done

I'll include it, thanks.


refactored modules, testing, example file for using tags

This is a really big pull request, sorry about that.
I've done a big refactor of all of the modules into smaller chunks: git, tasks, project and stage. Each has tests.
I've written an integration test that actually tries to manage a real Heroku app, but it is specific to my Heroku account at the moment. I'm working on making it more general.
One of the needs at Pivotal is to use auto_tagger to move through the deploy process. I've included a sample heroku.rake file that implements that.
If you'd like to pair to merge this requests in, I'd be happy to set up a time.
Ken
<EMAIL_ADDRESS>

Awesome! Give me a bit to digest this :)

Everything looked great, but it needs upstream merged one more time.

Ok, I'll get in it today before the changes again.
Ken
Sent from my iPhone ~<PHONE_NUMBER>
On Nov 21, 2011, at 7:57 AM, Elijah<EMAIL_ADDRESS>wrote:

Everything looked great, but it needs upstream merged one more time.

Reply to this email directly or view it on GitHub:
https://github.com/fastestforward/heroku_san/pull/63#issuecomment-2816850

I've merged everything onto a separate branch, so it can be tested IRL. Look at the pivotal-merge branch for a the new hotness.


Game developer mode

This branch serves as the deploying branch on the staging server: http://stg-cadet-frontend.s3-website-ap-southeast-1.amazonaws.com

Pull Request Test Coverage Report for Build 2736

0 of 14 (0.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.08%) to 37.132%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/academy/game/game.js
0
1
0.0%

src/components/academy/game/save-manager/save-manager.js
0
1
0.0%

src/components/academy/game/story-manager/story-manager.js
0
3
0.0%

src/components/academy/game/create-initializer.js
0
9
0.0%

Totals

Change from base Build 2732:
-0.08%

Covered Lines:
2494

Relevant Lines:
6022

💛  - Coveralls

Closed because PR to wrong branch.
Sorry.


fix: fix trailing commas in JSON

Fix for https://github.com/ublue-os/bazzite/issues/1972.
Invalid JSON was causing an error whenever shell was booted.

Thanks!

There's a merge conflict with testing, if you can fix that I'll merge today for :testing

Close, I'm seeing two unrelated files being deleted

Close, I'm seeing two unrelated files being deleted

Close, I'm seeing two unrelated files being deleted

Hmm, I am not seeing that, either locally or in PR. Where are you seeing the files being deleted?

I think it was the GitHub mobile app acting up, thank you for your time

@KyleGospo would you be open to follow up to add JSON linting to your pipeline to help contributors catch errors like this?

Absolutely, more QC the merrier


iPad Settings Crash.

Tapping the "box with arrow" crashes the Settings app on iPads. The logs are provided below.
Thanks! ^_^
Crash: https://ghostbin.com/paste/re5rn
Syslog: https://ghostbin.com/paste/3bubb

This is actually a bug in Cephei. Moved to https://github.com/hbang/libcephei/issues/6.


WWW_DIR → WWW_ROOT

Coverage remained the same at 90.82% when pulling 293edddfcafabb71d8361630226b3d3d506d8bfc on Schlaefer:patch-1 into d4776a632f2dde2f9d5cc0c1d471e33cf4f46def on davidyell:master.

Thanks for your PR, but please can you target the develop branch.

closed in favor of #96


Backport: #17866 Allow setting lifecycle to proxy containers

This is backport of https://github.com/istio/istio/pull/17866
Signed-off-by: Dinar Valeev<EMAIL_ADDRESS>

Hi @k0da. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

It looks like this is a back port of #17866.

/ok-to-test

@ericvn yup

As mentioned in #17866 we would want a cherry pick of https://github.com/istio/installer/pull/605 to keep things in sync.

@ericvn istio/installer#605 got merged

@k0da But does it need to be cherrypicked as well?

@ericvn to installer 1.4 branch?

@k0da Yes, if think so. As I understand it, correct me if I'm wrong, we had #17866 and https://github.com/istio/installer/pull/605 as a pair of PRs across repos that went into master. If we back port this to 1.4, shouldn't we back port the pair?

@ericvn sure, makes sense now to me. We just don't use installer (yet) and our use case is old fashioned helm chart. Opened backport PR https://github.com/istio/installer/pull/609


feat: Ability to customise default environments for new project

Thanks for submitting a PR! Please check the boxes below:

[x] I have run pre-commit to check linting
[x] I have added information to docs/ if required so people know about the feature!
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?
[x] I have used a Conventional Commit title for this Pull Request

Changes
This PR adds the default_environment_names_for_new_project FoF flag to customise default environment names when creating a new project.
How did you test this code?
Ran the build locally.

I ran the e2e tests locally, and they failed.

@novakzaballa Found the error and fixed it!

@novakzaballa The default value will be used for SaaS. The flag is intended for private/self-hosted installations.


fix: the judgement of the resource drifted

Signed-off-by: Bird<EMAIL_ADDRESS>Pre-Checklist
Note: please complete ALL items in the following checklist.

[x] I have read through the CONTRIBUTING.md documentation.
[x] My code has the necessary comments and documentation (if needed).
[x] I have added relevant tests

Description
See #975 for details.

maybe the file test_drifted_state could have a better name.

Thank you, done.


New release to support Debian packaging of elfx86exts?

Hello,
I'm packaging elfx86exts for Debian and it would be helpful if you could make a release with your updated dependency on the newer capstone cargo version 0.7
https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/108
Thanks!

Sure thing. Version 0.4.0, now on crates.io and GitHub. I'll close this issue but please feel free to reopen or comment if you have any follow-ups.

PS. Also, if you wouldn't mind submitting a PR to add the Debian info to the README.md once the package is finalized, that would be great!

A 2021 update: the review for entry into the Debian development distribution has been queued up! https://ftp-master.debian.org/new/rust-elfx86exts_0.3.0-1.html

Thanks for the update!


Add Oracle Cloud Simple Functions Guide

Fixed by https://github.com/micronaut-projects/micronaut-guides/pull/275


feat: GraphQL resolvers and schema for Webpack Module Graph

Creating a queryable schema for pulling information out of webpack

@ScriptedAlchemy I see that an e2e app is also been added but there are no changes related to the webpack GQL package. Is this intentional??
Can we remove the app if we aren't using it?


Merge data and errors into response body instead of re-assign

Hello. This module works pretty well. I am suggesting an enhancement. After executing and resolving GraphQL, the results are assigned to the response.body https://github.com/chentsulin/koa-graphql/blob/master/src/index.js#L294-L296.
This will overwrite any other information that the server might have set. There may be additional information we want to send down that isn't part of the schema. Perhaps instead of a reassignment, it could attempt an object merge so that the developer can send down other information. I've put in PR #103 for this suggestion.

IMO, this should be done by one of middleware before koa-graphql middleware:
app.use(async (ctx, next) => {
  await next();

  ctx.body = Object.assign({}, ctx.body, {
    // some others...
  });
});

app.use(graphqlHTTP({
  schema: MyGraphQLSchema,
}));

Otherwise, we should rewrite every middleware to support merging body.


Setup for readthedocs

Clone/adapt from https://github.com/TileDB-Inc/TileDB-Py

thanks @ihnorton !!