RFE: support rstrnt-abort --server "$RSTRNT_RECIPE_URL/tasks/$RSTRNT_TASKID/status"

At least for kernel-tests this command is used in multiple test, to abort the execution of a single test.
tmt seems to support tmt-abort, but only for the general case where the whole plan execution is aborted.
rstrnt-abort --server "$RSTRNT_RECIPE_URL/tasks/$RSTRNT_TASKID/status"

one of the repos with kernel tests that uses this: https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/
In case this is decided to not be supported we will need to update the tests so they can work well on tmt.

BTW, before changing the internals of tmt-abort, https://github.com/teemtee/tmt/issues/2377 should be implemented.


False negative on Struts 2.5.12?

Just installed Struts 2.5.12 on Tomcat 9 as a test target running locally - This should be a vulnerable version
http://<IP_ADDRESS>:8080/struts2-showcase/index.action shows the 'Welcome!' screen
$ ./struts-pwn.py -u 'http://<IP_ADDRESS>:8080/struts2-showcase/index.action'

[*] URL: http://<IP_ADDRESS>:8080/struts2-showcase/index.action
[*] Status: Not Affected.

Same result with any URL (even non-existent ones)

Let me know on the status on this so I can accurately test

Interesting:
python struts-pwn.py --url http://locahost:8080/struts2-rest-showcase/orders/5 [*] URL: http://localhost:8080/struts2-rest-showcase/orders/5 [*] Status: Vulnerable! [%] Done.
python struts-pwn.py --url localhost:8080/struts2-showcase/index.action [*] URL: http://localhost:8080/struts2-showcase/index.action [*] Status: Not Affected. [%] Done.
`python struts-pwn.py --exploit --url http://localhost:8080/struts2-showcase/index.action
[] URL: http://localhost:8080/struts2-showcase/index.action
[] CMD: echo test > /tmp/struts-pwn
[$] Request sent.
[.] If the host is vulnerable, the command will be executed in the background.
[%] Done.`
`python struts-pwn.py --exploit --url 'http://localhost:8080/struts2-showcase/index.action' -c 'id'
[] URL: http://localhost:8080/struts2-showcase/index.action
[] CMD: id
[$] Request sent.
[.] If the host is vulnerable, the command will be executed in the background.
[%] Done.`

Hi @hubert3 @Whiteflames @securitaydude,
I have noticed that the vulnerability can be only triggered in affected endpoints in the application.
For example, if /struts2-showcase/index.action is not affected, then struts-pwn will report it as "Not Affected".
I would suggest crawling the web-application, and then feeding struts-pwn with all identified URLs.
@securitaydude, -c id is not returning anything on the screen because the CVE-2017-9805 RCE vulnerability is OOB. you can provide a command that requests external server to verify the execution of the code for example, but you won't be able to view output on the response.
For the Metasploit module part, have you used a URI that worked Metasploit and did not work on struts-pwn?
Best,
Mazin

@mazen160 , for the Metasploit module, I was able to get a linux meterpreter shell with the following URL: http://localhost:8080/struts2-rest-showcase/orders/3 . I've had no success with http://localhost:8080/struts2-showcase/index.action.

@securitaydude Yes, this should be an expected behaviour, since /struts2-showcase/index.action is known to not be an affected endpoint.
In Metasploit, you can get a shell because the module runs a reveres connection, which is essentially popping a shell via OOB connection.
You can does the same with struts-pwn with a custom payload.
Best,
Mazin

@mazen160 Thank you for your help. I used `ping -c 5 attackingmachine'  on as a command argument and used tcpdump on the attacking machine to capture icmp packets.


programs.fzf.enable breaks some bash completions

Describe the bug
The last fzf update in nixos-unstable breaks certain bash-completions, for example git.
Steps To Reproduce
This happens since https://github.com/NixOS/nixpkgs/commit/e3812e187592c866349630cc097c786b353130c7
programs.fzf.enable = true;
programs.git.enable = true;

Then try bash completion for git.
My /etc/bashrc looks like this

# /etc/bashrc: DO NOT EDIT -- this file has been generated automatically.

# Only execute this file once per shell.
if [ -n "$__ETC_BASHRC_SOURCED" ] || [ -n "$NOSYSBASHRC" ]; then return; fi
__ETC_BASHRC_SOURCED=1

# If the profile was not loaded in a parent process, source
# it.  But otherwise don't do it because we don't want to
# clobber overridden values of $PATH, etc.
if [ -z "$__ETC_PROFILE_DONE" ]; then
    . /etc/profile
fi

# We are not always an interactive shell.
if [ -n "$PS1" ]; then
    # Show current working directory in VTE terminals window title.
# Supports both bash and zsh, requires interactive shell.
. /nix/store/9wxzfd8rx71cpk4jdf7z2bq0qjx3ja22-vte-0.74.2/etc/profile.d/vte.sh

shopt -s globstar
shopt -s histappend

HISTCONTROL=ignoreboth
HISTFILE="$HOME/.local/state/bash_history"
HISTFILESIZE=50000
HISTSIZE=50000

eval "$(direnv hook bash)"

source /nix/store/zp81cmraynjxpc5rkb9a3djvaiml42f2-nix-index-with-db-0.1.7/etc/profile.d/command-not-found.sh

eval "$(/nix/store/psmylmimp0023yibdx1w76hf8zds0sjj-fzf-0.49.0/bin/fzf --bash)"

# Check the window size after every command.
shopt -s checkwinsize

# Disable hashing (i.e. caching) of command lookups.
set +h

# Provide a nice prompt if the terminal supports it.
if [ "$TERM" != "dumb" ] || [ -n "$INSIDE_EMACS" ]; then
  PROMPT_COLOR="1;31m"
  ((UID)) && PROMPT_COLOR="1;32m"
  if [ -n "$INSIDE_EMACS" ]; then
    # Emacs term mode doesn't support xterm title escape sequence (\e]0;)
    PS1="\n\[\033[$PROMPT_COLOR\][\u@\h:\w]\\$\[\033[0m\] "
  else
    PS1="\n\[\033[$PROMPT_COLOR\][\[\e]0;\u@\h: \w\a\]\u@\h:\w]\\$\[\033[0m\] "
  fi
  if test "$TERM" = "xterm"; then
    PS1="\[\033]2;\h:\u:\w\007\]$PS1"
  fi
fi

eval "$(/nix/store/ifzwv2xqwdnv1gz87rxkizi67py5p3vj-coreutils-9.4/bin/dircolors -b)"

# Check whether we're running a version of Bash that has support for
# programmable completion. If we do, enable all modules installed in
# the system and user profile in obsolete /etc/bash_completion.d/
# directories. Bash loads completions in all
# $XDG_DATA_DIRS/bash-completion/completions/
# on demand, so they do not need to be sourced here.
if shopt -q progcomp &>/dev/null; then
  . "/nix/store/h7rc4ajxx8lrqg1i6cr8zhvz15rd2g0y-bash-completion-2.11/etc/profile.d/bash_completion.sh"
  nullglobStatus=$(shopt -p nullglob)
  shopt -s nullglob
  for p in $NIX_PROFILES; do
    for m in "$p/etc/bash_completion.d/"*; do
      . "$m"
    done
  done
  eval "$nullglobStatus"
  unset nullglobStatus p m
fi

alias -- eza='eza --hyperlink --all --git'
alias -- ip='ip -color=auto -iec'
alias -- l='eza --long'
alias -- ll='ls -l'
alias -- ls='ls --color=tty'
alias -- open='xdg-open'
alias -- t='l --tree'
alias -- tree='eza --tree'
alias -- wget='wget --hsts-file=~/.cache/wget-hsts'

# Bind gpg-agent to this TTY if gpg commands are used.
export GPG_TTY=$(tty)

fi

# Read system-wide modifications.
if test -f /etc/bashrc.local; then
    . /etc/bashrc.local
fi

Expected behavior
The regular bash completions for git should work.
As a fix I found this old issue in fzf https://github.com/junegunn/fzf/issues/72
To test this, I tried simply replacing /etc/bashrc with an edited version that
puts the fzf eval after the bash completions code (and before the alias
declarations). This fixes the issue. However, I am not sure how to solve this
cleanly in NixOS.
The bash completion code is inserted using programs.bash.promptPluginInit but
I don't know how to enforce ordering so that the fzf eval happens after the
completions.
Notify maintainers
@SebTM
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.8.4, NixOS, 24.05 (Uakari), 24.05.20240408.4cba8b5`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/etc/nix/inputs/nixpkgs`

Add a :+1: reaction to issues you find important.

Thanks for the report, I started a PR super-seeded by https://github.com/NixOS/nixpkgs/pull/303201 fixing this issue. As what I found this issue was already there previously but as most people didn't had the full integration enabled it didn't triggered the issue.

Is there any progress on this? Solution PRs seem to have been closed?

The fix already got merged and will be soon on unstable - otherwise you might cherry-pick/overlay it.
https://github.com/NixOS/nixpkgs/issues/303381#issuecomment-2050450978

The fix already got merged and will be soon on unstable - otherwise you might cherry-pick/overlay it.
#303381 (comment)

Cool, so we can close this presumably?

I looked at this in master and now we're basically back to how the fzf module was previously, right? So then it should still be an issue when enabling programs.fzf.fuzzyCompletion = true;, right?

As what I found this issue was already there previously but as most people didn't had the full integration enabled it didn't triggered the issue.


missing .dll files?

when i buildt and ran n64recomp, it said libgcc_s_seh-1.dll and libstdc++-6.dll are missing? it said reinstalling the program may fix this but i tried and it gives me the same error

AFAIK those are MSYS2 DLLs; you either need to copy them into the build directory, or choose a different C++ compiler.
Assuming you've installed MSYS2 to C:\msys64, you can typically find those DLLs here: C:\msys64\mingw64\bin
You will also need to copy libwinpthread-1.dll while you're at it.

i did it but, when i open the .exe it opens, then closes very quickly, i think its a command type of thing where you type commands but i dont know which ones


Adding subscription without schema

On my schema, I do not have defined any subscriptions. However, the merge process is adding a subscription on my schema:
schema {
  query: Query
  mutation: Mutation
  subscription: Subscription
}

But the merged file generated doesn't define the Subscription type. The merge should only add the subscription inside the schema if it exists

Thank you for opening the issue. I'll fix it soon.

Can you test the latest v0.2.12? I think it is fixed.

Sure, I will test today :)
Em qui., 14 de dez. de 2023 às 08:22, woonki @.***>
escreveu:

Can you test the latest v0.2.12? I think it is fixed.
—
Reply to this email directly, view it on GitHub
https://github.com/mununki/gqlmerge/issues/46#issuecomment-1855665806,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRTLZEMYRSOHGLQYQSGTWDYJLON5AVCNFSM6AAAAABATDHUQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJVGY3DKOBQGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

I just tested and it worked =D

I just tested and it worked =D

Thanks!


setting the velocity to 0 in each step

What is the reason for setting the velocity to 0 after each step in the agent?
 self.client.moveByVelocityAsync(vx=vx, vy=vy, vz=vz, duration=1,                                             drivetrain=airsim.DrivetrainType.MaxDegreeOfFreedom,                                             yaw_mode=airsim.YawMode(is_rate=False,                                                                     yaw_or_rate=180 * (alpha + psi) / np.pi),                                             vehicle_name=self.vehicle_name)             time.sleep(0.07)             self.client.moveByVelocityAsync(vx=0, vy=0, vz=0, duration=1, vehicle_name=self.vehicle_name)

There are two reasons to that

If we don’t set the velocity to zero, then with subsequent actions, the velocity vector keeps on accumulating and the speed of the drone keeps on increasing until it becomes so high that it crashes. So, we set the velocity, wait for the drone to travel for some time, and then set it back to zero.
In the RL algo (off-policy), we observe a state, move the drone, observe new state and reward, and based on this tuple we train the network. For a really slow CPU/GPU, the train step can take significant amount. During that time, if we don’t ensure that the drone is not moving, the drone would have traveled significant amount of distance, potentially losing information for intermediate states.

Thank you for you answer, it makes sense (although maybe it would be more 'realistic' to pause the simulation and setting the max speed instead of stopping the drone)


feat: Jupyterhub cognito fine grained access control

What does this PR do?
This PR creates a cognito identity pool, creates an iam role that is tied to the cognito user and injects credentials to the spawner using auth hooks. This way customers can manage all of their users through cognito and assign iam roles to the notebooks themselves for principle of least privilege.
🛑 Please open an issue first to discuss any significant work and flesh out details/direction - we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Motivation

More

[ ] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[ ] Mandatory for new blueprints. Yes, I have added a example to support my blueprint PR
[ ] Mandatory for new blueprints. Yes, I have updated the website/docs or website/blog section for this feature
[ ] Yes, I ran pre-commit run -a with this PR. Link for installing pre-commit locally

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

I added the conditionals ! Thanks for all the kind words and fast reviews :)

Fixed the index errors


[BUG] Azure ServiceBusReceiver maxWaitTime doesn't always work

Describe the bug
Azure ServiceBusReceiver maxWaitTime isn't always respected.
Expected behavior
When the maxWaitTime is set, the receiver will return a result no matter what upon expiration of the wait time.
Actual behavior (include Exception or Stack Trace)
Occasionally the receiver goes past the wait time before returning a result.
To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)
var sw = new Stopwatch();
sw.Restart();
var message = await messageReceiver.ReceiveMessageAsync(TimeSpan.FromSeconds(30));
_logger.LogInformation($"Message Received ({message != null}) in {sw.Elapsed.TotalSeconds}s");

Environment:

Azure.Messaging.ServiceBus" Version="7.2.1"
docker container: mcr.microsoft.com/dotnet/core/aspnet:3.1-buster-slim
VS 2019

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

@JoshLove-msft Can you take a look at this issue please?

Hi @ashf,
The maxWaitTime represents how long we will attempt to wait for a message to be received on the AMQP receive link. When initially establishing the link and connection, there will be an additional overhead that could cause the total elapsed time to be more than 30 seconds. If the link is already open, the time should be right around 30 seconds.

Hi @ashf, The maxWaitTime represents how long we will attempt to wait for a message to be received on the AMQP receive link. When initially establishing the link and connection, there will be an additional overhead that could cause the total elapsed time to be more than 30 seconds. If the link is already open, the time should be right around 30 seconds.

How would I ensure that the link is already open and keep it open?

/unresolve


CFE unable to reach back-end API endpoint in Azure

Do you already have an issue opened with F5 support?
Not yet, but will do so.
Description
Running a standard Active/Standby pair in Azure, once failover from primary (F5-1) to secondary (F5-2) occurs, F5-2 immediately initiates an HTTP POST /declare to the Azure metadata service back-end as indicated in the restnoded.log; however, after properly reading back the json template in the log, an error prompts as follows:
'Function error, retrying: getaddrinfo ENOTFOUND management.azure.com management.azure.com:443 Retries left: (x)'
Essentially, when the F5s failover, CFE should signal the Azure backend to change the next-hop in a particular Azure route-table to whatever the self-ips are specified in the Azure tag and referenced in the CFE json template.

The Azure NSG in front of the F5's mgmt NICs allow outbound to 'Any' on TCP-443
Tons of manual routes have been added to F5's mgmt routes to reach whatever Azure service they may require to function.
Tested with the latest CFE v1.8 and now back to 1.7.1 build 1
Each F5 VM has Contributor access to a shared Azure storage account and reach it successfully as indicated in the logs (log level silly).

Environment information
For bugs, enter the following information:

Cloud Failover Extension Version: 1.7.1 build 1
BIG-IP version: <IP_ADDRESS> Build 0.0.10
Cloud provider: Microsoft Azure

Severity Level
For bugs, enter the bug severity level. Do not set any labels.
Severity: 3
Thanks.

@csiggydev are you still facing this issue?

@shyawnkarim - yes, yes I am unfortunately. Followed the documentation to the letter and F5 Support doesn't have the knowledge to troubleshoot this issue. Failover appears to work intermittently at best, but usually not at all.

@csiggydev  Can you provide additional information:

QKviews
Repro steps with CFE declaration

@f5-chidambaram - i'm a bit hesitant to post the qkview here due to security concerns. Let me know if there's a secure place to submit that. As for the CFE declaration, the following template was posted to each F5:
{
    "class": "Cloud_Failover",
    "environment": "azure",
    "externalStorage": {
        "scopingTags": {
            "f5_cloud_failover_label": "centralus-f5-api-failover"
        }
    },
    "failoverAddresses": {
        "enabled": false,
        "scopingTags": {
            "f5_cloud_failover_label": "centralus-f5-api-failover"
        }
    },
    "failoverRoutes": {
        "enabled": true,
        "scopingTags": {
            "f5_cloud_failover_label": "centralus-f5-api-failover"
        },
        "scopingAddressRanges": [
            {
                "range": "<IP_ADDRESS>/0"
            }
        ],
        "defaultNextHopAddresses": {
            "discoveryType": "static",
            "items": [
                "<IP_ADDRESS>",
                "<IP_ADDRESS>"
            ]
        }
    },
    "controls": {
        "class": "Controls",
        "logLevel": "silly"
    }
}

@csiggydev  Can you please confirm the following:

In your declaration, defaultNextHopAddress should list SELF_IPs (i.e. internal self-ip <IP_ADDRESS> and <IP_ADDRESS> should be self-ips)
In Azure, they should have Route table correctly tagged and Route table should include internal subnet

Looking at error it seems that there is an issue with accessing Azure metadata service:
'Function error, retrying: getaddrinfo ENOTFOUND management.azure.com management.azure.com:443 Retries left: (x)'
It can be either a DNS issue or a permission issue

Can you confirm that you are able to reach management.azure.com from BIGIP
The list of permissions required is documented here: https://clouddocs.f5.com/products/extensions/f5-cloud-failover/latest/userguide/azure.html#rbac-role-definition
)

Also, you can send the qkview to my email<EMAIL_ADDRESS>

Hi @f5-chidambaram,

yes, those next-hop addresses <IP_ADDRESS> and <IP_ADDRESS> are the self-ip addresses of the F5s themselves, specifically on the 'transit' vlan.
The route-table 'ECPR-Transit-rt' has two relevant Tags for CFE as follows:
- 'f5_cloud_failover_label: centralus-f5-api-failover' and 'f5_self_ips: <IP_ADDRESS>,<IP_ADDRESS>'

I've tried variations of hard-coding the self-IPs in the declaration file, and also leveraging 'routeTag', and as stated previously, it works intermittently at best. Both F5s can resolve the FQDN management.azure.com and each F5 has the total list of Microsoft/Azure prefixes under each management route table, respectively. Furthermore, each f5 virtual machine has the appropriate permissions to a mutual storage account and route-table (Contributor access).
The QKViews will be sent to you soon. Thank you.

Hi @csiggydev: I'm afraid I did not receive the QKViews.
Do you still face the issue?
Will you be able to send the QKViews to<EMAIL_ADDRESS>/<EMAIL_ADDRESS>if the issue persists?

Closing. Please reopen if this is still an issue for you.


Device Unauthorized when using IMG_TYPE=google_apis_playstore

Issue
I am following the readme as I am interested in creating an android emulator with playstore.
The idea is that I would be able to run scrcpy to check the output. However, I keep getting the following error:
adb connect <IP>:5555
failed to authenticate to <IP>:5555

and with scrcpy:
scrcpy
scrcpy 2.1 <https://github.com/Genymobile/scrcpy>
ERROR: Device is unauthorized:
ERROR:     --> (tcpip)    <IP>:5555      unauthorized
ERROR: A popup should open on the device to request authorization.
ERROR: Check the FAQ: <https://github.com/Genymobile/scrcpy/blob/master/FAQ.md>
ERROR: Server connection failed

Steps followed:
docker build \
  --build-arg API_LEVEL=28 \
  --build-arg IMG_TYPE=google_apis_playstore \
  --build-arg ARCHITECTURE=x86 \
  --tag android-emulator .

docker run -it --rm --device /dev/kvm -p 5555:5555 android-emulator
Problems found
scrcpy says:
ERROR: A popup should open on the device to request authorization.

And following their docs it says we can connect via usb to solve this with the flag --otg or we need to accept it in the device.
In this case there is no device because it's an emulator.
The questions

Is this expected?
if yes, is there any way to accept the popup or connect to the emulator any other way to get around this?
could we somehow create a virtual usb device and use scrcpy with --otg and connect that way? (it won't work if USB debugging isn't enabled by default)

@lucasaas98 Did you ever figure this out? I am having the same issue, cannot get ADB to connect with authentication. I have copied the ADB keys and I have tried manually marking SKIP_AUTH = true

@lucasaas98 Did you ever figure this out? I am having the same issue, cannot get ADB to connect with authentication. I have copied the ADB keys and I have tried manually marking SKIP_AUTH = true

@faprobst nope, didn't even bother to try

I had the same symptom, so I googled it and found that the problem was caused by adbkey mismatch.
When I ran scrcpy with the -v container_name:/root/.android /root/.android option, scrcpy was executed.

I had the same symptom, so I googled it and found that the problem was caused by adbkey mismatch. When I ran scrcpy with the -v /root/.android /root/.android option, scrcpy was executed.

@PracticeofEno May I ask how can you connect using scrcpy? I have the same issue, even with pre-build docker image with mounted keys. I'm not sure what do you mean when you ran scrcpy with -v option


Multiple invalidation of Providers

Describe the bug
The bug concerns the invalidation of multiple providers, which leads to incorrect state management and unexpected behaviors in the application. When attempting to invalidate multiple providers, only the last one is invalidated correctly.
To Reproduce

Create a screen with two Widgets, each depending on a different provider.
Call the invalidate method for both providers.
Observe that only the last provider, affiliatedRestaurantsProvider, is triggered for invalidation.

Here is an example:

Expected behavior
All the providers must be invalidated and rebuilded.

Can you show us how you defined your riverpod?

A complete example is necessary to reproduce this.
As it is, I am capable of invalidating multiple providers at once. So there's likely something more to what you're saying here.

Closing in the lack of a minimal reproducing example


enabling picture in picture

Hello Developers.
As some video element has disablepictureinpicture property and causing confusion to users, I have enabled pictureinpicture mode even if the video element tag has a disablepictureinpicture property.

@googlebot I signed it!

@googlebot I fixed it.

@googlebot I fixed it.

NA.


Update what-is-sap-business-application-studio-8f46c6e.md

Thank you very much for your feedback. I have updated the documentation and you should see the changes in our next release.
I have added the missing "a". I have also divided the sentence describing the dev space tools into 2 and implemented your suggestion to add "that". Regarding "multi-target", our guidelines are to use "multitarget", so I will leave it for the sake of consistency.


Worldguard protection stuff.

Current Behavior
Weapons are able to break blocks by default in protected regions that do not explicitly have the weapon-break-block flag set to deny
Expected Behavior
Weapons (in my opinion anyways) should not break blocks in protected regions unless the flag is explicitly set to true, additionally they should (apparently) obey standard build protection according to the worldguard discord.
Steps To Reproduce

worldguard a region
fire an explosive or block-breaking gun
it destroys stuff
AHHHHHHHHHHHHHHHHHH

Version and Log
weaponmechanics v2.6.5
paper 1.20.1-170
Anything else?

I know I suggested you open an issue for this, but I changed my mind and now disagree... People will think that the config isn't working and come to the discord for solving "their problem" when they just didn't setup world guard flags.


Specifying multiple header directories

After reading this post, I find it somewhat limiting that there is no way to "merge" header directories in different locations that have the same name; the result is that one ends up with code coupled to biicode paths.
Shortly, the proposal is to eliminate the need for full biicode path includes by adding this capability:
Poco/Net/*.h: fenix/poco/Net/include, fenix/poco/NetSSL_OpenSSL/include

Thanks @aleks-f!
I agree, currently [include] mapping with Poco is solved with:
[includes]
   Poco/Net/*.h: fenix/poco/Net/include
   Poco/*.h: fenix/poco/Foundation/include

but to refer to NetSSL modules got to write full paths:
 fenix/poco/NetSSL_OpenSSL/include/Poco/Net/AcceptCertificateHandler.h
or: fenix/poco/NetSSL_Win/include/Poco/Net/AcceptCertificateHandler.h
which is an inconvenience.
I'm adding @drodri and @franramirez688 to discuss possible solutions.

Hi @aleks-f ,
That is a really interesting proposal! I'll talk @drodri about it and we'll study this possible new feature.
Thanks a lot for reporting it and I'll notify you with any news.


Unexpected result when comparing IP

CrateDB version
CrateDB 5.9.0-SNAPSHOT built 1064365
CrateDB setup information
Manual build following the instructions here: https://github.com/crate/crate/blob/master/devs/docs/basics.rst
Problem description
Consider the test case below. The third query could be unexpected since if the second query is evaluated to TRUE, which shows that the expression t0.c0 <= '<IP_ADDRESS>' is TRUE, thus the third query should return the row in the table. Otherwise the second query is unexpected.

Expected Result
As mentioned above.

Thanks for reporting this issue @suyZhong ! The fix will be available with the next hotfix release.


CPS capital gains treatment

This PR applies a temporary fix to impute short and long term capital gains when using CPS data.
The PR also makes a fix so that the /run_examples/run_ogusa_example.py script uses the Records.cps_constructor() method.

@hdoupe I merged PR #364 with the same unit test failure I'm seeing here.    I was hoping a clean push of the data files used for testing here would help pass this test, but they didn't.
I don't know why the tests fail on Travis CI, but pass locally.  Could it be with a tolerance on np.allclose()?  I haven't specified that anywhere, but perhaps this differs when run on Travis CI?  Other ideas?

@jdebacker I haven't figured out the error yet, but the warnings look like they are caused by the sse_mats array having NaN values in it.
I added the print statements in txfunc.py lines 558-561:
            # plt.show()
        print('sse_mat_new', sse_mat_new)
        print('thresh2', thresh2)
        print('sse_mat > thresh2', sse_mat_new > thresh2)
        print('(sse_mat_new > thresh2).sum() > 0', (sse_mat_new > thresh2).sum() > 0)
        if (sse_mat_new > thresh2).sum() > 0:
            # Mark the outliers from the second sweep above
            sse_mat_new2 = sse_mat_new.copy()
            sse_mat_new2[sse_big_mat] = np.nan
            if graph:
                # Plot sum of squared errors of tax functions over age
                # for each year of budget window

and got output:
HDoupe-MacBook-Pro:ogusa henrydoupe$ source activate ospcdyn
(ospcdyn) HDoupe-MacBook-Pro:ogusa henrydoupe$ py.test tests/test_txfunc.py::test_find_outliers -s -v -m 'not full_run and not regression' --showlocals
=========================================================================================== test session starts ============================================================================================
platform darwin -- Python 2.7.14, pytest-3.5.0, py-1.5.3, pluggy-0.6.0 -- /anaconda/envs/ospcdyn/bin/python
cachedir: ../.pytest_cache
rootdir: /Users/henrydoupe/Documents/OG-USA, inifile: setup.cfg
collected 2 items

tests/test_txfunc.py::test_find_outliers[2] MTRy :  1  observations tagged as outliers.
MTRy :  After second round,  1  observations tagged as outliers (cumulative).
sse_mat > thresh2 [[21. 22.]
 [20. 32.]
 [20. nan]] 32.1214034008 [[False False]
 [False False]
 [False False]]
PASSED
tests/test_txfunc.py::test_find_outliers[8] MTRy :  0  observations tagged as outliers.
PASSED

============================================================================================= warnings summary =============================================================================================
ogusa/tests/test_txfunc.py::test_find_outliers[2]
  /Users/henrydoupe/Documents/OG-USA/ogusa/txfunc.py:515: RuntimeWarning: invalid value encountered in greater
    thresh2 = (sse_mat_new[sse_mat_new > 0].mean() + se_mult *
  /Users/henrydoupe/Documents/OG-USA/ogusa/txfunc.py:516: RuntimeWarning: invalid value encountered in greater
    sse_mat_new[sse_mat_new > 0].std())
  /Users/henrydoupe/Documents/OG-USA/ogusa/txfunc.py:517: RuntimeWarning: invalid value encountered in greater
    sse_big_mat += sse_mat_new > thresh2
  /Users/henrydoupe/Documents/OG-USA/ogusa/txfunc.py:558: RuntimeWarning: invalid value encountered in greater
    print('sse_mat > thresh2', sse_mat_new, thresh2, sse_mat_new > thresh2)
  /Users/henrydoupe/Documents/OG-USA/ogusa/txfunc.py:559: RuntimeWarning: invalid value encountered in greater
    if (sse_mat_new > thresh2).sum() > 0:

-- Docs: http://doc.pytest.org/en/latest/warnings.html
================================================================================== 2 passed, 5 warnings in 11.48 seconds ===================================================================================
(ospcdyn) HDoupe-MacBook-Pro:ogusa henrydoupe$

@hdoupe Thanks for taking a look at this.  I'll remake my environment and look into the nan values.
Unfortunately, I'm running into similar issues over in the B-Tax repo.

B-Tax repo issues was from not being consistent with using CPS vs PUF micro data and is not fixed.
The test failure in this PR remains a mystery, but it seems likely that it has something to do with scipy.optimize().  The output I get locally from txfunc.txfunc_est()` (with the inputs used for testing) is:
Params =  [ 6.37000261e-22  2.73413298e-03  1.49073835e-08  1.39727771e-02
  2.32796890e-01 -3.69059719e-02  1.00000000e-04 -1.01967001e-01
  3.96030005e-02  1.02987671e-01 -1.30433574e-01  1.00000000e+00]
wsse =  19527.162030362062
obs =  3798

The output for the same when run on Travis CI is:
Params =  [ 6.37000261e-22  2.73404357e-03  1.34751071e-08  1.31120075e-02
  2.32797205e-01 -3.69059719e-02  1.00000000e-04 -1.01967001e-01
  3.96030037e-02  1.02987671e-01 -1.30433574e-01  1.00000000e+00]
wsse =  19527.16203
obs =  3798

The differences are in the 3rd and 4th parameters in the array of estimated parameters.  This could be related to some mix up between the CPS and PUF data because parameters 1 through 4 listed here are scaled by average income levels.  Checking now.

Ok - it's not differences in data.
From Travis CI: Checking Y =  7740.55345221 364739200.934
From local test: Checking Y =  7740.553452210688 364739200.9344876
Do maybe it's what is coming out of scipy.optimize()?
@hdoupe How can I see the version of Scipy used on Travis CI to compare to what I see from conda list in my local environment?

Click the red "x" by the travis icon. Then, you can see the installed versions if you click the down arrow by conda env update -f environment.yml.
It looks like travis is using SciPy 1.0.1. My tests ran fine locally with this version.

@hdoupe Thanks.
That is same version I'm running locally too - and tests pass.

The best I can figure is that there is some difference from scipy.optimize().  Inputs appear the same:
Local:
Param_init =  [1.         1.         1.         1.         0.39289996 0.25142765
 0.5       ]
mins and shift =  [-0.03690597 -0.101967   -0.13043357]
Data means =  32448.229691163007 8014.5537049564045 0.1249945122665625<PHONE_NUMBER>822012
Tax func type etc =  DEP etr

Travis CI:
Param_init =  [1.         1.         1.         1.         0.39289996 0.25142765
 0.5       ]
mins and shift =  [-0.03690597 -0.101967   -0.13043357]
Data means =  32448.2296912 8014.55370496 0.124994512267<PHONE_NUMBER>82
Tax func type etc =  DEP etr

I don't believe there is any randomness in the L-BFGS-B optimization algorithm, but there could be differences across platforms in the machine precision.  This SO thread discusses some relevant issues.
Given the potential issues here - can we test functions that rely on optimizers?

@jdebacker asked

Given the potential issues here - can we test functions that rely on optimizers? Is there anyway to be sure the types of numeric values (e.g., float vs double) are the same on both platforms?

I'm not really familiar with this type of problem. However, I hope we can find a way to reliably test these types of functions since OG-USA relies heavily on them. I just printed out the types for all of the inputs listed above:
# line 835 in txfunc.py
        print('Param_init = ', params_init, np.dtype(params_init[0]))
        print('mins and shift = ', np.array([min_x, min_y, shift]), np.dtype(min_x), np.dtype(min_y), np.dtype(shift))
        print('Data means = ', X.mean(), Y.mean(), txrates.mean(), wgts.mean(), X.dtype, Y.dtype, txrates.dtype)
        print('Tax func type etc = ', tax_func_type, rate_type)

and got output:
(ospcdyn) HDoupe-MacBook-Pro:ogusa henrydoupe$ py.test tests/test_txfunc.py::test_txfunc_est -v -s
============================================================================================================================ test session starts =============================================================================================================================
platform darwin -- Python 2.7.14, pytest-3.5.0, py-1.5.3, pluggy-0.6.0 -- /anaconda/envs/ospcdyn/bin/python
cachedir: ../.pytest_cache
rootdir: /Users/henrydoupe/Documents/OG-USA, inifile: setup.cfg
collected 1 item

tests/test_txfunc.py::test_txfunc_est Param_init =  [1.         1.         1.         1.         0.39289996 0.25142765
 0.5       ] float64
mins and shift =  [-0.03690597 -0.101967   -0.13043357] float64 float64 float64
Data means =  32448.2296912 8014.55370496 0.124994512267<PHONE_NUMBER>82 float64 float64 float64
Tax func type etc =  DEP etr
PASSED

========================================================================================================================== 1 passed in 7.27 seconds ==========================================================================================================================
(ospcdyn) HDoupe-MacBook-Pro:ogusa henrydoupe$

It looks like they are all np.float64 types. However, I have no idea how to control for different levels of precision on different machines.
What do you think about reducing the number of decimals in the dataframe before passing it to the optimize function:
    with open(os.path.join(CUR_PATH,
                           'test_io_data/txfunc_est_inputs.pkl'),
              'rb') as f:
        input_tuple = pickle.load(f)
    (_df, s, t, rate_type, output_dir, graph) = input_tuple
    df = _df.round(2) # round all inputs to two decimal places

Another option would be to raise the tolerance in the np.allclose function to something like rtol equal 0.05 or 0.1 (keeping atol=0).

@hdoupe writes:

I hope we can find a way to reliably test these types of functions since OG-USA relies heavily on them

Me too!
I've had some issues with different platforms and the use of MKL in the past.  To test if this an issue here, I added the nomkl package to environment.yml.  I then created a new environment with this, installed OG-USA, and ran test_txfunc.py.  Doing this causes test_txfunc.test_txfunc_est() to fail locally.  I printed the following input/output:
Param_init =  [1.         1.         1.         1.         0.39289996 0.25142765
 0.5       ]
mins and shift =  [-0.03690597 -0.101967   -0.13043357]
Data means =  32448.229691163007 8014.5537049564045 0.1249945122665625<PHONE_NUMBER>822012
Tax func type etc =  DEP etr
Raw param estimates =  [1.00000000e-12 6.87319703e+01 5.92567795e+00 1.14674142e+02]
Params =  [ 6.37000261e-22  2.73404765e-03  1.62463424e-08  1.48147213e-02
  2.32797191e-01 -3.69059719e-02  1.00000000e-04 -1.01967001e-01
  3.96030035e-02  1.02987671e-01 -1.30433574e-01  1.00000000e+00]
wsse =  19527.162030047846
obs =  3798
tax function type =  DEP
Checking Y =  7740.553452210688 364739200.9344876

This does not exactly reproduce the results from Travis CI, but it does show that using MKL makes a significant difference and causes the test to fail.  It seems likely that something is different in the implementation of SciPy across these platforms (such as the use of MKL or not) that is causing this test to fail.  However, I don't know a good way to handle this.

I've now marked test_txfunc.test_txfunc_est() to only run on "full runs".  This way it will not fail on Travis CI.  At the moment, I don't know of a better option given the different performance of Scipy on different platforms.


Update schema for doi 10.1038/srep01318 in rna_halflife_new collection

See issue #59 from datanator_rest_api

Use
{cell_line: gmxxxx, halflife: xxx} schema

Done in normalized schema version 2.0


⚠ Bofrost.de has degraded performance

In 991d512, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 926 ms

Resolved: Bofrost.de performance has improved in f7e8dca.


Prometheus Mixin Dashboard: add cluster filter variable

Proposal
Use case. Why is this important?
I would like to use the Prometheus Dashboards  from https://github.com/prometheus/prometheus/blob/main/documentation/prometheus-mixin/dashboards.libsonnet against a datasource with metrics from multiple Kubernetes clusters where Prometheus-Operator is deployed.
Here the current filter (job and instance) are not very helpful:

The jobname is identical over all cluster
the IPs from instance can also overlap between the cluster, as they are internal pod IPs. And it hard to find out which IP is currently from which cluster.

The kubernetes-mixins Dashboards all have a cluster filters included, which can be hidden for single instance use.
If this too Kubernetes specific, could a generic filter variable be added?

Hello from the bug scrub.
We believe this has been resolved by https://github.com/prometheus/prometheus/pull/13180. Please follow up if this is not the case.


Advanced parser for kernel boot params

Currently booster reads proc/cmdline and splits it by space. It works for majority of simple cases but it will fail if something more advanced is used in the command line.
For example parameters itself may use space. In this case quoting around the params need to be used. Per kernel documentation:

Double-quotes can be used to protect spaces in values

But it also looks like some bootloaders (e.g. grub) add quoting in a different way, like this "param=value with a space". So booster needs to handle quoting in both ways: param="value with a space" and "param=value with a space". This in addition to quotes around UUID handled here #6.
Besides spaces the values might contain escape symbols param="foo \" bar". And parser probably needs to handle other param delimiter, e.g. params might be separated with tabs.
It looks like we need a real advanced parser that handles all these cases. It worth reviewing kmod cmdline parser here to see if we can go similar way https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/tree/libkmod/libkmod-config.c?id=8742be0aa5ed14d28980eb706b08e8bdf650f21c#n528

TestLUKS2WithQuotesOverUUID test is failing now with
[    0.807449] booster: while parsing cmdline parameter unexpected " found at 98, input may be malformed, attempting to proceed
[    0.808704] booster: while parsing cmdline parameter unexpected " found at 135, input may be malformed, attempting to proceed
[    0.809946] booster: root=UUID="7bbf9363-eb42-4476-8c1c-9f1f4d091385": unable to parse UUID parameter UUID="7bbf9363-eb42-4476-8c1c-9f1f4d091385": expected input length is 36, got length 38
[    0.811831] booster: Press ENTER to reboot

I know whats causing this, I should have a small fix to address it and a few tests cases to ensure its covered better.


[Feature] Calendar widget

Summary
A calendar widget is a time grid. It'll be useful for showing events, schedules, etc. It's especially useful for teams that deal with deadlines like e-commerce companies, content creation companies, etc.
Features:

Ability to move events around
Ability to drill down to hour level, day level, week level, month level, year level
Creating events by selecting the time period

References:
https://fullcalendar.io/
https://github.com/nhn/tui.calendar
https://github.com/jquense/react-big-calendar
 Front conversations

@riodeuno @somangshu Can we schedule a discussion around this widget?

I think it would very valuable to have this widget integrated in appsmith

+1

Would've been great if this existed.. I'm building an app which MUST have it..

Hey @orenab1, thanks for showing your interest here. This widget is not yet planned to be developed. However I have a demo here, which might let you create an alternate solution. Do check this out and let me know what are your thoughts, The context you provide will help us triage this issue in order to pick it up

Hi, since I've written that post, I realized I don't actually need a
calendar.. I've also sticked with my Angular/.NET Core application..
But I'll definitely consider AppSmith next time.
Thanks!
On Mon, May 23, 2022 at 12:38 PM Somangshu Goswami @.***>
wrote:

Hey @orenab1 https://github.com/orenab1, thanks for showing your
interest here. This widget is not yet planned to be developed. However I
have a demo here
https://app.appsmith.com/applications/6138fbeddd7786286ddd4df1/pages/6138fbeddd7786286ddd4df3,
which might let you create an alternate solution. Do check this out and let
me know what are your thoughts, The context you provide will help us triage
this issue in order to pick it up
—
Reply to this email directly, view it on GitHub
https://github.com/appsmithorg/appsmith/issues/2410#issuecomment-1134431589,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5XIBCA2JSWU6VNDMIGSMTVLNGXTANCNFSM4VPOR6CA
.
You are receiving this because you were mentioned.Message ID:
@.***>

This is also something that I feel would be a great addition. Currently, I am using Appsmith alongside OpenProject as open project allows me to use a calendar to keep track of events etc, If I could move away from open project and have a calender widget on Appsmith this would make everything so much easier.
(CalDav/CardDav synchronization would also be great, lol)
I have looked at the sample app from @somangshu but I dont think that would cover what I am looking for as some tasks span over multiple days so the ability to have them displayed in a similar fashion to the below pic would be great

Hey @PaulMcF1987, thanks for providing us with the context; this widget is not yet on our roadmap and we dont plan on picking this up anytime soon. If you can help us understand your use case better we might be able to pull another solution with some other widgets; We probably can color code the date tiles to resemble the above UX.
cc @dilippitchika FYI

@somangshu I run a transport company, I use Appsmith to plan jobs. A calendar function would allow me to easily see what jobs are due on what days,
Also for job sourcing, it would allow me to easily identify at a glance which days still have jobs which need allocated.
It is not as easy to taker the details off of a table, especially when trying to work at speed.
Also, I have made an app for my brother who is a driving instructor, he has multiple appointments every day. A calendar function would help him see, at a glance if he had any spaces left for that specific day. Currently I have added a filter to the table to filter each day, however if trying to find a free day for a pupil to book a lesson, it can take a while as he can be required to filter through multiple days.
If a calendar was available, a glance should be enough to see where a space in the diary occurs and would save him a lot of time.

I understand @PaulMcF1987, Thanks for explaining the use case, I see how you wish to utilize the calendar widget and it makes sense as well.
However there could be a couple of other UX which can be thought of here for making this work well right now;
One of the pain points you mentioned was not being able to identify the days that need allocation. In that case another table / list showing the same in a chronological order might do the job. I infer from your explanation that your schema already can fit this UX.
Meanwhile, we will think about what kind of Impact this makes on the rest of our users and re-evaluate if this should be re-prioritized
cc @dilippitchika Any better ideas?

@somangshu I already have a few different queries which will arrange the table in different ways in order to make things a bit easier. But it is still no where near as easy as what a calendar widget would offer.
I genuinely believe that a calendar widget would be something that most/all businesses could benefit from.
All businesses out there require some sort of schedule and at present, whilst they may be using appsmith, they are more than likely going to have some sort of calendar/diary software which they use.
Currently, I use Openproject alongside appsmith
However, the ability to condense this into one app and get rid of the software that they are using for their time management and add this into appsmith I genuinely believe that would be a massive advantage to a lot of people businesses, and could be a good selling point for the software

Agreed @PaulMcF1987, we shall look into this requirement; Please subscribe to the issue to get notifications for any updates we leave here

another user in Discord is requesting this feature.
https://discord.com/channels/725602949748752515/1087360531846942820

@GreenFlux can you document the use case for us here?

@somangshu , from the user on Discord:

Our use case is mainly displaying timestamped data. For example there is a form that users can use to schedule events, but no way to have a more "natural" way to view them.
So the calendar widget would be purely for visualizing things, no CRUD features needed (for us at least)
Tooljet calendar widget provides everything we need. Tooljet in general is missing some features that make it worse, like code formatting, etc.

We recently added a custom widget where you can create a custom calendar widget.
Check out the post below where you can fork and try out the widget
https://community.appsmith.com/template/calendar


refactor prometheus cache to general output cache

Arista devices do not bundle Update messages into a single Notification, preferring to send all updates with their own timestamp (see https://github.com/openconfig/reference/blob/master/rpc/gnmi/gnmi-specification.md#3521-bundling-of-telemetry-update for details).  This can make it difficult to run event processors that expect multiple events in a single Notification.  Use of a per-subscription cache solves this -- the entire cache can be converted to events on a regular schedule and flushed by the upstream output per its needs (on scrape for prometheus, on a timer for Influx, etc)
As long as the flush interval is lower than whatever sample interval is being used in a subscription, no data would be lost.  Repeated sending of the same data (flushing more often than sample interval) doesn't result in extra storage, only extra network traffic, as most TSDB will discard identical points in the same metric

Testing today is showing something might be wrong with my configuration loading -- I can't correctly set the flush timer in the InfluxDB output.  It keeps setting it to github.com/nats-io/nats.go.DefaultReconnectJitterTLS<PHONE_NUMBER>)

Is there a reason that the prometheus cache required "target" in the subscriptions?  I've already forgotten twice to set set-target on a subscription and wondering why my updates weren't being cached

The caching is done per target ,that's why it's needed.
It could also be derived from the outputs.Meta source field.
I think the Enabled bool under gnmiCache is not needed, the presence of the struct can be an indication of cache being enabled.

I think the Enabled bool under gnmiCache is not needed, the presence of the struct can be an indication of cache being enabled.

Done, new changeset pushed

@bewing thanks again for the PR !


Update and build jpeglib from source

Description
This PR updates game and KscViewer tool to use latest jpeglib fetched from vendor.
This also allowed getting ride of some legacy libraries from project configurations.
This partially resolves the following ticket: https://github.com/stevewgr/ko/issues/38

Build passing: https://github.com/stevewgr/ko/runs/7592329194?check_suite_focus=true
Merging.


Reference to 'MGSwipeDirectionRightToLeft' is ambiguous

Since I upgraded my project to use frameworks (through Cocoapods), I cannot reference any of the enums, MGSwipeDirection, MGSwipeTransition, and so on. I tried following this suggestion, and still nothing.
If I don't use frameworks, it works fine, so my suspicion is it's something to do with that.
Any help would be great!

The issue was actually an import in an extension, that was only picked up now that the project uses frameworks.


If there is no inMessage use the inFaultMessage

I observed that when reading an entity from a response of a failed rest call the CXF throws a NullPointer exception.
I tracked this down to specific case where a JAXRS ReaderInterceptor is present on the chain and the response fails. When parsing the response this condition triggers a different path in JAXRSUtils.readFromMessageBodyReader which eventually results in a call to ProviderFactory.createMessageBodyReaderInterceptor which will throw a NullPointerException when there is no inMessage.
This fix tries to load  an inFaultMessage if there is no inMessage available which prevents the NPE and allows the code to execute successfully.
To reproduce create a JAX-RS Proxy client with a ReaderInterceptor. Then trigger a request that returns a 403 status code and try to 'readEntity' on the resulting ForbiddenException response.

Thanks for the PR. Could you add a unittest for it?

Sure, i'll see what i can do. Already looked at it and this method wasn't covered yet. So i'll have to write the test for the existing behaviour as well

BTW, Build failed due to a java OutOfMemory exception. Any way to restart it?

@deki I added the tests you mentioned. The build keeps failing due to issues with the Apache Jenkins. Do you permissions to restart the build?

The tests added in ProviderFactoryTest pass even without the changes in src/main, and so they are not really testing the change. I would have expected the tests to fail with the old code, and pass with the new.

@coheigea Yes. I started out by making the tests fail in those unit tests. However I had to setup a pretty large amount of mocks and additional classes. To prove this you basically need to setup a complete entity reader that parses an init stream and eventually calls a method that was initialised wrongly with a null value. I managed to get quite far but the test looked closed to a system test than a unit test.  Thinking about it again i concluded that the actual fix should be that the initialisation of the ReaderInterceptorMBR should just not accept a null value as message. So that is that actual fix with a associated unittest. The other new unittest do indeed not trigger on this error because it happens downstream in other flow, still i wrote them anyway so they might be useful to have. Long story short, the proof is the null check in the ReaderInterceptorMBR. I would be interested in adding a system test to prove that the entire chain works as designed now, but i would ask for some pointers on where to start.

Yes a system test sounds like the way to go. You can add it in systests/jax-rs. There are lots of tests in there that you can copy to try to reproduce the original error.


TN-979 take 3

Few bugs fixed:

include email on redirect to user.register, so it's correctly pre populated
exclude ALL the special roles when promoting the account.

@ivan-c sorry for the haste, but we need this on stg, not waiting for tests.


Update cats-effect to 3.4.3

Updates org.typelevel:cats-effect from 3.4.2 to 3.4.3.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.typelevel", artifactId = "cats-effect" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #12.

Superseded by #12.


Unable to use on mac

I followed the setup guide, I use the github visual client. When I launch unreal I get the following messages:

Yes, as stated in the Know Issues list of the README, the plugin is "Windows only (64 bits) -> Mac compiles but needs testing/debugging (Linux source control is not supported by Editor)"
This is because I have no access to a Mac, sorry!
If you are willing to help, we could add more debug logs to your copy of the plugin to try fix this

I don't know much about git, but if you tell me what to do I sure can help.

Who created the UE4Editor-GitSourceControl.dylib for Mac that is distributed with the 4.7 engine. I am a Mac developer and we are planning on using Unreal and having a GIT plugin is a must.

Epic did, and perhaps the Git plugin was tested successfully on certain
configuration, but does not handle well certain paths (like spaces on the
path to the project) or other things they did not yet.
Le jeu. 5 mars 2015 01:37, Dave Carlton<EMAIL_ADDRESS>a écrit :

Who created the UE4Editor-GitSourceControl.dylib for Mac that is
distributed with the 4.7 engine. I am a Mac developer and we are planning
on using Unreal and having a GIT plugin is a must.
—
Reply to this email directly or view it on GitHub
https://github.com/SRombauts/UE4GitPlugin/issues/23#issuecomment-77282810
.

Today I had a chance to test the Git plugin with a Mac, and unfortunately it does not work at all, whether there is a space or not in the path to the Project.
The problem come from the double-quotes added around path to handle space (like "/Users/Xxx/Unreal Projects/TestGit") : those does not work with the current UE4 FPlatformProcess::ExecProcess() method on Mac.
I've try with simple-quote instead, but this does not work either.
I've try removing them altogether, and this works if you don't have any space in any of your paths.
I'll report this to Epic, as I have no way to work seriously on resolving this issue.

Fixed on the Unreal Engine master branch with my pull request:
https://github.com/EpicGames/UnrealEngine/commit/2196a60dd6e5e59576a0e6ade6c3a4b621b4fe86


When the URL contains more than 65534 characters, the error code returned by Hyper is not 414.

The length of the from_shared method of the third-party library http::Uri is verified， The maximum length is (u16::MAX - 1).

Good catch! We could add a check for the length just before calling Uri::from_shared, and if too long, return a Parse error. An integration test in tests/server.rs would be good too.

First pull request. Happy to change based on feedback.


Add support for roof:levels

Description
If editing or creating a building, there is a text box for the "levels" (see screenshot below). It isn't clear for users that this describes only the building's levels, not the roof's. A short explanation or just an additional box for roof levels would be helpful.
Screenshots

This is already part of #1829, which is also part of https://github.com/openstreetmap/iD/issues/2550#issuecomment-78273632 .


Ability to remove existing filters

Hi,
The default ApplyXmlActionComments filter is clearing out any existing responses. That means that any 200 or 204 auto-generated responses by swashbuckle will be removed. In some cases this is fine, but we would like to change the ability to change this behaviour.
We can do this by creating our own filter, the only problem is that we can not remove the existing filter.  It would be good if filter collections would exposed, or options to remove them added.
P.s. the code for generating 200 and 204 responses could be one of the default a filters too.

I don't think this feature is necessary. Filters need to be explicitly added by application filters so if you don't want to use one, just don't enable it.
In the case of XML comments, a call to IncludeXmlComments will enable the ApplyXmlActionComments and ApplyXmlTypeComments filters. If you remove this call, neither will be enabled. If you want to enable one and not the other just drop down to the generic SchemaFilter or OperationFilter methods:
c.OperationFilter(() => new Swashbuckle.Swagger.XmlComments.ApplyXmlActionComments(filePath));

It's also worth noting that the future version for ASP.NET Core Swashbuckle.AspNetCore provides a little more flexibility around listing and documenting responses.


[Question] Having issues with autorization after initial setup

I ran through the initial setup successfully, ran the setup command which went fine.  When attempting to do Get-GSUser I get an error
Get-GSUser : Exception calling "Execute" with "0" argument(s): "Error:"unauthorized_client",Description:"Client is unauthorized to retrieve access tokens using this method.", Uri:"""

https://apps-apis.google.com/a/feeds/emailsettings/2.0/,
https://mail.google.com/,
https://sites.google.com/feeds,
https://www.google.com/m8/feeds/contacts,
https://www.googleapis.com/auth/activity,
https://www.googleapis.com/auth/admin.datatransfer,
https://www.googleapis.com/auth/admin.directory,
https://www.googleapis.com/auth/admin.directory.customer,
https://www.googleapis.com/auth/admin.directory.device.mobile,
https://www.googleapis.com/auth/admin.directory.domain,
https://www.googleapis.com/auth/admin.directory.group,
https://www.googleapis.com/auth/admin.directory.orgunit,
https://www.googleapis.com/auth/admin.directory.user,
https://www.googleapis.com/auth/admin.directory.user.readonly,
https://www.googleapis.com/auth/admin.directory.user.security,
https://www.googleapis.com/auth/admin.directory.resource.calendar,
https://www.googleapis.com/auth/admin.directory.userschema,
https://www.googleapis.com/auth/admin.reports.audit.readonly,
https://www.googleapis.com/auth/admin.reports.usage.readonly,
https://www.googleapis.com/auth/apps.groups.settings,
https://www.googleapis.com/auth/apps.licensing,
https://www.googleapis.com/auth/calendar,
https://www.googleapis.com/auth/drive,
https://www.googleapis.com/auth/gmail.settings.basic,
https://www.googleapis.com/auth/gmail.settings.sharing,
https://www.googleapis.com/auth/plus.login,
https://www.googleapis.com/auth/plus.me,
https://www.googleapis.com/auth/urlshortener,
https://www.googleapis.com/auth/userinfo.email,
https://www.googleapis.com/auth/userinfo.profile

Well dang. I removed the authorized client and put the client ID back in and it accepted it and now things work. My bad, thanks for the quick response!!

no worries, glad it was quick and easy!


llvm-embedded: Add focal build

When the CI moves away from bionic we'll need focal images to build
against.

Checklist

[ ] Language changes are updated in man/adoc/bpftrace.adoc and if needed in docs/reference_guide.md
[ ] User-visible and non-trivial changes updated in CHANGELOG.md
[ ] The new behaviour is covered by tests

sadly it has been broken for a whlie :(
The LLVM build actually pulls in LLVM & CLang from cmake and does the whole build magic stuff. For some reason  it cannot find LLVM just after building it
[100%] Built target embedded_llvm
[ 50%] Built target embedded_llvm
[ 57%] Creating directories for 'embedded_clang'
 CMake Error at CMakeLists.txt:66 (find_package):
  Could not find a package configuration file provided by "LLVM" with any of
  the following names:

    LLVMConfig.cmake
    llvm-config.cmake

It was (like many things :/ ) on my fix list but as we had an image that worked I found it low priority. Also because building LLVM is a huge pain and my hardware isn't that great. I ended up getting a big box at digital ocean for it, but thats adding $$ fast if I cant dedicate time.
Luckily we don't have to rush with this just yet. The embedded build builds BCC from source too (see docker/Dockerfile.ubuntu-glibc) so that will work (hopefully for a while).
And our build is not fully static, libc is still dynamically linked so keeping the bionic build is beneficial for older systems

Duplicate of #2372.


Fix user not being told that FirstPhase story quests fail in 10 years

Fixes #133 . Now those quests will appear with the days until failure much like other quests.
Unfortunately there's a few hours game time ( 10 seconds or so real life time) until the quests are updated after getting them. See code comments.

Should refactor this into a separate IPatch inheriting class similar to DisciplinarianPerkPatch fix that doesn't use Harmony. Need to find where the time frame is in code and extract it instead of hard-coding FirstPhaseTimeLimitInYears.

Go ahead.

Thought i'd take a stab at it. Moved patch to class EarlyStoryVisibleTimeoutPatch. Can squash the commits if necessary.

@Tyler-IN  Is that good, do you think?

@Tyler-IN should I change the PR to be merged into dev branch, or keep it going into master?


Build fail if g++ is not installed

On a simple docker with gcc but not g++ installed, lexbor does not build. CMake fails, but it shouldn't. If I'm right, lexbor doesn't need a c++ compiler. This force extra installation of c++ build tools.

@trikko
I have C++ turned on for one test.
Okay, I do this: by default, LEXBOR_BUILD_TESTS_CPP will be OFF, and the C++ compiler will only be included if LEXBOR_BUILD_TESTS_CPP=ON.
Now the C++ compiler is enabled regardless of the values passed in.

@trikko
Fixed in https://github.com/lexbor/lexbor/commit/14166847cfa85d80c9041f5387014961f70f3831.
Thanks for the report!

yay it works!


Dubious metric names in Prometheus

While inspecting Cassandra related metrics in our Prometheus server, I noticed that some metrics were badly re-labelled from the Cassandra model to the Prometheus model leading to numerous Prometheus metric .
For example:

org_apache_cassandra_metrics_connection_large_message_dropped_tasks_201_24_56_224_7000
org_apache_cassandra_metrics_connection_large_message_dropped_tasks_201_24_110_239_7000

I'm using the new metric endpoint without any additional configuration.
Impacted metrics are the following (I stripped the port, ip address, etc. to obtain expected metric name):
io_cassandrareaper_management_ICassandraManagementProxy_connections
io_cassandrareaper_management_jmx_JmxCassandraManagementProxy_cpicassandracluster_repairStatusHandlers
io_cassandrareaper_service_SegmentRunner_abort
org_apache_cassandra_metrics_connection_gossip_message_completed_tasks
org_apache_cassandra_metrics_connection_gossip_message_dropped_tasks
org_apache_cassandra_metrics_connection_gossip_message_pending_tasks
org_apache_cassandra_metrics_connection_large_message_completed_bytes
org_apache_cassandra_metrics_connection_large_message_completed_tasks
org_apache_cassandra_metrics_connection_large_message_dropped_bytes_due_to_error
org_apache_cassandra_metrics_connection_large_message_dropped_bytes_due_to_overload
org_apache_cassandra_metrics_connection_large_message_dropped_bytes_due_to_timeout
org_apache_cassandra_metrics_connection_large_message_dropped_tasks
org_apache_cassandra_metrics_connection_large_message_dropped_tasks_due_to_error
org_apache_cassandra_metrics_connection_large_message_dropped_tasks_due_to_overload
org_apache_cassandra_metrics_connection_large_message_dropped_tasks_due_to_timeout
org_apache_cassandra_metrics_connection_large_message_pending_bytes
org_apache_cassandra_metrics_connection_large_message_pending_tasks
org_apache_cassandra_metrics_connection_small_message_completed_bytes
org_apache_cassandra_metrics_connection_small_message_completed_tasks
org_apache_cassandra_metrics_connection_small_message_dropped_bytes_due_to_error
org_apache_cassandra_metrics_connection_small_message_dropped_bytes_due_to_overload
org_apache_cassandra_metrics_connection_small_message_dropped_bytes_due_to_timeout
org_apache_cassandra_metrics_connection_small_message_dropped_tasks
org_apache_cassandra_metrics_connection_small_message_dropped_tasks_due_to_error
org_apache_cassandra_metrics_connection_small_message_dropped_tasks_due_to_overload
org_apache_cassandra_metrics_connection_small_message_dropped_tasks_due_to_timeout
org_apache_cassandra_metrics_connection_small_message_pending_bytes
org_apache_cassandra_metrics_connection_small_message_pending_tasks
org_apache_cassandra_metrics_connection_timeouts_total
org_apache_cassandra_metrics_connection_urgent_message_completed_bytes
org_apache_cassandra_metrics_connection_urgent_message_completed_tasks
org_apache_cassandra_metrics_connection_urgent_message_dropped_bytes_due_to_error
org_apache_cassandra_metrics_connection_urgent_message_dropped_bytes_due_to_overload
org_apache_cassandra_metrics_connection_urgent_message_dropped_bytes_due_to_timeout
org_apache_cassandra_metrics_connection_urgent_message_dropped_tasks
org_apache_cassandra_metrics_connection_urgent_message_dropped_tasks_due_to_error
org_apache_cassandra_metrics_connection_urgent_message_dropped_tasks_due_to_overload
org_apache_cassandra_metrics_connection_urgent_message_dropped_tasks_due_to_timeout
org_apache_cassandra_metrics_connection_urgent_message_pending_bytes
org_apache_cassandra_metrics_connection_urgent_message_pending_tasks
org_apache_cassandra_metrics_hints_service_hint_delays
org_apache_cassandra_metrics_hints_service_hint_delays_count
org_apache_cassandra_metrics_hints_service_hints_created
org_apache_cassandra_metrics_hints_service_hints_not_stored
org_apache_cassandra_metrics_inbound_connection_corrupt_frames_recovered
org_apache_cassandra_metrics_inbound_connection_corrupt_frames_unrecovered
org_apache_cassandra_metrics_inbound_connection_error_bytes
org_apache_cassandra_metrics_inbound_connection_error_count
org_apache_cassandra_metrics_inbound_connection_expired_bytes
org_apache_cassandra_metrics_inbound_connection_expired_count
org_apache_cassandra_metrics_inbound_connection_processed_bytes
org_apache_cassandra_metrics_inbound_connection_processed_count
org_apache_cassandra_metrics_inbound_connection_received_bytes
org_apache_cassandra_metrics_inbound_connection_received_count
org_apache_cassandra_metrics_inbound_connection_scheduled_bytes
org_apache_cassandra_metrics_inbound_connection_scheduled_count
org_apache_cassandra_metrics_inbound_connection_throttled_count
org_apache_cassandra_metrics_inbound_connection_throttled_nanos

None of those metrics seems documented in https://cassandra.apache.org/doc/stable/cassandra/operating/metrics.html#client-metrics but it's easy to find them in Cassandra source code.
Should the default relabel configuration be updated to take those metrics into account or am I doing something wrong?

Should the default relabel configuration be updated to take those metrics into account or am I doing something wrong?

Should definitely be added. The current relabeling rules are based on the documented metrics, but clearly this isn't enough to get everything done correctly.
What Cassandra version was used?

In any case, the metrics names come from these lines:
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/metrics/InternodeInboundMetrics.java#L54
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/metrics/InternodeOutboundMetrics.java#L122
So we will need a relabeling rule that would catch these for IPv4 & IPv6 and put the target node as a label instead of allowing it to stay in the metricName.

We are using Cassandra 4.1.3 .
Where are the rules defined? There is this file https://github.com/k8ssandra/management-api-for-apache-cassandra/blob/f85032fa787a4e2a42a37ad16a94eeefa70ff907/management-api-agent-common/src/test/resources/collector-full.yaml (linked from the doc). Butsrc/test/resources  leads me to believe that it's not the file that's being used.

The default rules (you can define your own and they get appended to these) are in https://github.com/k8ssandra/management-api-for-apache-cassandra/blob/master/management-api-agent-common/src/main/resources/default-metric-settings.yaml

And here's an example how to append your own rules (like the ones I added to the default):
CassandraDatacenter changes:
https://github.com/k8ssandra/cass-operator/blob/14ce1a95f613104234cd3dba9154c4a428cdfeb7/tests/testdata/default-single-rack-single-node-additional-volumesources.yaml#L25
And the mounted ConfigMap:
https://github.com/k8ssandra/cass-operator/blob/14ce1a95f613104234cd3dba9154c4a428cdfeb7/tests/testdata/configs/my-metrics-config.yaml#L8


Raise ValueError when merge_mode is unknown in Bidirectional#call

Summary
In Bidirectional#call , when the merge_mode is unknown, currently there is no error.
We should raise error so that user becomes aware of the missing value.
Related Issues
PR Overview

[ ] This PR requires new unit tests [y/n] (make sure tests are included)
[ ] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[ ] This PR is backwards compatible [y/n]
[ ] This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

From https://travis-ci.org/keras-team/keras/jobs/433841492 :
The error was from tests/conftest.py which was not touched by this PR.

It seems from the result of the build that you have an issue with a mix of tabs and spaces. Can you look into that?


[5.7] Modifies Route::redirect to use 302 as the default status code instead of a 301

A 301 status is a permanent redirect from one location to another, these redirects are cached by browsers, which is the expected behaviour:

A 301 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls.

Laravel defaults to using a 301 in the Route::redirect method. This is unfortunately quite dangerous: if a developer does not know that a 301 is going to be used, and that it is going to be cached with no expiry, their users will be permanently redirected with no way for the developer to undo the redirect.
Laravel does not default to a 301 anywhere else, for example the redirect helper defaults to a 302.
I have performed a search of GitHub for open source Laravel projects using the Route::redirect method and found the following:

Many developers are explicitly defining their status code as 301
Some developers are using the redirect method within conditionals without specifying a 302

This indicates to me the following things are true:

Developers expect that the default is not 301
Developers who wish to use a 301 are explicitly defining it
Developers are shipping applications that will perform in unintended ways because they do not realise that by default all redirects are permanently cached by their user's browsers

Therefore I propose that the default be changed to a safe 302. Due to the permanent nature of a 301 it should only be used when explicitly defined by a developer.
Edit to add: this Super User post where people discuss accidentally using 301s and trying to deal with the cached result has over 230,000 views, which indicates that there are a lot of developers uninformed about the result of using a 301.
Thanks!

I would argue that the reason most people explicitly pass 301 as the status code is because that's what the example in the documentation does.
A better approach to this would be to change the documentation, to clarify that 301 is the default status code and that means redirections are permanent.
Redirect routes are most useful for migrating old URLs to new ones (which is generally a permanent change), or to alias common typos (i.e.: redirect '/user/1' to '/users/1', also a permanent thing). Using redirect routes for temporary redirects should be the exception, not the rule.
Instead of forcing everyone who knows what a permanent redirect is, and actually bothered to look at a method signature before using it, to go back and change all their routes files to explicitly add a 301 status codes, could we just make a better effort to educate new users?

There are many different use cases for the redirect method. A permanent redirect from a legacy route is one of them, but there are many more that don't involve permanency, such as conditional redirects and upcoming-feature "coming soon" page.
The documentation would need to read something like:

⚠This method uses a 301 status code by default, which is a permanent redirect. A permanent redirect is cached by the user's browser with no expiry, meaning that once the redirect has been followed by a user you will not be able to change that redirect for that user until their cache expires (which can take months, or years). This should only be used when you are absolutely sure that you will not need to use this route again. If you do not wish to permanently redirect this route, pass a 302 status code as the third parameter.

When a warning like that is neccessary, why not change the default behaviour to be safe and require explicit opt-in to the dangerous behaviour? There are no breaking changes with this change, all of your redirects (without an explicit status code) will continue to redirect, and if you wish for them to be cached permanently by your user's browser then you can add the 301 parameter -- which should take a couple of seconds even with hundreds of redirects.
The framework should be consistent and safe by default. A 302 is used for all other redirects (by virtue of using the redirect helper) -- it doesn't make sense to deviate from this for one class of redirect, and thus require a warning in the documentation. A user, like yourself, who understand the behaviour of a 301 and wants the behaviour of a 301 should opt-in.

I'm going to revert this. I don't think the Route::redirect and redirect helpers necessarily need to be consistent. They serve different purposes. If I am hard-coding a redirect right into my route's file like Route::redirect allows, I think the more common use case is that is a permanent redirect.

@taylorotwell my concern isn't that Laravel should be consistent for the sake of being consistent, Laravel exists to make developers lives easier and inconsistency is sometimes a part of that: my concern is that a 301 has severe side effects and so unlike, say, arguments about needle, haystack vs. haystack, needle, this isn't just a "whoops, I made an error in my code, I'll fix it and run my tests again / deploy the new version" it's a problem that can't be easily debugged or fixed because the damage lives on in user's caches indefinitely.
There are many ways to use redirect routes and certainly a permanent redirect is one of them and the most common, but in that case given the consequences associated with a 301 it should be up to the developer to actively decide that they want the redirect to live on in their user's cache forever by opting in to a 301.
If a 301 didn't have these side effects then I'd absolutely agree that it makes complete sense to be inconsistent here. I also understand that the api for redirect is pretty ugly when including a 301 if you do want a permanent redirect and it probably feels unnecessary, especially for someone who understands what a 301 is and the consequences of it, but for a developer who doesn't have that knowledge and ships an application with a 301 they don't know about, it's going to be a nightmare to debug the consequences and rectify them.
If making the redirect methods api cleaner is more important than ensuring developers don't shoot themselves in the foot, then I think at the very least the documentation should include a warning about the consequences of a 301 as it's quite common for developers not to be aware of them. I'm happy to update the documentation with that warning if this is reverted.
Thanks!


Native arrays are indexed three times

The problem
There are two arrays, one of them pointing here, and one native array. The first and last point to the same place, or close.
Suggestions
One problem here is the confusion of the name, array with the generic name for them. All of them should be changed to native arrays probably. But there are outstanding issues like #2257. In the meantime, probably a single indexing term would be the best.

indexing & searching has been overhauled, I can't see this issue when searching on @finanalyst 's site (whose latest updates will be in prod shortly).


Check in both pg and mysql schema in src code

Description
This PR allows us to checkin schema for both postgres and mysql at the same time in the source code and switch between the two based on config feature.
Test plan
cargo clippy

LG do we still need schema.rs under src?

No, we shouldn't need it anymore. It is getting replaced with pg.rs


Should we add info button on bottom left to toggle shortcuts ?

Something like this can be added which opens the shortcut modal.
Currently there is no way on Excalidraw which says Press ?

Yeap.. that's the duplicate of #1233.
Simple questionmark would do.


feat: Update height of QUERY_DYNAMIC_TEXT to 200px fixed

Description
This PR updated QUERY_DYNAMIC_TEXT field height to 200px. Before it was configured to 100vh / 4
Fixes #34322
Automation
/ok-to-test<EMAIL_ADDRESS>:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

/build-deploy-preview skip-test=true

It is overkill to run @tag.All


Dropped empty horizontal range data

I use imu(sparkfun imu m0), odom(provide by arduino), scan(urg laser scan) and cartographer(HEAD detached at 1.0.0 master), there is my lua file:
include "map_builder.lua"
include "trajectory_builder.lua"

options = {
  map_builder = MAP_BUILDER,
  trajectory_builder = TRAJECTORY_BUILDER,
  map_frame = "map",
  tracking_frame = "base_imu_link",
  published_frame = "base_link",
  odom_frame = "odom",
  provide_odom_frame = true,
  publish_frame_projected_to_2d = false,
  use_odometry = true,
  use_nav_sat = false,
  use_landmarks = false,
  num_laser_scans = 1,
  num_multi_echo_laser_scans = 0,
  num_subdivisions_per_laser_scan = 10,
  num_point_clouds = 0,
  lookup_transform_timeout_sec = 0.2,
  submap_publish_period_sec = 0.3,
  pose_publish_period_sec = 5e-3,
  trajectory_publish_period_sec = 30e-3,
  rangefinder_sampling_ratio = 1.,
  odometry_sampling_ratio = 1.,
  fixed_frame_pose_sampling_ratio = 1.,
  imu_sampling_ratio = 1.,
  landmarks_sampling_ratio = 1.,
}

MAP_BUILDER.use_trajectory_builder_2d = true
TRAJECTORY_BUILDER_2D.num_accumulated_range_data = 10
TRAJECTORY_BUILDER_2D.use_imu_data = true

return options

I check my urdf file and tf_graph ,tf_tree, I think they are ok without problems, but the cartographer is ceaselessly pose the warn about without range data.
[ WARN] [1534335805.047046943]: W0815 20:23:25.000000  3824 local_trajectory_builder_2d.cc:215] Dropped empty horizontal range data.
[ WARN] [1534335805.147245481]: W0815 20:23:25.000000  3824 local_trajectory_builder_2d.cc:215] Dropped empty horizontal range data.
[ WARN] [1534335805.246809306]: W0815 20:23:25.000000  3824 local_trajectory_builder_2d.cc:215] Dropped empty horizontal range data.

There is a link to tf graph.
What is the problem with my demo? Who can help me? Thank you very much!!

@gaschler when i just use odom and laser scan, the cartographer is ok without any warning, i can see the map in rviz. But when i launch the imu node and set TRAJECTORY_BUILDER_2D.use_imu_data = true , the cartographer requires the tracking_frame must be "base_imu_link" (but the imu link name in urdf file is "imu_link", the cartographer will say "base_imu_link" don't exit, so i change "base_imu_link" to "imu_link" ).
When i launch the imu node, i just change the tracking_frame and set the item TRAJECTORY_BUILDER_2D.use_imu_data with true. So if i use imu, are there any matters needing attention?

@gaschler I also use the rosbag tool to record a bag file and play the bag. There is alse the same warn information what i posed above.
I use tostopic tool can accept the imu data, odom data and laser scan data. Is real a timestamp mismatch problem?

@gaschler resently, I do some tests and find that when i set the imu's origin is (0,0,0) so that the positions are the same between imu and base_link. Then there are not warning information, but i do not think this is the real reason cause this issue.


Tx share url is not correct

How to reproduce:

Go to Activity tab at the bottom of the screen
Click on any transaction
Click the button on the upper-right corner to go to Transaction Details page
Click the share button on the upper-right corner

and you see the url link to the blockchain explorer misses '/tx/' part before the tx id, which causes a 404 page not found error

Fixed with this PR: https://github.com/symblox/alpha-wallet-android/pull/5


Visual Challenge!

I made a View of one X project.
The Result is:

I have a Frame with option to take a photo from gallery or camera, and the result is renderer inside of the Frame with Image control. Also, a severals of Picker and one Entry with button at the bottom of page.
The Good:

New way of Frame is renderer, is really nice to see in iOS and Android.

The Bad:

The Picker is not showing the given Title prop (Picker 1).
To display option camera or gallery I use DisplayActionSheet, but in iOS crashes, only in Android works good.
The issue with the margin and scroll for FlexLayout made the view showing bad in Android.
In iOS the consecutive Pickers showing bad.

Regards!

Thanks @mimunoz. fyi - we have a bug report for the DisplayActionSheet issue with Shell. That'll be fixed soon.
I haven't seen the other issues with the pickers, so that's a nice find. Thanks!

@mimunoz I need you email address please<EMAIL_ADDRESS>


lang="jade" to lang="pug", Solved #72

lang="jade" to lang="pug", Solved #72

Pug is already supported: https://github.com/vuejs/vue-syntax-highlight/blob/master/vue.YAML-tmLanguage#L98-L112

一点风格都没有了

Hi guys,
I'm kinda confused. When have
Do I need to install or set some things up?
I use VCS 1.8.
Thank you a lot!

@grafa I think the issue is about the extension,
so you have to modify the config of the extension in the VSC extension folder.
Go to ~/.vscode/extensions/hollowtree.vue-snippets/syntaxes
and find the vue.tmLanguage, open it, and replace
<string>(?:^\s+)?(<)((?i:template))\b(?=[^>]*lang="jade(?:\?[^"]*)?")</string>

to
<string>(?:^\s+)?(<)((?i:template))\b(?=[^>]*lang="pug(?:\?[^"]*)?")</string>

might solve your problem.

Hi, thanks for reply.
In the config file there are both variants. Please can you take a brief look on the file?
Thanks a lot.
vue.tmLanguage.txt

@grafa Just change L:268
<string>(?:^\s+)?(<)((?i:template))\b(?=[^>]*lang="jade(?:\?[^"]*)?")</string>

to
<string>(?:^\s+)?(<)((?i:template))\b(?=[^>]*lang="pug(?:\?[^"]*)?")</string>

and don't modify other jade-things.

Amazing, works!
Note:
But when I have in my .vue file lang="jade" the syntax highlight is almost off. So this is temporary solution I guess.


Add support for switching accounts

Like @fluffels pointed out in #6, it would be great to have an option to setup multiple instances of JIRA and be able to switch between them, I suggest to add support inside the main config file because it's a better way to centralize the general settings.

@miguelmich you're happy with the command itself on the #6 ? it's just the implementation you don't like?

@fluffels yes, I think there is a better way to handle multiple accounts, the main idea that I have in mind is to save an array of the current credentials object and then it will be easy to "activate" one of those instances like, for example, jira config switch and then display a prompt with the current options.
Apart from this, the implementation that you did looks good, but it should be located in a method inside the config class and not inside the jira.js class which acts like some kind of "command router" between the commander index and the different classes.
The roadmap in order to make this new feature works could be:

Add a command to setup multiple accounts using the current config file, and set an "active" parameter which determinates the active instance
Modify the current init method in order to get the "active" instance and load it from the start
Add config commands to modify & remove the different instances


update org.activiti.core.common:activiti-core-common-dependencies to 7.0.7

UpdateBot pushed maven dependency: org.activiti.core.common:activiti-core-common-dependencies to: 7.0.7

UpdateBot commands:
updatebot push-version --kind maven org.activiti.core.common:activiti-core-common-dependencies 7.0.7 --merge false

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


Minor issue with parentheses in test names

If you create a test name that ends with parenthesized text and then you change the name by removing parentheses by backspacing, the left parenthesis remains in the view until you restart VSCode.
To duplicate, create a test with name  # @name test (this and that)

Then just use the backspace key to remove all parenthesized text including poth parentheses, but it will still show the left parenthesis in the Testing view:

You will need to restart VSCode to have the Testing view show the updated name without the left parenthesis.
A really minor issue, but I once spent a few minutes messing with it and trying to understand what is going on.

That's a good one. I had a cache and the label was not updated on hits from the cache. But the cache usually didn't work because the name was included in the cache, except when only special characters were changed.


When does new version get release?

Is there a schedule for new releases? The STM32L4R5 support has been merged in and just curious when a new release will happen.
Thank you.

0.15 was released just now, including your L4R5 changes, thanks for your help!


get nonzero xx_si controls

What changes does this PR introduce?
Enable nonzero xx_ controls for sea ice
What is the current behaviour?
xx_[siarea,siheff] for sea ice are all zeros even though we get nonzero ADJ[heff,area]
What is the new behaviour
non-zero xx_si[area,heff] that matches corresponding ADJ at initial time.
Does this PR introduce a breaking change?
No expected breaking.
Other information:
Suggested addition to tag-index
(To avoid unnecessary merge conflicts, please don't update tag-index. One of the admins will do that when merging your pull request.)

For verification, I used the lab_sea code_ad as a test, added my code in, and got non-zero xx_siheff and xx_siarea that matched identically (visually) the ADJheff and ADJarea at initial time.


Change build.sh script to point to Helm 2 compatible version of Fabrikate

Closes #1412
Instead of the most recent version of Fabrikate, the script will now point to the most recent MAJOR version of 0.x.x
This ensures that bedrock is using a Helm 2 compatible version of Fabrikate.

@andrewDoing what do you mean by MAJOR version of 0.? What is the expectation of Fabrikate version numbers?

@andrebriggs The Fabrikate version numbers will change when a new release is cut. Major Version 0.x.x is guaranteed to be helm 2 compatible. Once new releases are cut, we can revisit this script and potentially point it at Major Version 1.x.x which will also be helm 2 compatible, but will receive new updates. Major version 2.x.x will be helm 3 compatible. Link to where this is described.

Manually ran the build here: https://dev.azure.com/epicstuff/bedrock/_build/results?buildId=28898&view=results


Add event demux code to async-tracker

Moves responsibility to match/filter async method name to async-tracker but allows user to register a 'default' handler which is notified about all async methods.
Fixes 2 issue in https://github.com/strongloop/async-tracker/issues/1

@piscisaureus PTAL

Two observations:

The 'default' handler is invoked only when there are no other listeners for the event. I wonder if that's really what users would expect. One of the effects is that adding a listener now has the potential side effect of partially "disabling" a default listener.

It's a bit out of scope for this patch, but the pervasive use of Object.keys when iterating over listeners is probably the worst you could do in terms of performance. for (element in list) would probably be a better option.

@piscisaureus I was modeling the default handler on a switch statement. The other option was to provide a regex matcher but that would slow things down even more.
I will make a separate issue to replace Object.keys

@cbrichford Please take a look

The API looks good to me and includes all the suggestions I made.  I did not carefully review the tests or code unrelated to the API contract.


nav bar and coaching marks..

hey, awesome effort! Testing it out, and my main need for coaching lives up in the nav bar, and the graphics are rendering under the bar, which makes it very confusing to use. For now I will create a fake screen with controls to be accessible, but thought to let you know. Looks like a little z-order tweak is in order? Cheers!

i got sidetracked with a test app for a potential gig, and will return to this shortly. Just in case you are testing a mark on the navbar, feel free to let me know, as i can test. I am likely going to replicate the mark in question to a space just below the bar and use that, and try just pushing the coordinates up and over the navbar to see if i can make it "just work" ..

Interestingly, at least to me ;), this issue with the navbar led me to a better solution for an fuller intro. I couldn't get the marks to display over the navbar, and thus decided to create screenshots, create new control views over the area of the buttons to mark. Seemed like more work until i realized the structure to encapsulate calls and images in sequence that allows me to show all screens options properly, in one new viewcontroller rather than marking up each view involved.
I may not have thought of it if i was able to access the controls directly. This not entirely ideal, i do like dropping all this into one VC. The other way would involve firing up each involved view in sequence.
It's all good. ;)


fix cl for pp/big science support

Need to also check and reset buffers in eval_batch.

I guess this is just now waiting for one Approval - probably one of @jeffra, @tjruwase, @ShadenSmith on Monday.


Unblock:

Channel ID (required)
TVP1
Reason (required)
Other
Notes
TVP1 is a free and non commercial channel. There is no valid reason to block it

https://github.com/iptv-org/iptv/issues/17674


[feature] Custom scan_each_shard batch size

This allows users to decide how many keys to fetch for each scan.
According to redis, the SCAN command

The default COUNT value is 10

This is not ideal for our use case -- we gonna end up with too many round trips. I updated the default to 1000 (the same default batch size as activerecord)
Test Plan

The changes are covered by spec
ci

Good thing to have, although it can't reduce more than 10% of current trips since 90% are finds that fetch 1 record

Good point! perhaps we can add a script to return full objects back.

rebase
:mag_right: Click to see changes since last update.

Codecov Report

Merging #84 (fc488cc) into master (596d425) will increase coverage by 0.23%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master      #84      +/-   ##
==========================================
+ Coverage   94.40%   94.64%   +0.23%
==========================================
  Files          32       32
  Lines        1680     1642      -38
==========================================
- Hits         1586     1554      -32
+ Misses         94       88       -6

Impacted Files
Coverage Δ

lib/redcord/redis.rb
91.42% <66.66%> (-0.58%)
:arrow_down:

lib/redcord/relation.rb
87.91% <0.00%> (-0.87%)
:arrow_down:

lib/redcord/tracer.rb
89.47% <0.00%> (-0.53%)
:arrow_down:

lib/redcord/attribute.rb
94.11% <0.00%> (-0.07%)
:arrow_down:

lib/redcord/redis_connection.rb
98.30% <0.00%> (-0.03%)
:arrow_down:

lib/redcord/logger.rb
100.00% <0.00%> (ø)

lib/redcord/serializer.rb
100.00% <0.00%> (ø)

spec/actions_spec.rb
86.52% <0.00%> (+0.44%)
:arrow_up:

spec/serializer_spec.rb
97.97% <0.00%> (+0.97%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


Don't ignore Authentication#CreatedAt

it was added here
with gorm:"-" `created_at``s are empty  on authentications (after create with bulk_create or with POST auth. endpoint )
or @lindgrenj6 as you added - do we need it ?

Fun fact created_at/updated_at do not exist on the authentications table in
the DB.
Jacob Lindgren
Senior Software Engineer - Insights Platform
Red Hat
@.***     M:<PHONE_NUMBER>
On Tue, Apr 12, 2022 at 11:17 AM Libor Pichler @.***>
wrote:

@lpichler https://github.com/lpichler requested your review on: #230
https://github.com/RedHatInsights/sources-api-go/pull/230 Don't ignore
Authentication#CreatedAt.
—
Reply to this email directly, view it on GitHub
https://github.com/RedHatInsights/sources-api-go/pull/230#event-6420546547,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMVZ6DKBBT3PTFLYVWQS3TVEWOZNANCNFSM5TH25FLQ
.


[Serialization] Load non-public dependencies of modules when testing is enabled

Non-public dependencies may be referenced from internal decls in a module with testing enabled. If that module is imported as testable by a client, the client can access those internal decls and references for which it needs to load the dependencies.
Ensure that we load transitive non-public dependencies from modules that enabled testing. To do so, we differentiate internal and fileprivate imports from implementation-only imports at the module-wide level to offer a different module loading strategy.
rdar://106514965

I'm suggesting something similar for implementation-only imports in https://github.com/apple/swift/pull/64509, where the dependency can only be optional as adding them as required could break projects.

@swift-ci Please smoke test


incorrect node position was found in mesh1d

Describe the bug
In hydrolib.core.io.net.models.Mesh1d, function _node_position is used to find the position of a node if it already exists in the mesh1d.
This function uses np.isclose with default arguments rtol=1e-05, atol=1e-08, (absolute tolerance and relative tolerance) to determine if two nodes are close.  But the rtol is too relaxed, which makes it not applicable for some reference systems. This should be more strict, e.g. using rtol = 0.0.
To Reproduce
import numpy as np
n = [1329618.61043459, 5765671.70552735]
a = [1329618.6104345862, 5765631.699667968]
b = [1329618.6104345862, 5765671.705527347]
When do the following:
np.all(np.isclose(a, n)) returns True --> incorrect, because  n[1]-a[1] = 40.00585938245058
np.all(np.isclose(b, n)) returns True --> correct
Expected behavior
But using rtol = 0.0:
np.all(np.isclose(a, n, rtol = 0.0)) returns False  --> correct
np.all(np.isclose(b, n, rtol = 0.0)) returns True  --> correct
Screenshots

Version info (please complete the following information):

OS: Windows
Version 0.3.0

Additional context
Add any other context about the problem here.

Hi @arthurvd @grongen, just an FYI for you. :) Cheers, Xiaohan


Tagline changed to technical interest

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

rd/istvan-novak.yml
:white_check_mark:Succeeded

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


syncthing: 0.14.17 -> 0.14.18

Motivation for this change
Upstream recommended upgrade. Not tested yet but should be safe.
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

It works just fine, just compiled it and run it, thanks 👍

Thank you for the review, @jokogr!


Auto-refresh on app open

It is quite annoying to have to either hit the refresh button everytime you take a new picture, or restart the app (which I never do). Could you please make it so that the app refreshes every time it is opened, even if I open it from the recent apps menu?

I second this. Could you please update the pictures in onResume() or something @kollerlukas ?

I will look into a way of automatically refreshing the app.

@kollerlukas  Great. Thank you.

When opening app on Android 7.0, loading time takes very long, then getting feedback "Loading failed" (see pic).

@pink-bird please open a new issue for this. This is a bug.

https://github.com/kollerlukas/Camera-Roll-Android-App/commit/c8cbb3dced65d7af7dd8abb16cb0a7b6d74dd27d