Populating a ScrollArea without having to add all items

Based on a question at https://github.com/emilk/egui/discussions/449
Showing a ScrollArea containing thousands of widgets can be slow. If each widget takes up the same amount of vertical space there is a possible shortcut where we only show the widgets that are actually visible (or partly visible).
We needs to figure out a good design for this. The major part that is missing is communicating from the ScrollArea to the inner ui what region is visible. Perhaps ScrollArea::show(|ui| …) should have a sibling ScrollArea::show(|ui, y_range| …).
(As usual, Dear ImGui does this right)

If ScrollArea is able to scroll in both directions (either now or in the future), maybe it may be better to pass range instead of y_range?

I got a proof-of-concept working:
    let text_style = TextStyle::Body;
    let row_height = ui.fonts()[text_style].row_height();
    let num_rows = 10_000;
    ScrollArea::auto_sized().show_rows(ui, row_height, num_rows, |ui, row_range| {
        for row in row_range {
            let text = format!("Row {}/{}", row + 1, num_rows);
            ui.label(text);
        }
    });

In this branch: https://github.com/emilk/egui/compare/master...scroll-rows

Nice. Thank you! Can I use this branch assuming the pub fn show_viewport (or similar) will be merged into main?


ValueError when a single parameter is supplied to GASearchCV

System information
OS Platform and Distribution: Windows 10
Sklearn-genetic-opt  version: 0.6.0
Scikit-learn version: 0.24.1
Python version: 3.8
Describe the bug
GASearchCV raises a ValueError : empty range for randrange() (1, 1, 0) after generation 0 when only one parameter is supplied to the argument param_grid. I am not 100% sure if this is a true bug or if this is an expected behaviour of the genetic algorithm; nonetheless, I have decided to raise this issue because the error is not very clear about what is happening (in my opinion).
To Reproduce
Below, I am showing two examples of this error when using a SVR and RandomForestClassifier with a single parameter for optimization. I have tested other algorithms and I have got the same error.
import numpy as np
from sklearn.svm import SVR
from sklearn.model_selection import GridSearchCV, KFold
from sklearn_genetic import GASearchCV
from sklearn_genetic.space import Continuous, Categorical, Integer
from sklearn.ensemble import RandomForestClassifier

#generate input to test SVR for regression and random forest for classification
X = np.random.normal(75, 10, (1000, 2))
y = np.random.normal(200, 20, 1000)
y_labels = np.random.randint(0, 2, size=1000)
cv = KFold(n_splits=5, random_state=42, shuffle=True)

This is the example for SVR:
params_svr = {"degree": Integer(2,3)}

evolved = GASearchCV(estimator=SVR(),
                     cv=cv,
                     population_size=10,
                     generations=40,
                     tournament_size=5,
                     elitism=True,
                     crossover_probability=0.85,
                     mutation_probability=0.1,
                     param_grid=params_svr,
                     criteria='max',
                     scoring="neg_mean_absolute_error",
                     algorithm='eaMuPlusLambda',
                     error_score="raise",
                     n_jobs=-1,
                     verbose=True,
                     keep_top_k=10)

evolved.fit(X, y)

This is the example for RandomForestClassifier:
params_rfc = {"max_depth": Integer(2,6)}

evolved = GASearchCV(estimator=RandomForestClassifier(),
                     cv=cv,
                     population_size=10,
                     generations=40,
                     tournament_size=5,
                     elitism=True,
                     crossover_probability=0.85,
                     mutation_probability=0.1,
                     param_grid=params_rfc,
                     criteria='max',
                     scoring="f1",
                     algorithm='eaMuPlusLambda',
                     error_score="raise",
                     n_jobs=-1,
                     verbose=True,
                     keep_top_k=10)

evolved.fit(X, y_labels)

Expected behavior
If I add an extra parameter to params_svr and params_rfc:
params_svr = {"degree": Integer(2,3), "C": Continuous(0, 1)}
params_rfc = {"max_depth": Integer(2,6), "criterion": Categorical(["gini", "entropy"])}

The algorithm runs as usual.
Screenshots
Please find below the full log of this error.
Traceback (most recent call last):

  File "<ipython-input-15-82a4ae8a09ac>", line 17, in <module>
    evolved.fit(X, y_labels)

  File "C:\Users\andre\Anaconda3\lib\site-packages\sklearn\utils\metaestimators.py", line 120, in <lambda>
    out = lambda *args, **kwargs: self.fn(obj, *args, **kwargs)

  File "C:\Users\andre\Anaconda3\lib\site-packages\sklearn_genetic\genetic_search.py", line 455, in fit
    pop, log, n_gen = self._select_algorithm(

  File "C:\Users\andre\Anaconda3\lib\site-packages\sklearn_genetic\genetic_search.py", line 547, in _select_algorithm
    pop, log, gen = eaMuPlusLambda(

  File "C:\Users\andre\Anaconda3\lib\site-packages\sklearn_genetic\algorithms.py", line 305, in eaMuPlusLambda
    offspring = varOr(population, toolbox, lambda_, cxpb, mutpb)

  File "C:\Users\andre\Anaconda3\lib\site-packages\deap\algorithms.py", line 234, in varOr
    ind1, ind2 = toolbox.mate(ind1, ind2)

  File "C:\Users\andre\Anaconda3\lib\site-packages\deap\tools\crossover.py", line 51, in cxTwoPoint
    cxpoint2 = random.randint(1, size - 1)

  File "C:\Users\andre\Anaconda3\lib\random.py", line 248, in randint
    return self.randrange(a, b+1)

  File "C:\Users\andre\Anaconda3\lib\random.py", line 226, in randrange
    raise ValueError("empty range for randrange() (%d, %d, %d)" % (istart, istop, width))

ValueError: empty range for randrange() (1, 1, 0)

Hi, thanks.
This is somehow the expected behavior, the way the new candidates are created in generation 1, is by using a crossover operation, which is a DEAPtools.cxTwoPoint, this function needs to sample 2 random points from each individuals parameter, as it has length 1, it can't be done.
To fix this, I'll introduce the tools.cxSimulatedBinaryBounded which can handle 1 parameter, but it won't probably be able to make a real optimization and get stuck in one single random value, so at the same time, a warning will be raised indicating that at least 2 parameters are advised to actually make an optimization, but an error won't be longer be raised.

Thank you very much for the explanation.


Mobile Issue | spinner does not showing

vue-autosuggest version: 1.8.3
node version: v8.11.2
npm (or yarn) version: 5.6.0

What you did:
Implemented auto suggest in my project. working flawlessly except mobile.
What happened:
Spinner not showing after typing
Problem description:
Does not show the spinning after a user typed something unless he taps out of the field.
Suggested solution:
not sure

@ahsansalaldaha there is no "spinner" bundled with vue-autosuggest so not sure what you mean. Can you please create a codesandbox to reproduce your issue?
You can fork this one: https://codesandbox.io/s/627qlx66oz

Not sure about the spinner (I guess some custom UI), but I can confirm that on-input-change does not fire on Chrome Android 73 while the input has focus. Only when the input loses focus on-input-change triggers. It works on Firefox Android though.
E.g. I use on-input-change to fetch search results from the backend while the user types. On Chrome Android the suggestions will only update after I click elsewhere on the page (then the event fires) and then focus the input again (the suggestions are shown).
You can test it with the official  demo

Some more insights: This is caused by https://github.com/vuejs/vue/issues/9777#issuecomment-478831263
On mobile phones the keyboard is in composing mode while typing a word, which prevents v-model to fire.
If we want to get notified after each keystroke we'd have to use <input v-on:input="e => searchInput e.target.value" :value="searhcInput" />.
Not 100% sure as I don't have any experience with languages that use composition but I assume eager updating would be generally the desired behavior for an autosuggest widget.

Thank you so much Rupert for the kind information.
On Wed, 24 Apr 2019, 3:58 pm Rupert Angermeier<EMAIL_ADDRESS>wrote:

Some more insights: This is caused by vuejs/vue#9777 (comment)
https://github.com/vuejs/vue/issues/9777#issuecomment-478831263
On mobile phones the keyboard is in composing mode while typing a word,
which prevents v-model to fire.
If we want to get notified after each keystroke we'd have to use .
Not 100% sure as I don't have any experience with languages that use
composition but I assume eager updating would be generally the desired
behavior for an autosuggest widget.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/darrenjennings/vue-autosuggest/issues/106#issuecomment-486175084,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACBRNME3KLHDGA6KRZF56N3PSA4L3ANCNFSM4HHW43AA
.

This seems like a duplicate of https://github.com/darrenjennings/vue-autosuggest/issues/70. Please try beta version (which is very stable, just working on some more things before I release as 2.0 officially):
npm install<EMAIL_ADDRESS>
this version removes internal v-model in favor of @input and :value as @rangermeier points out. Hopefully this helps:
https://codesandbox.io/s/2vr87nyvkp


Error copier fails trying to build for Odoo v8: Err https://deb.nodesource.com jessie/main Sources

Describe the bug
If I try invoke img-build or invoke img-build --pull
To Reproduce
Affected versions:
Odoo v8
Steps to reproduce the behavior:
run invoke img-build or invoke img-build --pull
The process stops with the present error:
Err https://deb.nodesource.com jessie/main Sources
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Err https://deb.nodesource.com jessie/main amd64 Packages
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
W: Failed to fetch https://deb.nodesource.com/node_6.x/dists/jessie/main/source/Sources  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
W: Failed to fetch https://deb.nodesource.com/node_6.x/dists/jessie/main/binary-amd64/Packages  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
E: Some index files failed to download. They have been ignored, or old ones used instead.
Fetched 11.8 MB in 3s (3215 kB/s)
Traceback (most recent call last):
File "/opt/odoo/common/build", line 30, in
subprocess.check_call(command)
File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '/opt/odoo/custom/build.d/20-update-pg-repos' returned non-zero exit status 100
ERROR: Service 'odoo' failed to build: The command '/bin/sh -c /opt/odoo/common/build && sync' returned a non-zero code: 1
Expected behavior A clear and concise description of what you expected to happen.
We expect the process as no problem with certificate issue
Additional context Add any other context about the problem here. (e.g. OS, Docker
version, ...)
Docker version 20.10.7, build 20.10.7-0ubuntu1~20.04.1
Invoke 1.5.0
Copier _commit: v2.8.0

Steps to reproduce:
copier copy gh:Tecnativa/doodba-copier-template
answer all questions:
Odoo v8
Postgresql 9.5
docker-compose -f prod.yaml down ; docker-compose -f prod.yaml build --no-cache ; docker-compose -f prod.yaml up --build --remove-orphans --force-recreate -d
Then fails and no instance created:
Err https://deb.nodesource.com jessie/main Sources
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Err https://deb.nodesource.com jessie/main amd64 Packages
server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Get:5 http://deb.debian.org jessie/main amd64 Packages [9098 kB]
Get:6 http://security.debian.org jessie/updates/main amd64 Packages [992 kB]
Get:7 https://apt-archive.postgresql.org jessie-pgdg-archive/main Sources [422 kB]
Get:8 https://apt-archive.postgresql.org jessie-pgdg-archive/main amd64 Packages [1142 kB]
Fetched 11.8 MB in 9s (1249 kB/s)
W: Failed to fetch https://deb.nodesource.com/node_6.x/dists/jessie/main/source/Sources  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
W: Failed to fetch https://deb.nodesource.com/node_6.x/dists/jessie/main/binary-amd64/Packages  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
E: Some index files failed to download. They have been ignored, or old ones used instead.
Traceback (most recent call last):
File "/opt/odoo/common/build", line 30, in
subprocess.check_call(command)
File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '/opt/odoo/custom/build.d/20-update-pg-repos' returned non-zero exit status 100
ERROR: Service 'odoo' failed to build: The command '/bin/sh -c /opt/odoo/common/build && sync' returned a non-zero code: 1

This is not a problem with the copier template, as it comes from invalid certificates from the Debian repo servers.
There is nothing we can do about it, but wait that they fix it, so closing...

I read you can put an external certificate on Docker file and with RUN command we can update this certificate this can be a good opportunity to update the images with this possibility?

https://askubuntu.com/questions/1095266/apt-get-update-failed-because-certificate-verification-failed-because-handshake

Ok, we might be able to update ca-certificates in the image to fix this, but I don't think putting the certificate there is the solution. Re-opening this to further investigate...

https://github.com/debuerreotype/docker-debian-artifacts/issues/15
I read:
My Go program running in the Debian container fails any HTTP requests towards sites using Let's Encrypt's certs with an error message as x509: certificate signed by unknown authority
Simply adding and running ca-certificates fixs the issue.
RUN apt-get update
&& apt-get install -y --no-install-recommends ca-certificates
RUN update-ca-certificates
From Docker's build log, guess this does the magic by adding the missing root ca.

Something like that would help, but the best solution might be placing another custom script like https://github.com/Tecnativa/doodba-copier-template/blob/main/odoo/custom/build.d/{%25 if odoo_version < 11 %25}20-update-pg-repos{%25 endif %25}.jinja with higher priority to update the packages in the Doodba images that are already frozen.

It seems promising !!!

Joao at this time how can i update modules on my productive odoo 8 environment?
Usually i run this command, but right now i cant update anithing o install a new odoo 8
docker-compose -f prod.yaml down ; docker-compose -f prod.yaml build --no-cache ; docker-compose -f prod.yaml up --build --remove-orphans --force-recreate -d
Any advise?
Regards

I have the same problem in version 12.0

Same error here with v8.0. This issue due https://github.com/nodesource/distributions/issues/1266.
I build osind/doodba:8.0-onbuild for development and precaution purpose while that issue still open. Works well for my development and few of my deployments.

Thanks all for the suggestions. Turns out that, for this particular issue, an update to the ca-certificates package wouldn't suffice as, for the old Debian versions we use in older Doodba images, it is no longer updated. Anyway, the fix is already on the way with https://github.com/Tecnativa/doodba-copier-template/pull/279


Upgrade global-dirs to 1.0.0

This fixes #2

Hmm, this is an interesting one! On OSX this works perfectly (even with node installed by Homebrew). But on Linux I can reproduce the issue, it's related to a "wrong" yarn package folder I think. Let me know if I should open an issue on the global-dirs repository or if I'm overlooking something.
OSX:
> npx ava
⠼ { globalDirs:
   { npm:
      { prefix: '/usr/local',
        packages: '/usr/local/lib/node_modules',
        binaries: '/usr/local/bin' },
     yarn:
      { prefix: '/Users/cedric/.config/yarn',
        packages: '/Users/cedric/.config/yarn/global/node_modules',
        binaries: '/Users/cedric/.config/yarn/global/node_modules/.bin' } } }

Linux (through docker run -v $PWD:/code -w /code node:10 npx ava):
root@061d5e7d715e:/code# npx ava
⠧ { globalDirs:
   { npm:
      { prefix: '/usr/local',
        packages: '/usr/local/lib/node_modules',
        binaries: '/usr/local/bin' },
     yarn:
      { prefix: '/usr/local',
        packages: '/usr/local/global/node_modules',
        binaries: '/usr/local/global/node_modules/.bin' } } }

I don't think the /usr/local/global is the proper folder for yarn right? When I manually add something globally through Yarn on the docker/linux instance, I get this path:
root@af923ba739ae:/code# yarn global add dog-names
yarn global v1.13.0
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
warning Your current version of Yarn is out of date. The latest version is "1.15.2", while you're on "1.13.0".
info To upgrade, run the following command:
$ curl --compressed -o- -L https://yarnpkg.com/install.sh | bash
success Installed<EMAIL_ADDRESS>with binaries:
      - dog-names
Done in 2.47s.
root@af923ba739ae:/code# which dog-names
/usr/local/bin/dog-names

The output of yarn global dir and npm root -g on contained Linux is also quite different:
root@af923ba739ae:/code# npm root -g
/usr/local/lib/node_modules

root@af923ba739ae:/code# yarn global dir
/usr/local/share/.config/yarn/global

root@af923ba739ae:/code# yarn global bin
/usr/local/bin

Can you open an issue on global-dirs?

Blocked by https://github.com/sindresorhus/global-dirs/issues/13

I'm going to close this as it doesn't look like https://github.com/sindresorhus/global-dirs/issues/13 will be resolved anytime soon...


Public Feed Project

Do the public feed.
https://sites.google.com/codeustudents.com/summer-2019/week-2-guided-projects/public-feed

https://github.com/fluffysheep-codeu/Summer2019-Team30/pull/65


Roll dice to decide the outcome of important decisions

Simple random number generator.

Thanks! I didn't see that script.
/roll on my part was just being cute. In reality /random is more what this script does. I can mod dice.coffee but I think we are doing different things.
What if we changed 'roll' into 'rand':
# rand - Generates a random number between 1 and 100 inclusive
# rand <num> - Generates a random number between 1 and <num> inclusive
# rand <num>-<num2> - Generates a random number between <num> and <num2> inclusive


Print iOS 13.0 when run and click on button on simulator

Whenever click the floating button it prints the iOS 13.0 and nothing happens.
flutter: within plugin iOS 13.0
flutter: Withing example iOS 13.0
In android, it is working perfectly. Why does this happen?

I get the same problem!!!! anyone have a solution？

I just checked the code and this package has not implemented the iOS part. Only Android is supported.


Space travelers -- Missions  -- fetch data from the API

In this pull request I've:

Created a missions-fetch-data branch
Fetched the data of the missions from the Space X API
Storage of just five missions in the store with just 3 properties: name, description, and status
This is the content of the store if you log it:

@Diegogagan2587 THanks dear reviewer, I have moved the dispatch action to App.jsx in order to fetch the data just once when the page loads. THe App.jsx now looks like this:

It should work better now!


Looking for feedback on async local storage in the browser

Hi localForage team and community,
The Chrome team is contemplating standardizing and shipping an async local storage API with the browser. In fact, it would be layered on top of IndexedDB, in a similar way to localForage. You can see the proposal repository at https://github.com/domenic/async-local-storage.
Although I recognize this project has as its mandate supporting older browsers, and so likely wouldn't make use of any browser async local storage directly, we'd still love to get your input on the proposal. Given all your experience building and supporting localForage, it'd be great to hear about how you woul design things from scratch, if they were shipping with the browser. In particular, we have a number of open API design issues that could use community input.
Thanks for your time!

Sounds cool, will take a look 👍

Hey folks, this has madea lot of progress over the last year! It's now living at https://github.com/WICG/kv-storage; there's also an introductory article on the experimental Chrome implementation at https://developers.google.com/web/updates/2019/03/kv-storage.
Things we could especially use the localForage team and community's thoughts on are around some of the open issues. (Or even closed ones.) Things like:

Should the default storage area be the default of the module?
Is an atomic compare-and-swap operation you've noticed people missing in localForage?
Is restricting the allowed key types a good idea?

Thanks in advance!

Will localForage support KV Storage in the future?


Message or notification when search returns no results

When the search does not return a value, the tree just shows a blank . Is there an attribute in jstree or a plugin so when the user searches a string and it does not exist in the tree, it will show a text like "No records found". This should also be available for the ajax loading or initial load when the query does not return anything. BTW, I'm using xml_data plugin.

How to open all children of a certain node ??
How to get the node IDs that resulted from the search ??

@AboObe
https://www.jstree.com/api/#/?q=open_node&f=open_node(obj [, callback, animation]) - use node.children as the first parameter
https://www.jstree.com/api/#/?q=search.js&f=search.jstree


Add retries

I often get the following error when running this gh-action:
   shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    TERM: xterm-256color
curl: (3) URL using bad/illegal format or missing URL
Error: Process completed with exit code 3.

This is because github most likely has often micro outages. Adding a retry should mitigate this.

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


Dependabot opens PR for unreleased github-actions

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
github-actions
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
No response
dependabot.yml content
https://github.com/ParanoidUser/toolbox-opdf/blob/develop/.github/dependabot.yml
https://github.com/ParanoidUser/codewars-handbook/blob/main/.github/dependabot.yml
Updated dependency
Bumps actions/setup-java from 19eeec562b37d29a1ad055b7de9c280bd0906d8d to c3ac5dd0ed8db40fedb61c32fbe677e6b355e94c.
What you expected to see, versus what you actually saw
Everything seems to work fine yesterday, but today Dependabot opened a couple of PRs across repositories to bump the current hash to the latest committed (but unreleased) version.
Here is the commit it's referring to https://github.com/actions/setup-java/commit/c3ac5dd0ed8db40fedb61c32fbe677e6b355e94c as well as list of releases - https://github.com/actions/setup-java/releases
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
https://github.com/ParanoidUser/toolbox-opdf/pull/38
https://github.com/ParanoidUser/codewars-handbook/pull/177
Smallest manifest that reproduces the issue
No response

It seems that the previous commit hash was not part of any release either?
In that case, I think this is expected. Dependabot understands that you want to track unreleased versions of the action if you are already pointing to unreleased versions of the action, otherwise you would specify released versions instead.
Can you explain your expectation a bit more? Were you temporarily pointing to that commit for some reason and were expecting Dependabot to switch you back to a released version as soon as that specific commit would become part of one release?

This is a manifestation of https://github.com/actions/setup-java/issues/422 - v 3.7.0 was released, Dependabot detected this and upgraded hundreds of repositories to use it, then the maintainers deleted the release leaving 3.6.0 as latest again.
Currently Dependabot just looks at this situation and goes "well, 3.7.0 is newer than 3.6.0, so everything is OK" instead of reacting to the fact 3.7.0 is now missing and the build is broken. Now we know this scenario is possible, could Dependabot try to handle it more gracefully please - either a PR to revert back to the now-latest release so builds work again, or at least flag the issue somewhere instead of just reporting "all ok"?

There was a call on that repo for them to fix it by retagging 3.6.0 as 3.8.0 rather than just disappearing 3.7.0 down the memory hole, presumably that's now been done, so Dependabot should now begin fixing the damaged repos automatically. Switching to using the hash would prevent this, but also prevent upgrades, so not really a solution generally AIUI?

Switching to using the hash would prevent this, but also prevent upgrades, so not really a solution generally AIUI?

How so?

Approx. 15 minutes ago a new version 3.8.0 was released 😃

For @ParanoidUser's case, I think specifying a commit hash with a commented out version like in https://github.com/dependabot/dependabot-core/pull/5951 might have avoided the issue. I will double check that, namely, that a commit hash with an incorrect version tag commented out (incorrect because of the removal of the associated tag) won't get any updates.

Just looping back here to confirm that even if a commented out version is specified, one will get updates to an unreleased version, and on top of that, the version comment won't be updated.
Hard for us to fix, but we should probably do something about it at some point, at least detect the situation and avoid creating a PR.

@deivid-rodriguez, I think, for one, the docs are misleading on this:

... this approach [using SHAs] means you will not automatically receive updates for an action ...

This is certainly not the case. We do and we should.
At Log4j, we also have the very same problem described in this ticket. As this dependabot PR shows,
apache/logging-parent/.github/workflows/build-reusable.yaml@e45457c683302242be5e8e7c3c33edf8f0e0ec0e # rel/10.4.0

(Commit e45457c683302242be5e8e7c3c33edf8f0e0ec0e indeed points to the 10.4.0 release tagged with rel/10.4.0)
reference is replaced with
apache/logging-parent/.github/workflows/build-reusable.yaml@7750fb0f674da0abb358414ea19464ecd996e36f # rel/10.4.0

Noite that neither 7750fb0f674da0abb358414ea19464ecd996e36f points to any release, nor the # rel/10.4.0 comment is correct anymore.
Hence, dependabot bumps the GitHub Actions reusable workflow reference to a commit ID that is not associated with any release.

I saw similar behavior in https://github.com/google/jax/pull/20639; dependabot opened a PR changing the commit hash to the current HEAD of actions/upload-artifact, while claiming the commit was associated with v4.

... this approach [using SHAs] means you will not automatically receive updates for an action ...

This is certainly not the case. We do and we should.

@vy Sorry for never replying here. You're right, I think the docs are misleading there. What I think they want to imply is that if you specify a major version for example (not a SHA), then your actions will automatically use the latest patch/security version in that major. That won't happen if you specify a SHA: Github Actions will always pick up that specific revision of the action. I think that's what's meant by "will not automatically receive updates for an action", but it's definitely confusing since Dependabot WILL indeed create PRs with updates for the workflows using a SHA-pinned action.
I think the Dependabot team would definitely appreciate a PR rewording those docs to make things more clear!

To be clear, the issue I saw is not a documentation issue, but bug in the dependabot implementation. Dependabot claimed to be updating a commit hash to v4, when in fact it was updating to the latest (unreleased) commit on HEAD.
I posted here becuase I thought this was a duplicate. If you'd prefer me to open a new issue, please let me know!

@deivid-rodriguez, dependabot submits PRs updating SHAs to values that don't correspond to a release. As @jakevdp and I have been trying to explain, this is not a documentation issue, this is certainly unexpected, and hence pretty much qualifies as a dependabot bug.
This bug also has security implications too. Such that, OSSF Scorecards expects a project to pin dependencies using their hashes, though as we have demonstrated above, dependabot messes up all such pinning.

@vy I did not say this is a documentation issue. You pointed out that, in addition to the report, the documentation was misleading and I said you're right and recommended to update it.
As I've been trying to explain, the original reason as reported by @ParanoidUser explaining why the Dependabot PR did not correspond to a release, it's because the action's author deleted the release (tag) after the PR was created, so the SHA became "orphan". I think there's not a lot that can be done about that.
I think the other example given by @jakevdp (https://github.com/google/jax/pull/20639) may be due to Dependabot not recognizing the version comment format (# ratchet: actions/upload-artifact@v4) and incorrectly thinking that the action is just tracking the latest HEAD sha (and thus updating it).
I think the latter issue can be addressed in Dependabot's side.
In any case, I'm no longer a maintainer of this repo so I can't help here, just tracking this issue and offering advice because I had participated in this thread originally when I was maintaining this repo.

Right @jakevdp, then it was probably a bad guess!
Ok, I have another guess. In https://github.com/google/jax/pull/20639/files, I think the previous SHA in your workflows (5d5d22a31266ced268874388b861e4b58bb5c2f3I) became out of date (now v4 is associated to a newer SHA). That makes Dependabot is incorrectly think that you want to pin to the latest SHA in the main branch of the action and updating to that.
If that's the case, that's a Dependabot bug, it should trust the comment even if the SHA does not point to the commented tag.


Global DOM state query will cause conflicts - should be scoped to component

This techniques queries the entire document to get input state out of the DOM. This could cause all sorts of trouble if you had other stuff on the page.
The query should be scoped to the current component.

https://github.com/didierfranc/react-stateless-input/pull/1#issuecomment-307100108


Some suggestions for TCoRFix

First of all, thank you for making this, It's great to see the original version of Butcher Bay working on modern GPUs without having to do any other workarounds. I don't know if you're still working on this, but I'd like to throw some suggestions here that would further enhance Butcher Bay.
1. Widescreen fix for fonts and HUD elements: The game has a very minimal HUD but there's a pretty noticeable stretching on HUD elements and subtitles when playing it in 16:9 aspect ratio, would be nice to have them at the correct aspect in widescreen.
2. Fix for flickering when using the Eyeshine mechanic on shader mode 2.0++: The shader mode 2.0++ provides really cool looking soft shadows, but there's an annoying issue with flickering when using the Eyeshine on lit areas, which doesn't happen in any other shader mode.
https://github.com/user-attachments/assets/976b313a-f193-4601-9516-234d27d575c5

Hi, I haven't see the flickering issue when I worked on this, what GPU do you use? Can you upload a savegame?

My GPU is a GTX 1060, using the latest driver, here's a quicksave if you want to check.
Quick.zip

I've added an optional fix that seems to fix the flickering on my nvidia card, can you try latest version?

Yup, that seems to fix it, I've tested in other levels aswell and haven't seen any flickering, thank you:
https://github.com/user-attachments/assets/65930f85-d4b1-47f0-abdb-52829b5b8ed0


makes version/action guard functional

As written, these guards will always return the original value. Was rather confused that "latest" was not being respected - indeed being passed literal - during our testing.

We're closing PRs against our old cookbooks (chef/ vs itchef/), as they have been retired -- apologies!


Add Devtestlabs/2018-09-15

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

This PR adds devtestlabs/2018-09-15 stable release. This swagger has already been reviewed and approved here: https://github.com/Azure/azure-rest-api-specs-pr/pull/579.

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

@jviau please rework you PR in a way that first commit is a copy of the existing swagger with the new name and folder structure and the second commit is update with you changes. Otherwise it is not clear what was changed since the last version.

@hovsepm sorry, thought that was only needed for the review PR. I have reworked the commits as requested now.

tag: package-2016-05

Is there any specific reason Java multi-api does not contain the new API version?

Refers to: specification/devtestlabs/resource-manager/readme.md:146 in 6af1914. [](commit_id = 6af191447abf057ee3216d1f7794014d19256ece, deletion_comment = False)

@hovsepm thank you for catching that. I have added it.

@AutorestCI rebuild azure-sdk-for-java

Anything else I need to do before this can be merged in?

For .NEt you will need to create a PR from this swagger to https://github.com/Azure/azure-sdk-for-net repository. Refer to the readme.md file there.


Build.sbt ArtifactID incorrect

In the Readme file, the build instructions show the following:
libraryDependencies += "com.500px" %% "kinesis-stream" % "0.1.6"
However, that artifact ID is not present in most common repositories and when attempting to build you will get:
sbt.librarymanagement.ResolveException: unresolved dependency: com.500px#kinesis-stream;0.1.6: not found
Searching on Sonatype it looks like it should be:
libraryDependencies += "com.500px" %% "kinesis-stream_2.12" % "0.1.7"

fixing in #10


custom aggregation types are wrong

material-react-table version
v1.11.3
react & react-dom versions
v18.20.0
Describe the bug and the steps to reproduce it
The arguments provided to a custom aggregation function don't seem to match the spec for custom aggregation functions:
export type AggregationFn<TData extends AnyData> = (
  getLeafRows: () => Row<TData>[],
  getChildRows: () => Row<TData>[]
) => any

Instead, getLeafRows (first argument), is the id of the column, and getChildRows (second argument) is an array of the data to aggregate:
{getLeafRows: "age", getChildRows: Array(4)}

(Actually, these arguments seem better, but they're not the expected ones.)
Minimal, Reproducible Example - (Optional, but Recommended)
CodeSandbox example
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
No, because I don't understand it
Terms

[X] I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

I guess I would say "aggregation arguments are wrong" -- not a Typescript issue, the arguments to aggregationFn are just not what the documentation says they should be (if I'm reading it correctly ...). Specifically:

Index
Expected
Actual

0
() => Row<TData>[]
string

1
() => Row<TData>[]
Row<TData>[]


Example of a GPU Job Pod ?

How do you specify a pod that has # of GPUs as requirements? I checked in the test/data examples but none of those have gpu as resource.

Problem is that Kubernetes is by default not allowing access to GPU devices. They are talking about it for over a year now. Writing up proposals, recommendations and plans. https://github.com/kubernetes/kubernetes/issues/19049 and https://github.com/kubernetes/kubernetes/issues/17035 This is so frustrating that Nvidia decided to have their own Docker clone especially for that purpose https://github.com/NVIDIA/nvidia-docker Also Mesosphere DCOS supports GPUs out of the box. A LOT of people especially from Deep Learning environments abandoned K8S because of lack of GPU direction. Seems silly,

k8s based on docker, not nvidia-docker. i use docker run on cpu, and use nvidia-docker run on gpu. but how to use the same way to run both gpu and cpu.
i also want a example to slove my problem

@styk-tv All great points, but to be clear, DC/OS had no issue because it runs binaries, not containers, by default.
@tbchj Please ask in the appropriate place then. Until upstream provides in 1.6 then what can be done here? https://github.com/kubernetes/kubernetes/issues/40998 https://github.com/kubernetes/kubernetes/issues/17035 Once it's in, you will use it here like you use it elsewhere in 1.6...which means probably not at all here because that's a pod-level concern not a node-level concern. Assuming your ASGs provide GPU enabled instances, if a pod can't be scheduled because of a lack of GPUs then it should scale up so it finds one.
How well that will work we won't know until we get there! :D but at least it's getting closer..

gpu support has been merged to kubernetes master https://github.com/kubernetes/kubernetes/pull/42116


Github Api analyze

We want to see number of stars so we can sort.
We want to see the code type, so we can also filter by Lua or vim script.
There is a rate limit that we need to discuss.
Plugins data will be statically available.
what about a 1 hour server cache for each plugin? Should it be enough? Better ideas?

I don't know much of the JS world and about our infrastructure. Ideal scenario would be a task queue that asynchronously gets this info (stars and language) and saves. I am pretty much familiar with stuff like that in Python or Go. Is that possible with the current servers?


[flink] Fix partition filter mismatch the column index

Purpose

Linked issue: close https://github.com/apache/paimon/issues/4004

Tests

API and Format

Documentation

+1


Made JsonPath and parse_json_path public.

I need access to these lower level components. I want to run the parser once and store the resulting JsonPath. Then I will reuse the path to make a JsonPathFinder for different instances of serde_json::Value.

Closing in favor or: https://github.com/besok/jsonpath-rust/issues/10


Cannot update valuesYaml field for catalog app

rancher/rancher:master

Deploy a catalog app
Click view API
Click upgrade action

Result:
There is no valuesYaml field in the params

Validation Steps:

Deploy an app e.g like docker-registry v1.6.1 from the library catalog with default configurations
after installed click View in API to upgrade the app with the following config

replicaCount: 2
image:
  repository: registry
  tag: 2.7

ensure both image tag and replicas are updated correctly.

Verified in master 02/15
Now I can see the valuesYaml field in upgrade param.

Deploy a catalog app with yaml in edit yaml mode
Upgrade the catalog by changing the yaml

Now I can see the changed yaml applied to the catalog


Swagger does not support two rest services in one web.xml

I have implemented two rest services with jersey, they are in different packages. I want to deploy them in one web.xml but I am expecting I can get two separate swagger.json(s) by visiting different path:
http://localhost:8080/mywebapp/service1/swagger.json
http://localhost:8080/mywebapp/service2/swagger.json
but actually, I could not get what I need, the result is, each first time I open one of the above url after the my web container(Jetty here) is start up I can get the right swagger.json doc, but the second time no matter which paths i visit, i will keep getting the doc that I first time visit.
if you could not understand the case, let me  give an example:  see below part of my web.xml
<servlet>
	<display-name>servlet1</display-name>
        <servlet-class>com.sun.jersey.spi.container.servlet.ServletContainer</servlet-class>
	<init-param>
		<param-name>com.sun.jersey.config.property.packages</param-name>
		<param-value>com.test.rest.service1; io.swagger.jaxrs.listing</param-value>
	</init-param>
	<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
	<servlet-name>servlet1</servlet-name>
	<url-pattern>/service1/*</url-pattern>
</servlet-mapping>

<servlet>
	<display-name>servlet2</display-name>
        <servlet-class>com.sun.jersey.spi.container.servlet.ServletContainer</servlet-class>
	<init-param>
		<param-name>com.sun.jersey.config.property.packages</param-name>
		<param-value>com.test.rest.service2; io.swagger.jaxrs.listing</param-value>
	</init-param>
	<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
	<servlet-name>servlet2</servlet-name>
	<url-pattern>/service2/*</url-pattern>
</servlet-mapping>

I can run the application in my local Jetty then I open path http://localhost:8080/mywebapp/service1/swagger.json and I can get the api doc successfully, But when I try to get the api doc for my another service by visiting http://localhost:8080/mywebapp/service2/swagger.json, I am not getting the api doc for service2, instead, I am keep getting the api doc for service1, even though I have set the path to service2.
if there a way that can make two rest services running in one container, and able to generate two separate swagger api docs by visiting different path?
Thanks

Please take a look at https://github.com/swagger-api/swagger-core/pull/1397 - there are also other issues here on the matter. I cannot tell you if or when that PR is going to be merged though.

Looking at the PR, seems like a good idea to provide config ID to distinguish between them. What PR is missing, is applying this idea to BeanConfig as well.

I think this issue (2 rest apis in one web.xml) is solved as of 1.5.8. Have a look at that example https://github.com/swagger-api/swagger-samples/tree/master/java/java-jersey-jaxrs-multi
The new functionality allows you to set swagger.config.id and swagger.scanner.id as init-params in web.xml to allow swagger to distinguish configurations.
I am still not sure though whether multiple apis using BeanConfig work.

This is where I am having trouble. I cannot figure out how to do this without web.xml
Does anyone know of an example or where there is more information?

If you want to do this without a web.xml file, you could just create 2 Swagger web-services like this one: https://github.com/Coreoz/Plume-archetypes/blob/master/plume-archetype-querydsl-jersey-guice/src/main/resources/archetype-resources/src/main/java/webservices/internal/SwaggerWs.java

@amanteaux This was the only approach that worked for me (without a web.xml) - THANKS A LOT! (just signed up to GitHub to say thank you)

I am facing something same issue.I have two servlet configure as folloeing:
http://localhost:8080/mywebapp/rest/swagger.json for this Rest service URL is
http://localhost:8080/mywebapp/rest/for/firmName/getMessage
http://localhost:8080/mywebapp/restservice/swagger.json
http://localhost:8080/mywebapp/restservice/firmName/getMessage2
I have configured this by declaring two beanconfing.But facing same issue as stated in orginal issue.
Could you please help me in this issue.


Support for B-frames in decode order

I have a IP camera that supports B-frames. Running the client example doesn't seem to support non-monotonic timestamps:
.\target\debug\examples\client.exe client mp4 test.mp4 --url "rtsp://<IP_ADDRESS>"
I20220624 13:08:23.257 main client::mp4] Using h264 video stream
I20220624 13:08:23.260 main client::mp4] No suitable audio stream found
W20220624 13:08:23.260 main retina::client] Connecting via TCP to known-broken RTSP server "GStreamer". See <https://github.com/scottlamb/retina/issues/17>. Consider using UDP instead!
3433148934 (mod-2^32:<PHONE_NUMBER>), npt 0.000: 20801-byte video frame
I20220624 13:08:23.391 main client::mp4] new video params: VideoParameters { rfc6381_codec: "avc1.640033", pixel_dimensions: (2688, 1512), pixel_aspect_ratio: None, frame_rate: Some((540000, 27000000)), extra_data: Length: 42 (0x2a) bytes
0000:   01 64 00 33  ff e1 00 1b  67 64 00 33  ad 00 c5 30   .d.3....gd.3...0
0010:   0a 80 2f fe  59 b8 08 08  0d 28 00 20  f5 80 0c df   ../.Y....(. ....
0020:   e6 00 20 01  00 04 68 ee  3c b0                      .. ...h.<. }
3433156134 (mod-2^32:<PHONE_NUMBER>), npt 0.080: 130-byte video frame
E20220624 13:08:23.570 main client] Fatal: Timestamp jumped -5400 (-0.060 sec) from<PHONE_NUMBER> to<PHONE_NUMBER> (mod-2^32:<PHONE_NUMBER>), npt 0.020; policy is to allow 0..10 sec only

conn: <IP_ADDRESS>:64589(me)-><IP_ADDRESS>:554@2022-06-24T13:08:23
stream: TCP, interleaved channel ids 0-1
ssrc: 8e3abf51
seq: 00002164
pkt: 23059@2022-06-24T13:08:23

Not sure what the warning about TCP is about

I have a IP camera that supports B-frames.

Interesting! What's the make/model? I've never seen this before. I'm sure I have .mp4 guess around with B frames though so hopefully I can point gstreamer at them to replicate this for testing.

Not sure what the warning about TCP is about

Yeah that seems wrong. It's supposed to say this only for certain live555 versions.

Interesting! What's the make/model?

It's an AXIS Q3536-LVE, but basically any Axis camera with their latest SoC should work.

I've never seen this before.

Same! FWIW it seems like FFmpeg struggles a bit with the stream as well
I can provide a Wireshark capture if you'd be interested, but AFAICT it's just sending video packets in decode order, with the RTP time indicating when it should be presented. It should be identical to how H.264/H.265 is stored in Matroska files.

Good news: I think I can reproduce this behavior with open source software rather than having to buy a camera. That will help with implementation.

Prepare a .mp4 with B-frames. Big Buck Bunny doesn't use them but you can re-encode it to do so: ffmpeg -i BigBuckBunny.mp4 -codec:v libx264 -preset veryslow $HOME/bbb-reencoded.mp4
Run rtsp-simple-server with the stock config in one terminal
In another terminal, publish to the server: ffmpeg -re -stream_loop -1 -i Downloads/BigBuckBunny.mp4 -c copy -f rtsp rtsp://localhost:8554/mystream
in a third terminal, start Retina: cargo run -p client -- mp4 --url rtsp://localhost:8554/mystream out.mp4

Bad news: I'm confused about (or maybe just disappointed by) how this works:

When writing a .mp4 file, we have to make up the DTS somehow. (For background, see ISO/IEC 14496-12 section <IP_ADDRESS>. There's an example in Table 2. This wiki page has links to a free download of that standard and several others.) I guess we need to basically assume DTS=PTS as we go through, but then as we see an entry that jumps backwards in PTS, we retroactively pull up the DTS for all frames we've already seen with a later PTS so they precede this DTS. In fact at least in theory, that can require bumping up DTSs all the way to the beginning of the file if they're dense, because two frames can't have the same DTS. (In practice, the times advance at 90kHz, and we'd never actually support that framerate, so maybe we can just error out if that happens.)

It's weird if at any point in the stream, you don't know if you've seen all the frames with PTS up to the current RTP timestamp or if more are yet to come. In particular:

You don't know how much buffering you should do when presenting a live view. If you guess low, you drop B frames.
Similarly, if you hit ctrl-C in the recording a .mp4, you might not actually have a prefix of the stream, but you might be missing B frames. That's surprising.

It also just seems to complicate the situation with cameras' flaky timestamps. They sometimes jump back in time due to (incorrectly) basing the RTP time on the wall clock (rather than a monotonic clock as they ought to), and stepping that back when using SNTP. Now when we see that, we have to wonder if it's supposed to jump back due to PTS/DTS differences or if it's the time jump behavior.

I can provide a Wireshark capture if you'd be interested

Yes, please, I think that would be helpful, just in case it is doing something differently than in my ffmpeg scenario. E.g. maybe it conveys the intended DTS via a RTP extension or something.
I believe MPEG-TS conveys both DTS and PTS. (See spec, Table 2-21, PTS_DTS_flag.) Seems weird if H.264-over-RTP doesn't.

I believe MPEG-TS conveys both DTS and PTS. (See spec, Table 2-21, PTS_DTS_flag.) Seems weird if H.264-over-RTP doesn't.

I think it really doesn't. There's an expired draft for conveying the dts via an RTP extension, but afaik no one has implemented it.
Curid's PR #81 adds support for this for H.264 by copying the similar approach in gortsplib. gstreamer also has something for this (h264timestamper). As mentioned in PR comments, I haven't compared the two yet.

I made a docker B-frame test stream.
docker run -it --network=host curid/test-stream
ffplay rtsp://<IP_ADDRESS>:8554/1

Image source
# https://nix.dev/tutorials/nixos/building-and-running-docker-images
let
  # nixos 23.05
  pkgs = import (fetchTarball "https://github.com/NixOS/nixpkgs/archive/bd836ac5e5a7358dea73cb74a013ca32864ccb86.tar.gz") {};
  ffmpeg = (
    pkgs.callPackage (
      { lib, stdenv, buildPackages, removeReferencesTo, fetchgit, pkg-config, yasm }:
      stdenv.mkDerivation (
        rec {
          pname = "ffmpeg";
          version = "6.0";

          src = fetchgit {
            url = "https://git.ffmpeg.org/ffmpeg.git";
            rev = "n${version}";
            sha256 = "sha256-ZFBj9vjY39E2yJIWXzcMbOKlnA7K27sCPujbAAy5pi8=";
          };

          configurePlatforms = [];
          setOutputFlags = false; # Only accepts some of them.
          configureFlags = [
            "--disable-everything"
            "--disable-ffprobe"
            "--enable-shared"
            "--enable-protocol=file,pipe"
            "--enable-demuxer=mov"
            "--enable-decoder=h264"
            "--enable-muxer=rtsp"
            "--pkg-config=${buildPackages.pkg-config.targetPrefix}pkg-config"
            "--bindir=${placeholder "bin"}/bin"
            "--libdir=${placeholder "lib"}/lib"
            "--incdir=${placeholder "dev"}/include"
          ];

          postConfigure = let
            toStrip = lib.remove "data" outputs; # We want to keep references to the data dir.
          in
            "remove-references-to ${lib.concatStringsSep " " (map (o: "-t ${placeholder o}") toStrip)} config.h";

          nativeBuildInputs = [ removeReferencesTo pkg-config yasm ];
          buildFlags = [ "all" ];
          doCheck = false;
          outputs = [ "bin" "lib" "dev" "out" ];
          enableParallelBuilding = true;
        }
      )
    )
  {} );
in pkgs.dockerTools.buildLayeredImage {
  name = "curid/test-stream";
  tag = "latest";
  contents = [
    ffmpeg
    pkgs.mediamtx
    (pkgs.writeScriptBin "init.sh" ''
      #!${pkgs.runtimeShell}
      mediamtx &
      ffmpeg -v warning -an -re -stream_loop -1 -i video.mp4 -c copy -f rtsp \
        -rtsp_transport tcp rtsp://<IP_ADDRESS>:8554/1 #>/dev/null 2>&1 </dev/null
    '')
    ./files
  ];
  config = {
    Cmd = [ "init.sh" ];
    Env = [
      "MTX_RTSPADDRESS=<IP_ADDRESS>:8554"
      "MTX_PATHS_1=rtsp://1"
      "MTX_PROTOCOLS=tcp"
      "MTX_RTMPDISABLE=yes"
      "MTX_HLSDISABLE=yes"
      "MTX_WEBRTCDISABLE=yes"
    ];
  };
}

The WebRTC example doesn't work for me on any branch, but it may work for you with some tweaking. The mp4 muxer in the client example would need major changes to support B-frames.


Merge master into feature/laura-bdi-data-import-service-refactor

This pull request was automatically generated because an automated merge hit a merge conflict

Tagging @ptewson-sfdo to review this and decide what we want to do with this branch.


Bring quotes URLs to top level

Since this is the primary function of the site, having it all under /quotes/ seems unnecessary.

Changed to /app/
See commit 4ed03b1


auth.ehealth/sign-in/: add "request factor" pages

auth.ehealth/sign-in/: add "request factor" pages
Summary:

new page "1" with:
- input field "factor" + button "send"
logic:
- after input factor  - call ws "request user 2FA" & goto page "2"
new page "2" with:
- input field "otp" + button "send"
- button "resend otp"
logic:
- after input OTP - call ws "approve user 2FA" and switching logic:
- return to previus page
- error - view message
[x]  Create spec for FE task
[x] Create design layout
[x]  Implement
[x]  Deploy
[x]  Test

@ivchenkodima - add remaining fix into #1550

done


[WIP] Added a test for LOR quad visualization.

@tzanio , do you know how to add a new baseline? I added some dummy pictures, but I do not see any related output in the artifacts 🤔


Adding #[must_use] on an item

When #[must_use] is added, code in downstream crates that did not use a value of that type will get a compiler lint.
New lints for existing code requires a minor version: https://github.com/rust-lang/rfcs/blob/master/text/1105-api-evolution.md#minor-change-introducing-new-lint-warningserrors
We want to support both "bare" #[must_use] and the form with a reason: #[must_use = "foo bar"]

According to Rust Reference about #[must_use] attribute, the following lints have to be added:

[x] enum_must_use_added
[ ] struct_must_use_added
[ ] function_must_use_added
[ ] method_must_use_added
[ ] trait_must_use_added
[ ] union_must_use_added

The union_must_use_added lint requires schema additions before it can be implemented to close this issue.


Ignore motion effect if reduce motion is turned on

If a user turns on reduce motion, we should ignore the motion effects.
If we want to keep the consumer of the library in charge, we should add a recommendation in the header docs and in the example code.
We can also choose to ignore motion on the library level - in which case we should update the header docs to reflect it.

I say we make the lib handle this and promote best practices.
Sent with GitHawk


Issue installing torch-1.7

Hi,
Thanks for sharing this code.
I am trying to install this library and when I run following command:
sudo pip3 install -r requirements.txt

I get following error:
Collecting torch==1.7.0 (from -r requirements.txt (line 3))
  ERROR: Could not find a version that satisfies the requirement torch==1.7.0 (from -r requirements.txt (line 3)) (from versions: 0.1.2, 0.1.2.post1, 0.1.2.post2)
ERROR: No matching distribution found for torch==1.7.0 (from -r requirements.txt (line 3))
WARNING: You are using pip version 19.2.3, however version 20.3.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

Can someone help?

You can comment out torch==1.7.0 from requirements.txt and install the rest.
Then follow https://pytorch.org/ to install pytorch separately. 1.7.1 is fine.

You can comment out torch==1.7.0 from requirements.txt and install the rest.
Then follow https://pytorch.org/ to install pytorch separately. 1.7.1 is fine.


Error with AOT Build

Bug, feature request, or proposal:
if I enable the property fullTemplateTypeCheck as recommended by https://angular.io/guide/aot-compiler#fulltemplatetypecheck
I receive the following error:
ERROR in node_modules\@material-extended\mde\mde.d.ts.MdePopover.html(1,105): : Property '_classList' is private and only accessible within class 'MdePopover'.
What is the expected behaviour?
no error
What is the current behaviour?
build fails
Which versions of Angular, Material-Extended, OS, TypeScript, browsers are affected?
 "@angular/compiler": "^5.2.5",
 "@material-extended/mde": "^1.0.0-alpha.6",

@stocksr
Thank you for reporting this issue.
I'll push a fix to resolve this issue today.

Many thanks - tested with<EMAIL_ADDRESS>and it is working correctly

@stocksr
Great! Thank you for the update.


Quick fix API doesn't work with aliases

Testing #166762
I think someone said that this API would resolve aliases before checking the command, but I don't see that happen
alias sdf='git statuz
I run sdf and don't get my quick fixes

Not yet ready to test 👍🏼
/duplicate #166501

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Extending hygiene tests set - no unused imports

https://github.com/edmcouncil/fibo/blob/master/ONTOLOGY_GUIDE.md#minimal-compliance-hygiene-tests suggests a test to the effect that no ontology is imported (by a given ontology) unless it is explicitly referenced in the importing ontology.
I am not sure what the exact content of this test is.
Looking at the code there I can see two options:

no ontology is imported (by a given ontology) unless the importing ontology has a triple with an entity (i.e., class, property, or individual) from the imported ontology.
a. the imported entity may occupy any position in the triple: subject's, property's, or object's.
no ontology is imported (by a given ontology) unless the importing ontology has a triple where:
a. the property is rdfs:isDefinedBy
b. the object is the imported ontology itself.

Of course both interpretations can be intended, but then this test should probably be split into two.
Also the test may have been designed to achieve something else.
I was wondering whether someone could inform me about the intended interpretation of this test.

I think the main issue is 1. above.  We really want to make sure that if something in an external ontology is referenced by any s, p, o, that the reference resolves, but that we don't import anything 'extra'.  I'm certain there are still cases of this - mainly in provisional ontologies where we've referenced things, then elements were moved around, and we forgot to remove the no longer needed imports.  There are also cases where in the original generation of the OWL, imports were added that were never used.  In the released ontologies there should be fewer cases, if any.

Then this query should do the trick - although it is painfully slow :), sp perhaps there is a space for optimisation.
prefix owl:   <http://www.w3.org/2002/07/owl#>
prefix rdf:   <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
prefix rdfs:  <http://www.w3.org/2000/01/rdf-schema#>

SELECT DISTINCT ?error
WHERE
{
    ?importingOntology owl:imports ?importedOntology.
    FILTER (CONTAINS(str(?importingOntology), "edmcouncil"))
    FILTER NOT EXISTS
    {
        ?s ?p ?o .
        FILTER (?p NOT IN (owl:imports))
        FILTER (CONTAINS(str(?s), "edmcouncil") || CONTAINS(str(?p), "edmcouncil") || CONTAINS(str(?o), "edmcouncil"))
        FILTER (CONTAINS(CONCAT(str(?s), str(?p), str(?o)),str(?importedOntology))).
    }
    BIND (concat ("WARN: ontology ", str(?importingOntology), " does not reference any resource from imported ontology ", str(?importedOntology)) AS ?error)
}


Use MapRootV1 in Key Transparency

This catches up with Trillian. Follow on to #949.
Now that trillian.SignedMapRoot does not directly expose fields, clients are (intentionally) forced to verify the signed map root before accessing it's fields.  This PR updates a few modules in KT to perform this verification where it was not happening before.
Changes:

Upgrade the mutationclient to verify SignedMapRoots.

Move the mutationclient[1]  into client which has the mapVerifier

Autoconfiure the mutation client's poll period to be equal to the minimum delay between map revisions.

Helper methods for retrieving and verifying the latest signed map root.
Update test vectors.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0a2f9f8). Click here to learn what that means.
The diff coverage is 9.7%.

@@            Coverage Diff            @@
##             master     #950   +/-   ##
=========================================
  Coverage          ?   50.33%
=========================================
  Files             ?       34
  Lines             ?     2573
  Branches          ?        0
=========================================
  Hits              ?     1295
  Misses            ?     1040
  Partials          ?      238

Impacted Files
Coverage Δ

core/client/get_and_verify.go
0% <0%> (ø)

core/monitor/monitor.go
16.09% <0%> (ø)

core/client/client.go
0% <0%> (ø)

core/client/mutations.go
0% <0%> (ø)

core/keyserver/epochs.go
36.84% <0%> (ø)

core/monitor/verify.go
0% <0%> (ø)

core/keyserver/keyserver.go
33.16% <23.07%> (ø)

core/client/verify.go
51.61% <25%> (ø)

core/adminserver/admin_server.go
48.93% <44.44%> (ø)

impl/integration/env.go
71.42% <50%> (ø)

Continue to review full report at Codecov.

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


Support mkdocs CSS autolinking feature

When mkdocs discovers a css file in the docs folder of your project, it'll automatically link it into every document in the tree. RTD doesn't do this.
A fix for me (since I'm using autogenerated documentation) is to generate a style linking directive at the top of every file I create. This isn't optimal though, since I have to compute relative links myself here and only here, since RTD translates relative links to be relative to the root of the site elsewhere.

#1313 is a duplicate of this, but contains more info so closing this in factor of it.


ACR cost of zone-redundancy / Availability zones?

where can we find info about the cost implication of zone-redundancy for ACR?
is it the same cost as: Geo Replication ?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 477ec376-8719-7678-dae7-a93f28c27843
Version Independent ID: 97ba21cf-20f9-00e4-55a5-cd4d71c294e7
Content: Zone-redundant registry for high availability - Azure Container Registry
Content Source: articles/container-registry/zone-redundancy.md
Service: container-registry
GitHub Login: @tejaswikolli-web
Microsoft Alias: tejaswikolli

@TiloGit
Thanks for your feedback! We will investigate and update as appropriate.

@TiloGit
Could you please go through below links for better understanding of Cost of Zone redundancy.
https://learn.microsoft.com/en-us/azure/reliability/migrate-app-service
https://learn.microsoft.com/en-us/azure/architecture/framework/cost/design-regions
if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@AjayBathini-MSFT , my questions is for only/pure ACR Azure Container Registry. I understand that if I run VM/AKS/Azure App I need to pay for a instance in each zone. But ACR has no info on that.

Hi @TiloGit
For details on ACR you can find below links
https://azure.microsoft.com/en-us/pricing/details/container-registry/
Zones List:

Pricing details doc;
https://learn.microsoft.com/en-us/azure/container-registry/container-registry-geo-replication

so @AjayBathini-MSFT zone redundancy cost the same as Geo-replication?
Assume AZ we mostly have 3 Zones so we can calculate zone redundancy = 2x Geo-replication?
Our scenario is having ACR in only one Zone (like West US 2) and no Geo-replication just Zone redundancy.
Yes we will use SKU premium

@TiloGit
if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

This was a good issue. No details in docs or pricing page on zone redundancy and if it's basically 3 times the cost, or included in premium?

@AjayBathini-MSFT there is just no information on the ACR page whether it will cost extra to enable zone redundancy. It will be good to have this information displayed somewhere to allow proper budgeting and costing presentation.

with more ppl don't have clarity on how ACR zone-redundancy is charged I deem this ready to be reopen
#please-open

@tejaswikolli-web
Can you add your inputs on above comments.

@TiloGit  - Did you get clarity on cost incur by ACR having just zone redundancy enabled?

@TiloGit - Did you get clarity on cost incur by ACR having just zone redundancy enabled?

After creating a support request I got the following answer:

According to your query I would like to update you that Zone redundancy is a feature of the Premium service tier in Azure Container Registry. According to the documentation, there is no separate cost associated with enabling zone redundancy during the creation of the container registry.
Please refer the below document for more insights on the same:
Zone-redundant registry for high availability - Azure Container Registry | Microsoft Learn


search filter on resources page

1. Objective
To allow easy look up on the resources page
Related Link(s)

search-filter-on-resource-page

2. Description of change
3. Quality assurance

go to /resources
start typing in the search bar, and ensure the resources are filtered according to your search query.

4. Operations impact
5. Business impact

Search bar/functionality on the resources page

6. Priority of Change

Normal

@Joponpin2000 I think we need to implement an 'empty' search results state.

@Joponpin2000 , checking to confirm you got the changes I requested.

@Joponpin2000 I think we need to implement an 'empty' search results state. Can you speak with design about this?

Implemented

@aremu-smog thanks for the pointers. Changes effected. You can check now.
cc: @Demoivre02

Amazing job @Joponpin2000 and kindly ignore this message till tomorrow or next week.
Please enjoy your birthday.
but is it possible for us to include the categories to the search algorithm? e.g someone searches for product, we show all results related to product design, management, etc.
If you think it may require more effort, we can probably put in a ticket for this.

Lol. Thanks, boss. Yes, I can include that.

@aremu-smog @Demoivre02 you can confirm now

Seen @Joponpin2000


Convert Fixnum to Integer in tests

to be compatible with Ruby 2.4.

Well, this might fix R2.4 compatibility but break older Rubies :/

I know. It was ment just as FYI (affects only tests), because I'm not sure how to properly resolve it (use regexp or logic based on Ruby version?).


Dwarf: vector element type resolution

Tag 'DW_TAG_unspecified_type' has gone.
Ref issue https://github.com/solana-labs/move/issues/403

@ksolana, thx!


Nielseniq -  Number of jobs on the  "Careers " button page is not the same with the "See Jobs" button page.

ENVIRONMENT: production
URL: https://scrapers.peviitor.ro
Browser: Chrome
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:

Open the URL in the browser
Search for "Nielseniq" Company
Click on the "Careers" button.
Open the "Careers" button.
Click on the "See Jobs".
Open https://nielseniq.com/?s=&market=global&language=en&orderby=&order=&post_type=career_job&job_locations=romania&job_teams=&job_types=

EXPECTED RESULTS:

Number of jobs on  the "Careers " button page is  the same with the "See Jobs" button page.

ACTUAL RESULTS:

Number of jobs on "Careers " button page is not the same with the  "See Jobs" button page.

Fixed can you retest?

Re-tested, Number of jobs on the "Careers " button page is the same with the "See Jobs" button page.


Panic on connect

I'm able to trigger this panic via a simple tcp connect port scan with nmap:
nmap -sT <IP_ADDRESS> -p8776

panicked netservices-0.5.0/src/connection.rs:108:36:
TCP stream doesn't know remote peer address: Os { code: 107, kind: NotConnected, message: "Transport endpoint is not connected" }
stack backtrace:
   0: rust_begin_unwind
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/panicking.rs:597:5
   1: core::panicking::panic_fmt
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/panicking.rs:72:14
   2: core::result::unwrap_failed
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/result.rs:1652:5
   3: core::result::Result<T,E>::expect
             at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/result.rs:1034:23
   4: <std::net::tcp::TcpStream as netservices::connection::NetConnection>::remote_addr
             at /home/cloudhead/.cargo/registry/src/index.crates.io-6f17d22bba15001f/netservices-0.5.0/src/connection.rs:108:9
   5: <radicle_node::wire::protocol::Wire<D,S,G> as reactor::reactor::Handler>::handle_listener_event
             at ./radicle-node/src/wire/protocol.rs:447:28
   6: reactor::reactor::Runtime<H,P>::handle_events
             at /home/cloudhead/.cargo/registry/src/index.crates.io-6f17d22bba15001f/io-reactor-0.3.0/src/reactor.rs:535:33
   7: reactor::reactor::Runtime<H,P>::run
             at /home/cloudhead/.cargo/registry/src/index.crates.io-6f17d22bba15001f/io-reactor-0.3.0/src/reactor.rs:486:26
   8: reactor::reactor::Reactor<C,P>::with::{{closure}}
             at /home/cloudhead/.cargo/registry/src/index.crates.io-6f17d22bba15001f/io-reactor-0.3.0/src/reactor.rs:300:13
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I have investigated this. The panic happens because, for this specific incoming connection, the OS doesn't know the IP address of the server which connects! This is very strange... I was assuming that for TCP incoming connections the remote address has to be always known, however in this case TcpStream::remote_peer returns io::Error - and I am expecting calls to this method never to error.
I assume that the connection is closed so quickly that when we ask for the remote_peer it is not there anymore...
The only way we have to deal with this, is to assume that remote_peer and similar methods (local_peer?) may fail, and it implies that the connection is dropped. Thus, we need to modify the API of the NetSession. For Heartwood it will mean we will need to match these lines

https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/tree/radicle-node/src/wire/protocol.rs#L457
https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/tree/radicle-node/src/wire/protocol.rs#L470

against errors, and, if one happens, assume the connection dropped and do not register the connection. Will it work?

Yes, this can happen if the connection is lost, or if it is not yet established, so I think we could treat it as a disconnect. As far as I understand, accept() should only return connected sockets, but the error we're getting is ENOTCONN. Still this could probably happen if the socket disconnects quickly enough.
Here's what the man page says are the possible errors:
ERRORS
       The getpeername() function shall fail if:

       EBADF  The socket argument is not a valid file descriptor.

       EINVAL The socket has been shut down.

       ENOTCONN
              The socket is not connected or otherwise has not had the peer pre-specified.

       ENOTSOCK
              The socket argument does not refer to a socket.

       EOPNOTSUPP
              The operation is not supported for the socket protocol.

       The getpeername() function may fail if:

       ENOBUFS
              Insufficient resources were available in the system to complete the call.

One option would be that netservices calls peer_addr, stores it inside the socket struct, and then just returns that. Then, on disconnect, it's just a normal disconnect.

This won't work since peer_addr is a trait method implemented for TcpSocket - there is nowhere to store a state.

When the socket is accepted, you can't call peer_addr and store it?
Otherwise the only option I guess is to have it fail for the caller, but that's quite annoying..

I can't store it - there is nowhere to store it.