Save State Issue

I am using the RG351P with ArkOS v 1.5 (01282021)
so here is the issue, while using the Playstation emulator i can make save states, however there is no way to load them.  ive set up all my hot keys to to save and load the save states. the Save hotkey works, shows the saving bar. scrolls to 100% and gives the check mark. the load hotkey does nothing. then i tried to do manual save states. going into retro arch selecting save, it runs a save, even makes a save state file in my game directory, however the load save state icon is not there.
troubleshooting steps i have taken so far.

going into the file directory and deleting the old save states. no resolution.
taking the SD card and loading it on the my pc to see if there was an error that needed repair via windows. no prompt for repair no obvious issue found.
switched the core to run on the Retro arch 64 version.  it worked briefly but after closing and reopening the rom the same issues with the 32 version have started.

save states seem to have worked normally on each version of retro arch once, then on future boot ups this issue happens.
to help you out. the game i was playing when i came across this issue was Final Fantasy Tactics. also with a secondary Saving issue.
since save states have not been working for me ive been using the in game saves.  during the first 10 hours of game play with the game, i could save in game as normal. and then when i was done playing shut the core down using the Select + Start Start hot key. the saves would be fine. however after a slightly longer play session, about 2 and a half hours, i saved, closed the core using those hot keys and all the saves and progress had been reverted to the state prior to that game session. losing a ton of progress and time.  frustrating but i have at least found a work around for this issue for now.
going into retro arch and closing the content first, then closing retro arch seems to resolve the issue,  an extra step but possibly something else you may want to look into.
sorry for the long post but i wanted to give you as much info on the issue as ive found to help you with troubleshooting this issue.
also. the save state issue is an issue my brother is dealing with as well. he is also on an RG351p. also the same version of ArkOS.
Before submitting your issue or feature request.  DO NOT REQUEST PORTS THROUGH THIS PROCESS.  I will no longer be focusing on adding additional ports at this time.  You may try to post your request here for an alternative unofficial solution.  Do understand support for those ports will not be available on this github.

This is not Anbernic Stock Emuelec or 351Elec.  ArkOS is a different distribution from those systems and will have differing features.  The only somewhat similarity is that they both use EmulationStation as a frontend.  Even with that, the versions of EmulationStation that's used in between ArkOS and Anbernic Emuelec/351Elec is different with different capabilities.  If there are features you prefer with Anbernic Emuelec/351Elec, just use those distributions instead.  The choice is yours.

Have you reviewed the Frequently Asked Questions available at https://github.com/christianhaitian/arkos/wiki/Frequently-Asked-Questions---RG351P ?

If your issue is related to being able to run certain emulators or ports, have you reviewed the Emulators and Ports section available at https://github.com/christianhaitian/arkos/wiki/ArkOS-Emulators-and-Ports-information for needed bios files and supported rom extensions?

Have you reviewed the known issues section available at https://github.com/christianhaitian/arkos/wiki/Known-issues ?

Describe the Issue (If applicable)
A clear and concise description of what the bug is.
How can the issue be reproduced? (If applicable)
What device are you using?
What version of ArkOS are you on?

You can find this during the initial boot process right before the Emulationstation loading screen

Anything else you'd like to include that may help to review this issue or feature request?

This issue is very odd.  First, if the issue is happening between retroarch 64 and 32, then this means it’s happening between 2 different emulator cores as the retroarch 64 PSX emulator is duckstation while on the reteoarch 32 the emulator is pcsx_rearmed.  It’s very strange that the issue happens fairly consistently the same between 2 completely different emulators.  So My thinking is that there’s either an issue both retroarch engines or an issue with your hotkey changes. By default, the image is set to use hotkey+r1 for savestates and hotkey+l1 to load savestates.  You indicated you changed this.  Are you sure you’re not changing your savestate slots by accident between sessions?  Or did you enable Increment Save State Index Automatically in the retroarch menu?  If that’s not the issue, are you experiencing this with any other system emulators?  I tried the following scenarios and can’t replicate this issue yet using Ape Escape
launch ape escape, savestate once started in new game.  Load savestate with no issues using default hotkeys,
Exited retroarch via hotkeys.  Load ape escape again, loadEd savestate without issue using hotkeys.
Shutdown the unit.  Boot the unit.  Launch ape escape, load savestate, no issue.  Saved over previous savestate with no issue.  Loaded new savestate,  no issue.

This issue is very odd.  First, if the issue is happening between retroarch 64 and 32, then this means it’s happening between 2 different emulator cores as the retroarch 64 PSX emulator is duckstation while on the reteoarch 32 the emulator is pcsx_rearmed.  It’s very strange that the issue happens fairly consistently the same between 2 completely different emulators.  So My thinking is that there’s either an issue both retroarch engines or an issue with your hotkey changes. By default, the image is set to use hotkey+r1 for savestates and hotkey+l1 to load savestates.  You indicated you changed this.  Are you sure you’re not changing your savestate slots by accident between sessions?  Or did you enable Increment Save State Index Automatically in the retroarch menu?  If that’s not the issue, are you experiencing this with any other system emulators?  I tried the following scenarios and can’t replicate this issue yet using Ape Escape
launch ape escape, savestate once started in new game.  Load savestate with no issues using default hotkeys,
Exited retroarch via hotkeys.  Load ape escape again, loadEd savestate without issue using hotkeys.
Shutdown the unit.  Boot the unit.  Launch ape escape, load savestate, no issue.  Saved over previous savestate with no issue.  Loaded new savestate,  no issue.

I’ll do some more testing and I’ll even take a video to show you what’s going on if that helps.  Also, those are the same hot keys I use for save state and load state. Didn’t realize that’s what they were already set to.   Would you like video of the issue so that you can see what’s going on?
On Jan 30, 2021, at 5:43 AM, christianhaitian<EMAIL_ADDRESS>wrote:

This issue is very odd. First, if the issue is happening between retroarch 64 and 32, then this means it’s happening between 2 different emulator cores as the retroarch 64 PSX emulator is duckstation while on the reteoarch 32 the emulator is pcsx_rearmed. It’s very strange that the issue happens fairly consistently the same between 2 completely different emulators. So My thinking is that there’s either an issue both retroarch engines or an issue with your hotkey changes. By default, the image is set to use hotkey+r1 for savestates and hotkey+l1 to load savestates. You indicated you changed this. Are you sure you’re not changing your savestate slots by accident between sessions? Or did you enable Increment Save State Index Automatically in the retroarch menu? If that’s not the issue, are you experiencing this with any other system emulators? I tried the following scenarios and can’t replicate this issue yet using Ape Escape
launch ape escape, savestate once started in new game. Load savestate with no issues using default hotkeys,
Exited retroarch via hotkeys. Load ape escape again, loadEd savestate without issue using hotkeys.
Shutdown the unit. Boot the unit. Launch ape escape, load savestate, no issue. Saved over previous savestate with no issue. Loaded new savestate, no issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/christianhaitian/arkos/issues/224#issuecomment-770192142, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASVAYWOBC5DLQGJ6T5CANMTS4PPGTANCNFSM4W2DOK3Q.

I’ll do some more testing and I’ll even take a video to show you what’s going on if that helps.  Also, those are the same hot keys I use for save state and load state. Didn’t realize that’s what they were already set to.   Would you like video of the issue so that you can see what’s going on?
On Jan 30, 2021, at 5:43 AM, christianhaitian<EMAIL_ADDRESS>wrote:

This issue is very odd. First, if the issue is happening between retroarch 64 and 32, then this means it’s happening between 2 different emulator cores as the retroarch 64 PSX emulator is duckstation while on the reteoarch 32 the emulator is pcsx_rearmed. It’s very strange that the issue happens fairly consistently the same between 2 completely different emulators. So My thinking is that there’s either an issue both retroarch engines or an issue with your hotkey changes. By default, the image is set to use hotkey+r1 for savestates and hotkey+l1 to load savestates. You indicated you changed this. Are you sure you’re not changing your savestate slots by accident between sessions? Or did you enable Increment Save State Index Automatically in the retroarch menu? If that’s not the issue, are you experiencing this with any other system emulators? I tried the following scenarios and can’t replicate this issue yet using Ape Escape
launch ape escape, savestate once started in new game. Load savestate with no issues using default hotkeys,
Exited retroarch via hotkeys. Load ape escape again, loadEd savestate without issue using hotkeys.
Shutdown the unit. Boot the unit. Launch ape escape, load savestate, no issue. Saved over previous savestate with no issue. Loaded new savestate, no issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/christianhaitian/arkos/issues/224#issuecomment-770192142, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASVAYWOBC5DLQGJ6T5CANMTS4PPGTANCNFSM4W2DOK3Q.

How about you grab another sd card, and image arkos onto it, update it, then load your game on it, then try that without making any hotkey changes there and see what happens.

How about you grab another sd card, and image arkos onto it, update it, then load your game on it, then try that without making any hotkey changes there and see what happens.

Sounds good. I’ll give that a shot and see what happens.
On Jan 30, 2021, at 8:45 AM, christianhaitian<EMAIL_ADDRESS>wrote:

How about you grab another sd card, and image arkos onto it, update it, then load your game on it, then try that without making any hotkey changes there and see what happens.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/christianhaitian/arkos/issues/224#issuecomment-770214867, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASVAYWJMGZV2VV35XNJWYEDS4QEPLANCNFSM4W2DOK3Q.

Sounds good. I’ll give that a shot and see what happens.
On Jan 30, 2021, at 8:45 AM, christianhaitian<EMAIL_ADDRESS>wrote:

How about you grab another sd card, and image arkos onto it, update it, then load your game on it, then try that without making any hotkey changes there and see what happens.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/christianhaitian/arkos/issues/224#issuecomment-770214867, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASVAYWJMGZV2VV35XNJWYEDS4QEPLANCNFSM4W2DOK3Q.

okay, so i flashed a new SD card. and everything is working as it should.  however i took a look at my other SD card (the one with the issue)  i dont think changing the hotkeys, or really remapping them to the same buttons as before is the issue,  when you go into the retro arch menu while the game is running the Load State option is missing. its there on the fresh flash of the OS.
so what im going to do is move all my games and saves off the old sd card and re flash it with a fresh install and go from there.  if the problem comes up again ill be sure to reach out to you again if i can replicate the issue.
thank you for your time. and keep up the good work on this OS.  its awesome!

From: christianhaitian<EMAIL_ADDRESS>Sent: Saturday, January 30, 2021 8:45 AM
To: christianhaitian/arkos<EMAIL_ADDRESS>Cc: ZillaTBO<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [christianhaitian/arkos] Save State Issue (#224)
How about you grab another sd card, and image arkos onto it, update it, then load your game on it, then try that without making any hotkey changes there and see what happens.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/christianhaitian/arkos/issues/224#issuecomment-770214867, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASVAYWJMGZV2VV35XNJWYEDS4QEPLANCNFSM4W2DOK3Q.

okay, so i flashed a new SD card. and everything is working as it should.  however i took a look at my other SD card (the one with the issue)  i dont think changing the hotkeys, or really remapping them to the same buttons as before is the issue,  when you go into the retro arch menu while the game is running the Load State option is missing. its there on the fresh flash of the OS.
so what im going to do is move all my games and saves off the old sd card and re flash it with a fresh install and go from there.  if the problem comes up again ill be sure to reach out to you again if i can replicate the issue.
thank you for your time. and keep up the good work on this OS.  its awesome!

From: christianhaitian<EMAIL_ADDRESS>Sent: Saturday, January 30, 2021 8:45 AM
To: christianhaitian/arkos<EMAIL_ADDRESS>Cc: ZillaTBO<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [christianhaitian/arkos] Save State Issue (#224)
How about you grab another sd card, and image arkos onto it, update it, then load your game on it, then try that without making any hotkey changes there and see what happens.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/christianhaitian/arkos/issues/224#issuecomment-770214867, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASVAYWJMGZV2VV35XNJWYEDS4QEPLANCNFSM4W2DOK3Q.


Train Code

Will training code be made available ?

when will the training code be released? thx

Sorry for the inconvenience. I originally planned to release the training code by last year but got stuck due to various conferences and vacations. I will try to figure it out in one or two months.

I would like to know when will the training code be released? thank you.


Timeline for std::filesystem support (IDFGH-2970)

Do you plan to support std::filesystem? (-> #2449)
Is it possible to build xtensa-esp32-elf-g++ with different flags to support it?

@xuio We do plan to enable std::filesystem support once we upgrade to a GCC version where it is fully supported (It is considered experimental in GCC 8).
For now you can try building the toolchain yourself, adding --enable-libstdcxx-filesystem-ts to the list of GCC configuration flags (CT_CC_GCC_EXTRA_CONFIG_ARRAY option in crosstool-NG). If you meet issues along the way, please let us know.
Regarding support for C++17 / C++20 in IDF, see also the discussion in https://github.com/espressif/esp-idf/pull/4846.

I tried adding the option while building the toolchain, but there is no library created in the corresponding folder.
Apart from std::filesystem, is it possible to build libatomic for xtensa? I am trying to build protobuf c++ and eventually gRPC, but it needs 64bit atomics. (it fails to find __atomic_fetch_add_8 during linking)

Thanks for the feedback, will look into std::filesystem support while preparing for the next toolchain release.
Regarding __atomic_fetch_add_8, please subscribe to https://github.com/espressif/esp-idf/issues/3163 — it will get updated and closed automatically when we implement this.

any roadmap for filesystem?

It looks like ESP-IDF v3.3 uses  GCC v8.4, shouldn't std::filesystem be implemented there?
Why does it not work?

@chipweinberger

The filesystem library facilities may be unavailable if a hierarchical file system is not accessible to the implementation, ...

https://en.cppreference.com/w/cpp/filesystem

Has there been any further consideration given to this?
I have found most std::filesystem functions actually work quite well, except for some unusual cases in path concatenation, and std::filesystem::directory_iterator does not work at all.
It appears this may be because _GLIBCXX_HAVE_DIRENT_H is not defined, even though we do have dirent.hin newlib/platform_include. Is this something that needs to be added to https://github.com/espressif/gcc/blob/esp-12_2_0/libstdc++-v3/config/os/newlib/os_defines.h ?

@nebkat We will take a look to see if we can just add the correct definition.

Should work after commit https://github.com/espressif/esp-idf/commit/994b4ed459269be1f6548137eac84ec3f9a8e37f
Please open another issue if something wrong is found


kubernetes manifest error

I believe the selector is obsolete, as I get this error:
error validating data: found invalid field selector for v1.PodSpec; if you choose to ignore these errors, turn validation off with --validate=false

But if I remove it, the DaemonSet starts without errors, but I see nothing coming in...

Which Kubernetes version do you use?
Did you enter SPM App Token and Logsene Token?

This issue might be relevant: https://github.com/kubernetes/kubernetes/issues/18130
https://github.com/kubernetes/kubernetes/issues/18130#issuecomment-163022690
Please note the apiVersion changed for 1.2 see comments in my DaemonSet definition:
# Kubernetes 1.1.8
apiVersion: extensions/v1beta1
# Kubernetes 1.2
# apiVersion: v1
kind: DaemonSet
metadata:
  name: sematext-agent
spec:
  template:
    metadata:
      labels:
        app: sematext-agent
    spec:
      selector: {}
      dnsPolicy: "ClusterFirst"
      restartPolicy: "Always"
      containers:
      - name: sematext-agent
        image: sematext/sematext-agent-docker:latest
        imagePullPolicy: "Always"
        env:
        - name: SPM_TOKEN
          value: "REPLACE THIS WITH YOUR SPM TOKEN"
        - name: LOGSENE_TOKEN
          value: "REPLACE THIS WITH YOUR LOGSENE TOKEN"
        - name: KUBERNETES
          value: "1"
        volumeMounts:
          - mountPath: /var/run/docker.sock
            name: docker-sock
          - mountPath: /etc/localtime
            name: localtime
      volumes:
        - name: docker-sock
          hostPath:
            path: /var/run/docker.sock
        - name: localtime
          hostPath:
            path: /etc/localtime
```

Create the daemonset with ```kubectl create -f sematext-agent.yml --validate=false```
This worked at least with Kubernetes 1.1.8.

I just migrated to 1.2.0 final and get this error:
no kind "DaemonSet" is registered for version "v1"

If I move back to extensions/v1beta1 it's fine...tnx

However, before I got logs...now I just get metrics ;(

maybe you are missing the udp port part

nevermind, had to use the live streaming feature, as pressing refresh button does NOT do what it promises...it just gets what is cached in NON live mode, which is stale data...live data is running fine

@Morriz are you referring to the little refresh icon at the top of the Logsene UI?  The one with 2 arrows?  That one just reloads whatever query / date range / filters you've used.  Clicking on one of the little "time-shortcut" icons left of that will show you the last X interval (last 10 min, last 30 min, or whatever you clicked on).  The "play" icon to the right of the refresh/reload icon is for "live tail" - https://www.youtube.com/watch?v=SNzEE1weVUg

Log parameters for Logsene
Please note logs are buffered for bulk indexing (up to 1000 records or 30 seconds timeout).

You could modify the relevant parameters via environment variables:
LOGSENE_LOG_INTERVAL=10000  (for 10 seconds, pls, don't get below that value it might result in http errors if our receiver starts to blog denial of service attacks ...)
LOGSENE_BULK_SIZE=500 (default is 1000 records)

Kubernetes DaemonSet
Pleas check if the DaemonSet is enabled:
For 1.1.8 it was this startup parameter for the apiserver:

--runtime-config=extensions/v1beta1/daemonsets=true

It looks Kubernetes had problems to get DaemonSets on 1.2 and they reverted a merge. Depending on the 1.2 (beta!) version you use the apiVersion might still be apiVersion: extensions/v1beta1
See here: https://github.com/kubernetes/kubernetes/commit/9a95e555ea8bfbee15fb5b830ff1884f6f0b6669#diff-4cb7085a8e1d9b8448ea3402e586181e
and here: https://github.com/kubernetes/kubernetes/issues/15310
I think the best place to ask is the Kubernetes repository, or wait until 1.2 is final (including proper documentation, as far I know in 1.2 DaemonSets should be enabled by default and apiVersion will be v1).
Please note there are alternatives if you use CoreOS Sematext Agent could be deployed via fleet:

https://github.com/sematext/sematext-agent-docker/tree/master/coreos
if you run a test env with a few nodes only you might simply start the agent on each node using "docker run".

Kubernetes is a fast moving project, and as soon v1.2 (final) is released, we will provide the updated instructions.

I have it working already, tnx. I have a bug to report tho about log output being shown differently in the sematext viewer (the kibana 4 viewer shows it ok): html chars escaped wrongly.
Where do you want me to report that?

On 18 mrt. 2016, at 09:49, Stefan Thies<EMAIL_ADDRESS>wrote:
Log parameters for Logsene
Please note logs are buffered for bulk indexing (up to 1000 records or 30 seconds timeout).

You could modify the relevant parameters via environment variables:
LOGSENE_LOG_INTERVAL=10000 (for 10 seconds, pls, don't get below that value it might result in http errors if our receiver starts to blog denial of service attacks ...)
LOGSENE_BULK_SIZE=500 (default is 1000 records)

Kubernetes DaemonSet
Pleas check if the DaemonSet is enabled:
For 1.1.8 it was this startup parameter for the apiserver:
--runtime-config=extensions/v1beta1/daemonsets=true
It looks Kubernetes had problems to get DaemonSets on 1.2 and they reverted a merge. Depending on the 1.2 (beta!) version you use the apiVersion might still be apiVersion: extensions/v1beta1
See here: kubernetes/kubernetes@9a95e55#diff-4cb7085a8e1d9b8448ea3402e586181e https://github.com/kubernetes/kubernetes/commit/9a95e555ea8bfbee15fb5b830ff1884f6f0b6669#diff-4cb7085a8e1d9b8448ea3402e586181e
and here: kubernetes/kubernetes#15310 https://github.com/kubernetes/kubernetes/issues/15310
I think the best place to ask is the Kubernetes repository, or wait until 1.2 is final (including proper documentation, as far I know in 1.2 DaemonSets should be enabled by default and apiVersion will be v1).
Please note there are alternatives if you use CoreOS Sematext Agent could be deployed via fleet:
https://github.com/sematext/sematext-agent-docker/tree/master/coreos https://github.com/sematext/sematext-agent-docker/tree/master/coreos
if you run a test env with a few nodes only you might simply start the agent on each node using "docker run".
Kubernetes is a fast moving project, and as soon v1.2 (final) is released, we will provide the updated instructions.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/sematext/sematext-agent-docker/issues/8#issuecomment-198260507

There is a chat window in Logsene UI (bottom right). Please report there.

Or you can email<EMAIL_ADDRESS> A screenshot would be very helpful in understanding this.  Thanks @Morriz!

The Kibana 4 output does not have this problem. Please see the attached screenie...
cheers,
Maurice

Hi Maurice,
Where do you see this?  Is this the main view in Logsene?  I assume it is,
but I don't see the whole UI in the screenshot, so want to make sure.
Thanks,
Otis
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/
tel: +1<PHONE_NUMBER>   fax: +1<PHONE_NUMBER>
On Tue, Mar 22, 2016 at 9:02 AM, Maurice Faber<EMAIL_ADDRESS>wrote:

The Kibana 4 output does not have this problem. Please see the attached
screenie...
cheers,
Maurice

I close this issuse, Sematext Docker Agent is working with Kuberntes 1.2. Escaping special characters in Logsene UI will be treated as Sematext Ticket and the UI fix will be in the next UI update.

A new example is here, working without --validate=false.
https://github.com/sematext/sematext-agent-docker#installation-on-kubernetes
https://github.com/sematext/sematext-agent-docker/blob/master/kubernetes/sematext-agent.yml


If possible, add GS66 to the list.

Works nicely with the MSI GS66. Thanks for making the code.
Regards,
Rob Oudendijk

"stays orange or flashes between orange and white" is import to know if your computer is using the Nvidia or the Intel graphics card. Maybe best not to change that.

Sorry, I actually meant to mention only the backlight color of the ESC key can't be changed with msi-perkeyrgb yet (all other keys can). I'm guessing a small change to the config files for the GS65 profile might be needed to make that work.
You are right about the small extra LED on that key, it should not be touched by any RGB scripts.

+1 gs66 works fine, but important note: need to enable keyboard highlight by FN + F10 before try msi-perkeyrgb

The power button backlight is not customizable and when using FN+F11 4 times, instead of turning off the keyboard backlight, a few keys are red with varying degrees of brightness. Also not an issue but I would like to see FN+F9 (The SteelSeries button) cycle through the color settings, ie; aqua, disco, roulette, etc.

@kayoisdumb if you're talking about the orange/white led in the power button, it is a hardware-level feature and it should reflect the use of cpu (white) or gpu (orange); also, probably it is just a hardcoded white-orange led - not rgb - so probably it can't be customized.

@mixalbl4-127 @robouden Actually, I'm on a GS66 Stealth (idk if it's relevant) and I cannot make it work, with any profile. All I get is the keyboard briefly flashing white. The keyboard lights work perfectly on windows and in grub or bios, but as soon as linux boot sequence starts, it flashes and get black. I'm on Ubuntu 20.04 LTS with kernel 5.11.0-46 , but I also tried different distros and updated kernels..

@FedericoCozziVM We have many duplicate issues regarding gs66 support. If you are still interested, thanks to other users contributions we managed to make some progress with some workarounds at https://github.com/Askannz/msi-perkeyrgb/issues/49
It is not perfect but al least we can enjoy the rgb light also on our pc.

@gturi That's great! thanks for reaching out! I'm testing it and I'll write some considerations at #49 asap


Used wrong api version value during initialization shopifyApp

https://github.com/Shopify/function-examples/blob/8b2ca3d0387a8cd40e32cb0e34246531fa183a2c/sample-apps/delivery-customizations/web/shopify.js#L21
As you can see, in config used value "2023-04", but in same time restResources imported for version 2023-01 (look at line 4).
Also, the app, created with using of this template, can't start properly, because some of dependencies has incompatible version but it's version still matched as compatible. I was able to start the app after reinstalling of all dependencies with npm ci (all dependencies installed wit versions as locked in lock file).

I'm having this issue. If anyone can help please:

I'm having this issue. If anyone can help please:

Hey @niveshsaharan were you able to figure this out? Seems like I'm running into the exact same issue.

@niveshsaharan you are awesome and amazing, thank you for the solution!


Add page break in DG

Codecov Report

Merging #209 (744918a) into master (f99b393) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #209   +/-   ##
=========================================
  Coverage     63.19%   63.19%
  Complexity      658      658
=========================================
  Files           111      111
  Lines          2421     2421
  Branches        271      271
=========================================
  Hits           1530     1530
  Misses          792      792
  Partials         99       99

Impacted Files
Coverage Δ

...n/java/seedu/address/commons/core/GuiSettings.java
69.23% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Export i18n js config

Add :export_i18n_js to config (global) which functions the same as I18n::JS.export_i18n_js_dir_path
Minor change of I18n::JS.export_i18n_js_dir_path so that any non-String is interpreted as "do not export". This should not break existing implementations, and also the README has previously said the only way you can set path is via a String variable.

Please merge PR #299 and #300 first

Here's a diff of master vs. this branch: fnando:master...johnnyshields:export-i18n-js-config

Sorry don't have time to review this today :S

Is there a reason to set it to :none instead of nil when it's not a string?
Just asking

Because nil evaluates as false (unset) when using the ||= operator. By using the symbol :none it means the user has explicitly said "I do not want to export this file" somewhere along the chain. This was the easiest way to preserve the existing behavior of this function.


RegressionResult is defined twice

Trait Regression is defined here and here.
Is there any specific reason for that? From time to time I get a compilation error from that, although sometimes it doesn't seem to matter...

dunno. feel free to clean it out.
On Wed, Jun 24, 2015 at 7:30 AM, Martin Mauch<EMAIL_ADDRESS>wrote:

Trait Regression is defined here
https://github.com/scalanlp/breeze/blob/149b3655977eb9dea38b53a18b83d0a4e0e08d41/math/src/main/scala/breeze/stats/regression/RegressionResult.scala
and here
https://github.com/scalanlp/breeze/blob/149b3655977eb9dea38b53a18b83d0a4e0e08d41/math/src/main/scala/breeze/stats/regression/package.scala
.
Is there any specific reason for that? From time to time I get a
compilation error from that, although sometimes it doesn't seem to matter...
—
Reply to this email directly or view it on GitHub
https://github.com/scalanlp/breeze/issues/416.

apparently tihs was fixed.


[BUG] Error not deserializable for invalid alias in alias request

What is the bug?
When executing an alias request with a non-existing alias (GET /_alias/alias1) the error response cannot be deserialized as a JSON object is expected, but the response contains only a string for the error field.
An UnexpectedJsonEventException is thrown:
org.opensearch.client.json.UnexpectedJsonEventException: Unexpected JSON event 'VALUE_STRING' instead of '[START_OBJECT, KEY_NAME]' because the response looks like this:
{
  "error" : "alias [nonExistingAlias] missing",
  "status" : 404
}

How can one reproduce the bug?
Request indices for a non-existing alias:
openSearch.indices().getAlias { request -> request.name("nonExistingAlias") }
What is the expected behaviour?
The error response will be deserialized correctly.
What is your host/environment?
AWS OpenSearch 1.2
Do you have any additional context?
I'm not quite sure who's at fault here since the error response is very inconsistent.
When doing it the other way around by requesting the aliases for an index (GET /index-1/_alias) the error message looks correct with the error being a JSON object containing the root cause, which the deserializer also expects in this case.

Hello @patschl,
this issue is a duplicate of: https://github.com/opensearch-project/opensearch-java/issues/301
Please try the latest SNAPSHOT release:
https://github.com/opensearch-project/opensearch-java/issues/301#issuecomment-1544428908

Sorry, my bad!
Thank you very much.


Add KV cache option for inference

Probably need to review #9 first (just refactoring stuff)
Fix #1

The code looks good to me and I've run it locally on my machine. @rchan26 suggested he take us through the implementation in next week's Karpathy session.


HAI-2595 Show notification if kaivuilmoitus work area overlaps with johtoselvitys work areas

Description
Show notification if kaivuilmoitus work area overlaps with johtoselvitys work areas. If there is only one overlapping johtoselvitys, show a link for it. Otherwise, show a general notification.
Jira Issue: https://helsinkisolutionoffice.atlassian.net/browse/HAI-2595
Type of change

[ ] Bug fix
[x] New feature
[ ] Other

Instructions for testing

Create some johtoselvitys (2 at least) and send them to Allu. Johtoselvitys application should have at least one work area that overlap with work area in another johtoselvitys in order to be able to create a kaivuilmoitus work area that also overlaps.
Create a kaivuilmoitus for the same hanke and add those johtoselvitys to it on the 1st page. Add it some work areas that overlap with johtoselvitys areas. Add also an area that does not overlap with johtoselvitys work areas.
A notification should be shown in kaivuilmoitus work area table. If overlapping occurs with a single johtoselvitys, the notification should contain a link to that application. The application view should open in a new browser tab.

Checklist:

[x] I have written new tests (if applicable)
[x] I have ran the tests myself (if applicable)
[ ] I have made necessary changes to the documentation, link to confluence
or other location:

Other relevant info
Please describe here if there is e.g. some requirements for this change or
other info that the tester/user needs to know.

Icons shown in Figma in front and behind of the text are missing.


fixes to character offsets/indices (Not meant to reflect base game)

These changes are purely to make the pose offsets and animations feel more fluid and consistent, these will very much not fit what they look like in base game and are purely based on what I feel looks best in-game

these all look good, although, can you recheck parents christmas? the throne slides lmao

oh and could u add -loop on the idle of xmas parents too?


[WIP] changes to be able to run test-minimal-image on OpenDataHub

Signed-off-by: Jorge Garcia Oncins<EMAIL_ADDRESS>

Closed in favor of 873


chore: fix dependabot alerts

What type of PR is this?

Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs from IPAMD/CNI showing the issue:
Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades. Has updating a running cluster been tested?:
Does this change require updates to the CNI daemonset config files to work?:

Does this PR introduce any user-facing change?:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@raulkele if you are still up for it, can u pls see if you can move this along? think I am close.

@raulkele can u give some feedback on the ci failure?

@andaaron tested this with zot build, and works fine. We just need to fix the unit tests.
Let's first bump up react-dom (this PR) to 18.x and then let's look at 19.x
We use quite a few libs and they need to catch up too.

Im in the process of checking the issues

I believe I've found the issue, been fiddling around with it for a while. #367 is finally starting to bite us. It's getting more and more difficult to upgrade our dependencies while using the outdated toolchain. I'll see if I can get these to pass while I investigate a bit about the toolchain upgrade during Christmas vacation

I believe I've found the issue, been fiddling around with it for a while. #367 is finally starting to bite us. It's getting more and more difficult to upgrade our dependencies while using the outdated toolchain. I'll see if I can get these to pass while I investigate a bit about the toolchain upgrade during Christmas vacation

I tested zot itself against this change. UI renders fine and nothing obvious seems broken.

I believe I've found the issue, been fiddling around with it for a while. #367 is finally starting to bite us. It's getting more and more difficult to upgrade our dependencies while using the outdated toolchain. I'll see if I can get these to pass while I investigate a bit about the toolchain upgrade during Christmas vacation

I tested zot itself against this change. UI renders fine and nothing obvious seems broken.
Was trying to fix the following, without success :(
console.error
      Warning: An update to ForwardRef(TouchRipple) inside a test was not wrapped in act(...).

      When testing, code that causes React state updates should be wrapped into act(...):

Yup, the mismatch between newer dependencies and old toolchain is causing tests to mees up. I tested the ui myself and found no issue. It's up to you if you wanna give me a couple of days to make it pass the checks or if we need to merge it as is

It's up to you if you wanna give me a couple of days to make it pass the checks or if we need to merge it as is

I can wait :) and help appreciated.

https://www.npmjs.com/package/react-dom
^ not sure if rest of the ecosystem is ready for 19.x just yet

Opened a draft PR #466  based on your changes here with some unittest fixes and some additional package updates that weren't vulnerable but to be up to date with the other changes.
Got the unit tests fixed but I seem to be having some sort of trivy related error in the test data population script for the e2e tests.
I can open a PR to your branch here @rchincha, or clean up mine if we wanna drop this in favor of that one. Your call

Opened a draft PR #466 based on your changes here with some unittest fixes and some additional package updates that weren't vulnerable but to be up to date with the other changes. Got the unit tests fixed but I seem to be having some sort of trivy related error in the test data population script for the e2e tests.
I can open a PR to your branch here @rchincha, or clean up mine if we wanna drop this in favor of that one. Your call

Let's continue building on PR #466
@andaaron can you pls help with the 'trivy' image failure in e2e test in that PR?

@andaaron can you pls help with the 'trivy' image failure in e2e test in that PR?

Fixed in https://github.com/project-zot/zui/pull/467

Cleaned and updated #466

Superseded by PR #466


Allow the ability to run a stack with a custom service account/role

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
Currently the operator service account is the same account used to run the relevant stacks. It would be ideal to allow each stack to specify the service account it should use.
e.g.:
apiVersion: pulumi.com/v1
kind: Stack
metadata:
  name: nginx-k8s-stack
spec:
...
  stack: "vivek/example/dev"
  projectRepo: https://github.com/viveklak/example
  branch: "refs/heads/master"
  destroyOnFinalize: true
  serviceAccount: <sa> # or
  role: <role>

This will probably require running the operator with a clusterrole but then "dropping privileges" to the appropriate serviceAccount/role. We may also need to consider a means to limit which roles to allow the operator to use - i.e. this is the logical equivalent of assume role in IAM in some ways and has similar security considerations.

Affected area/feature

I think this violates a potential security principle. Segregation of actions from permissions. If the stack can define it's own permissions, (via a service account, and related RBAC or IAM role assigned to the service account), that can lead easily to privilege escalation.
What specific problem are you trying to solve though, that brought you to filing this issue?

We are looking at pulumi as a self service model.

@rajendragosavi just be aware that the self-service in this way allows anyone to gain any & all access that the operator has, even if they shouldn't have that access. A better option is to run a multiple operators, a matrix of project & environment. This ensures that an operator deployed to "development" for projectA cannot change anything in production (even accidentally), nor can it access resources from projectB in any environment.

Flux went through many discussions about how to support multi-tenancy (https://github.com/fluxcd/flux2/pull/2093 is as good an entry point as any ..). There's one main lesson, and one main problem.
Lesson: if you let people specify a service account or user, the default (when not supplied) should be an unprivileged account. Otherwise, just leaving out the service account name gives you the operator's permissions.
Problem: many platforms implicitly grant permissions to workloads (i.e., the operator pod), and it can be difficult to arrange different permissions when acting on behalf of a user. The most pertinent example for Pulumi is platform secret/key management -- see https://github.com/fluxcd/kustomize-controller/issues/324 for an example of the problem. At best, each service or platform needs individual, careful treatment.

Good news everyone, we just released a preview of Pulumi Kubernetes Operator v2. This new release has a whole-new architecture that uses pods as the execution environment. The Stack spec has a new serviceAccountName field to specify the pod's service account.  Since the Pulumi program runs in the pod, it no longer uses the operator's own service account.  One is expected to create a service account for the stack and to assign permissions as necessary.
Please read the announcement blog post for more information:
https://www.pulumi.com/blog/pulumi-kubernetes-operator-2-0/
Would love to hear your feedback!  Feel free to engage with us on the #kubernetes channel of the Pulumi Slack workspace.


fanart.tv Invalid project API key

Today i noticed i was missing some fanart so i started to retrieve them manually using artwork.beef but it constantly gave me Invalid project API key messages.
So i started to add my own fanart.tv key but that didn;t worked either.
Did i do something wrong or has fanart.tv changed his terms of use?
19:24:53.806 T:20308   ERROR: CCurlFile::Stat - Failed: Peer certificate cannot be authenticated with given CA certificates(60) for https://assets.fanart.tv/fanart/tv/317953/hdtvlogo/iron-fist-2017-589781e36a330.png
19:24:57.583 T:19164   ERROR: Previous line repeats 1 times.
19:24:57.583 T:19164   ERROR: CCurlFile::Stat - Failed: Peer certificate cannot be authenticated with given CA certificates(60) for https://assets.fanart.tv/fanart/tv/317953/tvbanner/iron-fist-2017-589f206e1b0f8.jpg
19:24:58.820 T:19164   ERROR: CCurlFile::FillBuffer - Failed: HTTP returned error 500
19:24:58.820 T:19164   ERROR: CCurlFile::Open failed with code 500 for https://assets.fanart.tv/fanart/tv/317953/tvbanner/iron-fist-2017-589f206e1b0f8.jpg:
19:25:02.439 T:20920 WARNING: [script.artwork.beef] Error with provider 'fanart.tv': Invalid project API key

The certificate error and HTTP 500 are temporary errors from their servers.
The built in fanart.tv project key is working, so likely either the add-on isn't installed correctly (if you've installed from source see the bottom of the README), or an invalid project API key is in the add-on settings.


Can't find website

Having moved to a new server, KeyBase is claiming it can't find my website. However, it is working just fine. When I try to authenticate I just get 'That domain isn't loading. Are you running a site there?'. I am, and it's loading fine whenever I try it and I confirmed with down.com too. The address is https://mrpjevans.com/.

There seems to be something wrong with your SSL certificate. For example, I can't curl your website:
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.


"Readme Chart 1" broken link

Thanks.
https://github.com/vegas-viz/vegas-viz.github.io/pull/2 will fix the issue.


Export mesh not working

I am trying the official example but the vertices are empty
python -m lrm.inferrer --model_name lrm-base-obj-v1 --source_image ./assets/sample_input/owl.png --export_mesh

lrm/models/rendering/synthesizer.py", line 189, in forward_points
for k in outs[0].keys()
IndexError: list index out of range

how did you solve this?

hello I came across the same problem, how did you solve it?


Renovate poc

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: pankajmouriyakong:x: amankongYou have signed the CLA already but the status is still pending? Let us recheck it.


[AzureMonitorExporter] update dependent projects for Exporter

Azure.Monitor.OpenTelemetry.Exporter.Perf has a dependency on Azure.Test.Perf.
I added that project to our solution.

Curious, why do we want to do this?

Curious, why do we want to do this?

Our Perf project has a dependency on this project and will fail to build if the Azure.Test.Perf is not also built.

Curious, why do we want to do this?

Our Perf project has a dependency on this project and will fail to build if the Azure.Test.Perf is not also built.

What if Azure.Test.Perf later added another dependency, are you going to keep maintaining the dependency chain?

API change check
API changes are not detected in this pull request.

What if Azure.Test.Perf later added another dependency, are you going to keep maintaining the dependency chain?

At the moment, yes. :(
This could be mitigated if Azure.Test.Perf was published and we could take a PackageDependency. But for as long as we have ProjectDependencies we can have issues like this.

Would you investigate what's the right approach? I suggest that we avoid any hacks that require ongoing obligations (e.g. "are you going to keep maintaining the dependency chain - yes" is something I'm very concerned about).


Translate SlicerVisualizationTutorial to French

The tutorial is available here: https://spujol.github.io/SlicerVisualizationTutorial/

[ ] Upload .pptx file to the repository => Sonia
[ ] Update the English version: run the tutorial with the latest Slicer Preview Release, if anything has changed then change it in the slides
[ ] Translate the pptx to French

This repository will be removed because we have too many repositories for this project already. The issue is moved to https://github.com/Slicer/SlicerLanguagePacks/issues/3


Add Search box in staff and active members page

resolves #487

Awesome PR @MadhuSaini22!! Could make your variable names a little more descriptive please?

Awesome PR @MadhuSaini22!!


How to figure out the ideal number of contrastive steps

I am seeing that utterances belonging to different classes in my dataset are lying close to each other in the embedding space. For example, when I try to find utterances similar to I need to change beneficiary [updateBeneficiary], I get utterances from other classes too, like I need to remove beneficiary[removeBeneficiary] and Want to add beneficiary to my account [addBeneficiary].  Also, all the beneficiary related datapoints are being predicted as [addBeneficiary] regardless of the groundtruth. Representation in the training set is as follows: {"addBeneficiary":70, "updateBeneficiary":21, "removeBeneficiary":29}. Here are my questions:

Is the setfit approach sensitive to this kind of class imbalance?
Can this be solved by increasing the number of contrastive examples, currently set to 15? But increasing this would lead to overfitting?

This sounds really interesting. Did you make progress? Have you tried Optuna to tweak the hyperparameters? I'm thinking that it might be the logistic regression in the head that needs tuning rather than the contrastive iterations on the body.

After #439 is merged & released this week, then you'll be able to track evaluation loss during training. This might help guide your choice for the (new) max_steps and num_epochs parameters. You will also be able to use an EarlyStoppingCallback from transformers with a load_best_model_at_end=True argument to load the model which has the best evaluation performance rather than the model with the best training performance.
This should help avoid overfitting.


Changes LoadFile to LoadFrom to load DLLs included by plugins

This PR fixes an issue that was encountered trying to chain load DLL's included by a plugin.
Developing a plugin for sound control required an external DLL that refused to be found by Assembly.LoadFile. Upon further investigation replacing the function to LoadFrom fixes this without side-effects to existing functionality.

Thanks for the PR. Consider it merged!


Check markers for contrast for people who are color blind

I found a website that you can plug a URL into and get a synthesized color-blind view. Determine if the contrast between "Adopted Drains" and "My Drains" is different enough.
https://www.toptal.com/designers/colorfilter?orig_uri=https://lgrow-staging.herokuapp.com&process_type=protan

I like this map better than the actual map.  Blue tends to hold up best.  The red was always a bad ADA choice.
I would suggest changing the "Adopted by you" color to black.    This would help both color sighted and color blind folks.  Also it would enhance the "Adopted by you" symbol's figure-ground making "Adopted by you" symbols easier to spot.

Our resident color blind GVSU grad student ok'd the current map. They symbols are different enough for him to see. We can keep the map as-is.

Closing issue based on Cara's comment!


Update DG

Fixes #203

Codecov Report
Base: 48.65% // Head: 48.65% // No change to project coverage :thumbsup:

Coverage data is based on head (2b46393) compared to base (b15d4d6).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #205   +/-   ##
=========================================
  Coverage     48.65%   48.65%
  Complexity      578      578
=========================================
  Files           151      151
  Lines          2758     2758
  Branches        362      362
=========================================
  Hits           1342     1342
  Misses         1302     1302
  Partials        114      114

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Rubocop: Update 1.28.2->1.50.0; requires Ruby 2.6

I need to validate the rubocop.yml on a few modules before we can release this. some namespaces changed.

Tests:

https://github.com/voxpupuli/puppet-collectd/pull/1027


[1Password] ...

Extension
https://www.raycast.com/khasbilegt/1password
Description
Logging into business account gives the error "spawnSync /usr/local/bin/op ENOBUFS".

Signing into my personal account works fine.
Steps To Reproduce

Open My  Passwords
Choose a team account from the list

Current Behaviour
Receive an error and account is not opened.
Expected Behaviour
Should see passwords in team account

@pernielsentikaer could this be related to the buffer size?

Could be 😊
@aluminumfalkon what does op item list | wc -l in a terminal give you?

@aluminumfalkon what happens when you try to manually sign in using the cli directly?


One more question, sorry...

Hi, is the random augmentation implemented a faster/better transform than the torchvision transforms.RandomAffine function?

RandomAffine doesn't allow different shifts for individual samples in the batch, which is crucial.

Can I ask, what if the RandomAffine was applied in the DataLoader?

Sorry, I gotta bump this. I think for different augmentations, this could be a big speedup, especially if applying each one uniquely per datapoint is crucial


Cannot read property 'offsetWidth' of undefined

Hello, the release of the newest version (1.1.2) seems to have a bug. I get this error after updating:
index.js:65 Uncaught TypeError: Cannot read property 'offsetWidth' of undefined
    at Object.Tabs._this.onResize (index.js:65)
    at invokeFunc (index.js:160)
    at leadingEdge (index.js:170)
    at Object.debounced [as onResize] (index.js:235)
    at ResizeDetector.componentDidMount (ResizeDetector.js:69)
    at eval (ReactCompositeComponent.js:264)
    at measureLifeCyclePerf (ReactCompositeComponent.js:75)
    at eval (ReactCompositeComponent.js:263)
    at CallbackQueue.notifyAll (CallbackQueue.js:76)
    at ReactReconcileTransaction.close (ReactReconcileTransaction.js:80)

Thanks for reporting this. Fixed in 1.1.3


Update start-installation.md

In the Yii2 Guide, where the Advanced Project Template is mentioned, the link should be to the topic about it in the guide, rather than to an .md file in a github repository.

Merged. Thanks!


Running the tests

Just wondering if there is a trick to running the test suite?
I'm looking to fix/support setting state value for mapbox when geocoding a state value.
The tests for the mapbox geocoder fail and it seems like it's not picking up any of the VCR cassettes
Here is a gist of the output for that test https://gist.github.com/smingins/9f6cefeb4e75dbef29bf9ad26912e132
I'm using Ruby 2.3.0

Are you running the code off the master branch with no modifications?
That works fine for me with the command you ran (bundle exec rake test TEST=test/test_mapbox_geocoder.rb)
Travis (travis-ci.org) seems to be able to run it fine also.
I tried it on ruby 2.3.0 as well. Could you include the git sha of the commit your running and git status to ensure we're running the same code? (maybe a fresh clone into a new directory is a good idea too)

I tried a fresh clone.  The only modification is the .ruby-version file.
smingins:~/Projects/Temp/geokit[master] $ git st
On branch master
Your branch is up-to-date with 'origin/master'.
Untracked files:
  (use "git add <file>..." to include in what will be committed)

	.ruby-version

nothing added to commit but untracked files present (use "git add" to track)

smingins:~/Projects/Temp/geokit[master] $ git show-ref master
23f71f9f89915c21b860f3d45079e412a5eecc7a refs/heads/master
23f71f9f89915c21b860f3d45079e412a5eecc7a refs/remotes/origin/master
smingins:~/Projects/Temp/geokit[master] $ git last
commit 23f71f9f89915c21b860f3d45079e412a5eecc7a
Author: Michael Noack<EMAIL_ADDRESS>Date:   Sat Apr 30 00:04:49 2016 +0930

    Extract URLs to shorten lines/remove duplication
smingins:~/Projects/Temp/geokit[master] $

Still same results.  When digging yesterday it felt like something odd with VCR was happening for me.  I added a new test with a VCR block that I thought would have created a cassette on it's initial run, but did not.
Not sure if that sparks any thoughts as to what might be happening for me locally?
Otherwise I'll keep digging :-)
Cheers
Shane

@smingins I can ONLY get the same error as your initial gist if I delete the cassettes
e.g. I did this to replicate your error:
rm fixtures/vcr_cassettes/mapbox_*
Can you confirm that these mapbox cassettes exist and are not empty AND they match those in the geokit repo in master?
Interestingly there should be no difference but clearly geokit is now out of date compared to the live mapbox system by the looks of it.
But of course there still is some issue with your setup and it not using the provided cassette.

@mnoack looks like I am hitting a bug in vcr's webmock handler.  I created a small project and used vcr's example setup using Net:HTTP to get http://www.iana.org and it was not hitting any of the after request handlers to record and write the interaction.  I switched it to use Faraday and it works as expected.  I have a rails project that works as expected with webmock so I am puzzled.
Thanks for the help though ... hopefully I can get this resolved and get a PR in for the mapbox tweak :-)

@mnoack so an update ... for the tests to pass for me I needed to add:
require 'webmock/test_unit' to helper.rb
I don't know why but that fixed all cases.  And when using minitest it was require 'webmock/minitest' and likewise for rspec (which was why the existing rails project I had was working)
So not sure why I hit that and others don't.

@smingins Thanks a bunch, this started driving me nuts as well as it started affecting me. Turns out webmock 2.0 was just released recently which requires this addition (https://github.com/bblimke/webmock/blob/master/CHANGELOG.md#200)
So a week ago it was fine, but a fresh bundle now fails. Downgrading to webmock 1.x fixes it (or better the solution you gave)
I'll make a fix referencing the changelog for webmock very soon


x-axis date annotations doesn't show if x-axis type is category

I need help.
Can annotations x-axis be added when x-axis is of "categories" type?

@junedchhipa hey, it seems like xaxis annotations don't work if xaxis is category, the inputted data is string timestamps, and the tickPlacement is 'between'.
if i switch the tickPlacement to 'on', i see the xaxis annotation.
i think this is a bug

(well there is a work-around: just pretending x-axis labels are shown, then set them with a font size of 0)


[refactor-prompt] enforce pw prompt send

What current issue(s) does this address, or what feature is it adding?
In #780 (and another PR) we discussed if we should be prompted for the wallet password before we can send funds. The question has been posted on slack and after some thought I think that at least from the cli it should be asked for.
Previously we could bypass it using a --ask_for_pw type of flag. While the logic remains in some parts of the code (so people can programmatically choose), from the CLI it is no longer possible to bypass for security reasons.
How did you solve this problem?
remove optional arg to bypass
How did you make sure your solution works?
make test
Are there any special changes in the code that we should be aware of?
no
Please check the following, if applicable:

[X] Did you add any tests?
[X] Did you run make lint?
[X] Did you run make test?
[X] Are you making a PR to a feature branch or development rather than master?
[ ] Did you add an entry to CHANGELOG.rst? (if not, please do)

I think not, sorry. It took some input and more dabbling on the options before I got to this conclusion.


Remove the need for explicit expression syntax and parameter interpolation

Essentially make it so that instead of writing
@production(m, X, 1, PX, 100, [Input(PL, :(25 * $inputcoeff)), Input(PK, 50)])

one can write
@production(m, X, 1, PX, 100, [Input(PL, 25 * inputcoeff), Input(PK, 50)])

Definitely done.

Absolutely, fabulous.


fix: add option to change remote svg icon colour

[ ] Added an entry to CHANGELOG.md if this change could be valuable to users

No plugin provides settings:

Plugins with settings exist:

Codecov Report

Merging #1820 (bff41e2) into master (19cefff) will increase coverage by 0.03%.
The diff coverage is 0.00%.

:exclamation: Current head bff41e2 differs from pull request most recent head 55bfd7e.  Learn more


<EMAIL_ADDRESS>decompress error

Try to scoop update and install the latest. I was able to install 1.38.1 just fine.

Thank you, this works。


PANIC in query-engine/core/src/query_document/parser.rs:250:87called Option::unwrap() on a None value

Hi Prisma Team! My Prisma Client just crashed. This is the report:
Versions

Name
Version

Node
v14.17.0

OS
linux-musl

Prisma Client
2.24.1

Query Engine
query-engine 18095475d5ee64536e2f93995e48ad800737a9e4

Database
undefined

Query
mutation {
  createOneOrder(data: {
    total: 5e+23
    customer: "X"
    status: CREATED
    createdAt: "X"
  }) {
    id
    customer
    total
    status
    createdAt
    confirmedAt
    deliveredAt
    canceledAt
  }
}

Logs
prisma:tryLoadEnv Environment variables not found at null
prisma:tryLoadEnv Environment variables not found at undefined
prisma:tryLoadEnv No Environment variables loaded
prisma:tryLoadEnv Environment variables not found at null
prisma:tryLoadEnv Environment variables not found at undefined
prisma:tryLoadEnv No Environment variables loaded
prisma:client clientVersion: 2.24.1
prisma:engine { cwd: '/app/node_modules/.prisma/client' }
prisma:engine Search for Query Engine in /app/node_modules/.prisma/client
prisma:engine Search for Query Engine in /app/node_modules/.prisma/client
plusX Execution permissions of /app/node_modules/.prisma/client/query-engine-linux-musl are fine
plusX Execution permissions of /app/node_modules/.prisma/client/query-engine-linux-musl are fine
prisma:engine { flags: [ '--enable-raw-queries', '--port', '44537' ] }
prisma:engine stdout  Starting a postgresql pool with 7 connections.
prisma:engine stdout  Started http server on http://<IP_ADDRESS>:44537
prisma:engine Search for Query Engine in /app/node_modules/.prisma/client
plusX Execution permissions of /app/node_modules/.prisma/client/query-engine-linux-musl are fine
prisma:engine Client Version: 2.24.1
prisma:engine Engine Version: query-engine 18095475d5ee64536e2f93995e48ad800737a9e4
prisma:engine Active provider: postgresql
prisma:engine stdout  PANIC in query-engine/core/src/query_document/parser.rs:250:87
called `Option::unwrap()` on a `None` value
prisma:engine {
  error: SocketError: other side closed
      at Socket.onSocketEnd (/app/node_modules/@prisma/client/runtime/index.js:26097:24)
      at Socket.emit (events.js:388:22)
      at endReadableNT (internal/streams/readable.js:1336:12)
      at processTicksAndRejections (internal/process/task_queues.js:82:21) {
    code: 'UND_ERR_SOCKET'
  }
}
prisma:engine {
  error: Error: connect ECONNREFUSED <IP_ADDRESS>:44537
      at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) {
    errno: -111,
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '<IP_ADDRESS>',
    port: 44537
  }
}
prisma:engine { cwd: '/app/node_modules/.prisma/client' }
prisma:engine Search for Query Engine in /app/node_modules/.prisma/client
plusX Execution permissions of /app/node_modules/.prisma/client/query-engine-linux-musl are fine
prisma:engine { flags: [ '--enable-raw-queries', '--port', '40619' ] }
prisma:engine stdout  Starting a postgresql pool with 7 connections.
prisma:engine stdout  Started http server on http://<IP_ADDRESS>:40619
prisma:engine Search for Query Engine in /app/node_modules/.prisma/client
plusX Execution permissions of /app/node_modules/.prisma/client/query-engine-linux-musl are fine
prisma:engine stdout  PANIC in query-engine/core/src/query_document/parser.rs:250:87
called `Option::unwrap()` on a `None` value
prisma:engine Client Version: 2.24.1
prisma:engine Engine Version: query-engine 18095475d5ee64536e2f93995e48ad800737a9e4
prisma:engine Active provider: postgresql
prisma:engine {
  error: SocketError: other side closed
      at Socket.onSocketEnd (/app/node_modules/@prisma/client/runtime/index.js:26097:24)
      at Socket.emit (events.js:388:22)
      at endReadableNT (internal/streams/readable.js:1336:12)
      at processTicksAndRejections (internal/process/task_queues.js:82:21) {
    code: 'UND_ERR_SOCKET'
  }
}

Client Snippet
// PLEASE FILL YOUR CODE SNIPPET HERE

Schema
// PLEASE ADD YOUR SCHEMA HERE IF POSSIBLE

Hello! Can you please provide a minimal reproduction for the above crash? Unfortunately the automatically collected information in the issue does not give us much to go with here - we will need a bit more information. What were you doing? Can you share the code and schema that was active?

6 months later no further information, so I think we can consider this closed.
If this ever happens again, please comment here or even better - create a new issue. Thanks.


atom installation

Hi ,
I'm using this editor.due to insufficient system battery window had been shutdown automatically , when i reopened and start   editor its showing below error.
SyntaxError: Unexpected token
at Object.parse (native)
at FileSystemBlobStore.load (C:\Users\Admin\AppData\Local\atom\app-1.3.2\resources\app.asar\src\file-system-blob-store.js:36:31)
at Function.load (C:\Users\Admin\AppData\Local\atom\app-1.3.2\resources\app.asar\src\file-system-blob-store.js:10:14)
at window.onload (file:///C:/Users/Admin/AppData/Local/atom/app-1.3.2/resources/app.asar/static/index.js:18:39)
please help me in this

Duplicate of #10015.

Thanks @Zireael07! Closing in favor of https://github.com/atom/atom/issues/10015.


Ads on http://www.dallasobserver.com not blocked

All ads are showing up on this site.

Looks like these ads have a standard other than the () disclosure standard this is currently designed to detect. They seem to be served by "Real Media."


Cursors at Line Ends is confusing

Testing https://github.com/Microsoft/vscode/issues/16558
The command "Selection > Cursors at Line Ends" has too many cases for where it just does nothing:

when you do not have a selection
when you have multiple cursors without selection
when you have multiple cursors with selection
when you have a selection on a single line

It only seems to work when you have a multi line selection. If that is the intent then maybe it should be renamed?

@seanmcbreen Can you think of a better name for 'Cursors at Line Ends'?
Other editors have 'Split into Lines' for a similar action that keeps the characters selected. I just cannot think of a variation that would better label ours.

I've opened #16771 to track the multi-selection case. Lets use this issue to improve the label.

I think it mainly just needs a verb, like 'add cursors to line ends', I don't know if it can get any longer than that.
I think I would have figured it out if it did something when there's no selection.

Any reason we don't make the behavior the same as 'split into lines', and use that same name?

Add Cursor to End of Selected Lines  [long I know...]

From blaming the code that implements the action, it came in through PR #1479
IMHO this was a direct implementation of the Sublime Split into Lines command (Ctrl+Shift+L) which behaves 100% the same (@bpasero)

@alexandrudima my Sublime does not seem to have such a command.

+1 for naming it the same way as in ST then.

@alexandrudima The behavior is not the same from what I see. Ours ends with multiple cursor but no characters selected. Sublime's keeps the same characters selected while splitting the selection along lines.

We can ask our Sublime keybindings experts what Sublime action this is supposed to be and if it is a bug. @waderyan ?

I'll reach out and see what I can find out.

For this milestone: Updating it to 'Add Cursors to Line Ends' as @roblourens suggested. I think it is clear from the 'Selection' menu as its context that it will affect the selected lines, hence 'Add Cursor to End of Selected Lines' as @seanmcbreen suggested would seem a little redundant. Sublime's 'Split into Lines' is not a good match because that is not what the action does.

I would expect this command also to work when you have a selection in a single line. Currently this does not work.

@bpasero It does to a single line what it does to the last line in a multi-line selection. That seems consistent. What would you like to see change?

I see now. This is a command that is super hard to understand imho and I will never use it.

I see what you are saying. It is also slightly redundant with Add Cursor Above/Below because these followed by End achieve the same thing with only one additional keystroke. Let's see if it gets any significant use and remove it if not.


Update Concepts on the website

@sakshigoel12 commented on Wed Sep 13 2017

What specifically is still pending and what's the ETA?

I've checked the general conceptual overview and the Mixer material and all that is up to date for 0.2. Someone should give the traffic management stuff a once over as well as the auth section.

@wattli is going to run through Auth and clean it up.
@rshriram can you review traffic management section?

Traffic management has been updated. Auth was also updated, but might need a cleanup

@wattli  confirmed security is good.


refactor: group routing module files into dirs by feature

Issue or need
Same as previous PRs but for routing module

Proposed changes
Same as previous PRs but for routing module
Removes exporting the NAVIGATION_END type, not needed.

Quick reminders

🤝 I will follow Code of Conduct
✅ No existing pull request already does almost same changes
👁 Contributing docs are something I've taken a look at
📝 Commit messages convention has been followed
💬 TSDoc comments have been added or updated indicating API visibility if API surface has changed.
🧪 Tests have been added if needed. For instance, if adding new features or fixing a bug. Or removed if removing features.
⚙ API Report has been updated if API surface is altered.

#866  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @davidlj95 and the rest of your teammates on  Graphite


Need of restarting container for certificate to work

Some users are reporting that they need to restart the container for certificates to work.
It is strange, as it seems pretty recent and I did not changed anything.
The log when it renew
Creating/renewal btcpayserver.***.org certificates... (btcpayserver.***.org)
2020/03/10 12:45:51 Received event die for container 54f85b0c5026
2020-03-10 12:45:53,647:INFO:simp_le:1323: Generating new account key
2020/03/10 12:45:56 Received event start for container 54f85b0c5026
2020/03/10 12:45:58 Received event die for container 54f85b0c5026
2020/03/10 12:46:06 Received event start for container 54f85b0c5026
2020/03/10 12:46:08 Received event die for container 54f85b0c5026
2020-03-10 12:46:13,744:WARNING:simp_le:1346: --email was not provided; ACME CA will have no way of contacting you.
2020-03-10 12:46:13,745:INFO:simp_le:1353: By using simp_le, you implicitly agree to the CA's terms of service: https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf
2020-03-10 12:46:14,347:INFO:simp_le:1414: Generating new certificate private key
2020/03/10 12:46:23 Received event start for container 54f85b0c5026
2020/03/10 12:46:24 Received event die for container 54f85b0c5026
2020/03/10 12:46:39 Debounce minTimer fired
2020/03/10 12:46:40 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'
2020/03/10 12:46:51 Received event start for container 54f85b0c5026
2020/03/10 12:46:53 Received event die for container 54f85b0c5026
2020-03-10 12:47:00,863:INFO:simp_le:396: Saving account_key.json
2020-03-10 12:47:00,865:INFO:simp_le:396: Saving account_reg.json
2020-03-10 12:47:00,866:INFO:simp_le:396: Saving key.pem
2020-03-10 12:47:00,867:INFO:simp_le:396: Saving chain.pem
2020-03-10 12:47:00,868:INFO:simp_le:396: Saving fullchain.pem
2020-03-10 12:47:00,869:INFO:simp_le:396: Saving cert.pem
/app
Warning: /etc/nginx/certs/accounts/acme-v02.api.letsencrypt.org/directory does not exist. Skipping ownership and permissions check.
Warning: /etc/nginx/certs/accounts/acme-v02.api.letsencrypt.org does not exist. Skipping ownership and permissions check.
Warning: /etc/nginx/certs/accounts does not exist. Skipping ownership and permissions check.
Reloading nginx docker-gen (using separate container nginx-gen)...
Reloading nginx (using separate container nginx)...
Sleep for 3600s
2020/03/10 12:47:08 Debounce minTimer fired
2020/03/10 12:47:08 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'
2020/03/10 12:47:46 Received event start for container 54f85b0c5026
2020/03/10 12:47:47 Received event die for container 54f85b0c5026
2020/03/10 12:48:02 Debounce minTimer fired
2020/03/10 12:48:02 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'
2020/03/10 12:48:49 Received event start for container 54f85b0c5026
2020/03/10 12:48:51 Received event die for container 54f85b0c5026
2020/03/10 12:49:06 Debounce minTimer fired
2020/03/10 12:49:06 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'
root@raspberrypi:~/btcpayserver/btcpayserver-docker# btcpay-down.sh

Then the certificate does not work, they restart
Info: Rewriting ACME_CA_URI from production to https://acme-v02.api.letsencrypt.org/directory
Info: Creating Diffie-Hellman group in the background.
A pre-generated Diffie-Hellman group will be used for now while the new one
is being created.
Generating DH parameters, 2048 bit long safe prime, generator 2
Reloading nginx docker-gen (using separate container nginx-gen)...
Reloading nginx (using separate container nginx)...
Sleep for 3600s
2020/03/10 12:50:49 Generated '/app/letsencrypt_service_data' from 16 containers
2020/03/10 12:50:49 Running '/app/signal_le_service'
2020/03/10 12:50:49 Watching docker events
2020/03/10 12:50:50 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'
/etc/nginx/certs/btcpayserver.***.org /app
Reloading nginx docker-gen (using separate container nginx-gen)...
Reloading nginx (using separate container nginx)...
Creating/renewal btcpayserver.***.org certificates... (btcpayserver.***.org)
2020/03/10 12:50:52 Received event die for container a08838b254e4
2020-03-10 12:50:54,728:INFO:simp_le:1546: Certificates already exist and renewal is not necessary, exiting with status code 1.

Then the certificate finally works. Would you have any idea of what could go wrong?
Ping @pavlenex

Hi
Where does that log line
Info: Rewriting ACME_CA_URI from production to https://acme-v02.api.letsencrypt.org/directory
comes from ?

@buchdag it comes from our fork of your project:
https://github.com/btcpayserver/docker-letsencrypt-nginx-proxy-companion
this is based on your commit 9806ba25871d26a3eadeecf3771afd3378f0b01a
We needed to fork to publish multi arch image.

I'd say that either the symlinks in /etc/nginx/certs/ aren't correctly created after certificate issuance or nginx isn't correctly restarted, you should investigate both.

Thanks I will try to reproduce better and add more info.
I got report from users recently around this that did not had problems before, but I could not reproduce myself to study it. Will keep you posted.

i am also facing the same issue. I have to restart the container to get the certificate symlink

it's still happening time to time but sadly I don't manage to isolate the problem :(

@NicolasDorier you've established from your logs that the certificate are correctly renewed, so I can only thing of the few following things hapenning :

the letsencrypt-nginx-proxy-companion container somehow incorrectly removes the symlinks in /etc/nginx/certs
docker-gen generate an incorrect /etc/nginx/certs/default.conf file
the previous two are okay but the nginx config isn't reloaded

@buchdag
Might it be a timing issue?
Reloading nginx docker-gen (using separate container nginx-gen)...
Reloading nginx (using separate container nginx)...

What if what happen is:

docker-gen starts
nginx starts
docker gen generates the new default.conf

If you use docker restart, the command returning does not necessarily mean that the new config has been generated.

docker-gen is supposed to be signaling nginx to reload after generating default.conf :
$ docker run --volumes-from nginx \
    -v /var/run/docker.sock:/tmp/docker.sock:ro \
    -v $(pwd):/etc/docker-gen/templates \
    -t jwilder/docker-gen -notify-sighup nginx -watch /etc/docker-gen/templates/nginx.tmpl /etc/nginx/conf.d/default.conf

This is what the --notify-sighup flag does.

Inactive issue, closing.


Added current_timestamp alias

Which issue does this PR close?

Closes #12925 .
Rationale for this change

What changes are included in this PR?
Added current_timestamp alias to now()

Are these changes tested?

Are there any user-facing changes?

🚀


Update garbage-collector.md

added some clarification to the standalone GC configs. describes the behavior in .net8 and prior vs .net9. also added a header for each config since there are multiple in this section.

Internal previews

📄 File
🔗 Preview link

docs/core/runtime-config/garbage-collector.md
Runtime configuration options for garbage collection

CC @cshung.

I confirm the content is accurate.

do you have any feedback, @gewarren ?


[ROCm] Update to use ROCm 4.0 (when building TF with --config=rocm)

/cc @cheshire @chsigg @nvining-work

@gbaned anything I can do on my end to get this PR merged?

@gbaned anything I can do on my end to get this PR merged?

@deven-amd This PR is waiting for internal approval. Nothing to do at this moment from your end. Thank you!


Can live in and breathe oil

Mined into an oil well and fell right in, all is well.

Oritech 0.6.0

Good catch. Adding some sort of status debuffs while in oil might be a good idea. I'll probably include this in a future version

I've been playing with it on a server, and players are just falling into the oil holes left and right and dying from the fall. At the very least it should behave like water and not air.

I noticed that the oil doesn't seem to register any kind of collision/interaction with the player and possibly all other entities too.
I think the oil should apply great friction on the player like lava does, and maybe it can also hinder visibility. However, Fabric API's methods for registering fluids have felt rather weird and insufficient to me the last time I played with them, which was almost a couple years ago, so I don't know how easily this could be implemented or if the methods have improved since.

I made a short video demonstrating the issue:


Add support for elixir filetypes

resolves #8401
In this PR description I'm using ^[text]  to signify a line in the file starting with "text" and followed by a space. I.e., column 1 is occupied by a non-whitespace character.
Notes

I removed *.sface as an elixir filetype, which was listed as such in the issue. While Surface is a relatively popular UI library for Elixir/Phoenix/LiveView, it's not part of elixir core. All the other filetypes are.

I checked the first 10 lines of every .ex file in OpenEuphoria and found that almost every file had a line either starting with ^--  or ^include . I added a regex check for these most common lines in the first commit. (One interesting result in GitHub search is "--" extension:ex language:elixir.  One of the top results is a self-identified Euphoria4 file incorrectly identified by GitHub as an elixir file.)

There were only 3 of out 40+ .ex euphoria files in OpenEuphoria that were not correctly identified by ^--  or ^include

One could be detected via ^ifdef  (in fact, top advanced GitHub results for this show misidentified euphoria files).
The other two could be detected via ^--[text] , where [text] is any word.

I included checks against both of these scenarios in the second commit.

Other Euphoria keywords that likely never begin a line of elixir code are ^without , ^constant , and ^integer . I corroborated this via a brief advanced GitHub search of type [keyword] extension:ex language:elixir. I left these out of dist#ft#ExCheck because I worry about being too expansive in our regex checks, which could risk edge-case misidentification.

I was unsure how to best test dist#ft#ExCheck, though I did add tests for the other elixir filetypes.

Questions
Lastly, do you recommend this PR include updates to vim/runtime/doc/syntax.txt and vim/runtime/doc/tags?

Thanks for the PR.
Can you please add a test for the dist#ft#ExCheck() function?
Exercising the three possible outcomes.
There are some examples near the end of test_filetype.vim.

Hey @brammool , added a Test_ex_file() covering the four match cases.

OK, but the test only checks getting "euphoria3".  Well, there is a test getting "elixir" for an empty file, in the big table.  Please add a test case using g:filetype_euphoria.  Best is to use a file that detects as "elixir" first, then results in g:filetye_euphoria once that is set.

I actually had not added the empty-file test for file.ex, but since this will now be the new default filetype for that extension, I went ahead and added it there, in addition to testing again in the (now more robust) test of dist#ft#ExCheck.
I cleaned up the regex regarding the detection of lines starting with --. I was checking for both whitespace and non-whitespace, so just simplified it to ^--\|....


Make poetry init non-interactive by default

It seems odd to me that poetry init is, by default, interactive. The defaults are normally right and it's pretty annoying to go through those steps (or remember to use -n). I propose swapping -n, --no-interaction for -i, --interactive.
Furthermore, the default choices for defining dependencies should, in my opinion, be no. Although, searching for and listing dependencies is quite neat and would be appreciated in poetry add, either when no argument is given or when a -i flag is passed.
What are your thoughts on this? Feel free to close if you wholeheartedly disagree or open new separate issues if you like the ideas.

When using poetry init, my guess is you already have a pretty good idea of the dependencies you need as opposed to poetry new. Btw, if you spam Enter it works just fine even without specifying "no"


microservice: python function for database connection and retry.

Currently, the microservices connect to the db on startup.  If the database is not available the startup fails which causes "crashloopbackoff".   Also, if the db is taken down while the container is running then connection variable in the python code is no longer valid.
Need a function that will see if the microservice is connected to the db.  if not then retry otherwise use the existing connection.

What about this: 1. implement DB healthcheck (simple new connect/select/close sql) that microservice 'readiness' uses during start (will not be ready to serve request untill DB runs OK) 2. using it for liveness would cause microservice to restart, so connection pool will be refreshed

@tbulubas something like that could work.  Need to pin down the logic since we would not necessarily want to connect to the db on startup but delay it for the first transaction.  For example, 100 microservices in the k8s and only 20 of them are used frequently.
if we connect on startup then we have 100 db connections.  If we connect on usage, then only 20.  We will have a cost hit for first transaction to establish a connection but should be minimal. Once a connection is established then reuse it.
I think your idea of incorporating the health check could work if we can figure out where to hook it into the microservice.

@scanalesespinoza can you post the pybreaker code that you have working so far to a repo so I can grab it and take a look at it?

Hi @sbtaylor15 , I was working based on this repo https://github.com/gjorgjinac/recommender_server
Similar what we have

Hi @sbtaylor15  here is a PR with the local tested circuit breaker https://github.com/ortelius/ortelius-ms-dep-pkg-cud/pull/5
Need a peer review o tested from my fork in another environment just to double check.
Maybe @tbulubas can do the review

Looks good and simple.  Merged the PR.  Thanks for working on this.


[WIP] Implement Elastic Search Code Indexer

Creates Issue indexer as a separate package: "codes" (will be changed to code later).
Added elastic search support for indexer instead of "bleve"
Ref issue: #6648

Is this PR still alive? Otherwise I'd like to take #3670.

Is this PR still alive? Otherwise I'd like to take #3670.

Yes, planning on finishing it. (Haven't gotten a chance to work on it recently)

@jeffliu27 do you had some time for this feature?.

@jeffliu27 do you had some time for this feature?.

@jeffliu27 are you still working on this?

@lunny can this here be implemented with the same logic as you are implementingthe issue indexer?

@Cellebyte Yes. I will do that and replace this one if my previous issue indexer merged.

@jeffliu27 Any news on your diff? It seems your code has conflicts.


Eslint will enter error state and needs restart vscode.

After I fixed the eslint error, the it will, sometimes, still have old error there, and only restart can fix this.

Note: in the image above, I have already fixed the Radio by change it to Select, but the old error still exists and can fix until restart vscode

@xpol if this happens can you enable tracing to see if the server is still responding to validation request. To enable it add the setting "eslint.trace.server": "verbose" and provide the Output of the ESLint output channel.
Are you able to reproduce this. I would appreciate a GitHub repository I can clone then.


[FR] Improve a11y support for ApiDemoPanel

Is your feature request related to a problem?
Some elements in the ApiDemoPanel cannot be accessed by keyboard/tab.
Describe the solution you'd like
Apply tabindex: 0 to appropriate elements to ensure highest a11y experience.
Describe alternatives you've considered
n/a
Additional context
Improving a11y not only improves UX but also helps improve SEO.

PR: #149
The following ApiDemoPanel components are now fully supported with keyboard tab:

ParamOptions
Server

Pending Components:

[ ] Tab support for LiveEditor. Potential solutions achieve expected behavior when building locally, but does not persist within the Deployed Preview. Will need to investigate further, and/or table until prop solution becomes available for react-live


Onboarding Threema success screen contains debug information(?)

This looks like someone tested updating the onboarding success text to include the word Updated.


feat: filter and reprojection with increased usability

feat: filter and reprojection with increased usability

Summary of Changes

Lasso select is a new chip in the filter for filteredTable
Can rerun projection on filter
Loading animation for when the projection is running
If the embedding does not exist, say there is no embedding and do nothing

Known issues
For development, when hot reloading, the colors mess up. Requires a full reload. (only a development problem, for actual users this would never come up). ~Will create an issue for this and revise it in the next pr because its not terribly important right now to fix.~ Issue #355 was created for this.

Looks amazing!
One high-level comment is we should aim to make filtering as consistent as possible across the metadata widgets and lasso. * In my mental model when you select a metadata column it should be represented in the embedding, maybe by opacity?

And when you clear all, the lasso selection should go away.
When you re-run projection, it should also clear the lasso selection.
Maybe when you reproject we put those filters somewhere else? I cleared it by accident a couple of times and it reset to the main filter when I just wanted it to filter to the projection
Coloring seems to be broken in the re-projections?

No need to cram this into this PR I'll make an issue for them


Fixed Typographical Error in guide/english/cloud-development/azure/index.md

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

thank you @Manish-Giri :+1:


Adding explain debug.owl

Adding check to explain debug.owl and having pipeline fail right afterwards.

@nicolevasilevsky bring up at QC call in conjunction with the complicated  chromosomal diseases issues


Add windows support for fs

Make opendal works on windows.
Only fs needs some changes and tests. Other services should work now.

Hi! I just noticed that windows pathnames seem completely invalid. normalize_path seems to expect a unix style file path. This will always add a / in front of the root path. This makes it hard to use on Windows at all.
I would be happy to contribute to making this work on Windows. However, I would like a little bit of direction before I start doing that.
I think the biggest issue is that the normalize_root function doesn't work on Windows.

Is this a correct assumption?
How would you like to see this work on Windows?
Why did you opt not to use the Path type which already handles a lot of this out of the box?

I would be happy to contribute to making this work on Windows.

Thank you so much for your attention and participation.

Is this a correct assumption?

No, normalize_root only works well on UNIX platforms. That's why we have this issue.

How would you like to see this work on Windows?

normalize_root should consider C:/ or D:/.

On windows platforms, fs's root must start will a valid disk name like C:/, D:/.
All \ should be replaced by /. So the final root will be C:/path/to/root/.
Object path should represent in path/to/file instead of path\\to\\file to ensure it's always the same on different platforms.

Why did you opt not to use the Path type which already handles a lot of this out of the box? (Including network drives etc)

Because OpenDAL needs to work well with different services and make sure they work like the same one. And on storage services like s3, gcs, file a/b/c is different from file a\b\c. So we can't depend on Path to build the request path.
And only local fs will be affected by Path construction, we don't need to introduce it for object storage services.

I understand why OpenDAL doesn't use Path throughout the library. But I think that for the fs backend specifically, it would make more sense to use it. Only in the internals of that backend (and maybe in the Builder::root?). The std::fs::* functions already all use Path anyway. That way you can deal with all the different weirdness of different filesystems paths out of the box.
So the user still uses String but this is converted to a Path in the fs backend. Paths returned by fs backend are converted from Path to normalized strings again. WDYT?

So the user still uses String but this is converted to a Path in the fs backend. Paths returned by fs backend are converted from Path to normalized strings again. WDYT?

Sounds good to me. Let's have a try.

Thanks @baszalmstra, this issue has been fixed.


changed templating + annotation in pod template

this ensures the ueransim fn is providing the right ctx for NAD/specialization

/approve
/lgtm


[Edge] Graphical text artifacts

See https://github.com/phetsims/graphing-lines/issues/60, and the resistivity in resistance-in-a-wire, e.g.:

It seems Edge (at least Canvas and in the console) treats a number of embedding-mark patterns as (incorrectly) needing to be rendered with a unicode "box", but when rendered with Canvas they don't seem to take up space. Thus the awkward/clipped unicode box, depending on character dimensions.
A good example is [LTR]....[POP][LTR] will look like ...☐. Taking off the initial or trailing [LTR] will cause the box to go away.
As a general solution, simplifying embedding marks for displayed strings should do the trick, and this issue almost always comes up using StringUtils.format. Commit will patch this to simplify embedding marks.

Assigning to @jbphet for review.

Example:

I reviewed the code and tested on Resistance in a Wire (RIAW) and the issue has indeed gone away.  This is a fairly elaborate workaround, so I added a note about potentially removing it at some point in the future to the comments in the file.  Overall, looks like it works, so I'll close this and incorporate it into the upcoming RIAW release.

@pixelzoom suggested this could be moved to Scenery. Reopening for discussion.

My reasons for suggesting that this be moved to scenery are:
(1) It's not specific to StringUtils.format, the problem can occur by concatenating strings using + operator.
(2) The current implementation greatly increases the complexity of StringUtils.
(3) The current implementation requires the programmer to call StringUtils.simplifyEmbeddingMarks for any text concatenated using the + operator.
In Skype, @jonathanolson noted: It may be needed complexity, but isn't free (having to store both your provided "text" value, and the internally-used "text" value with simplified embedding marks)

3/3/16 dev meeting consensus: move to scenery.

@jonathanolson will additionally work with @phet-steele to submit a bug report to edge.

Moved to Scenery.
@phet-steele, I've also added a test case that shows the bug on Edge (http://phetsims.github.io/scenery/tests/browsers/edge-embedding-marks.html).
Can you submit a bug report to Microsoft for Edge?

@jonathanolson report made here: https://connect.microsoft.com/IE/feedback/details/2457310/edge-embedding-mark-patterns-rendered-incorrectly

@phet-steele, I can't see the images in the issue. Do they need to be attached separately? Maybe it just doesn't let me see images since I didn't create the issue?

@jonathanolson I knew you would notice! The site said it could take up to an hour for them to appear.

The site lied!
Marking as deferred, MAY be able to remove the workaround when it is fixed in the browser (at least if we can detect newer versions).

New url for report: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/6831905/

This came up during the developer meeting today, and I couldn't immediately reproduce on the latest Edge (Edge/16.16299 in the user agent string). It may happen on other devices however. Can we check to see if this still occurs?

@jessegreenberg noted that removing the workaround for this issue tripled (!) the frame rate for molecules-and-light, so if we can remove it (for newer Edge versions) that would be a large benefit.

@jonathanolson this is still buggy (also in Edge/16.16299). Reminder to test these two links to know for sure:
http://phetsims.github.io/scenery/tests/browsers/edge-embedding-marks.html
https://www.colorado.edu/physics/phet/dev/html/graphing-lines/1.1.1/graphing-lines_en.html?screens=2 (slope-intercept equation)

Verified. I see artifacts in Microsoft EdgeHTML 16.16299 with https://www.colorado.edu/physics/phet/dev/html/graphing-lines/1.1.1/graphing-lines_en.html?screens=2&rootRenderer=svg
If the problem is with Text, could we move the workaround to scenery/Text.js instead of joist/Sim.js? Maybe we will still get a performance benefit if we don't render the whole sim with canvas.


Add Ryan Levick as an RC

I am nominating or self-nominating a Recognized Contributor.
Name: Ryan Levick
GitHub Username: @rylev
Projects/SIGs:

Component Docs

Nomination
I nominate Ryan because of his many contributions to Wasmtime, wasm-tools, wit-bindgen, and other projects.
Optional: Endorsements

Bailey Hayes  (@ricochet)

[x] I have read and understood the qualifications for a Recognized Contributor

We discussed this in today's TSC meeting, and all agree that your contributions are worthy of recognition in the BA. Thank you for all the hard work!
@rylev, to finalize the addition, please send an email to<EMAIL_ADDRESS>to let us know which address to use for communicating with you as a Recognized Contributor, and to confirm that you accept the nomination.
That address will be added to our RCs mailing list, which receives community and project updates every few weeks or so.
Once we've received that email, we'll add you to the mailing list and merge this PR. Thank you!

We've received Ryan's email address and added him to the RCs mailing list, and will now merge this PR. Welcome as an RC, Ryan!


Running NANOGav 9-yr data tutorial notebook yields different results

My operating system name and version and system architecture:
$ lsb_release -a
LSB Version:	:core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
Distributor ID:	CentOS
Description:	CentOS Linux release 7.8.2003 (Core)
Release:	7.8.2003
Codename:	Core

$ hostnamectl
...
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-1127.10.1.el7.x86_64
Architecture: x86-64

Running Python 3.7
Numpy version: 1.18.5 (which is not the same as the version 1.16 in the requirements.txt file)
In using nanograv/enterprise git # f66648f, the NANOGrav 9-yr data reduction tutorial notebook results in different results than the ones that comes with the notebok.
The histogram looks less skewed towards lower values of log10_A_gw compared to the original (I had to use density=True instead of normed=True in the call to PLT.hist()). The upper limit estimated is also correspondingly different (less tight than the original). See attached screenshots. Note that the percentile() function in numpy has undergone a change between version wherein it now (in v1.18.5) requires q to lie between 0-100 (as percent), whereas it was expecting between 0-1 (as fraction) in v1.16. So I set q=95.0  instead of q=0.95 . If we rule out that the change in numpy has to do anything with these non-matching results, my guess was that there must be some difference in the pulsar selection/properties between the original and my run. I did see some pulsar related warnings whose screenshot is also attached.

It was suggested that the clock files getting used may not have been identical.
I see the NG-9yr data paper lists TT(BIPM) as the clock file, which is the same as what I found in the .par files. I assume if a psr is initialized without explicitly setting clk=, it defaults to what's in the .par file. If that's the case, I expect it to be using identical clock files between my run and the tutorial. So not sure why the difference arose. Just to be sure, I ran the notebook again by explicitly setting clk=TT(BIPM) in the call psr = Pulsar(p, t, ephem='DE421', clk='TT(BIPM)')

But it doesn't seem to have changed the results substantially, and is consistent with my previous run, which is different from the NG-9yr results as before.

Although unlikely to be the reason for this difference, is it possible that there was a seed set for the MCMC sampling for the NG 9-yr results that could be used here to produce identical results?