Support for id's for homebridge-nest

Hi
You have created support Nest token and id's for for homebridge-nest-cam which is great. However, I am using homebridge-nest, which needs similar tokens. Especially, the Cookie token needs to refreshed at regular intervals.
It would nice if this already existing functionality in configu-ui-x could also support that one.
Thanks.
Ejvind

All the code to make this happen lives in the homebridge-nest-cam repo; homebridge-nest would need to add the same or similar code to enable this.

Code ref: https://github.com/Brandawg93/homebridge-nest-cam/blob/master/src/uix.ts


Assert error in example

Example https://github.com/xsuite/xtrack/blob/main/examples/full_ring/006_timing.py
gives AssertionError on ContextCupy for some of the example cases.

In fact there is no difference between CPU and GPU, previously the test was done on different particles.
Needed to increase the threshold on the check by a factor of 4. Maybe explainable by different Faddeeva implementation in xtrack and ducktrack. To be watched...


Copyedit: Remove old screenshots and deprecated links

Summary of the changes / Why this is an improvement

Remove old screenshots still on server
Get rid of deprecated HTML links

Checklist

[ ] CLA is signed

NB @dbgj @RomanMeingassner: Hitherto I usually referred docs content to the PO (Luke). Since he is leaving, I am referring them to you. If you want, feel free to choose between you who wants to do it or refer me to someone else!


Bump test terraform to tf 1.0

This bumps the test terraform bin to 1.0. I also went ahead and bumped the internal pulled in terraform version to 0.15.3. Note that that specific version is unique, as it is the last version that exposes a lot of the internal helper functions. After that version, terraform hides all the internal helpers to internal package, which has special meaning in go: it can not be imported outside the project using it. So they are not accessible.
Longer term, we will need to figure out an alternative strategy for pulling in terraform helpers, but for now I think this would suffice.

Thanks for review. Will merge this in now!


Add Hoppity Collection data

Adds a mapping between rabbit names and rarities for https://github.com/hannibal002/SkyHanni/pull/1836.
Also adds currently-unused data for milestone rabbits and the CPS/multiplier bonuses for rabbits, which might be useful for later HoppityCollectionStats refactoring.

there is already https://github.com/NotEnoughUpdates/NotEnoughUpdates-REPO/blob/master/constants/hoppity.json which doesnt have all the data in here but i think it would be better to add that missing data to neu repo rather than have it duplicated so that there is only one place to update, also gravy's suggestion

Thanks for pointing me to that and for the jsonobject! Closing this as redundant.


Launch File Errors

Hi Thanks for your sharing! This is a good work.
I am now trying run ct_icp on my own dataset using Ubuntu1804/ROS/Melodic, However, when I roslaunch ct_icp_on_rosbag.launch, I got warning that Unknown <arg> attribute "required" and Unknown <include> attribute "args", it seems that these two tabs have no such attributes?
I wonder have you try this launch file on ros melodic? How can I fix it? Thanks!

Hi !
So despite these warnings can you run it on your dataset or does it fail ?
The warning should not be an issue (I have the same),
Don't forget that you need to specify the following parameters:

rosbag
topic points to the point cloud topic.

If you have failures, can you print the console log with the relevant error messages ?

Yes. The program run well with warning, thanks for reply!
Also, I have modified the launch to eliminate the warning.


fix: add strip-ansi

@W-8856585@ nuts for plugin-org needs to have responses stripped of ansi chars

This might have to do with my default shell on Mac (zsh), but w/o this change json parsing fails.


zenpower: 0.1.10 -> 0.1.12

Motivation for this change
Compatibility with kernel 5.7.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/) (compiled for 5.2/5.4/5.6/latest(5.7) kernels, tested on 5.6, 5.7; verified module loads without error and provides information)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Updated the commit message to prefix the attribute name by linuxPackages.


everyone who worked on this is missing hero badges...

This is literally the IDEAL stack for fast apps with extensibility, great looks, and the separation of api's is such a smart move.
i literallly have spent the past month looking for how to build this exact stack (well, i got about 70% of the way there with my wish list,this release far surpasses it).
add this to sandbox sections of code the way google sandboxes tabs, or bitwig sandboxes audio plugins....:
https://github.com/Trimma/react-redux-isolate
and add these semi-official 3rd party themes for semantic-UI.. (they all look great)
https://github.com/semantic-ui-forest/forest-themes
and is this possible to have sandboxed applets/widgets each requiring their own auth from an outside microsource?   ie: pretend i wanted to load facebook feed next to a twitter feed for users of my app, can i have them individuallly call directly out to get their auth tokens and use the middleware to store their information in a secure database so they can just single-sign-on to the app and the app will sign them into all their services  at once, while react is already rendering the framework pulling the ui elements and rendering them  while the clientside app is waiting for the api data to arrive?through feathers?
i want to load up all my modules and component pieces and objects into a rmongo database with memcached caching,  and store all the user profile information on mysql8 with redis caching,, where feathers contacts the outside world via KrakenD api gateway for auth and live data, and it splits off the auth to the the middle ware, but once auth is passed, it's all sockets passing the api data as fsat as possible to the app user..
who here is the resident expert on this stack? can they e-mail me some answers?

I keep running into this. and nothing i do seems to make the site work on my ipad or iphone in the latest chrome other than the home page, without any css, and can't nav to other pages.
i've got the rest of everything pretty great going, redid both the chat pages so they look nice, and load top down instead of adding messages to the bottom. eslinted it to death until i got vscode set up right so it formats correctly.  but.. there's a problem that traces back to  this code in server.js:

const modules = [];
    const component = (
      <Loadable.Capture report={moduleName => modules.push(moduleName)}>
        <Provider store={store} {...providers}>
          <ConnectedRouter history={history}>
            <ReduxAsyncConnect routes={routes} store={store} helpers={providers}>
              {renderRoutes(routes)}
            </ReduxAsyncConnect>
          </ConnectedRouter>
        </Provider>
      </Loadable.Capture>
    );

which leaves me with this error in terminal after a perfect compile, i hit refresh or simply open the page on my ipad or phone, and this comes up, and a not-quite fully rendered homepage.
[0] i ｢wdm｣: Compiled successfully.
[2] POST /authentication 201 2.123 ms - 398
[2] GET /loadInfo 200 0.289 ms - 64
[1] Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
[1]
[1] Check your code at App.js:122.
[1]     in App
[1]     in Route
[1]     in withRouter(App)
[1]     in Connect(withRouter(App))
[1]     in Route
[1]     in Switch
[1]     in Route (at ReduxAsyncConnect.js:69)
[1]     in ReduxAsyncConnect
[1]     in Route
[1]     in withRouter(ReduxAsyncConnect) (at server.js:138)
[1]     in Router
[1]     in ConnectedRouter (at server.js:137)
[1]     in Provider
[1]     in withContext(Provider) (at server.js:136)
[1]     in Capture (at server.js:135)
[1] MOUNT ERROR:   Error: Invariant Violation: Element type is invalid: expected a string (for bu  ilt-in components) or a class/function (for composite components) but got: und  efined. You likely forgot to export your component from the file it's defined   in, or you might have mixed up default and named imports.


MINOR: Add Makefile for std layout patch changes

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

thanks for the review. Added a comment.


Add syncBulkActions config to avoid the large amount of metrics data written ES in a single sync bulk request.

Please answer these questions before submitting a pull request

Why submit this pull request?

[ ] Bug fix

[ ] New feature provided

[x] Improve performance

Related issues

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.
Add syncBulkActions config to avoid the large amount of metrics data written ES in a single bulk request.

Follow #5697 to update two change log files.

If you plan to merge this for now.


Nested Includes, how to query?

This was apparently done in 3.x, yet I haven't found an example of it in the Wiki or any of the issues.
public class Book
{
    [BsonId] public string Id { get; set; }
    public List<Author> Authors { get; set; }
}

public class Author
{
    public string Role { get; set; }
    [BsonRef("users")] public User User { get; set; }
}

public class User
{
    [BsonId] public string Id { get; set; }
    public string Name { get; set; }
}

I want to query books and get the full User object. How is this possible? I've tried:

books.Include(x => x.Authors[0].User).FindById(id);
books.Include("Authors.User").FindById(id);

Both return only the user's Id (i.e. no inclusion). Any hints or suggestions would be appreciated.

Hi @freezy, there is no nested includes for List. In this case it´s better use Include(Action<T>), so you can define your function, likes:
books.Include(x => x.Authors.ForEach(z => z.User = users.FindById(z.User.UserId))

Thanks for the quick response! Would this be a possible feature in the future?

I tried to this but was not easy to be done because. In this case, need be deserialized many subdocuments per document and it´s not easy to detect this. Thats why I added this Include using an Action.

Alright, thanks for the info!

Could anyone solve this?


[Function] mbedtls_mpi_exp_mod ,sometimes the result  is wrong (Compared with the results of python's)

Summary
The result of exponentiation is wrong,sometimes.  (Compared with the results of python)
System information
(1)branch：origin/mbedtls-2.16
commit：ccfc2bff6fbcf3c3650f4cf8af020c3015663039
(2)branch：origin/development
commit：023aa11760186e32eb79f4465395676eaac703cc
Expected behavior
[example]
A                         E                                                                                N        mbedtls'        python's
(1)    -0xE6E30347     0x05                                                                                0x09       0x09               0
(2)    -0xB20295DF     0x89530fb4d2e6b2d5c74d29ffa6796a17892262a0acc89bb257bd51     0x09        0x09               0
[mbedtls script]
const char *strA[2]={"-E6E30347","-B20295DF"};
const char *strE[2]={"05","89530FB4D2E6B2D5C74D29FFA6796A17892262A0ACC89BB257BD51"};
const char *strN[2]={"09","09"};
for(int i=0;i<2;i++)
{
TEST_EQ(mbedtls_mpi_read_string(&A,16,strA[i]),0,ret);
TEST_EQ(mbedtls_mpi_read_string(&E,16,strE[i]),0,ret);
TEST_EQ(mbedtls_mpi_read_string(&N,16,strN[i]),0,ret);
TEST_EQ(mbedtls_mpi_exp_mod(&X,&A,&E,&N,&_RR),0,ret);
}
[python script]
def exp_pow():
a=[-0xE6E30347,-0xB20295DF]
e=[0x05,0x89530fb4d2e6b2d5c74d29ffa6796a17892262a0acc89bb257bd51]
n=[0x09,0x09]
for i in range(2):
x=pow(a[i],e[i],n[i])
print("0x%x"%x)

Well, the result isn't wrong: 9 == 0 mod 9. The documentation of mbedtls_mpi_exp_mod doesn't promise that the result is any particular representative mod N, although in most cases the result is in the range [0, N-1].
What's happening is that mbedtls_mpi_exp_mod first calculates |a|^e, then at the end it changes the result to (n - x) if it needs to be negated. This yields n when x = 0, but it would be nicer to yield 0.
In general, the bignum library in Mbed TLS is intended for cryptography, which doesn't use negative numbers much. Some of the ECC code in Mbed TLS does use negative intermediate values however, and regardless of that we do want the bignum library to be correct. We don't necessarily care about the bignum library being nice or efficient outside of crypto use cases.


How to forbid print to output the logs to console in release scheme?

e.g.:
print("my app");
By testing, I find it that outputs the logs to console in release scheme, how to forbid print to output the logs to console in release scheme?

You can use the Zone API to redefine print() and use a different entry point like flutter build -t lib/main_release.dart to have a release build where that takes effect.

@dyftxpro I would recommend not leaving print statements in your code. If you need generic logging support and want to disable it for production, you could use something like https://github.com/dart-lang/logging and then disable the root logger for production

This works too:
void log(Object o) {
  assert(() {
    print(o);
    return true;
  }());
}

Does not work for my iOS release App

Does not work for my iOS release App

Asserts are supposed to work only in debug mode.

Keep in mind that even if you avoid calling print, some libraries can call print and you can't block them from doing it, so I think the flutter compilation tools should have the option to block print in release mode if the developer wants to.

This works too:
void log(Object o) {
  assert(() {
    print(o);
    return true;
  }());
}

thank you. this is working for android app release build


fix: floating stack over nav-bar

Fixed #588
Describe your changes here.
Adding a z-index property to avoid it from floating over the navbar

If development process was changed
Description of changes

[ ] Updated README

Merge checklist

[ ] Changed base branch to release branch
[ ] Add or update TypeScript definitions (index.d.ts) if necessary
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge

Hey @taleymirza great catch and thank you for the PR! In this case, we don't necessarily want to create a new stacking context on the wrapper component here since we can't know how users will want to manage z-index in their own applications - I would rather apply a z-index 0 to the wrapper in the live editor which is over in https://github.com/primer/doctocat

Hey @taleymirza great catch and thank you for the PR! In this case, we don't necessarily want to create a new stacking context on the wrapper component here - I would rather apply a z-index 0 to the wrapper in the live editor which is over in https://github.com/primer/doctocat

Created an issue in Doctocat so closing this! https://github.com/primer/doctocat/issues/96


test_comparison failed due to different exception messages

Found in https://github.com/modin-project/modin/pull/6954

HDK engine is deprecated and will be removed in a future version.


[BUG] Longhorn accidentally schedule all replicas onto a worker node eventhough the setting Replica Node Level Soft Anti-Affinity is currently disabled

Describe the bug
After a reboot a the worker node in a cluster that has 1 control node + 1 worker node, Longhorn accidentally schedules all replicas onto a worker node even though the setting Replica Node Level Soft Anti-Affinity is currently disabled
To Reproduce
Steps to reproduce the behavior:

Create a cluster of 1 control node and 1 worker node.
Deploy Longhorn 1.3.1. Keep every Longhorn settings has default
Deploy a test deployment that use pvc provisioned by Longhorn
Observe that there is currently only 1 replica of the volume is scheduled on the worker node. The other 2 replicas are unschedule
Restart the worker node
Observe that all replica is scheduled onto the worker node.

Expected behavior
The expectation is Longhorn doesn’t accidentally schedule all replicas onto the worker node as the setting Replica Node Level Soft Anti-Affinity is currently disabled
Log or Support bundle
longhorn-support-bundle_a84c2476-8a0f-4b1e-bdc2-10aae414f3c5_2022-09-12T22-08-15Z.zip
Environment

Longhorn version: 1.3.1

@ w13915984028 is mentioning that this problem doesn't happen in Longhorn 1.3.0
However, I have not had time to test 1.3.0 yet.

@longhorn/qa this seems a regression, so please help check if this can be reproduced in 1.3.0 as well.

@chriscchien Can you please help check this on 1.3.0?

FYI: It's reproducable in my ENV with LH v1.3.1;  in v1.3.0, I did not encounter this issue, but I also did not spend time to try to reproduce in v1.3.0.
Wait for QA's update about v1.3.0 . thanks.
also cc @guangbochen @bk201

I can reproduce in v1.3.1 but not in v1.3.0,
In v1.3.0, after reboot the only worker node ( which is worker 2 on my environment), only 1 replica will on worker node as below

cc @khushboo-rancher

@longhorn/qa
I could reproduce this at v1.3.0 as the picture below

https://github.com/longhorn/longhorn-manager/blob/master/scheduler/replica_scheduler.go#L172-L182
Rebooting only one work node in the cluster would make all replicas failed.
And usedNodes will be always empty therefore this work node will be schuedlable.

Thank @mantissahz ,
After retest this case on v1.3.0, I found I can reproduce error in my local environment, still need time to figure out why last time I can not reproduce.
Double checked on v1.2.5 and can be reproduced but not every time :

I tried to reproduce in my ENV,  it happened right after system was rebooted:
an interesting log:
time="2022-09-27T13:11:31Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"harv2\", UID:\"570107d7-d044-4179-abb7-cebea913eb9c\", APIVersion:\"longhorn.io/v1beta2\", ResourceVersion:\"15691\", FieldPath:\"\"}): type: 'Normal' reason: 'Ready' Node harv2 is ready"

time="2022-09-27T13:11:31Z" level=debug msg="Schedule replica to node harv2" dataDirectoryName=pvc-964246c3-c41a-4a16-a613-fb76a2e55d37-3b2e3db6 disk=65518063-0357-4430-802b-f2b78945fac2 diskPath=/var/lib/harvester/defaultdisk replica=pvc-964246c3-c41a-4a16-a613-fb76a2e55d37-r-1daf780a
time="2022-09-27T13:11:31Z" level=debug msg="Schedule replica to node harv2" dataDirectoryName=pvc-964246c3-c41a-4a16-a613-fb76a2e55d37-638bea8e disk=65518063-0357-4430-802b-f2b78945fac2 diskPath=/var/lib/harvester/defaultdisk replica=pvc-964246c3-c41a-4a16-a613-fb76a2e55d37-r-28b9d056
time="2022-09-27T13:11:31Z" level=debug msg="Schedule replica to node harv2" dataDirectoryName=pvc-866003f2-df97-4ecb-8ba7-adf0bf4df22a-1c8440ce disk=65518063-0357-4430-802b-f2b78945fac2 diskPath=/var/lib/harvester/defaultdisk replica=pvc-866003f2-df97-4ecb-8ba7-adf0bf4df22a-r-204aeae8
time="2022-09-27T13:11:31Z" level=debug msg="Schedule replica to node harv2" dataDirectoryName=pvc-866003f2-df97-4ecb-8ba7-adf0bf4df22a-6e4f11cb disk=65518063-0357-4430-802b-f2b78945fac2 diskPath=/var/lib/harvester/defaultdisk replica=pvc-866003f2-df97-4ecb-8ba7-adf0bf4df22a-r-8f270ccf
time="2022-09-27T13:11:31Z" level=debug msg="Schedule replica to node harv2" dataDirectoryName=pvc-5158098c-9918-4992-b119-9064ead183c1-f6552402 disk=65518063-0357-4430-802b-f2b78945fac2 diskPath=/var/lib/harvester/defaultdisk replica=pvc-5158098c-9918-4992-b119-9064ead183c1-r-8bb6dbb4
time="2022-09-27T13:11:31Z" level=debug msg="Schedule replica to node harv2" dataDirectoryName=pvc-5158098c-9918-4992-b119-9064ead183c1-bf830066 disk=65518063-0357-4430-802b-f2b78945fac2 diskPath=/var/lib/harvester/defaultdisk replica=pvc-5158098c-9918-4992-b119-9064ead183c1-r-5c6763da

And, at this moment, all replicas were scheduled in the only running NODE, same DISK:
harv2:~ # kk get replica -A
NAMESPACE         NAME                                                  STATE     NODE    DISK                                   INSTANCEMANAGER               IMAGE                               AGE
longhorn-system   pvc-5158098c-9918-4992-b119-9064ead183c1-r-5c6763da   stopped   harv2   65518063-0357-4430-802b-f2b78945fac2                                                                     14m
longhorn-system   pvc-5158098c-9918-4992-b119-9064ead183c1-r-8bb6dbb4   stopped   harv2   65518063-0357-4430-802b-f2b78945fac2                                                                     14m
longhorn-system   pvc-5158098c-9918-4992-b119-9064ead183c1-r-b35b74c2   running   harv2   65518063-0357-4430-802b-f2b78945fac2   instance-manager-r-8795b562   longhornio/longhorn-engine:v1.3.1   14m
longhorn-system   pvc-866003f2-df97-4ecb-8ba7-adf0bf4df22a-r-204aeae8   stopped   harv2   65518063-0357-4430-802b-f2b78945fac2                                                                     14m
longhorn-system   pvc-866003f2-df97-4ecb-8ba7-adf0bf4df22a-r-361cdfaf   running   harv2   65518063-0357-4430-802b-f2b78945fac2   instance-manager-r-8795b562   longhornio/longhorn-engine:v1.3.1   14m
longhorn-system   pvc-866003f2-df97-4ecb-8ba7-adf0bf4df22a-r-8f270ccf   stopped   harv2   65518063-0357-4430-802b-f2b78945fac2                                                                     14m
longhorn-system   pvc-964246c3-c41a-4a16-a613-fb76a2e55d37-r-1daf780a   stopped   harv2   65518063-0357-4430-802b-f2b78945fac2                                                                     14m
longhorn-system   pvc-964246c3-c41a-4a16-a613-fb76a2e55d37-r-2557d80b   running   harv2   65518063-0357-4430-802b-f2b78945fac2   instance-manager-r-8795b562   longhornio/longhorn-engine:v1.3.1   14m
longhorn-system   pvc-964246c3-c41a-4a16-a613-fb76a2e55d37-r-28b9d056   stopped   harv2   65518063-0357-4430-802b-f2b78945fac2                                                                     14m

The bug looks to be related to ReconcileVolumeState, which iterate all rs, but unfortunately, when 1st replica is set to some NODE, the 2rd replica may still select this NODE.  Because 1st selection does NOT update the occupied quota/label to the related NODE.
@innobead @joshimoo @PhanLe1010 @mantissahz
func (vc *VolumeController) ReconcileVolumeState(v *longhorn.Volume, es map[string]*longhorn.Engine, rs map[string]*longhorn.Replica) (err error) {
	for _, r := range rs {
...
		scheduledReplica, multiError, err := vc.scheduler.ScheduleReplica(r, rs, v)
		if err != nil {
			return err
		}
...
		} else {
			rs[r.Name] = scheduledReplica
		}
	}

// ScheduleReplica will return (nil, nil) for unschedulable replica
func (rcs *ReplicaScheduler) ScheduleReplica(replica *longhorn.Replica, replicas map[string]*longhorn.Replica, volume *longhorn.Volume) (*longhorn.Replica, util.MultiError, error) {

	// get all hosts
	nodesInfo, err := rcs.getNodeInfo()
..

	nodeCandidates, multiError := rcs.getNodeCandidates(nodesInfo, replica)
	if len(nodeCandidates) == 0 {
..
	}

	diskCandidates, multiError := rcs.getDiskCandidates(nodeCandidates, nodeDisksMap, replicas, volume, true)

	// schedule replica to disk
	rcs.scheduleReplicaToDisk(replica, diskCandidates)

Suspect the BUG also has relationship with DISK size.
I used to test features in single-node Harvester, with LH default storageclass (3 replicas). This code logic seems to be there for a long time, but not all the time it is hitted.  This Harvester NODE is a KVM VM with 200Gb disk.  Harvester itself will occupy some spaces.
In the past, Harvester has only one build-in PVC before, prometheus 50Gb. The bug did not happen.

Now, there are 3 build-in PVCs, 50Gb, 5Gb, 2Gb. The bug comes.

When 3 replicas are scheduled into ONE node, ONE disk, but as long as the disk space is enough, LH can recover and remove those additional replicas silently.
But if all those replicas are over the space of disk, all replicas become STOPPED, and can not start anymore.
Please LH expert help confirm, thanks.

I think this issue will also happen at v1.2.5
Volume controller marks unused replicas failed after volume was detached to prevent the replica rebuilding. And it starts to schedule the failed/unused replica to the same node because all replicas are failed.

Verified passed on master-head (longhorn-manager 15f850c) by following the test steps.
In master-head, after instance reboot, the volume still only has 1 healthy replica + 2 unscheduled (N/A) replicas.
But in v1.3.0, after instance reboot, the volume would have 3 replicas scheduled to the same single node, 1 with healthy state, and 2 with failed state.


Not working in IE 11,throws syntax error

please expose source file,so that i can hook it up to my build pipeline .
eg:- expose src directory in package.json file

it stopped throwing syntax error once i imported preload-it/dist/preload-it.esm and added transpilation but its throws another error now which is xhr.onload = event => {
const type = event.target.response.type;
const responseURL = event.target.responseURL;
	item.fileName = responseURL.substring(responseURL.lastIndexOf('/') + 1); ===> substring of undefined(responseurl not there in event.target i guess).Thanks for this amazing library but please help me in resolving this issue

I would like the distributed files to be transpiled down to es5-compatible as well.


When core restart, the skill returns an error

When running skill as standalone, with  the core is restarted then a trace is generated inside the skill log.
2023-04-29 21:59:38.985 - OVOS - ovos_workshop.skill_launcher:_execute_instance_shutdown:334 - INFO - Skill ovos-skill-personal.OpenVoiceOS shut down successfully
exception calling callback for <Future at 0x7f9ac4b190 state=finished raised TypeError>
Traceback (most recent call last):
  File "/usr/lib/python3.11/concurrent/futures/_base.py", line 340, in _invoke_callbacks
    callback(self)
  File "/usr/lib/python3.11/site-packages/pyee/_executor.py", line 57, in _callback
    self.emit("error", exc)
  File "/usr/lib/python3.11/site-packages/pyee/_base.py", line 118, in emit
    self._emit_handle_potential_error(event, args[0] if args else None)
  File "/usr/lib/python3.11/site-packages/pyee/_base.py", line 88, in _emit_handle_potential_error
    raise error
  File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/ovos_workshop/skill_launcher.py", line 514, in load_skill
    self.skill_loader.reload()
  File "/usr/lib/python3.11/site-packages/ovos_workshop/skill_launcher.py", line 298, in reload
    return self._load()
           ^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/ovos_workshop/skill_launcher.py", line 359, in _load
    self.skill_module = self._load_skill_source()
                        ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/ovos_workshop/skill_launcher.py", line 390, in _load_skill_source
    main_file_path = os.path.join(self.skill_directory, SKILL_MAIN_MODULE)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen posixpath>", line 76, in join
TypeError: expected str, bytes or os.PathLike object, not NoneType

Fixed by https://github.com/OpenVoiceOS/OVOS-workshop/commit/498e3730fb82a33a93bc1ea4ea1d905794f89420


[WIP] Thread safety implementation using locking

Prototype for a solution to https://github.com/nodegit/nodegit/issues/827

I'm at a stopping point with this implementation.  The main part is the LockMaster class which holds locks related to parameters being passed to libgit2.  Currently, when we pass a repository object, we lock the repository.  When we pass an index, we lock the repository that owns the index (or the index, if there is no owner).  When we pass a commit, we lock the repository that owns the commit.  Support for more types can be easily added.
The objects are locked when the LockMaster is instantiated, and unlocked when it's destroyed.  Another class, LockMaster::TemporaryUnlock, is used to temporarily unlock these objects when the native layer in an async thread needs to process a callback in the javascript layer (otherwise a call to a sync method that needs to lock one of the locked objects would deadlock the system).
The current implementation uses a few c++11 features, like variadic templates, range-based loops and auto.  All of these can be replaced with non-c++11 code, if needed, but I think the library should still build on the compilers we are targeting.
The thread safety system can be disabled / enabled, and it is currently disabled by default.
It would be great to get some feedback on the implementation, also trying to build on different systems would be helpful.

This does compile on gcc 4.6 and clang 3.4

Wow, this is amazing!

The thread safety system can be disabled / enabled, and it is currently disabled by default.

I'd tentatively argue is should be safe (enabled) by default.

My C++ is pretty rusty, but I didn't see any obvious problems :+1:

@joshaber thanks for taking a look! I think you are right about having thread safety enabled by default, but maybe we could ease into it (have it disabled by default for a release or few, then turn it on).  My main concern is that turning it on makes it possible to lock the main node thread, so existing code using NodeGit can be adversely affected (and if it wasn't running into thread-safety issues, it would be adversely affected with no benefit... though scenarios in which the main thread would get locked are likely the scenarios in which thread safety is an issue, so maybe my concern is unwarranted).
It would be nice if in the long term, we find a way to avoid the risk of locking the main thread. That would mean that sync functions would never lock - and we've already discussed a few ways of achieving that (make sure that sync calls read data in a thread safe way, make everything else async, etc.), so maybe it wouldn't be too hard to get to that point.

Do we want to have tests running for both thread safety enabled and disabled?  Currently they run with the default (disabled) except for index tests, where they are explicitly turned on to test a deadlock scenario.
If we want both, what would be a good way to implement that?

I think you are right about having thread safety enabled by default, but maybe we could ease into it (have it disabled by default for a release or few, then turn it on).

Yeah, that's a fair concern too. I'm not sure how to best communicate this change. /cc @nodegit/owners

If we want both, what would be a good way to implement that?

Perhaps an environment variable, so that it can be part of the build matrix?

eh, not a bit fan of the both option, as then there are 2 modules to install. I'd say get through like 0.8.x with it disabled by default, and then a bump to 0.9.x with it enabled by default

I'd say enable it to default when we go to 1.0

Yeah thats a good idea, that way anybody has to explicitly upgrade to it in a project if htey've got stupid ^ deps in their package.json

I agree with switching on by default in 1.0, even though thread safety is more of a guideline than a rule /s

Just looked over this PR and honestly I think it's ready. Since it defaults to off I feel like this is a moderately safe PR to pull in and we'll be flipping thread safety on in GitKraken so we'll be doing some real-life testing and we'll iron out bugs as we go. I'm removing the [WIP] from this and if nobody speaks up I'll merge this in in about an hour.

@joshaber the environment variable idea sounds great to me.  @maxkorp I don't think this would require two versions of the module (though you might be thinking back to when I was proposing to add a switch to build NodeGit with/without the thread support).
The way I am interpreting this is we would have an environment variable, maybe NODEGIT_TEST_THREADSAFETY, and if it's set the tests would (at run-time) turn on thread safety.  By default, they would test with thread safety off.
I'd like to add this anyway, if nothing else to make it easier to test the thread safety code locally.  I'll open up a separate PR when I get a chance.


Doesn't start on Kubuntu 22.04.1 LTS

Got the following issue:
./synth.AppImage
Traceback (most recent call last):
  File "/tmp/.mount_synth.1YZ22t/usr/bin/synth", line 8, in <module>
    from PIL import Image, ImageTk
ImportError: cannot import name 'ImageTk' from 'PIL' (/usr/lib/python3/dist-packages/PIL/__init__.py)

Kubuntu 22.04.1 LTS
x86_64
Run many other appimages with no issues

Try this:
sudo apt-get install python3-pil python3-pil.imagetk

Close since it seems that was solved


Fix points thumbnail

Description
This PR fixes the bug where points layer thumbnails with more points than Points._max_points_thumbnail caused a crash (flagged by @cudmore in #932).
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

References
This fixes #932 .
How has this been tested?

[x] added tests for more points than the limit
[x] all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works

Thanks, @jni ! I made your suggested change. I will let the tests pass and merge later tonight.


README: Add community, license, contribution, badges.

This brings over elements from the Vello README.md.

Updates pushed, also fixed link to the LICENSE file (since it isn't LICENSE-APACHE).


Update condition in @ConditionalOnProperty, add some comments.

Update condition in @ConditionalOnProperty
add some comments.

/azp run java - spring - ci

/check-enforcer override


Request: add dogovori.info to the filter

Evidence: https://dogovori.info/questions/45671200/safari-not-requesting-srcset-images-on-resize
Original: https://stackoverflow.com/questions/45671200/safari-not-requesting-srcset-images-on-resize

Thanks!

Thanks!


Windows failing to run

Reported that it does not work properly on windows. Pushed 631d596d48ea729b8d7dafd257cfcb1b68e35d1f to avoid using linux specific mappings. Will test and debug to get it working properly on windows this weekend.
Thank you @Freakman on discord for testing this!

Current branch is giving this error on windows:
zig build-exe llama2 ReleaseSafe native: error: the following command failed with 1 compilation errors:
C:\Users\user\zig\.bin\master\zig.exe build-exe C:\Users\user\Documents\GitHub\llama2.zig\src\main.zig -fstrip -OReleaseSafe --cache-dir C:\Users\user\Documents\GitHub\llama2.zig\zig-cache --global-cache-dir C:\Users\user\AppData\Local\zig --name llama2 --listen=-
Build Summary: 0/3 steps succeeded; 1 failed (disable with --summary none)
install transitive failure
+- install llama2 transitive failure
   +- zig build-exe llama2 ReleaseSafe native 1 errors
C:\Users\user\zig\.bin\master\lib\std\os.zig:102:23: error: root struct of file 'c' has no member named 'MAP'
pub const MAP = system.MAP;
                ~~~~~~^~~~
referenced by:
    main: src\main.zig:619:102
    callMain: C:\Users\user\zig\.bin\master\lib\std\start.zig:614:32
    remaining reference traces hidden; use '-freference-trace' to see all reference traces

Honestly feels like a zig problem at this point 😅

c:\zig\zig build -Doptimize=ReleaseFast
zig build-exe llama2 ReleaseFast native: error: the following command failed with 1 compilation errors:
c:\zig\zig.exe build-exe C:!DEV!si\qlora\llama2.zig\src\main.zig -fstrip -OReleaseFast --cache-dir C:!DEV\eh\qlora\llama2.zig\zig-cache --global-cache-dir C:\Users\eh\AppData\Local\zig --name llama2 --listen=-
Build Summary: 0/3 steps succeeded; 1 failed (disable with --summary none)
install transitive failure
└─ install llama2 transitive failure
└─ zig build-exe llama2 ReleaseFast native 1 errors
c:\zig\lib\std\os.zig:99:23: error: root struct of file 'c' has no member named 'MAP'
pub const MAP = system.MAP;
~~~~^~
referenced by:
main: src\main.zig:844:102
callMain: c:\zig\lib\std\start.zig:574:32
remaining reference traces hidden; use '-freference-trace' to see all reference traces

Ok I believe it should work now! I have tested on linux with wine and everything seems fine.
llama2.zig replace-mmap*
 ❯ zig build-exe src/main.zig -O ReleaseFast -target x86_64-windows

llama2.zig replace-mmap* 3s
 ❯ wine main.exe stories15M.bin -t 0 -v
config: main.Config{ .dim = 288, .hidden_dim = 768, .n_layers = 6, .n_heads = 6, .n_kv_heads = 6, .
vocab_size = 32000, .seq_len = 256 }
shared weights: true
temperature: 0
top-p: 1
SIMD vector size: 4

Once upon a time, there was a little girl named Lily. She loved to play outside in the sunshine. On
e day, she saw a big, red ball in the sky. It was the sun! She thought it was so pretty.
Lily wanted to play with the ball, but it was too high up in the sky. She tried to jump and reach i
t, but she couldn't. Then, she had an idea. She would use a stick to knock the ball down.
Lily found a stick and tried to hit the ball. But the stick was too short. She tried again and agai
n, but she couldn't reach it. She felt sad.
Suddenly, a kind man came by and saw Lily. He asked her what was wrong. Lily told him about the bal
l. The man smiled and said, "I have a useful idea!" He took out a long stick and used it to knock t
he ball down. Lily was so happy! She thanked the man and they played together in the sunshine.

404 tokens per second

main.exe stories15M.bin -t 0 -v
config: main.Config{ .dim = 288, .hidden_dim = 768, .n_layers = 6, .n_heads = 6, .n_kv_heads = 6, .vocab_size = 32000, .seq_len = 256 }
shared weights: true
temperature: 0
top-p: 1
SIMD vector size: 4

Once upon a time, there was a little girl named Lily. She loved to play outside in the sunshine. One day, she saw a big, red ball in the sky. It was the sun! She thought it was so pretty.
Lily wanted to play with the ball, but it was too high up in the sky. She tried to jump and reach it, but she couldn't. Then, she had an idea. She would use a stick to knock the ball down.
Lily found a stick and tried to hit the ball. But the stick was too short. She tried again and again, but she couldn't reach it. She felt sad.
Suddenly, a kind man came by and saw Lily. He asked her what was wrong. Lily told him about the ball. The man smiled and said, "I have a useful idea!" He took out a long stick and used it to knock the ball down. Lily was so happy! She thanked the man and they played together in the sunshine.

34 tokens per second

If you are natively on windows, I would recommend using the build command in the read me, which will strip the binaries and ensure you are compiling with release fast

yeah. Ive done both. Fwiw.
Ill do the other one now. I did this one for completness. FWIW. the difference is in the noise at 15M

If you are natively on windows, I would recommend using the build command in the read me, which will strip the binaries and ensure you are compiling with release fast

c:\zig\zig build -Doptimize=ReleaseFast
PS llama2.zig> main.exe ../out/model15M.bin -t 0 -v -s 42 -p 1.0  -i "Versa ran"
config: main.Config{ .dim = 288, .hidden_dim = 768, .n_layers = 6, .n_heads = 6, .n_kv_heads = 6, .vocab_size = 32000, .seq_len = 256 }
shared weights: true
temperature: 0
top-p: 1
SIMD vector size: 4
Versa ran to the park. blah
63 tokens per second
c:\zig\zig build-exe src/main.zig -O ReleaseFast -target x86_64-windows
PS llama2.zig> main.exe ../out/model15M.bin -t 0 -v -s 42 -p 1.0  -i "Versa ran"
config: main.Config{ .dim = 288, .hidden_dim = 768, .n_layers = 6, .n_heads = 6, .n_kv_heads = 6, .vocab_size = 32000, .seq_len = 256 }
shared weights: true
temperature: 0
top-p: 1
SIMD vector size: 4
Versa ran to the park. blah
64 tokens per second

c:\zig\zig build-exe src/main.zig -O ReleaseFast -target x86_64-windows
 main.exe ../out/model110M.bin -t 0 -v -s 42 -p 1.0  -i "Versa ran"
config: main.Config{ .dim = 768, .hidden_dim = 2048, .n_layers = 12, .n_heads = 12, .n_kv_heads = 12, .vocab_size = 32000, .seq_len = 1024 }
shared weights: true
temperature: 0
top-p: 1
SIMD vector size: 4
Versa ran to the park. blah
9 tokens per second
llama2.zig> c:\zig\zig build -Doptimize=ReleaseFast
main.exe ../out/model110M.bin -t 0 -v -s 42 -p 1.0  -i "Versa ran"
config: main.Config{ .dim = 768, .hidden_dim = 2048, .n_layers = 12, .n_heads = 12, .n_kv_heads = 12, .vocab_size = 32000, .seq_len = 1024 }
shared weights: true
temperature: 0
top-p: 1
SIMD vector size: 4
Versa ran to the park. blah
10 tokens per second
largely in the noise  even at the larger sizes. if that is what you meant?


Testing/repairing apply_mask()

This PR is for initial work on retrofitting unit tests to apply_mask().
As of the first few commits, the work is incomplete. Therefore, this PR is intended for discussions around design & retrofitting testing to iteratively improve the retro-fix approach.
Interlinked problems exist with retro-fitting testing to this codebase:

Production code depends upon iris.cube.Cube objects.
iris.cube.Cubes need to be read from files
iris.cube.Cubes are complex data structures, with production code accessing multiple Cube attrs
Avoiding I/O (e.g. loading UM files) in low level unit tests
Simulating Cubes wtih mocks requires tricky/fragile work to build nested data structures

Fixes Required:
test_apply_mask_with_matching_grid_extents():

the final assertions are weak & incomplete, only checking for data modification. Does this need more detailed tests to ensure the algorithm works as expected?
Use np.where()?

test_apply_mask_with_non_matching_grid_extents():

relies on fragile mocking to synthesise cube attrs. Is there a way to create/ a synthetic cube from real data & skip mocking?
also has weak assertions

IDEA: instead of mocking coords, can the iris.cube.Coord subclasses be used directly?

Testing & cleaning apply_mask() needs cubes with coordinates & other attributes. This will be easier to complete when the changes in #111 & #69 are merged (make use of existing test fixtures).

I think this PR will not be added in the first release, and we might think about ways to restructure um2netcdf.py to make itself and testing easier and cleaner.
Therefore, I would close it without merging.
What do you think @blimlim ?

I think so, let's close this for now – I think testing the apply_mask() function would become easier in the future if we swap to using actual iris cubes for the tests (i.e. #150). Let's leave the relevant issue #15 open though


Pass the request name to the InvalidStateTransition exception

Fixes #10646
Status
In development
Description
Since I cannot reproduce neither find where the flaw is, I'm actually providing a change to the information that gets provided from the InvalidStateTransition exception, such that we also know which workflow name failed.
Other than that, there is a new unit test to test that cherrypy logic to move request status forward.
PS.: Lists are meant to keep the same order in which elements are appended/created, so the correct chained status transition should be guaranteed.
Is it backward compatible (if not, which system it affects?)
yes
Related PRs
none
External dependencies / deployment changes
none

This has been tested and we have the necessary information available now:
cmst1@vocms0265:/data/srv/wmagent/current $ curl --cert $X509_USER_CERT --key $X509_USER_KEY -X PUT https://alancc7-cloud2.cern.ch/reqmgr2/data/request/amaltaro_TC_PY3_TTbarPU_June2021_ValPY2_210630_102120_6021 -H "Content-Type: application/json"  -d '{"RequestStatus": "running-open"}'
...

400 Bad Request

Invalid spec parameter value: InvalidStateTransition c4c5c32bb7811224587c2a46b3200ad8 [HTTP 400, APP 1101, MSG "Invalid status transition for request: amaltaro_TC_PY3_TTbarPU_June2021_ValPY2_210630_102120_6021, from 'completed' to 'running-open'", INFO None, ERR None]

I need to hand it over to Imran very quickly, but a post-merge review would still be much appreciated. Thanks!


prevent eta-expansion in Scala 3

The issue is that if you define cancel with parenthesis it becomes basically unusable from scalac because forgetting parents doesn't trigger a compilation error. Also that is a big breaking change, so if a change is absolutely necessary I would prefer adding an alias instead of changing the existing cancel definition.
What's the situation with dotty? Do you get warnings with the current state?

I get a warning that this will not be supported by dotty anymore. But you are right; it would be quite the breaking change. Let's cross this bridge when we have to.

https://dotty.epfl.ch/docs/reference/changed-features/eta-expansion.html is the current situation with dotty in this regard.


Mac instructions for backend check

steps I had to perform to instal third_party/onnx needed by the check-onnx-backend tests

I'm a bit surprised that you need to manually install pybind, maybe I have it already installed as a dependency of other packages; regardless, it shouldn't hurt putting this extra information under FAQ. Thanks for the explanation!

I have a particular change to build on Mac. Since the default python on Mac is 2.7. I installed the new python. Even after I added the path to the new python and define alias of python, I still need to set PYTHON_EXECUTABLE in my make file. Otherwise check package for PyInterp will fail. Is there a simple solution to be included in the document?

@chentong319 Thanks for the input; I modified the text to incorporate your input.


util.toFastProperties loses its mojo in Node 7+

Just a heads up it looks like the toFastProperties trick has lost its magic in Node 7+.

@jdalton yeah, we realized - Bluebird runs on a lot of older versions too though.
If you're interested, the following works in Node 7 if I recall from when we discussed replacing it:
function enforceFastProperties(o) {
	function Sub() {}
	Sub.prototype = o;
	var receiver = new Sub(); // create an instance
	function ic() { return typeof receiver.foo; } // perform access
	ic();
	ic();
	return o;
	eval("o" + o); // ensure no dead code elimination
}

Nice That works in Node 4+ (including Node 7).


date picker color

I've read the documentation, but doesn't find anything on how to change the date picker color.
found the answer in:
https://stackoverflow.com/questions/35246411/how-to-change-default-body-color-of-materialize-datetimepicker
but with current version i don't think it's compatible anymore.
is there no implementation on changing the color like:
<input type="text" class="datepicker teal lighten-2">
or do i have to edit manually(or add custom css) to override the default css?
thank you.

You have to override the color of the time picker of materialize. You can change the following(using sass):
.timepicker-digital-display{
  background-color: #056ea3;
}

.timepicker-close{
  color: #056ea3;
}


"errorCode": null when fetch prices or get market

Hi, me again
I am getting this error when I want to get the market or the prices or whatever.
It appears randomly, if I retry the call it works...
I think it comes from ig, from what I saw, but in the companion it does not happen to me.
the content of ig response is request_code = 500 content {"errorCode": null}

ig_service = IGService(user, pass, api_key, env)
ig_service.create_session()
prices = ig_service.fetch_historical_prices_by_epic('CS.D.CFDSILVER.CFM.IP', resolution="W",
                                                                     start_date='2021-2-27',
                                                                     end_date='2021-3-29'
                                                                     )
market = ig_service.search_markets('EURUSD')

Thanks a lot!

If you think the problem is with IG, then this is not the place to report it. Try the IG community site, or IG support


TikTok black ring fix

Fixes the black ring around the TikTok icon. As of pbozyk's solution here: https://github.com/jaketrent/react-social-icons/issues/146

Recreate by using bgColor="white" fgColor="black"

can someone merge this? The tik tok ring is making this package literally unusable for me

hi @akakalle, this has been addressed in v6 of react-social-icons
CC @lizzieshipwreck

@couetilc great thanks for the update!


Change navbar

Fixed Issue: #291

@gauranshivarshney I didn't assigned you this issue and you have created Direct Pull Request.
This is not a Good Practice.
So I am Closing the Pull Request.
Untill I assign the issue bo one should create or commit the pull request.


Issue 35

This PR should resolve most of issue 35.  I added 2 files to src/test/resources that demonstrate the difference in output from running the python prototype implementation vs. the more current scala implementation.  The scala version has a mix of my interpretation of how translator reasoner api expects the message to be & what was returned in the python prototype.  That said, the scala version should be valid.

Tests seem to have failed on Files.writeString which is not in jdk8.  Are we really doing jdk8?

We can stick with Java 11 if you prefer. I have been continuing to test on both because I continue to have a few projects and machines stuck on Java 8.

@jdr0887 I made a commit with a little bit of ZIO style cleanup: fc86cb9f916adf22c487d733455b616ec50ab072

I'm trying to run this against the SPARQL endpoint at https://stars-app.renci.org/cam/sparql, with this query, with a limit of 5:
{"message": {
        "query_graph": {
          "nodes": [
            {
              "id": "n0",
              "type": "gene"
            },
            {
             "id": "n1",
             "type": "molecular_activity"
            },
              {
             "id": "n2",
             "type": "molecular_activity"
            },
            {
              "id": "n3",
              "type":"gene"
            }
          ],
          "edges": [
            {
                 "id": "e0",
                 "type": "enabled_by",
                 "source_id": "n1",
                 "target_id": "n0"
            },
              {
                  "id":"e1",
                  "type": "affects",
                  "source_id": "n1",
                  "target_id": "n2"
              },
              {
                  "id":"e2",
                  "type": "enabled_by",
                  "source_id": "n2",
                  "target_id": "n3"
              }
          ]
        }
      }
    }

The old app returns in less than 5 seconds. This code times out. The main query looks essentially the same; not sure where the slowdown is yet.

One issue I'm seeing: this query is executed 12 times:
SELECT DISTINCT  ?qid ?kid ?blslot ?label
WHERE
  { VALUES ( ?kid ?qid ) {
      ( RO:0002212 "e0000" )
      ( BFO:0000051 "e0001" )
      ( BFO:0000066 "e0002" )
      ( RO:0002233 "e0003" )
      ( RO:0002413 "e0004" )
      ( BFO:0000050 "e0005" )
      ( RO:0002234 "e0006" )
      ( RO:0002213 "e0007" )
      ( RO:0002333 "e0008" )
      ( RO:0002339 "e0009" )
      ( RO:0002338 "e0010" )
      ( RO:0002313 "e0011" )
      ( RO:0002629 "e0012" )
    }
    ?blslot  <http://reasoner.renci.org/vocab/slot_mapping>  ?kid
    FILTER NOT EXISTS { ?other  <http://reasoner.renci.org/vocab/slot_mapping>  ?kid .
                        ?other (blml:is_a)+/(blml:mixins)* ?blslot
                      }
    OPTIONAL
      { ?kid  rdfs:label  ?label }
  }

I think there must be some duplicate work happening.

I made a commit that partially addresses the issue.

Looking for your opinion....
This:
          allPredicates =
            trapiKGEdgeBindings
              .map(a => a.provenance)
              .filter(a => a.isDefined)
              .flatMap(a => prov2CAMStuffTripleMap.get(a.get).toList)
              .flatten
              .map(a => a.pred.toString)
              .distinct
          slotStuffList <- getSlotStuff(allPredicates)

versus:
allPredicates = (for {allPredicates = (for {
              edgeBinding <- trapiKGEdgeBindings
              prov <- edgeBinding.provenance.toList
              camStuffTriples <- prov2CAMStuffTripleMap.get(prov).toList
              triple <- camStuffTriples
              predicate = triple.pred.toString
            } yield predicate).distinct
          slotStuffList <- getSlotStuff(allPredicates)

              edgeBinding <- trapiKGEdgeBindings
              prov <- edgeBinding.provenance.toList
              camStuffTriples <- prov2CAMStuffTripleMap.get(prov).toList
              triple <- camStuffTriples
              predicate = triple.pred.toString
            } yield predicate).distinct
          slotStuffList <- getSlotStuff(allPredicates)

For me, the former is more readable.  Thoughts?

I would write your new version like this:
allPredicates =
            trapiKGEdgeBindings
              .flatMap(_.provenance)
              .flatMap(prov2CAMStuffTripleMap.get)
              .flatten
              .map(_.pred.toString)
              .distinct

It does look nice. In this case I still prefer the for comprehension, because I have to think hard about all the layers of Lists and Options. Writing it in the for comprehension made it easier for me to unravel step by step. I think either is fine.

That's really concise.


MINOR: update default for field in DeleteTopicsRequest

When using DeleteTopicsRequest with topic IDs, the topic name field should be null. Before, the code was programmatically assigning null, but it will be easier and less error prone to simply set that as the default.
Tested using the previously created DeleteTopicsRequestTest.java file.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Test failures are not related. Merging to trunk.


the question about function run_and_find_attn

Thanks for your work and code.
I would like to inquire why commenting out the run_and_find_attn function(ptp_utils  line 261) causes an error, as it seems that the output of the run'and_find_attn function is not being used.

This function monkey patches stable diffusion to the output of the cross attention in stable diffusion. This becomes the new forward function and this Is where the output of the cross attention is collected in the new forward function. This goes through and does the replacing. When this is done even though nothing is being specifically returned by the function it is able to collect the attention maps during the forward pass.I hope that makes everything clear :)

This function monkey patches stable diffusion to the output of the cross attention in stable diffusion. This becomes the new forward function and this Is where the output of the cross attention is collected in the new forward function. This goes through and does the replacing. When this is done even though nothing is being specifically returned by the function it is able to collect the attention maps during the forward pass.I hope that makes everything clear :)

Thanks for your replies.

Closing for now but feel free to reopen if you have more questions


Fix numba version to 0.56

Creating the fresh env locally, mamba thought it could install numpy 1.24 with numba 0.53, which are incompatible, but that is not specified on the numba 0.53 package on conda-forge.
So here we explictly add the most recent numba version, which results in mamba correctly resolving it to the numpy 1.23 + numba 0.56 pair

is there an issue opened for the numba package spec on conda-forge? Seems like they should fix that

Yes, several... I guess they didn't go as far back as 0.53 though. We should just require a recent version


passing null value as parameter throws "java.lang.IllegalArgumentException"

I've requirement to check null value for a parameter and this is how I'm passing it
given().
               contentType("application/json").
               pathParam("NI", 3000).
               pathParam("DP", null).

but this code throws error
java.lang.IllegalArgumentException: parameterValue cannot be null
related issue https://github.com/rest-assured/rest-assured/issues/631

What do you mean by "check null value"? You cannot pass "null" as a path parameter. It doesn't make sense, perhaps you mean an empty string?

@johanhaleby this is what I'm doing with cURL
curl -i -H "Content-Type: application/json" -X GET http://end_point/v1/grid?netIncome=3000&downPayment=null&loanDuration=null
It returns 200 after ignoring values of downPayment, loanDuration. I would like to simulate same with rest-assured library, please clarify.

Then pass in a null as a string, "null"

And besides downPayment and downPayment are query parameters in the REST Assured parlance, not path parameters.

So use queryParam instead

Thanks, I tried below with one issue
 given().
                contentType("application/json").
                queryParam("netIncome", 3000).
                queryParam("downPayment", "null").
                queryParam("loanDuration", "null").
        when().
                get("http://end_point/v1/grid").
        then().
                statusCode(200);

Expected status code <200> but was <400>.
But when I just have empty string " " , it works fine.

@johanhaleby can you please clarify per last comment ?

So use queryParam instead

Like you just did, don't use pathParam when you mean queryParam. Also "null" is a string, you probably want to use an empty string ("") or no value at all (e.g. queryParam("downPayment"))

Thanks for clarifications.

Hi,
How to pass empty body to post request using  Rest Assured? Help me to resolve this.

@PaulinSangeetha Im using "{}"


Vickel: Watch electrustelectrial.blogspot

Vickel requests the watch of the watch_keyword electrustelectrial\.blogspot. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

electrustelectrial\.blogspot has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Query cache

Motivation
Provide initial version of the cache mechanism.

First phase for enabling offline capabilities.
This cache works for queries. Entries do not expire and are merged so even if result is just fragment only particular fields will be updated.
Next phase is to provide:

Mutation support
Subscription postFetch action
Prefetch on start actions


feat(NumberField/CanonicalEmbedding): add normAtPlace

Working in the mixed space ℝ^r₁ × ℂ^r₂ associated to a number field can be sometimes tedious since one has to deal separately with real and complex components even though the arguments are often very similar.
In order to make working with norms easier, this PR defines for an infinite place w and an element x of  ℝ^r₁ × ℂ^r₂, normAtPlace w x as essentially ‖x w‖ and proves many properties about it. This make it possible to golf some existing proofs and will also make things simpler in the coming PRs about the fundamental cone.

Thanks!
bors merge


How to Integrate Three Biological Replicates within the same slice

Hi,
Thank you for developing such an elegant analysis tool. I have encountered some issues while using it. There are three biological replicates within the same slice, and I have noticed that the sample consistency is not very good when analyzing the entire section as a whole. Could the integration methods in stereopy address this situation?
I have separately read the split GEM files, processed them, and attempted to integrate them using the st.utils.data_helper.merge method. However, I encountered the following error message. Could you please advise on how to resolve this issue? Looking forward to your response.

N1 = res_dir / '210716_1_N1.TissueCut.gem'
N2 = res_dir / '210716_1_N2.TissueCut.gem'
N3 = res_dir / '210716_1_N3.TissueCut.gem'

N1 = st.io.read_gem(N1, bin_size=50)
N2 = st.io.read_gem(N2, bin_size=50)
N3 = st.io.read_gem(N3, bin_size=50)

N1.tl.cal_qc()
N2.tl.cal_qc()
N3.tl.cal_qc()

N1.plt.genes_count()
N2.plt.genes_count()
N3.plt.genes_count()

N1.tl.filter_cells(
        min_gene=15,
        min_n_genes_by_counts=3,
       # pct_counts_mt=5,
        inplace=True
        )

N2.tl.filter_cells(
        min_gene=15,
        min_n_genes_by_counts=3,
       # pct_counts_mt=5,
        inplace=True
        )

N3.tl.filter_cells(
        min_gene=15,
        min_n_genes_by_counts=3,
       # pct_counts_mt=5,
        inplace=True
        )

data_N = st.utils.data_helper.merge(N1, N2, N3)
---------------------------------------------------------------------------
ZeroDivisionError                         Traceback (most recent call last)
Cell In[156], line 1
----> 1 data_N = st.utils.data_helper.merge(N1, N2, N3)

File /share/zhangjm/software/miniconda3/envs/stereo_seq/lib/python3.8/site-packages/stereo/utils/data_helper.py:164, in merge(reorganize_coordinate, horizontal_offset_additional, vertical_offset_additional, space_between, *data_list)
    162 new_data.position = np.concatenate([new_data.position, data.position])
    163 if data.position_z is None:
--> 164     current_position_z += space_between / data.attr['resolution']
    165     new_data.position_z = np.concatenate([new_data.position_z, np.repeat([[current_position_z]], repeats=data.position.shape[0], axis=0)])
    166 else:

ZeroDivisionError: float division by zero

You could try MSData on your dataset, referring to the tutorial https://stereopy.readthedocs.io/en/latest/Tutorials/MSData_Clustering.html.
Ray

The function merge will calculate the z-coordinates of each slice, therefore, it need to use space_between representing distance between each slice and resolution representing resolution of sequencing chip, space_between is a parameter of merge needed you to input,  resolution can be mapped from file name of the input data, but i note that your data file name isn't a standard name, it normally is the sn of sequencing chip, which results in the resolution is still 0, you can change the file name of each slice to the sn of sequencing chip like 'sn.N1.TissueCut.gem' to aviod this error.

can I ask you how you separated the GEM files?


Update About page for version 3.5.0

I have updated the about page for CDC located here: https://docs.google.com/document/d/1XzBC65fvuNqCNhctJgDicPKqNWh0DsPucVByly9kiU0/edit#heading=h.ia0ex66ykr5q
Changes are marked with yellow

This is a separate action to the User Guide updates, despite the required changes being detailed in the User Guide GDoc


Overview graph  formatting off when content is all zeros

AH 23 with ah-resque 2.0.4
When I go to the overview screen and there are not tasks pending the graph view looks off.  I'm expecting to see a bunch of lines all running at 0 but instead there is a black bar.
Happens using on Brave browser, Chrome browser, and Firefox  on my Ubuntu 18.04 laptop
Idle Image

Image with some data

Thanks @mfvargo!
While I love this blob visualization, perhaps we should move back to a line chart... which has a y-axis and can handle "0".

If I had to guess, I would say whatever is trying to autoscale to find the mid-point has a bug when it's all zeros.


Grammar update for Interaction data paragraph

In the section: Data sources for custom analytics
The last sentence needs to add the word "to" so that it reads: to use the dataflow connector
In future releases, you'll also be able  use the dataflow connector.

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

ID: 06d56767-ae95-eb6b-353e-af2ccb415d00
Version Independent ID: 5100476a-5a38-b8b3-6ba7-b61869ba3383
Content: Prepare for analytic reporting with Power BI (Dynamics 365 Marketing)
Content Source: ce/marketing/custom-analytics.md
Service: dynamics-365-marketing
GitHub Login: @alfergus
Microsoft Alias: alfergus

Thank you! The updated doc should be live within a few hours.


Post-v2024.02.05 loose ends

Address prioritized issues from v2024.02.05 retro
### Tasks
- [ ] Implement merging of versioned tag into `stable` branch **after** build succeeds, from within the nightly build script. See #3347 for one way **not** to do this (and remove from `release.yml` workflow when fixed)
- [ ] Replace use of `regex` with built-in `re` in `pudl/extract/excel.py` and remove 3rd party library from our dependencies.
- [ ] Understand why the `pudl-etl.log` files in the distributed `stable` and tagged version buckets are such different sizes. Potentially suppress some verbose terminal output from the data uploads to minimize this difference.
- [ ] (Briefly) consider why the `setuptools_scm` versions we get on RTD, and stamped into the DB, and in the `pudl.__version__` outputs are so garbled and different in every context.

Adjacent to these tasks, while doing (and re-doing) the release, it became more clear to me why many projects with date-based versions use a version string more like vYYYY.M.x with the x representing the Nth release of the month in question.

Having the version string explicitly tied to a date guarantees collisions when working through several attempts and addressing failures.
PyPI seems to enforce a no-leading-zeroes policy on version numbers (or I don't understand how to avoid that behavior)

So I wonder if going forward we might want to adopt the more common (but less perfectly interpretable as a date) version format? Under that system the release that finally ended up working would have been v2024.2.3 (the 3rd release pushed out in Februrary, 2024).


 I think so.

No it isn't

Done


Semantic Versioning

This PR will close #242
Description
This PR contains changes for the API's versioning. Once this PR is merged, the API will follow semantic versioning, using a couple of automated tools to manage this. This is explained with the additions in README.md but essentially involves using the Angular commit message style to represent what type of release/version bump should be made. I've also added an extra check box for the PR template just as a reminder when you create/review a PR.
Since DataGateway API will be going into production soon and it's essentially ready for this, I have added a BREAKING CHANGE: commit which will automatically bump the API to v1.0.0.
This branch also contains commits from #275 to get the CI to pass.
Testing Instructions
To test, I have forked DataGateway API (https://github.com/MRichards99/datagateway-api), created a PR equivalent to this and merged it. You can see that a GitHub release of v1.0.0 has been made on my fork, as intended. Have a look at this and check everything looks all good, or fork DataGateway API yourself and follow the steps I did to see if it works for you.

[ ] Review code
[ ] Check GitHub Actions build
[ ] If icatdb Generator Script Consistency Test CI job fails, is this because of a
deliberate change made to the script to change generated data (which isn't
actually a problem) or is there an underlying issue with the changes made?
[ ] Review changes to test coverage

Agile Board Tracking
Connect to #242

The safety part of the CI workflow will be fixed once https://github.com/ral-facilities/datagateway-api/pull/278 is merged.


Update README.md

Purpose
The big change is adding a warning about M1 - docker-outside-of-docker wont work on emulated M1, so Codespaces must be used. Did you somehow get it working on yours?
Other changes are formatting.
Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[X] Documentation content changes
[ ] Other... Please describe:

@kjaymiller Some suggested changes after I went through this step.


Feature/add devtools properly

Description
Major overhaul to ModerationTest.

Clarified which buttons are broken.
Separated sections on /moderation page into ModeratorTools, PostModeration, and DevTools sections
Fixed functionality of Post Moderation so things happen when you select a cohort
DevTool section is set up for functionality, but currently is only skelton code.
Abstracted ModerationTest into smaller files for Seperation of Concerns  because it was just obscenely big.
Placed new files in AdminDashboard
Rerouted buttons to /admin instead of /moderation & left a Warning on /moderation that it is depreciated and will be deleted soon (Didn't delete yet, to avoid chaos with current dev's)
Styled

Fixes #

Tools for moderating posts were turned off.
/moderation was confusing
ModerationTest was too massive of a file.

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Change Status

[x] Complete, tested, ready to review and merge

Has This Been Tested

[x] Yes

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] There are no merge conflicts

Good work, there seems to be a bit of dead code still. Do we need to hang on to that?
Only a very few pieces should be kept. Most I'll be deleting in the next PR.

The moderationTest files will all be deleted in a couple days to give current devs a phase out period.
There are a few ant design pieces that are being kept to make it easy for next cohort to turn them back on if desired.
I'll be cutting the rest out in a future PR, I just didn't want to cut some things that might break anybody's functionality. I know that's the actual reason we use git to make it a non-issue, but it still makes me nervous to get rid of certain dead code till I'm sure.


KWMatcher Bug

line 33
if ([_subject isKindOfClass:[KWFutureObject class]]) {
The Unit Test can't found the symbols. so the method of isKindOfClass doesn't work

KWMatcher.m

the cocospod file needs to choose the unit test target.
If not, the method of isKindOfClass won't find the symbols. the expectFutureValue will always fail


mute

Is your feature request related to a problem? Please describe.
i don wan to constantly press - and wait a minute cuz volume is slow
Describe the solution you'd like
a mute keybind
Describe alternatives you've considered
muting alsa enitrely

i don wan to constantly press - and wait a minute cuz volume is slow

don't you already have the system mute key? Because of that, it doesn't make sense to implement one for spotify_player. spotify_player also supports setting volume from CLI: spotify_player playback volume 0 in case you may need.

I want to mute specifically spotify-player and not the rest of my system.


Release 0.13

coverage: 81.5%. first build
when pulling 3d5b4a0c867ff7f1e10d4acb5530e6571cca1359 on release_0.13
into 50b79fb6d64c12d40d7d8bbbe984d910bb9fd6e7 on master.


Testing NIFs

What is the recommended way to test NIFs in rustler?
Does one implement tests in elixir that test the wrapping module? Does one write tests in rust? If the latter, how are they run?

If you want to test the NIF as a whole, you need to implement your tests in Rust. This is because all functionality in rustler itself depends on functions exported by the BEAM.
If you want to test a more enterprise-logicy part of your NIF, it would probably make sense to write those tests with the Rust test framework.
If you have any more questions, feel free to ask them in the IRC or Slack channel.


imageProjection and mapOptimization node do not work.

Hi, I'm new to LIO-SAM.
I would like to execute the opensource with our own dataset.bag.
But... Our case, imageProjection and mapOptimization node do not work properly, so in rviz, we cannot see the saved cloud data.
every imu data, and velodyne point cloud data were published, but lio_sam/deskew/cluod_deskewed topic, and all the others with /lio_sam/* topic do not contain anything.
We would love to get some advice for our case. Have a nice day!

Even the map frame does not appear in the tf_tree

I think you shoule check whether the topic names you publish the same as the subscribed topics first.

I encountered the similar problem. I wonder where the topic "/lio_sam/mapping/odometry" comes from? According to the logic of this algorithm, "imuPreintegration" needs this topic from "mapOptimization" which is the last node.

If the "imageProjection.cpp" is not giving anything, probably something is wrong with your data. You can try to add some debug code in "imageProjection.cpp" to see if all the data is processed correctly.


Doesn't work expo web

First, the expo snack is broken.
Second, this doesn't work on expo web, I get repeated errors:
muteWarnings.fx.ts:21 Reanimated: createNode is unimplemented on web

You can use this for know: https://github.com/RichardLindhout/react-native-web-tab-view

any updated about it? still seems not to work with expo web

It should work, but I don't use expo web. This is a Typescript error with a @ts-ignore it should work.

I guess Latest Expo SDK version 36 causes the issue..It worked pretty well with the lower 35 version
Hope to get some solution soon !!


Update dependencies

This PR fixes all the warnings, tested on Linux.

:broken_heart: Test failed - status-travis

Issues revealed by CI:

32bit *-linux-androideabi failure: https://github.com/Stebalien/xattr/issues/18

64bit *-linux-android: fixed by https://github.com/rust-lang-nursery/net2-rs/commit/d958a03dea71f3b2315adc0167bda6aa63c081c9, new release was made recently with fix

powerpc64le-unknown-linux-gnu

LLVM error (click here to expand)
LLVM ERROR: Cannot select: 0x7f006fa7d0d0: ch = PPCISD::STBRX<ST6[%675](align=1)>   0x7f006e017840, 0x7f006e1939c0, 0x7f006e0167b8, ValueType:ch:i48
0x7f006e1939c0: i32 = truncate 0x7f006e193068
  0x7f006e193068: i64 = srl 0x7f006e016680, Constant:i32<16>
    0x7f006e016680: i64 = or 0x7f006e224f70, 0x7f006fa45b60
      0x7f006e224f70: i64,ch = CopyFromReg 0x7f006e017840, Register:i64 %249
        0x7f006e016000: i64 = Register %249
      0x7f006fa45b60: i64 = shl nuw nsw 0x7f006e193410, Constant:i32<16>
        0x7f006e193410: i64 = AssertZext 0x7f006e016af8, ValueType:ch:i8
          0x7f006e016af8: i64,ch = CopyFromReg 0x7f006e017840, Register:i64 %252
            0x7f006e1936e8: i64 = Register %252
        0x7f006e016bc8: i32 = Constant<16>
    0x7f006e016bc8: i32 = Constant<16>
0x7f006e0167b8: i64,ch = CopyFromReg 0x7f006e017840, Register:i64 %200
  0x7f006e016f70: i64 = Register %200
In function: _ZN6base646decode6decode17hddc925063b1fb17bE
error: Could not compile `hyper`.

x86_64-unknown-netbsd

libc issue? (click here to expand)
note: /usr/local/lib/gcc/x86_64-unknown-netbsd/5.3.0/../../../../x86_64-unknown-netbsd/bin/ld: /src/target/x86_64-unknown-netbsd/release/deps/libopenssl_sys-5b5efcbe61655b57.rlib(randfile.o): undefined reference to symbol 'setvbuf'
        /usr/local/x86_64-unknown-netbsd/lib/libc.so.12: error adding symbols: DSO missing from command line
        collect2: error: ld returned 1 exit status

Rebased with newer versions.
Android 64bit should get as far as 32bit now, it still needs fixing in libc or xattr crates.
PowerPC64LE and NetBSD will most likely fail again.

@Stebalien thank you for fix and notification.
PR rebased with updated xattr and other minor bumps, PowerPC64LE issue will be fixed in Rust 1.28.
Updating hyper to 0.12 could workaround the issue but it would be breaking change.

@bors r+

:pushpin: Commit f75f71b93f28043745a53c4e5c866fce70492c92 has been approved by Diggsey

:hourglass: Testing commit f75f71b93f28043745a53c4e5c866fce70492c92 with merge 1e621634db89c2849037b89a7ded61e62f02ad2c...

:broken_heart: Test failed - status-travis


#9  Issue - Form Fields Alert

WHEN I move my cursor out of one of the form fields without entering text
THEN I receive a notification that this field is required


Crawl mcot title date

Why this PR
Why we need this PR? To crawl titles and dates for news in MCOT
Changes

Add function to retry if get response403
Add functions to process and crawl titles and dates

Related Issues
Close #
Checklist

[ ] PR should be in the Naming convention
[ ] Assign yourself in to Assigneees
[ ] Tag related issues
[ ] Constants name should be ALL_CAPITAL, function name should be snake_case, and class name should be CamelCase
[ ] complex function/algorithm should have Docstring
[ ] 1 PR should not have more than 200 lines changes (Exception for test files). If more than that please open multiple PRs
[ ] At least PR reviewer must come from the task's team (model, eval, data)

Done


Make groups react to all state changes

Make sure you run the latest version before reporting an issue. Feature requests should go in the forum: https://community.home-assistant.io/c/feature-requests
Home Assistant release (hass --version): all current versions
Python release (python3 --version): not relevant
Component/platform: Group
Description of problem:
When you have two device trackers in a group and one the devices is at home, the group state is at home as well.
When that device leaves home and gets in another known zone before the device_tracker gets updated the device state goes from 'home' to 'work' directly and skips the 'not_home' state. This way the groups keeps the 'home' state.
Expected:
No one is at home, so the group state should be 'not_home'
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:
I think the issue is in this piece of code:
            if tr_state is None or (gr_state == gr_on and
                                    tr_state.state == gr_off):
                if states is None:
                    states = self._tracking_states

                if any(state.state == gr_on for state in states):
                    self._state = gr_on
                else:
                    self._state = gr_off

            elif tr_state.state in (gr_on, gr_off):
                self._state = tr_state.state

I think this should be:
            if tr_state is None or (gr_state == gr_on and
                                    tr_state.state == gr_off) or
                                    tr_state.state not in (gr_on, gr_off):
                if states is None:
                    states = self._tracking_states

                if any(state.state == gr_on for state in states):
                    self._state = gr_on
                else:
                    self._state = gr_off

            elif tr_state.state in (gr_on, gr_off):
                self._state = tr_state.state

Does #2631 fix the problem?

Fixed by #2631


problem compiling with VS2017 - not urgent

When trying to compile this project using VS2017 and _compile.bat, there is an error
(_compile_raw.bat works fine) :
C:\Users\ckdnn\CK-MISC\ck-crowdnode>C:\Users\ckdnn\CK-MISC\ck-crowdnode_compile.bat
C:\Users\ckdnn\CK-MISC\ck-crowdnode>call ck set env tags=compiler,lang-c --local --bat_file=tmp-ck-env.bat --bat_new --print   && call tmp-ck-env.bat   && del /Q tmp-ck-env.bat
C:\Users\ckdnn\Anaconda3\lib\runpy.py:125: RuntimeWarning: 'ck.kernel' found in sys.modules after import of package 'ck', but prior to execution of 'ck.kernel'; this may result in unpredictab
le behaviour
warn(RuntimeWarning(msg))
More than one environment found for required software with tags="compiler,lang-c" and setup={"host_os_uoa": "windows-64", "target_os_uoa": "windows-64", "target_os_bits": "64"}:

Microsoft C compiler - v19.10.25017 (64bits,compiler,host-os-windows-64,lang-c,lang-cpp,mcl,microsoft,target-os-windows-64,v19,v19.10,v19.10.25017 (fb528ca2021d4c9b))
- Depends on "msdk" (env UOA=1777d4bd6890515b, tags="microsoft,sdk", version=10.0A)

LLVM compiler - v4.0.0 (64bits,compiler,host-os-windows-64,lang-c,lang-cpp,llvm,target-os-windows-64,v4,v4.0,v4.0.0 (7048a5075ccd4687))
- Depends on "mvsc" (env UOA=fb528ca2021d4c9b, tags="microsoft,compiler", version=19.10.25017)

GNU C compiler - v6.3.0 (64bits,compiler,gcc,host-os-windows-64,lang-c,lang-cpp,target-os-windows-64,v6,v6.3,v6.3.0 (7cab70c651968ea8))

Select one of the options for required software with tags="compiler,lang-c" and setup={"host_os_uoa": "windows-64", "target_os_uoa": "windows-64", "target_os_bits": "64"} or press Enter for 0
:
CK environment found using tags "compiler,lang-c" : fb528ca2021d4c9b

** Visual Studio 2017 Developer Command Prompt v15.0.26228.9
** Copyright (c) 2017 Microsoft Corporation

[vcvarsall.bat] Environment initialized for: 'x64'

** Visual Studio 2017 Developer Command Prompt v15.0.26228.9
** Copyright (c) 2017 Microsoft Corporation

[vcvarsall.bat] Environment initialized for: 'x64'
C:\Users\ckdnn\Anaconda3\lib\runpy.py:125: RuntimeWarning: 'ck.kernel' found in sys.modules after import of package 'ck', but prior to execution of 'ck.kernel'; this may result in unpredictab
le behaviour
warn(RuntimeWarning(msg))
CK environment found using tags "tool,cmake" : 23ac3bf54fbf90bb
A subdirectory or file build already exists.
CMake Warning at C:/Program Files/CMake/share/cmake-3.7/Modules/InstallRequiredSystemLibraries.cmake:453 (message):
system runtime library file does not exist:
'MSVC14_REDIST_DIR-NOTFOUND/x64/Microsoft.VC140.CRT/msvcp140.dll'
Call Stack (most recent call first):
CMakeLists.txt:26 (include)
CMake Warning at C:/Program Files/CMake/share/cmake-3.7/Modules/InstallRequiredSystemLibraries.cmake:453 (message):
system runtime library file does not exist:
'MSVC14_REDIST_DIR-NOTFOUND/x64/Microsoft.VC140.CRT/vcruntime140.dll'
Call Stack (most recent call first):
CMakeLists.txt:26 (include)
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/ckdnn/CK-MISC/ck-crowdnode/build
Microsoft (R) Build Engine version 15.1.548.43366
Copyright (C) Microsoft Corporation. All rights reserved.
MSBUILD : error MSB1009: Project file does not exist.
Switch: Project.sln

I mixed up repository - sorry ...


64 bit windows builds

It looks like few packages are being built for 64 bit windows
https://conda.binstar.org/omnia/win-64
Is there a major barrier to building these?

I don't think so. I was doing the windows builds on an ec2 vm, and only did 32 bit.

Not all of the compiler packages include 64 bit support. I think you need the SDK compilers, described https://github.com/cython/cython/wiki/CythonExtensionsOnWindows#using-windows-sdk-cc-compiler-older-method

I build a couple of these on my machine. Is there a mechanism by which I can upload them to omnia?

I put them here https://binstar.org/mpharrigan

SWEET!
Do you have an account on binstar.org? I can add your username to the omnia organization to give you the permissions.

Nevermind. Obviously you do.

You should have permissions now. You can upload the files into the omnia org with binstar upload -u omnia ...  I think.

What steps did you have to follow to get the 64-bit env up and running?

This is going to be somewhat unsatisfactory:
I must have accumulated the compilers over the years. python setup.py install works fine without messing with the env et al. per that cython doc. It says it's using
Microsoft (R) C/C++ Optimizing Compiler Version 17.00.61030 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

I have many of the windows sdks installed and it seems to be finding the right one as well

That being said, appveyor has a whole slew of compilers and sdks as well
http://www.appveyor.com/docs/installed-software

Fair enough. I didn't realize they all worked together so well.

We should really find a way to get appveyor-based incremental builds working based on the stuff that @marsher has done with pyemma builds.  I just haven't had time to play with this yet.

I'm going to try playing with it in the near future

Re appveyor, it looks like the team at ioos/conda-recipes has gotten a system up and running. They're using some tooling from https://github.com/pelson/Obvious-CI which seems to handle some of the cross platform issues. Might be a good place to start from.
https://github.com/ioos/conda-recipes/blob/master/appveyor.yml

Done.


Wrong coordinates

Some coords are wrong in raw data, rows 137 to 236. To be checked by ANB.

After checking this with ANB, the solution is to solve it in the processing data by setting decimal separator after 6 digits.


User ID in send middleware with the Web adapter

When using a send middleware with the Web adapter, the user ID is not available in the message object during a conversation (i.e. Dialog).
For instance, the middleware (bot, message, next) => { console.log(message); next(); } displays these data for a bot message:
{ type: 'message',
  text: 'typed!',
  inputHint: 'acceptingInput',
  channelData: {} }

A possible solution consists in extracting the user ID for the convo vars in the function makeOutgoing(dc, line, vars)
of conversation.ts:
// copy user and channel from vars (for Web adapter)
if (!outgoing.user && vars.user) {
    outgoing.user = vars.user;
}

Then the message user can be leverage in the send middleware :tada:
{ type: 'message',
  text: 'typed!',
  inputHint: 'acceptingInput',
  channelData: {},
  user: '7a247882-bdab-c853-7175-f97d3978d663' // <= Yes!
}

Moreover, when a message is sent with bot.reply or bot.say, the user ID is not present in the traditional (legacy?) messager.user.
{ type: 'message',
  text: 'Echo: pizza',
  // ...
  recipient: { id: '7a247882-bdab-c853-7175-f97d3978d663' },
  // ...
  user: '7a247882-bdab-c853-7175-f97d3978d663', // <= It would be great to have this
  // ...
}

It could be great to add it in the function ensureMessageFormat(message) of botworker.ts:
const activity = {
    type: message.type || 'message',
    text: message.text,
    // ...
    user: message.recipient && message.recipient.id,
    // ...
};

Can these points be integrated in a future release of Botkit?
How can i make myself useful to the code?
Thanks,
Chris
Context:

Botkit version: 4.10.0
Messaging Platform: Web (botbuilder-adapter-web in version 1.0.9)
Node version: v10.15.1
Os: MacOS

Can you please send these in as a pull request? And can you include some test cases when you do?

Hi @benbrown!
I have just submitted the related tiny PR.
Finally I did not add user to the activity object in botworker.ts, to respect the Activity type. But the recipient field can be leverage in a send middleware to get the user.
So, with this fix, a send middleware like this can be done:
(bot, message, next) => {
    if (message && message.type === 'message') {
        const user =
            message.user ||
            (message.recipient && message.recipient.id);

        // => Store here the bot message for the given user
    }
    next();
}

Hey!
I have just added a comment to the related PR (#2043) in order to remove the stale flag.
The code is working nicely in my chatbots powered by Botkit 🚀
I hope the next release of Botkit will integrate this PR.
Cheers,
Chris

🆙 I still hope the next release of Botkit will integrate the related PR (#2043)...


Print only two decimals for build duration

This simple change prints only two decimals for the build duration. Before it
would print often many more decimals than I think are required to show the
duration of a build.

In general probably not, but I found at least one job that has build that last less than a minute, and showing just "0" would look strange I think


x/net/http2 building with gccgo

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

$ go version
go version go1.12.1 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/sgx/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/sgx/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="/usr/bin/gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build844707027=/tmp/go-build -gno-record-gcc-switches"

What did you do?

I tried to build the http2 package with gccgo by running the command go build -compiler gccgo golang.org/x/net/http2.
What did you expect to see?
I expected the build to succeed.
What did you see instead?
The following error occurs:
# golang.org/x/net/http2
./go111.go:15:30: error: reference to undefined field or method ‘WroteHeaderField’
  return trace != nil && trace.WroteHeaderField != nil
                              ^
./go111.go:19:26: error: reference to undefined field or method ‘WroteHeaderField’
  if trace != nil && trace.WroteHeaderField != nil {
                          ^
./go111.go:20:8: error: reference to undefined field or method ‘WroteHeaderField’
   trace.WroteHeaderField(k, []string{v})
        ^
./go111.go:26:15: error: reference to undefined field or method ‘Got1xxResponse’
   return trace.Got1xxResponse
               ^

Which version of gccgo are you using?

I suspect that the problem is that the go tool is using the gc release version, but you are using a version of gccgo that is at a different release version.
Have you tried building with the go tool that comes with gccgo instead?

Resolved. Didn't realize there was a go tool that came with gccgo. Will close this now, thanks!


Fix broken tidal_tag function in dea_tools.coastal

Proposed changes
Recent updates to xarray broke code in the tidal_tag function (See: https://github.com/digitalearthafrica/deafrica-sandbox-notebooks/pull/299).
~This PR fixes the code, and also attempts to add the notebook to our tests so we can pick up broken code in the future.~
Update: decoupling the tests from this issue so we can get these bugs resolved quickly, then we can think about how to deal with accessing OTPS data for testing purposes later.

This bug correctly breaks all coastal notebooks in the repo, so it will be good to get this PR merged and we can sort out the tests later on.


link to the needed password? is dead

Not sure the purpose of the password...increase in youtube views? But unfortunately link is dead, shame this is a cool well developed project. Hopefully i get to try it, as horrible as it use to use windows, needs must when the devil drives.

Hope they have a lovely day! /s
I hate pirating things because of this...

 A literal buffer overflow on the password entry prompt!
Serves them right.
I doubt it.

You can just enter about 140 characters and it just bypasses it lmfao.
Also, the password is hadikit. It's not in the exe file (probably compression/encryption/whatever), but it is stored in plaintext inside the process's virtual memory!
This wanker also got the delight of a nice dislike on his Youtube video for wasting me, your, and everyone's time.

Hahaha i love yeah buddy, cracking me up man, good times Hahaha thatll keep me going for a while. He is a talented programmer I hope he sees the importance of open source someday.

It's been a long time since I checked this tool.
It's been added for non-passwords.
I'm sorry & I will close this.

 Thank yoy for your work
On Mon, 5 Feb 2024, 12:57 am HadiKhoirudin, @.***>
wrote:

It's been a long time since I checked this tool.
It's been added for non-passwords.
I'm sorry & I will close this.
—
Reply to this email directly, view it on GitHub
https://github.com/HadiKhoirudin/Qualcomm-Tool/issues/4#issuecomment-1926282495,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADAWMPZKR5K6X6RM7JKKWQ3YSBYD7AVCNFSM6AAAAABBE6ZTMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRWGI4DENBZGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Error property in log and RUM context is stripped of properties

Describe the bug
DdLogs.[level] and DdRum.addAction strips properties from context.error
Using latest minor version of "@datadog/mobile-react-native", through "expo-datadog"
On Android
With a basic error
const error = new Error("foo")

When they reach the Log Explorer, these will have no @error.* attributes whatsoever
DdLogs.info('message', { error })
DdLogs.info('message', { error: { message: error.message, stack: error.stack, name: error.name })

When they reach the Log Explorer, these will have an @error.message, @error.stack and @error.kind, but no other Error properties
DdLogs.info('message', error.name, error.message, error.stack, { error })

Error.cause is also stripped, as are any custom properties if using a custom Error (the below will have no @error.* attributes in Log Explorer)
class MyCustomError extends Error {
  name = 'MyCustomError'

  foo = 'bar'
}

DdLogs.info('message', { error: new MyCustomError("foo", { cause: "bar" }) })

On iOS
We get a little more than on Android, but still not much
Most we only get:
{
  "error": {
    "jsEngine": "hermes"
  }

For a custom error class, then we see slightly more e.g. an Urql Network error (https://github.com/urql-graphql/urql) appears in Log Explorer like
{
  "error": {
    "jsEngine": "hermes"
    "name": "CombinedError"
     "networkError": {
        "jsEngine": "hermes"
      }
    }
}

Notes
The only workaround I found to ensure all "error" properties were kept was the following:
DdLogs.info('message', error.name, error.message, error.stack, {
  otherNonErrorContextProperty: 'value',
  'error.name': error.name,
  'error.customProperty': error.customProperty,
  'error.cause': {
    'message': error.cause.message,
    'stack': error.cause.stack,
    'name': error.cause.name,
    'customProperty': error.cause.customProperty,
  },
})

but this feels like this should be a responsibility of the library, not the caller
Reproduction steps
The following test passes + the differing behaviour between Android and iOS suggests it's in the native module side rather than this SDK
import { DdLogs } from '@datadog/mobile-react-native'
import { NativeModules } from 'react-native'

jest.mock('react-native', () => {
  const RN = jest.requireActual('react-native')

  RN.NativeModules.DdLogs = {
    info: jest.fn().mockImplementation(
      () =>
        new Promise<void>(resolve => {
          resolve()
        })
    ),
  }

  return RN
})

describe('tracking', () => {
  beforeEach(() => {
    DdLogs.unregisterLogEventMapper()
  })

  it('test', async () => {
    class CustomError extends Error {
      name = 'CustomError'

      foo = 'bar'
    }
    const context = { error: new CustomError('foo') }

    await DdLogs.info('message', context)

    const args = NativeModules.DdLogs.info.mock.calls[0]

    expect(args[1].error.message).toBe('foo')
    expect(args[1].error.stack).toEqual(context.error.stack)
    expect(args[1].error.name).toBe('CustomError')
    expect(args[1].error.foo).toBe('bar')
  })
})

SDK logs
No response
Expected behavior
DdLogs.[level] and DdRum.addAction should preserve all (built-in and custom) properties on an error property on the context argument
Affected SDK versions
2.4.3
Latest working SDK version
N/A
Did you confirm if the latest SDK version fixes the bug?
Yes
Integration Methods
Yarn
React Native Version
0.73.6
Package.json Contents
{
"dependencies": {
"expo-datadog": "51.0.2",
"react-native": "0.73.6",
"@datadog/mobile-react-native": "2.4.3"
}
}
iOS Setup
No response
Android Setup
No response
Device Information
No response
Other relevant information
No response

Hi @max-nicholson! 👋 thank you for reaching out :)
As a reference I will paste the arguments that all the DdLogs "with errors" APIs accept:
export type LogWithErrorArguments = [
    message: string,
    errorKind?: string,
    errorMessage?: string,
    stacktrace?: string,
    context?: object,
    fingerprint?: string,
    source?: ErrorSource
];

And its simplified overload:
export type LogArguments = [message: string, context?: object];

In your case, you want to keep track of all the error properties, by passing it inside the context.
I believe the problem is that, as the context has to be serializable in order to reach the native layer, it might be received as an empty object because Error in JavaScript does not have any enumerable properties.
What can you do?
If that's the root of the issue, you could write your serialize function once and use it on the errors that you want to report, as you mentioned in your description
e.g
function serializeError(error: Error) {
  return {
    'error.name': error.name,
    'error.customProperty': error.customProperty,
    'error.cause': {
      'message': error.cause.message,
      'stack': error.cause.stack,
      'name': error.cause.name,
      'customProperty': error.cause.customProperty,
  },
}

This would work because you are retrieving the values of the non-enumerable properties of the error, and you are manually inserting them into your context object.
What can we do?

Improve our validation of the context: it's our responsibility to report whether the context is valid or not
Provide a standardized way to serialise the error object: we could improve our SDK so that if an error object is passed in the context, we perform a default serialization on it to make sure no properties are lost

I'd be glad if you could confirm that this is indeed the problem and in the meantime we will plan some improvements, and keep you posted on the topic and on future evolutions of our SDK.
Does it sound good to you? :)