ci: Add Sync Labels Workflow

Description
This change introduces a label synchronisation system for the repository. It adds a new YAML file .github/other-configurations/labels.yml that defines a set of standardised labels, including default GitHub labels, Release Please labels, language-specific labels, and component-specific labels.
Additionally, a new GitHub Actions workflow .github/workflows/sync-labels.yml is created to automatically synchronise these labels with the repository. The workflow is triggered when changes are pushed to the main branch, specifically to the labels configuration file.
fixes #22

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

#10
#9
#8
#7  👈
#6
#5
#4
#3
#2
#1
main

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

Join @JackPlowman and the rest of your teammates on  Graphite

Merge activity

Sep 25, 2:20 PM EDT: @JackPlowman merged this pull request with Graphite.


Patch 1

i had done the required changes

how to create a new minified file??

how to create a new minified file??

npm run release

IT IS GIVING LOTS OF ERRORS WHEN MINIFIED

IT IS GIVING ERROR WHEN MINIFIED

Use npm run release command to create minified file


Explain power management problems in the PTP context

Hi Vinicius,
this provides a brief introduction into power management related issues and how to approach them.
I am open to any suggestions to improve it!
Greetings,
Florian

Applied. Thanks.


.update(obj) does not work as expected

My Problem is a bit weird because for one sort of my DataModel the .update(object)-Function does not work.
I am pulling Elements from a Wordpress Blog and if there is something new I overwrite all properties of the old/persisted element with the new one with this code:
function replaceObjectWith(n, db){
	var old = db.findObject({
			ID: n.ID
	});
	if(old != null){
		for (var property in n) {
			if (n.hasOwnProperty(property) && old.hasOwnProperty(property)) {
				old[property] = n[property];
			}
		}
		db.update(old);
	}
}

I have a few different categories and for each category I have one collection. This does work for all categories/collections except for one and I don't know why because I do it always the same way. With this category I get the following error:
TypeError: null is not an object (evaluating 'arr')
lokijs.min.js:3:18710
And then in this collection the Item is doubled, how can this be? I mean not only the complete Element is doubled but also the $loki has the same ID. How could that happen? I thought this is the unique ID... Already tried a lot of things but now a bit confused
EDIT:
The object I pass with db.update(old) is of course not null.
What is really strange is that if I commenting out the last line of Collection.prototype.update ("throw err") than it works like a charm! If it is not commented out it throws this error, and no I do not pass an array I pass a normal Object with a few properties!
Any help appreciated what is wrong here?

If you are able to reproduce this by "not commenting out the throw in collection.update()" then you have more to go on than me :)  Maybe post a plunkr or swap out the minified for full loki.js and step into it.
By default, loki returns your 'find' results as the same object references as it keeps internally.   So it would be easy for you to overwrite the internal objects if you modified the objects returned unintentionally and/or did not bother to call update().  The other possibility is that somewhere in findObject() and/or update(), we are ourselves duplicating your object.
I tried to recreate this in a simple example but it seemed to be working as expected for me.
Aside from posting a plunkr, if you can recreate this on a new collection you might use the 'clone' option when calling db.addCollection() to ensure internal object references are not exposed to user.  If it was your code corrupting it, that should prevent it and/or shed more light on issue.

Thanks for your help. I'll try with the full loki.js this evening and have a look if it is the same behavior or not. With your simple exmaple please click 2x very fast one after another on "Run" an then the result for me is this:

Not sure why but it seems that my code tries to update the object very fast 2 times for this one category, could that be? Whats going on than with loki.js? As be said I'll try out later and report...

Hmm not sure 2x click is loki issue, probably the sandbox page scripts since I clear text, wait 250 ms and -then- async add/run your script.  Both clears are happening before both logs.
You can modify the last line in that script to read :
sbv.editorOutput.setValue('');
logObject(result);
inspectObject(result);

Then the log is normal and Object inspector shows array of 1 document.
Yes if you can reproduce in the sandbox or somehow else please report.

So I tried out with the normal loki.js and I found out that in the Collection.prototype.update-Function my $loki-ID (via doc.$loki) is the right one for the object. But this function: var arr = this.get(doc.$loki, true) returns null --> does not find the object with specified $loki id, but if I log the whole collection this id is definetely in the collection. Not sure how to deal with that!?

Ok I'd still like to trace into the get statement, but here's a few things you might check.

Inspect the value of collection.idIndex (I believe you call collections db) and make sure all the 'values' in that array are ordered lowest to highest.

You might also make sure they are number and not a string... although loki ensures that the id you pass to get is number (integer), it does not ensure that $loki itself is number and since you are shallow cloning maybe there was a string $loki in object passed to replaceObjectWith.

If your data is not sensitive and you are running node/filesytem, maybe you could upload your db somewhere I can download and import into the sandbox.

In the first time the collection.idIndex is correct if I load it clean. But when trying to update the first item of category ("releases") than this index gets corrupted and nothing works as normal for this category. not sure how and why the idIndex gets bad for this category. I am not doing anything in another way than for other categories and for them it works.

I checked and it is always a number. You are right I am always try to complete clone the object with the new one. I searched for a method for this like "replaceObjectAtIndex:$loki With:newObject" but didn't find one. Now what I tried is it possible and good if I replace my for-loop with n.$loki=old.$loki;db.update(n); or is this not better?

Here you have a link to my fresh created database: https://www.dropbox.com/s/fsxqmk2p9jbyemd/lokiDB__hyphyDB?dl=0 It should not be corrupted and as said it works well for every collection except for "releases".

Usually if you were to inspect the collection data, you would find it is and should always be sorted by $loki and so the idIndex would also be sorted by $loki.
Does the object you pass to replaceObjectWith have its own $loki property?  Is this an import from an existing / alternate loki database?  If so you might want your for-loop to not clone any properties named '$loki' or 'meta'.  Maybe try something like :
function replaceObjectWith(n, db){
    var old = db.findObject({
            id: n.id
    });
    if(old != null){
        for (var property in n) {
            if (n.hasOwnProperty(property) && old.hasOwnProperty(property) && property !== "$loki" && property !== 'meta') {
                old[property] = n[property];
            }
        }
        db.update(old);
    }
}

That should in theory keep your update function from updating the 'in-place' data[] references with $loki document properties that are out of order.

You are right there is a "meta" field in my old/new Object. But this field is not only for that one category where it does not work rather every collection/category has it (due to Wordpress REST-API there it returns always a meta field).
I updated the replace Function as you mentioned but it did not help, the error persists. And I also thought previously of that the $loki property gets overwritten somehow but this is also not the case. Thus I am really helpless whats goingon. And as already mentioned I tried a lot of thins but this error persists and I can not update my app like this because the releases-Collection will than be corrupted... The weirdest thing is that it is really the same code for every collection (I think I have 9) and only one collections have this error all other work as expected.

Yes its even more curious because I don't have a good repro case to help you out with.  I am left to conjecture upon conjecture.
Do you need the old $loki to match with replaced object $loki?  If not, and you are just looking up by 'id' I would suggest remove() of old and insert() of replacement if time is short and you need quick fix.
If you need $loki id's to be the same, it might be better solution to just set $loki and meta on 'new' object and pass that to update rather than graft all properties onto old object.

Sorry for the circumstances. I find loki is pretty cool and it is really very helpful and fast! But I don't know what to try out on top to get this working 🙈.
It is completely irrelevant what $loki id an object has. The only requirement is that I can replace one old object with a new one. Because if there is an update from Wordpress for that object I don't want to store it twice because than it will be shown twice to the user, thus I somehow net to delete/update the old one with the new one.
I already tried to find the Object by ID. Delete this with db.remove(object) and insert the new one with db.insert(object), but it results in the same error after a few updates.
Now what really drives me crazy as already mentioned my Object from Wordpress has a Meta field and I tried to set the meta field to "null", because not sure if that somehow disturbes the loki function and then add the first time to Database:
var object = tempArray[i]; object.meta = null; db.insert(object);
But if I do that than there is the following error: TypeError: Attempted to assign to readonly property. lokijs.min.js:4043 (add-Function). How could that be? This is a none-loki-object (it is a normal JSON-Object) but why is there a Loki Error‽
And what I also tried is to randomly update some Objects by id with this Code:
function replaceObjectWith(old, n, db) { 		console.log(JSON.stringify(db.idIndex)); 		n.$loki = old.$loki; 		n.meta = old.meta; 		db.update(n); 		console.log(JSON.stringify(db.idIndex)); }
So as you can see I log the index before and after update and this is the (randomly) result:

And from the first update on the index is corrupted...
If you have a suggestion how to very easy store the objects, and possibility to replace the object with a new one or just update some properties of the object i would be very happy ;-)

So after long time of investigation I finally solved it 🙃🎉
The problem was that I show up the "Releases" in reversed order (I read out the Array from length to 0). I dont do this for the other categories. And this was the problem. Now I copy the data to read out with:
var releasesArray = JSON.parse(JSON.stringify(dbReleases.data)); and it works like a charm.
Thanks @obeliskos  for your thoughts and help!!!


#229 Explain repository compilation

Issues by #229
New for this PR:

Logging of compilation status
Short summary of compilation

@yegor256
Hi, could you take a look at this?
P.S. Idk why make-macos doesn't work...

@Raleksan thanks!


wen_restart: replace get_aggregate_result() with more methods

Since we only call LastVotedForkSlotsAggregate methods from a single thread, we don't actually need the LastVotedForkSlotsAggregateResult struct, we can just query the individual members separately.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.9%. Comparing base (b3fd87f) to head (309a7c8).

Additional details and impacted files
@@            Coverage Diff            @@
##           master     #254     +/-   ##
=========================================
- Coverage    81.9%    81.9%   -0.1%
=========================================
  Files         837      837
  Lines      226792   226789      -3
=========================================
- Hits       185795   185760     -35
- Misses      40997    41029     +32


omg help is not displayed unless the user is in the same dir as the executable

sandbox $ pwd
/home/ops

$ which omg-linux
/home/ops/bin/omg-linux

sandbox $ omg-linux -h
<nothing>

sandbox $ cd /home/ops/bin
sandbox $ omg-linux -h
NAME:
   omg-linux - A new cli application

USAGE:
   omg-linux [global options] command [command options] [arguments...]

VERSION:
   v1.0.3-572df1

COMMANDS:
     azure               azure [--flags] - deploy a bosh to azure
     aws                 aws [--flags] - deploy a bosh to aws
     gcp                 gcp [--flags] - deploy a bosh to GCP
     photon              photon [--flags] - deploy a bosh to photon
     vsphere             vsphere [--flags] - deploy a bosh to vsphere
     list-cloudconfigs
     list-products
     product-meta        product-meta <prod-name> - show product metadata
     register-plugin     register-plugin -type [cloudconfig, product] -pluginpath <plugin-binary>
     deploy-cloudconfig  deploy-cloudconfig <cloudconfig-name> [--flags] - deploy a cloudconfig to bosh
     deploy-product      deploy-product <prod-name> [--flags] - deploy a product via bosh
     help, h             Shows a list of commands or help for one command

GLOBAL OPTIONS:
   --help, -h     show help (default: false)
   --version, -v  print the version (default: false)

set the OMG_PLUGIN_DIR to whichever dir contains your plugins and you should be able to run omg-cli from anywhere.


The /edit?way=... does not pan/zoom the editor

A url for editing an object, such as /edit?way=... or /edit?relation=... do not pan or zoom the map in the editor. On the other hand, node=... works fine (as it is clearly much easier to position).
Originally reported at https://github.com/openstreetmap/openstreetmap-website/issues/1622

The same issue is observed when you click on an item in the search panel. Although it is not consitent - sometimes it pans to the object, sometime it just switches to it but does not pan the map.

This is quite a big issue since you have to search for an object twice to get to its geometry.

@yaugenka – good observation. It's very likely caused by the same issue in iD, which is that zoomToEntity doesn't properly take all the data it loads into account (e.g. the nodes of a way) to determine the extent/bbox to zoom to.

This is a duplicate of #4276


Fix balance_works() test across ERC20 code examples

balance_works() tests in 2.2-2.4 differed from corresponding test in 2.1 and failed since initial balance of contract instantiator should match total supply.

balance_works() tests in 2.2-2.4 differed from corresponding test in 2.1 and failed since initial balance of contract instantiator should match total supply.

Thank you for the PR!
@riusricardo We should finally update the contracts workshop. These tests are not respecting the current state of affairs.

Agree, is part of my pending tasks. I'll start working on it this week.


updates to workflow modules to support etpic196

https://github.com/cloud-native-toolkit/terraform-gitops-cp-datapower/issues/5

This PR is not required anymore. Deleting it.


KITE-1035 added kite configuration service for oozie to supplement the KiteURIHandler

https://issues.cloudera.org/browse/KITE-1035
Alternative implementation of the concept introduced first in pull #399
Sets the default configuration for kite to a list of configuration sources set at the property "oozie.service.KiteConfigurationService.kite.configuration"
(A consumer would also need to add the configuration service to the list of configurations specified for oozie under "oozie.services")

@rkanter @rdblue This is the branch with the Kite specific oozie configuration alternative to #399
It looks like the Flume tests bombed out on an OOM on the Travis build, it looks like #398 hit something similar, maybe the travis setup needs some adjustments?

Yeah, don't worry about the Flume test failure. I'll restart it but I doubt it's related.

I made a few minor comments.  Otherwise, that looks good to me.

Updates for Roberts comments are covered in 7061b11. Thanks @rkanter!

@rdblue Did we have anything else we wanted to look at with this PR before it gets merged in?

@bbrownz, I think we're ready to go. I've just been a bit swamped lately.

@rdblue no worries, just checking in to make sure I wasn't missing anything

+1 for merging.

@rdblue or @tomwhite  any objections to me merging this?

Nope, go for it!


GH-6: Dead Letter Queue Processing

Resolves #6

Need to add coverage for partitioned destinations.


Updated add and delete diagrams

Updated diagrams

For the Delete sequence diagram, is the parseAppointmentCommand from PlannerMdParser to AppointmentCommandParser missing? The activation bar also seems to be missing for AppointmentCommandParser.

yep you're right

Codecov Report

Merging #247 (37e3c30) into master (b7c675e) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #247      +/-   ##
============================================
- Coverage     80.43%   80.42%   -0.02%
  Complexity      988      988
============================================
  Files           146      146
  Lines          2842     2840       -2
  Branches        338      338
============================================
- Hits           2286     2284       -2
  Misses          478      478
  Partials         78       78

Impacted Files
Coverage Δ

...logic/commands/editcommand/EditPatientCommand.java
95.06% <0.00%> (-0.07%)
:arrow_down:

.../logic/commands/editcommand/EditDoctorCommand.java
96.00% <0.00%> (-0.06%)
:arrow_down:

Continue to review full report at Codecov.

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


Cuda functions treat *args as a normal parameter

Reporting a bug

[x] I have tried using the latest released version (53.1/97fe221b3704bd17567b57ea47f4fc6604476cf9) of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

When a cuda.jit function has *args parameter, it fails compilation with different errors, depending on how many arguments were passed.
This code:
from numba import cuda
import numpy as np

@cuda.jit()
def apply(array, *args):
    x = cuda.grid(1)
    if x < array.shape[0]:
        array[x] = args[0]

array = np.empty(128)

apply[8, 16](array, 2)

fails with

No implementation of function Function(<built-in function getitem>) found for signature:

>>> getitem(int64, Literal[int](0))

and when instead you call apply[8, 16](array, 2, 3), you get

Signature mismatch: 3 argument types given, but function takes 2 arguments

It appears as if the cuda pipeline just ignores the *, treating *args as a single parameter.
If it is for some reason not possible to correctly deal with this, I would at least expect a sane error message.

 Full tracback example one argument

Traceback (most recent call last):
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\test_cuda.py", line 12, in <module>
    apply[8, 16](array, 2)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 821, in __call__
    return self.dispatcher.call(args, self.griddim, self.blockdim,
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 964, in call
    kernel = _dispatcher.Dispatcher._cuda_call(self, *args)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 972, in _compile_for_args
    return self.compile(tuple(argtypes))
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 1093, in compile
    kernel = _Kernel(self.py_func, argtypes, link=self.link,
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_lock.py", line 35, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 509, in __init__
    cres = compile_cuda(self.py_func, types.void, self.argtypes,
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_lock.py", line 35, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 47, in compile_cuda
    cres = compiler.compile_extra(typingctx=typingctx,
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 606, in compile_extra
    return pipeline.compile_extra(func)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 353, in compile_extra
    return self._compile_bytecode()
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 415, in _compile_bytecode
    return self._compile_core()
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 395, in _compile_core
    raise e
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 386, in _compile_core
    pm.run(self.state)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_machinery.py", line 339, in run
    raise patched_exception
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_machinery.py", line 330, in run
    self._runPass(idx, pass_inst, state)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_lock.py", line 35, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_machinery.py", line 289, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_machinery.py", line 262, in check
    mangled = func(compiler_state)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\typed_passes.py", line 104, in run_pass
    typemap, return_type, calltypes, errs = type_inference_stage(
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\typed_passes.py", line 82, in type_inference_stage
    errs = infer.propagate(raise_errors=raise_errors)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\typeinfer.py", line 1071, in propagate
    raise errors[0]
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function(<built-in function getitem>) found for signature:

 >>> getitem(int64, Literal[int](0))

There are 22 candidate implementations:
  - Of which 22 did not match due to:
  Overload of function 'getitem': File: <numerous>: Line N/A.
    With argument(s): '(int64, int64)':
   No match.

During: typing of intrinsic-call at C:\Users\tramp\PycharmProjects\numba_render_engine\test_cuda.py (8)
During: typing of static-get-item at C:\Users\tramp\PycharmProjects\numba_render_engine\test_cuda.py (8)

File "test_cuda.py", line 8:
def apply(array, *args):
    <source elided>
    if x < array.shape[0]:
        array[x] = args[0]
        ^

 Full tracback example two arguments

Traceback (most recent call last):
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\test_cuda.py", line 12, in <module>
    apply[8, 16](array, 2, 3)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 821, in __call__
    return self.dispatcher.call(args, self.griddim, self.blockdim,
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 964, in call
    kernel = _dispatcher.Dispatcher._cuda_call(self, *args)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 972, in _compile_for_args
    return self.compile(tuple(argtypes))
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 1093, in compile
    kernel = _Kernel(self.py_func, argtypes, link=self.link,
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_lock.py", line 35, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 509, in __init__
    cres = compile_cuda(self.py_func, types.void, self.argtypes,
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_lock.py", line 35, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 47, in compile_cuda
    cres = compiler.compile_extra(typingctx=typingctx,
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 606, in compile_extra
    return pipeline.compile_extra(func)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 353, in compile_extra
    return self._compile_bytecode()
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 415, in _compile_bytecode
    return self._compile_core()
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 395, in _compile_core
    raise e
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 386, in _compile_core
    pm.run(self.state)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_machinery.py", line 339, in run
    raise patched_exception
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_machinery.py", line 330, in run
    self._runPass(idx, pass_inst, state)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_lock.py", line 35, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_machinery.py", line 289, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_machinery.py", line 262, in check
    mangled = func(compiler_state)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\untyped_passes.py", line 105, in run_pass
    raise TypeError("Signature mismatch: %d argument types given, "
TypeError: Failed in nopython mode pipeline (step: fix up args)
Signature mismatch: 3 argument types given, but function takes 2 arguments

Process finished with exit code 1

The errors get even more confusing when you try to call a device function. This code:
@cuda.jit(device=True)
def process(x, t):
    return t

@cuda.jit()
def apply(array, *args):
    x = cuda.grid(1)
    if x < array.shape[0]:
        array[x] = process(x, *args)

array = np.empty(128)

apply[8, 16](array, 2)

instead fails with

No implementation of function Function(<built-in function add>) found for signature:

 >>> add(UniTuple(int32 x 1), int64)

Full Traceback

Traceback (most recent call last):
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\test_cuda.py", line 27, in <module>
    apply[8, 16](array, 2)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 821, in __call__
    return self.dispatcher.call(args, self.griddim, self.blockdim,
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 964, in call
    kernel = _dispatcher.Dispatcher._cuda_call(self, *args)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 972, in _compile_for_args
    return self.compile(tuple(argtypes))
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 1093, in compile
    kernel = _Kernel(self.py_func, argtypes, link=self.link,
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_lock.py", line 35, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 509, in __init__
    cres = compile_cuda(self.py_func, types.void, self.argtypes,
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_lock.py", line 35, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\cuda\compiler.py", line 47, in compile_cuda
    cres = compiler.compile_extra(typingctx=typingctx,
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 606, in compile_extra
    return pipeline.compile_extra(func)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 353, in compile_extra
    return self._compile_bytecode()
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 415, in _compile_bytecode
    return self._compile_core()
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 395, in _compile_core
    raise e
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler.py", line 386, in _compile_core
    pm.run(self.state)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_machinery.py", line 339, in run
    raise patched_exception
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_machinery.py", line 330, in run
    self._runPass(idx, pass_inst, state)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_lock.py", line 35, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_machinery.py", line 289, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\compiler_machinery.py", line 262, in check
    mangled = func(compiler_state)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\typed_passes.py", line 104, in run_pass
    typemap, return_type, calltypes, errs = type_inference_stage(
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\typed_passes.py", line 82, in type_inference_stage
    errs = infer.propagate(raise_errors=raise_errors)
  File "C:\Users\tramp\PycharmProjects\numba_render_engine\venv\lib\site-packages\numba\core\typeinfer.py", line 1071, in propagate
    raise errors[0]
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
No implementation of function Function(<built-in function add>) found for signature:

 >>> add(UniTuple(int32 x 1), int64)

There are 12 candidate implementations:
  - Of which 2 did not match due to:
  Operator Overload in function 'add': File: unknown: Line unknown.
    With argument(s): '(UniTuple(int32 x 1), int64)':
   No match for registered cases:
    * (int64, int64) -> int64
    * (int64, uint64) -> int64
    * (uint64, int64) -> int64
    * (uint64, uint64) -> uint64
    * (float32, float32) -> float32
    * (float64, float64) -> float64
    * (complex64, complex64) -> complex64
    * (complex128, complex128) -> complex128
  - Of which 10 did not match due to:
  Overload of function 'add': File: <numerous>: Line N/A.
    With argument(s): '(UniTuple(int32 x 1), int64)':
   No match.

During: typing of intrinsic-call at C:\Users\tramp\PycharmProjects\numba_render_engine\test_cuda.py (23)

File "test_cuda.py", line 23:
def apply(array, *args):
    <source elided>
    if x < array.shape[0]:
        array[x] = process(x, *args)
        ^

I can reproduce the tracebacks. Presently CUDA doesn't support *args, and it would be better for the use of it to be caught and a helpful error message presented.


Crash Report: update failed for AnAction(nl.rubensten.texifyidea.action.sumatra.ForwardSearchAction) with ID=texify.sumatra.ForwardSearch

Description
Stacktrace
Please paste the full stacktrace from the IDEA error popup

Fixed in PR #443 and will be included in release b0.6.1 in the near future.


Hide config.ini in release zip

If you put the provided code directly into a directory served by NGINX (and possibly Apache), files like the config.ini get exposed, which can reveal information about your system.  You should put the PHP scripts under a directory like html in the distribution, and keep files that aren't intended to be served in the root directory, like config.ini, README.md, and so on.

I just saw that you have config.ini blocked in the htaccess file.  NGINX doesn't use htaccess which is why I saw this problem.  I'll close the issue.


duration ignored when passed to Action

Is it possible to change duration after Scene is defined?
For example, I want to set push transition to not have animation and pop to have
I have tried to pass duration to Actions.pop and that does not work
// Scene is defined something like this
 <Scene
    type={ActionConst.PUSH}
    direction="vertical"
    duration={0}
    key="article"
    component={ArticlePage}
    panHandlers={null}
/>

Actions.pop({ duration: 1000 }})

is something like that possible
Version
Tell us which versions you are using:

react-native-router-flux v3.?.?
react-native v0.36.0

Expected behaviour
When provided duration to Actions.pop it should use that duration no the one defined.
Actual behaviour
duration is ignored when passed to the Actions.pop

+1


Visual Studio code sidebar Vertical guideline (customize sidebar)

VSCode Version: 1.7.2
OS Version: windows 7

Steps to Reproduce:
I want vertical guideline on sidebar (for file and folders) like netbeans.
any issue for that?

I asked it on http://stackoverflow.com/questions/41898245/visual-studio-code-sidebar-vertical-guideline-customize-sidebar.
but nothing.

I don't known of an existing request. By the way, 1.7.2 is an old version, we're about to ship 1.10. You should consider updating :)

Dup is here: https://github.com/Microsoft/vscode/issues/17777

Thanks @kaiwood

Both this and the duplicate #17777 were closed, so I guess this is dead. I'm pretty sure there was an update to the three recently, but it would be nice if there were a config value to increase the indent. I don't really need tree lines, but more indent would be great.


fix: Upgrade pyproj and scikit-image

Codecov Report

Merging #7 (8c5c68c) into main (98fe893) will increase coverage by 9.43%.
The diff coverage is n/a.

:exclamation: Current head 8c5c68c differs from pull request most recent head 372ceb9. Consider uploading reports for the commit 372ceb9 to get more accurate results

@@            Coverage Diff             @@
##             main       #7      +/-   ##
==========================================
+ Coverage   72.12%   81.55%   +9.43%
==========================================
  Files         215      187      -28
  Lines        4366     3552     -814
  Branches      145        0     -145
==========================================
- Hits         3149     2897     -252
+ Misses       1181      655     -526
+ Partials       36        0      -36

Impacted Files
Coverage Δ

components/home/HomeContent.js

pages/_app.js

utils/file-download.js

components/home/MapsContent.js

components/home/DashboardsContent.js

components/SelectProjectButton.js

utils/analytics/dev.js

pages/home.js

pages/login.js

utils/ga.js

... and 18 more

Continue to review full report at Codecov.

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


python310Packages.monty: 2022.1.19 -> 2022.3.12

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.monty is: "Serves as a complement to the Python standard library by providing a suite of tools to solve many common problems"
meta.homepage for python310Packages.monty is: "https://github.com/materialsvirtuallab/monty"
meta.changelog for python310Packages.monty is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2022.3.12 with grep in /nix/store/rad1blm5q6mbcmf8acnfs7dp44ydx0pz-python3.10-monty-2022.3.12

found 2022.3.12 in filename of file in /nix/store/rad1blm5q6mbcmf8acnfs7dp44ydx0pz-python3.10-monty-2022.3.12

Rebuild report (if merged into master) (click to expand)

20 total rebuild path(s)

10 package rebuild(s)

10 x86_64-linux rebuild(s)
10 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
python310Packages.castepxbin
python310Packages.monty
python310Packages.pymatgen
python310Packages.pymatgen-lammps
python310Packages.sumo
python39Packages.castepxbin
python39Packages.monty
python39Packages.pymatgen
python39Packages.pymatgen-lammps
python39Packages.sumo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rad1blm5q6mbcmf8acnfs7dp44ydx0pz-python3.10-monty-2022.3.12 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.monty https://github.com/r-ryantm/nixpkgs/archive/403cdb3e9f202b5cf1ae97921a0b3540eb6b7b6b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rad1blm5q6mbcmf8acnfs7dp44ydx0pz-python3.10-monty-2022.3.12
ls -la /nix/store/rad1blm5q6mbcmf8acnfs7dp44ydx0pz-python3.10-monty-2022.3.12/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages marked as broken and skipped:

python310Packages.pymatgen-lammps
python39Packages.pymatgen-lammps

8 packages built:

python310Packages.castepxbin
python310Packages.monty
python310Packages.pymatgen
python310Packages.sumo
python39Packages.castepxbin
python39Packages.monty
python39Packages.pymatgen
python39Packages.sumo

Maintainer pings
cc @PsyanticY for testing.

Pypi already on 2022.04.26


Make partition_slice available

This was missing when experimenting with
combinations of process_tile() and postprocess() for SSB.
The correctness of the partition slice is mostly tested within the coordinate calculations already.
Basic correspondence check added as well.
This is based on #1197 for changelog purposes.
Contributor Checklist:

[x] I have added or updated my entry in the creators.json file
[x] I have added a changelog entry for my contribution
[x] I have added/updated documentation for all user-facing changes
[x] I have added/updated test cases
[N/A] I have included the rebuilt production build of the client (only if changes were made to the GUI)

Reviewer Checklist:

[ ] /azp run libertem.libertem-data passed

The test case fails, actually: Despite using process_partition(), the tile has the shape specified when creating the memory data set.
What is the correct behavior here? Feeding a tile that doesn't have the shape of the partition into process_partition() smells like a bug. Probably LiberTEM internals should raise an exception of the dataset produces a wrong kind of tile?

The test case fails, actually: Despite using process_partition(), the tile has the shape specified when creating the memory data set.
What is the correct behavior here? Feeding a tile that doesn't have the shape of the partition into process_partition() smells like a bug. Probably LiberTEM internals should raise an exception if the dataset produces a wrong kind of tile?

 Adding a per-partition check for this sounds good to me.
Generally on the PR, I think we need to discuss this still: as we discussed today actually, it would be nice to allow for partitions to span arbitrary ROIs (probably even weirdly structured/interlaced - not directly describable by a flattened slice) instead of only slices. I agree that the the functionality in general needs to be there, but we may want to have a different interface actually.
Can we maybe postpone this to 0.10?

Ok, that's a good point. Probably a "partition ROI". Feels similar to #764, actually!

Ok, that's a good point. Probably a "partition ROI". Feels similar to #764, actually!

Indeed that's very similar :)

Discussion with @sk1p : It boils down if self.meta.coordinates is available in get_task_data(), preprocess() and postprocess(). This would be a natural source of information on both the partition size and the position of parts of the partition within the dataset.

Closing in favor of #1397


Add verifying paymaster

To let tests pass, it requires settings in https://github.com/pilagod/waallet-contract/pull/20

Summarizing my observations:

Set the paymaster implementation during WaalletBackgroundProvider setup, allowing userOp transactions with configured paymasterAndData to have gas fees paid by the paymaster contract.
The paymaster implementation must include the requestPaymasterAndData() function, providing the paymaster owner's private key for signing the signature with address, validAfter, validUntil, and isGasEstimation data.
Following Alchemy bundler's rules, use a specified dummy signature for gas estimation.


added users,pets and breeds into configtest and tests for breeds endp…

added pets,users and breeds in configtest and tests for breed's endpoints

 Add test for breeds endpoints

 Add test for pets and breeds endpoints

 fix pet's permissions, simple user don't need to have acces to all pets


Improve system contract loading reliability

@thekevinbrown Are you guys still maintaining this. Just wondering if I should just use my own fork if you have moved on to different projects now.

@dallasjohnson, yes, we're still maintaining this, sorry for the delay. I'll have a look today.

Just wanted to let you know that this has been released (along with a bunch of dependency updates) in<EMAIL_ADDRESS>


Enable --styleCheck for nim compilation

As more people are working on the client, it would be nice to have some level of style consistency across the codebase, --styleCheck is a way towards that. It should catch things like lower/upper case inconsistencies (nim is case insensitive 😱) and other issues, but it's not a full fledged linter by any means...

I made a branch 'enable-stylecheck' and gave this a try. (I didn't push it yet.)
I've set '--styleCheck:error' in the config.nims and set about fixing all the issues. Pretty soon it was reporting mistakes in the vendor directory. According to Tanguy, this directory should be excluded by default on the right nim version. There's a backport for this functionality for 1.6 which, I think we have:
Added here:
https://github.com/nim-lang/Nim/pull/19822

Backport to 1.6 is here:
https://github.com/nim-lang/Nim/commit/c484943cab39c2aa876253cf09493679df3d6226

Yet it seems likely that generics/templates in external modules may still cause trouble. How shall we proceed? We can set the styleCheck to warn, ignore the ones from vendors, but that's a good chance we'll overlook them in the terminal output.

I made a branch 'enable-stylecheck' and gave this a try. (I didn't push it yet.) I've set '--styleCheck:error' in the config.nims and set about fixing all the issues. Pretty soon it was reporting mistakes in the vendor directory. According to Tanguy, this directory should be excluded by default on the right nim version. There's a backport for this functionality for 1.6 which, I think we have:
Added here:
https://github.com/nim-lang/Nim/pull/19822

Backport to 1.6 is here:
https://github.com/nim-lang/Nim/commit/c484943cab39c2aa876253cf09493679df3d6226

Yet it seems likely that generics/templates in external modules may still cause trouble. How shall we proceed? We can set the styleCheck to hint, ignore the ones from vendors, but that's a good chance we'll overlook them in the terminal output.

I would use the backport to do the initial cleanup with --styleCheck:error, locally on your machine and would leave it on hint in our builds for now.
One of two things will happen (or both) - either the backport makes it into some stable version (if it haven't already) or, we move away from the vendors directory once the nimble lock file mechanism is stable and we can use that instead of the makefile/vendor setup...

I managed to clean the style errors out of the codebase, and work around the errors coming from the vendor directory.
https://github.com/status-im/nim-codex/pull/353
Plan: Merge this. Rebase block-maintenance PR. Fix style errors for the new changes. Merge that.
Having to work around the vendors folder means not using the make commands but the nim commands directly, and then commenting out / changing the style errors in the vendors folder to get compilation to continue. The modifications don't have to work, they just have to compile so we can find the style errors in the non-vendor code.

Having to work around the vendors folder means not using the make commands but the nim commands directly,

Not sure what you mean by this, can you please elaborate?


Trying to uncomment a block uncomment another one on the same line

Steps to reproduce:

Write /*test1*/ code /*test2*/
Put cursor inside the second block comment (in test2)
Use block-comment-plus:toggle
I get test1 code /*test2*/

Hi @ariasuni
I don't use atom anymore so I don't plan to maintain this package, sorry.


PortFolio Optimaization Using Genetic ALgorithm added

#968 resolved

@ashis2004 good work ,just we are expecting EDA before using data for models

And add results in readme.md file


Bad SQL adapter introspection of an empty database

EdgeDB Version: 6.0-dev

Init a new, empty database.
pg_dump "sslmode=require host=localhost port=5656 user=edgedb" > dump.sql

pg_dump: error: schema with OID 163001966 does not exist

This happens because pg_class contains the made-up pg_namespace OIDs, which are needed for pg_class row for "global types", such as tuple<std::int64, std::int64>.
SQL adapter exposes tables for object types (and links) in a separate schemas, but those schemas don't exist in the backing PostgreSQL. So we must generate OIDs for such namespaces.
Now, when database is empty, virtual_tables is empty (as there is no virtual tables), but we still expose all tuple types in pg_class. These rows are the ones that contain the invalid oid-s.

Initially I wanted to just file this and forget about it, but when writing this report I think I figured out how to fix it.
This comment will be quite embarrassing if I did not in fact figure it out and so this issue will remain open for months :D


Yet Another _Ember is undefined error

Before opening this i removed node_modules and yarn.lock so the environment was as clean as possible, just to confirm it was still an issue.
yarn why ember-cli-babel | grep @7
=> Found<EMAIL_ADDRESS>=> Found<EMAIL_ADDRESS>=> Found<EMAIL_ADDRESS>=> Found<EMAIL_ADDRESS>=> Found<EMAIL_ADDRESS>=> Found<EMAIL_ADDRESS>=> Found<EMAIL_ADDRESS>=> Found<EMAIL_ADDRESS>
yarn why babel-plugin-ember-modules-api-polyfill | grep @2
=> Found<EMAIL_ADDRESS>=> Found<EMAIL_ADDRESS>
Still getting Uncaught ReferenceError: _Ember is not defined
From the stack, it looks to be coming out of ember-concurrency
Pre-transpiled
state: computed('isDropped', 'isCanceling', 'hasStarted', 'isFinished', function() {
    if (get(this, 'isDropped')) {
      return 'dropped';
    } else if (get(this, 'isCanceling')) {
      return 'canceled';
    } else if (get(this, 'isFinished')) {
      return 'finished';
    } else if (get(this, 'hasStarted')) {
      return 'running';
    } else {
      return 'waiting';
    }
  }),

Transpiled
state: (_Ember = Ember).computed.apply('isDropped', 'isCanceling', 'hasStarted', 'isFinished', function () {
      if (Ember.get(this, 'isDropped')) {
        return 'dropped';
      } else if (Ember.get(this, 'isCanceling')) {
        return 'canceled';
      } else if (Ember.get(this, 'isFinished')) {
        return 'finished';
      } else if (Ember.get(this, 'hasStarted')) {
        return 'running';
      } else {
        return 'waiting';
      }
    }),

This looks like exactly the thing that was fixed by 7.20.5 (via babel-plugin-ember-modules-api-polyfill@2.13.4).
@cah-timhuddle:

Can you rm -rf node_modules && yarn, then double check the transpiled results? (this is to try and ensure we aren't using a pre-cached transpilation result from a prior ember-cli-babel version)
Can you identify if there any other computed usages in this file? If so, what do they look like?

So, to be specific this file is here (I have nothing to do w/ ember-concurrency, we just use it). Looks like there's a couple other computeds in there like isDropped and a few others that aren't dependencies of state
After running rm -rf node_modules && yarn, the output from the two yarn why commands was identical.
Ran a yarn build instead of yarn start this time, just to make it easier to look at the transpiled output.
All of the output looks just like reported above.

Huh, so i tried to make the smallest possible repro, and when i go looking at that compiled code, it appears to be fixed. So its something weird in our repo (which is private and so cannot be shared).
FWIW, we're on Ember 3.0.4, but this would appear to actually indeed be "fixed" in a sane environment.

@cah-timhuddle - Are there any<EMAIL_ADDRESS>instances in use (anything over<EMAIL_ADDRESS>would get the "bad" babel-plugin-ember-modules-api-polyfill versions)?

Hoo boy, there's a whole bunch of 6.18.0's (like 30+) and also a few 5.2.8's.

You should be able to ensure that<EMAIL_ADDRESS>gets the fixed version of babel-plugin-ember-modules-api-polyfill.

I think this is fixed now (for a while), closing...


Code42 label currently installing older version due to URL change by devs

Currently, these links below from the C42 label:
https://download.code42.com/installs/agent/latest-mac.dmg
https://download.code42.com/installs/agent/latest-mac-arm64.dmg
Are not downloading the recently released version, 10.0. Code42 Representatives in the macadmins slack channel have stated the paths have been changed for the 10.0 release and there is currently not an updated "latest" link yet. They hope to provide one sometime.

It would appear both of the "legacy" URL's are offline so this workflow is no longer working. Has there been any update on new "latest" URL's from Code42?

I think we're going to have to remove the label.

I tested the script locally using the following URL: https://download.crashplan.com/installs/agent/latest-mac.dmg. This link downloaded version 10.4.  Replacing it in the Installomator script successfully downloaded and installed the application.

crashplan split off from code42 a few months back, they're separate products now so that link unfortunately doesn't point to the right installer called out in this issue.

Hi all, I'm an employee over at CrashPlan weighing in to try and help disambiguate things just a tad.
We at CrashPlan did split off from Code42 a few months ago. We also just released our version 11 app which is branded CrashPlan and so should make things a bit clearer moving forward. At this point we should have three different labels for CrashPlan/Code42. I can't fully comment on the Code42 piece since I am not employed by Code42.

A Code42 label, the one currently in place I suspect will work great.
https://github.com/Installomator/Installomator/blob/main/fragments/labels/code42.sh

A CrashPlan label. Built like this:

crashplan)
    name="CrashPlan"
    type="pkgInDmg"
    downloadURL="https://download.crashplan.com/installs/agent/latest-mac.dmg"
    expectedTeamID="UGHXR79U6M"
    blockingProcesses=( NONE )
    ;;

A CrashPlan small business label as discussed in this pull request. That will have a similar download URL, and team ID as the main CrashPlan one.
https://github.com/Installomator/Installomator/pull/931

None of the URLs are pointing to v12 of the installer which is what we require since they separated the AAT from the backup agent.

Any Code42 users know if this label can be updated for version 12 and beyond? Otherwise we may need to remove the label in a future release.

It looks like they're still using a dynamic URL per version, I think at this point it's best the label is removed and if this ever changes myself or someone can put in a PR to add it back.

Changing Issue topic now to depreceate.

Fixed in #766 (Excuse the lateness, doing some housekeeping on Issues)


Explore view save modal spec

add unit tests for Explore view saveModal. These tests are based on sliced reducer (saveModalReducer).

Coverage remained the same at 69.311% when pulling b6da30f4a7d8eb9a9c27a62c7229deb2ddb4708b on graceguo-supercat:gg-ExploreViewSaveModalSpec into f68189b54e0bc6467bf46ffb33b5cc4848a2a582 on apache:master.

Coverage remained the same at 69.311% when pulling b6da30f4a7d8eb9a9c27a62c7229deb2ddb4708b on graceguo-supercat:gg-ExploreViewSaveModalSpec into f68189b54e0bc6467bf46ffb33b5cc4848a2a582 on apache:master.

LGTM, want me to merge it since you don't have write access [yet]?

Coverage remained the same at 69.315% when pulling 8fa7db8fa53c2a0b9f1855ce39563dccef0895fe on graceguo-supercat:gg-ExploreViewSaveModalSpec into b3107bb603d2ddae38fec97d81878b2dae339624 on apache:master.


kotlin: support postgresql uuid

Support for UUID type in Kotlin.

@mightyguava Can you review these changes?

@eivindr Sorry this has languished for so long. I was hoping that @mightyguava could give it a review. If the tests pass after rebasing, I'm going to merge this in.


Queries returning more than 1024 results overflow the buffer

user=> (qq '[:find ?x :in $ :where [?x _ _]])
[nil
 #<java.lang.AssertionError@5414ad44 java.lang.AssertionError: Assert failed: No more than 1024 pending puts are allowed on a single channel. Consider using a windowed buffer.

Bulk-closing ClojureScript/Datomish tickets.


click.Date

click.DateTime is great, and you can use click.DateTime(formats=["%Y-%m-%d"]) to ensure that the value is logically just a date. However, the resulting object is still a datetime.datetime, which isn't ideal if you want to be dealing with pure dates.
Right now I'm working around this by using a click.DateTime() argument and doing start_date = start_date.date() at the top of my function, but that's not ideal because my team considers variable reassignment to be a code smell. I could rename the argument to something else, but that's also something of a kluge.
It'd be great to have a click.Date argument type that would act similarly to click.DateTime and return a date only.

You're welcome to create a custom type that returns what you need. However, dates with no time or timezone information are very ambiguous, and it's best to avoid them. I don't plan to add this directly to Click.


Home Assistant Cannot Set Brightness with Color

In attempting to turn on my light with Home Assistant I cannot seem to set color in conjunction with brightness
Device Info:
"category": "dj",
"product_id": "6cej2z4aazmtrvge",
"product_name": "Color Light",

service: light.turn_on
target:
  entity_id: light.mike_light_none
data:
  rgb_color:
    - 255
    - 0
    - 0
  # brightness_step_pct: 100
  brightness: 100

Will result in the light turning to the last form of "white" (daylight, candlelight, etc...) and 100% brightness.  I expected it to turn 100% brightness and Red in color. brightness_step_pct also does not work.
I also attempted to make this change via scenes within HA - that also failed.

Same issue here, cannot set brightness on any of my dimmers.
It works from the Smart Life app, but not through the integration.

Update to this: I'm not completely crazy. Tonight I took a brand new bulb and set up a scene with it.
I set it to give me orange (255, 127, 0) at 1% and clicked Save. During that time - the bulb actively responded correctly.
As soon as I exited out of the editor and clicked "Activate" on that scene - it only dimmed - but maintained the same default "white" it was on.


Cocoapod installation error

Trying to install via cocoa pods and getting this error:
[!] Unable to satisfy the following requirements:
- `MGSwipeTableCell (= 1.3.6)` required by `Podfile`

Podfile looks like this:
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, "7.0"
pod "MGSwipeTableCell", "1.3.6"
...other pods...

Don't have any problems with the other pods, just this one. Any suggestions?

Changed the version to 1.3.5 and it installed ok. But your pod spec has the version set to 1.3.6. Can you update?

I have just pushed 1.4.0 to cocoapod. Try with that version ;)

Cool, worked! Thanks for the prompt response and update! Cheers! :+1:


Query recommendations based on user id

As a Marketing Manager
I need the ability to query for recommendations assigned to particular users
So that I collect data and perform action routes
Details and Assumptions

We will employ PostgreSQL
Assuming List API is already implemented

Acceptance Criteria
Given our service is running
When I search for recommendations querying based on particular user ID
Then the user's recommendations are returned

This was done as part of #8 in sprint1.

Also handled the wrong data type in query parameters in the new PR.


Add support for detecting and preserving different newline types

I think this should resolve #61.  Same problem with duplicate implementations as with encoding, only slightly worse because the newline detection logic will always run twice.  Should only result in a single wasted re.search scan over the first line of the file.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

11 of 12 (91.67%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.06%) to 98.122%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/ssort/_utils.py
7
8
87.5%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
1254

Relevant Lines:
1278

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

23 of 23 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 98.214%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
1265

Relevant Lines:
1288

💛  - Coveralls


[BUG]  Chain Tool and LLM Chain not working together.

Hi everyone! I'm working on developing a chatbot capable of validating users' identity documents or passports. Users will be able to upload images of their documents or enter their data manually, which will then be validated.
To solve this problem, I wanted to create a structure composed of multiple specialized agents that collaborate with each other.
The first agent I'm developing is dedicated to collecting data from an ID card via image or text. The agent should guide the user through the chat, first asking them to upload the image of the front of the document, followed by the back, or to manually enter all the data.
Once the agent has obtained all the data from both the front and back, it should be able to return a message with a JSON containing the collected data.
I've created the following flow to represent this structure:
I have a chain that, through Claude, extracts all the information from the received images in JSON format. I’ve linked this chain to a Chain Tool called 'OCR - info', which is available to a Conversational Agent with the following prompt:
'''
Sei un assistente virtuale incaricato di estrarre i dati dell'utente dalla sua carta d'identità. Richiedi all'utente di caricare le immagini del fronte e del retro del documento. Usa l'apposito tool per estrarre le informazioni e ritornale sotto formato json, se qualche dato risulta illeggibile, etichettalo come NULL. Mantieni sempre un tono professionale e cortese e non rispondere a domande fuori contesto.
'''
Executing this flow always returns an error. I’ve tested the Chain on its own, and it works, but it seems there is an issue with passing information between the Chain Tool and the LLM Chain.
The prompt for the chain is as follows:
'''
Sei responsabile dell'analisi dei documenti di identità degli utenti e dell'estrazione di tutti i dati dall'immagine del documento. Non inventare MAI alcun dato. Se l'immagine non contiene un documento di identità, restituisci un JSON vuoto.
'''
I'm attaching the JSON of the chat flow and the image.
Can anyone help me figure out what's going wrong?
Thank you so much!
Image Retriver Agent_2.json

I think there are some known issues connecting LLMChain to ChainTool. A workaround is to create a separate sub-chatflow, and use Custom Tool/Chatflow Tool to connect to main flow. https://docs.flowiseai.com/use-cases/calling-children-flows


Use bootstrap's dismissible alerts

I'm thinking we could try and use bootstrap's dismissible alerts when using allow_dismiss
The html changes should be small and the changing position of the close button won't be necessary
to keep styling concise with bootstrap.
Thinking we can use 'close.bs.alert' and 'closed.bs.alert' events to handle logic when dismissed
i.e. change position of other alerts on close.
What do you think? is it worth spending time on a PR?

Closing this for now, I'll reopen if I feel there's a need for it.


rename SO compatibility job

as per title

/cherrypick release-v1.2

/cherrypick release-v1.1

/lgtm


Support retention policy

how long to keep data of a given entity and at which resolution?
e.g. after 1 year, I may be happy to keep instead of all data, only interpolation of data for 1h or so.

Brainstorming, this could be configured:

In the configuration file mentioned in #10
In the NGSI notification (but NGSI currently does not support this)
Configurable via protected API?

ngsi now supports 'dateExpires': http://fiware.github.io/specifications/ngsiv2 (so it's in the entity not in the subscription)
I propose then to have two ways:

leverage this attribute (if it exists)
have a default set-up via config file (that should be also the case for #10 )
configure it via API entity by entity (or entity type) of course using the tenant split

as far as I can tell, this has never been implemented? but should this functionality be in QL or rather a DB admin task?

i think, considering that timescale supports that, this is a more db specific thing


Can't use the "old data" to train alexnet.

I use the mxnet with "dmlc-core/src/io/input_split_base.cc" updated to train an alexnet model.
The data is packed with the old version mxnet's "im2rec.cc" which work well on the old version mxnet.
But when I try to use the new version mxnet to train the model, there are some errors occur.

./dmlc-core/include/dmlc/logging.h:241: [00:20:36] src/io/input_split_base.cc:157: Check failed: (files_.size()) != (0) Cannot find any files that matches the URI patternz /data/train.rec

What should I do to solve this problem?
Thanks a lot.

your path is '/data/train.rec'.
Try removing the leading '/' if it's not intended.

Thanks for your reply. This is not the problem. I just write '/data/train.rec' to indicate my data-dir.


BG deployment is not successful

Description
Hi all,
In my space, I have an application named "portal-cf-technical-support"
I am doing BG deployment with Piper step in order to deploy a newer version of it by:
deployToCloudFoundry( script: this, deployTool: 'mtaDeployPlugin', deployType: blue-green, mtaDeployParameters: '-f', cfApiEndpoint: api, cfOrg: org, cfSpace: space, cfCredentialsId: deployUser, mtaPath: pathToFile, mtaExtensionDescriptor: 'mta.mtaext')
after deployment is done, i see 2 versions of the application.
the original one named "portal-cf-technical-support" and another one named "portal-cf-technical-support-green" with almost same url but with postfix "idle"
I would expect that after deployment is done, i would have only the new version deployed with the original name.
Your environment
Listing installed plugins...
plugin              version   command name                 command help
blue-green-deploy   1.3.0     blue-green-deploy, bgd       Zero-downtime deploys with smoke tests
MtaPlugin           2.0.0     bg-deploy                    Deploy a multi-target app using blue-green deployment
MtaPlugin           2.0.0     deploy                       Deploy a new multi-target app or sync changes to an existing one
MtaPlugin           2.0.0     download-mta-op-logs, dmol   Download logs of multi-target app operation
MtaPlugin           2.0.0     mta                          Display health and status for a multi-target app
MtaPlugin           2.0.0     mta-ops                      List multi-target app operations
MtaPlugin           2.0.0     mtas                         List all multi-target apps
MtaPlugin           2.0.0     purge-mta-config             Purge no longer valid configuration entries
MtaPlugin           2.0.0     undeploy                     Undeploy a multi-target app
Steps to reproduce
In jenkins job login to your cf space, clone the mtar application and use Piper:
deployToCloudFoundry( script: this, deployTool: 'mtaDeployPlugin', deployType: blue-green, mtaDeployParameters: '-f', cfApiEndpoint: api, cfOrg: org, cfSpace: space, cfCredentialsId: deployUser, mtaPath: pathToFile, mtaExtensionDescriptor: 'mta.mtaext')
Additional information
This is the console output:
[deployToCloudFoundry] Deploying MTA (target/portal-cf-technical-support.mtar) with following parameters: -e mta-prod.mtaext -f
[Pipeline] sh
[GRADLE-DEPLOY-portal-cf-technical-support-i066861-gradle-dsl] Running shell script
API endpoint: https://api.cf.sap.hana.ondemand.com
Authenticating...
OK
Targeted org SAP_PORTAL_SERVICES
Targeted space val
API endpoint:   https://api.cf.sap.hana.ondemand.com (API version: 2.120.0)
User:           ****
Org:            SAP_PORTAL_SERVICES
Space:          val
Listing installed plugins...
plugin              version   command name                 command help
blue-green-deploy   1.3.0     blue-green-deploy, bgd       Zero-downtime deploys with smoke tests
MtaPlugin           2.0.0     bg-deploy                    Deploy a multi-target app using blue-green deployment
MtaPlugin           2.0.0     deploy                       Deploy a new multi-target app or sync changes to an existing one
MtaPlugin           2.0.0     download-mta-op-logs, dmol   Download logs of multi-target app operation
MtaPlugin           2.0.0     mta                          Display health and status for a multi-target app
MtaPlugin           2.0.0     mta-ops                      List multi-target app operations
MtaPlugin           2.0.0     mtas                         List all multi-target apps
MtaPlugin           2.0.0     purge-mta-config             Purge no longer valid configuration entries
MtaPlugin           2.0.0     undeploy                     Undeploy a multi-target app
Use 'cf repo-plugins' to list plugins in registered repos available to install.
Deploying multi-target app archive target/portal-cf-technical-support.mtar in org SAP_PORTAL_SERVICES / space val as ****...
Aborting multi-target app operation with id 426415992...
OK
Uploading 1 files...
/home/jenkins/workspace/deployServiceJobs-i066861-gradle-dsl/GRADLE-DEPLOY-portal-cf-technical-support-i066861-gradle-dsl/target/portal-cf-technical-support.mtar
OK
Uploading 1 files...
/home/jenkins/workspace/deployServiceJobs-i066861-gradle-dsl/GRADLE-DEPLOY-portal-cf-technical-support-i066861-gradle-dsl/mta-prod.mtaext
OK
Starting deployment process...
OK
Monitoring process 427998041...
Validating parameters...
Processing MTA archive...
Processing MTA extension descriptors...
Detecting MTA major schema version...
MTA schema version: 3.1.0
Detecting deploy target...
Detected deploy target "SAP_PORTAL_SERVICES val"
Validating and merging descriptors...
Detecting deployed MTA...
No deployed MTA detected
Collecting system parameters...
New MTA version: 2.10.0-20181003140145+b39ccc1495f2101159987b982aa0693b6252459c
Building cloud deployment model...
Building cloud undeployment model...
Validating services to create...
Validating applications to deploy...
Deleting unused reserved routes...
Creating or updating services...
Preparing applications deployment...
Building cloud deployment model for application "portal-cf-technical-support"...
Checking application "portal-cf-technical-support"...
Application "portal-cf-technical-support" does not exist
Creating application "portal-cf-technical-support"...
Uploading application "portal-cf-technical-support"...
Matched files count: 112
Matched resources processed, total size is 9,943,750
Upload status: queued
Upload status: running
Upload status: running
Upload status: running
Upload status: running
Application "portal-cf-technical-support" uploaded
Scaling application "portal-cf-technical-support"...
Upload status: finished
Starting application "portal-cf-technical-support"...
Application "portal-cf-technical-support" staged
1 of 1 instances running (1 running)
Application "portal-cf-technical-support" started and available at "https://portal-cf-technical-support-val.cfapps.sap.hana.ondemand.com"
Publishing public provided dependencies for application "portal-cf-technical-support"...
Building cloud deployment model for application "portal-cf-health-check"...
Checking application "portal-cf-health-check"...
Application "portal-cf-health-check" does not exist
Creating application "portal-cf-health-check"...
Uploading application "portal-cf-health-check"...
Matched files count: 106
Matched resources processed, total size is 7,653,833
Upload status: queued
Upload status: running
Upload status: running
Upload status: running
Upload status: running
Application "portal-cf-health-check" uploaded
Scaling application "portal-cf-health-check"...
Upload status: finished
Starting application "portal-cf-health-check"...
Application "portal-cf-health-check" staged
1 of 1 instances running (1 running)
Application "portal-cf-health-check" started and available at "https://portal-cf-health-check-val.cfapps.sap.hana.ondemand.com"
Publishing public provided dependencies for application "portal-cf-health-check"...
Building cloud deployment model for application "portal-cf-technical-support-ar"...
Checking application "portal-cf-technical-support-ar"...
Application "portal-cf-technical-support-ar" does not exist
Creating application "portal-cf-technical-support-ar"...
Uploading application "portal-cf-technical-support-ar"...
Matched files count: 116
Matched resources processed, total size is 12,826,544
Upload status: queued
Upload status: running
Upload status: running
Upload status: running
Upload status: running
Upload status: finished
Application "portal-cf-technical-support-ar" uploaded
Scaling application "portal-cf-technical-support-ar"...
Starting application "portal-cf-technical-support-ar"...
Application "portal-cf-technical-support-ar" staged
0 of 1 instances running (1 starting)
1 of 1 instances running (1 running)
Application "portal-cf-technical-support-ar" started and available at "https://portal-cf-technical-support-ar-val.cfapps.sap.hana.ondemand.com"
Publishing public provided dependencies for application "portal-cf-technical-support-ar"...
Creating subscriptions...
Registering service URLs...
Deleting discontinued subscriptions...
Deleting discontinued published dependencies...
Unregistering discontinued service URLs...
Creating service brokers...
Updating subscribers...
Process finished.
Use "cf dmol -i 427998041" to download the logs of the process.

Hello and thanks for being patient with the response.
The given output seems to be of a 'cf deploy ...' process which explains the version having no '-color' or '-idle' suffix to the app-name/route. The other version is created via a 'cf bg-deploy' execution. During the first phase of the bg-deployment (before the switch to a new version) a new version of the mta is spun-up on temporary (-idle) routes. You seem to have seen that state of your space.
The blue-green deploy process continues with mapping the 'live' routes new (-color) apps, the old apps get deleted as well as the '*-idle' routes.
Indeed, after a successfully bg-deploy process, there should be only one version of the app in the space. It should have a color suffix (e.g. -blue) and should have normal routes (not having -idle suffix).
Most probably in the current case the blue-green deployment was ongoing or has stopped due to an error before reaching the 'switch'.


Question on Lua Not Equal and For, and UTurns

I have read https://www.moonsharp.org/moonluadifferences.html and cannot seem to find any reference to != vs ~=. See also https://stackoverflow.com/questions/34713203/what-does-lua-operator-mean/34713230
Can you point me to the documentation where you figured that out? Also would ~= be any faster / better?

Also wondering on the looping of the vehicle types, there seems to be a basic for loop in most of the profiles: https://github.com/itinero/routing/blob/develop/src/Itinero/Osm/Vehicles/car.lua#L117
I am wondering if it would be more efficient / better to use for ... in ... especially for cases when there are less than 10 keys.

I have made the change locally to use for in and it seems to work just as well... I have not played with the != stuff yet.
I do however have one last question about the LUA while your here...
Looking at the profiles I can't really determine how turn cost is calculated via the profile.
I have a few scenarios where the route doubles back or it looks like U turn is performed, I can post a few samples if you need.
In these cases we know the train did not do a U turn so I am wondering how easy it would be to disable U turns via the profile...
I was thinking I could modify the is_oneway function to always return true? But I have not tested it yet because I been working on other things.
When you review the commits if you could address this question I would really appreciate it and then I will close this issue for you.
Thank you @xivk !

I attempted to modify the is_oneway and the results changes but were not better.
For the most part the routes generated are fine but in certain cases there are uturns which I am wondering how I can prevent, e.g. I want the route to take the the shortest or fastest but to not use any U Turns.
Here is a simple example:
example.geojson.txt
The actual route is around Peterborough however due to U Turns the route appears to go through Leicester.
I am hoping that if this cannot be changed in the profile that you can share some sample code which uses the RouterSettings to prevent such.
I know if we had some additional points given along the Peterborough route considered the Router would find the correct route so I am wondering if there is not a better way to resolve the points than using TryResolveConnected, perhaps adding a synthetic point between the 2 points if necessary.
I am currently using the following code to build up the points given to the Router
//Try to resolve the point connected to the route going forward
							var resolved = routing.TryResolveConnected(ProfileShortest, (float)ll.Latitude, (float)ll.Longitude, 2000, 1000, true);

							//If there was an error then use the normal resolve
							if (resolved.IsError)
							{
								resolved = router.TryResolve(ProfileShortest, (float)ll.Latitude, (float)ll.Longitude, 1000);

								//If still an error than discard it
								if (resolved.IsError) continue;
							}

@xivk just wondering if you will have any time to help me out on this as well as review the PR's I made for you:
https://github.com/itinero/routing/pull/302
Which requires
https://github.com/itinero/reminiscence/pull/23
After both are applied the issues with using Parallel are gone and I don't seem to have inconsistent results anymore when using a contracted vs non contracted database.
It also seems to address a a few other small things such as GetDistanceInMeters (https://github.com/itinero/routing/issues/279) now being correct as well as the issue when getting different weights were being obtained from TryCalculateWeight (https://github.com/itinero/routing/issues/293)
I can also address https://github.com/itinero/routing/issues/306 but I don't want to commit further until you have verified my changes.
Thank you!

I have experimented with TryCalulcate doing something like this:
var route = Router.TryCalculate(profile ?? TrainProfileFastest, routerPoints, float.MaxValue, (float?[])null, cancellationToken);
But I get:

System.NotSupportedException: Contraction-based many-to-many calculates are not supported in the given router db for the given profile.

Yet my RouterDb is not contracted.
Is there something wrong with my code or am I still going about this the wrong way?


smoother user experience to differentiate MyJFrog vs JFrog Platform

I believe it will be confusing to the users of this provider who are using it to manage a JFrog Platform instance to see the new behavior around managing https://my.jfrog.com.
This is especially relevant now that the provider config wants two different credentials:

access_token https://registry.terraform.io/providers/jfrog/platform/latest/docs#access_token
myjfrog_api_token https://registry.terraform.io/providers/jfrog/platform/latest/docs#myjfrog_api_token

The new warning output (when myjfrog_api_token is not provided) does indeed tell the user the scope of the problem:
MyJFrog API Token was not found in the JFROG_MYJFROG_API_TOKEN environment variable or provider configuration block myjfrog_api_token attribute. MyJFrog functionality will be affected.

... but I think that is still a scary-sounding warning to most Tofu/Terraform users. In most cases, a provider will fail hard if it doesn't have proper credentials (provided in any number of ways). Further, most providers only need a single credential. Thus, muscle-memory for a frequent Tofu/Terraform user says the warning above represents a big problem, even though it is actually only a problem if a platform_myjfrog_ip_allowlist is managed.
The nuance of this provider needing either (or both) of access_token and myjfrog_api_token seems to go against the grain of convention.
Describe the solution you'd like
As much as I hate to suggest it, I think MyJFrog should have its own provider with its own credentials needs.
Describe alternatives you've considered
N/A. Other than adding an internal README where we're using this provider to tell users to ignore the scary-sounding warning.

@StephenWithPH Thanks for the suggestion. I think it has merit and I'll add this to our planning.

@StephenWithPH Viola! Here's the newly released jfrog/myjfrog provider: https://registry.terraform.io/providers/jfrog/myjfrog/latest with a bonus resource myjfrog_custom_domain_name


Feature: Configuration Options

This pull-request aims to add configuration options for unassert.
@zoncoen Would you take a look?

LGTM 🙏
Thank you for your improvement!


[WIP] switch the builder image to use buildah instead of docker daemon

@nalind fyi/watch this space.

/hold

/retest all

/retest

/test unit

/retest

/retest

/retest

/retest
On Fri, Sep 28, 2018 at 8:51 PM, OpenShift CI Robot <
<EMAIL_ADDRESS>wrote:

@bparees https://github.com/bparees: The following tests failed, say
/retest to rerun them all:
Test name Commit Details Rerun command
ci/prow/gcp-crio 8c647a8
https://github.com/openshift/builder/commit/8c647a8b8145b939ee59ed7365e745c335036ab7
link
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_builder/5/pull-ci-openshift-builder-master-e2e-gcp-crio/18 /test
gcp-crio
ci/prow/gcp 8c647a8
https://github.com/openshift/builder/commit/8c647a8b8145b939ee59ed7365e745c335036ab7
link
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_builder/5/pull-ci-openshift-builder-master-e2e-gcp/16 /test
gcp
ci/prow/extended-image-ecosystem 8c647a8
https://github.com/openshift/builder/commit/8c647a8b8145b939ee59ed7365e745c335036ab7
link
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_builder/5/pull-ci-openshift-builder-master-extended-image-ecosystem/18 /test
extended-image-ecosystem
ci/prow/extended-builds 8c647a8
https://github.com/openshift/builder/commit/8c647a8b8145b939ee59ed7365e745c335036ab7
link
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_builder/5/pull-ci-openshift-builder-master-extended-builds/45 /test
extended-builds
Full PR test history
https://openshift-gce-devel.appspot.com/pr/openshift_builder/5. Your PR
dashboard https://openshift-gce-devel.appspot.com/pr/bparees. Please
help us cut down on flakes by linking to
https://github.com/kubernetes/community/blob/master/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests
an open issue
https://github.com/openshift/builder/issues?q=is:issue+is:open when you
hit one in your PR.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/builder/pull/5#issuecomment-425601880, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEvl3gSXdGea3E53buK7Y2Yp9c-Kop2wks5ufsQDgaJpZM4Wy2Aa
.

--
Ben Parees | OpenShift

/retest
On Fri, Sep 28, 2018 at 9:26 PM, OpenShift CI Robot <
<EMAIL_ADDRESS>wrote:

@bparees https://github.com/bparees: The following tests failed, say
/retest to rerun them all:
Test name Commit Details Rerun command
ci/prow/gcp-crio 8c647a8
https://github.com/openshift/builder/commit/8c647a8b8145b939ee59ed7365e745c335036ab7
link
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_builder/5/pull-ci-openshift-builder-master-e2e-gcp-crio/18 /test
gcp-crio
ci/prow/gcp 8c647a8
https://github.com/openshift/builder/commit/8c647a8b8145b939ee59ed7365e745c335036ab7
link
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_builder/5/pull-ci-openshift-builder-master-e2e-gcp/16 /test
gcp
ci/prow/extended-builds 8c647a8
https://github.com/openshift/builder/commit/8c647a8b8145b939ee59ed7365e745c335036ab7
link
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_builder/5/pull-ci-openshift-builder-master-extended-builds/45 /test
extended-builds
ci/prow/extended-image-ecosystem 8c647a8
https://github.com/openshift/builder/commit/8c647a8b8145b939ee59ed7365e745c335036ab7
link
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_builder/5/pull-ci-openshift-builder-master-extended-image-ecosystem/19 /test
extended-image-ecosystem
Full PR test history
https://openshift-gce-devel.appspot.com/pr/openshift_builder/5. Your PR
dashboard https://openshift-gce-devel.appspot.com/pr/bparees. Please
help us cut down on flakes by linking to
https://github.com/kubernetes/community/blob/master/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests
an open issue
https://github.com/openshift/builder/issues?q=is:issue+is:open when you
hit one in your PR.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift/builder/pull/5#issuecomment-425604545, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEvl3ln16PMHqZQJFXu-biUVAhtdPW2rks5ufsxQgaJpZM4Wy2Aa
.

--
Ben Parees | OpenShift

/test extended-builds
/test extended-image-ecosystem

/retest

/retest

/retest

/retest


Try creating ReactJS version

Try making a ReactJS version of the website to help with learning how to use a JS framework

no need

no need


Drop gray-matter from client bundle

PR includes

[X] Refactor

It reduces client js bundle by ~ 50Kb gzip.
Related issues
Resolve #1630

The fix is only to move getStaticProps inside "page" file - drop export { getStaticProps }.

@KateKate https://github.com/taskany-inc/issues/actions/runs/6097924218/job/16546594793?pr=1631#step:3:136

@KateKate https://github.com/taskany-inc/issues/actions/runs/6097924218/job/16546594793?pr=1631#step:3:136

fixed

fixed

U need to push it ;)

fixed

U need to push it ;)


Support ISO 8601 Duration formatting for RTClib's TimeSpan

Arduino board:  N/a (but I am testing code regularly on an Arduino Mega 2560)
Arduino IDE version:  1.8.13

This library provides support for ISO 8601 formatted DateTimes through the toString and timestamp methods, but doesn't have a similar option for TimeSpans. ISO 8601 specifies two formats for durations. (Durations appear to be basically the same thing as this library's TimeSpans)
I would like to add methods that format TimeSpans according to ISO 8601's PnYnMnDTnHnMnS or P<date>T<time> formats, both a zero allocation version (not sure what to call it, maybe format?) and one that returns a std::string called toString. I would also add a TimeSpan constructor taking one argument of const char *iso8601duration. Do you think this feature belongs in this library and would you consider merging a PR containing the changes I laid out?

That sounds like a great addition!

Without extra context (namely the starting point of the interval), these formats can be ambiguous. “P1M” is supposed to be a one-month duration, but how long is that? 30 days? 31?
The Wikipedia article you linked to references the documentation of the Java Duration class. It is worth noting that this class doesn't deal with the ambiguous units “year” and “month”, and only handles days, hours, minutes and seconds. Days are ambiguous too, if you consider DST changes. However, the documentation of the parse() method specifically states that days are “considered to be exactly 24 hours”. And toString() does not use days, and would write "PT48H" (48 hours) instead of "P2D" (2 days).

[a method] that returns a std::string called toString

std::string is not quite standard in Arduino land. People use String instead. And that would be inconsistent with DateTime::toString(), which is the zero allocation formatter. Maybe you could use overloads:

toString(char * buffer): zero-allocation version
toString(void): returns a String

std::string is not quite standard in Arduino land. People use String instead

Yeah, I misspoke above. I meant String.

the Java Duration class... doesn't deal with the ambiguous units “year” and “month”, and only handles days, hours, minutes and seconds.

I think this would be a good policy for this library as well. Specifically only outputting in days and smaller and failing to parse if the Duration string includes months or larger. I'm comfortable including days because I think it is pretty clear this library doesn't do daylight savings time, but I would be document this behavior in toString. This brings up the question of how to fail parsing, as the idiomatic way for C++ constructors to fail is by throwing. I think a named constructor returning std::optional<TimeSpan> would work, but that uses C++17 features, which might be too new?

Maybe you could use overloads

Yeah, I could, and your overloads are better than my proposed names. I rather dislike overloads because they make FFI to languages without overloads (C, Python, Go, Rust) annoying. How about

void toCharArray(char * buffer): zero-allocation version
String toString(void): returns a String

Also expect a pull request incoming, where you can make further comments.

how to fail parsing [...]

That's an issue. A few of the DateTime constructors suffer from the same problem. The ones that parse strings don't even have special handling for invalid inputs, and end up building garbage. It's not ideal, but it's cheap. I guess it could be said that the result of building from invalid strings is “unspecified”, which is not nearly as bad as “undefined”. The constructor that takes the numeric parameters (year, month, day, hour, minute, second) returns an invalid object, which is the cheapest approach in this case. Its documentation contains the following:

Warning
If the provided parameters are not valid (e.g. 31 February), the constructed DateTime will be invalid.
See also
The isValid() method can be used to test whether the constructed DateTime is valid.

You could take that last approach if a specif value of TimeSpan was reserved as invalid which, AFAIK, is not the case so far. Or you could take the cheap approach of not trying to validate the input.

std::optional<TimeSpan> would work, but that uses C++17 features, which might be too new?

Indeed. The Arduino IDE (version 1.8.13) passes the flag -std=gnu++11 to the compiler. This selects the GNU dialect of C++11.

[overloads] make FFI to languages without overloads (C, Python, Go, Rust) annoying.

Well, in the context of Arduino, I guess only C is concerned.
Not sure this should be a concern. From what I have seen, current practice on Arduino seem to be to use overloads. The Arduino core has lots of them. It often calls C from C++, but never the other way around.


Limit iterations by number of seconds

"Iteration" speed depends on the image, so it's hard to automatically find a value that will guarantee that image finishes optimizing before the user loses patience.
This is a change I've made for ImageOptim to limit processing time by checking progress against used CPU time.

Hello,
Thanks for this pull request. I'd prefer to not merge this one, though, as getting time is a library dependency that this core algorithm shouldn't have imho.
A possible other solution is to have an optional stop-condition function that it checks, so the time dependency can be implemented externally instead.
However, is it acceptable to not limit by CPU time, but measure roughly the amount of iterations per second depending on file size that it can handle and estimate time based on that instead?

OK, thanks. I'll refactor it sometime to be a callback.


Text update: Update ERRORFILE reference

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

@kevinvngo Kevin, can you take a look at these suggestions. If you agree, I can help get the merge conflicts resolved. Thanks for the feedback @raunakjhawar !

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

@kevinvngo Kevin, hello. Could you take a look at the proposed changes in the public PR? If you are not the right contact, please let me know who to reach out to (and we can also reassign the article owner in that case). Thank you!

@kevinvngo Kevin, hello. Could you take a look at the proposed changes in the public PR? If you are not the right contact, please let me know who to reach out to (and we can also reassign the article owner in that case). Thank you!


[Nomination] giansalex

Who are you nominating?
@giansalex (Giancarlos Salas)
What are you nominating them for?
Updgrading the CosmWasm code explorer CosmJS verision, adding Keplr support, and showing transaction time in the execution info.
Please provide links to their work.
https://github.com/CosmWasm/code-explorer/pull/62

Append:

Dark theme
Upload wasm binary
Instantiate new contracts

Live: https://blueprints.juno.giansalex.dev/

He also got Juno balance and add token working with keplr.

Also inflation module code

Additional:

Gitpod Workspace https://github.com/giansalex/cosmwasm-workspace

Keplr CW20 tokens: https://github.com/chainapsis/keplr-extension/pull/134

cosmwasm dApps upgrade: https://github.com/CosmWasm/dApps/pull/81

dApps works on Juno

https://dapps.juno.giansalex.dev/names/
https://dapps.juno.giansalex.dev/cw20-wallet/
https://dapps.juno.giansalex.dev/staking/
https://github.com/disperze/wrapped-dapp

Juno chain

https://github.com/CosmosContracts/Juno/pull/36
https://github.com/CosmosContracts/juno/pull/46
Additional contributions

Split contract: https://github.com/disperze/cw-contracts/tree/master/contracts/split

Lockbox contract: https://github.com/disperze/cw-contracts/tree/master/contracts/lockbox

NFT-Marketplace - Cosmverse

dApp - https://github.com/CosmosContracts/Cosmverse
Contracts - nft-market

A duplicate nomination for @giansalex (because he's so awesome): https://github.com/CosmosContracts/hack-juno/issues/15

Updated the nomination, there is so much to say. : )

copied from https://github.com/CosmosContracts/hack-juno/issues/65
Who are you nominating?
Giansalex @giansalex
What are you nominating them for?
Several months of work on Cosmverse the first NFT marketplace on Juno in collaboration with Highlander
Please provide links to their work.
https://cosmverse.com

closing https://github.com/CosmosContracts/hack-juno/issues/65


character menu doesn't scale

I'm not sure if this is a framework or schema issue but the main menu the buttons are clipping out of your screen in top left.
https://i.gyazo.com/62f7d1adb9f0c24db2f763c4f138eb21.png

Thanks for reporting, I will work on fixing this today. This is most likely caused by Reborn theme not being up to date.

Fixed in a6b4e23a0220534ab8180d4f3798fc9256a9d963


YOLO_small.ckpt

Where can I get the YOLO_small.ckpt file used in the YOLO_network.py file from the 3rd party directory?

You can get the file from YOLO_tensorflow.


Sets storage changed to cloud #39

I'll get back to this in a few days and try to push something - I think we can use your approach from #43 62b7fd9 , but swapping roles : with the storage listener in the background script, that would then send a message to any active panes (content script) !
Just linking my comment about the way to test synchronisation features on an in development Chromium extension, for reference : here.


Fixed zip download

one-liner
@soumyabasu @Sumukh Ready.
Zip downloads weren't working... because I didn't close... I removed the with block at some point and that broke things.

Whoops. Accidentally closed it
LGTM.


Add ability to disable teleport transitions

Every time you leave/join the game, it makes a transition (black screen fading in and out). It's achieved by sending a title with a specific character.
The issue is that sometimes the transition can feel too long or obstructive (for example, when you change courses in PKW: Dojo).
It would be really nice to have the ability to disable these transitions

Teleport transitions are there to hide some weird chunk loading and other things MCCI does in the background while you are teleporting
Because of that I don't really want to add a way to disable them.


Simplify Stackdriver Code

Proposed Changes

Remove any magic and be very explicit about where our labels are coming from.
Query region instead of zone (https://github.com/googleapis/google-cloud-go/issues/2810)
Improved debugging by exporting fields

Release Note

NONE

I've been testing this in encv-test, and it doesn't fix the issue, but it does make debugging easier.


fix: slight modification to MLP mapping to reduce potential for numpy…

… overflows and unnecessary computation. np.square(np.cosh(layer1)) was causing a numpy overflow error for some inputs. Since we have already computed the activations earlier in these functions, we can just make use of them directly instead of evaluating cosh() on the out output for the first layer (layer1). This modification eliminated the overflow for my data and passed all relevant tests.

Codecov Report

Merging #549 into devel will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##            devel     #549   +/-   ##
=======================================
  Coverage   51.68%   51.68%
=======================================
  Files         195      195
  Lines       19469    19469
  Branches     2635     2635
=======================================
  Hits        10062    10062
  Misses       8942     8942
  Partials      465      465