repository failure when updating mantl nodes using ansible

Whern running
ansible-playbook playbooks/upgrade-packages.yml
the following error occurs and only 2 nodes are successful
TASK: [refresh yum cache] *****************************************************
failed: [mantl-control-01] => {"changed": true, "cmd": ["yum", "makecache"], "delta": "0:00:00.560416", "end": "2009-10-01 11:08:47.928627", "rc": 1, "start": "2009-10-01 11:08:47.368211", "warnings": ["Consider using yum module rather than running yum"]}
stderr:
One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Disable the repository, so yum won't use it by default. Yum will then
    just ignore the repository until you permanently enable it again or use
    --enablerepo for temporary usage:

        yum-config-manager --disable <repoid>

 4. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
stdout: Loaded plugins: fastestmirror, langpacks
failed: [mantl-worker-002] => {"changed": true, "cmd": ["yum", "makecache"], "delta": "0:00:00.584094", "end": "2009-10-01 11:08:47.952997", "rc": 1, "start": "2009-10-01 11:08:47.368903", "warnings": ["Consider using yum module rather than running yum"]}
stderr:
One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Disable the repository, so yum won't use it by default. Yum will then
    just ignore the repository until you permanently enable it again or use
    --enablerepo for temporary usage:

        yum-config-manager --disable <repoid>

 4. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
stdout: Loaded plugins: fastestmirror, langpacks
failed: [mantl-worker-003] => {"changed": true, "cmd": ["yum", "makecache"], "delta": "0:00:00.674464", "end": "2009-10-01 12:10:42.225450", "rc": 1, "start": "2009-10-01 12:10:41.550986", "warnings": ["Consider using yum module rather than running yum"]}
stderr:
One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

 3. Disable the repository, so yum won't use it by default. Yum will then
    just ignore the repository until you permanently enable it again or use
    --enablerepo for temporary usage:

        yum-config-manager --disable <repoid>

 4. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

        yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

mantl-control-01           : ok=1    changed=1    unreachable=0    failed=1
mantl-control-02           : ok=1    changed=1    unreachable=0    failed=1
mantl-control-03           : ok=1    changed=1    unreachable=0    failed=1
mantl-edge-01              : ok=4    changed=2    unreachable=0    failed=0
mantl-edge-02              : ok=1    changed=1    unreachable=0    failed=1
mantl-worker-001           : ok=4    changed=2    unreachable=0    failed=0
mantl-worker-002           : ok=1    changed=1    unreachable=0    failed=1
mantl-worker-003           : ok=1    changed=1    unreachable=0    failed=1

Ansible version (ansible --version):  1.9.6
Python version (python --version): 2.7.5
Git commit hash or branch:
Cloud Environment: CentOS 7 with vsphere/vcenter
Terraform version (terraform version): 0.6.16

@ACluelessOne Looks like your machines can't connect to the Centos repo. Are you sure they're connected to the internet? Have you tried running the playbook again?

They are connected to the internet, i can ping websites

@ACluelessOne Can you try manually running yum makecache on your machines?
You might also try removing that task from the playbook and running ansible-playbook again.

One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail.
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
I got this error when running makecache

@ACluelessOne What's the output of
yum info epel-release

same error

@ACluelessOne I'm just searching on DuckDuckGo now, but you can try:
yum --disablerepo=epel -y update  ca-certificates

And
yum --disablerepo=epel info epel-release

Installed Packages
Name        : epel-release
Arch        : noarch
Version     : 7
Release     : 7
Size        : 24 k
Repo        : installed
From repo   : epel
Summary     : Extra Packages for Enterprise Linux repository configuration
URL         : http://download.fedoraproject.org/pub/epel
License     : GPLv2
Description : This package contains the Extra Packages for Enterprise Linux
: (EPEL) repository GPG key as well as configuration for yum.
no packages marked for updates when i try to update ca-certificates

@ACluelessOne What's the output of date?

Fri Oct  2 02:59:40 UTC 2009

isit due to wrong date?

@ACluelessOne See anything wrong? :wink: That needs to be set correctly.

@ACluelessOne See #1696. TLS certificates can't be verified unless the date is set correctly.

@ACluelessOne Please reopen if your issue isn't solved after setting the proper date. I've made a new issue for getting a more intuitive error message. Thanks for bringing this to our attention!

thanks a lot!!!


Link prefetching

We should support optional prefetching (and maybe preloading) of pages under various circumstances:

When the link enters the view port
When the link is hovered on
Programatically

Hi thank you for your work, is it something that is still on the roadmap or it is already developed ?

Hi, thank you!
It's still on the map. It's not particularly hard or anything, I just haven't needed it yet :D
Do you need it for a particular case or ideas on how to implement it? Maybe we can start a discussion.

I'm just asking, I discovered the feature on Next.js and I wanted to know if the feature was implemeted on Rakkas and I popped on this issue.
So I have no particular new ideas on this subject but it will be very cool if the feature is implemented 😁.

And after some researches, it's seem that it can be really useful to provide fast navigation between pages to users. The user don't click immediately on a link so you can gain some milliseconds

Implemented in #157 and released in 0.7.0-next.21.


Tokenize as part of the public API?

I'd like to clarify if dask.base.tokenize is part of the public API or not.
Basically, I'd like to replicate the rules used for name by dask's imread and read_csv when opening up a netCDF file in xray. To do this, it would be nice to be able to use dask's tokenize.

I'd say you should be able to use it, but be aware that there also might be changes in the future as we work more on the deterministic names.

This could be two questions:

Can we depend on the future existence of the function dask.base.tokenize
Can we depend on the consistent operation of this function.

I'm comfortable saying "yes" to 1 with moderately high probability and "no" to 2 with moderately high probability.

I'm happy with those constraints. As long as tokenize has a consistent signature, I'm happy. The goal is only to produce results that are consistent with dask -- they don't need to be fixed across versions.
On Sun, Aug 16, 2015 at 9:19 AM, Matthew Rocklin<EMAIL_ADDRESS>wrote:

This could be two questions:

Can we depend on the future existence of the function dask.base.tokenize
Can we depend on the consistent operation of this function.
I'm comfortable saying "yes" to 1 with moderately high probability and "no" to 2 with moderately high probability.

Reply to this email directly or view it on GitHub:
https://github.com/ContinuumIO/dask/issues/593#issuecomment-131578053

@jcrist do you anticipate any API changes?  If not then we can probably close this.

I don't. Implementation will probably change some, but the api is probably solid.


Also detecting desktop scroll/drag events

This library is great, works like a charm for touch devices.
But I also had a use-case where I wanted the swipe behavior to be similar for all devices. So is it possible to make it work for all devices?

Hi @UserSina,
Could you please provide examples of devices you would like to be supported?


[Breaking] Trainer completely breaks on GCP TPU VMs

🐛 Bug
Running the Lightning Trainer with TPUs on GCP TPU VMs leads to complete training failures - processing a single batch with any model takes forever, and eventually (on the order of ~20 batches, or 3 minutes!) completely stalls. This is notably with the provided MNIST example.
However, writing the equivalent "native" PyTorch code has no problems, completing a full epoch (~54 batches of MNIST) in only 8 seconds. Full code, logs (stdout & stderr), and XLA profiler report are in this Gist, with components listed below.
This is a semi-critical bug that's seriously affecting adopting PyTorch-Lightning for TPU workloads! The "native" loop only takes 8 seconds per epoch, but using the Trainer stalls at 20 batches in 2m30s.
Environment
This is using a TPU-v2-8 VM (but only training on a Single Core) with the default PyTorch 1.11 VM. I've checked versions for all necessary libraries, and include them below.

PyTorch Lightning Version (e.g., 1.5.0): 1.6.3 (latest, stable)
PyTorch Version (e.g., 1.10): 1.11
PyTorch XLA: 1.11
Python version (e.g., 3.9): 3.8.10
OS (e.g., Linux): Linux
Any other relevant information: This is using the new "one-stop" TPU VMs, not the older (soon-to-be deprecated) TPU Nodes.

To Reproduce

"Native" PyTorch Script with handwritten training loop and TPU device placement: debug_native.py

Produces this log file w/ stdout & stderr
Also dumped output of the XLA metrics report

Lightning Trainer Script: debug_lightning.py

Important: Training stalled out ~20 batches... had to kill process, impacting logging.
Produces this log file w/ stdout & stderr
Also dumped output of the XLA metrics report

Both python scripts are standalone, and should be runnable on TPU devices as-is.
Additional context
Not immediately clear what the problem is from the XLA metrics, but one thing to note is that the default behavior of the Lightning Trainer is to print the train loss in the progress_bar every step... this call hides an implicit .item() which is bad for TPUs/XLA?
Some runs with the Lightning Trainer (with PT_XLA_DEBUG=1) also sometimes point to pytorch_lightning.utilities.data and the function has_len_all_ranks() as implementing an "unlowered op"... but this alone doesn't account for the huge performance discrepancy.
cc @kaushikb11 @rohitgr7 @borda @akihironitta

We recently made some TPU fixes (cc @awaelchli). Would you mind trying on the latest version? (1.7.0rc0)

I'm getting similar behavior on pt-lightning 1.7.0 with all same specs except running on GCP TPU-v3-8 VM. 70 seconds per batch, breaks after 13 batches. (for reference: batch size of 128 images of dimension 96x96 with resent-50 backbone, tried 4096 previously but it just breaks with out-of-HBM error. For the record, I could perform distributed training on 4 V100 GPUS with batch size of 4096 with the exact same code; seems to be TPU-specific. I had also written my code with native PyTorch-XLA on Colab TPU and it worked fine, seems that translating to pytorch-lightning and running on GCP broke it?)

We now run tests on gcloud and don't see any issues related to the top post. Closing
Happy to discuss if this is still a problem


Fixing a race DisposeAsync is called when StartAsync hasn't finished

Fixes: #248

:up::date: - I also fixed an issue where in WebSocketsTransport and LongPollingTransport where stopping a transport that has not been started resulted in a first chance exception. It wouldn't bubble up because we have an umbrella catch but still it's better to not have it.


Brad-proof: Skip to next and previous song without playing.

If player is paused, the reverse and forward buttons should go to the appropriate song without starting to play the song.
If player is playing, reverse should go to the beginning of the current song and next should go to the next song and play should continue from there.

Closed by pull request #175


How can I change the character color after finishing a quiz?

Hello, how can I change the character color after finishing a quiz?
For example, I want to draw the strokes with a blue color, then when I finish it, it shows me the character in green.

Use writer.updateColor in onComplete()
const writer = HanziWriterClass.create("#element", "上", {
  width: 400,
  height: 400,
});

writer.quiz({
  onComplete() {
    // The color for the highlight animation that pulses in/out for ~1.5s
    writer.updateColor("highlightColor", "#ffc000");
    // Change character stroke color
    writer.updateColor("strokeColor", "#24ff04");
  }
});

Thank you very much!
El jue., 1 abr. 2021 12:04 a. m., jamsch @.***>
escribió:

Use writer.updateColor in onComplete()
const writer = HanziWriterClass.create("#element", "上", {
width: 400,
height: 400,
});
writer.quiz({
onComplete() {
// The color for the highlight animation that pulses in/out for ~1.5s

writer.updateColor("highlightColor", "#ffc000");

// Change character stroke color

writer.updateColor("strokeColor", "#24ff04");

}
});
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chanind/hanzi-writer/issues/225#issuecomment-811621730,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARPWHFDABF2CGKC5Z3B4JEDTGPWDDANCNFSM4Z5BZWJA
.


Don't assume indentation increases for void elements

Fixes https://github.com/dotnet/razor/issues/8836

/azp run

/azp run

Too used to flaky tests, this failure is actually real, and indicates a gap in our unit testing which I will happily now fill 🤦♂


phoc: 0.31.0 -> 0.35.0

Description of changes
The Phosh 0.35.1 release contains:

phoc 0.35.0
Phosh 0.35.0. That is PR #275037, but I also updated in this PR because it's impossible to test phoc without phosh.
phosh-mobile-settings 0.35.1, because why not.

The Phosh/phoc release tarballs URL has changed from storage.puri.sm to sources.phosh.mobi. I have updated the source urls for the above three packages, so that auto-bot-updates should work from now on.
phoc-0.35.0 now uses wlroots-0.17.1. Even so, it still needs to hack out the height 0 error check in wlroots, otherwise Phosh will crash at startup. This patch needs to be updated, so I just grab it out of phoc.src, rather than using fetchpatch. I have also added the wlroots dependency as an attribute of phoc. This is better for cases when users need to override the phoc package.
cc @masipcat @tomfitzhenry @zhaofengli
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[x] darwin N/A

Tested, as applicable:

[x] nixos/tests/phosh.nix (x86_64-linux only)
[x] Added a testers.testVersion as pkgs.phoc.tests.version
[x] Tested on a pinephone, built with --system aarch64-linux

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD".
[x] Tested basic functionality of ./result/bin/phoc. This is covered by phoc.tests.version and phoc.tests.phosh.
[x] 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes) N/A
[x] Fits CONTRIBUTING.md.

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

as for phosh-mobile-settings, i would be very thankful if anyone wishes to take over maintainership. i've been derelict on that one because i'm unable to test it on actual hardware anymore.

as for phosh-mobile-settings, i would be very thankful if anyone wishes to take over maintainership.

I can do it, thanks @uninsane.

Thanks for checking @tomfitzhenry.
As can be seen from those screenshots, and also from testing on my pinephone configuration, it looks like Phosh has changed the desktop file filtering or something like that. Apps such as Chatty and Calls are not present in the launcher.
The phosh-mobile-settings app does appear in the launcher, perhaps because it removes OnlyShowIn=Phosh; from the .desktop file :thinking:. I will investigate...

I figured out the reason for missing desktop launchers: My own configuration had broken the PATH setting for sm.puri.Phosh.service, meaning that only desktop entries with absolute paths in ExecStart= were available.
In the process, I realised that we have XDG_CURRENT_DESKTOP=GNOME set as a default by gnome-session. This is fixed by copying more settings from upstream phosh.service.

This is ready for a final review and merge now.
There are now 0.36.0 tags released, but they can be handled with automatic nixpkgs-update PRs.


Amalgamate "stop" and "cancel" commands for spectrometers

Description
DO NOT MERGE BEFORE v1.3
The OPUS API allows for sending both a "cancel" and a "stop" command during a measurement. "Cancel" stops the measurement immediately but it's not apparent what "stop" does (maybe it stops after the current series of measurements?). Either way, we don't need the separate stop command, so let's just drop the stop command and replace it with what we're currently calling cancel.
This means we can simplify SpectrometerBase slightly and drop a button from the GUI.
This code needs to be tested on real hardware before being merged. You will need the spectrometer for this.
A reasonable test would be:

Choose the "FINESSE (with DP9800)" hardware set from the dropdown box in the top left and click "Connect"
In the spectrometer panel, click the "Connect" button
Try starting a measurement by clicking the "Start" button and confirm that it has started in OPUS
Try cancelling this measurement partway through by clicking the "Stop" button and confirm that it has stopped in OPUS
Try running a measure script (I've attached an example one, but any should do)

Fixes #471.
Type of change

[x] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Documentation (non-breaking change that adds or improves the documentation)
[ ] Optimisation (non-breaking, back-end change that speeds up the code)

Key checklist

[x] Pre-commit hooks run successfully (pre-commit run -a)
[x] All tests pass (pytest)
[ ] The documentation builds without warnings (mkdocs build -s)
[x] Check the GUI still works (if relevant)
[ ] Check the code works with actual hardware (if relevant)
[ ] Check the pyinstaller-built executable works (if relevant)

Further checks

[x] Code is commented, particularly in hard-to-understand areas
[x] Tests have been added or an issue has been opened to tackle that in the future. (Indicate issue here: # (issue))

Something like that, though honestly I think the concepts ended up a bit confused in my head too :stuck_out_tongue: .
For the dummy device, I was treating stop() as meaning that the measurement had completed successfully and cancel() as meaning that it had been aborted, but that did mean that users could in theory prematurely trigger a successful end to the measurement, which is a bit weird. _on_measure_finished does the same thing as stop did (it just transitions to the "finishing" then "connected" states), but users now can't trigger it directly.

I've run the tests in lab, and confirm that they are working.


Collections In C++

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[ ] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?
This fixes #4767

This fixes #4767

Please always use the template provided by us.
I edited your initial comment and added the template. Check what matches your article.

@tetie, your article is too short of content. Kindly add more about collections. Also, ensure all code snippets are well explained!

t seems this PR is still quite a bit aways from being completed. It also seems this PR is rather light on substance. We will be closing this and please re-submit when it is ready to be published as a new PR (and you can add the duplicate label) and ping the reviewer.
Closing a PR does NOT mean the article can not be published (or fixed) it simply means that the edits, revisions, and fixes will happen outside of the queue. 👍 Be sure to consult previously published materials to get a better understanding of the level of quality the community expects.
Please feel free to go through our provided resources as well - those are there to help all our students improve their overall technical writing. To be able to take those skills to any position or program.


Actually use precomputed cached witness

This PR recovers a mechanic from Alpha's witness generation that wasn't integrated in LEM (my bad)

!gpu-benchmark


Bug in express-session: Store is a class

https://github.com/borisyankov/DefinitelyTyped/blob/da2bb07e037a61e6ead149ae89063b00892f6929/express-session/express-session.d.ts#L56-L62
Store is actually an abstract class, in the  express-session definition.
See here:

https://github.com/expressjs/session/blob/a7f7f6766f0877930b8c5dd09b59186ded0ce9c9/session/store.js#L23
https://github.com/expressjs/session/blob/a7f7f6766f0877930b8c5dd09b59186ded0ce9c9/session/memory.js#L39

This bug makes it impossible to access session.Store to extend it:

@phillips1012 please send a PR. I'll review it.


Android Mixpanel exception in application opening

I am getting the following exception in some cases, not always. This happen when my application is opened, this is very rarely and my application crashes, I need help to know why this could be happening. In advance thanks!
09-14 08:27:26.466  12986-13051/com.app.kuona E/CursorWindow﹕ Failed to read row 0, column 0 from a CursorWindow which has 0 rows, 3 columns.
09-14 08:27:26.499  12986-13051/com.app.kuona E/MixpanelAPI.Messages﹕ Worker threw an unhandled exception
java.lang.IllegalStateException: Couldn't read row 0, col 0 from CursorWindow.  Make sure the Cursor is initialized correctly before accessing data from it.
        at android.database.CursorWindow.nativeGetLong(Native Method)
        at android.database.CursorWindow.getLong(CursorWindow.java:511)
        at android.database.AbstractWindowedCursor.getLong(AbstractWindowedCursor.java:75)
        at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:220)
        at android.database.AbstractCursor.moveToNext(AbstractCursor.java:245)
        at com.mixpanel.android.mpmetrics.MPDbAdapter.generateDataString(MPDbAdapter.java:254)
        at com.mixpanel.android.mpmetrics.AnalyticsMessages$Worker$AnalyticsMessageHandler.sendData(AnalyticsMessages.java:405)
        at com.mixpanel.android.mpmetrics.AnalyticsMessages$Worker$AnalyticsMessageHandler.sendAllData(AnalyticsMessages.java:393)
        at com.mixpanel.android.mpmetrics.AnalyticsMessages$Worker$AnalyticsMessageHandler.handleMessage(AnalyticsMessages.java:268)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:135)
        at android.os.HandlerThread.run(HandlerThread.java:61)
09-14 08:27:26.500  12986-13051/com.app.kuona E/MixpanelAPI.Messages﹕ Mixpanel will not process any more analytics messages
java.lang.IllegalStateException: Couldn't read row 0, col 0 from CursorWindow.  Make sure the Cursor is initialized correctly before accessing data from it.
        at android.database.CursorWindow.nativeGetLong(Native Method)
        at android.database.CursorWindow.getLong(CursorWindow.java:511)
        at android.database.AbstractWindowedCursor.getLong(AbstractWindowedCursor.java:75)
        at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:220)
        at android.database.AbstractCursor.moveToNext(AbstractCursor.java:245)
        at com.mixpanel.android.mpmetrics.MPDbAdapter.generateDataString(MPDbAdapter.java:254)
        at com.mixpanel.android.mpmetrics.AnalyticsMessages$Worker$AnalyticsMessageHandler.sendData(AnalyticsMessages.java:405)
        at com.mixpanel.android.mpmetrics.AnalyticsMessages$Worker$AnalyticsMessageHandler.sendAllData(AnalyticsMessages.java:393)
        at com.mixpanel.android.mpmetrics.AnalyticsMessages$Worker$AnalyticsMessageHandler.handleMessage(AnalyticsMessages.java:268)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:135)
        at android.os.HandlerThread.run(HandlerThread.java:61)
09-14 08:27:26.577  12986-12998/com.app.kuona A/libc﹕ Fatal signal 11 (SIGSEGV), code 2, fault addr 0xa2a90a20 in tid 12998 (FinalizerDaemon)

Thanks for writing in!!
What I'm really curious about is CursorWindow. I don't think it's part of our library and looks like it's related to your database.
From the log Failed to read row 0, column 0 from a CursorWindow which has 0 rows, 3 columns., I guess the problem is that you are accessing a row which doesn't exist. And then Mixpanel gets mad as it can't access it.
Please let me know your thoughts and how it goes!!

The android.database.CursorWindow class appears to be from Android. The log from mixpanel did not crash my application. Finally I fond the reason of my Fatal signal 11 (SIGSEGV), this was caused by serialize android.location.Location with Gson and on deserialize this was causing the error in some cases.


ternary operations

beautify format for ternary operations if line length more to wrap_line_length
var some = question
    ? value1
    : value2;

+1

although possible duplicate of #605

If either of you are interested, bitwiseman and I are discussing implementation on this thread.  Please join in if you have any input.
I only raise this because what began as 'ternary operations' newline placement is broadening out to all operators.  Right now we're hashing out which operators possibly belong on a newline.

#735 added option to control this.

cool! thanks


Ex 5 Submission

Score: 3
Chemical Accuracy: 2.328134 mHa
Number of Parameters in the Ansatz: 69

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

Sorry for the delay. Thank you very much for your submission!


Update API method documentation

Update XDR in JSON examples
replace getLedgerEntry by getLedgerEntries

Something went wrong with PR preview build please check

Preview is available here:http://soroban-docs-pr445.previews.kube001.services.stellar-ops.com/


The git icon on the right side points to the wrong repo

The fast.ai web site https://course.fast.ai/ was created from this repo ( https://github.com/fastai/course22-web)
But the github reference is to  https://github.com/fastai/course22 which is misleading.
The error is in _quarto.yml:
repo-url: https://github.com/fastai/course22
should be changed to
repo-url: https://github.com/fastai/course22-web
and this change should also be done for the navbar

Thanks - fixed now.


Simplified BigDecimal support

Regarding this:
http://sourceforge.net/mailarchive/forum.php?thread\_id=5896978&forum\_id=6969
I've slightly modified some source files to support + -
* / > < >= <= == for BigDecimal. Please consider this
is an important enhancement to Loosely Typed Java Syntax.
Attached are the modified files (.java) and the
original files(.java.old from beanshell 2.0b4).
Reported by: gdressino
Original Ticket: "beanshell/feature-requests/11":https://sourceforge.net/p/beanshell/feature-requests/11

Already implemented in BeanShell 3.0.0-SNAPSHOT.841
bsh % BigDecimal a = 1;
--> $1 = 1.0w :BigDecimal
bsh % BigDecimal b = 2;
--> $2 = 2.0w :BigDecimal
bsh % a + b;
--> $7 = 3.0d :Double
bsh % a - b;
--> $8 = -1.0d :Double
bsh % a * b;
--> $9 = 2.0d :Double
bsh % a / b;
--> $0 = 0.5d :Double
bsh % a > b;
--> $1 = false :boolean
bsh % a < b;
--> $2 = true :boolean
bsh % a >= b;
--> $3 = false :boolean
bsh % a <= b;
--> $4 = true :boolean
bsh % a == b;
--> $5 = false :boolean

Closed: works as expected


Sample QR generator

What's here (& what to consider)
*Added qrcode.react npm package
*Added QRGenerator component to utilities with such functionality as:

rendering QR Code in DOM
giving ability to download QR Code in JPEG format

*Added route for QRGenerator component for testing purposes
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[x] Incomplete / work-in-progress, PR is for discussion or feedback
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How has this been tested?

[ ] Tested locally
[ ] Test suite provides the same results as prior to making changes

Checklist

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[ ] New and existing unit tests pass locally with my changes
[x] There are no merge conflicts

Great start to the QR generator!

Looks great! Let me know if there is anything I can do to help.
Thanks for taking the lead on this!
Ready to Merge.


Verify Starling Capture signatures

Fixes #89
Fixes #91
Contains some formatting fixes done by black automatically.
This PR also adds the new JSON schemas from https://github.com/starlinglab/integrity-schema/pull/5
Before merging

[x] Replace test JSON with JSON we've captured from phone that includes Zion signature (@YurkoWasHere will capture this)
[x] In JSON schema parsing code, don't change integrity-backend to api
[x] Get sigs verifying for our own captures
[x] Test with tampered sigs and/or keys to confirm they fail (create bad folder)
[ ] Update sigs once Starling edition of 1.9.0 app comes out
[ ] Get Zion sigs working
[ ] Verify chain of trust properly from Zion to session key

Closed in favour of #104


STEM support is broken in release 1.0.0-alpha.7

The current pagedjs version 0.1.40 doesn't handle math expressions created by MathJAX.
The error message is:
> An uncaught exception happened within the HTML page: Error: TypeError: Cannot read property 'display' of undefined
    at isContainer (file:///C:/workspace/asciidoc/asciidoctor-deep-dive/asciidoctorjs/manual.html:3218:18)
    at Layout.renderTo (file:///C:/workspace/asciidoc/asciidoctor-deep-dive/asciidoctorjs/manual.html:3450:19)
    at Page.layout (file:///C:/workspace/asciidoc/asciidoctor-deep-dive/asciidoctorjs/manual.html:4066:48)
    at Chunker.layout (file:///C:/workspace/asciidoc/asciidoctor-deep-dive/asciidoctorjs/manual.html:4864:29)
    at async Chunker.renderAsync (file:///C:/workspace/asciidoc/asciidoctor-deep-dive/asciidoctorjs/manual.html:4787:17)

Example to reproduce:
= PDF created by JavaScript

:stem:

This also uses extensions to show math!

[stem]
++++
sqrt(4)^2 = 2
++++

Workaround: downgrade to 1.0.0-alpha.6
This has been fixed upstream (see https://gitlab.pagedmedia.org/tools/pagedjs/issues/190 for @Mogztter's fix), but hasn't been released in upstream yet.
This issue is to track the upstream issue and to maybe add additional test cases to catch this issue (apparently the build is green?)

This issue is to track the upstream issue and to maybe add additional test cases to catch this issue (apparently the build is green?)

Indeed, we do not have a test right now but we need one!

@ahus1 Paged.js 0.1.41 is out and the STEM support is working again!


Defend against malfored or not-understood URLs

Ensure that paths like /) or /unknown redirect to the home page instead of the generic error page.

Duplicate #632


Develop and Document Procedure to Run on Private Tenancy Without Admin Privileges

Completed

Completed, steps included in LiveLabs Workshop documentation


Fix #1245

What is the purpose of the change
fix #1245
Brief changelog
fix #1245
Verifying this change
fix #1245
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[ ] Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Codecov Report

Merging #1374 into master will decrease coverage by 0.15%.
The diff coverage is 14.28%.

@@            Coverage Diff             @@
##           master    #1374      +/-   ##
==========================================
- Coverage   32.57%   32.42%   -0.16%
==========================================
  Files         691      691
  Lines       34537    34537
  Branches     6812     6812
==========================================
- Hits        11252    11199      -53
- Misses      21357    21404      +47
- Partials     1928     1934       +6

Impacted Files
Coverage Δ

...libaba/com/caucho/hessian/io/JavaDeserializer.java
41.52% <14.28%> (ø)
:arrow_up:

...bo/rpc/cluster/support/FailbackClusterInvoker.java
71.79% <0%> (-12.83%)
:arrow_down:

...ba/dubbo/remoting/transport/netty/NettyClient.java
72.58% <0%> (-11.3%)
:arrow_down:

...ubbo/rpc/protocol/dubbo/ChannelWrappedInvoker.java
41.66% <0%> (-8.34%)
:arrow_down:

...mon/serialize/support/dubbo/GenericDataOutput.java
69.12% <0%> (-6.32%)
:arrow_down:

...a/dubbo/remoting/transport/netty/NettyChannel.java
61.25% <0%> (-5%)
:arrow_down:

...ba/dubbo/remoting/transport/netty/NettyServer.java
67.85% <0%> (-3.58%)
:arrow_down:

...mmon/serialize/support/dubbo/GenericDataInput.java
60.23% <0%> (-3.48%)
:arrow_down:

.../dubbo/rpc/protocol/dubbo/filter/FutureFilter.java
54.54% <0%> (-2.03%)
:arrow_down:

...bo/remoting/transport/netty/NettyCodecAdapter.java
55.22% <0%> (-1.5%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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


Add Example using App Insights in the Browser

How about adding a snippet about how to use app insights in the browser now that I've configured my ASP.NET Core MVC app for app insights?
Can I just use appInsights.trackEvent({ name: 'blah' }); now?

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

ID: 4b88d8c4-0013-70aa-7997-a2203afd9743
Version Independent ID: 0ab99d5e-4ebd-8cb9-3d27-efe58def249f
Content: Azure Application Insights for ASP.NET Core applications
Content Source: articles/azure-monitor/app/asp-net-core.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@spottedmahn Thank you for your feedback. I'll take a look and get back to you shortly.

You are correct that the site is now setup for using the Javascript SDK and you can call methods like appInsights.trackevent(). I will assign this to the doc author to decide whether or not to add an example in addition to the linked documentation.

FYI appInsights.trackEvent({ name: 'blah' }); didn't "work".  The event gets logged but the name was something like '[object object]'.
appInsights.trackEvent('blah'); does work though.
I got the first approach from here.  Seems like that doc page is wrong 🚫.  Thoughts?

The JS SDK Github repo has the appInsights.trackEvent({ name: 'blah' }); syntax as well, so it doesn't look like that particular doc is the problem. I'll investigate that further.

I happen to be doing some more work around this today and I re-tested.
appInsights.trackEvent({ name: 'mike d event name test' }); produces:

https://github.com/microsoft/ApplicationInsights-JS/issues/1097

The API reference has been updated 👍
I opened another issue b/c I results are not lining up with the API reference: https://github.com/microsoft/ApplicationInsights-JS/issues/1101

Closing out as this article now covers all the latest config for the client side JS:https://docs.microsoft.com/azure/azure-monitor/app/javascript

#please-close

great, thanks @mrbullwinkle 🤝


Fix crash on brake pressed on subaru forester

The brake_light signal is not a boolean (it is an int, 1 for true and 0 for false), which caused a crash
short drive: https://connect.comma.ai/111b7e3a9ff2341a/1646862114749/1646862349196

Thanks! :)


Shorten critical period in upgrade

Reduce the amount of downtime that servers have when upgrading, via a variety of tricks.
Testing plan: Upgraded a server a few times, in various configurations.

This has grown a few changes that are based on the original work but not directly, because otherwise the conflicts would be gnarly.
It would be great to get reviewed.

Merged after making the small tweak noted in https://github.com/zulip/zulip/pull/21570#discussion_r878932306, thanks @alexmv!
I worry that this script is getting ever more complicated, but I think we actually are not too far from getting to start deleting some of the more complex migration blocks due to older releases requiring an intermediate upgrade before going to main.


Allow null in evidence schema to indicate not set.

The evidence schema does not allow for non-required fields (summary_text, biological_context, metadata) to have a value of null. One must omit the field to convey that it is not set.
I believe a JSON null can carry the same semantics for a BEL Evidence. For example, if the biological_context is null then it was not captured for the evidence.
A semantic difference also exists between null and an empty array. An empty array might indicate that no biological context was provided in the literature.
This issue would be to allow the JSON null type for non-required fields.

This looks good to me. Closing.


feat(gql): Create GQL resolvers & loaders for fetching single post's upvotes

i am undecided... Do we need pagination params?
type PanoPost implements Node {
  id: ID!
  title: String!
  url: String
  content: String
  createdAt: DateTime!
  owner: User
  comments(after: String, before: String, first: Int, last: Int): PanoCommentConnection
  upvotes(after: String, before: String, first: Int, last: Int): PanoPostUpvoteConnection
}

or not?
  upvotes: PanoPostUpvoteConnection


Flesh out README.md and clarify RE names

Overview
We need to get the README.md in shape.
Deliverables

[x] update 'catalyst-resource-jest' and update coverage with improved counting
[x] add 'Install' section
[x] add 'Usage' section
[x] add 'Regex reference' section (built from regexes)
[x] update RE names for clarity

Work for this issue will begin begin on branch work-liquid-labs/regex-repo/17.


How to handle unexpected alerts  in  Robotium

From<EMAIL_ADDRESS>on January 06, 2012 02:33:42
What steps will reproduce the problem? 1.solo.clickOnButton(S_BUTTON);
solo.clearEditText(0);
solo.enterText(0, GPData.USERID);
solo.enterText(1, GPData.PWD);
//If i get the unexpected after the above statement, robotium is not able to handle that alert it does nothing..
solo.clickOnButton(SIGN_IN_BUTTON); 2. 3. What is the expected output? What do you see instead? There should be some mechanism in Robotium to handle the unexpected alerts. What version of the product are you using? On what operating system? Robotium 3.0 Please provide any additional information below.
Original issue: http://code.google.com/p/robotium/issues/detail?id=203

From<EMAIL_ADDRESS>on January 06, 2012 11:47:22
The issue is that Robotium can not know that it is an unexpected alert. Therefore no mechanism can be built in as it can not know if an alert is excepted or not.
Status: WontFix


Prioritization

@danielgolden and I just chatted about the things that need work on the site, and I decided it would be really helpful to have a place to document the priorities. In rough order from my perspective, here's the prioritized list:

[x] Blog work (see #9)
[ ] Demo page cleanup (see #12)
[ ] Why HospitalRun page (see #15)
[ ] Features page (see #6)
[ ] Contributors page
[ ] Partners page (see #30)
[ ] Documentation (see #14)

cc @tangollama and @tracicakes who may have also input on the prioritization.

👍 This priority order is a check! Blog really is most important right now as we launch into doing PR middle of July.

@jglovier Hello, I am a front-end web developer. Would be glad to contribute to hospital run. Could I take up the task of making the above pages? Kindly do guide me with formalities :+1: (signing CLA etc)

@shaz13 thanks for your interest in contributing! We don't have a CLA right now, so not really any formalities. Just fork the project and open a PR with your work.
Most of the outstanding pages still need some design work before there is anything to build. Is design work something you're interested/able to contribute?
If so, then lets talk more about that in one of the dedicated issues for the outstanding pages. If not, then we'd still love to have your help building the pages once we get the design direction finalized.

Yes, I am interested in the design work. Please let me know of any improvements at current outstanding pages.


Allow wishlist items with pledges to be deleted

Playing around locally, I tried to delete a wishlist item with a pledge attached. It blew up with the following error:
ActiveRecord::InvalidForeignKey in WishlistItemsController#destroy
PG::ForeignKeyViolation: ERROR: update or delete on table "wishlist_items" violates foreign key constraint "fk_rails_d7e0620c95" on table "pledges" DETAIL: Key (id)=(15) is still referenced from table "pledges". : DELETE FROM "wishlist_items" WHERE "wishlist_items"."id" = $1

One way to solve this is by destroying dependent pledges when a wishlist item is destroyed with dependent: :destroy.

Hi @leesharma I can do that. I'll open PR soon. 😉


Remove GlobalDNS related codebase

Please check the issue for more details...
Summary

Global DNS was deprecated in v2.8.0. Removing the backend codebase related to it.

Related to https://github.com/rancher/rancher/pull/47590


[website] datathinking.org/principles

be clear
be specific

e.g. end of a highway vs end of a road; being more clear of the semantics and diction with which you communicate a problem statement (OK, sorry! We changed our mind and we'd rather receive bounding boxes for the ends of a street in the jpg images. Can you please revise this?)

write it down

recognize it's hard to assess:

how you feel
what you want to do

there are many factors at play, and tools like chatgpt can help you receive rapid feedback on which stage of the process you are at.
for example, are you clarifying a research question? identifying an unmet need in a population of stakeholders? designing a user interface to meet a need using artificial intelligence?
then:

see the available tools
tricks from google:

"plt" -matplotlib "point cloud" "annotat*"

feel, ask, do, think
thinking:

reflect, revise
find alternative tools (ask chatgpt, lean on code examples, etc)
respect how you feel (frustrated, impatient, giving up on a project, going in circles), and go back to asking for help, advocating for yourself
understand incentives (e.g. not being able to install dependencies, being blocked on VPN and limited in access, bureaucracy in getting and understanding data)
try to revise the research question (e.g. instead of cars, ends of roads or annotation pipelines) in hopes that existing solutions may generalize to yours

OK, sorry! We changed our mind and we'd rather receive bounding boxes for the ends of a street in the jpg images. Can you please revise this?
claude:
That is a quite different task! For street segmentation and finding end points, you'll want a semantic segmentation model rather than an object detector.
Here is an example using PyTorch and a pretrained segmentation model (DeepLabV3):
model = torch.hub.load('pytorch/vision:v0.10.0', 'deeplabv3_resnet101', pretrained=True)
model.eval()
img = torch.rand(3, 800, 1200)  # sample input image
output = model(img)
Get pixel predictions - each value is a class ID
predictions = output['out'].argmax(1)
Find endpoints where road class transitions to non-road
endpoints = []
for row in range(predictions.shape[1]):
for col in range(predictions.shape[2] - 1):
if predictions[0, row, col] != predictions[0, row, col + 1]:
endpoints.append((row, col))  # (y, x) coordinate
print(endpoints)  # e.g. [(223, 562), (401, 1103), ...]
So the endpoints list will contain (y, x) coords for all the spots where the road ends.
Again, you'd feed an actual street image into img, and the rest would be largely the same. Let me know if you have any other questions!

follow the money, follow the data, follow the status (kissinger, openai, etc)
understand incentives, behavioral economics, psychology, and ethnography to understand provenance in-context
parsimoniony:

if it doesn't work for me, it won't work for them
if it doesn't work here, it won't work there
focus on edge cases to ensure data thinking artefacts are simple

focus on low latency: balance compute with performance
validate with computers and humans
math before code
be clear, be specific, write it down.
self-monitoring for behavior change.
feel, ask, think, do
start with the math
visualizations: visualize early, visualize often
style: be fancy, principled, aesthetic. axes; ismael's.
great data thinkers steal.
data: FAIR
tech: use simplest tools that are most composable and most open source and most accessible worldwide.

if it's too complicated, make it simpler (mindshare). the market doesn't reward waiting.

have one source of ground truth and understand its provenance, governance, and metadata. look at it often and reflect on what unknown unknowns you may be missing.

Articulate things clearly.
Articulate status games, optics, and incentives that drive data and drive thinking clearly.

Teach someone to see the impact of your actions and principles on others (prespcriptive vs descriptive)(

focus on etymology in naming a la websters. / jsumers


"Toplița" is listed in the drop-down menu

Description:
"Toplița" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Toplița" in the search bar.

Expected results
The location is listed in the drop-down menu as "Toplița, Argeș (Mălureni)".


Add nix to CI

Nix install is now working, however it is not tested on CI. Integration tests should also be run on nix. This might require some adjustment to the way the integration tests are run.

After looking at CI for kevm, I think we do not need to test the whole integration test suite, and just each feature of kmir (kmir parse and kmir run currently).

After looking at CI for kevm, I think we do not need to test the whole integration test suite, and just each feature of kmir (kmir parse and kmir run currently).

We are still actively developing KMIR semantics, we will need to test the integration test suite to ensure nothing is broken.

I'm not sure that we need to test it with nix again though. The same semantics that the nix distribution is built on will be tested in a different job. If we do want to test all the integration tests on nix again, we will need to set up a different way to run them, as the pytest environment is not included in the nix build - which is possible of course.


Changing Text property of SvgText doesn't have an effect

Just updated library to 2.0.0
Sample code:
XmlDocument xml = new XmlDocument();
xml.LoadXml(
    "<svg xmlns=\"http://www.w3.org/2000/svg\" xmlns:xlink=\"http://www.w3.org/1999/xlink\" width=\"400\" height=\"400\" font-size=\"20\">" +
    "<text id=\"id1\" x=\"100\" y=\"100\">Test</text></svg>");

var sampleDoc = SvgDocument.Open(xml);
sampleDoc.GetElementById<SvgText>("id1").Text = "Test Output";
sampleDoc.Write(@"c:\output.svg");

Hello may you please fix this is? It is critical in the project I am working on.
Thank you in advance.

Faced the same problem. Fixed through the SvgContentNode element inside a SvgTextSpan, as follows:
SvgText node = ...
node.Children.Clear();
node.Children.Add(new SvgTextSpan {
    Nodes = {
        new SvgContentNode { Content = text }
    }
});

Nice one, hwndmaster :)

Thanks for your reply, but unfortunately it did not work. When I use the GetXML() method it returns the data that has been loaded initially. (Same when I use the Draw() method)

For me, changing the Text property setter in SvgTextBase to the following fixed the issue (changes start after comment):
set
{
	base.Content = value;
	this.IsPathDirty = true;
	this.Content = value;

	// get this element's SvgContentNode and set its Content value
	SvgContentNode contentNode = GetContentNodes().FirstOrDefault() as SvgContentNode;
	if (contentNode == null)
		return;

	contentNode.Content = value;
}

I haven't put up a pull request for this, however, because I'm not sure if SvgTextBase can have multiple content nodes. Anyone know of a situation where that might happen? Multiple spans?


Adding more in depth docs/tutorials

The goal of this PR is to add 3 tutorials to docs/source.
Tutorial 1: Toy Example

This should be able to run on a local machine in < 10 minutes. The goal here is to just explain some settings about the code and what it is outputting

Tutorial 2: Normalizing Flow without GNPE

This would contain production settings to train a normalizing flow. The goal here is to explain the production settings and how to change them to suit the user's needs. The problem with this tutorial is I have not trained a network without GNPE for a very long time, so actually, I'm not sure what the optimal settings are. For now, I was just going to put the same settings as GNPE.

Tutorial 3: Normalizing Flow with GNPE

Same as tutorial 2, except including the GNPE. These would be the recommended settings.

Note it is still a draft at the moment since need to fix some grammar and add more tutorials but feel free to add things.

Thanks Nihar. Regarding naming, I think it would be good to call the examples something like

Toy NPE model
NPE model (production)
GNPE model (production)

That way we avoid naming things by what they are not, e.g., "No GNPE".

I have make some edits to the toy example tutorial, mostly minor things to make the wording more concise. Let me know if there is anything you disagree with. Will have a look at the other tutorials next.

It also needs to be decided how to integrate these examples together with the "quickstart tutorial", which has significant overlap. Maybe, e.g., the quickstart could be replaced by the toy example, but the flow chart could go in the GNPE example. A simplified flow chart could also be used for the two NPE examples.

This should also be addressed at some point, but I understand if there isn't enough time now.


chore(main): release 0.17.0

:robot: I have created a release beep boop
0.17.0 (2024-03-09)
Features

Updates supported resource types (1) (#528) (b4fa4eb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/udondan/cfn-teleport/releases/tag/v0.17.0 :sunflower:


feat: clearable prop

i added a jest test for it, do you want a cypress test too?

ah sure. completely missed the min value ;)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Files with Coverage Reduction
New Missed Lines
%

dist/vue-next-select.es.js
81
56.65%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
324

Relevant Lines:
520

💛  - Coveralls


Spanish translation for Build a Website to Showcase your Resume

This issue is for the short workshop on Build a Website to Showcase your Resume
being translated into Spanish
The structure of the translation should follow other translations like https://github.com/microsoft/workshop-library/tree/main/full/intro-nlp-tensorflow/translations

@Alfonso-AmayaC gracias por tu ayuda con este issue :D

I'm closing this issue in particular because there is already an existing translation of this workshop in spanish


Fix Nintendo buttons in the @GlobalScope documentation

These were mistakenly referred to as DualShock buttons.

Thanks!

Cherry-picked for 3.1.2.


Autogenereted Ids for Cameras

In this branch, the way camera IDs are generated has been changed.
Now the ID field is no longer required. If it is passed, the endpoint will save it as usual. However, if not, the endpoint will look up all other numeric ID and assign the corresponding ID to the new camera.

I wonder what we should do with previously used IDs. With this implementation if I remove camera 0 and then add another camera it will get the same ID, inheriting all the files from the previous camera 0. I guess the most correct thing would be to remove the camera's folder when it is deleted, which I think we aren't doing now. But we would loose all its info as well. Maybe the ID could be derived from the URL so that if a camera is removed and re-added we could potentially "recover" the old stats. But this supposes that camera URLs don't change

Yes, I agree with you about the risk of "move data" between cameras when you delete/add cameras. However, I am not sure if we should fix it in the context of this PR or we can create a new one.

I wonder what we should do with previously used IDs. With this implementation if I remove camera 0 and then add another camera it will get the same ID, inheriting all the files from the previous camera 0. I guess the most correct thing would be to remove the camera's folder when it is deleted, which I think we aren't doing now. But we would loose all its info as well. Maybe the ID could be derived from the URL so that if a camera is removed and re-added we could potentially "recover" the old stats. But this supposes that camera URLs don't change

Yes, I agree with you about the risk of "move data" between cameras when you delete/add cameras. However, I am not sure if we should fix it in the context of this PR or we can create a new one.

I wonder what we should do with previously used IDs. With this implementation if I remove camera 0 and then add another camera it will get the same ID, inheriting all the files from the previous camera 0. I guess the most correct thing would be to remove the camera's folder when it is deleted, which I think we aren't doing now. But we would loose all its info as well. Maybe the ID could be derived from the URL so that if a camera is removed and re-added we could potentially "recover" the old stats. But this supposes that camera URLs don't change

Yes, I agree with you about the risk of "move data" between cameras when you delete/add cameras. However, I am not sure if we should fix it in the context of this PR or we can create a new one.

We should add a ticket for it then

I wonder what we should do with previously used IDs. With this implementation if I remove camera 0 and then add another camera it will get the same ID, inheriting all the files from the previous camera 0. I guess the most correct thing would be to remove the camera's folder when it is deleted, which I think we aren't doing now. But we would loose all its info as well. Maybe the ID could be derived from the URL so that if a camera is removed and re-added we could potentially "recover" the old stats. But this supposes that camera URLs don't change

Yes, I agree with you about the risk of "move data" between cameras when you delete/add cameras. However, I am not sure if we should fix it in the context of this PR or we can create a new one.

We should add a ticket for it then


Tried to synchronously call function {_definedProperty} from a different thread

When I run example component Skeleton, i had bug crash app.
I don't use Expo

Version:
-"@motify/skeleton": "^0.8.1"
-"expo-linear-gradient": "^9.0.0"
-"moti": "^0.8.1"
-"react-native-reanimated": "^2.1.0"
-"react-native-unimodules": "^0.12.0"
My Code:
`import React, { useReducer } from "react";
import { StyleSheet, Pressable } from "react-native";
import { View } from "moti";
import { Skeleton } from "@motify/skeleton";

const Spacer = ({ height = 16 }) => <View style={{ height }} />;
const transition = {
opacity: {
duration: 300,
},
};
export default function HelloWorld() {
const [dark, toggle] = useReducer((s) => !s, true);
const colorMode = dark ? "dark" : "light";
return (

<View
transition={{
type: "timing",
}}
style={[styles.container, styles.padded]}
animate={{ backgroundColor: dark ? "#000000" : "#ffffff" }}
>

<Skeleton
transition={transition}
colorMode={colorMode}
width={"100%"}
/>

<Skeleton
transition={transition}
colorMode={colorMode}
width={"100%"}
/>

);
}
const styles = StyleSheet.create({
shape: {
justifyContent: "center",
height: 250,
width: 250,
borderRadius: 25,
marginRight: 10,
backgroundColor: "white",
},
container: {
flex: 1,
justifyContent: "center",
},
padded: {
padding: 16,
},
});`

Which Reanimated version are you using?

I have an idea for what is causing this. I'll look into it and get back to you shortly.
Thanks for the issue!

I just stepped through Moti 8.1 to 7.1, all of which seem to have the same issue. Moti 0.6 does not have the issue.

Good to know, thanks for the heads up. I think it's related to AnimatePresence. Hopefully will be a quick fix.

I believe 0.7.2 is the cause. Could you try 0.7.1 and 0.7.2 to compare? Make sure you save exact versions to be sure.

Apologies, I don't think I was clear, when I said 0.8.1 to 0.7.1 I meant inclusively. I just tested 0.7.0, and I have the same issue.

Ah got it.

Could you try 0.7.0 but make sure to fully delete node modules and clear the cache with expo start -c if you're using Expo? I have a feeling this one should solve it. I'm not at my computer for now but I'm reading through the commits.

0.6.5 is the latest version I can run without encountering that exact issue on app launch.

Appreciate all the testing.
It's a bit odd because the release for 0.7.0 only includes a new hook. It doesn't seem to touch the files in question (skeleton included).
Are you using the same code as the original poster, or is yours not the skeleton?

I'm not using the same code as the original poster, I'm using Moti in an app I'm working on. Unfortunately after adding 0.7.0 and then running:
rm -rf ./node_modules
yarn
yarn start --reset-cache

I'm getting the same exact error.

Got it. Are you using Expo? I have no issues running the latest on my Expo SDK 41 app.
Also which Reanimated are you using? I'm on 2.0.0, maybe that could be it?
Are you using a skeleton or AnimatePresence?

I'm using AnimatePresence and expo in the bareworkflow.
"expo": "^40.0.1",
"react-native-reanimated": "2.1.0",

Good to know. Could you try 2.0.0? Reanimated has an aggressive cache FYI, so you'll need to expo start -c

Also, if you remote the exit prop from your components, does it solve it? I know it might be annoying to try that if you use exit in many places, so if you do, don't worry about it.

I try use react native reanimated version 2.0.0 with moti version 0.8.1 in
bare react native project, but it still. Hope you can fix it soon. Thank
you.
Vào Th 6, 2 thg 4, 2021 lúc 20:19 Fernando Rojo @.***>
đã viết:

Good to know. Could you try 2.0.0? Reanimated has an aggressive cache FYI,
so you'll need to expo start -c
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nandorojo/moti/issues/48#issuecomment-812525822, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGTYDQGO7S5B2DCBQIKHFY3TGW76TANCNFSM42ISQYMA
.

I can give it a shot. It's not a managed Expo app, I'm just using Expo unimodules and some select libraries.

I remote the exit prop from MotiView, it work. However, i use Skeleton
component. It dont work.
Vào Th 6, 2 thg 4, 2021 lúc 20:22 Fernando Rojo @.***>
đã viết:

Also, if you remote the exit prop from your components, does it solve it?
I know it might be annoying to try that if you use exit in many places, so
if you do, don't worry about it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nandorojo/moti/issues/48#issuecomment-812526718, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGTYDQDI2ALP3UCYA5KRG4TTGXAILANCNFSM42ISQYMA
.

Moti 7.0.0 and Reanimated 2.0.0 still has the issue. I'll try to remove the Exit props next.

Removing exit props from my Moti Views does in fact remove the error when using Moti 7.0.0 and Reanimated 2.0.0

That's good news. I should be able to fix this today then. Thanks for your patience here.

Does it also remove the error on the latest version if you remove exit?

Just released 0.8.2, which solves this on my end.
yarn add moti
Could you confirm that this fixes it?

moti 0.8.2 fixes it for me. Thank you for the speedy fix.

Awesome. Thanks for the testing.
The problem was that Reanimated didn't allow me to reduce an object using Object.keys. I changed it to a .forEach and that fixed it.


download_strategy: fix handling of Apache projects moved to Attic

Sounds like this bug has been going on for a while unreported.
https://github.com/Homebrew/homebrew-core/pull/178118

https://github.com/Homebrew/homebrew-core/pull/178118


'Unknown Error'

Hey, been using this lib for a few months now, and its started giving a random error that just says 'unknown error' here's the stack trace. Please let me know what you think
Next ErrorException: [0] Unknown error (View: /var/www/oblivion-networks.com/resources/views/layouts/main.blade.php) (View: /var/www/oblivion-networks.com/resources/views/layouts/main.blade.php) in /var/www/oblivion-networks.com/vendor/thujohn/twitter/src/Thujohn/Twitter/Twitter.php:297
Stack trace:
#0 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/View/Engines/PhpEngine.php(44): Illuminate\View\Engines\CompilerEngine->handleViewException(Object(ErrorException), 0)
#1 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/View/Engines/CompilerEngine.php(59): Illuminate\View\Engines\PhpEngine->evaluatePath('/var/www/oblivi...', Array)
#2 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/View/View.php(149): Illuminate\View\Engines\CompilerEngine->get('/var/www/oblivi...', Array)
#3 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/View/View.php(120): Illuminate\View\View->getContents()
#4 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/View/View.php(85): Illuminate\View\View->renderContents()
#5 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Http/Response.php(45): Illuminate\View\View->render()
#6 /var/www/oblivion-networks.com/vendor/symfony/http-foundation/Response.php(201): Illuminate\Http\Response->setContent(Object(Illuminate\View\View))
#7 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Router.php(1028): Symfony\Component\HttpFoundation\Response->__construct(Object(Illuminate\View\View))
#8 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Router.php(653): Illuminate\Routing\Router->prepareResponse(Object(Illuminate\Http\Request), Object(Illuminate\View\View))
#9 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Routing\Router->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#10 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php(41): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#11 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(137): Illuminate\Routing\Middleware\SubstituteBindings->handle(Object(Illuminate\Http\Request), Object(Closure))
#12 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(33): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#13 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php(65): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#14 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(137): Illuminate\Foundation\Http\Middleware\VerifyCsrfToken->handle(Object(Illuminate\Http\Request), Object(Closure))
#15 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(33): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#16 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php(49): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#17 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(137): Illuminate\View\Middleware\ShareErrorsFromSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#18 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(33): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#19 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(64): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#20 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(137): Illuminate\Session\Middleware\StartSession->handle(Object(Illuminate\Http\Request), Object(Closure))
#21 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(33): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#22 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php(37): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#23 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(137): Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse->handle(Object(Illuminate\Http\Request), Object(Closure))
#24 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(33): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#25 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php(59): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#26 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(137): Illuminate\Cookie\Middleware\EncryptCookies->handle(Object(Illuminate\Http\Request), Object(Closure))
#27 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(33): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#28 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(104): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#29 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Router.php(655): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#30 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Router.php(629): Illuminate\Routing\Router->runRouteWithinStack(Object(Illuminate\Routing\Route), Object(Illuminate\Http\Request))
#31 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Router.php(607): Illuminate\Routing\Router->dispatchToRoute(Object(Illuminate\Http\Request))
#32 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(268): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#33 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Foundation\Http\Kernel->Illuminate\Foundation\Http\{closure}(Object(Illuminate\Http\Request))
#34 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(46): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#35 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(137): Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle(Object(Illuminate\Http\Request), Object(Closure))
#36 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(33): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}(Object(Illuminate\Http\Request))
#37 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(104): Illuminate\Routing\Pipeline->Illuminate\Routing\{closure}(Object(Illuminate\Http\Request))
#38 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(150): Illuminate\Pipeline\Pipeline->then(Object(Closure))
#39 /var/www/oblivion-networks.com/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(117): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter(Object(Illuminate\Http\Request))
#40 /var/www/oblivion-networks.com/public/index.php(53): Illuminate\Foundation\Http\Kernel->handle(Object(Illuminate\Http\Request))
#41 {main}

Hi.
What do you have here ? /vendor/thujohn/twitter/src/Thujohn/Twitter/Twitter.php:297

That's your file. Its just throwing a generic exception with 'Unknown' as the message.

Yes but the line depends on the version ;)

My mistake, its just the line throwing the generic exception. specifically looks like
...
else
			{
				$error_code = $response['code'];
				$error_msg  = ($error_code == 503) ? 'Service Unavailable' : 'Unknown error';
			}

			$this->log('ERROR_CODE : '.$error_code);
			$this->log('ERROR_MSG : '.$error_msg);

			throw new Exception('['.$error_code.'] '.$error_msg, $response['code']);

When does this happen?
Which method do you call when this happen?
Can you provide me some code?

I dont have a lot of details on when its happening, it was a bug ticket logged by the client who's website is using it. It just says intermittent. I am caching the feed, maybe thats why its intermittent. I am calling it in a view composer
 /**
     * Fetch the latest tweets for the footer
     *
     * @return mixed
     */
    private function getTweets()
    {
        $username = env('TWITTER_USERNAME');
        $number = env('FOOTER_TWITTER_COUNT');

        $tweets = \Cache::get('tweets');

        if ($tweets)
            return $tweets;

        $tweets = Twitter::getUserTimeline(['screen_name' => $username, 'count' => $number, 'format' => 'object']);

        foreach ($tweets as $i => $tweet) {
            $tweets[$i]->text_entitled = $this->addTweetEntityLinks($tweets[$i]);

            $date = date_parse($tweet->created_at);

            if ($date['year'] == date('Y')) {
                $date = date('j F', strtotime($tweet->created_at));
            } else {
                $date = date('j F Y', strtotime($tweet->created_at));
            }
            $tweets[$i]->date_formatted = $date;
        }

        \Cache::put('tweets', $tweets, env('TWITTER_CACHE_LIFETIME'));

        return $tweets;
    }

You should try to catch the exception.
When error will happen again you can save the logs in a file or whatever you want.
 try
 {
     $tweets = Twitter::getUserTimeline(['screen_name' => $username, 'count' => $number, 'format' => 'object']);
 }
 catch (\Exception $e)
 {
     dd(Twitter::logs());
 }

I'd like to know what is causing the error, and 'unknown' doesnt really help me out much?

I never encountered this error so I can't help you.
Save the logs and you will know more.

as follow your direction @thujohn
and i get "ERROR_MSG : Failed connect to api.twitter.com:443; Operation now in progress"
how to fix it :(

    0 => "
    METHOD : POST"
    1 => "
    QUERY : statuses/update"
    2 => "
    URL : https://api.twitter.com/1.1/statuses/update.json"
    3 => "
    PARAMETERS : status=Laravel+is+beautiful&format=json"
    4 => "
    MULTIPART : false"
    5 => "
    FORMAT : json"
    6 => "
    ERROR_CODE : 7"
    7 => "
    ERROR_MSG : Failed connect to api.twitter.com:443; Operation now in progress"
    8 => "
    ERROR_CODE : 0"
    9 => "
    ERROR_MSG : Unknown error"
</samp>]

Hello bro did you solve this problem ? or not ?

nah he didnt do anything about it

i just try/catch

for me it work great on Localhost , but when i upload Laravel appilication on shared Hosting the show me that error

Hello Guys,
i solve this problem , any one facing this problem just change your web hosting , because it being banned from Twiteer ,  i had tested in a free Hosting from Hostinger , when i try in twiiter to add new application with the free hosting domain , they tell me that website is banned , so now when i had used a paied Hosting from Nextwab , it work fine

Started to see this error in the logs today several times.
@MarouaneSH that is not a fix at all. Might have worked for you, because that's one simple reason, why you weren't able to connect to the API.
I'm not using shared hosting, it's a dedicated IP and I'm not banned, because it works fine most of the time. I just see a very few users on my site who receive this error trying to query the API after around 10-11 seconds (information on this comes from the logs and analytics actually, that's why I can even see which Twitter users are trying to be queried -> there are no problems, when I try it with the same users myself).
Ideas:

Something wrong in the well known tmhoauth library.
(Don't think so)
Problem is based on connecting via SSL.
I guess this could be possible. The tmhoauth has a section about SSL and response code 0: https://github.com/themattharris/tmhOAuth#a-note-about-security-and-ssl
The cacert.pem is pretty old, so I wget'ed a new version from haxx.se. Let's see, if the error occours again.
It's just what the error is saying: Can't connect to the Twitter API.
Unlikely but possible in my opinion. In my case - it happens very unfrequent, that would explain it. Idea 1 and 2 would be strange, because of this.

Any other ideas and people interested in solving it?


jicofo

Can You Please Help Me with this issuse
Where I done wrong step.. Please tell me
Other pods working, but readiness of jicofo not working please help withis issuse
Thank You

@vigneshpalaniappan hi, how you solved this problem? Thanks.


Issue loading Neovim plugin using Lazy.nvim

I have the following to try to load bard-cli using Lazy.nvim, but it doesn't seem to be working.
return {
  "mosajjal/bard-cli",
  config = function(plugin)
    --[[ vim.opt.rtp:append(plugin.dir .. "/nvim") ]]
    vim.opt.rtp:append("/home/vendion/.local/share/nvim/lazy/bard-cli/nvim")
  end,
}

Note: the vim.opt.rtp:append() is how Lazy.nvim deals with the rtp.
The problem is it seems this is never getting loaded https://github.com/mosajjal/bard-cli/blob/main/nvim/plugin/bard.lua as Askbard in not recognized as a command in Neovim.

I'm not really familiar with lazy.nvim. in vim-plug, there needs to be another line to setup the environment and add the config env variables. maybe your conf misses that? something like this:
 lua require('bard').setup({bardcli_path="$HOME/go/bin/bard-cli", bardcli_config_path="$HOME/.bardcli.yaml"})

Adding that is didn't do the trick, as the :Askbard command still doesn't get registered in Neovim.
return {
  "mosajjal/bard-cli",
  config = function(plugin)
    --[[ vim.opt.rtp:append(plugin.dir .. "/nvim") ]]
    vim.opt.rtp:append("/home/vendion/.local/share/nvim/lazy/bard-cli/nvim")
    require("bard").setup({ bardcli_path = "$HOME/go/bin/bard-cli", bardcli_config_path = "$HOME/.bardcli.yaml" })
  end,
}

Even if I manually require the bard lua script with :lua require('bard').setup() it still doesn't work.
If I try to call :lua require('bard').ask "write a hello world program in go" directly, I get the following:
E5108: Error executing lua ....local/share/nvim/lazy/bard-cli/nvim/lua/bard/module.lua:5: attemp
t to concatenate local 'question' (a nil value)
stack traceback:
        ....local/share/nvim/lazy/bard-cli/nvim/lua/bard/module.lua:5: in function 'askbard'
        ...endion/.local/share/nvim/lazy/bard-cli/nvim/lua/bard.lua:20: in function 'ask'
        [string ":lua"]:1: in main chunk

Which seems to imply the RTP modification is working at least, since it finds lua/bard/module.lua and lua/bard.lua at least.

Same here. I couldn't find a way to make Lazy use nvim subdir.

hey. Happy to remove the neovim plugin from this repo and provide a link to your plugin repo. we don't even need it as a submodule :) I put it here as a PoC anyway.

is the (neo)vim plugin sitting in a separate repo now? please provide a link so I can remove it from the repo and add the link to the README :)

You can install with Lazy.nvim from path he provided (deepskyblue86/bard-nvim) which maps to this GitHub repository.

sweet. can you guys edit/write the vim part of the README.md with this so I can update and close this off. thanks


fixed commit #1

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

Project coverage is 0.24%. Comparing base (874688c) to head (7cb653c).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

R/utils.R
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##            main      #4   +/-   ##
=====================================
  Coverage   0.24%   0.24%
=====================================
  Files         12      12
  Lines        407     407
=====================================
  Hits           1       1
  Misses       406     406

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


in_syslog new line delimiter

td-agent version: td-agent 0.12.26
Environment information, e.g. OS: Debian 8 for td-agent, Windows 7 for Python code.
Plugin: in_syslog.rb
Configuration:

<source>
  @type syslog
  port 5140
  bind <IP_ADDRESS>
  tag graylog.syslog.dev
  format json
</source>
<source>
  @type syslog
  port 5142
  bind <IP_ADDRESS>
  tag graylog.syslog.dev
  format json
  protocol_type tcp
</source>

Problem explanation:

I'm using Python's SyslogHandler class from logging.handlers package to send syslog messages to a Fluentd syslog input (https://github.com/fluent/fluentd/blob/master/lib/fluent/plugin/in_syslog.rb), both in TCP and UDP. UDP works fine, but TCP does not work.
The "problem" is that the handler is not ending messages with a new line '\n' character (I realized that using tcpdump). I've temporarily added this to line 855 of handlers.py:
msg = prio + msg + '\n'

And now is working.
I did this, because of this comment in the code:
# syslog family add "\n" to each message and this seems only way to split messages in tcp stream
Coolio::TCPServer.new(@bind, @port, SocketUtil::TcpHandler, log, "\n", callback)

Technically, syslog protocol doesn't use any delimiter, but the message's length. After reading the RFC5424 it seems that there is no such "new line message delimiter":
4.3.1.  Message Length

   The message length is the octet count of the SYSLOG-MSG in the
   SYSLOG-FRAME.  A transport receiver MUST use the message length to delimit a syslog message

Am I right?
Thank you for your time.

Am I right?

Maybe right but fluentd's syslog parser doesn't support RFC5424 spec including structured format.
So this is why in_syslog can't parse your syslog message correctly.
I didn't test but one plugin exists for RFC5424. https://github.com/athenahealth/fluent-plugin-newsyslog

Thanks for the link. They are reusing the same line of code:
# syslog family add "\n" to each message and this seems only way to split messages in tcp stream
Coolio::TCPServer.new(@bind, @port, SocketUtil::TcpHandler, log, "\n", callback)

I've tested it and found the same behavior (tested with Python and PHP scripts; in both cases I had to add a \n at the end of the message). My conf file looks like this:
<source>
  type newsyslog
  port 5142
  bind <IP_ADDRESS>
  tag graylog.syslog.dev
  protocol_type tcp
</source>

Besides, the same statement can be found in RFC3164:

4.1.3 MSG Part of a syslog Packet
The MSG part will fill the remainder of the syslog packet.  This will
usually contain some additional information of the process that
generated the message, and then the text of the message.  There is no
ending delimiter to this part.

What do you think? I really don't have any problem adding that but maybe this is something to fix.

There is no ending delimiter to this part.

Yes. Syslog protocol itself doesn't define delimiter for their payload.
But typical syslog implementation treats the message as a text and it contains \n.
RFC5424 also doesn't define it so handling multiple messages in one TCP connection seems to depend on implementation.
Maybe, we need to check rsyslog or syslog-ng's implementation for better handling.

I've read https://tools.ietf.org/html/rfc6587 and I think that I'm starting to understand it. Apparently, There are two methods to distinguish different messages while using TCP syslog:

Syslog over TCP has been around for a number of years.  Just like
legacy syslog over UDP, different implementations exist.  The older
method of non-transparent-framing has problems.  The newer method of
octet-counting is reliable and has not been seen to cause problems
noted with the non-transparent-framing method.

3.4.1.  Octet Counting
It "prepends" the message length to the syslog frame:
TCP-DATA = *SYSLOG-FRAME
SYSLOG-FRAME = MSG-LEN SP SYSLOG-MSG   ; Octet-counting
                                       ; method
MSG-LEN = NONZERO-DIGIT *DIGIT
NONZERO-DIGIT = %d49-57
SYSLOG-MSG is defined in the syslog protocol [RFC5424] and may
           also be considered to be the payload in [RFC3164]

MSG-LEN is the octet count of the SYSLOG-MSG in the SYSLOG-FRAME.
3.4.2.  Non-Transparent-Framing
A trailer character to separate messages. This is what the plugin assumes:

The non-transparent-framing method inserts a syslog message into a frame and terminates it with a TRAILER character.

TCP-DATA = *SYSLOG-FRAME
SYSLOG-FRAME = SYSLOG-MSG TRAILER  ; non-transparent-framing
                                          ; method
TRAILER = LF / APP-DEFINED
APP-DEFINED = 1*2OCTET
SYSLOG-MSG is defined in the syslog protocol [RFC5424] and may
                  also be considered to be the payload in [RFC3164]

A transport receiver can assume that non-transparent-framing is used
if a syslog frame starts with the ASCII character "<" (%d60).

I think we can close this ticket, but it would be nice to mention it in the documentation.
Thanks again for your time.

Added to docs.fluentd.org.


[regression-test](stream load)Invalid file format check

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Latest firmware...

Afternoon
It looks like the manifest definition on the latest firmware (1.8.35) isn't recognize by your code. Hardly surprising, I think the new firmware was only released sometime last week....hopefully only the ID, bot the manifest structure, has actually changed...

I have updated the manifest list to include this new watch version.
Cheers,
Ryan

Thanks :-)
On Mon, Apr 20, 2015 at 10:16 AM, Ryan Binns<EMAIL_ADDRESS>wrote:

I have updated the manifest list to include this new watch version.
Cheers,
Ryan
—
Reply to this email directly or view it on GitHub
https://github.com/ryanbinns/ttwatch/issues/20#issuecomment-94402791.


can remove xformers dependency?

can remove xformers dependency? since the torch version is lower, e.g. torch=1.12.1

Hi @zimenglan-sysu-512 we are using flash attention via xformers. you can remove xformers dependency if you don't need that.


Publish new version for windows-x86 to crates-io

crash-context current version is v.0.5.1 on crates-io, it's not support 32-bit x86 mode, but I saw your github has the file crash-context/src/windows/ffi/x86.rs already.
Publish new version for i686-pc-windows-msvc please.
Thanks.

https://github.com/EmbarkStudios/crash-handling/releases/tag/crash-context-0.6.0


[BUG] HTTP 500 error

Was working as expected, until pulled new repo image and redeployed container.
Attached log file from the container.
_lubelogger-app-1_logs.txt

ah kk, did you pull the new .env file down? There are fields in there that configures SMTP, I believe to make it work you just have to set IsSSL to true or false if you don't want to set up SMTP

That did the trick thanks!

awesome! I've also updated the .env file so that those values are no longer blank. but I'm gonna pin this issue because I'm sure there will be a lot of people facing this problem when they pull down the latest image.

Gonna close this issue since it's been some time since the update was released and the .env file wasn't formatted properly.


Lost ability to change PAT in latest vscode

Seem like the option to reset PAT is not listing anymore. How do we now reset the PAT?

You need to reset all your settings to reset the PAT


Book rec page: dark mode

[Cite any related issue(s) this pull request addresses. If none, simply state “None”]
Fixes:  #2330
Description
Edited the hover line under the main heading (it was going out of the box)
Editing the UI for dark mode for book rec page issue #2330
Edited the color of the containers to match the navbar
Aligned the buttons and input fields
Added hover styles for the get book buttons

Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes. Make sure to attach before & after screenshots in your PR.]
Checklist:

[x] I have made this change from my own.
[ ] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers and screenshots after making the changes.

Conflicting files
assets/css/BookRecommend.css


Ansible request for /usr/lib/jvm/jdkXX symlink

The current java install on UNIX platforms puts a symlink into /usr/lib/jvm/jdk-XX (except JDK 8 which uses /usr/lib/jvm/jdk8) This issue is proposing changing that to /usr/lib/jvm/jdkXX for two reasons:

It will make the other versions consistent with JDK8
The openjdk build process will, by default, search in /usr/lib/jvm/jdkXX for a suitable boot JDK, so it would make our configurations more standardised and potentially reduce the amount of logic needed in the platform-specific-configuration scripts scripts.
e.g.

configure: Found potential Boot JDK using well-known locations (in /usr/lib/jvm/jdk11)
checking for Boot JDK... /usr/lib/jvm/jdk11
checking Boot JDK version... openjdk version "11.0.18" 2023-01-17 OpenJDK Runtime Environment Temurin-11.0.18+10 (build 11.0.18+10) OpenJDK 64-Bit Server VM Temurin-11.0.18+10 (build 11.0.18+10, mixed mode)

The decision here would need to be based on whether we want to be explicit about the boot JDK used (And we generally do use "one version back" which would be inconsistent with the autodetection) - or let it be autodetected (with the note that configure can still pick up things like /usr/lib/jvm/jdk-11.0.18+10 even without the short version)
This is partially driven by the fact that many of our static docker containers are set up with /usr/lib/jvm/jdk17 as the jenkins agent VM so we should aim to be consistent one way or another.
Given that the autodetection will pick up a full path like /usr/lib/jvm/jdk-11.0.18+10 regardless, I don't think there's a disadvantage to allowing /usr/lib/jvm/jdk11 and would recommend we change what's in the playbooks and build scripts to use that path.

+1 from me

Thanks for the heads up. +1 from me.

@Haroon-Khel I was just thinking about this after our call earlier. I think for now we should retaing both the jdk-XX and jdkXX links. While adding the jdkXX one shouldn't cause a problem for now in cases where the machine will retain the old one, as soon as we put in a PR for the update the platforms using build docker images will all be regenerated with ONLY the new one, and I'd prefer us to be able to do a bit more testing on that before making it live.
For example, this line:
https://github.com/adoptium/temurin-build/blob/25f24f457ae6567049fc7386098324f673458251/build-farm/platform-specific-configurations/linux.sh#L306
looks specifically for the location with the - at the moment (and it can also be overridden by a variable in the jenkins configuration, some of which may have a version with the -.

At the moment I am testing builds with and without the hyphen in the symlink in our build containers. The scripts run fine with and without the hyphen (it detects the correct bootjdk) as long as the appropriate edit is made in linux.sh
Therefore this infra pr needs to be coupled with a build pr which makes the appropriate changes in linux.sh and mac scripts

That's true, but the important thing for us to verify to ensure this change is useful is to ensure that if you're not using those scripts then running ./configure in the openjdk source directory can pick up the JDK automatically, otherwise there's no point in this change :-) I'm just slightly nervous after looking at the code.

Running bash configure on the centos7 and alpine3 biuld images after applying the symlink changes, using the upstream repos https://github.com/openjdk/
Centos7 build image
JDK11u
configure: (Your Boot JDK version must be one of: 10 11)
configure: Found potential Boot JDK using well-known locations (in /usr/lib/jvm/jdk11)
checking for Boot JDK... /usr/lib/jvm/jdk11
checking Boot JDK version... openjdk version "11.0.24" 2024-07-16 OpenJDK Runtime Environment Temurin-11.0.24+8 (build 11.0.24+8) OpenJDK 64-Bit Server VM Temurin-11.0.24+8 (build 11.0.24+8, mixed mode)

JDK21u
configure: (Your Boot JDK version must be one of: 20 21)
configure: Found potential Boot JDK using well-known locations (in /usr/lib/jvm/jdk21)
checking for Boot JDK... /usr/lib/jvm/jdk21
checking Boot JDK version... openjdk version "21.0.4" 2024-07-16 LTS OpenJDK Runtime Environment Temurin-21.0.4+7 (build 21.0.4+7-LTS) OpenJDK 64-Bit Server VM Temurin-21.0.4+7 (build 21.0.4+7-LTS, mixed mode, sharing)

JDK22u
configure: (Your Boot JDK version must be one of: 21 22)
configure: Found potential Boot JDK using well-known locations (in /usr/lib/jvm/jdk21)
checking for Boot JDK... /usr/lib/jvm/jdk21
checking Boot JDK version... openjdk version "21.0.4" 2024-07-16 LTS OpenJDK Runtime Environment Temurin-21.0.4+7 (build 21.0.4+7-LTS) OpenJDK 64-Bit Server VM Temurin-21.0.4+7 (build 21.0.4+7-LTS, mixed mode, sharing)

Alpine3 build image
JDK11u
configure: (Your Boot JDK version must be one of: 10 11)
configure: Found potential Boot JDK using well-known locations (in /usr/lib/jvm/jdk11)
checking for Boot JDK... /usr/lib/jvm/jdk11
checking Boot JDK version... openjdk version "11.0.24" 2024-07-16 OpenJDK Runtime Environment Temurin-11.0.24+8 (build 11.0.24+8) OpenJDK 64-Bit Server VM Temurin-11.0.24+8 (build 11.0.24+8, mixed mode)

JDK17u
configure: (Your Boot JDK version must be one of: 16 17)
configure: Found potential Boot JDK using well-known locations (in /usr/lib/jvm/jdk17)
checking for Boot JDK... /usr/lib/jvm/jdk17
checking Boot JDK version... openjdk version "17.0.12" 2024-07-16 OpenJDK Runtime Environment Temurin-17.0.12+7 (build 17.0.12+7) OpenJDK 64-Bit Server VM Temurin-17.0.12+7 (build 17.0.12+7, mixed mode, sharing)

JDK21u
configure: (Your Boot JDK version must be one of: 20 21)
configure: Found potential Boot JDK using well-known locations (in /usr/lib/jvm/jdk21)
checking for Boot JDK... /usr/lib/jvm/jdk21
checking Boot JDK version... openjdk version "21.0.4" 2024-07-16 LTS OpenJDK Runtime Environment Temurin-21.0.4+7 (build 21.0.4+7-LTS) OpenJDK 64-Bit Server VM Temurin-21.0.4+7 (build 21.0.4+7-LTS, mixed mode, sharing)

Looks like it finds them easy


Black Theme

Pure Black Theme, please.

Unfortunately there are no plans for a completely black theme.


201220085陈程完成了Task180对pkg/utils/kubeclient/secret.go文件的修改

添加了“Copyright 2023 The Fluid Authors.”

@CCisWorking pls fix DCO issue by following https://github.com/fluid-cloudnative/fluid/pull/3188/checks?check_run_id=13087253106

🐶


Hide  new Git "deployment" section?

VSCode Version: Code - Insiders 1.15.0-insider (3cfa565abbd6e162b7ae6f3055c231128da63df2, 2017-07-17T05:07:20.317Z)
OS Version: Darwin x64 16.6.0
Extensions:

Extension
Author (truncated)
Version

ng-template
Ang
0.1.4

vscode-markdownlint
Dav
0.9.1

code-settings-sync
Sha
2.8.2

sort-lines
Tyr
1.3.0

Bookmarks
ale
0.15.2

project-manager
ale
0.18.1

path-intellisense
chr
1.4.2

vscode-eslint
dba
1.2.11

vscode-html-css
ecm
0.1.7

tslint
eg2
0.16.0

auto-rename-tag
for
0.0.14

Angular2
joh
2.4.0

ecdc
mit
0.10.3

HTMLHint
mka
0.3.3

vscode-autoprefixer
mrm
2.0.0

vscode-stylefmt
mrm
2.4.1

angular2-inline
nat
0.0.17

stylelint
shi
0.27.0

ayu
tea
0.4.0

change-case
wma
1.0.0

(4 theme extensions excluded)

Question:  I don't plan on using the Git deployment.  Is there a prefs setting to hide that pane in the UI?

We've removed that section from current insiders.


Add Nong Song: This Side of Paradise (Please)

Song Name
This Side of Paradise
Artist Name
Coyote Theory
Source
Youtube
Youtube Link
https://www.youtube.com/watch?v=sniVezVELSM&t=0s
Direct File Link
No response
Song ID
964876
Start Offset [ms]
0
Extra
Used in the level "Lonely with me" by ImBreadSS

pls

Not stale