Project/density maps/jeffcarlin

Hi Nushkia - since you expressed interest in reviewing my Stack Club project a few weeks ago, I have invited you to review. Let me know if you are unable to review this notebook, or if you have any questions about it.
Alex - your comments are welcome as well, but if you want to weigh in after Nushkia, I can ping you then.

Thanks Jeff. I'll weigh in after Nushkia (if she is available).

I see this cell
! cd ~/stackclub/StackClub/ && python setup.py -q develop --user && cd -

I don't think you can use an absolute path like that, since not everyone has the Stack Club notebooks installed in the same place.
In the FindingDocs notebook (under GettingStarted), Phil does something like this:
! cd .. && python setup.py -q develop --user && cd -

Good point - I updated it to the relative path.

I see this call to see if a data set exists. Does this actually "guarantee" that the data set is on disk?
butler.datasetExists('deepCoadd_forced_src', dataId=dataref14)

I thought there may have been some subtleties here that involved getting the URI

I added the following to the notebook to clarify:
"Note, however, that in the Gen2 butler, this doesn't guarantee that the catalog actually exists as a file on disk. It only tells us that some processing steps were executed that intended to create the catalog, and thus added its entry to the registry. This issue will be remedied in the Gen3 butler, so it is not important to dwell on it further."

What does immediate=True mean here? I hadn't seen that before. Is it worth noting?
image14 = butler.get('deepCoadd_calexp', immediate=True, dataId=dataref14)

Indeed, that was a holdover to ancient times, but unnecessary now. See this community post

@jeffcarlin want to merge? This notebook is a nice holiday present!


ModuleNotFoundError: No module named 'faiss.swigfaiss_avx2'

hitting this error, created new miniconda environment with python 3.11 on m2 mac, looked online at how to fix swigfaiss_avx2 but didnt find good solution. any tips appreciated
(langchain) 2023/chat-your-data[master|✔] % python app.py
Traceback (most recent call last):
File "/Users/vidalgraupera/code/2023/chat-your-data/app.py", line 7, in
vectorstore = pickle.load(f)
^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'faiss.swigfaiss_avx2'

running into same issue on mac m1. seems to be a bunch of issues with faiss and the new mac m1 and m2 models.
found a workaround with making Faiss compatible outside the conda environment.
https://github.com/facebookresearch/faiss/issues/1773#issuecomment-1237908374

running into same issue on windows seriver 2019, created new conda environment with python 3.10:
(LangChain) D:\Code\LangChain\chat-your-data>python app.py
Traceback (most recent call last):
File "D:\Code\LangChain\chat-your-data\app.py", line 10, in
vectorstore = pickle.load(f)
ModuleNotFoundError: No module named 'faiss.swigfaiss_avx2'

this error occurs when you use a pickle file generated on a different CPU architecture which supports avx2. Try to generate your own pickle file

Hi siddhantdante I ran into the same error, how can I generate my own pickle file, given I am in a windows OS? , and based on what should i generate it?

Had the same problem on a mini M2.  Fixed in by running "python ingest_data.py" to create a new pickle file.
This step is covered in the blog post https://blog.langchain.dev/tutorial-chatgpt-over-your-data/ which I failed to read carefully enough.

Had the same issue on Win11 home ed. 22h2. Followed what @fowlert did to fix it.


Performance Guide

Docs need a Performance Guide chapter. Topics:

io_context models (single thread, multi-thread, multi-context)
dynamic buffer choices
flat_stream and ssl_stream

We aren't doing this anymore


ARROW-13294: [C#] Create Flight example server and client

Summary

Created an example Flight server that just stores Arrow tables in memory. The server code is based on the dotnet template provided by dotnet new grpc.
Created an example Flight client that goes through each Flight method.

I wrote these examples to learn about the Flight protocol.

Just a thought - but recently some of the other subprojects have been adding examples to a cookbook, would it make sense to start one for C♯? There's a similar example for Flight/Python there.

Just a thought - but recently some of the other subprojects have been adding examples to a cookbook, would it make sense to start one for C♯? There's a similar example for Flight/Python there.

Oh that's a good idea. I was just putting here since that's there the current existing example is. But if there are other Flight servers going there, I think the cookbook makes more sense.

Just a thought - but recently some of the other subprojects have been adding examples to a cookbook, would it make sense to start one for C♯? There's a similar example for Flight/Python there.

Oh that's a good idea. I was just putting here since that's there the current existing example is. But if there are other Flight servers going there, I think the cookbook makes more sense.

@lidavidm Looking further at the cookbook, I think there's a lot of work needed to get C# started there. We don't even have the API docs up for C# yet.
I mostly worked on this to learn about the Flight protocol and because I had previous experience writing services in C#; I don't plan on focusing on C# long term.
I'll keep this as a PR to add these examples to the main GitHub. But if we get more contributors to C# I hope we can move these examples to the cookbook.

@eerhardt @HashidaTKS Interested in reviewing?

Looking good. Some more detailed comments. I think this will be ready for merge when they are addressed.

Thank you for the detailed feedback! I have addressed each of your comments.


Component name: <pfe-icon>
Design specification updates
PatternFly v4 Icon
I'd like to change the public apis here somewhat, removing the iconset prefix from icon names and instead adding an optional set attribute, which falls back to the default icon set.
<blink>OLD:</blink>
<pfe-icon icon="fa-alert"></pfe-icon>
<pfe-icon icon="fas-warning"></pfe-icon>

<marquee>NEW:</marquee>
<pfe-icon icon="alert"></pfe-icon>
<pfe-icon icon="warning" set="fas"></pfe-icon>

Under the hood, I'd like to maintain the lazy-loaded icons approach from v1, but instead of pointing icon sets to a URL template and fetching in the SVG contents to display, I'd like to ship the default icon sets as lit TemplateResult objects in conventionally named modules, in the pfe-icon package. These modules would be gitignored and generated at build time, similar to how PF-react does it. At runtime, those modules would be dynamically import()ed. Like v1, we would provide imperative escape hatches to register icon sets as import specifier templates, which would be relative, absolute, or fully qualified URLs.
cc @mwcz @kylebuch8

pfe-icon will default to fontawesome, but will ship with redhat brand icons.
cc @markcaron


clipgrab

Describe the bug
cant install clipgrab
not found
manually installed using choco
using pwsh as default in winterm if that makes a difference
i thought maybe was trying to use winget.
rg says using choco...
thanks for all  the work. notice alot of change =)

Yes winutil right now doesn't use choco to install apps, we wanted to have choco as afall back in case winget doesn't have a package but that code was never implemented since there is no need for it. @ChrisTitusTech  Whoever added this package never even tested it. I'm not sure how it slipped through the cracks, we should definitely remove it from winutil.
@ChrisTitusTech I think we need to create a more rigurouse process of accepting apps into winutil. After all it is not an app store and people keep adding so much stuff and half of it doesn't work. :-) I was looking at ways to implement some basic telemetry for app usage but not sure were we could host an endpoint for telemetry. That way you could age out apps that are not used by people.


SAA-121 stubbed endpoint for retrieval of activity locations.

Codecov Report
Base: 70.78% // Head: 69.49% // Decreases project coverage by -1.28% :warning:

Coverage data is based on head (55b0735) compared to base (1f8f592).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##               main      #45      +/-   ##
============================================
- Coverage     70.78%   69.49%   -1.29%
  Complexity      190      190
============================================
  Files            47       48       +1
  Lines           705      718      +13
  Branches         10       10
============================================
  Hits            499      499
- Misses          202      215      +13
  Partials          4        4

Impacted Files
Coverage Δ

...pps/hmppsactivitiesmanagementapi/model/Location.kt
0.00% <0.00%> (ø)

...nagementapi/resource/ActivityScheduleController.kt
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


fix: bug with invalid config file path

What/Why/How?
Fix bug if invalid path provided to the configuration file. Also this bug cause issues with correct location of .redocly.lint-ignore.yaml for ignore potential problems.
Reference
Testing
Screenshots (optional)
Check yourself

[x] Code is linted
[ ] Tested with redoc/reference-docs/workflows
[x] All new/updated code is covered with tests

Security

[x] Security impact of change has been considered
[x] Code follows company security practices and guidelines

Left a few small comments.


Accept all peer requests that did not originate from device

myPeerID.hashValue not guaranteed to be greater than peerID.hashValue. Accept all requests that don't originate from current device.

I think the initial logic here was to have a deterministic way to have only one of the two peers accept the connection.


net: lwm2m: Allow string and opaque data types to be empty

When string and opaque types are uninitialized, we should
allow their data length to be zero. However, most content
formatters seem to calculate the string length separately
so replace the pointer of empty data into a static string
that is guaranteed to be empty.

Need someone else to approve.

@tbursztyka @pfalcon can you help to approve this? I believe you are codeowners of net/lib/* as well.


Build plugins from source for ansible deployments

With this PR, we will no longer build our plugins just to check the jars into the repo for ansible.
Artifacts will be collected by the :ansible:build gradle task prior to deployment. Vendored jars are moved to src/paper-plugins

This should be good, but I didn't want to hijack the test server from 1.20 to test it too hard. We can merge it, merge it up to 1.20, and then test it and make any fixes as needed.


[hf parser] Pass in model name to text generator

[hf parser] Pass in model name to text generator
I forgot to do this before, which would default to None model (I forget which model they used). This explains why the mistral detokenizer wasn't working properly even though ChaptGPT was.
For now just storing these different generators in memory through a dict where the key is model name. No matter what model, they all follow the same text generation API so it's ok

Stack created with Sapling. Best reviewed with ReviewStack.

#411
-> #410

gpt2
mistral

https://drive.google.com/file/d/1AhJ6mtVtpzyT2GTMPd2rHWqvOrRU9z6q/view?usp=sharing
https://drive.google.com/file/d/1kA84Qrx5idPi2ypuSeNDK7B76xpeNeY8/view?usp=sharing


Add support for kVTCompressionPropertyKey_DataRateLimits

It be great to be able to set kVTCompressionPropertyKey_DataRateLimits as the average bitrate is often overrun and being able to set more firm limits on it would be beneficial.

@triwav  Hi. framework supported it.
Try here. kVTCompressionPropertyKey_DataRateLimits seems to adjust a FPS.
let bitrate:UInt32 = 160 * 1024 // bitPerSecond
let dataRateLimits:[Int] = [160 * 1024 / 8, 1] // [byte, second]
rtmpStream.videoSettings = [
    "bitrate": bitrate,
    "dataRateLimits": dataRateLimits,
]

Have you tested out this commit? Looking at this line: https://github.com/shogo4405/lf.swift/commit/277852cb2cfc52cb105b34c6130a4ba68da461c8#diff-eab61c0f1ecc489ad80ca77abb811cd6R81
You are checking the oldValue as well and returning if it was nil. This means the first time you set this property to something besides nil it should be ignored. I haven't actually tested this but I'm pretty sure that's what it will do.

oh... You're right. I fixed it.

released 0.3.4


[FINE] Add fast refresh options

This PR is a Fine-specific backport of ManageIQ/manageiq-providers-openstack#57. Due to the OpenstackHandle gem being split out into manageiq-gems-pending after Euwe's release, a separate PR is available for Euwe. (https://github.com/ManageIQ/manageiq/pull/15538)

If ems_openstack.refresh.is_admin is set, then ManageIQ will attempt to use
admin-only api options to signficantly reduce the number of repeated API
calls necessary to build the Openstack inventory.
Due to differences in the way Heat's access control system works,
there is a separate flag to enable admin mode. This requires Heat to
be configured in a particular way.
See https://bugs.launchpad.net/heat/+bug/1466694 and
https://bugs.launchpad.net/keystone/+bug/968696 for more details
on why this is the case.
Add VCRs for fast refresh

Yeah, this one won't succeed until manageiq-gems-pending gets the associated patch merged to the fine branch.

Depends on https://github.com/ManageIQ/manageiq-gems-pending/pull/224

@tzumainn Re-ran Travis after merging https://github.com/ManageIQ/manageiq-gems-pending/pull/224 and it's now passing. Please let me know if this is good to go.

Ah, yep, this is good!

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1469702


GET API to retrieve Grafana and Alert manager URLs

What this PR does / why we need it:
This PR adds a GET API, which lets the Dashboard retrieve the redirect-to URLs for Grafana and AlertManager components and render the redirect functionality using these URLs
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
NA
Special notes for your reviewer:
GET
http://localhost:50040/v1beta/e93b4c0934da416eb9c8d120c5d04d96/metrics/urls

Response
{
    "alertmgr-url": "https://alertmgr",
    "grafana-url": "https://grafana-url"
}

Release note:

These values will be added to the opensds.conf file after installation. Have mailed the details to Pengyi to implement the same.

@skdwriting @wisererik @xing-yang @leonwanghui @NajmudheenCT @anvithks Please review

Coverage decreased (-0.1%) to 28.583% when pulling f30da857d7b5b0cadf0940d52de2bc98191908a9 on rhsakarpos:urls into 1e7944d17ab1eb8cf72305a5675c7cdd3a436d0e on opensds:development.


Facilitating design validation workshops

Description:
Let's test and validate our designs!
These sessions will be focused on internal users/staff to get feedback on initial designs. This will help us validate if we are on the right track and make any iterative changes before we start building out the frontend in more depth.
Acceptance Criteria:
[Note: Use 'Given/When/Then' format if it makes sense to. Otherwise, a simple checklist that can be tested.]
Development Checklist:

[ ] ...
[ ] ...
[ ] ...

Dependencies

Blocked by
Blocking

Relevant documentation as reference
Definition of Ready

[ ] Acceptance criteria are included
[ ] Wireframes are included (if applicable)
[ ] Design / Solution is accepted by Product Owner (if applicable)
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

Definition of Done

In progress:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] UI meets accessibility requirements
[ ] Unit tests are written
[ ] Work is traceable in GitHub
[ ] PR linked to ticket number
[ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment

Code review:

[ ] Code is peer reviewed and has passed CI/CD tests

QA:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Code is potentially shippable to the production environment
[ ] Functional features have been tested and passed by QA
[ ] UI components tested by designer
[ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)

PO Review:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Reviewed and approved by Product Owner

Notes:

Hi @pavelcreates - can you please take a look at this ticket and refine if needed before Thursday's sprint planning. Thanks!

Looks good to go! I made some edits to the ticket name, status and acceptance criteria as this is currently in progress.

It's been so informative sitting in on these sessions @pavelcreates - looking forward to seeing the analysis and next steps from that.


New Custom Field are not detected

Do i need to restart the browser for changes to take effect?
I've added a couple of custom field but are not working.
The "match" matches exactly the input field "name".

Are you still having this problem?

Sorry, not using the extension anymore, I've finished the project i was using it for.


[bug] [themes]: Dracula Theme Color Scheme not respected

TL;DR
The current built-in Dracula theme doesn't respect the official Dracula scheme, uses different colors and is missing light-versions of colors (reusing "non-light" versions), presenting contrast issues.
What I've experienced
I have just installed Ghostty and I chose to use the Dracula color scheme, as I did with Kitty.
Just after the first seconds I tried using zsh-autosuggestions but saw the autocompletion color in Ghostty was different than the one in Kitty (and the one in Ghostty had really low contrast with the background).
Kitty (left) vs Ghostty (right):

After investigating a bit, I discovered that the colors used by Kitty's Dracula theme are (mostly) different in Ghostty. For example, the autocompletion color used is the "8th color", which is #6272a4 for Kitty, while #555555 for Ghostty.
Anyway, I'm certain the "wrong" color scheme is Ghostty's because Kitty uses the color scheme from the official Dracula (org) repo, while Ghostty seems to use iTerm 2 "unofficial" theme.
Here are the (comparable) schemes used by Kitty and Ghostty, respectively (from the links above):

Light versions of colors are completely reused from non-light ones, some colors are different from the ones used by Kitty (ex. background)

 Kitty   Ghostty

foreground            #f8f8f2
background            #282a36
selection_foreground  #ffffff
selection_background  #44475a

# black
color0  #21222c
color8  #6272a4

# red
color1  #ff5555
color9  #ff6e6e

# green
color2  #50fa7b
color10 #69ff94

# yellow
color3  #f1fa8c
color11 #ffffa5

# blue
color4  #bd93f9
color12 #d6acff

# magenta
color5  #ff79c6
color13 #ff92df

# cyan
color6  #8be9fd
color14 #a4ffff

# white
color7  #f8f8f2
color15 #ffffff

# Cursor colors
cursor            #f8f8f2
cursor_text_color background

foreground = #f8f8f2
background = #1e1f29
selection-foreground = #ffffff
selection-background = #44475a

# black
palette = 0=#000000
palette = 8=#555555

# red
palette = 1=#ff5555
palette = 9=#ff5555

# green
palette = 2=#50fa7b
palette = 10=#50fa7b

# yellow
palette = 3=#f1fa8c
palette = 11=#f1fa8c

# blue
palette = 4=#bd93f9
palette = 12=#bd93f9

# magenta
palette = 5=#ff79c6
palette = 13=#ff79c6

# cyan
palette = 6=#8be9fd
palette = 14=#8be9fd

# white
palette = 7=#bbbbbb
palette = 15=#ffffff

cursor-color = #bbbbbb

Haven't looked at other themes but I hope they respect the original theme scheme... in my case the only flaw of migrating from Kitty to Ghostty was just the theme.
Throughts
From what I've experienced, I really liked the way Ghostty let you choose a theme, but what I really feel missing is support of official themes (ex. Dracula, Cappuccin), that should be in the "Ghostty org" or in the "theme org", not a "third-party org".

Upstream: https://iterm2colorschemes.com

Just posted about this here - https://github.com/mbadolato/iTerm2-Color-Schemes/issues/487

@Bellisario @mitchellh This has now been resolved upstream, if you want to run that workflow manually

Thanks, I'll do so before the next release, otherwise the weekly job will get it.


Some timeline events are missing

Some timeline events are missing. For example, I was looking for head_ref_force_pushed and I do not see it in https://github.com/yanyongyu/githubkit/blob/master/githubkit/versions/v2022_11_28/rest/issues.py#L2871-L2895
It looks like other events may be missing as well.

This event is a StateChangeIssueEvent. githubkit generates the models from the github's openapi schema. It's impossible to miss an event type unless github miss the event. In fact, many timeline events on GitHub use this type and has no extra detailed info.

Ah... I was expecting something more typed, like there is in the GraphQL API. Thank you for clarifying this!


Design new create ballot

Is your feature request related to a problem? Please describe.
The creating ballot form is hard to use and not intuitive at all. Also, its tiny and everything is crowded.
Describe the solution you'd like
Design that uses the whole screen and helps the user to focus on creating their ballot.
Acceptance criteria

The design should assume the user doesn't have previous knowledge of how polls work
The design must work for mobile, tablet and desktop
Design focused on polls ❓
Reflect current naming (e.g. DAO instead of treasury)
Indicate to the user how each voting type works
Indicate to the user how each DAO works
Max and min options with explanation
If the user is not in any DAO, display Join a DAO & create poll instead of Create Poll. This should have an explanation of why joining a DAO is required.
Add explanation for stake/liquid choices in ballot configuration when treasury allows a choice.
Use another component to create options that look more friendly.

This issue is already aborded in #79, maybe we can rename the issue and continue with it

@poplexity should we only focus on polls for this form? We're not entirely sure.

I will suggest splitting the Ballot creation form into several steps using this wonderful component "Stepper"
https://quasar.dev/vue-components/stepper
1 - Ballot main info

Title
Description
Image URL (with preview)
file.pdf

2 - DAO selection

(x) Telos community    ( ) Custom DAO
"information about the selected option"
If Custom DAO is selected then show

list of current registered DAOs for user
Button "Join new DAO" to redirect the user to DAOs section
Vote with: ( ) Liquid tokens    ( ) Staked token    (x) Both

3 - Voting options

(x) Simple Yes or No    ( ) Yes/No/Abstain    ( ) Multiple option
"information about the selected option"
if any of the first two are selected, then show two or three fields to edit the default words
if the Multiple Options is selected, then show an editable item list like a simple TODO-list app:

intput for the displayable text of the new option
"add" button
list of already created items with a cross button to delete it from the list
button: "clear list"
checkbox: [x] "Voters can only choose one option"
if the user unchecks it, then we show:

"information about 'min' n 'max' fields"
input "Min"
input "max"

4 - Open Voting

checkbox: [x] "Open voting right away"
if user keep option checked then show

input: "Ending date"

5 - Finish

show preview with the info
alert about the cost in TLOS
Button "Confirm"

There's a video for the current approach:
https://github.com/telosnetwork/app-telos-native/pull/188


EMR Initial Capability Defect/Desire List

After using this for a day or two I see a couple of issues and figured I'd start a ticket to capture any other defects/desires found after using this first attempt for a bit.

Investigate the use of EBS backed instances. Are we limited to instance types that use instance store disks?
In our internal use of this feature we wrap the call to the API in a Jenkins job. Expose more options like instance type to the user when running the job to provision the cluster
For a general purpose cluster to explore new functionality what we have is fine but for the case of standing up a cluster to conduct benchmarks more investigation needs to be done on the intialization of disks, this first attempt of mine is broken.

It looks like EBS no longer needs the old "pre-warming" step but we don't know if we can use EBS backed instances yet.
I thought the faster "read-once" method of restoring a snapshot image using the fio tool could be used for instance store volumes but the docs say, "first write to any location on an instance store volume performs more slowly than subsequent writes" and they recommend using the "dd" tool which, "Initialization can take a long time (about 8 hours for an extra large instance)"
The way the bootstrap script is currently written there is no way for the $INIT_VOLUMES flag to get set to true so it's never going to to run the initialize_volumes step.

Instance store disk init: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/disk-performance.html
EBS Volume Snapshot init: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-initialize.html

We currently use on the master and core (worker) node types and master is used to run GeoServer. The GeoServer process and other non-hadoop related tasks should be able to be run from a "task" node which is the third type of node available in the EMR framework. This would require a bit of refactoring of the existing boot scripts.

An option to have worker nodes provisioned via spot instances for large "best effort" workloads

automate the process of utilizing additional EBS volume as additional storage (perhaps one of the "task" node types may need to stage large amounts of data for ingest)

make sure Accumulo 1.7.0 is supported


Add long description to PYPI

See: https://pypi.org/project/asynctest/0.11.0/
@Martiusweb if you're okay with sticking to setuptools>=30.3.0, I'd send a PR using nice feature of automatic reading of README into long_description using declarative setup.cfg.

Hi, would it block someone using an older version of setuptools installing asynctest?
If not, I'll welcome the PR 👍

@Martiusweb it depends: older version will just omit reading/parsing setup.cfg.
We could add __requires__ = ('setuptools>=30.3.0', ) and then it will raise an exception asking user to install required version. But otherwise, it shouldn't affect users, unless we drop stuff from setup.py.
Oh.. and we'll need to upgrade setuptools in CI as well, before building dist, but that's easy.
Honestly, newer versions of setuptools bring features and improvements, so I feel good when promoting upgrades :)
For example, a while ago (>=36.3) I've added ability to concatenate more than one file in setup.cfg (if one needs to include their contents to long description), which will not be available to users unless they upgrade. This helps eliminate coding in setup.py (now lots of people just do lots of magic there, which is unfortunate)
So, it's declarative setup.cfg
[metadata]
long_description = file: README.rst

v.s.
coding the setup.py
from setuptools import setup
...
with open('README.rst') as readme:
    LONG_DESC = readme.read()

__name__ == '__main__' and setup(
    ...,
    long_description=LONG_DESC,
    ...,
)

Fwiw, I usually check what is provided by the latest LTS of ubuntu. The version of setuptools that it distributes is 20.7.
Since this feature is only useful when doing a release on pypi, I think we should not force users to update their dependencies if they want to install asynctest.
Let's force the version in the CI and rely on features of setuptools that users can safely ignore if they run with an older version.

Ref #54

I rebased your commits and updated the setup.py script:
https://github.com/Martiusweb/asynctest/commit/341d24c51c000f5103b6a6a45dbea01291940663
What do you think of it?

You could push in my repo instead of pushing additional branch here: this would go to the PR page and would be easier to comment on :)

I've added a few comments there

I merged you changes with mine.
Thanks :)


Do not require DenySettingsMode parameter for MG scoped deployment stacks with MG scoped underlying deployments

Is your feature request related to a problem? Please describe.
DenySettingsMode is required in MG scoped deployment stack New and Set cmdlets when underlying deployment is at MG scope, even though deny settings are not supported on MG scoped deployment stacks with MG scoped underlying deployments. The cmdlets require you to specify 'None' for the DenySettingsMode.
Describe the solution you'd like
Will discuss possible solutions if issue is upvoted enough.
Describe alternatives you've considered
N/A
Additional context
N/A

one possible way is to have Parameter sets in PS where DenySettings for MG scope is not required and it has one default value which is the only one available. Of course if the issue will be solved at later point why make the effort to do change now and later having to revert it.


Fix high cpu consumption

Added .gitignore file;
Added a sleep in Inotify::getNextEvent;

Codecov Report

Merging #22 into master will increase coverage by 0.05%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
+ Coverage    81.9%   81.96%   +0.05%
==========================================
  Files           8        8
  Lines         315      316       +1
==========================================
+ Hits          258      259       +1
  Misses         57       57

Impacted Files
Coverage Δ

source/Inotify.cpp
69.84% <50%> (+0.24%)
:arrow_up:

Continue to review full report at Codecov.

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

@spelcaster thank you for your pull request. Looks very nice. I think we should make the timeout adjustable in a future pull request.


fix(monkey-patch): enforce styles for 5.1 release

Related to #3025

https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/stylePatchBuild51/camunda-modeler-stylePatchBuild51-linux-x64.tar.gz
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/stylePatchBuild51/camunda-modeler-stylePatchBuild51-mac.dmg
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/stylePatchBuild51/camunda-modeler-stylePatchBuild51-mac.zip
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/stylePatchBuild51/camunda-modeler-stylePatchBuild51-win-ia32.zip
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/stylePatchBuild51/camunda-modeler-stylePatchBuild51-win-x64.zip

I can see the select template button, there are no sticky headers, and I couldn't see new glitches in the properties panel.

@christian-konrad Please review: https://github.com/camunda/camunda-modeler/pull/3026#issuecomment-1181452203.


.During remote session, whenever you press letter 'c' the Teams window jumps up even when it is minimized

Hello Folks,
When we are using Teams for remote session with customer, sometimes when you press letter 'c' the Teams window jumps up even when it is minimized.
This is especially problematic when typing on the customer environment. This has been reported by some other teammates and seems to be fixed by restarting Teams.

Hi @manihere, I'm unable to repro your issue from our end, could you please let us share more details/repro steps with us.

Hello sorry for the delay, please find me on teams<EMAIL_ADDRESS>:)

Thanks for reaching out us. According to your description, your issue is more related to Teams product, which we do not support. For issues related to teams product, please reach out to the Product support channels for Microsoft Teams. Thanks for your understanding and patience!


How do I bundle with webpack?

I have a site that already have jquery 1.7 loaded.
I want to bundle my dependencies with webpack.
I'm tried
import "select2"
require "select2"
my webpack config looks like this:
module.exports = {
    mode: "development",
    entry: {
        frb: "./src/app/loader.js"
    },
    output: {
        path: path.resolve(__dirname, "./src/lib"),
        filename: "bundle.js"
    },
    module: {
        rules: [
            // { parser: { amd: false } },
            {
                test: /\.(js|jsx)$/,
                exclude: /(node_modules)/,
                loader: "babel-loader",
                query: {
                    presets: [
                        [
                            "@babel/preset-env",
                            {
                                targets: {
                                    chrome: "58",
                                    ie: "9"
                                }
                            }
                        ]
                    ]
                }
            }
        ]
    },
    externals: {
        $: "jquery",
        jQuery: "jquery"
    },

    plugins: [
        // Ignore all locale files of moment.js
        new webpack.IgnorePlugin(/^\.\/locale$/, /moment$/),
        new webpack.ProvidePlugin({
            $: "jquery",
            jQuery: "jquery"
        })
    ]
};

I just keep getting : TypeError: $(...).select2 is not a function
Am I missing something?

Try :
    new webpack.ProvidePlugin({
      $: 'jquery',
      jQuery: 'jquery',
      'window.jQuery': 'jquery'
    })

import 'select2'
//or
import select2 from 'select2'

Did you get anywhere with this @simkessy ? I'm running into this same problem and @hfabiiano 's suggestion didn't work for me

I managed to get this to work in Typescript kind of (though I'm not sure if it's the right approach).
dropdown.ts
/// <reference<EMAIL_ADDRESS>/>
import * as $ from 'jquery';
// TODO this works but I'm not sure how to get the types right
// @ts-ignore
import * as select2 from "select2";

import "select2/dist/css/select2.css";
import "select2-bootstrap-theme/dist/select2-bootstrap.css";

// Hook up select2 to jquery
select2($);

@types/select2-module.d.ts
declare module 'select2' {
    function select2($: JQueryStatic): void;
    export = select2;
}

I also had to remove the dependency on requirejs from the DefinitelyTyped types because it conflicted with another require type, but that's kind of specific to my project I think.

I had to use this import get it to work (4.0.5):
import select2 from 'select2/dist/js/select2'

@stale
Still an unresolved issue

The proposed solutions do not work for me. Exporting everything from select2 returns an object with a default key that points to the Select2 function.
It would be great if we could use select2 in this way. I have to include the plugin the old fashioned way and it doesn't jive well with how my application works.

Ok. If you need to do this - with 4.0.7, I was able to extend what is exported by the select2 module:

$.fn.select2 = function(options) {
  options = options || {};

  this.each(function () {
    var instanceOptions = $.extend(true, {}, options);

    var instance = new Select2($(this), instanceOptions);
  });

  return this;
}```

Lines 3 - end are pretty much just copied from what I found in `src/js/jquery.select2.js` Lines 13 - 50. We only ever initialize select2 with an object so I don't need the conditional on line 16.

This appears to be more of a usage question than a bug report or common feature request.  As we continue to keep the Select2 issue tracker geared towards these two areas, bug reports and common feature requests, we are redirecting usage questions to other communities such as the mailing list, IRC, or Stack Overflow.

Maybe it would be an improvement to the documentation to add an up to date version of the installation. People will answer this question a lot, since there is no common example.

Maybe it would be an improvement to the documentation to add an up to date version of the installation.

Pull requests are always welcome at https://github.com/select2/docs
I don't use webpack, so I can't write the docs on how to make it work with webpack.


add custom smtp port to options

Description
Add {smtpPort: <your_port> } to init options. If not defined, the default port 25 will be used.

This would be useful.

Im really sorry this took me so long to get around to

@phungthanhdong  thank you for your pr

@phungthanhdong & @mvattuone  - updated 1.3.0


Improve tests.

Improve tests.
Signed-off-by: Azeem Sajid<EMAIL_ADDRESS>

please elaborate in the issue descvription - link to the relevant issue (you can do so in this way - CloudWebManage/cwm-worker-cluster#180), and write why this PR was opened

please elaborate in the issue description - link to the relevant issue (you can do so in this way - CloudWebManage/cwm-worker-cluster#180), and write why this PR was opened

This PR was in conjunction with https://github.com/CloudWebManage/cwm-worker-cluster/issues/180.
Just added some extended logging, some formatting changes, and defined constants for better maintainability.


UI examples and use cases with Taipy

We are always looking for innovative use cases and examples that showcase data science friendly UI libraries.
We welcome contributions related to examples, use cases, notebooks and integration with taipy

I want to create a taipy chatbot, similar to gguf_streaming_chatbot.py.

/assign

Would like to work on this issue. @doberst please assign this issue

Also, I think there are many opportunities to showcase the integration - chatbot as raised by @kom-senapati is one, but @Blacksujit and @Dkghuser if you have other ideas not a chatbot, then all 3 submissions would be very welcome

Yep, I am interested in adding it!

I am first time contributor to llmware, please give me the chance
@doberst

I would like to do it.


Implemented Binary Search Tree in Java and performed operations such as Insert, Delete, Inorder Traversal, Preorder Traversal, Postorder Traversal, Search, Exit

Add Java code examples for Binary Search Tree in java.

kindly follow the pr  template given inside readme.md file

Corrected the Commit and a Pull Request.

@kunal15112001 kindly use the pr template given in readme file

updates @kunal15112001


Why am I getting an error in the build function when changing the theme of the application?

My main file down below;
import 'package:flutter/material.dart';
import 'package:ajanda/screens/mainmenu.dart';
Future<void> main() async{
  runApp(MaterialApp(
      debugShowCheckedModeBanner: false, title: "Takvim", home: MainMenu()));
}

Mainmenu file down below;
import 'package:ajanda/blocs/theme.dart';
import 'package:provider/provider.dart';

//const String testDevice = 'Mobile_id';

class MainMenu extends StatelessWidget {
  MainMenu({Key key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return ChangeNotifierProvider<ThemeChanger>(
      builder: (_) => ThemeChanger(ThemeData.dark()),
      child: new MaterialAppWithTheme(),
    );
  }
}

class MaterialAppWithTheme extends StatelessWidget{
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: MainMenuBody(),
    );
  }
}

class MainMenuBody extends StatefulWidget {
  @override
  _MainMenuBodyState createState() => _MainMenuBodyState();
}

class _MainMenuBodyState extends State<MainMenuBody> {

....

}

I'm trying to make a dark theme, but I got 2 errors and I can't solve the reason why I would be glad if you could help. I'm getting an error like this in my build function. The argument type 'Widget Function (BuildContext)' can't be assigned to the parameter type 'Widget Function (BuildContext, Widget)'. The other issue like this error: The return type 'ThemeChanger' isn't a 'Widget', as required by the closure's context.
Theme.dart file down below
import 'package:flutter/material.dart';

class ThemeChanger with ChangeNotifier{

  ThemeData _themeData;

  ThemeChanger(this._themeData);

  getTheme() => _themeData;

  setTheme(ThemeData theme){
    _themeData= theme;

    notifyListeners();
  }

}

Hey, can you provide screenshot of the error

@abhikhedekar4241

You should use create to provide the ChangeNotifier. The builder is a WidgetBuilder.

Yes. You should use create instead of builder

@abhikhedekar4241 Can you give me a code sample that I can implement?

return ChangeNotifierProvider<ThemeChanger>(
      create: (_) => ThemeChanger(ThemeData.dark()),
      child: new MaterialAppWithTheme(),
);

@bierbaumtim Perfect 👍🏻

Also i'm not sure if it is possible or a good idea to have more than one MaterialApp. You can use the ChangeNotifierProvider inside runApp;
Like:
Future<void> main() async{
  runApp(ChangeNotifierProvider<ThemeChanger>(
         create: (_) => ThemeChanger(ThemeData.dark()),
         child: new MaterialAppWithTheme(),
      ));
}

@bierbaumtim I am getting one more error.

source : https://developer.school/flutter-dynamic-theming-with-provider/

move the line into the build function as in the provided source and it should work.
In an StatelessWidget it is only possible to access the BuildContext from the build method.
In an StatefulWidget you can use the BuildContext in all methods except initState to get InheritedWidgets.


Fix exception messages (remove period from message where found)

Plus convert $exception variable to $e where possible

I had terrible code style :/


MMTv4 multilingual engines

Hi MMTers
it seems that instructions for building multilingual engines are no more valid for MMT version 4. I suggest to keep them just for versions 2.* and 3.*, and add specific instructions for v4, where useless sections are removed (e.g. "Merge the aligner models") and other sections are updated (e.g. "Configuration file" has to follow what is written here).

@cettolo
thanks for reporting.
We will revise the documentation asap .

Hello, any estimate on when this 'asap' could be?
We are very happy after switching from v3 to v4 in terms of translation quality but the inability to create multilang engine is a big step back...

Hi @cettolo and @arteq
thanks for your patience, we have just updated our wiki page for multilingual engines.
Thanks for you support!


Class expression inside a generic function bug

This code seems to be valid TS:
interface ReactClass<P, S> {
    setState(state: S): void;
}

interface Props {}

interface State {
    hovered: boolean;
}

function createComponent<P extends Props, S extends State>() {
    return class Component implements ReactClass<P, S> {
        constructor() {
            this.setState({ hovered: true })
        }

        setState(state: S): void {}
    }
}

But it fails to compile:
issue.tsx(15,27): error TS2345: Argument of type '{ hovered: boolean; }' is not assignable to parameter of type 'S'.

Is it a bug?

this is not really related to classes or functions. the constraint on S is it has to be at least of type state, but does not mean that a value of type State is assignable to it, it may need more properties that are missing in the base type.
here is a simplified version of your snippit:
function setState<T extends State>(t: T) {
    var s: State = { hovered: true };

    s = t; // OK, t is a T, which is a State
    t = s; // Error, s may not be a T
}

@mhegazy I understand, thanks!


Behaviour of operator /

Currently, operator / is implemented as an element-wise multiplication with the division operator.
https://github.com/michelp/pygraphblas/blob/fcdd70836c11dd537ff5bde560279ffee8050e0c/pygraphblas/matrix.py#L517-L518
This causes unexpected results if one of the operands is empty.
A = Vector.from_lists([0,1], [1.0]*2, 4)
B = Vector.from_lists([1,2], [5.0]*2, 4)
C = A / B

print(A, A.type); print(A.to_string())
print(B, B.type); print(B.to_string())
print(C, C.type); print(C.to_string())

<Vector (4: 2)> <class 'pygraphblas.types.FP64'>
 0|1.0
 1|1.0
 2|
 3|

<Vector (4: 2)> <class 'pygraphblas.types.FP64'>
 0|
 1|5.0
 2|5.0
 3|

<Vector (4: 1)> <class 'pygraphblas.types.FP64'>
 0|
 1|0.2
 2|
 3|

The semantics should be changed to be more natural.
See relevant MATLAB code from SuiteSparse and previous discussion in #27 about operator -.

The behavior of A / B is now to use eadd() with the DIV operator.  This makes it consistent with scalar A / s as well.

Thank you.
For future reference a short demo of the new behaviour:
A = Vector.from_lists([0, 1], [1.0] * 2, 4)
B = Vector.from_lists([1, 2], [5.0] * 2, 4)

print("A"); print(A)
print("B"); print(B)
print("A / B"); print(A / B)
print("A / 5"); print(A / 5)
print("1 / B"); print(1 / B)

A
 0|1.0
 1|1.0
 2|
 3|

B
 0|
 1|5.0
 2|5.0
 3|

A / B
 0|1.0
 1|0.2
 2|5.0
 3|

A / 5
 0|0.2
 1|0.2
 2|
 3|

1 / B
 0|
 1|0.2
 2|0.2
 3|


White Screen / Blank View in routes if view is not imported

Description of the bug
Using the hilla-grocery-app example from the tutorial, When creating or adding a new route to "routes.ts",  it would compile just fine, but showing blank/white/empty view with no error messages / warnings on both backend and frontend.
export const views: ViewRoute[] = [
    // place routes below (more info https://vaadin.com/docs/latest/fusion/routing/overview)
    {
        path: '',
        component: 'grocery-view',
        icon: '',
        title: '',
    },
    {
        path: 'grocery',
        component: 'grocery-view',
        icon: 'la la-list-alt',
        title: 'Grocery',
    },
    {
        path: 'contact',   // <------------- NEW ROUTE
        component: 'contact-view',
        icon: 'la la-list-alt',
        title: 'Contact',
    },
];

For the new route to be recognized, the view needs to be imported. If the line below does not exist, you'll get the blank view.
import { Route } from '@vaadin/router';
import './views/grocery/grocery-view';
import './views/main-layout';
import './views/contact-view';   // <------------ NEED THIS LINE

Minimal reproducible example
As Above.
Expected behavior
Some checks should be performed and an error message should be displayed if the route is unknown or the view cannot be found.
Better yet, maybe don't use strings for the component reference and trigger an error during compilation. (Cf: maybe compare how the Angular router uses actual class/view object reference, not a string.)
Actual behavior
No errors/warnings, blank view.
Versions:
- Hilla 1.0.0 / 1.0.1 / 1.0. 2

Perhaps relatedly, no error is generated if the view is imported, but the component name in the routes is misspelled.

A minimal fix for that — the router could check if the component is registered under the name while rendering navigation results.
Optimally, we should probably support using component class names in the route map, so that TypeScript does static checking here.

How would class name references work together with lazy importing the view?

Thanks for pointing this out. From the top of my head, we could support setting component constructor name references lazily then, while TypeScript ensures that the lazy function promises a component constructor. Here is a TypeScript playground prototype:
type ComponentCtor = {new(): HTMLElement};
type LazyComponentCtor = () => Promise<ComponentCtor>;

type Route = {
    path: string,
    componentClass: ComponentCtor | LazyComponentCtor;
    children?: Route[],
};

class MainLayout extends HTMLElement {}

declare module 'my-view.ts' {
  export class MyView extends HTMLElement {}
}

const routes: Route[] = [
    {
        path: '',
        componentClass: MainLayout,
        children: [
            {
                path: '',
                componentClass: async() => (await import('my-view.ts')).MyView
            }
        ],
    },
];

Does not that require importing my-view.ts and all other views to set up routing?

Does not that require importing my-view.ts and all other views to set up routing?

The actual script is loaded in the browser only when the callback is run, even though the direct reference to .MyView gives the impression that it's eagerly imported.
As an alternative, we could maybe expect the class to be the default export and make a componentClass callback support promises so that the line could be reduced to this: componentClass: () => import('my-view.ts')

The import needed at the beginning of the file is also eager, right? That is currently the only solution. Maybe it would be best to change the sample code so that it fails if you try to copy-paste to add a new route?


(maint) Suppress fuzzy translation warning

When an English string changes slightly, the FastGettext will
attempt to choose a translation that seems similar, update its English
key, and mark the translation as "fuzzy", to inform the translator that
review is needed. By default, FastGettext will issue a warning when a
fuzzy translation is used at runtime. This warning comes out of FastGettext
directly, circumventing our logging framework, and so is impossible for
a user to turn off, and in some cases impossible for them to fix.
Therefore, this commit passes a flag to FastGettext to suppress the
warning.

Will the warning still be visible in the logs with this change?

Do we want to suppress these warning always or have them logged using Puppet's logging framework? Super new to this, so sorry if this is a completely naive question, but it looks like this might work to link the two loggers?  https://github.com/grosser/fast_gettext#logger

If people think there's a good reason to log this message, we could look into integrating the logging... but in reality the "fuzzy" comments in the PO files are only fixable by the translators, who so far as I know are never running Puppet. They have those messages surfaced to them via the Transifex UI.

That makes sense and is great reason for this change. I was confused by the "in some cases impossible for them to fix". Are there any scenarios where a user would be able and want to fix the fuzzy translations? Modules?

It looks like report_warning also suppresses warnings about obsolete translations. How concerned are we about this? Do you know if these also get marked in a similar way to the fuzzy translations?

Yeah, modules where the translations are user supplied, and the same user who supplied them happened to see that message. But if they were maintaining the translations properly, I would hope they would just be checking the files themselves periodically. Like every time they added a new translation, they would also update ones that had become fuzzy.

@justinstoller In the case of a module author, wouldn't they notice the change in the .po file, marking the the translation as fuzzy, or can modules not ship their own .po files?

@jhelwig we don't have any "obsolete" entries are entries that are no longer used and have been commented out by the gettext file generator (see https://www.gnu.org/software/gettext/manual/html_node/Obsolete-Entries.html). However, we just delete unused entries outright, so I don't think this warning would ever even show up for us. And even if it did, I think the same argument applies as to the one for "fuzzy": it's not generally useful to surface to users.

CLA signed by all contributors.


Download button is downloading too much

When receiving a download message, videos are sent when matching the prefix, even if the prefix is only partial.
E.g., if video with prefix Sentence44 is present, downloading request with Sentence4 will erroneously match.
Probably, just adding a _ at the end of the matching string will solve.

Solved by 3cecba171c6c1c3007954c3406c29feada595bcf


The debugger doesn't show pointer values

Any ideal to show pointer values?

Works for me.

Can you provide some code?
Is the value you try to inspect nested in other structs/arrays/maps?

Sorry I didn't make myself clear.
Any way to check the value of t in Variables like fmt.Println()?

Not really, even delve does not support this kind "pretty printing".

Thx buddy.


Getting this error  - ModuleNotFoundError: No module named 'pyngrok'  - Please Help !

ModuleNotFoundError                       Traceback (most recent call last)
 in <cell line: 6>()
4 import sys
5 import fileinput
----> 6 from pyngrok import ngrok, conf
7
8 Use_Cloudflare_Tunnel = False #@param {type:"boolean"}
ModuleNotFoundError: No module named 'pyngrok'

NOTE: If your import is failing due to a missing package, you can
manually install dependencies using either !pip or !apt.
To view examples of installing some common dependencies, click the
"Open Examples" button below.

same.

yes looks like an update is pending :(

The problem is on Requirements cell, it isn't working, maybe Colab problem. I'm trying a workaround here until TheLastBen try fix it.

Getting this too.  tried to add !pip install pyngrok before line 6 and then got "ModuleNotFoundError: No module named 'fastapi'"

wishing TheLastBen fixes it soon

It gave me the same error, then I tried later and entered without problems. Today I have the same problem.

sames

While it's being fixed you can still run this colab using "use reserve environment " command.  Not sure how it's called in English version, I'm using Russian translation, but anyway:
Top menu - Tools - Command palette (Ctrl + shift + p) - "Use reserve environment". Then run all your code cells again. It's working for me.

colab moved to python 3.10, need to adjust the deps

While it's being fixed you can still run this colab using "use reserve environment " command. Not sure how it's called in English version, I'm using Russian translation, but anyway: Top menu - Tools - Command palette (Ctrl + shift + p) - "Use reserve environment". Then run all your code cells again. It's working for me.

In the English language version the command is "Use fallback runtime version"

While it's being fixed you can still run this colab using "use reserve environment " command. Not sure how it's called in English version, I'm using Russian translation, but anyway: Top menu - Tools - Command palette (Ctrl + shift + p) - "Use reserve environment". Then run all your code cells again. It's working for me.

In the English language version the command is "Use fallback runtime version." I'm up and running with that option for now.

Same issues but resolved it with Fallback Runtime version, thanks for the help.

update your notebooks, should work fine now, let me know if any dependency needs updating

update your notebooks, should work fine now, let me know if any dependency needs updating

Thanks for the quick attention to this!

update your notebooks, should work fine now, let me know if any dependency needs updating

Grateful!! 🙏🙏

Thank you so much Ben :)

Thank you Ben - doing gods work <3
Sent through space
On 28 Apr 2023, at 07:44, HelpANewbie @.***> wrote:

Thank you so much Ben :)
—
Reply to this email directly, view it on GitHubhttps://github.com/TheLastBen/fast-stable-diffusion/issues/2053#issuecomment-1527068015, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AT45DRA3YJN5N72QIMZKHOLXDNRLPANCNFSM6AAAAAAXOFCPMU.
You are receiving this because you commented.Message ID: @.***>

update your notebooks, should work fine now, let me know if any dependency needs updating

I still get this: ModuleNotFoundError: No module named 'pyngrok'
How to update notebook :o

@Fuchsei how to reproduce the error ?


Allow giving jobs names via execute for IBMQ devices

Re-opens #3622.
Closes #3294
Summary
Details and comments

Dont forget about release notes!

run_config was designed for this kind of situations.
It seems to me that this is already supported: execute(..., run_config={'job_name': job_name}

run_config does work.  However if I change the backend to a simulator then it fails.  In addition, the user has no idea that this is even an option because there is nothing to tell you what run_config accepts.  As already mentioned, the acceptable kwargs that one can pass in this option are backend specific.

In addition, the user has no idea that this is even an option because there is nothing to tell you what run_config accepts. As already mentioned, the acceptable kwargs that one can pass in this option are backend specific.

That's true for all the kwargs in run_config. Probably the documentation can be improved, mentioning that the dict will be passed to backend.run(..., **run_config).

@1ucian0 I am not sure what the block is for here. This works, prevents errors due to backend specificity of the run_config kwargs, and documents the feature for end users.

The full point of run_config is handling this situation.

run_config does work. However if I change the backend to a simulator then it fails.

This is what I would expected. In the same way that you changed the parameter backend in execute, you also need to change run_config.  It is analogous to map, which might fail if you change func. run_config is forward to backend.run as parameters. I agree that more documentation can clarify this. Alternatively, we can recommend backends to ignore kwargs that are not in their run, implementing something like def run(qobj, ..., **_):. That is a different discussion.
Asking Terra to support job_name is asking terra to administrate a namespace that belongs to the backend. What if in the future another backend supports job_name but with a different semantics? What if the backend renames or drops job_name?
It is true that we handle other backend-specific-ish parameters (like seed_simulator). However, they are part of the qobj specification. That's way they are supported for every backend. I do think these kind of parameters should be also pull out the qboj and being handle with run_config (again, different discussion). We should move in that direction of making Terra more backend-agnostic instead of the direction that this PR suggests.
TL;DR - My main reason for blocking is because I think this PR undermines a fundamental principle of Terra: backend independency.

Do you agree?

Why can't this introduce an explicit job_name kwarg, but then have it be dumped into the run_config and shipped to the backend? The backend can decide what to do with it. Just leave a note saying that this option works if backend supports it, and IBM backends currently do.
The explicit hardcoding and special casing on 'IBMQBackend' string type name is a bit weird.
BTW this is like every other option. Half of those options are not generic for every backend, they either work only for simulator backends, or pulse backends, etc.. execute is supposed to be a high level wrapper function, whoever uses it presumably understands the backend they are sending jobs to. Documentation is important.

Because simulators will fail if it is added. So to get ibmq backend names to work that way the simulators and other providers need to be able to handle it gracefully. Execute should not fail if an additional option is passed that is irrelevant for success of the job itself. The string comparison is because terra does not depend on the ibmq provider, so I cannot import the instance to check with isinstance. With no documentation, run_config is impossible to rely on as there is no set of rules on how to use it or how it is consumed by various backends.

Yes my assumption is the user passes the option to backends that support it. This should of course be documented, but for example we currently can do:
execute(circuit, backend, meas_level=1)
There is no code in execute to catch that backend is definitely a pulse enabled backend. If backend is a circuit simulator, this will fail and we have been fine with that. I don’t see how this is different.

On Dec 18, 2019, at 7:16 AM, Paul Nation<EMAIL_ADDRESS>wrote:
Because simulators will fail if it is added. So to get ibmq backend names to work that way the simulators and other providers need to be able to handle it gracefully. Execute should not fail if an additional option is passed that is irrelevant for success of the job itself. The string comparison is because terra does not depend on the ibmq provider, so I cannot import the instance to check with isinstance. With no documentation, run_config is impossible to rely on as there is no set of rules on how to use it or how it is consumed by various backends.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub, or unsubscribe.

Things likes result = execute(circuit, BasicAer.get_backend('qasm_simulator'), meas_level=1) do not fail. That is because meas_level ends up in qobj. I think backends ignore fields in the qobj that are not used by them. However, job_name is not like meas_level. See backend.run signature.
The same behavior for job_name in run_config can be reached by asking backend to ignore kwargs that are not supported by them.

Ok based on the IBMQBackend.run() signature that you posted above, i'm not sure run_config will work for this case then. Run config is supposed to go in the qobj (by the assembler), but this is outside qobj. How does that work?
@1ucian0 said:

It seems to me that this is already supported: execute(..., run_config={'job_name': job_name}

Regardless I think if I do execute(circ, backend=simulator, job_name=...), this should be an error and not just silently ignored (as is done in this PR). I have made an assumption which cannot hold with my chosen backend.

Setting meas_level=2 is silently ignored by backends that do not support pulse, as is the case with many other options.  So not sure what changes with this PR in that respect.  In order for that to work, each backend must raise an error on any kwargs in run_config it does not recognize.  This will be pulse dependent on the IBMQ devices.

@nonhermitian you are right the current behavior is that irrelevant options are ignored. Your PR is thus keeping with the current behavior.
I am just saying that this is not a good behavior in my opinion. We can't just ignore an option that the user set, without raising a warning or error to inform the user. So I would be fine if you just allow this to fail here for Aer backends (omit the backend check). And then we follow up later to also catch other invalid qobj options on client-side, before sending qobj.
Reopening PR.

Since we agree the unused options should trigger error/warning, I would like to focus on the how.
I have the strong opinion that this responsibility should be on the provider/backend side via run_config for the reasons exposed here.

I am completely fine if the backends / providers take this over. Any option set that is not used / and does not affect the outcome should emit a warning not error.
This also means that the backends should dynamically generate their docstrings to indicate which kwargs they support in run config, e.g. the pulse options.
The downside to this is that changing between backends is not as simple as before

I am completely fine if the backends / providers take this over. Any option set that is not used / and does not affect the outcome should emit a warning not error.

I agree, a warning is the way to go.

This also means that the backends should dynamically generate their docstrings to indicate which kwargs they support in run config, e.g. the pulse options.

What do you mean by "dynamically generate their docstring"? The docstring is there already.

The downside to this is that changing between backends is not as simple as before

Not fully sure what you mean here. Maybe an example?

A backend tells you nothing about which kwargs it takes:
Docstring:      Backend class interfacing with an IBMQ backend.
Init docstring:
Initialize remote backend for IBM Quantum Experience.

Args:
    configuration: configuration of backend.
    provider: provider.
    credentials: credentials.
    api: api for communicating with the Quantum Experience.

Before, it was possible to simply change a backend in execute and it would work without warnings or errors, e.g. like noise_model can be passed to a real device.  Now warnings are emitted, which breaks the seamlessness that we touted before.

A backend tells you nothing about which kwargs it takes:

The run_config dict is passed to backend.run, not to the backend constructor. We can mention that in the  execute docstring. Something like "check backend.run to see what arguments can go in run_config".

Before, it was possible to simply change a backend in execute and it would work without warnings or errors, e.g. like noise_model can be passed to a real device. Now warnings are emitted, which breaks the seamlessness that we touted before.

A warning will allow the execution and an equally simple way.
Either unused options are silently ignored (which is something that @ajavadia does not like, and I tend to agree) by the backend or the backend emits a warning (which is something that you don't like). It has to be one of them, I don't see any other way around.

The first item will be addressed with the change to configurable backends.
I am fine with warnings, just pointing that out.

In summary, we are agreeing that:

The jobs name option should be handle in execute via run_config.
The backend should warning when elements from run_config are not being used.
The backend should extend the docstring to be explicit on what are the run_config elements that are being used.
Same should apply to backend-specific params, like pulse options.

@ajavadia and @kdk, are you okey with this?
If so, I will move this issue to the providers repo, since there is nothing here to do on the terra side. Or am I missing something?

I would say one issue is how to handle the kwargs that are already in execute. Everything will be grouped into a single backend_config, and warnings will be emitted for each kwarg that a backend does not support. For example, any open device will give many warnings for the pulse args in execute.

Everything will be grouped into a single backend_config

It's an option, but I don't feel very strongly about it because the current backend arguments are well defined by the qobj specification (while run_config are totally in the backend namespace).

any open device will give many warnings for the pulse args in execute.

Maybe it is possible to group them in a single warning?

So I guess my statement is that soon the backend calls will be
‘’’
backend = Backend(backend_config)
backend.run([circuits])
‘’’
So the default behavior will be a warning when the default execute options are not valid. In the case of open devices this means that every call to execute will give a warning. Are we comfortable with that?

What about something like this backend = Backend(backend_config, param_warning=False)?

With the v2 provider interface the need for execute() will be reduced (it should really exist for backwards compat only).
This particular feature can just exist in backend.run(circuit, job_name). This makes sense to me as job name and many other options are features of particular backends.
So I'm going to close this and let's make sure it works as expected with the new ibmq_backend.run() method.


tour: wrong link to the zh (simplified) tour

hi guys, i found some error on the simple-chinese version tour.
"https://tour.go-zh.org/"  should be "https://go-tour-zh.appspot.com/"
and
on "https://go-tour-zh.appspot.com/"
if u click the "RUN" button it will saying "Error communicating with remote server."
THANK U:)
Context: https://tour.golang.org/welcome/2
Change the title above to describe your issue and add your feedback here, including code if necessary

Thanks for the report.
We don't control or deploy the tour translations, so the "communicating with remote server." error should be reported to the owner of the zh tour.
Regarding the link: I'm not sure it would be a good idea to change it now, since the tour at the second link is broken too, at the moment. But we can change the link when it gets fixed.

Simplified chinese translation is now online. Closing here.


Replace fsouza/go-dockerclient by docker/docker/client

Currently, Weave Net relies on https://github.com/fsouza/go-dockerclient which, unfortunately, does not support Plugins API introduced in v1.24.
Instead, we could switch to the official Docker client (https://godoc.org/github.com/docker/docker/client) which is used internally in Docker.

iirc there is a good reason we don't use the latter. Lacking proper support for events. At the time I last looked, at least.


rustic-rustfix: change function call

Thanks!
The build isn't actually failing, it seems we have to move away from travis

Builds have been temporarily disabled for public repositories due to a negative credit balance. Please go to the Plan page to replenish your credit balance or alter your Consume paid credits for OSS setting.


[IS A BUG?] RedissonReadLock#tryLockInnerAsync

is this a bug ? when read lock try lock but write lock is held

the same with jdk rw lock


Please clarify Compute types required in demo

In blob/master/aiml30/README-Attendee.md please clarify the Compute type that should be created. The UI now separates Notebook VM / Training / Inference. I assume that the Kubernetes compute should be created under Inference for example...

Hi @rohancragg thank you for this feedback - very good spot - let me fix this and report back asap

Hi @rohancragg sorry for the delay - I have updated the instructions with further updated details - see commit here: https://github.com/microsoft/ignite-learning-paths-training-aiml/commit/ebcb3d491c64f1815f0fcde449cd6f61ff61911c


ETCDCTL_API=3 etcdctl lease grant  -w json does not return json

When creating a lease with json as the output format, the output is not printed in json. Instead, it is printed as a simple format.
ETCDCTL_API=3 etcdctl --cert /etc/etcd/peer.crt --key /etc/etcd/peer.key --cacert /etc/etcd/ca.crt --endpoints https://<IP_ADDRESS>:2379 lease grant 10 -w json
2017-04-20 09:40:33.817507 I | warning: ignoring ServerName for user-provided CA for backwards compatibility is deprecated
lease 694d5b8b1830d1ae granted with TTL(10s)

Affected version: etcd-3.1.3

Because https://github.com/coreos/etcd/blob/master/etcdctl/ctlv3/command/lease_command.go#L70

@heyitsanthony @gyuho

Maybe? Just shooting atm, did not try to compile it and run it.
if _, ok := display.(*simplePrinter); ok {
	fmt.Printf("lease %016x granted with TTL(%ds)\n", resp.ID, resp.TTL)
} else {
	displaydisplay.Get(*resp)
}

src/github.com/coreos/etcd/etcdctl/ctlv3/command/lease_command.go:73: cannot use *resp (type clientv3.LeaseGrantResponse) as type clientv3.GetResponse in argument to display.Get

Ok, the LeaseGrantResponse needs to implemented the interface.

Yeah, @heyitsanthony do you remember why some lease RPCs are missing from printer interface?

@gyuho lease commands weren't picked up during the printerization of the commands. They should be displayable as json since they map to RPCs.

Thanks guys


http://<IP_ADDRESS>/v1.2/4/shops returns 500 error.

I need to understand the json structure as there is no documentation on how to fetch data. Could you please check.

having the same problem please guide. do we have to connect it with apiary.io ?

Sorry for the inconvenience. The latest release is connected to the apiary mock server providing the basic functionality.


Qt GUI: HighDPI support

avoid scaling issues and blurred icons in menus on HighDPI screens
screenshots from KDE, left - no changes (master as is), right - with this fix (noticeable change for round icons)

Thank you for the update.


V1.0.3

refactor(release): rename function to createReleaseEnvironment
refactor: unify pending migration function return
refactor: add logging to export API functions
refactor(cli): update contentful management token env var

There are a lot of breaking changes in the PR. Renamed CLI args, renamed API functions. That should be a major release (v2.0.0).


mostly typo fixes.

Thanks for the fix, That really was a lotta typos concentrated on a small area.


Fix merge conflict. Terminal works again in the buffer-set branch

Fix merge conflict. Terminal works again.
Target-branch: buffer-set.
Signed-off-by: Oleksandr Andriienko<EMAIL_ADDRESS>

@parisk review, please.

Thanks 😄 , I closed this in acdfaa1d55f872bcbc0fb6585e665ef739e1375b.


Split test specimens to a separate repo

The source tarball is about 700 KiB, of which about 570 KiB are test specimens.
To slim down the repo:

Create a new repo with the specimens.

Where possible, record the URL from which the specimen is available, so it can be automatically refreshed and used with mock HTTP text fixtures.

Create sdmx.testing to retrieve these and provide them to the rest of the test suite.

Since this change removes the need to keep the set of specimens small, all of the endpoint tests could be stored as specimens; this would allow those nightly source tests to be run faster, and regardless of whether the service(s) were online. (The tests of the live services could be retained as a canary rather than functional test.)

https://github.com/khaeru/sdmx-test-data contains the test specimens as of 2128d4d.


Subapp

Tests are broken but demos work, @asvetlov could you please take a look on API in general, when you have free time?

Ok
On Mon, Nov 7, 2016 at 1:18 PM Nikolay Novik<EMAIL_ADDRESS>wrote:

Tests are broken but demos work, @asvetlov https://github.com/asvetlov
could you please take a look on API in general, when you have free time?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aio-libs/aiohttp_admin/pull/90#issuecomment-258810180,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVwL3I2ZZUA0KPvDOPUDBXGk1Pfc4eEks5q7wjqgaJpZM4KrClW
.

--
Thanks,
Andrew Svetlov

Current coverage is 94.12% (diff: 100%)

Merging #90 into master will increase coverage by <.01%

@@             master        #90   diff @@
==========================================
  Files            11         11
  Lines           663        664     +1
  Methods           0          0
  Messages          0          0
  Branches         78         79     +1
==========================================
+ Hits            624        625     +1
  Misses           29         29
  Partials         10         10

Powered by Codecov. Last update 9c8e1b8...339ed1d


docs(card): Update Card examples

Update card title and subtitle in the examples to be in sync with the upstream bootstrap docs

[ ] Bug fix
[ ] New feature
[x] Chore
[ ] Breaking change
[ ] There is an open issue which this change addresses
[x] I have read the CONTRIBUTING document.
[x] My commits follow the Git Commit Guidelines
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Closes #1991

@kyletsang I noticed 2 small typos in the default commit message

such as a documentation => such as documentation
indicating that is closes or fixes the issue. => indicating that it closes or fixes the issue.

Do you want me to create a separate issue for this?

Sure separate PR is best as it's unrelated to the current one.

Thanks


Documentation update

Improve & Update Readme file
adding workflows for raising issue template

@Khushalsarode hey i also have an separate pull request i want to know to link pull request to this issue bro can you explain once

you can assign that task to me under gsso-ext and Hacktoberfest label..

hey I want to improve Readme file with proper directions. I'm a beginner can you please let me work on this

@Khushalsarode hey i also have an separate pull request i want to know to link pull request to this issue bro can you explain once

what i understand from your query is: you want to know how to link issue to PR you raise? correct
so when you raise issue it has one number prefix by '#'
when you raise PR add '# and issue number' it will link and when use 'closes #number' it will close issue when merge or closed.
did you got it!
@nagajaideep

yeah got it after an yt tutorial

do we need to add gssoc and gssoc-ext labels here as this programs has been merged?
@07sumit1002 then this PR get counts!


Query S1GRD by Track

Is it possible to include the Track number in a query to the S1GRD collection? I was going through the example notebook here https://github.com/dcs4cop/xcube-sh/blob/master/examples/notebooks/Ex1b-DCFS-Datasets.ipynb and can't find any reference to a track number. That would be really helpful.
Also raised on

the sentinelhub forum: https://forum.sentinel-hub.com/t/query-s1grd-via-track/6763
xcube issues (actively taken care here): https://github.com/dcs4cop/xcube-sh/issues/93

We moved to openEO at CDSE


Carthage support, conformance to Swift 3

Thanks for the work @128keaton, I've added Carthage support to version 4.


Errors are not visible

How to reproduce: go to Create your TalentLayer ID step, try to press "create" button with insufficient balance (I reproduced with 1.1 matic) => an error message is only at console
Possible solutions: show toast message with an error

fixed


No "main" or "exports" field indefined in package.json

Just got an error message with this package in my Nuxt/Vue application and think it could be fixed on this package to prevent unnecessary logging:
[2:51:59 PM]  ERROR  (node:45277) [DEP0151] DeprecationWarning: No "main" or "exports" field defined in the package.json for /node_modules/dl-stream/ resolving the main entry point "index.js", imported from /node_modules.
Default "index" lookups for the main are deprecated for ES modules.

Basically, the build process complains that dl-stream has no main or exports field and is falling back to the index.js.
Adding the following to package.json should do the trick:
"main": "index.js"

Sure. I thought the module field was enough, but that didn't really catch on. The standard thing seems to be exports now (I don't know, I guess some older tools may expect main to point to a CommonJS module only).
You want to do the PR ?

At this time, I am not deep enough to know which of the two would be the correct one to add, as I have not developed any modules like this.
I just thought I'd report it so that others may not run into the same warning.

Fixed and published.

I just pulled the update into my project and the warning is gone. Thank you, @Touffy.


How to use with self-hosted GitLab?

Is it possible to use this extension/add-on with self-hosted GitLab?

Currently not supported since it will ask too ambitious permission, if you really need that, you can clone this repo, add permission to the manifest file and build the extension by yourself

I have never written an extension but would like to look into it.
When you say permission, what do you mean by that? What file do I need to look at? I saw in the code where you specify the GitLab URL so think adding a custom URL option is straight forward. Just not sure what the permission is for?

Scratch that. I see where you mean. I need to read up on what this setting is and what it means. Thank you!

So I cloned the repo and uncommented the <input id="gitlab-url" type="text" value="https://gitlab.com"/> line in options.html. I was able to login. But when I open a new script it says "Unknow Error" in the top, in a red box.
The spelling mistake helped because I only see two files with "Unknow": gas-api.js and gas-hub.js.
I modified both of them to narrow down and determined it is erroring on line 35 of gas-hub.js. I changed that line to include err.message:

Cannot read property 'forEach' of undefined

I am going to try to narrow down which forEach it is, unless you happen to have an idea where it might be failing?

Bleh. I figured it out.

jquery.min.js:6 Cross-Origin Read Blocking (CORB) blocked cross-origin response https://[internal gitlab URL]/api/v4/groups?per_page=25&private_token=[redacted] with MIME type application/json. See https://www.chromestatus.com/feature/5629709824032768 for more details.

Script editor is on https://script.google.com/ (internet) and it's trying to access our internal (intranet) gitlab environment.
Bollocks!

@imthenachoman  can you post the steps you followed to make it work with your gitlab server? Thanks!

I never got it working but that is because of my company's firewall rules.
I don't remember exactly what I did now but essentially:

Cloned the repo and uncommented the <input id="gitlab-url" type="text" value="https://gitlab.com"/> line in options.html.
Added my GitLab's URL to permissions in the manifest.json file
Loaded an unpacked extension in Chrome using the developer mode

@imthenachoman thanks!!


Fix CI passing when it shouldn't

I found instances when CI was passing when it shouldn't. This PR should fix that.

I'm going to merge even with failing tests because the failures are unrelated to this PR and things we need to fix.


the f1_NORM experiments crashed out; need to be run again.

the f1_NORM experiments crashed out because I switched branches in the middle of their execution. Good to know for future experiments. For now they'll need to be run again.

[x] rerun f1_NORM assimilation cases
[x] postprocess f1_NORM assimilation cases

Originally posted by @mollymwieringa in https://github.com/mollymwieringa/cice-scm-da/issues/6#issuecomment-1641137078

experiments were performed and postprocessed.


How to set multiple cronjob ?

in this code cronjob running only 1 schedule function
it's go micro can run only 1 job?
	// build leader
	lead := consul.NewLeader(leader.Nodes(serviceList...))

	cron := sync.NewCron(sync.WithLeader(lead))
	cron.Schedule(
		task.Schedule{Time: time.Now(), Interval: 5 * time.Second},
		task.Command{Name: "cron1", Func: cli.Test},
	)
	cron.Schedule(
		task.Schedule{Time: time.Now(), Interval: 2 * time.Second},
		task.Command{Name: "cron2", Func: cli.Test2},
	)```

Cron is unsupported. Please dont use it.


Switch to bundled buck2 prelude

https://buck2.build/docs/users/advanced/external_cells/

@JakobDegen, this is working on Linux and macOS, but not Windows.
BUILD FAILED
From load at implicit location

Caused by:
    0: non-forward relative bundled path (internal error)
    1: expected a normalized path but got an un-normalized path instead: `abi\BUCK.v2`

Fixed by https://github.com/facebook/buck2/commit/9de4fc1729c49eb7b000be7a0a5cd8d2aa6db136. Thank you!


Allow animation speed greater than 0

This PR changes

Documentation (jsdoc)
Nothing, it's a bug fix

Animation.speed= sets delay to 1000 / value if value is greater than or equal to 1. However, setting delay directly allows for animation delays greater than 1000. Therefore, changing Animation.speed= to allow for speed greater than 0.

Thanks, happy to merge this change in.


Find how to cap used memory to 70 MB

import resource

def limit_memory(maxsize):
    soft, hard = resource.getrlimit(resource.RLIMIT_AS)
    resource.setrlimit(resource.RLIMIT_AS, (maxsize, hard))

import resource
def limit_memory(maxsize):
soft, hard = resource.getrlimit(resource.RLIMIT_AS)
resource.setrlimit(resource.RLIMIT_AS, (maxsize, hard))

This only works on linux, there is an other way to do on windows but I wasn't able to implement it


feat: add asciinema player

Only thing that lefts here and I'm trying to do is pass the cast files properly and store them in the correct place


Add devices verification

encrypted_event_info.xml

line 20 "Event information" title should be defined as a string resource in string.xml (ex: "@string/encryption_information_title")


Use 'create' flag instead of instance.pk (#1274)

Problem
(issue #1274)
For bulk creates / updates, the instance.pk field was being used to determine whether a bulk update or create should be performed. This doesn't work when pk is dynamically generated (e.g. UUID).
This was originally reviewed in #1278, but that PR was closed when I force pushed following rebase :facepalm:
Solution
This fix uses the 'new' value returned from get_or_init_instance(), and passes this in as a kwarg to save_instance(). Hence the check against instance.pk is not required.
This will be an API breaking change.
Acceptance Criteria

Added new integration tests which verify the issue
Existing 'bulk' tests pass
Manually tested bulk imports using the import_book script (also made some changes here)

Coverage remained the same at 98.074% when pulling 9386fff057d60042a67a05fcc805ed3a88afd810 on matthewhegarty:use-create-flag-instead-of-instance-pk into 0ccd089149863dc680c289cdfb82c8a5d23208ac on django-import-export:main.


TypeScript language service dies when you have an untitled file open.

It appears that having an open untitled unsaved file breaks TypeScript features.
Desired behavior: One should be able to have an unsaved file in memory without losing all the valuable features of VS Code and TypeScript that we know and love.
Steps to Reproduce:

Create a new untitled file (cmd/ctrl + n) in a TS project
Wait just a moment while watching the TypeScript service output
Observe that the TS language server has died and the IDE is stuck in a loop of "Initializing JS/TS Language features

Issue Type: Bug

Create a new untitled file (cmd/ctrl + n) in a JS/TS project
Wait a moment
Observe that the TS language server has died and the IDE is stuck in a loop of "Initializing JS/TS Language features

output on my machine from the TS server:
[Trace  - 15:28:28.590] <semantic> Event received: projectLoadingStart (0).
Data: {
    "projectName": "tsconfig.json",
    "reason": "Creating possible configured project for untitled:^Untitled-1 to open"
}
[Trace  - 15:28:28.591] <semantic> Response received: updateOpen (2). Request took 25982 ms. Success: false . Message: Error processing request. Cannot read property 'path' of undefined
TypeError: Cannot read property 'path' of undefined
    at ProjectService.updateNonInferredProjectFiles (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:137442:43)
    at ProjectService.addFilesToNonInferredProject (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:137332:22)
    at ProjectService.updateRootAndOptionsOfNonInferredProject (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:137480:22)
    at ProjectService.loadConfiguredProject (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:137416:22)
    at ProjectService.createAndLoadConfiguredProject (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:137356:22)
    at ProjectService.createLoadAndUpdateConfiguredProject (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:137361:36)
    at ProjectService.assignProjectToOpenedScriptInfo (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:138186:44)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:138417:107
    at Object.mapDefined (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:565:30)
    at ProjectService.applyChangesInOpenFiles (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:138417:48)
    at Session.handlers.ts.createMapFromTemplate._a.<computed> (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:139271:46)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:140929:88
    at IOSession.Session.executeWithRequestId (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:140920:28)
    at IOSession.Session.executeCommand (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:140929:33)
    at IOSession.Session.onMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:140952:35)
    at Interface.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js:142267:27)
    at Interface.emit (events.js:200:13)
    at Interface._onLine (readline.js:314:10)
    at Interface._normalWrite (readline.js:459:12)
    at Socket.ondata (readline.js:170:10)
    at Socket.emit (events.js:200:13)
    at addChunk (_stream_readable.js:294:12)
    at readableAddChunk (_stream_readable.js:275:11)
    at Socket.Readable.push (_stream_readable.js:210:10)
    at Pipe.onStreamRead (internal/stream_base_commons.js:166:17)
[Trace  - 15:28:28.593] <semantic> Sending request: geterr (3). Response expected: yes. Current queue length: 0
Arguments: {
    "delay": 0,
    "files": [
        "/Users/vincentpaultrivett/linen/node/src/loom-get-applications/getData.js",
        "/Users/vincentpaultrivett/linen/node/src/loom-get-applications/LoomGetApplications.d.ts",
        "/Users/vincentpaultrivett/linen/node/src/loom-get-applications/filteringHelpers.ts",
        "/Users/vincentpaultrivett/linen/node/src/loom-get-applications/index.test.js",
        "untitled:^Untitled-1"
    ]
}
[Info  - 15:28:28.593] Killing TS Server
[Info  - 15:28:28.716] TSServer exited
[Info  - 15:28:28.716] Using tsserver from: /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib
[Info  - 15:28:28.719] <syntax> Forking...
[Info  - 15:28:28.725] <syntax> Starting...
[Info  - 15:28:28.727] <semantic> Forking...
[Info  - 15:28:28.743] <semantic> Starting...
[Trace  - 15:28:28.746] <semantic> TypeScript Server: trying to cancel ongoing request with sequence number 3
[Trace  - 15:28:28.752] <semantic> Sending request: configure (0). Response expected: no. Current queue length: 0
Arguments: {
    "hostInfo": "vscode",
    "preferences": {
        "providePrefixAndSuffixTextForRename": true,
        "allowRenameOfImportPath": true
    }
}

VS Code version: Code 1.41.1 (26076a4de974ead31f97692a0d32f90d735645c0, 2019-12-18T14:57:51.166Z)
OS version: Darwin x64 19.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz (4 x 2300)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
8, 7, 6

Memory (System)
8.00GB (0.20GB free)

Process Argv
.

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

vscode-sql-formatter
adp
1.4.4

vscode-opennewinstance
chr
0.0.6

path-intellisense
chr
1.4.2

gitlens
eam
10.2.0

prettier-vscode
esb
3.18.0

relative-import
sai
1.3.1

code-settings-sync
Sha
3.4.3

indenticator
Sir
0.6.0

highlight-matching-tag
vin
0.9.6

(1 theme extensions excluded)

I looked around a little for similar errors but haven't found one.

Duplicate of https://github.com/microsoft/TypeScript/issues/35914
Can you please try updating to the latest TypeScript version and letting us know on the upstream issue if that fixes the problem

Thank you mjbvz, I will watch that issue, apologies for not turning it up. I tried the nightly TS extension for the sake of experiment, but the error remained after a refresh. For now I am disabling the "files.defaultLanguage": "javascript", setting and avoiding the error.


unreachable code after return statement

unreachable code after return statement at line 111 detected in Firefox console

It's the end of the method. It shouldn't throw that error. Check if everything is working as intended. Also make sure you haven't added code after the return statement.


[WIP] Use CRD backed identities by default

This change is

test-me-please

test-nightly

Coverage decreased (-0.3%) to 44.048% when pulling a59eb473685aa57b6d6c502fb15bd4f8be48100e on raybejjani:default-crd-identities into 8f860e7d0037849dec90d501ec11a87ec58ee03a on cilium:master.

test-me-please

test-nightly

test-me-please

test-nightly

test-me-please

test-me-please

test-nightly

test-me-please

test-me-please

test-nightly

test-me-please

test-me-please

test-me-please

test-nightly

test-me-please

test-me-please

test-me-please

test-nightly

test-me-please

test-nightly

test-me-please

test-me-pleas

test-me-please

test-me-please

I'll merge since I addressed aanm's comments, and other PRs will depend on these commits.


anz client

anz client 👍

lmao, commit and commit2

Can you rewrite your changes to a branch within my repo (GitHub action workflows have funny permission rules for forked repos....)


chore: automate release of charts

This PR
Automates the generation and publishing of charts in the release workflow.
Related Issues

#219
Notes

Follow-up Tasks

How to test

Codecov Report

Merging #237 (552d345) into main (c486cc2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #237   +/-   ##
=======================================
  Coverage   53.16%   53.16%
=======================================
  Files           3        3
  Lines         363      363
=======================================
  Hits          193      193
  Misses        156      156
  Partials       14       14

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


License difference

Hi,
It seems Cargo.toml and the recent LICENSE file have a different license, would it possible to update one of them ?
Thanks a lot for this emulator, especially the tests :-)

Thanks, I noticed that, and I'll be sure to take it into account and use the proper licenses/citations.

Regarding the syntax of the Cargo.toml license line, do you know if it's case sensitive ? I could not find an answer in the docs; I'm not sure it's relevant.

Let's play safe and use the short identifier case from https://github.com/spdx/license-list-data/blob/v3.11/licenses.md
Thanks.

Thanks a lot !


fix some unsafe behavior in std.format

What is made safe by this and where is the @safe unittest that shows that.

@burner Walter is fixing various safety related bugs. In this case, the next version of dmd will disallow accessing .ptr in @safe code (which is currently allowed, IIRC). In order for the DMD PR to pass on the autotester, accessing .ptr should first be encapsulated throughout druntime ans phobos.
See also https://github.com/dlang/dmd/pull/5860

@ZombineDev thanks. @WalterBright I would have liked this link to the dmd PR in the original PR description. Figuring out what the purpose of this PR is would have been easier this way.

LGTM

Auto-merge toggled on

This pull request introduced a regression:
https://issues.dlang.org/show_bug.cgi?id=16676


TNT-37202  - Added xdm viewName mixin for SPA support

Please link to the issue #…
https://jira.corp.adobe.com/browse/TNT-37202

@clubycoder and @dancingcactus could you please take a look and let us know if the proposed changes are OK.
CC: @jfkhoury


Locale should be the first argument

I saw a slide in the presentation where the message string was first, locale second. We should keep locale as the first argument.

Are you proposing that the arguments should be (locales, source, options) or (locales, options, source)?
My sense is that any which way we go we'll need to break with some precedent, and that (source, locales, options) is the least worst choice as it adds the new required argument first and keeps the optional locales+options arguments together, as they are currently.
The current order was arrived at after some discussion with @gibson042 early on in the proposal.

Probably (locales, source, options) since options should be last so that you don't have any trailing arguments after the options bag.

I also agree with sffc. I think locales should be the first arg.