Lost Coins

Hello to the community. I sent about 2000 ROI from suprnova to my wallet (1.1.6) about a week before and never come. The transaction is confirmed, I found it on the explorer. Any help? And coins are locked in my wallet, are safe?

Hi
Can you provide the transactionID ?
Did you check that the wallet is in sync with the block explorer ? in otherwords that the last blocknr shown in the debug window matches the blockexplorer last reported block give or take 10 blocks ?
Are you on discord, best way to handle these type of issues is via direct messages to me.
Regards,

Sorry, I don't have discord account. The block that is synched my wallet is 169840 and the wallet shows it is synchronized. The latest block on the explorer at the same time is 172788. The TX ID is:
9916c43125dbe1e063b7f9ef0a5615da6ad74489c068e56c41d6898f0603934e

can you provide me your debug.log ( zip compressed) ?
did you just blindly copy the content of https://roi-coin.com/downloads/blockchain-11072018.zip ? you need to actually get rid of the old blocks/chainstate folders first.
you could try starting the wallet with the following startup flags  -rescan -zapwallettxes=2
it will rescan the chain for your transactions.
The other scenario would be to run dumpwallet c:\myprivatekeys,txt   then stop the wallet rename wallet.dat to wallet.old... restart it will make a new wallet.dat see if it syncs,  If it does you can then use importwallet c:\myprivkey.txt   to re-import your keys.

Sorry for my late response, I didn't have enough time to spend in previous weeks. Finally I download a new version of wallet(V <IP_ADDRESS>.0) and I copy/paste the wallet.dat in there and now it is fully synchronized. It works fine. Anyway, thanx for helping me.


RC v0.6.0

Features

add support for ruby 2.3 (d560d5b)

@classicalliu Please flow our release plan. This was supposed to be frozen only until we release it on Feb 25. (And that's why I don't assign a reviewers when creating this PR.)


joining() Returns Non-empty String for empty Stream

The documentation for joining(CharSequence delimiter, CharSequence prefix, CharSequence suffix) says

Returns:
a String. For empty input stream empty String is returned.

However, this code returns a String with 1 space in it.
      StreamEx.
         of("").
         remove(String::isEmpty).
         joining("", " ", "");

This code also returns a String with 1 space in it.
      StreamEx.
         of("").
         remove(String::isEmpty).
         joining("", "", " ");

Please fix joining() so that it returns an empty String for an empty stream.

The problem is in documentation, not in the implementation. Prefix and suffix should be also added even for empty stream. For example, StreamEx.empty().joining("", "[", "]") should return "[]", not empty string. I will update the documentation, thank you for your report.


fix(cli): Fix security vulnerabilities

copilot:all

Current dependencies on/for this PR:

main

PR #4278   👈

This comment was auto-generated by Graphite.


Move .prettierrc to repo's root

moves the .prettierrc with the settings for all packages to the repo's root
makes prettier and stylelint-config-prettier dependencies at the root level of the repo

Merging this, as I need it in my feature branch


please add nlp dataset section

some links can be found here
https://github.com/niderhoff/nlp-datasets

@YontiLevin can you please send a Pull Request with the datasets section?

done


Allow bookmarks and folders to open in reader mode

Allow user to define certain bookmarks and folders to open in reader mode by default.

@bhajneet done or not?


About .alias: what it does and if we want a different term for it

There are two aims for .alias:

"Pack" variables to lists or dictionary. Suppose a module script involves variables g, args
where args is a list(min_pi0=0,max_pi0=1, nsamp=1000)
We can use

.alias: args = List(min_pi0, max_pi0,nsamp)

To pack variables other than g into a list args. args = list() is a shorthand for packaging all in.

other than packing parameters to dictionary / List,  it is also an opportunity to overwrite parameter names that a user dislike but does not want to change it in the code, for example

  gamma: $x
  .alias: g = gamma

Because in the code one uses variable g which is not an informative name. We therefore offer a chance to fix here.

Ok, now I understand this I may be ok with it.
I was confused by the list() shorthand. But when done longhand it makes logical sense to me, and the shorthand is fine and potentially useful now explained to me.


Could you cut a new release please?

Hi!
I was wondering if you'd mind cutting a new release?
There is some very good stuff in master that I'd be interested in using. e.g: https://github.com/brianbianco/redisio/pull/228
Let me know if I can help!

Working on this.  Hopefully this will get done by the end of july.  No promises :)


Feat/archive

attempt to make a content api call from the browser using the content api docs.
https://docs.ghost.org/api/javascript/content/
the call to http://localhost:2368' and https://demo.ghost.io both resulted in the same error displayed below.

To replicate, go to admin dashboard and create a page with the slug "archives" and visit it locally.
http://localhost:2368/archives/

@raisedadead I setTimeout it for 10000ms and still didn't work. also if my script ran before the sdk loads, I think the error should  be something like " Uncaught ReferenceError: GhostContentAPI is not defined."

I will just add this forum thread for my future reference.
https://forum.ghost.org/t/sample-javascript-content-api-client-library-call-not-working/7719


SCM/Source ID case insensitivity

Is your feature request related to a problem?
We should be able to specify sourceID as well as Sourceid.
Same for scm ids.

I would even go a little further and remove all "...id" which don't add anything semantically and are just (IMHO) cumbersome.

Good idea.

While experimenting with jsonschema validation, I realize that this issue is a blocker.
The current state is not consistent and It would be better to have everything lowercase
Current jsonschema validation warning
Property sourceID is not allowed.
Property scmID is not allowed.

I like @lemeurherve suggestion by replacing sourceID by source but I have mix feeling for replacing scmID by scm because scm is a existing deprecated field.

@dduportal Any opinion?

As a maintainer, I understand the need to make it all lowercase.
As a end-user, if my current syntax scmId does not work anymore, then it is a breaking change that is not really acceptable (I expect the parser to manage all syntaxes OR to have a command that allows me to correct it one time).

Introducing breaking change is not an option to me.
I am considering printing a warning if scmID or sourceID are used instead of the lowercase equivalent scmid or sourceID
The work that  I am doing with jsonschema validation won't be enforced. If your IDE is configured with the updatecli json schema, like I have at the moment for experimenting, it would trigger error messages such as
Property sourceID is not allowed.
Property scmID is not allowed.

But existing updatcecli configuration would still run.

Introducing breaking change is not an option to me. I am considering printing a warning if scmID or sourceID are used instead of the lowercase equivalent scmid or sourceID
The work that I am doing with jsonschema validation won't be enforced. If your IDE is configured with the updatecli json schema, like I have at the moment for experimenting, it would trigger error messages such as
Property sourceID is not allowed.
Property scmID is not allowed.

But existing updatcecli configuration would still run until we fully remove none lowercase fields.

That sounds really cool! GO for it then!


Failed building wheel for thriftpy

I'm seeing the following issue when trying to install on Mac OSX 10.13.5
Collecting thriftpy
  Using cached https://files.pythonhosted.org/packages/f4/19/cca118cf7d2087310dbc8bd70dc7df0c1320f2652873a93d06d7ba356d4a/thriftpy-0.3.9.tar.gz
Requirement already satisfied: ply<4.0,>=3.4 in /Users/brentonmallen/anaconda/envs/blah/lib/python3.7/site-packages (from thriftpy) (3.11)
Building wheels for collected packages: thriftpy
  Running setup.py bdist_wheel for thriftpy ... error
  Complete output from command /Users/brentonmallen/anaconda/envs/blah/bin/python -u -c "import setuptools, tokenize;__file__='/private/var/folders/24/y4dr858s4ns5by5zg8t_bzcw0000gn/T/pip-install-eep46i0m/thriftpy/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /private/var/folders/24/y4dr858s4ns5by5zg8t_bzcw0000gn/T/pip-wheel-uos4sw2o --python-tag cp37:
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.macosx-10.7-x86_64-3.7
  creating build/lib.macosx-10.7-x86_64-3.7/thriftpy
  copying thriftpy/server.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
  copying thriftpy/hook.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
  copying thriftpy/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
  copying thriftpy/thrift.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
  copying thriftpy/rpc.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
  copying thriftpy/utils.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
  copying thriftpy/tornado.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
  copying thriftpy/_compat.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
  creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport
  copying thriftpy/transport/_ssl.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport
  copying thriftpy/transport/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport
  copying thriftpy/transport/sslsocket.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport
  copying thriftpy/transport/socket.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport
  creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
  copying thriftpy/protocol/binary.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
  copying thriftpy/protocol/compact.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
  copying thriftpy/protocol/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
  copying thriftpy/protocol/exc.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
  copying thriftpy/protocol/multiplex.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
  copying thriftpy/protocol/json.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
  creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/parser
  copying thriftpy/parser/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/parser
  copying thriftpy/parser/parser.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/parser
  copying thriftpy/parser/exc.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/parser
  copying thriftpy/parser/lexer.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/parser
  creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/contrib
  copying thriftpy/contrib/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/contrib
  creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport/memory
  copying thriftpy/transport/memory/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport/memory
  creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport/buffered
  copying thriftpy/transport/buffered/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport/buffered
  creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport/framed
  copying thriftpy/transport/framed/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport/framed
  creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/contrib/tracking
  copying thriftpy/contrib/tracking/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/contrib/tracking
  copying thriftpy/contrib/tracking/tracker.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/contrib/tracking
  copying thriftpy/contrib/tracking/tracking.thrift -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/contrib/tracking
  running build_ext
  building 'thriftpy.transport.cybase' extension
  creating build/temp.macosx-10.7-x86_64-3.7
  creating build/temp.macosx-10.7-x86_64-3.7/thriftpy
  creating build/temp.macosx-10.7-x86_64-3.7/thriftpy/transport
  gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/Users/brentonmallen/anaconda/envs/blah/include -arch x86_64 -I/Users/brentonmallen/anaconda/envs/blah/include -arch x86_64 -I/Users/brentonmallen/anaconda/envs/blah/include/python3.7m -c thriftpy/transport/cybase.c -o build/temp.macosx-10.7-x86_64-3.7/thriftpy/transport/cybase.o
  thriftpy/transport/cybase.c:3127:24: error: no member named 'exc_type' in 'struct _ts'
      tmp_type = tstate->exc_type;
                 ~~~~~~  ^
  thriftpy/transport/cybase.c:3128:25: error: no member named 'exc_value' in 'struct _ts'; did you mean 'curexc_value'?
      tmp_value = tstate->exc_value;
                          ^~~~~~~~~
                          curexc_value
  /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:237:15: note: 'curexc_value' declared here
      PyObject *curexc_value;
                ^
  thriftpy/transport/cybase.c:3129:22: error: no member named 'exc_traceback' in 'struct _ts'; did you mean 'curexc_traceback'?
      tmp_tb = tstate->exc_traceback;
                       ^~~~~~~~~~~~~
                       curexc_traceback
  /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
      PyObject *curexc_traceback;
                ^
  thriftpy/transport/cybase.c:3130:13: error: no member named 'exc_type' in 'struct _ts'
      tstate->exc_type = local_type;
      ~~~~~~  ^
  thriftpy/transport/cybase.c:3131:13: error: no member named 'exc_value' in 'struct _ts'; did you mean 'curexc_value'?
      tstate->exc_value = local_value;
              ^~~~~~~~~
              curexc_value
  /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:237:15: note: 'curexc_value' declared here
      PyObject *curexc_value;
                ^
  thriftpy/transport/cybase.c:3132:13: error: no member named 'exc_traceback' in 'struct _ts'; did you mean 'curexc_traceback'?
      tstate->exc_traceback = local_tb;
              ^~~~~~~~~~~~~
              curexc_traceback
  /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
      PyObject *curexc_traceback;
                ^
  thriftpy/transport/cybase.c:3154:24: error: no member named 'exc_type' in 'struct _ts'
      tmp_type = tstate->exc_type;
                 ~~~~~~  ^
  thriftpy/transport/cybase.c:3155:25: error: no member named 'exc_value' in 'struct _ts'; did you mean 'curexc_value'?
      tmp_value = tstate->exc_value;
                          ^~~~~~~~~
                          curexc_value
  /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:237:15: note: 'curexc_value' declared here
      PyObject *curexc_value;
                ^
  thriftpy/transport/cybase.c:3156:22: error: no member named 'exc_traceback' in 'struct _ts'; did you mean 'curexc_traceback'?
      tmp_tb = tstate->exc_traceback;
                       ^~~~~~~~~~~~~
                       curexc_traceback
  /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
      PyObject *curexc_traceback;
                ^
  thriftpy/transport/cybase.c:3157:13: error: no member named 'exc_type' in 'struct _ts'
      tstate->exc_type = *type;
      ~~~~~~  ^
  thriftpy/transport/cybase.c:3158:13: error: no member named 'exc_value' in 'struct _ts'; did you mean 'curexc_value'?
      tstate->exc_value = *value;
              ^~~~~~~~~
              curexc_value
  /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:237:15: note: 'curexc_value' declared here
      PyObject *curexc_value;
                ^
  thriftpy/transport/cybase.c:3159:13: error: no member named 'exc_traceback' in 'struct _ts'; did you mean 'curexc_traceback'?
      tstate->exc_traceback = *tb;
              ^~~~~~~~~~~~~
              curexc_traceback
  /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
      PyObject *curexc_traceback;
                ^
  thriftpy/transport/cybase.c:3178:21: error: no member named 'exc_type' in 'struct _ts'
      *type = tstate->exc_type;
              ~~~~~~  ^
  thriftpy/transport/cybase.c:3179:22: error: no member named 'exc_value' in 'struct _ts'; did you mean 'curexc_value'?
      *value = tstate->exc_value;
                       ^~~~~~~~~
                       curexc_value
  /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:237:15: note: 'curexc_value' declared here
      PyObject *curexc_value;
                ^
  thriftpy/transport/cybase.c:3180:19: error: no member named 'exc_traceback' in 'struct _ts'; did you mean 'curexc_traceback'?
      *tb = tstate->exc_traceback;
                    ^~~~~~~~~~~~~
                    curexc_traceback
  /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
      PyObject *curexc_traceback;
                ^
  thriftpy/transport/cybase.c:3187:24: error: no member named 'exc_type' in 'struct _ts'
      tmp_type = tstate->exc_type;
                 ~~~~~~  ^
  thriftpy/transport/cybase.c:3188:25: error: no member named 'exc_value' in 'struct _ts'; did you mean 'curexc_value'?
      tmp_value = tstate->exc_value;
                          ^~~~~~~~~
                          curexc_value
  /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:237:15: note: 'curexc_value' declared here
      PyObject *curexc_value;
                ^
  thriftpy/transport/cybase.c:3189:22: error: no member named 'exc_traceback' in 'struct _ts'; did you mean 'curexc_traceback'?
      tmp_tb = tstate->exc_traceback;
                       ^~~~~~~~~~~~~
                       curexc_traceback
  /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
      PyObject *curexc_traceback;
                ^
  thriftpy/transport/cybase.c:3190:13: error: no member named 'exc_type' in 'struct _ts'
      tstate->exc_type = type;
      ~~~~~~  ^
  fatal error: too many errors emitted, stopping now [-ferror-limit=]
  20 errors generated.
  error: command 'gcc' failed with exit status 1

  ----------------------------------------
  Failed building wheel for thriftpy
  Running setup.py clean for thriftpy
Failed to build thriftpy
Installing collected packages: thriftpy
  Running setup.py install for thriftpy ... error
    Complete output from command /Users/brentonmallen/anaconda/envs/blah/bin/python -u -c "import setuptools, tokenize;__file__='/private/var/folders/24/y4dr858s4ns5by5zg8t_bzcw0000gn/T/pip-install-eep46i0m/thriftpy/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /private/var/folders/24/y4dr858s4ns5by5zg8t_bzcw0000gn/T/pip-record-2l7268_k/install-record.txt --single-version-externally-managed --compile:
    running install
    running build
    running build_py
    creating build
    creating build/lib.macosx-10.7-x86_64-3.7
    creating build/lib.macosx-10.7-x86_64-3.7/thriftpy
    copying thriftpy/server.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
    copying thriftpy/hook.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
    copying thriftpy/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
    copying thriftpy/thrift.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
    copying thriftpy/rpc.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
    copying thriftpy/utils.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
    copying thriftpy/tornado.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
    copying thriftpy/_compat.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy
    creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport
    copying thriftpy/transport/_ssl.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport
    copying thriftpy/transport/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport
    copying thriftpy/transport/sslsocket.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport
    copying thriftpy/transport/socket.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport
    creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
    copying thriftpy/protocol/binary.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
    copying thriftpy/protocol/compact.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
    copying thriftpy/protocol/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
    copying thriftpy/protocol/exc.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
    copying thriftpy/protocol/multiplex.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
    copying thriftpy/protocol/json.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/protocol
    creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/parser
    copying thriftpy/parser/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/parser
    copying thriftpy/parser/parser.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/parser
    copying thriftpy/parser/exc.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/parser
    copying thriftpy/parser/lexer.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/parser
    creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/contrib
    copying thriftpy/contrib/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/contrib
    creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport/memory
    copying thriftpy/transport/memory/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport/memory
    creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport/buffered
    copying thriftpy/transport/buffered/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport/buffered
    creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport/framed
    copying thriftpy/transport/framed/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/transport/framed
    creating build/lib.macosx-10.7-x86_64-3.7/thriftpy/contrib/tracking
    copying thriftpy/contrib/tracking/__init__.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/contrib/tracking
    copying thriftpy/contrib/tracking/tracker.py -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/contrib/tracking
    copying thriftpy/contrib/tracking/tracking.thrift -> build/lib.macosx-10.7-x86_64-3.7/thriftpy/contrib/tracking
    running build_ext
    building 'thriftpy.transport.cybase' extension
    creating build/temp.macosx-10.7-x86_64-3.7
    creating build/temp.macosx-10.7-x86_64-3.7/thriftpy
    creating build/temp.macosx-10.7-x86_64-3.7/thriftpy/transport
    gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/Users/brentonmallen/anaconda/envs/blah/include -arch x86_64 -I/Users/brentonmallen/anaconda/envs/blah/include -arch x86_64 -I/Users/brentonmallen/anaconda/envs/blah/include/python3.7m -c thriftpy/transport/cybase.c -o build/temp.macosx-10.7-x86_64-3.7/thriftpy/transport/cybase.o
    thriftpy/transport/cybase.c:3127:24: error: no member named 'exc_type' in 'struct _ts'
        tmp_type = tstate->exc_type;
                   ~~~~~~  ^
    thriftpy/transport/cybase.c:3128:25: error: no member named 'exc_value' in 'struct _ts'; did you mean 'curexc_value'?
        tmp_value = tstate->exc_value;
                            ^~~~~~~~~
                            curexc_value
    /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:237:15: note: 'curexc_value' declared here
        PyObject *curexc_value;
                  ^
    thriftpy/transport/cybase.c:3129:22: error: no member named 'exc_traceback' in 'struct _ts'; did you mean 'curexc_traceback'?
        tmp_tb = tstate->exc_traceback;
                         ^~~~~~~~~~~~~
                         curexc_traceback
    /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
        PyObject *curexc_traceback;
                  ^
    thriftpy/transport/cybase.c:3130:13: error: no member named 'exc_type' in 'struct _ts'
        tstate->exc_type = local_type;
        ~~~~~~  ^
    thriftpy/transport/cybase.c:3131:13: error: no member named 'exc_value' in 'struct _ts'; did you mean 'curexc_value'?
        tstate->exc_value = local_value;
                ^~~~~~~~~
                curexc_value
    /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:237:15: note: 'curexc_value' declared here
        PyObject *curexc_value;
                  ^
    thriftpy/transport/cybase.c:3132:13: error: no member named 'exc_traceback' in 'struct _ts'; did you mean 'curexc_traceback'?
        tstate->exc_traceback = local_tb;
                ^~~~~~~~~~~~~
                curexc_traceback
    /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
        PyObject *curexc_traceback;
                  ^
    thriftpy/transport/cybase.c:3154:24: error: no member named 'exc_type' in 'struct _ts'
        tmp_type = tstate->exc_type;
                   ~~~~~~  ^
    thriftpy/transport/cybase.c:3155:25: error: no member named 'exc_value' in 'struct _ts'; did you mean 'curexc_value'?
        tmp_value = tstate->exc_value;
                            ^~~~~~~~~
                            curexc_value
    /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:237:15: note: 'curexc_value' declared here
        PyObject *curexc_value;
                  ^
    thriftpy/transport/cybase.c:3156:22: error: no member named 'exc_traceback' in 'struct _ts'; did you mean 'curexc_traceback'?
        tmp_tb = tstate->exc_traceback;
                         ^~~~~~~~~~~~~
                         curexc_traceback
    /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
        PyObject *curexc_traceback;
                  ^
    thriftpy/transport/cybase.c:3157:13: error: no member named 'exc_type' in 'struct _ts'
        tstate->exc_type = *type;
        ~~~~~~  ^
    thriftpy/transport/cybase.c:3158:13: error: no member named 'exc_value' in 'struct _ts'; did you mean 'curexc_value'?
        tstate->exc_value = *value;
                ^~~~~~~~~
                curexc_value
    /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:237:15: note: 'curexc_value' declared here
        PyObject *curexc_value;
                  ^
    thriftpy/transport/cybase.c:3159:13: error: no member named 'exc_traceback' in 'struct _ts'; did you mean 'curexc_traceback'?
        tstate->exc_traceback = *tb;
                ^~~~~~~~~~~~~
                curexc_traceback
    /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
        PyObject *curexc_traceback;
                  ^
    thriftpy/transport/cybase.c:3178:21: error: no member named 'exc_type' in 'struct _ts'
        *type = tstate->exc_type;
                ~~~~~~  ^
    thriftpy/transport/cybase.c:3179:22: error: no member named 'exc_value' in 'struct _ts'; did you mean 'curexc_value'?
        *value = tstate->exc_value;
                         ^~~~~~~~~
                         curexc_value
    /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:237:15: note: 'curexc_value' declared here
        PyObject *curexc_value;
                  ^
    thriftpy/transport/cybase.c:3180:19: error: no member named 'exc_traceback' in 'struct _ts'; did you mean 'curexc_traceback'?
        *tb = tstate->exc_traceback;
                      ^~~~~~~~~~~~~
                      curexc_traceback
    /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
        PyObject *curexc_traceback;
                  ^
    thriftpy/transport/cybase.c:3187:24: error: no member named 'exc_type' in 'struct _ts'
        tmp_type = tstate->exc_type;
                   ~~~~~~  ^
    thriftpy/transport/cybase.c:3188:25: error: no member named 'exc_value' in 'struct _ts'; did you mean 'curexc_value'?
        tmp_value = tstate->exc_value;
                            ^~~~~~~~~
                            curexc_value
    /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:237:15: note: 'curexc_value' declared here
        PyObject *curexc_value;
                  ^
    thriftpy/transport/cybase.c:3189:22: error: no member named 'exc_traceback' in 'struct _ts'; did you mean 'curexc_traceback'?
        tmp_tb = tstate->exc_traceback;
                         ^~~~~~~~~~~~~
                         curexc_traceback
    /Users/brentonmallen/anaconda/envs/blah/include/python3.7m/pystate.h:238:15: note: 'curexc_traceback' declared here
        PyObject *curexc_traceback;
                  ^
    thriftpy/transport/cybase.c:3190:13: error: no member named 'exc_type' in 'struct _ts'
        tstate->exc_type = type;
        ~~~~~~  ^
    fatal error: too many errors emitted, stopping now [-ferror-limit=]
    20 errors generated.
    error: command 'gcc' failed with exit status 1

My environment:
pip freeze
bitarray==0.8.3
certifi==2018.4.16
ply==3.11
pyspark==2.3.1
six==1.10.0

Any thoughts on a cause or solution?
Thanks

duplicate of #333


[Bug]: failed to get flashback sql on several db objects

ODC version
4.2.0
OB version
not related
What happened?
I want to generate flash back sql on some db objects, and I got nothing as you can see as follow:

What did you expect to happen?
I can get the generated flashback sql.
How can we reproduce it (as minimally and precisely as possible)?
try to generate a flashback sql
Anything else we need to know?
No response
Cloud
No response

OcaneaBase only supports these db objects as follows:
private static final Set<String> SUPPORTED_TYPES = new HashSet<>();

static {
    SUPPORTED_TYPES.add("TABLE");
    SUPPORTED_TYPES.add("VIEW");
    SUPPORTED_TYPES.add("TENANT");
    SUPPORTED_TYPES.add("DATABASE");
    SUPPORTED_TYPES.add("SCHEMA");
}

ODC will give up generating sql when meets unsupported types:
// DBRecyclebinService#getFlashbackSql
public String getFlashbackSql(@NonNull ConnectionSession session, List<DBRecycleObject> recycleObjects) {
        ...
        for (DBRecycleObject recycleObject : recycleObjects) {
            ...
            if (!SUPPORTED_TYPES.contains(type.toUpperCase())) {
                continue;
            }
            ...
        }
        ...
}

ref:  DBRecyclebinService

to fix this bug, we generate a sql comment when user's recycle object's type is not in available types:

pass


Fix a strange thing in parallel::detail::handle_exception. (Fix #2834.)

Fixes #2834 .
flyby: Fixes #3088 .

@taeguk Thanks for looking into this! It's overdue that you get access to the repository - I've sent you an invite.


LMDB is throwing an EPERM error when trying to create the database.

Looks promising, but I'm curious if you've managed to get this working on macOS. Specifically, in a sandboxed applications using a standard Xcode project.
When I try to create the Database within the initial Transaction, I get:
Error: other(returnCode: 1)
This maps to the EPERM that LMDB throws.
This is the same problem that is present in another Swift wrapper around LLMD when attempting to use it on macOS. It's likely related to how LMDB uses Semaphores. There was some discussion awhile back here:
Issue 23
If you're able to get this working on macOS, are you using any additional build flags?
In order to reproduce this, just create a new Xcode project for macOS, add the QuickLMDB package, then try and open a database from within a transaction. It will likely throw an exception and the error will be EPERM.

Hey thanks for bringing this up and referencing the discussion in the SwiftLMDB project.
My years of experience in Swift and LMDB is mostly based on Linux, the platform where this framework was forged and tested.
I recently began working on a new iOS and MacOS project (my first frontend project in years) - I hit this exact issue when I "broke ground" about a month ago. I was not able to get it working with a native MacOS (sandboxed) build, but I have since (for many reasons) reduced my deployment target to just iOS, and its working great (as it does in non-sandbox MacOS).
As your reference to issue 23 in SwiftLMDB mentions - its super weird that Apple (supposedly) allows use of these semaphores on the iOS sandbox, but not the MacOS sandbox?

Thanks for the follow-up. Running LLMD in noLock mode wasn't something I explored at the time but might be a viable workaround. My use-case at the time was mostly read-heavy and involved doing a lot of "full table scans", so I was interesting in seeing if I could use multiple cursors to parallelize that in some way.
You're welcome to close this issue because, like with the other projects, it's more of an LMDB issue than anything else. I was just curious if you had found a working build configuration or not. Thanks again for sharing this project.

https://bugs.openldap.org/show_bug.cgi?id=10043

Please provide a simple test case to reproduce this problem. Note that I don't usually spend any time with MacOS dev tools, so you will need to be explicit in every step otherwise I won't be able to investigate.

After seeing some additional feedback from @hyc in issue 23 of SwiftLMDB and in the ticket, I am thinking this one will get closed out and I'll need to adjust my support claims in the README to note this exception. QuickLMDB is meant to be a rather pure interpretation of a wrapper and this issue gets kinda messy.
That being said, it is very easy to swap a different (or modified) version of LMDB into QuickLMDB if someone is so inclined to make these changes.
As an aside,
I've entertained building an additional library on top of QuickLMDB that integrates natively with Swift's concurrency model (in place of the locking mechanisms), but never justified building it for many obvious reasons.
This might be an interesting avenue to explore in the future, but unfortunately, cant be on my immediate roadmap at this time.

Thanks for following up on this and exploring what the options where.


how to test with my own picture

I am interested with your work, it is wonderful, and I want to use a picture to test this network to directly generate output (such as .ply files or .obj files). Do you have  any opinions.

to directly generate output (such as .ply files or .obj files)

Hi @lisentao this modification did the job for me:
https://github.com/AlbertoRemus/mcmr/commit/7e9bd74f12da19e28365d0f2ba77bc3ec3648d9e

Thank you very much.@AlbertoRemus


Multiple different log formats with a merge report

Worst subject ever!! Sorry!
This feature request is linked to #190 and #78 ... I am thinking I would need this kind of thing in future, where using the logs from the web server and the reverse proxy, which both would have two different log formats, merged into one report. Not sure how accurate the representation might be?
Something like goaccess -p1 apache.conf -f1 access.log -p2 varnish.conf -p varnishncsa.log
Thanks

I think this would have to be done within one config file to avoid conflicts between options. I'm thinking something like:
log-format  %h %^[%d:%^] "%r" %s %b "%R" "%u" access.log
log-format  %h %^[%d:%^] "%r" %s %b "%R" "%u" varnish.log

Silly question, would you add the log file in the config file or pass the log file on the command line? Don't think goaccess would be able to match the logs files by corresponding matched patterns?

I'm using cat
cat files/*log > combined.log and parsing combined.log into goaccess...

how about:
log-format  %h %^[%d:%^] "%r" %s %b "%R" "%u"

[access.log]
log-format  %h %^[%d:%^] "%r" %s %b "%R" "%u"

[varnish.log]
log-format  %h %^[%d:%^] "%r" %s %b "%R" "%u"

This way it is backward compatible with option to adjust log formats per file.
Adding log file at the end may be problematic, especially when you process from stdin.

Short term fix, changed both the web server and reverse proxy logs to share a format and add extra details per format after "%~" in the goaccessrc file. Works for making goaccess reports but other local log reporting tools not happy, but I can live with that for now.
Hoping that we can get the hit/miss counter #190 / #291 .... '-)

Hi, is this still "evaluated"? I have the same issue, as I have pages with HTTPS (and reverse proxy for SSL termination), and pages without HTTPS. This results in some log files with the standard %h host variable, but others have the x-forwarded-for, in another field of the log (at the very end)...

@aadlung it certainly is. I just need to fix some pending issues before I get to this. Thanks for the reminder!

@allinurl been a little over a year now, any update on this?

@CraigNoble I agree, this release is way behind. I'm addressing the new on-disk storage which will be the cutoff for the next version. I appreciate the reminder, I'll make sure to prioritize this on the following release.

bump

my suggestion would be to add an optional additional parameter to log-file parameter to specify the log-format
e.g.
log-file /var/log/xferlog ftplog
then additional log formats could be defined like log-format-<name> e.g.
log-format-ftplog  %h %^[%d:%^] "%r" %s %b "%R" "%u"
if first not provided then you default to the default log-format, if the latter is not provided but is referred to - we should either send some error or fall back to the default

bump

My $.02 would be to split the pipeline into log reader->store and the reporter that works off the store. Looks to me like this is already happening if you use keep-db-file true?

@dmaziuk yes, it's using a similar model.

Good afternoon,
We're attempting to parse a number of log files, 4-5 of which have a different format for analytics reasons. As a result of this, it would be ideal to be able to configure goaccess to obey a line such as:
log-file /var/log/httpd/site.example.com-access_log log-format common
log-file /var/log/httpd/site2.example.com-access_log log-format combined

Alternatively, https://github.com/allinurl/goaccess/issues/213#issuecomment-210969069 is also reasonable, but would quickly increase config file size, but I'm happy with either.
For those who are trying to do this, my workaround is currently to setup multiple CustomLog directives in the VirtualHost definition, allowing me to have two formats on the disk. It's also not ideal, as we're doubling the disk space necessary for logs for those sites, but it does work.
I'll watch this issue for any movement on allowing this to be defined in the config file, which would definitely be preferable.

bump

@crbon Thanks for the reminder on this. As soon as I finish #117, I'll work on this (and several other cool features). It should be sooner than later. Stay tuned..

mil

Thank you for the update! I'd actually all but assumed this might never get addressed....
I'll look forward to an update in a future release! I'm still using my work around, but it is disk space heavy. Thank you again for your excellent work here.
As a remind for all of us:


Feature: allow specifying timeout

Currently, benches can run forever. Having a timeout option would be nice.

It's quite a messy problem to solve, and even harder if you are running on bare-bones runtime
There are two types of timeouts:

cpu time
wall clock time

wall clock time one is much easier to achieve, as it only requires setTimeout and event loop to not be blocked. meanwhile cpu time timeout is much harder to achieve because it requires a separate watcher thread/worker/process to be spawned that can terminate the main (halted) one
a robust timeout feature would have to implement both types and require making whole benchmarking process aware of timeouts being forced (on-disk/cross-thread/process state & additional tracking overhead during benchmarking)
one thing for sure is that core of mitata will never have such functionality but maybe one day there will be bigger brother library or additional function/module that has this


feat: remove connection gc

Signed-off-by: Gaius<EMAIL_ADDRESS>
Description

Remove connection GC.

Related Issue

Motivation and Context

Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

Codecov Report

Merging #1378 (3a2a035) into main (95c105a) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1378      +/-   ##
==========================================
- Coverage   45.56%   45.52%   -0.05%
==========================================
  Files         140      140
  Lines       12032    12032
==========================================
- Hits         5482     5477       -5
- Misses       5924     5929       +5
  Partials      626      626

Flag
Coverage Δ

unittests
45.52% <ø> (-0.05%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

client/daemon/peer/peertask_conductor.go
57.14% <0.00%> (-1.01%)
:arrow_down:

...ent/daemon/peer/peertask_piecetask_synchronizer.go
47.61% <0.00%> (+2.16%)
:arrow_up:


Raise ChannelClosedError in Merge if all channels are closed

Sorry I didn't see this before, this is probably covered by #61, which is a big revamp of exceptions.

this is probably covered by https://github.com/frequenz-floss/frequenz-channels-python/pull/61,

no,  because this PR is a condition check,  not the introduction of a new exception type.

Yeah, sorry, I meant #62. The commit changing this is the 9ne making ready() no-thow. It could be moved to #61 now, at some point it was more intertwined with the select change

But if we don't want to merge the commit in #62, there are more places similar to this that we need to fix

Now the mentioned commit was moved to #61.


wrong package json?

There is a space on the coverage_unit script on "unit{SPACE}_mocha", is it ok?

Yes, Mocha has two scripts, and istanbul uses _mocha,  the one that doesn't fork another process.
Chech here https://github.com/gotwarlost/istanbul/issues/44#issuecomment-16093330

thanks!!


MWPW-140273 Highlight replace fragment

Updates made by MEP's replaceContent are highlighted if you use mepHighlight, but replaceFragment updates do not highlight in the same way.
Manifest names in highlight are the full path, making it a much longer string.  Name has been truncated to match the preview button panel format.
Resolves: MWPW-140273
Test URLs:

Before: https://main--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/highlight-replace-fragment/?mepHighlight=true&martech=off
After: https://highlight-replace-fragment--milo--adobecom.hlx.page/drafts/vgoodrich/fragments/highlight-replace-fragment/?mepHighlight=true&martech=off

Should we add a unit test?

@mokimo added to the unit test to specifically test the new code


Killing a pod results in cluster unuseable  and status of pods show "Unknown" or "Pending" forever.

Sometimes, after a pod is killed, all the pods get into a state "Unknown" or "Pending".
kubectl logs -f  gives "net/http: TLS handshake timeout".
After waiting for a day, they all got into "Terminating" state".
Attaching cdk-field-agent output (taken after they went into "Terminating" state.
results-2018-07-11-16-27-54.tar.gz

Has not occurred again with our chaos tests so far. Will keep trying of course, but I suspect it possibly due to one of the machines going offline.


gitea own dark codemirror theme

fix #6573 (Editor in dark mode can't be seen)
feel free to modify the colors
old

examples - this PR
md

css

js

selection

added selection color

Codecov Report

Merging #7317 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7317      +/-   ##
==========================================
+ Coverage   41.25%   41.25%   +<.01%
==========================================
  Files         464      464
  Lines       62867    62867
==========================================
+ Hits        25934    25937       +3
+ Misses      33541    33539       -2
+ Partials     3392     3391       -1

Impacted Files
Coverage Δ

modules/log/file.go
77.62% <0%> (+2.09%)
:arrow_up:

Continue to review full report at Codecov.

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


[Feature Request] Change tracking similar or same as Neko/J2K

Why/User Benefit/User Problem
Does not have to open a "new page" where the screen is only tracking, and shows on the bottom screen
Be able to delete/remove manga from tracking list in case the wrong one was selected.
Selecting chapters are easier when inputting manually.
What/Requirements
Look at Neko?

Unlikely to be implemented, this falls under Tachiyomi Stable's purview then SY's. SY likely wont get any tracking upgrades on its own, unless someone that is not me makes it and posts a PR.

Oh man. Ok

My tracking button will be going away soon anyway, Ill will be dropping my manga page and implementing previews when its done, so I will be picking up whatever they do for the tracking tab(mine was just a stop gap)


Add MyReadingManga

Source name
Myreadingmanga
Source link
https://myreadingmanga.info/
Source language
Multi
Other details
It's mostly manga but it also contains a lot of video content. +18 = yes
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

This is only for video extensions

This is only for video extensions

It does has video extensions


Translation migration Pt.5

Tasks
Migrate copies in these pages including clickable components:

[ ] Wallet page

[ ] HKD Top and withdraw
[ ] LikeCoin connection
[ ] Transactions page

[ ] Settings

[ ] Page components
[ ] Email setup
[ ] Password setup
[ ] Connect LikeCoin

[ ] Search page

partially resolved at https://github.com/thematters/matters-web/pull/4323, closed and create new issue if need


AddressSanitizer: requested allocation size exceeds maximum supported size

JerryScript revision
Commit: https://github.com/jerryscript-project/jerryscript/commit/05dbbd134c3b9e2482998f267857dd3722001cd7
Version: v3.0.0
Build platform
Ubuntu 20.04.5 LTS (Linux 5.4.0-144-generic x86_64)
Build steps
python ./tools/build.py --clean --debug --compile-flag=-m32 --compile-flag=-fno-omit-frame-pointer --compile-flag=-fno-common --compile-flag=-fsanitize=address --compile-flag=-g --strip=off --lto=off --error-messages=on --system-allocator=on --logging=on --line-info=on --stack-limit=20

Test case
testcase

function func0 ( n , r , t , u ) { if ( n < 0 ) { throw arguments ; } return n + r + t + u ; } function func1 ( n , r , t , u , f ) { return i ( n , r , t , u * f ) ; } function func2 ( n , r ) { return t ( n , ... r ) ; } var e = new Float32Array ( 1 * 1000000.0 * 1000.0 ) . reverse ( ) . filter ( r => r === - r . valueOf ) [ 0 ] ; function func3 ( ) { ; } function func4 ( n ) { return r ( n , n ) ; }

// poc.js
var e = new Float32Array ( 1000000.0 * 1000.0 ) . reverse ( );

Execution steps & Output
$ ./jerryscript/build/bin/jerry poc.js
=================================================================
==2464945==ERROR: AddressSanitizer: requested allocation size 0xee6b2800 (0xee6b3800 after adjustments for alignment, red zones etc.) exceeds maximum supported size of 0xc0000000 (thread T0)
    #0 0x80efe65 in malloc (./jerryscript/build/bin/jerry+0x80efe65)
    #1 0x825f11c in jmem_heap_alloc ./jerryscript/jerry-core/jmem/jmem-heap.c:254:10
    #2 0x825f11c in jmem_heap_gc_and_alloc_block ./jerryscript/jerry-core/jmem/jmem-heap.c:291:24
    #3 0x81d5463 in ecma_arraybuffer_allocate_buffer ./jerryscript/jerry-core/ecma/operations/ecma-arraybuffer-object.c:169:28
    #4 0x81c47d1 in ecma_builtin_typedarray_prototype_dispatch_routine ./jerryscript/jerry-core/ecma/builtin-objects/typedarray/ecma-builtin-typedarray-prototype.c:1929:12
    #5 0x81b94a4 in ecma_builtin_dispatch_routine ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1460:10
    #6 0x81b94a4 in ecma_builtin_dispatch_call ./jerryscript/jerry-core/ecma/builtin-objects/ecma-builtins.c:1489:12
    #7 0x81fb6b7 in ecma_op_function_call_native_built_in ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1217:5
    #8 0x81fa81c in ecma_op_function_call ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1411:16
    #9 0x81fa5ce in ecma_op_function_validated_call ./jerryscript/jerry-core/ecma/operations/ecma-function-object.c:1371:10
    #10 0x82d7630 in opfunc_call ./jerryscript/jerry-core/vm/vm.c:758:5
    #11 0x82d7630 in vm_execute ./jerryscript/jerry-core/vm/vm.c:5217:9
    #12 0x82d4f61 in vm_run ./jerryscript/jerry-core/vm/vm.c:5312:10
    #13 0x82d4c38 in vm_run_global ./jerryscript/jerry-core/vm/vm.c:286:25
    #14 0x812a4e4 in jerry_run ./jerryscript/jerry-core/api/jerryscript.c:548:24
    #15 0x83eac3e in jerryx_source_exec_script ./jerryscript/jerry-ext/util/sources.c:68:14
    #16 0x812162c in main ./jerryscript/jerry-main/main-desktop.c:156:20
    #17 0xf7b9aed4 in __libc_start_main (/lib32/libc.so.6+0x1aed4)

==2464945==HINT: if you don't care about these errors you may set allocator_may_return_null=1
SUMMARY: AddressSanitizer: allocation-size-too-big (./jerryscript/build/bin/jerry+0x80efe65) in malloc
==2464945==ABORTING

Credits:
@Ye0nny, @EJueon of the seclab-yonsei.

Allocating such large arrays (1 000 000 000 * 4 bytes or nearly 4GB) is not a supported use case of jerryscript.

A low end library does not need to support allocating way too large arrays,


Readme

The README does not appear formatted anymore on GitHub at the moment. Maybe they've changed the way they handle readmes without extensions. Try adding an extension to your readme file.

A ".rst" extension is required for GitHub formatting.  I will consider adding it in the next release.


Clean up hello-world tests

Fixes https://github.com/winterchord/xjava/commit/d09fb713d19abbcbdaaa979adb59aa7fc94532fd#commitcomment-14962172
The original PR (https://github.com/exercism/xjava/pull/69) that this issue
could have been fixed in was merged before I could fix this issue.

@sit or @jtigger, can you review when you have a moment?

ah!  I missed that too.


Display all posts including replies

Is your feature request related to a problem? Please describe.
It is hard to see of activity happening on DevHub now that there is no option to see all replies.
Describe the solution you'd like
A button that shows all replies.
Describe alternatives you've considered
I couldn't come up with a better alternative.

@ori-near I would like to tackle this task

Hi @nearmax – thanks for sharing this. We actually had a planned solution for this as part of https://github.com/near/neardevhub-widgets/issues/114 through a sort button, see design:

I propose that as part of this ticket we implement the originally proposed scope below, which I believe addresses your concern. Please confirm if otherwise.
Scope
Problem
Currently, users can only see parent level posts ordered by recency. However, users may want to see additional posts such as all replies so that they can get a sense for everything that's happening on DevHub.
User Story
As a user, I want to have a sort filter experience so that I can easily find all posts.
Acceptance Criteria

A user sees the updated search/filter UI elements (Search box, Sort dropdown, Author dropdown, and Label dropdown) per the design
The sort label will have a dropdown with three options:

Latest – This is the default selection. It loads the most recent top-level posts and replaces the existing home button
Hottest – This shows the most popular posts and replaces the old hottest button
All replies – This shows all the replies (both parent or child level) in most recent order and replaces the existing recent button

Hey @carina-akaia – thanks for expressing interest here! Since @ailisp is focusing right now on all search improvements, I'd like to propose that he takes this on and can delegate to you if needed.


Unable to launch job in a p2 instance

Environment:
AWS ParallelCluster [ aws-parallelcluster-3.7.2]
region: eu-west-1
OS: [alinux2]
Scheduler: [slurm]
HeadNode instance type: [c5a.large]
Compute CPU instance type: [c5a.8xlarge] Partition = comp4x-cpu16-mem32-od
Compute GPU instance type: [p2.xlarge] Partition = gpu1x-gpu1-cpu4-od
Service Quota limit:
Running On-Demand P instances: 8
Running On-Demand Standard (A, C, D, H, I, M, R, T, Z) instances: 320
Custom scripts
pclusterTagsAndBudget post install script
Bug description and how to reproduce:
When I launch a job in the c5a.8xlarge instance, works OK. But when I launch the same job in the p2.xlarge instance (JobId=35), the instance is launched, but it is terminated after a few minutes. Job in squeue remains in CF or PD all the time.
P2 configuration
- Name: gpu1x-gpu1-cpu4-od
  CapacityType: ONDEMAND
  ComputeResources:
    - Name: p21xlargeod
      MinCount: 0
      MaxCount: 30
      Instances:
        - InstanceType: p2.xlarge
  Networking:
    SubnetIds:
      - subnet-xxxxxxxxx
  CustomActions:
    OnNodeConfigured:
      Script: s3://xxxxx/post_install.sh
  Iam:
    S3Access:
      - BucketName: xxxxxxxx
        EnableWriteAccess: false
    AdditionalIamPolicies:
      - Policy: >-
          arn:aws:iam::xxxxx
  ComputeSettings:
    LocalStorage:
      RootVolume:
        VolumeType: gp3

/var/log/slurmctld.log
[2024-01-12T10:05:46.156] sched: Allocate JobId=35 NodeList=gpu1x-gpu1-cpu4-od-dy-p21xlargeod-2 #CPUs=1 Partition=gpu1x-gpu1-cpu4-od
[2024-01-12T10:05:47.500] POWER: no more nodes to resume for job JobId=35
[2024-01-12T10:05:47.500] POWER: power_save: waking nodes gpu1x-gpu1-cpu4-od-dy-p21xlargeod-2
[2024-01-12T10:08:58.020] update_node: node gpu1x-gpu1-cpu4-od-dy-p21xlargeod-2 reason set to: Scheduler health check failed
[2024-01-12T10:08:58.020] requeue job JobId=35 due to failure of node gpu1x-gpu1-cpu4-od-dy-p21xlargeod-2
[2024-01-12T10:08:58.020] Requeuing JobId=35
[2024-01-12T10:08:58.020] powering down node gpu1x-gpu1-cpu4-od-dy-p21xlargeod-2
[2024-01-12T10:09:17.516] POWER: power_save: suspending nodes gpu1x-gpu1-cpu4-od-dy-p21xlargeod-2

/var/log/parallelcluster/slurm_resume.log
2024-01-12 10:05:47,688 - [slurm_plugin.resume:_resume] - INFO - Launching EC2 instances for the following Slurm nodes: gpu1x-gpu1-cpu4-od-dy-p21xlargeod-2
2024-01-12 10:05:47,704 - [slurm_plugin.resume:_resume] - INFO - Current state of Slurm nodes to resume: [('gpu1x-gpu1-cpu4-od-dy-p21xlargeod-2', 'MIXED+CLOUD+NOT_RESPONDING+POWERING_UP')]
2024-01-12 10:05:47,735 - [botocore.credentials:load] - INFO - Found credentials from IAM Role: pcluster-RoleHeadNode-xxxx
2024-01-12 10:05:47,781 - [slurm_plugin.instance_manager:_add_instances_for_nodes] - INFO - Launching instances for Slurm nodes (x1) ['gpu1x-gpu1-cpu4-od-dy-p21xlargeod-2']
2024-01-12 10:05:47,781 - [slurm_plugin.fleet_manager:create_fleet] - INFO - Launching instances with create_fleet API. Parameters: {'LaunchTemplateConfigs': [{'LaunchTemplateSpecification': {'LaunchTemplateName': 'pcluster-gpu1x-gpu1-cpu4-od-p21xlargeod', 'Version': '$Latest'}, 'Overrides': [{'InstanceType': 'p2.xlarge', 'SubnetId': 'subnet-015b1e1ad2c5f32de'}]}], 'TargetCapacitySpecification': {'TotalTargetCapacity': 1, 'DefaultTargetCapacityType': 'on-demand'}, 'Type': 'instant', 'OnDemandOptions': {'AllocationStrategy': 'lowest-price', 'SingleInstanceType': True, 'SingleAvailabilityZone': True, 'MinTargetCapacity': 1, 'CapacityReservationOptions': {'UsageStrategy': 'use-capacity-reservations-first'}}}
2024-01-12 10:05:50,022 - [slurm_plugin.instance_manager:_update_slurm_node_addrs_and_failed_nodes] - INFO - Nodes are now configured with instances: (x1) ["('gpu1x-gpu1-cpu4-od-dy-p21xlargeod-2', EC2Instance(id='i-0679xxx', private_ip='<IP_ADDRESS>', hostname='ip-10-0-1-36', launch_time=datetime.datetime(2024, 1, 12, 10, 5, 49, tzinfo=tzlocal()), slurm_node=None))"]
2024-01-12 10:05:50,022 - [slurm_plugin.instance_manager:_store_assigned_hostnames] - INFO - Saving assigned hostnames in DynamoDB
2024-01-12 10:05:50,055 - [slurm_plugin.instance_manager:_store_assigned_hostnames] - INFO - Database update: COMPLETED
2024-01-12 10:05:50,055 - [slurm_plugin.instance_manager:_update_dns_hostnames] - INFO - Updating DNS records for XXXXXXXXXXXXXXXX - pcluster.pcluster.
2024-01-12 10:05:50,433 - [slurm_plugin.instance_manager:_update_dns_hostnames] - INFO - DNS records update: COMPLETED
2024-01-12 10:05:50,434 - [slurm_plugin.resume:_resume] - INFO - Successfully launched nodes (x1) ['gpu1x-gpu1-cpu4-od-dy-p21xlargeod-2']
2024-01-12 10:05:50,435 - [slurm_plugin.resume:main] - INFO - ResumeProgram finished.

Hi @enrico-usai
Thank you!
I'm using 3.7.2. I just retrieved the console logs and I don't see any error.
The last 10 lines:
<13>Jan 12 13:00:45 user-data: Recipe: aws-parallelcluster-platform::sudo_config
<13>Jan 12 13:00:45 user-data:   * template[/etc/sudoers.d/99-parallelcluster-user-tty] action create[2024-01-12T13:00:45+00:00] INFO: Processing template[/etc/sudoers.d/99-parallelcluster-user-tty] action create (aws-parallelcluster-platform::sudo_config line 15)
<13>Jan 12 13:00:45 user-data: [2024-01-12T13:00:45+00:00] INFO: template[/etc/sudoers.d/99-parallelcluster-user-tty] created file /etc/sudoers.d/99-parallelcluster-user-tty
<13>Jan 12 13:00:45 user-data:
<13>Jan 12 13:00:45 user-data:     - create new file /etc/sudoers.d/99-parallelcluster-user-tty[2024-01-12T13:00:45+00:00] INFO: template[/etc/sudoers.d/99-parallelcluster-user-tty] updated file contents /etc/sudoers.d/99-parallelcluster-user-tty
<13>Jan 12 13:00:45 user-data:
<13>Jan 12 13:00:45 user-data:     - update content in file /etc/sudoers.d/99-parallelcluster-user-tty from none to 584e08
<13>Jan 12 13:00:45 user-data:     --- /etc/sudoers.d/99-parallelcluster-user-tty       2024-01-12 13:00:45.091170156 +0000
<13>Jan 12 13:00:45 user-data:     +++ /etc/sudoers.d/.chef-99-parallelcluster-user-tty20240112-5573-morzlt     2024-01-12 13:00:45.091170156 +0000
<13>Jan 12 13:00:45 user-data:     @@ -1 +1,2 @@
<13>Jan 12 13:00:45 user-data:     +Defaults:ec2-user !requiretty[2024-01-12T13:00:45+00:00] INFO: templ        2024-01-12T13:01:11+00:00

Hi @diegoamoros
I don't think these logs are complete, here I see  sudo_config recipe execution, but it is just an initial step of the configuration flow.
You should try to retrieve the log after a bit, to see if there are updated data. Please attach the entire log.
The other thing you can check is networking. Are you using the same subnet for p2 and c5a?

Hi @enrico-usai
Yes, these logs are complete.
Attached you can find the entire console-output.
Thank you!
fullLog.txt

Hi @diegoamoros
I've looked through the attached log and it still looks truncated (it is possible that the console log itself did not record everything). I see no errors present in the log and it seems to abruptly cut off.

Hi diegoamoros,

Hi @diegoamoros, are you still running into this issue? Were you able to retrieve the logs?

Hi @judysng. I am sorry. I have been busy and haven't been able to continue with the issue, but I will try to retrieve the logs shortly.

We have encountered the same issue. The drivers in the default AMI for PC 3.7.2 is too new for p2 (K80s)
AWS ParallelCluster AMI for ubuntu2204, kernel-5.15.0-1026-aws, lustre-<IP_ADDRESS>1.29, efa-2.5.0-1.amzn1, dcv-2023.0.15487-1, **nvidia-535.54.03**, cuda-12.2.20230626
https://www.nvidia.com/download/driverResults.aspx/206014/en-us/
K80s are not supported
Would have to build your own AMIs if we have to use p2 in 3.7.2

We have encountered the same issue. The drivers in the default AMI for PC 3.7.2 is too new for p2 (K80s)
AWS ParallelCluster AMI for ubuntu2204, kernel-5.15.0-1026-aws, lustre-<IP_ADDRESS>1.29, efa-2.5.0-1.amzn1, dcv-2023.0.15487-1, **nvidia-535.54.03**, cuda-12.2.20230626
https://www.nvidia.com/download/driverResults.aspx/206014/en-us/
K80s are not supported
Would have to build your own AMIs if we have to use p2 in 3.7.2

Thanks  @roshantm !!
Would it work on an earlier version of parallel cluster?


Allow to pass networks while creating k8s nodepool

Use-cases
When creating a new nodepool, it is possible to define the LAN IDs which should be attached to the worker nodes. Unfortunately, it is not possible to also define the networks and gateways for them.
Therefore, when creating a new nodepool, we have to first create the nodepool without the attached private LAN, wait for it to become ready and after that attach the private LAN which results in recreating the nodepool (which takes some time depending on the size of the nodepool).
Attempted Solutions
Nothing so far.
Proposal
Allow to also define the networks to be routed to the LAN while creating the nodepool.
I know, the command line might be really cluttered doing it that way. And you might also have to think about a way how to define the networks for each LAN to be attached.
One quite ugly option to define it would be to allow giving --lan-ids multiple times (maybe then renamed to --lan-id as it is only a single LAN) listing the LAN ID followed by the networks and gateways. Something like the following:
ionosctl k8s nodepool create \
    --datacenter-id DATACENTER_ID \
    --cluster-id CLUSTER_ID \
    --name NAME \
    --lan-id "1|<IP_ADDRESS>/9,<IP_ADDRESS>/10,<IP_ADDRESS>/12|<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>" \
    --lan-id "2|<IP_ADDRESS>/16|<IP_ADDRESS>"

Another approach might be to define the properties in a config file which also supports nesting (i.e. JSON or YAML) and then simply provide the config file on the command line.
Example:
ionosctl k8s nodepool create /path/to/options.json

options.json:
{
    "datacenter-id": "DATACENTER_ID",
    "cluster-id": "CLUSTER_ID",
    "name": "NAME",
    "lan-ids": [
        {
            "id": 1,
            "networks": [
                "<IP_ADDRESS>/9",
                "<IP_ADDRESS>/10",
                "<IP_ADDRESS>/12"
            ],
            "gateways": [
                "<IP_ADDRESS>",
                "<IP_ADDRESS>",
                "<IP_ADDRESS>"
            ]
        },
        {
            "id": 2,
            "networks": [
                "<IP_ADDRESS>/16"
            ],
            "gateways": [
                "<IP_ADDRESS>"
            ]
        }
    ]
}

The config variant might be also useful for the other create commands.

Firstly, thank you for your detailed issue. I have also thought of this config/options json file approach. In my opinion it's a very streamlined approach and it's a pretty clear/structured way to define resources.
However, have you considered IaC tools such as https://github.com/ionos-cloud/terraform-provider-ionoscloud/ or https://github.com/ionos-cloud/module-ansible ? They are designed for use cases such as the one you describe
Regarding the --lan-id approach, it is not the most user-friendly and I'm not a big fan of it, but it could be a feasible workaround.
Thanks for opening the issue, I'll update this thread as soon we've made a decision regarding this proposal, have a nice day!

Yes, we've already evaluated Terraform. Unfortunately, it doesn't exactly fit our use-case as we just want to create Kubernetes clusters and nodepools without actually keeping the state somewhere. Therefore we want to use ionosctl for that.

I just tested the new functionality but for me it is not working.
I used the JSON returned by ionosctl k8s nodepool create --json-properties-example, dumped it to a file and modified some values to match our setup. But it seems like the file is not used at all as ionosctl complains about an unsupported CPU family "AMD_OPTERON" even if I specified "INTEL_SKYLAKE" in the file.
Removing the cpuFamily property from the file and manually specifying it as --cpu-family INTEL_SKYLAKE works and then confirmed my guess about the file not being used at all as everything in the file is just ignored. For example, the nodepool does not contain the amount of nodes, the configured CPU cores, RAM, HDD size, etc.


Revise appearance for feature-state shortcode

Change how feature-state shortcodes look. The new look makes them stand out more, and makes it easier to use a different style in the future. We can build on this to, eg, color alpha and beta feature state notices with a special outline.
This PR also deletes a legacy CSS file.
/area web-development
Current example | Preview

/approve


Remove country - Netherlands Antilles

Netherlands Antilles - no longer exists

I see you added Sint Maarten but didn't add the flag. Guess I'll have to do that.
Thank you for contributing!

Turns out the flag actually does exist, not sure how 🤷♂

Yep, I found that the flag did exist, when I added the country. So all good 👍


HTTPS support

Nowadays, communication between client and server is sensitive, and a server should accept HTTPS communications, especially if some sensitive information is transported (e.g. a password, users use to use the same password everywhere so scanning the HTTP signalserver communication would permit e.g. an attacker to access the email account of the user).
Related to https://github.com/bavc/qctools/pull/242#issuecomment-270956925

It will be cool to have it. I need to add more serious web server + installing cert.  So once we start really thinking about putting this on the web server, I will add https.


Unable to tap login or cancel

I am running on stock touchwiz 4.4.2 rom..
I flashed Nanodroid microG..
But I am not able to tap Login or Cancel in microG login setup wizard...
here is the logcat taken with SysLog app https://drive.google.com/file/d/1k8SIHMkr0f1gy18fB5qR4lEm5JjghXBV/view?usp=drivesdk ..
Thanks..

It is a known issue. Either use an old version of microG (e.g. v2.4) and update it later, or connect an external keyboard and navigate the buttons with TAB key.

It is a known issue. Either use an old version of microG (e.g. v2.4) and update it later, or connect an external keyboard and navigate the buttons with TAB key.

Sir...thanka for reply...
I use Nanodroid package for microG...
when I replaced the gmscore with 0.2.4 , It cant spoof correctly... Maybe @Setialpha of Nanodroid is making some changes to GmsCore...
Can you please modify the 0.2.4 version of GmsCore to spoof correctly?....
with v0.2.4, I can login but it cant spoof correctly ....

You can use v0.2.4 only to log-in first and then update it to the newest release which can be downloaded directly from this GitHub repository. Of course, you will not be able to use the NanoDroid package afterwards because that one uses their own versions of microG.

You can use v0.2.4 only to log-in first and then update it to the newest release which can be downloaded directly from this GitHub repository. Of course, you will not be able to use the NanoDroid package afterwards because that one uses their own versions of microG.

With official microG latest version also not spoofing correctly since when I install Inbox by Gmail app , it warns to update google play services... but with Nanodroid microG it is not the case...

With official microG latest version also not spoofing correctly since when I install Inbox by Gmail app , it warns to update google play services... but with Nanodroid microG it is not the case...

My guess would be that you probably do not have the Play Store app installed.

edit:- sir Since i am new to microG .... Can you please suggeat a flashable package that has all apps required for microG like in NanoDroid ...

I do not use any all-in-one packages, but for a minimalist setup I would recommend to download Services Core and Services Framework Proxy from https://microg.org/download.html, download PlayStore from https://www.apkmirror.com/apk/google-inc/google-play-store/ (and rename the file to something short with no spaces), and then copy the three files to /system/priv-app/. I usually do this using the file manager in TWRP, or with adb push.
Of course, you will also need to have signature spoofing support in your ROM, either built in or patched. I like to use the NanoDroid patcher, but if it does not work (and I had this often happen with older versions of Android), then try to use Tingle (https://github.com/ale5000-git/tingle).
If you need location backends, etc., then you can just download and install them later from FDroid. There are also ways to work around without the official Play Store app, but I have had too many issues with apps which simply need it to work.

With official microG latest version also not spoofing correctly since when I install Inbox by Gmail app , it warns to update google play services... but with Nanodroid microG it is not the case...

My guess would be that you probably do not have the Play Store app installed.

edit:- sir Since i am new to microG .... Can you please suggeat a flashable package that has all apps required for microG like in NanoDroid ...

I do not use any all-in-one packages, but for a minimalist setup I would recommend to download Services Core and Services Framework Proxy from https://microg.org/download.html, download PlayStore from https://www.apkmirror.com/apk/google-inc/google-play-store/ (and rename the file to something short with no spaces), and then copy the three files to /system/priv-app/. I usually do this using the file manager in TWRP, or with adb push.
Of course, you will also need to have signature spoofing support in your ROM, either built in or patched. I like to use the NanoDroid patcher, but if it does not work (and I had this often happen with older versions of Android), then try to use Tingle (https://github.com/ale5000-git/tingle).
If you need location backends, etc., then you can just download and install them later from FDroid. There are also ways to work around without the official Play Store app, but I have had too many issues with apps which simply need it to work.

Finally with your suggesstion, microG is working sir.....
Thanks.. Can you please give your XDA user name..

Finally with your suggesstion, microG is working sir.....
Thanks.. Can you please give your XDA user name..

It is good to hear that :relaxed:.
My username on XDA is tomasz86, but I am not a very active user (read: I visit the forums once or twice per week). If you need urgent help, you will be better opening an issue here (or asking others on XDA).

DroidGuard

https://github.com/microg/android_packages_apps_GmsCore/issues/214
I do not use any apps that need it, so I also do not install the DroidGuard app. I would recommend installing it only if you absolutely have to.

FakeStore, BlankStore

https://android.stackexchange.com/questions/174635/fakestore-blankstore-gms-microg-unifiednlp-whats-best-for-android-without
Blank Store is deprecated, and FakeStore is only to appear as if you had the Play Store installed in your system (but you actually do not). None of them is needed if you use the official Play Store app.

Is Maps api files are needed?

I cannot really help with this one because I do not use Google Maps.

DroidGuard

https://github.com/microg/android_packages_apps_GmsCore/issues/214
I do not use any apps that need it, so I also do not install the DroidGuard app. I would recommend installing it only if you absolutely have to.

FakeStore, BlankStore

https://android.stackexchange.com/questions/174635/fakestore-blankstore-gms-microg-unifiednlp-whats-best-for-android-without
Blank Store is deprecated, and Fake Store is only to appear as if you had the Play Store installed in your system (but you actually do not). None of them is needed if you use the official Play Store app.

Is Maps api files are needed?

I cannot really help with this one. Where I live Google Maps is useless and I have to use other map providers anyway, so I have never needed these.

Thanks for clarification...
Is it necessary to put those GmsCore, GsfProxy, Phonesky to /system/priv-app?
Since in microG xda page, Ma-R-Vin said to install as normal apps....
My device is running on 4.4.2 KitKat....
Thanks

Is it necessary to put those GmsCore, GsfProxy, Phonesky to /system/priv-app?

GmsCore has to be in /system/priv-app in Android 7+ in order to use location backends. In older versions of Android it should not matter. GsfProxy can probably go to /system/app. Phonesky (the Play Store) has to be in /system/priv-app, unless the OS is Android 4.3 or older, where everything goes to /system/app. I just put all three in /system/priv-app for the same of simplicity and to avoid any potential system permissions related issues.

I have a doubt..
How GmsCore of microG and GooglePlayStore use its libraries if they are in /system/priv-app?
Since in Nanodroid and OpenGapps there are separate libs are placing in /system/lib.....
Thanks


Remove thatMark and sourceMark from ProcessedTargetsContext

Depends on https://github.com/cursorless-dev/cursorless/pull/1474

Checklist

[ ] I have added tests
[ ] I have updated the docs and cheatsheet
[ ] I have not broken the cheatsheet

Current dependencies on/for this PR:

main

PR #1473

PR #1474

PR #1475   👈

PR #1476

This comment was auto-generated by Graphite.

@pokey queued this pull request to merge with Graphite.

Graphite failed to merge this pull request for an unknown reason. Try your merge again, or report a bug if you see this consistently.


Update basics episode

Work in progress - do not merge yet. Is out here to get comments and to see what I am up to.

Ready for review.

Thanks for review! Merging.


[BUG] Network interfaces down after boot on non-default MTU

Describe the bug
After boot if MTU has been set to something other than 1500, and network interface doesn't support MTU of 1500 network interfaces will fail to be brought up.
To Reproduce
Steps to reproduce the behavior:

Install Harvester (MTU for mgmt-br and mgmt-bo has to be changed manually via tty2 during install - setting it via MTU field doesn't change this value)
On first boot networking will be down

Expected behavior
MTU should be set correctly to mgmt-br and mgmt-bo interfaces and they should be brought up
Environment

Harvester ISO version: harvester-v1.2.1-amd64.iso
Underlying Infrastructure: VM on OpenStack, max MTU of 1442

Additional context
It seems that MTU is not applied to mgmt-bo and mgmt-br (ip link shows 1500 instead of 1442, even though it's set in /etc/sysconfig/network/ifcfg-mgmt-br and ifcfg-mgmt-bo).
The simplest way to apply this change is to call wicked ifup all twice (log output from first and second call attached below).
Other way, purely using ip - without using wicked is to do this:
ip link set mgmt-br mtu 1442
ip link set mgmt-bo mtu 1442
ip link set ens3 up
ip link set ens3 down

I've tried adding ip link set $INTERFACE mtu 1442 to pre-up and post-up in wicked scripts, and it does correctly apply MTU to interfaces, but ens3 has to be still toggled on and off for interfaces to be brought up.
first.log
second.log

My awful fix is to add ip link set $INTERFACE mtu 1442 as pre-up action to wicked:setup_bond.sh and wicked:setup_bridge.sh + add wicked ifup all to stages.network.commands in /oem/90_custom.yaml, but it seems to me that this is a problem with wicked -  as it tries to bring ens3 interface without applying modified mtu first:
kernel: ens3: mtu greater than device maximum
kernel: mgmt-bo: (slave ens3): Error -22 calling dev_set_mtu

It seems the installer is only adding the MTU into the bridge configs but not into the actual configuration file of the
interface.
I fixed this with adding MTU=1400 to the ifcfg-ens18 file in /etc/sysconfig/network/.

cc @mingshuoqiu @starbops

Harvester does not nested virtualization for production.
In the installer, it allows to set the MTU for mgmt bond interface https://github.com/harvester/harvester-installer/blob/473895517c8304182ef85e5d26c64b8f579d03e3/pkg/config/config.go#L81, but not touching the bonded individual NICs.
In this example, the Harvester Node is backed by an OpenStack VM which is using MTU 1442. The fist issue/challenge is that before Harvester installer program runs, the OS needs to use MTU 1442 to set the NIC and let the NIC up. Per @lotherk 's solution, using a network config to guide the OS. This is the feasible solution. Sure, @UninspiredNickname 's solution can also work.
We can add @lotherk 's solution to https://docs.harvesterhci.io/v1.3/troubleshooting/index first.
On the other hand, if the network supports JUMBO frames, and user sets the mgmt interface with MTU 9000 but the underlayer NICs are still using the default MTU 1500, this may be an issue, needs double check.


SDL2 Cmake not finding freetype

I'm using the cmake files provided with the SDL_ttf download 2.22.0 to link SDL2 to my custom game engine. But when adding the SDL libraries to my executable using the add_subdirectory function my system tells me that I need to go install freetype. I thought that SDL_ttf included freetype for portability?

message.txt

Reading your log, it is actually configuring SDL2_ttf's vendored libfreetype, but fails to read external/freetype/builds/unix/configure.raw.
CMake Error at src/ThirdParty/SDL2_ttf-2.22.0/external/freetype/CMakeLists.txt:171 (file):
  file STRINGS file
  "C:/Users/trump/Documents/Wolverine-Engine/src/ThirdParty/SDL2_ttf-2.22.0/external/freetype/builds/unix/configure.raw"
  cannot be read.

The file is ascii.
I just verified SDL2_ttf 2.22.0's tarball and the file is present.

Reading this CMake issue, and this code or origin, perhaps the file does not exist on your system or there is a permissions problem?
Remove everything, and extract SDL2_ttf again. Eventually to another directory and do add_subdirectory("C:/tmp/SDL2_ttf-2.22.0" SDL2_ttf) instead.

Figured out this issue, I was needing to set the SDL2TTF_VENDORED cmake variable to true before adding the subdirectory. I was having the same problem with SDL2 Mixer, where I needed to set the SDL2MIXER_VENDORED variable to true and then download all of the external libraries/packages into my project by running the "download.sh" file in the "externals" folder.


Support for Argon2 KDF

I think it would be useful to have the Argon2 KDF contained within OpenSSL. It's the winner of the PHC and the recommendation of OWASP for new applications.
There is reference code available that is CC-0 licensed. So I'm guessing this is incompatible with OpenSSL and would require a rewrite?
Since I've poked around the last few days in the KDF code, I'd like to give this a shot as well and provide a PR.

Look at https://datatracker.ietf.org/doc/draft-irtf-cfrg-argon2/ for a text description, sample code (BSD license so okay to use as a starting point) and test vectors that can be used in the test suite.

Hi @richsalz, thanks for the pointer. So I guess this would be something that is of interest for inclusion?
For efficient computation of Argon2, the ability to run concurrent code is necessary. While OpenSSL abstracts some threading functions away from their OS libraries (such as NPTL), I do not see a way to create and wait for threads. Do you have an idea on how I should approach this?

Don't mistake my giving a link for general interest :)  @mattcaswell can best answer the thread questions, but if argon2 requires threads and will not work without them, then it's of much less interest.

I see :-)
Well, Argon2 doen't strictly require threads in the sense that it isn't computable without them. However, it is designed such that internally it has comutation that is entirely data-independent (and, thus, perfectly parallelizable). Of course this can be sequentialized, but would essentially mean a factor of n slowdown (this is the parametrizable "lane" paramter of Argon2). And slow means useless in that context (because an attacker obviously will use a highly optimized version that does make use of the parallelizability).
I do think it's something that'd be nice in OpenSSL (especially since it's becoming popular quickly), but before I'm doing actual work, I'd then be waiting for further input on this.

Just FYI: cryptsetup is one of the Argon2 users already - LUKS2 uses Argon2 as a KDF.
For now we use either system libargon2 (if available) or embedded reference implementation. If we can use OpenSSL directly, it would be much simpler (we can already use PBKDF2 from OpenSSL).
Just it should be the fully threaded version - while libargon2 code supports compilation without threads, this does not make much sense - the function has 3 costs: iterations (cpu cost), memory cost (it is memory-hard function) and parallel cost (threads). Code should support all of them.

Hi! First of all, thank you for your hard work and congrats on the 1.1.1 release. The release blog post says

The OpenSSL team will now be moving our focus to the next release which will see us developing a new FIPS module.

Does this mean that adding support for Argon2 will be postponed?

Does this mean that adding support for Argon2 will be postponed?

No, not necessarily. The master branch is currently open for new features. The primary focus of the dev team is the FIPS module but that doesn't mean we won't merge other stuff (in much the same way that the primary focus for the last release was TLSv1.3, but a load of other features went in too). However since this isn't a priority item it is more likely to get merged if someone contributes a PR.

Hey @mattcaswell -- could you maybe clarify on one part: Argon2 only makes sense when it can utilize concurrent computation. It was my understanding that this was the major blocker to its inclusion and it's also the reason why this pretty much came to a screeching halt even before anyone had written a line of code. Has this changed?

Hey @mattcaswell -- could you maybe clarify on one part: Argon2 only makes sense when it can utilize concurrent computation. It was my understanding that this was the major blocker to its inclusion and it's also the reason why this pretty much came to a screeching halt even before anyone had written a line of code. Has this changed?

No, my comment above was only meant to imply that the master branch is currently open to new features (whereas it has been frozen to features for sometime until yesterday). The concurrency issue would still need to be resolved. I don't have a good answer for that one.

@johndoe31415, @mattcaswell The reference implementation of Argon2 supports parallelism. Is there something I'm missing here that prevents using their code?

Even if there is a reference implementation, it still needs work to get integrated in the openssl ecosystem. That will happen in form of a PR, regardless of who does it.
So now it only takes someone making it enough of a priority. That could be you.

The reference implementation of Argon2 supports parallelism. Is there something I'm missing here that prevents using their code?

The creation and destruction of threads inside the library is not something we currently do. There is no thread pool mechanism to support that and I'm not convinced we would want to include one.

Of course the other problem with Argon2 is that AFAIK it is not standardised. The internet draft for it seems to have expired. It is a requirement for OpenSSL that all algorithms are standardised.

... or at least going steadily toward standardisation (see our TLSv1. 3 effort)

According to my information, there is still an intent to work on Argon2 RFC (and I asked authors again).
The reference implementation supports no threads option, but for real-world implementation you will need to support threads or some equivalents. But as the first step I think it can be implemented without thread support.

Of course the other problem with Argon2 is that AFAIK it is not standardised. The internet draft for it seems to have expired.

That said, the CFRG document is in RG Last Call (if you look at the list archives), which indicates an intent to advance to publication (assuming no critical flaws are found in the review period).  The CFRG chairs are a bit understaffed at the moment (and looking for help), so it is unsurprising that documents are only progressing slowly.

Argon2 RFC draft is in a new revision online: https://datatracker.ietf.org/doc/draft-irtf-cfrg-argon2/

Argon2 is already mature enough, 5 years, it's a time to get it on board!

I don't believe the question is regarding the maturity of Argon2 itself. The problem is with the lack of threading support of OpenSSL. Something that the currently open PR, #9444 adds as well. Arguably, the same goes for scrypt with p > 1 in the current implementation.
Anything that can be run in parallel (i.e., non-dependent computation) can trivially be sequentialized as well. However, it makes no sense because then the attacker has the full advantage and the honest implementation the disadvantage. Maybe counterintuitively, KDFs that run deliberately slow using an oftentimes parametizable work factor need to have fast implementations so that you're hurting your own performance but also that of the potential adversary equally much. You don't want to be the only one with a slow implementation while the attacker can make full use of parallel implementations.

This is currently being progressed in #12255 and #12256.

I don't believe the question is regarding the maturity of Argon2 itself. The problem is with the lack of threading support of OpenSSL. Something that the currently open PR, #9444 adds as well. Arguably, the same goes for scrypt with p > 1 in the current implementation.

Ignoring compatibility, you wouldn't want to remove Scrypt because it's vastly better than PBDFK2.  However, Argon2 has better sidechannel resistance and is more unfriendly to GPUs, FPGAs, and ASICs than Scrypt [§1]....

Maybe counterintuitively, KDFs that run deliberately slow using an oftentimes parametizable work factor need to have fast implementations so that you're hurting your own performance but also that of the potential adversary equally much. You don't want to be the only one with a slow implementation while the attacker can make full use of parallel implementations.

I think the situation is more nuanced than that.  I've been running into difficulty getting optimized versions of Argon2 because it's not popular enough. But I can't even get password managers to switch away from PBDFK2 :scream:  because Argon2 is not widely available in their favorite crypto library (hence all the external bikeshedders).
But I also agree that p > 1 on a serial implementation is a footgun :thinking:.  What if you limited support to Argon2id with a p = 1?  Then it any usage of Argon2 would be strictly more secure than the alternatives and discussion/implementation of threading can be deferred.

Hello! As an onlooker from outside who is excited about Argon2 KDF support, what action is currently needed on PRs #12255 and #12256 ? Are we just waiting for the 3.0 stable release before considering merging these PRs, or is there more work to be done?
Big shoutout to @ckalina for implementing the two PRs. :smiley: :tada:

Are we just waiting for the 3.0 stable release before considering merging these PRs, or is there more work to be done?

Basically everything is on hold until after 3.0 stable. So those PRs will have to target 3.1.

Understood, thanks for the update @mattcaswell !

Just FYI - released RFC for Argon2 is here: https://www.rfc-editor.org/rfc/rfc9106.txt

We really need Ardon2id!

Argon2id is part of the proposed code (and I successfully tested cryptsetup with patched OpenSSL 3.0.0).
The problem is that @ckalina has apparently no time to finish this to the state when merge request is acceptable ( #12255 and #12256).

Both MRs (threads support #12255 and Argon2 #12256) are now rebased, I hope it is not going to stay there forever again :-) Please review it or comment there.

Oh yeah, we have Argon2 support in OpenSSL 3.2.0. Closing this!


relogin for checking issue

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign ashishsatiso
You can assign the PR to them by writing /assign @ashishsatiso in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: sumitsheokand
To complete the pull request process, please assign ashishsatiso
You can assign the PR to them by writing /assign @ashishsatiso in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mderazon, sumitsheokand
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [mderazon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mderazon, sumitsheokand
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [mderazon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


First time minting on Statemine

Hey I'm checking minting for Statemine and this is where I land after clicking on Multiple NFTs
Then I have a button on the left back to onboarding.
Not sure if it's glitch or intentional but even as inner KodaDot I'm confused, why it's landing there?
Where is simple mint for Statemine?
cc @EthVlad

It's follow-up from this

https://github.com/kodadot/nft-gallery/issues/5987
#5939

Hey I'm checking minting for Statemine and this is where I land after clicking on Multiple NFTs
Then I have a button on the left back to onboarding.
Not sure if it's glitch or intentional but even as inner KodaDot I'm confused, why it's landing there?

here it drives me to massmint onboarding

Where is simple mint for Statemine?

i thought you guys were waiting to release it following a marketing campaign or something similar, but i did find strange because i remember this PR: #6251. last monday i even asked viki on Discord about why we didn't release classic statemine minting yet

we didn't release classic statemine minting yet

we can do

#5939

@yangwao pr merged close this issue


Using glm::perspective with z range [-1..+1] when Vulkan uses [0..+1]

I am just curious how glm's perspective method can work with Vulkan in your examples.
I mean, as long as your model stays within 0..1 of the transformed NDC depth range, everything should be okay, but as soon as NDC z transforms to anything within [-1..0] it will not be visible anymore in Vulkan, where it still would with OpenGL.
Currently I don't see any option in glm to switch to using Direct3D's/Vulkan's compatible clip space/NDC space.
See the section 23.2. Primitive Clipping

There is a new define in GLM for this called GLM_DEPTH_ZERO_TO_ONE.
I'll be updating GLM and add this to my examples.

fyi : as of glm 0.9.8 this define is called GLM_FORCE_DEPTH_ZERO_TO_ONE

Thanks for the info! Closing this now.


Added ServiceNow Integration.

We as a university use ServiceNow for monitoring and managing incidents and problems. This merge would add ServiceNow integration allowing for the automated creation of Incidents via the ServiceNow rest api. The required fields may not be entirely required outside of our institution.

Could you add documentation and update https://github.com/Yelp/elastalert/blob/master/elastalert/config.py#L47?

I have added the documentation and the alert mapping.


Cancel download (and resolve) when controller deletes object

Up until now, if the controller specifies a content tree, EVE will start  downloading it. If the content-tree is deleted, then the objects (ContentTreeStatus) will be deleted, but the downloader has a single goroutine per object and that will keep on running until the download succeeds or fails.
That uses bandwidth for no reason.
The approach here is a bit convoluted, since we need to make sure that we cancel the context for the current download and avoid having a late cancel of download 1 affect download 2 (recall, there is automatic retry etc). Hence when an operation starts, a channel is created and sent back to the top level handlers (sent over the receiveChan). The top level code sends a notification on that channel when it needs to cancel (and the actual code down in syncop etc does a normal cancel of the context, which causes the underlying transport code to clean up.)
Even though the resolve (of a OCI tag) doesn't download lots of bytes, it is still retrying etc. So applying the same cancel pattern there.
The difference between the two cases is that for the download there is an interlock between volumemgr and downloader (using a RefCount=0 in DownloaderConfig resulting in Expired=true in DownloaderStatus, and finally a delete/unpublish of the DownloaderConfig). Thus we also use a RefCount=0 at the top level modify handler  to also trigger a cancel.
To avoid retrying when an operation has been cancelled we return a "cancelled" boolean . That is used to have the log messages indicate vs. not a retry of the error.

Using a channel to signal a goroutine thread to cancel is the right thing to do. I do have a few questions:

are there concerns about two distinct content trees needing the same blob, one gets cancelled, cancelling the download, and the other is left hanging? Or will RefCount handle that correctly?

Even both are depending on downloading the same object, then the delete of the ContentTree object should presumably not cause the RefCount on that blob to drop to zero, hence the downloader should not see a RefCount=0 to make it cancel.
But definitely don't have a test case for that.
But cancellation shouldn't change this; if RefCount in DownloaderConfig drops to zero today, then the download will not take place.

are there possibilities of race conditions? E.g. download Tree abc, it starts, cancel it, start it again. Are the sequence of events and ownership handled correctly for it?

That is why I have that complex passing back the currentCancelChannel over the receiveChannel. Ensures that the cancel applies to the right instance/try/whatever of the download.
In practice that will not happen since we the most we do for a given per-object go-routine in the downloader is to retry downloading the same object after a failure.

I don't think it is necessary to have a cancel on the hash resolution. As you said, it is tiny, and happens so quickly that it is unlikely to get cancelled in time. As long as it works, though, and is the same design as the rest, it cannot hurt.

Yeah that's my point. And it made we find a bug where we left a ResolveConfig hanging around forever.

There are a few places where there are multiple channels. Would it be better with a single channel which can deliver different kinds of messages, i.e. a standard message-type wrapper? I don't think it really matters, at first thought, but worth contemplating.

The receivers/readers are different.

For a cancellation channel, why would we not just use the standard "go-way" of doing it, with a cancellable context?

That is what is done once we the notification is sent. I didn't feel comfortable having the main goroutine call the cancel function directly. Felt like too much data sharing compared to using a channel to send an event.

Thanks for the detailed responses. That pretty much covers it. Complexity always has me concerned, but this is pretty complex already anyways (partially due to work I have done :-) ). Let's go for it.

It is indeed pretty tricky (any chance this can be more unit tested at all?) but seems legit -- LGTM and let it test

I would like to have some automated unit tests but we don't have sufficient scaffolding to create the environment needed to be able to start a download from some source, and then cancel it).
It has been tested manually using an actual device. One should be able to come up with some tests using Eden (the trick is that the download has to be slow enough so that the test script can observe that it started (progress > 0) before cancelling it, and it can't have finished when the cancel happens. BUT the cancel isn't observable since the only way to do it is to delete the (app instance or) content-tree from the config. Maybe Eden can observe the ContentTree info message after the delete, or verify that the network rates on eth0 drop to near zero?

Thanks for the details comment @eriknordmark -- I was also thinking Eden -- @sadov any chance you can file a tracker story with the details so we can build it on the Eden side?


Error Catching for Retry Logic for Logger

The issue here is that a number of steps repeatedly log to the console to show the ⠋ type loading pattern, which results in repeated unnecessary requests to the logging endpoint. This is timing out presumably due to rate limiting or something like that. The best option here is to only send those log messages once, as repeated logs is completely unnecessary

This is also resolved as part of 1.0.8 where we only log a single message for those repeated log messages