Specifying some arguments of a simp theorem can make it unapplicable

...because remaining metavariables do not participate in matching
axiom p {α β} : α → β → Prop
axiom foo {α β} (a : α) (b : β) : p a b

example : p 0 0 := by simp [foo]  -- works
example : p 0 0 := by simp [foo 0]  -- fails
example : p 0 0 := by simp [foo 0 0]  -- works

TC resolution should probably be delayed as well
axiom p {α} : α → Prop
axiom foo {α} [ToString α] (n : Nat) (a : α) : p a

example : p 0 := by simp [foo 0]  -- fails at elaborating the argument


Finds peers and connects, but won't download

What version of WebTorrent Desktop? (See the 'About WebTorrent' menu)
Version 0.8.1 (0.95.2)
What operating system and version?
Ubuntu 14.04 (i686)

I have a torrent of my own content (magnet:?xt=urn:btih:dc251a62ace7ee0ff24bb59b79ba79b6e7a019f7&dn=2016202%2000%20%E2%80%94%20Forematter) that I am testing with.  There are three seeds (one is me, and two are people I know who downloaded the torrent from my initial seed).  WebTorrent Desktop finds all three seeds, and if I look at my seed it even connects, but transmission-daemon alternates between uI or uKI, that is, WebTorrent Desktop has connected to my seed and just isn't asking for anything.  So the download never progresses.  I know the seed works because two people have downloaded it already.

https://github.com/feross/webtorrent-desktop/issues/699

This is definitely a bug and we hope to have it fixed soon.

Closing as a duplicate of #699
Also, it's probably a bug in the underlying library: https://github.com/feross/webtorrent

Re-opening because issue #699 was locked.

@singpolyma Roughly how large is the torrent of your own content that you're using?

500 MB range

@dcposch This eliminates my theory that this was caused by extremely large torrents where the piece size is larger than 2GB. I think this is a bug in WebTorrent.
This issue is tracking the bug in the underlying library, so I'm going to close it here now: https://github.com/feross/webtorrent/issues/850


hipBlastLT build failed with msgpack error even though it is installed

Using ROCm-6.0 release
pip3 list | grep -i msgpack
msgpack                       1.0.8
Also did pip install -r .sphinx/requirements as instructed in the README.

./install.sh --clients
Creating project build directory in: /root/extdir/gg/git/codelab-scripts/build-install-scripts/rocm/ROCm-6.0/hipBLASLt/build
/home/rocm/ROCm-6.0/hipBLASLt /home/rocm/ROCm-6.0/hipBLASLt
/home/rocm/ROCm-6.0/hipBLASLt/build/release /home/rocm/ROCm-6.0/hipBLASLt/build/release /home/rocm/ROCm-6.0/hipBLASLt
/home/rocm/ROCm-6.0/hipBLASLt/build/release /home/rocm/ROCm-6.0/hipBLASLt
-DAMDGPU_TARGETS=all -DCMAKE_BUILD_TYPE=Release
-- The CXX compiler identification is Clang 17.0.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /opt/rocm/bin/hipcc - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Using hip-clang to build for amdgpu backend

*******************************************************************************
*------------------------------- ROCMChecks WARNING --------------------------*
  Options and properties should be set on a cmake target where possible. The
  variable 'CMAKE_CXX_FLAGS' may be set by the cmake toolchain, either by
  calling 'cmake -DCMAKE_CXX_FLAGS=" -D__HIP_HCC_COMPAT_MODE__=1"'
  or set in a toolchain file and added with
  'cmake -DCMAKE_TOOLCHAIN_FILE=<toolchain-file>'. ROCMChecks now calling:
CMake Warning at /opt/rocm/share/rocm/cmake/ROCMChecks.cmake:46 (message):
  'CMAKE_CXX_FLAGS' is set at
  /root/extdir/gg/git/codelab-scripts/build-install-scripts/rocm/ROCm-6.0/hipBLASLt/CMakeLists.txt:<line#>
  shown below:
Call Stack (most recent call first):
  CMakeLists.txt:9223372036854775807 (rocm_check_toolchain_var)
  CMakeLists.txt:130 (set)

*-----------------------------------------------------------------------------*
*******************************************************************************

-- Found Git: /usr/bin/git (found version "2.43.0")
CMake Warning (dev) at cmake/findBLIS.cmake:41 (set):
  Cannot set "BLIS_FOUND": current scope has no parent.
Call Stack (most recent call first):
  CMakeLists.txt:141 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at cmake/findBLIS.cmake:42 (set):
  Cannot set "BLIS_INCLUDE_DIR": current scope has no parent.
Call Stack (most recent call first):
  CMakeLists.txt:141 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at cmake/findBLIS.cmake:43 (set):
  Cannot set "BLIS_LIB": current scope has no parent.
Call Stack (most recent call first):
  CMakeLists.txt:141 (include)
This warning is for project developers.  Use -Wno-dev to suppress it.

BLIS heeader directory found: /root/extdir/gg/git/codelab-scripts/build-install-scripts/rocm/ROCm-6.0/hipBLASLt/build/deps/blis/include/blis
BLIS lib found: /root/extdir/gg/git/codelab-scripts/build-install-scripts/rocm/ROCm-6.0/hipBLASLt/build/deps/blis/lib/libblis.a
-- Performing Test COMPILER_HAS_TARGET_ID_gfx90a_xnack_on
-- Performing Test COMPILER_HAS_TARGET_ID_gfx90a_xnack_on - Success
-- Performing Test COMPILER_HAS_TARGET_ID_gfx90a_xnack_off
-- Performing Test COMPILER_HAS_TARGET_ID_gfx90a_xnack_off - Success
-- Performing Test COMPILER_HAS_TARGET_ID_gfx940
-- Performing Test COMPILER_HAS_TARGET_ID_gfx940 - Success
-- Performing Test COMPILER_HAS_TARGET_ID_gfx941
-- Performing Test COMPILER_HAS_TARGET_ID_gfx941 - Success
-- Performing Test COMPILER_HAS_TARGET_ID_gfx942
-- Performing Test COMPILER_HAS_TARGET_ID_gfx942 - Success
-- AMDGPU_TARGETS: gfx90a:xnack+;gfx90a:xnack-;gfx940;gfx941;gfx942
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Performing Test HIP_CLANG_SUPPORTS_PARALLEL_JOBS
-- Performing Test HIP_CLANG_SUPPORTS_PARALLEL_JOBS - Success
/usr/bin/python3 -m venv /root/extdir/gg/git/codelab-scripts/build-install-scripts/rocm/ROCm-6.0/hipBLASLt/build/release/virtualenv --system-site-packages --clear
/home/rocm/ROCm-6.0/hipBLASLt/build/release/virtualenv/bin/python3 -m pip install /home/rocm/ROCm-6.0/hipBLASLt/tensilelite
Processing /home/rocm/ROCm-6.0/hipBLASLt/tensilelite
  DEPRECATION: A future pip version will change local packages to be built in-place without first copying to a temporary directory. We recommend you use --use-feature=in-tree-build to test your packages with this new behavior before it becomes the default.
   pip 21.3 will remove support for this functionality. You can find discussion regarding this at https://github.com/pypa/pip/issues/7555.
Requirement already satisfied: pyyaml in /usr/local/lib64/python3.9/site-packages (from Tensile==4.33.0) (6.0)
Requirement already satisfied: msgpack in /usr/local/lib64/python3.9/site-packages (from Tensile==4.33.0) (1.0.8)
Requirement already satisfied: joblib in /usr/local/lib/python3.9/site-packages (from Tensile==4.33.0) (1.3.2)
Using legacy 'setup.py install' for Tensile, since package 'wheel' is not installed.
Installing collected packages: Tensile
    Running setup.py install for Tensile: started
    Running setup.py install for Tensile: finished with status 'done'
Successfully installed Tensile-4.33.0
WARNING: You are using pip version 21.2.3; however, version 24.0 is available.
You should consider upgrading via the '/home/rocm/ROCm-6.0/hipBLASLt/build/release/virtualenv/bin/python3 -m pip install --upgrade pip' command.
-- Adding /home/rocm/ROCm-6.0/hipBLASLt/build/release/virtualenv to CMAKE_PREFIX_PATH
-- The C compiler identification is GNU 11.4.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
CMake Error at build/release/virtualenv/lib64/python3.9/site-packages/Tensile/Source/lib/CMakeLists.txt:105 (find_package):
  By not providing "Findmsgpack.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "msgpack", but
  CMake did not find one.

  Could not find a package configuration file provided by "msgpack" with any
  of the following names:

    msgpackConfig.cmake
    msgpack-config.cmake

  Add the installation prefix of "msgpack" to CMAKE_PREFIX_PATH or set
  "msgpack_DIR" to a directory containing one of the above files.  If
  "msgpack" provides a separate development package or SDK, be sure it has
  been installed.

Please try apt-get install -y libmsgpack-dev and reinstall the Python msgpack to see if it works.

it is redhat not ubuntu

@jdgh000 Please try ./install.sh -d --clients

@jdgh000 Has this issue been resolved for you? Thanks!

I initially had the same error on Ubuntu 24.04 + rocm 6.2 with gfx908, installing libmsgpack-dev and running the script with -d to install other dependencies resolved the issue. Unsure if the manual package installation was actually necessary or would have been picked up by the script.

I initially had the same error on Ubuntu 24.04 + rocm 6.2 with gfx908, installing libmsgpack-dev and running the script with -d to install other dependencies resolved the issue. Unsure if the manual package installation was actually necessary or would have been picked up by the script.

libmsgpack-dev installation is part of -d
https://github.com/ROCm/hipBLASLt/blob/182e0f5c8e5499d00bd513e0d33cb991a15470c6/install.sh#L175

Great, looks like simply running -d is the complete solution then.

@ppanchad-amd t
May you open the issue ?

The install.sh will install libmsgpack, right ?  If so, then apt-get install -y libmsgpack-dev  is not the solution, right ?
Please explain why sudo permission is needed when using install.sh

Thanks


Add yield to emergency vehicle scenario

Description

Add YieldToEmergencyVehicle scenario. Along with WaitForTime(AtomicCondition) and YieldToEmergencyVehicleTest(Criterion).
Fixes #
Where has this been tested?

Platform(s): Ubuntu 20.04
Python version(s): 3.7
Unreal Engine version(s): 4.26
CARLA version: leaderboard-2.0 branch

Possible Drawbacks

This change is

Some feedback after testing:
The BasicAgent behavior is a bit cluncky, and the EV can sometimes collide with the ego. Also, if the ego is too fast, the EV might never catch it. This is specially true for ambulances and firetrucks. Maybe you can use the ConstantVelocityAgent? That might be too unrealistic though, as it stops instantaneously.
The current version of the YieldToEmergencyVehicleTest will miss fail if the ego is faster than the EV and making it a total miss of hit with the 15 seconds is a bit weird. It just occured to me to do the following. What we care about is how much did the ego block the EV, so record the target speed and compare it to its actual one, how bad the ego did it is proportional to that value.
Lastly, after testing this I found out that scenario specific criteria were making the route stop (which shouldn't be the case) so I've updated the leaderboard-2.0 branch

@glopezdiest

Maybe you can use the ConstantVelocityAgent? That might be too unrealistic though, as it stops instantaneously.

I've tried to do it. It shows that the EV will rear-end the ego initially if the ego is not that fast. I will try to make it work better anyway.

What we care about is how much did the ego block the EV, so record the target speed and compare it to its actual one, how bad the ego did it is proportional to that value.

That make sense. Will try it.

Lastly, after testing this I found out that scenario specific criteria were making the route stop (which shouldn't be the case) so I've updated the leaderboard-2.0 branch

Yeah! I was confused about this, and I thought it was somehow a bug of the scenario before. Thanks for the fix.

I forgot to mention, add the special lights to the EV! Should be somethign like this


[EventHubs] Event Processor should provide checkpoint support

Summary
Track One's Event Processor Host creates checkpoints upon user request so the same events don't get processed multiple times. When the responsibility for a certain partition is given to an Event Processor Host, it searches for any existing checkpoint so it can resume event processing from the oldest unprocessed event possible.
The current implementation of Track Two's Event Processor does not support this feature.
Goal
Implement checkpoint support in Track Two's Event Processor:

Changes in the EventProcessor class must be done to ensure that new PartitionPumps will start processing events from the stored checkpoint, if it exists.
InMemoryPartitionManager should provide proper checkpoint creation as well.

Solved by: #7508


Error after updating Windows

ℹ Computer information

PowerToys version: <IP_ADDRESS>
Running PowerToys as Admin: yes
Windows build number: Windows 10 20H2 (19042.867)

📝 Provide detailed reproduction steps (if any)

Update Windows to latest available stable version
Powertoys Run throws an error message on startup

✔ Expected result
No issues after startup
❌ Actual result
A window with an error appears right after startup.
Provided Log
OS Version: Microsoft Windows NT 10.0.19042.0
IntPtr Length: 8
x64: True
Date: 12/03/2021 10:52:06
Exception:
System.IO.FileNotFoundException: Could not find file 'C:\Program Files\PowerToys\modules\launcher\Images\app.dark.png'.
File name: 'C:\Program Files\PowerToys\modules\launcher\Images\app.dark.png'
   at System.IO.FileStream.ValidateFileHandle(SafeFileHandle fileHandle)
   at System.IO.FileStream.CreateFileOpenHandle(FileMode mode, FileShare share, FileOptions options)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at System.Windows.Media.Imaging.BitmapDecoder.SetupDecoderFromUriOrStream(Uri uri, Stream stream, BitmapCacheOption cacheOption, Guid& clsId, Boolean& isOriginalWritable, Stream& uriStream, UnmanagedMemoryStream& unmanagedMemoryStream, SafeFileHandle& safeFilehandle)
   at System.Windows.Media.Imaging.BitmapDecoder.CreateFromUriOrStream(Uri baseUri, Uri uri, Stream stream, BitmapCreateOptions createOptions, BitmapCacheOption cacheOption, RequestCachePolicy uriCachePolicy, Boolean insertInDecoderCache)
   at System.Windows.Media.Imaging.BitmapImage.FinalizeCreation()
   at System.Windows.Media.Imaging.BitmapImage.EndInit()
   at System.Windows.Media.Imaging.BitmapImage..ctor(Uri uriSource, RequestCachePolicy uriCachePolicy)
   at Wox.Infrastructure.Image.ImageLoader.Initialize(Theme theme)
   at PowerLauncher.App.<>c__DisplayClass14_0.<OnStartup>b__0()
   at Wox.Infrastructure.Stopwatch.Normal(String message, Action action)
   at PowerLauncher.App.OnStartup(Object sender, StartupEventArgs e)
   at System.Windows.Application.OnStartup(StartupEventArgs e)
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

@halkliff
Can you make a screen of C:\Program Files\PowerToys\modules\launcher\Images folder?

It looks like app.dark.png is not present.

Here you are

Here you are, it indeed is not present.

@halkliff
I suspect reinstalling of PowerToys would help.

@mykhailopylyp
Funny way to fix it, but why not 😆
Will do and, if fixed, will close the issue.

Closing this issue as reinstalling fixes it.
It is worth nothing though, that this issue happened after a Windows update, and as far as I'm concerned, lesser Windows updates should not break applications by deleting their files. It is a corruption error, and perhaps should be investigated by the OS team in a near future.
Thanks for the help, and cya!


Adds a document outlining Events

Summary
Introduces a document describing how to use Events
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

Would it be more accurate to call these Message metadata types rather than events? That they're called events makes it seem like we'd define them in an events folder, but based on what they are, I wonder if it would be more appropriate to put them in a types folder?

Also posted a Q here about using Custom types:
Trying to get Custom types and DefineEvent to work correctly, but it seems like I'm missing something:

I created a custom type IncidentType
If I create an event with DefineEvent that has type Schema.types.object with properties identical to IncidentType , then hermes run works as expected
If I change the type to IncidentType, despite all properties being identical, I receive the following error when trying to execute hermes run: failed to match exactly one allowed schema\nSource: /events/incident

Would it be more accurate to call these Message metadata types rather than events? That they're called events makes it seem like we'd define them in an events folder, but based on what they are, I wonder if it would be more appropriate to put them in a types folder?

I think the longer term vision is that they do become more of an event primitive of the platform, and have some discoverability around them as well. This led to them being defined under the events property on the app manifest. I think there's value in keeping the naming consistent with how we've chosen to identify them as part of an app's manifest. I agree it isn't obvious how they connect to message metadata "event_type" matching in the current state of things though, but longer term I hope that becomes more clear or less necessary for someone to know about.


 I've installed Planck via NPM, but I can't work out how to link the script in correctly.
On likely related topic, when I link Planck in via the CDN, it dies at the first use of Vec2 (in the world creation copied from the tutorial) unless I change it to planck.Vec2. That would suggest that it's not aliasing object names correctly.
Any help would be much appreciated.

Right, after much work, I can tell those who come after me that they need to be using Webpack/Browserify/ some other module-to-webcode Node utility. Then it's as 'simple' as reverse-engineering testbed/server.js and package.json. My webpack.config.js ended up looking like this, which I call through 'webpack --config-name static_planck' in the project folder in the command line.
This outputs a nice web-safe, script-includable .js file. Which still doesn't seem to work as the example code on this repo would suggest, because it still wants me to preface Vec2 with the planck namespace. So I have successfully reached the point of badly replicating the CDN.
Still. Progress!

You are right, adding one of those files is enough. All classes are name-spaced to avoid polluting global scope, please feel free to fix Vec2 in tutorial if required.


Dump junit xml

Closes https://github.com/temporalio/sdk-go/issues/1633

As in https://github.com/temporalio/sdk-python/pull/617 and https://github.com/temporalio/cli/pull/650, I propose to modify the test suite to output junit XML. The motivation for this is that, given appropriate tools, it will make it easier for us to study patterns of flakiness, test timings etc, across matrix builds within a run, and across runs. Producing the files now will allow us to test tools for doing this.

@Quinn-With-Two-Ns To output junit XML I had to switch to using gotestsum. One question here is are you OK with the new test output format from gotestsum? From a quick look it appears that one big difference is that output from successful tests is hidden by default. I was optimistic that we'd be OK with this switch since https://github.com/temporalio/temporal uses it, and it looks like it's quite configurable, and fairly widely used by high profile Go projects: https://github.com/gotestyourself/gotestsum

No concern about the test format. Question about the general PR though, from the issue it says

The motivation for this is that, given appropriate tools, it will make it easier for us to study patterns of flakiness

Does that appropriate tool exist yet today?

Does that appropriate tool exist yet today?

Good question. I couldn't find something that would work well, e.g. correlating tests across our matrix builds, so I've started creating our own from scratch. I'm not quite ready to have others test it (but absolutely welcome any help developing it).


Fix rule update bug

Fixed bug where revision was not incrementing on rule updates and added some UTs to check for similar issues.

Resolves https://github.com/amalgam8/amalgam8/issues/361.

Contributes to #354.


Add tracking of out-of-lane entities

Currently, if a vehicle has right of way it will not stop for vehicles in front of it. We should augment the IDM tracker to include vehicles that are not in the same lane and do not have right of way

Fixed by #6


Support non-integer primary key in shorthand function

Rather than rely on the documentation, I figure why not support this directly?
It has the nice benefit of making the generated SQL syntax match what you'd write by hand, though it doesn't really change the functionality.
Included test of String primary key and custom type primary key.

It has the nice benefit of making the generated SQL syntax match what you'd write by hand, though it doesn't really change the functionality.

Using the column constraint actually does still match (and is required for composite keys, for example).
This was actually originally a design decision. The assumption being that integer primary keys were the most common and to avoid the mistake of passing in just anything. This makes less sense now in hindsight, though, especially given that .Autoincrement is supported.
Let me check this out in the evening to make sure it doesn't create any ambiguity depending on how the functions are called. Leaving a few minor style comments in the meantime.

Hey, I'd love to merge this in but it's off the swift-1-2 branch instead of master. Do you think you could re-open it against master, instead? Or would you rather me commit the changes myself and close this when I'm done?

@stephencelis My assumption was that swift-1-2 will merge into or replace master when the next version releases. How are you handling merging changes into swift-1-2?
Next week I'm going to try to submit a PR to add a few things to Database like WAL mode checkpointing, but I'm only using the swift-1-2 branch since I'm doing my new app on the beta

Closing in favor of #78. Will rebase swift-1-2 soon.


AWS Layers: Unresolved resource dependencies [PythonRequirementsLambdaLayer]

I'm trying to use AWS Layers, but by the size of each lambda function packet you can realize that all third-party libraries (from the requirements.txt files) were packed together.
At the end of each process, I'm getting this error:

The CloudFormation template is invalid: Error in template format: unresolved resource dependencies [PythonRequirementsLambdaLayer] in template Features block

My serverless.yml:
custom:
  ...
  pythonRequirements:
    layer: true

package:
  individually: true
  exclude:
    - ./**

function1:
  module: module/channels
  handler: f1/hook.received_data
  vendor: ./common
  package:
    include:
      - module/channels/f1/hook.py
  layers:
    - {Ref: PythonRequirementsLambdaLayer}

function2:
  module: module/users
  handler: f2/singup.sing_up
  memorySize: 128
  vendor: ./common
  package:
    include:
      - module/channels/f2/hook.py
  layers:
    - {Ref: PythonRequirementsLambdaLayer}

Hmm. I don't think the layers option is compatible with individual packaging

Wow. But I think it loses the meaning of this library, which I use exactly to separate in modules, implement layers without module.

I'll gladly accept a PR adding support.

Hi, is anyone working on this ? I would love to see it implemented. If not, maybe I can try.

Hi,
If I define PythonRequirements layer in the same stack (written in the same serverless.yml file) the Ref should normally work according to serverless documentation:
https://serverless.com/framework/docs/providers/aws/guide/layers#using-your-layers
However I get the same error

The CloudFormation template is invalid: Error in template format: unresolved resource dependencies [PythonRequirementsLambdaLayer] in the Ressources block of the template

@Mzem that's an unfortunate side effect of how retain: true has to be implemented due to limitations in cloudformation. See https://github.com/serverless/serverless/pull/6010 for more discussion about it.

@crichon, no one is working on that AFAIK, feel free to take a stab at it!

Damn, this retain feature not make sense without export working correct...... So is there a way to reference one output value to another output value? Ref: TestLambdaLayerQualifiedArn seems logic for me but it is not working for some reason

Hey 👋 I'm closing this ticket as it looks like it's heavily outdated, we can of course reopen it if needed 👍


Understand how eks-node-viewer obtain the metrics

Hello,
First of all , thanks to share this tool with community :-)
This is not an issue it's only a question, because I tested with a EKS cluster running inside AWS and the results don't match with others tool like top, htop etc....

As you can see in the screenshot I understand that the pods are using a lot of CPU but in other hand I can see that we are not using a lot of memory.
In the next screenshot we can see the result of HTOP command.

Here the result it's totally true compared with eks-node-viewer info, the memory is very low comparing with the total. --> 6.63GB of 30.9GB
But as you can see the CPU is not very high... for me is strange because in eks-node-viewer it said that is around 94%...
Here other screenshot about kubectl top nodes.

Maybe eks-node-viewer check the CPU sum for deployments?¿ Only take the limits? Because is reserved to the pods?¿

Please would be possible to explain a little bit how to interpreter the results?
Thanks!! :-)

I checked eks-node-viewer too. The values are not correct.

I commented above, but the eks-node-viewer shows the pod requests only. It doesn't look at the actual resources used by the pods.


Update supported Python versions to 3.9-3.11

Description
On April 14, NEP 29 recommends Python 3.9+
Checklist

[ ] Add tests
[ ] Lint
[x] Update docstrings

Needs AmberTools packages to be updated with 3.11 support

Since there's less than a week between the planned 0.3.0 release (April 10) and this change coming into effect (April 14) I'm just going to merge now.


pivpn not working with pihole + ftldns

PiVPN is no longer maintained, see the README

PiVPN Issue Template

Issue
had a pi with pi hole and ftldns running successfully. wanted to try and put pivpn (openvpn) on there to make it more useful. for the life of me cant troubleshoot why it is not working. openvpn connect on my android fails to connect.
i have a feeling it may be due to the fact that my resolv.conf has nameserver set as <IP_ADDRESS>
has anyone been successful with this setup before? any help is super appreciated. thanks in advance.
Have you searched for similar issues and solutions?
(yes/no / which issues?)

yes, pivpn install on pi with pihole
Console output of curl -L install.pivpn.io | bash
  Output Here

Console output of pivpn add or pivpn add nopass
  Output Here

Console output of pivpn debug
 ::: Generating Debug Output
:::                                     :::
::              PiVPN Debug              ::
:::                                     :::
::      Latest Commit                    ::
:::                                     :::
commit 84cd315a522d99717cc4f103c5870b8d014bf846
Author: redfast00<EMAIL_ADDRESS>Date:   Tue Jan 29 11:16:48 2019 +0100

    So long and thanks for all the fish
:::                                     :::
::      Recursive list of files in       ::
::      /etc/openvpn/easy-rsa/pki        ::
:::                                     :::
/etc/openvpn/easy-rsa/pki/:
ca.crt
crl.pem
Default.txt
ecparams
index.txt
index.txt.attr
index.txt.attr.old
index.txt.old
issued
private
serial
serial.old
user.ovpn
ta.key
user2.ovpn

/etc/openvpn/easy-rsa/pki/ecparams:
prime256v1.pem

/etc/openvpn/easy-rsa/pki/issued:
server_generatedtext.crt
user.crt
user2.crt

/etc/openvpn/easy-rsa/pki/private:
ca.key
server_generatedtext.key
user.key
user2.key
:::                                     :::
::      Output of /etc/pivpn/*           ::
:::                                     :::
:: START /etc/pivpn/DET_PLATFORM ::
Raspbian
:: END /etc/pivpn/DET_PLATFORM ::
:: START /etc/pivpn/INSTALL_PORT ::
12221
:: END /etc/pivpn/INSTALL_PORT ::
:: START /etc/pivpn/INSTALL_PROTO ::
udp
:: END /etc/pivpn/INSTALL_PROTO ::
:: START /etc/pivpn/INSTALL_USER ::
dietpi
:: END /etc/pivpn/INSTALL_USER ::
:: START /etc/pivpn/NO_UFW ::
1
:: END /etc/pivpn/NO_UFW ::
:: START /etc/pivpn/pivpnINTERFACE ::
eth0
:: END /etc/pivpn/pivpnINTERFACE ::
:: START /etc/pivpn/TWO_POINT_FOUR ::
:: END /etc/pivpn/TWO_POINT_FOUR ::
:::                                     :::
:: /etc/openvpn/easy-rsa/pki/Default.txt ::
:::                                     :::
client
dev tun
proto udp
remote noip generated address 12221
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
tls-version-min 1.2
verify-x509-name server_rhOLT9p0kkjxehiK name
cipher AES-256-CBC
auth SHA256
auth-nocache
verb 3
:::                                     :::
::      Debug Output Complete            ::
:::                                     :::
:::
::: Debug output completed above.

Post the output of sudo cat /etc/openvpn/easy-rsa/pki/Default.txt, then try to connect to vpn then post the output of tail -50 /var/log/openvpn.log
You may want to censor the IP in bot files.

Hi,
I tried pihole and pivpn on the same pi but gave up. Put pihole on separate machine. But in the end stopped using pihole as lots of sites didn't like it. Now use no-script with Firefox.
That was my solution.
Adrian


Codeforces Round #644 (Div. 3) [Haskell]

For fun, I solved this contest using Haskell.

This is really cool, this is the first haskell code in the repo and I hope we get more :D
I'm gonna check the code and try to make some comments before I accept the PR just let me fully wake up :P

Unrelated question: wouldn't it be better for filenames to start with the contest name so that it is easier to find related solutions?

Yes, actually the problems from atcoder are named like that, let's change it for the codeforces too starting with these :D

btw @unihernandez22 just changed the name of the codeforces' files to the new naming convention :D


V2

This is a draft PR for the V2 branch.
This is extremely work in progress.
Here are the objectives of V2:

Unified message bus and simplified clients
We'll be refactoring all clients to handle input and output only, with an event bus to hook in response handlers.
Clients will have dramatically less code, and agents will be able to send messages across clients. This will also enable autonomous agent to unify all input and outputs into a single stream of thought and action.

Unified agent wallet
The current wallet system reflects the way we use humans use wallets today, but the UX around network switching and wallet management is a pain. Instead, the agent will have a unified wallet, with access to all registered chains at once. No wallet switching, and tokens will all be handled by agents in a unified way.

Model Provider Registry
The current model provider system requires a pull request to core for every model provider. v2 will have a registry and override pattern so new code doesn't need to be added to core, and any provider can quickly override with a few lines of code to add integration without a pull request.

Extensible and generic core framework
The v1 is very opinionated about prompts, state and some features. v2 will be very extensible so you can create different kinds of agents and override state management and context composition. For advanced developers, this will make the framework far more powerful and flexible for different user cases.

Community plugins
We'll be moving community plugins out of core and adding requirements for plugin inclusion in core around test coverage, documentation and code maintenance and ownership.

Better secret management
Currently, secret management in .env and character files is risky, so considering better and more secure options for this

100% Test Coverage
v2 reflects what we want Eliza to be, and we feel that after these changes we should focus entirely on stability, security and cutting down on issues. We'll be aiming for 100% test coverage of core, adapters and primary components, and end-to-end tests for clients.

For message bus - consider long term that we may want a way to coordinate different sovereign agents to interact with each other, so any design should consider this possibility.  The message bus as scoped is internal to the agent for v2, but maybe there's just a little bit of design that we can do upfront to more easily support cross-agent coordination in the future.
Here's some detail considerations to consider (from Sonnet FYI):
Message namespacing that could later accommodate agent IDs
Message routing infrastructure that could be extended beyond a single agent's boundary
Serialization formats that would work across different environments
Authentication/authorization hooks that could later be used for inter-agent security

SOPS might be a good tool for secrets management: https://github.com/getsops/sops
btw, we are cooking a more advanced TEE plugin for Eliza that also uses SOPS for secure initialization: https://github.com/comrade-coop/aapp-toolkit


Allow null names for artifacts

To allow artifacts without names -
Refactored Artifact type to be an array of artifacts with name properties instead of a dictionary.
To test

cd metaflow/plugins/cards/ui
yarn dev
Go to the URL in the output
Look at the first row of the Artifacts table to see that it doesn't have a name

looks good. I'm assuming this request is because an artifact can have a null name? should we be using ID's or anything?

Valay requested the ability to have artifacts without names, and gave this schema. I could see a use for UUID's or something for ID's in the future


Delete CHANGELOG.md in favor of GitHub Releases

As long as the existing changelog is retrofitted onto github releases. E.g. we go back and make release for previous versions with the changelog.

Yes, that is the key.

Or as part of the release process we create a changelog from the github releases.


Session information is not recreated after network failure recovery

What happened:
We injected a 5 minute network failure at a certain node. After the fault is restored, the exception below will always be reported
2023/01/13 15:06:57.651702 juicefs[3896811] <ERROR>: update session: no session found matching sid: 969 [sql.go:1904]

the sid=969 has been cleared in meta-store, but the mount client has not recreated the session.
What you expected to happen:
mount client can recreated the session information after Network failure recovery
How to reproduce it (as minimally and precisely as possible):
injected a 5 minute network failure to meta-store
Anything else we need to know?
Environment:

JuiceFS version (use juicefs --version) or Hadoop Java SDK version: juicefs version 1.0.3+2022-12-27.e4bf15a
Cloud provider or hardware configuration running JuiceFS:
OS (e.g cat /etc/os-release):
Kernel (e.g. uname -a):
Object storage (cloud provider and region, or self maintained):
Metadata engine info (version, cloud provider managed or self maintained):
Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
Others:

The session will be recreated for sql with #3190, just like that in redis/tkv.


Numerical issue with the local AHS simulator

Describe the bug
Braket emulator crashes  for a system of 10 atoms, with the error:
File "/usr/local/lib/python3.10/dist-packages/braket/analog_hamiltonian_simulator/rydberg/rydberg_simulator_helpers.py", line 566, in _apply_hamiltonian
output_register += (rabi_coef[index_time] / 2) * rabi_op.dot(input_register)
IndexError: index 400 is out of bounds for axis 0 with size 400
To Reproduce
execute attached demonstrator as-is.
https://bitbucket.org/balewski/quantummind/src/master/QuEra/python/issues/issue1_10atom_crash.py
It will crash in 5 seconds.
But if you reduce the number of atoms in line 74 to 9
nAtom=9
all works fine.
Expected behavior
program should simulate up to nAtom=16
System information (please complete the following information as applicable):
$ pip3 list |grep braket
amazon-braket-default-simulator 1.14.0
amazon-braket-schemas           1.17.0
amazon-braket-sdk               1.39.1

Working Environment: podman image running locally

Thanks for the bug report. I have transferred the issue to the default simulator repository as that is where the bug is. There seems to be an issue with the usage of the ode integrator from scipy. We will look into the source of the bug.

Hi Jan, this bug is due to the integrator taking intermediate steps outside of the range of interpolated values that are computed before the integration starts. I'll take a look at what needs to be changed to correct this error. In the meantime, can you try using device.run(..., solver_method="bdf") to select a different integration method and see if that one avoids this bug?

Hi Stephen,
yes, I confirm changing solver avoids this crash.
Now I can run my simulations on a bigger system. It is a big help!
Thank you for investigating it
Jan

On Jun 23, 2023, at 2:51 PM, Stephen Face @.***> wrote:
Hi Jan, this bug is due to the integrator taking intermediate steps outside of the range of interpolated values that are computed before the integration starts. I'll take a look at what needs to be changed to correct this error. In the meantime, can you try using device.run(..., solver_method="bdf") to select a different integration method and see if that one avoids this bug?
—
Reply to this email directly, view it on GitHub https://github.com/aws/amazon-braket-default-simulator-python/issues/168#issuecomment-1605022099, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMOFG7IFWBAYRM4VFXUQTXMYFXNANCNFSM6AAAAAAZQUDAEE.
You are receiving this because you authored the thread.

This issue seems resolved, closing


Enable update-pr-from-base-branch on forks

GitHub recently added a new API endpoint for this specific operation and it works across forks: https://developer.github.com/v3/pulls/#update-a-pull-request-branch
It would replace this:
https://github.com/sindresorhus/refined-github/blob/b3e38ad58c87fd1ab927e27368cf3c836aa29041/source/features/update-pr-from-base-branch.tsx#L19-L29
They don't have an API to verify whether the PR is up to date, so I sent them feedback to ask for one. For now, the API we're using for this should work across forks already.

Wow I opened this same issue 3 weeks before: https://github.com/sindresorhus/refined-github/issues/2097


Create homepage bg.js

Merged via https://gitlab.com/gitlab-org/gitter/gitter-translations/merge_requests/59
Thanks @brainsucked


cog icon works but throws a runtime error:

Bug Report
When using:
<Icon name='cog' />

The page renders just fine, but the following runtime error is thrown:
``
Warning: Failed prop type: Invalid prop name of value cog supplied to Icon.
Instead of cog, did you mean:

cogs

bug

car
in Icon (at App.js:212)
in App (created by Connect(App))
in Connect(App) (at src/index.js:90)
in Provider (at src/index.js:89)

### Version

"semantic-ui-css": "^2.3.1",
"semantic-ui-react": "^0.80.0"

### Testcase
[Fork, update, and replace this pen to show the bug]:
https://codesandbox.io/s/2l3n74j9y

<EMAIL_ADDRESS>and<EMAIL_ADDRESS>aren't compatible. The latest versions contains correct definitions, https://github.com/Semantic-Org/Semantic-UI-React/blob/v0.82.5/src/lib/SUI.js#L731
Please make sure that you're using the latest version of SUI and SUIR, this information is mentioned in docs: http://react.semantic-ui.com/usage#css
"semantic-ui-css": "^2.4.0",
"semantic-ui-react": "^0.82.5",

@layershifter thanks that solved it


Using lua-jump-to on ships with turrets renders turrets useless

When making a ship (usually capital ships) jump to another point via lua-jump-to from AxInMissionJump, that ship doesn't use its turrets anymore. They don't turn and they don't fire anymore.

Does  lua-jump-to issue a play-dead-persistent order?

@wookieejedi it issues a play-dead order...
	mn.runSEXP("( add-goal !" .. name .. "! ( ai-play-dead 101 ) )")

@Strygon does this work on RC3?

I'm pretty sure the issue that caused this bug was fixed in the aforementioned RC3.  In any case, I tested it with the latest source and it worked.


Allow warnings when building Podspecs

Motivation:
When pushing Cocoapods a warning is emitted for SwiftNIOSSL
('SecTrustEvaluateAsync' was deprecated in watchOS 6.0). Pushing the
pods fails as a result.
Modifications:
Allow warnings when pushing pods.
Result:
Pods can be pushed with warnings.

We should update to use the non-deprecated API where it's available as well.


PasswordPolicies expected values

Adding what is the expected values for new user provised after the EnforceCloudPasswordPolicyForPasswordSyncedUser is enabled and also clarifying expected value change after a password change is executed on-premises if the value has been set manually via powershell.

@VMrenato : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Introduce remove on maps?

I have noticed that we have the operator put that adds a new pair to a map:
https://github.com/informalsystems/tnt/blob/main/doc/lang.md#maps-aka-functions
But we do not have any operator that deletes a pair. Shall we introduce an operator remove:
f.remove(k) == f.keys().exclude(k).mapOf(x => f[x])

Both put and remove are redundant, as they can be expressed via mapOf. But if we have put, we should probably have remove too.
@bugarela, @shonfeder, wdyt?

+1. I'm trying to use quint and just discovered this is missing.

We have the definition of mapRemove in basic spells:
https://github.com/informalsystems/quint/blob/449c7d956fdf9640470718e69d66220ea5a82dfe/examples/spells/basicSpells.qnt#L112-L120
Here is an example of how you could use it, assuming that the spec t.qnt is in the Quint home:
module t {
  import basicSpells.mapRemove from "./examples/spells/basicSpells"

  pure def myMapRemoveTest =
    assert(Map(2 -> 4, 6 -> 7).mapRemove(6) == Map(2 -> 4))
}

And here is how you could test it:
$ quint test t.qnt

  t
    ok myMapRemoveTest passed 1 test(s)

  1 passing (6ms)

Hey yes I found it! Thanks

Now that we have a definition available, this will be solved by #1314


Update cartodb-layer-group-view-base.js tests

As @alonsogarciapablo commented here

Implement pending specs
Remove duplication in tests

There was also a TODO related to error handling.


Triage finschia-sdk#1149

The subject of the triage:

Finschia/finschia-sdk#1149

Desc

fix for release ci by bump-up goreleaser

Suggestion(Abandon/Maintain/Submit)

Maintain: finschia-sdk

Links

https://github.com/Finschia/finschia-sdk/pull/1149

TODO: check that goreleaser/goreleaser-action@v3 could replace it.


Missing AFTER directive

While generating "ALTER TABLE" sqls, DBDIFF doesn't add "AFTER $COLUMN" directive, so every new column have been added at the end of every table.
I found "modifyAfter" function but it doesn't add that directive anyway.
Thank you for any help.

I found this bug too

I found this too

modifyAfter() not used.
Is there a solution in one of the forks?

killerbug...


Update how-to-contribute.md

A few edits in punctuation and replacing words. This is a great article!

[x] Have you followed the contributing guidelines?
[x] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Thanks @NorahKiggundu! This would be a reasonable set of edits if the guides used brief headings and no oxford commas throughout, but that's not the case, so closing this. Thanks for the thorough read though, and if you notice anything else that could be improved, but in keeping with the style used throughout, feel free to open an issue or PR.


Unstable test raftstore::test_stats::test_query_stats

Bug Report
[2021-07-17T13:20:54.194Z] 21:20:42.330 runner.rs:49: [DEBG] case end, name: raftstore::test_stats::test_query_stats

[2021-07-17T13:20:54.194Z]

[2021-07-17T13:20:54.194Z] + awk '/^failures/{flag=1}/^test result:/{flag=0}flag' tests.out

[2021-07-17T13:20:54.195Z] failures:

[2021-07-17T13:20:54.195Z]

[2021-07-17T13:20:54.195Z] failures:

[2021-07-17T13:20:54.195Z]     raftstore::test_stats::test_query_stats

[2021-07-17T13:20:54.195Z]

[2021-07-17T13:20:54.195Z] + gdb -c 'core.*' -batch -ex 'info threads' -ex 'thread apply all bt'

[2021-07-17T13:20:54.236Z] /home/jenkins/agent/tikv-master/build/core.*: No such file or directory.

[2021-07-17T13:20:54.236Z] No threads.

[2021-07-17T13:20:54.236Z] + exit 1

What version of TiKV are you using?

What operating system and CPU are you using?

Steps to reproduce

in ci https://ci.pingcap.net/blue/organizations/jenkins/tikv_ghpr_test/detail/tikv_ghpr_test/4372/pipeline
What did you expect?
What did happened?

happend again in https://ci.pingcap.net/blue/organizations/jenkins/tikv_ghpr_test/detail/tikv_ghpr_test/4983/pipeline


Tittle [letu]

Leave a comment, Thank you

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

ID: d662deed-71c4-5823-2af3-0a982d90d33f
Version Independent ID: 54f94e5f-d034-dfba-070f-ed4a4e0c8063
Content: Deployment manifests for Office solutions - Visual Studio
Content Source: docs/vsto/deployment-manifests-for-office-solutions.md
Product: visual-studio-dev15
GitHub Login: @TerryGLee
Microsoft Alias: tglee

Title j

@1123347cg119 This doesn't appear to be actionable feedback, so we are closing the issue. If I missed something, please provide more details and we can reopen the issue.

@gewarren  you might have already done it, but you can use this to report spam comments and PRs https://help.github.com/articles/reporting-abuse-or-spam/#reporting-an-issue-or-pull-request

@nschonni Didn't know about that, thanks!


MCS-1501 Update requirements

Updated versions in the requirements file (as much as possible).
Added github workflows to automatically test python 3.8, 3.9, and 3.10 on both linux and mac.

@ThomasSchellenbergNextCentury I am getting a failure on integration tests using 3.10, here is the process I used:

git clone https://github.com/NextCenturyCorporation/MCS.git
cd MCS
python3.10 -m venv --prompt mcs venv
source venv/bin/activate
python -m pip install --upgrade pip setuptools wheel
python -m pip install machine-common-sense
pip install -r requirements.txt
python -m unittest  (Good)

- python run_tests.py  --mcs_unity_build_file_path ../../../unity/test19.app/Contents/MacOS/MCS-AI2-THOR --dev (Bad)
========================================
HANDMADE TEST METADATA TIER: LEVEL1
Initialize return: {'cameraNearPlane': 9.999999747378752e-05, 'cameraFarPlane': 9999.0}
RUNNING SCENE: 001.empty_room_movement.scene.json
Traceback (most recent call last):
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/integration_tests/run_tests.py", line 21, in
start_handmade_tests(
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/integration_tests/run_handmade_tests.py", line 355, in start_handmade_tests
successful, status = run_single_scene(
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/integration_tests/run_handmade_tests.py", line 226, in run_single_scene
step_metadata = controller.start_scene(scene_data)
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/venv/lib/python3.10/site-packages/machine_common_sense/controller.py", line 365, in start_scene
scene_config = self._convert_scene_config(config_data)
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/venv/lib/python3.10/site-packages/machine_common_sense/controller.py", line 345, in _convert_scene_config
return schema.load(config_data)
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/venv/lib/python3.10/site-packages/marshmallow/schema.py", line 722, in load
return self._do_load(
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/venv/lib/python3.10/site-packages/marshmallow/schema.py", line 909, in _do_load
raise exc
marshmallow.exceptions.ValidationError: {'_schema': ['Invalid input type.']}

@ThomasSchellenbergNextCentury I am getting a failure on integration tests using 3.10. Looks lie is marshmallow. Here is the process I used:

git clone https://github.com/NextCenturyCorporation/MCS.git
cd MCS
git checkout MCS-1501-reqs
python3.10 -m venv --prompt mcs venv
source venv/bin/activate
python -m pip install --upgrade pip setuptools wheel
python -m pip install machine-common-sense
pip install -r requirements.txt
python -m unittest  (Good)

- python run_tests.py  --mcs_unity_build_file_path ../../../unity/test19.app/Contents/MacOS/MCS-AI2-THOR --dev (Bad)
========================================
HANDMADE TEST METADATA TIER: LEVEL1
Initialize return: {'cameraNearPlane': 9.999999747378752e-05, 'cameraFarPlane': 9999.0}
RUNNING SCENE: 001.empty_room_movement.scene.json
Traceback (most recent call last):
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/integration_tests/run_tests.py", line 21, in
start_handmade_tests(
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/integration_tests/run_handmade_tests.py", line 355, in start_handmade_tests
successful, status = run_single_scene(
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/integration_tests/run_handmade_tests.py", line 226, in run_single_scene
step_metadata = controller.start_scene(scene_data)
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/venv/lib/python3.10/site-packages/machine_common_sense/controller.py", line 365, in start_scene
scene_config = self._convert_scene_config(config_data)
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/venv/lib/python3.10/site-packages/machine_common_sense/controller.py", line 345, in _convert_scene_config
return schema.load(config_data)
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/venv/lib/python3.10/site-packages/marshmallow/schema.py", line 722, in load
return self._do_load(
File "/Users/jacob.audick_cn/Documents/new-requirements/MCS/venv/lib/python3.10/site-packages/marshmallow/schema.py", line 909, in _do_load
raise exc
marshmallow.exceptions.ValidationError: {'_schema': ['Invalid input type.']}

@jaudick Oof, I forgot to check the integration tests for other python versions... Let me try to figure out if I can install Python 3.10, so I can test this locally

@jaudick There were two issues:

I forgot to update the versions in the setup.py file, and make sure it supports 3.10 (apparently I misread it, and we only supported up to 3.9 before, but now we fully support 3.10 as well!). Please pull the latest.
Your step number 7 is incorrect. That command installs the latest release of machine_common_sense, ignoring the modified code on your local branch. You need to run: python -m pip install -e . (remember the dot at the end). You can verify this refers to your local branch by running pip show machine_common_sense; the "Location" should be the file path to your local MCS repo.

The integration tests are currently running fine for me with 3.10, so hopefully this will fix your issue as well.


Add a precommit hook that runs tests and linting

This is something I've thought about for a while after running into it in other open source projects, and then just now while I was running tests where I don't get the webpack watch updates on my linting errors it was just pretty annoying every time having the build fail and having to push a git commit -m "linting fixes" commit just for that.
This can also be configured locally in your git settings (if you don't know precommit hooks basically every time you run git commit it'll run the hook and if it fails you won't commit), but what Husky does is allow it to be global and be shipped with package.json and I think it could be nice for everyone, especially beginners but as seen for me here obviously also more advanced users.
The biggest thing I could think of right now that could be different is I could possibly see an argument for just running linting tests and not the unit tests if our unit tests get slower in the future, but of course if you have arguments for not having this feature other than that, feel free to pitch in. This is pretty subjective in terms of workflow preferences I guess (since the CI will check it anyway so it's not like not having this means we don't test our code), but I quite like it.

Yeah I think my main thought of possible downside is for example the example I gave about about a temporary console.log, or possibly a temporary long line as you say, but I think that a big amount of the time it would be helpful, and as long as we make sure people are aware that they can simply do --no-verify when they commit (and when it fails the husky error message also informs you that you can do this), then I think it would over all be helpful.
Because it was really tedious having to keep doing the git commit -m "Fix linting errors". It felt so useless omg.
Another thought I just had though, again it's a subjective thing. There's also a prepush hook, so instead of on commit we could make these things only happen before a push, or we could split it so it always checks tests on commits and then linting on a push, or linting on a commit and then tests on a push etc. Any thoughts on that?

Hm, that's a good point. I think we should try with both tests and linting on commits at first just to enforce best practices and make the changes easier to manage. If it get's annoying, let's relax it a bit to just do it before the push. We can play it by ear and see what the rest of the team thinks.

Yep that sounds like a good idea! I'll rebase the branch onto master and merge it in :)


ERR_INVALID_URL for cloud users

i'm trying to setup a proxy for a cloud instance, with growth_api set to public cloud
ENV GROWTHBOOK_API_HOST = https://cdn.growthbook.io

but i get an error
2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | TypeError: Failed to parse URL from = https://cdn.growthbook.io/api/v1/sdk-connections?withProxy=1&limit=100&offset=0

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | at node:internal/deps/undici/undici:12618:11

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | [cause]: TypeError [ERR_INVALID_URL]: Invalid URL

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | at new NodeError (node:internal/errors:405:5)

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | at new URL (node:internal/url:676:13)

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | at new Request (node:internal/deps/undici/undici:6108:25)

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | at fetch (node:internal/deps/undici/undici:10396:25)

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | at Object.fetch (node:internal/deps/undici/undici:12617:10)

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | at fetch (node:internal/process/pre_execution:281:25)

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | at Registrar.<anonymous> (/usr/local/src/app/packages/apps/proxy/dist/services/registrar/index.js:108:36)

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | at Generator.next (<anonymous>)

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | at /usr/local/src/app/packages/apps/proxy/dist/services/registrar/index.js:8:71

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | at new Promise (<anonymous>) {

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | input: '= https://cdn.growthbook.io/api/v1/sdk-connections?withProxy=1&limit=100&offset=0',

2024-06-26T19:05:40.882 app[683d55df763148] hkg [info] | code: 'ERR_INVALID_URL'

This suggests that somehow you're setting your env variable value to '= https://cdn.growthbook.io'. Please double check your env vars.


add new example add_cluster.go for sdk

add new example add_cluster.go for sdk

Hello contributor, thanks for submitting a PR for this project!
I am the bot who triggers "standard-CI" builds for this project.
As a security measure, I will not run automated tests on PRs that are not from white-listed contributors.
In order to allow automated tests to run, please ask one of the project maintainers to review the code and then do one of the following:

Type ci test please on this PR to trigger automated tests for it.
Type ci add to whitelist on this PR to trigger automated tests for it and also add you to the contributor white-list so that your future PRs will be tested automatically. ( keep in mind this list might be overwritten if the job XML is refreshed, for permanent whitelisting, please follow #3 option )
If you are planning to contribute to more than one project, maybe it's better to ask them to add you to the project organization, so you'll be able to run tests for all the organization's projects.

It's an example so need to run CI testing. Let's merge this. Thanks @huihui0311 for your contribution.


caught easy errors, parentheses missing

I somehow overlooked this, easily fixed.

Howard, this is the second time you've submitted a pull request that breaks Symbulate completely. And once again, this is an error that would have been caught immediately by just trying to import Symbulate.
I want to remind you that every time you make a change, you are expected to test your code again. From now on, I expect you to submit a Jupyter notebook for every single change that you make, including this one. Please upload a notebook verifying that this change works.

I have completely reverted the pull request you submitted previously. Please open a new pull request to re-submit the change you made previously.


Add code for browser mockup

The filtering on the left-hand side will not show more than one result while we redo the mapping of GE terms to ontology terms/GECKO terms.
This includes the spreadsheet for #14 - https://docs.google.com/spreadsheets/d/1IRAv5gKADr329kx2rJnJgtpYYqUhZcwLutKke8Q48j4/edit?usp=sharing
This builds on #19.

I'm happy with the code, but would like some things moved around:

I don't want a browser/ directory. Please put all generated files under build/. A build/browser/ directory is fine, if that's what you prefer.
Please move browser/index.html to src/index.html. Then add a Make task to copy src/index.html to whatever location under build/ that you need.

Done!


Release Google.Cloud.Translate.V3 version 3.5.0

Changes in this release:
No API surface changes; just dependency updates.

Created release for Google.Cloud.Translate.V3-3.5.0


Markdown - only double newlines should cause new paragraphs

According to the GFM spec, at https://github.github.com/gfm/#paragraphs,
you may spread a paragraph over multiple lines.
For example, this sentence and the previous
one should render in one paragraph, not four.
But double newlines cause new paragraphs, like this. You can see how this can make it hard to read.
I write READMEs in vim with hard wrapping on, so all of them are hard to read, especially on iPhone in portrait mode. It is not typically a problem in comments and issues, because who is using hard wrapping there?
Example or hard to read README: https://github.com/valor-software/ng2-dragula

Bug Report Dump (Auto-generated)

Version 1.21.0<PHONE_NUMBER>)
Device: iPhone 6 (iOS 11.4.1)
TestFlight: false

I wonder where this diverges. We use GitHubs C parser.
Sent with GitHawk

The parser has a setting that turns this behavior on or off, CMARK_OPT_HARDBREAKS.  See cmark(3) man page for details.  This should be turned on for rendering issues and code comments, off for READMEs and other md content.
Sent with GitHawk

This is fixed now


Is there  layout concept?

how can i use layout with materical-ui? thanks a lot.

I was thinking the same thing.. it looks like the example page makes use of Flexbox?

+1

Duplication of #1109

I found this to be helpful - https://philipwalton.github.io/solved-by-flexbox/

If layout isn't supported there should be a note under Layout in the documentation.
Because people are going to keep asking where to get the standard Material margins to do stuff like this.  I know it's the first thing I went looking for.

@RichardJECooke I totally agree!
Some official advice would be nice :bowtie:

Continued in #3066.


Static lighting and stuff

Many things are here.
I. Static lights. Set model.isStatic=true and light.isStatic=true to enable. These lights will only affect the triangles they intersect. The benefits are:

You can have large amounts of lights in the scene without being afraid to go out of uniforms;
Doesn't use as much memory as lightmaps;
Fully correct specular;
You can dynamically change lights' colors or shadow/cookie properties. You can also dynamically narrow the radius or the spotlight cone;
Objects can cast dynamic shadows inside static lights;
In fact, you CAN move static lights and the associated geometry (that makes me unsure about the "isStatic" name). As long, as lights intersect same triangles, it will work (so for example, you can have a moving self-lit train).

You can recalculate static lighting data by calling renderer.prepareStaticMeshes(device, scene). It's usually rather fast (60ms for the space demo). This function is called automatically on app launch.
Also a bunch of new profiler stats are added.
Limitation: can't have more than 32 static lights touching one draw call, because of some optimizations. It's possible to remove these optimizations, but... I'd rather have them.
II. Directional lightmaps. Set light.bakeDir=true, then call lightmapper.bake(null, pc.BAKE_COLORDIR) to get it (it's also the new default value). Renders average light direction along with a color lightmap. The light direction map allows to reconstruct bump-mapped lighting and specular. The cost is 2 texture reads + one light calculation + tiny other stuff. Intersecting many lights with bakeDir=true may lead to incorrect bump/specular. As long, as lights don't intersect much, you can bake any amount of them.
III. Cookie transformations. Only work for spotlights (to rotate cubemap cookie, it's enough to just rotate the node, shadows ignore pointlight rotation). The new properties are:

cookieAngle (float): rotation angle;
cookieScale (vec2): scaling;
cookieOffset (vec2): translation offset.

Additional:

light.setCastShadows is optimized;
fixed incorrect lightmap dilation https://github.com/playcanvas/engine/issues/695 ;
fixed some bugs in StandardMaterial's key generation;
fixed some frustum culling bug which was related to parent scale;
added light.getBoundingBox();
added docs for pc.BoundingBox#add;
added docs for lightmapper.

Should we rename isStatic to static?

Should we rename isStatic to static?
I wanted to, but then "static" is a reserved keyword in JS. Although It SHOULD work as a variable name, but... I just don't like the idea, I think some day it can break - maybe in browser, maybe in our build tool, maybe somewhere else. Also Sublime annoyingly highlights "static".


retrieve_changes improvements

Improvements to the retrieve_changes task:

When you specify the include or exclude option to filter the retrieved components, the task will now retrieve only those components rather than all components listed in package.xml in the target directory.
Changes can now be retrieved into folders in DX source format. Namespace tokenization is not supported in DX format, since there isn't currently a way to deploy DX format source including namespace tokens.
The target directory now defaults to src if the project is using mdapi format or the default entry in packageDirectories in sfdx-project.json if the project is using sfdx format.

Along the way I also added some options to the sfdx util, refactored some of the namespace injection utils to support operating on a directory instead of a zip file, and gave the temporary_dir util an option to skip changing the current directory.
Caveats:

When retrieving in DX format, the task will update sfdx's revision number if and only if all changed components were retrieved. As a result, after retrieving a filtered subset of components, sfdx force:source:status may show conflicts.
Retrieving into mdapi format is accomplished by temporarily converting to dx format, running force:source:retrieve, then converting back. I've noticed a few spurious changes that can happen as a result of the conversion:

Reordering of components and removing blank lines inside a multi-component file (such as a .object file)
Changing the format of entities e.g. ' to '

Critical Changes
Changes
Issues Closed

@davisagli - curious about this:

When you specify the include or exclude option to filter the retrieved components, the task will now retrieve only those components rather than all components listed in package.xml in the target directory.

I definitely see how this is applicable to the include options, but how does this apply to the exclude option? If I specify to exclude profiles, wouldn't we want to pickup everything in the package.xml minus what we want to exclude?
Other than that, only a few minor things I can comment on. Was my first time looking through sourcetracking.py as well, so a lot to take in, but well worth spending some time on. I think that RetrieveChanges._run_task() could definitely be refactored so that it gives a good overview of all the steps involved. I'd be happy to do that as a learning exercise on my own after this is all wrapped up.

@Br4nd0R

If I specify to exclude profiles, wouldn't we want to pickup everything in the package.xml minus what we want to exclude?

The filters are applied to the list of components that have changed (you can see this list without retrieving anything using cci task run list_changes), not the existing contents of the package in the repo. It should have the same effect as what you said though, because if a component in the package didn't change then there's no need to retrieve it.

@davisagli - That makes complete sense, I didn't realize it's only pulling the components that have changed.

I also realize now that I should have just read the command name... retrieve_changes would imply that we're retrieving... changes. Need more ☕

@jstvz this is working as designed (but maybe we need a better design). include and exclude both do a substring match on the string "{metadata type}: {metadata name}" ... so -o include Profile includes any component with Profile as part of the name or type. You should be able to retrieve the specific component you're aiming for using -o include "Profile: Admin"

Currently, retrievechanges offers two options to control what metadata is retrieved:
• include: Include changed components matching this string.
• exclude: Exclude changed components matching this string.

This has led to some confusion on the part of users (including me) about what the expected behavior of these options is. I think we should update these tasks as follows:

Change the help text for the existing options to include an example of how its matching works, e.g. "Example: -o include Foo matches CustomField: Foo__c.Baz__c and CustomObject: Foo__c"
Add an option to filter based on metadata type. This option would accept a comma-separated list of metadata types (e.g. Profile) rather than a string. While this is possible with the existing option by matching against the record prefix (-o include Profile:), users often fail to include a colon and retrieve unwanted metadata.

Paper-cuts:

Running retrieve_changes without --org or a default org set results in a traceback rather than a note indicating that an org is required.
Not including the namespace_tokenize parameter results in a KeyError on line 218.

In some simple testing, the changes seem to work successfully on unpackaged MDAPI directories (not over-pulling).

@davidmreed thanks; both of those papercuts should be fixed now.

@Br4nd0R @jstvz @davidmreed I think I've addressed all the feedback and have this ready for final review.


#16990: 'View on Etherscan' now works for other networks

Resolves brave/brave-browser#16990.
https://user-images.githubusercontent.com/28645536/126897594-3b6b5eda-56bd-49e9-82d6-d9756759fc4d.mp4
cc @bbondy

@onyb thanks for the review! :)
Updated.


backdate function

Is your feature request related to a problem? Please describe.
To allow adding of backlog, as adding manually on google sheet requires the edit of the tracking sheet which can be confusing
Describe the solution you'd like
/addbacklog or something similar and from there ask users for date and info related to entry
copy and move everything from the first row of date down one row
edit the first row
Additional context
Add any other context or screenshots about the feature request here.

Suggestion:
/addbacklog feature
Similar flow to current /addentry, but add a date parameter to be defined before "type of entry"
User flow:

User keys /addbacklog
User inputs date of trxn
User inputs "type of entry": Transport or Others
User inputs price
User inputs details (eg. "Bought a new shirt")
User inputs category
User inputs subcategory
User inputs mode of payment
Trxn logged

released on v2.1.7


Use MapDataResults class to manage fetching, queryModel subscription

Use MapDataResults class to manage fetching, queryModel subscription (based on WordcloudComponent and FrequentWordsResults).

Pushed an update using @lukavdplas suggestion.


Can I inject script after body tag use addScriptTag function

When I inject a script use addScriptTag function. It injected between head tag.
In my project I want inject a script file after  close body tag. How can I do?

In my project I want inject a script file after close body tag. How can I do?

@microwin168 you'll have to resort to manual page.evaluate call:
const scriptToInject = `console.log("yo");`;
await page.evaluate(scriptText => {
  const el = document.createElement('script');
  el.type = 'text/javascript';
  el.textContent = scriptText;
  document.body.parentElement.appendChild(el);
}, scriptToInject);


BUG: scipy.spatial: incremental Voronoi doesn't increase size of point_region array

Something about the incremental mode of Voronoi diagrams is wrong, because the point_region array doesn't expand when more points are added.
Here's a simple test case, running on scipy master:
In [1]: from scipy.spatial import Voronoi

In [2]: import numpy as np

In [3]: v = Voronoi(np.random.random((5,2)), incremental=True)

In [4]: v.npoints
Out[4]: 5

In [5]: v.point_region
Out[5]: array([0, 4, 2, 3, 1])

In [6]: v.add_points(np.random.random((3,2)), restart=False)

In [7]: v.npoints
Out[7]: 8

In [8]: v.point_region
Out[8]: array([0, 5, 4, 1, 3])

Expected behavior (which we get with restart=True) is that v.point_region will have 8 elements.

The problem seems to be that self.numpoints is not incremented in _QHull.add_points although a new point array is added. Probably easy to fix.


Change default FELIX_LOGSEVERITYSCREEN from info to error

Hi guys, minor change on networking side.
Calico is logging A LOT non useful stuff, causing pressure on the logging side.
I changed FELIX_LOGSEVERITYSCREEN from info to error

Not sure if we should ship it by default seted to error or info. I will hold the review until listening more point of views.

Before and after

i am  fully agree with @nutellinoit . I would also like to make a similar discussion for audit logging that is pretty much intensive and should be refined in order to keep only "interesting events" and not "everything" because at the end, only the "errors" are useful when you analyze a post-mortem or issue context.

Exactly, is not only how many logs are the CNI emitting, there are other components emitting a huge amount of logs with the "default" configuration. So... three options:

Ship with the default logging configuration as we are currently doing. Then, as part of the delivery team work, you should ask client if they want info or error log level.
Change the default log level we are shipping, not only in the CNI but in all components. Then as part of the delivery team work, ask the client if they want more verbosity.
Change just the calico log level because it was bad implemented by calico project team (in this case) (they should emit current info logs -> debug).

What's your opinion?

I would go with 3 and than evaluate the other components in case they are logging too much without providing any useful information.

I agree about lowering the calico logging level.
Regarding the audit log, it is an audit log, so it should be complete, but as @angelbarrera92 was saying it should be a requirement from the customer whether auditability is needed or not in their specific context, for debugging purposes storing just errors should be more than enough.
I think we should definitely discuss this in a separate PR/Issue.

I will add an "unreleased" markdown file under docs/releases to don't forget to include it in the next release


bug: Forward slash (/) character not replaced in tag reference

As mentioned by @gmpinder in blue-build/discussions/12, an error occurs when using the latest version of the github action, which is caused by the blue-build CLI tool not correctly replacing the forwards slash (/) character within the generated tags, by the CLI.
See this failing build: https://github.com/CarrotManMatt/carrot-kinoite-nvidia/actions/runs/8055478674/job/22002432608
Example tag that causes a build failure: ghcr.io/carrotmanmatt/carrot-kinoite-nvidia:br-dependabot/github_actions/blue-build/github-action-1.1.0-39

Thank you for fixing this so speedily!❤
What steps must I take so that I can successfully rerun my build, now that this has been fixed? Or do I need to wait for some sort of release?

There's no way to use a non-released version currently, so you need to wait for a release. There's a tracking issue: https://github.com/blue-build/github-action/issues/17
Fortunately this only has to do with the branch tags, so you can hopefully live without for now, right?

Fortunately this only has to do with the branch tags, so you can hopefully live without for now, right?

I presume so, as when I merge the update the main build will succeed, even if the merge request one is failing👍🏻


Improve unit parsing to include derived units

Currently can only parse kilograms, meters, and seconds.  Improve unit parsing to include derived units such as newtons, kilopascals, etc.

Newtons and Pascals added, more units to come.


errors while unzipping files in FogchamberDataset and SeeingThroughFogCompressed

Hi,
unfortunately, I can not successfully unzip the files within FogchamberDataset and SeeingThroughFogCompressed.
To make sure that the download was not corrupted on my side, I already downloaded FogchamberDataset.zip and SeeingThroughFogCompressed.zip multiple times from your server.
While unzipping FogchamberDataset.zip and SeeingThroughFogCompressed.zip itself works fine,
unzipping the files within it's extracted subfolders doesn't work.
When trying to unzip those, I get the following message for the archives in FogchamberDataset:
4 archives were successfully processed.
7 archives had fatal errors.

and this for the archives in SeeingThroughFogCompressed:
10 archives were successfully processed.
1 archive had warnings but no fatal errors.
32 archives had fatal errors.

I think you should be able to reproduce a "fatal error" e.g. when you do
unzip lidar_hdl64_strongest.zip in FogchamberDataset/lidar_hdl64_strongest.

This is the trace I get:
Archive:  lidar_hdl64_strongest.zip
warning [lidar_hdl64_strongest.zip]:  zipfile claims to be last disk of a multi-part archive;
  attempting to process anyway, assuming all parts have been concatenated
  together in order.  Expect "errors" and warnings...true multi-part support
  doesn't exist yet (coming soon).
file #1:  bad zipfile offset (local header sig):  4
file #2:  bad zipfile offset (local header sig):  84
file #3:  bad zipfile offset (local header sig):  1292455
file #4:  bad zipfile offset (local header sig):  2585819
file #5:  bad zipfile offset (local header sig):  3877631
file #6:  bad zipfile offset (local header sig):  5169771
file #7:  bad zipfile offset (local header sig):  6462841
file #8:  bad zipfile offset (local header sig):  7755507
file #9:  bad zipfile offset (local header sig):  9046452
file #10:  bad zipfile offset (local header sig):  10341663
file #11:  bad zipfile offset (local header sig):  11633918
file #12:  bad zipfile offset (local header sig):  12929252
file #13:  bad zipfile offset (local header sig):  14225869
file #14:  bad zipfile offset (local header sig):  15518351
file #15:  bad zipfile offset (local header sig):  16816588
file #16:  bad zipfile offset (local header sig):  18111883
file #17:  bad zipfile offset (local header sig):  19405226
file #18:  bad zipfile offset (local header sig):  20698401
file #19:  bad zipfile offset (local header sig):  21990109
file #20:  bad zipfile offset (local header sig):  23281287
file #21:  bad zipfile offset (local header sig):  24574933
file #22:  bad zipfile offset (local header sig):  25868771
file #23:  bad zipfile offset (local header sig):  27161983
file #24:  bad zipfile offset (local header sig):  28453010
file #25:  bad zipfile offset (local header sig):  29745940
file #26:  bad zipfile offset (local header sig):  31039964
file #27:  bad zipfile offset (local header sig):  32334045
file #28:  bad zipfile offset (local header sig):  33629028
file #29:  bad zipfile offset (local header sig):  34923028
file #30:  bad zipfile offset (local header sig):  36218481
file #31:  bad zipfile offset (local header sig):  37512234
file #32:  bad zipfile offset (local header sig):  38810796
file #33:  bad zipfile offset (local header sig):  40106979
file #34:  bad zipfile offset (local header sig):  41401521
file #35:  bad zipfile offset (local header sig):  42699155
file #36:  bad zipfile offset (local header sig):  43992782
file #37:  bad zipfile offset (local header sig):  45287246
file #38:  bad zipfile offset (local header sig):  46581336
file #39:  bad zipfile offset (local header sig):  47873381
file #40:  bad zipfile offset (local header sig):  49170729
file #41:  bad zipfile offset (local header sig):  50466394
file #42:  bad zipfile offset (local header sig):  51766117
file #43:  bad zipfile offset (local header sig):  53062799
file #44:  bad zipfile offset (local header sig):  54360313
file #45:  bad zipfile offset (local header sig):  55654613
file #46:  bad zipfile offset (local header sig):  56949106
file #47:  bad zipfile offset (local header sig):  58244705
file #48:  bad zipfile offset (local header sig):  59539629
file #49:  bad zipfile offset (local header sig):  60835290
file #50:  bad zipfile offset (local header sig):  62129307
file #51:  bad zipfile offset (local header sig):  63422834
file #52:  bad zipfile offset (local header sig):  64718391
file #53:  bad zipfile offset (local header sig):  66013988
file #54:  bad zipfile offset (local header sig):  67311345
file #55:  bad zipfile offset (local header sig):  68606532
file #56:  bad zipfile offset (local header sig):  69899595
file #57:  bad zipfile offset (local header sig):  71192095
file #58:  bad zipfile offset (local header sig):  72485408
file #59:  bad zipfile offset (local header sig):  73781890
file #60:  bad zipfile offset (local header sig):  75075232
file #61:  bad zipfile offset (local header sig):  76376460
file #62:  bad zipfile offset (local header sig):  77671315
file #63:  bad zipfile offset (local header sig):  78964356
file #64:  bad zipfile offset (local header sig):  80256813
file #65:  bad zipfile offset (local header sig):  81549048
file #66:  bad zipfile offset (local header sig):  82844999
file #67:  bad zipfile offset (local header sig):  84137137
file #68:  bad zipfile offset (local header sig):  85437263
file #69:  bad zipfile offset (local header sig):  86731938
file #70:  bad zipfile offset (local header sig):  88028050
file #71:  bad zipfile offset (local header sig):  89325220
file #72:  bad zipfile offset (local header sig):  90617851
file #73:  bad zipfile offset (local header sig):  91915628
file #74:  bad zipfile offset (local header sig):  93210948
file #75:  bad zipfile offset (local header sig):  94503290
file #76:  bad zipfile offset (local header sig):  95796339
file #77:  bad zipfile offset (local header sig):  97087997
file #78:  bad zipfile offset (local header sig):  98383722
file #79:  bad zipfile offset (local header sig):  99678481
file #80:  bad zipfile offset (local header sig):  100973162
file #81:  bad zipfile offset (local header sig):  102270798
file #82:  bad zipfile offset (local header sig):  103566676
file #83:  bad zipfile offset (local header sig):  104860820
file #84:  bad zipfile offset (local header sig):  106155307
file #85:  bad zipfile offset (local header sig):  107451449
file #86:  bad zipfile offset (local header sig):  108749420
file #87:  bad zipfile offset (local header sig):  110054951
file #88:  bad zipfile offset (local header sig):  111346346
file #89:  bad zipfile offset (local header sig):  112641992
file #90:  bad zipfile offset (local header sig):  113894838
file #91:  bad zipfile offset (local header sig):  115147796
file #92:  bad zipfile offset (local header sig):  116399960
file #93:  bad zipfile offset (local header sig):  117654099
file #94:  bad zipfile offset (local header sig):  118910916
file #95:  bad zipfile offset (local header sig):  120168276
file #96:  bad zipfile offset (local header sig):  121429930
file #97:  bad zipfile offset (local header sig):  122694434
file #98:  bad zipfile offset (local header sig):  123955740
file #99:  bad zipfile offset (local header sig):  125219836
file #100:  bad zipfile offset (local header sig):  126479615
file #101:  bad zipfile offset (local header sig):  127734190
file #102:  bad zipfile offset (local header sig):  128988789
file #103:  bad zipfile offset (local header sig):  130241864
file #104:  bad zipfile offset (local header sig):  131497036
file #105:  bad zipfile offset (local header sig):  132754659
file #106:  bad zipfile offset (local header sig):  134011773
file #107:  bad zipfile offset (local header sig):  135268425
file #108:  bad zipfile offset (local header sig):  136526702
file #109:  bad zipfile offset (local header sig):  137790606
file #110:  bad zipfile offset (local header sig):  139056533
file #111:  bad zipfile offset (local header sig):  140327818
file #112:  bad zipfile offset (local header sig):  141598340
file #113:  bad zipfile offset (local header sig):  142868462
file #114:  bad zipfile offset (local header sig):  144135196
file #115:  bad zipfile offset (local header sig):  145403230
file #116:  bad zipfile offset (local header sig):  146680238
error: invalid zip file with overlapped components (possible zip bomb)

This is my setup:
$ hostnamectl

  Operating System: Debian GNU/Linux 9 (stretch)
            Kernel: Linux 4.9.0-13-amd64
      Architecture: x86-64

$ unzip --version

UnZip 6.00 of 20 April 2009, by Debian. Original by Info-ZIP.

I think you are getting those errors because of the split zip files (.z01, .z02, ...).
Try something like:
$ zip -FF lidar_hdl64_strongest.zip --out full_lidar_hdl64_strongest.zip
$ unzip full_lidar_hdl64_strongest.zip
See also:
https://askubuntu.com/questions/31298/how-to-extract-and-join-files-xxx-zip-xxx-z01-and-xxx-z02
https://support.firmex.com/hc/en-us/articles/204579673-Downloads-with-multiple-parts-z01-and-z02-files-

Hi Florian,
thanks for getting back to me so quickly.

I think you are getting those errors because of the split zip files (.z01, .z02, ...).
Try something like:
$ zip -FF lidar_hdl64_strongest.zip --out full_lidar_hdl64_strongest.zip
$ unzip full_lidar_hdl64_strongest.zip
See also:
https://askubuntu.com/questions/31298/how-to-extract-and-join-files-xxx-zip-xxx-z01-and-xxx-z02
https://support.firmex.com/hc/en-us/articles/204579673-Downloads-with-multiple-parts-z01-and-z02-files-

You were right, the two commands you mentioned work.
I thought of this as well, but then I thought that can't be it
because some of the multi-part files like cam_stereo_left.zip succeeded without concatenating the multiple parts beforehand.
While this should fix the errors,
it still makes it quite cumbersome to get the whole dataset ready
(because of its many subfolders and multi-part .zip files therein).
Anyways, thanks for your help, I am looking forward to play with your data once I fully unpacked it. 🙂

Hi Martin,
you're welcome. I don't know how to unpack all the data automatically from the terminal (maybe a short python script could work). However I tried to use 7zip, which can handle multipart zip files (although I only tried this on windows).
Regarding the cam_stereo_left.zip I think you should check if you unpacked everything, since I could unpack lidar_hdl64_strongest.zip with unzip, but it only unpacked the data from the actual .zip file and not from the .zXX files.

OK, thanks for letting me know. I will unpack everything again using the method you described above.
And a little python script may really be the way to go here.
Once I am done, I will share it here.

You were right again, beforehand only 483 files were extracted via unzip cam_stereo_left.zip
(which is probably the content of the last file in the multi-part sequence).
7zip seems to also work accordingly on Linux, so thanks for the hint.
$ 7z e cam_stereo_left.zip

7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,12 CPUs Intel(R) Core(TM) i7-8086K CPU @ 4.00GHz (906EA),ASM,AES-NI)

Scanning the drive for archives:
1 file,<PHONE_NUMBER> bytes (1368 MiB)

Extracting archive: cam_stereo_left.zip
--
Path = cam_stereo_left.zip
Type = zip
Physical Size =<PHONE_NUMBER>
Embedded Stub Size = 4
64-bit = +
Total Physical Size =<PHONE_NUMBER>
Multivolume = +
Volume Index = 2
Volumes = 3

Everything is Ok

Folders: 1
Files: 1500
Size:<PHONE_NUMBER>
Compressed:<PHONE_NUMBER>

7zip detects 3 volumes and extracts 1500 files.

# move all files out of their subfolders
find . -mindepth 2 -type f -print -exec mv {} . \;

# remove all folders but not files
rm -r */

# unzip all multi-part files via 7zip
7z x "*.zip"

Running this in .../FogchamberDataset/ and .../SeeingThroughFogCompressed/ now did the trick for me.

77% 7325 - cam_stereo_left_raw_history_-2/2018-12-13_10-36-07_00000.tiff
terminate called after throwing an instance of 'CInBufferException'
Aborted

# move all files out of their subfolders
find . -mindepth 2 -type f -print -exec mv {} . \;

# remove all folders but not files
rm -r */

# unzip all multi-part files via 7zip
7z x "*.zip"

Running this in .../FogchamberDataset/ and .../SeeingThroughFogCompressed/ now did the trick for me.

For the FogchamberDataset part, those commands worked fine.

Thanks for sharing your code snippets and insights! The missing .z15 is a problem. I will see what we can do about that.

Thanks for sharing your code snippets and insights! The missing .z15 is a problem. I will see what we can do about that.

No problem, same in cam_stereo_left_raw_history_-5.
There also cam_stereo_left_raw_history_-5.z15 is missing.

Unfortunately, I found more missing files:
cam_stereo_left_raw_history_1.z[01-04]

cam_stereo_left_raw_history_2.z01

All missing files have been added. 👍

@MartinHahner did you find a clean way to extract all the files?

# move all files out of their subfolders
find . -mindepth 2 -type f -print -exec mv {} . \;

# remove all folders but not files
rm -r */

# unzip all multi-part files via 7zip
7z x "*.zip"

Running this in .../FogchamberDataset/ and .../SeeingThroughFogCompressed/ now did the trick for me.

I think this worked for me in the end.

Sweet, thanks a lot for the help!!

Thanks Martin!


Fix the CI error

See: https://github.com/casdoor/casdoor/runs/5464379853?check_suite_focus=true

Fixed in: https://github.com/casdoor/casdoor/commit/380cdc5f7e2b6c0633a84311a2dc747c732d74c4


Updating propresenter presentation

I followed your tutorial and I was able to decode a presentation with the following.
protoc --decode rv.data.Presentation ./presentation.proto < /Users/user/Documents/ProPresenter/Libraries/Default/test.pro > simplePresentation.txt
Now, I am assuming that after reading that text, I could do the opposite and recode the resulting file back into a ProPresenter file like this,
cat SimplePresentation.txt | protoc  --encode rv.data.Presentation ./presentation.proto  > test.pro
But the resulting file does not have the slides that the original propresenter file had. Just to make sure that I wasn't missing something, I decided to do the following.
protoc --decode rv.data.Presentation ./presentation.proto < ./test.pro > simplePresentation2.txt
And then check if there was a difference between the original file and the one decoded from the encoding
diff simplePresentation.txt simplePresentation2.txt
And they were the same. I think that the data structure in the protobuf from 7.11 to 7.12 may have broken something, but I am just guessing.
I am using Ventura and Propresenter 7.12 if that helps.

I wonder if the author has some tools to generate .proto files by extracting classes from the Visual Studio solution generated by ILSpy decompilation of ProPresenter.DO.dll, Pro.Common.dll, Pro.SerializationInterop.dll, and Google.Protobuf.dll.

He mentioned using DLLs but never got more into it. I am not familiar with Windows and .NET programming, but if someone could update this, that would be great. The idea of creating a presentation using something like Golang sounds amazing but unobtainable for now!

I tried to reverse engineered <IP_ADDRESS> here https://github.com/wegylexy/ProPresenter7-Proto/tree/v7.15 but haven't tested it yet.
Pro.SerializationInterop.dll per se does not depend on WPF and should work on Linux and Mac too. I'm using .NET 8 to load it.

Thank you very much. I will give it a try on Monday and see if I can get it to work. Sadly I have never done any work with .NET and how it seems that you can analyze structures using reflection.  Anyway. I really appreciate this. Thanks!

@wegylexy  Nice reverse engineering code!
At a glance, yours looks a bit more clever than mine (which I have not shared).
I've been very busy over last year - but will have free time after April to get back into other things (like this).
In the meantime, I will update the protos for 7.16

Didn't notice. Now we have <IP_ADDRESS> https://github.com/wegylexy/ProPresenter7-Proto/tree/v7.16

Hey Wegylexy, for some reason your proto files do not work for me. But the new ones from greyshirt do. Thank you very much both of you. It seems that the resulting JSON is way to complicated to just create a simple presentation. I may get to it next month and see if I can do so anyway.

@tuxtlequino GPT generated bad code 😅 fixed in https://github.com/wegylexy/ProPresenter7-Proto/commit/110e28d926a126d2cadb5c566784cc3914cc3608

In case anyone else finds this, you can also just extract these on a Mac using protodump:
go install github.com/arkadiyt/protodump/cmd/protodump@latest
find /Applications/ProPresenter.app/ -type f -perm +111 -print -exec protodump -file {} -output ./proto \;

Thanks for reminder on that one. I starred that ages ago and forgot all about it!


QnA Maker multi-turn fix

Fixes #
Description

Specific Changes

Testing

Pull Request Test Coverage Report for Build 77586

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.594%

Totals

Change from base Build 77397:
0.0%

Covered Lines:
4428

Relevant Lines:
4804

💛  - Coveralls


[Portal] Docs: Winston/cnct 2314 consolidate documentation for in app wallets and ecosystem

https://linear.app/thirdweb/issue/CNCT-2314/consolidate-documentation-for-in-app-wallets-and-ecosystem

PR-Codex overview
This PR focuses on restructuring and updating the documentation and components related to thirdweb wallets, including In-App, Ecosystem, and External Wallets. It includes deletions of outdated files and additions of new guides and features.
Detailed summary

Deleted multiple outdated .mdx files related to In-App Wallet and Ecosystem documentation.
Added new images and updated asset paths for wallet-related components.
Introduced a new AuthList component to display various authentication methods.
Updated wallet security documentation to reflect changes in architecture.
Enhanced the sidebar for better navigation of wallet-related topics.
Revised various guides to improve clarity on wallet integration and user management.
Added detailed sections on wallet pregeneration and linking multiple identities.
Updated the sign-in methods documentation with clearer instructions and links.

The following files were skipped due to too many changes: apps/portal/src/app/connect/sidebar.tsx, apps/portal/src/app/connect/wallet/faq/page.mdx, apps/portal/src/app/connect/wallet/user-management/get-user-profiles/page.mdx, apps/portal/redirects.mjs, apps/portal/src/app/connect/wallet/security/assets/ecosystem-scoped.svg

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Merge activity

Nov 19, 5:30 PM EST: The merge label 'merge-queue' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


Appstudio update rhtap-demo-component-zpnb

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: rhtap-demo-component-zpnb-on-pull-request-
creating pipelinerun rhtap-demo-component-zpnb-on-pull-request- in namespace rhtap-demo-dev-layv-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


Where are template destinationions defined?

If I wanted to add a new template to be compiled along with the default ones, I figure I could go ahead and add it here and create the appropriate template.
files:
  xresources.tpl: Xresources
  index.tpl: index.html
  i3status.tpl: i3status.conf
  i3.tpl: i3.conf
  new.tpl: new.conf

What I'm unsure about is how where do I define where new.conf should be placed after rendering.

new.conf will be placed in $XDG_HOME/themer/$theme/, like all configuration files. The current theme folder will be symlinked to $XDG_HOME/themer/current, so you should in turn symlink the file, which will usually end up in ~/.config/themer/current/new.conf.

I thought I had covered this in the README, but I haven't it seems. I will expand the Configuration and Usage paragraphs.

I set up themer long ago directly from Charles Leifer's original article - I absolutely forgot about this step. Thank you.


Clarify errors for commands requiring subcommands

Currently, commands such as ks env non-existent-subcommand will output
an error Command 'env' requires a subcommand.
This is not helpful since the user may assume there is the subcommand
'non-existent-subcommand'. This commit will clarify the error messages
in this scenario.
Fixes #140

Sorry for being unclear!
This change just differentiates between the following scenarios:

ks env addition
ks env

In the first scenario, the output will be:
➜  foo2 git:(pkg-get-help) ✗ ../ks env test
ERROR test is not a valid subcommand

Usage:
  ks env [flags]
  ks env [command]

Available Commands:
  add         Add a new environment to a ksonnet project
  list        List all environments in a ksonnet project
  rm          Delete an environment from a ksonnet project
  set         Set environment fields such as the name, server, and namespace.

vs:
➜  foo2 git:(pkg-get-help) ✗ ../ks env
ERROR Command 'env' requires a subcommand

Usage:
  ks env [flags]
  ks env [command]

Available Commands:
  add         Add a new environment to a ksonnet project
  list        List all environments in a ksonnet project
  rm          Delete an environment from a ksonnet project
  set         Set environment fields such as the name, server, and namespace.

Note the difference in the first lines of the error (before the usage). It's subtle but currently on master both output the second scenario.