Reduce the use of File, FileInputStream, FileOutputStream and path existence checking with alternatives from Files where possible

Task Description
As part of the storage and repository refactoring, we need to reduce the use of the following as much as possible and replace it with respective implementations from Files:

new File(...) with basePath.resolve(path) (where path is a String)
File.exists(...) with Files.exists(path)
new FileInputStream(...) with Files.newInputStream(path)
new FileOutputStream(...) with Files.newOutputStream(path)

Tasks
The following tasks will need to be carried out:

[ ] Re-work the MavenArtifactGenerator. ( @carlspring )
[ ] Re-work the NugetArtifactGenerator.
[ ] Re-work the NpmArtifactGenerator.
[ ] Re-work the PypiArtifactGenerator.
[ ] Re-work the RawArtifactGenerator.
[ ] Re-work the RpmArtifactGenerator.

Task Relationships
This task:

Is a sub-task of: #1808

Help

Our chat
Points of contact:

@carlspring
@sbespalov
@steve-todorov

Hey, could I takeover this issue?

@svaddadhi ,
Thanks for offering to help! That would be great! I've already done some work on re-working the MavenArtifactGenerator already. Perhaps you could have a look at how I've done it and apply similar fixes to the rest of the ArtifactGenerator implementations...?
For more details, please join our chat channel.

That sounds great @carlspring , I will go ahead and get working on that, and I will join the chat channel as well

We should have a discussion on the chat first.

Hi, I would like to contribute. How to get started?

Hello! I'd like to contribute too if theres anything I could help with!

Guys, thanks for offering to help! Please, join our chat channel for more details.

Hi, do you still need some help?

Hi, Can I contribute to this issue?

Hi, I would like to contribute to this issue. Do you still need help?

Guys, you can just go ahead nad pick this up and proceed with it.

Hi,I would like to work in the task, however I don't understand the pipeline:
Re-work the MavenArtifactGenerator.
Re-work the NugetArtifactGenerator.
Re-work the NpmArtifactGenerator.
Re-work the PypiArtifactGenerator.
Re-work the RawArtifactGenerator.
Re-work the RpmArtifactGenerator.

I just opened a PR https://github.com/strongbox/strongbox/pull/1892 for MavenArtifactGenerator . I will wait the pipeline to check all the changes necessary to continue

As the old PR closed, I opened a new one: https://github.com/strongbox/strongbox/pull/1919

Updated the PR to do all points of this issue, by the way there is no RpmArtifactGenerator or similar for RPM and for P2 there isn`t as well

Please, ignore the P2 layout provider, as it was started and never completed. You are also right about the RpmArtifactGenerator. We have some active work the the RPM support a while ago, but the contributor who was working with me disappeared, so we have the code for this on a separate branch -- rpm-layout-provider. You can check here for more details. If you would like to fix it for this as well, you'll need to create a separate pull request for it against the rpm-layout-provider branch.

@luan-cestari ,
Would you like to look into the RpmArtifactGenerator, as explained above?

I've had a quick look at the RpmArtifactGenerator class and it looks like there's nothing to do there.
Thanks for your help, @luan-cestari ! :)


Support tmysql4

Need to add support for tmysql4 and mysqloo

[ ] Adjust module checking to check for both (tmysql and mysqloo), error only when one isn't present
[ ] Add Support for tmysql to the db wrapper: Check for existing solutions
[ ] Test connection is reistablished after failure and queued queries are executed
[ ] Eliminate all blocking calls (e.g. Updater)

If i'm using the tmysql mysqloo wrapper that was made (link How come it still produces this error?
[ERROR] addons/libk/lua/libk/server/sv_libk_database.lua:113: attempt to index field 'MySQLDB' (a nil value)

Query - addons/libk/lua/libk/server/sv_libk_database.lua:113
DoQuery - addons/libk/lua/libk/server/sv_libk_database.lua:167
3. s - addons/libk/lua/libk/server/sv_libk_model.lua:145
4. succ - addons/libk/lua/libk/shared/1_sh_promises.lua:48
5. Done - addons/libk/lua/libk/shared/1_sh_promises.lua:116
6. initializeTable - addons/libk/lua/libk/shared/1_sh_promises.lua:107
7. initModels - addons/libk/lua/libk/server/sv_libk_server.lua:52
8. v - addons/libk/lua/libk/server/sv_libk_server.lua:69
9. Call - lua/includes/modules/hook.lua:84
10. onConnected - addons/libk/lua/libk/server/sv_libk_database.lua:255
11. connect - lua/includes/modules/mysqloo.lua:55
12. ConnectToMySQL - addons/libk/lua/libk/server/sv_libk_database.lua:257
13. getDatabaseConnection - addons/libk/lua/libk/server/sv_libk_database

@SirNickParks It's because it doesn't support any blocking connections unfortunately.

Closing this as tmysql is no longer maintained and mysqloov9 is a full recode and the recommended module now.


问题请教

非常抱歉在这个时刻打扰到你，很荣幸阅读你的论文，从中受到了很多启发。但是我在使用你的源码去实验的过程中遇见了一些问题，希望能请教一下你。在使用validation_realWorld.py时遇见了这样的问题，不知道该怎么样解决。
Traceback (most recent call last):
File "D:\End-to-end-DRL-for-FJSP-main\FJSP_RealWorld\validation_realWorld.py", line 219, in
a = test(filepath, data_file)
File "D:\End-to-end-DRL-for-FJSP-main\FJSP_RealWorld\validation_realWorld.py", line 162, in test
ppo.policy_job.load_state_dict(torch.load(job_path1))
File "D:\anaconda\envs\pytorch\lib\site-packages\torch\nn\modules\module.py", line 1482, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for Job_Actor:
Unexpected key(s) in state_dict: "feature_extract.mlps.0.linears.0.weight", "feature_extract.mlps.0.linears.0.bias", "feature_extract.mlps.0.linears.1.weight", "feature_extract.mlps.0.linears.1.bias", "feature_extract.mlps.0.linears.2.weight", "feature_extract.mlps.0.linears.2.bias", "feature_extract.mlps.0.batch_norms.0.weight", "feature_extract.mlps.0.batch_norms.0.bias", "feature_extract.mlps.0.batch_norms.0.running_mean", "feature_extract.mlps.0.batch_norms.0.running_var", "feature_extract.mlps.0.batch_norms.0.num_batches_tracked", "feature_extract.mlps.0.batch_norms.1.weight", "feature_extract.mlps.0.batch_norms.1.bias", "feature_extract.mlps.0.batch_norms.1.running_mean", "feature_extract.mlps.0.batch_norms.1.running_var", "feature_extract.mlps.0.batch_norms.1.num_batches_tracked", "feature_extract.mlps.1.linears.0.weight", "feature_extract.mlps.1.linears.0.bias", "feature_extract.mlps.1.linears.1.weight", "feature_extract.mlps.1.linears.1.bias", "feature_extract.mlps.1.linears.2.weight", "feature_extract.mlps.1.linears.2.bias", "feature_extract.mlps.1.batch_norms.0.weight", "feature_extract.mlps.1.batch_norms.0.bias", "feature_extract.mlps.1.batch_norms.0.running_mean", "feature_extract.mlps.1.batch_norms.0.running_var", "feature_extract.mlps.1.batch_norms.0.num_batches_tracked", "feature_extract.mlps.1.batch_norms.1.weight", "feature_extract.mlps.1.batch_norms.1.bias", "feature_extract.mlps.1.batch_norms.1.running_mean", "feature_extract.mlps.1.batch_norms.1.running_var", "feature_extract.mlps.1.batch_norms.1.num_batches_tracked", "feature_extract.bn.weight", "feature_extract.bn.bias", "feature_extract.bn.running_mean", "feature_extract.bn.running_var", "feature_extract.bn.num_batches_tracked", "feature_extract.batch_norms.0.weight", "feature_extract.batch_norms.0.bias", "feature_extract.batch_norms.0.running_mean", "feature_extract.batch_norms.0.running_var", "feature_extract.batch_norms.0.num_batches_tracked", "feature_extract.batch_norms.1.weight", "feature_extract.batch_norms.1.bias", "feature_extract.batch_norms.1.running_mean", "feature_extract.batch_norms.1.running_var", "feature_extract.batch_norms.1.num_batches_tracked".

Traceback (most recent call last):
File "D:\End-to-end-DRL-for-FJSP-main\FJSP_RealWorld\PPOwithValue.py", line 468, in
main(100)
File "D:\End-to-end-DRL-for-FJSP-main\FJSP_RealWorld\PPOwithValue.py", line 319, in main
env = FJSP(configs.n_j, configs.n_m)
TypeError: init() missing 1 required positional argument: 'EachJob_num_operation'
运行PPOwithValue.py文件时出现这个错误应该怎么解决

非常抱歉在这个时刻打扰到你，很荣幸阅读你的论文，从中受到了很多启发。但是我在使用你的源码去实验的过程中遇见了一些问题，希望能请教一下你。在使用validation_realWorld.py时遇见了这样的问题，不知道该怎么样解决。 Traceback (most recent call last): File "D:\End-to-end-DRL-for-FJSP-main\FJSP_RealWorld\validation_realWorld.py", line 219, in a = test(filepath, data_file) File "D:\End-to-end-DRL-for-FJSP-main\FJSP_RealWorld\validation_realWorld.py", line 162, in test ppo.policy_job.load_state_dict(torch.load(job_path1)) File "D:\anaconda\envs\pytorch\lib\site-packages\torch\nn\modules\module.py", line 1482, in load_state_dict raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format( RuntimeError: Error(s) in loading state_dict for Job_Actor: Unexpected key(s) in state_dict: "feature_extract.mlps.0.linears.0.weight", "feature_extract.mlps.0.linears.0.bias", "feature_extract.mlps.0.linears.1.weight", "feature_extract.mlps.0.linears.1.bias", "feature_extract.mlps.0.linears.2.weight", "feature_extract.mlps.0.linears.2.bias", "feature_extract.mlps.0.batch_norms.0.weight", "feature_extract.mlps.0.batch_norms.0.bias", "feature_extract.mlps.0.batch_norms.0.running_mean", "feature_extract.mlps.0.batch_norms.0.running_var", "feature_extract.mlps.0.batch_norms.0.num_batches_tracked", "feature_extract.mlps.0.batch_norms.1.weight", "feature_extract.mlps.0.batch_norms.1.bias", "feature_extract.mlps.0.batch_norms.1.running_mean", "feature_extract.mlps.0.batch_norms.1.running_var", "feature_extract.mlps.0.batch_norms.1.num_batches_tracked", "feature_extract.mlps.1.linears.0.weight", "feature_extract.mlps.1.linears.0.bias", "feature_extract.mlps.1.linears.1.weight", "feature_extract.mlps.1.linears.1.bias", "feature_extract.mlps.1.linears.2.weight", "feature_extract.mlps.1.linears.2.bias", "feature_extract.mlps.1.batch_norms.0.weight", "feature_extract.mlps.1.batch_norms.0.bias", "feature_extract.mlps.1.batch_norms.0.running_mean", "feature_extract.mlps.1.batch_norms.0.running_var", "feature_extract.mlps.1.batch_norms.0.num_batches_tracked", "feature_extract.mlps.1.batch_norms.1.weight", "feature_extract.mlps.1.batch_norms.1.bias", "feature_extract.mlps.1.batch_norms.1.running_mean", "feature_extract.mlps.1.batch_norms.1.running_var", "feature_extract.mlps.1.batch_norms.1.num_batches_tracked", "feature_extract.bn.weight", "feature_extract.bn.bias", "feature_extract.bn.running_mean", "feature_extract.bn.running_var", "feature_extract.bn.num_batches_tracked", "feature_extract.batch_norms.0.weight", "feature_extract.batch_norms.0.bias", "feature_extract.batch_norms.0.running_mean", "feature_extract.batch_norms.0.running_var", "feature_extract.batch_norms.0.num_batches_tracked", "feature_extract.batch_norms.1.weight", "feature_extract.batch_norms.1.bias", "feature_extract.batch_norms.1.running_mean", "feature_extract.batch_norms.1.running_var", "feature_extract.batch_norms.1.num_batches_tracked".

请问，您解决了这个问题吗

请问，您解决了这个问题吗


Supporting multiple columns + arbitrary selects

I've recently had to build something quite similar to this (without knowing this library existed) that needs to support two things:

Multiple column cursor fields
Arbitrary selects in the query

I think #3 covers the first point, but it isn't as simple as it immediately seems because automating the following is difficult:

Imagine you have %MySchema{id_1: ..., id_2: ..., id_3: ...}
Our cursor_fields thus need to be [:id_1, :id_2, :id_3]
When we're fetching data we need to do: where: (x.id_1, x.id_2, x.id_3) > (^max_cursor.id_1, ^max_cursor.id_2, ^max_cursor.id_3)
You can construct a dynamic tuple for the above comparison quite trivially via fragment("(?)", splice(^cursor_fields))
HOWEVER I don't think there's a mechanism to dynamically generate arbitrary tuples of fields belonging to bindings... we resorted to hackily dynamically generating the tuples.. so it works but its hacky and honestly probably not great.

Doing the above also complicates using the library efficiently as you may have an index covering [:id_1, :id_2, :id_3] but if cursor_fields: [:id_3, :id_1, :id_2] is provided, no index will be used by postgres :(
Anyhow, totally solvable perhaps in a more intelligent way than we did it.
The only reason we did this is because I'm pretty sure (id_1, id_2, id_3) > (1, 2, 3) is semantically different from: id_1 > 1 AND id_2 > 2 AND id_3 > 3 but maybe I'm wrong? If these are identical then maybe our hack is unnecessary here.
For the second point though... this is much more problematic. Say I want to stream over:
from x in MySchema,
  select: %{id: nil}

This library (and our original implementation) will fail to stream over these records as the specified cursor fields aren't in the results returned from Ecto.Repo.all/2.
We fixed this by dynamically injecting a select_merge: %{__cursor__: {x.id_1, x.id_2, x.id_3}} but again, we had to resort to a lot of hacking in order to actually get this working (building fragment ASTs by hand and manually patching Ecto queries...)
Would love to know if you have any thoughts on the above!! Maybe there exists better/smarter ways to do what we're doing, and maybe there's an opportunity to collaborate on implementing these functions in EctoCursorBasedStream?

Hi @vereis, thanks for you detailed issue. I have released new version 1.2.0 that supports cursor on multiple columns, please give it a try. Regarding arbitrary selects, I find current implementation to be flexible enough to select what you need, as long as you select cursor fields as a map. Do you any examples that aren't possible?

I'll give this a try in the next few days! Thank you :-)
I'll let you know how it goes ❤


Updote wallet

Updote wallet
Originally posted by @mostafa3100 in https://github.com/ton-blockchain/wallet-contract-v5/pull/170

my coins not  received , x empire coins,cati,dogs tokens etc , please help


Caret over wide character behavior

Not implemented.

Highlighting the current insertion point by underlining or inverting the corresponding cell is sufficient.
I closed this issue because it doesn't make sense to highlight the presence of a wide character at the insertion point. Our character handling approach allows wide characters to be halved anywhere.
Moreover, our approach assumes the use of triple and quadruple characters along with narrow and wide ones, as well as characters more than one cell high, but that's another story.


Not discarding the previous teb in renewAndAnalyzeOldTebs

The function renewAndAnalyzeOldTebs currently discards plans pertaining to the same homotopy class without checking which one has the lowest cost.
This PR prevents this function from discarding the last best_teb_ in the case that another plan coming chronologically before in the tebs_ vector is evaluated in the same homotopy class.
To do so the last best teb is moved at the beginning of the tebs_ vector and its homotopy class identifier is added first.
I've seen there's a TODO for always selecting the teb with the lowest cost for each homotopy class; but such a change would have been more invasive (could for ex be achieved storing the tebs in a container sorted by cost).

thanks, merged ;-)


Fix exist status handling

Fixed #69

Incidentally, it also fixes the terminal going wonky because the wrapper binary was not waiting for the child process.

Is there something that needs to be changed in this PR?

looks fine, friendly bump @roynalnaruto :)


Question on localizeExtremumViaQuadraticFit()

Hi!
I would like to ask for a comment on line 180 in pysift.py file. Here you are computing keypoint.octave field which is composed of three quantities. Can you please give some hint what does third value mean and maybe some small explanation why it should be like that. (to be more concrete the quantity is computed as 'int(round((extremum_update[2] + 0.5) * 255))')
Many thanks in advance!

Hi @lilithgrigoryan ! Thanks for your interest in this repo.
Sure, let me think about how to explain this.


Output XML

Hello @mikeebowen
My organization uses XML and XML schemas for most of our workflows.
We would like to request the feature of having the validation errors optionally output in XML.

@Asbjoedt ,
If we output xml with the strict format status from the CLI. Do you still need strict validation displayed displayed on the OOXML Validator VS Code extension?

@mikeebowen
I cannot strictly say say I need it, at this moment.

Hi @Asbjoedt ,
Version 1.1.0 adds the ability to return xml with a --xml flag. You can download the executable for your system from the release page
To use the CLI call the executable for your system and pass in 3 arguments: the absolute path to the file (required), the Office version to validate against (Optional, defaults to Microsoft365), and the --xml flag (optional, defaults to JSON if omitted). To validate against the default Microsoft365 and return xml, you would use something like this:
OOXMLValidatorCLI.exe C:\absolute\path\to\file.docx --xml

Hi @mikeebowen `
Great, thank you a bunch!
If we want the validator to be able to bulk process all files recursively in a folder, do I need to open a new issue for this feature?

Hi @Asbjoedt ,
Yes please create another issue for processing files in bulk. I should have some time this week to get started working on it.


Refactor ForeignCall instruction

Problem
See comment here (https://github.com/noir-lang/noir/pull/1600#discussion_r1226746738).
We should be able to create a new Value type and follow the same flow as intrinsics rather than having a separate ForeignCall instruction.
Happy Case
Remove ForeignCall instruction and maintain same foreign call functionality
Alternatives Considered
The existing work is an alternative as foreign calls work as expected. The solution in this issue will enable us to remove an instruction.
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response

@vezenovm can this be closed?

Yes closed by #1644


sample.py assumes what input file to sample from

Currently, sample.py assumes the presence of a particular h5 file in data. Instead, sample.py should take the input data as a parameter. See related pull request.

I have a branch that overhauls sample.py which I've been meaning to get to finish up but just haven't had time the last couple days: https://github.com/maxhodak/keras-molecules/blob/decoder/sample.py
I'm back though and will get that landed.


Support tooltips that we can hover

I use tooltip in a special way, as I mount ReactJS components inside the tooltip.
These tooltips have buttons inside.
I was able to make it work with:
.tooltip-element.tooltip-theme-arrows {
  pointer-events: none;
  &.tooltip-hoverable {
    pointer-events: auto;
  }
}

And by adding the tooltip-hoverable class.
Drop seems clever and does not close the tooltip when it's hovered.
It would be nice to add that option in default themes as well as in the tooltip API

Hmm, tooltip is basically an extension of drop (as I'm sure you know) which defaults set to assume you will use tooltips as tooltips. For your case, I would just suggest using drop which doesn't use pointer-events: none in the styles.

hmmm yes it seems so :) I didn"t think the tooltip code was so simple actually :)

Haha yup. The repo is basically just for the tooltip styles :sweat_smile:


Add repo adoption to FAQ

As far as I can tell this should be a simple set of steps to achieve repo adoption.
There are, of course, many things that could otherwise make the process not work, but I think this should work for the most part.

🎺 🤖


Aurelia-cli import issue

Hi,
We've been fiddling around for quite some time,how to get the latest version (1.0.18) working in Aurelia (using the aurelia-cli). I'm wondering; is there a reason the module (bundle/ai.module.js) is named define('JavaScriptSDK.Module/AppInsightsModule', ...) and not define('applicationinsights-js', ...)'?
If we want Application Insights to be working we need the following to map everything together:
define('applicationinsights-js', ['JavaScriptSDK.Module/AppInsightsModule'], function(ai) { return ai; });
Maybe this is just a problem with Aurelia but if the name could be applicationinsights-js our problems would be fixed ;-)

@Zenuka  - it looks like the typescript compilation produced this define to include folder name JavascriptSDK.Module. Are you not able to use the define? What issue are you seeing?

When I use import { AppInsights } from "applicationinsights-js"; requirejs looks for a module named 'applicationinsights-js' and not 'JavaScriptSDK.Module/AppInsightsModule'. So when I try to use AppInsights it's null because it has no module 'applicationinsights-js' defined.

Anyone got an answer to this?

Can you please try beta sdk version @Microsoft/applicationinsights-web and reply if that resolves the issue. Beta usage is on home page.


⚠ Bofrost.de has degraded performance

In a57e3ff, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1033 ms

Resolved: Bofrost.de performance has improved in 76ee055 after 32 minutes.


⚠ ClamAV has degraded performance

In 988baa2, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 580 ms

Resolved: ClamAV performance has improved in 71cb996 after 5 minutes.


dynamic DataLoader name not respected

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
When using a dynamic name for a dataloader, the execution doesn't respect the different names and executes the dataloader only once.
Slack discussion here: https://hotchocolategraphql.slack.com/archives/CD9TNKT8T/p1640938992150400
Repro: https://github.com/OneCyrus/hcresolver_repro
three dataloaders are registered in the repro but only one is executed.

Steps to reproduce
a repo is here: https://github.com/OneCyrus/hcresolver_repro
the repro query is in the readme.md
Relevant log output
No response
Additional Context?
No response
Product
Hot Chocolate
Version
12.x

Found the issue. With the reworked DataLoader, we use a single cache. The cache key is composed of the type name and the key provided for an item. This means the DataLoader exists correctly in the DataLoaderRegistry but they are using all the same cache partition.
I will fix it later today.

This shows again ... having a repro helps us find and fix things quickly :D

Related to #4744

This one is now fixed and will be integrated into:
13.0.0-preview.17
12.8.0-preview.1


Bidirectional layer creates name with outdated Layer.count?

I am just starting to use this library and got an error running the lstm-chime example. It seems that the Bidirectional class is using Layer.count to construct the name which looks like has been changed to be an internal variable _count.

Excellent, thanks! Just fixed in 14fe580


Make Sayonara non-disruptive

When the project closes a sound is played and the thread is blocked which disrupts the next event like when shutting down the OS, it'll wait for the sound to finish. We need to find a way to run it in the background.
Maybe we can't achieve this because the IJ needs to be opened in order to play the sound, we can however improve it by using short-duration exit sounds.

Will opt to use short-duration Sayonara sounds as we can't really play sounds when the platform is closed.


[Bug]: towhee does not fit the environment python3.8.9

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
if install towhee in python3.8.9, it will raise error. While it's fine in python3.7 and python3.9. Here is the error.
Building wheels for collected packages: cffi
  Building wheel for cffi (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [38 lines of output]
      /Users/zilliz/virtual-environment/towhee3.8/lib/python3.8/site-packages/setuptools/config/setupcfg.py:508: SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use license_files instead.
        warnings.warn(msg, warning_class)
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.macosx-10.14-arm64-cpython-38
      creating build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/backend_ctypes.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/error.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/setuptools_ext.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/__init__.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/cffi_opcode.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/vengine_gen.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/pkgconfig.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/model.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/ffiplatform.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/api.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/vengine_cpy.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/commontypes.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/lock.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/recompiler.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/cparser.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/verifier.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/_cffi_include.h -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/parse_c_type.h -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/_embedding.h -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/_cffi_errors.h -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      running build_ext
      building '_cffi_backend' extension
      creating build/temp.macosx-10.14-arm64-cpython-38
      creating build/temp.macosx-10.14-arm64-cpython-38/c
      clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -DFFI_BUILDING=1 -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/ffi -I/usr/include/libffi -I/Users/zilliz/virtual-environment/towhee3.8/include -I/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/Headers -c c/_cffi_backend.c -o build/temp.macosx-10.14-arm64-cpython-38/c/_cffi_backend.o -iwithsysroot/usr/include/ffi
      c/_cffi_backend.c:2:10: fatal error: 'Python.h' file not found
      #include <Python.h>
               ^~~~~~~~~~
      1 error generated.
      error: command '/usr/bin/clang' failed with exit code 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for cffi
  Running setup.py clean for cffi
Failed to build cffi
Installing collected packages: cffi, bleach, requests-toolbelt, readme-renderer, pygit2, keyring, twine, towhee
  Running setup.py install for cffi ... error
  error: subprocess-exited-with-error

  × Running setup.py install for cffi did not run successfully.
  │ exit code: 1
  ╰─> [40 lines of output]
      /Users/zilliz/virtual-environment/towhee3.8/lib/python3.8/site-packages/setuptools/config/setupcfg.py:508: SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use license_files instead.
        warnings.warn(msg, warning_class)
      running install
      /Users/zilliz/virtual-environment/towhee3.8/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
        warnings.warn(
      running build
      running build_py
      creating build
      creating build/lib.macosx-10.14-arm64-cpython-38
      creating build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/backend_ctypes.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/error.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/setuptools_ext.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/__init__.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/cffi_opcode.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/vengine_gen.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/pkgconfig.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/model.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/ffiplatform.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/api.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/vengine_cpy.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/commontypes.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/lock.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/recompiler.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/cparser.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/verifier.py -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/_cffi_include.h -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/parse_c_type.h -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/_embedding.h -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      copying cffi/_cffi_errors.h -> build/lib.macosx-10.14-arm64-cpython-38/cffi
      running build_ext
      building '_cffi_backend' extension
      creating build/temp.macosx-10.14-arm64-cpython-38
      creating build/temp.macosx-10.14-arm64-cpython-38/c
      clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -iwithsysroot/System/Library/Frameworks/System.framework/PrivateHeaders -iwithsysroot/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/Headers -arch arm64 -arch x86_64 -Werror=implicit-function-declaration -DFFI_BUILDING=1 -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/ffi -I/usr/include/libffi -I/Users/zilliz/virtual-environment/towhee3.8/include -I/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.8/Headers -c c/_cffi_backend.c -o build/temp.macosx-10.14-arm64-cpython-38/c/_cffi_backend.o -iwithsysroot/usr/include/ffi
      c/_cffi_backend.c:2:10: fatal error: 'Python.h' file not found
      #include <Python.h>
               ^~~~~~~~~~
      1 error generated.
      error: command '/usr/bin/clang' failed with exit code 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> cffi

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

Expected Behavior
PASS
Steps To Reproduce
pip install -i https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple towhee==0.8.2.dev84
or
pip install towhee

Environment
- Towhee version(e.g. v0.1.3 or 8b23a93): 0.8.2.dev84
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:

Anything else?
No response

It seems there is no env to install cffi pkg.

@NicoYuan1986
it is ok in other 3.8 minor version?

It seems there is no env to install cffi pkg.

Yes. It's well-behaved under python3.8.10.

It seems there is no env to install cffi pkg.

Yes. It's well-behaved under python3.8.10.

OK，it is non-blocking issue, and defer to next release.


Reapply PR125

The changes introduced by previously merged PR #125 were overwritten by upstream updates from #213. This PR contains exactly the same changes as #125. Please apply these changes again and make sure to pass them upstream.
The object of the changes is fixing the dot over the Cyrillic letters Іі and Јј, which is mistakenly hidden.

@googlebot I signed it!

Thank you and sorry about the process mess up.

@rdaysky : Roman, could you check one or two fonts in https://github.com/googlefonts/noto-fonts ?

@marekjez86 At a glance seems OK


Add an option to disable log

Hi, I've added an option to disable Wine log which can cause huge log files problem (issue #152 ). Thank you.

Nice!


What is VCR Cassette format ?

The readme on github doesn’t link to a definition of the format.

Oh, that's a good point. We do link to it from docs.rs. We probably should from GitHub too.

The link, BTW, is dead, since relishapp shut down.


Add color_list setters in Layout and Animation

I keep writing this in client code:
self.color_list[:] = compute_something()

but that doesn't work:  I have to write
cl = self.color_list
cl{:] = compute_something()

which is really stupid.
The setters fix this.

The setters fix this.
You can view, comment on, or merge this pull request online at:
https://github.com/ManiacalLabs/BiblioPixel/pull/548
Commit Summary

Add color_list setters in Layout and Animation

File Changes

M bibliopixel/animation/animation.py
https://github.com/ManiacalLabs/BiblioPixel/pull/548/files#diff-0
(4)
M bibliopixel/layout/layout.py
https://github.com/ManiacalLabs/BiblioPixel/pull/548/files#diff-1
(4)

Patch Links:

https://github.com/ManiacalLabs/BiblioPixel/pull/548.patch
https://github.com/ManiacalLabs/BiblioPixel/pull/548.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/548, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6mo7YxR0oR-EA0DlzrqUlxTxBc_Tks5tCqoIgaJpZM4RKOA-
.

Ah, there is a reason for this - it's because color_list is a property, so when I do any sort of assignment, even layout.color_list[:] = ..., it tries to call the setter for that property - which doesn't exist.


Send marker for entries

Send market isn't implement for entries.
use tokio::fs::File;
use tokio_tar::Archive;
use futures::prelude::*;
use tokio::prelude::*;

#[tokio::main]
async fn main() {
	tokio::spawn(async {
		let file = File::open("/dev/null").await.unwrap();
		let mut a = Archive::new(file);
		let mut entries = a.entries().unwrap();
		entries.next().await;
	});
}

Dependencies:
tokio-tar = "0.1.0" # or async-tar = "0.1.1"
futures = "0.3.4"
tokio = { version = "0.2.13", features = ["full"] }

It is possible, but requires adding a Mutex, where there currently is none. I will think a bit on it

The Archive isn't either, and I think this is what's causing some trouble I've run into :( https://github.com/dignifiedquire/async-tar/blob/master/src/archive.rs#L45

Should be fixed in the new 0.2 release


Support Flake8 4

flake8 4.0.0 version released recently, this PR adds it in requires https://flake8.pycqa.org/en/latest/release-notes/4.0.0.html

Released in 3.7.0 👍


BUG-Missing link to taipy.gui.notify

Missing link : https://docs.taipy.io/en/develop/manuals/reference/taipy.gui.notify

Well... this link was moved with a refactoring of the whole doc.
Try https://docs.taipy.io/en/develop/manuals/refmans/reference/taipy.gui.notify/
If this works, @bengaid, do you agree this issue should be dropped?

The URL has changed to https://docs.taipy.io/en/develop/manuals/refmans/reference/taipy.gui.notify


LU decomposition of  a sparse matrix

I have sparse matrix that I decompose by splu in scipy and I looked at the sparsity pattern and it looked strange. I used same matrix and applied LU decomposition in matlab and I looked at the sparsity pattern and it is different
sparse.py.tar.gz
python sparsity pattern

matlab sparsity pattern
Download CastleImage matlab function and run the following code
CastleImage.m.tar.gz
 [G,a] = CastleImage; [L,U] = lu(sparse(G),0); spy(L)

That does not mean much --- the permutations can be different.
The relation Pr.T * (lu.L * lu.U) * Pc.T == A still applies.


Looking for old versions

Hi. Someone can point me where to find old versions of SDL_ttf? The oldest present here, 2.0.15 is not being detected by my SDL (1.2.15) configure script.

http://libsdl.org/projects/SDL_ttf/release/


extract_area silently fails

If you try to extract outside the dimensions of the image, both the function and writing the file appears to succeed but the file isn't actually created. I found this out thanks to a floating point error (#82), wherein the image was getting resized to height of 199 and I was expecting it to be 200.
Feel free to request an example. It's late and I wanted to get this in before I forgot tomorrow.

To be clear: I expect the code to explode if I try to do something that doesn't make any sense like this. A helpful error message that I'm trying to extract out of bounds would be awesome.

Hi @eltiare, yes, that's what should happen, it'll raise an exception with an error message. Perhaps you have a catch somewhere that's masking it?
irb(main):009:0> x = Vips::Image.black 100, 100
=> #<Vips::Image:0x1418920 ptr=0x1a464d0>
irb(main):013:0> x.crop 10, 10, 100, 100
Vips::Error: extract_area: bad extract area

	from /home/john/packages/gems/gems/ruby-vips-1.0.3/lib/vips/call.rb:184:in `build'
	from /home/john/packages/gems/gems/ruby-vips-1.0.3/lib/vips/call.rb:249:in `invoke'
	from /home/john/packages/gems/gems/ruby-vips-1.0.3/lib/vips/call.rb:278:in `call_base'
	from /home/john/packages/gems/gems/ruby-vips-1.0.3/lib/vips/image.rb:395:in `method_missing'
	from (irb):13
	from /usr/bin/irb:11:in `<main>'

Hm... maybe. I'm also using version 1.02 because I couldn't get 1.03 to compile on my system. Somebody else already posted a ticket for that one.

I'm catching it for validations, but maybe CarrierWave doesn't report errors on what happens with the sub-versions of an uploader. That's probably it. I'll double-check and then close if that's the case.

Oh dear, 1.0.3 should have worked. The 1.0.3 ticket was a PKG_CONFIG_PATH that hadn't been set, or alternatively a PATH that didn't have /usr/local/bin at the front, depending on how you look at it.

No worries. I'll give it all a shot by Monday.

@eltiare The ticket @jcupitt is referring to is: https://github.com/jcupitt/ruby-vips/issues/84

I was able to get 1.0.3 installed properly. I've not been able to confirm the error, though. I'll keep y'all updated.

@jcupitt I think this was fixed already. There used to be a problem in ruby-vips where it would return nil on error instead of raising an exception, but you fixed it. I don't remember if it was fixed in ruby-vips or libvips.

I don't remember either! Let's close. @eltiare could you reopen if there's still a problem?

Absolutely. 👍

You are probably trying to extract an area outside the image.
If you're sure the area is inside, please open a new issue with a sample image and some code that reproduces the problem.


Can't send a body with a PUT request

I've tried to implement a PUT request given below:
- test:
    - group: "My Group"
    - name: "PUT Test"
    - url: {template: '/myapi/$some_id'}
    - method: "PUT"
    - body: 'name=Some+Name&description=Some+description'
    - curl_option_ssl_verifypeer: False
    - headers: {Content-Type: application/json}
    - expected_status: [202]

and with this format as well,
- test:
    - group: "My Group"
    - name: "PUT Test"
    - url: {template: '/myapi/$some_id'}
    - method: "PUT"
    - body: '{"name": "Some Name", "description": "Some description"}'
    - curl_option_ssl_verifypeer: False
    - headers: {Content-Type: application/json}
    - expected_status: [202]

But I'm unable to receive a body in my apis, which just gets an empty body. As a result I'm unable to test out PUT endpoints for my app. However, the same format works with POST methods where a body is received.

Yeah me too. Also I've tested with Postman. My backend working well.
I think pyresttest has huge problem with PUT method.


Change GitLab to GitHub

Moved repository on GitHub.

Merged as 9ac0eae2356d9c180792c849fd556ae73911d057.

Thx.

Link will feel like not working...

Link will feel like not working...

In the last days we noticed some problems with the build process. See #141 for more information.

Thx, confirmed.


 Just 2 buttons Light/Dark like on the picture, the form, and save button. html/css only! Nevermind the sidebar and the nav. Please ask questions if you face any troubles! Thank you!

Alright thanks, I will get back to you here if I need any clarification.


Added fly-out animation to menu

Just as it sounds; I changed two lines of CSS to add transitions.
One is to add a transition to the left position of the code editor that lasts for 200 milliseconds.
One is to add a transition to the width of the code editor that, again, lasts for 200 milliseconds.
Doing just the left would add a jittering to the upper-right hand side of the buttons, since the width would be updated immediately. Computing both the left and width as the menu "flies out" would keep the position of those upper-right hand buttons constant.

Hey @dandalton1, thanks for submitting a PR! Is there an issue tracking this?

#59664 (a continuation of #56021) references this. I can't find anything else that specifically mentions a menu animation.

This change seems to assume that the sidebar is on the left:

I suggest scoping css changes as specifically as possible, if this should only effect the sidebar, then try to target only that. You can use the Developer: Toggle Developer Tools to bring up chrome dev tools and examine classes.

It seems to me that the logic for controlling the content for the sidebar also happens instantaneously; affecting VSCode's DOM instantly in the process. I'm going to propose adding a 200 ms delay via setTimeout() or something similar (possibly in a try/catch to make sure it's compatible with older browsers that maybe don't support setTimeout()). I'll find out more and commit/comment again later on.

I'm gonna simply close this after further consideration; animating the width of the sidebar makes a ghosting effect even after "sliding out" started to work. At least I tried, and I'm sorry for the inconvenience!

Thanks for giving it a shot!
Maybe you've already looked through these, but we do have a "good first issue" tag that are good places to start contributing, if you're interested.


NTRNL-474 add validation middleware to node template repo

JIRA link
NTRNL-474
Description
Adding validation to the node template repo.
Work checklist

[ ] Tests added where applicable
[ ] No vulnerability added

PR has been closed as Melissa has left the team and implementation was left unfinished. It has been superceded by #28


replace h2 with p

Pull Request Test Coverage Report for Build 2f92c20350b26dd8f466b4c8cd2834fa2c411626
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.233%

Totals

Change from base Build 98dc100b90a0b28d0a172dc3805f584fa98ab415:
0.0%

Covered Lines:
906

Relevant Lines:
913

💛  - Coveralls


Support saber config in theme directory

Feature request

What problem does this feature solve?
A theme should be able to pre-configure siteConfig themeConfig plugins etc.
What does the proposed API look like?
Just populate a saber config file in your theme directory.
Some options are not available when it is loaded from theme directory, e.g. theme
How should this be implemented in your opinion?
Merge it with the saber config we found at project root.
Are you willing to work on this yourself?
PR welcome.

There is a $80.00 open bounty on this issue. Add more on Issuehunt.

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on Issuehunt to raise funds.

@issuehunt has funded $80.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

This is actually already possible by using saber-node.js in the theme directory:
// Add a plugin based on `themeConfig`:
exports.beforeRun = function () {
  if (this.config.themeConfig.feed) {
    this.applyPlugin(require('saber-plugin-feed'))
  }
}


Make cluster creation easier and more reliable

Currently, cluster creation for CAPO with kubectl is not supporting all needed configuration options. Also, it would be nice to have more defaults and fewer values to configure.
Ideas:

have a helm values template file
have defaults in customer specific charts
use app platform defaults
configuration file for kubectl gs
do we need kubectl gs or is it easier for us and the customer to use helm
Use overloays (kustomize)

User stories

As cluster-admin I would like to get a cluster template with the desired OpenStack version in an easy manner.
As cluster-admin I would like to avoid entering the same default values when creating cluster resources.
As cluster-admin I would expect the API complaints if I submit a cluster definition that has wrong values.
As cluster-admin I would like to be alerted when a cluster creation failed for any reason.

I have added User stories in main comment

Please do consult honeybadger (cc @gianfranco-l @MarcelMue as latter has put most work into the WC app design) on this. We should not forget that we have quite some power in app platform's 4 levels of configuration. For MCs that is: app/chart defaults, catalog/installation defaults, user config and there should even be a way to (mis-)use cluster level config for another "template" level (e.g. we could use it for project related stuff that is sub-installation level).

@PrashantR31 has scheduled a meeting to talk about it

@gianfranco-l  @MarcelMue  does it makes sense to keep this issue in rocket? Do you want to take this issue to honeybadger  or are you tracking this already in an other issue?

Closing it then for rocket


az storage container generate-sas support for --FullUri option

I'm porting a PowerShell script to Azure CLI and I've noticed that PowerShell supports a '-FullUri' option that returns the full URI of the SAS token: https://docs.microsoft.com/en-us/powershell/module/azure.storage/new-azurestorageblobsastoken?view=azurermps-6.12.0
Here's the syntax:
New-AzureStorageBlobSASToken
   [-Container] <String>
   [-Blob] <String>
   [-Permission <String>]
   [-Protocol <SharedAccessProtocol>]
   [-IPAddressOrRange <String>]
   [-StartTime <DateTime>]
   [-ExpiryTime <DateTime>]
   [-FullUri] <<-- Here's the option
   [-Context <IStorageContext>]
   [-DefaultProfile <IAzureContextContainer>]
   [<CommonParameters>]

However - the CLI does not support this option:
az storage container generate-sas --name
                                  [--account-key]
                                  [--account-name]
                                  [--auth-mode {key, login}]
                                  [--cache-control]
                                  [--connection-string]
                                  [--content-disposition]
                                  [--content-encoding]
                                  [--content-language]
                                  [--content-type]
                                  [--expiry]
                                  [--https-only]
                                  [--ip]
                                  [--permissions]
                                  [--policy-name]
                                  [--sas-token]
                                  [--start]

Source: https://docs.microsoft.com/en-us/cli/azure/storage/container?view=azure-cli-latest#az-storage-container-generate-sas
I would love support for this flag - it saves me combining the container URI with the SAS token myself.

@williexu, do you have any suggestions for this?

We can implement this, though this is low-pri. Right now as a workaround, of course, one can simply append the sas token to the uri.


[3.x] Add soft shadows to the CPU lightmapper

Adds the light_size property to Lights. It's only considered in baked lightmaps for soft shadowing purposes.
Based on @RandomShaper's work in https://github.com/JFonS/godot/pull/3

Did you think about making light_size a Vector3? That way maybe you could have e.g. long thin lights and rotate them with the transform. Of course you can use emission to have more control over a light volume but a Vector3 is quite handy.
One thing I remember is if you place a volumetric light by a wall, you can end up getting light cast on objects from the other side of the wall, it can be kind of annoying in a confined space like a room. I think I solved it by doing a ray check from the centre of the light to the light start position before doing the main ray trace to the surface. If there is no path from the centre to the light start, the ray fails.

@lawnjelly sorry, I missed this somehow.
I would keep the light_size property as a float because it will have forward compatibility with master, also most people just want to soften shadows, with a Vector3, they would have to set the 3 components to the same value, so it less usable for the common case.
Light leaking is most likely a problem here too (I haven't tested), but I'm a bit swamped with things to do right now. I think we can merge the PR as it is and add some optional checks if we see it reported often.

Thanks!


[BUG]  Web site broken link

Describe the bug
See screenshot
Steps To Reproduce
Go to web site, navigate off of home page then click on the Home button
Expected Behavior
No response
Operating System
MacOS
Browser
Google Chrome
Screenshots

Additional information
No response

Thanks Michael (@EasyG0ing1) for raising the issue :smile:!
Do you like to work on it?

Hey can I work on these .

Hey can I work on these .

Sure @Cvr421 ! You can work on this.

Ok thanks. I'll start working on that

@Cvr421 I think the error has gone (seems so from my end), after I re-deployed the website without making any notable changes in the code base. Please check if it's the same from your end.

Closing this issue as the error has got resolved (Verified by @Cvr421 in our discord server) by just re-deploying the Website.

@SaptarshiSarkar12 Yes the whole site seems to be working quite well now. Even the stats images seem to be working now.

@SaptarshiSarkar12 Yes the whole site seems to be working quite well now. Even the stats images seem to be working now.

That's great :star_struck: ! Thank you @EasyG0ing1 for the confirmation :grinning: .


YCSB Cassandra DBWrapper: report latency for each error is false and specific error codes to track for latency are: []

Hi,
The message "DBWrapper: report latency for each error is false and specific error codes to track for latency are: []" generates interference in benchmark execution?
How to solve?
Environment:
Ycsb 0.12.0
Cassandra 2.1.5, replication factor 2, 6 VMs
Java (TM) SE Runtime Environment (build 1.8.0_121-b13)
Debian 8.7.1
Command:
/opt/ycsb-0.12.0/bin/ycsb load cassandra-cql -p hosts = <IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS> -p port = 9042 -p Cassandra.username = cassandra -p cassandra.password = cassandra -threads 128 -P /opt/ycsb-0.12.0/workloads/workloada -s
recordcount=250000
operationcount=250000
workload=com.yahoo.ycsb.workloads.CoreWorkload
readallfields=true
readproportion=0.5
updateproportion=0
scanproportion=0
insertproportion=0.5
requestdistribution=zipfian
Thank you very much

This is just a warning and doesn't mean anything bad. It's a duplicate of #546 which is the issue for tracking this.

Thank you


Allow the migration function to be supplied directly

Summary
This Pull Request enhances the experience of using contentful-migration as a library, by allowing the migration function to be specified as a configuration option, rather than in a separate file.
Description
This Pull Request:

Adds a new configuration option migrationFunction, which accepts a function of type MigrationFunction
Updates the expected type of the RunMigrationConfig to expect either the filePath or the migrationFunction
If specified, the supplied migration function is used instead of importing the function from a file
Documents the new configuration option
Adds an example script to the /examples folder

Please note that I've changed the exported RunMigrationConfig from an interface to a type.
Motivation and Context
As it stands, contentful-migration is available for use as a library,  but a file on disk is still required to run a migration. I've added the ability to specify a migration function directly, so that contentful-migration can be used with existing programmatic migration toolchains. For example, I'm busy writing a Contentful storage provider for umzug (the migration tool that powers sequelize).
Todos

[ ] I'd love any suggestions on how to add appropriate automated tests for this functionality. The end-to-end test suite seems to mainly test the code as a CLI and there are not currently any unit tests for the runMigration function.

@rouanw this is a great addition 🎉


NonZeroInt interface

Description
Turn the type NonZeroInt to a serializable interface and implement it with a value class.
Checklist

[ ] Create the interface available internally only and implement it with a value class.
[ ] Implement unary operations in this interface.
[ ] Implement binary operations in this interface.
[ ] Implement conversions in this interface.
[ ] Replace the old type using a type alias.
[ ] Rename the interface, remove the type alias and make the interface publicly available.
[ ] Make the interface serializable.
[ ] Update Work in progress section in changelog.

The usage of value classes inheriting interfaces doesn't improve the performance.
We should wait for Kotlin to enable inheriting between value classes before using it for the hierarchy of integers...

In the integers hierarchy, we should keep this class as an inline class for performance purpose.


EAM API: remove appid from appinstance path

What type of PR is this?

enhancement/feature

What this PR does / why we need it:
Removes appId from the appinstances path. For retrieval, it becomes an optional parameter, allowing a single API call to get appinstances from different Apps. For delete, it is not necessary because appInstanceId is sufficient to identify the instance.
Which issue(s) this PR fixes:
Fixes #299
Special notes for reviewers:
Changelog input
 release-note

Additional documentation
docs

Hi @gainsley , one thing about this:
for the get and the delete method, looks good to me, but I have doubts about the post method, because if we make appId as optional how do we know which App is going to be instantiate??
If  we don't add the appId on the requested body, could we instantiate all the Apps by mistake,??

Hi @JoseMConde thank you for catching that, indeed my change made the appId and appZone optional which is wrong. I've added the required spec so that they are required. Thanks for reviewing!


Return empty string if no battery is present on the Mac

Return empty string if no battery is present on the Mac (as is the case on the Mac Pro)
Resulting topics on MQTT

Resolves this issue
./mac2mqtt
2023/01/10 19:29:46 Started
2023/01/10 19:29:46 Connected to MQTT
2023/01/10 19:29:46 Sending 'true' to topic: mac2mqtt/Nicks-Mac-Pro/status/alive
cf
panic: runtime error: index out of range [1] with length 0

goroutine 29 [running]:
main.getBatteryChargePercent(0xc000207ef0, 0x131a642)
	/Users/nick/mac2mqtt/mac2mqtt.go:284 +0x115
main.updateBattery(0x137df60, 0xc0001426c0)
	/Users/nick/mac2mqtt/mac2mqtt.go:290 +0x85
main.main.func1(0xc0001a4000, 0x137df60, 0xc0001426c0, 0xc0001a4050)
	/Users/nick/mac2mqtt/mac2mqtt.go:318 +0xe5
created by main.main
	/Users/nick/mac2mqtt/mac2mqtt.go:310 +0x1d0

Because the output of pmset is:
/usr/bin/pmset -g batt
Now drawing from 'AC Power'

I can confirm this works. Without this change, when I try to build and run the mac2mqtt binary on my Mac Studio I get the "index out of range" error as reported and immediately crashes. But this change mac2mqtt starts up just fine and functions correctly.


Documentation needed to interface with tackle-pathfinder from Tackle Inventory

Hi , @jonathanvila , @mrizzi , @carlosthe19916  I'm onboarding to the Tackle project along with @jortel and @mansam right now.
(Note: From demos I've seen, I think Pathfinder is already integrated with Tackle Inventory quite heavily. I am curious about the relationship between the two though, and how Pathfinder is currently consumed over what API. I'm asking these questions on all projects that Inventory is meant to interface with)
We are working to learn how the Tackle App Inventory can interface with other tools in the Tackle suite, and trying to define the requirements of the App Inventory data model.
It would be helpful to have a reference doc on the public interface of tackle-pathfinder (TPF) so that we can get an idea of how TPF this would tie in with Tackle Inventory, and what changes might be needed to the Tackle Inventory data model:

Expected inputs / outputs of TPF (examples would be useful)
Methods for invoking TPF (REST? CLI? Java API? Something else?)
Is there a Quay.io container auto-build set up so we can consume TPF easily running as a Pod on OpenShift?
Is there a deploy YAML available with a deployment definition for TPF and any required auxiliary OpenShift resources (e.g. namespaces, services, routes). This would let us quickly play around with TPF using other info provided. We may be able to assist here if needed.

Do documents detailing the public interface of TPF exist? Even some simple examples would be useful to get started.
cc @rromannissen @jwmatthews @PhilipCattanach

@djwhatle,
A great starting point for each project are the README files.
The Application Controls and Pathfinder have detailed README files.
Application Inventory, the Controls and Pathfinder are Quarkus microservices, they are not java libraries and hence there is no CLI or java API invocation method.
With regard to the container image there is a github action (https://github.com/konveyor/tackle-pathfinder/blob/main/.github/workflows/push.yml) that builds native image and pushes it to quay.io with the appropriate tag.
Within https://github.com/konveyor/tackle/tree/main/kubernetes there are templates that facilitate the manual deployment of Tackle to a Kubernetes/OCP environment. Remember Kubernetes is our primary target.
This is the unrecomended approach, I would strongly encourage you to use the Tackle Operator.
The best way to start understanding the expected inputs/outputs is to look at the tests (e.g. https://github.com/konveyor/tackle-pathfinder/blob/main/src/test/java/io/tackle/pathfinder/controllers/AssessmentsResourceTest.java#L80)
Quarkus also lets developers have the OpenAPI Rest Endpoints documentation page.


doc: update firewall configuration documentation

Update the existing documentation and add information for UFW.
Signed-off-by: Ruth Fuchss<EMAIL_ADDRESS>

Documentation preview available at: https://linuxcontainers.org/lxd/docs/pr.10328/

DNM - the UFW section needs rework (see comments).

DNM

DNM?

DNM

DNM?

Do not merge :)
Because of https://github.com/lxc/lxd/pull/10328#discussion_r865036150 , which needs to be clarified first.

I think we can simplify this now that we know the --direct firewalld commands don't work :)

Thanks! I reworked the structure now - hope I caught all changes.


simplify break condition for epoch ticker thread

It seems that the crossbeam channel was just being used as a way to exit the ticker loop. Once the sender was dropped, then try_recv would fail and the loop would break.
However, it also seems, based on the wasmtime docs that just upgrading a weak reference to the Arc should serve roughly the same purpose. Once all references to the Engine are dropped, then the loop should break.
If there was a reason to use a channel here because there are potential references to the Engine Arc I didn't catch in the codebase, then feel free to ignore.
Thanks!

However, it also seems, based on the wasmtime docs that just upgrading a weak reference to the Arc should serve roughly the same purpose. Once all references to the Engine are dropped, then the loop should break.

Seems a little fragile to me since any consumer could clone the Engine, but given the low impact of leaking this thread its probably fine. :shrug:
In any case I certainly can't remember why I pulled in crossbeam-channel for this. :thinking:

@lann this was also my thought... It does seem fragile, but should the ticker keep going as long as there is potentially something using the engine?
Open to reasons why this might be a bad idea, not sure how often the engine gets cloned. I mostly opened this as a learning exercise. If it simplified things, great. If it introduces an issue, I'm curious to know why.

Oh sorry, I should have added: I'm fine with merging this. :slightly_smiling_face: I saw that @rylev added himself as a reviewer and want to give him a chance to weigh in.

@lann all good, I think I caught that 😄
Another option I guess would be to store the handle to the thread and make sure it shuts down in a drop handler or something?

After reviewing how all of this is supposed to work I actually think this PR actually makes this crate safer to use: If a consumer of this crate wanted to shut down the engine (but not the entire process) while a guest instance was running, killing the epoch ticker thread could leave a misbehaving guest running indefinitely where it would normally be time out.
I don't think this is relevant to any of the actual Spin trigger handlers (which always terminate immediately after dropping the engine anyway), but on balance I think this is an improvement.

@lann and @rylev thanks for the review!
Thinking on it more, it might feel less fragile if this thread was owned by the same struct as the actual engine, inside the Arc, so it could be cleaned up on Drop. But this would have to be in wasmtime itself I guess and since it isn't always used in this mode might also not be the right place for it.
But I appreciate you guys taking time to validate the idea, glad it helps!


When the service is set to externalTrafficPolicy: Local, servers in the same network segment cannot request EXTERNAL-IP

When the service is set to externalTrafficPolicy: Local, servers in the same network segment cannot request EXTERNAL-IP,Only the node running the pod can request
[root@master01 ~]# kubectl get all -o wide
NAME                                  READY   STATUS    RESTARTS   AGE   IP                NODE     NOMINATED NODE   READINESS GATES
pod/layer2-openelb-858bb6d5ff-w6pvz   1/1     Running   0          17m   <IP_ADDRESS>   node01   <none>           <none>

NAME                 TYPE           CLUSTER-IP    EXTERNAL-IP       PORT(S)        AGE   SELECTOR
service/layer2-svc   LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   80:30708/TCP   17m   app=layer2-openelb

[root@node2 ~]# curl  <IP_ADDRESS> -I
curl: (7) Failed connect to <IP_ADDRESS>:80; 拒绝连接

[root@master01 ~]# curl  <IP_ADDRESS> -I
curl: (7) Failed connect to <IP_ADDRESS>:80; 拒绝连接

[root@node01 ~]# curl <IP_ADDRESS>   -I
HTTP/1.1 200 OK
Date: Mon, 09 Jan 2023 09:01:03 GMT
Content-Length: 190
Content-Type: text/plain; charset=utf-8

Version of Kubernetes:v1.23.8
Version of OpenELB:v0.4.4

There may be such a problem.
Let me tell you why. If your cluster has 2 nodes, A and B. When using layer2 mode, we will use round robin to disperse different svc/svcip to nodes to process traffic and balance them.

When creating a loadbalancer svc, if the pod is on A, the node that openelb allocates to handle the svcip is also A. There is no problem with external access;
If the pod is on A, but the node that openelb allocates to handle svcip is B. The traffic will be forwarded from B to A. Since externalTrafficPolicy: Local is set, cross-node access to svc is not allowed. so external access will fail.

If you use vip or layer2 mode, I suggest you set externalTrafficPolicy to Local.
If you use bgp mode, externalTrafficPolicy can be set to Local or Cluster.

If you only want to use layer2 mode, maybe we can solve it in the following way.
Assign eip to specific nodes, https://github.com/openelb/openelb/issues/310, and make sure that there is a pod replica running on each of these nodes.


Login page redesign

Goal
Since we already have blade components that I've created for a user profile page, it's a good idea to reuse them for other forms as well to make the platform look consistent.
Before and after comparison

Since these reusable blade components have validation messages attached to them when error happens, we have this out of the box:

I think that overall the login form now looks a bit better with the purple button, it matches the footer and the navbar:

Compare it to the current login form that looks like it's not from this website imo:

Register page will be redesigned in a separate PR since it's a different page.

💯👍


Windows

This pull request provides support for building ament_cmake and ament_python packages on Windows.
It provides .bat versions of .sh helper scripts like <package_name>__build.sh It also provides a new workflow for CMake which uses some custom options and calls out to msbuild rather than make for building and installing.
Connects to ros2/ros2#9

lgtm

In general when adding handling for special case (in this case Windows) I usually add the "special case" behind the code for the "common" case. Imo it makes the general code more easy to read.
In this case I would prefer:
if NOT IS_WINDOWS:
    # do common stuff
else:
    # do Windows specific stuff

The same for single line conditions:
ext = '.sh' if not IS_WINDOWS else '.bat'

I believe the comments have been addressed.

lgtm

+1


extract_leads_wfdb.py bug

Line 52 will report error.
recording_ids = set(full_lines[i].split(' ')[0].split('.mat')[0] for i in range(1, num_full_leads+1))
Suggest changing to
recording_ids = set(full_lines[i].split(' ')[0] for i in range(1, num_full_leads+1))

Thank you for this feedback. This check caught an inconsistency in the training data and has been removed. Please direct future feedback to the Challenge forum and email address.


How to scale AssetMarker  size?

No matter how big the image icon is, it is displaying smaller in the map. Am I doing something wrong?
Here is what I have tried:
My asset directory
-icons/marker.png
-icons/1.5x/marker.png
-icons/2.0x/marker.png

OSMFlutter(
      mapIsLoading: Center(
          child: Image.asset(
        'assets/images/loading.gif',
        height: 50,
      )),
      controller: mapController,
      onMapIsReady: onMapIsReady,
      showZoomController: true,
      initZoom: 19,
      markerOption: MarkerOption(
        defaultMarker: MarkerIcon(
          assetMarker: AssetMarker(
            image: AssetImage(
              'assets/icons/marker.png',
            ),
            scaleAssetImage: 2.0,
          ),
        ),
      ),
    )

on which platform android or ios ?

I just checked on Android and it's working fine. This issue is only for iOS.

yeah for ios i made with fix size because im using diff sdk
without size marker will not be shown in the map
i will add size marker for ios or i will do it internally i will see how to fix
i know about the probelm i alrrady create issue for it


Always validate email

Fixes https://github.com/aspnet/Identity/issues/1189
@ajcvickers

Actually I don't htink we can do this, since this would require emails

Tweaked, so we always validate emails that are provided, but only throw when they are missing if they are required


Output assets as links

Must be tested on OBS in Windows

Asset link won't be created on Windows unless TSH is given admin privileges. Here's a log extract:
QPixmap::scaleWidth: Pixmap is a null pixmap
set type font ['./assets/font/RobotoCondensed.ttf', './assets/font/RobotoCondensed.ttf']
set type font ['./assets/font/RobotoCondensed.ttf', './assets/font/RobotoCondensed.ttf']
set type font ['./assets/font/RobotoCondensed.ttf', './assets/font/RobotoCondensed.ttf']
set type font ['./assets/font/RobotoCondensed.ttf', './assets/font/RobotoCondensed.ttf']
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
Traceback (most recent call last):
  File "C:\Users\wolfy\Git\TournamentStreamHelper\src\StateManager.py", line 145, in CreateFilesDict
    os.symlink(os.path.abspath(di), f"./out/{path}" + "." + di.rsplit(".", 1)[-1])
OSError: [WinError 1314] A required privilege is not held by the client: 'C:\\Users\\wolfy\\Git\\TournamentStreamHelper\\user_data\\games\\multiversus\\base_files\\icon\\file_Shaggy_00.png' -> './out/score/team/1/player/1/character/1/assets/base_files_icon/asset.png'

Traceback (most recent call last):
  File "C:\Users\wolfy\Git\TournamentStreamHelper\src\StateManager.py", line 145, in CreateFilesDict
    os.symlink(os.path.abspath(di), f"./out/{path}" + "." + di.rsplit(".", 1)[-1])
OSError: [WinError 1314] A required privilege is not held by the client: 'C:\\Users\\wolfy\\Git\\TournamentStreamHelper\\user_data\\games\\multiversus\\full\\file_Shaggy_00.png' -> './out/score/team/1/player/1/character/1/assets/full/asset.png'

libpng warning: iCCP: known incorrect sRGB profile
Traceback (most recent call last):
  File "C:\Users\wolfy\Git\TournamentStreamHelper\src\StateManager.py", line 145, in CreateFilesDict
    os.symlink(os.path.abspath(di), f"./out/{path}" + "." + di.rsplit(".", 1)[-1])
OSError: [WinError 1314] A required privilege is not held by the client: 'C:\\Users\\wolfy\\Git\\TournamentStreamHelper\\user_data\\games\\multiversus\\base_files\\icon\\file_Batman_00.png' -> './out/score/team/2/player/1/character/1/assets/base_files_icon/asset.png'

Traceback (most recent call last):
  File "C:\Users\wolfy\Git\TournamentStreamHelper\src\StateManager.py", line 145, in CreateFilesDict
    os.symlink(os.path.abspath(di), f"./out/{path}" + "." + di.rsplit(".", 1)[-1])
OSError: [WinError 1314] A required privilege is not held by the client: 'C:\\Users\\wolfy\\Git\\TournamentStreamHelper\\user_data\\games\\multiversus\\full\\file_Batman_00.png' -> './out/score/team/2/player/1/character/1/assets/full/asset.png'

@Wolfy76700 does it work now? I'm not sure, but I think this is faster than using the previous file copy command. From what I understand, it's really a "link" even though it doesn't appear as a shortcut.


dump with insert if not exist

i want to ask, what option when i want to dump data with insert if not exist?

i think to add INSERT IGNORE INTO to buildInsert fuction , how about u?

There is no way to do this currently.
Happy to accept a PR!


Ignore AMD integrated GPUs

Fixes #2054
Integrated GPUs (APUs) from AMD may be reported by ROCm, but we can't run on them with our current llama.cpp configuration.  These iGPUs report 512M of memory, so I've coded the check to ignore any ROCm reported GPU that has less than 1G of memory.  If we detect only an integrated GPU, this will fallback to CPU mode.  If we detect multiple ROCm GPUs, meaning one or more are discrete, and one is integrated, we'll now set ROCR_VISIBLE_DEVICES so we ignore the iGPU.  If the user has explicitly set ROCR_VISIBLE_DEVICES we'll respect their setting.

Is this related to https://github.com/ollama/ollama/issues/2277?
If so, when can we expect this pull to be integrated into a release?

This was included in 0.1.22.

Please let us use internal GPU again by switch. I'm sure i get some performance gain with my AMD 5800U CPU, thanks.

Please let us use internal GPU again by switch. I'm sure i get some performance gain with my AMD 5800U CPU, thanks.

@DocMAX can you file a new issue to track this?  We're still having a hard time finding the right compat matrix approach to ensure we don't crash on unsupported GPUs.  Unfortunately ROCm seems to be unforgiving when the device isn't supported.

@dhiltgen  the AMD iGPU780M could work on ROCm with extra settings in Linux. Please see my pull request https://github.com/ollama/ollama/pull/5426


Feature: Provide docker images for users

Describe the solution you'd like
Let's build public Docker images with N latest Python versions. These images can be interpret as recommended for any user of Faststream.
Feature code example
Add building images into CI/CD pipeline.
Additional context
Possible huge time economy for building custom user images, based on recommended ones. Quite useful for rapid development and testing too.

@AbstractiveNord What is the benefit?

Official pre-build images is quite useful for MREs, ad-hoc development or troubleshooting, also images simplify first move with FastStream for newcomers.


Update README.md

Updates README to reflect the current status of the repo.  @kayur  and @minrk  can you take a quick look at the wording?

:+1:


ETL speed issue

OrientDB Version

v2.2.11

Operating System

Windows 7 Pro 64bit

Hardware

Laptop with i7-4510U, 8GB, SSD

I'm trying to import two csv files into an empty database. First I've used a small csv files (about 1000 vertices and 2000 edges) and the ETL process was done in few seconds. Now I'm running the same json on the bigger files (4 mio vertices and 10 mio edges), had no problems with importing vertices but the edges import is extremely slow (very similar to https://github.com/orientechnologies/orientdb/issues/5508 )
My speed results:
extracted 537 records (0 records/sec) - 537 records -> loaded 36 vertices (0 vertices/sec) Total time: 2155503ms [0 warnings, 0 errors]
ETL command: oetl.bat payment_big.json payment_big_create.json
Below are my json files and the headers of the csv files (in xlsx format):
payment_big.json
{     "config": {         "log": "info",         "fileDirectory": "G:\orientdb-community-2.2.11\emp\datasets\\",         "fileName": "pmts_big.csv"     } }
payment_big_create.json
`{
"begin": [
    { "let": { "name": "$filePath",
               "expression": "$fileDirectory.append($fileName )"
             }
    },
],

"config": { "log": "info"},
"source": { "file": { "path": "$filePath" } },
"extractor": { "csv": { "ignoreEmptyLines": true,
                        "nullValue": "N/A"
                      }
             },

"transformers": [
        { "merge":  { "joinFieldName": "payer", "lookup": "client.name" } },
        { "edge":   { "class":         "transactions",
                      "joinFieldName": "receiver", "lookup": "client.name",
                      "direction":     "out",
                      "edgeFields": { "AmountEUR": "${input.AmountEUR}", "industry": "${input.TransIndustry}" },
                      "unresolvedLinkAction": "NOTHING"
                    }
        },
        { "field": { "fieldNames": ["payer", "receiver"], "operation": "remove" } }
    ],

"loader": {
    "orientdb": {
        "dbURL": "remote:localhost/test_big",
          "serverUser":"admin",
        "serverPassword":"admin",
        "dbType": "graph",
        "batchCommit": 1000,
        "useLightweightEdges": false,
        "classes": [
            { "name": "transactions",   "extends", "E" }
        ],
        "indexes": []
    }
}

}
`
example.xlsx

If this is a one-shot import, my suggestion is to use plocal access working embedded, then switch on the server.

Yes, this is one time import.
I have done this with plocal instead of remote - same result.
Added "parallel" - get three times more rows per tick but still very few vertices per second.
Maybe the problem with the index in the already imported vertices?

I have solved the problem by adding index to the joining field.
Get speed on the big file 10000 vertices/s for vertex import and 1500 vertices/s for edge import.


Add fuzz target for rustfmt crate

Cf. #24

This crashes after <1s, with and without seeds. For more info, see #24

bors r+


Inconsistent documentation for build parallelism

The crate-level doc says that:

If NUM_JOBS is not set, the RAYON_NUM_THREADS environment variable can
also specify the build parallelism.

However in default_jobserver(), only NUM_JOBS is used but not RAYON_NUM_THREADS.
It seems like this is an outdated documentation, but I'm not entirely sure so I opened this issue.

I will open a PR to remove this.


Add in ePDQ screenshots

Added in ePDQ screenshots to ePDQ section. A google doc with these screenshots has already been reviewed by Rory.

Completely agree and I tried to make it consistent; however the numbered bullets would break for some reason in some cases depending on where I put the screenshots. I will investigate if I can today and let you know.

I don't know if my experience helps but...
I would tend to put the image first - I think the user will scan the image,
either consciously or subconsciously ('F' scan pattern), before reading the
written instruction.  [I think] this image pre-scan gives the user some
context for the written instruction and possibly some prior
understanding before they read the text, which requires a slightly
different cognitive set.
Best regards
Neil
--
*Neil Bookless *
Technical Author, GOV.UK Verify
GOV.UK Verify https://identityassurance.blog.gov.uk/ | @GOVUKverify
https://twitter.com/GOVUKverify
The White Chapel Building | 10 Whitechapel High Street | London | E1 8QS
M: +44 (0) 7748 377 970
On 6 September 2017 at 09:06, Jonathan Glassman<EMAIL_ADDRESS>wrote:

Completely agree and I tried to make it consistent; however the numbered
bullets would break for some reason in some cases depending on where I put
the screenshots. I will investigate if I can today and let you know.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/alphagov/pay-tech-docs/pull/32#issuecomment-327408033,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AcuA4duDx_dy-W58KNmoUllbNaL_ejUWks5sflJ8gaJpZM4PNEiH
.

Neil, I agree, I will try to figure out why putting the image before the ordered list sometimes breaks the formatting and make it consistent. Not sure if it's the tech doc tool or markdown.


docs: Move metadata back to packages

The workspace one is not picked... no idea why & how
cc @sdroege

You also create PRs for gtk4-rs and gstreamer-rs?


http_11_proxy: Make inner transport_socket config optional

http_11_proxy: Make inner transport_socket config optional
Given that the top-level Cluster.transport_socket field is optional and defaults to plaintext, this should also be optional. gRPC is adding support for this transport socket, but they do not have a raw_buffer to explicitly configure. See https://github.com/grpc/proposal/pull/455#discussion_r1776143739 for additional context.
Risk Level: Low.
Testing: Existing tests.
Docs Changes: n/a
Release Notes: Done.

Also, tests seem to be failing
/wait

Also, tests seem to be failing
/wait

The failure isn't related to this PR:
================================================================================
INFO: Elapsed time: 2312.606s, Critical Path: 1217.31s
INFO: 26910 processes: 11952 remote cache hit, 11870 internal, 1 local, 2 processwrapper-sandbox, 3085 remote.
//test/integration:load_stats_integration_test                           FAILED in 377.3s
  /build/bazel_root/base/execroot/envoy/bazel-out/k8-dbg/testlogs/test/integration/load_stats_integration_test/test.log

Thanks for doing this!
Does the Envoy implementation need to be changed to default to plaintext if this field is unset?

@markdroth no change was required to the implementation.

/lgtm api
Thanks!

Please fix the build:
envoy/extensions/transport_sockets/http_11_proxy/v3/upstream_http_11_connect.proto:8:1:Import "validate/validate.proto" is unused.```

/retest
unrelated example flake

/retest
(https://github.com/envoyproxy/envoy/issues/36494)


pull request for e2e test at 11/17/2016 03:56:02

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update with more Support Info vs Linux

We had a case come into CSS about this feature on a Linux OS (SQL Linux), and since this article didn't mention Linux directly it was hard to find that it was not supported.

@EricBuMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Example fix only suited to Windows 10+

Warning C30029's advice to use non-executable memory is excellent, but the example given on the page uses an API that is only available in Windows 10 or later. Advice on addressing this issue for drivers that must be compatible with earlier OS versions would be appreciated here: should the warning simply be suppressed, or is there another strategy that can be used to provide a mapping to non-executable memory prior to Windows 10?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cdbcb5a3-69e2-aa09-7311-cdc7dce8c04a
Version Independent ID: cb040cf8-4b38-7cfe-7918-c08ca0cddc16
Content: C30029 warning - Windows drivers
Content Source: windows-driver-docs-pr/devtest/30029-memory-allocating-function-requests-executable-memory.md
Product: windows-hardware
Technology: devtest
GitHub Login: @DOMARS
Microsoft Alias: domars

This particular channel is monitored by the men and women who write the driver documentation posted on docs.microsoft.com/drivers. Though we'd like to, we don’t have the resources to provide support for specific scenarios.
I don't know a way to duplicate this functionality with previous versions of Windows, but it would seem that it should be possible. There may be a way to check the memory to see if it is execute, but you would need to do that carefully. Perhaps something like the ProbeForWrite function, although that seems to check user mode memory. There may be some related information in NX Pool Compatibility Issues, although that is for pool memory.
Your best bet is to use one of the forums where other driver developers and Microsoft engineers can be found. For example, the Hardware and Application Developers on Q&A. You can post your question there, and the community of developers usually give feedback fairly quickly.


Update GitHub Actions

This PR bumps GitHub Actions to their latest major versions, which now use Node 16 internally instead of Node 12 (EOL as of end of April 2022, no longer receives security updates):

Changelog for actions/checkout can be found here
Changelog for crazy-max/ghaction-github-pages can be found here
Changelog for github/codeql-action actions can be found here
Releases for actions/setup-node can be found here

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Bitwarden: Investigate Bitwarden Unified Deployment

Install and Deploy - Unified (Beta) | Bitwarden Help Center

Little advantages over Vaultwaren. Certain features like TOTP-codes & Duo are also paywalled.


prepare for flat packaging

Current coverage is 100% (diff: 100%)

Merging #17 into master will not change coverage

@@           master   #17   diff @@
===================================
  Files           2     2
  Lines          34    34
  Methods         1     1
  Messages        0     0
  Branches        8     8
===================================
  Hits           34    34
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 809e6e1...24918e4


Feature Request: Use non-optional properties in types

Is your feature request related to a problem? Please describe.
I've been using the types from this module - they've been very useful, so thank you. Lately I've been having to work around the optional properties (example). TypeScript gives me errors such as:

Argument of type 'string | undefined' is not assignable to parameter of type 'string'.
Type 'undefined' is not assignable to type 'string'.

Object is possibly 'undefined'.

Type 'undefined' cannot be used as an index type.

This is because every property (that I've seen) is optional, which means that something which should be type e.g. string is actually inferred to be type string | undefined, requiring use of type casts (modeName as string), non-null assertions, and/or optional chaining operators (stopPointsOnLines?.[modeName!]?.[line]).
Do they need to be optional? In my experience, the TFL API always returns something for each field, even if that's just an empty value (e.g. empty list), and if some field is missing, we might not want to just continue as though there were no issues. There may be some optional fields in TFL's spec, but I feel as though these would be the exception, rather than the rule.
Describe the solution you'd like
I propose making most, if not all, of the properties non-optional, so e.g. TfL['Mode'] would go from:
Mode: {
        isTflService?: boolean;
        isFarePaying?: boolean;
        isScheduledService?: boolean;
        modeName?: string;
    };

to
Mode: {
        isTflService: boolean;
        isFarePaying: boolean;
        isScheduledService: boolean;
        modeName: string;
    };

This would mean that instead of e.g. (property) isTflService?: boolean | undefined, we'd just have (property) isTflService: boolean, instead of needing to implement some way of telling TS it shouldn't be undefined for each property.
Describe alternatives you've considered
Workarounds as above, but this feels somewhat hacky/clunky.
Additional context
This information is based on my experience of using VSCode and create-react-app on Windows.

The only problem with this is that the types are auto generated from the swagger file, this means that I would have to reimplement custom types.

Swagger file, for reference
Couple of questions:

How is this used to generate the types?
At which point does the "optional" aspect get introduced?

re: compiling my app, is there anything in particular giving you trouble?

How is this used to generate the types?

I don't remember the exact name but there is a TypeScript tool

At which point does the "optional" aspect get introduced?

I assume it's when the types are actually generated

re: compiling my app, is there anything in particular giving you trouble?

No problems now, all sorted!

I've been having a look around [1] [2] [3] and it looks like the response definitions are missing the required field in TfL's swagger file.

Looks like this might have been the tool: https://www.npmjs.com/package/openapi-typescript
It also looks like the swagger file might be outdated (see here (dates erroneously in query instead of path, like in the swagger file) vs here (dates in path as intended - doesn't match the file)). I'm just going to make my own version to use.

Reopened to track adding custom types back, instead of using the swagger file to generate them, they will be maintained in this repo. (This is how it was done previously).

export module GetByIDs {
    export interface Root {
        naptanId: string;
        modes: string[];
        icsCode: string;
        stopType: string;
        stationNaptan: string;
        lines: Line[];
    }

    export interface Line {
        $type: string;
        id: string;
        name: string;
        uri: string;
        type: string;
        routeType: string;
        status: string;
    }
}

import * as IStopPoint from './interfaces/stopPoint'

getByIDs(ids: Array<string>, includeCrowdingData: boolean): Promise<Array<IStopPoint.GetByIDs.Root>> {
    return this.sendRequest(`/StopPoint/${TfLAPI.arrayToCSV(ids)}`, { includeCrowdingData }, 'GET');
}

This is how the types were done before, but I'm pretty sure it abuses TypeScript doing it this way. I thought about just removing all the optional properties from the current setup, do you think this is viable solution?

I'm quite new to TypeScript, so not qualified yet to say whether that's good practice or not.
What do you mean by removing all optional properties - just removing the ? after each property? That would be a viable solution (assuming that all responses should contain all properties - which I think is a valid assumption).
I think that would work, but I think it would be much better to have a fixed Swagger file to generate the TS from. I started work on one here, and I've also found this one from 5 years ago (haven't looked at it yet). I've also just created a thread on the API forums to see if any better Swagger file can be made available.

I think adding "required: [{field1}, {field2}, ...]" to each definition should work - the change I made in this example, along with the same change for a couple of other definitions, has rendered the corresponding TypeScript definitions non-optional.

This should work as a solution, though it will require some refactoring - Line's Tfl-3 definition is different from Journey's Tfl-3 definition, so each API (line, journey etc) would have to be stored in different files. I can provide the converted per-API files with the required fields added if you need (though it may take a little bit of time) - just let me know.


QIR runtime heap alloc and heap free functions should be removed

The QIR runtime currently includes functions for allocating and freeing memory from the heap:
https://github.com/microsoft/qsharp-runtime/blob/380003f44cea08ae0b91132ad168ea34ba56297d/src/Qir/Runtime/lib/QIR/bridge-rt.ll#L124
https://github.com/microsoft/qsharp-runtime/blob/380003f44cea08ae0b91132ad168ea34ba56297d/src/Qir/Runtime/lib/QIR/bridge-rt.ll#L129
These two methods are neither part of the QIR specification, nor are they used anywhere in the runtime implementation or in QIR generation, making them dead code. If we expect them to be needed in the future then we should update the QIR spec to describe their intended use, otherwise we should remove them and the underlying support to avoid the cost of maintaining them.
@bettinaheim @alan-geller @kuzminrobin FYI.

I would love to work on it. @swernli.

Thanks @Patil2099! Always happy to see involvement from the community! Just as a heads up, we may end up deciding to keep the functions, depending on feedback from the rest of the team on whether removal is the right way to go. I'll follow up on the PR with feedback there, and if the issue is triaged and accepted we can use your PR to resolve it.

Sounds like we have consensus that this is a good removal to make. Removing needs triage label.


Add more Go samples for BigQuery:

bigquery_extract_table
bigquery_extract_table_json
Additionally, make error reporting in snippet_test.go more informative.

test failure appears to be infrastructure related (lack of free test projects available for lease) rather than a code failure


Get Volume not working on webOSTV 5.0

I have 2 LG TVs, this integration works great with my older 49uj6565 which runs webOSTV 3.5. When I call get_volume the payload is:
{'returnValue': True, 'volumeMax': 100, 'muted': False, 'scenario': 'mastervolume_tv_speaker', 'subscribed': True, 'volume': 9, 'action': 'requested', 'active': False}

But on my LG CX running webOSTV 5.0 I get a different payload:
{'volumeStatus': {'activeStatus': True, 'adjustVolume': True, 'maxVolume': 100, 'muteStatus': False, 'volume': 9, 'mode': 'normal', 'soundOutput': 'tv_speaker'}, 'returnValue': True, 'callerId': 'secondscreen.client'}

so payload.get("volume")  fails, since there's a new volumeStatus  object.
I'll open a PR with the fix shortly

Thanks @bendavid ! Can we release a new version with this change to pip?

I wanted to consolidate a bit the config file handling to avoid breaking backwards compatibility before releasing a new version.  If you open a PR to the 0.3.x branch I can release a new version from there at least.


feat: variable buffer size

Added this functionality to complement zezo357's PR (#123) adding the ability to control MPV demuxer-max-bytes argument which is previously was fixed to 32 MB.
This is useful for network streams, where it can prevent playback from stalling or consuming too much bandwidth.
Changes made:

Added bufferSize to PlayerConfiguration with the default value of 32 MB.
Updated test example with the new configuration argument.

Tested on macOS
Tested video here.
Using the default 32 MB buffer size

Using 5 MB buffer size

Off topic: Too bad there isn't a "FileSize" class equivalent to Duration in Dart to have a better representation of byte sizes…

Off topic: Too bad there isn't a "FileSize" class equivalent to Duration in Dart to have a better representation of byte sizes…

Is that available on Flutter for Web?

Is that available on Flutter for Web?

I don't think so.

Off topic: Too bad there isn't a "FileSize" class equivalent to Duration in Dart to have a better representation of byte sizes…

Using bit manipulation will be more practical but less intuitive. 1 << 10 for KB, 1 << 20 for MB, and so on.
Duration has so many calculations that you do need unlike file sizes which are pretty straightforward.
BTW: I really like your package/tool, How can I help contribute to it more when I can?

@AhmedAbouelkher

BTW: I really like your package/tool, How can I help contribute to it more when I can?

Thanks! You're making me tear eyed. 🥲
We are still working on the first stable version of the media_kit, which will work on all platforms i.e. Android, iOS, Windows, Linux, macOS & Web. See: #114 for the plans for first 1.0.0 release. By the end of this month, we will be ready for 1.0.0.
Even though current version of library works, we are still working on things. An important & easy-to-work with issue is adding pre-built controls to Video widget for everyone to use. The video controls from YouTube look good & is how we want them to be like.
You may help us speed up things with your contributions.
You may join our Discord server for development to get in further touch: https://discord.gg/h7qf2R9n57
Thanks again!


Chapter1/homework/8

I implemented new functionality to repair and handle parsing of the corrupted balances file.

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 3
- Added 4

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/FilesUtility.cs  2
- Src/BootCamp.Chapter/BalanceStats.cs  7
- Src/BootCamp.Chapter/TextTable.cs  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 6
- Added 3

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/FilesUtility.cs  2
- Src/BootCamp.Chapter/BalanceStats.cs  7
- Src/BootCamp.Chapter/TextTable.cs  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 6
- Added 10

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/FilesUtility.cs  2
- Src/BootCamp.Chapter/BalanceStats.cs  7
- Src/BootCamp.Chapter/TextTable.cs  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 6
- Added 7

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/FilesUtility.cs  2
- Src/BootCamp.Chapter/BalanceStats.cs  7
- Src/BootCamp.Chapter/TextTable.cs  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 6
- Added 2

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/FilesUtility.cs  2
- Src/BootCamp.Chapter/BalanceStats.cs  7
- Src/BootCamp.Chapter/TextTable.cs  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 6
- Added 2

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/FilesUtility.cs  2
- Src/BootCamp.Chapter/BalanceStats.cs  7
- Src/BootCamp.Chapter/TextTable.cs  4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 6

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/FilesUtility.cs  2
- Src/BootCamp.Chapter/BalanceStats.cs  7
- Src/BootCamp.Chapter/TextTable.cs  4

See the complete overview on Codacy