Added More applications of electron.

Whatsapp Desktop , Twitch.tv , Wire and Light Table are some popular apps among the many others developed by electron.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Congrats @ayagrwl on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Add cilium-chart as a project to be created for registry mirror

Description of changes:
We switched to installing cilium through helm chart, so for a disconnected setup, this chart will be used from the registry mirror. Import-images command pushes the chart under a project cilium-chart. Users will have to create this project under their registry
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherry-pick release-0.8

/hold

/lgtm


README uses inconsistent example (in set item)

The following from the README:
// In localStorage, we would do:
localStorage.setItem('key', JSON.stringify('value'));
alert('value');

// With localForage, we use callbacks:
localforage.setItem('key', 'value', function(err, value) { alert(value); });

...is quite confusing. Specifically, the localStorage stored value is "value", yet the alerted string is just value (note - no wrapping quotes) and the the localforage stores value, but I'm now confused as to whether localforage is going to stringify...or not, or if it matters.
I think a good example (though I didn't PR this because I've not tested it myself) would be to use an object, along the lines of:
// In localStorage, we would do:
var obj = { value: "hello world" };
localStorage.setItem('key', JSON.stringify(obj));
alert(obj.value);

// With localForage, we use callbacks:
localforage.setItem('key', obj, function(err, result) { alert(result.value); });

(This assumes localforage handles serialisation).
Thoughts?

:+1:

For what it's worth your code will work; localForage handles serialisation.
That's a great point. The example is pretty silly. :+1: from me as well; if you send that as a PR we'll happily merge it.


Fixed issues with new lines in markdown

I've faced an issue with the new lines in markdown during rendering of my CV. Found that in case if optional fields aren't provided there were redundant new lines. Also project section missed new line after dates.

Thank you very much! I will merge this but we should fix the tests first.
Tests failed because of the reason I explained in #53:

The tests failed due to mismatches between the RenderCV's output and reference outputs in the testdata folder. Since a template has been updated, indeed, the reference outputs in the testdata folder should also be updated.
A note about tests:
In some of the tests:

RenderCV generates an output with a sample input.
Then, the output is compared with a reference output, which has been manually generated and stored in testdata. If the files differ, the tests fail.

When the testdata folder needs to be updated, it can be manually regenerated by setting update_testdata to True in conftest.py and running the tests.
Originally posted by @sinaatalay in https://github.com/sinaatalay/rendercv/issues/53#issuecomment-2041646184

I could also do this but it would be nice for new developers to go through this process. Let me know if you encounter any problems!

Yep, my bad. Forgot about tests. I'll check and fix


Loading worlds

When i loas the worlds from fiducial or orbslam examples i get a void world, so there is no bottom, the fiducial has the qr codes

The Dockerfile works for me. Can you provide more information?
If you're running inside docker, you could try to bring up Gazebo w/ the empty world, like this:
gazebo install/orca_gazebo/share/orca_gazebo/worlds/empty.world

If that does not work, then it could be a problem with your docker / rocker environment.

i got this error
Error Code 12 Msg: Unable to find uri[model://seafloor]
That let me with the void space,
and i solved it with this
export GAZEBO_MODEL_PATH=${PWD}/install/orca_gazebo/share/orca_gazebo/models/
Now it correctly shows the seafloor

Ah, of course. I will update the README and the Dockerfile. Thanks!

Thanks for letting me know. I updated the README.md and Dockerfile to point to https://github.com/clydemcqueen/orca3/blob/main/setup.bash.


"No LuaRocks module found for model" after re-pull the repo

Context of the issue.
[Provide more detailed introduction to the issue itself and why it is relevant]
I am practicing on re-train a DNN instructed by the openface. I have pulled new-version of this repo and overrided my old-version. But when I start to train, some errors appear.
Expected behavior.
[Describe what you would expect to have resulted from this process.]
I have cloned the repo several months ago, and to practice experiments, I have pulled the repo again today.
When I am trying to re-train the DNN, after images and classes been loaded. Some bugs appear as followings.
Actual behavior.
[Describe what you currently experience from this process, and thereby explain the bug.]
load the large concatenated list of sample paths to self.imagePath
[====================================== 5552/5552 ================================>]  Tot: 15m40s | Step: 177ms
Cleaning up temporary files============= 5550/5552 ===============================>.]  ETA: 355ms | Step: 177ms
[====================================== 5552/5552 ================================>]  Tot: 15m40s | Step: 178ms
Cleaning up temporary files============= 3011/5552 .................................]     ETA: 7m6s | Step: 167ms
nClasses:  | Ste555290ms================ 2695/5552 .................................]  ETA: 9m4s | Step: 190ms
/home/runzeli/local/torch/install/bin/luajit: ...runzeli/local/torch/install/share/lua/5.1/trepl/init.lua:384: module 'model' not found:No LuaRocks module found for model
no field package.preload['model']
no file '/home/runzeli/.luarocks/share/lua/5.1/model.lua'
no file '/home/runzeli/.luarocks/share/lua/5.1/model/init.lua'
no file '/home/runzeli/local/torch/install/share/lua/5.1/model.lua'
no file '/home/runzeli/local/torch/install/share/lua/5.1/model/init.lua'
no file './model.lua'
no file '/home/runzeli/local/torch/install/share/luajit-2.1.0-beta1/model.lua'
no file '/usr/local/share/lua/5.1/model.lua'
no file '/usr/local/share/lua/5.1/model/init.lua'
no file '/home/runzeli/.luarocks/lib/lua/5.1/model.so'
no file '/home/runzeli/local/torch/install/lib/lua/5.1/model.so'
no file '/home/runzeli/local/torch/install/lib/model.so'
no file './model.so'
no file '/usr/local/lib/lua/5.1/model.so'
no file '/usr/local/lib/lua/5.1/loadall.so'
stack traceback:
[C]: in function 'error'
...runzeli/local/torch/install/share/lua/5.1/trepl/init.lua:384: in function 'require'
...ort/das14a/satoh-lab/runzeli/openface/training/train.lua:23: in main chunk
[C]: in function 'dofile'
./training/main.lua:31: in main chunk
[C]: in function 'dofile'
...ocal/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
[C]: at 0x004064d0
Steps to reproduce.
[Present a minimal example and steps to produce the issue.]
OS and hardware information.
I run it on the centos with GPU K80.

Operating system: [todo]
Torch version: [todo]
CPU architecture: [todo]
GPU type (if using): [todo]

Hi,
problem happens at this line  local models = require 'model' in file "train.lua". I have checked the commit history. I am wondering is this the problem of the torch version?

Hmm, somebody else just posted this to our mailing list: https://groups.google.com/forum/#!topic/cmu-openface/7lS3sajfTmM
Let's keep the discussion here. model.lua is our file. Can you:

Make sure you are in the training directory when you run training?
Try using an older Torch version?

-Brandon.

Thanks @bamos   Solved it!
Make sure you are in the training directory when you run training

Great!
@bragilee - is your error also fixed if you are in the training directory?
I'd merge a PR making the error more clear for future users if anybody adds it.
-Brandon.

Hi Brandon,
Not yet. It is quite strange.
I use the screen on the CentOS.
I use the ".sh" script after the data preprocessing like this:
./util/prune-dataset.py data/nhknews_meanface/dlib-affine-size:96
--numImagesThreshold 3
./training/main.lua -data
/home/runzeli/local/openface/data/nhknews_meanface/dlib-affine-size:96
-cache /home/runzeli/local/openface/training/work
I have checked that filed mentioned are indeed not existing.
So does it make sense if I reinstall torch?
On 26 August 2016 at 22:06, Brandon Amos<EMAIL_ADDRESS>wrote:

Great!
@bragilee https://github.com/bragilee - is your error also fixed if you
are in the training directory?
I'd merge a PR making the error more clear for future users if anybody
adds it.
-Brandon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cmusatyalab/openface/issues/182#issuecomment-242717735,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKvd-qw4z7scT5sGItkBz1cPbvoyJMBqks5qjtbggaJpZM4JtxWd
.

--
Best Regards,
Bragi

Hi all,
Finally the problem is solved.
For me, one reason may be I did not update package installation of torch,
the other reason may be the incorrect directory entry.
Thank you for all your help. ^_^
On 27 August 2016 at 00:19, Lee Bragi<EMAIL_ADDRESS>wrote:

Hi Brandon,
Not yet. It is quite strange.
I use the screen on the CentOS.
I use the ".sh" script after the data preprocessing like this:
./util/prune-dataset.py data/nhknews_meanface/dlib-affine-size:96
--numImagesThreshold 3
./training/main.lua -data /home/runzeli/local/openface/
data/nhknews_meanface/dlib-affine-size:96
-cache /home/runzeli/local/openface/training/work
I have checked that filed mentioned are indeed not existing.
So does it make sense if I reinstall torch?
On 26 August 2016 at 22:06, Brandon Amos<EMAIL_ADDRESS>wrote:

Great!
@bragilee https://github.com/bragilee - is your error also fixed if
you are in the training directory?
I'd merge a PR making the error more clear for future users if anybody
adds it.
-Brandon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cmusatyalab/openface/issues/182#issuecomment-242717735,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKvd-qw4z7scT5sGItkBz1cPbvoyJMBqks5qjtbggaJpZM4JtxWd
.

--
Best Regards,
Bragi

--
Best Regards,
Bragi


chore(infra_utils): rename logger struct

Stack:

#2424 ⬅
#2385
#2384
#2329
#2332
#2328

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is


Unable to get registration token from database

This task doesn't get back any registration token in the gitlab-runner.yaml playbook :
- name: Extract Runner Registration Token directly from Gitlab DB
    become: true
    become_user: gitlab-psql
    vars:
        ansible_ssh_pipelining: true
        query: "SELECT runners_registration_token FROM application_settings ORDER BY id DESC LIMIT 1"
        psql_exec: "/opt/gitlab/embedded/bin/psql"
        gitlab_db_name: "gitlabhq_production"
    shell: '{{ psql_exec }} -h /var/opt/gitlab/postgresql/ -d {{ gitlab_db_name }} -t -A -c "{{ query }}"'
    register: gitlab_runner_registration_token_result

Cause the runners_registration_token column does not exist in the application_settings table. But the runners_registration_token_encrypted exists, however the runners_registration_token_encrypted string is rejected by runner-register api. So you have to copy runners registration token from the gitlab gui, hardcode it in the playbook and run the playbook again.
Did run into the same issue?

I encounter the same issue. Since merge request 23412 the runner tokens are encrypted in the database. gitlab.rb has a setting to seed the runner token on initial setup:
gitlab_rails['initial_shared_runners_registration_token'] = "token"

Did anyone try this?

Seeding the initial runner token didn't work for me. I extracted the token using the GitLab rails-console., see diff https://github.com/jonashackt/gitlab-ci-stack/compare/master...volemont:fixRunnerToken
@papiveron, can you confirm this works for you? I'll then submit a PR

Hello @volemont ...
Sorry for the lag, I didn't test, I find out another which is setting the token myself and pass to gitlab, instead of retrieving the token from gitlab server.
I'lln test it later.
Regards,
Eugène NG


[cudamapper] Ignore -Wunused-parameter for Thrust

Added pragmas for ignoring -Wunused-parameter in Thrust.
I only added it in needed places. @ahehn-nv do you think we should simply do it everywhere where Thrust is included?

rerun tests

rerun tests


fix: Fix interruption sample

add a thredhold in GetStarted intent to avoid over trigger.
fix malformed schema, extra comma
fix value expression.
fix turn.value -> this.value
fix allowInterrutions: notRecognized->true

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
If this is a bug fix, please describe the root cause and analysis of this problem.
Task Item
#1627
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code refactor (non-breaking change which improve code quality, clean up, add tests, etc)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Doc update (document update)

Checklist

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have functionally tested my change

Screenshots
Please include screenshots or gifs if your PR include UX changes.

@a-b-r-o-w-n  why the validation keep failing, I already attatched an issue in the body. any insights?

@luhan2017 The PR description needs to use the github reference syntax (https://help.github.com/en/github/managing-your-work-on-github/closing-issues-using-keywords). I will add some more details to the error output.


Package built for Deno has errors that prevent it from running

Hi, this is a nice tool! I tested this last night and it was working fine with a Deno version that I'm unsure what it was but must've been earlier than 1.2.0. It was compiling correctly and Deno was loading it correctly.
I upgraded Deno this morning to the latest version 1.2.0 and it no longer works. While the project compiles, Deno refuses to run it and throws these errors:
error: TS2345 [ERROR]: Argument of type 'string | URL' is not assignable to parameter of type 'string'.
  Type 'URL' is not assignable to type 'string'.
  return new URL(url).pathname
                 ~~~
    at https://deno.land/std/path/win32.ts:917:18

TS2345 [ERROR]: Argument of type 'string | URL' is not assignable to parameter of type 'string'.
  Type 'URL' is not assignable to type 'string'.
  return new URL(url).pathname;
                 ~~~
    at https://deno.land/std/path/posix.ts:438:18

Found 2 errors.

These are likely produced by this portion of code in %package_name%.js:
import * as path from 'https://deno.land/std/path/mod.ts';
>> const __dirname = path.dirname(new URL(import.meta.url).pathname); <<
const p = path.join(__dirname, '%package_name%_bg.wasm');

I believe this is an issue with the std module files your old Deno install cached. See this issue to reload the cache.
https://github.com/denoland/deno/issues/6737

Thanks a lot @juntao! I did
deno cache --reload my-deno-file.ts

and that solved it.


Remove css_browser_selector.js

css_browser_selector.js is using a proprietary license. We need to remove it

:+1:  We should try to avoid browser-specific hacks for our sample apps anyways.

fixed in the next release


Review Ticket

3/3= In addition to creating a python quiz, tool check, organizing my work, and linking helpful posts and videos, I also created a loop on my quiz. I did this using if, else, elif, and defining variables. This means that if the user types a non-answer, they will be prompted the question again until they do answer a defined answer.
Here is my fastpage.
This is my Quiz- here I used a loop so incorrect answers will not be taken.
This is my Tool Check.
This is my Work Page where I organize my work weekly.
This is my Extra Resources page, video resource post, and posts resource post.

3/3

created a great quiz (with an extra loop option that re-asks the question if you don't give a proper response <- using python)
made a tool check that works well
Creted a work page that organizes all her work for the class
also made an extra page with 2 posts where she stores extra recourses


Added ApertureScience Logo

Description
Only fill in the fields below if relevant.
Features

Added ApertureScience Logo

Issues
TODO

Hopefully you got the new commit aswell, because I forgot the ;; :)

I see no reason to merge this unless "ApertureScience" is an actual Linux distro.

I see no reason to merge this unless "ApertureScience" is an actual Linux distro.

Hmh sad. It looks really good though. But Windows isn't a Linux distro aswell.

I should've clarified: A distro or an actual OS. Like Solaris, AIX, etc.

I understand your decision just one question though, what is the downside of adding it?

It would set a dangerous precedent. If we merge this, in the future people will ask to add a Black Mesa logo or a sport team (e.g. Barcelona or Liverpool) logo because they saw this PR being merged, so we have to be fair, and if we have all non-OS related logo included, the filesize will be too big. Either we include them all, or we don't.
Since Dylan seems to endorse my decision here, I'm closing this PR.

Thanks for the explanation I fully understand :)


Add friendly name to event MQTT message

I wanted to be able to parse the sensors by their friendly name so I added a couple of lines to wyzesense2mqtt.py
Process event
def on_event(WYZESENSE_DONGLE, event):
if (valid_sensor_mac(event.MAC)):
if (event.Type == "state"):
LOGGER.info(f"State event data: {event}")
(sensor_type, sensor_state, sensor_battery, sensor_signal) = event.Data
sensor_name = SENSORS[event.MAC]['name']    <<<---------
event_payload = {
'available': True,
'name': sensor_name, <<<------------
'mac': event.MAC,
This works for me. Please consider adding it to the main code.
I do not run Home Assistant. I use MQTT with Node-Red and other local scripts. Thanks for the great bridge software, it gives me access to these very inexpensive sensors. Running as a service on an old Pi Model B Revision 2.0 under Buster.

I like this idea, but I would suggest that it be configurable via config.yaml.

Thank you for turning this into a proper pull request; I'm not facile with GIT. I appreciate your quick and well thought out response.

@dennyfmn thanks for the good idea here, and @dale3h thanks for the quick implementation. I submitted a few requested tweaks on the PR, but otherwise will be happy to pull this in this weekend. And I think I'll wrap 1.1 so that this is officially released as well.

This issue can be closed as per #26 and 7684bffc309895d1f29fd1d17b0f8473fe935577.


Bump inspec to 4.7.24/20190725222329

Sorry robot, we gave you bad instructions.  https://github.com/chef/automate/pull/1086


Replication: add an API to at least list existing replications

List of replication items
GET http://localhost:8080/services/rest/index/{index_name}/replication
{
  "successful":true,
  "info":"2 item(s) found",
  "items":
  [
    {
    "name":"http://localhost:8080/geo_repl",
    "replicationType":"BACKUP_INDEX",
    "remoteUrl":"http://localhost:8080",
    "remoteIndexName":"geo_repl",
    "secTimeOut":120,
    "isActiveThread":false
    },
    {
    "name":"http://localhost:8080/geo_repl2",
    "replicationType":"BACKUP_INDEX",
    "remoteUrl":"http://localhost:8080",
    "remoteIndexName":"geo_repl2",
    "secTimeOut":120,
    "isActiveThread":false
    }
  ]
}

Get one replication item
GET http://localhost:8080/services/rest/index/{index_name}/replication?name={replication_name}
{
  "successful":true,
  "name":"http://localhost:8080/geo_repl",
  "replicationType":"BACKUP_INDEX",
  "remoteUrl":"http://localhost:8080",
  "remoteIndexName":"geo_repl",
  "secTimeOut":120,
  "isActiveThread":false
}

Delete one replication item
DELETE http://localhost:8080/services/rest/index/{index_name}/replication?name={replication_name}
Create/update a replication item
POST http://localhost:8080/services/rest/index/{index_name}/replication?name={replication_name}
Header: Content-Type:application/json
Pass the parameter of the replication item as JSON in the body. The name will be automatically generated.
{
  "replicationType":"BACKUP_INDEX",
  "remoteUrl":"http://localhost:8080",
  "remoteIndexName":"geo_repl2",
  "secTimeOut":120
}

Run the replication
POST http://localhost:8080/services/rest/index/{index_name}/replication/run()?name={replication_name}

Documentation: http://www.opensearchserver.com/documentation/api_v2/replication/README.md


I can't execute command "./gradlew bundleRelease" in android

Please use the Discussion board if you want to get some help. Please use issues to report bugs.

Description
I want to make in app function using this library. So I install 'react-native-iap' module. And I follow every direction to use this library. But I didn't execute "./gradlew bundleRelease" command.
I follow these things:

add "minSdkVersion = 24, supportLibVersion = "28.0.0", kotlinVersion = "1.5.0", androidXAnnotation = "1.1.0", androidXBrowser = "1.0.0" " in android/build.gradle file.
add dependencies "classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlinVersion"" in android/build.gradle file.
add "missingDimensionStrategy "store", "play"" line in android/app/build.gradle file.

Expected Behavior
I want to connect store (app store, play store) and I want to get products' information.
And I want to make .aab file using './gradlew bundleRelease' command.
Screenshots

Environment:

react-native-iap: "^12.4.8"
react-native: "0.68.2"
Platforms (iOS, Android, emulator, simulator, device): android emulator

Error Message

Task :react-native-iap:generatePlayReleaseRFile FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':react-native-iap:generatePlayReleaseRFile'.

Could not resolve all files for configuration ':react-native-iap:playReleaseCompileClasspath'.
Failed to transform react-native-0.71.0-rc.0-release.aar (com.facebook.react:react-native:0.71.0-rc.0) to match attributes {artifactType=android-symbol-with-package-name, com.android.build.api.attributes.BuildTypeAttr=release, org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.libraryelements=aar, org.gradle.status=release, org.gradle.usage=java-api}.
Could not find react-native-0.71.0-rc.0-release.aar (com.facebook.react:react-native:0.71.0-rc.0).
Searched in the following locations:
https://repo.maven.apache.org/maven2/com/facebook/react/react-native/0.71.0-rc.0/react-native-0.71.0-rc.0-release.aar

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings
Execution optimizations have been disabled for 3 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.

[Optional] Additional Context

@Yeonbin the error states:

Could not find react-native-0.71.0-rc.0-release.aar
That's not related to this library

@Yeonbin the error states:

Could not find react-native-0.71.0-rc.0-release.aar
That's not related to this library

I just think the main was "react-native-iap:generatePlayReleaseFile Failed".
But main error was that you mentioned. Thank you! I fixed it!
I have another question. Is my code correct? Or is there any error to fixed?

You should probably change your import to
 import * as IAP from 'react-native-iap' or import the methods directly


Enhance repeat feature in TKG

Support three types of repetition in TKG:

exit test when encountering a failure in last iteration
keep running tests and collect failure rate in the result summary
stop  running when encountering a success in last iteration

Add AOT_ITERATIONS option to allow repeat on AOT tests with different iteration number.

Related: https://github.com/adoptium/TKG/pull/366


[SPARK-42584][CONNECT] Improve output of Column.explain

What changes were proposed in this pull request?
Currently, connect display the structure of the proto in both the regular and extended version of explain. We should display a more compact sql-a-like string for the regular version.
Why are the changes needed?
Improve output of Column.explain so as display the same as the explain API of sql expression.
Does this PR introduce any user-facing change?
'No'.
New feature.
How was this patch tested?
New test cases.

This PR has not been implemented yet.
@hvanhovell Could you take a look? Does this one satisfy your expected.

ping @hvanhovell Could you have time to take a look?

@hvanhovell Could you take a look again?

@hvanhovell Could you take a review ?

ping @hvanhovell Could you take a look?


ci: disable matrix fail fast

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 66.04%. Comparing base (4bd43c0) to head (83e3215).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #434      +/-   ##
==========================================
- Coverage   70.04%   66.04%   -4.01%
==========================================
  Files          44       44
  Lines        2474     2474
  Branches      526      526
==========================================
- Hits         1733     1634      -99
- Misses        573      666      +93
- Partials      168      174       +6

Flag
Coverage Δ

unittests
65.96% <ø> (-3.52%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 5 files with indirect coverage changes


CVE-2007-4559 - Creating a patch

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


nodePackages: init sass clubhouse-cli makam inliner undollar (combine several PRs)

This PR is my attempt to help with the issue (and potential, temporary solution) described in this Discourse thread.
Every time someone changes the NodeJS package list and generates a new .json file, it results in merge conflicts for subsequent NodeJS package list modifications, since they all affect the same file.
What I did was manually go through some PRs, copy their changes but skipping the .json file changes and then I just ran generate.sh once. I included all authors through co-authoring.
These are the PRs that I combined:

https://github.com/NixOS/nixpkgs/pull/64566
https://github.com/NixOS/nixpkgs/pull/65006
https://github.com/NixOS/nixpkgs/pull/63935
https://github.com/NixOS/nixpkgs/pull/67703
https://github.com/NixOS/nixpkgs/pull/77705

I haven't done any testing yet since I'm kinda still at work so I'd go through the checklist later, in case this approach here is considered worth doing.
I think this approach is easy to automate. Just go through a list of PRs, get their diffs, apply them but skipping the .json changes, accumulate the commit authors while doing so and then generate the .json files once.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/call-for-nodepackages-maintainers/9176/25

Result of nixpkgs-review pr 100606 1

2 packages marked as broken and skipped:
- rambox-pro
- teleprompter

54 packages built:
- antora
- bitwarden-cli
- castnow
- create-cycle-app
- emojione
- epgstation
- etcher
- fast-cli
- gtop
- image_optim
- imapnotify
- iosevka
- joplin
- lessc
- lumo
- mastodon-bot
- mirakurun
- netlify-cli
- parity-ui
- pm2
- postcss-cli
- pulp
- python37Packages.batchspawner
- python37Packages.dockerspawner
- python37Packages.jupyterhub
- python37Packages.jupyterhub-ldapauthenticator
- python37Packages.jupyterhub-systemdspawner
- python37Packages.jupyterhub-tmpauthenticator
- python37Packages.oauthenticator
- python38Packages.batchspawner
- python38Packages.dockerspawner
- python38Packages.jupyterhub
- python38Packages.jupyterhub-ldapauthenticator
- python38Packages.jupyterhub-systemdspawner
- python38Packages.jupyterhub-tmpauthenticator
- python38Packages.oauthenticator
- redoc-cli
- ripcord
- shout
- slack
- styx
- thelounge
- triton
- twemoji-color-font
- vimPlugins.coc-eslint
- vimPlugins.coc-go
- vimPlugins.coc-metals
- vimPlugins.coc-prettier
- vimPlugins.coc-stylelint
- vimPlugins.coc-tslint
- vimPlugins.coc-vetur
- vimPlugins.coc-yaml
- wasm-text-gen
- yaml-language-server

I tried bitwarden-cli and lessc binaries, and the both display help messages.

@cideM Any reason you see not to merge now?

I tried building all packages on my Macbook and makam fails with `attribute 'glibc' is missing. Comes from
    makam =  super.makam.override {
      buildInputs = [ pkgs.nodejs pkgs.makeWrapper ];
      postFixup = ''
        wrapProgram "$out/bin/makam" --prefix PATH : ${stdenv.lib.makeBinPath [ pkgs.nodejs ]}
        patchelf --set-interpreter ${stdenv.glibc}/lib/ld-linux-x86-64.so.2 "$out/lib/node_modules/makam/makam-bin-linux64"
      '';
    };

I'll have to look into the proper Darwin replacement for glibc

I made a change to the makam package. I simply wrapped the patchelf call in a condition so it only runs when we're on linux. The reason for this is that otool -L ./result/lib/node_modules/makam/makam-bin-darwin64 only turns up libSystem. I know more or less nothing about how dynamic linking works on MacOS but I guess the patchelf call here is really only necessary on Linux.
I can run makam so it outputs help text. So from my side this is now good to merge @ryantm


Compiled from sources... openFPGALoader sometimes reports errors

hi,
Compiled from sources... sometimes reports errors
SDK 1.5.1 default configuration BOARD_TYPE BOARD PICO  USB_CDC_UART_BRIDGE  0
root@cnc-centrum:~/pico-dirtyJtag/build# openFPGALoader --cable dirtyJtag --detect
Jtag frequency : requested 6000000Hz -> real 6000000Hz
JTAG init failed with: Unknown device with IDCODE: 0xa0811043 (manufacturer: 0x021 (lattice), part: 0x04 vers: 0xa
root@cnc-centrum:~/pico-dirtyJtag/build# openFPGALoader --cable dirtyJtag --detect
Jtag frequency : requested 6000000Hz -> real 6000000Hz
JTAG init failed with: Unknown device with IDCODE: 0xf0001043 (manufacturer: 0x021 (lattice), part: 0x00 vers: 0xf
root@cnc-centrum:~/pico-dirtyJtag/build# openFPGALoader --cable dirtyJtag --detect
Jtag frequency : requested 6000000Hz -> real 6000000Hz
JTAG init failed with: Unknown device with IDCODE: 0xf8000043 (manufacturer: 0x021 (lattice), part: 0x40 vers: 0xf
root@cnc-centrum:~/pico-dirtyJtag/build# openFPGALoader --cable dirtyJtag --detect
Jtag frequency : requested 6000000Hz -> real 6000000Hz
index 0:
idcode 0x1111043
manufacturer lattice
family ECP5
model  LFE5UM-25
irlength 8

This generally indicates that the connection between the pico and the FPGA isn't good enough to run at the JTAG frequency chosen. I have had good luck with braiding additional ground wires with the JTAG signals.

From: Grzegorz @.>
Sent: Sunday, October 15, 2023 1:07 PM
To: phdussud/pico-dirtyJtag @.>
Cc: Subscribed @.***>
Subject: [phdussud/pico-dirtyJtag] Compiled from sources... openFPGALoader sometimes reports errors (Issue #17)
hi,
Compiled from sources... sometimes reports errors
SDK 1.5.1 default configuration BOARD_TYPE BOARD PICO USB_CDC_UART_BRIDGE 0
@.:/pico-dirtyJtag/build# openFPGALoader --cable dirtyJtag --detect
Jtag frequency : requested 6000000Hz -> real 6000000Hz
JTAG init failed with: Unknown device with IDCODE: 0xa0811043 (manufacturer: 0x021 (lattice), part: 0x04 vers: 0xa
@.:/pico-dirtyJtag/build# openFPGALoader --cable dirtyJtag --detect
Jtag frequency : requested 6000000Hz -> real 6000000Hz
JTAG init failed with: Unknown device with IDCODE: 0xf0001043 (manufacturer: 0x021 (lattice), part: 0x00 vers: 0xf
@.:/pico-dirtyJtag/build# openFPGALoader --cable dirtyJtag --detect
Jtag frequency : requested 6000000Hz -> real 6000000Hz
JTAG init failed with: Unknown device with IDCODE: 0xf8000043 (manufacturer: 0x021 (lattice), part: 0x40 vers: 0xf
@.:/pico-dirtyJtag/build# openFPGALoader --cable dirtyJtag --detect
Jtag frequency : requested 6000000Hz -> real 6000000Hz
index 0:
idcode 0x1111043
manufacturer lattice
family ECP5
model LFE5UM-25
irlength 8
—
Reply to this email directly, view it on GitHubhttps://github.com/phdussud/pico-dirtyJtag/issues/17, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABVQKX5XDAVDYDXTK46PB23X7Q7BHANCNFSM6AAAAAA6BHKU2Y.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

thx..  it started working properly, it's possible that there was a problem with the connecting cables... best regards

closing this one


AScom cannot import bundled assets on legacy circumstances

Please verify the version of wc-generator you have installed
3.1.2
Please describe the bug
Anil Krishna is looking to import the auro-datepicker into the homelet on the AScom homepage.
He has added the following lines to AScom:
<script src="[https://unpkg.com/@('@')aurodesignsystem/auro-combobox@latest/dist/auro-combobox__bundled.js"](https://unpkg.com/@(%27<EMAIL_ADDRESS>type="module"></script>
<script src="[https://unpkg.com/@('@')aurodesignsystem/auro-datepicker@2.0.0/dist/auro-datepicker__bundled.js"](https://unpkg.com/@(%27<EMAIL_ADDRESS>type="module"></script>
<script src="[https://unpkg.com/@('@')alaskaairux/auro-icon@latest/dist/auro-icon__bundled.js"](https://unpkg.com/@(%27<EMAIL_ADDRESS>type="module"></script>
<script src="[https://unpkg.com/@('@')aurodesignsystem/auro-calendar@latest/dist/auro-calendar__bundled.js"](https://unpkg.com/@(%27<EMAIL_ADDRESS>type="module"></script>

        <script src="[https://unpkg.com/@('@')alaskaairux/auro-button@latest/dist/auro-button__bundled.js"](https://unpkg.com/@(%27<EMAIL_ADDRESS>type="module"></script>
<script src="[https://unpkg.com/@('@')aurodesignsystem/auro-dropdown@latest/dist/auro-dropdown__bundled.js"](https://unpkg.com/@(%27<EMAIL_ADDRESS>type="module"></script>
<script src="[https://unpkg.com/@('@')aurodesignsystem/auro-input@latest/dist/auro-input__bundled.js"](https://unpkg.com/@(%27<EMAIL_ADDRESS>type="module"></script>

This results in none of the unpkg-imported components to be registered to the customElements registry.

Reproducing the error
This issue cannot be reproduced on the Auro docsite
Expected behavior
Expected behavior: running customElements.get('auro-calendar') and all other unpkg-imported components from the homelet returns a valid component function. Currently, it returns undefined and elements cannot be used in the experience.
What browsers are you seeing the problem on?
Firefox, Chrome, Safari, Microsoft Edge
Additional context
Please contact @anikris1 for more details.
Exit criteria
Homelet can use the calendar and combobox.

thanks @gusnaughton  please let me know if there are further comments on this. thanks.

@anikris1 I need help understanding a few things here. This reference...
<script src="[https://unpkg.com/@('@')aurodesignsystem/auro-combobox@latest/dist/auro-combobox__bundled.js"](https://unpkg.com/@(%27<EMAIL_ADDRESS>type="module"></script>

Why all the extraneous characters? /@('@') and @(%27@%27)?
The new recommended CDN reference should be using //cdn.jsdelivr.net/npm/ not unpkg.com. We've had performance issues with unpkg.
Also, please DO NOT use @latest in the query from the CDN. There is a note about this in the example code.
<!-- **NOTE:** Be sure to replace `@latest` in the URL with the version of the asset you want. @latest is NOT aware of any MAJOR releases, use at your own risk. -->

I am moving this to auro-datepicker as it appears to be an issue with incorrect install instructions for the element, not a core issue with how elements are being created.


templatize viewer in a bunch of places

privacy policy. related https://github.com/lolopinto/ent/issues/619
builder?
ent

also templatize Viewer interface for nullable vs not viewerID and viewer methods


Out of date download page (link in readme)

The first item of the readmes' how to install section refers to manjaro-sway.download in order to find the latest images.
The page is not up to date and lists manjaro-sway-21.3.2-230116-linux515.iso as latest image.

My appologies, but I am quite puzzled. The one I mentioned is the latest release that is also listed here, but the file offered at manjaro.org/download corresponds to Manjaro-ARM-sway-generic-22.12.img.

My appologies, the one I mentioned is the latest release that is also listed here, but the file offered at manjaro.org/download corresponds to Manjaro-ARM-sway-generic-22.12.img.
22.12 vs. 21.3.2 caused the actual confusion on my side.

Manjaro still didn't update their version number inside lsb_releases, that's why our version is not updated still. perhaps @philmmanjaro wanted to look into it.
BUT: this repo is just for the x86 version of manjaro sway. For support regarding the ARM version, pls head over the manjaro forum.


ListView showing below error  while using inside AlertDialog

logs
elided 6 frames from class _AssertionError, class _RawReceivePortImpl, class _Timer, and dart:async-patch)
The following RenderObject was being processed when the exception was fired: RenderPositionedBox#33c00 NEEDS-LAYOUT NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
...  needs compositing
...  parentData: offset=Offset(40.0, 24.0) (can use size)
...  constraints: BoxConstraints(w=331.4, h=803.4)
...  size: Size(331.4, 803.4)
...  alignment: Alignment.center
...  textDirection: ltr
...  widthFactor: expand
...  heightFactor: expand
RenderObject: RenderPositionedBox#33c00 NEEDS-LAYOUT NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
  needs compositing
  parentData: offset=Offset(40.0, 24.0) (can use size)
  constraints: BoxConstraints(w=331.4, h=803.4)
  size: Size(331.4, 803.4)
  alignment: Alignment.center
  textDirection: ltr
  widthFactor: expand
  heightFactor: expand
...  child: RenderConstrainedBox#8d43e relayoutBoundary=up1 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
...    needs compositing
...    parentData: offset=Offset(0.0, 0.0) (can use size)
...    constraints: BoxConstraints(0.0<=w<=331.4, 0.0<=h<=803.4)
...    size: MISSING
...    additionalConstraints: BoxConstraints(280.0<=w<=Infinity, 0.0<=h<=Infinity)
...    child: RenderPhysicalShape#a4a65 relayoutBoundary=up2 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
...      needs compositing
...      parentData: <none> (can use size)
...      constraints: BoxConstraints(280.0<=w<=331.4, 0.0<=h<=803.4)
...      size: MISSING
...      elevation: 24.0
...      color: Color(0xffeeeeee)
...      shadowColor: Color(0xffeeeeee)
...      clipper: ShapeBorderClipper
...      child: RenderCustomPaint#69a37 relayoutBoundary=up3 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
...        needs compositing
...        parentData: <none> (can use size)
...        constraints: BoxConstraints(280.0<=w<=331.4, 0.0<=h<=803.4)
...        size: MISSING
...        painter: null
...        foregroundPainter: _ShapeBorderPainter#15329()
...        child: _RenderInkFeatures#d6f61 relayoutBoundary=up4 NEEDS-PAINT NEEDS-COMPOSITING-BITS-UPDATE
...          needs compositing
...          parentData: <none> (can use size)
...          constraints: BoxConstraints(280.0<=w<=331.4, 0.0<=h<=803.4)
...          size: MISSING
====================================================================================================

======== Exception caught by rendering library =====================================================
The following assertion was thrown during paint():
RenderBox was not laid out: RenderPhysicalShape#a4a65 relayoutBoundary=up2
'package:flutter/src/rendering/box.dart':
Failed assertion: line 2001 pos 12: 'hasSize'<details>

@nacpa
Can you provide flutter doctor -v and complete minimal reproducible code sample without any third party plugins that triggers the error you are reporting.

thanks  for your reply I  solve this issue,
the issue occurred bcz im not using Listview inside Contanier with some width.
now its working fine.
my  correct code is =>
ontap: () {
Get.defaultDialog(
title: "Select Member",
backgroundColor: Colors.grey.shade200,
radius: D.Hight10,
content: Container(
height: D.Hight100 * 6,
width: double.maxFinite,
child: ListView.builder(
itemCount: controller.Users_List!.length ?? 0,
itemBuilder: (__, i) {
return Container(
margin: EdgeInsets.all(D.Hight10),)

}


Update Workflows

Consistently use azure/powershell@v1 -- some were using specific old versions and some were getting the latest -- there was no particular reason for this

Consistently use actions/checkout@v4 -- some were using very old (v2), some were using specifically pinned (v3.5.2), and others a floating but outdated version (v3) -- there was no particular reason for this

Consistently use actions/setup-node@v4 -- some were using the original version (v1) and some the previous version (v3) -- there was no particular reason for this

Consistently use actions/github-script@v7 -- everyone was using a fairly old version (v3) -- the code here is simple and supported -- there's no reason not to use the current version (old versions will stop working as they rely on old versions of the actions runtime nodeX which are being discontinued incrementally)

Consistently use actions/stale@v8 -- two out of three were using an old version (v3) while one is actually already using the latest version!

Specify codql language as javascript  -- CodeQL complains that it can't auto-detect TypeScript, but it will work happily if you tell it that it's JavaScript

Name ci.yml -- Workflows should have names so they look pretty in https://github.com/Azure/login/actions

CodeQL does not need a special code -- CodeQL got smarter and doesn't need special code for checkout

@jsoref, thanks for your contribution!


Port dependabot PR automerge from vip-go-crontab to Github Actions

Description
As per title, this PR ports the code from vip-go-crontab to something that GitHub Actions would like.
We use the hydrated Octokit from GitHub instead of raw REST APIs, and we use auto-merge instead so that we don't need additional permission for getting the list of checks that needs to pass before merging.

Should finally be ready now.

I'm currently unhappy with this PR.
This has a few more problems vs the one written for vip-go-crontab.

The auto-merge feature of GitHub has its caveats. We need to ensure we meet these conditions.

The target repository must have Allow auto-merge enabled in settings.
The pull request base must have a branch protection rule with at least one requirement enabled.
The pull request must be in a state where requirements have not yet been satisfied. If the pull request can already be merged, attempting to enable auto-merge will fail.

Point number 3 has been a really difficult condition to deal with. We have two choices.

Trust GitHub, and assume that pull requests that are mergeable === true or mergeable_state === 'clean' is the same statuses that auto-merge relies on for point number 3. If it is, skip enabling auto-merge and just merge it. I'm running a few tests to see what exactly is the definition of mergeable.
Use a Personal Access Token instead of GitHub Action's, then give Adminstration read-only permission to our action ( see vip-go-crontab's PR) and don't use auto-merge and instead, rely on our own checks to see whether it's merge-worthy or not.

Looks like the bug will happen if mergeable_state is clean.
mergeable remains true even while a check is running.

Coming back to this at the next interlude! :flying_saucer:

So turns out there is a way to fetch dependabot metadata! However it'll involve us going into their open source code, reverse engineer their not-documented-but-public API.
It's currently not useful for us though as we're getting the data from their body and I think they don't plan to change how the body looks any time soon.

It turns out dependabot doesn't have any special API - they're doing the same thing as we do, parsing the body apparently.

Should be ready now.
Tested scenarios:

It should not approve and merge/auto-merge MAJOR semver version regardless of test result.
It should approve and merge/auto-merge MINOR and PATCH semver version if test results pass.
It should not approve and merge/auto-merge any semver version if required tests do not pass.

I think I need to write tests though. Last time I'm not sure what to write tests for but now I do.

Looking good, I'll wait for the tests and the conflict to be resolved before reviewing more deeply

That's it, tests are in

Figure out why https://github.com/abdullah-kasim/github-ci-tester-demo/pulls is failing. Was the setup instructions wrong?

Also we need more logs on all the steps or it'd be hard to keep track of the PR it's trying to act on and so on.

We had a bug report from the previous version of dependabot PRs from Slack.

Ahmed S. Wasif
:first_quarter_moon:  7 minutes ago
@abdullah
With that in mind - I wonder  if the dependabot auto-merge thing is too risky. Because the PR got auto-merged after I rebased it.

With this in mind, this PR also needs a detection mechanism to detect if someone has messed with the PR. Which in that case, the auto-merge routine must always ignore this PR.
It also means that enabling auto-merge might not the best thing to do. This needs some checking though.

There was an incident recently where this PR accidentally got merged:
https://github.com/Automattic/vip-go-api-public/pull/1753 despite there being no intention in doing so because automerge was enabled and the tests passed after a force-push occured.
I think for maximum control, we really don't want to use the 'enable auto merge' feature that GitHub has.

At this point I'm starting to wonder why we stick with dependabot in the first place. Renovatebot is a lot cooler, it could run automerge on a different day than the day the pull request is opened, so you could have dependabot open the PR on Wednesday but have it merge on Tuesday next week. Also supports a whole bunch of languages, and able to set whether to merge minor or major versions and so on, able to ignore specifically any version that matches your regex i.e. you don't like patch version 0, for example as it's usually riddled with bugs.
And it can also do security updates.
All configurable.

@abdullah-kasim Some previous discussion:
https://vipengineeringp2.wordpress.com/2022/04/14/thoughts-on-dependabot-renovate/


Introduce PermitCycles() option and don't permit cycles in AddEdge for acyclic graphs by default

At the moment, if the graph has been created with the Acyclic() option, AddEdge will return an error if a cycle would be introduced.
This behavior should be transferred to a new PermitCycles option: A graph created using Acyclic() should still allow the introduction of cycles in AddEdge, and only if the creation of cycles has been explicitly permitted using PermitCycles(), AddEdge should return an error.
Why?
There are two reasons for this:

The cycle check is an O(n) operation. Running an O(n) operation in AddEdge in the background might be an unexpected behavior for the user, who probably assumes that AddEdge is a O(1) operation (which it should be).
There are scenarios where you have an acyclic graph but still want to maintain and allow temporary cycles for an indefinite period, and delay the cycle checks.

This change is part of release 0.12.0.


Can i subtract moment from moment

i have, for example: moment('2000-12-01') and moment('2015-09-01')
i want calc difference in months
thank you!

@a-x- There is a lot of questions & answers on this topic on SO http://stackoverflow.com/search?q=[momentjs]+diff

var a = moment('2000-12-01');
var b = moment('2015-09-01');
b.diff(a, 'months') // 177


Cannot delete 2 areas in a row

Description
Provide a clear and concise description of the issue.
Steps to Reproduce
Steps to reproduce the behavior:

Go to whatever managed study that contains at least 2 areas, on a variant
Click on an area, remove it
Click on another area, remove it
See error

Status : 417
Exception : VariantGenerationError
Description :
Error while generating 440f95c0-1693-4aea-8c56-afce8cee9505

Possible Solution
If you have a solution in mind, describe it here.
Environment

[ ] Production
[X] Staging

Additional Information
After closing the variant, and opening it again, the following error appears

Add any other context about the problem here.

If applicable, provide the study ID that this issue relates to: 40f95c0-1693-4aea-8c56-afce8cee9505
Any relevant logs or error messages: NONE
Any relevant code snippets: NONE
Any relevant library versions: NONE
The date and time when the issue occurred: 15/07/2024
Browser and version: Firefox 107.0
Operating System: Ubuntu 20.04

I did not finish the investigation but the bug can be reproduced by removing only one area.


Glottolog mappings

I would suggest linking Chinbon to chin1478 / cnb and leave Nyhmoye unmapped (similarly to STEDT).

Another issue concerns Daai and Mkaang: both are mapped to daai1236, most likely because one of the alternative names of Daai is M'kaang. However, the lists differ a lot (compare Daai and Mkaang). Unfortunately, I don't have access to the original paper, so I might only suggest that Mkaang is Lamkang.

Since khum1250 is a bookkeeping entry, Wakung should probably be re-mapped to mroc1235.

Okay, I think this is reasonable. Linking just followed stedt mostly, and they give the same iso-code for daai and mkaang. But re-linking it is probably useful, specifically as long as we lack the original source.

Done in https://github.com/lexibank/sohartmannchin/commit/b97246e4b13f9764431698a73feac08123958e9e.


How to hide a specific notification banner when application is in killed state

In my project Pushy used to handle Firebase push notification. Now a requirement is that. Not to show notification banner when Application is in killed state or application is in background state.

I am able to handle this when application is in foreground.

func notificationWillPresent(userInfo: [String: Any], completionHandler: ((UNNotificationPresentationOptions) -> Void)?) {
 let remoteNotification = RemoteNotificationModel(userInfo)
completionHandler?([.sound])
}

But I want this same when app is in background or in killed state.

Hi @kumarlav0,
Thanks for reaching out. We'd be glad to assist.
Unfortunately, it is not possible to execute custom code in the background (for example, to update local SQLite data) without displaying a notification when your app is in the background/killed state on iOS.
As per the Apple docs:

Notification service app extensions only operate on remote notifications configured in the system to display an alert to the user. If alerts are disabled for your app, or if the payload specifies only the playing of a sound or the badging of an icon, the extension isn’t employed.

However, you can use the content_available: true flag to specify that the notification should be a silent one (no visible alert but you can still execute code). It won't be delivered when the app is killed, but it will be delivered if the app is running in the background/foreground. In that case, you can check the app background/foreground state and act accordingly to display a notification or not within your Pushy.setNotificationHandler():
let state = UIApplication.shared.applicationState
if state == .background || state == .inactive {
    // background
} else if state == .active {
    // foreground, generate a local notification
}

This requires the Background Modes -> Remote Notifications capability to be enabled.
Please let us know if there's anything else we can help with.


Files cannot be synchronized automatically

The editor will not automatically refresh synchronization after deleting files or modifying file names

What do you mean by synchronization? Can you explain better what your issue is?


Replace deprecated methods

Replaces deprecated methods with new calls. Tested until Go 1.9.2
Includes feedback on #27 to use the log package and output to stderr instead of to a file.
Except for requiring Go > 1.6, the changes are backwards compatible in the sense that any previous use case of teeproxy still works.
This PR prepares several other extensions (more control on connection handling, teeproxy acting as opaque proxy) which I'd like to add in separate PRs.

Thanks!


Switch to single container by default

Change pushed to the next major of the module. Refer to https://github.com/cyralinc/terraform-aws-sidecar-ec2/pull/118.


Test URLs

It might be a good idea to write a test that checks if the the URLs contained in the Notebooks are all working.

Somehow related to this:
My personal preference is that links that go to external sites should always open a new tab. Maybe it is possible to add this with sphinx?

closed by #32


Identifiers validation failed for dataset Fauna presente en los monitoreos de las fincas de Agropecuaria Aliar S.A.

Identifier validation failed for the dataset Fauna presente en los monitoreos de las fincas de Agropecuaria Aliar S.A.:

Crawler attempt: 114
Publishing organization: Agropecuaria Aliar S.A.
Publishing country: COLOMBIA
Installation: Datos sobre Biodiversidad de Colombia
Number of occurrences indexed for this dataset at the time of the issue: 287
Cause: GBIF ID problems exceed 50% threshold: 59% duplicates; 692 total records; 406 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3877443/step

New IDs sample:

LaFazenda:Fauna:0140
LaFazenda:Fauna:0262
LaFazenda:Fauna:0141
LaFazenda:Fauna:0263
LaFazenda:Fauna:0261
LaFazenda:Fauna:0268
LaFazenda:Fauna:0147
LaFazenda:Fauna:0266
LaFazenda:Fauna:0145
LaFazenda:Fauna:0267

Old IDs sample:

LaFazenda:Fauna:0255
LaFazenda:Fauna:0256
LaFazenda:Fauna:0257
LaFazenda:Fauna:0258
LaFazenda:Fauna:0259
LaFazenda:Fauna:0260
LaFazenda:Fauna:0261
LaFazenda:Fauna:0262
LaFazenda:Fauna:0263
LaFazenda:Fauna:0264

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Fauna presente en los monitoreos de las fincas de Agropecuaria Aliar S.A. : https://doi.org/10.15472/ohlqdy.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

We can proceed  indexing this dataset, we just added new records and it is flagged because there is more than 50% increase in the number of occurrences


fix: onboarding table widget is blank after adding binding

Description
For some reason the table widget content seems to have a display: none after updating the columnTypeMap property individually. Updating this along with other properties seems to fix this issue. Have updated the cypress test to check for visibility.
Minor: also updated the width of the columns of the table widget during onboarding.
Fixes #8275
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Cypress test updated to check for visibility of text
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
// Code coverage diff between base branch:release and head branch: fix/onboarding-table-content-invisible

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
app/client/src/sagas/OnboardingSagas.ts
17.05 (0.04)
1.33 (0)
11.11 (0)
17.42 (0.05)

/ok-to-test sha=ab7aff3


It seems my result is incorrect.

content img:

style img:

stylized img:

My command line is,
python run_styleid_diffusers.py --cnt horse.jpg --sty crystal_bunny.png

Hi,
we test your images with default settings and obtain the result as below.

My command line is,
python3 run_styleid_diffusers.py --sty_fn=crystal_bunny.png --cnt_fn=horse.jpg
but I additionally resize your images into the resolution of (512, 512).


Code clean up

Cleaning up code. Items to be sorted:

[x] Properties case classes encapsulated inside properties package
[x] AWS reading settings from LeaseProperties instead of config file
[ ] Ensure all variables use same naming convention as Nakadi, (i.e. event-type instead of topic)
[ ] Ensure event models are consistent with Nakadi API (such as Business event and Data changed event)
[ ] Rename namespace to org.zalando to be consistant with Sonatype namespace

Coverage decreased (-0.2%) to 55.877% when pulling e471c2c79419d25bb92d44c35b7b552e216035ee on code-cleanup into 4ec1ca24dfc7f011855dc54ba8b464fcf1e6ef17 on master.

Coverage decreased (-0.2%) to 55.877% when pulling e471c2c79419d25bb92d44c35b7b552e216035ee on code-cleanup into 4ec1ca24dfc7f011855dc54ba8b464fcf1e6ef17 on master.

Coverage decreased (-0.08%) to 55.978% when pulling ca7bb15d837add7dcda3917ec49692b0938d1b51 on code-cleanup into 4ec1ca24dfc7f011855dc54ba8b464fcf1e6ef17 on master.

Coverage decreased (-1.4%) to 54.662% when pulling 2b0542eabb27749b69803ac753e8fed391faa7d6 on code-cleanup into 4ec1ca24dfc7f011855dc54ba8b464fcf1e6ef17 on master.


Add code formatting integration to Elixir cells

Closes #296.
I figured out a way that should overcome the concerns I had with formatting and is actually pretty simple. There is a detailed comment in the code, but the important parts are:

user originates the formatting and it happens within editor as a regular edit (consequently it's a normal operation on the undo stack)
the formatting operation isn't a replace-all, but a set of operations that introduce the minimal diff, consequently the Delta sent from the client is reasonable, which should make conflict resolution work reliably if needed
formatting is only applied if the editor is intact, any change (remote or local) cancels the formatting, and that eliminates a whole category of conflicts

https://user-images.githubusercontent.com/17034772/124037620-20cb9480-da00-11eb-9380-d89861d634f8.mp4

@jonatanklosko it works for me on Mac


Added string compare test utility

I added string compare test utility ASSERT_STRSTR and ASSERT_NOT_STRSTR. I found it really usefull for testing json string output.
Enjoy!

There are some issues i see:

cointain -> contain
why do you check the combinations of hackstack + needle, where one can be NULL? Why not force both of them to be non-NULL?

There are some issues i see:

cointain -> contain
why do you check the combinations of hackstack + needle, where one can be NULL? Why not force both of them to be non-NULL?

 I fixed it so :
ASSERT_NOT_STRSTR(NULL, ""); => PASS
ASSERT_NOT_STRSTR("", NULL); => PASS
ASSERT_NOT_STRSTR(NULL, NULL); => PASS
ASSERT_STRSTR(NULL, ""); => FAIL
ASSERT_STRSTR("", NULL); => FAIL
ASSERT_STRSTR(NULL, NULL); => FAIL
Both ASSERT_NOT_STRSTR and ASSERT_STRSTR are bit ambiguous as one could argue that NULL does contain NULL.
Would you make a special case for those?


Kh bio in profile

just added bio to profile page and removed toasts from dashboard, profile, and profile edit. Also, the textareas in profile edit now have a character limit. These limits can be and maybe should be changed

Made a different branch that includes this one


Awsome

[Enter feedback here]

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

ID: 4200dd45-15ab-ee4a-9818-10cc81475f64
Version Independent ID: 0b96ac28-e2a2-41c9-eff0-efd864fc0529
Content: Key influencers visualizations tutorial - Power BI
Content Source: powerbi-docs/visuals/power-bi-visualization-influencers.md
Service: powerbi
Sub-service: powerbi-ai
GitHub Login: @aphilip94
Microsoft Alias: anphil

Thanks for your comment, @svsuma. This issue has been assigned to the doc author for review.

Thanks for the feedback! I'll let the author know.


is it too much of me to ask for an MPI option like llama.cpp?

i was always looking for the optimum (cheapest) way to run the large models.
kind of tired of going for the extremes. (coz i will need to "upgrade" and that means my other devices are "obsolete")
however, is an MPI option in the roadmap? would really hope to see it happen.
Thx in advance for the great work by the way.

I don't know, ExLlama is really focused on consumer GPUs. This would be asking for a complete rewrite so it can run on clusters of embedded devices instead. And it basically boils down to "can this project be llama.cpp instead?" So, I don't really think this is realistic.
As for the name, I didn't really give it much thought. Doesn't have those connotations to me, is all I can say I guess. Think of it as "extra" maybe?
And it's not categorically the fastest way to run Llama, either. It really depends on the use case.

@turboderp

basically running solely on gpu vram is fine but ability to distribute task as "clusterized" form (on consumer gpu etc).

the speed improvement is kind of evident for long running processes. i just saw v2 and extremely impress with the direction and performance optimized! do pls consider mpi (gpu only) as part of the roadmap.

what's the fastest way to run llama for consumer then? i thought most benchmark say exllama is the way to go.

p.s. : v2 is impressive. u guys are doing great.

what's the fastest way to run llama for consumer then? i thought most benchmark say exllama is the way to go.

Benchmarks tend to become outdated very quickly. When ExLlama first came out there was no CUDA support at all in llama.cpp at all, for instance, AutoGPTQ didn't exist and GPTQ-for-Llama was still using essentially the same kernel written for the original GPTQ paper. Since then, llama.cpp has had a huge amount of work put into it, AutoGPTQ has included the ExLlama (v1) kernel, and there's also AWQ, vLLM... something called OmniQuant..?
ExLlama is definitely a fast option, and depending on what you need to do, what your hardware setup is, etc., it may be the fastest in your case. If you want to run an inference server for an online chat service, probably you should look at TGI or vLLM or something. If you want to run on Apple Silicon, llama.cpp is (I think?) the only way to go. If you have an older NVIDIA GPU (Pascal or earlier), AutoGPTQ is probably still the best option. So it all depends.


Ensure it's possible to compile this crate with the stable compiler

Hmm it looks like Github included all of my later commits into this PR. I originally only meant to submit until 4598eea.
Let me know if you don't want some of the other changes, I can split this PR up again.

Thanks Karel. I added a commit to update the code with the new Direction::ALL and Piece::ALL constants. Changes are published to crates.io as "1.0.1".

Thanks a lot! Looks like Direction::ALL and Piece::ALL are even more useful than I thought!


Upgrade Jquery to 3.5.0

CVE-2020-11022
In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
Could you update werkzeug to use latest version of Jquery -3.5.1 or 3.5.0

Please send a PR.
Considering that the only place werkzeug uses jQuery is in the interactive debugger, a tool that lets you run arbitrary python code on the server, a potential XSS vulnerability exploitable by highly trusted users would not really be a problem - even if werkzeug did use the parts of jQuery that have the XSS issue, which I'm pretty sure it doesn't.

created a PR https://github.com/pallets/werkzeug/pull/1803,
Please check and approve it.

When is Werkzeug version 1.0.2 will be released as "CVE-2020-11022" is holding its adoption for one of our customers.
Thanks for all the good work.


Production Release - October 30 / 2024

This is for a production release. Stories that should be included:

#2175
#1207
#1978
#2108
#2162
#1973
#2103
#2177

:tada: This PR is included in version 1.28.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 5.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 5.0.0-alpha.12 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.0.0-alpha.9 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.2.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add DeleteInsuranceCommandParserTest.java

Currently, we have no tests for DeleteInsuranceCommandParser.
Let's add tests for DeleteInsuranceCommandParser to increase our test coverage.

Fixes #125


How to use a locally downloaded version of an NLP engine

I cannot use live http connection to download models directly by python due to a firewall.
However, I have downloaded "en_core_web_sm" in a local folder and
nlp = spacy.load('/en_core_web_sm/en_core_web_sm-3.5.0/') successfully loads the model.
Now how to use this in the following functions
TransformersNlpEngine, AnalyzerEngine
Thanks!

Are you interested in using the en_core_web_sm model, or a huggingface model?
In both cases, if you pre-downloaded the models, they should be installed without going online. Could you please provide more information if that's not the case?
On how to use the following functions, please see this doc: https://microsoft.github.io/presidio/analyzer/nlp_engines/transformers/#creating-a-configuration-file
Alternatively, if you prefer to configure it via code:
from presidio_analyzer import AnalyzerEngine, RecognizerRegistry
from presidio_analyzer.nlp_engine import NlpEngineProvider

# Configure which spacy and huggingface models you'd like to use
configuration = {
    "nlp_engine_name": "transformers",
    "models": [{
                    "lang_code": "en",
                    "model_name": {
                        "spacy": "en_core_web_sm",
                        "transformers": "StanfordAIMI/stanford-deidentifier-base",
                    },
                }],
}

# Note that additional configuration for things like entity mapping and more should be passed. Here we use the default

# create nlp_engine
provider = NlpEngineProvider(nlp_configuration = configuration)
nlp_engine = provider.create_engine()

# Use Presidio Analyzer
analyzer = AnalyzerEngine(nlp_engine=nlp_engine)
analyzer.analyze(...)

Thanks @omri374. I am interested to use "en_core_web_sm".
I cannot use the following due to a firewall and get http connection error
python -m spacy download en_core_web_sm
As I mentioned, I have downloaded it in a local folder  c:/en_core_web_sm/en_core_web_sm-3.5.0/
My question is how to give the location of the downloaded model to the code?
should I change the configuration like this:
configuration = {
"nlp_engine_name": "spacy",
"models": [{
"lang_code": "en",
"model_name": {
"spacy": "c:/en_core_web_sm/en_core_web_sm-3.5.0/",
"transformers": "StanfordAIMI/stanford-deidentifier-base",
},
}],
}
I did and it raised a ValueError: model_name must be a string

Hi, you are providing a transformers configuration (which is a spaCy pipeline with a transformers model in it) instead of a spacy configuration. For spacy, model_name should be the path to the model, not a dictionary.

Another option would be to load the model directly using spacy this way: https://microsoft.github.io/presidio/analyzer/nlp_engines/spacy_stanza/#using-a-previously-loaded-spacy-pipeline

Hi, you can use the following way as well.
from presidio_analyzer import AnalyzerEngine
from presidio_anonymizer import AnonymizerEngine
from presidio_analyzer.nlp_engine import SpacyNlpEngine
import spacy
text="Pls activate following login for portal my number is<PHONE_NUMBER>8"

class LoadedSpacyNlpEngine(SpacyNlpEngine):
    def __init__(self, loaded_spacy_model):
        self.nlp = {"en": loaded_spacy_model}

nlp = spacy.load(r"C:/Tasks/PIIFilter/Experiments/SpacyTrainedModel/model-best")

loaded_nlp_engine = LoadedSpacyNlpEngine(loaded_spacy_model = nlp)
analyzer = AnalyzerEngine(nlp_engine = loaded_nlp_engine)

# Call analyzer to get results
results = analyzer.analyze(text=text,
                           entities=["PERSON","PHONE_NUMBER","EMAIL_ADDRESS","IP_ADDRESS","US_SSN","UserId","Password"],
                           language='en')
print(results)

anonymizer = AnonymizerEngine()
anonymized_text = anonymizer.anonymize(text=text,analyzer_results=results)
print(anonymized_text)

Another option would be to load the model directly using spacy this way: https://microsoft.github.io/presidio/analyzer/nlp_engines/spacy_stanza/#using-a-previously-loaded-spacy-pipeline

Thanks @omri374
I get this error now:

Hi,
There might be two reasons for this
-> You might have downloaded wrong spacy model or the model which doesn't support ner or not giving the path of spacy where it couldn't find the config file.
Steps:
-> Go to the following official link - https://github.com/explosion/spacy-models/releases?q=en_core_web_sm-3.5.0&expanded=true
-> Download the tar file and extract the same.
-> Now while specifying the path make sure that you are giving the path till it can detect the config file. For example - D:/Experiment/en_core_web_sm-3.5.0/en_core_web_sm-3.5.0/en_core_web_sm/en_core_web_sm-3.5.0. Make sure that in this directory config file present.
-> Now use the same code and it will work.
from presidio_anonymizer import AnonymizerEngine
from presidio_analyzer.nlp_engine import SpacyNlpEngine
import spacy
text="Pls activate my number is<PHONE_NUMBER>8"

class LoadedSpacyNlpEngine(SpacyNlpEngine):
    def __init__(self, loaded_spacy_model):
        self.nlp = {"en": loaded_spacy_model}

nlp = spacy.load("D:Experiment/en_core_web_sm-3.5.0/en_core_web_sm-3.5.0/en_core_web_sm/en_core_web_sm-3.5.0")

loaded_nlp_engine = LoadedSpacyNlpEngine(loaded_spacy_model = nlp)
analyzer = AnalyzerEngine(nlp_engine = loaded_nlp_engine)

# Call analyzer to get results
results = analyzer.analyze(text=text,
                           entities=["PERSON","PHONE_NUMBER","EMAIL_ADDRESS","IP_ADDRESS","US_SSN","UserId","Password"],
                           language='en')
print(results)

anonymizer = AnonymizerEngine()
anonymized_text = anonymizer.anonymize(text=text,analyzer_results=results)
print(anonymized_text)```

Hi,
You can refer below code for reference.
from presidio_analyzer import AnalyzerEngine
from presidio_anonymizer import AnonymizerEngine
from presidio_analyzer.nlp_engine import SpacyNlpEngine, NerModelConfiguration
import spacy

text="Pls activate my number is<PHONE_NUMBER>8"

ner_model_config = NerModelConfiguration(
    model_to_presidio_entity_mapping={
    "PERSON":"PERSON",
    "LOC":"LOCATION"
    }
)

class LoadedSpacyNlpEngine(SpacyNlpEngine):
    def __init__(self, loaded_spacy_model, ner_model_configuration):
        self.nlp = {"en": loaded_spacy_model}
        self.ner_model_configuration = ner_model_configuration

nlp = spacy.load("/content/en_core_web_sm-3.5.0/en_core_web_sm/en_core_web_sm-3.5.0")

loaded_nlp_engine = LoadedSpacyNlpEngine(loaded_spacy_model = nlp, ner_model_configuration = ner_model_config)
analyzer = AnalyzerEngine(nlp_engine = loaded_nlp_engine)

# Call analyzer to get results
results = analyzer.analyze(text=text,
                           language='en')
print(results)

anonymizer = AnonymizerEngine()
anonymized_text = anonymizer.anonymize(text=text,analyzer_results=results)
print(anonymized_text)```

Hi. there are still some occasions when presidio tries to access the inherent.
For example if i'm including an email address, and asking the analyzer to analyze it with a locally loaded Spacy model I'm getting the following warning. followed by HTTP max retries error:
unable to cache publicsuffix.org-tlds.{'urls': ('https://publicsuffix.org/list/public_suffix_list.dat', 'https://raw.githubusercontent.com/publicsuffix/list/master/public_suffix_list.dat'), 'fallback_to_snapshot': True} in /home/ssm-user/.cache/python-tldextract/3.8.10.final__usr__7d8fdf__tldextract-5.0.1/publicsuffix.org-tlds/de84b5ca2167d4c83e38fb162f2e8738.tldextract.json. This could refresh the Public Suffix List over HTTP every app startup. Construct your `TLDExtract` with a writable `cache_dir` or set `cache_dir=None` to silence this warning. [Errno 13] Permission denied: '/home/ssm-user/.cache

Hi, You can refer below code for reference.
from presidio_analyzer import AnalyzerEngine
from presidio_anonymizer import AnonymizerEngine
from presidio_analyzer.nlp_engine import SpacyNlpEngine, NerModelConfiguration
import spacy

text="Pls activate my number is<PHONE_NUMBER>8"

ner_model_config = NerModelConfiguration(
    model_to_presidio_entity_mapping={
    "PERSON":"PERSON",
    "LOC":"LOCATION"
    }
)

class LoadedSpacyNlpEngine(SpacyNlpEngine):
    def __init__(self, loaded_spacy_model, ner_model_configuration):
        self.nlp = {"en": loaded_spacy_model}
        self.ner_model_configuration = ner_model_configuration

nlp = spacy.load("/content/en_core_web_sm-3.5.0/en_core_web_sm/en_core_web_sm-3.5.0")

loaded_nlp_engine = LoadedSpacyNlpEngine(loaded_spacy_model = nlp, ner_model_configuration = ner_model_config)
analyzer = AnalyzerEngine(nlp_engine = loaded_nlp_engine)

# Call analyzer to get results
results = analyzer.analyze(text=text,
                           language='en')
print(results)

anonymizer = AnonymizerEngine()
anonymized_text = anonymizer.anonymize(text=text,analyzer_results=results)
print(anonymized_text)

This solved the issue thank you very much for the help @VMD7


Clean and expand calibration system set up

These are some minor changes to the functions to set up calibration systems. It adds tests for the function that previously was not being tested. It also adds a feature for setting the box size, which previously was hard-coded. This should make it easier to study the effect of the box size.

Codecov Report

Merging #125 into master will decrease coverage by 0.01%.
The diff coverage is 18.91%.

@@            Coverage Diff             @@
##           master     #125      +/-   ##
==========================================
- Coverage   59.83%   59.81%   -0.02%
==========================================
  Files          36       36
  Lines        5086     5092       +6
==========================================
+ Hits         3043     3046       +3
- Misses       2043     2046       +3

Impacted Files
Coverage Δ

protons/app/ligands.py
1.76% <0%> (-0.01%)
:arrow_down:

protons/tests/test_ligands.py
48.8% <36.84%> (+1.89%)
:arrow_up:

Continue to review full report at Codecov.

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


Unable to remove lambda execute permission to SNS event source

I am getting this recently. At least since 0.36.0.
Is there something I need to do to fix that?
Tammo
Scheduling..
ERROR:Unable to remove lambda execute permission to SNS event source
Traceback (most recent call last):
  File "/home/theeren/.virtualenvs/em30_lambdas/local/lib/python2.7/site-packages/kappa/event_source/sns.py", line 94, in remove
    StatementId=function.name+'_'+self._context.environment)
AttributeError: 'PseudoContext' object has no attribute 'environment'
Removed event app.lambda_handler.
ERROR:Error adding lambdaInvoke permission to SNS event source
Traceback (most recent call last):
  File "/home/theeren/.virtualenvs/em30_lambdas/local/lib/python2.7/site-packages/kappa/event_source/sns.py", line 61, in add
    StatementId=function.name+'_'+self._context.environment,
AttributeError: 'PseudoContext' object has no attribute 'environment'
Created sns:Publish event schedule for app.lambda_handler!

What is your kappa version? We updated to 0.7.0, maybe your version in the venv isn't up to date?

you may also want to try 36.1

It happens with both 36.0 and 36.1. Kappa may not have updated to 0.7.0. I did try to update kappa but it said it was already on the latest version. Maybe it's to recent.

This seems to have got fixed with properly upgrading to kappa 0.7.0.


[Pager] Conflict Between Wear Compose Nav's SwipeDismissableNavHost and HorizontalPager

Description
If we use HorizontalPager() in a Wear OS app, it works fine, with one notable exception: if you navigate to a destination that has the pager, SwipeDismissableNavHost no longer lets you navigate back when you get to the left-most page.
Steps to reproduce
Run the attached project on a Wear OS 2 or Wear OS 3 device:
WearPagerNav-20220206.zip
This app launches into a two-page HorizontalPager(), containing a "Simple Content" and a "Second Pager" button.
Expected/actual behavior
If you run the app, then swipe back, you exit the app as expected:
https://user-images.githubusercontent.com/103772/152697934-f42d0e71-6d84-4b04-b6e2-a3a2ed9abb1f.mp4
If you run the app, then tap the "Simple Content" button on the first page, the button uses Wear Compose Navigation to display some text. Swiping back returns you to the original content:
https://user-images.githubusercontent.com/103772/152697972-5c464b55-46e8-407b-b497-b32b99d60365.mp4
If you run the app, then swipe to the second page and click the "Second Pager" button, the button uses Wear Compose Navigation to display another HorizontalPager(). If you swipe around that pager and attempt to swipe back to the previous content, it does not work. In principle, this should work the same way that it does for the simple text content.
https://user-images.githubusercontent.com/103772/152698014-c7b968f0-9638-4dbf-9746-aa9137be89e0.mp4
FWIW, these screencasts are recorded off of a Samsung Galaxy Watch4 using scrcpy.
Additional context
The project is using 0.22.0-rc of Accompanist Pager, 1.1.0-rc03 of Compose, and 1.0.0-alpha15 of Wear Compose Navigation.
Let me know if you need additional information, and thanks for everything with Accompanist!

Thanks for filing the bug.
The issue is that SwipeDismissableNavHost doesn't work via nested scroll mechanism yet so this could work better together. We filed a bug in the wear bug tracker - https://issuetracker.google.com/issues/218663790

I could not tell where the problem stemmed from, so I am glad that you determined the source of the difficulty. Thanks for your help!


Bump required version to 3.9 and add it to bazel

This bumps the required version to 3.9 which is what our codebase currently requires. It also adds a bazel rule to install a hermetic python 3.9 package. This will make bazel always use the hermetic package which should avoid backwards compatibility issues in the future.
Fixes #136

FYI @AaronWebster @robrussell

@reventlov fyi if you have an opinion

@reventlov fyi if you have an opinion

No strong opinion.  Scoping to tests only would use fewer system resources while compiling, but leave the open possibility of things breaking if an end user has Python 3.8 (or earlier) as their system Python 3.

As I just discovered in #167, this is insufficient to fix the issue as currently 3.9 is also failing. I confirmed on all other supported Python versions and it works fine, but it is failing on both 3.8 and 3.9.

This should "fix" the 3.8 issues and highlight failures on 3.9 so that we prevent future regressions right? Ofc it's already regressed, but once that's fixed it should do the job right?

Yeah, I didn't word that well, I meant without fixing 3.9 first.

Would it be possible to rebase this on #163 and do this or something similar to this in the MODULE.bazel file instead of WORKSPACE? That way we can land #163 and this without conflict.

Im fine landing #163 and breaking this PR. I'll be out a few weeks so if
you want to land a reworked version that's fine with me and we can just
abandon this one.
On Fri, Aug 9, 2024, 12:59 PM Jason Graffius @.***>
wrote:

Would it be possible to rebase this on #163
https://github.com/google/emboss/pull/163 and do this or something
similar to this in the MODULE.bazel file instead of WORKSPACE? That way
we can land #163 https://github.com/google/emboss/pull/163 and this
without conflict.
—
Reply to this email directly, view it on GitHub
https://github.com/google/emboss/pull/137#issuecomment-2278652195, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADIHJ6CEP2L27Q3X4F5LSLZQUNRDAVCNFSM6AAAAABGOCF5WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYGY2TEMJZGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Missing documentation of API versions suggested by Bicep for Microsoft.Storage/storageAccounts

Bicep version
v0.29.47
Describe the bug
When authoring a template in the VSCode bicep suggest two newer API versions for Microsoft.Storage/storageAccounts which no documentation exists at https://learn.microsoft.com/en-us/azure/templates/microsoft.storage/change-log/storageaccounts

For example, the version 2023-05-01 has a new value (TLS1_3) for minimumTlsVersion which is not documented. TLS1_3 is also not selectable in the Azure Portal. So, it is quite confusing if the option or even the API version should be used already or not.

@tfitzmac is this something you can take a look at?


Add asynchronous  frontend

Including tests and a change to CI (to not only test, but also try to build the package)

Coverage increased (+0.5%) to 97.311% when pulling 85ed3f7363d4f260f9e49faeff34f24b114b91d9 on async-frontend into b158dd305ef2892775d8b40908e3af2d160d6a1d on main.


Test if config samples are valid trough StyleCI API

See comment: https://github.com/Soullivaneuh/php-cs-fixer-styleci-bridge/pull/67#issuecomment-225041948

@GrahamCampbell about this, not sure this is the place for your API but it would be great to be able to download a config reference of .styleci.yml file with all the possible keywords.
Because the current problem is: If you add a config keyword, the bridge will throw an error because it does not know this one.
If I can integrate the config reference under the tests, I'll be warned of the issue very quickly thanks to Travis.
What do you think?

I think there is one in the docs.

Yeah... but I was thinking about something more... automatic? :-)


Font sizes on HTN page

Body text and Need to Know text are larger than Answer Section text - Unclear etiology

On 12/4/22 I no longer see this issue. Don't know what happened.


Token validation options

What issue does this PR address?
#4965 - Multiple valid issuers
Does this PR introduce a breaking change?
NO

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

Thanks for your contribution!
IdentityServer4 is feature complete.
All new feature work will happen in our new organization. The new Duende IdentityServer is available under both a FOSS (RPL) and a commercial license. Development and testing is always free. Contact us for more information.
This repo will be maintained with bug fixes and security updates until November 2022.

That being said, you can implement this feature yourself using our standard extensibility - so you have a workaround.

Can you advise me how to extend it? The TokenValidator is internal and there's no option to change the TokenValidationParameters:
            var parameters = new TokenValidationParameters
            {
                ValidIssuer = _context.HttpContext.GetIdentityServerIssuerUri(),
                IssuerSigningKeys = validationKeys.Select(k => k.Key),
                ValidateLifetime = validateLifetime
            };

The only option is to write completely custom implementation of the ITokenValidator which is in general not a good idea.

Hm - OK - then I am wrong. Need to discuss this.


Correct deprecated link

Actual link yield a 404.

Moved to https://github.com/awesomedata/apd-core/pull/272


ng serve hangs at 70%

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Windows 10
Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

$ ng --version
angular-cli: local (v1.0.0-beta.23, branch: master)
node: 6.9.2
os: win32 x64

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

It was working fine in beta-21.
Latest version results in this error. I desperately need this version as I need the i18n features.
The log given by the failure.

Normally this include a stack trace and some more information.

$ ng serve
** NG Live Development Server is running on http://localhost:4200. **
 70% building modules 1290/1290 modules 0 active

Mention any other details that might be useful.
Another issue ( https://github.com/angular/angular-cli/issues/3508 ) with this problem was marked as duplicate of ( https://github.com/angular/angular-cli/issues/3368 ). That's not right. In my case, in beta-21 the application compiles fine in AOT. So, as since beta-22 AOT is enabled by default, it should also still work. So it may be an AOT issue, but by making AOT no longer default, this issue won't be fixed.
I am starting to lose confidence in Angular CLI. I am aware it's work in progress, but in every commit I get random errors. I've tried most of the commits since i18n was introduced, and every one gives a different error.
And the fact that .beta-22 introduced a major bug (AOT enabled by default) doesn't help either.
You're doing a great job, but keep in mind that people use this tool for production websites.

downgrading to @ngtools/webpack 1.1.9 solved for a while

In my case downgrading to tslint 4.0.2 solved the problem.

@antonybudianto7 and @schroedan ... didn't work for me :/

@donotfold have you cleaned your node_modules before re-installing?

Have the same issue.
I deleted node_modules
I linked angular-cli in my project to use the latest beta.23
And put @ngtools/webpack 1.1.9 in my package.json
Run npm install
Run ng init to re-initiate my project.
But ng serve stucks on 70%

btw I used beta.22-1, not beta.23, sorry forgot to mention it.

I have the same issue with beta.22-1

Having the same issue with beta.21. Tried rm -rf node_modules to no avail.

+1

@nikoTM It definitely has something to do with yarn; after rm -rf node_modules && npm install, I had to upgrade "@angular/compiler" and "@angular/core" from 2.0.0 to 2.2.3 in my package.json. Then, I had lots of warnings from npm but finally got ng serve to work. ;)

Looks like it's solved
https://github.com/webpack/webpack-dev-middleware/issues/156
cc @hansl

Right. The process now terminates instead. I just submitted a PR for a better error message and, in the case of watching (serve or build --watch), stay in process and watch file changes.

@hansl I've just tested in latest version, and it still hangs?
$ ng serve --aot --locale zh --i18nFormat xtb --i18nFile "./src/i18n/messages.zh.xtb" --live-reload-port 42000
** NG Live Development Server is running on http://localhost:4200. **
 69% building modules 579/580 modules 1 active ...o.Web.Client\Dev\src\client\src async

It just hangs there.
The output of build:
$ ng build --aot --locale zh --i18nFormat xtb --i18nFile "./src/i18n/messages.zh.xtb"
 69% building modules 503/504 modules 1 active ...o.Web.Client\Dev\src\client\src async

.. then it stops.

Fresh install of angular-cli@latest(1.0.0-beta.22-1) and ng serve is hanging on 70%

@Kosmonaft I've raised this issue on the master branch. So either revert to beta.21, or clone the repository and run from there.
I've confirmed that the bug has been resolved in master branch.

I got it compiling by changing the codelyzer to version 2, but I'm not sure this was the culprit.
angular 2.2.3
angular-cli beta 22-1
"codelyzer": "2.0.0-beta.1",

I think it's related with how yarn is resolving the dependencies. It looks like it's installing versions that have NOT been published on npm such us version 1.2.0 of @ngtools/webpack instead of the last published version (1.1.9) and the same thing happens with codelyzer
@ngtools/package in npm displaying 1.1.9 is the latest of 13 releases

@rolandoldengarm  I clone the repository and now I'm getting this error:
notarget No compatible version found<EMAIL_ADDRESS>My current version:
fatal: Not a git repository (or any of the parent directories): .git angular-cli: local (v1.0.0-beta.23, branch: ??) node: 6.9.1 os: win32 x64

Clone the repository into a folder
Go to that folder and run "npm link"
Go to your Angular 2 project, and run "npm link angular-cli"

Just as documented here: https://github.com/angular/angular-cli#development-hints-for-hacking-on-angular-cli
@Kosmonaft

I had the same issue after updating to<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>I got around the 70% build hang by downgrading to<EMAIL_ADDRESS>and installing<EMAIL_ADDRESS>as a dev dependency.

Workaround:

ng build
ng server

For me in this way is working

I had this issue when I tried to use cli with angular 2. Then I switched to angular-webpack-starter which worked fine. Now Im trying to upgrade my app to angular 5 I have this issue again. It just freezes on 76% forever without any errors or something on how I can fix this issue. When I configure my app from scratch using angular 5 and systemjs - it works fine.

@Kosmonaft Thank you!!! This issue took me like 12 hours. I tried absolutely everything to resolve it, but, to no avail, nothing worked.
ng build
ng server
That's all it took all along.

@Kosmonaft Thank you!!!! This issue took me nearly 16 hours to figure out. Needless to say, I tried nearly everything to resolve the issue, however, to no avail, nothing worked.
ng build
ng server
is all it took. Also, below are some of my versions:
Angular CLI: 1.7.4
Node: 6.9.2
OS: win32 x64
Angular: 5.2.11
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
@angular/cli: 1.7.4
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.0.29
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.4.2
webpack: 3.12.0
Another thing I should mention is that I had to downgrade the ngx-spinner module from the latest version to version 6.0.0.