Vulnerabilities CVE-2023-39325 , CVE-2023-3978 and  CVE-2023-44487 in Hoverfly v1.6.0

Description of the bug
@tommysitu - Hoverfly v1.6.0 has three vulnerabilities  CVE-2023-39325 , CVE-2023-3978 and CVE-2023-44487 with golang.org/x/net
Steps to reproduce the issue

CVE Details:  https://avd.aquasec.com/nvd/cve-2023-39325
https://avd.aquasec.com/nvd/cve-2023-3978
https://avd.aquasec.com/nvd/cve-2023-44487
Observed result
Hoverfly error messages seen (If none, say none)
(paste here)

If possible, add screenshots to help explain your problem
Expected result
Vulnerabilities have to be fixed
Additional relevant information

Hoverfly version: 1.6.0
Anything that might help us to diagnose the problem

Hi, it has been fixed here: https://github.com/SpectoLabs/hoverfly/pull/1102
I will try to get a release out asap 👌

@tommysitu  thank you

https://github.com/SpectoLabs/hoverfly/releases/tag/v1.6.1 should contain the fix


The communication between pods on the same edge node failed

What happened:
I deployed two deps on the same edge node, and tried to let them communicate with each other by calling service FQDN but failed;
I got

And the edgemesh on the edgenode would show SERVFAIL error

What you expected to happen:
The pods on the same edge node could communicate with each other;
How to reproduce it (as minimally and precisely as possible):
Just deploy two pods on the same edge node;
Anything else we need to know?:
I didn't switch on cloudcore dynamicController, does it matter?
Environment:

EdgeMesh version:
v1.13.0

Kubernetes version (use kubectl version):
v1.20.15

KubeEdge version(e.g. cloudcore --version and edgecore --version):
v1.13.0

Cloud nodes Environment:

Hardware configuration (e.g. lscpu):
OS (e.g. cat /etc/os-release):
Kernel (e.g. uname -a):
Go version (e.g. go version):
Others:

Edge nodes Environment:

edgecore version (e.g. edgecore --version):
v1.13.0
Hardware configuration (e.g. lscpu):
2g2u
OS (e.g. cat /etc/os-release):
Kernel (e.g. uname -a):
Go version (e.g. go version):
Others:

refer to https://edgemesh.netlify.app/guide/#prerequisites and https://edgemesh.netlify.app/guide/edge-kube-api.html

Thank you for your reply @Poorunga   Indeed I noticed that they might need some meta info from edge api-server. But I don't want to expose my cluster info( like services, namespaces etc) to edge node, any other way to enable apps on the same edge node to communicate with each other( instead of service, endpoint) ? Is it possible to achieve it with MQTT ?

When edgemesh is running, it must be connected to edge-api-server. And Edgemesh's domain name resolution needs to obtain metadata from edgecore's metaserver module, and the metaserver module needs to communicate with cloudcore's syncController module to obtain metadata, such as services and endpoints, etc., edgemesh needs to consume these metadata to provide normal domain name resolution function.

Thank you @Poorunga . That's exactly wat I saw. However due to my personal requirement, I need to restrict the edge to have  limited access to the whole cluster's metadata(maybe only specific namespaces but not the whole cluster anyway).
I'm afraid that currently kubeedge does not fully fulfill my requirements, but i would try to do customized development on it and still follow up the latest version.


Check max_bin, etc. match config when using binary

To avoid binary file with non-matching parameters from being used.

Thank you @cyfdecyf

@guolinke What about other Dataset params from https://lightgbm.readthedocs.io/en/latest/Parameters.html#dataset-parameters, e.g. max_bin_by_feature, bin_construct_sample_cnt? Should they also be checked?

@StrikerRUS yes, thank you.
@cyfdecyf can you add these parameters too?

@guolinke OK. I will add checking for those parameters too.

I will add checking for those parameters too.

I think there are more params in Dataset Parameters section that can be checked.
Also, please refer to https://github.com/microsoft/LightGBM/blob/3e8e24b374fbfe6522e39862a79c81b2bea8b259/src/c_api.cpp#L186.

I focused only on checking parameters that are stored in Dataset https://github.com/microsoft/LightGBM/blob/3e8e24b374fbfe6522e39862a79c81b2bea8b259/include/LightGBM/dataset.h#L636
What's the desired way to check parameters that's not in Dataset now? e.g. feature_pre_filter, data_random_seed etc.
Storing them in the binary file and only load them for checking? That would be a bigger change than this PR.

I will add checking for those parameters too.

I think there are more params in Dataset Parameters section that can be checked.

@cyfdecyf yes, I think only check the stored parameter in the Dataset binary object is enough.
you can ping me once the PR is ready.

@guolinke I've already added checking for max_bin_by_feature, bin_construct_sample_cnt in https://github.com/microsoft/LightGBM/pull/3592/commits/9d19083aef6ccc131fcc5bd8833bb390c89a2db0.
I've checked parameters listed in https://lightgbm.readthedocs.io/en/latest/Parameters.html#dataset-parameters against private members in Dataset, but not sure if there's any other parameters that still need to be checked.

current implementation looks good to me. ping @StrikerRUS to confirm.

OK, I agree!
Thanks a lot @cyfdecyf for contribution!


include_membership flag on metadata call

Hello, first off this is a great looking API. You've done a great job.
I am having an issue though when passing in the include_membership call when trying to get the membership on a fondler and if never returns any members array. Also the Share_folder attribute does not return either on the metadata call.
is there something i'm calling incorrect?
thanks,
Rob

Resolved using commit 7f772cd4437d4acc4afbf793ac774738bc38fbe8 and released in version 1.0.5 of the NuGet package


test: fix compile

Signed-off-by: pingkai.pk<EMAIL_ADDRESS>

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@2e41579). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff             @@
##             develop      #24   +/-   ##
==========================================
  Coverage           ?   50.45%
==========================================
  Files              ?      198
  Lines              ?    10237
  Branches           ?        0
==========================================
  Hits               ?     5165
  Misses             ?     5072
  Partials           ?        0

Impacted Files
Coverage Δ

mediaPlayer/tests/player_command.cpp
94.11% <ø> (ø)

mediaPlayer/tests/mediaPlayerTest.cpp
90.9% <100%> (ø)

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 2e41579...c53b31d. Read the comment docs.


How to offset query?

Is it possible to offset the query using the API, I see there is an method for limiting, but not for offset?

Nothing native in the API that I'm aware of, but I believe many of the items that get generated are index-able...
import nfldb

db = nfldb.connect()
q = nfldb.Query(db)
q.game(season_year=2017, season_type='Regular')
for rank, pp in enumerate(q.sort('passing_yds').limit(5).as_aggregate(), 1):
    print rank, pp.player, pp.passing_yds
print '-'*25
for rank, pp in enumerate(q.sort('passing_yds').limit(8).as_aggregate()[3:], 4):
    print rank, pp.player, pp.passing_yds

1 Tom Brady (NE, QB) 714
2 Aaron Rodgers (GB, QB) 654
3 Drew Brees (NO, QB) 647
4 Carson Wentz (PHI, QB) 640
5 Alex Smith (KC, QB) 619
-------------------------
4 Carson Wentz (PHI, QB) 640
5 Alex Smith (KC, QB) 619
6 Carson Palmer (ARI, QB) 601
7 Matt Ryan (ATL, QB) 573
8 Jared Goff (LA, QB) 530

Would this be less performant though, let's say I wanted to offset by 100 for example. Would I then have to do .limit(100 + numberOfRowsIWant) and then load all of those rows into memory rather than doing it at the db level?

¯_(ツ)_/¯...probably?
If my approximately 10 seconds of testing I didn't see a huge difference.
import nfldb
import time

db = nfldb.connect()
q = nfldb.Query(db)
q.game(season_year=2017, season_type='Regular')

start = time.time()
for rank, pp in enumerate(q.sort('passing_yds').limit(5).as_aggregate(), 1):
    print rank, pp.player, pp.passing_yds
print time.time() - start

start = time.time()
for rank, pp in enumerate(q.sort('passing_yds').limit(508).as_aggregate()[503:], 504):
    print rank, pp.player, pp.passing_yds
print time.time() - start

1 Tom Brady (NE, QB) 714
2 Aaron Rodgers (GB, QB) 654
3 Drew Brees (NO, QB) 647
4 Carson Wentz (PHI, QB) 640
5 Alex Smith (KC, QB) 619
0.909999847412
504 Jeff Locke (DET, P) 0
505 Logan Ryan (TEN, CB) 0
506 David Amerson (OAK, CB) 0
507 Terrell McClain (WAS, DT) 0
508 Randall Cobb (GB, WR) 0
1.05400013924

But yeah, if an offset is something you want, it's probably more efficient to do it on the SQL side of things.  As limit appears to be passed through in many places to ultimately find it's way into that SQL expression, it may be an easy addition to the library since the SQL syntax changes very little to add an offset to the query
Out of curiosity, what's your scenario for desiring to offset by 100 (or any x)?  Something like displaying the 5th page of results where you display 20 per page or something else entirely?  Just being nosy...

Hmm yeah performance doesn't seem like it would be too bad at all, especially if you're not getting a ridiculous number of rows. Yeah it doesn't look like it would be too hard to add offset to the library, I might give it a shot.
What I'm thinking about doing is showing a graph of some players statistics, and then progressively loading more players as the user reaches the end of the graph, rather than fetch a huge list of stats right away.
I appreciate your responsiveness :)


Ritual advancement for greedy familiar has wrong ritual ID

advancement has occultism:greedy_familiar
https://github.com/klikli-dev/occultism/blob/master/src/main/resources/data/occultism/advancements/familiar_greedy.json#L22
ritual ID is occultism:familiar_greedy
https://github.com/klikli-dev/occultism/blob/master/src/main/resources/data/occultism/recipes/ritual/familiar_greedy.json

So now im not seeing this advancement at all :/ lol


add VIN pattern rule to pds-gitleaks #3655

This pull request:

closes #3655
updates the gitleaks version to the latest one 8.21.2, since at least 8.21 is required for the [[rules.allowlists]] feature used in this pull request
removes the customized generic-api-key rule since the default changed the keywords to what was customized before

This is too specific and won't be implemented


Fixed examples under Fast API section

Results:
https://jxnl.github.io/instructor/concepts/fastapi/#code-example-starting-a-fastapi-app-with-a-post-request

https://jxnl.github.io/instructor/concepts/fastapi/#streaming-responses-with-fastapi

Summary by CodeRabbit

New Features

Introduced new API endpoint /extract for handling streaming events and returning user data.

Documentation

Updated documentation to reflect the use of OpenAI library and new data models.

Refactor

Transitioned from asynchronous to synchronous calls for the OpenAI service interaction.

New Data Models

Added UserData and UserDetail models to standardize API input and output.

@Anmol6 can you take a look here?

Good catch @waseemhnyc !  turns out open ai async calls with stream=True return an async generator. I'll put up a fix to handle this. I don't think the example needs to change though!


[MINOR] Remove redundant return

What changes were proposed in this pull request?
Remove redundant return in scala code.
Why are the changes needed?
Syntactic simplification.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.

Are they all in the codebase?

Are they all in the codebase?

Yes, I inspect all scala code in spark by

Tool: "/Applications/IntelliJ IDEA CE.app/Contents/bin/inspect.sh"
Rule: Syntactic simplification - redundant return

Can one of the admins verify this patch?

Merged to master.

Merged to master.

I am very sorrry, I miss some scala code with the same problem. @HyukjinKwon
Followup PR:


i3lock-color: limit to i686 and x86-64 platforms

Motivation for this change
Compilation fails for other CPU architectures due to requiring the
SSE2 instruction set. See https://github.com/chrjguill/i3lock-color/issues/44 for upstream issue.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
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 nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

You should be able to un-limit this. I properly include-guarded some stuff now.

@PandorasFox From what I can tell the change hasn't been in a tagged release. I think we have to wait with the packaging until such a release is available. Thanks a lot for the heads up, though!

Ahhh, yeah. I'm giving it a week or so to make sure there's no bugs before I make another release tarball, since I won't be able to fix anything during my finals next week.

No worries :-)


Community Activities: Edit button does nothing

The edit button does not allow users to edit their activities, only to delete them.

Hey so do you just want this edit button to function similar to the edit button that we see when we finish creating an activity?


Remove not readonly commands #2832

Issue: #2832

Make sure that:

[x] You have read the contribution guidelines.
[x] You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
[x] You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
[ ] You submit test cases (unit or integration tests) that back your changes.

Just talked to @mp911de and he agreed that we should probably remove io.lettuce.core.masterreplica. ReadOnlyCommands. This could be done in another PR, but it would be awesome if we can do it here.

Hey @thachlp , thanks for submitting this PR.
I think there are a few things we needs to address first:

Seems like there are two ReadOnlyCommands classes - one in the io.lettuce.core.masterreplica package and one in the io.lettuce.core.protocol package. The one you modified (in the io.lettuce.core.masterreplica) appears to be unused. I believe the change needs to be done in the io.lettuce.core.protocol.ReadOnlyCommands class. Let's change both classes for now similar to how it was done in Add GEOSEARCH to read-only commands #2568 #2569
The GEOSEARCH command is read-only, let's not remove it from the list:

COMMAND INFO GEOSEARCH
1) 1) "geosearch"
   2) "-7"
   3) 1) "readonly"
   4) "1"

In a perfect world I'd love to see an integration test that loops over these commands and verifies that they are readonly so we can quickly adapt to server change (optional, but would be very nice).

@tishun,
You are correct, I rechecked and updated the list, please help review 🚀
Is there any way that I can run the integration test in local? I try to write the test that you recommend but I got the error
java: package jdk.net does not exist. How can I fix it?

Hey @thachlp , thanks for submitting this PR.
I think there are a few things we needs to address first:

Seems like there are two ReadOnlyCommands classes - one in the io.lettuce.core.masterreplica package and one in the io.lettuce.core.protocol package. The one you modified (in the io.lettuce.core.masterreplica) appears to be unused. I believe the change needs to be done in the io.lettuce.core.protocol.ReadOnlyCommands class. Let's change both classes for now similar to how it was done in Add GEOSEARCH to read-only commands #2568 #2569
The GEOSEARCH command is read-only, let's not remove it from the list:

COMMAND INFO GEOSEARCH
1) 1) "geosearch"
   2) "-7"
   3) 1) "readonly"
   4) "1"

In a perfect world I'd love to see an integration test that loops over these commands and verifies that they are readonly so we can quickly adapt to server change (optional, but would be very nice).

@tishun, You are correct, I rechecked and updated the list, please help review 🚀 Is there any way that I can run the integration test in local? I try to write the test that you recommend but I got the error java: package jdk.net does not exist. How can I fix it?

You should be able to run test locally if you call make test

You'd need to format your new changes too, try using mvn formatter:format

You'd need to format your new changes too, try using mvn formatter:format

Thanks @tishun 🙇

You'd need to format your new changes too, try using mvn formatter:format

Thanks @tishun 🙇

Hi @tishun, the error from CI is weird, could you re-run the job? Do you have any recommend?

You'd need to format your new changes too, try using mvn formatter:format

Thanks @tishun 🙇

Hi @tishun, the error from CI is weird, could you re-run the job? Do you have any recommend?

Hey @thachlp , List.of() is a feature of Java 9, and we compile with Java 8 to achieve maximum backwards compatibility.
Could you change the use of this method with something else like Arrays.asList()

You'd need to format your new changes too, try using mvn formatter:format

Thanks @tishun 🙇

Hi @tishun, the error from CI is weird, could you re-run the job? Do you have any recommend?

Hey @thachlp , List.of() is a feature of Java 9, and we compile with Java 8 to achieve maximum backwards compatibility.
Could you change the use of this method with something else like Arrays.asList()

Nice, thanks

I think you need to rebase your changes to include the latest fixes to the unit tests to pass the CI

I think you need to rebase your changes to include the latest fixes to the unit tests to pass the CI

@tishun, it's done 🙇

Thanks for the contribution!


flaky watchpoint.watchpoint - absolute address runtime test

Saw it randomly failing in two CI jobs so far.

PR merged


Update docker for default admin creds update

Changes
Passes in an initial admin password via env variable, implemented in security plugin main and 2.x lines, for 2.12.0 release.
Merge Requirements
For new features contributions please make sure you have completed the following
essential items:

[ ] CHANGELOG.md updated to document new feature additions
[ ] Appropriate documentation updates in the docs
[ ] Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

@YANG-DB can you help me understand what other changes this repo needs? It doesn't seem to follow the branching strategy of main/2.x - so do we need to handle logic to determine whether to use the default admin password, or the env variable password in the ES_PASSWORD field? Any other places you see that would need changes? Thanks!

https://github.com/opensearch-project/security/issues/3624

@derek-ho please use the .env for all the password’s place holders

@derek-ho please use the .env for all the password’s place holders

@derek-ho Could you please address this comment.

Marking this as draft until variable OPENSEARCH_VERSION changes to >= 2.12.0.

Done. @YANG-DB can you take another look? I also changed the image from staging to the actual released docker images, similar to the dashboards image (which is not using staging).

@YANG-DB can you double check again and we can merge if everything looks good?

@YANG-DB @pjfitzgibbons @ps48 @kavithacm @joshuali925 @dai-chen @rupal-bq @mengweieric @vamsi-amazon @Swiddis Could we get this reviewed as we are targeting 2.12 for this change?

@YANG-DB @pjfitzgibbons @ps48 @kavithacm @joshuali925 @dai-chen @rupal-bq @mengweieric @vamsi-amazon @Swiddis Still waiting for reviews. Could we get this reviewed as we are targeting 2.12 for this change?


CommercialSizeCategory

I was browsing around our vocab server to span for CodeTypes that can be used in SID when I came across CommercialSizeCategory. The descriptions for most of the codes need improvement.
https://vocab.ices.dk/?codetypeguid=9aa08f25-0e5e-49bb-8e08-b0b447e0836d
The regulation this vocab is based on: https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX%3A31996R2406

@MariaMakri to check the regulation and talk with the core group regarding changing the descriptions.

Core group pointed out that commercial categories differ among and within countries. There is also the CommercialSizeCategoryScale code type https://vocab.ices.dk/?codetypeguid=9aa08f25-0e5e-49bb-8e08-b0b447e0836d which could be made conditionally mandatory.

@MariaMakri to improve descriptions


.route() grouping breaks trigger event routes.

Trigger event routes/paths support works as a simple wrapper that gets the eventSource, and transforms it into method:TRIGGER path:eventSource Request for Hono to process, we would then register routes on TRIGGER method.
For it to work perfectly, the paths of the eventSource should never intended to be prefixed, i.e: TRIGGER method should never be prefixed
Currently Hono doesn't provide any (and I can't find hack-able) way to get or skip the prefix of .route() grouping, so, Hono instances with trigger events would break after getting grouped with .route()

Some possible solutions:

Solution 1: update to Hono's core, providing some way to get/skip the prefix of .route() grouping for specific routes.
Solution 2: Agree to never use path delimiter "/" as eventSource, we could then provide a helper function to loop through the top-level app.router.routes to remove all path prefixes on "TRIGGER" method, we only need to run it once.
Solution 3: A helper function that receives both the top-level app instance and the instance that contains the trigger event routes, would automatically detect and remove the prefixed path, we need to run it for each grouped instance that contains trigger event routes.

Solved in e834b15


Architecture design for the window server, client, and UI library

Here's what I'm thinking:
TinyWS Architecture:
  - Asks for root password upon start if not root
  - Elevates to root to create daemon

  - Displays black screen
  - Waits for a window manager to start IPC with self
  - CuteWindowServer communicates with the window manager when a window gets created and dies
  - Window manager can send a canvas of what it wants the top to look like

  - Window manager can recieve all mouse & keyboard events, but the window can only recieve mouse & keyboard events when it has focus

  - Window can send all messages to the window server for it to be forwarded to the window client

bciw (But Can It Window?) - Window Manager

bciw Architecture:
   - Communicates to the window server using IPC (aka Kernel extensions)

stlws - St(y)l(e) Window Server, UI Library

stlws Architecture:
  - Pass canvas to library
  - Can draw radio boxes, etc.
  - Communicates with window manager via the window server to get theme

Here's a summary of what changed so far:
bciw -> Renamed to Dusk
stlws -> Renamed to DawnUI/Dawn

TinyWS and Dusk are almost ready! :3


Old AngularJs version

Angularjs version being used in example code is 1.0.7. Can you upgrade an example to higher version (1.3.x)?

I'd like to update the example to use Angular 1.3.x and remove the dependence on jQuery. I hope to work on this after 5.2 is released, but possibly not until after 5.3.

:+1: I'd love to see this example improved and updated too...
I can't even get it to load, with fineuploader v5.4.1

Yes, this is a bit old. I can see updating it to the latest Angular 1.x version, but I doubt this will ever be updated to Angular 2.x (at least, not by me). There's a lot of other work scheduled for Fine Uploader 5.5 and 6.0 at the moment, and we have a limited number of hours and people to complete these tasks, so, I'm not sure exactly when this will happen.
My suggested approach for restructuring this example involves:

a simple Fine Uploader directive with no external dependencies (other than Angular)
a service that exposes the Fine Uploader instance for use by other directives, controllers, and services

This shouldn't be tough to complete.

I realize how important this example may be for AngularJS users, so I'm going to prioritize updating this for Angular 1.5 and Fine Uploader 5.4+. I hope to begin on this within the next week, and intend to update the GitHub code and associated blog post.

Code is completed updated and being staged in the update-angular-example branch. Last step before merging into master is to update the article at http://blog.fineuploader.com/2013/11/01/full-stack-javascript-image-uploader-using-angularjs-node-js/.

@rnicholus Great news! Thanks

GitHub repo and blog post have been updated!


RESET is confusing

I think this is both a bug and a doc issue.
It is not clear what reset is going to do.  While we require the user to be an admin and use --force, it is not clear we are going to delete data too.
winget source reset
The following sources will be reset if the --force option is given:
Name    Argument
bugbash https://s1
msstore https://s2
winget  https://winget.azureedge.net/cache
C:\WINDOWS\system32>winget source reset --force
Resetting all sources...Done
C:\WINDOWS\system32>winget source reset
The following sources will be reset if the --force option is given:
Name    Argument
msstore https://s2
winget  https://winget.azureedge.net/cache
Maybe we should add a comment, "This will remove source bugbash, are you sure you want to continue?"

This must also honor any Group Policy configured by IT Administrators.

Documentation at Microsoft Learn describes what winget source reset does.


Configure GitHub Actions as an alternative MSAM build pipeline for AWS Solutions

We'd like to trigger scans, tests, and builds within the Solutions infrastructure when new content is committed to this repo.

code scans (PRs and branch commits)
continuous test build (branch commits) and deploy
release build (release tag) and deploy

Open source analysis tools for consideration (for PR and push scans):

cfn-lint (CloudFormation)
cfn-nag (CloudFormation)
pylint (Python)
bandit (Python)
hawkeye (Multiple)
clamav (Malware?)


remaming STATIC file channels

Hi,
I am trying to rename channels in the STATIC trial in order to remove the static angle offsets for the dynamic skating trials. However when I run the bmech_renamechannel code, which call the renamech code, I get the following error:
och_pos = {'LAA_static','LEA_static','LHA_static','LKA_static','LPA_static','RAA_static','REA_static',...
'RHA_static','RKA_static','RPA_static','THA_static'};
nch_pos = {'LAA','LEA','LHA','LKA','LPA','RAA','REA','RHA','RKA','RPA','THA'};
bmech_renamechannel(och_pos,nch_pos,fld)
renaming the following channels:
renaming LAA_static to LAA
renaming LEA_static to LEA
renaming LHA_static to LHA
renaming LKA_static to LKA
renaming LPA_static to LPA
renaming RAA_static to RAA
renaming REA_static to REA
renaming RHA_static to RHA
renaming RKA_static to RKA
renaming RPA_static to RPA
renaming THA_static to THA
80  for i = 1:length(fl)
renaming channels for: \data\rename static ch test\female\P02\VAPSTATIC01.zoo
Reference to non-existent field 'Analog'.
Error in renamech (line 47)
ach = data.zoosystem.Analog.Channels;
Error in bmech_renamechannel (line 83)
data = renamech(data,och,nch);
This code does work, if you remember, to rename the 'Acceler' channel to 'Accel', whereby the Analog channel returns an empty 0x0 cell,
this is where the code breaks down when I try to rename the STATIC trial channels. Giving me the "Reference to non-existent field 'Analog'. " error,
thanks for the help!

The static files only have 'video' data so the call to 'renamech.m' resulted in an error. 'bmech_renamechannel.m' was updated to call the new subfunction 'renamechannel.m' which checks content of file for any existing video or analog data (if available).
The latest zoosystem update contains the new 'bmech_renamechannel.m' and 'renamechannel.m' . 'renamech' was removed as is now obsolete.


proposal: flag: option to accept abbreviations of flags

gopls version
Build info
golang.org/x/tools/gopls v0.8.4
<EMAIL_ADDRESS>h1:zGZsAXAb0LLws/Z+2BCWR17dkPHhIO2GYwYSSkeXX5c=
<EMAIL_ADDRESS>h1:dtDWrepsVPfW9H/4y7dDgFc2MBUSeJhlaDtK13CxFlU=
<EMAIL_ADDRESS>h1:81/ik6ipDQS2aGcBfIN5dHDB36BwrStyeAQquSYCV4o=
<EMAIL_ADDRESS>h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0=
<EMAIL_ADDRESS>h1:qyrTQ++p1afMkO4DPEeLGq/3oTsdlvdH4vqZUBWzUKM=
<EMAIL_ADDRESS>h1:6zppjxzCulZykYSLyVDYbneBfbaBIQPYMevg0bEwv2s=
<EMAIL_ADDRESS>h1:5KslGYwFpkhGh+Q16bwMP3cOontH8FOep7tGV86Y7SQ=
<EMAIL_ADDRESS>h1:rm+CHSpPEEW2IsXUib1ThaHIjuBVZjxNgSKmBLFfD4c=
<EMAIL_ADDRESS>h1:olpwvP2KacW1ZWvsR7uQhoyTYvKAupfQrRGBFM352Gk=
<EMAIL_ADDRESS>h1:CJwk4qG1fov4WP7/DWhhb7OQVZlQKAl1rEMnDF+ceGU=
<EMAIL_ADDRESS>h1:jokAF1mfylAi1iTQx7C44B7vyXUcSEMw8eDv0PzNu8s=
<EMAIL_ADDRESS>h1:2LdYUZ7CIxnYgskbUZfY7FPggmqnh6shBqfWa8Tn3XU=
<EMAIL_ADDRESS>h1:kTojdZo9AcEYbQYhGuLf/zszYthRdhDNDUi2JKTxas4=
<EMAIL_ADDRESS>h1:tzxjVAj+wSBmDcF6zBB7/myTy3gX9xvi8Tyr28AuQgc=
go: go1.18
go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/karelk/Library/Caches/go-build"
GOENV="/Users/karelk/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/karelk/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/karelk/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/local/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/local/lib/go/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.18.2"
GCCGO="gccgo"
AR="ar"
CC="/usr/bin/clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/c8/27sy8g9d47ngtrxhb_x34nkw00_w91/T/go-build943201535=/tmp/go-build -gno-record-gcc-switches -fno-common"
What did you do?

Defining flags using the flag package often leads to long flag names.

What did you expect to see?

The flag package should automatically recognize shorthands where possible.
Example: if a flag.FlagSet (which may be the global flag.CommandLine) holds the flags: verbose and length then automagically an invocation with -v and -l should work.

The package should resolve -v to the defined flag verbose and -l to the length.
Arbitrary lengths should be possible: -ver and -len should also resolve to verbose and length.
Only when a name can't be uniquely resolved to an existing flag, should an error be raised.

For ambiguous names the flags should be shortened until they are unique. E.g., defined flags item and id couldn't be abbreviated to -i, but instead to -it and -id.

What did you see instead?
The standard way that package flag works is that upon invocation, an error occurs that flag -i is given but not defined. It would be better if the package tried to resolve the flag in the set of defined names.
Implementation thoughts
I wrote a functional mockup at https://github.com/KarelKubat/flagnames. This has the drawback that the arguments that are passed into flag.Parse() are patched from abbreviated forms into whatever flags are defined. That works fine, but isn't too elegant.
A better approach would be to:

Define a bool acceptAbbrevs in the FlagSet structure, defaulting to false to keep parity with the existing way,
Provide accessors (per-FlagSet and global), e.g. flag.AcceptAbbrevs()
When the bool is set, resolve provided flags against defined names while allowing abbreviations
Only issue an error when a provided flag:

Doesn't occur as a prefix in any defined flag name
Could resolve to multiple defined flags

A hypothetical code sample:
var verboseFlag = flag.Bool("verbose", false, "increases verbosity")
flag.AcceptAbbrevs().  // allow -v, -ve, -ver, -verb etc.
flag.Parse()

My Question
Your thoughts?

I'm happy to propose this change to package flag.
But if you think it's not worth while then please let me know and I'll happily continue using github.com/KarelKubat/flagnames to scratch my itch.

Duplicate of #40138


Added source code for 'Counting Number of Inversion' problem in Java

Related Issue
Closes: #843
Describe the changes you've made
Added source code for 'Counting Number of Inversion' problem in Java
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Language used for coding
Java
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have documented the code.
[x] New and existing unit tests pass locally with my changes.

Please review my code.

Problem name is "Merge Sort- Counting Inversions"

Updated the file & folder name


Enhancements on documents and URLs.

Summary

Concisely describe the issue and your solution:

Add URLs to W3C DID/VC specs.
Fix FAQ typos.
Revise use-cases.

Link to existing issue (type "#" to check): No
Specify the tests done so far:
See: https://weidentitydocs.readthedocs.io/zh_CN/latest/ and https://weidentitydocs.readthedocs.io/en/latest/

@gmzer Fix done


wingetcreate.exe fails with Unable to create a reference to the forked repository

Brief description of your issue
wingetcreate.exe fails with the following error message:
Unable to create a reference to the forked repository. This can be caused when the forked repository is behind by too many commits. Sync your fork and try again.

Unfortunately, the error message doesn't really tell us anything. wingetcreate.exe presumably forks the latest package repository so the error message doesn't make sense to me. Does wingetcreate.exe have a -verbose flag?
Steps to reproduce
I'm using the following GitHub action:

https://github.com/filebot/plugins/blob/master/winget/make.ps1
https://github.com/filebot/plugins/blob/master/.github/workflows/winget.yml

You can find the GitHub CI log here:
https://github.com/filebot/plugins/actions/runs/6782204951/job/18433976886
Expected behavior
wingetcreate.exe should work or print a useful error message.
Actual behavior
wingetcreate.exe doesn't work.
Environment
GitHub Action `windows-latest` running the `https://aka.ms/wingetcreate/latest` executable.

@rednoah - It looks like you're more than 90,000 commits behind master on https://github.com/rednoah/winget-pkgs. Merging in the latest commits from microsoft/winget-pkgs should resolve the issue

Cheers! That was the key. I deleted my rednoah/winget-pkgs and now it works. Thank you very much for the help. Checking for forks in my accounts would never have occured to me.

For the future users:

Go to your profile on GitHub web page
Go to your repositories
Find there winget-pkgs repo
Press the sync fork button there

For the future users:
* Go to **your profile** on GitHub web page

* Go to your repositories

* Find there `winget-pkgs` repo

* Press the `sync fork` button there

That's certainly an option if you're doing things manually but may not be the most suitable option if you're automating the releases in a CI/CD pipeline. You can sync the repo using gh CLI if you're using wingetcreate in a CI environment, I'll link a couple of examples:

https://github.com/microsoft/devhome/blob/main/.github/workflows/winget-submission.yml#L9-L15
https://github.com/coder/coder/blob/817cc78b948216a1ec005a352cf0301b4510092c/.github/workflows/release.yaml#L410-L414


fix #717 and preserve compatibility with Atom pre-1.24

This will fix #717 without breaking functionality for everyone who has not upgraded to Atom 1.24 (upgrades for different OSes are not simultaneous and on Linux I believe there is still no automatic upgrade mechanism).

I'm closing in this since I've already merged in #728


[Feature Request] Bracket Pair Colorization: Consecutive/independent color mode

This would be porting over said feature from Bracket Pair Colorizer 2
"bracket-pair-colorizer-2.colorMode"
Consecutive brackets share a color pool for all bracket types
Independent brackets allow each bracket type to use its own color pool

I would change the name of this setting, I don't think consecutive is very clear.
I could imagine editor.bracketPairColorizer.colorizeBracketsIndependently: boolean (default false).
It is easy to implement, but is this feature useful? I would like to have as few settings as possible.

That name name makes more sense, yes. I don't know, I like it personally, maybe @CoenraadS has analytics on how often all the settings were used?

I don't have any data about which settings are popular or not used at all.

is this feature useful?

I can't speak for Stanzilla or CoenraadS, but I like this idea for a pretty specific reason. I like bracket colorization when brackets of the same type are nested (because it helps me find pairs quickly), but I find it distracting/jarring that literally every bracket is colored whether it is nested or not. I use VS Code for multiple languages. Some of these use "{ }" for blocks (like JavaScript) and some don't (like Python).
Consider how brackets are colored in the following toy examples:
Python:

JavaScript:

I don't like how busy it looks, and I find it a little distracting. I can try setting "editorBracketHighlight.foreground1" to "#000000" and it looks like this:
Python:

JavaScript:

The Python example looks better, but is flawed. I would prefer to not have any round brackets in that example colored. The JavaScript example looks just as busy as before because everything is in a "{ }" block.
So I want a clean look where brackets are black most of the time (in all languages), but become colored when brackets of the same type are nested. That way I get the benefits of bracket colorization without it being distracting.
Did I explain that well?

@oaahmad, if the problem is the distraction, it feels to me that you would be better served by just using less saturated/darker colors, so that the brackets are more identical in colors but not quite, and so you can still distinguished them if you need it but without being in-your-face when you don't.

@Nahor That would make it less distracting, but it would make it harder to distinguish the brackets when they are nested. The speed and ease at which I can see which brackets are pairs is kind of the whole point of bracket colorization, so I do like that the colors are very different.
It would also be nicer if the brackets were just black when not nested instead of a muted color. It kind of feels like the worst of both worlds: the brackets are still colored when I don't need them to be, and they are not distinct enough when I need them to be.
I do think this feature request is the better solution, but I can play around with colors in the meantime to see if I like something more. Thanks for the suggestion.

@oaahmad, what you want is not quite the suggestion either. It sounds like what you want is, that first level of color be excluded from the rotating color pool: black-color1-color2-color3-color1-color2-....
Also, it's hard to imagine that this would be a worthwhile feature. How often are brackets not nested? Between the lambdas, functional programming, namespaces, ... it feels like the non-nested brackets would be quite a minority (but I guess that's just my own experience, YMMV)

the brackets are still colored when I don't need them to be, and they are not distinct enough when I need them to be.

How can a color be colorful enough to be distracting and yet not colorful enough to distinguish from others? If you can't find a few color muted enough to not be distracted and but still be distinguishable, it must be hell to be you! :stuck_out_tongue_winking_eye:
Here another suggestion: have a shortcut to enable/disable bracket colorization (you'll probably need Settings Cycler for that). Then you can keep the colorization disabled until you need it.

what you want is not quite the suggestion either. It sounds like what you want is, that first level of color be excluded from the rotating color pool: black-color1-color2-color3-color1-color2-....

That's not quite right. I'm not asking for that because I can already do that. I can already set the first color to black. That setting exists. It does not solve my problem. I already tried it (see my first comment).
The issue is not that I need black to be the first color. The issue is that I need black to be the first color and I need this feature to be implemented.

How often are brackets not nested?

I think you're asking the wrong question. If this issue is implemented, then only brackets of the same type are nested. The right question is "how often are brackets of the same type not nested". The answer is very often with the exception of "{ }" in many languages. I understand that "{ }" will mostly be colored in many languages. I'm fine with that. There will still be a huge reduction in colored brackets.

If you can't find a few color muted enough to not be distracted and but still be distinguishable, it must be hell to be you!

I'm not saying the colors are so distracting that I can't work. I'm not saying the colors are so distracting that I want to disable the feature. I'm saying the colors are distracting enough to me that I would prefer most of the brackets to be black. It's just a preference. You may have a different preference. That's fine.

what you want is not quite the suggestion either. It sounds like what you want is, that first level of color be excluded from the rotating color pool: black-color1-color2-color3-color1-color2-....

That's not quite right. I'm not asking for that because I can already do that. I can already set the first color to black. That setting exists. It does not solve my problem. I already tried it (see my first comment).

You can set the first color to black, but you cannot remove it from the color pool after the first use. And from your description, it seemed to be what you want (among other things), i.e.:
black-color1-color2-color3-color1-color2-....
instead of
black-color1-color2-color3-*black*-color1-color2-....
Sorry if I misunderstood.

How often are brackets not nested?

I think you're asking the wrong question. If this issue is implemented, then only brackets of the same type are nested. The right question is "how often are brackets of the same type not nested". The answer is very often with the exception of "{ }" in many languages. I understand that "{ }" will mostly be colored in many languages. I'm fine with that. There will still be a huge reduction in colored brackets.

'()' is also nested very frequently , as in func1(func2(func3())), or constructs like while(!empty()). And lets not forget LISP 😛 (but ok, LISP guys are probably using Emacs anyway, not VSCode, so they don't really count 😝).
'[]' is not nested that often in C, but more frequently in Python because Lists Comprehensions.
So yes, I understood you, I just do not agree with the "not nested very often"

If you can't find a few color muted enough to not be distracted and but still be distinguishable, it must be hell to be you!

I'm not saying the colors are so distracting that I can't work. I'm not saying the colors are so distracting that I want to disable the feature. I'm saying the colors are distracting enough to me that I would prefer most of the brackets to be black. It's just a preference. You may have a different preference. That's fine.

What I meant is that for the colors to be distracting, there must be colors that you can distinguish. I can't imagine how you can have distracting colors that you cannot see, which is what you implied with the "worst of both worlds" earlier.
Anyways, my point is that it feels to me, from my anecdotal evidence/experience, like a niche feature. But sure, to each his own.

@Nahor Ah okay. I misunderstood what you were saying. Sorry about that. I do not want to remove black from the color pool. I am perfectly okay with black repeating. And yes "worst of both worlds" was not the best wording. I did not mean literally "worst". I just meant it would be a compromise in both directions. My point was just that this feature request would be a better solution because of those compromises.
And yeah I get that this feature will not make bracket colorization exceptionally rare, but the examples you're using are exactly the places where I would want brackets to be colored. My position is just that needless colorization is more distracting than helpful, but colorization is very much helpful when nesting of the same bracket type happens. I do prefer having bracket colorization on even as it is currently implemented because I like the benefits more than I am bothered by the distraction when it's not necessary.
I agree that my reason for wanting this feature might be very niche, and I want to clarify that this feature is not urgent to me. I'm just providing a use case because @hediet asked if this is useful. Thanks for clarifying what you meant about removing black from the color pool.

Here is a use case where someone never wants brackets of a certain type to be colored because they are never nested in a language: https://github.com/microsoft/vscode/issues/132336. This feature request could achieve that.

@oaahmad

So I want a clean look where brackets are black most of the time (in all languages), but become colored when brackets of the same type are nested. That way I get the benefits of bracket colorization without it being distracting.

I like that idea! But I think this is a different feature request, right? (in this case, please open a separate issue)
Would your feature cover the feature requested in this issue?

@hediet I can already set the first color to black which is the first step. Black would get repeated in deeply nested brackets, but that's not a problem (not for me at least).
The problem is that many languages use "{ }" heavily for scope. So even if I set the first color to black it makes no real difference because all my code will be inside a "{ }" scope (maybe nested inside several "{ }" scopes).
So what I'm trying to say is this: if I set the first color to black, and this feature is implemented ("colorizeBracketsIndependently") then I have what I want. Brackets would only be colored if brackets of the same type are nested (because I set the first color to black and because I have ("colorizeBracketsIndependently" set to true). So I don't need any feature to achieve this other than the one proposed here. It's just a use case for this feature.
So what I'm asking for would be covered in this feature request to my satisfaction (I just need to use this feature in combination with setting the first color to black).

I understand.
I guess an option like "Don't colorize top most bracket pair per type" would also do it (though we try to minimize the amount of settings).

In case anyone is still confused, I finally busted out GIMP and made this monstrosity:
Default settings:

Black:

Black + this feature:

(Except I'd obviously choose better colors than that)

I guess an option like "Don't colorize top most bracket pair per type" would also do it (though we try to minimize the amount of settings).

Yeah I respect your desire to not add extra settings which is partly why I'm advocating for this feature instead of an additional one.
I also just like this better. I want brackets to be colored independently (it's an extra bonus for me).

@oaahmad, I've added a proposal that could help with some of your distraction issues: #132488.
It's not a replacement for this feature, but it will help further to avoid "unnecessary" change of colors (in your example, it would help for "[["one":"two"]]" and "[[This is a very useless... clear]]")

Personally, the setting I want is forceIterationColorCycle

Too often, you'll have many opening blocks in the same lines and they'll all be the same colour. I don't like yellow enough to want it to be everywhere, ya know.

Verification steps:

Enable bracket pair colorization "editor.bracketPairColorization.enabled": true
Configure "editor.bracketPairColorization.independentColorPoolPerBracketType": true
Observe that each bracket type (e.g. (...), {...} in TS) has its own color pool


[Toolkit feature]: ColorField - Apply new color on edit without having to close the widget

Contact Details (Optional)
No response
What is the context of the feature/improvement?
Color values editable via the colorfield widget only update upon closing the colorfield widget. So in order to see a change, one has to click anything but the widget to close it -> see the change -> open colorfield to further change the value

Please describe the feature/improvement?
Automatically update / apply the underlying color value on each edit without having to close the widget (maybe with a slight delay)
What would be your solution? (optional)
The underlaying gui framework (ImGui) should be able to return true on each modification to ImGui::ColorEdit to trigger whatever logic is necessary to update or apply the color value
Version
2024.3.0

Thanks for the feedback. I've filed an internal ticket REMIX-3047 to track this on our side.


contribution model

Users may be modifying files below for a variety of reasons, and adding new system descriptions, etc.  We need to define:
0) We need to keep track of maintainers; is this per file?

Which changes we want upstreamed

new systems
system owners should update the default compilers on the system
full spec of the runs that we are putting on the dashboard

Which changes should remain local

study specific changes such as playing with compiler flags, turning on extra measurements, other changes that should not be the default behavior for the system/benchmark/experiment

Which changes should be upstreamed to Spack or Ramble

benchpark/repo is the way to test all of the components together
should we allow commits to the repo?
should commits to the repo trigger PRs to Spack and Ramble instead?  Once those are upstreamed, changes to benchpark/repo need to be made, and ${BENCHMARK1} should point at the upstreamed versions instead of at the repo.

We will try to keep Benchpark to new versions of Spack and Ramble, and there may be version compatibility issues.  So we will want to enable pulling in new Benchpark, and will need to update Spack and Ramble accordingly.  In this process, we expect that "core" functionality from all 3 projects needs to be updated.  Meanwhile, the users may well prefer to keep their local changes in system and benchmark configs.  This may introduce issues if the interfaces of either of the project change, but otherwise may be a desirable usage pattern for our users.
$benchpark
├── configs
│  ├── ${SYSTEM1}
│  │  ├── auxiliary_software_files
│  │  │  ├── compilers.yaml
│  │  │  └── packages.yaml
│  │  ├── spack.yaml
│  │  └── variables.yaml
├── experiments
│  ├── ${BENCHMARK1}
│  │  ├── ${ProgrammingModel1}
│  │  │  ├── execute_experiment.tpl
│  │  │  └── ramble.yaml
│  │  ├── ${ProgrammingModel1}
│  │  │  ├── execute_experiment.tpl
│  │  │  └── ramble.yaml
└── repo
├── ${BENCHMARK1}
│  ├── application.py
│  └── package.py
└── repo.yaml

Meanwhile, the users may well prefer to keep their local changes in system and benchmark configs. This may introduce issues if the interfaces of either of the project change, but otherwise may be a desirable usage pattern for our users.

In my first experiments I realized that some benchmark config files (like tpl templates) may depend on/relate to machine configs which adds an additional complication.


Fix missing context menu in ReactiveTextField

Connection with issue(s)

Close #398

Solution description
copied the default _defaultContextMenuBuilder from vanilla Flutter TextField to ReactiveTextField to keep the same behaviour
Screenshots or Videos

To Do

[ ] Check the original issue to confirm it is fully satisfied
[ ] Add solution description to help guide reviewers
[ ] Add unit test to verify new or fixed behaviour
[ ] If apply, add documentation to code properties and package readme

Hi! Any chance this commit comes soon to production?

Hi @victorcatn
Thanks for the PR. I will take a look at it. Is there a way to add a test to maintain the same coverage percentage?

Hi everyone, thanks once again for the support. I have released version 16.1.1 which fixes this issue. Please give it a look and don't hesitate to create a new issue or PR is something else is missing.


Can't change from seconds to datetime

Good morning, I have been trying to create a measure by modifying an integer type field at time.
I have tried from functions created from scratch and methods that have datetime but none work.

Steps to reproduce
I have a field called DURATION, type INT and the corresponding measures, DURATION.SUM and DURATION.MEAN

Actual Result

I want to pass the seconds, to time format, using the timedelta(seconds=m['DURACION.SUM']) or timedelta(seconds=logs['DURACION']) method, but it gives me an error

Expected Result
The objective is to pass X seconds to HH:MM:SS format, but it does not allow me to pass the column or the measure to the method... Is it my mistake or is there another way to do it?
Environment

atoti: 0.7.2
Python: 3.10.9
Operating System: Windows 10 Enterprise

Logs (if relevant)

Hi!
You need to choose the type of a field when creating a table (i.e. through read_xxx or create_table).
You can find the available types there: https://docs.atoti.io/latest/lib/atoti/atoti.type.html#module-atoti.type

Hi!
The DURATION column is already an INTEGER, since it is the only type of value that the function accepts.
m['TEST'] = timedelta(seconds=m['DURATION.SUM'])
That is, the column I need in int type is already there, the problem is that it doesn't let me read the column or the autogenerated measure as an int value
Thanks!!

Hi kiimot,
You cannot apply a timedelta() function to an atoti measure, you can only transform measures with atoti functions.
Sadly there is no out-of-the-box formatter for integer to time, nor way to transform integer to time.
What you can do is implement the logic yourself with tt.string.concat:
m["DURATION.hours"] = tt.math.floor(m["DURATION"] / 3600)
m["DURATION.minutes"] = tt.math.floor( (m["DURATION"] - m["DURATION.hours"] * 3600) / 60)
m["DURATION.secondes"] = m["DURATION"] - (m["DURATION.hours"] * 3600) - (m["DURATION.minutes"] * 60)
m["DURATION.formatted"] = tt.string.concat(m["DURATION.hours"], m["DURATION.minutes"], m["DURATION.secondes"], separator=":")

This results in something like that:

Hi!
Perfect, with this solution at least visually I can see it well.
Thank you so much for your time!!


Error in function call - data.azurerm_client_config.current.object_id is ""

Hi,
I'm seeing an issue when running a previously working terraform plan
terraform plan data.azurerm_client_config.default: Reading... data.azurerm_client_config.default: Read complete after 0s [id=2022-05-25 06:46:07.818982 +0000 UTC] module.caf.data.azurerm_client_config.current: Reading... module.caf.data.azurerm_subscription.primary: Reading... module.caf.data.azurerm_client_config.current: Read complete after 0s [id=2022-05-25 06:46:08.4485897 +0000 UTC] module.caf.data.azurerm_subscription.primary: Read complete after 1s [id=/subscriptions/98952024-fc38-4f12-9934-9c8a9f46a943] ╷ │ Error: Error in function call │ │   on .terraform\modules\caf\locals.tf line 298, in locals: │  298:   object_id = coalesce(var.logged_user_objectId, var.logged_aad_app_objectId, try(data.azurerm_client_config.current.object_id, null), try(data.azuread_service_principal.logged_in_app.0.object_id, null)) │     ├──────────────── │     │ data.azuread_service_principal.logged_in_app is empty tuple │     │ data.azurerm_client_config.current.object_id is "" │     │ var.logged_aad_app_objectId is null │     │ var.logged_user_objectId is null │ │ Call to function "coalesce" failed: no non-null, non-empty-string arguments. ╵
I can confirm my session is logged in and can retrieve the account using az account show:
{   "environmentName": "AzureCloud",   "homeTenantId": "########-bfe0-4f51-####-e96dd19548a1",   "id": "########-fc38-4f12-####-9c8a9f46a943",   "isDefault": true,   "managedByTenants": [],   "name": "Pay-As-You-Go",   "state": "Enabled",   "tenantId": "########-bfe0-4f51-####-e96dd19548a1",   "user": {     "name"<EMAIL_ADDRESS>    "type": "user"   } }
az version
{
"azure-cli": "2.37.0",
"azure-cli-core": "2.37.0",
"azure-cli-telemetry": "1.0.6",
"extensions": {}
}
terraform version
Terraform v1.2.1
on windows_amd64

provider registry.terraform.io/aztfmod/azurecaf v1.2.17
provider registry.terraform.io/hashicorp/azuread v1.4.0
provider registry.terraform.io/hashicorp/azurerm v2.88.1
provider registry.terraform.io/hashicorp/external v2.2.2
provider registry.terraform.io/hashicorp/local v2.2.2
provider registry.terraform.io/hashicorp/null v3.1.1
provider registry.terraform.io/hashicorp/random v3.1.3
provider registry.terraform.io/hashicorp/time v0.7.2
provider registry.terraform.io/hashicorp/tls v3.3.0

Please advise
Thanks,
Mark.

https://github.com/hashicorp/terraform-provider-azurerm/issues/16982

@mgibson85 I have opened an issue on the provider.
In the meantime you can add the following command  before you execute terraform in an interactive run:
export TF_VAR_logged_user_objectId=$(az ad signed-in-user show --query id -o tsv --only-show-errors)

Do you have a variable called logged_user_objectId set in your root module?
You need to add and pass it through the caf module
On Tue, 31 May 2022 at 17:32, mgibson85 @.***> wrote:

Thanks @LaurentLesle https://github.com/LaurentLesle, I've tried the
command but it still fails:
[image: image]
https://user-images.githubusercontent.com/12297674/171141980-4d20b779-f71c-4424-b202-7a9b6826fc13.png
—
Reply to this email directly, view it on GitHub
https://github.com/aztfmod/terraform-azurerm-caf/issues/1173#issuecomment-1141899893,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABD4AEEWZXXCL7QHJH6PNY3VMXMBBANCNFSM5W4Q5YQA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you @LaurentLesle.
If anyone needs a working example:
main.tf:
terraform {
  required_providers {
  }
  required_version = ">= 0.15"
}

provider "azurerm" {
  features {
    key_vault {
      purge_soft_delete_on_destroy = var.provider_azurerm_features_keyvault.purge_soft_delete_on_destroy
    }
  }
}

provider "azurerm" {
  alias                      = "vhub"
  skip_provider_registration = true
  features {}
  subscription_id = data.azurerm_client_config.default.subscription_id
  tenant_id       = data.azurerm_client_config.default.tenant_id
}

data "azurerm_client_config" "default" {}

variable "global_settings" {
  default = {}
}

variable "resource_groups" {
  default = {}
}

variable "logged_user_objectId" {
  default = {}
}

variable "provider_azurerm_features_keyvault" {
  default = {
    purge_soft_delete_on_destroy = true
  }
}

module "caf" {
  source  = "aztfmod/caf/azurerm"
  version = ">=5.4.2"

  providers = {
    azurerm.vhub = azurerm.vhub
  }

  global_settings             = var.global_settings
  resource_groups             = var.resource_groups
  logged_user_objectId        = var.logged_user_objectId
}

terraform.auto.tfvars:
global_settings = {
  default_region = "region1"
  environment    = "dev"
  regions = {
    region1 = "northeurope"
  }
}

resource_groups = {
  region1 = {
    name   = "rg01"
    region = "region1"
  }
}

export TF_VAR_logged_user_objectId=$(az ad signed-in-user show --query id -o tsv --only-show-errors)

or (for powershell)
$env:TF_VAR_logged_user_objectId=$(az ad signed-in-user show --query id -o tsv --only-show-errors)

terraform init
terraform plan

output:
data.azurerm_client_config.default: Reading...
data.azurerm_client_config.default: Read complete after 0s [id=2022-06-03 09:56:17.1526044 +0000 UTC]
module.caf.data.azurerm_client_config.current: Reading...
module.caf.data.azurerm_subscription.primary: Reading...
module.caf.data.azurerm_client_config.current: Read complete after 0s [id=2022-06-03 09:56:18.3891044 +0000 UTC]
module.caf.data.azurerm_subscription.primary: Read complete after 1s [id=/subscriptions/a0a1db5d-####-####-abd4-d953b09bdb81]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # module.caf.random_string.prefix[0] will be created
  + resource "random_string" "prefix" {
      + id          = (known after apply)
      + length      = 4
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = false
      + result      = (known after apply)
      + special     = false
      + upper       = false
    }

  # module.caf.module.resource_groups["region1"].azurecaf_name.rg will be created
  + resource "azurecaf_name" "rg" {
      + clean_input   = true
      + id            = (known after apply)
      + name          = "rg01"
      + passthrough   = false
      + prefixes      = (known after apply)
      + random_length = 0
      + resource_type = "azurerm_resource_group"
      + result        = (known after apply)
      + results       = (known after apply)
      + separator     = "-"
      + use_slug      = true
    }

  # module.caf.module.resource_groups["region1"].azurerm_resource_group.rg will be created
  + resource "azurerm_resource_group" "rg" {
      + id       = (known after apply)
      + location = "northeurope"
      + name     = (known after apply)
    }

Plan: 3 to add, 0 to change, 0 to destroy.

HI @LaurentLesle, this issue appears to be fixed in the provider release 3.9.0 - https://github.com/hashicorp/terraform-provider-azurerm/issues/16982.
What's needed for the CAF module to be updated?

Hi, can you provide a progress update on this fix?

You need to use az-cli version smaller than 2.37 , for example 2.36.
brew uninstall azure-cli  pip3 install azure-cli==2.36.0
This problem because CAF module uses old azurerm provider version = "~> 2.99"
And azure-cli have breaking changes in version 2.37 that renames objectId --> id

Many thanks for the response @MrTolerant , this is certainly the way I'm currently working.
I was curious when the update would take place to either remove the workaround of using TF_VAR_logged_user_objectId=$(az ad signed-in-user show --query id -o tsv --only-show-errors) or terraform plan -var logged_user_objectId=$(az ad signed-in-user show --query id -o tsv --only-show-errors) when using the latest version of azure-cli

hi folks, the problem is fixed after azurerm 3.9. For your testing purposes, you can use the following update branch: int-azrm-3.7.0 which includes 3.9 (despite the name ;)) this should fix the issue for local consumption.


unpairDevice produces bonding unavailable exception for Android versions >= 19

Mobile Device Environment
Provide a list of operating systems on which this issue is relevant.

Device: Android
OS: Version >= 19

Application Environment
Provide information about your development environment:

React Native version: 0.71.7
RN Bluetooth Classic version: 1.60.0-rc.27

Describe the bug
This is sort of a follow up from #252, as the issue hasn't been entirely resolved.
Calling unpairDevice still doesn't seem to work, but this time the problem appears to be that the check for the SDK version is the wrong way round.
While pairDevice errors if Build.VERSION.SDK_INT < 19, unpairDevice instead errors if Build.VERSION.SDK_INT >= 19.
Pairing:
public void pairDevice(String address, Promise promise) {
    if (!checkBluetoothAdapter()) {
        promise.reject(Exceptions.BLUETOOTH_NOT_ENABLED.name(),
                Exceptions.BLUETOOTH_NOT_ENABLED.message());
    } else if (Build.VERSION.SDK_INT < 19) {
        promise.reject(Exceptions.BONDING_UNAVAILABLE_API.name(),
                Exceptions.BONDING_UNAVAILABLE_API.message());
    } else {
       ...
    }
}

Unpairing:
public void unpairDevice(String address, Promise promise) {
    if (!checkBluetoothAdapter()) {
        promise.reject(Exceptions.BLUETOOTH_NOT_ENABLED.name(),
                Exceptions.BLUETOOTH_NOT_ENABLED.message());
    } else if (Build.VERSION.SDK_INT >= 19) {
        promise.reject(Exceptions.BONDING_UNAVAILABLE_API.name(),
                Exceptions.BONDING_UNAVAILABLE_API.message());
    } else {
        ...
    }
}

I'll put up another PR for this - I've tested the change and all seems to be working now.
To Reproduce
Steps to reproduce the behavior:

Pair with a device using pairDevice.
Once paired, attempt to unpair using unpairDevice.
Device is not unpaired.

Expected behavior
Device is unpaired.
Screenshots
N/A
Additional context
N/A

Thanks!


Can auto crawl parent dir

Is support  auto scan parent dir,such as  find a link like  "/templates/2009/index.css", then auto detect
/templates/2009/
/templates/

@ehsandeep

@Mzack9999

This could be a valuable inclusion in the input preprocessing stage to improve the crawling coverage -it can be optional. 💭 What do you think @Mzack9999 ?

I have found that other tools can do this, and I really hope to add this feature. Thank you

This could be a valuable inclusion in the input preprocessing stage to improve the crawling coverage -it can be optional. 💭 What do you think @Mzack9999 ?

I have found that other tools can do this, and I really hope to add this feature. Thank you

Could you tell which ones?

This could be a valuable inclusion in the input preprocessing stage to improve the crawling coverage -it can be optional. 💭 What do you think @Mzack9999 ?

I have found that other tools can do this, and I really hope to add this feature. Thank you

Could you tell which ones?

this https://github.com/chaitin/rad , but it is not opensource。

@Mzack9999  When can this requirement be developed? Thank you.


TS7018 error without file and line number

🔎 Search Terms
filename, noImplicitAny, TS7018, 7018
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about TS7018, line number, filename

⏯ Playground Link
https://www.typescriptlang.org/play?strict=false&strictNullChecks=false&jsx=0&ssl=9&ssc=14&pln=8&pc=7#code/GYVwdgxgLglg9mABAEzgZSgCwOoywBQEMAnQgWwGcAKABxPIoC5FwBrMOAdzAEpEBvAFCJEMYIipQAnjQCmccXVKVEAQgC86xAHI4AIwBWs6Nr5CRI4rKghiSfgF8A3MMQPBrqzbsDXIiMzawHBw2gA0fog0gXok4ZFMOrEAXvEizoLughAIFFCIscSIWuZRzGAgADaVESKJFdW1iAB0ragYOHiYRMrUpSLROpiy1aFNdYGccMSVyGluPBEZQA
💻 Code
function doSthWithParams(params: unknown) {
  if (typeof params !== 'object') {
    return {};
  }

  return {
    c: 'foo',
    p: 'bar',
    s: 'baz',
  };
}

const bar = {
  p: null,
  s: null,
  ...doSthWithParams({
    p: 'hello',
    s: 'world',
  }),
};

🙁 Actual behavior
We're trying to incrementally get our codebase toward the strict mode. When we've enabled noImplicitAny flag we got an error that was very hard to track as it didn't give a file and line number where the error happens.
Object literal's property 'p' implicitly has an 'any' type.

Object literal's property 's' implicitly has an 'any' type.

🙂 Expected behavior
The TS compiler error should point to a file and line number where the error occurs
Additional information about the issue
This happens if noImplicitAny is true and strictNullChecks is not yet enabled

This just looks like a bug - there shouldn't be an error in this code at all.

This just looks like a bug - there shouldn't be an error in this code at all.

What would be the correct behavior here? We get no implicit any error here outside of strictNullChecks (which this issue is about):
const obj = {
  prop: null, // Object literal's property 'prop' implicitly has an 'any' type.(7018)
};

In the OP's example the computed type of bar is:
const bar: {
    c?: undefined;
    p: any;
    s: any;
} | {
    c: string;
    p: string;
    s: string;
}

I guess that p and s in the first member could somehow inherit here a string type. It would require special-casing this here and investigating time in a strictNullChecks: false cases is not something I'm that interested in doing myself :P Is it even worth it at this point? Fixing error positions here seems like a reasonable solution to me.

What would be the correct behavior here?

To be 100% clear, the behavior I'm calling a bug is there appears to be an error on the object literal returned by the function doSthWithParams; bar seems to not be an error.  If either one of the returns in that function is removed, the error in question goes away, which just feels like the kind of spooky action at a distance Ryan always harps against.

Anyway, if the reported behavior isn't a bug, this surely is:
function doSthWithParams(params: unknown) {
  return {
    c: 'foo',
    p: 'bar',
    s: 'baz',
  };
}

const bar = {
  p: null,
  s: null,
  ...doSthWithParams({
    p: 'hello',
    s: 'world',
  }),
};

Variable 'bar' implicitly has an '{ c: string; p: string; s: string; }' type.

Umm... wut

Even more janky fun:

Comment out return {} in the playground from the OP
Observe that bar now becomes an error (the same as the one demonstrated above)
Uncomment the return
All errors are now gone!

I also noticed the above and I think it's fixed with my PR. I don't think it's worth looking more into it - the problem was that the error was reported on an undefined node and that should never happen. When that happens (node === undefined) a compiler-level diagnostic gets created (with file: undefined on it). I think that getDiagnosticsWorker might accidentally be dropping them here but that it only affects a situation that shouldn't exist in the first place.


update travis conventions

update travis CI testing conventions based on guidance from @ocefpaf
@knaaptime

PySAL's .travis.yml

#16

We have moved to github actions.


WIP [DO NOT MERGE]: test build from proposed cibuildwheel branch

This PR is just to test some proposed upstream changes to setup.py in https://github.com/pyFFTW/pyFFTW/pull/323 for compatibility with the recipe here.
I think we may also want to move away from static linking of FFTW to reduce package size (and potential license issue?). We originally did this because conda's NumPy had some kind of monkeypatching of mklfft over numpy.fft. I am pretty sure that is not the case for any recent NumPy on conda-forge, though?

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

everything seems to be working as expected, so I will go ahead and close this


Member updates

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

:heavy_check_mark: Deploy preview for landscape ready!
:hammer: Explore the source changes: c9c3c1edb7a60a6ab63704c47228da082228b370
:mag: Inspect the deploy logs: https://app.netlify.com/sites/landscape/deploys/5fecdc70dabb640007f057ba
:sunglasses: Browse the preview: https://deploy-preview-1944--landscape.netlify.app

LGTM @caniszczyk


releaseSonatypeStagingRepository fails even if release was successful

When I tried to release last time the release build failed with this exception:
Execution failed for task ':releaseSonatypeStagingRepository'.
See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings
> Staging repository is not in desired state [released, not_found]: StagingRepository(id=comtngtech-1552, state=closed, transitioning=false). It is unexpected. Please checkNexus logs using its web interface - it can be caused by validation rules violation. If not, please report it to https://github.com/gradle-nexus/publish-plugin/issues/ with '--info' logs

However, going to the Nexus web interface I saw that the release actually went through successfully. Unfortunately, I can't provide any --info logs, since the release is through now and I can't repeat it.
Could this have been a timeout problem? But AFAIS the default should pull 10 mins for state changes, right? And the whole build had only run 6 mins at this point :thinking:

It looks like it is worth adding closed to the list of statuses in https://github.com/gradle-nexus/publish-plugin/blob/0aea95597e2eeaf9275a286254894bad29b3d1e1/src/main/kotlin/io/github/gradlenexus/publishplugin/internal/StagingRepositoryTransitioner.kt#L33-L34

Thanks for the report. There could be some changes in Nexus, but AFAIR the API call to trigger the release finished not earlier than having the repository in "inTransitioning=true". Here, it is both closed and not transitioning. Assuming there were no other issues (the repo was in the end transited successfully) it is quite strange.
I would be reluctant to just add that status before easing the "--info" log (possibly in the another case, we can wait for it) and even better to find in the Nexus API documentation (maybe one has been created in the meantime) confirming that is possible.

@szpak , transitioning=false  is indeed strange, however, can it be something like "nexus received command to transition the repository, however, the command hasn't yet started"?
In other words, what if it hasn't had a chance to even start the transition?

I've filed https://issues.sonatype.org/browse/NEXUS-34163 to ask for a recommendation regarding the wait for the promotion to complete.

I believe that - in the past - the REST endpoint would wait until the transitioning is started, but I might be wrong or something could have changed. Thanks for creating an issue!
Btw, can you add user szpak to that issue or make it public? I see:

You can't view this issue
It may have been deleted or you don't have permission to view it.

Alternatively, please paste here their answer.

Oh, I just realized I might have used the wrong JIRA instance. I can't add people to the issue, sorry :-/
I wonder if I should have used https://issues.sonatype.org/projects/OSSRH instead.
Let us wait a bit for the response.
Here's what I put to the issue description:

It looks like https://support.sonatype.com/hc/en-us/articles/213465448-Automatically-dropping-old-staging-repositories is the only documentation available for /service/local/staging/bulk/promote.
Unfortunately, it does not clarify the way to wait till the promotion finishes.

https://github.com/gradle-nexus/publish-plugin uses this API to release repositories (autoDropAfterRelease:true)

The code calls {{/service/local/staging/bulk/promote}}, and then waits for some time and checks the repository status via {{staging/repository/}} requests.

Based on the past experience, it was expected to observe the following outcomes:
a) any state, transitioning=true. It looks like the repository is transitioning, so wait a bit.
b) released. Ok, the repository has been released, end of wait.
c) 404 NOT_FOUND. It means the repository has already been dropped, end of wait.

However, recently there was a case when Nexus returned {{id=comtngtech-1552, state=closed, transitioning=false}} during promotion.
In fact, the repository has been successfully promoted, however, it was unexpected to observe transitioning=false state.

Unfortunately, there's no much logs for that case, and
https://github.com/gradle-nexus/publish-plugin/issues/146 is the only information available.

Question: Could you please clarify what is the recommended way to wait for promotion to complete? Is state=closed & transitioning=false a valid outcome after a successful staging/bulk/promote request?

So far they thanked me for filing the issue and responded they no longer maintain v2 APIs, and they suggest users to migrate to Repository v3 which has better APIs for staging: https://help.sonatype.com/repomanager3/nexus-repository-administration/staging
I'm not sure it applies to OSSRH since oss.sonatype.org still uses Nexus 2.15.1-02, so I asked for a clarification.

Did they ever get back to you? Otherwise, maybe really file the issue at https://issues.sonatype.org/projects/OSSRH? Because there they can hardly say that you should upgrade to v3, right? :wink:

Their answer indeed was "we recommend all users migrate to Repository v3", and they ignored my request to reopen the issue 🤷♂
Let me file a new one as "clarify API or upgrade Central to v3" :)

I've filed https://issues.sonatype.org/browse/OSSRH-84806

Thanks a lot for following up on it, really appreciated :slightly_smiling_face:

@codecholeric , could you please clarify if you observed the issue with oss.sonatype.org or with s01.oss.sonatype.org?

@codecholeric , up? Could you please clarify if you observed the issue with oss.sonatype.org or with s01.oss.sonatype.org?

I'm going to close this issue due to inactivity. @codecholeric, if you're still facing the problem please comment here.


Produce gives an error even when successfully creating an app on iTunes Connect

When running produce to create an app on iTunes connect, it seems like you get an error even though the application was successfully created.
I have ran the test with and without skipping the dev center. Without skipping the dev center, I had a proper output, no error.
Check the output below for the information.
New Issue Checklist

[X] Updated fastlane to the latest version
[X] I have read the Contribution Guidelines

Issue Description
Complete output when running fastlane, including the stack trace and command used
[19:04:07]: Creating new app 'XXX' on iTunes Connect
[19:04:08]: Waiting for the newly created application to be available on iTunes Connect...
[19:04:18]: Waiting for the newly created application to be available on iTunes Connect...
[19:04:29]: Waiting for the newly created application to be available on iTunes Connect...
[19:04:39]: Waiting for the newly created application to be available on iTunes Connect...
[19:04:50]: Waiting for the newly created application to be available on iTunes Connect...
[19:05:00]: Waiting for the newly created application to be available on iTunes Connect...
[19:05:11]: Waiting for the newly created application to be available on iTunes Connect...
[19:05:22]: Successfully created new app 'XXXX' on iTunes Connect with ID XXXX

Looking for related GitHub issues on fastlane/fastlane...

➡  pilot upload: undefined method `apple_id' for nil:NilClass
   https://github.com/fastlane/fastlane/issues/3311 [closed] 1 💬
   08 Mar 2016

➡  Fastlane still use old Apple account instead of new Apple Account
   https://github.com/fastlane/fastlane/issues/5400 [open] 2 💬
   2 weeks ago

➡  🔑 Spaceship: NoMethodError being thrown in setup_screenshots_for(row)
   https://github.com/fastlane/fastlane/issues/5676 [closed] 2 💬
   2 weeks ago

and 12 more at: https://github.com/fastlane/fastlane/search?q=undefined%20method%20%60apple_id'%20for%20nil&type=Issues&utf8=✓
/Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/lib/produce/itunes_connect.rb:53:in `create_new_app': [!] undefined method `apple_id' for nil:NilClass (NoMethodError)
	from /Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/lib/produce/itunes_connect.rb:12:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/lib/produce/manager.rb:8:in `start_producing'
	from /Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/lib/produce/commands_generator.rb:37:in `block (2 levels) in run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
	from /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.50.3/lib/fastlane_core/ui/fastlane_runner.rb:36:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/lib/produce/commands_generator.rb:127:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/lib/produce/commands_generator.rb:11:in `start'
	from /Library/Ruby/Gems/2.0.0/gems/produce-1.2.0/bin/produce:6:in `<top (required)>'
	from /usr/local/bin/produce:23:in `load'
	from /usr/local/bin/produce:23:in `<main>'

Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Command was:
produce -u XXX -a XXX -q "XXX" -b XXX -d

+----------------+------------------------+
|        Summary for produce 1.2.0        |
+----------------+------------------------+
| username       | XXX|
| app_identifier | XXX       |
| app_name       | XXX  |
| team_id        | XXX             |
| skip_devcenter | true                   |
| sku            | XXX             |
| language       | English                |
| skip_itc       | false                  |
+----------------+------------------------+

Environment
fastlane version (run fastlane -v): produce 1.2.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? No
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? No

Interesting, it seems like produce can't find the newly created application. Did this happen before?

We have the same issue.
It started today.
produce ver 1.2.0
[12:00:50][Step 1/1] [05:00:50]: Creating new app 'XXX' on iTunes Connect

[12:00:51][Step 1/1] Looking for related GitHub issues on fastlane/fastlane...
[12:00:51][Step 1/1]
[12:00:52][Step 1/1] ������  undefined method `fetch' for nil:NilClass
[12:00:52][Step 1/1]    https://github.com/fastlane/fastlane/issues/5677 [open] 1 ����
[12:00:52][Step 1/1]    2 weeks ago
[12:00:52][Step 1/1]
[12:00:52][Step 1/1] ������  Produce: undefined method `[]=' for nil:NilClass
[12:00:52][Step 1/1]    https://github.com/fastlane/fastlane/issues/5875 [closed] 6 ����
[12:00:52][Step 1/1]    5 hours ago
[12:00:52][Step 1/1]
[12:00:52][Step 1/1] ������  undefined method `map' for nil:NilClass
[12:00:52][Step 1/1]    https://github.com/fastlane/fastlane/issues/5817 [closed] 23 ����
[12:00:52][Step 1/1]    19 hours ago
[12:00:52][Step 1/1]
[12:00:52][Step 1/1] and 158 more at: https://github.com/fastlane/fastlane/search?q=undefined%20method%20%60[]='%20for%20nil&type=Issues&utf8=���
[12:00:52][Step 1/1] /Users/vagrant/agent/work/b227cdd6c1438eaa/vendor/bundle/ruby/2.0.0/gems/spaceship-0.31.6/lib/spaceship/tunes/tunes_client.rb:232:in `create_application!': [!] undefined method `[]=' for nil:NilClass (NoMethodError)

@drorbiran did https://github.com/fastlane/fastlane/pull/5877 fix your issue? Run gem update spaceship to get spaceship 0.31.10 and let me know.

@asfalcone The update solved it. Thanks!

@KrauseFx yes, first time it happened to me. I got some stuff to create and test today, let me try it again with skipping dev center and then I'll tell you if it works or not.
I know exactly the steps I took to try it out.

I did some other test and didn't run into any issue related to that. Must've been a weird ITC response.
Thanks guys!

@GabrielCartier Awesome! Thanks so much for following up. So glad you got up and running.


Add MVP version of FoodRem UI

Let's create an MVP for the UI first.

Closes #197.

Codecov Report

Merging #198 (c3627fe) into master (43cde03) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #198   +/-   ##
=========================================
  Coverage     60.59%   60.59%
  Complexity      478      478
=========================================
  Files           102      102
  Lines          1713     1713
  Branches        173      173
=========================================
  Hits           1038     1038
  Misses          615      615
  Partials         60       60

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Rename Amazon storage manager AE models

This patch accompanies the renaiming of Amazon BlockStorageManager
into StorageManager::Ebs. It merely renames the corresponding
automation models.
@miq-bot label providers/amazon,providers/storage,automate/model,wip

This PR depends on https://github.com/ManageIQ/manageiq-providers-amazon/pull/107, which has received the first "ok". Please review this change as well.
@miq-bot remove_label wip

@blomquisg It looks like this PR has a codependency with https://github.com/ManageIQ/manageiq/pull/13549, so they both need to be merged before their tests will pass. Should we just merge them while red to see if the result is green?

@roliveri with yesterday's patches we did it like you suggested. Alternatively, I can make a PR with all the changes in the currently opened PRs to make sure we are safe.

@gberginc Given that the remaining 3 PRs are in the same repo, combining them into a single PR might be the safer way to go. Unless anyone has any objections to that.

@roliveri ok, let's see if this will work; I'll send you a message once I have the new PR ready

Closing in favour of https://github.com/ManageIQ/manageiq/pull/13569
@roliveri in my local environment, both of the failing tests were passing so hopefully they will in the above PR as well :-D


The delete button doesn't work for nuget package references or project references in the solution explorer

It just no-ops. Assemblies work though...

Projects used to work...


Variable attributes not being propagated in findall?

Trealla:
?- freeze(X, (X < 5)), findall(X, between(1, 20, X), Xs).
   Xs = [1,2,3,4,5,6,7,8,9,...], freeze(X,X<5).
% expected Xs = [1,2,3,4]

Scryer:
?- freeze(X, (X < 5)), findall(X, between(1, 20, X), Xs).
   Xs = [1,2,3,4], freeze:freeze(X,X<5).

SWI:
?- freeze(X, (X < 5)), findall(X, between(1, 20, X), Xs).
   Xs = [1, 2, 3, 4], freeze(X, X<5).

Nice, thanks!


Tabular: Fix GPU specification in FastAI to respect num_gpus

Issue #, if available:
Description of changes:

Fix GPU specification in FastAI to respect num_gpus
Previously if GPU was present, it would always be used regardless of num_gpus setting
Fixed edge case inefficiency in ensemble_selection when identical models caused selection to choose all of them due to rounding error instead of choosing just a single one.
Optimized ensemble selection to prioritize models already in ensemble when ties occur.

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

Job PR-1421-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1421/1/index.html

Job PR-1421-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1421/2/index.html


feat: Added Elestio as one-click deploy option

closes #4867

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes

Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[ ] I have run npm run test to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Hi - we don't generally add this type of thing to the README.
You could consider a PR on the docs on the website instead: https://nodered.org/docs/getting-started/

Hey @knolleary, Thank you so much for the comment. I will make a pr to the docs :D


Add SURFRAD page

closes #242

Note that the SURFRAD website only mentions 8 stations while we have 10 in the list

Note that the SURFRAD website only mentions 8 stations while we have 10 in the list

Two of the stations are retired/inactive. This info is note in the Time period column, so I think this is ok.

Thanks @IoannisSifnaios 🥳


Add CodePoint Type

This commit adds a CodePoint new type.
This type will not be used in performance critical code. I keep wanting to have it for error messages (particularly in the mapping tables), and a few non-performance critical methods.
This commit also adds the scalacheck and tests module.

Thanks for the iteration :) I forgot to mention, the scaladocs and comments are really great, makes for an enjoyable review :D

Thanks! I really appreciate the feedback


spring-cloud-starter-bus-amqp is broken?

I created a project with spring-initializr and added just a single starter.
This added this:
<dependencyManagement>
	<dependencies>
		<dependency>
			<groupId>org.springframework.cloud</groupId>
			<artifactId>spring-cloud-dependencies</artifactId>
			<version>Brixton.SR2</version>
			<type>pom</type>
			<scope>import</scope>
		</dependency>
	</dependencies>
</dependencyManagement>

and this:
	<dependency>
		<groupId>org.springframework.cloud</groupId>
		<artifactId>spring-cloud-starter-bus-amqp</artifactId>
	</dependency>

to my pom (I'll attach full pom as well later).
I guess that seems okay and as expected.
When I run this empty app however it crashes with some nasty error about failing to create JMX releated bean.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.boot.autoconfigure.admin.SpringApplicationAdminJmxAutoConfiguration': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private org.springframework.jmx.export.MBeanExporter org.springframework.boot.autoconfigure.admin.SpringApplicationAdminJmxAutoConfiguration.mbeanExporter; nested exception is org.springframework.beans.factory.NoUniqueBeanDefinitionException: No qualifying bean of type [org.springframework.jmx.export.MBeanExporter] is defined: more than one 'primary' bean found among candidates: [mbeanExporter, integrationMbeanExporter, endpointMBeanExporter]
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:334) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1214) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:543) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:772) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:839) ~[spring-context-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:538) ~[spring-context-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118) ~[spring-boot-1.3.6.RELEASE.jar:1.3.6.RELEASE]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:760) [spring-boot-1.3.6.RELEASE.jar:1.3.6.RELEASE]
	at org.springframework.boot.SpringApplication.createAndRefreshContext(SpringApplication.java:360) [spring-boot-1.3.6.RELEASE.jar:1.3.6.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:306) [spring-boot-1.3.6.RELEASE.jar:1.3.6.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1185) [spring-boot-1.3.6.RELEASE.jar:1.3.6.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1174) [spring-boot-1.3.6.RELEASE.jar:1.3.6.RELEASE]
	at com.example.DemoBusApplication.main(DemoBusApplication.java:18) [classes/:na]
Caused by: org.springframework.beans.factory.BeanCreationException: Could not autowire field: private org.springframework.jmx.export.MBeanExporter org.springframework.boot.autoconfigure.admin.SpringApplicationAdminJmxAutoConfiguration.mbeanExporter; nested exception is org.springframework.beans.factory.NoUniqueBeanDefinitionException: No qualifying bean of type [org.springframework.jmx.export.MBeanExporter] is defined: more than one 'primary' bean found among candidates: [mbeanExporter, integrationMbeanExporter, endpointMBeanExporter]
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:573) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:88) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:331) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	... 17 common frames omitted
Caused by: org.springframework.beans.factory.NoUniqueBeanDefinitionException: No qualifying bean of type [org.springframework.jmx.export.MBeanExporter] is defined: more than one 'primary' bean found among candidates: [mbeanExporter, integrationMbeanExporter, endpointMBeanExporter]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.determinePrimaryCandidate(DefaultListableBeanFactory.java:1255) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.determineAutowireCandidate(DefaultListableBeanFactory.java:1216) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1124) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1014) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:545) ~[spring-beans-4.2.7.RELEASE.jar:4.2.7.RELEASE]
	... 19 common frames omitted

I was expecting the empty app to not do anything, or, perhaps crash with some error for not being able to connect to rabbitmq unsintance until I install and configure it somehow. I was not expecting a problem with JMX beans.
Not sure who this error should be blamed on. Is it initializer not generating proper pom? Is it the spring-cloud-starter-bus-amqp? Something else?
I just made my best guess and raised this against 'spring-cloud-starters' as I don't get this with other starters so I'm inclined to blame the starter for this.

This is the full contents of the pom.xml as generated by initializr app.
https://gist.github.com/kdvolder/55e0f196f5db378cb43c698300022714

This appears to be some kind of conflict with the SpringApplicationAdminJmxAutoConfiguration stuff which is enabled when running applications from STS using spring-boot-dahsboard. STS turns on this functionality when launching a boot app by default. It is needed to manage the boot apps lifecycle (so IDE can request app to do a clean shutdown), discover info about running app (such as the port a webby app is running on).
When I disable these JMX related features in STS then the error goes away. (This however results in some loss of functionality in STS boot dashboard).
Any idea on how the spring-boot life-cycle management MBeans can be made to play nicely together with spring-cloud-starter-bus-amqp?

You'd have to get in touch with the STS and/or Spring Boot team. My guess is that you'd have the problem even without amqp if you had a plain integration app.

Thanks, but I'm actually on the STS team :-)
We need that 'admin' JMX bean which spring-boot provides. I'm trying to figure out who/why these other beans are getting turned on and who to talk to about figuriing out some kind of a solution to this conflict (other than just disabling a bunch of STS functionality to avoid it).
But I guess this problem isn't from the starter itselff but one part of spring-boot conflicting with another part of spring-boot (i.e. not a spring-cloud-specific problem)?

Sorry for not recognizing you Kris. I didn't get your previous message when I had written mine. The bus pulls in spring-cloud-starter-stream-rabbit and spring-cloud-stream and spring-integration-core. We don't do anything specific with jmx. I guess I'm not sure what to do, though I'm not the expert. @dsyer might have a better idea.

Closed in favor of https://github.com/spring-projects/spring-boot/pull/6328.
Thank you for spotting such a nasty regression. The only problem was that we don't have enough test coverage. But will we have it anyway ever?.. :smile: