[IR3] Graphene recipe does not show helium as an ingredient

Problem Description
I added the Graphene recipe to a subfactory, and the planner did not pick up helium as an ingredient or byproduct.
My guess is that this is due to the recipe having 2 catalysts, or due to the helium input and output being balanced.
Reproduction

Start a game with IR3
Create a subfactory for Graphene
Ingredients show plastic and liquid nitrogen, with a byproduct of nitrogen. Helium should be both an ingredient and a byproduct, but isn't.

Actually there's a good chance this is "not a bug". The recipe uses net zero helium. I guess it depends on what the purpose of Factory planner is. Maybe this a feature request to show net zero ingredients in both the inputs and outputs, but with zero quantity, to show that it's necessary for bootstrapping.

Yeah this is a known 'issue', the mod should really show the catalyst amounts in some way. It's on the todo list #91. I'll close this issue as duplicate in a while if there's no further comments :)

I agree it's a dupe. I'm happy for it to be closed as one.


iOs status-bar glitch

Is your feature request related to a problem? Please describe.
When ios app uses visible status-bar then when image is opened in photoiewer then status-bar starts becaming hidden and when I got back - status-bar appeared again but my ionic app is getting up and down. It's very annoying.
I modifyed code in OneImageViewController.swift file:
override var prefersStatusBarHidden: Bool {
  //return true
  return false
}

it's better but in this case images are rendered behind status-bar with transcluent background - it's visually like some kind of bug.
Describe the solution you'd like
option to hide status-bar or not with image rendering below of status-bar.

@ivanov84 have you had a look to angular-photoviewer-app. Do you have that issue. Could you share a repro app with the issue so i can look at it

@ivanov84 Did you find a solution for this?

@jepiqueau I used code that mentioned above. It's not very nice, but it's ok.


RuntimeError: CUDA out of memory. Tried to allocate

Did anyone face the same issue as below?
Traceback (most recent call last):
File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/-/BtcDet/btcdet/datasets/multifindbestfit.py", line 494, in
find_best_match_boxpnts(all_db_infos_lst, box_dims_lst, sorted_iou, pnt_thresh_best_iou_indices, mirrored_pnts_lst, pnts_lst, coords_num, occ_map, bm_dir_save_path, allrange, nx, ny, voxel_size, max_num_bm=max_num_bm_lst[i], num_extra_coords=num_extra_coords_lst[i], iou_thresh=iou_thresh_lst[i], ex_coords_ratio=ex_coords_ratio_lst[i], nearest_dist=nearest_dist_lst[i], vis=vis, save=save)
File "/home/-/BtcDet/btcdet/datasets/multifindbestfit.py", line 330, in find_best_match_boxpnts
bm_pnts, bm_coords_num = find_multi_best_match_boxpnts(selected_sorted_iou, cur_box, cur_mirrored_pnts_lst, cur_pnts_lst, selected_mirrored_pnts_lst, selected_pnts_lst, selected_pnt_thresh_best_iou_indices, cur_occ_map, selected_occ_map, max_num_bm=max_num_bm, num_extra_coords=num_extra_coords, iou_thresh=iou_thresh, ex_coords_ratio=ex_coords_ratio, nearest_dist=nearest_dist, vis=vis)
File "/home/-/BtcDet/btcdet/datasets/multifindbestfit.py", line 375, in find_multi_best_match_boxpnts
mean_instance, min_instance, max_instance = get_batch_stats(dist_l1, box_num_pnts_tensor, box_mask_tensor, box_reversemask_tensor)
File "/home/-/BtcDet/btcdet/datasets/multifindbestfit.py", line 351, in get_batch_stats
addmax_dist = masked_dist - reversemask_arry
RuntimeError: CUDA out of memory. Tried to allocate 198.00 MiB (GPU 0; 10.92 GiB total capacity; 8.94 GiB already allocated; 128.69 MiB free; 9.86 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

You should run this code on a PC that has more VRAM

Hi,
Thanks for your comment.
Do you have any idea about minimum VRAM requirement for this code?
The PC where I'm running this code has a VRAM (prefetchable, size 256M ). Is that not sufficient?

At least 12GiB VRAM for training, 256M is impossible for training any SOTA performance model

Yes, it is clear now. first I used VRAM with a total capacity of 10.91GiB, which caused this error.
Now when running on a higher capacity one it is working fine!


Unable to properly view the documentation on brave

📚 Documentation
My browser is Brave [Version 1.58.124 Chromium: 117.0.5938.62 (Official Build), When I scroll down on any page, the content gets hidden behind the side pane. For example, when I open this link, I can see the following

I have tried zooming out, but it doesn't work.
cc @borda

@willtryagain Sorry about the inconvenience. It should be fixed now, but it might need a hard refresh because of the caching mechanism in the browser. (Ctrl+F5 or hold shift + click reload button in browser).

this shall be resolved by #18751 for stable and #18764 for latest


docs: add sessions usage

🔗 Linked issue

fix #1444
❓ Type of change

[x] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

(put on draft to work on some refactors before officially adding the session page)


Strange characters in page title

Not a real problem but just wondering what might cause these weird characters to appear in both Webmin/Virtualmin & Usermin page titles

Read Troubleshoot on main page please. It's non UTF encoding issue.


Cycada/Cider?

Can you release the software on GitHub with source code, documentation, packages, tutorial on installing .ipa files, upload the ipa files you extracted to archive.org, and the shortcut and ciderpress .apks? And the closed source frameworks from apple put it on Acrhive.org, which is excluded from most copyright. If you are concerned about copyright to a big extent, email the files to<EMAIL_ADDRESS>which i will manage copyright and if Apple sues me, i will manage it.
https://systems.cs.columbia.edu/projects/cycada/
https://systems.cs.columbia.edu/files/wpid-asplos2014-cider.pdf

The software is about 8 years old now. Releasing it would be good for future contributions. I was searching and contacting for this program for about a month now.

Sorry, I can't help about that project, which is not related to PrivateKube.


Uncommon memory consumption with Sockets

I updated the reliability tests to use Sockets now that it's the default transport.
The memory consumption seems to grow, I would wait for more days to make any conclusion.

The first line is with Libuv, the one on the right is with Sockets.
NB: Right now I can't track the changes as EF has an issue on the latest bits.

How long did this take to reproduce? Or is this a chart across multiple builds?

Can you link to the test you were using?

DbFortunesMvcEf scenario in benchmarks.
It's a long run, the right one lasted a little more than one day. The left one is over many days.

Why is the left graph so stable. Is that using the libuv transport instead of sockets? A horizontal axis and a vertical axis starting at 0 would be nice.

The first line is with Libuv, the one on the right is with Sockets.

A horizontal axis and a vertical axis starting at 0 would be nice.

https://aka.ms/aspnet/benchmarks
Please help yourself

Cool. So we're looking at a zoomed in version the following graph from page 6 of 8?

How do I know which color line corresponds with which configuration without asking you? I only see time-related info in the hover text.

@sebastienros could you help with reading the graph?  Thanks.

I'll update the graph when I have more log, which hasn't run for many days, then I will explain.

Update: it's getting worse.
I took a memory dump this morning, and will do another one this afternoon.

Details on current run:
[08:11:42.717] SDK:                         2.2.0-preview1-007522
[08:11:42.717] Runtime:                     2.1.0-preview2-26325-03
[08:11:42.717] ASP.NET Core:                2.1.0-preview3-32064

Can we figure out if this affects preview2 bits please? I think the runs are on latest (so preview3 given how long ago we branched) but given the leak shows up as soon as we switched to sockets there's a good chance it affects preview2 as well (which is obviously super high priority).

@sebastienros can you share dump info as soon as you have it please?

Way ahead of you ;)
On Thu, Apr 5, 2018 at 11:44 AM, Sébastien Ros<EMAIL_ADDRESS>wrote:

Solved on my side, please close
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/KestrelHttpServer/issues/2416#issuecomment-379037986,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADUcbUeVuQNvoBowJ9xN2fkWD3xbbDxks5tlmYqgaJpZM4S3mzl
.


chore: extract manySmallTxsWithoutRandomness

Addresses https://github.com/celestiaorg/celestia-app/pull/781#discussion_r991585484

Codecov Report

Merging #855 (1af83fb) into main (be5406b) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #855      +/-   ##
==========================================
+ Coverage   25.59%   25.61%   +0.02%
==========================================
  Files          75       75
  Lines        9273     9272       -1
==========================================
+ Hits         2373     2375       +2
+ Misses       6677     6675       -2
+ Partials      223      222       -1

Impacted Files
Coverage Δ

pkg/prove/proof.go
83.56% <ø> (-0.12%)
:arrow_down:

pkg/da/data_availability_header.go
81.14% <100.00%> (+2.45%)
:arrow_up:

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


Node js Application Fails on Launch Debugger

VSCode Version: 1.18.1
OS Version: Windows 8
Node: v9.0.0

Steps to Reproduce:
Hit f5 to launch your node js application.
Launch Configurations:
{
        "type": "node",
        "request": "launch",
        "name": "Launch Program",
        "program": "${workspaceRoot}\\main.js"
    },

On launch I get the following error:
util.js:976
throw new errors.TypeError('ERR_INVALID_ARG_TYPE', 'superCtor', 'function');
^
TypeError [ERR_INVALID_ARG_TYPE]: The "superCtor" argument must be of type function

This problem started occurring when I updated node. Is there any way this problem can be solved?

And your program does not crash with node.js v9.0 when running outside of VS Code?
(The exception looks like a problem/incompatibility in your program and not a problem with VS Code).

Hi Weinand,
Hope you well.
I managed to resolve the issue. It did not have to do with VS Code as you suspected.
I ended up proceeding with the following:

Updating VS Code.
Cleaning all my node modules
Reinstalling node

I did not actually suspect at the beginning that it might have been an problem/incompatibility, but I see now that from the error message it is directly referring to the spdy library which should've made me realize this initially. After digging a bit I found zetta js is dependent on this library and this is how it made its way into the solution. I am having different battle now with with spdy and zetta library.
Thank you very much for your help, much appreciated.

I recommend to stay with the LTS version of node (v8.9.1 at the moment).


Web editor Issue

Hello,
I have an issue when I reconfigure my gogs from simple execute program into windows service.
I found I cannot successfully edit markdown files on the web editor anymore. Every time I finished editing and commit the change online, nothing happens. But I found in dashboard, there is a commit history for my change, while if I click on the MD5 link for the commit, the page leads me to the latest commit that I pushed from client which is different from the right one.
I guess it may have something to do with some permission setup for I changed gogs into Windows service. But I can create new repository, which means gogs has the permission to write the repository folder, and also the sqlite db because the new repository information can be shown normally on the web site.
I am using Windows server 2012R2, and my gogs version is <IP_ADDRESS>5.
Thanks in advance.
Update:
To avoid any influence of the reverse proxy setup I made on the IIS of the server, I downloaded latest release and install it on another server on which there is no special IIS settings. And I followed the guide to set the gogs on the new server as windows service and I found the problem still remains, I can push commits to the server but changes made in web editor doesn't work. Please note that on dashboard there is new commit change history related to that made by web editor, but it cannot be found in the repository pages,

Hi, if there is an error, this is a log. If there is no log message, I can't help you much...


Initial

The point of this repo is to make the code here usable elsewhere, e.g. pixel.
Starting with the absolute basics. More PRs to follow.

:sparkles: No lint errors found. :sparkles:

:sparkles: No lint errors found. :sparkles:

:sparkles: No lint errors found. :sparkles:

:sparkles: No lint errors found. :sparkles:

:+1:


Syntax highlight code samples

Should work on GitHub and PyPI, based on https://github.com/moreati/pypi-rst-ref

Thank you! I didn't know that worked on PyPI. Your citation of pypi-rst-ref made it an easy review. Cheers!


chore(deps): update pre-commit hook bridgecrewio/checkov to v3.0.34

This PR contains the following updates:

Package
Type
Update
Change

bridgecrewio/checkov
repository
patch
3.0.32 -> 3.0.34

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.

Release Notes

bridgecrewio/checkov (bridgecrewio/checkov)
v3.0.34
Compare Source
v3.0.33
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

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


WebGL doesnt work

Does the WebGL code work? from what I understand, its not possible to link C# and Rust in WebGL WASM without JS interop in between (js pre/jslib)?

The example code works in WebGL.


High Scores: tests should check for mutated arrays

I've talked with a couple fellow learners about this exercise and notice the tests don't check for mutated arrays. This allows for our code to pass all the tests while being flawed due to mutated arrays. Here's an example of a solution with a bug:
export class HighScores {
  constructor(input) {
    this.scoresArray = input;
  }

  get scores() {
    return this.scoresArray;
  }

  get latest() {
    return this.scores[this.scores.length-1];
  }

  get personalBest() {
    return Math.max(...this.scores);
  }

  get personalTopThree() {
    return this.scores.sort((a,b) => b-a).slice(0, 3);
  }
}

If we look at the latest getter, we see it just grabs the last score in the scoresArray. However, in the personalTopThree getter, it uses .sort() to get the top three scores, mutating the scoresArray. This will cause the latest getter to return a different score once called again.
It's a valuable opportunity to teach about mutability (I've also seen some solutions utilizing .pop() and .shift()). It should be an easy lift: adding some tests which check to see if the value for latest is the same before and after calling for personalTopThree and doing the same for the scores getter.

This is a great addition for the canonical data because other tracks will have the same issue.
PR this file. You can use the scenario local-scope for this test. Make sure to link to this issue in the PR. You probably want to use a new non-exising property, for example topThreeFollowedByLatest or whatever seems sane.
In the JavaScript PR we would not use a new property but simulate it: call personalTopThree and then latest and see if it's still correct.

This is a great addition for the canonical data because other tracks will have the same issue.
PR this file. You can use the scenario local-scope for this test. Make sure to link to this issue in the PR. You probably want to use a new non-exising property, for example topThreeFollowedByLatest or whatever seems sane.
In the JavaScript PR we would not use a new property but simulate it: call personalTopThree and then latest and see if it's still correct.


Tar and zip archivers read entries fully into memory

The use of chunkAll in TarArchiver#archive and in ZipArchiver#archive causes all the bytes for each entry to be read into memory, which can lead to out-of-memory errors for large entries.
I believe the main limitation/reason for why this is necessary is so tarEntry.setSize can be called with the correct size. I tried using chunks instead of chunkAll along with updating the size with each chunk, but it didn't work properly because tarOutputStream.putArchiveEntry(tarEntry) is executed while the size is still 0, so I ended up with an error when writing to tarOutputStream.
Can you think of any other ways to work around this? Here's my attempt in case it's helpful: https://github.com/lhns/fs2-compress/compare/main...mrdziuban:tar-zip-read-into-memory

Hi, yes this was a problem I encountered and sadly I don't think it can be resolved without buffering the entries somewhere. It needs to be documented however. The problem is that the entry size needs to be set before writing the entry because it is written into the entry header which has to be written first. Offering an api to buffer the file to disk might be an option.

@lhns It should be possible to add a ZipEntry without knowing the size up front when the method is ZipOutputStream.DEFLATED. Will you accept a PR which changes the typing of the ZipArchiver to Archiver[F, Option]?
We would love to use this library to add .zip functionality to our fs2.Stream, but the requirement that we need to know the size of each zip entry up front makes this impossible for us at the moment.

@jakobmerrild I am pretty sure that I tried with DEFLATED but I would love a solution to this. I don't mind the change from Archiver[F, Some] to Archiver[F, Option] in ZipArchiver if it works. Maybe there could be different types for different methods.

fixed in v2.2.0


NIFI-3344 Added property to JoltTransformJSON allowing the user to sp…

…ecify pretty print, defaults to false
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically master)?

[X] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[X] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

I have yet to be able to successfully build the Nifi master branch without skipping tests on either my windows and CentOS machines. I built with -DskipTests=true and validated the processor there.

What errors are you encountering when building with tests?

At the moment my windows installs fail on this NifiGroovyTest, where it tries to generate and reference a linux style path. I saw a recent email discussion that seemed to bring up a similar issue here.
mvn -version
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T02:58:13-05:00)
`Maven` home: C:\Program Files\apache-maven-3.5.2
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_151\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: `"windows"`

[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.nifi.NiFiGroovyTest
[ERROR] Tests run: 8, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1.667 s <<< FAILURE! - in org.apache.nifi.NiFiGroovyTest
[ERROR] testInitializePropertiesShouldSetBootstrapKeyFromFile(org.apache.nifi.NiFiGroovyTest)  Time elapsed: 0.495 s  <<< ERROR!
java.nio.file.InvalidPathException: Illegal char <:> at index 2: /C:/Users/nlewis/Desktop/Projects/NIFI/nickOfficialNifi/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-runtime/target/test-classes/\NiFiProperties\password-testInitializePropertiesShouldSetBootstrapKeyFromFile.txt
        at org.apache.nifi.NiFiGroovyTest.testInitializePropertiesShouldSetBootstrapKeyFromFile(NiFiGroovyTest.groovy:161)

[ERROR] testMainShouldHandleMalformedBootstrapKeyFromFile(org.apache.nifi.NiFiGroovyTest)  Time elapsed: 0.001 s  <<< ERROR!
java.nio.file.InvalidPathException: Illegal char <:> at index 2: /C:/Users/nlewis/Desktop/Projects/NIFI/nickOfficialNifi/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-runtime/target/test-classes/\NiFiProperties\password-testMainShouldHandleMalformedBootstrapKeyFromFile.txt
        at org.apache.nifi.NiFiGroovyTest.testMainShouldHandleMalformedBootstrapKeyFromFile(NiFiGroovyTest.groovy:141)

[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   NiFiGroovyTest.testInitializePropertiesShouldSetBootstrapKeyFromFile:161 ▒ InvalidPath
[ERROR]   NiFiGroovyTest.testMainShouldHandleMalformedBootstrapKeyFromFile:141 ▒ InvalidPath
[INFO]
[ERROR] Tests run: 8, Failures: 0, Errors: 2, Skipped: 0

It is to be noted that I am very new to developing on this project and could just be environment issues! :)

Thanks for reporting the context around that. If you're comfortable doing it, you can open a Jira to resolve that problem here. If not, let me know and I can do it in a bit. It is probably environment-specific in that the test was not verified on Windows before being re-enabled in PR 2821, but not your environment-specific in that other Windows users may have the same issue. Either way, I believe it's a legitimate thing to report and we can fix it. Thanks.

Went ahead and made the issue based on our discussion. Thanks @alopresto .
https://issues.apache.org/jira/browse/NIFI-5574

Code LGTM, merging to master, thanks @nalewis


Response codes of 0 are not being reported as request events, but are reported as an HTTP failure

Describe the bug
If there is some response code of 0, then it is not reported as a request event, but it is reported as an HTTP failure
Expected behavior
The response is recorded as both a request event and a failure
Actual behavior
it is not reported as a request event, but it is reported as an HTTP failure
Steps to reproduce
Create some request where the host responds with a 0 and raises the following error in event: requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
Environment

OS: Mac OS monterey
Python version: 3.10
Locust version: 2.8.6
Locust command line that you ran: N/A
Locust file contents (anonymized if necessary): N/A

Ok, will update and get back to you on if this behavior still exists tomorrow

@cyberw Can confirm this is still happening in version 2.12.2

Can you add your locustfile (ideally with a public http endpoint exhibiting this behaviour, so I can test it)?
If your locustfile is complex, start by taking away everything not needed to show this behaviour (https://stackoverflow.com/help/minimal-reproducible-example)


Feat(Core)!: CNX 8352 operations.send

As part of our effort to reduce analyser warnings across our code base. It's important that our Core functions are clear about what exceptions types they throw.
This motivation for this PR was to focus on Operations.Send and attempt to enforce and provide clear guidance on the exception types that can be thrown.
Our original Operations.Send overloads were doing some smelly things:
In the signature of the function alone:

We were allowing users to pass in a SerializerVerion enum to switch to using the old v1 serializer. This serializer hasn't been used (or tested) in almost two years, its past time we drop exposing it as an option for Operations.Send
A long time ago, we were using OnErrorAction to signal errors in transports and sending. We have since deprecated this in favour of throwing proper Exceptions instead. This property is effectively unused with our current Operations.Send
We were exposing a disposeTransports boolean (defaulting to false) that, when true, we would loop through and dispose any IDisposable transports that the user passes through.  Thus this "feature" was not really usable, and much cleaner solved by expecting caller to handle the disposal using e.g. using a using keyword.

And in the implementation:

We were performing input validation, logging, timers, error handling, SQLite setup, transport manipulation + extra nonsense for serailizer v1, as well as performing the actual send!

In my new implementation, we have far fewer parameters, removing the obsolete and questionable designed ones.
We have also separated logging and error handing into one function SendToTransports and the actual send logic in an internal SendInternal function.

I would have liked to make this change 100% non-breaking, allowing devs currently using Send to have their code still compile and work 100%.
This will be true for most cases, there are a couple permutation of positional and keyword args where devs will now see a compiler error saying "parameter mismatch" or "Could not find suitable method, candidates are...".

Unless we are prepared to change the name of our new Send function, this is unavoidable.
I would suggest that this shouldn't be a blocker. Any changes to overloads are technically breaking when you look at various positional keyword args. We have made far more breaking changes only last release with the inclusion of some extra functions in ISpeckleConverter,

To get a flavour for how likely this is to affect users. All existing uses of send within our codebase (with the exception of a single one in our integration tests) were no breaking.


getting duplicate id in multi-threded environment (django)

I want to use snowflake ID generation in my project. so I am trying to use this library. but I am getting unique constraint error for the field primary key. I am using Django. can you please guide me, on how to set it up correctly to avoid getting duplicate IDs. like do I need any additional configurations?

Hi! Each instance must have own instance_id. The standard schema of Django deploy is to use uwsgi or so on. It's spawning more than one process to server requests. Thus, you have more than one instances of snowflake.
So... you can't use the library in this way.
You have to create a separate service for generate ids.

I'm sorry for not getting back to you sooner. if I use a locking mechanism then can it be solved ?
`from snowflake import SnowflakeGenerator
import threading
class ThreadSafeIdGeneratorService:
def init(self, instance_id):
self.gen = SnowflakeGenerator(ip_address_int)
self.lock = threading.Lock()
def generate_unique_id(self):
    with self.lock:
        return next(self.gen)`


[V2] ThemeProvider only accepts single child

I was trying to do something like this
<ThemeProvider>
  <PageSection/>
  <PageSection/>
</ThemeProvider>

when I got Invariant Violation: React.Children.only expected to receive a single React element child.. Is there a reason ThemeProvider doesn't accept multiple children? Considering the provided functionality I would expect this to be quite trivial to implement, but maybe I'm overlooking something...

ThemeProvider would have to wrap the children in a div if it accepts multiple children because it only can return a single component. If the user has to pass a single children to ThemeProvider he can decide whether a extra div is needed.

@k15a Thank, that makes sense now I think about it.


Some files not mentioned

I am working on some parsing of this repo's readme and file list to help automate FTB. I found some programs that are in the repo but not linked to in the index, and one program that is mentioned in the readme but not present in the repo:
Not mentioned:

2d_array.f90
alloc.f90
array_intrinsics.f90
assoc.f90
bitwise.f90
bounds.f90
char.f90
count_pack.f90
do_loop_index.f90
elemental.f90
func.f90
function.f90
hello_world.f90
if.f90
implicit_save.f90
input_data.f90
loop.f90
merge.f90
module.f90
naming.txt
one_line_if.f90
operators.f90
power.f90
sections.f90
shortest_code.f90
sum_exit.f90
trim.f90

Mentioned in the readme but not present in the repo:

precision.f90

Thanks for pointing these out. I added precision.f90, and the link to it in the readme now works. I will look at whether the other codes have associated tweets.

Updated list
Not mentioned in the readme:

bitwise.f90
elemental.f90
func.f90
function.f90
hello_world.f90
if.f90
implicit_save.f90
input_data.f90
loop.f90
merge.f90
module.f90
naming.txt
one_line_if.f90
operators.f90
power.f90
sections.f90
shortest_code.f90
sum_exit.f90
trim.f90

I went through the list and added links to codes in the readme. In a few cases I wrote a code and uploaded it but decided I would not write a tweet about it.

Ok, sounds good. Feel free to close this issue if you are satisfied.
Here is the updated list for the record:
Not mentioned in the readme:

bitwise.f90
input_data.f90
naming.txt
operators.f90
shortest_code.f90
trim.f90


feat(react): Reactification of Settings and Profile Cont...

The cliff notes on this PR:

Consolidate the majority of  updateMy*** actions into one updateUserBackend action

Berkeley's third rule of Redux: "Never use two actions where one will do."

Add more options to /settings to allow the user a more control over their public profile
Consolidate all verifyCert endpoints into one /certificate/verify endpoint
Consolidate all showCert endpoints into one /c/:username/:certendoint
Allow the user to complete projects via the challenge itself or the settings page, either of which updates user.challengeMap as well as user.projects.
Allow the user to claim and see certs from /settings
Allow the user to update their username from /settings, with verification from the backend that the username is available
Fixes an issue where lang is undefined in the mapService
Fixes an issue where the settings container wraps itself off screen in FireFox
Fixes styling of flash messages

Their might be other things but I cannot remember right now.
closes #15917
closes #16237
closes #16270
closes #16271
closes #16273
closes #16278
closes #16279
closes #16283
closes #16285
closes #16587
closes #16597
closes #16598
closes #16599
closes #16600

@Bouncey From a functionality standpoint, these changes all look great. Thanks for creating the gifs, too! They make QA'ing much easier! LGTM.
@BerkeleyTrue what do you think - is this ready to merge?

@Bouncey Why is this coupled with the settings page? The settings page is already react.

I have a commit to remove the async and fetchMessages action. Both are leftover from previous itterations
The settings page has been heavily modified to add new options (mainly stuff that GitHub took care of) and remove depricated options, like social account linking, from the settings page. The functionality on the backend is still there, it should be removed in a subsequent PR.

The functionality on the backend is still there, it should be removed in a subsequent PR.

Can you just list the APIs or files? I'll take care of auditing and making a PR post this is merged?

@Bouncey, great work on this! From the GIFs, this looks great :smiley: I will pull this down when ready to properly QA everything.


Adding Admin Queries to Project Only Works if Groups Exist

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14.3.0
Amplify CLI Version
4.51.2
What operating system are you using?
MacOS - 11.3.1
Amplify Categories
auth
Amplify Commands
update
Describe the bug
If you do not select a group to restrict access to when adding Admin queries API to your project, it will not add the necessary code to your project. If you create groups in Cognito and then restrict access to one of them, it will add the necessary code to your project.
Expected behavior
If you do not have groups setup in your Cognito or do not want to restrict the Admin queries API at all, you should still be able to add the Admin queries API to your project, and have it unrestricted.
Reproduction steps

From command line type amplify update auth
Select "Create or update Admin queries API'
When it asks 'Do you want to restrict access to the admin queries API to a specific group?" press n
It says it Successfully updated auth resource XXX locally
It DOES NOT add the resource to the project at ./Amplify/function/XXX

If you select yes in the step above and select a group, it will add the correct resources locally. I had to create groups just to get the code added to my project. Thank you!
GraphQL schema(s)
No response
Log output
No response
Additional information
No response

Hey @TKMApp :wave: thanks for opening this. I have been able to reproduce and also noticed if we restrict to a certain group (which will add the resources) then step back through amplify update auth to remove the restriction we receive the Successfully updated auth resource XXX locally message without the appropriate changes. Marking this as a bug

This is by design. If the admin query is not restricted with a group and anyone can access the APIs  it goes against the best practice.


Add support for dependabot

Adding dependabot should help catch issues and update dependencies as needed. It's built-in with Github so no changes needed from your part.
Adding dependabot in a fork of this repo, created the following pull-requests to update npm dependencies:

Tried before, Dependabot too annoying for me.
Run npm update is better.
https://github.com/louislam/uptime-kuma/pull/167

Tried before, Dependabot too annoying for me.
Run npm update is better.
#167

I still think Dependabot is the way to go, specially to manage big projects. It can be setup to run Weekly to reduce the verbosity.

@louislam why don't add the bot to the project, it would be more sure and will stay the project up to date ?


Home page component caching

Closes #34
Summary

Used react's useMemo hook to cache the home page component.

Acceptance Criteria

[ ] Home page loads only on initial page load
[ ] After a user navigates away from home page, upon return there is no load time

I tested this and we still have loading on the Home page load... @supriyaamisshra

Here is an example of using localstorage instead of react state. This doesn't completely resolve the loading issue, but it's my progress so far:
https://github.com/moonshotcollective/tokenstream.party/commit/199861a481808fea6236d3d3d37c44fb3eab071f

*this is still WIP

I've moved to using a custom memo / cache to load streams data (balance, cap) for the home component.


Role field too short in Snowflake connection

System information:

Ubuntu 20.04
22.1.2

Connection specification:

Snowflake

Describe the problem you're observing:
If you write a >8 chars role you cannot see it clearly (see image)

Thanks for the report @rpalloni

Hello @GuenterSch
Usually, ROLE's name is not so long as Authenticator.

Hello Anastasiya
in our Account we use role names like
DEV_???_EXTENSION_DISTRIBUTE_RESTRICTED
I thought, the dialog is not more "symetric" (I do not know the right word ;-) ).


Typescript definition for redis.call is missing

The Typescript definition for redis.call is missing in the index.d.ts of @types/ioredis.
ioredis version: 1.14.1
@types/ioredis version: 4.0.18

This project is written in typescript.  Why doesn't it just export it's own types?  O_o

This project is written in typescript. Why doesn't it just export it's own types? O_o

See https://github.com/luin/ioredis/pull/981#issuecomment-538718567


[Question]: Vector index creation with LLM-A and Query with LLM-B. Loading vector without connection to API and costs for tokens.

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
Question 1.
Why does the loading of already created and stored vectors require OpenAI API and cost tokens the same as for creation?
How to avoid costs for tokens every time a vector is loaded?
Question 2.
Does LlamaIndex support other LLM integration?
_Vector creation with gpt4all and query with gpt4all is possible:
https://colab.research.google.com/drive/16QMQePkONNlDpgiltOi7oRQgmB8dU5fl?usp=sharing__
How about vector creation with gpt4all and query with OpenAI
Regards,
Sergiu

@logan-markewich i am also curious about using local LLMs with Llama index.
Could you fix the last two links above, which appear to describe how to do that?
They are broken with 404 errors.

@araichev
Embeddings
https://gpt-index.readthedocs.io/en/latest/core_modules/model_modules/embeddings/usage_pattern.html#embedding-model-integrations
LLMs
https://gpt-index.readthedocs.io/en/latest/core_modules/model_modules/llms/usage_custom.html#example-using-a-huggingface-llm
https://gpt-index.readthedocs.io/en/latest/core_modules/model_modules/llms/usage_custom.html#example-using-a-custom-llm-model-advanced


Structure

This branch's core goal is to structure the OOP school library  project  by  implementing the Classes for :

students
teachers
The main language used is Ruby.

changes made :

Referenced files using require_relative


ppsspp: refactor

new Boolean selectors:

useSystemFfmpeg, default false - because PPSSPP project uses a heavily patched fork of ffmpeg_4
useSystemSnappy, default true

move wrapping to postFixup
unpin ffmpeg_4 and glew

it required a self-referent argset

Phew!
Description of changes
Closes https://github.com/NixOS/nixpkgs/issues/304616

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3864


The book of sbt dark mode contains hard to read figures

Issue

Figures like above are unreadable
Expected
Figures should all be easily readable
Note
We probably need to raise the contrast? Or invert the color of the diagram?

I didn't want the dark theme to be selected, but when I added the language bar, the code that I copied from somewhere included a line about using OS's prefers-color-scheme.


Proposal: Cython Support

I believe the possible optimizations (without a refactoring allowing for processing multiple pixels at a time) for the lengthy decode process are severely diminished now, and it's only twice the speed that it originally was. So, I am proposing that I make an optional Cython extension. Cython is a superset of Python that compiles to C, which compiles to machine code. If you want to take a look at what it looks like and how fast it is, check out the pybase122.pyx file in my pybase122 decoder in my starred repos. I included benchmarks for the best Python version I could write, and the best Cython version I could write (with some help). You'll notice that the Cython version I wrote ended up being at least 10x faster than the python version, and the version that I got help with is over 20x faster. This is a huge speedup. While this won't have as major a speedup because it uses less math/bit operations, I bet you that I can get at least a 4x speedup for the section inside the two for loops in the get_file_from_image (I think that's the name) function.
The main obstacle to including Cython is that it needs to be compiled with every change, and you need to pip install Cython to compile. However, luckily, it is possible to fall back to a Python version of the code should a user not want to install Cython or compile it. This is why I'm proposing that I only Cythonize the slow part inside the loop, and add a check for if the user's system supports Cython before it actually tries running the Cython code.
For an example of a Cython library, google "pomegranate Cython". Pomegranate is a machine learning library that is blazingly fast because it uses Cython to compile its algorithms. It's also open-source, on GitHub, so you can check the internals.
I'm marking this as a proposal because I don't currently want to do the work if you're not comfortable with it.

Update:
I did the work because I have extra time, and I made a Cython version that decodes about 5-6x as fast as the current Python.

@Theelgirl Absolutely! Make the PR and I will take a look at it!

Ok, making now.

It benchmarks at about 4x faster on the Lenna image than Python, however it fails to decode the resulting mp4 with either version, producing an unusable file.bin
Is this a known bug?

@Theelgirl So to clarify, did decoding work?

@AlfredoSequeida Yes, using dobro's version fixed it. The problem wasn't with Cython, as it happened on the normal version also, it was with something else.

Closing because the PR has been ready for a while.


Brackets

// Brackets question: sub-tree or nah? (includes |abs|)
// if subtree: brackets stop being symbols, instead you can place the caret outside of the brackets and then there is another expression (usually row) inside them
// if not subtree: we need to find the ending bracket. which means that in the case of |abs|, we need to wrap it in its own row. and when |abs| gets deleted or edited, we gotta get rid of the useless row

Answer: Brackets are a special type of symbol


Add LICENSE to the code

Dear all, this is an attempt to license the code of the project. I am proposing this license, as a good option that is liberal and allows sharing without any limitations.
For this to happen, we need the okay from every contributor, otherwise we cannot do this, and may have to replace their contributions.
All contributors of code or documents have been added to the list, ordered by the number of commits, descending, and with the copyright starting from the first year of their contribution. Please make sure the names are okay.
Please, all, comment here and approve this PR:
@daknob :heavy_check_mark:
@mzampetakis  :heavy_check_mark:
@sonaht :heavy_check_mark:
@kabitakis
@kouts :heavy_check_mark:
@gsaslis
@padeler
@zakkak :heavy_check_mark:
@gvre
@fadamakis
Thanks!

This is the ISC license if I am not mistaken.
I am OK with the license but I think that most people are more familiar with the MIT license, which is effectively the same, so why not use the latter?
-------- Original Message --------
On Feb 15, 2020, 22:39, Antonios A. Chariton <<EMAIL_ADDRESS>wrote:

Dear all, this is an attempt to license the code of the project. I am proposing this license, as a good option that is liberal and allows sharing without any limitations.
For this to happen, we need the okay from every contributor, otherwise we cannot do this, and may have to replace their contributions.
All contributors of code or documents have been added to the list, ordered by the number of commits, descending, and with the copyright starting from the first year of their contribution. Please make sure the names are okay.
Please, all, comment here and approve this PR:
@mzampetakis
@sonaht
@kabitakis
@kouts
@gsaslis
@padeler
@zakkak
@gvre
@fadamakis
Thanks!

You can view, comment on, or merge this pull request online at:
https://github.com/devstaff-crete/devstaff.gr-website-static/pull/102
Commit Summary

Add LICENSE to the code

File Changes

A LICENSE.md (22)

Patch Links:

https://github.com/devstaff-crete/devstaff.gr-website-static/pull/102.patch
https://github.com/devstaff-crete/devstaff.gr-website-static/pull/102.diff

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

This is indeed the ISC, or BSD 2-Clause License.
I think it just lacks some unnecessary wording, so it’s more simple.
Feel free to replace it with the MIT one if you think it’s better, I didn’t think of that to be honest.
I know that some projects prefer this to the MIT one though for inclusion to their repos.

I personally approve this PR.
@DaKnOb @mzampetakis @sonaht @kabitakis @kouts @gsaslis @padeler @gvre @fadamakis please post a similar comment if you also approve the PR so that we can proceed and have the approvals on record.

I approve this PR

The change has been made, now there's a generic "DevStaff Community"

I approve this PR

Funny that ISC itself moved away from the ISC license...
It looks like they are now using Mozilla Public License 2.0 instead
https://www.isc.org/licenses/

@padeler, this is a kind reminder

:tada: Thank you all!
@DaKnOb (or anyone else with merge rights) please merge.


Make provisioning and releasing more explicit

Add explicit fields to Repository to track provisioning and releasing. I propose:
Repository.provisioned : boolean to just track whether it has been provisioned. We use URL for this right now, but it is indirect (aka if URL === null then it is not provisioned).
Repository.released: Status should also be used. Status is just to give us more flexibility, for now I propose NotReleased | ReadOnly | ReadWrite.
Also need to remove Team::custom::githubAttached and `Repossitory::custom::githubProvisioned```.

Updated label for now; we can come back to this if we need to, but this won't be a high priority unless something changes.


What should the review/testing status labels be?

From Slack on 5/1/19: (related to https://github.com/phetsims/phet-info/issues/75)

Ariel Paul [1:07 PM]
Hear ye Hear ye --- a long standing issue just was resolved to remove certain redundant labels. Someone had let this slip for a long time (pointing to big thumbs at myself). But let it be known the status:fixed-pending-testing should no longer exist. In particular for @KatieWoe that label has been collapsed into status:ready-for-review so that "review" is a general word for designers reviewing, developers reviewing, or QA testing/reviewing

From there discussion began as to whether this was best and how everyone used both tags.  I have observed them used interchangeably or to denote things like whether or not I should close the issue after.  @pixelzoom mentioned using them to denote if the review was testing or a design/code review.
I would suggest either going through with @ariel-phet's change and relying on instructions/assignments in issue for the nuances described above, or changing the labels to be: status:ready-for-QA and status:ready-for-review  When it is for review it is either not for QA, or if QA looks/test they do not close it.  Basically, it is not done, even if looked at.  If it is ready for QA we test and close if resolved

In my experience, it is typical for the status:fixed-pending-testing label to include instructions for testing. The 'status: ready-for-review' label follows a similar use case with instructions for what should be reviewed. I rather have just one label and vote for 'status: ready-for-review'.
If we are removing the status:fixed-pending-testing we should update the QA/issue-templates.

These issues should have the “status:fixed-pending-testing” label.

Why is it just "review/testing status" that we're considering?  Like "priority", perhaps issues should only be in one "state" at a time.   Perhaps we should start by describing the lifecycle of GitHub issues in the PhET process as a state machine, then create state: labels (or status:, if you prefer) that reflects that process.

I disagree with https://github.com/phetsims/QA/issues/312#issuecomment-488390590.  "Review" is very different than "test".   For example, I currently have Gas Properties issues where the work is done and is "ready-for-review".  Since it's an unpublished sim, those issues will be closed after review is accepted.   For a sim that is published, an issue will typically need to be review by a designer, and that is indicated by "ready-for-review".  When that's completed, I then need to remember to have it tested during an RC cycle, and (according to the QA issue template) I move the issue to the "status:fixed-pending-testing".   If we collapse so states into one, I have no way to determine which have been reviewed, and which are ready for RC testing.

I would disagree on having multiple tags for different people reviewing, and especially for only having one up at a time.  Quite often a change will be given to both the designer and myself to look over at the same time.  It seems silly to delay one of us looking in this case.  An issue may be in a set "state" of review, but that doesn't mean that only one type of review is relevant and happening at that time.

I would disagree on having multiple tags for different people reviewing, and especially for only having one up at a time. Quite often a change will be given to both the designer and myself to look over at the same time.

There's nothing preventing you and a designer from both reviewing an issue that is in the "ready-to-review" state.   And until a designer has reviewed the work, you certainly shouldn't be doing a full regression test on an issue.  status: ready-for-review means that work is ready to be reviewed, not thoroughly tested.  status:fixed-pending-testing indicates that something is ready for a full regression test, and comes after a review.  They are 2 different activities.

@pixelzoom I like the point of looking into the lifecycle of a github issue and creating labels that actually make sense for the tasks needed. I wonder though if the stage in the lifecycle is clear enough via assigning. If there is a single review label, and a designer is assigned, that feels obviously different to me than if QA is assigned to it with the same label. Do you feel like there would ever be overlap such that this could be confusing? In general I feel that may be more complexity than needed for a single github issue.

Issues (especially those that need to be verified in QA) often remain unassigned for long periods of time.  If you have multiple unassigned issues for my sim labeled with one "review" label, how do you know (without inspecting each issue) which issues need to be vetted by a designer, and which ones need to be vetted during RC testing?     This is not a hypothetical case.  I use these 2 labels all the time.  And I'm happy to replace them with something else, but not something that makes managing issues more difficult.

Relying on who is assigned to determine what state an issue is in is (for me) a non-solution.
Issues (especially those that need to be verified in QA) often remain unassigned for long periods of time.  If you have multiple unassigned issues for my sim labeled with one "review" label, how do you know (without inspecting each issue) which issues need to be vetted by a designer, and which ones need to be vetted during RC testing?     This is not a hypothetical case.  I use these 2 labels all the time.  And I'm happy to replace them with something else, but not something that makes managing issues more difficult.

We discussed changing "status:fixed:pending-testing" to "status:ready-for-qa".
"fixed-pending-deploy" and "???" could be collapsed.
The website can use a repo-specific "fixed-pending-deploy" label.
@jbphet and @Denz1994 use "fixed-pending-deploy" to know when to notify clients.
@KatieWoe needs a way to know whether to close issues after testing them.
"ready-for-review" will mean reassign to author when done.
"ready-for-qa" will mean close if it passes QA test.
Main label lifecycle for an issue in a sim pre RC branches:
unlabeled -> ready-for-review -> ready-for-qa -> closed
Main label lifecycle for an issue in a sim with RC branches:
unlabeled -> ready-for-review -> ready-for-qa  -> fixed-awaiting-deploy -> closed
Can also mention "feel free to close if all is well".  But default would be to assign back.
if a dev test, "ready-for-qa" should be closed
if an rc test, "ready-for-qa" should be moved to fixed-awaiting-deploy
What about issues that do not require QA?
For sims that have release branches, we should be more careful about this lifecycle.  For initial 1.0 sims, we do not need all this tracking.
@zepumph points out the advantage of seeing green/red open/closed linked from RC issues.

Summary:
The main philosophy for "ready-for-qa" labeled issues: close issues if they don't require further issue-specific work. (Deploying the sim doesn't count as issue-specific work).
The default for "ready-for-review" is to reassign to author.
Keep fixed-pending-deploy for edge cases, like clients that need to be emailed.  That is the exception rather than the rule.
Action items:
@KatieWoe will update the template.
@mattpen will make "status:ready-for-qa" label.

QA book and issue template updated.

New label has been added to all repos.


Organize Imports does not alphabetically sort the same way as tslint

From @MichaelRBond on April 12, 2018 11:23
Issue Type: Bug
When running Organize Imports on the following line: import {abc, Xyz} from "./foo"; the command changes the import sort order from
abc, Xyz to Xyz, abc. This causes a tslint error, because tslint expects it to sort alphabetically regardless of case.
Steps to reproduce:

Run Organize Imports

Expected Result:
sorted order of imports is the same as tslints expected sort order. import { abc, Xyz } from "./foo";
VS Code version: Code 1.22.1 (950b8b0d37a9b7061b6f0d291837ccc4015f5ecd, 2018-04-06T00:21:13.607Z)
OS version: Darwin x64 17.4.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz (8 x 2800)

Load (avg)
4, 4, 4

Memory (System)
16.00GB (1.94GB free)

Process Argv
/Applications/Visual Studio Code.app/Contents/MacOS/Electron -psn_0_3691397

Screen Reader
no

VM
0%

Extensions (25)

Extension
Author (truncated)
Version

vscode-markdownlint
Dav
0.14.1

todo-tree
Gru
0.0.31

JSDocTagComplete
Hoo
0.0.2

vscode-todo
Mat
0.8.0

vscode-docker
Pet
0.0.26

cform
aws
0.0.10

solargraph
cas
0.15.0

tslint
eg2
1.0.28

json-tools
eri
1.0.2

vscode-emacs
hir
0.1.1

ruby-linter
hoo
1.0.0

terraform
mau
0.0.23

prettify-json
moh
0.0.3

python
ms-
2018.3.1

azure-account
ms-
0.4.0

dust
nem
0.0.1

Ruby
reb
0.18.0

java
red
0.22.0

vscode-icons
rob
7.22.0

code-spell-checker
str
1.6.6

vscode-java-debug
vsc
0.8.0

vscode-java-pack
vsc
0.3.0

vscode-java-test
vsc
0.5.0

vscode-maven
vsc
0.7.0

vscode-todo-highlight
way
0.5.12

(1 theme extensions excluded)

Copied from original issue: Microsoft/vscode#47734

From @vscodebot[bot] on April 12, 2018 11:23
(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

Import orginization doesn't honor tslint line length rules (#47679)

This is also conflicting with an existing ts-lint rule, see https://github.com/Microsoft/TypeScript/issues/23888


TT-Buda Installation Failed

Hello, I am new here and I would like to try TT-Buda and Pybuda flow for my research.I wonder can I use the compilation tools for tests if I don't have a real tt-device?
I failed the installation when I first follow tt-buda-install. And while I followed "Setup HugePages" and tried to run sudo -E python3 setup_hugepages.py first_pass, It shows Assertion ERROR that Did not find any tt devices.
I have used tools like TVM and it can compile the DNN network into JSON or other forms for my own accelerator when I give TVM the description of it. Therefore, I wonder how to use TT-BUDA and Pybuda without the real tt-device? Or is there any step wrong in my description?
Thanks!

Hi @OwenKZ -- you can run some examples through pybuda using what we call "Golden".
For installation, you can skip the Hugepages step as that is only required when physical devices are present.
These would be the steps to follow:

https://github.com/tenstorrent/tt-buda-demos/blob/main/first_5_steps/1_install_tt_buda.md#backend-compiler-dependencies
https://github.com/tenstorrent/tt-buda-demos/blob/main/first_5_steps/1_install_tt_buda.md#pybuda-installation

After you have an environment with a version of pybuda installed, you can try running in "Golden".d.
As an example of this, refer to the example file here: https://github.com/tenstorrent/tt-buda/blob/main/first_5_steps/2_running_nlp_models.ipynb
On Step 5: Instantiate Tenstorrent device, you can add a parameter to TTDevice which sets the target backend to be Golden.
tt0 = pybuda.TTDevice(
    name="tt_device_0",  # here we can give our device any name we wish, for tracking purposes
    arch=pybuda.BackendDevice.Grayskull,  # we set the target device architecture to compile for
    devtype=pybuda.BackendType.Golden  # we set the target backend type to be Golden for running off device
)

Now it works fine! Thanks ~


Link "Copy and Edit this visualization" doesn't work for some Chart tables

In publication mode, the link "Copy and Edit this visualization" doesn't work for some Chart tables
The link leads to the list of datasets instead to the page where the table is configurated.
It seems to be the case only when applying Heatmap to a column.

Open https://int.visualize.admin.ch/en/v/wmh6GNFCPxZn
Click on "Copy and edit this visualization"
The link leads to the list of datasets instead to the page where the table is configurated.

Environment (please complete the following information):

Visualize environment and version: INT v3.12.0
Browser and version Edge

Seems the work now, when creating a new table chart with heatmap, but the previous published one stays broken


Implement ADC test for PAY-SSM v4 PCB

Create a new manual_tests/adc_test that reads all 12 channels on both ADCs (ADC1 and ADC2), printing their descriptions, raw values, and converted values (with units). Also need to update the constants in src/devices.h for the new board.

commit 77b4b9e52f41df39b636ec929793b627ba0944ce addresses this

Thank you Tahreem for doing this! I am going to upload this test to PAY-SSM v4 soon. Will let you know if anything worth noting comes up.


Render does not trigger after card is loaded

Greetings,
I'm no expert of lit-element, but it seems that on some instances the render() method does not fire a second time after the page load, leaving the card like this until user interaction (mainly because of the missing map.invalidateSize() call ) :

The issue seems to arise only the first time the dashboard with the map card is loaded, without error output.
I've solved the issue with a quick hack, but it would be great if you can look into it.

@Manuel-Materazzo let me know when ready!

ps. I don't have your issue, odd.

Salutations,
I've done some digging on the issue, and it turns out that the card works flawlessly on any pre-2023.7.0 homeassistant versions.
I've tested using clean docker container installations, specifically on these versions and using HACS:
...
2023.6.0 - no issues
2023.7.0 - map loading issue
2023.9.0 - map loading issue
2023.10.0 - map loading issue
2023.12.4 - map loading issue
2024.2.2 - map loading issue (my main installation)
Interestingly enough, starting with 2023.7.0 the card_size: 16 property does not create a "full-screen" card by default, unless you select the "panel" view for the dashboard. I guess it might be related, considering that the root of the issue is leaflet not being able to correctly pick up the canvas size.
Also i noticed i messed up the merge request by pushing other things, the "quick hack" i mentioned was on the force first render commit.

@Manuel-Materazzo thanks a lot for testing, I'm on 2023.11 without issue. Will test your PR and provide feedback+merge.
Thanks a lot!

@Manuel-Materazzo thanks a lot for testing, I'm on 2023.11 without issue. Will test your PR and provide feedback+merge.
Thanks a lot!

Weird, i just tested with a clean docker installation of 2023.11 + hacs and i can reproduce the issue.


Data racing issue with heavy load

Hi,
Your SPMC_Queue is really inspiring! But it seems there's still a data racing issue.
My test steps:

in multhread.cc, extend array size defined in struct Msg to make it heavier, e.g.,
struct Msg
{
uint64_t tsc;
uint64_t i[1];
};
to
struct Msg
{
uint64_t tsc;
uint64_t i[100];
double f[100];
};
compare Msg.f as well
Loop more times (1e6 -> 1e7)

Then these's a possibility of assert fault.
I think it may related to the write() operation: sees that operation does't care if the data is occupied by a reader -- the data may be changed by write() while reader is reading.

I also have this question. how to deal with the competition?while reader is reading, the writer is going to write the same area.


Ensure Concurrent::Stack elems handling is thread-safe

Do you have a concrete situation where this actually matters? The element count is only ever dependable if we know no other changes are going on, and to know that we'd have needed to use some other kind of synchronization mechanism, which would have barriered?

I could see there being a possibility of wanting to maintain a bounds on the size of the stack, but offhand, no. You're right about the barriers, that's something I didn't consider.


chore(clean up e2eAnnotations.test.ts #213)

Issue #213
Reviewers
Functional:
@seve
@atolopko-czi
Changes

removed irrelevant tests as annotations are no longer modifiable in any way
added smoke-test-annotations to push_tests.yml

forgot to switch back to main prior to checking out new branch. closing and will reopen fixed PR.


[MODEL] Support for querying multiple models

This PR adds support for multiple models search, as discussed in:

https://github.com/elastic/elasticsearch-rails/issues/10
https://github.com/elastic/elasticsearch-rails/issues/30
https://github.com/elastic/elasticsearch-rails/issues/50

A previous attempt of implementing this was done in:

https://github.com/elastic/elasticsearch-rails/pull/129

But although the PR is open, it was rejected mainly due to:

Lack of documentation
Missing unit and integration tests
An inconsistent Search response API: Even though #results was part of the multimodel-search response, #records was not.

This PR tries to address the problems outlined above, and also implement a performant hit-to-record deserialization.
Thank you very much to @AaronRustad for his PR, which motivated this one.
Example usage:
Elasticsearch::Model.search('fox', [Article, Comment]).results.to_a.map(&:to_hash)
# => [
#      {"_index"=>"articles", "_type"=>"article", "_id"=>"1", "_score"=>0.35136628, "_source"=>...},
#      {"_index"=>"comments", "_type"=>"comment", "_id"=>"1", "_score"=>0.35136628, "_source"=>...}
#    ]

Elasticsearch::Model.search('fox', [Article, Comment]).records.to_a
# Article Load (0.3ms)  SELECT "articles".* FROM "articles" WHERE "articles"."id" IN (1)
# Comment Load (0.2ms)  SELECT "comments".* FROM "comments" WHERE "comments"."id" IN (1,5)
# => [#<Article id: 1, title: "Quick brown fox">, #<Comment id: 1, body: "Fox News">,  ...]

NOTE: It is not possible to chain other methods on top of the records object, since it
is a heterogenous collection, with models potentially backed by different databases.

Description updated. Build fixed. I already signed the CLA too, however, it's not reflected here.

Hello Miguel, thanks for the patch, it looks very promising!
I went over the code a bit, and I like the approach, naming and implementation. I'm starting a two week vacation now, however, so I'd like to get back to it later, and evaluate it in more detail. Is that OK for you? Can you ping me in two weeks if this gets buried under hundreds of other tasks and e-mails after I return? :)
I have one plea, actually -- your patch modifies a lot of source code locations, some are unrelated to the feature (like fixing the lograge test). Would it be possible for you to do git reset master (that's a soft reset, no files will be changed), and then commit logical chunks of the feature? Then you can just force push git push --force to the multimodel-support branch, and the pull request will be automatically updated.)
If this would be too complicated, no problem, I can always do it by myself.

Of course @karmi, I will undo rebasing and commit again the changes.
And in relation to the timings, no problem. I know you've been busy with the query DSL last week, so don't worry. I will comment on the issue in a couple of weeks if I don't have any news from you.

@miguelff Perfect, thanks!

Done splitting PR into meaningful commits

This PR really helps me +1
Thanks for the hard work @miguelff

@karmi Hope your holidays went well :wink:

@miguelff Did some minor tweaks and b26b67a and merged, many thanks!

:+1: Thank you @karmi :rainbow:

So happy to see this in. Thanks @miguelff & @karmi for completing the feature!

@karmi @miguelff  - I dont see anything specific in the documentation for how to filter on multiple models
So for example i want to do something like
Elasticsearch::Model.search(params[:search], [Conversation, Message]).results.to_a.map(&:to_hash)
=> [{"_index"=>"conversations",
  "_type"=>"conversation",
  "_id"=>"20",
  "_score"=>0.6684941,
  "_source"=>{"id"=>20, "subject"=>"This is my subject", "created_at"=>"2016-03-30T18:55:55.000-04:00"}},
 {"_index"=>"conversations",
  "_type"=>"conversation",
  "_id"=>"21",
  "_score"=>0.6684941,
  "_source"=>{"id"=>21, "subject"=>"Another subject ", "created_at"=>"2016-03-30T18:57:01.000-04:00"}}]

# I want to do something like this
Elasticsearch::Model.search(params[:search], [Conversation, Message], {term: {id: "21"}}).results.to_a.map(&:to_hash)

# which should only return this object
[ {"_index"=>"conversations",
  "_type"=>"conversation",
  "_id"=>"21",
  "_score"=>0.6684941,
  "_source"=>{"id"=>21, "subject"=>"Another subject ", "created_at"=>"2016-03-30T18:57:01.000-04:00"}}]

Is that possible to do?

Is that possible to do?

As per this line, options are being forwarded to the search request. Then, they will merged with search definition provided (params[:search]  in your example) and then run against Elasticsearch.
So, yes, it should be possible, although is not a behavior that has been properly tested.

@miguelff - I have encountered this issue as well, can you give a quick snippet to show what you mean?


Judy readme

Changes Unknown when pulling 3118da056f25f070d1911c838b7c40f7091f34e6 on judy-README into ** on staging-branch**.

Coverage remained the same at 94.848% when pulling c8b7e3a050721f4f54f856a1622386f021ff2c2a on judy-README into fccf804098806cc072fa63600d5c695efef514ad on staging-branch.


AWS Lambda

Version: 4.1.0
Runtime Version: .NET 6
OS: AWS Lambda (Linux)
Expected behavior
Works fine on windows with the unit tests I made
Actual behavior
Crashing due to an environment dependency, which this library says it has none.
I realise you are using Iron Compress, which that library may have a dependency on something.
I'll try changing from the default compression of Snappy to the others and none shortly and report back.
System.AggregateException: One or more errors occurred. (Unable to load shared library 'nironcompress' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable)
Steps to reproduce the behavior
Run this library in an AWS Lambda and use the writer.

Disabling Snappy and using uncompressed worked. Ended up using AWS Glue to convert from JSON to Parquet in the end so I could maintain Snappy compression.


Minor issue

@bennyguo Kudos on how far you've brought this project since it's early stages. Indeed, performance has come an incredibly long way since the bug in issue #9 . Cheers.
By the way going through the current version I noticed some minor issues in the ReadMe which I've fixed in this PR #62 . Another issue I'm looking into is that I noticed when optimizing a NeuS on DTU without mask, this line throws a data type error: https://github.com/bennyguo/instant-nsr-pl/blob/5927901771d49ef0e38f4125d818485d9bb4aeca/models/neus.py#L157
I haven't come around to resolving it yet but let me know if you've already caught it.

Could you post the full error message? Thanks!

Sure. So a scalar type double was expected, but a float was found. I solved this by casting the variable as a double. All is good on my end now. Weirdly, I noticed issue #66 is quite the opposite case :)

Hello, I also encountered the same problem as you, can you tell me how you solved it, thank you very much

@aztsdfhj Please refer to https://github.com/bennyguo/instant-nsr-pl/commit/d834831a2a98b8647463dcbb26b1458aa51a3bcc. You may try adding back the .double() and see if it works.


Remove unused class OAuth2DestinationBuilder

Minor housekeeping

This is currently used by customers: https://github.tools.sap/search?q=OAuth2DestinationBuilder.&type=code
If we remove it we probably need to offer an alternative. Maybe making the header provider public?

If we remove it we probably need to offer an alternative.

I went through some options but they didn't look convincing.

Maybe making the header provider public?

Yeah.. before I'm doing that, I'll keep the current convenience API. Presumably it stays experimental.


Update index.md

hiya can i name the books the names i have given?

🚀 ship it

Lovin' the new names!


Rename no_coverage feature to coverage_attribute

The name has changed in recent rust nightly versions

Thanks!

Can you release a new version in the crates.io?

Can you release a new version in the crates.io? Without that, we can't bump our rust-toolchain.

I've pushed 0.5.2


How does this extend or improve upon default profiles?

How does this extend or improve upon the default Django profiles?
I don't know why I would use this app, and would like to understand.

me too i would like to know
please can you explain?


RHF is a dependency

RHF 7 should be a suggestion / peer for use with RHF-related hooks, not a hard dependency. This breaks integration with our legacy applications that use RHF 6 where I'd like to sideload RUI 5 for gradual upgrade alongside ORIS/ui 4.

 Swap it over to an optional dependency, since it's only necessary when a dev uses the hook that wraps it.

Looks like optionalDependencies are also installed on npm ci unless I throw on the --no-optional flag. I'll probably have to update our CI accordingly anyway, but I still think it makes sense to make RHF optional since it only impacts a single hook.

Forgot to tag this one in the commit. This is resolved

🤦♂ since I'm microbundling it all into a single runtime file, of course the imports for react-hook-form are going to execute. So I had this setup right, but I can't do an optional dependency like that if I'm using microbundle. I think I'm just going to move the RHF wrapper components off into their own package.

Dropped the RHF wrapping hook. Will re-release as a separate package in the future.


[ez][vscode] Remove Initialization Flow from Extension Activation

[ez][vscode] Remove Initialization Flow from Extension Activation
This diff removes the Initialization flow from ocurring on Extension Activation.
The landing page directs the user to invoke this command.
The Opening an AIConfig may invoke this if dependencies are not installed (not implemented yet)
Invoking the Initialize Command will no longer automatically install dependencies on the pre-selection python interpreter.
Testplan
https://github.com/lastmile-ai/aiconfig/assets/141073967/04031cdc-2c9d-47e8-b43d-a9d2f6aa769d

Followup, this was implemented on opening/creating AIConfig file in https://github.com/lastmile-ai/aiconfig/pull/1307


string to be encoded contains characters outside of Latin1 range

I get this error when polling a result (containing characters like ♫ and ♪) from my database:

Uncaught DOMException: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range

I could fix the issue for me by replacing "btoa(string)" by "btoa(unescape(encodeURIComponent(string)))" using this google-result
Unfortunately I couldn't reproduce this error in a simple environment:
namespace App\Http\Livewire;
use Livewire\Component;
class Counter extends Component
{
    public $string;

    public function mount()
    {
        $this->string = '♪ ♫ ♫';
    }

    public function hydrate()
    {
        $this->string = '♪ ♫ ♫';
    }

    public function render()
    {
        return view('livewire.counter');
    }
}

<div wire:poll="$refresh">
    {!! $string !!}
</div>

Maybe somebody else has more luck, or my fix helps others experiencing the same error.

I'd love a PR for that fix if it works for you

Issue is fixed


lokijs.min.js references non-existent ./loki-indexed-adapter.js

In 'lokijs.min.js` from npmjs.org
{adapter=require("./loki-indexed-adapter.js")}return adapter}
Should it not be;
{adapter=require("./loki-indexed-adapter.min.js")}return adapter}

so when I install lokijs from npm, its package.json's 'main' setting points to the 'src' folder which is non-minified.  How are you importing lokijs itself?

I've moved on and honestly, I don't recall the details. I typically npm i -D to install stuff. I also use Typescript so maybe there's an issue there.


[Combobox] It's not possible to scroll outside of focused item

Current behavior
In multiselect example (with focusOnHover enabled), when scrolling, the focus doesn't allow to scroll the item outside of the visible area and results in glitching (see video)
https://github.com/ariakit/ariakit/assets/6851247/27cc6424-bbff-4b7a-8cc7-d525fab5c717
Steps to reproduce the bug

Open multiselect example
Hover over an item
Try to scroll away

Expected behavior
It's possible to scroll the list without issues
Workaround
No response
Possible solutions
No response

Thanks for the report, @honzatmn!
Are you able to reproduce this issue locally, or does it only occur on the site? I suspect that an unreleased change might have introduced this regression.


fix: use logger.debug to be compatible with console interface

Landed in https://github.com/metarhia/metasql/commit/e32cf737a0b7dedd99c18c6deee80163bc0bb854


[BUG] CustomMetrics not logging value attribute anymore

CustomMetrics not logging value attribute.

SDK Version [e.g. 22]: 2.5.7

We used to pass value to average attribute as below
let metric = {             name: name,             average: value,             max: max,             min: min,             sampleCount: sampleCount };
average was getting logged to value attribute (as shown below in portal.azure > app insights)

But since yesterday, value attribute doesn't have any value

Find the network call in browser

There has been no updates to the SDK in the last few days and it looks like you are specifically using v2.5.7.
As such this doesn't appear to be an SDK issue (this GitHub is only for the JavaScript SDK issues), this looks like an ingestion / server issue. Especially as it looks like the data is still being sent from the SDK (the outbound network request).

Yes @MSNev , i believe this could be an ingestion issue. Will follow up with azure App Insights team for this. Thank you


Remove cinder orphaned code / volume code deduplication

What this PR does / why we need it:
This PR removes orphaned code, which was migrated from in-tree k8s cloud providers. This is a follow-up for the https://github.com/kubernetes/cloud-provider-openstack/pull/808/files#r341504413 comment.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Since there is still code, which depends on CCM, the overall PR requires similar amount of time (maybe more) like in #735
Release note:

/ok-to-test
@kayrus please apply for k8s org membership

cc @dims @lingxiankong

@lingxiankong @ramineni I need more time for this PR, since the cinder-related functionality contains a lot of duplicate code. Considering the amount of interfaces, it is not obvious what depends on what.

@lingxiankong @ramineni I need more time for this PR, since the cinder-related functionality contains a lot of duplicate code. Considering the amount of interfaces, it is not obvious what depends on what.

sure, let me know if you need any help

/test cloud-provider-openstack-e2e-test-csi-cinder

/test cloud-provider-openstack-e2e-test-csi-cinder

/test cloud-provider-openstack-e2e-test-csi-cinder

@ramineni @lingxiankong ready for review

@kayrus standalone cinder driver is deprecated in last cycle , lets wait for 1-2 cycles before its removal

@ramineni I didn't touch standalone driver. It is compiled correctly, check it by running make cinder-provisioner. I removed legacy code, which is not used anywhere.

@ramineni I didn't touch standalone driver. It is compiled correctly, check it by running make cinder-provisioner. I removed legacy code, which is not used anywhere, but adds a lot of confusion to new contributors.

Thanks, got it. One more question,
Looks like openstack_routes_test.go is being deleted when corresponding openstack_routes.go still exists, why is that?

@kayrus Interested to get it updated?

@ramineni yes, a little bit later.

/close
some of this is fixed in https://github.com/kubernetes/cloud-provider-openstack/pull/1036 , please repopen if you would like to work on this further.


Endpoint /member/info added.

Closing Issue #8: Missing endpoint was added.

Thanks @NoHeDidnt, I'll get this into a release ASAP.


the performance is quite slow

my gpu is 3080, use 38ms, the paper said 6900xt use 3ms.
I need set something?

sorry, after reboot my computer, it cost 3ms now, and ssgi is 1ms, still slow than paper, but not that much.


AAP-9450 Present useful message when engine is dead

Description
This PR adds a message "Deployment Engine unavailable, please re-deploy" when the login form receives a 502, which happens when the backend is timed out.  This is a partial fix, since it doesn't take care of an already logged in screen.  Maybe we should add a message on the UI that  shows itself when the backend goes away too.
Commit message reminder
Commit messages are important because they will be used to build list of items included in Errata when the deployment driver container image is built and QE will use that list to figure out what to test before the image is published.

For user facing features or fixes make sure Jira item number AAP-nnnnn is included in the commit message(s)
For other changes, like unit tests or code refactoring, do not include Jira item numbers

PR task checklist

[x] I have used appropriate commit messages based on section above
[x] I have performed a self-review of my code
[x] I have followed code style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added thorough tests
[x] I have had a successful deployment with the changes in this PR

Jira
This PR is for JIRA item: https://issues.redhat.com/browse/AAP-9450
Testing
Steps to test

Pull down the PR
Start deployment
Wait for engine to end naturally or connect to container and kill it ('server' process).
Attempt to log in, see new message.

Expected result
With the changes in this PR you will see a new message when attempting to log in when engine is down.

New commit changes Driver to Engine.

While this approach works and adds better handling of 502 error, we should follow up with a solution that checks status of the engine and present user with better, static page.

@tznamena
Does this mean we need changes or OK as is?
Do you think we should also pop up a message on the main page if the backend goes away (GET on /steps starts failing, which could be a trigger).

While this approach works and adds better handling of 502 error, we should follow up with a solution that checks status of the engine and present user with better, static page.

@tznamena Does this mean we need changes or OK as is?
Do you think we should also pop up a message on the main page if the backend goes away (GET on /steps starts failing, which could be a trigger).

This PR is OK as is, we will need another Jira work item to implement a status API for the engine and whole new static page. We can then add a logic that re-routes user to it once engine goes away.


Validations should not work without required options

Validations should not work without required options nor show error messages.
https://stackblitz.com/edit/angular-pekuf1?file=app/app.component.ts

expression: (c) => !c.value || /(\d{1,3}\.){3}\d{1,3}/.test(c.value),


Action Type Check in Env [feature request]

Describe the bug
TypeError: 'int' object is not subscriptable
Ran a couple time into this bug, and found it really hard to debug within stable baselines.
To spare others (as well as my future self) much frustration I would suggest to add a type check to wrapper envs like dummyEnv (or only check_env?) before using the action to make sure it's an iterable, before continuing with the code.
The following example assertion will give a developer friendly error message that's easy to understand and offers an immediate solution, saving much frustration.
Code example
obs, reward, done, info = env.step(action)

https://github.com/hill-a/stable-baselines/issues/40#issuecomment-425743048
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/stable_baselines/common/vec_env/base_vec_env.py", line 134, in step
    return self.step_wait()
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/stable_baselines/common/vec_env/vec_check_nan.py", line 35, in step_wait
    observations, rewards, news, infos = self.venv.step_wait()
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/stable_baselines/common/vec_env/dummy_vec_env.py", line 41, in step_wait
    self.envs[env_idx].step(self.actions[env_idx])

Proposed Solution
self.actions = actions
try:
    iterator = iter(self.actions)
except TypeError:
    # not iterable
   raise Exception( "Action must be of type iterable. Try wrapping your action variable in a list [ ] to fix this issue." )

for https://github.com/hill-a/stable-baselines/blob/master/stable_baselines/common/vec_env/dummy_vec_env.py#L37

Hello,
Do you have a minimal example (minimal custom env) where that error happens?
It seems that you are using custom action generation (i.e. not using .train(), nor  .predict() to select the action).
But I agree we can add a check in the VecEnv (but using isinstance(actions, (list, np.ndarray))) and also checking that it corresponds to the number of environments.
Feel free to submit a PR that solves that issue ;)

It happens when I pass a single action, without wrapping it in a list. CartPole example where the possible actions are LEFT or RIGHT (one var) is an example.
The issue/code described by lhorus though is of the same problem.
OK for isinstance() method if list & np.ndarray are the only 2 iterables that are acceptable.
I can implement it here.
However, I'm not sure on how to check for  'checking that it corresponds to the number of environments'?

However, I'm not sure on how to check for 'that it corresponds to the number of environments'?

I guess that's just
if len(self.actions) != len(self.envs):
    raise ValueError("The number of actions needs to be equal to the number of environments in a VecEnv")

I guess that's just sth like

This works but we need to make an exception for the _UnVecWrapper.... cf PR


Android Webview Support

I am working to show this webapp on an Android using webview. It doesnt work :(

I was a permission problem, dumb me...


Silence gcc false positive

The strncat call is perfectly safe. It wasn't previously giving a warning
but as of gcc-11, that is no longer the case.
Closes #3806

Passing run for a gcc 11 test environment:

Here's the pre-change build error with gcc 11:

With change:


Login: should remove -p option

It is fundamentally unsafe as terminals are often logged by default. Having a -p option encourages unsafe behaviour.

Hi @sebasgarcep, thanks for the report. I think you're probably right here, and this has been on our radar for a little bit. We're currently working on overhauling a bunch of our authentication stuff, and I expect we'll be able to support a token-based environment variable instead of the CLI password flag soon.
We're hoping to have this in place sometime in January 2017, and I'll update this issue once it's available.

tracking in https://github.com/expo/expo/issues/172


[fixed] db-migrations-job did not have spec.serviceAccountName

Describe your changes :
The db-migrations-job chart didn't have a parameterized spec.serviceAccountName field and as a result, db migrations couldn't authenticate using a serviceAccount.
When I added it with the correct value to my own deployment, the migrations ran w/out error, so this seems to be a complete fix.

Type of change :

[x] Bug fix

Frontend Preview (Screenshots) :
n/a

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have performed a self-review of my own.
[ ] I have tagged my reviewers below.
[x] I have commented on my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] All new and existing tests passed.

Reviewers
@sureshms @harshach

Hello @awittzb . The changes looks good to me. Can you please rebase the PR and fix the merge conflicts. We would love to get this available in the upcoming Helm Release. Thanks.

Thanks @awittzb ! Will be merging in!


Partial plugin ids

Not sure.
Currently, if a plugin doesn't have an id property, the file name (possibly postfixed with a number) is used as the id.
It may be useful to allow a user to partially supply an ID, e.g.
File name is: my-plugin
Allow the plugins to specify a suffix.
E.g.
module.exports = [
  {
    id: '*-thing'
  },
  {
    id: '*-json'
  }
]

Would define 2 plugins, with ids: my-plugin-thing and my-plugin-json.
It should only apply to ids which are prefixed with a *.

Idea behind this is so you can e.g. have a plugin with a filename "local-system.js", and export an array of plugins inside, e.g.

*-env - lists environment variables
*-proc - does something with processes
*-file - something about files

Then the IDs are more uniform with  the same prefix - local-system-env

Probably not worth it. IDs aren't that important for user plugins. And it would add complexity for no real reason.
Maybe come back to it if Swish-Core becomes more popular.
Also there is a workaround:
const prefix = 'my-plugin';

module.exports = [
  {
    id: `${prefix}-thing`
  },
  {
    id: `${prefix}-json`
  }
];
``


Lookup models using the datasource modelbuilder instead of cfg file

Reached this approach through a discussion with the loopback developers.  You can read the exchange on the google group:
https://groups.google.com/forum/#!searchin/loopbackjs/seth$20schubert/loopbackjs/dKOI4UHqfcU/JOoldrT38WQJ

I've addressed the issues raised in the latest commit - let me know if you find anything else

I will test today. Thanks


Feature/add docker goreleaser

Add docker build to goreleaser

Scan submitted to Checkmarx

Checkmarx SAST - Scan Summary & Details
Cx-SAST Summary
Total of 7 vulnerabilities 0 High 0 Medium 7 Low 0 Info
Violation Summary
No policy violation found

Checkmarx SCA - Scan Summary & Details
Cx-SCA Summary
Total Packages Identified: 0
Scan Risk Score: 0.00
 0 High severity vulnerabilities
 0 Medium severity vulnerabilities
 0 Low severity vulnerabilities
View more details on Checkmarx UI
Cx-SCA vulnerability result overview
No package violation found


FeatureSet record has empty ReferenceSet field

The current implementation of FeatureSet is not properly initialized with a valid ReferenceSetId, and the corresponding field in responses to featuresets/search and featuresets/<id> is currently left blank.

This is resolved in the sql repo branch.

Not sure I see how - I've been testing the jeromekelleher/remove-filesystemdataset branch today (which I believe is the latest SQL repo manager codebase), and addFeatureSet (as well as removeFeatureSet) is not implemented in the RepoManager object there yet. Unless there's some other place I should be looking, I'll supply the needed code.

It looks like something weird has happened with that branch @macieksmuga, sorry about that. It's turned into a bit of a mess trying to keep all these PRs going at the same time. Here's what happens with the code in the sql_repo branch now:
jk@holly$ python repo_dev.py init test.db  -f
jk@holly$ python repo_dev.py add-dataset test.db ds
jk@holly$ python repo_dev.py add-featureset test.db ds tests/data/datasets/dataset1/sequenceAnnotations/gencodeV21Set1.db
repo_dev.py: error: a reference set name must be provided
jk@holly$ python repo_dev.py add-featureset test.db ds tests/data/datasets/dataset1/sequenceAnnotations/gencodeV21Set1.db -R NCBI37
repo_dev.py: error: ReferenceSet with name 'NCBI37' not found
jk@holly$ python repo_dev.py add-referenceset test.db tests/data/referenceSets/NCBI37.fa.gz
jk@holly$ python repo_dev.py add-featureset test.db ds tests/data/datasets/dataset1/sequenceAnnotations/gencodeV21Set1.db -R NCBI37

Closed by #1166.


Add upload component

I don't think this component could be placed in the category: Component Collections.
Even could, it should be added to the last line of category
And why added a break line?

Hi there!
@airyland

I don't think this component could be placed in the category: Component Collections.
Even could, it should be added to the last line of category

That's true.
I think that it should be moved UI Elements category. (e.g. vue-file-base64)
@lian-yue
Can you push the PR once more ?


Enable VK_KHR_storage_buffer_storage_class on VK-1.0

This is required for the next Naga update, see https://github.com/gfx-rs/naga/pull/612

Is SPIR-V 1.3 required Vulkan 1.1 ?
Based on  Android distribution dashboard this requirement drops 22.0% of Vulkan based devices. Also based on gpuinfo.org information VK_KHR_storage_buffer_storage_class not supported on 23.7% devices.

yes, Vulkan 1.1 requires SPIR-V 1.4.
I'm told that pretty much everything under the sun either supports the extension, or Vulkan 1.1

I'm told that pretty much everything under the sun either supports the extension, or Vulkan 1.1

Maybe my point looked too scary (drops 23% of Android devices), but after I open my link again I realized that only 19 devices don't support VK_KHR_storage_buffer_storage_class 😄
Is this an urgent task? Can I try to solve it?

Please do!
This is a little bit urgent in a sense that it's going to block the next naga train (gfx-19), which we aren't doing yet.
We haven't fully got gfx-18 arriving to wgpu-rs yet, even.


Support local podspec file that download sources from remote.

I'd like to get a function such as below, any good idea?
for now I implemented it by describing path with file://.
curl https://raw.githubusercontent.com/Alamofire/Alamofire/master/Alamofire.podspec > path/to/local_podspecs/Alamofire.podspec

pod pack file://path/to/local_podspecs/Alamofire.podspec ...

The reason why I needed is to create also frameworks that not published libraries.

nice!


gatsby build fails

gatsby: 2.0.17
gatsby-plugin-cockpit: 1.0.39
Error Message:
Your plugins must export known APIs from their gatsby-node.js.
The following exports aren't APIs. Perhaps you made a typo or your plugin is outdated?
See https://www.gatsbyjs.org/docs/node-apis/ for the list of Gatsby Node APIs

The plugin<EMAIL_ADDRESS>is exporting a variable named "collectionsItems" which isn't an API.

The plugin<EMAIL_ADDRESS>is exporting a variable named "regionsItems" which isn't an API.

The plugin<EMAIL_ADDRESS>is exporting a variable named "collectionsNames" which isn't an API.

That’s a different plugin, not the one I develop.
I can try mine out later with gatsby v2 and see if there’s any work to be
done.
On Thu, 4 Oct 2018 at 15:54, Craeckerffm<EMAIL_ADDRESS>wrote:

gatsby: 2.0.17
gatsby-plugin-cockpit: 1.0.39
Error Message:
Your plugins must export known APIs from their gatsby-node.js.
The following exports aren't APIs. Perhaps you made a typo or your plugin
is outdated?
See https://www.gatsbyjs.org/docs/node-apis/ for the list of Gatsby Node
APIs

The plugin<EMAIL_ADDRESS>is exporting a variable
named "collectionsItems" which isn't an API.
The plugin<EMAIL_ADDRESS>is exporting a variable
named "regionsItems" which isn't an API.
The plugin<EMAIL_ADDRESS>is exporting a variable
named "collectionsNames" which isn't an API.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mpartipilo/gatsby-source-cockpit/issues/6, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAcgaTjr4mCBg1tBqgsKlC_fgx-FGBZwks5uhhMRgaJpZM4XIKXV
.

cheeese, im sorry.
i got fooled by the github link on the gatsby plugin-page


Update publish command's --skip-existing description

This is Twine's description of this flag:
  --skip-existing       Continue uploading files if one already exists. (Only valid when uploading to PyPI. Other
                        implementations may not support this.)

I originally interpreted this as "upload the file anyway" -- which is wrong and sounded odd since being able to replace published packages probably wouldn't be great design for a package repository.
To me this wording is more clear about what this flag actually does.

Can you also add this to the docs?


Fix meta copy invalid argument err

hi @benbjohnson . in my prj, tx.WriteTo returns "meta copy: invalid argument" err.
we use bytes.Buffer as argument of tx.WriteTo,
since we may write some headers before calling tx.WriteTo the buffer not always page-aligned.
Under linux, O_DIRECT requires page-aligned buffer,
and tx.WriteTo should guarantee that.
test code:
buf := bytes.NewBuffer(make([]byte, 8))
ok(t, db.View(func(tx *bolt.Tx) error {
       n, err := tx.WriteTo(buf)
       return err
}))

ping @benbjohnson , any other solutions?

@xiaost Sorry for the delay. I went through the code when you first PR'd but I want to research and understand the O_DIRECT issue better. I also want to do some additional testing/quick tests and try this on a variety of operating systems before merging. I just haven't had the time though to devote to it unfortunately.


Properly exit the watchdog Observer to avoid daemon thread crashes

Daemon threads can cause Python to crash on exit: http://bugs.python.org/issue1856. This was fixed for Python 3.2+ but was backed out from Python 2.7: http://bugs.python.org/issue21963.
I literally get the very same crash on exit described in the Python issue randomly (Debugged with Symbols). It reproduces for me by stressing the reloader. That means constantly modifying files.
Reproduces for me on Windows.

Thanks for the fix. Applied.