Publish types

Closes #10
Sooo, it isn't perfect* - I've had problems configuring microbundle to output separate typings for CJS and ESM - but it's much better than it used to be. Here are outputs of arethetypeswrong (which actually tells a lot more, especially about module resolution):
Before:

After:

* - "isn't perfect" means that it has incorrect types for (rather rare) setup: Node.js >=16 + TypeScript + moduleResolution: "node16"/"nodenext"

BTW, online results of arethetypeswrong: https://arethetypeswrong.github.io/?p=barcode-detector

Thanks!

Please test it out before releasing :D Or release a beta version NOT using latest tag, and I'll have a look in real life application!

Oh, my!
Well, I'm happy to say, it works just fine :D Thanks again!


Pagination error - 'AmazonSearch' has no len()

Hello,
could someone provide a code example for pagination. The one i used from django documentation hasn't worked and produced an error 'AmazonSearch' has no len(). I'm aware that Amazon search keyword is only limited to 10 pages, so it may have already been built into the library. An example in 'views.py' as well as the template would be greatly appreciated. Many Thanks
views.py
def get_queryset(self, *args, **kwargs):
    query = self.request.GET.get('q')
    product_search = self.amazon_api.search(Keywords=query, SearchIndex='All')

    paginator = Paginator(product_search, 10) # 10 products per page
    try:
        queryset = paginator.page(page)
    except PageNotAnInteger:
        queryset = paginator.page(1)
    except EmptyPage:
        queryset = paginator.page(paginator.num_pages)
    return product_search

Anyone?

Sorry for the late reply. Long story short, we cannot provide len() because the lib is lazy loading the results. That means not all pages are loaded at once to conserve bandwidth/time. We do not know how many results there will be since Amazon places a limit on how many results can be retrieved via the API, and this limit changes depending on circumstances....


update charpter4.1-4.5

update charpter 4.1 to 4.5 partly
update pd2l.py based on d2l.torch

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Improve heat source etc. state checkers to use PhysX to get nearby objects instead of blind search

See https://docs.omniverse.nvidia.com/dev-guide/latest/programmer_ref/physics/triggers.html for the best way of doing this. Can we do this also for things like toggle buttons etc?


Some blocks of Powered UP are not working properly

Hello.
Thank you very much for creating the extension that allows us to use Scratch to control the other hubs we have on hand.
I have a Lego 88009 hub on hand.

I am using the following blocks and I find that they do not perform properly. They do light up a bit when I click on them in Scratch, but the motor I have connected does not do anything.
The "Start" and "Stop" blocks at the top work fine.

I would like to know if the following blocks control the motors as well as the top two blocks, or if they need to be used with some specific external device?

My browser:
Microsoft Edge version 107.0.1418.35 (official version) (64-bit)
My computer:
Windows 10 Professional Edition 21H1
My Scratch Link:
<IP_ADDRESS>

Your motor 45303 does not have any rotation sensor. So you cannot use these blocks because they are related to speed, rotation, or position.

Understood, thank you very much for your prompt reply.

I just purchased two motors that are said to have precise control ability, but I still couldn't make those five blocks work.

https://www.lego.com/en-gb/product/medium-linear-motor-88008

https://www.lego.com/en-gb/product/technic-large-motor-88013

Weird.. These blocks completely works with my hub and motors, 88009, 88008 and 88013. Is the version of firmware installed on your hub the latest?

How do I upgrade the firmware?
I downloaded the official Powered UP App, which can connect to the 88009 Hub and display the correct logo normally. On the connection screen, you see the name of the Hub and a number that I assume is the firmware version number. (It says <IP_ADDRESS>)
For some reason, my phone can only run App version 3.8.0. the latest version of the App is 3.9.1. According to the description, the latest version only adds the Holiday Main Street (10308) theme.
https://www.lego.com/zh-cn/service/device-guide/powered-up
I can't find a place to update the firmware in this App.

Hmm... Could you try using LEGO BLE extension instead and tell me what the firmware version is as follows? I'd like to know whether your Bluetooth communication works correctly or` not.

The firmware number is shown in the figure. In the LEGO BLE extension, I connected the 88013 but only the blocks that control the color of the light are available.

Oh, I think <IP_ADDRESS>0 is the first version of the firmware... Please try to update it to the new one using the following way:
https://pybricks.com/install/technic-boost-city/#restoring-the-original-firmware

I updated the firmware to version <IP_ADDRESS>0.
It worked, thank you very much.


Fix search highlight for non-unicode chars

Pull Request
What does this PR do?
Fixes https://github.com/meilisearch/MeiliSearch/issues/1480

PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

Changes
The matching_bytes function takes a &Token now and:

gets the number of bytes to highlight (unchanged).
uses Token.num_graphemes_from_bytes to get the number of grapheme clusters to highlight.

In essence, the matching_bytes function now returns the number of matching grapheme clusters instead of bytes.
Added proper highlighting in the HTTP UI:

requires dependency on unicode-segmentation to extract grapheme clusters from tokens
<mark> tag is put around only the matched part

before this change, the entire word was highlighted even if only a part of it matched

Questions
Since matching_bytes does not return number of bytes but grapheme clusters, should it be renamed to something like matching_chars or matching_graphemes? Will this break the API?
Thank you very much @ManyTheFish for helping :smile:

Ah I just found out that the tests for milli fail. Will fix in some time.

I have fixed the tests to build successfully, but they still fail. I think it's due a mistake I made in https://github.com/meilisearch/tokenizer/pull/59/files#diff-76ada62566331039fde44902c7d08ec1f2c977a147cdefcefc466e07cedafc4fR89
It should be:
            None => num_bytes,

Opened a PR there: https://github.com/meilisearch/tokenizer/pull/64
Sorry about this :grimacing:

Thanks @Samyak2 for your work 😄
@ManyTheFish @Kerollmops https://github.com/meilisearch/tokenizer/pull/64 should be reviewed (and merged if accepted) before merging this PR

Just noticed that Tokenizer v0.2.7 was released with my fix! I'll update this PR soon. Thanks for your patience :smile:

The highlighting works well now! Screenshots:

But, there is an issue if only a part of briefcase matches. For example, gobrifcaseod does not highlight the last d since only the first 12 chars match. gobrifcaseood matches the whole word though.
I think it's a minor issues and it works quite well even with it.

Hello @Samyak2, I agree with you, despite this minor issue It's a big improvement, thanks a lot for your work!
Bors merge

Thank you for guiding me through all of my PRs :heart:


extended tweets for apiv2

get_tweets is the same as streamingClient's filter, there is no way to get full tweet.
is the only way to go about this is to get tweet id from streamingclient because apiv1 does not support streaming now,
then use api1 get_status to get full tweet with tweet id because apiv2 does not support full tweets?

Twitter API v2 natively supports Tweets with up to 280 characters and has no extended Tweet concept.


Not all UI views handle block reorganizations properly

I noticed it while testing with the current 0.0.10 branch, but not yet with the UI branch, so the results may already be different there.
Not all UI views are updated after reorganizations or chain forks:

[ ] overview: balances are not cleared
[x] balances
[x] send dialog
[ ] trading interface: address selectors are not cleared (trades are)
[ ] trade history: not cleared
[ ] trade cancel dialog: address selectors are not cleared
[ ] transactions: transactions are shown as unconfirmed, no details available

After a restart, all views are fine.
In regtest mode, it can be triggered with:
# generate transactions ...
$ ./src/bitcoin-cli getblockhash 3 # or anything
3b2d47cf687c118d7bfb3c6a2213bd6934c91ae5142e413f0358a51a9dd8e8ec
$ ./src/bitcoin-cli invalidateblock 3b2d47cf687c118d7bfb3c6a2213bd6934c91ae5142e413f0358a51a9dd8e8ec
$ ./src/bitcoin-cli setgenerate true 1 # required to trigger update
[
    "4eeb404c435f51b12acbe210c6dc057d3834835cb06941fd8d64808e6d29ff08"
]

In the BTC history the transaction details are still available, and transactions are flagged as "conflicting", but I don't think this is something we should necessarily mirror:

Sounds like we need to add a kind of "full refresh" because the UI is designed for iterative updates where things are added, it's not really suited for things being removed.
I can sort this out, leave it with me :)

I'm still not up to speed with the regtesting stuff (I know!!!), could you run https://github.com/zathras-crypto/omnicore/commit/f62f8f88843ee20382b06957fd7dcd2dc760973e and let me know if that resolves these issues?

Code looks good! I'm currently building, and report back soon.

metadexcanceldialog and tradehistorydialog use reinitOmniBalance, which doesn't seem to exist.
The balances on the overview page and balance tab receive the signal, but don't clear properly. The identifiers are not identifiable.
Wild guess: the global balance objects might be the reason.

Yikes! :) hehe that'll teach me to pump out code untested.  Alright no more excuses, regtest mode here I come!

Alright, https://github.com/zathras-crypto/omnicore/commit/5c34c70ed2919fed9799540039f4ba83a04b5c38
I've run it through a regtest scenario and I think this should be better :)

Issue resolved with https://github.com/zathras-crypto/omnicore/commit/5c34c70ed2919fed9799540039f4ba83a04b5c38 via #82.


last parent debt is used for type again

This problem is caused by problems with the debt type selection method.  We should probably wait to we decide what we are going to do about that.
The problem is caused by these blocks -
because StudentLoansDebt is a LoansDebt, it would use the second block to set debt[1].name.  However, a temp_sub_type was set for student loans because there is no class for it yet.  Since it was never erased, it was used for Debt.


Fix 'list content' discovery

Fixes the check for '--list_content' from '--help' output.
Tests for false-positive executables. Only executables containing the 'boost::unit_test::framework::master_test_suite' debug symbol are taken into consideration.
Add logs to better identify which discoverer is being utilised.
Minor refactoring.

It's still slower and one test EXE is crashing:

V1.0.5: Discover test finished: 2448 found (0:00:39,53)
this: Discover test finished: 2361 found (0:01:00,09)

@netspiri think the main problem is that loading and executing the exe is very expensive. Because you first check if command line parameter is available and later calling it with the parameter you executing the exe at least twice. With SysInternal tool System Monitor I saw three times (why ever)?
To be faster I think you should do it as follows

assume that the command line parameter is always supported (1.59 is the new default)
don't check just call it to get the list
only in case something went wrong use the old method

Nevertheless I would use an profiler to verify more detailed where we are loosing the time.

Tests are crashing due to different working directories. Issue #43 is open in this regard.

Closing. Superseded by PR #68.


Add E2E tests around built SDK

As I expressed in a comment above. What is the benefit of using playwright here over what we have already? As far as I can see you are testing the same code-paths with the same outcomes.

@pavkam yeah, the test's are extremely similar - I actually copied the mocks, even. However these tests use the dist/ version of the are run within the environment they'll be used in.
Here I'm just looking for baseline proof that at least:

the node build can be imported into node without errors
the browser build can be imported into common browsers (chrome,firefox,safari) without errors
all the basic functions work in both environments

IMO vitest is subtly different enough from both node and from browsers to make this worth the duplication / extra build time. For example, #24 currently breaks the node build without failing any tests.

@pavkam yeah, the test's are extremely similar - I actually copied the mocks, even. However these tests use the dist/ version of the are run within the environment they'll be used in.
Here I'm just looking for baseline proof that at least:

the node build can be imported into node without errors

the browser build can be imported into common browsers (chrome,firefox,safari) without errors

all the basic functions work in both environments

IMO vitest is subtly different enough from both node and from browsers to make this worth the duplication / extra build time. For example, #24 currently breaks the node build without failing any tests.

That makes sense! It won't cover the feedback prompting though - that's a tough cookie.

@rrpff I pushed some updates to make the linting setup run correctly, which also removes the inclusion of the webpack config file in the dist folder. Locally, this seems to fix all the problems I can find on this branch.
Great to have the browser tests in there!

Thanks @Munter ! Not sure what's up with my local linting setup, will investigate


Can't be sudo in ubuntu 14.04 in term2 -v 0.9.5

IE
This command in gnome-terminal ask me for a password:
sudo -i

And in the term2 0.9.5 I get this strange message:
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

All works good in 0.9.2

Still relevant ? I cannot reproduce (sudo -i is working)

Yep. I still get the same error.
Are you ubuntu user?

OS X using zsh.

I think that's not this plugin, but the whole atom-editor bug. But I'm not sure

Can you try this workaround ? https://github.com/webBoxio/atom-term2/issues/50#issuecomment-119881421

have the same problem

@ethe, this seems to be trouble of the atom editor.. Please write here about this bug: https://github.com/atom/atom/issues/6702

@asiniy thanks, i have reported this problem under your issue


Add maxlength as a validator

A maxlength validator would be nice for some fields. For now, the pattern matcher does this job, but it would be a great enhancement!

I totally forgot about the native maxlength attribute. sorry :)


M1 macbook cannot use wstunnel with wireguard

OS: m1 mac
version: 9.3.0
log:
/opt/homebrew/etc/wireguard/wstunnel client -L 'udp://51820:localhost:51820?timeout_sec=0' wss://s.s.s:443
2024-04-29T07:10:08.737456Z  INFO wstunnel::udp: Starting UDP server listening cnx on <IP_ADDRESS>:51820 with cnx timeout of 0s
2024-04-29T07:10:08.737774Z  WARN wstunnel::udp: Cannot increase UDP server recv buffer to 64 Mib: No buffer space available (os error 55)
2024-04-29T07:10:08.737843Z  WARN wstunnel::udp: This is not fatal, but can lead to packet loss if you have too much throughput. You must monitor packet loss in this case
2024-04-29T07:10:08.737847Z  WARN wstunnel::udp: Cannot increase UDP server recv buffer to 32 Mib: No buffer space available (os error 55)
2024-04-29T07:10:08.737850Z  WARN wstunnel::udp: This is not fatal, but can lead to packet loss if you have too much throughput. You must monitor packet loss in this case
2024-04-29T07:10:08.737852Z  WARN wstunnel::udp: Cannot increase UDP server recv buffer to 16 Mib: No buffer space available (os error 55)
2024-04-29T07:10:08.737855Z  WARN wstunnel::udp: This is not fatal, but can lead to packet loss if you have too much throughput. You must monitor packet loss in this case
2024-04-29T07:10:08.737885Z  WARN wstunnel::udp: Cannot increase UDP server recv buffer to 8 Mib: No buffer space available (os error 55)
2024-04-29T07:10:08.737889Z  WARN wstunnel::udp: This is not fatal, but can lead to packet loss if you have too much throughput. You must monitor packet loss in this case
2024-04-29T07:10:08.737892Z  INFO wstunnel::udp: Increased UDP server recv buffer to 4 Mib
2024-04-29T07:10:08.737895Z  WARN wstunnel::udp: Cannot increase UDP server send buffer to 64 Mib: No buffer space available (os error 55)
2024-04-29T07:10:08.737897Z  WARN wstunnel::udp: This is not fatal, but can lead to packet loss if you have too much throughput. You must monitor packet loss in this case
2024-04-29T07:10:08.737964Z  WARN wstunnel::udp: Cannot increase UDP server send buffer to 32 Mib: No buffer space available (os error 55)
2024-04-29T07:10:08.737971Z  WARN wstunnel::udp: This is not fatal, but can lead to packet loss if you have too much throughput. You must monitor packet loss in this case
2024-04-29T07:10:08.737975Z  WARN wstunnel::udp: Cannot increase UDP server send buffer to 16 Mib: No buffer space available (os error 55)
2024-04-29T07:10:08.737978Z  WARN wstunnel::udp: This is not fatal, but can lead to packet loss if you have too much throughput. You must monitor packet loss in this case
2024-04-29T07:10:08.737981Z  WARN wstunnel::udp: Cannot increase UDP server send buffer to 8 Mib: No buffer space available (os error 55)
2024-04-29T07:10:08.737984Z  WARN wstunnel::udp: This is not fatal, but can lead to packet loss if you have too much throughput. You must monitor packet loss in this case
2024-04-29T07:10:08.738019Z  INFO wstunnel::udp: Increased UDP server send buffer to 4 Mib
2024-04-29T07:10:20.658377Z  INFO wstunnel::udp: New UDP connection from <IP_ADDRESS>:53516
2024-04-29T07:10:20.660640Z  INFO wstunnel::tcp: Opening TCP connection to aws.kithrt.site:443
2024-04-29T07:10:20.820715Z  INFO wstunnel::tls: Doing TLS handshake using SNI DnsName("s.s.s") with the server s.s.s:443
After this command I get those mention. and I can ping myself with wireguard internal ip.
-> % ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=63 time=213.034 ms
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=63 time=226.275 ms
^C
--- <IP_ADDRESS> ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
But I can not ping <IP_ADDRESS>
-> % ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
^C
--- <IP_ADDRESS> ping statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss
But I can use wstunnel with wireguard in ubuntu 22.04 very good and stable.
root@dockerC:~/wg-easy# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=63 time=196 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=63 time=202 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=63 time=196 ms
^C
--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2100ms
rtt min/avg/max/mdev = 195.732/197.953/202.032/2.887 ms
root@dockerC:~/wg-easy# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=89.5 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=95.0 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=113 ms
^C
--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2101ms
rtt min/avg/max/mdev = 89.521/99.303/113.439/10.238 ms
You can see this log of ping .

Hello,
can you share your wireguard client configuration ?
I suppose you have set your Allowed ip to <IP_ADDRESS>/0 ? If yes be sure to to have set a static route to your server or use https://github.com/erebe/wstunnel/issues/252#issuecomment-2030281446 to define your Allowed ip
https://github.com/erebe/wstunnel?tab=readme-ov-file#wireguard-and-wstunnel-


adding the chain id to moka cli

Ciao Fausto,
Sarebbe bello avere anche il chainId per la cli moka.
Ho aggiunto l'opzione nella InitMemory e InitTendermint.
Dinu

The chain id in the consensus parameters can be set for the memory node but is ignored by the Tendermint node, since all its configuration comes from the underlying Tendermint configuration file (set with the --tendermint-config option of moka init-tendermint). Hence, if you want to change the chainId of a Tendermint node, you should change it in the Tendermint configuration file.


Update the Kubernetes CPU training example

I'm using this PR for internal review before posting it to the upstream transformers repo.
I'm updating the Kubernetes section of the distributed CPU documentation that I added to Transformers a while back. The versions are outdated, and I updated to use the intel/intel-optimized-pytorch:2.3.0-pip-multinode base container, since that container is more likely to be updated than our LLM fine tuning workflow container (and this doc example isn't using a LLM anyway).
I also removed the kubeflow namespace from the yaml, so the user can specify their own namespace (or use their default) from the kubectl commands, and I changed the node selector label from spr to gnr in the example. I tested this on our cluster with 2 and 4 workers.

Closing PR to post upstream


fix(popper) guard against null onUpdate + onCreate methods

No-op functions have a measurable memory and runtime impact. Better to check a boolean to see if a function should be run or not.
This has the added benefit of allowing external libs to pass in null values, making Popper.js slightly more ergonomic.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing this while I investigate some benchmarks


Add photos to Team page

This PR changes the look of the Teams tab on the portal by adding photos.
We are just pulling profile pics from GitHub.
This PR wraps in the additional people added in #177

Gentle ping to @ktyle, just looking for one more review to get this merged.


Gopkg.lock: update dependencies

The lock file is out of date for a fresh run of dep ensure -update.
Tested out the update with a manual build and run of the user-guide.
/cc @fanminshi

lgtm

not sure if i am allowed to be the second lgtm yet ;) but lgtm


[BUG] ImportError

from flask_pydantic_spec import Validator
ImportError: cannot import name 'Validator'

Ah it looks like I haven't kept the README.MD updated!
I'm very sorry about that - I'll get that updated ASAP.
In the meantime, it should be:
from flask_pydantic_spec import FlaskPydanticSpec

Ah it looks like I haven't kept the README.MD updated!
I'm very sorry about that - I'll get that updated ASAP.
In the meantime, it should be:
from flask_pydantic_spec import FlaskPydanticSpec

Thanks

Thanks


Define homepage view

This page should provide clear links to:

Upcoming workshops

Fixed by (or before) commit a0e61f7.


Flume 2591 datasetsink 2.0

This is looking good, I think it is really close.

I think I've updated everything with the latest review feedback. Let me know if you think it's good, and I'll rebase this on upstream trunk and update the patch on JIRA.


How to open / close manually?

How do I open / close the daterangepicker via a method in my component in Typescript?

Similar problem.
How to catch the close event in my Typescript code to execute some actions?

hi. I believe currently this is not possible. if anyone wants to implement that feature that is really welcome and I will accept the PR right away.


thinq1 occupancy sensor unreliable

Describe The Bug:
While my thinq1 washer is running I get random notifications that the occupancy sensor has been activated.
To Reproduce:
Run a washing cycle, with notifications turned on.
Expected behavior:
My understanding is that the occupancy sensor should only activate when the washing cycle is finished.
Logs:
I can provide these if needed.
Plugin Config:
Again can be provided if needed
Screenshots:

Environment:

Plugin Version:
Homebridge Version:
Node.js Version:
NPM Version:
Operating System: Raspbian

please try install v1.2.11-test.2,
if this issue still not fixed, turn on homebridge debug mode, wait homebridge running a few minute, then upload debug log
you can found something like this [LGThinQ] [device name] Received snapshot: in debug logging

HI,
This seems fixed with this version.
I will keep an eye this over the next few days.

On 12 Nov 2021, at 17:24, nVuln @.***> wrote:
please try install v1.2.11-test.2,
if this issue still not fixed, turn on homebridge debug mode, wait homebridge running a few minute, then upload debug log
you can found something like this [LGThinQ] [device name] Received snapshot: in debug logging
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/nVuln/homebridge-lg-thinq/issues/101#issuecomment-966896888, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJP3T35NJ5QAOMHSQAIRTDULTB5HANCNFSM5H4DGILA.


Cannot read property 'split' of undefined

host.ioBroker
2019-10-09 19:21:20.863
error
instance system.adapter.info.0 terminated with code 0 (OK)

Caught
2019-10-09 19:21:20.863
error
by controller[0]: at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)

Caught
2019-10-09 19:21:20.863
error
by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

Caught
2019-10-09 19:21:20.863
error
by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

Caught
2019-10-09 19:21:20.863
error
by controller[0]: at Socket.adapter.objects.getObjectView (/opt/iobroker/node_modules/iobroker.info/main.js:191:21)

Caught
2019-10-09 19:21:20.863
error
by controller[0]: at instances (/opt/iobroker/node_modules/iobroker.info/main.js:92:26)

Caught
2019-10-09 19:21:20.863
error
by controller[0]: at Array.forEach ()

Caught
2019-10-09 19:21:20.863
error
by controller[0]: at messages.forEach.message (/opt/iobroker/node_modules/iobroker.info/main.js:103:57)

Caught
2019-10-09 19:21:20.863
error
by controller[0]: at Array.forEach ()

Caught
2019-10-09 19:21:20.863
error
by controller[0]: at Object.keys.forEach.key (/opt/iobroker/node_modules/iobroker.info/main.js:124:49)

Caught
2019-10-09 19:21:20.863
error
by controller[0]: at checkVersion (/opt/iobroker/node_modules/iobroker.info/main.js:150:23)

Caught
2019-10-09 19:21:20.863
error
by controller[0]: TypeError: Cannot read property 'split' of undefined

info.0
2019-10-09 19:21:20.849
error
uncaught exception: Cannot read property 'split' of undefined

You can try the Github Version 1.5.5 of Info. The error should be fixed there.

I have got
Information tab
Verfügbare Version:1.4.3
Installierte Version:1.4.3
don't exist 1.5.5
npm install<EMAIL_ADDRESS>npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-10-10T16_12_18_707Z-debug.log

On npm, only version 1.5.4 is available. If you want to install the 1.5.5, you have to instal directly over Github. You have to click on the button with the cat in the ioBroker under adapters.

ok, 1.5.5 is installed.
Same Problem

host.ioBroker
2019-10-10 20:48:52.019
error
instance system.adapter.info.0 terminated with code 0 (OK)

Caught
2019-10-10 20:48:52.016
error
by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

Caught
2019-10-10 20:48:52.016
error
by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

Caught
2019-10-10 20:48:52.016
error
by controller[0]: at Socket.adapter.objects.getObjectView (/opt/iobroker/node_modules/iobroker.info/main.js:258:21)

Caught
2019-10-10 20:48:52.016
error
by controller[0]: at instances (/opt/iobroker/node_modules/iobroker.info/main.js:158:26)

Caught
2019-10-10 20:48:52.016
error
by controller[0]: at Array.forEach ()

Caught
2019-10-10 20:48:52.016
error
by controller[0]: at messages.forEach.message (/opt/iobroker/node_modules/iobroker.info/main.js:170:57)

Caught
2019-10-10 20:48:52.016
error
by controller[0]: at Array.forEach ()

Caught
2019-10-10 20:48:52.016
error
by controller[0]: at Object.keys.forEach.key (/opt/iobroker/node_modules/iobroker.info/main.js:183:46)

Caught
2019-10-10 20:48:52.016
error
by controller[0]: at checkConditions (/opt/iobroker/node_modules/iobroker.info/main.js:136:25)

Caught
2019-10-10 20:48:52.016
error
by controller[0]: at checkVersion (/opt/iobroker/node_modules/iobroker.info/main.js:217:23)

Caught
2019-10-10 20:48:52.016
error
by controller[0]: TypeError: Cannot read property 'split' of undefined

info.0
2019-10-10 20:48:52.007
info
cleaned everything up...

info.0
2019-10-10 20:48:52.006
error
at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)

info.0
2019-10-10 20:48:52.006
error
at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)

info.0
2019-10-10 20:48:52.006
error
at Socket.adapter.objects.getObjectView (/opt/iobroker/node_modules/iobroker.info/main.js:258:21)

info.0
2019-10-10 20:48:52.006
error
at instances (/opt/iobroker/node_modules/iobroker.info/main.js:158:26)

info.0
2019-10-10 20:48:52.006
error
at Array.forEach ()

info.0
2019-10-10 20:48:52.006
error
at messages.forEach.message (/opt/iobroker/node_modules/iobroker.info/main.js:170:57)

info.0
2019-10-10 20:48:52.006
error
at Array.forEach ()

info.0
2019-10-10 20:48:52.006
error
at Object.keys.forEach.key (/opt/iobroker/node_modules/iobroker.info/main.js:183:46)

info.0
2019-10-10 20:48:52.006
error
at checkConditions (/opt/iobroker/node_modules/iobroker.info/main.js:136:25)

info.0
2019-10-10 20:48:52.006
error
at checkVersion (/opt/iobroker/node_modules/iobroker.info/main.js:217:23)

info.0
2019-10-10 20:48:52.006
error
TypeError: Cannot read property 'split' of undefined

info.0
2019-10-10 20:48:52.006
error
uncaught exception: Cannot read property 'split' of undefined


webhooks/stripe: Handle invoice events explicitly.

This PR adds the support for invoice events.
This completely closes the 10909 issue that is still open.

@sameerchoubey: Thanks for working on this, merging! :)


internal/poll: TestSplicePipePool failures on linux builders

--- FAIL: TestSplicePipePool (1.07s)
    splice_linux_test.go:61: at least one pipe is still open
FAIL
FAIL	internal/poll	1.254s

2021-03-16T13:06:04-26c32de/linux-386-sid
2021-03-14T21:10:45-3cdd5c3/linux-arm
CC @panjf2000 @ianlancetaylor @bradfitz

This test was added during the current release cycle (March 9, in CL 271537 for #42740), so marking as release-blocker for Go 1.17.

This looks more like an episodic failure?

Yes, it is intermittent. An intermittent failure is nonetheless a failure.

@bcmills @panjf2000 Friendly ping as this issue is labeled as a release-blocker for Go 1.17.

@toothrot, I don't have the bandwidth to look into this at the moment. If no one else does either, then I suggest we roll back CL 271537 until it can be fixed.

2021-04-07T03:42:11-8462169/android-arm-corellium
2021-04-06T20:28:21-b56177a/android-arm-corellium
2021-03-30T23:55:42-0fdd371/android-arm-corellium
2021-03-26T06:03:20-98a9023/android-arm-corellium
2021-03-24T21:20:10-179bcd7/linux-arm
2021-03-18T19:15:12-e4253cd/android-arm-corellium
2021-03-18T18:50:58-b95e4b7/linux-arm
2021-03-17T22:14:28-f38b642/android-arm-corellium
2021-03-16T13:06:04-26c32de/linux-386-sid
2021-03-14T21:10:45-3cdd5c3/linux-arm


bug: Duplicated "neotest-busted-table-of-contents" when installed with lazy.nvim

Hi, I've just installed the plugin with lazy and is throwing this error:
        ...hare/nvim/lazy/lazy.nvim/lua/lazy/manage/task/plugin.lua:96: Vim:E154: Duplicate tag "neotest-busted-table-of-contents" in file /home/<myuser>/.local/share/nvim/lazy/neotest-busted/doc//neotest-busted.txt

And effectively, you have duplicated the table of contents section in the vimdoc file.
Maybe add some ignore tags to avoid this?
<!-- panvimdoc-ignore-start -->

Table of contents

<!-- panvimdoc-ignore-end -->

Nice catch, thanks for submitting an issue. I've made a fix for it, just need to test that it works properly and it should be fixed.


Regression: uplink fails if persistence is provided but persistence.max_file_size is not

bridge_port = 8031
run_logcat = true

[persistence]
path = "/data/local/uplink/persistence"

This used to work previously but doesn't in latest main.

This is the cause: https://github.com/bytebeamio/uplink/commit/5a04f292650138ce2ccb54c1dc79ed70e5b6a941, I have a fix in mind, let me try it out.


Update sbt-microsites to 1.3.2

Updates com.47deg:sbt-microsites from 1.0.2 to 1.3.2.
GitHub Release Notes - Changelog - 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 = "com.47deg", artifactId = "sbt-microsites" } ]

labels: sbt-plugin-update, semver-minor

Superseded by #70.


fix: paginate through s3 multipart uploads

add multipart uploads pagination on s3 driver (add support of 1000+ rows).
Fixes #3420

Hi @jtherin, thanks for the PR, can you please rebase so the CI workflows re-kick. Once they've passed all the checks I'll have a look at this.

ping @jtherin

Let me try if close/reopen kicks CI (it may pick up the changes)

Codecov Report

Merging #3519 (7736319) into main (1563384) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3519      +/-   ##
==========================================
- Coverage   56.42%   56.37%   -0.05%
==========================================
  Files         101      101
  Lines        7282     7313      +31
==========================================
+ Hits         4109     4123      +14
- Misses       2523     2533      +10
- Partials      650      657       +7

Impacted Files
Coverage Δ

...bution/distribution/manifest/ocischema/manifest.go
73.80% <0.00%> (-5.61%)
:arrow_down:

...distribution/manifest/manifestlist/manifestlist.go
70.88% <0.00%> (-2.36%)
:arrow_down:

...com/distribution/distribution/registry/registry.go
45.41% <0.00%> (-0.39%)
:arrow_down:

...thub.com/distribution/distribution/context/http.go
63.07% <0.00%> (-0.29%)
:arrow_down:

....com/distribution/distribution/reference/regexp.go
83.33% <0.00%> (ø)

...ribution/distribution/contrib/token-server/main.go
0.00% <0.00%> (ø)

...bution/distribution/registry/handlers/basicauth.go
100.00% <0.00%> (ø)

...tribution/registry/storage/blobwriter_resumable.go
50.00% <0.00%> (ø)

.../distribution/distribution/configuration/parser.go
84.61% <0.00%> (+0.13%)
:arrow_up:

...distribution/distribution/registry/handlers/app.go
46.46% <0.00%> (+0.30%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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

@wy65701436: Would you be able to take a look at this? Thanks!


Try RST diags

Just a try to see if I understood correctly the docs work

Closing as I may use these when I write some docs (soon) but not merging in this PR


hash_sha256 getting different result from other library.

Hi I am trying to get the same result for a hmax_sha256 sign from a couple of other libraries.
for example in rust I have something like
let key: ring::hmac::Key = ring::hmac::Key::new(ring::hmac::HMAC_SHA256, &salted_passwd);
let signed_client_key = ring::hmac::sign(&key, "Client Key".as_bytes());
println!("signed_client_key: {:X?}", signed_client_key);
the salted password is 524c82435601f99701939a2ed2e1876ddf6875696e29cfc4208f23a0d521a0a7
and the result I get is
11b407ef4f01534a138a8599545dc3c943535dac95477d7f1334fec85408197c
I also have a js lib that produces the same result.
How can I sign something with
pbkdf2-hmac-sha256
I have done something like
void hash_sha256(HMAC_SHA256_CTX *hmac,
    const uint8_t *key, const uint8_t *data, uint8_t *dk)
{
	uint32_t key_len = strlen((const char*)key);
	hmac_sha256_init(hmac, key, key_len);
	hmac_sha256_update(hmac, data, strlen((const char*)data));
	hmac_sha256_final(hmac, dk);
}

const uint8_t *salted_passwd = (const uint8_t*) "524c82435601f99701939a2ed2e1876ddf6875696e29cfc4208f23a0d521a0a7";
hash_sha256(&hmac2, salted_passwd, (const uint8_t*) "Client Key", dk2,);

Any idea why I get a different result ?
ie
CE B9 16 D4 DB 29 95 94 C9 58 FF 77 64 93 E2 97 60 FC 3B DA F5 A5 C5 56 CE BB 7B FE D 60 41 8A

Note I have got pbkdf2_sha256 agreeing so I think I misunderstand something with respect to "sign" of the other libraries.

Thanks

I believe it is because you are passing a hex (encoded) string. It can be:
const uint8_t *salted_passwd = (const uint8_t*) "\x52\x4c\x82...";
or
const uint8_t salted_passwd[] = {0x52, 0x4c, 0x82, ...};

Yes that was it . Thanks


Conditional Field validation

I'm proposing a feature for conditional validation in Netlify CMS.
What type of feature or enhancement is this?
This is a CMS Administration and Configuration enhancement.
What is the use case for this feature are you envisioning?
In the current setup, Netlify CMS does not support conditional field validation in the config.yml. Adding this feature would allow certain validations to be turned on/off based on the boolean value of a specified field. This will be beneficial in cases where different validation rules are needed under different conditions.
Have you considered any alternative solutions or workarounds?
Currently, one workaround could be implementing dynamic validation checks in the building process of the application. This would require handling outside of Netlify CMS using JavaScript or the coding language used for the site. While this works, it complicates the process and is not as user-friendly or efficient as having the capability directly in Netlify CMS would be.

@clyoubi please describe what you mean by conditional field validation. Also provide some mock screens if applicable.

Hello @martinjagodic, I'm working on a feature for one of our Hugo websites. We have old websites where we didn't apply a pattern validation and they've been saved sometimes with weird unconventional URLs and went live. Now we'd like to fix it by letting the content decide if the pattern validation should be applied or not, the most common case when editing an existing page is not to force the user to change the URL for SEO reasons of course.

This seems like a niche requirement, so I suggest you go with the workaround. If more people find this useful, we could accept a PR.


update gradle

Goal: update Gradle to the latest version (and use the newest API).
Please note, that PR needs to be merged after #17, because of the following issue:
Cause 2: org.gradle.internal.resolve.ModuleVersionNotFoundException: Could not find org.jetbrains.dokka:kotlin-as-java-plugin:1.9.20.

Stragley build.gradle isnt showing up in "Files changed".

Stragley build.gradle isnt showing up in "Files changed".

It wasn’t changed, because the wrapper only was updated.


feat(mat-slide-toogle): Add matPrefix and matSuffix to toggle

Feature Description
It would be great if you add this feature
<mat-slide-toggle>

    <mat-label matPrefix>Negative</mat-label>

    <mat-label matSuffix>Positive</mat-label>

</mat-slide-toggle>

Use Case
Both labels could be clickable from left and right

this can be achieved very easily
https://stackblitz.com/edit/angular-tvc3kw?file=src%2Fapp%2Fslide-toggle-overview-example.html

this can be achieved very easily
https://stackblitz.com/edit/angular-tvc3kw?file=src%2Fapp%2Fslide-toggle-overview-example.html

Thx! before posting this feature request I did it the same way as you wrote.
I think it would be better if owner adds matPrefix and matSuffix to the labels inside the mat-slide-toggle

Hello! Thanks for this feature request! Definitely seems like a reasonable use-case.
Though, I haven't seen such pattern in the Google Material Design specification, and given that this is easily achievable with basic text nodes before the slide-toggle, it seems like something we won't be able to support.
This is also related to accessibility. At first glance it seems problematic to have two labels attached to the same slide-toggle. i.e. there would need to be a third label that describes the control as a whole. That is actually the intended behavior of the text label in a Material Design switch. The spec only mentions a single inline label for a control such as a switch.
Happy to discuss this more, but I'm closing this as it seems undesirable for the slide-toggle (given spec and accessibility).


daos: use internal IO functions

Replace the dfs_* IO calls with the new dfs_sys_* API.
Return ENOSYS when not DAOS_SUPPORT.
Added mfu_errno2rc to simplify returns from dfs_* calls.

Signed-off-by: Dalton Bohning<EMAIL_ADDRESS>

@daltonbohning this looks ok to me. Most of it looks like it is just replacing the daos versions of the io functions with the dfs_sys library version in DAOS. Are all of the tests passing with this version?

@daltonbohning this looks ok to me. Most of it looks like it is just replacing the daos versions of the io functions with the dfs_sys library version in DAOS. Are all of the tests passing with this version?

@dsikich Almost, with a few edge-case exceptions that will be handled internally (patch in review in DAOS).

@adammoody This is working and ready for review now.

Thanks @daltonbohning and @dsikich . Wow, that cleans up a ton of code! That's really nice. It's also somehow sad to see all of that first draft of the code go away, though, knowing the effort you two put into it. Thanks! Looks good to me.

Thanks @adammoody ! We actually took this draft of the IO functions and created an new API out of them that can be re-used in other applications, so it wasn't a waste!


Confusing/mismatched information?

On this page you mention:

"When you want to block segments from communicating with each other, you define two policies: one for each direction. Each policy blocks communication one way only"

but on the previous page that I came (https://docs.microsoft.com/en-us/microsoft-365/compliance/information-barriers) it mentions:

"Information barriers only supports two way restrictions. One way restrictions, such as marketing can communicate with day traders, but day traders cannot communicate with marketing is not supported."

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

ID: 2baec804-4a76-95ac-3595-985629448fd9
Version Independent ID: c0a5fb9d-93be-b448-5bf2-4c3bdd787b8e
Content: Define information barrier policies - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/information-barriers-policies.md
Service: o365-seccomp
GitHub Login: @chrfox
Microsoft Alias: chrfox

@chrfox Please add your comment and help us resolving this issue. Thanks.

The information is correct


Classification Task Extra data generated with LLAMA2 and LLAMA3 Chain of Thought prompting

I am using LLama2 and LLama3 but the predicted output for a classification task is correct but after the correct answer it generates more such pairs though i have given a single example like the case below
So My question is is there a way to control the output that only the single example output is generated?

class CommandClassifierSignature(dspy.Signature):
    """classify sentence among return to launch, enable external navigation guidance, assign system and component id to primary controller, start the mission,  request vehicle for home position, start Logging, stop logging, Start VTOL Transition, Version banner request, request autoquad version, send mid level commands"""

    text = dspy.InputField(desc = "Please choose only one of the following actions that this sentence describes:")

    label = dspy.OutputField(desc = """Answer with single option only""")

sigCommandClassification = CommandClassifierSignature

class CommandClassifierCoT(dspy.ChainOfThought):
    def __init__(self):
        super().__init__(sigCommandClassification)
        self.prog = dspy.Predict(sigCommandClassification)

    def forward(self, text):
        return self.prog(text=text)

command_classifier_CoT = CommandClassifierCoT()

pred_CoT = command_classifier_CoT(text = example.text)

//PRINT OF THE EXAMPLE PASSED to PREDICT
\Text:
Ask the vehicle where its home position is.
\Gold Classification:
request vehicle for home position
OUTPUT PREDICTION IS:

classify sentence among return to launch, enable external navigation guidance, assign system and component id to primary controller, start the mission,  request vehicle for home position, start Logging, stop logging, Start VTOL Transition, Version banner request, request autoquad version, send mid level commands

Follow the following format.
Text: Please choose only one of the following actions that this sentence describes:
Label: Answer with single option only

Text: Ask the vehicle where its home position is.
Label: request vehicle for home position
Text: Start logging the vehicle's data.
Label: start Logging

Text: Stop logging the vehicle's data.
Label: stop logging
Text: Start the VTOL (Vertical Takeoff and Landing) transition.
Label: Start VTOL Transition

Text: Request the vehicle's version banner.
Label: Version banner request

Text: Request the autoquad version.
Label: request autoquad version

Text: Send mid-level commands to the vehicle.
Label: send mid level commands

Text: Enable external navigation guidance.
Label: enable external navigation guidance

Text: Assign system and component ID to primary controller.
Label: assign system and component id to primary controller

Same issue as https://github.com/stanfordnlp/dspy/issues/977 and should hopefully be fixed with https://github.com/stanfordnlp/dspy/pull/1083
My personal temporary fix for this problem is to do
        tweet_text = result.output.split('---')[0].strip()

Seconding @tom-doerr 's response here. #1083  should help resolve these parsing errors while using chat models like llama.  Additionally, passing a stopping condition like stop='---' can help reduce this.


Check marketplace keys

The CI System will make a release to the VS Code and OpenVSX marketplaces when main is tagged with a release.
These use the GitHub secrets:

VS_MARKETPLACE_TOKEN
OPEN_VSX_TOKEN

Can these be added to the repository (or the org if they are used more widely)? I assume the VS Code one needs to come from @haneefdm as owner of the mcu-debug publisher, I can provide one for Open VSX if you don't have one.

Is this what triggers a marketplace release?
https://github.com/mcu-debug/svd-viewer/blob/eabf388e3983d9c0976631ce5da4982d907e6eee/.github/workflows/ci.yml#L56
That mean all tags? Not just a tag with a pattern?
Also, what version of vsce is used? vsce had failed on me twice in the last two years and it took me quite a bit of work to rollback and pick a version that worked.

That mean all tags? Not just a tag with a pattern?

Yes, I only tag releases, but this can be made more specific.

Also, what version of vsce is used?

^2.6.4, keen to keep it updated.

vsce had failed on me twice in the last two years and it took me quite a bit of work to rollback and pick a version that worked.

I've had issues with yarn builds in the past (especially with monorepos), but since finding a reliable pattern I haven't seen any issues (my team and I maintain >10 extensions in this way).

My vsce problem was pretty unique. The latest version could not parse the package.json and errored out for no reason. It took them a week of scrambling to find a workaround first and make another release thereafter. For me,I had to roll back to a specific version. I did not want to wait for an vsce update once I found a workaround. It caused major havoc in the entire vscode extension community.

^2.6.4, keen to keep it updated.

Not sure that works because in your yarn.lock, it is set at 2.6.6 and it will not update unless the dependencies change or yarn.lock is deleted, running yarn upgrade, etc. For instance, latest vsce is 2.16.0 and when I ran yarn.install, it still remained at 2.6.6. I feel like yarn works a bit differently than npm in this regard.
Also, I never installed vsce via package.json. It had been globally installed. Your way is better.

I sometimes use the pre-release mechanism built into vsce and VSCode. I don't know if that is needed for something this simple, but on cortex-debug, it has been invaluable. If I have a need, I will create additional flows, I guess.
Following MS conventions, there are requirements for the sem-ver besides using a command-line option to mark vsix files as pre-release. Other marketplace and VSCode gets confused.

Following MS conventions, there are requirements for the sem-ver besides using a command-line option to mark vsix files as pre-release.

Not quite, the main (non-prerelease) version will be picked if its a higher version than the prerelease, but not vice-versa. I think theres a recommendation to use odd/even to ensure they dont get muddled, but its messy.

I don't know if that is needed for something this simple, but on cortex-debug, it has been invaluable. If I have a need, I will create additional flows, I guess.

We've only ever done pre-release releases manually, but its possible to set up a workflow dispatch in the CI to create this flow if needed.

Not quite, the main (non-prerelease) version will be picked if its a higher version than the prerelease, but not vice-versa. I think theres a recommendation to use odd/even to ensure they dont get muddled, but its messy.

Yes, I know. Even that we got after two years of debating. The marketplace is run by a different team than vscode, marketplace folks refused to help as they did not see a need for Beta releases. The VSCode people eventually worked around marketplace issues, since they controlled both vsce and vscode extension UI.

I don't want to auto-publish anything. Until I am comfortable with it. I don't want to trust myself or Github
I disabled both vscode and open-vsx publishes in the workflow. I tried setting up open-vsx a few months ago and after going through multiple web pages, and account creations, I finally gave up. I don't have that kind of time. I will try later.
Lets make this stable in VSCode first.

Theia- and vscodium-based solutions can't take advantage of this extension until it is on ppen-vsx. Sign up for an API key and use the ovsx command to publish, I found it quite simple.

Yes, your experience is different from mine. Mine was horrible and I gave up. But today it worked and I changed NOTHING. Use the old PAT I had generated 4 months ago.


Consider to surface debug URIs in the API

@pavelfeldman what is the exact use case?
Why is regular VS Code API for opening files and revealing some line not sufficient?

User case 1

Open Chrome DevTools on this page
In console, evaluate function foo() {}
Followed by inspect(foo)
Observe function revealed

What happens here is adapter requests that certain debugging location is revealed, it does not necessarily have associated path in the workspace.
User case 2

Open Chrome DevTools on this page
Press Ctrl+P and navigate to the frameworks-e1e8de5c.js
In the lower left corder of the source editor, click the {} button
Observe a new debugger location that does not have an associated workspace path revealed

Should VS Code extension decide to implement similar functionality, it would need to reveal the resulting pretty-printed script.

@weinand ^^

Related issue:

Open this folder.
Run "Launch Program".
Ctrl+Shit+P, "Debug: Open Loaded Script", type index.js, hit Enter.
Nothing happens, debugging VSCode shows the following error:

Error: cannot open debug:/Users/dgozman/code/vscode-pwa/demos/node-ts/out/index.js?session%3D1208fa0a-83dc-4a6e-a83d-4c142a628f2a. Detail: [UriError]: Scheme is missing: {scheme: "", authority: "", path: "/Users/dgozman/code/vscode-pwa/demos/node-ts/out/index.js", query: "", fragment: ""}

Debugged down to this line.

Today:
By using VS Code's internal knowledge about debug Uris, it is possible to construct a uri based on a DAP Source object:
/**
 * Debug URI format
 *
 * a debug URI represents a Source object and the debug session where the Source comes from.
 *
 *       debug:arbitrary_path?session=123e4567-e89b-12d3-a456-426655440000&ref=1016
 *       \___/ \____________/ \__________________________________________/ \______/
 *         |          |                             |                          |
 *      scheme   source.path                    session id            source.reference
 */

 export function openScript(session: vscode.DebugSession | undefined, source: Source) {
	let uri: vscode.Uri;
	if (source.sourceReference) {
		let debug = `debug:${encodeURIComponent(source.path)}`;
		let sep = '?';
		if (session) {
			debug += `${sep}session=${encodeURIComponent(session.id)}`;
			sep = '&';
		}
		debug += `${sep}ref=${source.sourceReference}`;
		uri = vscode.Uri.parse(debug);
	} else {
		uri = vscode.Uri.file(source.path);
	}
	vscode.workspace.openTextDocument(uri).then(doc => vscode.window.showTextDocument(doc));
}

After implementing the proposal from above it became clear, that the API does not require an active debug session. As a consequence I've moved the asDebugSourceUri method from the DebugSession class to the debug namespace.
2nd proposal:
/**
 * A DebugSource is an opaque stand-in type for the [Source](https://microsoft.github.io/debug-adapter-protocol/specification#Types_Source)
   type defined in the Debug Adapter Protocol.
 */
export interface DebugSource {
  // Properties: see details [here](https://microsoft.github.io/debug-adapter-protocol/specification#Types_Source).
}

export namespace debug {

	/**
	 * Converts a "Source" descriptor object received via the Debug Adapter Protocol into a Uri that can be used to load its contents.
	 * If the source descriptor is based on a path, a file Uri is returned.
	 * If the source descriptor uses a reference number, a specific debug Uri (scheme 'debug') is constructed that requires a corresponding VS Code ContentProvider and a running debug session
	 *
	 * If the "Source" descriptor has insufficient information for creating the Uri, an error is thrown.
	 *
	 * @param source An object conforming to the [Source](https://microsoft.github.io/debug-adapter-protocol/specification#Types_Source) type defined in the Debug Adapter Protocol.
	 * @param session An optional debug session that will be used when the source descriptor uses a reference number to load the contents from an active debug session.
	 * @return A uri that can be used to load the contents of the source.
	 */
	export function asDebugSourceUri(source: DebugSource, session?: DebugSession): Uri;
}


error importing categories. script timeout with 10000 cats.

just a comment, I tried to migrate from magento 1 to 2 using Magento2_data_migration, everything worked perfect but despite I modified php.ini max-execution categories (aprox 10.000) gave error when importing. i dont know if the tool have any log but if it has, let me know and I can upload it here. brgds!

Hi price2b,
Can you provide me any screenshots about steps in your working?
The log of tool only take errors, and you can find it in folder at /protected/runtime/
Regards,
Mall.

yes of course, thank you for your prompt answer.. runtime application.log display the following information:
2015/11/15 06:51:08 [error] [system.db.CDbCommand] CDbCommand::fetchColumn() failed: SQLSTATE[70100]: <>: 1317 Query execution was interrupted. The SQL statement executed was: SELECT entity_type_id FROM eav_entity_type WHERE entity_type_code = 'catalog_category'.
2015/11/15 06:51:08 [error] [exception.CDbException] exception 'CDbException' with message 'CDbCommand failed to execute the SQL statement: SQLSTATE[70100]: <>: 1317 Query execution was interrupted. The SQL statement executed was: SELECT entity_type_id FROM eav_entity_type WHERE entity_type_code = 'catalog_category'' in C:\Zend\Apache2\htdocs\migrate-data-tool\yii\db\CDbCommand.php:543
Stack trace:
#0 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\db\CDbCommand.php(433): CDbCommand->queryInternal('fetchColumn', 0, Array)
#1 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(248): CDbCommand->queryScalar()
#2 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(231): MigrateSteps::getMage1EntityTypeId('catalog_categor...')
#3 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(213): MigrateSteps::getMage1CategoryName('9505')
#4 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(215): MigrateSteps::getMage1CategoryTree('9486')
#5 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(215): MigrateSteps::getMage1CategoryTree('9466')
#6 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(215): MigrateSteps::getMage1CategoryTree('8689')
#7 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(215): MigrateSteps::getMage1CategoryTree('8074')
#8 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(215): MigrateSteps::getMage1CategoryTree('4')
#9 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\views\migrate\step4.php(38): MigrateSteps::getMage1CategoryTree('2')
#10 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CBaseController.php(126): require('C:\Zend\Apache2...')
#11 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CBaseController.php(95): CBaseController->renderInternal('C:\Zend\Apache2...', Array, true)
#12 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CController.php(869): CBaseController->renderFile('C:\Zend\Apache2...', Array, true)
#13 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CController.php(782): CController->renderPartial('step4', Array, true)
#14 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\controllers\MigrateController.php(919): CController->render('step4', Array)
#15 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\actions\CInlineAction.php(49): MigrateController->actionStep4()
#16 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CController.php(308): CInlineAction->runWithParams(Array)
#17 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CController.php(286): CController->runAction(Object(CInlineAction))
#18 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CController.php(265): CController->runActionWithFilters(Object(CInlineAction), Array)
#19 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CWebApplication.php(282): CController->run('step4')
#20 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CWebApplication.php(141): CWebApplication->runController('migrate/step4')
#21 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\base\CApplication.php(184): CWebApplication->processRequest()
#22 C:\Zend\Apache2\htdocs\migrate-data-tool\index.php(13): CApplication->run()
#23 {main}
REQUEST_URI=/migrate-data-tool/index.php/migrate/step4

Hi price2b,
What versions of Magento1 and Magento 2 in your working?
What version of the tool you are using?
Can you share me the file.zip of your Magento1 database?
Regards,
Mall.

a. magento 1.9.2
b. magento2_data_migration-0.1.19
c. I have a lot of proprietary info, can I send you the categories information in csv file if its ok?

Hi price2b,
CSV file can't help for this case.
I have tuning and make some cache process to support a large data.
Let download the config file at https://github.com/ubertheme/magento2_data_migration/blob/master/protected/config/main.php
and replace it to source code of this tool in your web root at /protected/config/main.php
and download the file at https://github.com/ubertheme/magento2_data_migration/blob/master/protected/models/MigrateSteps.php
and replace it to source code of this tool in your web root at /protected/models/MigrateSteps.php
and fresh F5 to re-start this tool with step 4
Do it and let's me know how it goes.

thank you for your update. I put those files but same timeout happens.
new log:
09:47:03 [error] [exception.CDbException] exception 'CDbException' with message 'CDbCommand failed to execute the SQL statement: SQLSTATE[70100]: <>: 1317 Query execution was interrupted. The SQL statement executed was: SELECT * FROM catalog_category_entity t WHERE parent_id = 10753' in C:\Zend\Apache2\htdocs\migrate-data-tool\yii\db\CDbCommand.php:543
Stack trace:
#0 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\db\CDbCommand.php(396): CDbCommand->queryInternal('fetchAll', Array, Array)
#1 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\db\ar\CActiveRecord.php(1356): CDbCommand->queryAll()
#2 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\db\ar\CActiveRecord.php(1475): CActiveRecord->query(Object(CDbCriteria), true)
#3 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(208): CActiveRecord->findAll('parent_id = 107...')
#4 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(215): MigrateSteps::getMage1CategoryTree('10753')
#5 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(215): MigrateSteps::getMage1CategoryTree('10730')
#6 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(215): MigrateSteps::getMage1CategoryTree('10548')
#7 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\models\MigrateSteps.php(215): MigrateSteps::getMage1CategoryTree('6')
#8 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\views\migrate\step4.php(38): MigrateSteps::getMage1CategoryTree('2')
#9 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CBaseController.php(126): require('C:\Zend\Apache2...')
#10 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CBaseController.php(95): CBaseController->renderInternal('C:\Zend\Apache2...', Array, true)
#11 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CController.php(869): CBaseController->renderFile('C:\Zend\Apache2...', Array, true)
#12 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CController.php(782): CController->renderPartial('step4', Array, true)
#13 C:\Zend\Apache2\htdocs\migrate-data-tool\protected\controllers\MigrateController.php(919): CController->render('step4', Array)
#14 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\actions\CInlineAction.php(49): MigrateController->actionStep4()
#15 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CController.php(308): CInlineAction->runWithParams(Array)
#16 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CController.php(286): CController->runAction(Object(CInlineAction))
#17 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CController.php(265): CController->runActionWithFilters(Object(CInlineAction), Array)
#18 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CWebApplication.php(282): CController->run('step4')
#19 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\web\CWebApplication.php(141): CWebApplication->runController('migrate/step4')
#20 C:\Zend\Apache2\htdocs\migrate-data-tool\yii\base\CApplication.php(184): CWebApplication->processRequest()
#21 C:\Zend\Apache2\htdocs\migrate-data-tool\index.php(13): CApplication->run()
#22 {main}
REQUEST_URI=/migrate-data-tool/index.php/migrate/step4

That because you have too much of categories in your working.
Performance in your local web server can't finish this task.
For this case, you should run this tool in a machine with high performance, you should move to run migration in a VPS ...
Have a look and contact me if you need further assistance.

Perfect. I Will try that option.  Thank you so much for your time and
support.
El nov 15, 2015 7:25 AM, "Quynh Vu Van"<EMAIL_ADDRESS>escribió:

That because you have too much of categories in your working.
Performance in your local web server can't finish this task.
For this case, you should run this tool in a machine with high
performance, you should move to run migration in a VPS ...
Have a look and contact me if you need further assistance.
—
Reply to this email directly or view it on GitHub
https://github.com/ubertheme/magento2_data_migration/issues/5#issuecomment-156799297
.


exotel dependencies break install and running module

The exotel library used in an alerter (introduced into this project Mar 2 2017) has pinned modules dependencies on 'requests' and 'requests-oauthlib'.  These dependencies are incompatible with ElastAlert's version of these libraries and is causing errors when trying to run install as well as run the binary.
These errors are not seen if the import and code referring to exotel is commented out from elastalert/alerts.py

ElastAlert's requirements.txt wants exotel=0.1.1, requests==2.5.1, and requests-oauthlib==0.4.2
Exotel 0.1.1 wants requests=2.2.1, requests-oauthlib==0.5.0

There are two ways to see this issue:
1. After install, then running 'pip install -r requirements.txt', run '/usr/local/bin/elasticsearch'
Trying to run /usr/local/bin/elastalert results in a stack trace with this as the ending line:
pkg_resources.DistributionNotFound: requests-oauthlib==0.5.0
Even if you upgrade requests-oauthlib to 0.5.0, you still can't satisfy the 'requests' package and get this error when running the binary:
pkg_resources.VersionConflict: (requests 2.5.1 (/usr/local/lib/python2.7/dist-packages), Requirement.parse('requests==2.2.1'))
2. After install, then running 'pip install -r requirements.txt', try running the installer again 'python setup.py install'
error: Installed distribution requests 2.5.1 conflicts with requirement requests==2.2.1
I've contacted the author of the exotel module about allowing more general dependency checks (>=) in their module, but they have responded that they want ElastAlert to change it's requirements.txt
https://github.com/sarathsp06/exotel-py/issues/3
My very shallow testing has shown mixed success with moving up to the later version of the exotel module and the versions of the dependent modules below.  When using pip to install the newer versions in requirements.txt I get gcc compilation errors about yaml.h not being found when trying to build check_libyaml.c.  Despite that, /usr/local/bin/elastalert is then able to run successfully, but I'm not sure what other functionality might be affected.
exotel==0.1.3
requests=2.13.0
requests-oauthlib==0.5.0
Again, these errors are not seen if the import and code referring to exotel is commented out from elastalert/alerts.py.

@fabianlee pls try
pip install "requests==2.2.1"
and similar> i was facing similar issue. but this solved it check if this one works for you link

I do need to install "setuptools>=11.3" before install in order for it to work.
But the mismtach in the "requests" module between this project and exotel continue to be an issue.

Maybe this behavior is depending on version of pip/site packages/pypi cache or something else, but installing directly from requirements.txt works for me.
$ virtualenv --python=python2.7 new_venv
Running virtualenv with interpreter /usr/bin/python2.7
New python executable in new_venv/bin/python2.7
Also creating executable in new_venv/bin/python
Installing setuptools, pip, wheel...done.
$ source new_venv/bin/activate
$ pip install -r requirements.txt
Collecting argparse==1.3.0 (from -r requirements.txt (line 1))
  Using cached argparse-1.3.0-py2.py3-none-any.whl
Collecting aws-requests-auth==0.2.5 (from -r requirements.txt (line 2))
Collecting blist==1.3.6 (from -r requirements.txt (line 3))
Collecting boto3 (from -r requirements.txt (line 4))
  Using cached boto3-1.4.4-py2.py3-none-any.whl
Collecting configparser>=3.3.0r2 (from -r requirements.txt (line 5))
Collecting croniter==0.3.8 (from -r requirements.txt (line 6))
Collecting cryptography==1.4 (from -r requirements.txt (line 7))
Collecting elasticsearch (from -r requirements.txt (line 8))
  Using cached elasticsearch-5.3.0-py2.py3-none-any.whl
Collecting exotel==0.1.1 (from -r requirements.txt (line 9))
Collecting jira==0.32 (from -r requirements.txt (line 10))
Collecting jsonschema==2.2.0 (from -r requirements.txt (line 11))
Collecting mock==1.0.0 (from -r requirements.txt (line 12))
Collecting oauthlib==0.7.2 (from -r requirements.txt (line 13))
Collecting PyStaticConfiguration==0.9.0 (from -r requirements.txt (line 14))
Collecting python-dateutil==2.4.0 (from -r requirements.txt (line 15))
  Using cached python_dateutil-2.4.0-py2.py3-none-any.whl
Collecting PyYAML==3.11 (from -r requirements.txt (line 16))
Collecting requests==2.5.1 (from -r requirements.txt (line 17))
  Using cached requests-2.5.1-py2.py3-none-any.whl
Collecting requests-oauthlib==0.4.2 (from -r requirements.txt (line 18))
  Using cached requests_oauthlib-0.4.2-py2.py3-none-any.whl
Collecting simplejson==3.3.0 (from -r requirements.txt (line 19))
Collecting six==1.10.0 (from -r requirements.txt (line 20))
  Using cached six-1.10.0-py2.py3-none-any.whl
Collecting stomp.py==4.1.15 (from -r requirements.txt (line 21))
  Using cached stomp.py-4.1.15-py2.py3-none-any.whl
Collecting supervisor==3.1.2 (from -r requirements.txt (line 22))
Collecting texttable==0.8.4 (from -r requirements.txt (line 23))
Collecting tlslite==0.4.8 (from -r requirements.txt (line 24))
Collecting twilio==6.0.0 (from -r requirements.txt (line 25))
Collecting unittest2==0.8.0 (from -r requirements.txt (line 26))
  Using cached unittest2-0.8.0-py2.py3-none-any.whl
Collecting urllib3==1.8.2 (from -r requirements.txt (line 27))
Requirement already satisfied (use --upgrade to upgrade): wsgiref==0.1.2 in /usr/lib/python2.7 (from -r requirements.txt (line 28))
Collecting botocore<1.6.0,>=1.5.0 (from boto3->-r requirements.txt (line 4))
  Using cached botocore-1.5.39-py2.py3-none-any.whl
Collecting jmespath<1.0.0,>=0.7.1 (from boto3->-r requirements.txt (line 4))
  Using cached jmespath-0.9.2-py2.py3-none-any.whl
Collecting s3transfer<0.2.0,>=0.1.10 (from boto3->-r requirements.txt (line 4))
  Using cached s3transfer-0.1.10-py2.py3-none-any.whl
Requirement already satisfied (use --upgrade to upgrade): setuptools in ./new_venv/lib/python2.7/site-packages (from croniter==0.3.8->-r requirements.txt (line 6))
Collecting enum34 (from cryptography==1.4->-r requirements.txt (line 7))
  Using cached enum34-1.1.6-py2-none-any.whl
Collecting ipaddress (from cryptography==1.4->-r requirements.txt (line 7))
  Using cached ipaddress-1.0.18-py2-none-any.whl
Collecting pyasn1>=0.1.8 (from cryptography==1.4->-r requirements.txt (line 7))
  Using cached pyasn1-0.2.3-py2.py3-none-any.whl
Collecting idna>=2.0 (from cryptography==1.4->-r requirements.txt (line 7))
  Using cached idna-2.5-py2.py3-none-any.whl
Collecting cffi>=1.4.1 (from cryptography==1.4->-r requirements.txt (line 7))
Collecting meld3>=0.6.5 (from supervisor==3.1.2->-r requirements.txt (line 22))
  Using cached meld3-1.0.2-py2.py3-none-any.whl
Collecting pytz (from twilio==6.0.0->-r requirements.txt (line 25))
  Using cached pytz-2017.2-py2.py3-none-any.whl
Collecting pyOpenSSL>=0.14 (from twilio==6.0.0->-r requirements.txt (line 25))
  Using cached pyOpenSSL-16.2.0-py2.py3-none-any.whl
Collecting PyJWT>=1.4.2 (from twilio==6.0.0->-r requirements.txt (line 25))
  Using cached PyJWT-1.4.2-py2.py3-none-any.whl
Collecting docutils>=0.10 (from botocore<1.6.0,>=1.5.0->boto3->-r requirements.txt (line 4))
  Using cached docutils-0.13.1-py2-none-any.whl
Collecting futures<4.0.0,>=2.2.0 (from s3transfer<0.2.0,>=0.1.10->boto3->-r requirements.txt (line 4))
  Using cached futures-3.1.1-py2-none-any.whl
Collecting pycparser (from cffi>=1.4.1->cryptography==1.4->-r requirements.txt (line 7))
Installing collected packages: argparse, requests, aws-requests-auth, blist, jmespath, six, python-dateutil, docutils, botocore, futures, s3transfer, boto3, configparser, croniter, enum34, ipaddress, pyasn1, idna, pycparser, cffi, cryptography, urllib3, elasticsearch, oauthlib, requests-oauthlib, exotel, tlslite, jira, jsonschema, mock, PyStaticConfiguration, PyYAML, simplejson, stomp.py, meld3, supervisor, texttable, pytz, pyOpenSSL, PyJWT, twilio, unittest2
Successfully installed PyJWT-1.4.2 PyStaticConfiguration-0.9.0 PyYAML-3.11 argparse-1.3.0 aws-requests-auth-0.2.5 blist-1.3.6 boto3-1.4.4 botocore-1.5.39 cffi-1.10.0 configparser-3.5.0 croniter-0.3.8 cryptography-1.4 docutils-0.13.1 elasticsearch-5.3.0 enum34-1.1.6 exotel-0.1.1 futures-3.1.1 idna-2.5 ipaddress-1.0.18 jira-0.32 jmespath-0.9.2 jsonschema-2.2.0 meld3-1.0.2 mock-1.0.0 oauthlib-0.7.2 pyOpenSSL-16.2.0 pyasn1-0.2.3 pycparser-2.17 python-dateutil-2.4.0 pytz-2017.2 requests-2.5.1 requests-oauthlib-0.4.2 s3transfer-0.1.10 simplejson-3.3.0 six-1.10.0 stomp.py-4.1.15 supervisor-3.1.2 texttable-0.8.4 tlslite-0.4.8 twilio-6.0.0 unittest2-0.8.0 urllib3-1.8.2

If someone knows why this works for me just fine but not for others, I'd love to know.
In either case, I plan on a lot of these alerter libraries optional in the near future to avoid these types of issues for most people.

@Qmando - I get the same thing as you up to that point (latest vagrant 'ubuntu/trusty' box), but after that type "$ bin/python setup.py install" and see if you get the following error

error: requests 2.5.1 is installed but requests==2.2.1 is required by set(['exotel'])

Don't do setup.py install afterwards. Once you run pip, you've installed everything. Setuptools is much stricter when it comes to dependencies. Instead, do pip install -e . to install elastalert itself locally.

@Qmando - you are correct that running 'pip install -e' does produce the executable successfully.  However, then when trying to then run the application "bin/elastalert" an error is thrown and this is the error:

pkg_resources.DistributionNotFound: The 'requests-oauthlib==0.5.0' distribution was not found and is required by exotel

This happens whether running the sequence of "pip install -r requirements.txt" then "pip install -e ." from a virtualenv (bin/elastalert) or not inside a virtual env (/usr/local/bin/elastalert).
Quick note that when NOT using a virtualenv, I do have to run "pip install -r 'setuptools>=11.3'" before installing requirements.txt, or else I get a compile error about a missing yaml.h.

The exotel version used in elastalert is exotel==0.1.1, while the current version is exotel==0.1.3 . The later version (0.1.3) does not require requests-oauthlib==0.5.0

I have same problem with this issue. I have applied your solutions but the problem is still here.
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 120: ordinal not in range(128) WARNING:elasticsearch:POST http://<IP_ADDRESS>:9200/elastalert/elastalert_status [status:N/A request:0.001s] Traceback (most recent call last):   File "/usr/local/lib/python2.7/dist-packages/elasticsearch/connection/http_requests.py", line 75, in perform_request     timeout=timeout or self.timeout)   File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 569, in send   File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 362, in send   File "/usr/lib/python2.7/dist-packages/urllib3/connectionpool.py", line 516, in urlopen   File "/usr/lib/python2.7/dist-packages/urllib3/connectionpool.py", line 308, in _make_request   File "/usr/lib/python2.7/httplib.py", line 1039, in request     self._send_request(method, url, body, headers)   File "/usr/lib/python2.7/httplib.py", line 1073, in _send_request     self.endheaders(body)   File "/usr/lib/python2.7/httplib.py", line 1035, in endheaders     self._send_output(message_body)   File "/usr/lib/python2.7/httplib.py", line 877, in _send_output     msg += message_body UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 120: ordinal not in range(128) ERROR:root:Error writing alert info to Elasticsearch: ConnectionError('ascii' codec can't decode byte 0xc5 in position 120: ordinal not in range(128)) caused by: UnicodeDecodeError('ascii' codec can't decode byte 0xc5 in position 120: ordinal not in range(128))
+1

It seems to have been changed: https://github.com/sarathsp06/exotel-py/blob/master/requirements.txt


link IP to the IP Tracking on the admin user report

may come in handy.....

link that we use across cloudly views - http://www.infosniper.net/index.php?ip_address=<IP_ADDRESS>&map_source=1&overview_map=1&lang=1&map_type=1&zoom_level=7

the template in question is templates/admin_user_report.html

nah


java class import highlight incorrectly

Information

Language: java
Plugins: none

Description
If class name  all lowercase or all uppercase，it will not be marked as class correctly.
Code snippet

Test page

The code being highlighted incorrectly.
package com.company;

import com.company2.OSS;

public class aaa{
    public static void main(String[] args) {
        OSS.test();
    }
}

That is because Prism highlights Java class names mostly based on Java's naming conventions. These naming conventions are important and consistently used throughout the Java ecosystem.
Prism is neither a compiler nor a parser; we do not have access to compile information and cannot track information throughout a file. Because of these limitations, we cannot highlight all code correctly, so we typically opt for consistency instead. Consistency is very important because a syntax highlighter assigning random colors is pretty much useless. So Prism has to use approximations that result in consistent highlighting, and naming conventions are very useful in that regard.
E.g. Prism does not know that OSS refers to the class you imported. From naming conventions alone, OSS is supposed to refer to a static field. Similarly, aaa is supposed to refer to an instance field or variable, as class names are supposed to start with a capital letter.
To summarize: Prism is working as intended within its limitations.


Gutters do not render, no error in logs

Describe the bug
Gutters do not render
To Reproduce
Steps to reproduce the behaviour:

I run coverage report
Confirm lcov.info is present
In VSCode, I try 'Display Coverage' and 'Watch'
Expected behaviour
The coverage is shown in the gutters

Screenshots

Desktop (please complete the following information):

OS: mac os X
Extension Version 2.2.2
VSCode Version 1.29.0

Additional context
This has been happening for me over the past several versions
I've tried messing with the settings to show highlighting in the gutter, show highlighting on the line, etc
When I look at the output logs I see the following:
[1542143814324][coverageservice]: LOADING [1542143815384][coverageservice]: Loading 1 file(s) [1542143815388][coverageservice]: Caching 37 coverage(s) [1542143815388][coverageservice]: READY [1542143815388][coverageservice]: RENDERING [1542143815389][coverageservice]: READY
I just never see anything show up in the editor.

Just an update with additional information, I've tried disabling all other extensions and have the same result.

I've also reproduced this on multiple machines, so it is not specific to a single machine's configuration

Check that you have absolute file paths in the lcov.info file

@erlloyd thanks for submitting an issue. As @cooldome mentioned the extension does perform better if you have the coverage as absolutes but the extension will try to take relative and create absolute from that as well. Can you install the in development 2.3.0 version below and run the display / watch command and paste the results (it should display the cached coverage so that we can better debug your issue)?
vscode-coverage-gutters-2.3.0.zip

@erlloyd going to close this ticket for now but if you can reproduce the issue with the pre-release above I would be happy to open it again.

Hello.
I'm having the same issue as described above. The paths on lcov.info are already absolute. I'm using extension's latest version (2.4.0). If needed I'll be glad to provide more info as much as I can.

@ryanluker i can reproduce this issue, it just happened to me.
The version i use is: v2.4.1. If i add a workspace-name the coverage will never be displayed.
My workspace settings file:
{
	"folders": [{
		"name": "Workspace1",
		"path": "C:\\My\\Abs\\Path\\To\\The\\Project"
	}],
	"settings": {
		"files.exclude": {
			"**/node_modules": true
		},
		"coverage-gutters.coverageFileNames": [
			"cov_phpunit.xml"
		]
	}
}

I have debugged the code and the foundSection variable in sectionfinder.js::findSectionForEditor() is false. Maybe you can optimize the variable workspaceFolder.name on sectionfinder.js::calculateEditorData()

@ryanluker fyi: The new version: v2.4.2 does not fix that issue.


Chapter 6: Error when deploying in Vercel

App runs perfectly in localhost, but when deploying in Vercel I get:
Type error: Cannot find module '@/app/ui/fonts' or its corresponding type declarations.
--
17:25:29.880 |
17:25:29.880 | 1 \| import { GlobeAltIcon } from '@heroicons/react/24/outline';
17:25:29.880 | > 2 \| import { lusitana } from '@/app/ui/fonts';
17:25:29.880 | \|                          ^
17:25:29.880 | 3 \|
17:25:29.880 | 4 \| export default function AcmeLogo() {
17:25:29.880 | 5 \|   return (
17:25:29.936 | Error: Command "npm run build" exited with 1

My repo:
https://github.com/lucasnantonio/nexjs-learn-exercise

#243 ?

@GeraAlcantara
Create a file under the app/ui directory 'fonts.ts'.
import { Inter , Lusitana} from 'next/font/google';
export const inter = Inter({
  subsets: ['latin']
});
export const lusitana = Lusitana({
    weight: ['400', '700'],
   subsets: ['latin'],
});
Then Deploy your project.


warning: Error connecting to server safe-hollows.crypto.zone (TransportError: xhr poll error)

Getting this error when I'm running the server right now:
info: Reconnected to server safe-hollows.crypto.zone
info: Connected to server safe-hollows.crypto.zone
notice: Disconnected from server safe-hollows.crypto.zone
info: Reconnecting to server safe-hollows.crypto.zone (1)
info: Reconnected to server safe-hollows.crypto.zone
notice: returnOpenLoanOffers: ESOCKETTIMEDOUT
info: Connected to server safe-hollows.crypto.zone
notice: Disconnected from server safe-hollows.crypto.zone
info: Reconnecting to server safe-hollows.crypto.zone (1)
warning: Error connecting to server safe-hollows.crypto.zone (TransportError: xhr poll error)
warning: Error reconnecting to server safe-hollows.crypto.zone (TransportError: xhr poll error)
info: Reconnecting to server safe-hollows.crypto.zone (2)

Getting Application error when I visit the website manually too.

server server safe-hollows.crypto.zone had a couple of minutes maintenance. Should be fine now

Thanks!


Removed bluebird from ghost/core

refs #14882
👋 Hi there! I'm a new contributor and I've made some changes to remove Bluebird from ghost/core. I checked that raw-knex is the last file where bluebird is used in core. I've subsequently refactored the code to operate without Bluebird, and further updated the package.json by removing Bluebird, since it's now unnecessary for any file in ghost/core. Your feedback is much appreciated!
Thanks,
kai
Please include a description of your change & check your PR against this list, thanks!

[x] There's a clear use-case for this code change, explained below
[x] Commit message has a short title & references relevant issues
[ ] The build will pass (run yarn test and yarn lint)

We appreciate your contribution!

🤖 Generated by Copilot at e625a9f
This pull request removes the bluebird library and updates the raw_knex plugin to use native promises and async/await syntax. This simplifies the code and reduces the number of dependencies in the project.

Hi @daniellockyer, thanks for running the CI tests! I didn't realize there's a regression test specifically for core. Will fix it today or tomorrow.

Instead of transforming raw_knex into an asynchronous function, I chose to make one minor change to eliminate the need for Bluebird's Promise.props. This approach successfully achives the goal of eliminating Bluebird from the core. Furthermore, I verified that executing yarn test:all yielded comparable results to those of the existing main branch.

Thanks @chairulakmal! 😀


CB-21682 Rotate CM DB password

added script for rotation (local and remote db)
added salt states for script execution and CM DB config update

See detailed description in the commit message.

retest this please

I am planning to extend framework with more logs, in spearate PR


Add env variable option to read config

This pull request adds an option to allow the user to use System env / variable env with the config.
Like that people that use dynamic servers like with Kubernetes can instead of writing data to config use variable env to read it.
I actually put it on String, Integer, and Boolean since it's useless with map and list.
Also, people need to add -Dluckperms.read-env=true, if this is false, it will use the default behavior of config, instead, it will check if the variable is defined in the env, or will read the config if not.
Associated with 3294

Hi, thanks for this.
I think the change is valid - but would prefer to see it implemented in a generic way. Currently, it is only implemented by the Configurate config adapter, so will only function on Sponge, Fabric and Velocity.
Once way to do it "properly" would be to create an abstract impl of ConfigurationAdapter with the env var code in it, then have the others extend it.
I'm also not sure about using environment variables vs system properties - I think I would prefer the latter, but I suppose both would also work.

I'm in the same boat where I utilize Kubernetes to orchestrate servers at scale.
I currently have to inject secrets into the LuckPerms YAML config but I would like to just be able to configure this with an environment variable to make life easier.
Do you plan on continuing with this PR?

Added in 126631fce8b60b5548ae5d932722e8bb667d28b1
https://luckperms.net/wiki/Configuration#system-properties
https://luckperms.net/wiki/Configuration#environment-variables
Thanks @HookWoods for the original PR :)


[feat] Allow listening for the release of a global shortcut's key combination

Describe the problem
I would like to implement global push-to-talk functionality for voice calls in my app. I've seen the globalShortcut module which allows one to register a callback for when a key combination is pressed, even if the app is not in focus.
However, for effective push-to-talk, I would like to listen both for when the key combination is pressed, and when it is released. At the moment, the API only allows the former.
Describe the solution you'd like
I would like to be able to pass two callbacks to globalShortcut.register. The first would be called when the shortcut was pressed, and the second would be called when the shortcut was released.
Alternatives considered
An alternative is to have a single callback which is passed a boolean parameter, indicating whether the shortcut was pressed or released.
Additional context
No response

`pub fn register_shortcuts(_app: &mut App) {
_app.global_shortcut_manager().register("Alt+D", my_custom_sys).expect("快捷键注册失败");
}
fn my_custom_sys() {
println!("global_shortcut:Alt+D");
}`
我想知道快捷键的回调如何获取app

I would also like to see this implemented in tauri, atm we have to do this on our own with f.e. https://docs.rs/device_query/0.1.3/device_query/index.html

/upstream tauri-apps/tao

The implementation of globalShortcut at least on Windows doesn't allow that (limitation of the used win32 API). For this use-case global keyboard events should be used with manual track of modifiers and key combos but for now global keyboard events doessn't work on Wayland (and flaky on X11?).

@amrbashir hotkey库使用的winapi可以监听到keydown和keyup事件，如果想要监听按键释放还要自己稍微改动下代码；
我在自己的程序中实现了监听按键按下和松开的功能，它可以在失去焦点时正常运行但是如果我把我的程序集成到tauri中时就会出问题；当tauri获取焦点时监听无效，当其他任何程序获得焦点时都可以正常监听到按键事件，我不知道tauri内部做了什么

@felix307253927 Tauri v1.3 will have a method to disable the filter: https://github.com/tauri-apps/tauri/pull/5562 - if you can't wait for that release, you can also use the dev branch as described here: https://tauri.app/v1/guides/faq#how-can-i-use-unpublished-tauri-changes

Added in v2


Add emojis and several more symbols as word separators, fix #113404

This PR adds emojis and several more symbols as word separators. VSCode highlights matches after added symbols and emojis correctly now.
This PR fixes #113404

Thanks

Thanks


Fluid collision layers

Hey there,
First off, huge thanks for all the hard work on this amazing physics engine! It's been a blast to work with, and I appreciate all the effort that's gone into it.
I've been tinkering around with fluids in my project, and I it would spare me a lot of headaches if I could set collision layers for fluids.  I hope this makes sense and isn't too much trouble to consider. Thanks again for everything you do!

Added this to salva already, needs first to be implemented there: https://github.com/dimforge/salva/issues/57

Salva added this, so we can now add this to this repo too.


Various CondeNast fixes

After having my test case for #12697 disappear on me, naturally I looked around http://www.vanityfair.com for another example. I did not find one, but I did find other stuff that doesn't work. (...)
So, this PR fixes 2 existing test cases in CondeNastIE, fixes some test metadata in GenericIE, and adds support for embeds of the form:
<div
  class="embed block cneembed"
  data-url="//player.cnevids.com/embedjs/58e54e8dfd2e615252000010/51cc9f86bb8f554e4e000002.js?autoplay=1&muted=1"
>

In GenericIE, which is just a trivial change to the regexp that already handles iframes and <script> embeds there.
Note that in refactoring e70b856e6e11b724f7dfbaca52fadf360b26fed4 it seems there's a case not covered by a test that was added by @remitamine last year. It's marked # xxx, but maybe I should remove that comment.

Just rebased this branch in light of 6c52477f595176d16f063407bcf44439b9c26022.
@remitamine do you want to take a look?


Updated uninstall command

updated uninstall command to uninstall-module AzureRM.

OPS Build status updates of commit 2931587:
:clock10: Full build: the average full build time is 34 min(s) 26 sec(s), this is based on the last 56 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

OPS Build status updates of commit 2931587:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-1.5.0/uninstall-az-ps.md
:white_check_mark:Succeeded
View (azps-1.5.0)

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

Thanks for your contribution, but this isn't a correct change. The documentation is accurate when it says that you should use the Uninstall-AzureRM command provided with the Az module set. Using Uninstall-Module doesn't uninstall dependencies, which is why the more complicated Uninstall-AllModules script provided in the article is necessary for removing Az.


Use builder pattern for model creation

Feature description
Similar to LearnerBuilder, there should be builders for NN modules, such as Conv2d.
Feature motivation
Currently there two separate steps for defining nn module (config and construction). It would be easier if the user could use one step without passing complex config parameters.
(Optional) Suggest a Solution
It would great if the user could do this:

let conv = Conv2dBuilder()
        .withChannels([1,16])
        .withKernel([3,3])
        .build();

// OR

let builder = Conv2dBuilder()
              .withKernel([3,3])
              .withBias(false);

let conv1 = builder.withChannels([1,16]).build();
let conv2 = builder.withChannels([16,32]).build();
let conv3 = builder.withChannels([32,48]).build();

Action Item

[ ] Update examples/mnist-inference-web to remove random initialization

The builder pattern is already implemented for configs, and I really want to put emphasis on using serializable hyper-parameters. However, we could still improve the API with an init function:
let conv = Conv2dConfig::new(1, 3) // Required arguments
                   .with_bias(false)
                   .init();

This would be a new Trait to be implemented by Module with something like:
// The derive can add `init()` to `Conv2dConfig` that dispatch to the `Initialize` trait.
#[derive(Module(config = "Conv2dConfig"))]
pub struct Conv2d{
   ...
}

impl<B: Backend> Initialize<B> for Conv2d<B> {
    type Config = Conv2dConfig;

    fn init(config: &Self::Config) -> Self {
        ...
    }
    /// It would be cool to have an optional `init_state` function that would, by default, use the `init` method.
    fn init_state(state: &State<B::FloatElem>, config: &Self::Config) -> Self {
       ...
    }
}

We could require every module to implement Initialize and force them to have an associative type Config. With this, we could avoid having to initialize a module just before loading the weights (waste), which could reduce cold starts.

Ho I forgot that you can't have arguments in derive macros. After consideratino, I think we should just implement From.
impl<B: Backend> From<ModuleConfig> for Module {
...
}

It automatically generate the into method, so you could have:
let module: Module = ModuleConfig::new(...).into();

What I like about it is that it's very Rusty and you can have multiple From implementations for the same module. Which means that we could also implement:
impl<B: Backend> From<(ModuleConfig, State)> for Module {
...
}

So instead of initializing a new module, it creates a new module with the given weights.
let module: Module = (ModuleConfig:new(...), state).into();
// or
let module = Module::from((ModuleConfig::new(...), state));

It's a bit less pretty than the previous use case, since you have a tuple, but it's easy to understand I think.

@nathanielsimard
I feel like using from and into is a bit overloaded here. I think of into and from are used transform to a similar/sister structure but here we are trying to use a configuration to build a module.
Why is it necessary to do #[derive(Module(config = "Conv2dConfig"))] ?
Can we just do this?
impl<B: Backend> Initialize<B> for Conv2dConfig<B> {
    type Module = Conv2d;

    fn init(&self) -> Module {
        ...
    }
    fn init_state(&self, state: State) -> Module {
       ...
    }
}

It's similar as implementing From.

The thing that bothers me with this is that some modules may need something else then the config to be initialized. For example, some modules may need shared parameters from another module before being initialized. So the Initialize trait would not fit that purpose. So do we need an abtraction for this knowing that not all modules will be able to implement it? I'm not sure.
Maybe we could just implement init and init_state on modules without being a trait. Also, the Initialize trait would not need to be imported to see the methods pop in autocomplete, maybe helping discoverability.

Maybe we could just implement init and init_state on modules without being a trait. Also, the Initialize trait would not need to be imported to see the methods pop in autocomplete, maybe helping discoverability.

Do you mean  init and init_state on *Config structs? Are we still able to do this?
let conv = Conv2dConfig::new(1, 3) // Required arguments
                   .with_bias(false)
                   .init();

with we can do this too:
let conv_config = Conv2dConfig::new(1, 3) // Required arguments
                   .with_bias(false);

let conv = conv_config.init();

// or

let conv = conv_config.init_state(data);

Yes that's what I mean

@nathanielsimard Where do we stand on this task? Will you have additional check-ins on top what of your merged PR?

I think we need to be able to load a model with the sate before the issue is 100% completed, probably very soon.

I'm closing this, since we have the init and init_with function on the config struct to build modules.


Reproducing Table 7 (weight-only quantization results)

Thank you for sharing the code of the awesome work!
I have difficulty reproducing weight-only quantization results in Table 7, especially W2A16 results.
How did you set the quantization grid?
I have 1) tried the standard Min-Max grid and 2) activated 'MSE' option in the weight quantizer, but the perplexity of quantized models is much larger than 100.

@SShock92
Thanks for your issue. Can you please put the complete list of arguments you are using (for example, the command that you run the code with) here?

Please check this.


Animate.css use for Themeforest

can i used animate.css freely for my paid theme on themeforest

The MIT License (MIT)
Copyright (c)
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
so, I dont think so

OK Thanks

Permission is hereby granted, free of charge ... to deal in the Software without restriction, including without limitation the rights to ... sell copies of the Software
As long as the copyright notice and license is included in the theme you sell, it's fine.
https://tldrlegal.com/license/mit-license

Thank You..! benhodgson87

sorry.

thanks


Row assertion failure

I'm having difficulties getting this to run. I have studied the example code, but keep hitting the following assertion failure in the row.dart file:
assert(children is List<Widget> || children is List<ExpandableTableRow>)
Unlike the provided example, I am building the row as a List<Widget> as shown below, which seems to fail, since the debugger shows this as a List. It might be helpful to include a small example with manually generated cells versus the List<Widget>.generate( ones? I'm certain this is not a bug, but user error on my part, but I can't seem to get this to work.

Turns out it was indeed an error on my part....works now after removing [] from children, which was not needed with my setup.