Bug fix to support Multi-path log rotations

@targeting Thanks for opening this PR.  I'm a bit confused though.  What bug does this fix and how does it fix it?

@stevendanna Hi Steve, while leveraging the cookbook and followed the instructions to handle multiple log file rotations(in this case two log files) by specifying two log file with absolute path for e.g.
path      ['/var/log/tomcat/myapp.log', '/opt/local/tomcat/catalina.out']
The cookbook when converged by chef-client at runtime  just picked up the first element in the array and leaving the next element or more forcing the call to template multiple times, my fix will avoid this code duplication when leveraging your cookbook and loop through the path array when converging

@stevendanna Please ignore this PR, looks like one of the older tags that were pined in my development had the diffs, the master version is good


apps sc: grafana user values file

What this PR does / why we need it: the user grafana values file rendering fails during apply when whitelistRange is enabled, because the annotations key for ingress was missing
Checklist:

[x] Added relevant notes to WIP-CHANGELOG.md
[x] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[x] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] will create noticeable cluster degradation.
E.g. logs or metrics are not being collected or Kubernetes API server
will not be responding while upgrading.
[ ] requires draining and/or replacing nodes.
[ ] will change any APIs.
E.g. removes or changes any CK8S config options or Kubernetes APIs.
[ ] will break the cluster.
I.e. full cluster migration is required.

Chart checklist (pick exactly one):

[x] I upgraded no Chart.
[ ] I upgraded a Chart and determined that no migration steps are needed.
[ ] I upgraded a Chart and added migration steps.

This a problem in 0.32?

It is, will include this fix once it's merged


Log level of error reporting

Hi,
I added:
IMGPROXY_SENTRY_DSN=https://HASH@my-host/ID
and errors do come to my sentry (only one error), but when I enable syslog logging, I see much more warnings in /var/log/syslog
Is there variable for log level of error reporting? To log even warn beside error?
I tried:
IMGPROXY_REPORT_DOWNLOADING_ERRORS=true
IMGPROXY_LOG_LEVEL=warn

but no change
imgproxy version: 3.14.0

Hey @VedranTrivic!
What kind of warnings do you mean?

I revised reporting of downloading errors a bit in the latest build. Should work as you expect now.

Ok, thank you. Will check it, when newer version is released


[feature] Added Estima model

Status
PRODUCTION
Description
Adds a new car model.
Related PRs
Please refer to #836 for a full description and how to test.

Added 2 more colors


Added check for if range exists when getting progress for resumable u…

As per the resumable upload docs

If nothing has been uploaded yet, the API response will not include the Range header.

If no data has been uploaded you will get an invalid offset 1 when trying to access $range[1]. This fix allows progress to be set only if the range exists in the response header.

I signed it!

I signed it!

I signed it! (third times a charm right?)


Update knowledgebase requirement to 2.2.6

This PR bumps the version of the internal knowledgebase repository to version ~2.2.5~ 2.2.6 (note: purposefully no 'v').
Changes

Bump knowledgebase from v2.2.4 to ~2.2.5~ 2.2.6.

Testing

Unit tests: tox -e optional-private knowledgebase.

Checklist

[X] Changes are limited to a single goal (no scope creep)
[X] Code can be automatically merged (no conflicts)
[X] Passes all existing automated tests
[X] New functions include new tests
[X] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[X] Reviewers requested with the Assignee tool :arrow_right:

@willbarton I've updated this PR to use a new 2.2.6 release that properly includes test fixture data so that tests can pas for cfgov-refresh using pip install knowledgebase without needing the -e editable modifier. Would you mind re-reviewing?


Fix for when webpack plugin builds multiple bundles.

To fix: https://github.com/glenjamin/webpack-hot-middleware/issues/18

I tried this out locally, there's a bit more to it than this.
You effectively get given multiple stats entries in the stats.children property, which have different hashes, times and module lists - even with the fix in this PR the module still doesn't work properly.
I think the proper fix would be to send multiple "built" update packets down to the client - one for each module that completed, and then the client will have to have some way of identifying which one it cares about. This would also support multiple client builds in the same compiler.
For now I'd recommend creating two webpack() instances with a shared cache and only attaching the middleware to the client one.

(feel free to re-open the PR if you want to try and expand the fix)

Yeah I agree this is more complicated than I realized at first - will punt on it and use separate webpacks for now. It doesn't really make sense to attempt to hot load modules in my server-specific bundle anyway, I was just trying to keep everything in a single webpack.config.


open is not skipped for skipped modules

While experimenting with the package, I have found that the open builtin is faked for even for modules that I have excluded from faking via the Patcher context manager.
Traceback (most recent call last):
  File "c:\Users\gilad\Documents\my_module\test.py", line 9, in <module>
    test()
  File "c:\Users\gilad\Documents\my_module\test.py", line 7, in test
    my_func()
  File "c:\Users\gilad\Documents\my_module\my_file.py", line 7, in my_func
    open('test.py')
  File "C:\Users\gilad\AppData\Local\Programs\Python\Python38\lib\site-packages\pyfakefs\fake_filesystem.py", line 4449, in open
    return fake_open(file, mode, buffering, encoding, errors,
  File "C:\Users\gilad\AppData\Local\Programs\Python\Python38\lib\site-packages\pyfakefs\fake_filesystem.py", line 4935, in __call__
    return self.call(*args, **kwargs)
  File "C:\Users\gilad\AppData\Local\Programs\Python\Python38\lib\site-packages\pyfakefs\fake_filesystem.py", line 4983, in call
    file_object = self._init_file_object(file_object,
  File "C:\Users\gilad\AppData\Local\Programs\Python\Python38\lib\site-packages\pyfakefs\fake_filesystem.py", line 5037, in _init_file_object
    self.filesystem.raise_os_error(errno.ENOENT, file_path)
  File "C:\Users\gilad\AppData\Local\Programs\Python\Python38\lib\site-packages\pyfakefs\fake_filesystem.py", line 960, in raise_os_error
    raise OSError(errno, message, filename)
FileNotFoundError: [Errno 2] No such file or directory in the fake filesystem: 'test.py'

How To Reproduce
I have the following setup:
.
├── __init__.py
├── __pycache__
│   ├── __init__.cpython-38.pyc
│   ├── my_file.cpython-38.pyc
│   └── test.cpython-38-pytest-6.0.2.pyc
├── my_file.py
└── test.py

test.py:
from pyfakefs.fake_filesystem_unittest import Patcher

from my_file import my_func

def test():
    with Patcher(additional_skip_names=['my_file']):
        my_func()

test()

my_file.py:
import os

def my_func():
    os.open('test.py', os.O_RDONLY, 0o777) # works!

    open('test.py') # fails...

Your enviroment
python -c "import platform; print(platform.platform())"
python -c "import sys; print('Python', sys.version)"
python -c "from pyfakefs.fake_filesystem import __version__; print('pyfakefs', __version__)"

The output is as follows:
Windows-10-10.0.19041-SP0
Python 3.8.3 (tags/v3.8.3:6f8c832, May 13 2020, 22:37:02) [MSC v.1924 64 bit (AMD64)]
pyfakefs 4.1.0

Could a possible solution be patching the builtin open by overriding it only in the modules not listed for skip? It should be checked that the module hadn't overrode the open by itself, since it may cause overriding it again.

Thanks for the report -- this has probably never been used so far, so it has nor been noticed.

This one may be a bit tricky, because other than all other patched imports, open is imported implicitely from buildins, so the usual mechanism does not work here. I have to think about this...

Out of interest - what is the use case you need this for?

I am using the botocore library, which generates classes dynamically based on data files that come with it. It uses the builtin open for that, and mocking the fs making it break as it cannot find its config files. As a temporary solution I am using add_real_directory for adding the necessary files to the fake fs, but this is not ideal...

As a temporary solution I am using add_real_directory for adding the necessary files to the fake fs, but this is not ideal...

Actually I used to do the same for some django-related package (I think tzinfo, which loads the timezone info from disk). I agree that this is not ideal (though it works well enough, and has no real performance penalty), so to fix these things is a good idea.

Hi. In my project I have a file logsio.py and it has open inside. So pyfakefs doesn't fake it. I tried to do pyfakefs.fake_filesystem_unittest.Patcher.SKIPNAMES -= {"io"} but it doesn't look safe and fs.add_real_file doesn't work well. Changing the source name or moving open to another source file should solve the issue but I'd like to fix that on the pyfakefs side (without changes in repo). Do you know how?

@hard7 - thanks for the report--this is obviously a bug. logsio shall not get skipped just because it ends with io.  Can you please write a new issue for this, as it is not related to this one (other than it may have been introduced while fixing this one)? I will try to fix this ASAP.


feat(): add dependency badge

add dependency badge

Looks good to me

@moritzkoenig Stop pressing the green merge button like @DevVersion! Merge it manually per Command-Line

@Lordnoname Indeed!, @Lordnoname stop modifying images using Photoshop :smiley:

I didn't photoshop this picture :octopus: Look at #4

@Lordnoname That means not, that the GREEN BUTTON was pressed. This was just a normal CLI Merge for multiple commits using git merge [BRANCH] :+1:


[WIP] Lid-driven cavity verification experiment

This PR aims to add the lid-driven cavity as a verification experiment (first) and as a simple example (second) that is very well-known in the CFD world.
It's set up as a 2D problem in the yz plane. It also tests that horizontal/channel boundary conditions work.
The verification experiment aims to reproduce the results detailed by Ghia, Ghia, & Shin (1982).
Unfortunately right now it seems to blow up no matter what I do. Once the top plate is set in motion a vorticity anomaly makes its way along the top plate then down to the bottom plate at which point blow up seems to occur no matter the time step or Reynolds number.
A Physics StackExchange post suggested that quiescent initial conditions should be fine "although if the wall Mach number is large, the sudden impulse could be numerically destabilizing" which would only make sense for compressible models. I tried with vortical initial conditions too but no luck.

Thanks @glwagner for fixing pressure boundary conditions in #677!
Lid-driven cavity is looking pretty good now!

Well, I'm happy that its working far better than before --- though the pressure solver is still incorrect! What is the Reynolds number (Re) for this problem? In this problem, the pressure solver errors are probably inversely proportional to Re. Could be nice to have a low Re reference so we can measure the changes that occur when we fix the pressure solver.

What is the Reynolds number (Re) for this problem? In this problem, the pressure solver errors are probably inversely proportional to Re. Could be nice to have a low Re reference so we can measure the changes that occur when we fix the pressure solver.

It's Re = 100 from the plots, which is the lowest Ghia et al. (1982) go. Could still be relatively high Re as far as pressure solver errors go...
The "forced flow" test is better in this regard as it runs at Re = 1.

The above comment was incorrect. I've struck it through.
The forced flow convergence tests in #767 run at Re = 1.

Alright after PR #910 I think we're good to go with this verification (we needed to compute vorticity at the top wall).
I produced movies for each Re (100, 400, 1000, 3200, 5000, 7500, 10000) that I'm going to upload to YouTube.
I'm attaching the last frame from each movie here showing the agreement. Vorticity seems to agree very well. Velocities at higher Re don't agree exactly but I think it's close enough for this kind of verification (maybe more simulation time is needed to reach equilibrium, but there may be several other factors).

^ Note that one of the w data points is off. This is due to a probable typo in table 2 of Ghia et al. (1983).

@ali-ramadhan should we merge? We might want to redo this experiment with new time-stepper and advection schemes, at which point we can rewrite the plotting script if we desire.

I was going to update the documentation to include a page on this verification test/experiment and try to embed some YouTube videos, but yeah might be a good chance to translate the script and try RK3 + WENO if data needs to be generated again.


Not working

JNot working for me - I have the latest of everything - Jessie, node, node-red on a Raspberry Pi - lots of nodes - just installed this - the map comes up a treat but no matter what I put into the payload as an inject - makes no difference whatsoever - I always end up with the map pointing somewhere in the south of England.
I'm putting in a string in an inject node into the worldmap node.... injecting - nothing - map stays the same even after a refresh of the page. What if anything am I doing wrong??
Pete.

working fine... resolved via mailing list.
No issue.


Update Dotnet Isolated Images with WorkerIndexingEnabled.

Add Worker Indexing enabled flag to the dotnet-isolated images natively to support customers building on custom workloads.

Builds running merging and releasing as <IP_ADDRESS>


Getting slow response time after some data points

Describe the bug
After it starts sending frames, i can only get some data points, then it becomes too slow. There was an issue adressing someone only getting one data point, tried its solution (Changing the hardcoded AP IP to my AP IP) and it didn't solve my issue, also tried all baud rates.
For all baud rates other then 1500000, i could get only one data point, for 1500000 i get the logs i posted below. The first 5 data points are almost instant, then it becomes slow.
Tool Settings

Baud Rate: tried 921600, 1000000, 1152000, 1500000, 1552000
WiFi Channel per Device: 6
FreeRTOS > Tick rate (Hz): 1000

To Reproduce
Steps to reproduce the behavior:

Build project(s) ... (active_sta)
Flash project(s) ... (active_sta)
External device setup (if applicable)
See error

Desktop (please complete the following information):

OS: Win11
ESP-IDF Version: 4.3.6

Additional context
I'm getting those logs:
I (682) wifi:AP's beacon interval = 102400 us, DTIM period = 2
-Data point-
I (1105) wifi:idx:0 (ifx:0, aa:bb:cc:dd:ee:dd), tid:0, ssn:1, winSize:64
-Data point-
-Data point-
wifi not connected. waiting...
I (1632) esp_netif_handlers: sta ip: -ip-, mask: -mask-, gw: -gatewayip-
I (1633) Active CSI collection (Station): Got ip: -ip-
-Data point-
initial wifi connection established.
sending frames.
-Data point-
-Data point-
-Data point-
-Data point-
...

Forgot to mention, but at 1000000 i get some encoding errors, nut sure if it helps tho.

@StevenMHernandez


Consider removing Rackspace support

Rackspace support has not ben updated in a few months.
cluster/rackspace/cloud-config/minion-cloud-config.yaml is using etcd_servers for kubelet and kube-proxy, but support for them has been removed since v0.9, I think.
I'll remove it in a few days if no-one makes a counter-offer to get the config working with latest release.

There's been some work on this but it is blocked while we figure out some
load-balancer design stuff.
On Thu, Apr 16, 2015 at 10:18 PM, Eric Tune<EMAIL_ADDRESS>wrote:

Rackspace support has not ben updated in a few months.
cluster/rackspace/cloud-config/minion-cloud-config.yaml is using
etcd_servers for kubelet and kube-proxy, but support for them has been
removed since v0.9, I think.
I'll remove it in a few days if no-one makes a counter-offer to get the
config working with latest release.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/6962.

Okay, I will remove the link to rackspace until it is fixed (#6987).
Leaving this issue open to remind us to delete it in, say, a month, if no progress is made.

cc @doublerr

See also #5215

I'd prefer to try to get things updated and keep support. However I don't want to continually become stale.  every few months either.

Hi all,
I want to use kubernetes on my existing rackspace infrastructure but I don't understand if rackspace suppor was removed or not. In Doc, under "custom cloud solution" it's linked but I wasn't able to deploy it neither with get.k8s.io install method nor with hack/dev-build-and-up.sh. With dev-build-and-up.sh i got a cannot allocate memory error (I have 16GB or RAM!).
thanks in advance,
Fx

It looks like no support has happened on Rackspace for a year.

You should not expect it to work, and we should delete rackspace support.

ACK.

Unfortunately I think we'll need to drop support for Rackspace as a deployment target since I can't commit to keeping the deployment scripts up to date.
Rackspace support as a cloudprovider should be maintained.

I would be willing to support the Rackspace deployment target, if there is interest to keep it alive.

@devx There would be definitely an interest from our side - sad to see that Rackspace has no interest in maintaining it

No problem, I will take over the maintenance. It will take me a bit of time to get caught up, but I will get it done as soon as possible.

@devx Do you think it would be hard to get the [OpenStack Implementation] of LBaaS (https://github.com/kubernetes/kubernetes/blob/4694a6dd7134135ce249ec403882e01a54712c4a/pkg/cloudprovider/providers/openstack/openstack.go#L509) working here ?

@w0mbat Sorry it took me a bit to respond. there is a quick update as to where I am.
I was busy with some stuff, that prevented me from working on this. But that has been resolved, and should have updates by the end of next week. However what's causing the delays is the lack of a good API for Rackspace Cloud.  I've used the gophercloud, it works but I'm not a fan.  Additionally gophercloud doesn't have full API support (one of the things I'm not a fan).  This would make it hard to implement LBaaS.  I should have a better idea of your request sometime next week.

@devx I have seen this api docu: https://developer.rackspace.com/docs/cloud-load-balancers/v1/ - is it the same as you saw? I think it should be doable with it.


fix a problem

one rest action has multiple same parameters in schema generated by swagger

based on swagger,  duplicated parameters are not allowed.
from https://swagger.io/specification/#pathItemObject
"A list of parameters that are applicable for all the operations described under this path. These parameters can be overridden at the operation level, but cannot be removed there. The list MUST NOT include duplicated parameters. A unique parameter is defined by a combination of a name and location. The list can use the Reference Object to link to parameters that are defined at the OpenAPI Object's components/parameters."

Then i will keep this on my branch. the problem is actually related to their implementation using jax-rs.
in master-update of evomaster, a funtion to remove duplicated parameters is added


New namespace fo BFO 1.1?

From<EMAIL_ADDRESS>on July 25, 2007 11:52:30
Using a new namespace requires existing consumers of BFO 1.0 to  edit their files to change all
references to 1.0 classes to 1.1 classes. This is troublesome and probably unnecessary.
Original issue: http://code.google.com/p/bfo/issues/detail?id=2

From<EMAIL_ADDRESS>on August 09, 2009 20:58:46
Resolution: Release 2 and upwards will use non-versioned ids per Foundry standard.
Status: Done


Chore(Internal): Switch all resources to use status struct with common fields

Similar to #1765 this is working towards grinding down the differences between the various resources and reconciliation functions.
The goal here is to establish a common set of fields that should always be present on a Status object.
Additional fields can then be added as necessary as seen in the Dashboard status

@Baarsgaard My concern here is that it's not a 1:1 switch, because some resources do not implement either LastResync (alert groups, contact points, notification policies) or Conditions (datasources). So, I guess we should add the missing logic either in this or a separate PR. WDYT?

The plan was to discuss what fields should be in the Common status object.
Then once we agree, add them all in this PR since unused fields don't really do any harm.
After that I would refactor each reconciler one at a time.
This way it also aligns with how @theSuess wanted to do releases previously with less changes per release.


Fix server & client typings.

Fixes #65

The commit history for this is absolutely fucked, please reopen with a new branch that has a clean commit history


[DPE-5005] Update charm to latest standards

Issue

Charm isn't up to latest standards
Library mongos_client_interface is not published.

for allure, remember to add branch<EMAIL_ADDRESS>
Branch created

remember to add to charmcraftcache-hub<EMAIL_ADDRESS>
-> https://github.com/canonical/charmcraftcache-hub/issues/81

@Gu1nness should we have a validation of the existence requirements.txt in charmcraft yaml? like here


Add Docker images that specify requirefips with GOFLAGS

Pulled out of https://github.com/microsoft/go/issues/930
Based on https://github.com/microsoft/go/issues/928

We could add tags like golang:1.21-requirefips-bullseye setting GOFLAGS=-tags=requirefips.
We only have one team who we know wants to use requirefips, and I'm not sure this image will be useful or potentially give a dangerous expectation for others who try to use it later. -tags specified in GOFLAGS are entirely dropped if -tags=... is present in the go build command, so putting it in the global environment of a FROM image seems risky if the build commands change without someone keeping a keen eye on this. And it might be difficult to keep an eye on it, because changes might come from upstream, or might be buried in a build script.
GOEXPERIMENT is a little more straightforward. You can remove an experiment by setting another (GOEXPERMENT=somethingelse), but that seems more obvious. It's easy to properly extend GOEXPERIMENT with GOEXPERIMENT=$GOEXPERIMENT,foo. I don't think it's as clear how to resolve a combination of GOFLAGS and go build -tags=....

We only have one team who we know wants to use requirefips, and I'm not sure this image will be useful or potentially give a dangerous expectation for others who try to use it later.

I think that having a requirefips image will confuse users, as it wouldn't be straightforward to grasp the differences between -fips and -requirefips.
Right now it is a niche knob that we are even documenting not to use it the general case: https://github.com/microsoft/go/pull/970/files#diff-30de323f63b7da7bd97a87d8c834d4f0a834dd78c92bb3a8f9379c218e78a924R222. With this in mind, I would not add an image for it right now. Maybe in the future expectations and/or policies change and we can reconsider it.


Copy Command ignores the vcs ignored files if those are present in build.include

Considering the following file structure and contents.
.gitignore
web/app/themes/*/
!web/app/themes/theme
node_modules

ymir.yml
...
    build:
      include:
        - web/app/themes/theme

When the copy is being done, if the theme folder has a node_modules folder, this is being added to the deployment, despite the fact the folder is being ignored on .gitignore.
I think this is happening because we include the build.include on the last step. https://github.com/ymirapp/cli/blob/main/src/Build/CopyWordPressFilesStep.php which copy over the gitignored files.
A possible solution that I see is to apply the $finder->ignoreVCSIgnored(true); at the very end.
This is currently causing the copy of thousands of node_modules files to s3.

I think you can fix this by removing the build.include option. The finder component is pretty finicky about .gitignore formatting. I've opened a few issues about it. If you look at the .gitignore for carlalexander.ca here, you'll see what I mean.
I'd change yours to be something like this:
web/app/themes/*/
!web/app/themes/theme/**
node_modules

Can you let me know if that fixes the issue?

Yes, this seems to work.

Awesome! Closing this 🙂


Lidar Data for Semantic Segmentation Test Set?

Dear authors,
I would like to express my gratitude for your work. I have been using the lidar data downloaded from your source for my experiments. However, I have encountered an issue where the timestamps of the lidar data and the semantic labels do not correspond to each other. I wanted to inquire whether the lidar data includes point cloud data corresponding to the semantic segmentation test set.
Thank you for your attention to this matter.

Hi @liupeng3425
Is this specific to LIDAR data? The timestamps between images and semantic labels are as expected?

Hi @magehrig
Thanks for your prompt reply!  Yes, the timestamps of images and semantic labels are matched.
e.g.,
zurich_city_15_a/images/timestamps.txt and zurich_city_15_a/zurich_city_15_a_semantic_timestamps.txt

However, I failed to find the corresponding lidar data by timestamps when iter over the lidar data. My code is like below:
      from rosbags.highlevel import AnyReader
      from pathlib import Path

      # get the timestamps of test data
      path = 'test/zurich_city_15_a/zurich_city_15_a_semantic_timestamps.txt'
      timestamp_data = set()
      with open(path, "r") as f:
          data = f.read().splitlines()
          for line in data:
              timestamp_data.add(int(line))

      # read lidar data from bag file
      lidar_path = 'lidar_imu/data/zurich_city_15/lidar_imu.bag'
      with AnyReader([Path(lidar_path)]) as lidar_data:
          conn = lidar_data.connections
          conn = [i for i in conn if i.topic == '/velodyne_points']
          for connection, timestamp, rawdata in lidar_data.messages(connections=conn):
              if timestamp/1000 in timestamp_data: # !!can't  find expected lidar data
                  msg = lidar_data.deserialize(rawdata, connection.msgtype)
                  # process lidar data

It is unlikely that there is an exact match. Are you able to retrieve a lidar pointcloud close to these timestamps?


Fixed a null file argument provided to the plugin constructor

Description
Added a non-null file argument in the JavaPlugin constructor used by MockBukkit.
In plain Java, having a null argument works fine, even if it is annotated as @NotNull, because annotations are not checks, only annotations.
However, it will not work when plugins are developed using Kotlin. It has very strict null-checks in place, and especially with these kind of annotations. Using MockBukkit with Kotlin results in a NullPointerException thrown by the constructor, which only accepts non-null parameters.
This PR aims at adding a non-null file argument, so that this error will not be thrown.
Note: I cannot unit-test this, as the getter method to retrieve this file is protected.
Checklist
The following items should be checked before the pull request can be merged.

[x] Version number updated in settings.gradle.
[x] Unit tests added.
[x] Code follows existing code format.

Info on creating a pull request
Before the pull request can be accepted, the version number stored in settings.gradle should be updated.
MockBukkit uses semantic-versioning (https://semver.org/)

If the PR fixes a bug in MockBukkit, update the patch version. (if the current version is 0.4.1, the new version should be 0.4.2)
If the PR adds a new feature to MockBukkit, update minor version. (if the current version is 0.4.1, the new version should be 0.5.0)
Make sure that unit tests are added which test the relevant changes.
Make sure that the changes follow the existing code format.

Note that a PR that fixes an UnimplementedOperationException should be considered a new version and not a bugfix.
The version number can be found in settings.gradle.

Note: I cannot unit-test this, as the getter method to retrieve this file is protected.

As a side note: Yes you can.
protected means package-protected. If you use the same package for your unit test class as for the class being tested, you should have access to that method.
Not sure if such a "hacky" approach is worth that though.

@TheBusyBiscuit any update? I saw there was new merges and the version string has been updated, do I need to update it as well? If so I'll do it asap


Expanded examples docstring for regridder

In GitLab by @jc-hunink on Nov 25, 2021, 14:30
Small changes in the documentation of class Regridder(object)

In GitLab by @jc-hunink on Nov 25, 2021, 21:10
requested review from @Huite

In GitLab by @JoerivanEngelen on May 11, 2022, 17:20
@Huite Could you verify if the docstring added is true? It probably requires some clarification.
I see the regrid method can regrid along 3 dimensions, so I guess ("z", "y", "x"), right? Or does that include ("time", "y", "x") as well? We could point to LayerRegridder here for people who have a layer dimension.


Fixed escaping while input are compared to existingTags

The Script didnt matched escaped Tags. The problem occours when the user entered an existing tag that contained special characters. Passing an escaped value as "existing tag" directly into the component didnt help because the escaped tag wold be displayed.

Thanks! I wasn't able to reproduce the bug myself though, so please provide specific steps/examples next time. Merged this anyway as it doesn't seem to break anything either.


wip: create in-cluster mcpc agent for diagnostic and load testing

TODO:

add README.md
use spf13/cobra for command line and flag management.
Refactor main.go into more manageable pieces
Add simulated NACK percentage rate
Add re-connection frequency parameter
Add scale parameter for additional connections (alt: simply scale the number of replicas)

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ayj
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

galley/OWNERS [ayj]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

cc @mandarjog, thoughts on putting this mcpc debug agent here or under https://github.com/istio/tools/tree/master/perf?
cc @ozevren @nmittler - any other options we may want to add for load testing Galley re: endpoints or other config churn?

@ayj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
466e69050d2ccf617e12e0172081617e8d75d11d
link
/test istio-pilot-multicluster-e2e

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

The code in istio/istio and helm charts in tools

frequent disconnect/reconnect?

Would be nice to get this in soon, as stale bot seems pretty insistent on closing this one (even with the no stale bot label!).

@ayj @ozevren if this is still needed please send it to master


[stable/openvpn] add .Values.openvpn.clientConfServer option

What this PR does / why we need it:
This PR adds an option to override the server in the remote endpoint
configuration of clients.
This is helpful if the Service is using a LoadBalancer and external-dns to support changes to the LoadBalancer IP when e.g. recreating clusters without needing to rewrite all client configs.
@jasongwartz, @dippynark, I’d be happy about your feedback :)
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

@jasongwartz, @dippynark, do you think you’ll have time to look into this?
As there’s no replacement for the stable repo yet for OpenVPN, I’d appreciate it a lot. We’ll look into maybe publishing our own fork, too.

@morremeyer Thanks for the contribution! Sorry for the silence, but I’m not able to review PRs at the moment. I’m hoping to get back to reviewing all the open PRs for the openvpn repo soon.

[remove stale label]
2 Sep 2020 06:48:57 stale[bot]<EMAIL_ADDRESS>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub[https://github.com/helm/charts/pull/23029#issuecomment-685293371], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AB2T336NBQPSXO67N5BMT7TSDXFDHANCNFSM4ONNJRJQ]. [https://github.com/notifications/beacon/AB2T336L56D7JPKO363TPTDSDXFDHA5CNFSM4ONNJRJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFDML6OY.gif]

[remove stale label]


Icon character artifact

I remade your solution to swift 5, but i can’t figure out how to hide icon “image” produced by placeholder character “\uFFFC” (i guess it´s that). Providing screenshot with partly transparent view.

Is it works fine with OC ?

you can override the method -[NSTextAttachmentContainer imageForBounds:textContainer:characterIndex:], and return nil.  which is in NSTextAttachment


Upgrade Elastic operator to 0.9.0

This is an update for the Elastic operator.
Updates to existing Operators

[X] Is your new CSV pointing to the previous version with the replaces property?
[X] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[X] Have you tested an update to your Operator when deployed via OLM?

/ok-to-test


[SPARK-11541][SQL] Break JdbcDialects.scala into multiple files and mark various dialects as private.

Merged build triggered.

Merged build started.

Test build #45161 has started for PR 9511 at commit c42e183.

+1 on splitting this file up.

Test build #45161 has finished for PR 9511 at commit c42e183.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45161/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #45171 has started for PR 9511 at commit e8db45e.

Test build #45171 has finished for PR 9511 at commit e8db45e.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * final class DecisionTreeRegressor @Since(\"1.4.0\") (@Since(\"1.4.0\") override val uid: String)\n  * final class GBTRegressor @Since(\"1.4.0\") (@Since(\"1.4.0\") override val uid: String)\n  * class IsotonicRegression @Since(\"1.5.0\") (@Since(\"1.5.0\") override val uid: String)\n  * class LinearRegression @Since(\"1.3.0\") (@Since(\"1.3.0\") override val uid: String)\n  * final class RandomForestRegressor @Since(\"1.4.0\") (@Since(\"1.4.0\") override val uid: String)\n

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45171/
Test FAILed.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #45175 has started for PR 9511 at commit 1ff523f.

Test build #45175 has finished for PR 9511 at commit 1ff523f.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45175/
Test FAILed.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #45187 has started for PR 9511 at commit 5c95b20.

Test build #45187 has finished for PR 9511 at commit 5c95b20.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45187/
Test FAILed.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #45194 has started for PR 9511 at commit 27cb354.

Test build #45194 has finished for PR 9511 at commit 27cb354.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45194/
Test PASSed.


Update rancher-images generator to support feature and system charts min/max version constraint

Problem:
The airgap image exporter selects images from the latest version of each system and feature chart. This logic doesn't work for cases like monitoring v1 where we need to update old versions of it to keep support for older k8s versions and the images aren't included because only the latest version is being used.
Solution:
Update the image exporter to support exporting images in feature and system charts based on the Rancher version constraint set for each chart.

This was bumped to 2.6.1. We should unassign reviewers for now until we wrap up 2.6.0 work.

Pass Verified in [v2.6.4-rc3](https://github.com/rancher/rancher/releases/tag/v2.6.4-rc3)
This ticket added additional constraints and added support for version specific of constraints in images files.
This also confirmed Images from unused charts are in rancher-images.txt


Support For Plugin Sharing

While the plugin system is cool and everything its completely useless without the option to send and share plugins. For example, an option in the context menu strip named "Send Plugin" or have an option in the "Send File" Named Plugin. Really as long as we can send plugins that are made by other people it would be fine.

Perhaps a better option would be to implement something similar to nanocore? each plugin has the ability add buttons to the server menu. this would make plugins seem a lot more native and would only require a little automation for the creation of the buttons with variables such as drop down names provided by the plugin itself

Perhaps a better option would be to implement something similar to nanocore? each plugin has the ability add buttons to the server menu. this would make plugins seem a lot more native and would only require a little automation for the creation of the buttons with variables such as drop down names provided by the plugin itself

Yes! That would be awesome, and was one of the things I mentioned and in my suggested features list. (Not NanoCore style exactly I was actually thinking of Orcus in that list.)


Make sure that checkpoints in PBT are removed once they are no longer…

… needed
This should solve the issue about checkpoints not being removed. I just return STOP instead of PAUSE. See the code comment why I think this is fine.
I also implemented early checkpoint removal for the synchronous schedulers, which requires the scheduler to flag paused trials for which the checkpoint is no longer needed.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I should also check what happens for synchronous multi-fidelity methods.
The potential issues with promo-based ASHA remain, because checkpoints of paused trials are never removed before the end of the experiment.

Converting this to draft. I'd still like to resoved the situation for synchronous MF schedulers

OK, this should go in, since it fixed the checkpoint situation for PBT and the synchronous schedulers. Pre-emptive removal for ASHA promotion is more complicated, I'll do it later.


Error plot brushing

Implement brushing on the Error Plot to give users a focused view on a subset of points.

[x] Research feasibility and design considerations
[x] Proof of concept / basic implementation to give visual starting point for feedback
[x] Discuss priorities and plan components of feature
[x] Figure out translation from d3 selection on plot to points on graph
[ ] Implement!

Next planned step is filming a brief video with visual examples of the kind of options with the brushing feature and writing up a few initial corresponding questions, then sending those out for feedback in the herbie channel. Goal to do that is morning of 8/28, though haven't done much on this besides previously discussed planning!

Assuming that's 8/29, that feedback plan sounds good to me! I think we can already plan to implement subset selection with what you've got, pending the solution of the bucketing issue. We can discuss in the meeting tomorrow.

Update: Thread with video of initial design considerations and discussion. General plan for details of first implementation summarized there. New related step:

[ ] Transfer those notes in a design-doc style to existing brushing doc

Notes from 9/12 meeting:

Grab subset of points selected (Point type not plot circles)
(but not until brushing is totally complete, utilize small delay?)

Make new analysis call, passing in subset of points, to get local error plot for average of points

If single point is selected, have that replace brushed area, and vice versa

UI notes:

Make brush more transparent

Current in-progress (besides above):

[ ] adjusting brushing to make sure it works with multiple expressions
[ ] actually pushing brushing to main to get more eyes on it --> send note to folks that there have been package/-lock.json changes
[ ] fixing removal of brushing (currently only works with dblclick and it's a little weird, single click partially deselects but not all)

Lower priority UI adjustments to keep in mind for later:

[ ] adding Selected point
[ ] considering Pavel's feedback:

can we make the "default" state, where you haven't brushed, the same as brushing to select the whole region? (Appear the same way in the UI)
this might mean presenting the input range differently (making it always use two pins at either side) and also maybe add a background to the not selected region instead of the selected one

Notes about difficulty with updating global variable causing re-render:

see if there's a "mouse up" or other action to see when brushing ends (while still retaining selection)
if "mouse down" bail
if trying to do continuously: consider  implementation style of retaining focus
make global variable to write to when you want to update
keep svg itself to try to keep from rerendering, just rerender the content of svg
transient vs permanent state

"mouse up" action can be detected with .on("end", () => {... originally I was using .on("brush end", () => {...
"brush end" may be the correct behavior for the highlighting as it's nice for that to be continuous as the mouse drags, but just "end" can be defined separately and may be good for helping with the global variable setting, however that doesn't fix it on its own.

(I'm sick, so not much progress) Have an in-progress attempt to save the brushing state so the selected subset of points can be stored globally and then the brushing can be reapplied after the re-render. Have yet to try to debug it, so unsure if it'll work.

Monday, I re-familiarized myself with what I was attempting earlier last week ^^, and I roughly diagnosed the current bugs, but I also reminded myself how ugly my current approach is. I expect to have a solid hour tomorrow before RA meeting to attempt those fixes I have in mind, but if it works that really just feels like a proof of concept to me, I'd love to find a cleaner way to handle it.
(Covid-catch up on all other things has left me with less time on this than I'd like, so sorry!)

Working on an attempt on the pattern we talked about in 2:1 yesterday.
This portion (the easy part) works fine with a play value for the subset analysis:
global context exists for subset of points analysis
...
in the `ExpressionTable` for each expression where the "error" and "speedup" are calculated
     if a subset of points have been selected
               instead calculate values to be rendered using subset analysis instead of standard analysis

I need to actually get that analysis value correctly which I will continue to work on before the meeting tomorrow!
Not currently blocked, though I will update here if something comes up as I continue to work on it.

I have an analysis call working on just the subset of points selected.
If I have some free time before tomorrow, I'll try to get the "cost" call working as well. I haven't looked into it much, so if it's a similar pattern it should be quick, otherwise I'm unsure.
There's also some bugginess with deselecting of a brushed region, so I'll try to debug that by tomorrow as well!

Created flag to hide brushing implementation for feature freeze

Plan by meeting tomorrow:

Will make sure all my (working) code is up to date and in main, still hidden behind the flag I made before, for now. I have a local branch and some stashed things, so I just need to get it organized and together again.
Will think about/work on how brushing will effect Error plots for multiple variables. I may have some questions on that tomorrow.
Since the analysis call has been successful, I am returning to the actual brushing appearance. I doubt I'll have much of anything new finished to demo by tomorrow though.


Recompute fees in CreateAtomicTxnWrapper

This PR has kinda increased in scope but I'm adding a description below that addresses all of the changes in this PR from feature/proof-of-stake. I'm also going to change the comparison branch to feature/proof-of-stake to make it a full review.

From @diamondhands:

Improve the error returned when we reject a txn from the mempool

This required adding a cache of the errors we produce when validating txns and using that to return the error upon request

Improve CreateAtomicTxnWrapper to add automatic fee computation

CreateAtomicTxnWrapper will now compute the exact fee required for each inner txn and update the fee on that txn if it's lower than what was computed
CreateAtomicTxnWrapper now computes the TOTAL fee required to submit the atomic txn, including the wrapper txn, and intelligently adds the extra required to the first inner txn in the list

Fix a bug in computeFeeRecursive to properly assess the nonce. Without this, we were over-estimating the fee significantly.

Fix a bug in computeFeeRecursive to properly assess signature sizes in atomic txns. Without this, we were significantly under-estimating txn size.

Introduce an UpdateTxnFee function that bundles in a special-case of updating the fee on a DAOCoinLimitOrder txn

Replaced all raw fee adjustments with a call to this function in core and backend

Mark DAOCoinLimitOrder.FeeNanos as deprecated. We don't need it after balance model, but if we don't set it to exactly the txn.TxnFeeNanos we get an error.

Add some error-checking in pos mempool that was missing

From @lazynina:

Proper sanity-checking of atomic txns

Add nonce handling for atomic txns

Although note there is still a TODO to add a synthetic nonce for atomic txns so that you can replace them by fee. This isn't time-sensitive so we're punting on it. Added a TODO in addTransactionNoLock for it.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1183  👈
#1156
feature/proof-of-stake

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @lazynina and the rest of your teammates on  Graphite

Merge activity

Apr 9, 2:42 PM EDT: @lazynina started a stack merge that includes this pull request via Graphite.


dotnet app example fails when you use GitBash with Unhandled Exception

What version of gRPC and what language are you using?
C#
What operating system (Linux, Windows, …) and version?
Windows 10
What runtime / compiler are you using (e.g. python version or version of gcc)
dotnet --version
2.1.503
What did you do?
If possible, provide a recipe for reproducing the error. Try being specific and include code snippets if helpful.
What did you expect to see?
I follow the quick start of C#
https://grpc.io/docs/quickstart/csharp.html
When I start the GreeterServer on the GitBash, it fails.
$ dotnet run -f netcoreapp2.1
Greeter server listening on port 50051
Press any key to stop the server...

Unhandled Exception: System.InvalidOperationException: Cannot read keys when either application does not have a console or when console input has been redirected. Try Console.Read.
   at System.ConsolePal.ReadKey(Boolean intercept)
   at System.Console.ReadKey()
   at GreeterServer.Program.Main(String[] args) in C:\Users\tsushi\Codes\grpc\grpc\examples\csharp\Helloworld\GreeterServer\Program.cs:line 46

What did you see instead?
It works on cmd.
Anything else we should know about your project / environment?
I have workaround. However, I'd like to know why it happens.  Someone new might confused if there is no direction for not using GitBash.

maybe it's not grpc problem.
As you say, System.ReadKey is always failed when running on mintty directly.
I used winpty dotnet [args] for workaround.

Ok, given the exception message surfaced, this doesn't look like an issue within grpc, so closing. Thanks for the update


Enable async action closure in ConsentView

Async action within OnboardingActionsView
:recycle: Current situation & Problem
The ConsentView takes an action closure that is synchronous in nature. This closure is passed to the OnboardingActionsView which also takes an asynchronous function.
:bulb: Proposed solution
Enable passing an asynchronous function to the ConsentView.
This enables the following code block:
ConsentView(
    header: ...,
    asyncMarkdown: ...,
    action: {
        await testFunction()
    }
)

:gear: Release Notes

ConsentView action parameter takes an asynchronous closure

:heavy_plus_sign: Additional Information
--
Related PRs
SpeziTemplateApplication PR
Testing
--
Reviewer Nudging
Very minor code changes
Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[X] I agree to follow the Code of Conduct and Contributing Guidelines.

@PSchmiedmayer Thanks for the feedback, the branch is now ready to merge, all lints and tests in the pipeline finish successfully. However, some checks are staying on "Wating for status to be reported" (the same also happenes in another repo), even though the actual job (e.g. linting) ran through. Retriggering the CI didn't help. Any hints?

@philippzagar Sorry about that; I need to update the CI requirements as we did some changes under the hood. Will do that and merge the PR in a second 👍


Update chainsync to work with events

The functionality will be relatively unchanged at first, as this is an "under the hood" modification. However, it will unlock new features:

add ability to boot into iHyperdrive from any chain block
“replay history” feature & "backtesting"
shift repo in the direction of a more general utility
allow us to sync wallets more easily with a single utility

Added via https://github.com/delvtech/agent0/pull/1464


Feature: Turn user profile pages into Server-side rendering to enable SEO & Microformats

Type of feature
🍕 Feature
Current behavior
Currently the user profile pages inner content are client-side rendered, and here's the illustration from google crawl bot:

The user data itself isn't server-side rendered, so can't be crawled and the SEO & microformats won't work on it.
Suggested solution
Activate server-side rendering for these pages.
Additional context
No response
Code of Conduct

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

Contributing Docs

[ ] I agree to follow this project's Contribution Docs

We should call them "schemas" or the official "structured data markup" to avoid confusing them again with v2 microformat 🍕


c++ implementation of cost state and ctrl + bindings

In GitLab by @cmastalli on Jul 18, 2019, 17:39
null

In GitLab by @cmastalli on Jul 18, 2019, 17:39
assigned to @cmastalli

In GitLab by @cmastalli on Jul 26, 2019, 13:26
mentioned in merge request !181

In GitLab by @cmastalli on Jul 26, 2019, 13:26
closed


Add Read organizations by ids permission

Adding missing scope needed for migration. Will need to remove scopes due to permissions migration.
new permissions migration guide

Closing since this is a bit old and needs to be re-investigated (and some tests added for linkedin)


Publish a 2nd recommended ruleset that contains only the contrib rules

Hello there,
I'm in a situation I'd like to be able to pull and use the bleeding edge code from the master branch (specifically, because in 2.0.13, still having no-duplicate-key set to true is breaking my build).
Would this be possible?
Thanks so much.

An alternative to this would be to strip out all rules not residing in this project from the tslint.json file.
Users who "extends": ["tslint-microsoft-contrib"] may not be aware that by extending this project, they're also extending tslint proper.

@dsifford have you tried using our "releases" branch? It is the latest compiled code. Does that fix the issue
I'm not sure how having the source code in the /dist dir solves your problem.
(sorry, I thought I'd replied to this earlier).

@HamletDRC No worries.
No, the releases branch did not work for me. I'm using the nightly branch of tslint and that was not cooperating with the fact that if I extend your releases branch, I'd also be extending the no-duplicatekey` rule from tslint proper (which is set in your tslint.json).
I think the main issue is that this repo creates a circumstance that results in an "extends cascade". In other words, if I extend this repo, I'm also extending all the repos that you extend (or, in this case, the rules from tslint proper that you have set in your tslint.json file).
I ended up just removing the extends rule for this repo from my project for now until your tslint.json is free of the no-duplicate-key rule.
(I hope that makes sense. It's admittedly a bit confusing).

@dsifford so your problem would be solved if we published a 2nd tslint.json that only contained our rules, right?

Correct

💀 It's time! 💀
TSLint is deprecated and no longer accepting pull requests other than security fixes. See #876. ☠
We recommend you instead use typescript-eslint to lint your TypeScript code with ESLint. ✅
👋 It was a pleasure open sourcing with you!


too small a value error in "min(exp(B*alpha))" while running ISMA fit

I am trying the toy fitting problem (Figure 3) from the paper "Data fitting with geometric programming compatible function". I did manage to get the 'MA' and 'SMA' fit, however while trying the 'ISMA' fit i am constantly encountering the "Fitted constraint with too small values" error in the parameters value after running levenberg-marquardt algorithm. I did check the implementation a lot of times and i ended up getting the same error either in the parameter B( with too small value) or in the parameter A (with too large value). Is there a work around to this problem? Please note that I tried initializing the parameters using both 'MA' and 'SMA'. The alpha_init value was set to 1. And the lambda to be 0.2.

This is likely because you have too many posynomial terms. What is the dimension of your data, and the parameters of your fit? Also, you can try disabling the error in the source code and see what you get.

(you can find the directory of gpfit by calling import gpfit; gpfit.__path__.)

i just have a 1D data with 50 points. x.shape = (50,1),  y.shape=(50,1) and K=3 affine planes. With that i am supposed to get the constraint "1 = (linear combination of 3 affine planes)". I did try bypassing the constraint fit (cs = FitCS(fitdata)) and also tried disabling the errors, but still faced the same issue.

Sorry, I should have realized you were trying to replicate the example.
The issue is not in FitCS though, it is on lines 111-112 of fit.py. Have you tried commenting those?

Oh yes i did. Facing same issues

I'm trying to replicate now. I am currently using gpfit with no issues on similar examples, so this is odd.

Alright, I replicated with the following MWE (please provide this for future issues):
np.random.seed(314)
x = np.arange(-2,2,0.01)
a = -6*x + 6
b = 1/2*x
c = 1/5*x**5 + 1/2*x
y = np.max([a,b,c], axis=0)
K=3
cstrt, rms = fit(x, y, K, "ISMA")

The issues can be caused by random seed. I put 314 and issues were fixed.

the value of a is -6*x-6. Even with random seed i am encountering the "RuntimeWarning: invalid value encountered in double_scalars
abs(RMStraj[itr] - RMStraj[itr-2]) <" in levenberg_marquardt.py.

Here's the deal. I ran the LM algorithm with high verbosity for a shorter maxtime, and here are the results.
## -- End pasted text --

                    First-Order                        Norm of

Iter        Residual        optimality            Lambda            step        Jwarp

    0         0.513567             75.1

    1              inf             75.1                0.02               230.6        3.17e+06

    2              inf             75.1                 0.2               51.39        3.17e+06

    3              inf             75.1                   2               19.99        3.17e+06

c:\users\berk\dropbox (mit)\mit graduate school\code\gpfit\gpfit\levenberg_marquardt.py:112: RuntimeWarning: invalid value encountered in double_scalars
  abs(RMStraj[itr] - RMStraj[itr-2]) <
    4         0.511031             31.3                  20               2.786        3.17e+06

    5         0.508551             29.6                  20               4.319        3.42e+06

    6              inf             29.6                   2                8.12        3.933e+06

    7         0.506592               28                  20              0.8293        3.933e+06

    8         0.504837             26.6                  20              0.8376        4.582e+06

    9         0.494917             19.2                   2               3.416        5.262e+06

   10              inf             19.2                 0.2               21.68        7.78e+06

   11         0.487916             15.4                   2                8.11        7.78e+06

   12         0.482042             13.4                   2               4.453        3.844e+07

   13              inf             13.4                 0.2               54.59        7.21e+07

   14         0.476498             14.3                   2               23.94        7.21e+07

   15         0.471157             14.7                   2               10.64        6.618e+08

   16              inf             14.7                 0.2               227.3        1.266e+09

   17         0.465943             14.7                   2               102.9        1.266e+09

   18         0.460868             14.6                   2               22.93        4.715e+10

   19              inf             14.6                 0.2                1913        6.755e+10

   20         0.455908             14.4                   2               705.4        6.755e+10

   21         0.451069             14.2                   2               52.03        3.704e+13

   22              inf             14.2                 0.2           3.991e+04        1.988e+13

   23         0.446337             13.9                   2                8187        1.988e+13

   24         0.441714             13.7                   2               166.2        3.744e+17

   25              inf             13.7                 0.2           3.557e+06        1.272e+17

   26         0.437194             13.5                   2           5.656e+05        1.272e+17

   27         0.432772             13.2                   2                 300        6.785e+24

   28              inf             13.2                 0.2            1.38e+10        3.008e+24

   29         0.428445               13                   2           4.394e+09        3.008e+24

   30         0.424206             12.8                   2               131.8        2.879e+40

   31         0.388818             10.7                 0.2              0.8375        1.574e+40

   32         0.463318             10.7                0.02               6.135        1.027e+40

   33         0.359146             9.24                 0.2              0.3963        1.027e+40

   34           0.3343             8.08                 0.2              0.4035        2.152e+40

   35         0.269662             12.8                0.02               4.806        1.794e+40

   36              inf             12.8               0.002                3.69        1.647e+39

Reached maxtime (0.15 seconds)
Final RMS: 0.269662263366964
ISMA fit from params
1 = (1/w**2.27559e-10) * (u_1)**-1.21462e-09
    + (0.990747/w**0.770619) * (u_1)**0.364169
    + (9.9639e-06/w**1.6515) * (u_1)**10.6377

It is clearly converging towards an optimum...

But for some reason it ends up getting derailed.

Fyi, the occasional infs in the residual give the warnings. I didn't write the algorithm so I don't know how the method navigates these solutions. But it is clear that as the solution is further refined, the singularity of the coefficients get worse.

Actually i did do the same thing just now. Printed out the residuals as a sanity check. I got similar results like you posted.  It is strange that ISMA works perfectly well for a log-space transformed input and gives out a perfect GP compatible fit function. However, it is just for this problem, the residuals go wild. Thanks a lot for helping out though.

No problem! I will keep this issue open since this is undesired behavior, and one that should probably be addressed. I am 95% certain it is because of the kink in this specific function.

I have a small query in plotting the ISMA fit function.  Currently the f_{ISMA} function that i computed is f_{ISMA}= max(b_k+a_k.Tx), b_k and a_k being the parameters and x being the independent variable of the dataset. With that function, $\hat f_{ISMA}$ = log(sum(exp(alpha(b_k+a_k.Tx-f_{ISMA}(x)))) = 0. When i plot x against the f_{ISMA} function, which is implemented as max(np.dot(X,ba)), i get the following plot.

Somehow for data points x >=0.6, the fit function is not approximated properly. I am not sure if i am plotting the right thing here or is it due to the 1st order optimality condition not achieved.


Add metis goerli testnet

Pending
Waiting for https://github.com/safe-global/safe-singleton-factory/issues/82 to be closed in order to deploy

Let us know when it's available on https://chainlist.org/

I have read the CLA Document and I hereby sign the CLA

@Uxio0 it's available now on chainlist, https://github.com/ethereum-lists/chains/pull/1736 was meged

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Files with Coverage Reduction
New Missed Lines
%

gnosis/eth/ethereum_client.py
1
81.1%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
3277

Relevant Lines:
3905

💛  - Coveralls


Fix JS tests in CI

Codecov Report
Base: 83.80% // Head: 83.88% // Increases project coverage by +0.08% :tada:

Coverage data is based on head (84c4cc1) compared to base (a1f4bfb).
Patch coverage: 77.98% of modified lines in pull request are covered.

:exclamation: Current head 84c4cc1 differs from pull request most recent head 1d0755f. Consider uploading reports for the commit 1d0755f to get more accurate results

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #119      +/-   ##
===========================================
+ Coverage    83.80%   83.88%   +0.08%
===========================================
  Files           17       17
  Lines         2099     2178      +79
===========================================
+ Hits          1759     1827      +68
- Misses         340      351      +11

Flag
Coverage Δ

unittests
83.88% <77.98%> (+0.08%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/common/wallet.c
84.64% <76.97%> (+0.03%)
:arrow_up:

src/common/buffer.h
100.00% <100.00%> (ø)

src/common/wallet.h
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


allow sidebar content to scroll

Fix for #23

Sweet!  I noticed this last night and was planning to tackle it this morning, what a pleasant surprise.
Thank you so much @asarode! :+1:


Tweaked Platformer Example

Improvement to the platformer example
Description
When checking out the platformer example I noticed that the movement of the player is very weird.
The player cube is rotating and gets stuck to a wall if you keep pushing against it.
I made a minor improvement by changing the player model to a sphere with a radius of 0.5;
Then I added a little line of code to teleport the playermesh to the sphere ( instead of making it a child, which rotates the cube aswell when the sphere is moving).
I also increased the angular damp of the player to decrease the sliding.
This together makes the controls feel more familiar to a classic platformer.
scene img
code img
nsp file
Version

nunuStudio V0.9.2 Beta Build<PHONE_NUMBER>28

Hi viktor
Thanks a lot it does feel better.
When i was writing that tutorial i actually had planned to have the player collider as a sphere but i kinda feels "cool" to see the cube tumbling around.
I think that it would be nice to add this as an extra step in the tutorial "Tweaking player collider" what do you think?
Cumps

Hello,
I have made a pull request, where I have added the extra step to the tutorial.
I don't know if it fits the rest of the the tutorial but you can take a look at it.
#86
-Viktor

Thanks a lot viktor.
PR was merged.
I have changed it a bit (hope that you don't mind).
Cumps.


test2: this pr for test rerere CI

What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
Proposal: xxx
What's Changed:
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
PR to update pingcap/tidb-ansible:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note

/rerere

/rerere


Fix CNAME issue

@bhawnasehgal with this update CNAME file will only be uploaded to upsidedownlabs gh-pages. Please review and merge.

@bhawnasehgal merging it to check if it works, I hope that's fine.


Unable to find type [VSTeamVersions]

Steps to reproduce

On a windows Server 2012 R2 machine.
Install latest VSTeam powershell module.
Create a new PowerShell script (ps1) file and call 'Import-Module -Name VSTeam' in the script.
Execute the script in PowerShell console.

Expected behavior
The PowerShell module VSTeam should import successfully.
Actual behavior
An error is thrown, please see the log output below
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\VSTeam.psd1'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\Approvals.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\builds.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\cloudSubscriptions.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\repositories.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\policies.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\releaseDefinitions.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\releases.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\serviceendpoints.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\team.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\teammembers.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\teams.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\tfvc.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\users.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\workitems.ps1xml'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\pullrequest.ps1xml'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\formats\Approvals.format.ps1xml'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\formats\builds.format.ps1xml'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\formats\policyTypes.format.ps1xml'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\formats\profile.format.ps1xml'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\formats\serviceendpoints.format.ps1xml'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\formats\serviceendpointTypes.format.ps1xml'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\formats\team.format.ps1xml'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\formats\users.format.ps1xml'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\formats\workitemTypes.format.ps1xml'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\formats\workitems.format.ps1xml'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\formats\vsteamPSDrive.format.ps1xml'.
VERBOSE: Populating RepositorySourceLocation property for module VSTeam.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\src\teamspsdrive.ps1'.
VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\src\teamspsdrive.ps1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\src\team.psm1'.
Unable to find type [VSTeamVersions].
At C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\src\team.psm1:504 char:1
+ [VSTeamVersions]::ModuleVersion = _getModuleVersion
+ ~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (VSTeamVersions:TypeName) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : TypeNotFound

Import-Module : The module to process 'C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\src\team.psm1', listed
in field 'NestedModules' of module manifest 'C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\VSTeam.psd1' was
not processed because no valid module was found in any module directory.
At C:\ReleaseManagement\InstallScripts\WindowsUpdateMonitor.ps1:20 char:1
+ Import-Module -Name VSTeam -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (VSTeam:String) [Import-Module], PSInvalidOperationException
    + FullyQualifiedErrorId : Modules_ModuleFileNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

Environment data

> $VSTeamVersionTable

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.1.14409.1005
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14409.1005
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Please note that if I use VSTeam version 3.0.x the module is imported successfully without any errors.

can also reproduce it on a Win10 system
> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.1.15063.1292
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.15063.1292
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

same effect when importing module from cloned repo in some script:
import-module C:\...\vsteam\VSTeam.psd1 -verbose

Looking into this now.

I just RDPed into a Windows Server 2012 R2 machine and installed 4.0.10 as administrator.
I then created a file named import.ps1 with the following in it:
Import-Module -Name VSTeam -Verbose
When I run the script:
. .\import.ps1
I don't get any errors.
Can you see if you have mulitiple versions installed?
Get-Module VSTeam -ListAvailable
Do you see multiple versions?

I don't have multiple versions installed that I can see. Please see the output below:
Copyright (C) 2016 Microsoft Corporation. All rights reserved.
PS C:\Users\myusername> Get-Module vsteam -ListAvailable
    Directory: C:\Program Files\WindowsPowerShell\Modules
ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Manifest   4.0.10     VSTeam                              {Add-VSTeamAzureRMServiceEndpoint, Add-VSTeamSonarQubeEndp...

I create a fresh Windows Server 2012 R2 in AWS using CloudFormation.
I install VSTeam module as administrator.
I open windows Powershell ISE, I create new ps1 file with the following in it:

Import-Module -Name VSTeam -Verbose

I close windows PowerShell ISE.
I open a new Windows PowerShell command prompt.
I browse (cd) to the directory containing the new ps1 file and I execute it.
I see the following errors.

PS C:\ReleaseManagement> .\test.ps1
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\VSTeam.psd1'.
VERBOSE: Loading 'TypesToProcess' from path 'C:\Program
Files\WindowsPowerShell\Modules\VSTeam\4.0.10\types\Approvals.ps1xml'.
...
VERBOSE: Populating RepositorySourceLocation property for module VSTeam.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\src\teamspsdrive.ps1'.
VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\src\teamspsdrive.ps1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\src\team.psm1'.
Unable to find type [VSTeamVersions].
At C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\src\team.psm1:504 char:1
+ [VSTeamVersions]::ModuleVersion = _getModuleVersion
+ ~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (VSTeamVersions:TypeName) [], RuntimeException
    + FullyQualifiedErrorId : TypeNotFound

Unable to find type [VSTeamVersions].
At C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\src\team.psm1:507 char:33
+ Set-VSTeamAPIVersion -Version $([VSTeamVersions]::Version)
+                                 ~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (VSTeamVersions:TypeName) [], RuntimeException
    + FullyQualifiedErrorId : TypeNotFound

Set-VSTeamAPIVersion : Cannot validate argument on parameter 'Version'. The argument "" does not belong to the set
"TFS2017,TFS2018,VSTS" specified by the ValidateSet attribute. Supply an argument that is in the set and then try the
command again.
At C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.10\src\team.psm1:507 char:31
+ Set-VSTeamAPIVersion -Version $([VSTeamVersions]::Version)
+                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Set-VSTeamAPIVersion], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Set-VSTeamAPIVersion

VERBOSE: Importing function 'Add-VSTeamAccount'.
...
PS C:\ReleaseManagement>

Are you able to use the module from PowerShell? Does it only fail when called from Scripts?
I am also not sure why you need to import the script again. Once you install as an Admin it should be auto loaded and available to your script.
Can you share your Get-ExecutionPolicy output?  Mine is RemoteSigned.

Only a wild guess : execution context / scope is different when imported from a script compared to importing from the command line. Class definition for VSTeamVersions is not added to the scope of the script.
This must somehow relate to the breaking change from v3 to v4.

I am still stumped on why I can't repro. I believe you it is throwing for you but I can't seem to get it to do that. So I am thinking it is an environmental issue or it would be breaking for me as well.  We need to figure out how I can repro as well so we can identify the culprit.

@DarqueWarrior  - I now have a reproducible case on a plain / new Windows 2016 Server (Azure VM) - I do it again and record the steps

I don't know if this helps, because it doesn't seem like it would be very reproducible, but on a win 10 machine with VSTeam 4.0.12, I was able to ipmo fine, but...
Add-VSTeamAccount -Level Process -PersonalAccessToken <validToken> -Account <accountName> -Version VSTS
...produces a bunch of "Unable to find type [VSTeamVersions]" exceptions.

When I get a moment I will try @KaiWalter steps to repro and see if I can get to the bottom of this.

I had to load it with Using module "C:\Program Files\WindowsPowerShell\Modules\VSTeam\4.0.12\VSTeam.psd1" Apparently classes aren't loaded when using Import-Module
Hope that helps.

I've the same issue. When running a vsteam command using version 4.0.12 I get a whole bunch of Unable to find type [VSTeamVersions].
At C:\Users\stefstr\Documents\WindowsPowerShell\Modules\vsteam\4.0.12\src\team.psm1:428 char:13

        [VSTeamVersions]::Version = 'VSTS'

        ~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (VSTeamVersions:TypeName) [], RuntimeException
FullyQualifiedErrorId : TypeNotFound

errors.

Having same issue here on Win7. Install (from command line or script) works fine but command execution (e.g. Add-VSTeamAccount) from command line or script results in many
Unable to find type [VSTeamVersions]

I am going to call in some big guns in the PowerShell world to help me figure this out.

Not able to repro on Win10, Win2k12, nor macOS running Get-VSTeam.  For those who are hitting an issue, perhaps try using powershell -noprofile to eliminate the possibility something in the profile is causing issues?

Not sure if this helps, but this morning I was having the same issue after I installed the module from the 64bit window.  Just for giggles I tried it again from the x86 window, it worked, but I noticed it was referencing the module in C:\Program Files\WindowsPowerShell instead of x86 .  After that I tried using it again from the 64bit window and everything worked fine.  I can't really explain it.   I work from a Windows 10 Pro machine.

Thanks for the data.  I am working a huge restructure of the module that might help with this. Once it is out it will be version 6.0.

Can someone who could repo this please re-test with version 6.0.x?

@DarqueWarrior I checked positive with my reproducible setup (see my comment on Oct 20, 2018) and one of my regular machines.

Hey @KaiWalter you re-tested with 6.0.x and it still does not load?

@DarqueWarrior, sorry "checked positive" seems a bit confusing. I re-tested on 3 different setups (on 2 of them I had problems and the module was not loading with 5.x) and now it is loading and working perfectly!

Got it. So I can close these finally!  :). Thanks for confirming.


This Plugin not working on ios 16.2

am using MAUI framework and ios emulator 16.2
this plug showing an empty page with nothing on ios emulator 16.2

Can you provide a sample solution showing this?

@LuckyDucko  it shows a blank popup without controls on physical device (14 pro max)


Segment settings are not updated

Describe the bug
Analytics settings are not updating
To Reproduce

Create an Android source in Segment's web app
Add a destination
In the mobile app integrate with that destination (usually the destination's dev provides a segment integrated library)

Observed behavior
The newly added destination is not returned by https://cdn-settings.segment.com/v1/projects/$writeKey/settings.
If I make additional changes of the Android source in Segment's web app (e.g. delete a destination) its values are still returned too.
Expected behavior
The newly added destination & its settings should be returned by https://cdn-settings.segment.com/v1/projects/$writeKey/settings
Platform:

Library Version in use: 1.7.0
Platform being tested: Android

hey @peterplamenovpenchev, thanks for bring this to our attention. looks like the cdn server is not reflecting the changes. we're looking into this.

got a response from the team. the cdn server can take up to a day to reflect the changes. sometimes if you request it enough times it will get cached and then you will have to wait for the cache to expire. closing out this issue since this is normal. feel free to reopen it if your issue still persists.

Thanks @wenxi-zeng.


<Tabs client:visible> in Docs code doesn't sync tabs anymore

📝 Issue Description
We had to change <Tabs client:visible> to <Tabs client:idle> in the docs code {Astro v3 PR](https://github.com/withastro/docs/pull/4461).
This is simply an issue to track that we changed it and probably need to change it back sometime in the future!
📋 On which page(s) it occurs
all pages where the <Tabs> Preact component is used
🤔 Expected Behavior
🤷♂
👀 Current Behavior
🙅♂
🖥 Browser
All of 'em
📄 Additional Information
No response

Hey @ElianCodes I was testing the website on my end and tabs seem to be syncing for me on chrome & safari. I'm curious about which browser are you using.

@ElianCodes can you confirm whether this is still something to be concerned about with the migration to Starlight?

This is fixed in the Starlight migration with the replacement of the Preact component

Right! I kinda forgot about this! Thanks @TheOtterlord !


CSS collisions with class .active

Occasionally I run across a site whose CSS declares styles for the class .active. Here's an example: http://gohumansocal.org/Pages/Home.aspx
The display of the status bar is sometimes affected by these rules. The only solution I can think of is to change the class name to something more distinct, maybe "status-bar-active" or something. Any chance someone could do this?
Thanks for the great extension!

I am not seeing any problems on that page, do you have the latest version of the extension? Still, I came up with a possible fix that will now wait to be reviewed.

Ah, I must have been running some different branch (1.8 instead of 1.18?). In the current version the problem is fixed, by including a lot of reset-style CSS rules marked !important. Thanks!


Update dependabot yml

Done as of https://github.com/AdvisorySG/mentorship-streamlit/commit/17fbcbf0aaa2015920e660fe787167142e720586.


Revise content around downloads

Our website hasn't been updated in a notable way content wise since ASF. We should do that.
Here's some advice from @nacx

A download page in addition to the quickstart one with links to the official Apache release (which are the source archives) as the first option. To quote an example from LEGAL-270, All official Apache releases are in source form; Docker images can be built from our official source releases, but are derived distributions analogous to, say, Debian packages. So when we say official releases, we refer to the source archives the PMC votes upon.

That's it. The main project website should have pointers to the official Apache source releases. Currently it only has the Quickstart guide and newcomers coming to Zipkin reading the website to learn about the project will just see the Docker image, the built jar, and a link to Github (that host the source archives for the tag, wihch is not exactly the same as the ASF source release as voted and published to the ASF repos).

Take this into account when creating the download page: https://www.apache.org/dev/release-distribution.html#download-links

this changes the script to intentionally not use apache maven repo https://github.com/apache/incubator-zipkin-website/pull/13

A rough look and I notice a huge variety in satisfying the download page rule.
For example, ZK only mentions their combined source+binary release from apache sites and doesn't mention anything else https://zookeeper.apache.org/releases.html This probably works as they are a monorepo project
Dubbo is a non-monorepo project and they break down their download page based for some of their repos https://dubbo.incubator.apache.org/en-us/blog/download.html Similarly, they do not mention maven at all. In this case they do not mention all of their projects. For example, they have several repos which have never had an ASF release, yet this seems to be non-blocker for graduation (news to me)
My 2p is that we so the least efforts required here. ZooKeeper's approach is maintenance free in so far as it doesn't imply duplicating information like version numbers. I think if we combine this with a caveated quick start which mentions this uses maven central and blah .. we could be good.

chatting with @michaelsembwever I'm really uncertain the value of distracting folks with every minor repo on the main website. For example, https://github.com/apache/incubator-zipkin-layout-factory  is not going to bring value to end users advertising.
I think the ASF rules were written in days of monorepos and it is really almost all apache projects are monorepos. Zipkin is the largest project in terms of repo count to ever go through incubation.. at least pages of scrolling tells me this..
I would strongly prefer if we can simply document the source of the main zipkin codebase and leave it at that. This means that in subordinate repositories people can refer to README which all list where the sources are.

I would strongly prefer if we can simply document the source of the main zipkin codebase and leave it at that. This means that in subordinate repositories people can refer to README which all list where the sources are.

This seems reasonable to me and what users would generally expect.

You may be correct that Zipkin has a large number of repositories. OpenWhisk has 51 repositories and 20 different releases. NetBeans had 676 different release artifacts.
If you wish to graduate from the Incubator you need to comply with policy and point to all of your current releases. You can certainly highlight what is most important to users first and reference the others.
This page http://zipkin.apache.org/pages/community.html needs to reflect the Apache Zipkin podling. Have you considered naming this Apache OpenZipkin

totally right about OpenWhisk having more repositories. I missed that. Hopefully, they have a lot more people working on ASF related stuff. Seems they might, but good luck to them anyway!
We don't yet have so(1) Podling Suitable Name Search: https://incubator.apache.org/guides/names.html#conducting_a_suitable_name_search
To your question, we have no plans to double-brand zipkin with Apache and Open..

aside to this topic, but added note about podling search to the main graduation issue also https://github.com/apache/incubator-zipkin/issues/2544

for those curious, netbeans has only one download on their page, so not particularly relevant to this topic apart from workload comparisons..
OpenWhisk otoh is very relevant..  they have a categorized website to help steer people through it. https://openwhisk.apache.org/downloads.html
The below is about the legal feasibility about borrowing the code if it helps (both sites are jekyll)..
The website is mostly IBM staff, and includes an IBM-specific copyright note in their license. The ASF downloads page is also written by IBM, but it was contributed after incubation. This makes sense as this is an ASF requirement and not relevant pre-ASF.
If we borrowed code contributed after ASF, written by a vendor in a project with the same vendor in copyright notices.. would we require adding "Copyright 2015-2017 IBM Corporation" to our LICENSE file? ITOW is the LICENSE addendum forever, or only up to the dates mentioned about the vendor.

Regardless, of implementation, let's go with what @dave2wave mentions and prioritize the download page in order of relevance, noting all the downloads. We've spent more time discussing this than probably desired, and probably adding internal downloads won't make the page much worse.

there were some various things busted in our website, so I fixed them today. I will work on the downloads page tomorrow.

very popular issue! I guess this is the most important issue in all of zipkin. We got yet another email about this, this time from craig, eventhough we noted this many times.
I will still do this today since clearly no one else will
Please note that this announcement does not meet requirements for release announcements.

For the next release, please create a downloads page for the release artifacts that includes https links to the mirror download site, the checksums and signatures. The download page also needs an https link to the KEYS file and instructions how to verify the release.

You might consider having a single download page that contains information about all of the components that you release separately.

http://www.apache.org/legal/release-policy.html#release-announcements

done hopefully https://github.com/apache/incubator-zipkin-website/pull/17


debug_assert! fails silently

Description
I'm submitting a ...

bug report

debug_assert! does not output a browser console message when it fails.  This issue started after migrating the codebase from using stdweb/cargo web to wasm-bindgen/wasm-pack.
FWIW dbg! and panic! output a console message as expected.
Context (Environment)

Rust: v1.37.0 (eae3437df 2019-08-13)

yew: Latest commit of master branch (56de638)

target: wasm32-unknown-unknown

wasm-bindgen: v0.2.42

wasm-pack: v0.8.1

This is not a bug.  As stated in the wasm-pack build profile documentation at https://rustwasm.github.io/wasm-pack/book/commands/build.html#profile "If none is supplied, then --release is used".  The consequence of that is that debug info is not included in the built artifact.
When passing --dev or --profiling to wasm-pack build, debug_assert! outputs a browser console message when it fails as expected.


bin/libgmssl.so.3.0: undefined reference to `_rdseed64_step'

make demo_zuc                                                                      [14:42:28]
[ 96%] Built target gmssl
[ 96%] Linking C executable bin/demo_zuc
bin/libgmssl.so.3.0: undefined reference to `_rdseed64_step'
collect2: error: ld returned 1 exit status
CMakeFiles/demo_zuc.dir/build.make:103: recipe for target 'bin/demo_zuc' failed
make[3]: *** [bin/demo_zuc] Error 1
CMakeFiles/Makefile2:218: recipe for target 'CMakeFiles/demo_zuc.dir/all' failed
make[2]: *** [CMakeFiles/demo_zuc.dir/all] Error 2
CMakeFiles/Makefile2:225: recipe for target 'CMakeFiles/demo_zuc.dir/rule' failed
make[1]: *** [CMakeFiles/demo_zuc.dir/rule] Error 2
Makefile:216: recipe for target 'demo_zuc' failed
make: *** [demo_zuc] Error 2

ubuntu version：
Description:    Ubuntu 16.04.7 LTS

glibc version:
(Ubuntu GLIBC 2.23-0ubuntu11.3

The fix, that worked for me:
in file  src/rdrand.c
+#include <x86intrin.h>

I will post an PullRequest to fix it

建议使用Cmake编译时加上cmake .. -DCMAKE_INSTALL_PREFIX=/usr/local/gzgmssllib ，我是在centos8.2编译时使用的该命令，完美解决该问题

大佬们你们都是怎么解决的？

make demo_zuc                                                                      [14:42:28]
[ 96%] Built target gmssl
[ 96%] Linking C executable bin/demo_zuc
bin/libgmssl.so.3.0: undefined reference to `_rdseed64_step'
collect2: error: ld returned 1 exit status
CMakeFiles/demo_zuc.dir/build.make:103: recipe for target 'bin/demo_zuc' failed
make[3]: *** [bin/demo_zuc] Error 1
CMakeFiles/Makefile2:218: recipe for target 'CMakeFiles/demo_zuc.dir/all' failed
make[2]: *** [CMakeFiles/demo_zuc.dir/all] Error 2
CMakeFiles/Makefile2:225: recipe for target 'CMakeFiles/demo_zuc.dir/rule' failed
make[1]: *** [CMakeFiles/demo_zuc.dir/rule] Error 2
Makefile:216: recipe for target 'demo_zuc' failed
make: *** [demo_zuc] Error 2

ubuntu version：
Description:    Ubuntu 16.04.7 LTS

glibc version:
(Ubuntu GLIBC 2.23-0ubuntu11.3

The fix, that worked for me: in file  src/rdrand.c
+#include <x86intrin.h>

I will post an PullRequest to fix it

nice bro!


added num image recomputation on slotchange

this allows user-defined polymer elements to include an image-carousel, and populate it using dom-repeat.  An element to demonstrate this, image-carousel-demo-app.html, had been added, and demo/index.html updated to show its usage.
Once this has been accepted & merged, I'll create an additional pull request for a selection notification.

Can you add new test cases also?

Also can you remove the listener in disconnectedCallback

I added a test case, but its very simple.  I think I should create a fixture which instantiates image-carousel-demo-app and populates the slot in the fixture, rather than using the addLightDom() method.  That way, I can then query for the number of images to see if the slot was filled correctly.  I assume that it's possible to do so -- what do you think?

Ya, i think your test case should also make sure that the event was fired and right information was passed down.

I've updated the test to check that the number of images is correct (should be 3).  Also verified that this was actually a bug by commenting out the fix, which caused the test to fail with _numberOfImages=0.

Left some minor comments. Rest of it looks good.


Upgrade instructions for 2.5 need to mention removing alerts/notifiers

What kind of request is this (question/bug/enhancement/feature request):
Documentation request.
Steps to reproduce (least amount of steps as possible):
Upgrade from Rancher 2.4 to 2.5 on a system that has alerts and notifiers configured.
Result:
You can't successfully disable monitoring, because the alerts and notifiers are configured, which causes Rancher to keep recreating the monitoring daemons even though monitoring is actually shown as disabled in the UI.
The upshot is that you can't then successfully enable the new monitoring system via the app in Cluster Explorer.
Other details that may be helpful:
Deleting all the alerts and notifiers (including project alerts and cluster alerts) resolves the problem. This should be mentioned in the documentation.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.5.1
Installation option (single install/HA): HA

@al45tair thanks for calling this out. We have added the documentation here https://github.com/rancher/docs/pull/2813, which shows up in https://rancher.com/docs/rancher/v2.x/en/monitoring-alerting/v2.5/migrating/ to address this, so I'll close out this ticket.
On the same note, for any users who are looking for a way to check why Monitoring V1 doesn't appear to be disabled, disabling Monitoring V1 involves the following steps:

Either 1) remove all Notifiers from the Notifier tab of the Cluster or 2) Navigate to each Alert tab (for the whole cluster and for each individual project) and remove any recipients under any of the Alert Groups that you have defined.
On each project that has Project Monitoring enabled, disable it under the Monitoring tab of the Project
Disable Cluster Monitoring by navigating to the Monitoring tab of the Cluster

The script at https://github.com/bashofmann/rancher-monitoring-v1-to-v2/pull/3 may help you audit why Monitoring V1 doesn't appear to be disabled.


CLI-Created Web Projects All have the Same Project ID For User Secrets

It seems that all projects - even on different machines - are using this same GUID when created from the CLI: 0799fe3e-6eaf-4c5f-b40e-7c6bfd5dfa9a, resulting in a shared set of user secrets. The userSecretsId for all project.json files created is aspnet-WebApplication-0799fe3e-6eaf-4c5f-b40e-7c6bfd5dfa9a.
These projects are created with dotnet new -t web.

@MisterJames there is already an issue in the CLI repo tracking this in dotnet/cli#3617. Will close this one as a duplicate.


RHEL 7.5: Needs JDK 1.8+ instead of minimum JDK 1.6 version for TFVC

The documentation states that:
"If you'll be using TFVC, you will also need the Oracle Java JDK 1.6 or higher. (The Oracle JRE and OpenJDK are not sufficient for this purpose.)"
On Red Hat Enterprise Linux version 7.5 with on-prem agent, JDK 1.7 throws exit code 100 when trying to query workspaces, with JWT authorization failing.
##[error]Exit code 100 returned from process: file name 'tf', arguments 'workspaces -format:xml "-collection:https://xxxx/xxx/" -jwt:*** -noprompt'.
Updating to JDK 1.8 solves the issue.

@RSTZZZ -- Thanks for your feedback; we appreciate it. To make sure we have all the information needed to process your issue, please let us know which topic you’re referencing.

@WilliamAntonRohm -- I'm referencing this documentation: https://docs.microsoft.com/en-ca/azure/devops/pipelines/agents/v2-linux?view=azure-devops#check-prerequisites

@RSTZZZ -- thank you for clarifying.
@steved0x -- please look into this issue.