cannot delete emails and delete button missing

Hello all,
Really liking Nylas Mail so far, been using it for a couple months now.
OS: elementary Loki (Ubuntu 16.04.2 LTS)
Nylas Mail version: 2.0.10
Summary of issue: On some IMAP accounts, there is no delete button available (as in not even displayed) when viewing a message, and there is no response to pressing the 'delete' key either.
More details: I just moved my websites to a new server and this was not an issue before.  So, it appears to be happening only with certain server configurations, and gmail is not affected, either.  I'm not sure how to troubleshoot it as the actual account configuration is set up just fine and everything else works.  The previous host was with GoDaddy, and the new one is DreamHost.  I'm using their secure connections to the mail server.
I'm pasting below a snip from the error log.  It is complaining repeatedly about an authentication error, and yet I am receiving emails and have checked that it is in fact correct.  In addition, I cannot create folders and when Nylas tries to create a 'snooze' category it logs getting the same error.

{"host":"aaron-desktop","timestamp":"2017-06-22T03:02:54.237Z","payload":{"fingerprint":["{{ default }}","sync loop","Error: Authentication failed."],"rateLimit":{"ratePerHour":30,"key":"SyncError:SyncLoop:Error: Authentication failed."},"pluginIds":[]}}
{"host":"aaron-desktop","timestamp":"2017-06-22T03:02:54.237Z","payload":"{ Error: Error: Authentication failed.\n    at NylasError (errors.es6:1:8)\n    at IMAPAuthenticationError (imap-errors.es6:29:5)\n    at convertImapError (imap-errors.es6:142:15)\n    at wrappedReject (imap-connection.es6:245:34)\n    at Connection.onErrored (imap-connection.es6:254:11)\n    at emitOne (events.js:101:20)\n    at Connection.emit (events.js:188:7)\n    at reentry (/usr/share/nylas-mail/resources/app.asar/node_modules/isomorphic-core/node_modules/imap/lib/Connection.js:1610:12)\n    at Connection.checkCaps (/usr/share/nylas-mail/resources/app.asar/node_modules/isomorphic-core/node_modules/imap/lib/Connection.js:1635:22)\n    at Connection._resTagged (/usr/share/nylas-mail/resources/app.asar/node_modules/isomorphic-core/node_modules/imap/lib/Connection.js:1535:22)\n    at Parser.<anonymous> (/usr/share/nylas-mail/resources/app.asar/node_modules/isomorphic-core/node_modules/imap/lib/Connection.js:194:10)\n    at emitOne (events.js:96:13)\n    at Parser.emit (events.js:188:7)\n    at Parser._resTagged (/usr/share/nylas-mail/resources/app.asar/node_modules/isomorphic-core/node_modules/imap/lib/Parser.js:179:10)\n    at Parser._parse (/usr/share/nylas-mail/resources/app.asar/node_modules/isomorphic-core/node_modules/imap/lib/Parser.js:143:16)\n    at Parser._tryread (/usr/share/nylas-mail/resources/app.asar/node_modules/isomorphic-core/node_modules/imap/lib/Parser.js:86:15)\n    at TLSSocket.Parser._cbReadable (/usr/share/nylas-mail/resources/app.asar/node_modules/isomorphic-core/node_modules/imap/lib/Parser.js:57:12)\n    at emitNone (events.js:86:13)\n    at TLSSocket.emit (events.js:185:7)\n    at emitReadable_ (_stream_readable.js:432:10)\n    at emitReadable (_stream_readable.js:426:7)\n    at readableAddChunk (_stream_readable.js:187:13)\n    at TLSWrap.onread (net.js:543:20)\n    at Socket.ondata (_stream_wrap.js:58:20)\n    at emitOne (events.js:96:13)\n    at Socket.emit (events.js:188:7)\n    at readableAddChunk (_stream_readable.js:176:18)\n    at TCP.onread (net.js:543:20)\n  message: 'Error: Authentication failed.',\n  userMessage: 'Incorrect IMAP username or password.',\n  statusCode: 401,\n  source: 'authentication' } { fingerprint: [ '{{ default }}', 'sync loop', 'Error: Authentication failed.' ],\n  pluginIds: [] }\n"}

this is way old..


Cannot publish 2 images with rancher-pipeline

What kind of request is this :
Bug
Steps to reproduce (least amount of steps as possible):
Make a pipeline with 2 publishimagesteps
stages:
- name: test1
  steps:
  - publishImageConfig:
      dockerfilePath: ./server/Dockerfile
      buildContext: ./server
      tag: test/test:1.0
- name: test2
  steps:
  - publishImageConfig:
      dockerfilePath: ./test/Dockerfile
      buildContext: ./test
      tag: test2/test2:1.0

Result:
Second publish image will have status:
11:32:11 [pipeline_p-7pc6h-5] Running shell script
11:32:13 + /usr/local/bin/dockerd-entrypoint.sh /bin/drone-docker
11:32:13 + /usr/local/bin/dockerd -g /var/lib/docker
11:33:09 EXITCODE   0time="2018-11-16T11:33:02Z" level=fatal msg="Error authenticating: exit status 1"

It's impossible to build 2 images with one pipeline now
Environment information

Rancher version: v2.1.2-rc12
Installation option (single install/HA): single install

The cause is that currently the docker daemon storage path is sharing among containers in the build pod, but in docker's design /var/lib/docker is intended to be managed by a single daemon.
For muliple publish steps, we can:

have multiple independent docker daemon
set up dockerd in the first step and share it with the rest publish steps.

We are also investigating having a centralized dockerd in a project for caching purpose.
Workaround in v2.1.1:
You can try the following to bypass the conflict:
stages:
- name: test1
  steps:
  - publishImageConfig:
      dockerfilePath: ./server/Dockerfile
      buildContext: ./server
      tag: test/test:1.0
- name: test2
  steps:
  - publishImageConfig:
      dockerfilePath: ./test/Dockerfile
      buildContext: ./test
      tag: test2/test2:1.0
    env:
      PLUGIN_STORAGE_PATH: /var/lib/docker2

@pensiero It might be a docker related issue. Could you open another issue and provide docker info for your environment? We can help diagnose then.

@aggelito thank you! It worked great with your fix!

@gitlawr I solved with @aggelito workaround

Confirmed, it works smoothly (without any workaround) with v2.2.1 (didn't try with v2.2.0)

v2.2.1 was working smoothly; having the issue again with v2.2.3

I'm using rancher v2.3.3 and got this exact same error. I had to use @aggelito's workaround to get it working.

I am also using rancher v2.3.3 and the same error still exists. I have similar setup like @edergillian

For me, I have experienced the problem in Rancher 2.3.3, but it is intermittent. Parallel build works 2/3 of the times, and I had 3 PublishImage.

This still seems to be an issue even with the workarounds. I have ~25% success rate on the builds with publishing two images. Is this still being looked at?

@metajar I actually have 100% success rate with the new changes. I've implemented it as below:
`- name: Publish Image 1
steps:

publishImageConfig:
dockerfilePath: .
buildContext: .
tag: <TAG_NAME>:${CICD_EXECUTION_SEQUENCE}
name: Publish Image 2
steps:

publishImageConfig:
dockerfilePath: .
buildContext: .
tag: <TAG_NAME2>:${CICD_EXECUTION_SEQUENCE}
env:
PLUGIN_STORAGE_PATH: /var/lib/docker/2`

It only means that it builds one image at a time, which was not the case previously.


Add /office_users endpoint for admin API

Description
As an System Admin
I want to query the office user list admin endpoint
So I can verify who has office permissions
Reviewer Notes

Is there anything else I need to do to make sure the endpoint is unreachable to people that aren't logged in?

Setup

make server_run
make server_test

Code Review Verification Steps

[x] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

@mikena-truss do you think this is ok to merge?


Pro account vanity URL not working

I got a pro account a few months back and my vanity URL is not redirecting correctly (I assumed it was a manual process, so I gave it time). Using <vanity>.jsbin.com/<binID> simply redirects to output.jsbin.com/<binID> and pushing a bin to the vanity URL itself says it succeeds, but it does not.
Username is Xinchro

Hey, not to bother...but has this been looked into?

Hey sorry, I've been trying to look at this but not making any progress. I think I need to double check the logic around the redirect to output (which is relatively recent too).

Same issue with me. I clicked "Publish to my vanity homepage" while viewing one of my projects, and it gave me this link:
http://brentoncozby.jsbin.com/
...but this takes me to a blank JSBin project (http://jsbin.com/?html,css,js,output).

I'm taking a look at this now.

Took a lot of digging, but managed to get there in the end.
@Xinchro sorry for the delay getting this one to land!

@remy Thanks Remy! Works now. :)
http://brentoncozby.jsbin.com/

@remy 10/10 Great work. Thanks!


xone: fix kernel 6.11 compatibility

Description of changes
Fixes build on 6.11 kernel.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[X] Fits CONTRIBUTING.md.

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

I'm fine merging that. There should also be a backport for 24.05 cause it breaks this version of nixos with latest as well. Did the same with the framework-laptop-kmod

fixes https://hydra.nixos.org/build/272715506

@ofborg build linuxKernel.packages.linux_6_11.xone


Create Blog “example”

Automatically generated by Netlify CMS

👷 Deploy Preview for famous-kulfi-ae21db processing.

Name
Link

🔨 Latest commit
9577ad7e67e3896f1bc895de4ef7a2da324f1157

🔍 Latest deploy log
https://app.netlify.com/sites/famous-kulfi-ae21db/deploys/6580878353b6050008dc9158


Add new device YAML uses deprecated LibreTiny component

The LibreTiny component was split between supported chip families but the "New Device" button still generates the old format YAML.
EspHome Libretiny v2023.9.0-dev installed within Home Assistant as Addon.
Reproduce: Click on New Device. Select any LibreTiny board. View YAML config. Shows:
libretiny:
  board: cb3s
  framework:
    version: dev

When it should be:
bk72xx:
  board: cb3s
  framework:
    version: dev

How did you install the add-on? (and where from exactly)
LibreTiny has been merged into ESPHome already, and is available in the official dev channel of ESPHome add-on. That version doesn't have LibreTiny in the wizard at all (decision of the team to postpone modifying the wizard).

Also available in the beta channel of ESPHome :)

How did you install the add-on? (and where from exactly)
LibreTiny ESPHome was installed as Addon within HAOS virtual machine.

LibreTiny has been merged into ESPHome already...
OK, great to hear that. Will migrate configs.

Migrated configs from LibreTiny ESPhome and everything works. Uninstalled LibreTiny ESPhome.
Thanks for the great work on this. Its a real game changer that the Beken chips are supported.


delete it

delete it

Hey Airdrop!
Your Golden Ticket:
At Hey, we hold our community in high esteem and want to extend our gratitude for your steadfast support. That's why you've clinched a spot in this exclusive airdrop bonanza. We've taken notice of your lively engagement, contributions, or unwavering loyalty to the Hey ecosystem, and we believe it's time for you to enjoy the fruits of this special airdrop.
By participating in this exclusive event, you stand to receive Hey tokens as a token of our appreciation. These tokens open doors to thrilling possibilities within the Hey ecosystem, offering access to exclusive features, a voice in governance decisions, and even potential future perks.
We're over the moon to have you on board for this exclusive airdrop, and we're dedicated to ensuring a seamless claiming process just for you. Let's dive in and grab those Hey Airdrop tokens!

Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Verify your eligibility for the Hey Airdrop right here.

Engage for Extra Rewards:

Join community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Feel free to share your experiences or ask any questions about claiming the Hey Airdrop in the comments below. Let's make this process a breeze for everyone!

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.


CI built debian images fail to start a container

Recently, all of the PRs I opened fail at CI to start debian image containers with the notorious Failed to check if grpc server is working err msg.
Looking at the logs, there's this in the (kata-proxy reported) Linux journal message:
Failed to isolate default target, freezing.

This is not reproducible on my local machine.
Longer log:
Freeing unused kernel image memory: 1132K
Run /usr/lib/systemd/systemd as init process
systemd[1]: Mounting cgroup to /sys/fs/cgroup/blkio of type cgroup with options blkio.
systemd[1]: Mounting cgroup to /sys/fs/cgroup/pids of type cgroup with options pids.
systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpu,cpuacct of type cgroup with options cpu,cpuacct.
systemd[1]: Mounting cgroup to /sys/fs/cgroup/freezer of type cgroup with options freezer.
systemd[1]: Mounting cgroup to /sys/fs/cgroup/perf_event of type cgroup with options perf_event.
systemd[1]: Mounting cgroup to /sys/fs/cgroup/net_cls,net_prio of type cgroup with options net_cls,net_prio.
systemd[1]: Mounting cgroup to /sys/fs/cgroup/devices of type cgroup with options devices.
systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpuset of type cgroup with options cpuset.
systemd[1]: Mounting cgroup to /sys/fs/cgroup/memory of type cgroup with options memory.
systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
msg="
msg="Welcome to \x1b[1mDebian GNU/Linux 9 (stretch)\x1b[0m!
msg="
systemd-sysv-generator[68]: Native unit for procps.service already exists, skipping.
systemd-sysv-generator[68]: Native unit for chrony.service already exists, skipping.
systemd-sysv-generator[68]: Native unit for hwclock.service already exists, skipping.
systemd-sysv-generator[68]: Ignoring S01chrony symlink in rc2.d, not generating chrony.service.
systemd-sysv-generator[68]: Ignoring S01chrony symlink in rc3.d, not generating chrony.service.
systemd-sysv-generator[68]: Ignoring S01chrony symlink in rc4.d, not generating chrony.service.
systemd-sysv-generator[68]: Ignoring S01chrony symlink in rc5.d, not generating chrony.service.
Failed to isolate default target, freezing.
systemd: 89 output lines suppressed due to ratelimiting

@grahamwhaley I mentioned you this earlier today

@marcov - yes, I'd seen that error here: https://github.com/kata-containers/osbuilder/pull/265#issuecomment-503466741.

@chavafg @GabyCT - known issue? Seen it before?

I could replicate that in a clean setup (thanks @grahamwhaley), and I have a copy of a "bad" image. I'll play around with it a bit today.

A problem I found is that the kata-containers.target Requires=tmp.mount, that does not exist as a service. This solved the issue for me, but I am not 100% if that's a red herring for another problem.


[FEATURE] Improvement for backup process

(1) Change the order of the backup to
0 = Google
1 = iCloud
2 = PassKey
3 = Recovery Phrase
(2) Create the progress bar above the backup page to visually track the backup process.

(3) Create two separate pages: one for create the seed phrase and the other for displaying it. Add an overlay to the first page.

(4) Update the summary page to the latest design

This issue already fixed in Android prod version r2.4.11


Add Favorite(MyPlan) Tab for iOS

Overview (Required)

add favorite(my plan) tab
fix layout of tabs

Screenshot

Before
After

Cool 🆒

LGTM 👍


bge-reranker is extreamly slow

With 686 tokens, a single run would take more than 6 secodns on a 96C machine.
Here is the profiling data for compute graph.
bge-reranker-dump.txt
Any advice for better performance?

This is strange. You can check your CPU utilization, and try -n 96.

This is strange. You can check your CPU utilization, and try -n 96.

I wrote a simple test to reproduce the issue: https://github.com/foldl/chatllm.cpp/pull/25
PS. I accidentally created a PR which is cancelled. Please just ignore the related notifications.

I tested with num_thread=1  and num_thread=96. Single thread setup is slower than the 96-thread setup.  Within a loop of 100 iterations, all cores are fully burned, so I believe the it's correctly scheduled.

I have test this data, using "hello" as question. With Q8 quantization, it took less than 2sec on a 8-core 7735.
https://raw.githubusercontent.com/huggingface/hf-endpointsdocumentation/main/docs/source/guides/create_endpoint.mdx
Let me assume that the model file is saved on SSD. The result (>6 sec) looks impossible.

I have test this data, using "hello" as question. With Q8 quantization, it took less than 2sec on a 8-core 7735.
https://raw.githubusercontent.com/huggingface/hf-endpointsdocumentation/main/docs/source/guides/create_endpoint.mdx
Let me assume that the model file is saved on SSD. The result (>6 sec) looks impossible.

Could share the SHA256 of the checkpoint you are using? So that I can check if my conversion is valid.
The bin file is converted using your convert.py script, and its SHA256 digest is b3e05dbe06c0aa52fd974d9c9dedbc51292b81f2f285d56113c060a0931a7f0f.

You can find some quantized models (BGE-Reranker included) here:
https://modelscope.cn/models/judd2024/chatllm_quantized_models/files
I have test both Q8 and Q4_1. This model is very small, and throughput should be much higher.

You can find some quantized models (BGE-Reranker included) here:
https://modelscope.cn/models/judd2024/chatllm_quantized_models/files
I have test both Q8 and Q4_1. This model is very small, and throughput should be much higher.

Well, I downloaded models you mentioned and re-run the tests.
With Q4 variants of BGE models, it indeed has latency around 2s.  I was testing with Q8 models.
https://github.com/RobinQu/chatllm.cpp/blob/perf/test.cpp
qa_rank: num_threads=1, elapsed=12003
qa_rank: num_threads=10, elapsed=1722
qa_rank: num_threads=192, elapsed=1248
text_embedding: num_threads=1, elapsed=11963
text_embedding: num_threads=10, elapsed=1730
text_embedding: num_threads=192, elapsed=1017

BTW, it seems more threads won't help in terms latency. I would try with a multi-instance setup for higher thourughput in production.
Any other advice?

On a 96C machine, data shows that throughput is saturated at just 48 threads, so RAM throughput is the bottleneck now. A simple calculation: assuming model file size is 2GB, 400 tokens per second requires RAM throughput > 800GB/s.

Oh, such calculation applies to token generation, but not batch prompt evaluation.

EPYC 9004 series claim to have 460GB/s bandwidth for single socket configuration. But the benchmarks inference won't benfit much more with 48 threads setup. I think you are right about the bottleneck on RAM throughput.
Maybe optimizaiton like flashattention should be considered. But I am not sure if it perfroms well on CPU.


[Support] Is there a way to increase WireGuard speed?

In raising this issue, I confirm the following:

[x] I have read and understood the contributors guide.
[X] The issue I am reporting can be replicated.
[X] The issue I am reporting can be is directly related to the pivpn installer script.
[X] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

Issue
Hi folks!
Today I formatted my SD card, installed the newest raspbian lite and set up a WireGuard server via pivpn on my Raspberry Pi 3 Model B+. The pivpn setup was seamless and WireGuard clients on my iPhone and MacBook are working great. Thanks a lot folks!
Now, about performance. I have a 200 Mbit/s up/down fiber optics connection and WireGuard manages to reach 97Mbit/s up/down on speedtest.net (server and client are using ethernet). Yes, I know, Iiperf would most likely report higher numbers, but I wanted to check "real-life" speeds. The download speed (97 Mbit/s) is a slight improvement over OpenVPN (86 Mbit/s), while upload speed (97 Mbit/s) is a significant improvement over OpenVPN (67 Mbit/s). I can also see that CPU load of my Raspberry Pi 3 Model B+ is only ~22%.
Now, I browsed the web and issues in this repo, but I could not find speed reports from others. Hence, my question - is there a way to significantly increase the WireGuard speed by changing some aspects of the pivpn WireGuard config on my Raspberry Pi 3 Model B+? If not, will an upgrade to Raspberry Pi 4 Model B allow to increase the speed relative to what I have right now? If yes, what speeds are you experiencing on Pi 4?
Thanks!

Have you searched for similar issues and solutions?
Yes
Console output of      curl -L install.pivpn.dev | bash
  I got the blue Existing Install Detected! screen in my Terminal. What exactly should I post here?

Console output of      pivpn add or pivpn add nopass
 Enter a Name for the Client:

Console output of      pivpn debug
  ::::		PiVPN debug		 ::::
=============================================
::::		Latest commit		 ::::
commit f045e3935d12e1eb714fa0f630b021209e926aef (grafted, HEAD -> master, origin/test, origin/master, origin/HEAD)
Author: Orazio<EMAIL_ADDRESS>Date:   Mon Mar 23 08:48:19 2020 +0100

    Merge pull request #991 from rayden84/typo-fix

    Update install.sh
=============================================
::::	    Installation settings    	 ::::
PLAT=Raspbian
OSCN=buster
USING_UFW=0
IPv4dev=eth0
dhcpReserv=1
IPv4addr=<IP_ADDRESS>/24
IPv4gw=<IP_ADDRESS>
install_user=pi
install_home=/home/pi
VPN=wireguard
pivpnPORT=1194
pivpnDNS1=<IP_ADDRESS>
pivpnDNS2=<IP_ADDRESS>
pivpnHOST=REDACTED
INPUT_CHAIN_EDITED=0
FORWARD_CHAIN_EDITED=0
pivpnPROTO=udp
pivpnDEV=wg0
pivpnNET=<IP_ADDRESS>
subnetClass=24
UNATTUPG=1
INSTALLED_PACKAGES=(git dnsutils iptables-persistent raspberrypi-kernel-headers wireguard wireguard-tools wireguard-dkms qrencode unattended-upgrades)
=============================================
::::  Server configuration shown below   ::::
[Interface]
PrivateKey = server_priv
Address = <IP_ADDRESS>/24
ListenPort = 1194
# begin reinis
[Peer]
PublicKey = reinis_pub
PresharedKey = psk
AllowedIPs = <IP_ADDRESS>/32
# end reinis
# begin macbook
[Peer]
PublicKey = macbook_pub
PresharedKey = psk
AllowedIPs = <IP_ADDRESS>/32
# end macbook
=============================================
::::  Client configuration shown below   ::::
[Interface]
PrivateKey = reinis_priv
Address = <IP_ADDRESS>/24
DNS = <IP_ADDRESS>, <IP_ADDRESS>

[Peer]
PublicKey = server_pub
PresharedKey = psk
Endpoint = REDACTED:1194
AllowedIPs = <IP_ADDRESS>/0, ::0/0
=============================================
:::: 	Recursive list of files in	 ::::
::::	[4m/etc/wireguard shown below	 ::::
/etc/wireguard:
configs  keys  wg0.conf

/etc/wireguard/configs:
clients.txt  macbook.conf  reinis.conf

/etc/wireguard/keys:
macbook_priv  macbook_pub  psk	reinis_priv  reinis_pub  server_priv  server_pub
=============================================
::::		Self check		 ::::
:: [OK] IP forwarding is enabled
:: [OK] Iptables MASQUERADE rule set
:: [OK] WireGuard is running
:: [OK] WireGuard is enabled (it will automatically start on reboot)
:: [OK] WireGuard is listening on port 1194/udp
=============================================
:::: Having trouble connecting? Take a look at the FAQ:
:::: https://github.com/pivpn/pivpn/wiki/FAQ
=============================================
:::: WARNING: This script should have automatically masked sensitive       ::::
:::: information, however, still make sure that PrivateKey, PublicKey      ::::
:::: and PresharedKey are masked before reporting an issue. An example key ::::
:::: that you should NOT see in this log looks like this:                  ::::
:::: YIAoJVsdIeyvXfGGDDadHh6AxsMRymZTnnzZoAb9cxRe                          ::::
=============================================
::::		Debug complete		 ::::

Have you taken any steps towards solving your issue?
I searched online, but could not find an answer.

Not related to PiVPN, though here's my take: maybe check if your ethernet cable on the rapberry Pi support 1 Gigabit/s, the 3B+ should be able to do more than 100 Megabit/s. Do you get 200 Megabit/s using speedtest-cli on the 3B+?

Not related to PiVPN, though here's my take: maybe check if your ethernet cable on the rapberry Pi support 1 Gigabit/s, the 3B+ should be able to do more than 100 Megabit/s. Do you get 200 Megabit/s using speedtest-cli on the 3B+?

Hi! Thanks for the response. I checked the ethernet cable with my laptop - I can confirm 200 Mbit/s up/down. I also run speedtest-cli on 3B+ and here's the output (I wonder why upload is only 150 Mbit/s - SD card limitation? other limitation?).
pi@wireguard:~ $ python speedtest.py --server 1268
Retrieving speedtest.net configuration...
Testing from TET (REDACTED)...
Retrieving speedtest.net server list...
Retrieving information for the selected server...
Hosted by Tet (Riga) [0.38 km]: 8.072 ms
Testing download speed................................................................................
Download: 203.16 Mbit/s
Testing upload speed................................................................................................
Upload: 152.51 Mbit/s

I also run speedtest-cli on 3B+ and here's the output (I wonder why upload is only 150 Mbit/s - SD card limitation? other limitation?).

I don't know, probably CPU power? Quirks with that specific speedtest server: https://github.com/sivel/speedtest-cli#inconsistency. Most likely not an SD card issue, the test should be performed in RAM.
There are not many knobs with WireGuard, maybe MTU but I've never experimented with that.

I don't know, probably CPU power? Quirks with that specific speedtest server: https://github.com/sivel/speedtest-cli#inconsistency. Most likely not an SD card issue, the test should be performed in RAM.

I installed speedtest-cli on my 2019 quad-core mac and I get the exact same down/up speed as with 3B+. Hence, I suppose it is the limitation of python.
That being said, I would still appreciate if someone could please post their speed results when running a PiVPN Wireguard server on Raspberry Pi 3B+ or 4B. Thanks!

Returning to the original topic - I would still really appreciate if someone could please post their speed results when running a PiVPN Wireguard server on Raspberry Pi 3B+ or 4B. That would allow to verify whether going above 97Mbit/s up/down with Wireguard server on a Raspberry Pi is possible. Thanks!

I found this: https://www.reddit.com/r/WireGuard/comments/eeafds/wireguard_throughput_on_raspberry_pi_4/


casper: Avoid nesting wait statements to avoid flakes.

This test had flaked before. Nesting waitUntilVisible
statements is generally discouraged in casper tests.

Testing Plan:
GIFs or Screenshots:

Merged, thanks @showell!  No guarantees this was it, but could be.


Profunctor Equivalence Isos

Merging in the Isos between the definitions, as well as some clean up in Profunctor General.
There are Isos for

Def1 ~= Def2
Def2 ~= Def3
Def3 ~= Def4

This completes the rest of the work for Issue #7


Support tsx (TypeScript + JSX syntax)

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/28571003-support-tsx-typescript-jsx-syntax?utm_campaign=plugin&utm_content=tracker%2F535900&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F535900&utm_medium=issues&utm_source=github).

Would also love to see emmet-atom work like emmet in webstorm when editing .tsx. Classes should be applied as className instead of class, and working with tab instead of having to press ctrl+e would be very nice...


there is a error when upgrade the package to the 5.1.1

my previous version 3.10 was working fine but when updated to the current version
it returns an error
OperationException(linkException: ServerException(originalException: null, parsedResponse: Response(data: null, errors: null, context: Context({ResponseExtensions: Instance of 'ResponseExtensions'}), response {error: Unauthorized, message: Access token invalid})), graphqlErrors: [])

I would expect upgrading two major versions may break your app. It looks like the error is pretty obvious from your error message, try and have a look at how your links are set up and if the authorisation tokens are properly passed.

Please I couldn't find the error so please have a look at my code and tell me where the error could be found
https://i.ibb.co/mcvVMPc/screen-1.png
https://i.ibb.co/Y36sZgf/screen2.png

@budde377
class GraphQLService {
late GraphQLClient _client;
GraphQLService() {
initClient();
}
// Setup the apollo client on initialize
initClient() {
try {
  String serverUrl = AppUrls.getServerUrl(appFlavor);
  Logger().i("Server Url: $serverUrl");

  final HttpLink _httpLink = HttpLink("$serverUrl/graphql");
  final token = Preference.getString(PrefKeys.accessToken) ?? "";
  Logger().i("graph token: $token");
  //
  final AuthLink _authLink =
      AuthLink(getToken: () async => Preference.getString(PrefKeys.accessToken));
  Link _link = _authLink.concat(_httpLink);
  final GraphQLClient client = GraphQLClient(cache: GraphQLCache(store: InMemoryStore()), link: _link,);
  // readRepositories(client);
  return this._client = client;
} catch (e) {
  print(e);
  print('error initializing graphql');
}

}
/// Use this for cached queries
Future query({required String query,  Map<String, dynamic> ?variables}) async {
final QueryOptions options = QueryOptions(
document: gql(query),
variables: variables??{},
fetchPolicy: FetchPolicy.networkOnly,
);
final QueryResult result = await _client.query(options);

return result.handleResponse();

}
/// Use this for mutations
Future mutate({required String mutation, required Map<String, dynamic> variables}) async {
final MutationOptions options = MutationOptions(
fetchPolicy: FetchPolicy.networkOnly,
document: gql(mutation),
variables: variables,
);
final QueryResult result = await _client.mutate(options);
return result.handleResponse();

}
}

I don't know what kind of token your API requires. Maybe you'll need to prefix your token with Bearer ?
I.e.,
      AuthLink(getToken: () async => "Bearer ${Preference.getString(PrefKeys.accessToken)}");

Please I couldn't find the error so please have a look at my code and tell me where the error could be found

@Refaat2020 You are 2 years late, that with software is history! What we suggest is try to follow https://github.com/zino-hofmann/graphql-flutter/blob/main/changelog-v3-v4.md that is easily found in the repository.
If the error persists, take an empty project and start a graph_flutter project from scratch. debugging your code with difference between the new and old version is an easy job more than you are asking to us

Have you found a solution?


[BUG] Not switching from fullscreen to window mode correctly on Linux

Please give System Info
OS: Xubuntu 18.04 64-bits
CPU: Intel Core i3-4160
GPU: Intel HD Graphics 4400
Storage: 1 TB SATA III Toshiba PC P300
Please give your StepMania Info
StepMania Version: v5.3.0-alpha.4.9.7GG
Theme: Soundwaves (default, but it happens with all themes)
Describe the problem
StepMania OutFox doesn't switch from fullscreen to window mode correctly. Instead, it stays on fullscreen and only makes the game screen smaller, usually occuping only the bottom-left part of the entire screen, and the rest of the screen is only black.
This occurs both in "Exclusive mode" and "Borderless window" modes.
Describe what should happen
Switch to window mode completely, without leaving a huge black space on the screen.
Logs and Additional context

Go into the game folder
Open the Logs folder
Grab every file in there and post with the issue.
Go back to the game folder, if there's an crashinfo.txt then send it too

info.txt
log.txt
userlog.txt

This is after I tried switching from a fullscreen 1280x1024 mode to a 1024x768 window mode.

After you switch the resolution, if you exit, and reopen, does it display correctly?

I can replicate the same behaviour on Windows 10 with Nvidia's 1050Ti card. In my case after lowering resolution in settings and then changing from fullscreen to windowed mode, it still remains fullscreen. Using Alt+Enter actually switches from fullscreen to windowed and vice versa.

After you switch the resolution, if you exit, and reopen, does it display correctly?

Yes it does. I have to restart OutFox so that it can restore to window mode completely.

I can replicate the same behaviour on Windows 10 with Nvidia's 1050Ti card. In my case after lowering resolution in settings and then changing from fullscreen to windowed mode, it still remains fullscreen. Using Alt+Enter actually switches from fullscreen to windowed and vice versa.

In my case, using Alt+Enter actually switches to window mode, but the window does not revert back to the internal resolution (output resolution) that I'm using and it has the same size as my desktop resolution, again, with the game screen occuping only the bottom-left part of the window:

Long Time, but this is fixed in 4.9.9.
Thanks for reporting it!


feat: Use craft single-file binary

This switches from using npm to install craft to directly downloading the single-file binary. This should speed up the craft install and reduce the complexity around installing it (no more temp dir or path modification etc.)

Still failing?

Successful run: https://github.com/getsentry/release-tester/runs/2451653170?check_suite_focus=true
Shaved ~6s bringing the action time from 12s to 6s. I'd say pretty good.


SWP-1159 - Initial development

Bring code over from the @pod-point/typescript package
Update from TSLint to ESLint
Update README

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@ea8ae7c). Click here to learn what that means.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             master     #1   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      1
  Lines             ?     17
  Branches          ?      3
=======================================
  Hits              ?     17
  Misses            ?      0
  Partials          ?      0

Impacted Files
Coverage Δ

src/services/Redis.ts
100% <100%> (ø)

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 ea8ae7c...4ffd872. Read the comment docs.


docs(@angular-cli): update README as per #6070

The <IP_ADDRESS> host format will never work with current webpack version and will always show "invalid host header". Instead, a valid domain or public IP has to be specified. See #6070 .

I signed it!

@dimitrovs Please, could you fix commit message.
Please fix the failing commit messages before continuing...
Commit message guidelines: https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#commit

@PavelGonzales sorry, I don't think I can amend the commit message as I did this change directly in GitHub. But it's a simple one line change in the README, may be you guys can just redo it in your repo.

Is there any options to support <IP_ADDRESS> hostname?

@dimitrovs you can amend the commit message by locally cloning the fork, amending the commit, and force-pushing to the fork. this will automatically update the commit in the pull request. good luck!

These options are going to be refactored in v6.

@hansl is there any place to read about upcoming changes?


Generating CSharp client from swagger containing escaped quotes does not compile

Generating a CSharp Client (In NSwagStudio v10.6.6324.28497) based on a swagger containing the definition below does not compile.
"output1Item": {
  "required": [
    "Something \"some1\"",
    "Something \"some2\""
  ],
  "properties": {
    "Something \"some1\"": {
      "type": "number",
      "format": "double"
    },
    "Something \"some2\"": {
      "type": "number",
      "format": "double"
    }
  }
}

The CSharp client from http://editor.swagger.io/#/ seems to handle this. Would be great if NSwag could handle it as well.

How do you expect that this should be handled?

fixed in v11

Great job! Sorry I was not able to find the time to describe how I wanted it to be handled.


ENH: implement FrozenDict with frozendict

Closes #309

Some obscure things related to https://github.com/ComPWA/ampform/pull/444#issuecomment-2553404202...

As opposed to ComPWA/ampform@8a9a171, the hash of FrozenDict is already stable in QRules before switching to frozendict
Even after switching to frozendict, the hash of a ReactionInfo object still is not stable


InfraredRadiation image

How can I get the InfraredRadiation images for D435 by SDK2.0?

Yes it is the left imager.

Hi @fenneishi  To access both left and right IR, if you visit the link below then there is a C++ script sample under the 'Librealsense2' heading.
https://github.com/IntelRealSense/librealsense/wiki/API-How-To#start-streaming-left-and-right-infrared-imagers
A C# version is here:
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/csharp/Documentation/cookbook.md#start-streaming-left-and-right-infrared-imagers
And one for Python:
https://github.com/IntelRealSense/librealsense/issues/1297#issuecomment-371418188

This case will be closed after 7 days from the time of writing this message if there are no further comments.   Thanks!


Add cilium-servicemonitors app as default

Signed-off-by: Matias Charriere<EMAIL_ADDRESS>

This PR adds the cilium-servicemonitors app
Towards https://github.com/giantswarm/roadmap/issues/3283

Checklist

[x] Update changelog in CHANGELOG.md.
[ ] Make sure values.yaml and values.schema.json are valid.

Trigger e2e tests

/run cluster-test-suites

/run cluster-test-suites

/run cluster-test-suites

/run cluster-test-suites

/run cluster-test-suites


Schematics: antenna connection

First and foremost, thank you for this great piece of code, this isn't an issue but a question. I wanna connect the antenna's pins to an 1:9 balun, to playing with various length of wire. I know, isn't the best suitable antenna for this project, a dipole could be way better...but: do i need some decoupling capacitors between antenna output and the balun, who de facto short-circuits the output pins? There is a risk to burn the output? If yes (and i think this will be the answer) can you suggest a proper value? Thank you again, have a nice day!

because of limitations in the way the PIO code is written, after the first transmission, whenever it is idle in between transmissions one leg idles high, and the other low, so yes a balun would act as a short circuit to this DC voltage.
When testing at home I used a 1uF cap for DC blocking with very good results.
But the RP2040 seems very tolerant to shorts. One person has been running a Pi Pico as a standalone beacon into a balun with no caps at all, and other than the pico running a "little warmer" there have been no ill effects.  But I definitely recommend the cap to be on the safe side...

Thank you so much for your quick reply, I'll go for a 1uF cap, I've already found it in my spare parts junkyard, I hope to test the whole thing ASAP


fpp: 0.7.2 -> 0.8.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/fpp/versions.
meta.description for fpp is: '"CLI program that accepts piped input and presents files for selection"'.
meta.homepage for fpp is: '"https://facebook.github.io/PathPicker/"
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.8.2 with grep in /nix/store/580bsdd6b8gp81barj8h5v2l1f5vbr66-fpp-0.8.2

directory tree listing: https://gist.github.com/f4f781288f5c305c48cf320f1c58d59c

du listing: https://gist.github.com/c970b3837e215af13a170ff946eb21fe

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
fpp
tmuxPlugins.fpp

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/580bsdd6b8gp81barj8h5v2l1f5vbr66-fpp-0.8.2 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A fpp https://github.com/r-ryantm/nixpkgs/archive/d0f27576d8e03ea68dcf3c15955e969d69a3db77.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/580bsdd6b8gp81barj8h5v2l1f5vbr66-fpp-0.8.2
ls -la /nix/store/580bsdd6b8gp81barj8h5v2l1f5vbr66-fpp-0.8.2/bin

 ./bin/fpp
Traceback (most recent call last):
  File "/nix/store/580bsdd6b8gp81barj8h5v2l1f5vbr66-fpp-0.8.2/share/fpp/src/processInput.py", line 12, in <module>
    import format
  File "/nix/store/580bsdd6b8gp81barj8h5v2l1f5vbr66-fpp-0.8.2/share/fpp/src/format.py", line 13, in <module>
    from formattedText import FormattedText
  File "/nix/store/580bsdd6b8gp81barj8h5v2l1f5vbr66-fpp-0.8.2/share/fpp/src/formattedText.py", line 9, in <module>
    from colorPrinter import ColorPrinter
  File "/nix/store/580bsdd6b8gp81barj8h5v2l1f5vbr66-fpp-0.8.2/share/fpp/src/colorPrinter.py", line 7, in <module>
    import output
  File "/nix/store/580bsdd6b8gp81barj8h5v2l1f5vbr66-fpp-0.8.2/share/fpp/src/output.py", line 8, in <module>
    from builtins import str


Fixing broken demos for basic popup and missing script demo

While doing some reading of docs I noticed a couple non-functional demos. The popup demo is an easy fix, but I couldn't find a reference to the "script tag component" so just deleted that.
Not sure how to get this published to the krakenjs docs site, will need help with that.

@gregjopa @bluepnume I don't have write access to this repo, nor do I know how to deploy these docs updates. If either of you gets a chance, can you merge the PR in and show me how you deploy?
Thanks!


HDDS-10093. Make recoverLease call idempotent

What changes were proposed in this pull request?
To be compatible with HDFS behavior, once a file is recovered by calling recoverLease, next time call recoverLease with same path will succeed.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-10093
How was this patch tested?
new unit test case

Thanks @jojochuang  and @ashishkumar50 for the code review.


merge from arlac77/template-arlac77-github,arlac77/template-esm-only

package.json

chore(deps): add ^3.11.1 remove ^3.11.0 (devDependencies.ava)
chore(deps): add ^7.3.0 remove ^7.2.1 (devDependencies.c8)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Secure mode

Does this mixin support any way of enabling intercom's secure mode?
Thanks!

There's no reason why this addon wouldn't support secure mode. You are responsible for generating a HMAC token on your own back-end, and passing it to Intercom as you initialize it through the ember service

@mike-north I created #26 to solve this issue when you get a chance, would love a merge.

This isn't an issue anymore thanks to https://github.com/levanto-financial/ember-intercom-io/pull/26
@cprussin you want to close the issue?

Closing.  Thanks all!


[REQUEST] Dynamic IconURL

I would like to be able to have a dynamic IconURL like the Slack-IRC bot has (https://github.com/ekmartin/slack-irc, "avatarUrl": "https://robohash.org/$username.png?size=48x48"). I use this function to grab custom avatars of users that are on IRC.
I didn't see anything that suggests that this feature already exists so I'm hereby requesting it. I would be more than enough if I could use the {NICK} syntax in the IconURL variable.

For slack you can now use eg
IconURL="https://robohash.org/{NICK}.png?size=48x48" but PrefixMessagesWithNick has to be false otherwise it won't work.

Thanks a lot @42wim!


[Fix] Issues with ramsey/uuid when installing?

Hey folks, not a bug, but a compatibility issue downstream from this package.
This is likely a newbie issue more than anything, but if you're using Laravel 7 (in my case 7.13) it requires ramsey/uuid ^3|^4".
However, opencensus/opencensus (a dependency of this package) has its ramsey/uuid dependency set to "~3".
Thus, you need to manually downgrade ramsey/uuid directly in your project PRIOR to requiring gluedev/laravel-stackdriver or you too could wind up in the dependency-hell I just escaped from.
Do this by running composer require ramsey/uuid "^3".  Then you can proceed on and run composer require gluedev/laravel-stackdriver.
Again, this dependency tracing may be second nature to others... but it just gobbled up about 90 minutes of my time.  Thus, I hope this helps others.

Hey guys, any plan for a patch on this? I'm also trying to upgrade the Laravel version and getting the same issue. Cheers.

Thanks for your suggestion!
This Package will not work with Laravel 8 because it requires ramsey/uuid:^4.0

Thanks for your suggestion!
This Package will not work with Laravel 8 because it requires ramsey/uuid:^4.0

Any workaround on this?

Any workaround on this?

This is an issue with the opencencus package. They seem to not be in a rush when it comes to releasing new versions:
https://github.com/census-instrumentation/opencensus-php/issues/253
https://github.com/census-instrumentation/opencensus-php/issues/268
Maybe there's some way to circumvent this through composer.json, or someone would have to fork the opencencus package.

yes the only way is to fork the project and setup composer.json to use your fork.
I used this guide and it worked for me

So a new release was finally pushed, but unfortunately the PR for updating ramsey/uuid still goes unnoticed:
https://github.com/census-instrumentation/opencensus-php/pull/261

For now, I forked and made it work with ramsey/uuid v4 , not ideal but it works for now.
        {
            "type": "vcs",
            "url": "git@github.com:nanosolutions/laravel-stackdriver.git"
        },
        {
            "type": "vcs",
            "url": "git@github.com:nanosolutions/opencensus-php.git"
        },
        {
            "type": "vcs",
            "url": "git@github.com:nanosolutions/opencensus-php-exporter-stackdriver.git"
        }

Hey @cerw Can you share the steps on how to upgrade the composer and use this package in Laravel 8?Thanks

Thanks for your suggestion!
This Package will not work with Laravel 8 because it requires ramsey/uuid:^4.0

Hey

yes the only way is to fork the project and setup composer.json to use your fork.
I used this guide and it worked for me

Hey @JulianMar
In this case, we have 3 packages:

laravel-stackdriver
opencensus
opencensus-exporter-stackdriver

I bumped the version of ramsey/uuid inside opencensus and pushed to my own fork.
Added the "repositories" section to opencensus-exporter-stackdriver and changed the version of the opencensus package used as "dev-master"
Add the "repositories" section to laravel-stackdriver and changed the versions of the opencensus to "dev-master" and also the same thing with openensus/-exporter-stackdriver.

In my Laravel app, I made the gluedev/laravel-stackdriver with version "dev-master" together with a "repositories" section to my own forked version of the package.
When I try to run "composer update", I get this:
Problem 1
    - opencensus/opencensus-exporter-stackdriver dev-master requires opencensus/opencensus ~0.5 -> satisfiable by opencensus/opencensus[v0.5.0, v0.5.1, v0.5.2, v0.6.0].
    - You can only install one version of a package, so only one of these can be installed: opencensus/opencensus[dev-master, v0.5.0, v0.5.1, v0.5.2, v0.6.0].
    - gluedev/laravel-stackdriver dev-master requires opencensus/opencensus dev-master -> satisfiable by opencensus/opencensus[dev-master].
    - gluedev/laravel-stackdriver dev-master requires opencensus/opencensus-exporter-stackdriver dev-master -> satisfiable by opencensus/opencensus-exporter-stackdriver[dev-master].
    - Root composer.json requires gluedev/laravel-stackdriver dev-master -> satisfiable by gluedev/laravel-stackdriver[dev-master].

Hey @cerw Can you share the steps on how to upgrade the composer and use this package in Laravel 8?Thanks

Hello,
See example of one of projects:
{
    "name": "*******",
    "type": "project",
    "description": "*",
    "keywords": [
        "framework",
        "laravel"
    ],
    "license": "proprietary",
    "authors": [
        {
            "name": "Nano Solutions Pty Ltd",
            "email"<EMAIL_ADDRESS>            "homepage": "https://nanosolutions.io",
            "role": "Developer"
        }
    ],
    "require": {
        "php": "^7.3 || ^8.0",
        "ext-json": "*",
        "bugsnag/bugsnag-laravel": "^2.20",
        "doctrine/dbal": "^2.11",
        "erusev/parsedown": "^1.7",
        "facade/ignition": "^2.5",
        "fideloper/proxy": "^4.4",
        "fruitcake/laravel-cors": "^2.0",
        "gluedev/laravel-stackdriver": "dev-develop",
        "guzzlehttp/guzzle": "^7.0.1",
        "htmlmin/htmlmin": "^8.0",
        "kalnoy/nestedset": "^5.0",
        "laravel/framework": "^8",
        "laravel/horizon": "^5.6",
        "laravel/legacy-factories": "^1.1",
        "laravel/slack-notification-channel": "^2.2",
        "laravel/tinker": "^2.5",
        "laravel/ui": "^3.0",
        "league/flysystem-cached-adapter": "^1.1",
        "maatwebsite/excel": "dev-main",
        "predis/predis": "^1.1",
        "simplehtmldom/simplehtmldom": "^2.0@RC",
        "spatie/laravel-activitylog": "^3.16",
        "spatie/laravel-medialibrary": "^9.0",
        "spatie/laravel-tail": "^4.3",
        "stevebauman/purify": "^3.0",
        "superbalist/laravel-google-cloud-storage": "^2.2"
    },
    "require-dev": {
        "barryvdh/laravel-debugbar": "^3.5",
        "beyondcode/laravel-dump-server": "^1.5",
        "enlightn/security-checker": "^1.8",
        "ergebnis/composer-normalize": "^2.13",
        "fakerphp/faker": "^1.9.1",
        "jakub-onderka/php-console-highlighter": "^0.4.0",
        "laravel/dusk": "^6.8",
        "mockery/mockery": "^1.4.2",
        "nano/docs": "dev-master",
        "nunomaduro/collision": "^5.0",
        "php-parallel-lint/php-parallel-lint": "^1.1",
        "php-webdriver/webdriver": "^1.8",
        "phpro/grumphp": "^1.0",
        "phpunit/phpunit": "^9.3.3"
    },
    "config": {
        "optimize-autoloader": true,
        "preferred-install": "dist",
        "sort-packages": true
    },
    "extra": {
        "laravel": {
            "dont-discover": []
        }
    },
    "autoload": {
        "psr-4": {
            "App\\": "app/",
            "Database\\Factories\\": "database/factories/",
            "Database\\Seeders\\": "database/seeders/"
        }
    },
    "autoload-dev": {
        "psr-4": {
            "Tests\\": "tests/"
        }
    },
    "repositories": [
        {
            "type": "vcs",
            "url": "git@github.com:nanosolutions/Laravel-Excel.git"
        },
        {
            "type": "vcs",
            "url": "git@github.com:nanosolutions/laravel-stackdriver.git"
        },
        {
            "type": "vcs",
            "url": "git@github.com:nanosolutions/opencensus-php.git"
        },
        {
            "type": "vcs",
            "url": "git@github.com:nanosolutions/opencensus-php-exporter-stackdriver.git"
        }
    ],
    "minimum-stability": "dev",
    "prefer-stable": true,
    "scripts": {
        "post-autoload-dump": [
            "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover --ansi"
        ],
        "post-root-package-install": [
            "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
        ],
        "post-create-project-cmd": [
            "@php artisan key:generate --ansi"
        ]
    }
}

Thanks @cerw
Not only you need to add repositories section to opencensus-php-exporter-stackdriver and laravel-stackdriver, but also in the project using laravel-stackdriver?
Thanks

Thanks @cerw I managed to make it work.
I had to do the following:

Fork & Bump ramsey/uuid on opencensus
Fork & add repositories section on opencensus-php-exporter-stackdriver
Fork & add repositories section on laravel-stackdriver (develop is the main branch not master)
In my main app, I use "gluedev/laravel-stackdriver": "dev-develop", and added the three forked repositories all together in the app composer.json file.


Why does the animation not take effect when using the  tag？

Reproduction demo：https://jsbin.com/xuyapuyuna/1/edit?html,js,output

It seems that it's because the span is an inline element. Change it to block and the animation will work.


considered MIT license?

Just curious why gpl3 vs MIT.  libsoundio uses MIT so seems like that would be a good fit here.

The reason is, that the GPL enforces that modifications to the source code have to be open sourced as well. Maybe I'm changing the license to MIT in a future release, but not before 1.0.
If you have any concerns about the usage of the GPL license, then please let me know.

You might consider the LGPL, which, as I understand it, would allow static linkage with proprietary programs while still forcing modifications to rsoundio to be made public.
Personally its not a problem for me right now as I'm currently working on open source code.  It would be nice to standardize on one library for proprietary and non-proprietary though.
Anyway, nice work on the library, very clean!  It works on arm, I was testing a number of libs this weekend and this is one that works on the raspberry pi (arch).  libsoundio isn't in the arch repos yet but it builds successfully if you disable jack support.  That should be fixed soon according to a bug report I found.

@bburdette
I'm happy that you like it! I've already made a bug report for the JACK fix in Arch Linux. The issue closed and will be fixed with next JACK release in the Arch repositores (the version from the community-testing repos works fine). Also very good to hear that it works on Arch! I'm building a FM synth in Rust that I want to test on a raspberry Pi 3 as well.
PS: I will consider to choose an LGPL license but not now.
PPS: If you like to contribute to rsoundio then please send me PRs or open issues etc.

Especially since rsoundio only really supports the Linux portions of libsoundio right now, rsoundio could really use contributors. But allowing contributors would make changing the license more difficult. Which is your priority?

Especially since rsoundio only really supports the Linux portions of libsoundio right now, rsoundio could really use contributors.

I haven't tested it on Windows or Mac yet but I think that the Rust part is not using any platform specific code.
Contributors are welcome and I would be happy to get PRs. Are there any concerns with the current dual Apache/MIT license?

Whoops, really sorry about missing the license change!


integrate love-console

It'd be really handy to include a debug console OOTB, and it just so happens that I've got such a thing which could be made to work.
depends on several APIs in order to happen, notably working fonts.

Haha yeah! Count me in for this... when support for fonts and graphics is implemented I'll help on this


setting content-type with charset=utf-8?

Hi,
stout is great! We are deploying an angularjs app to s3 with it. But are having issues because the charset needs to be set to utf-8 for all our files:
Content-Type: text/html; charset=utf-8
The go mime library doesn't guess that correctly.
Would you be interested in a pull request that adds a commandline charset option to explicitly set charset option?

It looks like Go does have a method for detecting encoding: https://godoc.org/golang.org/x/net/html/charset#DetermineEncoding
I have a few questions though (not necessarily for you to answer):

Will it give the same (bad) answer the browser is giving, causing you to have your issues?
Can we just always put utf-8 in and expect it to work instead?

Can you run that method on your file perhaps, and let me know if it does indeed return utf-8.

@zackbloom Thanks for pointing out the method for determining encoding - I'll try to use that. Regarding your questions, always putting utf-8 was our fall-back if we couldn't get a proper encoding determination to work. S3 definitely needs encoding set, otherwise the static website server Amazon uses doesn't give back the right encoding headers... so we think it will help, the other software we're using (gulp-s3 does this and we get the right encoding headers back. But gulp-s3 doesn't have a zero-downtime-deploy option... :-)
I'll give this a shot today or tomorrow and let you know - if it works I'll send a pull request.

maybe an option to solve this can be allowing custom headers to be set in deploying files.

What's the issue with the original solution? Of figuring out the encoding and setting that?

Stout is already setting charset=utf-8 on S3. See https://github.com/EagerIO/Stout/blob/2b8f03bbb4c54d7c546aa8968a46c0cd438d01ac/src/deploy.go#L134.


V3.0.0 pre release

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 92.06349% with 5 lines in your changes missing coverage. Please review.

Project coverage is 95.98%. Comparing base (ca07bc8) to head (2127b8d).

Files with missing lines
Patch %
Lines

src/redis_dict/core.py
90.74%
5 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #67      +/-   ##
==========================================
- Coverage   97.20%   95.98%   -1.22%
==========================================
  Files           1        2       +1
  Lines         250      299      +49
==========================================
+ Hits          243      287      +44
- Misses          7       12       +5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


How to use this library, no documentation?

Please provide information about which methods we can call. There is no documentation in readme file.

This is not a library, just a side project application


Extending a GDScript on a node clears the exported script variables.

Godot version: 3.2.1 / master (a2da99f40cf2123c0906c734a2eb01e9b65a45a2)
OS/device including version: Windows 10
Issue description:
Using Change Type on a node with an attached script (notably scripts with class_names and hence appearing as types in Add Child dialogs) does nothing.
Steps to reproduce:

Provided Reproduction

Create a script with class_names (A).
Create a new node with with the type

Extend the node with the attached script.

Minimal reproduction project: TempTest.zip

Related to #37479
There is a common misbehavior around changing the type of nodes with GDScripts on them. Also notable are:

Dropping a script that extends the script currently on a node clears the script variables.
Dropping a script that is a sibling of the script currently on a node clears the script variables.
Dropping a script that is extended by the script currently on a node clears the script variables.

All of which are situations I would expect to work correctly.

I would be willing to attempt fix these two issues and improve this overall (fixing the additional three cases above). I could also create a proposal for this behavior if necessary.

Upon implementing some code to (attempt a broken) fix for the issue in #37479 I realized the correct way to implement all of the above is probably with duck typing. As that is how the code appears to be written in the first place! It just isn't working at the moment (for scripts at least).

So I guess the proposal/fix I might submit here is to call the "change type" code, which in turn calls the Node::replace_by code which copies variables (I am about to have a pull request to fix #37479 that improves the behavior of this code), instead of calling into the Object::set_script code directly. I have two reasons suggest this:

It will allow variables to propagate to the new script from the old script (via duck typing).
It will better support undo/redo (specifically it will store the variables of the script).

A downside of this is that we will end up creating a new node every time a script is changed from the editor. This also means that the script instance will not be modified and will instead continue to persist with the old node in the undo history (I don't know if there would be negative side effects to this). However I would contend that changing which script is attached to which node is a relatively uncommon occurrence.


fix(plugins): add realm to removed fields

Summary
Basic-auth and key-auth added new field "realm" but it was not added to "removed_fields" which breaks backwards compat between new CPs and old DPs. Adding realm to removed fields fixes the issue.

Checklist

[x] The Pull Request has tests
[x] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[x] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference
KAG-4516

@nowNick I am not sure we need to backport this to 3.6 in CE

@kikito I think we do. However the backport needs to be tweaked a little because it'll only need basic-auth changes (the other - key-auth was changed in 3.7).


It seems create-react-app could have overcome the "all lower case" issue?

I read the pages:

https://stackoverflow.com/questions/59159553/why-cant-react-project-name-contain-capital-letters
https://github.com/facebook/create-react-app/issues/2165

but isn't it a simple solution:
https://stackoverflow.com/questions/66076461/if-create-react-app-requires-only-lower-case-what-if-we-create-an-app-but-on-a
what if we do
mkdir TryingMobXApp02
cd TryingMobXApp02
npx create-react-app my-app
cd my-app
# and then we do some work on the project

then we git push to a new github.com repo, and then, if we have another computer, we do
git clone ...   TryingMobXApp02

so in that case, the other computer has the project but is in the folder TryingMobXApp02.
So the question is:

is that going to run into trouble later on possibly? But the fact is that I have done it that way many times and never ran into any problem
so if it is not a problem, isn't it true create-react-app could have done it, by invoking npx create-react-app tmp-app, and then, just rename the folder back to TryingMobXApp02?

The name tmp-app could be app and then append a SHA256 of the UNIX timestamp to it.  This name should not exist in the user's folder by the claim it is almost impossible to happen, but if that happens we can always try again.
Perhaps one reason to use title case is, some people UNIX usage habits would name their folder name to have capital case to begin with.

I solved this using the following command.
npm uninstall -g create-react-app
npm cache clean --force
then
npx create-react-app project_name --template all
Thanks for this! Worked for me too.


Implement TypeScript type generation for the configuration

Resolves #1004
📚Description
This PR adds a new script to the project: schema/build-config-declaration.js. The script takes the existing configuration schema, and generated a new file markdownlint-config.d.ts with type declaration for the config. This script now runs as part of the build-declaration npm script.
The generated type is then used in the libs/markdownlint.js file to enrich the existing Configuration type:
/**
 * Rule configuration object.
 *
- * @typedef {Object.<string, RuleConfiguration>} Configuration
+ * @typedef {import("../schema/markdownlint-config").Config} Configuration
 */

With this change, the functions that already used this type now has proper suggestions:

A new defineConfig() function was added as well to make it easier to define configurations in js files, like vite, astro or nuxt does.

Thanks for sharing this!
I like what it does for the user and the way the new types are referenced is clean, but build-config-declaration.js is a lot more complicated than I'd like. Per the discussion in #1004, I'm hoping for something simpler. I'll need to spend some time exploring options here before I can review this PR. I have a few other tasks on the TODO list, so it may be a week or two before I come back to this.
I don't think I'd suggest spending time on this before I do, but if you're bored I can say after a first pass that defineConfig would need to be documented in README.md and type-check.ts should have a line or two added to validate this. I'd also rather not touch the files in the micromark directory, as that seems unrelated.

Let me know when you think we can move forward with this approach, and I will update the readme and the type checks^^
Regarding the changes in the micromark folder, I did those, because the linting would fail otherwise

I spent a bit of time this evening and pushed the branch condef to show the approach I imagined and was hoping for in #1004 - you can see the diff here: https://github.com/DavidAnson/markdownlint/compare/next...condef
I only need to write a few lines of code to work around a quirk/bug of TypeScript index types. All the type information comes directly from the JSON schema. From what I can tell experimenting quickly in type-check.ts around line 85, the definition is working as intended. I didn't spend time on defineConfig since you'd already done that in this PR.
The only thing I see missing vs. what's proposed in this PR is deprecations - but that's part of the 2019-09 JSON specification and may carry over automatically once used/added.

There are a few key differences with these approaches.
JSDoc quality
Even though the generation in this PR is longer, most of the lines are for making the JSDoc comments more readable and neatly organized. For example, here is the MD021 rule:

The upper one has the description, the most important part first, has a paragraph for the aliases and a link to the rule's documentation.
Readability of the d.ts file
I would say the generated file is more readable in this PR. If we compare the MD022 rule for example:

The second interface has a lot of duplication and is bit weird. The upper is short and readable.
Interfaces are also randomly generated in the condef branch's output. Sometimes there is an interface for a rule, sometimes the types are inlined:

Errors
When an interface is generated for a rule in the condef branch's output, there is no JSDoc for that rule when using the Configuration type. This happends for the MD022 rule for example:

Compromises
We can delete most of the code from the generation script, if we don't want to make the JSDoc comments more readable, and the output would still be okay. I think it it's a nice addition, but if you don't think it's worth the ~100 plus lines of code, I can delete it.

JSDoc quality: I agree that what you show is richer. At the same time, the JSON schema is seen by more people and if there are readability improvements to be had there, I’d prefer to make them so everyone benefits. The rule link is a nice touch. Good news is that it seems VS Code automatically linkifies bare URLs in the description field, so I’ve made myself a note to add that to each rule’s description in the JSON schema.
Readability of the .d.ts file: This is not a goal in my mind; that file is not something users are expected to read. I agree it’s nice if it’s more readable, but I would not base a decision on this unless it was the only difference.
Errors: This seems like a VS Code problem? It’s worth looking into on my part.
FYI, I’m iterating on a different PR at the moment and will come back to this when that’s done.

Note to self
Fix for the problem raised above in the section "Errors". As it happens, this also largely addresses (and improves upon?) the section "Readability of the d.ts file" by defining everything inline.
diff --git a/schema/build-config-schema.js b/schema/build-config-schema.js
index 9a13fd7..a6290b5 100644
--- a/schema/build-config-schema.js
+++ b/schema/build-config-schema.js
@@ -530,9 +530,7 @@ for (const rule of rules) {
     scheme.additionalProperties = false;
   }
   for (const [ index, name ] of rule.names.entries()) {
-    schema.properties[name] = (index === 0) ? scheme : {
-      "$ref": `#/properties/${rule.names[0]}`
-    };
+    schema.properties[name] = scheme;
   }
 }

I spent about an hour playing with quicktype this evening. It seems very similar to json-schema-to-typescript in a lot of ways. At one point, I thought I found a command-line I could use instead of writing any code, but there are some of the same issues with this library:

configuration.d.ts is full of red squiggles unless the default handling of additionalProperties is altered. Link to the json-schema-to-typescript bug for this: https://github.com/bcherny/json-schema-to-typescript/issues/356. I couldn't find a corresponding bug for quicktype, but the same edit of the .d.ts fixes the squiggles: [property: string]: unknown;.
Default output from the tool suffers from the same problem raised above in the "Errors" section where alternate rule names don't get their own JSDoc comments. I suspect the same fix I describe above would address it.

Overall, because json-schema-to-typescript has about 10x the daily downloads according to npm and uses the same license as this project (MIT), I'm inclined to go with that. I'm going to rebase my condef branch onto the latest next branch now, review the changes tomorrow, and probably commit these changes since it's what I described in the original issue comments. Your good work on defineConfig would still be applicable and could be put into its own PR.
PS - quicktype --src-lang schema ./schema/markdownlint-config-schema.json —out ./lib/configuration.d.ts --just-types --top-level Configuration

The vite documentation linked above (https://vitejs.dev/config/#config-intellisense) shows a simpler alternative to defineConfig that avoids creating a project dependency and making a function call by relying entirely on the type system. That's clean, efficient, and a generally applicable technique, so I'm going to close this PR as the intended functionality should be available in the next release.. Thank you very much for spending time discussing and working on this!


Q&A tool

depends on #66
since we've already done Q&A on the old site I'm not going to re-explain it here or create new wireframes right now. please bring over the Q&A functionality as best you understand it for a first draft. let me know when you finalize the database schema and I will review just the schema file at that time. Q&A will be a new tool on the home screen.
it is important for this functionality to be built on top of the document viewer code. This feature will be different than the document viewer (new page), but we want the React component that the document viewer uses to be the same component that the Q&A uses. Other features/pages will use this document viewer component as well, so it needs to be well architected.

the document page, Q&A page, and Pericope page need to all use the same document viewer component. the doc view page won't show any special features on top of words, but the Q&A and Pericope pages will show special stuff on the words. The Q&A page will have question and answer dots above the words, the pericope will have similar things.
So be sure to architect these components so that all the pages can use them.


Left-recursive EBNF expansion

When testing #171 I found I was running out of memory when parsing a large JSON sample (~1kB), using the example scannerless JSON parser in the repo.
I realised that we're expanding EBNF rules like
string -> "\"" validChar:* "\""

into
string$ebnf$1 ->
               | validChar string$ebnf$1

Since Earley loves left-recursion, I think it would be better to expand these left-recursively instead! In particular, I think this avoids some weird n^2 behaviour when parsing long strings.
Anyway, even on master this patch appears to speed up a 1k JSON sample by ~3x, so this seems worthwhile :-)
@hardmath123 What do you think?

Yes! This is a thing I've been meaning to do for a while. Thank you!

(I published v2.7.14 on npm because I think this is really worthwhile. Also, I recompiled the bootstrapped grammar so now compiling is faster as well.)

(I published v2.7.14 on npm because I think this is really worthwhile.

:D

Awesome 👍
I can confirm a 300% (X4) performance increase on a 45k input JSON file
between 2.7.13 and 2.7.14.

@bd82 Neat! What do you get with #171?

@tjvr I will answer on #171


Clang/GCC incompatiblity

There are few problems with clang.
First, It is not able to find GCC headers, it is caused by -fcoroutines-ts and -fcoroutines does not define the same preprocessor definition, It can be workarounded with -D__cpp_impl_coroutine=1 (what -fcoroutines does).
And now, clang complains that a coroutine cannot be used without <experimental/coroutine> inclusion what is breaking with GCC.
eg.:
~/cppcoro/test/async_latch_tests.cpp:59:4: error: std::experimental::coroutine_traits type was not found; include <experimental/coroutine> before defining a coroutine
                        co_await latch;
                        ^

Currently the only way to use with clang is to use libc++ (tested with clang-12 on Arch):
cmake -DCMAKE_CXX_FLAGS="-stdlib=libc++" <path_to_sources>

On ubuntu, executables must be explicitly linked with -lc++:
cmake -DCMAKE_CXX_FLAGS="-stdlib=libc++" -DCMAKE_EXE_LINKER_FLAGS="-lc++" <path_to_sources>

Is this now solved with the latest changes in the integrate_all branch?

No, it is not.
Clang will only compile with libc++, but it should also work with libstdc++.
This won't change until clang updates it's coroutine header to non-experimental path, or even accept it.

I guess this is solved in the master branch of andreasbuhr/cppcoro?
I see that more documentation is required.

The answer is simple can you build it with clang without --stdlib=libc++ ?


Resource Contrained Shortest Pahts to every vertices from source : r_c_shortest_paths_to_n

Hello everyone bare with me if this has no place here but I have a requirement for a professional project to find every best feasible path to every vertex in a graph. My research did not provide me any way to do it but I may have missed something. If so tell me and I will gladly use it and get rid of my useless code.
It appears that r_c_shortest_paths does that already but does not provide an api to get the solution for all vertices.
Right now r_c_shortest_paths extends all feasible labels and then pick the best ones for the vertex identified as the 'target'. What i want is to get the best labels on every vertices.
I have already created a r_c_shortest_paths_to_n (took very little time but only a few unitary tests have been added) for my project but would like to offer a boost extension for such feature.
I am not sure on how to proceed further (never contributed to boost).

A better place to ask this kind of question is on the boost-users mailing list<EMAIL_ADDRESS>

A better place to ask this kind of question is on the boost-users mailing list<EMAIL_ADDRESS>

Thanks indeed the mailing list would be better to as the question.

Thanks indeed the mailing list would be better to as the question.


Image size is getting bigger than real on iOS[🐛]

Image size is getting bigger than actual image on iOS with the latest react-native-image-picker (3.x)

Same issue

I checked other image pickers too.
It seems bug is related with react-native self.
When I use react-native-crop-image-picker if I don't compress image i.e if I use original image self, image size is getting bigger.

Hmm, someone posted on #1272 to suggest that this was a particular React Native bug: facebook/react-native#27099. Would that match the symptoms you're seeing?

Yes, I think it's react-native bug.

Going to close this issue for now. It's a good reference point for other facing the same issue.  If it is at some point determined to be a problem of the image picker, then we can open/create a new issue.
Thanks!


Optimize for large dataset

Coverage increased (+0.05%) to 72.115% when pulling 59d155f2873b84b7992129a25347c210f6305d79 on optimize-for-large-dataset into 318d5012c5af87c19aab7afa1b2041cc08bfded7 on master.


Build a .NET core console app to manage data in Azure Cosmos DB not found

About cosmos DB tutorials, I can find build a console app with .net framework to manage data in Azure Cosmos DB
https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-get-started
and also build an ASP.NET Core MVC web application to manage data in Azure Cosmos DB
https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-dotnet-application
However, the build a .NET Core console app using Azure Cosmos DB return 404
https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-dotnetcore-get-started-preview
Not sure any difference between .Net core and .Net framework for cosmos DB?
Thanks for the feedback

Thanks for your feedback @galenyjl. Where are you seeing that link that 404s?
@SnehaGunda can you help with his?

@mairaw Please check https://docs.microsoft.com/en-us/samples/azure-samples/cosmos-dotnet-core-getting-started/developing-a-net-core-console-app-using-azure-cosmos-db/
and then click full tutorial on the Azure Cosmos DB documentation page.

Thanks @galenyjl. @deborahc you seem to be the owner of the https://aka.ms/CosmosDotnetCoreGetStarted link. Can you please check?


fix 'over scrolling' bug

when the text field is at the very bottom of the scrollView, by the time keyboard dismiss, you will see a ‘over scroll gap’ at the bottom, the contentOffest has wrong value. then slightly touch the scrollView, it jump to the correct value.

DO NOT merge this branch. It has severe bug of wrong scrolling. My textFields are jumping to a very wrong position on dismiss by using above code. No issue with existing code

Cheers for the review @tariq235! Going to close this one.

what's wrong with this piece of code? in what case?


Maximum File Size

I'm trying to set the Maximum File Size (in bytes) for the default website.
The following is how I'm trying to do it..
# Configure IIS logging
iis_site 'Default Web Site' do
  log_period :Daily
  log_truncsize 3000000
  site_id 1
  bindings 'http/*:80:,net.tcp/808:*,net.pipe/*,net.msmq/localhost,'\
           'msmq.formatname/localhost,https/*:443:'
  action :config
end

I've also tried like:
log_truncsize 3_000_000

either way, the setting is not set...

Please let me know what I'm missing.
Thank You!!

@kalapakim what size are you trying to set the file to? It has to be greater than 1MB and less than 4GB...it is in bytes (might change this to MB for simplicity...
So if you want to set it to say 4MB it would be:
# Configure IIS logging
iis_site 'Default Web Site' do
  log_period :Daily
  log_truncsize 4194304
  site_id 1
  bindings 'http/*:80:,net.tcp/808:*,net.pipe/*,net.msmq/localhost,'\
           'msmq.formatname/localhost,https/*:443:'
  action :config
end

this should work
1024 * 1024 * 4 = 4MB

Looks  like rubocop  likes every 3 digits to be separated with a _

You know what I figured it out, I was trying to verify it's settings in the UI and found that i would be in the applicationHost.config file, which was getting set correctly. I just thought it would be reflected in the Logging view of the UI of IIS Manager. Thanks!!!

Sounds good, closing this issue...feel free to open it back up if something changes


Bump option-select to latest

Brings in the following changes:

Accessibility option select
Add close on load to
govuk-option-select

(Includes fixes for the problem described in this story: https://www.pivotaltracker.com/story/show/105291876

Looks good :+1:

Missed a few changes that were rolled into the updates on the govuk component. Now included.


Fixes to make this app work with Bigcommerce again

The changes in this PR were necessary in order to have a working BC app; they also make this example more complete. The changes include:

changing references to api.bigcommerceapp.com to api.bigcommerce.com
adding /uninstall endpoint
adding setup steps in the README
adding client_secret to the bigcommerce API client config
expanding auth scope to all permissions

Thanks for your contribution, I will look this over today.

@tautologistics Thanks for this. I have added line comments for things I'd like to see before we merge.
cc @pedelman @gabelimon @philipmuir

@tautologistics Another commit was merged that overlaps with yours, so you'll need to rebase off of master. In particular, the uninstall callback was added, so you should remove your implementation.

Most of the changes you made have been merged in other pull requests, so closing this for now.


Auth with social providers

How would one set up authentication using one of the social providers available in Supabase instead of username/password authentication?

I'm wondering this too.
This is in the docs at the bottom:

Add support for third party authentication

Is there a timeline for this?

Hi, and thanks for your question. As explained in the react-admin contributing guide, we use the GitHub issues for bugs and feature requests only.
For support question ("How To", usage advice, or troubleshooting your own code), you have two options:

Community support: Ask your question on StackOverFlow. This makes your question easy to find by the developer community. StackOverFlow has great SEO, gamification, voting, and reputation system.
Professional support: If you're a React-Admin Enterprise Edition subscriber, you have unlimited access to the Professional Support service. This service guarantees that you'll get an answer shortly.

If your problem is urgent, please consider subscribing to the Enterprise Edition, starting at 125€. It's a good way to contribute to the sustainability of react-admin.
So I'm closing this issue, and inviting you to ask your question in one of the support channels above.

oops, sorry I went a big too fast: I thought we were on the react-admin repository!
I'm reopening the issue.

@fzaninotto I think you can categorize this as a feature request.

There's no timeline for this. Feel free to open a PR to implement it

I guess we could add magic link as well (email login links)

Implemented in 2.0.0


Vector instructions have no RM field

The descriptions of the vector instructions here refer to the RM field, but vector instructions have no such field. The descriptions should say "current rounding mode in fscr", or something similar.

Fixed.


Support for running under mvn jetty:run

Hi Luke,
Sadly I've reverted our (Apache Isis') dependency on your library, because if I run our webapp using mvn jetty:run then the classpath system property will not be populated.  Since that's a use case we need to support, it's a bit of a showstopper.
I did a bit of playing around to see if there was another way to determine the directories/JARs to search through (eg ClassLoader.getSystemClassLoader()) but without success.  In any case, getting into the whole classloader thing w.r.t. servlet containers is not something I want to get into without a bit of care.
So this ticket is a request to see if FCS can be made to run under mvn jetty:run (and also mvn antrun:run that we use to run our app via a standalone main() bootstrap method).
Thx
Dan

Hmm, I didn't know there was any other mechanism for setting up the
classpath. How does Jetty even find its classes in that environment? Does
it manage its own classpath, and dynamically load classes?
I'm more than happy to add an API call to add custom paths to search,
and/or to read the classpath using some other mechanism.. Maybe you can
raise the question on the Maven/Jetty mailing lists to figure out how to
determine the path, and then let me know?
On Aug 2, 2015 4:18 AM, "Dan Haywood"<EMAIL_ADDRESS>wrote:

Hi Luke,
Sadly I've reverted our (Apache Isis') dependency on your library, because
if I run our webapp using mvn jetty:run then the classpath system property
will not be populated. Since that's a use case we need to support, it's a
bit of a showstopper.
I did a bit of playing around to see if there was another way to determine
the directories/JARs to search through (eg
ClassLoader.getSystemClassLoader()) but without success. In any case,
getting into the whole classloader thing w.r.t. servlet containers is not
something I want to get into without a bit of care.
So this ticket is a request to see if FCS can be made to run under mvn
jetty:run (and also mvn antrun:run that we use to run our app via a
standalone main() bootstrap method).
Thx
Dan
—
Reply to this email directly or view it on GitHub
https://github.com/lukehutch/fast-classpath-scanner/issues/18.

It may not be servlet containers per se (though the classpath loading for
servlet containers is non trivial, see eg [1]).
I think with mvn jetty:run etc the problem is with mvn, which evaluates the
classpath from the pom and then must set up the classpath dynamically.
This stack overflow [2] offers some clues
I shall let you explore some more... afraid I can't get too sidetracked
with this myself right now.
Thx
Dan
[1] https://www.mulesoft.com/tcat/tomcat-classpath
[2]
http://stackoverflow.com/questions/773855/setting-the-a-property-to-what-maven-compile-classpath-contains-without-ant
On 2 August 2015 at 22:18, Luke Hutchison<EMAIL_ADDRESS>wrote:

Hmm, I didn't know there was any other mechanism for setting up the
classpath. How does Jetty even find its classes in that environment? Does
it manage its own classpath, and dynamically load classes?
I'm more than happy to add an API call to add custom paths to search,
and/or to read the classpath using some other mechanism.. Maybe you can
raise the question on the Maven/Jetty mailing lists to figure out how to
determine the path, and then let me know?
On Aug 2, 2015 4:18 AM, "Dan Haywood"<EMAIL_ADDRESS>wrote:

Hi Luke,
Sadly I've reverted our (Apache Isis') dependency on your library,
because
if I run our webapp using mvn jetty:run then the classpath system
property
will not be populated. Since that's a use case we need to support, it's a
bit of a showstopper.
I did a bit of playing around to see if there was another way to
determine
the directories/JARs to search through (eg
ClassLoader.getSystemClassLoader()) but without success. In any case,
getting into the whole classloader thing w.r.t. servlet containers is not
something I want to get into without a bit of care.
So this ticket is a request to see if FCS can be made to run under mvn
jetty:run (and also mvn antrun:run that we use to run our app via a
standalone main() bootstrap method).
Thx
Dan
—
Reply to this email directly or view it on GitHub
https://github.com/lukehutch/fast-classpath-scanner/issues/18.

—
Reply to this email directly or view it on GitHub
https://github.com/lukehutch/fast-classpath-scanner/issues/18#issuecomment-127072440
.

Thanks, I took a look at this, and it looks complicated. Tomcat's use case might be a bit too niche to support, but Maven probably needs supporting. For my own reference, it looks like I'll need to use the plexus-classworlds API to get at Maven's classpath: https://github.com/sonatype/plexus-classworlds
I don't know if I'll be able to get to this for a while, but meanwhile, I added the method .overrideClasspath(customClasspath) so that you can at least pass in your own path when running under Maven. I don't know if this will solve your problem, since it requires an additional configuration step, but it's a start.

OK, thanks.
On 3 August 2015 at 11:19, Luke Hutchison<EMAIL_ADDRESS>wrote:

Thanks, I took a look at this, and it looks complicated. Tomcat's use case
might be a bit too niche to support, but Maven probably needs supporting.
For my own reference, it looks like I'll need to use the plexus-classworlds
API to get at Maven's classpath:
https://github.com/sonatype/plexus-classworlds
I don't know if I'll be able to get to this for a while, but meanwhile, I
added the method .overrideClasspath(customClasspath) so that you can at
least pass in your own path when running under Maven. I don't know if this
will solve your problem, since it requires an additional configuration
step, but it's a start.
—
Reply to this email directly or view it on GitHub
https://github.com/lukehutch/fast-classpath-scanner/issues/18#issuecomment-127185371
.

OK, I may have been able to solve this in the last commit (see the code in parseSystemClasspath()). I basically walk up the call stack and pick up any classloaders at any level of the stack. This, I think, will solve the classloader issue for Maven at least -- not sure about Tomcat apps though. Would appreciate if you could please test and let me know.

ok, will do.  thanks.
On 3 August 2015 at 12:18, Luke Hutchison<EMAIL_ADDRESS>wrote:

OK, I may have been able to solve this in the last commit (see the code
in parseSystemClasspath()). I basically walk up the call stack and pick up
any classloaders at any level of the stack. This, I think, will solve the
classloader issue for Maven at least -- not sure about Tomcat apps though.
Would appreciate if you could please test and let me know.
—
Reply to this email directly or view it on GitHub
https://github.com/lukehutch/fast-classpath-scanner/issues/18#issuecomment-127198884
.

Did the new changes to classloader detection work for your situtation? If not, would it be helpful to be able to manually specify a path to scan?

I didn't get the chance to try them out... getting close to a release so
decided best to revert for now. Will look again when start work on next dev
phase.
Thx, Dan.
On 19 Aug 2015 09:08, "Luke Hutchison"<EMAIL_ADDRESS>wrote:

Did the new changes to classloader detection work for your situtation? If
not, would it be helpful to be able to manually specify a path to scan?
—
Reply to this email directly or view it on GitHub
https://github.com/lukehutch/fast-classpath-scanner/issues/18#issuecomment-132484821
.

Hi Dan, I just pushed some fixes that make classpath scanning work much better in the case of jar files that specify their own classpaths. (1) I support ".war" as a jarfile extension, and (2) I support "Class-Path:" entries in a jar's manifest file. This may fix the issue you raised with Jetty (not sure about Maven). When you get done with your release, it would be great if you could please test the HEAD version again. Thanks!

Hi Dan, I fixed one more issue with Maven classpath support: Maven sometimes uses "file:" URIs for classpath entries. With this and the other fixes described previously, I'm pretty sure Maven support is fixed, although I don't know how to properly test Jetty or Tomcat.
I'll close this bug for now, feel free to reopen or open a new bug if you find something is still broken. Thanks for the report.


Looking for FUD Crypter

Can anyone recommend any Free/Cheap FUD Crypter/Obfuscator that makes this undetected?

Im seaching too..Let me know if you find it.

Im seaching too..Let me know if you find it.

Contact me on discord username is:Silentsniper0


fix: Always create cookie store with network context (3-1-x)

Description of Change
Backports https://crrev.com/c/1152083
Ref https://github.com/electron/electron/pull/15836
Checklist

[x] PR description included and stakeholders cc'd
[x] Patch information is added to appropriate .patches.yaml
[x] script/update runs without error
[x] PR title follows semantic commit guidelines

../../services/network/network_context.cc:323:12: error: member reference type 'network::URLRequestContextBuilderMojo *' is a pointer; did you mean to use '->'?
    builder.SetCookieAndChannelIdStores(std::move(cookie_store),
    ~~~~~~~^
           ->

@codebytere lets merge this, the 3-1-x libcc bump will use the merge commit and these builds are useless.


2021-02-14 Version 3.6.1: Fixed build issues

Codecov Report

Merging #77 (ce78382) into master (a299d75) will not change coverage.
The diff coverage is n/a.

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


Submit App to F-Droid

Look at adding the app to the F-Droid store https://gitlab.com/fdroid/fdroiddata/blob/master/CONTRIBUTING.md

Hi all, I started the F-droid import process in this repository.
It currently runs into these 6 errors during the build process:
* ERROR: Found Android DEX code at node_modules/capacitor-file-selector/android/build/.transforms/22e8b49399b3a302abdaacacc9519ef6/classes/classes.dex
* ERROR: Found usual suspect 'firebase' at<EMAIL_ADDRESS>* ERROR: Found usual suspect 'google.*play.*services' at<EMAIL_ADDRESS>* ERROR: Found usual suspect 'firebase' at<EMAIL_ADDRESS>* ERROR: Found usual suspect 'google.*play.*services' at<EMAIL_ADDRESS>* ERROR: Found binary at .gradle/5.6.4/fileChanges/last-build.bin

The .dex  file generated by the capacitor file selector, mention of firebase, and mention of play services seem to be triggering F-droid's blacklist. I'm not sure what the last error is about.. just looks like a lingering cached binary.
We'll have to find alternatives for these libraries, otherwise it looks like F-droid is a no-go. 😢

Thanks @danielloera for taking the time to look at this.
From what I can tell if we want to make use of capacitor we need to use plugins that use version 3. They have unbundled firebase and Google services out and in to individual modules.
I'm sure we can find a file selector package that will support this change.

So if I understand correctly, mentions of firebase and play services are coming from the capacitor file selector? And not from direct use by the app?

That is correct. capacitor is a successor to Cordova created by Ionic.
Here is a mention of it. https://github.com/ionic-team/capacitor/discussions/3443
We will look to see if there is an alternative file selector else if we can update the capacitor-file-selector itself to use capacitor 3

Did a little bit of digging and found:
https://www.npmjs.com/package/capacitor-file-select
This uses capacitor 3.
I tried updating this repo to use it but ran into a number of errors related to upgrading the project to cap 3.

My in-progress conversion can be found here:
https://github.com/danielloera/mymonero-android-js
I was able to use capacitor-file-select successfully but unfortunately, as far as I can tell, the QR scanner plugin no longer works. I think the community-managed qr-scanner is our best bet but it it does not currently support cap v3.. 🙃

Support for v3 is "coming soon"! https://github.com/capacitor-community/barcode-scanner/issues/23#issuecomment-819423100
I'll keep an eye out for the update

Looks like we can continue with this as capacitor 3 is now a stable release as of this week

We will still need to find appropriate plugins that use cap 3.

Hi @danielloera
I was able to get the following branch working with a barcode scanner:
https://github.com/mymonero/mymonero-android-js/tree/capacitor3-migration
Once I've wrapped up the multi-currency exchange code, I'll pull your branch, merge mine into it, test everything, and if working, open a PR to the develop branch. You're more than welcome to work on it in the interrim, but I don't want to impose on your time schedule given that you've already helped us along.
Thank you for your assistance with this :-)

Open source ftw, picked up on what you guys did and combined it all into #82


twitter bot: Update instructions.

This is the docs update for #P89.

Looks great, merged, thanks @derAnfaenger!  We should be sure to do a pypi release soon so that the instructions actually match the code on pypi.  I guess maybe a good opportunity to test @eeshangarg's work on automating the release process :).


Can't use command on iOS12?

It's normal on iOS10, but I can't use it on iOS12.......

http://newosxbook.com/articles/MDGA.html

http://newosxbook.com/articles/MDGA.html

The third QiLin tool csflags does not seem to support iOS12.........

The link was to show you why LLDB was not working. Perhaps you can patch QiLin to your iOS version or notify the authors of the jailbreak you're using to provide support for debugging apps that you shouldn't be allowed to debug.

can this be closed?