#167399298 built user registration endpoint

What does this PR do?
It creates a user registration endpoint.
Description of Task to be done?

It sets up the server
It creates authentication route file and specifies the user registration route.
It specifies the registration route in the app.js file
It creates a user registration controller for registering the user.
It encrypts a submitted password during the registration.
It creates dummy data for being used in the test

How should this be manually tested?

Start the Server and POSTMAN.
Browse the following endpoint route: localhost:3000/api/auth/signup.
Submit the required information with POST method.
Check if the validations work once you don't submit any of the required information.
After passing the validations, you should receive a 201 HTTP Status Code along with the information that you have submitted.

This looks good bcs this endpoint is working well as I tested it. Moreover You have used the same variable naming conversion.

Good work bro, I thought it would be better if we could version our APIs like "/api/v1".

Thanks! I'm gonna work on that.

Good work bro, however, there is a simple misspelling on where you are validating email. check line number 17. I've pointed the mistake therein you codes

Also, I was suggesting that we include a token during sign up and reduce the token payload to include only id and user email.

Good work bro, I thought it would be better if we could version our APIs like "/api/v1".

I'm gonna implement that!

Thanks! I have implemented your feedback.


Stevia Package Version Differences Causing Issues

When working in the example project of YPImagePicker, it uses the Swift Package Manager Stevia 5.1.1. This is causing issues when using YPImagePicker through cocoapods in others projects because it uses 4.7.3 but the example is using SPM 5.1.1.
This mainly creates confusion and forces the developer to know which methods are supported in 4.7.3 and which are in 5.1.1 when working with this library.
Write Stevia code that uses methods from 5.1.1 but not 4.7.3.
An example is button.fillHorizontally(padding: 30)
Pull in the project through cocoapods and see that build compilation fails because the project is using methods that does not exist in 4.7.3.
I recommend to remove cocoapods complete from the project, there is no reason for developers not to start using both at the very least. I know it is not easy to get away from cocoapods since a lot of old libraries haven't moved yet, especially libs that haven't had support in some time.

Still a lot of people use cocoapods (so am I) and in our team we don't use SPM because of VPN issues. SPM is too automatic for us.
So I recommend to wait until apple make SPM more effective and convenience.

@gintechsystems please try https://github.com/Yummypets/YPImagePicker/releases/tag/5.1.1 and tell if it build ok with SPM or cocoapods.

@NikKovIos I will try that and let you know.
Thanks for clarifying your issues with SPM, I was not aware of those. I am still using cocoapods myself as SPM seems to be very specific about versioning too and you can't easily use a forked version of a library.

@gintechsystems also SPM is a big problem if you haven't internet connection or it is slow.

Yeah you are correct, I personally wish Stevia would allow for cocoapods still. They dropped support to early!

@gintechsystems I've made a PR today https://github.com/freshOS/Stevia/pull/163 Give a like to it ;)

I gave it a like, you said one person did it why don't you use that version in the picker for now until Stevia adds back support? Are you concerned about that person keeping the lib up to date?

@gintechsystems because his repo is outdated too. Now I've bringing back old versions of Stevia for cocoapods and SPM. Check new release description.

I see. Lets hope Stevia adds back support for cocoapods. I think your listed reasons are fair enough for them to do it. I subscribed so I will be watching the thread as well.

@gintechsystems open new issue if find problems.


Powershell script to help setup Map Kit

Create a Powershell script to help setup the Map Kit project / source code.

If/when creating Linux/Mac, create a parallel bash script.

If/when creating Linux/Mac, create a parallel bash script.

Done!


ClipboardItem data DOMString support usage document

Document showing how to enable and use ClipboardItem data DOMString support in Chromium-based browsers.

@microsoft-github-policy-service agree company="Microsoft"


Expose private items

Is there a way to use some private items from this crate?
Some macros may tweak (or re-define) some structures from syn but still re-utilize other items and private functions from it.
I wouldn't know if an alternative branch would be better, but I'm currently using a "patched" version of syn: https://crates.io/crates/syn-pub-items
Thanks in advance, and for your work on syn!

All of the items in https://github.com/swfsql/syn/commit/76636a6f02e73760b2bf75bd1f9579d9b6b76cc1 and https://github.com/swfsql/syn/commit/f8cf358ff569537da039cbfd77ce7bbdba320a75 are private intentionally and we can't provide a backward compatibility guarantee for them. Forking is fine, or copying out whatever private things you need into the macro crate.


Clasp push does not update remote code

Please search existing issues before creating a new one.
DON'T DELETE THIS! FILL THESE SECTIONS OUT!

Expected Behavior
Making a change to the code and pushing it remote, it should update after a push
Actual Behavior
Pushing once does not reflect updated code, it needs a second push to be seen.
Steps to Reproduce the Problem

Make changes to code.js, save
Run clasp push, confirms push
Reload script, change is not seen
Run clasp push, confirms push
Reload script, change is seen

Specifications

Node version (node -v): 11.6.0
Version (clasp -v): 2.0.1
OS (Mac/Linux/Windows): OSX 10.12.6

Official Google™ solution: alias clasp push to clasp push && clasp push

Official Google™ solution: alias clasp pushffs to clasp push && clasp push

Does that actually works?

running 'clasp push' twice in a row just worked for me. It's a workaround.

Er, I thought it was a workaround. It doesn't - running push twice still doesn't help.

@erickoledadevrel Any update on this issue, is the fix expected to come soon ?

@erickoledadevrel just tried using clasp but I am unable to push any changes. Is there any update on this issue? It seems like a very serious issue if people can not push changed code?

I just started using clasp and have yet to have it work successfully, so it could be that I'm doing something wrong, but it appears to be this issue.

I used clasp create to create a standalone project
Copied files into the project directory
Attempted to use clasp push
Terminal shows a list of files and "Pushed 56 files." so it appears to have been successful
When I open the GAS project in my browser, only the default Code.gs is there and the manifest has not been updated

This appears to make clasp pretty useless :(

I also just tried with no success :(

I also just tried with no success :(

For me clasp was working for a few deployments, then it stopped pushing the changes. When I reload the online editor, it still has the old code, If i pull the code back, I am pulling back the old code to the local project. :(

Greenfield project still exhibiting this behavior in Sept.

In my case I copied the code from the Code editor (visual studio code) and pasted it into the google code editor, and then I realised there was an error on the .js . For that error I could not save the changes on google editor. So I just corrected the mistake and I could save it. That was the reason when running  'clasp push' that seems to push it well, but didn't make the changes. It just could't be saved  on google just for a mistake in the code.

Hello there! I had the same problem. I figured out this was because I had an opened tab in my browser pointing to my Apps Script project.
If you also have such a tab, try closing it and pushing the code again.
Hope this helps.

I think for me I found the issue after using trying clasp version "YOUR_VERSION_STRING". I got a console message to enable API access. Once I enabled that I was able to make pushes. It's funny because I was able to clone and pull just fine.
So this is the Settings URL and then make sure that "Google Apps Script API Access" is on.

I think for me I found the issue after using trying clasp version "YOUR_VERSION_STRING". I got a console message to enable API access. Once I enabled that I was able to make pushes. It's funny because I was able to clone and pull just fine.
So this is the Settings URL and then make sure that "Google Apps Script API Access" is on.

worked for me. thanks

I had the same problem and I tried all suggestions here, but no success. So I changed the main file extension to ".gs" and clasp push worked.

I had the same problem...
clasp push && clasp push doesn't work.
Is there any progress on this issue?

I had the same problem...
clasp push && clasp push doesn't work.
Is there any progress on this issue?

One thing I would advise is to look at the error message you got from your CLI. That can help diagnose the problem. Before using files you must have logged in using npm clasp login and have cloned files from your apps script using npm clasp clone to the root folder of your project When you push files to Google Apps Script, you ought to see a pushing files message when you're done. If successful, you should able to see a list of files that are pushed from your directory as well as a message telling you your files have been pushed successfully.

As @jiro2017 said, I would make sure you aren't getting any error messages in your CLI. I thought clasp push was not working because my remote editor was not updating (even though the files appeared to have been pushed successfully on my terminal). But when I scrolled up, I saw that I had a syntax error.

Hi there
Was working on extension for Google sheets and accounted a problem with cloned project when I couldn't push new changes to Apps Script via clasp.
I'm quite ashamed to spend a bit of time on it, but @davidpedrero and @jiro2017 comments here helped me: there was only an issue with access as "User has not enabled the Apps Script API". Toggling it as recommended at error message worked like a charm.
But nonetheless, I'd like to say that failing push command with  error messages on the top AND a list of all project files at the bottom with closing Pushed N files is extremely inconvenient. CLI user will have limited height of terminal and whenever list of files exceeds this height (for me it took 7 files of 27 existing in project, for example) the only thing that he'll notice on completion of failed command is a list of all files with "Pushed" statement as if it was pushed successfully.


Tabs: support "select" output

Tabset should have the select output (event) which should be fired before a new tab is selected. Event's payload should have:

id of a tab to be selected
id of the actual tab
preventDefault() method to abort tab change.

Ref: http://v4-alpha.getbootstrap.com/components/navs/#events (but IMO we should implement only show)

Opened the pull request, the only thing is that I had to rename 'select' event to 'change' event as there is already public 'select' method


Add: KCCG-TV2

Channel Name
KCCG-TV2
Alternative Names (optional)
No response
Network (optional)
No response
Owners (optional)
No response
Country
US
Subdivision (optional)
US-MO
City (optional)
Kansas City
Broadcast Area
s/US-MO
Languages
eng
Categories (optional)
legislative
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://www.kcmo.gov/city-hall/departments/city-manager-s-office/city-communications-office/channel-2
Logo
https://www.kcmo.gov/Project/Contents/Main/_gfx/cmn/logo-footer.png
Notes
Streaming URL:
https://youtu.be/eUtzSJHMYsI

https://iptv-org.github.io/?q=KCCG-TV2


Environment variables not being substituted

Hi,
I'm trying to use your Github Action to replace two environment variables with the value of Github Secrets in a .sh file before building and pushing a Docker image. However, the variables are not being substituted. Instead they are left blank. The filename that contains the environment variables that need to be substituted is named 'entrypoint.sh' and is located in the root of my repository. I've setup your Github Action as follows:
jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - name: Variable Substitution
        uses<EMAIL_ADDRESS>        env:
          STEAM_USERNAME: ${{ secrets.STEAM_USERNAME }}
          STEAM_PASSWORD: ${{ secrets.STEAM_PASSWORD }}
        with:
          fail_on_missing_variables: "true"
          search_input: |
            {
              "files": ["entrypoint.sh"],
              "depth": 1
            }

Source: https://github.com/Freekers/docker-ggcombatcarnage/blob/main/.github/workflows/automation.yml
And the entrypoint.sh file containing the environment variables that need to be substituted looks like this:
#!/bin/bash -ex

[ "$UID" != 0 ] || {
    mkdir -p ~user/Steam
    chown user: ~user/Steam
    runuser -u user "$0" "$@"
    exit 0
}

GAMEDIR="$HOME/Steam/steamapps/common/Gas Guzzlers Combat Carnage/Bin32"

cd "$HOME"
STEAMCMD="./steamcmd.sh +@sSteamCmdForcePlatformType windows +login ${STEAM_USERNAME} ${STEAM_PASSWORD} $STEAMCMD"

# eval to support quotes in $STEAMCMD
eval "$STEAMCMD +app_update 596620 +quit"

rm -f /tmp/.X1-lock
Xvfb :1 -screen 0 800x600x24 &
export WINEDLLOVERRIDES="mscoree,mshtml="
export DISPLAY=:1

cd "$GAMEDIR"

[ "$1" = "bash" ] && exec "$@"

wine ./GGDedicatedServer.exe

Source:  https://github.com/Freekers/docker-ggcombatcarnage/blob/main/entrypoint.sh
Why aren't ${STEAM_USERNAME} and  ${STEAM_PASSWORD} being substituted for their values stored as Github Secrets?
Thanks

Hello,
Hmm interesting, let me double check it and get back to you by the end of today.

Hey, just took a quick look...
I think you are missing just a step before the action:
    steps:
      - name: Checkout
        uses: actions/checkout@v2

Git hub action just runs a docker container and executes your command. But it needs to checkout your code first ... unfortunatelly this doesn't happen automatically, you have to tell github actions to check out your code.
Can you please try again and let me know if it works ?
Full example of your github action:
name: Build and Push Docker Image
on:
 push:
 schedule:
    # * is a special character in YAML so you have to quote this string
    - cron:  '11 11 1 * *'

jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: Variable Substitution
        uses<EMAIL_ADDRESS>        env:
          STEAM_USERNAME: "${{ secrets.STEAM_USERNAME }}"
          STEAM_PASSWORD: "${{ secrets.STEAM_PASSWORD }}"
        with:
          fail_on_missing_variables: "true"
          search_input: |
            {
              "files": ["entrypoint.sh"],
              "depth": 1
            }
      - name: Login to DockerHub
        uses: docker/login-action@v1
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}
      - name: Build and push
        id: docker_build
        uses: docker/build-push-action@v2
        with:
          push: true
          tags: freekers/docker-ggcombatcarnage:latest,freekers/docker-ggcombatcarnage:${{ github.run_number }}

Also, make sure to use the latest version v1.2.2 ^^

Thanks for the quick reply and your help so far, I appreciated it 👍
I implemented the checkout step and updated the version of your Github Action, but sadly it's still substituting them with blanks.
Here's the output of my Docker container:
eval './steamcmd.sh +@sSteamCmdForcePlatformType windows +login    +app_update 596620 +quit'

As you can see there are two white spaces between +login and +app_update where the username and password should be.
Any ideas :) ?
Thanks!

Try also with uses like this (using "uses"):
- name: Test action
        uses: ./
        env:
          COOL: "test value"
          blacklisted: "blacklisted"
          whitelisted: "whitelisted"

to make sure you are on the root directory.

I found the issue... and it has nothing to do with your code/action.
Apparently the docker/build-push-action@v2 step checks out the code by itself automatically, unless you specifically tell it not to do so. So what was happening was is that I checked out the code using actions/checkout@v2, did the variable substitution, but then the docker/build-push-action@v2 step would checkout the code again and basically render the previous steps useless.
To fix this, all I needed to do was add context:  to the docker/build-push-action@v2 step, which basically tells it not to checkout the code again, but build the image using the code that's already checked out. The automation.yml looks like this now:
name: Build and Push Docker Image
on:
 push:
 schedule:
    # * is a special character in YAML so you have to quote this string
    - cron:  '11 11 1 * *'

jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: Variable Substitution
        uses<EMAIL_ADDRESS>        env:
          STEAM_USERNAME: "${{ secrets.STEAM_USERNAME }}"
          STEAM_PASSWORD: "${{ secrets.STEAM_PASSWORD }}"
        with:
          fail_on_missing_variables: "true"
          search_input: |
            {
              "files": ["entrypoint.sh"],
              "depth": 1
            }
      - name: Login to DockerHub
        uses: docker/login-action@v1
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}
      - name: Build and push
        id: docker_build
        uses: docker/build-push-action@v2
        with:
          context: .
          push: true
          tags: freekers/docker-ggcombatcarnage:latest,freekers/docker-ggcombatcarnage:${{ github.run_number }}

Sorry for wasting your time on this, I'm still new to Github Actions.

@Freekers Don't worry about it. Happy it was solved ^_^


bosh upload release with insufficient local space

When the local disk has insufficient space and a 'bosh upload release' is run, the error received is a traceback complaining about lack of disk space, but it's not clear which system is out of space.
It would be useful if, instead of a traceback, the error would indicate that the local system was out of space.
The output was as follows:
# bosh upload release

Copying packages
----------------
ruby (cd102a7fe440fd9eaeee99c6bc460b06884cbda6) haproxy (917ceeaf9931e5c9e6921f61c5490be20a3051e6) dea_logging_agent (afa74c194ae7030e46961fabdb5c7984adcdb8ac) smoke-tests (e01d9d4046d95f59c66a7a47f8f0650ca6c5d487) postgres (b63fe0176a93609bd4ba44751ea490a3ee0f646c) buildpack_php (7ce5f94b4904cc67d9e5e964ffdab7f1572a7367) acceptance-tests (14abc1069a1941f08c2d4a44b21eaeeae1bf7e61) nats (cc6bda829a77ab2321c0c216aa9107aca92c3b1a) loggregator (63db903b803e215793789f7bdf98b561df37eb18) etcd (0171c102f5b67947021e271601122982607c9d59) sqlite (af44d44e58fffd069459cb63f6fcc37c6326e370) buildpack_ruby (dafbc4b72dfcdf5d19487dbcd5451d8cbe2e8866) login (edf41c9349e3eac12ef8a7a726570c0fecac5d03) golang (aa5f90f06ada376085414bfc0c56c8cd67abba9c) uaa (e95f22b7838e41bde03de3e10ffc5dddbfdfbd9a) nginx_newrelic_plugin (d3b2bdf36a2c5553e9fefcda0a93d0bed04c71c0) debian_nfs_server (aac05f22582b2f9faa6840da056084ed15772594) syslog_aggregator (4d4111ba19a8e7875184462d178fddb44fa87440) hm9000 (9595c4c0e16a261ccbeaea9b8edf6e87c3eaf159) buildpack_nodejs (bb0e4c1bb90effad1ffa50d2aa90e727a55039ff) cli (ec2ffd170251323e6ee11efbd8f5e61603aa6283) buildpack_cache (4ced0bc62f12dcaa79121718ca3525253ede33b5) libyaml (681bb455c35ef17cabbd41344f924cb61c2bb8e7) buildpack_java (08d7aa96c476559aa088a2e1f1c3fd812c36e2aa) cloud_controller_ng (41a73e0d71d88f9f29effdc1c6786425b2313b12) common (51c0a25512aa6e61c321a004e80ece95bf77e145) libpq (49cc7477fcf9a3fef7a1f61e1494b32288587ed8) collector (652024d837cb253df05e75ff0f500e4712bee659) gnatsd (3ade99da461f1744ad392da916afb1da5048b223) nginx (385ce4eca93c53c163ea82204a28e96d851bb65d) warden (5e6d50d31a878ee58e3fbfe397edd50a3877587b) buildpack_java_offline (546631e74a24465152b8553672ef2e30841afeaa) buildpack_python (d568479d7ef2a992f3e78a131e044ffe5a724b7b) metron_agent (e30b369f7640aa0ceedb43ec65d18ae6eb65e076) mysqlclient (8b5d9ce287341048377997a9b3fe4ff3e6a1c68f) gorouter (626050640d8da78ffa2724b34f1322115442e21d) rootfs_lucid64 (053c40914ab425794131d7d2c57943588d1e80be) /usr/lib/ruby/1.9.1/fileutils.rb:1372:in `copy_stream': No space left on device - write (Errno::ENOSPC)
    from /usr/lib/ruby/1.9.1/fileutils.rb:1372:in `block (2 levels) in copy_file'
    from /usr/lib/ruby/1.9.1/fileutils.rb:1371:in `open'
    from /usr/lib/ruby/1.9.1/fileutils.rb:1371:in `block in copy_file'
    from /usr/lib/ruby/1.9.1/fileutils.rb:1370:in `open'
    from /usr/lib/ruby/1.9.1/fileutils.rb:1370:in `copy_file'
    from /usr/lib/ruby/1.9.1/fileutils.rb:477:in `copy_file'
    from /usr/lib/ruby/1.9.1/fileutils.rb:396:in `block in cp'
    from /usr/lib/ruby/1.9.1/fileutils.rb:1515:in `block in fu_each_src_dest'
    from /usr/lib/ruby/1.9.1/fileutils.rb:1531:in `fu_each_src_dest0'
    from /usr/lib/ruby/1.9.1/fileutils.rb:1513:in `fu_each_src_dest'
    from /usr/lib/ruby/1.9.1/fileutils.rb:395:in `cp'
    from /var/lib/gems/1.9.1/gems/bosh_cli-1.2839.0/lib/cli/release_compiler.rb:58:in `block in compile'
    from /var/lib/gems/1.9.1/gems/bosh_cli-1.2839.0/lib/cli/release_compiler.rb:51:in `each'
    from /var/lib/gems/1.9.1/gems/bosh_cli-1.2839.0/lib/cli/release_compiler.rb:51:in `compile'
    from /var/lib/gems/1.9.1/gems/bosh_cli-1.2839.0/lib/cli/commands/release/upload_release.rb:61:in `upload_manifest'
    from /var/lib/gems/1.9.1/gems/bosh_cli-1.2839.0/lib/cli/commands/release/upload_release.rb:39:in `upload'
    from /var/lib/gems/1.9.1/gems/bosh_cli-1.2839.0/lib/cli/command_handler.rb:57:in `run'
    from /var/lib/gems/1.9.1/gems/bosh_cli-1.2839.0/lib/cli/runner.rb:56:in `run'
    from /var/lib/gems/1.9.1/gems/bosh_cli-1.2839.0/lib/cli/runner.rb:16:in `run'
    from /var/lib/gems/1.9.1/gems/bosh_cli-1.2839.0/bin/bosh:7:in `<top (required)>'
    from /usr/local/bin/bosh:23:in `load'
    from /usr/local/bin/bosh:23:in `<main>'

Agreed. Good suggestion.

Geokala, when you got this error did you determine if the disk space issues was on the local box or the director?

Hi cwb124,
It's been a while now so my memory may be faulty but I think it was the local machine (the one on which the bosh CLI was being run, not the director).

Agreed, this error comes from the local system running out of space.
Since this issue, we have released a new version of the BOSH CLI (found in cloudfoundry/bosh-cli). It handles error reporting slightly differently (and hopefully better in this situation), so I'm going to close this issue in this repo.
Please feel free to create new issues in the bosh-cli repo, or join us on cloudfoundry#bosh slack for more help or guidance when starting to use the new CLI!


Handle rate limit

Did you consider handling GH API rate limits with exponential backoff?
Alternative idea: run the tool on schedule and collect data in chunks and combine later. Or collect data incrementally. Makes sense?

Hi @prein
The current solution if you're running into rate limits is to run on a shorter time-frame, or to filter out misc repos.
What's the maximum you've been able to run with? 7 days?
Full historical data is available for actuated customers stored in a performant database, with insights added.
https://docs.actuated.dev/dashboard/


Update reference_algorithms/prize_qualification_baselines/README.md

Fix a presumable typo - I'm assuming the self-tuning section ought to refer to the self_tuning directory.

Thanks for catching this. Will fix on dev.


Error PHABRICATOR_USER should be defined

Hi,
I have an error, when pushing my commits from local repo to server. It seems like this
$git push
<EMAIL_ADDRESS>password:
Counting objects: 19 done.
Delta compression using up to 2 threads.
Compressing objects: 100% (5/5), done.
Writing objects^ 100% (10/10), 656 bytes | - bytes/s, done.
Total 10 (delta 3), refused 0 (delta 0)
remote [2015-01-21 17:20:35] EXCEPTION: (Exception) usage: PHABRICATOR_USER sho
ild be defined! at [/scripts/repository/commit_hook.php:36]
remote:
To spimenov@phabricator.tsi.ru:/opt/git/tts.git
! [remote rejected] 4.5 -> 4.5 (pre-receive hook declined)
error^ failed to push some refs to 'spimenov@phabricator.tsi.ru:/opt/git/tts.git'

I have a virtual server with git, before i install phabricator i could normally do push/pull, checkout, etc.
Then I install phabricator (the same server with my git repos) and use configuration guide and advanced guide, at the and i have web phabricator with no issues, i config outbound emails and some other features. Then I started with deffusion
I configure daemon-user and vcs-user to use ssh protocol. Maybe important, I start SSH to phabricator on 222 port, and 22 for my putty client.
I press new repository. press Import an Existing External Repository, type-GIT, name - TTS, callsign - T
Remote URI ssh://vcs-user@phabricator.tsi.ru:222/opt/git/tts.git (I check, that from my putty I can login with vcs-user and can do this git command on 222 port without password (i install assymetric rsa)). In Authentication tab I choose correct private key for my vcs-user
Then I continue to config it. Hosting Hosted -> Host on phabricator, ssh -> read/write. Storage Path /opt/git/tts.git (is it right??).

Finally I can see all src, tags, branches and commits, etc.
But when I try to push from my local I have an error. What can it be?
PS my pre-recieve-phabricator.d is empty (except of README), and I dont need custom hooks now.
Thank you and sorry for my english )

When hosting a repo in phabricator, the uri should be something like
ssh://vcs-user@phabricator.tsi.ru:222/diffusion/T/tts.git - copy it from the repository's page in phabricator.
Password authentication should also not be available, if hosting is configured correctly - only ssh keys configured in phabricator should work.
It looks like you're connecting using the wrong ssh daemon.
phabricator installs it's hook in the hosted repo, which is why it's trying to run even though the ssh connection is passing through it.

When I do this

Then I continue to config it. Hosting Hosted -> Host on phabricator, ssh -> read/write. Storage Path /opt/git/tts.git (is it right??).

My clone ssh automatically changes to:
git clone ssh://vcs-user@phabricator.tsi.ru:222/diffusion/T/tts.git
When storage is /opt/git/tts.git
Unfortunately, I cannot understand what does ssh://vcs-user@phabricator.tsi.ru:222/diffusion/T/tts.git, becouse I have no /deffusion folder on my server root. On the other hand I can see al code and brunches, becouse of my storage is in /opt/git/tts.git where my git repo locates. So the question, what does this ssh link means?
How can I check if my ssh daemon config correctly? I try to do some clones from the standart command line, and ssh daemon for vcs-user and daemon-user on 222 port works well.

/diffusion/ is a virtual path, that is managed by phabricator; It only works when the sshd is set up correctly.
https://secure.phabricator.com/book/phabricator/article/diffusion_hosting/#troubleshooting-ssh can help you debug the issue.
Specifically, try ssh -T -p 222<EMAIL_ADDRESS>and see if you get the right message.

Ok, I try it, but have no answer. It's meen, i suppose, that i have wrong ssh config. Hope, that you can help me a little.

The first question is:  ssh -T -p 222<EMAIL_ADDRESS>- from what user i should exec this command? I've tried from my root user.

If I understand right, when I connect to 222 port, phabricator-ssh-hook.sh should automatically start ssh-auth script. I've tried to start it manually and result was

$ ./phabricator-ssh-hook.sh vcs-user
No keys found.

I could not understand this "To authenticate over SSH, users should add SSH Public Keys in the Settings screen." This is about web phabricator page. Now I have 5 web accaunts, and no keys. I can generate key-pair, or upload, but I couldn't understand how my linux vcs-user ssh certs correspond to my web accaunts certs.

I can generate key-pair with web form, and save public part. But where should I past it?

UPD.
Hmmm... I understand the terrible mistake. When I started to config ssh to phabricator, I manually generate pair of rsa keys and install them to my linux server for vcs-user. I think that I need installed certeficate to connect via ssh. Now I understand that only certificate that i need I should generate via phabricator web form. I delete my manually generated keypair, then i create vcs-user accaunt on my phabricator.tsi.ru and generate new keypair (I can download private key, but can't understand, where i should install this private part of keypair)
Now, I have
[vcs-user@phabricator libexec]$ ./phabricator-ssh-hook.sh vcs-user
command="'/opt/phabricator/phabricator/bin/ssh-exec' --phabricator-ssh-user 'vcs-user'",no-port
forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa
AAAAB3NzaC1yc2EAAAADAQABAAABAQC7q8E6A7s72wwQx+JGTRmVS7cxC35ZgEm6yotO3oTvI
BkKKWO+4IEpKLLDWDhUj3vL3xLxv1jApATZp4GC+VhUJqvHvAkS2xyGy22IJTSkMad8/OmhwJIw
HdZfNHTlDJsbg4MQCDh43K50M32L1CTwWhkNiQ25ETRiV4sPT7cyaAQQsNDI/lxu10oqVSnx0ql6
Y0pHd8jahnE2Q1r65ogLWm0cUqS/QyuIocGBSNSh0PAofMlsxoXnGkH07IJhMpO1PKgPvtaK8snN
+aGFp6WOyQgaOxnEdtbIuWwWcBinOJtdqckd+6KCOW1OnugZFAGcuRvI3ryLUuiyFl1j

and
[vcs-user@phabricator libexec]$ ssh -T -p 222<EMAIL_ADDRESS>Permission denied (publickey,keyboard-interactive).

When connecting to phabricator's sshd, you're trying to log into phabricator, using ssh keys.
Your private key goes in the computer you're connecting from, and the public key goes in phabricator, in the account you're trying to connect to.
You can specify a specific key for ssh to use with -i private-key-file (See http://askubuntu.com/questions/30788/does-ssh-key-need-to-be-named-id-rsa for more options).
vcs-user is not a phabricator user, and should not have any keys configured. The linux certs and users are not related to the phabricator certs and users.
Since you get the error "keyboard-interactive" from ssh, you've probably didn't set the right sshd configuration - the right configuration prevents password identification.

Finally I finish this battle.
Yeah, the problem was so easy, but as for me, https://secure.phabricator.com/book/phabricator/article/diffusion_hosting/#troubleshooting-ssh wasn't clear. It tells nothing about how to use "settings -> ssh public keys" in web form and where should I install private part of this key.
I understand, that phabricator hooks connection with specific script, than calls ssh-auth php script, then call ssh-exec php script. In this scripts we can see. that it automatically use phabricator internal scripts. But in docs I can find only few words about this principals.
Finally in my local repo I use clone command like git clone ssh://vcs-user@phabricator.tsi.ru:222/diffusion/T/tts.git, I use git Bash and can't specify key with -i private-key-file, but when I copy my id_rsa key to HOME/.ssh folder (git home I mean, "env" command helps me), it takes keys automatically (the name should be "id_rsa").
Maybe it is useful to modify documentation, i don't know.
Thank you very much for support!


iosevka-comfy: 1.3.0 -> 1.4.0

Description of changes
https://github.com/protesilaos/iosevka-comfy/releases/tag/1.4.0
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 259054 run on x86_64-linux 1

12 packages failed to build:

iosevka-comfy.comfy
iosevka-comfy.comfy-duo
iosevka-comfy.comfy-fixed
iosevka-comfy.comfy-motion
iosevka-comfy.comfy-motion-duo
iosevka-comfy.comfy-motion-fixed
iosevka-comfy.comfy-wide
iosevka-comfy.comfy-wide-duo
iosevka-comfy.comfy-wide-fixed
iosevka-comfy.comfy-wide-motion
iosevka-comfy.comfy-wide-motion-duo
iosevka-comfy.comfy-wide-motion-fixed

Result of nixpkgs-review pr 259054 run on x86_64-linux 1

12 packages built:

iosevka-comfy.comfy
iosevka-comfy.comfy-duo
iosevka-comfy.comfy-fixed
iosevka-comfy.comfy-motion
iosevka-comfy.comfy-motion-duo
iosevka-comfy.comfy-motion-fixed
iosevka-comfy.comfy-wide
iosevka-comfy.comfy-wide-duo
iosevka-comfy.comfy-wide-fixed
iosevka-comfy.comfy-wide-motion
iosevka-comfy.comfy-wide-motion-duo
iosevka-comfy.comfy-wide-motion-fixed

Thanks for testing and reporting back.


Video instance reference is kept in the agent and cannot be destroyed

After using NewRelicVideoStart the video node reference is saved in the scope of the new relic agent.
https://github.com/newrelic/video-agent-roku/blob/master/components/NewRelicAgent/NRAgent.brs#L58
Even when we remove nodes with a player view, the player instance is still existing and the video is still "alive".
Could you add a function for example NewRelicVideoStop that will clear this reference so the video component will be destroyed properly?

I added a PR with a proposal for the change.


chore: change project to monorepo for publishing @hawtio/react pkg

Fix #9

This moves the Hawtio React component into a workspace with project name @hawtio/react so that it can be published separately
Use tsup for building @hawtio/react
The application part based on CRA is moved to /app, which only serves as a test app for development

@phantomjinx @mmelko @joshiraez @jsolovjo These are the changes I'm going to apply to the project.


Crashing issue in the use of pistons on glass mirrors

Is it a mod compatibility issue?
No
If it's a mod compatibility issue, please provide the link(s) to the incompatible mod(s)
If you create a mirror with glass and push it with a piston, the game will crash.
Minecraft version
1.20.4
Describe the issue
To recreate the issue, simply create a glass mirror with flint and steel, then attempt to push and pull the mirror with a Piston/Sticky Piston. I did this multiple times with multiple crashes.

Sorry I misunderstood the format about the incompatibility section.

I cannot reproduce this issue. Can you post the crash report


Looping Broadcast Increament .

let success = 0
let error = 0
for (let x in data.users) {
Bot.copyMessage (data.users[x] , data.owner , body.callback_query.data.split(" ")[1] )
.then(options => { success += 1 })
.catch(err =>{ error += 1 })
}
console.log (success)
console.log (error)
Broadcast code i used . I want it like it should increment success & error.
Tried using .then() and .catch()  , but found its not working..

Question better suited for stackoverflow.


[Spark] Base merge schema evolution off set expressions, not source schema

Which Delta project/connector is this regarding?

[x] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[ ] Other (fill in here)

Description

Resolves #2300
This updates schema evolution in merging to use the target assignment columns and expression schema to determine the new target schema instead of the source schema. The current implementation seems to only support upserting use cases, where the source schema looks like the target schema. However when using custom set expressions, there's no requirement for this to be the case.
When auto schema migration is enabled and the target assignment column doesn't exist in the table, the column parts and the data type of the expression are used for determining schema updates, regardless of what the source schema is. For upserting cases, this works the same way, since the data types and assignment columns will match the source table. But it also supports more use cases where the source schema doesn't match the target schema.
How was this patch tested?

Updated two tests that were showing this use case didn't work, to show it now does work, and added one additional test for adding a new nested column in an update.
Does this PR introduce any user-facing changes?

Yes, supports more schema evolution use cases in merge

cc @johanl-db since you added the non-star schema evolution in https://github.com/delta-io/delta/commit/affd5774def34bc4d553aff805cd17afe7d57ea1

I actually considered this when implementing non-star schema evolution, the main concern was that schema evolution then becomes very error-prone as any typo will happily add a new column to the target:
MERGE INTO target
USING source
WHEN MATCHED THEN UPDATE SET userid = source.user_id

where the target already contains a column user_id which was misspelled as userid. This concern is actually the main reason schema evolution initially only applied to UPDATE SET * / INSERT * and not non-star action.
We could allow it but in my opinion (and others that I discussed this with) is that this would do more harm than good.
The following should enable the use case you describe on the other hand (using the example from https://github.com/delta-io/delta/issues/2300):
  spark.createDataFrame([["a"], ["b"], ["c"]], ["old"]).write.format("delta").mode("overwrite").save("merge-test")

  val df = spark.createDataFrame([["a", "1"], ["b", "2"], ["c", "3"]], ["first", "second"])
  val source = df.withColumnRenamed("second", "new")

  val dt = DeltaTable.forPath(spark, "file:/path/to/table/merge-test")
  (dt.alias("target").merge(df.alias("source"), "target.old = source.first")
      .whenMatchedUpdate(set = {
          "new": "source.new"
      })
      .execute()

Renaming the source column before merging has the advantage that the intent is explicit:
  val source = df.withColumnRenamed("second", "new")

I actually considered this when implementing non-star schema evolution, the main concern was that schema evolution then becomes very error-prone as any typo will happily add a new column to the target:
MERGE INTO target
USING source
WHEN MATCHED THEN UPDATE SET userid = source.user_id

where the target already contains a column user_id which was misspelled as userid. This concern is actually the main reason schema evolution initially only applied to UPDATE SET * / INSERT * and not non-star action.

Aren't all operations prone to typos? You could have a DataFrame with userid in it and do a UPDATE SET * and end up in the same scenario, not sure how this is any different. If someone is that worried about typos, they should be testing their queries or not enable automatic schema evolution (which is disabled by default so this is all already feature-gated).

The following should enable the use case you describe on the other hand (using the example from #2300):

That was a trivial example. In reality what we are doing is
set={'new.nested.field': complexExpressionInvolvingSourceAndTarget}

Getting the source to "look like" the target is non-trivial for our case without doing a pre join, which then just adds another whole join (really two since merge is two passes). And it provides no real benefit.
Additionally the current implementation has a fun side effect if you deviate from the "copy the exact field" (which is only one use case for merge)
(spark.createDataFrame([["a"], ["b"], ["c"]], ["old"])
    .repartition(1)
    .write
    .format("delta")
    .mode("overwrite")
    .save("merge-test")
)

df = spark.createDataFrame([["a", 1], ["b", 2], ["c", 3]], ["first", "second"]).repartition(1)

dt = DeltaTable.forPath(spark, "file:/path/to/merge-test")
(dt.alias("target").merge(df.alias("source"), "target.old = source.first")
    .whenMatchedUpdate(set = {
        "first": "source.second"
    })
    .execute()
)

spark.read.format("delta").load("merge-test").printSchema()
spark.read.format("delta").load("merge-test").show()

The output:
root
 |-- old: string (nullable = true)
 |-- first: string (nullable = true)

+---+-----+
|old|first|
+---+-----+
|  c|    3|
|  b|    2|
|  a|    1|
+---+-----+

Even though the target value I inserted was an integer (second), first is used as the data type to use for schema evolution, adding a string column, and then casting the integer I am inserting to a string. This seems much more problematic than worrying about typos.

Schema evolution allows adding columns/fields that are present in the source dataframe but missing in the table schema, the use case you are describing is different though since the field new.nested.field isn't present in the source in the first place.
You would need to explicitly add the column to the table beforehand:
DeltaTable.forPath(spark, "file:/path/to/merge-test")
  .addColumn('new.nested.field', dataType= <type>)
  .execute()

Relying on the merge clauses to define what the new schema instead of just the target/source schemas comes with some challenges:

It's a departure from the current definition of schema evolution, likely a breaking change.
The resulting schema is ambiguous: multiple clauses may introduce the same new column with different types,

Schema evolution allows adding columns/fields that are present in the source dataframe but missing in the table schema, the use case you are describing is different though since the field new.nested.field isn't present in the source in the first place. You would need to explicitly add the column to the table beforehand:

Yes that is the exact scenario I'm trying to fix since we have all the information we need to do the schema evolution automatically without manually adding the column beforehand. Again this assumes that upserting is the only use case for merge, and that is not the case at all. If that was the case then custom set expressions shouldn't be supported. The source table doesn't have to have anything to do with the target table schema wise.

Relying on the merge clauses to define what the new schema instead of just the target/source schemas comes with some challenges:

It's a departure from the current definition of schema evolution, likely a breaking change.
The resulting schema is ambiguous: multiple clauses may introduce the same new column with different types,

The code is simplified and all the existing tests pass, do you have an example you think will cause problems? The new behavior should be a superset of the existing behavior (beside from fixing the example buggy behavior mentioned in the last post). If you update/insert a field as is then it will use the schema as is as well.

User-facing change 1: Assigning to a column that isn't in the target or source now adds that column to the target table instead of failing:
target: key int
source: key int

MERGE INTO target
USING source
ON source.key = target.key
WHEN MATCHED THEN UPDATE SET new_column = source.key

User-facing change 2: Assigning to a column that exists in the source but not the target can now result in the column being added with a different type:
target: key int
source: key int, value string

MERGE INTO target
USING source
ON source.key = target.key
WHEN MATCHED THEN UPDATE SET value = source.value::int

Currently value is added to the target with type string, with your proposal it's added with type int.
I'm not too concerned about the first case as we're just making schema evolution more permissive (hopefully users don't rely on an error being thrown there). The second one could be breaking some use cases though.
The bigger question remaining is what should the resulting type be if there are multiple clauses introducing a new column?
If one is strictly larger than the other, then arguably we should pick the larger type and upcast the smaller one:
WHEN MATCHED AND condition THEN UPDATE SET value = source.value::int
WHEN MATCHED THEN UPDATE SET value = source.value::long

value should be added with type long
What if both types can be upcast to each others:
WHEN MATCHED AND condition THEN UPDATE SET value = source.value::timestamp
WHEN MATCHED THEN UPDATE SET value = source.value::timestampNTZ

Both timestamp and timestampNTZ are valid types for the new column value, how do we pick one? We could for example catch such a case and throw an error because the resulting type is ambiguous.
Similar with string which supports implicit cast to and from most other types:
WHEN MATCHED AND condition THEN UPDATE SET value = source.value::string
WHEN MATCHED THEN UPDATE SET value = source.value::date

Should value in the target table be a date or string?
If we can get a good answer for type reconciliation and get some confidence that the second user-facing change isn't going to break user workloads then that would clear the path forward for this change

User-facing change 1: Assigning to a column that isn't in the target or source now adds that column to the target table instead of failing:

I wouldn't consider this a breaking change, just a new feature. Something that wasn't possible before is now possible.

User-facing change 2: Assigning to a column that exists in the source but not the target can now result in the column being added with a different type:

Technically a breaking change, but I would consider this a bug fix. I can't imagine a reasonable person would expect this behavior, let alone rely on it.

The bigger question remaining is what should the resulting type be if there are multiple clauses introducing a new column?
...
If we can get a good answer for type reconciliation and get some confidence that the second user-facing change isn't going to break user workloads then that would clear the path forward for this change

I will add some tests case for this. Because it all uses the mergeSchemas helper with allowImplicitConversions=true, I would expect it would do type reconciliation to the smallest common type, but the tests cases will find out for sure.

So it looks like the current behavior is all based around Spark's implicitCast, which itself depends on the order of the types you're merging. Giving this, it seems like there's 4 possible options for the behavior of multiple expressions to the same new field:

Use the implicitCast behavior, ensuring to process all clauses in order, regardless of update or insert. This behavior is highly dependent on the two types for how it behaves, but it's what the current process uses for adding any new fields into the target table.
Use a method like you described of "upcasting" to the common type. I would need to see if there's any existing Delta or Spark helper to do something like this. This would be a little different than the implicit cast. For example merging an int and a long (in that order), would result in an int in the implicitCast method (casting the long to an int), but a long in an "upcasting" approach.
Use the first type seen for a given target column and then rely on the casting of any additional uses of that target column.
Check that all assignments to the same column are the same data type, and fail if not. Maybe the least ambiguous approach from a user perspective.

I added some unit tests showing the current behavior, which is mostly 1) but without the full ordering across both insert and update

The order of the clauses shouldn't have an impact on the resulting type of a column, that would be arbitrary. This rules out 1. and 3. and leaves 2., the more permissive approach and 4. the stricter one.
The issue with 4. and failing when the clauses use different types is that MERGE operations may start to fail:
source: float_col: float, new_column: double
WHEN MATCHED THEN UPDATE SET *
WHEN NOT MATCHED THEN INSERT (new_column) VALUES (source.float_col)

This is valid today and will insert new_column as double but would fail with approach 4.
It also leads to cases that have limitations that seem very arbitrary:
WHEN MATCHED AND condition1 THEN UPDATE SET new_column = 5 -- int
WHEN MATCHED AND condition2 THEN UPDATE SET new_column = 10 / 2 -- double

fails because the two types are different.
I'd be in favor of the 3rd option, reconciling the different types found but being very careful about what is allowed.
Spark's AnsiTypeCoercion.findTightestCommonType seems suited, it'll allow common type widening without being too permissive - e.p. it forbids a whole class of ambiguous cases I mentioned in my previous comment which implicit cast or even upcast would allow.
Few things that I see that would need to be covered:

If the column already exists in the target, then the target type should not be changed.
Sufficient testing of the type reconciliation logic.
Struct evolution must work correctly, e.p. adding fields to structs nested in maps/arrays. I don't think we necessarily need special handling in this change but this is an area that was missed in the past and we don't have tests yet that cover adding fields that exists already in the source.

Updated to use TypeCoercion.findWiderTypeForTwo
AnsiTypeCoercion will resolve a string and a integral to a long, and not a string. The non-ansi TypeCoercion seemed like a better fit.
I updated the tests I made to suit. Trying to figure out what nested tests to add. For the most part nested things shouldn't be any different.

Added more complex type tests, let me know what how it looks


Add a description

If you add a description to the top of the Code tab, it will show up in search results and previews:


InvalidCbor error when running cncli-sync on SanchoNet

Describe the bug
The cncli sync service does not fully sync when running on a SanchoNet node. Instead it fails around 86-88% with ERROR cncli::nodeclient::sync   > InvalidCbor("unexpected type u8 at position 263: expected array"). The error does not always occur at the same block.
Removing the cncli db and starting from scratch yields the same result.
To Reproduce

Spin up a SanchoNet node and let it sync with the SanchoNet chain
Start a fresh cncli instance with an empty database
Let it sync and wait for the error to show up in the journal

Expected behavior
It will sync to 100% and keep it there.
Additional context
Last lines from the journal:
INFO  cncli::nodeclient::sync > block 1016212 of 1163604:  87.33% sync'd
INFO  cncli::nodeclient::sync > block 1032098 of 1163604:  88.69% sync'd
ERROR cncli::nodeclient::sync > InvalidCbor("unexpected type u8 at position 263: expected array")
cncli-sync.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: cncli-sync.service: Failed with result 'exit-code'.

The service is started with the following command and runs as a systemd service:
cncli sync --host [redacted] --port 3004 --db /var/local/cncli/db.sqlite --network-magic 4
Tested with precompiled versions 6.0.1 and 6.1.0.

Closed by -> https://github.com/cardano-community/cncli/pull/52
Released in v6.2.0


feat: expost history methods

Coverage remained the same at 87.282% when pulling 244a934b88264d34cc8d9d365a96226f9dd5c19d on feat/expose-history into 2dee251f60dbf27db86bb70f78ec261e3d9cbcae on master.

Merged 后但未发布，请问这个修复什么时候发布呢？


[Mention The Feature]: Add complete tutorial page for Heart Disease Prediction using Machine Learning in projects page website

Is your feature request related to a problem? Please describe.
create a tutorial page
Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots
No response
Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

@DarshAgrawal14 assigning this issue to you.
Make sure to complete this.
And one more thing this project is going to be inactive from october 25th,, including me.


NUnit 3 support

We're finally adding support for NUnit 3 for Xamarin.UITest. We will be supporting NUnit 2 and 3 in the cloud, but you can finally upgrade in Visual Studio.

After Upgrading to NUnit 3,  will it support Local Test Run?

@ssidizc Yes! You will be able to run local NUnit 3 UITests.

exist some ETA for this upgrade?

Hi any news on upgrade ? Reply very much appreciated

It is still in the works, the team is still squashing and developing.

Hi All, there is a pre-release of this available now. Go check it out, let us know how it looks. https://www.nuget.org/packages/Xamarin.UITest/3.0.0-dev1

It seems like NUnit 3 support was removed from App Center (At least via the appcenter-cli) recently, however I cannot find any information on why. Can someone please provide an update on this?

@MrAusnadian what issues are you seeing with the CLI? It should still work, at least it was working for me last week when I last ran an upload.

I have successful test uploads using NUnit 3 from within the last 24 hours, @MrAusnadian the exact CLI version & error message you are seeing would help with debugging this issue.

Sorry for the confusion. I think it may have been a local environment issue. I just attempted to reproduce it and was not able to.


Computed fiat value not appearing for native token (Ethereum mainnet) despite rate and balance being available

Not sure if it's still reproducible on master

i will double check it, but for now i am not facing such issue

Non reproducible

@oa-s probably fixed with a recent change.


fix: adjust nav button behavior in app

What does this PR fix?

Fixes unfavorable interaction behavior of buttons by adjusting timeout to increase by a factor of 10 in window.setTimout()
Fixes issue of clickable area of interaction on dropdown menu.

:tada: This PR is included in version 9.29.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Initial install of extension does not discover R until restarted

On Windows, when I initially install the VSCode extension, it couldn't find R even though it was on my PATH.  I restarted VSCode and it was able to find R and worked as expected.
I then installed Positron and hit the same issue.  I had to restart Positron in order for it to find R on my PATH.

Closing, unable to repro.


Add homebrew-installed completions to fpath

Used the node submodule as inspiration.

Is this a bit better?
Would we want to change the node module to work the same? https://github.com/sorin-ionescu/prezto/blob/master/modules/node/init.zsh#L14-L15

Yes, brew is written for Ruby 1.8, which is slow. Calling it twice is not good. A separate pull request should be opened for that.

No longer using prezto, so can't test this anymore


Make chart and filter field backgrounds a darker colour in dark theme

In dark theme, the contrast between the chart background and the tab background should be reduced (same for the filter background). This makes the data stand out more and draw the user's eye towards the data.

New dark theme filter and background colours should have a similar difference in brightness to the existing light theme background colours.
Tip: Colorizer.org is useful for easily adjusting colours along different scales

Current Light Theme
Proposed Dark Theme

Difference in brightness (HSB): ~2
Difference in brightness (HSB): ~2

Background: #ffffff  Chart background: #f4f7fb
Chart background: #232323  Tab background: #1e1e1e

Comparison of darker and lighter backgrounds:

Current backgrounds (lighter)
Proposed backgrounds (darker)

Difference in brightness (HSB): ~13
Difference in brightness (HSB): ~2

Chart background: #3f3f3f  Tab background: #1e1e1e
Chart background: #232323  Tab background: #1e1e1e

Fixed by PR #382. (This issue should have been linked to the PR so that it was closed when the PR was merged.)


Please add support for recent versions of optparse-applicative

It would be very convenient for us in NIxOS if we could postgrest with the default version of optparse-applicative: http://packdeps.haskellers.com/feed?needle=postgrest.

OK, I'll look into this in combination with #130.
I'll also try adding packdeps as a step in continuous integration so that packages never get out of date.

Thank you very much! The package now compiles fine: http://hydra.cryp.to/build/537202.

Cool! I'm glad you pointed out the outdated packages.
Two questions. Would there be a way to let Hydra create my binaries for me and host them for download? Right now I build them manually, upload to S3, and update the links on the readme which is time consuming.
Also the postgrest hackage page links me to a nix hydra status page that shows failed builds of <IP_ADDRESS>. Will it get around to trying <IP_ADDRESS> or has it given up on this package?

Hydra creates binary packages for every release you make on Hackage. The trouble with those binaries is that they won't work easily on any system that doesn't have Nix installed, because our directory structure is vastly different from that of traditional Linux distributions. I know that some Nix users have set up chroot builds that use Nix to compile binaries for Ubuntu, Debian, etc. As a matter of fact, the releases for the Nix package are built that way so that people from other distributions can use Nix. I don't know much about how that works, though, I'm afraid. I know it's possible, but I don't know how it's done.
About your second question: hydra.nixos.org typically lags two or three days behind the current HEAD of the Nixpkgs git repository. By now, you'll find that it has built postgrest-<IP_ADDRESS> successfully and that package is now available to our users for download.


Macro for if requires else

Right now if you use an if in a lambda without providing an else, then the following happens:
if (foo["bar"] == "baz") do
  {qux: 5}
end

That becomes:
if (eq(foo["bar"], "baz")) do
  {qux: 5}
end

since eq(a, b) returns a %Q{}, the if is made to be always true, which is pretty bad...

In master.


Android chevron fix cherry-pick

This is a cherry-pick of the chevron fix for Android from this pull request #4566
Microsoft Reviewers: Open in CodeFlow

Thanks! Curious - where's the corresponding Test/sample changes for regression testing?

Thanks! Curious - where's the corresponding Test/sample changes for regression testing?

That's not a regression, it was a problem that always existed. The issue was that the chevron would have been showing in the wrong direction if a different show card action was "clicked" in the same action set. Unless we add interface testing then we don't have a way to add tests


[EKS + Weave + Istio]Error creating: Internal error occurred: failed calling webhook "sidecar-injector.istio.io": Post https: //istio-sidecar-injector.istio-system.svc:443/inject?timeout=30s: net/http: request canceled while waiting for connection (Client.Timeout exceeded while await ing headers)

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities/
To ask questions about how to use Istio, please visit https://discuss.istio.io
)
Bug description

If auto-inject is labeled in a namespace, and no pod will spawn. The error on the corresponding rs is Error creating: Internal error occurred: failed calling webhook "sidecar-injector.istio.io": Post https: //istio-sidecar-injector.istio-system.svc:443/inject?timeout=30s: net/http: request canceled while waiting for connection (Client.Timeout exceeded while await ing headers)
The problem is basically similar as the issue https://github.com/istio/old_issues_repo/issues/271. I found the conclusion for this issue is to open port 443 between worker nodes and control plane. But it does not work for my case.

Unable to create the traffic management resource gw/vs/dr
eg.

cat <<EOF | kubectl apply -f -
pipe heredoc> apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: grafana-gw
  namespace: istio-system
spec:
  selector:
    istio: ingressgateway-internal
    # istio: istio-ingressgateway-internal
  servers:
  - hosts:
    - 'mydomain.com'
    port:
      name: https
      number: 443
      protocol: HTTP
EOF

The output is
Error from server (Timeout): error when creating "STDIN": Timeout: request did not complete within requested timeout 30s , and the resource failed to create.
Actually, my K8S cluster is a little bit tricky. I DISABLED the CNI for AWS.
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[x ] User Experience
[x ] Developer Infrastructure
Expected behavior
The sidecar can be successfully injected.
Steps to reproduce the bug
The process I setup the EKS clsuter:

Create an EKS cluster from AWS console.
Get access to the control plane API via kubectl
delete the CNI plugin by kubectl delete deploy/aws-node -n kube-system
Install weave network.   kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n')"
Create worker nodes with the officially provided cloudformation template, a little hack is to inject the bootstrap parameter with --use-max-pods=false; sed -i 's/"maxPods":.*/"maxPods": 200/' /etc/kubernetes/kubelet/kubelet-config.json; systemctl restart kubelet;.
Follow the doc to make worker nodes join the cluster, then the cluster is up with your nodes.
Install helm and tiller with cluster-admin permission (for simple use this case)
Install Istio

helm upgrade --install istio install/kubernetes/helm/istio --namespace istio-system \
    --values install/kubernetes/helm/istio/values-istio-demo-auth.yaml \
    --set gateways.istio-egressgateway.enabled=false \
    --set gateways.istio-ingressgateway.sds.enabled=true \
    --set global.k8sIngress.enabled=true \
    --set global.k8sIngress.enableHttps=true \
    --set global.k8sIngress.gatewayName=ingressgateway \
   --set certmanager.enabled=true \
    --set<EMAIL_ADDRESS>
===
Label namespace default
kubectl label namespace default istio-injection=enabled
Setup Application
kubectl run nginx --image=openresty/openresty:alpine --port 80
kubectl expose deploy/nginx --port 80 --target-port=80

$ kubectl get deploy nginx
NAME    READY   UP-TO-DATE   AVAILABLE   AGE
nginx   0/1     0            0           15h

Version (include the output of istioctl version --remote and kubectl version)
$ istioctl version --remote
client version: 1.2.3
citadel version: 1.2.3
galley version: 1.2.3
ingressgateway version: 1.2.3
ingressgateway-internal version:
pilot version: 1.2.3
policy version: 1.2.3
sidecar-injector version: 1.2.3
telemetry version: 1.2.3

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.3", GitCommit:"5e53fd6bc17c0dec8434817e69b04a25d8ae0ff0", GitTreeState:"clean", BuildDate:"2019-06-06T01:44:30Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.8-eks-a977ba", GitCommit:"a977bab148535ec195f12edc8720913c7b943f9c", GitTreeState:"clean", BuildDate:"2019-07-29T20:47:04Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
Using Helm
helm upgrade --install istio install/kubernetes/helm/istio --namespace istio-system \
    --values install/kubernetes/helm/istio/values-istio-demo-auth.yaml \
    --set gateways.istio-egressgateway.enabled=false \
    --set gateways.istio-ingressgateway.sds.enabled=true \
    --set global.k8sIngress.enabled=true \
    --set global.k8sIngress.enableHttps=true \
    --set global.k8sIngress.gatewayName=ingressgateway \
    --set certmanager.enabled=true \
    --set<EMAIL_ADDRESS>
Environment where bug was observed (cloud vendor, OS, etc)
AWS EKS.
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.

Since the port 443 between control plane and the worker nodes are enabled by default, I began to suspect whether the issue is due to the overlay network by Weave on EKS. But I am not sure and that's why I raised this issue here.
However, my another k8s cluster setup by kops on AWS also using Weave overlay network, and the istio works fine.

Just made another try, and find the manual injection works.

removed the auto inject labels in the namespace
Manual inject with kubectl get deploy nginx -oyaml | istioctl kube-inject -f - | kubectl apply -f -

So this looks like the sidecar-injector webhook not work. However, this blog Amazon claims EKS added the support to the webhook/controller.
Really confused, anyone has idea?

@hustshawn Been trying to get this to work for days. I ran into this, you actually need to run both the AWS and WeaveNet CNIs in parallel (pods with multiple network interfaces). This can be accomplished with CNI-Genie. The reason for this is that the validation webhooks Istio uses cannot be sent to the WeaveNet subnet CIDR range.
Here's how I did it:

Modify the CNI-Genie config to use "default": "weave"
Installing CNI-Genie
Installing WeaveNet
Add the annotation cni: 'aws,weave' to Istio pods - galley, sidecar-injector, telemetry (mixer)
Install Istio

Once I did that, the post-install-security job and sidecar-injection worked. I've now encountered another problem though. While pods can reach each other using the WeaveNet IPs, they are unable to reach any service (ClusterIP) IPs which map to WeaveNet IPs. Did you run into anything like that?

@cmanzi  I did not try your solution, but I suppose I understand your solution. You are assuming the istio component will utilize the CNIs, while other applications use weave. However, in terms of the problem you encountered, this is totally not acceptable.
I think this should be a compatibility issue between Amazon EKS and Istio. There is almost little thing I can do as a basic user, or too much hacky way may incur more unexpected result.
By the way, I found a document that AWS shows EKS work with Istio, and the truth is they just disabled the sidecar-injection by helm install install/kubernetes/helm/istio --name istio --namespace istio-system --set global.configValidation=false --set sidecarInjectorWebhook.enabled=false --set grafana.enabled=true --set servicegraph.enabled=true.  So at this stage, I suppose EKS still not able to support Istio to install with sidecar-injection, and all other applications are working fine.

i have the problem ,  cannot create gateway and virtualservice ,  auto inject is failed ;

Error creating: Internal error occurred: failed calling admission webhook "sidecar-injector.istio.io": Post https://istio-sidecar-injector.istio-system.svc:443/inject?timeout=30s: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

use Manual inject , but  can not create  virtualservice, error message is

Error from server (Timeout): error when creating "hxtrip-product-vs.yaml": Timeout: request did not complete within requested timeout 30s
Error from server (Timeout): error when creating "hxtrip-product-vs.yaml": Timeout: request did not complete within requested timeout 30s

Hey all, thanks for the reports. We are tracking and actively working on this issue in https://github.com/istio/istio/issues/13840. Lets consolidate this in one place to make things easier. Thanks!

this problem is not solved how did @howardjohn closed the issue

@howardjohn  - Is this issue fixed ? I get the same error
Can someone please let me know how to fix this issue ?


Audio driver troubles on latest macos runners.

Description
Recently I update a project MacOs runners (it was running on MacOs 11 before).
I now encounter troubles with audio drivers: https://github.com/utopia-rise/fmod-gdextension/actions/runs/10158162846/job/28089640224?pr=232
Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[X] macOS 14
[X] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
https://github.com/utopia-rise/fmod-gdextension/actions/runs/10158162846/job/28089640224?pr=232
Is it regression?
macos-11
Expected behavior
FMOD should initialize well.
Actual behavior
FMOD does not initialize well failing with:
ERROR: A call to a standard soundcard driver failed, which could possibly mean a bug in the driver or resources were missing or exhausted.void

Repro steps
Run godot-fmod action linked.

Hi @piiertho We are looking into the issue.Will keep you posted.

Hi @piiertho,
We are aware of the FMOD issue in arm64 machines. We are working on it and do not have a set timeline yet.
Closing this issue since the resolution/update will be tracked in #10219 . Please let us know incase of any questions.


Update NearFutureElectrical-Core for 1.1, primary moved to SpaceDock

Not sure why the build failed. JSONLint says the syntax is valid...

The failure is caused because netkan gets too many "hits" for .version files. It detects B9PartSwitch.version, CRP.version, and NearFutureElectrical.version and doesn't know which one to use. I'll think on this a bit to see if I can come up with an elegant workaround.

Because of how $vref works there isn't an elegant solution for this case. You'll need to hardcode ksp_version.

Many thanks for your super patient assistance in the face of my helpless flailing around the spec. The AVC thing was another thing I thought I should add because the guide makes it sound like a great idea, but clearly I wasn't aware of what it would cause to happen.

No fault to you for the AVC thing. It generally is a good idea to use it, this is just a very niche scenario where this particular metadata isn't installing the .version file for this mod so netkan scans the entire .zip for any and all .version files.


Mac version

Is there any port to mac os x of the latest version with file transfer?

Same as https://github.com/aws/aws-sdk-ios/issues/498 in v2 of SDK.


Added inital documentation for search payload

Can you guys take a look at this and suggest edits. Also the result payload is still missing, which I will get to when I can.

Looks good to me except for a few typos which I noted


Add rosetta-cli check:construction to Nightly

We should add the rosetta-cli checks to CI. They could be marked as okay to fail if we're worried about third party deps breaking CI, but it'd be good to spot changes that break these checks. The commands to add, from a cursory look, are:

[ ] rosetta-cli check:construction
[x] rosetta-cli check:data

https://community.rosetta-api.org/t/automated-construction-api-testing/120
https://community.rosetta-api.org/t/feedback-request-automated-construction-api-testing-improvements/146/14
https://github.com/coinbase/rosetta-cli/issues/112
https://github.com/coinbase/rosetta-cli/blob/v0.5.0/configuration/configuration.go#L117-L119
We can store the private key as a GitHub secret, then inject it into the workflow

https://github.com/input-output-hk/cardano-rosetta/pull/185#issuecomment-702777737


Platformer Keymapping in Settings not working

When I change the buttons in the settings menu for "Platformer" nothing happens. Jump is always mapped to A, run to B and interact to A.
Other platformer settings like gravity do work.

Could you double check you're using version 3.0.3 and try cleaning the build cache and see if it works?

Same happened to me, after cleaning up everything and run it again, it solves my issue. This issue happened me over two different projects, so cleaning up and building can be require for all your affected projects.


Cities in the country

Hello,
There are missing cities or regions in the country we specified in the search criteria. Is there a way to fix this?

Use Bulk Edit


IllegalArgumentException: class java.lang.Object is not an interface

This stacktrace is shown when attempting to detach an Activity that uses MvpNullObjectBasePresenter but does not implement any Interface
java.lang.RuntimeException: Unable to destroy activity {com.mypackage/com.mypackage.ui.account.AccountActivity}: java.lang.IllegalArgumentException: class java.lang.Object is not an interface
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3831)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3849)
        at android.app.ActivityThread.-wrap5(ActivityThread.java)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1398)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:148)
        at android.app.ActivityThread.main(ActivityThread.java:5422)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
        Caused by: java.lang.IllegalArgumentException: class java.lang.Object is not an interface
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:147)
        at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:228)
        at com.hannesdorfmann.mosby.mvp.NoOp.of(NoOp.java:41)
        at com.hannesdorfmann.mosby.mvp.MvpNullObjectBasePresenter.detachView(MvpNullObjectBasePresenter.java:42)
        at com.hannesdorfmann.mosby.mvp.delegate.MvpInternalDelegate.detachView(MvpInternalDelegate.java:70)
        at com.hannesdorfmann.mosby.mvp.delegate.ActivityMvpDelegateImpl.onDestroy(ActivityMvpDelegateImpl.java:71)
        at com.hannesdorfmann.mosby.mvp.MvpActivity.onDestroy(MvpActivity.java:47)
        at android.app.Activity.performDestroy(Activity.java:6422)
        at android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1142)
        at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:3818)
        at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:3849)
        at android.app.ActivityThread.-wrap5(ActivityThread.java)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1398)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:148)
        at android.app.ActivityThread.main(ActivityThread.java:5422)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

I feel that the error message could be improved by checking in MvpNullObjectBasePresenter if the class to be detached implements MvpView, but I'm not sure if that's the best way, I haven't dig too much into Mosby code
Class<V> viewClass = (Class<V>) types[0];
//add check here? Throw an Exception if it doesn't implement MvpView?
view = NoOp.of(viewClass);

Also, this error is only happening in release version with ProGuard. It's been in development like that for months and it hasn't crashed.

Thanks for reporting.
Which version of Mosby do you use? I assume 2.x , because I think this issue has been solved with Mosby 3.0.0-SNAPSHOT

Sorry I forgot to mention, it's version 2.0.1

Could you please try it with latest 3.0.0-SNAPSHOT

My code does not compile with 3.0.0-SNAPSHOT, it looks like BaseMvpViewStateDelegateCallback no longer exists

I think it has been renamed to MvpViewStateDelegateCallback

It doesn't crash in 3.0.0-SNAPSHOT, I see that you catch the exception in MvpNullObjectBasePresenter's constructor

Thanks for your feedback. So it's not crashing, but it should crash since the view is not implementing the view interface, right? or does base class you extend from implement MvpView interface?

It's not crashing, but com.hannesdorfmann.mosby.mvp.MvpActivity does implement MvpView

Ok, I have to dive into the code again to verify whether or not this is the desired behavior.
Just to sum it up:
You have a FooActivity extend MvpActivity<FooPresenter, FooView> (but FooActivity doesn't implement FooView) and a FooPresenter extends MvpNullObjectBasePresenter<FooView>. Is that correct?

Yes, that's the scenario. Some details

The Activity is empty, it's just a Fragment container
It didn't crash in version 2.0.1 until I used ProGuard

Got it! I have to verify the source code ... Regarding proguard, I guess a
rule is missing here, will check that too ... Thanks for your patience!
Miguel Aragues<EMAIL_ADDRESS>schrieb am Di., 6. Sep. 2016 um
18:01 Uhr:

Yes, that's the scenario. Some details

The Activity is empty, it's just a Fragment container
It didn't crash in version 2.0.1 until I used ProGuard

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sockeqwe/mosby/issues/159#issuecomment-244999878, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAjnrsSuUtKn0dsdI_QJT3UJZ4CCcIJ6ks5qnY50gaJpZM4J146O
.

Thanks to you for the time you devote to the community!

I have same error when tryed to add parametr to my extention of MvpView interface. I tryed to compile with  3.0.0-SNAPSHOT, but gradle cant find it

Can you please show me a code snipped of your view interface and presenter
class (basically I'm only interested in the interface / class definition)
Yuri<EMAIL_ADDRESS>schrieb am Mi., 4. Jan. 2017, 22:46:

I have same error when tryed to add parametr to my extention of MvpView
interface. I tryed to compile with 3.0.0-SNAPSHOT, but gradle cant find it
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sockeqwe/mosby/issues/159#issuecomment-270496184, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAjnro5mKT3P5pZ6M1IRIvfgKQ0hokqkks5rPBNCgaJpZM4J146O
.

My base interface looks like
public interface BaseListMvp {
    interface View<D> extends BaseMvpView {
        void updateData(List<D> data);
    }

    interface Presenter<D, V extends View> extends BaseDataPresenter<V> {
        List<D> getData();
    }
}

I also create BaseListPresenter
public abstract class BaseListArticlesPresenter<D extends RealmObject, V extends BaseListMvp.View<D>>
        extends BasePresenter<V> implements BaseListMvp.Presenter<D, V> {

    protected RealmResults<D> mData;

    public BaseListArticlesPresenter(MyPreferenceManager myPreferencesManager, DbProviderFactory dbProviderFactory, ApiClient apiClient) {
        super(myPreferencesManager, dbProviderFactory, apiClient);
    }

    @Override
    public List<D> getData() {
        return mData;
    }
}

And finaly create concrete presenter so:
public class RecentArticlesPresenter extends BaseListArticlesPresenter<Article, RecentArticles.View> implements RecentArticles.Presenter {

    public RecentArticlesPresenter(MyPreferenceManager myPreferencesManager, DbProviderFactory dbProviderFactory, ApiClient apiClient) {
        super(myPreferencesManager, dbProviderFactory, apiClient);
    }
}

where RecentArticles interface is
public interface RecentArticles {
    interface View extends BaseListMvp.View<Article> {
    }

    interface Presenter extends BaseListMvp.Presenter<Article, View> {
    }
}

And it works until I try to replace fragement or rotate screen, after fragment try to destoy them self. Then onDestroy called and an error. that mentioned previously in this issue occures

@mohaxspb I tried to reproduce your issue, but I can't reproduce it. I have added a unit test with your interface specifications, but it is not crashing.
Could you please take a look here and verify that the classes / interface are equal to what you have:
https://github.com/sockeqwe/mosby/tree/master/mvp-common/src/test/java/com/hannesdorfmann/mosby3/mvp/test/regression159
and the corresponding test:
https://github.com/sockeqwe/mosby/blob/master/mvp-common/src/test/java/com/hannesdorfmann/mosby3/mvp/test/regression159/MvpNullObjectBasePresenterRegression159Test.java
Could you also post your stacktrace here?
Are you absolutely sure that you are using 3.0.0-SNAPSHOT? because the exception should be called directly in constructor (if null object releated) and not when view is detached / because fragment has been destroyed.


¬∃x. ¬y => ∀x. y

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ehuss (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

@bors: r+

:pushpin: Commit e97b36ab336440ddc641b23eaa84d49f70d0bc8c has been approved by alexcrichton

:hourglass: Testing commit e97b36ab336440ddc641b23eaa84d49f70d0bc8c with merge c7eddc1ee99b63185112a17922ba5d71c05af244...

:sunny: Test successful - checks-azure
Approved by: alexcrichton
Pushing c7eddc1ee99b63185112a17922ba5d71c05af244 to master...


metrics merging: detect prometheus.io.scrape format

Due to escaping logic in prom, this is equivilent to prometheus.io/scrape (__meta_kubernetes_pod_annotation_prometheus_io_path). So we probably want to detect both. See https://github.com/openfaas/faas-netes/issues/714.

not stale
On Mon, May 31, 2021 at 10:04 PM Istio Policy Bot @.***>
wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2021-03-02.
It will be closed on 2021-06-15 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/31187#issuecomment-851806826, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXOVXAOGXSPVXA3TLPDTQRS4ZANCNFSM4YPWCMKQ
.

not stale
On Mon, Aug 30, 2021 at 10:02 PM Istio Policy Bot @.***>
wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2021-06-01.
It will be closed on 2021-09-14 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/31187#issuecomment-908900525, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXOXY63PMY7XA5IRSCLT7RO6VANCNFSM4YPWCMKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

not stale
On Mon, Nov 29, 2021 at 9:02 PM Istio Policy Bot @.***>
wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2021-08-31.
It will be closed on 2021-12-14 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/31187#issuecomment-982287400, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXPMHZH6MHG36KTPQBTUORLFDANCNFSM4YPWCMKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@howardjohn what's this means? can you share more details?

Currently we look for prometheus.io/scrape annotation in pkg/kube/inject
and rewrite it. But actually due to how prometheus Kubernetes meta -> prometheus labels mapping works, many characters end up as the same thing.
So for example, prometheus.io/scrape and prometheus.io.scrape are
identical to prometheus, but we only match the first format.
On Tue, Jan 18, 2022 at 12:50 AM zirain @.***> wrote:

@howardjohn https://github.com/howardjohn what's this means? can you
share more details?
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/31187#issuecomment-1015192610, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXIFREX64EWJTJM2IPDUWUSV5ANCNFSM4YPWCMKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


Add cache toEthersDB/AlloyDB for remote state

For evm execution, storage and account will be journaled, so it's ok to not cache remote state.
But for block_hash, maybe lack cache for it.

You can use CacheDb for this, as a additional layer of Database that are going to do caching.


UARTinit() not called with arduino-esp32 core 2.0

Discussed in https://github.com/eModbus/eModbus/discussions/141

Originally posted by mstegen January 16, 2022
Hi again,
I'm trying arduino core 2.0.2 on my project, and noticed something strange.
In my project the ModbusServerRTU is listening for modbus data from other devices on the bus,  and processing data without sending any data back.
I noticed that the request and response interval time was not working correctly. Both messages were processed as one block of data, and the CRC check failed.
This was not a problem on arduino core 1.0.6.
After some tests, i noticed that somehow UARTinit() is not called. At least i can not see the debug output "UARTinit: Serial1 FIFO threshold set to 1 (was 112)" this is for both 1.0.6 and 2.0.2 versions of arduino core.
So i added the call to UARTinit() in the ModbusServerRTU::start code.
Now it's working on core2.0.2

@mstegen I doubt the call is not made, but the initialization we do in there may be overwritten later again.
Which development environment are you using? In PlatformIO, that I usually am using, the 2.0 core has not been deployed yet.

Hi @Miq1, i'm using PlatformIO. These are the settings i used for core 2.0.2:
platform_packages = framework-arduinoespressif32 @ https://github.com/espressif/arduino-esp32.git#2.0.2
     platformio/tool-esptoolpy @ https://github.com/tasmota/esptool/releases/download/v3.2/esptool-v3.2.zip

But even when using core 1.0.6 i can not see the debug output that sets the FIFO threshold to 1.
Do you see it?

Did some more tests on core 1.0.6.
You were right, the call to UARTinit was made.
But at that time the Uart is not initialized yet, so i guess the changes to the FIFO threshold get overwritten when the Serial port is setup.
Somehow this did not affect the library on 1.0.6 (at least for me), but it does on 2.0.2
Moving the call to UARTinit to ModbusServerRTU::start will fix this for both core versions.

Thank you for testing that. I think for the time being moving the call as you are suggesting will do no harm.
I still am waiting to learn what has been improved with the different UART handling in 2.0.  The core maintainers were completely ignorant about that...

I provided a commit for ModbusServerRTU and ModbusClientRTU. Would be great if you could do some tests with this.

Thanks. I do see some more packet length errors though, when it thinks it receives a single 'E5' byte.
But Uart handling has improved a lot in 2.0.2 from what i can see. I'm working on a project that uses all three Uarts simultaneously, and i used to see lot's of gaps in reception, that resulted in checksum errors on the data (checksum was required on all three Uarts because of this behavior).
It's now running for a few hours, and i have not seen one checksum error yet.

Can you provide us a log of the E5 errors occurring? Best with the -DLOG_LEVEL=6 compiler flag to see the raw data as well.
E5 can be an indication of bad timing on the bus, most probably done by us, if it worked before. If you got industrial servers on the bus with high baud rates, chances are that the lib is losing pace. We for instance do not care at all about the intra-message gap control that the Modbus standard advises, because we are depending from the UART to deliver the data without any chance to interfere.

Here's the logfile, it looks like the E5 error is only happening after the software writes a response to the bus.
logfileE5.txt

Thanks!
There is always a stray 0x00 byte on the bus that is causing the E5 error (as I suspected...). In combination with the fact that you had sent a response immediately before that, that strongly points to the signal issue @bertmelis analyzed and has explained thoroughly in the pinned thread in Discussions.
In short, the switch of the DE/RE pin after sending back to listening mode in combination with a suboptimal biasing on the Modbus leads to a three-state effect that is registered as a "ghost 0x00" on UART.

Yes, i "fixed" it for now by adding
serial.read(); just after the Rts pin of the RS485 transceiver is set to low.
so it absorbs the ghost 0x00.
If there is nothing to read, it will return immediately, so it should not block or harm in any way i think ?
All E5 errors are gone now..

That is a fix of the symptoms, with the threat of more to happen later on. I rather would try to exactly bias my bus with Bert's example. If you have proper biasing and termination on the bus, you will be safe.

Yes, i understand that exactly biasing the bus is preferred, however i think it's a bit to sensitive now. It's not that there is random data on the bus that can be removed by biasing the bus. It's always a 0x00.
It's caused by the transceiver switching from RX to TX, and this spike is then mistakenly read by the uart as a 0x00.
The thing is: the uart should -not- listen to the bus at this time, as it is half duplex, it should only start listening again when the transmission has finished. So i think it's ok to reject any data that is received when the transmission is in progress...
And that brings me to this: It also suppresses the 0x00 if you move the serial.read() just before the rts(LOW); (so before the tx ends)
Btw, on core 1.0.6 the E5 error appeared only once every 10 minutes or so, not every 2 seconds. So they definitely 'improved' the uart code ;-)

The 0x00 is caused by toggling RE/DE only, so I am wondering why the UART should have changed anything about that? The time interval would only be affected by the sketch doing the toggle, right?
I agree the UART is not particularly well-suited to do our Modbus communications, but writing our own low-level serial code was no feasible option.

With core 2.0.2 it's now much more reliable at receiving all data at all three uarts, at the same time. That might have something to do with it.
I noticed they just added a callback, so that probably means that the polling loop can be removed in the future?
https://github.com/espressif/arduino-esp32/pull/6134

That is sounding promising. If only the PlatformIO guys woul lift to 2.0 at least.

Closing this, as it seems to work with the moved UARTinit call.


Cannot update or delete documents with an Uuid

Hi!
I'm using this type of IDs in my entities :
/**
 * @ORM\Id
 * @ORM\GeneratedValue(strategy="UUID")
 * @ORM\Column(type="uuid")
 */
private $id;

On update or remove I get an MeiliSearch\Exceptions\InvalidArgumentException in this method :
private function assertValidDocumentId($documentId): void
{
    if (!\is_string($documentId) && !\is_int($documentId)) {
        throw InvalidArgumentException::invalidType('documentId', ['string', 'int']);
    }

    if (\is_string($documentId) && '' === trim($documentId)) {
        throw InvalidArgumentException::emptyArgument('documentId');
    }
}

Hello @tomdoo!
Can you give in which context you have this error? What kind of document id triggers this problem?

This error occurs when I persist entities with an UuidV4 primary key.
It fails on MeiliSearch\Bundle::remove() because the ID send is an object instead of int|string.

Add a test with this specific situation would be perfect then :)

I added the tests.
There was also an issue in MeiliSearchService::search. For a reason I don't know this doesn't works with generic objects
$entity = $repo->findOneBy(['id' => $id]);

I replaced it with, it's also better if your identifier is not named "id"
$entity = $repo->find($id);


Incorrect favicon shown during setup

Setup

Rancher version: master / 2.7.3 ish

Describe the bug

Set up page shows an incorrect favicon
There's a request made to /public/favicon.png, which returns a 200 but it's the loading page rather than an image

To Reproduce

Bring up a new rancher
Nav to UI

Expected Result

In default setups this should be the blue rancher bull

Screenshots

Additional context

Calls to /public/favicon.png continue to be made (on load) after setting up rancher, however the favicon is still correct

Caused by <link rel="shortcut icon" type="image/x-icon" href="/public/favicon.png"> in template, think this should just be /favicon.png

We should also validate the custom favicon that can be set via branding

After bringing up the same docker container used when discovering this issue the error isn't reproducible. I'll retest when the first RC is out in case there was something odd going on

Engineering to write an automated test in #8827 to help QA.


No outgoing internet access within the server

Server OS: Ubuntu 16.04 (VPS)
Client OS: Ubuntu 18.10
The VPN works really well, except for the fact that the server itself has issues. Its DNS is failing.
I can ping IP's without issue:

PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=123 time=1.13 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=123 time=1.47 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=123 time=1.15 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=123 time=1.34 ms
64 bytes from <IP_ADDRESS>: icmp_seq=5 ttl=123 time=1.24 ms
64 bytes from <IP_ADDRESS>: icmp_seq=6 ttl=123 time=1.41 ms
64 bytes from <IP_ADDRESS>: icmp_seq=7 ttl=123 time=1.61 ms
^C
--- <IP_ADDRESS> ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6005ms
rtt min/avg/max/mdev = 1.130/1.337/1.611/0.166 ms

But if I ping a domain it doesn't even ping it once

ping google.com
ping: unknown host google.com

Also, I am using UFW if that makes any difference
It cripples the whole server as I cant even update ubuntu lol

Fixed it!
I checked /etc/resolv.conf and found just this

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

It was empty, not a single DNS server. Once I added one, the DNS started working
Since it removes itself after reboot I installed dnsmasq

sudo apt-get install dnsmasq

Then I edited its config file

sudo nano /etc/dnsmasq.conf

I added the servers at the end of the file like so

server=<IP_ADDRESS>
server=<IP_ADDRESS>

saved and restarted, now it works well :)

Thanks for posting your solution :)


Not working with Secure-Ls

vuex-persistedstate version:     "vuex-persistedstate": "^4.0.0-beta.3",
node  10.24:
npm (or yarn) version: 1.22

Relevant code or config

What you did:
What happened:
Problem description: old state, its never updated, changed.
https://github.com/softvar/secure-ls/issues/56
So, custom STORAGE option could be broken, tested with  latest persistedstate and Securels, also some old version stopped to work.

Could you at least provide a reusable example?

@robinvdvleuten
import { createStore } from 'vuex'
. . .
import createPersistedState from "vuex-persistedstate";
import SecureLS from "secure-ls";
const ls = new SecureLS({ isCompression: false });

export default new createStore({
  state: {
    count: 0
  },
  plugins: [
    createPersistedState({
      storage: {
        getItem: (key) => {
          console.log(key)
          ls.get(key)
        },
        setItem: (key, value) => ls.set(key, value),
        removeItem: key => ls.remove(key)
      }
    })
  ],
  modules: {
    xxxx,
    search
  }
});

Loading the page shows
index.js:163 Uncaught Error: Could not parse JSON
    at SecureLS2.get (index.js:163)
    at Object.getItem (index.js?t=1631830051988:19)
    at n2 (index.ts:38)
    at s (index.ts:80)
    at index.ts:90
    at vuex.esm-bundler.js:935
    at Array.forEach (<anonymous>)
    at new Store2 (vuex.esm-bundler.js:935)
    at new createStore (vuex.esm-bundler.js:880)
    at index.js?t=1631830051988:10

And the console.log(key) shows a string of "vuex".
Maybe related to https://github.com/robinvdvleuten/vuex-persistedstate/pull/400 ?


Releases/2.5.0 -> mrtk_dev

Overview
Some docs updates went in after https://github.com/microsoft/MixedRealityToolkit-Unity/pull/8725

closed in favor of https://github.com/microsoft/MixedRealityToolkit-Unity/pull/8743


Boron recipe chain is still diborane-positive at high prod.

Mod source
Factorio Mod Portal
Operating system

=Windows 10

What kind of issue is this?

[ ] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[X] Balance
[ ] Pypostprocessing failure
[ ] Other

What is the problem?

There was a previous attempt to solve this by catalyst-flagging the diborane byproduct, but it's insufficient when the full chain is prodded.
Dropping the diborane byproduct output of the boron recipe from 50 to below 16.9 would prevent closing the loop, as would removing prod from at least two of the four steps.
Steps to reproduce
No response
Additional context
No response
Log file
No response

I will mark this as "not a bug"
You are spending ref syngas, boron mixture, aluminium, ect just for a small amount of diborane.
Even if this is technically a dupe, no sane player would use this as a primary source of diborane.

The main weirdness, to me, is that this allows the production of boron without any borax input (except to kickstart).  So flavor more than mechanics.  But obviously not a big deal, and breaking the game post-victory is baked in anyway.