Multiple Issues At Login

Expected Behavior
Sucessful Login and Execution
Actual Behavior
2016-08-07 17:19:46,423 [       cli] [INFO] PokemonGO Bot v1.0 2016-08-07 17:19:46,425 [       cli] [INFO] No config argument specified, checking for /configs/config.json 2016-08-07 17:19:46,444 [       cli] [INFO] Configuration initialized 2016-08-07 17:19:46,444 [pokemongo_bot.health_record.bot_event] [INFO] Health check is enabled. For more logrmation: 2016-08-07 17:19:46,445 [pokemongo_bot.health_record.bot_event] [INFO] https://github.com/PokemonGoF/PokemonGo-Bot/tree/dev#analytics 2016-08-07 17:19:46,579 [requests.packages.urllib3.connectionpool] [INFO] Starting new HTTP connection (1): www.google-analytics.com 2016-08-07 17:19:48,258 [PokemonGoBot] [INFO] [set_start_location] Setting start location. 2016-08-07 17:19:48,258 [PokemonGoBot] [INFO] [x] Coordinates found in passed in location, not geocoding. 2016-08-07 17:19:48,258 [PokemonGoBot] [INFO] [location_found] Location found: 34.0087, -118.4982 (34.0087, -118.4982, 0.0) 2016-08-07 17:19:48,259 [PokemonGoBot] [INFO] [position_update] Now at (34.0087, -118.4982, 0) 2016-08-07 17:19:48,259 [PokemonGoBot] [INFO] [login_started] Login procedure started. Traceback (most recent call last):   File "pokecli.py", line 496, in <module>     main()   File "pokecli.py", line 130, in main     report_summary(bot)   File "pokecli.py", line 139, in report_summary     metrics.capture_stats()   File "/Users/Fglosson/PokemonGo-Bot/pokemongo_bot/metrics.py", line 73, in capture_stats     request = self.bot.api.create_request()   File "/Users/Fglosson/PokemonGo-Bot/pokemongo_bot/api_wrapper.py", line 28, in create_request     self._position_alt   File "/Users/Fglosson/PokemonGo-Bot/pokemongo_bot/api_wrapper.py", line 44, in __init__     PGoApiRequest.__init__(self, *args) TypeError: __init__() takes exactly 5 arguments (6 given) 2016-08-07 17:19:53,224 [sentry.errors] [ERROR] Sentry responded with an error: 'ascii' codec can't decode byte 0x9c in position 1: ordinal not in range(128) (url: https://app.getsentry.com/api/90254/store/) Traceback (most recent call last):   File "/usr/local/lib/python2.7/site-packages/raven/transport/threaded.py", line 174, in send_sync     super(ThreadedHTTPTransport, self).send(data, headers)   File "/usr/local/lib/python2.7/site-packages/raven/transport/http.py", line 47, in send     ca_certs=self.ca_certs,   File "/usr/local/lib/python2.7/site-packages/raven/utils/http.py", line 66, in urlopen     return opener.open(url, data, timeout)   File "/usr/local/lib/python2.7/site-packages/future/backports/urllib/request.py", line 494, in open     response = self._open(req, data)   File "/usr/local/lib/python2.7/site-packages/future/backports/urllib/request.py", line 512, in _open     '_open', req)   File "/usr/local/lib/python2.7/site-packages/future/backports/urllib/request.py", line 466, in _call_chain     result = func(*args)   File "/usr/local/lib/python2.7/site-packages/raven/utils/http.py", line 46, in https_open     return self.do_open(ValidHTTPSConnection, req)   File "/usr/local/lib/python2.7/site-packages/future/backports/urllib/request.py", line 1284, in do_open     h.request(req.get_method(), req.selector, req.data, headers)   File "/usr/local/Cellar/python/2.7.12/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 1057, in request     self._send_request(method, url, body, headers)   File "/usr/local/Cellar/python/2.7.12/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 1097, in _send_request     self.endheaders(body)   File "/usr/local/Cellar/python/2.7.12/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 1053, in endheaders     self._send_output(message_body)   File "/usr/local/Cellar/python/2.7.12/Frameworks/Python.framework/Versions/2.7/lib/python2.7/httplib.py", line 895, in _send_output     msg += message_body UnicodeDecodeError: 'ascii' codec can't decode byte 0x9c in position 1: ordinal not in range(128) 2016-08-07 17:19:53,265 [sentry.errors.uncaught] [ERROR] [u'TypeError: __init__() takes exactly 5 arguments (6 given)', u'  File "pokecli.py", line 496, in <module>', u'  File "pokecli.py", line 130, in main', u'  File "pokecli.py", line 139, in report_summary', u'  File "pokemongo_bot/metrics.py", line 73, in capture_stats', u'  File "pokemongo_bot/api_wrapper.py", line 28, in create_request', u'  File "pokemongo_bot/api_wrapper.py", line 44, in __init__']
Steps to Reproduce
python pokecli.py
Other Information
OS: MAC OS X 10.11.6
Git Commit: (run 'git log -n 1 --pretty=format:"%H"' and paste it here) b5b3e7048b4d28f8fa5984dc92c54745db82f75f
Python: Python 2.7.12

had a bunch of errors, too. Try to completly delete everything and reinstall it.
Another problem I had was setting "use_lucky_egg" in the config.json to true.

Are you still having this issue? If so please try setting "health_record": false,
If that still doesn't work, please seek help on the slack forum.


Website

[ ] the development links says this is v0.11 but we are in dev0.12

[ ] when hovering over header links, it displays the paragraph symbol, this doesn't seem like the correct behavior.

[ ] the example figures look funky here:
http://martinos.org/mne/dev/auto_examples/visualization/plot_meg_eeg_fields_3d.html#sphx-glr-auto-examples-visualization-plot-meg-eeg-fields-3d-py

can you refresh your browser cash?

when hovering over header links, it displays the paragraph symbol, this doesn't seem like the correct behavior.

That's a symbol that means you can use it as a link and I think it's useful. I've seen it on other sites, too.

the website is up-to-date for me now. everything looks great!

That's a symbol that means you can use it as a link and I think it's useful. I've seen it on other sites, too.

ah, ok. sounds fine.
closing


Another MSVC compiler problem with pcg32 vs pcg64

Hi there!
I'm trying to use pcg64 in my program (first question: should I? When is pcg32 enough?)
When I do that I get the following compiler error with MSVC 19:
 error C2678: binary '<<': no operator found which takes a left-hand operand of type 'dest_t' (or there is no acceptable conversion) [C:\Users\Eike\Documents\grazer\build\src\Auxillary\Mathfunctions\mathfunctions.vcxproj]

 message : could be 'std::ostream &pcg_extras::operator <<(std::ostream &,uint8_t)' [found using argument-dependent lookup] [C:\Users\Eike\Documents\grazer\build\src\Auxillary\Mathfunctions\mathfunctions.vcxproj]
C:\Users\Eike\Documents\grazer\pcg\include\pcg_uint128.hpp(774,3): message : or       'pcg_extras::uint_x4<uint32_t,uint64_t> pcg_extras::operator <<<uint32_t,uint64_t>(const pcg_extras::uint_x4<uint32_t,uint64_t> &,const pcg_extras::bitcount_t)' [C:\Users\Eike\Documents\grazer\build\src\Auxillary\Mathfunctions\mathfunctions.vcxproj]
C:\Users\Eike\Documents\grazer\pcg\include\pcg_extras.hpp(425,1): message : or       'built-in C++ operator<<(UIntX2, UIntX2)' [C:\Users\Eike\Documents\grazer\build\src\Auxillary\Mathfunctions\mathfunctions.vcxproj]
          with
          [
              UIntX2=uint64_t
          ]

Note that the line numbers are probably wrong, because I clang-formated the sourcecode inadvertedly.
The same compiles without issue with pcg32. I guess I would have to supply an additional overload for << but I don't know how. Can someone help me?

Note that the same goes through without issue on both clang and gcc.

I guess, a pull request would be the way to go, I guess. Its just that i don't know how to write it.

A pull request would be the way to go, I guess. Its just that i don't know how to write it.

Why would you issue a pull request? Do you have a patch for the issue that you have found?

Not yet. But as soon as i have i will file a pull request.

I realize that I just don't know enough c++ to fix my issue. I guess I'll stick with pcg32 for now.

I checked on Visual Studio 2019 and I don't see any issues using << with pcg64. When reporting an issue, please provide a short test program that shows the purported problem, rather than just an error message you got compiling your own larger codebase.

I don't know, what happened. Now that I tried to reproduce the issue I failed to do so.
Once again sorry for bothering you.


APPS HTTP server: trace requests and responses, clean up logging

This preliminary PR depends on #18386.

APPS HTTP server: trace requests and responses when enabled
apps/lib/http_server.{c,h}: clean up logging and move it to log.{c,h}
OSSL_trace_enabled.pod: add missing synopsis for OSSL_TRACE()
apps/ocsp.c etc.: rename 'multi' to 'n_responders' for clarity
BIO_f_prefix: improve diagnostics where not implemented; fix nit in doc

Moved to https://github.com/openssl/openssl/pull/18434.


Use Array.isArray to check if pipeline output is an array

TiddlyWiki (https://tiddlywiki.com), when run on Node, loads all of its
modules via Node's vm.runInContext.  This means that for my full text search
plugin (https://github.com/hoelzro/tw-full-text-search/), there is a
pipeline function loaded in its own context, separate from the context
lunr is loaded in.  This mismatch of contexts causes
result instanceof Array to always evaluate to false, which causes lunr
to break in further ways down the line.

Here's a contrived example that reproduces the issue:
let lunr = require('./lunr.js');
let vm = require('vm');

let source = `
let noOpFilter = function noOpFilter(token) {
    console.log(token);
    return [token];
}

exports.noOpFilter = noOpFilter;
`;

let sandbox = {
    exports: {},
    console: console
};

vm.runInNewContext(source, sandbox);

let idx = lunr(function() {
    this.ref('id');
    this.field('body');
    this.pipeline.after(lunr.stopWordFilter, sandbox.exports.noOpFilter);

    this.add({
        id: 1,
        body: 'Colorless green ideas sleep furiosly'
    });
});

console.log(idx.search('green'));

Since the vm module is Node-specific, I couldn't think of a way to incorporate this test without breaking browser tests; if you have any ideas on how I could add a test for this, let me know!

The change seems fine to me, support for Array.isArray is probably good enough (at least as good as Object.create which is used already).
I'm happy to make the change but would you mind explaining a bit more why this specific case requires it? I'm not familiar with either vm.runInContext nor TiddlyWiki's module loading.

@olivernn So what vm.runInContext does is run the specified code in its own little sandbox, so it can't affect the invoking environment.  When code is compiled in this context, the prototypes of built-in objects, such as Array, different from context to context.
Let's say I create a function F in its own context, and then call it from another function G.  F returns an Array named a, but that array's prototype points to the Array from F's context, which is different from the Array in G's context, so a instanceof Array will always return false within G.

Ok, I understand, I'll merge and put together a release.


Chrome 48+ IDB - success/error callback or Promises don't return on non-existent keys

This seems to have started happening in Chrome 48 and above. The function callbacks or Promises don't resolve if I do a getItem on a key that doesn't exist. It should return null but it doesn't in those Chrome versions.
Using IndexedDB driver. Firefox works as expected.

Restarted the Chrome and it started working again. Not sure why. I'll reopen once I've investigated properly.


Fix doc link

warehouse.pypi.io return a 404

Ah, yea that's because I hit a bug with RTD with my custom domain, and I'm waiting for @ericholscher to make it work again :)
I'll go ahead and merge this so that the link is correct in the interim.

Thanks !


Update audioSegmentation.py to handle ValueError

silenceRemoval throws ValueError when plot=True due to difference in dimension for x and y. Propose to add an element with value 0 to extend the length of array.
Error:
ValueError: x and y must have same first dimension, but have shapes (193,) and (192,)
Reference #83

I'm still having this problem May I know if you intend to solve it?


Clicking on links in the Install Packages tab opens blank browser windows

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Clicking on external (http) links in the Install Packages tab opens blank Chrome browser windows. This is on a fresh install of Atom, just downloaded to try out.
Steps to Reproduce

Search for packages in the Install Packages tab
Click on any external link

Expected behavior: A tab will open in my current browser session at the linked URI.
Actual behavior: A new, blank window is opened for each click.
Reproduces how often: 100%
Versions
Atom    : 1.22.1
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0

apm  1.18.8
npm  3.10.10
node 6.9.5 x64
python 2.7.10
git 2.5.0

Additional Information
Enjoy a gif!

Huh, this seems to be happening in all my applications. Might be a OS level bug from installing a couple new things at once, will report back.

Odd, was an issue at OS level. Fixed with a restart. Nevermind!


Please provide the azure cli examples

This entire document is showing powershell examples but how can I do it with the azure cli?

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

ID: e7097406-c1fa-4426-82fc-5325d1ae8440
Version Independent ID: 31844be0-b20d-a145-7794-27c706770735
Content: Find and use marketplace purchase plan information using PowerShell - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/cli-ps-findimage.md
Service: virtual-machines
Sub-service: imaging
GitHub Login: @ebolton-cyber
Microsoft Alias: edewebolton

@justinmchase
Thanks for your feedback! We will investigate and update as appropriate.

I see the corresponding azure cli docs are on another page, it may be useful to have a link at the top of the page linking to the azure cli version of the docs.

@justinmchase
Thank you for your feedback!
Since this issue isn't directly related to improving our docs, and to gain a better understanding of your issue, I'd recommend leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
[Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows.
[Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1)
Thank you for your time and patience throughout this issue.


Assertion failure (KD tree) or hang

With 58a56ef4a, I have the following assertion failure on a 3-node 18-rank configuration
solver: /gpfs/alpine/scratch/bandok/csc335/Softwares/legion/runtime/legion/region_tree.inl:6604: Legion::Internal::KDNode<DIM, T, RT>::KDNode(Legion::Rect<DIM, T>&, std::vector<std::pair<Realm::Rect<N, T>, RT> >&) [with int DIM = 1; T = long long int; RT = unsigned int; Legion::Rect<DIM, T> = Realm::Rect<1, long long int>]: Assertion `right_set.size() < subrects.size()' failed.

gdb0.txt
gdb1.txt
This doesn't reproduce for a 2-node 12-rank configuration.
With 2dc039225 (I noticed some kd-tree related recent commits), the same 3-node 18-rank configuration hangs with the following unusual backtraces
gdb0.txt
gdb2.txt

Attach a debugger and print out all the rectangles in the subrects data structure and post them here.
I'm going to ignore the hang on 2dc0392 unless you can reproduce it on a more recent commit.

On one of the frozen process
$4 = {
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 26634}, hi = {x = 191999}}, second = 1},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 1112}, hi = {x = 191079}}, second = 3},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 23431}, hi = {x = 191988}}, second = 0},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 29}, hi = {x = 152559}}, second = 4},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 35220}, hi = {x = 151989}}, second = 6},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 0}, hi = {x = 161763}}, second = 9},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 23031}, hi = {x = 167159}}, second = 8},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 23030}, hi = {x = 167988}}, second = 7},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 17}, hi = {x = 154187}}, second = 5},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 629}, hi = {x = 173429}}, second = 2},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 11200}, hi = {x = 155818}}, second = 10},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 22920}, hi = {x = 164488}}, second = 11},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 696}, hi = {x = 176767}}, second = 13},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 20336}, hi = {x = 191459}}, second = 15},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 30415}, hi = {x = 150378}}, second = 12},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 42370}, hi = {x = 191982}}, second = 16},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 33200}, hi = {x = 191969}}, second = 17},
  {<std::__pair_base<Realm::Rect<1, long long>, unsigned int>> = {<No data fields>}, first = {lo = {x = 1177}, hi = {x = 191204}}, second = 14}
}

I have updated to 8f24818af

Pull and try again.

On 69eadbca, the assertion is gone. Now the 3-node case hangs. The 2-node case still runs to completion. I tried looking at backtraces but nothing stood out to me. The only thing that seems to change between processes is the state of the gasnet poller. I saw things like
Thread 8 (Thread 0x20003b90f890 (LWP 176473)):
#0  0x0000000011b34834 in Realm::Clock::current_time_in_nanoseconds (absolute=false) at /gpfs/alpine/scratch/bandok/csc335/Softwares/legion/runtime/realm/timers.inl:69
#1  0x000000001364b9d4 in Realm::XmitSrcDestPair::time_since_failure (this=0x20056c2f8a40) at /gpfs/alpine/scratch/bandok/csc335/Softwares/legion/runtime/realm/gasnetex/gasnetex_internal.cc:2525
#2  0x000000001364d290 in Realm::GASNetEXPoller::do_work (this=0x341b35d0, work_until=...) at /gpfs/alpine/scratch/bandok/csc335/Softwares/legion/runtime/realm/gasnetex/gasnetex_internal.cc:2884
#3  0x0000000013353944 in Realm::BackgroundWorkManager::Worker::do_work (this=0x20003b90e8e8, max_time_in_ns=-1, interrupt_flag=0x0) at /gpfs/alpine/scratch/bandok/csc335/Softwares/legion/runtime/realm/bgwork.cc:621
#4  0x0000000013350ba0 in Realm::BackgroundWorkThread::main_loop (this=0x34c4e200) at /gpfs/alpine/scratch/bandok/csc335/Softwares/legion/runtime/realm/bgwork.cc:125
#5  0x0000000013356628 in Realm::Thread::thread_entry_wrapper<Realm::BackgroundWorkThread, &Realm::BackgroundWorkThread::main_loop> (obj=0x34c4e200) at /gpfs/alpine/scratch/bandok/csc335/Softwares/legion/runtime/realm/threads.inl:97
#6  0x000000001359b268 in Realm::KernelThread::pthread_entry (data=0x34c4e580) at /gpfs/alpine/scratch/bandok/csc335/Softwares/legion/runtime/realm/threads.cc:774
#7  0x0000200000208ae0 in start_thread () from /lib64/power9/libpthread.so.0
#8  0x000020000a80e7c8 in clone () from /lib64/power9/libc.so.6

but I don't know what it exacly means. I am attaching here the 18 backtraces, sorry I wasn't able to more precisely identify the problem.
backtraces.zip

Please leave debug hanging processes on sapling, run with -ll:force_kthreads. If possible see if it hangs with -lg:inorder.

These results come from Summit, trying to reproduce on sapling right now. It does hang with -lg:inorder and the last run produced the following warning
[0 - 20003c20f890]    6.020287 {4}{runtime}: [warning 1114] LEGION WARNING: Failed to find a refinement for KD tree with 1 dimensions and 18 rectangles.

The same configuration with 18 ranks on a single sapling node didn't hang.

I tried to reproduce on sapling using the 16 gpus, it didn't. I tried on Piz Daint with 18 ranks, it also didn't reproduce. Since the only thing I could tell from the backtraces was that there is some failure at the gasnetex interface, I tried gasnet1 on Summit. It didn't reproduce. Maybe @streichler can chime in.

On which machine did the hang occur before? What was the result of running with -lg:inorder -ll:force_kthreads? If you can get it to hang with that, then please report the backtraces.

The hang was obtained on Summit using 3 nodes and 18 ranks only with gasnetex. Attached are the 18 backtraces
backtraces.zip
The command line was the following
jsrun --nrs 18 --rs_per_host 6 --tasks_per_rs 1 --cpu_per_rs 7 --gpu_per_rs 1 --bind packed:7 --latency_priority gpu-cpu /gpfs/alpine/scratch/bandok/csc335/Softwares/DG-Legion/build_2/exec/solver -logfile logs/log_%.log -hdf5:forcerw -dm:memoize -ll:cpu 0 -ll:util 2 -ll:bgwork 3 -ll:bgworkpin 1 -ll:csize 20000 -ll:rsize 0 -ll:gpu 1 -ll:fsize 14000 -ll:onuma 0 -ll:ht_sharing 1 -ll:ocpu 1 -ll:othr 3 -ll:ib_rsize 512m -ll:ib_zsize 0 -cuda:legacysync 1 -ll:force_kthreads -lg:warn -lg:partcheck -lg:safe_ctrlrepl 1 -lg:safe_mapper -lg:inorder

The hang occurs only with gasnetex reminder me that my program also runs extremely slow with gasnetex. Have you tried running with -gex:bindcuda 0 to see if the hang still occurs?

Thanks for the suggestion. Without binding, it doesn't hang. But I need this for best performance.

Thanks for the suggestion. Without binding, it doesn't hang. But I need this for best performance.

I think it is a realm issue, and I just created an issue for my program. https://github.com/StanfordLegion/legion/issues/1265
It may not be a hang for you, but just runs very slow. If you can reduce your problem size, it may runs with -gex:cudabind 1. You can also add  GASNET_NUM_QPS=1 to see if it works for me.

This depends on the configuration (problem size + number of ranks), so I don't think it is the same issue. Runs that do not hang are fast with cuda binding.

I just run my program several times, and it is not even slower, but also sometime hangs as well. I just reproduce the hanging with the realm memspeed benchmark under test/realm . Could you please run the memspeed test on summit? Just want to double check if you can reproduce it or not.

I agree with @eddy16112 that this is most likely a Realm/GASNet issue. Legion hangs usually will not reproduce with -lg:inorder and when they do it's usually obvious which task is at fault. In this case it looks like all the tasks are at the same point in the program and waiting for the same index tasks launch to run. Please run with -ll:defalloc 0 -level dma=2 and provide logs for each process of a hung run.

@eddy16112 I quickly ran memspeed with 2 ranks on summit, it worked but i don't think that is necessarilly useful info to you.

This is definitely a Realm issue, there are 251 started copies in log_3.log but only 244 of them have finished.

This is "fixed" by adding the following flag -gex:obcount 256 (higher if it is still not enough). Leaving this open and tagging @streichler so that he can track it and possibly add a cleaner fix


[TfLite] SPLIT_V quantization support for int8

This PR adds int8 quantization for SPLIT_V operator. See issue https://github.com/tensorflow/tensorflow/issues/36965
I added tests as for split_v for int8 by refactoring the existing one, so that they are not Copy&Paste.

We need to bump the op version for this.
To do this, you can add logic in GetBuiltinOperatorVersion to detect the input/output types, and use an incremented version, update the op version to TFlite version mapping here, and then update the max version where the builtin is registered here.

Hi @jdduke I bumped a version for this operator as requested. Please take a look. Thanks for the review!

@gbaned Can it be merged?

Hi @rthadur ! Can this PR be merged ? It has been marked as 'ready_to_pull' many days ago. Thanks!

@wwwind it got stuck internally , @jdduke can you please help merge this PR internally.


Add Cross-encoder finetuning support and dataset generation functions for generating dataset

Description
This PR adds support to fine-tune cross-encoder models and also adds dataset generation functions to generate a training dataset over a large corpus of documents using LLMs. Based on my reading of the below blogs and cookbooks https://www.sbert.net/examples/applications/cross-encoder/README.html , https://github.com/openai/openai-cookbook/blob/main/examples/Search_reranking_with_cross-encoders.ipynb , https://weaviate.io/blog/cross-encoders-as-reranker . As I was inspired by the embedding-adapter approach by LLamaIndex team to boost the performance of proprietary embeddings like OpenAI Embeddings which don't support domain/data specific finetuning currently, I also wanted to add support for fine-tuning specific cross-encoder models as re-rankers which can also be used to boost performance of proprietary embeddings.
Fixes # (issue)
Type of Change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[x] Added a sample code python script
[ ] I stared at the code and made sure it makes sense

Suggested Checklist:

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

This is super neat @bhavishpahwa !
Can you move your example script to a notebook in docs/examples/finetuning
It would be great if there was a neat little way to show the improvement in re-ranking performance (either qualitative or quantitative)

Hi @logan-markewich I added the respective colab example for cross-encoder finetuning showing the respective boosts in hits of relevant context chunks as well as Rag performance. Also had to remove the 'def get_finetuned_model(self, **model_kwargs: Any) ' function as Cross Encoder class in Sentence Transformers doesn't currently supports passing in model path and instead accepts only model string corresponding to the respective huggingface hub repo. Have raised this issue here:- https://github.com/UKPLab/sentence-transformers/issues/2325 . Might raise a PR in sentence-transformers repo to resolve that.

let's not check in the .csv files if possible, it increases the size of the repo. can we download in the notebook from a public link? (e.g. dropbox)

Sure can probably do that, will do this along with other changes and push the changes by today. Also if size of the repo a major concern why not move all the ipython/jupyter notebooks/tutorial docs to another repo away from the main library source code like how OpenAI does it with OpenAI cookbook https://github.com/openai/openai-cookbook and renders all the tutorials on the website.

Hi @logan-markewich @jerryjliu have made the respective changes as suggested can you please review.

Thanks @bhavishpahwa looks good to me now!

@bhavishpahwa congrats on this PR. What's your twitter handle? Will promote on socials tomorrow

Thanks @jerryjliu btw not gonna be my last PR while working through this PR I saw various other ways to improve LLamaIndex gonna raise them soon 😊 . My socials:- twitter:- https://twitter.com/BpHigh_BpLow , LinkedIn:- https://www.linkedin.com/in/bhavishpahwa/ . Also thanks @logan-markewich for reviewing and guiding me throughout the process.


Packages cannot be authenticated

On a fresh Ubuntu 14.04 LTS vagrant environment I am trying to install the web packages with sudo ee stack install --web or with sudo ee stack install --all and always get an error. sudo tail /var/log/ee/ee.log gives me the following:
vagrant@trusty64:~$ sudo tail /var/log/ee/ee.log
0 upgraded, 198 newly installed, 0 to remove and 4 not upgraded.
Need to get 85.5 MB of archives.
After this operation, 357 MB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
mysql-common mariadb-common libmariadbclient18 libmysqlclient18
mariadb-client-core-10.0 mariadb-client-10.0 mariadb-server-core-10.0
mariadb-server-10.0 hhvm mariadb-server nginx-common nginx-custom
E: There are problems and -y was used without --force-yes
2015-06-15 07:00:11,906 (INFO) ee : Oops Something went wrong!!
2015-06-15 07:00:11,906 (ERROR) ee : Check logs for reason tail /var/log/ee/ee.log & Try Again!!!
ee version:
vagrant@trusty64:~$ sudo ee -v
EasyEngine v3.2.0
Copyright (c) 2015 rtCamp Solutions Pvt. Ltd.

Related to #560.
@sianios , refer: https://github.com/rtCamp/easyengine/issues/560#issuecomment-110263534


Automated Package Upgrade

:tada: This PR is included in version 10.0.15 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


use shell arihmetic expansion instead of 'expr'

Arithmetic expansion is posix, and slightly slimper/cheaper than calling expr

Neat, thanks for contribution!


Fix for Issue 567

https://github.com/razeware/emitron-iOS/issues/567

I haven't worked with Emitron in a long time. Is this failure expected?

I don't know of a reason why the tests would fail. The only issue might be around timeouts for the async tests. Taking a look at the output will give an indication of which tests are failing, which might help narrow down what the problem is.

Passed here: https://github.com/razeware/emitron-iOS/pull/593
How do I kick off the tests again? I feel pretty certain I don't need to make any code changes.

Details. Then "re-run jobs > Re-run all jobs"

Again, it failed.
Once more, and it did not fail.
That's good enough for me for now, but I'd prefer it to be more deterministic… 😑

I think the solution is to either come up with a better way to test the async code, or just extend the timeouts. Not sure why they take so long. I guess shared Macs being quite slow.


Output video is very laggy/choppy

So, basically I was playing with BBMetalImageDemo on my iPhone. I changed VideoFilterVC2 video path to my own video which is basically a 15sec iPhone screen recording. Then I added let lookupFilter = BBMetalLookupFilter(lookupTable: UIImage(named: "lookup_6")!.bb_metalTexture!) - basically just changed the filter to be a LookupFilter.
And I saw that now the video is very laggy/choppy. I think because the video is not the default demo video. But it's also very low quality video. Also, I tried to save the video from outputUrl to camera roll but it's still laggy and choppy.
Is there anything I can do to make my output video don't be choppy and laggy?
This framework works great with photos but I don't know if I can use it with videos. Thank you!

I found out where the problem is - Asset writer or video input is not ready for writing this frame.
What actually works for me is usleep:
videoSource.start(progress: { (frameTime) in                 usleep(4000)                 print(frameTime)             }
So, I'm thinking that for video saving into photo library some short delay is not a problem for user. Now the question is how to solve the problem if user wants to preview filters when trying to edit the video? I'm going to try testing if videoWriter works better with lower resolution videos. Maybe that's an option for live editing. I'm going to keep this issue open in case anyone have a solution.

I found out where the problem is - Asset writer or video input is not ready for writing this frame.
What actually works for me is usleep:
videoSource.start(progress: { (frameTime) in                 usleep(4000)                 print(frameTime)             }
So, I'm thinking that for video saving into photo library some short delay is not a problem for user. Now the question is how to solve the problem if user wants to preview filters when trying to edit the video? I'm going to try testing if videoWriter works better with lower resolution videos. Maybe that's an option for live editing. I'm going to keep this issue open in case anyone have a solution.


add #Detecting legacy context apis for strict mode post

Add a new section for warning on legacy APIs in the strict mode post.
https://github.com/facebook/react/pull/12849
cc @acdlite @bvaughn

@acdlite Refactored.

The screenshot's been updated, also some other wordings.
Thanks @acdlite @bvaughn

What about this suggested wording change? 😄
https://github.com/facebook/react/pull/12849#discussion_r189119949

Did we intentionally merge it before the release that contains it?

No, it was an oversight. It's probably fine though since this is minor.
If we don't end up releasing today or tomorrow, I'll revert this.


Boxplots-- notches and points

We (Gary, Rob, and I) noticed that the notched feature for the boxplots has disappeared.  Was this on purpose? Can it be (easily) resurrected?
We were also wondering if it would be possible to have a toggle on/off button for the scatter points on the boxplot, giving the user the option of seeing the scattered points or not.  Perhaps a user might want to see the points on the screen but maybe not download them as a png file for illustration purposes?
Thanks

It was briefly discussed here:
https://github.com/USGS-R/wateRuse/issues/162
You guys wanted a hover features that the plotly package could provide, but plotly will not do notches.
Personally, I've never been a fan of the notches, so I was happy to get rid of them. If your user-base is stuck on wanting notches (in my opinion, I don't think the data is refined enough to get much use for this feature)...then there would have to be some work to make a toggle that would go to the static, notched plots and vs. interactive ones. By overlaying the actual data points, you get the same (and more) information as the notch would provide.

@ldecicco-USGS Ah Perfect, thanks, I think I missed that discussion. I'm fine without the notches too.  It sounds like it would be some work to have a toggle to turn the points overlay on and off, like with the log scale toggle?

Creating a toggle for the points overlay probably wouldn't be too hard. Would probably be a good task for one of you guys to try.


Service request: Pocket Casts

Requested by @mathus13 (Nuvola Patron). Pocket Casts  - The only podcatcher you’ll ever need. Listen to your favorite shows in one place.

Homepage
Web player

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Oh man! This is awesome news! My must have podcatcher.

The script will be available only for NP >= 3.1 as it requires loading insecure content.

The first release available at https://github.com/tiliado/nuvola-app-pocket-casts
Flatpak build will be available with the next rebuild of the archive (~within a week).
Formal announcement will come with Nuvola 4.8.

Man! This is awesome!
On Sun, Sep 17, 2017 at 9:46 AM, Jiří Janoušek<EMAIL_ADDRESS>wrote:

[image: pocket_casts]
https://user-images.githubusercontent.com/853706/30521900-c3d3a62a-9bc7-11e7-8f07-c5da1e795742.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tiliado/nuvolaruntime/issues/186#issuecomment-330054041,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKf3U-pavp_w17h0gj_NUNv3LnDMvhpRks5sjTDVgaJpZM4Gqqzl
.

--
Andrew Allen

Packages built, script announced on Patreon, official announcement will come with Nuvola 4.8.


Run goimports and update all caps constants to idiomatic go

This is purely code style and formatting

Run goimports on all go source files.
Update go constants using all caps (except for VERSION which is set at compile time via the linker option) with idiomatic go of snakeCase. This is something we've been doing in all the other repos to conform closer to the go style guide.

Thanks for review! Will merge this in (but hold off on cutting a release since this is just internal style changes).


TST: non-rewindable pause while bundling

Current coverage is 83.03% (diff: 100%)

Merging #536 into master will not change coverage

@@             master       #536   diff @@
==========================================
  Files            19         19
  Lines          3984       3984
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           3308       3308
  Misses          676        676
  Partials          0          0

Powered by Codecov. Last update c442fca...99f4d8b

And this PR shows why line coverage is a bad measure of test coverage :disappointed:

Assuredly a single metric is enough to tell you that your code is perfect. Right, guys? ... guys?

Clearly the answer is to the failure of annoying github integrations is more annoying github integrations.


[feature] Can OccamsRecord be made multi-DB aware?

ActiveRecord supports multiple DBs (https://guides.rubyonrails.org/v6.0/active_record_multiple_databases.html). Can OccamsRecord be updated to support this?
I've been able to get this working by creating a "dummy" model that points to the desired DB and then monkey-patching OR to use that model's connection:
class DummyModel < ApplicationRecord
  self.abstract_class = true

  connects_to database: { writing: :replica, reading: :replica }
end

module OccamsRecord
  class RawQuery
    def conn
      @conn ||= DummyModel.connection
    end
  end
end

It would be nice to be able to do this with OR methods, maybe something like this:
OccamsRecord.sql(query, params, :replica).find_in_batches

Yes, that's a good idea. I haven't used that feature much, but I'll start reading up on it.

After some research and false starts, I'm a little hesitant to bake this into OR directly. I think the vast majority of cases can be covered by AR itself:
ActiveRecord::Base.connected_to(role: :reading) do
  OccamsRecord
    .sql(query, params)
    .find_in_batches do |batch|
      ...
    end
end

Or in cases where you needed a specific model for some reason:
OtherModel.connected_to(role: :reading) do
  OccamsRecord
    .sql(query, params)
    .model(OtherModel) # it will use this model for the connection
    .find_in_batches do |batch|
      ...
    end
end

Closing since multi-db support can seemingly be had using ActiveRecord::Base.connected_to.


RxSwift flatMap "Unable to infer closure type in the current context", Migration from 8 to 11

✨ Moya/RxSwift version 11.0.2, installed via Cocoapods
I am updating my project (from 8.0.5) to use the latest version of Moya (11.0.2) because I have other co-dependencies I want to update, and I am unsure as to how to update the following code in my project:
let provider = RxMoyaProvider<MyAPIService>()
return provider.request(endpoint)
    .filterSuccessfulStatusAndRedirectCodes()
    .mapJSON()
    .flatMap { response -> Observable<Any> in
        // etc
    }

because I am getting this vague compiler error in Xcode on the flatMap line (after changing RxMoyaProvider to MoyaProvider and inserting an rx between provider. and request):

Unable to infer closure type in the current context

I thought maybe it was a matter of changing flatMap to compactMap but then I get:

Value of type 'PrimitiveSequence<SingleTrait, Any>' has no member 'compactMap'

I also checked to see what the autocomplete uses for flatMap and it gives me:
.flatMap({ (<#Any#>) -> PrimitiveSequence<SingleTrait, R> in
    <#code#>
})

which I'm not sure what to make of…
I am asking this as a question, doubt there's any kind of bug here. I'm not even entirely sure if this is really specific to Moya, or more of an RxSwift thing…

Oh looks like what I am missing is an .asObservable() in there…
Relevant question #1423
Seems to fix it, although I'm wondering if I'm missing the point of the updates by doing this?

And, based on the providers documentation:

Always remember to retain your providers, as they will get deallocated if you fail to do so.

So I moved the provider to a stored variable in the class containing the network method, and now calls are going through.
I have also developed a better understanding of the distinction between Observables and Singles as a result of this investigation.


Remove the revoke option in the application protocol section.

Describe the issue:
$subject until first-class support for application disabling is provided.
Along with that, we need to remove the  component.

Have we tracked the story to implement the revoke/disable application at application level instead of OAuth protocol level?
If so can we link it here?

@mefarazath The issue is tracked in product-is with https://github.com/wso2/product-is/issues/11456.


dependencies

Thanks for the inspiration, that's a clean way of doing the binary export.
I didn't use the package as-is mainly because of the jspm dependency. Any chance you can make that optional?
Also, I'd suggest to add threejs as a peerDependency.

I didn't use the package as-is mainly because of the jspm dependency. Any chance you can make that optional?

Oops, you are absolutely right, that should be a dev dependency https://github.com/Doodle3D/ThreeJS-export-STL/commit/c9a74a46d44bb83adb4ed6e0e247d09b0bd1d3e8

Also, I'd suggest to add threejs as a peerDependency.

I was hoping I could write this three.js extension without importing three.js. This way when using the library you wouldn't have to worry about having installed three.js multiple times.
So instead of doing this
  if (geometry instanceof THREE.BufferGeometry) {

I would do this
  if (geometry.type === 'BufferGeometry') {

but in line https://github.com/Doodle3D/ThreeJS-export-STL/blob/master/src/index.js#L69 I have to use THREE.Geometry. I've added three.js as a jspm dependency. https://github.com/Doodle3D/ThreeJS-export-STL/commit/c39e02207ce1a576625a20b7ceb7b788d497f788
Not yet as a npm dependency. I'm using the modular source of three.js so I can write
import { Geometry } from 'three/core/Geometry';

note sure yet how to set this up in npm

You have a threejs dependency there. Just add threejs to peerDependencies and optionally devDependencies. It won't create duplicates as a lib. Make sure to specify a broad enough semver range for threejs in peerDependencies.

I'm not quite sure if that would work, would you consider making a pull request showing the changes you are proposing?

added in https://github.com/Doodle3D/ThreeJS-export-STL/commit/0854117a45032bb174d806ae144fe7b58b9eadf3


Could not search this plugin

Sublime 3  Console  could not search this plugin

visible on my end, do you have more information or thoughts on why this could be happening to you?

I don't see it either...

That's pretty bizarre! I doubt it's installed already (if it's installed it doesn't show up).
I see the package just fine on Package Control's website, which makes me think I have everything configured correctly. https://packagecontrol.io/packages/react-native-snippets
I don't really know what to suggest, to be honest.

Same issue here.. can't find it. :(

whoops.. nvm.. already had it installed 🙈


Fix "Bad state: stream has already been listened too"

Fixes #64

works for me

@juliansteenbakker could you please merge this PR?

Thanks for the contribution and sorry for the late response. Please see my comment https://github.com/juliansteenbakker/mobile_scanner/issues/64#issuecomment-1085710847


Skip 'this' for a better window check that actually works and passes tests

This PR implements the safer IS_BROWSER test described in #1598.
In a nutshell, if the window object is shimmed for some reason in node environments, styled-components will try to rehydrate the styles on the server. This PR implements a more robust browser check to ensure that no browser code will run server-side, even in shimmed environments.

@mxstbr Dang... I would think so, but I'll find out to be 100% sure!

Thanks, much appreciated!

@mxstbr Yes, it's a thing on IE9! Tested in BrowserStack.

@kitten Good point. Will this work better?

@kitten Ha!  We'll just switch the && to a ||, which is what I was THINKING of, and that should work in all cases. Right?

@mxstbr awesome, thank you!! 😄


Updated network-policies.md for default deny all ingress and egress traffic

Updated network-policies.md  for the section "Default deny all ingress and all egress traffic" to refer to the proper file.
Updated network-policy-default-deny-all.yaml
 for proper formatting.

Fixes #19047

/lgtm
@sujaypillai can you add "Fixes #19047" to the initial description?

Page preview:
https://deploy-preview-19052--kubernetes-io-master-staging.netlify.com/docs/concepts/services-networking/network-policies/

/approve

/sig network


Compiler stack overflow, should give Type Mismatch instead

I've whittled down my code to the following example, which causes a stack overflow:
type alias Persisted record = { record | id : Int }
type alias Update record = record -> Int -> record
type Foo record = Foo (Update record) (Persisted record)

bar (Foo update record) =
  let foo = update record
  in "foo"

The key here is that line 3 should be:
type Foo record = Foo (Update (Persisted record)) (Persisted record)

(changing it to this causes things to compile just fine, by the way)
However, instead of getting a type error I get a stack overflow. Interestingly enough, if I pull the update and record arguments to bar out of the ADT and use type annotations it gives me the type error I'd expect:
bar : Update record -> Persisted record -> String
bar update record =
  let foo = update record
  in "foo"

{-
The type annotation for `bar` does not match its definition.

5| bar : Update record -> Persisted record -> String
Could not unify user provided type variable `record`. The most likely cases are:

  1. The type you wrote down is too general. It says any type can go through
     but in fact only a certain type can.
  2. A type variable is probably being shared between two type annotations.
     They are treated as different things in the current implementation, so
     Try commenting out some type annotations and see what happens.

As I infer the type of values flowing through your program, I see a conflict
between these two types:

    Persisted record

    record
-}

Interesting, thanks for the report! Do you think this is a version of #832 or something new?

Okay, I'm gonna guess that it is the same as that issue for now. I'll add a reference over there, so when we fix that issue we can be sure to check if this example is fixed is well.
Thanks again for the report!


Improve Portuguese translation of Compilers guide

Added missing translations, improved some wording and removed extraneous whitespace.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Congrats @diogocampos on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


sqlite undefined. retrieveConnection not working | Ionic Vue | function call

first of all thank you very much for the package. I can successfully create my sqlite database and insert rows and access them and load them all into a page (ion-list). this works perfect. now however I want to implement a filter functionality. with a selection of an ion-select the data should be filtered via an WHERE query. when I try to do that I get the following error:
Uncaught (in promise) TypeError: Cannot read property 'retrieveConnection' of undefined
this happens when I call the same file (same function. different parameter) as the one in which I create the connection but also happens when I put it in a separate file. I have all the proper lines in my main.ts (described at https://github.com/jepiqueau/vue-sqlite-app-starter ) and I use the lines
const app = getCurrentInstance();
const sqlite = app?.appContext.config.globalProperties.$sqlite;

does it has to be in a component or page or can it also be in a function only Typescript file?
the following shortened code looks like this:
import { ref, onMounted, getCurrentInstance } from 'vue';
import { createTablesNoEncryption, importAllAnimals } from '@/utils/utils-init-db';
import { deleteDatabase } from '@/utils/utils-delete-db';

export function getAllAnimals(filterSize?: any) {

    const animals= ref<Animal[]>();
    const app = getCurrentInstance()
    const sqlite = app?.appContext.config.globalProperties.$sqlite;

    const initVDB = async () => {

        // initialize the connection
        const db = await sqlite
            .createConnection("vdb", false, "no-encryption", 1);

        // open db testNew
        let ret = await db.open();
        if (!ret.result) {
            return false;
        }

        // create tables in db
        ret = await db.execute(createTablesNoEncryption);
        if (ret.changes.changes < 0) {
            return false;
        }

        // add two users in db
        ret = await db.execute(importAllAnimals);
        if (ret.changes.changes < 0) {
            return false;
        }
        app?.appContext.config.globalProperties.$existingConn.setExistConn(true);
        return true;
    }

    const loadAnimals = async () => {

         // initialize the connection
         const db = await sqlite
         .createConnection("vdb", false, "no-encryption", 1);

         let ret: any = await deleteDatabase(db); //TODO: remove Line when RELEASE

         ret = await db.open();
            if (!ret.result) {
                console.log("error opening DB");
                return false;
            }

        ret = await db.query("SELECT * FROM animal");

        if(ret.values.length !== 33) {
            await initVDB();
            ret = await db.query("SELECT * FROM animal");
            if(ret.values.length == 33) {
                animals.value = ret.values;
                console.log("animals loaded");
            }else{
                console.log("error loading animals")
            }
        } else {
            animals .value = ret.values;
            console.log("animals loaded");
        }

      }

      const filterAnimal= async () => {

        //const animals= ref<Animal[]>();
        //const app = getCurrentInstance()
        //const sqlite = app?.appContext.config.globalProperties.$sqlite;

        // initialize the connection
        console.log("before connection");
        const db =  await sqlite.retrieveConnection("vdb");
        console.log("retrieved connection");

        let ret = await db.open();
        if (!ret.result) {
            console.log("error opening DB");
            //return false;
        }
       console.log("db for filtering opened");

       let where = " WHERE size>20";

       ret = await db.query("SELECT * FROM animal" + where);
       if(ret.values.length >= 0) {
           animals.value = ret.values;
           console.log("animals loaded");
       }
   }

    onMounted(async () => {
        if(filterSize == undefined){
          loadAnimals();
        }
    });

    if(filterSize != undefined){
        filterAnimal();
    }

    return animals;
}

Windows10. "@capacitor-community/sqlite": "^2.9.9". "vue-sqlite-hook": "^1.0.0". "@ionic/vue": "^5.4.0"
Samsung Galax S7. Android

@Snogo I only test it from a component call by a view where i encapsulate the component into a Suspense for dealing with asynchroneous functions like this for the component ExistingConnTest
          <Suspense>
            <template #default>
              <ExistingConnTest />
            </template>
            <template #feedback>
              <div> Loading ... </div>
            </template>
          </Suspense>

I never test it like you do. Can you show how this function is called

I see. here are the two code snippets of interest:
 <ion-select multiple="false" cancel-text="back" ok-text="ok" v-model="filterSize" @ionChange="onChange($event, filterSize)">
          <ion-select-option value="0">small</ion-select-option>
          <ion-select-option value="1">medium</ion-select-option>
          <ion-select-option value="2">large</ion-select-option>
        </ion-select>
 <ion-list>

...

         <Suspense>
         <ion-item :key="animal.id" v-for="animal in animals">
           <ion-label>
                <h2>{{ animal.name_dt }}</h2>
              </ion-label>
         </ion-item>
         </Suspense>
        </ion-list>

and
 setup() {
    console.log("Animals setup");
    let animals = getAllAnimals();
    const filterSize = ref([]);
    const onChange = async (e: any, filter: any) => {
      filter = e.target.value;
      filterSize.value = filter;
      console.log(JSON.stringify(filterSize.value));
      animals = getAllAnimals(filterSize.value);
    }
     return { animals, filterSize, onChange }
  },

@Snogo can you also share createTablesNoEncryption, importAllAnimals so i can try to reproduce. Would be in fact better if you can share the whole code on github

@Snogo i do not see where you call initVDB, Would changing
    if(filterSize != undefined){
        filterAnimal();
    }

by
    if(filterSize != undefined){
       async () => {
          filterAnimal();
      }
    }

make a difference

you are right. should put it in async but then somehow filterAnimal is not called anymore (not console outputs)
and initVDB is called inside loadAnimal  if there is no data in the sqlite database
I send you an invitation to the GitHub

@Snogo ok thanks

@Snogo yes i did not saw it in a first look
if you do this can it solved
    onMounted(async () => {
        if(filterSize == undefined){
          loadAnimals();
        } else {
          filterAnimal()
        }
    });

true. this is actually how I wanted it to be - but again filterAnimal() seems to be mysteriously not called anymore
maybe in the second function call in the same file in the LifeCycle onMounted  is not fired anymore (?)

@Snogo Can you try this filterSize is a ref so
    onMounted(async () => {
        if(filterSize.value != undefined){
          filterAnimal();
        } else {
          loadAnimals();
        }
    });

@Snogo i have try to implement your stuff in my app but it seems that the ion-select ionChange is not triggered so it never calls the filterAnimal

@Snogo Can you try this filterSize is a ref so
    onMounted(async () => {
        if(filterSize.value != undefined){
          filterAnimal();
        } else {
          loadAnimals();
        }
    });

I did but actually I give over filterSize.value in the parameter. thus it shouldn't be a ref anymore. I will also get a runtime error if I put that in the onMounted event for the first call of the function (loadAnimals)

@Snogo i have try to implement your stuff in my app but it seems that the ion-select ionChange is not triggered so it never calls the filterAnimal

ionChange is triggered. it actually tells me the correctly selected value of the ion-select in the console - however the onMounted event is not triggered again (a second time after loading the data). this is strange
and I don't think I can code a different component based solution because inter alia of the nature of separation of ion-list and ion-select. do you have another idea? I guess I am using the Typescript function call wrongly (with onMounted) and then somehow the sqlite reference is not ready

about the onMounted not firing. it makes sense according to the Ionic Docs :

Ionic Vue manages the lifetime of a page, certain events might not fire when you expect them to. For instance, mounted fires the first time a page is displayed, but if you navigate away from the page Ionic Framework might keep the page around in the DOM, and a subsequent visit to the page might not call mounted again.

I now tried to close the sqlite connection everytime I finish doing something with the database before calling filterAnimal with no effect unfortunately. also the line app?.appContext.config.globalProperties.$existingConn.setExistConn(true); when trying to retrieve the connection also didn't make a change. everytime filterAnimal  gets called I get  Uncaught (in promise) TypeError: Cannot read property 'createConnection' of undefined because sqlite is undefined

@jepiqueau I put it now all in the .vue file in it works! the file gets huge and its against the project structure but at least it works now. file this as solved for now. don't know why the function calls don't work

@Snogo i finally got it look at https://github.com/jepiqueau/vue-sqlite-app-starter/tree/refactor/src/components/Animals it works wit a new version of the plugin 2.9.12 and a new version of the vue-sqlite-hook 1.0.1 Tell me if you like it

@jepiqueau thank you very much
however i just tried to use your new code with mine but get this error
Property 'isDBOpen' does not exist on type 'SQLiteDBConnection'
I have updated to the new packages  plugin 2.9.12 and vue-sqlite-hook 1.0.1

@Snogo Can you close the issue if everything work fine or i will close it to morrow

I didn't use the same code structure as before for now but got no problems anymore with getting the SQLconnection so far with your fix. thus I will close this issue


Branch coverage for BinarySearchTree<T::getDFS and BinarySearchTree<T::replaceNodeWithNode

Implement branch coverage by manual instrumentation of the source code.
Use the "branch coverage" branch on git for this, as this code is not permanent.

Clover showed a 90% coverage for getDFS(). When manually checked, we had 3 branches uncovered out of 27.


Cannot assign to read only property '_recording'

We're receiving an error when trying to use nockback (see below) with the latest version of node (0.12.2). We tried with an older version of node 0.10.0 and it worked. Here's a gist of the code to test with.
Message:
     TypeError: Cannot assign to read only property '_recording' of http://tablexi.com
   Stacktrace:
     TypeError: Cannot assign to read only property '_recording' of http://tablexi.com
    at /Users/tablexi/Downloads/nock-wtf/node_modules/nock/lib/recorder.js:196:24
    at Object.module.request (/Users/tablexi/Downloads/nock-wtf/node_modules/nock/lib/common.js:127:14)
    at Object.exports.get (http.js:53:21)
    at Object.<anonymous> (/Users/tablexi/Downloads/nock-wtf/spec/wtfSpec.js:10:18)
    at Back (/Users/tablexi/Downloads/nock-wtf/node_modules/nock/lib/back.js:54:12)
    at null.<anonymous> (/Users/tablexi/Downloads/nock-wtf/spec/wtfSpec.js:9:9)
    at null.<anonymous> (/usr/local/lib/node_modules/jasmine-node/lib/jasmine-node/async-callback.js:45:37)

@jdzak I'm having a hard time reproducing this. Can you send me a piece of code that triggers this?

I think I spotted the problem in your gist:
var nockBack = require("nock").back;
var http = require("http");

nockBack.fixtures = __dirname + "/fixtures";
nockBack.setMode("record");

describe('x', function() {
  it('y', function(done) {
    nockBack('whatever.json', function(nockDone) {
      http.get("http://tablexi.com", function() {
        console.log(arguments);
      });
      nockDone();
      done();
    });
  });
});

You're calling nockDone() too soon, and the fixture gets recorder empty. You have to let the request completely finish before you do that.
Here's an example of how to do it:
var test     = require('tap').test;
var nock = require('../');
var nockBack = nock.back;
var http = require("http");

nock.enableNetConnect();
nockBack.fixtures = __dirname + "/fixtures";
nockBack.setMode("record");

test('recording', function(t) {
  nockBack('recording_test.json', function(nockDone) {
    http.get('http://tablexi.com', function(res) {
      res.once('end', function() {
        nockDone();
        t.end();
      });
    });
  });
});
``

I copied your code, but ran into the same issue. Here's the stracktrace I got with your example.
TAP version 13
# recording
not ok 1 TypeError: Cannot assign to read only property '_recording' of http://tablexi.com
  ---
    type:    TypeError
    message: |
      Cannot assign to read only property '_recording' of http://tablexi.com
    code:    ~
    errno:   ~
    file:    /Users/tablexi/Downloads/nock-error/node_modules/nock/lib/common.js
    line:    127
    column:  14
    stack:
      - |
        /Users/tablexi/Downloads/nock-error/node_modules/nock/lib/recorder.js:196:24
      - |
        Object.module.request (/Users/tablexi/Downloads/nock-error/node_modules/nock/lib/common.js:127:14)
      - |
        Object.exports.get (http.js:53:21)
      - |
        Object.<anonymous> (/Users/tablexi/Downloads/nock-error/spec/wtfSpec.js:31:10)
      - |
        Back (/Users/tablexi/Downloads/nock-error/node_modules/nock/lib/back.js:54:12)
      - |
        Test.<anonymous> (/Users/tablexi/Downloads/nock-error/spec/wtfSpec.js:30:3)
      - |
        Test.emit (events.js:129:20)
      - |
        Test.emit (/Users/tablexi/Downloads/nock-error/node_modules/tap/lib/tap-test.js:104:8)
      - |
        GlobalHarness.Harness.process (/Users/tablexi/Downloads/nock-error/node_modules/tap/lib/tap-harness.js:87:13)
      - |
        process._tickCallback (node.js:355:11)
    thrown:  true
  ...

Here's my example project I'm getting the error with.
https://www.dropbox.com/s/6miualxp7v1o7j0/nock-error.zip?dl=0

Fix landed in v1.6.1.

@pgte Thanks for fixing this so quickly! You're awesome.


add exclude_modeladmins option

Coverage increased (+1.2%) to 90.972% when pulling e94f55188b07013be35fa9ad23bce86c3a4db2fe on PetrDlouhy:master into 53ecdfa9604cbd049e34930f48845d445af452e5 on greyside:master.

Coverage increased (+1.2%) to 90.972% when pulling e94f55188b07013be35fa9ad23bce86c3a4db2fe on PetrDlouhy:master into 53ecdfa9604cbd049e34930f48845d445af452e5 on greyside:master.

Coverage increased (+1.2%) to 90.972% when pulling 2bb265daa1870e6ea98144b9e8a1c5edab54e045 on PetrDlouhy:master into 53ecdfa9604cbd049e34930f48845d445af452e5 on greyside:master.

Coverage increased (+2.6%) to 92.361% when pulling 681a2610485db06c947eea03b93fbaaebe59236d on PetrDlouhy:master into 53ecdfa9604cbd049e34930f48845d445af452e5 on greyside:master.

Sorry for not getting to this sooner. Did you still want this merged?

No, this is replaced by #8 which contains all commits from here. I am still working on improving the PR (increasing the coverage a bit more and cleaning some details including that fixture), so if you wait few minutes, you can merge it in better shape. I will write on #8 after I am finished.


Error: Failed to load the llama dynamic library. Segmentation fault

platform：Intel(R) Xeon(R) Gold 6150 CPU @ 2.70GHz
os: Suse 13
model：mistralai/Mistral-7B-Instruct-v0.2
ipex-llm：2.1.0b20240515
transformers: 4.37.0
ldd: 2.22
gcc/g++: 11.1.0
After Loading checkpoint shards 100%, it shows:
Error: Failed to load the llama dynamic library. Segmentation fault

Hi, @eugeooi !
We tried running Mistral CPU example with Mistral-7B-Instruct-v0.2 model. However, we didn't reproduce your result.
Could you please provide more information e.g. output of pip list, full error message (include traceback) and minimal reproducible code example about this issue?
Please feel free to ask if you have any questions. :)

pip list:
Package                  Version
------------------------ --------------
accelerate               0.21.0
antlr4-python3-runtime   4.9.3
certifi                  2024.6.2
charset-normalizer       3.3.2
filelock                 3.14.0
fsspec                   2024.6.0
huggingface-hub          0.23.2
idna                     3.7
intel-openmp             2024.1.2
ipex-llm                 2.1.0b20240515
Jinja2                   3.1.4
MarkupSafe               2.1.5
mpmath                   1.3.0
networkx                 3.3
numpy                    1.26.4
nvidia-cublas-cu12       <IP_ADDRESS>
nvidia-cuda-cupti-cu12   12.1.105
nvidia-cuda-nvrtc-cu12   12.1.105
nvidia-cuda-runtime-cu12 12.1.105
nvidia-cudnn-cu12        <IP_ADDRESS>
nvidia-cufft-cu12        <IP_ADDRESS>
nvidia-curand-cu12       <IP_ADDRESS>
nvidia-cusolver-cu12     <IP_ADDRESS>
nvidia-cusparse-cu12     <IP_ADDRESS>
nvidia-nccl-cu12         2.20.5
nvidia-nvjitlink-cu12    12.5.40
nvidia-nvtx-cu12         12.1.105
omegaconf                2.3.0
packaging                24.0
pandas                   2.2.2
pip                      22.3.1
protobuf                 5.27.0
psutil                   5.9.8
py-cpuinfo               9.0.0
python-dateutil          2.9.0.post0
pytz                     2024.1
PyYAML                   6.0.1
regex                    2024.5.15
requests                 2.32.3
safetensors              0.4.3
sentencepiece            0.2.0
setuptools               65.5.0
six                      1.16.0
sympy                    1.12.1
tabulate                 0.9.0
tokenizers               0.15.2
torch                    2.3.0
tqdm                     4.66.4
transformers             4.37.0
triton                   2.3.0
typing_extensions        4.12.1
tzdata                   2024.1
urllib3                  2.2.1

When I tried to run the sample script, it shows error:
python generate.py
/user/ipex_llm/lib/python3.11/site-packages/transformers/utils/hub.py:124: FutureWarning: Using `TRANSFORMERS_CACHE` is deprecated and will be removed in v5 of Transformers. Use `HF_HOME` instead.
  warnings.warn(
/user/ipex_llm/lib/python3.11/site-packages/huggingface_hub/file_download.py:1132: FutureWarning: `resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.
  warnings.warn(
Error: Failed to load the llama dynamic library.
Segmentation fault

But when I ran the same script on other Core-based system on Ubuntu 22.04, it works fine.

hi @JinBridger, is there any update on this issue?

hi @JinBridger, is there any update on this issue?

Hi, @eugeooi  Looks like it is an issue with your glibc library. Could you please provide your glibc version? :)

$ ldd --version

ldd (GNU libc) 2.22
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

Hi @eugeooi,
We recommend glibc version >= 2.28. :)


Domain not handle None object

validators None issue:
code:
def validator_test():
    import validators
    if validators.domain(None):
        print("None object is FQDN")
    else:
        print("None object is NOT FQDN")

error
Traceback (most recent call last):
  File "/home/vagrant/scadafence/rea-helper.py", line 49, in <module>
    main()
  File "/home/vagrant/scadafence/rea-helper.py", line 45, in main
    validator_test()
  File "/home/vagrant/scadafence/rea-helper.py", line 33, in validator_test
    if validators.domain(None):
  File "</home/vagrant/scadafence/venv/local/lib/python2.7/site-packages/decorator.pyc:decorator-gen-2>", line 2, in domain
  File "/home/vagrant/scadafence/venv/local/lib/python2.7/site-packages/validators/utils.py", line 83, in wrapper
    value = func(*args, **kwargs)
  File "/home/vagrant/scadafence/venv/local/lib/python2.7/site-packages/validators/domain.py", line 60, in domain
    return pattern.match(to_unicode(value).encode('idna').decode('ascii'))
AttributeError: 'NoneType' object has no attribute 'encode'

Of course, I can check it before using the validators, but the validator already checks it, so why not to handle the "None" case?
After all, None is not an FQDN...

a solution may be in the catch statement:
try:
        return pattern.match(to_unicode(value).encode('idna').decode('ascii'))
    except (UnicodeError, AttributeError) as e:
        return False

Open new PR:
https://github.com/kvesteri/validators/pull/144

I looked at other validators (not only the domain) and it seems that all of them don't handling the "None" as input...
If this PR will be approved I can also fix all the validators to handle the "None" case...


Drag performance in Chrome

What is this (program) business?

Maybe this SO answer can help you a bit: Slow javascript execution in chrome, profiler yields (program).


pkg/dev_compiler/test/expression_compiler/expression_compiler_e2e_amd_sound_test broke: Pass -> RuntimeError

See https://ci.chromium.org/ui/p/dart/builders/ci.sandbox/pkg-mac-release/25360/overview
  Exception: Compilation failed with: [../../../x/t/ddc_eval_test_anchorJgjKP4/ddc_eval_test6Plea7/test.dart:7:21: Error: Variable pattern 'a' doesn't have the same type or finality in all cases.
            case [int a, String b] || [String a, int b]:
                      ^, ../../../x/t/ddc_eval_test_anchorJgjKP4/ddc_eval_test6Plea7/test.dart:7:31: Error: Variable pattern 'b' doesn't have the same type or finality in all cases.
            case [int a, String b] || [String a, int b]:
                                ^]

I've approved these failures.

@annagrin It looks like some of the expression compiler tests added for patterns are now giving compile time errors.


hdfview: mark as broken

Description of changes
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks, let's leave it broken until swt upgraded.

I'm slightly more hopeful that if upstream (in a new version) will use a newer SWT, it will also work, just as it worked until ~2 months ago.


Update GitBook to new contributing guidelines

See https://github.com/inttter/md-badges/commit/34c2feceada39108bf843dc689d39b89e5afaf3b for the new guidelines.

Added to GitBook, closing this.


fix: show zero values when dedicated resources is disabled

fixes #2119

Codecov Report

Merging #2162 (b4158fa) into main (960d815) will not change coverage.
Report is 2 commits behind head on main.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main    #2162   +/-   ##
=======================================
  Coverage   87.07%   87.07%
=======================================
  Files          85       85
  Lines        9312     9312
  Branches      494      494
=======================================
  Hits         8108     8108
  Misses       1204     1204


Automated cherry pick of #4459: fix: openstack image: vmdk -> qcow2

Cherry pick of #4459 on release/2.13.
#4459: fix: openstack image: vmdk -> qcow2

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.13@16544f5). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             release/2.13   #4460   +/-   ##
==============================================
  Coverage                ?   6.85%
==============================================
  Files                   ?     521
  Lines                   ?   88602
  Branches                ?       0
==============================================
  Hits                    ?    6074
  Misses                  ?   82021
  Partials                ?     507

Flag
Coverage Δ

#aFlag
6.85% <ø> (?)

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 16544f5...ab2d1c3. Read the comment docs.

/lgtm

/approve

/approve


"Building..." message not removed (compiling in watch mode, using Workspace TSC).

I'm using the TypeScript Compiler from the Workspace (not the global one), in a shared project.
When compiling in watch mode, after it finishes compiling the first time, the "Building..." message is never removed.

The "Building..." message should be removed every time it finishes compiling in watch mode.
The message works fine if I use the Global TypeScript Compiler (to compile in watch mode) or if I don't use watch mode at all.
Maybe the way I use the Workspace TSC is wrong? This is the content of my tasks.json containing both tasks, using Workspace and Global TSC:
{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "Debug (workspace tsc)",
			"type": "shell",
			"command": "node",
			"args": [
                "${workspaceFolder}\\node_modules\\typescript\\bin\\tsc",
                "-p",
                "tsconfig_debug.json",
				"--watch"
			],
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "presentation": {
                "clear": true
            },
            "problemMatcher": [
                "$tsc-watch"
            ],
        },
        {
            "label": "Debug (global tsc)",
            "type": "typescript",
            "tsconfig": "tsconfig_debug.json",
            "option": "watch",
            "problemMatcher": [
                "$tsc-watch"
            ],
            "group": "build",
            "presentation": {
                "clear": true
            }
        }
    ]
}

Tested on: Windows 10 with VSCode 1.37.1 and VSCode Insiders 1.38.0.
Does this issue occur when all extensions are disabled?: Yes
Related issues: #60396 and #50943.

You need to set "isBackground": true,

Works like a charm! Thanks very much!


Grid viewer does not work on high contrast

At least in HC black. #3134 for details

I can't repro on Win10 and styling in XAML seem to be default/VS.

My repro was on Win7.

OK, most probably fix for #3145 will resolve this one as well unless this is something with WPF on Win7. In any case, it is not very high priority since things appears OK on Win10.

https://github.com/Microsoft/RTVS/commit/953ce796947f6a11f334ab12f49cefbb30b382fa, reopen if there are issues


Add overflow:hidden when overlay is shown

Targets https://github.com/segmentio/evergreen/issues/261
Rather than setting overflow to null on componentWillUnmount, I have set it to the default value of overflow. i.e. visible

This is now implemented (just need to make a new release soon)


chore: move examples to separate sub-projects

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

#146  👈
#145
#144
#143
#142
#141
#140
#139
#138
#137
#136
main

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

Join @NathanFlurry and the rest of your teammates on  Graphite


Rename vendored OCaml libraries to avoid conflicts

To minimize code churn, each file using the vendored libraries has an
alias to the original module name.
This is a replacement for #1904 in a form that is hopefully more friendly to all of Reason's compilation targets.
Fixes #1740

Works. Thanks!

Thanks, just found a case where this saved me!

I'm glad it helped!


feat: let apply_fun use CoeFun and dependent functions

Changes apply_fun to use the main function application elaborator, then uses Lean.MVarId.congrN to solve for a congruence proof. This means that apply_fun f at h should work whenever f applies to both sides of the equation h (even when coercions need to be involved).

@semorrison The TermElab monad ends up being very helpful here, and I was able to delete a lot of what I wrote. Floris mentioned Term.elabAppArgs to me today, which ends up doing most of the work.  It's nice being able to use this rather than writing my own half-baked version of the elaborator!
Who would have thought apply_fun could do this?
example (f : ℤ ≃ ℤ) (a b : ℕ) (h : a = b) : True := by
  apply_fun f at h
  guard_hyp h : f a = f b -- coercions on `f`, `a`, and `b`!

bors merge


Some notes on the "universal" field config

Some notes from the discussion Friday, in addition to those in the notion doc. Probably needs editing/cleaning up..
Not sure if notes should be added to the repo or stored elsewhere?

@molomby I've captured these in Notion.


⚠ Bofrost.lu has degraded performance

In eb7e951, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1306 ms

Resolved: Bofrost.lu performance has improved in 5cac52c after 8 minutes.


Example with only mandatory fields does not work

Hi,
this example https://github.com/digitalbazaar/ecdsa-sd-2023-cryptosuite#creating-a-derived-proof-with-only-mandatory-fields-revealed does not seem to be possible with the latest version. I am getting an error along the lines of having to specify some disclosable data.

This test (https://github.com/digitalbazaar/ecdsa-sd-2023-cryptosuite/blob/main/test/derive.spec.js#L281) in the test suite still passes.
It could be that the examples were generated with a bug in them in the past, so I just regenerated them now. The examples are produced from the test suite -- so if those tests are passing, the examples should be as well. Perhaps take another look now with the updated example data? If you're having trouble at that point, could you provide an example to run or more details / code snippets and the error text you're seeing? Thanks!

@lemoustachiste,
I ran the above and hit that error. It looks like there aren't any pointers provided at all -- no mandatory pointers and no selective pointers. This would, in fact, result in no data being generated, hence the error. When the original VC is signed, if it has no mandatory pointers provided, then something selective will have to be provided later, but I suspect you should be passing some mandatory pointer when signing the VC to begin with, such as requiring the issuer and issuanceDate fields, minimally.
You could make this change here:
    const suite = new DataIntegrityProof({
      signer: keyPair.signer(),
      cryptosuite: createSignCryptosuite({
        mandatoryPointers: [
          '/issuanceDate',
          '/issuer'
        ]
      })
    });

https://github.com/blockchain-certificates/poc-ecdsa-sd-2023-blockcerts/blob/repro/error-no-disclosure/src/suite/ecdsa-sd-2023.ts#L37-L40
If I make that change locally, then npm run derive passes without an error.
I'll note that even in the case that nothing is mandatory in credentialSubject, a holder would need to selectively disclose something from credentialSubject to generate a valid VC (because a VC requires a credentialSubject property). The ecdsa-sd cryptosuite doesn't care about this (it's at a lower layer), but a VC consumer would.

Ah I must have missed that possibility. That's great that answers one of the questions I asked in the CCG group.
From a philosophical standpoint, would it be expected from the issuer to always specify what are mandatory fields in the VC, or since we can specify them at derive time, we could have either the wallet or the verifier specify those? And subsidiary question, can you augment the initial list from the issuer at derive time, or would that overwrite it?
Thanks

@lemoustachiste,

Ah I must have missed that possibility. That's great that answers one of the questions I asked in the CCG group.
From a philosophical standpoint, would it be expected from the issuer to always specify what are mandatory fields in the VC, or since we can specify them at derive time, we could have either the wallet or the verifier specify those?

To be clear, there are two different kinds of fields to be disclosed: mandatory and selective (and either set of these can be empty but not both). Only the issuer can define what is mandatory to disclose and must do so when the original VC is issued and the base proof is added. If these fields are not disclosed at derive time, the design is such that verification of the derived VC will fail.
The cryptosuite algorithms are also designed such that the mandatory to disclose fields are automatically disclosed when deriving. Which fields are mandatory to disclose is expressed in the base proof data so implementations just use this information automatically -- and then add any additionally specified selective-to-disclose fields specified at derive time.
So, at derive time, any other (non-mandatory) fields can be selectively disclosed, including nothing extra at all. Of course, something needs to be disclosed, so if an issuer didn't say anything was mandatory, then the disclosure must add something selective -- or else the VC would be totally empty which is treated as an error.
The cryptosuite isn't meant to be prescriptive at the VC layer in what MUST be mandatory or not, so it's up to VC designers and issuers to make those choices. But, in general, issuers are expected to make things like issuer and issuanceDate/expirationDate (for VC 1.1 and validFrom/validUntil if present, for VC 2.0) mandatory to disclose.
As for what is selectively disclosed, expectations are also that verifiers will ask for what they want. The way this is done today with, for example, a VPR with a QueryByExample query coming in from VC API / CHAPI, is that the QueryByExample query can be translated into JSON pointers and passed to the disclose/derive cryptosuite. A digital wallet can show the user which fields will be disclosed then, based on what the verifier is looking for. A more advanced digital wallet could allow the user to add / remove certain fields at-will, however, doing so might just make the verifier refuse to continue whatever work flow is in progress (or perhaps they will ask again for something different, it is all use case specific).
In implementations we're finding that if a verifier does not ask for any information in the credential subject to be disclosed, then a digital wallet may recommend disclosing the whole credential subject or just its id, if present. This is because a VC MUST have a credentialSubject with something in to be a valid VC. Either way, users should be made aware of what will be disclosed. Digital wallets will evolve over time to figure out how to best serve users in these circumstances.

And subsidiary question, can you augment the initial list from the issuer at derive time, or would that overwrite it?

So you can't override the list of mandatory fields from the issuer, but providing selective disclosure JSON pointers "augments it" by disclosing more than what is mandatory.
Note: Technically speaking (down in the cryptosuite layer / spec itself), the way mandatory fields are revealed and secured is different from the selectively disclosable fields. The mandatory ones are bound together and secured with a single hash and signature whereas the selectively disclosable ones each get their own signature, which is only revealed if the selectively disclosable field is also revealed (this approach provides some additional benefits such as hiding side channel information around the number of fields and a reduction in proof size). The mandatory hash is always recomputed by the verifier from the presented data, and if it does not match the original value, the signature verification will fail.

Thanks Dave,
I have been able to work with a mandatory fields derived cert and verify, so at a high level I understand the features of this library.
May I suggest that for a better understanding the example on the README highlights that you can/should pass mandatory fields at sign time?
When I looked at the API of createSignCryptosuite it became obvious but I missed that as I just re-implemented the example to get to the initial signature of the document.


New layout nodes

Added two new layout nodes

The pull request now has conflicts. Can you check please? It's too late for me right now =)

I did the merge and updated the pull request.


Prevent overwriting petnames via Follow User form

Fixes https://github.com/subconsciousnetwork/subconscious/issues/769
Demo
https://github.com/subconsciousnetwork/subconscious/assets/5009316/74cbe177-07a9-4763-acf0-63d7d770e383
Questions

Is it better to:

mark collision as a validation error and force the user to pick a new name
replace the name with an available suffixed version in the form
dismiss the form and find a unique name in the background, adding a suffix if needed

I tried (1) first and liked it but currently we have (2). (3) seems like a hard sell without #333.
Changes

Prevent overwriting petnames
Surface overwrite petname error to UI
Suggest a unique name if there is a collision

@gordonbrander Do you think it's better to:

mark collision as a validation error and force the user to pick a new name
replace the name with an available suffixed version in the form, or
dismiss the form and find a unique name in the background, adding a suffix if needed

I tried (1) first and liked it but currently we have (2). (3) seems like a hard sell without https://github.com/subconsciousnetwork/subconscious/issues/333.


[NO MERGE] Small test for CI speed

A DB tweak to be done properly if results are good

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)


how avoid translation failed, because of empty result ?

Hello, i always encounter 503 with message
{
    "code": 503,
    "message": "Translation failed, API returns an empty result."
}

how to avoid this ? is premium going to help in this case ?
and is premium really unlimited for translating ?
i have a batch of text that need to be translated,
thanks..

Maybe you can try using the Pro API with dl_session.

I have the same issue.
Although the test passed using curl, the Immersive Translate always returned {"code":503,"message":"Translation failed, API returns an empty result."}
I am using the /v1/translate endpoint and have configured dl_session.

Perhaps the requests initiated by Immersive Translate are too frequent and the intervals are too short.

Perhaps the requests initiated by Immersive Translate are too frequent and the intervals are too short.

Thanks for your reply. But that's not the case.
I just clicked Verify service once.

This is the log of everything:

Could this be an Immersive Translate bug? Likely, sending the wrong header?

Perhaps the requests initiated by Immersive Translate are too frequent and the intervals are too short.
Same Issue

Perhaps the requests initiated by Immersive Translate are too frequent and the intervals are too short.

Same Issue

No questions, someone just DDoSed me a lot of time

tbh, free tier is very unreliable, you guys should try Pro version, it much better -- never face any issue so far myself


Missing loader for example code

This repo includes a piece of example code, assets/deck.example, and the tutorial provides instructions for including it in the presentation by adding the code
const code = {
  deckSample: require('../assets/deck.example')
};

and the slide
<Slide>
  <ComponentPlayground code={code.deckSample} theme={dark} />
</Slide>

However, doing so yields an error:
ERROR in ./assets/deck.example 1:0
Module parse failed: 'return' outside of function (1:0)
You may need an appropriate loader to handle this file type.
> return (
|   <Deck transition={['zoom','slide']} transitionDuration={800}>
|     <Slide bgColor="primary">
 @ ./presentation/index.js 41:14-47
 @ ./index.js
 @ multi @babel/polyfill webpack-hot-middleware/client react-hot-loader/patch ./index

I was able to get the example code displayed by updating the Webpack config to use the raw loader for .example files:
{
  test: /\.example$/i,
  use: 'raw-loader',
},

Same problem


create a matplotlib widget with the same properties as the cytoscape widget and save that widget to a file

This would be a way to get around the export limitations of cytoscape widgets.

Added matplotlib widget and automatic saving in version 1.1.0


Mean of empty slice error?

Can any one tell me, while creating a training model the below error is triggering.....so please kindly provide me the solution..
C:\Python27\lib\site-packages\numpy\core\fromnumeric.py:2957: RuntimeWarning: Mean of empty slice.
  out=out, **kwargs)
Traceback (most recent call last):
  File "ocropus-rtrain", line 293, in <module>
    network.lnorm.measure(np.amax(line)-line)
  File "C:\Users\jenova jasmine\Desktop\ocropy-master\ocrolib\lineest.py", line 38, in measure
    self.mad = mean(deltas[line!=0])
  File "C:\Python27\lib\site-packages\numpy\core\fromnumeric.py", line 2957, in mean
    out=out, **kwargs)
  File "C:\Python27\lib\site-packages\numpy\core\_methods.py", line 80, in _mean
    ret = ret.dtype.type(ret / rcount)
FloatingPointError: invalid value encountered in double_scalars

Environment Setup

Python version: 2.7

Git revision of ocropy:
Operating System and version: windows 7

What command did you use for training? Besides the warning there is also a FloatingPointError... Do you see this immediately or is the training process working for a while? Does the ./run-rtrain work?


Add support for client-go exec auth plugins

To support a kubeconfig with a user such as
users:
- name: aws
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      command: heptio-authenticator-aws
      args:
        - "token"
        - "-i"
        - "terraform-eks-demo"

Note, the client.authentication.k8s.io API group is alpha prior to Kubernetes v1.11 and it is beta in v1.11.

Whoops, this was added in #417.


Update Get-SmbShare.md

added description for smbshare

Docs Build status updates of commit 76bebac:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012r2-ps/smbshare/Get-SmbShare.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@dariomws306 @get-itips @tseward
Peer review needed for this PR that addresses a fill in the blank area in the article. Thanks.

better with the example

Can you please provide more textual details about what the input is so I know how to use it? Perhaps adding an additional example in the Examples section would be helpful.

I have added an example . The only values accepted are CSV and Default.

Docs Build status updates of commit 11cd2dc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012r2-ps/smbshare/Get-SmbShare.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

I think we should also add possible values here:

I think we should also add possible values here:

Default is a Value, I can replace it with CSV which is another accepted value ..  Let me know.

@dariomws306 Any further input?

Example is ok. But I think we should add possible values to the description. For example:
Specifies the input to this cmdlet. You can use this parameter, or you can pipe the input to this cmdlet. Possible values are:

Default
CSV
SBL
SR

Docs Build status updates of commit 5595c09:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012r2-ps/smbshare/Get-SmbShare.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 674c701:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012r2-ps/smbshare/Get-SmbShare.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Docs typo: missing ` in insertSpaces

Following https://github.com/microsoft/monaco-editor/pull/1824.

Thank you!


Asynchronous event listeners not waiting

What happened?
I tried calling this.wait() inside of a handler for the 'fetchcomplete' event, as explained here. The crawler continued on without waiting. I'm using v1.1.1.
What should have happened?
I expected the crawler to pause while some async processing took place, then continue when the function returned by this.wait() was invoked (or 10 seconds passed).
Steps to reproduce the problem
This code seems to reproduce the problem I was having. If you look at the console while running it, it gets flooded with URLs.
const Crawler = require('simplecrawler');

const crawler = Crawler('https://google.com');

crawler.on('fetchcomplete', function(queueItem, data, res) {
  const resume = this.wait();
  console.log(queueItem.url)
});

crawler.start();

Hi Cory — thanks for filing an issue!
The purpose of the wait method is not to halt all other operations in process, but to prevent the crawler from completing and terminating the crawl, if you're still waiting on the results of an asynchronous operation to, for example, add some items to the queue (which would continue the crawl, even if the current queue is exhausted.)
The documentation for this method could be a bit clearer, but it does say:

Sometimes, you might want to wait for simplecrawler to wait for you while you perform some asynchronous tasks in an event listener, instead of having it racing off and firing the complete event, halting your crawl. For example, if you're doing your own link discovery using an asynchronous library method.

I am curious to hear about your use case though — I might be able to assist you to solve it a different way.


jwt-play should automatically add "iat" in addition to "exp"

The security section of your website says "you should always add an issuedAt attribute to it". I think jwt-play should automatically add iat and update during session refreshes.

While we're at it, is nbf worth adding to the token as well?

 There is always that one person with a use-case where it is not needed and there is no way to remove it anymore... There is plenty of other ways to generate a different tokens without using iat for example, using nbf is one of them.
I could consider having it behind a config property enabling it if someone want to do a PR.

Following the RFC-7519, most of the Claims are optional. I think there's no need to add this feature.


vibed spelling

I think that vibed should be named everywhere as vibed, not vibe-d, because sometimes it's sometimes when you are finding it's on code.dlang.org you are typing vibed, but not vibe-d (as now package called)

Wait is it called vibe.d, vibe-d or vibed now?

The actual name is vibe.d, but unfortunately the dot needs to be represented differently in certain contexts. Using vibe.d.http.server would of course be possible, but is also quite silly, so there I simply dropped the ".d" part. "Vibed" is mostly used as  a short form by people other than me.
I guess this can be kind of confusing, but I'm also not sure what to do about it, renaming the original "vibe.d" to something else is something that I wouldn't want to do at least.