Add sidebase core

Closes #82.
This PR:

re-adds the initial npx command to the readme (#82)
links in the current starter screen image
removes unused images
moves the welcome component to a separate layer to reduce the starter-size  (https://github.com/sidebase/core)

Checklist:

[x] issue number linked above after pound (#)

replace "Closes " with "Contributes to" or other if this PR does not close the issue

[x] manually checked my feature / checking not applicable
[x] wrote tests / testing not applicable
[x] attached screenshots / screenshot not applicable

I downloaded a zip for this branch.
I could:

[X] npm install
[X] npm run dev
[X] npm run built
[X] npm run start

Looks good to me! And cool way of removing more boilerplate and separating our welcome component!


[SUPPORT]: Remove .unit usage from account.unit

✅ Checklist

[x] npx changeset was attached.
[ ] Covered by automatic tests.
[x] Impact of the changes:

Remove usage of account.unit or getAccountUnit and replaced it with a more centralised way in Settings for each currency

📝 Description
Move "unit" field out of Account and move the related settings from Account settings back to the Currency settings (LLD only currently, LLM will be next)

https://github.com/LedgerHQ/ledger-live/assets/112866305/bd0d409d-4287-4b19-9e8d-66913405f6da
❓ Context

JIRA or GitHub link: LIVE-11770

🧐 Checklist for the PR Reviewers

The code aligns with the requirements described in the linked JIRA or GitHub issue.
The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
There are no undocumented trade-offs, technical debt, or maintainability issues.
The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
Any new dependencies have been justified and documented.
Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

=> https://github.com/LedgerHQ/ledger-live/pull/6796


Fix search rate bug

What?
Trello card
This PR is to fix a bug (see trello card) which has crept into the code base resulting in search_rate for a content item being calculated incorrectly.
Search rates were being calculated incorrectly due to our use of the method
number_with_delimiter which, for example, returns '10,000' when passed 10000.
Calling to_f on '10,000' returns 10 and this is the cause of our current incorrect
calculation for search_rate on some pages.
How?
This is solved by formatting the total_searches and total_pviews into
a float before using them to calculate on_page_search_rate.
This PR adds a test for this functionality and makes changes to default data in order
to test that this bug is not longer a problem.

 (1) Page data - fix % of users searched the page in the at a glance metrics


WIP:nonsense change to test linting

Hello @Olllom! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file tests/test_stencils.py:

Line 25:80: E501 line too long (151 > 79 characters)
Line 35:1: E265 block comment should start with '# '
Line 35:1: E303 too many blank lines (8)


[APPM-1071] Incorrect user agent version string in axis2.xml

In 1.0.0 pack, axis2.xml has following for userAgent and server,  <!-- User agent and the server details to be used in the http communication --> <parameter name="userAgent" locked="true">WSO2 AM 1.4.1</parameter> <parameter name="server" locked="true">WSO2 AM 1.4.1</parameter> This should be renamed to reflect correct product name and versionReference: https://wso2.org/jira/browse/APPM-1071

Not related to IoT server, hence closing the issue.


helm secrets install fails when home folder has an '@' symbol

When running helm secrets install I receive the following error due to there being an @ symbol in my home folder:
<EMAIL_ADDRESS>line 458: cmdopts[@]: unbound variable

I'm using a company laptop, hence the convention of having an email address as the user home folder. I'm assuming this is because of set -ueo is specified in secrets.sh but I could be wrong. I've commented out that line and it works for me now.

Had the same issue, commenting out worked. The strange thing is it works for one chart but not for another and I cannot see the difference.

I also had this issue, but for a different reason. I tried to run a standard helm upgrade ... command, but changing it to helm secrets upgrade .... This resulted in the error in the title of this issue. Looking at the secrets plugin script referenced in the error message it occurred to me that the helm secrets command was missing command line options (e.g., cmdopts). That was indeed the issue. Updating the command to helm secrets upgrade --values path/to/secrets.yaml ... worked.


nfd-master node not in running state when setup is run on VMs

Hi,
I am new to Openness and trying to create an edge controller & network edge setup using VMs.
I have created another VM to run the deployment script. My problems are:

Can this setup be run using CentOS7.6 VMs?
On the controller node, I can't login from landing_ui page. I have read somewhere, that this login page is applicable only for on-premise deployment. Is this correct.
On the controller node, I ran kubectl describer pods nfd-master -n openness and the output is:
"Failed to create pod sandbox.... networkPlugin cni failed to setup pod nfd-master.... /run/openvswitch/kube-ovn-daemon.sock: connect: no such file or directory

I am badly stuck with the above error, any help will be appreciated.

Hi,
I am new to Openness and trying to create an edge controller & network edge setup using VMs.
I have created another VM to run the deployment script. My problems are:

Can this setup be run using CentOS7.6 VMs?

OpenNESS currently support running on bare-metal. Running in VMs has not been tested by OpenNESS team.

On the controller node, I can't login from landing_ui page. I have read somewhere, that this login page is applicable only for on-premise deployment. Is this correct.

Correct. This is applicable only for on-prem. For NE deployment, you have the option to deploy the Kubernetes dashboard

On the controller node, I ran kubectl describer pods nfd-master -n openness and the output is:
"Failed to create pod sandbox.... networkPlugin cni failed to setup pod nfd-master.... /run/openvswitch/kube-ovn-daemon.sock: connect: no such file or directory

It is not clear why this could have happened, but there is a general observation that kube-ovn is slow to deploy. If this is persistent, please report a separate issue for it and provide the following:

print out of all the pods in the cluster
logs of the any failing pods
the Ansible configuration files

Please note that we can only support bare-metal installation at the moment.

I am badly stuck with the above error, any help will be appreciated.


ci: Rename macro to avoid conflict during CI unity builds

Unity builds (which we do for CI to speed it up) combine source files,
sometimes in ways that are a bit non-deterministic, and can run into
violations of the ODR that were not a problem when separate definitions
of the same thing (a macro in this case) were in different compilation
units but are in the same one as a unity build.
In this case, a private OIIO_DISPATCH_TYPES macro in printinfo.cpp
conflicted with a different macro of the same name in imagebufalgo_util.h.

Preemptively merging since it's just an internal macro rename confined to one source file, and it fixes a broken CI for something I want to submit.


Mechanics. Send sound only to player who triggers Mechanic

Description
Option to send Mechanic sound only to the player who is triggering the event.
For instance the Out_Of_Ammo event. Players can just spam Q/Right click to trigger reload.
If they don't have the ammo on them it will play a sound. Players can just hold this button and it will be annoying to others.
Instead of playing the sound to everyone with volume etc. 0.5. Would be nice if it could be send only to the player who is trying to spam or reload his/her gun.
Configuration
Ammo:
  Out_Of_Ammo:
    Message:
      Action_Bar:
        Message: Empty magazine
        Time: 1
    Sounds:
      - 'custom:reload.end.normal-0.5-1-0-0.1'

Payment (optional)

[ ] I'm willing to pay for this feature

I cheated to use something like this in WMC for bullet "zip" sounds. Maybe we can add another argument at the end to only send the sound to the caster.

I support this, I don't need other players to hear me reload :(

Fixed by #244


Create uckfield.txt

@jshrimpton Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


Support from date in time ago filter

The idea is be able to pass a extra argument to indicate the from date in time ago filter. I have made a test for this case.

thanks!

Released at 0.10.2


How you collect datum from two radiologists and how to use to get consistency loss ?

you remind in paper that there are two radiologists in your test. I wonder if the two radiologists look the same X-ray images or different?
if they look the same images, how do you use the one X-ray image with two annotations to caculate the attention consistency loss with uncertainty?

In fact, there are multiple solutions:

duplicate the image, then you have (im1,gaze1) and (im1,gaze2) as two individual item;
chose one and discard the other one, which means you have (im1,gaze1)

You should choose your approach by your image. We have test a few: knee x-ray, mammography, chest x-ray and CatVsDog. Viewer variance on knee-xray & catvsdog are smaller than mammography and chest x-ray. Approach_2 can be applied to smaller variance data while approach_1 can be applied to both.

Thanks! I want to follow your work. Unfortunately, i have no idea to get the annotations dataset of radiologists. So would you mind publishing or sharing the dataset used in your paper?


allow ENV to be configured via ENV

hey,
thanks for kemal! <3
what do you think about having something similar to RACK_ENV for kemal?
we deploy mostly to Heroku, it would be great to not have that hardcoded.
best,
ben

How about KEMAL_ENV 👍


Window seems to reload/flash often

It seems that the window is reloading often, resulting in parts of it twitching/flashing.
Here's a video: https://photos.app.goo.gl/XQqSFVS6MZm9WjZR8

That indeed seems strange. I haven't seen this behavior before.
Thanks for recording a video demonstrating this issue.


i18n(zh-cn): Update client-side-scripts.mdx

Description (required)
i18n(zh-cn): Update client-side-scripts.mdx
Related issues & labels (optional)

#9314
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

zh-cn
guides/client-side-scripts.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


jshint complains when overriding fetch in node env.

When:
/*jshint node:true*/
const fetch = require("node-fetch");

JSHint complains that fetch is being redefined. It should only probably do that in the browser env., not in the Node env., as it's not a global there.

actually, nm... need to set browser:false

actually, I lied... it works in Sublime 3 for some reason, but the command line tool still complains...
bin/fetchl10nstrings.js: line 15, col 7, Redefinition of 'fetch'.

Are you enabling the browser option in a .jshintrc file and then disabling it in fetchl10nstrings.js?

Oh... um, yeah :sweat_smile:

So, I'm still a bit confused... .jshintrc should not be overriding browser:false in the file, right?

So, I'm still a bit confused... .jshintrc should not be overriding browser:false in the file, right?

It should, but it doesn't (#1535)

For some reason this is the first link for this search on google so I'm adding this here. If your project uses fetch in node node-fetch and fetch in the browser and your .jshintrc contains both of the following
"node": true,
"browser": true,

You can add this to suppress the "jshint redefinition of fetch" warning
"-W079": false


[docs] Improve BaseDirectory documentation

Is it possible to improve the documentation for BaseDirectory here:
https://github.com/tauri-apps/tauri/blob/4db363a03c182349f8491f46ced258d84723b11f/tooling/api/src/path.ts#L19
It might be enough to just add a reference to each enum value to the respective path.appFooBar documentation (so add a note to BaseDirectory.AppCache that points to path.appCacheDir())
Other enum that's documented:
https://github.com/tauri-apps/tauri/blob/b7ae725/tooling/api/src/window.ts#L228
Discord thread: https://discord.com/channels/616186924390023171/1137125879571558480 and https://discord.com/channels/616186924390023171/731495028677148753/1137122018744074391 that have a bit more context for someone using the enums without knowing what they resolve to.
Would be nice if we didn't have to deal with inline headers ### downstream in docs, but I can handle that for the sake of more documentation <3

@lorenzolewis Let me try to resolve this

@lorenzolewis Let me try to resolve this

Awesome! Give us a shout here or on Discord if you need any help


Feature: IPv6 NAT

I believe that IPv6 NAT (like outbound NAT, not NPT) is really a critical feature for OPNsense to have. Many may not realize the need for NAT with IPv6, since it has so many ips, and that is true, you would not need NAT to accommodate a limited number of public ips with IPv6.
There are however, situations where Outbound NAT is required for IPv6. Take for example having a native (or tunneled) IPv6 connection, with a routed range where you allocate all your LAN IPv6 ips from, but you also have a VPN connection (or multiple) which give you a single IPv6 ip, and hands you some IPv6 routes to route over the VPN.
In this case, the routes that the VPN gives you no longer function from the LAN, because the connections to the VPN IPv6 routes will have a source ip that is not routable back over the VPN. The only solution to this is to NAT the connections with the VPN interface's IPv6 ip.
From what I understand, FreeBSD's PF firewall already supports this functionality, so it should be relatively simple to implement.

In this case, the routes that the VPN gives you no longer function from the LAN, because the connections to the VPN IPv6 routes will have a source ip that is not routable back over the VPN

The system should use the IP matching the network of the default gateway, when accessing resources behind that gateway, then you don't have this problem.

I'm sorry 8191, but i don't think you really understood what i said.
Also, i don't see what pf being ported from OpenBSD has to do with anything

Reminder: Misunderstandings are part of life. We deal with them in a compassionate way.

Was I not "compassionate" in some way?
I wasn't being hostile in any way, I was just saying (based on his reply) that i don't think he really understood my request properly. As for the pf part, it may be a port, but it is still FreeBSD's port, and they have implemented this feature from the upstream pf (or perhaps implemented it themselves, i really don't know).
I think that IPv6 NAT is critical to any modern firewall such as OPNsense, not for use in the way IPv4 NAT is mostly used for, but for the situations where it is required, such as a Native/Tunneled + a IPv6 VPN connection.

closing in favour of #167

#167 is not even remotely the same thing as this request. #167 is IPv6 to IPv4 NAT, what I'm asking for here is IPv6 to IPv6 NAT, just like we have IPv4 to IPv4 NAT

Do you mean this? https://lists.freebsd.org/pipermail/freebsd-current/2014-July/051373.html
We don't have an expert on the subject. Are you willing to assess the individual parts that are needed to make this work and under which constraints this is allowed to operate?

Sure, but this is literally identical to the existing IPv4 Outbound NAT, even the pf rules are the same:
nat on ovpnc6 from 2001:470:1f07:5ba::/64 to any -> 2607:fcd0:a:b::1004/128 port 1024:65535
This would make any ipv6 connection originating from 2001:470:1f07:5ba::/64 that is going outbound on the ovpnc6 interface be translated to the ip 2607:fcd0:a:b::1004

Thanks, so that means Firewall: NAT could do this pending some IPv6 inputs?

Yes, the existing outbound nat should work with only a few minor modifications. After researching the rules a bit more, it probably makes sense to add in inet6 to the rule (though not required):
nat on ovpnc6 inet6 from 2001:470:1f07:5ba::/64 to any -> 2607:fcd0:a:b::1004/128 port 1024:65535
I think all the outbound nat page would need is a dropdown for IPv4/IPv6, and then allowing the inputs to accept IPv6. Basically the way that the firewall rules pages work.

Even I still don't understand your scenario, I'd opt to rename this feature to "prefix rewriting" or NAT66 (to clarify that it's not a 6/4 transition mechanism).

This is not prefix writing, we already have NPT for that. This is just NAT like it is on IPv4. Prefix rewriting requires that you have the same size prefix both internally and externally. This is for when you only have a single external IPv6 IP, but obviously, have a larger internal prefix (such as /64).

I guess this function is technically NAT66, but there is no reason to rename it, it is simply "Outbound NAT", which we already have.


[AIRFLOW-1484] Fix set task instance state

Fix set task instance state when execution_date has milliseconds.
Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following:

AIRFLOW-1484 Updating Tasks through UI crash when execution_date has milliseconds

Description

[x] Here are some details about my PR, including screenshots of any UI changes:
When task instance contains milliseconds - setting task instance state fails with crash:

Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1988, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1641, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1544, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1639, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/lib64/python2.7/site-packages/flask/app.py", line 1625, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/usr/lib/python2.7/site-packages/flask_admin/base.py", line 69, in inner
    return self._run_view(f, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/flask_admin/base.py", line 368, in _run_view
    return fn(self, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/flask_admin/model/base.py", line 2068, in action_view
    return self.handle_action()
  File "/usr/lib/python2.7/site-packages/flask_admin/actions.py", line 113, in handle_action
    response = handler[0](ids)
  File "/usr/lib/python2.7/site-packages/airflow/www/views.py", line 2593, in action_set_retry
    self.set_task_instance_state(ids, State.UP_FOR_RETRY)
  File "/usr/lib/python2.7/site-packages/airflow/utils/db.py", line 53, in wrapper
    result = func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/airflow/www/views.py", line 2628, in set_task_instance_state
    raise Exception("Ooops")
Exception: Ooops

This PR fixed this.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

No tests were added since there is not views.py tests.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2561 into master will decrease coverage by 0.03%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #2561      +/-   ##
==========================================
- Coverage   70.88%   70.85%   -0.04%
==========================================
  Files         150      150
  Lines       11585    11590       +5
==========================================
  Hits         8212     8212
- Misses       3373     3378       +5

Impacted Files
Coverage Δ

airflow/www/views.py
69.74% <0%> (-0.26%)
:arrow_down:

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 9df0ac6...586fb74. Read the comment docs.

Please add tests. And yes views.py is tested

@bolkedebruin thanks will add tests.


[Bug] Setting up with NGINX on UBUNTU server

Version
latest
Reproduction link
Nginx file:
server {
    listen 8080;

    index index.php index.html index.htm;

    server_name example.com;

    return 301 https://example.com$request_uri;

}

server {
    listen 443 ssl;

    server_name example.com;
    root /data/vue-material-dashboard-laravel/laravel-json-api/public;

    ssl_certificate /etc/nginx/ssl/cert.pem;
    ssl_certificate_key /etc/nginx/ssl/key.pem;

    add_header X-Frame-Options "SAMEORIGIN";
    add_header X-Content-Type-Options "nosniff";

    index index.php;

    charset utf-8;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location = /favicon.ico { access_log off; log_not_found off; }
    location = /robots.txt  { access_log off; log_not_found off; }

    error_page 404 /index.php;

    location ~ \.php$ {
        fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        include fastcgi_params;
    }

   # location ~ /\.(?!well-known).* {
   #     deny all;
   # }
}

Operating System
Ubuntu
Device
server
Browser & Version
firefox, latest
Steps to reproduce

I set all up according to documentation and run npm run build.
I let nginx server the laravel/public folder. I use a rather minimal nginx configration in sites-enabled folder (see nginx code above)

What is expected?
I use the npm command, output tells me to look at http://example.com:8081
Everything looks fine and login should be working with default given login
What is actually happening?
I get some sort of backend, but cannot login.
It says: "Invalid credentials"
Solution
Do you maybe have a nice example of how nginx should server the app?
I could not find anything online. I tried running vue-material-dashboard over https by adding "vue.config.js":
module.exports = {
  devServer: {
    open: process.platform === 'darwin',
    host: '<IP_ADDRESS>',
    port: 8081, // CHANGE YOUR PORT HERE!
    https: true,
    hotOnly: false,
  },
}

Then indeed everything goes through https but login does still not work. Any ideas why? Seems api does not communicatie well with vue
Additional comments
If we can let it all work on a linux server we woudl want to go and buy the PRO version eventually (after we tested it and so on)

Hi @rafaelteb,
Thanks for using reporting this issue and for using Creative Tim products.
Could you please send the .env for both the frontend and backend, please? Also, you've mentioned the npm run build. Can you please let us know why is that? Thank you very much.
Best,
Updivision Team

Hi there @rafaelteb,
We would like to check if the issue was solved and if there is anything else we can help with.
Please let us know if you have any other issues.
All the best,
Updivision Team

Jo @teamupdivision,
sorry for my late answer.
I did not do anything specific with the .env file. Just added the database. Here is the .env file (o boy I forgot something small somewhere right):
APP_NAME=Laravel
APP_ENV=local
APP_KEY=base64:Ojwx/O0E8YfUyQe5hYSioTlWy4618YGIr6ujAlx6l18=
APP_DEBUG=true
APP_URL=

LOG_CHANNEL=stack

DB_CONNECTION=mysql
DB_HOST=<IP_ADDRESS>
DB_PORT=3306
DB_DATABASE=laravel_json_api_vue_dashboard
DB_USERNAME=username
DB_PASSWORD=dfdagdg!

BROADCAST_DRIVER=log
CACHE_DRIVER=file
QUEUE_CONNECTION=sync
SESSION_DRIVER=file
SESSION_LIFETIME=120

REDIS_HOST=<IP_ADDRESS>
REDIS_PASSWORD=null
REDIS_PORT=6379

MAIL_DRIVER=smtp
MAIL_HOST=smtp.mailtrap.io
MAIL_PORT=2525
MAIL_USERNAME=null
MAIL_PASSWORD=null
MAIL_ENCRYPTION=null
MAIL_FROM_ADDRESS=null
MAIL_FROM_NAME="${APP_NAME}"

AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
AWS_DEFAULT_REGION=us-east-1
AWS_BUCKET=

PUSHER_APP_ID=
PUSHER_APP_KEY=
PUSHER_APP_SECRET=
PUSHER_APP_CLUSTER=mt1

MIX_PUSHER_APP_KEY="${PUSHER_APP_KEY}"
MIX_PUSHER_APP_CLUSTER="${PUSHER_APP_CLUSTER}"

Hi @rafaelteb,
Thanks for this. Could you share the .env for the frontend too, please?
All the best,
UPDIVISION Team

Hi there @rafaelteb,
We would like to check if the issue was solved and if there is anything else we can help with.
Please let us know if you have any other issues.
All the best,
Updivision Team

Hi @rafaelteb,
Just checking if the issue was solved and if there is anything else we can help with.
Please let us know if you have any other issues.
All the best,
Updivision Team


makes param description optional

solves: https://github.com/ruby-grape/grape-swagger/issues/395

:+1:


Add different run modes for the TUF server, allow saving TUF keys as a secret

Summary
Addresses part of https://github.com/sigstore/scaffolding/issues/1182.
This commit implements features necessary to run/operate the TUF server in production much better:

The TUF server can now be run in 4 different modes:

init - only init the TUF repository and exit
init-no-overwrite - same as init, but won't overwrite the TUF repository if it already exists
serve - only serve an existing TUF repository (no init)
init-and-serve - init and then serve (this is default to preserve backwards compatibility)

The TUF repository can now be initialized/served from a given path, as opposed to always living in a /tmp directory.
The TUF keys can optionally be exported as an individual k8s secret.

Some notes:

The idea behind this PR is that:

There is a k8s Job/initContainer that runs the server with either init or init-no-overwrite to create the TUF repository at a mounted volume.
TUF server Deployment starts using only serve to serve the TUF repository from the mounted volume.
TUF keys are saved in the secret, so the admin of the system can download them and keep operating the TUF repository - they do so by updating TUF files localy and placing them in the volume.

The PR could optionally be split into multiple PRs. I think this functionality is interconnected and hence makes sense to submit as a single PR, but let me know if you want me to split it into multiple ones.
The choice to save the TUF keys into an individual secret (as opposed to adding them to the one that is already created) is kind of arbitrary. We could very well put everything in one secret, however I think having the option to delete the secret with keys (after it's downloaded by the admin of the system) and keeping the one with the repository is good to have.

Release Note

The TUF server was modified to be run in 4 different modes:

init - only init the TUF repository and exit
init-no-overwrite - same as init, but won't overwrite the TUF repository if it already exists
serve - only serve an existing TUF repository (no init)
init-and-serve - init and then serve (this is default to preserve backwards compatibility)

The TUF repository was made to be initialized/served from a given path, as opposed to always living in a /tmp directory.
Option to export the TUF keys an individual k8s secret was added.

Documentation
It feels like this change would deserve some docs, but I don't know if there even are docs for the TUF server. I can certainly write something up if you can point me to the right place.

@evankanderson thanks a lot for your review! I think I addressed all the points. As noted in one of the inline comments, the currently saved secret intentionally explicitly excludes the keys directory from being saved. I'm not sure why it was coded this way, but I think it makes sense that these two are independent and the keys secret can be downloaded and deleted altogether. (I don't think this is a huge benefit, but it felt to me that it might be nice, YMMV of course).


Fix missing IAM permission to write to SSM param store

Fix #47
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Fixed in v1.4.1


"API v2 Officially Leaves Beta"

https://www.digitalocean.com/company/blog/apiv2-officially-leaves-beta/
Are we nearing a point to tag a stable release here?

(y)

:+1:

@GrahamCampbell @yassirh done! https://github.com/toin0u/DigitalOceanV2/releases/tag/1.0.0


Update sloc package to version 0.1.10

I updated the sloc package to version 0.1.10 in order to increase the supported languages.

Thanks.  Merged in 0.5.0

but apm can't install new version, wish you  publish it

Sorry.  I just published it now.

thank you


Add instant preview

Is your feature request related to a problem? Please describe.
Preview not really synced with the static site generator’s output.
Describe the solution you'd like
Take advantage of the static site generator’s built-in “watch” to update the preview pane.
Describe alternatives you've considered
-
Additional context
https://forestry.io/docs/previews/instant-previews/ for reference

Hi @inwardmovement, can you please follow the feature template?
Linking to other resources that might change with time can make it difficult to understand the requested feature.

Ok I edited

Netlify CMS runs in the browser and most of these watch features happen during build time and have file system access (which the CMS doesn't have).
Not sure what "preview not really synced with static site generator files" means.
If you're registering custom previews via https://www.netlifycms.org/docs/customization/
it is mostly up to your build setup to make sure they are updated per change.

I cannot for now, I think we can close this issue and I'll reopen it when I can provide more details?


Universal resolver raw method data

In order to make these tests fair, we need to ensure that the UR is not dropping properties, or doing any parsing of the JSON LD for these tests.
We should be getting JSON as it comes from the method resolver, with no modifications at all.
Some of these errors are UR exploding trying to handle linked data contexts:
https://travis-ci.org/decentralized-identity/context/builds/642227864#L285
Others are just UR test identifiers that don't even resolve.
@peacekeeper interested to hear your thoughts on getting the raw resolver data directly for testing compatibility.

I'm implemented a local caching layer which allows you to bipass the universal resolver for dids that don't currently resolve because of jsonld issues.

this also saves the UR from our test spam.


Enable download count for go package?

Is there any way to get the download numbers for this connector?
I believe there is a setting to enable keeping track of the downloads from github. Would it be possible to enable it?

Not that I'm aware of. Internally there is a github clone count, right now I think this driver is around 1.4k unique clones per months. But many people will also simply clone once, then keep the source code in the needed repo or in GOPATH. Other people won't store the source locally and count a clone for just the CI build and each dev. So while it isn't without merit, I wouldn't put too much stock in it.
Why are you asking for it?


Add workflow for running one-off ECS tasks

Problem

We need to be able to run one-off ECS tasks for things like management commands.
Description

Using the ecs-run-task command it should be possible to do this. There are some existing actions, but after reviewing many of them, they all appear to do "too much" or don't really work as expected.
This one is popular: https://github.com/marketplace/actions/run-ecs-task
However, it automatically outputs CloudWatch logs into GitHub. I kind of suspect it might be best for us not to do that, and instead link to the place the logs could be found instead. If there's no reason not to hide the logs, then maybe that action is okay. My main concern with it, however, is that we wouldn't be able to easily see the logs while the task is running. For that I would like an action that worked like this:

Run the task with the configured command
Log a link to the AWS console area where the task logs can be found
Once the task is done, download the CloudWatch logs and print them into GitHub (if that's okay for us generally).

I haven't found any that do the second bit, and it would be crucial to make it easy to visit logs for long-running tasks.
Additionally, none appear to have any mechanism whatsoever for stopping the task, which would be critical.
Alternatives

Using a GitHub workflow might not be the right answer when considering long-running tasks, at least not one that is waiting the entire time for the workflow to end. It might be best to take the approach that a workflow would run the task and output a link to the logs but the immediately close and that the status of the task would be monitored via Slack notifications (like deployments), for example. I don't know how implementing that would work though as we'd need something polling the tasks to report the status as they finish. Potentially EventBridge would be able to do that for us too though.
Maybe script to run locally or in one-off EC2 instances would be better for this. ECS SSM is another option but comes with its own issues.
Additional context

Just documenting here that I have a strong preference for using SSM via a pre-configured EC2 instance similar to our "jumpbox" for this rather than trying to sort out the various edge cases and problems with GitHub actions, logs, and task cancellation.
Using SSM would mirror our current capabilities with our EC2 deployment and doesn't cause new problems, just maintains the existing problems (of running commands on boxes that are also meant to be serving requests). If we enable auto-scaling, it theoretically wouldn't even be an issue anyway as ECS would compensate for the potentially over worked box by automatically deploying a new instance (which would incur the same costs as ecs-run-task).


Opendata: Automate remaining single datasets

[x] Building Elevation and Subgrade (BES)
[x] Census Tract Equivalency table
[x] Directory of Land Use Application Fees
[x] Food Retail Expansion to Support Health (FRESH)
[x] Lower Density Growth Management Area (LDGMA)
[x] Neighborhood Names -> 37v4-hksf
[ ] NYC Zoning Map Index
[ ] Transit Zones
[ ] Waterfront Public Access Areas (WPAAs) - 6 datasets?
[ ] CDBG Eligibility by Census Tract
[x] Privately Owned Public Spaces (POPS)

Questions about:

NYC Zoning Map Index (is one actually an fgdb? Did tyler migrate them?)


Fix title in Engine API getting started

A weird character was causing it to not be rendered correctly.

Can you please change it to Next steps while you are at it?

Pardon the intrusion, @bfirsh I changed it to "Next steps"
Thanks for the PR -- and nice to see you! :)


[Feature] Improve contact-us card

do something that merges well into the website theme
you're open to be creative, and can suggest us designs in this thread

@jobs-code Sure, go ahead!

Hey @jobs-code, what is the latest update?

Hey @jobs-code, what is the latest update?

sorry for the late reply. Just created a pull request please check it and let me know if there is any improvements needed.
Thank you.


Revision Display is not cleaned when another file is opened from Dropbox

Repro steps:

With an already opened file (which is stored in Dropbox), notice the Revisions List
Open a different file from Dropbox via "Open from Dropbox"
The Revisions List is updated with the revisions of the lastly opened file
However, the Revision Display keeps opened with the last revision being displayed
Notice that, because of that, it is possible to restore that revision (which is related to an already closed file) to the recently opened file.

Expected behavior: when a different file is opened (or even created), the Revisions Display should be cleaned and closed.

@glandre
I'm interested in this item and trying to reproduce this issue but not sure if my reproducing steps are correct or not. The following are my steps and please kindly help confirm if I have any incorrect understanding:

Open a file "TestFile01" from Dropbox.

Select the "View Revision" below to open the revision file of "TestFile01".

Select "Open from Dropbox" again and select the other file "TestFile02" from Dropbox:

Then the file "TestFile02" will be launched but the old revision file of "TestFile01" will be still opened and launched as well:

So do you mean that on the Step 4 above, after opening new file from Dropbox, the old revision file of "TestFile01" should be closed and cleared? Do I understand correctly?

@WhiteHsu This issue has aready been worked on and is awaiting approval in the pull requests: https://github.com/sebbrudzinski/Open-LaTeX-Studio/pull/89

Hey guys,
I'm sorry for my absence these days. I started working on a new project at
work  so I am still getting used to my new routine. I will take a look at
the pull request ASAP.
Bests,
Geraldo
Em 14/04/2016 13:06, "Sebastian Brudziński"<EMAIL_ADDRESS>escreveu:

@WhiteHsu https://github.com/WhiteHsu This issue has aready been worked
on and is awaiting approval in the pull requests: #89
https://github.com/sebbrudzinski/Open-LaTeX-Studio/pull/89
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/sebbrudzinski/Open-LaTeX-Studio/issues/87#issuecomment-210052075

Solved by @sebbrudzinski!


Centos7 install

Trying to install this package on a CentOS 7 install and I'm getting
rpm -Uvh unifi-poller-1.2.2-106.x86_64.rpm Preparing...                          ################################# [100%]         package unifi-poller-1.2.2-106.x86_64 is intended for a different operating system

Hi Jay,
I have yet to really give the rpm much testing. I'm building it with fpm in a reasonably generic manner. I'll throw a centos install into a vbox and see what sorta fixes I can come up with. Thank you for the report!

Found the problem. I'll cut anther release tonight that works on RedHat variants. Sorry about that!

Excellent - thanks for looking into this

Have you given it a try yet? :D Did it work okay?

yes, it installed okay.  Now I just need to finish going through the installation guide.
Thanks!

Okay, read through your wiki.  It was the first time for me ever using Grafana and influxDB.  This is just me nitpicking, but maybe in your install wiki, at the beginning have a section of 'Prerequisites'?  List out:

Grafana
Grafana plugins
3:  influxDB

Here is the link I used to install Grafana for Centos7 (https://grafana.com/docs/installation/rpm/)
Here is the link I used to install influxDB for Centos7 (https://computingforgeeks.com/install-grafana-and-influxdb-on-centos-7/)
I found a typo on your page here 'The package installs them into /usr/share/doc/uniti-poller' it's just with the word 'unifi'.
Great job on all of your hard work!  This is a ton of info to look at in Grafana.  I manage about 6 different sites and this is very useful info.  Now let me try to wrap my head around it!

Yes it worked!  I left some comments on the closed issue.  All running good.
Thanks
On June 10, 2019 12:14:39 PM CDT, David Newhall II<EMAIL_ADDRESS>wrote:

Have you given it a try yet? :D Did it work okay?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/davidnewhall/unifi-poller/issues/30#issuecomment-500500435

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Great feedback! Thank you! I'm excited you got everything working! Please crack open a new Issue if I can help out with anything else. I may not see your comments here, things have gotten pretty crazy; a lot of interest. Thanks again!

Typo fixed. You're welcome to edit wiki pages too, anyone can! I also added your links to the Grafana and InfluxDB wiki pages. Added two more steps to prereqs. Thanks!


Automated cherry pick of #3606: influxdb: 记录结果中的tags

Cherry pick of #3606 on release/2.11.
#3606: influxdb: 记录结果中的tags

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@c68bec9). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #3609   +/-   ##
==============================================
  Coverage                ?   7.11%
==============================================
  Files                   ?     478
  Lines                   ?   77773
  Branches                ?       0
==============================================
  Hits                    ?    5536
  Misses                  ?   71769
  Partials                ?     468

Flag
Coverage Δ

#aFlag
7.11% <0%> (?)

Impacted Files
Coverage Δ

pkg/util/influxdb/influxdb.go
0% <ø> (ø)

pkg/compute/models/loadbalancerbackends.go
2.8% <0%> (ø)

pkg/compute/models/loadbalancers.go
1.71% <0%> (ø)

pkg/compute/models/loadbalancer_backendstatus.go
0% <0%> (ø)

pkg/compute/models/loadbalanceragents.go
2.25% <0%> (ø)

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 c68bec9...f86a02a. Read the comment docs.

/lgtm

/approve

/approve


Added pressure units

pascal = kg / m * s^2
resolves #57

I tried fixing units_cpp.stg but couldn't find what causes the newline.
I edited all_units.h manually for now.


Functional Commit 1 - Design Review Needed

Added new team image to the bottom of projects list. Empty project list now has image and text to signify as such. Fixed bug where it would flash quickly when logging in as regular user.

This is what this screen looks like on an SE in the simulator:


search bar is not visible

search bar is not visible when I created a UIViewController in storyboard and it is extending locationpickerviewcontroller

I also tried to add a custom search bar but it doesn't do anything when I start searching despite I added it the the location picker


chore(bindings/C): resolve doxygen warnings

OOPS, Some checks were not successful . Pls convert this pr to draft at first……
https://github.com/apache/incubator-opendal/issues/3480
fix doxygen warning
There are some wrongs

Hi, opendal.h is auto-generated by the Rust code. You need to change the comment documentation in the Rust code and run make build to update the opendal.h correspondingly.

Hi, opendal.h is auto-generated by the Rust code. You need to change the comment documentation in the Rust code and run make build to update the opendal.h correspondingly.

OMG.....
close this pr, Try again, .....


Truncated deployment ID

I'm noticing that Panoptes will give a URI with a truncated deployment ID; for example, "0025" becomes "25". Maybe there's a step where the deployment ID is converted to a number and back to a string?
Example:
GET http://m3.shore.mbari.org/panoptes/v1/images/Doc%20Ricketts/0782/06_24_07_09.png
gives
{
    "cameraId": "Doc Ricketts",
    "deploymentId": "0782",
    "name": "06_24_07_09.png",
    "uri": "http://search.mbari.org/ARCHIVE/framegrabs/Doc%20Ricketts/images/782/06_24_07_09.png"
}

where the true URI for the image is http://search.mbari.org/ARCHIVE/framegrabs/Doc%20Ricketts/images/0782/06_24_07_09.png.
Not a big issue, but I just want to ensure I'm uploading the processed images to the same spot as the original ones and linking the correct returned URL in VARS.

Fixed: GET http://m3.shore.mbari.org/panoptes/v1/images/Doc%20Ricketts/0782/06_24_07_09.png
{
  "uri":"http://search.mbari.org/ARCHIVE/framegrabs/Doc%20Ricketts/images/0782/06_24_07_09.png",
  "cameraId":"Doc Ricketts",
  "deploymentId":"0782",
  "name":"06_24_07_09.png"
}

This change has been deployed internally at MBARI


NPE in SelectorBuilder for CMMN tasks

Caused by: java.lang.NullPointerException
	at org.camunda.bpm.extension.reactor.SelectorBuilder.extractTypeName(SelectorBuilder.java:138) ~[camunda-bpm-reactor-core-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
	at org.camunda.bpm.extension.reactor.SelectorBuilder.selector(SelectorBuilder.java:26) ~[camunda-bpm-reactor-core-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
	at org.camunda.bpm.extension.reactor.listener.PublisherTaskListener.notify(PublisherTaskListener.java:20) ~[camunda-bpm-reactor-core-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]

When using the SelectorBuilder with a DelegateTask, the builder is not aware of the CMMNness of the task and will therefore cast the DelegateTask to BpmnModelExecutionContext which - fo course - it is not.

will fix this while provoding a CMMN example

BTW TaskEntity implements BpmnModelExecutionContext. This is misleading as the TaskEntity might represent a case task, too.

See also: https://app.camunda.com/jira/browse/CAM-5371


Update voice-input-in-unity.md

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/voice-input-in-unity.md
:white_check_mark:Succeeded
View

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.


Adds a error message for creation of routes with host flag

What type of PR is this?
/kind bug
What does does this PR do / why we need it:
Adds a error message which is displayed when creation of routes is triggered using a host flag.
Which issue(s) this PR fixes:
Fixes https://github.com/openshift/odo/issues/3354
How to test changes / Special notes to the reviewer:
On a openshift cluster, try to create a route based URL with a host flag
odo url create example --host
It should error out with a appropriate message.

/lgtm
/approve

/test all

Platform issue
/test v4.2-integration-e2e

/lgtm

https://travis-ci.com/github/openshift/odo/jobs/359774038#L654
/hold

Test failure are fixed. Thanks
/lgtm

/refresh


[Image -> Data] An onscreen element must not have a null BoundingRectangle property.

The following accessibility issue needs investigation.
App: devenv
Element path: pane ''
Issue Details: An onscreen element must not have a null BoundingRectangle property. Section 508 502.3.1
How To Fix: If the element is offscreen, set its IsOffscreen property to TRUE.
If the element is onscreen, provide a BoundingRectangle property.

Image Classification -> Data tab, before you select a dataset


Question: Labview support for D455?

Required Info

Camera Model
D455

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win 10

Kernel Version (Linux Only)
NA

Platform
PC

SDK Version
2.33

Language
labview

Segment
AR/others

Labview is unable to detect/open the D455, my assumption is that it is because the wrapper's api hasn't been updated to the latest version yet.  Is there as estimation of when the wrapper will be updated to support the D455?

Hi @johnras   The details of the Hello World: Color + Depth example on the LabVIEW wrapper page reference the D455.

I therefore would recommend replacing the realsense2.dll that was included in the LabVIEW package for the same file from the current version of the SDK.  You can either compile this replacement file, as indicated by the wrapper instructions, or you can obtain it from the SDK folder that is created when the full Windows SDK is set up with the installer file from the Assets file list on the SDK Releases page.

Once the SDK is installed, the pre-built realsense2.dll file can be found in the SDK folder's bin directories (32-bit in the x64 sub-directory, and 64-bit in the x64 sub-directory).

An easy way to find the SDK folder is to right-click on the RealSense Viewer launch icon on the Windows desktop and select Open file location from the menu.
The likelihood is that you will want the 64-bit version of the DLL in bin/x64.  Delete the original realsense2.dll from the LabVIEW folder and copy the new one into the folder in its place.

Yes exactly

I updated to SDK v2.40.0, copied the new realsense2.dll over to the LabVIEW folder and updated the firmware on the device to <IP_ADDRESS>.00 and it is working!  Thank you.

That's great news @johnras - thanks for the update   :)

Hellow there!

Hello there!

I
Opening the LabVIEW Example was successful.
Opening LabVIEW Example by changing the dll file was successful.
However, the LabVIEW program runs but no screen appears. I have both LabVIEW 64bit and 32bit. Even if I try to run both by changing the dll file, the screen does not appear.

RealSense_HelloWorld_Left_Right_IR.vi is excutable.

Any help on how to solve this problem would be appreciated.
Thanks!!

Hi @woodal  Although the Monochrome + Depth LabVIEW example is included in the LabVIEW package, it is not described in the wrapper documentation.  From the descriptive text on the window of the image of the example that you kindly provided though, it looks as though it is streaming monochrome color from the left infrared sensor, probably with the monochrome UYVY format.

D455 supports streaming color from the left infrared imager if firmware version <IP_ADDRESS> or newer is installed, so your <IP_ADDRESS> firmware should allow this.  I do not know if this specific LabVIEW example has been tested with D455 though, as it would have more likely been designed for the older D415 model (which also supports color from the left infrared sensor - the D435 / D435i models do not).
Does the RealSense Hello World: Color + Depth example function correctly with your D455?  That example also streams color from the left infrared sensor.


feat: skip already translated keys

Add a feature of translation of a particular key is already present in translation file, it will not generate it again

Hey  @ParvinEyvazov can you please add hacktoberfest-accepted label to this PR as it will help me in my Hacktoberfest journey.

sure @fadkeabhi! Adding it to both PRs! Thank you!


update(build): update libcurl to 8.0.1

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

Does this PR require a change in the driver versions?
No

What this PR does / why we need it:
Update libcurl to fix recent vulnerabilities. As usual, for details check the libcurl website: https://curl.se/docs/security.html
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

update(build): update libcurl to 8.0.1

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@LucaGuerra can you open a branch on Falco to test that it builds (i am scared by the major version bump, ie: 7.x -> 8.x)

LGTM label has been added.  Git tree hash: 693b0dff8a6df10bc40c74f229760dfba06f23ab

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


report stepsize

suggest report changes in stepsize. This useful monitoring the progress (or lack thereof)
it should maybe use Verbose parameter, but that is also not used in most other output, so i didn't bother..

Please rebase on top of master, fix the test failures, flush the output, fix the description of what you're printing, and enable this only when verbose output is set.

I think you can fix the commit message by squash merging..

The |ds| is still wrong I think?


Concurrency issue brought in by commit

https://github.com/apache/incubator-openwhisk/commit/21d37a1af329544e245d376ad613d1a603fc104c
This commit makes openwhisk unstable, including unstable travis build, concurrency issue raised in wskdeploy integration tests.
I have no idea about the detailed reason, but this commit makes Travis vulnerable.

Can you clarify and add some details to make this actionable?

wskdeploy travis build works fine before this commit.
When I pin the openwhisk version to this commit, the travis failed:
https://travis-ci.org/apache/incubator-openwhisk-wskdeploy/builds/308707393

@rabbah we are seeing "concurrency" errors when trying to "undeploy" or delete resources.  We have a series of integration tests that repeatedly deploy then undeploy packages/actions/triggers/rules and every Travis build (as of yesterday fails) with a moving concurrency error... I have documented some of the errors as they move to different int. tests in this issue https://github.com/apache/incubator-openwhisk-wskdeploy/issues/651

@houshengbo thanks for working to "pin" commits in our Travis to isolate where this issue was introduced.

Kafka is not part of the CRUD operations. So I suspect it’s a red herring.

@houshengbo @rabbah so I was informed by Dave Grove that we discovered that we were not publishing Docker images for perhaps 2 weeks and that was fixed yesterday thereby bringing in whatever caused this issue to suddenly appear for us yesterday.

@mrutkows I'll speculate based on your comment the issue is due to the HA controller enablement. CRUD operations are sprayed round robin and cache invalidation messages for CRUD operations are likely happening slower than your deploy/undeploy operations.

@rabbah Jeremias indicated he saw this once after merge, but could not recreate it.

I'm going to remove the bug label until you have confirmation this is a bug. I believe the system is working as intended and you'll need to add some retries for eventual consistency in the tests.

@rabbah It is a bug IMO since these tests have worked before these changes and is an exposure to users who should not be expected to write special logic because resource locking at the server side is taking longer than previously.

As I explained - we now have multiple controllers and CRUD operations are eventually consistent as a result. So you have to adapt the client accordingly.

@rabbah actually MS Azure adapts at the server on all APIs...

Re-titled and re-labelled accordingly.

@rabbah enhancement to return behavior to its previous state?

@rabbah The failure of the wskdeploy build is from the deploy and undeploy's perspective.
You can take a look at the recent Travis builds for PRs. There could be no error, but there could be raised randomly each time.

This is a new feature - the client didn't observe this before because OpenWhisk was deployed with one active controller at a time. So while there were no transactional semantics guaranteed, you got to observe them for most operations (see here as an example this was always the case: https://github.com/apache/incubator-openwhisk/issues/1815; in fact could close one of these as duplicate).

@houshengbo in the meantime we likely need to disable all undeploys in our integration tests and create a plan for adding retries on all concurrency errors in every test or perhaps every CRUD operation.

Also, if this is a client-side/user strategy for this failure that is now surfaced, we will need a plan to document that they need to expect these errors and retry accordingly.

this is causing deja vu for me, saw this in MS Azure 7 years ago
MS they made users retry (documented this) and then they built the retry into .NET client libraries and then fixed it at the server (retry)

A point to reiterate here is that the CRUD operations are round robin distributed to controllers. If there was some session (read namespace) stickiness, it would alleviate this problem. cc @cbickel

@houshengbo confirmed by reproducing and inspecting the logs that the conflict is caused by requests being sprayed to two controllers:

rule disable to controller 0
rule delete to controller 1

both of these operations update the associated trigger document.
Thinking further about server side retry on a conflict is wrong and the client should resolve the conflict. The session stickiness will alleviate this problem a bit and since we have two issues open related to that I'm going to consolidate these issues (hence closing this is a duplicate of 3032 for now since it contains a more accurate represenation of the issue).

@rabbah thanks Rodric for your analysis and 3032 reference


funding reference in metadata

Is your enhancement request related to a problem? Please describe.
Third-party funded research e.g. funded by the DFG requires researchers to provide funding reference. This is part of the DataCite DOI metadata e.g.:
"fundingReferences": [
{
"awardUri": "https://gepris.dfg.de/gepris/projekt/441958208",
"schemeUri": "https://ror.org/",
"awardTitle": "NFDI4Chem – Chemistry Consortium in the NFDI",
"funderName": "Deutsche Forschungsgemeinschaft",
"awardNumber": "441958208",
"funderIdentifier": "https://ror.org/018mejw64",
"funderIdentifierType": "ROR"
}
]

Describe the solution you'd like
User should be able to provide that metadata or add this metadata if they update the metadata (connected to #1105)
Best,
Tillmann

[ ] Add funder field for the project/sample
[ ] Add to datacite + bioschemas metadata


When debugging tests (incl -p option): browser's developer tools closes constantly

When I debug tests using (for example) Chrome's developer tools, it seems that some sort of refresh happens which constantly closes the developer tools after an indeterminate amount of seconds (sometimes less than 1s, sometimes up to 20s). I have to be quick enough to find out what I need in this time window which makes it a bit stressful. ;)
I haven't yet found out what causes this behaviour so maybe someone here has an idea?
I start wct with the following config:
  module.exports = {
  verbose: false,
  persistent: true,
  plugins: {
    local: {
      browsers: ['chrome']
    }
  },
};

I think I have just found the solution thanks to this blog post: http://japhr.blogspot.ch/2015/04/the-debugger-and-breakpoints-with-web.html
What worked for me was:

start wct and copy the URL minus the ?cli_browser_id=0 argument
open a new tab in the browser window that wct created and past that URL

Then, debugging should work as expected and the dev tools will remain open.

Could you please consider reopening this? Existing workaround doesn't mean it shouldn't be fixed, or, at least documented. It took me half of the day today to find this issue to solve it. Besides, it seems ot be related to
https://sites.google.com/a/chromium.org/chromedriver/help/devtools-window-keeps-closing

and it is still closing.

Thank you!

Yeah, this is a complication from wct-sauce plugin, which sends a selenium command every 45 seconds to keep the sauce connection alive.
I need to refactor how the plugins load to fix this.

Sauce? I thought I've turned it off:
var wct = require('web-component-tester').test;
...
gulp.task('tests-persistent', ['systemjs'], function(){
wct({persistent: true, plugins: {local: {}, sauce: false}, testTimeout:<PHONE_NUMBER>7}, function(error){
if (error) {
notifier.notify({
'title': 'Build failed',
'message': '' + error
});
}
else {
notifier.notify({'title': 'Build passed', 'message': 'Yay!'});
}
})
});
Have I?

@azakus can you describe the refactoring you had in mind? Agree this is super annoying.

My thought was to not load the plugins unless they are specified on the command line or in the config file. Right now, wct will load both the local and sauce plugins even if the other is not used.

In addition, is there a way to send the keep-alive command only to the sauce launched browsers?

+1 this is insane

FWIW, this still seems to happen with a disabled sauce plugin, and in debug mode I can see this output repeating - devtools close always at that time.
chrome 58                CALL title()
chrome 58                GET /session/:sessionID/title
14:58:49.923 INFO - Executing: [get title])
14:58:49.927 INFO - Done: [get title]
chrome 58                RESPONSE title()

Hi! Any news on this? I'm trying to debug some tests and tried everything here but devtools keeps closing... :(

It's workaround time!

polymer test -p
copy URL
close chrome
open a new chrome manually
paste url + enter
Voilà, devtools now stays open, but becomes more slow over time (seems like a memory leak), you'll have to reboot it after some time


DefaultProps issue

Describe the bug
I get this in my logs:
Warning: (Block, Icon, Button, Typography, Input ….): Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
Smartphone (please complete the following information):

Device: android
Type of device: physical
react-native": "0.74.1",
"expo": "^51.0.0",
"galio-framework": "^0.8.0"

+1

the same issue


Please consider adding support for VK_EXT_load_store_op_none

Description
VK_EXT_load_store_op_none adds two ops, VK_ATTACHMENT_LOAD_OP_NONE_EXT and VK_ATTACHMENT_STORE_OP_NONE_EXT. The latter is the same op as VK_ATTACHMENT_STORE_OP_NONE_QCOM (and will find its way to core Vulkan eventually). Currently, if an application uses these ops in a render pass, RenderDoc instead replays with LOAD_OP_LOAD and STORE_OP_STORE.
This is not only less efficient, but can lead to VVL's syncval generating errors where there shouldn't be. For example, if a render pass uses a read-only depth stencil attachment, it can use LOAD_OP_LOAD and STORE_OP_NONE. A following image barrier would select its src access based on the fact that the image was used read-only. There is no synchronization hazard with that. However, when RenderDoc turns the store op to STORE_OP_STORE, there's now a WaW synchronization hazard as reported by syncval.
Environment

RenderDoc version: 1.13 (although looking at the code, the current top-of-tree (adb2b659) doesn't handle these ops either).
Operating System: Linux (but that's irrelevant)
Graphics API: Vulkan

FYI, the latest Nvidia beta driver release on Linux (470.62.02) includes this extension. SwiftShader also has an implementation.

This extension was only released a few days ago which is why you don't see any support in any stable version, certainly not 1.13 as that's many months old :smile:. Typically there is a gap between release of an extension publicly and it being implemented, depending on its complexity and demand.
Note that a valid application cannot be using these ops with RenderDoc, because the application must check for the extension and enable it, and when RenderDoc is enabled the extension will not be reported as supported. So I'm not quite sure what you mean about validation hazards or RenderDoc replaying different ops, since it's impossible to use these ops until the extension is supported.

This extension was only released a few days ago which is why you don't see any support in any stable version, certainly not 1.13 as that's many months old :smile:

Hah, that's courtesy of having known about the extension for a few months in advance!

when RenderDoc is enabled the extension will not be reported as supported

You're right, I verified that that is the case. I didn't know RenderDoc did that.

So I'm not quite sure what you mean about validation hazards or RenderDoc replaying different ops

RenderDoc is replaying with correct ops (based on above info that the unknown extension is not exposed). The application itself is generating hazards without this extension, which is expected. So nothing for RenderDoc to worry about regarding that.


SQL Server Data Warehouse: view/procedure definition read

SQL Server DW doesn't support sp_helptext procedure so we need to use another way to read definitions.

verified


Azure doesn't remember the lexicon settings & error loading it

Every time I load a lexicon I get an error saying "Collection was of a fixed size.", and then have to go through the Open lexicon process again to load it.
The other problem is that it only sticks for that game session. Every time you exit the game you have to redo it all over again, error phase included.
Is there a reason there's not a persistent path to the lexicon like Polly and other service providers?

Oh, I was wondering why nobody had reported this — someone did, and I just never saw it 😔
Fixed as of a couple weeks ago: https://github.com/karashiiro/TextToTalk/commit/44053fdba7c103f3b952a6c06e704cbbee46b6de


Create the first architecture for the project

Create the first architecture for the project using draw.io

First version. Feel free to comment if needed.

Aws version of the architecture: (without elastic)

Components and Their Roles:
Event Sources:

Discord: Event source sending data to a Lambda function.
LinkedIn: Event source sending data to a Lambda function.
GitHub: Event source sending data to a Lambda function.

Lambda Functions:

Discord Lambda: Processes events from Discord.
LinkedIn Lambda: Processes events from LinkedIn.
GitHub Lambda: Processes events from GitHub.

RDS (Relational Database Service):

Central database where processed data from the Lambda functions is stored.

Grafana:

Used for visualizing data stored in RDS.

API Gateway:

Provides an interface for external actors to interact with the data or services.

CloudWatch and CloudTrail:

CloudWatch: Used for monitoring and logging.
CloudTrail: Used for auditing and tracking API calls.


NIFI-4644 Fixed LookupService API to allow for more than String/Strin…

…g lookup pairs.
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@m-hogue I think on the mailing list it said you did a lot of work on the Record API. Do you think you could take a look at this? It's an API change that was necessitated by the String,String limitation.

Thanks @markap14 I'll fix these and push a new version.

@MikeThomsen I am just a bit concerned about potential implications of this change... at first glance I don't see any particular problem with it, but I feel like there may be a condition that I am overlooking... It is probably okay, but I would like to think about this just a bit more.

@markap14 That's fine. I posted on the mailing list that someone already found a real case where it broke their flow because it converted an integer to a string and MongoDB couldn't do the lookup. The ticket reference for that particular problem is in there if you want to take a look.

Ok, code review notes should all be addressed now.

@markap14 Have you had a chance to think more this? FWIW, it doesn't seem to break any of the unit tests.


expand is unsafe

Since it does a naive Union, it can introduce duplicate labels, which will lead to runtime errors since our semantics match records. This needs some typelevel-prelude wizardry to remove duplicates.

An alternative is to use RowLacks constraints whenever we eliminate a variant.

On reflection, I don't think it's actually unsafe. Since Union is left-biased, it should be truthful, even though you might need to introduce bogus cases which will never get called in the case of duplicate labels.


langchain embedding from remote server

What is the issue?
I am using this code langchain to get embeddings.
Code -
loader = PyPDFDirectoryLoader("data")
data = loader.load()

from langchain.text_splitter import RecursiveCharacterTextSplitter

text_splitter=RecursiveCharacterTextSplitter(chunk_size=500, chunk_overlap=0)
all_splits = text_splitter.split_documents(data)

from langchain.embeddings import OllamaEmbeddings
from langchain.vectorstores import Chroma
oembed = OllamaEmbeddings(base_url="https://11aa-11-111-111-111.ngrok-free.app/:11434", model="nomic-embed-text")

Upto this, code is working fine.
The following line is throwing error :-
vectorstore = Chroma.from_documents(documents=all_splits, embedding=oembed)

ValueError: Error raised by inference API HTTP code: 404, 404 page not found
I want to use these embeddings for RAG, with groq
rag_template = """Answer the question based only on the following context:
{context}
Question: {question}
"""
rag_prompt = ChatPromptTemplate.from_template(rag_template)
rag_chain = (
    {"context": retriever, "question": RunnablePassthrough()}
    | rag_prompt
    | llm
    | StrOutputParser()
)

I am able to generate collection using chromaDB standalone (i.e. not using langchain), using this code embedding-model
but then I don't know how to use the generated embeddings with groq llm for RAG.
What did you expect to see?
chroma db should have generated the vectorstore
Steps to reproduce
No response
Are there any recent changes that introduced the issue?
No response
OS
Linux
Architecture
No response
Platform
No response
Ollama version
No response
GPU
No response
GPU info
No response
CPU
No response
Other software
No response

There might be a bug in the base_url. The port number :11434 is after a slash /, so the port isn't actually specified; it's interpreted as a path (hence 404 page not found error).
Try removing the slash /: ngrok-free.app:11434

ok, thanks for your response.
I tried without the slash, but still getting the error
oembed = OllamaEmbeddings(base_url="https://xxxx-xx-xxx.ngrok-free.app:11434", model="nomic-embed-text")
vectorstore = Chroma.from_documents(documents=all_splits, embedding=oembed)

ValueError: Error raised by inference endpoint: HTTPSConnectionPool(host='xxx-xx-xxx.ngrok-free.app', port=11434): Max retries exceeded with url: /api/embeddings (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fcc71d09c30>: Failed to establish a new connection: [Errno 111] Connection refused'))

@Ana0112, take a look at this comment and the discussion in the issue. You may need to set the OLLAMA_HOST environment variable appropriately.

I am doing
os.environ["OLLAMA_HOST"]= "https://xx.ngrok-free.app"

which is giving the above error.
I couldn't understand what should be the public ip in my case to set - "OLLAMA_ORIGINS=http://public_ip:11434"

Hi @Ana0112 for using Ollama with ngrok see https://github.com/ollama/ollama/blob/main/docs/faq.md#how-can-i-use-ollama-with-ngrok
Hope this helps!


coded in c language

Sometimes, considering a static value will also be considered as a solution! Here, I have taken the result in the form of an array and solved this FIZZZZBUZZZ!

Ya sorry for that, but this is a C++ code labeled for C, can you take care of that


Completions for $schema only work if string empty

VSCode Version: insiders latest
OS Version: os x

Steps to Reproduce:

Have a myjson.json with the following content
Trigger intelisense after character 'h' - notice you do not get any useful proposals
Delete 'h' and trigger intelisense again - notice all the proposals start with 'h'

{
"$schema": "h|trigger intelisense here"
}

Got fixed and works form me in the latest insiders.
@isidorn Can you verify as well?

Works fine


be able to pass a header to a specific request

Brex is about to start requiring an Idempotency-Key header for some requests

https://developer.brex.com/docs/idempotency/
https://developer.brex.com/openapi/payments_api/#operation/createTransfer!in=header&path=Idempotency-Key&t=request

I don't see a way to pass this through the wrapper. Any plans for this or should I go around?
a new interface like RequestHeaders so things like CreateTransferRequest could extend it
Thanks!

Hi!
I've added a way to specify idempotency key for these requests. I decided to not extend CreateTransferRequest interface, but add a new method argument, where you can specify the key:
    const res = await client.transfers.create(
      {
        amount: {
          amount: 799,
          currency: 'USD',
        },
        description: 'Test transfer',
        counterparty: {
          type: 'VENDOR',
          paymentInstrumentId: 'xxx',
        },
        externalMemo: 'ACH PMT',
        originatingAccount: {
          id: 'yyy',
          type: OriginatingAccountType.Cash,
        },
      },
      { idempotencyKey: '123-456' }
    )

I hope this will work for you.


redis error

Hi, I'm receiving this error:
| redis.exceptions.ConnectionError: Error -2 connecting to your_redis_instance.your_region.redisenterprise.cache.azure.net:10000. Name or service not known.
Based on my understanding, this error suggests that a Redis setup is required in Azure. However, I couldn't find any information about this infrastructure in the project's readme. I'm also curious about the presence of a Redis Docker container in the setup, and how it relates to the Azure setup.
Regards.

thanks @ruoccofabrizio
regards.


UI fixes

IE 11 bugfixing with flex: 1
upload form should accommodate enough space for uploading items

@LachlanStuart 1 more commit for tour page

@LachlanStuart I've updated the PR


Add command line interface

This is an enhancement request. I have done several Google searches and searched the issue repo about this and have found no results so if this is a duplicate, I apologize.
It would be incredibly convenient if one could download a VOD by supplying the link, file destination, and relevant options to a command line interface instead of going through the UI. Sometimes I have a batch of different VODs I'd like to pull and if I could write a shell script to do it, it would save a lot of time.
Thank you for your consideration.

See #157


Fantasy

Adding fantasy aspects to the main and tests

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

Files with missing lines
Patch %
Lines

Support.cpp
51.21%
20 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ

RealmOfFeastTest/RecipeTest.cpp
100.00% <100.00%> (ø)

RealmOfFeastTest/SupportTest.cpp
98.96% <100.00%> (+<0.01%)
:arrow_up:

Support.cpp
64.34% <51.21%> (+0.40%)
:arrow_up:

... and 1 file with indirect coverage changes


The problem of wrist_camera.launch

How did you measure the bias between the camera_link and m1n6s200_link_6.

The code is

the code is node pkg="tf" type="static_transform_publisher" name="realsense_link_broadcaster"
args="0.05425 -0.024 -0.1258 3.14 1.32 0 /m1n6s200_link_6 /camera_link 10"

I measured the transform in CAD (with some help from the realsense datasheet).  That transform is specific to the Kinova Mico, the Realsense SR300 and the camera mount in the cad folder.

@dougsm Thanks for your answer, i will try the hand eye calibration to find out the transform between the arm and eye, but i am not sure it will work.


Rules API: complete API documentation according to doc team guidelines.

To account for Rules API documentation in Security Analytics and complete it in accordance with STYLE_API_TEMPLATE.md in the documentation repo.

https://opensearch.org/docs/latest/security-analytics/api-tools/rule-api/


Change stitch extension to .js

so importing doesn't break - importing .spec will now break though

This can be closed, I merged it in with my geo PR.


Support the use of a static media port in a Connection

This makes it possible to run inside a docker container without a STUN/TURN server.
The issue with a randomly assigned port is that all ports must be published in advance when the container ls launched,

In most use-cases (e.g. WebRTC) there are going to be multiple connections, how is this going to work?

In our use-case we do CPU/GPU intensive processing on the WebRTC media stream and need to scale the hardware infrastructure as the number of client grows, and we've decided to run one container per client hence the need to know which port to open beforehand.
That being said, the solution mentioned in https://github.com/aiortc/aioice/issues/47 seems like a more flexible option that will cater for our use-case as well.

This is a more flexible solution https://github.com/aiortc/aioice/pull/63


Description of "Beth" in TractableBufferStockModel?

Maybe this could be slightly more informative? :)
https://github.com/econ-ark/HARK/blob/master/HARK/ConsumptionSaving/TractableBufferStockModel.py#L108-L109

This issue is duplicative of #36 , which has been outstanding for over two years.

Alright, closing then :)


Run carbon-cache.py as a windows service

Hi,
This sounds propably a rare asked question:
I managed to install Graphite carbon, whisper and webapp on windows - the whole things works well. So down to detailed issues, this one seems pretty annoying. Is there a thought that how to start carbon-cache.py as a windows service that can direct me to right way ? Thanks.
Regards
James

wow stale bot, after 7 years, well done!

Did you managed to get this done?
One way to start things are a service is to use tools like NSSW or https://github.com/mtkennerly/shawl


Better syntax for Java array

NativeScript for Android does not provide syntax to create Java array from JavaScript. The current way is quite verbose and not intuitive. For example
var arr = java.lang.reflect.Array.newInstance(java.lang.Byte.class.getField("TYPE").get(null), 10);
// arr = new byte[10];

There are a few suggestions.

var arr = array([ "element1", "emelemt2", ...]); This will work for only scenarios where we can deduce the element type.
var arr = array("byte", 10) The first parameter is type name, the second parameter is length.
extends the built-in Array with fromJavaType or whatever. For example var arr = Array.fromJavaType("byte", 10);
same as 3) but provide custom object. For example var arr = JavaArray.create("byte", 10);
same as 4) but add type specializations as well. For example: var arr = JavaArray.createByteArray(10);
reuse existing "cast" functions for primitive types. For example var arr = new byte(10);. This scenario does not work for reference types, so should be combined with another one.

Any other suggestions are welcome.
Note: suggested syntax that fits TypeScript well have advantage.

Suggestion 5) looks most explicit to me for primitive types. For reference types we would have to have a method that accepts type parameter.

+1 for point 4 -  var arr = JavaArray.create("byte", 10);
Where byte is the full name of the type. In my opinion most of the time we will use it with primitive types so it will be easier if byte, int are allowed as type specifiers.

I actually ran into this and asked a question (which I just closed now that I see the proper answer)
+1 for point 3; I like enhancing the existing Array function, since we are dealing with Arrays.   Although 5 is also acceptable since we are dealing with a JavaArray...

I suggest this syntax to be only for arrays of reference types. Primitive arrays should be covered by the typed arrays support. #65

suggest using Array.of syntax similar to this: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/of
Array.of(android.view.View, 20)
we can monkey patch this as this:
if (!Array.of) {
Array.of = function() {
return Array.prototype.slice.call(arguments);
};
}
so it will be
Array.of = function(type, number) {
return java.lang.reflect.Array.newInstance(type.class, number);
}
actually I think I just implemented it in this comment. That's called "in comment driven development" :)

We can create globals.js or use our prepareExtends.js to include js functions like this.

I would be confused to use Array.of to create Java objects. If I read the docs correctly
Array.of(element0[, element1[, ...[, elementN]]])

it would create JavaScript array [element0<, element1,...>]. Let's keep it that way and don't change the standard JavaScript features.

Consider this as a better variant of Array.fromJavaType. So to take the best of both I suppose Array.ofJavaType is better. The "from" implies an iteratable objects in Javascript

Also consider this syntax
Array.create(android.view.View, 20);

I am fine with Array.create. The point is to avoid any breaking change. For example if you currently run
var a = Array.of(java.lang.Object, 10);
console.log("a.length=" + a.length);

it will print 2 as expected. So, in short Array.create sounds good to me.

+1 for Array.create(type, count)


Update Notification

When a user updates the plugin, then they should be able to see a quick message describing the changes that they are consuming.

 Update Notification, Normandy


[WIP] Update various xfails after 14.2 deployment

Pull Request Description
In This PR

Update various projects with xfails and created the associated git issues

@swift-ci test

@swift-ci test


ROx-17388: Retry curl calls in roxctl tests

Description
There was an existing flake within the tests for the sensor bundle creation.
Within the tests, curl is used to reach out to central to retrieve the cluster ID. Occasionally, the call failed due to timeouts etc.
Added retries for the curl command to ensure such flakes should be reduced to a minimum.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed

see CI passing.

Current dependencies on/for this PR:

master

PR #6621   👈

This comment was auto-generated by Graphite.


Can I predict the number of streams?

I'm curious about the number of threads and the number of streams by proxy http.
when I test with 100 http-proxy ip and 1000 threads, the number of streams converges to 16-24.
Of course, I confirmed that all 100 of the proxies I use were normal.

first of all, you shouldn't run program with proxies count less than threads count

I want to keep the number of streams around 100.
Is there a recommended number of proxies and threads?

I want to keep the number of streams around 100.
Is there a recommended number of proxies and threads?

first of all, what's your pc specification ? I need to know, backtesting is my coffee close friends. Can you tell me which proxy used ?
ps. I'm still figuring out the best ratio between proxies = threads, because of the differences pc specification, inet speed, working or death proxies, etc.

ok. I understand Thank you.
As a result my computer pc spec and 100 http proxy, 10 thread,  70 streams go up in 5 minutes

ok. I understand Thank you.
As a result my computer pc spec and 100 http proxy, 10 thread, 70 streams go up in 5 minutes

I just test some :
100 threads
1300+ proxies (socks4)
not getting much views, around 30-50
what is the error number counting for @Airkek ?
I see 1:2 between botted and error.
the funny thing is, on some test, error number surpassed the proxies number. what ?


hbase support

hbase backend for SAIL.
I'm going to use this issue to track my patches for an hbase sail backend.

FWIW, there seems to be a somewhat similar project (Apache licensed) https://merck.github.io/Halyard/

Thanks for the pointer.
My RDFJ stuff in on hold right now due to work schedule.
On Mon, Jul 24, 2017 at 4:39 PM, Bart Hanssens<EMAIL_ADDRESS>wrote:

FWIW, there seems to be a somewhat similar project (Apache licensed)
https://merck.github.io/Halyard/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/eclipse/rdf4j/issues/816#issuecomment-317547378, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AXp1Hwmx9OZafImuVVu8PAe9iGCVLaXzks5sRQEAgaJpZM4M-f7r
.

Given there is a solid third-party open source alternative for this I am closing this for now. Feel free to re-open if/when you want to start working on this again.


Check for new and older content URLs

Some requests appear to be returning an older version of the content URL key. This was causing corso backup failures. This commit expands the logic to check for both the new and old keys for the URL.

Does this PR need a docs update or release note?

[ ] :white_check_mark: Yes, it's included
[ ] :clock1: Yes, but in a later PR
[x] :no_entry: No

Type of change

[ ] :sunflower: Feature
[x] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Supportability/Tests
[ ] :computer: CI/Deployment
[ ] :broom: Tech Debt/Cleanup

Issue(s)

closes #3262

Test Plan

[x] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

successfully backed up a user's OneDrive locally even though it was failing prior to the changes. Temporary log statement showed the data was returned under the newly added property


3851573: [v2] LCW closeChat methods throws exception

Added method to check if voice and video calling option is enabled.

isVoiceVideoCallingEnabled() will be helpful for developer using omnichanel sdk to Identify if calling options is enabled or not because of which we have kept method as public..


alerts/cluster-etcd-operator/etcdDivergentRevisions: Doc new alert

I'm proposing etcdDivergentRevisions in openshift/cluster-etcd-operator#774, and this commit is adding the docs it will link.

openshift/cluster-etcd-operator#777 also writing out some of the response suggestions.


[enhancement] use radio buttons for filters

in the filters section maybe consider using radio buttons instead. this would allow you to choose more than 1 item for the filter.
For example:  Maybe I want to watch a comedy, but not an animated comedy or I wanted to watch a movie that i haven't seen from the "90's" -- I would just choose all of the years that are available that are in the "90's" and then refresh until I find what I want.

Released in v2.1, please update to :latest image.


Is this project still active?

I'll be a bit bummed if this is dead. I was really hoping to use this on our current project.

Hi.  Thanks for the question.  I promise that I have not intentionally abandoned this project.  In fact, I still have a long wishlist of new features and improvements, and I was just talking with a friend of mine last week about our plans to implement some of those features soon.
That said... there are not enough hours in a day.  :(
Back when originally created Swagger Express Middleware, I was getting paid to do it as part of my job because the company I worked for needed it.  Then last year, partly because of my work on Swagger Express Middleware, I landed a dream job working at Postman.  It's a great job and I love it, but it keeps me busy for 10 to 12 hours a day, 5 or 6 days a week, and sadly, working on Swagger Express Middleware is not part of the job.  So, between work and family commitments, I'm only left with a few hours each week to work on open-source stuff, and some of my other projects have been higher priority lately, hence the lack of activity on this one.
So what's going to change?  Well... first of all, my workload will (hopefully) be getting lighter soon, because the product that I've been feverishly building for the past year just launched this week.  And secondly, a friend and former co-worker of mine (who helped me build this project at our old company) has offered to help me work on it.  Our work will start with some other projects that Swagger Express Middleware uses under the hood, so you may not see much activity here until we're ready to start updating this project to use the latest versions of those dependencies.

Thank you for the comprehensive update. That's what I thought when looking at the history. It did look like you work on it full time, but then obviously life changes. Thank you for open sourcing this project and will look forward to the next activities and good luck in Postman! 👍
(Hopefully, you can merge all the PR without even adding new features so people won't feel left behind in this project.) :)


widgets: Support markdown in widgets.

Previously, markdown was not supported in widgets like polls and todo. This is fixed by adding an inline only backend processor ZulipInlineMarkdown, and using it to render the poll options or tasks and descriptions of todo before adding them to the database.
Fixes: #21917

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@roanster007 Reviewed the changes locally <time and basic markdown seems to be working fine.

I've noticed that the current process of adding time to a poll in Zulip involves typing the time in the compose box and then copying it to the "Add Option" field. While this works well, it would be even more user-friendly to directly implement time rendering for additional options.
I suggest extending the time rendering functionality to the "Add Option" field, allowing users to input time in a similar manner. This enhancement would streamline the process and provide a consistent experience across the poll creation interface.
Implementation Details:
When users type a time in the "Add Option" field, the system should recognize and render it accordingly.
Ensure that the time rendering follows the same format as when entered in the compose box.
Benefits:
Improved user experience by eliminating the need to copy-paste time from the compose box to the "Add Option" field.
Consistency in time rendering across different input fields.
I believe this enhancement would make the poll creation process even more efficient and user-friendly. I'd be happy to contribute to the implementation if needed.
The decision should be made by project contributors to include the above suggestion or not.

Thanks! For polls, links and emoji look good to me, but the time should be rendered like it is in messages. Compare:

For todo lists:

The elements should work in the description part of the item as well, not just the first part.
These changes break the crossed out formatting for checked items.

@bupd I agree that we should ideally have a better way to input times (and emoji), but let's make sure we get the rendering part of this working first.

@alya I have updated the PR and screenshots as per the feedback.

Thanks! It looks like the space after the : and before the descriptions might have disappeared?

Other than that, the screenshots look good to me. You can add the "maintainer review" label (via Zulipbot) and ping @N-Shar-ma to take a look once that's been fixed.

@zulipbot add "maintainer review"

@N-Shar-ma could you have a look at this..

I believe this pr also fixes #21674 #16821 #12947 and #21674.


added validation logging

Codecov Report

Merging #1016 (e01b0de) into master (323fdb1) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1016      +/-   ##
==========================================
- Coverage   81.45%   81.43%   -0.02%
==========================================
  Files         115      115
  Lines        3774     3776       +2
  Branches      122      121       -1
==========================================
+ Hits         3074     3075       +1
- Misses        700      701       +1

Impacted Files
Coverage Δ

...n/scala/com/ing/baker/runtime/akka/AkkaBaker.scala
75.36% <100.00%> (+0.17%)
:arrow_up:

...la/com/ing/baker/runtime/model/RecipeManager.scala
96.42% <100.00%> (+0.13%)
:arrow_up:

...la/com/ing/bakery/baker/InteractionDiscovery.scala
85.41% <0.00%> (-2.09%)
:arrow_down:

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 323fdb1...e01b0de. Read the comment docs.


Increase number of enabled golangci-lint linters

CAPM3 has 40+ linters enabled in our config whitelist. Golangci-lint has 100+ linters. Enable more linters to increase coverage and code quality.
/kind ci

/triage accepted
Let's propose new linters under a github discussion.


Android13 changes

new google API to handle in-app language changes
simple backup configuration
new savedstatehandle to get/set StateFlow's from it
ability to test changes with fragments
ability to pick 1/multiple images from gallery
2 helper methods to observe changes, made by other fragments, and to get savedhandle to make this changes
use hiltViewModel() method instead of "by viewModels" helper method in compose fragment

Activity do restarts, but it restores previous state afterwards. Please, add logs in onCreate method to verify it. I don't know if other projects have same requirements as Puff, but on Puff there is requirement to turn hebrew as default locale, so we need to use activity instead of fragment/composable, because language screen not necessary will be on top. On Puff there is some guidance screen on top, and so we can't apply default language logic in fragment.
There was flag USE_BOTTOM_NAVIGATION_WITH_FRAGMENTS in MainActivity, that you was able to switch on/off to verify that language change work with fragments fine. Also we were able to test some other features with fragments, not fully composable's screens just to turn on this flag.
I'm talking about these 2 methods: fun NavigationDispatcher.observeBackStackStateHandle() and fun  NavigationDispatcher.observeNavigationResult() in NavControllerExtensions, not clear where you'd like them to put.
We can drop "by viewModels" extension, and instead use hiltViewModel() method inside composable. Not much noticeable benefits, just we can remove one method, and don't have long "non-composable" methods (I mean onCreateView will become in 4-5 lines long). You can check code of some fragment from application.fragment package. So, no much benefit, but we can simplify migration from fragment to composable in future (if it'll happen :) ) Because it's all copy paste, only "main composable" part differs between fragments

@Skyyo Fixed navigation in "dog"/"cat" places, fixed layout direction on android 12


Use code build number instead of shasum for development release if it is available

We could use code build numbers for our development builds for helm charts and we'd have more meaningful helm chart build releases and tags.

This may be done?

Dup of #139