empty output and already defined variables for the IPython terminal

Description of your problem
Once started Spyder, there are three variables already defined in the explorer (e, euler_gamma, using_mklfft).
Theses variables produce no output in the Ipython console. Actually, the output of the IPython console shows an empty output for those or any other variables.
What steps will reproduce the problem?

Open Spyder 3.1.3
Click on the IPython terminal
Go to the variables explorer

What is the expected output? What do you see instead?
I expected the output of whatever I enter as "In". I can't see nothing instead
Please provide any additional information below
Versions and main components

Spyder Version: 3.1.3
Python Version: 3.6.0
Qt Version: 5.6.2
PyQt Version:
Operating system: Ubuntu

Dependencies
Please go to the menu entry Help > Optional Dependencies (or
Help > Dependencies), press the button Copy to clipboard
and paste the contents below:
jedi =0.9.0      :  0.9.0 (OK)
matplotlib >=1.0 :  2.0.0 (OK)
nbconvert >=4.0  :  4.2.0 (OK)
numpy >=1.7      :  1.11.3 (OK)
pandas >=0.13.1  :  0.19.2 (OK)
pep8 >=0.6       :  1.7.0 (OK)
psutil >=0.3     :  5.0.1 (OK)
pyflakes >=0.6.0 :  1.5.0 (OK)
pygments >=2.0   :  2.1.3 (OK)
pylint >=0.25    :  1.6.4 (OK)
qtconsole >=4.2.0:  4.2.1 (OK)
rope >=0.9.4     :  0.9.4-1 (OK)
sphinx >=0.6.6   :  1.5.1 (OK)
sympy >=0.7.3    :  1.0 (OK)

Please run
spyder --reset

in a terminal and try again

That made the trick ;)
Thanks a lot and my most sincere congratulations for this excellent IDE!

:+1: glad that trick solved your problem and thanks for your kind words :-)


sky shader example has validation eror

Related to #232, push constants when used in a "block" fashion as they are in the sky shader need a Block decoration in spir-v, I guess https://github.com/EmbarkStudios/rust-gpu/issues/232
though it does still work for me, at least on nvidia

The dev guide example for uniforms has the same error. And you will likely run into this as well when running ark if you enable validation.

SwiftShader uses SPIRV-Tools and that also fails (see https://github.com/EmbarkStudios/rust-gpu/issues/136#issuecomment-732047047) with:
SPIR-V ERROR: 0:0 PushConstant id '8' is missing Block decoration.
From Vulkan spec, section 14.5.1:
Such variables must be identified with a Block decoration
  %shared__ShaderConstants = OpTypeStruct %uint %uint %float

Looks like this is easy to reproduce with:
spirv-val --target-env vulkan1.0 target/spirv-unknown-unknown/release/sky_shader.spv


nz-input style

nz-zorro input background color can be changed? I tried a lot of ways are not in the source code components to join the style does not work

please read the doc
https://angular.cn/guide/component-styles#特殊的选择器


Unable to authenticate against grafana Ingresses

/area monitoring
/kind bug
What happened:
Unable to authenticate against grafana ingresses.
What you expected to happen:
To be able to authenticate against grafana ingresses
How to reproduce it (as minimally and precisely as possible):

Create a new Shoot

Navigate to grafana-operators or grafana-users host.

Authenticate with the username/password from the corresponding observability-ingress-<hash> or observability-ingress-users-<hash> Secret.

Make sure that the authentication attempt fails with 401 Unauthenticated.

Environment:

Gardener version: 09e7c0528ba4dafa09e5ff53c5ae2b773b864cab
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
Others:

Thanks for noticing this @ialidzhikov!
This was introduced as part of https://github.com/gardener/gardener/pull/5608/commits/3397cb7147a7b9f02fce81a0b85a10c688494100.
It seems the .data.auth value is double base64-encoded (called here: https://github.com/gardener/gardener/blob/09e7c0528ba4dafa09e5ff53c5ae2b773b864cab/pkg/utils/secrets/basic_auth.go#L145 and implemented here: https://github.com/gardener/gardener/blob/ebe812bbee4b4058671e08253890d736855f8241/pkg/utils/encoding.go#L136-L141).
Probably we should change https://github.com/gardener/gardener/blob/ebe812bbee4b4058671e08253890d736855f8241/pkg/utils/encoding.go#L140 to
	return []byte(credentials)

(needs to be verified)

Thank you! I am able to confirm that it now works with your suggestion. In short, looks like previously we needed https://github.com/gardener/gardener/blob/ebe812bbee4b4058671e08253890d736855f8241/pkg/utils/encoding.go#L140 because we passed the Secret value to the helm chart. With #5608 we switched to client-go calls and client-go under the hood takes care to base64 the Secret data values. This is my explanation how we ended with double base64 encoded value.
I noticed that the fix from https://github.com/gardener/gardener/pull/5724 for some reason is not applied to existing clusters. Logic for the Secret data generation is changed and now generates a different value but for some reason the new value is not updated to the existing Secret. For newly created Shoots I can see the Secret data is the correct one. Do you know if this is expected/what might be the problem?

Thanks for taking the time to verify this!
Yes, for existing shoots the secret needs to be deleted and regenerated, so this works as expected. However, it only affects clusters which were already reconciled with the master branch, so the bug/regression was not yet released.


Cluster.split (acg & dcg methods default parameters)

Due to the limitations of acg & dcg methods with default parameters (in complex analysis many bacteria are assigned to "other bacteria" category i.e. proteobacteria), one must consider tuning the setup if the acg will remain the main clustering method.
The issue needs to be further discussed.

I agree. An actual analysis with different values of precision in the cluster.split command must be tested and benchmarked. One of the questions is whether the change of precision value does increase the RAM consumption significantly.

@Setnea Since the problem with other bacteria was recognized with #47 and fixed with #49 I think you can close the issue.


Automating the task of sending some images or wishes to many contacts

We use WhatsApp on our day to day basis. If there is any festival or any special occasion then we use to wish everyone by forwarding some gifs, images or some long messages. Instead of searching and replying to all the contacts we can automate this task with the help of a bot.
With the help of Robotic Process Automation(RPA) using Uipath we can achieve this task and many other sequential task.

Please assign this issue to me. I want to work on this issue.

Done, you have 4 days. If there is no queue you can ask for more days.

I would like to work on this issue. Can it be assigned to me?

@poojasrinivass added to queue

I need few days for solving this issue.

@Antaripa sorry, we have a queue. The issue will be assigned to @poojasrinivass. You can enter in queue again @Antaripa.

@Antaripa assigned again!

I had opened this issue and I know how to do this. I have already done this task, how can u assign it to someone else

Your name will be added in Queue for this issue if @Antaripa is still unable to solve the issue then after the deadline you will be assigned this issue
wait for the deadline date i.e 17th march

@saks1209am assigned!

I will upload the solution as an XML file which can be opened only using Uipath studio. If unable to see the solution i will try to share the video of my solution

I have a .xaml file as a solution to this issue which can be opened using uipath studio only. But it will be very difficult to integrate that file with this cmd software

Can this issue be explained in little detail.

@rpotter12 Can i work on this issue? #GSSOC21

@Aayush-hub Please go ahead.


Change 2019-10-preview to 2019-10-01-preview

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

#sign-off

It is standard practice to group tags by year and month. So the fix is not necessary.


What's the story with the map loading?

It's pretty confusing where to specify the map file to load.
We have server_config.toml, the MapFile string in GameTicker.cs, and a cvar.
Just make it a config file only thing, because as of right now, changing it in the GameTicker and the server_config.toml doesn't stop saltern from loading.

The MapFile String was removed in this commit.
So only the CVar should be the one to define the map.
The server_config.toml just sets cvars.

Discussion? I find this very straight-forward tbh. just edit the server_config.toml that sets the cvars

Imo just keeping it open if someone/swept finds that it really won't read from the cvar or there is some other problem

Not an issue/I don't care.


Add NuSpec

Do you have any information on what the nuspec for UAP is?

Not yet, but win81 should work until we know better.

From: Morten<EMAIL_ADDRESS>Sent: ý3/ý26/ý2015 2:07 AM
To<EMAIL_ADDRESS>Cc: Oren<EMAIL_ADDRESS>Subject: Re: [WindowsStateTriggers] Add NuSpec (#5)
Do you have any information on what the nuspec for UAP is?
—
Reply to this email directly or view it on GitHubhttps://github.com/dotMorten/WindowsStateTriggers/issues/5#issuecomment-86356748.

The only problem marking it as win81 is there will be someone out there that tries to use it in an actual Win81 app :)

Completed


xSQLServer: Fix CHANGELOG.md after recent merge

Pull Request (PR) description

Changes to xSQLServer

Fix CHANGELOG.md after recent merge.

This Pull Request (PR) fixes the following issues:
n/a
Task list:

[x] Change details added to Unreleased section of CHANGELOG.md?
[ ] Added/updated documentation, comment-based help and descriptions in .schema.mof files where appropriate?
[ ] Examples appropriately updated?
[ ] New/changed code adheres to Style Guidelines?
[ ] Unit and (optional) Integration tests created/updated where possible?

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Codecov Report

Merging #889 into dev will increase coverage by 94%.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            dev   #889     +/-   ##
=====================================
+ Coverage     2%    96%    +94%
=====================================
  Files        31     31
  Lines      3436   3436
=====================================
+ Hits         79   3317   +3238
+ Misses     3357    119   -3238


fix redirect on web clients

Description
This PR fixes a bug when using the Iridiuim SDK on mobile clients.
Motivation and Context
It fixes a bug that makes front-end apps seem unresponsive.
How has this been tested?
It's been tested end to end.
Screenshots (if appropriate):
Types of changes

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

Checklist:

[x] My code follows the code style of this project.

This was reviewed given the Ok by jasper via Discord.  We are still working the kinks out in our approval process. 😄


fix: no returns negative size

Suppresses the error that occurs when the width is too narrow.
Before PR, following error is raised.
RangeError: Invalid count value: -1
    at String.repeat (<anonymous>)
    at getHighlights (file:///.../denops/popup_preview/markdown.ts:253:23)
    at async getStylizeCommands (file:///.../denops/popup_preview/markdown.ts:273:22)
    at async DocHandler.showFloating (file:///.../denops/popup_preview/documentation.ts:66:19)

Thank you!


Make createpackage.sh cope more gracefully when run as non-root

Automatically sudos itself if run as non-root.

Just below where the new ensure_running_as_root function is called, the script checks to see if it is running as root, warning and exiting appropriately if it isn't.
The original behavior of warn & exit rather than invoking sudo seems much more well behaved to me, compared to automatically calling sudo if it's not root.  Typically with root privileges it is the responsibility of the user to provide them to the script that needs them rather than for the script to take them for itself (at least in my experience).
I'm leaning towards not making this particular change based on how I'd expect it to behave from most other "root required" scripts, and that it already warns & exits rather than blowing up if not run as root.
@soh, do you have any thoughts?  UX is definitely one of your hot-spot areas.

I agree with Jacob.  I understand the motivation behind this change, but I think it's unexpected behavior for a script to assume root privileges without notification or confirmation.  The simple and common notify/confirm behavior is as Jacob describes:  warn & exit, and allow the user to sudo !!.

I'm closing the pull request since this would cause createpackage.sh to break from common & generally expected behavior for a script that requires root permissions.


Remove docker dependency

The new version of DeckTape uses Puppeteer instead of PhantomJS. So it should be safe to use it without docker. Still a nightmare to install (because of NodeJS version etc.), but might be the path forward.

Thanks! I will have a look at it when I find some spare time. :blush:

@frederik-elwert Docker was removed as a dependency. Markdownreveal now uses Decktape directly underneath to export to PDF. Documentation has been updated:
https://markdownreveal.readthedocs.io/en/latest/subcommands.html#export-to-pdf


Pivot table

Closes https://github.com/OHDSI/Ares/issues/115
Added pivot table to the data quality results component.

Is there a way to filter the data fields available in the list to drag/drop? The columns CHECK_DESCRIPTION, CONCEPT_ID, EXECUTION_TIME, NUM_DENOMINATOR_ROWS, NUM_VIOLATED_ROWS, PCT_VIOLATED_ROWS, QUERY_TEXT, THRESHOLD_VALUE, UNIT_CONCEPT_ID, WARNING, _row, and checkId should be removed.
If you click on the word 'Table' in the top left cell you can change the viewer type, can this be disabled?
Font family varies across the component (verdana) and Ares (Roboto). Can we standardize on Roboto. I prefer no bold text in the pivot view results column.

Yes, we can.
We can disable the type change button but along with all the other interface elements except for the table itself. In this case we will need write separate row and column table constructors.
So the table headers can stay bold?

I don't think they need to be bold. They can be consistent with the overview tab where the background color of the header row is differentiated but the font is not bold.

I don't think they need to be bold. They can be consistent with the overview tab where the background color of the header row is differentiated but the font is not bold.

So, there are two ways to disable the renderer type button:

Just plain disable it, but the cell containing it remains:

Create custom controls:

Which one do you prefer?

The custom controls seem to have a much more integrated appearance.  I prefer them.

Looks great.  Only issue is that the custom control font size is 16px, can you change to 14px?


feat(frameworks): Anu added

I would like to introduce Anu in the frameworks section.
Thanks 🙏🏻
Please Read
Link Submission
Please submit your link(s) to the official Vue.js Awesome List repository (read first their contributing guide).
If they merge your pull request there, it will also be updated in this repository.
But if you really want to add it here, I would still review it.
Bug Fix or New Feature
For bug fixes or new features to this repository, delete this template text and proceed to provide information about the changes introduced in this pull request.
Contribution Agreement
By submitting a pull request to this repository, you are accepting this contribution agreement:

I dedicate any and all copyright interest in this software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

@rmjordas can you review it?

Thank you @jd-solanki 🎉


PTFE-751 bootstrap scheduler for healthchecks run

Codecov Report

Merging #361 (d078b0a) into main (0b4e7fa) will decrease coverage by 21.33%.
The diff coverage is 55.55%.

@@             Coverage Diff             @@
##             main     #361       +/-   ##
===========================================
- Coverage   86.98%   65.65%   -21.33%
===========================================
  Files          25       26        +1
  Lines         845      888       +43
===========================================
- Hits          735      583      -152
- Misses        110      305      +195

Flag
Coverage Δ

api
65.65% <55.55%> (+0.20%)
:arrow_up:

unit
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

runner_manager/scripts/scheduler.py
0.00% <0.00%> (ø)

runner_manager/jobs/healthcheck.py
53.84% <50.00%> (-22.63%)
:arrow_down:

runner_manager/models/runner.py
72.97% <50.00%> (-24.33%)
:arrow_down:

runner_manager/jobs/startup.py
71.73% <78.26%> (-28.27%)
:arrow_down:

runner_manager/dependencies.py
100.00% <100.00%> (ø)

runner_manager/models/runner_group.py
60.25% <100.00%> (-32.06%)
:arrow_down:

runner_manager/models/settings.py
91.83% <100.00%> (-8.17%)
:arrow_down:

... and 4 files with indirect coverage changes


Underscores in emphasized text break output

Hey,
thank you for this great library!
I've noticed an issue with URLs containing _ in hrefs of links inside of s:
const md = '*This is emphasized text with [a link](https://example.com/asdf_asdf.pdf), and another [link](https://example.com).*'
const element = compiler(md)

outputs

  This is emphasized text with [a link](
    https://example.com/asdf
  asdf.pdf), and another
  link.*

(indentation added manually for better readability)
My guess is that because _ also terminates emphasis in markdown the parser gets confused.
Let me know if you need any more information!
Thanks!

I'll take a look, thanks!

Should be fixed in https://github.com/probablyup/markdown-to-jsx/releases/tag/6.6.8

Awesome! 🥇 Thank you so much! 🙏  I can confirm that the problem is fixed!


Fix CRC32 in the initialization header

The definition was copied verbatim from src/cio_file.c, but it
turned out that the byte order was wrong.
We can confirm this by testing the following with Python:
>>> import binascii, struct
>>> binascii.crc32(b"\0" * 2)
1104745215
>>> struct.pack(">I",<PHONE_NUMBER>) # network order
b'A\xd9\x12\xff'

So the initial bytes should be the following
{0x41, 0xd9, 0x12, 0xff}

not:
{0xff, 0x12, 0xd9, 0x41}

Fix the definition thusly.
Signed-off-by: Fujimoto Seiji<EMAIL_ADDRESS>

@fujimotos
The CRC bytes must be in network byte order, so is this solution portable across different archs ?

The CRC bytes must be in network byte order, so is this solution portable across different archs ?

@edsiper I believe it's safe.
Since this patch only touches cio_file_win32.c, and we can safely assume Windows
as a little endian, this must cause no portability issue.

I verified that the fix works for us. Any other concerns not merging it in @edsiper? Thanks!

I verified that the fix works for us. Any other concerns not merging it in @edsiper? Thanks!

thanks!

Hi, do we have any upcoming release scheduled that would include this fix?

Hi, do we have any upcoming release scheduled that would include this fix?

@qingling128 if I am not wrong file system buffer in the windows version won't be available until the official v1.7 release, so this fix is not applicable for v1.6 series

@qingling128 if I am not wrong file system buffer in the windows version won't be available until the official v1.7 release, so this fix is not applicable for v1.6 series

Good to know. We'll stay tuned. CC @sophieyfang

Good to know. We'll stay tuned. CC @sophieyfang


Keyboard shortcut to clear sheet

A keyboard shortcut like e.g. Ctrl + N to clear the sheet would be appreciated.

Hi @Reyhn3,
Thanks for the feedback.  The shortcut you are looking for is already implemented as Ctrl/Cmd + D.  Sorry for lack of documentation on this repo.  I should really invest some time into putting one together for things like these.

Great!
The D-key was not intuitive, but I'll buy it.😃

Ctrl + N was used at some point to open a new calculator window but that functionality was removed due to calculation persistence issues between windows.  Hence , the Ctrl + D :smile:


cl.exe dependency tracking breaks with international languages

Ninja uses cl.exe /showIncludes to figure dependencies, and then filters out the generated compiler spew from the output:
Note: including file: C:\Program Files (x86)\Microsoft Visual Studio\2019\IntPreview\VC\Tools\MSVC\14.26.28801\include\stdint.h
Or, for Japanese users:
メモ: インクルード ファイル: C:\Program Files (x86)\Microsoft Visual Studio\2019\IntPreview\VC\Tools\MSVC\14.26.28801\include\stdint.h
Which Ninja filters using msvc_deps_prefix.
Scenario: A user of EN-US Windows sets Visual Studio to Japanese. Visual Studio sets the VSLANG environment variable so cl.exe will produce error messages in Japanese. For Japanese characters to be preserved in the output of cl.exe, it needs to output UTF-8, which Visual Studio indicates using uses chcp 65001. However, it is then impossible to use msvc_deps_prefix to tell Ninja what the /showInclude message prefix is because rules.ninja must be encoded as ANSI, which in this scenario is the English codepage and cannot represent the Japanese characters メモ: インクルード ファイル.
The result is that Ninja's dependency tracking is broken, and the user sees the /showIncludes spew in the compiler output.
This issue would be resolved by #1671, since it would make rules.ninja utf-8 on Windows.

Potentially related https://github.com/ninja-build/ninja/issues/2167


Revert logback-xyz dependencies to 1.3.1

All logback -xyz dependencies must be reverted to version 1.3.1 in order to use the javax namespace. The 1.4.x versions use the jakarta namespace, which we cannot use at present.

After doing this, dependabot then submitted more new PRs to update the version to 1.4.x and I forgot about this. So need to re-revert the logback dependencies again to 1.3.x.

ok, this was done in release 0.20.0, so I need to create a new issue for 0.22.0


Refactor Cookie handling

Existing now :
@UsesCookie
public void myMethod(RoutingContext context) {
  routingContext.getCookie("bleh");
}

That's probably not consistent with dependency injection used everywhere else.
Keep this annotation if some user just wants to set a cookie but won't read any (and rename it @SetsCookie ?)
Moreover provide another annotation :
public void myMethod(@Cookie("myCookie") Cookie cookie)

If the parameter type is Cookie then simply inject context.getCookie(annotation.value()) else if it's a String inject context.getCookie(annotation.value())?.value()

Done


Automate release to Docker Hub

Split off from #44
Automate release to Docker Hub

There's no demand for this currently. It was out of scope at the launch of the project AFAIK. I'll close the ticket for now.

Closing as "not planned"


Override cluster allocation for agent jobs

Since also agent jobs are using ofcir

cc @zaneb @derekhiggins

@bradmwilliams is there any test that could be run to verify that the patch is ok?


Install Custom CA certs also for existing nodes

How to categorize this issue?

/area os robustness
/kind enhancement
What would you like to be added:
Custom CA certs provided via CloudProfile or Shoot to be installed also on existing nodes.
Why is this needed:
#1515 installed custom CA from cloudProfile/shoot only on newly created nodes, the  reason was that docker daemon had to be restarted to activate the newly installed certs, however restarting docker daemon triggers restart for all containers which was causing issues for the already existing workload. Now, containerd can be restarted without restarting the already running containers, see https://github.com/moby/moby/discussions/46449#discussioncomment-6966822.

/reopen

/remove-lifecycle rotten


Use the nonword tokenizer in Bloodhound search

As we discussed on gitter I had a look at Bloodhound and I used the nonword tokenizer for the datumTokenizer. This makes the search a little more fuzzy and allows to search for only the name of repos as well as for the full name.
Note that typeahead.js caches the search in localStorage so to test this change you have to clear you localStorage.

 You should sign our Contributor License Agreement in order to get your pull request merged.

@bradrydzewski What do you think? Is this ok or do I need to change something?

LGTM

we've moved to the user interface to the drone-ui and switched to a new technology stack and no longer using jquery / bloodhound and instead using react with custom search.


503 Service Unavailable

Hello!
I'm getting 503 when trying to curl -i http://firehose.libraries.io/events

@brainoutsource should be working again now, sorry about the downtime

Thank you!


Bugfix/add underscore

Description
Add an underscore to the built out client executable to fix an issue where UnrealCEFSubProcess.exe is launched by the launcher instead of the intended project.
Release note
Bugfix: Ensure correct exe file is launched in a cloud deployment by adding an underscore to the start.
Tests
(Has been successfully used in local branch for a few weeks now)
Documentation
Updated known issues.
Primary reviewers
@improbable-valentyn @girayimprobable

We'll need to increment RequireSetup also.


Add option to disable root form validation

Some nested forms shouldn't get validated when the root form is.
For example, a small form to add some item to a main form. The small form should only be validated if the add button is clicked, and the form doesn't contain any data used to save the main form.
This will likely be a simple bool on TyneFormFluentValidator to disable the call to RootFluentValidator.RegisterNestedValidator in OnInitialized.

Added in v3.4.0.


Fix Digital take-up report exception when no data

This is happening when running the api locally and there is no data. Nevertheless it's good to handle it better as it may confuse someone not familiar with MTP.

@ushkarev this still happened when running api in main against usual version of mtp-common so I decided to fix it to avoid future confusion.


New provider

Can you add this provider please ?
http://www.torrent.ai/lt/account-login.php?returnto=%2Flt%2Fmain
Thanks

I have no account on that website.

I can send you invitation to create an account
2019-04-17, tr, 21:00 Denis<EMAIL_ADDRESS>rašė:

I have no account on that website.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/elgatito/script.elementum.burst/issues/114#issuecomment-484198027,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALZN7IJHIKOU3CCPONAMD5TPQ5QSBANCNFSM4HEY52JA
.

you can send invite to<EMAIL_ADDRESS>or just leave it here.

Please, check v0.0.36.

Thanks!!!
2019-04-24, tr, 20:56 Denis<EMAIL_ADDRESS>rašė:

Please, check v0.0.36.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/elgatito/script.elementum.burst/issues/114#issuecomment-486360008,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALZN7IJZ3H75AEGQISOJAJLPSCNNHANCNFSM4HEY52JA
.


PWA by default

Hi! Would it be possible to make this PWA by default, like Gatsby? Using Angular for my Website would be so much more exciting, i dislike React.

Closing as duplicate(ish) of #23,
This is already on our radar, but we are investigating first how people are using Scully.
The default Angular service working is only partly suited for our use-case.


Update launch.template.json for new node debugger

Without this, the new debugger won’t respect the “Auto-expand getters” setting, which makes debugging the TS codebase a huge pain: https://github.com/microsoft/vscode-js-debug/issues/447#issuecomment-639619286

This might be unnecessary after the next VS Code release, I'm waiting for clarification at https://github.com/microsoft/vscode-js-debug/issues/447


[HOLD] Send an email if a collection is left in the draft state

Why was this change made? 🤔
Fixes #2285
Note: merging these changes in #2521
How was this change tested? 🤨
CI

Superseded by https://github.com/sul-dlss/happy-heron/pull/2521, closing


[RELEASE] 2024.7.1

Release Checklist
Release details
Scheduled release date - 2024/07/29 2024/07/31
Release captain responsible - @viniciusdc
Starting point - a new release is out

[x] Create this issue to track and discuss the upcoming release.
[x] Use the previous release issue for any final release-specific discussions, then close.

This can be a good time to debrief and discuss improvements to the release process.

Looking forward - planning

[x] Create milestone for next release (if it doesn't already exist) and link it back here.
[x] Triage bugs to determine what be should included in the release and add it to the milestone.
[x] What new features, if any, will be included in the release and add it to the milestone.

This will be, in large part, determined by the roadmap.
Is there a focus for this release (i.e. UX/UI, stabilization, etc.)?

Pre-release process

[x] Decide on a date for the release.

What outstanding issues need to be addressed?
Has documentation been updated appropriately?
Are there any breaking changes that should be highlighted?
Are there any upstream releases we are waiting on?
Do we need to update the dask versions in the nebari-dask?
Will there be an accompanying blog post?

[x] Prepare for the release.

[x] Update the nebari upgrade for this release

[x] Add upgrade messaging including deprecation warnings, version specific warnings and so on.

[x] Include DigitalOcean deprecation warning in Upgrade command

[ ] Announce build freeze.
[x] Release Candidate (RC) cycle.

Is this a hotfix?

[ ] Create a new branch off of the last version tag.

Use this branch to cut the pre-release and the "official" release.

[ ] git cherry-pick the commits that should be included.

[x] Perform end-to-end testing. Use the Testing Checklist template.

For minor releases, relying on the end-to-end integration tests might suffice.

[x] Cut RC via GHA release workflow (w/ "This is a pre-release" checked).
[x] End-user validation.

If possible, pull in volunteers to help test.
(Repeat steps if necessary)

[x] Update RELEASE.md notes.

Cut the official release
If there were changes to the following packages, handle their releases before cutting a new release for Nebari

[ ] Cut PyPI release for nebari-workflow-controller
[ ] Cut PyPI release for argo-jupyter-scheduler

These steps must be actioned in the order they appear in this checklist.

[x] Tag, build and push docker images
[x] Update and cut release for nebari-dask meta package on Conda-Forge.
[ ] Update CURRENT_RELEASE (and any other tags) in the constants.py
[ ] Cut PyPI release via GHA release workflow.

Avoid appending v to tag.

Copy release notes from RELEASE.md.

[ ] Merge automated release PR for nebari on Conda-Forge.
[ ] Merge release branch into main

@viniciusdc I assume this can be closed


Server and client in sync loop, using up server CPU

The Telegram bridge (the only one I'm currently using) and the client (both SchildiChat and Element do this, I haven't tried any others) get into a loop of network requests.
The synapse process on the server is consuming about 63% CPU, and the mautrix-telegram python process is consuming about 17%.
Here is a trimmed version of the logs, with the request, response code, and the first part of the user agent to tell which is the server and which the client.
logs.txt
If you need full logs, or logs collected some other way, let me know.

maybe https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2664


Idea: Add podping button to podcast pages?

Would it make sense to add a podping button to the individual podcast pages. I think that would make it easier for podcasters to request podpings of their feeds.

It would probably need to be heavily Captcha'd to keep from being abused.  Maybe also the button is inserted into the DOM after the fact by scripting so that it doesn't show up to naive scrapers.  If anyone else has thoughts on this please let me know.


feat: initial steps allow image embeddings

I would like to start the discussion about the possibility to add Image as an Input to the Embedding route.
I guess it would also need the llama.cpp runner to be able to handle it, for which I still need to look at.
Also, I would like to know if batch embeddings is something you would consider adding.
This PR would only be a first step in that direction doing a small refactoring and adding the Image to the Embedding Request.

Thanks for taking the time to post a PR. I noticed you've made some changes to server.cpp, so I wanted to let you know that we're about to merge another PR (#5034) to begin replacing that code with a new Go based equivalent. The goal of this is to add more unit testing and fix some long standing stability bugs while preserving vision model support. If you need help rebasing your PR don't hesitate to contact us by replying here.


The Coleshill School

Pull req to add my school

School URL: https://www.thecoleshillschool.org/
IT Course (2 years) https://www.thecoleshillschool.org/sixth-form/application-page-sept-2021#collapse14 and https://www.thecoleshillschool.org/uploads/PDF/sixth-form/Sixth-Form-Options-September-2021-FINAL-VERSION.pdf (page 22)
Screenshot of the domain being used for emails (all students receive an email account upon enrolling: https://i.imgur.com/DAzViuE.png

School URL: https://www.thecoleshillschool.org/
IT Course (2 years) https://www.thecoleshillschool.org/sixth-form/application-page-sept-2021#collapse14 and https://www.thecoleshillschool.org/uploads/PDF/sixth-form/Sixth-Form-Options-September-2021-FINAL-VERSION.pdf (page 22)
Screenshot of the domain being used for emails (all students receive an email account upon enrolling: https://i.imgur.com/DAzViuE.png

@hypewsthedev Pull request merged. Thank you!

@hypewsthedev Pull request merged. Thank you!


[BEAM-1347] Convert an InputStream into an Iterable using the Beam Fn data specification

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

This is towards sharing common code that supports the Beam Fn State API and the Beam Fn Data API.

R: @vikkyrk

retest this please

retest this please
Last failure run was unrelated: https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/13854/

retest this please

Coverage increased (+0.003%) to 69.967% when pulling a936b509b755c88c77f4fffe2c120bebed4a6cff on lukecwik:state_api into d03a1284c51cbf39116f4cd91ebb405623cecfa2 on apache:master.


NO TICKET: Fix key deserialization

This PR fixes both bincode encoding and human readable JSON encoding for Keys used in the trie.
Further property tests are also introduced.

bors r+


W&G Die Roller v2

This change is to the readme, json, and js files.
Specific changes:

Updated layout of output.
Added ability to total DR and Successes for total damage.

Note: All files converted to Unix EoL file format and a new contributor added.

@clevett I tested out the sheet and die roller and got the following on the die roller on the load; obviously it does not work.
Spinning up new sandbox...
Failed to load WH40k Wrath & Glory Die Roller
No such file or directory @ rb_sysopen - /home/symbly/www/d20-app/apiscripts/Wrath And Glory/2.0/WrathAndGlory_DieRoller.js
"Starting webworker script..."
"Loading 0 translation strings to worker..."

Greetings @bts1967
This should be fixed now. It was missing the appropriate directories for versioning. I detailed the changes here.
Thanks,
Cassie


Fix typo in Reducers.md

Hi @alexcho617, thanks for the PR, but I don't think this quite the right fix.
I just opened https://github.com/pointfreeco/swift-composable-architecture/pull/3085 to fix a bunch of references in the docs, including this one. I am going to close this for now.


fix: use weak self in city guide, fix memory leak

The type of this PR is: fix

This PR resolves []
Description

Fixes a memory leak causing citySelection not to work on subsequent entries to cityGuide

TODO: there still is an issue with the selectedCity not being updated correctly on RN side that needs to be resolved before this can be merged.
PR Checklist (tick all before merging)

[ ] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have tested my changes on iOS and Android.
[ ] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[ ] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added an app state migration, or my changes do not require one. (What are migrations?)
[ ] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against 403b5b5740724722cecf56a2b83664581c9fe987


Remove badges on folders when you click into them

@keybase/react-hackers

Adding or deleting a KBFS favorite was causing a navigateUp() in those sagas.  I moved the navigation outside of the sagas so that we can use them here without navigating.

We want to remove the "new" badge on a KBFS folder when you click on it in Folders, but!  Turns out that the way to remove the "new" badge is to add the folder as a favorite, and our concept of "Unignore folder" is a mapping onto adding it as a favorite -- that's how you unignore a folder.

So if we added a favorite every time we clicked on a folder, we'd keep unignoring that folder every time we clicked.  So we have to check that it's unignored, and that's it's "new" (to avoid unnecessary server round trips while you're clicking around) before favoriting it.

i don't think we want to favorite it if you go in. i think the core side has a way to set this w/o favoriting

@mmaxim, what do you think?

Favoriting is the current way. With the FS mount, if you go into the folder, you favorite it. Seems reasonable here as well, especially since there is a call to action on the screen you land on.

Thanks.  @chrisnojima?


Docs missing hint for docker compose up achgateway example

https://moov-io.github.io/achgateway/usage/docker/
is missing the hint that the main readme.md has about
# Inside of ./examples/getting-started/

Thanks!


Add some explanations to the "width" and "slit_width"?

Hi, since there are multiple expressions of the Gaussian width used in Solar physics (e.g., sigma, 1/e width, and FWHM), would you like to add some explanations about the "width" used in the user's guide? Because it takes me some time to figure out that the fitting returns the sigma width. And I also noticed that the "slit_width" restored in the data_cube.meta is in FWHM (I guess because it is calculated from the SSW eis_slit_width.pro). Though the "slit_width" is not used in EISPAC, it might be better to remind the users to avoid confusion.

Hello, that is a good point! I will add the definition when I next update the docs. For what it is worth, we are using the sigma widths, which is the standard for EIS data.
You are correct, the "slit_width" metadata is not currently used by EISPAC. It is included mostly for completeness and user reference. I don't think it is technically the FWHM, but I could be mistaken. I will look into it and update the documentation accordingly.
Thanks for using EISPAC!

Please address this as part of the JOSS review: https://github.com/openjournals/joss-reviews/issues/4914


Wrong output If a first character in a paragraph of the HTML is

There is a bug, where if the first character in
 in HTML is , it outputs wrong HTML. Basically I am trying to use the library to convert string HTML from RichText into a raw HTML in my page.
import React from "react";
import Markdown from 'markdown-to-jsx';

const markdownText = `<p><strong>Test</strong>asda sdasd asd asd asd as d</p>`;

export default function App() {
  return (

      <Markdown>{markdownText}</Markdown>

  );
}

this outputs to:

Test
asda sdasd asd asd asd as d

instead of

Testasda sdasd asd asd asd as d

It basically nests the paragraphs which is invalid and creates errors in console.
If I change it to:

Testasda sdasd asd asd asd as d

it correctly outputs to:

Testasda sdasd asd asd asd as d

I've encountered the same problem, and I believe it applies not only to strong but probably to every inline tag, as the same occurs for

Lorem ipsum dolor sit amet

It also started happening only from 7.5.1, in older versions this did not occur.

I've encountered the same problem, and I believe it applies not only to strong but probably to every inline tag, as the same occurs for

Lorem ipsum dolor sit amet

It also started happening only from 7.5.1, in older versions this did not occur.

Not just "inline tags". Rather, anything that looks like this:

text more text

  ^^ the first child of the
 is a  and will result in:

text

more text

text more text

  ^^ the first child of the
 is a  and will result in:

text

more text

<CustomComponent /> more text

  ^^ the first child of the
 is a <CustomComponent> and will result in:

<CustomComponent />

more text

<Tag><Tag /> more text</Tag>
    ^^ the first child of the <Tag> is a <Tag> and will result in:
       <Tag><Tag /></Tag>
       <Tag>more text</Tag>

When a text character is placed before the first child will render without issue:

beginning text text more text

  ^^ the first child of the
 is plain text and will result in:

beginning text text more text

beginning text text more text

  ^^ the first child of the
 is plain text and will result in:

beginning text text more text

beginning text <CustomComponent /> more text

  ^^ the first child of the
 is a <CustomComponent /> and will result in:

beginning text <CustomComponent /> more text

<Tag>beginning text <Tag /> more text</Tag>
    ^^ the first child of the <Tag> is a <Tag /> and will result in:
    <Tag><Tag /> more text</Tag>


Bumped development RELEASE for 1.22-14

Bumped development RELEASE for 1.22-14
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/unhold


Default Variables for Sass Mixins

Continuing on from #64. Suggestion and quoted content attributed to @cbirdsong.
The proposal suggests that the mixins should include default variables to reduce repetitive code and become more manageable.
e.g. $fontsourceDisplay: swap !default; or $fontsourceWeight: 400 !default;.

For defaults, relying on the mixin arguments is fine for things that are likely to change each time you call the mixin, but it seems really unlikely you'd change font-display, file path and character set for each individual typeface. That feels like an advanced feature and it's good the mixin allows for it, but it introduces a lot of repetition.
I imagine the far more common scenario is someone deciding "we're using font-display: optional; and keeping our compiled files in /dist/", and those people have to repeat those instructions to each "@include fontFace` over and over again. Compare these two code blocks:

@use "@fontsource/open-sans/scss/mixins" as OpenSans;
@use "@fontsource/barlow-condensed/scss/mixins" as Barlow;

@include OpenSans.fontFace($fontDir: "/dist/node_modules/@fontsource/open-sans/files", $display: optional);
@include OpenSans.fontFace($fontDir: "/dist/node_modules/@fontsource/open-sans/files", $display: optional, $style: italic);

@include OpenSans.fontFace($fontDir: "/dist/node_modules/@fontsource/open-sans/files", $display: optional, $weight: 700);
@include OpenSans.fontFace($fontDir: "/dist/node_modules/@fontsource/open-sans/files",  $display: optional, $weight: 700,  $style: "italic");

@include Barlow.fontFace($fontDir: "/dist/node_modules/@fontsource/barlow-condensed/files", $display: optional, $weight: 600);
@include Barlow.fontFace($fontDir: "/dist/node_modules/@fontsource/barlow-condensed/files",  $display: optional, $weight: 600,  $style: "italic");

@use "@fontsource/open-sans/scss/mixins" as OpenSans;
@use "@fontsource/barlow-condensed/scss/mixins" as Barlow;

$fontsourceDir: "/dist/node_modules/@fontsource/"
$fontsourceDisplay: optional;

@include OpenSans.fontFace($weight: 400, $style: normal);
@include OpenSans.fontFace($weight: 400, $style: italic);

@include OpenSans.fontFace($weight: 700, $style: normal);
@include OpenSans.fontFace($weight: 700, $style: "italic");

@include Barlow.fontFace($weight: 600, $style: normal);
@include Barlow.fontFace($weight: 600,  $style: "italic");

The second way leads to much more maintainable code than the first. You can understand what typefaces are being loaded at a glance*, adding another weight is a simple copy/paste, and modifying the file path requires editing only a single line.

Released in 4.2.0.

@DecliningLotus Just opened https://github.com/fontsource/fontsource/issues/153 - a few suggestions there on how to fix the problem introduced by these changes


[azingest] remove deprecated code

Removing the deprecated azingest module. Use `sdk/monitor/ingestion/azlogs' instead.
Part of https://github.com/Azure/azure-sdk-for-go/issues/22377

/azp run go - azingest - ci

/azp run go - azingest - ci


Deploy Commerce Mock Application in the Kyma Runtime

Tutorials: https://developers.sap.com/tutorials/cp-kyma-mocks.html
Hello,
in step 2 of the tutorial a namespace "dev" is to be created.
Open the Kyma console and create the dev Namespace by choosing Add new namespace, providing the name dev, and choosing Create.
It would be great to mention here, that if the namespace is called any different than dev, the apps will not work / environment variables have to be adjusted.
Thanks
Daniel

Hi Daniel,
Thanks for the feedback. Can you help me understand why you didn't use the name dev as listed in the instructions?
Regards,
Jamie

Hi Jamie,
we share a kyma environment for the team, so after one colleague has done
the tutorial, the namespace is already taken and can not be done by another
person.
Also, usually in such tutorials the naming is not so important meaning I
don't need to name artefacts exactly similar to the tutorial. I expected
the name of the space to be similar to e.g. a project name as I didn't know
this influences the URLs later.
Thanks
Daniel
Am Fr., 4. Feb. 2022 um 15:27 Uhr schrieb Jamie Cawley <
@.***>:

Hi Daniel,
Thanks for the feedback. Can you help me understand why you didn't use the
name dev as listed in the instructions?
Regards,
Jamie
—
Reply to this email directly, view it on GitHub
https://github.com/sap-tutorials/Tutorials/issues/18064#issuecomment-1030038050,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC47DHJUKRIGWNFVKZ73XYDUZPO6VANCNFSM5M5SWESQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok, I'll enter some text to indicate so. It will be made available in the next few weeks.


Fix dspy chain of thought doc

Seems like the hint is not required for vanilla Cot?
https://dspy-docs.vercel.app/docs/cheatsheet#dspychainofthoughtwithhint
Happy to open a PR for the fix, seems minor. Any recommended workflow for that?

Thank you! What are you trying to fix? Looks OK to me

Hey!
dspy.ChainOfThought
and dspy.ChainOfThoughtwithHint
have the exact same docs!
My guess was that the former does not need the hint variable?

We don't end up passing the hint. So it is kind of confusing for the standard CoT

ah got it! thanks so much @adityalahiri , fixed in the folder docs/ , but not sure how fast this will propagate to the site4


Runtime issue

I can build main branch, but something prevents game from launching (after clicking "Launch Northstar").

Logs are of no help.

I could build branch v1.9.4 and use it with no problems.

Are you building Debug or Release mode?
Also, what happens if you try running the CI build from newest commit?
https://github.com/R2Northstar/NorthstarLauncher/commit/7aa2008ea5a38f66a0b25bb23fa35db6fc2d1d16

I tried building and using 7aa2008ea5a38f66a0b25bb23fa35db6fc2d1d16 with both debug and release modes, to no avail; both compile correctly, but after putting dll + exe in game folder, game gets stuck once I click "Launch Northstar".

What happens if you use the CI build of most recent commit?
https://github.com/R2Northstar/NorthstarLauncher/actions/runs/2982633093

Oops, didn't get your message at first :)
Same result while using CI build:

I asked a friend of mine to build on his computer and send me build results, I used them and got the same result.
I'll check tomorrow if I can identify the breaking commit.

I asked a friend of mine to build on his computer and send me build results, I used them and got the same result.
I'll check tomorrow if I can identify the breaking commit.

Yeah, if anything I believe that unless the issue actually is with some change with Launcher code, the issue is outside of NorthstarLauncher and Northstar.dll.

I tested both using CI builds and building from main commits myself, I couldn't get to a stable result: builds can work for a few launches, then stop working with no reason.
Seeing that I can't run https://github.com/R2Northstar/NorthstarLauncher/pull/237 while I successfully reviewed it (on another computer) makes me indeed think of a system-related issue.
I'll check on my desktop computer asap.

Launching NorthstarLauncher.exe directly instead of launching through Viper seems to solve the issue.
Highly suspecting a #271 duplicate now :)

Issue totally due to Viper.


GPG tests not runnable on Windows

I tried to fix a bug in signing project.
Therefore I first wanted to write a failing test.
Therefore I first wanted to run a successful test.
So I tried to run org.gradle.plugins.signing.SigningTasksIntegrationSpec#out-of-date when signatory changes.
Unfortunately this test fails on Windows.
I have gpg2 available on my path, so the @Requires is satisfied.
But when the test tries to do Files.createSymbolicLink in org.gradle.plugins.signing.GpgCmdFixture#prepareGnupgHomeSymlink this fails with
java.nio.file.FileSystemException: C:\Users\bkautler\AppData\Local\Temp\tfy2p: Dem Client fehlt ein erforderliches Recht.

	at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:92)
	at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103)
	at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108)
	at java.base/sun.nio.fs.WindowsFileSystemProvider.createSymbolicLink(WindowsFileSystemProvider.java:581)
	at java.base/java.nio.file.Files.createSymbolicLink(Files.java:1058)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at org.gradle.plugins.signing.GpgCmdFixture.prepareGnupgHomeSymlink(GpgCmdFixture.groovy:77)
	at org.gradle.plugins.signing.GpgCmdFixture.setupGpgCmd(GpgCmdFixture.groovy:55)
	at org.gradle.plugins.signing.SigningIntegrationSpec.setupGpgCmd(SigningIntegrationSpec.groovy:64)
	at org.gradle.plugins.signing.SigningTasksIntegrationSpec.out-of-date when signatory changes(SigningTasksIntegrationSpec.groovy:111)

Probably because it cannot create symlinks.
Would be nice if this maybe could changed somehow do work-around the 108 characters limit in a different way than using symlinks, for example by copying the files to the directory instead of symlinking or similar.
Acutally, as my gpg2 is from Cygwin, the next problem then is, that an absolute Windows path is used, which also then will not work. :-(

Same still happens in latest master

Sorry for the late reply
Thank you for providing a valid report.
The issue is in the backlog of the relevant team, but this area of Gradle is currently not a focus one, so it might take a while before a fix is made.


Chore: Remove yarn.lock file

Related issue: https://github.com/grafana/grafana/issues/40764

Closing this PR in favor of https://github.com/grafana/grafana/pull/42663


[Bug] browse_multiple contents lost on validation failure related to other fields

Bug report
What I did
Created a CRUD form which contains a series of fields including, for example, title and attachments.
title is a text field, and is required.
attachments is a browse_multiple field, and has no validation rules specified whatsoever.
(The attachments field may or may not contain any selections on any given create or update operation, i.e. it is entirely optional at all phases.)
What I expected to happen
After submitting the form, if title validation failed, the contents of the browse_mutliple field would be unchanged.
What happened
When validation fails on title, the form reloads without any of the contents of the existing browse_mutliple field. The attached items are lost whenever a validation error occurs on another field.
What I've already tried to fix it
I've looked at the various existing issues regarding validation of multiple upload fields (including #4073/#4080 and #3781), but these seem to slightly miss the mark in that I'm not trying to validate the browse_multiple field.  But perhaps they point to the source of some issues re: whether or not 'unchanged' fields get re-POSTed.
Is it a bug in the latest version of Backpack?
Yes
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
PHP 7.4.3 (cli) (built: Nov 25 2021 23:16:22) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Zend OPcache v7.4.3, Copyright (c), by Zend Technologies
    with Xdebug v2.9.2, Copyright (c) 2002-2020, by Derick Rethans

### LARAVEL VERSION:
v8.78.1@16359b5ebafba6579b397d7505b082a6d1bb2e31

### BACKPACK VERSION:
4.1.63@c3a09d64090cc15c51df7898889d763aaa335260

Hello @tibbsa
I think that is problem with our old() mechanism that is fixed in 4.2 already but it's totally a breaking change for 4.1.
In 4.2 I cannot reproduce your issue: https://recordit.co/3XRtFnWTlP but I could in 4.1.
So, I will leave this open until I got some time to look at this field and try to fix it in a non-breaking way in 4.1, in the meanwhile if you are going to fix this yourself and are willing to send a PR for it, we would really appreciate.
Sorry can't be more help at this moment.
Best,
Pedro

Hey @tibbsa good news.
We launched today Backpack v5 that has this fix as I mentioned. Check out the upgrade guide
There are some breaking changes, but it should not take much time to upgrade.
I will be closing this issue, let me know if you have some trouble upgrading.
Wish you the best,
Pedro

@pxpm: Upgrading will be a little trickier with half the project now in a closed source repo, which I can't as easily clone it to develop the local patches needed. In my case, #3480 is a blocking issue for screen reader accessibility, and so now those label issues span both backpack/crud and backpack/pro.... But I will see what can be done.

Hey @tibbsa that label issue is on the roadmap to be addressed. We take acessibility very consciouly here. It just need a little tinkering on how to implement, because label for is supposed to have a matching ID, so we need to think in a way to assure we don't have duplicate id's even if inside repeatable fields, or inside inline modals etc. Maybe we need to resort to random id's or something alike to guarantee uniqueness in all those scenarios.
Now that we launched we have more time to work on this "minor" issues. We will be working in some of the most requested features as per the pool @tabacitu created and some others we see fit.
I get the trouble you are in, I will talk @tabacitu about this to see what kind of priority he thinks this should be given, maybe he thinks this is more important than I do, don't get me wrong, I get the importance of it, but also think there are other things more important left to do. But if @tabacitu thinks different he's usually rigth about it, so ... lets see.
About the fix for this in 4.1 I don't think it will ever happen, it was one of the big breaking changes from 4.1 -> v5.
Sorry can't be more help here for the moment.
Pedro

If I understand, it's not possible to 'git clone' backpack/pro now, is it? I could "fix" it for my current use case -- we are not using repeatable's -- but tracking upstream and re-applying that branch when backpack/pro upgrades come along is the trick.

Indeed not, but if you have the licence purchased and have some special need regarding that, please shout an email to @tabacitu explaining your situation, he migth be able to work something out until we fix that label issue.
<EMAIL_ADDRESS>Cheers


Fix #15699

Snapshot stored with reference name:
refs/pull/15711/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15711/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15711/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15711/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15711/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15711/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15711/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15711/merge#BCU1XR#0

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15711/merge/testResults/webgpuplaywright/index.html

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15711/merge/testResults/webgl2playwright/index.html


Unable to add events to calendar with plugin version 3.0.0

Just updated to version 3.0.0 and I'm unable to save a new event.
Got this error message:
type 'NoSuchMethodError' is not a subtype of type 'Exception'
in DeviceCalendarPlugin.createOrUpdateEvent (package:device_calendar/src/device_calendar.dart:202:54)

recently started using this one, thanks for all contributors
flutter: persmission is granted
[VERBOSE-2:ui_dart_state.cc(157)] Unhandled Exception: NoSuchMethodError: The getter 'name' was called on null.
Receiver: null
Tried calling: name
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:53:5)

using this ^3.0.0+3 version what is the temporary workaround? which version I should use? I'm using _deviceCalendarPlugin.createOrUpdateEvent only!


Relax glthread assertion for loadTexture() and loadCubemapTexture()

Now textures can be constructed in non-GL thread. GL commands are deferred until binding (e.g., getId()).

Fixed in https://github.com/Samsung/GearVRf/pull/432

Can this be closed now?

@danke-sra Do you think we can close this now?

Yes, please close it.


Minimum Number of Operations to Move All Balls to Each Box [LeetCode Medium]

Please assign me this in cpp.
Leetcode problem number #1769.

@Samarth-Gupta-2909 Assigned in C++


[bug] Unable to deploy image

Error encountered
...
ERROR: failed to solve: process "/bin/sh -c pip install --upgrade pip &&     pip install ." did not complete successfully: exit code: 1
Error: buildx failed with: ERROR: failed to solve: process "/bin/sh -c pip install --upgrade pip &&     pip install ." did not complete successfully: exit code: 1

Workflow run for reference.
Expected behavior
A new version of the cnb-tools package should be available.

After some sleuthing, I suspect that alpine may be too minimal.  Building with slim worked locally, so will be pushing this fix.

Confirming that the latest push has fixed the issue - v0.3.1 now available!


NLog: Improved default JsonSerializerSettings, and reduced allocations

Convert enums to their string-value (instead of integer value)
Do not throw exceptions on cyclic reference loops
Skip JToken code-path for simple types that converts nicely to Protobuf
Reuse the JsonSerializer instead of allocating new for every property

Still missing the ability to not serialize the whole world to an infinite depth.

Thanks for the PR. I'm currently on vacation, so will look at this in detail then I return in a week or so.

@chrisdunelm Have updated the PR according to your review comments.


Add BaggageRestrictionManager

Using the "strategy" pattern as seen in the Java client.

Coverage increased (+0.2%) to 85.533% when pulling 5e8676bf6fefa682fb7d3900fb0e4da4fa2d6bc1 on baggage_good into 2df69f0e5f60d6a8fb6d5c1c405caa9d6b16d447 on master.

Coverage increased (+0.2%) to 85.533% when pulling b2ab63f1f9abe5bfc42e6c164cdd0a258ba3c3ab on baggage_good into 2df69f0e5f60d6a8fb6d5c1c405caa9d6b16d447 on master.

Coverage increased (+0.2%) to 85.393% when pulling 9394a154d133741d53ab1aee1e77318ab9847d09 on baggage_good into 88fe15c916404e600f673ad457f2a4baec91e5d3 on master.


Source control does not update status automatically

Issue Type: Bug
Git integration does not update status automatically.  When I change files 'source control '  does not react to any file changes, it does not show that there are changed files.
But if I click on 'refresh' icon it loads the changes correctly.
I know there is another similar issue when files are changed not with VS Code.
This is not that case. Files were changed using VS Code.
VS Code version: Code 1.21.0 (9a199d77c82fcb82f39c68bb33c614af01c111ba, 2018-03-07T11:01:43.521Z)
OS version: Linux x64 4.8.0-34-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz (4 x 3600)

Load (avg)
0, 0, 0

Memory (System)
11.61GB (1.30GB free)

Process Argv
/usr/share/code/code --unity-launch

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

vscode-intelephense-client
bme
0.8.8

laravel-goto-view
cod
1.2.0

vscode-eslint
dba
1.4.7

gitlens
eam
8.1.1

vetur
oct
0.11.7

laravel-blade
one
1.17.0

laravel-5-snippets
sac
2.0.1

Reproduces without extensions

Does the file explorer react to file changes?

Yes.

I've been experiencing the same issue since the 1.21.0 update. After I commit changes, the files still show in the staged area and the little badge over the source control icon in the nav also still displays, even after hitting the manual refresh. I've been having to quit the program and re-open to get it to update. File changes show correctly in the file tree.
One thing I haven't really considered/explored—I still perform most Git operations through the command line. I use the Source Control mainly for reference or to more easily break apart a lot of file changes to smaller commits after I've gotten too deep. I don't know if that may be causing a disconnect/delay in the update process. But I've usually waited a few minutes and still experienced the issue.
VSCode: 1.21.1
OS: Mac OS Sierra 10.13.3

I cloned second copy of one of my repositories to my workstation (don't ask), and discovered similar behavior when using VSCode to look at files in the new copy. The first copy was working fine. It looks like VSCode wasn't checking the repo when saving files. Modified files were not showing as modified in the file explorer, even after forcing a refresh from under Source Control.
When I create a .code-workspace file for the second repository, that seemed to fix things.
VSCode: 1.21.1
OS: Windows 10 Enterprise 1703

cc @bpasero File event problems.

Very likely related to #3025

Ever since I saw the above error about file handles I've been having similar issues.
For me is more like the trigger for the git source control "changed files list" to update isn't the saving of the files as it use to be. Instead its when I click on them or refresh the source control actively. Even then it seems to be hooked up to wait until the build is completed before displaying the changes. Which in our large angular app is quite a while more than a few seconds.
so things are working its just sometimes I'm stuck waiting for the list to properly update and reflect my changes before I can commit.

I am also facing the same issue. File changes are not at all being identified in the source control even after clicking the refresh button.
VS Code Version - 1.24.1

In my current setup, since the june update, most of the time my files in the tree are not updated, they show no SCM change when commits are pending. The folders usually do.
Since the last update, after commiting, the files themselves in the code editor are not updated, with a file showing "changes" since last commit when there's nothing pending:

I have the same issue and in my case (monorepo using lerna and yarn workspaces) I have identified what is causing the issue.
It seems that when monorepo packages (node modules) within the repo are symlinked into ./node_modules/ through the lerna bootstrap process, git status -z -u and friends (as seen in the Git log Output panel) are no longer called on file changes.
I verified this by manually deleting the symlinked modules from ./node_modules/<symlinked-packages> and (after restarting code) all file changes caused git status -z -u and friends to be called again and changes were reflected within the workspace tree.
See lerna for monorepo details but I think this is not lerna or monorepo specific and is probably due to symlinks within ./node_modules although I have not verified this outside of my monorepo case.
Code-Insiders version info:
Version: 1.26.0-insider
Commit: e8b1ee0b4d016bc38bbc1cf06d6d1868760d5fe8
Date: 2018-07-26T05:19:02.094Z
Electron: 2.0.5
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

I just had the same issue. The source control tab suddenly became irresponsive and I have to add the files using the command line and push them to repo.
However, I deleted my local repo and cloned the remote again and it started working again.

I'm having the same problem as @LeoLozes but my source control view works fine. Should this be a new issue?

Symlink support: #5970
Git repo root not the same as open folder: #41085
@Lev09 Is this still an issue for you?

@joaomoreno after getting few updates that problem seems to be solved for me.
Now I am using following version of VSCode
Version: 1.27.2
Commit: f46c4c469d6e6d8c46f268d1553c5dc4b475840f
Date: 2018-09-12T07:11:15.873Z
Electron: 2.0.7
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64


Readme improvments

The idea is to have a more appealing README for the next release.

@cmoissar, @vgenot do you have any notebooks we could add to the Speasy gallery :) ?
That would be nice to add some more realistic use-cases here https://speasy.readthedocs.io/en/latest/examples/index.html.

Working on it!
On Fri, 27 Oct 2023 at 09:57, Alexis Jeandet @.***>
wrote:

@cmoissar https://github.com/cmoissar, @vgenot
https://github.com/vgenot do you have any notebooks we could add to the
Speasy gallery :) ?
That would be nice to add some more realistic use-cases here
https://speasy.readthedocs.io/en/latest/examples/index.html.
—
Reply to this email directly, view it on GitHub
https://github.com/SciQLop/speasy/pull/104#issuecomment-1782552383, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGIQQK4772NAOVYZDAPW6MTYBNZRJAVCNFSM6AAAAAA6RPNYGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBSGU2TEMZYGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@nicolasaunai you can check the readme for the wording as we discussed about the introduction that was not user friendly.
@brenard-irap if you can review examples notebooks with @vgenot and also the new readme that would be awesome.


MID0038 - Select Job Invalid Data

I wanted to test the Library You created as it could help me a lot in project that I'm helping to my friend to work with the Ingersoll Rand  Controller and in general all is working great except I can't select the job, I'm receiving message Invalid Data all the time. I checked the message that is being send and it is "00240038009" for JOB ID 9 bu when I check the Opent Protocol specification there is mentioned that 0024 mean that this is a Revision 2 so from the documentation it should be maybe 4 digits for the job ID  and maybe the proper message should be "002400380009"? Maybe this is somehow controlled by some option or it is a matter of the Controller that I configured wrong but can you take a look and help me with figuring this out?
Thank you in advance.

Hello @URSIRob, thanks for submitting it.
The problem is with the code, since the breaking changes of the version 6.0.0, all constructors that set datafield were removed.
In SendJobCommand.cs:
https://github.com/Rickedb/OpenProtocolInterpreter/blob/d082e88a94a23124cc73d3c83a06f4a9ef3caf02/sample/OpenProtocolInterpreter.Sample/Driver/Commands/SendJobCommand.cs#L16-L29
The new Mid0038(jobId) is calling the Mid0038(int revision) constructor and setting the revision as 9, not the Job Id and that's why it's messing up.

Thank you. After your fix It's working great, thanks to your comment I understood it better. Great job, one more time thank you!


raft: introduce/fix TestPreVoteWithCheckQuorum

raft: set leader id to none when becomePreCandidate.
When a follower election timeout, it should mark leader to none (so that old leader is not in lease).  Current implementation of Pre-Vote ignore this, which may cause wrong judgement .

@javaforfun can you add a test case?

@xiang90 done. add two test

seems confusing when raft recv a message with higher term, we will create a new pr for this

@bdarnell
can you take a quick look too?

I've updated this pr,  please take a look. @xiang90 @bdarnell

I've found another interesting scenario for Pre-Vote together with checkQuorum.

cluster have 5 nodes [A, B, C, D, E], with leader A, all terms are 1.
network partition happen, cluster have two partition [A, B],  [C, D, E].
so [A, B] has leader A with term 1,   [C, D, E] has leader C with term 2.
A will checkQuorum after election timeout, and become follower, set leader to None with term 1.
B start pre election, but B has leader = A with term 1.

it's strange that one node think another node is leader,   but the other node is not leader,  and they are in same partition!
so if leader can become follower, and change r.lead to none with term not changed,   follower also can do this.

CheckQuorum can prevent disruptive servers, which described in thesis section 4.2.3.

it seems Pre-Vote is good for network jitter. For example.

Assume cluster have 3 nodes [A, B, C], the network between C and A,B is not stable, the link will jitter every hour.
If without Pre-vote, node C will election periodically to make the cluster leader step down. But if with Pre-Vote, node A/B will work as node C cannot increase term to step down cluster leader.

checkQuorum seems good for disruptive server which had been removed from the cluster, but it's resolved the issue from network jitter.
So it's good to enable both checkQuorum and Pre-vote.

So is this ever going to get merged? We've hit this issue in production, where with checkQuorum and preVote activated we are in an endless loop of ignoring MsgPreVotes. 3 nodes. Leader goes down. Other two endlessly try to PreVote and keep ignoring each other. The randomization in "pastElectionTimeout" which I think is supposed to prevent this is not working.

No, that is not what I am seeing. In that scenario, B and C grant each other's votes. In my scenario B ignores Cs vote and C ignores B's vote. Also, we have that change in the version we are using. I am fairly confident we are seeing the issue described here related to the lease not expiring.
So I am wondering if we can get these changes merged as they are fairly small, and have been sitting here for over a year.
On Nov 21, 2018 1:48 AM, ls<EMAIL_ADDRESS>wrote:
So is this ever going to get merged? We've hit this issue in production, where with checkQuorum and preVote activated we are in an endless loop of ignoring MsgPreVotes. 3 nodes. Leader goes down. Other two endlessly try to PreVote and keep ignoring each other. The randomization in "pastElectionTimeout" which I think is supposed to prevent this is not working.
I don't think your problem is related to this RP. But it seems you've met this: #8346https://github.com/etcd-io/etcd/pull/8346
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/etcd-io/etcd/pull/8334#issuecomment-440601316, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAvL8nte6qFehQqFeMNJtcDpFDPT-kF7ks5uxSGIgaJpZM4OnTvd.

@xiang90  PTAL

@bdarnell   I've updated the test case.

lgtm


Error: Julia: type OpSum has no field second_q_ops

Computing the ground state energy with GroundStateEigensolver().solve() from Qiskit raises the following error: Julia: type OpSum has no field second_q_ops.

I think we determined this is not a bug.


Fixes watch of expressions property

Hi, firstly thank you for this awesome package!
I'm creating this PR to fix the error caused on trying to watch the undefined expressionsMap property.

Error:

Hey but the right value to be watching for is indeed expressionsMap not expressions the reason why it throws that error is probably because the expressionsMap was not set on the payload sent to nova, which can only happen if you forgot to include the HasConditionalContainer trait into your resource


inconsistent mappings classifiers: language vs filetype?

Background
we got parse_packages_from_user_args() checking against a language mapping
https://github.com/williamboman/mason-lspconfig.nvim/blob/e95ee7b6c811a4ed734a724b93e59f5181cdfe93/lua/mason-lspconfig/api/command.lua#L18-L21
whereas parse_packages_from_heuristics() uses the term filetype instead
https://github.com/williamboman/mason-lspconfig.nvim/blob/e95ee7b6c811a4ed734a724b93e59f5181cdfe93/lua/mason-lspconfig/api/command.lua#L52-L55
this makes it harder to track in the documentation
https://github.com/williamboman/mason-lspconfig.nvim/blob/e95ee7b6c811a4ed734a724b93e59f5181cdfe93/doc/mason-lspconfig.txt#L84-L89
Suggested solution

It's probably for the best to pick a qualifier and stick with it to avoid confusion, my vote goes for either filetype or languageId
there's no reason that parse_packages_from_user_args() should rely on mason.mappings.language
consider renaming mason.mappings.language in mason.nvim

Hey! These serve different purposes, where the "language" mapping allow convenient installation by explicitly providing a language you want to install (:LspInstall lua). From what I've observed, this seems to be a pretty common way for users to install a server. The filetype-backed installation is never directly surfaced to users and is only in place to support the use case where you just run :LspInstall and a list of suggested servers are presented to you. This is sourced from the filetype mappings in lspconfig.
As for sourcing from LSPs languageId - I'm not sure the list of languages is part of the spec, and even if they were they'd have to be manually mapped somewhere?

The filetype-backed installation is never directly surfaced to users and is only in place to support the use case where you just run :LspInstall and a list of suggested servers are presented to you. This is sourced from the filetype mappings in lspconfig.

oh I'm not arguing the use-case, it's rather just the wording/terminology.
compare these two prompts
https://github.com/williamboman/mason-lspconfig.nvim/blob/e95ee7b6c811a4ed734a724b93e59f5181cdfe93/lua/mason-lspconfig/api/command.lua#L30
vs
https://github.com/williamboman/mason-lspconfig.nvim/blob/e95ee7b6c811a4ed734a724b93e59f5181cdfe93/lua/mason-lspconfig/api/command.lua#L58

As for sourcing from LSPs languageId - I'm not sure the list of languages is part of the spec, and even if they were they'd have to be manually mapped to a lspconfig server, or Mason package, somewhere?

I think they're currently a recommendation, but what I want to get across is that neovim treats filetype as languageId in nearly all the cases where it's relevant, and language is just shortened from languageId when it's user-facing, at least that's how I interpret it.

I'm probably being overly pedantic here, but I figured it's worth pointing out to see if we could arrive at a consistent naming scheme.

Ah ok now I follow. Had there been such a structured enumeration of languages (which also were to have a 1:1 relation with Vim's 'filetype') it'd be great, but to my knowledge it doesn't really exist. I also still can't help but view these as separate concepts.
My thinking is as follows:

The "languages" are sourced from Mason's language definitions. These are entirely internalized in Mason and are really only meant for UI components, as well as :LspInstall <language> where they're lowercased. It's not meant for "programmatic" use, as opposed to 'filetype'.
'filetype' has some characteristics that I think makes it a bad identifier for a "language":

There's often multiple filetypes for the same language. Take typescript, typescript.jsx and typescriptreact for example - are these three distinct "languages"?
Although it is the exception, there are 3rd party plugins language plugins that fill in missing ftdetect, leading to "unstandardized" filetypes.

I don't think the prompt examples are problematic from a user experience point of view? One is centered around 'filetype', which is a very central Vim concept, and the other is for when a user explicitly provides a language. In both cases these are visible in the prompt.
The purpose of these things in the context of Mason is purely to enable a better end-user experience. I personally don't really care too much where things are sourced from. If getting rid of one of the underlying mappings is achievable without a worsened experience I'm all for it!


vue-router breaks nuxt/types

Version
v2.12.2
Reproduction link
https://any-ts-nuxt-project
Steps to reproduce
see https://github.com/nuxt/typescript/issues/374
What is expected ?
compile without error
What is actually happening?
compilation fails with error:
: Property component does not exist on RouterConfig

This bug report is available on Nuxt community (#c10764)

This error shows only when create new nuxt app with typescript

ERROR  ERROR in /Users/dev/Code/draft/typescript/node_modules/@nuxt/types/config/router.d.ts(14,27):
14:27 Property 'component' does not exist on type 'RouteConfig'.
12 |   chunkName?: string
13 |   chunkNames?: Record<string, string>
14 |   component?: RouteConfig['component'] | string
|                           ^
15 | }
16 |
17 | export interface NuxtConfigurationRouter extends RouterOptions {

ℹ Version: typescript 3.8.3

Error Message:

File<EMAIL_ADDRESS>

This problem come from this commit: https://github.com/vuejs/vue-router/commit/dab86c5
Meanwhile, you can force the previews vue-router version to avoid this: "vue-router": "3.3.2"

Hi! This is already fixed:

#7503
https://github.com/nuxt/typescript/commit/b181e7aa49080e10a8bbea3d0818258f5ecf1e8e

Please ensure upgrading to<EMAIL_ADDRESS>:)

@pi0
Thank you for your enthusiasm.
Today i tried to update nuxt to 2.13.1 (and I was check @nuxt/types version is '0.7.9').
But I got this error in extendRoutes
 Type '(route: Route) => { bar: boolean; }' is not assignable to type 'Dictionary<boolean | Object | RoutePropsFunction>
extendRoutes (routes, resolve) {
    routes.push({
        name: 'foo',
        path: '/foo/',
        component: resolve(__dirname, 'components/my-component.vue'),
        props: (route) => ({ bar: true }) <= Error occurred here.
    })
}

I thought RouteConfigSingleView.props has disappeared after type RouteConfig = UnionToIntersection<_RouteConfig>.
interface _RouteConfigBase {
  path: string
  name?: string
  children?: RouteConfig[]
  redirect?: RedirectOption
  alias?: string | string[]
  meta?: any
  beforeEnter?: NavigationGuard
  caseSensitive?: boolean
  pathToRegexpOptions?: PathToRegexpOptions
}

interface RouteConfigSingleView extends _RouteConfigBase {
  component?: Component
  props?: boolean | Object | RoutePropsFunction
}

interface RouteConfigMultipleViews extends _RouteConfigBase {
  components?: Dictionary<Component>
  props?: Dictionary<boolean | Object | RoutePropsFunction>
}

export type RouteConfig = RouteConfigSingleView | RouteConfigMultipleViews

type UnionToIntersection<T> = (T extends any ? (k: T) => void : never) extends ((k: infer U) => void) ? U : never
type RouteConfig = UnionToIntersection<_RouteConfig> <= RouteConfigSingleView.props has disappeared here?

export interface NuxtRouteConfig extends Pick<RouteConfig, Exclude<keyof RouteConfig, 'children' | 'component'>> {
  children?: NuxtRouteConfig[]
  chunkName?: string
  chunkNames?: Record<string, string>
  component?: RouteConfig['component'] | string
}

I'm sorry, my English is not good.

@pi0
It may not be what I should write here, but let me comment.
That's all the errors I'm seeing in my IDE.

TS2322:
Type '(route: Route) => { foo: boolean; }' is not assignable to type '(false & Dictionary<boolean | Object | RoutePropsFunction>) | (true & Dictionary<boolean | Object | RoutePropsFunction>) | (Object & Dictionary<...>) | (RoutePropsFunction & Dictionary<...>) | undefined'.
Type '(route: Route) => { foo: boolean; }' is not assignable to type 'RoutePropsFunction & Dictionary<boolean | Object | RoutePropsFunction>'.
Type '(route: Route) => { foo: boolean; }' is not assignable to type 'Dictionary<boolean | Object | RoutePropsFunction>'.       Index signature is missing in type '(route: Route) => { foo: boolean; }'.

It looks to that for each union type in RouteConfigSingleView, the props in RouteConfigMultipleViews intersect.
However, with TypeScript Playground it seems fine.

(property) props?: boolean | Object | RoutePropsFunction | Dictionary<boolean | Object | RoutePropsFunction> | undefined

There may be a problem with my environment.
Sorry for my long post.


Newest htmlbars release (0.14.17) breaks block indentation rule

This change breaks the block indentation rule because now this check passes for text nodes.  Those two spaces' location points to column 0, which the block indentation logic flags as incorrect, and then when trying to log the error, throws an exception on this line because text nodes don't have a path attribute.
I think the fix is to look for an explicit list of node types instead of the !child.loc check, but I don't have time to prepare a fix right now. If somebody else does, great, otherwise maybe we can just pin the version of htmlbars to 0.14.16 until we have time to get in a fix?

Yep, I'm mid update. Should be released in < an hour.

OK, sorry about this.  I thought I had it all ready to go before releasing the HTMLBars update, but missed a few tests on my first pass. Should be resolved in v0.3.4.

Yup, all working for me again. Plus the new code caught some bad indentation of text content in my templates -- nice! Thanks :smile:

Awesome!


Clarify support disclaimer

They have to go through Critique. We have a branch protection rule that should have prevented this, it looks right to me, but I guess it's misconfigured..

It looks like the branch protection rules are not applied to administrators. I created an internal change that should override the commit history on sync.

awesome! Thanks
On Wed, Jul 22, 2020 at 6:40 PM Lukas Berger<EMAIL_ADDRESS>wrote:

It looks like the branch protection rules are not applied to
administrators. I created an internal change that should override the
commit history on sync.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/buildpacks/pull/65#issuecomment-662560503,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABFPF7KFATX45KLBTMJUHLR44I6HANCNFSM4PEHEHWA
.


Fix bug that caused Wallaroo to shut down when connecting a new source after a 3->2 shrink

We were not correctly updating the RouterRegistry's boundary
builder map during autoscale events, leading to routing problems
in certain shrink scenarios (such as 3->2).
Closes #2071

This looks reasonable but I don't have time to test. Is there an automated test for this or short of that for right now, can you get someone to manually test?

@SeanTAllen I'll get someone to manually test.  I'm going to bring it up with Nisan as a test scenario we need to figure out how to capture.

@nisanharamati is going to test this.

@jtfmumm I can't test adding a sender, because the shrink stalls for me.
I'm doing this on testing/correctness/apps/alphabet, so it might be due to the larger number of partitions.
Steps:

start 1-worker (initializer)
join 2 workers (worker1, worker2)
shrink worker2
<<< stall >>>
start sender (can't get to this part)

@jtfmumm repro steps for above bug:
build
make build-testing-correctness-apps-alphabet build-utils-cluster_shrinker build-utils-data_receiver build-giles-all

Start 1, Join 2, Shrink 3->2, Start sender, validate.

Semi-successful means: the shrunk worker migrates its steps off to the remaining workers, and the remaining workers unmute, BUT the shrunk worker doesn't complete its shutdown.

@nisanharamati Do you see the same problem on master or is it related to these changes?

Yes. I think it's a separate bug.

I also see the same issue where the departing worker doesn't exit on master

@nisanharamati What bug are you finding in the work on this branch that is not present on master?  I'm assuming that's what's holding up this PR.

@jtfmumm I think both bugs I found are separate. The manual test works as expected, so I think this is good to go.


ModuleNotFoundError: No module named '' with requirements volume added.

Version: docker-compose-LocalExecutor.yml
I'm working to include a custom plugin that uses a new module and so I've added  - ./requirements.txt:/requirements.txt to ensure that this module is installed but this issue persists.
The specific module I'm trying to import is jbxapi. When running the command docker-compose up | rg jbxapi to see what's going on. The first results on startup are what seems to be the module being installed:
webserver_1  | Collecting jbxapi==3.4.0
webserver_1  |   Using cached jbxapi-3.4.0-py2.py3-none-any.whl (13 kB)

but then immediately after I'm getting:
webserver_1  | ModuleNotFoundError: No module named 'jbxapi'
webserver_1  | [2020-02-07 23:53:41,081] {{plugins_manager.py:188}} ERROR - No module named 'jbxapi'
webserver_1  |     import jbxapi

I use this module in the operator I define for my custom plugin using the structure mentioned in #443.
In the WebUI this manifests as:

I had the same error when I added cbapi to airflow's requirements.txt


Move the Ethereum SDK version check used in plugins to the reusable workflow repository

As seen here
https://github.com/LedgerHQ/app-plugin-boilerplate/pull/112


prop-types-exact prevents user from using data-testid prop for locating components during testing

Bug report
Describe the bug
When using the common data-testid practice for components (https://blog.kentcdodds.com/making-your-ui-tests-resilient-to-change-d37a6ee37269), prop-types-exact prints errors that are not able to be disabled.
Was added here: https://github.com/zeit/next.js/pull/2516
https://github.com/suprraz/babel-plugin-react-element-info/issues/2
Solutions
a. Remove prop-types-exact
b. Add another prop to Link that allows disabling it (escape hatch).
Workaround
Wrap Link component, and don't add data-testid to next/link, only to the wrapper.

Adding data-testid to <Link> won't add anything to the resulting HTML document, adding it to <a> or the element under <Link> will, so the exact proptypes check is correct here, and this is not a bug.

Ah wait, I see what you mean. I was using a babel-plugin to generate the data tags. Placing one on the Link tag would never make it to the dom anyway as you said


Validating HTTPRouteFilter type consistency

What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR adds validates that a HTTPRouterFilter Type matches it's value.
Which issue(s) this PR fixes:
Fixes #942
Does this PR introduce a user-facing change?:
NONE

Hey @jpeach, this PR looks to address  #942

/ok-to-test

/retest-required

/retest

/retest

/retest

Once the deep equal issue is done, this LGTM, pending Rob's concurrence.
/lgtm
/hold

After some discussion with Rob regarding validation we decided to check for nil instead of empty and to check these two cases for each filter:

if filter != nil  && filter.Type != filter return some error
if filter == nil  && filter.Type == filter return some other error
Please let me know what y'all think.

Thanks @crmejia! Will leave final LGTM for someone else, but this looks great.
/approve

/remove-hold


Creating a context WithTargetID closes browser even if the context is not canceled

What versions are you running?
$ go list -m github.com/chromedp/chromedp
v0.7.2

What did you do? Include clear steps.
So I am working with an already created Browser and I am trying to connect to a tab that is already open. When I call chromedp.Targets() and iterate over those and find the correct target I can create a context and everything works as planned.
targets, err := chromedp.Targets(ctx)
if err != nil {
}
if len(targets) == 0 {
}
var newTarget *target.Info
for _, rTarget := range targets {
	if rTarget.TargetID == target.ID(page.Id) {
			newTarget = rTarget
	}
}
tabCtx, tabCancel := chromedp.NewContext(ctx, chromedp.WithTargetID(newTarget.TargetID))

However I do not want to iterate over the targets every single time I perform this action. Instead I already know the ID of the tab so I tried doing
newTarget := target.Info{}
newTarget.TargetID = target.ID(page.Id)
tabCtx, tabCancel := chromedp.NewContext(ctx, chromedp.WithTargetID(newTarget.TargetID))

this also works as intended except after I execute
if err := chromedp.Run(tabCtx, chromedp.Reload()); err != nil {
      return err
}

the browser is closed. I am unsure as to why this is any different than iterating over the targets since WithTargetID is simply just setting a field on the context.
What did you expect to see?
I expected the reload action to run and the browser to stay open
What did you see instead?
The reload action was run and then the browser was closed as if I canceled the context however I did not cancel it

@GRVYDEV Can you post a full reproducer? (for the target ID, leave a comment that describes how to get it).
From the current information, one possible reason is that the parent context is cancelled.

The page is gotten by issuing an http request to localhost:1234/json This returns a list of pages and their data looks like this:
type Page struct {
	Description          string `json:"description"`
	FaviconUrl           string `json:"faviconUrl"`
	Id                   string `json:"id"`
	Title                string `json:"title"`
	Type                 string `json:"type"`
	Url                  string `json:"url"`
	WebSocketDebuggerUrl string `json:"webSocketDebuggerUrl"`
}

As far as I can tell the parent context is not being canceled. I am using the context in the exact same way. I am just creating it differently so it shouldnt have to do with the parent context.

Can you provide a minimal runnable demo to reproduce the issue?

Ive refactored what I was doing an thus solved my issue

Do you mind sharing what's wrong in your original implementation? So that others can avoid it in the future.

Previously I was building multiple contexts for the same browser instance and switched to use only 1 context for all browser interaction


Feature: Fotter navbar Focus

Footer navbar focus if we want
https://github.com/Sayak-Bhunia/mystory/assets/109230049/b9243266-cf07-4605-9c37-d4f4cf660b91
Previous navbar dot have focus
https://github.com/Sayak-Bhunia/mystory/assets/109230049/61db4cfa-de47-41fe-8649-8b282be990ed

assigned.
but make a fork of the new main branch the do your changes.

@Che140401 updates?


Add delete button to action tab

In the case of trying to get rid of a bunch of actions, it's kind of handy to have the delete button in the action list.

I literally was going to post this as an idea now. Definitely needs to be added. Deleting all the actions from say a pre made category is a pain.

Closed by f1dfe110201fdc2d25cc91a0b036ab3c708be650


fix: update certifi version to address CVE-2023-37920

Summary
Fix image vulnerability from docker and aws inspector scan
Does this close any open issues?
Closes #6508
Screenshots

Other Information
As it has been discussed on psf/requests repo, update certifi version to address critical CVE #6494, maintainers have decided to not update certifi :
This change isn't required. Requests already support the latest version of cryptography and users are free to upgrade as needed.

I have overridden poetry certifi version dependency to 2023.07.22 as mentioned in fix subdependency versions, while keeping subdeps separated from direct dependencies. #2546
It only concerns the backend/python/pydevlake/pyproject.toml file since other pyproject files include it as a dependency.
[tool.poetry.dependencies]
python = "~3.9"
pydevlake = { path = "../../pydevlake", develop = true }

Lock files have been updated with poetry lock --no-update to keep the same dependencies versions in :

backend/python/pydevlake
backend/python/plugins/azuredevops
backend/python/test/fakeplugin

LGTM
@keon94 @CamilleTeruel What do you think?

LGTM @keon94 @CamilleTeruel What do you think?

LGTM too


Implement write throughput in Fuse Stressbench

Is your feature request related to a problem? Please describe.
Fuse stressbench is added which supports getting the fuse read throughput.
Docs available at https://docs.alluxio.io/os/user/stable/en/operation/StressBench.html#fuse-io-stress-bench
Related PRs
https://github.com/Alluxio/alluxio/pull/13869
https://github.com/Alluxio/alluxio/pull/14018
Describe the solution you'd like
Support write throughput as well
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Urgency
Explain why the feature is important
Additional context
Add any other context or screenshots about the feature request here.

A few ideas by @ssz1997 :
Rename the current Write operation to PrepareData
For write throughput test, all threads just keep writing during the warmup time and duration time until time is up. Report the number of bytes written
Delete all written data after testing.


add IPV6 support

add scripts for setting up KinD clusters on IPV6 for major CNIs

antrea
calico
cilium: see https://github.com/cilium/cilium/blob/839c3e3e6e612f992196ed8642beabe9ecf16b60/.github/workflows/smoke-test-ipv6.yaml#L58-L70

handle traffic matching in IP matcher

see https://kind.sigs.k8s.io/docs/user/quick-start#ipv6-clusters