Dev mees

PR of Mees' contributions #27

@bmosseveld Could you look at the following messages?
These messages are the most important:

Variable and function name style should be camelCase.
Use <-, not =, for assignment.
Only use double-quotes.

filename
line_number
column_number
type
message
line
linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
27
3
style
Variable and function name style should be camelCase.
event_cohorts = TreatmentPatterns:::doCreateTreatmentHistory(
object_name_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
27
17
style
Use <-, not =, for assignment.
event_cohorts = TreatmentPatterns:::doCreateTreatmentHistory(
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
34
81
style
Lines should not be more than 80 characters.
expect_equal(nrow(event_cohorts[!(event_cohorts$event_cohort_id %in% eventCohortIds)]), 0)
line_length_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
38
3
style
Variable and function name style should be camelCase.
current_cohorts = c(1, 2)
object_name_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
38
19
style
Use <-, not =, for assignment.
current_cohorts = c(1, 2)
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
48
3
style
Variable and function name style should be camelCase.
current_cohorts <- current_cohorts[ , c("cohort_id","person_id","start_date")] # remove end_date column
object_name_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
48
38
style
Commas should never have a space before.
current_cohorts <- current_cohorts[ , c("cohort_id","person_id","start_date")] # remove end_date column
commas_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
48
38
style
Do not place spaces after square brackets.
current_cohorts <- current_cohorts[ , c("cohort_id","person_id","start_date")] # remove end_date column
spaces_inside_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
48
55
style
Commas should always have a space after.
current_cohorts <- current_cohorts[ , c("cohort_id","person_id","start_date")] # remove end_date column
commas_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
48
67
style
Commas should always have a space after.
current_cohorts <- current_cohorts[ , c("cohort_id","person_id","start_date")] # remove end_date column
commas_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
48
81
style
Lines should not be more than 80 characters.
current_cohorts <- current_cohorts[ , c("cohort_id","person_id","start_date")] # remove end_date column
line_length_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
58
12
style
Variable and function name style should be camelCase.
colnames(current_cohorts) <- c("cohort", "person", "startDate","endDate")
object_name_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
58
66
style
Commas should always have a space after.
colnames(current_cohorts) <- c("cohort", "person", "startDate","endDate")
commas_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
68
18
style
Use <-, not =, for assignment.
targetCohortId = 7
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
78
18
style
Use <-, not =, for assignment.
targetCohortId = c("6", "7")
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
88
18
style
Use <-, not =, for assignment.
eventCohortIds = c(1, 2, 3, 4, 5, 6)
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
98
22
style
Use <-, not =, for assignment.
periodPriorToIndex = "A"
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
108
3
style
Variable and function name style should be camelCase.
event_cohorts = TreatmentPatterns:::doCreateTreatmentHistory(
object_name_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
108
17
style
Use <-, not =, for assignment.
event_cohorts = TreatmentPatterns:::doCreateTreatmentHistory(
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
114
3
style
Variable and function name style should be camelCase.
extended_event_cohorts = inner_join(
object_name_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
114
26
style
Use <-, not =, for assignment.
extended_event_cohorts = inner_join(
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
117
7
style
Put spaces around all infix operators.
by=c('person_id'))
infix_spaces_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
117
10
style
Only use double-quotes.
by=c('person_id'))
single_quotes_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
118
81
style
Lines should not be more than 80 characters.
expect_equal(nrow(event_cohorts[extended_event_cohorts$event_start_date < extended_event_cohorts$start_date]), 0)
line_length_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
122
3
style
Variable and function name style should be camelCase.
event_cohorts = TreatmentPatterns:::doCreateTreatmentHistory(
object_name_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
122
17
style
Use <-, not =, for assignment.
event_cohorts = TreatmentPatterns:::doCreateTreatmentHistory(
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
128
3
style
Variable and function name style should be camelCase.
extended_event_cohorts = inner_join(
object_name_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
128
26
style
Use <-, not =, for assignment.
extended_event_cohorts = inner_join(
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
131
7
style
Put spaces around all infix operators.
by=c('person_id'))
infix_spaces_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
131
10
style
Only use double-quotes.
by=c('person_id'))
single_quotes_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
132
81
style
Lines should not be more than 80 characters.
expect_equal(nrow(event_cohorts[extended_event_cohorts$event_end_date < extended_event_cohorts$start_date]), 0)
line_length_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
145
22
style
Use <-, not =, for assignment.
periodPriorToIndex = 365
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
146
3
style
Variable and function name style should be camelCase.
event_cohorts = TreatmentPatterns:::doCreateTreatmentHistory(
object_name_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
146
17
style
Use <-, not =, for assignment.
event_cohorts = TreatmentPatterns:::doCreateTreatmentHistory(
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
152
3
style
Variable and function name style should be camelCase.
extended_event_cohorts = inner_join(
object_name_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
152
26
style
Use <-, not =, for assignment.
extended_event_cohorts = inner_join(
assignment_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
155
7
style
Put spaces around all infix operators.
by=c('person_id'))
infix_spaces_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
155
10
style
Only use double-quotes.
by=c('person_id'))
single_quotes_linter

D:\Users\mvankessel\Documents\R-Packages\TreatmentPatterns\tests\testthat\test-doCreateTreatmentHistory.R
156
81
style
Lines should not be more than 80 characters.
expect_equal(nrow(event_cohorts[(extended_event_cohorts$event_start_date - extended_event_cohorts$event_start_date) > periodPriorToIndex]), 0)
line_length_linter


Issues to fix

[ ] fireworks in tables take up extra space, replace with red text
[x] make “Requires recreation” the 2nd column
[x] logical resource ids are still looooooong even after trimming. Trim more heavily?
[ ] calculating change sets only makes sense if the change set is calculated on a the merge result with the base branch. Otherwise the changeset should be interpreted as “what would happen if I deploy this PR to ….”. Does the same apply to the diff?
[x] Use second template with collapsed diff

Text colour comes with some pretty significant downsides, naimly that it cannot be copy-pasted, is not supported on mobile at all and support for it on desktop is very flaky.


better parent for CHEBI:133747

CHEBI:133747 is unaware of the stereo-unspecific CHEBI:82968 which is clearly a parent of it. Also, the stereo-unspecific name "γ-Glu-Thr" and the synonym "γ-glutamylthreonine" are identical to those of CHEBI:82968.

Thanks for letting us know. This has now been corrected.


Account Confirmation Error

Users are reporting that when they sign up for a DRAW account they encounter an error in being unable to change their password or confirm their email address and thus login to their account to begin transcribing.
The error encounter is as follows:
"DNS_PROBE_FINISHED_NXDOMAIN" and “ERR_EMPTY_RESPONSE"
Users tried the following to trouble shoot:

check FAQ
reload page
ask for another confirmation email to be sent
check internet connection
delete all my cookies
open VPN
close VPN
reset CMD
reset DNS

This has now been resolved


feat: Add support for count(*) aggregation query firestore

Adding count(*) functionality in firestore

Hi @jskeet @amanda-tarafa ,
Its a draft PR for query count feature. Its still under process.
I have raised the PR to get some internal feedback on the same.
Please do not review. Will let you know once the changes are finalized.
Thanks,

I will have a look later today after going through the design document. Thanks.

Hi @jskeet  @amanda-tarafa ,
This is now ready for review.
Please review and provide you feedback.
Thanks,

Will look when I get the chance - even coming back from one day off, I've got a bit of a backlog...

Thanks for the feedback Jon. I will address them and let you know.


the model weights can not be found on the shared link.

the model weights can not be found on the shared link.
please share the model and if it is possible training data

Thank you for reporting! Something went terribly wrong with my owncloud and deleted all these files. They are back now.


Fix publisher pool size

rosout topic is not used anymore in micro-ROS so an extra publisher for each node is not necessary

@mergify backport foxy galactic


bugfix for kitti

Hi Simon,
some bugfix as follow.

reader/kitti.py: line44 and line 99
samples = None ->samples =-1;
because samples = 32 if args.debug else -1 in main.py line194;
reader/kitti.py: line98
num_files = (len(os.listdir(path_testing)) - 1) // 2 -> num_files = len(os.listdir(path_testing)) // 2;
reader/kitti.py: line105 & line106
img0 = cv2.resize(img0, resize)
img1 = cv2.resize(img1, resize)
->
adj_resize = (resize[1], resize[0])
img0 = cv2.resize(img0, adj_resize)
img1 = cv2.resize(img1, adj_resize)
because cv2.resize() should be dim(width, height) -> dim(cols, rows)

Hi Rongliang, thanks a lot for bugfixing!
We will fix them in the repo soon.

Bu it seems you haven't updated this fix in the repo.

Hi @chengrongliang ,
Thanks for sharing this bug.
I'm wondering if you can get the evaluation results of Kitti 2012/2015 as they reported in the table (e.g., 3.25, 0.11 | 9.14, 0.18 for dbbSep30) or not.
I have modified the codes and fixed the bugs, however, the calculated AEPE and F-1 are not matching.
Hope to hear from you soon.


Auto corrected by following Format Ruby Code

Auto corrected by following Format Ruby Code
Click here to configure it on awesomecode.io

Coverage decreased (-0.03%) to 80.251% when pulling 0fa9cceab1ab01aeb20d72639a8da10b8c593056 on awesomecode-format-ruby-code-48118 into 595cea9b452c6ab376ad99c9e1efcff932a30a8d on master.


feat: add following and follower tabs to profile page

Adds following and follower tabs to the profile page.
Closes #617

although the data for following/followers is only being fetched depending on the value from the query params, we no longer are seeing the number.

I tried setting staleTime to Infinity similar to the profile card but still seems to show up with no followers/following if you refresh the page. Do you know how we can access the cache for each address?

@gregogun I didn't think about this indeed, that's a problem. We need to fetch this data somehow and as there is no API endpoint to just fetch the number it's tricky. I created this pull request adding the required data, so now you should have all the data you need :) https://github.com/sigle/sigle/pull/638

ok perfect will use that, thanks! :D


three-stdlib/index.cjs.js - Illegal variable reference before declaration: i

three version: 0.129.0
three-stdlib version: 2.1.0

Problem description:
When I try to get a production build with shadow-cljs (It uses Google Closure library), I get the following error:
Closure compilation failed with 2 errors
--- node_modules/three-stdlib/index.cjs.js:2
Illegal variable reference before declaration: i
--- node_modules/three-stdlib/index.cjs.js:2
Illegal variable reference before declaration: t

If I don't require @react-three/drei library in the namespace/class/my project everything seems fine, I assume some code in the library is broken/invalid, but Webpack is able to ignore it and process it.
Here is the discussion with the author of shadow-cljs:

You forgot to fill out the relevant code part of the template. If you can recreate this bug in a small reproduction, we'll be able to look into it 👍🏼

@joshuaellis Here is the repo https://github.com/ertugrulcetin/racing-game-cljs and I created a branch for the repro: repro-three-stdlib-bug, you can run the project through README. After npm run watch you'll see the error.

@ertugrulcetin
I also run into this bug using closure compiler and shadow-cljs. I figured out you can sidestep this issue by using the different module type in the shadow-cljs.edn config:
:builds {:main
          {:target     :browser
           ;;snipped details
           :js-options {#_#_:entry-keys ["module" "browser" "main"]
                        :resolve {"three-stdlib" {:target :file :file "node_modules/three-stdlib/index.js"}
                                  "@react-three/drei" {:target :file :file<EMAIL_ADDRESS>                                  "@react-three/fiber" {:target :file :file<EMAIL_ADDRESS>           :compiler-options {:infer-externs :auto
                              :output-feature-set :es6}}
          }

Note that the closure compiler is probably complaining about a legitimate issue, so it would be great if this bug is fixed, but this should get you further for now.

@bbss thank you so much! But I still have some problems, when I remove drei require from the namespace everything works otherwise I get the following error and the app crashes:

Here is my shadow-cljs config:
:target :browser
:js-options {:resolve {"three-stdlib" {:target :file :file "node_modules/three-stdlib/index.js"}
                       "@react-three/drei" {:target :file :file<EMAIL_ADDRESS>                       "@react-three/fiber" {:target :file :file<EMAIL_ADDRESS>                       "@react-three/cannon" {:target :file :file<EMAIL_ADDRESS>:compiler-options {:infer-externs :auto
                   :output-feature-set :es6}

This error looks like it's to do with three-mesh-bvh not three-stdlib?

@bbss could you fork the project and try on? Maybe I'm doing something wrong...

@joshuaellis nope, it's three-stdlib. There is something wrong/invalid code inside node_modules/three-stdlib/index.cjs.js.

@joshuaellis When I add this code (regeneratorRuntime) to drei library everything seems work now:
@react-three/drei/index.js:
import regeneratorRuntime from "regenerator-runtime";
Could you add this so every other JS platform can leverage these libraries?

I haven't had the time to look into this issue yet, but I'm not sure if drei should be supplying regenerator-runtime as some people will be using this in their own projects already.
Also, i've just checked out the repo, it's very hard to understand whats going on there, I would suggest you just isolate the problem to a simple scene using r3f & drei.

@joshuaellis Sorry, you're right. I had to be more clear, drei uses three-stdlib so I thought maybe this workaround might work. But I found a way, just adding regenerator-runtime as a dep and my project is able to work. I had to use modules so I don't get this Illegal variable reference before declaration error. I think we can close this issue, it seems that the libraries work with webpack projects without having a problem.

I was able to resolve the issue by adding the following to my shadow-cljs.edn:
:js-options {:entry-keys ["module" "browser" "main"]}

But you should consider what the shadow-cljs documentation says about using the :entry-keys JS option:

Make sure to test thoroughly and compare the build report output to check size differences when switching this. Results may vary greatly in positive or negative ways.

Using :js-options {:resolve ...} as mentioned by @bbss (above) also works for me. I don't get any errors in the DevTools Console (Note: I tried it in my own project and not the mentioned example repo).
For both solutions, there was no need to pull in extra deps or change anything else.


On the road to simpler components & better dev experience

🚧 ➡ 🛣 work in progress pull request

State of the art, summer 2016 🚀
The project is developed in 24 hours: the React components are working, though it takes time to read through them / make a modification (ex: jQuery was actually used somewhere, at some point, to clean :empty DOM 🛩 🌮)
Pimped components ✨
This PR intends to:

provide a better dev experience thanks to a component explorer (Storybook) and tests (snapshot testing with Jest);
components easier to read, manage and update by tending toward functional components (recompose ftw) and using of CSS-in-JS (styled-components).

What's going on now? 🛠

[x] Setup Storybook with mocked data apollo-test-utils

it's working!
uncertainty: are there better way to mock data than the way I did?

[ ] Setup snapshots testing thanks to Storyshots

it's working however...
I need to use a local addDecorator cause of https://github.com/storybooks/storyshots/issues/68 (will find time to fix this problem there)
I'm not using jest-transform-graphql, it's obsolete (screenshot of the bug). I rolled my own (~fork), I don't believe I'm using the graphql-tag/loader the right way (RecentTours snapshots are displaying "Loading..." 👎 https://github.com/partyparrot/codetours/commit/a77f2b0489f53ceb6f22b0701dc777fe686fea37#diff-c2bc02f8e206c05e949653f49305bf42).

[ ] And of course, write useful stories helping understand the app and refactor the components

TourBadge is used in RecentTours & Tour 🤓
still a lot to do there 👍

Note: I've hit (and solved/got around) quiet a few walls while setting up the tooling, happy to talk about the decision taken. And happy to talk about the components refactoring / styling / direction of the project 🙂

I'm closing this, I'm working on something really simpler (lol) and with a better user experience
Sneak peek:


It doesn't expect other folder then src

I've downloaded an example
https://github.com/sgb-io/codehawk-cli-example
and it is looking to work well, but ./node_modules/.bin/codehawk ./src/util scan the others also, so I'm getting same result as for npm run codehawk.
There is also parsing issue.
I would expect to see scan result from util folder only.
[codehawk-cli] Unable to parse "/Users/dominikjelinek/my/Development/sandbox/codehawk-cli-example/src/util/other-examples/cannot-be-parsed-correctly.ts", skipping

    Codehawk Static Analysis Results
    Top 5 files

    | File                                               | # of Lines | Times Used/Depended On | Maintainability (higher is better) |
    | -------------------------------------------------- | ---------- | ---------------------- | ---------------------------------- |
    | /src/util/complex-utils.js                         | 99         | 1                      | 50.76 (Could be better)            |
    | .../util/other-examples/can-be-parsed-correctly.ts | 58         | 1                      | 56.77 (Could be better)            |
    | /src/typescript-supported-too/typescript-sample.ts | 11         | 1                      | 70.73 OK                           |
    | /src/pages/index.js                                | 209        | 1                      | 89.94 OK                           |
    | /src/pages/api/hello.js                            | 6          | 1                      | 91.93 OK                           |

[codehawk-cli] Generating maintainability badge...
[codehawk-cli] Badge was generated

Closing due to https://github.com/sgb-io/codehawk-cli/issues/122
Hopefully you will not experience this issue using FTA


Cannot find module “cordova/exec” in ionic 2

I am trying to develop a project in typescript, but for it i need to run a library in javascript, the link for the library is that https://www.grabba.com/downloads/cordova/plugin.
When i try to run this library in with my code, the ionic 2 return the error above. I am trying to solve it per days, and already pass for all the integration javascript and typescript tutorials in the google. Would someone help me to run this library?
My codes follow bellow:
guarda-codigo.ts:
import { Component } from '@angular/core';
import { NavController } from 'ionic-angular';
import { GrabbaProxcard } from './com.grabba.cordova.plugin/www/grabba';
    declare var cordova: any;

    /*
      Generated class for the GuardaCodigo page.

      See http://ionicframework.com/docs/v2/components/#navigation for more info on
      Ionic pages and navigation.
    */
    @Component({
      selector: 'page-guarda-codigo',
      templateUrl: 'guarda-codigo.html'
    })
    export class GuardaCodigoPage {

      constructor(public nav: NavController) {
          function acessaGrabba(value: number){
          let proxcard = new GrabbaProxcard();
            proxcard.prototype.registerCallback();
          }
      }

      ionViewDidLoad() {
        console.log('ionViewDidLoad GuardaCodigoPage');
      }

    }

Someone could help me please? I really need to solve this problem. I will be very grateful. Thank you for the attention.

same issue here


fix/ Add C++17 build flag in CMakeList pybind

Just add 2 flag of CMAKE  in CMakeLists.txt config to force the gcc build using C++17
set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_STANDARD_REQUIRED ON)
Otherwise  the command 'python setup.py install' will be failed on some machine. Because of requiring CPP > C++14 when building the binding lib

Thanks for reporting this. The problem is that we did not test the setup.py build option properly. If build from the top-level CMakeLists.txt the standard is already set to 17. Could you please do me the favor and move the two lines down into the if (NOT hasParent) block. That is the path that has the issue.

I have changed

Thanks!


Incomplete output when source files are large

Refs: https://github.com/nodejs/node/pull/54994
When the source files are large, the outputs will be incomplete, like env.cc (81K) or node_contextify.cc (69K).

The solution is to avoid manually calling process.exit or to call it after stdout is flushed.
However, I now intend not to fix it this way.
Considering the maintenance costs,  I'll directly compile the original clangFormat.cpp, which will ensure full support for the original CLI features.


Update carbon.identity.framework version

$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/3737485136


chore(master): release 1.1.197

:robot: I have created a release beep boop
1.1.197 (2023-10-02)
Miscellaneous

deps: update dependency vite-node to v0.34.7 (5438e15)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/keywind/releases/tag/v1.1.197 :sunflower:


Update index.md - "arbitrary" typo

fix typo

HI @vielmetti, Thank you for picking this up. It has been addressed.


fix recent clang build proposal.

-Weverything implies -Wunsafe-buffer-usage, compilation fails because of pointer_offset macro, regardless the offset is negative or not.

Hmm, I literally just committed the same thing, not sure why github is not picking up on that in this PR... https://github.com/mjansson/rpmalloc/commit/e6fe78ecf86265a7fe89929198aa1d3b42c4c483


[Connectivity] Fixes issue "connectivity using deprecated api"

Description
This pr will fix issue "connectivity using deprecated api"
Related Issues

#29770 and #33768 on Flutter

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

@cyanglaz Hi, could you please review my pr. Thank You

@hey24sheep Thanks! Do you mind fix the format before I can merge this in?

@cyanglaz I have pushed the changes. Kindly have a look. Let me know if there is anything else form my part. Thank You

@hey24sheep which time this PR will be merge with this library?

It's already merged

It's already merged

Im still getting the error
‘’’
connectivity-0.4.4/android/src/main/java/io/flutter/plugins/connectivity/ConnectivityPlugin.java uses or overrides a deprecated API.
‘’’

@Fernandomr88 +


Failed to build release 0.5.0 with gcc 5.4 and default -std setting

Here is the diagnostic:
[ 50%] Building CXX object CMakeFiles/test_package.dir/test_package.cpp.o
In file included from /tmp/c3ipr/pr_66_1_0_0/test_package/test_package.cpp:1:0:
/tmp/c3ipr/pr_66_1_0_0/.conan/data/span-lite/0.5.0/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/nonstd/span.hpp: In function ‘void nonstd::span_lite::detail::throw_out_of_range(nonstd::span_lite::index_t, nonstd::span_lite::index_t)’:
/tmp/c3ipr/pr_66_1_0_0/.conan/data/span-lite/0.5.0/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/nonstd/span.hpp:614:11: error: ‘out_of_range’ is not a member of ‘std’
     throw std::out_of_range( "span::at(): index outside span" );

More details here: https://github.com/conan-io/conan-center-index/pull/66#issuecomment-533714103

I can prepare the corresponding pull request but the new release should be issued in order to successfully push it to the conan repository.

Hi @flexferrum , would you be willing yo handle it (making you a contributor here)?

Yes, I would. But I can't make releases here.

Invitation sent, let's see how far it brings us.

Invitation accepted.

I've got the all desired access. Thanks!


Fix semantics of provide and improve type inference

This is mainly to fix semantics of provide which was incorrectly using "last one wins" instead of "scoped provision". However, I also improved type inference.

I can't see how using ZIO.bracket doesn't allocate two objects: BracketAcquire and BracketRelease.
If my computation will use bracket in hot path (for example to acquire some Ref or Semaphore) then it will cause many allocations.

@LGLO Did you see if we can fix by some other means? Sorry overnight 17 pull requests appeared and I am way behind on reviews. Will do more tomorrow.
My other idea is to have a ZIO.bracket which takes ALL parameters at once. Then the "syntax sugar" method simply delegates to this one. This way if you have it in a hot path, you just use the uncurried form...

@jdegoes I made this uncurried version but TBH I don't really like it if was the only version available. Having both looks good to me.
Is ZIOInvarant required? Why is it better than instance methods?

@LGLO Can you submit a pull request to my pull request? 😄
ZIOInvariant improves type inference by eliminating one layer of widening (if we put it onto ZIO directly, then we have to widen all parameters).

Happy to help, but tomorrow, if that isn't a problem.
niedz., 3 mar 2019, 22:45: John A. De Goes<EMAIL_ADDRESS>napisał(a):

@LGLO https://github.com/LGLO Can you submit a pull request to my pull
request? 😄
ZIOInvariant improves type inference by eliminating one layer of widening
(if we put it onto ZIO directly, then we have to widen all parameters).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/scalaz/scalaz-zio/pull/597#issuecomment-469067641,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACkc0SMkJ70tSnlUQaCD8lxOIG6wOaAOks5vTEJugaJpZM4bbKB5
.


CreateFunctionCommand fails on functions with empty lines

Attempting to create a function via ParseAndCreateCommand fails when the parsed function has empty lines. I was able to repro the failure, which is thrown from CreateFunctionCommand::TrimFunctionSchemaBody, with the below function.
.create-or-alter function aa()
{

// something
range dateHour from 1d to 10d step 1d
}

The issue appears to be upstream from CreateFunctionCommand, potentially in KustoCode.Parse, which only parses ".create-or-alter function with (skipvalidation = \"true\") aa() {". Is this empty line behavior expected? If so, should the fix be made in Kusto.Language package?

Delta Kusto assumes each command is separated with one (or many) empty lines.  So it breaks a script into commands by the empty lines.
Having an empty line in a function therefore...  breaks its algorithm (no pun intended).
Workaround would be to remove those empty lines.


Fixes 18349: proper version comparison

Describe your changes:
Fixes 18349
I worked on openmetadata-airflow-apis/opendata_managed_apis/api/utils.py because reported bug prevented DAG deployment in Airflow 2.10.2.
Changes were tested by using updated file in custom Airflow image and creating DAG from OM UI.

Type of change:

[x] Bug fix
[ ] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.

[x] My PR title is Fixes <issue-number>: <short explanation>

[ ] I have commented on my code, particularly in hard-to-understand areas.

[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

[ ] I have added a test that covers the exact scenario we are fixing. For complex issues, comment the issue number in the test for future reference.

Hey @IceS2
Python checkstyle is happy now

Hey @IceS2
When you have time, can you take a look, please?

@pmbrull @IceS2 @harshach
Anyone, please?

Thanks @imishchuk-tsgs
Found this issue when testing OM 1.6.0.rc3 with Airflow 2.10.3. I've applied this fix and it work.
This is a bug, since version strings can not be compared literally. For Python, "2.6" > "2.10.3".

thanks for the PR!


Improve unhandled rejection reason strings

This PR improves the strings that end up in Q.getUnhandledReasons() two different ways:

Ensure that unhandled rejection strings created from actual Errors in all modern browsers include the error type and message (in addition to the stack).
Add a hook, Q.customizeRejectionString which can be used for developers to customize how rejection values are string-ified.

For 1, the problem I ran into was that rejection reasons inside Q.getUnhandledReasons() didn't actually contain the error type and message and they only had the error stack in some browsers. This is because Q uses error.stack and the output of error.stack in Firefox and Safari is different than I expected. For example:
try { throw new Error('Test error') } catch (e) { console.log(e.stack) }

// in Chrome (and similar in Edge/IE)...
// => Error: Test error
// =>      at <anonymous>:1:13

// but in Firefox and Safari the error type and message isn't included, and you get ...
// => @debugger eval code:1:13

Not only was that surprising to me, but it makes tracking down the unhandled rejections that real users run into in Firefox & Safari much harder to debug since the error message is missing. So in these changes I detect when error.stack is missing the error type & message and manually insert it to the beginning of the string that ends up in Q.getUnhandledReasons():
Before in Firefox
Q.reject(new Error('faux error'));
Q.getUnhandledReasons()[0];
// => @debugger eval code:1:10

After in Firefox
Q.reject(new Error('faux error'));
Q.getUnhandledReasons()[0];
// => Error: faux error
// => @debugger eval code:1:10

While 1 is an improvement, it doesn't help when some code rejects an object, primitive, or custom instance (which don't have a stack strace). So 2 adds the Q.customizeRejectionString hook which can allow developers to customize unhandled rejection strings themselves. For example:
CustomClass = function () {}
Q.reject(new CustomClass)

Q.getUnhandledReasons()[0];
// => (no stack) [object Object]

// But if we add this...
Q.customizeRejectionString = function(reason) {
  if (reason.constructor && reason.constructor.name) {
    return 'CUSTOM: ' + reason.constructor.name;
  }
};

Q.reject(new CustomClass)

Q.getUnhandledReasons()[1]
//=> (no stack) CUSTOM: CustomClass

Or some JSON.stringify-ing...
Q.customizeRejectionString = function(reason) {
  if (!(reason instanceof Error) && typeof reason === 'object') {
    return JSON.stringify(reason)
  }
};

Q.reject({ foo: 'bar' });
Q.getUnhandledReasons()[0]
// => (no stack) {"foo":"bar"}

I know that we ideally should only be rejecting JS errors and not other values, but we're far from perfect. We have plenty of code written before we had a better understanding of promises, have legacy CoffeeScript where automatic returns can get in the way, need to do a better job of teaching developers about promise foot-guns, etc. So Q.customizeRejectionString could a big help for us to track down some of these problematic promise chains.

I should also mention that I've added a some tests for these changes, ensured npm test was green, and ran q-spec.html in a few browsers (latest Chrome, Firefox, and Safari).
ps: This PR and https://github.com/kriskowal/q/pull/816 came out of me trying to provide better tooling to other (HubSpot) developers trying to track down and fix various unhandled rejections. On our production apps we have code that polls Q.getUnhandledReasons() every 5 seconds, sending anything there to a JS error tracking service. While that helped us track down several  problematic promise chains, there still were many unhandled "errors" that were useless. And I'm hoping these changes will help track those down.

Released in v1.5.1

Looks like ^ comment on v1.5.1 is accidental? (The PR isn’t merged and I don’t see any other commits in 1.5.1 related to this) ¯\_(ツ)_/¯

@timmfin Indeed. There was an unrelated change to the same feature.


Specify default for write_compression config

update create_table_as.sql and specify default write_compression as none

I tested this in my local dbt project and it appears to resolve #93 .

@Tomme can you merge this change?
this is pretty urgent fix.

Thank you!!


Unable to open Gitpod

What version are you using?
Just clicking the link in the README.

What did you do?

Tried to open the repo in Gitpod
What did you expect to see?
Success
What did you see instead?

If I try and Continue with the Default Image I get this in the console in Gitpod
 HISTFILE=/workspace/.gitpod/cmd-0 history -r; {
cargo fetch
make build test

} && {
gp ports await 23000
gp open README.md
gp open increment/src/lib.rs
gp open increment/src/test.rs
gp open README.md
soroban invoke --id 1 --wasm target/wasm32-unknown-unknown/release/soroban_increment_contract.wasm --fn increment

}
gitpod /workspace/soroban-examples (main) $  HISTFILE=/workspace/.gitpod/cmd-0 history -r; {
> cargo fetch
> make build test
>
> } && {
> gp ports await 23000
> gp open README.md
> gp open increment/src/lib.rs
> gp open increment/src/test.rs
> gp open README.md
> soroban invoke --id 1 --wasm target/wasm32-unknown-unknown/release/soroban_increment_contract.wasm --fn increment
>
> }
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: latest update on 2023-01-10, rust version 1.66.1 (90743e729 2023-01-10)
info: downloading component 'cargo'
info: downloading component 'clippy'
info: downloading component 'rust-src'
info: downloading component 'rust-std' for 'wasm32-unknown-unknown'
info: downloading component 'rustc'
info: downloading component 'rustfmt'
info: downloading component 'rls'
info: downloading component 'rust-analysis'
info: downloading component 'rust-std'
info: removing previous version of component 'cargo'
info: rolling back changes
error: could not rename component file from '/home/gitpod/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/etc/bash_completion.d' to '/home/gitpod/.rustup/tmp/ojn2k3qp55an_9t6_dir/bk': Invalid cross-device link (os error 18)
cargo build --target wasm32-unknown-unknown --release -p soroban-token-contract
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: latest update on 2023-01-10, rust version 1.66.1 (90743e729 2023-01-10)
info: downloading component 'cargo'
info: downloading component 'clippy'
info: downloading component 'rust-src'
info: downloading component 'rust-std' for 'wasm32-unknown-unknown'
info: downloading component 'rustc'
info: downloading component 'rustfmt'
info: downloading component 'rls'
info: downloading component 'rust-analysis'
info: downloading component 'rust-std'
info: removing previous version of component 'cargo'
info: rolling back changes
error: could not rename component file from '/home/gitpod/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/etc/bash_completion.d' to '/home/gitpod/.rustup/tmp/89ua23syzap5peox_dir/bk': Invalid cross-device link (os error 18)
make: *** [Makefile:10: build] Error 1
gitpod /workspace/soroban-examples (main) $

When I tried to open the Gitpod for examples this morning, 20230120, I got this both during initial startup and after running "gp rebuild"
Step 11/18 : RUN rustup update stable
---> Running in 5f1dea715501
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: latest update on 2023-01-10, rust version 1.66.1 (90743e729 2023-01-10)
info: downloading component 'cargo'
info: downloading component 'clippy'
info: downloading component 'rls'
info: downloading component 'rust-analysis'
info: downloading component 'rust-src'
info: downloading component 'rust-std'
info: downloading component 'rustc'
info: downloading component 'rustfmt'
info: removing previous version of component 'cargo'
info: rolling back changes
error: could not rename component file from '/home/gitpod/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/share/zsh/site-functions' to '/home/gitpod/.rustup/tmp/my2sx_fbx0uo2n08_dir/bk': Invalid cross-device link (os error 18)
The command '/bin/sh -c rustup update stable' returned a non-zero code: 1
Image Build Failed


Skeleton implements Structure

For #100.
As discussed with the architect, we should have more composability. Skeleton now implements Structure so it can be decorated, like this:
    Structure classes = new MergeTypes(
        new Skeleton(base)
    );

classes will now provide the base XML representation (the "skeleton") altered in some way via MergeTypes -- this Structure decorator, as well as Skeleton, should work based on an XSL stylesheet.
Added 2 puzzles:
1 for continuing implementation of Structure decorators
1 for adding more ctors to Report. The way it is done now is not so composable since Structure.xml() has to be called before instantiating the Report.

Job #157 is now in scope, role is REV

@0crat status

@0crat status (here)

@amihaiemil This is what I know about this job, as in §32:

The job #157 is in scope for 1hr
The role is REV
The job is assigned to @carlosmiranda/z for 3min
There is a monetary reward attached
@carlosmiranda/z will get 25% of their hourly rate for this job
The job doesn't have any impediments
The budget is 15 minutes/points
These users are banned and won't be assigned:

@amihaiemil/z: This user reported the ticket

This pull request #157 is assigned to @carlosmiranda/z. The budget is 15 minutes, see §4. Please, read §27 and when you decide to accept the changes, inform @yegor256/z (the architect) right in this ticket. If you decide that this PR should not be accepted ever, also inform the architect.

@yegor256 @amihaiemil looks good to me, we can proceed.

@yegor256 ping :)

@amihaiemil I don't think it's right. I would go with a different design:
XML xml = new XSLChain( // from jcabi-xml
  new XSLDocument("xsl/skeleton-first.xsl"),
  new XSLDocument("xsl/skeleton-second.xsl"),
  new XSLDocument("xsl/skeleton-third.xsl"),
).transform(new Skeleton().xml());

No new classes, just a collection of new XSL stylesheets.

@yegor256 I see. I'll look into it later today.

@amihaiemil I actually forgot about this XSLChain class... see how it can make the code look nicer: cb9b37d

@yegor256 Done. Now each report has the skeleton transformed according to its metric. But I still think Skeleton should have an interface and be decorated somehow -- now there is also the problem of saving. Only the common skeleton is saved, not the one transformed for each report. :_? It needs to be a proper object :D Should I leave a puzzle about that?

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 10min)

Order was successfully finished: +15 points just awarded to @carlosmiranda/z, total is +1245

Payment to ARC for a closed pull request, as in §28: +15 points just awarded to @yegor256/z, total is +9640

The job #157 is now out of scope


Don't reattempt webhook delivery after non-transient HTTP errors

Fixes #14559
This makes Saleor give up immediately when it encounters a non-transient HTTP error (HTTP 4xx) or a redirect attempt (HTTP 3xx).
Change in behavior: we previously considered any HTTP status between 200 and 399 a success. Now, only 200-299 are considered successful.
I want to merge this change because...

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations

Docs

[ ] Link to documentation:

Pull Request Checklist

[ ] Privileged queries and mutations are either absent or guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migrations are either absent or optimized for zero downtime
[ ] The changes are covered by test cases

@patrys Should we port these changes to versions between 3.14 and main?

@maarcingebala Good question. If we want to backport this, we need to make sure it's not a breaking change for any customers.


build RPM for peridot cli

todo: actually make semver releases.

#169  👈
main

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

Join @NeilHanlon and the rest of your teammates on  Graphite


Fix typo in Build Guide

@Dylan-Brown
In the Build Guide change to take affect to to take effect.
@sumitshyamsukha and @JudyWeng can help with opening a pull request.

So, I made the relevant change in the documentation. However, I can't commit to the project. Should I fork and make a pull request?

Yes you'll need to make a fork.

Pull request here: https://github.com/AnalyticalGraphicsInc/cesium/pull/4486


adding transition & animation to navbar and footer buttons to animated portfolio - frontend project

To add transition and animation effects to navbar buttons and social media icons in the footer to make the links more interactive.
They are not easily recognizable.

@pranjay-poddar kindly assign me this issue under GSSOC'23

@TusharKesarwani @MohitGupta121 kindly look and assign the issue under GSSOC23


Presence and Visible of NormalizedLandmark  always zero

Plugin Version or Commit ID
v0.10.3
Unity Version
2021.3.5f1
Your Host OS
window 10
Target Platform
Android
Description
Presence and Visible of mediapipe::NormalizedLandmarkList  always zero.
but mediapipe::LandmarkList has Presence and Visible correct value.
how can i get Presence and Visible of mediapipe::NormalizedLandmarkList ?
Code to Reproduce the issue
No response
Additional Context
No response

duplicates #601
Please check if the official sample app returns presence first.


Fix potential NullReferenceException

Fixes https://github.com/Azure/azure-sdk-for-net/issues/34950

/azp run net - servicebus - tests

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

The prefetch count would be updated on the next iteration of the RunReceiveTask loop.

👍  That addresses my concern.  We still reflect the right value eventually, timing is just delayed.


Add option to save the INITIAL .zshrc file if it exists

the idea is that a zshrc_backup file is created everytime you run the script.
that will stay but i want to create an INTIAL zshrc (if one existed) that a user can manually go back to and have all the configs they had before

https://github.com/Xmetalfanx/zshSetup/commit/7764506b37bc25bedd9e20aad011fbead432d4fc adds this support


Tree level prediction algorithm

It is strange that raising  skills to +1 crown level counts towards achieving next tree Level.
Example: My tree is at L2.  and was predicted to be at L3 in 2021. I have some skills at L3 which i raised to L4. Now it predicts i will reach L3 by the end of 2020.
Personally i would use only skills  that were raised from L2 to L3 as prediction to achieving L3 tree.

It should already be working as you suggest. There are a few things that could cause the prediction date to change. The first is that that you are seeing a fall-back prediction method being used. The second is that it is using the main prediction algorithm, and you noticed the date change when you reached your daily goal, which is when it takes into account the progress you have made today.
There are two prediction methods: one based off of the user's extended profile file, and one based off of Duo Strengths saved record of the changing progress over time. The latter can only be used if there is enough saved data, it requires at least 5 progress making entries (essentially 5 days on which progress was made towards the next tree level). If there is not enough of these entries, the first method based off of the calendar section of the user's data file. This calendar method is (as far as I can tell) what duome uses.
The calendar section in the userData file is a record of all the XP earning events of a user from the last 3 weeks, with how much XP was earned, the skill ID (if not a story) and a timestamp of when it happened. This is the same information that you view if you click on show RAW on duome above the daily progress graph. Here is a sample of my calendar:
7:  {skill_id: "c37fb34b037212ed2332436bdfb83253", improvement: 12, event_type: "lesson", datetime:<PHONE_NUMBER>000}
8:  {skill_id: "fb9af227309b0ab90d81c5e1caedfe5d", improvement: 14, event_type: "lesson", datetime:<PHONE_NUMBER>000}
9:  {skill_id: "a15377a46caf42e948441cf0f3777376", improvement: 10, event_type: "practice", datetime:<PHONE_NUMBER>000}
10: {skill_id: "c7fdf4e20d652becf3da33b2cb394f0d", improvement: 12, event_type: "lesson", datetime:<PHONE_NUMBER>000}
11: {skill_id: null, improvement: 18, event_type: "practice", datetime:<PHONE_NUMBER>000}
12: {skill_id: "30417892911333802be5f2daba516e24", improvement: 10, event_type: "practice", datetime:<PHONE_NUMBER>000}
13: {skill_id: "7210bee5a1de77d558c1dc561be73260", improvement: 10, event_type: "practice", datetime:<PHONE_NUMBER>000}

This data is filtered based on the skill_id to make sure that it ignores any skills that are not for the current tree. You can see that there is no way of knowing from this data alone what crown level the skill was at, so all lessons are counted in the prediction method. This means that this method tends to over estimate the progress rate and so puts the date too soon.
If this method is being used, then it could have the effect you describe where doing a lesson that shouldn't contribute towards getting you to the next tree level, changes the predicted date.
The second method, based on the saved progress history should be more accurate, as it will only look at lessons that contribute towards getting to the next tree level, just as you suggest. This method works by saving an entry for each day that any progress is made towards getting to the next level. I.e. it looks at the total number of lessons left on skills that are at the current tree level, and records how much this changes every day. You have seen this record before, but here is a sample of mine:
67: (3) [1604275200000, 0, 468]
68: (3) [1604361600000, 0, 467]
69: (3) [1604880000000, 0, 466]
70: (3) [1605657600000, 0, 465]
71: (3) [1606089600000, 0, 463]
72: (3) [1606521600000, 0, 462]

The first entry is the timestamp of midnight of that day, the second is the tree level at the time, and the last is the number of lessons remaining to go until the next tree level. The 7 most recent entries from this information is used to calculate the average number of lessons done per day that contribute to getting to the next tree level, and that is then used to work out how long it will be until the user gets there.
Also note that the progress graph in the crowns info is just displaying this information but showing the change between entries for each day of the last week. Here only the last two entries in the above are from the last week and are shown in the graph below:

An entry from the current day is only used as part of the prediction algorithm if the user has met their daily goal for today. This is to avoid the date fluctuating while the user is doing their lessons for the day. For example, suppose that the user typically does 3 lessons per day that contribute towards getting to the next tree level. At the start of any given day, after the first lesson has been completed, if today's progress is included in the prediction algorithm, it will stand out compared to the previous days as there has only been one progress making lesson done, and thus push down the average progress rate, making the predicted level up date further into the future. To stop this, the current day's entry is not included until the daily goal is met, at which point it is supposed that it is representative enough to include.
I hope that helps explain what could be going on. Of course there could also be a bug in the saving of the progress entries, but from my end nothing looks out of place.

wow, such a lengthy answer to my humble comment!  What did i do to  merit such detail technical explanation :)
FYI  I observed  change in date prediction after i achieve my daily goal
** Is there a way to check which prediction method is used ?**
I've been working on spanish tree for 2+weeks. So there should be plenty of data for DuoStrength to use
Do you use local midnight  or San Francisco  GMT0 as in leagues ?
To check for space I run as in  https://github.com/ToranSharma/Duo-Strength/issues/117#issuecomment-718763047
and my result is :
There are 1930B/102400B being used in total
There are 692B/8192B being used in a single entry for the progress history
Yes i can see on the graph that none of the lessons recently done contribute to the next tree Level. (normally i have that graph turned off)
However when i focus on the current rate and estimated days till completion - they changed during the day!
Today i only raised strength back to 100% on a number of L2 skills.
Note that rate  & days changed from 9.50 & 31 to 10.42 & 28 days ( which makes NO sense)
Prediction  @ Duome changed  from 15.89 & 18 to 15.66 & 19 days ( which makes sense)
So it's not crowns but lessons completed in a day. IMHO as none of the lessons done during the day count towards next tree Level they should not be used in the prediction.
I guess that means that 1st method of prediction was used ( based on Duome data)
Below are screenshots:  1.at the start and 2.at the end of the day

I am happy to explain the workings of things! It helps me make sure I fully have my head around what I am doing.

FYI I observed change in date prediction after i achieve my daily goal
** Is there a way to check which prediction method is used ?**

Looking at the code, both prediction methods should only update after the daily goal has been reached for the reason mentioned previously.
You can see which prediction algorithm you are using just by running the two different prediction methods:
daysToNextTreeLevel()
daysToNextTreeLevelByCalendar()

Then see which one corresponds to what is being shown in the crowns info. Both functions return an object, with a time (in days), a rate (in lessons/day) and the number of lessons left to complete.
You can also run
progress.length

to see if it is over the needed 5 data points to use the non calendar method. This match the results of the above.

Note that rate & days changed from 9.50 & 31 to 10.42 & 28 days ( which makes NO sense)
Prediction @ Duome changed from 15.89 & 18 to 15.66 & 19 days ( which makes sense)

I will have to see what duome is doing if there are some discrepancies between the calendar method and duome's prediction. In theory they can also do a bit better than the calendar method as they have a record of the crown level of each skill so can work out (to some degree of accuracy) if a lesson contributed to getting to the next tree level or not.

So it's not crowns but lessons completed in a day. IMHO as none of the lessons done during the day count towards next tree Level they should not be used in the prediction.

Yes, the progress based method counts lessons that reduce the total number left to get to the next tree level. It doesn't matter if they happen to be the last lesson of skill that actually earns to crown. All lessons on skills of the correct crown level will contribute towards to prediction.

Do you use local midnight or San Francisco GMT0 as in leagues ?
The timestamps in the progress history list, should be for midnight local time.

To check for space I run as in #117 (comment)
and my result is :
There are 1930B/102400B being used in total
There are 692B/8192B being used in a single entry for the progress history

Should be no issues currently. I still need to address the filling up of data found in #117, I will try to get to it in the next couple of days.

progress.length said 4
I am puzzled. I'll keep an eye on it.

Obviously re-installing your plug-in or changing my user name (?)will reset the progress day counter. I just don't remember doing it...
Other possible causes are
Chrome update
Joining a classroom
Achieving daily goal on a different language course
Achieving daily goal on a different device
Achieving daily goal in  a different browser
Starting with (and or doing only) practice(dumbbells)
Starting with (and or doing only) stories

Now that progress.length says 6 prediction works properly :)


Load balancer health check redirected; not making it to the app

Hi.  Apologies if this is the wrong location for this question.
We are trying to use your gem to create a single exception for a single endpoint in our use of SSL in our app.   We want to allow a port 80 health check inquiry from a load balancer (LB) but we can't seem to configure your gem (or maybe nginx?) correctly to accomplish this.   Rails (nginx?) keeps redirecting the LB's health request with a 301 regardless of our rack-ssl-enforcer configuration.
Before attempting to use your gem, we had our app working fine in the Elastic BeanStalk environment of AWS, with an LB configured to handle SSL termination (and with the default TCP LB healthcheck).   We configured the app for SSL with the "config.force_ssl = true" setting so that the app only had to deal with port 80 traffic, and we didn't modify the default nginx configuration at all.   With this setup, Rails works fine and accepts only port 80 traffic with a special header HTTP_X_FORWARDED_PROTO indicating that the LB has terminated the 443 traffic and routed it on to the app on port 80.   And this works fine for us.
But now, we desire the LB to do a health check on our HTTP /alive endpoint.   But we found that this didn't work, since the health check from the LB (sent on port 80) comes in WITH OUT that special header the LB usually adds to requests from a browser.   Rails sees no head so it does a 301 redirect to HPPTS.  The LB then considers the health check to have failed. :-(
To fix this, we had hoped to use your gem to configure our app to allow our /alive endpoint to be hit without the HTTP_X_FORWARDED_PROTO header.  So, we removed the Rails "config.force_ssl = true" line, and added these two lines of configuration for your gem:

config.middleware.use Rack::SslEnforcer, ignore: lambda { |request| request.env["HTTP_X_FORWARDED_PROTO"].blank? }, strict: true
config.middleware.insert_before  ActionDispatch::Cookies, Rack::SslEnforcer

We expected that this would simply allow non-SSL traffic to hit our /alive endpoint.  But instead, we always see a 301 redirect for the LB health check, and never see the lambda code get called.   We tried applying some of the nginx config settings your README suggests, but did not find them to accomplish anything.
If you could offer us any advice, that would sure be appreciated.   Thank you very much!

Hi Glenn,
if i understand correctly, you want your setup to behave like this:
1. Client ---> http://your.domain.tld ---> LB ---> NginX ---> Rails # redirect to HTTPS
2. Client ---> https://your.domain.tld ---> LB ------> NginX ---> Rails # serve app
3. LB ---> http://your.domain.tld/alive ---> NginX ---> Rails # serve app

LB has set HTTP_X_FORWARDED_PROTO to http
LB has set HTTP_X_FORWARDED_PROTO to https
LB has initiated the request, HTTP_X_FORWARDED_PROTO not set

For your scenario, config.middleware.insert_before ActionDispatch::Cookies, Rack::SslEnforcer, except: %r{^/alive/} should do the trick. HTH, if it does not, please post the output of rake middleware

Yes, Tobias, you understand what we were trying to set up.     Thanks!  Just had to change your regex to %r{^/alive$} (since we are hitting "/alive" not "/alive/").  I also removed the nginx configuration we were trying to use earlier... they weren't needed after all.
Again, thank you very much for your help Tobias, and thanks for a great gem that has really helped us out!

Glad you figured it out. I'm closing here, take care!


Go through existing Thymeleaf test files, try convert some to JUnit tests

I've just added a bunch of JUnit tests for some enhancements and found they're much nicer than some of my existing tests (Thymeleaf test files) in that they're integration tests and thus break whenever something seemingly unrelated changes :confused:
I should have a look through some of those test files, see if I can replace more of them with unit tests.

Am currently simplifying tests as I go.  Still a few disabled, so am waiting to clear those first.


MSID: 93062 Version: 1 DOI: 2<IP_ADDRESS>3877

[PLACE MANUSCRIPT AND EDITOR DETAILS HERE WHEN AVAILABLE] See step 3
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=93062)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/93062/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[ ] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>3877)
[ ] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/93062/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/93062)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/93062

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/93062

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/93062/v1/93062-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/93062)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

(Issues to resolve)

Reviews unavailable and RP doesn't seem to be available on EPP.


Add static ICE endpoints

Added new API endpoint "probing", which returns list of ICE endpoints
so that clients could perfrom RTT measurements.
Example of output:
{
    "ice": {
        "candidates": [
            {
                "ip": "<IP_ADDRESS>",
                "port": 10000,
                "protocol": "udp"
            },
            {
                "ip": "<IP_ADDRESS>",
                "port": 10001,
                "protocol": "udp"
            },
            {
                "ip": "<IP_ADDRESS>",
                "port": 10002,
                "protocol": "udp"
            },
            {
                "ip": "<IP_ADDRESS>",
                "port": 4443,
                "protocol": "tcp"
            }
        ],
        "pwd": "bVDyyTCxoAuB1VQIvnWrUZik",
        "ufrag": "8gAxW5C3GxsJgV"
    }

Each endpoint expects STUN Binding Request with provided
ICE credentials and replies with  "ok" STUN response.
Static ICE credentials are generated on every SMB startup.
RTC-13083

Do we have any unit test that calls on the HTTP API to get the ice-candidates and check that they are somewhat correct.
A unit test could also create a sort of test client, perhaps reuse SfuClient to test the ICE connectivity with the candidates provided. You have to provide a onfig.json that allows opening of <IP_ADDRESS>, but there are tests doing that.

Do we have any unit test that calls on the HTTP API to get the ice-candidates and check that they are somewhat correct. A unit test could also create a sort of test client, perhaps reuse SfuClient to test the ICE connectivity with the candidates provided. You have to provide a onfig.json that allows opening of <IP_ADDRESS>, but there are tests doing that.

I've added an integration test. As discussed it queries API for ICE candidates and invokes connect() on transport to trigger ICE probing, then verifies that best RTT is greater than 0.


BibTeX Entries with Volume and Number Fields

According to BibTeX's documentation the entry types book, inbook, incollection, proceedings and inproceedings can have either the volume field or the number field specified, but not both. I have a Zotero item of type Conference Paper with fields Volume and Issue filled out. This entry is exported by BBT's BibTeX exporter as an inproceedings entry with both fields volume and number. BibTeX outputs the following warning when parsing the exported bibliography:
Warning--can't use both volume and number fields in [citation key]

The resulting BBL file contains only the contents of the volume field (the number field is omitted). This would suggest that BBT's BibTeX exporter should only include the volume field in book, inbook, incollection, proceedings and inproceedings entries when the values of both volume and number are known from Zotero's Volume and Issue fields respectively. Here's a debug-report ID with a relevant Conference Paper entry: A45Y75PT-euc. Please note that BibLaTeX's documentation doesn't seem to indicate that BibLaTeX has this limitation too.

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>89 ("Merge branch 'gh-1476' into gh-1475")
Install in Zotero by downloading test build <IP_ADDRESS>89, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Can you try 6289?

Thanks, the issue is resolved in the test build.

Thanks for the confirmation, merged


Add uc 08 implementing part1

Running the files in the test resources directory gives me:
simtools-production-generate-simulation-config --azimuth 60.0 --elevation 45.0 --nsb 0.3 --ctao_data_level "A" --science_case "high_precision" --file_path tests/resources/production_dl2_fits/prod6_LaPalma-20deg_gamma_cone.N.Am-4LSTs09MSTs_ID0_reduced.fits --file_type cone --metrics_file tests/resources/production_simulation_config_metrics.yaml --site North
INFO::calculate_statistical_errors_grid_point(l132)::load_data_from_file::Unique azimuths: [0.] deg
INFO::calculate_statistical_errors_grid_point(l133)::load_data_from_file::Unique zeniths: [70.] deg
INFO::calculate_statistical_errors_grid_point(l136)::load_data_from_file::Setting initial grid point with azimuth: 0.0 deg zenith: 70.0 deg
INFO::calculate_statistical_errors_grid_point(l379)::calculate_metrics::Effective Area Error (max in validity range): 0.999999, Reference: 0.020
INFO::calculate_statistical_errors_grid_point(l324)::calculate_error_energy_estimate_bdt_reg_tree::Calculating Energy Resolution Error
INFO::calculate_statistical_errors_grid_point(l392)::calculate_metrics::Energy Estimate Error: 0.184, Reference: 0.050
INFO::production_generate_simulation_config(l149)::main::Simulation configuration: {'core_scatter_area': np.float64(200070.0), 'viewcone': np.float64(1053.0), 'number_of_events': '27499935690566.387 ct'}
INFO::production_generate_simulation_config(l152)::main::Simulation configuration saved to: /Users/maierg/DESYCloud/CTA/Pipelines/MC-Pipeline/gammasim-tools/simtools/simtools-output/production_generate_simulation_config/configured_simulation_params.json

What is a viewcone of 1053? I assume that is not in degrees.
Fur a future implementation, we need to discuss how we want to do the rounding for the number of events to be simulated. We of course can simulate ''27499935690566" events, but my preference would be e.g., round this to 275..
The output says Unique zeniths: [70.] deg. Are we sure that this is not a mixup of zenith and elevation?

Running the files in the test resources directory gives me:
simtools-production-generate-simulation-config --azimuth 60.0 --elevation 45.0 --nsb 0.3 --ctao_data_level "A" --science_case "high_precision" --file_path tests/resources/production_dl2_fits/prod6_LaPalma-20deg_gamma_cone.N.Am-4LSTs09MSTs_ID0_reduced.fits --file_type cone --metrics_file tests/resources/production_simulation_config_metrics.yaml --site North
INFO::calculate_statistical_errors_grid_point(l132)::load_data_from_file::Unique azimuths: [0.] deg
INFO::calculate_statistical_errors_grid_point(l133)::load_data_from_file::Unique zeniths: [70.] deg
INFO::calculate_statistical_errors_grid_point(l136)::load_data_from_file::Setting initial grid point with azimuth: 0.0 deg zenith: 70.0 deg
INFO::calculate_statistical_errors_grid_point(l379)::calculate_metrics::Effective Area Error (max in validity range): 0.999999, Reference: 0.020
INFO::calculate_statistical_errors_grid_point(l324)::calculate_error_energy_estimate_bdt_reg_tree::Calculating Energy Resolution Error
INFO::calculate_statistical_errors_grid_point(l392)::calculate_metrics::Energy Estimate Error: 0.184, Reference: 0.050
INFO::production_generate_simulation_config(l149)::main::Simulation configuration: {'core_scatter_area': np.float64(200070.0), 'viewcone': np.float64(1053.0), 'number_of_events': '27499935690566.387 ct'}
INFO::production_generate_simulation_config(l152)::main::Simulation configuration saved to: /Users/maierg/DESYCloud/CTA/Pipelines/MC-Pipeline/gammasim-tools/simtools/simtools-output/production_generate_simulation_config/configured_simulation_params.json

What is a viewcone of 1053? I assume that is not in degrees.
Fur a future implementation, we need to discuss how we want to do the rounding for the number of events to be simulated. We of course can simulate ''27499935690566" events, but my preference would be e.g., round this to 275..
The output says Unique zeniths: [70.] deg. Are we sure that this is not a mixup of zenith and elevation?

Thanks for the review @GernotMaier. Yes rounding would not be an issue. Should also think about if we should do a refit with a power-law function to the scaled events, as there is probably no possibility to do a simulation without a power-law.

@GernotMaier thanks again for the review. Fixed the remaining points and it should be ready to merge now. Let me know if there is anything missing.

All good, thanks! Please merge.


SpellCheck broken on Samsung devices (S8)

Is this a bug report?
yes

Have you read the Contributing Guidelines?
yes
Environment

react-native -v: 0.46.4
node -v: v6.9.5
npm -v: 3.10.10
yarn --version: 0.21.3

Then, specify:

Target Platform: Android (Samsung)

Development Operating System: MacOS

Build tools: using create-react-native-app and Expo

Steps to Reproduce

(Write your steps here:)

Use Samsung S8 with latest firmware (should be reproducible S6 and above)
Enable Spell Checker in the phone menu
Create controlled <TextInput value={this.state.val} onChangeText={this.onChange} editable={true} spellCheck={true} />
Run the app and input some obviously wrong spelled text, (e.g. aiefsjaliesfj or adsjfaleifjlaisef :))

Expected Behavior

I would expect the text input to underline the invalid text with red line, allowing me to click it and select from close correctly spelled candidates.
Actual Behavior

The red line just flashes and then disappears, breaking the system spell check feature.
Reproducible Demo

https://snack.expo.io/B1-6Lw_uW
Fire this up and insert some text.

The red line just flashes and then disappears, breaking the system spell check feature.

spell check is ios only.

Well even though the prop might not be supported, TextInput still breaks the native functionality.


Remove .editorconfig

Presense of this file force me to use TAB to indent JSON files.

Sorry but do you still indent manually? Just put these in your vscode settings
{
  "editor.defaultFormatter": "denoland.vscode-deno",
  "editor.formatOnSave": true,
}

And you can indent however you want and it will be fixed when you save the file.
And if you don't use vscode, I'm sure there are similar features available in the IDE of your choice.
Please stop manually doing formatting, leave it to tools, it will save you a lot of time.

I'm sorry but that's not point. This invalid .editorconfig (I'm saying this as invalid because the setting is for any filetypes) might overwrite settings (and does in my environment.)

Please stop manually doing formatting, leave it to tools, it will save you a lot of time.

Agreed but invalid configuration file break toolset.

I think this was originally committed for formatting of makefiles -- maybe instead of deleting we could limit it to only makefiles?


Error when running

On Debian with python3, running using command:
/usr/local/bin/wal-e
with or without any params:
/usr/bin/envdir /etc/wal-e.d/env /usr/local/bin/wal-e backup-push /storage/postgresql/data
I'm getting this error:
Traceback (most recent call last):
  File "/usr/local/bin/wal-e", line 7, in <module>
    from wal_e.cmd import main
  File "/usr/local/lib/python3.4/dist-packages/wal_e/cmd.py", line 528
    print pkgutil.get_data('wal_e', 'VERSION').strip()

Any ideas?

This looks like a Python2/v0.9.0 or before version of WAL-E combined with a new python.
The equivalent source code in 1.0 looks like:
    if subcommand == 'version':
        import pkgutil

        print(pkgutil.get_data('wal_e', 'VERSION').decode('ascii').strip())
        sys.exit(0)

You can cooroborate this finding by looking at the VERSION file directly.
How did you install wal-e? You may need to add the --pre flag to your pip invocation.

Thanks for the info. Yeah, I installed it through pip I'll check out the VERSION file as suggested  and let you know what I find. If I need to,  I'll try and reinstall with the --pre flag see if that fixes it also.

The version was 0.9.2.
I ran pip install wal-e --pre --upgrade but now am getting this error:
wal_e.main   INFO     MSG: starting WAL-E
        DETAIL: The subcommand is "backup-push".
        STRUCTURED: time=2016-08-26T00:45:54.295177-00 pid=20140
wal_e.main   CRITICAL MSG: An unprocessed exception has avoided all error handling
        DETAIL: Traceback (most recent call last):
          File "/usr/local/lib/python3.4/dist-packages/wal_e/cmd.py", line 565, in main
            backup_cxt = configure_backup_cxt(args)
          File "/usr/local/lib/python3.4/dist-packages/wal_e/cmd.py", line 466, in configure_backup_cxt
            creds = s3_explicit_creds(args)
          File "/usr/local/lib/python3.4/dist-packages/wal_e/cmd.py", line 401, in s3_explicit_creds
            from wal_e.blobstore import s3
          File "/usr/local/lib/python3.4/dist-packages/wal_e/blobstore/s3/__init__.py", line 10, in <module>
            from wal_e.blobstore.s3.s3_credentials import Credentials
          File "/usr/local/lib/python3.4/dist-packages/wal_e/blobstore/s3/s3_credentials.py", line 1, in <module>
            from boto import provider
        ImportError: cannot import name 'provider'

It seems some things were either incompatible or not installed correctly.
I ran these series of commands to get everything back up and running:
$ sudo pip freeze > installed.txt

$ sudo pip uninstall -y -r installed.txt

$ rm -rm ~/.cached/pip

$ sudo pip install wal-e --pre --no-cache

$ sudo pip install boto --no-cache

And now everything works!
Thanks for the help.

I was going to ask what version of boto was involved, with regard to the
import error, but I'm glad things worked out.
On Fri, Aug 26, 2016 at 11:01 AM Craig Holden<EMAIL_ADDRESS>wrote:

It seems some things were either incompatible or not installed correctly.
I ran these series of commands to get everything back up and running:
$ sudo pip freeze > installed.txt
$ sudo pip uninstall -y -r installed.txt
$ rm -rm ~/.cached/pip
$ sudo pip install wal-e --pre --no-cache
$ sudo pip install boto --no-cache
And now everything works!
Thanks for the help.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/wal-e/wal-e/issues/274#issuecomment-242759892, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcFxtNmCWl2m7xUueMZZrzKjuZTHgrks5qjv-ZgaJpZM4JtlrT
.


⚠ Bofrost.de has degraded performance

In 29d4226, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1125 ms

Resolved: Bofrost.de performance has improved in 0db1af3 after 15 minutes.


[BUG] Problems with ionic/angular routing where current and next page have Cupertino-pane

Describe the bug
A clear and concise description of what the bug is.
When using the <ionic-router-outlet> cupertino pane does not render on the page being routed to
Error occurs: Cupertino Pane: specified selector or DOM element already in use
To Reproduce
Steps to reproduce the behavior:
app.component.html
<ion-app>
  <ion-router-outlet></ion-router-outlet>
</ion-app>

page.page.html
<ion-content>

          Page

           Other Page

    Test

</ion-content>

otherPage.page.html
<ion-content>

          Page

           Other Page

    Test

</ion-content>

page.page.ts and otherPage.page.ts
...
public myPane: any;

ngOnInit() {
    this.myPane = new CupertinoPane(
      ".cupertino-pane", // Pane container selector
      {
        initialBreak: "top",
        breaks: {
          top: { enabled: true, height: screen.height * 0.65 },
          middle: { enabled: true, height: screen.height * 0.53 },
          bottom: { enabled: true, height: 35 },
        },
        buttonClose: false,
        inverse: true,
        onTransitionStart: () => {
          if (this.myPane.currentBreak() == "top") {
            this.menuShown = true;
          }
        },
      }
    );
    this.myPane.present({ animate: true });
  }
...

Expected behavior
A clear and concise description of what you expected to happen.
Able to navigate between the two pages with both having the cupertino-pane properly show.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: iOS 10.15.5
Browser: Chrome
Version: 87.0.4280.67

Additional context
Add any other context about the problem here.
As it is shown in the video above, the cupertino pane stays properly loaded wherever it is initialized first. Returning to that page will have a proper cupertino-pane

Nevermind. Realized that both my panes had the same name and that's why they were not working.


530 sprint 80 81 push to production

Copied over all files that are listed in #530 from docs-staging (today's snapshop) to production.
Many files already copied over by Ed.
This pull request contains the ones that were not, plus some last minute edits that were needed.

Connected to issue: https://github.ibm.com/Watson-IoT/Docs/issues/530


[RFE] Optionally include the file name when searching for contexts

Currently:
❯ find .kube/configs -type f
.kube/configs/ha-edge-385.yaml
.kube/configs/vm-k3s-only.yaml

❯ cat .kube/switch-config.yaml
kind: SwitchConfig
version: v1alpha1
kubeconfigStores:
- kind: filesystem
  kubeconfigName: "*.yaml"
  paths:
  - /Users/eminguez/.kube/configs/
  - /Users/eminguez/.kube/config

❯ switch list-contexts
configs/default
configs/default

Ideally:
❯ switch list-contexts
configs/default (ha-edge-385.yaml)
configs/default (vm-k3s-only.yaml)

Hi, thanks for the issue. That's a valid point. I always uniquely name my directories or have unique context names if multiple kubeconfigs are in the same directory. That could be a workaround.
I currently don't have the time to work on this project, so I'd suggest using the above approach for now.


Fix invalid data check in query/mutation fn

Changes
Closes #1973
How to Review

Checklist

[ ] Unit tests updated
[ ] docs/ updated (if necessary)
[ ] pnpm run update:examples run (only applicable for openapi-typescript)

After working on tests it got me thinking - should we even check if data is undefined?
Perhaps just an if(error) check would be sufficient?
Because the problem is

if we throw when data is undefined, we just throw undefined as error(cause error is undefined too)
react query already handles returning undefined as an error and will throw accordingly - perhaps it should just remain their responsibility

I do not exactly remember why we checked for that data in the first place. But maybe yes we could just remove this check as we need to handle responses with no content anyway (see https://github.com/openapi-ts/openapi-typescript/issues/1973#issuecomment-2445815605).


Extra whitespace in string format

https://github.com/sormuras/junit-platform-maven-plugin/blob/be28792abb6ba9d6489713c407a58389c96da2d4/src/main/java/de/sormuras/junit/platform/maven/plugin/MavenDriver.java#L315
Results in this edge case failure:

Caused by: java.util.FormatFlagsConversionMismatchException: Conversion = s, Flags =
at java.util.Formatter$FormatSpecifier.failMismatch (Formatter.java:4422)
at java.util.Formatter$FormatSpecifier.checkBadFlags (Formatter.java:3151)
at java.util.Formatter$FormatSpecifier.checkGeneral (Formatter.java:3109)
at java.util.Formatter$FormatSpecifier. (Formatter.java:2870)
at java.util.Formatter.parse (Formatter.java:2713)
at java.util.Formatter.format (Formatter.java:2655)
at java.util.Formatter.format (Formatter.java:2609)
at java.lang.String.format (String.java:2897)
at de.sormuras.junit.platform.maven.plugin.MavenDriver.lambda$copyDirectoryStructure$1 (MavenDriver.java:315)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept (ForEachOps.java:183)
at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:195)
at java.util.Iterator.forEachRemaining (Iterator.java:133)
at java.util.Spliterators$IteratorSpliterator.forEachRemaining (Spliterators.java:1801)
at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:484)
at java.util.stream.AbstractPipeline.wrapAndCopyInto (AbstractPipeline.java:474)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential (ForEachOps.java:150)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential (ForEachOps.java:173)
at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.forEach (ReferencePipeline.java:497)
at de.sormuras.junit.platform.maven.plugin.MavenDriver.copyDirectoryStructure (MavenDriver.java:303)
at de.sormuras.junit.platform.maven.plugin.MavenDriver.buildPathMap (MavenDriver.java:138)
at de.sormuras.junit.platform.maven.plugin.JUnitPlatformMojo.execute (JUnitPlatformMojo.java:384

The sequence causing the exception was sequentially running mvn test twice, without a clean, [...]

That should not make the build fail per-se.

[...] with a configuration using the same source directory for a jdk8 build and jdk11 build (that just adds a module-info).

An interesting setup. Producing a multi-release JAR?

Not sure if that should be supported anyway,

Would need to see the configuration/setup you're using. Care to provide a minimal example as an integration test in src/it?

[...] so I'm just going to add a clean between runs to avoid it.

Glad, a workaround exists.

[...] with a configuration using the same source directory for a jdk8 build and jdk11 build (that just adds a module-info).

An interesting setup. Producing a multi-release JAR?

No... for Reasons™, I don't want to mix JDK8 and JDK9+ releases in the same JAR.  I have two (Maven) modules, one the full regular JDK8-compatible project, and a second (Maven) module containing exactly 3 files:

/src/main/java/module-info.java
/src/test/java/module-info.test
pom.xml

The POM uses build-helper-maven-plugin to add source directories pointing to the other module's source tree, effectively merging them.
I'd been experiencing what I thought were random failures of this plugin (that a clean always fixed) until a change in one of my CI setups made it 100% reproducible... but then hit this little typo which hides the debug information I need to figure out more. :grin:

Would need to see the configuration/setup you're using.

Linked above.

Care to provide a minimal example as an integration test in src/it?

I needed this fix in for the next step of debugging to figure out what's even going on.  Is the fix for this issue in a snapshot build I can use?

Is the fix for this issue in a snapshot build I can use?

Yes. See https://github.com/sormuras/junit-platform-maven-plugin#access-snapshot-version-via-jitpack for details.
Find the associated build log here: https://jitpack.io/com/github/sormuras/junit-platform-maven-plugin/master-SNAPSHOT/build.log

Thanks. Bug located and new issue created. :)


chore: improve coverage to 100%

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Have steps be clickable/collapsible to be able to go back to them

We decided to start the web app from scratch after the major design/architecture decisions and changes we made. No longer relevant.


[Improvement-11293][dolphinscheduler-api] remove some variables that redundant in subclasses of AbstractAuthenticator

Purpose of the pull request
remove some variables that redundant in subclasses of AbstractAuthenticator
Brief change log
remove some variables that redundant in subclasses of AbstractAuthenticator
Verify this pull request
This pull request is code cleanup without any test coverage.
this close #11293

There are so many commits, please rebase from upstream dev when you submit PR next time.

@davidzollo Please optimize the commits title and log next time merging a PR

@ruanwenjun Thanks for reminding


Access to children

Hi,
First of all, great library!
I have a question about the following use case. I want to set some props for the children depending on both children. For example, if i transition from component A to component B, i want to give both children a certain value, while i want to give another value if the transition is from component A to C. Is this possible?
Thanks!

I see, the behavior you described is quire rare, I am not sure if PageTransition can support it as it is very depends on the details implementation of transition animation and how you want the layout to be used across the app. I can only advice if you have the specific idea of what you want to achieve.

If you just only want an API to access to children, let me know what should it looks like, and specifically define a useful use case of it, I am willing to implement / review PR!

Close due to inactive.


How to properly tackle with has_one polymorphic associations?

Hi, guys! I have a question: how to properly tackle with has_one associations? I’ll show the example with which I stuck.
For example, I have models Post and Image:
class Post < ActiveRecord::Base
	has_one :cover, class_name: 'Image', as: :imagable
end

class Image < ActiveRecord::Base
	belongs_to :imagable, polymorphic: true
end

And I have form object to create/update some post:
class PostForm < Reform::Form
	property :cover, skip_if: :skip_cover_process!, populator: :populate_cover! do
		# Image is processed by another API endpoint and there only id is passed
		property :id
		property :_destroy, virtual: true
	end

	def skip_cover_process!(fragment:, **)
		if fragment['_destroy'] == 'true'
			# ???
		end
	end

	def populate_cover!(fragment:, model:, **)
                #…
	end
end

So how to properly break the association? The only one solution which I found and it works for me is:
def skip_cover_process!(fragment:, **)
    if fragment['_destroy'] == 'true'
        image_id = self.cover.id
        image = ::Image.find(image_id)
        image.update_attributes imagable_id: nil, imagable_type: nil
        return true
    end
end

I use reform 2.1.0.
Thanks.

If you want all those features (create/retrieve and delete) you currently have to write your own populator, you don't need :skip_if, you can do that in the populator, too, using skip!. http://trailblazer.to/gems/reform/populator.html#delete

@apotonick thanks for the response!
But what I must do in the populator?
Regarding to the example which you propose by link, in the case of has_many association I do that:

@apotonick thanks for the response!
But what I must do in the populator?
Regarding to the example which you propose by link, in the case of has_many association I do that:

@apotonick thanks for the response!
But what I must do in the populator?
Regarding to the example which you propose by link, in the case of has_many association I do that:
songs.delete(item)

And by this code I break association.
But in the case of has_one association what I must do?

I mean that just call skip! does not break association, is it?

If you have queries on how to use Reform, please read the docs on the trailblazer site, read the (book)[https://leanpub.com/trailblazer], or post your question on the (Trailblazer gitter room)[https://gitter.im/trailblazer/chat].
Github issues are now restricted to bug reports and fixes.
We look forward to seeing you on Gitter!


Encoding issues with .so files produced by Cython

Describe the bug
I have .pyx source files which contain some doctests. When I cythonize them, I obtain some .so files. These .so files are picked up by pytest because they contain some doctests. When I run coverage run -m pytest I get the following error: SyntaxError: invalid or missing encoding declaration.
To Reproduce
How can we reproduce the problem?  Please be specific.

What version of Python are you using? I'm using Python 3.7.6.
What version of coverage.py are you using? The output of coverage debug sys is helpful.

version: 4.5.4
             coverage: /Users/mhalford/opt/anaconda3/envs/creme/lib/python3.7/site-packages/coverage/__init__.py
          cover_paths: /Users/mhalford/opt/anaconda3/envs/creme/lib/python3.7/site-packages/coverage
          pylib_paths: /Users/mhalford/opt/anaconda3/envs/creme/lib/python3.7
               tracer: CTracer
 plugins.file_tracers: Cython.Coverage.Plugin
  plugins.configurers: -none-
         config_files: .coveragerc
         configs_read: .coveragerc
            data_path: /Users/mhalford/projects/creme-ml/creme/.coverage
               python: 3.7.6 (default, Jan  8 2020, 13:42:34) [Clang 4.0.1 (tags/RELEASE_401/final)]
             platform: Darwin-19.2.0-x86_64-i386-64bit
       implementation: CPython
           executable: /Users/mhalford/opt/anaconda3/envs/creme/bin/python
                  cwd: /Users/mhalford/projects/creme-ml/creme
                 path:
                       /Users/mhalford/opt/anaconda3/envs/creme/lib/python37.zip
                       /Users/mhalford/opt/anaconda3/envs/creme/lib/python3.7
                       /Users/mhalford/opt/anaconda3/envs/creme/lib/python3.7/lib-dynload
                       /Users/mhalford/opt/anaconda3/envs/creme/lib/python3.7/site-packages
                       /Users/mhalford/projects/creme-ml/creme
          environment: -none-
         command_line: /Users/mhalford/opt/anaconda3/envs/creme/bin/coverage debug sys
         source_match: -none-
    source_pkgs_match: -none-
        include_match: -none-
           omit_match: *__init__.py
                       *.so
          cover_match: /Users/mhalford/opt/anaconda3/envs/creme/lib/python3.7/site-packages/coverage
          pylib_match: /Users/mhalford/opt/anaconda3/envs/creme/lib/python3.7

What versions of what packages do you have installed? The output of pip freeze is helpful.

alabaster==0.7.12
appnope==0.1.0
argh==0.26.2
astroid==2.3.3
attrs==19.3.0
Babel==2.8.0
backcall==0.1.0
beautifulsoup4==4.8.2
bleach==3.1.0
certifi==2019.11.28
chardet==3.0.4
coverage==4.5.4
-e git+https://github.com/creme-ml/creme.git@15f211de5f9bd8b47258832f65e3e84a93daba58#egg=creme
css-html-js-minify==2.5.5
cycler==0.10.0
Cython==0.29.14
decorator==4.4.1
defusedxml==0.6.0
doc8==0.8.0
docutils==0.16
entrypoints==0.3
flit==2.2.0
flit-core==2.2.0
graphviz==0.13.2
idna==2.8
imagesize==1.2.0
importlib-metadata==1.5.0
ipykernel==5.1.4
ipython==7.12.0
ipython-genutils==0.2.0
ipywidgets==7.5.1
isort==4.3.21
jedi==0.16.0
Jinja2==2.11.1
joblib==0.14.1
json5==0.9.1
jsonschema==3.2.0
jupyter==1.0.0
jupyter-client==5.3.4
jupyter-console==6.1.0
jupyter-core==4.6.1
jupyterlab==1.2.6
jupyterlab-server==1.0.6
kiwisolver==1.1.0
lazy-object-proxy==1.4.3
livereload==2.6.1
lxml==4.5.0
m2r==0.2.1
MarkupSafe==1.1.1
matplotlib==3.1.3
mccabe==0.6.1
mistune==0.8.4
more-itertools==8.2.0
nbconvert==5.6.1
nbformat==5.0.4
nbsphinx==0.5.1
nbval==0.9.4
notebook==6.0.3
numpy==1.18.1
packaging==20.1
pandocfilters==1.4.2
parso==0.6.1
pathtools==0.1.2
pbr==5.4.4
pexpect==4.8.0
pickleshare==0.7.5
pluggy==0.13.1
port-for==0.3.1
prometheus-client==0.7.1
prompt-toolkit==3.0.3
ptyprocess==0.6.0
py==1.8.1
Pygments==2.5.2
pylint==2.4.4
pyobjc-core==6.1
pyobjc-framework-Cocoa==6.1
pyobjc-framework-FSEvents==6.1
pyparsing==2.4.6
pyrsistent==0.15.7
pytest==5.3.5
pytest-cov==2.8.1
pytest-cython==0.1.0
python-dateutil==2.8.1
python-slugify==4.0.0
pytoml==0.1.21
pytz==2019.3
PyYAML==5.3
pyzmq==18.1.1
qtconsole==4.6.0
requests==2.22.0
restructuredtext-lint==1.3.0
scikit-learn==0.22.1
scipy==1.4.1
Send2Trash==1.5.0
six==1.14.0
snowballstemmer==2.0.0
soupsieve==1.9.5
Sphinx==2.3.1
sphinx-autobuild==0.7.1
sphinx-copybutton==0.2.8
sphinx-material==0.0.23
sphinxcontrib-applehelp==1.0.1
sphinxcontrib-devhelp==1.0.1
sphinxcontrib-htmlhelp==1.0.2
sphinxcontrib-jsmath==1.0.1
sphinxcontrib-qthelp==1.0.2
sphinxcontrib-serializinghtml==1.1.3
stevedore==1.31.0
terminado==0.8.3
testpath==0.4.4
text-unidecode==1.3
torch==1.4.0
tornado==6.0.3
traitlets==4.3.3
Unidecode==1.1.1
urllib3==1.25.8
watchdog==0.10.1
wcwidth==0.1.8
webencodings==0.5.1
widgetsnbextension==3.5.1
wrapt==1.11.2
zipp==2.1.0

What code are you running?  Give us a specific commit of a specific repo that we can check out.

You can download the master branch of creme to check out the error for yourself. The make cython command builds the Cython code.
>>> git clone https://creme-ml.github.io/
>>> cd creme
>>> make cython

What commands did you run?

>>> coverage run -m pytest creme/optim
>>> coverage report

Expected behavior
I'd expect no encoding issue to arise.
Additional context
I've tried setting the language-level of Cython to 3 instead of 2 (the default) to no avail.
PS: by the way, great work on this library, I love it.

Hey @MaxHalford, it'd be helpful if you could post the output of your commands where it's visible how it fails. Even a traceback which I suspect you're seeing too. This may be a bug in Cython.Coverage.Plugin which would mean that you'd have to report it on their tracker.


HOP-2119 Rename ActionCopy to ActionMeta

I just renamed things

there is a conflict in engine/src/main/java/org/apache/hop/workflow/WorkflowPainter.java

Ah, damn now I messed it up