Use databroker.temp instead of sqlite databroker.

In the test suite, we currently reach into databroker's test fixtures and make a databroker using its deprecated sqlite backend. In this PR, we use databroker.temp() instead, which currently generates a msgpack-backed catalog.

This seems good in general (avoid using another library's deprecated object; avoid reaching into another library's test fixtures) but the immediate motivate is that the sqlite backend frequently generates cursor TimeoutErrors in CI. See for example #1429.

Power-cycled to re-run CI

I was able to replicate the failed test on my system and investigate. It seems that what is happening is that test_broker_base is failing because the BrokerCallbackBase object is trying to call db.fill_events, which has been deprecated for the v1 databroker (but probably not for the sql databroker I guess). Therefore, you get a NotImplementedError.
Changing the db fixture from the SQL databroker to the temp() databroker has correctly exposed that test_broker_base is failing. Indeed, the BrokerCallbackBase has probably been broken for quite some time if you use a v1 databroker.
I think that the failing test should be fixed in a different PR, and that this test fix should just be merged. The failing test is an indication of how over-due this PR really is...

Maybe test_broker_base could be marked as xfail for NotImplementedError so that it doesn't confuse people while a fix for that is discussed. I haven't though enough about Databroker to know what the solution should be.

Fix pushed. IF CI is happy, merge at will whoever sees this first. :-)

Thanks for pushing on this @cjtitus!


Proposal to create a controlled vocabulary for content description

This proposal is intended to help resolve several other open issues: #230 (Problems with Iptc4xmpExt:CVterm), #244 (Outdated Link in Notes for Iptc4xmpExt:CVterm), #200 (Term needed to designate when an image or ROI is a label), and #166 (View for "in habitat").
Background
During the development process of the subjectPart controlled vocabulary, the community was interested in providing a way to indicate that a particular image or region of interest within an image contained something that was not part of the organism.  Another situation was to indicate that the photograph was of the habitat of the organism (either the organism wasn't in the habitat photo, or the organism was in the photo, but the entire organism was not the primary subject of the image -- the habitat was). Photos of scale bars and color scales would be similar to the label use case, and an audio analog would be to indication that a region of interest in the recording was a voice introduction.
The Task Group decided that these terms were out of scope for a vocabulary about subject parts, since they didn't actually involve any part of the organism. However, it recommended that the Audubon Core Maintenance Group consider other alternative methods to make it possible to filter for these features.
Proposal
Create a Content Description controlled vocabulary. The concept IRIs would be used as values for Iptc4xmpExt:CVterm (defined as "A term to describe the content of the image by a value from a Controlled Vocabulary") and controlled value strings would be used as values for a newly minted term: ac:CVtermLiteral (defined below).
In the event that there were multiple values for Iptc4xmpExt:CVterm, the normal rules for serializing lists in that serialization would apply (e.g. RDF Turtle, JSON-LD). If there were multiple values for ac:CVtermLiteral, they MAY be concatenated and pipe separated if the user chose not to implement one of the methods described in Section 3.2 (Tabular serializations) of the Audubon Core Structure guide.
The revised definitions remove recommended vocabularies from the term metadata. If Audubon Core wishes to recommend vocabularies, it should do so via informative documents that do not require going through the standards process to change them. The URLs for many of the currently recommended vocabularies are broken (see Issue #244 for example) and others aren't actively maintained. The current recommendations are: the NASA Global Change Master Directory (GCMD; http://gcmd.nasa.gov/), Subject Categories defined in Key to Nature (K2N; http://www.keytonature.eu/wiki/Subject_Category), the BioComplexity Thesaurus; https://www2.usgs.gov/core_science_systems/csas/biocomplexity_thesaurus/, the Description Type GBIF Vocabulary; http://rs.gbif.org/vocabulary/gbif/description_type.xml, the TDWG Species Profile Model; http://rs.tdwg.org/ontology/voc/SPMInfoItems.rdf, the Plinian Core; https://github.com/tdwg/PlinianCore/wiki, the European Environmental Agency GEneral Multilingual Environmental Thesaurus (GEMET; http://www.eionet.europa.eu/gemet), and the Long Term Ecological Research Network Controlled Vocabulary (LTER; http://vocab.lternet.edu/).
The changes proposed here simplifies use of the terms. Either a globally unique IRI is used as a value for Iptc4xmpExt:CVterm (as IPTC expects), a controlled value string from the new AC Content Description vocabulary (initial values defined below) is used as a value for ac:CVterm, or a controlled value string for another vocabulary is used as a value for ac:CVterm and that vocabulary is identified using ac:subjectCategoryVocabulary.
Term revisions
New text is in italics. Removed text is in ~strikethrough~. The definition of Iptc4xmpExt:CVterm remains unchanged from that given by the IPTC.
Term name: Iptc4xmpExt:CVterm
Label: Subject Category
IRI: http://iptc.org/std/Iptc4xmpExt/2008-02-29/CVterm
Required: No
Repeatable: Yes
Definition: A term to describe the content of the image by a value from a Controlled Vocabulary.
Usage: Values MUST be IRIs from a controlled vocabulary of subjects to support broad classification of media items. IRIs ~Terms~ from the Audubon Core Content Description controlled vocabulary are preferred, but other ~various~ controlled vocabularies may be used as long as the term is uniquely identified by an IRI. This term MAY be used to describe the content of a region of interest within an image. ~AC-recommended vocabularies are preferred and MAY be unqualified literals (not a full URI). For terms from other vocabularies either a precise URI SHOULD be used, or, as long as all unqualified terms in all vocabularies are unique, metadata SHOULD provide the source vocabularies using the Subject Category Vocabulary term. The value SHOULD be a string, whose text can also be in the form of a URL.~ These guidelines on value format are less restrictive than is specified by the IPTC guidelines.
~Notes: Recommended sets include: the NASA Global Change Master Directory (GCMD; http://gcmd.nasa.gov/), Subject Categories defined in Key to Nature (K2N; http://www.keytonature.eu/wiki/Subject_Category), the BioComplexity Thesaurus; https://www2.usgs.gov/core_science_systems/csas/biocomplexity_thesaurus/, the Description Type GBIF Vocabulary; http://rs.gbif.org/vocabulary/gbif/description_type.xml, the TDWG Species Profile Model; http://rs.tdwg.org/ontology/voc/SPMInfoItems.rdf, the Plinian Core; https://github.com/tdwg/PlinianCore/wiki, the European Environmental Agency GEneral Multilingual Environmental Thesaurus (GEMET; http://www.eionet.europa.eu/gemet), and the Long Term Ecological Research Network Controlled Vocabulary (LTER; http://vocab.lternet.edu/). The vocabulary may include major taxonomic groups (such as "vertebrates" or "fungi") or ecosystem terms ("savannah", "temperate rain forest", "forest fires", "aquatic vertebrates"). Other formal classifications (published in print or online) such as habitat, fuel, invasive species, agroproductivity, fisheries, migratory species etc. are also suitable.~
Type: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Term Name: ac:subjectCategoryVocabulary
Label: Subject Category Vocabulary
IRI: http://rs.tdwg.org/ac/terms/subjectCategoryVocabulary
Required: No
Repeatable: ~Yes~ No
Definition: Any controlled vocabulary ~or formal classification~ from which values for ac:CVterm ~terms in the Subject Category~ have been drawn.
Usage: The value SHOULD be a stable URL for the vocabulary if one is available.
Notes: If controlled string values for ac:CVterm are taken from the Audubon Core Subject Category controlled vocabulary, it is not necessary to provide a value for this property. If pipe separated strings are used to provide multiple values for ac:CVterm, this term MUST NOT be repeated. It MAY be repeated if data structuring allows particular ac:CVterm string values to be associated with particular values for this term. ~The AC recommended vocabularies do not need to be cited here.  There is no required linkage between individual Subject Category terms  and the vocabulary; the mechanism is intended to support discovery of  the normative URI for a term, but not guarantee it.~
New terms
Term name: ac:CVtermLiteral
Label: Subject Category (literal)
IRI: http://rs.tdwg.org/ac/terms/CVtermLiteral
Required: No
Repeatable: Yes
Definition: A term to describe the content of a image or a region of interest within an image using a controlled value string.
Usage: Values SHOULD be selected from the Audubon Core Content Description controlled vocabulary or a vocabulary that can be identified using ac:subjectCategoryVocabulary. If a value is from the Audubon Core Content Description controlled vocabulary, it is not necessary to provide a value for ac:subjectCategoryVocabulary. Multiple values MAY be provided and separated by space vertical bar space ( | ), however they MUST be from a single vocabulary. It is best practice to use Iptc4xmpExt:CVterm instead of ac:CVtermLiteral whenever practical.
Type: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
The following terms would be included in the initial Content Description controlled vocabulary (with others potentially added in the future). The type of all terms in the vocabulary is http://www.w3.org/2004/02/skos/core#ConceptScheme .
Label: Label
Definition: physical text providing metadata about the focal resource
Note: The focal resource MAY be any kind of specimen.
Controlled string: label
Label: Context
Definition: a depicted feature that is the context in which the focal resource was located
Usage: If the media item includes a depiction of the focal resource, the focal resource SHOULD NOT be the main feature of the media item.
Examples: the habitat in which an organism was found, the strata from which a fossil or mineral sample was removed
Controlled string: context
Label: Scale Bar
Definition: a linear graphic used to associate size with a dimension of the media item
Example: a ruler
Controlled string: scaleBar
Label: Color Bar
Definition: chromatic graphic used to calibrate the color profile of an image with the actual color of the object
Controlled string: colorBar
Label: Spoken Description
Definition: audio media that contains a voice description of the content of the media item
Controlled string: spokenDescription
Label: Organism Part
Definition: all or part of an organism
Usage: The media item primarily depicts some part of a organism. If the organism is not the main feature that is depicted, context SHOULD be used instead.
Note: The organism MAY be living or dead, and MAY be preserved. If this value is used, the terms ac:subjectPart/ac:subjectPartLiteral and ac:subjectOrientation/ac:subjectOrientationLiteral SHOULD be used to provide more detailed information about what precisely is depicted and how the depicted part is oriented.
Controlled string: organismPart
Ping @ben-norton with respect to lists as values.
Refer to https://github.com/tdwg/camtrap-dp/issues/191#issuecomment-1030732612

May I suggest changing spokenIntroduction to spokenDescription? "intro" implies it comes before something, but the description may come at the end or elsewhere.

@danstowell Yes, makes sense to me.

Changed proposal to use spokenIntroduction as suggested by @danstowell.
Capitalized human-readable labels to conform to existing practice.

I have completed revisions of this proposal to implement the decision made at the 2022-11-10 Audubon Core Maintenance Group working session: that we should mint a new term ac:CVTermLiteral for literal values rather than recommending using ac:tag as in the original proposal in order to follow the existing AC patterns for literal and IRI-valued terms (action item D on the agenda).
Note that as a part of this proposal I have included a general cleanup of how Iptc4xmpExt:CVterm is to be used. Originally there was a cludgy system where one could use either an IRI value or a string from one of the AC recommended vocabularies. The term ac:subjectCategoryVocabulary was then used to provide clues about what vocabulary was intended when a string value was provided.
Since we now have the ability to indicate whether the term value should be an IRI or a controlled value string, the proposal allows for three straightforward options for indicating the subject category:

Provide a full IRI for Iptc4xmpExt:CVterm. No other information is required as the values would be globally unique and self describing (if the IRIs dereference).
Use a controlled value string from the new controlled vocabulary we are creating. In that case, no other information is required and it isn't necessary to provide a value for ac:subjectCategoryVocabulary; the AC vocabulary would be assumed.
Use a controlled value string from any other controlled vocabulary and indicate what that vocabulary is by providing a value for ac:subjectCategoryVocabulary.

There is a bit of complexity introduced by allowing multiple values to be provided for ac:CVtermLiteral using space bar space separation. In simple text based systems, there wouldn't be a way to associate a particular ac:CVtermLiteral value with a particular ac:subjectCategoryVocabulary value. So one must either limit the delimited strings to a single vocabulary, or use some structured data system that allows the controlled values to be associated with their vocabularies. No such restriction exists for IRI values -- one reason why they are preferred.

Updated the proposal to make it clear that the terms may be used with regions of interest within an image in addition to an entire image.

Created usage examples as requested at AC MG meeting. Edited proposal to link to examples.


Add busy retry for container locks

Corresponding native PR.
Also:

add container.abandonChanges
make vacuum an instance method rather than static method on DgnDb.

You meant to target imodel02 branch, not master, correct?

Yes. Already fixed.


Record not receiving MIDI from TRS input

When recording in any mode (step/overdub/overwrite) I am unable to get the Performer to respond to midi events coming in on the TRS input. I have experimented with channel settings, omni etc. Makes no difference.
I am getting midi input on TRS in general. Midi/CV tracks are working, routing is working, learn in routing is working etc. Arpeggiator is working through TRS midi.
But when trying to record to a track using the TRS midi input: Nothing.
When attaching a keyboard via USB it works without a hitch.
As I recall, this used to work, so perhaps a bug has been introduced with the  updates made to MIDI in the last versions?
Using USB means I cannot simultanously use my Launchpad as well as other drawbacks, so having midi through USB for recording is a big advantages.
Kind regards, Rolf

Recording via TRS MIDI works fine for me. Can you try again with an empty project?

Hi, I just encountered same issue on a project I'm working on, but discovered that i can't record incoming MIDI from the TRS input if I have any of the tracks set as a MIDI/CV track. Even if I want to capture the MIDI on another track it won't let me. In my case, I have Tracks 6-8 receiving MIDI from CH 1-3 of a Yamaha QY300 sequencer, but I also wanted to capture parts of the pattern coming from MIDI ch 1 onto, say, Track 1 of the Westlicht.
I suppose that makes sense (although i don't have full clarity of why it does...something about MIDI loop or feedback I suppose?), but also, it would be nice to be able to use some tracks of the Westlicht as real-time MIDI/CV converter (which it does very well), and also still be able to capture incoming MIDI on another track.


Compiling in Java 8 - invalid ELF header (Possible cause: endianness mismatch)

Hi,
I am developing a Java Application with library jpy.jar.
I added the dependency through maven to jpy.jar and called PyLib.startPython(). Then, build process complained asking me to set system property jpy.jpyLib. Then, I added the location of jpy.jar (jpy-0.9-SNAPSHOT.jar) as system property jpy.jpyLib. Now, I get the following new error during maven build.
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.1.1:java (default) on project org.example.learn2: An exception occured while executing the Java class. null: InvocationTargetException: ~/jpy/lib/jpy-0.9-SNAPSHOT.jar:~/jpy/lib/jpy-0.9-SNAPSHOT.jar: invalid ELF header (Possible cause: endianness mismatch) -> [Help 1]
Am I doing something wrong? How to fix this?

What host OS are you running on? (For example, Windows 64-bit, macOS, Ubuntu 14.10 64-bit.) Only certain native libraries are built and distributed with JPY at the moment and I'm guessing it's trying to use the wrong one.

@madhawav it is quite easy to build jpy for Unix/Darwin, please have a look into the README.

Hi,
I managed to get this issue solved.
The path to "jpy.cpython-35m-x86_64-linux-gnu.so" should be provided as system property "jpy.jpyLib" instead of the *.jar file I have provided previously.
Thanks


AutoBuilder.conifgureCustom doesn't support flipping

It's not possible to flip path with configureCustom, since it doesn't get BooleanSupplier of shouldFlip, insteaf it's set it to false.
The desired solution is to add it as a pram to the method, like all other config methods.

The flipping happens within the command itself, on initialize. It is not possible to do this in AutoBuilder, since it can be used to build commands when code first starts, and the robot does not yet know which alliance it is on.

It doesn't flip the initial pose.

Oh, for odom reset? Yeah, you're right. Can fix that.


Xamarin.UITest.XDB.Exceptions.DeviceAgentException : Unable to verify app installation state  (Xamarin.UITest package to 3.0.4)

With Xamarin.UITest package to 3.0.4 there is an issue running Xamarin.UITests on all iOS devices/Simulators. The following error occurs:
Xamarin.UITest.XDB.Exceptions.DeviceAgentException : Unable to verify app installation state

ExitCode: 134

  Reason: no suitable image found.  Did find:
  Referenced from: /var/folders/g1/1jz4c5yd6bx41bgkjh7vmdw80000gn/T/xdb/DeviceAgent.iOS.Dependencies/0a3ddc92d1ddf25e2059c72229db762c/bin/iOSDeviceManager
	/private/var/folders/g1/1jz4c5yd6bx41bgkjh7vmdw80000gn/T/xdb/DeviceAgent.iOS.Dependencies/0a3ddc92d1ddf25e2059c72229db762c/bin/../Frameworks/FBControlCore.framework/Versions/A/FBControlCore: code signature invalid for '/private/var/folders/g1/1jz4c5yd6bx41bgkjh7vmdw80000gn/T/xdb/DeviceAgent.iOS.Dependencies/0a3ddc92d1ddf25e2059c72229db762c/bin/../Frameworks/FBControlCore.framework/Versions/A/FBControlCore'
	/private/var/folders/g1/1jz4c5yd6bx41bgkjh7vmdw80000gn/T/xdb/DeviceAgent.iOS.Dependencies/0a3ddc92d1ddf25e2059c72229db762c/bin/../Frameworks/FBControlCore.framework/Versions/A/FBControlCore: stat() failed with errno=1
dyld: Library not loaded: @rpath/FBControlCore.framework/Versions/A/FBControlCore

This was talked about here:
https://github.com/microsoft/appcenter/issues/829
The resolution to this issue is to downgrade to Xamarin.UITest package to 3.0.3 to keep running the tests.
Please fix it in the next release, and if more information is requested please feel free to ask.

This is a very problematic issue, and downgrading is not a option (3.0.4 fixed many compatibility issues). This is gradually blocking all iOS testing.

UITest 3.0.5 has been released. Could you both test with that and let us know whether you are still experiencing any problems please?

@jonstoneman the 3.0.5 update fixes the issue for me, thanks!

3.0.5 working for me as well. Thank you so much!

@jonstoneman
Even after updating to Xamarin.UITest Version 3.0.5, I am still seeing the following when trying to launch Xamarin.UITest from
Visual Studio for Mac 8.3.7 (Build 1)
XCode Version 11.2.1
to
iPhone6s - iOS 13.3
`{Xamarin.UITest.XDB.Exceptions.DeviceAgentException: Failed to launch simulator
ExitCode: 134
Reason: no suitable image found.  Did find:
Referenced from: /var/folders/sl/x1qg9tt511n7gzx43n2vcb_m0000gn/T/xdb/DeviceAgent.iOS.Dependencies/42d07e9bfef833f40c0ad2b89bf48b10/bin/iOSDeviceManager
/private/var/folders/sl/x1qg9tt511n7gzx43n2vcb_m0000gn/T/xdb/DeviceAgent.iOS.Dependencies/42d07e9bfef833f40c0ad2b89bf48b10/bin/../Frameworks/FBControlCore.framework/Versions/A/FBControlCore: code signature invalid for '/private/var/folders/sl/x1qg9tt511n7gzx43n2vcb_m0000gn/T/xdb/DeviceAgent.iOS.Dependencies/42d07e9bfef833f40c0ad2b89bf48b10/bin/../Frameworks/FBControlCore.framework/Versions/A/FBControlCore'
/private/var/folders/sl/x1qg9tt511n7gzx43n2vcb_m0000gn/T/xdb/DeviceAgent.iOS.Dependencies/42d07e9bfef833f40c0ad2b89bf48b10/bin/../Frameworks/FBControlCore.framework/Versions/A/FBControlCore: stat() failed with errno=1
dyld: Library not loaded: @rpath/FBControlCore.framework/Versions/A/FBControlCore`

@seangriffin2
Let's collect some more information about iOSDeviceManager and its dependent libraries.
Please verify the version of iOSDeviceManager:
{
  "VERSION" : "3.7.3",
  "GIT_REMOTE_ORIGIN" : "git@github.com:calabash/iOSDeviceManager.git",
  "GIT_BRANCH" : "tag/3.7.3",
  "GIT_SHORT_REVISION" : "47f494b"
}

If you don't see version 3.7.3 then you haven't properly updated to 3.0.5.
$ /var/folders/sl/x1qg9tt511n7gzx43n2vcb_m0000gn/T/xdb/DeviceAgent.iOS.Dependencies/42d07e9bfef833f40c0ad2b89bf48b10/bin/iOSDeviceManager version -j

Check the code signing information for the FBControlCore framework:
$ codesign --display --verbose=4
/private/var/folders/sl/x1qg9tt511n7gzx43n2vcb_m0000gn/T/xdb/DeviceAgent.iOS.Dependencies/42d07e9bfef833f40c0ad2b89bf48b10/bin/../Frameworks/FBControlCore.framework/Versions/A/FBControlCore

Check the certificate status:
# This should print "rejected" (this is the expected and correct output)
# You should not see CSSMERR_TP_CERT_REVOKED
$ spctl --assess --type execute /private/var/folders/sl/x1qg9tt511n7gzx43n2vcb_m0000gn/T/xdb/DeviceAgent.iOS.Dependencies/42d07e9bfef833f40c0ad2b89bf48b10/bin/../Frameworks/FBControlCore.framework/Versions/A/FBControlCore

Watch the iOSDeviceManager logs here for more information about the failure:
$ tail -F ~/.calabash/iOSDeviceManager/logs/current.log

@jmoody @jonstoneman - Thank you so much for the quick response!  I was able to get iOS UI Test launch working again.
While troubleshooting this morning, I tried completely removing the Xamarin.UITest 3.0.5 Nuget Package (in Visual Studio for Mac) from my UI Test Project and then adding it again. After that, test launch started working again on iOS.
I'm not sure what was going on, but it definitely seems to suggest that Visual Studio is having some issues with Nuget Packages. Before posting my previous comment regarding Xamarin.UITest.XDB.Exceptions.DeviceAgentException: Unable to verify app installation state, I looked in my packages folder and verified it showed the Xamarin.UITest 3.0.5 Nuget Package
Thank you again for the help!

@jonstoneman 3.0.5 appears to be working as intended and that is with the new VZ for mac and Xcode updates. Thank you for all the help!


New feature

Added new desc PetClinic2

@EROSSHINI Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


ci: Test against OpenEXR 3.3 and deal with its 4.0 bump

OpenEXR 3.3 was just released and its main branch has bumped its advertised version to 4.0 (the latter breaking our "bleeding edge" CI test).
Raise our "latest releases" test to use 3.3.
Our "bleeding edge" test picking up the now-called-4.0 OpenEXR main branch required some minor logic changes to not reject the version as too new to be compatible.

This demonstrably fixes our broken CI test, and changes no code so it can't really break anything. So I'm going to pre-emptively merge without review.


Updated strings based on recent review

Verified that @boxtcarpel has signed the CLA. Thanks for the pull request!


Computing/ProgrammingArticles/Articles: In the Flow/Zone

| How to get in the flow while coding (and why it’s important) - The GitHub Blog |

#3248 closes #3238


sendSms bad typing: Expected 5 arguments, but got 4.

The type for the function sendSms is wrong, in the example you are using 4 arguments, but in its type declaration 5 arguments are needed.
Expected Behavior
Calling the sendSms function and passing arguments like in the example should work.
Current Behavior
There is an error when I try to use the sendSms function. I have the following SS:

Possible Solution
Update the docs to provide a correct example or update the type of the function.
Steps to Reproduce

Try to run this using TypeScript

Context (Environment)
I'm trying to test your API following the basic example for sending an sms. I'm currently using:

Node.js: v16.16.0
TypeScript: v4.7.4
@vonage/server-sdk: v2.11.2

Previous to v3 our typescript definitions were community maintained, but v3 now ships with proper typescript definitions.


orphan Private endpoint

Looking for Orphan azure private endpoint in this workbook
Please share your inputs on this

Hi @rajeshsura189 ,
Happy to update that orphaned Private Endpoints are now part of the workbook. (Thanks to @include-caio contribution)
You are welcome to update the version of the workbook and thanks again for your suggestion.


Add a Gitter chat badge to Readme.md

kissjs/node-mongoskin now has a Chat Room on Gitter
@guileen has just created a chat room. You can visit it here: https://gitter.im/kissjs/node-mongoskin.
This pull-request adds this badge to your Readme.md:

Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Coverage remained the same when pulling aa38cbffa96b9330b5c400ad587e1229dcb10bc5 on gitter-badger:gitter-badge into 098a3f23db0bef4574a1a4109fc2db367f765894 on kissjs:master.


Update velocity:node-soft-mirror

This package is using velocity:node-soft-mirror 0.2.4. https://github.com/mad-eye/meteor-mocha-web/blob/master/package.js#L24
This version of node-soft-mirror spawns an instance of node on the path, instead of using Meteor's node instance. This can be pretty annoying if the system's node version is below Meteor's required version (v0.10.33).
velocity:node-soft-mirror 0.2.7 made a change to spawn Meteor's node instead. https://github.com/meteor-velocity/node-soft-mirror/blob/v0.2.7/nodeMirrorServer.js#L64 We should upgrade to at least this version.
Thanks!

+1 - I don't want to have to manage node versions manually on my system

@mad-eye I think this is a serious issue for new users.

You install meteor
You get velocity
You install the package that is the first one on the velocity home page, mike:mocha
You see the error: [velocity-mirror] Meteor requires Node v0.10.33 or later.
You assume velocity doesn't work and uninstall it forever

Can we please get this fixed as soon as possible? @rdickert this is the issue I was talking about

Thanks guys!

Running into some issues publishing at the moment..might be an hour or two before this is live.

Released :-)


Improve acq_max seeding of L-BFGS-B optimization

The utils.acq_max() function attempts to find the maximum of the function space by first random sampling, then performing a L-BFGS-B optimization starting from some number of random points in the parameter space. This function is used by the optimizer.suggest() routine.
I was using some code like this to do a quick-and-dirty estimate of the current optimal parameters, which should simply find the maximum value of the currently fitted Gaussian process model function:
suggestion = optimizer.suggest(UtilityFunction(kind='ucb', kappa=0.0, xi=0.0))
print(f"Best guess: {suggestion} = {optimizer._gp.predict([[suggestion['x'], suggestion['y']]])[0]}")

This worked most of the time, but I noticed that the suggestion is sometimes worse than the current best result in optimizer.res. In other words, the returned "best" y value can actually be worse than the best known y_max which is passed in as a parameter!
It turns out while suggest() passes acq_max() the best y_max value it has found so far, it doesn't let it know what set of parameters were used to obtain it. This commit passes in these parameters to the acq_max() function where they are added to the list of seeds used for the L-BFGS-B optimization routine. This ensures that the returned best value is at least as good as y_max, but also means the optimization routine should be able to "walk up" the local maximum around the current best y_max.
The changes to acq_max() uses a new keyword parameter with a default of None which retains API backwards compatibility.
In addition, the best candidate from the random sampling phase is also added to the list of seeds for the L-BFGS-B optimization routine, allowing the algorithm to "polish" that result by walking up its local maximum as well.

TOP !

@ptapping

sorry about slow response; I'm trying to work through all the open issues and pull requests....
could you please make any random commit (e.g. add a space or a comment) to this branch, which will trigger the (newly working) CI to run  (actually - can you add the new parameter to the docstring?)
suggest is also called from maximize - in your opinion should this behavior be coded into maximize as well? Probably right?

Hi @bwheelz36
Good stuff. I'm on a bit of a holiday at the moment, but will take a look at this soon when I'm back in front of my real computer.

Hi @bwheelz36 ,
Better late than never! I finally updated this pull request to sync with the changes in master over the last two years. My testing seems to indicate it all still works as expected.
The docstring is added to the acq_max() function.
I don't think any other changes are required inside of maximize() as the suggest() call takes care of everything transparently.

Looks good to me, @till-m unless you have any concerns I can merge?


Update language file

guy plz update language file, i need that

Next time use the correct issue template, please. What's not updated in the language file?

Closing due to inactivity


Fix lint issue reported by fatcontext

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR refactors queueReconcileForWorkloadsOfClusterQueue to avoid using nested contexts, as it has become unwieldy. This issue was identified by the fatcontext linter.
Special notes for your reviewer:
We don't need nested context in our case ctx = ctrl.LoggerInto(ctx, log).
Also, nested contexts may cause performance issues. See more about fat contexts here https://gabnotes.org/fat-contexts/
Does this PR introduce a user-facing change?
Fix performance issue in logging when processing LocalQueues.

/remove-kind cleanup
/kind bug

/retest

/cherry-pick release-0.7

@alexandear could you prepare a cherry-pick?

Cherry-picked in #2492


error 403 for SLD with dash

1. What version of Caddy are you using (caddy -version)?
0.10.14
2. What are you trying to do?
Curl domain with dash via HTTPS thus initiate certificate generation.
3. What is your entire Caddyfile?
https://exam-ple.com {
  tls (email) {
    max_certs 10
    key_type rsa4096
  }
  redir / {scheme}://www.{host}{uri} 301
}

4.
On Ubuntu using the init.d script:
/usr/local/bin/caddy -agree=true -log=/var/log/caddy.log -conf=/etc/caddy/Caddyfile -disable-tls-sni-challenge
5. Please paste any relevant HTTP request(s) here.
curl -I https://exam-ple.com
6. What did you expect to see?
Certificate is generated and delivered and a redirect (301) is given to the requester.
7. What did you see instead (give full error messages and/or log)?
Log entry for request that fails to generate the certificate (domain was replaced):
2018/04/24 09:34:58 [INFO] Obtaining new certificate for www.best-price.com
2018/04/24 09:34:59 [INFO][exam-ple.com] acme: Obtaining bundled SAN certificate
2018/04/24 09:34:59 [INFO][exam-ple.com] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/tpkQwBaci8xACW50K8WQp5PARMt9vnK46mMLdGe-xqM
2018/04/24 09:34:59 [INFO][exam-ple.com] acme: Trying to solve HTTP-01
2018/04/24 09:35:05 http: TLS handshake error from <IP_ADDRESS>:40779: [exam-ple.com] failed to get certificate: acme: Error 403 - urn:ietf:params:acme:error:unauthorized - Invalid response from http://exam-ple.com/.well-known/acme-challenge/o96GjZP6dXNGnzcV8kEs30pjaDEhBzb2aSIVRO2vSz4: "<!DOCTYPE html><html>
    <head>
        <base href="/"/>
        <title>exam-ple.com</title>                        <meta htt"

Log of response from curl:
curl: (35) error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error
Domains that don't follow the schema 'exam-ple.com' (with dash) like 'example.com' are working as expected.
8. How can someone who is starting from scratch reproduce the bug as minimally as possible?

install caddy 0.10.14
configure like the example in (3)
request domain with dash in second level pointing to caddy
check log

Does it happen if you take out the redir directive? If so, does it happen if you disable on-demand TLS? (Why are you using on-demand TLS anyway?)

Without the redir directive the behaviour is the same.
When disabling on-demand TLS the solver takes several minutes without success and caddy never comes up because it fails. The log messages in this case are:

2018/04/24 16:48:16 [INFO][exam-ple.com] acme: Obtaining bundled SAN certificate
2018/04/24 16:48:16 [INFO][exam-ple.com] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/<auth-token>
2018/04/24 16:48:16 [INFO][exam-ple.com] acme: Could not find solver for: dns-01
2018/04/24 16:48:16 [INFO][exam-ple.com] acme: Trying to solve HTTP-01

We are using on-demand TLS because our caddy handles 1500+ known domains and several unknown customer controlled domains.
If we wouldn't use on-demand the startup of caddy would take to long.
According to the test with disabled on-demand TLS caddy even wouldn't start as the certificate generation process doesn't succeed.
Also on-demand TLS is the only reason why we are using caddy.

@root360-AndreasUlm, some related questions:

Is it the only domain having this issue?
Is it the only domain name with a dash?
How is the DNS configured for this domain?
If you disable TLS for that domain name (with "TLS off" in that block) is the domain name reachable?
Are you 100% sure that the "dash" is a "dash" and not an "em dash"?

It seems the domain has an A record that points to <IP_ADDRESS> -- is that where your Caddy instance is?
The fact that it stops at "trying to solve HTTP-01" is making me suspicious about the domain's DNS configuration.

Incidentally, that's an Amazon IP address, and there's a slim chance you were affected by this: https://doublepulsar.com/hijack-of-amazons-internet-domain-service-used-to-reroute-web-traffic-for-two-hours-unnoticed-3a6f0dda6a6f - I'm not exactly sure how, but if everything else was properly configured, it's possible there was some other anomaly...

I visited your domain in my browser, and it's definitely an Apache server that responded, indicating that your DNS or infrastructure isn't even pointing to your Caddy instance.
I will close the issue for now, unless it can be confirmed that it's a bug in Caddy. Let us know what you find out!

So now I finally found the reason for this behaviour and IMHO found a regression concerning caddy's log mechanism.
We had two domains that produced the same error message in caddy.log (quoted above).
The reasons were different.
Domain1 just ran into limits of Let's encrypt and now could generate a valid certificate.
Domain2 has a faulty DNS configuration.
I found the real cause by downgrading caddy to version 0.10.10.
This version now logged the following:
2018/04/25 16:48:30 [INFO] Obtaining new certificate for exam-ple.com
2018/04/25 16:48:31 [INFO][exam-ple.com] acme: Obtaining bundled SAN certificate
2018/04/25 16:48:31 [INFO][exam-ple.com] AuthURL: https://acme-v01.api.letsencrypt.org/acme/authz/<auth-code>
2018/04/25 16:48:31 [INFO][exam-ple.com] acme: Trying to solve HTTP-01
2018/04/25 16:48:34 http: TLS handshake error from <IP_ADDRESS>:33932: [exam-ple.com] failed to get certificate: acme: Error 403 - urn:acme:error:unauthorized - Invalid response from http://exam-ple.com/.well-known/acme-challenge/vGT8OnHmcAntVLH__Ibr2dnN6AuJwp1AxTHVmFtbOog: "<!DOCTYPE html>

<!--// OPEN HTML //-->
<html lang="de-DE">

        <!--// OPEN HEAD //-->
        <head>

                <!-- Manually set render engin"
Error Detail:
        Validation for www.exam-other.com:80
        Resolved to:
                <IPv4-1>
                <IPv6-1>
        Used: <IPv4-1>

        Validation for exam-ple.com:80
        Resolved to:
                <IPv4-2>
                <IPv6-1>
        Used: <IPv6-1>

The important difference of the log message is the part "Error Detail" which pointed me to the fact that 'exam-ple.com' has an IPv4 and an IPv6 address while the IPv6 address is pointing to 'exam-other.com'.
As this part shows the servers of Let's Encrypt used the IPv6 address to validate the request.
That failed as the request wasn't responded by caddy.
This example also shows that caddy version 0.10.12+ (didn't tested 0.10.11) logs different messages than 0.10.10 did resulting in to few information to find the cause of an issue.
@mholt can you fix the IMHO regression of the logging?

I think the change is in the upstream xenolf/lego package -- the acmev2 branch may not report that error, if the ACMEv2 endpoint itself is programmed with different error messages. This is a good question for @xenolf and perhaps should be an issue made upstream: https://github.com/xenolf/acme.

The error message changed from v1 to v2. The information that is shown is all we're getting from LE.


fix: run build with semantic-release

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


reduced gradle build time

@opticod please merge this. I'll pr the another one as soon as this get's merged!
Sorry for delay.

@croozeus  please review so that i can proceed with further prs.
thanks

@DravitLochan , Thanks for the PR. We will be reviewing and merging it shortly. Thank you for the patience.


Redundant subtopics?

There are some topics and subtopics with the same title in the yaml document.  I believe this could lead to confusion later on. Should these subtopics be kept?

This happens for vectors and work.

Hi @KafkaNoNeko I thought I had gone through and made sure that wouldn't happen but I guess I missed a few. Just delete the redundant subtopic and put any relevant LOs under the topic.


New Bluesky user

Title
Leif Davisson
Bluesky profile url
https://ioc.exchange/@leifdavisson
Twitter profile (url or username)
No response
Category
security
Type
None

https://bsky.app/profile/leifdavisson.ioc.exchange.ap.brid.gy


Invoke-PnPTenantTemplate - Continues to give error after running Register-PnPManagementShellAccess

Category

[x] Bug

Describe the bug
Running Invoke-PnPTenantTemplate -Path starterkit-spfx-only.pnp continues to give error even after allowing access to PnP Management shell via Register-PnPManagementShellAccess.
Expected or Desired Behavior
Ran  Register-PnPManagementShellAccess and accepted terms and expect invoke command to work
Observed Behavior
Getting the following error even though Management shell consent given

_Invoke-PnPTenantTemplate : Your template contains artifacts that require an access token for
https://graph.microsoft.com. Please provide consent to the PnP Management Shell application first by
executing: Register-PnPManagementShellAccess
At line:1 char:1

Invoke-PnPTenantTemplate -Path starterkit-spfx-only.pnp

  + CategoryInfo          : WriteError: (:) [Invoke-PnPTenantTemplate], PSInvalidOperationException
  + FullyQualifiedErrorId : EXCEPTION,PnP.PowerShell.Commands.Provisioning.Tenant.InvokeTenantTemplate_

Steps to Reproduce

In PS, ran  Register-PnPManagementShellAccess (ran PS ISE as Administrator)
2.Connect-PnPOnline ->  Logged in as global admin (same as app catalog admin) using -UseWebLogin as MFA is enabled
PnP Management Shell Permissions requested pops up and click Accept (did NOT consent on behalf of org) - note that MFA IS enabled for the tenant
Attempt to run Invoke-PnPTenantTemplate -Path starterkit-spfx-only.pnp
Still getting error

Environment Details (Development & Target environment)

Starter kit version: v2
OS:  Windows 10
Target Environment:  SharePoint Online
Framework: n/a
PnPPowerShell Version : 1.8.0
Browser(s): N/A
Additional details: The more context you can provide, the easier it is (and therefore quicker) to help.
The account used with Pnp powershell does have MFA enabled

I have resolved this - It appears only using the -interactive switch with connect-pnponline works (as opposed to UseWebLogin) when there are calls to the Msft Graph.


What's the function of rt_interface_lcm?

It seems to read data from sbus, and modify the attributes of “main_control_settings” based on the data. But I don't know who send data to sbus , and who publish message on "INTERFACE_gui_main_control_settings" channel with LCM, and how does “main_control_settings” work in the program.

We use this code to control the robot with a wireless R/C radio when testing untethered.  The radio receiver connects to the control computer with SBUS.  It is an alternative to the USB game controller, but also allows us to change the current mode (locomotion, standing, ...).  The LCM channel is no longer used, and nothing will send/receive messages with the "INTERFACE_gui_main_control_settings" (nothing ever calls the init_interface_lcm function).

We use this code to control the robot with a wireless R/C radio when testing untethered. The radio receiver connects to the control computer with SBUS. It is an alternative to the USB game controller, but also allows us to change the current mode (locomotion, standing, ...). The LCM channel is no longer used, and nothing will send/receive messages with the "INTERFACE_gui_main_control_settings" (nothing ever calls the init_interface_lcm function).

Thanks for your detailed explanation.


Saving Webmap json

I'm fooling with adding bookmarks to a web map programmatically and I thought I would use this app to see what endpoints were available. While testing I noticed a few things that I thought you might want to be aware of.
Url formatting
First, I think these lines and this one are creating urls like https://arcgis.com/sharing/rest/content/users/{user}///items/{id}/update with extra /'s when there isn't a folder.
Network traffic
Upon clicking save, the same payload was posted 3 times to the server which seems a bit inefficient.
I don't have a local repo to debug with but I'd be happy to help figure this out with you all since this is a great time saving project!

You're absolutely right; the formatting of urls needs some cleanup especially when it's the root folder. We can use an empty string instead of / for the root folder, but that would still leave two forward slashes in your example. Do you have any thoughts on an alternative approach?
I've seen similar behavior with multiple posts. If you start from scratch (refresh the app) and go directly through that workflow once, does it still post multiple times? I suspect this is caused by old listeners not getting cleaned up when switching context in the "I want to" menu.

I'd have to look at how the urls are created a bit closer but I came into the app and updated a webmap json and it posted 3 times. That was on a fresh load with no event leaks I'm pretty sure.
I'd be happy to talk about it in the slack chat next week.

quit breaking the platform @steveoh and lets see a PR! 👯♂

Ok @jgravois


Upgrade to Ruff v0.4.2

Summary
No new diagnostics (given that the set of enabled rules hasn't changed), but gains access to our new parser (much faster) and reduced false positives all around.

More changes than I would've expected in the Poetry lock, but I ran with the same version (1.6.1) and poetry lock --no-update.


Import sb1-ynoiw5 Unexpected end of JSON input

Describe the bug
It doesn't work anymore
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-ynoiw5
Steps to reproduce

Go to https://bolt.new/~/sb1-ynoiw5
Put any prompt

Expected behavior
To continue develop the app
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 128
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 329311810,
  "usedJSHeapSize": 271845846,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Chat ID = b2385bb5be19

Additional context
Error:
An unknown error occured while running an action.

fixed


Use Blue-Green Deployment to Reduce Downtime and Risk

Reference this great article by @marcingrzejszczak https://spring.io/blog/2016/05/31/zero-downtime-deployment-with-a-database.

Introduce DB schema versioning first.
Create two production environments on PWS: blue, green and prepare your scripts
We have only one DB instance for both environments. Make sure that you document how the process of DB migration (to the next version) should look like, so you are 'backward compatible' (at least one release back). This way you can do a rollback if needed.

Check out how we do this testing in Spring Cloud Pipelines :) With Cloud Foundry it's extremely simple
function performGreenDeploymentOfTestedApplication() {
    local appName="${1}"
    local newName="${appName}-venerable"
    echo "Renaming the app from [${appName}] -> [${newName}]"
    local appPresent="no"
    cf app "${appName}" && appPresent="yes"
    if [[ "${appPresent}" == "yes" ]]; then
        cf rename "${appName}" "${newName}"
    else
        echo "Will not rename the application cause it's not there"
    fi
    deployAndRestartAppWithName "${appName}" "${appName}-${PIPELINE_VERSION}" "PROD"
}

function deleteBlueInstance() {
    local appName=$( retrieveAppName )
    # Log in to CF to start deployment
    logInToPaas
    local oldName="${appName}-venerable"
    echo "Deleting the app [${oldName}]"
    cf app "${oldName}" && appPresent="yes"
    if [[ "${appPresent}" == "yes" ]]; then
        cf delete "${oldName}" -f
    else
        echo "Will not remove the old application cause it's not there"
    fi
}

I will. Thanks @marcingrzejszczak

This is done. Only on Monolith app. Microservices are going to be a challenge  :)


[Likee] can't download some videos

Checklist

[X] I'm reporting a broken site
[X] I've verified that I'm running yt-dlp version 2022.05.18 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Russia
Description
When I copy link on video from Likee app (for iOS) I got link like this:
https://l.likee.video/v/qe6tdo
And yt-dlp can't download video from this link.
Verbose log
D:\PROGRAMS\TikTok Download>!dl https://l.likee.video/v/qe6tdo -vU
[debug] Command-line config: ['https://l.likee.video/v/qe6tdo', '-vU']
[debug] Encodings: locale cp1251, fs utf-8, pref cp1251, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.05.18 [b14d523] (win_exe)
[debug] Python version 3.8.10 (CPython 64bit) - Windows-10-10.0.19044-SP0
[debug] Checking exe version: ffprobe -bsfs
[debug] Checking exe version: ffmpeg -bsfs
[debug] exe versions: ffmpeg n4.4.2-1-g8e98dfc57f-20220507 (setts), ffprobe n4.4.2-1-g8e98dfc57f-20220507
[debug] Optional libraries: Cryptodome-3.14.1, brotli-1.0.9, certifi-2021.10.08, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
Latest version: 2022.05.18, Current version: 2022.05.18
yt-dlp is up to date (2022.05.18)
[debug] [generic] Extracting URL: https://l.likee.video/v/qe6tdo
[generic] qe6tdo: Requesting header
[redirect] Following redirect to https://likee.video/trending?postId=7087181733124333126&c=cp
[debug] [likee:user] Extracting URL: https://likee.video/trending?postId=7087181733124333126&c=cp
[likee:user] trending?postId=7087181733124333126&c=cp: Downloading webpage
ERROR: [likee:user] trending?postId=7087181733124333126&c=cp: Unable to extract user info; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "yt_dlp\extractor\common.py", line 642, in extract
  File "yt_dlp\extractor\likee.py", line 190, in _real_extract
  File "yt_dlp\extractor\common.py", line 1226, in _search_regex

That link just seems to take me to the home page

https://l.likee.video/v/RdsdCl
try this.
you can get links like this by copy link on video from Likee app (for iOS)

Its a site bug, link only playable on ios app

It playable in browser too

for some likee videos not for all videos, such as this one : https://l.likee.video/v/v9UpVo
try on iphone and browser, it only works on likee app

Hi! The same problem for me, every link from Android app can be opened via browser, but yt-dlp crashes with "Unable to extract user info".
Examples:
https://l.likee.video/v/mKT3N0
https://l.likee.video/v/L0HgEZ
https://l.likee.video/v/BSLxYi
https://l.likee.video/v/W9YdU9
https://l.likee.video/v/ISYo5h


GA : Build ZIP File and push it to release

This should go to 2.0.x, 2.1.x and develop.

Questions
Answers

Description?
GA : Build ZIP File and push it to release

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
N/A

Sponsor company
@PrestaShopCorp

How to test?
CI is :green_circle: and the ZIP for Classic is available : https://github.com/PrestaShop/classic-theme/actions/runs/4055277378 :tada:

Ping @PrestaShop/committers

Can I merge it? There is nothing more to test than checking the zip in CI. 🤷♂

Ping @PrestaShop/qa-functional

Hello @Hlavtox
It's Ok for us. GO
Thanks @Progi1984 for your PR

Thank you @Progi1984 and @HanaRebaiQA !


OpenSSL 1.1.1a: openssl_pkey_get_details expects parameter 1 to be resource, boolean given

Setup
Ubuntu 18.04.1
OpenSSL 1.1.1a, compiled by source (./config && make && checkinstall)
Nextcloud 14.1
PHP 7.2.10
nginx 1.15.7 + OpenSSL 1.1.1a
Summary
I have a Nextcloud instance running on my VPS. With OpenSSL 1.1.1 compiled by source everything ran fine. Yesterday I upgraded OpenSSL 1.1.1 to 1.1.1a and encountered an internal server error (500), when I tried to login into Nextcloud.
The reason I post this bug at the OpenSSL repository and not at the Nextcloud repository is because of the error message I found in the Nextcloud log file:
{"reqId":"a0FfZr6Dfd2Q7wFQ5t4Q","level":3,"time":"2018-12-05T23:22:41+00:00","remoteAddr":"XXX.XXX.XXX.XXX","user":"USER1","app":"index","method":"POST","url":"\/nextcloud\/login?redirect_url=\/nextcloud\/apps\/files\/","message":{"Exception":"TypeError","Message":"openssl_pkey_get_details() expects parameter 1 to be resource, boolean given","Code":0,"Trace":[{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/Authentication\/Token\/PublicKeyTokenProvider.php","line":301,"function":"openssl_pkey_get_details","args":[false]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/Authentication\/Token\/PublicKeyTokenProvider.php","line":70,"function":"newToken","class":"OC\\Authentication\\Token\\PublicKeyTokenProvider","type":"->","args":["*** sensitive parameter replaced ***","*** sensitive parameter replaced ***","*** sensitive parameter replaced ***","*** sensitive parameter replaced ***","*** sensitive parameter replaced ***","*** sensitive parameter replaced ***","*** sensitive parameter replaced ***"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/Authentication\/Token\/Manager.php","line":69,"function":"generateToken","class":"OC\\Authentication\\Token\\PublicKeyTokenProvider","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/User\/Session.php","line":641,"function":"generateToken","class":"OC\\Authentication\\Token\\Manager","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/core\/Controller\/LoginController.php","line":322,"function":"createSessionToken","class":"OC\\User\\Session","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/AppFramework\/Http\/Dispatcher.php","line":166,"function":"tryLogin","class":"OC\\Core\\Controller\\LoginController","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/AppFramework\/Http\/Dispatcher.php","line":99,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->","args":[{"__class__":"OC\\Core\\Controller\\LoginController"},"tryLogin"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/AppFramework\/App.php","line":118,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->","args":[{"__class__":"OC\\Core\\Controller\\LoginController"},"tryLogin"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/AppFramework\/Routing\/RouteActionHandler.php","line":47,"function":"main","class":"OC\\AppFramework\\App","type":"::","args":["OC\\Core\\Controller\\LoginController","tryLogin",{"__class__":"OC\\AppFramework\\DependencyInjection\\DIContainer"},{"_route":"core.login.tryLogin"}]},{"function":"__invoke","class":"OC\\AppFramework\\Routing\\RouteActionHandler","type":"->","args":[{"_route":"core.login.tryLogin"}]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/Route\/Router.php","line":297,"function":"call_user_func","args":[{"__class__":"OC\\AppFramework\\Routing\\RouteActionHandler"},{"_route":"core.login.tryLogin"}]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/base.php","line":987,"function":"match","class":"OC\\Route\\Router","type":"->","args":["\/login"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/index.php","line":42,"function":"handleRequest","class":"OC","type":"::","args":[]}],"File":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/Authentication\/Token\/PublicKeyTokenProvider.php","Line":301,"CustomMessage":"--"},"userAgent":"XXX}
{"reqId":"qwr19jSFwzwTGTaBeVGY","level":3,"time":"2018-12-05T23:25:33+00:00","remoteAddr":"XXX.XXX.XXX.XXX","user":"USER1","app":"PHP","method":"POST","url":"\/nextcloud\/login?redirect_url=\/nextcloud\/apps\/files\/","message":"openssl_pkey_export(): cannot get key from parameter 1 at \/var\/www\/domain.tld\/nextcloud\/lib\/private\/Authentication\/Token\/PublicKeyTokenProvider.php#298","userAgent":"XXX}
{"reqId":"qwr19jSFwzwTGTaBeVGY","level":3,"time":"2018-12-05T23:25:33+00:00","remoteAddr":"XXX.XXX.XXX.XXX","user":"USER1","app":"index","method":"POST","url":"\/nextcloud\/login?redirect_url=\/nextcloud\/apps\/files\/","message":{"Exception":"TypeError","Message":"openssl_pkey_get_details() expects parameter 1 to be resource, boolean given","Code":0,"Trace":[{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/Authentication\/Token\/PublicKeyTokenProvider.php","line":301,"function":"openssl_pkey_get_details","args":[false]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/Authentication\/Token\/PublicKeyTokenProvider.php","line":70,"function":"newToken","class":"OC\\Authentication\\Token\\PublicKeyTokenProvider","type":"->","args":["*** sensitive parameter replaced ***","*** sensitive parameter replaced ***","*** sensitive parameter replaced ***","*** sensitive parameter replaced ***","*** sensitive parameter replaced ***","*** sensitive parameter replaced ***","*** sensitive parameter replaced ***"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/Authentication\/Token\/Manager.php","line":69,"function":"generateToken","class":"OC\\Authentication\\Token\\PublicKeyTokenProvider","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/User\/Session.php","line":641,"function":"generateToken","class":"OC\\Authentication\\Token\\Manager","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/core\/Controller\/LoginController.php","line":322,"function":"createSessionToken","class":"OC\\User\\Session","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/AppFramework\/Http\/Dispatcher.php","line":166,"function":"tryLogin","class":"OC\\Core\\Controller\\LoginController","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/AppFramework\/Http\/Dispatcher.php","line":99,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->","args":[{"__class__":"OC\\Core\\Controller\\LoginController"},"tryLogin"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/AppFramework\/App.php","line":118,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->","args":[{"__class__":"OC\\Core\\Controller\\LoginController"},"tryLogin"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/AppFramework\/Routing\/RouteActionHandler.php","line":47,"function":"main","class":"OC\\AppFramework\\App","type":"::","args":["OC\\Core\\Controller\\LoginController","tryLogin",{"__class__":"OC\\AppFramework\\DependencyInjection\\DIContainer"},{"_route":"core.login.tryLogin"}]},{"function":"__invoke","class":"OC\\AppFramework\\Routing\\RouteActionHandler","type":"->","args":[{"_route":"core.login.tryLogin"}]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/Route\/Router.php","line":297,"function":"call_user_func","args":[{"__class__":"OC\\AppFramework\\Routing\\RouteActionHandler"},{"_route":"core.login.tryLogin"}]},{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/base.php","line":987,"function":"match","class":"OC\\Route\\Router","type":"->","args":["\/login"]},{"file":"\/var\/www\/domain.tld\/nextcloud\/index.php","line":42,"function":"handleRequest","class":"OC","type":"::","args":[]}],"File":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/Authentication\/Token\/PublicKeyTokenProvider.php","Line":301,"CustomMessage":"--"},"userAgent":"XXX}

The interesting part here is the following error message:
"Exception":"TypeError","Message":"openssl_pkey_get_details() expects parameter 1 to be resource, boolean given","Code":0,"Trace":[{"file":"\/var\/www\/domain.tld\/nextcloud\/lib\/private\/Authentication\/Token\/PublicKeyTokenProvider.php","line":301,"function":"openssl_pkey_get_details","args":[false]
Those are the file Nextcloud files referenced in the log above:

https://github.com/nextcloud/server/blob/stable14/lib/private/Authentication/Token/PublicKeyTokenProvider.php#L301
https://github.com/nextcloud/server/blob/stable14/lib/private/Authentication/Token/Manager.php#L69

Nothing has changed at Nextcloud and it seems that nothing relevant has changed between 1.1.1 and 1.1.1a according to the changelog. That's why I believe this may be a bug at OpenSSL 1.1.1a.
If I revert back to OpenSSL 1.1.1 the bug vanishes again. Please let me know if you need any more information.

"Exception":"TypeError","Message":"openssl_pkey_get_details() expects parameter 1 to be resource, boolean given","Code":0,"Trace":[{"file":"/var/www/domain.tld/nextcloud/lib/private/Authentication/Token/PublicKeyTokenProvider.php","line":301,"function":"openssl_pkey_get_details","args":[false]

Actually that error is not coming out of OpenSSL. There is no function with that name in OpenSSL. Its a PHP thing:
https://secure.php.net/manual/en/function.openssl-pkey-get-details.php

Actually that error is not coming out of OpenSSL. There is no function with that name in OpenSSL. Its a PHP thing

Indeed, here is its implementation: https://github.com/php/php-src/blob/PHP-7.2.10/ext/openssl/openssl.c#L4715
How shall we proceed? Do you agree that the problem likely lies on the side of OpenSSL? Shall we leave the issue opened? Shall I report the bug to the PHP team as well?
If you would like me to debug the issue further, I would appreciate it if you could guide me.
Regards

The error message suggests that the caller of the PHP function (presumably Nextcloud) is not behaving correctly by passing an invalid value as a parameter. So that suggests a bug in the PHP function caller (presumably Nextcloud?).
Most likely what has happened is that the upgrade to 1.1.1a has suddenly caused some OpenSSL function call to behave differently in some way which has had a knock on impact in Nextcloud - thus triggering the Nextcloud bug and causing it to make the openssl_pkey_new_error function call with an invalid value.
What the reason for the change in OpenSSL behaviour is, is unclear. It could be an intended change in behaviour (e.g. due to a bug fix), or it could be accidental (i.e. a newly introduced bug). Either way the next step would be to isolate the bug in Nextcloud and get that fixed. That should also identify what the underlying change in OpenSSL behaviour was that triggered it.

If I revert back to OpenSSL 1.1.1 the bug vanishes again. Please let me know if you need any more information.

If the bug can be reproduced reliably, you could try to do a git-bisect between the tags  OpenSSL_1_1_1 and  OpenSSL_1_1_1a to find the offending commit.

If the bug can be reproduced reliably, you could try to do a git-bisect between the tags  OpenSSL_1_1_1 and  OpenSSL_1_1_1a to find the offending commit.

Thanks, I will try the binary bad commit search approach later, when I find some more time! :)

With the help of the Nextcloud contributor @danielkesselberg I was able to solve the issue. Somehow my OpenSSL 1.1.1a looks for
/usr/local/ssl/openssl.cnf  instead of /etc/ssl/openssl.cnf  as OpenSSL 1.1.1 did.
To sum up, the following has resolved the issue:
sudo ln -s /etc/ssl/openssl.cnf /usr/local/ssl/openssl.cnf

Can I somehow display the config details to proof it?

You can dump the configuration using the perl configdata.pm --dump command in the source root directory.

Thank you @mspncp . I could proof that both used the same compilation flags, however, there is a minor difference between the Debian packages:
 dpkg -c openssl_1.1.1-1_amd64.deb | grep /usr/local/ssl/
drwxr-xr-x root/root         0 2018-09-21 17:11 ./usr/local/ssl/
-rw-r--r-- root/root       414 2018-09-21 16:46 ./usr/local/ssl/ct_log_list.cnf
-rw-r--r-- root/root       414 2018-09-21 16:46 ./usr/local/ssl/ct_log_list.cnf.dist
drwxr-xr-x root/root         0 2018-09-21 17:11 ./usr/local/ssl/misc/
-rwxr-xr-x root/root      7598 2018-09-21 16:46 ./usr/local/ssl/misc/CA.pl
-rwxr-xr-x root/root      6578 2018-09-21 16:46 ./usr/local/ssl/misc/tsget.pl
-rw-r--r-- root/root     10998 2018-09-21 16:46 ./usr/local/ssl/openssl.cnf
-rw-r--r-- root/root     10998 2018-09-21 16:46 ./usr/local/ssl/openssl.cnf.dist
lrwxrwxrwx root/root         0 2018-09-21 16:46 ./usr/local/ssl/misc/tsget -> tsget.pl

$ dpkg -c openssl_1.1.1a-1_amd64.deb | grep /usr/local/ssl/
drwxr-xr-x root/root         0 2018-12-05 12:42 ./usr/local/ssl/
-rw-r--r-- root/root       414 2018-12-05 12:24 ./usr/local/ssl/ct_log_list.cnf.dist
drwxr-xr-x root/root         0 2018-12-05 12:42 ./usr/local/ssl/misc/
-rwxr-xr-x root/root      7598 2018-12-05 12:24 ./usr/local/ssl/misc/CA.pl
-rwxr-xr-x root/root      6579 2018-12-05 12:24 ./usr/local/ssl/misc/tsget.pl
-rw-r--r-- root/root     10911 2018-12-05 12:24 ./usr/local/ssl/openssl.cnf.dist
lrwxrwxrwx root/root         0 2018-12-05 12:24 ./usr/local/ssl/misc/tsget -> tsget.pl

./usr/local/ssl/ct_log_list.cnf is indeed missing in 1.1.1a.
Maby you have an idea why checkinstalled may not have it included?

./usr/local/ssl/ct_log_list.cnf as well as ./usr/local/ssl/ct_log_list.cnf are indeed missing in 1.1.1a.

Probably because it was configured with no-ct?

./usr/local/ssl/ct_log_list.cnf as well as ./usr/local/ssl/ct_log_list.cnf are indeed missing in 1.1.1a.

Probably because it was configured with no-ct?

Sorry, of the ct_log_list.cnf should have been a openssl.cnf. And no no-ct was not used at all.
Whatever, if I am the only one with this issue, then let's leave it by that! :)


zetacore : Register interfaces

Check if we need to register interfaces twice
We manually register them here
https://github.com/zeta-chain/zeta-node/blob/c8c833f66e3862cfa9e12c357436322e4f12c807/app/encoding.go#L32-L49
But they also registered the get with cosmos SDK in the makeconfig call.

We manually register them here
https://github.com/zeta-chain/zeta-node/blob/c8c833f66e3862cfa9e12c357436322e4f12c807/app/encoding.go#L32-L49

This link doesn't return to an existing code
Why is it needed to register the interface twice?

I dont think we do , noticed that it was being done twice while working on a pr , will investigate and remove in a future task


Use the new analysis options

With Flutter 2.5, Google seems to have gotten their preferred analysis options into better shape.  They might add a little value, and at first glance there's nothing too troubling there, so moving to the new analysis options is probably worth doing.

Published in 1.0.7


feat(ad_service_state_monitor)!: remove ad_service_state_monitor

Description
Remove ad_service_state_monitor and add the autoware state node for compatibility. The functionality of ad_service_state_monitor has been reorganized into the autoware state node and the following packages.

state machine: /autoware/state is now converted in autoware state node from initialization state, routing state and operation mode provided by AD API

finalizing state: /autoware/shutdown service will continue to be supported in autoware state node.
arrived goal: The goal arrival check is moved to mission_planner package.
topic check: The topic rate check is moved to component_state_monitor package.

clear route: /autoware/reset_routeis removed. Use /api/routing/clear_route instead.
disengage_on_goal: The routing node in default_ad_api changes operation mode to stop when the vehicle goals.
disengage_on_route:  The routing node in default_ad_api changes operation mode to stop when /api/routing/clear_route .

Related links
https://github.com/tier4/autoware_launch/pull/568
Tests performed
Using simple_planning_simulator.

Check if the vehicle can drive and if the state transitions as before.
Check if the operation mode will be stop when the vehicle goals.
Check if the operation mode will be stop when the route is cleared (while the vehicle is driving).
Check if the autoware state will be finalizing when /autoware/shutdown service is called.

Notes for reviewers
None
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@kenji-miyake
Instead of discarding it, I now add at least one status for alive monitoring. https://github.com/autowarefoundation/autoware.universe/pull/2311/commits/46d9d4a495b6bc1ee86dcd2e71b5df346e8f1f6b


Creating custom ROS2 interfaces

I want to create a custom service in my environment.
@pablogs9 has previously linked to this tutorial
which is depending on setting up a Micro-ROS workspace
Do I have to install Vulcanexus, and create a micro ROS workspace? In an old issue, Pablo replied this:  https://github.com/micro-ROS/micro_ros_raspberrypi_pico_sdk/issues/83#issuecomment-847568777_
Does this recipe still hold? The microros_static_library/library_generation/extra_packages folder is already in my environment, and the correct tag seem to be in Docker hub

Yes it is possible.
Closing as solved


Fix for Wrong struct for IoTCustomAuthorizerRequest #400

Issue #400:
Description of changes:
Fix for Wrong struct for IoTCustomAuthorizerRequest #400

closing as a duplicate of #401 per https://github.com/aws/aws-lambda-go/issues/400#issuecomment-941972600


fix : support list/dict subscript format in KCL string

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

fix #149
2. What is the scope of this PR (e.g. component or file name):

kclvm/runtime/src/value/val_fmt.rs
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.712%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1369

Relevant Lines:
1526

💛  - Coveralls


mapDriver.sys issue

Severity	Code	Description	Project	File	Line	Suppression State
Error	MSB3030	Could not copy the file "E:\kernel driver\x64\Release\mapDriver.sys" because it was not found.	mapDriver	C:\Program Files (x86)\Windows Kits\10\build\WindowsDriver.common.targets	1683
Cant seem to find the problem.

Thanks @NorvalMarley
Got me all the way to
"Cannot open include file
No such file or directory ..\10.0.15063.0\shared\warning.h"
Anyone know the exact WDK to use for this with VS2015? I might need to uninstall/reinstall?

I'm ready for my userMod issues @NorvalMarley :)


aksv2 - UI should show AZs only for supported regions

What kind of request is this (question/bug/enhancement/feature request): Bug
Steps to reproduce (least amount of steps as possible):
UI should show AZs for only supported regions. Eg:
UI shows AZs 1, 2 and 3 for westus, which is not correct.
Result:
Error failed to create cluster: containerservice.ManagedClustersClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: Code="AvailabilityZoneNotSupported" Message="Availability zone is not supported in this region." Target="agentPoolProfile.availabilityZone"
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
Installation option (single install/HA):

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

(paste the output here)

Docker version (use docker version):

(paste the output here)

@prabalsharma I'm not sure how we want to support this functionality. Currently the UI keeps a list of locations that support availability zones but I could not find a list of what AZ are available in each location. It looks like there may be a small bug with this logic because if a location is selected without zone support the radio buttons should be disabled and un-selectable.
That being said I still think we're still going to run into issues because some locations don't support ALL zones from what I understand. We currently do not have an API to fetch the availability zones nor am I sure that one actually exists. I dug around a bit looking for an API that would do this and it seems there may be some way to do this from the CLI but I could not find any other info actual rest APIs.
@mjura is there any way for you to fetch the availability zones for a location? Even better would be adding the availability zone to the locations call but I'm not sure that's possible?

It looks like there may be a small bug with this logic because if a location is selected without zone support the radio buttons should be disabled and un-selectable.

My bug is for this ^ : AZ buttons not getting disabled for Regions which do not support AZs

That being said I still think we're still going to run into issues because some locations don't support ALL zones from what I understand. We currently do not have an API to fetch the availability zones nor am I sure that one actually exists. I dug around a bit looking for an API that would do this and it seems there may be some way to do this from the CLI but I could not find any other info actual rest APIs.

I was not able to find a region which supports partial AZs (either a Region supports all 3 AZs or none). Do you have an example of a Region which supports a subset of AZs 1, 2 and 3?

@mjura is there any way for you to fetch the availability zones for a location? Even better would be adding the availability zone to the locations call but I'm not sure that's possible?

I was not able to find a region which supports partial AZs (either a Region supports all 3 AZs or none). Do you have an example of a Region which supports a subset of AZs 1, 2 and 3?

@prabalsharma I think I may have misread or seen something early on in dev because I couldn't find one either. If this ticket is solely for the radios not being disabled then I will move this. The change for that went in with rancher/ui#4648

tested on master-b2f8824


go tool vet complain about package name for *_test.

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?
1.6

What operating system and processor architecture are you using (go env)?
amd64 linux

What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.

Created a test in the same dir as the package api except the test package was api_test. Should go vet complain here?

What did you expect to see?
No error?

What did you see instead?
package api_test; expected api

Yes. Your package name for tests should be the same as for your code.

Ah ok thanks, was the special handling for _test only meant for the stdlib?
Also, go vet didn't report it only go tool vet -v did, is that intentional? I was under the impression go vet runs all checks by default.

As far as I know, *_test test packages aren't limited to the standard library. Their main purpose is to break circular dependencies, which is equally valid for 3rd party code as it is for the stdlib. Furthermore, a fair amount of people use them to write blackbox tests.
However, I'm not sure there's an issue here. -v prints verbose information, and the "package api_test, expected apiis likely to be a semi-internal debug message related to the type checker. If it was an offence that the tool wanted to report to the user, it would do so without the-v` flag, too.

The error is returned by config.Check in the check function in types.go. And this only occurs when using go tool vet on a set of files, as all files are expected to be in the same package. If you use go vet, which deals with Go packaging, it will work correctly and test the two packages separately.

Ah that last part makes sense, thanks.

I am also trying to diagnose where /usr/local/go vet ./somepackage is working on my host but not in a docker container. This is after a fresh untar of the go1.6.linux-amd64.tar.gz on both. Only difference in go env. One is reporting a struct field not using key and the other is not. Any ideas?


DynamicFormBootstrapComponent - inline template:1:5 caused by: Expression has changed after it was checked. Previous value: 'true'. Current value: 'false'.

Team,
Did any one of you observe following error?
I'm getting this error when I reload the page. Although it does not have functional impact, however it may be sign of some hidden problem.
Could you please take a look. Thanks
Error: Error in ./DynamicFormBootstrapComponent class DynamicFormBootstrapComponent - inline template:1:5 caused by: Expression has changed after it was checked. Previous value: 'true'. Current value: 'false'.
    at ViewWrappedError.ZoneAwareError (http://localhost:4200/vendor.bundle.js:101576:33)
    at ViewWrappedError.BaseError [as constructor] (http://localhost:4200/vendor.bundle.js:30734:16)
    at ViewWrappedError.WrappedError [as constructor] (http://localhost:4200/vendor.bundle.js:30799:16)
    at new ViewWrappedError (http://localhost:4200/vendor.bundle.js:63192:16)
    at CompiledTemplate.proxyViewClass.DebugAppView._rethrowWithContext (http://localhost:4200/vendor.bundle.js:85265:23)
    at CompiledTemplate.proxyViewClass.DebugAppView.detectChanges (http://localhost:4200/vendor.bundle.js:85238:18)
    at CompiledTemplate.proxyViewClass.AppView.internalDetectChanges (http://localhost:4200/vendor.bundle.js:85025:18)
    at View_DynamicFormBootstrapComponent12.detectChangesInternal (/DynamicFormsBootstrapUIModule/DynamicFormBootstrapComponent/component.ngfactory.js:705:19)
    at View_DynamicFormBootstrapComponent12.AppView.detectChanges (http://localhost:4200/vendor.bundle.js:85040:14)
    at View_DynamicFormBootstrapComponent12.DebugAppView.detectChanges (http://localhost:4200/vendor.bundle.js:85235:44)
    at ViewContainer.detectChangesInNestedViews (http://localhost:4200/vendor.bundle.js:85372:37)
    at View_DynamicFormBootstrapComponent10.detectChangesInternal (/DynamicFormsBootstrapUIModule/DynamicFormBootstrapComponent/component.ngfactory.js:841:14)
    at View_DynamicFormBootstrapComponent10.AppView.detectChanges (http://localhost:4200/vendor.bundle.js:85040:14)
    at View_DynamicFormBootstrapComponent10.DebugAppView.detectChanges (http://localhost:4200/vendor.bundle.js:85235:44)
    at ViewContainer.detectChangesInNestedViews (http://localhost:4200/vendor.bundle.js:85372:37)

@rahul-winner: This has already been discussed in #250 and #266.
Actually should not happen when you stick to the examples.
For further investigation however I'd need a plunkr.

thanks @udos86
Could you please elaborate what do I need to fix this issue. I went through #250 & #266, however I could not perceive the concrete working solution.
Is using "this.changeDetectorRef.detectChanges();" really the correct solution? I could not see that example using same thing.
I'm still confused and facing this error. Pls help.

@rahul-winner
I'd like to help but It's really hard to tell from afar what causes this problem in your application. The thing is that I'm aware that this has been happening under certain circumstances because of the way how template references are set internally. However this should ultimately have been fixed a couple of versions ago.
Are you using any other libraries? How does your code differ from example? A live sample would really help.

Thanks @udos86
I'm able to make it work with detectChanges() after data is returned from server.
Regards, Rahul


What are instances_minival and instances_valminusminival?

Hi! I am using coco2017 dataset and have changed paths in paths_catalog from 2014 to corresponding 2017 ones. When I run the project I got this error:
No such file or directory: 'datasets/coco/annotations/instances_valminusminival2017.json'
It seems there is no such json file in coco datasets. May I ask what are these minival json files? How can I reproduce one?

When you change the dataset from coco2014 to coco2017, you need to change the corresponding annotations too.
DATASETS = {
"coco_2017_train": (
"coco/train2017",
"coco/annotations/instances_train2017.json",
),
"coco_2017_val": (
"coco/val2017",
"coco/annotations/instances_val2017.json",
),
}

Thanks!

When you change the dataset from coco2014 to coco2017, you need to change the corresponding annotations too.
DATASETS = {
"coco_2017_train": (
"coco/train2017",
"coco/annotations/instances_train2017.json",
),
"coco_2017_val": (
"coco/val2017",
"coco/annotations/instances_val2017.json",
),
}

Hi. Where can I find this annotation?

When you change the dataset from coco2014 to coco2017, you need to change the corresponding annotations too.
DATASETS = {
"coco_2017_train": (
"coco/train2017",
"coco/annotations/instances_train2017.json",
),
"coco_2017_val": (
"coco/val2017",
"coco/annotations/instances_val2017.json",
),
}

Hi. Where can I find this annotation?
In case this may help, I have solved this problem by referring to this link.

You can find here https://github.com/facebookresearch/Detectron/blob/master/detectron/datasets/data/README.md#coco-minival-annotations


iCub: Update neck_pitch and neck_roll position PIDs in head version > = 2.0

The updated PID values are obtained by an automatic and robust tuning process described and simulated here.
These values were then tested on iCubGenova02 and iCubGenova09.

iCubGenova07, iCubGenova09 and iCubGenova10 are now up-to-date as well.


Cant satisfy complier on calls x implements y, where y is class.

Hi,
Typescript 1.6.2
When trying to implement a class with private variables complier wants the derived class to implement the parent's private variables.
export class Father {
    private hidden: string;
    public visible: string;
}

export  class Child implements Father{
    public visible: string;
}

(7,15): error TS2420: Class 'child' incorrectly implements interface 'father'.
Property 'hidden' is missing in type 'child'.
Trying to do the wrong thing and do implement the private variable results in the compiler not happy since we implement a private variable of the parent (In a typed language this is wrong as well, but in JS it might be a good catch...)
export class Father {
    private hidden: string;
    public visible: string;
}

export  class Child implements Father{
    private hidden: string;
    public visible: string;

}

(7,15): error TS2420: Class 'child' incorrectly implements interface 'father'.
Types have separate declarations of a private property 'hidden'.

Can you try extends instead of implements ? implements is for interfaces.

I can try, but as you can see I try to do some "mixin" stuff
Typescript has an official documented approach for it, https://github.com/Microsoft/TypeScript-Handbook/blob/master/pages/Mixins.md
I'm sure I've seen some other places in the docs that "implement" concrete classes...
So it should be possible

the issue here is the private property declaration. When implementing  a class with private, the implementing class gets the property declaration but not its implementation. private members can not be re-implemented, the only allowed implementation for them is their original declaration. so now you have a class is not implementable.
for mix-in patterns, do not use private members, or split your non-private declarations in an interface and use that.

see #1101 for more details.


Added hamburger Menu to all the required pages

PR Description 📜
I added and/or modified the nav-bar to be consistent in all the following pages:

About Page
Contributors Page
How to Play Page
FAQs Page

The theme of these pages is totally different, and there is no nav-bar at all in these pages:

Privacy Policy Page
Licensing Page
Terms of Service Page

The Home screen layout is not responsive enough for mobile devices,, and I have avoided making any change in it fuee to the following two reasons:

to avoid possible conflicts.
the new navbar won't be useable  enough in the current conditions of the home-page

Fixes #624

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for review.

Screenshots

Thank you soo much for contributing to our repository 💗

Note: The weird behavior of the images in the Contributions page was not caused due to my changes. The problem was already there as the time of the last version of the repo.

@ayush-t02 please kindly check

resolve conflicts

why is the hamburger not a part of the navbar?

@ayush-t02  The hamburger has to be shifted when the side menus is opened, and it will disturb the position of the logo of the website when shifted.

@ayush-t02 should I change the hamburger position?

the hamburger is supposed to be a part of the navbar, in the same line as the logo, look into it if you can otherwise just resolve the conflicts

@ayush-t02 as I mentioned putting it inside the Nav bar will shift the Nav-bar logo when the side menu opens.
One thing that will look better is inserting the logo inside the side-menu. But it will leave the main nav bar empty in mobile menu.


[darwin] CI macos-14 : updated toolchains for macOS Apple Silicon

Summary
added shell script darwin_arm64.sh  for macOS Apple Silicon
updated toolchains for macOS on Apple Silicon

arm64
aarch64
xpack-riscv
xtensa-esp32

Impact
Impact on user: No changes to user-facing functionality
Impact on build: Build process remains the same
Testing
tested only on github workflow with only [macos]
macos-14
github macos-14

[Experimental Bot, please feedback here]
This PR appears to mostly meet the NuttX requirements but is missing some key information.  Here's a breakdown:
Strengths:

Clear Summary:  The summary clearly states the "what" and "why" of the changes.  Adding support for macOS Apple Silicon is a good justification.
Impact Assessment (Mostly): Most impact sections are addressed, although some lack detail.
Testing Confirmation:  Confirmation of testing is present, and a link to the GitHub workflow is provided.

Weaknesses:

Missing Details in Impact:  While most impact sections are marked "NO," it's important to consider potential impacts more thoroughly, even if they are negative. For example:

Impact on hardware: Even if no existing architectures/boards/drivers change, explicitly stating which ones were tested with the new toolchains would be helpful.  Did you test any physical boards?
Impact on documentation:  Does the documentation need updating to reflect the new supported toolchains for macOS Apple Silicon? Even if not, explicitly stating this would be beneficial.

Limited Testing Information:  While the GitHub Actions link is good, it doesn't replace showing actual logs.  Include snippets of relevant logs demonstrating successful builds with each of the mentioned toolchains (arm64, aarch64, xpack-riscv, xtensa-esp32).  "Tested only on GitHub workflow" isn't sufficient. Provide more specifics about the configurations tested within the workflow.
Missing "How it Works" in Summary:  The summary doesn't explain how the toolchain updates were implemented. Briefly describe the changes made to the build system or configuration files.
Lack of "Before" Logs: Even if the behavior hasn't changed functionally, providing "before" logs would create a baseline for comparison and prove that the existing functionality remains unaffected.  This is especially important when changing build tools.

Recommendation:
To fully meet the NuttX requirements, the PR should be revised to include:

More detailed impact assessment:  Even if the answer is "NO," briefly explain why.  If "YES," provide specifics.  For hardware impact, list the tested architectures/boards.  For documentation, explicitly state whether changes are needed.
More comprehensive testing information: Include relevant snippets of logs demonstrating successful builds with each toolchain (before and after).  Specify the configurations (board, architecture) used in the tests, both locally and in the GitHub workflow.
Explanation of implementation in the summary:  Briefly describe the changes made to support the new toolchains.
"Before" logs: Include logs demonstrating the previous behavior before the change, even if no functional changes are expected.

By addressing these points, the PR will be much stronger and more likely to be accepted.


1.1.0(ADAS) Zero byte files are not processed by SSM

Hi,
I'm not sure if this is by design or not, but lets say I have two files:

/tmp/notes.txt - this file is 10Kb
/tmp/3.xml  - this is an empty file

If I do checkstorage/move/ or any action from gui, I do not see any response from the SSM, result is empty.
I believe for some reason SSM does not process 0 byte files.
Attaching snapshot to prove the same.

If you look at the results, SSM says "true" and "successful" although I don't believe the 0 byte files were processed.
Please feel free to add comments/questions/
Thanks
Varsha

@aurorahunter Checkstorage/move action do process the 0 byte file. For checkstorage action, as there are no blocks for the file, so there is no result output.  For move action, it has no result output at all, no matter the file length.

Hi,
Thanks for getting back on this, but it is very misleading as there isn't any result/output shown.
Can we maybe get some sort of message or something so we know that operation indeed happen?

Ok, We'll fix it soon.


Minimap misaligned

Still works as a button, though. Chrome, Windows 10
First noticed with the foyer/study, there was no map

In the kitchen it's off but technically okay

It's perfect in the lounge. An alignment issue?

Hah, I fixed this before I even saw this 😂
Probably better to bring up issues directly in Discord today rather than on here.


Whitespace is hidden at end of line

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
New bug in 1.56.0: whitespace is hidden at end of line in editor
Steps to Reproduce

Turn on "show invisibles".
Type a line ending in a space character (for example, "abcde ").

Expected behavior:
The space character is shown at the end of the line, before the newline indicator (so the display looks like abcde ¬). This was the behavior before version 1.56.0.
Actual behavior:
The space character is hidden (so the display looks like abcde¬), until another character is typed after it. This bug is new in 1.56.0.
Reproduces how often:
100% of the time. This behavior is consistent in normal mode, even with all packages disabled (I used Package Cop to bisect), but does not occur in safe mode.
Versions
Atom    : 1.56.0
Electron: 9.4.4
Chrome  : 83.0.4103.122
Node    : 12.14.1

I'm using Mac OS 11.2.3.
Additional Information
None that I can think of.

This could possibly have been an issue with the Monokai theme. It went away after I upgraded Monokai, and I see this issue: https://github.com/kevinsawicki/monokai/issues/111


Registry has to wait for quarks

https://rancher-users.slack.com/archives/C021TRREKPT/p1623937453126600
🚢 Deploying ServiceCatalog...I0617 13:42:14.230820   18603 request.go:655] Throttling request took 1.164210551s, request: POST:https://<IP_ADDRESS>:41605/api/v1/namespaces
...............................................................................
✔  Quarks deployed
.....panic: Deployment epinio-registry failed with error: Failed installing Registry: Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "QuarksSecret" in version "quarks.cloudfoundry.org/v1alpha1"

We are already waiting for quarks pods to appear and be ready: https://github.com/epinio/epinio/blob/main/deployments/registry.go#L135
This means there can be a small time window between the moment the quarks deployment start and the moment when the quarks crd is established. I will add a check for the CRD to be in place.


add regclient to ecosystem tools github action

Is your feature request related to a problem? Please describe.
We currently verify against skopeo and oras. We should also do regclient.
Describe the solution you'd like
https://github.com/regclient/regclient

makefile test regclient exists, install if missing
add to Zot blackbox push-pull tests

regclient pull OCI image (if there is an image already in Zot)
regclient push new OCI image

makefile test regclient exists, install if missing
add to Zot blackbox push-pull tests (test/blackbox/pushpull.bats)
* regclient pull OCI image (if there is an image already in Zot)

* regclient push new OCI image

We can add the install step in the github workflow instead of in the Makefile, fwiw

Done in #668


Fix GitLab group support and pagination

Fixes #8 and #10
@szpak please try it out and provide feedback, if possible

I've just run it and it worked, thanks!
All direct repos and from subgroup was discovered when a group/subgroup pattern was provided in REPOS. It took some time to fetch the PRs (and even more for get the onboarding statuses - even up to 10 second per repo), but it was still <1 minutes for ~15 repos and ~150 MRs.
The scrapper hit a few times "Unable to parse dependency table: expected Link, but got", but it is not related and I will examine that and I will report it separately with sample MRs.
It would be probably good to have @robrobert99 run it with his repos, but for me it looks ok :)
(btw, I haven't tested the user: case)

Thank you. There were a few more problems with user: repos, which I fixed.

It worked for me with my repositories as well, but it also worked with the first implementation of the GitLab client. I noticed no difference in performance and had no error logs. However, I had one warning for gitlab_client.py at line 71, where the get_all=True parameter could be set as well.


Error while parsing response: SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data

Hi, i have error what can be wrong?

No idea what is going wrong, maybe PHP error are print in the middle of the JSON?

You seem to have a problem in function makeRequest(url, params, callback).
This happens if you have a JSON.parse(xhr.responseText) where xhr.responseText is not Json but an HTML page, that gets returned. Of course, this can not be parsed then as Json...
I had this error, when trying to run the shell on an application that was hosted on Windows. You don't have things like /bin/bash there. It seems the script is only useful on Linux hosts.

I know some people have it working with Windows but yes it is not the dev focus.
Also it is not normal you receive HTML content in response of the XHR.... Can you provide the content of the HTML page? is it a php error page?

Hi, i have error what can be wrong?

it seems like, php is not installed on that target machine.

@flozz What is the state of this issue, is this still open?

I think we can close this issue :)


[Help] Tree/Node Behavior with Auto Increment?

Hello,
Is it posible to use auto-increment with the tree/node behavior?
If not, how can I have an ID before the persist call?
I get the following error:
You must provide an id for this node if you want it to be part of a tree.
Maybe the librarie should use PostUpdate to get the ID and finally generate the path.
Imposible to use this behavior for me, I have no ID before to persist my entities.
Do someone has any example of implementation of this behavior?
Thanks.

Ok, I had to add the folowing function in my entity:
    /**
     * Get the node id
     *
     * @return int
     */
    public function getNodeId()
    {
        return is_null($this->id) ? -1 : $this->id;
    }

It now work fine, of course, I have to persist the parent before to persist the child.

Hi @skrosoft.
I'm not sure this library should bother with autoincrement issues.
One thing you can do to have an ID before persisting in database, is to generate an UUID into your code directly, instead of letting the database doing it.
Exposing an auto-increment ID is not considered as a good practice anyway.
This way, you guarantee a more secure way of storing IDs and at the same time, you keep the control of IDs out of the DB process.

@Einenlum exactly what I did.
The only change I had to do was changing the field because VARCHAR(255) was not enough.
/**
 * @ORM\Column(type="text")
 */
protected $materializedPath = '';

Hi, I'm going through old opended issues and PRs to cleanup too-long-opened items and close them. Thank you for your contribution and time.
We needs a feature with test and passing CI to be able to merge it without letting a bug in.
If this is still relevant for you, please add code with test and make CI pass first. Then we'll able to merge your feature without further waiting :+1:
Thank for understanding.