Requires double click in ListView

I don't know if it's a repo or Admob SDK issue but clicking the ad is hard and it doesn't respond for first click. It's a huge blocker. I was using sticky banner with another package, I had 10k impressions and 0,50 CTR and now I have 150k impressions but 0,01 CTR. It's worth look into that.

I tried a minimal example on both android and iOS emulator and I was not able to reproduce the problem.
Are you sure that it's not something else that is capturing the first event in your list? Are you using any gesture APIs?
Please try this example, it renders five banners in a ListView and each of them responds to the first click:
'use strict';

var React = require('react-native');
var {
  AppRegistry,
  Component,
  StyleSheet,
  Text,
  View,
  ListView,
} = React;

var Banner = require('react-native-admob').AdMobBanner;

class Example extends Component {

  constructor() {
    super();
    const ds = new ListView.DataSource({rowHasChanged: (r1, r2) => r1 !== r2});
    this.state = {
      dataSource: ds.cloneWithRows([
        ['Banner 1', 'banner'],
        ['Banner 2', 'banner'],
        ['Banner 3', 'mediumRectangle'],
        ['Banner 4', 'banner'],
        ['Banner 5', 'banner'],
      ]),
    };
  }

  render() {
    return (
        <ListView
          style={styles.list}
          dataSource={this.state.dataSource}
          renderRow={(rowData) => (
          <View style={styles.container}>
              <Text>{rowData[0]}</Text>
              <Banner
                bannerSize={rowData[1]}
                adUnitID={"ca-app-pub-3940256099942544/2934735716"} />
            </View>
            )}
        />
    );
  }
}

var styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    marginTop: 20,
    backgroundColor: '#8AADAD',
  },
  list: {
    marginTop: 30,
  },
});

AppRegistry.registerComponent('Example', () => Example);

I never had this problem with simulator + mouse click. And not always with real devices too, it's kind of tricky to get response from a click. Maybe it is related with click region or AdmobSDK after all.
Here is my structure
_renderRow
{
if (adsActive)
banner= ( <AdMobBanner
            style={{alignSelf:'center'}}
            bannerSize={"smartBannerPortrait"}
            adUnitID={ adUnitIDS[0] } /> );

return (
... ...
some codes here
... ...
                <View style={styles.separator}/>
              </View>
            </TouchableHighlight>
            {banner}
          </View> );
}

Sorry for the late reply, I was really busy!
Do you have any news on the issue?
So I tested my example on both iOS and Android devices and I was not able to reproduce your problem.
I'm sorry but I can't help you with this issue.
Does it happen for iOS and Android or only one of them? If it happened on both I think this would imply that it's either a problem with your code (maybe not the ListView but something else) or with react-native itself.
Otherwise I guess there has to be the same bug in both my iOS and Android implementation.

hi there @sbugert
Maybe it's related with my UI but I changed to another module to use only sticky banner. Right now I don't have the same problem.
Actually I realized it because of my Admob revenue. Before using this module I had only one sticky banner, afterwards I switched to this and placed 8 more banners to specific points. My ad view increased like 10k to 100k but click rate was down, so I think that maybe users couldn't click it.
Anyway I'll try reproducing issue with a video soon :)


chore: Implement Retries

Description
Implement Retries as mentioned in https://github.com/noir-lang/noir/issues/1391
Currently retries maximum of 5 times.

I agree @phated! that looks way better 👍

@vicyyn did you rebase out your changes on the master branch or something? Ideally you'd be working from separate branches for each PR so you don't have these sync problems.


tried with nvram but experience som problems

Dear Peter,
I tried to use your nice piece of FRAM code to use it for NVRAM. Although I think it is ok, it seems that the /nvram does not get mounted as pyb.mount(f,'nvram',mkfs=True) reports that the disk f is already exists.
I have included the code for reference, next step would be to merge this with yours to have a FRAM/NVRAM/RAM module, but....
My question: did I forget something very trivial? (running mpy 1.5.2) and bug #1765 on git)
# Running mpy 1.5.2 and have problems with I2C1
# from the standpoint that Peters's code is running, I'm probably overlooking why the code from me doesn't?????
#
"""
# using the module
import pyb                      # ok
import NVRAM from nvram         # ok
f=NVRAM()                       # ok
f.low_level_format()            # ok
pyb.mount(f,'/nvram',mkfs=True) # in most cases "already mounted" error
pyb.mount(None,'/nvram')        # no error on this

"""

"""
M24M02 device has Enable (E2) and two address bits extra to have up to 4x64kbyte of storage
in the I2C "memory device" range 0x50-0x57... One M24M02 occupies four device addresses.
+----+-----+-----+-----+-----+-----+-----+-----+-----+----+----+----+----+----+----+----+----+----+----+
| E2 | A17 | A16 | A15 | A14 | A13 | A12 | A11 | A10 | A9 | A8 | A7 | A6 | A5 | A4 | A3 | A2 | A1 | A0 |
+----+-----+-----+-----+-----+-----+-----+-----+-----+----+----+----+----+----+----+----+----+----+----+
|     device     |              addrbuf[0]                     |           addrbuf[1]                  |
+----------------+---------------------------------------------+---------------------------------------+
|                                                   addr                                               |
+----------------+---------------------------------------------+---------------------------------------+
|                |                                          memaddr                                    |
+----------------+---------------------------------------------+---------------------------------------+
"""
import pyb

# dumb file copy utility to help with managing NVRAM contents at the REPL.
def cp(source, dest):
    if dest.endswith('/'):                              # minimal way to allow
        dest = ''.join((dest, source.split('/')[-1]))   # cp /sd/file /fc/
    with open(source, 'rb') as infile:                  # caller should handle any OSError
        with open(dest,'wb') as outfile:                # e.g file not found
            while True:
                buf = infile.read(100)
                outfile.write(buf)
                if len(buf) < 100:
                    break

class NVRAMException(OSError):
    # no errors will crash the system
    pass

class NVRAM():
    NVRAM_BASE  = const(0x50)       # I2C address 0x50 to 0x57
    def __init__(self, verbose = False):
        self.verbose = verbose
        self._i2c = pyb.I2C(1, pyb.I2C.MASTER, baudrate=100000) # 1MHz/400kHz?
        devices = self._i2c.scan()
        if self.verbose:
            for d in devices:
                print(hex(d))
        lstdev = [d for d in devices if d in range(NVRAM_BASE, NVRAM_BASE + 8)]
        self.ndevices = len(lstdev)
        if self.ndevices > 1:
            lstdev.sort()
            if lstdev[-1] - lstdev[0] != self.ndevices -1:
                raise NVRAMException("NVRAM device addresses not contiguous.")
        elif self.ndevices ==0:
            raise NVRAMException("No NVRAM device found.")
        if lstdev[0] != NVRAM_BASE:
            raise NVRAMException("NVRAM address must start at BASE.")
        if self.verbose:
            print("{:d} NVRAM device(s) detected".format(self.ndevices))
        self.addrbuf = bytearray(2)     # Memory offset into current chip
        self.i2c_addr = None            # i2c address of current chip

    # low level access
    def _getaddr(self, addr, nbytes):   # Set up addrbuf and i2c_addr
        self.addrbuf[0] = addr >> 8     # addr is ADDR[18..0]
        self.addrbuf[1] = addr & 0xFF   # this covers 64K
        device = addr >> 18             # 8 blocks of 64K
        memaddr = addr & 0xFFFF         # offset into chip = 65535
        if device >= self.ndevices:
            return 0                    # higher than available devices?
        self.i2c_addr = NVRAM_BASE + device # combine into new dev addr
        end_addr = memaddr + nbytes     # check if it will fit the device(s)
        if end_addr < 0x10000:          # within the 64k of the device?
            return nbytes               # everything can be processed
        return 0x10000 - memaddr        # what's left

    def readwrite(self, addr, buf, read):
        nbytes = len(buf)
        start = 0
        while nbytes > 0:
            bytes_handled = self._getaddr(addr, nbytes)
            if bytes_handled == 0:
                raise NVRAMException("NVRAM Address out of range")
            if read:
                irqstate = pyb.disable_irq()
                self._i2c.send(self.addrbuf, self.i2c_addr)
                pyb.enable_irq(irqstate)
                irqstate = pyb.disable_irq()
                buf[start : start + bytes_handled] = self._i2c.recv(bytes_handled, self.i2c_addr)
                pyb.enable_irq(irqstate)
            else:
                irqstate = pyb.disable_irq()
                self._i2c.send(self.addrbuf +buf[start: start + bytes_handled], self.i2c_addr)
                pyb.enable_irq(irqstate)
            nbytes -= bytes_handled
            start += bytes_handled
            addr += bytes_handled
        return buf

    # block protocol - see pyb
    def readblocks(self, blocknum, buf):
        return self.readwrite(blocknum << 9, buf, True)     # 2^9 = 512

    def writeblocks(self, blocknum, buf):
        self.readwrite(blocknum << 9, buf, False)           # 2^9 = 512

    def count(self):
        return self.ndevices * 64         # 8 x 64kByte = 512kByte

Your mount command looks wrong. You need
pyb.mount(f,'/nvram',mkfs=True)

What nvram hardware are you using?

Dear Peter,
Indeed in the mail the ‘/‘ is gone, however in the code and what I used the ‘/‘ is definitely there.
The hardware I use is the STM32F405RG :-) and on I2C1 I have a STM M24M02 EEPROM of 256kByte.
http://www.st.com/web/en/resource/technical/document/datasheet/CD00290537.pdf

This is tricky as we both have different hardware. I'll check that there hasn't been a firmware regression by checking that my FRAM code works with the latest build: it does seem an odd error. I assume you've checked that the device isn't already mounted as a result of previous testing (os.listdir('/')), and that unmounting it has actually worked. It's worth issuing ctrl D between runs although I can't remember whether this unmounts devices.
As for merging the code that sounds interesting but to get good performance from the EEPROM you really need to use the page mode, which complicates things (see my flash driver for an example of what's involved). A generic driver without page mode is certainly easiest to implement, but it would need some attention to parameterise the chip size.

OK, thanks for checking this!
I will check out my reference PYB1.0 with mpy v1.5.2  and check it against my modified mpy version and used target board.

Have you had any success here? At risk of stating the obvious, when testing code for block protocol devices it's not unknown for the code to fail leaving the device still mounted. This causes the next run to fail with the message you see. Options are to manually check with os.listdir('\') or to use
try:
    pyb.mount(sd, '/fc')
except OSError:
    pass                                    # Probably already mounted under test conditions

This arises even when testing code which uses thoroughly debugged drivers (when the code under test falls over) so I use this construct widely. It would be good if the mount command implemented a context manager and I'll raise an issue to suggest this.


Add lang segment prefix for web routes

Changes for this PR  https://github.com/apiato/apiato/pull/440

This duplicates all web routes, right? WITH and WITHOUT the {lang} field.. I don't know if this is the desired behaviour?!
Why don't we go for something like:
Add a config flag in the apiato.php Config file like: apiato.web.use_localized_routes (default false in order to keep backwards-compatibility)
Then, use this config flag in this method in order to generate EITHER only non-localized routes or localized ones.
What do you think?

@johannesschobel
Now both variants is available: http://admin.apiato.loc/en/dashboard http://admin.apiato.loc/dashboard (this will be use default lang). Are you want disable routes without lang prefix (for cases with disabled config flag)?
What with this case: http://admin.apiato.loc/ - developer must configure the redirect from the root address to the localized by him self?

Ok, I remove duplicate rotes and add flag to apiato config.
Optional flag was required for correct working laravel route helperm but now I override it.


Merge app dockerfiles

Maybe it's just me, but I think maintaining 2 Dockerfiles for app is annoying and can be source of errors. Since the difference is just the download URL of Mattermost, I propose to use build argument to choose between between team and entreprise edition.
I didn't change the default behavior (which is entreprise edition), so this is not a breaking changes. The only change is that it need to comment out two lines on docker-compose.yml instead of only one to use team edition.
@jasonblais  @xcompass I'll appreciate reviews since there is, maybe, a good reason to keep 2 separate Dockerfiles. But I don't see it.

A dirty solution could be, when we want to trigger an auto-build (new version of Mattermost).

modify app Dockerfile with team as default value, commit and tag as NUMVERSION-team
modify app Dockerfile with entreprise as default value, commit and tag as NUMVERSION-entreprise

So Docker Hub images will have a NUMVERSION-team and NUMVERSION-entreprise tag and latest will alway be Entreprise edition.

That could work, but git history will be kind of confusing. Is it better than two dockerfiles?

Yes Git history will be a mess, you're right I don't think it is better than 2 Dockerfiles.
Or maybe configure Travis to run a script only on tagged commit and build/push 2 versions (team and entreprise) of the image to Docker Hub. I'm not familiar with this (usually I use private docker registry and Gitlab CI) but I guess I could setup something like that.

Up @jasonblais , is there plan to build, for Docker Hub, team and enterprise edition ? Because if not, I'll merge this ;)

Not sure, I don't think right now. If we did add it, would this cause issues in the future?

@jasonblais I don't know how Docker Hub auto-build works (I don't even know how it is configured for this repository). But @xcompass seems to say that it does not support build argument, so if we merge the 2 Dockerfiles (that's what this PR do) then you will only be able to build one version (Team or Entreprise) automatically to Docker Hub.

That's correct. If we ever want to build two versions on dockerhub, we have to have two dockerfiles. If you look at other official repos that has multiple variants, they have multiple dockerfiles. (https://github.com/docker-library/php/tree/master). To void multiple dockerhub repo for different versions, maybe we can apply for official repo on dockerhub, like others. (https://github.com/docker-library/official-images). Not sure if the team wants to go that direction. @jasonblais ?

@pichouk @xcompass Excellent points.
@pichouk  On Monday, would you like to post in the Developers channel and get the Mattermost developers thoughts? I'm thinking this question is better directed to our core engineers than myself.
If you don't hear any response, let me know and I'll bring it up to the team myself.

@jasonblais I'll do :)

@jasonblais Conclusion is that it seems people using Mattermost Enterprise Edition can use without Licence and it will be the exact same as Team Edition.
So I think we can have only Enterprise Edition on Docker Hub, so using Docker build argument is OK, so we can merge Dockerfiles.

Yep, sounds good. As long as we offer a way to also install TE (which the above plan includes), we should be covered

Thanks @pichouk :)

Thanks @pichouk


Error: Cannot find module 'typescript' Require stack: -

Hello using your plugin with the latest stencil core version. 2.12.1
Adding your plugin and here my stencil config:

but got this error when running npm start after:

Do you have any idea ?
thank you a lot for your work

The plugin requires typescript to be installed as a dev dependency in your project.
Can you please check if your package.json has this?

That looks it was the issue. Now having

I am using your example in the doc with the bare minimum.  and here my tailwind

ok added manually via tailwindConf made it works apparently. I don't know if its the default behavior. But maybe in the doc we should say when somehting is required or not

Glad it is working.
The plugin doesn't auto detect the config so you have to give it.
I'll look at updating the docs to make it more explicit. Thanks for the feedback 🙂


Create README.md

Create folder for northern track analysis, in which each of us can have a subfolder.

Hi @Peterandresen12,
I think it would also make sense to update the CODEOWNERS file to assign the people actively working on the northern tracks analysis as owners of this newly created directory. Then new people joining the analysis can always be added later. :)

I added northern_tracks to CODEOWNERS in the same PR I have for another folder creation. Peter can add the remaining members in that PR


TC-SC-3.1: Fix and Automate

This test case seems to be suffering from copy/paste problems. The goal of this is to verify the case session parameters at the low level. So this is just a single session establishment, not a case session re-establishment, ie steps related to establishing the session, closing the session and re-establishing the session can be removed. This can be fairly well simplified to just store the parameters and verify them at the end of the session establishment.
requires plumbing to store and extract the case session parameters.

Hello, I tried to solve the issue.
This is what I did:
Modified the TCDD11 class to remove unnecessary steps, focus on verifying CASE session parameters, and add plumbing to store and extract these parameters. Simplified the test steps and execution flow.
You can review changes in this commit: https://github.com/lattaai13/project-chip-matter-test-scripts-432/commit/debf11c03ff1d9799c50bae20e958fccf6258a4f.

[!CAUTION]
Disclaimer: The commit was created by Latta AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

This issue was tried to solve for free by Latta AI - https://latta.ai/ourmission
If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.


Feature/allow removing sub groups

Fixes #334

Acceptance criteria taken from the task #334
In group composition page, for "direct children" and "all descendants", for "sub-groups", "sessions" and "teams":

[ ] (same as in user list) let the user select one, all or several rows
[ ] (same as in user list) add a "trash" icon + "Remove from group" bottom-right of the table, which is greyed out when there is no selection
[ ] on click on "Remove from group", display a primeng ConfirmPopup with "?" icon and msg "Do you want to also delete the selected group(s)? (will only work if those are empty)"

[ ] on "no": display a primeng ConfirmPopup with "!" icon and msg "By removing "groupA", "groupB" from the group, you may loose manager access to them (if no explicit permission or through other parent group). Are you sure you want to proceed?"
[ ] on "yes": display a primeng ConfirmPopup with "!"  This operation cannot be undone."

depending on the decision, you call "removeGroup" or groupRemoveChild (ignore the orphan thing) service on each group. Grey out action and table while processing.

[ ] removeGroup
[ ] groupRemoveChild

on success/failure/partial success, display appropriate message as done in pending request component.

[ ] success
[ ] partial success
[ ] failure

[ ] If the group could not be deleted because it was not empty, display an appropriate message.
[ ] the table needs to be refreshed after every (?) is done (same as in user list)


Need contribution guide

Need to add a contribution guide to this repository since this is open source.

Because BrightHive will not be maintaining this repository it doesn't make sense for us to add our own contribution guidelines. My recommendation is to close this issue and simply recommend that whoever ends up owning this open source repository adds their own contribution guidelines.


Remove ErrorMessageProcessor class

If https://github.com/grasshopper7/extentreports-cucumberjson-plugin/issues/15 issue is fixed, remove class and test class

Fixed in 2.7.0

Fixed in 2.7.0


Can PyG run on cuda9?

❓ Questions & Help

The nvidia driver version of our server is low. I can only use cuda9 on server. I test it and failed. Could you please tell me that can PyG run on cuda9?

It can run on cuda9, see our dockerfile.

That is really helpful! I will try it. Thanks for your reply.

I use image provided in https://hub.docker.com/r/shengwenliang/pytorch_graph
and got following error:
user@331999e30282:~/pytorch_geometric/examples$ python gcn.py  Traceback (most recent call last):   File "gcn.py", line 5, in <module>     from torch_geometric.datasets import Planetoid   File "/home/user/pytorch_geometric/torch_geometric/__init__.py", line 2, in <module>     import torch_geometric.nn   File "/home/user/pytorch_geometric/torch_geometric/nn/__init__.py", line 2, in <module>     from .data_parallel import DataParallel   File "/home/user/pytorch_geometric/torch_geometric/nn/data_parallel.py", line 5, in <module>     from torch_geometric.data import Batch   File "/home/user/pytorch_geometric/torch_geometric/data/__init__.py", line 1, in <module>     from .data import Data   File "/home/user/pytorch_geometric/torch_geometric/data/data.py", line 7, in <module>     from torch_sparse import coalesce   File "/home/user/miniconda/envs/py36/lib/python3.6/site-packages/torch_sparse/__init__.py", line 5, in <module>     from .spspmm import spspmm   File "/home/user/miniconda/envs/py36/lib/python3.6/site-packages/torch_sparse/spspmm.py", line 7, in <module>     import torch_sparse.spspmm_cuda ImportError: libcusparse.so.9.0: cannot open shared object file: No such file or directory user@331999e30282:~/pytorch_geometric/examples$

I use image provided in https://hub.docker.com/r/shengwenliang/pytorch_graph
and got following error:
user@331999e30282:~/pytorch_geometric/examples$ python gcn.py
Traceback (most recent call last):
File "gcn.py", line 5, in
from torch_geometric.datasets import Planetoid
File "/home/user/pytorch_geometric/torch_geometric/init.py", line 2, in
import torch_geometric.nn
File "/home/user/pytorch_geometric/torch_geometric/nn/init.py", line 2, in
from .data_parallel import DataParallel
File "/home/user/pytorch_geometric/torch_geometric/nn/data_parallel.py", line 5, in
from torch_geometric.data import Batch
File "/home/user/pytorch_geometric/torch_geometric/data/init.py", line 1, in
from .data import Data
File "/home/user/pytorch_geometric/torch_geometric/data/data.py", line 7, in
from torch_sparse import coalesce
File "/home/user/miniconda/envs/py36/lib/python3.6/site-packages/torch_sparse/init.py", line 5, in
from .spspmm import spspmm
File "/home/user/miniconda/envs/py36/lib/python3.6/site-packages/torch_sparse/spspmm.py", line 7, in
import torch_sparse.spspmm_cuda
ImportError: libcusparse.so.9.0: cannot open shared object file: No such file or directory
user@331999e30282:~/pytorch_geometric/examples$

image was updated by @shengwenLeong in https://hub.docker.com/r/shengwenliang/pytorch_geometric_liang


GEODE-6883: Creating membership api package

Creating a new membership API package. Starting that package out with
three classes:

MembershipManagerFactory - created by moving NetMember factory stuff
out of MembershipFactory and renaming MembershipFactory

MembershipManager - Created by renaming the old MembershipManager to

InternalMembershipManager and extracting a subpackage

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Maybe MembershipPool or Members or just Membership

I could go with that. So leave InternalMembershipManager as MembershipManager until we can delete it, and have the new interface called Membership? If you are ok with those names @prettyClouds I'll rename the interfaces and update the pr.


Maker should reject rollover if fails upon starting it instead of just appending RolloverFailed

When working on https://github.com/itchysats/itchysats/pull/2272 we noticed that upon handling a rollover proposal the maker might fail at start_rollover_maker. This currently leads to appending a RolloverFailed event which is a bit odd.
At that point the maker should rather append RolloverRejected (potentially with a reason) and then spin off a task to send RolloverRejected to the other party.
We did not do that back when we implemented it to avoid side effects with the tasks (i.e. only one task per cfd in the rollover actor), but I don't think it is likely that we will run into conflicts there. The problem that we wanted to avoid is the one where we replace a currently ongoing rollover task with another task that would send the rejection (this could happen if a user triggers another rollover while the first one is still ongoing). If we still see this as problem we could introduce a Spawner for the rejections so we don't have to replace the task.

I believe this is a duplicate of #2259 .

This project is unmaintained


alerta: 8.5.2 -> 8.5.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for alerta is: Alerta Monitoring System command-line interface
meta.homepage for alerta is: https://alerta.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 8.5.3 with grep in /nix/store/vh12w7ggls139lm6pdfinca245h9lw1x-alerta-8.5.3
found 8.5.3 in filename of file in /nix/store/vh12w7ggls139lm6pdfinca245h9lw1x-alerta-8.5.3

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
alerta

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vh12w7ggls139lm6pdfinca245h9lw1x-alerta-8.5.3 \
  --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 alerta https://github.com/r-ryantm/nixpkgs/archive/68fad31376c4eedeafe8928cbb084233e2d08c25.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/68fad31376c4eedeafe8928cbb084233e2d08c25#alerta

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vh12w7ggls139lm6pdfinca245h9lw1x-alerta-8.5.3
ls -la /nix/store/vh12w7ggls139lm6pdfinca245h9lw1x-alerta-8.5.3/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 --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages built:

alerta
alerta.dist

Maintainer pings

Result of nixpkgs-review pr 303769 run on x86_64-linux 1

2 packages built:

alerta
alerta.dist


[BUG] Spilling logic can spill data that cannot be freed

The spill code in RapidsBufferStore will spill data from a buffer that is currently not spillable.  This can be very wasteful when the thread that has locked the buffer is busy blocked on an allocate call that is causing spilling to occur.  Such buffers cannot be freed to satisfy the allocation, and spilling them in the hopes the buffer can be relinquished later can be a complete waste of time and I/O bandwidth if the buffer is never unlocked.
Rather than spilling all buffers, the code should track spillable (i.e.: not currently acquired) buffers and only spill those.  The waiting logic for pending free buffers should be changed to waiting logic for buffers to be released (and thus spilled only at that point).

Related issue: https://github.com/NVIDIA/spark-rapids/issues/6561, since in that one we want to make sure the spill framework is told when the underlying buffer is actually freed. For consideration when working on this specific issue.

This is the cuDF side of this change: https://github.com/rapidsai/cudf/pull/12125. We have decided that a callback is all we need from the memory buffer, where we would make something spillable once the memory buffer reaches refCount=1 (e.g. it is held only by the spillable framework).


Scheduling w/o registration

Add classes to the session so a user can register without logging in

removing courses doesn't work with a temp user

i fixed the removing courses with a temp user

cool, works on my home setup.
However for some reason it doesn't work on production. Let's revisit this later.

welp, problem was that the server wasn't running on the same port as the public facing website. This guy works


doubts about roles and abilities

Hi, first of all, I love Motor Admin!
I'm the main developer of the platform and I have a few stakeholders that should only VIEW dashboards, use forms, and manage company data (add/remove/edit users or orders).
So this users should not be able to add links in the header, remove Resources from sidebar or delete a dashboard.
For this, I created the following ability but it does not work as intended:
# frozen_string_literal: true

module Motor
  class Ability
    include CanCan::Ability

    def initialize(user, _request)
      if user.super_admin?
        can :manage, :all
      elsif user.admin?
        can :manage, :all
        cannot %i[create update destroy], motor_resources
      end
    end

    def motor_resources
      [Motor::Query, Motor::Form, Motor::Tag, Motor::Dashboard, Motor::Alert, Motor::Config, Motor::Resource]
    end
  end
end

This prevents the user for creating or editing a Form, Dashboard, Alert, Query, and it works OK
This doesn't prevent the user to remove all Resources from sidebar, or change any configuration on the resources, so they can mess everything in resources.
They can also manage links in the header, but I don't want that.
They can also delete anything in the "Report" section, and I don't want that.
Can you help me achieve this?
Admins should only be able to see dashboards and use the forms and CRUD s.
Even more, I would love to have the ability to lock the whole admin section in production environments and only be able to edit it in local environment so we can keep a clean dashboard in production.

Hi @silva96, thanks for reporting this issue!
So there was a bug in the cannot logic on the front end side - it has been fixed in the newest version of the gem so now resource settings and link settings should be correctly disabled with cannot as well as the ability to remove report items.

Even more, I would love to have the ability to lock the whole admin section in production environments and only be able to edit it in local environment so we can keep a clean dashboard in production.

You can achieve this by adjusting super admin abilities in production environment:
  def initialize(user, _request)
      if user.super_admin?
        can :manage, :all
        cannot :manage, [Motor::Resource, Motor::Config] if Rails.env.production?
      elsif user.admin?
        .....

great! that was lightning fast!


Shared attributes prototype

!!! DO NOT MERGE !!!
(intended for discussion only)
Which problem is this PR solving?
This is a prototype of shared/common attributes - attributes that are applied to all spans and log records. The immediate use cases are for the Web SDK where a number of attributes are relevant across many traces and events. Example attributes are session ID, page URL, window width/height.
Background
Originally, we wanted to capture these as resource attributes (see this OTEP), but it has become apparent that this would likely not get accepted.
Another alternative proposed solution was to capture these as "context" attributes (see this OTEP). This prototype includes a mechanism for context attributes. However, the primary use case for client telemetry is global attributes, which cannot be implemented using context.
Short description of the changes
The prototype introduces a new package shared-attributes, which includes

APIs for capturing and retrieving global attributes - setGlobalAttributes(), getGlobalAttributes()
Span and LogRecord processors that call getGlobalAttributes() and add the attributes to each signal
same as above but for context attributes

setContextAttributes(), getContextAttributes()
Span and LogRecord processors for context attributes

The main files to focus on are:

experimental/packages/shared-attributes/src/utils.ts
experimental/packages/shared-attributes/src/GlobalAttributesSpanProcessor.ts
experimental/packages/shared-attributes/src/GlobalAttributesLogRecordProcessor.ts

This prototype also comes with a web example app that shows how it might be used

examples/opentelemetry-web/examples/shared-attributes/index.js
examples/opentelemetry-web/examples/shared-attributes/tracing.js
examples/opentelemetry-web/examples/shared-attributes/events.js

Open Questions

Do we want to have a generic mechanism like this for capturing global attributes (as opposed to handling each attribute case by case)?
Where should these APIs live? Does a separate package like this make sense or should this be part of the core SDK?
Is this something that all SDKs should adopt, and does it require a spec?

As there were already spec discussions created by people with no JS focus it's a clear indication that this is likely relevant for other languages as well.
The context attributes seem to be well scoped.
For the global attributes I'm not that sure. They might change several time while spans are started/ended in parallel. A snapshot is copied to span at start but changes afterwards are not seen. As I don't have a specific use case in mind for these attributes it's hard to judge if such races are problematic.
First thing I miss is a remove/clear API but well, that's easy to add.
I think this needs to be on API level. In special the context attributes are likely created/modified by instrumentations because these are the locations where e.g. a span is set on a context and a context is activated for a specific code range.
Till now it was quite clear that instrumentations should only depend on API.
I know there is core which is needed in some cases but I remember several discussions in this area which mostly ended up in core should be moved to API.
One topic to clarify is likely the priority of attributes. Which value ends up in the span if the same key is used global, on context and directly set?


Set up CI

We should set up Travis and Appveyor to verify that pony-stable builds. From there, we can move to potentially adding tests.

So, should we test against most recently released Pony version or master? I'm thinking most recently released (and see if we can use our bintray packages on Linux and Windows).
Thoughts?

@kulibali I tried to do an .appveyor.yaml for this and realized I just don't know Windows well enough. Think you can get an .appveyor.yaml together?

Sure, I can work on this tomorrow.

AppVeyor is in place and building.  It doesn't deploy to BinTray yet.

Perfect. Thanks.


Is there any way to access page / report / visual level filters from inside the visual?

Is there any way to refer to the page / report / visual level filters from inside the visuals' code?

No, that is not possible today


[MINOR] Fix wrong file name

What changes were proposed in this pull request?
Fix the filename in doc
Why are the changes needed?
improve docs and output tips.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Not needed.

Merged to master.
Thanks for fixing this @dengziming


Minor change to handle sections correctly

Minor change to handle sections - for some reason passing them in normally wasn't working.

looks good. working on pushing v1.0.6 to rubygems


Installation has changed but instructions haven't for rakudo-star

It looks like we should now use the rstar binary in bin to install rakudo-star on linux - is that right?
The instructions still say to run perl Configure.pl which doesn't exist where it is supposed to according to the instructions anyway.

Ping @Tyil


About specific position input

Hello, thank you very much for your work. I am a doctoral student who has recently joined the research work of 3D agents.
In this demo, I mentioned "Develop a description of the object at the specific position in the 3D backlog" and attached an object surrounded by a red bounding box in the 3D input. I would like to know how the "specific position" is understood by the network and how it is reflected in the code. I am confused. Looking forward to your reply!

LEO does not predict the coordinates of the objects. The model directly provieds the text responses according to the 3D scene and the text prompt. In this demo, the bounding box is used for visualization. In fact, you can modify the model and add special tokens to predict coordinates of the objects.

LEO does not predict the coordinates of the objects. The model directly provieds the text responses according to the 3D scene and the text prompt. In this demo, the bounding box is used for visualization. In fact, you can modify the model and add special tokens to predict coordinates of the objects.

Thank you for your reply. Sorry, I think I may not have described the problem clearly.
What I mean is, in this example, how do I let LEO know that I am asking a question about a keyboard (not a chair, bed, etc.), and more specifically, how do I explicitly let LLM know that I am asking a token question about a keyboard (or any object).
My guess for this is to give LEO some additional location prompts, such as: "Please describe the keyboard and its neighbor object on the table in this scene." or: "Please describe what the object corresponding to the center position [x, y, z] is? And describe what is around it."  Is this how it is implemented? Or is there any other way? Thank you very much!

LEO does not predict the coordinates of the objects. The model directly provieds the text responses according to the 3D scene and the text prompt. In this demo, the bounding box is used for visualization. In fact, you can modify the model and add special tokens to predict coordinates of the objects.

Thank you for your reply. Sorry, I think I may not have described the problem clearly. What I mean is, in this example, how do I let LEO know that I am asking a question about a keyboard (not a chair, bed, etc.), and more specifically, how do I explicitly let LLM know that I am asking a token question about a keyboard (or any object).
My guess for this is to give LEO some additional location prompts, such as: "Please describe the keyboard and its neighbor object on the table in this scene." or: "Please describe what the object corresponding to the center position [x, y, z] is? And describe what is around it." Is this how it is implemented? Or is there any other way? Thank you very much!

You can ask the question like "Please describe the keyboard and its neighbor object on the table in this scene.". But the question "Please describe what the object corresponding to the center position [x, y, z] is? And describe what is around it." may be difficult for LEO, since our curated dataset lacks such data, which will lead to the bias responses. Maybe you can add additional data in the training set to unlock this interesting capability.

I understand now. Thanks for your answer！

@Germany321 @docShen
I'm still confused. Do you mean that we need to prompt "Please describe the keyboard and its neighbor object on the table in this scene." given 3D input with the red bounding box? How can I reproduce the demo?

Let me clarify this. The specific position is associated with the model input whose key is anchor_locs, 3-dim coordinates sampling within the target object to indicate which object the model is supposed to describe. So, if you prompt in this manner such as specific position, you can modify the anchor_locs to customize what you want.

@huangjy-pku
I'm sorry to say that I'm still being confused.
Do you mean that the current published LEO is not able to take and predict any specific position in 3D , but can be done when training with anchor_locs. Please correct me if I'm wrong.
However, in the paper below, the instruction asks LEO to describe about the object at 'specified position'. How is it possible?

The key anchor_locs is not only used for training. It is always a part of the input. When the model is asked to describe specific position, it will utilize the information in anchor_locs, which indicates the coordinate of the specific position.

I got it. So the anchor_locs is necessarily used for both training and predicting in captioning task for a given specific object.
Can I test it with inference.sh by passing a further argument anchor_locs to specify an object?
I also have a question why not using obj_locs or obj_pcd rather than anchor_locs to specifiy an object.

anchor_loc = obj_pcd[:, :3].min(0) + np.random.rand(3) * obj_size

To generate captions for a specific object, you need to first obtain the location of that object and assign a corresponding position to anchor_locs.


Tab Separator not showing with containers

Hello,
first of all I would like to show appreciation for the tab shape of
userChrome.TabCorners.Option10.Enabled
since I read that some shape may be removed based on appreciation I thought it was a good idea to let you know that I really appreciation this option (I think this was the previous "edge" style)
After this, I would like to report that tab separators don't seem to work between containers tabs (they don't show) even if
userChrome.TabSeparatorsMediumSaturation-Enabled
is enabled.
My system info are:
FF113 stable release channel
Win10 22h2
Oh, and one last question: where is the folder named "v1.6.116" that is present in the .zip file of the 113 release supposed to go? in the chrome folder as usual?
Thanks for making WaveFox, I really appreciate your hard work!

I originally wanted to keep all the changes for v1.6.116, but later changed my mind, as users of Firefox 115 ESR will have to use the style for more than a year. To reduce fragmentation between styles, I decided to make the changes that are possible in v1.6.114. This version will most likely become v1.6.115 ESR. I want to use a month in reserve to find bugs and fix them. In v1.6.116 it is planned to remove support for Windows 7/8 and ecotic tab layouts. Everything else has already been removed in v1.6.114. As for the tab separators, they should not be displayed if the container is active, since the containers already have a background.

I originally wanted to keep all the changes for v1.6.116, but later changed my mind, as users of Firefox 115 ESR will have to use the style for more than a year. To reduce fragmentation between styles, I decided to make the changes that are possible in v1.6.114. This version will most likely become v1.6.115 ESR. I want to use a month in reserve to find bugs and fix them. In v1.6.116 it is planned to remove support for Windows 7/8 and ecotic tab layouts. Everything else has already been removed in v1.6.114.

I see, it makes sense! That a nice way of thinking in my opinion!

As for the tab separators, they should not be displayed if the container is active, since the containers already have a background.

Argh, I have modified the code to disable the container background as that was too colorful for me, do you happen to know if there's any "on the fly" way to have separators showing with containers?
Only if it isn't too much work to think on, of course!

I corrected the description in the release to the current one.

Thanks! I think it will be a great clarification as most stable release channel are approaching to FF113 just today, right now.

If you want, you can put directly into 1.6.114. Although it is marked as beta, I already made all the changes I wanted there. It is fully compatible with version 113 of the browser. The only thing I didn't do was remove the old svg set, but otherwise the style is ready for browser version 114.

Argh, I have modified the code to disable the container background as that was too colorful for me, do you happen to know if there's any "on the fly" way to have separators showing with containers?
Only if it isn't too much work to think on, of course!

Delete this line.

Much appreciated! Thanks a lot!

Argh, I have modified the code to disable the container background as that was too colorful for me
@Minibus93, can you please specify how exactly you achieved this? I don't like coloured container tabs as well.

@QNetITQ Hi! I saw the comment by my notification bar on my phone, but I can't see it anymore so I'm not sure if you still need it (and I'm not sure if I remember it all lol).
Anyway, it was about containers, so sure, I'll try to give as much details as possible on how fir them into WaveFox.
I'm not the author of the code for this style of containers, I just saw them somewhere and frankensteined it into WaveFox (I may have changed something for the FF113 update out of the original code, but that's about it)
Anyway, so:

Delete the "Container Indicators" section in the WaveFox css file;
add this code instead:

/* rework of container style */ .tab-context-line {   order: 1 !important;   opacity: 1 !important;   transition: none !important; }
And it's done.
Hope it's still useful :D

Hey @Minibus93, thanks for the info. Actually, it was me who commented 😅.
I deleted the comment because I was able to fix it myself (well, sort of). I found some css related to the container indicator in the userChrome.css and deleted them. But, your solution is much better. I can't thank you enough for the deatiled response and sorry for causing the confusion.


How should I integrate Nodes into my design process?

I really not understand why nodes are there and how can I keep into account them when designin the game, I feel like I'm missing something really important. There are some obscure points that probably are handled in automatic by Svelto:

Implementors are instantiated by?
Implementors are injected according to what..nodes?

What I don't get (and that is probably a feature), is that
I can have a Implementor implementing components A,B,C, while at same time a Node map components B,C,D. How exactly svelto make sure an Entity have N components, and that all those components are used by some Node?

The simplest way to see nodes vs components is this:

Components must be designed as part of an entity. The components, starting from their names, are thought to compose an entity.
Nodes instead are linked to the engines. Nodes are how engines see entitites.

In this way you totally decouple the design of your entities from the design of your engines.
You build an entity always through the BuildEntity function (see my last article). The BuildEntity needs the list of implementors. You can create implementors on the spot or pass them as monobehaviour, it doesn't matter.
As you realised, components are not object in Svelto.ECS, they are just interfaces, so an object must implement them. These objects are the implementors.
About the last question, it doesn't matter for you, that Svelto.ECS magic. If you don't implement some components needed for an Entity, Svelto.ECS will tell you with an exception in run-time.


Update the Docker image for NCS 1.7.0

Update the toolchain and nRF Command-line tools.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


chore(docs): update Node.js requirement (#1883)

ng --version does not work on Node.js 4 anymore as reported in #1883

We've updated our release process to pre-build everything, so the problem in #1883 has been fixed now.


Timeline upgrade + partial resolve

This PR updates the timeline dependency to the latest and adds a config option to use the new timeline-resolve feature for using a cache to do partial resolves (improves performance when only small changes are made in the timeline)

Codecov Report

Merging #159 into release24 will increase coverage by 0.01%.
The diff coverage is 95.00%.

@@              Coverage Diff              @@
##           release24     #159      +/-   ##
=============================================
+ Coverage      80.25%   80.27%   +0.01%
=============================================
  Files             44       44
  Lines           5460     5470      +10
  Branches        1229     1296      +67
=============================================
+ Hits            4382     4391       +9
  Misses          1017     1017
- Partials          61       62       +1

Impacted Files
Coverage Δ

src/types/src/superfly-timeline.ts
100.00% <ø> (ø)

src/AsyncResolver.ts
78.84% <91.66%> (+0.12%)
:arrow_up:

src/conductor.ts
87.71% <100.00%> (+0.15%)
:arrow_up:

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 ee3a056...7c793ef. Read the comment docs.


Add "labels" to SetFitModel, store/load from configuration file

Hello!
Pull Request overview

Add SetFitModel.labels, SetFitModel.label2id, SetFitModel.id2label.
By default, use labels in model.predict. Can be disabled with model.predict(use_labels=False).
Save normalize_embeddings and labels in a config_setfit.json file.
Move config_setfit_span.json contents (i.e. span_context) to config_setfit.json.
Fix for wrong device with training with a differentiable head.

Details
The core of this PR is to allow:
model = SetFitModel.from_pretrained("tomaarsen/setfit-bge-small-v1.5-sst2-8-shot")
preds = model.predict([
    "It's a charming and often affecting journey.",
    "It's slow -- very, very slow.",
    "A sometimes tedious film.",
])
print(preds)
# ['positive', 'negative', 'negative']

i.e. get string outputs.

Tom Aarsen

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Build fixes

Yup that's right
That interface is if you are wrapping the form component and want to pass props down to the form component


interp: improve handling of interface struct field

Wrap non empty interface value  in struct field, to allow method
lookup.
Fixes #1208.

@mpl can you review please 🙏


HasManyIds does not reflect additions to HasMany relationship

If an entity is added to a HasMany relationship collection, it should be added to the Ids in HasManyIds.  That is currently not the case within the same session.
[Model]
public class Person
{
    [HasManyIds("pizzas")]
    public IEnumerable<Guid> PizzaIds { get; set; }
    [HasMany]
    public ICollection<Pizza> Pizzas { get; set; }
}

var moarPizza = session.Get<Pizza>(moarPizzaId);
person.Pizzas.Add(moarPizza);
await session.Update(person);
// FAILS in same session.  Succeeds in new session
Assert.True(person.PizzaIds.Contains(moarPizzaId));

This is fixed by #77 if session.Update was called.  If the Ids are accessed before session.Update is called, they will still return outdated information


Need to update based on ADLS Gen2 Functionality

Page needs to be updated based on the ADLS Gen2 functionality. It actually offers GRS. Incorrectly stated.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4931350d-0c12-00b2-64a8-112f67aba3f2
Version Independent ID: eed89d06-7676-30e1-b801-2f67a09856f0
Content: Choosing a data storage technology
Content Source: docs/data-guide/technology-choices/data-storage.md
Service: architecture-center
Sub-service: cloud-fundamentals
GitHub Login: @ZoinerTejada
Microsoft Alias: pnp

@salavala Thank you for your feedback! We have assigned this issue to the author to review further and take the right course of action.

We've taken this item to our internal backlog for further research and will update as necessary!


Some thoughts and questions

Hi
First off: Thank you for this compiling this list
I have used phpwhois and a script by Ben Okopnik in private projects for some years - and I have to (shamefully) say without much thought as to what goes on behind them. But its obvious they are in need of some updates which arent happening.
And so I came to researching other options and found your list.
Despite some experience of web dev and inter-net-working I never quite grasped the hassle caused because there is no standardised format for whois.  I am astounded at this and dont understand why its never been corralled by an rfc or similar.
I notice around github you have been asking others to combine efforts to compile a list of servers which imho under the circumstances has to be a good thing.
Do you think your script will become the "standard list"
Do you think xml is the right format?
Do you have any pointers or thoughts re. parsing whois output?
Regards
l

Do you think your script will become the "standard list"

I can't predict that. But at the current time I didn't receive so much acceptance from the other projects around. So it looks like everybody wants to brew his own soup. Therefore I just consume those soups and present you this compiled soup.

Do you think xml is the right format?

I do. It's a perfectly mature interoperable format and I do believe unmarshaller are available in any language. But if you think there's a better format I'm listening. Also I'm open for changing the schema as well.

Do you have any pointers or thoughts re. parsing whois output?

Not really. And to be honest at current time I don't care much about that. The only information I do care is checking the availability of a domain. But if parsing the other informations would become interesting I'd define antlr grammars similar to the one I use currently for IANA's whois server.
I'll close that issue as I don't see any issue here.


Can we have access to the V2 Form Recognizer container?

Or at least provide us with a time frame as to when it will be available? It's been in preview for a while now as a service in Azure.

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

ID: a36a9196-5e31-1d88-115b-75dfb0b3fb0f
Version Independent ID: 51db9675-eb67-a325-cd10-a2fbff8e102a
Content: How to install and run container for Form Recognizer - Azure Cognitive Services
Content Source: articles/cognitive-services/form-recognizer/form-recognizer-container-howto.md
Service: cognitive-services
Sub-service: forms-recognizer
GitHub Login: @IEvangelist
Microsoft Alias: dapine

@smf723 we will review your feedback and get back to you shortly. Thanks.

@smf723 thanks for your feedback. There isn't a published availability timeline at the moment. However, I encourage you to upvote this similar request in the feedback forum where you can comment/monitor updates to your request. Thanks.

Hi @smf723,
We are hopeful that in the next several months it will be available. Thank you for your continued patience. #please-close

I also would like v2 so I can do custom labeling with a local form recognizer in docker.

I also would like v2 so I can do custom labeling with a local form recognizer in docker.

You can download the labeling tool in a docker container following the instructions here
What's not available is the ability to analyze forms locally in a container with V2. We need this for compliance reasons to keep data on premise. I'm not sure why this is so difficult because they are just running the same container in the cognitive services.

I have the labeling tool in a docker container but it is pointing to an azure blob storage. I can't put our data in the cloud for compliance reasons as well. I want to do custom labeling and keep the data on premise.

I have the labeling tool in a docker container but it is pointing to an azure blob storage. I can't put our data in the cloud for compliance reasons as well. I want to do custom labeling and keep the data on premise.

I just used forms without sensitive data for my training. For us the forms are not sensitive, there actually publicly available forms, it's just the data on them that is.
Keep in mind, even if you could keep all your training data locally, you still have to the Azure service to analyze the forms so you won't be compliant anyway. That's why I was asking about being able to run the analysis functionality locally in a container.


Unable to Deposit Into Aave

Hello,
I'm trying to follow your example. I am attempting to run aave_borrow_web3.py, but the function is failing when it reaches the deposit function. I get the following error:
Approving ERC20...
Approved<PHONE_NUMBER>0000000 tokens for contract 0xE0fBa4Fc209b4948668006B2bE61711b7f465bAe
Depositing to Aave...
Traceback (most recent call last):
  File "/home/ec2-user/environment/aave_protocol.py", line 211, in <module>
    main()
  File "/home/ec2-user/environment/aave_protocol.py", line 33, in main
    tx_hash = deposit_to_aave(w3, amount, lending_pool, nonce=nonce_two)
  File "/home/ec2-user/environment/aave_protocol.py", line 148, in deposit_to_aave
    "nonce": nonce,
  File "/home/ec2-user/.local/lib/python3.7/site-packages/web3/contract.py", line 1087, in buildTransaction
    **self.kwargs
  File "/home/ec2-user/.local/lib/python3.7/site-packages/web3/contract.py", line 1648, in build_transaction_for_function
    prepared_transaction = fill_transaction_defaults(web3, prepared_transaction)
  File "cytoolz/functoolz.pyx", line 250, in cytoolz.functoolz.curry.__call__
  File "/home/ec2-user/.local/lib/python3.7/site-packages/web3/_utils/transactions.py", line 102, in fill_transaction_defaults
    default_val = default_getter(web3, transaction)
  File "/home/ec2-user/.local/lib/python3.7/site-packages/web3/_utils/transactions.py", line 66, in <lambda>
    'gas': lambda web3, tx: web3.eth.estimate_gas(tx),
  File "/home/ec2-user/.local/lib/python3.7/site-packages/web3/eth.py", line 728, in estimate_gas
    return self._estimate_gas(transaction, block_identifier)
  File "/home/ec2-user/.local/lib/python3.7/site-packages/web3/module.py", line 60, in caller
    null_result_formatters)
  File "/home/ec2-user/.local/lib/python3.7/site-packages/web3/manager.py", line 190, in request_blocking
    null_result_formatters)
  File "/home/ec2-user/.local/lib/python3.7/site-packages/web3/manager.py", line 168, in formatted_response
    raise ValueError(response["error"])
ValueError: {'code': -32016, 'data': 'Reverted', 'message': 'The execution failed due to an exception.'}

The only things I have changed from your project to mine are the KOVAN_RPC_URL, my private key, and my_address which I'm now defining as my_address = Web3.toChecksumAddress('0xe6c3e6373Ea83da6A555Fcee944038308130bB67').
And you can see the transactions getting approved here: https://kovan.etherscan.io/address/0xe6c3e6373Ea83da6A555Fcee944038308130bB67
Additionally, this comment indicates that error code "-32016" corresponds to "token transfer failed".
This is my first attempt at programming with Web3 and I'm very excited about the defi space so any help here would be greatly appreciated.
Thanks

Apologies, I had not run the get_weth module. Please disregard this issue.


Change getstart.ipynb

The first Lambda equation in the docs contains a small typo ; Change the subtraction symbol to addition.

Good observation, thanks.


Support new and login on servers - where there is no browser

https://github.com/dotenv-org/dotenv-vault/pull/61


Support for Dreamscreen solo

I have a Dreamscreen Solo that I'm trying to link to Home Assistant.
I end up getting the following error message: Unknown Device type: 7.
I think this is simply because DS created a new type for the Solo next to the HD and 4K versions.
In the message received from the Solo one can even conclude that the HDMI-inputs are 'supported' although the Solo only has 1 input and no outputs.
I went through the python code and I cannot figure what to change in the code itself to get my Solo working with your great work.
I hope this is a simple fix and you can guide me to the right lines in the python code.
Andre Klap
2019-06-21 15:07:31 INFO (MainThread) [homeassistant.setup] Setting up dreamscreen
2019-06-21 15:07:31 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=dreamscreen, service=set_mode>
2019-06-21 15:07:31 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=dreamscreen, service=set_hdmi_source>
2019-06-21 15:07:31 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=dreamscreen, service=set_brightness>
2019-06-21 15:07:31 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=dreamscreen, service=set_ambient_scene>
2019-06-21 15:07:31 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=dreamscreen, service=set_ambient_color>
2019-06-21 15:07:31 DEBUG (MainThread) [custom_components.dreamscreen] Discovery Timeout: 1
2019-06-21 15:07:31 DEBUG (MainThread) [custom_components.dreamscreen] Configured devices: 1
2019-06-21 15:07:31 DEBUG (MainThread) [custom_components.dreamscreen] Adding dreamscreen_solo - <IP_ADDRESS> [Timeout: 99]
2019-06-21 15:07:31 DEBUG (MainThread) [pydreamscreen.devices] Listening...
2019-06-21 15:07:31 DEBUG (MainThread) [pydreamscreen.devices] Received b'\xfc\x92\xff`\x01\nDreamScreen Solounassigned\x00\x00\x00\x00\x00\x00\x00\x00d\x0f\xff\xff\xff\xff\xff%\x1a\xff\xc4\xff\x0c\x18HH\x01\x07\x00\x00\x02\x01222\x00\x00\x00\x01\x04\x00\xcd \x00\x00\x00\x00\x00\x02\x00\x00HDMI 1          HDMI 2          HDMI 3          \x01\x01\x01\x1b\x00\x00\x00\x01\x06\x06\x02\x00\x00\x03\x01\x00\x00\x07g' from <IP_ADDRESS> [8888]
2019-06-21 15:07:31 DEBUG (MainThread) [pydreamscreen.devices] Processing state from <IP_ADDRESS> [8888]
2019-06-21 15:07:31 DEBUG (MainThread) [pydreamscreen.devices] Unknown device type: 7
2019-06-21 15:09:10 ERROR (MainThread) [pydreamscreen.devices] couldn't get_state of <IP_ADDRESS>
2019-06-21 15:09:10 WARNING (MainThread) [custom_components.dreamscreen] Failed to add device [<IP_ADDRESS>] dreamscreen_solo. Try setting a 'timeout' in the device config.
2019-06-21 15:09:10 INFO (MainThread) [homeassistant.setup] Setup of domain dreamscreen took 99.2 seconds.
2019-06-21 15:09:10 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=dreamscreen>

I went through the python code and I cannot figure what to change in the code itself to get my Solo working with your great work.

First guess, you looked into the wrong repo. This is only the HA bridge and loads PyDreamscreen
I have no time right now. But here is the quickstart:
Pydreamscreen throwing your error.
Your Message contains 7 and the code doesn't handle it yet. See here
https://github.com/GregoryDosh/pydreamscreen/blob/4e2c72e4d79fa8b0a4153cb6e5ea39cecc7d40cc/pydreamscreen/devices.py#L110
I'll check later.

Hi Gregory,
Thanks for the tip. I got it working in the meantime !!
I was not aware of the pydreamscreen (I’m a newbie to home assistant and docker and python, but I have some background in C++, so I managed) 😊
Attached the updated files
init.py from the custom_components/dreamscreen folder:

Added pydreamscreen.DreamScreenSolo class/type
Removed logger on line 249. It broke the code, don’t know why.

Pydreamscreen/__initi.py & devices.py in PYDREAMSCREEN_SOLO.zip

Added DreamScreenSolo device (7) and class etc etc.
I think the code is complete, I updated everywhere where there was DreamScreen4K I added similar code for DreamScreenSolo

Thanks for your quick reply, it set me on the right track to resolve this in ~3 hours.
Andre
Van: J3n50m4t<EMAIL_ADDRESS>Verzonden: vrijdag 21 juni 2019 17:55
Aan: GregoryDosh/Home-Assistant-DreamScreen-Service<EMAIL_ADDRESS>CC: AndreKSB<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Onderwerp: Re: [GregoryDosh/Home-Assistant-DreamScreen-Service] Support for Dreamscreen solo (#19)
I went through the python code and I cannot figure what to change in the code itself to get my Solo working with your great work.
First guess, you looked into the wrong repo. This is only the HA bridge and loads PyDreamscreen https://github.com/GregoryDosh/pydreamscreen
I have no time right now. But here is the quickstart:
Pydreamscreen throwing your error.
Your Message contains 7 and the code doesn't handle it yet. See here
https://github.com/GregoryDosh/pydreamscreen/blob/4e2c72e4d79fa8b0a4153cb6e5ea39cecc7d40cc/pydreamscreen/devices.py#L110
I'll check later.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/GregoryDosh/Home-Assistant-DreamScreen-Service/issues/19?email_source=notifications&email_token=AMNKMFB4DSVDXKHB25SOSN3P3T2UZA5CNFSM4H2S2HVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYI3JRY#issuecomment-504476871 , or mute the thread https://github.com/notifications/unsubscribe-auth/AMNKMFD6TYTWYCID56ZOKHDP3T2UZANCNFSM4H2S2HVA .  https://github.com/notifications/beacon/AMNKMFHSVYOUBMSYSDLUXATP3T2UZA5CNFSM4H2S2HVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYI3JRY.gif

Hi,
I'm not Gregory :D
Happy you got it. I would file a PR if you don't want to..
If @GregoryDosh  doesn't want to maintain the tool i may have to, because i love it. But tahts another story.
Could you close the Issue, as its done please?

Sorry I've not been active with this.  I've moved across country and been unable to get much coding done along with the fact that my Dreamscreen is still back in my previous house at the moment.  @J3n50m4t thank you for your pull requests & help.

Thanks J3n50m4t :)

I've "merged" your commit to both Repos.
Next time it would be nice if you create a PR.


F* fails on lenth-indexed lists with length ≥ 19

Let's assume a length-indexed list type and a number of lists of increasing length:
open FStar.List.Tot

type vector 'a n = v:list 'a {length v == n}

val v1 : vector nat 1
let v1 = [1]

val v2 : vector nat 2
let v2 = [1; 2]

val v3 : vector nat 3
let v3 = [1; 2; 3]

// ...

val v18 : vector nat 18
let v18 = [1; 2; 3; 4; 5; 6; 7; 8; 9; 10; 11; 12; 13; 14; 15; 16; 17; 18]

val v19 : vector nat 19
let v19 = [1; 2; 3; 4; 5; 6; 7; 8; 9; 10; 11; 12; 13; 14; 15; 16; 17; 18; 19]

val v20 : vector nat 20
let v20 = [1; 2; 3; 4; 5; 6; 7; 8; 9; 10; 11; 12; 13; 14; 15; 16; 17; 18; 19; 20]

F* fails with some variant of the following error for each list of length ≥ 8:
Bug1.fst(29,9-29,33): (Error 19) Subtyping check failed; expected type Bug.vector Prims.nat 8; got type Prims.list Prims.nat; The solver found a (partial) counterexample, try to spell your proof in more detail or increase fuel/ifuel (see also Bug1.fst(5,30-5,43))

This makes sense: the default setting for fuel is 8, so F* is probably running out of fuel while checking the length of the larger lists. Indeed, if we increase the fuel, we can progressively push back the errors: with 9 fuel we can check lists up to length 9, with 10 fuel we can check lists up to length 10, etc.
Unfortunately, this stops at 19... no matter what amount of fuel we give F*, it fails to check length-indexed lists with length ≥ 19.

Bug1.fst.txt

Curiously, the bug does not happen when the lists contain nested lists as opposed to numbers:
open FStar.List.Tot

type vector 'a n = v:list 'a {length v == n}
type matrix 'a r c = vector (vector 'a c) r

val m_1_1 : matrix nat 1 1
let m_1_1 = [[1]]

val m_2_1 : matrix nat 2 1
let m_2_1 = [[1]; [1]]

val m_3_1 : matrix nat 3 1
let m_3_1 = [[1]; [1]; [1]]

// ...

val m_18_1 : matrix nat 18 1
let m_18_1 = [[1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]]

val m_19_1 : matrix nat 19 1
let m_19_1 = [[1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]]

val m_20_1 : matrix nat 20 1
let m_20_1 = [[1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]; [1]]

Bug2.fst

Z3 could easily get deep in the weeds with such a high fuel setting.
A better, more predictable way of doing this is to use the normalizer, as in
val v20 : vector nat 20
let v20 =
  let v = [1; 2; 3; 4; 5; 6; 7; 8; 9; 10; 11; 12; 13; 14; 15; 16; 17; 18; 19; 20] in
  assert_norm (length v = 20);
  v

Thanks! That does work. Why isn't normalising done by default before querying Z3?

The limit of 19 comes from a Z3 cutoff that you can adjust with --z3cliopt smt.QI.EAGER_THRESHOLD=n for whatever number n you want.  But, as Santiago said, using the normalizer is safer than adding a lot of fuel.  F* could normalize more by default before querying Z3, but this can result in larger SMT queries that are slower for Z3 to process.

Thanks, @Chris-Hawblitzel, that's great to know!


Install with Nuxt – safelist/css missing including backdrop for modals/drawer

Describe the bug
Backdrop CSS and other CSS is missing because of JIT, the safelist provided on flowbite is missing dozens of css
To Reproduce
Steps to reproduce the behavior:

go here https://flowbite.com/docs/getting-started/nuxt-js/
Flow steps
On app.vue add the modal example or drawer example.

Expected behavior
Backdrop should work, it doesn't. other CSS is not included because of JIT

Hey @timothymarois ,
I believe you can easily fix this by adding the Flowbite JS paths to tailwind.config.js:
module.exports = {

    content: [
        "./node_modules/flowbite/**/*.js"
    ]

}

Source: https://flowbite.com/docs/getting-started/quickstart/
Cheers,
Zoltan


Classification EnergyCarrier needs to be restructured

The class EnergyCarrier with subclasses like Air, Heat and Fuel is currently a subclass of bfo:object. As they dont have boundaries and are uncountable (same problem as with StateOfMatter) EnergyCarrier needs to be reclassified.

EnergyCarrier should be a subclass of bfo:disposition instead of bfo:object.
Air, Heat, Fuel etc. should not be subclasses of EnergyCarrier accordingly, but have the disposition to be an EnergyCarrier.


types, cache: Remove Capture level

The type Cache has only one field with is Capture only the capture is
going to be cached. This change remove the Capture level of cache.
Signed-off-by: Quique Llorente<EMAIL_ADDRESS>

I remember we have discussed this already and reasoned for it to be a better structured hierarchy in the output.
It allows the API to support other caches, like arbitrary metadata or some other data.
The cost is minimal and also looks much better on the spec.

I remember we have discussed this already and reasoned for it to be a better structured hierarchy in the output. It allows the API to support other caches, like arbitrary metadata or some other data.
The cost is minimal and also looks much better on the spec.

ok, closing.


Complete documentation for 3.11.0

BJData
contributors for 3.11.0

Further changes:

removed deprecated BJData functions
removed example for deprecated iterator_wrapper function
added a lot more examples

Todo:

[x] check descriptions of exceptions (see https://github.com/nlohmann/json/pull/3463#discussion_r862485440)
[x] check binary size table (see https://github.com/nlohmann/json/pull/3336#issuecomment-1114333114)
[ ] have @fangq have a look at the documentation for BJData

Coverage remained the same at 100.0% when pulling e44c2793730f54880a9d4c057970810fa91c4c80 on documentation into 0c698b75ccb81c2218e0b0b3ae8e9e60ba97c6bb on develop.

@nlohmann, let me know if the above commit looks ok to you: https://github.com/NeuroJSON/json/commit/d2238e58f27cb3a1524c8432c04410ff4c0e25d3
or
https://github.com/NeuroJSON/json/blob/issue3464/docs/mkdocs/docs/features/binary_formats/bjdata.md

@nlohmann, let me know if the above commit looks ok to you: NeuroJSON@d2238e5 or https://github.com/NeuroJSON/json/blob/issue3464/docs/mkdocs/docs/features/binary_formats/bjdata.md
not sure how to do a PR to a PR, feel free to copy the bjdata.md file directly to your local branch.

I think when creating a PR you can select a different destination branch than develop. This PR is being developed in the documentation branch (see line below the PR title).

I think when creating a PR you can select a different destination branch than develop. This PR is being developed in the documentation branch (see line below the PR title).

thanks @falbrechtskirchinger, new PR against documentation branch at https://github.com/nlohmann/json/pull/3493


fix port unmarshal issue and add ut.

Resolve: https://github.com/istio/istio/issues/15366
Also add back the removed UT for unmarshalling from YAML/JSON to go struct.

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

Test name
Commit
Details
Rerun command

operator-test-master
db87d00132e872cdeca5e219650aa999d53e1b36
link
/test operator-test-master

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


Added extra info to unknown templates

Currently, we have a very limited number of variable available to the unknown templates which prevent us to match the alert and action notification template (includes incident states) and sometimes unknowns are getting unnoticed due inconsistency (when using external notification systems e.g. pagerduty).
With this patch, I tried to include the alert states to unknown which is very useful when grouping disable using unknownMinGroupSize.
Please let me know your thoughts.

here is an example of a PagerDuty alert body template
pdMonitoringBody = `{
       "service_key": "XXXXXXXXXXXXXX",
       "event_type": "trigger",
       "description": "{{.Subject | jsonStr}}",
       "client": "bosun",
       "client_url": "{{.Incident}}",
       "incident_key": "AlertName={{.Alert.Name}};IncidentId={{.Id}}"
 }`

if you make close attention to incident_key we use alert name and incident id combination to reduce duplication. With current unknown template contexts/var, it's impossible for us to prepare an unknown body that matches the above specification and due to this may unknowns are getting unnoticed by teams.
With this patch, we are able to produce the unknown body and post  to PagerDuty successfully
pdMonitoringUnknownBody = `{
       "service_key": "XXXXXXXXXXXXX",
       "event_type": "trigger",
       "description": "Alert goes to unknown states",
       "client": "bosun",
       "client_url": "{{ .IncidentUnknownLink .States.Id }}",
       "incident_key": "AlertName={{.Name}};IncidentId={{.States.Id}}"
}`

@kylebrandt / @captncraig  could you please let us know your thoughts?

can this be merge soon :)

Hey @kylebrandt, @captncraig!
Any objections to this change? Is there something else we need to implement before this gets merged?
Thanks,
Anna


Added ability to (optionally) set the swagger-metadata Multer options

Added ability to (optionally) specify the swagger-metadata Multer options
The multer middleware handles multipart/form-data using memoryStorage by default. Can now be redefined (see https://github.com/expressjs/multer). Alternatively, it can be defined as null to completely skip multipart/form-data parsing. In that case another middleware or the route handler would need to take care of it

This isn't going to happen.  swagger-tools provides these middlewares as a convenience and if you need custom versions or custom configured versions, just configure them yourself.  This has come up a number of times, like #322, and the agreement even outside of myself is that this is outside the scope of swagger-tools.


Properly follow live_view redirects so as to retain flash

Today I was working with an acceptance test making assertions on flash after submitting a form.
      step "the school user submits valid data, and is returned to the 'browse' page with a confirmation message" do
        page =
          page
          |> OldPages.Program.Add.submit_form(%{"name" => "Big Band Big Time"})
          |> OldPages.Program.Browse.assert_here()
          |> OldPages.assert_flash_messages(["Added program"])
      end

However, my assertion consistently failed: there was no flash on the page or in the conn.
If we examine the existing logic in handle_rendered_result/2, it becomes clear why this is:
  defp handle_rendered_result(rendered_result, %__MODULE__{} = page) do
    case rendered_result do
      rendered when is_binary(rendered) -> %{page | rendered: rendered}
      {:error, {:live_redirect, %{to: new_path}}} -> new(page.conn, new_path)
      {:error, {:redirect, %{to: new_path}}} -> Pages.new(page.conn) |> Pages.visit(new_path)
      {:ok, live, html} -> %{page | live: live, rendered: html}
    end
  end

In the second case, the live redirect, we simple reuse our conn and visit a new path. However, by doing this we are losing information about what should be in the flash post-redirect. The implementation for the macroPhoenix.LiveViewTest.follow_redirect/3 shows how to do this properly.

Thanks Andrew!

v0.6.2 with this change has been released to hex.


Fetch Colors error on colors theme

When I'm trying to change the color of the VS Code theme, a new window with the title: "Fetch Colors" opens up, and the program exits the theme selection. This is very stressful!

/needsMoreInfo
As well following the upcoming guidance please use the Start Extension Bisect command to investigate whether the problem is being caused by one of your extensions.

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Allow setting whether to include exception details per request

Product
Hot Chocolate
Is your feature request related to a problem?
I want to include exception details for requests authenticated as my smoke test user (regardless of the environment).
The solution you'd like
Add a member to IQueryRequestBuilder to set whether to include exception details, so that a rqeuest interceptor can modify it.
Currently configuring the inclusion of exception details is only possible globally using ModifyRequestOptions(options => options.IncludeExceptionDetails = true). I have not found a way to configure this per request.

We will not do this one ... this potentially can have a lot of security implications.

Wait, what? I am of the exact opposite opinion; this could increase security.
If you don't want to prioritize it for other purposes, I get it, and I won't bother you. But if you really want to drop it for security purposes, I humbly request you to elaborate and reconsider.
If you are referring to the general problem of leaking security-sensitive details through exception details, then in this case, I don't see the problem:
Firstly, as mentioned, HotChocolate already allows globally enabling/disabling exception details. I could already shoot myself in the foot by enabling it globally across all environments (which of course I won't). My suggestion is more fine-grained, e.g. enabling only when authenticated as specific users, as in my use-case. (If someone were to steal the credentials to my integration test user, then I have much bigger problems than them having access to exception details.) Security-wise, my proposal is a subset of the current global enable/disable functionality. It does not add additional risk, and in fact can improve security by allowing users to be more fine-grained (e.g. only enable it for superusers or manual/integration test users) whereas the current functionality could push devs to enable it in e.g. semi-open QA environments, which is not safe.
Secondly, the proposed feature would be in the same category as other current authorization-related request-specific functionality such as allowing/disallowing introspection using IQueryRequestBuilder.AllowIntrospection.

Hi, just following up on this. I kindly ask you to either re-open this issue, or provide rebuttals to my arguments.

Hi, just a friendly reminder that I would like this issue re-opened, or alternatively that my arguments are met with compelling counterarguments.


Type is not supported, please register

Type is not supported, occurs invalid error: List`1 InnerException:System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: Type is not supported, occurs invalid error: ProductHomepageModel InnerException:System.InvalidOperationException: Type is not supported, please register CompletionField
The CompletionField is needed for Elasticsearch suggest feature.
I tried with Formatter.RegisterArray<CompletionField>() but RegisterArray() was not found.
How can I fix this?

CompletionField should be properly decored with [ZeroFormatterAttribute] and [Index(n)] attributes. If you can't because of it is not your own code you should implement a specific CompletionField Formatter, see Extensibiliti section in wiki area.

Same here with proper attributes... Did you find any fix ?

same for me, also with proper attributes..


Biography for condensed version

We need the biography for the teachingRSE project. It counts towards the word count of the Dagstuhl seminar series book.

we should move this together with the acknowledgements.


config.guess, config.sub files for proj-4 outdated for Summit

I got the following error when trying to install UCVMC, cybershake_18_8 tag on Summit:
checking build system type... ./config.guess: unable to guess system type
This script, last modified 2007-03-06, has failed to recognize
the operating system you are using. It is advised that you
download the most up to date version of the config scripts from
http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.guess
and
http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.sub
If the version you run (./config.guess) is already up to date, please
send the following data and any information you think might be
pertinent to<EMAIL_ADDRESS>in order to provide the needed
information to handle your system.
config.guess timestamp = 2007-03-06
uname -m = ppc64le
uname -r = 4.14.0-49.18.1.el7a.ppc64le
uname -s = Linux
uname -v = #1 SMP Thu Nov 29 03:27:24 EST 2018
/usr/bin/uname -p = ppc64le
/bin/uname -X     =
hostinfo               =
/bin/universe          =
/usr/bin/arch -k       =
/bin/arch              = ppc64le
/usr/bin/oslevel       =
/usr/convex/getsysinfo =
UNAME_MACHINE = ppc64le
UNAME_RELEASE = 4.14.0-49.18.1.el7a.ppc64le
UNAME_SYSTEM  = Linux
UNAME_VERSION = #1 SMP Thu Nov 29 03:27:24 EST 2018
configure: error: cannot guess build type; you must specify one
ERROR:
An error occurred while trying to setup UCVM. Specifically, the error was:
Error executing command.
At step: ['./configure', u'--prefix=/gpfs/alpine/proj-shared/geo112/CyberShake/software/UCVM/ucvm-cybershake_18_8/lib/proj-4', u'--with-jni=no']
I think the issue is that the config.guess and config.sub files which ship with proj-4.8.0 are too old to correctly handle Summit's architecture.  When I copied in the config.guess and config.sub files in automake on Summit (at /usr/share/automake-1.13/), I could configure proj-4 correctly.

We are moving to pro-5 in the new release and the config.guess and config. sub are both dated : timestamp='2017-04-02', should be able to recognize SUMMIT


TensorFlowSharp API Question: How to get a tensor by name

Hi everyone,
In the Python code that I am trying to move over to C#, it references an 'Output Node', like this;
output_node = tf.get_default_graph().get_tensor_by_name(name=FLAGS.output_node_names)
How would I replicate this in TensorFlowSharp? My model is saved and stored in a .bytes file (I'm using it in Unity). Thanks.

TensorflowSharp uses the model of.Pb file, usually I turn the model into.Pb file in Python, this process seems to be called "model persistence".
If you already have the.Pb model file, you can print out the graph and see what the name of the output node is.

@samueljlopes did you ever figure out how to do this?  I am trying to do the same.

its not all you need but this is how far i  could go (still looking for my outputs)
`
static public void AnalyzeGraphOpperations(TFGraph graph)
{
bool echo = false;
bool echo2 = true;
int n = 0;
string result = "";
List PlaceHoldersList = new List();
List VarsList = new List();
List outputListmaybe = new List();
List optypelist = new List();
        IEnumerable<TFOperation> tfgrph =  graph.GetEnumerator(); // get graph enumerator
        foreach (TFOperation op in tfgrph)
        {
            n++;
            if (echo) result += n + " " + op.OpType + "\t" + op.Name + " \n";
            if (op.OpType == "Placeholder") PlaceHoldersList.Add(op); // i think these are the inputs to the graph - mainly image
            if (op.OpType == "Variable" || op.OpType == "VariableV2") VarsList.Add(op);

            TFOperation[] oplist = op.ControlOutputs;
            if (oplist.Length > 0)
            {
                result += (n + " " + op.OpType + " \t" + op.Name + "\n");
                if (op.OpType == "Const" || op.OpType == "Assign" || op.OpType == "NoOp" || op.OpType == "Placeholder") result += "maybe but not likly output\n";
                else
                {
                    outputListmaybe.Add(op);
                    foreach (TFOperation opad in oplist)
                    {
                        result += "\t\t\t" + opad.OpType + "\t" + opad.Name + "\n";
                    }
                }
            }
        }
        if (echo2)
        {
            if (PlaceHoldersList.Count > 0)
            {
                result += "\nPlaceholders\n";
                foreach (TFOperation pl in PlaceHoldersList) result += pl.OpType + "\t" + pl.Name + " \n";
            }
            else result += "\ncould not find input placeholders\n";

            if (VarsList.Count > 0)
            {
                result += "\nVariable and VariableV2\n";
                foreach (TFOperation pl in VarsList) result += pl.OpType + "\t" + pl.Name + " \n";
            }
            else result += "\nCould not find Variable or VariableV2\n";

            if (outputListmaybe.Count > 0)
            {
                result += "\nThese may be my output\n";
                foreach (TFOperation pl in outputListmaybe) result += pl.OpType + "\t" + pl.Name + " \n";
            }
            else result += "\nCould not find outputs\n";
        }

`


Predicates of the form @de@<http://rdaregistry.info/Elements/u/P60470> in query result

When indexing data with QLever, sometimes strange values are returned for the predicates. To reproduce:
curl https://qlever.cs.uni-freiburg.de/api/dnb --data 'query=SELECT%20%3Fp%20%3Fo%20WHERE%0A%20%7B%0A%20%20%3Chttps%3A//d-nb.info/454818084%3E%20%3Fp%20%3Fo%20.%0A%20%7D' -X POST

This produces values that look like:
{
    "head": {
        "vars": [
            "p",
            "o"
        ]
    },
    "results": {
        "bindings": [
            {
                "o": {
                    "type": "bnode",
                    "value": "bn27771275"
                },
                "p": {
                    "type": "uri",
                    "value": "http://id.loc.gov/vocabulary/relators/aut"
                }
            },
---8<----   etc.  ---8<----
            {
                "o": {
                    "type": "literal",
                    "value": "mit Abb.",
                    "xml:lang": "de"
                },
                "p": {
                    "type": "literal",
                    "value": "@de@<http://rdaregistry.info/Elements/u/P60470>"
                }
            }
        ]
    }
}

Notice the weird literal shown as a predicate, as if there was a linebreak issue in parsing the source data. Here we are showing one of the example datasets provided by the authors, the DNB set.
But this has also happened in some cases for triples that I have created myself, where I could verify that the input triples did not seem malformed.

Just to make sure that I understand your question correctly:
Are you wondering about the strange predicate @de@<http:....>  which is (wrongly) marked as a literal?
Those predicates and their triples are artifacts of QLever's implementation of language filters. They are currently leaked for queries without a fixed predicate in all triples (your predicate is a variable ?p).
It is on our list to fully hide these triples (wrt to exports/query results/ statistics) such that this can't happen.
Thanks for reporting this, we now have an issue to track. It is also interesting to see, how these triples currently interact with the JSON exporter.
Please confirm that I have correctly identified your issue.

Thanks for the answer, yes I was wondering about the predicates being marked as literals in the SPARQL query results.
First time I saw something like this was in a CMS vendor publishing their Linked Data one year ago. Filed a bug report there, but  never heard back from them. Now we know that they are using QLever as a triplestore "under the covers" ;-)
I am new to QLever, just ran some tests ingesting data last week and noticed the strange output. At first I thought it was something wrong in my own data, but then noticed it was also in the sample datasets provided. (and I recalled seeing this previously elsewhere, as mentioned)
Look forward to learning more about the internals later, good to know that this is an implementation artefact and will eventually disappear.

@epoz Interesting story, which CMS vendor was this? Is there a issue on their GitHub or was this some internal bug tracker?

It is a Dutch CMS for cultural heritage content: https://kleksi.com/nl/home
Their service is not open source, and does not have a bug tracker. I submitted a request to their support@ mail, and received a reply via email later from the owner that they would pass my query on to their tech department. Never heard back from them, and I did not consider it important enough to follow up.
This was the event where we were spelunking for interesting data sources.


PHP8 bugfixes

@123andy - Hey Andy, are you still reachable here? Your Stanford email appears to be disconnected. Are you able to merge this and make a release? Otherwise, I can talk to @mmcev106 to accept releases from my fork.

@grezniczek unfortunately, andy is no longer at stanford, but just merged your pull request. thanks!

@yjael, thanks for merging. Would you mind making a new release as well? v1.4.8. Can you submit to the EM Repository (https://redcap.vanderbilt.edu/surveys/?s=X83KEHJ7EA). But once a release is made, I guess I could fill the form as well. Please keep me updated. Thanks!


Attach sanity check for run_python_code

Codecov Report

Merging #203 (c652564) into master (a22c619) will decrease coverage by 1.96%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##            master     #203      +/-   ##
===========================================
- Coverage   100.00%   98.03%   -1.97%
===========================================
  Files           23       23
  Lines         2597     2593       -4
===========================================
- Hits          2597     2542      -55
- Misses           0       51      +51

Impacted Files
Coverage Δ

src/viztracer/patch.py
81.72% <0.00%> (-18.28%)
:arrow_down:

src/viztracer/main.py
94.85% <0.00%> (-5.15%)
:arrow_down:

src/viztracer/viztracer.py
95.06% <0.00%> (-4.94%)
:arrow_down:

src/viztracer/code_monkey.py
98.33% <0.00%> (-1.67%)
:arrow_down:

src/viztracer/simulator.py
98.38% <0.00%> (-1.62%)
:arrow_down:

src/viztracer/viewer.py
99.60% <0.00%> (-0.40%)
:arrow_down:

src/viztracer/cellmagic.py
100.00% <0.00%> (ø)

src/viztracer/prog_snapshot.py
100.00% <0.00%> (ø)

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 a22c619...c652564. Read the comment docs.


Navigation: Add link to Academy into lower menu

Summary of the changes / Why this is an improvement
Adding link to Academy should increase visibility, sessions. Crosslinking is also good in general
Preview
https://crate-docs-theme--526.org.readthedocs.build/en/526/
Checklist

[ ] Link to issue this PR refers to (if applicable): https://github.com/crate/crate-docs-theme/issues/525
[x] CLA is signed

@matkuliak while we're at it, shouldn't we open those links in a new window with target="_blank"?

Oh yes, totally agreed. Thanks for the suggestion!
Will add a patch if @amotl isn't vehemently against.


Explore UI/UX for the Nomios mobile based wallet

Description
Users use their mobile devices everyday. For convenience there should be a native mobile version of Nomios so that the user can carry is identity wallet everywhere.
At first, we will research the best UI/UX for this future implementation.
Acceptance Criteria

[ ] Research a few UI/UX elements for the mobile version of Nomios.

@satazor @PedroMiguelSS @PedroMiguelSS as you guys know, the focus of the first milestone was predict and design the main features for the app, with this in mind we only adjusted the most flexible flow #20 (lock-screen) for the mobile breakpoint. Everything else needs to be created from scratch.
Thanks.


[BUG] C2440 error for complex square root on Windows

Describe the bug
The following code produces these conversion errors
error C2440: 'function': cannot convert from '__pyx_t_double_complex' to '_Dcomplex'
warning C4024: 'csqrt': different types for formal and actual parameter 1
error C2440: '=': cannot convert from '_Dcomplex' to '__pyx_t_double_complex'

The reason, I believe, is that __Pyx_c_prod_double returns __pyx_t_double_complex but sqrt expects _Dcomplex on Windows MSVC since for some reason it is not subject to cython's magic handling of double complex.
Code to reproduce the behaviour:
from libc.complex cimport csqrt
cdef double complex a = 3
cdef double complex b = 4
cdef double complex s = csqrt(a*b)

Expected behaviour
No error
OS
Windows
Python version
No response
Cython version
3.0.11
Additional context
No response

since for some reason it is not subject to cython's magic handling of double complex.

It's because MSVC's handling of C standard library complex is broken to non-existent.
If you can, compile it in C++ mode since MSVC's C++ standard library is a lot better.
I do have a vague plan to try to improve this at some point, since there are a whole bunch of complex types which all have the same memory layout so could all be used pretty interchangeably so long as Cython understood that they're all the same. It remains a vague plan though. And getting it to play nice with MSVC may be the hardest bit.

Thanks! Compiling as c++ worked.


HHH-12939 - Database name not quoted at schema update

@pbruski @vladmihalcea I suggest a slightly different approach: https://github.com/hibernate/hibernate-orm/pull/2512/commits/3816c26a3a6f52ae5fd93939ae2897985b2d44d3 .
Why use the TableInformation elements and quote them if the elements of Table are quoted instead of simply using the ones from Table?
I think the elements of Table are what we want.
@vladmihalcea could you take a look and check that my assumption is right?
If so, I'll extract my commit from this PR and apply it as a fix.

@gsmet The QualifiedTableName just qualifies the path (e.g. catalog.schema.table), it does not quote the path automatically. If we apply the same logic you did in this commit, how would we escape a table that contains an illegal character like -, as described in HHH-12939?

@vladmihalcea you are using schema.isQuoted() to decide if you should escape the TableInformation schema with quotes. So I suppose the schema Identifier is already properly quoted if it needs to be.
Otherwise the existing code wouldn't work.

@gsmet Let's add another test case to validate your findings then. That's the best way to make sure we handle it properly.

@gsmet I thought that the intention was to always include the catalog in the alter table. For that to happen, the data has to come from TableInformation (Table doesn't have to have it) and has to be quoted before use.

I don't think that's the original intention. In any case, it's not very consistent with the rest as the other commands are not qualified with the catalog. My version improves consistency and is far more readable.
I'll see if I can add a test case.

@vladmihalcea done here: https://github.com/hibernate/hibernate-orm/pull/2526 .

Superseded by https://github.com/hibernate/hibernate-orm/pull/2528 .