Zero division has lots of behaviors

ergo$ return 1.0 / 0.0;
Response. inf
  :  {emit: Unit[], response: Double, state: Unit}?
ergo$ return 0.0 / 0.0;
Response. nan
  :  {emit: Unit[], response: Double, state: Unit}?
ergo$ return 1 /i 0;
Response. 0
  :  {emit: Unit[], response: Integer, state: Unit}?
ergo$ return 0 /i 0;
Response. 0
  :  {emit: Unit[], response: Integer, state: Unit}?
ergo$ return sqrt(-1.0);
Response. nan

I'm not sure I agree with all of these outcomes (I think they should all be errors — because what happens if you try to serialize nan/inf to JSON?). But I imagine they're not up for negotiation because they're built-in to Qcert. At the very least, then, the behavior should be documented, and there should be ways to check is_nan or is_infinity from Ergo. Also, nan and inf should be globally available constants.

I think Double behavior should be consistent with IEEE spec. I believe it is.
I think Integer behavior should be consistent with .. something. I'm less clear about that. What we see here is Coq's specification for Z (I believe). There is some possibly useful text here:
https://stackoverflow.com/questions/29282819/coq-qarith-division-by-zero-is-zero-why
Also: functions / expressions in Ergo have to be total.

I mean, sure, it's not hard to make things consistent with a spec. But Ergo's users don't know/care about the spec, because they're focused on other things. They will write things like this:
clause yearly_performance_review(request : Request) {
  let output_per_hour = request.total_lines_of_code_written / request.time_worked;
  if output_per_hour < 10.0 { // not working hard enough
    emit LayoffObligation {};
    return "done";
  } else {
    emit RaiseObligation {};
    return "done";
  }
}

and now a person who has 0.0 output and worked 0.0 hours will be given a raise.
I'm sure we can find a way to make arithmetic exceptions cause errors (like enforce) or emit warnings or something. If the goal is to protect users, then saying "it matches a spec" isn't helpful.

I won't comment on how easy/hard it is to make a IEEE 754 implementation -- I just hope no-one else sees this :)
Just couple of points: when we generate code, we have to generate operations on a target language. IEEE floating points are one of the few datatypes well supported across pretty much  all languages. Defining yet another kind of floating point number semantics is actually hard, and generating code for that semantic will be even harder.
Your example is really good, but I would do that with a library (maybe internally based on floats, or maybe based on an arbitrary precision datatype to avoid issues of rounding). Enforce/warning checks could then happen inside that library. If the library is written in Ergo then we avoid problems of portability.

A few more things about this issue, before I close it 🙂

I'm adding a "question" label to the issue
sqrt(-1.0) is a good illustration of why NaN is in the IEEE spec for floating points
JSON's inability to properly support JavaScript numbers is quite a flaw, but sadly well documented. Various not very convincing workarounds are documented here: https://stackoverflow.com/questions/1423081/json-left-out-infinity-and-nan-json-status-in-ecmascript
This is indeed leading to problem when exporting Ergo values to JSON. See #643 and some suggested resolutions.
Ergo's semantic for Double is well founded, based on the flocq formalisation of IEEE 754 (https://www.lri.fr/~melquion/doc/11-arith20-article.pdf) -- but compilation targets underlying implementations for IEEE 754 (number in JavaScript, float in OCaml, etc) so we will have to keep an eye on that.


[WIP] Fix [krbd_exclusive_option} workunit for RHEL 8

RHEL 8 Pass log:
http://pulpito.ceph.redhat.com/julpark-2020-03-30_02:30:09-krbd:rbd-nomount-nautilus-distro-basic-argo/368606/

@julpark-rh please revisit the PR. there are 2526 file changes and some old commits in the PR. rebase or fix your fork. And you are sending the PR to master. why?

Please remove WIP from the PR title

Please delete this PR. I will request PR to Nautilus again. I will remove the WIP PR title as well.


More reliable mobile support for mobile 'interrupt' using touchstart

Love the interrupt feature but was having issues on mobile browsers.  I added a quick check to see if touchstart is enabled (mobile) and, if so, added a one-time listener that used any subsequent touch events to interrupt the scrolling event.  For non-touchstart devices (desktop), continue to use the Tween.prophooks callback since it works great on desktop.
possible resolution to this issue?...
https://github.com/flesler/jquery.scrollTo/issues/131
Thanks! Nate Smith

Hi, I was trying to avoid doing that, because it makes the whole thing messier. If the user doesn't touch, the event remains bound beyond the scrollTo duration, that can cause weird side-effects.
Are you sure there's no way solve this more or less in the same way as Desktop?
About the whitespacing, can you merge the commits? Merging it this way would touch all lines.
You can git reset --soft HEAD^ until you removed all your commits, then create a commit and git push -f. That's what I always do.

I see that. Your demo page works fine on my phone as well (iPhone 6 chrome/safari) but on all pages I test within my application--where I'm scrolling on the window (e.g. "$.scrollTo")--the result is that the page scrolls for about 10-20 px, then stops automatically.
I believe the issue is that mobile browsers can't distinguish between a window scroll via scrollTo and a user physically scrolling.  As a result, the scroll starts then stops almost immediately, since it detects a window scroll (its own in this case).
Hopefully that makes some sense.  I redid my pull request to add a simple one-time listener on the document (targetting "html" and listening for "scroll DOMMouseScroll mousedown mousewheel touchstart" events) that is removed either by executing an interrupt action listed or when the scroll is completed.  If you want to get rid of the "mousedown" listener, no problem. I went back and forth about whether a user clicking should trigger the interrupt.
This approach works in all cases (no need to identify device type) and does not introduce any lag per my testing.
If you already have a full-document selector (like body/html) that I may have missed, then you could even remove the "var $html = $('html');"  part and replace use that existing one to add/remove the interrupt listener.
Would love to know your thoughts. We're using this plugin within our org and would love to integrate these changes directly instead monkey-patching. Great work. Thanks! Nate

Hi, to be honest I'll need to test it in detail before proceeding. I'll try to reproduce the problem with my phone asap.
Cannot assume there is a problem without seeing it.
Note that $('html').off() will unbind all handlers from all events from that element.
The unbinding can be done in the complete() callback of animate(). It's currently only used if user included an onAfter() but that can be easily changed.
I'd advise you to monkey-patch for now and upgrade if the change is indeed deployed.
You should be able to do so without changing the plugin's code, you bind your handler when you call the plugin and unbind on onAfter().

Sounds good man and great catch on the risky .off() call / tip on the complete() callback. I'm going to make those changes in my patch.  Take care!

Just wanted to follow up with the change I'm implementing in my environment (incorporating your tips!)  Still can't figure out why the spacing is always f'd up when I push to your branch but take a look if you get the chance! Peace.


Automated cherry pick of #1441: feature: capability add brands

Cherry pick of #1441 on release/2.10.0.
#1441: feature: capability add brands

/approve
/lgtm


v-bind="object" syntax validation error

Hi!
I am currently migrating one application from vue-cli to vote using the vue-ts template.
In some components I use the <component v-bind="props" /> patterns to pass multiple props in one directive but, when I run vue-tsc --noEmit it seems that vue-tsc is not able to read the props type even if it's correctly typed in the setup method.
For example I have a template like this:
<IntervalEditBox
  v-for="interval in intervalsRef"
  :key="interval.id"
  v-bind="interval"
  @update="update"
  @delete="deleteInterval"
/>

where intervalsRef is defined in the setup method as:
export enum IntervalType {
  Work = 'work',
  ShortBreak = 'short-break',
  LongBreak = 'long-break',
  None = 'none',
}

export interface Interval {
  type: IntervalType;
  duration: number;
  remaining?: number;
  id: string;
}

const intervalsRef = ref<Interval[]>([...props.intervals]);

The error I'm receiving is:
error TS2322: Type '{ key: string; }' is not assignable to type 'Partial<{ type: IntervalType; duration: number; remaining: number; }> & Omit<Readonly<{ type: IntervalType; id: string; duration: number; remaining: number; } & {}> & VNodeProps & AllowedComponentProps & ComponentCustomProps, DefaultKeys<...>> & Omit<...> & Record<...>'.
  Property 'id' is missing in type '{ key: string; }' but required in type 'Omit<Readonly<{ type: IntervalType; id: string; duration: number; remaining: number; } & {}> & VNodeProps & AllowedComponentProps & ComponentCustomProps, DefaultKeys<...>>'.

Any hint on how could I fix this error?

Add will add support for v-bind="..." syntax, thanks for the report! btw this is volar issue. 😅

Thank for your reply.
By the way,  great project! I found a couple of type errors thanks to this! 👍

Great! Thank you! 💯


Data

Hi Haoyu,
I noticed that you preprocessed the data files into tsv format. Do you have the preprocessing script for SemEval_raw_data -> your .tsv, and ACE05_data -> your .tsv? We have both data. And if you need, I can show you our LDC license, so that you can feel free to just send me your data. Thank you for making it easier to reproduce your paper and show them in our work following you.
Best,
Zhijing

@zhijing-jin Unfortunately that preprocessing file is not uploaded into the repo and I do not have access to that anymore since I have already left the company. But writing your onw preprocess script should still be doable.
The output file is a following tsv file format as: text, relation, entity1_start_index, entity1_end_index, dummy_value, entity2_start_index, entity2_end_index, dummy_value. We were putting the text for entity1 and entity2 as the initial value but you can just put a dummy one as it is no longer used in the code. Meanwhile, to construct a multi-relation file, you will need to append  (relation, entity1_start_index, entity1_end_index, dummy_value, entity2_start_index, entity2_end_index, dummy_value) just multiple times.
For more details, you could also refer to the code to parse the input data - https://github.com/helloeve/mre-in-one-pass/blob/master/run_classifier.py#L224-L273

Hi Haoyu,
Do you remember how you dealt with "no-relation" and also "bi-directional relations" such as friendship in ACE05?

For the "no-relation" question: In the ACE05 training set, do you only use the no-relation provided by the original ACE05 dataset, or use the combination of every entity pair to generate additional no-relation instances?
For bi-directional relations: Also for ACE05, for bidirectional relationships such as friendship (because A---friendship--->B will also mean B---friendship--->A), do you auto-complete these and add the other direction into the training data as well?


Error when running 'pongo run' against the official 'kong-plugin' template using WSL2: "nginx: [emerg] bind() to unix:/kong-plugin/servroot/worker_events.sock failed (95: Operation not supported)"

Pongo version: 2.2.0
kong-plugin: master (7d2759493cfb1a73ee01553862210ca4b938b9d3), latest
OS: Windows 11 22H2, WSL[2] <IP_ADDRESS>, Ubuntu 22.04.1
Docker Desktop: 4.15.0 (93002), Docker Engine 20.10.21
Another user/report about the same issue, apparently: https://github.com/Kong/kong-pongo/pull/321#issuecomment-1245602045
danilo@SOPHIA:/mnt/e/workspace/kong-plugin-master$ KONG_IMAGE=kong:3.1.0-ubuntu pongo run
[pongo-INFO] auto-starting the test environment, use the 'pongo down' action to stop it
Kong version: 3.1.0

Stopping after installing dependencies for kong-plugin-myplugin 0.1.0-1

[==========] Running tests from scanned files.
[----------] Global test environment setup.
[----------] Running tests from /kong-plugin/spec/myplugin/01-unit_spec.lua
[ RUN      ] /kong-plugin/spec/myplugin/01-unit_spec.lua @ 18: myplugin: (schema) accepts distinct request_header and response_header
[       OK ] /kong-plugin/spec/myplugin/01-unit_spec.lua @ 18: myplugin: (schema) accepts distinct request_header and response_header (0.40 ms)
[ RUN      ] /kong-plugin/spec/myplugin/01-unit_spec.lua @ 28: myplugin: (schema) does not accept identical request_header and response_header
[       OK ] /kong-plugin/spec/myplugin/01-unit_spec.lua @ 28: myplugin: (schema) does not accept identical request_header and response_header (0.25 ms)
[----------] 2 tests from /kong-plugin/spec/myplugin/01-unit_spec.lua (790.74 ms total)

[----------] Running tests from /kong-plugin/spec/myplugin/02-integration_spec.lua
/kong-plugin/spec/myplugin/02-integration_spec.lua:28: 2022/12/13 17:11:48 [warn] the configuration value 'strict' for configuration property 'worker_consistency' is deprecated
2022/12/13 17:11:48 [warn] the 'worker_consistency' configuration property is deprecated
Error: nginx configuration is invalid (exit code 1):
nginx: the configuration file /kong-plugin/servroot/nginx.conf syntax is ok
nginx: [emerg] bind() to unix:/kong-plugin/servroot/worker_events.sock failed (95: Operation not supported)
nginx: configuration file /kong-plugin/servroot/nginx.conf test failed

  Run with --v (verbose) or --vv (debug) for more details

stack traceback:
        /kong-plugin/spec/myplugin/02-integration_spec.lua:28: in function </kong-plugin/spec/myplugin/02-integration_spec.lua:11>

/kong-plugin/spec/myplugin/02-integration_spec.lua:28: 2022/12/13 17:11:51 [warn] the configuration value 'strict' for configuration property 'worker_consistency' is deprecated
2022/12/13 17:11:51 [warn] the 'worker_consistency' configuration property is deprecated
Error: nginx configuration is invalid (exit code 1):
nginx: the configuration file /kong-plugin/servroot/nginx.conf syntax is ok
nginx: [emerg] bind() to unix:/kong-plugin/servroot/worker_events.sock failed (95: Operation not supported)
nginx: configuration file /kong-plugin/servroot/nginx.conf test failed

  Run with --v (verbose) or --vv (debug) for more details

stack traceback:
        /kong-plugin/spec/myplugin/02-integration_spec.lua:28: in function </kong-plugin/spec/myplugin/02-integration_spec.lua:11>

[----------] 0 tests from /kong-plugin/spec/myplugin/02-integration_spec.lua (4185.38 ms total)

[----------] Global test environment teardown.
[==========] 2 tests from 2 test files ran. (4976.65 ms total)
[  PASSED  ] 2 tests.
[  ERROR   ] 2 errors, listed below:
[  ERROR   ] /kong-plugin/spec/myplugin/02-integration_spec.lua @ 11: myplugin: (access) [#postgres] lazy_setup
[  ERROR   ] /kong-plugin/spec/myplugin/02-integration_spec.lua @ 11: myplugin: (access) [#off] lazy_setup

 2 ERRORS

Same issue for WSL2 + Debian after running the exact instructions from pongo's README.

duplicate of #333


Revert "Commit fetch means we can checkout fetch head"

Reverts buildkite/agent#339

Ah, sorry about this! It just needed the checkout line copied. I'll re-apply the patch and fix the problem, then test it a little more thoroughly.


Added basic filter, some TODOs

Reviewed 3 of 3 files at r1.
Review status: 2 of 3 files reviewed at latest revision, 7 unresolved discussions.

angular_scripts.js, line 93 [r1] (raw file):
I think having the .then on a newline would be more consistent here.
As an aside, I think the use of ES6 fat arrow functions will make this code a little bit easier to read, since there are so many promise functions floating around.

angular_scripts.js, line 150 [r1] (raw file):
For bonus points, run the ingestion in a worker, so that the UI always remains responsive.

angular_scripts.js, line 152 [r1] (raw file):
There are a bunch more things that we will want to do ofc; I think it makes more sense to have all of these as issues than as comments e.g.

Filter by parent/child, by test path, by multiple allowed statuses
Multiple filters combined by AND
Ability to load more than the first page of results
Ability to set how many results to see at a time
Ability to dump the full set of results as some text format for further processing

index.html, line 23 [r1] (raw file):
You are missing TIMEOUT, NOTRUN and CRASH.
(for the future, we will certainly need the ability to select more than one of these).

LovefieldService.js, line 306 [r1] (raw file):
Surely you can do something like var op = filter.negate ? "neq" : "eq"; then further down do test_runs.name[op](filter.run);. Or even var op = filter.name ? test_runs.name.neq : test_runs.name.eq;.

LovefieldService.js, line 308 [r1] (raw file):
I don't understand why you don't just return the columns you want here rather than running a second query below?

LovefieldService.js, line 313 [r1] (raw file):
So this is only going to show the results from a single run, which may or may not be right, depending on what you intended. But it is at least going to need to change in future iterations so that selecting the results from one run doesn't affect the rows from other runs.

Comments from the review on Reviewable.io

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 5 unresolved discussions.

Comments from the review on Reviewable.io

Review status: 0 of 3 files reviewed at latest revision, 6 unresolved discussions.

angular_scripts.js, line 25 [r3] (raw file):
No need to fix it in this PR, but you can remove some braces and the return statement here (and elsewhere where there's a single expression)
`(logData) => logCruncher(logData, testsFilter)

LovefieldService.js, line 320 [r3] (raw file):
test_ids.map((test) => test.test_id) ?

LovefieldService.js, line 324 [r3] (raw file):
Comment that lovefield doesn't support subqueries.

Comments from the review on Reviewable.io

Reviewed 2 of 3 files at r3, 1 of 1 files at r4.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io


How to get Controller, Action name informations?

I need make my own request Log but i can't catch the name  of controller petition
'use strict'
// const CatLog = require('cat-log')
// const log = new CatLog()
const Route = use('Route')
const Ioc = require('adonis-fold').Ioc

class LogRequest {

  static get inject() {
    return ['App/Model/LogRequest', 'Route', 'App/Model/User'];
  }

  constructor(LogRequest, Route, User) {
    this.LogRequest = LogRequest;
    this.Route = Route;
  }
  * handle(req, response, next) {
    /*  var red = Iog.on("end", function() {
          log.info("handle", response.info);// to get controller name and action name.
      })

      console.log(red)

    /* const ruta = this.Route.routes
     var req = request
     const method = request.method()
     const ip_address = request.ip()
     const url = request.originalUrl()
     const body = request.all()
     var ModelRequest = new this.LogRequest();
     ModelRequest.method = method;
     ModelRequest.ip_address = ip_address;
     ModelRequest.url = url;
     ModelRequest.body = body;
     ModelRequest.user = id
     yield ModelRequest.save()
     yield next*/
  }
}

module.exports = LogRequest

Hey @salvadorzepeda 👋
Please, for those kind of question use directly the forum instead of creating an issue (which should be used to report bug or make feature request).
https://forum.adonisjs.com/

Yup closing the issue. Please jump in the forum instead :)

@thetutlage Bro what was the result for this query?


enabling DUK_USE_DEBUGGER_SUPPORT and DUK_USE_INTERRUPT_COUNTER does not help

Hi,
I am newly trying to learn how to use Duktape debugger and I referred to the below link:
https://github.com/svaarala/duktape/blob/master/debugger/README.rst
However it is unclear to me how to enable these defines so i have added the lines in the file duktape.c like so:
#define DUK_COMPILING_DUKTAPE
#define DUK_USE_DEBUGGER_SUPPORT
#define DUK_USE_INTERRUPT_COUNTER
#define DUK_CMDLINE_DEBUGGER_SUPPORT
#include "duktape.h"
However this does not activate the debugger after following the further instructions. Please help me out here. I apologize if the answer is obvious. I am not not where to enable the required parameters. Thanks a lot!
#DuktapeDebugger

Commenting on the defines:

You shouldn't need to define DUK_COMPILING_DUKTAPE at all.
The DUK_USE_xxx defines should go into duk_config.h.
The DUK_CMDLINE_DEBUGGER_SUPPORT define is not for Duktape itself, but for the command line example examples/cmdline/duk_cmdline.c. If you're not using the command line utility, the define is not needed.

When using the command line debugger, run as duk --debugger to enable debugger integration. If you're using your own application you need to call duk_debugger_attach() and provide the necessary callbacks to enter debugger mode.

Ok cool. So now I have added the two defines (i.e changed #undef to #define ) in duk_config.h. I have run a dummy js source file with the command:
./duk -- debugger file.js
and then run the follwing command in another terminal:
cd debugger/
make  # runs 'node duk_debug.js'
But the above command gives me the following output saying that 0 files found in the parent directory, whereas my code is running from the parent directory:
"/usr/bin/nodejs" duk_debug.js --source-dirs=../
((o) Duktape debugger
Effective options:
--target-host:       <IP_ADDRESS>
--target-port:       9091
--http-port:         9092
--json-proxy-port:   9093
--json-proxy:        false
--source-dirs:       ../
--dump-debug-read:   null
--dump-debug-write:  null
--dump-debug-pretty: null
--log-messages:      false
Scanning source files: ../
Found 0 source files in 1 search directories
Connecting to <IP_ADDRESS>:9091...
Listening on *:9092
Debugger detached
As a result of this, when I open the link: http://localhost:9092/ in the browser, it shows no source files loaded. I haven't used any debugger except the GDB and Android Studio debugger so I am quite misled here.

Hmm, are you running on Windows? If so, could you change ../ to ..\ or an absolute path?
The debug client is expected to have access to the source files being debugged; the debug target doesn't provide source text at present.

Windows recognizes forward slashes in paths just fine.  I should know; miniSphere's sandbox implementation depends on it. :)

svaarala, I am running this on Ubuntu. So may be the path is not the issue. The source file is present int the ../ path itself.

@Wodehouse211 Hmm, seems that the source code scan has bit rotted at some point - but if you click Attach and start the debug session itself the source code is correctly loaded. I'll fix that source code scan issue.

I am unable to start debug session by clicking attach. Let me please list out the steps I'm following, in case I'm doing something wrong.

From duktape directory, which is parent directory to debugger folder, I run my JS source file like so:
./duk --debugger trial.js
(trial.js is a simple js file with instructions and an infinite loop, so that the code runs while I am                                                                    attaching debugger)
While the JS code runs, I enter the debugger folder and run the following command:
make  # runs 'node duk_debug.js'
Whose output is no source files found.
I open the browser using the following URL:
http://localhost:9092/
However, I still am getting no source file loaded, and there is no option for choosing a source file. I have attached the screenshot of the URL page herewith, for better clarity.

Thanks

Does the "duk" command respect the --debugger option and enter debug mode (it should print out info indicating it's waiting for a debug client connection)? If not, you might be missing DUK_CMDLINE_DEBUGGER_SUPPORT from the "duk" command compilation.

I just found out that there is indeed no debugger support. The command line is ignoring the --debugger option. I do not know what to change in Makefile.dukdebug. It would be great if you could walk me through it in more detail. How to enable the DUK_CMDLINE_DEBUGGER_SUPPORT. What are the steps to be followed after that.

When you compile duk_cmdline.c just make sure -DDUK_CMDLINE_DEBUGGER_SUPPORT is given to the compiler. You shouldn't need to change anything in Makefile.dukdebug if you're using that to build the 'duk' command, it should be enough to just say 'rm duk; make -f Makefile.dukdebug' and then run './duk --debugger'.

Please take a look at the makefile contents :

Duktape command line tool with debugger support.

DUKTAPE_SOURCES = src/duktape.c
Windows (MinGW): use examples/debug-trans-socket/duk_trans_socket_windows.c
and link with -lws2_32.
DUKTAPE_CMDLINE_SOURCES =
examples/cmdline/duk_cmdline.c
examples/debug-trans-socket/duk_trans_socket_unix.c
CC      = gcc
CCOPTS  = -Os -pedantic -std=c99 -Wall -fstrict-aliasing -fomit-frame-pointer
CCOPTS += -I./prep -I./examples/debug-trans-socket
CCOPTS += -DDUK_CMDLINE_DEBUGGER_SUPPORT     # enable --debugger in ./duk
CCLIBS  = -lm
Use tools/configure.py to prepare Duktape config header and sources with
custom configuration.
duk:    $(DUKTAPE_CMDLINE_SOURCES)
@rm -rf prep
python2 tools/configure.py
--source-directory src-input
--output-directory prep
--config-metadata config
-DDUK_USE_DEBUGGER_SUPPORT
-DDUK_USE_INTERRUPT_COUNTER
-DDUK_USE_DEBUGGER_DUMPHEAP
-DDUK_USE_DEBUGGER_INSPECT
$(CC) -o $@ $(DEFINES) $(CCOPTS) $(DUKTAPE_SOURCES) $(DUKTAPE_CMDLINE_SOURCES) $(CCLIBS)
It already compiles duk_cmdline.c file with the -DDUK_CMDLINE_DEBUGGER_SUPPORT option. But it does not recognize the debugger still. (I did not have to add any changes to the makefile to compile duk_cmdline.c file).

I don't know what could go wrong unfortunately. Here's what happens for me (from master):
duktape@keppihevonen:~/duktape/dist$ make -f Makefile.dukdebug
python2 tools/configure.py \
	--source-directory src-input \
	--output-directory prep \
	--config-metadata config \
	-DDUK_USE_DEBUGGER_SUPPORT \
	-DDUK_USE_INTERRUPT_COUNTER \
	-DDUK_USE_DEBUGGER_DUMPHEAP \
	-DDUK_USE_DEBUGGER_INSPECT
configure.py          INFO    Configuring Duktape version 2.1.99, commit<PHONE_NUMBER>ca17e5ea196130b4f751673edebf21, describe v2.1.0-225-g32609632, branch shared-evalcall-call-handling
configure.py          INFO      - source input directory: /home/duktape/duktape/dist/src-input
configure.py          INFO      - license file: /home/duktape/duktape/dist/LICENSE.txt
configure.py          INFO      - authors file: /home/duktape/duktape/dist/AUTHORS.rst
configure.py          INFO      - config metadata directory: /home/duktape/duktape/dist/config
configure.py          INFO      - output directory: /home/duktape/duktape/dist/prep
genconfig.py          INFO    Creating duk_config.h: platform=any, architecture=any, compiler=any
genconfig.py          WARNING Recommended config option DUK_USE_FATAL_HANDLER not provided
genbuiltins.py        INFO    Creating built-in initialization data: ram built-in support
genbuiltins.py        INFO    Removed 1 objects (0 disabled, 1 not needed by config), 7 properties (0 disabled, 7 not needed by config)
genbuiltins.py        INFO    Removed 1 objects (0 disabled, 1 not needed by config), 7 properties (0 disabled, 7 not needed by config)
combine_src.py        INFO    Combined 91 source files, 3475686 bytes written to /home/duktape/duktape/dist/prep/duktape.c
gcc -o duk  -Os -pedantic -std=c99 -Wall -fstrict-aliasing -fomit-frame-pointer -I./prep -I./examples/debug-trans-socket -DDUK_CMDLINE_DEBUGGER_SUPPORT      prep/duktape.c examples/cmdline/duk_cmdline.c examples/debug-trans-socket/duk_trans_socket_unix.c -lm
[...]
duktape@keppihevonen:~/duktape/dist$ ./duk --debugger
Debugger enabled, create socket and wait for connection
Waiting for debug connection on port 9091

@Wodehouse211 Did you manage to figure out the cause?


Update index.md

Data intensive

[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.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Program efficiency is an important thing to know.


Are there any plans for a TypeScript Programmatic Visual Web Components Library (and RAD)?

Are there any plans by Microsoft to spin off some side project concerning the definition of programmatic visual components strictly based on Typescript?
The reason of this question is that, even if Web Libraries and Frameworks abound, they basically either have severe flaws or steep learning curves and unnecessary complex systems that have to cope with either supporting HTML-CSS definition of objects or support of non-TS languages.
And what about a RAD?
It is funny (and really counterproductive) that today’s development of visual interfaces lacks tools like Delphi or Visual Basic that - in the '90s(!) - were orders of magnitude more productive than the bunch of campy tools that badly glue XML/HTML/CSS/JS now.
Having Microsoft behind a visual components/polyfills open tool could make the difference and set a new standard for (at least enterprise) development.
Just like TypeScript fixed inner-page and server Javascript development now it’s time to fix the front-end.
Thank you for your time and your wonderful project.
– R

Angular 2 and Dojo 2 are both being built on TypeScript and other major frameworks are considering migrating too.
The design goals for TypeScript really preclude it from being anything more than a language.
This issue forum is for suspected bugs and enhancement to TypeScript and general discussion should take place in other forums.

Hi @kitsonk and thank you for your prompt involvment.

Angular 2 and Dojo 2 are both being built on TypeScript and other major frameworks are considering migrating too.

You mention two libraries:

one is still vaporware
the other is a perfect example those campy non-programmatic tools I was talking to

The design goals for TypeScript really preclude it from being anything more than a language.

I don'think so, besides that, I clearly asked if Microsoft is considering a side project
It is my opinion that only projects strongly and clearly backed by large components can emerge as enterprise solutions.
The last 10+ years web history is littered with undead corpses of nice frameworks that had no userbase traction (name your favourites here) or were abandoned by the company that created them (Tibco GI,YUI)
Anyway, I think that the question could be of interest for more persons.
To admins: Feel free to mark this ish as "Inappropriate" and close it, if you so wish.
My bests.
--R
Oh, btw, Kitson,I see that you're involved in Dojo2 and I wish you best luck, since I used Dojo in several projects and it was one of the best frameworks by the time. Documentation apart.

That question is not related to Typescript itself, if you wish to ask if Microsoft want to do something, based on Typescript or whatever, may be you should ask from Microsoft, but not from Typescript (or whatever) project?
I understand it is related to Typescript, but does not look like appropriate place to keep. There is already 1200+ issues opened, high chance that will just sit here increasing the noise.

Great, @Karabur,
do you know where?
BTW: I still think that it could loosely belong here, since it's an obvious enhancement/extension.
--R

Oh, btw, Kitson,I see that you're involved in Dojo2

Not only involved in said vaporware but the project lead.

@kitsonk I knew and since this OT I will bug you there.

TypeScript is JavaScript; the JavaScript echo system provides a whole set of tools and frameworks that support UI development. TypeScript should work with all these frameworks. Building and end-to-end framework or development tool chain is one of the non-goals of the TypeScript projects (see https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals#non-goals).
So to answer your question, we have no intentions to build a UI framework or a templating language based on TypeScript.

So to answer your question, we have no intentions to build a UI framework or a templating language based on TypeScript.

Thanks for the clear and definite answer, @mhegazy .
I can hear sighs of relief from all companies implementing current UI frameworks.
--R


chore(CSharp): add character limit

PR Checklist:

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is on refer on the language README.md file
[x] My addition does not have a spelling problem
[x] My submission has a proper and user-friendly description of the algorithm
[x] My submission has the time complexity of the algorithm
[ ] My submission has sample input-output of the program (NOT FOR PYTHON)

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR
Character_Limit allows a user to enter a string and determine how many characters in that string will be shown before it continues with periods. For example, entering in "Hello" and limiting the character limit to 2 will out put "He..."

Other information:

Quick question. In regards to time complexity. Is this something that needs to be added in the code (which gives an output in ms) or description (linear time)?

@Waqar-107 Ok so I fixed the changes, but it appears it failed a test. I tried looking through this, but could not figure this out. Apologies as I am new...

@Waqar-107 Ok so I fixed the changes, but it appears it failed a test. I tried looking through this, but could not figure this out. Apologies as I am new...

@maty714 no worries, looking into it.

@ming-tsai according to my understanding, codespell detects common spelling mistakes in the code. Here it has considered Hel as misspelled but it is a part of the test case. Any idea how to make it avoid checking testcases?

@ming-tsai according to my understanding, codespell detects common spelling mistakes in the code. Here it has considered Hel as misspelled but it is a part of the test case. Any idea how to make it avoid checking testcases?

I will check it out.

@ming-tsai Just committed the suggestions. Third time is a charm!


Example/docs for using as a library

Add some more docs and a godoc example for https://github.com/heptiolabs/kubernetes-aws-authenticator/blob/master/pkg/token/token.go.
cc @gtaylor

Hello, this would help us as we would like to use a lambda at the end of a codePipeline to deploy applications to an existing EKS cluster, similar to #96

See sample code in issue #133


{Items} Blink Dagger Upgrade Dump

This is just a dump of all the blink dagger upgrade suggestions I've seen, just to keep it all in one place
A- A delay on the blink dagger that allows you to blink to a location after a small-medium delay
B- A double dagger that allows you to blink back to your original location in case things go wrong
C- A Dagger that stuns on blink, in a small AoE, also stuns yourself
D- A Dagger combined with force staff when used on a target you force staff them, but use it on a location and you blink
E- A Dagger that teleports all people in an AoE to a location, has smaller range, can't tp creeps
F- A Dagger that has smaller range and shorter cool downs and has 3 charges
G- Side grade/replacement that banishes; when it spawns the target it will teleport them to a random place in the AoE
H- Instead of blinking to a location within a small distance channel, for a small time and blink a large gap, this can be used while being attacked, but any CC will interrupt this
Credit Section: @Baumi @zelding @WarpDragon @Katrix @chrisinajar and probably some others, but it's late at night so i'll give the rest later

you read #196 ? anyway, about E, i sugest instead of blinking aoe create a "portal" that can be entered by allays to also go in to location. that remove trolling potential of item. portal can be only one way or both ways. it depends

Jump dagger, Throw dagger are things.  Cross them out?

Blink Hammer

Recipe, blink dagger plus basher (or abbysal blade if you want)
Ability, after blinking stun enemy around for x second (0,75s should be ok with radius 350, with abbysal in recepe ofc should be more powerful)

Arcane dagger

Ability, after blinking next ability used have shorter cooldown and needs less mana if it was casted in x seconds of blink.

Flame dagger. [someone took knife to a flamethrower fight]

Ability, after blink put in flames path traveled, deal damage per second (damage dealing similar to meatball)

Acid dagger. [Maybe look like cheese but i bet it not taste like one]

Ability, after blink evry enemy unit that was on path is poisoned, poison deal dmg over time and resources armor.

Frozen dagger. [be careful, it's cold]

Ability, after blinking create ice path on traveled path(?) (work like invoker ice path but this version is long and narrow instead of short and wide)

Earth Dagger. [yep, still elemental family,youngest child but hit like a grandpa]

Ability, after blink create wall on path, enemies hited by wall are stunned (work like es wall)

Heel Dagger [Worst nightmare of Achilles]

Recipe, dagger plus medalion or his upgrade.
Ability, after blinking aply debuff on caster and surrounding enemies.(debuff of medaliin or his update, or creative variation)

Time dagger [i rly wanted to finish in this one, i promise i wanted end on 13 ]

Ability, if targeted hero work like glimpse, if not work normally

Blink Shield

Recipe, blink dagger plus vanguard (could be also other shields)
Ability, after blinking create shield around hero that block all damage,lasts 7 seconds or until destroy, hp of shield is 5% of wielder hp, have no reductions.

SOME MORE!
Shield Dagger: On blink deal  a small AoE of damage and gain that damage as a Shield that decays over 10 seconds
Illusion Dagger: After blink, across the path that was blinked from, created an illusion every 100 units.
Dagger of Blight: Double range, on blink get -34% armour and spell resistance
Dagger of Fright: On blink, walk in a random carnal direction for 2 seconds, 2/3 cooldown of normal dagger
Reverse reggaD: Instead of blinking, teleport to where you were 5 seconds ago
Dagger of Smite: Cast a lightning bolt where you blink to, and teleport back to your original position after 3 seconds, when teleporting cast lightning bolt on all heroes within 300 units of both places.

For Wu's:
1 is pretty scary. Interesting for interrupting channels, but I would hesitate to make it more than a ministun
2 is okay, I guess. Gotta be careful with CDR though.
3 and 4 are similar.
5 and 6 may be too strong as CC. Will need to be careful if we want this.
9 is... eh. I would like it better if the shield HP was fixed.
The ones I didn't mention are ok
For Vafnar's update:
Illusion dagger sounds like PL cancer. I don't like it.
Fright sounds like bad design, with the randomness.
Dagger of Smite is also weird, in that it's more of a nuke item than a positioning one, and the 3s stay is also quite confusing.
I like the other two.


Include intercepted canvas attempts in the site summary

Summary

Canvas fingerprinting protection has recently been added to this extension, and if I understand correctly, this intercepts attempts to use Canvas APIs like getImageData. What I really like about this extension is that it has a summary of all the trackers it has blocked on a site, but I see nothing in the summary indicating that Canvas APIs have been intercepted. That means that it looks like the extension has made no changes to the website, but really it has.
Motivation

I recently noticed a problem with text-rendering in Phaser that turned out to be because Phaser reads Canvas APIs to determine the size of text before it positions it, and this extension was causing those APIs to return incorrect data. It was harder to diagnose because the extension didn't report that it was doing anything on the site.
This would also help diagnose other issues that are caused by this interception, such as the ones with Konva.js.
Additional context

Priority: This feature isn't critical itself, but I feel that being able to fix issues caused by the fingerprint protection code is critical, and this is one way of helping catch and fix those issues.
Impact: Anyone who is trying to use sites that legitimately manipulate canvas could potentially benefit from knowing that this extension is interfering with those attempts.

Thanks for the detailed description, I think that's a good idea to expose that fingerprint resistance is enabled. I'll talk with our UX folk and see if there's anything we can do here.
The issue highlights the same in Brave and Tor which makes a lot of sense, perhaps we could surface when a site is doing this using the badging api from extensions perhaps.

@jonathanKingston
I just wanted to mention another use case to consider for the UX/UI. My company makes a precision medical annotation tool. Users paint areas of the canvas to annotate clinically-relevant features of the medical image. In our case, it's important that annotations include only specified RGB values.
This extension adds a seemingly random number of pixels that add 1 value to each RGB channel. I included screenshots showing a summary of the RGBA values on the canvas after the same 3 annotations with and without the extension. I didn't know about canvas fingerprinting but as I learned about it I understood why you'd want to mitigate that privacy risk. However, it might help to include a tooltip or something that informs the user about this feature and enables them to disable it (temporarily or permanently) or whitelist that particular site if canvas pixel accuracy is important for their use case. Another option could be to overlay an actionable button with half-opacity in the corner of every canvas. When the user hovers, it can give details about the canvas fingerprinting protection, when that protection could impact work, an option to turn it off when needed, and maybe an option to never show that button forever or for X days. I imagine people are likely to hide the button without reading the description, and then they wouldn't know what's causing precision canvas issues. Did you have a chance to consult with the UX/UI people yet?
I realize this sounds like a bit of an edge case, but troubleshooting it was quite difficult because no one on our team knew that an extension could/would alter canvas data, so we it wasn't one of the first things we asked. From now on, we'll ask for a list of installed extensions at the start of troubleshooting, but I wonder how many other precision canvas use cases are silently impacted by this feature.

Stock Chrome
DuckDuckGo extension

We do already allowlist certain sites due to breakage when they reach a certain level of severity. Do you have anything I can investigate @drecali in terms of URLs of the scripts with this issue? (jkingston [@] duckduckgo.com if you need this to be private)

Additionally for certain APIs calls we allowlist the usage and provide a path through the code that ignores the protection; it may be for your code we could do the same if there's only these small number of colours needed.

Largely the values that differ between rendering engines are where anti-aliasing provides different values of artefacts rendered, if you're only ever seeing fixed values it should be safe to also disable protections.

As you can see from the return values we only modify pixels by one bit on each channel this may however change overtime; however for now these should all correlate to the same fixed value.

I think we would prefer not to complicate the user with exposing details of our implementation (our motto is 'privacy simplified') however we could consider adding a console warning for the first modification of canvas data on the page to assist developers looking into the issue.


What castlemacs shouldn't do?

What kind of feature requests are you looking for? Language specific features, tools, bug fixes or something else?
I am asking this because castlemacs is minimalistic.

Hi,

bug fixes
usability and UI improvements
language specific features, but not going too far into the IDE land. Basically, Castlemacs should eventually support whatever Sublime Code supports out of the box: basic modes for popular languages and frameworks, linting, some sort of dumb-jumping, etc. I'd like to draw comparisons with VS Code, but it gradually becomes way to bloated IMO.


Issues with docker exec error handling

On Docker:
$ docker -H $DOCKER create busybox
<container_id>
$ docker -H $DOCKER exec <container_id> ls
FATA[0000] Error response from daemon: Container <container_id> is not running

On Swarm:
$ docker -H $SWARM create busybox
<container_id>
$ docker -H $SWARM exec <container_id> ls
FATA[0000] Error response from daemon: invalid character 'C' looking for beginning of value

We are probably not checking the HTTP error code somewhere

/cc @vieux

Fixed by @jimmyxian

which release include such fix ? Could tell me how to find that ?
Thanks

06/16/2015 - Release 0.3
It has already fixed in master


"download zip" on tutorial page links to "download zip" image

on the page https://github.com/WorldFamousElectronics/PulseSensor_Amped_Arduino, there is an instruction:

Download ZIP on this page:  Download Zip

the "Download Zip" button links to the image for the button, not a zip file.

Hi kaeverens,
I just visited the repo, and the Download Zip link from the "Clone or Download" option does download on my computer lickety split. What kind of computer are you using? Do you have limitations on what you can download?
If you continue to have trouble, contact the nice folks at github, since it's their site and all.
Joel

I'm using Chrome on Linux, but that doesn't matter in this case.
the problem is that the HTML of the page literally links to an image, and not a zip.
Here is a screenshot explaining visually.

Oh, I see the problem! You are looking at our readme. That is an image of the button in the github page above. Scroll up in the browser window, and you will see the green button "Clone or Download" Click that, and you will see the option to clone the repo on your machine, or download the zip file.
Best,
Joel

I understand that. But the README doesn't say that. It implies heavily that the way to download the zip is to click the Download Zip image. It says nothing about scrolling up, etc.
anyway... you get the problem now


Update Chinese Traditional

While your at it, brb.gui.pin.add and brb.gui.pin.remove has been updated to include "%s" in place of "R"

Fixed


nextcloud-client: Revert "nextcloud-client: remove inkscape from runtime closure"

Description of changes
This reverts commit 1f70a0a9e07be3e2dde872f700e4ede82c98c2ab, which causes nextcloud-client to not launch anymore.
@SuperSandro2000

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set 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/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I'll investigate this more later.

causes nextcloud-client to not launch anymore.

Both work for me but if we remove inkscape we don't need the workaround anyway.


[BUG] Requested content ".css" but built .sass.

Bug Report Quick Checklist

[x] I am on the latest version of Snowpack & all plugins.
[x] I use package manager yarn
[x] I run Snowpack on OS Linux
[x] I run Snowpack on Node.js v14.15.3

Describe the bug
My snowpack build is failing, there is a problem with react-refresh and sass plugin interfering.
To Reproduce
We can't fix bugs that we can't see for ourselves. Issues often need to be closed if this section is skipped.

npm init snowpack-app --template @snowpack/app-template-react
add sass plugin
import a sass file with only variables (this will not produce a css file)
snowpack build
See error!

[08:15:55] [snowpack] BUILD: /_dist_/styles/variables.css
[08:15:55] [@snowpack/plugin-sass] load() starting… [src/styles/variables.sass]
[08:15:55] [@snowpack/plugin-sass] ✔ load() success [src/styles/variables.sass]
[08:15:55] [@snowpack/plugin-react-refresh] transform() starting… [src/styles/variables.sass]
[08:15:55] [@snowpack/plugin-react-refresh] ✔ transform() success [src/styles/variables.sass]
[08:15:55] [snowpack] Build Result Error: There was a problem with a file build result.
[08:15:55] [snowpack] /workspace/fantomas-tools/src/client/src/styles/variables.sass - Requested content ".css" but built .sass.
[08:15:55] [snowpack] Error: /workspace/fantomas-tools/src/client/src/styles/variables.sass - Requested content ".css" but built .sass.
    at FileBuilder.verifyRequestFromBuild (/workspace/fantomas-tools/src/client/node_modules/snowpack/lib/index.js:112530:19)
    at FileBuilder.getResult (/workspace/fantomas-tools/src/client/node_modules/snowpack/lib/index.js:112742:42)
    at Object.loadUrl (/workspace/fantomas-tools/src/client/node_modules/snowpack/lib/index.js:131558:51)
    at async flushFileQueue (/workspace/fantomas-tools/src/client/node_modules/snowpack/lib/index.js:131966:28)
    at async build (/workspace/fantomas-tools/src/client/node_modules/snowpack/lib/index.js:131992:5)
    at async Object.command (/workspace/fantomas-tools/src/client/node_modules/snowpack/lib/index.js:132080:9)
    at async cli (/workspace/fantomas-tools/src/client/node_modules/snowpack/lib/index.js:132389:9)

Variables.sass looks like
$dark: #211426
$primary: #22A7F0
$secondary: #5fcde3
$danger: #E01D31
$warning: #D69D36
$success: #66D4AC
$white: #FFF

Expected behavior
A clear and concise description of what you expected to happen.
Anything else?
A workaround is to add some sass code that will produce css.
$dark: #211426
$primary: #22A7F0
$secondary: #5fcde3
$danger: #E01D31
$warning: #D69D36
$success: #66D4AC
$white: #FFF

// workaround for snowpack issue
blink
    font-weight: bolder

According to @snowpack/plugin-sass’ README, you have to isntall the plugin and add it to your Snowpack config to enable it, like so:
- plugins: ['@snowpack/plugin-react-refresh', '@snowpack/plugin-dotenv'],
+ plugins: ['@snowpack/plugin-react-refresh', '@snowpack/plugin-dotenv', '@snowpack/plugin-sass'],

If I do this, I’m able to load .sass files just fine.
Let me know if I missed your issue, or if there’s something else that’s causing problems!

Edit: ah, sorry—I missed the “only variables” part. You’re right that does result in an error.
I’m not sure, though, if this is an error on Snowpack’s fault? In Sass, what is an empty file supposed to produce? I believe the intended effect is to @use or @import within Sass to import these variables, right? I believe that is still working as expected for Snowpack, but let me know if there’s a scenario where you want an empty .css file in the build output.

There is no scenario where I explicitly want that empty file.
I import a file that only contains variables.
https://github.com/fsprojects/fantomas-tools/blob/f51c04dc93cf095f9b363d42a2e9f4ab9a913cab/src/client/src/styles/fantomas.sass#L1
And that leads to problems with snowpack.

Yes, I can confirm. The problem seems to be resolved.


[DNM ] 📖  Document code-cell directive and cell tag functionality

I noticed that there's no documentation of the {code-cell} directive for executing content within markdown files. From looking at the code it sounds like this is still an alpha-level feature, but I thought it'd be helpful to document it since the functionality is technically there, even though it still has a ways to go.
This also adds some documentation for the supported tags to control cell behavior. While I was documenting that, I also uncovered this bug:

#1112

Hold off a sec on this one, I didn't realize that {eval} was already supported. I'm going to document that quickly so that we can close

https://github.com/executablebooks/mystmd/issues/1109

OK I think this one is ready to go now. Requesting a review/merge from @agoose77 since this touches on some of the eval and execution work you did

Also just noting that I don't necessarily want to turn @agoose77 into a bottleneck for merging, if @rowanc1 has the info to know that our {eval} description is correct, then I'd say just go for it. I just pinged @agoose77 since I know he worked on it, but my general modus operandi is bias towards action unless explicitly stated otherwise :-D


String generated by file.readline() gives list options when using tab-complete

Description

What steps will reproduce the problem?

Open new file in Spyder.
Write a line to open a text file: my_file = open("path/text.txt", "r")
Read first line of file with: first_line = my_file.readline()
Search through string methods by: first_line. hit tab button here

What is the expected output? What do you see instead?

A drop-down menu should appear including options such as:
capitalize
center
count
decode
...
Instead the menu shows:
append
count
extend
index
...

Please provide any additional information below
Basically, the menu would make it appear as if the variable "first_line" is a list instead of a string. Here are a few things that I've tried so far:

I've tested this on three computers; all show the same result.
Other strings will still tab complete to their methods properly in the same script.
If I run the exact same lines in the IPython console, the tab completes properly.
Executing a string method on "first_line" (i.e. print first_line.capitalize) from the file runs without producing any errors.
I updated everthing via "conda update conda" and "conda update anaconda".
The image I've attached shows the menu when produced from a file, and when produced from the IPython console (top and bottom respectively).

Version and main components

Spyder Version:  2.3.4
Python Version:  2.7.8
Qt Version    :  4.8.6, PyQt4 (API v2) 4.10.4 on Windows

Optional dependencies
pyflakes >=0.5.0:  0.8.1 (OK)
pep8 >=0.6      :  1.6.2 (OK)
IPython >=1.0   :  3.0.0 (OK)
zmq >=2.1.11    :  14.5.0 (OK)
pygments >=1.6  :  2.0.2 (OK)
pandas >=0.13.1 :  0.15.2 (OK)
sphinx >=0.6.6  :  1.2.3 (OK)
rope >=0.9.2    :  0.9.4 (OK)
jedi >=0.8.1    :  0.8.1 (OK)
matplotlib >=1.0:  1.4.3 (OK)
sympy >=0.7.3   :  0.7.6 (OK)
pylint >=0.25   :  None (NOK)

@blink1073, could you take a look at this one?

This looks like a case where Rope is wrong but doesn't know it.  I don't know that we can prevent that from happening.

Apart from giving priority to jedi, which brings other inconsistencies ?

Right, we just need an AI on top of both, no problem...

so, wont'fix then?

I guess we could report the bug to rope ?

Or maybe we should defer to jedi on completions and rope for docs?
—
Sent from Mailbox
On Wed, Jun 10, 2015 at 1:20 PM, Joseph Martinot-Lagarde
<EMAIL_ADDRESS>wrote:

I guess we could report the bug to rope ?
Reply to this email directly or view it on GitHub:
https://github.com/spyder-ide/spyder/issues/2474#issuecomment-110863090


Convert Enum Casing during translation.

enum Color { Red, Green, Blue, LightBlue};

in dart it should be
enum Color { RED, GREEN, BLUE, LIGHT_BLUE }

Because this change will break the API for our  customers, we should do this soon.

Turns out I was wrong No action needed: https://www.dartlang.org/articles/style-guide/

Shouldn't they be lowerCamelCase in Dart - red, lightBlue  ?

@vicb Dart seems to be inconsistent, we no strong preference. I have discussed this with @yjbanov and we decided that PascalCase is fine. We can't have it both ways without significant changes to ts2dart.

@mhevery Dart style guide is pretty clear that constant names should be lowerCamelCase. PascalCase would be fine in the style guide recommended so. ts2dart already supports type-based symbol rewriting. It shouldn't be a significant change to ts2dart. Reopening.

Updated the issue description.

Are you really sure it's a good idea to rename enums, for usability reasons? I'd expect that to cause more confusion than to do good.
Outside of that, the Angular code base is not completely well-typed, i.e. it doesn't pass noImplicitAny. That means we'd have to outlaw any property name that could also be an enum name, so this seems difficult at this point.


Show warning for users of 2024.1 with proxy servers

This PR displays a message about broken proxy support for users

using 2024.1.x
with an enabled HTTP proxy server
which did not click "Don't show again" when the same message was displayed earlier

"Don't show again" deactivates the message for all projects.

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

v0.68.0
GitHub release

Your semantic-release bot :package::rocket:


Set Buffer to MySQL BLOB field

function updateFile(id, file) {
  // file - <Buffer 01 ac 02 bc 52 ec 39 ... >
  squel.update().table('test').set('file', file).where('id = ?', id);
}

Returns:

field value must be a string, number, boolean, null or one of the registered custom value types

I'm not sure how Blob data is to be passed to the MySQL but in any case you can use a custom value handler for this, see https://hiddentao.com/squel/#custom_formatting

BLOB data doesn't require transformation to string in MySQL driver
http://stackoverflow.com/questions/25951251/nodejs-mysql-insert-blob

squel.registerValueHandler(Buffer, buffer => buffer);
Its must be by default

@Smert Sorry, don't understand your comment. Please clarify.

Add this line somewhere in your project. This will convert all ``Buffer` instances to hex code.

squel.registerValueHandler(Buffer, buffer => '0x'+buffer.toString('hex'));

@SeregPie It will be work fine. But toString() is unnecessary conversion of type. mysql driver could work with Buffer type directly


DBZ-6190: Fix support for ddl filter

@jpechane @Naros I see the DB2 test fails with the same error in other PRs... Is it known to be flaky? If so, can you please re-run it?

@nirolevy Applied, thanks!


Python3

I've made some changes so that the tests pass on Python 3. Some of the changes are just to fix things that are breaking, so comments on the actual intents of the tests are welcome. In fact, any comments are welcome.

Coverage increased (+0.05%) to 88.124% when pulling d3ce0e8b8fa6d9161f185df4178eccc24e624bbb on python3 into 6b5bc844412563484517f2a7d69e9edc7721e6dd on master.

Someone (me or @MJGaughran) needs to run and fix the system tests before this is merged.

It looks like we can't easily support Python 3 on RHEL6 because of difficulties installing python-ldap, but it's not really worth solving a problem that will go away by itself. Thanks @skyfrench for figuring this out.

Closed in favour of #78.


warning emitted: CGAffineTransformInvert: singular matrix

I get following warning when pushing or popping from NavigationStack
 [90654:2639075] [Unknown process name] CGAffineTransformInvert: singular matrix.
Am I doing something wrong here:
        PushView(destination:SettingsView()) {
          VStack {
            Image(systemName: "gear")
              .resizable()
              .scaledToFit()
              .clipShape(Rectangle())
              .shadow(color: .primary, radius: 5)
              .padding([.horizontal, .top], 7)
            Text("Settings").lineLimit(1)
          }
          .frame(minWidth: 50, maxWidth:100, alignment: .center)
        }

          PopView {
            Text("<-")
          }

Hi @lingolab2, sorry for the late response. I tried your code in a minimum viable example (shown below) and I didn't get any warning from xCode (with xCode v11.5):
import SwiftUI
import NavigationStack

struct Root: View {
    var body: some View {
        NavigationStackView {
            ZStack {
                Color.green.edgesIgnoringSafeArea(.all)
                PushView(destination:ChildView()) {
                    VStack {
                        Image(systemName: "gear")
                            .resizable()
                            .scaledToFit()
                            .clipShape(Rectangle())
                            .shadow(color: .primary, radius: 5)
                            .padding([.horizontal, .top], 7)
                        Text("Settings").lineLimit(1)
                    }
                    .frame(minWidth: 50, maxWidth:100, alignment: .center)
                }
            }
        }
    }
}

struct ChildView: View {
    var body: some View {
        ZStack {
            Color.yellow.edgesIgnoringSafeArea(.all)
            PopView {
                Text("<-")
            }
        }
    }
}

struct Transition_Previews: PreviewProvider {
    static var previews: some View {
        Root()
    }
}

You can copy paste my example and everything should be fine. Probably your issue doesn't strictly depend on the code you showed me. If you can show me more code (which still generates the problem) I'll try to help you. Thank you.

excellent, i’ll search in my code, sorry for the trouble. please close ticket.

On 2 Jul 2020, at 19:13, Matteo<EMAIL_ADDRESS>wrote:
Hi @lingolab2 https://github.com/lingolab2, sorry for the late response. I tried your code in a minimum viable example (shown below) and I didn't get any warning from xCode (with xCode v11.5):
import SwiftUI
import NavigationStack
struct Root: View {
var body: some View {
NavigationStackView {
ZStack {
Color.green.edgesIgnoringSafeArea(.all)
PushView(destination:ChildView()) {
VStack {
Image(systemName: "gear")
.resizable()
.scaledToFit()
.clipShape(Rectangle())
.shadow(color: .primary, radius: 5)
.padding([.horizontal, .top], 7)
Text("Settings").lineLimit(1)
}
.frame(minWidth: 50, maxWidth:100, alignment: .center)
}
}
}
}
}
struct ChildView: View {
var body: some View {
ZStack {
Color.yellow.edgesIgnoringSafeArea(.all)
PopView {
Text("<-")
}
}
}
}
struct Transition_Previews: PreviewProvider {
static var previews: some View {
Root()
}
}
You can copy paste my example and everything should be fine. Probably your issue doesn't strictly depend on the code you showed me. If you can show me more code (which still generates the problem) I'll try to help you. Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/biobeats/swiftui-navigation-stack/issues/22#issuecomment-653013659, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHBLCK5GKP2SS4YNVP5HYNTRZSFIFANCNFSM4OJGPKKA.

excellent, i’ll search in my code, sorry for the trouble. please close ticket.
…

Hi @lingolab2 take a look at #24, it might help you.


Request: ensure director verbose mentions if it created a new directory

It would be nice if the verbose mode actually said something like
Ensuring directory ('...') status: existing
Ensuring directory ('...') status: creating
Maybe have a second verbose level if you want to maintain the original way.

It actually does do this.
If the directory doesn't exist it says: print('Ensuring new directory ({!r})'.format(dpath)).
If the directory does exist it says: print('Ensuring existing directory ({!r})'.format(dpath)).
but perhaps that's not clear. I'll change it to:
            print('Ensuring directory (create {!r})'.format(dpath))
            print('Ensuring directory (exists {!r})'.format(dpath))

This is fixed by #64


annotations - allow for pointer events to be controlled on the slotted element

Fixes #1019

defers control of pointer events to slotted elements, similar to opacity

LGTM 👍 thanks for catching this and contributing a fix!


Add more features to Talk - tag, star, etc

The title says it all, and the file diffs too!
I think this will be an awesome addition to this extremely valuable package.

@nahid Do you mind if Travis build or equivalent is setup for this repo?

I erroneously proliferated features in this PR in several places, PR #135 and PR #131.
This PR consolidates the suggestions in comments in those PRs (all now closed in favour of this PR), as well as other code additions and improvements.
@nahid and @cfpinto I apologize for the delay in putting this right. I believe we are all good to merge.
Thanks

@nafiesl @nahid @cfpinto Please I need your opinion: because some of the additions I made adds fundamentally different behavior to Talk (e.g. the notifications feature), is it not advisable that merging this PR should necessitate bumping of Talk to the next major version?

hi @damms005 I am not sure what to review here.

the additions I made add fundamentally different behavior to Talk

:point_up_2: are those behaviour changes already discussed with the project maintainer?

Add more features to Talk - tag, star, etc

Regarding the PR title, I am suggesting you create different PR of each feature you contribute. So the project maintainer can easily track the changes as it needed.

@nafies He's already aware of some of the changes. I simply moved everything to a single PR so it can be discussed wholistically.

Regarding the PR title, I am suggesting you create different PR of each feature you contribute. So the project maintainer can easily track the changes as it needed.

I think it is wrong for me to call it "features" in this PR title, because it is just a single "feature": the Tag feature. This is the main feature in this PR.
So while working on this tag feature, I did some refactoring to make it easy to work with Talk. I then built on this new Tag feature to give an example of how it can be used (hence the "Star"-ing of conversation was included, system notification example, etc).
All the changes I made are all about the same single feature: Tag.
The other one is being able to add "Title" to a conversation, which was already discussed in PR#131.

@nafiesl @imanghafoori1 Support now added for up to Laravel v8

@nahid @nafiesl It's been a while this issue is opened. I hope I can convince you to merge it; else we should rather close it. I want us to agree on a tradeoff and have a midpoint to resolve this.
It was my mistake and big oversight to not have made my changes modular and opened smaller PRs, rather than this large one. I sincerely do not have the bandwidth and resources to reword this to correct this mistake.
However, Talk already has extensive and significant test coverage. If I add tests that cover the features in this PR and update the README as necessary, will this be enough to get this PR merged?

I'll let you know after checking


issue3100 from connectapp Radio group option style breaks when there …

…is very long text for the radio group option
PR for https://github.com/appirio-tech/connect-app/issues/3100
@maxceem

This is what we want? @maxceem

The radio will always at first line no matter how many lines for the label?

@maxceem done. Thanks.

Sorry, for the late reply,

This is what we want? @maxceem

yes

The radio will always at first line no matter how many lines for the label?

yes
Will check out the new PR.

@vikasrohit I think this PR can be merged independently without waiting for other CF fixes.

I'm closing this PR and will create another one as per requested change https://github.com/appirio-tech/connect-app/issues/3100#issuecomment-509090006

Reopen this PR as per update https://github.com/appirio-tech/connect-app/issues/3100#issuecomment-509092402
@vikasrohit I think this PR can be merged independently without waiting for other CF fixes.


Issue in Object classification pixel based case

Hello,
I have to classify few objects from a tiff file(multiple tiff page) using the ''Object classification pixel based''. But I add the files in both parts (prediction map, raw data). But after that the next option 'Threshold and size filter' is not opening. But 2 days back I did this, but now it is not opened.
Does not show any error. I am not able to use it.
Kindly help me to suggest something.

Hello @Pampa1996,
sorry for the delayed reply. One way to potentially get a project into this kind of state would be to change the thresholding parameters and save the project. This deletes all downstream annotations.
Did this maybe happen?
Cheers
Dominik


Lapce syntax highlighting issue

System:
OS: MacOS, 12.2
Chip: Apple M1
Cargo: 1.62.0 (a748cf5a3 2022-06-08)
Rustc: 1.62.1

Problem:
Here is the video. The way it looks like:

Installing Rust extension
Openning directory
Finding out that highlight is not working -> Reloading Lapce
Opening directory once again
Reloading window
Pressing esc
Highlighting not working

I don't know actually why that happening and the theme is changing incorrectly, but id does

Have you tried reinstalling the Plugin ? You could try to remove "(Username).lapce\plugins\lapce-rust".

Nope, same.

I tried the dev version through the cargo run. Installed plugin and installed plugins tab appeared and the extensions too. Themes appeared too

Seems like the Language Server is crashing.

Well, I was thinking, that is true. But Neovim feels good with rust_analyzer

To me it looks like Neovim is not compiling to WASM. It does not look like a plugin error, since you can see the hightlight for a second or so. We could try to downgrade rust-analyzer threw a modification of the lapce-rust plugin repo but i would prefer to find the main issue.

To me it looks like Neovim is not compiling to WASM.

RA is ran directly, not compiled to WASM by us. I doubt this is an issue with RA's version.

Is the Rust plugin starting at all? When you open a folder do you see information on the bottom left status bar? Do you get hover information, or anything?
Typically the disappearing highlighting is due to RA getting confused about what workspace it is in, and providing empty semantic highlighting.

Try disabling, then re-enabling the plugin. I think I saw a bug where it wouldn't start properly and this fixed it.
Check what folder you're in. I've seen this issue when Lapce is opened on a folder that doesn't have the cargo.toml at the 'top'. Though based on the terminal, it looks like you've just opened the normal Lapce folder.
If Rust isn't starting at all, then check to see if you have a 'rust-analyzer-something-something-something' file in the plugin folder, without a .gz extension.

Well, after some changes, I figured out that problem related not on plugin. Problems were in rust_analyzer. Real solution of this is just update and restart system. WM tests tells, that that is working solution, so... No other solutions here, only rust_analyzer update


Nested class as array - bug in saving

Reproduction Repo: https://github.com/s7dhansh/meteor-astronomy-bug
Steps:

Have a nested array in an astro class
Instantiate the parent class
Save it
'Set' the nested class
Push the nested class into parent class key
Save it again

It throws an error saying: MongoError: Cannot update <nestedClass> and <nestedClass.0.nestedClassField> at the same time.

Hmmm, yes it's seems to be a bug. However, for now you can change:
var phone = new Phone();
phone.set({
  /* ... */
});

to
var phone = new Phone({
  /* ... */
});

and it's gonna work. However, I will prepare a fix.

Ok I've fixed it but haven't published yet. I will do it today or tomorrow

Thank you.
Yes, there are multiple workarounds. I used phone.raw() for now.

Similar issue, with arrays. I have an array of nested classes. When I add a instance of the class to that array, and then edit/set a field in that class, and then save, I get the following error:
"Cannot update 'responses.0' and 'responses.0.codes' at the same time".
This is occurring on the latest release (1.2.0).

Yes it's a limitation of MongoDB that you can execute multiple operations on the same fields or nested fields of the field. I will have to create some workaround for this. We will see what I can do about it.

It's a limitation that you can, or that you cannot?
Hmm - perhaps in cases like this, you could take the safer route and keep the parent-most update, removing the more specific nested updates?

"can't"
It's a little bit more complicated than that. I have to merge top level and nested changes.

Any further thoughts on this? Is the best workaround right now to always set the entire array class (not the nested class property)?
// this
rawObj = obj.responses[0].raw();
rawObj.codes = [200, 400];
obj.set('responses.0', rawObj)

// instead of this
obj.set('responses.0.codes', [200, 400])

@marbemac can you show your schema?

Sure thing, abbreviated models below:
SL.M.EndpointResponse = Astro.Class({
  name: 'EndpointResponse',
  fields: {
    mimeType: {
      type: 'string',
      default: 'application/json',
    },
    codes: {
      type: 'array',
      nested: 'number',
      default() {
        return [200];
      },
    },
  },
});

SL.M.Endpoint = Astro.Class({
  name: 'Endpoint',
  collection: SL.C.Endpoints,
  transform: null,
  fields: {
    name: {
      type: 'string',
      default: '',
      validator: [
        Validators.maxLength(100),
      ],
    },

    responses: {
      type: 'array',
      nested: 'EndpointResponse',
      default() {
        return [];
      },
    },
  }
})

I should mention that in the example I gave before, I first set the new response via:
obj.set('responses.0', new SL.M.EndpointResponse());
obj.set('responses.0.codes', [200,500]);
obj.save(); // error

That is a very simplified example. In reality, those steps happen in disparate parts/components of my app. Otherwise I'd obviously do a simple:
obj.set('responses.0', new SL.M.EndpointResponse({codes: [200, 500]}));
obj.save();

It's the same thing as in the main issue. It's just differs that you are setting document under specified index instead pushing. I will solve this problem. You have to wait a little bit. Stay tuned. I will inform you.

Cool! Not trying to be pushy, was just curious. Thanks a lot.

Any further luck on this one? We regularly run into random scenarios where our front-end is used in a particular new way, which results in an order of operations to the underlying model that triggers this bug. We're working around it as we find issues, but it's leading to messier code (and the odd 500 error as users uncover the bug).
Again, don't want to be pushy! Just curious where this might fit into your roadmap. Thanks!

I'm testing new ways of working with nested data (that will appear in 2.0). I've already solved all issues but it can't be implemented in 1.x because it would be compatibility breaking. I don't know if I want to mess with it in 1.x, or I just should focus on 2.0 and propose you some fix for now.
I've tried to find some workaround for now but it seems that you have to execute the save() method between operations. It's hard to prepare an universal fix.

We're running into this issue more and more, any idea on when a fix for this might be ready? (2.0 other otherwise?). Thanks!

I will try to publish Astronomy 2.0-rc.1 today. Of course it's still early version but it should be usable

Awesome! Really looking forward to it. I know updating the documentation is a huge project, but in the meantime will you perhaps publish a simple list of major API / Philosophy changes for those that want to experiment with 2.0?

Oh also, I guess this was implicit in my original question, but is this issue fixed in 2.0?

Yes it's fixed in 2.0. The best way to learn what changes I've made is taking a look at the example repository for v2 https://github.com/jagi/meteor-astronomy-examples/tree/v2

Dude, the new nesting syntax looks so much nicer! Excited.

Glad that you like it. I'm making last fixes in validation and will publish a package in a few hours.

RC.1 published -> https://github.com/jagi/meteor-astronomy/issues/236


2018 06 deps upgrade

Puh, that was some hard work upgrading dependencies!

node 10.3 has a problem with promises, which only shows up with recent versions of core-js. This was a hard one. Be sure to get node >10.4 or stay with an older version
some change caused the QInfiniteScroll component to hit the recursive limit of vue when the page is loading. I worked around that by adding a Vue.nextTick´ as delay to the done` call.
vue2-leaflet had major changes concerning component names and event names. It also had a completely unexpected and undocumented change how it renders its components. The mounted() function needs to be called, otherwise this.ready is not set to true and no map component shows. vue-test-utils doesn't call this properly (unexpected in itself!), so it added an await Vue.nextTick() to affected tests. The storyshots with maps in them are severely incomplete, but the nextTick trick didn't help there unfortunately
our test/helpers.js mount function included a global stub for window.getComputedStyle(), which unfortunately was quite limited. This introduced a conflict with an undocumented change in Quasar.
the name of vue-test-utils was changed to @vue/test-utils. It also received major badly documented changes, which made lots of our tests fail or throw errors. I didn't upgrade, instead I would rather wait for a proper release with documentation.

I'll merge this PR now to give people the opportunity to test it on dev.karrot.world.
EDIT:
Upgrading clone-deep to v4 causes yarn build to fail:
Unexpected token: keyword (const) [./node_modules/clone-deep/index.js:28,0]

Seems like it doesn't get transpiled by babel...
P.S.:
Updates to webpack 4 are still tbd. Maybe it would be a chance to switch to Quasar CLI, but that would mean restructuring frontend files a bit.

Oops, CI couldn't create the APK:
* What went wrong:
Could not resolve all files for configuration ':releaseCompileClasspath'.
> Could not find runtime.jar (android.arch.lifecycle:runtime:1.0.0).
  Searched in the following locations:
      https://jcenter.bintray.com/android/arch/lifecycle/runtime/1.0.0/runtime-1.0.0.jar
> Could not find common.jar (android.arch.core:common:1.0.0).
  Searched in the following locations:
      https://jcenter.bintray.com/android/arch/core/common/1.0.0/common-1.0.0.jar

I didn't try it locally.
I'll be back on Thursday, will have a closer look then.

Back to work! Android build seems to fail in master too: https://circleci.com/gh/yunity/karrot-frontend/10711
I suspect it's not our fault, but we need to deal with it... @nicksellen any insight how this can happen? I'll try to reproduce it locally.


:bug:  add log controller to operator

Summary
Related issue(s)
Fixes #
Tests

[ ] Unit/function tests have been added and incorporated into make unit-tests.
[ ] Integration tests have been added and incorporated into make integration-test.
[ ] E2E tests have been added and incorporated into make e2e-test-all.
[ ] List other manual tests you have done.

/retest

/override ci/prow/sonarcloud

/override "SonarCloud Code Analysis"

/cc @ldpliu

/lgtm


Issue templates updated to prevent spam in repository

Issues are pretty messy. Good templates should helps.

@skoll43 Is any ways to fix Travis CI jobs ? I found that PPA is not added for Postgres and Cassandra.

@skoll43 Ok, then only issues templates in changes and can be merged.

can i get some free dogecoin.

can i get some free dogecoin.

No!

Thanks!

😀


RabbitMQ secrets engine examples

Add README to the default example and add more examples covering different use cases to help practitioners understand how the module works.

This has been done in #33


Add Sengled Zigbee White 2700K A19/E26 100W Bulb

Device information

Home Assistant Device information

Checklist

[x ] I have created a single PR per device. When you have multiple submissions please create separate PR's.
[x ] For lights - I have only included the gzipped files (*.gz), not the raw CSV files.
[ x] For lights - I have provided a CSV file per supported color mode. Look that up in Developer Tools -> States

Additional info

Thanks for the PR.
A few remarks:

model.json is missing
directory under data should be manufacturer/model. currently you only have model.
please share the device information of this light, from the device page. Than I can judge if everything is correct from a naming perspective.

@dhedges01 did you see my comments?

@bramstroker Added model.json and manufacturer/model folder structure.
Device info
Element extra bright (A19) (E11-N13/E11-N13A/E11-N14/E11-N14A)
by Sengled
Connected via [Zigbee2MQTT Bridge]
Z2M Product Page: [https://www.zigbee2mqtt.io/devices/E11-N13_E11-N13A_E11-N14_E11-N14A.html#sengled-e11-n13%252Fe11-n13a%252Fe11-n14%252Fe11-n14a]

Also need to add E11-N13/E11-N13A/E11-N14/E11-N14A as an alias to model.json, because it contains slashes.
"aliases": [
  "E11-N13/E11-N13A/E11-N14/E11-N14A"
]

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 99.972%

Files with Coverage Reduction
New Missed Lines
%

custom_components/powercalc/sensors/utility_meter.py
1
98.94%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
3566

Relevant Lines:
3567

💛  - Coveralls


Suggestion: Add way to determine MaterialX release used for shipped library / nodes

Issue
Currently if you just look at the shipped "standard" libraries folder there is no way to determine for what release it is used for.

It is possible to load in a random file and hope that the version indicated for the release but this is not guarantee.
Also development or patch versions are not stored inside a file / document so nodes modified / added during a patch release are not discoverable at all.

Nodes themselves have no indication as to what version they belong to either, though they may have a creation version. (Note by default almost all nodes have not version so it needs to be assumed they are version "1".
Proposal

If possible it would be useful to at least include a release version with the libraries.

This could be the same version as provided as a C++ define or run-time string.

Unsure what can be done with per nodes version correspondence.

This is an interesting question, @kwokcb, and although we can modify our CMake build script to stamp the README.md in the libraries folder with the version of the associated MaterialX codebase, I'd be interested in whether this is something that MaterialX developers will often need.
Would it not be sufficient for developers to query the MaterialX version through C++, Python, or JavaScript, or by looking at the version in the CMake script in the root folder of the project?

I'll close out this issue for now, since the mechanisms described above seem like reasonable ways for developers to access the MaterialX version, but I'm open to additional discussion on this topic in the future.


Implementation of RemoteZip functionality to extract only relevant data from dataset.

Describe the solution you'd like
Say, I need only, VV Polarized channel from S1 SLC data. I need to download the whole product (~8G) where almost 4G data is non-utilizable for me.
If we implement Remotezip functionality, we can only extract the relevant bands/Polarization and download them for our use case. This time only ~4G will be downloaded and no unusable data will be there.
Additional context
For more details, you can see how Alaska APIs works here
https://github.com/asfadmin/Discovery-asf_search/blob/75d4bfde8d73a1fbfab9af03b42c0b8c29694496/asf_search/download/download.py#L77
They have also provided an example here https://github.com/asfadmin/Discovery-asf_search/blob/master/examples/5-Download.ipynb (under Downloading Single Products section)

Hello @harshal306 and thanks for submitting this feature request.
remotezip needs the provider to support range requests. The last time we checked for this, no available provider was supporting this feature.

[ ] However, this may have changed now, and we should check again if some available providers support range requests to benefit from feature.


'grav-plugin-markdown-rubytext'

I would like to publish a new plugin 'grav-plugin-markdown-rubytext'.

It is my first plugin:
it has been made possible with support of @rhukster and @sommerregen.

It create a markdown shortcut to make ruby tagged text simply:
it is helpful especially for far east languages like:

japanese,
korean,
chinese
...

I am very proud to have the honor to contribute modestly to GravCMS:
I have tested it as much as I could: to me it's OK.

Here is the link:
grav-plugin-markdown-rubytext

Thank you.

You need to fix the name of your bluerpints.. should be blueprints.yaml, not blueprint.yaml.  After that you will need to rerelease.
Thanks~

I changed to blueprints.yaml

I rereleased

Thanks ～

Should get picked up next hour if all is good.. i'll watch to see what happens.

Ok added!


How convert XSSFSimpleShape to XSSFPicture

How convert XSSFSimpleShape to XSSFPicture?
I want to export simple shapes to pictures.

I know HSSFSimpleShape
I seem to know that HSSFSimpleShape can be converted to HSSFPicture.
HSSFSimpleShape simpleShape = ...;
HSSFPicture picture = new HSSFPicture(simpleShape, simpleShape.Anchor);


HDR file reader fails on files written by ImageMagick

Some .hdr files are failing to load if they are written by ImageMagick. The problem is that it uses an unusual signature of #?RGBE instead of #?RADIANCE (see this thread).
While ImageMagick is getting fixed to use the standard signature on write, there are still .hdr files out there with the unusual signature. Therefore, the .hdr reader should be updated to accept the alternative signature for reading, but should stick with the official one for writing.

It is quite likely that a number of other products have forks of the ImageMagick code, so this problem can potentially impact a number of different tools.

Fixed in this commit


Option action must be equal to one of: nothing, install, delete!  You passed :create

Hello,
Today I was changing a few things on my devbox cookbook when the following error suddenly started to happen with the mysql2_chef_gem cookbook.
Option action must be equal to one of: nothing, install, delete!  You passed :create
I've always used it as described in the docs and have never changed it:
mysql2_chef_gem 'default' do
  client_version '5.6'
  action :install
end

Then I decided to create a completely fresh cookbok depending only on mysql2_chef_gem, nothing else. Same error happened when I executed the code above on the default recipe.
I believe it has something to do with dependency compatibility. This cookbook requires mysql >=6.0 and a new version of the mysql cookbook has just been released. Coincidently the error started to happen approximately at the same time berkshelf downloaded the new version of the mysql cookbook, 8.0.0.
Removing my Berksfile.lock and adding depends 'mysql' '~> 7.2' to my metadata.rb fixed the issue, but this is probably something you might wanna check...

Hello, I still have this exception and I have
depends "mysql", ">= 6.0.21"
depends 'mysql2_chef_gem', ">= 1.0.1"

Has it been fixed?

Hello, I still have this exception and I have
depends "mysql", ">= 6.0.21"
depends 'mysql2_chef_gem', ">= 1.0.1"

Has it been fixed?

Hello, I still have this exception and I have
depends "mysql", ">= 6.0.21"
depends 'mysql2_chef_gem', ">= 1.0.1"

Has it been fixed?

@marcomancuso The correct syntax for that to work is below
depends 'mysql', '~> 7.2'
You'll need to add that to your metadata until they can get the pull request merged.

same issue here - upvoting 👍

Could you do a new release with the fix ? Thanks.

The same issue here

This has been fixed on master


Linux version doesn't build any more

Importent:
Before posting bug repport, make sure you have the lastest retromode.library installed.
and have the lastest files from github.
Describe the bug:
In many places case sensitivity is not respected by the file system, eg. OS!=os directory, AmosKittens.h != amosKittens.h.  Makefile.linux is bitrotted as it doesn't pull in core_includes definitions.  sys_free needs to be free not FreeVec under Linux.
To Reproduce:
from BASH prompt:
make -fmakefile.linux
Expected behavior
(it compiles)
Screenshots
N/A
Desktop (please complete the following information):

OS: [Manjaro Linux]
OS Version [current]
CPU: [x86_64]
Hardware: [2nd generation i7 with 16 GB of RAM]

Additional context
N/A

sys_free is macro is defined depending on the OS, Linux build has broken for some time now.

Tokens has to be endian swapped before you can interpret the tokens.

64bit not really supported, peek / poke / deek / doke, poke into real memory, we need to preallocate a block memory so a internal memory allocation routine from that block to avoid the 64bit memory space.

Adding SDL2 as a dependency will allow assembly optimized endian swapping via sdl_endian.h if interested.

Yes an Linux build need SDL, or Allegro, It might even be native X-Windows, what ever that API is.

I guess a thread can be implemented using C++11 api, it does not matter really as we fallback on AmigaOS.

SDL2 works on Windows, Mac, Linux and MorphOS if you want to combine trips.  Unlike version 1.2, SDL 2.0 wraps hardware graphics acceleration on all platforms.

For Linux we need allow building extensions as .so objects, so that’s a lot work.

retroModePC is also out date I guess.

Sure SDL2 sounds ok, makes no difference it all graphic routines are CPU driven routines, its only when you have the final result and need to scale it has any use, no 3D graphics supported anyway.

the Linux build will also need Menu support, currently we are using AmigaOS menus, we need fallback to legacy menus.

We will also need to change the syntax of peek/poke/deek/doke/leek/loke to accept the bank start of the bank being read from or written to.  Otherwise sidestepping memory protection will result in a segmentation fault.  Any other direct memory accesses will be forbidden.  (This also solves the 64-bit support issues.)
On Fri, Apr 10, 2020 at 11:11 AM, Kjetil<EMAIL_ADDRESS>wrote:
the Linux build will also need Menu support, currently we are using AmigaOS menus, we need fallback to legacy menus.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Peek, poke, leek, loke also needs to work with local variables,
Amos Basic “varptr” returns address of local variable.

We'll just have to replace those special cases with specialized commands and functions like Var Peek() or Hot Spot X=varname.

Yes sure it make sense provide commands make easier to code, but we also have some legacy to support.

There is also the width of bob, that poke after, this of course gives really poor accuracy as its in number int16’s, and not pixels on classic Amos, we have more precise width in Amos Kittens.

Bob banks and icon banks should be stored as texture coordinates, width and height on a huge texture so we can use the texture mapper on the graphics card to blit faster.

Sure, we can do that, maybe hybridize retroMode fuse it with GL stuff.

That's what SDL version 2 does, but better!  Windows uses DirectX, Mac uses Metal, Linux uses Mesa and MorphOS uses TinyGL.

Well lets see what we can use or not the ARGB stuff is not defined yet anyway, so we do what ever like, but logical that use same commands on ARGB as you can on 8bit, the only thing know I wont to do, I forget the palette in ARGB format, as just extra useless lookup.


Default Tab

How do you specify the default tab that should be highlighted when first displaying a page?
How can you make it so that NO tab is initially selected?

You can use the selectedTabIndex property but now has a problem with iOS that I'll fix right nowY
but always will have one item selected.
I'll refer this issue to this #8


CP cannot stat

I tried to install ettern
To Reproduce
Steps to reproduce the behavior:

yay -S etterna-git
wait for finish setup and it says cp cannot stat:no such file directory

Expected behavior
Expected behavior is succesful setup.
Screenshots
https://imgur.com/a/Sh2Hc04
Desktop (please complete the following information):

Archlabs
XFCE4
64bit

Additional context
cp: cannot stat '/home/anonim/.cache/yay/etterna-git/src/etterna/etterna': No such file or directory
==> ERROR: A failure occurred in package().
Aborting...
Error making: etterna-git
.

So, I recently (as in, just a couple few hours ago yesterday technically) tried to install Etterna via etterna-git (AUR). Ran into this and asked
This happens because at some point the executable got renamed from etterna to Etterna, additionally, after fixing that, GtkModule.so no longer exists, so the line related to that has to be removed from the PKGBUILD as well.
I eventually decided to make a non -git AUR package for etterna (AUR), since it felt like that would make sense here.

I will update the AUR package after work, test and report back within 24 hours.

There is a single report that this currently works.

Pushed an update that should fix things as of v0.70.1.


'unicode' object has no attribute 'platformID'

Traceback (most recent call last):
  File "/Users/dcrossland/src/github.com/googlefonts/fontbakery/fontbakery-check-ttf.py", line 1999, in <module>
    main()
  File "/Users/dcrossland/src/github.com/googlefonts/fontbakery/fontbakery-check-ttf.py", line 1326, in main
    elif (familyname.platformID == fullfontname.platformID
AttributeError: 'unicode' object has no attribute 'platformID'

I commented the code block and got
Traceback (most recent call last):
  File "/Users/dcrossland/src/github.com/googlefonts/fontbakery/fontbakery-check-ttf.py", line 1999, in <module>
    main()
  File "/Users/dcrossland/src/github.com/googlefonts/fontbakery/fontbakery-check-ttf.py", line 1712, in main
    logging.err("METADATA.pb name='{}' does not match correct font name format.".format(f.name))
AttributeError: 'module' object has no attribute 'err'

There are occurences of logging.err( that should be logging.error(

The "logging.err(" occurrences as well as the unicode.platformID were not detected by the linter and also not reached by the Cousine font I was using to test this code.
I'll fix the typos and temporarily disable the broken test before I properly fix the test implementation.

I fixed it at https://github.com/googlefonts/fontbakery/commit/6a1baa602e7485942bbe52f86e12bfc66913d3e6


Added Hello World in WarayLang

What does the program do ?
It prints out Hello, World!.
In what programming language it is written?
WarayLang

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


Login Failed. Did endpoint change?

Describe the bug
When I follow github initial steps to login, it gives me below error:
"Enter code sent to "email"
Invalid PIN
Unable to access https://rest-u035.immedia-semi.com/networks after token refresh.
False"
To Reproduce
Steps to reproduce the behavior: Follow initial steps on GITHUB given:
"The simplest way to use this package from a terminal is to call Blink.start() which will prompt for your Blink username and password and then log you in. In addition, http requests are throttled internally via use of the Blink.refresh_rate variable, which can be set at initialization and defaults to 30 seconds.
from blinkpy.blinkpy import Blink
blink = Blink()
blink.start()
This flow will prompt you for your username and password. Once entered, if you likely will need to send a 2FA key to the blink servers (this pin is sent to your email address). When you receive this pin, enter at the prompt and the Blink library will proceed with setup."
Expected behavior
Should have sent me an email with a pin code; I never got the email with the pin code. Some endpoint changed and this repository needs updated? See unable to access url above.
@fronzbot

Actually I got the pin sent to my phone. And now it gives me below error:
"Unable to retrieve cameras from response {'range_days': 7, 'reference': {'usage': 400}, 'networks': [{'network_id': 234025, 'name': 'DomesticTesr', 'cameras': []}, {'network_id': 234027, 'name': 'DomesticTest', 'cameras': []}]}
False
"