Component Error when attempting to use pre-defined label List

I've started receiving this error whenever I try to pass a label list as input to the text_labeler().
Dependencies:
python 3.11.4
streamlit==1.31.0
streamlit-annotation-tools==1.0.1
col1, col2 = st.columns(2)

with col1:
    st.header("Document")
    annotations = text_labeler(text=get_document(), labels=['one', 'two', 'three'])

with col2:
    st.header("Abstracted Fields")
    st.write(annotations)

ERROR: text_labeler component is not presented. However, the annotations object is presented as expected

Component Error
n.sort is not a function. (In 'n.sort(((e,t)=>e.start-t.start))', 'n.sort' is undefined)

Chrome Inspector shows the following error, but JS is enabled. Same on Brave and Safari.
<noscript>You need to enable JavaScript to run this app.</noscript>
Removing the labels allows the text_labeler to render.
annotations = text_labeler(doc_text)

web component loads and I can label without error

Look at the example https://github.com/rmarquet21/streamlit-annotation-tools/blob/master/examples/example.py
You have here the format of parameter labels
def labeler_page():
    st.title("Text Labeling Tool")

    text = "Yesterday, at 3 PM, Emily Johnson and Michael Smith met at the Central Park in New York to discuss the merger between TechCorp and Global Solutions. The deal, worth approximately 500 million dollars, is expected to significantly impact the tech industry. Later, at 6 PM, they joined a conference call with the CEO of TechCorp, David Brown, who was in London for a technology summit. During the call, they discussed the market trends in Asia and Europe and planned for the next quarterly meeting, which is scheduled for January 15th, 2024, in Paris."

    labels = {
        "Personal names": [
            {"start": 20, "end": 33, "label": "Emily Johnson"},
            {"start": 38, "end": 51, "label": "Michael Smith"},
            {"start": 327, "end": 338, "label": "David Brown"},
        ],
        "Organizations": [
            {"start": 118, "end": 126, "label": "TechCorp"},
            {"start": 131, "end": 147, "label": "Global Solutions"},
        ],
        "Locations": [
            {"start": 63, "end": 75, "label": "Central Park"},
            {"start": 79, "end": 87, "label": "New York"},
            {"start": 351, "end": 357, "label": "London"},
            {"start": 436, "end": 440, "label": "Asia"},
            {"start": 445, "end": 451, "label": "Europe"},
            {"start": 542, "end": 547, "label": "Paris"},
        ],
        "Time": [
            {"start": 0, "end": 9, "label": "Yesterday"},
            {"start": 14, "end": 18, "label": "3 PM"},
            {"start": 265, "end": 269, "label": "6 PM"},
            {"start": 519, "end": 531, "label": "January 15th"},
            {"start": 533, "end": 537, "label": "2024"},
        ],
        "Money": [{"start": 179, "end": 198, "label": "500 million dollars"}],
    }

    labels = text_labeler(text, labels)

OK. Perhaps there is an opportunity to clarify the code doc here.
The labels input isn't a list as defined in the code.  It's actually a Dict.
def text_labeler(text: str, labels=[], in_snake_case=False):
    """Create a new instance of "text_labeler".

    Parameters
    ----------
    text : str
        The text to be labeled

    labels : list

You're right, I'll take care of it.


The memory on the machine is less than 1 GB

[Enter feedback here]
version : Microsoft-ASR_UA_<IP_ADDRESS>_Windows_GA_16Jul2021_release
The Azure Windows VM has 16GB Memory, ASR mobility step fails with this, possibly bug.
11:05:51:Handler for check MachineMemoryCheck is SystemRequirementValidator.Handler
11:05:51:Entered Machine Memory Check
11:05:51:Total machine memory size : 15,9995613098145 GB
11:05:51:Machine has only 15.9995613098145 GB memory. Minimum memory of 99 GB required.
11:05:51:SystemRequirementValidator.SystemRequirementNotMet: Exception of type 'SystemRequirementValidator.SystemRequirementNotMet' was thrown.
at SystemRequirementValidator.SourceRequirementHandler.MachineMemoryCheck(IDictionary`2 attribMap, String logFile)
at MobilityServiceValidator.Program.Main(String[] args)
11:05:51:Error count : 1
11:05:51:Writing error info to Output file
11:05:51:The output json file C:\ProgramData\ASRSetupLogs\InstallerErrors.json does not exist
11:05:51:Writing installer errors list to output json file
11:05:51:error_name: ASRMobilityServiceInstallerRequiredMemoryError , default_message:
Failed to enable replication due to a prerequisite check error.
Possible causes: The memory on the machine is less than 1 GB. For Azure Site Recovery to efficiently function, a minimum memory of 1 GB is required.
Recommended action: Ensure memory of the machine is greater than or equal to 1 GB and retry the operation. , error_params:
11:05:51:Exiting main
11:05:51:
2021-09-03T11:05:51.7388335+00:00       Always: Trace Session Ended
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2b86a281-be89-e4e5-5696-a139c6e9bc50
Version Independent ID: 538995af-6c16-717d-d16f-58a94814b577
Content: Troubleshoot Azure VM replication in Azure Site Recovery - Azure Site Recovery
Content Source: articles/site-recovery/azure-to-azure-troubleshoot-errors.md
Service: site-recovery
GitHub Login: @rochakm
Microsoft Alias: rochakm

@VGSandz Thank you for reporting this. The issue has been addressed here - https://docs.microsoft.com/en-us/answers/questions/496250/asr-minium-99gb-of-ram-on-windows-vm.html

@VGSandz Closing this issue for now. If you've any further questions in this matter, you may continue the conversation in the forum shared in my previous post.


Docstring decorators confuse pdb, any way to fix?

FYI @adamklein this is what this looks like for me
(Pdb) debug s.sum()
ENTERING RECURSIVE DEBUGGER
> <string>(1)<module>()
((Pdb)) s
--Call--
> /home/wesm/code/pandas/pandas/core/series.py(734)sum()
-> @Substitution(name='sum', shortname='sum', na_action=_doc_exclude_na,
((Pdb)) l
729             -------
730             nunique : int
731             """
732             return len(self.value_counts())
733
734  ->     @Substitution(name='sum', shortname='sum', na_action=_doc_exclude_na,
735                       extras=_doc_ndarray_interface)
736         @Appender(_stat_doc)
737         def sum(self, axis=0, dtype=None, out=None, skipna=True, level=None):
738             if level is not None:
739                 return self._agg_by_level('sum', level=level, skipna=skipna)
((Pdb))

Hmm, I'll try in (pdb), but in ipdb it looks ok I think:
ipdb> debug s.sum()
ENTERING RECURSIVE DEBUGGER

(1)()->None
(ipdb>) l
[EOF]
(ipdb>) s
--Call--
/home/adam/code/pandas/pandas/core/series.py(734)sum()
-> return Series(counter).order(ascending=False)
(ipdb>) l
729             """
730             from collections import defaultdict
731             counter = defaultdict(lambda: 0)
732             for value in self.dropna().values:
733                 counter[value] += 1
734  ->         return Series(counter).order(ascending=False)
735
736         def nunique(self):
737             """
738             Return count of unique elements in the Series
739
(ipdb>)

Can you just hit 'n' to skip over the @Substitution docstring?

did you notice that it's pointing at the wrong line? That doesn't look like Series.sum

it looks like it's just a "feature" that any decorated functions, it starts pointed at the top decorator. same with @property, I guess I've seen @property so much that my brain has just tuned it out. So it's just a quick about the interactive debugger


RFR: Bugfix port error

Lots of changes!! If anyone wants a tour let me know.

@aamontal Tour is probably a good idea, but you've added a lot of tests and they are all passing. Merge away, and I'd like to see your two presentations on this topic uploaded somewhere and linked in README.md, too!


Bug fix/fight drop follower

Increase minimal timeout for RocksDB case. Computation based on body size not document count.

LGTM


Please add a License (MIT) to your cool project!

Hi there @brihernandez,
Just mentioning that for people to work + remix your project, a license file is needed.
I added the MIT License for now as a default one for your nice tutorial project!
Hope this helps!

Thanks for merging, that's awesome! Grateful for your understanding! :smile:


Unable to read specific barcode with type Code-128

Hello Guys,
I am using this barcode reader and it seems very good but i am facing one issue with CODE-128 type. I am attaching screenshot with highlighting two different barcodes but with same type CODE-128. The green one is very easily readable within a second but  i am facing difficulty with red one. It takes a lot of time to read with 90% failure rate.I am using version 6.0 and i need very urgent help. Your help will be appreciated. Thanks

I have the same problem with this image.
The library is based on the Apple's AVFoundation so if there are issues to read code should open a bug report (https://bugreport.apple.com).

Thanks @yannickl for the reply.
Can you please suggest me any alternative which can read that barcode? i need to integrate this feature in project very badly.

Maybe ZBar but it's much harder to integrate in an iOS project.


Error when dragging cell out of collectionView

For some reason when I implemented the exact same files into my own project, I am getting this issue whenever I drag a cell out of a collection view:
‘Invalid update: invalid number of items in section 0. The number of items contained in an existing section after the update (21) must be equal to the number of items contained in that section before the update (21), plus or minus the number of items inserted or deleted from that section (1 inserted, 0 deleted) and plus or minus the number of items moved into or out of that section (0 moved in, 0 moved out).’
I set up the storyboard the exact same way as the example project, but I can't seem to figure out this issue. Thanks, Neil

Are you implementing the delegates that are responsible for updating the actual data?

I think so, but it looks like the problem is in the data source. The crash happens in the willMoveItem function. In my project, the dragDropDataSource just shows my view controller in the debugger, but in the example project it shows the three collection views, the data, and the dragAndDropManager as well. I'm pretty inexperienced so I'm not sure what this means.

Have a look at the guide. You need to implement a part of the protocol so that when you move items around, delete or add them you update the model first.

I used the exact same files from the example. Here are pictures of the debugger in the willMoveItem function in the example project vs my project

Can you please send my a zipped file of your project? I might have some time to have a look.

TestKDCollectionView.zip

Ok, if you look at the guidelines you will see that I used the collection view's tag as an index to the data. It is just for testing purposes and you should create your own strategy to pick the correct data depending on the collection view.
Uploading TestKDCollectionView.zip…


Adding pid & lyap_control pkgs for kinetic.

Yoy cannot just rename the release tags. You need to run a bloom release for Kinetic.

@dirk-thomas OK. I interpreted from the email to ros-users that rosdistro was the first step:
"Once your package has been added to Kinetic in rosdistro, you can generate
a prerelease command on prerelease.ros.org."

If you want to adda release entry to do a prerelease it should not have a version field.

I believe you just need the source entry so you can run a prerelease (using the devel option). You can omit the release entry until your first release I think.


z/Linux R&D Efforts

Starting in Nov. 2021 the project began investigating the possibility of porting GenevaERS to z/Linux.  On Dec 17, the R&D meeting resulted in these insights and next steps.
Points Learned:

Alternative work effort could be on Python
Object module format transferability doubtful
Then HL ASM Macro accessibility becomes a question for assembly on z/Linux.  (The product exists.  Licenses?)
We have admin rights to z/Linux so can create new accounts there

Next Steps:

Assembler (or even C) on z/Linux manual access and knowledge base.  Nicolas question?
Could ask Vicom Infinity for access on z/Linux to HL ASM Macros.  Kip to ask?
Learn how to make new z/Linux accounts and create one for Karl.  Neil to ask Bob.
Rename the spark-poc to the R&D Repo.  Kip to investigate.

Reference files:  http://www.tachyonsoft.com/s8139db.pdf
http://www.longpelaexpertise.com/ezine/HLASMfromJava.php

R&D Results from February 18th R&D Session:

Bob M has successfully assembled and run a hello world application on z/Linux
GIl has found that the HLASM toolkit for z/Linux is a very different syntax than on z/OS

Proposed approach:  For HLASM toolkit, we can generate ASM code on z/OS which can be transferred to z/Linux for assembly.  This follows the existing license agreement as a license is not needed for run-time, only assembly, and the assembly on z/OS will still require that license for anyone desiring to do a build.  This needs to be tested to see if it is possible.
Proposed Study of Operating System Functions:  The next step would be a study of approaches to existing code.  It would have the following structure:

Objective of study, including

Reuse of existing existing code base
Performance of existing code base and new functionality, weighted with time to develop
Learning of z/Linux issues.

For example, in the short run, we would likely use standard read and write routines on z/Linux for even event files in order to develop quickly, rather than GenevaERS high performance BSAM type IO as is done on z/OS today.

A list of all operating system functions in GenevaERS today, and the equivalent function in z/Linux
An analysis by each one of these function of the following:

Possible approaches to conversion of that function to z/Linux
Weights of those approaches  against the opening criteria
Suggested approach for this function

An analysis of potential conflict between recommended approaches for each of the functions, in the overall approach.
An overall recommended approach for the development effort, with some sense of resources and time needed.


Dialog should communicate scenario details

#90 describes how the overworld icon should have an icon, but this should also appear when you talk to the customer.
They could say something generic like, "I was hoping you could help me in my kitchen today!" and a popup window could appear with some details:
  Goal: 100 points
  Bonus: Finish as fast as you can!
  Difficulty: Medium hard
  Reward: $2000
  Other: Your next pieces are untrustworthy

Or maybe something more thematic:
  Order: 1,000 kCal of food, as fast as possible!
  Urgency: I'll get to it frosting tomorrow morning...
  Bill: $20.00
  Other:

Downgrading; with the game's new scenario-based structure, this isn't as important.

Closing due to removal of freeroam mode (#1257)


Readme error in GRPC go examples

In provider-go:

pact_verifier_cli -f ../consumer-go/pacts/grpc-consumer-go-area-calculator-provider.json --transport grpc -p 39821

The json doesn't exist
In consumer-go:

The test method test_proto_client first sets

The link doesn't exist

The JSON file is created by running the consumer tests in consumer-go.


[Concurrency] Refine getResumeFunctionForLogging to avoid reading invalid future contexts.

When using a future adapter, the resume context may not be valid after the task starts running. Only peer through the adapter when we're starting to run.
rdar://126298035

@swift-ci please test

@swift-ci please test macos platform

@swift-ci please smoke test macos platform


Which country?

Screenshots
Example 1

Example 2

@gavinwye Is this a specific pattern? Or is it just a set of radio buttons and a text field?
The radios should be vertically stacked because there is more than 2 of them. See http://govuk-elements.herokuapp.com/form-elements/#form-radio-buttons

@stevenaproctor Those are separate screenshots. I've added headings to (hopefully) make it clearer.
It's more of a "Country picker" component IMO

@rpowis OK. Is it not superseded by the GOV.UK autocomplete or a standard set of radio buttons?

Although created long before the new radio buttons Register to vote have this pattern - https://www.registertovote.service.gov.uk/register-to-vote/country-of-residence?_ga=2.258443402.1688332797.1511342022-331215250.1510583990

But is it a pattern or just a fairly simple set of radio buttons?

Country finder pattern from Defra - https://defradigital.blog.gov.uk/2017/11/22/putting-the-service-toolkit-to-work/

GDS are doing this so we should not be. But speaking to @timpaul the work on this has been paused so if we have services that need this we can potentially pick up the work that GDS have done and build on it with a view of contributing this back.

This issue has been closed because it will be part of the GOV.UK Design System. Possibly as part of the accessible autocomplete. Otherwise, it is a text field or a set of radio buttons.


added forgot password link

Description
Added a password forgotten link in the login screen so that it opens in the chrome custom tab.
Related issues and discussion
fixes #824
Screen-shots, if any

Checklist

[x] Apply the AndroidStyle.xml style template to your code in Android Studio.

[x] If you have multiple commits please combine them into one commit by squashing them.

[x] Read and understood the contribution guidelines .

@Karljoones  Is it okay now?

LGTM, @Karljoones ?

Merging, thanks @sachincool :)


Multiple definition error on __builtin_clz() in MSVC

In MSVC, the header file util.h defines a function __builtin_clz().
Since it is not a inline function, a multiple definition error LNK2005 can occur.
https://github.com/lemire/FastPFor/blob/d873fe18edf487ff7e4e737883e6f63a54a0a578/headers/util.h#L117-L126
A possible solution is adding the inline to the function:
inline uint32_t __builtin_clz(uint32_t x) {

Would you issue a PR? This way you get credit for your contribution.


Whatever bgcolor is set on paraview view can now be set in cinema as wel...

...l.
The accompanying script shows how you would set one background color on the view in paraview, then also write it out into the metadata so that cinema can use apply it to the container.

@jourdain @patrickoleary What do you guys think of this?


More DRY code thanks to using inheritance + Spinners, Badges, Alerts.

When adding spinners to this, i noticed how much more DRY the code could be.
As a result, this is one big PR with both those changes, Spinners and more DRY code, and also Badges and Alerts thrown in for good measure.
AFAIK the only downside of the factory pattern is that type(GrowDangerSpinner) will show Spinner (and type checkers will do the same)

Hi @laundmo,
i like the changes and i wan't that functionality, but i don't like the approach. I don't think the added complexity is worth the usecase.
I don't expect this code to change much in the future, because bootstrap5 wont change in a major way and Lona neither (at least from a public facing API point of view), so the maintenance on this repository will presumably remain low. So there is no point in decreasing the readability to shorten up the code in my opinion.

I changed it about, it's still slightly simplified because STATIC_FILES does really not need to be redefined for every single node thanks to inheritance. This also allows people to use only a Div from this library and still get the static files.

Much better, thanks! I still have some nitpicks:

Please use single quotes instead of double quotes to be consistent with the rest of the code base
Please don't use one-line if statements
You define lona_bootstrap.nodes.Div as a Div that contains all Bootstrap 5 related static files. This name is confusing because it is named like lona.html.Div but behaves slightly different
Please squash your commits together

Please use single quotes instead of double quotes to be consistent with the rest of the code base

sorry, i use the black formatter, and thats what it uses

Please don't use one-line if statements

i can remove it, but i have to ask why?

You define lona_bootstrap.nodes.Div as a Div that contains all Bootstrap 5 related static files. This name is confusing because it is named like lona.html.Div but behaves slightly different

Do you think i should change the name to something like BootstrapDiv?

Please squash your commits together

can do

@laundmo,

Please don't use one-line if statements

i can remove it, but i have to ask why?

I generally dislike one-line statements. The benefit is very low, but they make the code less readable, especially for beginners.
Thanks for contributing! :)


Python script for checking that the examples match the event schema.

Does the same checks as check.sh, but is a lot faster making it
suitable for using as a pre-commit hook.
I don't suggest replacing check.sh since it's good to check that the
schema works with multiple implementations of jsonschema.

LGTM except minor comments


Add input validation to simple metadata api

Coordinate with validation guidelines https://github.com/theupdateframework/tuf/issues/1130
Description of issue or feature request:
Some suggestions:

Avoid schema, see secure-systems-lab/securesystemslib#183 (just don't use it)
Make use of type hints for simple type validation
Perform additional non-metadata parameter validation at user boundary
Provide methods to validate JSON representation at user boundary, i.e. fail on bad json metadata in from_json_file/to_json_file method, but with option to
disable check as there might be a justified reason to read or write WIP
metadata to json.
Be lenient on bad/invalid metadata objects in memory, they might be
work in progress. E.g. it might be convenient to create empty metadata
and assign attributes later on.
Consider using in-toto style ValidationMixin (see the mixin and it's usage for details).

Current behavior:
No input validation
Expected behavior:
Add input validation

Consider using in-toto style ValidationMixin (see the mixin and it's usage for details).

This looks like a nice pattern. Each class defines appropriate validation methods, which are called by the Mixin's validate() method at the end of the object's construction. Any thoughts on whether a decorator might be a more idiomatic approach than a Mixin? We can
This article suggests how to to type validation with type hints https://aboutsimon.com/blog/2018/04/04/Python3-Type-Checking-And-Data-Validation-With-Type-Hints.html

Consider using in-toto style ValidationMixin (see the mixin and it's usage for details).

This looks like a nice pattern. Each class defines appropriate validation methods, which are called by the Mixin's validate() method at the end of the object's construction.
Any thoughts on whether a decorator might be a more idiomatic approach than a Mixin? We could wrap classes with a decorator which performs validation after init, before returning the instantiated object.

https://aboutsimon.com/blog/2018/04/04/Python3-Type-Checking-And-Data-Validation-With-Type-Hints.html
https://realpython.com/primer-on-python-decorators

Another idea is to copy validation techniques Django/Rails use...

Nice idea. I took a brief look those look to be quite complicated and not equivalent to what we're trying to do here Django Model validation.

Good thinking, @trishankatdatadog. But I agree with @joshuagl that we might not need something as powerful (Django's validation is really tailored towards web forms and/or ORM, similar is true for WTForms, which I also briefly considered).
I think the in-toto approach is not so bad. It's also featured in this quite interesting blog post about different instance attribute validation techniques, at least the "individual validation functions" aspect (not the neat self-inspecting mixin part).
The blog also mentions two promising validation libraries, marshmallow and pydantic,  which both are actually de/serialization libraries with validation features.  Given that we want to minimize dependencies (see #1165), I'm leaning towards rolling our own validation, which doesn't even have to be that generic (see secure-systems-lab/securesystemslib#183).
The blog also mentions a Python built-in feature, i.e. Descriptors, that as per official docs seems well-suited for attribute validators. Although it looks interesting, I'm unsure if it gives us the flexibility of e.g. initializing empty objects, assigning values, and only then calling validate, which might be a desirable usage pattern (see snippet 2 in https://github.com/theupdateframework/tuf/pull/1223#issuecomment-737188686). Same reservation goes for decorators, which the blog also mentions in conjunction with descriptors. But I can check if there is a solution that involves decorators and/or descriptors that allows for said flexibility.
What I like about both the decorator and descriptor approach(es) is that they make the constraints on the attributes more visible (in the head of the class definition) than vanilla validation methods.

The blog also mentions a Python built-in feature, i.e. Descriptors, that as per official docs seems well-suited for attribute validators. Although it looks interesting, I'm unsure if it gives us the flexibility of e.g. initializing empty objects, assigning values, and only then calling validate, which might be a desirable usage pattern (see snippet 2 in #1223 (comment)).

Descriptors look nice, and I'm all for avoid additional dependencies. I believe the pattern of: initialising empty objects, assigning values, and then validating should still work – so long as our empty objects have sane defaults. Based on 5mins experimentation in the Python interpreter:
>>> class MetadataType:
...     def __get__(self, obj, objtype=None):
...         return self.value
...     def __set__(self, obj, value):
...         if value not in ['root', 'timestamp', 'snapshot', 'targets']:
...             raise ValueError('Invalid _type field')
...         self.value = value
...
>>> class Metadata:
...     type = MetadataType()
...     def __init__(self, type):
...         self.type = type
...
>>> class Targets(Metadata):
...     def __init__(self):
...       super().__init__('targets')
...
>>> md = Metadata('badger')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<stdin>", line 4, in __init__
  File "<stdin>", line 6, in __set__
ValueError: Invalid _type field
>>> md = Metadata('root')
>>> md.type = 'badger'
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<stdin>", line 6, in __set__
ValueError: Invalid _type field
>>> t = Targets()
>>> t.type
'targets'

The __slots__ mechanism, described in the Descriptor HowTo, could be something worth including in our new classes also. hat-tip @sechkova

I wonder if sane defaults will always be possible, e.g. when thinking of the newly added MetadataInfo or TargetInfo in https://github.com/theupdateframework/tuf/pull/1223.
But maybe the usage pattern that requires initialization of empty objects is suboptimal. I must say that it would be quite nice to always have certainty about the validity of tuf objects.

In https://github.com/theupdateframework/tuf/pull/1223/commits/7cfd100eeb37a7878741722a1b766b5313022287#r541018751 we discussed whether JsonDict is the right name for our generic Dict[str, Any] type, and agreed to handle that type's name with this issue instead.

In https://github.com/theupdateframework/tuf/pull/1223/commits/7cfd100eeb37a7878741722a1b766b5313022287#r541018751 we discussed whether JsonDict is the right name for our generic Dict[str, Any] type, and agreed to handle that type's name with this issue instead.

In a discussion with @jku, we noticed that our tests for the metadata classes don't test instantiating metadata objects
without their required fields.
We should add tests for that.

I think we can lose this issue as we discussed that each of the cases has to be discussed separately.
We don't need a common strategy to do this.
We had discussions validation for all cases separately:

Signed attributes: #1418, #1430, #1420
Key attributes: #1438
Role attributes: https://github.com/theupdateframework/python-tuf/pull/1360/commits/0c3131b4a2b2f9abb6c35d271e38db7ffa7ea18b, #1439
Root: #1630
MetaFile: #1451
DelegatedRole: https://github.com/theupdateframework/python-tuf/commit/76d46336007ef9a6974b5ef3e6bac7e3a62924f6, https://github.com/theupdateframework/python-tuf/commit/aa480b1280f38741155b8d065952db86115b9750, #1558, #1527 (still open)
TargetFile: #1451
Targets: we didn't find need to validate it
Additional: #1356,

@lukpueh and/or @joshuagl do you agree with me?

Agreed, thanks Martin. Closing because we have implemented validation on a case-by-case basis.


CUDA_ERROR_ILLEGAL_ADDRESS error when running cityscapes training

I am trying to run the cityscapes training with the information provided. Prepared the data as indicated.
Using resnet50_beta_os32.textproto with cityscapes_panoptic.
tensorflow              2.5.0
tensorflow-gpu       2.5.0
NVIDIA-SMI 460.84
CUDA Version: 11.2
cuDNN version 8.1.01GeForce RTX 2080  (10MiB / 11019MiB)
I changed the batch size from 32 to 8 in case I was running out of memory, but I got the same error
CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered
Any suggestions?
Commad:
python trainer/train.py \     --config_file="configs/cityscapes/panoptic_deeplab/resnet50_beta_os32.textproto"\     --mode=train \     --model_dir="output" \     --num_gpus=1
Output:
....
2021-07-28 12:18:26.707841: I tensorflow/core/common_runtime/bfc_allocator.cc:1066] Stats:
Limit:<PHONE_NUMBER>8
InUse:<PHONE_NUMBER>
MaxInUse:<PHONE_NUMBER>
NumAllocs:                        1320
MaxAllocSize:<PHONE_NUMBER>
Reserved:                            0
PeakReserved:                        0
LargestFreeBlock:                    0
2021-07-28 12:18:26.707916: W tensorflow/core/common_runtime/bfc_allocator.cc:467] ***************************************************************************************************_
2021-07-28 12:18:26.707968: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at conv_ops.cc:662 : Resource exhausted: OOM when allocating tensor with shape[8,256,257,513] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
restoring or initializing model...
restored model from /home/mimi/code/deeplab2_proj/deeplab2/output/CITY_PANOPTIC_EXAMPLE/ckpt-0.
restored from checkpoint: /home/mimi/code/deeplab2_proj/deeplab2/output/CITY_PANOPTIC_EXAMPLE/ckpt-0
train | step:      0 | training until step 60000...
Traceback (most recent call last):
File "trainer/train.py", line 81, in
app.run(main)
File "/home/mimi/Envs/deeplab2/lib/python3.6/site-packages/absl/app.py", line 312, in run
_run_main(main, args)
File "/home/mimi/Envs/deeplab2/lib/python3.6/site-packages/absl/app.py", line 258, in _run_main
sys.exit(main(argv))
File "trainer/train.py", line 77, in main
FLAGS.num_gpus)
File "/home/mimi/code/deeplab2_proj/deeplab2/trainer/train_lib.py", line 191, in run_experiment
steps=config.trainer_options.solver_options.training_number_of_steps)
File "/home/mimi/code/deeplab2_proj/deeplab2/models/orbit/controller.py", line 240, in train
self._train_n_steps(num_steps)
File "/home/mimi/code/deeplab2_proj/deeplab2/models/orbit/controller.py", line 439, in _train_n_steps
train_output = self.trainer.train(num_steps_tensor)
File "/home/mimi/code/deeplab2_proj/deeplab2/models/orbit/standard_runner.py", line 146, in train
self._train_loop_fn(self._train_iter, num_steps)
File "/home/mimi/Envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/eager/def_function.py", line 889, in call
result = self._call(*args, **kwds)
File "/home/mimi/Envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/eager/def_function.py", line 950, in _call
return self._stateless_fn(*args, **kwds)
File "/home/mimi/Envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 3024, in call
filtered_flat_args, captured_inputs=graph_function.captured_inputs)  # pylint: disable=protected-access
File "/home/mimi/Envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 1961, in _call_flat
ctx, args, cancellation_manager=cancellation_manager))
File "/home/mimi/Envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 596, in call
ctx=ctx)
File "/home/mimi/Envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/eager/execute.py", line 60, in quick_execute
inputs, attrs, num_outputs)
tensorflow.python.framework.errors_impl.ResourceExhaustedError: 2 root error(s) found.
(0) Resource exhausted:  OOM when allocating tensor with shape[8,64,513,1025] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
[[{{node while/body/_1/DeepLab/resnet50_beta/stage2/block1/conv1_bn_act/conv/Conv2D}}]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.
 [[while/merge/_973/_13]]

Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.
(1) Resource exhausted:  OOM when allocating tensor with shape[8,64,513,1025] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
[[{{node while/body/_1/DeepLab/resnet50_beta/stage2/block1/conv1_bn_act/conv/Conv2D}}]]
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info.
0 successful operations.
0 derived errors ignored. [Op:__inference_loop_fn_46399]
Function call stack:
loop_fn -> loop_fn
2021-07-28 12:18:28.097617: E tensorflow/stream_executor/cuda/cuda_event.cc:29] Error polling for event status: failed to query event: CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered
2021-07-28 12:18:28.097660: F tensorflow/core/common_runtime/device/device_event_mgr.cc:221] Unexpected Event status: 1
Fatal Python error: Aborted
Thread 0x00007f85d6c43740 (most recent call first):
File "/home/mimi/Envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/ops/gen_dataset_ops.py", line 1264 in delete_iterator
File "/home/mimi/Envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/data/ops/iterator_ops.py", line 546 in del

If it is related to GPU memory, maybe take a look at FAQ.
For example, you could use crop size 513x1025 and batch size 1 and see if it trains.
If it works, you could then gradually increase the batch size and crop size.

Your suggestions solved the issue. Thank you.


Support customisation of the lyric panel rendering

Font face, font size, foreground & background colours, etc so that it looks reasonable (or can be made to look reasonable) on non-default styles.

Would also like this very much. I had my LyricShow3 fully customized, but now OpenLyrics is so tiny I can't read it unless I get really close to my monitor.


Validate the output style json

The map will refuse to start with errors anyway, but this will cause them to show up in the checks.

Will this also cause the build to fail if there are errors?

Yes.
I expect that would only be an issue if the two npm packages happen to diverge, but not if their releases go correctly.


Add back withdrawals

The withdrawal logic was removed during some of the refactors. Put it back in and test it works on Sepolia

Closed by #33


x/tools/gopls: provide foldingRange for the case sections within a select

Filing this report per @stamblerre's feedback on Gopher Slack #vscode channel
What version of Go, VS Code & VS Code Go extension are you using?

Run go version to get version of Go

go version go1.14.4 windows/amd64

Run code -v or code-insiders -v to get version of VS Code or VS Code Insiders

1.47.0 d5e9aa0227e057a60c82568bf31c04730dc15dcd x64

gopls version

golang.org/x/tools/gopls 0.4.3
<EMAIL_ADDRESS>h1:irz7Q+XdHNECamFKbNWKvMV2Ak6zBbwdwbZndG4545I=

Check your installed extensions to get the version of the VS Code Go extension

v0.15.1

Run go env to get the go development environment details

set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\atc0005\AppData\Local\go-build
set GOENV=C:\Users\atc0005\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\atc0005\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=T:\github\brick\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\atc0005\AppData\Local\Temp\go-build004075302=/tmp/go-build -gno-record-gcc-switches

Share the Go related settings you have added/edited
Run Preferences: Open Settings (JSON) command to open your settings.json file.
Share all the settings with the go. or ["go"] or gopls prefixes.
    "[go]": {
        "editor.defaultFormatter": "golang.go",
        "editor.suggest.insertMode":"replace"
    },
    "go.formatTool": "goimports",
    "go.useLanguageServer": true,
    "[go.sum]": {
        "editor.defaultFormatter": "golang.go"
    },
    "[go.mod]": {
        "editor.defaultFormatter": "golang.go"
    },
    "go.lintTool": "golangci-lint",
    "go.lintFlags": [
        "--new"
    ],
    "go.languageServerFlags": [
        //"-rpc.trace", // for more detailed debug logging
    ],
    // Force VSCode to use native Windows 10-provided SSH and by extension,
    // the ssh-agent holding the private key used to access private Git repos.
    // This unfortunately means that I will need to load the key twice: once
    // for Git for Windows terminal use and again for VSCode to use.
    "go.toolsEnvVars": {
        "GIT_SSH":"C:\\WINDOWS\\System32\\OpenSSH\\ssh.exe"
        //"GOPRIVATE": "github.com/atc0005/brick",
        // "GIT_ALLOW_PROTOCOL":""
    },

Describe the bug
I can expand case blocks within a switch statement, but cannot expand case blocks within a select statement.
Example of collapsing a case within a switch statement:

Example of where this isn't enabled for a case within a select statement:

Note: I can collapse the entire select statement, but that's not always the desired behavior.
While I cannot recall if this ever worked, this seems like odd behavior.

@hyangah: Thanks for the feature request, @atc0005 !
This advanced language analysis feature is available through gopls, so I will transfer this issue to gopls issue tracker.

Thanks!


visualization

Hello!Thanks to your excellent work!I am very interested in your visualization part, can you share the code? Thank you very much

interested in the visualization part, too

We use the openTSNE library to visualize the visual features of the base branch. Please refer to the code.


[FLINK-4172] [gelly] Don't proxy a ProxiedObject

Retrieve the proxied object and wrap in a new proxy.

@vasia or @StephanEwen would you have a minute to look this over? I'll look to merge this for RC1.

I am not an expert in the proxy magic of Gelly, but it looks fine to me.
From my side, feel free to merge at your discretion...

+1 to merge. The previously not working TriangleListing example (undirected, rmat, print) is now working with this change.


add all missing values for properties in flex

http://www.w3.org/TR/css-flexbox-1/#property-index

Thanks! Merged as 341a850


docker image very big

almost 1.8GB decompressed...
is there any way to improve the size?
Thanks for all the work on shynet :-)

Hey! We could probably switch to a leaner base image at some point, and I'd review a PR that made this change. For now, though, this isn't a top priority.


Add details about voltage and amperage of chargers

It would be helpful to add information about maximum voltage and amperage of chargers (e.g. to differentiate what power a DC charger can deliver to 400V vs. 800V vehicles).
This data is currently not available through the GoingElectric API (or actually, it is available, but only with the API key used by the web frontend - 3rd party applications do not get the data).
OpenChargeMap does provide this data.

Implementing it for OpenChargeMap and making its datasource better (contributing to OpenChargeMap in germany) would be a functional solution at the moment.


Align resource parameter "args" to choco's "params" ?

Would it be possible to alias the args parameter so that it also takes the same name as choco ("params")?

The args attributye actually alligns with the --installargs parameter, not params.

probably need something for params :)

Well there is the options attribute which is a hash of of arguments to send to choco.exe:
chocolatey "some_package" do
  options ({'params' => 'my_value'})
end

Not sure we want to create one to one mappings of resource attributes to choco parameters.

Ah, well that works as well. :)


Add pagination to admin resources

Description
We want to be able to explore all the records in a table without loading them all at once.
Reviewer Notes

Should we move more of the pagination logic from the handler into the Pagination service? I wasn't sure exactly where to draw the line.

Setup

make server_run
make client_run
Log in to the admin app.
You should only see 25 records per page and be able to navigate between pages.

Code Review Verification Steps

[x] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

@lynzt it looks like we just don't have a test user with the email<EMAIL_ADDRESS>😄 . That's confusing. I'll address your other feedback soon.

looks good...
just a thing I noticed when testing this... you can put any numbers in and they're dealt w/ correctly... but if you put in a non-numeric character, it won't bring back any rows and just says, no results found.
might wanna catch if we're passed in a non-numeric number...
other than that, 🚢

Good catch! I'll create another ticket for that.


Add Suite branding to navbar

Consistent logo, color, and height with other suite products.
@bartvde Is this fine to add in the main repo? Is WPS builder being used anywhere other than suite where it may want different branding (I assume not, but thought it would be good to check).

Sure this is fine to add @tbarsballe put one comment in the diff


Feedbuilder config fixes

Changes made to the Feedbuilder tool to allow configs to be saved and used on different machines for the same codebase.
Changes in detail:

Added support for relative paths in config based on application path.
Fixed so that current settings are persisted on close as intended.
Stored configurations should now load properly. Fixes #88.
Added support to adopt configurations from other machines.
Fixed an error that could occur if a configuration was saved with one of the textareas left empty.
Fixed the "New" button functionality.
Changed so that debug build out is located in the FeedBuilder/bin folder.

lgtm, thanks!


Replace META-INF/spring-configuration-metadata.json manually

To replace META-INF/spring-configuration-metadata.json manually instead of auto-generation.

该项目是否可以投入到生产环境中，查看aliyun的Maven私服已经到了dubbo-spring-boot 2.0版本,0.11本周什么时间点可以发布。

Hi,
Welcome!
Would you please consider ask in English? Since this project is moved to ASF repo, we hope it is understandable by people all over the world so that everyone can join to discuss.

Whether the project can be put into production environment, we can see that aliyun's Maven private clothing has arrived in dubbo-spring-boot 2 version, and 0.11 what time can we release this week?

@duming08899  I will commit code in this week,  will release one in next week.


Clarify that raw React types can be used in libdefs.

Closes #1795, #1954.

Doing import type works inside the module (as long as it is a built-in type) though right? For example doing stuff like
declare module 'other-module' {
  import type { Node } from 'react';
  import type { Server } from 'http';

  declare var server: Server;
  declare var node: Node;
}

Should that be mentioned or should it not be to avoid complexity?
As a side note it might be worth putting this cheatsheet somewhere in the CONTRIBUTING.md so people know which internal types they can use.

Catch up on #1857 before continuing, in case you haven't.

Unfortunately flow-typed does not currently support the second approach as it can't depend on other libdefs during the tests. Other problem is nasty dependencies between library definitions which might become very hard to maintain.

As I interpreted this, it doesn't work full stop. Admittedly, I didn't test it. Have you found otherwise?

Yeah, I have done so in some of the definitions I've submitted. Just double checked:

Ah, good to know.
Well, based on the conversation in #1857, the current ruling is to not encourage dependencies between libdefs, because that could get gnarly very, very quickly. I propose we move forward with this PR, continue the conversation there, and update if needed?

Sounds good 👍

Can I get a formal 👍 from @villesau or @GAntoine?

It's actually possible to import types which Flow has baked in, like everything from Node and React.

@villesau I think that's what was being discussed above your comment.


Typo in Kubernetes docs: Externalizing config using MicroProfile, ConfigMaps and Secrets

"tha approrpriate" in
https://kubernetes.io/docs/tutorials/configuration/configure-java-microservice/configure-java-microservice/
Although Secrets are also used to store key-value pairs, they differ from ConfigMaps in that they're intended for confidential/sensitive information and are stored using Base64 encoding. This makes secrets tha approrpriate choice for storing such things as credentials, keys, and tokens, the former of which you'll do in the Interactive Tutorial. For more information on Secrets, you can find the documentation here.

PR'ed this here: https://github.com/kubernetes/website/pull/24552
Closing the issue


Revert Jakubs ecs-deploy script in Jenkins file

Sad times, I’d be interested to know why it had to be removed.


Remove cortexOrgID from Prometheus scaler

In line with the deprecation of cortexOrgID in v2.10 and its scheduled removal in v2.12, this commit removes all references to cortexOrgID within the Prometheus scaler codebase and documentation.
Fixes #5538

Mind updating the docs as well please?

Done

Could you help to update the CHANGELOG?

Can you please tell me where should i update i am new in this

You can update it in https://github.com/kedacore/keda/blob/main/CHANGELOG.md
There is a checklist in default description when you create a PR. You can follow it in the next time.
Checklist

[ ] When introducing a new scaler, I agree with the scaling governance policy
[ ] I have verified that my change is according to the deprecations & breaking changes policy
[ ] Tests have been added
[ ] Changelog has been updated and is aligned with our changelog requirements
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[ ] A PR is opened to update the documentation on (repo) (if applicable)
[ ] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Can you please tell me where should i update i am new in this
thsi is the file https://github.com/kedacore/keda/blob/main/CHANGELOG.md 😄

@MeenuyD Any update on this PR?

We still need to address this

This is already done


New version: ByteDance.Lark version 32

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/113566&drop=dogfoodAlpha

Close with reason: Duplicate version;


unable to float/align last content in inline form fields to the right

http://jsfiddle.net/bhpn1j6z/
No matter what I try, I can't get the content of the final three wide field in the above example to float its content to the right of the allotted space. Am I missing something crucial, or is this in fact a bug?

It looks like the desired behavior can be obtained through two means:
  display: -webkit-flex;
   display: flex;
   -webkit-flex-direction: row;
   flex-direction: row;
   -webkit-justify-content: flex-end;
   justify-content: flex-end;

or
width: auto and margin-left: auto


Update embedQuery to use inputType

Input type is a required parameter when using v3 models. It is ignored for v2 models.
Adding it here satisfies both use cases and avoids a Cohere API rejection when using v3 models.

Fixes #3900

Thank you, pushing a new version now.


[BUG] Font Color error in Goals section on dashboard

Describe the bug
Whatever we add in Goals section the font color is white on white background making it hard to visible

To Reproduce
Go to Dashboard
Go to Goals
Enter anything
Expected Behavior
No response
Screenshot/ Video
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hey, I'd like to help, can you assign me please?


[TASK] Be able to manage tasks for sub-assembly

--

be able to add tasks for sub-assembly. Quote, product order
be able to add tasks for sub-assembly. Quote, product order


Documentation of sap.ui.core.RenderManager extends Object (Javascript Object)?

OpenUI5 version: latest (git)
Browser/version (+device/version): all
Any other tested browsers/devices(OK/FAIL): n/a
URL (minimal example if possible): n/a
User/password (if required and possible - do not post any confidential information here): n/a
Steps to reproduce the problem: n/a
What is the expected result?
Full (XPath-)Definition to the parent object in JSDoc for RenderManager expected (sap.ui.base.Object), same as everywhere else.
What happens instead?
Relativ Path is displayed (Object)
Any other information? (attach screenshot if possible)
See following lines:
Bad example:
https://github.com/SAP/openui5/blob/db8fdb2982bced534bda17fa2fea25f3669bd5e1/src/sap.ui.core/src/sap/ui/core/RenderManager.js#L155
Good example:
https://github.com/SAP/openui5/blob/db8fdb2982bced534bda17fa2fea25f3669bd5e1/src/sap.ui.core/src/sap/ui/core/EventBus.js#L22
I'm currently writing a automatic JSDoc parser that tries to handle all the XSD generation for XMLView-Intellisense. During this conversion I noticed that during my minimal examples that the RenderManager points to a relativ "Object" path in it's documentation in contrast to every other piece of JSDoc documentation.
edit: it's actually sap.ui.base.Object instead of sap.ui.core.Object, my bad.

The current JSDoc is correct.
RenderManager is not extending sap.ui.base.Object nor any other UI5 base class, its prototype is indeed derived from the prototype of the JavaScript built-in Object.
As the SDK fails to display that built-in class correctly ("resource not found"), I would rather suggest to remove the @extends from the JSDoc.

BTW: instead of parsing the JSDoc on your own, I would recommend to rely on our api.json files. They are an API summary extracted from the source code, based on JSDoc and UI5 class metadata (managed properties, aggregations, designtime metadata etc.).

Thanks for the info - I assumed that if it extends Object i'd assume a sap.ui object and not the basic Javascript object.
With that in mind I closed the PR for this.
Are you aware of any other instances where there is a similar case here?
I'd assume if it doesn't extend any base class that there is no need for a "@extends" property in the jsdoc, but if there are other cases where a similar @extends is in the source we would prolly like to keep it in a unified style.

I quickly searched the code base and couldn't find another class that obviously extends Object.
And no, I didn't mean api-index.json. That one is just the overall class index used by the SDK to show the navigation tree for the API reference. I meant files like https://openui5nightly.hana.ondemand.com/test-resources/sap/ui/layout/designtime/api.json.
The following class fetches all api.json files for a given UI5 release (OpenUI5 as well as SAPUI5) and allows a simple lookup:
/*
 * A simple helper class to read all api.json files for a given UI5 release (OpenUI5 or SAPUI5).
 * Provides some basic lookup functions.
 */
class APISummary {

    constructor(server) {
        this._symbols = new Map();
        this._promise =
            fetch(`${server}/resources/sap-ui-version.json`)
            .then((response) => response.json())
            .then(versionInfo => Promise.all(
                versionInfo.libraries.map(lib =>
                    fetch(`${server}/test-resources/${lib.name.replace(/\./g, '/')}/designtime/api.json`)
                    .then((response) => response.json())
                    .then((data) => this._addSymbols(data), () => (null)) // ignore missing api.json files
                )
            ));
    }

    whenLoaded() {
        return this._promise.then(() => this);
    }

    _addSymbols(data) {
        if ( data && Array.isArray(data.symbols) ) {
            data.symbols.forEach(symbol => {
                this._symbols.set(symbol.name, symbol);
            });
        }
    }

    has(name) {
        return name && this._symbols.has(name);
    }

    get(name) {
        return (name && this._symbols.get(name)) || undefined;
    }

    forEach(callback, thisArg) {
        this._symbols.forEach(callback, thisArg);
    }

    symbols() {
        return this._symbols.values();
    }

    findSymbols(predicate) {
        return [...this._symbols.values()].filter(predicate);
    }

}

It can be used like this
new APISummary("https://openui5nightly.hana.ondemand.com")
    .whenLoaded()
    .then((api) => {
        api.forEach((symbol, name) => {
            console.log(`symbol '${name}' of kind '${symbol.kind}'`);
        });
    });

@kuhnchris According to your comment, I guess we can close this issue, too?

Ah yes, sorry, I'll close it, so we are cleaned up here. :-)


Can't click on lower parts of page for screenshot

What Operating System?
Windows 10
What steps will reproduce the issue?
When going to take the screen capture, scroll down and try to take it by clicking on the lower parts of the webpage. This resulted in an error 'can't read property 'id' of null' and the screen capture was not taken.
What would you expect to be the outcome?
The screen capture should be taken no matter where the user clicked on the page.
All these details will help people to fix any potential bugs?
Pretty sure this issue is in overlayscreen.js as the error was coming from line 266

fixed in commit aadd826 - see commit message for more information


Update CredHub CLI to 2.7.0

For whatever reason, it doesn't look like the CF CredHub CI Pipeline has kicked this over.  Submitting PR manually.

Thank you for the PR! We updated the CI config to automatically trigger the homebrew update every time we publish a new credhub cli from now on. And credhub cli 2.7 is now available on homebrew.

Thanks!


Fix missing DVM_OUTPUT

Restore the DVM_OUTPUT variable to avoid running source ""

/me waits for Travis

Once Travis is done building the tag, 0.3.3 will be out for dvm upgrade. Thanks @coreypobrien


typo deatil

is this typo also in the OHDSI CDM spec?
https://github.com/OHDSI/MIMIC/blob/dev_ant_tuf_10_basic/etl/etl/cdm_visit_detail.sql#L225

The typo is not longer in the OHDSI CDM spec, fixed here too.


Cloning existing project using wrangler CLI.

I created worker and I added my code through quick edit from cloudflare dashboard.
I want to clone this existing project to local machine and after some development I want to deploy it back using wrangler CLI. But I couldn't find this cloning feature in wrangler CLI. Any idea what should I do?

Hey @fira-pro, this is a feature of wrangler 2 - you can check it out here: https://github.com/cloudflare/workers-sdk/tree/main/packages/wrangler
wrangler init --from-dash <name-of-worker> should do the trick
Note that wrangler 1 (this repo) is called @cloudflare/wrangler in npm, while wrangler 2 (and all future versions) are just wrangler


Add information about embedded registry

This PR:

Adds information about the embedded registry (mostly copied from k3s)
Includes extra information about private registries (thanks @dereknola )

Let me remove the exerimental/GA message from the airgap.md and leave it in the embeded-registry.md. It should be enough to have it in one place


ConcurrentModificationException in data-set changed events

https://gitter.im/Android-Orma/Lobby?at=593a8eb3e531dbc905c76c1c
Maybe because WeakMap is not thread-safe.

Fixed in 5.0.0-rc4

Great! Thank you!


bump version to 2.1.0-SNAPSHOT

What's the purpose of this PR
bump version to 2.1.0-SNAPSHOT
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Read the Contributing Guide before making this pull request.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit tests to verify the code.
[x] Run mvn clean test to make sure this pull request doesn't break anything.
[ ] Update the CHANGES log.

Codecov Report

Merging #4403 (7893983) into master (5048db6) will decrease coverage by 0.01%.
The diff coverage is n/a.

:exclamation: Current head 7893983 differs from pull request most recent head cfaa850. Consider uploading reports for the commit cfaa850 to get more accurate results

@@             Coverage Diff              @@
##             master    #4403      +/-   ##
============================================
- Coverage     53.17%   53.15%   -0.02%
+ Complexity     2673     2671       -2
============================================
  Files           489      489
  Lines         15277    15277
  Branches       1580     1580
============================================
- Hits           8124     8121       -3
- Misses         6602     6603       +1
- Partials        551      553       +2

Impacted Files
Coverage Δ

...rk/apollo/spring/property/SpringValueRegistry.java
83.78% <0.00%> (-5.41%)
:arrow_down:

.../framework/apollo/spring/property/SpringValue.java
87.71% <0.00%> (-1.76%)
:arrow_down:

Continue to review full report at Codecov.

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


SOCK configs

Adds support for SOCK Space Shuttle Orbiter.
Things I want to do:
Is there a better way to offset the power consumption to be 14 kW?
Should something be done to the radiator?
larger battery? The current battery is the real life size, but the issues with fuel cells turning off makes the time window to fix it very small.

Can be merged with https://github.com/KSP-RO/RealismOverhaul/pull/2432

https://github.com/KSP-RO/RealismOverhaul/pull/2432 has now been merged, so this can be merged too.


Elastic Search support

Hello, has anyone successfully gotten the elastic search container to work for global search on a hosted instance?  I was able to get ES working but I think there is an error in the python calls to ES.

What you need is elasticsearch:1.7-alpine image with ICU plugin installed /usr/share/elasticsearch/bin/plugin -install elasticsearch/elasticsearch-analysis-icu/2.7.0.
Then you should provision and reindex, see recently contributed doc.
Not absolutely sure that's the case with current master in this repository - you may also need to install elasticsearch==1.7.0 with pip.
P.S. Hopefully, I will open a pull with up-to-date RTD, search working, etc in coming weeks. It has been working on my desk for quite some time..

@scottnasello, ES should be working out-of-box with current master (see #4).
Please comment if you experience any issues.
Good luck!


Drop all direct use of the TUF CLI

The TUF CLI has a specific issue preventing us from creating our desired fixtures. Moreover, the intentions behind the CLI are undetermined; the CLI may never become a fully fledged production tool.
So, instead, we should leverage the Python library's high-level repository interface and document the changes. Fixture generation should happen with a committed Python file.

Fixed with the switch to the Python library for fixtures.


Newer versions throw error "TypeError: 'method' object is not iterable" on query_engine.query()

I'm using a custom LLM with code based on
https://github.com/amrrs/LLM-QA-Bot/blob/main/LLM_Q%26A_with_Open_Source_Hugging_Face_Models.ipynb
With older versions of llama_index and langchain  (0.5.27 and  0.0.142) the code works correctly, as in the line
response = index.query( "What's the cost of Whisper model?")  in cell 13
With newer versions of llama_index and langchain (0.6.7 and  0.0.169), and the code changed to use the newer syntax
query_engine = index.as_query_engine(service_context=service_context)
response = query_engine.query( "What's the cost of Whisper model?")
I get the error TypeError: 'method' object is not iterable, on line 145 of RetrieverQueryEngine, which is listed below
response = self._response_synthesizer.synthesize(
query_bundle=query_bundle,
nodes=nodes,)

Could you show more of you code to help us debug?

minimal_example.zip
Here's a minimal example ; the cmd file ( Windows) installs specific versions of llama_index and langchain, and runs the exact same code ( minimal.py) with each pair of versions. The 2 txt files are the output ; the 0.6.7.txt has the full exception stacktrace, while the 0.5.27.txt has the correct answer from the query
The code does have an if statement based on the version of llama_index, since the query syntax is slightly different between the 2 versions, as shown below.
if ( llama_index.version == '0.6.7'):
query_engine = index.as_query_engine(service_context=service_context)
response = query_engine.query( "What benchmarks was the model validated on?")

else:
response = index.query( "What benchmarks was the model validated on?")

I am getting the exact same error.

@logan-markewich  any idea what's going on here? Do you think it's related to using custom LLM?

I got the same problem with
torch       : 1.13.0
langchain   : 0.0.170
transformers: 4.21.3
llama_index : 0.6.7

@Disiok @chaklam-silpasuwanchai @adityakadrekar16 @rajphaniraj
Looks like newer versions of langchain have changed how to declare custom LLMs. Please see this page (notice the property decorator on identifying params):
https://python.langchain.com/en/latest/modules/models/llms/examples/custom_llm.html
I can update the docs with this new syntax as well

@logan-markewich  Thanks, that does work. The langchain documentation does indicate that _identifying_params is optional, but it seems to be needed for this use case.  This is what I had to add to my CustomLLM class to make it work.
from typing import Mapping
@property
def _identifying_params(self) -> Mapping[str, Any]:
    """Get the identifying parameters."""
    return {"n": "nothing important"}

@logan-markewich @rajphaniraj  thanks, it works.
This is how I write my custom LLM....not sure it is correct but it works.  Copy right from Langchain website.
`from typing import Mapping, Optional, Any, List
from langchain.callbacks.manager import CallbackManagerForLLMRun
class CustomLLM(LLM):
n: int
model_name = "google/flan-t5-large"
pipeline = pipeline("text2text-generation", model=model_name, device=1, model_kwargs={"torch_dtype":torch.bfloat16})

@property
def _llm_type(self) -> str:
    return "custom"

def _call(
    self,
    prompt: str,
    stop: Optional[List[str]] = None,
    run_manager: Optional[CallbackManagerForLLMRun] = None,
) -> str:
    if stop is not None:
        raise ValueError("stop kwargs are not permitted.")

    out = self.pipeline(prompt, max_length=9999)[0]["generated_text"]
    return out[:self.n]

@property
def _identifying_params(self) -> Mapping[str, Any]:
    """Get the identifying parameters."""
    return {"n": self.n}`

Version:
torch       : 1.13.0
langchain   : 0.0.171
transformers: 4.21.3
llama_index : 0.6.7

I still have the same error message
TypeError: 'method' object is not iterable
llama_index 0.6.7
torch 1.13.0+cu117
langchain 0.0.171
transformers 4.21.3
`
class customLLM(LLM):
model_name = "google/flan-t5-large"
# Transformer Pipelines
pipeline = pipeline("text2text-generation", model=model_name, device=0, model_kwargs={"torch_dtype":torch.bfloat16})
@property
def _llm_type(self) -> str:
    return "custom"

def _call(
    self,
    prompt: str,
    stop: Optional[List[str]] = None,
    run_manager: Optional[CallbackManagerForLLMRun] = None,
) -> str:
    if stop is not None:
        raise ValueError("stop kwargs are not permitted.")

    out = self.pipeline(prompt, max_length=9999)[0]["generated_text"]
    return out[:self.n]

@property
def _identifying_params(self) -> Mapping[str, Any]:
    """Get the identifying parameters."""
    return {"n": self.n}
def _call(self, prompt, stop=None):
    return self.pipeline(prompt, max_length=9999)[0]["generated_text"]

def _identifying_params(self):
    return {"name_of_model": self.model_name}

def _llm_type(self):
    return "custom"

Imported from llama-index
llm_predictor = LLMPredictor(llm=customLLM())
`

I'm going to close this issue as fixed 👍 the docs have the correct links and examples
https://gpt-index.readthedocs.io/en/latest/how_to/customization/custom_llms.html#example-using-a-custom-llm-model-advanced

Above link is no longer working,Can you give me proper information,Because I'm stuck with the same issue till now.

TypeError                                 Traceback (most recent call last)
in ()
1 query_engine = index.as_query_engine()
----> 2 response = query_engine.query("What this document talk about?")
3 print(response)
/usr/local/lib/python3.10/dist-packages/llama_index/indices/query/base.py in query(self, str_or_query_bundle)
21             if isinstance(str_or_query_bundle, str):
22                 str_or_query_bundle = QueryBundle(str_or_query_bundle)
---> 23             response = self._query(str_or_query_bundle)
24             return response
25
/usr/local/lib/python3.10/dist-packages/llama_index/query_engine/retriever_query_engine.py in _query(self, query_bundle)
173                 )
174
--> 175             response = self._response_synthesizer.synthesize(
176                 query=query_bundle,
177                 nodes=nodes,
/usr/local/lib/python3.10/dist-packages/llama_index/response_synthesizers/base.py in synthesize(self, query, nodes, additional_source_nodes)
123             CBEventType.SYNTHESIZE, payload={EventPayload.QUERY_STR: query.query_str}
124         ) as event:
--> 125             response_str = self.get_response(
126                 query_str=query.query_str,
127                 text_chunks=[
/usr/local/lib/python3.10/dist-packages/llama_index/response_synthesizers/compact_and_refine.py in get_response(self, query_str, text_chunks, **response_kwargs)
32         # the refine template does not account for size of previous answer.
33         new_texts = self._make_compact_text_chunks(query_str, text_chunks)
---> 34         response = super().get_response(
35             query_str=query_str, text_chunks=new_texts, **response_kwargs
36         )
/usr/local/lib/python3.10/dist-packages/llama_index/response_synthesizers/refine.py in get_response(self, query_str, text_chunks, **response_kwargs)
47                 # if this is the first chunk, and text chunk already
48                 # is an answer, then return it
---> 49                 response = self._give_response_single(
50                     query_str,
51                     text_chunk,
/usr/local/lib/python3.10/dist-packages/llama_index/response_synthesizers/refine.py in _give_response_single(self, query_str, text_chunk, **response_kwargs)
78         for cur_text_chunk in text_chunks:
79             if response is None and not self._streaming:
---> 80                 response = self._service_context.llm_predictor.predict(
81                     text_qa_template,
82                     context_str=cur_text_chunk,
/usr/local/lib/python3.10/dist-packages/llama_index/llm_predictor/base.py in predict(self, prompt, **prompt_args)
114             else:
115                 formatted_prompt = prompt.format(llm=self._llm, **prompt_args)
--> 116                 response = self._llm.complete(formatted_prompt)
117                 output = response.text
118
/usr/local/lib/python3.10/dist-packages/llama_index/llms/langchain.py in complete(self, prompt, **kwargs)
44
45     def complete(self, prompt: str, **kwargs: Any) -> CompletionResponse:
---> 46         output_str = self._llm.predict(prompt, **kwargs)
47         return CompletionResponse(text=output_str)
48
/usr/local/lib/python3.10/dist-packages/langchain/llms/base.py in predict(self, text, stop, **kwargs)
824         else:
825             _stop = list(stop)
--> 826         return self(text, stop=_stop, **kwargs)
827
828     def predict_messages(
/usr/local/lib/python3.10/dist-packages/langchain/llms/base.py in call(self, prompt, stop, callbacks, tags, metadata, **kwargs)
784             )
785         return (
--> 786             self.generate(
787                 [prompt],
788                 stop=stop,
/usr/local/lib/python3.10/dist-packages/langchain/llms/base.py in generate(self, prompts, stop, callbacks, tags, metadata, **kwargs)
556             ] * len(prompts)
557
--> 558         params = self.dict()
559         params["stop"] = stop
560         options = {"stop": stop}
/usr/local/lib/python3.10/dist-packages/langchain/llms/base.py in dict(self, **kwargs)
882     def dict(self, **kwargs: Any) -> Dict:
883         """Return a dictionary of the LLM."""
--> 884         starter_dict = dict(self._identifying_params)
885         starter_dict["_type"] = self._llm_type
886         return starter_dict
TypeError: 'method' object is not iterable

@rajivmehtaflex https://gpt-index.readthedocs.io/en/latest/core_modules/model_modules/llms/usage_custom.html#example-using-a-custom-llm-model-advanced


Added support for service IP address

I need the ability to retrieve the IP address of a service instance in Consul, so the first part of the change I need to make to Spring Cloud Consul is to add the required "address" field to org.springframework.cloud.client.ServiceInstance.

Can you tell me why you need it? There's a setting to prefer ipaddress which would end up in host.

I didn't know they're was a setting for this.  What's it the key name?

https://github.com/spring-cloud/spring-cloud-consul/blob/master/spring-cloud-consul-discovery/src/main/java/org/springframework/cloud/consul/discovery/ConsulDiscoveryProperties.java#L88


camel-core - Resumable DSL keep same type in Java DSL as it has no mo…

…re configuration, and changing types can cause problems for Java DSL. Add string parameter variant to make it easy to use.

Ah yeah just updated the docs


Support JSDoc param destructuring

:rocket: Feature Request
Affected Languages

[x] TypeScript or Javascript
[x] Python
[x] Java
[x] .NET (C#, F#, ...)

General Information

JSII Version: 0.18.0
Platform:     all

[ ] I may be able to implement this feature request

[ ] This feature might incur a breaking change

Description
JSII doesn't allow JSDoc-ing destructured parameters. For example:
/**
 * @param bar Example description
 */
public foo({ a, b }: {[key: string]: string}) {
    console.log(a, b);
}

throws the following error:
warning TS9999: JSII: In doc block of 'foo', '@param bar' refers to a nonexistent parameter.

In a real-world use:

/**
 * Generate an Domain Name health check
 *
 * @param scope the parent Construct for this Construct
 * @param id the logical name of this Construct
 * @param props Domain name health check properties
 */
public static domainName(
    scope: Construct,
    id: string,
    { protocol, ...props }: DomainNameHealthCheckProps
) {
    return new EndpointHealthCheck(scope, id, { ...props, ...protocol.options });
}

Proposed Solution
Don't check the parameter name for destructured properties

The restructuring is syntax sugar in TypeScript/Javascript that doesn't quite translate in other languages (such as Java), where we wouldn't know what to attach such documentation to.
I would actually be somewhat more inclined to prohibit usage of the destructuring syntax in exported declarations...

I'm not sure I understand. What would be the difference in translating to other languages my previous example vs. the following?
/**
 * Generate an Domain Name health check
 *
 * @param scope the parent Construct for this Construct
 * @param id the logical name of this Construct
 * @param props Domain name health check properties
 */
public static domainName(
    scope: Construct,
    id: string,
    props: DomainNameHealthCheckProps
) {
    const { protocol, ...otherProps } = props;
    return new EndpointHealthCheck(scope, id, { ...otherProps, ...protocol.options });
}

Let's take the case of your first example:
/**
 * @param bar Example description
 */
public foo({ a, b }: {[key: string]: string}) {
    console.log(a, b);
}

The doc-string mentions something called bar, but there is no declaration named bar.
The example you propose with the de-structuring done inside the method as opposed to in the signature gives me an absolutely unambiguous property name label, which I can translate to other languages as-is... But it's not possible to infer the label in other scenarios.

I'm probably missing something here, but couldn't you use the @param label? They would have to be ordered if there are multiple argument destructred:
/**
 * @param bar Probably the first argument
 * @param qux Definitely the second argument
 * @param baz Probably the third argument
 */
public foo({ a, b }: {[key: string]: string}, qux: string, { c }: {[key: string]: string}) {
    console.log(a, b, qux, c);
}

This is currently how IDEs handle it:

Well that's just not how JSDoc works... The label after @param must correspond to the name of an argument in the function's signature... I don't want to go guessing because it may not always be correct.

JSDoc has a section on "Documenting a destructuring parameter", but it doesn't account for multiple parameters.

If a parameter is destructured without an explicit name, you can give the object an appropriate one and document its properties.

That still makes the interpretation of the documentation non-deterministic. I don't want to depend on ordering of declarations for entities that include a name that should map to other declarations. That seems backwards to me & is a recipe for shipping incorrect documentation.
Also, apparently, TSDoc (which is a variation of JSDoc that is slightly more appropriate, since TypeScript) has this rule: https://github.com/microsoft/tsdoc/issues/186 -- it'd recommend a syntax such as:
**
 * doc for `a`,`b`, and `c` here:
 * @param a - the first parameter
 * @param b - the second parameter
 * @param c - the third parameter
 * @returns the return value
 */
function foo({
  a,
  b,
  c
}:{
  a: string,
  b: number,
  c: string
}): boolean {

}

While this form makes sense to me, that wouldn't be something the can be ported over to other languages easily.

Let's flip the conversation around if you will (because I just feel like we're going in circles here). What problem are we trying to solve here?
Fundamentally, we're just trying to unblock a short-hand syntax for destructuring which is a minor code change away. That pattern is a very natural thing to do in Javascript, but is impossible to model in at least some other target languages.
Purely from an API design standpoint (talking about the API that is compiled by jsii here), I see two main scenarios:

{ a, b } = { [key: string]: string } - this makes for a relatively poor API contract

the signature implies only a and b will be considered, but the declared type of the parameter does not even mention the need for an a and b fields
I also reckon TypeScript will infer the types of a and b to be string, but they'll actually be undefined if not provided through arguments, which can lead to bugs that tsc could have avoided.

{ a, b } = SomeTypeName - this is sugar for when the implementation only cares for a subset of SomeTypeName's features

should there be a parent interface/class to represent only that subset? In other words - is the method's contract too broad?
otherwise, this method is only leaking implementation details through it's signature

Basically, I understand (I think) the papercut here, but I'm not sure the benefits of the de-structured notations are worth the added complexity (and non-determinism) of our documentation parsing.

Completely forgot that TSDoc existed. This syntax is cute, but not really useful for the CDK, since we're already making and documenting interfaces for everything.
And yeah, I agree that relying on parameter order is less than idea, but it seems that it's what TSDoc is doing, without relying on the parameter name. In the TSDoc Playgound:
/**
 * @param second - This should be the second param
 * @param first - This should be the first param
 * @returns 0
 */
function getZero(first, second) {
    return 0;
}

Like you've mentioned, this is a very minor paper cut. The syntactic sugar that parameter destructuring provides is 1 line per parameter. We can close this issue.
On a sidenote:

I also reckon TypeScript will infer the types of a and b to be string, but they'll actually be undefined if not provided through arguments, which can lead to bugs that tsc could have avoided.

That's kind of unfortunate, I would have hoped them to be typed string | undefined.


Add pipeline step to validate changelog

@izgeri I agree with using bash-lib. I think that can be a follow up PR


Add functions unAddressHash

Need this to extract the underlying ByteString to stick it in the explorer database.

bors r+

bors r+


fix default admin user in sitedefault

sitedefaults.yaml was incorrectly formatted for default admin user.
Ref SR: [SAS<PHONE_NUMBER>]
(was)
application:
    identities:
        sas.identities:
            administrator: viya_admin

(corrected)
application:
    sas.identities:
        administrator: viya_admin

Testing is completed. signing off.

@asbisen while you changed the example file, you did not change the file that is actually deployed. They are separate. Please make the same change to /roles/vdm/files/sitedefault.yaml and then this can be merged.

@NormJohnIV thanks for catching that. The change was in place on my deployment dir but forgot to make the change on git repo. Added the change to /roles/vdm/.. as well.


Any chance of supporting 8-bit platforms?

I'm trying to compile k256 for ATmega328, a popular 8-bit chip on arduino boards, but I'm getting:
error: this crate builds on 32-bit and 64-bit platforms only
  --> /.cargo/registry/src/github.com-1ecc6299db9ec823/crypto-bigint-0.4.9/src/limb.rs:31:1
   |
31 | compile_error!("this crate builds on 32-bit and 64-bit platforms only");

The other alternatives to k256, secp256k1 and libsecp256k1 both need alloc, which I have not been able to get working yet on that platform. Any thoughts?

With the forthcoming cpubits crate we may be able to select the 32-bit backend for 8-bit platforms, if that works: https://github.com/RustCrypto/utils/issues/824

sidenote: I tried compiling for 32-bit ARM and it still failed because of getrandom crate:
error[E0463]: can't find crate for `std`
 --> /home/usr/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.2.8/src/error_impls.rs:9:1
  |
9 | extern crate std;
  | ^^^^^^^^^^^^^^^^^ can't find crate
  |
  = note: the `thumbv6m-none-eabi` target may not support the standard library

error[E0463]: can't find crate for `std`
  |
  = note: the `thumbv6m-none-eabi` target may not support the standard library
  = note: `std` is required by `once_cell` because it does not declare `#![no_std]`

error: target is not supported, for more information see: https://docs.rs/getrandom/#unsupported-targets
   --> /home/usr/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.2.8/src/lib.rs:268:9
    |
268 | /         compile_error!("target is not supported, for more information see: \
269 | |                         https://docs.rs/getrandom/#unsupported-targets");
    | |________________________________________________________________________^

error[E0433]: failed to resolve: use of undeclared crate or module `imp`
   --> /home/usr/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.2.8/src/lib.rs:290:5
    |
290 |     imp::getrandom_inner(dest)
    |     ^^^ use of undeclared crate or module `imp`

so with the upcoming cpubits crate, k256 wouldn't still compile for an 8-bit platform like AVR, unless dependencies are changed.

getrandom is only under dev-dependencies. Did you add default-features = false to disable the std feature?
We ensure all of the crates in this repo build on no_std targets that are unsupported by getrandom:
https://github.com/RustCrypto/elliptic-curves/blob/master/.github/workflows/k256.yml#L30

getrandom is only under dev-dependencies. Did you add default-features = false to disable the std feature?
We ensure all of the crates in this repo build on no_std targets that are unsupported by getrandom:
https://github.com/RustCrypto/elliptic-curves/blob/master/.github/workflows/k256.yml#L30

Oops, my bad, it works! I'd deleted default-features = false before while I was trying different combinations for AVR.
Btw, regarding cpubits: I checked and the crate is simply empty for now. What are you blocked on atm? Might be able to hepl.


Bring nested recursion example into noir-lang/noir

### Prerequisites
- [ ] https://github.com/AztecProtocol/dev-rel/pull/207

Details from Tom:

[ ] We'll need to have them pull the dependencies from the workspace rather than being fixed to a particular npm version.

If we're referencing the package.json in the docs then we're going to need to swap out the dependencies for the npm versions when pushing a new release.

[ ] We're going to need to run these as part of CI so we can enforce that the code still works and we can fix as needed.

Following https://github.com/noir-lang/noir/pull/5072, proving and verification workflow would be scoped out of NoirJS.
The PR includes updates to the doc page. Commenting here for @noir-lang/developerrelations and readers' awareness in case it leads to changes to existing / planned works with respect to this Issue.

if not done by the end of the week, moving to blocked

Yeah, issue relayed again to Noir team. Now blocked until workaround/fix found.

@jzaki could you link me to the relevant noir-lang/noir or AztecProtocol/aztec-packages Issue?

Okay, with a little tip form Tom, I did get it to pass, but by doing something that seems wrong and different to between what nargo returns and bb expects between binary vs js. I'll check with Tom this morning and create an issue for the lack of intuition on the .js side to document, or an issue for the .js side to be aligned with the binarys' way.

Added two benchmark circuits from Savio, 2^17 succeeds, 2^18 fails. The recursion test is skipped.
PR here
Once 2^18 works again, the skipped recursion tests should readily be made to pass again, so can unskip it and remove the benchmark tests.

Thanks @jzaki. If you have time it might be good to file an Issue for it in https://github.com/AztecProtocol/aztec-packages.


sidebar can not shrink

sidebar can not shrink

the branch you pulled is feature/1.2.0 ?

same issue

If you switch from branch other to master, required reinstall dependencies

If you switch from branch other to master, required reinstall dependencies

i remove the whole project

I tested without the bug you described, do you have a demo?

I tested without the bug you described, do you have a demo?

i run it on my own pc, no web link

お兄さんが大好きです
I can't help for you. sorry

@peter527 GlobalHeader.vue , change click.native to click, it can work, I test it

ok, i will check it

@peter527 GlobalHeader.vue , change click.native to click, it can work, I test it

it works, thanks

the root cause may be the version of ant-design-vue

recommend ant-design-vue 1.1.10 , Not yet supported ^1.2.0

recommend ant-design-vue 1.1.10 , Not yet supported ^1.2.0
And package management YARN is recommend ( yarn.lock file).

OK, thanks


2.17.2: untranslatable strings

After updating to 2.17.2 version, strings All fields, All tags and All relations are in English and it's not possible to translate them.
The same with Maxar layer tooltip.

Oh dear, this is because Transifex is pulling the strings from the latest 2.x branch but 2.17.2 is based on an earlier version with slightly different strings. This will get addressed in the next feature update but I'm not sure if we need to fix it sooner.


Fix issue 12987 - topN should return the top portion of the range

Could somebody please have a look over this and see whether the tests need to be more robust?  I'm not sure how all ranges would interact with these changes.

Yah, that's right. Thanks!

There are problems with my changes in this PR, and I have updated my branch with some fixes.  To get them, do we need to revert this PR and then do I need to open a new PR?  Or is there an easier way?
@JackStouffer: please scrutinise.  :)

You should open a new PR. Reverting this would take an extra PR anyway, so it might as well just be fixed.


[TASK] Specify max charge/discharge rate and loss rate of storage component from HERON XML file

Issue Description
Is your feature request related to a problem? Please describe.
There seems to be no simple way to modify the charge/discharge behavior of a component which . Without implementing a custom dispatcher, the charge and discharge rate of the storing component seems to only be limited by the other consumers and producers interacting with the stored resource (e.g. turbine capacity limiting storage discharge rate). I would also like to be able to set a loss rate for storage components.
Describe the solution you'd like
I would like to be able to set the min/max charge/discharge rates from the HERON input XML. A subnode for  where these bounds could be set would make sense to me, with minimum and maximum rates using the existing  and  tags. Heat loss rate could similarly be specified with a <loss_rate> subnode. It would be helpful to be able to use both fixed values and functions (or DataGenerators, generally) to specify these values.
Describe alternatives you've considered
Provide a sample custom dispatcher which implements these features.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[ ] 1. Is it tagged with a type: defect or task?
[ ] 2. Is it tagged with a priority: critical, normal or minor?
[ ] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[ ] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[ ] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[ ] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

Note heat loss is probably covered by the <RTE> (round trip efficiency) node. Providing more complex functions for this node (than simple scalars) may introduce remarkable complexity to the optimization constraints, but should be approachable if needed.

Note heat loss is probably covered by the <RTE> (round trip efficiency) node. Providing more complex functions for this node (than simple scalars) may introduce remarkable complexity to the optimization constraints, but should be approachable if needed.

Related to #88 which includes ramp rates generally

Yeah, extending RTE to be time-dependent would be state-of-the-art work. It moves the analysis from the regime of level/charging to further include integrated level of storage as a function of time. If solving 8760 continuous histories, this would be pretty straightforward to march through, and probably would yield manageable pyomo expressions. If solving clustered typical days, however, I think this time integration would become almost impossible to track effectively. I'm certainly interested in hearing how it could be approached!

Good points. Probably not worth the expense to model heat loss in that sort of detail. As long as the storage is cycled periodically, RTE is probably a good enough approximation.
Regarding ramp rates, do you think you all might take a look at that in the near future? If not, I'll look at it myself if/when it becomes immediately useful to us here.

As of this moment, I don't have any uses cases requiring ramp rates, so it's on the back burner. It might be good to check back in when it becomes apparent you'll need them, and we can see if our priority stack has shifted.


Removing the leading zeros when I use ExcelReader to read it as Dataset from an excel file

    String ParentXML = String.Empty;
    GenericXMLHelper obj = new GenericXMLHelper();
    ParentXML = ParentXML.Replace(" xmlns=\"http://tempuri.org/\"", String.Empty);

    if (fileUpload.HasFile)
    {
        FileStream stream = File.Open(filePath, FileMode.Open, FileAccess.Read);
        IExcelDataReader excelReader;
        Boolean isXLSX = IsXLSX(fileUpload.FileName);
        String connectionString = String.Empty;
        if (isXLSX)
        {
            excelReader = ExcelReaderFactory.CreateOpenXmlReader(stream);
        }
        else
        {
            excelReader = ExcelReaderFactory.CreateBinaryReader(stream);
        }

        DataSet dataSet = new DataSet();
        excelReader.IsFirstRowAsColumnNames = true;

        DataTable dt = new DataTable();

       **dataSet = excelReader.AsDataSet(true);**
        excelReader.Close();

I was trying to create a dataset reading from excel by using excelreader, even though I have leading zero values in excel file. It is stripping out the leading zeros and giving me the output. How to resolve this issue (like the actual value in the excel is "0940" the output after reading by using excel reader is "940". Any help is greatly appreciated.

The column format in excel is general format since the clients enter the data and try to upload it so we need to read the data from client excel sheet, still we have leading zeros in General format.

Hi, I believe this is a known problem with earlier versions of ExcelDataReader, but has been fixed since v3.0.

Thank you Andersnm for replying but any example code please that might help me.

No worries I fixed it. Thank you


flexible pricing: remove up/down arrows from income input field

As a learner applying for financial assistance, I don't want to adjust my income in $1 increments.
Designs and Mockups

Acceptance Criteria:

[ ] remove the up and down arrows

@pdpinch Simply removing the up/down arrow is just a visual thing.

I am still able to press my keyboard up and down to increment it by $1. Is that ok?
Currently, it's set step="any" which I believe defaults to step = 1. What incremental should we set here besides removing the arrow? or do you think removing the arrow is enough?


Feature Request: Sparklines tooltip sync

When using the Sparklines (or others graphic in a dasboard for example), it would be nice to be able to display the tooltip at the same on other graphs sharing the same X Axis.
It's the case in the sample Sales / Expenses / Profits, where on hover, it's good to see the Profits, but it's hard to see if it's based on increase of Sales or Expenses:

I understand a combined graph could resolved it, but it will not be as beautiful as 3 sparklines.
Perhaps adding an event for tooltip, and the ability to display the tooltip on another chart (like the sync charts method with updateOptions?).
Thanks for the library very helpful.

Good suggestion.
I am thinking of making easier to sync similar charts by providing chart-ID in options.sync and that way user can input chartID in that array to sync charts which share a lot of things (xaxis in your case).

Would be amazing! If you need help, let me know would be interested to contribute.

Here is a sneak peak of the grouped charts where zooming/panning as well tooltip will sync for charts having the same group.

Will provide demo/samples once I release a new build

Great news! It will be really useful. Thanks.


signinRedirect with extraQueryParams

I hoped that this sort of thing might be possible
      .signinRedirect({
        extraQueryParams: { Foo: 'Bar' }
      })

But TypeScript says no.

Error	TS2345	(TS) Argument of type '{ extraQueryParams: { Foo: string; }; }' is not assignable to parameter of type 'SigninRedirectArgs'.

Is there a way to make it work with TypeScript?

For what it's worth, that compiles fine for me in both an older 2.2 and the newer 3.0, and the parameters make their way to the idp authorize call.

works here in my application and in the unit-test https://github.com/authts/oidc-client-ts/blob/faf3a8e5614c664004e90813d601b6ec8a3c335e/src/SigninRequest.test.ts#L218


Create docker container

Would be another nice way to implement and might also help with some environmental issues.

Getting access to I2C and GPIO in Docker is potentially tricky.
https://stackoverflow.com/questions/62719486/accessing-the-i²c-bus-with-node-red-in-docker-on-a-raspberrypi-4
https://stackoverflow.com/questions/64926963/is-it-possible-to-use-rpi-gpio-library-in-docker


Improve attribute with enum aut-completion

Closes #236
When autocompleting attributes that define a set of valid values, the autocompletion snippet will directly offer a choice dropdown with those values instead of having to manually press ctrl+space to trigger the value completion.

Merci!


[path_provider] Update win32 to 5.x

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Use case
Because path_provider_windows >=2.1.6 depends on win32 >=2.1.0 <5.0.0 and app depends on win32 ^5.0.2, path_provider_windows >=2.1.6 is forbidden.
Proposal
Bump dependency win32 to 5.x in  path_provider_windows

Hi @temzints
Try adding win32: lower version then 5.0.0
instead of win32: ^5.0.2

For the APIs used by path_provider_windows, v5 should be compatible with v4. So a pull request similar to this one should be ideal: https://github.com/flutter/packages/pull/3820/files
(For those paying attention, I don't expect we'll need to update the major version for win32 for a while now. The changes in v5 move the unstable WinRT APIs into a separate package, leaving win32 to focus on APIs that won't change.)

for current you can fix it by
dependency_overrides:
  win32: ^2.0.0