Check for duplicate records

Duplicate records can be a problem, could check for this? E.g. check unique rows, or make a set? Could be nasty for a large dataset though? Easy enough to experiment with some random data (presumably worst case scenario)

function
sklearn checker
pandas df accessor

Hello, I would like to work on this. Can you elaborate more on what is expected?

@bhoomikaagrawal16 hello, and thanks for thinking of contributing!
I guess there's at least a couple of scenarios:

Duplicate rows in any dataset -- not a good thing.
Rows in data that appeared in training -- really not good.

There are 3 place I put things:

Functions in a module like duplicates.py -- I would start here
sklearn transformers, both supervised and unsupervised, in ``sklearn.py` (usually trying to use functions from whatever modules)
pandas accessors, in pandas.py (usually trying to use functions from whatever modules)

So a good place to start might be to create a module with an experimental 'duplicate detecting' function. It needs to be fast enough to work reasonably fast on at least 100k records, as a rule of thumb.
Write simple docstrings and doctests please (see the other modules).
Does this help? Let me know if you need more.


Section rc specific

Pull request made for transparency, still more to be done I believe?

@talledodiego Thanks for your comments. I forgot to communicate what I intended with this pull request, and thus I have created unneccessary work for you - sorry for that. What I have done is to define the class RectangularSection(GenericSection), and I pasted in your code from earlier so I could easier look at what you did. What I have done is basically define and write some calculations in calculate_gross_section_properties() for this class (which might be not necessary as of yet). What more do we want in this class? Maybe some dunder-classes?

Any idea why the values n_max_marin and res_marin.n is both equal to 0.0?

Any idea why the values n_max_marin and res_marin.n is both equal to 0.0?

I think it is because your rectangular section is a rectangle of homogeneous material. If you use concrete (that in this stage is imagined with zero tensile strength) there is no way it can take a tensile force. Therefore the value zero for both marin and fiber integrators.

Hey there @sshaave !
During the last days me and @mortenengen worked on adding a further "specific section" that is a circular "section".
After some thinking we concluded that probably the wrapper class should not be a wrapper to a Section but a wrapper to a geometry. Saying it differently with these special methods we create geometries (or compound geometries) that then can be assigned to a GenericSection.
PR #207 does exactly that. Specifically I included a CircularGeometry that is a SurfaceGeometry derived class that permits to get a concrete surface to which apply some reinforcement. In the case of the circual geometry the pattern of reinforcement is easily inserted with the new function add_reinforcement_circle.
I propose to do the same in this PR for the rectangular case creating a RectangularGeometry that as you developed here takes as arguments b, h and the material.
It is better in our opinion to wrap around geometry and not section to better highlights the responsibilities here: with geometry we create the geometries, while we use the geometries in sections for doing the computations.
In the same PR #207 you can find also the relevant tests that I implemented for this new geometry.
What do you think? Are you willing to try modifying your code according to this suggestion?
Let me know if I can give you any further assistance on this.

Hello. I have looked through #207, and while I do not understand the practical differences between the approches, I am pleased to see implementations for other ubiquitous cross sections. I don't have the capacity to continue this work this year, and I have struggled to find time for structuralcodes lately. Feel free to rewrite the code for rectangular cross section/geometries.

@sshaave @mortenengen I included in this PR the homogeneous RectangularSurface.
We will think in a future PR if there is the need for a RCRectangularGeometry. This PR can be considered completed.
@mortenengen ready for your review.


Memory leaks during key creation and signing

Hi,
we are currently developing a crypto api and found some memory leaks with valgrind during key creation with pqc algorithms.
The leaks we found:

During EVP_PKEY_keygen_init in  oqs_kmgmt.c, line 422
gctx->oqs_name = OPENSSL_strdup(oqs_name);
During EVP_PKEY_generate in oqsprov_keys.c, line 618
ret->tls_name = OPENSSL_strdup(tls_name);
During EVP_DigestSignInit from ASN1_item_i2d in oqs_sig.c
Not able to fix it, but we assume its coming from line 156: ctx->aid_len = get_aid(&(ctx->aid), ctx->sig->tls_name);, from a not correctly freed aid.

We started with version 0.4.0 of the oqs-provider, when we saw that there are memory leaks fixed on commit, we switched to the current main version. The leaks listed above also occurred there.

Yes, no problem, I will try to fix the last leak and open a pull request.

@baentsch Do i have the permissions to create a branch in this repository? I have fixed it locally but cannot push it.

Please submit your fixes via PR from your own fork. A nice summary has recently been posted by Thom Wiggers to the oqs-developers mailing list:

The way PRs work on Github is that you create a copy of a repository under your own account (a so-called fork), add this fork as a "remote" to your local copy of the repository, and then push your changes to the fork under your github account. You can then open a pull request (so-called because it's a request to pull changes from your git repository!) through the command line.
See also: https://docs.github.com/en/get-started/quickstart/contributing-to-projects


Publish APK on Github?

Would you consider publishing the .apk together with the releases/ here at Github? After all, it's hosted here, and its about Github – so that would be only consequent :) Thanks in advance!

@IzzySoft , it will done with all new releases, thanks!

Thanks a lot, @DmitryMalkovich – but maybe you could keep this issue open and close it as soon as the first APK has arrived, so I have a signal then when to check for it?


Bugfix for undefined threshold from Scrublet

This is a bugfix to allow for the fact that Scrublet doesn't always find a threshold and produce predictions by:

Detecting when threshold not present, and setting prediction column to False'
Not assuming presence of threshold in plot functions.

Make a case where a threshold can't be found (not sure how this would be done)

I think manually unsetting it is probably the way to do this- I'll get on it when I can.


self.model instead of Page in PagesAPIViewSet get_base_queryset method.

Is your proposal related to a problem? No
I attempted to build a viewset for a specific page type by inheriting from PagesAPIViewSet. I assumed that I only needed to change the model to my CustomPage and that all the endpoints for that specific CustomPage would be available.
For example, in my particular use case, since I know that my page has only one parent and subpage type, the slugs, for my CustomPage, are unique. Therefore, I could handle detail_view by slug and not check if it's unique. Currently, it is possible to override methods like detail_view to add a slug and an URL in the get_urlpatterns method.
However, for the listing_view, the get_base_queryset method is used in PagesAPIViewSet. This method uses queryset = Page.objects.all().live(). Hence, listing_view doesn't specifically list my CustomPage, even though I set my model to CustomPage.
Although it is possible to achieve everything I want to do with the built-in API endpoint, I thought it would be easier to build a specific page type API viewset.
Describe the solution you'd like
I propose to change queryset = Page.objects.all().live() to queryset = self.model.objects.all().live(). I think this change won't affect the normal behavior of the API, but it allows us to create specific endpoints for each page type more easily.

Based on the description you provided, it sounds like the proposed solution is reasonable and would allow for easier creation of specific endpoints for each page type in Wagtail.
To implement the proposed solution, you would need to modify the "get_base_queryset" method in the PagesAPIViewSet class. Specifically, you would replace the line "queryset = Page.objects.all().live()" with "queryset = self.model.objects.all().live()" in your custom viewset class that inherits from PagesAPIViewSet.
This would ensure that the queryset used for listing pages in the API is based on the custom page type you specify in your viewset, rather than the default "Page" model used by PagesAPIViewSet.
Overall, this change should not affect the normal behavior of the API and would make it easier to create specific endpoints for each page type in Wagtail.

@priyanshpsalian your comment doesn't add anything constructive to this issue and reads like it's been automatically generated by ChatGPT, I'll hide it for now as it's unhelpful.

@Zogsha have you tried extending the method get_base_queryset instead?
See https://docs.wagtail.org/en/stable/reference/pages/queryset_reference.html#wagtail.query.PageQuerySet.type
Something like this should work I think...
class CustomAPIViewSet(PagesAPIViewSet):
    def get_base_queryset(self):
        queryset = self.super().type(CustomPage)
        return queryset

Now I think I understand. It's because get_base_queryset is used in child_of and descendant_of filters as well, to find parent pages. So even though my viewset inherits from PageAPIViewSet, get_base_queryset needs to query all Page object, in order to find the parent.
@lb- I think I should extend get_queryset instead of get_base_queryset, and filter the queryset as you mentioned : queryset = super().get_queryset().type(CustomPage). Thanks.
Sorry for the inconvenience, but as I looked for PagesAPIViewSet code, it felt odd to me that get_base_queryset don't use the model attribute.
I think this should be closed.

No problems @Zogsha - a reminder we also have the Slack channel for community support and Stackoverflow for community questions.
https://github.com/wagtail/wagtail#-community-support
I'll close this now.

@Zogsha one more reminder to read the docs on Page querysets, they have a bunch of helpful features and also that Django querysets are lazy and can be appended to all the way down until the query is actually resolved.
https://docs.wagtail.org/en/stable/reference/pages/queryset_reference.html
Hope you get to solve your problems well.


Upload Coin Display Network Token

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[ ] Filename in the lowercase format
[ ] Image format: png
[ ] Image size: 256 by 256 px

Please lowercase file name

@ngocvuong0605 Added it here https://github.com/TrustWallet/tokens/commit/a2d49c0271238353dae9a2fffbcc2c4de812aa1c

Also, you can use these graphics to say that your ERC20 token fully compatible with Trust Wallet (https://trustwalletapp.com/logo-assets). Tokens will show up automatically once the user receives them.
Feel free to share this on social media and tag Trust Wallet:

Twitter: @trustwalletapp

Facebook: @trustwalletapp


Fix can't be disabled AppWorks

修复套件引入插件 Chinese (Simplified) Language Pack for Visual Studio Code 不能被禁用，导致整个套件不能被禁用问题
#848

Codecov Report

Merging #849 (37a602b) into master (b18a447) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #849   +/-   ##
=======================================
  Coverage   57.14%   57.14%
=======================================
  Files           1        1
  Lines          70       70
  Branches       15       15
=======================================
  Hits           40       40
  Misses         30       30

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 b18a447...37a602b. Read the comment docs.

README.md 里面的 recommends 去除一下这个插件


undefined symbol: cudnnCreate

I tried building an image from the Dockerfile.gpu file and the build process succeeded without any errors.
However when I try to run some of the tensor flow scripts the scripts fails with the following error
F tensorflow/stream_executor/cuda/cuda_dnn.cc:221] Check failed: s.ok() could not find cudnnCreate in cudnn DSO; dlerror: /root/miniconda3/envs/carnd-term1/lib/python3.5/site-packages/tensorflow/python/_pywrap_tensorflow.so: undefined symbol: cudnnCreate Aborted (core dumped)

I have been able to work around this temporarily by using the offlicial tensorflow image as the base image instead of using nvidia's docker image.
I replaced the # FROM nvidia/cuda:8.0-cudnn5-runtime-ubuntu16.04 with FROM gcr.io/tensorflow/tensorflow:latest-gpu-py3

Sounds like you found a fix, so closing out.


Notes: Design & Implementation TBB

Following on from the discussion in #333 .. I have been re-reading the doc at https://www.torproject.org/projects/torbrowser/design/index.html.en - its been a while since I read it, and seems like its had a few changes and updates
I'll just use this issue to make some notes as I come across them

FYI the whole extensions.hotfix.* was removed in FF60 (meta ticket, wiki)

It's also interesting to follow all the tickets for the new Enterprise/Policy thingie which Mike Kaply is working on - lots of new prefs

OT: https://www.wired.com/story/hansa-dutch-police-sting-operation/
OMG .. so many OpSec failures: IRC (server) logs (reminds me of Lulzsec), and what about the dealers and geolocation metadata in their images .. WTF?

As they tell it, the police eventually became so brazen that they staged a fake server glitch that deleted all the photos from the site, forcing sellers to re-upload photos and giving Dutch authorities another chance to capture the metadata. That ruse alone snagged the geolocated coordinates of more than 50 dealers

Relevant tor ticket: https://trac.torproject.org/projects/tor/ticket/24965

Also https://xkcd.com/538/

Under questioning in a German jail, the two men handed over credentials to their accounts

They were nabbed with their machine's logged in and unencrypted (reminds me of police directives to nab phones when unlocked), this is about their online accounts. So long story short, you can't trust anyone. Mitigate the damage beforehand.

Closing this. When TBB based on ESR60 comes out, we will do a diff as a long overdue exercise.
I also don't think there is anything I can really do with that document. It's a bit "tattered" with various edits, and has some outdated and/or irrelevant info.


Refactor kairos-tx

I extracted great improvements of kairos-tx done by @Avi-D-coder in Trie integration, to reduce clutter in his PR.
List of changes:

Now all structures - Deposit, Withdrawal, Transfer, SigningPayload - can be created with flexible constructor. Thus helpers.rs got removed.
Now DER encoding/decoding is part of SigningPayload.
Updated Nix e2e test to use 2 different account for deposit and withdrawal, also fixed nonces.
Added Rust e2e test for encoding payloads.

One additional change that I made myself is to allow cloning the base fields, so we can extract nonce/amount/public-key without taking ownership of full transaction - https://github.com/cspr-rad/kairos/pull/81/commits/9fc5a007295bbfdeff54da64dd57493821b2f9ff.

@Rom3dius Thanks! Let me provide you context :wink: Schema for Kairos transaction is defined as ASN.1:
TxSchema DEFINITIONS AUTOMATIC TAGS ::= BEGIN

  -- Basic types.
  PublicKey ::= OCTET STRING
  Amount ::= INTEGER (0..18446744073709551615)

  Transfer ::= SEQUENCE {
    recipient PublicKey,
    amount Amount,
    ...
  }

Notably it's fully abstract syntax - there is no definition how those should be converted from and to bytes. However, ASN.1 is closely associated with multiple sets of encoding rules: BER, DER, CER, and others. DER-encoding is the one we are using, as it is fully deterministic, so we can have the exact same bytes representation that is implementation agnostic.

You did not address the comments I left about some of the changed files in Avi's PR:

Removing the Nonce from deposits
An explanation for why the payloads and signatures the way they changed in the end-to-end test

@marijanp I believe that simple change in Nix e2e tests was explained 3 days ago.
Your objectives about nonce in schema are not relevant here: this PR is basically refactoring API of schema, but not changing schema itself.


Add data from words.hk

words.hk (https://words.hk/) is a great Cantonese-Cantonese and Cantonese-English dictionary. Of particular value are the Cantonese definitions, as well as the example sentences.
words.hk does not provide their data available as a download, but the majority of their data is licensed under the open data license that permits use as long as proper credit is given and it is for non-commercial purposes. Scraping the website is also not expressly forbidden, so that may be what needs to be done.

@hnfong The contents in that link only seem to contain words that public. Is that right? I'd also like to include words that are still hidden behind the login.

I believe the list is complete.

Oh wow, yeah, after taking a second look it does seem to have all the entries. I'll update the code I have in the repository to parse that file instead when I have the time.

Since I've already written code that generates dictionary data from words.hk through scraping, that implementation fulfills the requirements of this issue. However, I will create a new issue to instead parse the file from the link in this discussion.


Update modularity tests based on Java 11 changes in SDK

Resolves https://github.com/AdoptOpenJDK/openjdk-systemtest/issues/150
Signed-off-by: Mesbah Alam<EMAIL_ADDRESS>

This PR contains the changes required to get modularity tests running on JDK11 : https://github.com/AdoptOpenJDK/openjdk-systemtest/pull/196
Change summary

Removed reference to java.transaction module from all tests (as this module no longer exists in JDK11) and replaced them with java.xml.
Upgrade module path related tests have been updated to exclude tests for "upgrading an upgradale system/platform module -- as the only "upradale" platform modules were ee modules (java.transaction) which have been removed in jdk11.
Updated CpMpJink test and removed use of --class-for-name (this option is no longer supported in jdk11).
Updated TestJDKInternalAPI test and removed reference to sun.reflect.Reflection as it no longer exists in JDK11.
Removed exclusion of modularity project from system test project build list.

The PR has been tested here: https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/465/tapResults/
Note: the two failing layers stress tests could e real issues. I'll open separate PR to investigate them, they will be excluded from the playlist.

Playlist changes to include modularity tests to jdk11 is contained here: https://github.com/AdoptOpenJDK/openjdk-tests/pull/703

Just to confirm that if excluded tests "upgrading an upgradale system/platform module" and CpMpJink test "use of --class-for-name" are excluded for all jdk versions?

Are we still testing Java 9 or 10?  Modularity doesn't exist in Java 8. And I believe it safe to not write and maintain complicated tests for modularity features not supported in Java 11 but only in Java 9 as Modularity had still been evolving during Java 9-- lots of things have been changed since.

@sophia-guo - agreed. Here's the grinder with JDK 8 - with a modularity test target - it builds successfully and runs nothing : https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/469/console


Increase time response when getting account history

Hi! Can we increase time response when getting account history? In general time response from 6 to 50sec.
root@xtz-02:~# time curl -s 'http://<IP_ADDRESS>:8000/explorer/account/tz1ftXcwbkeef2GnwqecUw7M26EuGXWY1mHt/op?offset=0&limit=100'
{...}
real	0m17.786s
user	0m0.006s
sys	0m0.000s

root@xtz-02:~# time curl -s 'http://<IP_ADDRESS>:8000/explorer/account/tz1YhtbmHd7cWYohQRsdtfcriiYTaETbGKLS/op?offset=0&limit=100'
{...}
real	0m51.207s
user	0m0.000s
sys	0m0.007s

Some times response 504.
Tzindex run on machine with:

8 CPU
64GB RAM
NVME SSD 1TB

tzindex config.json. Which database parameters we can change for Increase performance?
{
	"server": {
		"addr": "<IP_ADDRESS>",
		"port": 8000,
		"scheme": "http",
		"host": "<IP_ADDRESS>",
		"workers": 50,
		"read_timeout": "5s",
		"header_timeout": "10s",
		"write_timeout": "1000s",
		"keepalive": "90s",
		"shutdown_timeout": "15s",
		"max_list_count": 50000,
		"default_explore_count": 20,
		"max_explore_count": 100,
		"cors_enable": false,
		"cors_origin": "*",
		"cors_allow_headers": "Authorization, Accept, Content-Type, X-Api-Key, X-Requested-With",
		"cors_expose_headers": "Date, X-Runtime, X-Request-Id, X-Api-Version",
		"cors_methods": "GET, OPTIONS",
		"cors_maxage": "86400",
		"cors_credentials": "true",
		"cache_enable": false,
		"cache_control": "public"
	},
	"crawler": {
		"queue": 1000,
		"snapshot_path": "./db/xtz/snapshots",
		"snapshot_blocks": [],
		"snapshot_interval": 0
	},
	"database": {
		"path": "./db/xtz",
		"engine": "bolt",
		"gc_interval": 50000000,
		"gc_ratio": 1.0,
		"log_slow_queries": "2s",
		"account": {
			"cache_size": 4
		},
		"account_index":{
			"cache_size": 8
		},
		"contract": {
			"cache_size": 2
		},
		"contract_index":{
			"cache_size": 2
		},
		"op": {
			"cache_size": 4
		},
		"op_index":{
			"cache_size": 128
		},
		"block": {
			"cache_size": 8
		},
		"block_index":{
			"cache_size": 64
		},
		"flow": {
			"cache_size": 4
		},
		"supply": {
			"cache_size": 2
		},
		"chain": {
			"cache_size": 2
		},
		"right": {
			"cache_size": 2
		},
		"income": {
			"cache_size": 2
		}
	},
	"rpc": {
		"host": "<IP_ADDRESS>",
		"port": 8732,
		"threads": 10,
		"disable_tls": true,
		"dial_timeout": "20s",
		"keepalive": "30m",
		"idle_timeout": "30m",
		"response_timeout": "60s",
		"continue_timeout": "60s",
		"idle_conns": 50
	},
	"logging": {
		"backend": "stdout",
		"flags": "date,time,micro,utc",
		"level": "info",
		"blockchain": "info",
		"database": "info",
		"rpc": "info",
		"server": "debug",
		"report": "info",
		"micheline": "info"
	}
}

We use tzindex version 6.0.1
#./tzindex version
2020/04/14 11:29:03.799537 WARN MAIN Missing config file, using default values.
2020/04/14 11:29:03.799560 INFO MAIN Blockwatch tzindex dev -- none
2020/04/14 11:29:03.799564 INFO MAIN (c) Copyright 2018-2020 -- Blockwatch Data Inc.
2020/04/14 11:29:03.799571 INFO MAIN Starting Blockwatch-tzindex/dev.none on 8 cores
2020/04/14 11:29:03.799574 INFO MAIN Go version go1.13.9
2020/04/14 11:29:03.899669 INFO MAIN Profiling mutex/blocking at 1.00% sample rate.
Blockwatch tzindex dev -- none
(c) Copyright 2020 -- Blockwatch Data Inc.
Go version (client): go1.13.9

tzindex logs for last few minutes: https://pastebin.com/raw/FdTZtjsc

You may want to increase size of caches for tables you are hitting regularly. Call GET /system/tables and look for packs_count vs packs_cached and index_packs_count vs index_packs_cached (the DB may cache different versions of packs so leave some leeway). For the op table I suggest 256 to 1024 regular packs and 1024 index packs.
Watch memory consumption. If you run this with too little memory allowance in Docker and don't disable oom_kill then you may experience data loss. With oom_kill_disable=true the container just freezes and you can give it some extra memory to continue or shutdown gracefully (docker --update -m 32G --memory-swap 33G <id|name>)
To set TzIndex config values you can either use the config file or ENV vars (e.g. TZ_DATABASE_OP_CACHE_SIZE=1024).
You may increase HTTP write timeouts as well if you can't spend memory to speedup database lookups or you have slow clients. To do so set TZ_SERVER_WRITE_TIMEOUT=90s

Thanks a lot. This env parameters helped us to improve response time.
TZ_DATABASE_OP_CACHE_SIZE
TZ_DATABASE_OP_INDEX_CACHE_SIZE


Client fails to connect to Docker based validator node: Deadline exceeded

I did exactly the 6 steps as described in the Libra Docker Readme.
After doing the steps 1-5 the validator nodes and the faucet server are running successfully:
docker ps

CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                          NAMES
fd84c8aa87a6        libra_mint:latest   "/bin/sh -c 'cd /opt…"   13 minutes ago      Up 13 minutes       <IP_ADDRESS>:8080->8000/tcp         awesome_pike
22e5b50811dc        libra_e2e:latest    "/bin/sh -c 'cd /opt…"   14 minutes ago      Up 14 minutes       6180/tcp, 8000/tcp, 9101/tcp   pedantic_wescoff
31273f30a6f9        libra_e2e:latest    "/bin/sh -c 'cd /opt…"   14 minutes ago      Up 14 minutes       6180/tcp, 8000/tcp, 9101/tcp   friendly_gauss
4a7f99d15f80        libra_e2e:latest    "/bin/sh -c 'cd /opt…"   14 minutes ago      Up 14 minutes       6180/tcp, 8000/tcp, 9101/tcp   sweet_mendel
324cb273f4fa        libra_e2e:latest    "/bin/sh -c 'cd /opt…"   14 minutes ago      Up 14 minutes       6180/tcp, 8000/tcp, 9101/tcp   pensive_kepler

But the last command  fails and I get the error message below:
cargo run -p client --bin client -- -a localhost -p 8000 -f localhost:8080 -s terraform/validator-sets/dev/consensus_peers.config.toml

Not able to connect to validator at localhost:8000, error RpcFailure(RpcStatus { status: DeadlineExceeded, details: Some("Deadline Exceeded") })

god is sooo goood make a pray


rules list command returns generic 404 when no rules are configured

Running cortextool rules list when no rules are configured returns the following error message
$ cortextool rules list
time="2019-12-17T12:49:29-05:00" level=fatal msg="unable to read rules from cortex, requested resource not found"

This initially led me to believe there was an issue with my CORTEX_ADDRESS value. Should it return an empty list / fail silently instead?

With #10 this issue has been resolved


Update _misc.py

This part of the code raised the following error for me: AttributeError: module 'jax.numpy' has no attribute 'astype'. Did you mean: 'dtype'?. Therefore, this is my proposed solution.

Hmm, I think you might just be on a really old version of JAX? At least on v0.4.25i then jnp.astype exists.

I was running it on the latest jax-metal version since I have an apple with M1 chip. That might be the root cause of the error. I switched to jax["cpu"] because with the jax libraries I was using I ran in to many errors. I will train on an Nvidia GPU anyway, so for now this is a sufficient solution. But I have noticed that many jax libraries don't integrate well with jax-metal or apple M1.
Thank you for your rapid response, I have been enjoying reading your research on Neural ODEs and am using them (and Diffrax) now for my master thesis.

Ah, perhaps that is a metal thing. Indeed the metal plugin is still known to be very incomplete.
On that basis I'm going to close this PR for now!


File system layout

By default, only the relevant dir for the container runtime should be writable.
We should have then:

[ ] read only /usr - / if feasable
[x] ephemeral /etc that gets wiped out each time (tmpfs mount?)
[x] persistency only on /usr/local and /oem folder

Mind also to switch back https://github.com/mudler/cOS/blob/31749456b54f3eb60ad203cd3f212c6717b29320/packages/initramfs/loader.sh#L225
Persistency partitions and /etc/fstab configuration can be driven by cloud-init config files, currently in https://github.com/mudler/cOS/blob/31749456b54f3eb60ad203cd3f212c6717b29320/packages/cloud-config/yipfiles/01_defaults.yaml#L12 and from the installation phase
Every user-side or oem configuration, will be handled by #4 and #24
Action items:

[ ] Investigate layout from other projects on how they feased problematics regarding this topic
[ ] Configure the layout in the init, and cloud-config files
[x] Modify installer to create a persistent partition (that occupy all the space left)
[x] Tweak init to mount such partition
[ ] QA

Depends on #4 Merged

I did a search on MicroOS and the layout there looks like:

/etc is an overlayfs on tmpfs
/ is a readonly mount
root, /opt, /home, /usr/local and /srv read/write btrfs subvolume
/var read/write partition
Then some boot artifacts are read write too.

I'll close this as we merged #48 , if needed will file new issues for follow-ups


links aren't rendered as code

cc @hamelsmu @jph00

I think you might have forgotten to export

Hmm CI should be catching the non synced notebook I'll look


chore: Update transform script to accept acl permission at any position

Description
Fixes #Issue Number
or
Fixes Issue URL

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation
/ok-to-test<EMAIL_ADDRESS>:mag: Cypress test results

[!WARNING]
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/9613243545
Commit: e1812f2115b2ce624562f674876c7c24cefaa0f4
Cypress dashboard.
Tags: @tag.Sanity
It seems like no tests ran 😔. We are not able to recognize it, please check workflow here.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[x] No

Merging this as server tests went through.


Add tutorial for openlayers intergration

I was hoping to be able to present geopackage on my website using openlayers.
Looking at the documentation and using google search did not allow me to find how to use this library with openlayers.
Is it possible to add a tutorial to the documentation to show what needs to be done in order to make openlayers present geopackage tiles?

I have not worked with OpenLayers however there are many convenience methods in the API that should help: getTileFromXYZ for 3857 tiles, draw4326TileInCanvas for 4326 tiles, in addition to the query for GeoJSON methods.  If you would like to contribute a tutorial, I will accept the pull request.

Documentation for the library can be found here: http://ngageoint.github.io/geopackage-js/jsdoc/module-GeoPackage-GeoPackageAPI.html
You can find an example of how to use those methods to integrate with Leaflet here: https://github.com/ngageoint/geopackage-js/blob/master/leaflet/leaflet-geopackage.js
I will re open this issue in the hopes that someone can provide a tutorial.

In fact, the previous link provided is for untiled vector layers.
For raster tiles, see https://labs.webgeodatavore.com/partage/gpkg-raster-tiles/
PS: I'm the author of both samples.

Only remaining demo would be vector tiles. I will maybe play with it later :)

Thomas, I'm running Chrome and those samples don't work on my machine.  The vector sample gives an error about not loading geopackage.  The tile sample doesn't explicitly produce an error but shows no data either.

@xirias No clue. The examples are working on Chrome Version 72.0.3626.81 and Firefox 65 (64 bits) on Linux.
Only clue could be you have a plugin that block also some network calls. Open samples in a browser private window to try out.

@ThomasG77 Thanks for the info!!
The main thing that I haven't found any info about is how to convert the geopackage styles to openlayer styles mainly for the use cause of map rotation and keeping the text aligned.
If you get this working it would be support if you could post a link here.
Keep up the good work!

GeoPackage does not (currently) have a way to define styles within the GeoPackage.

Really? Then how does the rendering works if the styles are not defined inside the file? Are they defined elsewhere?

It is left up to the clients to decide how to render each vector layer.  The demo page just renders the vectors in a shade of blue.  I believe the OGC is working on a style extension, but I am not sure what the progress is on that.

I've seen the below two articles where it is suggested that some GeoPackage creators are doing this, but it might not be a standard, did I get this right? using a table called layer_styles...?
https://www.geocat.net/extending-geopackage-to-include-projectstyling-information/
https://gis.stackexchange.com/questions/273750/is-there-any-way-to-include-universal-style-symbology-in-geopackage

Styles are in your code in OpenLayers.
There are extensions in Geopackage to support styling https://www.geopackage.org/extensions.html. One is vendor related (QGIS), another is tied to OWS Context.
The only possible move for styles with these extensions would be to support conversion from QGIS or SLD styles to OpenLayers styles. I'm not aware of "out of the box" solutions for this intent.

I found this package:
https://github.com/Norkart/SLDexit
Which can be used to convert SLD to mapbox gl style
And this one:
https://github.com/openlayers/ol-mapbox-style
From mapbox gl to openlayers.
I haven't tried it myself but it's an interesting idea I've read somewhere...

@ThomasG77 is the https://labs.webgeodatavore.com/partage/trails/ sample still available somewhere? Or did anyone else grab a copy of it that can share it?
Thanks.

@elwoodhouse Restored the broken url


Refactor The Entire Codebase

User Story
As a developer, I would like to be able to work with clean code, so that I don't laugh at you (lol).
Description
Refactor the codebase.

Forgot to close in a previous PR. The issue is not a duplicate and had already been completed in a previous commit.


Error: Cannot find module '../build/Release/keyboard-layout-observer.node'

Version: b6d6fb4 (master)
OS: Linux HP-NONE 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64 GNU/Linux
NODE: iojs v1.4.3
Build:
PYTHON=/usr/bin/python2.7 script/build
sudo PYTHON=/usr/bin/python2.7 script/grunt install

Reproduce:
Launch Atom
What occurs:
Error: Cannot find module '../build/Release/keyboard-layout-observer.node'
    at Module._resolveFilename (module.js:351:15)
    at Function.Module._resolveFilename (/usr/local/share/atom/resources/app/src/module-cache.js:383:52)
    at Function.Module._load (module.js:293:25)
    at Module.require (module.js:380:17)
    at require (module.js:399:17)
    at Object.<anonymous> (/usr/local/share/atom/resources/app/node_modules/atom-keymap/node_modules/keyboard-layout/lib/keyboard-layout.js:6:28)
    at Object.<anonymous> (/usr/local/share/atom/resources/app/node_modules/atom-keymap/node_modules/keyboard-layout/lib/keyboard-layout.js:33:4)
    at Module._compile (module.js:475:26)
    at Object.loadFile [as .js] (/usr/local/share/atom/resources/app/src/babel.js:162:21)
    at Module.load (module.js:370:32)
/usr/local/share/atom/resources/app/src/space-pen-extensions.js:64 Uncaught TypeError: Cannot read property 'dispatch' of null

Hy,
I have the same problem running the same Linux version but nodejs v0.12.0 so it's not a problem with iojs.

Yay, I reinstalled it a view minutes ago and now it works, bug seems to be fixed.
Interestingly it seems there was no commit (on the used branch) since yesterday, so the bug probably was in some of the build dependency or similar.

I can confirm it's fixed aswell.

I'm encountering this regardless of atom version. Same operating system, and nodejs v0.12.0. I was able to compile on my other Arch system without any trouble.
I've tried building on master, v0.194.0, v0.192.0, and v0.189.0.

Fixed: I deleted the repo, re-cloned, and built master. Perfect.

In the future you might want to try script/clean before removing the repo.

How embarrassing. I swear I looked for something like that. Even did a
make clean in a fleeting moment of desperation.
Wliu writes:

In the future you might want to try script/clean before removing the repo.

Reply to this email directly or view it on GitHub:
https://github.com/atom/atom/issues/5865#issuecomment-95328931

--
Sent with my mu4e


Add Conflict Cause parameter and logic

Add conflict cause for bulk insert.

Hi!  Cool idea!
Can you remove the space after Parameter (see failures here?
Guess it doesn't like [parameter ()] vs [parameter()]

Awesome, thank you!
Going to merge this in, will flip it to ConflictClause for consistency with the docs.


Gh 2061 store properties simplification 2

Closing as code has been copied to local branch gh-2061-store-props-simplification to allow fixing of tests and to fix merge conflicts.


Reactive Eval::get should propagate errors

Currently, for reactive/ CompletableEvals Eval get() swallows any errors recieved via the reactive-streams error channel (but propagates errors thrown inside it's own operators). It returns null instead.
This is a bug. It is reasonable to expect that round triping from a Future with a NoSuchElementException results in a failed Future with a NullPointerException and not a successful Future with a null value.
Eval::get should throw any errors recieved from any Publisher to which it was subscribed (this does make mixing Eval with reactive-streams operators fromPublisher / mergeMap unsafe, likely for the duration of the 10.X.X cycle).

Tests
@Test(expected = NoSuchElementException.class)
     public void fromFuture(){
      Future<Integer> f = Future.ofError(new NoSuchElementException());

      Eval.fromPublisher(f).get();

    }

    @Test
    public void toTry(){
        Future<Integer> f = Future.ofError(new NoSuchElementException());
        Try<Integer, Throwable> t = Eval.fromPublisher(f).toTry();
        System.out.println(t);
        assertThat(t.isFailure(),equalTo(true));
        assertThat(t.failureGet().orElse(null),instanceOf(NoSuchElementException.class));
    }
    @Test
    public void fromFuture2(){
        AtomicReference<Throwable> error = new AtomicReference<>(null);
        Future<Integer> f = Future.ofError(new NoSuchElementException());
        Future.fromPublisher(Eval.fromPublisher(f)).recover(e->{
            error.set(e.getCause());return -1;
        });

        assertThat(error.get(),instanceOf(NoSuchElementException.class));
    }

Released in 10.1.1


S2Geometry geographical point index: preliminary results

I started working on some Python/NumPy wrappers for s2geometry indexes here: https://github.com/benbovy/pys2index
I did some preliminary tests and naive benchmarks (random points) against scikit-learn's BallTree index (with Haversine metric), and the results are very promising! It might be worth to also compare it against some fast KD-Tree implementations available in Python (with appropriate coordinate system transformation).
A nice thing with s2geometry is that we could leverage additional features like:

setting a maximum lookup distance to speed-up queries (related to #11 and #13).
range queries, i.e., select all points within a latitude and/or longitude range (which would work well with xarray.Dataset.sel(lat=slice(...), lon=slice(...))) ... or actually within a region of any geometry (polygon).

Build index benchmark: pys2index.S2PointIndex 3x faster than sklearn.neighbors.BallTree for 10M points.

Query index benchmark: pys2index.S2PointIndex 40x faster than sklearn.neighbors.BallTree for 100k points!

Notebook link: https://gist.github.com/benbovy/1f35c717b44791ca600655081b5b6fc3

Added adapter for this index in #28.


Unused property Element.handler

https://github.com/eight04/angular-datetime/blob/9785c3d3356c1cea0be8e36f8cc3cedfa588d603/lib/directive.js#L8
We should also remove this.doc = document and use $document instead. Why eslint didn't warn us?

We should also remove this.doc = document and use $document instead. Why eslint didn't warn us?

NVM, it's a function argument.


Fix remaining characters UI being cut off with multiple langs selected on small devices

Fixes: #6178

Summary
The footer component of the composer dialog gets messed up when multiple langs are selected on small devices like iPhone SE 3rd Gen. We display the circle/pie progress bar next to the number of remaining characters, and it seems it can be optimized so that text lives inside the progress bar. It will create a room for the composer footer so that all components in it can fit nicely.

Solution
I referenced how X handles it, and it seemed quite reasonable.

The number doesn't appear until we approach the limit. (-20) It will help prevent the text width from getting bigger than the progress bar when the number is more than 2 digits, like 250.
The progress bar disappears when the input is far above the limit. (+10) same reason as above

Recording
https://github.com/user-attachments/assets/a29201db-3eec-472d-9f7d-fed1fb965f43

I'd love to receive any feedback/comments on these changes.

Let's get this rebased.

Oops! Something went wrong! :(

ESLint: 8.47.0

ESLint couldn't find the config "preact" to extend from. Please check that the name of the config is correct.

The config "preact" was referenced from the config file in "/Users/admin/Work/Personal/OpenSources/social-app/bskyembed/.eslintrc".

If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.

husky - pre-commit hook exited with code 1 (error)

I am not sure what's changed recently, but I cannot commit the merged changes because of the above issue. Husky fails on eslint for some reason.

@gaearon I merged main by bypassing husky pre-commit hook with --no-verify flag. I am not sure exactly why it was failing. However, after merging, I confirmed no lint errors by running yarn lint. It's still mysterious to me 🤔
I think it's probably related to the recent eslint config update made in this commit. And maybe, husky doesn't handle it well with git merge --continue command especially when there were merge conflicts. 🧐


Menu displaying problem

Hi,
When I run the program, the menu displays "{" and "}" characters !

How can I fix this problem ? Thank you.

See #110.

Closed as duplicate of #110 , see that issue for details.


(Long term) Update php-ast dep to version 50

Time when this should be merged to master

some point after phan 0.9.4 is released (Done)
before the PHP 7.2.0 branch has been released,
before php-ast version 40 deprecation is released

TODO: Add more specific error for the test case
(Not supported in php <= 7.1)

@morria @rlerdorf - To avoid disruption for third party plugins or for projects using methods from Phan (not sure how many there are, I've only worked on the PhanUnusedVariable plugin), it might make sense to bump the release number from 0.9 (and 0.8, but probably not) to 0.10 at the same time. Thoughts?

How hard do you suspect it'll become to backport patches from 0.10 to 0.8 if it's on an older AST version?
My preference will be to leave 0.8 behind if you don't think it'll be prohibitively expensive.
Moving from 0.9 to 0.10 for the new AST version makes sense to me.

Reverting this patch (for 0.8 only) and maintaining that seems possible without that much work after the initial change - Most of the code (except for entry points for analysis, which rarely change) deal with Nodes.

Got it. LGTM.


Should the list of recipes in the README be alphabetized or use another "obvious" ordering?

Or perhaps grouped, e.g., RAG with two sub-bullets for the two recipes. The current ordering seems chaotic because there is no obvious ordering. An alternative would be simpler to more sophisticated.

Agreed.

I will add section headers to that list, which will give it more of an obvious flow.  Roughly from simple to more complex


fix device mapping issue of llama gptq

https://inteltf-jenk.sh.intel.com/job/inc_gaudi_test/178/

https://inteltf-jenk.sh.intel.com/job/inc_gaudi_test/179/


feat: add option to include file url

Adds the option to include a link to the references gitignore file in the README.
I prefer to add a link, so contributors know where it was derived from.
When the setting is enabled, the output looks like the following:
# https://raw.githubusercontent.com/github/gitignore/master/Maven.gitignore
target/
pom.xml.tag
pom.xml.releaseBackup
pom.xml.versionsBackup
pom.xml.next
release.properties
dependency-reduced-pom.xml
buildNumber.properties
.mvn/timing.properties
# https://github.com/takari/maven-wrapper#usage-without-binary-jar
.mvn/wrapper/maven-wrapper.jar

Hey! Glad to see that you're alive! \(^-^)/
This weekend I can review all the ones you closed just to verify if they're cool, and fix the conflicts for the ones you've left open.
Thanks for peeking at the PRs!

Fixed merge conflicts and updated it to match the new project structure.
I did one extra change, I hope that's alright!
I added a new script I hope you don't mind! It's just to run the tests in a headless environment. This will be useful later anyway if you set up GitHub Actions.
More Info: https://code.visualstudio.com/api/working-with-extensions/continuous-integration#github-actions

I've rebased with master and resolved merge conflicts. :+1:


I can run project in intel chip but cannot run in apple M1. Getting error.

In my intel base apple MacBook project working successfully I used TTPDF version 1.5.4, After that I am trying to run same project in new apple M1 chip.
I tried with various version of TTPDF. (even tried latest version)
I tried with rosetta mode of Xcode (Version 13.2.1 (13C100))
I am attaching screenshot here.
Old version of TTPDF 1.5.4

New version of TTPDF 2.3.5

When try to jump on that

It seems to be conflicts with PDFKit.

Hi, yes this is conflicting with PDFKit (even tough TPPDF is older than PDFKit).
You can use both by adding a prefix PDFKit.PDFDocument and TPPDF.PDFDocument.
This should not be related to Intel vs M1

Thanks TPPDF.PDFDocument works for me :)


client/load: tiny typo fix

Signed-off-by: Ma Shimiao<EMAIL_ADDRESS>

Ah, great! Thank you.
LGTM

LGTM


Allow resource owners to set resource 'shreable' flag

When a resource is created by default the 'shareable' flag is set true  meaning resource can be shared by any users who have some level of access permission to the resource. Only resource owners can set this flag. If 'shareable' is set to false, only resource owners can share the resource with other users.
Pabitra to implement backend support for this functionality
Mauriel to implement frontend support for this functionality

By shareable do you mean the ability to grant permissions to other users?

Yes. When the resource is not shareable a user who has either 'edit' or 'view' permission on that resource can't give access to that resource to any other users. However, the resource owners can always give permissions to other users.

Following is the definition of the sharing attribute in the Access Control Policy
Shareable – Entities other than owners may grant access to the resource. If False, non-owners who receive access to the resource may not grant that access to others.
Sharing (extending access)
The boolean attribute ‘Shareable’ is intended to give resource owners control over who the resource may be distributed to, a use case that is deemed important to protect the intellectual content of resources that may contain unpublished data.  Shareable=False effectively holds the rights to enable access to another user at the owner level.  Shareable=True extends these rights to users with change and view privileges, allowing redistribution of the resource at the same level of permissions that a user has, i.e. the resource is "Distributable", even for users with read-only privilege.  Specifically, when Shareable=True then a user with view settings can share the resource at the view level (i.e. enable view access to another user or group in the system).  When Shareable=True, a user with change settings can share the resource at the change or the view level.  Only owners may change the ‘Shareable’ setting.
The full policy document is in Alfresco at: https://my.alfresco.com/share/s/WJuMf2ghRlyuty0oXrqe5g
Please do review the full policy as we will eventually need an interface that allows management of all the access control attributes.

@mauriel133 I have now fixed this issue(both front and backend). Can you make the necessary adjustment to the fontend styling may be? Branch:664-using-resource-shareable-flag. Once you are done, I can create the PR for it.

Sure, I will have a look.

This PR should wait for the new access control interface to be merged in order to avoid conflicts and working on it twice. Once the interface is merged I will bring this one up to speed.
It looks to me that this should be a toggle button. When enabled, view users should have access to the access panel when the resource is in view mode (since they are not allowed to go into edit view). This will make things a little inconsistent with the respect to the access control interface, which right now is only accessible through edit mode.
Should we bring the access control interface back into view mode for every user that can grant at least one level of permission?

@mauriel133 There is no PR for it at this point. Once you make the necessary changes to this branch, I can create a PR. If you think this should wait until the new access control interface gets merged then we will wait to create the PR until then.

@mauriel133 @pkdash and @dtarb - this inconsistency seems complicated to me.  Do we really want the access control panel to show outside of edit mode for users that have view only access? We just moved this functionality to the edit page so that all editing is done consistently in one place. And, do we also want to allow view only users to actually edit the access control for a resource (e.g., to add more view only users)?  I just want to make sure we are clear on the implications of this.

@horsburgh we do want users with view permissions to be able to add new view users for resources for which "shareable" is set.  This is to encourage sharing, and was a policy decision made without considering how the functionality would be implemented.  I recognize that the choice to have access control on the edit page that is only accessible to users with edit permissions makes this complicated, but would prefer that design choices about the layout do not dictate policy.
The reason for the policy is to reduce copying and offline sharing of content, as if a user could not share a resource with someone, they may be tempted to make a copy or download and share it separately.  It is better to keep the collaboration in HydroShare.

@dtarb - I understand the desires behind the policy.  But, the current implementation would be overly complicated as it is now. We should make policy decisions with some consideration about how the functionality would be implemented.
Since the access control panel needs to be accessible outside of editing mode for view only users, I suggest we move it outside of editing mode for everyone.  If a user has any permissions that would allow them to grant others permission, a button would appear on the resource landing page outside of editing mode allowing them to click to get the new access control panel.  Unfortunately, I think this undoes some work that @mauriel133 has already done, but may not be too involved.

Policy did not dictate that you had to implement on separate pages.  That was the choice that led to the complication.

Implementation and maintenance costs should absolutely be an important consideration in policy, both in terms of defining overall goals and in prioritizing what has a greater ROI to deliver sooner rather than later.

@mauriel133 Wondering on the status of UI changes needed for setting the 'shareable' flag.

I didn't make progress on this issue during the break, but I'm working on it this week.

Is there anything else that needs to be done for this functionality?

Tested and working to my liking.


Script is resumed as soon as node-inspector is loaded

I'm launching my program with --debug-brk. Execution is immediately paused. However, as soon as I load up node-inspector's page in Chrome, the script resumes, and immediately crashes (with the error I'm trying to debug). This gives me no time to set, say, a breakpoint. (Incidentally, debugger; statements don't help.)
I'm not sure what other information I can share, here. My own code is fairly complex; if you'd like to try and reproduce this on your end, the following should approximately duplicate the environment where I'm seeing this:
brew install nvm
nvm install 0.11
nvm use 0.11
npm install -g node-inspector
node-inspector &
git clone git@github.com:Paws/Rulebook.git --branch letter-01
git clone git@github.com:ELLIOTTCABLE/Paws.js.git --branch support-rulebook
cd Paws.js
npm install
npm install # yes, run it twice. bugs in my codebase. unrelated.
node --debug-brk ./Executables/paws.js check "../Rulebook/The Letters/01. On rules, meaning, and consistency.rules.yaml"
# At this point, it should be paused ...
# ... but as soon as you load up http://<IP_ADDRESS>:8080/debug?port=5858, for me, it resumes and crashes.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/7978672-script-is-resumed-as-soon-as-node-inspector-is-loaded?utm_campaign=plugin&utm_content=tracker%2F195817&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F195817&utm_medium=issues&utm_source=github).

Please share also error message.

Can you reproduce this behavior on some siple app? (for example node-debug-samples)

@3y3 from what? There's no error, it just opens, flashes the inspector for a moment, and then my code resumes-fails-exits, returning the inspector to the “Hit Cmd+O to open a file” view.

re: simpler codebase, I'll try that right now. (Wasn't expecting this quick of a reply at 4AM Chicago time, heh; about to crash soon. FYI.)

Works fine on node-debug-samples/sourcemap. I don't think it's a general problem with NI, I suspect it's the peculiarities of my codebase surfacing some weird edge-case. Problem is, I haven't the slightest idea where to start looking, because I don't … actually know how node-inspector works. >,>

Wasn't expecting this quick of a reply at 4AM Chicago time

I work by Russia's Moscow time =)

Works fine on node-debug-samples/sourcemap

That's nice! Now we need to find that is special in your app. Some cases for test:

Run node-inspector without & this way we can confirm, that ni don't throw errors by himself (looking at his console log)
Run node-inspector with --no-inject flag, this prevents ni from modify your app code (now we wrap all console functions to trace them to frontend)
Try to reproduce this behavior on v0.7.4

I also have this problem but only with Node.js 0.11.15.
0.11.14 doesn't work, 0.11.13 is good

I confirm the problem with 0.11.15.

Thanks for targetting node version. I can confirm the probem with 0.11.15.
To @bajtos :
The current problem - now we receive debug event when app started with --debug-brk flag, previously we only check that the application is paused. But the initial problem - we can receive a debug event before all sources have been downloaded, in this situation BreakEventHandler._onBreak works incorrectly.
I see two ways to fix this problem:

Cache all incoming events from app, before all sources will loaded in ScriptManager. We already do same thing with all incoming from frontend. In this way I prefer to emit resource-tree event not from PageAgent but from process.
Make BreakEventHandler._onBreak async and try to request source from app on the fly (with caching the response)

Are you see the third?

Both ways look sane. Which one is easier to implement?

Option 1) looks reasonable to me. It will probably fix also https://github.com/node-inspector/node-inspector/issues/314 which has been around for quite some time.

Option 1) looks reasonable to me. It will probably fix also #314 which has been around for quite some time.

On the second look, the fix of this issue will most likely not fix #314. However, we should take #314 into consideration while working on the patch, so that we don't make the situation even worse.

Ok. We selected first way.
@ELLIOTTCABLE , @oliverzy , @iliakan , are you want to fix this or this is job for me?

I don't think it is that easy, I'll try to get some time to work on this myself. Unfortunately that won't be sooner than in 2-3 weeks. So if there is anybody else willing to take up the challenge, then go for it!

Don't treat that as a lack of support, I'm a really a user, not a developer here. Other projects eat 146% of my time.

P.S. Thank you for what you're doing.

:+1:

+1, just updated to note 0.12.0 and this issue came up.

Thanks I reported 558, and I'm glad to know someone's looking at it. At some point, I may have time to help, but not now unfortunately.

I'm going back to 11.3 node until this sorts out. I'm dead in the water w/0.12.0 and latest node-inspector that I can't get to install due to v8-profiler issues on Debian (wheezy).

@ChrisRus Try npm install -g<EMAIL_ADDRESS>That version has less native dependencies at the cost of missing profiler tabs.

I'm in the same boat, using node 0.12 and node-inspector 0.9.1.
In case you need any further examples, I've reproduced with a very simple script. Screencast here.

I am having the same issue, with node 0.12.0, node-inspector 0.9.1. Typically I use node-debug for convenience, but the same thing happens running node-inspector plus the --debug-brk option.
I have been experiencing this issue with a fairly complex script. In light of the suggestions above, I have just tried it with a simple script I used to test the mathjs published module. It does not break at the first line, and runs through to completion without any ability to set a breakpoint.
ie.
node-debug test_mathjs.js
The test_mathjs.js script is below:
var math = require('/path/to/node_modules/mathjs');
var parser = math.parser();
var minutes = 1000 * 60;
var hours = minutes * 60;
var days = hours * 24;
var years = days * 365;
var str = 'now()-startTime';
var match = str.match(/[+-]/gi);
console.log(match);
if (match.length > 0) {
var strArray = str.split(match[0]);
console.log(strArray);
if (strArray[0] == 'now()') {
var expr_term1 = Date.now();
}
else {
var expr_term1 =<PHONE_NUMBER>111111;
}
if (strArray[1] == 'now()') {
var expr_term2 = Date.now();
}
else {
var expr_term2 = Date.parse('2015-01-28T19:18:48Z');
}
var scope = {
	expr_term1: expr_term1,
	expr_term2: expr_term2
};
var math_expr_str = 'expr_term1 ' + match[0] + ' expr_term2';
var x = math.eval(math_expr_str, scope);
var y = Math.round(x / days);
//var x = parser.get('x');
console.log(y);

}
parser.eval('x = 7 / 2');
var x = parser.get('x');
console.log(x);
var d= Date.parse('2015-01-28T19:18:48Z');
var y = Math.round(d / years);
console.log(y);
var n = Date.now();
var diff = n - d;
console.log(diff);
var y = Math.round(diff / days);
console.log(y);

Colin G

So, in order to implement:

Cache all incoming events from app, before all sources will loaded in ScriptManager. We already do same thing with all incoming from frontend. In this way I prefer to emit resource-tree event not from PageAgent but from process.

I am trying to make these events:
Fri, 06 Mar 2015 14:48:30 GMT node-inspector:ScriptManager addScript id: 82 localPath: C:\Users\Sean\p\websql-server\node_modules\primus\errors.js hidden? false source? true
Fri, 06 Mar 2015 14:48:30 GMT node-inspector:ScriptManager _getSourceMapUrl(82) - using the suplied source
Fri, 06 Mar 2015 14:48:30 GMT node-inspector:ScriptManager addScript id: 78 localPath: C:\Users\Sean\p\websql-server\bin\websql-server.js hidden? false source? true
Fri, 06 Mar 2015 14:48:30 GMT node-inspector:ScriptManager _getSourceMapUrl(78) - using the suplied source
Fri, 06 Mar 2015 14:48:30 GMT node-inspector:ScriptManager addScript id: 67 localPath: assert.js hidden? false source? true
Fri, 06 Mar 2015 14:48:30 GMT node-inspector:ScriptManager addScript id: 77 localPath: _linklist.js hidden? false source? true
Fri, 06 Mar 2015 14:48:30 GMT node-inspector:ScriptManager addScript id: 71 localPath: _stream_writable.js hidden? false source? true

...
appear before which events?
I think it is these events:
Thu, 05 Mar 2015 23:40:30 GMT node-inspector:protocol:v8-debug request: {"seq":2,"type":"request","command":"continue","arguments":{"stepaction":"out","maxStringLength":10000}}

Thu, 05 Mar 2015 23:40:30 GMT node-inspector:protocol:v8-debug response: {"seq":3,"request_seq":2,"type":"response","command":"continue","success":true,"running":true}

Currently "command":"continue" is happening before addScript(s) are completed, correct?

@MetaMemoryT , look at my pr https://github.com/3y3/node-inspector/commit/702542e7dbf3f05439a07760a2f37e6d59f77360

Nice, I am pulling and testing your more-iojs branch.

@MetaMemoryT , feedback will be useful, thanks =)

so I pulled more-iojs
ran:
$ node bin/inspector.js

$ node --debug-brk simple-server/index.js
Debugger listening on port 5858
node.js:444
        stream = new tty.WriteStream(fd);
                 ^
TypeError: undefined is not a function
    at createWritableStdioStream (node.js:444:18)
    at process.stdout (node.js:502:16)
    at console.js:111:37
    at NativeModule.compile (node.js:805:5)
    at Function.NativeModule.require (node.js:774:18)
    at node.js:214:27
    at Server.<anonymous> (C:\Users\Sean\p\node-debug-samples\simple-server\index.js:23:3)
    at Server.g (events.js:199:16)
    at Server.emit (events.js:104:17)
    at net.js:1144:12

(from node-debug-samples)
seems like another third party error?
then I ran:
$ node bin/inspector.js

$ node --debug-brk sourcemap/app.js

and still got the same problem this issue is about, and got this message in the inspector console:
TypeError: Cannot read property 'prototype' of undefined

FYI; The NodeJS tools for Visual Studio ran into this exact same issue: https://nodejstools.codeplex.com/workitem/1808
According to information from that issue, it seems that NodeJS 0.12 now signals the initial break as an actual breakpoint, and if you treat that as an unknown breakpoint and just instruct the debugger to continue, then the app immediately resumes and runs to completion.
If I'm reading this correctly, their fix is to treat unknown breakpoints differently (basically; not instruct the debugger to continue on) while the debugger hasn't finished attaching itself.

NAVER - http://www.naver.com/
<EMAIL_ADDRESS>님께 보내신 메일 <Re: [node-inspector] Script is resumed as soon as node-inspector is loaded (#534)> 이 다음과 같은 이유로 전송 실패했습니다.

받는 사람이 회원님의 메일을 수신차단 하였습니다.

Great information, @rjgotten
Trying to find the code handling unknown breakpoints:
https://nodejstools.codeplex.com/SourceControl/latest#Nodejs/Product/Nodejs/Debugger/DebugEngine/AD7MemoryAddress.cs
https://nodejstools.codeplex.com/SourceControl/latest#Nodejs/Product/Nodejs/Debugger/DebugEngine/AD7BreakpointResolution.cs
Would this require changes to https://github.com/node-inspector/v8-debug ?

I have tried downgrading to node v0.11.16 and node-inspector v0.7.4 and node-inspector v0.8.3 - still can't break on first line.

@rafis node-inspector 0.9.1 and node 0.11.13 is working for me.

Do I get it right that this bug totally screws up debugging with --debug-brk for all recent iojs and node versions?

yes，0.11.13 is the last version that works

Any node-inspector replacement if I still want to debug with --debug-brk ?

@iliakan , you can try to fork from #560

@iliakan , so if you'll do it, send me email, if this pr doesn't work for you correctly.

@3y3 I can live without --debug-brk (and without --debug at all too! and without any dev tools! I'm an old programmer motherf*cker! :))
Just tracking the situation to jump on something when it's production ready.

it seems this bug is related to https://github.com/iojs/io.js/issues/877

Experiencing the same issue. --debug-brk works, but as soon as I attach node-inspector, the code resumes running and finishes. debugger statements do not help, and actually segfault the process (see below). Using node-debug gives the same result. Figured I'd add my two cents, in case there's any useful information in it - I have a simple testcase, in any case.
I use CoffeeScript, but I am compiling with sourcemaps and then running the .js file instead, so the issue shouldn't be with CoffeeScript here. Exact commands run are coffee -c -m test-leak.coffee and node --debug-brk test-leak.js.
sven@linux-etoq:~/projects/node-bhttp> node -v
v0.12.0
sven@linux-etoq:~/projects/node-bhttp> cat /usr/lib/node_modules/node-inspector/package.json | grep version
  "version": "0.9.2",

CoffeeScript source:
firstCode = global.code
require "./"
secondCode = global.code
console.log "Leaking global.code:", (firstCode != secondCode)

Compiled JS:
// Generated by CoffeeScript 1.9.1
(function() {
  var firstCode, secondCode;

  firstCode = global.code;

  require("./");

  secondCode = global.code;

  console.log("Leaking global.code:", firstCode !== secondCode);

}).call(this);

//# sourceMappingURL=test-leak.js.map

Adding a debugger statement will segfault the process, upon attaching node-inspector.
sven@linux-etoq:~/projects/node-bhttp> node --debug-brk test-leak.js
Debugger listening on port 5858
Leaking global.code: true
Segmentation fault

CoffeeScript source:
debugger;
firstCode = global.code
require "./"
secondCode = global.code
console.log "Leaking global.code:", (firstCode != secondCode)

Compiled JS:
// Generated by CoffeeScript 1.9.1
(function() {
  debugger;
  var firstCode, secondCode;

  firstCode = global.code;

  require("./");

  secondCode = global.code;

  console.log("Leaking global.code:", firstCode !== secondCode);

}).call(this);

//# sourceMappingURL=test-leak.js.map

I'm experiencing the issue (debugger / breakpoints have no effect) with Node v0.12.0 and Node Inspector v0.9.1

I'm also experiencing this issue, with Node v0.12.0 and Node Inspector v0.9.2

i just spent a couple of hours working on this. it seems like a pretty widespread problem. something should be mentioned in the readme until its fixed.

Why is all the related tickets for the same issue closed? was this fixed? I'm encountering the same issue. Please help

+1 @harindaka

Why is all the related tickets for the same issue closed?

Because there is no point in having multiple issues open for the same problem, they are just cluttering the issue list.

was this fixed? I'm encountering the same issue. Please help

Not yet, watch this issue to track any progress.

Thanks for the clarification. I confused this ticket with an already closed one. Will wait for a fix and hope for the best :D

Please don't confirm the issue here. There're enough confirmations.
If another debug-brk related issue is closed, that's probably a dupe.
When you write something here, all subscribed people get an email.
The issue is important, many people are subscribed.

Quick summary for those who land here needing a workaround (like me):
Affects node v0.11.14 or higher.  Use an earlier version of node to unblock yourself

v0.11.13 (Last compatible Unstable) - http://nodejs.org/dist/v0.11.13/
v0.10.38 (Last compatible Stable) - http://nodejs.org/dist/v0.10.38/

Node v0.10.38 will give you the profiler 'partial support' warning which you can ignore if you do not use the profiler.  Use v0.11.13 as the warning suggests if you need the profiler.

@dpwolfe if your statement is accurate then it should be added to README.md
@bajtos can you weigh in?

I am ok with adding the summary to README, can somebody please submit a pull request?

+1 :(

Fixed in 0.10.0 release. Reopen this bug if the problem still persists for you.

Wow! holy dude, I'll start using node-inspector once again!
It even installed on my io.js!

:joy:

Thank you! Will give it a try tomorrow!

Still experiencing the issue with node v0.12.2 and node-inspector 0.10.0. Placed breakpoint in the Express 4 app and it wasn't hit. The code just runs to completion.

In my case it stopped at the first line as --debug-brk should do, but then did not stop at any breakpoints.

Seems to work for me now.
I use it in cases when I'm running unit tests with mocha --debug and somehow it decides to skip past a breakpoint.
if I run mocha --debug-brk I'm now consistently getting stops using debugger; lines in my code.
using node v0.12.2 and node-inspector 0.10.0 with nvm 0.13.1
I will say the most consistent cases skips over debugger lines happen when running with mocha --debug is in a class like object instantiation with the new keyword.
Maybe it has something to do with jit / hotloading type of code if that helps at all.
Summary: works for me now thanks. hopefully those cases where --debug break for me helps you track stuff down

Fixed in 0.10.1

Thank you!

I am facing same problem ..i installed Ni vesion is 0.10.1
i tried with --debug-brk also

--debug-brk not running my code, node version 0.12.2 and ni 0.11.1 here. but working with --debug

windows 10 not working.

@Alex-Nabu When you say Windows 10, I'm assuming you are using the new IE Edge browser.  Is that correct?  If so, have you tried IE (not Edge) in Windows 10 or any other browsers and had different results?

@dpwolfe No I meant chome. I actually have to downgrade my nodejs version to get it working again. downgraded to 0.12.4

--debug-brk isn't working for me at all on Mac OS X 10.10.5 + Node.js 0.12.7 (64-bit) + Chrome 45.0.2454.85 (64-bit).  My startup.js script is very simple:
debugger;

var connect = require('connect');
var http    = require('http');

var app = connect();
app.use(function(req, res) {
  console.log(req.url);
  res.end('Hello from Connect!\n');
})

http.createServer(app).listen(3000);
console.log("For status, connect your web browser to http://localhost:3000");

This lands me in the weeds in module.js.  Hitting run doesn't stop at debugger.
I'm running with node --debug-brk startup.js.  startup.js is definitely loaded in the debugger.  It doesn't stop if I put a manual breakpoint there either.

node --debug-brk    doesn't work (nothing is shown in node-inspector)
% node --debug-brk ./test.js                                    # 130 17:26 ~/dev/react-starter
Debugger listening on port 5858
% node-inspector --web-port=9000         # 130 17:26 ~/dev/react-starter/node_modules/bootstrap
Node Inspector v0.12.3
Visit http://<IP_ADDRESS>:9000/?ws=<IP_ADDRESS>:9000&port=5858 to start debugging.
test.js:
console.log(1)
console.log(2)
node v0.12.2
Node Inspector v0.12.3
Description:    Ubuntu 14.04.3 LTS
Release:        14.04


Preloading hashed, static assets with rel="preload"

Hey there,
I wanted to add a link tag with rel="preload" for two fonts that I am using, so that the priority in which they are loaded is higher (especially when coming from a ServiceWorker, since they are currently prioritized as lowest — which slows down things).
I added this to my nuxt.config.js inside the link array, where all other links are:
{
  rel: 'preload',
  as: 'font',
  crossorigin: 'crossorigin',
  type: 'font/woff2',
  href: 'fonts/ApercuPro.woff2'
}

The problem I am experiencing is that the preloaded font is now being loaded twice, once the hashed version, the other time the raw, original one as can be seen here:

Ideally, only the hashed version of the file should be referenced inside href, just like Nuxt already does this with all other references to that particular file (e.g. url(/_nuxt/fonts/ApercuPro.5398148.woff2) inside style).
Sorry if I am missing something here and thank you for your feedback in advance. :) Been a happy user for a while now. ❤  Also glad to help in any way, if I can!

Hi @mixn
Normally you don't have to add yourself the preload link since Nuxt.js does it for you if you're using it into your application.
Does it perform the preload of the hased version if you remove your link into nuxt.config.js?
(Please mention me so I can keep track of this issue).

@mixn, can you try this:
nuxt.config.js
module.exports = {
  render: {
    bundleRenderer: {
      shouldPreload: (file, type) => {
        return ['script', 'style', 'font'].includes(type)
      }
    }
  }
}

Thank you for your quick response, @Atinux, really appreciate it! 💯
Nuxt does preload some scripts, but not the .woff2 fonts, which is why I wanted to add <link rel="preload" as=font crossorigin="crossorigin" type="font/woff2" href="/fonts/FontName.hash.woff2"> to the head.
If I don’t add anything to nuxt.config.js, only the aforementioned scripts get preloaded.
With
module.exports = {
  render: {
    bundleRenderer: {
      shouldPreload: (file, type) => {
        return ['script', 'style', 'font'].includes(type)
      }
    }
  }
}

in place, the font is still not preloaded. If I add + the code suggested above
{
  rel: 'preload',
  as: 'font',
  crossorigin: 'crossorigin',
  type: 'font/woff2',
  href: 'fonts/ApercuPro.woff2'
}

as before, the font (still) gets loaded twice.
Hope I am not missing anything. And thank you for your feedback! 👍

@mixn do you have a repo where I can try your implementation?

@Atinux I’ve added you as a collaborator and added the relevant stuff on its own branch (font-preload). Hope that helps? Thank you!

Can you add @pi0 as well please?

@Atinux @pi0 ✅  Thank you.

@mixn After some investigations, we have finally found the problem! It was with webpack scope hoisting which is not working well with server-renderer (SSR and Client bundle assets differ so it couldn't detect non js files for preload). Unit tests also updated to prevent this bug happening with future updates.

@pi0 @Atinux Thank you both so much! Happy it wasn’t a misunderstanding on my side — I kinda started to think that it was. 😆  Anything else I can do here? 🤓  Please let me know. And thank you again!

Should be fixed with rc8 now :) @mixn please reopen or mention if the problem still exists.
https://github.com/nuxt/nuxt.js/releases/tag/v1.0.0-rc8

@pi0 Upgraded to rc8. By adding
{ rel: 'preload', as: 'font', crossorigin: 'crossorigin', type: 'font/woff2', href: 'fonts/MyFont.woff2' }

the font still gets loaded twice. By not adding the code above, there is no link with rel="preload" added to the head.
Hope I’m not missing something. :)

@mixn Do you add render.shouldPreload too? I'm on mobile but examples/global-css is working. Also there is no need adding meta link.

@pi0 Yes, I have added
module.exports = {
  render: {
    bundleRenderer: {
      shouldPreload: (file, type) => {
        return ['script', 'style', 'font'].includes(type)
      }
    }
  }
}

to nuxt.config.js as well. When I drop
{ rel: 'preload', as: 'font', crossorigin: 'crossorigin', type: 'font/woff2', href: 'fonts/Interface-Regular.woff2' }

no fonts get preloaded via link rel="preload" in the head. :(

@pi0 @Atinux Any updates on this? ❤

what does this preload script do? I'm really confused....

 #1508

Hello. I've tried shouldPreload option today and it actually works, but with little problem.
If you have non woff2 fonts, they're being preloaded too, but they should be ignored, since browsers with ability to preload fonts can use woff2.
I made simple check in shouldPreload, buy maybe it should be done by nuxt itself? Or you can add another type to just woff2 files.
shouldPreload: (file, type) => {
  if (type === 'font') return /.woff2/.test(file)
  return ['script', 'style'].includes(type)
}

See #1838 for more


feat: add config for mode on file creation

Fixes #129

@jsumners this is ready to go. I think we can land this safely, would you like to take a quick look?


Remove BOM from project.json, *.cmd, *.sh and *.shade files.

Hi @NTaylorMullen, I'm your friendly neighborhood Microsoft Open Technologies, Inc. Pull Request Bot (You can call me MSOTBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Taylor Mullen). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla2.msopentech.com.

TTYL, MSOTBOT;


add adamamer20 as a recipe maitainers and remove estshorter

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


googleapis": "^26.0.1 does not work on the tutorial step07

On step07, when intalling googleapis(26.0.1), the latest version got error.
TypeError: google.sheets is not a function.
then googleapis(7.0.0) is work.

Thanks for the report. I've updated the instructions to install version 25 of the library.


Local storage of gps data

Every 5 minute take a sample of gps data.
We will store everything in a particular day without the need to make a request

Every 20 minutes (time of gathering 4 samples every 5 minutes) we execute OnReachedSize() method in LocationRepo.cs


improve storage wrapper

wip

storage wrapper is of debatable utility imo

better solution than #1114  but more elaborate


Bad formatting of docstrings

Describe the bug
Here in commit applied bad formatting - https://github.com/file-validator/file-validator/commit/30a211158af2caf18bf72e5534f6f8a2641c67d5

Describe the bug Here in commit applied bad formatting - 30a2111

Thanks for reporting
I will fix it


Update scala-library, scala-reflect to 2.13.8

Updates

org.scala-lang:scala-library
org.scala-lang:scala-reflect

from 2.13.5 to 2.13.8.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #40.


Add Support for AutoIt v3

https://www.autoitscript.com/site/

This fails on Travis. Since this is old, I'm closing the PR. Please resubmit if this is a PR you want to continue with.


fixes #383: Ability to authentificate to harbor using Bearer Token

related to: https://github.com/goharbor/terraform-provider-harbor/issues/383

see #409


Add logo to repo files and link to it in README header

added in https://github.com/MarkOates/allegro_flare/commit/e3d5355f9b5369b78d5d12c209c8e4b042b3f648


Title on Detail page and Main Page never update after the first time a detail page is shown (Part 3)

On Mac desktop build and iphone simulator
MAUI RC3
Mac VS 2022 RC2
After part 3
Once you select a monkey and see its detail page the title is set to that monkey.
Going back to main list does not update title (should go back to "Monkey Finder" but keeps monkey name).
Selecting a new (different) monkey does not update title on detail page (still shows original monkey's name).

Confirmed MAUI RC3, still happening

I think it is this one -> https://github.com/dotnet/maui/issues/6582

Yes, that is what I'm seeing. Thanks.


Added Microsoft Edge Dev version 91.0.864.1.

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run


FIles imported from symlinked folders are treated different then others

Description
I'm currently facing problems with importing files from symlinked folders.
Consider this example filestructure
app/
├── core/
│   ├── configuration/
│   ├── Player.js
│   └── GameServer.js
├── client/ << create-react-app
│   ├── build/
│   ├── public/
│   └── src/
│       ├── components/
│       │   └── Game.js
│       └── lib/
│           └── core/ -> ../../../core/ (SYMLINK)

/core/Player.js
export default class Player {
    constructor(
        name,
        color,
        position={x:0, y:0, z:0},
        velocity={x:0, y:0, z:0},
        rotation={x:0, y:0, z:0}
    ) {}
[...]

/client/src/components/Game.js
import React, { Component } from 'react';
import Player from '../../../lib/core/Player';

class Game extends Component {
    constructor(props) {
        console.log(Player);
    }
}

export default Game;

When having this file in /client/src/lib everything works fine, but when moving the file to the subfolder core, which is a symlink to the root of the project, things start to break.
I'm unfortunately still trying to figure out, what exactly goes wrong, but it must have to do with the webpack configuration, I think. Importing normal configuration objects from this symlink work like a charm, but something is happening (or not happening), when importing classes.
When importing from /client/src/lib console.log outputs the following:
function Player(name, color) {
        var position = arguments.length > 2 && arguments[2] !== undefined ? arguments[2] : { x: 0, y: 0, z: 0 };
        var velocity = arguments.length > 3 && arguments[3] !== …

While, when importing from the symlink /client/src/lib/core console.log outputs the following:
 class Player {
    constructor(name, color, position={x:0, y:0, z:0}, velocity={x:0, y:0, z:0}, rotation={x:0, y:0, z:0}) {....}

Expected behavior
Since I'm technically still in /src I would expect that the code is treated the same way, even though I'm importing from a symlinked folder.
Actual behavior
So some compiling doesn't happen, when importing from symlinks. Is this correct? Should this happen?
Environment
Run these commands in the project folder and fill in their results:

npm ls react-scripts (if you haven’t ejected):

<EMAIL_ADDRESS>/WebstormProjects/xxx/client
└──<EMAIL_ADDRESS>

node -v: v6.11.0
npm -v: 3.10.10

Then, specify:

Operating system: macOS 10.12.5
Browser and version: Google Chrome Version 58.0.3029.110 (64-bit)

Reproducible Demo
Will provide a demo if needed.

Also, when trying to run the build script, it throws this error
static/js/main.dc8f221c.js from UglifyJs
Unexpected token: name (Landscape) [../core/Landscape.js:5,0][static/js/main.dc8f221c.js:140702,6]

This file is written in ES6 using class. How am I able to tell the build script to handle the files the way they should? I've added a .eslintrc inside the ./core folder, but it seems to be ignored.

Hmm, that's odd! react-scripts should yell at you for importing out of src/; we need to review this.

Thanks for looking into this. If you need a reproducable demo, just ping me. :+1:

I'm afraid but "want it to work" @Timer means we should crash (since we don't currently support this use case). So not sure if it will help you 😛

Yeah, to clarify we'd basically make symlinks within src/ that point outside of something in src/ error out since it's not supported.
I did not mean to imply we'd try compiling these sources (unless that's something we should do (?)). That seems more of a webpack-specific thing, however.

The same issue mentioned here #3547

Finally I found a workaround.  You can run a watch process to compile your shared library and use it as symlink in your project. Here is my gist.


Update json4s-core, json4s-jackson, ... to 4.0.5

Updates

org.json4s:json4s-core
org.json4s:json4s-jackson
org.json4s:json4s-native

from 4.0.4 to 4.0.5.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.json4s" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #743.


Port HD to lwjgl/rlawt

Changes the OpenGL backend to use lwjgl and rlawt instead of jogl.
Incorporates the changes from https://github.com/runelite/runelite/commit/f090031, https://github.com/runelite/runelite/compare/0c56435...2141304, and https://github.com/runelite/runelite/commit/b256378.

Everything seems to be working Great for me! Great job

Me too

I tested it out a bunch and it looks like it even fixed a rare bug I was encountering sometimes. This seems great!

I tested it out a bunch and it looks like it even fixed a rare bug I was encountering sometimes. This seems great!

which one?

Was a rare crash when loading the game like rlly rare on Linux

Yeah it was some weird X11 lock error on startup, super rare happened like every 1/50 times but this definitely seems to fix it so I'm even more pleased with this LWJGL port :+1:

Any objections to adding a static import for GL43C, other than performance in IntelliJ? I don't notice a slowdown, and everything in OpenGL starts with gl or GL_ anyway. Seems like a good fit. I think this is ready to merge either way.

My only objection is that that would introduce more of a difference between the core GPU and HD plugins, which would make porting any future changes the tiniest bit more difficult. But if you're okay with that, we can do it. Just let me know and I'll make the change 🙂

Yeah, that's fine imo. The only thing I guess would be if they for instance change it to use GL33C in certain places, and there's somehow a name clash, but I think OpenGL is backwards compatible in that respect anyway. I have a branch you can cherry-pick from if you'd like here: https://github.com/aHooder/RLHD/commits/pr4. That also changes the PI constant to use Math.PI for initialization, since it's just the same number.

Updated 👍


AQL Analyzer with number return type gives odd results when getting tokens

My Environment

ArangoDB Version:        3.11.1
Deployment Mode:       Single Server
Deployment Strategy:   Manual Start
Configuration:               N/A
Infrastructure:               Own
Operating System:        Windows 10
Total RAM in your machine:       16GB
Disks in use:        SSD
Used Package:              N/A

Component, Query & Data
Affected feature:
AQL query using web interface
AQL query (if applicable):
RETURN TOKENS("abcd", "dd")

AQL explain and/or profile (if applicable):
Explain Output
Query String (27 chars, cacheable: true):
 RETURN TOKENS("abcd", "dd")

Execution plan:
 Id   NodeType          Est.   Comment
  1   SingletonNode        1   * ROOT
  2   CalculationNode      1     - LET #0 = [ [ "oMAQAAAAAAAA", "sMAQAAAAAA==", "wMAQAAA=", "0MAQ" ] ]   /* json expression */   /* const assignment */
  3   ReturnNode           1     - RETURN #0

Indexes used:
 none

Optimization rules applied:
 none

43 rule(s) executed, 1 plan(s) created, peak mem [b]: 0, exec time [s]: 0.00015

Profile Output
Query String (27 chars, cacheable: false):
 RETURN TOKENS("abcd", "dd")

Execution plan:
 Id   NodeType          Calls   Items   Filtered   Runtime [s]   Comment
  1   SingletonNode         1       1          0       0.00000   * ROOT
  2   CalculationNode       1       1          0       0.00000     - LET #0 = [ [ "oMAQAAAAAAAA", "sMAQAAAAAA==", "wMAQAAA=", "0MAQ" ] ]   /* json expression */   /* const assignment */
  3   ReturnNode            1       1          0       0.00000     - RETURN #0

Indexes used:
 none

Optimization rules applied:
 none

Query Statistics:
 Writes Exec   Writes Ign   Scan Full   Scan Index   Cache Hits/Misses   Filtered   Peak Mem [b]   Exec Time [s]
           0            0           0            0               0 / 0          0              0         0.00019

Query Profile:
 Query Stage               Duration [s]
 initializing                   0.00000
 parsing                        0.00006
 optimizing ast                 0.00002
 loading collections            0.00000
 instantiating plan             0.00001
 optimizing plan                0.00005
 instantiating executors        0.00002
 executing                      0.00001
 finalizing                     0.00001

Dataset:
You don't need data in the database to test this
Size of your Dataset on disk:
1kb
Replication Factor & Number of Shards (Cluster only):
N/A
Steps to reproduce

Create an analyzer with the following settings

{
    "name": "dd",
    "type": "aql",
    "features": [],
    "properties": {
        "queryString": "RETURN LENGTH(@param)",
        "collapsePositions": false,
        "keepNull": true,
        "batchSize": 10,
        "memoryLimit": 1048576,
        "returnType": "number"
    }
}

Try to return tokens using that analyzer e,g, RETURN TOKENS("abcd", "dd")

Problem:
It's supposed to simply return the number of characters in the input text  but it returns this:
[
  [
    [
      "oMAQAAAAAAAA",
      "sMAQAAAAAA==",
      "wMAQAAA=",
      "0MAQ"
    ]
  ]
]

Expected result:
It should return something like:
[
   4
]

I noticed 2 other things:

If I write an AQL query using the analyzer dd, it actually works

FOR doc IN someView
    SEARCH ANALYZER(doc.firstName == 3, "dd")
    RETURN doc

Even though it gives odd results when trying to get tokens, it returned the documents with first names with only 3 characters.

If I change the return type to string when creating the analyzer, gettings tokens work but of course, it returns the number of characters of the input data in string form.

This is the expected albeit not desirable behavior. The TOKENS function returns a serialization of the internal representation as it would enter the search index. For numbers but also the output of geopoint, collation, and other Analyzers, this representation is only useful internally. Some other Analyzers return regular strings as the processing is limited to e.g. tokenization and stemming without requiring a special representation.

Alright. Thank you for the explanation.


Join periodic export using the data scheme provided by evalytics

https://187350916-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUKhoh5rgfVskIr1bwi%2Fuploads%2FVssIOQb6tnLbMCj5E898%2Fdata-export.svg?alt=media&token=cfbd13aa-0af7-4b93-8354-136c671c342b

[x] questionToLabel --> questionLabel
[ ] questionScale --> questionScaleValue
[ ] question --> questionToLabel
[ ] question --> questionScale

Note:
In our exports we found that genericTopicLabel and genericTopicToLabel were empty.

Note regarding joining the question dataset with the questionScale and questionLabel data.
As questionScale has all the values of the scales, this will cause the dataframe to be longer, as we match each question hash to each scale


FEATURE: getProperty() for MessageMetadata

ObjectAccess::getGettableProperties break badly with this

ObjectAccess::getGettableProperties break badly with this, so the serialization is broken ... or I miss something

Yes, it breaks for me too. @robertlemke ?


How to complete user-defined git subcommands?

git and some other tools support user-defined subcommands by having git-some-subcommand in PATH. Running git some-subcommand runs the custom subcommand via git binary. I can't figure out how to make argcomplete support completion on that subcommand alone. Obviously it works for git-some-subcommand directly, but how to enable it via git while preserving regular git completion?

I'm not sure if that's possible with argcomplete - git registers its own completion module that gets activated when bash sees a command line that starts with git .
With that said, I have some custom git commands defined in my ~/.gitconfig, and the git completion module completes them for me.

To provide completions for git some-command, git completion looks for a function called _git_some_command.
If git-some-command is written to be completed with argcomplete, you just need to define a wrapper function that adjust the necessary completion-related variables to make it look like the original command is being completed and then calls _python_argcomplete like normal completion would.
Using the example from argcomplete docs:
chmod +x describe_github_user.py
ln -s describe_github_user.py git-describe-github-user
PATH+=:$PWD

_git_describe_github_user() {
	# remove (path to) `git` from the line
    COMP_LINE=${COMP_LINE#"$1"}
	# decrement point by a corresponding ammount
    COMP_POINT=$((COMP_POINT-${#1}))
	# call the argcomplete handler
    _python_argcomplete "git-describe-github-user"
}

and now you'll get completions for git describe-github-user as expected.


Add restricted and implicit address types

Description of change
Adds the new address types from TIP 50.
Links to any relevant issues
Closes #1220
Open Questions
There are still some todo's where we match on address, not sure what to do.

Could add type defs for the various Restricted variants for shorter names

Could add type defs for the various Restricted variants for shorter names

Tbh I personally prefer explicit names, even if rather long

They could still be pretty explicit, and would technically be more correct, like RestrictedEd25519Address


[Question] llava 1.6 use mistral 7b instruct

Question
I wondered that which version of mistral using in llava 1.6, instruct or base?

Base LLM: mistralai/Mistral-7B-Instruct-v0.2
You can check out our model card for different variants of our llava-v1.6 models. Thanks.
https://huggingface.co/liuhaotian/llava-v1.6-mistral-7b