WARNING - The model and loaded state dict do not match exactly

Should I be concerned about the warning in question title followed by unexpected key in source state_dict: bbox_head.loss_balancer.weight? The warning, in context is in output of "run 2" below
In the output below, "run 1" is with default openvino_training_extensions/pytorch_toolkit/object_detection/configs/person-vehicle-bike-detection-crossroad-1016.py
"run 2" is with load_from set to 'https://download.01.org/opencv/openvino_training_extensions/models/object_detection/person_vehicle_bike_sd512_mb2_clustered_epoch_21.pth'
loading annotations into memory...
Done (t=0.00s)
creating index...
index created!
2020-04-26 12:37:17,420 - INFO - Start running, host: root@584361725b51, work_dir: /content/openvino_training_extensions/pytorch_toolkit/object_detection/outputs/person-vehicle-bike-detection-crossroad-1016
2020-04-26 12:37:17,420 - INFO - workflow: [('train', 1)], max: 5 epochs
2020-04-26 12:37:17.699099: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2020-04-26 12:37:21,478 - INFO - Epoch [1][1/3]	lr: 0.00003, eta: 0:00:35, time: 2.549, data_time: 0.301, memory: 2027, loss_cls: 21.3558, loss_bbox: 3.3673, loss: 24.7232
2020-04-26 12:37:21,962 - INFO - Epoch [1][2/3]	lr: 0.00005, eta: 0:00:19, time: 0.483, data_time: 0.291, memory: 2027, loss_cls: 21.2597, loss_bbox: 3.5810, loss: 24.8407
2020-04-26 12:37:22,464 - INFO - Epoch [1][3/3]	lr: 0.00006, eta: 0:00:14, time: 0.503, data_time: 0.309, memory: 2027, loss_cls: 20.4839, loss_bbox: 3.7702, loss: 24.2541
2020-04-26 12:37:23,044 - INFO - Epoch [2][1/3]	lr: 0.00007, eta: 0:00:11, time: 0.518, data_time: 0.327, memory: 2027, loss_cls: 23.6279, loss_bbox: 3.4143, loss: 27.0422
2020-04-26 12:37:23,585 - INFO - Epoch [2][2/3]	lr: 0.00009, eta: 0:00:09, time: 0.542, data_time: 0.351, memory: 2027, loss_cls: 20.8027, loss_bbox: 3.7198, loss: 24.5225
2020-04-26 12:37:24,033 - INFO - Epoch [2][3/3]	lr: 0.00010, eta: 0:00:07, time: 0.448, data_time: 0.259, memory: 2027, loss_cls: 21.4886, loss_bbox: 3.6796, loss: 25.1682
2020-04-26 12:37:24,582 - INFO - Epoch [3][1/3]	lr: 0.00010, eta: 0:00:06, time: 0.490, data_time: 0.302, memory: 2027, loss_cls: 22.5884, loss_bbox: 3.7312, loss: 26.3196
2020-04-26 12:37:25,080 - INFO - Epoch [3][2/3]	lr: 0.00010, eta: 0:00:05, time: 0.498, data_time: 0.310, memory: 2027, loss_cls: 20.1915, loss_bbox: 4.1587, loss: 24.3502
2020-04-26 12:37:25,522 - INFO - Epoch [3][3/3]	lr: 0.00010, eta: 0:00:04, time: 0.442, data_time: 0.254, memory: 2027, loss_cls: 20.1830, loss_bbox: 4.6393, loss: 24.8223
2020-04-26 12:37:26,049 - INFO - Epoch [4][1/3]	lr: 0.00010, eta: 0:00:03, time: 0.467, data_time: 0.276, memory: 2027, loss_cls: 19.0899, loss_bbox: 3.9331, loss: 23.0230
2020-04-26 12:37:26,583 - INFO - Epoch [4][2/3]	lr: 0.00010, eta: 0:00:02, time: 0.534, data_time: 0.346, memory: 2027, loss_cls: 19.4745, loss_bbox: 4.2293, loss: 23.7038
2020-04-26 12:37:27,080 - INFO - Epoch [4][3/3]	lr: 0.00010, eta: 0:00:01, time: 0.498, data_time: 0.309, memory: 2027, loss_cls: 19.0027, loss_bbox: 3.6967, loss: 22.6994
2020-04-26 12:37:27,632 - INFO - Epoch [5][1/3]	lr: 0.00010, eta: 0:00:01, time: 0.492, data_time: 0.304, memory: 2027, loss_cls: 18.2804, loss_bbox: 3.8447, loss: 22.1251
2020-04-26 12:37:28,140 - INFO - Epoch [5][2/3]	lr: 0.00010, eta: 0:00:00, time: 0.508, data_time: 0.320, memory: 2027, loss_cls: 19.0801, loss_bbox: 3.5954, loss: 22.6755
2020-04-26 12:37:28,638 - INFO - Epoch [5][3/3]	lr: 0.00010, eta: 0:00:00, time: 0.498, data_time: 0.309, memory: 2027, loss_cls: 21.2304, loss_bbox: 4.0392, loss: 25.2695

work_dir = 'outputs/person-vehicle-bike-detection-crossroad-1016'
#load_from = None
load_from = 'https://download.01.org/opencv/openvino_training_extensions/models/object_detection/person_vehicle_bike_sd512_mb2_clustered_epoch_21.pth'
resume_from = None
workflow = [('train', 1)]

loading annotations into memory...
Done (t=0.00s)
creating index...
index created!
2020-04-26 12:38:07,880 - INFO - load checkpoint from https://download.01.org/opencv/openvino_training_extensions/models/object_detection/person_vehicle_bike_sd512_mb2_clustered_epoch_21.pth
2020-04-26 12:38:07,934 - WARNING - The model and loaded state dict do not match exactly

unexpected key in source state_dict: bbox_head.loss_balancer.weight

2020-04-26 12:38:07,935 - INFO - Start running, host: root@584361725b51, work_dir: /content/openvino_training_extensions/pytorch_toolkit/object_detection/outputs/person-vehicle-bike-detection-crossroad-1016
2020-04-26 12:38:07,935 - INFO - workflow: [('train', 1)], max: 5 epochs
2020-04-26 12:38:08.214011: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
2020-04-26 12:38:11,996 - INFO - Epoch [1][1/3]	lr: 0.00003, eta: 0:00:36, time: 2.578, data_time: 0.319, memory: 2027, loss_cls: 1.2410, loss_bbox: 0.2311, loss: 1.4720
2020-04-26 12:38:12,535 - INFO - Epoch [1][2/3]	lr: 0.00005, eta: 0:00:20, time: 0.539, data_time: 0.349, memory: 2027, loss_cls: 1.5146, loss_bbox: 0.5705, loss: 2.0852
2020-04-26 12:38:13,080 - INFO - Epoch [1][3/3]	lr: 0.00006, eta: 0:00:14, time: 0.545, data_time: 0.354, memory: 2027, loss_cls: 1.6790, loss_bbox: 0.3525, loss: 2.0315
2020-04-26 12:38:13,656 - INFO - Epoch [2][1/3]	lr: 0.00007, eta: 0:00:11, time: 0.517, data_time: 0.327, memory: 2027, loss_cls: 1.5311, loss_bbox: 0.4902, loss: 2.0213
2020-04-26 12:38:14,123 - INFO - Epoch [2][2/3]	lr: 0.00009, eta: 0:00:09, time: 0.467, data_time: 0.281, memory: 2027, loss_cls: 1.2086, loss_bbox: 0.5029, loss: 1.7114
2020-04-26 12:38:14,590 - INFO - Epoch [2][3/3]	lr: 0.00010, eta: 0:00:07, time: 0.467, data_time: 0.279, memory: 2027, loss_cls: 1.9947, loss_bbox: 0.6080, loss: 2.6027
2020-04-26 12:38:15,113 - INFO - Epoch [3][1/3]	lr: 0.00010, eta: 0:00:06, time: 0.462, data_time: 0.272, memory: 2027, loss_cls: 2.0217, loss_bbox: 1.0948, loss: 3.1165
2020-04-26 12:38:15,635 - INFO - Epoch [3][2/3]	lr: 0.00010, eta: 0:00:05, time: 0.522, data_time: 0.333, memory: 2027, loss_cls: 1.5160, loss_bbox: 0.3437, loss: 1.8596
2020-04-26 12:38:16,118 - INFO - Epoch [3][3/3]	lr: 0.00010, eta: 0:00:04, time: 0.483, data_time: 0.295, memory: 2027, loss_cls: 1.2501, loss_bbox: 0.2759, loss: 1.5260
2020-04-26 12:38:16,658 - INFO - Epoch [4][1/3]	lr: 0.00010, eta: 0:00:03, time: 0.475, data_time: 0.288, memory: 2027, loss_cls: 1.1488, loss_bbox: 0.2404, loss: 1.3892
2020-04-26 12:38:17,181 - INFO - Epoch [4][2/3]	lr: 0.00010, eta: 0:00:02, time: 0.524, data_time: 0.334, memory: 2027, loss_cls: 1.2485, loss_bbox: 0.4387, loss: 1.6871
2020-04-26 12:38:17,681 - INFO - Epoch [4][3/3]	lr: 0.00010, eta: 0:00:02, time: 0.499, data_time: 0.312, memory: 2027, loss_cls: 1.2782, loss_bbox: 0.5573, loss: 1.8354
2020-04-26 12:38:18,261 - INFO - Epoch [5][1/3]	lr: 0.00010, eta: 0:00:01, time: 0.517, data_time: 0.328, memory: 2027, loss_cls: 1.4078, loss_bbox: 0.3881, loss: 1.7959
2020-04-26 12:38:18,784 - INFO - Epoch [5][2/3]	lr: 0.00010, eta: 0:00:00, time: 0.523, data_time: 0.336, memory: 2027, loss_cls: 1.3143, loss_bbox: 0.4636, loss: 1.7778
2020-04-26 12:38:19,300 - INFO - Epoch [5][3/3]	lr: 0.00010, eta: 0:00:00, time: 0.516, data_time: 0.325, memory: 2027, loss_cls: 1.0513, loss_bbox: 0.3218, loss: 1.3732

Hi @js333031
It's ok, not affect training process.


_interopRequireDefault2 is not a function

Environment

Operating System: Darwin
Node Version:     v20.11.0
Nuxt Version:     3.14.159
CLI Version:      3.15.0
Nitro Version:    2.10.4
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      default
Runtime Modules<EMAIL_ADDRESS>vue-yandex-maps/nuxt<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
my [...].ts file
import { NuxtAuthHandler } from '#auth';
import CredentialsProvider from 'next-auth/providers/credentials';
import bcrypt from 'bcrypt'

export default NuxtAuthHandler({
    secret: useRuntimeConfig().authSecret,
    pages: {
        error: '/auth/error',
        signOut: '/?isLogout=true',
    },
    providers: [CredentialsProvider.default({
        name: 'credentials',
        credentials: {},
        async authorize(credentials: {email: string, password: string}){
            const user = await UserSchema.findOne({email: credentials.email})
            if (!user) {
                throw createError({
                    statusCode: 401,
                    statusMessage: 'User is not found',
                })
            }
            const isPasswordValid = await bcrypt.compare(credentials.password, user.password)
            if (!isPasswordValid) {
                throw createError({
                    statusCode: 401,
                    statusMessage: 'errorPasswordWrong',
                })
            }
            return {
                ...user.toObject(),
                password: ''
            }
        }
    })],
    session: {
        strategy: 'jwt',
    },
    callbacks: {
        async jwt({ token, user }) {
            if (user) {
                token.user = {
                    _id: user._id,
                    email: user.email,
                }
            }
            return token
        },
        async session({ session, token }) {
            const user = await UserSchema.findById(token.user._id)
            session.user = user
            return session
        },
    }
});

nuxt.config.ts
auth: {
    baseURL: `${process.env.NUXT_AUTH_ORIGIN}`,
    provider: {
        type: 'authjs',
        defaultProvider: 'credentials',
        addDefaultCallbackUrl: false,
    },
  },

Describe the bug
I have this an error
next-auth_react.js?v=ff837320:4048 Uncaught TypeError: _interopRequireDefault2 is not a function
at node_modules/next-auth/react/index.js (next-auth_react.js?v=ff837320:4048:24)
at __require (chunk-V4OQ3NZ2.js?v=ff837320:11:50)
at next-auth_react.js?v=ff837320:4628:16

Additional context
When I run my nuxt application via npm run dev, I have this problem. But in production building I don't have it.
Logs
No response

Could you please share which version of next-auth do you have? It should be 4.21.1 as more recent versions cause build failures

@phoenix-ru it's 4.21.1
"next-auth": "^4.21.1",

I did like in documentation says

I get this trouble, when I am updated nuxt version to latest.

Thank you for sharing. I noticed you have a "lousy" specifier ^, which may update next-auth to a higher version. Could you please fix the version by doing
"next-auth": "4.21.1"

and rerun the install.
It should work if the version is correct. To check the correctness, run
npm why next-auth

You should see the same 4.21.1 version everywhere in the output.
If you use a correct version and the issue still persists, please share if you're using vite or webpack.

@phoenix-ru unfortunately, this not work me. I tried set next-auth to 4.21.1 and I have same problem. For now my package.json
"next-auth": "4.21.1",
"@sidebase/nuxt-auth": "^0.9.4",

When I use npm why next-auth I have next message:
<EMAIL_ADDRESS>node_modules/next-auth
<EMAIL_ADDRESS>from the root project
  peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>  node_modules/@sidebase/nuxt-auth
    dev<EMAIL_ADDRESS>from the root project

I am using vite for my project. Vite version 10.2.4

any updates?

Hi @bobrov-site 👋
I have not tested NuxtAuth with Nuxt version 3.14 yet. As there were some big breaking changes in 3.13 it would be related to this.
We are still working on resolving the issues that occured when upgrading to 3.13 in this PR: https://github.com/sidebase/nuxt-auth/pull/942
Could you do me the favour of installing this version of NuxtAuth built from the PR mentoned above and checking if this resolves the issue?
npm i -D https://pkg.pr.new/@sidebase/nuxt-auth@c72268d

pnpm i -D https://pkg.pr.new/@sidebase/nuxt-auth@c72268d

yarn add --dev https://pkg.pr.new/@sidebase/nuxt-auth@c72268d

Note: You may need to completly uninstall and reinstall the new package mentioned above

@zoey-kaiser i will try soon your instructions. Thanks for replaying!

@zoey-kaiser i use npm and follow your command. This is not work for me.
Now my package.json looks now:
"@sidebase/nuxt-auth": "https://pkg.pr.new/@sidebase/nuxt-auth@c72268d",

Hi @bobrov-site, thats too bad 😢
Do you think you could create a minimal reproduction of the issue please? Without it I fear it will be hard for us to investigate the issue futhur.

@zoey-kaiser i tried to create reproduction.  https://stackblitz.com/edit/github-adkgbz7q?file=server%2Fapi%2Fauth%2F[...].ts . In this case it's seems like okay.
But in my original project, I have mongo db and I have auth logic there. I cannot share to public with my project because inside I have secret data. How can we resolve this problem?

@bobrov-site You don't really need to share your data or application to reproduce. What is the output of the following command?
npm ls next-auth

On the reproduction you created it correctly returns
nuxt-app@ /home/projects/github-adkgbz7q
+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>deduped
`--<EMAIL_ADDRESS>
Do you still get this problem if you install for example @sidebase/nuxt-auth@next?

@phoenix-ru I have same data for npm ls next-auth, that you share
nuxt-app@ /Users/thewalkingdan/projects/fridda
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
└──<EMAIL_ADDRESS>
I still have problem, even installed @sidebase/nuxt-auth@next


build error

Describe your problem here.
when I downloaded all the necessary libraries and after installing vscode 2019, then after the "warning" nothing else happens. I waited for over 6 hours, but nothing changes ...

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
no

you should use the newer haxe

well, warnings can be ignored

but this thing is kinda weird

you should use the newer haxe

installed a new version, but ... still can't build.

it might be taking a long time to build wait

this is VERY unlikely. before that, I installed libraries and everything was fine. after installing 64 bits (I had 32 bits), now I am suffering with this problem.


Servers in the US

We might be getting users from the US, so I plan to add a couple of servers there.
I plan to go with Linode, since I've had a good experience with them.
I'm open to suggestions as to where to set them up.
https://www.linode.com/speed-test/

Added 1 server:
us-dns1
DoT: us-dns1.bancuh.com
DoH: https://us-dns1.bancuh.com/dns-query
Do53-ipv4: <IP_ADDRESS>
Do53-ipv6: 2600:3c00::f03c:94ff:fe97:f94f
Logs-ipv4: http://<IP_ADDRESS>:8080/logs
Logs-ipv6: http://[2600:3c00::f03c:94ff:fe97:f94f]:8080/logs
Logs-ssl: [https://us-dns1.bancuh.com:8443/logs](http://us-dns1.bancuh.com:8443/logs)

Server is stable. I'll keep this 1 server for now.


Major version changes merge master

Merge master into major_version_all_changes. I had to resolve a good number of conflicts manually (mainly from the adaptive banner changes), so I decided to create a PR just to sanity check the adaptive banner changes.

Nice! Glad to see formatting issues getting surfaced and addressed


Frontend: Refactor layout

Description

Removed sizing from HTML element to use div as container for more consistency
Removed the deactivation of the legend when option where toggled on and vice versa
Panels will stack on each other and when screen height is overflowing, scrolling will be activated
Interaction with the graph are not prevented if a panel is activated (around the panel)
Graph is visible under panel container

Screenshots
Scroll bar in panel space (smaller screen)

Interaction with graph and width consistency (bigger screen)

closes #53

Shoudnt the query panel stay a the the bottom?

Shoudnt the query panel stay a the the bottom?

Do you mean it should always be last in the list of panels? Because it is atm
But if you are talking about a position fixed, that is exactly why this PR is made for, get rid of all fixed position (which makes very difficult to implement new panels).
But I am open to any insights if you have an idea

No I meant the query panel should be fixed at the bottom, if its just a floating panel then it would be jumping all over the place as you toggle some other panels.

No I meant the query panel should be fixed at the bottom, if its just a floating panel then it would be jumping all over the place as you toggle some other panels.

Mmmh. This is basically the previous implementation which leads to a lot of problems when implementing other panels (like shortcut panels)
Having the panel fixed is taking it out of the flex container basically. IT makes the UI very difficult to extend and improve.
Also, how would you handle the different screen sizes? Having the panels floating with one fixed? I foresee a lot of issues with this kind of implementation.
We can have a chat on zoom if you want to iterate through ideas but as far as now, I don't see how this would be good implementation as suggested now :x

Flex allows you to put things at the end of the container, dont really see the issue, as long as the container holding the panels is full height.

Flex allows you to put things at the end of the container, dont really see the issue, as long as the container holding the panels is full height.

That for sure, but it will still be pushed down if overflows. But if that is okay, then I can for sure implement that =)

But if that is okay

yes, dont spend too much time on supporting small screens, the common case needs to be solid first.

But if that is okay

yes, dont spend too much time on supporting small screens, the common case needs to be solid first.

Some updates:
I played around with the code to try some different solutions and we have some trade off to make if we go for this (at this stage)

If we make the container full screen to put the filter at the bottom, we have to activate interaction with the container in order to overflow (which is necessary for adding new panels). This will prevent interaction with the graph (like hovering feature, and all) on the area covered by the container even if no panels are open. I personally think that the benefit to have a fixed position for the filter is not worth losing interaction with the graph on that area. (cf screenshot)

Any insights are welcome, but I don't see how to fix this without reworking the whole frontend structure (which is out of the scope of this PR, since this is to allow more panels to be added in a smooth way).
I suggest we make an issue for this and try to address it once the rework on the panels as been done.

With design suggested by Ruthger

Btw, we got feedback about the opacity of the links and they would like to have it at 0.3 instead of 0.15. I included this into this PR.

lgtm

Nice additions and changes but there are still a number of issues that needs to be addressed, namely:

Ubuntu 20.04 Chrome looks like below:

Is this how it is supposed to look, with a scroll bar?

Yes, the graph options has its own size. We would need to refactor that to fix this. But the scroll is the expected behaviour

Non-interactive mode stops when you change settings, intentional perhaps?

Mmmmh, not sure. On the other hand, being able to change settings on the graph with a graph moving can be difficult to actually see results, so I would consider this as beneficial.

I can't seem to see or locate the shortcut section of the settings panel. Was this part of this PR?

No, separate PR for shortcut panel and shortcuts

Firefox complains that the page seems to be slowing down its performance. Not sure if this is exclusive to the refactor but possibly not. Same issues except for performance hit persist over Chrome/Firefox.

I had the same warning in firefox prior to starting working on this refactoring.

Safari and chrome do work fine. Also fixed the bug on safari that was preventing displaying the filter panel (thanks to refactoring layout, was not willingly haha)


Upcoming breaking API change

Hello! This is not an issue per se and more a heads up that on September 9th, Alpaca will be implementing a breaking change to the API.
The change affects "unpriceable" assets, specifically, positions in an account that are not priceable. This can occur when certain corporate actions are processed or when a stock gets delisted. In this scenario, API endpoints that call functions that use asset prices are returning an error response.
In order to avoid the error response and keep the API available even in the event that one of your positions’ underlying asset is missing a price, Alpaca will introduce a minor breaking change to the API.
Starting on September 9, 2021, the following API response fields will change from non-nullable to nullable. They will appear null in the response in the case that the underlying asset is missing the price for some reason.

Additionally, the following API response fields’ values will exclude the account’s position in the unpriceable asset.

Thanks so much for your work building and maintaining this excellent SDK! Please let me know if there are any questions the Alpaca team can help answer in regards to these changes.

On it, thank you for the notification @ccnixon!


refactor: delint JS

This builds on #202 and eliminates the vue lint that cropped up. The new stuff here is just the last two commits.
There are still some bugs / type errors, but this makes eslint happy.

@NGPixel , when running this, I'm finding that I have to re-run the nuxt dev server a couple times before the interface works. There's something suspicious about the logs. I wonder if you might have insight into what's going on?
On the first run, the UI loads but isn't running properly. Despite being logged in via OIDC, the "Login" widget still sits in the not-logged-in state and the pages don't work. Javascript console has an error about the snackbar provider not being injected. The nuxt dev server log shows (among other things):
ℹ ✨ new dependencies optimized: vue3-snackbar                                         1:27:20 PM

If I then stop and restart the dev server and reload the page in the browser, the Javascript console error is gone and things work. The nuxt dev server log shows
ℹ ✨ new dependencies optimized: luxon, humanize-duration, lodash-es                   1:27:54 PM
ℹ ✨ optimized dependencies changed. reloading                                         1:27:54 PM
[...]
ℹ ✨ new dependencies optimized: fuse.js/basic                                         1:28:57 PM
ℹ ✨ optimized dependencies changed. reloading                                         1:28:57 PM

Note that the earlier message mentioned optimizing vue3-snackbar, but there was no "reloading" afterwards. Any idea why?
I can make this a separate issue, and it may belong to #202 instead..

@NGPixel tells me out-of-band that the issues I'm seeing at start-up are not affecting vscode's startup path. Since that just leaves @microamp and I, I've merged this and will try to debug the non-vscode configuration separately.


option to not make optical flow when making fake batch

Pull Request
Description
optionla to have no optical flow in fake batches
Fixes #
How Has This Been Tested?

added tests
normal unitests
[ ] Yes

Checklist:

[ ] My code follows OCF's coding style guidelines
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked my code and corrected any misspellings

Codecov Report

Merging #654 (d5a8856) into main (c6ad9e4) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #654   +/-   ##
=======================================
  Coverage   93.30%   93.31%
=======================================
  Files          47       47
  Lines        3168     3170    +2
=======================================
+ Hits         2956     2958    +2
  Misses        212      212

Impacted Files
Coverage Δ

nowcasting_dataset/data_sources/fake/batch.py
87.50% <100.00%> (+0.10%)
:arrow_up:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


odyssey viz.json maps_api_template is not set to https when is requested with https

create an odyssey
request the viz.json using https

the master slide is good, the first slide is http instead of https

We are removing odyssey from the vizjson altogether, basically, removing slides.


Pattykev pollingus 1

Suggestions

Rename the FORM folder to ensure that it's significant for users.
Create a documentation for the syntax and locate it at the root of the FORM folder.


raml-mocker version has been updated

@alexeytokar Thanks for the PRs and the interest on the project !


Database Restore Documentation Not Accurate/ Needs Clarification

I tried to restore a database from a backup following the steps in our documentation, however, the restore failed.
Our documentation states the following:

Restoring a database will create a new database and restore all of its tables and views.
The created database will have the name of the database in the backup. The database cannot already exist in the target cluster.

The inaccuracy, pertains to this statement:
The database cannot already exist in the target cluster.
I attempted to restore the database after dropping it and received the following errors:
root@:26257/defaultdb> drop database test;
DROP DATABASE
Time: 358ms total (execution 85ms / network 274ms)

root@:26257/defaultdb> RESTORE test.* FROM 'nodelocal://1/full_backup' WITH into_db = 'test';
ERROR: a database named "test" needs to exist to restore table "t1"

root@:26257/defaultdb> RESTORE test.* FROM 'nodelocal://1/full_backup';
ERROR: a database named "test" needs to exist to restore table "t1"

Please notice, I tried 2 different restore calls and both failed:

WITH into_db = 'test'
and without the WITH into_db = 'test'

I then proceeded to creating an empty database and tried again. This time the restore worked:
root@:26257/defaultdb> create database test;
CREATE DATABASE
Time: 111ms total (execution 110ms / network 1ms)

root@:26257/defaultdb> RESTORE test.* FROM 'nodelocal://1/full_backup';
        job_id       |  status   | fraction_completed | rows | index_entries | bytes
---------------------+-----------+--------------------+------+---------------+--------
<PHONE_NUMBER>20070403 | succeeded |                  1 |    5 |             0 |    95
(1 row)
Time: 725ms total (execution 724ms / network 1ms)

root@:26257/defaultdb> use test;
SET
Time: 21ms total (execution 21ms / network 1ms)

root@:26257/test> select count(*) from t1;
  count
---------
      5
(1 row)

Server version: CockroachDB CCL v20.2.6 (x86_64-unknown-linux-gnu, built 2021/03/15 16:04:08, go1.13.14) (same version as client)

Relevant slack convo: https://cockroachlabs.slack.com/archives/C01PHNMUFLN/p1616597376002800
The example in the docs is incorrect - it needs to be RESTORE DATABASE backup_database_name (it's missing the DATABASE). We might also want to remove the into_db option from this simple example too, as it can be confusing. Once the correct syntax is used, the RESTORE worked as documented (i.e., you can't restore a database if the database already exists)

Thanks for the detailed info and working on correcting the docs :-)


cmake: Support GNUInstallDirs.

This supports GNUInstallDirs and should offer a safe fallback for platforms its not available (?). This makes it easier to install cubeb to a system with the correct paths.
Please review it to make sure its correct, thanks!

Merged with typo fixed in https://github.com/kinetiknz/cubeb/commit/12b78c0edfa40007e41dbdcd9dfe367fbb98d018


Show relevant fields when issue or flag used in filter

That fact that I am suggesting a feature like this shows just how awesome the hosted portals are already.
To facilitate the investigations and correction of data issues, it would be extremely useful to show the fields relevant to the issue used in the filter. That would let a user readily see and browse, for example, invalid datums without having to download them.

Do I understand correctly when I read this issue as:

it would be useful to know what fields affect issue X
it would be useful to configure the table to show the relevant columns (if not even adding them automatically when searching for issues)

Do I understand correctly when I read this issue as:

it would be useful to know what fields affect issue X
it would be useful to configure the table to show the relevant columns (if not even adding them automatically when searching for issues)

@MortenHofft Yes. I was suggesting to add them to the table when the flag is part of the query. I wasn't suggesting that any other indication of what fields are involved, but it would be great to see descriptions of the flags that revealed that information in a description property like that for other columns in the table.

@MortenHofft Yes. I was suggesting to add them to the table when the flag is part of the query. I wasn't suggesting that any other indication of what fields are involved, but it would be great to see descriptions of the flags that revealed that information in a description property like that for other columns in the table.


add stream block to nginx.conf

This PR addresses issue #402 reported by @greglanthier. Users can include configurations for proxying TCP services as part of their sidecar customization. This is an interim fix until we support generating TCP config files as part of the config reload process.

fixes #402


consider merging _input & _output objects with _affordance

this might just simplify things & I'm starting to suspect multiple input / output affordances just aren't necessary

we're in too deep, I think separation has it's merits even if multiple i/o is not a thing


Routed URLs are inconsistent.

The HTTP interface is inconsistent!
Let's have a look (lets say our bot is called "homer"):
/hubot/version
/hubot/ip
etc.
BUT:
/homer/help
Is this by design or a bug?
If it is by design maybe we should change that. I think this is really inconvient to use.
btw: I could fix these, if you guys tell me which one to use (hubot or the bot's name).
Cheers,
Christian

@ChristianGaertner Did you ever submit a PR for this? If not, I can pick it up.

@michaelansel Feel free to do so :D

I did some digging, and it looks like it is exclusively external scripts that define a route of /#{@name}/stuff (core is all /hubot/stuff. I'll start putting together PRs for things in hubot-scripts, but I think the only action for the core is adding documentation.

Closing this since we have documentation talking about using the /hubot namespace.


React Json Schema Form crashes

To replicate, paste this schema:
https://gist.github.com/guitavano/13e1915976b7d746eeb64270db554aaa
On playground:
https://rjsf-team.github.io/react-jsonschema-form/

We did this PR and it worked.
But we should fix it on the root.

More info: We discovered that the root cause is related to the fact that some types (specially arrays) takes more time to render on RJSF, replacing T[] to T[] | null makes it faster somehow

More info: We discovered that the root cause is related to the fact that some types (specially arrays) takes more time to render on RJSF, replacing T[] to T[] | null makes it faster somehow

What do you think about move this question to the rjsf-team? Maybe they can give us an explanation why this is slow and give us a better explanation about slow schemas


Plotly Charts

Is it possible to use Plotly Charts in the Dashboard feature?

Anyone figure how to do this for non-nivo charts?


How is the Spacing implemented in production?

Goal: exemplify how the spacing feature can be implemented by using the Stand alone component CSS.
From
https://github.com/SAP/techne/pull/821
The Spacing feature is already implemented but is it only for the use on SCSS, not for the use on plain CSS, which is the majority of the Use Cases that we have.
Question
How a consumer of the library in CSS form will implement this feature on their UI?

Good question!
The compact version of the library will be considered an advanced feature and will be adjustable when using the SASS — just as any other theming feature. Supplying multiple out-of-the-box spacing options, e.g.,  tn-card--compact and tn-card--tight, for every component will bloat the CSS for all users to cover edge cases for a small number of users.
The question is should teams be able to use a mix of regular and compact components to suit their needs or is it a feature to be enabled globally? I don't have enough information or examples of compact UIs to know for sure. My feeling is that the drop-in Techne theme should have assumptions built-in and we shouldn't encourage mixing and matching. We are providing lots of ways for teams with advanced theming needs to adjust components to meet their needs, SASS feature flags, exposing component local variables, reduced CSS specificity.
Sp far we only have one team that has requested this feature. Let's check with them to better understand their needs, global vs. fine-tuned. We no doubt need an "Advanced" page on the website to explain the SASS powerful customization features available when using the source.

Is not only one team, but a set of products, the EC products.
Don't consider it and "advanced" feature. There is no advanced features, there are features, that's all.
All components have to be implemented to adapt to a spacing class that can be present in a higher element in the DOM tree. The spacing options can be set at any level on the component hierarchy and the components bellow that will use the compact space.
The solution was first described at the request https://github.com/SAP/techne/issues/748
Was also designed at https://github.com/SAP/techne/issues/763, https://github.com/SAP/techne/issues/751
That will answer your question.
Example:

That's is already implemented on
https://techne-alpha.firebaseapp.com/components/structure/spacing


Fix heading + audio player spacing

This used to be good, now it's overlapping.
What happened?
https://crimethinc.com/podcast/53
And to a lesser degree:
https://crimethinc.com/podcast

lgtm. Browser/OS/viewport?

Safari on 13" Pro window.
Also on iOS Safari, audio player is just not showing up on the podcast pages now.

👍 on it


Center QR code in reveal

Hey there!
Thanks for the extension, very nice! I had some trouble using this inside the reveal format. I can add it fine, but I would like to be able horizontally center the QR code.
For text I can do e.g.
::: {style="text-align: center;}
This text is centered
:::

But having the QR shortcode inside that does not help. Any ideas on how to get it horizontally centered?

I usually assign an id to the qrcode (see https://jmbuhr.de/quarto-qrcode/) and use css to position it. e.g.
#qr1 {
  position: absolute;
  top: 0;
  right: 50%;
}

Thanks, that works!


Version Hash Actually Doing Something + Remove "Failed to Launch" (useless) probably

I only tested my fork and it works, I did not test this specific pull request, I heard @returnrqt was already working on it and my roblox had a now-resolved issue prompting me to make it so I did.
Tested by downgrading to version-b7eebc919e96477a

Thanks I'll add you to credits next update. Currently I'm on a short break.


Can the model make assertions about the page? Just like doing ui automation testing, the core is to assert the presence or absence of elements

Can the model make assertions about the page? Just like doing ui automation testing, the core is to assert the presence or absence of elements

I second this question


Probe IMDS /metadata/instance endpoint during discovery in MsiAccessTokenProvider

The way the probe is currently being made to the token endpoint, the request is always going to return a 400. This is causing noise in the monitoring and logging for the Identity Plugin in IMDS and is creating additional confusion on the customer side of things both because of the inaccurate error description and the extra unexpected web traffic.
If the goal is to see if IMDS exists, the probe should go to the main instance endpoint and reflect the availability of IMDS as a whole, rather than the /token endpoint.
Extending the timeout as well, because we've seen additional support issues pop up where the call is occasionally taking slightly more than the two seconds to reach IMDS in the first place and timing out before the request even appears in the log trace.

@AlexGhiondea ACK


static.rust-lang.org: Suggestion of deleting redundant files

All files end with these extensions seem redundant:
.tar.gz.asc.asc
.tar.gz.asc.asc.sha256
.tar.gz.asc.asc.sha256.sha256
.tar.gz.asc.sha256.sha256
.tar.gz.sha256.sha256

All of them created at the same time (2016-01-11 09:30/09:31), looks like they are generated by accident.
Should we delete them? That will make file list cleaner.

These are historical, and we generally don't delete files, but we've since fixed the bug that caused these to get generated.


when will the Causal-Learn support causal evaluation

Currently，the Causal-Learn only support causal discovery；but in practice we also need to evaluate the effect of Treatment to obejct，so when will we support causal evaluation

Perhaps dowhy could come handy for that purpose instead?

Here is an example of how to do effect estimation with dowhy based on results from causal-learn.


Strip trailing newlines before converting

closes #265
Also allows us to simplify some tests, as flake8 will no longer complain about too many whitelines

Codecov Report

Merging #266 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #266   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          374       371    -3
=========================================
- Hits           374       371    -3

Impacted Files
Coverage Δ

nbqa/__main__.py
100.00% <ø> (ø)

nbqa/save_source.py
100.00% <100.00%> (ø)

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 bbc518f...3b338db. Read the comment docs.


[GHSA-3gh6-v5v9-6v9j] Jetty vulnerable to errant command quoting in CgiServlet

Updates

Affected products
Summary

Comments
The title incorrectly says "CgiServlet".
There's no such class in Jetty, it's just called "CGI" and it happens to extend from HttpServlet.
See: https://github.com/eclipse/jetty.project/blob/jetty-10.0.x/jetty-servlets/src/main/java/org/eclipse/jetty/servlets/CGI.java

Hi there @gregw and @sbordet! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our highly-trained Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory


Add API for entity glow

Rebase of #1122
Spectral arrows can give an entity glow potion effect temporarily. You can also apply it permanently with Glowing NBT tag. This exposes this to SpongeAPI.
I've added a TODO in one of the javadocs - basically a couple entities do not show the glow, will need to do some testing when possible to work out exactly which entities do not do this.

Re-open this PR after branches are resolved as there are definitely not 100+ commits being merged into bleeding.


fix ol.source.Vector#getFeaturesAtCoordinate

As noted in https://github.com/openlayers/ol3/issues/3703, ol.source.Vector#getFeaturesAtCoordinate sometimes returns empty when it should return matching features.
Currently, it only returns features containing the coordinate, while the docs state that it should return all intersecting geometries. This PR changes this.
While doing this, I noted that ol.geom.Circle and ol.geom.LinearRing doesn't implements ol.geom.Geometry's abstract intersectsExtent method. This means that using this method will fail on any source containing those geometries. I'll open an issue about implementing intersectsExtent on those geometries. Perhaps that should be fixed, and these tests updated, before merging this PR?

However, i just realized that omitting geometry.intersectsExtent from some features might be deliberate.
I guess that LinearRings does not intersect an extent that is completely contained within it, which would match the expected behaviour of getFeaturesAtCoordinate.
But is ol.geom.Circle a round LineString or a round Polygon? Should circle.intersectsExtent return true or false for an extent completely contained by the circle? Should ol.source.Vector#getFeaturesAtCoordinate return true or false for a coordinate within the circle? The expected behaviour is probably depends on the application, and the style of the circle (filled->true, non-filled->false).

I created a pull request for ol.geom.Circle#intersectsExtent here: https://github.com/openlayers/ol3/pull/3764

I commented https://github.com/openlayers/ol3/issues/3703#issuecomment-109248047 and would wait from input of the @-mentioned people.

While this is not merged, ol.source.Cluster.getFeaturesAtCoordinate() is completely unusable. As mentioned, ol.geom.Geometry.prototype.containsCoordinate always returns false.

I'm not sure how to proceed with this, because the relevant information is scattered across too many places. I'm closing this due to lack of activity, and would suggest a new ticket that summarises the problems and potential solutions.


Added MqttClientUnsubscribeOptionsBuilder

MqttClientUnsubscribeOptionsBuilder  is the analogous Builder to MqttClientSubscribeOptionsBuilder.

For me, this looks good.

Please also fill the release notes in the nuget file in the proper format.

Please also fill the release notes in the nuget file in the proper format.

Is it okay like this? (First time i've done this.)


Feat: nic_nmcli - Improve role capabilities

Rewrite the role logic.
One line jinja was hard to read or debug, and did not covered all needed aspects.
Using dedicated variables that contains multi lines jinja code allows greater capabilities, while having a readable code.

looks good for me.


Hide buffer

Hi there. How can I hide buffer?

:set nobuflisted should work.

@chrisbra not work for me

which one do you want to hide? Please show output of :ls and :set buflisted in each buffer. Also you might need to force an update of the bufferline. (a window command should do)
Please note, this is not an airline issue.

@chrisbra I'm using airline tabs. So at the right side I can see my(cursor) position in current tab. I wanna hide it.

Am 2016-03-02 08:22, schrieb Denis Papushaev:

@chrisbra [1] I'm using airline tabs. So at the right side I can see
my(cursor) position in current tab. I wanna hide it.

I don't follow. You want to hide the cursor position in the tabline?
What cursor position?

@chrisbra, oh mate sorry for my bad english.
Look at the right side of screenshot


⚠ ClamAV has degraded performance

In 62d8783, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 90 ms

Resolved: ClamAV performance has improved in 029549e after 542 days, 11 hours, 8 minutes.


Question on: mothur's blog

Hi Pat,
I have a quick question about Miseq SOP, after screen.seqs we will get a good.fasta and good.count_table files. So in the following step using unique.seqs shouldn't we be using these files instead of unique.seqs(fasta=stability.trim.contigs.fasta, count=stability.contigs.count_table) as in below?
unique.seqs(fasta=stability.trim.contigs.good.fasta, count=stability.contigs.good.count_table)
Thank you,
Sithara

Correct
On Fri, Aug 26, 2022 at 5:45 PM Sithara Vivek @.***>
wrote:

Hi Pat,
I have a quick question about Miseq SOP, after screen.seqs we will get a
good.fasta and good.count_table files. So in the following step using
unique.seqs shouldn't we be using these files instead of
unique.seqs(fasta=stability.trim.contigs.fasta,
count=stability.contigs.count_table) as in below?
unique.seqs(fasta=stability.trim.contigs.good.fasta,
count=stability.contigs.good.count_table)
Thank you,
Sithara
—
Reply to this email directly, view it on GitHub
https://github.com/mothur/mothur.github.io/issues/91, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJUUBEDKJGRA7GKGSA27Q3V3E3HJANCNFSM57YC5IMA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


liveness-based slicing should detect version of live symbols at the time the cell was run

Example failure:
# cell 1
x = 0

# cell 2
if True:
    y = 7
else:
    # even though this branch is not taken,
    # liveness-based usage should detect the
    # version of `x` used at the time it was
    # live, meaning cell 1 should get included
    # in the slice
    print(x)

# cell 3
x = 5

# cell 4
print(x + y)

The slice for reconstructing cell 4 should use all of cells 1, 2, 3, and 4, but the current slicer will leave out cell 1, since it will detect the more recent version of x used in cell 3 during liveness checking and therefore leave out the definition in cell 1.

Yeah my test case also has this issue, I realize

Suggested way to go about doing this: in safety.py, there's a function called _precheck_for_stale that is run before a cell is executed. In this function, we run liveness analysis and bail if it's detected that the cell has any live references to stale symbols.
This is a good place to record, for each live symbol, the symbol's timestamp / defined_cell_num at the time of liveness. We can add a field to DataSymbol to record this info; e.g. some kind of dictionary called version_by_liveness_timestamp that maps the current cell number to a symbol's defined_cell_num each time that symbol is live in _precheck_for_stale. There is a comment block in _precheck_for_stale with the suggested spot for where to update this field in each live data symbol with a TODO; i.e. it looks something like this:
    def _precheck_for_stale(self, cell: str) -> bool:
        ...
        ...
        ...
        # TODO: For each of the live symbols, record their `defined_cell_num` at the
        #   time of liveness, i.e. at the time `self.cell_counter()`, for use with the
        #   dynamic slicer.
        ###########
        # CODE HERE
        ###########

        self._last_refused_code = None
        return False

From here, we can use the same strategy for live references as we use for dynamic usages; i.e., in get_dependencies, we can grab all the static dependencies for every cell and then aggregate them along with all the dynamic ones:
        for sym in self.all_data_symbols():
            for live_timestamp, version in sym.version_by_liveness_timestamp.items():
                cell_num_to_static_deps[live_timestamp].add(version)

One other issue we may want to address is that sometimes the dynamic dependency set for cell n includes cell m where m > n. This gives us extra cells we may not need. For example:
# cell 1
x = 0

# cell 2
if True:
    y = 7
else:
    # even though this branch is not taken,
    # liveness-based usage should detect the
    # version of `x` used at the time it was
    # live, meaning cell 1 should get included
    # in the slice
    print(x)

# cell 3
x = 5

# cell 4
print(y)

In PR #60, calling get_dependencies for cell 4 will result in cells {1, 2, 3, 4} when you really only need cells {1, 2, 4}. (even cell 1 is not necessary, but this is a different problem)

I think I went in and fixed this for dynamic dependencies already -- I think this is happening because we're still running the liveness checker in _get_cell_dependencies, and the live symbols retrieved therein will all be the latest versions. For example, when we _get_cell_dependencies on cell 2, we'll see that x is live, but its version will already be associated with the value in cell 3, which is why we get the spurious extra dependency. With your most recent fix, I think we can just eschew running liveness analysis just-in-time altogether and instead only use the information you recorded in the PR for this issue. See 247dafe.


context.sendActivity throws unknown error when invoked from a handleTeamsTaskModuleSubmit

I have an application that renders a tab using adaptive cards (via a bot).
The tab contains a button that opens up a task module. When I click on the submit of the task module, I'd like to send a message in the chat. However, I'm getting an [onTurnError] unhandled error: Error: Unknown. Why is it not working?
This is a simplification of my handleTeamsTaskModuleSubmit:
  async handleTeamsTaskModuleSubmit(context: TurnContext, taskModuleRequest): Promise<TaskModuleResponse> {
    const data = context.activity.value.data;
    const teamsCtx = contextToTeamsContext(context);
    const submitEvent = taskModuleRequest.data.submitEvent;

    switch (submitEvent as TeamsAppEventKeys) {
      case TeamsAppEventKeys.CANCEL:
        return;

      case TeamsAppEventKeys.MENTORSHIP_REQUEST_SUBMIT: {
        await context.sendActivity("hello"); // this throws the error
        return;
      }

      default:
        break;
    }
  }

@guillewu - Could you please confirm is your issue resolved or are you still facing this issue?


SW-6171 Add timestamps to species search table

Allow the created and modified times of species to be queried using the search
API.

#2512  👈
main

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

Join @sgrimm and the rest of your teammates on  Graphite

Merge activity

Oct 18, 5:44 PM EDT: A user merged this pull request with Graphite.


Output interpretation of ONNX

First off - I managed to use this model, to train it and then use it to detect my objects in Python.
So I know that the base model works. I then converted my trained model to .onnx.
Now I am trying to use my trained model as an .onnx model in a different framework (C#/OnnxRuntime).
It seems that I can get some results in the form of 3 matrices in the following formats:
Identity:0_dimension = [1, 13, 13, 3, 7]
Identity_1:0_dimension = [1, 26, 26, 3, 7]
Identity_2:0_dimension = [1, 52, 52, 3, 7]

However I do not know how exactly should I interpret these output results ? I mean, it seems these are my output layers matrices but how would I get my bounding boxes or labels out of them ?
And according to zzh8829 the format should be:
[N, 13, 13, 3, 6], but instead of 6 I have a 7 at the end. Does this mean my model is corrupted ?
Here is a small snapshot of one of the output results:
{
    {
        {
            {
                {23.08749,-10.212144,-2.0024538,-25.060818,-55.372665,-110.56176,135.68314},
                {105.10561,-9.675938,19.458107,-96.64158,-89.85328,46.84661,96.895294},
                {1.4982919E-23,-3.4266643E-24,-1.4070271E-23,-4.4147082E-24,-90.44509,2.3854504E-23,4.3499056E-24}
            },
            {
                {3.372866,11.668075,-9.567041,-64.213486,-63.719658,-206.94586,244.01846},
                {125.439095,-18.278257,24.981243,-140.09473,-69.141045,3.0593386,229.12059},
                {2.3764304E-23,-1.8169582E-23,-8.978708E-24,-1.3363941E-24,-116.09719,3.6178897E-23,1.670591E-23}
            },
            {
                {-3.3982036,28.097092,-8.490401,-67.545,-75.23361,-241.23103,271.9279},
                {126.59347,-10.928274,32.26725,-157.15622,-97.7135,-16.002384,262.35583},
                {2.8793467E-23,-1.7884054E-23,-9.630813E-24,8.891573E-25,-146.35085,4.105369E-23,2.0694067E-23}
            }
            ...

Basically my problem is - I dont now how to use the savedModel when one loads it (as a savedModel).
The author of this project made a great job in delivering everything. So one can train his own model and use it for detection.
However when one tries to use the savedModel method then it is not so straightforward in how do you get the results. To describe the problem - this here works:
yolo = YoloV3(classes=FLAGS.num_classes)
yolo.load_weights(FLAGS.weights).expect_partial()
logging.info('weights loaded')
boxes, scores, classes, nums = yolo(img)

This here however delivers something else:
yolo = tf.saved_model.load(pathToSavedModle)
infer = yolo.signatures[tf.saved_model.DEFAULT_SERVING_SIGNATURE_DEF_KEY]
logging.info(infer.structured_outputs)
(identity0, identity1, identity2) = yolo(img)

I am not experienced enough in python te figure out how would you get from
(identity0, identity1, identity2) = yolo(img)
to
boxes, scores, classes, nums = yolo(img)
I suppose most of the "magic" happens in the models.py somewhere in function YoloV3 but its a bit tricky to debug it.


Fixed messages referring to Learn

Changed Learn to Help in messages about keystore.

@jisqyv @halatmit

@lizlooney LGTM

MERGED


Document development commands

Run tests (minikube start; make minikube-test)
Run partial tests (TELEPRESENCE_TESTS="-k tocluster tests/test_run.py" make minikube-test)
Run command line with images built above (TELEPRESENCE_VERSION=$(make version) cli/telepresence ...)

Fixed in commit I pushed just now.


Add ir_data_utils.copy and update

This adds ir_data_utils helpers to handle copying and updating ir_data instances. Some instances of CopyFrom that aren't associated with a builder are updated to use copy or update.
Part of #118.

FYI @robrussell

Not sure if you saw the question about header_generator_test.py - it has the only remaining direct calls to CopyFrom, did you intend to update those too?

It's used in a few files, the changes I made here were instances that aren't already using a builder. The ones in header_generator_test are all essentially builder(...).CopyFrom.


AsyncProducerConsumerQueue has no interface

I really love to use AsyncProducerConsumerQueue in my library code as a way of allowing library classes to quickly enqueue event objects for sequential processing (in the correct order yaayyyy!!!) by a consumer.
This is quickly replacing functionality wherever in the past I would have given a library class multiple public events to be handled synchronously. (Where a library class is raising multiple events, like public event Action<EventArgs> MyEvent1, MyEvent2, MyEvent3, etc; concurrently, it's often impossible for the consumer to process all the events in the correct order)
And queueing the events rather than waiting for them to be handled complete allows the library object to "move on" much faster. I love it!
However, I feel a bit "guilty" by writing library classes whose factories require calling code to only provide Nito.AsyncEx.AsyncProducerConsumerQueue objects as event consumers, which can't even be inherited for some kind of slight modification.
I'd really like, instead, to create factory methods in my libraries that accept IEnqueueAsync interface implementations, where the definition of the interface might be something like:
public interface IEnqueueAsync<T> {
  void Enqueue(T value);
  Task EnqueueAsync(T value);
}

public interface ISomeLibraryFactory {
  Task CreateSomeObject(Options options, IEnqueueAsync<object> eventConsumer>();
}

Is there an interface like this defined somewhere in the .net core framework that could be borrowed and added to the AsyncProducerConsumerQueue?

There is not. TPL Dataflow has a sort-of equivalent (ITargetBlock<TInput>), but its semantics are different enough that it would not be very useful.
I recommend writing your own interface with proxy implementation objects (which you can leave open for derivation).


Avoiding column wrap to next line

I do not want the final column in my datatable to wrap over to the next line. How can I achieve this. I have tried setting column width in percentages as well as fixed width. I can still see the green '+'
in my row

This is a question about Datatables, not AltEditor. You should better ask on their forum.


game is not starting

[Error  : Unity Log] MissingMethodException: void MysticsRisky2Utils.BaseAssetTypes.BaseItemLike.SetAssets(string)
Stack trace:
MysticsRisky2Utils.BaseAssetTypes.BaseEquipment.Load () (at :IL_000C)
MysticsRisky2Utils.ContentManagement.ContentLoadHelper+AsyncLoadingEnumerator`1[OutType].System.Collections.IEnumerator.MoveNext () (at :IL_0035)
HG.Coroutines.ParallelProgressCoroutine+d__13.MoveNext () (at :IL_007F)
HG.Coroutines.ParallelProgressCoroutine.MoveNext () (at :IL_0000)
EliteVariety.EliteVarietyContent+d__2.MoveNext () (at :IL_0207)
HG.Coroutines.ParallelProgressCoroutine+d__13.MoveNext () (at :IL_007F)
HG.Coroutines.ParallelProgressCoroutine.MoveNext () (at :IL_0000)
RoR2.RoR2Application+d__61.MoveNext () (at :IL_0161)
UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at <2cc17dca390941eeb4d7b2ff1f84696a>:IL_0027)****
help

You are using Elite Variety, which is no longer maintained by me and was bound to break with MysticsRisky2Utils 2.0 update. You can either disable it, or disable Mystic's Items and downgrade Utils to the previous version.


Add Device Management User Guide and update Device Mgmt README files

Adds user guide language for Device Management (Google Doc here)
Inserts README templates for Device Registry packages - will need devs to fill in descriptions and remove sections as needed
Adds one contributing.md file for every README file to reference

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


Minimap drag, scroll and focus

Currently when clicking on the minimap, the clicked line is brought into view, but the minimap scroll position is always with the visible area in the middle.
Also when you attempt to drag-drop, this becomes a "scroll to top or bottom" operation, as the mouse will stay above the highlighted area, which will trigger another scroll, etc.
Ideally the highlighted area in the minimap should not always be dead-center, but where you dragged it, so you can use it as more than pretty scroll up/down button (check the drag behavior in SublimeText f.i.)

Damn, I didn't test it properly with a large file. I see the problem and will fix it asap.

Fixed. Much better but still needs a little adjustment. This is on my todolist and I'll get back to this later.


Refactor app to use const generics.

This commit replaces the old, dynamic initialization approach with
const generics, ensuring at compile-time that the number of categories
is correct.
I disabled some tests, but I'll re-enable them in a follow-on PR.
Ultimately, this PR represents a transitory period for the computation
of test statistics, so the code is pretty rough, but I'll be cleaning
it up immediately.

#16  👈
trunk

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

Join @RobbieMcKinstry and the rest of your teammates on  Graphite


[WIP] Continue work on xmile parsing and running

Continue working on xmile support for latest version of PySD.
Pull request created for showing the progress and running the CI.

Coverage increased (+0.009%) to 90.0% when pulling 11a1f58ae13ab787c235968ecc43db5581e02e4e on alexprey:structuring_readers into 91ce868339c644dacfe70f5f072d65b1f3ac1c13 on JamesPHoughton:structuring_readers.

Coverage decreased (-0.09%) to 89.905% when pulling 2a0eed17b07a24d1444f97fae4e4a7cb1dc8c620 on alexprey:structuring_readers into 91ce868339c644dacfe70f5f072d65b1f3ac1c13 on JamesPHoughton:structuring_readers.

Coverage decreased (-0.07%) to 89.922% when pulling 307f80aeb3705bbae96f83ad42ffdd1642045938 on alexprey:structuring_readers into 91ce868339c644dacfe70f5f072d65b1f3ac1c13 on JamesPHoughton:structuring_readers.

Coverage decreased (-0.06%) to 89.931% when pulling a32fd015cda5e3f7dee5e435d7ec307b778adcc3 on alexprey:structuring_readers into 91ce868339c644dacfe70f5f072d65b1f3ac1c13 on JamesPHoughton:structuring_readers.

Coverage decreased (-0.06%) to 89.931% when pulling 254a0482fc809c1f36761571f079ee05ebb969c8 on alexprey:structuring_readers into 91ce868339c644dacfe70f5f072d65b1f3ac1c13 on JamesPHoughton:structuring_readers.

Coverage decreased (-0.05%) to 89.94% when pulling 3fa407ecb1ad854b6e42289b1eee8594b9814980 on alexprey:structuring_readers into 91ce868339c644dacfe70f5f072d65b1f3ac1c13 on JamesPHoughton:structuring_readers.

Coverage decreased (-0.1%) to 89.854% when pulling 58850283c089265fc90a4b0b8caad50ca00393d9 on alexprey:structuring_readers into 91ce868339c644dacfe70f5f072d65b1f3ac1c13 on JamesPHoughton:structuring_readers.

Coverage increased (+1.2%) to 91.144% when pulling 9e5d7cdd12b176af5e4544bce0794cfc55e24102 on alexprey:structuring_readers into 91ce868339c644dacfe70f5f072d65b1f3ac1c13 on JamesPHoughton:structuring_readers.

Coverage increased (+1.4%) to 91.402% when pulling d137c0a72859e1ce1643debf072e9bc111812a06 on alexprey:structuring_readers into 91ce868339c644dacfe70f5f072d65b1f3ac1c13 on JamesPHoughton:structuring_readers.

Coverage increased (+1.4%) to 91.402% when pulling 0a48169b024e3db2d446746d4020198c9b3145d5 on alexprey:structuring_readers into 91ce868339c644dacfe70f5f072d65b1f3ac1c13 on JamesPHoughton:structuring_readers.

Hi @JamesPHoughton !
I think that this PR is completed. I'm change title and description.
In travis build we have strange some issues, that I can't understand by which cause it: model execution or unit test. I think we can continue work on this error in separate PR.
Also I think that this solution can be released in nearest feature if you don't have any additional plans for it. Our sdCloud team will be happy when we return the XMILE support and update our environment for it. What do you think about it?

Regards,
Alexey from sdCloud.io development team.

Coverage increased (+1.5%) to 91.468% when pulling edf32fa655bbc1afb95dd21c665640c7a28a752e on alexprey:structuring_readers into 91ce868339c644dacfe70f5f072d65b1f3ac1c13 on JamesPHoughton:structuring_readers.

Hi @JamesPHoughton !
I complete small refactoring and add some additional fixes for xmile and vensim. The good news, I implement logic to detecting the constant equations for aux, flows and stocks. And I fix issue #145 for xmile and vensim (takes solution from PR #148). I introduce this changes because builders for vensim parser fully rewrited by the same logic as for xmile.
I think you will be happy with this changes!

Regards,
Alexey from sdCloud.io development team.

Hi,
I am finding this model I am attaching  a bit challenging.  May be a good
test file.

This is great progress! Thanks for your very good work!
I'll merge into my branch for now, and we can decide how much more to implement before bringing it all the way to master. What are your thoughts on next steps?

We have a good coverage at now and I think we can merge it to master with new release of PySD. And we can quickly integrate the new version to our core of sdCloud.io in nearest release that planed on end of October.
After it we can continue work to improve supporting the XMILE specification. The next stage should be an lookups functionality and something more.
Also I have some interesting plans to refactor core of this library to implementing the new way to providing results as a stream, but it plans so far...

Sounds good. I'll give everything a triple check and bring to master. Might be a few days.
re: refactoring for stream - can you open an issue to discuss?

Thanks!

re: refactoring for stream - can you open an issue to discuss?
Yes, of course.


docs(HelixUI): fix misspelling

Helix UI -> HelixUI

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

Thanks!


Allow the user to visualise the FILA according to a selected range of date

Lets ask MoH first just to make sure. Knowledge Acquisition for now


Refactoring styles

Description

fixing tabs, toolbar styles
fixing main title
fixing some errors (proptypes and props)
removing separate toolbar components (both toolbar components actually used the same one.. so, there is no need to have them)

Before

After

Codecov Report

Merging #13 into master will increase coverage by 0.77%.
The diff coverage is 8.33%.

@@            Coverage Diff            @@
##           master     #13      +/-   ##
=========================================
+ Coverage   21.52%   22.3%   +0.77%
=========================================
  Files          37      35       -2
  Lines         288     278      -10
  Branches       23      23
=========================================
  Hits           62      62
+ Misses        211     201      -10
  Partials       15      15

Impacted Files
Coverage Δ

src/SmartComponents/Workflow/Workflow.js
0% <ø> (ø)
:arrow_up:

src/App.js
0% <ø> (ø)
:arrow_up:

src/SmartComponents/Common/FormRenderer.js
0% <ø> (ø)
:arrow_up:

src/SmartComponents/Request/RequestList.js
0% <0%> (ø)
:arrow_up:

src/SmartComponents/Workflow/WorkflowList.js
0% <0%> (ø)
:arrow_up:

src/SmartComponents/Workflow/Workflows.js
0% <0%> (ø)
:arrow_up:

src/SmartComponents/Request/Requests.js
0% <0%> (ø)
:arrow_up:

...esentationalComponents/Shared/FilterToolbarItem.js
100% <100%> (ø)
:arrow_up:

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 fda4fba...298dfbc. Read the comment docs.

Please merge only after https://github.com/ManageIQ/approval-ui/pull/10

@Hyperkid123


feature: Make pip an explicit dependency of Meltano

Feature scope
Other
Description
Similar to what https://github.com/meltano/meltano/pull/7198 did for virtualenv, we'd make pip an explicit dependency so Meltano doesn't end up using old versions that come with the system, for example.

Great fan, I had to do a fair bit of digging and rejigging to get Meltano to use a specific version.


CB-11034: Camera.getPicture -Handle of OutOfMemoryError gracefull

Catch OutOfMemoryError for memory intensive operations and handle them
gracefully.
Tested on a Samsung SII which throws OutOfMemoryException when taking a photo and fetching it as a DATA_URL.Not able to test when selecting from gallery

Silently handling OutOfMemoryError is not a good idea - we should look to optimize the code so that it uses less memory instead.

Ah, I think I misunderstood your JIRA and I agree with @nikhilkh that optimizing our memory use is the right approach. Looking through the code, it seems we already consume that exception in a number of places when dealing with bitmaps which is probably a very bad thing. Google provides some guidance here on managing bitmap memory.

There are definitely cases where native exceptions should be surfaced to the javascript, but memory issues are the responsibility of the native developer. There isn't much that can be done from the Webview to correctly handle that situation

@riknoll @nikhilkh as an app developer I have to disagree with you.
I would expect a framework such as cordova to never crash an app under no circumstances if it's preventable.
Crashing an app is a very significant event which impacts users perception of the app very negatively and causes a significant effort wrt. end-user support for enterprise apps. It will in many cases cause entered data to be lost, and nothing frustrates users more.
There is lots the app can do to handle such an exception. In my case I can make sure the users understand the issue is because the size of the image and how they can perform workarounds.
Ideally, the CameraLauncher.failPicture would allow me to pass some semantics regarding the nature of the issue for example an error code. But since this was not in place already in the code, I didn't do any changes to it.
However, I totally agree that refactoring the code to reduce the memory footprint is an even better approach which actually tackles the root cause. But this doesn't negate the need to avoid OutOfMemoryErrors when performing memory intensive operations. Even with an exceptionally optimized memory handling of images in cordova-camera-plugin there will always be situations where an OutOfMemoryError occurs, for example if the app uses a lot of memory on the webview side and the device is old with a strict limit on heap size (a G1 had 16MB of heap)


OneDrive Service exception Error code: Unable to parse error response message

The error is persistent for a certain file when trying to upload. Two problems with this:

is the request faulty and if yes, where? Why is the response also faulty?
although the request is made from a try block, the ClientException is not caught in the catch block.
Logcat: https://gist.github.com/sw-dev1/73131f9e7c6bbfb15862

Most likely cause of this error seems to be a long file name with spaces or characters not allowed in a HTTP request. Are there requirements for pre-handling of file names that I might have missed?
A possible workaround is to use  java.net.URLencode as pre-handling. But this leads to server items created with + in the name instead of space. Any ideas how to move forward on (or around) this?

Thanks for the report, the source of the problem is that the filename contains invalid characters for a request url, you should be able to URL encode the file name to prevent this problem.
To the error message, we are getting an xml error from a much lower part of our framework that routes requests which is why the json parsing fails.  Thanks for reporting.

Great that this is solved. Would you recommend java.net.URLencode for URL encoding?  Would names of items be then decoded correctly? I saw server items being created with + in the name instead of space when using java.net.URLencode.


Set recursive true on the ecto.* mix tasks.

This allows you to run ecto.create for example in an umbrella app and
it will create all the repositories in the child apps.
I'm not entirely certain this is the correct way to make this work - what
happens when one of the child apps doesn't use ecto, for example?
If there's a better way to make this work then please let me know. I ran
into this because I'm using Phoenix inside an umbrella app.

Updated as per your comments @josevalim. Thanks.

Thanks @jamesotron. I also not sure myself what is the best way to proceed here. You are correct that the task will fail if it does not have a repository. Maybe the best option is to not make those recursive after all but create aliases in your app. Something like:
aliases: ["ecto.create_all": ["ecto.create -r Foo.Repo", "ecto.create -r Bar"]]

Or just allow multiple repositories to be given:
mix ecto.create -r Foo.Repo -r Bar.Repo

Which you can invoke manually or by creating a quick alias in your umbrella.

Yeah. I'd really like if there was a better way to do this, but I can't quite visualise what that might be. It'd be ace if we could have task dependencies like Make or Rake, or were able to namespace tasks by their app in umbrellas. I'm running into a similar issue with espec also.
I'll have a go with the aliases idea. Thanks.

Yeah. I'd really like if there was a better way to do this, but I can't quite visualise what that might be. It'd be ace if we could have task dependencies like Make or Rake, or were able to namespace tasks by their app in umbrellas. I'm running into a similar issue with espec also.

Task dependencies can be done with aliases:
[aliases: ["ecto.reset": ["ecto.drop", "ecto.create", "ecto.migrate"]]

Regarding the namespacing, we could likely have a task that does just that: mix do --in foo ecto.drop. Or something of sorts.


fix/w-11021600

After W-11021600 decided to add some clarification around a warning on HTTP_PROXY that's usually displayed and may mislead customers.

@PabloCamino please take a look at my edits, thanks!


improve websocket small query performance

Codecov Report
Attention: Patch coverage is 54.54545% with 20 lines in your changes missing coverage. Please review.

Project coverage is 55.62%. Comparing base (a1a52b2) to head (810c46b).

Files with missing lines
Patch %
Lines

...java/com/taosdata/jdbc/ws/AbstractWSResultSet.java
54.54%
13 Missing and 7 partials :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #202      +/-   ##
============================================
- Coverage     55.73%   55.62%   -0.11%
+ Complexity     2223     2220       -3
============================================
  Files           150      150
  Lines         10184    10207      +23
  Branches       1301     1306       +5
============================================
+ Hits           5676     5678       +2
- Misses         3705     3720      +15
- Partials        803      809       +6

Flag
Coverage Δ

unittests
55.62% <54.54%> (-0.11%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Fix unit tests

archaius-pull-requests #323 SUCCESS
This pull request looks good

NetflixOSS » archaius » archaius-pull-requests #158 SUCCESS
This pull request looks good


Output stderr upon test failure

Coverage remained the same at 56.462% when pulling 748b455ed79f972c9711ab6f19c28c85ead2ebdf on output-stderr-on-test-failure into ba57d03a0d1cb502229e04b82f6754dcd6c3060e on master.


No Results Appear Available

Description
No results appear when opening the :Trouble window.  This includes all modes except loclist but only after a loclist has been generated using :LspDocumentDiagnostics (which I believe comes from vim-lsp).
I'm guessing that I'm missing some pivotal config step but I haven't been able to figure out what I'm leaving out.
Any help would be appreciated.
Setup
NVIM: 0.5.0
LSP Client: vim-lsp
Init.vim
call plug#begin()
Plug 'kyazdani42/nvim-web-devicons'
Plug 'prabirshrestha/vim-lsp'
Plug 'mattn/vim-lsp-settings'
Plug 'folke/trouble.nvim'
call plug#end()

let g:lsp_diagnostics_enabled = 1

lua << EOF
  require("trouble").setup {
    -- Empty
  }
EOF

I've encountered a bug where :Trouble lsp_references turns up an empty results window even though :lua vim.lsp.buf.references() shows a list of references like normal.
Environment
Neovim version
NVIM v0.6.0-dev+1745-g516775e9d
LSP client
Built-in Neovim LSP client
Operating system/version
macOS Catalina 10.15.7
Terminal
iTerm2
$TERM variable
xterm-256color
Init.vim
let g:python3_host_prog='~/.asdf/installs/python/3.9.2/bin/python'
let g:python_host_prog='/usr/bin/python2.7'
lua << EOF
require('packer').startup(function()
use 'neovim/nvim-lspconfig'
use {
"folke/trouble.nvim",
requires = "kyazdani42/nvim-web-devicons",
}
end)
EOF
lua << EOF
local lsp = require('lspconfig');
lsp.pyright.setup{}
EOF
lua << EOF
require'trouble'.setup{}
EOF
Steps to reproduce

Open a Python file
Move to a variable that is referenced multiple times in the workspace
Enter :Trouble lsp_references

Expected behavior
The results of :lua vim.lsp.buf.references() should show up in a new Trouble window.
Actual behavior
An empty Trouble window shows up, with the message [Trouble] no results.

Apologies, I believe my bug was introduced upstream quite recently in this PR. I've fixed it in my fork for others using the nightly build of Neovim, and I'll make a PR if/when this change make it into a stable build.

Thanks @HungryJoe !  I gave your fork a try but it looks like maybe the issue I'm seeing has a different cause (as it's still occurring for me).

I'm not sure if this is related but I did see this in the output from nvim -V9nvim.log:
not found in 'packpath': "pack/*/start/*/indent.vim"
not found in 'packpath': "start/*/indent.vim"
not found in 'runtimepath': "lua/trouble.lua"
not found in 'packpath': "pack/*/start/*/lua/trouble.lua"
not found in 'packpath': "start/*/lua/trouble.lua"
not found in 'runtimepath': "lua/trouble/providers.lua"
not found in 'packpath': "pack/*/start/*/lua/trouble/providers.lua"
not found in 'packpath': "start/*/lua/trouble/providers.lua"

None of these files exist under the ~/.config/nvim/plugged/trouble.nvim/ directory (though, there are ./lua/trouble and ./lua/trouble/providers directories).
Other than that, I don't see any other errors.

So this appears to be caused by the fact that I was using vim-lsp as my LSP client instead of NVIM's built-in LSP support.  Converting my setup to use nvim-lspconfig et al fixed this.


Add render_mode parameter for plotly plotting functions

Plotly supports a render_mode parameter which allows switching between the default svg and webgl which is more performant for plots with larger numbers of glyphs.
More info here: https://plotly.com/python/webgl-vs-svg/
Propose exposing this as a parameter in functions that use plotly internally and passing through, to enable use of webgl if desired.

To do: check if being used in all functions.

I haven't yet found a place where render_mode is not supported in the codebase.
However, the mechanism for support is inconsistent. In some places it is explicitly supported as a named parameter, e.g. plot_dendrogram(), whereas, in other places, there is a general-purpose plot_kwargs parameter,  e.g. plot_diversity_stats() has:
        # Scatter plot comparing diversity estimators.
        fig4 = px.scatter(
            data_frame=df_stats,
            x="theta_pi_estimate",
            y="theta_w_estimate",
            error_x="theta_pi_ci_err",
            error_y="theta_w_ci_err",
            title="Diversity estimators",
            width=scatter_plot_width,
            height=scatter_plot_height,
            **plot_kwargs,
        )

In other places it appears to be supported via **kwargs, e.g. plotly_discrete_legend() has
def plotly_discrete_legend(
    color,
    color_values,
    **kwargs,
):
[...]
    fig = px.scatter(
        data_frame=data_frame,
        x="x",
        y="y",
        color=color,
        template="simple_white",
        range_x=[1, 2],  # hide the scatter points
        range_y=[1, 2],
        **kwargs,
    )


Add fallback policy in xds

This is basically keeping the same fallback behavior as grpclb, except for two changes:

To exit fallback mode, the child policy must be READY. Previously, we exit fallback mode as long as the serverlist is received.
We will enter fallback mode as long as the child policy fails. Previously, we should also lose contact with the balancer to enter fallback mode. I feel this can increase the availability of the service. The drawback is that if the balancer usually sends a new serverlist right after the previous serverlist fails, we will waste some cycles to enter and exit fallback mode.

Still need to add/modify some tests, but it's generally ready for review now.

This change is

Closing in favor of #18665.
Will add the fallback-after-startup when needed.


We need a muesli recipe

Hey look at my recipe repository! I have a great recipe that would be awesome for your collection

Thank you @miriamrabels , sounds lovely! I am looking forward to your PR!

closed by #81


Update to Swift 3.0 and RAC 5.0, remove UI Extensions

First of sorry that theres so much in this one Pull Request at once.

Update to Swift 3.0
Update to RAC 5.0
Removal of UIKit/AppKit Extensions and some other little things that are now already part of RAC

I tried to separate these out, but it is all intertwined, Swift 3.0 required RAC 5.0, and then converting all those methods that would be removed in the next step anyway seemed like unnecessary work.
Open Question
Theres two RACSignal extensions:

RACSignal.rex_toSignal()
RACSignal.rex_toTriggerSignal()

For now I was hesitant to require ReactiveObjC/ReactiveObjCBridge just for those two extensions...

ReactiveObjCBridge only contains a toSignalProducer and no toSignal. Either we could add toSignal to the bridge as well, or just remove this conversion?
rex_toTriggerSignal was mostly used internally to convert use rac_willDealloc as a trigger, which now is not necessary anymore with Lifetime.

Complete List of Removals
Those are all documented in Deprecations+Removals.swift, but this list here could also be used in the change log for the next release.
Removals
RAC Extensions

Removed Action.rex_enabledProducer. Use Action.reactive.isEnabled instead.
Removed Action.rex_executingProducer. Use Action.reacitve.isExecuting instead.

Foundation Extensions

Removed NSObject.rex_producerForKeyPath. Use NSObject.reactive.values(forKeyPath:) instead.
Removed NSObject.rex_willDealloc. Use NSObject.reactive.lifetime.ended instead.

UIKit Extensions

Removed Reusable protocol, use Reusable protocol from RAC instead

Removed UITableViewCell.rex_prepareForReuse. Use UITableViewCell.reactive.prepareForReuse instead.
Removed UITableViewHeaderFooterCell.rex_prepareForReuse. Use UITableViewHeaderFooterCell.reactive.prepareForReuse instead.
Removed UICollectionReusableView.rex_prepareForReuse. Use UICollectionReusableView.reactive.prepareForReuse instead.

Removed UIControl.rex_enabled. Use UIControl.reactive.isEnabled instead
Removed UIControl.rex_selected. Use UIControl.reactive.isSelected instead
Removed UIControl.rex_highlighted. Use UIControl.reactive.isHighlighted instead
Removed UIActivityIndicatorView.rex_animating. Use UIActivityIndicatorView.reactive.isAnimating instead.
Removed UIBarButtonItem.rex_action. Use UIBarButtonItem.reactive.pressed instead.
Removed UIBarItem.rex_enabled. Use UIBarItem.reactive.isEnabled instead.
Removed UIButton.rex_pressed. Use UIButton.reactive.pressed instead.
Removed UIButton.rex_title. Use UIButton.reactive.title instead.
Removed UIDatePicker. use UIDatePicker.reactive.date or UIDatePicker.reactive.dates instead.
Removed UIImageView.rex_image. Use UIImageView.reactive.image instead.
Removed UIImageView.rex_highlightedImage. Use UIImageView.reactive.highlightedImage instead.
Removed UILabel.rex_text. Use UILabe.reactive.text instead.
Removed UILabel.rex_attributedText. Use UILabe.reactive.attributedText instead.
Removed UILabel.rex_textColor. Use UILabe.reactive.textColor instead.
Removed UIProgressView.rex_progress. Use UIProgressView.reactive.progress instead.
Removed UISegmentedControl.rex_selectedSegmentIndex. Use UISegmentedControl.reactive.segmentedSegmentIndexes or UISegmentedControl.reactive.segmentedSegmentIndex instead.
Removed UISwitch.rex_on. Use UISwitch.reactive.isOn or UISwitch.reactive.isOnValues instead.
Removed UITextField.rex_text. Use UITextField.reactive.text, UITextField.reactive.textValues or UITextField.reactive.continuousTextValues instead.
Removed UITextView.rex_text. Use UITextView.reactive.text, UITextView.reactive.textValues or UITextView.reactive.continuousTextValues instead.
Removed UIView.rex_alpha. Use UIView.reactive.alpha instead.
Removed UIView.rex_hidden. Use UIView.reactive.isHidden instead.
Removed UIView.rex_userInteractionEnabled. Use UIView.reactive.isUserInteractionEnabled instead.

AppKit Extensions

Removed NSTextField.rex_textSignal. Use NSTextField.reactive.continuousStringValues instead.

Tests
I've kept all the UIKit and AppKit Tests around, but converted them to use the reactive extensions. I've converted them almost completely via quick-fixes to verify that the replacements in Deprecations+Removals.swift work correctly.

What's left in Rex at this point? I've been assuming that Rex would disappear with RAC 5.

I'd day left are

Extensions for ReactiveCocoa that may not fit in the core framework.

😄

some operators on Signal and SignalProducer that are not in RAC like ignoreError, filterMap, timeoutAfter, muteFor uncollect, groupBy
some additional bindings for NSUserDefauls, NSData
Signals for UIViewController for view will/did appear/disappear
Boolean Properties:

        let lhs = MutableProperty(false), rhs = MutableProperty(false)
        let and = lhs.and(rhs)

Personally, I like (and use) the stuff for properties...

Signals for UIViewController for view will/did appear/disappear
These are covered by NSObject.reactive.trigger(for:), which takes a selector.


Subtask 3: Get user gender from user preference

This is a sub-task of https://github.com/rilling/OpenTracksConcordia/issues/188

Commit id - 9713cf992b913ce660ae03f7a1513795e8472148


Is it Possible to send proactive message as a browser notification using service worker?

Is it Possible to send proactive message as a browser notification using service worker?
If yes , is there any example available on how to achieve this?

'How to' questions such as this one are better suited for Stack Overflow. Please feel free to post other questions you have about developing your own features over there so the community at large may help out. Thank you!


feat: #3365 Add more data to the dashboard page chart

add more data to the dashboard page chart such as “Groups,Roles,Certs and so on”

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Gexinyu2333:x: gxygxy seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

add more data to the dashboard page chart such as “Groups,Roles,Certs and so on”

replaced by https://github.com/casdoor/casdoor/pull/3375


This project still alive?

Read the blog posts and looked interesting. Any recent updates?

Not really. It's just too slow for anything useful and often can't find best circuit topologies. Making it better would require adding more intelligence but that is not easy.

It could be nice to have a small note on top of the readme to explain this. (At least have a link to this issue.)


Webhook status code check

If the webhook does not return a happy status i think it would be a good idea to return an error and allow pilot to return the generated output it created.

@kyessenov @costinm

I signed it!

@nmnellis: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
df3a4a2100887a632b7497b1ea9d3e5def44e9fc
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmnellis: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
df3a4a2100887a632b7497b1ea9d3e5def44e9fc
link
/test istio-unit-tests

prow/istio-presubmit.sh
df3a4a2100887a632b7497b1ea9d3e5def44e9fc
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: costinm
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:

pilot/OWNERS [costinm]

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

@nmnellis: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
df3a4a2100887a632b7497b1ea9d3e5def44e9fc
link
/test istio-presubmit

prow/istio-unit-tests.sh
df3a4a2100887a632b7497b1ea9d3e5def44e9fc
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

/retest


CloudSQL Postgres:Ensure that the 'log_min_duration_statement' database flag for Cloud SQL PostgreSQL instance is set to '-1' (disabled)

CIS 6.2.7

Fixed in #116


Is recursion possible?

I ran this code:
var factorial = Fn.new{|n|
  if (n == 1){
    return 1
  } else{
    return n * factorial.call(n-1)
  }
}
System.print(factorial.call(5)) // It's 120.

and got this:
[./main line 7] Error at '}': Variable 'factorial' referenced before this definition (first use at line 5).

So, i guess factorial recursion isn't possible..
or is it? Am i doing it wong

var factorial
factorial = Fn.new{|n|
  if (n == 1){
    return 1
  } else{
    return n * factorial.call(n-1)
  }
}
System.print(factorial.call(5)) // It's 120.

Should get it working.

Oh thanks!


UI framework

front page
about us page
header
footer
navbar
teams
category page
dashboard
summary page
topbar

hey i wish to work on header part

@cyberbuddy-manas  open a new issue for sam and you are all set to go


Scalability issue with missing feature to request "all offers for a known asset ID"

After receiving access to the repo last week, I'm now trying to dig deeper into the protocol spec. One question I have is regarding scalability of requests when the AssetId is already known. In the 'old' specification I understood, that it was part of the IDS protocol to request 'all offers for 1 asset' with adding the 'requestedEelment' to the request to the catalog service.
Ref:
https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Communication/sequence-diagrams/data-connector-to-data-connector
With the 'new' spec, it looks to me like this part is 'outsourced' to the implementation part with the very general 'ids:filter' expression
https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/catalog/message/catalog.request.message.json
I would see this as a very crucial part for scaling. Catalogs can become VERY big. Transferring the whole content even if the requester already knows the asset id is a problem. And outsourcing this scalability critical part should not be desired from my perspective.
My proposal is NOT to define all filters in IDS, but specify a way to 'filter' for one specific assetId only.
Any thoughts on this? Unfortunately I can not join the Thursday meeting this week because of a Catena-X Workshop. Maybe you can comment here if you have thoughts on this.
Thanks in advance,
Matthias Binzer

Closing this issue, since the changes have been merged into the 0.8 release already.


query windows not getting all streaming messages

try "sender:kosak and not instance:graffiti"

Fixed in https://github.com/kosak/z2kplus/pull/16


Profile v3 - main UI

going offchain - partially

Design

updated in Figma, page profile v3 : https://www.figma.com/file/JXNtryaNYhY0XJNArzvPQx/Handoff?type=design&node-id=2116-13786&mode=design&t=3ECZpbp3kGl9oWOO-11
main difference is the top part, bottom one (nft previews) stays the same
extended with profile picture, banner, follow function, bio, different stats
Introduced 14px font size—finally, the time came to use this size—sometimes 16px is just too big, and 12px is just too small.
look for font sizes - for example in the stats section, different sizes than we are used to are used

letsgo
Banner and profile picture

there is banner of size 1440x360 - i guess 360px will be the maximum height
on top of the banner, there is 144x144px big profile picture (padding is 10px - the actually img is only 124px big)

the rest is underneath
Top part

lets start with artist name - this will be the offchain name, if the offchain name is not set, it will show the address

under are buttons

follow - states of the follow button are in the component section
wallet and links - new one, it consists of wallet address and links the user predefined

copy button, transfer (redirect to our transfer page with prefilled address, subscan, subID)

share button

Bio

limited to 200 characters (in the edit profile modal - issue will be linked in the tracking issue)
14px font size

Followed by

this will show people that follow the account, and you follow them - same as Twitter, Instagram, etc.

Stats

bigger this time, bigger font size, different data

then divider and the rest stays the same, now for different states
Different views
Visitor

visitor will see follow button and the things you defined in the profile creation
this is how empty profile looks like (user did not created the offchain profile yet)

placeholder banner, placeholder profile picture, no bio

Owner
this is how the owner will see the empty account

instead of the follow function, there is "create profile"

if the profile is already created, there is edit profile

Mobile

stacks up the components
Dark mode

following the rules of our color system and color pairs

Components section
all useful components found here

issue 1/3

@daiagi few things i realized now
as the default (empty) profile picture, we can use this from from polkadot address
this type:

and here is the follow button prototype. I had issues recording
https://github.com/kodadot/nft-gallery/assets/90852205/e9616046-d1fd-4932-a6ec-5d1da79eaf9d

OK @exezbcz
Thanks for the update , will make the needed changes

hi @exezbcz
almost done
but font-awesome doesn't have farcaster icon
where did you get it from?

@daiagi we use one in success modal - afaik its imported from somewhere

Profile off-chain worker implementation

banner
avatar
profile links


⚠ Fortnite has degraded performance

In 733b108, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1518 ms

Resolved: Fortnite performance has improved in 2441d50.


FlatList is not scrolling.

Hello,
In my accordion component I can't load my flatlist as expected. Flatlist is not scrollable in accordion component.
This is my section instance.
const SECTIONS = [             {                 title: 'title',                 content: flatlist,             },             {                 title: 'title',                 content: flatlist1,             },         ];
and this is how I use accordion component.
<Accordion                             activeSections={this.state.activeSections}                             sections={SECTIONS}                             renderContent={_renderContent}                             renderHeader={_renderHeader}                             onChange={_updateSections}                         />
How can I make my flatlist scrollable?

Can you create an example on https://snack.expo.io that reproduces this? I'd need a full example to debug.


InstanceAdmin::ListInstances ignores failed_locations.

google::cloud::bigtable::internal::InstanceAdmin::ListInstances ignores failed_locations.
failed_locations is used to indicate which locations the RPC failed to get the responses from. If an instance has presence only in a location reported as failed_locations, it will silently be skipped.
Failed locations should be aggregated and reported to the user. If a location is unavailable, we might retry for a while but we shouldn't fail the whole request. Otherwise, the users wouldn't be able to list instances if one location is down.

It is not clear what the proper solution is.
Here is some pseudocode showing how it should work IMO:
ListInstancesResponse GetPage(
    std::shared_ptr<RPCRetryPolicy> rpc_retry_policy,
    RPCBackoffPolicy const &backoff_policy, std::string& page_token,
    grpc::Status &status) {
  // If we're here we're either starting the whole ListInstances thing, or previous
  // call to ListInstances succeeded, so we should use a fresh backoff policy.
  // However, we want to use an RPCRetryPolicy common for all pages to respect
  // the global expectation on the whole operation.
  auto backoff_policy_cloned = backoff_policy.clone();

  btadmin::ListInstancesRequest request;
  request.set_page_token(std::move(page_token));
  request.set_parent(project_name_);
  auto response = ClientUtils::MakeCall(  // this is retried
      *client_, *rpc_policy, *backoff_policy_cloned, metadata_update_policy_,
      &InstanceAdminClient::ListInstances, request,
      "InstanceAdmin::ListInstances", status, true);
  return result;
}

// We return the list of instances and the list of locations we
// failed to get the instances for.
std::pair<std::vector<btadmin::Instance>, std::vector<string>>
ListInstances(grpc::Status& status) {
  auto rpc_policy = rpc_retry_policy_->clone();

  std::string page_token;
  std::vector<Response> failed_responses;
  std::vector<btadmin::Instance> result;
  do {
    auto response = GetPage(rpc_retry_policy, *rpc_backoff_policy_, page_token, status);
    if (not status.ok()) {
      return /* empty result */;
    }
    page_token = std::move(*response.mutable_next_page_token());
    if (response.has_failed_locations()) {
      failed_responses.push_back(std::move(response));
    } else {
      for (auto& x : *response.mutable_instances()) {
        result.emplace_back(std::move(x));
      }
    }
  } while (not page_token.empty());
  // At this point we have all the pages but some of them might contain
  // failed_locations, so we should keep retrying them until the RPCRetryPolicy
  // stops allowing us.
  auto backoff_policy_cloned = backoff_policy.clone();
  grpc::Status forged_unavailable_status(StatusCode::UNAVAILABLE, "some locations failed");
  while (!failed_responses.empty()) {
    if (not rpc_policy.OnFailure(forged_unavailable_status)) {
      break;
    }
    auto delay = backoff_policy.OnCompletion(status);
    std::this_thread::sleep_for(delay);
    std::vector<Response> new_failed_responses;
    for (failed_response : failed_responses) {
      Status local_status;
      auto response = GetPage(
          rpc_retry_policy, *rpc_backoff_policy_,
          failed_response.next_page_token(), local_status);
      if (not local_status.ok() or not rpc_policy.OnFailure(forged_unavailable_status)) {
        // in real code there is more work to do here not to return partial results
        break;
      }
      if (response.has_failed_locations()) {
        new_failed_responses.push_back(std::move(response));
        // or maybe we should put failed_response there
      } else {
        for (auto& x : *response.mutable_instances()) {
          result.emplace_back(std::move(x));
        }
      }
      failed_responses.swap(new_failed_responses);
    }
  }
  // We reached the RPCRetryPolicy's limits but we have full results, just with
  // some failed_locations. Due to that we'll return status OK and the failed locations.
  std::set<std::string> failed_locations;
  for (response : failed_responses)
    for (auto& x : *response.mutable_failed_locations()) {
      failed_locations.insert(std::move(x));
    }
    for (auto& x : *response.mutable_instances()) {
      result.emplace_back(std::move(x));
    }
  }
  return std::make_pair(result, failed_locations);
}