Error: while building for IOS only

I have added this package to my application and it works perfectly with android and web with online and file videos that supper great but when i wanted to try it with IOS it was working and at some point stoped working honestly I dont know what did i do this is what im getting:
Error Log:
Launching lib/main.dart on iPad Pro (11-inch) (4th generation) in debug mode...
main.dart:1
Xcode build done.                                           10.6s
Failed to build iOS app
Error (Xcode): Undefined symbol: _MDK_setLogHandler

Error (Xcode): Undefined symbol: _mdkPlayerAPI_delete

Error (Xcode): Undefined symbol: _mdkPlayerAPI_new

Error (Xcode): Linker command failed with exit code 1 (use -v to see invocation)

Could not build the application for the simulator.
Error launching application on iPad Pro (11-inch) (4th generation).
Exited

this is one example of usage :
// ignore_for_file: public_member_api_docs, sort_constructors_first

import 'package:flutter/material.dart';
import 'package:flutter/services.dart';
import 'package:flutter_meedu_videoplayer/meedu_player.dart';

class CustomVideoPlayerWidget extends StatefulWidget {
  final String videoUrl;

  const CustomVideoPlayerWidget({
    Key? key,
    required this.videoUrl,
  }) : super(key: key);

  @override
  // ignore: library_private_types_in_public_api
  _CustomVideoPlayerWidgetState createState() =>
      _CustomVideoPlayerWidgetState();
}

class _CustomVideoPlayerWidgetState extends State<CustomVideoPlayerWidget> {
  final _meeduPlayerController = MeeduPlayerController(
    loadingWidget: const Center(
      child: CircularProgressIndicator(),
    ),
    initialFit: BoxFit.contain,
    pipEnabled: true,
    manageBrightness: false,
    screenManager: const ScreenManager(
      forceLandScapeInFullscreen: true,
      hideSystemOverlay: true,
    ),
  );

  @override
  void initState() {
    super.initState();
    _meeduPlayerController.setDataSource(
      DataSource(
        type: DataSourceType.network,
        source: widget.videoUrl,
      ),
      autoplay: true,
    );
  }

  @override
  void dispose() {
    _meeduPlayerController.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return MeeduVideoPlayer(
      controller: _meeduPlayerController,
    );
  }
}

Version:
Flutter 3.13.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision efbf63d9c6 (6 days ago) • 2023-08-15 21:05:06 -0500
Engine • revision 1ac611c64e
Tools • Dart 3.1.0 • DevTools 2.25.0

Notes*
I already added '  initMeeduPlayer(); ' to main
Already added this in info.plist
<key>NSAppTransportSecurity</key>
<dict>
  <key>NSAllowsArbitraryLoads</key>
  <true/>
</dict>

Aslo the minimum IOS version is on 14
I will gladly provide more information if needed

One question is it possible to force the player to use rtl or ltr ?

I have added this package to my application and it works perfectly with android and web with online and file videos that supper great but when i wanted to try it with IOS it was working and at some point stoped working honestly I dont know what did i do this is what im getting:
Error Log:
Launching lib/main.dart on iPad Pro (11-inch) (4th generation) in debug mode...
main.dart:1
Xcode build done.                                           10.6s
Failed to build iOS app
Error (Xcode): Undefined symbol: _MDK_setLogHandler

Error (Xcode): Undefined symbol: _mdkPlayerAPI_delete

Error (Xcode): Undefined symbol: _mdkPlayerAPI_new

Error (Xcode): Linker command failed with exit code 1 (use -v to see invocation)

Could not build the application for the simulator.
Error launching application on iPad Pro (11-inch) (4th generation).
Exited

this is one example of usage :
// ignore_for_file: public_member_api_docs, sort_constructors_first

import 'package:flutter/material.dart';
import 'package:flutter/services.dart';
import 'package:flutter_meedu_videoplayer/meedu_player.dart';

class CustomVideoPlayerWidget extends StatefulWidget {
  final String videoUrl;

  const CustomVideoPlayerWidget({
    Key? key,
    required this.videoUrl,
  }) : super(key: key);

  @override
  // ignore: library_private_types_in_public_api
  _CustomVideoPlayerWidgetState createState() =>
      _CustomVideoPlayerWidgetState();
}

class _CustomVideoPlayerWidgetState extends State<CustomVideoPlayerWidget> {
  final _meeduPlayerController = MeeduPlayerController(
    loadingWidget: const Center(
      child: CircularProgressIndicator(),
    ),
    initialFit: BoxFit.contain,
    pipEnabled: true,
    manageBrightness: false,
    screenManager: const ScreenManager(
      forceLandScapeInFullscreen: true,
      hideSystemOverlay: true,
    ),
  );

  @override
  void initState() {
    super.initState();
    _meeduPlayerController.setDataSource(
      DataSource(
        type: DataSourceType.network,
        source: widget.videoUrl,
      ),
      autoplay: true,
    );
  }

  @override
  void dispose() {
    _meeduPlayerController.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return MeeduVideoPlayer(
      controller: _meeduPlayerController,
    );
  }
}

Version:
Flutter 3.13.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision efbf63d9c6 (6 days ago) • 2023-08-15 21:05:06 -0500
Engine • revision 1ac611c64e
Tools • Dart 3.1.0 • DevTools 2.25.0

Notes* I already added ' initMeeduPlayer(); ' to main Already added this in info.plist
<key>NSAppTransportSecurity</key>
<dict>
  <key>NSAllowsArbitraryLoads</key>
  <true/>
</dict>

Aslo the minimum IOS version is on 14
I will gladly provide more information if needed

were you using an older version?
i had to migrate from media_kit to fvp so if you were using a n older version that may be the cause
also can you try to compile the package example? since the github actions are working as expected i want to be sure if its a project problem or a main problem

I think the reason was the app was already running and i added this package with hot restart was fine and stated an ipad emulator to check the size and this happened, sorry when can i get the example so i can try and see what is the problem

now a very wired thing happened i got my physical device and run the application throw Xcode and it works fine i will try a couple of things see what is it my its my side, one small question is there a way to force the player from ltr to rtl or vice versa

now a very wired thing happened i got my physical device and run the application throw Xcode and it works fine i will try a couple of things see what is it my its my side, one small question is there a way to force the player from ltr to rtl or vice versa

i didnt try that before, maybe but for each part you can control that yes? not all of it at once

Good thank for helping i'm still trying to figure it out because my physical phone is on a beta version but i don't still i cant test it on Xcode for emulators will try to fix it for now i will close this

i was a problem from fvp on the simulator
fvp author comment
I've updated mdk in cocoapods. Now you can run pod repo update to update local indices, then run pod cache clean mdk and in example/ios run pod deintegrate
to fix it


rtdb Lists document sample still used $ref

The documentation our rtdb lists here: rtdb lists
uses the $key property as follows:
<button (click)="updateItem(item.$key, updatetext.value)">Update</button>
<button (click)="deleteItem(item.$key)">Delete</button>

but in Ver 5 (according to the docs here version-5-upgrade indicates that you are:
Moving away from $key and $value
The sample provided on the first reference therefore does not work anymore with "angularfire2": "^5.0.0-rc.2",

Thanks, will address.

the topic is about $ref, not $key
looks like $ref is also missing, used to make a transaction calls like that
this.afd.object(path).$ref.transaction(...

any clue how to deal with it after upgrde to 5 ?

ok, I guess this will be
this.afd.object(path)
.snapshotChanges()
.subscribe( action => action.payload.ref.transaction(...));

?

i'm having the same issue with $key. has the sample app in rtdb/list.md been updated yet?

all is explained in the migration docs https://github.com/angular/angularfire2/blob/master/docs/version-5-upgrade.md

@kleeb , yes, maybe some kind of explanation,  but what essentially happened here is that RDDB went from BETA to MATURE with a lot of CORE changes suddenly thrown in which effect angularfire2 (/5) quite a lot.
The native Firebase SDK might be fairly mature, but AngularFire2 (ver 4) is essentially being thrown out the window. I don't think the Google guys did a great job in making life easier for angular users.
If anything, they really need to put better effort into the documentation if they want to drive out rapid changes.
Sometime they need to stop selling new features and make sire the current features (which they sold us yesterday) is still properly documented and supported. If not, they should have called it angularfireX and not Ver 5 of angularfire2.
@davideast , as much as we love your videos, we kind of dread reading your/(the) docs.
And Videos always only deals with the simple stuff.. documentation deals with the real issues we handle when trying to build large scalable systems.

Maybe thats why its RC. Anyway I still vote for @davideast playing with the core dev instead of writing great doc and samples. They will come up in time.

@gerhardcit AngularFire2 is not mature, yet. It is in RC. Having solid documentation is required before we go final. We will be doing major documentation work in the near future. However, we are still trying to add features to the library like SSR support and async loading. Designing and implementing AngularFirestore was also a large task. It was a hard decision to deprecate version 4 of the RTDB, but we wanted to provide a similar API for Firestore and the RTDB.
What are you referring to when you say "large scalable systems"? I am always open to suggestions for improving the documentation so please respond with your thoughts.
I do suggest reading the official Firebase documentation. This library is a convenience for Angular developers and it's still the Firebase SDK under the hood.
@kleeb Thanks for the vote of confidence 😃

I am also closing this issue as we have fixed this in the documentation.


Avatar In User Class Should Be Optional

The code below will throw an exception if the avatar is null. This will happen when the user does not have a custom avatar, some sort of check needs to be added or making the avatar Optional[str] and setting a default.
class User(BaseModel):
    id: str
    username: str
    discriminator: str
    avatar: str
    avatar_url: Optional[str]
    locale: str
    email: Optional[str]
    bot: Optional[bool]
    mfa_enabled: bool
    flags: int
    premium_type: Optional[int]
    public_flags: int

    def __init__(self, **data: Any):
        super().__init__(**data)
        self.avatar_url = f"https://cdn.discordapp.com/avatars/{self.id}/{self.avatar}.png"

This will then throw an validation_error from the pydantic module.

Already fixed in a newer version of the module.


Refactor mnemonics

Purpose
This PR adds missing mnemonics and reorders the already existing mnemonics to match with the order of the instruction codes.
Resolves #12220

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-0.990.0@9e68bc7). Click here to learn what that means.
The diff coverage is 0%.

@@                Coverage Diff                 @@
##             release-0.990.0   #12823   +/-   ##
==================================================
  Coverage                   ?   59.86%
  Complexity                 ?      659
==================================================
  Files                      ?     2068
  Lines                      ?   101670
  Branches                   ?    12931
==================================================
  Hits                       ?    60863
  Misses                     ?    35616
  Partials                   ?     5191

Impacted Files
Coverage Δ
Complexity Δ

.../org/wso2/ballerinalang/programfile/Mnemonics.java
0% <0%> (ø)
0 <0> (?)

...java/org/ballerinalang/util/codegen/Mnemonics.java
0% <0%> (ø)
0 <0> (?)

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 9e68bc7...8a9a3b9. Read the comment docs.


chore: automated PR to update VHDVersion for 202307.10.0 VHD

This is an automated PR to bump VHDVersion for the VHD release with image version 202307.10.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall First build on imageBump/202307.10.0 at 61.542%

Totals

Change from base Build<PHONE_NUMBER>:
61.5%

Covered Lines:
2570

Relevant Lines:
4176

💛  - Coveralls


Failed to open "capture.rdc" for replay. Network I/O operation failed.

Description
I'm having the following error while trying to open a capture made on an Adroid device:

It's the same if the capture is opened from the device, or saved locally and then opened.
It doesn't happen in other devices I own, only on this one (that happens to be needed to reproduce an issue with that GPU).
Steps to reproduce
Looks like it happens with the common workflow of capturing and opening the capture afterwards.
capture sample
Environment

RenderDoc version: 1.25
Operating System: Windows 10, Ubuntu 22.04
Graphics API: Vulkan
The problematic device is: Android 10 armeabi-v7a, Samsung SM-M105M, GPU Mali-T830 MP1, Vulkan. I Tried with another device and works well.

This capture contains invalid use of Vulkan. There is a renderpass being created with one color attachment where the VkAttachmentReference contains a value of attachment =<PHONE_NUMBER> which is not a valid value. This causes an invalid index and then a crash while loading which leads to the disconnect.
I would recommend running your program with the validation layers (I'm not sure how/if that's possible on android but I assume so) to catch errors like this, as RenderDoc does not handle invalid API use.


undefined is not an object evaluating '_reactNativeBottomsheet2.default.showBottomSheetWithOptions'

I'm gettings this error when trying this on Android:
BottomSheet.showBottomSheetWithOptions({
options: SORT_OPTIONS,
title: Strings.Sort,
dark: true,
cancelButtonIndex: SORT_OPTIONS.length - 1,
}, (value) => {
this.sort(value);
});

BottomSheet is always undefined in Android.
react-native: 0.48
react: 16.0.0-alpha.12
react-native-bottomsheet: 1.8.1

+1

news?

Have you linked it yet?
react-native link react-native-bottomsheet

I fix this issue by adding the following code to MainApplication.java
import com.clipsub.rnbottomsheet.RNBottomSheetPackage; // Import this

....
@Override
protected List<ReactPackage> getPackages() {
  return Arrays.<ReactPackage>asList(
       new RNBottomSheetPackage() // Add this
  );
}

I hope it help

I still get this error although I linked as mentioned in README. Any solution?

@mstfymrtc you have to do the i said in a comment above

MainApplication.java file already contain lines which you wrote.


Incompatibility with hedgehog-1.0

This appears particularly in the TimeGen testing module, and is affected by the following from the hedgehog CHANGELOG:

Simplify MonadGen, this breaks the use of StateT on the outside of a GenT for the time being, it still works fine on the inside though and you can use distributeT to run it

since there seems to be a StateT around a GenT at the top of whatever is running these tests.

Notice in particular that the unicode function has has its contraints changed from:
unicode :: MonadGen m => m Char

to
unicode :: (MonadGen m, GenBase m ~ Identity) => m Char

Would it suffice to use the unicodeAll function instead, which doesn't seem to have the funky GenBase constraint?

@fosskers I think we don't want to use unicodeAll because that produces invalid unicode sequences. I am looking into this.

This is tricky with the GenBase m ~ Identity constraint on functions like unicode. It means we can't have StateT inside of GenT, but at the same time we can't have StateT outside of GenT. It seems we'd also be unable to do something like Reader+IORef instead because that would require GenBase of IO? Maybe we should just wait a bit on this to see if see hedgehogqa/haskell-hedgehog#287 gets resolved upstream? Any other thoughts @fosskers?

Does this comment in the CHANGELOG help at all?

Simplify MonadGen, this breaks the use of StateT on the outside of a GenT for the time being, it still works fine on the inside though and you can use distributeT to run it

Unfortunately that does not help from what I understand, because it's not possible for us to switch the order of StateT and GenT because we need GenBase m ~ Identity, not StateT _

Do we absolutely need the state? Is there a way around it what would simplify everything back down to just Gen?

Yeah, we need MonadState unless we were to make some significant changes. But it turns out that hedgehog master has a commit that's removed the GenBase m ~ Identity constraint for unicode, so we are now in the clear. I've created a draft PR that contains the fix for this (but where the nix build is broken until someone figures out how to integrate hedgehog 1.0 into it): #636.

Is it possible to allow for hedgehog-1.0 compat without forcing the upgrade?

I might have been doing something wrong but I ended up having to make an elaborate chain of 10-15+ modifications to default.nix before I gave up.

One more option is to switch to latin1 (
http://hackage.haskell.org/package/hedgehog-1.0/docs/Hedgehog-Gen.html#v:latin1)
if
unicode is not available.
On Wed, Sep 11, 2019 at 2:03 PM Brian Schroeder<EMAIL_ADDRESS>wrote:

I might have been doing something wrong but I ended up having to make an
elaborate chain of 10-15+ modifications to default.nix before I gave up.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/kadena-io/pact/issues/628?email_source=notifications&email_token=AACL5RNKOLFXV5SJGF42HQLQJFMKDA5CNFSM4ISVSUQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6P4M3Q#issuecomment-530564718,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACL5RL4QI22XK344GJFL5TQJFMKDANCNFSM4ISVSUQQ
.

A switch to latin1 would be a good option if we had a scenario where we could upgrade to 1.0 but not master, but it seems we should be safe to use these new commits that were added since 1.0. So unicode seems all set for use.

Can we prompt the hedgehog guys for a release?

They created a new release two days ago. I just incorporated it into #636.


Add serializeToBinDat/deserializeFromBinDat

Codecov Report

Merging #12 into master will increase coverage by 0.76%.
The diff coverage is 97.14%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
+ Coverage   81.11%   81.87%   +0.76%
==========================================
  Files          16       17       +1
  Lines        4315     4491     +176
==========================================
+ Hits         3500     3677     +177
+ Misses        815      814       -1

Impacted Files
Coverage Δ

voile/bindat.d
97.14% <97.14%> (ø)

voile/sync.d
72.45% <0.00%> (+0.79%)
: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 af780a7...ba648a2. Read the comment docs.


numpy-dispatch tests disabled for numpy 1.20

I am filing this issue to remember to turn back on the numpy-dispatch tests (in ci-build.yaml). I turned them off when trying to fix the numpy 1.20 issues. Now the rest of JAX works with numpy 1.20, but we are still keeping a pin to numpy<1.20 until we release the next jaxlib. At that point we should try to re-enable the numpy-dispatch tests.

@shoyer FYI

BTW, the error that I was seeing in Github CI was some binary incompatibility between some numpy datastructures (running with numpy 1.20 and the HEAD of numpy-dispatch).


pulseeffects: 4.8.0 -> 4.8.1

Motivation for this change
saw it was out of date
cc @jtojnar
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

was able to use the same qualities as the previous release


Added Audio file in #5953

Description 📜
06.02 Circular ImageView in android - Added Audio file
Fixed -  #5953
Type of change 📝

[x] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)

Domain of Contribution 📊

[x] Android Dev #(Kotlin)

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Hey @rahulsain , Checkout this PR and if everything is fine , Kindly marge it .

Hey @rahulsain , Checkout this PR and if everything is fine , Kindly marge it .


Fixes for going via gateways

A couple of issues

it was doing some key magic which is not necessary and broke
it could only handle setting one bastion host for each run. update it so that each node can have their own bastion host configured

Whoops, meant to submit that to our fork repo!


Wrong data at "Service Problems", "Unhandled Services" and "Problems" at the to view.

Expected Behavior
In view at "Service Problems", "Unhandled Services" and "Problems" no problems should be displayed.
In detailed host and service view below, there are no problems displayed.
In Icinga2 Web2 GUI, there are no problems displayed too.
Current Behavior
In view at "Service Problems", "Unhandled Services" and "Problems" are wrong or maybe old data will be displayed.
BUT in detailed host and service view below, there no problems displayed.
In Icinga2 Web2 GUI, there are still no problems.
Possible Solution
How can I check from where and how dashing-icinga2 receives the data?
Steps to Reproduce (for bugs)

In Icinga2 Web2 GUI - NO problems where displayed - (there are really no problems at this time)
Open dashing-iicnga2 - in "Service Problems", "Unhandled Services" and "Problems" problems will be displayed.

Context
See screenshot:

Your Environment

Dashing version (gem list --local dashing):

# gem list --local dashing

*** LOCAL GEMS ***

dashing (1.3.7)

Ruby version (ruby -V):

# ruby -v
ruby 2.0.0p648 (2015-12-16) [x86_64-linux]

Version of this project (tarball name, tag name or git show -1):

VERSION=2.0.0

Modifications to this project, if any (git diff):
NO
Operating System and version:
CentOS-7 (7.7.1908)
Client browser and version:
Windows - Firefox 70.0

Hi,
sorry for that issue, with VERSION 3.0.0 it work's as expected.
Sorry,
Klaus.


Aromaticity of non-protein molecules in PDB not detected

The PDB reader does not seem to assign aromaticity correctly for non-protein molecules, see this example which reads in 3 different versions of the small molecule benzamidine:
The .pdb file retrieved from rcsb (rcsb: 3ptb):
BEN_pdb_rdkit = Chem.MolFromPDBFile("3ptb_BEN.pdb", removeHs=False, sanitize=True)
AllChem.Compute2DCoords(BEN_pdb_rdkit)
Chem.Draw.MolToFile(BEN_pdb_rdkit, osp.join(masttmpdir, "BEN_pdb.png"))

The same .pdb file as before with hydrogens added:
BEN_Hs_pdb_rdkit = Chem.MolFromPDBFile("BEN+Hs_3ptb.pdb", removeHs=False, sanitize=True)
AllChem.Compute2DCoords(BEN_Hs_pdb_rdkit)
Chem.Draw.MolToFile(BEN_Hs_pdb_rdkit, osp.join(masttmpdir, "BEN_Hs_pdb.png"))

The .mol file retrieved from chemspider (chemspiderID: 2242).
BEN_mol_rdkit = Chem.MolFromMolFile("benzamidine.mol", removeHs=False, sanitize=True)
AllChem.Compute2DCoords(BEN_mol_rdkit)
Chem.Draw.MolToFile(BEN_mol_rdkit, osp.join(masttmpdir, "BEN_mol.png"))

The first two (pdbs) incorrectly do not assign aromaticity to the ring
The mol correctly identifies the aromatic rings.
I would just use the .mol but the atom ordering is different making it a real pain to translate them.
Additionally the protein has the correct assignments as far as I can tell.
3ptb_BEN.pdb.txt
BEN+Hs_3ptb.pdb.txt
benzamidine.mol.txt

Assigning bond orders to arbitrary molecules from PDB data is a subtle and difficult thing. The RDKit doesn't even try.
What you can do is use the combination of a mol file or a SMILES together with the PDB molecule to get a version of the molecule with the PDB atom numbering and coordinates but correct bond orders. The function to do this is AllChem.AssignBondOrdersFromTemplate.
The documentation is here:
http://www.rdkit.org/Python_Docs/rdkit.Chem.AllChem-module.html#AssignBondOrdersFromTemplate
There are some examples of using it here:
http://www.rdkit.org/docs/Cookbook.html#d-functionality-in-the-rdkit

Thanks Greg! Just another reason to love the PDB format.

I'm going to close this because I think the question is answered. Please re-open if you want to followup.

BEN_MOL_rdkit = Chem.MolFromMolBlock("benzamidine.mol", sanitize=True)
BEN_PDB_rdkit = Chem.MolFromPDBBlock("BEN+Hs_3ptb," removeHs=False, sanitize=True)
BEN_rdkit = AllChem.AssignBondOrdersFromTemplate(BEN_MOL_rdkit, BEN_PDB_rdkit)

This almost works for me, up until the call to SanitizeMol in AllChem.AssignBondOrdersFromTemplate (line 503) I get this error message:
ValueError: Sanitization error: Explicit valence for atom # 2 N, 4, is greater than permitted

I used GetTotalValence on each atom before the call to SanitizeMol and the Ns both returned 3. However, after the call (in ipdb debugger) the second one had been altered to 4. I couldn't step into SanitizeMol, so that is all I know.
I think the unsanitized molecule would give me all I need anyhow as I only need if the atom is aromatic, which is already set.

This is related to #1029, but unfortunately the fix for that is unlikely to help here.
The specific problem here is that the amidine group in the PDB ligand is protonated: both Ns have two Hs attached. This means that one has to have a + charge, which it doesn't in that PDB file.
The + charge that's required to make the ligand sensible will make it so that the benzamidine from the mol file, which doesn't have that + charge, isn't a match. To be fair, it's not a match.
Since the solution to #1029 is going to end up working only for amino acids (where the connectivity is known in advance), managing the same thing for the ligand is likely going to require a different implementation. I'm going to have to think about it for a bit, but I don't think this is a general use case. It's probably better to write some special-purpose code to manage these situations.

FYI, there is at least one extension to the PDB where the connect records are duplicated to indicate single, double and triple bonds.  It is not a bad thing to support for internal round tripping.  I'll see if I can get an example.

Have you tried the AssignBondOrdersFromTemplate function from #886 ? You can just copy it to your code and it should work. I found it to be more robust, but yet needs some polish on my side to merge it to master. What it does is removing extra bonds an disconnected fragments from your template using inverse matching (mol -> template) and/or MCS.


fix Process available memory to increase the Jemalloc cache

What problem does this PR solve?
Currently, when the Doris BE process exceed memory limit, Jemalloc cache will be manually released.
Add the Jemalloc cache to the available memory of the BE process is expected to have little impact on the risk of the process OOM killer. the process memory used has already subtracted the Jemalloc cache.
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[x] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[x] Other reason

Behavior changed:

[ ] No.
[x] Yes.

Does this need documentation?

[ ] No.
[x] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall


Cleanup mesh and ini filename handling

@jourdain I was have some issues running the PyFR workflow, I saw you made a few changes ( thanks ). I think this should clean things up.

ok cool. I had to do some changes as the id provided was not taking care of, but I guess you went even further and delete the code for extracting the info from the item.... ;-)


[3.1.x] Added admin translatable string.

I never know if pushing the green button will push to the right branch with the right prefixed message. Should I do that?

Should I do that?

Yes, it works :+1:  :green_circle:

Thanks, but no, it didn't work completely as the commit message is not the right one (sorry for that). Nothing better than the command line :smile:


Can't figure out this 400 Error

Hi @bennycode,
First thanks for the hard work this is an awesome project.
Unfortunately I do seem to have come to a dead end in my project and can't figure out the issue at this point.
I'm trying to place an order using the rest client and this is what I get back:
    at createError (.../node_modules/coinbase-pro-node/node_modules/axios/lib/core/createError.js:16:15)
    at settle (.../node_modules/coinbase-pro-node/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (.../node_modules/coinbase-pro-node/node_modules/axios/lib/adapters/http.js:269:11)
    at IncomingMessage.emit (events.js:323:22)
    at endReadableNT (_stream_readable.js:1204:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:13720) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
(node:13720) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

This is the Api call I'm making:
const order = await this.client.rest.order.placeOrder(data)

This is the data I'm passing to the call:
data:  {
  product_id: 'SOL-USD',
  type: 'market',
  client_oid: '0ceca3ed-2591-42a8-8051-c5631eebc780',
  funds: 10
}

Any ideas?
Thanks again

Hi @latifs, can you please add a catch to your placeOrder call or surround it by a try-catch, so that we can see the error.message?

For sure @bennycode,
here's my whole function:
async buy({ price, funds }) {
    if (!this.isLive) {
      return { size: funds / price, price: price };
    }

    if (this.state !== 'running') return null;
    this.state = 'buying';  //update my state

    const token = uuidv4();
    this.tokens[token] = 'buy';

    const lock = () => {
      return new Promise((resolve, reject) => {
        this.callbacks[token] = resolve;
      });
    };

    try {
      const data = this.generateMarketData({ token, funds });
      const order = await this.client.rest.order.placeOrder(data);

      console.log('order:', order);

      if (order.message) {
        this.state = 'running';
        throw new Error(order.message);
      }

      const filled = await lock();
      this.state = 'running';
      return filled;
    } catch (error) {
      this.state = 'running';
      throw error;
    }
  }

the generateMarketData function returns this data:
data:  {
  product_id: 'SOL-USD',
  type: 'market',
  client_oid: '0ceca3ed-2591-42a8-8051-c5631eebc780',
  funds: 10
}

Unless it is coming from somewhere else, I'm not quite sure but the error appears right around I place the order.

@bennycode,
I'm realizing now that the error could be coming from my Feed which I actually call In my constructor in the class in the previous code I sent.
const {
  CoinbasePro,
  WebSocketChannelName,
  WebSocketEvent,
} = require('coinbase-pro-node');

const config = require('../../configuration');

class Feed {
  constructor({ product, onUpdate, onError }) {
    this.product = product;
    this.onUpdate = onUpdate;
    this.onError = onError;
    this.running = false;
  }

  async start() {
    this.running = true;
    this.client = new CoinbasePro({
      apiKey: config.get('API_KEY'),
      apiSecret: config.get('API_SECRET'),
      passphrase: config.get('API_PASSPHRASE'),
      useSandbox: config.get('API_USE_SANDBOX'),
    });

    const channelUser = {
      name: WebSocketChannelName.USER,
      product_ids: [this.product],
    };

    const channelHeartbeat = {
      name: WebSocketChannelName.HEARTBEAT,
      product_ids: [this.product],
    };

    // ON_OPEN, we subscribe
    this.client.ws.on(WebSocketEvent.ON_OPEN, () => {
      this.client.ws.subscribe([channelUser, channelHeartbeat]);
    });

    // ON_MESSAGE
    this.client.ws.on(WebSocketEvent.ON_MESSAGE, (response) => {
      // console.log('response:', response);
      if (response.type === 'heartbeat') return;
      this.onUpdate(response);
    });

    // ON_ERROR
    this.client.ws.on(WebSocketEvent.ON_ERROR, (event) => {
      this.onError(event);
      this.client.ws.connect();
    });

    //ON_CLOSE
    this.client.ws.on(WebSocketEvent.ON_CLOSE, (event) => {
      if (this.running) {
        this.client.ws.connect();
      }
    });

    //we connect
    this.client.ws.connect();
  }

  stop() {
    this.running = false;
    this.client.ws.disconnect();
  }
}

module.exports = exports = Feed;

Hi @latifs, I got the stacktrace from you and the info that it is a HTTP error 400. Can you also get me the exact error message? You can get this by adding the following on top of your code:
process.on('unhandledRejection', error => {
  console.log('here comes the error message', error.message);
});


[<IP_ADDRESS>] Panic when writing empty data points via Ruby

I've been experimenting with InfluxDb <IP_ADDRESS> and found a weird bug which i cant replicate via CURL.
What im doing is just writing an empty string to the write enpoint with ruby:
require "faraday"
Faraday.post("http://<IP_ADDRESS>:8086/write?db=mydb", "\n")

Example above results in influxdb's panic:
2015/09/27 19:11:08 http: panic serving <IP_ADDRESS>:55438: runtime error: index out of range
goroutine 1755 [running]:
net/http.(*conn).serve.func1(0xc8213484d0, 0x7f4e221fef18, 0xc820e17f58)
	/home/philip/.gvm/gos/go1.5/src/net/http/server.go:1287 +0xb5
github.com/influxdb/influxdb/services/httpd.(*Handler).serveWriteLine(0xc82007d080, 0x7f4e221ff570, 0xc8209b6480, 0xc821236000, 0xc820f9ec00, 0x1, 0x200, 0x0)
	/tmp/build/src/github.com/influxdb/influxdb/services/httpd/handler.go:458 +0x1384
github.com/influxdb/influxdb/services/httpd.(*Handler).serveWrite(0xc82007d080, 0x7f4e221ff570, 0xc8209b6480, 0xc821236000, 0x0)
	/tmp/build/src/github.com/influxdb/influxdb/services/httpd/handler.go:376 +0x79c
github.com/influxdb/influxdb/services/httpd.(*Handler).(github.com/influxdb/influxdb/services/httpd.serveWrite)-fm(0x7f4e221ff570, 0xc8209b6480, 0xc821236000, 0x0)
	/tmp/build/src/github.com/influxdb/influxdb/services/httpd/handler.go:106 +0x48
github.com/influxdb/influxdb/services/httpd.authenticate.func1(0x7f4e221ff570, 0xc8209b6480, 0xc821236000)
	/tmp/build/src/github.com/influxdb/influxdb/services/httpd/handler.go:673 +0x70
net/http.HandlerFunc.ServeHTTP(0xc82012c4a0, 0x7f4e221ff570, 0xc8209b6480, 0xc821236000)
	/home/philip/.gvm/gos/go1.5/src/net/http/server.go:1422 +0x3a
github.com/influxdb/influxdb/services/httpd.gzipFilter.func1(0x7f4e221ff448, 0xc8209b6440, 0xc821236000)
	/tmp/build/src/github.com/influxdb/influxdb/services/httpd/handler.go:734 +0x2af
net/http.HandlerFunc.ServeHTTP(0xc82012c4c0, 0x7f4e221ff448, 0xc8209b6440, 0xc821236000)
	/home/philip/.gvm/gos/go1.5/src/net/http/server.go:1422 +0x3a
github.com/influxdb/influxdb/services/httpd.versionHeader.func1(0x7f4e221ff448, 0xc8209b6440, 0xc821236000)
	/tmp/build/src/github.com/influxdb/influxdb/services/httpd/handler.go:743 +0xc0
net/http.HandlerFunc.ServeHTTP(0xc82012c4e0, 0x7f4e221ff448, 0xc8209b6440, 0xc821236000)
	/home/philip/.gvm/gos/go1.5/src/net/http/server.go:1422 +0x3a
github.com/influxdb/influxdb/services/httpd.cors.func1(0x7f4e221ff448, 0xc8209b6440, 0xc821236000)
	/tmp/build/src/github.com/influxdb/influxdb/services/httpd/handler.go:776 +0x328
net/http.HandlerFunc.ServeHTTP(0xc82012c500, 0x7f4e221ff448, 0xc8209b6440, 0xc821236000)
	/home/philip/.gvm/gos/go1.5/src/net/http/server.go:1422 +0x3a
github.com/influxdb/influxdb/services/httpd.requestID.func1(0x7f4e221ff448, 0xc8209b6440, 0xc821236000)
	/tmp/build/src/github.com/influxdb/influxdb/services/httpd/handler.go:786 +0x15d
net/http.HandlerFunc.ServeHTTP(0xc82012c520, 0x7f4e221ff448, 0xc8209b6440, 0xc821236000)
	/home/philip/.gvm/gos/go1.5/src/net/http/server.go:1422 +0x3a
github.com/influxdb/influxdb/services/httpd.logging.func1(0x7f4e221ff448, 0xc8209b6420, 0xc821236000)
	/tmp/build/src/github.com/influxdb/influxdb/services/httpd/handler.go:794 +0x10b
net/http.HandlerFunc.ServeHTTP(0xc82012c540, 0x7f4e221ff448, 0xc8209b6420, 0xc821236000)
	/home/philip/.gvm/gos/go1.5/src/net/http/server.go:1422 +0x3a
github.com/influxdb/influxdb/services/httpd.recovery.func1(0x7f4e221ff3e8, 0xc821348790, 0xc821236000)
	/tmp/build/src/github.com/influxdb/influxdb/services/httpd/handler.go:804 +0x114
net/http.HandlerFunc.ServeHTTP(0xc82012c560, 0x7f4e221ff3e8, 0xc821348790, 0xc821236000)
	/home/philip/.gvm/gos/go1.5/src/net/http/server.go:1422 +0x3a
github.com/bmizerany/pat.(*PatternServeMux).ServeHTTP(0xc820022108, 0x7f4e221ff3e8, 0xc821348790, 0xc821236000)
	/tmp/build/src/github.com/bmizerany/pat/mux.go:109 +0x244
github.com/influxdb/influxdb/services/httpd.(*Handler).ServeHTTP(0xc82007d080, 0x7f4e221ff3e8, 0xc821348790, 0xc821236000)
	/tmp/build/src/github.com/influxdb/influxdb/services/httpd/handler.go:172 +0x357
net/http.serverHandler.ServeHTTP(0xc8201784e0, 0x7f4e221ff3e8, 0xc821348790, 0xc821236000)
	/home/philip/.gvm/gos/go1.5/src/net/http/server.go:1862 +0x19e
net/http.(*conn).serve(0xc8213484d0)
	/home/philip/.gvm/gos/go1.5/src/net/http/server.go:1361 +0xbee
created by net/http.(*Server).Serve
	/home/philip/.gvm/gos/go1.5/src/net/http/server.go:1910 +0x3f6

Panic also triggers Farday::ConnectionError in ruby code, which was unexpected behavior because server did not handle the connection properly.
The reason why its happening is simple: when making a HTTP call with Faraday, it will set content-type header to application/x-www-form-urlencoded and set empty body (new line \n). This behavior is correct although data is not.
Just wanted to bring this up.

Someone with Ruby experience could repro the issue above, using the Faraday library, and perform the write above. Be sure to create the database db first.
If the error occurs, then fix the panic.

Reproduced with curl as follows:
echo '' | curl -v "http://<IP_ADDRESS>:8086/write?db=mydb" --data-binary @-

Thanks @vwong

I'm able to repro this with <IP_ADDRESS>-1, happy to take a look into the panic.

Go for it @jademcgough

I just built from master and can't repro the issue there:
[http] 2015/11/07 10:30:41 <IP_ADDRESS> - - [07/Nov/2015:10:30:41 -0800] POST /write?db=mydb HTTP/1.1 204 0 - Faraday v0.9.2 a6541cf4-857d-11e5-8006-000000000000 68.875µs

irb(main):003:0> Faraday.post("http://localhost:8086/write?db=mydb", "\n")
=> #<Faraday::Response:0x007f8b8104e4d0 @on_complete_callbacks=[], @env=#<Faraday::Env @method=:post @body="" @url=#<URI::HTTP http://localhost:8086/write?db=mydb> @request=#<Faraday::RequestOptions (empty)> @request_headers={"User-Agent"=>"Faraday v0.9.2", "Content-Type"=>"application/x-www-form-urlencoded"} @ssl=#<Faraday::SSLOptions (empty)> @response=#<Faraday::Response:0x007f8b8104e4d0 ...> @response_headers={"content-encoding"=>"gzip", "request-id"=>"a6541cf4-857d-11e5-8006-000000000000", "x-influxdb-version"=>"0.9", "date"=>"Sat, 07 Nov 2015 18:30:41 GMT", "connection"=>"close"} @status=204>>

Yeah, neither can I using the curl command shown above.
Thanks for your help!

$ echo '' | curl -v "http://<IP_ADDRESS>:8086/write?db=mydb" --data-binary @-
* Hostname was NOT found in DNS cache
*   Trying <IP_ADDRESS>...
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 8086 (#0)
> POST /write?db=mydb HTTP/1.1
> User-Agent: curl/7.38.0
> Host: <IP_ADDRESS>:8086
> Accept: */*
> Content-Length: 1
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 1 out of 1 bytes
< HTTP/1.1 204 No Content
< Request-Id: 99a9ad81-8581-11e5-8006-000000000000
< X-Influxdb-Version: 0.9
< Date: Sat, 07 Nov 2015 18:58:57 GMT
<
* Connection #0 to host <IP_ADDRESS> left intact

Fixed in master so closed.


Make graphql function available in afterBuild

Issue: #715

Thanks for the PR, @cco3. My only concern with this change is that the store has to be in memory until the api.afterBuild() hook has run. I think we are going to remove the store right after the JSON-files have been generated in one of the next releases. But maybe we should add a new hook that runs either before or right after the "Execute GraphQL" step? For example a api.onExecuteQueries() hook?


On Hiding Step, Previous button not works

Hi,
This plugin is great,
I found an issue in this plugin, by fixing bugs this plugin would be more useful
When we hide any tab programmatically, then surprisingly 'Previous' button stops working,
This issue also persists in the given examples
Regards,
Naveed Yousaf

Thank you very much, Naveed. I will push this to the Rails gem as well. https://rubygems.org/gems/twitter_bootstrap_wizard_rails
~ Cheers!

@naveedyousaf09 you need to call refresh.


"Error": "BUG: glusterfs.GlusterFSVolume doesn't have required field Name"

Wow, this is confusing. I just filed this issue against the community catalog because I thought the glusterfs code was maintained outside of this repository, by someone in the community.
I'm hitting various issues that may be fixed in newer Convoy drivers, mainly around removing volumes with docker volume rm. Seeing that the community Gluster catalog used v0.3 of this repository, I tried upgrading to V0.7 to see what would happen. I got the error in this issue's title, and the log included below.
Any chance the Gluster driver will be updated to work in V0.7? I can't docker volume rm volumes because I suspect 0.3 isn't compatible with Docker 1.10.3.
Waiting for metadata
time="2016-06-23T02:00:14Z" level=info msg="Execing [/usr/bin/nsenter --mount=/proc/27301/ns/mnt -F -- /var/lib/docker/aufs/mnt/fcce70de21b33415a276d79b1bf8dd7ac1637e5e543cc1fcf77b37142c95726c/var/lib/rancher/convoy-agent/share-mnt --stage2 /var/lib/rancher/convoy/convoy-gluster-acf30ea9-00c1-46de-b7cc-fb2f0c31740f -- /launch volume-agent-glusterfs-internal]"
Waiting for metadata
Registering convoy socket at /var/run/convoy-convoy-gluster.sock
time="2016-06-23T02:00:15Z" level=info msg="Listening for health checks on <IP_ADDRESS>:10241/healthcheck"
time="2016-06-23T02:00:15Z" level=info msg="Got: root /var/lib/rancher/convoy/convoy-gluster-acf30ea9-00c1-46de-b7cc-fb2f0c31740f"
time="2016-06-23T02:00:15Z" level=info msg="Got: drivers [glusterfs]"
time="2016-06-23T02:00:15Z" level=info msg="Got: driver-opts [glusterfs.defaultvolumepool=my_vol2 glusterfs.servers=glusterfs]"
time="2016-06-23T02:00:15Z" level=info msg="Launching convoy with args: [--socket=/host/var/run/convoy-convoy-gluster.sock daemon --root=/var/lib/rancher/convoy/convoy-gluster-acf30ea9-00c1-46de-b7cc-fb2f0c31740f --drivers=glusterfs --driver-opts=glusterfs.defaultvolumepool=my_vol2 --driver-opts=glusterfs.servers=glusterfs]"
time="2016-06-23T02:00:15Z" level=debug msg="Creating config at /var/lib/rancher/convoy/convoy-gluster-acf30ea9-00c1-46de-b7cc-fb2f0c31740f" pkg=daemon
time="2016-06-23T02:00:15Z" level=debug msg= driver=glusterfs driver_opts=map[glusterfs.defaultvolumepool:my_vol2 glusterfs.servers:glusterfs] event=init pkg=daemon reason=prepare root="/var/lib/rancher/convoy/convoy-gluster-acf30ea9-00c1-46de-b7cc-fb2f0c31740f"
time="2016-06-23T02:00:15Z" level=debug msg="Cleaning up environment..." pkg=daemon
time="2016-06-23T02:00:15Z" level=error msg="BUG: glusterfs.GlusterFSVolume doesn't have required field Name"
{
	"Error": "BUG: glusterfs.GlusterFSVolume doesn't have required field Name"
}
time="2016-06-23T02:00:15Z" level=info msg="convoy exited with error: exit status 1"
time="2016-06-23T02:00:15Z" level=info msg=Exiting.

Duplicate of #121

Any idea when is this going to be fixed ?

I made a PR: #134
It should be merged soon.

PR #134 merged. But we're pulling the support for glusterfs in the foreseeable future due to resource limitation. Sorry about that...

Duplicate of https://github.com/rancher/convoy/issues/121 which was fixed in https://github.com/rancher/convoy/commit/2053eec006728ad83765c270879f3fbb00de6e05


Autocomplete doesn't work on aliases

Updated to 3.6.8 and using DB2.
Autocomplete doesn't work on aliases (used to work on 3.6.4).
Example:
select (autocomplete work)
from client
select c.(autocomplete doesn't work)
from client c

Duplicate of #467


cli: use SO_REUSEADDR with multicast addresses

This sets the SO_REUSEADDR socket option when the address is a multicast address.
This feature has been requested in #7.

@F5OEO I've checked with strace that this calls
setsockopt(4, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0

Can you check if this allows sharing the multicast address and port in your intended use case?

Force-pushing because I've realized that we can have the libc crate as an optional dependency, because it's only needed for the cli feature.

Merging, since this has been sitting for a while already.


Using srrg2_proslam without velodyne data

Hello,
Thanks for this new version I follow your project since srrg_proslam.
Why do I need the velodyne pointcloud in this version as normally it's only a stera-camera slam ? Is it to create the map?
Thank you for your job.

Hello,
I'm sorry I didn't get your problem. To use srrg2_proslam you do not need the LiDAR cloud.
Can you please be more specific?

Maybe I misunderstood the new operation with srrg2 then. When I run the slam from the srrg2_executor it will use the message.json file with the kitti dataset that uses Pointcloud? Or when I do this "run sync slam" it launches both of the Slam explained on your paper?
I also have a second question. Maybe you can help me. Is it possible to have a same view as on the srrg_proslam with the camera view on the GUI ? (See image in attachment)
Thank you for your help,
Loan

Hi @LoaBe
Consider the message.json file as a message container, like ROSBags. Thus, it stores all the messages that are acquired in the dataset gathering run.  Then, in your configuration file, you decide whether to read a message or not depending on the topic you subscribe.
For the second question, you can add as many canvases as you want using the terminal using the command:
add_canvas <name> <module>

The functionality of camera following is not implemented yet. The top view can be easily achieved moving the view using the cursor.


Add numpy~=1.17.5 dependency explicitly

This is to satisfy the older numpy dependency of aiida-core.
Closes #2

I think this change (numpy~=1.17.5) plus the dependency of optimade-client (numpy~=1.19) results in a broken environment. Don't you think so?

Yeah, this is now what I'm wondering if it will. Perhaps it will. It just seems crazy that one would need to downgrade the numpy version to satisfy possible out-of-date packages.

Yeah, this is now what I'm wondering if it will. Perhaps it will. It just seems crazy that one would need to downgrade the numpy version to satisfy possible out-of-date packages.

Just put numpy~=0.17 to the optimade client, and it will be alright.

Yeah, this is now what I'm wondering if it will. Perhaps it will. It just seems crazy that one would need to downgrade the numpy version to satisfy possible out-of-date packages.

Just put numpy~=0.17 to the optimade client, and it will be alright.

Sure, but that also seems extreme, is my point. Why not try to instead push for updating numpy in aiida-core and only then "revert" the dependency of an unrelated package?

Sure, but that also seems extreme, is my point. Why not try to instead push for updating numpy in aiida-core and only then "revert" the dependency of an unrelated package?

I am fine with any solution, to be honest. It is just not clear why it is set to <0.18 in aiida core, maybe there is a reason for that.

Sure, but that also seems extreme, is my point. Why not try to instead push for updating numpy in aiida-core and only then "revert" the dependency of an unrelated package?

I am fine with any solution, to be honest. It is just not clear why it is set to <0.18 in aiida core, maybe there is a reason for that.

The issue stems from pymatgen, which allows development versions of numpy, I believe. The person to latest experience this issue was @csadorf in setting up the requirements stuff for aiida-core.

Sure, but that also seems extreme, is my point. Why not try to instead push for updating numpy in aiida-core and only then "revert" the dependency of an unrelated package?

I am fine with any solution, to be honest. It is just not clear why it is set to <0.18 in aiida core, maybe there is a reason for that.

The reason is this one: https://github.com/aiidateam/aiida-core/commit/f5d6cba2baf0e7ca69b742f7e76d8a8bbcca85ae
We could try to unpin aiida-core and see if that breaks the installation/ or tests. This is something we have to do anyways sooner or later anyways. @CasperWA Do you want to give it a shot?

Made redundant by an update in AiiDA core.


fix: changing customizable values in config:set to lowercase

- What I did

reformatted variable names that are part of the ModifiableConfigs enum
carrying the abovementioned changes to all instances where the ModifiableConfigs enum was used
making necessary changes in functional tests and e2e tests
adding a couple of test cases in func_tests covering most of the values of ModifiableConfigs enum

- enum value modifications list

older enum values

commitLogCompactionFrequencyMins,
accessLogCompactionFrequencyMins,
notificationKeyStoreCompactionFrequencyMins,
autoNotify,
maxNotificationRetries

new enum values

commit_log_compaction_freq_mins,
access_log_compaction_freq_mins,
notification_keystore_compaction_freq_mins,
auto_notify,
max_notification_retries

- Description for the changelog

fix: changing customizable values in config:set to lowercase

commits from this pr have been merged into https://github.com/atsign-foundation/at_server/pull/1040. Closing this PR as the code will the part of the aforementioned PR


chore(TaskOrg): Add AC to all issues missing AC

Task Description
Some of our issues do not have acceptance criteria defined which could lead to misconfiguration. We need to identify those and populate them accordingly.
Acceptance Criteria:

[ ] All issues must have a description and at least one acceptance criteria outline.

List of Issues without AC:

https://github.com/cloudoperators/heureka/issues/81


chore) bump virtual-go/fs pkg

approve

Codecov Report

Merging #3 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master     #3   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          21     21
=====================================
  Hits           21     21

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 c809e30...b606800. Read the comment docs.


HBASE-26270 Provide getConfiguration method for Region and Store interface

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 56s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

-1 :x:
mvninstall
4m  8s
root in master failed.

+1 :green_heart:
compile
3m 18s
master passed

+1 :green_heart:
checkstyle
1m 13s
master passed

+1 :green_heart:
spotbugs
2m 12s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 11s
the patch passed

+1 :green_heart:
compile
3m 21s
the patch passed

+1 :green_heart:
javac
3m 21s
the patch passed

+1 :green_heart:
checkstyle
1m 12s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
20m 21s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
2m 23s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 13s
The patch does not generate ASF License warnings.

52m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3671

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 70d7be33c03b 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 922d0666a3

Default Java
AdoptOpenJDK-1.8.0_282-b08

mvninstall
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/1/artifact/yetus-general-check/output/branch-mvninstall-root.txt

Max. process+thread count
86 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@anoopsjohn Looking at the code, we use ReadOnlyConfiguration in CoprocessorEnvironment to prevent CPs change the configuration.
But we do have a getConnection method in CoprceossorEnvironment and it also has a getConfiguration method, which will return the Configuration object directly, should we also make it read only for CP?
And another problem here is that, the sub classes for Region and Store are not only used in CPs right? So making the getConfiguration method returns only read only copy of the Configuration object is not suitable, maybe we should name it getReadOnlyConfiguration?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  7s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 40s
master passed

+1 :green_heart:
compile
1m 15s
master passed

+1 :green_heart:
shadedjars
8m 24s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 47s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 36s
the patch passed

+1 :green_heart:
compile
1m 23s
the patch passed

+1 :green_heart:
javac
1m 22s
the patch passed

+1 :green_heart:
shadedjars
8m 35s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
the patch passed

_ Other Tests _

-1 :x:
unit
148m 14s
hbase-server in the patch failed.

182m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3671

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux abd59af55b11 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 922d0666a3

Default Java
AdoptOpenJDK-11.0.10+9

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/1/testReport/

Max. process+thread count
4038 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 20s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 16s
master passed

+1 :green_heart:
compile
1m  5s
master passed

+1 :green_heart:
shadedjars
8m 37s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 40s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 55s
the patch passed

+1 :green_heart:
compile
1m  3s
the patch passed

+1 :green_heart:
javac
1m  3s
the patch passed

+1 :green_heart:
shadedjars
8m 41s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
the patch passed

_ Other Tests _

-1 :x:
unit
162m 37s
hbase-server in the patch failed.

194m 58s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3671

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 799e14b429d3 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 922d0666a3

Default Java
AdoptOpenJDK-1.8.0_282-b08

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/1/testReport/

Max. process+thread count
3791 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@anoopsjohn Looking at the code, we use ReadOnlyConfiguration in CoprocessorEnvironment to prevent CPs change the configuration.
But we do have a getConnection method in CoprceossorEnvironment and it also has a getConfiguration method, which will return the Configuration object directly, should we also make it read only for CP?
And another problem here is that, the sub classes for Region and Store are not only used in CPs right? So making the getConfiguration method returns only read only copy of the Configuration object is not suitable, maybe we should name it getReadOnlyConfiguration?

+1 for making an explicit name.   BTW the config object what we get from Region and Store are a compound conf one?  I mean, we allow to make configs at table specific. For one table we can override a config value.  Now when we get the conf using this new method in Region, it will reflect this overridden value?  May be some thing we can check. I believe it might.
getConnection().getConf() exposing conf!  hmm.. May be we can see how to correct it. In another issue. I dont think within our code also, we do have any need to write/update anything to conf.  Whenever we need (like when we create connection for Replication etc), we will create new Conf object

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 20s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 14s
master passed

+1 :green_heart:
compile
1m  3s
master passed

+1 :green_heart:
shadedjars
8m 39s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 54s
the patch passed

+1 :green_heart:
compile
1m  2s
the patch passed

+1 :green_heart:
javac
1m  2s
the patch passed

+1 :green_heart:
shadedjars
8m 34s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 38s
the patch passed

_ Other Tests _

-1 :x:
unit
9m 47s
hbase-server in the patch failed.

41m 33s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/3671

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e5da2a334397 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / c60adfd13a

Default Java
AdoptOpenJDK-1.8.0_282-b08

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/2/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/2/testReport/

Max. process+thread count
1009 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3671/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 57s
Docker mode activated.

Ping @anoopsjohn


On Podman, detect if application is listening on the loopback interface, and either error out or not depending on --ignore-localhost

What type of PR is this:
/kind feature
/area dev
/area odo-on-podman
What does this PR do / why we need it:
The way odo currently does port-forwarding on Podman is via a HostPort in the relevant container in the pod spec. But as reported in https://github.com/redhat-developer/odo/issues/6510 and https://github.com/containers/podman/issues/17353, Podman won't forward traffic to the container if the container port is bound to the container loopback interface.
As discussed in https://github.com/redhat-developer/odo/issues/6510#issuecomment-1439986558 (and similar to how things work on DevSpaces), this PR tries to detect if ports that need to be forwarded are bound to the container loopback interface. If this is the case:

by default, odo dev on Podman will error out with an error message indicating the issue, along with a recommendation to either change the application to listen on <IP_ADDRESS>, or to run odo dev with  --forward-localhost (PR to follow up soon).
if odo dev is run with --ignore-localhost, this message will be displayed as a warning, but this won't prevent odo dev from running. However, any request sent out to the local port forwarded to the container on its loopback interface might not work with Podman.

I'll create a subsequent PR that adds a new --forward-localhost flag, the goal of which is to make port-forwarding work in such cases via a side container. It'll be inspired by what had been done in https://github.com/redhat-developer/odo/pull/6589
Which issue(s) this PR fixes:
This relates to #6510
PR acceptance criteria:

[x] Unit test

[x] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:
This behavior should not affect the default cluster mode.
To test the changes on Podman, either use a project with an application listening on some port on localhost, or leverage some existing stacks like Node.JS which have debuggers listening on localhost.
$ mkdir /tmp/nodejs && cd /tmp/nodejs
$ odo init --name debug-nodejs --devfile nodejs --starter nodejs-starter

Without --ignore-localhost, odo dev on Podman should start but error out after detecting that the port is bound to the container loopback interface:

$ ODO_EXPERIMENTAL_MODE=t odo dev --platform=podman --debug

...
↪ Running on podman in Dev mode
 ✓  Deploying pod [3s]
 ✓  Building your application in container (command: install) [2s]
 •  Executing the application (command: debug)  ...
 ✗  Detected that the following port(s) can be reached only via the container loopback interface: debug (5858).
Port forwarding on Podman currently does not work with applications listening on the loopback interface.
Either change the application to make those port(s) reachable on all interfaces (<IP_ADDRESS>), or rerun 'odo dev' with any of the following options:
- --ignore-localhost: no error will be returned by odo, but port-forwarding on those ports might not work on Podman.
- --forward-localhost: odo will inject a dedicated side container to redirect traffic to such ports.
Cleaning up resources
 ✗  Finished executing the application (command: debug) [16s]
 ✗  cannot make port forwarding work with ports bound to the loopback interface only

NOTE: only ports that are expected to be forwarded are checked. In the example above, if I run ODO_EXPERIMENTAL_MODE=t odo dev --platform=podman (without --debug), odo dev should start and work normally.

With --ignore-localhost, odo dev on Podman should start but display a warning message after detecting that the port is bound to the container loopback interface:

$ ODO_EXPERIMENTAL_MODE=t odo dev --platform=podman --debug --ignore-localhost

...
↪ Running on podman in Dev mode
 ✓  Deploying pod [3s]
 ✓  Building your application in container (command: install) [4s]
 •  Executing the application (command: debug)  ...
 ⚠  Detected that the following port(s) can be reached only via the container loopback interface: debug (5858).
Port forwarding on Podman currently does not work with applications listening on the loopback interface.
Either change the application to make those port(s) reachable on all interfaces (<IP_ADDRESS>), or rerun 'odo dev' with '--forward-localhost' to make port-forwarding work with such ports.
 -  Forwarding from <IP_ADDRESS>:20001 -> 3000
 -  Forwarding from <IP_ADDRESS>:20002 -> 5858

↪ Dev mode
 Status:
 Watching for changes in the current directory /tmp/test/nodejs

 Keyboard Commands:
[Ctrl+c] - Exit and delete resources from podman
     [p] - Manually apply local changes to the application on podman

  Expected
      <*url.Error | 0xc0007d3170>: {
          Op: "Post",
          URL: "http://<IP_ADDRESS>:65530/api/newuser",
          Err: <*errors.errorString | 0xc00007c130>{s: "EOF"},
      }
  to be nil
  In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/3329/tests/e2escenarios/e2e_test.go:306

  There were additional failures detected after the initial failure.  Here's a summary - for full details run Ginkgo in verbose mode:
    [FAILED] in [AfterEach] at C:/Users/Administrator.ANSIBLE-TEST-VS/3329/tests/helper/helper_filesystem.go:48
------------------------------

Summarizing 1 Failure:
  [FAIL] E2E Test starting with non-empty Directory add Binding [It] should verify developer workflow of using binding as env in innerloop
  C:/Users/Administrator.ANSIBLE-TEST-VS/3329/tests/e2escenarios/e2e_test.go:306

Flaky E2E test - reported in https://github.com/redhat-developer/odo/issues/6582
/override windows-integration-test/Windows-test


Ignore dependency check when finding a kernel spec

For #13754
Speed up kernel provider for native notebooks.
Ignoring the dependency checker makes a significant difference.

Codecov Report

Merging #13761 into master will decrease coverage by 0.00%.
The diff coverage is 94.11%.

@@            Coverage Diff             @@
##           master   #13761      +/-   ##
==========================================
- Coverage   59.84%   59.83%   -0.01%
==========================================
  Files         675      675
  Lines       37820    37822       +2
  Branches     5452     5456       +4
==========================================
- Hits        22633    22631       -2
+ Misses      14027    14019       -8
- Partials     1160     1172      +12

Impacted Files
Coverage Δ

src/client/datascience/kernel-launcher/types.ts
23.07% <ø> (ø)

...client/datascience/kernel-launcher/kernelFinder.ts
73.65% <93.33%> (+0.12%)
:arrow_up:

...ient/datascience/jupyter/kernels/kernelSelector.ts
66.49% <100.00%> (+2.53%)
:arrow_up:

src/client/datascience/crossProcessLock.ts
79.41% <0.00%> (-11.77%)
:arrow_down:

src/client/common/utils/platform.ts
56.00% <0.00%> (-8.00%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

src/client/logging/levels.ts
61.11% <0.00%> (ø)

src/client/logging/logger.ts
62.74% <0.00%> (ø)

... and 5 more

Continue to review full report at Codecov.

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


Unknown error occurred

Unable to complete the setup
Already tried to restart the ECU-B and restart HA
Device is available on the network and reply correctly to nc -v <IP_ADDRESS> 8899
v 1.3.1
Core
2024.1.5
Supervisor
2023.12.1
Operating System
11.4
Frontend
20240104.0

What if you take an older version of the integration 1.2.30 for example?

Thanks for the feedback, there might be a bug somewhere, I'll have to look into that. Was it a complete new install?

Update to version 1.3.1
All seems ok till now.
I just downgrade to 1.2.30 and updated again today, I did not removed the integration from HACS.

Strange, not sure what the issue was because I was not able to reproduce it. Might any other question arrise, feel free to open a new issue.


Blender interface/link

From<EMAIL_ADDRESS>on 2011-02-09T18:32:05Z
It would be great to have a simple link to Blender so that is possible to write scripts in spyder (with autocompletion of Blender methods) and directly run them in Blender.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=553

From ccordoba12 on 2011-03-21T15:07:42Z
If someone with the proper Blender knowledge jumps in and tries to develop this feature, it would be great to help him/her to do it.
Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low

From pierre.raybaut on 2011-05-16T01:27:39Z
Labels: Cat-SpyderGUI

From pierre.raybaut on 2012-03-18T14:08:35Z
Labels: -Type-Enhancement Type-Enh

From<EMAIL_ADDRESS>on 2011-11-17T20:46:57Z
Status: ContributorNeeded

From pierre.raybaut on 2012-03-18T14:16:38Z
Status: HelpNeeded


export/00000000-tmp/export-?????-of-00001 is not in all_model_checkpoint_paths. Manually adding it.

Now that I am using the 11rc, I am seeing a lot of this printed out:
INFO in saver: /output/4885/export/00000000-tmp/export-?????-of-00001 is not in all_model_checkpoint_paths. Manually adding it.

I believe when I call:
# Done once:
saver = tf_saver.Saver(sharded=True)
model_exporter = exporter.Exporter(saver)
model_exporter.init(...)
...
# Done each epoch / step:
model_exporter.export(export_path, tf.constant(i), sess)

Environment info
Operating System:
Using nvidia Docker,
uname -a
Linux b2dcea60c730 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Installed version of CUDA and cuDNN:
(please attach the output of ls -l /path/to/cuda/lib/libcud*):
# ls -l /usr/local/cuda/lib64/libcud*
-rw-r--r-- 1 root root 322936 Aug 15  2015 /usr/local/cuda/lib64/libcudadevrt.a
lrwxrwxrwx 1 root root     16 Aug 15  2015 /usr/local/cuda/lib64/libcudart.so -> libcudart.so.7.5
lrwxrwxrwx 1 root root     19 Aug 15  2015 /usr/local/cuda/lib64/libcudart.so.7.5 -> libcudart.so.7.5.18
-rwxr-xr-x 1 root root 383336 Aug 15  2015 /usr/local/cuda/lib64/libcudart.so.7.5.18
-rw-r--r-- 1 root root 720192 Aug 15  2015 /usr/local/cuda/lib64/libcudart_static.a

The commit hash (git rev-parse HEAD)
8915f0f8072c406ae3fe0dff888f51b4cad02d7d
The output of bazel version

# bazel version
INFO: Reading 'startup' options from /root/.bazelrc: --batch
Extracting Bazel installation...
Build label: 0.3.1
Build target: bazel-out/local-fastbuild/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Fri Jul 29 09:09:52 2016<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>

@cancan101 : That is an informational log line, not an error. That logging line has been there for a while, so I'm surprised that you're seeing it only now. Perhaps your logs were being redirected somewhere else before and you didn't notice them?
Regardless, this shouldn't be causing any problems. Is it?

On older versions of TF, instead of the log I got exceptions like:
    model_exporter.export(export_path, tf.constant(i), sess)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/session_bundle/exporter.py", line 268, in export
    meta_graph_suffix=constants.EXPORT_SUFFIX_NAME)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/saver.py", line 1078, in save
    meta_graph_suffix=meta_graph_suffix)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/saver.py", line 941, in _MaybeDeleteOldCheckpoints
    self._CheckpointFilename(p)):
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/lib/io/file_io.py", line 53, in get_matching_files
    return pywrap_tensorflow.GetMatchingFiles(compat.as_bytes(filename), status)
  File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
    self.gen.next()
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/errors.py", line 450, in raise_exception_on_not_ok_status
    pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors.NotFoundError: /output/gap/4887/export/00000000-tmp

which actually killed training.
Is there any way to suppress that log message? It fills my logs and I don't even know what / if I am doing anything wrong.

@concretevitamin : Could you take a look at this?

@sukritiramesh: can you take a look?  Is it caused by the way Exporter.export() uses Saver?

I don't see it when just using the Saver

@concretevitamin This might be related to exporter using a -tmp location and then performing an atomic copy to the final export location. In this case, the checkpoint file contents include the -tmp location but the actual export location is the final one. Do you think that might be the case here, re: interaction with how Saver reads the checkpoint file?

@sukritiramesh: yes, I agree w/ your hypothesis.  I think you're already working on making the paths in "checkpoint" relative?  That could mitigate the issue.

@concretevitamin Not sure we'll be able to switch Exporter to use relative paths since that might impact existing exports. We could try to see if relative paths could be made the default in future versions though. Thoughts?

So I think this issue is related to the checkpoint file containing the tmp path before the rename occurs.
Inside the checkpoint folder:
# cat output/diam/20170130-005509/export/00000060/checkpoint
model_checkpoint_path: "/usr/src/app/output/diam/20170130-005509/export/00000060-tmp/export"
all_model_checkpoint_paths: "/usr/src/app/output/diam/20170130-005509/export/00000060-tmp/export"

but that folder has been renamed:
# ls /usr/src/app/output/diam/20170130-005509/export/00000060/
checkpoint  export.data-00000-of-00001  export.index  export.meta

Any way to suppress this INFO message? It is entirely spurious.

This INFO message is not blocked even when I set:
import os
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '3'
import tensorflow as tf

It seems like this is very old code?

tf.logging.set_verbosity(tf.logging.WARN)
This should have the desired effect

It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Invalid behaviour when using with livereload

i have noticed a problem when using gulp-if in combination with livereload. my goal is to trigger livereload only if the condition is true, but it seems that the "true branch" is always triggered. this behaviour only occurs with livereload ...
.pipe(gulpif(false, livereload()));

version 1.1.0

I've been unable to reproduce this.  Can you help me pinpoint the fail?

Hi @mrmuh,
looks like it's normal for the call .pipe(gulpif(false, livereload())); to execute the live-reload functionality. I had exactly the same problem at my repository https://github.com/elgervb/skeletonSPA.
Let me explain the situation:
The executionpath for this call is:

livereload
gulpif
pipe

Gulp-if expects a function as a second parameter, you're doing the function call right here in your gulpfile and by mistake pass the result of this function call.
Please change your original call .pipe(gulpif(false, livereload())); to:
.pipe(gulpif(false, livereload));
or
.pipe(gulpif(false, function() { return livereload();} ));
That will fix your problems... and this call can be closed.


Type definitions can override eachother when one type definition is a alias to a built-in type

Description:

import ballerina/io;

type A int;

type A record { // This overrides the previous 'A' type
    int i = 0;
};

public function  main() {
    A a = { i: 33 };
    io:println(a);
}

Cause of this is for the isRedeclaredSymbol function, first A has a different owner (annotation pkg), and second A have the current pkg as the owner.
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Fixed on slbeta3. Now results in a redeclared symbol error.


Jerky scrolling

I've tried the example code on an iphone 5 and ipad both running 8.4 and get jerky scrolling. I'm guessing this is not normal?

I'll check scrolling behavior on iOS 8.4.


Toggle cleanup

Updated toggles so that they can be used with ID's properly.  Updated index.js to reflect the changes as well.

I think this covers all of the id carriers

Made Changes, fixed placement of className.

@samrocksc looks like the switch.js file was altered to be tab indented

fixed the tab spacing, just had to pull in to 2-spacing standards

Think we're good here

@samrocksc nope, still wrong.  you have to look at the diff you produce here on github to see where you are unnecessarily changing things

leaving nothing but pertinent changes


Source Native Support

To be tested and merged together with https://github.com/source-academy/js-slang/pull/1231

CI will only pass after bumping js-slang once it is merged

Using the Native variant, we will expect to see performance gains from existing Source snippets while still adhering to existing source syntax and builtIns rules

[x] Add introduction text for Source Native variants

OK, I'll bump js-slang soon, and then try to merge this PR.

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

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

Details

12 of 15 (80.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 30.772%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/commons/utils/IntroductionHelper.ts
11
12
91.67%

src/pages/playground/Playground.tsx
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
3516

Relevant Lines:
10624

💛  - Coveralls


Implemented sounds for Level Up, Bomb, Whetstone, and Potion

Hey again @RMDern. #60 will introduce a wrapper class for playing sounds, hang tight until that's merged!

#60 has been merged. You have to use PlaySoundFile() instead of PlaySound().


What is the output type

First, thank you for sharing this awesome work. looks amazing!
just trying to understand what is the output of your process -
is it a point cloud? a mesh? just a rendered RGB image?
my main interest is getting the best possible 3D model of the scene.
thanks again

For nerf-slam, the main outputs are rendered RGB images.
For sigma-fusion, the main outputs are 3D meshes.
For both approaches, the intermediate outputs are depth maps, depth uncertainties, and 3D poses, which combined can be used to create point clouds.


fix(scully-plugin-puppeteer): correctly track requests in bare project

Previously, instead of adding/removing each request from the requests set, the set itself was added/removed. Since Set deduplicates its values, it would always contain just one item (regardless of how many requests would be pending) and it would be emptied once the first request was completed.
This commit fixes this by adding/removing the actual request to/from the requests set.

 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.


Test EKS Guide

Guide: https://docs.cilium.io/en/latest/gettingstarted/k8s-install-eks/

[ ] Write down unclear steps in the documentation
[ ] Report failures

Which version of eksctl did you use to create the cluster in the docs?
With: [ℹ]  version.Info{BuiltAt:"", GitCommit:"", GitTag:"0.1.20-rc.2"} I'm getting the following timeout (tried in both us-west-2 and eu-central-1):
$ eksctl create cluster
[ℹ]  using region us-west-2
[ℹ]  setting availability zones to [us-west-2b us-west-2a us-west-2c]
[ℹ]  subnets for us-west-2b - public:<IP_ADDRESS>/19 private:<IP_ADDRESS>/19
[ℹ]  subnets for us-west-2a - public:<IP_ADDRESS>/19 private:<IP_ADDRESS>/19
[ℹ]  subnets for us-west-2c - public:<IP_ADDRESS>/19 private:<IP_ADDRESS>/19
[ℹ]  nodegroup "ng-8edac58f" will use "ami-0a2abab4107669c1b" [AmazonLinux2/1.11]
[ℹ]  creating EKS cluster "exciting-wardrobe-1549034701" in "us-west-2" region
[ℹ]  will create 2 separate CloudFormation stacks for cluster itself and the initial nodegroup
[ℹ]  if you encounter any issues, check CloudFormation console or try 'eksctl utils describe-stacks --region=us-west-2 --name=exciting-wardrobe-1549034701'
[ℹ]  creating cluster stack "eksctl-exciting-wardrobe-1549034701-cluster"
[ℹ]  creating nodegroup stack "eksctl-exciting-wardrobe-1549034701-nodegroup-ng-8edac58f"
[ℹ]  --nodes-min=2 was set automatically
[ℹ]  --nodes-max=2 was set automatically
[✔]  all EKS cluster resource for "exciting-wardrobe-1549034701" had been created
[✔]  saved kubeconfig as "/home/brb/.kube/config"
[✖]  timed out waiting for control plane "exciting-wardrobe-1549034701" after 20m0s

@errordeveloper - is it common for eksctl to take more than 20min to bootstrap a cluster? I could provide verbose logs in private.

@brb I'm using the following version and it has been flawless so far
eksctl version
[ℹ]  version.Info{BuiltAt:"", GitCommit:"", GitTag:"0.1.19"}

Found the culprit:
2019-02-01T19:01:17+01:00 [▶]  control plane not ready yet – Get https://<REDACTED>.eu-central-1.eks.amazonaws.com/version?timeout=32s: exec: exec: "heptio-authenticator-aws": executable file not found in $PATH

Hey folks!
Hey Martynas! The auth error can be fixed by installing authenticator
binary. It is weird and I could never understand why some users get this,
and the code that does those checks is not supposed to depend on the
authenticator binary being present.
Besides that, if you get stuck with eksctl - ping me on slack!
On Fri, 1 Feb 2019, 6:03 pm Martynas Pumputis<EMAIL_ADDRESS>wrote:

Found the culprit:
2019-02-01T19:01:17+01:00 [▶]  control plane not ready yet – Get https://.eu-central-1.eks.amazonaws.com/version?timeout=32s: exec: exec: "heptio-authenticator-aws": executable file not found in $PATH
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cilium/cilium/issues/6878#issuecomment-459812179, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAPWS9S63jXUg4MXuO0pUY_0jAARkJM0ks5vJIFigaJpZM4ad9rO
.


merge_config / read_config doesn't work if set_config_file is not called

merge_config and read_config methods accepts a file parameter, but those methods doesn't work as expected if set_config_file has not been called before with the same file parameter.
(Because _unmarshall_reader calls _get_config_type which itself calls _get_config_file)

I just realised file parameter should be an opened file (stream) instead of filepath string.


Address Resolved TransactionView

Problem

Need to resolve ATLs to eventually process transaction type TransactionView

Summary of Changes

Add ResolvedTransactionView which wraps a TransactionView with loaded addresses and writable cache

Fixes #

@tao-stones I haven't added tests yet, but could you take a quick look at this?
This is the type that I will (soon) feed into RuntimeTransaction, and is what impls SVMTransaction so that we can send to SVM for processing.
Signature meta can/should be cached by RuntimeTransaction, so we don't need to loop ixs to find it again.

rebased due to naming/comment conflicts with merged PR #2830

@jstarry think I hit all your comments, if there's something missing please let me know so I cna fix and keep progressing


Case Study Page

Description
Code a Case Study page in accordance with the design shared in the link below using React.js
https://www.figma.com/file/8kV2PkJG5V2wlUVhWBDPy9/Case-Study?node-id=0%3A1
Please follow contribution guidelines and code of conduct
Screenshots
No response
Additional information
No response

Hey ,
Please assign me this issue.
I will try to submit pixel perfect design.